01 / PHONES/CAMERA
Phones/Camera
GoPro, DJI and representative flagship phones: video, GPS, IMU, metadata access and real track-day limitations.
Explore cameras and phones →Track-day hardware reference
Choose what records the data you actually need.
Cameras, phones, GPS receivers and specialist loggers do different jobs. Start with the outcome you want, then see what each device records and how the files fit together.
Five practical routes through track-day hardware
This guide covers phones and cameras, OBD-II adapters, setup, specialist logging and post-session compatibility. Product pages and technical guides sit beneath the relevant route, so comparisons and workflows support the hardware rather than competing with it.
02 / OBD-II
ELM327
OBD-II adapters, example PIDs, vehicle data and the difference between requesting a parameter and reading CAN messages.
Explore OBD-II and PIDs →
03 / SETUP
Setup & recording
Settings, mounting, satellite lock, heat, power and storage—plus complete examples for common track-day setups.
Build a reliable setup →04 / LOGGERS
Loggers & telemetry
RaceBox, AiM, VBOX and related hardware, compared by recorded channels, rates, storage, connectivity and openness.
Browse specialist hardware →
05 / WORKFLOWS
Compatibility & workflows
See which device supplies video, GPS, IMU and vehicle channels—and how separately recorded files can be synchronised.
See what works together →Start with a device page
Technical specifications are separated from practical consequences, with unknown or app-dependent fields labelled plainly.
GoPro HERO13 Black
Video modes, GPS metadata, IMU access and extraction requirements.
Open device pageRaceBox Mini S
25 Hz GNSS, standalone storage and documented Bluetooth data.
Open device pageAiM Solo 2 DL
GPS lap timing, IMU and supported vehicle-data connections.
Open device page