RaceResult can be used as a middleware between your RaceResult Devices and RaceDay Scoring to pass times directly from RaceResult into RaceDay Scoring.


There are two main pieces of the integration - 

  • The connection to the RaceResult software itself
  • How we should filter that single stream of data into multiple Streams in RaceDay Scoring.

Setting up Race Result 12

  1. Start the Race Result Web Server 

  2. Start a New Event

    File -> New Event

  1. Name the event and set the event date

  2. Save the event .ses file somewhere that makes sense for your workflow

  3. Double click on the event name to open Race Result 12 


In Race Result 12, go to Timing. For the purposes of a simple integration, like we are covering today, we will not be loading any participant data into RR12.


The purpose of this setup is a very simple workflow using Race Result 12 as middleware - you may develop a different workflow over time, but users scoring in RaceDay Scoring and just getting started should follow this path


Go to Exporters + Tracking to set up your exporter to RaceDay Scoring. 


It is important to understand that we are using Race Result 12 as middleware here. 


Middleware connects Hardware (your Race Result decoder) to Software like RaceDay Scoring




  1. Name can be set to “All” since we are sending all timing points to this exporter. Note that Timing Point/Split is set to “<All>”

  2. IP/Server Name is set to “localhost” and the Port is set to “3061”

  3. Export Data is set to “Raw Data Record V2”

  4. Save the settings once you have set this up




Playing Data from Race Result 12


The exporter(s) must be set up before you are able to play data out of Race Result 12 to RaceDay Scoring.

You MUST turn on the reads connector in RaceDay Scoring before playing the Race Result 12 exporter

In Race Result 12, go to Timing -> Systems and scroll down to Exporters + Tracking and press Play (green arrow





Once your Exporter is playing (you will see options for Pause, Replay, and Stop) you can play data TO the exporter from your devices. Data can be replayed with the blue back arrow.


While you can do things in a different order and still get results, this is the path preferred by support.




If you are getting an error similar to the one on the right, you need to make sure your reads connector is on in RaceDay Scoring and that you have given it permission on your computer to accept data.



Connecting to RaceResult Software


In order to connect to the RaceResult software, we need to know two things when setting up Streams in RaceDay Scoring.


  • Listen Port - default is 3601
  • List Address - default is localhost


If you are running RaceResult on the same computer as RaceDay Scoring these defaults should work. If you are running RaceResult on another computer on the same network you could use the IP Address of that computer to access it.

Setting Chip System Defaults


Go to Streams -> Settings and save the defaults for RaceResult (or change them based on your needs)

Adding Streams for each RaceResult Source/Device

Now that you've set your default RaceResult configuration settings like Port and Address, you should create a Stream in RaceDay Scoring for each RaceResult Device you are using for this Race.


When you connect to RaceResult directly, all data from all readers comes in at once and RaceDay Scoring needs to know how to split up those reads into different devices that you will use in different Locations for your Race.


To do this - we use the RaceResult Source Name or Decoder Box Name - usually something like D-4501


You can access the Stream Setup by going to the Streams item on the left hand toolbar:



Click the “Add Stream” button to begin creating a new Stream for you to use for your Races.

Now select Race Result Direct from the Stream Type dropdown:

And fill out the configuration needed. Be sure to set a Name, Source Name, Timing Location Assignment (optional right now, can be set later):


Once you have these items set you can being collecting reads as described here.