Adapter data and settings

What the app learned from the adapter, the settings that fix slow or unstable readings and how the sensors are searched.

The OBD adapter page opens from the blue information button next to the saved adapter, on the Connection screen. It gathers three cards: one to read, with what the app learned from the device, one of adapter settings and Sensor search.

One distinction matters here: the OBD protocol and the Response timeout are set per vehicle, the four settings on the second card per adapter, and the Sensor search options apply to every car and take effect at once.

  1. Check what the app identified

    The Adapter info card shows name, MAC, chip, ELM version, description, Avg latency and the dates of first pairing and last connection. Rows with no value stay hidden.

    The ELM version is the most relevant item on the card, because it decides whether grouped readings are available.

  2. Force the protocol, if the car does not connect

    The OBD protocol comes set to Auto (detect), and that is the right setting for most cars. If your vehicle never completes the connection, open the list and choose a specific protocol.

    Each option is numbered, so that support can point at an item by its number. The change applies to the active vehicle and takes effect immediately, with no need to reconnect.

  3. Adjust the response timeout

    Response timeout also starts on Adapter default, which sends no value and leaves the decision to the device. The options run from 32 ms to 1020 ms.

    Raise the value when the car answers slowly and the app stops waiting before the answer arrives. The setting applies per vehicle, and setting a value by hand discards what the app had learned.

  4. Raise the refresh rate

    On the Adapter settings card, turn on Group sensor requests. The option asks for several sensors in a single request, and it is the setting with the largest effect on reading speed.

    If the option is unavailable, the adapter reported an ELM version earlier than 1.3, which does not support the feature.

  5. Fix readings that come back empty

    If long readings of a module (advanced sensors, for example) come back blank, turn on Long response stabilization. It answers each module's long messages with flow control addressed to it, and tests itself: if long answers still arrive incomplete, the app goes back to automatic on that car and says so on the adapter screen.

    Keep Skip repeated setup commands on, which is the default. Turn it off only if the sensors stop answering, a situation that points to an adapter losing its configuration between one command and the next.

  6. Tune the sensor check

    Alternative detection of supported sensors tests the sensors one by one instead of trusting the list the ECU reports, because some ECUs publish that list incorrectly. Turn it on only if sensors the car has are missing, because every connection becomes noticeably longer.

    Group identical probes asks the vehicle each distinct question only once during sensor discovery, which makes it far faster. Turn it off only to compare results.

    On Nissan and Infiniti cars, Manufacturer sensor list (Nissan and Infiniti) asks the ECU which manufacturer sensors it serves, 32 at a time, and Open and close a diagnostic session serves modules that only answer that list inside a session, returning the module to normal reading afterwards.


← All guidesIn the FAQ: Adapters and connection →