Adapter<->Vehicle Communication sometimes not successful about ltsupportautomotive HOT 3 OPEN

Chances are our init sequence is correct, and it's rather a faulty adapter (of which there are literally thousands…).

See also brendan-w/python-OBD#22

It is also possible that most of these issues are due to electrical problems (such as incorrect seating of the adapter in the socket), or missing ignition. It is – unfortunately – impossible to programmatically decide whether ignition is on or off. ATIGN is not doing what it is supposed to. It returns ON as soon as the adapter has power.

from ltsupportautomotive.

@mickeyl I’m currently testing with OBDLink CX and it always returns that ignition is off, where clearly its on- tested with car scanner and etc.

from ltsupportautomotive.

I wonder if we can tell anything from the voltage read via ATRV. Perhaps if the engine is running, we might have a higher voltage? But I guess it doesn't help with detecting the ignition being ON but the engine not running.

from ltsupportautomotive.