Failed update, features disabled, stopped communicating

[avdonr]

I see. Since I updated all modules, I'm also guessing I have the updates for 6.3.0, 6.4.0, 6.5.0 and 6.6.0, as no further updates were at all available on FDRS.

The only weirdness was my FordPass app got a notification that there was a blind spot detection fault.

If you applied all the updates in FDRS including the powertrain updates then yeah you are up to date with 6.6.0.

The faults are usually false positive just because a bunch of modules go offline during programming so the car freaks out. After updating modules I always go and clear all DTCs from the car under the self test menu. This should clear your faults as well.

Sponsored

 

[jayadelson]

The faults are usually false positive just because a bunch of modules go offline during programming so the car freaks out. After updating modules I always go and clear all DTCs from the car under the self test menu. This should clear your faults as well.

I actually did clear out all DTCs after I performed all the updates. The fault happened on a drive since the updates. I'll plug in later and see if I can get any info on it.

I noticed there are different firmware updates that seem more option/engineering oriented in other tabs, I'm presuming I should leave all that stuff alone that isn't in the SW UPDATES section, right?

 

[avdonr]

I actually did clear out all DTCs after I performed all the updates. The fault happened on a drive since the updates. I'll plug in later and see if I can get any info on it.

I noticed there are different firmware updates that seem more option/engineering oriented in other tabs, I'm presuming I should leave all that stuff alone that isn't in the SW UPDATES section, right?

Hmm, to be honest I didn’t get a fault but I got an issue where the blind spot detection settings in the APIM were disabled on the first drive after I updated. It fixed itself after the first drive though and everything was fine after that.

You’ll probably be able to clear the fault again and it’ll be fine, but if it still persists it may be an actual issue.

Those other tools are useful but have very specific use cases. The only other tools I’ve used beyond software updates are TPMS learning mode to re-pair my tire pressure sensors, BECM battery health report, and the PMI programs to help solve dependency issues in the past.

 

[Jbk]

Just updating the ACM and GWM already fixed the Connected Vehicle Services issue! No need to swap the GWM module, as @Mach-Lee predicted.

While I’m at it, I’ll catch up the OTA on the other modules and APIM using FDRS. Not sure there are enough acronyms in that sentence…

I’m excited to see you’ve been able to fix! However I have no idea what you did or used. The only acronym I know is OTA!
Is it possible for me to fix or am I stuck with dealership?(They want to keep it a couple of days to begin with) What equipment would I need and how (think 10 year old kid!) do I do it?

 

[jayadelson]

I’m excited to see you’ve been able to fix! However I have no idea what you did or used. The only acronym I know is OTA!
Is it possible for me to fix or am I stuck with dealership?(They want to keep it a couple of days to begin with) What equipment would I need and how (think 10 year old kid!) do I do it?

The process I used involved using my laptop (Windows unfortunately), a Mongoose OBD interface cable, and the FDRS software (Ford sells a license, but you can get a cheaper one that only lasts a short time).

I have a lot of experience using tools like this for my work, though, so the process was a bit more natural for me.

Fortunately, there is a thread dedicated to this topic that even includes some instructional videos:

https://www.macheforum.com/site/thr...ach-e-with-fdrs-alternative-to-forscan.10217/

Sponsored