Sorry for the late reply!
Quote:
Originally Posted by Clavurion
Of course it would have been best to first check that ZCS on EWS and original cluster match so it's accurate. Though ZCS on EWS is likely as it should unless someone has deliberately changed it (or EWS, DME and keys are from another donor vehicle).
Verifying ZCS would mean checking every bit according to vehicle specs and additional equipment. There are some tools like Zeko to help in this if really needed.
|
Yes! I tried using Zeko, but the version I have does not run in Win10.
I'm trying Zeko version 4.2 and no compatibility settings I used works. But I did try Decode BMW v0.3 and was able to look at my SA options--and they seem reasonable. As for the PO, he said the original cluster was busted and he threw it out. So no luck there.
I'll try to do more digging and find a working version of Zeko.
Quote:
Originally Posted by Effduration
I use PA Soft, NCS, etc and understand ZCS, GM SA and how to program the KMBI.
But does the cluster show the accurate mileage of the original car or the donor car? Does it have a tamper dot? I always thought you needed to solder in a new chip or something to use a used cluster in a different cluster
|
Yes, the used cluster has the tamper dot. And with that I'm curious as to "actual" mileage. I'm not sure I ventured enough in INPA to look at what the EWS says the mileage is. This should be in the "IDENT" function of INPA, ya? I'll need to explore more.
To my understanding, the larger one should be displayed on the cluster and is "checked" every 60 miles or so. It would be great to re-write the vin on the cluster to get rid of the tamper dot as well as the trifecta. But I'm working on getting my ABS module rebuilt hopefully.