Use the free connection-stage checker to separate adapter power, phone access, adapter handshake, vehicle response, and module coverage before retrying.
Connect it to ScanWrench and see what your car actually returned.
Where does your scan stop?
Choose the first statement that matches. The result narrows the failed stage; it does not diagnose a vehicle or certify the adapter.
No adapter power
The scan has not reached the phone, adapter software, or vehicle network yet. Start at the physical connection and vehicle power supply.
- Park safely, switch the vehicle off, and reseat the adapter without forcing it.
- Use the ignition position required by the vehicle and adapter instructions.
- If the adapter still has no power, stop. Use the vehicle's current fuse and connector information or qualified help—never bridge connector terminals.
Do not assume: No adapter light does not identify a bad adapter, blown fuse, damaged connector, or wiring fault by itself.
Check the simple things in order
Confirm the adapter is fully seated and powered, the ignition is in the position required by the vehicle, and the vehicle battery is not obviously weak. Then confirm the phone or computer is connected to the adapter path the app expects—Bluetooth Low Energy, Bluetooth Classic, Wi-Fi, or USB are not interchangeable.
- Adapter has power and is seated correctly.
- Ignition state matches the scan instructions.
- Bluetooth, local-network, or USB permission is allowed.
- No other app or device is holding the adapter connection.
The error should name the failed step
Discovery, wireless connection, adapter handshake, vehicle protocol detection, ECU response, multi-frame assembly, and live-data streaming are separate steps. “Connection failed” hides the information needed to recover.
If the adapter connects to the phone but no controller responds, the next check belongs to vehicle power, connector pins, protocol support, adapter capability, or exact vehicle coverage—not repeated Bluetooth pairing.
Retry once, then change the evidence
A bounded retry after checking power and connection state can recover a temporary interruption. Unlimited retries can hide a failing adapter, drain a battery, or leave a frozen-looking session.
- Cancel cleanly from every waiting state.
- Reconnect and re-identify the adapter.
- Do not silently reuse an old vehicle identity.
- Keep partial results labeled incomplete.
A connection does not prove coverage
A successful second attempt proves only that the exact request completed. It does not prove the adapter can reach ABS, airbag/SRS, stability control, every manufacturer module, or state-changing functions. Record the vehicle, adapter, transport, requested function, responding controller, and result separately.
Why does my OBD2 adapter have power but not connect?
Power only proves the connector is supplying electricity. The phone-to-adapter link, adapter command set, vehicle protocol, ECU response, and app support can still fail separately.
Should I delete and reinstall the app first?
Usually not. First check adapter power, ignition state, permissions, radio or cable type, and whether another device is using the adapter. Reinstalling does not change unsupported hardware or vehicle communication.
Does a successful connection mean it can read every system?
No. Generic OBD2 normally focuses on regulated emissions information. ABS, airbag/SRS, stability control, and manufacturer functions need exact enhanced coverage, compatible hardware, and any required authorization.
THE TAKEAWAYGood retry logic recovers useful work while preserving the failure evidence needed to improve the next session.
Turn the warning into a saved record.
Use ScanWrench to capture the standardized evidence your exact vehicle and compatible adapter return. Manufacturer-controlled systems remain not checked unless exact support is verified.
ScanWrench Editorial created this issue from the platform's evidence model and current primary sources. It separates observed facts, plausible paths, decisive tests, safety limits, and remaining unknowns. Its purpose is to improve vehicle decisions; it does not replace exact manufacturer procedures or qualified professional judgment.
See how this page earns trust.
These links are primary-source starting points for the page's scope. They do not replace the current manufacturer procedure, wiring, specification, or service information for a specific vehicle.
Publisher
ScanWrench Editorial is the working byline for this library. Joshua Black, founder and publisher, is responsible for publication decisions, disclosures, and corrections.
A reviewed date means an editorial scope and safety check. It is not an ASE credential, OEM authorization, or vehicle-specific repair approval.
Primary sources
- SAE J1978-1 — OBD-II Scan Tool: First Generation ProtocolsSAE International · Primary scan-tool standard separating establishment of vehicle communication from the regulated OBD services requested after communication succeeds.
- On-Board Diagnostic regulations and requirements: questions and answersU.S. Environmental Protection Agency · Official boundary around standardized emissions-related OBD monitoring and manufacturer-controlled diagnostic information.
- If an app would like to use Bluetooth on your deviceApple Support · Current iPhone guidance for reviewing or changing an app's Bluetooth permission under Privacy & Security.
- If an app would like to connect to devices on your local networkApple Support · Current iPhone guidance for reviewing or changing an app's Local Network permission when it needs to communicate with a nearby network device.
Revision history
- Initial publication and review: claim boundaries, safety language, internal links, and cited source scope checked.
- Material update: added the interactive connection failure finder, refreshed iPhone permission guidance, and preserved the original diagnostic and safety boundaries.
No material correction is hidden. Material additions and corrections are dated above when they occur.
Report a possible correction ↗