GoMango logo GoMango Timing Help Timing · LiveTiming · Announcer
🔍
LiveTiming app

Using LiveTiming

Publishing live results from Timing to your event website.

What it does

LiveTiming has one job: watch the event running in Timing and push every run — as it happens — to a website, so people not at the event can follow results online in real time. There's nothing to configure in LiveTiming itself; the destination website is set once, in Timing's Preferences under Live Timing Site.

Starting it

  1. Make sure Timing is already running on the network (see Event-Day Quick Start).
  2. Launch LiveTiming. It broadcasts a request on the local network and connects to Timing automatically — there's no login or address to type in.
  3. If it can't find Timing, it shows this computer's IP address (or addresses) and asks whether to keep retrying or close. Select OK to try again once Timing is confirmed running, or see Troubleshooting.

The window while it's running

LiveTiming's window is intentionally minimal: a scrolling message log of what it's doing (connecting, sending each run, any failures reaching the website) and a Reset button.

When to use Reset
Select Reset to re-send the complete current state of the event to the website — useful if the website's results look out of sync (for example, after a network hiccup, or if Timing's data was corrected while LiveTiming was briefly disconnected).

What gets sent

For every run added, updated, or deleted in Timing, LiveTiming sends the driver, class, index, run number, time, splits, cone/gate counts, DNF status, and heat name to the website, along with an overall index/PAX summary when the event uses indexing. If the website is briefly unreachable, updates queue up and send in order once it's reachable again.