ECU module programming guide using FDRS

[betathalguy]

Hey everyone, I spent the past 5 hours updating modules. I updated the APIM module early like the instructions stated with all of the engine start stops and USB transfers, etc. The trouble is that now the APIM update is showing up again and has "run" outlined in green. I went through it again and there were no usb instructions and then it went into a tcu update with no usb instructions and everything finished rather quickly. I cannot get the APIM software update to quit showing up. Im also still at update 2.1.1. Is there a way to re-do the APIM update? Maybe I did something wrong or something got corrupted, I don't know. Here is a screenshot below.There was also never a higher version of software available on the updates higher than the one that I have.

I noticed that there are a lot of new things on my screen though. For example, I am now able to schedule updates on multiple days whereas I was not able to before. My siriusxm screen also now has a different format. Additionally, I have front camera views when Im parking.

Should I try to delete and re-install the APIM update? If so how do I go about re-doing it. Its not working in the pic below anymore, it just keeps me in a constant loop of relaunching the update without the USB stick. Ive done it like six times. Any help is appreciated.

Sponsored

 

[Shyrax]

The IPMA took FOREVER... about 3 hours. Even though the truck was on the power supply, the voltage dropped from 12.1 to 11.2 during the upgrade. Then to 10.9 when everything turned back on after the update. Might not have had a good enough connection to the battery. The 3 updates involved with the IPMA all finished and showed no errors. The IPMA update is still in the list though. It is green and says I can Run it. Will try again tomorrow.

 

[Shyrax]

Just realized I forgot to hit Start on the charger so Power Supply mode never started.
I’m an idiot…
?‍

 

[alexthelion2539]

I just want to say thank you for all the great information on this thread. I ended up reading every page while waiting for my mongoose to arrive.

I have a huge lesson learned that I would like to share as I have not found the solution, nor my exact indications for this anywhere on the internet. If you get the USB error 0 after it says system updating (not upon immediately inserting the USB drive) then the software downloaded from Ford via FDRS got corrupted somehow.

I spent two days troubleshooting this. 7 different drives. Charging the battery overnight. Reverting all forscan changes on all modules even if they weren’t related to the module of concern. Performing TSB procedure. Buying a new battery. Using a different computer.

I checked functionality after each change to initial conditions of the truck in order to narrow down the culprit in the event I got the update to complete successfully. What ended up working is deleting FDRS completely in order to remove all downloaded files, that way when I restarted the APIM update, I got fresh files from Ford instead of just flashing by all the files already loaded in the cache of FDRS.

I hope this helps others that may experience this issue.

 

[ENG430]

I just want to say thank you for all the great information on this thread. I ended up reading every page while waiting for my mongoose to arrive.

I have a huge lesson learned that I would like to share as I have not found the solution, nor my exact indications for this anywhere on the internet. If you get the USB error 0 after it says system updating (not upon immediately inserting the USB drive) then the software downloaded from Ford via FDRS got corrupted somehow.

I spent two days troubleshooting this. 7 different drives. Charging the battery overnight. Reverting all forscan changes on all modules even if they weren’t related to the module of concern. Performing TSB procedure. Buying a new battery. Using a different computer.

I checked functionality after each change to initial conditions of the truck in order to narrow down the culprit in the event I got the update to complete successfully. What ended up working is deleting FDRS completely in order to remove all downloaded files, that way when I restarted the APIM update, I got fresh files from Ford instead of just flashing by all the files already loaded in the cache of FDRS.

I hope this helps others that may experience this issue.

Thanks for your effort to solve USB error 0 issue.
But you said that you used a different computer and did not solve that. My question is does the second computer had FDRS installed earlier or did you install a fresh version of FDRS in the second computer when it failed?

Thanks in advance

 

[alexthelion2539]

That is an excellent point. Now that I think about it, when I used the second computer I don’t think I reformatted the drive, so it just checked software part numbers.

 

[betathalguy]

The IPMA took FOREVER... about 3 hours. Even though the truck was on the power supply, the voltage dropped from 12.1 to 11.2 during the upgrade. Then to 10.9 when everything turned back on after the update. Might not have had a good enough connection to the battery. The 3 updates involved with the IPMA all finished and showed no errors. The IPMA update is still in the list though. It is green and says I can Run it. Will try again tomorrow.

mine is doing the same thing with the APIM module. My voltage was a little over 12, but my battery charge was only 50%. I deleted FDRS and user information. Will reinstall tonight with a clean USB and new FDRS installation and completely full charge. Set the charger on before I left for work this morning.

 

[Braxx]

I know the newer Mongoose Plus adapter is working and recommend but has anyone used the original Ford Mongoose adapter? A neighbor asked if I had a correct adapter and could do the updates for him. I have 2 of the original first gen Mongoose adapters.

 

[Shyrax]

Reran the IPMA making sure the battery charger was actually turned on this time. Finished in just a minute or two. Ran all the other updates. After rerunning the network scan, the IPMA is orange in the list. Ran self test on it and got the message below. Any ideas?

 

[JEB]

I just want to say thank you for all the great information on this thread. I ended up reading every page while waiting for my mongoose to arrive.

I have a huge lesson learned that I would like to share as I have not found the solution, nor my exact indications for this anywhere on the internet. If you get the USB error 0 after it says system updating (not upon immediately inserting the USB drive) then the software downloaded from Ford via FDRS got corrupted somehow.

I spent two days troubleshooting this. 7 different drives. Charging the battery overnight. Reverting all forscan changes on all modules even if they weren’t related to the module of concern. Performing TSB procedure. Buying a new battery. Using a different computer.

I checked functionality after each change to initial conditions of the truck in order to narrow down the culprit in the event I got the update to complete successfully. What ended up working is deleting FDRS completely in order to remove all downloaded files, that way when I restarted the APIM update, I got fresh files from Ford instead of just flashing by all the files already loaded in the cache of FDRS.

I hope this helps others that may experience this issue.

This is a really interesting solution to the USB Error 0 problem. Well done. But I was wondering if something a little less extreme might also work. Have you tried deleting just the downloaded software files directly and redownloading instead of deleting the entire program? The downloaded files can be found at c:/ProgramData/Ford Motor Company/FDRS/fdrs/data/vehicle_software

 

[JEB]

Reran the IPMA making sure the battery charger was actually turned on this time. Finished in just a minute or two. Ran all the other updates. After rerunning the network scan, the IPMA is orange in the list. Ran self test on it and got the message below. Any ideas?

Click on “View CMDTCs” on the home page after the network scan. Then “clear and retest.” See if that clears it for you. This error might also clear by just driving it around for awhile.

 

[Shyrax]

Click on “View CMDTCs” on the home page after the network scan. Then “clear and retest.” See if that clears it for you. This error might also clear by just driving it around for awhile.

Seems to have cleared itself. Thanks

 

[betathalguy]

So I have updated all of the modules and APIM again. I also got a message in the FOrdpass app that says my Bluecruise is active. However, I am going back and forth between the APIM updates and the Gateway updates. Im on about the third round of this and lots of downloads to the USB drive. Is this normal to have to keep updating the the APIM then the Gateway over and over?

BTW, my Prologix charger completely died. It won’t turn on or light up at all. I had it charging while I was at work and then put it on PS while restarting the updates. I had to get my neighbors car charger, he was a lifesaver!

 

[Burner]

I'm working on the APIM updates now after months of the dealer not being able to. I'm using the pro-logix charger on power supply mode and it keeps clicking on and off about once every 2 seconds. My voltage is also dropping why fdrs downloads the files. Anyone have any experience with this? I'm down to 11.9v according to fdrs

 

[betathalguy]

Connect the black clips to the bolt in front of the truck that connects the ground wire from the black terminal.

Sponsored