[redog4dy]

Hello guys, need some assi5тдnce, i have one cluster that was virginised by someone else and every contact on jumps +5 km. 
i ordered a new 160d0 eeprom at 7 Eur, backup old eeprom with problems write into the new memory, coded to the car. 
Everything is perfect except the tamper dot i have near kms. 
How to fїж it ? 
i have vvdi prog, r270, cg pro 9s12. 
i understood that i need to copy ID from old to new one, but if backup is written to the new memory, id should be copied also? 

Thanks,

[painsage]

Hello, use vvdi prog to read old eeprom ID, write in your new VVDI 160d0 chip using the same tool, red dot should go away.

[redog4dy]

Where do I have in vvdi prog to read id?
Didn't see anything. Thanks

[andriusx]

Where do I have in vvdi prog to read id?
Didn't see anything. Thanks

You have to go to Special function and select the chip there you will have option to read id

[redog4dy]

Where do I have in vvdi prog to read id?
Didn't see anything. Thanks

You have to go to Special function and select the chip there you will have option to read id

thanks mate, found it under in special function, will try today to read longid and see if it will work to write into new memory. 

Regards,

[al70]

you'll need a vvdi chip

[redog4dy]

it seems like longid is readable, i manage to write to blank chip.
vvdi chip is 35128? or which one? i had 160d0, memory/long id is written now, i will try tonight/these days to write new memory on cluster and see if manage to get rid of tamper dot.

Regards,

[HU_man]

use R270 clear short vin on 70 & 80 line and long vin on 590 5A0 line and VO coding 2 times, red dot will be gone

[redog4dy]

i will try to buy one vvdi eeprom, yesterday with other memory i have, seems after writing long id/memory, its broken, again in ignition/off jumps + 5 km every time.

Thanks a lot.