![]() i'm planning to install this BMS in my leaf's trunk as an extender with a home built 21700 NCA pack. ![]() I'm fooling around with what appears to be a grey/black BMS (2015) and a white wiring harness (2011). If the first response starts with 0x07, this is the number of databytes.īut if the first byte of the response starts with 0x10 then the second byte contains the total number of following databytes without each first byte of the following responses ![]() ID: 7BB DLC: 8 Data: 03 59 02 4E FF FF FF FF (zero DTC's returned) Then the first read DTC command returns zero errors like this: ID: 7BB DLC: 8 Data: 01 54 FF FF FF FF FF FF (command executed ?) ID: 79B DLC: 8 Data: 04 14 FF FF FF 00 00 00 (do something else ?) ID: 7BB DLC: 8 Data: 02 50 C0 FF FF FF FF FF (? The FF on the last 0x7BB is probably a trigger that this was last error data. Some data in the first reply causes the subsequent 0x79B to fire or not. ID: 7BB DLC: 8 Data: 22 00 4E 33 DD 00 4E FF (this contains DTC code P33DD 004E ) ID: 7BB DLC: 8 Data: 21 4E 33 D7 00 4E 33 D9 (this contains piece of previous DTC and subsequent DTC codes P33D7 004E and P33D9 004E To request all subsequent data is with the familiarĪnd then all codes come flowing in 0x7BB packets. ID: 7BB DLC: 8 Data: 07 59 02 4E D0 00 00 4E (response contains somewhat coded U1000 004E) The return is in 0x7BB datagrams and contains the actual codes. Here's a piece of logging with just one error: 'U1000 004E': ![]() The byte width errorcode in 0x5C0 is just for quick diagnoses or something. It's like expected, they use the 079B 0x7BB system to request all DTC codes from the LBC. Ok I think got it how it works with the DTC error codes I can probably mimic some of these to get rid of the error but in the end it probably wont make a difference when just using the LBC and batteries. I guess the LBC wants to see some datagrams from other components like the VCM. Looking into the EVB manual it says U1000 error is caused by lack of some CANbus datagrams for at least 2 seconds. Haven't looked at what happens when clearing DTC's but assume they use this in somewhat similar way. ![]() Not very usable but interesting to see how they use this 0x79B and 0x7BB request/response system.Īnd obviously there are a lot more groupID's then i have seen sofar in de DBC files. Maybe it is just an array of messages and number 96 is just this particular Pcode and there's no fancy coding at all.ĭuring peeking and poking around I noted when requesting the LBC/ECU version number it is 'hidden' in the group 131 and 132, each group with 4 frames, within the 0x7BB response datagrams. So I will code some lines that spit all 256 possible errorcodes on the CANbus and see what Pcodes pop-up in the LeafSpy. LeafSpy won't reveal the decoding?Īnd as always its more fun trying to find the 'flag' myself.Īnyway, I tried to trigger other faults by pulling the temp sensors and see what happens.įunny thing is I still get one error per sensor, one error per 2 sensors or one error per 3 sensors. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |