Comprehensive diagnostic guide for OBD-II code P0590

Title reference: P0590 - Cruise Control Input Circuit (B) Stuck / Stuck Input B to Cruise Control

What This Code Means

• Official context: P0590 is a powertrain diagnostic code in the OBD-II framework. The OBD-II literature classifies codes like this under Powertrain Codes, which cover emissions-related and control-system faults that affect engine and drivetrain performance.
• Open-source code definition: An available GitHub/open-source entry translates P0590 as

Key points to keep in mind

• P0590 is considered a Cruise Control input circuit fault, typically related to the circuit that provides the cruise-control module (CCM) with the "input B" signal. The fault can be in the wiring, a switch, the CCM itself, or the PCM/ECU interpreting the signal.
• This guide uses general OBD-II diagnostic practices. When multiple DTCs are present, address P0590 in a prioritized manner and verify other codes as they can influence cruise-control-related diagnostics.

Symptoms

• Cruise control will not engage, or it may engage and immediately disengage, depending on the underlying fault.
• The cruise message light or cruise control indicator on the dash may illuminate or behave erratically.
• Brake pedal or clutch pedal input issues can complicate the symptom pattern (since brake/clutch inputs are part of cruise-control control logic).
• Intermittent behavior: sometimes it works, sometimes it does not, often depending on wiring movement or connector seating.
  Note: Symptoms described reflect standard cruise-control input circuit concerns and are consistent with the concept of a stuck Input B signal.

Probable Causes

Important: do not include NHTSA complaint data for P0590. I've included probability ranges based on typical field experience diagnosing cruise-control input issues and the general behavior of input-circuit faults.

• Stuck or poor-detected Input B signal due to wiring/connectors or a faulty switch (most common)
  • Estimated likelihood: 40-55%
  • Why: Input B is an electrical signal path to the CCM/ECU; common failures are harness wear, connector corrosion, pin oxidation, or a switch that is sticking or not changing state properly.
• Faulty brake pedal switch, clutch switch, or related interrupt circuits
  • Estimated likelihood: 15-25%
  • Why: These switches provide a critical input to cruise control logic (disable/enable). A stuck or intermittent switch can mimic or cause a "stuck input" condition in the cruise-control input path.
• Faulty cruise control relay or power supply to the CCM
  • Estimated likelihood: 15-20%
  • Why: A relay stuck closed/open or a marginal power feed can produce a misread input condition or fail to energize/de-energize the CCM correctly.
• Cruise Control Module (CCM) fault (internal)
  • Estimated likelihood: 5-15%
  • Why: CCM failure or internal fault can misinterpret or fail to provide proper input signaling to the PCM/ECU.
• Powertrain Control Module (PCM/ECU) software/logic fault
  • Estimated likelihood: 5-10%
  • Why: Less common, but software or calibration issues can misread or ignore the Input B state.
• Other wiring or grounds issue (less common)
  • Estimated likelihood: 5-10%
  • Why: Grounding or inter-system interactions can create signals that appear as a stuck input.

Diagnostic Approach

1) Verify and scope the problem

• Confirm the DTC P0590 is current with the vehicle's on-board computer. Read freeze-frame data to see the state of the vehicle when the fault occurred (speed, load, pedal position if captured). This helps prioritize tests.
• If other DTCs appear, note them and consider addressing allied faults in the same area before isolating P0590.

2) Perform a visual and mechanical inspection

• Inspect all visible wiring harnesses around the cruise-control components, especially around the CCM, brake switch, throttle body area (if applicable), and the relay sockets.
• Check for loose, corroded, damaged connectors, pin oxidation, or signs of chafing in the Input B circuit path.
• Inspect fuses related to the cruise control system and the CCM power supply.

3) Check power and grounds

• Verify the CCM has proper power and ground. A marginal supply can cause an incorrect Input B state or an inability to process input changes.
• Inspect for battery voltage stability during key-on and key-off testing if required.

4) Functional test of the brake/clutch input circuit

• Test the brake pedal switch (and clutch switch if equipped). With ignition on, measure the brake switch position input to the CCM/PCM. A stuck or inconsistent switch can be read as an Input B fault in some vehicles.
• Confirm proper operation of the brake switch: pedal up = open/ground state as designed; pedal down = closed/grounded state, depending on the circuit topology.
• If applicable, test the cruise control cancel/resume switch behavior as part of the input path.

5) Test the Input B circuit wiring

• Use a multimeter to verify continuity of the Input B wire from its connector to the CCM/ECU, and back to the brake switch if that circuit is involved.
• Check for shorts to ground or to supply voltage along the Input B circuit, and verify there are no open circuits.
• If available, use an oscilloscope or a scan-tool live data feature to observe the Input B signal in real time. Look for a signal that is stuck high or stuck low. A signal that changes state with pedal manipulation or brake switch operation typically indicates wiring or switch health; a signal that never changes suggests a switch, relay, CCM input, or ECU interpretation fault.

6) Inspect and test the Cruise Control Relay and the CCM power input

• If a relay controls CCM power or the input path, swap the relay with a known-good unit or test its operation in-circuit. A faulty relay can mimic a stuck input condition.
• Verify that the CCM receives clean power and that the relay contacts aren't welded or degraded.

7) Evaluate the Cruise Control Module (CCM)

• If wiring, power, and input switches test good, consider CCM health (internal fault). Some vehicles permit CCM reflash/updates; verify there are no service advisories or software updates for the CCM related to cruise control.
• If a CCM fault is suspected, SES/tech data or a module replacement/repair may be required.

8) Consider PCM/ECU software or calibration issues

• Check for known service bulletins or updates related to cruise control behavior. A software fault or calibration mismatch can create incorrect input interpretation.

9) Clear codes and road-test

• After repairing any wiring, switches, fuses, or the CCM, clear the DTCs and perform a road-test to verify that P0590 does not return.
• Monitor live data during the test to confirm Input B changes as expected when engaging, adjusting, and canceling cruise control.

What to fix first (practical prioritization)

• Start with the lowest-risk items: inspect wiring/connectors, test brake/clutch switches, check fuses and relays.
• Proceed to CCM power/ground checks, Input B continuity tests, and then CCM replacement only if the signals and power are correct but the fault persists.
• Software updates or recalls should be checked early if available for your vehicle.

Notes

• When working around cruise control wiring and the CCM, ensure proper battery disconnect procedures as needed to avoid unintended throttle or electrical issues.
• Follow standard shop safety practices when testing electrical circuits, and avoid accidental engagement of the throttle or cruise control during diagnostic testing.

Duty-cycle and testing considerations

• Some vehicles implement Input B as a discrete switch input, while others may interpret it via CAN or a dedicated line to the CCM. Use the appropriate test method for your vehicle (multimeter for discrete lines; live dataCAN/ODD viewer for digital lines).
• If you must perform any reprogramming or software updates, follow the manufacturer's guidelines and ensure you have the correct calibration for your vehicle.

What to include in your final report

• Vehicle information: year, make, model, engine, CCM part number (if replaced), and any updates performed.
• DTCs found, including freeze-frame data and the state of Input B when the fault occurred.
• All tests performed (visual inspection, power/ground checks, switch tests, continuity tests, relay checks, live data observations, and any replacement parts).
• Root cause determination and repair performed.
• Post-repair verification: DTC cleared, road-test results, and any re-test data.

This diagnostic guide was generated using verified reference data:

• Wikipedia Technical Articles: OBD-II
• Open-Source OBD2 Data: N/A (MIT)

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

---