B2592

PSD Not Fully Closed (Module Commanded Successfully)

Body Chassis/Safety Power Door Control 🟢 Low — Fix at next service ✅ Safe to Drive
💬

What This Actually Means

In plain language — no jargon

Your vehicle's Power Sliding Door (PSD) didn't fully close even though the ECU sent the command to do so—like pressing your garage door button but the door stops halfway and won't complete its movement. The module successfully commanded the action, but something is physically preventing the door from reaching its fully closed position.

⚡

Symptoms You May Notice

3 known symptoms for this code
Power sliding door remains partially open or doesn't latch completely
Door closure warning light illuminated on dashboard
Audible clicking or grinding noise from door motor during closing attempt
🔬

How Your ECU Detects This

Technical sensor logic and voltage thresholds

The ECU monitors the PSD position sensor and motor current draw during the close cycle. It expects the door to reach a fully closed position within a specific timeframe and verify closure via position feedback. If the sensor doesn't confirm full closure after the motor command completes, the fault is triggered.

Voltage & Parameter Thresholds

ParameterNormal RangeFault Condition
Door Position Sensor Signal 0.2-0.8V at fully closed position Voltage does not reach expected closed threshold within timeout
Motor Current Draw 2-8A during normal operation Excessive current (>12A) or stalled motor condition detected
🔧

Diagnostic & DIY Fix Guide

Check these in order — from cheapest to most complex
1
Door tracks and rollers
Clean and lubricate the sliding tracks and roller wheels to remove debris or rust binding the door.
2
Door weatherstripping and seals
Inspect and replace worn weatherstripping that may be catching or binding during the closing sequence.
3
PSD position sensor
Check sensor connector for corrosion or loose pins, clean contacts, and verify proper voltage signal with a multimeter.
⚠️

When to See a Professional Mechanic

Not all fault codes are safe to DIY

Code B2592 is a low-severity fault. Your vehicle is generally safe to drive to a workshop for diagnosis. However, do not ignore it indefinitely — low-severity codes often indicate developing problems that become expensive if neglected. Book a diagnostic appointment within 2–4 weeks. If you notice any additional symptoms (rough running, power loss, unusual smells), treat it as higher priority.

Safety note: OBD-II codes identify the system or circuit where a fault was detected — they do not always identify the exact failed component. A professional mechanic using live sensor data will diagnose the root cause more accurately than replacing parts based on the code alone.
🔄

How to Clear Code B2592

What happens after you fix the fault

Once the fault is repaired, B2592 can be cleared using any OBD-II scanner. Connect the scanner, navigate to "Clear Codes" or "Erase DTCs," and confirm. The check engine light turns off immediately.

The code will return if the root cause was not actually fixed. The ECM re-detects the fault within 1–3 drive cycles and sets the code again.

✅ Safe to Clear When
  • Fault has been diagnosed and repaired
  • You want to confirm the repair worked
  • Code appeared after a sensor was cleaned
⚠️ Do Not Clear When
  • Preparing for an emissions/PUC test
  • Root cause is still undiagnosed
  • Check engine light is flashing
Emissions test note: Clearing codes resets OBD readiness monitors. Most vehicles need 50–100 km of mixed driving before monitors complete. Do not clear codes immediately before an emissions or PUC inspection.