Your check engine light just came on and you have no idea what it means. You could ignore it, you could rush to a workshop, or you could read the fault code yourself using a cheap adapter and your phone. OBD2 (On-Board Diagnostics, version 2) is a system every modern car uses to monitor the engine and other systems. Reading a fault code is simple, but interpreting what it actually means takes a bit more knowledge.
What is the OBD2 port and where to find it in your car
The OBD2 port is a standardized sixteen-pin connector found in every car sold in the European Union since 2001 (petrol engines) and since 2003 (diesel engines). It sits below the steering wheel on the driver's side, usually slightly to the left of the steering column. Sometimes it's covered by a plastic cap or hidden behind a small panel in the lower dashboard trim.
If you can't spot it right away, check your car's owner manual or simply search for your model online. The port is always within the driver's reach because technicians use it during every diagnostic session or vehicle inspection.
What you need for reading fault codes with your phone
For basic fault code reading you need two things: an ELM327 Bluetooth adapter and a free app on your phone. The adapter is a small device that plugs into the OBD2 port and wirelessly sends data to your phone. It costs roughly the same as two oil filters and is available from most local online electronics shops. There are also Wi-Fi versions that work better with iPhones, since iOS doesn't have open access to the Bluetooth protocol used by the cheaper adapters.
One important note about the adapter itself: there are versions v1.5 and v2.1. The v2.1 is often a cheaper clone that works unreliably with the CAN protocol — the protocol most modern cars use. The v1.5 adapter with a PIC18F25K80 chip works more reliably and that's the one we recommend looking for. The box or product description usually states which chip is inside.
As for apps, Torque Lite is popular on Android, and Car Scanner works on both platforms. Both are free in their basic versions and perfectly adequate for reading and clearing fault codes.
How to read a fault code step by step
- Plug the ELM327 adapter into the OBD2 port while the engine is off.
- Turn the ignition on (you don't need to start the engine — just turn the key to position two or press the start button without pressing the brake).
- Enable Bluetooth on your phone and pair it with the adapter. It usually shows up as "OBDII" or "ELM327" in the device list.
- Open the app and let it connect to the adapter. Once the connection is established, the app will automatically detect your car's protocol.
- Go to "Read Fault Codes" and wait a few seconds.
- The app displays a list of fault codes with short descriptions in English.
The entire process takes 2 to 3 minutes. When you're done, you can turn off the ignition and unplug the adapter. If the app shows no faults but the warning light is still on, it's possible that your adapter doesn't support your car's protocol or that the fault is stored in a module the generic adapter can't access.
What a fault code really tells you — and what it doesn't
Every fault code starts with a letter followed by four digits. The most common ones begin with P (powertrain). P0xxx codes are generic and mean the same thing on every car: P0420 points to a catalytic converter issue, P0171 to a lean fuel mixture, P0300 to misfires. Besides P codes, there are also B (body), C (chassis), and U (network communication between modules), but generic adapters often can't read those.
P1xxx codes are manufacturer-specific and their meaning varies from brand to brand. For those codes you typically need dedicated software or experience with the particular manufacturer.
Here's the key thing to understand: a fault code tells you WHAT the car's computer detected, but it doesn't tell you WHY it happened. Code P0300 says there are misfires, but it doesn't say whether the problem is a spark plug, an ignition coil, low compression, or bad fuel. A fault code is a symptom, not a diagnosis. It's like someone telling you "you have a headache" without telling you what's causing it.
When clearing a fault code helps and when it just hides the problem
Most apps offer a one-tap option to clear fault codes. The check engine light turns off and at first glance the problem seems solved. But this is where most drivers go wrong.
If the fault was caused by a one-off event that won't repeat (bad fuel, a momentary sensor contact loss), the light will stay off and the problem really is gone. But if there's an active fault, the light will come back after a few minutes of driving or after one or two ignition cycles. In the meantime, the computer loses the fault history and data about how long the problem has been present.
Clearing a fault code without fixing the underlying issue can cause additional damage. An engine running with a faulty oxygen sensor burns more fuel and puts extra stress on the catalytic converter. If you keep clearing the code every time it pops up, the catalytic converter can fail — and that's a far more expensive repair than replacing the sensor. It's especially risky to clear codes before a vehicle inspection hoping the light won't come back in time.
When you still need professional diagnostics
The ELM327 adapter is useful for basic generic fault code reading, but it has clear limitations. Professional diagnostic tools like VCDS (for the VAG group) or Delphi units can read manufacturer-specific faults that a generic adapter simply can't see. On top of that, professional tools display live data in real time: fuel trims, oxygen sensor voltages, turbo boost pressure, and temperatures at various points in the system.
That information is what allows a mechanic to go from a fault code to an actual root cause. When you come into the workshop with a fault code you read on your phone, that's a useful starting point. We immediately know which direction to look, but the final diagnosis is based on live data, measurements, and experience with the specific engine.
If the warning light keeps coming back after clearing, if you have multiple faults at the same time, or if you notice a change in how the car behaves, don't rely solely on what the app shows you. Book an appointment and we'll run a full diagnostic on professional equipment.