ECU module programming guide using FDRS

[Ebrou]

That is something different. During an active update, the truck behaves electrically differently. It’s really not telling you anything to monitor that stuff. What @dougbillings was talking about is what he was seeing during the shutdown period after the USB update had completed and before the truck was restarted.

Got it. Thank you for pointing that out.

Sponsored

 

[FordConvert]

Yeah unfortunately that one seems to kick off when it feels like it. Some have suggested a long drive. Some disconnect the battery charge it for a while it is disconnected and then reconnect and had that work.. iceman drove for a few days and it kicked in.. so yeah just leave it in

I haven’t tried this but maybe giving the APIM a direct nudge might help. Leave the flash drive in, log into FDRS and run a self-test. Might wake it up and cause it to recognize the flash drive.

I’ll try that. Would it be a bad idea to update other modules while waiting for the APIM USB?

 

[JEB]

I’ll try that. Would it be a bad idea to update other modules while waiting for the APIM USB?

I can’t say for sure. But take a look through the other options. My practice is that if there’s a GWM update, I usually apply that first before proceeding to other modules. One thing you might try is to update everything else you can and then try the APIM again at the end from scratch with a fresh download on a clean drive. It doesn’t sound like it‘s doing anything right now except sitting there waiting to kick off.

 

[JasonATL]

I’m fully updated and have Blue Cruise! Huge thanks to all of those helping in this thread. The last gateway and APIM installed from USB super fast. Was expecting a long wait but each was done in probably less than 20 Mins. I didn’t have any other updates available so not sure if that made a difference or not.

 

[Fordphanatic]

I’m fully updated and have Blue Cruise! Huge thanks to all of those helping in this thread. The last gateway and APIM installed from USB super fast. Was expecting a long wait but each was done in probably less than 20 Mins. I didn’t have any other updates available so not sure if that made a difference or not.

Another FDRS success story with the help of a lot of awesome f150gen14.com members! Congrats enjoy your new features. We have all been waiting long enough

 

[jordandev]

Ok so with a 302A, 8 inch cluster, with 360 cams, no BC

I'm at 21281 revision 244 and not seeing anymore updates.

I only have an ACM "update" showing that seems to be for adding a woofer (it asks if adding one) that just fails:

Not sure if it's normal to be stuck here at 244 now or not. But no cams at speed or on the side yet so hopefully not as those were what I was hoping to get ?‍

 

[nicholsbradley]

Anybody tried disabling the double honk with BC updates installed? I don’t want to mess all my work and tons of help from others in this forum.

 

[MikeYQM]

Anybody tried disabling the double honk with BC updates installed? I don’t want to mess all my work and tons of help from others in this forum.

I had it prior, never removed it. Works fine. All my ForScan changes work fine. I had to renter a few after update.

 

[JEB]

Anybody tried disabling the double honk with BC updates installed? I don’t want to mess all my work and tons of help from others in this forum.

I don’t have BC, but I received all the same updates with the exception of the driver spy cam. I had no problems with a disabled double honk. That FORScan change is to the BCM. That module was not updated in the last round so it shouldn’t create any conflicts.

 

[Fordphanatic]

I have BC and it works great. The only forscan changes that I made before the BC update was double honk disable, and Bambi mode. I left all my changes before applying updates with FDRS and I don't have any issues.

 

[Bob_Mac]

The only issues that some have had including myself was with FORScan changes to the APIM, IPC & IPMA. That's not to say everyone will have issues but any mods done on those modules should be reverted to avoid any configuration mismatches and/or update failures.

 

[Jesse-Infotainment]

Ok so with a 302A, 8 inch cluster, with 360 cams, no BC

I'm at 21281 revision 244 and not seeing anymore updates.

I only have an ACM "update" showing that seems to be for adding a woofer (it asks if adding one) that just fails:

Not sure if it's normal to be stuck here at 244 now or not. But no cams at speed or on the side yet so hopefully not as those were what I was hoping to get ?‍

I am thinking you guys have a similar issue to the 12” cluster guys a file mismatch in the cluster update prevents the updates

 

[Ajzride]

After my experience and reading here about others, I agree the IPC updates are problematic, and it's on Ford's end and not ours. Some people with complex Forscan changes have had no issues with the IPC, while some with no Forscan changes get their IPC hung. I think it's a problem child for Ford right now.

 

[Ebrou]

I am thinking you guys have a similar issue to the 12” cluster guys a file mismatch in the cluster update prevents the updates

@Jesse-Infotainment, Is there a way to reinitiate the IPC update? My whole update was over CAN, never an option for USB during the install. It took about 6.5 hrs as most here have been saying to complete. I do not recall any DTC's after update.

 

[Ebrou]

After my experience and reading here about others, I agree the IPC updates are problematic, and it's on Ford's end and not ours. Some people with complex Forscan changes have had no issues with the IPC, while some with no Forscan changes get their IPC hung. I think it's a problem child for Ford right now.

I can agree with that... I have not made any FORSCAN changes at all. The last OTA I received was 2.3.0 OTA, then I believe it was a GWM update. Not that long after the GWM OTA that I completed the IPC update.

Sponsored