Sponsored
rugedraw
Well-known member
You may not be able to do this. You swapped out your 8" screen for the 12" and swapped out the APIM. Did you buy the parts to do the swap from a company that specializes in those things, or did you do everything yourself?
Are there any TCU, GWM or IPC updates showing? If so, do those first to see if the APIM updates releases.
farmtruckman
Well-known member
Facing an issue where all modules in HS2, HS3, HS4, MS CAN networks do not respond to FDRS - Looked at the SSM 51331 and did the GWM configuration and still facing the same issue. Attached some screenshots. Grateful if someone can advise what to do here.
rugedraw
Well-known member
A little back-story: I've been working with him for literally months trying to get his truck updated. His dealer had his truck and was trying to get it updated. With Jesse's help, we were able to make some progress in getting some of the Sync modules updated, but the dealer had trouble getting a TCU USB update installed and all of these modules are now grayed out and unresponsive to FDRS.
I've been following this thread for years, and I know I have seen this issue here before get resolved, but I am not sure what was done to get these modules to successfully start communicating again. I am working with him via messages, but asked him to post here so others can share their insight on this issue as it is something I have never dealt with myself and I've hit all wall in terms of what else we can try. He now has a Mongoose and month long license to FDRS, so hoping that we can get him through this and get his module network fully online again.
JEB
Well-known member
Try this.
SSM 52719 2021-2023 F-150 And 2024 F-150 Lightning - Modules On HS-CAN2, HS-CAN3, HS-CAN4, MS-CAN Do Not Respond To FDRS - No DTCs In The Affected ModulesSome 2021-2023 F-150 vehicles and 2024 F-150 Lightning vehicles may exhibit modules on the high-speed controller area network 2 (HS-CAN2), high-speed controller area network 3 (HS-CAN3), high-speed controller area network 4 (HS-CAN4) and/or the medium-speed controller area networks (MS-CAN) not responding to the Ford Diagnosis and Repair System (FDRS) and the modules on these networks fail the network test without any diagnostic trouble codes (DTCs) tied to the affected modules. The modules on the flexible data rate controller area network 2 (FD-CAN1) and the high-speed controller area network 1 (HS-CAN1) will communicate with the FDRS. Vehicles equipped with a power opening/closing tailgate may also exhibit an intermittent inoperative power tailgate. This may be due to the gateway module A (GWM) not being configured properly. To correct this condition, download and run the GWM - Gateway Module A (GWM) Configuration application using the latest version of the FDRS. For claiming, use causal part number 14G490 and applicable labor times from Section 10 of the Service Labor Times Standard (SLTS) Manual.
Sponsored
rugedraw
Well-known member
JEB
Well-known member
GWM is on HS1. It would remain responsive even if modules on other CANs listed are not responsive. I’d try updating to the most recent version of FDRS, updating GWM if any updates are available and then rerunning the GMW Configuration tool again.
rugedraw
Well-known member
He just installed FDRS, so I am sure it's on the latest version. The problem is, he is in the UAE, so the module updates that require a USB cannot be done by traditional FDRS means since it won't pull the files from the servers over there. He is on the LKB version of the GWM which is not the latest, but there is a TCU update showing that would have to be done first before it will release more updates. Also important to note is those modules were online at one point with the software levels at their current state.
@mmir I can tell you from other cases I have seen where people outside the US update their vehicles with FDRS have had to use a VPN to trick FDRS into thinking it was here in order to be able to fully update their vehicles. It may be worth a try to do this and see if it lets you update the TCU update you have showing and see if that releases a new update for the GWM.
Edit: Just noticed the TCU is showing offline, so I doubt that you'll be able to update it.
farmtruckman
Well-known member
@rugedraw All screenshots today were after the laptop was connected to a VPN exiting Chicago. Confirmed that IP used was indeed a US IP address. When I tried the TCU update this afternoon, it started the process and stopped when the module was to be read and errored out saying - the module cannot be reached and if I wished to try again. It gave the same error for other modules too like the door ones.
Sponsored
JEB
Well-known member
I don’t know either. According to Ford, that’s the fix and you’ve already done it. I’m out of additional steps to try.
Configuration issues seem to be pretty common with trucks located outside the US. Just out of curiosity, is the country code stored in the GWM correct? I believe it’s in the first four bits of 716-08-01. ASCII Code is AE (Arab Emirates) and would be 4145 in Hex. However, I wouldn’t recommend doing anything to the GWM without competent guidance.
rugedraw
Well-known member
JEB
Well-known member
That is the Country Code for the US. Not sure if this is the (or a) culprit, but the code does not match the truck’s current location.This is what he shows:
Same country code int he TCU:
APIM, IPC and PCM all show 5443. PTS also shows vehicle was originally sold in the UAE.
rugedraw
Well-known member
Yup. That is weird that everything is configured as if the truck was here. Thanks for your insight.
@mmir As this point, I would try changing the country code in those 5 locations with FORScan, re-scan with FDRS and run the GWM config again. Worse case scenario, you can just change everything back.
Message me and I'll guide you through it. I've done this with people in other countries to address other issues when importing a vehicle from one country to another. Not sure if this will help your cause or not, but I don't see how it can make things worse.
Sponsored
