In regards to new module parameterization/installing new/used modules. Is there a current a list of platform components that are known to have Component Protection() build in. I'm assuming all main modules would have that, i.e instrument cluster, can gateway, radio etc. However a list of 'Do have' and 'Don't have' modules would be nice!
Side question about component protection, is it possible to "revert" when component protection kicks in? For example, I install a new module and get error. Can I reinstall the original module to remove component protection? Or is the only option visit to a dealer? Thanks
OEMplusCC: If I can add a not inconsistent response to those that you have already received - the "constellation" (isn't that a wonderful descriptor?) which the official language describes as the modules that are captured by Component Protection is a bit like this:
Notice the position of J533 which in the diagram is labelled as the Data bus diagnostic interface, but which identifies as the
CAN Gateway (@ address hex19) - its the master which means that it's the module that oversees the entire interrogation/response process.
My understanding is that the hex19 module retains a list of the identities of all of the other modules in the constellation (including, I believe the car's VIN for the purpose of ). After ignition switch-on, the master interrogates each of the constellation modules for their identity - if the responses are not equivalent to the information contained in the master-list, a error is initiated both in the master and in the itinerant module.
So, in answer to your second question - as long as the original CAN Gateway is not changed, no error will occur if you re-install any of the original constellation modules because when the interrogation process re-occurs (post ignition switch-on) the identity of the replaced module(s) will once again align with the data in the master list. This assumes of course that you haven't had the master list data changed - as would happen if you removed the error through the official process.
The other question that you haven't asked is: is it possible avoid errors when swapping constellation modules? The answer is YES (well....... it's a type of YES in theory). I've not done this, but theoretically, if it's possible to hot-swap any of the constellation modules after a successful challenge/response process has been completed (i.e. post ignition switch-on) - it should be possible to avoid errors. Of course this would only apply for the current ignition cycle - once the ignition is switched-off and if the replaced module remains installed, a error will occur at the next ignition switch-on
Don