RLC Data Logger- not clear on dashware csv file specification / requirements

[iteracer71]

I am using a Dash / Data Logger from RLC (rlcracing.com). It captures either to a proprietary binary BIN file format, and/or can encodes the data right into the chasecam video file.

Using their latest PC software I can import a log file or video file, then export it to a tab delimitted text file. I have found that I can then import this into Excel, and back out to a CSV file. (tedious, but perhaps I can write a program to aid with the conversion once I get one going)

My problem is that I am not clear what the file specification is for dashware to read the file. Using the "other" feature it keeps giving an error reading the file when I attempt to import it.

- Does the first column need to be auto numbered?
- Does the second column need to be timestamp? If so, RLC does not export that value in the current version of their software
- Does the file format need to have delimiters for nulls?
- Can you point me to a basic well formed CSV that represents the mimimal set?
- Etc...

In short, without a clear file spec- I don't know how to format the data so dashware will read my files.


RLC Tab-delimited Exported Text File Format:

Water Temp Oil Temp Oil Pressure GForce - X GForce - Y GForce - Z Car Battery Tach Latitude Longitude Speed
201.72 238.16 84.26 0.64 0.97 0.12 14.82 5940.00
201.72 238.16 84.26 0.64 0.97 0.12 14.82 5885.00
201.72 238.16 84.26 0.64 0.97 0.12 14.82 5885.00
201.72 238.16 78.12 0.64 0.97 0.12 14.82 5889.00
201.72 238.16 78.12 0.64 0.97 0.12 14.82 5889.00
201.72 238.16 78.12 0.64 0.97 0.12 14.82 5995.00
201.72 238.16 78.12 0.64 0.97 0.12 14.82 5995.00
201.72 238.16 78.12 0.64 0.97 0.12 14.82 6071.00
201.72 238.16 78.12 0.64 0.97 0.12 14.82 6071.00
201.72 238.16 78.12 0.64 0.97 0.12 14.82 6097.00
201.72 238.16 78.12 0.64 0.97 0.12 14.82 6117.00
201.72 238.16 77.56 0.64 0.97 0.12 14.82 6117.00
201.72 238.16 77.56 0.64 0.97 0.12 14.82 6079.00
201.72 238.16 77.56 0.64 0.97 0.12 14.82 6079.00
201.72 238.16 77.56 0.64 0.97 0.12 14.82 6061.00
201.72 238.16 77.94 0.64 0.97 0.12 14.82 6061.00
201.72 238.16 77.94 0.64 0.97 0.12 14.82 6006.00
201.72 238.16 77.94 0.64 0.97 0.12 14.82 6006.00
201.72 238.16 77.94 0.64 0.97 0.12 14.82 5982.00
201.72 238.16 83.88 0.64 0.97 0.12 14.82 5982.00 4535.93847 -12241.96484 46.45



Re-formatted CSV File I put together:

Sample,Water Temp,Oil Temp,Oil Pressure,GForce - X,GForce - Y,GForce - Z,Car Battery,Tach,Latitude,Longitude,Speed
1,201.72,238.16,84.26,0.64,0.97,0.12,14.82,5940,,,
2,201.72,238.16,84.26,0.64,0.97,0.12,14.82,5885,,,
3,201.72,238.16,84.26,0.64,0.97,0.12,14.82,5885,,,
4,201.72,238.16,78.12,0.64,0.97,0.12,14.82,5889,,,
5,201.72,238.16,78.12,0.64,0.97,0.12,14.82,5889,,,
6,201.72,238.16,78.12,0.64,0.97,0.12,14.82,5995,,,
7,201.72,238.16,78.12,0.64,0.97,0.12,14.82,5995,,,
8,201.72,238.16,78.12,0.64,0.97,0.12,14.82,6071,,,
9,201.72,238.16,78.12,0.64,0.97,0.12,14.82,6071,,,
10,201.72,238.16,78.12,0.64,0.97,0.12,14.82,6097,, ,
11,201.72,238.16,78.12,0.64,0.97,0.12,14.82,6117,, ,
12,201.72,238.16,77.56,0.64,0.97,0.12,14.82,6117,, ,
13,201.72,238.16,77.56,0.64,0.97,0.12,14.82,6079,, ,
14,201.72,238.16,77.56,0.64,0.97,0.12,14.82,6079,, ,
15,201.72,238.16,77.56,0.64,0.97,0.12,14.82,6061,, ,
16,201.72,238.16,77.94,0.64,0.97,0.12,14.82,6061,, ,
17,201.72,238.16,77.94,0.64,0.97,0.12,14.82,6006,, ,
18,201.72,238.16,77.94,0.64,0.97,0.12,14.82,6006,, ,
19,201.72,238.16,77.94,0.64,0.97,0.12,14.82,5982,, ,
20,201.72,238.16,83.88,0.64,0.97,0.12,14.82,5982,4 535.93847,-12241.96484,46.45

[Rolf]

Hello iteracer71,

We will actually parse comma, semicolon or tab delimited data.

The first thing I notice is there is no Time column in your data. DashWare needs to have a time value for every row, otherwise we do not know the frequency of your data. The time unit should be seconds (note that you can have decimal values such as 0.1) and the time column's header entry should have the word "Time" in it.

If your logger software will not export a time column but you know the frequency of the log lines, then you can add your own Time column in Excel using its Fill Down feature (I think that's what it's called).

There is a topic in the DashWare help that will better explain how your data needs to look when using the logger type "Other". Hit F1 then you can locate this topic in the help table of contents under "How Do I... > Importing Video and Data > Using your Data Logger Software > Using Other Loggers".

Pay careful attention to the translation table. DashWare hunts for specific column names, stopping at the first match.

So in your case:

You need a "Time" column with the running time in seconds.
To get a sync map, change your "Latitude" column name to "X" and your "Longitude" column to "Y". I know the full names should work but I have seen us have problems with those, so the safest is to use X and Y.
To avoid problems with the map accidentally using your G Force values, change your "GForce - X" column name to "LatG" and your "GForce - Y" to "LongG". Some loggers flip X and Y, so you may need to flip your mapping and use "LongG" for "GForce - X" and "LatG" for "GForce - Y".


I also notice that you only get GPS coordinates every once in a while, instead of in every row. I assume this is because your accelerometer gives you more frequent readings than the GPS (as that is usually the case). Some loggers will interpolate coordinates in between these GPS readings, but yours is leaving the values empty. DashWare will interpret empty values as 0 so I am worried your map will not draw correctly.

Can you send your unmodified, tab-delimited data file to rolf@chasecam.com ? I would like to try it out. We are overhauling our data importing code so I would like to make sure we support these types of things in the future.

Thanks,
Rolf

[tentenths]

I'm testing an RLC logger next week. Does it work with DW?

thanks,

mr

[Rolf]

Hi mr,

I am not familiar with the RLC software and its export options, and we do not have a sample CSV file. I can only go by the data pasted above.

The data shown is missing a required Time (running time in seconds) field. If you know the rate of data, you could always create a Time column in Excel or Open Office. Also, some of the column headings should be renamed, as per above. The GPS data is missing in many of the rows, and needs to be filled in with either the previous value or an interpolated value.

DashWare 1.1 (targeted for release mid Sept) should allow us to address these issues more easily with Data Profiles. If you get some data, could you send a CSV file to us?

Thanks,
Rolf

[Dmitriy]

I'll send you a data file, got a copy of one here. I have gotten it to work!

[Rolf]

Awesome, thanks!

[RLC_Racing]

My name is Jennifer and I work for RLC Racing. I would like to let everyone know that it is now easy to use your data from one of our race loggers with Chase CAM Dashware. The new PC software posted at our website has an easy export function that coverts the data to the correct format to be used with the DashWare. One the next release of the DashWare, there will be an RLC Racing dash that you can easily add to your video.

Also, if you used a Chase CAM camera with an RLC Racing dash then it is even easier to use DashWare. RLC Racing worked directly with Chase CAM to allow for truly synchronized video. The Chase CAM camera is plugged directly into the RLC Racing unit and the data being logged by the race logger is embedded into the video file. Now when you take that file to DashWare there is nothing for you to do but press play. The data and video are already synchrnonized!

[Jadon]

really gr88888!!!!!

[Jadon]

gr8 post !!!