P1391

Comprehensive diagnostic guide for OBD-II code P1391

PowertrainManufacturer SpecificModerate

Quick Answer

What P1391 Means

Comprehensive for OBD-II code P1391. This affects your vehicle's manufacturer specific system.

Most Likely Cause

Multiple possible causes - see diagnostic details below

Moderate DIY

Difficulty varies depending on the specific cause.

Address Soon

Generally safe to drive short-term. Have it diagnosed soon.

Safe to Drive (Short-Term)

Generally safe to drive short-term. Have it diagnosed soon.

Need Personalized Help?

Our AI can help diagnose your specific situation and answer follow-up questions.

Ask MechanicGPT

Detailed Diagnostic Information

Overview and scope

  • Code class: P1391 is a powertrain diagnostic trouble code (DTC). OBD-II DTCs cover powertrain and related systems; the exact meaning of a given P-code can vary by manufacturer, so OEM service information should be consulted for the precise definition on a specific vehicle.
  • Real-world context: In the NHTSA real user complaints database, a complaint described braking performance loss with the ABS/Brake/Traction warning icons illuminated and a P1391 code reported in the ABS system. This is a brake/ABS symptom set that can be related to wheel-speed sensing, ABS hardware, or a timing/reference input issue in some vehicle architectures. This single complaint illustrates how P1391 can appear with braking/ABS warnings, but does not define the root cause for all vehicles.

Symptom description (useful to match the case)

  • Primary complaint (from the real-world example): During hard braking, the brake pedal felt softer and less responsive. Subsequently, the ABS, Brake, and Traction warning icons illuminated. P1391 was reported in the ABS system. This combination is typical of ABS/wheel-speed sensor problems, ABS module faults, or related wiring, but the exact interpretation of P1391 is vehicle-specific.

What P1391 might mean (two common interpretations)

  • Engine/ECU interpretation (timing reference perspective): On many platforms, P1391 is associated with timing reference signals (e.g., crankshaft/camshaft timing references or sensors) that are not detected or are out of expected range. This interpretation is engine-control-centric and is a separate domain from the ABS/traction-control domain, though some manufacturers assign a P1391 within the engine control module's domain or have cross-watch between engine and ABS subsystems. OEM service information will confirm the exact definition for a given vehicle.
  • ABS/vehicle dynamics interpretation (ABS/TC context): Some systems may report P1391 in the ABS module context as a problem with the timing reference input to the ABS controller or a related signal/communication issue that the ABS module uses to synchronize wheel-speed data. The NHTSA complaint example aligns with this ABS/traction brake-side presentation.

Probable Causes

Because the NHTSA data for P1391 is limited (a single complaint mentioning ABS/brake symptoms), the probabilities below blend that data with common diagnostic patterns for P1391-type issues. Percentages are rough likelihood estimates to guide priority, based on how often ABS/wheel-speed-related issues appear with braking symptoms in reported cases and common failure modes observed in practice.

  • Wheel speed sensor or tone ring / wiring harness issues (open/short, contamination, damaged connector, sensor grounding): 40%
  • ABS control module, pump, or hydraulic controller fault (faulty module, internal fault, or communication issue to other controllers): 20%
  • Engine timing reference related fault (crank/cam sensor or timing chain/belt synchronization or related wiring, depending on OEM interpretation): 15%
  • Wiring/ground issues or power supply problems affecting ABS or engine sensors (battery/alternator voltage dips, corroded grounds, harness chafing): 15%
  • Other related faults (mixed fault codes, intermittent sensor signals, or a separate non-P1391 fault that triggers ABS/TC lights): 10%

Important Notes

  • P1391 definitions vary by manufacturer. Always verify with OEM service information for the vehicle in question. Because the NHTSA data set is limited, you should rely on vehicle-specific fault code definitions and data streams when forming a repair plan.

Diagnostic Approach

1) Safety and initial validation

  • If braking performance is compromised or ABS/Traction lights are on, perform a cautious, controlled diagnostic environment test. Do not rely on aggressive braking in public traffic; use a safe lot or workshop area.
  • Confirm P1391 is current (active) and check for any additional DTCs stored in the ABS module and other controllers (engine, transmission, BCM). Note freeze-frame data (engine RPM, vehicle speed, braking status, sensor data).

2) Data collection and symptom correlation

  • Read ABS/TC-related data streams with a high-quality scan tool. Look at wheel-speed sensor values, ABS active status, Pump/Valves status, and any fault codes in the ABS controller and related modules.
  • Check engine data if the interpretation might be engine-timing related: crankshaft position sensor, camshaft position sensor data, engine RPM stability, misfire indicators, and related DTCs.

3) Visual and physical inspection (ABS and brake domain)

  • Inspect all wheel-speed sensors and wiring:
    • Look for damaged, corroded, frayed, or loose connectors at the wheel hubs.
    • Inspect sensor reluctor (tone ring) teeth for damage, contamination, or debris.
    • Verify sensor mounting distance and any foreign material that could affect readings (rust on tone rings, metal shavings, dirt on sensors).
  • Inspect ABS modulator/pump and hydraulic lines for leaks or contamination; check for signs of water intrusion or corrosion in the ABS module area.
  • Check the brake system for safety-critical issues that could affect pedal feel (brake fluid level, condition of brake lines, master cylinder function). Note: a soft pedal can be associated with tire/wheel sensor issues, but a hydraulic problem can also lead to misleading pedal feel.

4) ABS/wheel-speed sensor fault path (primary for this symptom set)

If the data indicate abnormal or inconsistent wheel-speed signals:

  • Test each wheel-speed sensor:
    • Resistance/continuity with the harness disconnected; compare against manufacturer specs (typical ranges vary by sensor type and vehicle; consult OEM specs).
    • Check for shorts to ground or to power, and verify shielding integrity.
  • Inspect the sensor wiring harnesses for chafing or pinched wiring, especially at harness routing along suspension components.
  • Inspect tone rings for damage, missing teeth, or debris; ensure there is no excessive play in the sensor mounting.
  • Clear codes, cycle ignition, and drive at a safe speed to observe data in the real-time stream. Confirm that wheel-speed readings synchronize properly and that no sensor is reporting zero or wildly off values.

5) ABS module and system integrity (secondary for this symptom set)

  • If all wheel-speed sensors appear healthy but the ABS/TC warning lights remain, inspect the ABS control module power supply and grounds. Poor voltage or grounding can cause intermittent sensor readings to be interpreted as faults.
  • Check for fault codes specifically tied to the ABS module (e.g., "module fault," "internal fault," or communication errors on the CAN bus or LIN bus if applicable).
  • Consider OEM-recommended tests such as module communication checks and, if indicated, targeted module diagnostics or reflash/reprogramming per OEM procedures.

6) Engine timing reference path (if engine-side timing interpretation is suspected)

  • If the vehicle exhibits engine symptoms (rough running, misfires, stalling) or if the OEM definition points to timing reference signals:
    • Verify crankshaft position sensor and camshaft position sensor operation in the data stream (watch for glitches, loss of reference, or inconsistent phasing).
    • Inspect the timing belt/chain, tensioners, and sprockets for wear or misalignment per the service intervals.
    • Verify mechanical timing alignment if there is any evidence of engine timing discrepancy.
    • Inspect engine grounds and battery/charging voltage, since voltage dips can produce spurious sensor readings.
  • If a timing reference fault is confirmed, follow OEM service procedures to replace faulty sensors or realign timing as required.

7) Confirm and verify repair

  • After performing the remediation (sensor replacement, wiring repair, ABS module service, or timing-related repair):
    • Clear the codes and perform a road test or test-drive under controlled conditions.
    • Monitor ABS/wheel-speed data to confirm proper readings and absence of fault codes.
    • Confirm that the ABS, Brake, and Traction icons are no longer displayed and that pedal feel returns to normal.
    • Re-check for any new codes that may appear after the repair.

8) Documentation and customer communication

  • Record all findings, diagnosed causes, parts replaced, and calibration or programming performed.
  • Explain to the customer how the symptom (soft pedal during hard braking with ABS/Traction lights) can be caused by a wheel-speed sensor issue, ABS module fault, or timing/reference signal concerns, and why the OEM service information is essential for definitive interpretation on their vehicle.
  • Provide driving recommendations and a follow-up plan if any intermittent issues recur.

Repair Options

  • Wheel-speed sensor / tone ring / wiring issues: replace sensor(s) or repair wiring, fix tone ring, secure connectors.
  • ABS module / hydraulic system fault: service or replace ABS module or related hydraulic components; reflash if required by OEM.
  • Engine timing reference fault (crank/cam sensor or timing chain/belt issues): replace faulty sensor(s), repair timing components, or re-torque/realign timing as per OEM.
  • Wiring/ground/power supply problems: repair grounds, replace damaged harness sections, correct power supply issues; verify battery/charging system health.
  • Other intermittent faults: locate and fix based on OEM diagnostics and additional DTCs.

This diagnostic guide was generated using verified reference data:

  • NHTSA Consumer Complaints: 1 real-world reports analyzed
  • Wikipedia Technical Articles: OBD-II

Content synthesized from these sources to provide accurate, real-world diagnostic guidance.


Consider professional help if:

  • You are not comfortable performing the diagnosis yourself
  • The issue requires specialized tools or equipment
  • Initial repairs did not resolve the code
  • Multiple codes are present simultaneously
  • The vehicle is still under warranty

Frequently Asked Questions

What does code P1391 mean?

P1391 indicates Comprehensive diagnostic guide for OBD-II code P1391. This is a powertrain code related to the manufacturer specific system. When your vehicle's computer detects this condition, it stores this code and may illuminate the check engine light.

Can I drive with code P1391?

You may be able to drive short distances with P1391, but it should be addressed soon. Extended driving could lead to additional problems or increased repair costs.

How much does it cost to fix P1391?

Repair costs for P1391 typically range from $100-$800, depending on the root cause and your vehicle. Diagnostic fees are usually $50-$150, and actual repairs vary based on whether parts need replacement. Get multiple quotes for the best price.

What causes code P1391?

Common causes of P1391 include sensor malfunctions, wiring issues, mechanical failures in the manufacturer specific system, or related component wear. The specific cause requires proper diagnosis with a scan tool and visual inspection.

Will P1391 clear itself?

P1391 may temporarily clear if the underlying condition improves, but the root cause should still be diagnosed. If the problem persists, the code will return.

Important Disclaimer

This information is for educational purposes only. We are not licensed mechanics. Always consult a certified mechanic for diagnosis and repair. Improper repairs can be dangerous.

Last updated: 2025-11-26

P1391 diagnostic guide by MechanicGPT