• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 49 subscribers
  • Views 1360 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TSW1400EVM: TI Radar Studio: "ARM" and "Trigger Frame" buttons expected behavior

Thomas Teisberg
Prodigy 110 points

Part Number: TSW1400EVM

I'd like to clarify what exactly the "TSW1400 ARM" and "Trigger Frame" buttons do.

In the training video (2.7 mmWave Sensor Raw Data Capture Using the TSW1400 Board), the procedure shown is as follows:

1. Press "TSW1400 ARM".
2. Wait until HSDCPro says "Waiting for user input..."
3. Press Trigger Frame (presumably this is when the actual data is captured).

This procedure does not seem to work for me. I get the same 0 byte .bin file issue described previously on this forum. The suggested solution is to press "Trigger Frame" immediately rather than waiting for HSDCPro to finish and display "Waiting for user input..." This approach does appear to work, but it creates some confusion about what is actually happening and when data is being acquired.

First I tried doing an acquisition following the advice on the forum and immediately pressing "Trigger Frame":

// Press Setup TSW1400
[12:46:02]  [RadarAPI]: TSW1400 set-up complete.
// Press ARM TSW1400
[12:46:09]  [RadarAPI]: ar1.StartTsw1400Arm("C:\\ti\\mmwave_dfp_00_07_00_04\\rf_eval\\radarstudio\\PostProc\\adc_data_samplingtest_6us_256samp_10000ksps.bin")
// Press Trigger Frame while "Check D3 bit" still shows up in HSDCPro - Status: "CONNECTED"
[12:46:15]  [RadarAPI]: ar1.StartFrame()
[12:46:15]  [RadarAPI]: Status: Passed
[12:46:15]  [RadarAPI]: Frame trigger async event received!
[12:46:15]  [RadarAPI]: Frame Ended
[12:46:17]  [RadarAPI]: TSW1400 capture complete

This seems to work just fine (except that it doesn't follow the directions in the video training or the Radar Studio guide).

If I wait until HSDCPro finishes and says "Waiting for user input..." before pressing Trigger Frame, though, I get an odd behavior:

// Press ARM TSW1400
[12:46:48]  [RadarAPI]: ar1.StartTsw1400Arm("C:\\ti\\mmwave_dfp_00_07_00_04\\rf_eval\\radarstudio\\PostProc\\adc_data_samplingtest_6us_256samp_10000ksps.bin")
[12:46:59]  [RadarAPI]: TSW1400 capture complete
// Press Trigger Frame after waiting - Status "TRIGGER ARM"
[12:47:06]  [RadarAPI]: ar1.StartFrame()
[12:47:06]  [RadarAPI]: Status: Passed
[12:47:06]  [RadarAPI]: Frame trigger async event received!
[12:47:06]  [RadarAPI]: Frame Ended

The "TSW1400 capture complete" message comes before I press "Trigger Frame." Does this mean that a radar capture was performed before pressing "Trigger Frame"? If so, what settings were used? Was this an actual radar sounding or just the TSW1400 capturing random bits from a radar that wasn't outputting anything?

Could anyone clarify this situation? Which of these (or both/neither) result in a radar sounding? What is actually happening in the other case?

Thanks!

  • 0
    TI__Mastermind 20541 points
    Hi Thomas,

    We are looking into your question. Someone will reply back to you as soon.

    Regards,
    Neeraj
  • 0 in reply to Neeraj Gill
    Prodigy 110 points
    Hi Neeraj,

    Thanks. Any update on this?

    I was actually intending to post this in the mmWave Sensors forum, but when I tagged it with TSW1400, the forum software automatically put it here. If you think it would be better and are able to, please feel free to move this thread back to the appropriate category.

    Thanks
  • 0 in reply to Thomas Teisberg
    TI__Mastermind 30545 points

    Hello Thomas,

    This is a known issue and something that I experience as well. I was told that the TSW1400 has an inbuilt timeout which occurs if the data is not received within that time frame.

    This is why the 'TSW1400 capture complete' message comes up before the Trigger Frame button is pressed if you wait. The TSW1400 times out, resulting in Radar Studio displaying a false capture complete message. In this case, no data is captured. You must re-arm the TSW1400 and then trigger the frame before the timeout occurs to capture any data. 

    Regards,

    Adrian

  • 0 in reply to aozer
    Prodigy 60 points
    Hi.

    After I installed the new Radar Studio (v1.9.1.0) and updated HSDC (v4.80), I experienced the same problem.

    My button sequence at Radar Studio is:

    Set Up TSW1400 -> TSW1400 Arm -> Trigger Frame.

    and here is the output window of Radar Studio. I tried it many times.

    [12:58:28] [RadarAPI]: ar1.SetupTSW1400()
    [12:58:32] [RadarAPI]: TSW1400 set-up complete.
    [12:58:37] [RadarAPI]: ar1.StartTsw1400Arm("C:\\ti\\mmwave_dfp_00_09_01_06\\rf_eval\\radarstudio\\PostProc\\adc_data.bin")
    [12:58:48] [RadarAPI]: MatlabProc Status: Error Type: No Data was collected. Please check.
    [12:58:48] [RadarAPI]: TSW1400 capture complete
    [12:58:51] [RadarAPI]: ar1.StartFrame()
    [12:58:51] [RadarAPI]: Status: Passed
    [12:58:51] [RadarAPI]: Frame trigger async event received!
    [12:58:51] [RadarAPI]: Time Unit report async event received!
    [12:58:51] [RadarAPI]: Frame start/end async event received!
    [12:58:51] [RadarAPI]: Frame Ended

    And I couldn't get captured data from HSDC "Read DDR Memory" button. It says "No trigger occured".

    Regards,

    M. Emin YANIK