Race timing: prepare the meet and RFID reader

Prepare a test before race day

Set up the intended meet/race, scoring rules and participants. Confirm bib-to-racer and RFID tag mappings; an arbitrary detected tag is not automatically a registered competitor. Reader and antenna setup need testing in the actual environment.

Configure the system

1. Install Race Timing and its documented dependencies. Connect the correct Hub account and meet where used.
2. Configure the reader connection and intended antennas according to the supplied app reference and reader documentation.
3. Review graphical racer/bib/RFID assignments for duplicates, missing tags and incorrect identities.
4. Conduct a controlled read test with known registered tags. Verify that expected reads appear under the correct racers and that non-race tags do not enter race results.
5. Check start/finish/split configuration, clock and time zone. Test the intended start/stop workflow with non-production data first.

Run the race

Use the race controls deliberately. Starting, stopping and restarting capture or a race clock are different actions; read the current state before clicking again. Monitor timing controls separately from the public/team-results display. Do not publish unreviewed anomalies as final simply because a reader detected a tag.

Review and preserve

Investigate duplicate, missed or out-of-order detections with the available review tools. Export/save the intended records and publish reviewed results through the supported Hub workflow. Preserve original observations for later review. Hardware placement, interference and missed reads require practical testing; software setup alone cannot guarantee every athlete is detected.