OBD-II trouble code
P0575: Cruise Control Input Circuit
On a lot of modern vehicles the cruise switches do not connect to the engine computer at all — they report to another module over the network. The circuit named here may not be a wire, and that changes where you look.
Quick facts
- System
- Powertrain
- Category
- Cruise Control
- Severity
- Low severity
- Drivable
- Usually safe to drive short-term
- Repair cost range
- $0 – $700
- DIY difficulty
- Intermediate DIY
What does P0575 mean?
P0575 identifies the cruise control input circuit without a letter, without a named button and without saying whether the reading was too high or too low. It is the general-purpose entry in a family whose other members are specific, and each of those omissions tells you something.
The absence of a letter matters most. Codes that carry one — the multi-function input "A" family, for example — are describing a specific numbered input among several. This one describes the input path as a whole: the route by which a driver's request reaches the module that acts on it. And the single most useful fact about that route on a modern vehicle is that it very often is not a wire.
For decades cruise switches ran on copper from the steering wheel to the engine controller, and diagnosis was continuity and voltage. That is no longer the general case. On a large proportion of vehicles built in the last fifteen years or so, the steering wheel controls terminate at a body control module or a dedicated steering column module. That module reads the buttons locally, works out what was pressed, and publishes the result as a message on the vehicle network. The engine controller never sees a switch. It sees a data frame.
The practical consequence is significant and it is where most of the time on these gets wasted. If a network message is the input, there is no wire between the switch and the engine controller to test, because none exists. A lost communication fault, a bus wiring problem or a module that has dropped off the network will produce this code with every switch, contact and conductor in perfect condition. So the first move is to determine which module owns the cruise input on your particular vehicle. Get that wrong and you can spend an afternoon under a steering column proving that a healthy circuit is healthy.
The second thing this code's vagueness tells you concerns what other codes are present. The low and high siblings exist to report a reading outside a defined window. When the module stores the general code instead of one of those, it is saying the input failed a test that was not a simple range check — a signal that appeared briefly and vanished, a value that sat inside the legal window but did not correspond to any real button, or a message that did not arrive when it should have. That is the signature of an intermittent, and intermittents are found by watching live data over time and by disturbing connectors, not by taking single measurements and comparing them to a table. If a low or high code is stored alongside this one, that reasoning does not apply and you have a hard fault to find, which is the better outcome of the two.
Common causes
- Loss of the network message carrying the cruise request from another module
- Bus wiring fault or a module that has dropped off the vehicle network
- Intermittent open in the switch wiring where it is hardwired to the receiving module
- Worn clockspring ribbon inside the steering wheel interrupting the input briefly
- Poor ground at the module that reads the cruise input, offsetting everything it measures
- Corroded or partially seated connector at the column or under the dash
- Failed switch assembly producing values that do not correspond to any real button
- Module software or configuration mismatch after a replacement part was fitted without programming
Symptoms
- Cruise control working sometimes and not others, with no pattern the driver can name
- Cruise control unavailable with no indicator or warning of any kind
- Communication or lost-module faults stored in other modules alongside this one
- Other steering wheel controls behaving oddly at the same time
- Fault appearing after a module, steering wheel or airbag replacement
- Cruise control returning to normal after the battery is disconnected, then failing again later
- Check engine light with the engine running exactly as it should
- No low or high companion code stored, which is itself a clue
Diagnostic steps
- 1.Answer the ownership question first: which module on this vehicle actually receives the cruise switches? On older designs the switch wiring runs to the engine controller. On many newer ones it runs to the body controller or a steering column module, which then broadcasts the driver's request over the network. Service data will tell you in a couple of minutes and it decides whether the rest of this diagnosis is done with a multimeter or with a scan tool.
- 2.Scan every module, not just the powertrain. If cruise requests arrive over the network, a lost communication or bus fault stored in another module is not a coincidental extra finding — it is the fault, and no amount of probing under the steering column will improve it.
- 3.Note carefully whether a low or high sibling code is stored alongside this one. This code arriving alone is meaningful: it means the module rejected the input without either range test catching it, which points at something intermittent or at a value that is technically in range but does not make sense. This code stored together with a low or high code is a hard, present fault and a much easier day.
- 4.Read the cruise input in live data with the key on and the engine off, and simply watch it for a minute with nothing touched. A parameter that wanders on its own, with no hand near the wheel, is telling you the input is unstable rather than absent.
- 5.If the switches are hardwired to the receiving module, back-probe at the module connector rather than at the switch. Testing at the module end means a good reading has already proven the switch, the clockspring and the whole harness in one measurement, which is a far better use of the first test than starting at the wheel.
- 6.Check the power and ground feeding the module that owns the cruise input before condemning anything. A module with a marginal ground misreads inputs it is otherwise perfectly capable of reading, and the giveaway is a scattering of unrelated input faults stored together.
Repair cost
$0 – $700
The range is wide because the cause space is wide. A connector that is not fully seated or a terminal pushed back out of its lock costs nothing to correct once found. A clockspring is $60 to $300 for the part plus one to two hours, because the airbag has to come off the wheel to reach it — $200 to $550 fitted, and not a first job for someone who has never handled a live restraint device. Repairing bus wiring runs $150 to $450, most of it labour spent locating the break. If a module needs replacing and programming, expect $400 to $900 and up. Diagnosis is $80 to $180 and is worth more on this code than on most, because determining which module owns the cruise input is the step that decides whether the repair is a ten-minute connector or a day of network tracing.
Estimate your repair
Run the numbers for your vehicle
Open the Repair Cost Estimator with cruise control switch / stalk replacement preselected. Adjust labor rate and vehicle category to fit your situation.
DIY vs shop
This is an intermediate DIY job. It usually involves diagnostic steps, specialty parts, and some careful work in tight spaces. If you have the tools and a service manual or trustworthy video for your specific vehicle, it is achievable in a weekend. Otherwise, a competent independent shop will be faster.