U1006 — 5 documented meanings by make

U1006 does not mean the same thing on every car — manufacturers reuse the number for different faults. 8 makes document it: Audi, Chevrolet (USA), Chrysler, Ford, Mazda, SEAT, Skoda, Volkswagen. Find your make below.

U1006 on Audi, SEAT, Skoda

On Audi, SEAT, Skoda vehicles U1006 is documented as: NOx sensor 1, bank 1, no communication. U1006 is stored when the ECU sees no signal on SCR / AdBlue system (bank 1, sensor 1). That describes how the circuit is behaving, not which part has failed — the wiring, the connector and the component itself can all produce it, which is why the checks below start with the cheapest.

Usually one of: Module has no power or no ground; Broken bus wire or a bad splice in the network; The module itself has failed; Terminating resistor or bus fault taking the network down.

Check first, cheapest first:

1. Check power and ground at the module before suspecting the module itself
2. Read whether other modules on the same bus also report faults — that separates a network fault from a single module
3. Inspect connectors at the module and any inline joints
4. Measure bus resistance across the two lines at the diagnostic socket
5. Replace the module last, once supply and network are proven good

Related Audi, SEAT, Skoda codes:

U1006 on Chevrolet (USA)

On Chevrolet (USA) vehicles U1006 is documented as: Loss of serial communications for class 2 devices.

Related Chevrolet (USA) codes:

U1006 on Chrysler

On Chrysler vehicles U1006 is documented as: J1850/PCI bus circuit low. U1006 is stored when the ECU sees signal too low on the circuit named in the code. That describes how the circuit is behaving, not which part has failed — the wiring, the connector and the component itself can all produce it, which is why the checks below start with the cheapest.

Usually one of: High resistance in the supply or ground path, dragging the signal down; Corroded connector adding resistance the module reads as a low reading; Sensor drifted out of tolerance with age; Partial short to ground somewhere in the signal line.

Check first, cheapest first:

1. Read the live value on a scanner and compare with a known-good reading
2. Clean and re-seat the connector, then re-test before replacing anything
3. Check the ground point for that circuit — a poor ground causes this far more often than a bad sensor
4. Measure the sensor against specification with the connector back-probed
5. Replace the sensor only once the wiring and ground have been ruled out

Related Chrysler codes:

U1006 on Ford, Mazda

On Ford, Mazda vehicles U1006 is documented as: SCP J1850 communications bus fault. U1006 is stored when the ECU sees malfunction on the circuit named in the code. That describes how the circuit is behaving, not which part has failed — the wiring, the connector and the component itself can all produce it, which is why the checks below start with the cheapest.

Usually one of: Wiring or connector fault in the circuit; Component failed electrically; Supply or ground problem feeding the circuit; Controlling module fault, though this is the least common of the four.

Check first, cheapest first:

1. Read all stored codes — a general fault code is often the symptom of a more specific one
2. Inspect the connector and wiring for the named component
3. Check supply and ground at the component
4. Measure the component against specification
5. Replace the component once wiring and supply are ruled out

Related Ford, Mazda codes:

U1006 on Volkswagen

On Volkswagen vehicles U1006 is documented as: SCP (J1850) Invalid or Missing Data for Primary Id. U1006 is stored when the ECU sees range or performance on the circuit named in the code. That describes how the circuit is behaving, not which part has failed — the wiring, the connector and the component itself can all produce it, which is why the checks below start with the cheapest.

Usually one of: Sensor reading is inside its electrical range but does not match reality; Contamination or deposits changing what the sensor sees; A mechanical fault upstream that the sensor is correctly reporting; Sensor drifted with age without failing outright.

Check first, cheapest first:

1. Compare the live value against a second sensor or a known-good figure — this code is about plausibility, not a dead circuit
2. Look for the mechanical cause first: leaks, restrictions or wear that would genuinely produce this reading
3. Clean the sensor if it is the type that fouls
4. Check freeze-frame data to see under what conditions it triggered
5. Replace the sensor only after the mechanical side is ruled out

Related Volkswagen codes:

Which one is yours

A generic OBD reader gives you the number, not which of these meanings your manufacturer assigned to it. To get to the specific one:

1. Use a brand-specific scanner — VCDS for VAG, INPA or ISTA for BMW, XENTRY for Mercedes, Forscan for Ford. It shows the manufacturer's own text rather than the generic one.
2. Read all stored codes together — the neighbouring ones usually point at which system is involved and narrow the list.
3. Check freeze-frame data: the RPM, temperature and load at the moment it triggered indicate which system was active.
4. If you have no brand scanner, tell me the make and model below and I will tell you which of these applies to your car.

Code family

U1xxx is network communication, manufacturer-specific.

Severity

Manufacturer-specific network code — a module is not answering on CAN. Check power and ground before suspecting the module.

That is what holds for U1006 in general. From here it depends on your engine — tell me which car it is and what it does, and I will give you the steps for it: real procedures, torque figures and diagrams instead of general advice.