AWR1642: The target is seen in two different azimuth, but at same range when we run mmwave demo project.

Rajesh Desai

Hello,

We have kept the AWR1642device on one vehicle which is not moving. This means sensor is kept at fixed location. Then we have another vehicle which is approaching the sensor at 30KMPH constant speed from 60m distance. we have collected the plot data and analyzed the detection. we plotted range vz azimuth and range vs frame number. we found the single target is coming in two different azimuth with same range.

The same vehicle which is cumming from 60m say in azimuth 0, is also coming in +15 degree azimuth also. both these detection are belonging to same time stamp.

did anyone come across this problem. Please let us know what could be issues.

Regards,

Rajesh

over 7 years ago

0 Anil Mani over 7 years ago

TI__Expert 4720 points

Hello Rajesh,

Which version of the SDK are you using or are you using your own scripts? Can you share an image of the detection? Could you also your configuration and what the maximum-unambiguous velocity of your configuration is?

Regards

Anil

0 Rajesh Desai over 7 years ago in reply to Anil Mani

Prodigy 95 points

Hello Anil.

we are using

We are using mmwave_sdk_01_00_00_05 sdk version.

Regards,

Rajesh

0 Anil Mani over 7 years ago in reply to Rajesh Desai

TI__Expert 4720 points

Hi Rajesh,

I suspect that the car in question exceeded the maximum unambiguous velocity of the chirp configuration that you selected. In that case, please
move to the mmwave sdk v1.1, which has a max-velocity enhancement algorithm that should help in such cases.

Regards
Anil

Sensors

Sensors forum

AWR1642: The target is seen in two different azimuth, but at same range when we run mmwave demo project.