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.

IWR6843AOPEVM: CFAR Config and DOA Config

Part Number: IWR6843AOPEVM

Hello,

So this is a little annoying, I searched everywhere for the cfarCfg property and the doaCfg, explaining what each number meant but couldn't find anything useful!

The pplcount customization guide has stuff about the doaCfg but doesn't explain all the numbers, and nothing about cfarCfg. As for the mmwave SDK i found cfarCfg but not doaCfg yet the numbers aren't explained properly, the numberl of sections under cfarCfg in the sdk is less than the numbers in the CFG (it doesn't say what all the numbers do)

I would appreciate it if someone could explain what the numbers mean for the doaCfg and the cfarCfg. like it was done in the pplCount customization guide e.g.

So the reason Im trying to understand this is because i've been tuning the parameters to remove ghosts, better detection when people are next to each other..but when I stop moving and stand still it doesnt detect me as a target anymore and only when I start moving, so I want to increase the sensitivity, would this be the right way to go? Below is my cfg file.

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 0
profileCfg 0 60.75 7 7 41.10 0 0 54.71 1 96 2950.00 0 0 36 
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
chirpCfg 2 2 0 0 0 0 0 4
frameCfg 0 2  96  0 50 1 0
dynamicRACfarCfg -1 4 4 2 4 8 16 4 4 4.00 4.50 0.50 1 1
staticRACfarCfg -1 4 4 2 4 8 16 4 6 12.00 13.00 0.30 0 0
dynamicRangeAngleCfg -1 0.75 0.0010 1 0
dynamic2DAngleCfg -1 1.5 0.0300 1 0 1 0.50 0.85 8.00
staticRangeAngleCfg -1 1 8 4
antGeometry0 -1 -1 0 0 -3 -3 -2 -2 -1 -1 0 0
antGeometry1 -1 0 -1 0 -3 -2 -3 -2 -3 -2 -3 -2
antPhaseRot 1 -1 1 -1 1 -1 1 -1 1 -1 1 -1
fovCfg -1 70.0 20.0
compRangeBiasAndRxChanPhase 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 
staticBoundaryBox -2 2 2 -8.5 -2 2
boundaryBox -1.5 1.5 0 2.6 -2 1
sensorPosition 1.9 0 -30
gatingParam 3 2 2 2 0
stateParam 10 3 10 40 5 600
allocationParam 100 800 0.1 15 0.1 20
trackingCfg 1 2 1000 20 67 105 50
sensorStart
Thanks for the help!

  • Hello

    Different demo may have a custom implementation specific to the needs of the application and implementation.

    So not all explanations from one demo would be valid of other demo.  Please check the demo specific config explanations.

    The Customization guide for Building automation demo  callas out the parameters that we would typically allow users to alter.  Are there any specific configuration changes that you are trying to make for tuning purpose.

    Thank you,

    Vaibhav

  • I want to increase the sensitivity because when I stand very still in front of the radar it starts detecting 0 targets. I want it to be able to detect me regardless if I standstill or move.

    Please advise.

    Kind Regards

    Sagar Jaiswal

  • Hi Sagar,

    First, you can lower CFAR settings:

    dynamicRACfarCfg -1 4 4 2 4 8 16 4 4 4.00 4.50 0.50 1 1 - decrease the bold values for more detected points.

    Second, you can modify the chirp to have a higher velocity resolution - increase idle time between chirps, increase frame time to 100 ms.

    Regards,
    Justin

  • Hi  

    How would I modify the chirp to have a higher velocity resolution? Where are the numbers explained for that? same with increasing the idle time between the chirps.

    I have a hunch how to increase the frame time, but it would help if you could tell me just so I could confirm, please!

    Thank you.

    Kind Regards

    Sagar Jaiswal

  • Hi Sagar,

    Please see the SDK user's guide, look at profileCfg and FrameCfg commands. Also see this document. Increasing chirps per frame gives better Velocity resolution without lowering Max Velocity, so if memory allows it is better to increase chirp loops. However, the default chirps use most of the memory so most likely it is easiest to experiment with increased idle time first. When increasing either value, you may need to increase Frame Period to allow enough time for the device to chirp and process the data.

    Regards,

    Justin