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

AWR1843: Wall detection and parking assistance

AWR1843: Why is detecting walls insensitive compared to obstacle detection?

Lei
Expert 2050 points
Part Number: AWR1843

I use automotive mrr demo to detect a wall.

The radar sensor opposits to a white painted wall about 4 meters. When radar sensor is static, the GUI tool doesn't show that there are any detected objects 4m away from; when radar sensor is moving, the GUI tool shows a detected object. But comparing to wall detection, GUI tool shows that the radar sensor can see more objects when detect an obstacle, such as a steel bar.

Logically, a wall has much larger reflection surface than an obstacle, but it seems radar sensor is less sensitive to detect it. 

Can you please explain this behavior and is it possible to increase the sensitivity of wall detection?

Kind regards

  

  • 0
    TI__Guru*** 148804 points

    Hi,

    The reflectivity of the wall makes detection challenging.

    The MRR demo was designed for adas detection. It may not be optimal for wall detection.

    Isn't the wall detected even for MRR sub-frames?

    Here are some things that can help

    • Increase Rx Gain
    • Lower CFAR threshold

    If  the main use case is wall detection, you could also use the mmWave SDK oob demo

    thank you
    Cesar

  • 0 in reply to Cesar
    Expert 2050 points

    Thank you very much. 

    Can I ask what are the differences in the design for ADAS detection and other detection? What are the benefits and downsides we have with MRR demo comparing to OOB demo?

    Thanks

  • +1 in reply to Lei
    TI__Guru*** 148804 points

    Hi,

    As you have probably seen in the MRR demo documentation, this demo was developed to support two types of sub-frames

    • Ultra Short Range - max range 30m, MIMO (one Tx enabled at a time)
    • Medium Range - max range 120m, Beam Forming (all Tx enabled at the same time)

    The mmWave SDK demo was developed as a general purpose MIMO demo and does not support Beam Forming.

    So, the main benefit of the MRR demo is Beam Forming Support. This provides capability for longer range.

    The downside is that longer range has smaller field of view and smaller angle resolution.

    If your use case requires short ranges than probably using Beam Forming is not recommended and you should focus on using the mmWave SDK demo instead of the MRR demo.

    thank you

    Cesar