Power-Up OTA 6.8.0 - Smart Changes: Center Screen

[TaxmanHog]

Have you tried to manually update using the update now option?

Yes, several times in various conditions, I'm really curious "WHAT" the process is that interrupts the install process and why it can't be told to us if there is something proactive we can do to inhibit said process.

Sponsored

 

[EdRudy]

That seems odd. I usually use update now because I’m impatient and never had anything interrupt the install. The only other thing I regularly do is disable the interior alarm.

 

[TaxmanHog]

That seems odd. I usually use update now because I’m impatient and never had anything interrupt the install. The only other thing I regularly do is disable the interior alarm.

I had the alarm system turned off already, but when I looked to verify, there is another switch under a drop down for the sensors, so I flipped that off too, ran the install now, and still failed due to interruption.....

I'm beginning to wonder if the truck's call the mothership, she fails to give a timely response to validate and continue the update process, seems only a few of us are running into this road block, most are getting through, my working theory is that as the deluge of requests subside, more of us will get through and the update will proceed to conclusion.

 

[jerock]

Can an OBD reader cause a problem with updates? I just pulled mine to be safe.

 

[Jim Lewis]

I'm really curious "WHAT" the process is that interrupts the install process and why it can't be told to us if there is something proactive we can do to inhibit said process.

I've had the failure notice "interrupted by another process quite a few times." I think it's always been insufficient LVB SOC because when I've checked, the LVB SOC is usually less than 80% when I get that notification, e.g., failed at 73% SOC. If you also get a failure alert in FordPass, it's usually more specific on update requirements. When I've charged the LVB up only as much as 80% or 82%, several updates have succeeded. I have a younger LVB than you and have driven a lot less - I forget whether you had the health of your LVB checked, clearly not the LVB SOC for you. I've protested the same as you that the failure notice should explain why. Shouldn't require rocket science to do that.

Can an OBD reader cause a problem with updates?

IIRC, I got 6.8 the other night with an OBDLink MX+ device plugged in. OTH, that adapter works by classic BT, not BT LE.

BTW, interesting reading ABRP's website. They mention that for many OBDII readers, leaving it plugged in is a security risk as a hacker can attack and unlock your vehicle through an insecure OBDII reader.

 

[jerock]

IIRC, I got 6.8 the other night with an OBDLink MX+ device plugged in. OTH, that adapter works by classic BT, not BT LE.

BTW, interesting reading ABRP's website. They mention that for many OBDII readers, leaving it plugged in is a security risk as a hacker can attack and unlock your vehicle through an insecure OBDII reader.
[/QUOTE]

I've received updates with mine plugged in, but wandered if the LVB was at a lower level if it might effect it. I have the Veepeak OBD II Scanner.
The possible security risks certainly motivates me not to leave it plugged in though.

 

[bmwhitetx]

Yes, several times in various conditions, I'm really curious "WHAT" the process is that interrupts the install process and why it can't be told to us if there is something proactive we can do to inhibit said process.

Right there with you. Manual updates, battery chargers, bench power supplies, blower charge method, slow charge method, BT off, key fob in Faraday bag - did them all over the last two weeks. All interrupted.

If you watch in manual mode you see the countdown from 120 to 0, then the "Preparing Updates", then the instrument panel turns on, then boom, screen says process interrupted. Every time @rugedraw or others looked for me it was low 12V SOC or 12V battery doesn't have capacity (despite being at 92%+ SOC).

But last night it installed. Go figure. 23-PU0110-RAD-PS failed 30 times before it worked. I let them know it in the 6.8.0 survey they sent me at 2:38 am this morning, 30 minutes after it installed at 2:00 am!

 

[TaxmanHog]

I've had the failure notice "interrupted by another process quite a few times." I think it's always been insufficient LVB SOC because when I've checked, the LVB SOC is usually less than 80% when I get that notification, e.g., failed at 73% SOC. If you also get a failure alert in FordPass, it's usually more specific on update requirements. When I've charged the LVB up only as much as 80% or 82%, several updates have succeeded. I have a younger LVB than you and have driven a lot less - I forget whether you had the health of your LVB checked, clearly not the LVB SOC for you. I've protested the same as you that the failure notice should explain why. Shouldn't require rocket science to do that.

The LVB was at 95% at the start of the manual update request, after three minutes it was at 93%
Tried it again, after second failure it was at 90%

Right now, a couple hours later it's 67% just sitting in the garage plugged in, doing nothing!!

I suspect the LVB isn't strong enough to retain much of a charge, it will go in for a test 12/26 when My light bar is installed.

 

[rugedraw]

Right there with you. Manual updates, battery chargers, bench power supplies, blower charge method, slow charge method, BT off, key fob in Faraday bag - did them all over the last two weeks. All interrupted.

If you watch in manual mode you see the countdown from 120 to 0, then the "Preparing Updates", then the instrument panel turns on, then boom, screen says process interrupted. Every time @rugedraw or others looked for me it was low 12V SOC or 12V battery doesn't have capacity (despite being at 92%+ SOC).

But last night it installed. Go figure. 23-PU0110-RAD-PS failed 30 times before it worked. I let them know it in the 6.8.0 survey they sent me at 2:38 am this morning, 30 minutes after it installed at 2:00 am!

It could be worse. You could have a defective vehicle with a problem impossible for dealers to diagnose like mine where it is incapable of getting an IPC update via traditional means forcing me to install them via CAN that takes 6 hours. It has been showing for me in FDRS for a week or so and they already tried sending it to me once. Look a little further down my OTA dashboard and you can see what happened the last time I was sent. Same thing happened two years ago with IPC OTA my truck needed to activate Bluecruise, so I'm used to it by now and can laugh at it.

 

[NCMike]

Received this update while eating lunch today. Installed without issue.

 

[carys98]

Downloaded today and failed install twice already. After the first try the 12V was at 76% so I left it on in the garage for 3 hours and it only got to 80%. I kicked it off again and it failed a second time. I’m thinking I need to keep it parked where it will be easy to tow.

 

[TaxmanHog]

Finally posted 6.8.0 this morning, SOC was pretty low 50's when I remote started the truck at 7:40, ran for 20 minutes which helped increase SOC, drove to breakfast location, but left the truck "idling with 30 minute countdown turned off, after breakfast head home and initiated the update, SOC was in the mid/upper 80's.

Truck was parked in the driveway, shut down cell phone, moved key fob out of reach.

Waited an hour before firing up my phone, blessed to see the following. Post install SOC is at 64%

 

[Its PJ Bia]

Got the 6.8 update last night and installed without issue. So happy to finally see the SOC on my dash screen and I can now use my big screen for viewing other things.

 

[TaxmanHog]

First drive after the update completed, 3 hours resting time, headed out on errands, IPC has the speed limit icon moved to left side of Speedo. No impact on my pre-existing dynamic SOC that I got last summer, 100% power was available from the battery to motors, the motor display showed traction & regeneration coming from front & rear set, TPMS straightened out to correct readings.

She appears to be running perfectly fine, looking forward to 6.13.0 in the next week or so.

 

[carys98]

The last two days I’ve been running the truck and driving around to get the 12V above 80%. After 4 failures it looks like @Ford Motor Company has pulled the update for me. I thought they were starting to get the OTA process under control but it’s still a shit show. I’m doing some more research into North Carolina’s lemon law.

Sponsored