Micromod MOD: 1800P - MOD 30ML Identity Module (Version 2) System, I/O and Communications Functions - Manual (Page 57)

Logic Functions - Book 1
SYSTEM EVENT BLOCK
3-31
Figure 3-9. System Event Block (SE), Alarms Menu
3.4.1 System Event Block Operation
System events are handled in the following way:
•
When an event is generated, an entry corresponding to that event is stored in the
circular buffer (the size of this system event queue is configurable), and the queue
entry ID (QID) attribute in the system event block is incremented.
•
Whenever the QID attribute value changes, the interface software should request new
information from the circular buffer. The interface software may maintain a circular
buffer of its own size, with its own local rules about display and acknowledge.
•
Most events, including those indicating hardware faults, are processed by database
blocks.
•
Any block that generates a diagnostic event may have an attribute for suppression of
that event. In addition, attributes for suppression of groups of diagnostic events are
provided by the system event block. Some diagnostic errors in a database block have
counter attributes that are incremented with each occurrence of the error condition
even when the events are suppressed. These events have addressable attributes in
the block.
•
Event entries are stored in the circular buffer at 10 bytes each, where each entry is
broken down as to block type, block occurrence, event code, event transition, date,
and time. See Section 3.4.4 for a listing of suggested text related to system event
codes and Section 3.4.5 for transitions. See the appropriate block type for event
codes and messages for that block. Each system event code (0 to 255) or diagnostic
event code (4 to 127) describes a particular event which is translated into a text
message or logged through the appropriate interface software.