OBD-II code family
Engine Coolant Temperature Sensor 2 Faults (5 codes)
5 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.
What these codes mean
These five entries concern engine coolant temperature sensor 2 but preserve different reported conditions. P2182 names the circuit, P2183 range/performance, P2184 low, P2185 high and P2186 intermittent/erratic. P2181 cooling-system performance is a separate report. Sensor 2 does not establish a universal radiator location, connector, cooling-loop count or relationship to the dashboard display.
The complete manufacturer code and monitor matter more than an assumed electrical-versus-mechanical divide. Ford’s 2011 model-year 6.7L diesel summary uses P2182 for a temperature-rationality comparison, with P2184/P2185 listed separately as low/high circuit checks. The general circuit title therefore does not prove an open conductor, and the dated example does not define every manufacturer’s P2182 procedure.
Range/performance does not certify healthy wiring or a correct signal. Audi’s cited 2014 CPNB table describes a radiator-outlet comparison with intake-air, ambient or fuel temperature at startup. The archived 2012 Jaguar XJ 5.0L index also lists P2183 subtypes that direct open/high-resistance and short-to-power checks. These are bounded diagnostic contexts, not one universal cold-soak comparison or a sensor-replacement rule.
Low and high describe the monitored electrical condition rather than the coolant’s actual temperature. Audi’s cited table names a grounded radiator-outlet circuit for P2184 and short to battery for P2185. A high label is therefore not proof that a sensor is electrically open, and a low label is not proof that the engine is cold. Identify the actual circuit design and prescribed test state before interpreting a scan value.
An intermittent/erratic result concerns behavior over time. The archived 2012 Panamera Turbo DME information describes signal jumps and connection, line and sensor alternatives for P2186. A steady parked reading can miss the event, while an abrupt input change is not automatically a real coolant-temperature change or a reason to bleed the system. Any substitute value or control response belongs to the installed application.
Record the full scan, suffixes, status, event data, warnings, coolant loss and recent cooling or electrical work. Have the actual component locator, circuit diagram and matched temperature-plausibility or electrical checks establish the cause. One plausible display, surface reading or cold comparison does not prove that either the signal or the whole cooling system is healthy. Ask which finding supports the proposed sensor, wiring, cooling-system or control repair and how it will be verified.
Keep clear of hot coolant, fans and belts. Do not open a hot pressurized system, bridge unknown sensor terminals, flex live wiring or use an unplugged display change as proof of a repair. Cooling, pressure relief, fluid service and setup depend on the confirmed work. Follow the vehicle’s actual temperature and coolant-loss warnings, and arrange recovery when overheating, coolant loss or unreliable operation makes continued use unsafe. A circuit code or apparently normal gauge cannot provide a safe-distance guarantee.
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.