• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 349 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.

CCS/AWR1642BOOST: Do not understand the code of MmwDemo_XYestimation

user5916025
Prodigy 230 points
Part Number: AWR1642BOOST

Tool/software: Code Composer Studio

While building a project in mmWave Sensor Automotive Toolbox v:2.4.7 lab2 short range radar.

I tried to understand  the function by defining MmwDemo_XYestimation.

But I don't know why in this project, the code is only written to detect two angles.

I guess that the angular resolution is not enough, so we don't have to detect more angles.

I don't know if this is the reason, or the configuration capacity of this project is only allowed to measure two angles.

  • 0
    TI__Guru*** 147894 points
    Hi,

    The algorithm to perform angle estimation in the SRR lab is similar to the mmWave SDK Demo.

    I recommend you review the angle estimation documentation for this demo since it is more extensive and should provide you all the information needed to understand how the algorithm works. This is a standard algorithm that you will also be able to find in radar litterature.

    file:///C:/ti/mmwave_sdk_02_00_00_04/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html

    Thank you
    Cesar
  • 0 in reply to Cesar
    Prodigy 230 points
    Hello, thank you for your reply. But you misunderstood my problem.
    I know how TI detects object angles and their corresponding theories, so I don't want to ask the theoretical part.
    In theory, as long as the resolution of the angle is high enough, it is possible to detect multiple objects at the same speed and the same speed.
    However, in this project, I don't quite understand why we are only willing to detect two objects at the same speed and the same distance.
  • 0 in reply to user5916025
    TI__Guru*** 147894 points
    Hi,
    Yes, this is an implementation decision.

    The code only checks for two peaks of angle fft.

    We could have implemented the code to check for third peak. That would have added more complexity

    Thank you
    Cesar
  • 0 in reply to Cesar
    Prodigy 230 points

    i Cesar,

    Thank you for your response.

    I want to continue to understand this issue.

    Can I know what experiments or reasons you are based on, and then the code only checks for two peaks of angle fft ?

    Thank you

  • 0 in reply to user5916025
    TI__Guru*** 147894 points
    Hi,

    When implementing an algorithm on an embedded chip there are tradeoffs that have to be performed. Usually one is limited by processing cycles and memory.

    I think that in the case of this algorithm, the reason is processing cycles

    thank you
    Cesar