ADAS sensor calibration requirements don’t follow a single standard across manufacturers. Whether a front camera, radar module, or blind spot sensor requires a static target board calibration, a dynamic drive cycle, a scan tool reset, or some combination depends on the specific make, model, year, and which repair operation disturbed the sensor. A windshield replacement on one platform may require a relatively short static procedure. The same job on a different platform may require both static calibration and a highway drive cycle before the system clears its initialization. I-CAR’s OEM Calibration Requirements Search consolidates those OEM procedures into a searchable database organized by vehicle and repair event.
For vehicle owners, the practical value is verification: knowing what your make and model requires lets you confirm your repair shop completed the right procedure, not just any procedure. For technicians, the search provides the OEM reference and identifies whether dealer-level equipment is required before the job begins.
Quick answer
The I-CAR OEM Calibration Requirements Search runs at rts.i-car.com and covers 2016 and newer vehicles. Filter by year, make, and model, then select the affected system or repair event. The result shows which calibration type (static, dynamic, or scan-only) is required, whether special tools are needed, and whether the system will set a DTC. An I-CAR account is required to view full results.
Specifications
| Calibration type | Setup | Common trigger events | Scan tool required? |
|---|---|---|---|
| Static | Target board at OEM-specified distance and height; level floor required | Windshield replacement, camera replacement, mounting bracket repair | Yes, on most platforms |
| Dynamic | Drive at OEM-specified speed on a road with visible lane markings | Some radar systems; post-static follow-up on certain platforms | Yes |
| Static + Dynamic | Both in sequence, per OEM order | Forward-facing cameras on several Honda, Toyota, Subaru, and VW platforms | Yes |
| Scan tool (OBD only) | No physical setup; module initialization via scan tool | Battery disconnect, module replacement, software update | Yes, dealer-level |
| Pre-repair scan | Diagnostic scan before repair begins | ADAS-equipped vehicles before collision repair, glass replacement, sensor-area work, electrical work, module replacement, or other ADAS-adjacent work | Yes |
| Post-repair scan | Final DTC verification after all calibrations | All ADAS-equipped vehicles after any ADAS-adjacent work | Yes |
Calibration requirements are vehicle-specific. The table above reflects general categories; exact procedures vary by make, model, year, sensor type, and the specific repair event. Always confirm against the I-CAR search result or the OEM repair documentation before starting work.
Static calibration
Setup and equipment. Static calibration uses a target board (sometimes called a pattern board or target chart) mounted at a specific distance and height in front of the vehicle. The floor must be level; some OEM procedures specify the allowable surface flatness tolerance. Lighting conditions also vary: some OEMs require controlled ambient light levels, which rules out performing the calibration outdoors or in a shop bay with daylight interference. The camera sensor is then aligned to the target through a scan tool interface while the vehicle remains stationary.
Which platforms require it. Many Toyota Safety Sense, Honda Sensing, Subaru EyeSight, and VW camera systems use static target calibration after windshield or front camera work, but the exact requirement depends on year, model, trim, sensor type, and repair event. Confirm the procedure in the I-CAR search or the OEM repair manual before quoting the job. A calibration rig validated for one platform may not be usable for another that carries the same calibration type label.
Dynamic calibration
Drive conditions. Dynamic calibration requires driving at an OEM-specified speed for a set distance on a road with clearly visible lane markings. Exact thresholds vary by platform and must be confirmed in the OEM procedure or I-CAR search result before starting. Some platforms require motorway driving; others accept residential roads. Weather, road quality, sun glare, and lane marking clarity can all prevent the calibration cycle from completing, requiring a repeat.
Partial initialization problem. Platforms that require dynamic calibration after static (dual calibration) present a specific diagnostic trap. After static target work is complete, the scan tool shows no active DTCs. The system appears ready. Only the dynamic drive cycle is missing. Without the required dynamic step, the system may remain in an incomplete or reduced initialization state even if no active DTC is shown. I-CAR’s database documents which platforms require both steps and in what order.
Scan-tool-only procedures
When no physical setup is needed. Some calibration events require only a scan tool command: an initialization, angular offset reset, or module write. No target board, no drive cycle. Battery disconnection on certain platforms (depending on how long power was interrupted and which modules reset) falls here, as does sensor module replacement where the physical sensor position was not disturbed. Not all generic OBD-II scanners can send manufacturer-specific ADAS initialization commands. Dealer-level tools (Toyota Techstream, Honda HDS, Subaru SSM, VW/Audi ODIS) or approved aftermarket equivalents are needed to complete the write sequence. A shop running a generic scanner on an ADAS module reset job will confirm the connection but cannot perform the calibration.
Pre-repair and post-repair scanning
Pre-repair scan. I-CAR and several OEM position statements specify a pre-repair diagnostic scan before collision, glass, electrical, module, or ADAS-adjacent work on an ADAS-equipped vehicle. The pre-repair scan documents which DTCs and system states existed before the repair. Without it, a shop cannot distinguish between a fault it caused and one that was already present. For insurance purposes, the pre-repair scan is often required documentation. Skipping it leaves the shop unable to defend its work if a pre-existing ADAS fault surfaces after the job is closed.
Post-repair scan. After all calibrations are complete, a final post-repair scan confirms no new DTCs were set and that all systems have passed initialization. For vehicles equipped with federally required AEB or PAEB systems, an unresolved post-repair calibration fault may mean the vehicle leaves the shop without that safety function operating as intended. Documenting the completed calibration protects the shop and gives the owner verifiable confirmation.
How to check
- Go to rts.i-car.com/oem-calibration-requirements-search.html. Sign in or create an I-CAR account. Full procedure details require an account; basic system availability information is visible without one.
- Select year, make, and model. The search covers 2016 and newer vehicles. For older vehicles, the OEM repair manual is the primary reference.
- Select the repair event. Options include windshield replacement, camera replacement, radar sensor replacement, bumper repair, suspension work, and others. The calibration requirement depends on the event, not only the sensor type.
- Read the result carefully. Note whether static, dynamic, or both are required; what equipment is specified; and whether the OEM lists any pre-conditions (floor level tolerance, ambient temperature, vehicle ride height).
- Cross-reference against the OEM repair manual. I-CAR’s database is based on OEM documentation, but OEMs update procedures independently of I-CAR’s publication cycle. If the repair is on a recently updated model, check the OEM directly.
- Confirm the shop has the required scan tool. Ask specifically whether they have the OEM-level software for your vehicle’s brand, not just an aftermarket scanner. The distinction matters for module initialization.
- Request the calibration documentation. A completed calibration generates a result record from the scan tool. Ask for that printout or digital file before leaving the shop.
Questions to ask the repair shop
- Did this repair require ADAS calibration for my exact year, make, and model?
- Was the requirement checked in I-CAR or the OEM repair manual?
- Was a pre-repair scan performed before work began?
- Was a post-repair scan performed after calibration?
- Was the calibration static, dynamic, scan-only, or a combination?
- Can I get the calibration report or scan tool printout?
- Was the vehicle road-tested after calibration if the OEM procedure required it?
What goes wrong
Static calibration performed on an uneven floor. A shop bay with floor drains, lift pads, or surface dips introduces a tilt angle into the camera’s reference frame. The system calibrates to a position that appears valid but is off by a fraction of a degree. At highway distance, a fraction-of-a-degree error shifts the camera’s reference point by several meters. The DTC scan shows clear; the system fails to detect targets in certain lateral positions.
Dynamic step skipped on a dual-calibration platform. After static calibration, the system often shows no active codes. A shop unfamiliar with the specific platform’s dual requirement closes the job. The vehicle is returned to the customer. No warning appears until a scenario triggers the partially initialized forward system to behave differently than a fully calibrated one.
Generic scanner used for dealer-level initialization. A generic OBD-II tool connects to the module and reads fault codes successfully. When the technician attempts the initialization command, the tool times out or returns a generic acknowledgment without actually writing the calibration parameters. Some tools display a “complete” message regardless. The only reliable check is repeating the post-repair DTC scan with the same tool and confirming the initialization-specific codes cleared.
Calibration skipped because no DTC was set. Not every ADAS sensor sets a fault code when it falls out of calibration. Some systems operate in a degraded state with reduced detection range or reduced braking authority without triggering any warning light. A sensor that was mechanically disturbed but not replaced may continue appearing functional by all standard checks while no longer meeting OEM performance specification.
Pre-repair scan skipped, then a fault appears post-repair. A shop skips the pre-repair scan to save time. After the repair, the customer reports an ADAS warning light that wasn’t there before. Without the pre-repair DTC record, the shop cannot demonstrate the fault existed before the job began. The vehicle may go back to the shop for no-charge work on a fault it didn’t cause.
Wrong target geometry used for a multi-brand shop. Calibration target boards are not universal. A board validated for one OEM’s camera system carries different pattern geometry and distance requirements than one built for another brand’s system. Using the wrong target, or approximating the distance with a tape measure instead of a dedicated mounting tool, produces a calibration that passes the software handshake but misses the physical alignment. See Pre-collision system malfunction for the diagnostic path when ADAS warnings appear after a repair.
