GE Industrial Solutions Entellisys System User Manual - Manual (Page 225)

Alarms and events description and system troubleshooting guide 225
A
Invalid Setting ST From CPUB
Change Rejected Messenger has received an invalid short time
enable or disable setting from CPU B and has
rejected the value This event is recorded by CPU A based on
status information sent to the Messenger by
CPU B. The Sequence of Events for CPU B
should have an “Invalid Setting ST Change
Rejected” or “Invalid Setting ST Pickup
Change Rejected” event. See the description
of those events for details.
Invalid Setting GF From CPUA
Change Rejected Messenger has received an invalid ground
fault enable or disable setting from CPU A
and has rejected the value This event is recorded by CPU B based on
status information sent to the Messenger by
CPU A. The Sequence of Events for CPU A
should have an “Invalid Setting GF Change
Rejected” or “Invalid Setting GF Pickup
Change Rejected” event. See the description
of those events for details.
Invalid Setting GF From CPUB
Change Rejected Messenger has received an invalid ground
fault enable or disable setting from CPU B
and has rejected the value This event is recorded by CPU A based on
status information sent to the Messenger by
CPU B. The Sequence of Events for CPU B
should have an “Invalid Setting GF Change
Rejected” or “Invalid Setting GF Pickup
Change Rejected” event. See the description
of those events for details.
Note Messngr Ignored Invalid
Command CPUA Messenger has received an invalid command
from CPU A and will ignore it Contact GE Post Sales Service (see How to
contact us on page 2 ).
Note Messngr Ignored Invalid
Command CPUB Messenger has received an invalid command
from CPU B and will ignore it Contact GE Post Sales Service (see How to
contact us on page 2 ).
Note Messngr Arbitrated
Command From CPUA Messenger has received conflicting
commands from CPU A Examine event logs from both CPUs to
determine if CPUs sent conflicting
commands at approximately the same time.
Note Messngr Arbitrated
Command From CPUB Messenger has received conflicting
commands from CPU B Examine event logs from both CPUs to
determine if CPUs sent conflicting
commands at approximately the same time.
Note Messngr Reports CPUA
Command Timed Out Command sent to Messenger from CPU A has
timed out • Verify that breaker is in the Test or
Connect position.
• If Open command timed out, check shunt
trip fuse.
• If Close command timed out, verify that
breaker is an electric breaker. If it is, verify
that closing spring is charged, also check
the fuse for the charging motor.
• Contact GE Post Sales Service (see How
to contact us on page 2 ).
Note Messngr Reports CPUB
Command Timed Out Command sent to Messenger from CPU B has
timed out Same as CPU A above.
CPUA Synch Clock OK Messenger reports that CPU A is using the
CPU Synch Clock (event recorded by CPU B)
Table A-2 Sequence of events description and troubleshooting guide
Event Description Notes and Troubleshooting tips