ECU module programming guide using FDRS

[Kanuck]

Yep you are good to install it. I believe it only fixes the tailgate issue for non-power tailgates.

Thanks

Sponsored

 

[newdeal99]

what a nightmare. Started trying to get OTA fixed like 9 months ago. First dealer had it three times and no success (once was slightly before the TSB came out, twice after). Second dealer we waited a while and tried, no luck, they then had it back a couple times and still no luck, they then ordered a gateway module and ripped my truck apart to put it in and no luck, they damaged my passenger seat in the process and deny doing it (zipper on the upholstery popped open and is damaged so won't zip back up...yes they even removed the seats). Then they told me they need to order an APIM. I told them that they might be able to just update it because I got past the OTA myself y having a USB plugged in for a month and a bit. Clearly they didn't try because out of frustration I ordered the mongoose again and just yesterday spent 8 hours installing every single update that showed up to get me to the most recent version. My only question now is when will Ford recognize that my truck is updated so that blue cruise will activate? My app is still showing that the most recent update was 2.1.1 which was installed august 30th but my aim is way past that now and is up to date

 

[Mwathey515]

My understanding is that you ran the J2534 Toolbox diagnostics and the driver installation checked out ok but the diagnostics failed the Vehicle/OBD2 test by failing to return a VIN. If that’s the case, you probably have a bad cable. It isn’t common, but there have been a few malfunctioning units. Opus can run you through a few more checks and authorize a replacement.

Talked to Opus, they say as long as that bit shows "active" its all good.
They said it doesn't necessarily have to pull the VIN to work.
I'll be getting the license today and go fwd with updates along with the assistance of @Jesse-Infotainment, fingers crossed

 

[JEB]

Talked to Opus, they say as long as that bit shows "active" its all good.
They said it doesn't necessarily have to pull the VIN to work.
I'll be getting the license today and go fwd with updates along with the assistance of @Jesse-Infotainment, fingers crossed

Thanks for the feedback. Mine always returned a VIN, so I thought you had a communication issue when yours didn’t. Good to know that it isn’t necessary. Sorry if I slowed down your work.

Good luck with your programming session.

 

[Mwathey515]

Thanks for the feedback. Mine always returned a VIN, so I thought you had a communication issue when yours didn’t. Good to know that it isn’t necessary. Sorry if I slowed down your work.

Good luck with your programming session.

Doesn’t appear to be necessary as I am in process of downloading updates !

 

[Paul Neubauer]

It's that time again boys and girls... who's feeling brave enough to mash down that accept button?

 

[BlackSheep]

It's that time again boys and girls... who's feeling brave enough to mash down that accept button?

It's an APIM update, and I already installed it without any issues.

 

[Demps]

It's that time again boys and girls... who's feeling brave enough to mash down that accept button?

I did a few days ago. Didn’t notice anything negative.

BTW Just noticed sync now has Android using USB. Don’t know when that happened. And mobile apps are greyed out.

 

[wayfarer556]

Just got this non specific update. Anyone know what this is? I don’t want to push through an upgrade that will downgrade my truck like the last upgrade that attempted to go through…

 

[Ford4Ever]

Mine popped up today after work and I let it install. I don't see an issue with it but it does state that I will receive another update soon. NOTE, my truck is non Blue Cruse.

 

[Big Dog Daddy]

Auto updates "OFF" didn't work. Since early July when @speedracercjr had his updates go horribly wrong. I've religiously followed @Jesse-Infotainment 's advice and have left auto updates off.

Since then my routine has been, before going to work every morning go to updates and check for updates, and check again at night before leaving for home. Every time the response was "you're up to date".

I did the same today, but here's what happened, I checked before and after work as usual, nothing. Got home sat down at the kitchen table and Fordpass popped an alert. I tapped it to take a look and it said "update successfull - check out what's new." So I went out to the truck fired it up, and there’s the screen "new updates have been installed "

Apparently, Ford has somehow pushed this update without my consent!

After having lost use of the truck to my inept dealer for the entire month of March, only not to be fixed, and then spending a $1000.00 and 12 hours to get it fully updated with FDRS and Jesse's help, Thank you Sir! I'm not pleased with what happened today.

Don't get me wrong, I'm very happy that after 9 months of not receiving any OTA's that this happened today. It proved the system work's again. But I'm very disappointed the way Ford has handled this.

 

[antho]

If anyone gets bored, Could you check my vin for updates? Thanks! 1FTFW1RG1MFC28185

 

[RickBullotta]

If anyone gets bored, Could you check my vin for updates? Thanks! 1FTFW1RG1MFC28185

See below. Also, you'll likely get an APIM update after you install the GWM update.

 

[antho]

Thank you @RickBullotta

I would assume thats the Bluecruise map update that people have been getting. I wonder how the OTA releases are done. Some folks have already received these OTA but i dont show any new OTA's pending etc.

 

[redditn00b92]

Howdy, folks. I am typically more active on the Mach-E forums, but it seems like there's a knowledgeable crowd around here for APIM updates.

I've had a stuck APIM since my Mach-E came in (bought it used). TSB 21-2150 applies to my car, but when I tried to run it, I got an error in FDRS saying it failed to download the diagnostic files from the server and that it could mean my VIN is locked out. Based on my vehicle history, I can't figure out how it would be locked out. The module repair wasn't ran more than 15 times in 20 days.

I am now trying to update the USB via the "drive-around-and-wait" method. Mike G from the mach-e forums has been tremendously helpful in pointing me in that direction. I am trying to be patient, but I wanted to check-in here and see if anyone had any tips to get it to update faster? Has anyone ever seen the error I referenced when performing the TSB?

Thanks!

Sponsored