Exporting from your logger
DriverPeak reads the file your logger already wrote. Nothing is converted, exported to CSV or re-saved first. This page says where that file is for each supported logger and what DriverPeak does with it.
Last verified against build f98a29e · 2026-09-06
The one rule
Upload the original file, with its original name. The four loggers below each write one native file per session, and that file is what the upload form and the desktop agent accept:
| Logger | File | Companion |
|---|---|---|
| Racelogic VBOX | .vbo | — |
| AiM | .xrk, .xrz | — |
| MoTeC | .ld | .ldx, optional, same name as the .ld |
| iRacing | .ibt | — |
Note
A CSV export from the logger software is not accepted, even from a supported logger: the native file carries the channel definitions, the sample rate and the GPS data the lap detection needs. Another logger entirely? Send one file through Support and we will tell you whether it can be read.
Racelogic VBOX
- File
- .vbo, the plain-text file the logger records to its card and that VBOX Tools and Circuit Tools save.
- Channels
- Read from the file's own [column names] header rather than fixed positions, so the column order of different VBOX models and firmware versions does not matter.
- Time
- VBOX records the UTC time of day; the date comes from the file's File created on line when it is present.
AiM
- File
- .xrk, or the compressed .xrz: the file Race Studio 3 stores when it downloads a session from the logger.
- Channels
- AiM channel names are set in Race Studio, so DriverPeak maps channels by the function AiM assigns them, not by their name. The exception is GPS: the GPS channels are matched by their default names.
Watch out
If the GPS latitude or longitude channel has been renamed in Race Studio, DriverPeak cannot tell which one it is. The session uploads, but it has no usable position data and laps are not detected. Where the file still marks the channel as GPS-sourced, it is listed under the session's logger channels with an unmapped_gps prefix; not every AiM configuration marks it that way, so the absence of that prefix does not prove the GPS channels are fine. Keep the GPS channels at their default names.
MoTeC
- File
- .ld, the logged-data file the logger download creates and i2 opens. Channels recorded at different rates are merged onto one 10 Hz timeline.
- Companion
- .ldx, optional: the marker file that holds the lap beacons. Upload it in the form's second file field, or leave it in the same folder as the .ld for the desktop agent to pick up. It must have the same name as the .ld: session.ld with session.ldx. A different name is refused with the message doesn't match file … expected the same basename with a .ldx extension, so a marker file from the wrong session cannot be attached by accident.
- What the beacons do
- Laps are still detected from GPS. The beacon markers are cross-checked against that detection and only ever add a warning: if the manual markers disagree with the GPS crossings by more than 3 seconds, the session carries the note Beacon markers present but disagree with GPS detection … treat lap boundaries as uncertain. They never override the detected laps.
iRacing
- File
- .ibt, the telemetry file iRacing writes to Documents › iRacing › telemetry while disk telemetry recording is on. In the sim, Alt + L toggles that recording; one file is written per recording.
- Laps
- Taken from the sim's own lap counter, not from GPS, so lap numbers match the sim's and the sector columns are the sim's splits. The session's lap table caption says iRacing splits.
- Size
- iRacing records at 60 Hz with a few hundred channels, so a long session is a large file (around 100 MB is normal). The upload is parsed before the response comes back; a large file takes longer than a minute. Do not re-submit while the button says Uploading & parsing….
Honesty note
A recording in which the sim's lap counter never wraps, for example a single out-lap, has no complete lap. It is kept as one unconfirmed segment and the session says No LapDistPct wrap found — a single unconfirmed segment.
What is read from the file
Six channels are charted: speed, throttle, brake, RPM, gear and steering. A channel the logger does not record is shown in the channel rail as no data rather than hidden. GPS latitude and longitude drive lap detection, the sector positions and the track map. Every other channel in the file is kept with the session and listed as a logger channel.
Tip
Once the file is somewhere on your laptop, the desktop sync agent can watch that folder, or the card reader, and upload each new file by itself. During the beta it is available on request.