• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 727 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.

IWR1843BOOST: Traffic monitoring demo cfg commands error and program abort

Zhikai Zhang
Prodigy 90 points
Part Number: IWR1843BOOST

Hi I am trying out the traffic monitoring demo and when I am sending the cfg file there are some errors and some skipped parsing: 

Not sure why they are the case since I used the cfg file in the chirp config folder instructed by the userguide

also another problem:
the visualiser stopped updating new info and got stuck if there are a lot of targets and if I move the sensor, I debugged the source code and it aborted, looks like the source is this assert in objectdetection.c:

Does anyone know how to resolve this issue?

I am using the mmwave_sdk_03_05_00_04 and industrial toolbox 4.5.1

thanks in advance!

  • 0
    TI__Mastermind 23725 points

    Hello

    Can you please confirm if you are using the provided version of binary image and config file that goes with it.

    Thank you,

    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Prodigy 90 points

    Yes I am using the provided prebuild binary, I did debug with css but they yielded the same end result, and the config file in chirp config folder

  • 0 in reply to Zhikai Zhang
    TI__Mastermind 30405 points

    Hi Zhikai,

    1. Are you sending the configuration file using the provided GUI or from a UART terminal program such as Tera Term (or a similar terminal program)?

    2. This should not result in the parsing error you mentioned earlier, however please note that there is a discrepancy in the trackingCfg command in toolbox 4.5.1 which will be corrected in a future release. This may result in incorrect tracking behavior so please modify the command as shown below.

    Can you modify the trackingCfg command as given below as let us know your observations?  

    Current: trackingCfg 1 2 250 20 113 355 50

    New: trackingCfg 1 1 250 20 113 355 50

    Please run the demo with the GUI using the command modified as above and share your observations.

    -Nitin

     

  • 0 in reply to Nitin Sakhuja
    Prodigy 90 points

    I am using the GUI, 

    I did modify it and doesn seem to change much of the result

    I changed the frame duration to a bigger number and now it is not aborting anymore idk if it was because it couldn't finish process in time for that before

    still some of the commands stopped parsing and there is alos error for the stateparam as mentioned in the post, how do I solve those? Because I used the cfg file in the toolbox and I didn't change any of it

  • 0 in reply to Zhikai Zhang
    TI__Mastermind 30405 points

    Hi Zhikai,

    Have you made any other modifications to the config like changing CFAR thresholds etc?

    -Nitin