Guide

How to read your MyChron data

A between-sessions guide for karters and parents. Updated October 14, 2026.

You come off the track with ten minutes before the next session. The data is on the dash. This guide shows what to look at first, what each trace is telling you, and how to turn it into one or two changes for the next run.

What your MyChron records

Depending on your MyChron model and the sensors fitted, a session can include lap times, speed, engine speed (RPM, revolutions per minute), GPS position and temperatures such as water or exhaust gas temperature. Not every kart has every channel. Check what your own setup logs before you go looking for a trace that isn't there. AiM's Race Studio 3 documentation and your MyChron manual list what each model supports.

Getting files off the dash

MyChron stores each session as a native .xrk file, and some workflows produce a compressed .xrz. Race Studio 3 downloads these files and can also export a session as CSV. Those are the formats N10 reads: .xrk, .xrz and Race Studio 3 CSV.

Start with lap times: consistency before pace

Before you look at a single trace, look at the lap list. Ignore the out-lap, in-lap and any lap with traffic or a spin. How far apart are your clean laps? A driver whose laps are scattered has more to gain from consistency than from chasing a tenth in one corner. Once your laps are tight, your best lap becomes a reliable reference.

The speed trace: braking, minimum speed, exit

The speed trace is the most useful line on the screen. In each corner, look for three things:

1. Braking point: where speed starts to fall. Braking later than your best lap and still making the corner is free time.
2. Minimum corner speed: the lowest point in the dip. A lower minimum than your best lap usually means over-slowing.
3. Exit: how quickly speed climbs after the apex. A good exit carries speed all the way down the next straight.

Overlay your best lap on a slower lap and find where the lines split. That's where the time went.

The engine speed (RPM) trace: gearing and the rev limit

RPM tells you how the engine is working with your gearing. Look at the lowest RPM in slow corners (too low and the engine bogs on exit) and the highest RPM at the end of the longest straight.

Worked example: LO206 Junior Light. Junior Light runs the blue .520 carburetor slide and a 6,150 RPM limit (Briggs & Stratton 206 rule set, 2026). If your RPM trace goes flat at 6,150 well before the end of the main straight, you're sitting on the limiter, and taller gearing may be worth trying. If you never get near the limit, the gearing may be too tall for the track. Always check your class rules with your sanctioning body.

Comparing laps and sessions

Don't try to fix every corner. Compare your best lap with a typical lap and pick the two or three corners where the gap is biggest. Then compare sessions: did a change you made (line, gearing, driving style) close the gap in those corners or not?

Temperatures: what to watch

N10 doesn't show temperatures yet, so check these in Race Studio 3. If you log water or exhaust temperature, look at the trend across the session rather than one reading. Is it stable, climbing or dropping? Compare it with earlier sessions at the same track and in similar weather, and follow your engine builder's guidance for your class.

Reading data between runs with N10

Between sessions you need a quick read, not a full analysis. N10 opens your .xrk, .xrz or Race Studio 3 CSV in any browser, with no install and no account, and your files stay on your device. It shows your laps, your best lap, where a slower lap lost time, and speed and RPM overlays.

Upload a session

For deeper work, such as configuring your logger, maths channels and detailed analysis, Race Studio 3 on Windows is AiM's full tool. Use N10 for the quick read at the track and Race Studio 3 when you have time at home.

A between-sessions checklist

1. Get the session file onto your phone, tablet or laptop.
2. Throw out the out-lap, in-lap and any compromised laps.
3. Check lap-time consistency.
4. Overlay best vs typical lap on the speed trace and find the two or three corners with the biggest gap.
5. Check the RPM trace for bogging in slow corners and time on the limiter.
6. Glance at temperatures, if logged.
7. Pick one or two changes for the next session and write them down.

Questions

What files does MyChron produce?

MyChron loggers save sessions as .xrk files (and compressed .xrz). Race Studio 3 can also export session data as CSV. N10 reads .xrk, .xrz and Race Studio 3 CSV.

Can I read MyChron data without a laptop?

Yes, for a quick between-runs read. Once the session file is on your phone or tablet, N10 opens it in the browser and the file stays on your device. For deep analysis, Race Studio 3 on Windows is the full tool.

Do I still need Race Studio 3?

Yes. Race Studio 3 is AiM's full Windows software for downloading, configuring and deep analysis. N10 is a quick between-runs read, not a replacement.

What's a good minimum corner speed?

There's no universal number. It depends on the track, the corner, your class and conditions. Compare each corner with your own best lap and with a faster driver's lap from the same session.

Why does my RPM flatten on the straight?

Usually because the engine has reached its rev limit, or your gearing is too short for that straight. In LO206 Junior Light the limit is 6,150 RPM, so a flat line there means you're on the limiter.

Need help importing a file? See Support.