Appendix F Diagnostic Events - Ametek DMS-3K Installation & Operation Manual

Appendix F Diagnostic Events

The following diagnostic events could be reported in the Event Log.
M = Master
S = Slave
Unit Diagnostic Events
Configuration Related Events
M/S Configuration Changed via WEB
M/S Configuration Changed via File Restore
M/S Enabled Alarm Input via WEB Page
M/S Disabled Alarm Input via WEB Page
System Operational Events
M/S Alarm Acknowledged
M Remote Alarm Acknowledged
S Alarm Acknowledged at Remote Master
M/S Restored to Scan
M/S Off Scan
M/S SER Buffer Overflow
M/S Lost a maximum of
Power Related Events
M/S Main Board Power On
M/S Power Loss / Reboot
M/S Power Restored / Reboot Complete
Combined SER (CR) Events
M Connected to Remote Device at
M Disconnected from Remote Device at
M Slave at Station ID no longer responding
S Master Combined SER at Station ID Disconnected Slave unit identifying that it is no longer connected to a
S Master Combined SER at Station ID Connected
M Alarm Out of Sync Forced ON
M Alarm Out of Sync Forced OFF
Page 185
(Descriptor 'D')
X events.
Station ID
Station ID
Description
Alarm Inputs/Outputs configuration Change
Alarm Inputs/Outputs configuration Change by importing a
configuration file via the web page Restore feature
Alarm manually enabled via configuration
Alarm manually disabled via configuration
Alarm Acknowledged via the browser at the same unit
Alarm Acknowledged at the Master browser for a Slave unit
Alarm Acknowledged at the Master browser for a Slave unit
Auto Delete from scan de-activated for a repetitive alarm
Auto Delete from Scan activated for a repetitive alarm
The number of alarms received exceeded the capability of
the unit
80 events/sec x 35 inputs for several minutes
This event may occur in conjunction with an "SER Buffer
Overflow" event. An attempt is made to recover the lost
event(s).
Unit powered up or configuration just performed which
took the system off line
Loss of power or unit powered down automatically during a
firmware upgrade
Power restored or unit powered up automatically during a
firmware upgrade
Master unit connected to Slave unit (occurs during initial
set-up)
Master unit manually disconnected from Slave unit
Master unit no longer communicating to the Slave
Master
Slave unit identifying that it has been connected to a
Master
When a Master Reconnects to a Slave, any existing Slave
alarms are treated at the Master as new alarms
When a Master disconnects from a Slave, any existing Slave
alarms at the Master are automatically returned to normal
Appendix H