Look in flash for the CPU

these counters nobody reads processors because they are not needed for anything

what difference in behaving?

Would you share?



What do you mean by that?

By the way I guess (based on your nickname) that you are from Poland and so do I. If I am right, we can talk a little on Facebook

Anyway, I tried everything, without luck .

I did as follows.
1) took eeprom with desired k-value and speedo scale.
2) loaded it into dash. Of course it caused def.
3) recoded it in VCDS. Def is gone but so is my custom k-value
4) read this recoded eeprom from dash
5) compared it with version that causes def error
6) copied all cells that were different - from "recoded, no error, overwritten undesired k-value" to my "def error, custom desired k-value" eeprom (6 different bytes total). I have only left my desired k-value, everything else is the same as in "no error recoded" eeprom.

I was hoping, that if I copy all these different values, I would copy also checksum and other stuff that is under control test, and I would bypass def error. But no luck.

My observation is that recoding changed not only k-value back to factory. It changed 6 other bytes, but no idea of their functions. These are:
Address: value from def eeprom -> value from "after recoding with no def" eeprom
0x5C: 5EC0 -> C89D
0x14A: 0000 -> 0002
0x190: 0324 -> 030C
0x192: 0D98 -> 1056 (this is k-value, that was returned form my desired 3480 to factory 4182)
0x4BE: 0000 -> 0032
(note that it is 6 bytes difference, despite 5 addresses. First address has both bytes different)

Seems like two options:
1) this dash just won't accept k-value other than factory. And def is not related to checksums, but to the k-value only
2) it is still necessary to recalculate checksum and have it corrected already when writing eeprom. It could be possible, that for example, after reseting ECU (and it is necessary to reset ECU in order to new eeprom work so I can't pass this step) the dash calculates again checksum in order to validate it with this one that is currently in eeprom (but without correcting it). And I don't have this correct checksum present in any time in my custom eeprom with desired k-value (more probable scenario)

Any other ideas? Maybe other fix for def, without recoding necessity?

Its not posible to turn off ESP via button.... I have A6 C5 cluster in Audi TT 8N which is same as S3 8L. The difference is that TT/S3 have ATE ESP unit but A6 C6 have Bosch ESP unit. There is probably some different behavior between them and software in instrument cluster is probably cooperating with ESP unit. I can't figure out where to change that behavior.

Did you try to use a s3 8l dump?

4b0920933N is also a crypted cluster so... write a s3 dump that is also from a crypto cluster. Maybe there will be def but you will test if the esp behaviour changes.  At any time you can go back to your dump without any problem.

As long you write a dump from a crypto cluster you are safe , if you write a dump from a non- crypto cluster its worse but also it can be repaired.
 
Its easy to know if its a non- crypto cluster - the middle part of dump is ful of FFFFFF.... In crypto there is some data.