GE Industrial Solutions Entellisys 4.0 System User Manual - Manual (Page 260)

Alarms and events 260
A
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)
CPUB Synch Clock OK Messenger reports that CPU B is using the
CPU Synch Clock (event recorded by CPU A)
Caution CPUA Synch Clock Err
Backup Clock On Messenger reports that CPU A is not using
the CPU Synch Clock (event recorded by CPU
B) Verify that CPU A is connected to the CPU
Synch Clock, verify that the CPU Synch Clock
is operating correctly.
Caution CPUB Synch Clock Err
Backup Clock On Messenger reports that CPU B is not using
the CPU Synch Clock (event recorded by CPU
A) Verify that CPU B is connected to the CPU
Synch Clock, verify that the CPU Synch Clock
is operating correctly.
Messngr Synchronization OK Messenger reports that it has successfully
synchronized to one of the CPUs
Messngr Synch Not Locked Messenger reports that it is not synchronized
to either CPUs It is normal for this to occur during start-up,
or when an Entellisys Messenger is first
plugged in to the system or rebooted. If it
occurs repeatedly during normal operation,
contact GE Post Sales Service (see
How to
contact us on page 2 ).
Time Server Started Logged when CPU switches to server mode
and starts servicing time synchronization
requests
Time Server Stopped Logged when CPU switches to client mode
and starts polling server for current time
Table A-2 Sequence of events description and troubleshooting guide
Event Description Notes and Troubleshooting tips