Lightning Software Updates using FDRS

[Mike G]

And yesterday FDRS 42.5.6 was released.

So no more spamming the 're-run network test' to see if new updates show up I guess.

Also since this is a major (41. to 42.) update remember to tick the box for 'remove user settings' during setup so you don't end up with weird results. They may have changed some of the layout internally.

Sponsored

 

[ChrisCon]

What he's experiencing is what happens if you've logged on to FDRS and you're actually still logged on and working when your daily login timeout expires.

Have you tried my method ? I think it's the same problem with two work arounds I've never tried your way . This happens to me daily and I never realized what the root cause was.

 

[Mike G]

Have you tried my method ? I think it's the same problem with two work arounds I've never tried your way . This happens to me daily and I never realized what the root cause was.

I log on something like 0530 most mornings. By roughly 1630 my cached credentials are timed out.

So if I happen to be actually out working on either the car or the truck when that happens...and I'm in the middle of doing some update...I will get the continual login screen repeats until I actually shut FDRS completely off and then start a new session after about a minute. Last time this happened I was in the middle of a module update and the software had loaded but it wouldn't do the configuration step because it wanted me to log in, over-and-over. So I exited FDRS and gave it 30 seconds. Logged back in, and specifically ran the config routine on the module I had been working on to finish up.

 

[ChrisCon]

I log on something like 0530 most mornings. By roughly 1630 my cached credentials are timed out.

So if I happen to be actually out working on either the car or the truck when that happens...and I'm in the middle of doing some update...I will get the continual login screen repeats until I actually shut FDRS completely off and then start a new session after about a minute. Last time this happened I was in the middle of a module update and the software had loaded but it wouldn't do the configuration step because it wanted me to log in, over-and-over. So I exited FDRS and gave it 30 seconds. Logged back in, and specifically ran the config routine on the module I had been working on to finish up.

I'm in the situation where I just never close FDRS after I use it, so each day I open up my laptop around 8:00am and when I'm ready to do the network scan, I get the login pop ups. I never thought to just close out the software since, I use that laptop for just FDRS . Seems silly to have to do that.. Either way, I click forgot password. Then Click the "return to previous page" hyperlink on the blank webpage that pops up after I click forgot password. Then the login credetials go away and I can use FDRS. I'm going to try your method tomorrow.

 

[starrtech2000]

What he's experiencing is what happens if you've logged on to FDRS and you're actually still logged on and working when your daily login timeout expires.

When this happens (at least with 41.5.6) you will have to completely close FDRS. Wait about 30 seconds and then reopen the program and log in again.

I've done this many times...and that login dialog page will just keep coming back up until you finally give up and close the program completely and start over.

A close out and restart of the computer did it...

 

[starrtech2000]

I've got the BCM update that requires the special lock smith login or whatever. It seems that there are two other updates that I keep running and completing but they won't actually leave the list, so I wonder if they are dependent on the BCM update...

Any workarounds for the login needed for the BCM update?

I'm trying to add the walk away lock feature and wondering if that's going to require the BCM update.

 

[PJnc284]

I'm trying to add the walk away lock feature and wondering if that's going to require the BCM update.

BCM will require a dealer trip. Had mine updated while in to have the battery sensor replacement. The ACM and RFA sticking around after updating is a known issue

 

[bmwhitetx]

Haven't seen this mentioned in a while but I know many of us were getting the SOBDM & SOBDMC DTC's after the PCM/SOBDMx modules were updated earlier this year (either by dealer or those of you rolling your own).

I checked my DTC's yesterday and I had none! The last time I checked on Aug 31, they were still there.

I had mobile service out in September but they just did IPMA and BCM. And I got the ECG-24.2.5.6.1 OTA on Sep 2nd. So not sure if one of these cleared them or if I got a silent update.

 

[Mike G]

Haven't seen this mentioned in a while but I know many of us were getting the SOBDM & SOBDMC DTC's after the PCM/SOBDMx modules were updated earlier this year (either by dealer or those of you rolling your own).

I checked my DTC's yesterday and I had none! The last time I checked on Aug 31, they were still there.

I had mobile service out in September but they just did IPMA and BCM. And I got the ECG-24.2.5.6.1 OTA on Sep 2nd. So not sure if one of these cleared them or if I got a silent update.

It was the ECG (GWM) update that fixed it.

 

[Mike G]

4 Nov, and there's an interesting blurb in the supplemental update (#1) for FSA 24B56 (the Front sensors/IPMA update).

Ford is recommending the use of a VCM 3 for this procedure because it apparently has the ability to handle large file sizes better than the VCM 2 (which is Mongoose comparable).

But the interesting thing I saw was a note that simply said:

"FDRS Update
FDRS software was updated on 10/07/2024 to reduce battery consumption."

So that's interesting, even if there isn't a more complete explanation of how that's being done.

 

[Gimme_my_MME]

4 Nov, and there's an interesting blurb in the supplemental update (#1) for FSA 24B56 (the Front sensors/IPMA update).

Ford is recommending the use of a VCM 3 for this procedure because it apparently has the ability to handle large file sizes better than the VCM 2 (which is Mongoose comparable).

But the interesting thing I saw was a note that simply said:

"FDRS Update
FDRS software was updated on 10/07/2024 to reduce battery consumption."

So that's interesting, even if there isn't a more complete explanation of how that's being done.

Yes, dealers should have more success now but still need to read directions and use a power supply

 

[shelnian]

Tonight while out and about I noticed that the Power-Up 6.8.0 update didn't complete. I updated all the modules, some several times, in early Oct and I now have the battery percent displayed. Not sure why this update is trying to be installed or why it couldn't complete. 1FTVW1EL6PWG51962

 

[Mike G]

Tonight while out and about I noticed that the Power-Up 6.8.0 update didn't complete. I updated all the modules, some several times, in early Oct and I now have the battery percent displayed. Not sure why this update is trying to be installed or why it couldn't complete. 1FTVW1EL6PWG51962

Weirdness with your truck. It's not pulling up any connected vehicle info at all. No OTA history. No VHA history.

Assuming you haven't turned off connected vehicle toggles in Sync:

I recommend you go out and disconnect the 12V battery for a couple of minutes and then reconnect to see if that clears things up a bit.

Also, you show a GVMS warning on your IPC. Not sure what that's about. So that's either on Ford's end or on your end. But the server thinks your asbuilt settings in the IPC aren't right for whatever reason. You can try running a "Config" on the IPC using FDRS to see if that will put the server saved settings back into your IPC and clear the warning.

 

[shelnian]

Weirdness with your truck. It's not pulling up any connected vehicle info at all. No OTA history. No VHA history.

Assuming you haven't turned off connected vehicle toggles in Sync:

I recommend you go out and disconnect the 12V battery for a couple of minutes and then reconnect to see if that clears things up a bit.

Also, you show a GVMS warning on your IPC. Not sure what that's about. So that's either on Ford's end or on your end. But the server thinks your asbuilt settings in the IPC aren't right for whatever reason. You can try running a "Config" on the IPC using FDRS to see if that will put the server saved settings back into your IPC and clear the warning.

I'll disconnect battery for a few and check connected settings. I did use Forscan to turn on glare free lights per the Forscan thread a few weeks ago. Would that cause some of this? I save the original settings so can reverse, if needed. The glare free does work.

 

[shelnian]

Weirdness with your truck. It's not pulling up any connected vehicle info at all. No OTA history. No VHA history.

Assuming you haven't turned off connected vehicle toggles in Sync:

I recommend you go out and disconnect the 12V battery for a couple of minutes and then reconnect to see if that clears things up a bit.

Also, you show a GVMS warning on your IPC. Not sure what that's about. So that's either on Ford's end or on your end. But the server thinks your asbuilt settings in the IPC aren't right for whatever reason. You can try running a "Config" on the IPC using FDRS to see if that will put the server saved settings back into your IPC and clear the warning.

Disconnected the battery for 20 to 30 minutes, checked and connected vehicle toggles are on. Took it for a drive before I disconnected battery. Do you see any changes?