android-obd

What problem does it solve?

This Skill helps Android developers reliably connect to an OBD2 adapter (ELM327 and compatible) and obtain valid vehicle data by using the correct init sequence, response handling, and protocol negotiation.

Core Features & Use Cases

• ELM327 init sequence: Ensures the adapter is reset and configured in the right order (ATZ, ATE0, ATL0, ATH0, ATSP0, ATAT1) before any PID polling.
• Robust response parsing: Reads until the ELM327 prompt character (>) and correctly strips command echo to prevent broken payload parsing.
• Vehicle protocol detection & recovery: Interprets SEARCHING/BUS INIT as expected negotiation steps, extends wait time for first-connect, and uses ATSP protocol fallbacks when UNABLE TO CONNECT occurs.
• Mode 01 PID polling + Mode 03 DTC reading: Provides PID constants, parsing patterns for common live data (RPM/speed/temp/etc.), and decoding logic for DTCs.
• Adapter-specific quirks: Includes guidance for OBDLink MX+ behavior (e.g., reflection RFCOMM channel-1, Classic vs BLE path choice, extended AT commands, one-connection-at-a-time constraints).
• Android Auto / Car App Library integration hooks: Points to Android Auto display integration patterns for live PID rendering and troubleshooting when OBD is “connected” but data is missing.

Quick Start

Ask your AI assistant to implement the full ELM327 init + PID polling loop on Android using ATZ → ATE0 → ATL0 → ATH0 → ATSP0 → ATAT1, then read responses until the > prompt and parse Mode 01 and Mode 03 reliably.