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.

AWR1843BOOST: mmWave demo: clustering and tracking outputs in gui monitor

Part Number: AWR1843BOOST

Hello, 

The GUI for mm-wave demo project shows clustering and tracking outputs. In the mss_main.c, the UART outputs are 

  1. detectedObjects
  2. logMagRange
  3. noiseProfile
  4. rangeAzimuthHeatMap
  5. rangeDopplerHeatMap
  6. statsInfo

In my understanding, the clustering and tracking outputs are being sent through detectedObjects via UART to GUI. The detectedObjects structure contains x, y, z, doppler, snrand noise. I exported the detectedObjects data in Matlab and plotted it, but didn't see the output in the form of clusters and trackers like shown in the attached figure.

It'd be great if someone could clarify:

  1. how the clusters and trackers are sent to GUI and how the rectangular and diamond boxes are formed?
  2. what is the data format of them?
  3. do they get updated at every frame?

Thank you 

Best regards,

Arvind

  • Hi

    This is not the mmWave SDK demo. This is the MRR demo. Please read the MRR demo user guide for specific data format.

    Thank you

    Cesar

  • Yeah right! Thanks for pointing out.

    For the SDK demo project, I can provide the configuration file using a Python code and read the UART outputs into a .dat file. I also want to get the clustering output and going through the codes of both SDK demo and MRR, it looks like incorporating the code for tracking into the demo project would be complex and time-consuming. 

    I could also build the MRR project and flash the MSS and DSS binary files to the 1843 module after loading ccsdebug binary file to it. Now, could you please answer the following queries:

    1. Is it possible to program the configuration of MRR using a config file using Python? 
    2. If programmable, the config file for the MRR would be somewhat different from that for SDK demo. Could you please suggest changes, or share resources (like documentation) that mention the description of the config file for MRR project?
    3. Is there's a better alternative to export the clustering/tracking data to a file using a script?

    Thanks.

    Best regards,
    Arvind 

  • Hi Cesar,

    Thanks for your clarification earlier. Could you please answer the queries I posted above?

  • Answer #1 - Currently the config is hard coded in the code. (see) so, it is not possible to program the configuration through uart (python or other)

    Answer #2: see 

    Answer #3 clustering/tracking data is sent by the demo through uart. You can save it on a host through python or other sw running on host PC