• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 29 subscribers
  • Views 631 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.

IWR6843AOPEVM: Out-of-Box Demo Data Struct

Bing Chen1
Intellectual 290 points
Part Number: IWR6843AOPEVM

Hi,

I was wondering if you could provide the data struct breakdown for the AOP out-of-box demo. I was not able to find the full definition in the mmw_output.h other than the frame header and the statistics.
What do TLV 01 (I assume detected objects?), 07, 06, and 02 stand for and how do they break down structurally?

If I simply want to record the raw point cloud, I would just use the AOP Area Scanner Demo, correct?

Thanks in advance!
- Bing 

  • Former Member
    0 Former Member

    Hello,

    You can find more details in the doxygen. Please go to docs directory in the SDK demo. (.../docs/doxygen/html/index.html). The section "Output Information to the Host" should describe each of the message types. The messages are enumerated so the first one in the list is 1 and the following are all sequentially assigned (ex range profile = 2 and noise profile = 3 and so on).

    Yes, if you are recording the UART stream using the record feature from the online visualizer you will get the entire UART stream and be able to save other plot and header information. Using the Area Scanner visualizer you will only be able to visualizer scatter plot data and save the point cloud to a CSV file.

    I would also recommend viewing the Matlab source code for an example of UART parsing.

    Amanda

  • 0 in reply to Former Member
    Intellectual 290 points

    Found it. Thanks a lot!