Volkswagen-MEB-EV-CAN-parameters icon indicating copy to clipboard operation
Volkswagen-MEB-EV-CAN-parameters copied to clipboard

Enyaq FW update causes changes to data

Open MatinF opened this issue 2 years ago • 7 comments

Hi again,

It looks like a recent FW update to the Enyaq has causes various changes to the data. For example, the HV Current changed as below:

OLD:

1662389810.759750;1;17FC007B;1;8;8;1;0;0;03221E3D55555555
1662389810.764900;1;17FE007B;1;8;8;0;0;0;07621E3D00024964

NEW (missing flow control in request, hence only 1 response frame for now)

1662890610.746300;1;17FC007B;1;8;8;1;0;0;03221E3D55555555
1662890610.750350;1;17FE007B;1;8;8;0;0;0;1008621E3D000249

Any updated version of the decoding rules?

MatinF avatar Sep 12 '22 18:09 MatinF

Hi

There has not been any changes to MEB CAN messages since ver 2.0 to ver 2.4. And I don’t think it will change with ver 3.0 either.

Mvh Conny Nikolaisen

Skickat från min iPhone 11 Pro Max

12 sep. 2022 kl. 20:57 skrev Martin Falch @.***>:



Hi again,

It looks like a recent FW update to the Enyaq has causes various changes to the data. For example, the HV Current changed as below:

OLD:

1662389810.759750;1;17FC007B;1;8;8;1;0;0;03221E3D55555555 1662389810.764900;1;17FE007B;1;8;8;0;0;0;07621E3D00024964

NEW (missing flow control in request, hence only 1 response frame for now)

1662890610.746300;1;17FC007B;1;8;8;1;0;0;03221E3D55555555 1662890610.750350;1;17FE007B;1;8;8;0;0;0;1008621E3D000249

Any updated version of the decoding rules?

— Reply to this email directly, view it on GitHubhttps://github.com/spot2000/Volkswagen-MEB-EV-CAN-parameters/issues/5, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASNPIBIIUPV6HUV4GMR4CNDV554K5ANCNFSM6AAAAAAQKXZOQQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>

spot2000 avatar Sep 12 '22 19:09 spot2000

@MatinF looks like the response is one byte longer which means it needs to be split in 2 CAN frames requireing some flow control.

rs38 avatar Jan 09 '23 08:01 rs38

Also people report EVNotify having weird consumption data with software 3.2.

https://github.com/EVNotify/EVNotify/issues/290

MattiJarvinen avatar May 12 '23 20:05 MattiJarvinen

Hello,

is there an update on this issue? I am unable to decode the current value....

ptbil94 avatar May 08 '24 16:05 ptbil94

I also had problems decoding it and the key is indeed the flow control.

Here is the initialization commands I use:

ATD ATZ ATE0 ATL0 ATSP7 ATSH 17FC007B ATCM 00000000 STCFCPA 17FC007B,17FE007B

Previously I used ATCRA which somehow messed up the flow control, and I only got the first frame back. (I'm quite a noob in CAN bus / ELM327)

If I remember correctly, a stole the ATCM and STCFCPA commands from Carscanner logs.

With the above, 221E3D will respond with multiframe response:

008 62 1E 3D 00 02 49 A6 3E AA AA AA AA AA

where 00 02 49 A6 is the value you need to decode. Apply the forrmula from the CSV: (WW*2^32+XX*2^16+YY*2^8+ZZ-150000)/100 And you will get battery current.

tolnaiz avatar May 08 '24 18:05 tolnaiz

Hello tolnaiz,

thank you for your reply. You helped me decode the current signal. Indeed, there must be some kind of new flow control (or I was unaware of it). Furthermore, it seems as if it is possible to request multiple values at once, but I am also quite new to CAN/ELM and this feature might have existed before.

From my data, I can see the following request and responses:

Index Time CAN ID Type DLC Data 0 Data 1 Data 2 Data 3 Data 4 Data 5 Data 6 Data 7
1 1.386789e+06 1 402391163 RxDX 8 07 22 1e 3b 1e 3d 1e 3c
2 1.386789e+06 1 402522235 RxDX 8 10 12 62 1e 3b 06 fe 1e
3 1.386789e+06 1 402391163 RxDX 8 30 00 00 55 55 55 55 55
4 1.386789e+06 1 402522235 RxDX 8 21 3d 00 02 44 a9 33 1e
5 1.386789e+06 1 402522235 RxDX 8 22 3c 00 1b f5 16 aa aa

My Interpretation: Row 1 Requests IDs 221E3B (HV Voltage), 221E3D (Current) and 221E3C (HV Voltage again?) Row 2+3 Response for HV Voltage Row 4 Response for HV Current Row 5 Response for HV Voltage

I also received the HV voltage by directly requesting 221E3B, so I didn't bother decoding it again. However, I was lacking the current signal.

For me, I decoded the bytes 44 A9 33 1E in Row 4 by a different equation than you (WW2^32+XX2^16+YY*2^8+ZZ-20)/1000, but I am not 100% sure, that this conversion is correct. With your conversion I received wrong values.

Anyway, thank you for your tips, as they have helped me a lot.

Kind regards, Ptbil84

ptbil94 avatar May 10 '24 08:05 ptbil94

Hey, I think you are off by two bytes with the current. There is an error with your formula too.

I think the correct calculation in your case is: (02*2^16+68*2^8+169-150000)/100

Where you will get -13,51A which is quite plausible if you have a heavy HV consumer like AC or heating.

tolnaiz avatar May 14 '24 17:05 tolnaiz