AutoLogicTools

OBD-II trouble code

P0804: 1-4 Upshift (Skip Shift) Lamp Control Circuit Malfunction

On most cars a dead dashboard bulb just goes dark. This one is monitored, so it sets a code and lights the check engine lamp instead — which is why a trivial fault arrives looking like a serious one.

Low severityPowertrainTransmission / Shift ControlDrivable short-term

Quick facts

System
Powertrain
Category
Transmission / Shift Control
Severity
Low severity
Drivable
Usually safe to drive short-term
Repair cost range
$5$900
DIY difficulty
Intermediate DIY

What does P0804 mean?

P0804 concerns the indicator that tells the driver to upshift on manual transmission vehicles fitted with a skip shift system. When the module decides the conditions are right to force the driver from first into fourth, it lights a small lamp or message in the instrument cluster so the driver knows what is being asked of them. This code sets when the module's monitoring of that lamp's control circuit finds it outside the expected range — typically an open circuit where the bulb or its driver has failed.

The thing worth understanding about this code is why a burned-out bulb produces a diagnostic trouble code at all, because on most of the car it would not. Almost every warning lamp in a dashboard is simply driven and forgotten; when the bulb dies, the lamp stops working and nobody is told. This one is different because the module measures the current flowing through the circuit as a way of confirming the lamp can actually be lit. An open filament reads as no current, the module concludes it cannot communicate with the driver, and it records a fault and illuminates the malfunction indicator lamp. So the reported severity and the actual severity are unusually far apart here: a check engine light comes on, which reasonably alarms people, and the underlying problem may be a component costing a couple of dollars.

Nothing mechanical is affected. The transmission is untouched by this code, the skip shift lockout continues to operate exactly as it did, and the car drives identically. What is lost is the notification — the solenoid may still block second and third while the driver gets no indication of why the shifter suddenly will not go where they are pushing it. That is mildly confusing rather than dangerous, though it is the one practical consequence worth mentioning.

Where the fault actually lies has shifted over time with cluster design, and that changes the repair substantially. On older vehicles the indicator is a genuine replaceable incandescent bulb in a twist-lock socket behind the cluster, and the fix is a bulb and half an hour of trim removal. On modern clusters the indicator is an LED soldered to the cluster's circuit board with no serviceable socket at all, and a failed LED or a failed driver transistor means either a cluster repair by a specialist or a replacement cluster — which on many vehicles then needs programming and mileage transfer, turning a nominally trivial fault into a genuinely expensive one. Establish which design is fitted before forming an expectation about cost.

Because this code and P0803 belong to the same feature, they get conflated, and separating them saves time. P0803 is the solenoid that physically blocks second and third. P0804 is the lamp that tells the driver about it. They sit on different circuits with different drivers and they fail independently, so having one says nothing about the other. If both are stored, treat them as two faults that happen to share a subject rather than as one fault reported twice — though a connector or a fuse common to both is worth checking first on the chance that a single cause explains them.

Common causes

  • Burned-out upshift indicator bulb in the instrument cluster on vehicles that use a replaceable bulb
  • Failed LED or driver transistor on the cluster circuit board on vehicles with a non-serviceable indicator
  • Corroded or loose bulb socket behind the cluster
  • Open or shorted wiring between the powertrain module and the cluster
  • Poor connection at the cluster connector, often after previous dash or stereo work
  • Blown fuse on the circuit feeding the indicator
  • Failed lamp driver output in the powertrain control module
  • Water damage to the cluster from a leaking windscreen seal or heater core
  • Aftermarket cluster, cluster repair or gauge modification that omitted or disturbed this circuit
  • Corrosion in the cluster connector on older or high-mileage vehicles

Symptoms

  • Check engine light on with no change whatsoever in how the car drives
  • Upshift or skip shift indicator in the cluster never illuminating
  • Shifter refusing to enter second or third with no lamp explaining why
  • Indicator staying lit continuously on some failure modes
  • Other cluster indicators or backlighting affected at the same time, pointing at a cluster-wide fault
  • Fault appearing after dashboard, stereo or instrument cluster work
  • Code returning after clearing with no drivability symptom at all
  • Emissions inspection failure caused solely by the illuminated malfunction indicator lamp
  • Skip shift solenoid codes stored alongside this one, which are a separate fault rather than the same one

Diagnostic steps

  1. 1.Confirm the vehicle has a manual transmission and a skip shift system, and identify whether the indicator is a replaceable bulb or a soldered LED. That single question determines whether this is a cheap repair or an expensive one.
  2. 2.Watch the indicator during a key-on bulb check if the vehicle performs one, since a lamp that does not participate in the sweep is already telling you it cannot be lit.
  3. 3.Check the fuse feeding the circuit under load rather than by inspection.
  4. 4.On vehicles with a replaceable bulb, remove the cluster and test the bulb directly rather than judging it by eye. A filament can be broken and still look intact.
  5. 5.Inspect the bulb socket for corrosion, heat discolouration and spring tension, since a socket that no longer grips produces exactly this code with a perfectly good bulb.
  6. 6.Check the cluster connector for corrosion and for pins pushed back out of the housing, particularly if the dash has been apart before.
  7. 7.Test continuity between the powertrain module pin and the cluster connector pin with both disconnected, wiggling the loom behind the dash while watching the meter.
  8. 8.Command the lamp with a bidirectional scan tool if the function is supported, which tests the driver and the lamp together in one step.
  9. 9.Look for signs of water ingress into the cluster — staining, corrosion on the board, fogging behind the lens — before condemning the module.
  10. 10.Treat any accompanying skip shift solenoid code as a separate fault on a separate circuit, while still checking for a shared fuse or connector that could explain both.

Repair cost

$5$900

The range here is wide because two very different vehicles set the same code. On a design with a replaceable bulb this is close to the cheapest repair in the whole library: the bulb is a couple of dollars, and the cost is trim removal to reach the cluster, so $60 to $200 at a shop and effectively free if you do it yourself. A corroded socket or a connector repair is $90 to $300. A wiring repair behind the dash runs $150 to $450 depending on how much trim has to come out. On a modern cluster with a soldered LED there is nothing to unplug: a specialist cluster repair is $200 to $500, and a replacement cluster with programming and mileage transfer is $400 to $900. Establish which type you have before accepting an estimate, because the two answers are an order of magnitude apart.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with instrument cluster repair or 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.

Related codes

Frequently asked questions

Why does a burned-out bulb turn on my check engine light?

Because this particular lamp circuit is monitored, which most dashboard lamps are not. The module measures current through the circuit to confirm the lamp can actually be lit. An open filament means no current, so the module concludes it has lost its ability to communicate with the driver and records a fault, which brings on the malfunction indicator lamp. It is an unusual situation where the warning is far more alarming than the problem — the check engine light is on because a two-dollar bulb died.

Does P0804 affect how the transmission works?

No. The transmission is entirely untouched by this code and the skip shift lockout carries on working exactly as before. The only real consequence is that when the system does block second and third, you get no indication of why the shifter suddenly will not go where you are pushing it. That is mildly confusing the first time it happens and nothing worse. Nothing is wearing, nothing is at risk, and the car drives identically with this code stored.

Can I keep driving with P0804?

Yes, without reservation from a mechanical standpoint — this is one of the genuinely harmless codes. The practical reasons to fix it are two: an illuminated malfunction indicator lamp will fail an emissions inspection in most places on its own merits, regardless of the trivial cause, and while this lamp is lit it masks the arrival of any other code. A second, more serious fault could set behind it and you would never notice, because the light is already on.

Is this the same as P0803?

No — they are the two halves of the skip shift feature and they fail independently. P0803 is the solenoid circuit that physically blocks second and third; P0804 is the indicator lamp circuit that tells the driver about it. Different drivers, different wiring, different failure points. Having one tells you nothing about the other. If both are stored, treat them as two separate faults, but do check for a shared fuse or a common connector first in case a single cause explains the pair.

Editorial context

About This Diagnostic Information

AutoLogicTools diagnostic guides explain OBD-II trouble codes using recognized code definitions, standard automotive diagnostic principles, and practical automotive context. A trouble code records a condition detected by a control module. It does not automatically identify a failed part, and the right diagnostic procedure can vary by vehicle.

Manufacturer service information, technical service bulletins, wiring diagrams, and vehicle-specific procedures should take precedence when available.

AutoLogicTools was founded by Vincent Fisk, an automotive locksmith and shop owner in San Diego with hands-on experience in vehicle keys, immobilizer systems, electrical issues, modules, programming, and diagnostics.