tonesto7
Well-known member
Yep. I thought I screwed the whole truck up.Luckily I do have the backup, I’ll restore it.
Did you have the weird blinking lights?
Sponsored
Yep. I thought I screwed the whole truck up.Luckily I do have the backup, I’ll restore it.
Did you have the weird blinking lights?
Well shit that makes me feel better now!Yep. I thought I screwed the whole truck up.
Hope your feeling better. I’ve been there 3 times and I’ve been vaccinated.NOTICE: I have updated the guide to reflect the changes to the preferred VCI device being the Mongoose-Plus as well as well as posted warning not to perform Network Scan if you decide to stick with the VCX Nano device
I apologize for the delay, I have promised to update the guide a week ago, but after 2 years of avoiding the COVID plague, this time it got me and hit me pretty hard
Apologize? You’re doing uncompensated work while suffering from a killer (literally) virus. That’s silly.NOTICE: I have updated the guide to reflect the changes to the preferred VCI device being the Mongoose-Plus as well as well as posted warning not to perform Network Scan if you decide to stick with the VCX Nano device
I apologize for the delay, I have promised to update the guide a week ago, but after 2 years of avoiding the COVID plague, this time it got me and hit me pretty hard
Just a follow up for future readers, if you get the weird disco lights after a BCM update restoring your as-built as @tonesto7 suggested fixed it for me. Thanks!!Do you have a backup of the module from FORScan?
you can restore that to the module and your tpms should restore its config.
this happened to me
You can order directly from the manufacturer here.Can someone tell me the difference between the VCX nano linked by the OP and this one? The one linked is sold out but this one appears to be the same? I don’t know.
VXDIAG VCX Nano Compatible for Ford/Mazda 2 in 1 Diagnostic Tool with IDS Programming Tool https://www.amazon.com/dp/B07YD6ZXT...t_i_XS7RSJT648F1RKETNPDH?_encoding=UTF8&psc=1
@speedracercjr , the asbuilt you restored, is it the asbuilt prior to you performing the module software upgrade? I download from motorcraft website my asbuilt before and after to compare the changes that were done with updated module software. Isn't restoring to the prior asbuilt defeating the purpose of the software update, or am I misunderstanding this process?Just a follow up for future readers, if you get the weird disco lights after a BCM update restoring your as-built as @tonesto7 suggested fixed it for me. Thanks!!
No, not if used properly. Make sure you run the first three diagnostics under the Support tab of the J2534 Toolbox. This is important. The Mongoose must be plugged into the truck with the ignition on, engine off when running the diagnostics. If all checks out, you can then immediately proceed to FDRS.Got the mongoose pro in. Just double checking here that running network scan will not corrupt like it does with the nano?
I'm actually adding these steps now to the doc that'll be ready soon...No, not if used properly. Make sure you run the first three diagnostics under the Support tab of the J2534 Toolbox. This is important. The Mongoose must be plugged into the truck with the ignition on, engine off when running the diagnostics. If all checks out, you can then immediately proceed to FDRS.
Think of it this way: The software is essentially firmware—the basic programming of the module. The as-built data are the variable configurations/settings applied to that module so that it operates properly with your specific truck. If you look in other parts of FDRS, you will see a tool called “[module] configuration” which is what FDRS calls the as-built data loader. You can change the settings/configuration without overwriting the firmware.@speedracercjr , the asbuilt you restored, is it the asbuilt prior to you performing the module software upgrade? I download from motorcraft website my asbuilt before and after to compare the changes that were done with updated module software. Isn't restoring to the prior asbuilt defeating the purpose of the software update, or am I misunderstanding this process?
Thanks @JEB for the reply, after I updated my IPC, I did not run the configuration tool, should I have or only if I have enco7ntered issues after the update? I have not noticed any problems and it has been about 2 weeks since I updated it via the CANBUS. Thanks again!Think of it this way: The software is essentially firmware—the basic programming of the module. The as-built data are the variable configurations/settings applied to that module so that it operates properly with your specific truck. If you look in other parts of FDRS, you will see a tool called “[module] configuration” which is what FDRS calls the as-built data loader.