Making this change in Forscan worked. Changed xxxx xxx* xx-- from "2" to "3".Interesting. If it's just a config thing, then it can be done with FORScan.
@ziptbm The key is somewhere here. Right now, you are showing a 2 there. Maybe try 3 for stretched? Make sure you reboot the APIM after making the change. If it works, you save $50. If it doesn't, you can just put it back to what it was.
I'm nearly in your boat. My dealer is going to "look into it" when I go in on Sept 9th for 30k service. After that, assuming nothing done, I'll be getting a mongoose. I'm still exploring power supply options myself. Also still on the 4.X software.
That's not a bad deal. I think I might just use the 20A that I ordered, and if I see it dropping too low, I'll hook up to my wife's car with jumper cables.
I think it's the IPM update that takes several hours and requires a beefier supply. It would be interesting to see if just updating a few jump starts the process again. We've somehow fallen through the safety net and Ford forgot we exist so running an update might put us back on the queue. I might ask the dealer just to push a single quick update if they don't find anything wrong.
Hey Mike, just wondering if Ford has kicked this can down the road yet?You, like the rest of us, are still waiting for a new gateway update to solve all of our powertrain problems. This is the one we've been waiting on since April or May?
That's why FSA 23B57 is still on hold, and that's why we don't have the new Sync (1122) like your Mach-E has now (because we need a gateway software update for that too)...and obviously we probably need the new gateway for BC 1.3 to get turned on.
We've got two weeks left in August at this point. Let's just hope they don't kick the can down the road again like they did back at the end of June.
Nothing's changed as of this morning.Hey Mike, just wondering if Ford has kicked this can down the road yet?
Just wondering as again now there is close to a week left in August. Thanks!
I will say the one recommended in the beginning post is very insufficient for module programming. If you have any long-running module programs, then this will not supply enough current to tide the overall draw and you will dip dangerously into a low voltage state. This is a perfect power supply for ICE vehicles which don't run battery coolant pumps during updates, but as it stands our Lightnings can draw nearly 60A current during a module program, which means that even if you had two of the above, you would still be at a deficit.
This is perfect!When you first start FDRS (with "Key on, Engine Off", AKA "accessory mode") you'll come to this screen. Before flipping over to see how many updates you have, first click the View CMDTCs button, and then when presented with the list, and after a brief review, just select the option to clear and retest. Do this before attempting any updates. Do this after doing an update to clear any errors resulting from FDRS telling other modules on the network to 'stop talking' while the previous update was getting programmed, and do this at the end after updating all modules to ensure you're leaving the vehicle in a 'clean green' state before disconnecting.
Doing a clear and retest between updating modules is particularly important because after FDRS says "Application Finished, click OK" and you're returned to the list of available updates, and you think you're ready to start the next one...the left side panel may be showing you all 'green' module tiles, when actually due to the intentional interruption of network communications many of those modules are actually in an error state (orange). So double-checking by doing a clear and retest before starting the next update will ensure you're once again starting off with a green board.
Sarcasm? ?Nothing's changed as of this morning.
But I'm sure they're doing their very best to fix this 4 month old problem by the end of this month.
