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-RF-EVM: Losing a lot of frames with cascaded radar

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

Hello,

I have exactly the same issue with MMWCAS-RF-EVM and MMWCAS-DSP-EVM as described in this question: 

https://e2e.ti.com/support/sensors/f/sensors-forum/934840/mmwcas-rf-evm-cascaded-radar-raw-data-capture-the-frames-are-lost-largely

Unfortunaly the thread has been locked. Due to this i want to ask if there is any solution?

In my case the NUM_FRAMES parameter is set to 300 and the INTER_FRAME_INTERVAL is set to 11. The num_frames_to_capture parameter is set to 0, because I want all of the 300/299 Frames.

However I only get around 250 to 290 frames.

Thanks very much for your help.

Best regards,

Julian

  • Hi,

    Please give us a few days to check with the team

    thank you

    Cesar

  • Hello Julian,

    A couple of questions here:

    1. Can you confirm the mmWave Studio version, DFP version and the AWR device you are running this with?

    2. Have you tried this experiment with the example scripts provided as a part of our mmWave studio package? (since I assume you have your own chirp configuration)

    3. What is the throughput required for your configuration? Make sure the CSI-2 data-rate per lane is < 600 Mbps.

    4. Maybe you could also send us your scripts/configuration for us to see if the issue can be reproduced at our end.

    Regards,

    Ishita

  • Hello Ishita,

    thank you for your help!

    1. mmWave Studio version: 03.00.00.14
        DFP version: 02.02.02.01
        AWR device: AWR2243 ES1.1

    2. Yes, I have experimented with the example scripts. Our script is a modification of the script "Cascade_Configuration_MIMO" and "Cascade_Capture". We have adjusted some parameters. You can find our scripts in the attachment. Please try it out. Sometimes you will get all 300 frames, but sometimes you will just get around 280 frames.

    3. Sorry, I don't know what throughput is required for our configuration. Maybe you can find it out with our configuration in the scripts.

    Best Regards,
    Julian

    Frames lost script.zip

  • Hello Julian,

    Thankyou for attaching the scripts.

    Currently, I'm not sure of why this happens, but maybe you can try with the default configuration as well, since we have tried capturing 1000 or more frames a number of times with that configuration and we have never faced this issue before. 

    With this experiment, I'm basically trying to narrow down if this is something related with the configuration or in general with the capture card.

    Regards,

    Ishita

  • Hi Ishita,

    thank you, let me know if you find out anything.

    We can't use the exact default configuration, because we have to use a maximum INTER_FRAME_INTERVALL of 11.7017ms.
    Should this be possible or is it too short?

    Regards,
    Julian