F150chief is correct as ever, your Focus should be set to 68 for this field.
If you have a GPSM showing up in forscan, then your vehicle was not fitted with sync 3 from factory. This was for Sync 2, and someone has incorrectly set your clock master.
Looks like the value is set to 28. @Louage, so I should go ahead and switch this to 68? When I pull my factory AsBuilt, it looks as if this is set to 28 in that .ab file as well.
28 and 68 difference is the amount of time the radio stays on, 20 min vs 60 min, when you push the power button with the ignition off. Basically the same otherwise.
Set it to 68, master reset the APIM, shut down the car completely, let simmer for 15-30 minutes, then start the car, ignition and motor running. See what that does. The BCM needs to pick up the change, hopefully, without doing a reset on the BCM.
Unfortunately doing this alone didnât make a change. I poked around a little bit within the AsBuilt and I noticed that my Region was set to 5753 instead of 5553, so I set it to 5553 for US and now it seems to be working, albeit intermittently. It will still boot up and show 12:00, but eventually it seems to be able to correct itself to the right time. Some sort of latency talking to the GPS? I have kind of always had weird quirks with this APIM ever since I purchased the car brand new, so who knows⌠anyways thanks for your assistance!
Thatâs a change to enable nav in motion. It causes other issues.
If you still have a GPSM attached in the car, unplug it and see if it resolves the issue. If it does, there is a contention between it and the APIM for time. Otherwise just leave it connected. It should be just under the dash at the top.
pretty confident others with the same issue as you have fixed it by flipping that bit? maybe iâm wrong i havenât stayed up to date on the posts on this forum in a while as had other stuff going on.
OK Iâll keep that in mind and try this if it happens again. I hopped in the car earlier today and the clock was correct upon first start, so maybe itâs fixed now?
Most folks with this issue find that it fixed itself after a few key cycles. If you want to downgrade, all you need to do is use the app file for 20196.