OBD-II trouble code
P0899: Transmission Control System MIL Request Circuit High
The lamp request line between the transmission module and the engine controller is reading high or open. This is the failure direction that can silence a warning — the transmission may be reporting a fault that never reaches the dashboard.
Quick facts
- System
- Powertrain
- Category
- Transmission / Electrical
- Severity
- Medium severity
- Drivable
- Usually safe to drive short-term
- Repair cost range
- $90 – $1,400
- DIY difficulty
- Advanced DIY
What does P0899 mean?
This code and its low-side counterpart describe the same wire, but they are not equal in what they cost you. A circuit stuck low produces a lamp that is on when it should not be, which is irritating and visible. A circuit reading high or open produces the opposite and far quieter problem: the transmission module can decide something is wrong and be unable to make anything appear on the dashboard. The fault that matters may already have happened and you would have no way of knowing.
That inverts the usual order of work. On most circuit codes the sensible first move is to test the circuit. Here the first move is to scan every module on the vehicle and write down what the transmission module has stored on its own account, because that is the list of things it has been trying to tell you. A car can arrive with P0899 in the engine controller and three genuine transmission faults sitting quietly in the transmission module, none of which ever lit a lamp. Repairing the wire without reading those first means the customer drives away with a dark dashboard and the original problem intact.
The electrical detail that saves an hour is that on a pulled-up circuit like this one, an open and a short to battery voltage look identical to the module. Both leave the line sitting high, and the code cannot distinguish them. In practice the open is much more common — a broken conductor, a backed-out terminal, a corroded pin, a connector that was disturbed during other work — because the alternative requires a battery-voltage source to have found its way onto a low-current signal wire, which needs a specific and unlikely kind of damage. So the productive first test is continuity end to end with the line disconnected at both modules. It takes two minutes and it resolves the ambiguity the code cannot.
There is a real-world consequence that has nothing to do with driving and everything to do with paperwork. In jurisdictions with emissions testing, part of the test is confirming that the malfunction indicator lamp works — it must illuminate at key-on as a bulb check and extinguish once the engine runs. A vehicle whose transmission-side request path is open can still pass that bulb check, because the engine controller drives the lamp for its own purposes, but any monitor or readiness requirement that depends on the transmission module reporting through will not behave correctly, and the stored P0899 is itself a failure. A driver whose dashboard looks completely clean can therefore be refused a certificate, which is a surprising outcome from a code with no symptoms.
One architectural check is worth doing early. Not every vehicle uses a discrete wire for this. On designs where the lamp request is a network message, this code points toward the data bus and the module's ability to transmit rather than toward a single conductor, and you would expect communication codes to keep it company. Confirming from the wiring diagram which architecture you are dealing with, before you start looking for a wire that may not exist, is the difference between a focused diagnosis and an afternoon spent probing the wrong thing.
Common causes
- Open circuit in the MIL request wire between the transmission module and the engine controller
- Broken or backed-out terminal in a module connector
- Corrosion in a connector raising resistance until the line reads open
- Connector disturbed or not fully seated after unrelated work in the area
- Short to battery voltage on the request line, which reads the same as an open
- Failed output driver inside the transmission control module unable to pull the line down
- Failed input circuit in the engine control module
- Damage from a previous harness repair or an aftermarket installation
- Data bus fault on vehicles where the lamp request is a network message rather than a wire
- Transmission control module not communicating at all, so the request never arrives
Symptoms
- P0899 stored with no drivability complaint and often with no lamp on the dash
- Transmission faults stored in the transmission module that never illuminated the warning lamp
- Warning lamp that fails to come on when the transmission clearly has a problem
- Emissions inspection failure or refusal despite a clean-looking dashboard
- Communication or module codes stored alongside on networked vehicles
- Intermittent appearance that follows rough roads, temperature or recent workshop visits
- Normal shift quality and normal transmission behaviour
- Code returning after being cleared with no other symptom developing
- Transmission entering a protective mode without any dash warning to explain it
- Lamp behaviour inconsistent between key cycles
Diagnostic steps
- 1.Scan all modules first and record every code stored in the transmission module. On this code that list is the actual complaint and the wiring is why you never saw it.
- 2.Confirm from wiring diagrams whether the vehicle uses a discrete lamp request wire or a network message before looking for a conductor.
- 3.With the line disconnected at both modules and the ignition off, check continuity end to end. An open here resolves the ambiguity the code cannot.
- 4.If continuity is good, check the same wire for battery voltage with the key on, which is the much rarer alternative cause.
- 5.Inspect both connectors closely for backed-out pins, spread terminals and green corrosion, and compare pin tension against a neighbouring terminal.
- 6.Ask what work has been done recently. A connector left unseated after unrelated repairs is one of the commonest causes of this code.
- 7.Wiggle-test the harness end to end while monitoring, since an intermittent open behaves differently from a permanent one.
- 8.Verify the transmission module is powered, grounded and communicating, because a module that is offline cannot make the request at all.
- 9.On networked vehicles, check for bus errors and lost-communication codes before treating this as a single-wire fault.
- 10.Recheck the transmission module for stored faults after the circuit is repaired, and make sure the customer is told about anything that was hidden.
Repair cost
$90 – $1,400
Two costs live behind this code and they need separating. The circuit repair itself is modest: $110 to $250 for diagnosis, $90 to $300 for a connector repair with new terminals, and $120 to $450 for tracing and repairing an open conductor. A transmission control module, where the internal driver is genuinely at fault, is $400 to $1,400 with programming. The larger and less predictable cost is whatever the transmission module was unable to report while the circuit was open, which is why the scan comes before the repair estimate rather than after it. On networked vehicles where the request is a message rather than a wire, budget for bus diagnosis at $150 to $350 instead of harness work, since chasing a conductor that does not exist is the commonest way to waste money on this code.
Estimate your repair
Run the numbers for your vehicle
Open the Repair Cost Estimator with wiring harness / circuit repair preselected. Adjust labor rate and vehicle category to fit your situation.
DIY vs shop
This is an advanced DIY job. It typically requires specialty tools, scan-tool access, lifting equipment, or careful sequencing to avoid causing new failures. Plan for extended downtime and have a backup vehicle. Most owners are better served by a shop that has done this repair before.