As best I know, the coding for a given car should not change when the correct replacement part is installed. If the coding is wrong, one would expect a 01042 - Control Module; Not Coded or something to that effect to be flagged. Thus, so far, so good.
I have to disagree...........some controllers will code incorrect attributes and not display a .
The fact remains that an incorrect module or correct module with incorrect settings for sizes of wheels/brakes can in fact be coded wrong for any of the cars in addition to other stupid options.
To know for sure is to verify it.......
To just base it on a prior aforementioned part # and old coding is not advised because the config could be different and that includes old scans.
What if someone tampered it?
I have been experimenting with them for a while and seeing what data it will allow for writes to an off road unit.
My goal is to write Off road VIN configs for upgraded brake sizes, and race controllers, matched to the systems which still need to see a specific chassis or data string from the VIN......... being intertwined with a checksum/byte swap etc...
So far if you know how to calculate the VIN and the option which is selectable as a table stored in the controller......... it seems to take it.
That doesn't mean it is correct!