Exporting and analysing MyChron 5 data
The AiM MyChron 5 is the most common kart logger. Getting its data out and using it properly is what turns a lap timer into a development tool.
1. Getting sessions off the dash
- USB key / cable — the most common route. Sessions transfer to Race Studio 3 on the PC.
- Wi-Fi — the MyChron 5 broadcasts its own network. Race Studio connects to it and downloads sessions without a cable.
- Automated download — the dash answers on the network and can be queried directly, so sessions can be pulled automatically as soon as you are back in the paddock.
2. Exporting CSV from Race Studio 3
- Open the session in Race Studio Analysis.
- Choose data export,
CSVformat. - Select channels: time, distance, GPS speed, GPS position (latitude/longitude), RPM, EGT, water temperature.
- Export every lap of the session, not just the best one — session evolution is information in itself.
The native AiM .xrk file is only readable by Race Studio. CSV is what lets your data live elsewhere: multi-session comparison, per-track history, engine analysis.
3. MyChron 5 channels that find lap time
| Channel | What to read |
|---|---|
| GPS Speed | The reference channel: more reliable than wheel speed when the tyre spins |
| Lat / Lon | Line overlay, automatic track detection |
| RPM | Check revs at the end of the straight and validate the sprocket |
| EGT | Check mixture strength — see the Rotax jetting guide |
| Water temp | Validate radiator taping against ambient temperature |
4. What to look at after a session
Gap between your best lap and your median
A consistent driver has a small gap between best lap and the median of clean laps. A large gap means the speed is there but the repeatability is not — that is driving work, not setup work.
Theoretical best
Take the best time achieved in each sector across the whole session and you get the lap you could have driven. The gap to your actual best lap shows how much is available without changing anything on the kart.
Throttle re-application point
In slow, technical sectors this is the first lever. Getting back on the throttle slightly earlier pays off down the whole following straight.
Session drift
If the last laps are consistently slower, check cold tyre pressure before blaming the driver.
5. Managing several dashes and drivers
As soon as a team runs several MyChrons, the problem stops being analysis and becomes organisation: which session belongs to which driver, on which track, with which setup. Pairing each dash serial number with a driver automates attribution at import time.
KartAnalytics imports the Race Studio CSV, detects the circuit from GPS, rebuilds laps and sectors, and compares sessions side by side — including between drivers in the same team.
Frequently asked questions
How do I export a MyChron 5 file to CSV?
In Race Studio 3 Analysis, open the session and use data export in CSV format, selecting time, distance, GPS speed, GPS position, RPM and EGT.
Can I read an .xrk file without Race Studio?
.xrk is an AiM proprietary format. The reliable route is converting it to CSV, which any analysis tool can then use.
GPS speed or wheel speed?
GPS speed is more reliable for driving analysis because wheel spin does not affect it. Wheel speed is still useful precisely to detect that spin.
How many laps do I need for a valid analysis?
At least three clean laps, excluding out-lap and in-lap. Below that, no evolution trend can be computed reliably.
Analyse your telemetry in seconds
Import your file, compare laps, get setup advice.
Create an account