ECU module programming guide using FDRS

[rugedraw]

I recently updated all the modules since 4.2.1 on my truck in FDRS following this very helpful guide. Thank you everyone.

I have been up since 6am and did about 20 updates. After the test drive and doing everything but BCM, I have a PCM and SCCM DCT. I have rerun and reset numerous times and also tried forscan.
Can anyone point me in the right direction please? The IPMA will be green most of the time like it is now.

All vehicle report some codes. If the truck is not having any issues, I would not stress it.

Sponsored

 

[ebsocalmtb]

I also want to thank those that put this guide together and have posted in this thread helping. I spent most of the day yesterday updating my 22' 402A that was stuck on 3.4.something and now I'm mostly caught up. Honestly the hardest part was getting the login going, the guide was flawless from there to the end that this whole process has been very easy.

A few questions/statements that I wouldn't mind input on:
1) I'm being prompted for an NTSA login when I try to update the BCM. I was able to update the BCM(C) whatever that is. Is this normal?
2) I am leery to do the DSP and ACM update as I do not have audio issues with my B/O unleashed. I have had a few of the fireworks/tommygun incidents, which obviously sucked, but I didn't want to borrow trouble with all of the sound quality issues people have been having. Is this rational and should I do it anyway?
3) I haven't gotten any prompts for the ipma update. This is one that despite the timesink... I really wanted to get done. Maybe that's related to #2? Any advice here?

 

[fordtruckman2003]

I also want to thank those that put this guide together and have posted in this thread helping. I spent most of the day yesterday updating my 22' 402A that was stuck on 3.4.something and now I'm mostly caught up. Honestly the hardest part was getting the login going, the guide was flawless from there to the end that this whole process has been very easy.

A few questions/statements that I wouldn't mind input on:
1) I'm being prompted for an NTSA login when I try to update the BCM. I was able to update the BCM(C) whatever that is. Is this normal?
2) I am leery to do the DSP and ACM update as I do not have audio issues with my B/O unleashed. I have had a few of the fireworks/tommygun incidents, which obviously sucked, but I didn't want to borrow trouble with all of the sound quality issues people have been having. Is this rational and should I do it anyway?
3) I haven't gotten any prompts for the ipma update. This is one that despite the timesink... I really wanted to get done. Maybe that's related to #2? Any advice here?

Unleashed, with the 18 speakers, and the DSP update released long time ago fixed my issues with static pops. It is only an issue for the 8 speaker system causing problems. That has since been corrected with another update. Some have reported weird issues with sync and audio after updates and reported that it went away after factory reset.

If your BCM is far behind on updates that might be holding you up on IPMA and others, but I'm not certain the relationship between those updates. I was under impression only the newest BCM was locked behind a login, but maybe it is all of them now. ?‍

 

[ebsocalmtb]

Unleashed, with the 18 speakers, and the DSP update released long time ago fixed my issues with static pops. It is only an issue for the 8 speaker system causing problems. That has since been corrected with another update. Some have reported weird issues with sync and audio after updates and reported that it went away after factory reset.

If your BCM is far behind on updates that might be holding you up on IPMA and others, but I'm not certain the relationship between those updates. I was under impression only the newest BCM was locked behind a login, but maybe it is all of them now. ?‍

thanks for the response. I did the DSP/ACM updates and everything is all good. All I have left in my list is the BCM. I did some of the self test stuff to check of there were DTCs with the ipma, there were a few showing but once i re-tested they were clear.

Maybe I'll try and talk the dealer into updating the bcm and then I'll see if I can get the ipma update going.

 

[Davidwnuc]

Im pretty certain the issue will be your cable. THe IPMA is on Can FD and the only modules that handle it well are the Ford VCM and Mongoose. Ive seen some other cables that are high end OEM styles do OK.. But its hit and miss.

Just wait for the mongoose. It is the best bet versus trying anymore. Not only does the other cables cause failures.. It garbles the data submissions. Causing updates to not release and bad data on Fords server.

Got the mongoose.
Im guessing it being Sunday evening is the reason I am having issues logging in to FDRS?

 

[Big Dog Daddy]

Got the mongoose.
Im guessing it being Sunday evening is the reason I am having issues logging in to FDRS?

You shouldn't have a problem right now, Sunday mornings are typically when login problems arise due to Ford updating there servers.

 

[Davidwnuc]

 

[Davidwnuc]

Im in now
Already can tell a difference between the other cable and the mongoose.

 

[Davidwnuc]

Got my IPMA issue fixed.
Mongoose was the answer. Lesson learned…dont assume just because the cable you have will update the PCM with a third parties software that it will work correctly FDRS.
Thank you everyone for the assistance.

 

[fordtruckman2003]

Got my IPMA issue fixed.
Mongoose was the answer. Lesson learned…dont assume just because the cable you have will update the PCM with a third parties software that it will work correctly FDRS.
Thank you everyone for the assistance.

#1 lesson in this thread is to only use Mongoose or legit Ford VCM and none of the cheaper options.

Glad you were able to get updates completed.

 

[Davidwnuc]

#1 lesson in this thread is to only use Mongoose or legit Ford VCM and none of the cheaper options.

Glad you were able to get updates completed.

agreed.
only reason i even had a different cable was to do a Roush tune update and i purchased the one they recommended for that purpose. Figured it was worth a shot updating stuff with it….until it wasn't. Lol

 

[fordtruckman2003]

agreed.
only reason i even had a different cable was to do a Roush tune update and i purchased the one they recommended for that purpose. Figured it was worth a shot updating stuff with it….until it wasn't. Lol

Tunes are complicated. Several people delay PCM updates until aftermarket tunes are updated to be compatible. I don't think it holds up other updates but not certain.

 

[drumminmandan]

Big thanks to those who came before me, and to those still here helping!

I had an early build ’21 with the stuck sync (version 4.0.20301) and the auto-updates were grayed out / could not be toggled on. Through FDRS I was able to update to Sync 4.0.23159 along with many module updates along the way.

The initial APIM update was a little stubborn, but I got it moving within a couple hours. I am not sure what worked, but here are some notes:

• Started with a high speed USB stick. No luck.
• Switched to an old low speed USB stick. No luck.
• Leaving the low speed USB stick in the truck, I went through 3 full shutdown cycles (1 cycle: Key on, engine running for about 5 minutes. Full power down for 30 minutes). On the 4th start, the truck screen said the USB update was going through.
• After this APIM update, I went back to using the high speed USB stick for all the remaining module updates with no issues.

Other than a couple hours trying to do the initial APIM update, everything went relatively smooth. The initial login to FDRS took a bit of patience. I am not sure what the deal was, but after a few installs of different versions, I was able to finally get version 40.4.8 to work.

Thanks again all!

 

[fordtruckman2003]

We have lucky people on forum this year recovering trucks on the bad software. Does that mean Ford fixed whatever the initial issues were with updating that version? ?

 

[Jesse-Infotainment]

We have lucky people on forum this year recovering trucks on the bad software. Does that mean Ford fixed whatever the initial issues were with updating that version? ?

NO.. ITs the same. Its always been a crap shoot. Some have the update kick off fast and some have to wait a month

No rhyme or reason.

Sponsored