• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 322 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.

AWR1642BOOST: How to relate the parsed data v, compDetectedRange, azimuth, elevation, SNR and noise to the X-Y scatter, range profile for zero doppler and doppler-range plot.

robert Low
Prodigy 30 points
Part Number: AWR1642BOOST

Attached are my config files, mmWave demo recorded data, image of visualizer scatter plot and Ti scripts. I used the python script available in C:\ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\demo\parser_scripts\ by editing to print more hex data. I can't find the relationship between the parsed data v, compDetectedRange, detectedAzimuth, detectedElevAngle to the X-Y scatter, range profile for zero doppler and doppler-range plot. Also, SNR and Noise always zero from the parsed data, but the plot showing values other than zero.

0317.data.zip

  • 0
    TI__Mastermind 32705 points

    Hi,

    We will check this internally and get back to you by next week.

    Thanks,

    Pradipta.

  • +1 in reply to robert Low
    TI__Mastermind 20605 points

    Hi Robert,

    Thank you for your patience.

    Here is the sequence of steps from device to parsed data:

    • Device (AWR) processes radar ADC data and generates different outputs based on its input signals.
    • The output on the device is packetized into a Tag-Length-Value (or TLV) format based on different types of data to be sent out.
    • This packetized data is shipped out via the UART data port.
    • This UART data is intercepted by the mmWave Demo Visualizer.
    • The TLV data is parsed, and some additional changes are done to the data to enable various types of plots that you see. This processing is done on the Visualizer and the data at used here will also be the one that is logged onto the .dat file when a capture is initiated.
      You can use F12 on your browser to view the source code of the demo visualizer in the file mmwave.js if you are keen on understanding how the data is translated.
    • This .dat is further decoded by the python script to see what you obtain.

    Regards,

    Kaushik