RaceCapturePro2 logfile reference: Difference between revisions

 
(6 intermediate revisions by 2 users not shown)
Line 28: Line 28:


===Special Columns===
===Special Columns===
The following columns are system defined and will appear on every log file sample, regardless of the indicated sample rate.
====Interval====
====Interval====
Interval represents the milliseconds uptime of the system, and will reflect the number of milliseconds elapsed between samples.
Interval represents the milliseconds uptime of the system, and will reflect the number of milliseconds elapsed between samples.


====Utc====
====Utc====
Utc is sourced from GPS data and will be a valid, non zero value representing Utc time in milliseconds. When there is no GPS lock, UTC will be zero.
Utc is sourced from GPS data and will be a valid, non zero value representing UTC time in milliseconds, using the Unix time epoch of 1/1/1970 (number of milliseconds since 1/1/1970)
 
When there is no GPS lock, UTC will be zero.


==Data segment==
==Data segment==


Within the data segment, sample values appear at the frequency defined in the header file. When channels are logged at different sample rates the data logged at lower sample rates will appear sparsely within the file, with empty values appearing in the space between samples.
Within the data segment, sample values appear at the frequency defined in the header file. Channels logged at lower sample rates will appear sparsely within the file, with empty values appearing in the space between samples.
 


==Example==
==Example==
Line 49: Line 53:


</pre>
</pre>
==Sample Logs==
Sample log files can be downloaded [https://www.dropbox.com/sh/my8uocu3yp8bseb/AAA7Qa4tFOjaWlCx24VtkSK1a?dl=0 here]
==Troubleshooting==
It's best to use a freshly formatted FAT16 or FAT32 file. If you log a file and the data looks scrambled, encrypted, do a fresh re-format and try again.

Latest revision as of 20:04, 10 December 2023

Log file format

RaceCapture/Pro logs data onto SD cards using a sparsely populated comma separated value (CSV) format.

File naming

RaceCapture/Pro names files in an ascending order in a pattern of RC_XX.LOG where XX represents a number. When a new log file is created, RaceCapture/Pro will create the next log file where XX is the next available number, preventing duplicate or overwritten log files.

Header

The log file header defines the information present in the data segment of the log file.

Format

Each sampled channel is represented by a comma separated column. The column in the file is defined as a data structure with the following format:

  • Channel Name
  • Units Label
  • Min value
  • Max value
  • Sample Rate (Hz)

The data structure is defined as follows:

"<Name>"|"<Units>"|<Min value>|<Max Value>|<Sample Rate>

Example:

"Battery"|"Volts"|0.0|50.0

Each data structure describing a segment is separated with a comma.

Special Columns

The following columns are system defined and will appear on every log file sample, regardless of the indicated sample rate.

Interval

Interval represents the milliseconds uptime of the system, and will reflect the number of milliseconds elapsed between samples.

Utc

Utc is sourced from GPS data and will be a valid, non zero value representing UTC time in milliseconds, using the Unix time epoch of 1/1/1970 (number of milliseconds since 1/1/1970)

When there is no GPS lock, UTC will be zero.

Data segment

Within the data segment, sample values appear at the frequency defined in the header file. Channels logged at lower sample rates will appear sparsely within the file, with empty values appearing in the space between samples.

Example

"Interval"|"ms"|0|0|1,"Utc"|"ms"|0|0|1,"Battery"|"Volts"|0.0|50.0|1,"AccelX"|"G"|0.0|0.0|25,"AccelY"|"G"|0.0|0.0|25,"AccelZ"|"G"|0.0|0.0|25,"Yaw"|"Deg/Sec"|0.0|0.0|25,"Pitch"|"$
402,0,,-0.02,-0.03,0.93,0.5,-6.2,-0.2,,,,,,,,,,,,,,,,,,,,
442,0,,-0.02,-0.03,0.95,0.2,-6.0,-0.3,0,,,979,26,0.0,0.0,0.0,0.0,0.0,0,0,0.0,0,0.0,-1,0.0,0.0,0.0,0
482,0,,-0.01,-0.03,0.97,0.1,-5.5,-0.2,,,,,,,,,,,,,,,,,,,,
522,0,,-0.01,-0.03,0.99,0.0,-5.0,-0.2,,,,,,,,,,,,,,,,,,,,
542,0,,,,,,,,0,,,986,26,0.0,0.0,0.0,0.0,0.0,0,0,0.0,0,0.0,-1,0.0,,0.0,0

Sample Logs

Sample log files can be downloaded here

Troubleshooting

It's best to use a freshly formatted FAT16 or FAT32 file. If you log a file and the data looks scrambled, encrypted, do a fresh re-format and try again.