Sounds like that byte is the battery capacity in 0.5Ah since when new it is reported as 66 Ah which would be 132 or 84h and slowly degrading from there. Cor
> On Jan 27, 2017, at 2:28 AM, Tom Parker via EV <ev@lists.evdl.org> wrote: > >> On 27/01/17 13:36, Collin Kidder via EV wrote: >> >> Any logs anyone could send me from a Leaf would be great. But, I might >> be on to something. Byte 4 (the fifth byte if you start counting at 0) >> is always a constant value for a given car. It stays the same across >> all 0x5C0 frames, it stays the same whether driving or charging. Every >> vehicle I've got a capture from has a unique byte here that never >> changes with any captures from that car no matter what else the car is >> doing. Pretty much all of the rest of the bytes change as you charge >> or discharge. I think what might be happening is that this byte is a >> sort of identifier that the rest of the system uses to see whether the >> pack is the same one it last knew. 256 unique values might not seem >> like a lot but that means that your odds of getting a pack with the >> same byte as your old pack is 1/256 or less than 0.5% - not so likely. >> One way to test this would be to set up a man in the middle >> configuration and then change that byte and see if it makes the car >> puke. Or, take a car with a replaced pack and try to change the >> reported byte from the new LBC to the reported byte from the old LBC >> and see if the car then wants to work better. > > I don't see a constant here. With the exception of one capture, each capture > from my car has a single value in byte 4 but it is decreasing (except once > when it went down and up) slowly over the last year or so for which I have > data: > > Each line represents one capture and has the following format > byte_number value_in_hex:count_in_decimal > > 4 84:7 > 4 84:12 > 4 84:14 > 4 84:80 > 4 84:252 > 4 84:128 > 4 84:10 > 4 84:14 > 4 82:1607 > 4 82:40 > 4 82:22 > 4 82:91 > 4 80:40 > 4 80:4332 > 4 7e:14 > 4 7e:53 > 4 7c:531 fe:1 > 4 7c:36 > 4 7c:19 > 4 7c:6 > 4 7a:72 > 4 7c:8 > 4 7c:22 > 4 7c:8 > 4 7c:28 > 4 7c:30 > 4 7c:1 > 4 7a:40 > 4 7a:165 > 4 7a:38 > 4 7a:54 > > The exception was captured during remote climate control, and I have 531 > frames with 7c with one frame containing fe about 2/3 of the way through the > capture: > > 157227 2017-01-07 08:38:05.031301 LBC 0x5c0 16 STD: > 0x000005c0 c0 72 74 00 7c d4 00 00 > 157533 2017-01-07 08:38:05.531215 LBC 0x5c0 16 STD: > 0x000005c0 00 fe fe 00 fe fc 00 00 > 157227 2017-01-07 08:38:05.031301 LBC 0x5c0 16 STD: > 0x000005c0 c0 72 74 00 7c d4 00 00 > > I have 2 short captures made on the same day from a Gen 2 and there it > alternates between two values: > > 4 ba:5 c0:2 > 4 ba:8 c0:4 > _______________________________________________ > UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub > http://lists.evdl.org/listinfo.cgi/ev-evdl.org > Read EVAngel's EV News at http://evdl.org/evln/ > Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA) > _______________________________________________ UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub http://lists.evdl.org/listinfo.cgi/ev-evdl.org Read EVAngel's EV News at http://evdl.org/evln/ Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)
