Missing SoC Error - Connection via obd fails for KGM Torres EVX

Hi @Hans de Vries ,

Please add more information such as;

• Vehicle model

• OBD device model

• Error messages if any given

Unless you already have, please read this article;
OBD Connection

Hello,

the vehicle is a KGM Torres EVX

The OBD Device is a Vgate Vlinker MC+

ABRP detects the dongle and connects to it successfully (step 1 and 2 of three)

When trying to link the device in abrp, I see the OBD Led flash on the device, but at 27 seconds (after 3 seconds) step three, connecting to vehicle, fails.

If I try to connect the vehicle using the OBD dongle with CarScanner, it immediately connects. I have made sure car scanner is not running when trying to connect ABRP.

This is the step where it fails:

Hi

Can you please explain a little bit more. Can you add a screen shot of the error message.

@Thomas do you need any more information? If you believe the dongle is the issue, can you please recommend an OBD2 dongle that will work?

I am running ABRP on IOS, have you guys tested that? I can try an android phone as well.

Hi all, is there any news? I extracted a brief CarScanner pro log from my dongle (which reads SoC, 91% at the time of log)

I have managed to get the PID Editor in abrp working, but can not find the correct PID for SoC. I suspect 22FD0D2 or 22EF01, but can not seem to parse the result with INT16(A:B)

@Thomas

I’ve been digging around some more using car scanner.

This seems to get the SoC from the VCU (relative state of charge)

ATSH7E0 OK

22FD0D2 7E8100962FD0D000384 7E821038200AAAAAAAA

response is E7E8100962FD0D000384 7E821038200AAAAAAAA

Car scanner decodes this as ‘data for calculation’

A:00

B:03

C:84

D:03

E:82

F:00

resulting in 89.8, which is correct.

@Thomasit appears as to get SoC a different ‘initialization’ command is needed.

ATSH761 to get all measurements except SoC from VCU

To get SoC from VCU, before requesting SoC, ATSH7E0 needs to be sent, then with 22FD0D2 resulting in two frames as described below.

INT16(B:C)*0.1 seems to give correct SoC in PID tester.

However, I can only get either SoC or the other values because of the difference in initialisation.

@Thomas

If ABRP could support multiple OBD2 commands per data-fetching command, I could get it to work. All is needed is the extra initialisation command before fetching SoC, and the default before all other values.

I have got this working reliably in PiD editor; by only switching the order of initialisation commands I can get either SoC or the other values. This is perfectly in line with the CarScanner logs.