Phoenix Contact 1136419, Руководство пользователя, Страница: 110 / 130

RFC 4072R
110 / 128
PHOENIX CONTACT 110146_en_00
13 Troubleshooting
The most recent status or error message is indicated in PLCnext Engineer as a digit in the
RDNCY_ERROR system variable (see column 1 in Table 13 - 1 ).
Table 13 - 1 Possible status and error messages in the “Redundancy” menu
Digit Status or error message Description Remedy
1 OwnRdncyTypeChanged The redundancy type of the controller
has been changed.
• Restart the controller to apply the
modified setting.
2 OwnIPAddressChanged The IP address has been changed at
at least one of the Ethernet inter -
faces.
• Restart the controller to apply the
modified setting.
3 InvalidIpAddress At least one IP address is outside of
the valid IP address range.
• Assign an IP address that is within
the valid IP address range to each
Ethernet interface that is used.
4 MultipleArpReplies There are multiple instances of at
least one IP address in the connected
network.
• Make sure that only one instance of
each IP address exists.
5 MultiplePeers No 1-1 connection between first and
second controller.
• Establish a 1-1 connection be -
tween the first and second control -
ler via the SYNC interface.
6 GetPeerRdncyTypeFailed Unable to read the redundancy type
of the BACKUP controller.
• Make sure that there is a 1-1 con -
nection between the first and sec -
ond controller via the SYNC
interface.
• Restart the BACKUP controller.
7 GetPeerRdncyRoleFailed Unable to read the redundancy role
of the BACKUP controller.
• Make sure that there is a 1-1 con -
nection between the first and sec -
ond controller via the SYNC
interface.
• Restart the BACKUP controller.
8 RdncyTypeConflict Both controllers have the same re -
dundancy type.
• Assign redundancy type “First” to
one of the controllers and redun -
dancy type “Second” to the other
controller, see Section 4.11.7.2 .
• Restart the respective controller to
apply the modified setting.
9 RdncyRoleConflict Both controllers have the same re -
dundancy role.
The problem is automatically rectified in
a few minutes.
10 DifferentPlcTypes The remote controller is not an RFC
4072R controller.
• Replace the remote controller with
an RFC 4072R controller.
11 DifferentFirmwareVersions Different firmware versions are in -
stalled on the controllers.
• Make sure that the same firmware
version is installed on both control -
lers.