098-00720-000 Revision D1 – February, 2018 SyncServer 600 Series User’s Guide 197
Chapter 6 Provisioning
Provisioning Inputs with Manual Entry Controls
though the IRIG with year is not actually driving the precise synchronization output
in this S6xx, it is now being used to extract the current year. Note that the year may
not be immediately adjusted upon qualification of the IRIG that supplies the year,
but it will happen within a few minutes. The message log will provide an entry when
the timeline shift occurs. Here¡¦s an example:
Jan 30 18:46:28 SyncServer alarmd: id 152, index 000,
severity Notify ALARM SET: Timeline has been changed
Continuing with this example, the year is now derived from an external input but the
pending leap and UTC offset values continue to be taken from the user-entry since
the IRIG input on BJ1 does not provide these items either. Since GPS provides all
the information, if we provide GPS as an input these remaining items will be driven
by the status provided via GPS. Since the manual values were intentionally set
incorrectly for this example, they should change to the correct values as GPS
comes up. Figure 6-12 Shows that with GNSS now qualified (and it is also selected
in this case) the leap pending status has been updated because there is actually no
pending leap, which is what the S6xx learned from the addition of the GPS input.
Similarly, Figure 6-13 shows that the UTC offset is now showing 37 seconds, which
is the correct value. Keep in mind in the situation that is the purpose for these
manual controls, such as one where only an IRIG is available as input, then of
course the manual entry for leap would have been “none” and UTC offset set to
“37”, thus allowing for correct information to be encoded on time outputs even
though no active input is providing it.
When GPS was connected, we can see the actions in the message log: the leap
pending event is cleared, GPS becomes selected as the S6xx reference for time
and frequency, the timeline is changed (due to the change in offset).
Jan 30 23:29:40 SyncServer alarmd: id 173, index 000,
severity Notify, ALARM CLEAR: Leap event pending cleared
Jan 30 23:29:40 SyncServer alarmd: id 022, index 000,
severity Notify ALARM SET: GNSS input time qualified
Jan 30 23:29:42 SyncServer alarmd: id 025, index 000,
severity Notify ALARM SET: GNSS input selected as frequency
reference
Jan 30 23:29:44 SyncServer alarmd: id 024, index 000,
severity Notify ALARM SET: GNSS input selected as time
reference
Jan 30 23:33:32 SyncServer alarmd: id 152, index 000,
severity Notify ALARM SET: Timeline has been changed
To Next Page
Loading...
