Suzuki Diagnostics Library
Simple cars on paper, but the same rules apply: capture data first, separate air/fuel control from ignition/mechanical, and verify sensor plausibility before replacing parts.
Platform notes (UK/EU focus)
- Small petrol engines: drivability issues are often basic (air leaks, weak ignition, low fuel pressure), but they can hide behind generic codes.
- EVAP influence: purge behaviour can create a rough idle or long crank after refuel. Confirm before condemning coils or injectors.
- Sensor plausibility: a biased MAF/MAP or lazy O2 can create trims problems without setting an obvious sensor code. Use live data to validate.
- Voltage matters: low battery/charging issues can cause multi-warning events and spurious codes. Always check system voltage first.
Start here (popular models)
Swift
Small petrol triage: misfire vs mixture, EVAP traps, and sensor plausibility checks that stop guessing.
Open model →Vitara
Real-world SUV complaints: hesitation under load, EVAP and mixture control, plus simple checks before expensive parts.
Open model →Best workflow: read codes, then capture a short log (idle + steady cruise + one moderate pull). If trims and load data look sane, stop chasing fuel and look at ignition/mechanical.