grantmethepower
Well-known member
Ok, I was able to get everything up and running and I went ahead and saved each module's AB and labeled each with todays date and identifier for which it was before changes.Just a second piece of advice. Please do allow yourself to get familiar with FORScan and configuration changes and using the dashboard any just poking around, checking DTC, etc. before doing "MFU (Module Firmware Update)" I think FORScan goes a little bit overboard on the warnings and liability BS, but it's understandable because some people would just jump right in and try wild things. If you're on this forum following good advice you're probably OK, but still it helps to be familiar with FORScan and start slow, it's not the most easy piece of software to understand.
I then did two small changes-I turned off the panic button on my key fob and the reverse brake detection thing off. Both seemed to work just fine. I get the hang of the way it works for those basic changes.
Where I'm at now though is to do the module update. From what I read it sounds like what you're saying is that the firmware needs to be updated to tell the truck that the physical hardware is there before I should make the changes to BCM numbers. Is that right? How do I do that exactly? I read the FORScan forum and its a lot of warnings but I dont see exactly how.
I saw this you posted but I dont see where these are exactly. None of the tutorials I could find talked about the MCU process. Sorry to bug you again. Hopefully this is it!
Sponsored