• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 562 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWR1642BOOST: How to calculate the configuration parameters "cfarCfg" and "doaCfg" according to the traffic_monitoring demo?

user6092104
Prodigy 220 points
Part Number: IWR1642BOOST

Hi, TI teams,

In the TI traffic_monitoring demo (c:\ti\mmwave_industrial_toolbox_3_6_1__win\mmwave_industrial_toolbox_3_6_1\labs\lab0013_traffic_monitoring_16xx), I use the  <mmw_tm_demo_longRange.cfg> configuration file, but it could not meet my requirements, so I try to use the mmWaveSensingEstimator tool to modify the parameter according to the <mmw_tm_demo_longRange.cfg> configuration file, as below,

I try to modify the "profileCfg" and "frameCfg" according to the simulation result, but I do not know how to modify the "cfarCfg" and "doaCfg",.

I read the DSS and MSS source code, "mmwave_sdk_user_guide.pdf" file, "index.html" file(c:\ti\mmwave_sdk_02_00_00_04\packages\ti\demo\xwr16xx\mmw\docs\doxygen\html\) and some documents in TI website, but I still can not find  how to calculate the parameters value about "cfarCfg" and "doaCfg".

Could you offer a few suggestions? I am looking forward for you respond.

Tahnk you.

Regards,

eric

  • Former Member
    0 Former Member

    Hello Eric,

    The Sensing Estimator serves to provide information for configuring the radar front end via the chirp profile and frame config settings. CFAR and DOA are the processing algorithms used and are not exactly related to the sensing estimator except for that you can set the detection limit which relates to the threshold in dB needed for detection. The CFAR threshold can be adjusted to match your settings. 

    Amanda 

  • 0 in reply to Former Member
    Prodigy 220 points

    Hello, Amanda,

    Thank you for your reply.

    I just try to modify the "profileCfg" and "frameCfg" according to the simulation result as above picture.

    The old value,

    <profileCfg 0 76 2 5 52.62 0 0 4.007 1 256 5490 0 0 48>
    <frameCfg 0 0 118 0 50 1 0>

    The new value,

    <profileCfg 0 77 2 4.30 36.88 0 0 9.51 1 178 5636 0 0 48>
    <frameCfg 0 0 180 0 40 1 0>

    The other configuration parameters are same.

    I open the "tm_demo.exe"(C:\ti\mmwave_industrial_toolbox_3_6_1\labs\lab0013_traffic_monitoring_16xx\gui), connect the UART, load the configuration file, then click Start, but it is no data output in Data COM.

    Finally, the tm_demo window quits automaticly and print ERROR Message in script window.

    So I use the CCS Debug the DSS and MSS program, I retry to load the configuration file again, the CCS debug log is below,

    [Cortex_R4_0] **********************************************

    Debug: Launching the Millimeter Wave Demo
    **********************************************
    Debug: MMWDemoMSS Launched the Initialization Task
    Debug: System Heap (TCM): Size: 98304, Used = 4880, Free = 93424 bytes
    Debug: MMWDemoMSS mmWave Control Initialization was successful
    [C674X_0] Debug: Logging UART Instance @00816110 has been opened successfully
    Debug: DSS Mailbox Handle @0080c488
    Debug: MMWDemoDSS create event handle succeeded
    Debug: MMWDemoDSS mmWave Control Initialization succeeded
    Debug: MMWDemoDSS ADCBUF Instance(0) @008160f8 has been opened successfully
    Debug: MMWDemoDSS Data Path init succeeded
    Debug: MMWDemoDSS initTask exit
    [Cortex_R4_0] Debug: CLI is operational
    Error: MMWDemoMSS mmWave Stop failed [Error code -203227134]
    Error: MMWDemoMSS mmWave Stop failed [Error code -203227134]
    Debug: Heap before creating a tracker
    Debug: System Heap (TCM): Size: 98304, Used = 25664, Free = 72640 bytes
    Debug: MMWDemoMSS Received CLI sensorStart Event
    Error: MMWDemoMSS mmWave Configuration failed [Error code -203685734]

    Are there any other parameters should be modified at the same time?

    Regards,

    Eric

  • Former Member
    0 Former Member in reply to user6092104

    Hello,

    Please note that the Sensing Estimator doesn't take into consideration digital processing constraints and requirements. The profile and frame configs generated by the estimator are calculated based on RF analog front end requirements. Because the processing time and memory requirements vary from demo to demo the estimator can generate invalid commands for the a specific demo.

    You can debug the error by following the steps in this e2e thread and adjust your commands accordingly.

     

    https://e2e.ti.com/support/sensors/f/1023/t/723912?IWR1642BOOST-Changing-profileCfg-parameters-in-the-people-counting-demo

    Amanda