Battery / APIM issue, now ACM issue.

[JDaleo]

@Jesse-Infotainment , before freaking out more at Ford and requesting my truck back (if i don't get something concrete from them by early next week, after I get the FORScan adapter), i just want to see how confident you are that i'll be able to fix this issue on my own. I noticed on the pictures in the other thread of how to correct this, there are items in there that I don't believe would would fit my vehicle's, such as "Climate Overlay" options, which I think were for Sync 3? Just want to make sure that it seems like the issue is the same and I may just have to enable those modules.

Sponsored

 

[rugedraw]

So this morning they're telling me a "field service engineer was looking at the truck yesterday and the truck is not recognizing the satellite signal, the Ford software does not enable the antennas".... what?!
@rugedraw , do you happen to see anything in the system where my truck was even touched yesterday? I don't see anything on my end, the truck wasn't started or driven. He said the next step is a note needs to be sent to Ford because there is an issue with the APIM, and they need to await Ford's reply, but he said they can be pretty slow to respond.

I see no indication anyone has touched your truck since 6/2. If Jesse says he can fix it, then he can fix it.

 

[JDaleo]

@Jesse-Infotainment upon connecting the truck to my laptop, I see some codes: B119F, U3003, U0554. Waiting on an extended license to FORScan. When I get it, what should I be checking? Is it the Mobile Navication, Navigation Repeater and X40 SDARS setting in the APIM or something else?

 

[Jesse-Infotainment]

Clear codes and see what returns

In as build select load factory as build and then write all

 

[JDaleo]

Clear codes and see what returns

In as build select load factory as build and then write all

Nothing returned after ignition cycle. Hit Load Factory AB under APIM, it downloaded. When I hit Write All, it says no changes. Force write?

 

[Jesse-Infotainment]

Nothing returned after ignition cycle. Hit Load Factory AB under APIM, it downloaded. When I hit Write All, it says no changes. Force write?

that means whatever is in the ApIM matches online.

Send me your vin SO I can look

 

[JDaleo]

Nothing returned after ignition cycle. Hit Load Factory AB under APIM, it downloaded. When I hit Write All, it says no changes. Force write?

Also wanted to point out that in APIM, X40 SDARS Radio has a value of "Pre X40 SDARS". Mobile Navigation is Enabled, but Navigation Repeater in Cluster Setting is Disabled.
Not sure if they apply here like they did in the other thread

 

[JDaleo]

that means whatever is in the ApIM matches online.

Send me your vin SO I can look

Sent.

 

[JDaleo]

Sent.

And just like that, it's fixed. Thank you Jesse!

 

[bigbulls]

I've been following this problem just because. Did I read this right that your truck has been at the dealership for nearly 4 weeks and they couldn't fix it and in just a few minutes Jesse fix it online?

 

[Jesse-Infotainment]

I've been following this problem just because. Did I read this right that your truck has been at the dealership for nearly 4 weeks and they couldn't fix it and in just a few minutes Jesse fix it online? Time for a new dealer.

No dealer could fix it. Wouldnt matter who he went to.

 

[bigbulls]

Okay my bad,

 

[Jesse-Infotainment]

Okay my bad,

Ill expand.. I should have

The issue was the as build got corrupted in the update. The dealer can only run the config in FDRS and FDRS will only load what is on Fords servers.

The as build was wrong on Fords side so no matter how many APIMs they would install the problem would have been the same. The apim was never bad.

The as build was corrected and it works now. It was only one change. Dealers do not have the ability to look at as build in modules unless they have forscan which most do not. Even if they did most wouldnt know what does what or what to change or what it should be. I do.. So I was able to see the issue very quickly after getting his vin

 

[bigbulls]

Ill expand.. I should have

The issue was the as build got corrupted in the update. The dealer can only run the config in FDRS and FDRS will only load what is on Fords servers.

The as build was wrong on Fords side so no matter how many APIMs they would install the problem would have been the same. The apim was never bad.

The as build was corrected and it works now. It was only one change. Dealers do not have the ability to look at as build in modules unless they have forscan which most do not. Even if they did most wouldnt know what does what or what to change or what it should be. I do.. So I was able to see the issue very quickly after getting his vin

Thank You Jesse for the update, We are very fortunate to have you on this site.

 

[JDaleo]

I've been following this problem just because. Did I read this right that your truck has been at the dealership for nearly 4 weeks and they couldn't fix it and in just a few minutes Jesse fix it online?

Yup! As Built data from Ford had incorrect values.. he was able to jump in and fix them. Simple write to APIM, it rebooted and gps and sxm kicked right in. Incredible!

Now that I have FORScan, I might as well activate Glare Free headlights. Anything else that you all recommend changing? Possibly Bambi mode, if that does not conflict with Glare Free, or would even serve a purpose with GF. I would like to play around with the different DRL modes, just for fun.

Sponsored