• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 1367 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR1843: How to use sub-frameCfg?

TAK
Prodigy 150 points
Part Number: AWR1843


I want a chirp like below then I tried to make a configuration file like this, but the demo visualizer doesn't work.
Would you tell me which is the wrong command, please?

sensorStop
flushCfg
dfeDataOutputMode 3
channelCfg 15 5 0
adcCfg 2 1
adcbufCfg 0 0 1 1 1
profileCfg 0 77 429 7 57.14 0 0 17.5 1 256 5209 0 0 30
profileCfg 1 78 429 7 57.14 0 0 17.5 1 256 5209 0 0 30
profileCfg 2 79 429 7 57.14 0 0 17.5 1 256 5209 0 0 30
profileCfg 3 80 429 7 57.14 0 0 17.5 1 256 5209 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
chirpCfg 2 2 1 0 0 0 0 1
chirpCfg 3 3 1 0 0 0 0 4
advFrameCfg 4 0 1 1 0.1
subFrameCfg 0 0 1 4 2 10.0 4 1 1 20.0
lowPower 0 0
guiMonitor 0 1 1 0 0 0 1
cfarCfg 0 0 0 8 4 4 0 1280 1
cfarCfg 0 1 0 4 2 3 1 1280 1
multiObjBeamForming 0 1 0.5
clutterRemoval 0 0
calibDcRangeSig 0 0 -5 8 256
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
aoaFovCfg 0 -90 90 -90 90
cfarFovCfg 0 0 0 8.92
cfarFovCfg 0 1 -1 1.00
sensorStart

  • 0 in reply to TAK
    TI__Guru 70050 points

    Hi,

    In the given configuration you are using single frame setting, with that visualizer may not get sufficient object result to plot, recommend to make it '0' (infinite frame) and try.

    advFrameCfg 4 0 1 1 0.1 (single frame)

    advFrameCfg 4 0 1 1 0.1  (selected for 4 subframe but only one subFrameCfg CLI command is given)

    subFrameCfg 0 0 1 4 2 10.0 4 1 1 20.0 (chirp startIdx should start from zero to select 4 set of chirps).

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 150 points

    Thank you for your replying quickly.
    I changed to the configuration like below one.
    And demo visualizer indicates that necessary to reduce the frame rate, then I also changed the each periodicity time.
    But demo visualizer doesn't show any graph.
    May I have some tips additionally, please?
    We need some additional line of corresponding to each subframe index?

    Great thanks, Best Regards
    Tak

    sensorStop
    flushCfg
    dfeDataOutputMode 3
    channelCfg 15 5 0
    adcCfg 2 1
    adcbufCfg 0 0 1 1 1
    profileCfg 0 77 429 7 57.14 0 0 17.5 1 256 5209 0 0 30
    profileCfg 1 78 429 7 57.14 0 0 17.5 1 256 5209 0 0 30
    profileCfg 2 79 429 7 57.14 0 0 17.5 1 256 5209 0 0 30
    profileCfg 3 80 429 7 57.14 0 0 17.5 1 256 5209 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4
    chirpCfg 2 2 1 0 0 0 0 1
    chirpCfg 3 3 1 0 0 0 0 4
    advFrameCfg 1 0 0 1 0.1
    subFrameCfg 0 0 0 4 2 100 4 1 1 100
    lowPower 0 0
    guiMonitor 0 1 1 0 0 0 1
    cfarCfg 0 0 0 8 4 4 0 6000 1
    cfarCfg 0 1 0 4 2 3 1 6000 1
    multiObjBeamForming 0 1 0.5
    clutterRemoval 0 0
    calibDcRangeSig 0 0 -5 8 256
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    aoaFovCfg 0 -90 90 -90 90
    cfarFovCfg 0 0 0 8.92
    cfarFovCfg 0 1 -1 1.00
    sensorStart

  • 0 in reply to TAK
    TI__Expert 5320 points

    Hi Tak

    As mentioned in the user guide, for mmw demo, the way processing is structured, every subframe can only support one profile. 

    {quote}

    profileCfg: profileId

    Legacy frame (dfeOutputMode=1): could be any allowed value but only one valid profile per config is supported.

    Advanced frame (dfeOutputMode=3): could be any allowed value but only one profile per subframe is supported. However, different subframes can have different profiles

    {quote}

    Hence your configuration is not succeeding in getting through Visualizer. However, we have a bug in our parsing code due to which it is not throwing an appropriate error to help you root cause. We will address that in upcoming release. 

    if I change the chirpCfg for 2 and 3 chirps to use profile 0, your configuration goes through. 

    To keep your desired RF config, I would suggest reviewing the code in ti/demo/utils/mmwdemo_rfparser.c and understand how the various RF parameters are translated into processing chain related params.

    -Madhvi

  • 0 in reply to Madhvi
    Prodigy 150 points

    Thank you for your reply and support, I would try it to read and understand it.