How it works
A GPS lap timer stores the coordinates of a start/finish line and of sector lines.
Each time the car's path crosses a line, it records a crossing time. AiM's Solo 2, for example, matches its position against a database of over 4,000 tracks and learns unknown layouts from the car's path.Medium4
Update rate decides how finely a crossing can be placed. At 25 Hz a new fix arrives every 40 ms, and at 100 mph (161 km/h) the car covers about 1.8 m (5.9 ft) between fixes. Timers therefore estimate the crossing between the fixes either side of the line instead of using the nearest sample.Medium76
Transponder systems put the reference in the track. A transponder in the car is detected by a loop buried at the line, and a decoder stamps the time. MYLAPS quotes 0.001 s resolution for its X2 system, which race control uses for official results.Medium92
Infrared beacon systems sit between the two: a trackside emitter marks the line and a receiver in the car triggers the lap. They give a fixed trigger point without satellite reception, but someone has to place the beacon at every event.Low2
Predictive timing compares the current lap, point by point, with a reference lap and shows the running gain or loss as a delta. A theoretical best lap adds up the best sector times. Both depend on position quality, so a weak GPS fix makes the delta wander.Medium4
Typical values
- About 1.8 m at 25 Hz5.9 ft
- About 4.5 m at 10 Hz14.7 ft
- About 2.0 m CEPu-blox NEO-M9N
- AiM quotes under 0.5 m for GPS091.6 ft
How an ECU uses it
A lap timer does not control the engine, but its lap and sector markers are how tuners index logs.
A timer with ECU logging, such as AiM's Solo 2 DL, records engine channels alongside GPS, so a slower lap can be traced to rpm, throttle, lambda or boost.Medium5
Dash loggers often accept a lap beacon signal on a dedicated input, and AiM's MX series lists a lap signal input. The lap marker then splits ECU and sensor data into laps for comparison. Timing accuracy still comes from the timer or beacon, not from the ECU.Medium3
How to test it
4 checks, in order.
- Check the start/finish line against the real line on a satellite map. A line set too narrow or in the wrong place can miss laps; RaceChrono treats about 50-75 m as a normal line width.Medium8
- Confirm engine data lines up with GPS. Use a sharp event, such as a hard brake at a known marker, and check that the GPS speed drop and the throttle or brake channel coincide.Low5
Symptoms and causes
Laps missing or two laps merged into one.
Likely causes Start/finish line misplaced or too narrow, or a GPS dropout at the line.
Check Plot the GPS path against the line and check satellite count at the crossing.
Medium8
Predictive delta jumps by tenths on a straight.
Likely causes Poor fix quality, low update rate, or a reference lap that took a different line.
Check Log fix quality and compare a 25 Hz receiver with phone GPS on the same lap.
Lap times differ from official timing by a constant amount.
Likely causes The virtual line is not in the same place as the timing loop.
Check Move the virtual line to the loop position and compare again.
Low9
In tuning
Lap time is the final score but a noisy one.
Driver variation of a few tenths can hide a calibration change, so compare sector times and speed at fixed points, such as speed at the end of the longest straight.Medium4
Overlay laps by distance, not time. Plotting rpm, throttle, lambda and boost against distance lines up corners between laps, so a change in exit speed can be tied to drivability, boost response or traction control intervention.Medium51
Watch for heat across a session. Compare the first and last laps for intake temperature, coolant and timing retard; lap times that fade while the driver stays consistent often point to heat soak or knock control pulling timing.Medium1011
Formula and worked example
Common mistakes
Mistake Comparing laps from different days without recording conditions.
Do instead Log ambient temperature and pressure and note tire state; air density and grip change lap time independently of the tune.Medium114
Mistake Relying on 1 Hz phone GPS for corner-by-corner analysis.
Do instead Use an external receiver at 10-25 Hz; some phone and older receivers update at only 1 Hz.Medium87
Mistake Placing the virtual line somewhere other than the official timing loop.
Do instead Line it up with the official line when comparing against transponder times.Low9
Myths vs facts
Myth A GPS lap timer can only be as precise as its sample interval.
Fact Interpolating between the fixes on either side of the line places the crossing far more finely than 40 ms at 25 Hz. Position error still adds noise, so compare averages over several laps.Medium74
Myth Predictive lap time is a forecast of the final lap.
Fact It is the reference lap time plus the current gain or loss. It assumes the rest of the lap matches the reference, so it swings with every corner.Medium4
Frequently asked
How does a GPS lap timer work?
It tracks the car's position several times per second and stores the coordinates of a start/finish line and sector lines. When the path crosses a line, it calculates the crossing time, usually by interpolating between fixes. It then shows lap, sector and predictive times against your best lap.Medium47
Is 10 Hz GPS good enough for lap timing?
For lap times, generally yes, because interpolation places the line crossing between fixes. For corner analysis, faster is better: at 100 mph a 10 Hz receiver has about 4.5 m between fixes versus about 1.8 m at 25 Hz. Avoid 1 Hz sources, which some phone GPS units still use.Medium78
What is predictive lap timing?
Predictive timing compares where you are now with where you were at the same point on a reference lap, usually your best. It shows the running gain or loss as a delta and adds it to the reference time to predict the lap. The prediction changes at every corner.Medium4
Is GPS or transponder lap timing more accurate?
A transponder loop gives a fixed physical trigger and MYLAPS quotes 0.001 s resolution, so it is the standard for official results. GPS depends on fix quality and line placement, but it needs no trackside equipment and also records speed and position for analysis.Medium97
Wiring, pinouts and parts
Sources
Numbered as cited above. Hover or tap a citation chip to preview it.
11 sources
- Data logger · Wikipedia · reference · retrieved 2026-10-27
- Transponder timing · Wikipedia · reference · retrieved 2026-10-27
- MX series dash logger technical specifications (MXS, MXP, MXG, MXT) · Aim Technologies (AiM UK distributor) · vendor-doc · retrieved 2026-10-27
- AiM Solo 2 GPS lap timer product page · Aim Technologies (AiM UK distributor) · vendor-doc · retrieved 2026-10-27
- AiM Solo 2 DL lap timer and ECU logger product page · Aim Technologies (AiM UK distributor) · vendor-doc · retrieved 2026-10-27
- AiM GPS09 module product page · Aim Technologies (AiM UK distributor) · vendor-doc · retrieved 2026-10-27
- NEO-M9N-00B GNSS module data sheet (UBX-19014285) · u-blox AG · vendor-doc · retrieved 2026-10-27
- RaceChrono support and FAQ (GPS receivers, OBD-II adapters, start/finish lines) · RaceChrono · vendor-doc · retrieved 2026-10-27
- X2 Timing System · MYLAPS · vendor-doc · retrieved 2026-10-27
- Automotive Handbook, 10th edition (2018) · Robert Bosch GmbH / Wiley · book · retrieved 2026-10-27
- Internal Combustion Engine Fundamentals, 2nd edition (2018) · McGraw-Hill (John B. Heywood) · book · retrieved 2026-10-27

