Race Link Core

Standalone timing and tracking. Race-ready by design.

Race Link Core is the dedicated in-vehicle timing and tracking device for events that need modern race intelligence without depending on a perfect cloud link. Course awareness, virtual timing, pass protocol, hazards, SOS, and cloud handoff run from one hardened race-day system.

//

The device layer

The timing system becomes a product.

Core turns course files, GPS, driver screen state, and live telemetry into a clean operating layer for racers, race control, and the cloud platform.

RACE LINK CORE #864 RM 44.1
Race mode CLEAR OPEN COURSE AHEAD
Race mile42.7
Speed63
NextClear
ActionDrive
SOSPTPACKMUTE
01Course loaded

GPX route, checkpoints, speed zones, neutral sections, and race-mile context prepared before staging.

02Timing local

Start/finish, course progress, distance remaining, and checkpoint context stay available on the vehicle.

03Network tolerant

Core keeps race state useful when satellite fades, then syncs when the connection returns.

04Cloud unified

When connected, Core feeds Race Link Live timing, maps, leaderboards, race control, and replay.

01

Why Core

Built to replace fragile race timing with one modern source of truth.

Legacy race tracking often asks teams and officials to reconcile radios, trackers, manual notes, and delayed cloud data. Core starts from the other direction: give the vehicle a clear local race brain, then publish the same truth everywhere else.

Timing

Standalone start/finish logic

Core can keep course progress and start/finish context on the vehicle instead of waiting for cloud timing to catch up.

Course

GPX course awareness

Routes, checkpoints, speed zones, and race-mile context become a driver-facing operating picture, not a buried setup file.

Track

Live race tracking

Position, speed, heading, freshness, and race context feed the platform map, leaderboards, replay, and race control views.

Pass

Passing protocol

Pass requests, received requests, acknowledgements, no-response states, and neutralized sections are explicit on the screen.

Safety

Hazards and SOS state

Driver-visible hazard, SOS, and GPS-degraded states make critical race context harder to miss.

Cloud

Clean cloud handoff

When the link is available, Race Link Live receives the same state used by the vehicle, reducing gaps between racers, officials, and fans.

5 inDriver screen
target form factor
GPXCourse package
input
LocalTiming continues
through link gaps
CloudSyncs into Race
Link Live
02

Modern timing

Designed like infrastructure, not a bolt-on tracker.

The product work is in the system behavior: predictable setup, visible state, defensible timing, and graceful degradation when the race moves beyond perfect connectivity.

Defensible

Evidence-friendly timing

Course crossings, race-mile context, and event state can feed the same timeline used for leaderboards, officiating review, and replay.

Resilient

Store-and-forward posture

Race state is useful locally first and syncs outward when the network allows. That is the right failure mode for remote racing.

Clarity

Driver-readable states

Clear, pass ready, request sent, pass OK, GPS weak, wrong course, speed zone, and SOS states are built for quick reads under pressure.

Ops

Fleet and setup visibility

Assignment confirmation, diagnostics, Wi-Fi setup, course status, and device readiness reduce race-morning guesswork.

Privacy

Role-aware data sharing

Teams, officials, fans, and sponsors do not need the same data. Core feeds the platform that controls what each audience sees.

Upgrade path

Roadmap-ready architecture

The same Core layer can grow into richer local relay, telemetry, incident review, and AI-assisted race operations without changing the event workflow.

03

Driver screen states

The race is reduced to clear decisions.

The screen system is intentionally direct: race mode, vehicle ahead, pass request, pass OK, SOS, crash ahead, GPS weak, setup required, neutral zone, and speed-zone states. No hidden tabs. No consumer-app clutter.

Race Link Core driver screen state contact sheet showing clear course, pass protocol, SOS, hazard, setup, GPS, neutral zone, and speed zone states
Race Link Core driver screen state study. Production hardware and firmware details may vary by deployment.
04

Roadmap

The Core device is the base layer for the next generation of race operations.

The public promise is simple: timing, tracking, and race state get more reliable with each deployment. The roadmap keeps the operator in control while the platform gets smarter underneath.

Relay

Local race network expansion

Deeper local relay options for events where satellite visibility, terrain, or cost requires more than one path out of the vehicle.

Control

Race-control tools

More structured handoff from Core states into race control review, incident context, checkpoint validation, and post-race audit.

Telemetry

Expanded sensor fusion

Tighter integration between GPS, CAN, driver screen state, and device health so timing and vehicle context stay aligned.

Rules

Course-rule packages

Speed zones, neutral sections, pass windows, and course-specific alerts packaged as event configuration instead of one-off manual setup.

AI-assisted

Operator-assist intelligence

Anomaly, incident, reliability, and production recommendations grounded in Core data. Human operators accept, suppress, or override.

Experience

Fan and team surfaces

Core timing becomes the signal behind cleaner leaderboards, better race stories, sharper broadcast graphics, and team-specific operating views.

See it live

Put Core on your course. Then run the race from one truth.

We will map your course, timing rules, vehicle count, and connectivity plan into a Core deployment path.