Device configuration alarms, System alarms, What happens when an alarm is triggered – Vaisala viewLinc 4.3 User Manual
Page 123: Calibration, System alarms)
About Alarms
viewLinc 4.3
4
|
4
115
Device Configuration Alarms
If you receive a Configuration Alarm, this indicates that your Device has
stopped recording data history or was configured incorrectly.
This could be the result of:
•
Device settings set to stop when full.
•
A delayed start (as set on a Vaisala Veriteq Logger).
•
An internal Device error.
•
A Channel has been disabled in the Device, manually or with the
Device configuration software.
Note: You can verify or modify the Vaisala Veriteq Device settings
using vLog or HMT140 Utility software; however, if the problem
persists, contact your Vaisala technical support representative.
The default delay for most configuration alarms is 60 seconds (this delay
can be modified in viewLinc). However there is no delay for certain
alarm types such as missing Channel Alarms, configuration changes and
probe changes (cannot be changed).
System Alarms
If your system uses VL-type data loggers (on a validated system), you
may receive these alarms:
•
Device Validation Alarms: Sent if the validation memory in the
Device is corrupted or has been modified. Contact your Vaisala tech-
nical support representative for assistance.
•
Device Calibration Alarms: An intermittent notification sent
when your Device is due for calibration. You receive notifications at
the following intervals: 3 months and 1 month before the cal-
ibration due date, then again on the data logger’s scheduled recal-
ibration date. This alarm remains active until the Device is
What Happens When an Alarm is Triggered?
When an alarm is triggered, several things can happen, depending on
your system configuration settings: