Blog
Notes on track day logging, telemetry imports and getting more out of your sessions.
Turning your track data into an AI race engineer
Most AI telemetry tools read one lap. Connect an assistant to your whole logbook — sessions, setups, tire wear, costs — and ask the questions a single trace can't answer.
Syncing onboard video with track telemetry, in the browser
How to line up a YouTube onboard with RaceChrono or RaceBox telemetry — one sync point, then every lap plays with the track map and speed trace following the footage.
Reading OBD data from a track day: RPM, fuel and temperatures
How to record OBD-II channels alongside GPS in RaceChrono — what hardware works, which channels you get, and what a season logbook does with them after the import.
RaceBox Mini for track days: getting more from your data
What the RaceBox Mini records at a track day, how to export the CSV, and how to turn one session into a season-long logbook with lap times, telemetry and setup history.
Track day tire pressures: cold vs hot, and how to actually dial them in
What psi to run at a track day, why the hot pressure is the number that matters, how much pressure builds cold-to-hot, and the FWD vs AWD difference — with a simple loop to find your numbers.
What a track day season costs — and the one number worth tracking
Nobody agrees what a track day costs because everyone measures it differently. The fix isn't a bigger spreadsheet — it's one normalised number: cost per lap.
What to do with your RaceChrono data after the session
RaceChrono .rcz vs CSV v3 export, explained: when to use each, what they actually contain, and how one session's data becomes a season-long logbook.
How to keep a track day logbook (without spreadsheets)
A plain-English guide to a track day log book: what to capture per session, why spreadsheets break around session 8, and why a digital track day logbook app holds a whole season that Notes, Sheets and RaceChrono can't.