AiM loggers

AiM telemetry analysis without the spreadsheet

Drop the .xrk file from your Solo 2, Solo 2 DL, MXm, MXS, MXP, MXG or EVO straight into Pitwall. It is decoded on your own device, lined up lap against lap, and turned into a corner-by-corner debrief that says where the time goes and what to try next. No Race Studio session, no CSV wrangling.

Analyze an AiM session See an example debrief

Which file to load

Download the session from the logger as usual. Connect the logger to Race Studio 3 over Wi‑Fi or USB and download the day's sessions. Nothing else needs to happen in Race Studio.
Find the raw file. Race Studio 3 keeps each session as a .xrk file, usually under C:\AIM_SPORT\RaceStudio3\user\data on Windows. A .xrz is the same file compressed; Pitwall reads both.
Drop it into Pitwall. Up to six sessions from the same car and track at once, so a whole track day becomes one analysis and the theoretical best is built from your best corners across all of it.

Prefer a CSV? Race Studio 3 Analysis exports any session as a CSV (File, Export). Pitwall reads that too, and recognizes the channels by their names. Files from the older Race Studio 2 (.drk, .rrk) can't be read directly: use the matching .xrk or a CSV export.

How the .xrk is read, and where

AiM's format is binary and proprietary, so Pitwall carries a converter in the page: libxrk, an open-source reader, running under Pyodide (Python compiled to WebAssembly) in a background thread of your browser. The first time, the converter downloads about 25 MB and is kept for next time. Your raw file never leaves the device; what continues to the analysis server is a plain table of the channels below, like any other logger export, and it is not kept after the debrief is returned.

From the logger	What Pitwall does with it
GPS speed, latitude, longitude, altitude	Finds the circuit, cuts and lines up the laps, places the official turns, builds the speed trace and the delta.
Inline and lateral acceleration (the logger's own accelerometers)	The grip circle, braking peaks, trail-braking overlap, and the estimated pedals when the car isn't wired.
Yaw rate (gyro)	With steering, the car-balance calls: understeer mid-corner, the rear stepping out on exit.
Engine RPM, throttle position, brake pressure or position, steering angle, gear	Picked up when the logger was wired to the ECU or CAN bus (Solo 2 DL, MXS, MXm, EVO). They unlock the pedal calls: brake later, get to pressure sooner, trail the brake, stop coasting, back to throttle sooner, commit once.
Log date and time, driver, vehicle, venue	The session's date in the garage and the car's name when you save it.

Channels are matched by the function AiM tagged them with first (Engine RPM, Percentage Throttle Load, Brake Circuit Pressure, Steering Angle, Gear), then by name, and resampled onto the GPS timebase. Anything above 50 readings a second is thinned before upload; nothing the analysis uses is lost.

What you get from each logger

Solo 2 (GPS and accelerometers)Lap times to hundredths, every corner ranked by time lost against your theoretical best, minimum and exit speeds, the running delta, the grip circle and the consistency figure. Throttle and brake are estimated from g-forces and drawn with a hollow dot: good for pictures, never used for a verdict.

Solo 2 DL, MXm, MXS, MXP, MXG, EVO (wired to the car)All of the above, plus the pedal calls with their evidence: how many feet later the reference braked, how much longer you took to reach peak pressure, where you coasted, where you lifted on exit. With steering and yaw, the balance calls and the "one thing to work on" across the lap.

Any AiM with a video cameraAdd the MP4 in the debrief's Video section and watch the lap with speed, pedals, gap and corner names drawn over it. The footage is played in your browser and never uploaded.

What the debrief says

The debrief is built for the question you actually have in the paddock: what do I fix first? It opens with the three corners costing you the most against a theoretical best stitched from your own fastest clean segments, each with one finding, the evidence behind it, and a drill. The corner-by-corner section covers all of them. Laps & data holds the traces, the delta, the track map and the grip circle for when you want to check the call yourself. Every coaching call is a written rule with a stated threshold, listed on the methodology page, and it is only made when the file has the measured channel it needs.

A real example, from a 718 GT4 RS at Road America, is on the Road America page and on the front page.

If something goes wrong

"No GPS stream in this file." The logger recorded without a GPS fix (antenna unplugged, or an indoor test). Pitwall needs position to cut laps; try a session recorded on track.
The converter won't load. It needs a browser that can run WebAssembly workers (current Safari, Chrome, Firefox, Edge). As a fallback, export a CSV from Race Studio 3 Analysis and load that.
A huge file. One .xrk holding a whole weekend works, but a session at a time keeps the theoretical best honest: conditions change. Pitwall analyzes up to three hours of driving per request.
A call looks wrong. The feedback button on any debrief sends your note, and the file if you attach it, to the person who writes the rules. That is how they get corrected.

Try it on your last session

Free while in beta. No account needed.

Analyze a session See a real debrief