P0804: deep diagnostic and measurement file for 1-4 Upshift (Skip Shift) Lamp Control Circuit Malfunction
An open technical file that diagnoses P0804 without jumping to one part by combining event data, live data, circuit measurement, physical-system evidence and repair validation.
Advanced diagnostics and measurement7 sourcesUpdated 2026-07-31
Use the code as a measurement starting point, not a failed-part label. Preserve event data and compare symptoms, likely causes, live data and physical measurements under the same operating condition.
This code is receiving real search demand. The answer remains consolidated in one strong canonical dossier instead of thin duplicate pages for query variants.
P0804 · DEEP DTC FILE
P0804: deep diagnostic and measurement file for 1-4 Upshift (Skip Shift) Lamp Control Circuit Malfunction
CODE IDENTITY
Bind P0804 to the correct module and operating condition
Code text, event data and the exact vehicle variant must agree.
P0804 base definition: 1-4 Upshift (Skip Shift) Lamp Control Circuit Malfunction. Record any OEM subtype and failure-type byte separately.
For 1-4 skip-shift lamp circuit, preserve the reporting module, software identity, current/history/pending state and mileage together.
Freeze frame must place 1-4 skip-shift command, cluster/lamp driver state, engine/vehicle load, temperatures and system voltage on one timeline.
Before clearing P0804, preserve companion DTCs, readiness/monitor state and permanent-code information.
Limit driving if the vehicle will not start, enters limp mode, or fuel, ignition or transmission safety is affected.
LIVE DATA AND CIRCUIT
Measure 1-4 skip-shift lamp circuit by command, feedback and physical response
One static voltage or a parts swap is not a diagnosis.
First data group: 1-4 skip-shift command, cluster/lamp driver state and clutch and gear-position switches; record sampling rate and units.
Second data group: vehicle speed and throttle position and PCM output-circuit current; compare command and response at the same load and temperature.
Use loaded voltage-drop testing on 1-4 skip-shift lamp circuit power, ground and signal circuits instead of unloaded continuity alone.
For intermittent faults combine connector movement, thermal change and scope/current-clamp capture.
Do not conclude from an idle snapshot without safely reproducing the condition that set P0804.
DIFFERENTIAL DIAGNOSIS
Separate electrical, hydraulic/mechanical and software paths for P0804
The same symptom can arise from different root causes.
First hypothesis: open/short in lamp or cluster circuit; counter-test power and feedback under load.
Second hypothesis: PCM output-driver fault; verify whether physical evidence and data deviation occur together.
Third hypothesis: clutch/gear-switch logic fault; do not condemn a part without an actuation test and comparison measurement.
Fourth hypothesis: aftermarket wiring modification; review service history, fluid, calibration and previous repairs.
Common trap: incorrect calibration on a variant without the feature; P0804 alone is not enough evidence for an expensive replacement.
REPAIR VALIDATION
Validate the P0804 repair under the original operating condition
Clearing the code does not prove the fault is gone.
Store before/after logs of 1-4 skip-shift command, clutch and gear-position switches and vehicle speed and throttle position.
Perform any adaptation, basic setting or relearn for 1-4 skip-shift lamp circuit only with the applicable OEM procedure.
Check pending/permanent codes, readiness monitors and related modules for new low-voltage/network codes.
Recreate the original temperature, load, speed and run-time conditions and attempt to re-trigger P0804.
Record part number, software level, instruments, test conditions and final road test in the service file.
FIELD WORKFLOW
Evidence-preserving diagnostic sequence
Preserve P0804 and every companion code before clearing.
Verify VIN, engine/transmission identity, reporting ECU and software level.
Place 1-4 skip-shift command, cluster/lamp driver state, load, temperature and voltage from freeze frame on a timeline.
Perform loaded tests on 1-4 skip-shift lamp circuit power, ground and signal circuits.
Compare vehicle speed and throttle position with PCM output-circuit current under the same operating condition.
Use counter-tests to separate open/short in lamp or cluster circuit from PCM output-driver fault.
After repair/relearn, recapture clutch and gear-position switches and the relevant command-response relationship.
Complete final validation under the original condition and check pending/permanent codes and monitors.
DIFFERENTIAL DECISION MATRIX
Connect the symptom to evidence, not a guessed part
Evidence
Observation / condition
Correct next action
Identity and event
P0804 is stored but OEM subtype or reporting module is unknown
Do not select a part until module, software and subtype are verified.
Command/feedback
vehicle speed and throttle position is commanded but PCM output-circuit current does not respond
Separate open/short in lamp or cluster circuit from clutch/gear-switch logic fault under load.
Electrical evidence
Power looks normal while clutch and gear-position switches drops intermittently
Capture connector, harness and thermal/scope evidence.
Physical system
The circuit is normal but 1-4 skip-shift command conflicts with the system model
Run physical/hydraulic tests for PCM output-driver fault and aftermarket wiring modification.
Validation
The code was cleared but the original condition was not repeated
Repeat the same temperature, load and speed; check permanent/pending status.
Exact pins, voltages, resistance, pressure, torque and test conditions must be verified against VIN-specific OEM service information and ECU software identity.
6-step technical decision tree
Verify identity
Preserve first-event data
Compare command and feedback
Confirm with physical measurement
Isolate root cause
Retest under the same condition after repair
Other names and search terms
P08041-4 Upshift Skip Shift Lamp Control Circuit Malfunction
Do not treat the code label as a parts diagnosis. Narrow root cause through freeze-frame, simultaneous module codes, power/ground, live data and active testing.
Capture freeze-frame, first/last occurrence, load, rpm, temperature, vehicle speed and system voltage.
2. Eliminate shared causes
Rule out battery/charging, power, ground, fuses, network communication and shared-reference faults before replacing parts.
3. Compare command and result
Compare commanded values with real sensor/actuator response under the same operating condition.
4. Prove the repair
Clearing codes is not enough; recreate the monitor condition and verify that code/symptom does not return.
Decision tree
This page is prioritized for deeper evidence-led coverage: reproduce symptom → capture event data → eliminate shared electrical/network causes → perform system-specific measurements → verify under the same condition.
Evidence-led DTC checklist
Capture freeze-frame/event data and a full-module scan before clearing the code.
Separate DTC status bits: active, pending and history/permanent do not carry the same diagnostic weight.
Eliminate supply, grounds, 5 V reference and network health as shared causes.
Graph ECU command against actual sensor/actuator feedback.
Load-test wiring and validate the system physically before replacing parts.
After repair, check readiness/DTC return under the same operating condition.
Verify the code against vehicle identity and system context
The same DTC can lead to different root causes across manufacturers, controllers and operating conditions. Cross-check model, engine/transmission and the measurement chain.
This powertrain context reference is intentionally kept manufacturer-aware. Confirm the exact definition for the vehicle, model year and controller before replacing parts.
1 · Capture the event
Save DTC status, freeze-frame/event data, operating state and companion codes before clearing memory.
2 · Verify identity and power
Confirm the reporting module, supply, grounds, fuses and connector condition before judging a sensor or actuator.
3 · Compare command and feedback
Use live data to compare commanded state with actual feedback under the same operating condition.
4 · Measure the circuit or system
Use the OEM procedure for pin locations and exact thresholds; separate electrical/network faults from mechanical, hydraulic, pneumatic or flow faults.
5 · Reproduce and verify
After repair, reproduce the original load and operating condition and confirm that the code and related symptoms do not return.
OTODÜNYAMAUTOMOTIVE KNOWLEDGE CENTER