Post here if you have an active FDRS account and are willing to look up info for others

[Mike G]

They have a receptionist answer the phone to schedule service appointments and I told her what was going on but she didn't seem to know anything.

When you say pump are you talking about the oil pump? I remember seeing a video from Munro Live where they tore down the rear MachE motor and they basically had to take apart the whole motor just to get to the oil pump. Wondering if they will just replace the rear motor?

Yup that’s that pump alright.

Sponsored

 

[B177y]

Did my first FDRS update yesterday and had a "java.lang.NullPointerException" error on my final module, the ACM. That post is here:

https://www.macheforum.com/site/thr...fdrs-alternative-to-forscan.10217/post-839335

I tried clearing the FDRS cache as suggested and reloaded my MME and the update in FDRS. Today I got this warning for the BECM:

"A GVMS Warning exists which may result in FDRS not offering necessary apps. To remove the warning associated with the module you are working on, select the module to open a case. Status an be viewed on PTS page "As-Built Assistance Request Status""

As I'm an FDRS noob, asking for any help or guidance for what this BECM error is. I also got the same Java error when I tried the ACM update again.

Everything seems to work fine and no DTC in car or FDRS that I can see.

3FMTK2SU2PMA65714

Thank you!

 

[Mike G]

Would someone please check my VIN to see if I have open updates? Trying to decide if I should purchase a two-day license. Thanks in advance I as always appreciate your help! 3FMTK4SE2MME00387.

Here's your list:

 

[Cjpayne]

Thanks Mike! Looks like part of my Saturday is booked! I appreciate your support!

 

[Mike G]

Update: Spent the weekend with FDRS firstly on the 2024 Lincoln Corsair GT as only six module line item updates, before the 2022 Mach-E GT P which had twenty-two line item updates...plus..Wife didn't want me learning on her Mach-E first!
Before each update, cleared the DTCs. All went ok, expect the CMR update on both vehicles, the "F118" CMR module didn't move from completion to next module "F120". Progress bar looping from 0 to 100%, then back to 0%, Mongoose adapter red light just occasionally blinking too when this looping occurs. I had to abort (heart in my mouth...) after I gave it 15-20mins of looping on each vehicle. When started CMR update again, F118 flashed up as OK, then FDRS immediately onwards to next module F120, though to successful completion of the CMR update. All tests passed when complete.

Was disappointed on the 2022 Mach-E to still be on BlueCruise 1.0, was hoping for 1.2, even 1.3 level.

@Mikeg Mike, after your intial analysis, does everything look ok to you? 5LMTJ5DZ5RUL06383 & 3FMTK4SXXNMA47660 Thanks.

Your Lincoln now has a cruise control module update available. It might have popped up after the server figured out you'd done everything else. That happens. I will hit the "Re-run Network Scan" button a couple of times when my list is empty, just to make sure there's nothing else before I disconnect.

Your MME has no available updates.

 

[Mike G]

Hi, can someone look up if my car has pulled down the update that is responsible for 2023's being unable to unlock? I also read that ECG-24.2.4.10.2 is supposed to fix that, is my car queued up to get that update? Vin is 3FMTK3S53PMB00260. Thanks!

Looks like you just got BC 1.3 on the 19th.

You do have the new gateway that's supposed to address the vehicle lockout issue in your available list in FDRS. But it's not yet queued as an OTA for your car.

 

[Mike G]

Could anyone check updates for 3FMTK4SX1NMA24199 ?

Thanks in advance.

 

[Mike G]

Could anyone check updates for 3FMTK4SE2PMA44592 please?

Thanks in advance.

 

[Mike G]

Did my first FDRS update yesterday and had a "java.lang.NullPointerException" error on my final module, the ACM. That post is here:

https://www.macheforum.com/site/thr...fdrs-alternative-to-forscan.10217/post-839335

I tried clearing the FDRS cache as suggested and reloaded my MME and the update in FDRS. Today I got this warning for the BECM:

"A GVMS Warning exists which may result in FDRS not offering necessary apps. To remove the warning associated with the module you are working on, select the module to open a case. Status an be viewed on PTS page "As-Built Assistance Request Status""

View attachment 131515

As I'm an FDRS noob, asking for any help or guidance for what this BECM error is. I also got the same Java error when I tried the ACM update again.

Everything seems to work fine and no DTC in car or FDRS that I can see.

3FMTK2SU2PMA65714

Thank you!

The BECM is the module responsible for monitoring your battery cells and ensuring they are balanced. It is a powertrain module. Most, if not all, 23.5 MMEs are showing a GVMS error for that module right now. Ford doesn't want techs trying to update that module until they put out revised software to address whatever the concern is that is involved with that module right now. Don't worry about it. At least it's not as bad as all the '22 and '23 Lightnings right now where every single powertrain module those trucks have has an associated GVMS warning, and has had for three months, while we're all waiting for a promised solution.

 

[B177y]

The BECM is the module responsible for monitoring your battery cells and ensuring they are balanced. It is a powertrain module. Most, if not all, 23.5 MMEs are showing a GVMS error for that module right now. Ford doesn't want techs trying to update that module until they put out revised software to address whatever the concern is that is involved with that module right now. Don't worry about it. At least it's not as bad as all the '22 and '23 Lightnings right now where every single powertrain module those trucks have has an associated GVMS warning, and has had for three months, while we're all waiting for a promised solution.

Thank you for that explanation! Calms my nerves.

My license expires tonight, so I'll fiddle around a little more and work on the ACM update and see if I can get that to go.

 

[oostertoaster]

Looks like you just got BC 1.3 on the 19th.

You do have the new gateway that's supposed to address the vehicle lockout issue in your available list in FDRS. But it's not yet queued as an OTA for your car.

Any idea how long it takes to get queued up as an OTA update? Or am I better off buying the cable and FDRS subscription to program it myself?

 

[Mike G]

Any idea how long it takes to get queued up as an OTA update? Or am I better off buying the cable and FDRS subscription to program it myself?

Nobody has any idea how long a given OTA will take to drop from the cloud.

I started doing updates back in March of '22 precisely because I wanted the BC 1.0 I'd paid for nine months earlier on my '21 MME and F-150 Powerboost. Been doing my own ever since. If that helps.

 

[grein002]

I just purchased extended warranty through Grainger - does that warranty show up in PTS or FDRS? If so, could someone check 3FMTK4SX9PMA25197 to see if it is showing up?

 

[Mike G]

I just purchased extended warranty through Grainger - does that warranty show up in PTS or FDRS? If so, could someone check 3FMTK4SX9PMA25197 to see if it is showing up?

Signed effective 22 Aug 24 at 4108 miles. Does that sound right?

 

[grein002]

Signed effective 22 Aug 24 at 4108 miles. Does that sound right?

Yes, should be premium 10yr/100K miles, $0 deductible, with lighting coverage

Sponsored