System redundancy error codes
Available from 2022.0 LTS with RFC 4072R
The most recent status or error message is indicated as a digit, visible in the PLCnext Engineer at the RDNCY_ERROR system variable.
This is how to decode and handle the messages:
|
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 interfaces. |
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-to-1 connection between first and second controller. |
Establish a 1-to-1 connection between the first and second controller via the |
|
6 |
GetPeerRdncyTypeFailed |
Unable to read the redundancy type of the BACKUP controller. |
Make sure that there is a 1-to-1 connection between the first and second controller via the Restart the BACKUP controller. |
|
7 |
GetPeerRdncyRoleFailed |
Unable to read the redundancy role of the BACKUP controller. |
Make sure that there is a 1-to-1 connection between the first and second controller via the Restart the BACKUP controller. |
|
8 |
RdncyTypeConflict |
Both controllers have the same redundancy type. |
Assign redundancy type “First” to one of the controllers and redundancy type “Second” to the other controller (see IP settings for redundancy operation). Then restart the respective controller to apply the modified setting. |
|
9 |
RdncyRoleConflict |
Both controllers have the same redundancy 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 installed on the controllers. |
Make sure that the same firmware version is installed on both controllers. |
|
12 |
SetUserConfigFailed |
An error occurred when synchronizing the user roles. |
Make sure that there is a 1-to-1 connection between the first and second controller via the |
|
13 |
SetPnNameFailed |
During synchronization, an error occurred on the BACKUP controller when setting the PROFINET name. |
Make sure that there is a 1-to-1 connection between the first and second controller via the |
|
14 |
GetIpConfigFailed |
An invalid IP address configuration was reported by the BACKUP controller. |
Restart the BACKUP controller. If the message occurs again, contact Phoenix Contact. |
|
15 |
SetIpConfigFailed |
During synchronization, an error occurred on the BACKUP controller when setting the IP address configuration. |
Make sure that there is a 1-to-1 connection between the first and second controller via the |
|
16 |
CheckRoleTimeout |
Timeout when checking the redundancy roles. |
Make sure that the remote controller is fully initialized. |
|
17 |
ChangeRoleTimeout |
Timeout when changing the redundancy roles. |
Make sure that the BACKUP controller is fully initialized after it has been restarted. |
|
18 |
GetInfoTimeout |
Data exchange timeout during initialization of the redundant control system. |
Make sure that there is a 1-to-1 connection between the first and second controller via the |
|
19 |
BasicSyncDoneTimeout |
Timeout when switching to |
Make sure that there is a 1-to-1 connection between the first and second controller via the |
|
20 |
TransferApplicationFailed |
Error during synchronization: An error occurred when transferring the PLCnext application to the BACKUP controller. |
Make sure that there is a 1-to-1 connection between the first and second controller via the |
|
21 |
StartBackupPlcFailed |
An error occurred when starting the BACKUP controller. |
Make sure that there is a 1-to-1 connection between the first and second controller via the If the message occurs again, contact Phoenix Contact. |
|
22 |
StopBackupPlcFailed |
BACKUP controller: An error occurred when switching to the STOP operating mode. |
Make sure that there is a 1-to-1 connection between the first and second controller via the If the message occurs again, contact Phoenix Contact. |
|
23 |
ResetBackupPlcFailed |
BACKUP controller: An error occurred when resetting the controller. |
Make sure that there is a 1-to-1 connection between the first and second controller via the If the message occurs again, contact Phoenix Contact. |
|
127 |
UnspecifiedError |
An unknown error has occurred. |
Restart the affected controller. If the message occurs again, contact Phoenix Contact. |