
THE ESSENTIALS BEFORE YOU START
- The port, diagnostic protocol and available data are three different things.
- A fault code describes a detected problem, not a repair to carry out automatically.
- The app relies on what the vehicle and adapter can actually transmit.
What is OBD2 for?
OBD stands for On-Board Diagnostics. The vehicle monitors certain systems, particularly those related to the engine and emissions. When it detects an anomaly, it may store a diagnostic trouble code, or DTC, and turn on a warning light.
IN PRACTICEA check-engine light comes on: the stored code gives a first starting point. Further checks help explain why it appeared.
How does Car AI access the information?
A compatible adapter plugs into the diagnostic port and connects the vehicle to your phone. Car AI can then display accessible information and help you interpret it in a conversation.
- Check the vehicle and adapter.
- Follow Car AI’s pairing steps.
- Check when the data was last updated.
What data can you read?
Depending on the setup, readings may include engine speed, coolant temperature, vehicle speed, engine load or fuel trims. Not every vehicle provides the same values.
IN PRACTICECoolant temperature and engine load percentage measure different things. Start by understanding each reading’s unit and context.
What should you do with a fault code?
Record its exact description and context: warning light, vehicle behavior, date and conditions. An explanation helps prepare the checks, but the precise cause requires a diagnosis appropriate to the vehicle.
Standard OBD2 and manufacturer data
Standard OBD2 diagnostics cover the engine and emissions in particular. A compatible port does not mean that ABS, airbags or traction battery data will be accessible. Those readings may depend on the manufacturer, protocol and adapter. Car AI presents the data available for your setup.
Find this information in the app.
Connect your adapter step by step