Search results

All you have is an ACM update in your list right now.

So my ancient Craftsman table saw actually pulled fewer amps when it was configured for 220V than 110V (just change the jumpers around on the motor). I wanna say it was around 11-15 amps? With that said. You only need a 60amp circuit to power a 48amp EVSE (like the Wallbox Plus). Remember, the...

Weirdness with your truck. It's not pulling up any connected vehicle info at all. No OTA history. No VHA history. Assuming you haven't turned off connected vehicle toggles in Sync: I recommend you go out and disconnect the 12V battery for a couple of minutes and then reconnect to see if that...

23B50 has now been updated to include Lightnings' built October 14, 2021 through February 1, 2023. Some people on the MME forum who had never had this performed (it's a powertrain update) or gotten it by an OTA saw this CSP get dropped off their list of FSAs. So now it's been expanded a bit...

Well, I don't know if it sounds right or not. I can tell you that another member here asked me to check his VIN yesterday afternoon because he just got his truck back after the dealer was going to do everything on his available list. And his VIN still shows the ACM and RFA as still available (no...

They’re not aware of it because it doesn’t apply to dealer techs. Dealer techs are granted permissions in the FMC dealer system to be able to do PATS functions. They don’t need a NASTF login. That’s just for independent shops like locksmiths.

Switzerland as well right?

I have -CS. But remember, this is the RFA (along with the ACM) that won't clear from FDRS when you try to update it. So I'm not entirely sure whether this update was successful or not.

So you're saying this representation on the Build and Buy for a 2024 Lariat is not accurate, then?

4 Nov, and there's an interesting blurb in the supplemental update (#1) for FSA 24B56 (the Front sensors/IPMA update). Ford is recommending the use of a VCM 3 for this procedure because it apparently has the ability to handle large file sizes better than the VCM 2 (which is Mongoose...

Absolutely. Marketing miss is an understatement. Not offering Lightning Blue at least on the first year as a launch option (like First Edition MMEs) was a big mistake I think. My 3 previous F-150s had been some variation of that color. I really miss it. But things now are so much worse...

Was checking out the 'Build and Buy' this morning and noticed that the gallery photos showed a Rapid Red Lightning, but the Lariat Build and Buy only shows this color selection: So you can get two different 'whites', a silver, a black, and a blue that is so dark that it might as well be black...

They will, and likely get paid for it as well.

Everybody can call their dealer's service advisor and ask them to pull up your VIN and tell you what open FSAs you have. It's right there on the main PTS 'Vehicle ID' screen.

When you update your truck with FDRS it doesn't 'sign off' the FSA in Ford's system. I still have the IPMA and the FHCM FSAs open in the system, but I did the updates myself (a while ago).

It seems to happen more when I'm using my phone rather than when using the computer.

It was the ECG (GWM) update that fixed it.

I log on something like 0530 most mornings. By roughly 1630 my cached credentials are timed out. So if I happen to be actually out working on either the car or the truck when that happens...and I'm in the middle of doing some update...I will get the continual login screen repeats until I...

And yesterday FDRS 42.5.6 was released. So no more spamming the 're-run network test' to see if new updates show up I guess. Also since this is a major (41. to 42.) update remember to tick the box for 'remove user settings' during setup so you don't end up with weird results. They may have...

What he's experiencing is what happens if you've logged on to FDRS and you're actually still logged on and working when your daily login timeout expires. When this happens (at least with 41.5.6) you will have to completely close FDRS. Wait about 30 seconds and then reopen the program and log...