• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 793 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.

AWR1843AOPEVM: Obstacle Detection AOP effective sensing distance

Cherry Zhou
Mastermind 22235 points
Part Number: AWR1843AOPEVM
Other Parts Discussed in Thread: MMWAVE-DFP, MMWAVE-STUDIO, AWR2243, AWR1243, AWR1843AOP

Hi team,

Here's an issue from the customer may need your help:

The customer is trying to follow the link  below to modify the .cfg file:

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1076086/awr1843aopevm-obstacle-detection-aop-demo-max-range-for-detection?tisearch=e2e-sitesearch&keymatch=Obstacle%252520Detection%252520AoP

On the GUI ods_3d_visualizer.exe graph, although you can see something marked out in a distance, when a real person enters the sensing area, it is only sensed within 2m.

Are there any other parameters that need to be corrected to allow the program to detect something that is actually farther away?

When the person is at 1m (the red box):

When people fall back to 2m (green box right in the middle of the screen):

People back to 2m (no one detected):

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Mastermind 35425 points

    Hello Cherry,

    Please do go through this document for understand more on how to design the chirp for the distance, velocity and other parameters https://www.ti.com/lit/an/swra553a/swra553a.pdf

    Regards,
    Saswat Kumar

  • 0 in reply to Saswat Kumar
    TI__Mastermind 22235 points

    Hello Saswat Kumar,

    Thanks for your support.

    Regarding the mmwave-dfp and mmwave-studio of section 5.4 in Programming Chirp Parameters in TI Radar Devices, is the difference between the two different IC models that apply?

    MmWave-DFP is available for AWR1243, AWR2243. While the mmWaveSensingEstimator in mmWave-studio works with xWR1243, xWR1443, xWR1642, xWR1843, xWR6843, xWR6443. 

    The customer is using AWR1843AOP. Is it ok to directly use mmWaveSensingEstimator to configure the required parameters or is the mmWave-DFP tool also common? 

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 35425 points

    Hello Cherry,

    So, the sensing estimator is only a tool which generates the Cfg file. It does not configure the board directly. based on the values provided to the sensing estimator, the output which is a config file is given to the demo as an input.
    Could you be more specific as to what mmwave-DFP tool you are mentioning here?

    Regards,
    Saswat Kumar

  • 0 in reply to Saswat Kumar
    TI__Mastermind 22235 points

    Hello Saswat Kumar,

    The customer just wants to confirm that if the values generated by the estimator can directly modify the Lab14 obstacle Detection AOP .cfg file, or is there a limited specific example to use directly? Any remaining examples need to be modified?

    They had try to modify the .cfg of Lab14 using the value generated by the mmWaveSensingEstimator but failed.

    While based on the MMWAVE-DFP in the above file you given, the customer would you to figure out the difference and whether it is common on AWR1843AOP?

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 35425 points

    Hello Cherry,

    Could you explain what failed? As in what is not working if they are changing the cfg files?
    Also are you modifying the cfg files that is present or directly trying to plug in the cfg file generated by the sensing estimator?

    Regards,
    Saswat Kumar

  • 0 in reply to Saswat Kumar
    TI__Mastermind 22235 points

    Hi Saswat Kumar,

    For example, as you can see below, use mmWaveSensingEstimator to generate the following values:

    profileCfg 0 60 7 4.1 97.29 0 0 32.54 1 625 6779 0 0 30
channelCfg 15 7 0
adcbufCfg -1 0 1 1 1
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 15 0 100 1 0

    Then update these parameters to .cfg to generate follows:

    sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
profileCfg 0 60 7 4.1 97.29 0 0 32.54 1 625 6779 0 0 30
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 15 0 100 1 0
lowPower 0 1
guiMonitor 1 1 0 0
cfarCfg 1 4 12 4 2 8 2 256 30 2 0 5 100 0.5
dbscanCfg 4 4 13 20 3 256
sensorStart

    Then use the GUI to load .cfg:

    Although it looks like it can be loaded, the GUI does not show anything:

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Guru*** 148804 points

    Hi,

    Please give us some time to review this question

    thank you

    Cesar

  • +1
    TI__Expert 4250 points

    Hello Cherry,

    The obstacle detection experiment is customized for the 2m range. Please ask the customer to use the out of box demo instead.