Daylight savings woes with clock

[Hilltop]

I was hoping my truck would automatically update the clock to “fall back” but alas, no. So I proceeded to manually go in to the settings and adjust it manually. However, the next time I started the truck, instead of the correct time, the clock showed “— —“ so I manually entered the correct time again. This scenario has now repeated three times. Is anyone else experiencing this? Any suggestions?

Sponsored

 

[SkeeterB]

No, fell back without a hitch.

 

[MavDave]

I noticed when I first got in mine Sunday morning it didn't fall back but after I connected my phone it did. I don't know if it needed a reference or it was slow updating, I also keep the wi-fi off so that may have contributed.

 

[TpaTruck]

Mine did the same thing once. However the next time I restarted the truck, it was fine. I had problems setting it before too. It doesn't have a 'submit' or 'ok' button after you change the time, which is silly.

 

[TedTX]

Really long delay. But it happen automagically.
to the ——— poster yeah if you exactly correct the time on a autocorrecting time system to the second: it doesn’t know what to due so designed to give up. Ok for computers either it not an issue or you would just retry click set if still wrong.
But since it’s not a computer OS you are left with the unknown as its answer.
Just retry again the chances of hitting it exactly to the second again is still 1/60

 

[TedTX]

Mine did the same thing once. However the next time I restarted the truck, it was fine. I had problems setting it before too. It doesn't have a 'submit' or 'ok' button after you change the time, which is silly.

Ok details I left out above, this really reminded me of stress I had to add a simple I first thought function to set local time on a multiple country company new user interface.
There is a massive problem to set the clock back in a running system. It blows up so much code and to add safety in all those cases would add 3x the code. Going forward is much less problematic.
So the system treats clock changes at a very protected mode. It doesn’t really change the time until the shutdown after all the data logging has turn off. Network generally is still active so time servers can be used as a safeguard.
I was able to get source code of that subsystem and they gave a chunk of code to fool the user that time was changed. There is no direct way available to change time directly.
Buttons to cause action would be immaterial. You are triggering an action to be applied once in the future.

 

[TedTX]

Follow up. I think we ( Ford) have not actually been through a clock reset BACK in large numbers. I think some of the battery issues Ford fixed was caused by Ford snooping on our trucks too much. So the fix was to stop doing that. That also caused the large delay in triggering the clock adjustment. I bet this would not happen in the future.
I think Ford is trying new technology ideas as they make new models. It would make sense that if they could off load the once in the while events to mainframe code and just trigger the results in the truck stripped down car computer.

 

[MakinDoForNow]

I was hoping my truck would automatically update the clock to “fall back” but alas, no. So I proceeded to manually go in to the settings and adjust it manually. However, the next time I started the truck, instead of the correct time, the clock showed “— —“ so I manually entered the correct time again. This scenario has now repeated three times. Is anyone else experiencing this? Any suggestions?

There should just be a setting daylight savings = on/off. All my clocks self set except battery ones. I have one that just counts the AC cycles. About every four months I have to set it up 5 or six minutes so I am guessing that the 60 cycles AC is off slightly but it may loose a few seconds when it's running on battery when electricity goes off. If electricity is off for 45 minutes the clock on battery backup may only lose a very few seconds.

 

[TedTX]

To the poster above I missed that you did already try multiple times

Enter in the incorrect time less than 14 minutes off, over future time should be more successful than changing back if this is the side effect I think is occurring.
That should trigger the fetch of time sync and end your stalemate issue.
The result should be that the network time sync servers ( more trusted than you human ) return time would be used. It should automagically correct itself. Either way you should clear the screen and display time again even if wrong.

 

[MLowe05]

There should just be a setting daylight savings = on/off. All my clocks self set except battery ones. I have one that just counts the AC cycles. About every four months I have to set it up 5 or six minutes so I am guessing that the 60 cycles AC is off slightly but it may loose a few seconds when it's running on battery when electricity goes off. If electricity is off for 45 minutes the clock on battery backup may only lose a very few seconds.

There is a daylight savings time on/off setting in my Lariat with Sync3. Had to select it manually but it worked fine. It did not do it automatically like our Acura.

 

[ShadowChas]

I thought only the lariat’s with actual sync3 systems would do it automatically. I changed my xlt myself no problem

 

[MLowe05]

I thought only the lariat’s with actual sync3 systems would do it automatically. I changed my xlt myself no problem

Have Lariat with Sync3 and it was definitely not automatic.

 

[Fitzovich]

In the year 2022 with all the technology built into these vehicles it is absurd that the clocks do not automatically sync with the correct local time. it is also absurd that if they don’t the owners manuals don’t have the word “clock“ in the index.

 

[MakinDoForNow]

Have Lariat with Sync3 and it was definitely not automatic.

Should be once you set daylight savings ON

 

[minitrucknuts]

Ok details I left out above, this really reminded me of stress I had to add a simple I first thought function to set local time on a multiple country company new user interface.
There is a massive problem to set the clock back in a running system. It blows up so much code and to add safety in all those cases would add 3x the code. Going forward is much less problematic.
So the system treats clock changes at a very protected mode. It doesn’t really change the time until the shutdown after all the data logging has turn off. Network generally is still active so time servers can be used as a safeguard.
I was able to get source code of that subsystem and they gave a chunk of code to fool the user that time was changed. There is no direct way available to change time directly.
Buttons to cause action would be immaterial. You are triggering an action to be applied once in the future.

Follow up. I think we ( Ford) have not actually been through a clock reset BACK in large numbers. I think some of the battery issues Ford fixed was caused by Ford snooping on our trucks too much. So the fix was to stop doing that. That also caused the large delay in triggering the clock adjustment. I bet this would not happen in the future.
I think Ford is trying new technology ideas as they make new models. It would make sense that if they could off load the once in the while events to mainframe code and just trigger the results in the truck stripped down car computer.

To the poster above I missed that you did already try multiple times

Enter in the incorrect time less than 14 minutes off, over future time should be more successful than changing back if this is the side effect I think is occurring.
That should trigger the fetch of time sync and end your stalemate issue.
The result should be that the network time sync servers ( more trusted than you human ) return time would be used. It should automagically correct itself. Either way you should clear the screen and display time again even if wrong.

WITF?

Sponsored