B124B – Automatic high beam system (Lexus)

Lexus-specific code — factory diagnostic data

B124B means the automatic high beam feature may stop working or act unpredictably, even though the headlights still work normally. On a Lexus ES, you may lose auto high-beam switching, or it may default to low beams for safety. According to Lexus factory diagnostic data, this is a Lexus-defined body DTC that indicates a fault in the Automatic High Beam system. This code does not prove a failed camera or switch. It tells you the control module saw an out-of-range input, missing signal, or a system plausibility problem that prevented normal automatic high-beam operation.

🔍Decode any Lexus ES VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data

B124B Quick Answer

B124B on a Lexus ES points to a detected fault in the Automatic High Beam system. Start with scan data and basic electrical checks at the related camera/sensor and headlamp control circuits before replacing any parts.

What Does B124B Mean?

Official definition: “Automatic high beam system.” In practical terms, the Lexus ES has disabled, limited, or flagged a fault in the auto high-beam function. The driver may notice the Auto High Beam indicator flashing, the system refusing to turn on, or the beams not switching when expected.

What the module actually checks: The body/lighting logic monitors inputs and outputs tied to the Auto High Beam feature. Depending on Lexus platform design, that includes the forward recognition camera data, the auto high-beam request from the stalk switch, headlamp output feedback, and network messages used to coordinate lighting decisions. Why that matters: B124B points to a “suspected trouble area,” not a confirmed bad component. You must confirm power, ground, signal integrity, and message plausibility before you touch parts.

Theory of Operation

Under normal operation, the Lexus ES uses a forward-looking sensor (commonly a camera) to detect oncoming traffic and ambient conditions. The driver enables the function with the headlamp switch and high-beam stalk position. The lighting control logic then commands high beams on or off. It also watches for conflicts, like low battery voltage or manual override.

B124B sets when the control logic cannot trust the Automatic High Beam system. A missing camera message, an implausible switch input, a headlamp output fault, or a network communication issue can trigger it. The system then fails safe. Most Lexus strategies default to low beams and may disable Auto High Beam until the fault clears.

Symptoms

These symptoms usually show up when the Lexus ES disables or limits Automatic High Beam operation.

• Auto High Beam inoperative The system will not enable, or it cancels shortly after enabling.
• Indicator behavior The Auto High Beam indicator may flash, change color, or show a warning message.
• No high-beam switching High beams do not turn on automatically in dark areas.
• Unexpected switching The system toggles at the wrong time, then disables itself.
• Manual high beams OK High beams work when you command them manually.
• Other ADAS warnings You may see camera-related warnings if the shared sensor goes offline.
• Intermittent operation The feature works after a restart, then fails again during the drive.

Common Causes

• Forward recognition camera view obstruction: Dirt, haze, tint film edges, or windshield damage in the camera field can stop the automatic high beam system from classifying traffic correctly.
• Camera mounting or aim issue: A shifted bracket, loose mount, or windshield replacement without proper setup can skew camera alignment and trigger an automatic high beam system fault.
• Low system voltage or unstable power supply: Weak battery, charging concerns, or power distribution faults can cause the body network to flag the automatic high beam system as unreliable.
• High resistance in power or ground to the related control unit: Corrosion at a ground point or loose terminals can pass a simple continuity check yet fail under load.
• Open or short in the headlamp high-beam control circuit: Harness damage can prevent commanded high beam operation, so the module logs a system fault.
• Headlamp assembly or shutter/driver malfunction: LED driver issues or an internal actuator fault can block high beam output and create a command-versus-result mismatch.
• CAN communication disruption between body systems and camera/lighting control: Network noise, poor splice joints, or connector fretting can interrupt status messages used for automatic high beam decisions.
• Related switch/input issue (AUTO high beam request): A steering column switch fault or incorrect input state can make the system logic invalid and set B124B.

Diagnosis Steps

Use a scan tool that can access Lexus body systems and read data list items for the automatic high beam function. Keep a DMM for voltage-drop tests under load and a test light for quick power checks. A wiring diagram and connector views matter here. If available, use a scope for CAN integrity and intermittent power glitches.

1. Confirm B124B and record DTC status (pending, current, history). Save freeze frame data if the module provides it. Focus on battery voltage, ignition state, vehicle speed, ambient light status, headlamp switch state, and any camera or lighting-related codes stored at the same time.
2. Check power distribution first. Inspect related fuses and fusible links for the headlamp system, body ECU feeds, and any camera/recognition ECU supplies. Do a quick visual inspection of the circuit path at the battery, main fuse box, and obvious harness routes before any meter work.
3. Verify ECU power and ground under load with voltage-drop testing. Backprobe the suspected control unit power feed while the circuit operates. Load the circuit by commanding headlights and high beams ON. Confirm less than 0.1 V drop on grounds with the system operating, not with a key-off continuity check.
4. Run a full network scan and note any U-codes or camera-related B-codes. If the scan tool shows a module offline, diagnose that first. A missing camera/recognition module or lighting module can make B124B set as a secondary symptom.
5. Check live data for plausibility. Watch the headlamp switch position, AUTO high beam request status, high beam command, and high beam feedback if available. Compare the commanded state to the actual lamp operation. Use a scan tool active test to command high beam where supported.
6. Inspect the forward recognition camera area and windshield condition in the camera view zone. Look for dirt, condensation, aftermarket tint edges, stickers, or a damaged windshield. Verify the camera housing sits flush and the connector locks fully.
7. Perform a close connector and harness inspection at the camera/recognition ECU (if separate), headlamp assemblies, and any body/lighting control connectors involved. Look for backed-out pins, terminal spread, water tracks, and green corrosion. Tug-test suspect wires and check for harness rub points near the radiator support and hood hinge areas.
8. Test the high-beam control circuit at the lamp side and control side. Check for opens and shorts to ground or power with the circuit isolated as needed. When you find abnormal readings, isolate the harness section by section. Avoid condemning a lamp or module until the wiring proves solid.
9. If you suspect a communication issue, verify CAN integrity at accessible connectors. Measure with ignition ON so the network bias voltage exists. Look for intermittent dropouts by wiggling harness sections while watching live module communication and data list stability.
10. Correct the verified fault, clear codes, and rerun the same operating conditions. Confirm the automatic high beam function works and B124B does not return. If the concern is intermittent, capture a scan tool snapshot during a road test to catch the moment it fails. Remember the freeze frame shows conditions when the DTC set, while a snapshot captures the failure live during your test.

Professional tip: Treat B124B as a “suspected area” code, not a failed-part verdict. On Lexus body systems, low voltage and poor grounds create false system faults. Prove power and ground quality with voltage-drop under load before chasing camera calibration or swapping headlamp parts.

Possible Fixes

• Clean and correct camera viewing conditions: Remove obstructions, address condensation, and correct any film or sticker intrusion in the camera field of view.
• Repair power or ground integrity: Restore proper voltage delivery by fixing corroded terminals, loose grounds, or damaged power feeds verified by voltage-drop testing.
• Repair wiring faults in the high-beam control circuit: Fix opens, shorts, or high resistance in the harness and connectors, then retest command versus output.
• Restore network communication stability: Repair CAN wiring/connector issues and confirm all related modules appear on the scan tool network scan.
• Perform required aiming/initialization after confirmed mechanical change: If you verified a shifted mount or windshield replacement effects, complete the Lexus-required camera setup procedure using the correct equipment.
• Replace a verified failed component only after testing: Replace a headlamp assembly, shutter/driver, or related control unit only after inputs, outputs, and circuit integrity prove the component cannot respond correctly.

Can I Still Drive With B124B?

You can usually drive a Lexus ES with B124B stored because the fault targets the automatic high beam system, not the engine or braking system. Expect the high beams to stay manual, cancel by themselves, or refuse to activate. That change matters most on dark roads and in poor weather. Treat it as a lighting safety concern, not a drivability concern. Until you fix it, use the headlight switch manually and verify low beams, high beams, and turn signals work normally. If you also see multiple driver-assist warnings, limit night driving and diagnose sooner.

How Serious Is This Code?

B124B ranges from an inconvenience to a safety risk, depending on when and where you drive. In city traffic with street lighting, you may only lose the “AUTO” high beam function. On rural roads, losing automatic control can reduce forward visibility or cause glare if you forget to dim. This system sits in the ADAS/lighting overlap on many Lexus platforms, so calibration or initialization may be required after camera, windshield, or related component replacement. Do not assume a new camera or module will work safely without the correct scan-tool procedures and confirmation tests.

Common Misdiagnoses

Technicians often replace a headlamp bulb, LED headlamp assembly, or the forward recognition camera based on the code title alone. That wastes money because B124B does not prove a failed lamp or camera. The most common misses involve basics: low battery voltage during start-up, a loose connector at the camera or headlamp, or water intrusion at a harness junction. Another frequent error involves skipping live data. If the module never sees the AHB switch request, vehicle speed status, or ambient light input change, the root cause can sit upstream in inputs, not in the high-beam output.

Most Likely Fix

The most common confirmed repair directions involve restoring clean power, ground, and signal integrity to the automatic high beam system, then proving correct operation with scan-tool data. Start with connector and harness repairs at the forward camera area and headlamp circuits, including corrosion removal and terminal tension correction. If the fault began after windshield work or front-end repairs, correct camera mounting issues and perform the required Lexus initialization/calibration routine with the proper scan tool (typically Toyota Techstream). Only consider module or camera replacement after you verify inputs and outputs under load and confirm the code resets.

Repair Costs

Repair cost depends on whether the confirmed root cause is wiring, connector condition, a sensor, a module, or the labor needed to diagnose the fault correctly.

Last updated: April 3, 2026

Definition source: Lexus factory description · Autel MaxiSys Ultra & EV. Diagnostic guidance is based on factory-defined fault logic for this code.