TL;DR
To set up a RaceBox Mini S with Drivurs: charge + mount the device, grant Bluetooth permissions, close the official RaceBox app, then connect inside a Drivurs race session and wait for telemetry + GPS Ready before you run. If you get stuck on “Waiting for telemetry,” another app is usually holding the connection.
Common mistakes that cause bad data
- Running before GPS is ready
- Mounting where the device can’t see the sky (deep cup holders, glove box, under heavy tint)
- Leaving the official RaceBox app open (it can hold the telemetry connection)
- Comparing runs from different roads/directions/conditions and treating them as “gains”
- Changing mounting/position between runs and wondering why results drift
What you need
- A supported RaceBox device (Mini, Mini S, or Micro)
- A phone with Bluetooth enabled
- Drivurs installed
- A safe, legal place to test (empty road, closed course, or track—never public road racing)
Step 1: Mounting (the “silent” setup step)
GPS-based performance tracking depends heavily on mounting and sky visibility.
Basic mounting rules:
- Place the device where it has a clear view of the sky (dashboard, rear deck, or near the windshield)
- Avoid pockets, glove boxes, and deep cup holders
- Keep it stable—movement adds noise and confusion
If you’re running multiple tests, keep mounting consistent across sessions.
Step 2: Power and readiness
- Fully charge the RaceBox (low battery can cause unstable behavior).
- Turn it on and confirm it’s broadcasting Bluetooth.
If you’re unsure, verify you can see it in the device scan list (inside the Drivurs connect modal).
Step 3: Phone permissions (Bluetooth)
On iOS/Android, Bluetooth permissions can block scanning/connecting.
If Drivurs can’t find devices:
- Ensure Bluetooth is on
- Ensure Drivurs has Bluetooth permission
- On older Android versions, location permission can affect BLE scanning (depending on OS behavior)
Step 4: Close the official RaceBox app (important)
RaceBox telemetry over BLE is often “single-consumer” in practice: if the official RaceBox app (or another app) is connected, Drivurs may not receive telemetry reliably.
If you see this message in Drivurs:
- “Waiting for telemetry… Ensure the RaceBox app is fully closed”
…it’s a strong signal that another app is connected, or the connection is incomplete.
Step 5: Connect in Drivurs (in-app flow)
- Start a race session in Drivurs.
- Tap Connect.
- The RaceBox Devices modal opens and scans for devices.
- Select your device and tap Connect.
Once connected, Drivurs begins reading device info and subscribing to telemetry.
Step 6: Wait for “GPS Ready” before you run
Drivurs shows readiness states because runs built on stale or missing samples aren’t useful.
Common statuses:
- Connecting… (Drivurs is waking the device and starting telemetry)
- Waiting for telemetry… (no usable packets yet)
- GPS Not Ready (telemetry exists but fix quality isn’t sufficient)
- GPS Ready (ready to run)
If you’re stuck on “GPS Not Ready,” move to an open sky area and wait a bit. Urban canyons, heavy tint, garages, and tall trees can slow time-to-fix.
Optional: speed mode warnings (when Drivurs asks to change a setting)
Depending on your device and configuration, Drivurs may show a warning about a RaceBox speed mode setting (for example, “3D speed” vs ground speed).
Practical guidance:
- If Drivurs recommends a change for timing consistency, read the prompt and follow it if it matches your use case.
- If you’re unsure, leave the setting as-is, record a couple test runs, and focus on repeatability (same road, direction, and setup).
Avoid chasing settings as a substitute for good mounting and open sky view.
Step 7: Run a safe test and review
After a short test pull (in a safe location):
- Review the run and the session bests
- Watch for validation labels (valid / warnings / invalid / incomplete)
- If a run is flagged, treat it as “context,” not truth—improve conditions and try again
Consistency matters more than chasing a single hero run.
Troubleshooting (quick table)
| Symptom | Likely cause | Fix |
|---|---|---|
| Device not found | Permissions or Bluetooth off | Enable Bluetooth, grant permissions, rescan |
| Connect fails | Device in use / unstable state | Power-cycle device, try again |
| “Waiting for telemetry” | Official RaceBox app still connected | Fully close other apps; reconnect |
| “GPS Not Ready” for a long time | Poor sky view | Move to open sky; wait; avoid garages |
| Runs feel inconsistent | Mounting or conditions changed | Keep mounting + road + direction consistent |
Tips for better consistency (without over-claiming accuracy)
- Use the same road and direction (grade + wind matter).
- Wait for GPS readiness before each run.
- Keep mounting identical.
- Avoid heavy traffic and rapid lane changes.
Next steps (Drivurs)
- Feature page: RaceBox in Drivurs
- Use case: For Track Drivers
Related guides
- Pillar: Performance tracking for cars (GPS timing + validation)
- Same cluster: How accurate is GPS for racing apps?
- Same cluster: How does drag timing work in GPS-based apps?
- Different cluster: Should you use a build log or spreadsheet to track car mods?