Update Unable to Install (23-PU0630-YAW-RT)

[imarun]

My truck (VIN# 1FTFW1ED1MFA45784) has been trying to install this priority update (23-PU0630-YAW-RT) for the past three weeks. It always fails and reschedules it for the next day. First I thought that it could be due to low battery charge, However, that was not the case since I tried after charging the battery to 100% a few times. It never succeeded to install. The error message says that it was interrupted by another process since one of the preconditions was not met. It does not specifically says which precondition was not met. Any ideas about how to get it installed?

Sponsored

 

[rugedraw]

It is repeatedly failing due to poor battery stats. This is what it reported to the cloud when you tried to install it last night. Your capacity is at 22 out of 80 and charge is at 54%. If you fully charged your battery and this is what you're getting, either your battery needs to be replaced, or your BMS is way off and could use a reset. I would fully charge the battery again, reset the BMS< and try to install the update right after.

"errorCode":"InhibitRequiredHvNotQualifiedLvLow(204)""totalLvBatteryCapacity":"22""currentLvBatteryDataQuality":"OK""currentLvBatteryVoltage":"12""currentLvBatterySoc":"54""currentLvBatteryTemperature":"31""dynamicPostUpdateSocThreshold":"41""estimatedTimeToActivate":"450""estimatedTimeIncludingRollback":"900""currentDrainRate":"9"

Keep in mind that this OTA was sent to you on 3/14 and the OTA trigger is good for 30 days. You have 3 days to get this update to install before it times out and you have to wait for it to be resent. On 3/14, you were also sent 22-PU1009-TLC-CSM2 about 25 minutes before this one, but this update activated the trigger first, which means the OTA trigger for the other update will expire before the one that is active. This means if the active update goes all 30 days without installing and fails, the other pending update will also fail before it has a chance to install.

 

[imarun]

It is repeatedly failing due to poor battery stats. This is what it reported to the cloud when you tried to install it last night. Your capacity is at 22 out of 80 and charge is at 54%. If you fully charged your battery and this is what you're getting, either your battery needs to be replaced, or your BMS is way off and could use a reset. I would fully charge the battery again, reset the BMS< and try to install the update right after.

"errorCode":"InhibitRequiredHvNotQualifiedLvLow(204)""totalLvBatteryCapacity":"22""currentLvBatteryDataQuality":"OK""currentLvBatteryVoltage":"12""currentLvBatterySoc":"54""currentLvBatteryTemperature":"31""dynamicPostUpdateSocThreshold":"41""estimatedTimeToActivate":"450""estimatedTimeIncludingRollback":"900""currentDrainRate":"9"

Keep in mind that this OTA was sent to you on 3/14 and the OTA trigger is good for 30 days. You have 3 days to get this update to install before it times out and you have to wait for it to be resent. On 3/14, you were also sent 22-PU1009-TLC-CSM2 about 25 minutes before this one, but this update activated the trigger first, which means the OTA trigger for the other update will expire before the one that is active. This means if the active update goes all 30 days without installing and fails, the other pending update will also fail before it has a chance to install.

Thanks for looking into it. Looks like my battery is having issues. I tried this update after fully charging it and it still failed. I then reconnected the charger and it reported a charge level of only 54%. I am having frequent battery issue that I have to recharge my battery at least twice a week. I guess, I need a new battery. I will try the update again after replacing the battery.

 

[Bo15]

I'm still showing this from March 7th. Nothing sent since then. Never did the inhibit EV driving to recalibrate after install. Not sure it really installed or is stuck maybe. VIN 1FTFW1EDXMFA85054

 

[imarun]

I got a new battery installed (X2 AGM H7 from Battery Plus) and charged it completely. Reset the BMS module (5 times high beam and 3 times break, the battery sign did flash). I just tried the update again and still it did not succeed. Anything else I should try?

 

[rugedraw]

I got a new battery installed (X2 AGM H7 from Battery Plus) and charged it completely. Reset the BMS module (5 times high beam and 3 times break, the battery sign did flash). I just tried the update again and still it did not succeed. Anything else I should try?

Looks like the OTA process being a little b*tch. Capacity is beyond good but charge was reported as 81% at the time it tried to install which isn't bad, but it is unknown what the actual required charge is. PITA, but just keep trying. I've seen this happen many times and it will go through eventually.

"errorCode":"InhibitRequiredHvNotQualifiedLvLow(204)""totalLvBatteryCapacity":"83""currentLvBatteryDataQuality":"NotWithinSpec""currentLvBatteryVoltage":"12""currentLvBatterySoc":"81""currentLvBatteryTemperature":"35""dynamicPostUpdateSocThreshold":"41""estimatedTimeToActivate":"450""estimatedTimeIncludingRollback":"900""currentDrainRate":"9"

 

[rugedraw]

I'm still showing this from March 7th. Nothing sent since then. Never did the inhibit EV driving to recalibrate after install. Not sure it really installed or is stuck maybe. VIN 1FTFW1EDXMFA85054

It was sent to you twice on the same day. Installed the first time and failed he second becase it was already installed.

@imarun

Look at his battery stats compared to yours. SUPER low and it went through. These are the things I don't understand no matter how many times I see this.

 

[imarun]

Looks like the OTA process being a little b*tch. Capacity is beyond good but charge was reported as 81% at the time it tried to install which isn't bad, but it is unknown what the actual required charge is. PITA, but just keep trying. I've seen this happen many times and it will go through eventually.

"errorCode":"InhibitRequiredHvNotQualifiedLvLow(204)""totalLvBatteryCapacity":"83""currentLvBatteryDataQuality":"NotWithinSpec""currentLvBatteryVoltage":"12""currentLvBatterySoc":"81""currentLvBatteryTemperature":"35""dynamicPostUpdateSocThreshold":"41""estimatedTimeToActivate":"450""estimatedTimeIncludingRollback":"900""currentDrainRate":"9"

You were right. Eventually, it succeeded yesterday!

 

[WalterMitty]

It was sent to you twice on the same day. Installed the first time and failed he second becase it was already installed.

@imarun

Look at his battery stats compared to yours. SUPER low and it went through. These are the things I don't understand no matter how many times I see this.

My last update is showing March 14, 2023 and was 23-PU1113-UNX-DC. Is this the latest and greatest update?

Thanks

 

[rugedraw]

My last update is showing March 14, 2023 and was 23-PU1113-UNX-DC. Is this the latest and greatest update?

Thanks

That update is a minor config update for the TCU to fix an issue some vehicle were having with connectivity. It is not the "latest" in terms of the string of updates that lead to new or improved features.

 

[WalterMitty]

That update is a minor config update for the TCU to fix an issue some vehicle were having with connectivity. It is not the "latest" in terms of the string of updates that lead to new or improved features.

Any recommendations on how to speed up the updates? Or just be patient?

 

[rugedraw]

Any recommendations on how to speed up the updates? Or just be patient?

There is nothing you can do so speed up the OTA process. The only thing you can do is use a Mongoose and FDRS to do them yourself.

Sponsored