Search results

Yeah the order's status still says May shipment...in production. My order # is past 7900.

Same here just arrived today. The shipment email I got from Ford last week included a dead link to FedEx's website with no tracking number. The order status still says estimated to ship in May. ...now if I only had my car out of the shop I could test the new adapter! :D

Ouch that damn heat!! I'll see if I can get it replaced, or do you think a BMS reset might help? Wonder if the 12v is covered by the extended warranty plan...

Thanks. Here's the VIN: 3FMTK4SE8MME03150. Appreciate the help

This issue is happening with me too for the 6.6.0 OTA update. 12v battery is at 90% currently and has failed again to install due to some other "process". I've been trying the different methods for a few weeks now. FDRS isn't showing me any updates to do manually. Can anyone see if something...

I did your experiment again today before going on a trip...changed the update time by adding 2 additional minutes compared to the previous setting, and got this OTA today...Ford Power-Up 6.3.0. Either Ford is pushing a lot of OTA updates back to back, or your trick really works!! ...Or at least...

Tried your trick yesterday before starting an hour drive to visit family, and it seemed to work for me! After doing a DC fast charge, I got this notification on my screen that it updated to 6.2.1. Thanks for the heads up. I normally do my own updates in FDRS but it was nice to have this one OTA.

Same with mine. It happened after the 4.2.4 Power-up update and also disabled PAAK from working. It's really frustrating constantly having bugs and settings changed after each update.

Oh no!! So sorry that happened. Same thing happened to my first Mach E two years ago Halloween. Insurance ended up totaling it because they could make more selling the parts/salvaging the car rather than getting it fixed. Hope this is a quick process for you and sorry that happened again. Glad...

You can download the Android Auto beta .apk file from the Apk Mirror website. That's how I upgraded mine to take a peak at the new beta update.

OK thanks Mike. Wonder what is changed/improved since the recall? I only noticed after the recall update that DCFC seemed to be a lot slower compared to before. And after 80% I would still get 70-90 charging rates up to 90% but after the update it seemed to peak at 45 after 80% and at 90% drop...

Would someone be willing to run my VIN for me? Updated about a month ago and several battery related warnings in the Fordpass app keep popping up. Never receive any OTA updates either since owning the car. VIN: 3FMTK4SE8MME03150 Thanks a bunch

Not sure if anyone has posted this but after the updates, my MME GT at DCFC EA stations seems to only charge at 79kW max, even when I started charging at 5%. Could outside temps play a role in max charging with the new update? Prior I got well over 125kW charging speed on a 250kW station before...

Yeah no issues with the car and no warnings. Saw the ABS DTC and reset and cleared it, but the IPMA DTC still showed. If the IPMA DTC was easy enough to update and clear, I would try that but wasn't sure if it was.

Thanks for the info too. I appreciate it :)

Ah ok cool. I downgraded the laptop to Windows 10 and tried again today and saw the GWM module no longer had the SW update showing up in the list, however now I have a DTCs related to the IPMA: DTCs B1578:78 and see there is a TSB 22-2109 for it. You think that one is an easy update I can do to...

haha! Sorry for the long error log post lmao. I'm using the Mongoose-Plus Ford cable.

Here's the error log from FDRS I'm getting. Tried the update again last night: [SYSTEM] {"fdrsVersion":"31.6.7","fdspServerURL":"https://www.fdspcl.dealerconnection.com"} 2022-05-10T20:16:45,449 INFO class G2132531.G2132531.authorLogs - LOG>> (HEX) Read from module AFTER config write DE11 =...

Yeah doing those steps exactly. First GWM update had 14/14 updates and then cleared. Went back to SWUpdate and stated another GWM and this time it process 2/2. Yes go back to FDRS after USB removal and it completes a process, but looking into the log it shows error communicating to DID (whatever...

Ah just checked it says ERROR G2132531.G2132531 - Error in application. Cannot read DID: DE37 Another error in the log says no response for DID F162