Call me back | My basket | Checkout | Add to email list

     You are here: Website » Knowledge base

« back to website

Software / RunProcessor

Run Processor

Run processor is the Race Technology's Run data file management utility. It can be used to:

  • Extract data and save to disk in different formats (export)
  • Split large run files into smaller ones
  • Convert (binary) run file data to readable text
  • Batch process run files etc.

This program's screen is divided into three sections:

  • Run file processing options
  • Export format selection (file or local window)
  • Source RUN file(s) selection.

Run file processing options

There are ten different run file processing options available:

  • Convert Raw data to a table of ASCII text values
  • Performance results
  • Extract all DBC processed CAN data
  • Raw CAN data extract
  • Extract GPS binary data
  • Extract serial data as binary
  • Extract serial data as ASCII
  • Text analysis of run file
  • Split RUN file
  • Batch processing to extract lap times and summary statistics

1. Raw data

Following options are availabe when Raw data export type is selected

  • Sample frequency: The amount of data read from the .RUN file per second is depend on this value.
For example, if 10Hz is selected, the CSV file will have data at 0.1s intervals.
The higher the frequency the larger the resulting CSV file.
  • Load variables: Used to select a different variable file, if not used then the default variable file with all default names will be used.

2. Performance results

This mode is for post processing data from the SPEEDBOX range of products.

Before data can be processed, the required tests must be configured, to do this click on the "Configure" button.

To get the maximum accuracy from the performance calculations the input data sample rates must be set up correctly. The data that the system requires configuration for is:

  • NED velocity - this is the key message which calculations are based
  • Accelerations - this is used for the calculation of some results, and also in the logic for determining when the vechicle pulled away from a halt
  • GPS positional accuracy - this is used to know when the GPS data is reliable and accurate
  • Hardware triggers - For detecting button presses or laser trigger events, only required if triggering on these inputs
  • Analogue inputs - For triggering on analogue voltages, only required if triggering the test based on voltage

Recommended samples rates are:

For the SPEEDBOX, running in GPS only mode:

  • NED velocity - 20Hz
  • Accelerations - 200Hz
  • GPS positional accuracy - 20Hz
  • Hardware triggers - Anything except disabled
  • Analogue inputs - 200Hz

For the SPEEDBOX, running in GPS and accelerometer mode:

  • NED velocity - 200Hz
  • Accelerations - 200Hz
  • GPS positional accuracy - 20Hz
  • Hardware triggers - Anything except disabled
  • Analogue inputs - 200Hz


  • NED velocity - 200Hz
  • Accelerations - 200Hz
  • GPS positional accuracy - 20Hz
  • Hardware triggers - Anything except disabled
  • Analogue inputs - 200Hz

There is no issue with having other channels enabled as well, for example when using an INS system it might be also desireable for be logging vehicle pitch, but these are the channels are are essential for the performance calculations.

3. DBC processed CAN data (text with time stamps)

Output file will contain list of DBC Processed CAN data messages with following information for each message.

  • Time stamp
  • CAN port no
  • CAN msg name
  • Signal name
  • Decoded value

Please note that the relevant dbc file(s) must be loaded to decode the run files correctly.

4. Raw CAN data (text with time stamps)

Output file will contain list of raw CAN data messages with the following fields for each message:

  • Time stamp
  • CAN port no - from which port the constructed CAN message outputted
  • Type (11 bit or 29 bit)
  • CAN address
  • Number of bytes in the can message
  • Received CAN bytes in hex format

5. Embedded raw GPS data

The GPS binary file will contain all the data that is output from the GPS module including and processed positional/velocity messages as well as the raw ranging data etc. This information is only available from Mk2 DL1 (with the black connector) or DL2s. This file is binary and only normally required for specialist applications.

6. Embedded serial data (binary)

This file format will contain all the data that was logged by the DL1 or DL2 assuming that it was configured to not expect RT format data. If the DL1 or DL2 was configured to expect standard RT on it's serial port then this file will be empty (0 bytes).

7. Embedded serial data (text with time stamps)

Output file will contain a list of serial data input messages with following fields:

  • Time stamp - raw serial data packet received time
  • Raw serial data in hex
  • Raw serial data as a string

8. Text analysis of data file (for debugging only)

All hardware messages in the selected run file will be outputted to a readable text format with following informaiton:

  • Hardware Message number (for list of hardware messages see here
  • Length of the message in bytes
  • Message data in hex format
  • Number of returned channels (variables) in the message

Then it lists the channels (variables) embedded in the message with following information.

  • Variable reference number
  • Channel (variable) name
  • Variable value
  • Variable value after the unit convertion

Selecting the file format

Run data can be exported to following formats.

1. CSV (comma separated value) format

For the .CSV file format, enter the character that you would like to use as the data value separator, in to the Separator edit box.
(It is recommended to keep the default separator - comma (,))

2. Matlab .m file

You can also extract raw GPS and raw Serial data from the .RUN file and save them into two separate files in binary format (.bin).

Files section

To select run files do one of the following:

  • Drag & drop a run file or a folder containing run files to the text box
  • Click on the "Load file" button and select a single run file
  • Click on the "Load folder" button to select a directory containing run files.

Press Start button to start conversion. Progress bars visually indicate the amount of data processed whilst 'Status'' gives you the progress as a percentage. You can the conversion at any moment, while it is in progress. Created file(s) will have data only up to that point. Output files (CSV or matlab) will be created in the same directory as the source run files.

Page last modified on November 23, 2020, at 10:45 AM