Spider DSA User’s Manual
325
Automated Alarm Limit Test
The Automated Alarm Limit test function allows the Spider front-end to conduct
automated limit checking for time or frequency signals. The function is supported
in both PC-tethered mode and Black Box mode.
The Spider compares the limits to the live measured signal in real-time, after
every single frame of measurement. If the limits are exceeded, the Spider takes
the appropriate actions based on the user setup.
Limiting signals are created and edited using EDM on the host PC. There are four
elements in a limiting test: the signals being tested, upper or lower limits applied,
testing schedule and testing log. In most cases it will be easy to generate
automated alarm responses when the limits are exceeded. Alarm responses
include sending email notifications, beeping, screen flashing and controlling the
current test.
In every type of test, limits can be bound to time stream signals, block signals and
spectrum signals. Users can define a high limit and a low limit. When a live signal
exceeds a limit, a predefined event will be triggered as an alarm. Each limit line
can have up to 64 segments and there can be a maximum of 64 limit signals.
A testing schedule is used to automatically control the limit checking test. The
testing schedule defines various operations to automate the process. For example,
the testing schedule can tell the instrument when the limit checking will be turned
on, when it will be turned off and for how long the test will be conducted.
To record the events of the test, a Testing Log and a summary report are needed.
The Testing Log records the important events in chronological order, including
whether the limits have been exceeded. The Summary Report provides the status
of the limiting checks since the beginning of the test.
When the limit signal is exceeded, a user defined limit alarm event will be
triggered. These can include audible beeps, signal saves, send email messages etc.
To summarize: An automated limit checking test requires the following building
blocks:
◼ At least one test signal
◼ At least one limit signal applied to the measured signals
◼ A testing schedule
◼ A testing log and summary report
◼ A setup for the limit alarm events
To Next Page
Loading...