skodapilot Forum

Hello, I have problems with using the latest version of the VDO Editor on a 1K8 speedometer. Reading out EPROM still works without any problems, but reloading EPROM doesn't work. Every time I write to the EPROM again, it blocks my access to the immobilizer. First I just wanted to change the start logo, then I wanted to change the scale, finally I just read EPROM and wrote it again unchanged. Same problem every time, immobilizer access blocked. What could be the reason? Part number is 1K8920885J, HW02, SW1104. Thanks for tips.

Utility bug: changes immo state value independently did you touch it or not before.
Will fix soon.

Tapatalk

Many thanks for answer .
Do you need information about what is changed by the program when writing to the EPROM ?
The program changes values by itself, even if I as the user don't change anything .

I know bit and offset.The reason is selecting of cluster type. Different types have different meaning of the same value.

Tapatalk

Hello, I'm writing this here because it's the same speedometer with the same part number, I hope that's ok.

I have the problem that I want to put the speedometer in an EOS. Unfortunately I cannot recode the K number. I would have to set 7 under byte 0 bit 0-3. But it is stuck at 1 and cannot be changed. Now my question is, can I adjust it somehow in the eeprom, or adjust it somewhere in the VDO editor so that I can get the 7 in there? Tire circumference and all the other settings also fit Eos as it is set up. It just shows a completely wrong speed compared to the GPS signal (18km/h difference from 100km/h). I would be very happy about a positive feedback.

Not possible on 11xx firmware

Is there perhaps the possibility of flashing to a higher level where you can then code it again? Or is it possible to specify this somehow in the eeprom? I think there must be a possibility. Because even for a scirocco, where the original is available, a k value of 7 should be set, as I said, it is stuck at 1.

Use values from original eos dump from following offsets: 0xAD and 0xB6

Tapatalk

I'll take a look at what's in the values right away. Can you tell me what these values do, or what exactly they adjust?

This pair defines k value. Full algorithm is unknown for me, but I am not agree with opinion that the second byte is just unlocking mask (just for sw10** and higher). Check real value via measuring channel. Possible values can be observed via research module

Tapatalk