B2322 – P-door motor electronic control unit (ECU) communication stop (Toyota)

B2322 means your Toyota has detected a loss of communication with the P-door motor electronic control unit (ECU), which can cause a power door function to stop working or behave unpredictably. For most owners, the real-world effect is simple: a powered door feature may not operate, may stop mid-travel, or may need to be operated manually. On a 2010 Toyota Prius, this is a manufacturer-specific Body system code, and the exact network path and module roles can vary by Toyota platform. The code is set when the vehicle’s body control network can no longer reliably exchange messages with the P-door motor ECU.

B2322 Quick Answer

B2322 indicates a communication stop with the P-door motor ECU on Toyota vehicles, usually caused by a network/wiring issue, poor power/ground to the door ECU, or a failed ECU that is not responding.

What Does B2322 Mean?

In simple terms, B2322 means the car “can’t talk to” the P-door motor ECU, so power door-related operation may be disabled or inconsistent. In technical terms, Toyota uses B2322 as a manufacturer-specific Body DTC defined as “P-door motor electronic control unit (ECU) communication stop,” meaning the controlling module(s) stop receiving expected data messages from that door motor ECU or detect that communication has halted on the related in-vehicle network.

Theory of Operation

On Toyota vehicles, powered door features typically rely on multiple modules sharing information over the body communication network. The P-door motor ECU (the motor controller for the powered door function, depending on Toyota platform design) exchanges status and command messages with other body-related controllers so the system can coordinate enable/disable logic, motor drive requests, position/status feedback, and safety interlocks.

B2322 sets when the supervising controller detects that the P-door motor ECU’s messages have stopped or become invalid for long enough to be considered a communication loss. This can happen if the P-door motor ECU loses power or ground, a connector has high resistance or corrosion, wiring is open/shorted, or the network lines are compromised. It can also occur if the ECU is present but internally locked up and no longer transmits or responds to scan-tool requests.

Symptoms

Depending on Toyota platform and option content, you may notice one or more of the following:

• Scan-tool behavior P-door motor ECU may not appear in the ECU list, may show “no communication,” or may drop offline intermittently during a health check
• Power door function Powered door operation may be inoperative, disabled, or intermittent
• Manual override Door may require manual operation because the motor control system is unavailable
• Stops mid-operation Door movement may stop unexpectedly if communication is lost while operating
• Body warnings Body-related warning messages or indicators may appear depending on Toyota cluster/software strategy
• Related DTCs Additional body/network communication DTCs may be stored in other modules that expected messages from the P-door motor ECU
• Intermittency Concern may worsen with vibration, door movement, or after moisture exposure due to connector or harness issues

Common Causes

• Open or high-resistance in the communication circuit between the P-door motor ECU and the rest of the Toyota body network
• Short to ground, short to power, or short between communication lines causing the P-door motor ECU to drop off the network
• Power supply fault to the P-door motor ECU (blown fuse, poor power distribution connection, or intermittent feed)
• Ground circuit fault for the P-door motor ECU (loose fastener, corrosion at ground point, or high resistance under load)
• Connector issues at the P-door motor ECU or related junction connectors (water intrusion, corrosion, backed-out terminals, bent pins, poor terminal tension)
• Harness damage in a moving/flexing area (pinched wiring, chafing, door-area loom fatigue, or previous repair damage)
• Network-related issue elsewhere on the same Toyota body communication bus that prevents stable messaging (another module or wiring fault loading the bus)
• P-door motor ECU internal malfunction causing loss of communication or failure to respond to scan-tool queries

Diagnosis Steps

Tools needed: a Toyota-capable scan tool with network (ECU) health check, DTC and data list access, and the ability to clear codes; a digital multimeter; a test light or other load tool for power/ground checks; and basic back-probing tools. Use Toyota service information for connector views and harness routing so you test the correct circuits without damaging terminals.

1. Confirm DTC B2322 is present and record all stored/pending codes from every module. Save freeze frame or snapshot data and note whether B2322 is current or history. If other communication, battery/power, or body DTCs are present, document them because they can be the root cause of the “communication stop.”
2. Before probing the ECU, check fuses and power distribution related to body electronics and the P-door system, and perform a scan-tool network health check. Verify whether the P-door motor ECU appears in the network scan and whether other ECUs show “no communication.” If the P-door motor ECU is missing from the scan list, treat this first as a power/ground, connector, or bus integrity problem rather than a motor problem.
3. Verify the P-door motor ECU power and ground under load. With the ECU connected (or using a safe back-probe method), use a test light/load tool to confirm the power feed(s) can carry current and that the ground path is solid. A voltage reading with no load can look normal even when the circuit fails under operating conditions, so prioritize loaded testing.
4. Inspect the P-door motor ECU connector(s) and nearby junction connectors for water intrusion, corrosion, terminal spread, partially seated connectors, and backed-out pins. Gently tug-test the harness near the connector while watching scan-tool communication status (do not force the terminals). Repair obvious connector faults before deeper circuit testing.
5. Inspect the harness routing from the P-door motor ECU to the body harness/network path. Pay special attention to areas prone to flexing or pinch points (for example, near a moving door/hinge area if applicable on the platform design). Look for chafing to metal, prior repair splices, crushed loom, or signs of overheating. Correct any physical damage found.
6. Perform communication circuit integrity checks between the P-door motor ECU connector and the next network junction per Toyota wiring information: check for opens and high resistance end-to-end, and check for shorts to ground and shorts to power with the circuit isolated as directed by service information. If a short is found, isolate by disconnecting sections/junctions to locate the branch that loads the bus.
7. If Toyota service information calls for checking communication line bias, measure communication line voltage levels with ignition ON. Communication-line bias voltage is only present when the network is powered; ignition-OFF readings are not a valid reference. Compare side-to-side behavior across the network at accessible points to help identify whether the issue is localized to the P-door motor ECU branch or is affecting the bus more broadly.
8. Use the scan tool to run active tests or utility functions that request communication with the P-door motor ECU (where supported). Observe whether the ECU intermittently drops in/out during commands, and correlate dropouts with harness movement, connector manipulation, or changes in load. If the ECU communicates sometimes, prioritize intermittent connection, terminal tension, or power/ground stability.
9. Rule out a network-wide fault by checking whether other body-related modules share similar symptoms or codes. If multiple ECUs show communication stop conditions, diagnose the common power supply, shared ground, or main network wiring before condemning the P-door motor ECU.
10. After repairs, reconnect all components, clear DTCs, and rerun the network health check to confirm the P-door motor ECU is consistently recognized. Road test or operate the relevant door function through multiple cycles (as applicable) and recheck for returning codes. Confirm no new communication DTCs set during the verification period.

Professional tip: For Toyota “communication stop” DTCs like B2322, avoid jumping straight to ECU replacement. First prove whether the P-door motor ECU is missing from the network because it has lost power/ground, because the communication lines are being pulled down by a wiring/connector fault, or because another module on the same bus is corrupting communication. A network scan result (present vs. not present) combined with loaded power/ground testing is often the fastest way to choose the correct diagnostic path.

Possible Fixes

• Replace a blown fuse and correct the underlying cause of the overload, then verify stable communication with the P-door motor ECU
• Repair/clean and properly secure power feed or ground connections (including restoring damaged terminals) for the P-door motor ECU
• Repair harness damage (open/high resistance/short) in the communication circuit and protect the wiring from future chafing or pinching
• Clean, dry, and repair connector/terminal issues (corrosion removal, terminal replacement, reseating pins, restoring terminal tension) at the P-door motor ECU or junction connectors
• Correct a network wiring fault affecting multiple modules (repair the branch or main bus segment that is loading communication)
• Replace the P-door motor ECU only after power/ground integrity and communication circuit checks confirm the ECU is the source of the communication stop, then perform any required Toyota initialization or calibration steps per service information

Can I Still Drive With B2322?

Usually, yes—Toyota DTC B2322 indicates a communication stop involving the P-door motor ECU, which is a body-system function rather than a powertrain control issue. On a 2010 Toyota Prius, this typically means a door-related powered feature may not operate correctly, may stop mid-operation, or may be disabled by the vehicle as a fail-safe. Driving is generally possible if the vehicle otherwise operates normally, but you should verify that the affected door function does not create a hazard (for example, a door or latch-related power function that won’t complete, unexpected operation, or a warning that indicates the system is not in a safe state). If the issue coincides with other communication-related DTCs, multiple warning lights, or intermittent electrical problems, treat it as higher priority because it can signal a broader network, power, or ground problem affecting multiple body ECUs.

How Serious Is This Code?

B2322 is often “moderate” in severity: it can be mostly an inconvenience when it only affects a powered door motor function (loss of automatic operation, loss of convenience features, or a stored code with no current symptom). It becomes more serious when the communication stop is active/current (not just history), the condition is intermittent while driving, or multiple body/network codes appear together—those patterns can indicate an unstable power supply, poor ground, harness damage, or a network communication issue that may spread to other body functions. While B2322 is not typically associated with engine performance, body-network instability can cause unpredictable operation of features, repeated battery drain events, or false warnings. Consider it urgent if the affected door function is needed for safe entry/exit, if the system behaves unpredictably, or if the vehicle logs additional communication loss codes at the same time.

Common Misdiagnoses

Technicians often replace the door motor or the P-door motor ECU too early because the description mentions “ECU communication stop,” which sounds like a failed module. On Toyota vehicles, the more common root causes are power/ground interruptions, connector issues (loose pins, corrosion, poor terminal tension), harness damage in a flexing area, or a network line problem that prevents stable communication. Another frequent mistake is focusing only on the door assembly and ignoring related ECUs or the network gateway/body control context; a shared power supply, shared ground, or shared communication splice can take the module “offline.” To avoid wasted spending, confirm whether B2322 is current or history, verify scan tool communication with the involved ECUs, check for companion communication DTCs, and perform voltage-drop and continuity checks at the module connector before condemning any ECU.

Most Likely Fix

The most frequently confirmed repair directions for B2322 on Toyota vehicles are restoring reliable electrical supply/ground and restoring reliable communication path to the P-door motor ECU. Practical first wins often include cleaning and reseating connectors, repairing pin-fit problems, and correcting harness damage or poor splices that intermittently open when the door is moved. If wiring integrity, powers/grounds, and network line integrity check out and the communication stop remains current, then module-level diagnosis becomes more likely; in that case, replacement of the P-door motor ECU or related control unit may be considered, typically followed by Toyota-specific initialization/calibration and verification with a capable scan tool. Do not treat module replacement as certain until inputs/outputs and network health are proven good.

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