● With an m:n PCU switchover – the PCU is switched to another NCK and, therefore, to
another PLC – the PCU takes on the switchover disable settings of that PLC.
● The m:n interlock options on the PLC side have priority over the TCU switchover disable,
so that a set TCU switchover disable cannot prevent an m:n switchover. If necessary, the
m:n interference options should be synchronized here with those for the TCU in the PLC.
It may, for example, be practical to set or remove the m:n displacement disable
simultaneously with the TCU switchover disable.
Obtaining user authorization
On a TCU that has no user authorization, the first key that is pressed serves exclusively to
request the user authorization, i.e. this key is not evaluated by the operating software.
The settings for the right to veto are stored in file tcu.ini and are only effective if the operating
software is installed on the PCU. At the OP of the TCU, the operating software can be operated
in exactly the same way as an OP directly connected to the PCU.
Note
These operator input sequence steps must only be carried out by qualified personnel!
1.4.2.11
Example: How to select the behavior of the TCUs during boot up
Example: Distributing boot support across two PCUs
To distribute boot support over two PCUs, "Boot support runtime and configuration only (TFTP/
FTP)" must be selected on PCU_1 and "Boot support IP address only (DHCP)" must be
selected on PCU_2.
The "No boot support" configuration must be selected on PCU_3:
Table 1-26
"TCU support" settings
TCU_1
192.168.214.10
VNC connections:
192.168.214.241
192.168.214.242
192.168.214.243
PCU_1
192.168.214.241
Operator panel front: OP 010
Manual, 07/2018, A5E36371538B
TCU_2
192.168.214.11
VNC connections:
192.168.214.241
192.168.214.243
Switch to system network
PCU_2
192.168.214.242
General information and networking
TCU_3
192.168.214.12
VNC connections:
192.168.214.241
192.168.214.243
PCU_3
192.168.214.243
1.4 Networking
TCU_4
192.168.214.13
VNC connections:
192.168.214.241
192.168.214.242
75