Navisport Documentation

The scenario

You're running a medium-sized orienteering race where the finish line is 500 meters from the event center. You don't have enough volunteers to staff the finish, so you set up a phone running Automaton in Finish mode. It records times automatically, gives audio feedback to runners, and you monitor everything remotely from the desktop.

Before the event (Desktop)

Step 1. Create the event and set up classes

Create your event on the desktop as usual — set up classes, courses, and import registrations. Assign start times if it's an individual start event. Everything here is standard race setup.

The key difference from a normal race is that you won't have a person at the finish to handle problems in real time. This means your preparation needs to be more thorough — fewer loose ends means fewer issues during the race.

Step 2. Verify all registrations have chip numbers

Since the finish is unattended, there's no human to handle "unknown chip" situations gracefully. Go through your registration list and make sure every participant has a valid chip number assigned. Flag any missing ones and contact those participants before race day.

Step 3. Plan your finish line hardware

You'll need: one Android phone with the Navisport app, one USB chip reader, a waterproof case or shelter, a power bank (the phone will run for several hours), and optionally a Bluetooth speaker for louder audio feedback.

Finish line setup (Mobile)

Step 4. Mount the phone at the finish

Arrive early and set up the finish station. Mount the phone where runners can easily reach the chip reader — typically on a table or post at waist height. Make sure the USB reader cable has enough slack that runners don't pull the phone off its mount.

Step 5. Enter Automaton Finish mode

Open the app, select your event, and choose Automaton mode. Select Finish as the role. The phone is now in fully automatic mode — every chip read is saved immediately without any manual confirmation.

The Automaton screen shows a large display with the last recorded result. This serves as visual confirmation for runners that their finish was registered.

Step 6. Configure audio and display settings

Turn on speech so the phone announces each runner's name and time aloud when they finish. This gives runners immediate feedback even though no official is present. The app automatically keeps the screen on while running, so you don't need to worry about the screen locking mid-race.

Step 7. Test the setup

Read a test chip to verify everything works: the phone should announce the name, show the result on screen, and sync it to the cloud. Check the Event Monitor on desktop to confirm the test result appeared. Then delete the test entry.

Step 8. Secure the station

Make sure the phone is protected from weather and won't be knocked over by tired runners. A simple plastic box with a slot for the reader cable works well. Ensure the power bank is connected and the phone has good mobile signal.

During the race

Step 9. Runners finish and get automatic feedback

As runners cross the finish and read their chip, the Automaton saves their time instantly. The phone announces their name and elapsed time via speech. The screen shows a confirmation with their result. No human interaction needed.

Step 10. Monitor remotely from Event Monitor

At the event center, keep the Event Monitor open on the desktop. You'll see finish times appearing in real time as runners complete the course. This lets you track progress without being physically at the finish line.

Set up a simple checklist: compare the number of finishers with the number of starters at regular intervals. If the gap grows unexpectedly, something might be wrong at the finish station.

Step 11. Handle DSQ proposals as results come in

When a runner's chip data shows a mispunch, the Event Monitor flags it immediately — just like in any other race. Handle these in real time as each result arrives. The runner may still be at the finish area reading the confirmation screen, so if you need to check their chip data, you have a window to reach them or radio someone nearby.

Step 12. Watch for operational issues

Keep an eye out for: gaps where you expected finishes (might indicate a phone problem), "unknown chip" entries (a runner whose chip isn't in the system), or a sudden stop in incoming results (could mean the phone lost power or connectivity).

Handling issues

Step 13. What if WiFi or mobile data drops

The Automaton continues recording times locally even without connectivity. Results queue up and sync automatically when the connection returns. You won't see them in Event Monitor during the outage, but no data is lost.

Step 14. What if an unknown chip is read

The Automaton still records the time with the chip number, even if it can't match it to a participant. You'll see these as "unknown chip" entries in the monitor. In most cases you can identify the runner from context (expected finish window, chip number lookup) — but since the finish is unattended, this may need to wait until you collect the phone.

Step 15. What if you need to intervene

If something goes wrong (phone falls, reader disconnects), go to the finish station and fix the issue. The Automaton resumes automatically once the reader is reconnected. Any reads that happened while the reader was disconnected are lost — but the phone shows the last successful read time so you know when the gap started.

After the event

Step 16. Collect the phone and confirm sync

Once all runners are accounted for, go to the finish station and collect the phone. Check the sync status in the app — if there are pending uploads, keep the phone connected until everything is synced.

Step 17. Take a backup and export

Back at the desktop, results have been live throughout the event. Any unknown chip reads that were recorded during the race can be matched to participants if needed — the timestamp and chip number are preserved — but this is typically a minor cleanup item.

Take a backup of the event data and export results to your federation's system if needed. Share the results link with participants.

Tips

Always do a full test run the evening before or morning of the event. Walk through the entire flow: chip read → voice announcement → Event Monitor update.
Bring a backup phone with the app installed. If the primary phone fails, you can swap in the backup and continue timing with minimal interruption.
A Bluetooth speaker makes the voice announcements audible even in windy conditions. The phone's built-in speaker is often too quiet outdoors.
Set the phone's screen brightness to maximum so runners can read their result in direct sunlight.
If the finish is in a cellular dead zone, consider a portable WiFi hotspot with a better antenna. Real-time monitoring only works if data reaches the cloud.
Tell runners at the start briefing that the finish is automated — "read your chip and wait for the beep, then you're done." This avoids confusion when they don't see a person at the finish.
Place a visible sign at the finish explaining the process: "Read your chip on the reader. Wait for the beep. Your time is recorded." This helps runners who missed the briefing.
Check the phone's temperature if it's a hot day. Direct sunlight can cause overheating and automatic shutdown. A shade cover or reflective material helps.

Unattended Finish with Automaton