When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Going back to February 12 they tried to do some updates, but they all failed with the battery condition failure.
Procedure unsuccessful. - BatteryCheck Poor battery condition Battery Voltage = 13.197v Minimum required = 10.0v Battery Estimated State of Charge = 9% Minimum required = 50%
April 3 there was this:
It looks like they just gave up even trying?
Thanks for the assist! I hope you looked that up in PTS and not FDRS. They are banning FDRS accounts now if you type in a VIN without being plugged directly into the vehicle. Just FYI in case you didn't know.
If they ran a PMI on the TCU, it seems like they may suspect a bad modem. I did see a code in February citing a component failure in the TCU, but that isn't why the IPC update was failing back then. I can tell when an update is failing due to a lack of connectivity, and that was not the case in October and November. If the TCU did go bad which is possible, replacing the TCU won't address the failed IPC update. It will fail again whenever they send it again.
They may not have given up even though it seems that way. The TCU is programmed using a USB. They could have popped the USB in to PMI the new modem and just closed out FDRS without confirming the update went through. I hope that's what they did, because you can't just put a new TCU in there without programming it. The only way I can confirm that the PMI was done is with FDRS to compare the files FDRS downloads to the strategy the TCU is currently on. I stopped paying for FDRS when they started banning accounts, so I can't verify if the PMI was actually done anymore.
Thanks for the assist! I hope you looked that up in PTS and not FDRS. They are banning FDRS accounts now if you type in a VIN without being plugged directly into the vehicle. Just FYI in case you didn't know.
Yep, that was from PTS.
It'd be crazy long to screenshot all of the history - would anything stand out with regard to the other updates you mentioned that I could scan for in the history?
Thanks again for your help. I just don’t understand how you can have this solution but Grapevine Ford and FORD engineering are either unaware or haven’t tried it
I will once again insist that I see the update history when I go to the dealership on Monday. I’m not exactly filled with confidence.
Going back to February 12 they tried to do some updates, but they all failed with the battery condition failure.
Procedure unsuccessful. - Battery Check Poor battery condition Battery Voltage = 13.197v Minimum required = 10.0v Battery Estimated State of Charge = 9% Minimum required = 50%
Why would the SOC be 9%? Is that net current in/out as measured by the BMS?
It'd be crazy long to screenshot all of the history - would anything stand out with regard to the other updates you mentioned that I could scan for in the history?
No need; I know for a fact they didn't update the IPC. That I can check by comparing the IPC strategy file in his ab data to the one the OTA wanted to install.
Originally Posted by SkyeCam
Thanks again for your help. I just don’t understand how you can have this solution but Grapevine Ford and FORD engineering are either unaware or haven’t tried it
I will once again insist that I see the update history when I go to the dealership on Monday. I’m not exactly filled with confidence.
The thing is, they are addressing an issue with your modem and assuming that is the reason the IPC OTA update was failing. In their eyes, they are doing the right thing. I don't think you need to ask for update history. All you need to ask them to do is to update the IPC after the fix whatever is wrong with the TCU. Remember you catch more flies with sugar than with sh*t, so I would recommend you go in there nice and playing the victim instead of going in there guns blazing.
Screenshot below shows that when the OTAs were sent, the truck pinged the cloud back to receive it. It shows the logs posting which would not have happened if the modem was bad back then. The people in the service department do not know how to interpret this information. Ford does not train them to know what any of this means.
@rugedraw is absolutely right. Sugar is the best policy. Be part of the team that is trying to fix the problem works well. I did the same over a leaking F150 Sunroof. Left a note for the Tech (I got lucky with a smart one) going through all the symtoms and all the things I had checked. Got a great note back .