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: DCA1000 binary file size

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

hello!

set the AWR6843AOP radar parameters as shown in figure 1

figue 1

samplesperchirp=256, numof-frames=50, framesperchirp=96

and we get the theoretical binary file size will be 19200KB

and we did get a 19200KB binary file the first time

but when we tried to trigger the radar again,we got tens of 1GB binary file in PC ,as shown in figure 2

the binary file size is completely beyond my apprehension

figure 2

I do need your help to deal with the problem

thanks 

  • Hi,

    I will check and get back to you in a day or two.

    Regards,

    Samhitha

  • HI,

    Samhitha

    Sorry to rush you,

    but the problem needs to be addressed urgently

    Sincere thanks for your help

    Regards

  • Hi,

    I have reassigned this thread to Sivaprasad. He will help you to resolve the issue.

    Regards,

    Samhitha

  • Hi,
    Usually 1GB of data capture files we get when the number of frames is to zero. This way the data will be captured for an infinite time on your PC or until you explicitly press the "Stop Frames" button. The DCA1000 will capture the raw data in a new file after every 1GB of data capture. Are you sure you are not settings number of frames to zero? I have few more queries

    1) Are you manually setting API's in mmwave studio or are you using Lua script? If you are using a Lua script please do share.
    2) Please try 2nd capture without re-naming ".bin" file?
    3) Please clear Lua output logs, freshly repeat the procedure and share the log file.

    Regards,
    Sivaprasad

  • Hi,

    I have checked my parameters and I am sure that I'm not setting numbers of frames to zero,as shown in figure1

    about your queries

    1) I am manually setting parameters in mmwave studio and I have never used Lua  scripts

    figure 1

    2) I followed your advice,try 2nd capture without re-naming.'bin' file;But the issue still occurs

    I got tens of 1GB capture binary file,as shown in figure2

    figure  2

    3)the log file is shared in .txt

    1780.adc_data_LogFile.txt
    25-Apr-2024 20:33:34: IsFPGA:,0,0,
    25-Apr-2024 20:33:34: C:\ti-mmwavestudio\mmwave_studio_02_01_01_00\mmWaveStudio\RunTime,0,
    25-Apr-2024 20:33:37: API:select_capture_device,DCA1000,0,
    25-Apr-2024 20:34:15: API:select_chip_version,IWR6843,0,
    25-Apr-2024 20:37:32: API:ChannelConfig,7,15,0,
    25-Apr-2024 20:37:32: API:AdcOutConfig,2,1,0,
    25-Apr-2024 20:37:33: API:DataFmtConfig,15,2,1,0,1,0,
    25-Apr-2024 20:37:33: API:LowPowerConfig,0,0,0,
    25-Apr-2024 20:37:37: API:DataPathConfig,1,1,0,2,0,
    25-Apr-2024 20:37:38: API:LvdsClkConfig,1,1,0,
    25-Apr-2024 20:37:38: TSW1400 Sampling rate : 600000000 7500000,0,
    25-Apr-2024 20:37:38: API:SetHsiClock,9,0,
    25-Apr-2024 20:37:39: API:LaneConfig,3,0,
    25-Apr-2024 20:37:39: API:LvdsLaneConfig,0,1,0,
    25-Apr-2024 20:37:53: API:ProfileConfig,0,1491308089,700,466,5690,0,0,1823,0,256,5000,0,0,30,0,
    25-Apr-2024 20:37:54: API:ProfileConfig,0,1491308089,700,466,5690,0,0,1823,0,256,5000,0,0,30,0,
    25-Apr-2024 20:38:04: API:ChirpConfig,0,0,0,0,0,0,0,1,0,
    25-Apr-2024 20:38:04: API:ChirpConfig,1,1,0,0,0,0,0,2,0,
    25-Apr-2024 20:38:04: API:ChirpConfig,2,2,0,0,0,0,0,4,0,
    25-Apr-2024 20:38:06: API:ChirpConfig,2,2,0,0,0,0,0,4,0,
    25-Apr-2024 20:38:18: API:EnableTestSource,0,1,0,
    25-Apr-2024 20:38:18: API:FrameConfig,0,0,50,32,10000000,0,512,0,
    25-Apr-2024 20:38:18: API:AdvancedFrameConfig,1,0,0,0,1,32,10000000,0,1,1,10000000,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,50,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
    25-Apr-2024 20:38:21: API:EnableTestSource,0,1,0,
    25-Apr-2024 20:38:21: API:FrameConfig,0,2,50,32,10000000,0,512,0,
    25-Apr-2024 20:38:21: API:AdvancedFrameConfig,1,0,0,0,3,32,10000000,0,1,1,10000000,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,50,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
    25-Apr-2024 20:38:23: API:select_capture_device,DCA1000,0,
    25-Apr-2024 20:38:42: API:SensorStart,0,
    25-Apr-2024 20:38:59: API:EnableTestSource,0,1,0,
    25-Apr-2024 20:38:59: API:FrameConfig,0,2,400,32,10000000,0,512,0,
    25-Apr-2024 20:38:59: API:AdvancedFrameConfig,1,0,0,0,3,32,10000000,0,1,1,10000000,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,400,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
    25-Apr-2024 20:39:04: API:SensorStart,0,
    

    and this time I got mmwave studio output error as shown in figure 3

    timeout error!

    System disconnected

    Record stop failed

    figure 3

    Sincere thanks for your help

    Regards

  • Hi,
    I apologize for the delay in response due to holiday here.

    1) I would need output log file. Please see the image attached below.
        Perform a fresh data capture (Newly opened mmwave studio) -> Go to output->right click and open
         log folder->share the latest one.

          


    2)Please share the image of switch settings details (EVM/DCA1000/MMWAVEICBOOST if used)
    3)Please share the version of the BSS/MSS firmware which you are using (Can be found in connections tab of mmwave studio)?
    4)Please share adc_data_raw_logfile (CSV file - present in PostProc folder)

    Regards,
    Sivaprasad

  • Hi,

    thanks for help

    the issue disappeared when I turned to a new PC

    Regards,

    chen