ODB2 App (Car Scanner) new Honda E profile

[Reuben80]

I just realised that now on Car Scanner app there is a profile for the E. I have been waiting years for this.
However I have 2 OBD dongles and none of them are connecting to the ECU.
I have the OBDlink LX and the VLinker BM+
Can someone please let us know which one is working for them. I am interesting in buying the OBDlink Mx+ if it works.

[happyV]

There are two Apps that have "Car Scanner" in the name... which one is it?

[Reuben80]

Car scanner ELM obd2

[londiniumperson]

I have tested the Car Scanner app with the vLinker MC, the app connects to the dongle but fails to read the car modules

[Reuben80]

I have tested the Car Scanner app with the vLinker MC, the app connects to the dongle but fails to read the car modules

Yes many dongles connect to the elm but not ecu. I have bought the obdlink Mx+ but still on the way. When I test it I will let you know guys.

[stzrd]

I also tried my ProScan ELM327 OBD adapter, connects to the app but not to the ECU.

Looking forward to seeing if the one you have ordered works Reuben80! Some very useful information available through the app.

[miura88]

Same problem

[happyV]

To me it looks like the app tries to connect to the E like every other car. But the e doesn't respond how the ODB-Standard is designed (I wrote an App to read out data from the e). And therefore it fails.
Technically speaking the connection is OBD, but the data is raw CAN-Bus.

[EEEE]

My iCarSoft CR Max can read practically every module and piece of information. It plugs into the OBD port, but the OBD protocol is not for extra body module data, just the bare minimum of engine codes (not even sure how that'd apply to an EV).

You can hear the internal relays physically clicking as it must connect to various busses as it scans, not just the normal ODB/Serial one (eg CAN busses etc).

It could be quite useful if you did have a fault (The readouts and information is vast), but if you don't have any faults, I've never felt the need to plug it in again to check anything.

With it you can test various outputs and inputs, check individual stalk switches, window switches, actuate door locks / window motors and so on. Kick off various calibrations and service things. TBH though I have no interest in looking at them. You can read individual cell voltages and various other parameters.

I was pleasantly surprised that plugging it into the non OBD prelude also showed various details (small 3pin adaptor required, just a connector change, not logic level etc).

[drumbag]

The OBDII-protocol doesn't contain any EV-specific values, and is of no use for reading EV data. To get data from the Honda e, you have to use a protocol called UDS (unified diagnostic services), the same protocol used by diagnostic testers. When reading data via UDS, you only send a few queries to the car's CAN gateway and receive all the data back as long, multiplexed messages (as opposed to talking directly to the individual control units on the CAN bus). The actual content of the messages is manufacturer-specific, and needs to be reverse-engineered or interpreted using a manufacturer's database. Some of them are publicly accessible, but Honda is well known for the fact that they don't share anything.

Tools like PowerCruiseControl just use a UDS query with a database they probably reverse engineered from a diagnostic tester. As I understand, the reason that not every cheap ELM327-clone OBD adapter works with Honda e apps, is that a lot of them lack the memory required for the long multiplexed UDS messages.