5 |
Error |
|
|
|
|
|
|
|
|
|
|
|
Code |
|
| Message |
| Fault Description |
|
| Corrective Action | |||
9 |
| Primary and Secondary | The local unit cannot be placed in RUN |
| Modify the configuration or terminate | ||||||
|
| Units are Incompatible | mode when its redundancy configuration is |
| the C debugger session. | ||||||
|
|
|
|
|
|
| incompatible with the remote unit. This |
|
|
| |
|
|
|
|
|
|
| error is logged when (1) Store of an |
|
|
| |
|
|
|
|
|
|
| incompatible configuration is attempted and |
|
|
| |
|
|
|
|
|
|
| (2) attempting to synchronize with an |
|
|
| |
|
|
|
|
|
|
| incompatible configuration. This error is |
|
|
| |
|
|
|
|
|
|
| also logged when the local unit and/or the |
|
|
| |
|
|
|
|
|
|
| remote unit has a C debugger session active |
|
|
| |
|
|
|
|
|
|
| and the units are attempting to synchronize. |
|
|
| |
|
|
|
|
|
|
|
|
|
|
| |
10 |
| CPU to CPU |
| Synchronization protocol has been violated. |
| If this fault is also accompanied by an | |||||
|
| communications |
|
|
|
| RCM failed fault, replace the failed RCM: | ||||
|
| terminated |
|
|
|
| otherwise power cycle the CPU or CPUs. | ||||
11 |
| Redundant Link has timed | The RCM has timed out while waiting on |
| Power cycle the | ||||||
|
| out |
|
|
|
| communications from the other unit. |
| controlling the process); increase the fail | ||
|
|
|
|
|
|
|
|
|
| wait time. | |
12 |
| Units Are Not Fully | Due to actions taken by the user, the two |
| Enable the data transfer copy on the | ||||||
|
| Synchronized |
| units in a CPU redundant system are not |
| backup unit | |||||
|
|
|
|
|
|
| fully synchronized. This means the backup |
|
|
| |
|
|
|
|
|
|
| unit is not executing with the same inputs |
|
|
| |
|
|
|
|
|
|
| and/or outputs as the active unit while the |
|
|
| |
|
|
|
|
|
|
| units are synchronized due to data transfers |
|
|
| |
|
|
|
|
|
|
| being disabled. |
|
|
| |
|
|
|
|
|
|
|
|
|
| ||
>12 |
| CPU Redundancy Status | A change in the status of the system has |
| Corrective action to be taken depends on | ||||||
|
| has Changed |
| occurred. |
|
| the error code. | ||||
|
|
|
|
|
|
|
|
|
| ||
|
|
|
| The following table lists messages, descriptions, and corrective actions for error codes associated | |||||||
|
|
|
| with redundancy in other fault groups. |
|
| |||||
|
|
|
|
|
|
|
|
|
| ||
Group |
| Error |
|
|
|
|
|
|
| ||
|
|
|
| Code |
| Message | Fault Description |
| Corrective Action | ||
Loss of |
|
| 57 |
| Redundant link hard | The RCM has been faulted due to an | Power cycle the rack with the | ||||
Option |
|
|
|
| failure occurred. | error while accessing memory. |
| faulted RCM. If the RCM's | |||
Module |
|
|
|
|
|
|
|
|
| BOARD OK LED is on, replace | |
|
|
|
|
|
|
|
|
|
|
| the cable between the RCM and |
|
|
|
|
|
|
|
|
|
|
| the BTM. If the RCM's BOARD |
|
|
|
|
|
|
|
|
|
|
| OK LED is off, replace the RCM. |
|
|
|
|
|
|
| |||||
PLC Software |
| 148 |
| Units contain | The firmware in the redundant CPUs | Upgrade the CPUs so that they | |||||
|
|
|
|
|
| mismatched firmware; | has different revision levels. Having | have the same revision of | |||
|
|
|
|
|
| update recommended. | different revisions of firmware in the | firmware according to the | |||
|
|
|
|
|
|
|
| CPUs is intended for |
| firmware upgrade procedure. | |
|
|
|
|
|
|
|
| synchronization only as some change in |
| ||
|
|
|
|
|
|
|
| the behavior of the system may be |
| ||
|
|
|
|
|
|
|
| experienced when mixing revisions. |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
Series |