Race Timing System: Live race display

Live race display

Start the existing local timing receiver, then open Live race display from the dashboard, racer assignment screen, or camera review screen. Direct address: http://127.0.0.1:8765/display (or the HTTPS address and port configured for your receiver). Use the same local timing login. The result display does not publish results to Sports Hub. Its authenticated Start Race control records a local gun start.

Choose the race, gun/chip ranking basis, all racers or finishers, and rows per page. Full screen presents the display on a monitor, TV or projector connected to the timing computer. Rotate pages advances through the selected results every ten seconds. You can select a race directly using /display?race=RACE_KEY.

The large race clock waits at zero until Start selected race is pressed, then counts upward from the actual recorded gun start. The smaller current clock displays the server's time in the display browser's local timezone. Synchronize the timing computer's clock before the race and set the actual gun start in its race configuration or Sports Hub import. Press Start selected race at the start signal. The actual timestamp is taken when the timing server receives the request; browser/network delay can affect alignment with a physical signal. The system does not detect a starter's pistol. Use a wired/local connection and coordinate the button with the starter. The race clock continues until the display is closed, even after all racers finish.

Results refresh every two seconds. Clock animation runs between snapshots. On-course time is an elapsed clock, not a finish detection; chip elapsed time requires a captured start. Finish places use the chosen timing basis; equal times share a place and missing chip times remain unranked. Pending racers are not automatically marked DNS/DNF. Unapproved camera detections never affect results. All displayed finishes remain provisional.

A lost connection clearly marks the results as frozen and the continuing clock as estimated. Hidden tabs pause result requests and reconnect when visible. /api/live and /display require existing local Basic authentication; no public/unprotected endpoint is added. A separate computer can view the screen using the receiver's existing HTTPS LAN configuration and local login. Do not expose the receiver on the public internet. No additional service, background worker, or database migration is needed.