NSAT support.
Where are you stuck?

Work through these in order:

1. Confirm the RaceBox is powered on and its light indicates it's awake. A unit that has been in a bag for months is usually flat.
2. Check that Bluetooth is on in iOS Settings, and that NSAT has Bluetooth permission (Settings › NSAT › Bluetooth).
3. Make sure no other app or device is already connected to that RaceBox — the official RaceBox app, another phone, a laptop. It accepts one connection at a time.
4. Move the phone within a few feet of the receiver and scan again.

If the RaceBox appears in the official RaceBox app but not in NSAT, disconnect it there first and rescan.

NSAT reconnects on its own. You'll see a brief reconnecting indicator rather than being thrown back to the scan screen, and race state is preserved while it does.

If it doesn't come back within a minute, the usual causes are a flat receiver battery or the receiver having gone to sleep. Power-cycle the RaceBox and NSAT will pick it up again.

RaceBox Mini, RaceBox Mini S, and RaceBox Micro. NSAT reads their 25 Hz data stream directly.

The iPhone's own GPS is not used for timing and can't substitute — it isn't accurate or fast enough to place a finish line to the millisecond.

No. NSAT makes no network connections at all. Everything it needs arrives over Bluetooth from the receiver, and everything it saves stays on your device. Airplane mode with Bluetooth on works fine, and is a reasonable way to keep calls from interrupting a run.

Almost always sky view. The receiver needs a clear, wide look at the sky — not the phone, the receiver.

• Put the RaceBox high on the dash or on the roof, away from the windshield frame.
• Metallic or heat-reflective windshield tint blocks satellite signal badly. Many modern cars have it. If in doubt, try the roof.
• Roof racks, light bars, and overhanging trees all hurt.
• A receiver that hasn't been used in a while, or has traveled a long distance since it last had a fix, takes longer on its first acquisition. Give it several minutes outdoors.

A clear-sky cold start usually completes in a minute or two.

That threshold is intentionally strict, because horizontal accuracy sets the outer bound on how precisely NSAT can time your crossing. A receiver reporting two-meter accuracy cannot place a finish line to the millisecond, and the app won't pretend otherwise.

Improve the sky view and give it another minute. Accuracy typically keeps tightening for a while after the first 3D fix appears.

The receiver reporting that its clock has resolved to nanosecond precision. NSAT interpolates the start and finish moments between GPS readings, and that arithmetic is only trustworthy once the receiver's own time is fully resolved.

It's the last item to turn green, and it can lag the others by a short while. Nothing is wrong if the first three pass and this one takes a bit longer.

Correct — that's the design. You set a start time and NSAT starts itself when the GPS clock reaches it, so the clock matches the official time you were assigned rather than your thumb.

Set the start time as the very last thing you do before the run.

This is a safety feature, not a bug. Two things push it out to at least four minutes ahead:

• Opening and then closing the course list, run log, or guide. The timer can't start while one of those is open, so closing one resets the start to a safe distance.
• A GPS sync that took longer than the initial buffer.

Do your setup first — course, target speed, GPS offset — then set the start time last and leave the screen alone.

Every time NSAT shows is UTC, taken from the GPS satellites, because that's how open-road events publish start times. It is not your local clock and doesn't shift with daylight saving.

Convert your assigned start time to UTC before entering it.

The distance from the RaceBox antenna back to the front bumper, measured along the length of the car, in feet. Adjustable from 0 to 22 feet in half-foot steps.

NSAT shifts the finish threshold by that amount so the clock stops when your nose reaches the line, not when the receiver on your dash does. Measure it once for the car and it's remembered.

Green with down arrows means you're ahead of pace — running fast, arriving early. Red with up arrows means you're behind pace and need to make time up.

The number compares you against a car running your target speed exactly, the whole way. The goal is zero at the line, from either direction.

It's hidden in two situations, both on purpose:

• Before five miles. Early in a run the figure swings wildly on small errors and would send you chasing noise.
• Inside the final minute. At that point a correction can't be made safely or usefully, so the number goes away rather than tempting you.

In between, it shows the average speed that lands you at exactly zero variance.

Intentional. NSAT forces maximum brightness and prevents auto-lock so the display stays readable in direct desert sun. Your normal brightness returns when you leave the app.

Run the phone on a charger — full brightness plus a constant Bluetooth stream is hard on a battery over a long day.

NSAT silences notification banners and sounds while it's in the foreground. For a phone call, or anything else that could pull you out of the app mid-run, turn on Do Not Disturb (or a Focus mode) before you stage. Leaving the app during a run ends the run — see below.

NSAT stops when your position crosses the finish coordinate in the course's configured direction of travel. If either the coordinate or the direction is wrong for the leg you ran, the crossing never registers.

Check the finish-line card on the dashboard before a run — it shows exactly what the app is watching for: the axis (latitude or longitude), the threshold coordinate, and the travel direction. A southbound leg selected as northbound will not stop.

The GPS fix dropped out within two miles of the finish and stayed out for four seconds or more — typically an underpass, a cut, or a canyon wall. Rather than record nothing, NSAT projects your last known speed to the line and saves that time, labeled clearly so you always know which results were measured and which were estimated.

The app was left during the run — Home button, app switcher, or another app taking over. That's treated as an emergency stop: the elapsed time is captured and saved to the log, and the app exits. A run can't be resumed after that.

To avoid it, turn on Do Not Disturb before staging and don't touch the phone during the run.

When an event runs multiple legs, only the total matters. If leg one finished twelve seconds slow, turn on the variance offset before leg two and the display will pace you twelve seconds fast — so driving the second leg "to zero" cancels the first.

It changes only what the display asks of you. Each run is still logged and scored against the true target. The toggle turns itself off after the run so it can't quietly carry into a third leg.

Open the run log and tap the share icon. NSAT exports every run as a CSV file — course, date, UTC start time, start and finish coordinates, distances, target and actual and top speeds, times, variance, and how each run ended.

The log files are also visible in the iOS Files app under NSAT's folder, and through Finder when the phone is connected to a computer.

No. Courses, run log, target speed, and GPS offset are stored on the device and survive updates. Deleting the app removes them, so export the CSV first if a run history matters to you.