OTA Power Up 2.3.0 Is out

[Texas-E]

I need to catch up on this thread, so my apologies if it has been discussed and I've not seen it yet.

I have a couple of observations that might be unrelated, but I think they are interesting. My Mach-E is a commuter vehicle for me, and I've worked at home since the start of the new year. I've driven it some, but not a lot.

I've checked often to see if I was queued for the update and happened to pull it out of the garage yesterday for an extended period of time. Within 1 hour of pulling it outside (good cell coverage), I checked and saw that I was queued for 2.3.0. Most likely unrelated, but I thought it was interesting.

The second part is that I monitor my LVB with an ANCEL BT500 Battery Tester and just saw that I was at 12.15V an hour ago (I'm running a dashcam, and I keep an eye on it). I started the car, and the display showed that the update failed. I'm speculating (and it might have been covered before) that the LVB voltage might be a trigger to abort the update. It seems logical, and if someone is having trouble with an update, it might be something to consider. I turned my dashcam off and topped my LVB to see if anything interesting happens. Of course, it could have failed for any number of reasons, and it could be successful the next time for some entirely different reason.

Nothing earth-shattering with what I've seen, but I thought I'd share it.

Sponsored

 

[Sneezy]

2.3.0 is a freaking train wreck. It decided to install while we were at our gun club and when my daughter got in to drive, the screen rebooted 3 times while driving home. I would expect the vehicle to know when I'm home and plugged in, not do it while I'm in public not plugged in.

It doesn't know me when I am the only one getting in the car. I have to tell it my profile even though the profile is assigned to me.

The screen decided to change profiles while I was driving and put me in guest mode.

WTF FORD??? My patience is running low with the bugs. I just don't get why they can't fix the profiles instead of giving us GAMES we didn't ask for.

Side note, I write custom computer software for a living. I have earned my bitch about it badge and wear it proudly!

 

[Neil4Real]

2.3.0 is a freaking train wreck. It decided to install while we were at our gun club and when my daughter got in to drive, the screen rebooted 3 times while driving home. I would expect the vehicle to know when I'm home and plugged in, not do it while I'm in public not plugged in.

It doesn't know me when I am the only one getting in the car. I have to tell it my profile even though the profile is assigned to me.

The screen decided to change profiles while I was driving and put me in guest mode.

WTF FORD??? My patience is running low with the bugs. I just don't get why they can't fix the profiles instead of giving us GAMES we didn't ask for.

Side note, I write custom computer software for a living. I have earned my bitch about it badge and wear it proudly!

Well, that's a large part of 2.3.0... it'll now allow you to set an update schedule properly and also fetch updates for your car so you can install it when you know you aren't going to be needing it.

 

[Stang68]

The second part is that I monitor my LVB with an ANCEL BT500 Battery Tester and just saw that I was at 12.15V an hour ago (I'm running a dashcam, and I keep an eye on it). I started the car, and the display showed that the update failed. I'm speculating (and it might have been covered before) that the LVB voltage might be a trigger to abort the update. It seems logical, and if someone is having trouble with an update, it might be something to consider. I turned my dashcam off and topped my LVB to see if anything interesting happens. Of course, it could have failed for any number of reasons, and it could be successful the next time for some entirely different reason.

Nothing earth-shattering with what I've seen, but I thought I'd share it.

Interesting observation. I have a dash cam plugged into the OBD port of the car and I’m having trouble pulling down or at least installing this latest update. My widget app has been showing as installation requested for a while. Going to try unplugging the dash cam to see if that does anything.

 

[Logal727]

Something different I noticed after 2.3.0 is the screen would turn off as soon as I opened the door after vehicle turn off even if there was a message up there. Now, when the Check Occupants message comes up the screen doesn't turn off until I dismiss that message. I guess that makes sense, not a big deal at all, just an observation.

 

[VegStang]

The dealer installed module PAAK updates deleted my presets but not the 2.1 or previous OTA updates. I'm still waiting for the update gods to deem me worthy for the 2.3 update. Hoping the fact that some of the modules were not updated by the dealer like they should have will not negatively impact my chances.

 

[Dr Obnxs]

iSde note, I write custom computer software for a living. I have earned my bitch about it badge and wear it proudly!

Doesn't matter. Someone will tell you your past experience, even though they don't know what your past experience is, doesn't transfer to the technical marvels that is our Mach-E. Ask me how I know.

The OTA system is horribly designed and it's implimentarion is poor as well. I get my car back from service today and I hope most of the stuff is cleaned up, but I fear not.

I still really really like the vehicle and recommend it to anyone who asks. But I call it like I see it. It's too bad that the HMI/OTA combo is such a big touch point for the owner/vehicle relationship because it sure has an outsized impact on the whole experience.

 

[Dr Obnxs]

Interesting observation. I have a dash cam plugged into the OBD port of the car and I’m having trouble pulling down or at least installing this latest update. My widget app has been showing as installation requested for a while. Going to try unplugging the dash cam to see if that does anything.

I made automotive accessories that plugged into OBD ports. Some cars are very very sensitive to stuff plugged into the port. At least BMW was kind enough to use two of the non defined pins for an always on and a switched power 12 VDC supply. But don't be surprised if leaving stuff plugged in there has unforseen effects. Audis used to be the worst.

 

[Dr Obnxs]

So much for clear communication:

Still no idea what was installed. But at least the dealer seems to have made some progress.

 

[Stang68]

I made automotive accessories that plugged into OBD ports. Some cars are very very sensitive to stuff plugged into the port. At least BMW was kind enough to use two of the non defined pins for an always on and a switched power 12 VDC supply. But don't be surprised if leaving stuff plugged in there has unforseen effects. Audis used to be the worst.

Yeah, it's interesting that after I unplugged the camera from the OBD my widget OTA screen looked like this:

So clearly something happened when I unplugged the camera from OBD. The OTA info came back after a while, but still no dice on the install of 2.3.

 

[GrisGris]

Yeah, it's interesting that after I unplugged the camera from the OBD my widget OTA screen looked like this:

So clearly something happened when I unplugged the camera from OBD. The OTA info came back after a while, but still no dice on the install of 2.3.

I know we're all punching at shadows here, and that error may happen for numerous reasons, but, as it happens, that's the screen I got right before it then showed the failed 2.3 update.

 

[Logal727]

I know we're all punching at shadows here, and that error may happen for numerous reasons, but, as it happens, that's the screen I got right before it then showed the failed 2.3 update.

I got that today after checking it for the first time after successful install yesterday. I think it might be a server update thing.

 

[Dr Obnxs]

Yeah, it's interesting that after I unplugged the camera from the OBD my widget OTA screen looked like this:

So clearly something happened when I unplugged the camera from OBD. The OTA info came back after a while, but still no dice on the install of 2.3.

Auto manufacturers got lazy with the OBD port. They never imagined that people would actually use the data available at the interface, much less just an easy power hook up, and didn't buffer them properly.

Here's a stinker:. BMW actually puts a data out delay on the OBD line so it's impossible to use it for any serious state based option control like water injection or the like. Bastards!

But what do I know? My past experience means I don't know anything about automotive systems and engineering!



God, I'm gonna run with that one for a while!!!!

 

[GrumblesTheDog]

Doh! 2.3.0 update failed. Got the big message on the main screen, and also see a 'General Failure Will Retry' using the API trick. Oh well. 1.7.1 took a few tries but eventually worked.

 

[PeeKay]

Looks like that is the way to do it. Hoping that 3rd times the charm for me as well.
Or perhaps an intervention from @Ford Motor Company , will keep this thread updated.

3rd time was indeed the charm. WiFi client in the car was off, and I let it sit in the driveway. After a few hours it went through various states of pending, delivery, etc. Even while the update was being applied it went through different stages that were indicated by the "OTAM_..." value. Took a couple of hours.

Hopefully from now on, "On Demand" updates work, v/s waiting for approval at the server end.

Sponsored