FCA was forced by the EPA to offer a large incentive for us to get the AEM. I don't see any incentive being offered to get an AEM update, unless you're running the crappy original AEM.But if there ever is a AEM patch released and you take in your vehicle any fix, they will want to apply the patch and it will again over write your Hot Tune.
I was thinking about a recall(EGR) or you wanting to take advantage of the extended warrantee on a failed emissions part and they see you don't have the latest AEM update, they will make their case that you need to have that done while in the shop for repairs. If you never go back to the dealership you are correct and will be just fine. I just can't trust the emissions junk to last or not be recalled in the future.FCA was forced by the EPA to offer a large incentive for us to get the AEM. I don't see any incentive being offered to get an AEM update, unless you're running the crappy original AEM.
setup new ecm today and the new ecm shows original vin and also the new vin.Hey guys – I been following this thread, and ones like it on other forums, and really looked forward to using AlphaOBD to write a new VIN and injector codes to a second ECU. I picked up a used ECU out of a 2015 Overland from a salvage yard that I figured would work fine in my 2014 Summit. Unlike some of the other people here, I am having a heck of a time getting the “new” used ECU to clear all its problems. I followed the detailed procedure on the ramforum using AlphaOBD to connect to the new ECU, write all 6 injector codes and the new VIN. Exited out of AlphaOBD, turned the vehicle off for 5 minutes, turned it back to run and here’s what I get; the dash flashes “Service Air Suspension System” and “Cruise/FCW unavailable Service Required”. I’ve cleared all the fault codes using AlphaOBD, put it back to sleep, and still no change. Same errors. The Jeep does startup and runs but I didn’t try to take it out with the existing errors on this “new” ECU. I uploaded copies of my working ECU config and the “new” ECU config to my google drive (EDC17_CHRYSLER_Info.log) and did a “stare and compare”.
The first thing that jumped out to me between the two configs are the VIN numbers. On the working ECU both the VIN – Current and the VIN – Original are identical (my VIN number). On the “new” ECU, the VIN – Current is the VIN I entered using AlphOBD (my VIN) and the VIN – Original is the one that came from the 2015 Overland. I thought they should both be the same after the AlphaOBD update, just like the working one. The procedure I was following from the ramforum showed they should be but I can’t get them to ever be the same. When using AlphaOBD to write my VIN number into the “new” ECU I always get a “procedure complete” message after hitting the start button, so it appears that it’s accepting the new VIN. All the problems clear and the Jeep runs just fine when I put my original ECU back in.
Can someone who’s done this before remember if the “new” ECU they programmed with AlphaOBD showed the same VIN numbers or different ones on the AlphaOBD status page? Thanks in advance for any help, advice or questions. I’m pulling out what’s left of my hair trying to make this work.