Filter
Top Products
Reference Manual
00809-0100-4832, Rev AA
October 2004
Rosemount 3095FC
3-34
• Alarm Log: The Alarm Log contains the change in the state of any
alarm signal that has been enabled for alarms. The system Alarm Log
has the capacity to maintain and store up to 240 alarms in a “circular”
log. The Alarm Log has information fields that include time and date
stamp, alarm clear or set indicator, and either the Tag name or a
14-byte detail string in ASCII format.
In addition to providing functionality for appending new alarms to the
log, the Alarm Log allows host packages to request the index of the
most recently logged alarm entry. Alarm Logs are not stored to the flash
ROM during the Save Configuration function in Rosemount User
Interface Software.
The Alarm Log operates in a circular fashion with new entries
overwriting the oldest entry when the buffer is full. The Alarm Log
provides an audit history trail of past alarms. The Alarm Log is stored
separately to prevent recurring alarms from overwriting configuration
audit data.
• Event Log: The Event Log contains changes to any parameter within
the 3095FC made through the protocol. This Event Log also contains
other 3095FC events, such as power cycles, cold starts, and disk
configuration downloads. The Event Log provides an audit history trail
of past operation and changes.
The system Event Log has the capacity to maintain and store up to 240
events in a circular log. The Event Log has information fields that
includes point type, parameter number, time and date stamp, point
number if applicable, the operator identification, and either the
previous, current parameter values, and either the Tag name or a
14-byte detail string in ASCII format.
In addition to providing functionality for appending new events to the
log, the Event Log allows host packages to request the index of the
most recently logged event entry.
Event Logs are not stored to Flash memory when Save Configuration is
issued in Rosemount User Interface Software. The Event Log operates
in a circular fashion with new entries overwriting the oldest entry when
the buffer is full. The Event Log provides an audit trail history of past
operation and changes. The Event Log is stored separately to prevent
recurring alarms from overwriting configuration audit data.