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.

DCA1000EVM: mmWave Studio ADC data logging

Part Number: DCA1000EVM
Other Parts Discussed in Thread: MMWAVEICBOOST, IWR6843ISK,

Hi,

I have #DCA1000EVM and #MMWAVEICBOOST+#IWR6843ISK setup and trying to reliably start experimenting with chirp configurations to record raw ADC data and do offline Matlab processing.

While I managed to run the DataCaptureDemo_xWR.lua (and other demos in CCS), I am struggling to use provided gui to tweak chirp configurations. Specifically, the mmWave Studio gui (v2.0.0.2) seems to crash randomly when I try to modify gui configurations using the provided tabs. I have read the pdf manuals and understand that things have to be done in sequence, but still the gui crashes all the time.

I am inclined to think that I ought to follow the strict sequencing as in the DataCaptureDemo_xWR.lua file and may need to start scripting in lua. Could you please comment on this?

I also had to tweak a bit readDCA1000.m code provided in swra581b to get adc_data.bin to load in Matlab as follows:

.
.
fclose(fid);
fileSize0 = size(adcData, 1);
fileSize = floor(fileSize0/(numADCSamples*numRX))*(numADCSamples*numRX);
fprintf('Original # of entries %d, grabbing %d \n', fileSize0, fileSize);
% real data reshape, filesize = numADCSamples*numChirps
if isReal
.
.

I'm not sure if this is expected. Could you please comment on this?

Cheers,

-Manny

  • Hello,

        Could you please post the sequence of steps you have followed? 

    Also post the logs that studio provides? 

    For the sequence of steps have you reviewed the DCA1000 training video? 

    https://training.ti.com/dca1000-training-video  This is developed for the 1243/1443/1642 family of devices, however mmWave studio interface and sequence of steps should be similar for record raw ADC data and do offline Matlab processing. 

    Thanks and regards,

    CHETHAN KUMAR Y.B.

  • Hello,

    Also please note that ES1.0 silicon may not have been tested and supported with  mmWave studio 2.00.00 version.

    Below are the supported device for this version. 

    Thanks and regards,

    CHETHAN KUMAR Y.B.

  • Hello,

    Were you able to make a progress on this?

    Thanks and regards,
    CHETHAN KUMAR Y.B.
  • Hi Chethan,

    Thank you for the pointers. Have followed instructions in the video you pointed out and things are a lot more stable now, which allowed me to get my system going, which is great!

    Data capture when having large number of frames (e.g. 800) seems to be a bit temperamental. Any advice on how to get more reliable/stable setup? E.g. yesterday I managed to acquire data with no problem but today when number of frames is relatively high, I get a lot of "out of sequence" packet reception notes in log and then post process crashes.

    Grateful for an input.

    Cheers,
    -Manny
  • Hello,

         Thanks for confirming on your setup is now working.  To capture large frames you may want to review available RAM space in your PC and harddisc space.  If there is large data-set on RAM, there may not be sufficient memory for the mmWave studio post processing operation, Hence crash could happen.  

    Also when we transfer large data there could be a packet out of sequence could happen, you may try giving more time (Say 75usec) delay for the packet delay in the DCA1000 configuration section.

    Thanks and regards,

    CHETHAN KUMAR Y.B.

  • Hi,

    I'm still struggling stabilising data capture over ethernet. I experimented with various packet delays but essentially I'm seeing random behaviour in that I sometimes success and sometimes don't. I have 16G ram and just ordered another 16 in case ram has any bearing on UDP packets as per above advice.

    Would appreciate any tips on how to get reliable data acquisition going so I can begin scripting everything up and run my data collection campaign.

    Cheers,
    -Manny
  • And here is a log for when things don't work:

    [12:11:58]  CaptureCardConfig_Mode Success
    [12:11:59]  [RadarAPI]: ar1.CaptureCardConfig_PacketDelay(25)
    [12:11:59]  [RadarAPI]: Status: Passed
    [12:11:59]  [RadarAPI]: CONFIG_PACKET_DATA_CMD_CODE Async event recieved(11)
    [12:11:59]  CaptureCardConfig_PacketDelay Success
    [12:12:00]  [RadarAPI]: ar1.CaptureCardConfig_StartRecord("C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\adc_data.bin", 1)
    [12:12:00]  [RadarAPI]: Status: Passed
    [12:12:00]  [RadarAPI]: RECORD_START_CMD_CODE Async event recieved(5)
    [12:12:01]  [RadarAPI]: ar1.StartFrame()
    [12:12:01]  [RadarAPI]: Status: Passed
    [12:12:01]  Frame start async event received!
    [12:12:02]  [RadarAPI]: RECORD_PKT_OUT_OF_SEQ_ERROR_CODE Async event recieved(195)
    [12:12:02]  [RadarAPI]: RECORD_PKT_OUT_OF_SEQ_ERROR_CODE Async event recieved(195)
    [12:12:02]  Frame End async event received!
    [12:12:02]  [RadarAPI]: Frame Ended
    [12:12:02]  [RadarAPI]: RECORD_PKT_OUT_OF_SEQ_ERROR_CODE Async event recieved(195)
    [12:12:03]  Please wait for a few seconds for Packet reorder utility processing .....!!!! 
    [12:12:03]  [RadarAPI]: Packet Reorder Utility Started...please wait...
    [12:12:03]  [RadarAPI]: ar1.PacketReorderZeroFill("C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\adc_data_Raw_0.bin", "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\adc_data.bin", "C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\pktlogfile.txt")
    [12:12:04]  [RadarAPI]: STS_RECORD_COMPLETED Async event recieved(8)
    [12:12:04]  [RadarAPI]: ar1.CaptureCardConfig_StopRecord()
    [12:12:04]  [RadarAPI]: Status: Passed
    [12:12:04]  [RadarAPI]: RECORD_STOP_CMD_CODE Async event recieved(6)
    [12:12:08]  [RadarAPI]: Packet Reorder Utility process completed!
    [12:12:18]  Packet reorder utility processing done.....!!!! 
    [12:12:18]  Please wait for a few seconds for matlab post processing .....!!!! 
    [12:12:18]  [RadarAPI]: ar1.StartMatlabPostProc("C:\\ti\\mmwave_studio_02_00_00_02\\mmWaveStudio\\Scripts\\..\\PostProc\\adc_data.bin")
    [12:12:19]  [RadarAPI]: Error: 
    [12:12:19]  
    [12:12:19]  ... MWMCR::EvaluateFunction error ... 
    [12:12:19]  15-Feb-2019 12:12:19: The file C:\ti\mmwave_studio_02_00_00_02\mmWaveStudio\Scripts\..\PostProc\adc_data.bin is empty. Please capture more data.,1,
    [12:12:19]  Error in => process_adc_data.m at line 52.
    [12:12:19]  
    [12:12:19]  ... Matlab M-code Stack Trace ...
    [12:12:19]      at
    [12:12:19]  file C:\Users\sdr\AppData\Local\Temp\sdr\mcrCache8.5.1\Matlab0\Logging\log_status.m, name log_status, line 32.
    [12:12:19]      at
    [12:12:19]  file C:\Users\sdr\AppData\Local\Temp\sdr\mcrCache8.5.1\Matlab0\Processing_functions\read_adc_data.m, name read_adc_data, line 28.
    [12:12:19]      at
    [12:12:19]  file C:\Users\sdr\AppData\Local\Temp\sdr\mcrCache8.5.1\Matlab0\MatlabPostPr\process_adc_data.m, name process_adc_data, line 52.
    [12:12:19]  
    [12:12:19]  
    [12:12:19]  Trace:
    [12:12:19]     at MathWorks.MATLAB.NET.Utility.MWMCR.EvaluateFunction(String functionName, Int32 numArgsOut, Int32 numArgsIn, MWArray[] argsIn)
    [12:12:19]     at MathWorks.MATLAB.NET.Utility.MWMCR.EvaluateFunction(Int32 numArgsOut, String functionName, MWArray[] argsIn)
    [12:12:19]     at MatlabPostProcGui.MatlabPostProcGUIClass.process_adc_data(MWArray adc_file_name, MWArray force_cont_stream_mode)
    [12:12:19]     at AR1xController.frmAR1Main.iStartMtlabPostProc()
    [12:12:28]  
    [12:12:28]  ***Script completed successfully.***
    

    And a photo of the Packet_Reorder_Zerofill.exe when I try to call it manually from command line:

  • Hello,

    It appears that ADC data has been captured correctly, problem seem to be in post processing side.
    Could you please post the adc_data_Raw_0.bin, Also screen capture of the configuration that is applied and output/log files.

    Thanks and regards,
    CHETHAN KUMAR Y.B.
  • Hello,

    Were you able to make progress on the suggestion made?

    Thanks and regards,
    CHETHAN KUMAR Y.B.
  • Hello,

    Closing this thread due to inactivity, If problem is still persisting please raise a new thread with above requested information.

    Thanks and regards,
    CHETHAN KUMAR Y.B.
  • Thanks Chethan. Not 100% sure, but a combination of more ddr ram and changing ram settings in bios may have resolved the crashing zero fill utility. It's stable so far, so fingers crossed.
  • Hello Manny,

    Thank you for the confirmation. And best wishes for your experiments.

    Thanks and regards,
    CHETHAN KUMAR Y.B.