Esta página solo está disponible en inglés.

Guide

Phone GPS vs RaceBox: what accuracy you actually get

You don't need hardware to start — and it's worth knowing exactly what hardware buys you when you're ready. The honest version, with numbers.

What your phone gives you

A phone fixes about once a second. In a kart that's a point every 15 to 30 meters — more in a car. That's enough to time laps, draw your racing line, find the corners, and name the one that cost you the most. Hit Record in LapperSnapper and that's a full session — the complete analysis, not a preview.

What 25 Hz sharpens

A RaceBox (Mini, Mini S, or Micro) samples 25 times a second — a point roughly every meter at kart speeds — and carries an accelerometer and gyro besides. Apex speeds stop being estimates between fixes, sector deltas tighten, and braking points land where they actually happened. The verdict rarely changes; the resolution does.

At a glance
Fix rate  — phone ~1 per second · RaceBox 25 per second
Point spacing in a kart  — 15–30 m · about 1 m
Extra channels  — none · accelerometer + gyro
Lap times, line, corner detection  — both, same engine

Getting RaceBox data in

LapperSnapper connects to the RaceBox over Bluetooth: record live, or — on a Mini S or Micro — download the onboard recordings straight off the device, split into one session per run, and pick the runs you want. No other app in the loop. Prefer files? A .ubx shares straight to LapperSnapper or loads from Files. Same engine as every other source: line, sectors, ultimate lap, corner losses, traction.

So which should you run?

Start with the phone — it's free and already in your pocket. Upgrade when tenths matter: if you're chasing apex-speed deficits and sector-level habits across sessions, 25 Hz is the difference between roughly-there and exactly-there. The logger raises the resolution, not the verdict.

See every way data gets in