Navisport Documentation

Before the Event (Desktop)

Step 1. Create the relay event

Create an event with competition format "relay". Set the number of legs and assign a course to each leg. Set the class default start time to the mass start time.

Step 2. Define teams

Import or enter teams. Each team has runners named for each leg. Ensure every runner has a valid chip number — missing chips show as "unknown" at the checkpoint.

Step 3. Define checkpoints

Go to the Checkpoints page and add a checkpoint. Enter a name (e.g., "Radio control") and the control code that matches the physical control in the terrain. Multiple checkpoints can be added — each needs its own phone.

Step 4. Plan device roles

One phone for the start (Automaton), one for the radio control (Online Control), one for the finish (Reader). Label the devices physically.

Race Day — Checkpoint Setup (Mobile)

Step 5. Place the phone at the radio control

Mount the phone in a waterproof case near the control flag. Connect the USB reader and verify the green indicator in the bottom bar.

Step 6. Switch to Online Control mode

Select the event → Online Control → select the checkpoint defined in step 3. The phone listens for punches and sends them to the cloud in real time.

Step 7. Check connectivity

Do a test punch and verify it appears in the Event Monitor. With weak signal, punches queue locally and send when signal returns — but real-time announcer use requires immediate transmission.

Race Day — Start and Finish (Mobile)

Step 8. Set up the start with Automaton

At the start line, switch to Automaton mode with start settings. In a mass start, a chip read registers the runner as "On course". The actual start time comes from the event's mass start time.

Step 9. Set up the finish with Reader

On the finish phone, open Reader → Finish tab.

Step 10. Record changeovers

A runner's finish recording automatically triggers the next leg's start time for that team. Reader shows the team name and completed leg for confirmation.

During the Race (Desktop)

Step 11. Monitor split times in Event Monitor

Split times appear in real time as runners pass the checkpoint. You can see team positions and gaps. The monitor updates automatically.

Step 12. Handle DSQ proposals

A missing punch or wrong control appears in the Event Monitor immediately. Handle it right away — the runner is likely still in the finish area. The same applies to checkpoint data: anomalies appear in the monitor immediately.

Step 13. Use the Announcer's Window

The Announcer's Window shows incoming split times and finish times in a large, easy-to-read format. The announcer sees gaps between teams and can report to spectators in real time.

Step 14. Track team progress

The Event Monitor shows each team's progress across all legs: runners on course, changeovers completed, and runners approaching the finish.

After the Event

Step 15. Collect devices and verify sync

Retrieve the phones and check sync status — keep them connected until all punches have been sent (zero pending transmissions).

Step 16. Back up and export results

Results have been on the public page throughout the race. Take a backup and export results in the required format (e.g., IOF XML for Eventor or IRMA).

Tips

Connect a power bank to the checkpoint phone — Online Control mode drains the battery continuously.
In weak mobile signal areas, consider a portable WiFi hotspot. Even weak 3G is enough for transmitting punch data.
Test the full chain before the race: punch at checkpoint → Event Monitor → Announcer's Window.
Multiple checkpoints can be set up — each needs its own phone and its own checkpoint definition.
Label phones physically (tape: "START", "FINISH", "CHECKPOINT").

Relay with Intermediate Timing