• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 32 subscribers
  • Views 386 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: AWR6843 + MMWAVEICBOOST + DCA1000EVM: Postprocessing results

navid Amani
Prodigy 60 points
Part Number: DCA1000EVM
Other Parts Discussed in Thread: IWR6843

Hi TI team,

I’ve been running some measurements using the setup described in the title along with mmWave Studio. I was able to get the bin files out, and for the measurement scenario mmWave Studio generated multiple bin files (3 in total). I understand this is because the measurement data size exceeds the bin file size cap.

When I try to look at the post processing results from the bin files using mmWave Studio, the output looks different between the 3 bin files from the same scenario. Attached are some screenshots comparing the output between the first 2 bin files.


From what I could see, the first bin file looks as expected, but the second appears with a remarkable difference (compare 1D-FFT range plots). This happens for any measurement scenario that generates multiple bin files. Please let me know why these two bin files with the same log file show differences in the processed results.

MmWave Studio also seems to think there are less frames than there actually are. There should be 874, but only 520 are shown.
Could there be a problem with how the log file was saved? I copy the content of the log file below:

15-Jul-2023 10:39:35: IsFPGA:,0,0,
15-Jul-2023 10:39:35: G:\ti\mmwave_studio_02_01_01_00\mmWaveStudio\RunTime,0,
15-Jul-2023 10:39:37: API:select_capture_device,DCA1000,0,
15-Jul-2023 10:40:02: API:select_chip_version,IWR6843,0,
15-Jul-2023 10:41:53: API:ChannelConfig,7,15,0,
15-Jul-2023 10:41:53: API:AdcOutConfig,2,1,0,
15-Jul-2023 10:41:53: API:DataFmtConfig,15,2,1,0,1,0,
15-Jul-2023 10:41:57: API:LowPowerConfig,0,0,0,
15-Jul-2023 10:42:20: API:DataPathConfig,1,1,0,2,0,
15-Jul-2023 10:42:23: API:LvdsClkConfig,1,1,0,
15-Jul-2023 10:42:23: TSW1400 Sampling rate : 600000000 7500000,0,
15-Jul-2023 10:42:23: API:SetHsiClock,9,0,
15-Jul-2023 10:42:25: API:LaneConfig,3,0,
15-Jul-2023 10:42:25: API:LvdsLaneConfig,0,1,0,
15-Jul-2023 10:43:57: API:ProfileConfig,0,1491308089,700,520,5565,0,0,1897,0,600,12000,0,0,30,0,
15-Jul-2023 10:45:25: API:ProfileConfig,0,1491308089,700,520,5565,0,0,1897,0,600,12000,0,0,30,0,
15-Jul-2023 10:45:59: API:ProfileConfig,1,1491308089,700,520,5565,0,0,553,0,600,12000,0,0,30,0,
15-Jul-2023 10:47:38: API:ChirpConfig,0,0,0,0,0,0,0,7,0,
15-Jul-2023 10:47:51: API:EnableTestSource,0,1,0,
15-Jul-2023 10:47:51: API:FrameConfig,0,0,100,128,2000000,0,1200,0,
15-Jul-2023 10:47:51: API:AdvancedFrameConfig,1,0,0,0,1,128,2000000,0,1,1,2000000,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,100,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
15-Jul-2023 10:47:56: API:select_capture_device,DCA1000,0,
15-Jul-2023 10:48:10: API:SensorStart,0,
15-Jul-2023 10:48:17: API:update_num_adc_files_and_frames,1,100,1,0,
15-Jul-2023 10:48:51: Play as movie ,0,0,
15-Jul-2023 10:49:01: Play as movie ,1,0,
15-Jul-2023 10:49:02: Play as movie ,0,0,
15-Jul-2023 10:49:03: Play as movie ,1,0,
15-Jul-2023 10:49:04: Play as movie ,0,0,
15-Jul-2023 10:49:16: Play as movie ,1,0,
15-Jul-2023 10:49:17: Play as movie ,0,0,
15-Jul-2023 10:49:34: API:SensorStart,0,
15-Jul-2023 10:49:41: API:update_num_adc_files_and_frames,1,100,1,0,
15-Jul-2023 10:50:10: The logfile name is ,G: i15-Jul-2023 10:50:17: The radar data file name is ,G: i15-Jul-2023 10:50:19: Play as movie ,1,0,
15-Jul-2023 10:50:22: Play as movie ,0,0,
15-Jul-2023 10:50:55: API:SensorStart,0,
15-Jul-2023 10:51:03: API:update_num_adc_files_and_frames,1,100,1,0,
15-Jul-2023 10:51:09: API:update_num_adc_files_and_frames,1,100,1,0,
15-Jul-2023 10:51:26: The logfile name is ,G: i15-Jul-2023 10:51:31: The radar data file name is ,G: i15-Jul-2023 10:51:33: Play as movie ,1,0,
15-Jul-2023 10:51:36: Play as movie ,0,0,
15-Jul-2023 10:52:15: API:EnableTestSource,0,1,0,
15-Jul-2023 10:52:15: API:FrameConfig,0,0,200,128,2000000,0,1200,0,
15-Jul-2023 10:52:15: API:AdvancedFrameConfig,1,0,0,0,1,128,2000000,0,1,1,2000000,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,200,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
15-Jul-2023 10:54:02: API:SensorStart,0,
15-Jul-2023 10:54:12: API:update_num_adc_files_and_frames,1,200,1,0,
15-Jul-2023 10:54:17: Play as movie ,1,0,
15-Jul-2023 10:54:19: Play as movie ,0,0,
15-Jul-2023 10:57:31: API:ProfileConfig,0,1491308089,700,520,5565,0,0,1897,0,600,12000,0,0,30,0,
15-Jul-2023 10:57:31: API:ProfileConfig,1,1491308089,700,520,5565,0,0,553,0,600,12000,0,0,30,0,
15-Jul-2023 10:58:15: API:EnableTestSource,0,1,0,
15-Jul-2023 10:58:15: API:FrameConfig,0,0,0,128,2000000,0,1200,0,
15-Jul-2023 10:58:15: API:AdvancedFrameConfig,1,0,0,0,1,128,2000000,0,1,1,2000000,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,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
15-Jul-2023 10:58:21: API:SensorStart,0,
15-Jul-2023 10:58:32: API:SensorStop,0,
15-Jul-2023 10:58:35: API:update_num_adc_files_and_frames,1,306,1,0,
15-Jul-2023 10:58:44: Play as movie ,1,0,
15-Jul-2023 10:58:45: Play as movie ,0,0,
15-Jul-2023 11:00:03: API:SensorStart,0,
15-Jul-2023 11:00:12: API:SensorStop,0,
15-Jul-2023 11:00:14: API:update_num_adc_files_and_frames,1,173,1,0,
15-Jul-2023 11:00:36: The logfile name is ,G: i15-Jul-2023 11:00:42: The radar data file name is ,G: i15-Jul-2023 11:00:44: Play as movie ,0,0,
15-Jul-2023 11:01:09: Incorrect number of samples. We expect 614400. However, we got 307200.,1,
15-Jul-2023 11:02:16: API:SensorStart,0,
15-Jul-2023 11:02:43: API:SensorStop,0,
15-Jul-2023 11:02:45: API:update_num_adc_files_and_frames,1,796,1,0,
15-Jul-2023 11:02:51: Play as movie ,1,0,
15-Jul-2023 11:02:52: Play as movie ,0,0,
15-Jul-2023 11:03:36: Play as movie ,1,0,
15-Jul-2023 11:03:59: Play as movie ,0,0,
15-Jul-2023 11:04:01: Play as movie ,1,0,
15-Jul-2023 11:04:06: Play as movie ,0,0,
15-Jul-2023 11:04:20: Play as movie ,1,0,
15-Jul-2023 11:04:37: Play as movie ,0,0,
15-Jul-2023 11:04:50: Play as movie ,1,0,
15-Jul-2023 11:05:01: Play as movie ,0,0,
15-Jul-2023 11:07:21: API:SensorStart,0,
15-Jul-2023 11:07:28: API:SensorStop,0,
15-Jul-2023 11:07:31: API:update_num_adc_files_and_frames,1,121,1,0,
15-Jul-2023 11:07:47: The logfile name is ,G: i15-Jul-2023 11:07:52: The radar data file name is ,G: i15-Jul-2023 11:07:58: Play as movie ,0,0,
15-Jul-2023 11:08:16: Incorrect number of samples. We expect 614400. However, we got 307200.,1,
15-Jul-2023 11:09:54: API:SensorStart,0,
15-Jul-2023 11:10:00: API:SensorStop,0,
15-Jul-2023 11:10:04: API:update_num_adc_files_and_frames,1,120,1,0,
15-Jul-2023 11:10:10: The logfile name is ,G: i15-Jul-2023 11:10:16: The radar data file name is ,G: i15-Jul-2023 11:10:21: Play as movie ,1,0,
15-Jul-2023 11:10:22: Play as movie ,0,0,
15-Jul-2023 11:10:39: Incorrect number of samples. We expect 614400. However, we got 307200.,1,
15-Jul-2023 11:10:58: The logfile name is ,G: i15-Jul-2023 11:11:13: The radar data file name is ,G: i15-Jul-2023 11:11:23: Play as movie ,1,0,
15-Jul-2023 11:11:25: Play as movie ,0,0,
15-Jul-2023 11:11:43: Incorrect number of samples. We expect 614400. However, we got 307200.,1,
15-Jul-2023 11:16:12: API:SensorStart,0,
15-Jul-2023 11:16:20: API:SensorStop,0,
15-Jul-2023 11:16:22: API:update_num_adc_files_and_frames,1,198,1,0,
15-Jul-2023 11:16:27: Play as movie ,1,0,
15-Jul-2023 11:16:28: Play as movie ,0,0,
15-Jul-2023 11:17:42: API:SensorStart,0,
15-Jul-2023 11:17:56: API:update_num_adc_files_and_frames,1,306,1,0,
15-Jul-2023 11:18:02: Play as movie ,0,0,
15-Jul-2023 11:21:08: API:SensorStart,0,
15-Jul-2023 11:21:50: API:SensorStop,0,
15-Jul-2023 11:21:52: API:update_num_adc_files_and_frames,2,1266,1,0,
15-Jul-2023 11:21:56: Play as movie ,0,0,
15-Jul-2023 11:22:10: Play as movie ,1,0,
15-Jul-2023 11:22:25: Play as movie ,0,0,
15-Jul-2023 11:47:59: API:SensorStart,0,
15-Jul-2023 11:49:05: API:update_num_adc_files_and_frames,3,1862,1,0,
15-Jul-2023 11:49:11: Play as movie ,0,0,
15-Jul-2023 11:49:13: Play as movie ,1,0,
15-Jul-2023 11:49:44: Play as movie ,0,0,
15-Jul-2023 11:51:52: Incorrect number of samples. We expect 614400. However, we got 384960.,1,
15-Jul-2023 11:56:09: API:SensorStart,0,
15-Jul-2023 11:56:51: API:SensorStop,0,
15-Jul-2023 11:57:00: API:update_num_adc_files_and_frames,2,1258,1,0,
15-Jul-2023 11:57:21: The logfile name is ,G: i15-Jul-2023 11:57:29: The radar data file name is ,G: i15-Jul-2023 11:57:29: The binary fileG: i15-Jul-2023 11:57:39: The radar data file name is ,G: i15-Jul-2023 11:57:39: The binary fileG: i15-Jul-2023 11:57:49: The radar data file name is ,0,0,0,
15-Jul-2023 11:57:49: The file name is ,0,0,0,
15-Jul-2023 11:57:54: The logfile name is ,G: i15-Jul-2023 11:58:01: The radar data file name is ,G: i15-Jul-2023 11:58:01: The binary fileG: i15-Jul-2023 11:58:29: The radar data file name is ,0,0,0,
15-Jul-2023 11:58:29: The file name is ,0,0,0,
15-Jul-2023 11:58:40: The logfile name is ,G: i15-Jul-2023 11:58:45: The radar data file name is ,G: i15-Jul-2023 11:58:45: The binary fileG: i15-Jul-2023 11:58:53: The radar data file name is ,G: i15-Jul-2023 11:58:53: The binary fileG: i15-Jul-2023 11:59:09: The logfile name is ,G: i15-Jul-2023 11:59:14: The radar data file name is ,G: i15-Jul-2023 11:59:14: The binary fileG: i15-Jul-2023 11:59:31: The logfile name is ,G: i15-Jul-2023 11:59:39: The radar data file name is ,G: i15-Jul-2023 11:59:44: Play as movie ,1,0,
15-Jul-2023 11:59:46: Play as movie ,0,0,
15-Jul-2023 12:00:01: Play as movie ,1,0,
15-Jul-2023 12:00:15: The logfile name is ,G: i15-Jul-2023 12:00:23: The radar data file name is ,G: i15-Jul-2023 12:00:23: The binary fileG: i15-Jul-2023 12:02:46: The logfile name is ,G: i15-Jul-2023 12:02:52: The radar data file name is ,G: i15-Jul-2023 12:02:56: Play as movie ,0,0,
15-Jul-2023 12:04:07: The logfile name is ,G: i15-Jul-2023 12:04:15: The radar data file name is ,G: i15-Jul-2023 12:04:15: The binary fileG: i15-Jul-2023 12:07:02: API:SensorStart,0,
15-Jul-2023 12:07:38: API:SensorStop,0,
15-Jul-2023 12:07:41: API:update_num_adc_files_and_frames,2,1029,1,0,
15-Jul-2023 12:07:48: Play as movie ,0,0,
15-Jul-2023 12:08:53: Play as movie ,1,0,
15-Jul-2023 12:09:04: Play as movie ,0,0,
15-Jul-2023 12:09:09: Play as movie ,1,0,
15-Jul-2023 12:09:18: Play as movie ,0,0,
15-Jul-2023 12:09:24: Play as movie ,1,0,
15-Jul-2023 12:13:15: API:SensorStart,0,
15-Jul-2023 12:13:34: API:SensorStop,0,
15-Jul-2023 12:13:44: API:update_num_adc_files_and_frames,1,520,1,0,
15-Jul-2023 12:14:09: Play as movie ,0,0,
15-Jul-2023 12:15:10: Play as movie ,1,0,
15-Jul-2023 12:15:32: The logfile name is ,0,0,0,

BR,

Navid

  • 0
    TI__Mastermind 38315 points

    HI, Navid:

    You cannot post process the second binary data file by itself.  Any data that does not finish in the first binary data file will continue to be saved in the second file.  Therefore, the second/third binary file will not start from frame boundary.   

    Best,

    Zigang

  • 0 in reply to zigang Yang
    Prodigy 60 points

    Hi Zigang,

    Thank you for your prompt reply! So what is the correct way of loading binary files in mmWave Studio and get the results? I have 4 saved binary files from my measurement called: name.bin, name_0.bin, name_1.bin, and name_2.bin?

    name.bin is an empty file and when I load this in mmWave Studio nothing happens and no results appear in the plot windows.

    BR,

    Navid

  • 0 in reply to navid Amani
    TI__Mastermind 38315 points

    Hi, Navid:

    Can you try to configure the mmwave GUI the same way as you capture these data, and then enter the same name as you capture the data? Then skip the trigger and capture part and directly click on the "postProc" botton.  You should be able to see all the frames from all three files (name_0.bin, name_1.bin, and name_2.bin). 

    Best,

    Zigang

  • 0 in reply to zigang Yang
    TI__Mastermind 38315 points

    Just let you know that I will be on vacation for the next 10 days. 

    Best,

    Zigang 

  • 0 in reply to zigang Yang
    Prodigy 60 points

    Hi Zigang,

    Thank you for letting me know. I wish you an amazing vacation!

    I tried what you proposed earlier and got the below error messages! Any hint? 

    BR,

    Navid

  • 0 in reply to navid Amani
    TI__Genius 13235 points

    Hi Navid,

    I'm going to take a look into this while Zigang is out. I'll follow up in a day or so with some feedback.

    Thanks,

    Clinton

  • 0 in reply to Clinton Rodgers
    TI__Genius 13235 points

    Hi Navid,

    I reviewed this thread and have some follow up.

    1. I wanted to confirm the process you are performing that resulted in the most recent errors you posted
      1. I believe Zigang suggested following "step 1" and "step 4" from the image found at this part of the DCA user's guide: https://dev.ti.com/tirex/content/radar_toolbox_1_10_00_13/docs/hardware_guides/dca1000_mmwave_studio_user_guide.html#3-preparing-for-capture
      2. Is this the process you followed?
    2. In the output I noticed "NewMeas16.bin" being referenced, though earlier you mentioned the bin files being named name_0.bin, name_1.bin, etc.
      1. Are you using a different set of capture data now?
      2. If you are, is this new data also being broken up across multiple bin files?
      3. Could you provide the details, if that is the case (how many bin files, what file names were assigned)?

    Thanks,

    Clinton 

  • 0 in reply to Clinton Rodgers
    Prodigy 60 points

    Hi Clinton,

    Thank you for your reply.

    To clarify the bin file name, I had written it as a placeholder for the actual bin file names, since the problem occurred across all measurement scenarios that generated multiple bin files. In the screenshots I uploaded so far, the file used is 'newMeas16.bin'. So, I am not using different set of capture data.
    The data from this measurement was broken up across 3 files, named 'newMeas16_0.bin',  'newMeas16_1.bin'', and newMeas16_2.bin'. There is also another bin file named 'newMeas16.bin' which is empty.
    The process I followed is as you said. I hit Browse and loaded in the bin file, 'newMeas16.bin', then hit the PostProc button.
    BR,
    Navid
  • 0 in reply to navid Amani
    TI__Genius 13235 points

    Hi Navid,

    Thanks for the additional details. Could you try loading newMeas16_0.bin and following the same procedure? 

    Thanks again,

    Clinton

  • 0 in reply to Clinton Rodgers
    Prodigy 60 points

    Hi Clinton,

    It gives the below error:

    Any suggestion?

    BR,

    Navid

  • 0 in reply to navid Amani
    TI__Mastermind 38315 points

    Hi, Navid:

    I assume that the postProc works well with smaller capture size.   In that case, it means the postProc has some limitations in handling the long captures. We have an App notes (https://www.ti.com/lit/an/swra581b/swra581b.pdf ) describe the binary data format, and you can parse the data files accordingly.

    I have personally developed a parsing script for complex1x mode for single binary file.  and then extended to cross multiple binary files.  You can use them as a reference.  These scripts are not formal releases, and they are provided as it is. 

    2352.RawAdcDataProc.m

    0525.RawAdcDataProcCrossFiles.m

    Best,

    Zigang