Post here if you have an active FDRS account and are willing to look up info for others

[dannyn67]

Welcome to the forum. Your build date is 13 Sep '20, which makes your car one of the earliest I've seen.

Here's the list of available updates showing in FDRS:

Also, as to your inability to activate and use your car with FordPass......

It would be terribly spiffy if somebody at your Ford dealership could take your car our of "Fleet mode"...which is the reason you can't connect.

It needs to say "Retail Authorized" under Modem Activation. You don't need any parts...this doesn't require engineering support. It just needs to be taken out of fleet mode.

Sometimes with some folks it's like they're a hog lookin' at a wristwatch.

Oh, and I guess you can get them to finally finish the BlueCruise programming that previous owner(s) never got around to. Or at least get the service department to confirm it's done and clear the FSA.

Thank you so much Mike!!

Sponsored

 

[CarGuy11]

Can I get a status check? Thx! 3FMTK3SU9NMA41574

 

[Hammered]

Can I get a status check? Thx! 3FMTK3SU9NMA41574

 

[LeanneL]

12 Apr '22 build date.

If you cannot schedule updates using the Sync menu you have a problem that needs to be diagnosed and corrected by the dealer. Normally this diagnosis will result in the GWM (gateway) being reprogrammed at a minimum, and if that doesn't correct the situation it might need to be replaced (although completely reprogramming it by doing a PMI should do the trick).

Now, having said that....ask your service advisor why your TCU modem activation status says both "Retail Authorized" and "Fleet Authorized" at the same time.

That might be a clue. Normally on a customer owned car it just says "Retail Authorized" and OTAs show up.

Here's the list of available software updates from FDRS:

Once my dealership removed the fleet authorized, I was able to get OTA's. Fingers crossed that works for you as well! I mean, I also did a bunch in FDRS, but OTA did start working, I'm just very impatient

 

[Ressex]

Congrats on the new car!

Here's the list of available updates shown in FDRS:

Thank you soo much Mike really appreciate it having major issues at the minute one week in where I’m not getting blue cruise at all after subscribing it’s not even showing up on the about screen and I’m on a really old software version and also my connected icon on the dashboard is intermittent.

 

[rugedraw]

Thank you soo much Mike really appreciate it having major issues at the minute one week in where I’m not getting blue cruise at all after subscribing it’s not even showing up on the about screen and I’m on a really old software version and also my connected icon on the dashboard is intermittent.

Does you "about sync" say you're on Sync 4.0.23ddd? You got APIM OTA 4.1.2.2 a few days ago, but I don't think that is the Sync version that coincides with that update.

 

[Ressex]

Does you "about sync" say you're on Sync 4.0.23ddd? You got APIM OTA 4.1.2.2 a few days ago, but I don't think that is the Sync version that coincides with that update.

Hi Rugedraw

yes it does say that. What does that mean.

 

[rugedraw]

Hi Rugedraw

yes it does say that. What does that mean.

I have no idea. Maybe it means nothing, but it does not look normal to me. Based on my experience, with the 4.x.x updates, your Sync version should read 5 numerical digits starting with 22 or 23.

 

[Ressex]

Does you "about sync" say you're on Sync 4.0.23ddd? You got APIM OTA 4.1.2.2 a few days ago, but I don't think that is the Sync version that coincides with that update.

I have no idea. Maybe it means nothing, but it does not look normal to me. Based on my experience, with the 4.x.x updates, your Sync version should read 5 numerical digits starting with 22 or 23.

yea no idea what’s going on with it but it’s very annoying and dealers don’t seem to have any control over updates they simply have to submit a ticket to the Ford engineering team. Why can consumers obtain the equipment and updates but dealers have not got it all very odd.

 

[rugedraw]

yea no idea what’s going on with it but it’s very annoying and dealers don’t seem to have any control over updates they simply have to submit a ticket to the Ford engineering team. Why can consumers obtain the equipment and updates but dealers have not got it all very odd.

The dealers do have the equipment. What they don't have is the knowledge. Mechanics are not software engineers. The program they use has guided routines that does the module programming for them. If something goes wrong, they have to contact engineers. That's how it is with all brands.

 

[rugedraw]

@Ressex I asked someone with above-average knowledge to take a look at your car. It does not seem that the Sync version you are on is an issue. However, it seems like the APIM OTA you got somehow changed the config in one of the locations of the APIM which is causing some of the issues you are reporting. It's an easy fix with FORScan. I can't tell you much about the connectivity issue, though.

7D0-09-04 xxxx xxxx Fxxx

That value should be an "F" and your car is showing an "E" there.

If you're not a FORScan kinda person, then take it to the dealer. They can run an APIM config with FDRS and that'll fix it. You can also ask them to look into the connectivity issue.

 

[Ressex]

@Ressex I asked someone with above-average knowledge to take a look at your car. It does not seem that the Sync version you are on is an issue. However, it seems like the APIM OTA you got somehow changed the config in one of the locations of the APIM which is causing some of the issues you are reporting. It's an easy fix with FORScan. I can't tell you much about the connectivity issue, though.

7D0-09-04 xxxx xxxx Fxxx

That value should be an "F" and your car is showing an "E" there.

If you're not a FORScan kinda person, then take it to the dealer. They can run an APIM config with FDRS and that'll fix it. You can also ask them to look into the connectivity issue.

That’s really good of you to look into this I appreciate it. I took it to the dealer today they said they did something but that didn’t resolve anything. They have now submitted a request to Ford Engineering to see what they advise as for some reason they can not do anything more their end.

 

[Ressex]

@Ressex I asked someone with above-average knowledge to take a look at your car. It does not seem that the Sync version you are on is an issue. However, it seems like the APIM OTA you got somehow changed the config in one of the locations of the APIM which is causing some of the issues you are reporting. It's an easy fix with FORScan. I can't tell you much about the connectivity issue, though.

7D0-09-04 xxxx xxxx Fxxx

That value should be an "F" and your car is showing an "E" there.

If you're not a FORScan kinda person, then take it to the dealer. They can run an APIM config with FDRS and that'll fix it. You can also ask them to look into the connectivity issue.

Also how easy is this to do myself and what would I need.

 

[rugedraw]

Also how easy is this to do myself and what would I need.

Oh it's still at the dealer? Ok they should be able to get it sorted out. We can revisit this if the issue persists.

 

[Ressex]

Oh it's still at the dealer? Ok they should be able to get it sorted out. We can revisit this if the issue persists.

Yes but there are waiting to hear back from Ford.

Sponsored