ECU module programming guide using FDRS

[Paul Neubauer]

Just think of it as sweating off a few pounds. I updated for about an hour on Friday afternoon in TX. Garage door open, truck parked about half way in, windows down, doors closed. Slight breeze, but plenty of sweat.

Edit - I updated 13 modules in about 45 minutes for those looking at timing and how long to alot for updates. This was on a Lightning, but most of the SW is the same. PCM, ABS, SOBDMC, BECM, DCDC, GFM2, SOBDM, SOBDMB, ACM, TRM, RFA, DSM, HVAC

I'm curious if mine has any updates available. It's been sitting at the dealership for a couple months now but I think they updated the BCM and did a PMI on the HCM. It's been a while since I had it and updated anything before that.

Sponsored

 

[GDN]

I'm curious if mine has any updates available. It's been sitting at the dealership for a couple months now but I think they updated the BCM and did a PMI on the HCM. It's been a while since I had it and updated anything before that.

I'd check for you but my 2 day license expired this morning. You likely have a good hand full for sure. I'm not sure there was anything earth shattering from these. I already had the BCM, IPMA and other modules that brought me BC 1.4 and WAL (Lightning).

 

[Lead Foot PowerBoost]

I have also had to put a fan in the truck blowing on the laptop to prevent it from shutting itself down due to overheating now that it is summer.

My garage was 95 the entire time I was updating. Had 2 fans pointing at the power supply and put my laptop in a big cooler to cool it down between updates. It was getting very hot to the touch at times.

 

[digitaltrucker]

Am I correct in assuming that when you do this manually, that you are connecting via your laptops internet connection to Ford? If so, then it behooves you to connect via a hard wire network connection and not wireless for a faster up and down speed?

 

[Big Dog Daddy]

Am I correct in assuming that when you do this manually, that you are connecting via your laptops internet connection to Ford? If so, then it behooves you to connect via a hard wire network connection and not wireless for a faster up and down speed?

That is correct. I wired ethernet connection would be the most stable and fastest way to connect.

 

[Gord0]

That is correct. I wired ethernet connection would be the most stable and fastest way to connect.

Except for the fact that Ford servers seem to only allow download speeds that equate to about 3g cellular...

 

[m_bt54]

You are limited by the speeds on the server side(and everything inbetween). It most likely will make no difference unless you have poor WiFi connection where your vehicle it

 

[GDN]

As others have noted, your home Wifi speeds far exceed what your bandwidth is that you've got coming in from the ISP. Wired might be a tad more reliable, but in today's world with retries, etc Wifi should pose no real problems, as long as you have a decent signal.

 

[Snakebitten]

I can't count how many updates I performed with FDRS while sitting in the vehicle using my smartphone as a Hotspot.

 

[Gord0]

I can't count how many updates I performed with FDRS while sitting in the vehicle using my smartphone as a Hotspot.

My phone is usually around 2-3x what my home wifi is. The problem is "usually".

 

[digitaltrucker]

My wired connection speeds are 949 down and up. My wireless is about 450/350.

 

[Snakebitten]

Ford is about 3/1 ??

 

[HammaMan]

Ford is about 3/1 ??

Yeah, the update downloads are pretty bad. I've seen them rip a couple of times but it's rare. Most sites throttle. I had 5Gb symmetrical but it'd rarely if ever top out. Dropped to 700Mb and the only time I notice a difference is a speed test. Still doing about 5TB a month though.

 

[bassaway]

Not sure where you are in this right now, so I’m going to start from scratch.

The first post was created approximately three years ago and a lot has changed since then. That post cannot be edited because the user who created it no longer participates on the forum. So, we, and you, are stuck with it, warts and all. One of those warts is that the “non-dealer motorcraft” user type in FDRS no longer exists. It has been replaced by “independent operator/non-dealer” and it is the only user type that will work for non-Ford employees. Don’t attempt to use any other user type. It won’t work.

The site where you bought the FDRS license is maintained by a Ford subsidiary called Helm. It uses a different set of credentials than any other Ford-affiliated site. Create one set of credentials for that site (username and password) and use those credentials ONLY for buying your license.

Ford.com, motorcraftservice.com and FDRS all use the same credentials and they are NOT the same as the credentials used to purchase your license. To make sure your credentials are properly synced, log into Ford.com first. Email and password. You want to make sure these creds work properly because these are also the credentials you’ll ordinarily use for FordPass.

Once you’ve verified that your creds work properly on Ford.com, go to motorcraftservice.com and log in there with the same credentials you used for Ford.com and FordPass. If those credentials do not work, then create a new motorcraftservice.com account using those same credentials. Then log in and accept a couple of EULAs. You’ll also be asked to identify what kind of user you are. I used DIYer.

Once you’ve confirmed that your creds work on motorcraftservice.com and you’ve accepted the EULAs, then try to log into FDRS as “independent operator/non-dealer” using the same credentials you used for Ford.com and motorcraftservice.com. If it doesn’t work immediately, wait for an hour and try again. But DO NOT keep creating new credentials. It will only make things worse.

See if that works.

Hey All - Unfortunately, I am experiencing the same issues User Lead Foot recently experienced with logging into FDRS. I have successfully logged into Ford.com and motorcraftservice.com using the same credentials, waited overnight after getting the error last night, and tried again this AM with the same result. Running with FDRS 44.4.7 logging in as "Independent Operator/Non-Dealer".

My first login attempt this AM brought me to the Ford.com login screen where I entered by correct credentials and moments later received the following error: "Error: Page not found. The requested URL was not found on this server."

Now when I hit "log in" on FDRS, I am immediately taken to the "Page not found" error screen and completely bypasses the Ford.com login screen.

2-day license is valid. All FDRS network diagnostics passes. Reinstalled FDRS. I even ran a Windows 11 update which was due. At a loss here folks! Any help would be greatly appreciated!

 

[bassaway]

Hey All - Unfortunately, I am experiencing the same issues User Lead Foot recently experienced with logging into FDRS. I have successfully logged into Ford.com and motorcraftservice.com using the same credentials, waited overnight after getting the error last night, and tried again this AM with the same result. Running with FDRS 44.4.7 logging in as "Independent Operator/Non-Dealer".

My first login attempt this AM brought me to the Ford.com login screen where I entered by correct credentials and moments later received the following error: "Error: Page not found. The requested URL was not found on this server."

Now when I hit "log in" on FDRS, I am immediately taken to the "Page not found" error screen and completely bypasses the Ford.com login screen.

2-day license is valid. All FDRS network diagnostics passes. Reinstalled FDRS. I even ran a Windows 11 update which was due. At a loss here folks! Any help would be greatly appreciated!

Update - The bypassing of the Ford.com login screen was because I had another window open with the Error screen from a previous login attempt. After closing all Error screens, I am back to being directed to the Ford.com login screen, but login attempts continue to result in the "Page not found" error screen.

Also just deleted browsing history, cookies, cache, etc from all internet browsers. Same result.

HELP! ?

Sponsored