Code
P1380
CHRYSLER
P — Powertrain
Misfire Detected Rough Road Data Not Available
Views:
UK: 32
EN: 38
RU: 34
AI status
Completed
Completed
100%
Causes
- Missing or invalid wheel speed/ABS sensor data
- Loss of CAN/serial communication between ABS/ESP module and PCM
- Faulty ABS, VSM or body control module that supplies rough‑road/accelerometer data
- Faulty PCM or internal software/calibration issue
- Intermittent or actual engine misfire (ignition, fuel, compression) concurrent with missing rough‑road input
- Damaged wiring, corroded connector, or poor ground in sensor/communication circuits
Symptoms
- MIL/Check Engine Light illuminated
- Stored or pending misfire-related DTCs (P03xx) alongside P1380
- Intermittent engine hesitation, bucking or reduced drivability
- Noisy or abnormal vibration perception at certain speeds
- ABS/traction control warning or loss of ABS-related functionality (if ABS module affected)
What to check
- Connect a full-function scan tool; read all powertrain and ABS/VSM/BCM modules for DTCs and freeze frame data
- Check freeze frame: vehicle speed, engine RPM, misfire counts, and conditions when P1380 set
- Verify wheel speed sensor signals (live data) on all wheels while rotating wheels or during road test
- Check CAN bus/communication status and any module communication errors
- Inspect wiring and connectors for ABS, wheel sensors, and PCM for damage or corrosion
- Check battery voltage and ground integrity; low voltage can cause comms issues
Signal parameters
- Wheel speed (per wheel)
- Vehicle speed
- Engine RPM
- Misfire counters / cylinder contribution
- Crankshaft position sensor signal
- Camshaft position sensor(s)
Diagnostic algorithm
- Use a scan tool and read all modules. Record P1380 plus any other DTCs and freeze frame data.
- Clear DTCs and perform a controlled road test capturing live data: monitor wheel speeds, vehicle speed, engine RPM and misfire counters. Attempt to reproduce code conditions.
- If misfire counters increase while ABS/wheel speed or rough‑road data are absent or invalid, focus on communications and wheel/ABS sensors.
- Verify ABS/wheel speed sensor signals at each wheel. Wiggle test harnesses, inspect connectors for corrosion or damage.
- Check CAN bus continuity and look for intermittent module communication errors; repair wiring or connectors as needed.
- Scan ABS/VSM module for its own DTCs and address them. Reprogram/update ABS/PCM software if TSB or update exists.
- If communication and sensor data are good but misfires occur, perform ignition/fuel and mechanical tests: inspect spark plugs/coils, fuel pressure/flow, injectors, and perform compression or leak‑down tests.
- Repair or replace faulty sensor/module (wheel sensor, ABS module, harness, PCM) only after confirming the root cause. Clear codes and re-test under the same conditions to verify resolution.
- If intermittent or hard-to-reproduce, instrument vehicle with datalogging through multiple driving conditions (including rough surfaces) to capture the event.
Likely causes
- Failed wheel speed sensor or ABS wheel sensor wiring
- ABS/VSM module has DTCs or is not communicating on the CAN bus
- PCM software bug or out‑of‑date calibration requiring reflash
- Loose/dirty connectors at ABS or PCM harness
- Actual misfire causes (bad plug/coil/injector, low fuel pressure, low compression) that coincided with missing rough‑road data
Fault status
Status
Misfire detected but rough‑road/vehicle vibration data required by the misfire monitor was unavailable or invalid. Check wheel speed/ABS sensors, module communications, wiring/connectors, and investigate concurrent misfire causes.
Repair difficulty: Medium
Diagnostic time: 1.5-4.0 hours
Similar codes
Your experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email