• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 351 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:

AWRL1432: velocity disambiguate in SDK 5.3 MMW demo

AWRL1432: How does SDK5.3 MMW demo achieve a speed measurement range of ±120km/h?

J G1
Intellectual 835 points
Part Number: AWRL1432

Hi,

    I am working on a project using the MMW demo of SDK5.3, which requires a speed measurement range of at least ±120km/h and a maximum detection distance of >70 meters.

    Since MMW demo only supports 2tx BPM mode, even if there are only 256 real sampling points, the maximum unambiguous velocity is only about 60km/h.

    MMW demo currently does not support velocity disambiguate at the point cloud level. I plan to use g-track for velocity disambiguate. But if the target speed >60km/h, the Doppler compensation before BPM decoding will be wrong, which will lead to angle measurement errors in the point cloud, so g-track cannot solve my problem.

    I tried to use only 1tx, but this configuration resulted in many abnormal point clouds, and the document also said that MMW demo only supports 2tx BPM mode, so 1tx is not feasible.

  

    So, I have two questions:

    1.Will the MMW demo in the next version of the SDK support velocity disambiguate in BPM mode or support 1tx mode?

    2.Besides waiting for the new SDK, is there any other way for me to achieve a speed range of ±120km/h?

    Thanks！