The ADAS Calibration Line That Appeared on Fleet Estimates

Two main families on the platforms we see. Forward radar, usually behind or within the front bumper or grille area, which measures distance and closing speed to objects ahead and feeds forward collision warning and adaptive cruise. And a camera behind the windshield near the mirror mount, which reads lane markings and often contributes to object recognition and to automatic high beam control.

Both are aimed devices. A radar looking a fraction of a degree low sees the road surface as an object. A camera whose position relative to the vehicle centreline has shifted by a small amount reports lane position incorrectly. Neither failure mode produces an obvious fault, because the hardware is working perfectly and simply reporting the world from the wrong angle.

More than owners expect. Removing and reinstalling a front bumper or grille assembly, replacing a windshield, replacing or moving a radar bracket, any suspension work that changes ride height, an alignment, and on some platforms a wheel or tire size change. Each of those either moves a sensor or moves the vehicle's relationship to the road that the sensor was aimed against.

The authority is the platform documentation and any position statement the manufacturer has published for that operation. That is worth stating plainly because it is the answer to the reasonable question of who decided this is necessary. It is not the shop, and a shop that omits it because a customer objected has performed an incomplete repair on a system with a safety function.

• Front bumper or grille removal and reinstallation
• Windshield replacement, on camera equipped vehicles
• Radar bracket replacement or any disturbance of its mounting
• Suspension work, alignment or a ride height change

Static calibration happens in the building. It needs a genuinely level floor, controlled lighting without reflections, a measured centreline reference, and physical targets positioned at distances the manufacturer specifies to a tolerance in millimetres. The scan tool then walks the procedure and the sensor learns its position relative to those targets. Floor space is the binding constraint, because the target distances for a commercial van are longer than for a car.

Dynamic calibration happens on the road. The vehicle is driven at a specified speed range on a road with clear lane markings for a specified duration while the scan tool monitors the learning process. It sounds easier and it is often harder to schedule, because it depends on traffic and on road conditions and it cannot be completed at four in the afternoon on a Friday. Some platforms require both procedures in sequence.

We scan before the repair and after it, and both reports go in the file. The pre repair scan records what fault codes existed on arrival, which matters because a vehicle that came in with an unrelated stored code should not have that code attributed to the repair. The post repair scan records that the calibration completed and passed.

That pair of documents settles nearly every dispute this subject generates. A carrier questioning the line sees a procedure with a documented output. A fleet manager questioning whether it was actually done sees the same. And if a system behaves oddly six months later, the file shows the state of it on the day it left, which is the only thing anybody can prove after the fact.

The reports also carry the vehicle mileage and the date, which matters on a fleet unit that will pass through several shops over its life. A calibration record from March is evidence that the aim was verified in March, and it is the reason a later complaint can be investigated as a new event rather than as an argument about work somebody did months ago. Fleets that file these alongside their own maintenance records find the pattern useful within a year.

Spurious intervention. A radar with its aim low enough to see the road surface as an obstacle produces occasional unrequested braking or a collision warning on an empty road. Drivers report that as a brake fault, because from the seat that is exactly what it feels like, and it gets sent to a mechanical shop that finds nothing wrong with the brakes.

The other version is a lane system that drifts or nags on a straight road, which drivers usually respond to by switching the system off. That is a rational reaction and it means a safety system is now disabled on a working vehicle. Fleets tracking driver complaints will find both patterns in their own data if they look for them, and both are calibration questions rather than mechanical ones.

Four items, all of which a shop performing the work correctly already has. Asking for them costs nothing and it distinguishes a documented procedure from a line item somebody typed.

1. The pre repair scan report, with the date and mileage
2. Which specific operations in the scope triggered the calibration
3. Whether static, dynamic or both procedures were required
4. The post repair scan showing the calibration completed and passed