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

MMWAVE-STUDIO: CQ data and DFE energy monitor in mmWave studio

kose3
Prodigy 100 points
Part Number: MMWAVE-STUDIO

Hi team,

I'm using mmWave studio 2.1.0.0 in order to check CQ(Chirp quority) data, especially DFE Energy monitor.

The DFE Energy monitor have been got as shown in below.
However, the monitor always shows the same graph, even if I change chirp parameters and environmental factors, such as targets and surrounded absorbers.





CQ data represents energy of real and image band signal, so I'm guessing the CQ data or the DFE energy change every time pushing postproc.

My questions are,

1) Isn't it possible to check the CQ data with this application?
2) Is it possible to confirm the CQ data by parsing an adc_data.bin?
3) Do I need to do additional setting to check the CQ data?

Regards,

Kose

  • 0
    TI__Guru 69960 points

    Hi Kose,

    Make sure that you call Rx_saturation_Detector_mon_config and Rx_signal_and_image_mon_config (under AnalogRxMon Tab of Studio GUI). 

    Along with this CalMonTimeUnitConfig needs to call to set the FTTI in terms of no. of frame at which interval CQ data will get refreshed.

    Based on your snapshot looks like it is junk data which is streaming over LVDS as form of CQ data.

    Follow the attached snapshot for the steps in the mmWave Studio.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 100 points

    Hi Jitendra,

    Thank you for your reply.

    I tried setting AnalogRxMon, AnalogTxMon, CalibConfig and DataConfig as shown in previous reply.
    As a result, the DFE Energy monitor changed.

    I however came up with several questions through the setting.
    So, let me ask additional questions about the setting and CQ data.

    1) I set above configs in order of AnalogRxMon, AnalogTxMon, CalibConfig and DataConfig by following your reply.
        But, in DataConfig tab, Data path couldn't be choosen CSI2, as shown in below.
        In addition, CQ Cfg, CQ(0~2)TransSize didn't activate here.
        How can I change these parameters?



    2) Profile Index can be set in Rx Saturation Detector Mon Config and Rx Signal and Image Mon Config.
        What will be change depending on the Profile Index?

    3) Third question is regard to CQ ping pong buffer. Bottom figure shows time slices, which is introduced by TI's website.

        Could you teach me a relationship between start time of primary time slice and start time of secondary time slice?
        If I understand correctly, the relationship can be illustraled as shown in below. Is this correct?



    Regards,

    Kose

  • 0 in reply to kose3
    TI__Guru 69960 points

    Hello Kose,

    1. You need to select LVDS interface option in the above mentioned Studio Snapshot for CQ data stream (CP_ADC_CQ) as you might be capturing the data with DCA1000. So you don't need to switch for CSI-2 selection in this case. And could you confirm the Studio version

    2. Profile ID is the one which should be used by current chirp of running frame. This should be same profileIdx which is configured already and used by the current chirps. if you are using different chirp set connected with different profiles then you can call this monitoring APIs multiple times with different profileIdx. So during all the chirps in a frame this monitoring will happened with matching profileIdx.

    3. Start time of primary slice will be at ADC-startTime of chirp and secondary slice time will half time onward compare to primary slice. Based on your given snapshot-

    1usec: P1, 1.5usec: S1, 2usec: P2, 2.5usec: S2 ...

    Regards,

    Jitendra