B2321 – Driver door motor electronic control unit (ECU) communication stop (Toyota)

B2321 means your 2010 Toyota Prius has lost communication with the driver door motor electronic control unit (ECU), which can cause driver-door features to stop working or behave intermittently. For most owners, the real-world impact is usually limited to convenience items on the driver door (such as power window/lock behavior), not engine operation. Technically, Toyota uses this manufacturer-specific Body DTC when the vehicle’s body control network (and the module that supervises door functions) detects that the driver door motor ECU is no longer communicating as expected. Because this is a Toyota-specific code, the exact monitoring logic and involved modules can vary by platform and equipment.

B2321 Quick Answer

On Toyota vehicles, B2321 indicates a communication stop with the driver door motor ECU. Fixes usually involve confirming the module is present on the network and checking power, ground, and wiring at the driver door/hinge area before replacing parts.

What Does B2321 Mean?

In plain terms, B2321 means the car can’t “talk” to the driver door motor ECU, so some driver-door electrical functions may not work correctly. In more technical terms, Toyota sets this Body communication-loss DTC when the supervising body system detects that messages from the driver door motor ECU are missing, invalid, or the ECU is not responding during network health checks; the exact test criteria and which ECU logs the code depend on the Toyota platform and configuration.

Theory of Operation

On Toyota vehicles, driver-door functions are typically coordinated by a body control strategy that relies on networked communication between ECUs. The driver door motor ECU (naming varies by Toyota platform and option content) participates on the body communication network and exchanges status/command information needed for normal operation of door-related motors and switches.

B2321 is stored when the expected communication does not occur. Depending on the Prius configuration, this can be caused by a powered-down module (loss of B+ or ground), an open/short in the door-harness wiring (especially through the door-jamb flex point), poor connector contact, network line faults, or an internal module issue. The code itself points to communication stopping—not to a specific motor failure—so diagnosis should focus on network presence, power/ground integrity, and connector/wiring condition.

Symptoms

Common symptoms on Toyota vehicles with B2321 include:

• Scan tool behavior driver door motor ECU may be missing from the ECU list, show “no communication,” or drop out intermittently during scanning
• Power window driver window inoperative, intermittent, or limited to manual operation depending on fail-safe strategy
• Power lock driver door lock/unlock commands may not respond consistently from switches or remote requests
• Door switch inputs driver door switch panel functions may act erratically or not register
• Intermittency symptoms may change with door movement (opening/closing) due to harness flex
• Warning messages body-related warnings may appear depending on what other ECUs detect and report
• Other body DTCs additional communication or body control codes may be stored alongside B2321

Common Causes

• Loss of power feed to the driver door motor ECU due to an open fuse, poor fuse contact, or power distribution issue affecting the door ECU supply.
• High resistance or open ground path at the driver door motor ECU ground point, including loose fasteners or corrosion at the body ground location used by the door circuitry.
• Open, shorted, or high-resistance communication line between the driver door motor ECU and the rest of the Toyota body network (for example, in the door harness or body-side harness).
• Poor connection at door-related connectors such as partially seated connectors, backed-out terminals, water intrusion, or terminal fretting at the driver door motor ECU or body-side junction.
• Harness damage at the door-to-body flex point where repeated door movement can stress wiring, leading to intermittent opens or shorts that stop communication.
• Driver door motor ECU internal fault where the ECU stops communicating even with correct power, ground, and network conditions.
• Network fault elsewhere impacting communication such as a shorted network branch, another module pulling the bus down, or a wiring issue that prevents normal network biasing and messaging.
• Incorrect installation or incompatible replacement part (ECU/door motor assembly or related module) causing network incompatibility or initialization issues on the Toyota body network.

Diagnosis Steps

Tools you’ll typically need include a scan tool capable of Toyota body/network health checks, DTC freeze-frame access, and module list/topology, plus a digital multimeter, back-probing leads, and basic hand tools for trim and connector access. For intermittent faults, a harness wiggle test plan and a way to load-test power/ground circuits (without using service-manual thresholds) are helpful.

1. Confirm the DTC and capture the evidence. Using a scan tool, confirm B2321 is present and record DTC status (current/history), freeze frame (if available), and all related body/network DTCs. Note whether the complaint is intermittent and whether other door/body ECUs report communication-related codes, as that changes the direction from a single-ECU fault to a network/power distribution issue.
2. Check fuses, power distribution, and scan-tool network presence before probing the ECU. Verify relevant body/door power supply fuses are intact and correctly seated, and that power distribution to the driver door circuits is not compromised. Then run a network scan/health check: confirm whether the driver door motor ECU appears in the module list and whether it is “not responding.” If it is missing from the scan, treat this first as a power/ground/connection or bus-down issue rather than immediately condemning the ECU.
3. Verify ECU power and ground under load. Access the driver door motor ECU connector(s) as needed. With the circuit powered, confirm the ECU’s B+ feed(s) and ignition feed(s) are present when expected and that ground paths can carry current without excessive drop (test under load rather than only checking continuity). If power or ground is unstable, repair that root cause before any network diagnosis.
4. Inspect connectors and harness routing (door module, door jamb, body-side junctions). Disconnect and visually inspect the driver door motor ECU connector(s) and any inline/body-side connectors in the door circuit path. Look for moisture, corrosion, bent pins, terminal push-out, poor terminal tension, and evidence of prior repairs. Closely inspect the door-to-body flex boot area where repeated motion commonly causes broken strands or intermittent shorts.
5. Perform a targeted harness wiggle test while monitoring communication status. With ignition ON and the scan tool connected, monitor module presence/communication status and any live data indicators relevant to the driver door system. Wiggle the harness at the door jamb flex point and at connector bodies. If communication drops in/out with movement, prioritize locating the exact section with an open/high-resistance condition and repairing the wiring/terminal issue.
6. Check the communication circuit integrity to the driver door motor ECU. With ignition OFF, you may perform basic continuity and short-to-ground/short-to-power checks on the communication line(s) between the driver door motor ECU and the next connector/junction, but do not treat ignition-off measurements as proof the network is healthy. Identify and isolate opens/shorts by splitting the circuit at connectors (door-side vs body-side) to narrow down where the fault resides.
7. Verify communication line bias/voltage behavior with ignition ON (powered network). If the Toyota network to this ECU uses a biased communication line, check for normal powered behavior with ignition ON, because communication line bias is only present when the circuit is powered; ignition-off readings are not a valid reference for network bias. If the powered measurements suggest the line is being pulled low/high or is unstable, isolate segments by disconnecting the door ECU and rechecking the line on the body side to determine whether the fault is in the ECU or the harness/body network.
8. Functional test the driver door system and command tests (if supported). Use the scan tool to run active tests/utility functions related to the driver door motor ECU (as supported on this Prius platform). If the module is present, attempt actuator commands or initialization routines and confirm whether communication remains stable. If the module intermittently fails during commands, suspect power/ground integrity, terminal tension, or an ECU internal fault after wiring checks are complete.
9. Look for related Toyota body DTC patterns that indicate a shared cause. If multiple door/body ECUs set communication stop codes at the same time, focus on shared power supplies, shared grounds, or a bus fault affecting multiple modules. If only the driver door motor ECU is affected, concentrate on the door harness, door connectors, and that ECU’s dedicated feeds/grounds.
10. Confirm the repair and prevent repeat failures. After repairs, clear DTCs, cycle ignition, and re-run the network scan to confirm the driver door motor ECU is consistently present and communicating. Operate the driver door through multiple open/close cycles and repeat the harness wiggle test at the door jamb. Verify B2321 does not return as current or pending and that door-related functions behave normally.

Professional tip: For “communication stop” faults, don’t jump straight to ECU replacement. On Toyota door circuits, the most efficient time-saver is to first confirm whether the driver door motor ECU appears in the scan tool’s module list, then prove power and ground integrity under load, and only then isolate the network line by splitting the circuit at the door-to-body connector to separate door-side faults from body-side network problems.

Possible Fixes

• Repair/restore ECU power supply by correcting open fuses, poor fuse contact, or power distribution faults feeding the driver door motor ECU.
• Repair/restore ECU ground integrity by cleaning/tightening ground points, repairing damaged ground wiring, or correcting high-resistance ground connections.
• Repair harness or connector faults including terminal repair, reseating connectors, correcting pin fit/tension issues, and repairing damaged wiring at the door jamb/flex boot.
• Repair communication circuit faults by locating and fixing opens/shorts/high resistance in the communication line between the driver door motor ECU and the body network.
• Replace the driver door motor ECU (as applicable) only after power/ground and communication circuits are verified good and the ECU is confirmed to be the cause of the communication stop.
• Correct incompatible or incorrect parts/installation by verifying the correct Toyota application and ensuring any required setup/initialization procedures are completed after replacement.

Can I Still Drive With B2321?

On a 2010 Toyota Prius, DTC B2321 indicates a communication stop involving the driver door motor ECU, which typically affects body functions rather than core powertrain operation. In many cases you can still drive the vehicle, but you may lose or intermittently lose driver-door related features (for example power window/lock/mirror functions, depending on how your Prius is equipped and how Toyota networks that door ECU). Do not ignore basic safety: if the driver door will not latch reliably, if a window cannot be closed in bad weather, or if the vehicle shows broader network symptoms (multiple warning lights, many body DTCs, or intermittent power to modules), you should avoid driving until a wiring/power/ground issue is ruled out and the communication fault is stabilized.

How Serious Is This Code?

B2321 is usually an inconvenience-level code when it is limited to the driver door motor ECU communication stop and only door features are affected. It becomes more serious when the root cause is a shared network, power, or ground problem that can disturb multiple body ECUs, create unpredictable electrical behavior, or cause repeated battery drain. From a drivability perspective, this code alone typically won’t change acceleration or braking, but it can affect daily usability and security (locks) and may indicate a harness or connector condition that can worsen. Treat it as moderate severity: not usually an immediate roadside emergency, but worth prompt diagnosis to prevent intermittent no-ops and expanding communication loss.

Common Misdiagnoses

Technicians often replace the driver door motor/actuator assembly or the door ECU prematurely because the symptom looks like a failed motor, when the actual fault is the “communication stop” itself. Another common error is focusing only on the door side and skipping network fundamentals: verifying the door ECU has stable power and ground under load, checking for corrosion or looseness at the door-to-body harness connector area, and confirming the network line is not open/shorted. Misdiagnosis also happens when codes are cleared and the car is returned without a confirmation drive/cycle to see whether the module drops offline again. To avoid wasted spending, always confirm whether the scan tool can reliably identify and communicate with the driver door motor ECU, and compare results with physical checks of connectors, harness flex points, and shared grounds.

Most Likely Fix

For Toyota vehicles setting B2321, frequently confirmed repair directions include restoring reliable electrical and communication integrity to the driver door motor ECU: repairing a damaged or high-resistance wire in the door-jamb harness area, cleaning and securing a compromised connector (door-to-body connector, ECU connector, or ground point), or correcting a poor power/ground feed that causes the ECU to reset and “drop” communication. If wiring integrity and power/ground are verified and the module still will not communicate or repeatedly goes offline, replacement of the driver door motor ECU/door control unit may be considered, typically followed by Toyota-appropriate initialization or calibration steps using a factory-level scan tool such as 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.

Last updated: March 28, 2026