Yet another OTA issue

[Deleted member 4994]

I've been trying to install the OTA for "Battery and Remote Start Enhancements" and all I get is the useless "[...] interrupted by another process" message (why can't they give a more insightful message ?).
It's not an LVB issue, the last time it failed the SOC was 95%, I had just returned from charging it and the car was parked with everything unplugged.
The first time it failed it was from an automatic update, all the other times I forced the update.

Sponsored

 

[JohnFoxeSheets]

I've been trying to install the OTA for "Battery and Remote Start Enhancements" and all I get is the useless "[...] interrupted by another process" message (why can't they give a more insightful message ?).
It's not an LVB issue, the last time it failed the SOC was 95%, I had just returned from charging it and the car was parked with everything unplugged.
The first time it failed it was from an automatic update, all the other times I forced the update.

Was the LVB SoC 95% or the HVB? Usually that message means the LVB is too low for the update to complete. Ironically I think the update that is trying to install is the one that fixes that problem!

 

[Dysan911]

I wonder if a Sync Reboot would help?

 

[rugedraw]

I've been trying to install the OTA for "Battery and Remote Start Enhancements" and all I get is the useless "[...] interrupted by another process" message (why can't they give a more insightful message ?).
It's not an LVB issue, the last time it failed the SOC was 95%, I had just returned from charging it and the car was parked with everything unplugged.
The first time it failed it was from an automatic update, all the other times I forced the update.

The only way to check is with the VIN.

 

[Mach-Lee]

I've been trying to install the OTA for "Battery and Remote Start Enhancements" and all I get is the useless "[...] interrupted by another process" message (why can't they give a more insightful message ?).
It's not an LVB issue, the last time it failed the SOC was 95%, I had just returned from charging it and the car was parked with everything unplugged.
The first time it failed it was from an automatic update, all the other times I forced the update.

Here's the list of everything to avoid failures:

Thread 'How To Get Failed OTAs To Install'

Someone can check your VIN why it failed, sometimes it's nothing you can do anything about.

 

[Deleted member 4994]

Was the LVB SoC 95% or the HVB? Usually that message means the LVB is too low for the update to complete. Ironically I think the update that is trying to install is the one that fixes that problem!

No, the LVB was at 95%, I checked with Car Scanner (the HVB was at 98%).

 

[Deleted member 4994]

Here's the list of everything to avoid failures:

Thread 'How To Get Failed OTAs To Install'

Someone can check your VIN why it failed, sometimes it's nothing you can do anything about.

Thanks, I have that thread saved. I haven't had the chance to try all of the different methods.

I'll see if someone can check my VIN.

 

[Deleted member 4994]

Got an answer from Mach-Lee

Failed due to poor battery data quality. This is covered on my failed OTA topic (see “BMS Poor Data Quality” section for instructions).

 

[Deleted member 4994]

Update:
All the tricks failed. Since the LVB was replaced at the end of April I decided that a BMS reset would be harmless enough and that did it.

n.b.: before doing the reset I checked some more data with Car Scanner and noticed that the LVB reset time was 380 days. That didn't make any sense: the original LVB was installed more than 3 years ago and the replacement less than 3 months ago. Obviously the dealer, when they replaced the battery, did not perform a BMS reset. That still leaves the mystery of the 380 days. I do recall bringing it in for a mandatory update last year (don't recall the exact date or reason), I guess they reset the BMS at that time. Did I mention that my dealer sucks ?

 

[Mach-Lee]

Update:
All the tricks failed. Since the LVB was replaced at the end of April I decided that a BMS reset would be harmless enough and that did it.

n.b.: before doing the reset I checked some more data with Car Scanner and noticed that the LVB reset time was 380 days. That didn't make any sense: the original LVB was installed more than 3 years ago and the replacement less than 3 months ago. Obviously the dealer, when they replaced the battery, did not perform a BMS reset. That still leaves the mystery of the 380 days. I do recall bringing it in for a mandatory update last year (don't recall the exact date or reason), I guess they reset the BMS at that time. Did I mention that my dealer sucks ?

Ah, that sort of makes sense. If the dealer reset the BMS to do an update but the battery wasn’t full, that could throw everything off and may have caused the 12V battery to have a reduced lifespan. But whenever the 12V battery is replaced the BMS must be reset, if they didn’t that can also cause problems. It does not have the adaptability to learn a new 12V battery unless it’s been reset properly, so the new battery probably confused it enough to cause the poor data flag. For some reason it sometimes is not able to learn the correct 12V SoC unless reset.

 

[rugedraw]

Update:
All the tricks failed. Since the LVB was replaced at the end of April I decided that a BMS reset would be harmless enough and that did it.

n.b.: before doing the reset I checked some more data with Car Scanner and noticed that the LVB reset time was 380 days. That didn't make any sense: the original LVB was installed more than 3 years ago and the replacement less than 3 months ago. Obviously the dealer, when they replaced the battery, did not perform a BMS reset. That still leaves the mystery of the 380 days. I do recall bringing it in for a mandatory update last year (don't recall the exact date or reason), I guess they reset the BMS at that time. Did I mention that my dealer sucks ?

Tech notes say they did, but if they did, they did not do it with FDRS. On my truck, there is a way to reset the BMS by putting in accessory mode, flashing high beams 5 times and tapping the brake 3 times. If these cars can have the BMS reset the same way, then maybe they did do it and that is why vehicle history does not show it. It's impossible to tell.

 

[Sikkun]

Tech notes say they did, but if they did, they did not do it with FDRS. On my truck, there is a way to reset the BMS by putting in accessory mode, flashing high beams 5 times and tapping the brake 3 times. If these cars can have the BMS reset the same way, then maybe they did do it and that is why vehicle history does not show it. It's impossible to tell.

I don’t remember 100% the procedure off the top of my head, but yes, Mach E can be reset doing something like what you just said.

 

[Deleted member 4994]

Tech notes say they did, but if they did, they did not do it with FDRS. On my truck, there is a way to reset the BMS by putting in accessory mode, flashing high beams 5 times and tapping the brake 3 times. If these cars can have the BMS reset the same way, then maybe they did do it and that is why vehicle history does not show it. It's impossible to tell.

That's exactly what I did: turn on in accessory mode (don't touch brake), flash 5 times, tap brake 3 times.

Sponsored