Originally Posted by
G_Force
There appears to be ambiguity and confusion over the use of the Vehicle Writer methodology to disable SKIM with the "SKIM Disable for retrofit". If this feature was added in by the HPTuners development staff for the purpose of disabling SKIM, then why do we even need to mess with the other Security parameters? Secondly, did the new 3.0 Editor fix something in the "SKIM Disable for retrofit" function that didn't quite do all that was intended in the 2.25 Beta, or is it doing the exact same thing, because this function definitely did not work for me before.
Are we supposed to coordinate anything we do in Security and/or during the Vehicle Write procedure with "unchecking" the SES Enable of DTC U0168 in Engine Diagnostics, which is for "Lost Communications with Vehicle Security Control Module?"
Finally, I have read on this forum and others that changing the VIN of the PCM to match the Vehicle VIN will enable SKIM to function properly and allow the engine to start and run. However, this Editor has no provisions to allow changing the Dodge VIN at all. I have changed the VIN numerous times in GM ECMs/PCMs as necessary to get replacement controllers to match the vehicle identity, but why is this feature not included for working on the Dodge PCMs? Why should I go through somebody else to accomplish this, dealing with time delays, shipping and the overall extra costs involved?? I should be able to do this in the HPTuners Editor.
What is the proper methodology for disabling SKIM using the current 3.0 Editor?
Thanks for providing some clarity to this muddy subject!