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.

IWR1642BOOST: Increase Max Velocity in Traffic Monitoring

Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1642

Hi everyone,

I want to detect cars with high speed (up to 180 Km/h) in a short range. 

I changed the config file of "traffic monitoring", and run on IWR1642, but it didn't work.

I read these related posts, but I don't get my answer, so post a new thread.

I understand that to increase the "Max Velocity", sum of the "Idle time" and "Ramp End time" must be decreased. But when I decrease this sum lower than 25 us, the device don't work. I tried and changed every parameters and didn't work.

This config file work fine:

 channelCfg 15 1 0

adcCfg 2 1

adcbufCfg 0 1 1 1

profileCfg 0 77 5 8 20 0 0 21.5 1 64 6250 0 0 48

chirpCfg 0 0 0 0 0 0 0 1

frameCfg 0 0 64 0 100 1 0

 

but when I change "idle Time" form 5 to 4, don't work:

profileCfg 0 77 4 8 20 0 0 21.5 1 64 6250 0 0 48

 

or when I change "Ramp End time" form 20 to 19, don't work:

profileCfg 0 77 5 8 19 0 0 21.5 1 64 6250 0 0 48

 

Also, I used the mmWave Sensing Estimator to set the parameters in config file. My config has not any error in this tool but did not work.

 I have some questions, please help me.

1. Is it possible to detect a car with 180 Km/h with IWR1642 and "Traffic Monitoring" project just by changing the config file? How?

2. I think the "Traffic Monitoring" has limitations in config parameters, how to understand these limitation without trial and error. For example the minimum value of "Ramp End time". ( I read the documents and consider the formulas, also using the "mmWave sensing Estimator", but there are some limitation that i don't know.)

3. Why the output parameters from the "mmWave Sensing Estimator" have problem in device, but there is not an error in the tool?

 4.I did some practice tests and found that when the car's speed is more than "max velocity", it shows less speed. How can I understand if the speed of the car is more than "max velocity"?

 Thanks in advance for your consideration. 

  • Former Member
    0 Former Member

    Hello,

    1. Using the long range non-MIMO chirp configuration, the native max velocity of this config is ~65km/hr. With velocity extension enabled this would give ~3x for ~180km/hr.

    2/3 The sensing estimator doesn't take into consideration the digital processing requirements as this will vary across the signal chains and data output requirements. Therefore, unfortunately there is quite a bit of trial and error to the process currently.

    4. There is no way to know for sure that is why the max velocity is considered the limit for "unambiguous max velocity". Beyond that we have additional velocity extension to try and unwrap and determine the object's true velocity. However there are still some errors. The results can be see in this document http://www.ti.com/tool/TIDEP-0090

    Amanda

  • Thanks Amanda for your response.

    I don't get my answer about my config that not work. Please explain more about that. 

    How to enable "velocity extension" in chirp configuration?

    Please can you explain more about "Beyond that we have additional velocity extension to try and unwrap and determine the object's true velocity"?

    Thanks a lot for your help.

    Alireza

  • Former Member
    0 Former Member in reply to Alireza

    Please refer to the TI Design I linked which explains how the velocity extension works. 

    Your chirp configuration may fail due to timing or memory issues. Please see this thread on how to decode errors. You may need to be in CCS debug mode to see the error code: e2e.ti.com/.../2672951