Changes

Time Synchronization settings, where the user can choose which source(s) to use for {{{model|FMB1YX}}} time synchronization. User has a choice to: use only one synchronization source (<span style="color:#F6A83E">Disable (GPS only)</span>), allow synchronization from both the GNSS and NTP server (<span style="color:#F6A83E">NTP</span>), select synchronization through GNSS and GSM operator (<span style="color:#F6A83E">NITZ</span>) or from all three sources (when <span style="color:#F6A83E">NITZ+NTP</span> is selected). Users can select which NTP server (it is possible to configure up to two servers) and what time period to use to resynchronize time. <br>

Time Synchronization settings, where the user can choose which source(s) to use for {{{model|FMB1YX}}} time synchronization. User has a choice to: use only one synchronization source (<span style="color:#F6A83E">Disable (GPS only)</span>), allow synchronization from both the GNSS and NTP server (<span style="color:#F6A83E">NTP</span>), select synchronization through GNSS and GSM operator (<span style="color:#F6A83E">NITZ</span>) or from all three sources (when <span style="color:#F6A83E">NITZ+NTP</span> is selected). Users can select which NTP server (it is possible to configure up to two servers) and what time period to use to resynchronize time. <br>

*using 03.25.13 or older firmware

{{{txt_hide_tmt250|*using 03.25.13 or older firmware

 

===New time synchronization method implementation*===

===New time synchronization method implementation*===

From 03.25.14 firmware the new time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. <br> This state checks the difference between RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a resynchronization procedure by GNSS. <br> After that, the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time resynchronization.<br>

From 03.25.14 firmware the new time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. <br> This state checks the difference between RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a resynchronization procedure by GNSS. <br> After that, the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time resynchronization.<br>

In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to the state of syncing by NTP. Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP resynchronization time is reached (if the resynchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.  

In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to the state of syncing by NTP. Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP resynchronization time is reached (if the resynchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.  

* using 03.25.14 or newer firmware<br>

{{{txt_hide_tmt250|* using 03.25.14 or newer firmware<br>

 

[[image:Timesyncflowchart.png|center]]

[[image:Timesyncflowchart.png|center]]