Phoenix Contact 1136419, Руководство пользователя

Страница: 17 / 130

The redundant control system
110146_en_00 PHOENIX CONTACT
17 / 128
3.3 Causes of switch-over
The redundancy role of the controllers (PRIMARY or BACKUP) determines which of the two
controllers manages the process.
Table 3 - 2 shows what causes the redundancy roles to be switched over. Each cause has a
defined code.
The most recent cause of a switch-over is indicated in PLCnext Engineer as a digit in the
RDNCY_LAST_SWITCH_OVER_REASON system variable (see column 1 in Table 3 - 2 ). In
addition, the most recent cause of a switch-over is displayed in PLCnext Engineer in the
“Cockpit” editor (“Redundancy Status” view, “Switch Over Reason”).
Table 3 - 2 Causes of switch-over
Digit Display in the “Cockpit” edi -
tor
Description
0 None No switch-over of the redundancy role since
the last time the PRIMARY controller was re -
started.
1 FirmwareService The redundancy role was changed by the
user.
2 RuntimeException A runtime error occurred on the PRIMARY
controller.
3 LinkDownPnLan The physical network connection to Ethernet
interface LAN1 was disconnected (LNK LED:
off).
4 AllArsLost The PROFINET controller has lost the connec -
tion to all PROFINET devices via Ethernet in -
terface LAN1.
5 ArLost The PRIMARY controller has lost the connec -
tion to at least one PROFINET device.
6 SystemShutdown The firmware of the PRIMARY controller was
stopped by the user.
7 SystemTerminate The firmware of the PRIMARY controller was
stopped due to an operating system exception
that occurred.
8 PowerDown The PRIMARY controller was disconnected
from the power supply.
9 SyncLinkTimeout A timeout occurred on the SYNC interface and
on Ethernet interface LAN1.
10 InternalError An internal error occurred.