How To: Add a Datalogger Overlay

See Also: Compatible Dataloggers

In order to add a datalogger overlay to a RaceRender project, you will need to first use the datalogger's software to export the data in a compatible CSV or text file format. The CSV format is most common, and is also known as a comma-delimited text or spreadsheet file. Files delimited by a tab or semi-colon may also work. Details on how to create these files for several popular dataloggers are provided further below.

Once you have your data in a compatible CSV file, it can be added to the current project as an input file. After adding a datalogger file to the project from the Main screen, a version of the Template Menu will appear and display several data templates to choose from. If you cancel it, some basic display objects may be created automatically. You can add more display objects by right-clicking on the input file in the list on the Main screen and selecting "Create Display Object". The Synchronization Tool can be used to synchronize the datalogger file with the video files of your project.

Because datalogger capabilities vary widely, some data visualization objects may not be supported by your datalogger file. It is recommended that you arrange and configure the data visualization objects to your liking, and then create a template of them, so that they can be easily imported into your future projects. Template files you create can also be shared with other RaceRender 2 users.

RaceRender's datalogger features require certain data to be provided in the input file, and in a form that it recognizes. Depending on the actual output of your datalogger's software, some RaceRender features may not be functional with all dataloggers or in all cases. You may be able to improve compatibility by manually assigning the data fields on the Input File Configuration screen.


Missing Lap Numbers & Times

Some dataloggers do not provide lap numbers in their exported data, or in a compatible format. This is needed for several features, including lap counters & timers, and cleaner rendering of track maps. However, this missing lap data can be substituted by manually setting the Start / Finish point.


Speeds in MPH, Km/h, m/s, or Knots

RaceRender attempts to automatically display vehicle speeds in Miles Per Hour (MPH). In cases where you want to display a different measure of speed, or if the automatic conversion is not correct, you can use the Input File Configuration screen to select the "Vehicle Speed" field and the desired units conversion. Once the selection is changed to something other than "(Automatic)", the unit conversion option to the right will become active.


NMEA and GPX Format Support   (Generic GPS Dataloggers)

Note: The GPX format referred to in this section is the GPS eXchage file format (.GPX), and should not be confused with dataloggers that may use the letters "GPX" in their product name.

RaceRender also provides support for the NMEA and GPX (GPS eXchange) file formats commonly used by non-motorsports GPS loggers. It requires them to be in standard ASCII or UTF-8 text encoding, with the samples in normal sequential order. This will typically provide a track map and vehicle position at a relatively low sample rate, but other data visualizations may not be available. Generally, NMEA will provide more useful information than GPX for this purpose, and is preferred. In order to get lap counts and times, as well as draw a cleaner track map (based on one selected lap), you will need to manually set the Start / Finish point.

Important (NMEA): NMEA data must contain RMC, GGA, and/or GLL sentences, in the standard format of one NMEA sentence per text line. Valid fix times are required on all applicable NMEA samples that are marked Active. RMC and GGA are recommended; GLL support is simply included for compatibility reasons. All NMEA sentences must start with "$GP", such as "$GPRMC" and "$GPGGA".

Important (GPX): GPX data will only work if the session is logged as a set of "track" points (not waypoints), and each of those points includes a timestamp in the standard format. Because this is a somewhat loose format, there may be variations that do not work with RaceRender. Generally speaking, the file must begin with an <?xml> tag, and each track point should look similar to the following example:

  <trkpt lat="39.602613" lon="-105.020217">
      <ele>1624.77</ele>
      <time>2011-06-02T14:28:35Z</time>
      <speed>31.2</speed>
  </trkpt>

The time tag is always required. The elevation and speed tags are optional, but recommended.


How to Export a Datalogger Session into a Compatible File

These are basic instructions for how to get several datalogger products to export data for use with RaceRender, based on information available at the time of this writing. This depends on functionality provided by these other products; compatibility and the accuracy of this information may change at any time and without notice.




The third party product and brand names mentioned here are trademarks of their respective owners. They are referenced here in order to provide compatibility guidance, and do not construe any endorsement or affiliation by those entities.



Copyright © 2012 RaceRender LLC

iPhone, iPod touch, and iTunes are trademarks of Apple Inc., registered in the U.S. and other countries.
Content purchased from the iTunes Store is for personal lawful use only. Don’t steal music.