PaaK issues possible resolution with update. All trims / models.

[DevSecOps]

My PaaK performance has been pretty solid. I'm wondering if I would see significant improvement with an RFA update. I have a Job 2 build date, but I have only had the PCM and its associated modules flashed at the dealer.

The last RFA update from a month/2 ago was a solid update that resolved many issues, and was the reason for the thread originally. I think that it's safe to stay on that version.

There are a few issues that I've been tracking that might be PaaK related that I haven't really talked about on here. One of them I just raised in the thread about the trunk opening on it's own. Another is a strange phenomenon whereas the car recognizes your presence however the antennas used for location of the phone aren't calibrated/working correctly. I'm hoping that those issues might be resolved in the new RFA module update.

So far my PaaK experience seems to be as good, if not slightly better, than it was prior to the update, but since it's just been a few hours I don't want to jump to any conclusions.

Sponsored

 

[BMT1071]

The last RFA update from a month/2 ago was a solid update that resolved many issues, and was the reason for the thread originally. I think that it's safe to stay on that version.

There are a few issues that I've been tracking that might be PaaK related that I haven't really talked about on here. One of them I just raised in the thread about the trunk opening on it's own. Another is a strange phenomenon whereas the car recognizes your presence however the antennas used for location of the phone aren't calibrated/working correctly. I'm hoping that those issues might be resolved in the new RFA module update.

So far my PaaK experience seems to be as good, if not slightly better, than it was prior to the update, but since it's just been a few hours I don't want to jump to any conclusions.

Does FDRS show you all previous versions of module software or just current and available? Curious as to where my RFA software is in the progression.

 

[DevSecOps]

Does FDRS show you all previous versions of module software or just current and available? Curious as to where my RFA software is in the progression.

Prior version: LJ9C-14G627-AC
New version: LJ9C-14G627-AD

 

[alexgorod]

Prior version: LJ9C-14G627-AC
New version: LJ9C-14G627-AD

Where do you see it?

 

[DevSecOps]

Where do you see it?

The easiest way to tell is by going into c:\ProgramData\Ford Motor Company\FDRS\fdrs\data\vehicle_software

There you can see the previous and current installed software versions. Date stamp is your friend here.

You can also see this in the history of the module update under the app author log. It's a bit more work to find it there because it will reference other modules that need to be updated as well. In my case, with this update, there's 4 modules that must be updated with the RFA update, but my vehicle already had those, so they are skipped. If you compare the start of the log with the end you can see that the only change was the file I originally noted, which was the RFA module.

2021-11-27T13:07:41,958 INFO class G2259168.G2259168.authorLogs - ENTERING GetVehicleNodeInfo

2021-11-27T13:07:41,961 INFO class G2259168.G2259168.authorLogs - node count    0

2021-11-27T13:07:41,962 INFO class G2259168.G2259168.authorLogs - node address    731

2021-11-27T13:07:41,963 INFO class G2259168.G2259168.authorLogs - GIVIS CDL DID  DE00 = 0A74228503201000

2021-11-27T13:07:41,964 INFO class G2259168.G2259168.authorLogs - GIVIS CDL DID  F10A = LJ9C-14G627-AC

2021-11-27T13:28:51,391 INFO class G2259168.G2259168.authorLogs - ENTERING SetPartNumDids

2021-11-27T13:28:51,399 INFO class G2259168.G2259168.authorLogs - After  F10A  set part number   LJ9C-14G627-AD

 

[alexgorod]

The easiest way to tell is by going into c:\ProgramData\Ford Motor Company\FDRS\fdrs\data\vehicle_software

But how?? Sorry if it's common knowledge, but I was kept out of it.

P.S. This?

 

[DevSecOps]

But how?? Sorry if it's common knowledge, but I was kept out of it.

Ok so I assumed you have FDRS ... maybe you don't?

You have to have software that provides the ability to connect to the car via the software and the OBDII adapter. This is normally only found at the dealership, however there's a couple of us crazy folk that have paid too much money to be able to do it at home ourselves. Basically we have the same tools as the dealer to perform updates and diagnostic troubleshooting.

 

[alexgorod]

I assumed

Assumptions are the developers' best friends!

 

[Skip Towne]

This is only done when you first setup your vehicle. Since you've already done it, you would have to do a master reset of your car and start over.

FWIW, I tried the Master Reset. I removed the car from my account . I removed the car from the FP app. I deleted the FP app from my Android phone. I twirled 3 times while patting my head and rubbing my tummy. I added the car back to my account, reloadeded fordPass, created new user profiles and....no luck. I was just an hour closer to dead with nothing to show for it

 

[DevSecOps]

FWIW, I tried the Master Reset. I removed the car from my account . I removed the car from the FP app. I deleted the FP app from my Android phone. I twirled 3 times while patting my head and rubbing my tummy. I added the car back to my account, reloadeded fordPass, created new user profiles and....no luck. I was just an hour closer to dead with nothing to show for it

Send me your VIN via DM and I'll check if your modules are outdated.

 

[benk016]

FWIW, I tried the Master Reset. I removed the car from my account . I removed the car from the FP app. I deleted the FP app from my Android phone. I twirled 3 times while patting my head and rubbing my tummy. I added the car back to my account, reloadeded fordPass, created new user profiles and....no luck. I was just an hour closer to dead with nothing to show for it

There might be another step of deleting the profile from your account as well.
When I added my GT to my account, it started giving me the option to setup the profile again. And clicking it gave me the option of which car I wanted to set it up for. The Old car already had one, and it gave me the option to delete it and start a new one.

Unfortunately, I'm not seeing how to get back to that now that I just have one car again.

 

[NeonMustang]

Dealer replaced BCM after an update. PAAK stopped working since then- tried resetting PAAK, tried with different phones, etc. It shows I have PAAK in FP, prompts to setup backup passcode, then error stating " cannot connect due to a system error" . Cannot lock/unlock/start. @DevSecOps mentioned there are multiple modules in the PAAK chain, could it be I need the BCM update that is part of the PaaK chain ? Thanks

 

[DevSecOps]

Dealer replaced BCM after an update. PAAK stopped working since then- tried resetting PAAK, tried with different phones, etc. It shows I have PAAK in FP, prompts to setup backup passcode, then error stating " cannot connect due to a system error" . Cannot lock/unlock/start. @DevSecOps mentioned there are multiple modules in the PAAK chain, could it be I need the BCM update that is part of the PaaK chain ? Thanks

Yes the BCM is part of the PaaK chain. Since this was caused by the dealer replacing the BCM there's probably little help that we could offer here. My suggestion would be to contact Ford and get a case started. They will put pressure on the dealer to get it resolved.

Sponsored