B1249 – Double locking electronic control unit (ECU) communication stop (Toyota)

B1249 means your Toyota’s body system has detected that communication with the double locking electronic control unit (ECU) has stopped. For most drivers, the real-world effect is that some door lock functions may not work normally, such as locking/unlocking behavior or security-related features tied to double locking. Technically, this is a manufacturer-specific Toyota code, and the exact network path and module role can vary by platform and option content. On a 2010 Toyota Prius, it points to an interruption in the data exchange the vehicle expects between the body control network and the double locking ECU, not necessarily a failed lock motor.

B1249 Quick Answer

On Toyota vehicles, B1249 indicates the vehicle stopped communicating with the double locking ECU. Start by checking related fuses, power/ground to the locking control electronics, and connector/wiring integrity before replacing any module.

What Does B1249 Mean?

B1249 is Toyota’s way of saying the car can’t “talk” to the double locking electronic control unit anymore, so lock-related features may be limited or unreliable. In technical terms, the Body system has logged a communication stop involving the double locking ECU, meaning expected messages are missing or the ECU is not responding on the vehicle network.

Theory of Operation

On Toyota vehicles equipped with a double locking function, the double locking ECU (or a double-locking control function within a related body controller, depending on platform design) participates in body network communication to coordinate lock states, security logic, and command execution. When you press the key fob, use the key, or actuate an interior switch, commands and status confirmations are exchanged so the rest of the vehicle knows whether doors are locked, unlocked, or in a secured state.

B1249 sets when that communication stops—typically when the ECU loses power/ground, a connector or harness issue disrupts the communication lines, or another network/module condition prevents message exchange. Because Toyota configurations vary, confirmation should be made by identifying the actual ECU location and network path in the vehicle’s wiring and network topology, then verifying whether the ECU is present on the scan tool and responding.

Symptoms

You may notice one or more of these symptoms when B1249 is stored:

• Lock function Door locks may not respond consistently to the key fob or interior switch
• Double lock feature Double locking (if equipped/active) may not engage or may cancel unexpectedly
• Security behavior Theft-deterrent/door security related behavior may be abnormal depending on configuration
• Warning indicators A body/security warning message or indicator may appear on the instrument cluster (varies by trim)
• Intermittent operation Symptoms may come and go with vibration, temperature changes, or door movement
• Other body DTCs Additional Body or network-related trouble codes may be stored alongside B1249

Common Causes

• Open, short to ground, or short to power in the communication line(s) between the double locking ECU and its networked module(s) (network design varies by Toyota platform)
• Poor connector fit, corrosion, water intrusion, or terminal damage at the double locking ECU connector or related junction connectors
• Loss of power supply or ground to the double locking ECU (intermittent or constant), causing the ECU to drop off the network
• High resistance in shared grounds or body grounds affecting network transceivers and causing intermittent communication dropouts
• Aftermarket accessories or recent electrical work introducing noise, pinched wiring, or improper splices near body harness routes
• Network issue on the body communication bus (such as a shorted node, damaged harness section, or poor termination, depending on the Toyota system architecture)
• Double locking ECU internal fault (less common; consider after verifying powers/grounds and network integrity)
• Related ECU on the same body network intermittently failing and disrupting network communication (confirm by network diagnosis, not by parts swapping)

Diagnosis Steps

Tools that help most: a Toyota-capable scan tool with body/network functions (health check, ECU list, freeze frame, and data list), a digital multimeter for power/ground and continuity checks, and basic back-probing tools. If available, an oscilloscope is useful for verifying communication signal integrity during an intermittent fault without relying on guesswork.

1. Confirm the DTC and vehicle context: Verify B1249 is present on the Toyota Prius (2010) and record all stored/pending codes and freeze frame or event data. Communication-stop codes are often secondary to a power or network fault, so capture the full DTC set before clearing anything.
2. Run a full network/ECU scan: Use the scan tool’s ECU list/health check to see whether the double locking ECU is currently detected. Note any ECUs that appear “not responding” and whether the issue is isolated to one ECU or affects multiple modules on the body network.
3. Check for pattern and operating conditions: Attempt to reproduce the fault (key cycles, lock/unlock commands, temperature/vibration changes). An intermittent communication stop often correlates with harness movement, moisture, or a weak power/ground feed.
4. Verify battery and main supply stability: Confirm the 12V system is stable and that low system voltage is not present during the failure. Then focus on the double locking ECU feeds: check for consistent B+ and ground at the ECU connector while the fault is present (do not rely only on static key-off measurements).
5. Inspect fuses and power distribution for the body system: Identify the fuses and relay feeds that support the body/locking network and specifically the double locking ECU circuit. Confirm fuse integrity under load and inspect for overheated terminals at the fuse/relay block.
6. Perform a focused visual inspection of connectors and harness routing: Inspect the double locking ECU connector(s) and nearby junction connectors for water intrusion, corrosion, terminal push-out, loose locking tabs, or evidence of prior repairs. Follow the harness along common pinch/abrasion points (behind trim, along door sills, and near body grommets) relevant to the body system.
7. Check grounds with a loaded test: Measure voltage drop across the ECU ground path while commanding locks or while the network is active. A ground that looks “good” with no load can still cause a communication stop when current demand increases.
8. Evaluate network integrity at the ECU connector: With the vehicle safely powered down as required for testing, check continuity and shorts between the communication line(s) and ground/power, and inspect for unintended resistance caused by damaged wiring or poor splices. Then, with the system active, observe whether communication activity is present at the lines (scan tool and, if available, oscilloscope).
9. Isolate intermittent wiring faults: If the ECU drops on/off the scan tool, perform a controlled wiggle test at suspect harness sections and connectors while monitoring ECU presence and communication status. If the fault is repeatable with movement, repair the affected wiring/terminal issue rather than replacing modules.
10. Rule out network disruption from another module: If multiple ECUs show communication issues, diagnose the network as a whole: identify whether one node is intermittently shorting or pulling the bus down. Disconnecting components should only be done methodically and one at a time, verifying the network recovers and the DTC behavior changes.
11. Consider ECU fault only after fundamentals pass: If power, ground, and communication line integrity are verified and the network remains healthy yet the double locking ECU still stops communicating, follow Toyota service information for confirmation tests and replacement/programming requirements (if applicable). Clear codes and verify the repair with repeated lock/unlock and multiple key cycles.

Professional tip: Treat B1249 as a “communication symptom” until proven otherwise. On Toyota body networks, the fastest way to avoid unnecessary ECU replacement is to prove three things at the double locking ECU during the failure: stable power, stable ground under load, and a communication line that is not shorted or open. If the ECU disappears from the scan tool intermittently, prioritize terminal tension, corrosion, and harness movement tests.

Possible Fixes

• Repair or replace damaged wiring in the double locking ECU communication circuit (open/short/high resistance), then secure the harness to prevent repeat chafing
• Clean, repair, or replace corroded/loose terminals and connectors at the double locking ECU and related junction connectors; ensure correct terminal fit and connector locking
• Restore proper power supply/ground to the double locking ECU (repair ground point, fuse/relay terminal issue, or damaged feed circuit) and confirm stability under load
• Remove or correct faulty aftermarket wiring/splices that introduce network noise or intermittent opens/shorts in body harness routing
• Repair a broader body network fault that is pulling communication down (shorted node or harness section), verified by network isolation testing
• Replace the double locking ECU only after confirming correct inputs (power/ground) and communication line integrity; follow Toyota procedures for setup/coding if required

Can I Still Drive With B1249?

In most Toyota applications, DTC B1249 (“Double locking electronic control unit (ECU) communication stop”) is a Body-system communication fault rather than a powertrain or braking fault, so the vehicle will usually remain drivable. However, you should treat it as a security/locking reliability issue: the affected functions can include double-lock or related door locking features that depend on the double locking ECU being able to communicate with the rest of the body network. If the code is current (not just stored history), expect intermittent or complete loss of some locking features and possible warning indications. If you cannot reliably lock/unlock the vehicle, or if the vehicle exhibits abnormal security behavior (unexpected lock/unlock events), park it in a safe place and diagnose promptly to avoid being locked out or leaving the car unsecured.

How Serious Is This Code?

B1249 is often “mostly an inconvenience” when it only affects double-locking convenience and the rest of the body network is healthy; drivability is typically unchanged. It becomes more serious when the communication stop is a symptom of a wider body network issue (for example, multiple Body-related DTCs, frequent module dropouts, or repeated loss of communication during driving). In that case, the concern shifts from convenience to reliability of body electronics—door lock control, smart entry behavior, and theft deterrent functions may become unpredictable. While it generally is not a direct safety or drivability hazard like an engine or brake fault, unresolved communication problems can escalate into no-start or immobilizer-related complaints on some Toyota platforms if key/authorization and body communication is disrupted. Confirm severity by checking whether the DTC is current and whether other communication codes are present.

Common Misdiagnoses

Technicians often misdiagnose B1249 by assuming the double locking ECU itself has failed and replacing it without proving a communication fault path. Because the definition is “communication stop,” the most common root causes are power/ground interruptions, connector issues, or network integrity problems—not necessarily a bad module. Another frequent error is chasing the symptom (door lock actuator issues) instead of the cause (ECU-to-network communication), leading to actuator replacement that does not restore communication. Some shops also clear codes and return the vehicle without confirming the code status transitions from current to history and without verifying the double-lock function under the same conditions that set the fault. To avoid wasted spending, confirm: the ECU has stable battery power and ground under load, network lines are not open/shorted, connectors are clean and fully seated, and scan tool communication with related body modules is consistent before condemning any ECU.

Most Likely Fix

The most frequently confirmed repair directions for a “double locking ECU communication stop” on Toyota vehicles are restoring reliable electrical supply to the double locking ECU (repairing power/ground feeds, resolving poor terminal fit, corrosion, or a loose connector) and repairing network wiring/connectors associated with the body communication path (pin fitment, damaged harness sections, or poor connections at junction/connector points). These should not be presented as certain until you verify the DTC is current, confirm the ECU drops offline when the fault occurs, and perform basic network/power integrity checks. If wiring and power/ground are proven good and the ECU repeatedly fails to communicate while other body modules remain normal, then ECU replacement and required initialization/coding (as applicable per Toyota service information) becomes a reasonable next step.

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.

Last updated: March 28, 2026