Redundancy In The Same Lan - Siemens SICLOCK TS Betriebsanleitung

User Manual SICLOCK TS V2.0

9.7 Redundancy in the same LAN

By utilization of two SICLOCK TS units and by setting the parameter 222/3B Redundancy to the value
"Priority Master" or "Priority Slave" a redundant operation in the same LAN is possible. A SICLOCK TS
defined as "Priority Master" examines after network start-up for 5s long, whether there is already a SIC-
LOCK TS functioning as Timemaster in the network and transmits Alive protocols to it (individual addres-
ses). If this is the case, it remains in Slave mode. A SICLOCK TS defined as "Priority Slave" behaves
analogous, but waits for 15s after network start-up. A Slave takes over the Master time with every Alive-
Protocol received (per jump) and compares this with its own external synchronization. If the Master
breaks down for more than 3s, the Slave takes up the transmission operation, falling back into Slave
mode when the Master returns.
Master and slave must be parameterized identically in respect of the LAN channels. Pa-
rametering must also contain a channel for the transmission of the Alive protocol every
second to the corresponding individual address.
The current network status is displayed in menu 1A. In correct operation, the LAN indicator on the
Slave must be on SLV and the synchronization indicator on L. The reception of protocols can be ob-
served in menu 1D. On the Master, only the LAN-indicator in menu 1A must be on MAS. If a Slave
takes up the transmission operation even though the Master is functioning perfectly, then the correct
parameterization (addressing) of the Alive protocol should be checked.
9.8 Redundancy on S7/PCS7
By setting the parameter 222/3B Redundancy to the value "S7 Master" SICLOCK TS can be integrated
in S7/PCS7 synchronization strategies (from Version 5). Such a S7-Master checks for at least 2 minutes
after network start-up whether synchronization protocols for S7/PCS7 are in the network. If this is the
case, then their time will be taken over (per time leap).
Taking over of transmission occurs in the following cases:
• No synchronization protocol in the timeout
• SICLOCK TS is synchronized externally and the current Master is not a SICLOCK TS
• The current Master is not synchronized and is not a SICLOCK TS
• The current Master proves to be a time-standby server.
As standby servers as a rule S7/PCS7 components are used, these withdraw after the transmission ope-
ration has been taken up by the SICLOCK TS. It is also possible, however, to define a second SICLOCK
TS (S7-Master) as standby server. Then it is necessary for a preferential position to be set in the case
of joint start-up. This is achieved via various different timeouts. The timeout of a S7-Master is therefore
2 minutes plus an offset of 0.5s dependent on its own MAC address.
Transmission take-over by SICLOCK TS is normal, so in such a configuration no time-
out message is generated.
32
Checkbox
Version 2.0 Order No. 2XV9450AR53-BA