• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 511 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.

IWR6843: New SDK3.5 and Traffic Monitoring

user5310849
Intellectual 730 points
Part Number: IWR6843

Hello TI,

Last week I spotted that ne SDK and Industrial Toolbox has been released. Especially I was looking forward to sensor position configuration and other stuff.

Unfortunately, using the same parameters for the tracker, the tracking does not seems correct. We have managed to tune the tracking for the previous version (although there were and still are bad max speed and speed resolution values in the .cfg file). Were there any changes or is there any reason why this should not work (constantly failing tracking object – track does not follow the object speed)?

Another issue I’m facing is with CLI customization. Only 32 values are supported in SDK/Toolbox and now with custom commands and additional commands for updated demo I’m over that limit. 64 would be definitely better.

Thank you, Lukas

  • Former Member
    0 Former Member

    Hello,

    There are changes from the older tracker to the new. If you have already tuned for the old tracker it may not benefit you to migrate to the new tracker and go through retuning.

    If you choose to use the sensor position command you should ensure that you've defined the position and boundary boxes accordingly.

    For the CLI commands you can modify the demo to remove the additional tracker CLI commands and instead have the values hardcoded if you do not need the CLI functionality for those parameters.

    Amanda

  • 0 in reply to Former Member
    Intellectual 730 points

    We would definitely like to use the sensorPosition parameter and thus define the elevation of the sensor. Thus I'm wondering what can be so different because tracker is not following objects at all. How can I determine version of tracker (in the first and the other case) as there is also changelog with latest version?

    Thank you, Lukas

  • 0 in reply to user5310849
    TI__Mastermind 30405 points

    Hi Lukas,

    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

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    TI__Mastermind 30405 points

    Hi Lukas,

    Since we have not heard back from you, we'll assume this issues is resolved, and close the thread. Please create a new thread for further support.

    Regards

    -Nitin