Your first OBD2 connection: car, adapter and phone
Your first goal is simple: receive a reading from the car. Work through each stage so you can distinguish a phone-to-adapter connection from a responding vehicle control unit.
This guide covers SC OBD2 Legacy 6.1.27.13 (1063), the public reference version. Alpha 7.1.x screenshots may show different controls.
Connect step by step
- Check the exact vehicle and adapter combination, supported protocol and manufacturer’s instructions. An ELM327 label alone does not establish compatibility. Choosing an adapter.
- With the car parked, locate the diagnostic socket using the handbook, plug in the adapter and check that it has power. Follow the vehicle instructions for ignition and engine state.
- For Bluetooth, follow the manufacturer’s pairing procedure and select the correct device in the app. For Wi-Fi, join the adapter’s network and use its documented address and port, not settings for a different model.
- Grant the permissions requested by your Android and app versions. An in-app setting does not grant an Android permission. End other connections that are using the same adapter.
- Start the connection in SC OBD2. Check its status, then open Live data and look for a supported reading. Bluetooth pairing or joining a Wi-Fi network alone does not show that the vehicle has responded.
- Once data arrives, check the value and unit. Continue to read fault codes or choose the parameters to display.
If readings do not arrive
| Where it stops | Focused check | Next milestone |
|---|---|---|
| Adapter not visible | Power, Bluetooth or Wi-Fi, and the exact adapter’s connection procedure. | The expected device or network is visible to the phone. |
| Phone connected, app disconnected | Selected device and transport, permissions, Wi-Fi address/port, another app holding the connection. | The app opens communication with the adapter. |
| Adapter responds, no vehicle readings | Required ignition/engine state, vehicle protocol and exact error message. | At least one supported reading arrives from the vehicle. |
| Only one parameter is missing | Support for that parameter, reading conditions, and inputs if it is a calculation. | A listed parameter is not proof of an available reading. |
Change one setting at a time and keep the result. Do not erase profiles or history or reinstall the app just to repeat a connection check.
What to include in a support request
Note your app and Android versions, adapter model, connection type and the last stage reached in the table. Include the exact message. Do not send passwords, VINs, tokens or personal addresses. Get support.
Explore SC OBD2 · SC OBD2 on Google Play
Author: Nicola Santini / Smart Control.