Skip to content
OBDScan
FeaturesHow it worksCompatibilityPrivacyFAQ
English
EspañolEnglishالعربيةDeutschΕλληνικάSuomiFrançaisहिन्दीBahasa IndonesiaItaliano日本語한국어Norsk bokmålNederlandsPolskiPortuguêsРусскийSvenskaTagalogTürkçeУкраїнськаTiếng Việt简体中文

Support

One person answers the email. There is no call centre and no chatbot.

Before writing, it is worth ruling out the most common causes: nearly everything reported turns out to be an adapter that does not behave as advertised, or a signal the vehicle simply does not expose.

Write to me

For bugs, suggestions, privacy questions or requests about your data.

israel.alvarado.segura.dev@gmail.com

Replies on working days. Write in English or Spanish; other languages are fine too, though the reply will take longer.

What to include in your message

The more of this that comes in the first email, the sooner it is solved:

  • Vehicle make, model and year, and whether it is petrol, diesel, hybrid or electric.
  • Phone model and Android or iOS version.
  • OBDScan version, shown in Settings → About.
  • ELM327 adapter brand and connection type: Wi-Fi, BLE or classic Bluetooth.
  • What you expected to happen and what happened instead.
  • A screenshot if you can. It does not need to include the VIN.

The most common questions

The adapter will not connect

Wi-Fi: the phone must join the network the adapter itself creates, from the system settings, before connecting in the app. The default IP and port (192.168.0.10:35000) are common, not universal: check the manufacturer's. Classic Bluetooth: pair first from the phone's settings using the manufacturer's PIN, then tap Refresh in the app. BLE: the adapter must expose a compatible UART; the FFF0/FFF2/FFF1 profile is an editable example, not universal auto-detection.

Sensors I expected are missing

OBDScan only shows the PIDs your ECU declares it supports, and that set varies enormously between vehicles of the same year. If a sensor does not appear, the vehicle does not advertise it on the standard channel. Transmission, ABS, airbag and hybrid-system data usually travel over manufacturer-proprietary protocols that the app deliberately does not decode, so as not to show false values.

I cleared a code and it came back

That is the expected behaviour: clearing turns off the light, it does not repair the cause. If the code reappears, the fault is still there. A permanent code is not even removed by the clear command: it disappears when the ECU itself verifies that the problem is resolved, after completing its monitoring cycles.

The map is blank

Map tiles need an internet connection. If you are joined to a Wi-Fi adapter's network, the phone usually has no internet access that way. The app keeps drawing the route on its own canvas with the markers and readings, and tells you why there is no map.

The trip did not start by itself

Automatic recording requires exceeding 20 km/h on two consecutive samples, so that an isolated GPS spike does not create a false thirty-metre trip. If you want to record from a standstill, tap Start now: a manual start consults no threshold.

I want to take my data with me

Export trips in .obs format, which both Android and iOS open, and sessions in CSV or JSON with the original values in SI/OBD units. Everything goes through the system file picker. Do this before changing phone: there is no cloud copy to restore.

OBDScan

Honest OBD-II diagnostics: it tells you what the ECU says, and it also tells you what it cannot know.

Product

  • Features
  • How it works
  • Compatibility
  • Download
  • Support

Legal

  • Privacy notice
  • Terms and conditions
  • Acceptable use policy
© 2026 OBDScan Not affiliated with any vehicle manufacturer, adapter maker or store.