ECU module programming guide using FDRS

[Dlh]

Did you go to the control panel of your computer to uninstall any previous versions of FDRS? The procedure didn't work for me at first when I only put the installed version into the recycling box. I had to physically uninstall through the control panel. Once I did and reinstalled it works now every time I login. I'm not the most computer savvy so I had to do some research to figure out how to wipe the corrupted versions first. Hope this helps

Yes, I did the same thing. Even tried using ver37.4.7 as someone else recommended using a previous version. Uninstalled 38, and followed the steps listed above. No dice....I'm beginning to wonder if my computer has enough processing power. 1.8ghz, 16gb ram running Windows 10.
Thanks for the suggestions though, it is appreciated as I'm going to keep trying!

Sponsored

 

[Thekameleon]

Yes, I did the same thing. Even tried using ver37.4.7 as someone else recommended using a previous version. Uninstalled 38, and followed the steps listed above. No dice....I'm beginning to wonder if my computer has enough processing power. 1.8ghz, 16gb ram running Windows 10.
Thanks for the suggestions though, it is appreciated as I'm going to keep trying!

It appears that FDRS is using some new Single Sign On authentication method. I haven't run into this problem, so I can't reproduce and test what I'm going to suggest. However, I have seen simular issues with other services and SSO.

One thing I don't know is if FDRS attempts to use your computer's default browser when authenticating. If it is, you default browser may be different than MS Edge. Edge is based on the Google Chromium source code.

So for your default browser, I would clear your cookie cache. You may want to clear it for all your browsers. Then try repeating the steps above in this post. You may want to try logging into Chrome as it suggests for MSEdge as well.

 

[fordtruckman2003]

All I know is I was using Ford single login process for FDRS last summer, well before these updates came along. I use same login across everything Ford including FDRS. I didn't intend that, but forgot which email I had for my Ford account, so they were linked back in May/June. I haven't needed to use FDRS again since the recent IPC update worked without forcing it. Hopefully it does work same as it was if I need it again.

 

[JasonATL]

If you had been using a user ID to login instead of email address try the email address now. I had that issue previously. Once I signed in to the browser with email and then used the same email in FDRS it all worked.

 

[Dlh]

It appears that FDRS is using some new Single Sign On authentication method. I haven't run into this problem, so I can't reproduce and test what I'm going to suggest. However, I have seen simular issues with other services and SSO.

One thing I don't know is if FDRS attempts to use your computer's default browser when authenticating. If it is, you default browser may be different than MS Edge. Edge is based on the Google Chromium source code.

So for your default browser, I would clear your cookie cache. You may want to clear it for all your browsers. Then try repeating the steps above in this post. You may want to try logging into Chrome as it suggests for MSEdge as well.

Turns out, my laptop had insufficient processing power (1.7ghz which is lower than what FDRS recommends) Upgraded the laptop and I’m in business! This thread has been beyond helpful in tackling these updates on my job1 2021. Appreciate everyone who contributes here!

 

[Fordphanatic]

Anyone ever come across this message in FDRS while looking up vehicle history

 

[Fordphanatic]

No one?

 

[nitrobass24]

Theres known to be weirdness with version 38 & Windows 11.
Perhaps try 37.4.7...seems to be the most stable version as of late.

 

[Snakebitten]

I thought I'd license up for FDRS so that I could check on the calibration routine for the rear CCD height sensors for another forum member.
It's been awhile since I scanned the truck, but after recently receiving 6.8.0 OTA, I naively thought I'd NOT have much if anything in the FDRS queue.

How did this happen?
Ford has been BUSY
Certainly busier than I was aware.
Nothing in the list can be stale.

By the way, I had to upgrade from my trusty older version of FDRS to get logged in successfully.
So for me 38.5.7 is working fine in Windows 11 Pro on a Surface Laptop 5

 

[nitrobass24]

No gateway or APIM update? You must be pretty up to date unless they just havent hit yet because of another dependency. Be prepared the CMR/IPMA/PSCM are chained and take a long long time

 

[Snakebitten]

@nitrobass24

I'm just about done. Down to the IPMA of that grouping.

Yea, I don't normally let GWM, APIM, TCU, or especially PCM/ABS sit.

I wasn't expecting the PCM update. Don't know how I missed that news.
Or maybe it was mentioned and I just have a case of oldtimers.

 

[Cnixon]

This isn't really the correct thread but someone here may know, I sent my PCM out to HP tuners to be unlocked for OBD2 flashing capabilities, it mentions that factory tools will not be able to calibrate but all other functions are not effected, will that stop whatever OTA updates that are pushed? I assume the FDRS updates will be killed for the PCM as it is the OEM method

 

[nitrobass24]

That’s an interesting question. I don’t really know what the unlocking process entails but I’m still getting sent updates despite running a tune.

what are you planning on doing with it once you get it back?

 

[Cnixon]

That’s an interesting question. I don’t really know what the unlocking process entails but I’m still getting sent updates despite running a tune.

what are you planning on doing with it once you get it back?

Just an OZ Omega tune for now, I've run out of all of my extended warranties so I figure it's free game, it'll likely have a Whipple before the year ends based on my previous habits ?

 

[Braeden]

Anyone ever come across this message in FDRS while looking up vehicle history

Yeah I have gotten that. I did not find a way around it.

Sponsored