- Joined
- Jan 8, 2015
- Posts
- 10,030
- Reaction score
- 5,930
- Location
- St. Louis
- Ram Year
- 2014
- Engine
- 3.6 Pentastar
Got it, I think I'm going to have to get a new Occupancy Restraint Module that accepts the new DS value being changed to DS - Ram 1500 as a proper BCM value to clear the error. I am going to contact Alexi with AlfaOBD though to see if it is an option he can add to the Android Version for selection OR if the Windows version can connect as a different BCM (similar to connecting as Pacifica to set the 12" screen settings you early adopters did) and set the value to DS...Nope 18 .
On a positive note, I've seen it repeated hear many times that folks couldn't get the used BCM to accept a new VIN using the VIN Write feature in AlfaOBD. You can get the BCM to write the VIN for the installed vehicle for both Original VIN and Current VIN by performing the following steps:
1. Connect to the BCM
2. Select the "Engineering Reconfiguration Reset"
3. Select "Reset ECU"
This will write the Current VIN the BCM is installed in and leave the Original VIN blank (with a bunch of question marks for the value like this ?????????????). Performing the above 3 steps again will write the value for both fields bumping the Current VIN Value to Original VIN and then re-writing the current VIN with the currently installed VIN (I know @Jimmy07 has said this doesn't matter for operation of the vehicle, but my OCD couldn't let it slide).