Race Control Bridge reads timing from Orbits on your track computer. It sends those observations to your organization in Race Control. Your computer starts the connection. Race Control does not connect into the track network.

Create a bridge

An organization Admin creates and configures a bridge. Other organization members can read its status.

  1. Open Setup › Integrations › Bridges.
  2. Select Create Bridge.
  3. Enter a name that identifies the track computer.
  4. Select Create Bridge in the dialog.
  5. Copy the Race Control Bridge Token before you close the dialog.

The token appears once. Keep it private. It connects this track computer to your organization across events. Keep the same token for later weekends. If you lose the token, revoke the bridge and create another bridge.

Connect Orbits

Install Race Control Bridge on a Windows computer that can reach Orbits. Download the Windows installer, then run it. Windows installs the app as LapBrain Race Control Bridge. Open that name from the Start menu. The app window title includes the installed version.

  1. Open Connection in the desktop app.
  2. Enter your Bridge Token.
  3. Select the network adapter that can reach Orbits.
  4. Select Discover Orbits or enter the Orbits host and port.
  5. Save the connection, open Bridge, and select Start Bridge.

The desktop app connects to Race Control automatically. There is no server address to enter.

Check the organization, Current Orbits Event, and Current Race Control Event that the app shows. Race Control selects the destination from the source event and the organization schedule. Check the destination dates when rounds share a name. Waiting for Event is normal before timing starts. If an event match needs review, the app shows the source and its reason.

If the destination needs review or Orbits recreates its runs, open Review Bridge timing to check the event and session matches.

The desktop app keeps the token in protected Windows storage. Use Diagnostics to review recent connection messages and available updates.

Observe Only collects timing without changing results. After a restart or update, the Bridge can wait briefly for its previous connection to expire. It retries automatically. You can leave the app open. If Another Bridge is connected stays visible, check the connection details shown with the warning and close the other Bridge using this token. Use a separate bridge and token for each timing computer.

The app keeps its Orbits connection open between timing reads. It uses small event and run lists to discover changes, and limits background reads so active timing takes priority. It still checks earlier sessions for corrections. Initial catch-up can take longer because the Bridge limits those reads.

After a lost connection, it reconnects and reads complete timing again. Check its last successful read and upload in Bridge. Open Diagnostics if collection does not resume. Diagnostics also summarizes Orbits connections, traffic and view requests. The website's Bridge Version shows the installed version when reported; Not Reported alone does not mean the Bridge is disconnected.

The Bridges list and each bridge's status page update automatically every five seconds. Updates wait while you edit or use a menu or dialog, then catch up automatically. Your filters and mapping drafts stay in place, and status reads leave the timing controls available. A failed read keeps the previous status and shows the error until the next successful update.

Display refresh and timing application are separate. Observe Only keeps collecting observations without applying timing to sessions.

Read Bridge traffic

The Bridges list shows requests per second and data sent to Orbits from the latest five-second measurement, such as 2.4 req/s · 18.6 KB/s. Transfer rates use decimal units: 1,000 KB/s is 1 MB/s. These are Orbits rates, separate from uploads to Race Control.

Select the Bridge name and open Traffic to see request and transfer graphs. The transfer graph separates data sent to Orbits from data received from Orbits. Choose 15 Minutes, 1 Hour, or 24 Hours. The default is one hour. The graphs update automatically every five seconds. Your selected range and open measurement details stay in place while traffic changes.

Not Reported means no measurement is available. A measurement older than 15 seconds is marked Stale. Its measured time and received time are separate: a delayed upload does not make old traffic current.

Fine measurements remain for one hour. Older measurements become minute summaries, retained through 24 hours. Each summary shows its average and minimum-to-maximum band. Open Traffic Measurements for each interval's values, standard deviation, sample count and covered seconds. Partial coverage and blank gaps mean missing measurements, not zero traffic. A failed refresh keeps the last successful graph and its displayed range.

System administrators can open an organization's Bridges from their console and expand Technical Logs on a selected Bridge. These are original Bridge messages with measured and received times, version and session details. Pages contain up to 100 records, newest first; logs remain for 30 days. Organization members and impersonated sessions cannot read these logs.

Bridge software updates

Keep Windows signed in and leave the desktop app open to receive updates. The Bridge downloads and checks new versions in the background. It waits until the event ends before installing an automatic update. A break between races, a stopped Bridge or a lost connection does not end that protection.

Installation briefly pauses collection. The app restarts with its saved connection. If the Bridge was running before the update, it starts again. If you had stopped it, it stays stopped. After reconnection, it checks complete timing from Orbits again. Timing already received by Race Control remains available.

If diagnostics cannot be saved to disk, installation waits. Open Diagnostics to read the storage error. Installation can continue after the disk problem is resolved.

An organization Admin can update during an event:

  1. Open Setup › Integrations › Bridges and select the bridge's name.
  2. Check the installed and available versions.
  3. Select Update Now and confirm the interruption.
  4. Watch Update Status until the new version and Bridge state are confirmed.

An offline request waits for the desktop app to connect. Requests expire if the Bridge does not accept them in time. Check the status before trying again. Older Bridge versions need a local installation to enable remote updates.

Recover a previous version

The Bridge keeps a verified working version on the timing computer. If installation or startup fails, a recovery helper restores that version and the previous running or stopped state. It does not need a new download. The failed release stays blocked from automatic installation. An Admin can select Update Now to install that version again. A lost internet or Orbits connection alone does not cause a rollback.

An Admin can select Roll Back on the bridge's website page when a retained previous version is available. Confirm the interruption, then check Update Status and the installed version. Use this action if a new version starts but does not work correctly.

The website updates status automatically while preserving your current task. Update Now and Roll Back change the software on the timing computer.

Review runs

See Review Bridge timing for the steps.

Resolve a run match

See Review Bridge timing.

Enable automatic timing

See Review Bridge timing for the steps.

Catch up missed sessions

See Review Bridge timing for the steps.

For a corrected completed session or an earlier event, use Sync selected sessions. It requests a finite background read while the Bridge continues live timing.

Watch Live Timing

The public Live Timing page follows the event through each session. Its button appears beside the event on the home page and on the event page when this Bridge is enabled, receiving timing, and near a scheduled session. An active session keeps it available even when running late.

The page updates about every five seconds during an active session. It checks about once a minute while waiting or offline, keeps the last timing visible, and resumes faster updates when a healthy active session appears. What riders see explains the page and its links.

Revoke a token

Revocation stops this bridge from uploading timing. Select Revoke Bridge Token on the named bridge, then confirm the action. Previously received observations remain available. Create another bridge to connect again with a new token.