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

IWR1642: Velocity Data not consistent for objects travelling parallel to IWR1642

Anup Kulkarni
Intellectual 335 points
Part Number: IWR1642
Other Parts Discussed in Thread: TIDEP-0090

I have a IWR1642 ES1.0 running SDK version 1.0

I need to detect heavy vehicles like trucks and commercial vehicles with containers attached, I only need the Y-Axis and Velocity information. The vehicles moves  in the parallel axis to X-axis of the sensor. 

I am able to read the data, but the velocity values show a maximum around 2.0 , even though the vehicle moves more than 60kmph. Due to this sometimes i detect slower moving objects also, which is not desired. 

Am I missing something?

  • 0
    TI__Guru 50240 points
    Hi Anup,

    We'll need more information in order to assist you. What demo are you running? Which chirp configuration are you using?

    Is this velocity data problem happening all of the time or only some of the time?

    Have you seen the Traffic Monitoring TI-Design? TIDEP-0090


    Cheers,
    Akash
  • 0 in reply to Akash Gondalia
    Intellectual 335 points

    Hi Akash,

    I am running the demo in sdk 1.0.0.

    I am using the configuration file, derivedlarge_area_veocity_resolution.cfg from the visualiser demo. Attached is one such configuration file. 

    For any other configuration, i have the same problem. 

  • Former Member
    0 Former Member in reply to Anup Kulkarni

    Hello Anup,

    I looked at your attached chirp configuration and the maximum unambiguous velocity is 2.5m/s. An object moving at 60kmh (~17m/s) will exceed the max velocity of the chirp designed and velocity wrapping will occur - causing the detection points to appear to have velocity as the remainder of actual velocity/2.5.

    To accurately determine velocity, you can either design a new chirp capable of greater max velocity or use maximum velocity extension.

    To achieve 60kmh I would suggest both strategies.

    If you want to continue using the OOB demo, you need to update to a newer SDK. SDK 1.02.00.05 which supports max velocity extension for 2x the max chirp velocity. Use the extendedMaxVelocity to enable this feature. More details can be found in the SDK user's guide (page 23).

    However, I would suggest you also refer to the Traffic Monitoring TI Design which gives an example chirp and uses vmax extension - this configuration and software is capable of 60kmh.

    Demonstration Video:

    Reference design with details on vmax extension:

    Lab on TIREX (please not you need to download Industrial Toolbox version 2.3.0 for your ES1.0 board)

    Thanks,

    Amanda