Source map
If the GoPro model has GPS, its embedded track can be retained as a sync reference or comparison source. Do not blend two location streams without choosing which is authoritative.
Rates and files
| Source | Data | Rate | Files |
|---|---|---|---|
| HERO11/13 example | Video, GPS, accelerometer, gyro | GPS approximately 10 Hz; IMU higher | MP4 with GPMF |
| RaceBox Mini/S | GNSS, accel, gyro | 25 Hz output; IMU sampled internally at 1 kHz then averaged | Vendor session; CSV/VBO/GPX export documented |
Recording procedure
- Mount RaceBox level, near the vehicle centre and with a clear sky view.
- Mount the GoPro rigidly without obstructing safety equipment or the driver.
- Acquire satellite lock on both GPS-capable devices before leaving the paddock.
- Start RaceBox recording, then the camera, and create a sharp visible/motion cue.
- After the session, verify both logs before packing away.
Synchronisation
RaceBox exports carry GNSS-derived time. GPS-enabled GoPro footage includes GPS time within GPMF, so capable third-party tools may align them automatically. HERO12 has no GPS, so use audio/visual and acceleration events or the RaceBox app’s supported video workflow.
Its official app can overlay RaceBox data on GoPro or other-camera video. Alternatively, export CSV or VBO for third-party overlay software.
Limitations
- Separate clocks can introduce offset and drift.
- Neither device supplies ECU channels in this two-device setup.
- RaceBox GPX may not preserve every motion or lap field available in richer exports.
- Two IMUs observe different mounting locations and orientations.