ECU module programming guide using FDRS

[JEB]

Frustration level is rising, and license time is ticking by while not being able to actually use the software license I purchased...not really happy with Ford right now.

More things I've been trying:
Started completely over on a totally different computer, using a totally different internet connection (mobile hotspot this time). Still used the same log in, and successfully transferred the same FDRS license to the new computer.
Same result - "cannot reach the FDRS servers". Network tests are now consistently "pass" (had some fails earlier) but not able to log in. FDRS WILL take me to the Dealer website to attempt login that way, but will not do it with non-dealer selection.

If you’re running Windows 11, try a much older version of FDRS—37.X.X. @nitrobass24 ’s database goes back that far.

Sponsored

 

[nitrobass24]

@jgrant I have found 37.4.7 to be the most stable on W11 for me. I don’t even bother upgrading anymore.
https://github.com/nitrobass24/FDRS-Archive?tab=readme-ov-file#version-3747

 

[jgrant]

@jgrant I have found 37.4.7 to be the most stable on W11 for me. I don’t even bother upgrading anymore.
https://github.com/nitrobass24/FDRS-Archive?tab=readme-ov-file#version-3747

Just tried 37.4.7 - no change.
Should I need IDS installed? Or anything else?

 

[Big Dog Daddy]

Did you install ford's vcm software. I use a mongoose, but somehow after installing the vcm software it all worked.

 

[jgrant]

Did you install ford's vcm software. I use a mongoose, but somehow after installing the vcm software it all worked.

Are you talking about the VCI software package? I had it installed before but I've sinced uninstalled it as I try to get this to work. I'm going to re-install and see if it makes any difference.

 

[Big Dog Daddy]

Are you talking about the VCI software package? I had it installed before but I've sinced uninstalled it as I try to get this to work. I'm going to re-install and see if it makes any difference.

Yes

 

[Micho523]

OK, everybody, I'm getting the dreaded "cannot reach FDRS servers" message when trying to login to FDRS. Any help is greatly appreciated. Here's what I've done so far:
1. Installed FDRS 39.6.8 (latest release, 18 March)
2. Selected "Independente Operator/Non-Dealer" and "USA".
3. Hit Log In and get the message.
4. Tried un-installing and re-installing 4 times. Tried installing "VCI" software because it was complaining about it.
5. Tried creating a new Motorcraft account and being logged in while running FDRS.
Is anyone else having issues today?

Literally just used it without issue

 

[jgrant]

Literally just used it without issue

Problem is probably something on my end, then. Thanks for the data. Still trying to figure it out...

 

[Gord0]

Since I won't have time this weekend to tackle my list of updates on my new to me truck I figured I'd at least do a little prep. Grabbed my asbuilt from Ford, then plugged into forscan for the first time to download my asbuilts there. I was somewhat shocked I only had 1 dtc. ?

It'll be nice to clear this list, then figure out why I get no cam in motion even though I'm on Sync23159 rev915. Yes, only 1 cam. Surprisingly this Lariat wasn't optioned with 360... Yet.

 

[JEB]

Problem is probably something on my end, then. Thanks for the data. Still trying to figure it out...

There are two “non-dealer” login choices—Non-Dealer ETIS and Independent Operator/Non-Dealer. Make sure you are using Independent Operator/Non-Dealer.

 

[jgrant]

There are two “non-dealer” login choices—Non-Dealer ETIS and Independent Operator/Non-Dealer. Make sure you are using Independent Operator/Non-Dealer.

Thank you for double checking that, but yes that's the one I'm picking.
I did some sleuthing and I'm pretty sure that the Ford login server is using some outdated security certificates, some of which expired a few years ago. This is possibly the reason why there is so much varied success with using FDRS. Different systems will deal with the outdated certificates in different ways. This also could explain why some wierd combinations of having the website open and logged in in the background will actually make a difference (sometimes). The login servers for their Dealer options and ETIS are both using different, and correct, security certificates, so they are probably working much more consistently for people.
I'm just an amateur at this stuff, so I don't really know for sure, but if anyone out there is super smart on how TLS certificate chains work, maybe you can figure out a workaround.

 

[jgrant]

I've successfully wasted my entire day on trying to make this work, with no luck. If any more newbies come along and can make FDRS work for them, please let me know. Looks like a total bust for me.

 

[Mwathey515]

I've successfully wasted my entire day on trying to make this work, with no luck. If any more newbies come along and can make FDRS work for them, please let me know. Looks like a total bust for me.

All I remember from January was I couldn't find it in my "downloads" folder but did find it in my network downloads, used my Ford Pass info & it worked for me....that was a couple months ago though.....I wish I had a better answer....I have windows 10 pro & FDRS version 38.5.7

 

[Jesse-Infotainment]

I've successfully wasted my entire day on trying to make this work, with no luck. If any more newbies come along and can make FDRS work for them, please let me know. Looks like a total bust for me.

Does the login screen show for you?

 

[jgrant]

This is as far as I get. All day - Version 37, 38, 39, all the same.

Sponsored