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.
Separate start-request, interlock, cable, ground, solenoid, and starter-motor evidence before bypassing the circuit or replacing the starter.
Test-first procedureSeparate state of charge, battery condition, and connection problems before blaming the starter or alternator.
Test-first procedureSeparate missing ignition, fuel delivery, control, synchronization, and mechanical evidence after the engine is confirmed to crank.
Test-first procedureCheck whether the vehicle is replenishing electrical energy under its intended operating strategy instead of applying one universal voltage rule.
Test-first procedureFind resistance in a loaded power or ground path without assuming that continuity or an unloaded voltage proves the circuit is healthy.
Test-first procedureCompare operating pattern, temperature data, and airflow evidence without applying a universal gauge, infrared, or fan rule.
Test-first procedureThe control module detected a vehicle-speed-signal input below the range expected by its monitoring strategy. The generic code does not prove which sensor, wheel-speed source, wiring path, module, or communication path is responsible.
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 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 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 does not rotate when starting. Separate battery, cable, starter-control, interlock, security, and starter faults before replacing anything.
intermediateAn 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.
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.
intermediateSeparate an intermittent radio or screen reset from a complete power loss by recording what else resets, then test supply, ground, protection, network, and heat evidence before blaming the head unit.
intermediateSeparate fuel, spark, compression, timing, and security-system faults with a test-first process.
IntermediateThe starting system must authorize the request and deliver high current long enough to rotate the engine. A no-crank condition is different from an engine that cranks normally but does not run.
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 steering system changes wheel direction and returns road forces to the driver. Pull, vibration, looseness, and heavy steering should be separated from tire, brake, suspension, alignment, and road-surface effects.
System guideElectrical diagnosis follows the circuit and the evidence. A module-related code can be caused by supply, ground, wiring, communication, input, output, configuration, or the module itself.
System guideIAR 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.