Headlight Calibration and AFS Initialization Tool

Sound familiar?

• You replaced a headlight assembly and now the dash reads adaptive headlight malfunction or headlamp vertical aim control failure
• One headlight points at the pavement ten feet in front of the car and the other one is flashing oncoming traffic
• The AFS OFF light is on or flashing and the headlights stopped swiveling into corners
• You put in new struts, springs, a lift kit or a leveling kit and the beams never came back to where they were
• A ride height sensor or its linkage arm broke, you replaced it, and the warning will not clear
• The car failed state inspection on headlight aim and the shop says the adjusters are already at the end of their travel
• The battery went dead or was disconnected and the headlights have been aimed wrong ever since

Why this happens

Any vehicle with HID, LED or adaptive headlights is required to keep the beam inside a legal window no matter how the vehicle is loaded. Put four passengers and luggage in the back and the body squats, the nose rises, and a fixed beam that was aimed correctly in the shop is now pointed into the eyes of oncoming drivers. Automatic leveling exists to cancel that out. Ride height sensors, usually one at the front axle and one at the rear, report suspension travel to a leveling control module. The module compares the two readings, works out how much the body has pitched, and drives a small stepper motor behind each projector to tilt the beam back down to where it belongs. Mercedes calls the controller the headlamp range adjustment unit. Volkswagen and Audi call the module Xenon Range. Toyota and Lexus call it the headlight leveling ECU. Mazda runs it inside the AFS control module. The names differ, the mechanism is the same.

Static leveling corrects for load. Dynamic leveling corrects for pitch while you drive, so the beam does not shoot skyward every time you accelerate and does not dive into the pavement under braking. On a Mazda CX-5, for instance, the module samples vehicle height every 0.1 seconds, averages one second of readings, and only then calculates a new target optical axis and commands the actuator. That averaging is why the system never seems to react to a single pothole and why a sensor reading that is wrong by a constant amount produces a beam that is wrong by a constant amount, permanently.

Here is the part that catches people. Everything the module does is relative to a stored reference. The module has no way to know the mechanical zero of a sensor arm, the home position of an actuator, or the unloaded ride height of the car it is bolted into. Those numbers are learned once and written to memory. Replace the ride height sensor, unbolt it and bolt it back on, replace the leveling module, replace a headlight that carries its own driver module, or change the ride height with new springs or a lift kit, and the stored reference no longer matches reality. Toyota and Lexus service information is blunt about this: the headlight leveling ECU must be initialized and vehicle information synchronized if the ECU is replaced, if the rear height control sensor is replaced or removed and reinstalled, or if work changes vehicle height such as replacing suspension components. Mazda ships a dedicated fault, B1041:54, whose entire meaning is that headlight auto leveling initialization has not been performed.

AFS adds a second axis. Beyond up and down, an adaptive headlight swivels left and right, driven by a swivel motor inside the housing that takes its cue from vehicle speed and steering angle. That motor has to know its own travel limits, so on power up the system runs a reference sweep and the module watches the feedback to confirm the motor reached each stop and reported a sane position. If you have ever seen the headlights twitch once when you turn the key, that is the reference run. An actuator that cannot find a stop, or a replacement housing whose motor has never reported its range to this module, fails that check. On Toyota and Lexus the swivel motors and leveling motors talk to the headlight ECU over a LIN bus, and codes such as B2410 and B2411 set when that conversation fails for ten seconds or more.

The last layer is identity. On BMW, Mercedes and Audi the headlight is not a passive lamp. It contains driver modules, and on BMW a pair of headlamp driver modules, often called TMS units, that the car has to recognize as its own. A replacement module arrives generic. Until it is coded to the VIN and the vehicle's option list, the car sees a module reporting the wrong hardware and refuses to trust its position feedback, which is exactly the condition that produces adaptive headlight malfunction on a car whose headlights are physically perfect. This is why a secondhand module pulled from another car of the same model so often fails: it carries the other car's stored data. Toyota service information warns about the same thing and tells technicians to use a new ECU, because a used one from another vehicle may set a code on mismatched data.

Related trouble codes

Code	What it means	Typical makes
B2416	Height control sensor malfunction. The rear height control sensor sub assembly has failed, or its power supply is open or shorted. Automatic beam leveling is disabled and the beam usually parks at its lowest position.	Toyota, Lexus, Subaru
B241A	Rear height control sensor. Sensor malfunction or an open or short in the signal circuit. Very often sets together with B2416.	Toyota, Lexus
B2410 / B2411	Headlight swivel ECU LH or RH communication. A LIN bus communication error persisting ten seconds or more with the ignition on.	Toyota, Lexus
B2424 / B2425	Headlight beam level control motor LH or RH, lost communication. Same LIN bus detection logic, this time to the leveling motor rather than the swivel motor.	Toyota, Lexus
B1041:54	Levelling control, missing calibration. On Mazda this is logged as a headlight auto leveling system initialization error and means initialization was never performed. Fail safe puts the swivel actuator at center and freezes the leveling actuator.	Mazda, Ford
C1A03	Left front height sensor circuit fault. Reported out of the headlamp control module with a sub code for the failure type, such as :29 signal invalid or :12 short to battery.	Ford
01539	Headlights not adjusted, no or incorrect basic setting or adaptation. Headlight adjustment is disabled. Causes include an adjustment that was never performed, lowered suspension, or level sensor readings out of range.	Volkswagen, Audi
01537	Vehicle level sensor supply voltage, signal outside specifications. Fix this one before 01539 if both are stored.	Volkswagen, Audi
01534	Control circuit for left headlight range adjusting motor (V48), open or short to plus. Headlight leveling stops working.	Volkswagen, Audi
00776	Level control system sensor, front left (G78). Either an open or short to ground at the sensor, or an implausible signal. Can set harmlessly if the car was lifted with the ignition on.	Volkswagen, Audi
800FC2 / 800FC3	Initialization fault in the right or left headlamp driver module. Commonly seen after a headlight or TMS module is fitted without being coded to the vehicle.	BMW
U0126	Lost communication with steering angle sensor module. Relevant because AFS swivel uses steering angle. This is a network fault, not a calibration fault.	Generic, all makes

Read this before you buy a headlight assembly. The single most expensive mistake on this job is condemning a $900 to $2,500 headlight because the beam is aimed wrong or the dash says adaptive headlight malfunction. Work the cheap causes first. Get under the car and physically look at the ride height sensor links. The plastic arm that ties the sensor to the control arm snaps, pops off its ball stud, or gets knocked loose during suspension work, and the module then sees a sensor frozen at one angle and aims the beam to match. A sensor reinstalled upside down or with the arm pivoting the wrong way produces the same result. Next, check whether the system has simply never been initialized: B1041:54 and 01539 both say so in plain language, and neither one is fixed by hardware. Then confirm the module was coded, if a module or a headlight was replaced. Only when the sensor reads smoothly through its range in live data, the initialization completes, the coding is correct, and the actuator still will not move or will not report its position does the housing itself deserve to be replaced. Note too that a broken linkage and a bad sensor look identical on a scan tool, so put eyes on the linkage before you order the sensor.

What you need to know before you calibrate

The calibration is only as good as the condition the car is in when you run it. The module is recording a snapshot it will treat as normal for the life of the vehicle. Park on genuinely level ground. Let the suspension settle, bouncing the car and letting it come to rest if it was just on a lift. Take the load out: no passengers, nothing heavy in the trunk, and a fuel level consistent with what the service procedure specifies. Mazda records vehicle height during the initial setting with the vehicle unoccupied. Calibrate with a toolbox in the back and you have taught the car that squatting is level, and every beam position from then on will be biased high.

Lowered and lifted vehicles are a known trap. On a lowered car the level sensor arm can reach the end of its travel and bottom out, so the module never sees a plausible reading and the basic setting fails outright. On a lifted truck the opposite happens and the beams end up aimed over the horizon. In both cases the fix starts with the sensor geometry, not with the scan tool, and in some cases the sensor bracket itself has to be modified so the arm works in the middle of its range. Nothing you command in software will rescue a sensor operating outside its mechanical range.

Order of operations matters. Do the mechanical work first, then the suspension settling, then the electronic calibration, then the mechanical aim check if the procedure calls for it in that order, then verify through a key cycle. If more than one fault is stored, clear the supply and circuit faults before the calibration faults. Volkswagen is explicit that 01537 is fixed before 01539, and the reason generalizes to every make: a module cannot learn a reference from a sensor whose power supply is out of specification.

One more honest warning. You will find forum procedures that initialize a leveling system by shorting pins in the OBD2 connector with a paperclip and then cycling the headlight switch a set number of times. Some of them genuinely reflect a factory sequence. They are also unforgiving of a mistake on a connector that carries battery power, and they tell you nothing about why the system was wrong in the first place. Running the procedure through a scan tool costs you nothing in risk and gives you the fault memory, the live sensor data and a confirmation that the routine actually completed.

How headlight calibration works with the UCAN-II Pro

1. Finish the mechanical work. Put the car on level ground, unloaded, and let the suspension settle so it is sitting at its true static ride height.
2. Plug the scanner into the OBD2 port and run a full system scan. Note every stored code, not just the headlight ones, because a ride height sensor fault often shows up in the suspension module as well.
3. Open the headlight leveling, AFS or Xenon Range module and read the fault memory. Sort the codes into three piles: circuit and supply faults, communication faults, and calibration or initialization faults.
4. Check live data for the front and rear ride height sensors. Load and unload the corner by hand or push the suspension through its travel and confirm each value moves smoothly with no dropouts, no sticking and no pegging at a limit. A value frozen while the suspension moves means a broken linkage or a dead sensor, and no calibration will fix it.
5. If a headlight, a driver module or a leveling module was replaced, code the new module to the vehicle before attempting the calibration. An uncoded module will fail the routine.
6. Run the headlight leveling initialization or AFS initialization routine for the vehicle. Follow the on screen prompts exactly: where the procedure tells you to set the mechanical aim partway through, stop and set it against a target before continuing.
7. Use the actuator tests to command the leveling and swivel motors through their range and watch the beam move on the wall. This is how you prove a motor is alive rather than guessing.
8. Clear the fault memory, cycle the ignition, and verify that the reference sweep runs clean, the warning stays out and the beams return to the same position every start. Finish with a check of the mechanical aim on a wall or an optical aimer.

Your options

	Dealer or shop	UCAN-II Pro
Cost	$45 to $100 for a mechanical aim, and $50 to $300 more for electronic calibration on an adaptive or auto leveling system. Module coding is typically billed at $100 to $250 on top.	$485 once, yours to keep
Risk of the wrong repair	Hard to argue with a quote for a complete headlight assembly at $800 to $2,500 per side when you cannot see the live sensor data yourself	Read the sensor, prove the linkage, run the initialization, and only buy the part if it actually failed
Next suspension job	Another appointment and another calibration charge every time ride height changes	Recalibrate in your own bay, as many times as you like
Shops that will touch it	Many independents refer self leveling and matrix LED systems straight to the dealer	You are the shop that does it
Other systems	Each procedure billed separately	SAS calibration, EPB service mode, ABS bleed, battery registration, DPF regen and more included

More than a headlight tool

• Full system diagnostics: engine, transmission, ABS, ESP, SRS, body, lighting and more
• Bidirectional control and coding, including actuator tests that drive the leveling and swivel motors on command
• Steering angle sensor calibration, which the AFS swivel function depends on
• EPB service mode for rear brake jobs
• Battery registration after replacement
• ABS bleeding, DPF regeneration and transmission adaptation
• Free updates, no subscription

Check your car before you buy

Headlight leveling and AFS initialization are supported across a wide range of European, Asian and American makes, but the module the routine lives in, what it is called, whether coding is also required and whether the procedure interleaves a mechanical aim step all vary by make, model and year. Do not guess. Enter your VIN or your year, make and model in the YOUCANIC coverage checker and it will tell you exactly which functions the UCAN-II Pro supports on your vehicle.

If you would rather hear it from a person, call 1-888-959-4265 Monday to Friday, 9 AM to 4 PM Eastern, and a technician will tell you plainly whether the tool does this job on your car. If it does not, we will say so.

Why YOUCANIC

YOUCANIC is based in Towson, Maryland, and has been publishing repair guides and videos since 2015. The tool is backed by the same team that writes those guides, and support comes from real US technicians, not a call center.

Frequently asked questions

Is headlight calibration the same as headlight aiming?
No, and the difference matters. Aiming is mechanical: you turn the adjuster screws on the housing until the beam pattern sits correctly on a target or in an optical aimer. Calibration is electronic: the module learns its reference positions and what the level sensors read with the car unloaded. A vehicle can be perfectly calibrated and still fail an aim check, and it can be perfectly aimed and still throw an initialization fault. Many factory procedures require both, in a specific order.

Will this help me pass a state safety inspection?
Indirectly, yes. Inspection is a mechanical aim check. Virginia, for example, has the inspector verify aim with an optical headlamp aimer when misalignment is apparent, and reject the vehicle if the pattern is more than four inches off the centerline. On a vehicle with an onboard leveling device, the inspector checks that device and rejects the vehicle if it shows the adjustment is out of specification. So if the leveling system is parked in a fail safe position or is working from a wrong reference, that is what the inspector sees. Getting the calibration right puts the beam back inside the range where the mechanical adjusters can do their job.

I replaced one headlight assembly and now the dash says adaptive headlight malfunction. Is the new headlight bad?
Usually not. On BMW, Mercedes and Audi the assembly contains driver modules that have to be coded to the VIN and the vehicle's option list. Until that is done the car sees a module it does not recognize and refuses to trust its position feedback. Code the module, then initialize, then clear the codes. A used module pulled from another car of the same model carries that car's stored data and will often set a fault for exactly that reason.

Do I need to recalibrate after a lift kit or lowering springs?
Yes, and sometimes recalibration alone is not enough. Changing ride height moves the level sensor arms away from the range they were designed to work in. Toyota and Lexus service information lists work that changes vehicle height, such as replacing suspension components, as a condition that requires initialization. If the arm is bottomed out or topped out, the sensor geometry has to be corrected first, because no software routine can learn a reference from a sensor that is out of its mechanical range.

Why did only one headlight drop and the other stay put?
Each side has its own leveling actuator and, on many vehicles, its own driver module on a LIN bus. When one actuator loses communication or hits a fault, the fail safe strategy typically freezes that side where it was or parks it at the low limit, while the healthy side keeps working. On Mazda, the documented fail safe centers the swivel actuator and stops the leveling actuator at the point the fault was detected. One beam at your feet and the other on the horizon is a classic single side fault, not a system wide one.

Can I do this without a scan tool?
On a handful of vehicles there is an initialization sequence using the headlight switch, or a pin shorting trick at the OBD2 connector. They exist, they sometimes work, and they tell you nothing about why the system was wrong. The majority of auto leveling and AFS vehicles require a tool to command the routine, and in the Volkswagen and Audi procedure the tool is what tells you when to set the mechanical aim and when the module has learned it. Reading the sensor live data is also what keeps you from buying a part you do not need.

Is there a subscription?
No. You pay once and updates are free.

What if it doesn't work for me?
You have 31 days from delivery to return it, no questions asked. For US returns we email you a prepaid label and deduct its cost from the refund; a defective unit ships back free. The refund is issued within 24 hours of the return arriving.