• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 1078 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.

AWR1642BOOST: dat data file donot correspond with csv data file

Kathy Lee60
Intellectual 515 points
Part Number: AWR1642BOOST

Hi TI-team,

I run the mmWave Demo Visualizer according to the mmwave_sdk_user_guide.pdf, and I got two data file "*.dat" and "*.csv".  My operation order was:  at first click "log start", then click "record start", then after a while the record stopped automatically according to the "record time" configuration, then click "log stop".  I thought that these two kinds of files represent the same data but with different forms, I read the *.dat datafile to a *.txt file according to the python program "parseTLV.py" that TI-team suggested. After that, I looked through these two data file, I could not find any correspondence in these two files. For example, in the ".csv" file the total targets number(the second coloumn) is alway less than 8, but in the ".txt" file there are some packet whose targets number bigger than 10. Is there anything wrong? Thanks a lot in advance!

Best wishes,

Kathy

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/1023/csv-dat-txt-datafile.7z

  • 0
    TI__Mastermind 24955 points
    Kathy,

    Please refer to this information taken from the mmWave Demo Visualizer User's Guide: www.ti.com/.../swru529b.pdf

    "4. 4. Concurrent Recording of Processed Stream From mmWave Device

    If users want to save the incoming processed stream from the mmWave device for some offline analysis while its getting plotted, they can use the Record Start button in the plots tab. The recording can be started while the device is in stopped state and unconfigured (for example, after a fresh reboot and/or the sensor is stopped using the Sensor Stop button), or while the device is running and actively outputting data. The data is saved to a timestamped file in binary format on the device. The data keeps accumulating in the file until one of the following conditions are met:

    • User presses the Record Stop button
    • File size exceeds the limit set in the user-configurable field, File Size Max (MB).
    • File accumulated data for at least the time set in the user-configurable field, Record time max(s).

    The data saved in this file is the exact same data and format that is transmitted out of the mmWave device over the DATA_port. Users should see the mmWave demo doxygen in the mmWave SDK package to understand the format of the data and how to parse it."

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Intellectual 515 points

    Hi Kyle,

    thanks for your reply. I have read through the 4.4 in mmWave Demo User's Guide before, but there is no information about the relationship between *.dat data file and *.csv data file. Is the *.csv data file derived from the correponding *.dat data file? How can I match the *.csv and *.dat files?

    Regards,

    Kathy

  • 0 in reply to Kathy Lee60
    TI__Mastermind 24955 points
    Kathy,

    The .dat file and .csv file have the exact same data. One additional step is taken to make the .csv file readable and easier to parse with programs like MATLAB that have a csv read function ( i.e. csvread() ).

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Intellectual 515 points

    Hi Kyle,

    many thanks for your reply. If they are the exactly same data, how can I find the one-to-one relationship between the frames in *.csv and packets in *.dat? I found that in every *.csv file the frameID always start from 1, while in the *.dat file the packetID are some other serial numbers. Here I uploaded a parsed dat file with range profiles omitted, and a corresponding csv file. Please note that the csv file is a superset of the dat file temporally. Thanks again!

    Best wishes,

    Kathy

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/1023/csv_5F00_dat.7z