Couldnt really find a section for this..

[festy]

one more try for tonight, I think i had one of the checksums backwards.

[The1]

ok just had a play around with it.

Going by antus's readings, i havn't learnt yet, but i just changed a bit to test and check.

Original 348,982

Code: Select all

C0 B5 E1 13 FF 00 DF 20 FC 03 D3 2C 6E 91 BE 41 
FC 03 D3 2C 6E 91 BE 41 FC 03 D3 2C 6E 91 BE 41

So i changed it to this, which is the 3 to 4 in the hundred thousands
448,982

Code: Select all

C0 B5 E1 13 FF 00 DF 20 FC 03 D3 22 6E 91 BE 41 
FC 03 D3 2C 6E 91 BE 41 FC 03 D3 22 6E 91 BE 41

I fired it up but still read the same, so i read the chip back again and it's changed the bottom row back to 2C and left the top one alone

Code: Select all

C0 B5 E1 13 FF 00 DF 20 FC 03 D3 22 6E 91 BE 41 
FC 03 D3 2C 6E 91 BE 41 FC 03 D3 2C 6E 91 BE 41

[festy]

There's 3 copies of the numbers - you changed two of them (which both failed the checksum check) but because the third copy was still 'valid' (checksum was ok) it used that one, and "repaired" the two "corrupted" data sets
Edit - it only repaired one, not both. Interesting...

[The1]

arh ok, ill get it

I tried your test3, still 555, lol it even writes 555 back into the code. This is what i read out after.

Code: Select all

C0 B5 E1 13 FF 00 DF 20 0E F1 B7 48 D3 2C 95 6A
0E F1 B7 48 D3 2C 95 6A FF 00 55 AA 55 AA 55 AA

arh, 6:30am start, i think i best hit the sack

[The1]

So i wonder is the first line model specific? The first one from antus was a vn, the bottom i also pulled from a vn, the middle one i pulled from a vs

Code: Select all

300,609KM
01 01 D9 26 FF 00 DF 20
FC 03 F3 0C 9F 60 6F 90
FC 03 F3 0C 9F 60 6F 90
FC 03 F3 0C 9F 60 6F 90

348,982KM
C0 B5 E1 13 FF 00 DF 20 
FC 03 D3 2C 6E 91 BE 41 
FC 03 D3 2C 6E 91 BE 41 
FC 03 D3 2C 6E 91 BE 41

358,604KM
01 01 D9 26 FF 00 DF 20
FD 02 53 AC 9E 61 DF 20
FD 02 53 AC 9E 61 DF 20
FD 02 53 AC 9E 61 DF 20

[festy]

I was wondering if that was it, or whether they were storing settings for other functions in the dash.
The first word doesn't have it's own checksum, the second word is checksummed, but relates to the first word - i.e. word 0 = 0101, then word 1 will be D926 it would seem.

Which means there's nowhere left to hide another checksum - all other words are accounted for.
Does your bench dash work with all 3 of those bins you posted? And what model was your dash out of?

Here's mine (vp so i was told), translated to MSB hex and LSB hex:
(last column is the format your dumps are in if I've done this right...)

Code: Select all

addr 0: 31611 7b7b dede
addr 1: 257 101 8080
addr 2: 255 ff 00ff
addr 3: 1275 4fb 20df
addr 4: 7905 1ee1 7887
addr 5: 13515 34cb 2cd3
addr 6: 13515 34cb 2cd3
addr 7: 31110 7986 9e61
addr 8: 7905 1ee1 7887
addr 9: 13515 34cb 2cd3
addr 10: 13515 34cb 2cd3
addr 11: 31110 7986 9e61
addr 12: 7905 1ee1 7887
addr 13: 13515 34cb 2cd3
addr 14: 13515 34cb 2cd3
addr 15: 31110 7986 9e61

[The1]

the trip unit im using was out of the VS cluster, the other vn cluster i had i used the lcd driver board to fix my vs cluster which died, so i still had the vn mainboard here which i removed the chip and tested in the vs board which works, so i have two 24c44 chips here, i have tested both the vs and vn bins and they all work on this cluster, i have also tried myself changing the numbers and updating the checksums as you explained a few pages back but i get 555,555 error as well, so looking for any other differences came down to that first part of the first line, but similar clusters seem to have the same line. So there's not much left.

So if yours is right then first line variation for models is this

Code: Select all

VN
01 01 D9 26 FF 00 DF 20
VP
DE DE 80 80 FF 00 DF 20
VS
C0 B5 E1 13 FF 00 DF 20 

[festy]

I just changed my word 0 to 0101 and odo still correct, so that one's not critical...

[festy]

but... word 1 was updated to d926 when i powered up the dash, that starts to explain the relationship between the two.

[The1]

so i guess the question is how does the first bit relate to the 3 odo parts