How to Use a Car Code Reader Safely
To use a car code reader, park safely, follow the reader's ignition instructions, connect to the 16-pin diagnostic socket, read and save every code, then interpret the result for the exact vehicle. Do not clear codes until the evidence is recorded and the cause has been addressed.
If the car is overheating, smoking, losing oil pressure, running roughly or showing a flashing warning, stop and seek help rather than continuing a tutorial.
Before connecting
- Park off the road, select neutral or park, apply the parking brake and switch off accessories.
- Check the vehicle handbook and the reader manual. Some tools request ignition on with the engine off; others collect live data only with the engine running.
- Make sure the phone has charge and the correct app if the reader is wireless.
- Record the warning colour, whether it is steady or flashing, the mileage and the symptoms.
For a new driver in an older first car, practise finding the port and opening the app at home. The roadside is the wrong place to learn while frightened by a new symbol.
How to use a car code reader in eight steps
- Find the socket. It is commonly beneath the dashboard near the steering column, but location varies. Use the handbook rather than forcing a plug into a similar connector.
- Inspect without dismantling. If pins look bent, wet or damaged, stop. Do not probe the connector with improvised metal tools.
- Insert the reader squarely. The keyed plug should fit without excessive force.
- Set the ignition state. Follow the tool prompt. “Ignition on” usually means dashboard lamps on without starting, but vehicle procedures differ.
- Pair or identify the vehicle. Select the exact profile where offered. Do not accept an automatically guessed model without checking it.
- Run the scan. Read stored, pending and permanent codes. Scan relevant modules only if the exact tool and vehicle support them.
- Save the evidence. Screenshot the full code, description, status and freeze-frame data. Note symptoms and operating conditions.
- Disconnect correctly. End the session in the app, switch the ignition off if instructed, then remove the reader without pulling its cable.
Turn the result into a useful message
Send a family helper or garage a compact report: “2012 Ford Fiesta 1.25 petrol, 91,400 miles; steady amber EML after cold start; P0302 stored and pending; rough for 20 seconds; screenshot attached.” That is much safer than remotely guessing “change coil two”. The code states what the ECU detected; testing identifies why.
If the app supplies live data, change only one observation at a time and use correct units. Do not stare at graphs while driving. A passenger can observe, or a competent workshop can perform a controlled road test.
Stored, pending and permanent codes
- Stored: the ECU has logged the condition according to its criteria.
- Pending: the condition has been noticed but may need another occurrence before it becomes stored.
- Permanent: on supported systems, the record is cleared by the ECU after it confirms the fault no longer occurs, not simply by pressing erase.
Descriptions shown by an app can be generic. Verify the exact code in reliable manufacturer information, especially where bank, sensor, cylinder or module numbering matters.
When—not—to clear a code
Do not clear a code to prepare for a sale, silence an MOT warning or see whether it “stays away”. Save the evidence first. Clear only after a repair or a documented diagnostic step calls for it, with the owner's permission. The vehicle may need specific operating conditions before monitors complete again.
If the reader will not connect
- Confirm the ignition position and that the reader powers up.
- Check the app selected the correct adapter and vehicle.
- Try the documented pairing procedure once; do not repeatedly force or unplug it.
- Verify coverage for the exact year, engine and module.
- If communication still fails, stop. “No codes” and “no communication” are entirely different results.
For warning-light severity, read check engine light: what to do. For code meanings, use the common error-code guide.
Product-page note
ScanVia currently lists a wireless XTOOL OBD2 code reader at £95.57. Confirm the exact model, vehicle/function coverage, app requirements and current terms before ordering; this article does not extend the product page's claims.
Frequently asked questions
Do I start the engine before connecting a code reader?
Follow the reader and vehicle instructions. Many scans begin with ignition on and engine off; live-data checks may require the engine to run.
Can I leave a Bluetooth code reader plugged in?
Only if the manufacturer explicitly supports it for your vehicle. Some adapters can draw power or create connection and security concerns, so remove it after the session unless instructed otherwise.
Why does the reader say no communication?
Possible causes include the wrong ignition state, pairing, unsupported protocol or module, connector power or a vehicle fault. It does not mean the car has no faults.
Should I erase a code after taking a screenshot?
Not automatically. Interpret and address the cause first. Clearing may remove useful evidence and reset monitor status.
Sources
- RAC, engine, DTC and OBD codes (accessed 20 July 2026).
- The AA, engine management light guidance (accessed 20 July 2026).
- DVSA, MOT inspection manual: engine malfunction indicator lamp (accessed 20 July 2026).