U0182 – Lost communication with adaptive front-lighting system (AFS)

Last updated: April 8, 2026

U0182 means your vehicle lost communication with the adaptive front-lighting system (AFS). For most drivers, the first sign is a headlight warning and lights that stop turning with the steering. Night visibility can suffer, especially on curves. This code does not prove the AFS module failed. It only tells you the network cannot reliably “see” the AFS system. According to factory diagnostic data, this code indicates a communication loss with the AFS over the vehicle network. The next step is to confirm whether the AFS module is missing on a network scan, or if it drops offline intermittently.

🔍Look up your vehicle's recalls, specs & safety ratings — free VIN decoder with NHTSA data

U0182 Quick Answer

U0182 points to a network communication problem with the AFS, not a confirmed bad headlamp. Check if the AFS module responds on a full module scan, then verify its power, grounds, and network wiring.

What Does U0182 Mean?

Official definition: Lost communication with adaptive front-lighting system (AFS). In plain terms, another control module expected to exchange data with the AFS, but it stopped hearing back. When that happens, the AFS usually disables adaptive functions and may default the headlights to a fixed position.

What the vehicle actually checks: Modules on the network monitor expected messages and acknowledgments from the AFS. If those messages stop for long enough, the reporting module sets U0182 and may log it as pending or confirmed. That matters because a dead AFS module, a power/ground issue, or a network wiring fault can all create the same “lost communication” result.

Theory of Operation

Under normal operation, the AFS controller exchanges data with other modules over the vehicle network. It uses those messages to calculate headlamp swivel and leveling commands. Inputs commonly include steering angle, vehicle speed, yaw rate, and ride height signals. The AFS then drives actuators in the headlamp assemblies and reports its status back to the network.

U0182 sets when the rest of the network cannot communicate with the AFS reliably. AFS can drop offline if it loses battery power, ground integrity, or network connectivity. Shorted wiring, backed-out terminals, corrosion in a headlamp/AFS connector, or a network branch fault can also block messages. SAE J2012-DA keeps U-code descriptions intentionally general, so you must confirm which module and network segment the vehicle uses for AFS before you choose a repair path.

Symptoms

U0182 symptoms usually affect headlamp aiming behavior and what your scan tool can access.

• Scan tool behavior: AFS module missing from the module list, shows “no communication,” or drops out during a full vehicle scan
• Headlight warning message: “AFS OFF,” “Adaptive headlights malfunction,” or a headlamp system warning lamp illuminated
• Adaptive function disabled: Headlights no longer swivel into turns, especially noticeable at low speeds
• Self-leveling inoperative: Beam height does not adjust with load changes, or performs a limited “safe mode” routine
• Fixed beam position: Headlamps park at center or a default angle after key cycle
• Intermittent operation: AFS works until bumps, moisture, or heat cause a dropout
• Related network codes: Other U-codes stored in multiple modules, often pointing to a common network or power feed issue

Common Causes

• AFS module power supply interruption: A blown fuse, poor fuse contact, or open feed prevents the AFS module from powering up, so it never transmits network messages.
• High-resistance or open AFS ground: Corrosion at a ground lug or a loose fastener lets voltage float under load, which causes module resets and repeated communication dropouts.
• Open circuit in CAN/LIN communication wiring to the AFS module: A broken conductor stops data traffic, so other modules log U0182 when they time out waiting for AFS responses.
• Short to ground or short to power on a network circuit: A chafed harness can pull the bus low or high, which corrupts messages and can knock multiple modules offline.
• Poor connector terminal fit at the AFS module: Spread terminals, backed-out pins, or water intrusion creates intermittent contact that looks like a “lost communication” event.
• Shared network issue affecting multiple modules: A fault on the same bus segment, splice pack, or gateway path can prevent AFS messages from reaching the rest of the network.
• AFS module stuck in boot/reset due to low system voltage: Weak battery, charging issues, or voltage dips during cranking can keep the module from staying online long enough to communicate.
• Aftermarket lighting or alarm wiring interference: Added equipment can load power/ground circuits or damage harness routing, which leads to bus faults and repeated U0182 setting.

Diagnosis Steps

Tools you need include a scan tool with full network scan capability, a DVOM for voltage-drop testing, and wiring diagrams for the AFS power/ground and network circuits. A two-channel oscilloscope helps on intermittent network issues. Use back-probing pins and terminal tension tools to avoid damaging connectors during checks.

1. Confirm U0182 on a full vehicle scan. Save the report, note whether it shows as pending or confirmed, and record freeze frame data. For this communication code, focus on ignition state, vehicle speed, battery voltage, and any other U-codes or low-voltage DTCs logged at the same time.
2. Run a network/module presence scan and check whether the scan tool can communicate with the AFS module. If the AFS module does not appear, treat it as an offline module problem first. If it does appear, treat it as an intermittent bus, connector, or power/ground issue.
3. Check for related codes in other modules, especially gateway, body control, headlamp leveling, or low-voltage codes. Multiple “lost communication” codes on the same bus point to a shared network fault instead of a single module. Single-module U0182 often points to AFS power/ground or its local connector and wiring.
4. Inspect fuses and power distribution that feed the AFS system before probing the module connector. Verify fuse integrity and confirm the circuit actually carries load. A fuse can look good and still fail under load due to heat damage or poor terminal contact.
5. Verify AFS module power and ground with voltage-drop tests under load. Command the headlamps/AFS on if possible, then measure ground drop from the AFS ground pin to battery negative; target less than 0.1 V drop with the circuit operating. Next measure B+ feed drop from battery positive to the AFS B+ pin; excessive drop indicates resistance in the feed.
6. Inspect the AFS module connector and harness routing closely. Look for water tracks, green corrosion, overheated terminals, or evidence of prior headlamp or bumper work. Perform a terminal fit check and look for backed-out pins that can pass a quick continuity test but fail with vibration.
7. If U0182 suggests a CAN-based network on your vehicle, check CAN bus resistance with ignition OFF and the battery disconnected. Measure between CAN+ and CAN- at an accessible connector on the same bus segment; a healthy bus reads about 60 ohms. A reading near 120 ohms or OL indicates an open or missing termination, while a low value suggests a short or extra termination.
8. With ignition ON, check network bias voltage to ground at the AFS connector or a nearby network access point, if the wiring diagram confirms CAN. A healthy CAN bus typically shows about 2.5 V on both CAN+ and CAN- to ground. Do not use ignition-OFF readings as a reference because bias voltage only appears when modules power up.
9. If the vehicle uses a LIN sub-network for headlamp/AFS communication, inspect the LIN line for shorts to ground/power and for opens. Use the wiring diagram to confirm which wire is LIN. A scope pattern helps here because LIN faults often appear as intermittent “flat-line” periods during headlamp movement.
10. Use a scan tool snapshot during a road test or a headlamp/steering angle exercise to catch an intermittent dropout. Freeze frame shows conditions when the code set. A snapshot captures live data at the moment communication drops, which helps you correlate the fault to bumps, steering input, or charging voltage changes.
11. After repairs, clear codes and run another full network scan. Confirm the AFS module stays present and U0182 does not reset. Recheck headlamp aiming/adaptive operation, and verify no new network codes appear after a complete key cycle and a short drive.

Professional tip: If U0182 returns immediately at key-on and the AFS module stays offline, stop chasing CAN voltages first. Prove module power and ground quality with voltage-drop under load. A marginal ground often allows brief communication, then triggers resets that look like network failure.

Possible Fixes

• Restore AFS power feed integrity: Replace the correct fuse only after you find the reason it opened, and repair loose or overheated fuse box terminals that cause voltage loss under load.
• Repair the AFS ground path: Clean and tighten the ground lug, repair corroded wiring, and confirm less than 0.1 V ground drop with the system operating.
• Repair CAN/LIN wiring faults: Locate and repair opens, shorts to ground, or shorts to power in the network circuits using proper splices and harness protection.
• Service connector and terminal issues: Remove corrosion, dry and seal water intrusion paths, and replace spread or damaged terminals to restore reliable pin tension.
• Correct shared network or gateway issues: Repair damaged splice packs, bus connectors, or gateway power/ground faults when multiple modules show communication losses.
• Address low system voltage problems: Test the battery and charging system and correct voltage dips that cause AFS module resets, then recheck for U0182.

Can I Still Drive With U0182?

You can usually drive with a U0182 code, but you should treat it as a lighting safety issue. When the vehicle loses communication with the adaptive front-lighting system (AFS), the headlights may stop swiveling with steering input. Some vehicles also disable auto-leveling or cornering light functions. Night driving on dark, curving roads becomes the main risk. Glare control can also change, which may affect oncoming traffic. If the headlights point incorrectly, reduce speed and avoid nighttime driving until you confirm aim and basic low/high beam operation. If other network codes appear, or the dash shows multiple module warnings, stop and diagnose soon. A broader network fault can create unpredictable system behavior.

How Serious Is This Code?

U0182 ranges from an inconvenience to a real safety concern, depending on your driving conditions and how the AFS fails. In daylight, you may not notice more than a warning message and a stored U-code. At night, especially on winding roads, losing swivel or leveling can shorten your sight distance and increase driver workload. This code does not usually create an engine drivability problem because it sits in the Network system. Still, it can signal a CAN or LIN communication problem that may spread to other modules. If the scan shows multiple “lost communication” codes, treat it as high severity and diagnose the network and module power feeds immediately. Some vehicles may require AFS initialization or calibration after repairs, especially after module replacement or headlamp assembly work.

Common Misdiagnoses

Many people replace an AFS headlamp assembly or the AFS module as soon as they see U0182. That approach wastes money because U0182 only says the network lost communication, not that a component failed. Technicians also miss the basics by checking CAN wiring first and skipping loaded power and ground tests at the AFS module. A weak ground, corroded splice, or water intrusion at the headlamp connector can drop module voltage just enough to reset it. Another common mistake involves scan tool behavior. If the scan tool cannot talk to the AFS module, some assume the module is “dead.” In practice, a bus short, a missing wake-up, or an open in the communication line can block access. Always prove network integrity, module power, and ground before condemning hardware.

Most Likely Fix

The most common confirmed repair direction for U0182 involves restoring reliable power, ground, or network connection to the AFS control unit or headlamp assemblies. Start with connector issues because AFS components live in high-moisture, high-vibration areas. Cleaning and tightening terminals, repairing water-damaged connectors, or fixing a broken ground near the radiator support often restores communication. The next frequent direction involves repairing an open or shorted communication circuit on the AFS network path, which may share harness routing with front-end collision repairs. After the repair, road test long enough to confirm the code stays cleared. Enable criteria vary by vehicle, so use service information and re-scan after several ignition cycles and a night-time functional check.

Repair Costs

Network and communication fault repairs vary by root cause — wiring/connectors are often the source, but module-level repairs or replacements can be significantly more expensive.