Home / DTC / P1380 — Misfire Detected Rough Road Data Not Available

P1380 — Misfire Detected Rough Road Data Not Available

Detailed page for trouble code P1380.

34,405codes
59brands
11,914generic
22,491specific
Reset
Code

P1380

BUICK P — Powertrain

Misfire Detected Rough Road Data Not Available

Brand: BUICK
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

CADILLAC P — Powertrain

Misfire Detected Rough Road Data Not Available

Brand: CADILLAC
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

206

Browse 206 CADILLAC manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

CADILLAC

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

CHEVROLET P — Powertrain

Misfire Detected Rough Road Data Not Available

AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

456

Browse 456 CHEVROLET manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

CHEVROLET

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

CHRYSLER P — Powertrain

Misfire Detected Rough Road Data Not Available

Brand: CHRYSLER
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

193

Browse 193 CHRYSLER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

CHRYSLER

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

FORD P — Powertrain

VCT Solenoid Valve Circuit Short or Open

Brand: FORD
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

GM P — Powertrain

Misfire Detected Rough Road Data Not Available

Brand: GM
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

GMC P — Powertrain

Misfire Detected Rough Road Data Not Available

Brand: GMC
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

GWM P — Powertrain

- Fault in the system - data can not be read

Brand: GWM
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

HUMMER P — Powertrain

Misfire Detected - Rough Road Data Not Available

Brand: HUMMER
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

Repair manuals

Manual library for HUMMER

138

Browse 138 HUMMER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

HUMMER

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

LAND ROVER P — Powertrain

Variable camshaft timing solenoid 1 faulty functioning

AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

320

Browse 320 LAND ROVER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

LAND ROVER

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

LINCOLN P — Powertrain

VCT Solenoid Valve Circuit Short or Open

Brand: LINCOLN
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

166

Browse 166 LINCOLN manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

LINCOLN

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

MERCURY P — Powertrain

VCT Solenoid Valve Circuit Short or Open

Brand: MERCURY
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

296

Browse 296 MERCURY manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

MERCURY

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

OLDSMOBILE P — Powertrain

Misfire Detected Rough Road Data Not Available

AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

Other P — Powertrain

Misfire Detected - Rough Road Data Not Available

Brand: Other
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

9,429

The library contains 9,429 repair and diagnostic manuals. Choose a brand to open the full manual tree by year, model and trim.

Your experience will help others
+100 karma for a short comment :)
Send to email
Code

P1380

SATURN P — Powertrain

Misfire Detected Rough Road Data Not Available

Brand: SATURN
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Missing or corrupt rough-road/vehicle dynamics input to the PCM
  • Faulty or intermittent wheel speed (vehicle speed) sensor(s)
  • Faulty crankshaft or camshaft position sensor or signal
  • Low or unstable battery/charging system voltage
  • PCM software anomaly or corrupted memory/calibration
  • Wiring harness or connector faults (open/short/intermittent)

Symptoms

  • MIL (check engine light) illuminated
  • Possible rough or uneven engine operation when misfire occurs
  • Loss of driveability or reduced power if misfires are present
  • No specific vibration pattern flagged as rough-road by PCM
  • Recorded misfire counts in scan tool but rough-road flag absent

What to check

  • Check for additional DTCs and note freeze frame data
  • Scan live data: misfire counts, RPM, vehicle speed, wheel speed sensors, crank/cam signals
  • Check battery voltage and charging system under load
  • Inspect wiring and connectors for crank, cam, wheel speed sensors and related grounds
  • Verify proper operation of wheel speed sensors and ABS tone rings
  • Confirm PCM has correct software/calibration; check for manufacturer TSBs or updates

Signal parameters

  • Engine RPM (crankshaft position sensor)
  • Camshaft position signal
  • Cylinder misfire counters / misfire detection status
  • Vehicle speed / wheel speed sensor signals
  • Throttle position (TPS) and accelerator pedal position
  • Mass air flow (MAF) or manifold absolute pressure (MAP)

Diagnostic algorithm

  1. Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
  2. Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
  3. Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
  4. Using a scan tool, monitor live data while performing an in-vehicle test drive. Observe misfire counters, vehicle speed, wheel speed sensors, RPM and TPS to see if rough-road inputs are present.
  5. Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
  6. If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
  7. If misfires are present, diagnose and repair the root cause (ignition system, fuel injectors, fuel pressure, compression/leakdown, vacuum leaks) per standard misfire troubleshooting before concluding rough-road data problem.
  8. If no hardware faults found, check for available PCM software updates or reflash; follow manufacturer guidance for clearing P1380 after repairs and confirm with road test.
  9. If intermittent, use extended data logging or manufacturer diagnostic tools to capture events; consider replacing PCM only after exhaustive checks and manufacturer confirmation.

Likely causes

  • Bad or intermittent wheel speed sensor or related wiring
  • Crankshaft position sensor signal issues causing misfire detection ambiguity
  • Low battery/charging problem causing incomplete data logging
  • Faulty PCM or corrupted calibration/software
  • Other stored misfire-related DTCs (ignition coil, injector, fuel, compression) interfering with rough-road logic

Fault status

⚠️ Status
PCM detected misfire(s) but rough-road validation data was unavailable or invalid. Additional sensor inputs or communications are required to complete rough-road misfire processing.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1-3 hours

Similar codes

Your experience will help others
+100 karma for a short comment :)
Send to email