Racer Utilities¶
Predictive Reference Lap¶
One of the most appreciated features of AiM devices is the predictive time. In short, based on recorded data, the device predicts the lap time of the lap you are currently completing. You’ll see this predicted time directly on your dash—handy and very useful!
The prediction is always computed against a reference lap. This reference lap can be: the best lap of the session, the best lap of the day, the previous lap, or a lap saved from RaceStudio 3 Analysis.
In all these cases, you need to instruct your device which strategy to use. You can set this either in the dash user menu or in the device window of RaceStudio 3.
If you use a reference lap saved from analysis, you must (a) save the reference file, and (b) transmit it to your device. This can be done from the device window. If you want to manage multiple reference files, you must tell the device which one to use.
See also:
Predictive Reference Lap in Device — how to move reference lap files (*.prl) into or from your device, and how to configure which one is active.
Predictive Reference Lap in Analysis — how to save a reference lap.
Predictive Reference Lap in Tracks — how to double-check all the reference laps you’ve created for a track configuration.
Please note that a reference lap is strictly bound to a track configuration, and that there can be only one default reference lap file per track configuration. This behavior is similar, though not identical, to User Pit Lane.
Bound to a track configuration means that the device first identifies the configuration you’re racing on (if multiple are available) and then loads the associated reference file.
Important: If you create and transmit a new track map to your device, you must also create and save a new predictive reference lap file in RaceStudio 3 Analysis.
User Pit Lane¶
In November 2025 AiM introduced for some devices the support for pit lane information, enabling useful computations for racing classes in which pit stops and pit times are critical.
With pit lane information we mean: Pit IN detection, Pit OUT detection, and lap detection while in the pit lane.
Pit IN, Pit OUT, and Pit Start/Finish line detection can be managed either with GPS or with external triggers. External triggers are useful, for example, when detection must be triggered manually by the driver or provided by external electronics to AiM systems.
When using GPS, the device needs to know where the trigger points are. Devices can obtain this information from AiM track files (*.tkk) — many already include pit lane markers — or from user-created pit lane files (*.upl).
On your dash
Pit lane computations can be displayed in different ways depending on the chosen strategy. Each strategy implies a specific set of parameters:
- Entrance to Exit
Minimum Pitlane Time: minimum mandatory time between Pit IN and Pit OUT.
Estimated Time to Exit: user-estimated time from box to Pit OUT.
Max Speed: pit speed limiter value.
- Stationary in Pit
Minimum Pitlane Time: minimum time for pit stop.
Max Speed: pit speed limiter value.
When Pit Entrance is detected, the dash shows current speed. LEDs turn green or red depending on whether the speed is below or above the limiter.
During the Pit Stop, LEDs turn off. When the countdown reaches zero, LEDs blink green and the dash shows 0:00.0 to indicate the driver may leave the pit.
Upon leaving the pit, the dash shows predictive time relative to the Estimated Time to Exit. LEDs light up green or red (±0.1s) to advise whether to go faster or slower.
On your PC
You can configure how you want your device to trigger the pit lane points, and/or if you want the pit triggers information to be managed in your devices network.
You can create pit lane files directly on the device by driving to detection points to record their GPS coordinates, or by saving them from previously recorded data in analysis.
You can analyze pit lanes times and speeds in analysis in a dedicated window. This, independently from what you do with your dash.
See also:
Configuration of Commands — how to configure devices to use pit (in, out, start/finish points) triggers other than GPS.
User Pit Lane in Analysis — how to save user pit lane files in analysis.
Pit Lane Analysis — how to view computed pit lane information in analysis.
User Pit Lane in Device — how to move pit lane files (*.upl) into or from your device, and how to configure visualization strategies.
User Pit Lane in Tracks — how to review all pit lanes created for a track start/finish line.
Please note that a user pit lane is strictly bound to a track start/finish line position. This means that if two or more track configurations share the same start/finish line, the same pit lane definition will be used for all of them. This behavior is similar, though not identical, to Predictive Reference Lap.
Important: You need the most recent firmware and software. How to check if your hardware supports this feature? Once the latest firmware is installed, connect your device to your PC and open the device window in RaceStudio 3. If the User Pit Lane in Device window is available, your device supports this feature.