Racing turns telemetry into validated, readable run history.
Use this hub to understand Drivurs sessions, Auto Track vs manual mode, run validity labels, run viewer graphs, uploads, and the leaderboard model.
- Auto Track
- Manual sessions
- Validity labels
- Leaderboards
Guides
6 pages
Racing and timing guides
This hub includes new racing guides plus the legacy data-logging device/setup articles.
Validity
4 labels
Valid, warnings, invalid, incomplete
Runs need readable quality state before they belong in history or leaderboards.
Surfaces
Session -> Viewer -> Board
One continuity chain
Run details and rankings should share the same underlying truth instead of separate promo abstractions.
Start here
Open the right surface first
These cards anchor the live app workflow and the most relevant guides for this hub.
Session model
Pick the right session mode up front
The product supports automatic and manual session behavior because they solve different timing workflows. The UI should explain that clearly.
Quality model
Make run validity legible
Users need to understand why a run is valid, warned, invalid, or incomplete before they trust comparisons or best-time summaries.
Viewer + boards
Keep uploads and rankings attached to the same run truth
Run viewer graphs, uploaded sessions, and leaderboard entries should all point back to the same recorded session and vehicle identity.
Core guides
Racing guides
Start with session mode and validity, then move into graph interpretation and upload behavior.
Auto Track vs manual sessions in Drivurs
How to choose between Drivurs Auto Track and manual session mode, and why both exist in the live racing workflow.
Read guide →
What do valid, warning, invalid, and incomplete runs mean in Drivurs?
A practical guide to Drivurs run validity labels so users can tell when a run belongs in comparisons, history, or leaderboards.
Read guide →
How do the run viewer and leaderboards connect in Drivurs?
Why the run viewer, uploaded sessions, and leaderboards should read as one truth layer instead of separate racing surfaces.
Read guide →
Legacy collection
Data logging guides kept live in phase one
These URLs stay stable, but new editorial investment should go into Racing.
How accurate is GPS for racing apps? (What to look for)
A practical guide to GPS accuracy for racing apps: fix quality, sample rate, mounting, environment, and how to get more consistent runs.
Read guide →
How do you set up a RaceBox Mini S with Drivurs? (Setup guide)
A step-by-step RaceBox Mini S setup guide for Drivurs: mounting, Bluetooth permissions, connection flow, GPS readiness, and troubleshooting.
Read guide →
Get early access
Use Racing when the question is about session truth, not generic performance talk.
The session flow, run viewer, upload model, and leaderboards should read as one coherent system tied back to a vehicle.