ECU module programming guide using FDRS

[JEB]

Mines still looking to install 2.1.0 even though I'm fully up to date! I also only have updates OFF and haven't deleted the schedule. I don't understand what the heck Ford is trying to do. They have to have the most inept software engineers in the world! So far nothing has installed on mine and I hope it stays that way until this all "SYNC's" LOL with Ford's systems.

I wonder if there is something like an unflipped switch in your as-built data that’s causing the server to send you an older update Ike 2.1.0. Not every OTA involved a full module software update. Some of them (or parts of them) involved very minor changes like a change to the module configuration to activate a feature (e.g., new camera angle, Securialert or horn & lights button in FordPass) that stopped well short of a software overhaul. If you have a missing feature that 2.1.0 would have activated, that might be why you’re getting it even though your software is otherwise up to date.

Sponsored

 

[Itsjustmd]

I wonder if there is something like an unflipped switch in your as-built data that’s causing the server to send you an older update Ike 2.1.0. Not every OTA involved a full module software update. Some of them (or parts of them) involved very minor changes like a change to the module configuration to activate a feature (e.g., new camera angle, Securialert or horn & lights button in FordPass) that stopped well short of a software overhaul. If you have a missing feature that 2.1.0 would have activated, that might be why you’re getting it even though your software is otherwise up to date.

Even after already sending us newer updates? That's crazy. It'd still mess things up, right?

 

[speedracercjr]

Even after already sending us newer updates? That's crazy. It'd still mess things up, right?

It certainly messed mine up!

 

[JEB]

Even after already sending us newer updates? That's crazy. It'd still mess things up, right?

Yes. Problem is that the updates aren’t always “newer” in the same way PC software frequently is. It isn’t cumulative—newer releases don’t include everything in the older releases plus the new stuff. They frequently just add the new stuff. And if you missed an “older” release, you might still be missing some of the changes that older release made even after a newer release. In that sense, the older release isn’t really older for you because it still carries unapplied changes.

And in answer to your second question, sure it can mess things up. Given what’s happened to a couple of people, like @speedracercjr (who seems to be a magnet for black cats, ladders and broken mirrors), the releases aren’t surgical. It’s blunt force trauma. If one release did lots of things, and you only need one small part of that release, you still get the whole thing. The hope is that the release containing something “new” for you would apply only what you need and disregard the rest, but that doesn’t seem to be what’s happening recently.

 

[JeffC57]

Yes. Problem is that the updates aren’t always “newer” in the same way PC software frequently is. It isn’t cumulative—newer releases don’t include everything in the older releases plus the new stuff. They frequently just add the new stuff. And if you missed an “older” release, you might still be missing some of the changes that older release made even after a newer release. In that sense, the older release isn’t really older for you because it still carries unapplied changes.

And in answer to your second question, sure it can mess things up. Given what’s happened to a couple of people, like @speedracercjr (who seems to be a magnet for black cats, ladders and broken mirrors), the releases aren’t surgical. It’s blunt force trauma. If one release did lots of things, and you only need one small part of that release, you still get the whole thing. The hope is that the release containing something “new” for you would apply only what you need and disregard the rest, but that doesn’t seem to be what’s happening recently.

Well, fortunately for me, my GWM, at ver EKP at the time the procedure was proposed by the software doctors at Ford, declined the surgery. Based on this PTS data, I think the decision avoided software malpractice.

 

[JEB]

Well, fortunately for me, my GWM, at ver EKP at the time the procedure was proposed by the software doctors at Ford, declined the surgery. Based on this PTS data, I think the decision avoided software malpractice.

Right. You don’t want to roll back the GWM. That would be bad.

But here’s the lingering, insidious problem. What if there was a change that 2.1.0 made to the configuration data that was included with the software revision to the GWM? Has that change been made? Do you still need it, which is why the server keeps trying to send you 2.1.0 despite your GWM being way out in front of the version in that distribution? Those are the more problematic questions.

 

[Mike G]

Right. You don’t want to roll back the GWM. That would be bad.

But here’s the lingering, insidious problem. What if there was a change that 2.1.0 made to the configuration data that was included with the software revision to the GWM? Has that change been made? Do you still need it, which is why the server keeps trying to send you 2.1.0 despite your GWM being way out in front of the version in that distribution? Those are the more problematic questions.

In that event couldn't he just do a config on the GWM to confirm he has the latest settings?

 

[Mike G]

Anyone have time for a vin check?
1FTFW1ED2MFA76509

Mike

 

[Jesse-Infotainment]

Right. You don’t want to roll back the GWM. That would be bad.

But here’s the lingering, insidious problem. What if there was a change that 2.1.0 made to the configuration data that was included with the software revision to the GWM? Has that change been made? Do you still need it, which is why the server keeps trying to send you 2.1.0 despite your GWM being way out in front of the version in that distribution? Those are the more problematic questions.

The config changed in the latest update and that is the latest config. If they rolled it back that would be a problem. Nothing is missing! It would possibly be if the outdated update succeeds though.

 

[Itsjustmd]

Yes. Problem is that the updates aren’t always “newer” in the same way PC software frequently is. It isn’t cumulative—newer releases don’t include everything in the older releases plus the new stuff. They frequently just add the new stuff. And if you missed an “older” release, you might still be missing some of the changes that older release made even after a newer release. In that sense, the older release isn’t really older for you because it still carries unapplied changes.

And in answer to your second question, sure it can mess things up. Given what’s happened to a couple of people, like @speedracercjr (who seems to be a magnet for black cats, ladders and broken mirrors), the releases aren’t surgical. It’s blunt force trauma. If one release did lots of things, and you only need one small part of that release, you still get the whole thing. The hope is that the release containing something “new” for you would apply only what you need and disregard the rest, but that doesn’t seem to be what’s happening recently.

I get what you're saying now. I guess I'm just not seeing how I could be missing a small part of the release if I used FDRS to update what that update should have updated. That's what I find weird. Why would an OTA have something relevant in it that FDRS doesn't. Seems like the system needs a lot of work.

 

[JEB]

In that event couldn't he just do a config on the GWM to confirm he has the latest settings?

I’m theorizing here. What if an update did more than one thing to more than one system? For example a software update to the GWM and an as-built tweak to another module, like the APIM to activate a new camera angle and Ford decided to just roll everything into one OTA? I’m not saying this is what happened in this instance but it could help explain the pattern of why we keep seeing people with supposedly up to date trucks still getting older distributions.

 

[Ruffner69]

Mike

Thank you

 

[mflynndelta]

Thank you

Auto update off, schedule cleared and wifi off but I still get this each time I start truck. Any suggestions?

 

[Paul Neubauer]

Auto update off, schedule cleared and wifi off but I still get this each time I start truck. Any suggestions?

It is asking to update instead of just automatically doing it behind the scenes.

 

[mflynndelta]

It is asking to update instead of just automatically doing it behind the scenes.

I am trying to prevent it from installing an old update. I already have bluecruise

Sponsored