DCA1000EVM: Failing, reading output file adc_data_0.bin

Aanund Storhaug

Part Number: DCA1000EVM
Other Parts Discussed in Thread: IWR6843

Hi,

We have an IWR6843 radar card we run together with the raw data capture device DCA1000EVM. We run it through mmWaveStudio version 2.1.0. To read the data after it has been through the reorder zero fill function in the post process functionality in mmWaveStudio, we use the Matlab function described in the document, Mmwave Radar Device ADC Raw Data Capture section 9.2. Adjusting the parameters according to our configuration. This works fine as long as data capturing should stop after a certain number of frames is selected in the mmWaveStudio. Resulting in a adc_data.bin file less than or equal to max size.

If the parameter No. of Frames is set to 0 (means continuously data capture), the same reading functionality fails. The data file are divided in files named adc_data_0.bin, adc_data_1.bin and so on. Size of one file shown in Windows explorer is 1 048 576 KB . The file size lacks 32 complex double values to match a complete set of chirps/frames. The fileSize = size(adcData, 1); returns the size 536870880. This does not match an integer when numChirps is defined. Setting No. of Frames to 512 file size becomes 536870912 which is 32 complex values larger than when automatic stop of file is set, the reading functions works fine. What is the problem? Is the data files cut off in the middle of a chirp so I have to append more data files and make a restructuring of the data my selves?

Regards

Aanund Storhaug

over 5 years ago

0 Kyle Cousino over 5 years ago

TI__Mastermind 24955 points

Aanund,

If you are going to set the number of frames to 0 (infinite frames), then you should switch to using the DCA1000EVM in hardware mode instead of in software mode.

Please keep in mind that when configuring the IWR6843 for either Complex1x or Complex2x mode, the size of each ADC sample is 32 bits, with 16 bits comprising the real part and 16 bits comprising the imaginary part. This aligns with the ADC providing up to 16 bits of resolution.

Based on this information, you may need to recalculate your expected file size value.

Regards,

Kyle

0 Aanund Storhaug over 5 years ago in reply to Kyle Cousino

Intellectual 260 points

Thanks for trying to help Kyle.

I am afraid I am not getting any closer a solution of my problem, though.

Do you have more details to add?

Regards,

Aanund

0 Kyle Cousino over 5 years ago in reply to Aanund Storhaug

TI__Mastermind 24955 points

Aanund,

You can consult the DCA1000 Debug Handbook and see if some of the solutions offered there help resolve your issue.

You can find this handbook here: https://e2e.ti.com/support/sensors/f/1023/t/872161

Regards,
Kyle

0 Aanund Storhaug over 5 years ago in reply to Kyle Cousino

Intellectual 260 points

Kyle,

I have solved the issue Kyle. I found that the files are consistent with an increasing offset of 32 bytes. That means you have to add the first 32 bytes from the next file to the end of the first file to complete the last chirp. For the next file it will be 64 bytes you have to add from the next file since you missed the beginning of the file by 32 bytes, and so on!

Regards

Aanund

0 Kyle Cousino over 5 years ago in reply to Aanund Storhaug

TI__Mastermind 24955 points

Aanund,

I am glad to hear that you were able to resolve this issue and identify the solution on your own!

I will consider this issue to be resolved now and close the thread.

Regards,

Kyle

Sensors

Sensors forum

DCA1000EVM: Failing, reading output file adc_data_0.bin