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: 2243: How to achieve rough synchronization

Part Number: MMWCAS-DSP-EVM


Hi,

I have trouble in acquire the start time of data capturing using mmstudio.

We have tried to get the start time by adding "socket.gettime() " in "Cascade_Capture.lua". 

But we don't know which sentence means the chip starts getting data.

Does anyone know where can we get the start time of data capturing?

We are looking forword to your answer.

Thanks!

Chenyu

  • Hello Chenyu,

    In mmWave Studio, when you press the TDA ARM button, it prepares the capture card for incoming data capture. Data capture starts as soon as you start transmitting the frames by pressing the "start frames" button in mmWave studio. The capture duration depends on your configured chirp and frame time and the number of frames.

    Hope this makes sense. Let us know if you have further questions/concerns. 

    Regards,

    Ishita

  • Hello Ishita,

    Thank you for your answer. Following your instruction, i using the lua shell to generate the starting time according to the frame trigger step. Below is what I get in mmwave studio output. And since using the cascade radar, i get the frame triggering time of four chips and i think the yellow might be the right one, is that correct?  

    TDA ARM Successful
    [15:26:52] Starting Frame Trigger sequence...
    [15:26:52] Start Time : 1633937212.9027
    [15:26:52] [RadarAPI]: ar1.StartFrame_mult(8)
    [15:26:52] [RadarAPI]: Status: Passed
    [15:26:52] temp Time : 1633937212.9957
    [15:26:52] Device 4 : Start Frame Successful
    [15:26:53] [RadarAPI]: ar1.StartFrame_mult(4)
    [15:26:53] [DeviceId-3] Frame start async event received!
    [15:26:53] [RadarAPI]: Status: Passed
    [15:26:53] temp Time : 1633937213.115
    [15:26:53] Device 3 : Start Frame Successful
    [15:26:53] [RadarAPI]: ar1.StartFrame_mult(2)
    [15:26:53] [DeviceId-2] Frame start async event received!
    [15:26:53] [RadarAPI]: Status: Passed
    [15:26:53] temp Time : 1633937213.2144
    [15:26:53] Device 2 : Start Frame Successful
    [15:26:53] [RadarAPI]: ar1.StartFrame_mult(1)
    [15:26:53] [DeviceId-1] Frame start async event received!
    [15:26:53] [RadarAPI]: Status: Passed
    [15:26:53] temp Time : 1633937213.3484
    [15:26:53] Device 1 : Start Frame Successful
    [15:26:53] Mid Time : 1633937213.3604
    [15:26:53] Capturing AWR device data to the TDA SSD...
    [15:26:53] [DeviceId-0] Frame start async event received!
    [15:26:54] [DeviceId-0] Frame End async event received!
    [15:26:54] [RadarAPI]: Frame Ended
    [15:26:54] [DeviceId-3] Frame End async event received!
    [15:26:54] [DeviceId-1] Frame End async event received!
    [15:26:54] [DeviceId-2] Frame End async event received!
    [15:26:54] Status: Passed for notifying TDA about Stop Frame
    [15:26:54] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
    [15:26:58] Stop Time : 1633937218.3916
    [15:26:58] Capture sequence completed...

    I am looking for your reply.

    Regards,

    Chenyu

  • Hello Chenyu, 

    Yes, you're right. 

    All devices will only start framing after the main or the primary device i.e. device 1 is triggered. 

    Regards,

    Ishita

  • Hi Ishita,

    This is useful. Thans for your help!

    Regards,

    Chenyu