Offline
What keeps working on the hill without internet, and how the desk catches up when it is back.
What it's for
No internet on the hill is normal. Race Bureau is built so that a drop costs you nothing you cannot get back:
- The timing device keeps every press in its own memory, whatever the connection is doing. An FDS T-Box holds its current run; the timing box holds what its devices sent.
- The Race Bureau Timing app on this device (
/timing, installed from the browser) keeps the race on the device — competitors, the run 1 start list, the desk of every run, settings, devices, list formats, logos — and keeps timing while the connection is down. Every change you make and every impulse the device sends is kept on this device and sent, in order, when the internet is back. Nothing is drawn as done until the server confirms it. - The sync pill at the top of the Timing app says where things are: Connection, Timing desk (changes waiting), Timing devices (impulses waiting), Other changes, Last sent. A send that did not get through is tried again by itself.
- The gap fill compares the device's memory with what Race Bureau stored and brings in the presses the drop missed. Each press is judged at the moment it was taken: filed into the race and run that was green then; not stored if the light was red; never brought back if you deleted it; never taken from more than 15 minutes before the drop. A caught-up press is an ordinary impulse: nothing is assigned, reordered or calculated from it.
- The light stays green across a drop. With a timing box the desk stays open and green until the box has sent everything.
- A new version never reloads the app by itself. A pill says New version — reload when ready; nothing happens until you tap it.
The full desk in a browser tab (not the installed app) needs the connection: it shows the last confirmed state while the connection is down and catches up when it returns.
Before you start
- The race put on the device under This device › Race on this device, and the checklist reading Ready to time offline. See Race on this device.
Steps
- Before you leave internet, open Race on this device and press Update now. Leave Keep this race on this device ticked.
- Time the race as usual. The sync pill shows what is waiting to send.
- When the internet is back, watch Last sent on the sync pill move and Waiting to send fall to 0.
- If the device was cut off from the desk during the race, run the gap fill on the device's row (TBC: the exact button on the Timing devices screen that fills the gap since the last stored impulse).
What success looks like
After the drop, Data Management holds every finish, the sync pill says nothing is waiting, and no impulse taken while the light was green is missing.
If something goes wrong
- The last send did not get through: it is retried by itself, in order. Leave the device online.
- Not ready to time offline — Run 1 start list: No start list yet: draw run 1 online first, then Update now.
- A press from before the drop is missing: the gap fill takes only presses newer than the last one Race Bureau stored on that channel, and nothing older than 15 minutes before the drop. Older presses stay on the device; read them off the device's times list and enter the time with Modify data.
Related
- Previous: Import a run
- Next: Race on this device
- How it fits: Timing devices, from the box to the desk
- Backups and USB export
- The traffic light
Was this helpful?