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.

MMWCAS-DSP-EVM: Calibration of the mmWave cascaded radar

Part Number: MMWCAS-DSP-EVM
Other Parts Discussed in Thread: MMWCAS-RF-EVM

Hello,

I'm trying to use the mmWave cascaded radar (MMWCAS-RF-EVM + MMWCAS-DSP-EVM) to generate some images. Here I have a question about the calibration:

I tried to calibrate the radar in the MIMO mode using the default number of frames (num_frames_to_capture = 0), after that, if I capture the data also use the default number of frames and do the post-processing in Matlab, everything is fine. However, if I set the number of frames to 1, then in Matlab it will give me an error when post-processing the captured data. Is this normal? In other words, do I need to calibrate the radar again if I want to change the number of frames?

I really appreciate any help, thank you!

-Yiran

  • Hello Yiran,

    num_frames_to_capture parameter in the cascade_capture.lua script is something that is sent to the MMWCAS-DSP-EVM board during "TDA ARM" to notify the capture card about space allocation for frame capture. It is always suggested to keep this parameter as "0". This way the card will capture the frames actually specified in the configuration by you.

    "nframes_master" and "nframes_slaves" decide the actual frame count (If you're using our example scripts, this is the variable that controls the parameter). The device captures equal number of frames for all the four devices, hence keep these two parameters equal. 

    Regards,

    Ishita

  • Hello Ishita,

    Thanks for the clarification! I tried your method and it seems to be working.

    However, it brings two more questions:

    1) When I set the "nframes_master" and "nframes_slaves" to be both equal to 1, I would expect the total size of the files transferred to the host PC to be smaller compare with the case when they are equal to 10. But after some testing, in both cases the total size is around 120 MB. Is this normal?

    2) When doing post-processing in MATLAB (using the code "cascade_MIMO_signalProcessing.m"), no matter if the number of frames is 1 or 10, it always shows "frameCountGlobal = 1" all the way to "frameCountGlobal = 8" in the command window. What does this mean?

    Thank you!

  • Hello Yiran,

    Sorry for the delay here. I was on leave for the later part of the last week and hence couldn't reply.

    Regarding your observations, this is not expected. The file size depends on the number of frames you've configured for the capture. Can you maybe reset the board, change the file name and try experimenting a little more by capturing different number of frames.

    Regards,

    Ishita

  • Hello Ishita,

    When I set the number of frames to a much larger value (e.g. 100), the folder size is significantly larger. So I guess the difference between 1 and 10 frames is not big enough for Windows to tell.

    However, the other question remains:

    When the number of frames is set to 1 or 10, when I run cascade_MIMO_signalProcessing.m in Matlab, it consecutively shows from "frameCountGlobal = 1" to "frameCountGlobal = 8". But when the number of frames is set to be 100, Matlab gives an error after showing "frameCountGlobal = 8". This is confusing. Any advice on that?

    Thank you!

  • Hello Yiran,

    I would need some time to study this and try out a configuration with more than 8 frames to get similar results. 

    If its okay, I can get back to you by early next week on this.

    Regards,

    Ishita

  • Hello Yiran,

    Sorry for the delay here. I did check this with the team internally. 

    We have tested this script for minimum of 1000 frames and it seems to work fine, so I don’t see why the code would give the error after 8 frames. Can you double check if the test folder is set properly in “\ti\mmwave_studio_03_00_00_14\mmWaveStudio\MatlabExamples\4chip_cascade_MIMO_example\main\cascade\input\testList.txt”.

    Below are the contents of the testList.txt file :

    C:\ti\mmwave_studio_02_01_00_00\mmWaveStudio\PostProc\MIMO_Capture\

    .\input\calibrateResults_dummy.mat

    .\paramGen\module_param.m

     

    - The first line should point to the folder for the .bin adc data file

    - The second line should be the calibration mat file

    - The third line should be the corresponding .m chirp configuration file.

     

    The first and the third should match in terms of configuration.

    Regards,

    Ishita