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.

AWR1642: Chirp Parameters (CP) and Chirp Quality (CQ) data Monitoring

Part Number: AWR1642

Hi community,

Using the DCA1000 for raw data capture I want to use Chirp Profile (CP) Chirp Quality (CQ) report.

My current capture process is with the mmWave demo and CLI commands setting the required parameters:

analogMonitor 1 1 - to enable CQRxSatMonitor and CQSigImgMonitor

lvdsStreamCfg -1 1 4 0 - for CP_ADC_CQ

adcCfg 2 2 - complex 2x (image band visible))

CQRxSatMonitor 0 3 5 123 0 - using 5 Msps and <priSliceDuration> = 0.8us * (123+1)/2 = 49.6us whereas 51.2us @ 256 is total sampling time

CQSigImgMonitor 0 127 4 - means #pri = 64, #sec = 63 -> 256 samples

However my raw data is not showing expected results.

For example SigImg Data are always 0xF but since there should only be noise in the image band values should vary.

Also when changing <numSlices> the N found in byte 0 stays 123.

For the format I am referring to the AWR1xxx Radar Interface Control Document Interface Control Document (ICD) 

Chapter 8. Chirp Parameters (CP) and Chirp Quality (CQ) data


Exemplary data is attached (must be changed to .bin)

It appears that CP data for 3 frames is 16bytes*16 starting with DC 0A DC 0A DA

This appears 2 times per frame since complex data is enabled.

At each frame end SigImgMonitor data is 0xFF seperated by 0x7B which is 123 dec

Next comes RXSatMonitor with all 0x00 seperated by 0x7B

Then the next CP data and frame data followed

 

Anybody with experiences, ideas, suggestions?

Or is there a mmWave studio lua script to test CP CQ Data?

Regards,

 Robert

CQ4_satsigimg_3frames - Copy.txt

  • Hello Robert,
    For CP CQ related feature you can get reference from mmwavelink test application which is available in mmWave SDK installation.
    (C:\ti\mmwave_sdk_02_00_00_04\packages\ti\control\mmwavelink\test) this test application checks for CQ and CP data.

    And further you can use mmWave Studio to capture LVDS data for ADC + CP+CQ with DCA1000/TSW1400 board and with PostProc it will post process the recieved data.

    For data format please go through documents avaialble at these links
    www.ti.com/.../swra581.pdf
    www.ti.com/.../swra555.pdf


    Regards,
    Jitendra
  • Hi Jitendra,

    How can the CP+CQ be enabled? I found ar1.SaveCQData(String FileName, UInt32 CQDataType)
    In combination with:
       cq_data_path = data_path.."\\cq_data.bin"
       ar1.SaveCQData(cq_data_path, 2)
    There is an error:
       Please provide a file name. The file name provide : seems to be a directory. ,1,
       Error in => save_cq_data.m at line 10.
    Do futher settings have to be made?
    Is there an exemplary lua script to be used?

    Looking at the output file I'm also wondering about the Chirp Parameters Data.

    There are 4*16bytes for each frame but the values stay the same - independent from config.


    Regards

  • Hi Robert,

    I'm looking into this. I will need some time and will get back to you by Friday.

    Best Regards,
    Anand
  • Hi Anand,

    What seemed to be the issue with my config was that 2x complex in adcCfg was enabled.
    This has prevented proper CQ output.
    Signal Image Monitor seems to be working fine. For RxSaturation I have not verified yet.
    I will review my results.

    More information on the issue would be welcome.
    Thank you
  • Hi Robert,

    I'm not sure why having 2x complex in ADCCFG would prevent proper CQ output.

    Anyway, it appears that you are unblocked. So I will close this thread.

    If you require more support, please raise another thread.

    Best Regards,
    Anand