196 SyncServer 600 Series User’s Guide 098-00720-000 Revision D1 – February, 2018
Chapter 6 Provisioning
Provisioning Inputs with Manual Entry Controls
Manual Entry Example
The example below illustrates the “pooling” behavior that ALL qualified time inputs
(not just the selected time reference) are used to learn current status for any of
these manual entries. In this case, two IRIG inputs are initially enabled; the specific
configurations shown in Figure 6-6 (access this form via References„³Status). Note
that the IRIG input configured for slot A does NOT provide the year whereas the
IRIG input configured for slot B does provide the year. Initially, only the no-year IRIG
is actually supplied (this is why it is green and the slot B J1 input is red). Figure 6-7
shows the status from the Dashboard„³Timing form. Since the only qualified (and
selected) reference does not provide the year (or pending leap or UTC offset)
information, the user can provide this information. On the manual inputs portion of
the Timing > Input Control form (Figure 6-8) an action is taken to provide all of these
values. For this example, they are intentionally provided with wrong values in order
to illustrate the behavior when inputs are added later that provide the correct
information. Of course, in actual usage (where only the input shown is available) the
correct information should be provided.
With only the IRIG no-year input qualified (Figure 6-7) the values shown in Figure 3
were entered. The effectiveness of each of these entries can be seen by the
following methods:
The manually entered year was accepted as can be seen in the upper right of the
web application (see Figure 6-9). All time outputs that provide year information
will now be providing this year.
The manually entered pending leap was accepted as can be seen on the Leap
Pending row in Figure 6-7. Outputs that supply pending leap information indicate
pending (and direction of the leap) at the time appropriate for those outputs (see
section titled Reporting of Leapsecond Pending).
In release 2.0, the only output that is not based on UTC timescale is the PTP
(IEEE-1588) master capability. If a PTP master is configured on one of the LAN
ports (2-4), the current value of UTC to TAI conversion can be seen on the
Network Timing„³NTPr/PTP Status form. For this example, LAN2 had been
configured for PTP master function. Figure 6-10 shows a portion of the status.
Note that the Current UTC offset value is shown to be 14 seconds, which is due
to the manual entry (Figure 6-8). Note also that a pending leap is NOT shown
even though it is indicated on Figure 6-7. This is behavior is illustrated in Figure
6-14.
Now connect the year-capable IRIG that is configured on the slot B J1 input(see
Figure 6-6). Figure 6-11 shows that after this input becomes qualified, the correct
year is extracted from this input, shown in the upper right of the web interface (and
will be encoded onto any time outputs that provide year). Note that the time input
that is currently driving the S6xx outputs is still the IRIG without year connected to
slot A J1. This is because that input has higher priority. The example illustrates that
ALL qualified inputs are used for extraction of the items shown on Figure 6-8. Even
To Next Page
Loading...
