Why will not Ford take my money?

[rugedraw]

Still no BC maps. Do have this DTC (not on dash) after each trip:

Code: U2400 - Ethernet Failure With Gateway Module A (GWM)

Status (-2C):
- DTC Maturing - Intermittent at Time of Request
- Malfunction Indicator Lamp is Off for this DTC

Module: Image Processing Module A

Found a TSB for this code, but the fix doesn't fix it.

I can tell you with 100% confidence that code will prevent BC from working. That code references an old TSB citing outdated BC maps in the GWM. See attached.

Sponsored

 

[hb.sagen]

10 key cycles doesn´t fix it. But I had a large chunk downloaded a few weeks back. Wondering if its just a Gateway misconfiguration at this point.

 

[rugedraw]

10 key cycles doesn´t fix it. But I had a large chunk downloaded a few weeks back. Wondering if its just a Gateway misconfiguration at this point.

I don't think so. Unless you went into the GWM blindly and started changing stuff. Even then, the code for a misconfiguration is U2101 and it would specifically say that. The changes you made to enable BC worked. BC shows active in your connected services now. You have BC until 2028.

While ethernet failure codes often mean bad hardware or a loose ethernet connection, I don't think that is the case here. Based on the updates in queue in your OTA history, your GWM is very outdated.

 

[hb.sagen]

I got a "Welcome to BlueCruise" message in the Sync one day, and the subscription showed up in the app.

My Gateway coding is very far from US trucks with similar build, but as you say, it's very outdated as well. And will forever be as we don't get OTAs.

We don't have the Software Updates tab in the Sync either, even though it's enabled in APIM with Forscan. This I also believes is connected to the gateway coding.

 

[rugedraw]

I got a "Welcome to BlueCruise" message in the Sync one day, and the subscription showed up in the app.

My Gateway coding is very far from US trucks with similar build, but as you say, it's very outdated as well. And will forever be as we don't get OTAs.

We don't have the Software Updates tab in the Sync either, even though it's enabled in APIM with Forscan. This I also believes is connected to the gateway coding.

You need to get the dealer to update the APIM, TCU and GWM at least once each. Or invest in a Mongoose cable and do it yourself.

 

[hb.sagen]

I am hesitant to do it myself as the vehicle is still under warranty.

Neither of those modules have pending updates in PTS. But that may be separate from FDRS?

 

[rugedraw]

I am hesitant to do it myself as the vehicle is still under warranty.

Neither of those modules have pending updates in PTS. But that may be separate from FDRS?

FDRS can show something different. If you have no pending updates for the APIM, GWM, TCU or IPC in FDRS, then there may be some back-end issues that would need to be addressed by Ford engineers. If you still have warranty, I would take it to the dealer, tell them BC is not working and you have an IPMA code referencing the TSB I sent you. This will give them an avenue to do those updates and bill Ford for the work. If there are no updates for those modules pending, they would need to open a case with TAC and see why. If that's the case, then be prepared to leave your truck there for an extended period of time.

 

[hb.sagen]

I managed to read DID 0x9140 directly from the Gateway Module.

The GWM uses:

• Request CAN ID: 716
• Response CAN ID: 71E
• UDS request: 22 91 40

Commands used:

ATZ
ATE0
ATL1
ATS1
ATH1
ATSP6
ATCAF1
ATCFC1
ATSH716
ATCRA71E
229140

The GWM returned a valid multi-frame ISO-TP response:

71E 10 7B 62 91 40 5A 55 35
71E 21 54 2D 31 34 48 33 39
71E 22 34 2D 58 58 58 30 30
71E 23 30 30 30 00 00 00 00
...

After removing the ISO-TP frame bytes and decoding the data as ASCII, DID 9140 contains:

ZU5T-14H394-XXX00000

The remaining bytes are all 00. The final CC CC bytes shown by the adapter are only CAN-frame padding and are not part of the DID value.

The response was successful:

• 62 = positive response to ReadDataByIdentifier
• 91 40 = requested DID
• 0x7B = 123-byte UDS response payload

The value ZU5T-14H394-XXX00000 appears to be a default or placeholder BlueCruise map identifier rather than an actual installed map version. This matches my issue where SYNC does not display a BlueCruise map version, despite BlueCruise being enabled.

For comparison, a normally populated North American BlueCruise map DID looks like MU5T-14H394-AAY, with earlier versions including AAT, AAU and AAV. European vehicles have used identifiers such as MU5T-14H394-EAU.

My GWM instead reports ZU5T-14H394-XXX00000, which appears to be an unpopulated or placeholder value rather than an actual regional BlueCruise map package.

 

[rugedraw]

Everything you posted above goes well beyond my scope of knowledge, but it seems like a reasonable finding. I really just think you need to get the dealer to update the GWM and everything will work.

 

[Henry Ford]

One guy on Earth wants to pay for BlueCruise and his truck is broken. It's like the episode of the Twilight Zone where the guy who loves reading survives an atomic blast, has access to all the books in the library with nobody to bother him and he steps on his glasses.

Sponsored