rugedraw
Well-known member
Your truck reported these codes on 8/1 and again on 8/2 before it went off the grid. Both TSB's call for an update of the GWM to correct the issue.TCU is back! It turned on at some point while at work but it never turned on during my 1 hour commute this morning lol. If I had to guess, it was a battery voltage issue. I found out in a funny way that it was on lol.
As for the dongle, I think I am going to go with the bluetooth version. I might just go with the OBDLink Mx+ simply for the fact that it will have coverage for many other vehicle brands than just the Vgate VLink FS bluetooth version. I understand the Vgate FS bluetooth also has coverage but it will depend on which app/software it is linked to it while OBDLink has their own updated app and then I can just re-use it with FORscan.
Anyways, mind checking my Vin before something else happens? lol Vin: .
Lots of pending updates. The problem is, you do not show a pending update for the GWM. According to FDRS, there are no pending updates waiting behind these that are showing for you. Also, your truck is on Sync 22230 which is 3 year old software at this point. Because you are not showing any pending updates for the GWM, APIM or TCU, this means your truck is most likely affected by the attached SSM where Ford, for whatever stupid reason, is blocking updates for vehicles on Sync 23187 or lower.
Even if you had FDRS, you would not be able to update you truck's Sync modules to the latest version. The issue is on Ford's side and not with your truck. Until Ford gets its head out of its own ass in regards to why they are blocking updates for vehicles on antiquated software, there is nothing you (or the dealer) can do.
Sponsored
Attachments
-
162.7 KB Views: 47