The Complete DIY Guide to Updating Your Mach-E with FDRS

[Mike G]

I've got the same updates for my Job 1 (along with the OBCC rollback that I haven't done yet). I'll do them all this afternoon and see what happens. Perhaps it's time for @Jimrpa to get excited?

That's what I'm thinking is going on. I suspect that the -ACR BCM update was in prep for the long-awaited frunk button but since I didn't get the GFM update to go along with it there was a mismatch that is causing the Frunk System Error message.

Hopefully I'll see the GFM pop up soon and this will all get sorted out.

Mike

Sponsored

 

[generaltso]

That's what I'm thinking is going on. I suspect that the -ACR BCM update was in prep for the long-awaited frunk button but since I didn't get the GFM update to go along with it there was a mismatch that is causing the Frunk System Error message.

Hopefully I'll see the GFM pop up soon and this will all get sorted out.

Mike

I wonder if your BCM already being updated has anything to do with the GFM not showing as available for your car? Maybe it's a package deal?

 

[Mike G]

I wonder if your BCM already being updated has anything to do with the GFM not showing as available for your car? Maybe it's a package deal?

Dunno. Take a look at what your before and after revisions on the BCM are. I wonder if you'll be getting the same -ACR that I have on mine now.

 

[Jimrpa]

I've got the same updates for my Job 1 (along with the OBCC rollback that I haven't done yet). I'll do them all this afternoon and see what happens. Perhaps it's time for @Jimrpa to get excited?

Actually, you just reminded me of something I was going to ask. Back when I had my escape, one of the features US escapes didn’t have was “Global open/Global close”, however European kugas DID have that feature. Escape “hackers” figured out that all you had to do was use some “magic software” to make a change in the BCM (Body Control Module) and presto, the US escape would have global open and close as well. As I recall, they were using FORScan, but the code with the BCM change came from a .ru website and everything only ran on PCs. I’m purely an Apple person and stay away from .ru stuff (unless someone like @DevSecOps tells me it’s safe and even then, I tend to be super cautious), so I sort of forgot about it.
Anyway, I went down that tale because I’m wondering if our Job 1 lack of a frunk release might actually be something as simple as a parameter change, not a code update? Perhaps there’s just a parameter sort of like “Enable Frunk Release” with a value of True/False in some module that has to be toggled using FDRS for job 1 cars?

 

[generaltso]

I’m wondering if our Job 1 lack of a frunk release might actually be something as simple as a parameter change

It's not.

 

[generaltso]

Well, this isn't off to a good start. After updating FDRS to 33.5.1, it hangs after doing the initial module scan. I can't even get to the point where I can apply the updates.

 

[ZuleMME]

Well, this isn't off to a good start. After updating FDRS to 33.5.1, it hangs after doing the initial module scan. I can't even get to the point where I can apply the updates.

It's always something. Reboot!

 

[WyldStallyn]

I wonder if your BCM already being updated has anything to do with the GFM not showing as available for your car? Maybe it's a package deal?

On Job 2, GFM is offered even with BCM installed.

 

[generaltso]

It's always something. Reboot!

I did reboot, but FDRS still hangs. I think I can get past it by not connecting to the car until after I'm at the update screen.

 

[Mike G]

I did reboot, but FDRS still hangs. I think I can get past it by not connecting to the car until after I'm at the update screen.

I did the FDRS update this morning (33.5.1) and checked my two VINs but on the Mach-E I didn't see the GFM. On a hunch that it needed a network scan to show up, I just connected and after a slightly longer than normal scan process it did indeed show that I needed the GFM updated. So I connected the PS and ran that.

My GFM was running the -AE version and has updated to the -BE version and the "Frunk System Error" message is now gone.

Note to Jim...there still is no Frunk button on my Job 1 as a result of these efforts.

But I am back to not having any errors once again and will likely receive total consciousness on my deathbed, so I've got that going for me, which is nice.

But still no Frunk button........

 

[cbcasas]

I did the FDRS update this morning (33.5.1) and checked my two VINs but on the Mach-E I didn't see the GFM. On a hunch that it needed a network scan to show up, I just connected and after a slightly longer than normal scan process it did indeed show that I needed the GFM updated. So I connected the PS and ran that.

My GFM was running the -AE version and has updated to the -BE version and the "Frunk System Error" message is now gone.

Note to Jim...there still is no Frunk button on my Job 1 as a result of these efforts.

But I am back to not having any errors once again and will likely receive total consciousness on my deathbed, so I've got that going for me, which is nice.

But still no Frunk button........

How do you initiate a network scan?

 

[Mike G]

How do you initiate a network scan?

When you connect to the car with the Mongoose it will do that automagically.

I started off this morning without the laptop connected to the car. And the GFM update wasn't showing up. So I took the laptop down and connected to the car and it ran the network scan and the GFM showed up.

If it's not showing up for you without being connected, go connect to your car and it's probably there.

There's also a "Rerun Network Test" button that will initiate a scan manually.

Mike

 

[generaltso]

I finally got it to work by not connecting to the car until after the point it was hanging. Still not sure what's up with that. Here's what happened with my module versions:

BCM - MU5T-14C184-ACM -> MU5T-14C184-ACR
GFM - LJ8B-14H121-AE -> LJ8B-14H121-BE
OBCC - LJ98-14G684-AN -> LJ98-14G684-AM

Although there's still no Frunk button, this update did enable the servo that electronically pops the frunk. It's now audible when you press the emergency release button inside the frunk.

 

[cbcasas]

When you connect to the car with the Mongoose it will do that automagically.

I started off this morning without the laptop connected to the car. And the GFM update wasn't showing up. So I took the laptop down and connected to the car and it ran the network scan and the GFM showed up.

If it's not showing up for you without being connected, go connect to your car and it's probably there.

Mike

Thanks. Going to try updating mine too. Car runs fine with the frunk service message but annoying nonetheless.

 

[WyldStallyn]

I finally got it to work by not connecting to the car until after the point it was hanging. Still not sure what's up with that. Here's what happened with my module versions:

BCM - MU5T-14C184-ACM -> MU5T-14C184-ACR
GFM - LJ8B-14H121-AE -> LJ8B-14H121-BE
OBCC - LJ98-14G684-AN -> LJ98-14G684-AM

Although there's still no Frunk button, this update did enable the servo that electronically pops the frunk. It's now audible when you press the emergency release button inside the frunk.

They're just building suspense. The update plan is:

1. Frunk error
2. Inoperable frunk button
3. Frunk button does partial release followed by manual single pull
4. Frunk button fully functional just so you can realize you are still just going to use the manual release 99% of the time just like Job 2 owners

Looks like they added a step between 1 and 2 ... Enable frunk release servos.

Progress.

Sponsored