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.

AWR2243: Unable to capture number of frames other than 10 in cascade MIMO

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

Hi!

I have a AWR2243 with MMWCAS-DSP-EVM board and mmWave studio to collect data under the cascade MIMO mode.

mmWave studio version: 03.00.00.14

firmware version: mmwave_dfp_02_02_03_01

I am having trouble collecting data other than exactly 10 frames. I am using the provided Cascade_Configuration_MIMO.lua to configure the sensor, and Cascade_Capture.lua to capture data. It seems the sensor always stop after capturing 10 frames. I tried specifying number of frames to capture (num_frames_to_capture in Cascade_Capture.lua) to other numbers and PostProc always returned 10 frames. I also attempted infinite number of frames and manual 'stop capture' from GUI and that ended up stopping prematurely with 10 frames as well. I attached the log output in the following, it seems that [RadarAPI] returned frame ended almost immediately after starting, but I'm not sure if this is coming from the board or from the studio.

What might be the cause for this ? What is the proper way to start capture data until told to stop and are there examples or APIs that I can look up? Is the variable ar1 going to be the primary communication tool between my PC and the sensor? Thanks!

[03:56:05] LuaLoad("C:/ti/mmwave_studio_03_00_00_14/mmWaveStudio/Scripts/Cascade/Cascade_Capture.lua")
[03:56:05] Loops Remaining : 1
[03:56:05] Starting TDA ARM...
[03:56:05] [RadarAPI]: ar1.TDACaptureCard_StartRecord_mult(1, 0, 0, adc_duration_test_50, 50)
[03:56:05] Device 0 - Configuring TDA with Width : 2048 and Height : 768
[03:56:05] [RadarAPI]: Device 0 - setWidthAndHeight Status: Passed
[03:56:05] [RadarAPI]: Device 1 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:05] Device 1 - Configuring TDA with Width : 2048 and Height : 768
[03:56:05] [RadarAPI]: Device 1 - setWidthAndHeight Status: Passed
[03:56:05] [RadarAPI]: Device 2 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:05] Device 2 - Configuring TDA with Width : 2048 and Height : 768
[03:56:05] [RadarAPI]: Device 2 - setWidthAndHeight Status: Passed
[03:56:05] [RadarAPI]: Device 4 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:05] Device 3 - Configuring TDA with Width : 2048 and Height : 768
[03:56:05] [RadarAPI]: Device 3 - setWidthAndHeight Status: Passed
[03:56:05] [RadarAPI]: Device 8 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:05] Sending Frame Periodicity of 100 to TDA..
[03:56:05] [RadarAPI]: Status: Passed. Frame Periodicity sent to TDA
[03:56:05] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:06] Sending Capture Directory with name /mnt/ssd/adc_duration_test_50 to TDA..
[03:56:06] [RadarAPI]: Status: Passed. Capture Directory sent to TDA
[03:56:06] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:06] Sending File Allocation of 0 files to TDA..
[03:56:06] [RadarAPI]: Status: Passed. File Allocation sent to TDA
[03:56:06] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:06] Sending Enable Data Packaging (0 - 16-bit; 1 - 12-bit) with value of 0 to TDA..
[03:56:06] [RadarAPI]: Status: Passed. Enable Data Packaging sent to TDA
[03:56:06] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:06] Sending Number of frames to capture with value of 50 to TDA..
[03:56:06] [RadarAPI]: Status: Passed. Number of frames to capture sent to TDA
[03:56:06] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:06] [RadarAPI]: Status: Passed for notifying TDA about Creating Application
[03:56:06] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:06] [RadarAPI]: Status: Passed for notifying TDA about Start Frame
[03:56:06] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:06] TDA ARM Successful
[03:56:07] Starting Frame Trigger sequence...
[03:56:07] [RadarAPI]: ar1.StartFrame_mult(8)
[03:56:07] [RadarAPI]: Status: Passed
[03:56:07] Device 4 : Start Frame Successful
[03:56:07] [RadarAPI]: ar1.StartFrame_mult(4)
[03:56:07] [RadarAPI]: Status: Passed
[03:56:07] Device 3 : Start Frame Successful
[03:56:07] [RadarAPI]: ar1.StartFrame_mult(2)
[03:56:07] [DeviceId-3] Frame start async event received!
[03:56:07] [RadarAPI]: Status: Passed
[03:56:07] Device 2 : Start Frame Successful
[03:56:07] [RadarAPI]: ar1.StartFrame_mult(1)
[03:56:07] [DeviceId-2] Frame start async event received!
[03:56:07] [RadarAPI]: Status: Passed
[03:56:07] Device 1 : Start Frame Successful
[03:56:07] Capturing AWR device data to the TDA SSD...
[03:56:08] [DeviceId-1] Frame start async event received!
[03:56:08] [DeviceId-0] Frame start async event received!
[03:56:08] [RadarAPI]: Frame Ended
[03:56:09] [DeviceId-1] Frame End async event received!
[03:56:09] [DeviceId-0] Frame End async event received!
[03:56:09] [DeviceId-3] Frame End async event received!
[03:56:09] [DeviceId-2] Frame End async event received!
[03:56:09] Status: Passed for notifying TDA about Stop Frame
[03:56:09] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[03:56:18] Capture sequence completed...
[03:56:19] Starting Transfer files using WinSCP..

<The following logs are omitted since they are info about file copy>

  • Hello User,

    Thankyou for reaching out and we will assist you shortly. 

    What is the value of the 2 highlighted variables in the your Cascade_Configuration_MIMO.lua script? 

    This is what that determines the frame count. 

    The 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 the user (configuration corresponding to the lines 52-90 in Cascade_Configuration_MIMO.lua. 

    Hope that makes sense and gets you some direction. 

    Regards,

    Ishita

  • Hi Ishita,

    Thank you very much! This indeed resolve my issue, I really appreciate it.