Search results

Looking into it. Stand by. As was mentioned, your truck has expired BC maps and that should not be the case as I see the warranty started on 5/31/24. I am not sure what is going on and am consulting with someone else to figure it out.

Not much you can say, really. Your truck is not reporting any codes I can use to give you some leverage to get them to do at least some of the updates. I'll be able to see if they do any of them before you pick it up, but other than asking nicely and hope they do it, there isn't much you can do...

Not sure about the failed update and what you're seeing. Your OTA dashboard in PTS does not show any recent OTA history.

@DeusEx I don't mind at all. I don't want a monopoly on checking VIN's. lol I appreciate the help from you or anyone that has PTS/FDRS access with these things.

In these cases, what I do is pull the as-built data of the IPMA module to compare what certain lines that have to do with BC functionality are showing can compare it to some notes I keep that shows what it should be showing. For some reason, certain updates that have nothing to do with the IPMA...

@j8g VIN?

Yea, I remember you mentioning that. I asked you for the VIN so I can look it to it, but never heard from you.

Very common. Every inhibit OTA says the update will take longer than it actually does.

No where that I know of. You'd need to pull them off of another vehicle with FORScan, I guess. It's something I have never messed with because it goes beyond the scope of things I am comfortable doing.

It is newer, but it is being called 1.3 which is confusing, but that's what it is. When updating with FDRS, the PSCM & IPMA updates are tied together and have to done at the same. The one Mach E I checked that got the 1.3 OTA did not show any updates pending in FDRS for the IPMA or PSCM when the...

No worries. That info is in the screenshot I posted, but I don't expect you to be able to decipher everything there. The OTA trigger was accepted by your car at 11:59am on 6/28 and is good for 336 hours (2 weeks). So it will expire at that time on 7/12.

@lazjen In that case, if you can get me the VIN of any Sync 4 Ford vehicle there with working connected features, I can pull the as built data off of it to compare the country code on the TCU of that vehicle to yours and we can take it from there. Your truck is on the latest Sync version and...

Because you posted your VIN before and I pulled the as built data from your truck to check this. The dealer is not going to know what you're talking about, but you can take that route if you want.

This was brought up in the Mach E forum yesterday. The answer is: Nobody knows for sure. The IPMA update the Mach E's are getting with this OTA differs from the one in FDRS that has been believed to be part of the BC 1.4 puzzle for many months now. Unlike the 7.0.0 OTA for BC 1.4 that was...

It will either download the files and install before the OTA trigger expires, or it won't and it will fail and you'll have to wait for it to be resent. Dealers can apply the update manually, but they are usually not helpful with these types of things.

Yea OTA 6.4.0 is in your queue right now. It is not downloading the files for some reason. Not the first time I see this, but there is nothing you can do to help the process.

No, it has to be a legit start. He and a few others claim they got an email first. No email; no update it seems. Still too early to say.

https://www.macheforum.com/site/threads/i-just-got-bluecruise-1-3-on-my-2022.37049/#post-819034 A member on the Mach E forum in early access reported getting BC 1.3 with an update today. I checked his VIN and it's legit. It updated the IPMA. Hopefully it makes its way to you guys soon.

I'm guessing that is from the last OTA you got on 6/12.

Not complete means the OTA failed. PTS shows it failed due to a hash mismatch. A bunch of people on the Mach E forums have reported this update failing for them today and a few VINs I checked showed it failed with the same error. The issue is on Ford's side.