• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 500 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.

AWR1642: ExtendedMaxVelocity wrap around issue when the detected target is relative zero velocity and doppler is 128. The result is -128 not 0.

James Austrial
Expert 4030 points
Part Number: AWR1642

Hi,

HW AWR1642 ES2.0

SW mmWave SDK 2.0

When ExtendedVelocity is set, and Doppler(numloops) is 128 pts, then resolved Doppler index could be -128 to 127.

We met the a wrap around problem: When we measured a detected target of relative zero velocity, the measured the Doppler index result in -128, not 0.

Is this a known issue? How to avoid it?

 

  • 0
    TI__Guru 69960 points
    Hello james,
    Let me check with team and get back to you.


    Regards,
    Jitendra
  • 0
    TI__Guru 69960 points
    James,
    Could you describe us more about the setup?
    How many objects at observed in the detected range, azimuth angles of these objects, also was there a channel calibration performed, etc.?
    When extended velocity is enabled we test for two hypotheses, one for non-aliased velocity and one for aliased velocity, and select more likely hypothesis, i.e. one with the maximum peak in the azimuth FFT output.

    In the static scene normally the zero velocity should have been picked. It would be good if you can pull out and plot azimuth FFT output for the two hypotheses to visually compare them.


    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    TI__Expert 4030 points

    Hi Jitendra,

    After more field testings customer found too many error scenarios regarding to this ExtendedMaxVelocity feature no matter static objects or moving objects.
    Customer decided not to use ExtendedMaxVelocity.

    I close this thread.

    Meanwhile, I would suggest worldwide team to do the real field test for this ExtendedMaxVelocity feature and keep improving it.
    A lot of errors can't be seen in chamber. 

    Thank you.