OBD-II code family
Injector Control Pressure Circuit and Performance Faults (7 codes)
7 related fault descriptions. Use each full code and the exact vehicle service information to identify its circuit, monitored condition, and required tests.
Codes in this family
This is the complete published member list for this guide. Each code retains its own page; shared diagnostic context does not mean that every member has the same test or repair.
- P2283Injector Control Pressure Sensor Circuit
- P2284Injector Control Pressure Sensor Circuit Range/Performance
- P2285Injector Control Pressure Sensor Circuit Low
- P2286Injector Control Pressure Sensor Circuit High
- P2287Injector Control Pressure Sensor Circuit Intermittent
- P2288Injector Control Pressure Too High
- P2289Injector Control Pressure Too High - Engine Off
What these codes mean
These seven entries distinguish an injector-control-pressure sensor-circuit report from pressure-functional results. P2283 names the general sensor circuit; P2284 range/performance; P2285 low input; P2286 high input; and P2287 intermittent. P2288 reports pressure too high, while P2289 preserves the engine-off qualifier. Keep each complete condition rather than treating them as seven ways of ordering the same sensor.
Identify the engine, pressure medium, relevant sensor and control arrangement. Ford’s cited 2004 model-year 6.0L summary describes high-pressure oil supporting fuel injection with electronic injector-solenoid control. That bounded example does not assign the same pump, rail, valve, wiring, pressure multiplier or fallback to every vehicle carrying an ICP label.
The Ford summary separately lists low/high ICP electrical checks and pressure-functional checks. Its P2284 example is actual pressure exceeding commanded pressure, with a separate low-pressure result listed under P2290. Range/performance therefore does not universally mean a pressure shortfall or prove that the sensor and its electrical paths are healthy. An absence of an individual circuit code does not certify every signal.
High electrical input and pressure too high are different findings. P2286 does not establish a universal pull-up or prove an open wire, and P2288 does not independently confirm measurement accuracy or a failed relief valve. A regulator command beside reported pressure is useful evidence, not a parts truth table. Use the actual sensing, circuit, control and relevant mechanical checks.
The engine-off condition also has its own limits. Ford’s covered P2289 monitor specifies an engine-off pressure criterion and duration, rather than condemning any nonzero key-on display. The name does not establish a session-wide zero tare or prove that heat and connection conditions are irrelevant. A stopped engine is not permission to open a pressure circuit.
Preserve status, failure records, symptoms and recent work. An intermittent report can require protected recording because a parked check may miss the event. A spike is not automatically a terminal fault and drift is not automatically a sensor. Do not heat or freeze connections, flex live wiring, jumper reference/signal terminals, improvise a running pressure gauge or reproduce a loaded road failure.
Have the matched protected procedure establish the serviceable repair and required verification. Fluid service, sensor or connector replacement, pressure-control work and setup each need supporting evidence. Seek assistance for stalling, unsafe response, leaks or severe running concerns. The code does not promise safe travel, a predictable fallback or a universal replacement price.
Identify the circuit on your vehicle
Match the full DTC, reporting module, and any failure-type suffix to the service information for your exact year, make, model, engine, and equipment. An identifier alone does not establish installed hardware count, location, connector pinout, or a universal measurement.
Where the manufacturer publishes its own meaning for this code, that is the one to work from — it describes the actual component on your vehicle, which the generic definition cannot. Keep the generic description for what it is good for: it tells you which subject area the standard assigned the code to, which is useful context when the two appear to disagree. If they do disagree, follow the manufacturer.