Device alarm templates are automatically applied to each monitoring device connected to the viewLinc Enterprise Server (data loggers and transmitters). Host alarm templates are applied to hosts (Device Host computers and access points).
Device alarm templates contain default (and modifiable) settings which define:
- Alarm priority
- Alarm notification delay
- Acknowledgment requirements
- Group authorized to modify device alarm settings
You can modify the default device and host alarm templates. You can also create new alarm templates with unique settings for specific Locations.
- Device or host communication alarms (Default Communication Alarm)
-
Device communication alarms occur when communication is interrupted between a host computer, access point or viewLinc Enterprise Server, and its connected devices.
Host Communication Alarms occur when a device host or access point loses its connection to the viewLinc Enterprise Server. Communication alarms are like a system health test, alerting you if there is a problem that might disrupt viewLinc monitoring and alarming.
By default, there is one communication alarm template preconfigured for each host and each device. Communication alarm templates control:
- How alarm notification displays
- Who is notified
- When alarm notification is initiated
- Whether alarm acknowledgment is required
If a device host computer or access point host goes offline, the system generates a host communication alarm only. Connected devices do not generate device communication alarms.
- Device or host configuration alarms (Default Device/Host Configuration Alarm)
-
If you receive a device configuration alarm , this indicates that your device is configured incorrectly or has stopped recording data history. Host configuration alarms are triggered when there is a synchronization error between a host and its connected devices.
Here are a few examples:
- An internal device error is preventing data history from recording.
- viewLinc detects a device's stop mode is not set to Wrap when full (DL data loggers).
- viewLinc cannot retrieve historical samples because a device is configured with a delayed data recording start (DL data loggers).
- viewLinc detects a device that is locked to another system.
- A device may have a disabled channel that is linked to Location.
- There is a problem with the HMT140, causing it to send too many transmissions which may drain the battery.
The default delay before viewLinc sends a device configuration alarm notification is 60 seconds. You can adjust the notification delay and other device configuration settings in viewLinc.
- Device validation alarms (Default Device Validation Alarm)
-
If the validation memory in a device is corrupted or has been modified, this alarm notification will advise that you contact your Vaisala technical support representative for assistance.
- Device calibration alarms (Default Device Calibration Alarm)
-
A device calibration alarm is an intermittent notification sent when a Vaisala data logger or probe is due for calibration.
By default, you receive notifications at the following intervals: 3 months and 1 month before the calibration due date, then again on the scheduled recalibration date (auto-generated for 1 year from last calibration date). This alarm remains active, even after acknowledgment, until the device is recalibrated (for more information contact Vaisala Calibration Service Center).
You can set the default calibration duration for all data loggers in System Preferences, or, if you have Manage Devices right, modify the calibration duration for a specific data logger or probe in Sites Manager.
- Historical data alarms (Default Historical Data Alarm)
- An historical data alarm is a notification send when there is communication between the host and device(s), but the historical data has either fallen behind or is unrecoverable.