When Tamper condition occurs after changing LCM (expected behaviour), this can be cleared by coding correct VIN and resetting mileage to zeroĨ. Any previous faults/coding options are inherited from the donor LCMħ. If LCM is changed and not re-coded, Tamper condition is set, but vehicle is fully operableĦ. (When changing LCMs, coding correct VIN and setting mileage to zero will prevent/correct this)ĥ. If VIN matches but mileage doesn't then Tamper is activated If VIN doesn't match then Tamper is activatedĤ. If VIN matches, mileage updates every 100kmģ. Just to make sure I understand 100%, can I ask a few more questions, hopefully you can give me a one word answer!Ģ. A forum member who lives not far from me has offered to helpĬlavurion, you are a superstar! Thanks for explaining that. So the associated question is, what is the "tolerance" on mileage across the various modules in a vehicle before the "tamper" is triggered?ītw, I won't be doing he re-coding myself. Or does it trigger the tamper anyway but reset it once the correct mileage has been set?Īs a side issue, when I was experimenting with PA I noticed that the mileage is recorded in about 4 or 5 modules - what I did spot was that they weren't all absolutely matching, there was maybe a variance of about 15 units (reported back as kilometres in PA, is this normal?) I get the replacement, plug it in, then what? At what point does "the system" decide that the LCM's mileage setting is wrong, and trigger the "tamper" warning? I'm a bit intrigued as to the sequence of events to recode this. Having had guidance from the gurus (Clavurion, Know-Dice, V8Warrior etc - thanks guys!), I know that the LCM will need recoding, I think mainly for mileage setting, otherwise I will get a "tamper" warning (sorry,forgotten the proper name for it). So I have my eye on a replacement LCM III B "mit man LWR", should hopefully get it early next week.
0 kommentar(er)
