Lightning Software Updates using FDRS

[jlcreasy]

I've newly jumped into the FDRS pond.... Has anyone had issues with FDRS bringing up the Ford Login screen using the Independant Operator/Non-Dealer option? It works on my Win11 desktop but not on my Win11 laptop (freshly loaded OS). When I click login on FDRS I get a dialog box saying Cannot reach FDRS servers....

I just loaded a 38. version and the login worked. Not sure what happens when I upgrade....

Sponsored

 

[jlcreasy]

I just loaded a 38. version and the login worked. Not sure what happens when I upgrade....

Crazy path... Once I had FDRS version 38 working, I updated to the latest FDRS and it worked. Then I updated to Win11 and everything still worked. Go figure... Now to figure out what is safe to update on the truck.... Any guidance would be greatly appreciated.

 

[TaxmanHog]

Any guidance would be greatly appreciated.

https://www.f150lightningforum.com/...software-updates-using-fdrs.11029/post-388871

 

[rugedraw]

Crazy path... Once I had FDRS version 38 working, I updated to the latest FDRS and it worked. Then I updated to Win11 and everything still worked. Go figure... Now to figure out what is safe to update on the truck.... Any guidance would be greatly appreciated.

Start with GWM, APIM, TCU and IPC in that order as they appear. Doing one of these will cause another one of these to pop up.

CMR will take about an hour. The IPMA will take 3 hours and it is tied to the PSCM, so don't start either one of those late at night unless you plan on staying up late.

 

[jlcreasy]

Start with GWM, APIM, TCU and IPC in that order as they appear. Doing one of these will cause another one of these to pop up.

CMR will take about an hour. The IPMA will take 3 hours and it is tied to the PSCM, so don't start either one of those late at night unless you plan on staying up late.

Thanks so much!!

 

[16cards]

When attempting a BCM update this evening, FDRS prompts to to authenticate using a NASTF account. Is this new?

 

[jlcreasy]

When attempting a BCM update this evening, FDRS prompts to to authenticate using a NASTF account. Is this new?

I hit the same issue last week. I created an NASTF account but it didn’t work. I was told it is a Ford issue. All updates except BCM worked fine.

 

[16cards]

I hit the same issue last week. I created an NASTF account but it didn’t work. I was told it is a Ford issue. All updates except BCM worked fine.

Same. Created an account. Can log in to NASTF. But credentials don’t work in FDRS.

So how are others here updating BCM. There appear to be quite recent reports of successful updating it?

 

[rugedraw]

Same. Created an account. Can log in to NASTF. But credentials don’t work in FDRS.

So how are others here updating BCM. There appear to be quite recent reports of successful updating it?

It is an issue on Ford's side. It should not be asking for those credentials unless you are trying to program keys. Until they fix it, there isn't anything you can do. There's a member that was going to install an older version of FDRS yesterday to see if you can circumnavigate the problem that way, but I can't remember who it was; I think it was someone in the Mach E forum.

 

[16cards]

It is an issue on Ford's side. It should not be asking for those credentials unless you are trying to program keys. Until they fix it, there isn't anything you can do. There's a member that was going to install an older version of FDRS yesterday to see if you can circumnavigate the problem that way, but I can't remember who it was; I think it was someone in the Mach E forum.

Last night I downgraded from the current 40.x to 38.x and still am prompted for NASTF credentials when attempting the BCM update.

 

[rugedraw]

Last night I downgraded from the current 40.x to 38.x and still am prompted for NASTF credentials when attempting the BCM update.

In that case, the problem is on the server side and not the FDRS version. Nothing to do but wait for Ford to fix it. I am sure they are aware of the issue at this point.

 

[16cards]

In that case, the problem is on the server side and not the FDRS version. Nothing to do but wait for Ford to fix it. I am sure they are aware of the issue at this point.

I found the following announcement in the NASTF forum itself which appears to describe the issue of FDRS failing to accept NASTF credentials. As rugedraw stated, given that those lurking here are just owners and not vehicle security professionals... nothing to do but wait for Ford to fix it.

 

[BSull]

It is an issue on Ford's side. It should not be asking for those credentials unless you are trying to program keys. Until they fix it, there isn't anything you can do. There's a member that was going to install an older version of FDRS yesterday to see if you can circumnavigate the problem that way, but I can't remember who it was; I think it was someone in the Mach E forum.

It was me, but I see that someone tried that and it didn't work, so I'll not bother. Waiting for Ford to fix an issue. What a concept

 

[jlcreasy]

In that case, the problem is on the server side and not the FDRS version. Nothing to do but wait for Ford to fix it. I am sure they are aware of the issue at this point.

If there is anyone in the SW Florida area that is able to update the BCM and willing to assist me getting mine downloaded, let me know.

 

[rugedraw]

If there is anyone in the SW Florida area that is able to update the BCM and willing to assist me getting mine downloaded, let me know.

I'm in Miami. We can try; maybe the dealer login I have to FDRS will allow me to do it without the password issue that is currently in FDRS. I have not tried any BCM updates since the issue popped up, but we can try if you want.

Sponsored