To diagnose diagnostic trouble codes (DTCs), first you'll need to connect your vehicle. Plug in your OBDeleven device into the car's OBD2 port and connect it to your mobile app. Make sure Bluetooth is enabled and is within range of the device. If you're having issues connecting, refer to this article.
What’s new: Extra AI layer for fault explanations
With the app version 1.38.0, diagnostics received an additional AI layer which summarizes diagnostic results, explains the faults, and cross-references it with your own vehicle’s data and manufacturer resources.
Step 1: Scan your vehicle
You’ll need to scan your vehicle before reading faults. Once connected, tap to scan to check all control units.
The app will list the number of detected faults once the scan completes and show which systems have issues.
Step 2: Open the control unit list
After the scan finishes, tap the icons on the top row or the button in the middle of the screen to open the fault summary.
You'll need to scan your vehicle first. You can find instructions on how to do it in this article.
Here, you can clear all faults or tap on individual faults to read about them in more detail. You’ll also notice labels added to each fault, describing its severity. The labels can be:
High-risk – faults that require immediate attention
Medium-risk – faults that should be resolved soon but don’t prevent you from driving yet
Low-risk – faults that are less serious and can be addressed later
Step 3: View the fault description
Once you’ve opened a specific fault, you'll see tabs named About, How to fix, Freeze frame (only for Volkswagen, Audi, Škoda, SEAT/Cupra, Lamborghini, Bentley), and Resources.
The About tab provides you with a general description of what this fault means and its seriousness. You’ll also see a Google button at the top which will take you to Google results for this fault code if you want to dig deeper.
The How to fix tab will provide you with solutions on how to fix specific faults. Some fixes might be as simple as securing a fuel cap and clearing the fault, while some might require assistance from a workshop.
Step 4: Review freeze frame data & manufacturer resources
After reviewing fault information, you can also look up the freeze frame data* from when the fault occurred. It might give you more context for what happened.
*Freeze frame data is available only for Volkswagen, Audi, Škoda, SEAT/Cupra, Lamborghini, Bentley vehicles.
You can also check manufacturer-provided information about specific faults and typical operating ranges for selected control units.
Notes and tips
These fault explanations are designed to help you interpret diagnostics without needing to search online manually. However, AI-powered fault explanations might not be available for all fault codes, but if that’s the case, you’ll still be able to review technical descriptions and run an online search.
We will continue training this AI layer to provide you with even more accurate information tailored to your situation.
Important information: Some faults, such as internal processor, can't be cleared. The control unit may refuse to clear them or still display the fault after an attempt.
Also keep in mind that clearing codes does not fix the problem that caused the fault. DTCs should only be erased after correcting the conditions that caused them.
There is no way to erase individual DTCs while leaving others. In some cases, the ignition must be cycled after clearing codes before performing certain functions such as basic settings.