mattyjf01 wrote: ↑Sun Aug 09, 2020 5:36 pm
Ve Series 2 odometer

KMs
Start__End__Range__Checksum & ^FF
65536 81919 16383 DB24
10000 13FFF 3FFF

81920 106495 24575 A758
14000 19FFF 5FFF

106496 131071 24575 8F70
1A000 1FFFF 5FFF

131072 139263 8191 DF20

20000 21FFF 1FFF

139264 163839 24575 B748
22000 27FFF 5FFF

163840 180223 16383 AF50
28000 2BFFF 3FFF

180224 221183 40959 ?
2C000 35FFF 9FFF

221184 245759 24575 1FE0
36000 3BFFF 5FFF

245760 294911 49151 ?
3C000 47FFF BFFF

294912 319487 24575 D629
48000 4DFFF 5FFF

0 kms
F50A EA15 D42B A857
50AF A15E 42BD 857A
0AF5 15EA 2BD4 57A8
AF50 5EA1 BD42 7A85

Ive worked out how it Calculates the km
But cant see the pattern for the checksum except the High byte low byte xor FF

I know this is a little old, but I’m having trouble understanding the odometer on the VE Series 2 eeprom. If someone could explain a little more on how it is calculated.
I was able to use a zero kms file then use SPS to put the corrected mileage. In the eeprom the odometer is 0x8 to 0x27
From what I can tell 0x8 to 0x17 are the main bytes. 0x18 to 0x27 are swapped bytes of the first set at least in the few bins I’ve looked at.