Lexus-specific code — factory diagnostic data| DTC Data Sheet | |
| System | Body |
| Standard | Manufacturer Specific |
| Fault type | Communication Loss |
| Official meaning | Double locking electronic control unit(ECU) communication stop |
| Definition source | Lexus factory description · Autel MaxiSys Ultra & EV |
B1249 means the Lexus ES lost communication with the double locking electronic control unit, so some lock and security functions may not work right. You may notice doors that will not double-lock, inconsistent lock behavior, or a security feature that acts up. According to Lexus factory diagnostic data, this code indicates “Double locking electronic control unit (ECU) communication stop.” This is a manufacturer-specific Lexus body code, so the exact network path and module arrangement can vary by platform. Treat it as a direction to test the communication circuit and module power/ground, not as proof that a module failed.
Decode any Lexus ES VIN — free recalls, specs & safety ratings — free VIN decoder with NHTSA data
B1249 Quick Answer
B1249 on a Lexus points to a communication loss with the double locking ECU. Diagnose it like a network fault first: confirm the ECU is present on the scan tool, then verify its power, ground, and network wiring before considering any module replacement.
What Does B1249 Mean?
Official definition: “Double locking electronic control unit(ECU) communication stop.” In plain terms, one or more Lexus body modules expected to “hear” the double locking ECU, but did not. In practice, the ES may lose double-lock capability, show abnormal keyless entry behavior, or store body DTCs after a lock/unlock event.
What the module actually checks: a supervising body controller (often the main body ECU or gateway, depending on Lexus platform) monitors network messages and response timing. When it does not receive required communications from the double locking ECU within an expected window, it sets B1249. Why this matters: the code points to a suspected trouble area (communication path and module availability). It does not identify the root cause, so you must verify network integrity and the double locking ECU’s power and ground under load.
Theory of Operation
On Lexus vehicles, the body network coordinates door locking, theft deterrent logic, and keyless entry requests. Modules share status and commands over a vehicle network. The double locking ECU (where equipped) participates by reporting its state and accepting lock commands. The system relies on consistent message traffic and correct wake-up behavior.
B1249 sets when the supervising module no longer sees the double locking ECU “online.” A power or ground interruption can take the ECU off the network. A harness fault can also block communication. Network problems often show up during wake/sleep transitions, like after a remote lock command or after the vehicle sits.
Symptoms
These symptoms commonly show up when the Lexus ES logs B1249.
- Scan tool double locking ECU missing from the ECU list, not responding, or dropping offline intermittently
- Double-lock function does not engage, works only sometimes, or behaves differently from other doors
- Power lock behavior delayed locking, repeated lock cycling, or incomplete locking confirmation
- Keyless entry inconsistent response to smart key lock/unlock requests
- Security indication theft deterrent or lock status indicators behave abnormally after locking
- Body DTCs other communication-related body codes stored with the same timestamp
- Battery drain intermittent parasitic draw if a module fails to sleep due to network chatter
Common Causes
- Power supply interruption to the double locking ECU: A weak feed, blown fuse, or poor power distribution connection can reboot the ECU and stop communication.
- High-resistance ground at the double locking ECU: Corrosion or a loose ground point creates voltage drop under load and the ECU drops off the network.
- Open or short in the communication pair: A cut, pinched, or chafed harness can open the network path or short a bus line and halt messages.
- Poor terminal fit or corrosion at ECU/connectors: Spread pins, moisture, or fretting corrosion increases resistance and causes intermittent “communication stop” events.
- Network disturbance from another module on the same bus: A failing node or shorted branch can pull the network down and make the double locking ECU appear offline.
- Aftermarket device or improper accessory wiring: Added electronics tied into body power or network wiring can introduce noise, backfeed, or an intermittent short.
- Low system voltage event: Battery, charging, or jump-start related voltage dips can trigger a module reset and set a communication loss DTC.
- ECU internal fault (only after circuit proof): If power, ground, and network integrity test good, the ECU may stop transmitting due to an internal failure.
Diagnosis Steps
Use a scan tool that can run a full Lexus body network scan and view freeze frame. Have a quality DVOM for voltage-drop tests and a back-probing kit. A fused test light helps load circuits. If available, use a lab scope to evaluate network signal integrity during an intermittent drop-out.
- Confirm B1249 and record all DTCs from every module. Save freeze frame data. For this communication loss code, focus on ignition state, vehicle speed, battery voltage, and any network-related companion codes. Freeze frame shows when the fault set. A scan tool snapshot captures an intermittent drop-out you trigger during testing.
- Run a network scan and note whether the double locking ECU appears online. If it does not appear, treat the concern as an offline module or bus-down condition. If it appears but logs B1249, treat it as intermittent communication quality or resets. Before touching the ECU connector, check related fuses and power distribution points that feed body ECUs.
- Check battery condition and charging system basics. Look for low-voltage history in scan data when available. A low system voltage event can mimic a communication stop by forcing module resets.
- Verify the ECU power and ground under load, not with simple continuity. Power the circuit and load it with the circuit operating. Perform voltage-drop testing across the power feed path and across the ground path while the ECU remains connected. Keep ground drop under 0.1 V with the circuit operating. A high-resistance ground can look “good” unloaded and fail under load.
- Inspect the ECU connector area and harness routing before meter work on the network lines. Look for moisture tracks, green corrosion, loose locks, or pushed-back terminals. Tug-test the harness lightly and check for strain at the connector.
- Check terminal fit and pin tension at the ECU and any inline connectors in the body harness. Use the correct terminal test tools. Do not “tighten” pins with picks. Confirm proper engagement and that the connector fully seats and locks.
- With ignition ON, measure the communication line bias behavior at an accessible point. Communication line bias voltage only exists with the network powered. Ignition-OFF readings do not provide a valid reference. If you see an abnormal steady reading, suspect a short to power, short to ground, or a pulled-down network from another node.
- If the scan tool shows multiple modules offline, isolate the bus fault. Disconnect suspected branch connectors one at a time and recheck network recovery. Start with recently serviced areas and any connectors with water intrusion risk. A single shorted branch can stop communication for multiple ECUs.
- If only the double locking ECU drops out, perform a wiggle test while monitoring network status and the ECU’s online/offline state. Wiggle the connector, harness bend points, and any clips that can cut insulation. Capture a scan tool snapshot during the wiggle test to document the exact moment communication stops.
- Check for accessory wiring issues. Inspect for splices into body power circuits or network wiring. Verify any installed equipment does not share ECU feeds or grounds and does not tie into communication wiring.
- Clear codes and confirm the repair. Cycle the ignition and run a network scan again. Road-test if needed and verify B1249 does not return as pending or stored. If B1249 returns immediately on key-on, treat it as a hard fault and repeat power/ground and bus integrity checks before condemning the ECU.
Professional tip: On Lexus body networks, a “communication stop” code often results from voltage drop, not a dead module. Prove power and ground with loaded voltage-drop tests first. Then prove the bus stays stable with ignition ON. Only after you confirm a healthy feed, ground, and network should you consider an ECU fault.
Need network wiring diagrams and module connector views?
Communication stop and network faults require module connector pinouts, bus wiring routes, and power/ground diagrams. A repair manual helps you trace the exact circuit path before replacing any ECU.
Possible Fixes
- Repair power feed issues: Replace the failed fuse only after you find and correct the overload or short, and restore clean power distribution connections.
- Restore ground integrity: Clean and tighten the body ground point, repair damaged ground wiring, and verify less than 0.1 V drop under load.
- Repair communication wiring faults: Fix opens/shorts in the communication pair, correct pinch points, and resecure harness routing to prevent repeat damage.
- Service connectors and terminals: Remove corrosion, address moisture intrusion, and replace damaged terminals or connector bodies that fail a pin-tension check.
- Remove or correct aftermarket wiring: Rewire accessories to proper power and ground sources and eliminate any connection to network wiring.
- Replace the double locking ECU only after proof: If power, ground, connectors, and bus integrity all pass and the ECU still drops offline, replacement and initialization may be required.
Can I Still Drive With B1249?
You can usually drive a Lexus ES with B1249 stored, because this code points to a body-network communication loss, not a powertrain control failure. Expect convenience and security features to act up. Double-locking may not engage, may engage inconsistently, or may not report status correctly. Treat it seriously if the vehicle will not lock, will not unlock reliably, or shows other network-related warnings. Also stop and diagnose if you notice battery drain, repeated clicking from door locks, or intermittent no-start due to immobilizer-related functions on your platform. Use basic precautions until repair. Park in secure areas and confirm lock operation manually.
How Serious Is This Code?
B1249 rates as low to moderate severity in most cases. It becomes mostly an inconvenience when only the “double locking” function stops while normal lock and unlock still work. It becomes more serious when the communication loss spreads. Multiple body modules may drop offline on the same network branch. That can disable remote entry, cause a parasitic draw, or create intermittent “no communication” during scans. It can also indicate unstable power or ground to a body ECU. That condition can cascade into repeated resets and unpredictable behavior. This code does not directly affect braking or engine control, but it can leave the vehicle unsecured or stranded due to network instability.
Common Misdiagnoses
Technicians often replace door lock actuators or the smart key components too early. B1249 does not prove a bad latch or key. It only says the vehicle lost communication with the double locking ECU. Another common mistake involves clearing the code and calling it fixed after it stays off at idle. Network faults often show up during vibration, door movement, or low-voltage events. Many people also ignore basic voltage-drop checks at the ECU power and ground pins. High resistance there can mimic a “dead module.” Finally, technicians sometimes condemn the ECU because the scan tool cannot see it. A shorted network line, a poor splice, or a corroded connector can block communication with a good ECU.
Most Likely Fix
The most frequently confirmed repair direction for B1249 on Lexus vehicles involves restoring stable power, ground, and network integrity to the double locking ECU. Start with connector inspection at the ECU and related harness routes in the door or body area. Look for moisture, pin fit issues, and harness damage from repeated door movement. Next, prove the communication lines can carry traffic. Check for shorts to ground, shorts to power, or an open between the ECU and the network junction. If the wiring tests pass and the ECU still drops offline intermittently, verify the ECU stays powered under load. Only then consider ECU replacement and required registration or initialization with Techstream.
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.
| Repair Type | Estimated Cost |
|---|---|
| Basic DIY inspection (battery, fuses, connectors) | $0 – $50 |
| Professional diagnosis | $100 – $200 |
| Wiring / connector / ground repair | $80 – $400+ |
| Module replacement / programming | $300 – $1500+ |
Definition source: Lexus factory description · Autel MaxiSys Ultra & EV. Diagnostic guidance is based on factory-defined fault logic for this code.
Key Takeaways
- B1249 on Lexus: Manufacturer-specific body DTC for double locking ECU communication stop.
- Meaning: The network lost communication with the double locking ECU, not a confirmed bad actuator.
- Best first proof: Verify ECU power, ground, and voltage drop under load before parts.
- Network focus: Inspect door-area harnessing and connectors that flex and trap moisture.
- Repair confirmation: Recheck for stable module communication during a road test and repeated lock cycles.
FAQ
Does B1249 mean the double locking ECU has failed?
No. B1249 only identifies a suspected trouble area: communication with the double locking ECU stopped. An open network circuit, shorted wiring, poor ground, or low system voltage can create the same result. Confirm the ECU has stable power and ground under load, then verify the network lines are not shorted or open before condemning the ECU.
My scan tool cannot communicate with the double locking ECU. What does that prove?
It proves a communication problem exists, but not the root cause. If other body modules communicate, suspect a local issue on that ECU branch. Check ECU power and grounds first, then inspect the network pair between the ECU and the network junction. If multiple modules drop offline, test the main body network and power supply stability.
How can I confirm the repair is complete after fixing wiring or connectors?
Confirm stable communication and repeatable double-lock operation under real conditions. Cycle locks and unlocks many times, including with doors opening and closing. Then road test on rougher pavement to recreate vibration. Enable criteria vary by Lexus platform, so use service information to confirm when the body network self-check runs and when it will log faults again.
Do I need Toyota Techstream if the double locking ECU requires replacement?
Yes, plan on using Toyota Techstream for Lexus body module work. Replacement often requires initialization, registration, or configuration so the new ECU matches the vehicle’s options and communicates correctly. Without the correct scan tool functions, the vehicle may store new communication codes or lose specific lock behaviors. Verify wiring first to avoid unnecessary programming costs.
Can a weak battery or charging issue set B1249?
Yes. Low voltage during cranking, jump starts, or a marginal battery can reset body ECUs and disrupt network traffic. The result can look like an ECU communication stop. Check battery condition and terminal connections, then verify charging system output and ripple with proper equipment. After repairs, confirm the code does not return during cold start and lock cycles.