Connection & Reader Setup

Platform: 📱 Mobile only

See also: Mobile App Setup, Local Server, Serial Settings

When you need this

You've arrived at the event venue and need to get your phone connected to a chip reader and the Navisport server before timing starts. Whether you're plugging in a USB reader, scanning a QR code to connect to a local server, or just checking that your cloud connection is solid — this page covers all the connection options.

Getting connections right before the first runner starts saves you from troubleshooting under pressure. Take two minutes to verify everything is green before the event begins.

QR code connection to a local server

When you're on the same WiFi network as a computer running the Navisport desktop client, you can connect directly to it over the local network. This gives you faster communication and works even without internet access.

How to connect:

  1. On the desktop client, open the local server panel — it displays a QR code
  2. On your phone, open the Navisport app's main menu (hamburger icon on the event list) and tap Connect to local server
  3. Point the camera at the QR code on the desktop screen
  4. The app reads the server address and connects automatically

Once connected, the app communicates directly with the desktop client over your local network (LAN) instead of routing through the cloud. This means lower latency and independence from internet connectivity.

The app remembers the local server address. If you restart the app or it returns from the background, it automatically reconnects to the same local server without needing to scan the QR code again. If the desktop client restarts with a new IP address, scan a new QR code to update the connection.

A toast notification confirms when the local connection is established, and the connection indicator changes from a WiFi icon to a server icon while connected locally.

Checking connection status:

Tap the connection icon (WiFi or server icon) on any timing screen to see connection details — whether you're connected to the cloud, to a local server, and the server's IP address. From this panel you can also disconnect from the local server and forget the saved address if you no longer need it.

Disconnecting from local server:

  1. Tap the connection icon on any timing screen
  2. The connection panel shows your current cloud and local server status
  3. Tap Disconnect and forget local server to clear the saved address and switch back to cloud-only communication

USB serial reader connection

The most common setup for chip timing: a USB reader connected to your Android phone via an OTG (On-The-Go) cable.

Connecting a reader:

  1. Plug the USB reader into your phone using an OTG adapter or cable
  2. Android shows a USB permission dialog — tap Allow to grant the app access
  3. The app detects the reader and shows a green USB indicator in the status bar (header or footer depending on the timing mode)
  4. Select the correct reader type (see below) if prompted

If the permission dialog doesn't appear, unplug and replug the cable. Some phones require you to unlock the screen first.

Reader types

When connecting a USB reader, select the type that matches your hardware:

Reader type When to use
EMIT USB Standard EMIT card reader connected via USB. The most common setup for EMIT-based events.
EMIT ECB/ETS EMIT base station (ECB) or ETS reader. Used for fixed installations or when reading from an EMIT timing station.
SportIdent SRR SportIdent short-range radio dongle. Receives wireless punches from SportIdent Air+ cards within radio range.
Huichang USB Huichang timing chip reader. Used with Huichang chip systems.

If you're unsure which type to select, check the label on your reader hardware or ask your equipment provider. Selecting the wrong type means the app can't interpret data from the reader — the USB indicator may still show green (it only indicates physical USB connection), but chip reads will fail silently or produce errors.

WiFi and cloud connection

The connection indicator tells you whether the app can reach the Navisport server:

  • Green — Connected. Results sync to the cloud in real time. Other devices and the desktop client see your data immediately.
  • Red — Offline. The app continues working normally — all timing data is saved locally. When connectivity returns, queued results sync automatically. You won't lose any data.

The app uses your phone's regular internet connection (WiFi or mobile data) to reach the cloud. If you're in a forest with poor reception, don't worry — just keep timing. Everything syncs when you're back in range.

Clock synchronization

Accurate time is critical for timing events. Even a 1-second drift between devices can affect results, especially when start and finish are recorded on different phones.

The app syncs its internal clock with the Navisport server to maintain accurate time. This happens automatically when the app connects and periodically while running. The server provides a reference time, and the app calculates the offset between the device clock and server time.

Manual sync:

If you want to force a clock sync — for example, right before an event starts — tap the clock display in the header bar of any timing mode. The app contacts the server and updates its time reference. A brief confirmation appears showing the sync result.

When clock sync matters most:

  • Events with separate start and finish devices (different phones recording start vs. finish times)
  • Long events where device clock drift could accumulate
  • Any situation where sub-second accuracy is important for results

If the server is unreachable (no connection), the app uses the device's system clock with zero offset. Make sure your phone's automatic time setting is enabled as a fallback.

Local server connection

When connected to a local server (via QR code scan), the app's communication path changes:

  • Without local server — The app sends data to the Navisport cloud, and the desktop client also syncs with the cloud. Communication goes: Phone → Cloud → Desktop.
  • With local server — The app sends data directly to the desktop client over the local network. Communication goes: Phone → Desktop (LAN). The desktop client then syncs to the cloud on its own.

Advantages of local server connection:

  • Faster data transfer (no round-trip to the cloud)
  • Works without internet — timing continues even if WiFi has no internet access
  • Lower latency for real-time result display on the desktop

When to use it:

Use a local server connection when you have a desktop client running at the venue and both devices are on the same network. This is the recommended setup for larger events where you want results appearing on the desktop instantly.

The local server connection doesn't replace the cloud — the desktop client still syncs to the cloud when internet is available. It just means your phone talks to the desktop directly instead of going through the cloud first.

Troubleshooting

USB reader shows red indicator

  • Unplug and replug the OTG cable
  • Check that you granted USB permission when prompted
  • Try a different OTG adapter — not all adapters work with all phones
  • Verify you selected the correct reader type
  • Restart the app if the reader was connected before the app launched

Cloud indicator stays red

  • Check that your phone has internet access (open a browser to verify)
  • If on WiFi, confirm the network has internet access (some venue networks are local-only)
  • Switch to mobile data temporarily to test
  • The app works fully offline — red cloud just means results won't sync until connectivity returns

QR code won't scan

  • Make sure the desktop client's local server is running
  • Check that both devices are on the same WiFi network
  • Ensure the QR code is fully visible and well-lit
  • Try moving closer to the screen displaying the QR code

Clock sync shows large offset

  • This usually means your phone's system clock is significantly wrong
  • Enable automatic time in your phone's date/time settings
  • Tap the clock display again to retry the clock sync
  • If the server is unreachable, ensure you have a connection (cloud or local server)

Tips

  • Always verify connections before the event starts. Green indicators for both USB and cloud mean you're ready.
  • For events without internet at the venue, set up a local server connection via QR code. You get full functionality without needing cloud access during the event.
  • If your USB reader disconnects during timing (cable gets bumped), just replug it. The app reconnects automatically and no data is lost.
  • Keep a spare OTG cable in your timing kit. Cable failures are the most common hardware issue at events.
  • Clock sync is most important when using multiple phones for the same event. If you're timing start and finish on separate devices, sync both clocks before the event begins.