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.

AWR1243BOOST: No ADC Data Captured with MMWAVE-DEVPACL + HSDC Pro

Part Number: AWR1243BOOST
Other Parts Discussed in Thread: MMWAVE-DFP, AWR1243

Hi,

We have the 3 board (AWR1243BOOST + MMWAVEDEPACK + TSW1400) combo all connected together, and goal is to collect adc data with the hsdc pro tool and also try out post-processing in radar studio.

The AWR1243BOOST + MMDEVPACK was configured with Radar Studio. The TSW1400 was connected and the firmware loaded with HSDC Pro. All the software has been downloaded from the mmwave-dfp.

All the firmware and ADC files were also copied as outlined in the Radar Studio User Guide. 

The AWR1243BOOST+DEVPACK was configured and everything connects without any errors including dataconfig and laneconfig.

The default chirp configuration is used. 128 chirps in loop + 40 ms periodicity + 256 samples per chirp + 10 frames. Sampling frequency is default 10 MHz. 

First profile is set, then Chirp and then Frame.

Then I click SetUp TSW1400, and then click on TSW1400ARM. then I trigger the frame (I can observe the current increase during the duration of frames to indicate that the set up is chirping).

After Trigger Frame is done, I get the message in output shell that No data was collected.

Meanwhile, the HSDC Pro still shows that the Trigger is armed. Seems like it did not get the trigger (please refer to second below).

The adc_data.bin file is created but it is 0 KB in size. All the LEDs on TSW1400 are ON except USER_LED4, which is expected. 

I tried different variation of periodicity and number of frames, but have not been able to collect any data. 

The same issue also persists in CW or ContStream mode. 

  

Thank you so much for your help and support, 

RJ

  • RJ,

    Did you wait for 1 second after you click TSW1400 ARM button, then click Trigger Frame? Below info can be found in radar studio user guide.

    6. ARM TSW1400. Wait one second.

    Or after you click the TSW1400 ARM button, pls check the status of HSDC Pro (at left bottom ) and see the status changes to "Check D3 bit", then click Trigger Frame.

  • Hi Chris, 

    Thank you for your reply. 

    I have waited for more than one second after I click the TSW1400 ARM button. 

    After your message, I also went and repeated multiple times to make sure that I press Trigger Frame after seeing the "Check D3 bit" message on left bottom of HSDC Pro. The results have not changed since before.

    There seems to be an intermittent issue where I can capture data may be 1 out of 30 attempts. I have not been able to figure out if there is a pattern to it. I am assuming this is not how it is supposed to work, and may be I am missing something.

    When it works, after pressing Trigger Frame, the LEDs on the TSW1400 blink and I can captured data. The other times, the lights dont blink at all. The output window shows that the async event has been received, but the LEDs on TSW1400 do not blink and the adc_data file size is also 0B. 

    We would need more assistance to resolve this issue. I also swapped TSW1400, and the other board also shows the same issue. 

    I appreciate your help and support, 

    RJ

  • Hello RJ,

    Can you try pressing 'Trigger Frame' immediately after pressing 'TSW1400 ARM'? Do not wait between these two. I know the guide says to wait but we have found that it works best when you press one immediately after the other.
  • Hi Aozer/Chris,

    Thank you for your suggestion. I have found a sequence which works under the chirp mode at least. The steps are as follows:

    1. Set up the TSW1400 before configuring the AWR1243BOOST + DEVPACK. This includes loading TSW1400 firmware.

    2. Once the TSW1400 is set up, then go through the AWR1243 set up in radar studio the way it has been prescribed.

    3. I have been able to log data using this sequence.

    4. If any settings change in Chirp, Profile and/or Frame Config, the AWR1243BOOST needs to be reset again for the new changes to take
    place. Then I have been able to collect data. If I change params, and then go do a TSW1400 setup, TSW1400 ARM and Trigger Frame, the set up does not work and no ADC data gets collected.

    I am not sure if this is how things are supposed to work. If this is how the set up is then it would nice to update the manual.

    I still have issues getting data in ContStream mode.

    Regards,

    RJ
  • Hi RJ,

    Glad to know that you have been able to capture data via your setup. Wonder if you had a chance to try the steps mentioned by Adrian and if your working setup already incorporated those.

    Regarding chirp vs continuous mode:
    After configuration of mode is done the trigger mechanism should be identical for both modes.
    Would you please list out which steps were different between the two modes.

    Thank you for your patience!

    Vaibhav
  • Hi Vaibhav,

    Thank you for your reply. As you suggested that after configuration, the trigger mechanism should be the same - I was able to also get adc data in continuous mode as well. One question that came out of the acquisition is as follows:

    When I choose multiple averages in ContStream for example 15 averages, the output data collected in the HSDC Pro seems to be showing data from only a single capture and not an averaged output. I understand that if I use the DataProcessing Matlab Tool, I get the data for all the individual 15 runs, but not an averaged output. Is it possible to show the averaged data in HSDC Pro ?

    Thank you,

    RJ
  • Hi RJ,

    HSDCPro is simply an interface to the capture card (TSW1400). We don't use it to analyze radar signals.Assuming that you used RadarStudio, to configure the number of samples and the number of averages (shown below), 'RadarStudio' itself has the capability to average across chirps. In the GUI please go to 'miscellaneous options', and then select in the tab 'FFT Processing settings', 'non-coherent integration across chirps'. This would instruct the postproc tool to average across chirps.

    Regarding your question, on inconsistent capture when transmitting Frames, note that the 'maximum time period' available for capture from the moment you press 'Arm TSW1400'  is about 10 seconds. Taking into account the latencies in the system (and giving a generous 1 second for the user to press 'Trigger Frame'), it would be difficult to capture more than 8 seconds consistently, so make sure that the transmission (when using Frames) is complete in about 8 seconds.

    Regards,

    Anil

  • Thank you all of you for your help and inputs. I will try the averaging from the post proc tool. 

    Regards,

    RJ