Code
P1380
BUICK
P — Powertrain
Misfire Detected Rough Road Data Not Available
Views:
UK: 32
EN: 30
RU: 35
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
CADILLAC
P — Powertrain
Misfire Detected Rough Road Data Not Available
Views:
UK: 33
EN: 35
RU: 34
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
CHEVROLET
P — Powertrain
Misfire Detected Rough Road Data Not Available
Views:
UK: 30
EN: 29
RU: 38
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
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 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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
FORD
P — Powertrain
VCT Solenoid Valve Circuit Short or Open
Views:
UK: 32
EN: 34
RU: 32
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
GM
P — Powertrain
Misfire Detected Rough Road Data Not Available
Views:
UK: 32
EN: 61
RU: 38
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
GMC
P — Powertrain
Misfire Detected Rough Road Data Not Available
Views:
UK: 37
EN: 39
RU: 34
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
GWM
P — Powertrain
- Fault in the system - data can not be read
Views:
UK: 1
EN: 5
RU: 2
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
HUMMER
P — Powertrain
Misfire Detected - Rough Road Data Not Available
Views:
UK: 13
EN: 17
RU: 23
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
LAND ROVER
P — Powertrain
Variable camshaft timing solenoid 1 faulty functioning
Views:
UK: 9
EN: 12
RU: 18
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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
Workshop Manuals
Repair manuals for LAND ROVER
3
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop ManualLand Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop ManualLand Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop ManualYour 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
Code
P1380
LINCOLN
P — Powertrain
VCT Solenoid Valve Circuit Short or Open
Views:
UK: 29
EN: 29
RU: 30
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
MERCURY
P — Powertrain
VCT Solenoid Valve Circuit Short or Open
Views:
UK: 29
EN: 32
RU: 31
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
OLDSMOBILE
P — Powertrain
Misfire Detected Rough Road Data Not Available
Views:
UK: 30
EN: 29
RU: 30
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
Code
P1380
Other
P — Powertrain
Misfire Detected - Rough Road Data Not Available
Views:
UK: 29
EN: 30
RU: 31
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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
Workshop Manuals
Available brands with manuals
2
AUDI 11
6-speed manual gearbox 0B1, front-wheel drive — Workshop Manual (Edition 05.2014)
Workshop ManualAudi A3 (1997) – 1.6L 4-cylinder (2‑valve) Engine Mechanical Components Service Manual (AEH, AKL, APF) – Edition 07.2002
Workshop ManualAUDI A3 (2004) Workshop Manual — 2.0L FSI Turbo (4‑cyl, 4‑valve) Engine, Mechanics — Edition 03.2017
Workshop ManualAudi A3 2004 — Electrical System (Workshop Manual, Edition 02.2018)
Workshop ManualAudi A4 / A4 Cabriolet – 4.2 l V8 (5‑valve, timing chains) – Workshop Manual (Mechanics) – Edition 04.2007
Workshop ManualAudi A4 / A4 Cabriolet — Auxiliary Heater Workshop Manual (Edition 08.2004)
Workshop ManualAudi A4 / A4 Cabriolet (1.8T 4‑cyl turbo) — Motronic Injection & Ignition System Service Manual (Edition 01.2015)
Workshop ManualAudi A8 (2003) — Electrical System Workshop Manual (Edition 08.2014)
Workshop ManualAudi Q4 e-tron (Type F4) - Self-study Programme SSP 685
Workshop ManualAudi Q8 (2018) — Electrical System Workshop Manual (Edition 05.2019)
Workshop ManualAudi Servicing Manual — 7‑Speed Dual Clutch Transmission 0CJ / 0CL / 0CK / 0DN / 0DP / 0HL (Edition 05.2018)
Workshop ManualLAND ROVER 3
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop ManualLand Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop ManualLand Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop ManualYour 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
Code
P1380
SATURN
P — Powertrain
Misfire Detected Rough Road Data Not Available
Views:
UK: 31
EN: 29
RU: 32
AI status
Completed
Completed
100%
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
- Retrieve all stored and pending DTCs, plus freeze frame and event counters. Note any other misfire or sensor codes.
- Verify battery voltage and charging system. Repair any low-voltage issues and clear codes, then retest.
- Inspect connectors and wiring for crankshaft, camshaft, wheel speed sensors and common grounds for corrosion, damage or looseness.
- 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.
- Test suspect sensors (wheel speed, crank, cam) with an oscilloscope or multimeter per manufacturer procedures. Replace any that fail.
- If sensor signals are good and wiring intact, check for CAN/PCM communication errors and review module network messages. Repair communications faults.
- 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.
- 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.
- 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 :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email