Speedhive

Speedhive supplies two separate things: championship standings that a grid can be ordered by, and live timing during an event. They are set up separately and neither requires the other.

Championship standings

Open Setup → Integrations → Speedhive and enter your Speedhive organization id. Race Control then finds the championships for a season and asks you to confirm which local classA competition category such as 600 Superstock. A class joins riders to races, and championship points accrue in it. each one maps to.

Every mapping needs your confirmation. Race Control suggests a match only when a class name agrees exactly, after ignoring case and spacing. An abbreviation never matches silently, so Female LW does not map itself to Female Lightweight.

Once mapped, current class season points become available as a grid criterionOne rule that orders riders, such as qualifying lap time. A grid configuration applies its criteria in order.. See How grids are ordered.

How a standings row reaches a rider

A row resolves to one of your riders automatically only when the number and the normalized name both agree inside the mapped class. Check missing matches on the event's Entries leaf.

A decision you make once is replayed on later refreshes. When you resolve a number difference between Orbits and MotorsportReg, that choice also confirms the matching Speedhive row for that season.

Check points before making grids

Open Event → Entries and check Season Points for each rider and class. Expand a cell to read the source championship and fetch time, or the reason points are missing. The displayed total is the resolved value available to grids. A published zero appears as 0 points.

If no standings exist for the season, the page says so. This is a setup step, not a problem with each rider. Use Speedhive Setup to confirm class mappings and fetch standings.

For a missing value, the cell distinguishes an unmapped class, a class not fetched, and a rider absent from the championship. It also identifies name or number mismatches, ambiguous identities, incomplete identities, invalid links, unlinked rows, and missing totals. Read the cell's next action before correcting the source or refreshing standings. The Reviewed column in number reconciliation records that review decision; it does not report points resolution.

A later snapshot can omit a rider or have no resolved total. Grids and Entries then retain that rider's earlier resolved value. Check the fetch time in the cell before using it.

Live timing

Your club can link one Speedhive live event to one Race Control event. Timing then arrives while sessions run, and the public schedule updates to show what has finished.

The link is explicit and one event at a time. There is no club-wide automatic mode, and what the link reads is recorded so you can see and replay it.

This path uses a Speedhive web feed that MyLaps does not publish as a supported interface. Treat it as convenience, not as infrastructure: it is watched, it is replayable, and manual upload remains the fallback whenever it is wrong.

Live timing and grid readiness

Whether a live classification can order a grid is a separate choice, and it starts off.

When it is off, a live-only classification does not make a race ready and cannot supply qualifying order. Upload the Orbits file for that session and it does both. Live results, provisional sheets, and schedule updates keep working either way, so leaving it off costs you none of those.

An Orbits file makes a session qualifying-ready whatever the switch says, because a file you uploaded already outranks a feed.

What the choice depends on

This depends on your own uplink from Orbits to Speedhive, and on how well your club manages it.

Race Control reads what Speedhive publishes. Keep that link healthy and current, and the live classification matches the file you would upload. Let it lag or drop, and a grid built from it is built from the gap.

You know which of those describes your weekend. Race Control cannot.