VDO NEC+64 Virgin Countdown?

[Lidahus]

In the memory area 0x10C0 until 0x1173 I found a number of data which seems to be related to virgin information of this cluster. I fed just terminal 30 by +12V and traced I?C bus. After releasing RESET and after about 15 seconds run time I found that ?P overwrites some of this data with 0xFF. On used clusters I found 0xFF on all cells of mentioned area. Is this a kind of countdown until virgin status will be void?

[Lidahus]

Found that area 0x10C0 until 0x1173 contains cluster fault information. Starting at 0x10C0 error code is 10 Bytes each.

10 C0    FF FF FF FF FF FF FF FF FF FF
10 CA    FF FF FF FF FF FF FF FF FF FF
10 D4    10 02 FF 00 0E 03 00 00 01 FF
10 E0    FF FF FF FF FF FF FF FF FF FF
10 EA    FF FF FF FF FF FF FF FF FF FF
10 F4    FF FF FF FF FF FF FF FF FF FF
11 00    FF FF FF FF FF FF FF FF FF FF
11 0A    FF FF FF FF FF FF FF FF FF FF
11 14    FF FF FF FF FF FF FF FF FF FF
11 20    FF FF FF FF FF FF FF FF FF FF
11 2A    FF FF FF FF FF FF FF FF FF FF
11 34    FF FF FF FF FF FF FF FF FF FF
11 40    FF FF FF FF FF FF FF FF FF FF
11 4A    FF FF FF FF FF FF FF FF FF FF
11 54    FF FF FF FF FF FF FF FF FF FF
11 60    FF FF FF FF FF FF FF FF FF FF
11 6A    FF FF FF FF FF FF FF FF FF FF

Actually dump above shows a check sum error.

Wondering why a virgin cluster shows 11 error codes including the check sum error.

[Lidahus]

I had this error entry persistent on the cluster. VCDS shows following:

10485825 - Internal Control Module Memory Check Sum Error 
          B2000 41 [137] - General checksum failure
          MIL ON - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 2
                    Mileage: 1044480 km
                    Date: 2000.14.00
                    Time: 00:00:01

Did you find the correlation according to my previous post? Odometer shows 231km, no idea where the 1Mio came from. There was no way to clear this error entry, just to poke 0xFF into the error entry at 0x10D4. Now this error is gone.

[hansdevogel89]

thx very much for this solution

[H2Deetoo]

When you power up a cluster on bench, you get many many errors because of missing sensors and signals.
This results in filling up the DTC area -> 0x10C0 and up

[H2Deetoo]

Some errors you cannot erase using DTC command, like internal checksum error for example.
I guess they are "important" enough to be maintained for later analyse. As you found out already the only way to erase them is to erase DTC area in eeprom.

[Elektrik001]

Big Thanks Lidahus !!!! Your solution work with dash 3T1920841M Superb II 2015

[uzumanfred]

I confirm that it also worked on Tiguan 2011 5N0920882C cluster with sw version 0417.

Thank you very much Lidahus !