40 S&C Instruction Sheet 1043-550
Each historic event message consists of these components, all having a corresponding
column in the Event View table:
Category
Each historic logging event, generated by the UIM, is assigned to one category by S&C,
based on what part of application’s functionality it belongs to. This is done to ease filtering
and sorting, as well as allow viewing only events of desired categories on these screens.
The currently supported categories are:
ITII
Events related to IntelliTEAM II team maintenance and transfer activity
UIM
Events related to the interaction with Host Device
DNP
Events specific to DNP communications, both between IntelliTEAM II team
members and UIM to External Device
LOG
Events generated by Data Logging itself, for instance Compact Flash-related
Event Description
There are a fixed number of historic logging events in each category, each generated in
certain cases. This column succinctly summarizes what the event is. The list of all pos-
sible events is below.
Timestamp
Specifies when the historic event occurred, with millisecond precision. Note that this time
is set based on the control’s clock, not your PC’s. Also, clocks on different controls are
not automatically synchronized, so events that occurred on different controls at the same
time might still have different timestamps. If you want to chronologically sort events that
occurred on different controls, you first need to manually synchronize all control clocks,
either through SCADA or the External Device Menu / SETUP: Miscellaneous screen. You
can also synchronize a control with the clock in your PC computer, or manually set the
time using IntelliLINK. Go to Tools > Set Control Clock on the IntelliLINK screen menu.
Events in the Event View are always sorted by timestamp in the ascending order (older
to newer). However, because the View is circular when in Real-Time mode, the oldest
event is usually not on top but rather drifts down as newer events continuously overwrite
older ones.
Data1—Data 4
Many events have, together with the timestamp and the description, some numerical data
associated with them. For example, if a switch was successfully closed in the course of
IntelliTEAM transfer activity, the number of the team for which transfer took place, is sup-
plied in the Data 1 column. There are up to 4 such pieces of data that can potentially come
with an event, each placed in one of these 4 columns, always starting with Data1.
Some event messages contain text in parenthesis, which summarizes the meaning of the
associated DataX columns, such as: “Transfer Approved (team, code)”. This notation
means that Data 1 is the team number, Data 2 is approval code and Data 3/Data 4 are either
unused or contain solely tracing information. Other event messages have supplementary
data codes that are solely documented below.
Data Logging
