ECU module programming guide using FDRS

[Shoebox72069]

My truck has been on almost all morning (3 hours). Took it for another drive. Turned off Wifi as TJSparky mentioned, no change so far (not that I expected it that fast I guess).

My USB stick is very warm to the touch so you would think it is working perhaps but the read/write light isn't lit up though.

Sponsored

 

[iceman77]

Hi SpeedRacer… yes I left the USB stick in and turned off WiFi completely (that connects to house) within Sync. About 24 hours later I noticed the auto updates and schedule updates allowed me to change the settings. After that the very old version of sync was listed in the About Sync area. (It was all blank for the longest time)

After seeing all that I pulled the USB stick, started up the truck, then re-inserted the stick… about 3-5 minutes later. BAM! The USB install notice popped up!

This is very critical to get this update done! I have talked about this earlier here. What happened, you managed to get your APIM out of the stuck update mode, and that's when it will take your USB drive! Well done!

Apparently, there is no straight forward way to accomplish this, for some, disconnecting wifi works, for others hard reseting APIM/GWM up to a point of abuse.

 

[Shoebox72069]

This is very critical to get this update done! I have talked about this earlier here. What happened, you managed to get your APIM out of the stuck update mode, and that's when it will take your USB drive! Well done!

Apparently, there is no straight forward way to accomplish this, for some, disconnecting wifi works, for others hard resetting APIM/GWM up to a point of abuse.

It really seems like it needs the abuse based on all of the feedback here. Outside of the soft reset via the Power + Seek Key and or resetting it in FDRS... If I didn't have PB I would disconnect the battery for half a day. That seems like that is literally the other other option outside of praying at that point.

Is there a way in FDRS to reset the GWY? I hadn't looked but was wondering if that's another dependency that needs to be considered? Clearly the soft reset or even the reset in FRDS doesn't appear to be enough at times.

 

[Snakebitten]

The unknown variables are frustrating, but at least one by one they are being revealed and documented here.

Obviously there are multiple states/conditions of various settings that must be met to remove the unseen obstacles. I'm glad each time a new item makes the list.

Example.... Wifi settings. Go figure.
Example.... OTA Update schedule in Sync.

I bet there's still more and we collectively just need to stumble across them?

My truck never delayed for more than a few seconds recognizing a USB update was inserted. Yet my obstacle was on the other end of the update procedure and I couldn't get out of the "restart to complete update" loop. Only to discover (finally) that I needed to shut the truck down and remove the USB stick in order to complete the task.

Anyways, great thread and getting better every time someone's tenacity pays off!

 

[iceman77]

You can reset various modules (including GWM) via FORScan. You can find this functionality under the Wrench button in FORScan

I would really focus getting APIM back on track (update buttons enabled with Sync version visible) prior inserting the USB flash drive. How to get there, is the challenge you need to tackle.

As you can see, we all tried different approach and it is quite possible that none of our suggestions made any impact. It is quite possible that there is a timer running inside APIM that keeps this vicous circle of installing (yet failed) 1.7.1 OTA on and on. But there seems to be a short window when this loop is not active. That’s when your update buttons are active and sync version visible. And that’s when you have to attempt the USB update.

I’m just really speculating here, as noone really knows what is going on inside APIM/GWM

 

[speedracercjr]

I’m just really speculating here, as noone really knows what is going on inside APIM/GWM

Including Ford as well....

 

[Jesse-Infotainment]

You’d think it would go smooth. Jesse said he’s getting a serial number error. I read somewhere online that they were plug and play. But guess not. Extremely pist!

The serial number error happens Of you try to update an apim without doing the PMI first. Fdrs will only allow updates to modules it has record of. The PMI process not only replaces the serial that is stored it updates as well

 

[Ruffiano99]

Whats the PMI? Im planning on attempting this all over the weekend. Trying to get my steps in order.

 

[JEB]

Whats the PMI? Im planning on attempting this all over the weekend. Trying to get my steps in order.

Programmable Module Installation. It’s an FDRS procedure the tech is supposed to perform when replacing a malfunctioning module with a new one. It takes the as-built configuration from the server and writes it onto a new module. You shouldn’t need to use it if your existing modules are functioning and you are only using FDRS to update the software. It could be handy however if something goes wrong during an update.

 

[Shoebox72069]

On a NON APIM note...

What other modules are safe to update? My understanding reading that thread is that all the other modules that FRDS indicates a software update for are "safe". APIM, TCU, GWY, all require a USB, or some times do?

Maybe we should start a list?

I'm only sitting here wondering about this since I'm waiting on my APIM to figure itself out but have pile of other modules to update. Can those generally be safely updated, independently of everything else, even with APIM issues?

I'd ideally like to get some value before my FRDS license expires. I knew I should have spung for a month!

 

[speedracercjr]

On a NON APIM note...

What other modules are safe to update? My understanding reading that thread is that all the other modules that FRDS indicates a software update for are "safe". APIM, TCU, GWY, all require a USB, or some times do?

Maybe we should start a list?

I'm only sitting here wondering about this since I'm waiting on my APIM to figure itself out but have pile of other modules to update. Can those generally be safely updated, independently of everything else, even with APIM issues?

I'd ideally like to get some value before my FRDS license expires. I knew I should have spung for a month!

You can update everything that is available. I don't remember which module it was for me, but one of them stuck in the list to be updated even though it already was. Just make sure you have a battery charger for the longer updates, especially the IPMA as that takes ~3 hours.

 

[Snakebitten]

I had 14 updates available when I first logged in to FDRS. I didn't really consider what order to go in except I wanted to do the Gateway Module first. However, it wasn't listed as one being available.
So knowing the APIM/TCU was the one that both took the longest and most likely to be a challenge, I did the other dozen updates first.

Note: After I accomplished the APIM/TCU update, a rescan resulted in the Gateway update being available. Go figure.

 

[Snakebitten]

You can update everything that is available. I don't remember which module it was for me, but one of them stuck in the list to be updated even though it already was. Just make sure you have a battery charger for the longer updates, especially the IPMA as that takes ~3 hours.

For me it was the GSM and ABS updates that would successfully update but not be removed from the list. I did them both multiple times.

 

[Shoebox72069]

You can update everything that is available. I don't remember which module it was for me, but one of them stuck in the list to be updated even though it already was. Just make sure you have a battery charger for the longer updates, especially the IPMA as that takes ~3 hours.

I think I'll avoid the IPMA one for the time being. Can it be done with the truck started, or Igntion only? I found my battery tender didn't seem to work too well with the PB, when I had the ignition on it still wanted to shut the truck down after about an hour even though FRDS said voltage was OK.

 

[Shoebox72069]

So I updated a pile of modules, all pretty easy to do.

DSP = Couple minuets
SCCM = Couple minutes
GSM = Couple minutes
ABS = Couple Minutes

Updated BECM also required to update ABS, SOBD and PCM. However the BECM updated fails out of the gate due to "procedure Unsuccessful - GetVehicleNodeInfo Unknown Error". The ABS, PCM and SOBD finish happily however.

Running a scan still shows updates for ABS, GSM, BECM and APIM.

I know folks have said ABS and GSM won't seem to go away.

I DID see a GWY module update pop up. By the time I could copy off the APIM updates and go back to it... it went away. I also saw a tail gate module also... go away.

Not sure what to make of it but I guess if I see the gateway module pop back up I need to go after that one.

I wish the updates it would display is consistent. All the modules were green and responding positively too.

Sponsored