Original owner of 22 lariat need help please

[Vegas]

This what it showed than and still does to date .

Sponsored

 

[Jesse-Infotainment]

If they manually updated.. THen it was postponed. Since Ruged has your vin he can see if indeed they did the updates in FDRS.. then you can ignore the Software update tab in the vehicle.

FDRS and the OTA side is not linked. You can get an OTA for an Update that has already been installed manually via FDRS. The update will run the interrogator and see the current version nd then either call the update successful or cancel it and it will show as incomplete ..

 

[Vegas]

This is the sequence of what happens . I make sure I have good WiFi . Than I go to the software update screen . Pix 1 . Than I hit the update now it says to turn off car and secure the truck. Which I lock . I watch the my passenger window and it counts down it get to zero then it says on the screen it preparing update . Than the car makes some noises and clicks and a few minutes later I see thru the screen that the update has postponed. That the cycle see pix 2 .

 

[Vegas]

When he is online again maybe he can rerun the vin I sent him and he see what the dealer head technician did and suggestions

 

[rugedraw]

@Jesse-Infotainment Unfortunately, with my watered-down PTS access, I can no longer see vehicle history to see what the dealer did or not. I can also no longer see the software updates tab to see what strat his BCM is on compared to what the OTA wants to send him.

@Vegas The SoC and battery capacity being reported to the cloud seems to be fine. I am not sure what this message "unrecognizedFields":"\"updateTimeInSeconds\":358" means or if that has something to do with why the OTA is not installing.

If you have FORScan, try pulling the module details of your BCM to see what strategy it is on. According to PTS, you should have AAT and this OTA wants to install AAJ. If you already have AAJ installed, then the dealer updated it.

The problem with the battery disconnect for 20 minutes trick is that I have seen that cause an OTA trigger to get canceled. Because to me, there is no clear-cut reason why this OTA is failing, I would try disconnecting the battery to see if it helps or not because clearly, it does not want to install anyway. The last 6 OTA's that have been sent to you have all failed, so something different needs to be tried.

 

[Vegas]

After my last try 30 minutes it didn’t install it had a new message I never saw before . See below . The frunk update not installed but this message appeared

 

[chl]

@Jesse-Infotainment Unfortunately, with my watered-down PTS access, I can no longer see vehicle history to see what the dealer did or not. I can also no longer see the software updates tab to see what strat his BCM is on compared to what the OTA wants to send him.

@Vegas The SoC and battery capacity being reported to the cloud seems to be fine. I am not sure what this message "unrecognizedFields":"\"updateTimeInSeconds\":358" means or if that has something to do with why the OTA is not installing.

If you have FORScan, try pulling the module details of your BCM to see what strategy it is on. According to PTS, you should have AAT and this OTA wants to install AAJ. If you already have AAJ installed, then the dealer updated it.

The problem with the battery disconnect for 20 minutes trick is that I have seen that cause an OTA trigger to get canceled. Because to me, there is no clear-cut reason why this OTA is failing, I would try disconnecting the battery to see if it helps or not because clearly, it does not want to install anyway. The last 6 OTA's that have been sent to you have all failed, so something different needs to be tried.

The battery SOC reported to the cloud was inaccurate in my case...
The 12V battery needs to by 85% or better from what I have read or the/some updates will get delayed until it reaches that level.
A lot of threads about OTAs and low battery.
Do what they say to charge it up - just driving it for a couple hours as Ford suggested did not work for me, but putting it on my FCSP overnight to charge from 70% to 90% did the trick.

 

[RickLightning]

This is the sequence of what happens . I make sure I have good WiFi . Than I go to the software update screen . Pix 1 . Than I hit the update now it says to turn off car and secure the truck. Which I lock . I watch the my passenger window and it counts down it get to zero then it says on the screen it preparing update . Than the car makes some noises and clicks and a few minutes later I see thru the screen that the update has postponed. That the cycle see pix 2 .

So here's my 2 cents:

- You don't need WiFi at all. Your update is downloaded already, you don't need any connection.
- Your 12v is the issue. You haven't disconnected it that I see as recommended. Or, put it on a charger (passenger panel connections) until it's fully charged.

 

[Vegas]

I will put it on charger but I am unable to disconnect it because of issues with age and a disability I can not reach it to take off the right frunk liner . I have the left panel off where I can hook up my charger overnight if you think if it will work . I did drive it after the new battery install for 5 hours of highway driving.

 

[rugedraw]

The battery SOC reported to the cloud was inaccurate in my case...
The 12V battery needs to by 85% or better from what I have read or the/some updates will get delayed until it reaches that level.
A lot of threads about OTAs and low battery.
Do what they say to charge it up - just driving it for a couple hours as Ford suggested did not work for me, but putting it on my FCSP overnight to charge from 70% to 90% did the trick.

If the SoC being reported to the cloud is wrong, then the BMS data quality is compromised and PTS will show you that is the case. No harm in trying a BMS reset once the battery is at 100% charge.

 

[rugedraw]

After my last try 30 minutes it didn’t install it had a new message I never saw before . See below . The frunk update not installed but this message appeared

The OTA failed; that's why you got that message. It failed due to a software mismatch, so it is possible the dealer did update it and the OTA failed because there was nothing to update.

Sponsored