Start with your phone. Add hardware when it pays off.
Everything TRACK needs is already in your phone. Connect adds precision GPS for tighter timing, cameras for better onboards and OBD-II for engine data, and tells you plainly which devices are tested and which aren’t yet.
- 25 Hz
- precision GPS support
- 8
- GoPro models supported
- iPhone + Android
- compatibility shown per device
RaceBox Mini S, awaiting hardware validation.
Control and sync for HERO9–13 and MAX2; file import for older models.
The Android app is planned.
05TRACK Connect · hardware
Start with your phone. Add hardware when it pays off.
We list exactly what works today and what doesn’t. No universal OBD claims. If a device hasn’t been tested on real hardware yet, we say so.
- ANothing to buy
iPhone only
- GPS ~1 Hz · IMU up to 100 Hz · cameraBuiltBuilt-in. On-device validation pending
- BRoad-car engine data
OBD-II adapters
- ELM327-compatible BLE adaptersDevice-dependentWorks only with documented BLE services; results shown per device
- ELM327 Wi-Fi adaptersIn development
- OBDLink CXPlannedPending vendor documentation
- OBDLink MX+PlannedNeeds vendor approval for iOS
- Classic-Bluetooth ELM327 clonesNot supported on iOSiOS does not expose Bluetooth serial
- C10–25 Hz position
Precision GNSS
- RaceBox Mini / Mini SAwaiting hardware validationDecoder built from the published protocol
- DRead-only gateways
Pro CAN / ECU
- Motorsport CAN gatewaysPlannedRead-only, user-mapped channels. Never writes to an ECU
- EExtra angles
Camera nodes
- Spare iPhone as a camera nodePlannedRecords locally, transfers after the session
OBD-II reports RPM, speed and temperatures at a few Hz per value. Its “throttle position” is the ECU’s throttle-plate reading, not your pedal, and TRACK labels it that way. Product names describe compatibility only and imply no partnership or endorsement.
25 Hz ≠ accurate.
Sample rate is how often you get a position. Accuracy is how close each one is. A fast receiver with poor accuracy is still off, just more often. TRACK reports both, and every lap carries its own timing uncertainty.
- Phone 1 Hz
- 0.037 s
- median lap-time error
- External 25 Hz
- 0.007 s
- median lap-time error
Simulation benchmark vs. simulated ground truth · not yet validated on track
01How it works
How it works
- 01
Phone only
GPS around 1 Hz, motion sensors up to 100 Hz and the camera: enough to time and coach.
- 02
Add precision
A 25 Hz GPS receiver sharpens timing, delta and traces.
- 03
Add engine data
An OBD-II adapter adds RPM, temperatures and more, depending on your car.
- 04
Add cameras
A GoPro gives a sharper onboard that TRACK starts, stops and syncs.
02What’s in it
Built, tested, and labelled honestly.
Every feature shows where it really stands: built and tested, in beta, awaiting hardware validation, or planned.
- Built · device-dependent
OBD-II engine
Start-up, channel discovery, parsing and conservative polling, with results shown per car.
- Awaiting hardware validation
RaceBox decoder
Built from RaceBox’s published protocol, with clock alignment over Bluetooth.
- Awaiting hardware validation
GoPro control and import
Pairing, clock set, opt-in record start/stop, status and post-session Wi-Fi import.
- In the app beta
Sensors hub per car
Recommended, available and live sensors for each car, with a live test screen.
- Planned
Pro CAN gateways
Read-only, user-mapped channels from motorsport loggers.
03Who it’s for
- Data-curious driversEngine data and sharper traces for little money.
- Video makersGoPro footage synced with no editing.
- Hardware partnersHelp validate devices for the community.
Questions
Do I need any hardware?
No. The phone alone times laps and coaches. Hardware improves precision and adds data.
Will my cheap OBD adapter work?
On iPhone it must be Bluetooth LE. Classic-Bluetooth adapters can work with the planned Android app.
Does TRACK ever write to my car?
Never. It only reads data.