• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 516 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.

Original question:

IWR1642BOOST: Traffic monitoring velocity extension

AWR2944: Tracker layer max velocity extension of AWR2944

Ken Zhang
Expert 3455 points
Part Number: AWR2944
Other Parts Discussed in Thread: IWR1642

Hi Experts

In the release notes of  AWR2944 lab0015_high_end_corner_radar, It says 

The chirp configs support a maximum velocity of 140kmph natively. This is extended to 200kmph by the tracker.

In the following thread,  in traffic monitoring demo of IWR1642

IWR1642BOOST: Increase Max Velocity in Traffic Monitoring - Sensors forum - Sensors - TI E2E support forums

the native max velocity of this config is ~65km/hr. With velocity extension enabled this would give ~3x for ~180km/hr.

 How to decide the max extended velocity achieved by tracker?  or what's the relationship between max extended velocity and native max velocity of config by tracker?

  • +1
    TI__Genius 15046 points

    Hi,

    In the tracker, the maximum velocity extension is dependent on tracking the movement of the object itself. As far as I am aware, there is no mathematical construct behind this, but the shorter the interframe period, the better the tracker will be at Vmax extension. Finding out the extension achieved might just be a matter of verifying the results empirically.

    Regards,

    Aayush