Connect Open Live Timing to RMonitor

Your timing software already sends the classification to scoreboards through its RMonitor output. A small agent on the timing PC, or on a mini PC on the same network, reads that output and publishes a free live timing page for drivers, teams and spectators. Nothing changes in the way you time the sessions.

Compatible with MYLAPS Orbits, Westhold Race Manager, TAG Heuer Elite, any software with an RMonitor (AMB) scoreboard output.

Start
  1. 1

    Create your account

    Sign in, or create a free account with your e-mail address, Google or a passkey.

  2. 2

    Choose the live timing page

    Each live timing page has its own address (olt.live/lt/your-track). Use one you already have or create one for your track, club or event.

    Sign in first: your live timing pages show here.

  3. 3

    Install the agent

    On the timing PC (Windows) or on a mini PC on the same network (Linux x64 or ARM64, such as a Raspberry Pi). One executable, nothing else to install; it only needs an internet connection going out.

    The agent is in early access: write to info@openlivetiming.com and we send it to you.
    Windows: install as a service
    • In the folder of the agent, in PowerShell run as administrator (with the pairing code of step 5):
    • The service starts with Windows and restarts after a failure. -Uninstall removes it.
    .\install-agent-windows.ps1 -Code ABCD-EFGH -Source 127.0.0.1:50000
    Linux mini PC
    • Unpack the Linux archive (x64 or arm64) in a folder of the mini PC, then:
    • Needs OpenSSL and CA certificates, present on any standard installation (sudo apt install libssl3 ca-certificates on a minimal one).
    ./olt-agent pair --code ABCD-EFGH --source 192.168.1.20:50000
    ./olt-agent
    Linux mini PC with Docker
    • With the agent.compose.yml file of the agent, in a folder of the mini PC:
    docker compose -f agent.compose.yml run --rm agent pair --code ABCD-EFGH --source 192.168.1.20:50000 --config /data/agent.json
    docker compose -f agent.compose.yml up -d
  4. 4

    Enable the scoreboard output

    In the timing software, turn on the RMonitor scoreboard output (TCP, port 50000 by default) or a serial output. Note the address and port.

    MYLAPS Orbits
    • Open the settings of the scoreboard output (RMonitor) and enable it; its TCP port is 50000 by default.
    • If the agent runs on the timing PC itself, the source is 127.0.0.1:50000; from a mini PC, use the address of the timing PC on the network.
    • Allow the port in the Windows firewall of the timing PC when the agent runs on another computer.
    Westhold Race Manager, TAG Heuer Elite and others
    • Look for the scoreboard output in the settings and choose the RMonitor (AMB) format, over TCP or a serial port.
    • A serial output works with a USB adapter: the source is then serial://COM3 on Windows or serial:///dev/ttyUSB0 on Linux (9600 baud by default, ?baud= to change it).
    • Not sure where the setting is? Write to info@openlivetiming.com with the name and version of your software.
  5. 5

    Pair the agent

    On the page of the agent in your back office, accept the terms and create a pairing code (valid 10 minutes, once). Give it to the agent with the address of the output.

    olt-agent pair --code ABCD-EFGH --source 127.0.0.1:50000 --server https://openlivetiming.com
    olt-agent
  6. 6

    Check and share

    The back office shows the agent online, connected to the timing software, with the current session. Then share the live page: its link, and the embed code for your website.

What the live page shows

  • Positions, laps, last and best lap, gaps and intervals, classes
  • Flags (green, yellow, red, checkered) and the time or laps to go
  • Finishers, and every session archived as published results
  • Sector times when the software sends its intermediate lines (IMSA format)
  • Push notifications, the big screen leaderboard and the embed for your website

Good to know

  • The agent reads the output only: it never writes to the timing software, and the timing stays yours.
  • The page shows what the software sends: names and classes as entered, no data from the transponders themselves.
  • A connection drop at the track pauses the live page; it catches up with the classification when the connection comes back.

Questions

Is it really free?

Yes. Open Live Timing is free for clubs, circuits and organisers: the live timing page, the agent, the results and the notifications.

Does the agent change anything on the timing PC?

No. It connects to the scoreboard output like a scoreboard would and only reads it. It can also run on a separate mini PC.

Can my scoreboard keep working at the same time?

The agent is one more client of the output. Most outputs accept several clients; if yours accepts only one, write to info@openlivetiming.com and we will find a setup with you.

Has it been tested with my software?

The agent was built and tested on recorded RMonitor feeds and on a simulator. We are looking for clubs to test it during their events: write to info@openlivetiming.com.

Who may publish the timing of a meeting?

The organiser of the sessions, or someone they authorized (circuit, series, timekeeper). The terms are accepted in the back office before the first pairing.

What happens if I revoke the agent?

Its key stops working at once: the agent stops publishing. Create a new code to pair it again.

Product names are trademarks of their respective owners. Open Live Timing is not affiliated with, endorsed or sponsored by them; the names only describe compatibility.

An unhandled error has occurred. Reload 🗙