22S41 Recall Software - Server Deployment Issue

[GoGoGadgetMachE]

I think you're missing the point. There's still a bunch of issues I think this caused. We have confirmed that a few people had the wrong update installed and cleared out of the recall system.

Just because OTA's work doesn't mean there's not heartburn in other regards.

No, I'm not missing the point.

I've read all 17 pages of this thread, from the start. There was a TON of posts over the weekend around "the recall getting pulled" and "things are so confused now" and on and on, with all kinds of speculation.

At this point, there's a limited set of possibilities:

1. Someone has the software fix through a formal Ford mechanism - OTA or dealer FDRS, doesn't matter, the important things are they have it and it's marked as done. Ideal case.
2. Someone has the software fix through self-installed FDRS. In that case, I'd expect (although this is an assumption at the moment) that at next OTA pass, they will get sorted on the flag, in the worst case.
3. Someone did a dealer trip that was wasted and had the flag flipped. OTA will clean that up. The OTA is being done aggressively as we know from reports on here. This is the least desirable of the three options but still gets to the right place in the end.

That's the full list, right? In all three cases we quickly get to the right state, which is software installed, flag flipped, just not necessarily in the ideal way.

Heartburn at this point would only be from people in bucket 2 who are worked up over the flag not being flipped when, let's be honest, if you're using FDRS to do stuff yourself, you pay your money and you take your chances, and you know that it's part of that deal, and people in bucket 3, who are "officially" fixed but not yet fixed (but will be, soon, because again, aggressive OTA)...

Sponsored

 

[Mathington]

and it's installing now.

okay, so, the recall wasn't pulled, it's still moving forward as an OTA. So I think we can move past all of the "recall was pulled" bit once and for all.

Are you in Early Access?

 

[GoGoGadgetMachE]

I guess investigating an issue, providing proof to that issue and keeping the main thread honestly updated with latest news is now considered mob rule, speculative and assumptive.

The fanboys are out in force today. I'm off ?

ok, well, at the risk of being a fanboy, I'm just going to point to this:

https://www.macheforum.com/site/thr...are-server-deployment-issue.19486/post-461361

This whole thread is an embarrassing sh*tshow at this point, and people that I thought would know better, didn't.

 

[Neil4Real]

No, I'm not missing the point.

I've read all 17 pages of this thread, from the start. There was a TON of posts over the weekend around "the recall getting pulled" and "things are so confused now" and on and on, with all kinds of speculation.

At this point, there's a limited set of possibilities:

1. Someone has the software fix through a formal Ford mechanism - OTA or dealer FDRS, doesn't matter, the important things are they have it and it's marked as done. Ideal case.
2. Someone has the software fix through self-installed FDRS. In that case, I'd expect (although this is an assumption at the moment) that at next OTA pass, they will get sorted on the flag, in the worst case.
3. Someone did a dealer trip that was wasted and had the flag flipped. OTA will clean that up. The OTA is being done aggressively as we know from reports on here. This is the least desirable of the three options but still gets to the right place in the end.

That's the full list, right? In all three cases we quickly get to the right state, which is software installed, flag flipped, just not necessarily in the ideal way.

Heartburn at this point would only be from people in bucket 2 who are worked up over the flag not being flipped when, let's be honest, if you're using FDRS to do stuff yourself, you pay your money and you take your chances, and you know that it's part of that deal, and people in bucket 3, who are "officially" fixed but not yet fixed (but will be, soon, because again, aggressive OTA)...

I guess not much comprehending was done in the 17 pages? For one, you're differentiating between "dealer FDRS" and "self-installed FDRS" which is the same thing.

This thread was invaluable as quite a few people have said they got the recall done, when in fact they didn't. There is hope it'll get "cleaned up" via OTA, but no one knows. The OTA updates have not been in smooth in any sense of the word. All OTA update campaigns have been horrible - paused midway, abandoned completely and started a new numbering sequence to try again, people getting "stuck," etc.

It most certainly WAS unavailable and, hopefully, people that saw this were able to reschedule appointments they had for early this week until it gets resolved.

I'm not really sure what you're trying to prove? The update was UNAVAILABLE to be installed by dealers, which is everything we've been discussing on this thread and IN THE FIRST PAGE. Cool, you got it OTA when many, many others haven't. That doesn't mean it is readily available since you can't force an OTA.

 

[tobin1920]

No, I'm not missing the point.

I've read all 17 pages of this thread, from the start. There was a TON of posts over the weekend around "the recall getting pulled" and "things are so confused now" and on and on, with all kinds of speculation.

At this point, there's a limited set of possibilities:

1. Someone has the software fix through a formal Ford mechanism - OTA or dealer FDRS, doesn't matter, the important things are they have it and it's marked as done. Ideal case.
2. Someone has the software fix through self-installed FDRS. In that case, I'd expect (although this is an assumption at the moment) that at next OTA pass, they will get sorted on the flag, in the worst case.
3. Someone did a dealer trip that was wasted and had the flag flipped. OTA will clean that up. The OTA is being done aggressively as we know from reports on here. This is the least desirable of the three options but still gets to the right place in the end.

That's the full list, right? In all three cases we quickly get to the right state, which is software installed, flag flipped, just not necessarily in the ideal way.

Heartburn at this point would only be from people in bucket 2 who are worked up over the flag not being flipped when, let's be honest, if you're using FDRS to do stuff yourself, you pay your money and you take your chances, and you know that it's part of that deal, and people in bucket 3, who are "officially" fixed but not yet fixed (but will be, soon, because again, aggressive OTA)...

As someone in your 3rd bucket, I appreciate your confidence that things will be corrected OTA. I’ll be super relieved once we have reports of that actually happening for people [in bucket 3].

 

[Neil4Real]

ok, well, at the risk of being a fanboy, I'm just going to point to this:

https://www.macheforum.com/site/thr...are-server-deployment-issue.19486/post-461361

This whole thread is an embarrassing sh*tshow at this point, and people that I thought would know better, didn't.

Thanks to you.

 

[Neil4Real]

As someone in your 3rd bucket, I appreciate your confidence that things will be corrected OTA. I’ll be super relieved once we have reports of that actually happening for people [in bucket 3].

Don't believe his spew, he doesn't know what he's talking about and now he's HIGHLY SPECULATING which he accused everyone else of LOL.

 

[GoGoGadgetMachE]

Are you in Early Access?

Honestly, I don't know. The site says I am, but I've never had any real evidence that I am - OTAs don't seem to show up particularly early compared to what others have reported, and I never get any of the EA survey emails or anything like that.

 

[Neil4Real]

Honestly, I don't know. The site says I am, but I've never had any real evidence that I am - OTAs don't seem to show up particularly early compared to what others have reported, and I never get any of the EA survey emails or anything like that.

FALSE, they DO come out earlier to EA members, AS REPORTED, BC was insanely sooner to EA members than to non-EA.

 

[DevSecOps]

ok, well, at the risk of being a fanboy, I'm just going to point to this:

https://www.macheforum.com/site/thr...are-server-deployment-issue.19486/post-461361

This whole thread is an embarrassing sh*tshow at this point, and people that I thought would know better, didn't.

You know Michael - The updates were not available and dealers are still not able to install them in FDRS. So that was not speculative and it's 100% true as of this moment.

When a system that many of us AND DEALERS rely on, no longer has something we made an assumption that it was pulled. My main thread said all along until today that it was "investigative" and we were looking into why. We said all along we didn't know why. But the fact remains, it was not in FDRS and still is not in FDRS which thousands of dealers in the USA alone rely on to install updates. Dealers don't install updates with OTA and there's no such thing as an FDRS OTA.

Here's my VIN and I DO NOT HAVE the recall. Do you see any updates available?

 

[GoGoGadgetMachE]

Don't believe his spew, he doesn't know what he's talking about and now he's HIGHLY SPECULATING which he accused everyone else of LOL.

how so?

What are the other cases outside of the three I gave? If you're going to say I don't know what I'm talking about, you need to be specific. What specifically have I said that's incorrect or uninformed?

We know from other OTA experience in the past that Ford's systems pick up OTA status and reflect after the OTA is offered, aligning with FDRS updates. This has been demonstrated repeatedly, by people on this very thread in other circumstances. The back end picks up the modules are updated, records it is, and doesn't offer the OTA for it.

Thanks to you.

 

[Neil4Real]

You know Michael - The updates were not available and dealers are still not able to install them in FDRS. So that was not speculative and it's 100% true as of this moment.

When a system that many of us AND DEALERS to rely on no longer has something we made an assumption that it was pulled. My main thread said all along until today that it was "investigative" and we were looking into why. We said all along we didn't know why. But the fact remains, it was not in FDRS and still is not in FDRS which thousands of dealers in the USA alone rely on to install updates. Dealers don't install updates with OTA and there's no such thing as an FDRS OTA.

Here's my VIN and I DO NOT HAVE the recall. Do you see any updates available?

Objection - speculation! Lol, yet he's going on to now speculate non-stop and trash people like yourself looking out for others.

 

[GoGoGadgetMachE]

FALSE, they DO come out earlier to EA members, AS REPORTED, BC was insanely sooner to EA members than to non-EA.

I didn't say that they didn't. What I said was that in my specific case, I didn't know if I'm successfully in EA or not. I have no idea how you took that differently.

 

[WyldStallyn]

ok, well, at the risk of being a fanboy, I'm just going to point to this:

https://www.macheforum.com/site/thr...are-server-deployment-issue.19486/post-461361

This whole thread is an embarrassing sh*tshow at this point, and people that I thought would know better, didn't.

I was going to ignore the last few posts but I wanted to add that the thread has been helpful in ways which @Neil4Real described. Also, the fact that this is a safety recall and we have owners who now think that they have the recall updates when they actually don't is a problem. We also have dealerships likely releasing vehicles from legal delivery hold without the recalls actually being applied. Until we see how these issues are resolved this thread is completely relevant.

 

[GoGoGadgetMachE]

You know Michael - The updates were not available and dealers are still not able to install them in FDRS. So that was not speculative and it's 100% true as of this moment.

When a system that many of us AND DEALERS rely on, no longer has something we made an assumption that it was pulled. My main thread said all along until today that it was "investigative" and we were looking into why. We said all along we didn't know why. But the fact remains, it was not in FDRS and still is not in FDRS which thousands of dealers in the USA alone rely on to install updates. Dealers don't install updates with OTA and there's no such thing as an FDRS OTA.

Here's my VIN and I DO NOT HAVE the recall. Do you see any updates available?

I don't have FDRS, so I don't know if I have updates available in it. I do know I'm getting the updates as OTA.

I'm not disputing anything about seeing things in FDRS. What I am saying is that all weekend, this thread went in lots of directions because the update wasn't in FDRS. We know - because you've confirmed it - that it was a mistake to not be in there.

I completely agree that this is not a good situation - I said so in my listing of possible cases.

So far, I'm not seeing anyone dispute my breakdown of the current situation at this point. Some people are in the bad way, some people are not, through three specific sets of situations. Is that right?

Sponsored