Event Information

In this Timer Tip Tuesday session, we’ll cover how to integrate RaceDay Scoring with RFID timing systems to simplify setup, improve accuracy, and streamline your race-day workflow.

We’ll cover:

• How to connect your RFID reader to RaceDay Scoring for automatic data collection and live scoring updates.
• Best practices for managing streams, file formats, and reader configurations.
• Troubleshooting tips for common connection and data flow issues.

View Slides

Summary of Webinar 

What You’ll Learn

• Why file streams are the recommended way to connect RFID → RaceDay Scoring

• How to configure RDS streams for RFID files

• How to configure RFID Server (middleware): bib–chip file, target/output files

• How to read and troubleshoot the output file from RFID

• What a rewind file is, why it’s critical, and how to set it up

• Best practices for:

  • IP addressing

  • Folder structures

  • Cleaning old race data

  • Handling OneDrive / cloud sync

  • Time zone gotchas

• How to use the Replay/Replay Stream feature inside RDS when data is in the file but not in the results

• General troubleshooting mindset: “If the box is beeping, you don’t have a problem.”

Key Concepts

1. Hardware + Middleware + Software

• RFID box – Physical race timing hardware (RFID Race Timing Systems).

• RFID Server – Middleware application that:

  • Reads data from the box

  • Uses a bib–chip file to map chip codes to bib numbers

  • Writes timing data files to a folder

• RaceDay Scoring – Consumes those files via file streams, turns them into timing data, results, etc.

Setting Up RaceDay Scoring for RFID

1. Use File Streams (Recommended)

In RDS:

1. Go to Streams

2. Add a new stream:

   • Stream Type: File – Custom or Chip System

   • This will expose a File Type dropdown

3. File Type: select RFID File

   • RDS will automatically rename the stream type accordingly

4. Folder Path:

   • Point this to the folder where only this stream’s reads will be stored

   • The extension is usually .txt, but make sure other random .txt files don’t live there or RDS will try to ingest them

Naming tip:
Name streams after the box or location (e.g., Start_121, Finish_122) so they’re easy to identify.

2. Device IP in Advanced Settings

• In the stream’s Advanced Settings in RDS, there’s a field for Device IP.

• You find the real box IP in the RFID hardware interface:

  • On the RFID box: Settings → Networking → IP address

• Each physical device must have a unique IP during a race.

Setting Up RFID Server (Middleware)

1. Bib–Chip File

In RFID Server:

• Go to Settings

• Load a bib–chip file:

  • 2 columns: bib,chip

  • Comma-separated

  • Order matters: bib first, then chip

• Enable “Use a bib file” and select that file.

This file tells the system which chip code belongs to which bib, so when a chip is read, the bib number can be recorded in the output file.

2. Target Files / Output Format

In RFID Server:

• Go to Target Files

• Set:

  • File format: typically “RFID Timing” (Todd’s preferred format – simple, chip+bib+timestamp)

  • Output folder: where the file for that device/stream will be written

• You can also configure a secondary output folder (e.g., OneDrive) for remote monitoring / backup.

3. Understanding the Output File

The RFID output file typically looks like:

• Chip Code, Bib Number, Timestamp

You should be comfortable opening this output file (or a copy of it) to:

• Spot unknown chips (chips not in your bib–chip file)

• Verify that reads are actually present

• Check timestamps when troubleshooting gaps

Key skill: If RDS shows “Unknown” or is missing a read, this file is where you confirm what really came off the hardware.

Rewind Files & Recovery

What is a Rewind File?

A rewind file is a special output configuration and matching stream that allows you to replay reads from the RFID box after the fact.

Why it matters:

• If connection drops, or you misconfigured the initial output, you can:

  • Fix your settings

  • Rewind from the box

  • Regenerate the output file in the correct format

  • Feed it into RDS via a rewind stream

Creating Rewind Output in RFID Server

• Configure another target file using RFID Timing format

• Name the output file as a fictional IP address not used by any actual box

  • Example:

    • Real box: 192.168.1.21

    • Rewind file: 192.168.1.98.txt

Matching Rewind Stream in RaceDay Scoring

In RDS:

• Create a separate stream for the rewind file:

  • Description: note that it’s a rewind (e.g., Start – Rewind 192.168.1.98)

  • Device IP: the same fictional IP address you used as the file name

• This stream will ingest the rewind file when generated.

Todd’s approach:

• Use consistent IPs for rewinds across all races/computers:

  • e.g., 192.168.1.98 for “Start Rewind”, 192.168.1.99 for “Finish Rewind”, etc.

• All timers know: “Start rewind always uses .98” etc. – easier to train & troubleshoot.

Best Practices 

1. Create a “Dummy Race” in RDS

• Set up a dummy race that includes all possible streams for all your boxes:

  • Start, Finish, splits, rewinds, etc.

• When you onboard a new timer or computer:

  • Import this dummy race

  • All streams come in pre-built

  • You only need to update the folder paths for that machine.

2. Keep Folders & Files Clean

• Before each race:

  • Clear out old files in the RFID data folder on each timer’s computer

  • Avoid accidentally pulling reads from previous events, especially if you’re changing read dates to the race date

• Todd’s practice:

  • Leave files on the computer for ~1 week after the race (in case of questions)

  • Then clear them once prepping for the next event

3. OneDrive / Cloud Storage Gotchas

• OneDrive can “hijack” file locations:

  • RDS may try to read from a OneDrive path where there is no new data

• Best pattern:

  • Primary output: local path (e.g., desktop folder) → used by RDS

  • Secondary output: OneDrive or cloud → for remote viewing / backup

• Never open the live file directly in OneDrive while it’s being written:

  • Always copy it and open the copy

  • Opening a live file being written can corrupt it

4. Time Zones

• Make sure:

  • Race time zone in RunSignup / RDS matches the actual race location

  • RFID boxes are set to the same time zone

• Quick check in RDS:

  • Time zone is shown next to the race name (top-left)

5. Main Streams & Replay in RaceDay Scoring

• All chip-based streams (RFID) should be set as Main Streams in RDS (unless you have a specific override like FinishLynx).

• If data is in the file but didn’t process correctly in RDS:

  • Use the Replay/“Replay Stream” option in RDS on that stream

  • RDS will re-ingest everything from that file and re-apply scoring logic

6. Practice Rewinds Before You Need Them

Todd’s rule:

• If your box is beeping, it’s reading chips – the data exists.

• Even if:

  • Output format was wrong

  • Wrong bib–chip file was used

  • Connection to RDS dropped

• You can always:

  • Fix your settings

  • Rewind from the box

  • Regenerate a clean file and feed it into RDS

But to avoid panic:

• Do a rewind at every race as part of your normal workflow:

  • After the first finishers, run a small, time-bounded rewind (e.g., from 8:14:12 onward)

  • Confirm it works and loads to the rewind stream

• Then, when something actually goes wrong mid-race, rewinding is muscle memory, not a crisis.

Handling Streaming Drops

Two main scenarios mentioned:

1. Using remote server (e.g., Outreach) / network drops

   • When the connection comes back, Outreach can automatically resync and fill in the missing data by rewinding from the box.

2. Using local Ethernet / nano stations and the connection breaks

   • It won’t auto-resume to backfill missing data to RDS.

   • Solution:

     • After detecting the missing block (e.g., several runners with same “gap”), perform a rewind from the box for that time window.

     • Save using the correct rewind filename/IP.

     • Let RDS ingest via the rewind stream.