• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 949 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.

AWR1843: Rx Saturation Data

Sebastian Brueckner
Intellectual 395 points
Part Number: AWR1843

Hi,

I would like to test if the radar receiver chain ever gets over-driven/saturated for large close-in targets.

The mmWave SDK 3.5 mmw demo offers "CQRxSatMonitor" and "analogMonitor" CLI commands for this purpose. 

I was not able to find documentation or example code that showcases how to use the results from these monitors. Could you point me to a document, if available, that explains how to use the saturation monitor and how to evaluate its output data?

Thanks.

  • 0
    TI__Genius 17265 points

    Hi,

    Have you looked at the documentation for these commands in the SDK user's guide? They can be found in the section titled "Configuration (.cfg) File Format"
    The sections for these params also refer to some other relevant docs which go into further detail. Let me know if there are further questions here.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Intellectual 395 points

    Alec,

    the SDK User Guide points to the Doxygen documentation for the configuration format (rlRxSatMonConf_t, file:///C:/ti/mmwave_sdk_03_05_00_04/packages/ti/control/mmwavelink/docs/doxygen/html/structrl_rx_sat_mon_conf__t.html). That, in turn, mentions something about a CQ buffer. I could not find any mention of a async message delivering monitor results like for most other monitors.

    So I guess that the RxSat Monitor is different from other monitors: It does not produce an async event in case of saturation, but I somehow have to get that CQ data and parse it myself. Is that a correct statement?

    Do you have a code sample that shows this process? The mmw demo seems to only implement the commands to set these monitors up. I could not find any code that would analyze or even collect the results - hence my original question. I am probably not looking in the right spot.

    Ultimately, I want to know if the receiver chain was saturated at any point in the previous radar frame.

    Thanks for your help

    Sebastian

  • 0 in reply to Sebastian Brueckner
    TI__Mastermind 40685 points

    HI, Sebastian:

    I need to consult with the software expert and will get back to you soon.

    Best,

    Zigang

  • 0 in reply to Sebastian Brueckner
    TI__Genius 17265 points

    Sebastian,

    I referred to the Out Of Box Demo (version for 68xx with the DSP) and could see relevant discussion in the header comment of the mss_main.c as well as in mmw_lvds_stream.c. I believe you can only capture this data when you are using LVDS streaming (raw ADC data) which is why you do not see it used in the demos by default.

    Let me know if there are further questions.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Intellectual 395 points

    In case anyone comes upon this thread:

    I looked through the mmw demo documentation in the source files mentioned by Alec. There is no information in there about the structure or meaning of the CQ data. As he explained, the mmw demo only address the setup of the monitor, not the analysis of the results.

    The best source of information on the CQ data organization seems to be the mmWave Radar Interface Control Document from the mmWave DFP (https://www.ti.com/tool/MMWAVE-DFP). That has some info on the structure of the data in Chapter 10.2 "Chirp Quality data".

    Best regards

    Sebastian