Post here if you have an active FDRS account and are willing to look up info for others

[Mike G]

@Mike G can you run my vin one more time, I left my car on for 4 hours just to see if it would download that pending update. Just trying all the tips in this forum before I take it to a dealer.

Here's what the OTA dashboard looks like this morning:

And here's the list of available software updates in FDRS as well:

Sponsored

 

[gtmoy]

Well, I downloaded FDRS and tried to update myself but it failed. I then updated the IPMA and was then able to update to 6.14.0

3FMTK4SX5NMA20253

Does anyone know if there's anything else I need to do except wait patiently for BC1.3?

THanks

This update has been sent to you a dozen times and it failed every time with the same error:

"errorCode":"FordPartNumberMismatch(55)""errorCategory":"ERROR_CATEGORY_ALM(3)""ecuId":"2000""fpn":"PU5T-14H009-MAA"

This is very strange and I have no idea what is causing this. I don't see your APIM has never been replaced, so I am not sure why the mothership is confused with part numbers. I don't recall seeing this particular error before. Based on this, you have a leg to stand on to get your dealer to try and do it for you. I am not sure if FDRS will be able to circumvent whatever the issue is with the OTA side of things.

 

[rugedraw]

Well, I downloaded FDRS and tried to update myself but it failed. I then updated the IPMA and was then able to update to 6.14.0

3FMTK4SX5NMA20253

Does anyone know if there's anything else I need to do except wait patiently for BC1.3?

THanks

No, you no longer need to wait. I'll message you.

 

[zooka]

I'm not sure which fuse you have to pull. In theory, disconnecting the 12v for 30 minutes or so should cause a full reset of everything. Again, I am not sure if this is a good idea or not or if this will help the cause. Maybe @Mike G or @Mach-Lee can provide an opinion on this before you do anything.

@rugedraw can you see if you see the vehicle ping back, I went ahead and disconnected the 12v for 30min , redid the 12v learn and drove for 30min

 

[rugedraw]

@rugedraw can you see if you see the vehicle ping back, I went ahead and disconnected the 12v for 30min , redid the 12v learn and drove for 30min

Sorry man, but it looks exactly the same as before.

 

[zooka]

Sorry man, but it looks exactly the same as before.

Thanks , guess its going to the dealer. I have not even had it a month. So weird because it shows all the connected features and reports back to ford pass app. I even test the hotspot to check data throughput all seems good. Even got the up and down communication with ford icon. @rugedraw I did call ford in vehicle support and they said the see diagnostic trouble codes every day back to the purchase of the vehicle, they said they couldn't go in to detail what there were though. Do you see those through FDRS?

 

[rugedraw]

Thanks , guess its going to the dealer. I have not even had it a month. So weird because it shows all the connected features and reports back to ford pass app. I even test the hotspot to check data throughput all seems good. Even got the up and down communication with ford icon. @rugedraw I did call ford in vehicle support and they said the see diagnostic trouble codes every day back to the purchase of the vehicle, they said they couldn't go in to detail what there were though. Do you see those through FDRS?

Codes it reported today are below. There are some lost comms codes between the TCU and some modules, but can't say that is the direct cause. It is difficult to diagnose things like this based on looking on codes unless there is something very obvious. Either way, it may not be a bad idea to take it to them. While it is there, tell them that BC is behaving erratically and hopefully they'll update the CMR for you based on the U0565 code it is reporting.

 

[lanebk]

The BC 1.3 update is reporting not completed. I was wondering if someone could check my vin: 3FMTK3SU7NMA57496? I'm curious if anything actually updated or if the reason for the error is there.

Thanks.

 

[Grnfoot]

Would someone check for available updates and OTA if any are Queued.
thanks. Alan
3FMTK3SU4NMA58329

 

[Mike G]

I'm not sure which fuse you have to pull. In theory, disconnecting the 12v for 30 minutes or so should cause a full reset of everything. Again, I am not sure if this is a good idea or not or if this will help the cause. Maybe @Mike G or @Mach-Lee can provide an opinion on this before you do anything.

 

[Mike G]

The BC 1.3 update is reporting not completed. I was wondering if someone could check my vin: 3FMTK3SU7NMA57496? I'm curious if anything actually updated or if the reason for the error is there.

Thanks.

The OTA was cancelled by the cloud server. And apparently it was for only the PSCM, not the IPMA and PSCM.

Your IPMA software is also not at the rev level needed for BC 1.3. That would also have to be updated. When doing the IPMA update using FDRS it is scripted to coordinate the PSCM update at the same time for dependency purposes.

I don't know why the PSCM OTA was cancelled by the server but it may be because it was only 'part of the story'...since without the IPMA being updated, (which is a far bigger update) you wouldn't have ended up with BC 1.3 anyway.

Here's the list of available software this morning in FDRS:

 

[Mike G]

Would someone check for available updates and OTA if any are Queued.
thanks. Alan
3FMTK3SU4NMA58329

No OTA history or status showing for your VIN.

In FDRS you have the subset of the powertrain updates that showed up yesterday for everybody, as well as the previously released BCM update.

 

[lanebk]

The OTA was cancelled by the cloud server. And apparently it was for only the PSCM, not the IPMA and PSCM.

Your IPMA software is also not at the rev level needed for BC 1.3. That would also have to be updated. When doing the IPMA update using FDRS it is scripted to coordinate the PSCM update at the same time for dependency purposes.

I don't know why the PSCM OTA was cancelled by the server but it may be because it was only 'part of the story'...since without the IPMA being updated, (which is a far bigger update) you wouldn't have ended up with BC 1.3 anyway.

Here's the list of available software this morning in FDRS:

Thank you for the information and explanation. I'm not quite ready to progress from Forscan to FDRS, so I'll keep an eye out for the needed OTAs. I appreciate the help

 

[bloodstar57]

Can someone check my VIN for available updates. I think something is wrong with my car.
thank you very much!
3FMTK4SX8NMA57832

 

[Mike G]

Can someone check my VIN for available updates. I think something is wrong with my car.
thank you very much!
3FMTK4SX8NMA57832

So here's the thing. You haven't gotten an OTA in at least 60 days and probably longer. Your car was produced at the end of September 22 and you bought it on 3 July of last year. It sat for a long time and didn't receive many OTAs that other cars got in the meantime, because dealers don't enable OTAs to download while they have the car.

I would bet that once that gateway update in this list below is applied using FDRS (along with whatever else the dealer tech is willing to update) that your car would once again get back on track. Bottom line, you need to be caught up. You're so far behind that the system isn't offering you anything. You can call the BEV team at 800-392-3673 or 866-631-3788 x79969 and get them to take a look and then ask them to contact your local dealer to hopefully arrange something. This could be covered under warranty labor code OTAWTY. But they would need to confirm that.

Sponsored