SSM 51571 - Phone As A Key Inoperative After An OTA Update

[Mach-Lee]

SSM 51571 2021-2023 Mustang Mach-E - Phone As A Key Inoperative After An OTA Update With Loss Of Communication With The RFA

Some 2021-2023 Mustang Mach-E vehicles may experience loss of phone as a key after an over the air (OTA) update. There may also be diagnostic trouble code (DTC) U0214 stored various modules for loss of communication with the remote function actuator (RFA) module. This may be due to software in the RFA module causing it be locked/stuck in programming mode. To restore phone as a key functionality for the customer and RFA communication, remove RFA fuse (F18/19) located in the body control module (BCM) for one minute and plug it back in. Reprogram the RFA module using the latest software level of the Ford Diagnosis and Repair System (FDRS). For claiming, use causal part 14G617 and applicable labor operations in Section 10 of the Service Labor Time Standards (SLTS) Manual.

---End SSM---

A RFA update was just released that I assume fixes the issue of the RFA staying in programming mode after OTAs. Getting that done may also improve the reliability of PAAK.

Sponsored

 

[GreaseMonkey]

This happened to me yesterday. I drove 20 miles and when I got to my destination (even before turning the vehicle off) it started indicating No Key Found and was unresponsive. I had to turn it off, get out of the vehicle, close FordPass completely and reopen it. I had to go through a couple of cycles of opening and closing the vehicle via FordPass before the issue went away. I’m also running into occasional slow response before the vehicle detects my phone and allow me to open the door.

 

[rkmoray]

I know this is a little off topic, but it does have to do with the phone as a key. Why would anyone want to use the phone as a key. I always need a key with me when I leave the house so I can lock the front door when I leave and unlock it when I get home. Therefore I always need a key with me.

 

[generaltso]

I know this is a little off topic, but it does have to do with the phone as a key. Why would anyone want to use the phone as a key. I always need a key with me when I leave the house so I can lock the front door when I leave and unlock it when I get home. Therefore I always need a key with me.

Not everyone uses a physical key for their house.......or anything.

 

[Logal727]

Not everyone uses a physical key for their house.......or anything.

Exactly, I haven't used a key for my house in 5 years, mostly because I go through my garage but also because I put a Schlage smart lock on the front door 5 years ago and it's still kicking

 

[Neil4Real]

So when doing this ourselves, we should still pull the fuse for the RFA before updating it in FDRS?

 

[generaltso]

So when doing this ourselves, we should still pull the fuse for the RFA before updating it in FDRS?

No need to unless it's stuck in programming mode.

I just updated mine. Took about 25 minutes.

 

[Neil4Real]

No need to unless it's stuck in programming mode.

I just updated mine. Took about 25 minutes.

How do I know if it is stuck though? Would it now allow me to update it when I try?

 

[generaltso]

How do I know if it is stuck though? Would it now allow me to update it when I try?

PaaK would be inoperative if it was stuck.

 

[AhardFSU]

Exactly, I haven't used a key for my house in 5 years, mostly because I go through my garage but also because I put a Schlage smart lock on the front door 5 years ago and it's still kicking

Same here. I haven’t used a key for my home on 10 bc I have z wave locks on the front door and garage entry door.

 

[stmache]

After I lost PAAK after the last series of OTA updates. I kept trying to get it back. The app would talk to Ford's servers but the car refused to give me a Bluetooth Pass Code so I could not finish the setup.

Nice to see Ford putting out a fix but, since I don't have access to FDRS, I will have to make a dealer visit and pray they don't screw it up (again).

 

[astrorob]

this is interesting - i couldn't set up PAAK on the day i took delivery. would always get stuck after giving me the pairing code to copy/paste.

the dealer thought it was the TCU, probably because the TCU doesn't seem to appear on the CAN bus via the OBD2 port - i see this also with CarScanner. but the TCU does seem to work (sometimes) as i have all the connected service stuff (but it comes and goes from start to start)

at some point i pulled the fuses for the TCU and the RFA and after that i was able to set up PAAK. it seems to work OK but i've had a few "key not detected" events and also had to enter my backup start passcode twice. since that time i started carrying the key fob again.

maybe it's unrelated because the car was like this from the start, and nothing bad apparently happened after the two OTA updates i got. my wife continues to use PAAK and it is apparently working OK for her.

 

[EasyPass]

I know this is a little off topic, but it does have to do with the phone as a key. Why would anyone want to use the phone as a key. I always need a key with me when I leave the house so I can lock the front door when I leave and unlock it when I get home. Therefore I always need a key with me.

I use PaaK strictly as a convenience, like when I go to the garage to get something out of the car, or pull it out to give it a wash. I always have my phone, but not always my key in those cases. As for relying on PaaK 100% for vehicle access, there are too many potential points of failure to solely rely on it alone. I've had phones terminally die in my hand while using it, for example.

I do appreciate the ability, however, to have a few methods to enter and start/operate the vehicle; i.e. fob, phone, door sill code/console code.

 

[Polar]

After I lost PAAK after the last series of OTA updates. I kept trying to get it back. The app would talk to Ford's servers but the car refused to give me a Bluetooth Pass Code so I could not finish the setup.

Nice to see Ford putting out a fix but, since I don't have access to FDRS, I will have to make a dealer visit and pray they don't screw it up (again).

I had the exact same experience- my dealer finally resolved it at the beginning of April. *But mine was dealer applied update caused.


Thread with info and my resolution details.

 

[dtbaker61]

SSM 51571 2021-2023 Mustang Mach-E - Phone As A Key Inoperative After An OTA Update With Loss Of Communication With The RFA

Some 2021-2023 Mustang Mach-E vehicles may experience loss of phone as a key after an over the air (OTA) update. There may also be diagnostic trouble code (DTC) U0214 stored various modules for loss of communication with the remote function actuator (RFA) module. This may be due to software in the RFA module causing it be locked/stuck in programming mode. To restore phone as a key functionality for the customer and RFA communication, remove RFA fuse (F18/19) located in the body control module (BCM) for one minute and plug it back in. Reprogram the RFA module using the latest software level of the Ford Diagnosis and Repair System (FDRS). For claiming, use causal part 14G617 and applicable labor operations in Section 10 of the Service Labor Time Standards (SLTS) Manual.

---End SSM---

A RFA update was just released that I assume fixes the issue of the RFA staying in programming mode after OTAs. Getting that done may also improve the reliability of PAAK.

very interesting......

I'm wondering if this had anything to do with a temporary SVS alert I got yesterday? I checked DTC, and just about every module 'lost communication' and threw related codes. Two hours later, wrench and SVS cleared itself.

The disturbing thing is that I've had auto-updates DISABLED for months.

I think there are still updates being pushed thru whether we ask for them or not ?!

Sponsored