A fault code is not a parts order
A scanner gives the investigation a starting point. The missing step is finding out why the monitored system produced that result.
Read the guidePut noises, fault codes and changing behaviour into context.
35 guides in view
No guides match. Try a shorter phrase or choose another category.
A scanner gives the investigation a starting point. The missing step is finding out why the monitored system produced that result.
Read the guideThe useful part of a scan is the evidence it preserves, not the moment the warning disappears.
Read the guideThe status beside a fault code helps explain how the system recorded it. It does not provide a universal severity scale.
Read the guideSome fault records preserve a small snapshot of operating conditions. Read it as a clue with boundaries.
Read the guideAn incomplete monitor says a check has not finished. It is different from a recorded failure.
Read the guideA connector that fits does not guarantee access to every control unit or every useful function.
Read the guideA connection failure belongs to the diagnostic setup first. It is not proof that the car needs a new control unit.
Read the guideA plausible-looking number can still be misread when its units or definition are missing.
Read the guideThis code describes detected misfire activity. It does not tell an owner which part to buy.
Read the guideA mixture-related code reports a control-system result. The cause still has to be established.
Read the guideAn efficiency code deserves a diagnosis of the conditions around it, not an immediate parts order.
Read the guideA few consistent observations can help more than a long list of possible causes.
Read the guideA recording can help describe a sound, provided the way you capture it stays safe.
Read the guideWhen the uneven running appears can be as useful as how it feels.
Read the guideA brief pause in response needs clear context, not repeated hard acceleration.
Read the guideAn unexpected stall is different from a normal automatic stop. Establish which one occurred before describing the fault.
Read the guideA demanding stretch of road can reveal a problem, but it is not a place to keep testing it.
Read the guideCheck the comparison before deciding that the engine has developed a fault.
Read the guideColour is a clue, but duration, temperature and the vehicle’s behaviour matter too.
Read the guideDo not turn a suspected leak into a home diagnostic experiment.
Read the guideDescribe the rhythm and conditions without reaching toward a running engine.
Read the guideThe timing of a whistle helps distinguish a usual sound from a change worth investigating.
Read the guideA delay, a harsh shift and slipping are different complaints.
Read the guideA reluctant lever needs a precise description. Forcing it is not a diagnostic step.
Read the guideA mismatch between engine speed and road speed needs attention without a home stress test.
Read the guideStrong airflow and useful cooling are separate things. Start by describing which one is missing.
Read the guideA noisy fan with little air at the vents asks a different question from strong air that is not cool.
Read the guideBefore suspecting a failed part, establish whether the climate system is being asked to produce two different temperatures.
Read the guideSeparate normal warm-up time from a new failure to produce heat, and keep cooling-system safety in view.
Read the guideRepeated misting is a visibility problem first, then a question about moisture and ventilation.
Read the guideThe location and recent use help describe a puddle, but appearance alone cannot identify every fluid.
Read the guideIdentify when the smell appears before choosing a cleaning treatment.
Read the guideDrying the visible carpet is useful housekeeping. Finding how the water arrived is the repair question.
Read the guideAn engine that has stopped can still have active cooling equipment. Keep hands away and check the context.
Read the guideWhere you feel a vibration and whether the engine itself runs evenly are separate clues.
Read the guide