ECU module programming guide using FDRS

[mdomicolo]

I was using FDRS 41.5.2 today and it worked well. Make sure you use the non-dealer/independent option while logging in.

thank you, I finally got it to work. I’m currently like 1hr 45mins into the APIM update, ??

Update: the APIM update took about 3hrs to completely install, but I have the side view mirror cams working with blinkers now so I suppose it was all worth it! Just make sure you leave yourself lots of time to do the update!

Thanks everyone ??

Sponsored

 

[rugedraw]

Just wanted to say a sincere thanks to the folks here, especially @rugedraw for helping me on my update journey. My stuck APIM went from 20301 -> 21146 -> 22087 -> 22293 -> 23159 -> 23167 -> 23291. Based on the TCU update after the last APIM update, I reckon my truck is sitting at 6.4.0, which is pretty good for a Job 1 XLT. I'll leave the rest of it to the OTA gods.

It's nice to finally have a fully functional truck! Also noticed that for the 1st time ever, all my modules on FDRS were green.

You're not on 6.4.0 any more; you're up to date. You won't get the other OTA's now since you did all the updates with FDRS, so don't expect any OTA's any time soon.

 

[GMPowerboost]

Hey all, I am working this weekend to fully upgrade mine and take care of some tsb with the transmission shift solenoid (2021 F150 PB, 2x4, April of 2021 mfg date (I think job 1) 502a lariat).. I did a shotgun approach and updated everything last night. I went on a 50 mile drive earlier today just to relearn the transmission as when I first finished it would not go into electric mode at all.

Last night I updated the ACM - Audio Front Control Module (Software update G2426299-2.0) atleast 12+ time yesterday, and another 3 or 4 times today.. yet the module still appears under the SW updates each time.. Also a BCM update that wants a safety organization log in..

So my question to more advanced users, is hitting update and running through the endless cycles of the ACM actually doing anything? or is it some glitch in my FDRS? sometimes it will say update failed and other say update successfully.. And Q2 is if my "shotgun" approach of hit update all would of updated that solenoid that I mainly bought this to do? Any / All help is appreciated. My apologies if this was all already covered somewhere else in the 893 pages on this forum

 

[Kanuck]

Hey all, I am working this weekend to fully upgrade mine and take care of some tsb with the transmission shift solenoid (2021 F150 PB, 2x4, April of 2021 mfg date (I think job 1) 502a lariat).. I did a shotgun approach and updated everything last night. I went on a 50 mile drive earlier today just to relearn the transmission as when I first finished it would not go into electric mode at all.

Last night I updated the ACM - Audio Front Control Module (Software update G2426299-2.0) atleast 12+ time yesterday, and another 3 or 4 times today.. yet the module still appears under the SW updates each time.. Also a BCM update that wants a safety organization log in..

So my question to more advanced users, is hitting update and running through the endless cycles of the ACM actually doing anything? or is it some glitch in my FDRS? sometimes it will say update failed and other say update successfully.. And Q2 is if my "shotgun" approach of hit update all would of updated that solenoid that I mainly bought this to do? Any / All help is appreciated. My apologies if this was all already covered somewhere else in the 893 pages on this forum

ACM showing after an update in FDRS is a known thing. It is a FORD problem...just ignore it. Do it once and your done. If, at a later date, you are updating your truck in FDRS, you can run it again, just in case it is a new update.

 

[Igetit]

I found the Big Heavy's YouTube channel before this forum and the only thing I missed was not connecting the black side of my charger to the terminal. Using FDRS and the Mongoose cable I was able to get quite a few updates completed except of course the APIM one. Has anyone else encountered this error condition - it pulls down the new code, writes it to the USB, the truck reads the USB successfully and writes the update, then fails on the verification step because the part numbers (software versions) don't match. Not sure how to move forward from here.

<edit> thought I should add that (being an IT guy), I disconnected from FDRS, deleted the files from the USB drive, reconnected and rescanned current state, then let download the updates again, just to make sure it was pulling the correct version for my VIN. Verified the filename matches the truck's VIN, got the same result.

 

[rugedraw]

I found the Big Heavy's YouTube channel before this forum and the only thing I missed was not connecting the black side of my charger to the terminal. Using FDRS and the Mongoose cable I was able to get quite a few updates completed except of course the APIM one. Has anyone else encountered this error condition - it pulls down the new code, writes it to the USB, the truck reads the USB successfully and writes the update, then fails on the verification step because the part numbers (software versions) don't match. Not sure how to move forward from here.

<edit> thought I should add that (being an IT guy), I disconnected from FDRS, deleted the files from the USB drive, reconnected and rescanned current state, then let download the updates again, just to make sure it was pulling the correct version for my VIN. Verified the filename matches the truck's VIN, got the same result.

Disconnecting from FDRS may not do the trick. I would try restarting the laptop completely.

 

[Igetit]

Disconnecting from FDRS may not do the trick. I would try restarting the laptop completely.

Did I mention that I work in IT?
I rebooted in between FDRS sessions. As software applications go, it's fairly garbage. Plus writing embedded software to ECUs via CAN bus protocol is prone to stuff lingering in cache, unless you allow extra time for all the electrons to disperse. And who has time for that?

 

[rugedraw]

Did I mention that I work in IT?
I rebooted in between FDRS sessions. As software applications go, it's fairly garbage. Plus writing embedded software to ECUs via CAN bus protocol is prone to stuff lingering in cache, unless you allow extra time for all the electrons to disperse. And who has time for that?

lol noted and I agree that FDRS while user-friendly for a novice, is not great. With that said, you would not be the first or last to have issues with the a USB update that has had to push it through via CAN. Tell it to me and many others that have had to push an IPC update via CAN that took 6 hours because it would not take via USB. Based on what you're telling me, I would recommend trying the CAN way as tedious as it may seem.

As far as lingering data goes, just allow 5-10 seconds to pass between the time you cycle the ignition on/off and you click "ok" in FDRS to let it know the ignition is on/off. Also, remember to go into the settings and turn off the 30 minute idle timer to make sure it doesn't shut down mid-update. I have never had to CAN a TCU update an I am not sure if the touchscreen stays on during the update process or not, but jic, turn that off.

 

[Igetit]

turn off the 30 minute idle timer to make sure it doesn't shut down mid-update

I think that timer only applies to the internal combustion engine (ICE), which wouldn't be running while doing software updates anyway. That's why I bought a 20-amp battery charger. The idle timer is to prevent you from running out of gas if you are hammering the ProPower bank so hard that you forget what day it is. Right?

 

[rugedraw]

I think that timer only applies to the internal combustion engine (ICE), which wouldn't be running while doing software updates anyway. That's why I bought a 20-amp battery charger. The idle timer is to prevent you from running out of gas if you are hammering the ProPower bank so hard that you forget what day it is. Right?

The 30 minute timer applies to being in accessory mode, too. I bricked my CMR and the CMR of a Mach E by forgetting to shut that off. It won't happen to me a third time. lol

 

[Igetit]

That's good to know. Hasn't been a problem so far.

So does anyone at Ford actually support FDRS beyond what is on the - FordServiceInfo.Com website, cause that's all just documentation. Based on what I've read, most dealers know less than the collective wisdom of this group.

I haven't had time to read all 894 pages of this thread but this is a little more than frustrating.

 

[rugedraw]

That's good to know. Hasn't been a problem so far.

So does anyone at Ford actually support FDRS beyond what is on the - FordServiceInfo.Com website, cause that's all just documentation. Based on what I've read, most dealers know less than the collective wisdom of this group.

I haven't had time to read all 894 pages of this thread but this is a little more than frustrating.

Most updates take way less than a half hour. CMR and the IPMA/PSCM combo will take 45 minutes and 2.5-3 hours respectively. However, if you are doing an update via CAN, it will take longer than 30 minutes for sure. Better safe than having to write the update via CAN again to recover a bricked module.

Yes, there is FDRS support, but not in real time. You can message support, but by the time they get back to you, you'll probably need another license.

 

[Igetit]

I always backup my asbuilt data when using FDRS

How is that done? It might lower the pucker factor on my attempt to update a 21 PB APIM that's stuck. USB updates crash because FDRS says they're not the right version. I'm getting frustrated and looking for a bigger hammer.

 

[SilverPigeon]

How is that done? It might lower the pucker factor on my attempt to update a 21 PB APIM that's stuck. USB updates crash because FDRS says they're not the right version. I'm getting frustrated and looking for a bigger hammer.

You use FORScan to make the backup. In Module Configuration (the "chip" icon) select APIM as-built. When it loads, select "Save all" At the bottom.

 

[jcaspar]

I just updated my APIM and got the configuration failure. DO I need to return my APIM to as-built with FORScan to get it to configure correctly? I did it via the canbus, did not see another option.
Thanks

You use FORScan to make the backup. In Module Configuration (the "chip" icon) select APIM as-built. When it loads, select "Save all" At the bottom.

Sponsored