Quote:
Originally Posted by IK6SPEED
Quote:
Originally Posted by Poochie
Quote:
Originally Posted by IK6SPEED
Quote:
Originally Posted by Poochie
Quote:
Originally Posted by IK6SPEED
Quote:
Originally Posted by Poochie
Quote:
Originally Posted by IK6SPEED
Quote:
Originally Posted by Poochie
He already claims the EEPROM is cleared.
I feel like it might just be a programming error in syncing official vin and mileage to the new cluster, hence the tamper dot.
What do you suggest?
|
If it was done correctly, he would not have issue. |
If he has Esys, I guess Steve from CMB can recode it remotely with the Team Viewer.
Like I said, I'm at a loss here.. |
*sigh*
For second time in 24 hours, eSys cannot virginize Kombi.
Quote:
Originally Posted by M135imike
Quote:
Originally Posted by IK6SPEED
Quote:
Originally Posted by Poochie
Quote:
Originally Posted by M135imike
Quote:
Originally Posted by Poochie
Quote:
Originally Posted by M135imike
Quote:
Originally Posted by Poochie
Quote:
Originally Posted by M135imike
Quote:
Originally Posted by Poochie
|
Yep, know it's a tamper dot, the mileage was set to 0 and cluster also eeprom virgin'd is there more things to do? Obviously it's been coded and flashed too |
Hmm.. It sounds like you covered your bases, that should of taken care of the tamper dot.
I guess use something like ISTA to seek out any possible errors codes than can point you in the right direction and then possible reprogram the cluster to see if it then erases. |
Have also done that, had no errors in the kombi other than the sos call |
That's so weird and confusing; clearing the EEPROM and programming the cluster should of sync the mileage with the three other computers, that stores redundancy data, thus, erasing the dot.
I'm sorry, I'm at a loss. I guess it might be time to get professional help on this issue.
Good luck. |
Any recommendations on who to chat with ? |
I heard good things about these guys below, PM them and describe your issue. They code remotely.
steve@codemybimmer
https://www.codemybimmer.ca/contact/?v=7516fd43adaa |
Kombi cannot be virginized remotely or with ISTA (or eSys). |
It's been sent away to be virgin'd, and I've received it back, seems like the job hasn't been done correctly. |
Obviously it wasn't done correctly, as previously stated. |
*sigh*
Can you not read, I told you already the cluster's memory was reset, as he stated that in the post above that. Esys is suggested for the coding the vin and mileage.
If you're not going to contribute anything useful to the topic but unnecessary sarcasm, please just get lost! |
Once again, you are absolutely wrong. And proven so for about the 10th time in the last 10 months.
If you cannot post correct info, for God's sake, quit posting. |
*sigh* God, you're just that dingleberry that's just so hard to shake off.. 
Thanks for derailing the thread with your typical nonsense. |
Except OP admitted I was correct and thus you were wrong again. |
*sigh*
You're like an infant, what you want, a cookie?