Chapter 5
Alarms and Events
©
National Instruments Corporation
5-13
month,
DD
is the day,
HH
is the hour,
MM
is the minute and
.evt
is the
extension for all event log files.
There are three steps you must complete to log alarms and events:
1.
Configure your tags to have Log/Print Events enabled. You configure
it on a per tag basis. To select event logging for a single tag, go to the
panel for configuring the tag.
2.
Configure a path to a directory for the event (
.evt
) files. To choose the
path, select Configure»Events… in the Tag Configuration Editor.
3.
Turn on event logging for the BridgeVIEW Engine, according to one
of the techniques outlined below.
There are three techniques for turning event data logging on or off:
•
You can configure event logging in the Tag Configuration Editor.
To turn on event logging, select Configure»Events…. Configure the
path and set Start logging on system start-up to be TRUE.
•
For programmatic control, you can call the Enable Event Logging VI
in the System palette. With this VI, you can turn event logging on or
off dynamically for all the tags in the system, while the BridgeVIEW
Engine is running.
•
The Engine Manager also has a button to turn event logging on or off.
If you have Supervise or higher-level privileges, you can access this
button.
Table 5-2 provides a description of the event logging configuration
selections.
How Do You Print Alarms and Events?
In BridgeVIEW, events are printed to a standard line printer through a
parallel port. There are three steps you must complete to print alarms and
events:
1.
Configure your tags to have Log/Print Events enabled. You configure
it on a per tag basis. To select event printing for a single tag, go to the
panel for configuring the tag.
2.
Configure a printer for event printing. To choose the printer, select
Configure»Events… in the Tag Configuration Editor.
3.
Turn on event printing for the BridgeVIEW Engine, according to one
of the techniques outlined below.
