Power-up 6.2.0 déjà vu

[GatorJ_MME]

And I'm sure if you hook up to a car with FDRS or similar tool that you can see an md5 or other hash / checksum to see what is actually loaded for every module actually included in the package.

It is still a bad idea to release two versions of software that share the same version number even if it is just the customer facing one....

They have the third digit available to them, why not release it as 6.2.1?

Sponsored

 

[superdave80]

Ability to actually disable motion sensors at power down

I've received the (1st?) 6.2.0, and motion sensors still turn back on after the next power up. How can Ford software engineers be THIS bad at their job?

 

[Mach-Lee]

The image of the FordPass release notes does not include what this updates name is. It is 23-PU1103-NAT-VCE which would have shown in the vehicle release notes I believe.

Correct, it’s at the bottom. But I think people see the 6.2.0 mention first.

 

[DevSecOps]

I've received the (1st?) 6.2.0, and motion sensors still turn back on after the next power up. How can Ford software engineers be THIS bad at their job?

I think that was just for the temporary disablement which never worked. That was supposed to reset on power-up. I don't know that they ever intended on it being a permanent disablement.

 

[Mach-Lee]

I've received the (1st?) 6.2.0, and motion sensors still turn back on after the next power up. How can Ford software engineers be THIS bad at their job?

That’s how it’s supposed to work. Permanent disablement is not possible by design, must be done each time vehicle is parked.

 

[azerik]

I believe 6.2 is supposed to address:

Drive mode not available
Guest profile bugs
Phone call issues and static
Ability to actually disable motion sensors at power down

The real question is what new bugs will you now have?

Pretty sure I've had these issues patched a couple times this year. Maybe, just maybe they'll fix something this year. But I'm not going to hold my breath.

Yeah, this is a really bad idea from a configuration management standpoint.

Someone needs to update the current firmware poll to 6.2.0 (original release) and 6.2.0 (re-release 1)....

We really have to start doing a worse job at keeping track of these PowerUps. I have a feeling someone at Ford opens this site and looks at the top results for "power up" and uses that number for the release. Then C&P the release notes and add a line of gibberish at the bottom.

 

[rugedraw]

And I'm sure if you hook up to a car with FDRS or similar tool that you can see an md5 or other hash / checksum to see what is actually loaded for every module actually included in the package.

Which files get updated in the modules can be seen in PTS once the OTA trigger is created for the vehicle. It shows the location for the file within the module, and it also shows the current file name and what the new file name will be post-update.

 

[GatorJ_MME]

Looks like the specific update is referred to as 23-PU1103-NAT-VCE , which hopefully is unique.

 

[corradoborg]

'23 Premium here too, purchased in August. Three days ago I got 6.1.0 straight after being on 4.2.3, skipping over 5.x.x. I wouldn't be worried (although I was ). Hang tight, you'll probably get 6.2 before I do. Patience will prevail.

Another '23 Premium here, and almost exactly the same progression, except I got to 4.2.4 before skipping 5.x.x and going to 6.1.0.

 

[Okuma]

6.2.0 moves some UI controls around. The missing buttons may moved. The frunk & trunk are now on the screen you see as soon as you go into Settings (same screen where you can pick the drive mode). There's a graphic of the car ... the buttons are in the upper right corner of that image/graphic -- and with the background being dark, they are easy to miss.

Also, my first several attempts to do 6.2.0 also failed (Incomplete). Ultimately I discovered my 12v battery was at a 75% charge. I put it on a charger (a real charger ... not a trickle charger/maintainer) and left it overnight. The next day it successfully installed.

I do wish the car would more aggressively maintain the 12v battery power. It waits until the voltage is low enough to decide to charge it ... rather than just topping it off every time you drive or charge. Updates wont apply if the 12v is low. It wants to make sure it has a nice safe margin of batttery power to complete the update.

When I go to settings now, those buttons are not available at all, along with the drive mode options. They have literally disappeared. Ford has to redo my 6.2.0 for them to come back. I keep my '22 GT plugged in most of the time per manual but still no updates. I'll have to go to the dealer because for some reason, they can't push an OTA to me.

 

[azerik]

JubOnez are still stuck tho yeah? (Safety first!)

 

[macchiaz-o]

JubOnez are still stuck tho yeah? (Safety first!)

 

[Just Lurking]

I believe 6.2 is supposed to address:

Drive mode not available
Guest profile bugs
Phone call issues and static
Ability to actually disable motion sensors at power down

The real question is what new bugs will you now have?

That's a good list. I've experienced three of those bugs frequently, but not in a few weeks, so hopefully these fixes stick. I'm on 6.4.0 at this point (with the first 6.2.0 release, not the second.) Also haven't received either of the two recent priority updates.

'22 GT, not in EA program.

 

[Mirak]

That’s how it’s supposed to work. Permanent disablement is not possible by design, must be done each time vehicle is parked.

I know I’m preaching to the choir here, but that is stupid. It is also dumb software design. If @Ford Motor Company didn’t intend for us to be able to permanently turn off the sensors, then why did they bury a setting 5 or 6 taps deep into the menu to turn off the sensors? Did some fool actually think drivers would do that every time they turned off their car (probably yes, unfortunately).

Moreover, it was redundant. There was already an ability to turn off the sensors once, with one tap, upon exiting the vehicle. It didn’t work (maybe now it does?), but it was there.

So stupid software design, stupid nanny inability to turn this crap off. What is the reason? Safety? Ford lets us disable our rear occupant sensor for six months at a time, but we can’t do the same for the motion sensor?

This is something that might have warranted a mention during the latest love fest between Ford engineers and a few social media types. But as we all know, you can’t criticize Ford’s stupid decisions if you want to keep getting a seat at the table.

/rant

 

[Mach-Lee]

I know I’m preaching to the choir here, but that is stupid. It is also dumb software design. If @Ford Motor Company didn’t intend for us to be able to permanently turn off the sensors, then why did they bury a setting 5 or 6 taps deep into the menu to turn off the sensors? Did some fool actually think drivers would do that every time they turned off their car (probably yes, unfortunately).

Moreover, it was redundant. There was already an ability to turn off the sensors once, with one tap, upon exiting the vehicle. It didn’t work (maybe now it does?), but it was there.

So stupid software design, stupid nanny inability to turn this crap off. What is the reason? Safety? Ford lets us disable our rear occupant sensor for six months at a time, but we can’t do the same for the motion sensor?

This is something that might have warranted a mention during the latest love fest between Ford engineers and a few social media types. But as we all know, you can’t criticize Ford’s stupid decisions if you want to keep getting a seat at the table.

/rant

It’s driven by the demands of the insurance industry to reduce car thefts. Motion sensors shall not be disabled permanently. That’s how it works on every car that has motion sensors. It’s not a Ford decision. I guess you better make sure you don’t buy a car with motion sensors next time.

Security systems have to be certified to specific standards before they will qualify for insurance discounts.

Sponsored