• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 1709 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.

AWR1642BOOST: The parameters of mmwave sensing estimator to configure file cannot run on mmave demo visualizer, why?

A-Kai
Intellectual 310 points
Part Number: AWR1642BOOST


Hi, 

   I modified the CLI config file(.cfg) with the parameters of mmwave sensing estimator ver 1.3.0 and used it to mmwave demo visualizer ver 3.2.0. But It will generate "Error: incorrect cofig reported ...".

   The procedures we create the config file and test result are as follows.

 Step 1: Use mmwave sensing estimator ver 1.3.0 to modify the system spec and generate the chirp configuration parameters.

       

 Step 2:  modify config file(profile_2d_new.cfg) based on the chirp configuration parameters from step 1 and TI SDK 3.2 samples profile file, profile_2d.cfg. The file comparison is as follows.

        

 Step 3: Input the profile_2d_new.cfg to mmwave demo visualizer 

   

Step 4:  the error will show   "Error: Incorrect cofig reported ..." on mmwave demo visualizer

   

Q1: Where is something wrong for the configure file (profile_2d_new.cfg) in step-2 about ProfileCfg and FrameCfg command ???

Thanks for your support and help.

Best Regards,

 A-Kai

  • 0
    TI__Guru*** 149854 points

    Hi,

    Could you try to increase in profileCfg the idle time to 5?

    thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 310 points

    Dear Cesar,

      I just tried the idle time up to 5, It will happen another error message as shown in demo visualizer and CSS debug console.

      1. Demo visualizer:

        

      2. CSS debug console:

       

     My question is : why are the CLI commands of config file not consistent with the parameters of mmwave sensing estimator ?  

     Thanks for your help.

     Best Regards,

      A-Kai

  • 0 in reply to A-Kai
    Intellectual 310 points

    Dear Cesar,

        I re-built the newest binary codes of mss and dss  based on the user manual section 4.5.3, Building demo,  on C:\ti\mmwave_sdk_03_02_00_04\packages\ti\demo\xwr16xx\mmw. 

       Then the config file test still fail  based on your suggestion which the idle time is modified from 2 into 5. 

        My questions are : 

       Q1: why are the CLI commands of config file not consistent with the parameters of mmwave sensing estimator ? 

       Q2: If we need to change the chirp parameters from mmwave sensing estimator due to system spec change again, how could I confirm these chirp parameters correct from the mmwave sensing estimator? 

       Thanks for your help.

      Best Regards,

      A-Kai

  • 0 in reply to A-Kai
    TI__Guru*** 149854 points

    Hi,

    Sorry for the late reply

    Question #1

    Q1: why are the CLI commands of config file not consistent with the parameters of mmwave sensing estimator ?


    This is a very common question on this forum. The answer to this question is that the mmWave SDK demo is a general purpose demo that is designed to showcase most features of the mmWave sensor. This means that there are configurations that will not work with this demo because the demo was not designed for that.

    The mmwave sensing estimator was designed to provide help for configuration design.

    Q2: If we need to change the chirp parameters from mmwave sensing estimator due to system spec change again, how could I confirm these chirp parameters correct from the mmwave sensing estimator?


    Our experience with the mmwave sensing estimator tool is that it is robust and only in a few corner cases it provides correct results.

    At the same time, one should also use the mmwave foundational equations to understand the configuration. Using the mmwave training provided and the following appnote (see below) it is possible to create the chirp configuration without the sensing estimator tool. This is one way that can be used to check that the chirp configuration produced by the tool is correct

    Programming Chirp Parameters in TI Radar Devices

    Thank you

    Cesar