• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 275 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.

DCA1000EVM: Same configuration but inconsistent .bin file sizes when data is captured using RtttNetClientAPI.dll and MATLAB

Muhammad Muaaz
Prodigy 20 points
Part Number: DCA1000EVM

Hi, 

I use DCA1000 EVM to collect raw data from IWR 1443Boost. Set up works fine and I am able to capture RAW ADC data using mmWave Studio. Thereafter, I send commands using the RtttNetClientAPI.dll and MATLAB, which also works fine.  I am able to capture the raw data files by sending the commands this way. 

However, I noticed that the size of the .bin file that is produced by sending the commands through MATLAB is not consistent for different runs (Note all configuration parameters are kept the same). Whereas, (with the same configuration) the mmWave studio produces the same size files for different runs. 


I will be really thankful if you can explain why this inconsistency is happening. 

  • 0
    TI__Mastermind 22637 points

    Hello,

    So you are saying that the there are variations in binary size when you do the MATLAB methodology of capturing data? We only support mmWaveStudio and StudioCLI software packages for raw data capture. Any other software capture methodology would be generally out of scope, but have you ran processing on this .bin? You could record an environment using mmWaveStudio, change nothing then capture with MATLAB, then compare and see what looks different.

    Best Regards,

    Pedrhom Nafisi

  • 0 in reply to Pedrhom Nafisi
    Prodigy 20 points

    Yes, I have manually calculated the number of chirps and frames from the collected raw data using mmWAVE studio and MATLAB. In mmWAVE studio each run produces a file of 51,200KB  (for this frame config "ar1.FrameConfig(0,0,200,64,40,0,0,1)". However, when records are done through MATLAB the file sizes are different 51,200KB,  50,944KB, 51,025KB, etc.  

    Moreover, I have also manually calculated the number of frames 51,200KB size file is the correct one as it gives the exact number of frames as they were sent. Whereas others don't. 

    I have done both ways configuring using mmWave and configuring using MATLAB. The output file of mmWave studio is always correct in size and number of samples whereas the MATLAB one is different in different runs. Although this difference is not big as mentioned above but good enough to break post-processing scripts.

    Technically the underlying commands are the same irrespective of mmWave or RtttNetClientAPI.dll.   

  • 0 in reply to Muhammad Muaaz
    TI__Mastermind 22637 points

    Hello,

    I am not sure what your MATLAB recording process is doing, without having details it is hard for me to debug anything due to not being able to have a delta between the two softwares,

    Best Regards,

    Pedrhom