Allen-Bradley 1756-CNB/E, Руководство пользователя

Страница: 113 / 186

Publication 1756-UM523F-EN-P - December 2006
Maintain and Troubleshoot the System 113
Interpret SRM events
Use this table to interpret events recorded in the SRM’s event log.
SRM Event Descriptions
Event Description Meaning
Autoqualification Trigger Something happened that caused the system to try and synchronize again. Double-click the
event to see what happened.
Blank Memories Rule A check to choose a primary chassis if both chassis power up at the same time. Suppose
that the controllers in one chassis don't have projects while the controllers in the other
chassis do have projects. In that case, the other chassis becomes primary.
Chassis Modules Rule A check to choose a primary chassis if both chassis power up at the same time. Suppose
that one chassis has more modules than the other chassis. In that case, the chassis with
the most modules gets the first chance to become primary. It becomes primary as long as
the other chassis isn't more able to control the system.
Chassis Redundancy State changed to… The chassis changed to a different redundancy state.
•
PwQS — Primary with qualified (synchronized) secondary partner
•
QSwP — Qualified (synchronized) secondary with primary partner
•
DSwP — Disqualified secondary with primary partner
•
DSwNP — Disqualified secondary with no partner
•
PwDS — Primary with disqualified secondary partner
•
PwNS — Primary with no secondary partner
•
PLU — Primary locked for update
•
SLU — Secondary locked for update
Crossloading Error A module isn't able to get some information to its partner.
Disqualified Secondaries Rule A check to choose a primary chassis if both chassis power up at the same time. Suppose
that the modules in one of the chassis powered down in a disqualified secondary state. In
that case, the other chassis becomes primary.
Failed Modules Rule A check to choose a primary chassis if both chassis power up at the same time. Suppose
that a module in one of the chassis is faulted but its partner module in the other chassis is
not faulted. In that case, the other chassis becomes primary.
Firmware Error The SRM has a problem.
Improper Mode or Keyswitch Position A lock for update cannot be performed if the primary controller is faulted. A lock for update
or locked switchover cannot be performed if the keyswitch on either controller is not in the
REM position.
Incompatible Application A lock for update cannot be performed if the project names or applications are not identical
in the primary and secondary chassis.
Invalid Application A lock for update cannot be performed if test edits or SFC forces exist in the application.
Module Insertion The SRM now sees the module on the backplane. This means the module has either just
powered up, just been put into the chassis, or just finished resetting. Double click the event
to see the slot number of the module.
Module Rejected Lock for Update Command
from SRM A module (with a slot number specified in byte 0 of the extended status) rejected the
lock-for-update command. See events from that module to determine the cause.