Navisport Documentation

Before the Event (Desktop)

Step 1. Create the event and define classes

Create the event as normal — classes, courses, registrations, start times. With an unattended finish, preparation must be more thorough because there is no person on site to handle problems.

Step 2. Verify chip numbers

Go through the registration list and ensure every participant has a valid chip number. In an unattended finish, nobody handles "unknown chip" situations in real time.

Step 3. Plan the finish hardware

You need: an Android phone or tablet with the Navisport app, a USB reader, and a power bank. In rain, a waterproof case; outdoors, a Bluetooth speaker for audio feedback.

Finish Setup (Mobile)

Step 4. Mount the phone at the finish

Install the phone where runners can easily reach the reader — typically at waist height. Ensure sufficient slack in the USB cable.

Step 5. Switch to Automaton

Select the event and switch to Automaton → role Finish. Every chip read is saved automatically without manual confirmation. The screen shows the most recent result as visual confirmation for runners.

Step 6. Configure audio and display settings

Turn on speech synthesis — the phone announces each runner's name and time aloud. The app keeps the screen on automatically.

Step 7. Test the setup

Read a test chip. Verify: speech synthesis announcement, result on screen, sync to Event Monitor. Remove the test entry.

Step 8. Secure the station

Protect the phone from weather and bumps (a plastic box works well). Connect the power bank and verify mobile signal.

During the Race

Step 9. Automatic finish recording

Runners read their chip → Automaton saves the time → phone announces name and time → screen shows confirmation. No human action needed.

Step 10. Monitor remotely from Event Monitor

Keep the Event Monitor open on the desktop. Finish times appear in real time. Compare the number of finishers to starters at regular intervals — a growing gap may indicate a problem at the finish.

Step 11. Handle DSQ proposals

Missing punches appear in the Event Monitor immediately. The runner may still be in the finish area, so there is a time window to act.

Step 12. Watch for operational issues

Monitor for: pauses in finishers (phone problem?), "unknown chip" entries, sudden stop of results (power or connection lost?).

Troubleshooting

Step 13. Connection loss

Automaton continues recording times locally. Results sync automatically when the connection returns. No data is lost.

Step 14. Unknown chip

Automaton records the time with the chip number even if the participant is not identified. These appear in the monitor and can be matched afterwards.

Step 15. Physical problem

Automaton continues automatically after the reader is reconnected. Punches during disconnection are lost — the time of the last successful punch is shown on screen.

After the Event

Step 16. Retrieve the phone and verify sync

Check the sync status — keep the phone connected until everything has been sent.

Step 17. Back up and export results

Match any unknown chip punches to participants if needed (timestamp and chip number are preserved). Take a backup and export results.

Tips

Do a full test run before the event: chip read → speech synthesis announcement → Event Monitor update.
Bring a backup phone with the app installed.
A Bluetooth speaker makes announcements audible in windy conditions.
In areas with poor mobile coverage, consider a portable WiFi hotspot.
Tell runners at the start briefing: "Read your chip and wait for the beep."
Post a sign at the finish: "Read your chip on the reader. Wait for the beep. Your time has been recorded."

Unattended Finish with Automaton