Loading IAR content
Results are grouped by useful content—not by paid placement or guessed parts. Describe the symptom naturally; IAR recognizes common alternate wording while keeping exact codes and vehicle details precise.
Your available vehicle context is included where the destination supports it. AI guidance stays separate from verified IAR source records.
Measures pressure on compatible systems. High-pressure direct injection requires specialized procedures.
Diagnostic toolsApplies controlled pressure to a cool system for leak inspection. Never exceed the specified test pressure.
Specialty toolsThe fuel system stores and meters fuel under controlled conditions. A no-start, lean code, odor, or hesitation can involve supply, command, air measurement, electrical control, mechanical condition, or vapor management.
System guideThe engine turns stored fuel energy into controlled torque. Good diagnosis separates a combustion problem from a mechanical, control, mounting, or support-system problem before parts are removed.
System guideThe tire is the vehicle's contact with the road. Pressure warnings, vibration, pull, noise, and wear patterns must be interpreted with the vehicle placard, tire condition, wheel mounting, and chassis condition.
System guideThe brake system converts motion into heat and controls wheel deceleration. Noise, vibration, pull, warning lamps, and pedal changes require inspection of the whole system rather than one assumed axle or part.
System guideThe cooling system moves heat away from the engine and releases it through controlled coolant flow and airflow. Overheating demands immediate safety judgment before diagnosis.
System guideThe system may be reporting low tire pressure, a sensor/communication problem, or a relearn/registration condition. Measure the tires before diagnosing electronics.
CautionThe engine or emissions control system has detected a condition that should be investigated. The lamp alone does not identify a failed part.
Assess promptlyThe engine or cooling system is reporting excessive temperature or a related protection condition. The warning does not identify whether the cause is coolant loss, airflow, circulation, control, or internal leakage.
Stop and assessThe traction-control, stability-control, or related chassis-control system has reported a fault, has been switched off, or is actively intervening. The lamp alone does not identify a failed sensor or module.
Assess promptlySeparate actual tire-pressure loss from sensor detection, compatibility, registration, and receiver concerns without guessing a universal relearn process.
Test-first procedureUse controlled pressure on a cool system to investigate leaks without opening a hot, pressurized cooling circuit.
Test-first procedureSeparate vibration caused by brake application from a shake that follows road speed before choosing a brake, wheel, tire, hub, or suspension path.
Test-first procedureSeparate missing ignition, fuel delivery, control, synchronization, and mechanical evidence after the engine is confirmed to crank.
Test-first procedureUse warning behavior, scan context, cylinder pattern, and controlled contribution evidence to separate ignition, fuel, air, and mechanical branches.
Test-first procedureCompare operating pattern, temperature data, and airflow evidence without applying a universal gauge, infrared, or fan rule.
Test-first procedureA fuel-economy complaint is meaningful only after establishing a repeatable baseline and separating normal operating changes from engine, emissions, tire, brake-drag, drivetrain, or temperature-control faults.
intermediateAn oil-pressure warning can represent actual lubrication-pressure loss or an electrical/sensor reporting fault. Because real pressure loss can damage an engine quickly, operation safety comes before diagnosis.
professional recommendedTreat gasoline or diesel odor as a safety signal first, then separate a liquid leak, vapor-system concern, refueling spill, exhaust odor, and cabin-source issue without running the vehicle beside an active leak.
professional recommendedSeparate actual low tire pressure from a TPMS malfunction, sensor, compatibility, registration, or relearn concern.
intermediateUse the first starting split—cranks or does not crank—to choose the correct electrical, authorization, fuel, ignition, or mechanical diagnostic path.
beginnerUse operating conditions, code context, cylinder patterns, and targeted tests to separate ignition, fuel, air, mechanical, and control causes.
intermediateSeparate fuel, spark, compression, timing, and security-system faults with a test-first process.
IntermediateTreat overheating as a stop-and-assess condition, then separate coolant loss, airflow, circulation, control, and combustion concerns.
professional recommendedUse steering angle, speed, throttle, braking, and road surface to separate tire, wheel, hub, bearing, CV-joint, suspension, steering, and driveline causes.
intermediateFirst determine whether the engine cannot make power, the transmission is not transferring it, or a chassis/control system is limiting torque.
intermediateClassify whether the engine stalls at idle, under load, during deceleration, immediately after starting, or with a broader electrical power loss before choosing a test path.
intermediateClassify smoke or a burning smell by location, color, timing, and nearby systems before attempting another drive or touching a hot component.
intermediateA wheel that locks, a brake that stays applied, or a vehicle that pulls with heat or odor can become a control and fire hazard. Stop driving and separate friction, hydraulic, parking-brake, mechanical, and control evidence with the exact vehicle procedure.
professional recommendedAn EVAP code identifies a monitored vapor-control condition, but the useful next test depends on whether the evidence points to a leak/sealing fault, purge-flow fault, electrical circuit fault, or an incomplete monitor.
intermediateSeparate braking pull, acceleration/load-sensitive pull, tire pull, steering/suspension faults, and alignment geometry before ordering an alignment or replacing a part.
intermediateUse road speed, steering load, acceleration/coast, gear or drive mode, and tire condition to separate wheel-bearing, tire, CV/shaft, differential, axle, and other rotating-noise paths.
intermediateThe control system reached a rich-condition diagnostic threshold for Bank 1. The data does not by itself prove an injector, fuel-pressure, MAF sensor, or oxygen-sensor failure.
Generic codeThe control system reached a rich-condition diagnostic threshold for Bank 2. The data does not by itself prove an injector, fuel-pressure, MAF sensor, or oxygen-sensor failure.
Generic codeThe generic EVAP monitor reported a system-level malfunction. The code identifies the monitored emissions system, not a failed cap, valve, hose, canister, sensor, or other specific part.
Generic codeThe generic EVAP monitor detected purge-flow behavior outside its expected strategy. The code does not prove the purge valve itself is failed; the flow path, sealing, sensing, electrical control, and vehicle-specific monitor conditions still have to be tested.
Generic codeThe EVAP monitor detected a small-leak or sealing condition. The code does not identify the physical leak location or prove which component failed.
Generic codeThe EVAP monitor detected a very small leak or inability to maintain the expected seal. The code does not identify the leak location or prove a specific valve, cap, hose, or canister failed.
Generic codeThe control system reached a lean-condition diagnostic threshold for Bank 1. The data does not by itself prove a vacuum leak, MAF sensor, or fuel pump.
Generic codeThe control system reached a lean-condition diagnostic threshold for Bank 2. The data does not by itself prove a vacuum leak, MAF sensor, oxygen sensor, or fuel-delivery failure.
Generic codeThe control module detected a misfire pattern associated with cylinder 1. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 2. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 3. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 4. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 5. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 6. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 7. It does not identify the failed component.
Generic codeThe control module detected a misfire pattern associated with cylinder 8. It does not identify the failed component.
Generic codeThe EVAP monitor detected a large-leak or inability-to-seal condition. It does not identify where the leak or control fault is located.
Generic codeThe engine did not reach the expected temperature behavior under the monitor’s conditions. The thermostat is one possibility, not the only one.
Generic codeThe control module detected intake-air-temperature sensor behavior outside its expected range or relationship. The code does not by itself prove the sensor, wiring, connector, intake condition, or control module is the cause.
Generic codeThe control module detected an intake-air-temperature sensor signal in a low range for its monitoring strategy. The code does not by itself prove the sensor, wiring, connector, intake condition, or control module is the cause.
Generic codeThe control module detected an intake-air-temperature sensor signal in a high range for its monitoring strategy. The code does not by itself prove the sensor, wiring, connector, intake condition, or control module is the cause.
Generic codeThe control module detected cooling-system temperature behavior outside its expected performance range. The code does not by itself identify a thermostat, coolant-temperature sensor, fan, coolant level, radiator, water pump, or other failed part.
Generic codeThe control module detected a malfunction in the mass-or-volume-air-flow circuit. The code does not by itself identify the sensor, wiring, intake path, power/ground, or control module as the cause.
Generic codeThe control module detected a mass-or-volume-air-flow circuit signal in a low range for its monitoring strategy. The code does not by itself prove a MAF sensor, wiring, connector, intake path, power/ground, or control module is the cause.
Generic codeThe control module detected a mass-or-volume-air-flow circuit signal in a high range for its monitoring strategy. The code does not by itself prove a MAF sensor, wiring, connector, intake path, power/ground, or control module is the cause.
Generic codeIAR does not passively record this search. Save feedback only if you want a local note that you can export later for editorial planning. VIN-like vehicle identifiers are redacted before local save.