| Alarm message | How to respond |
|---|---|
| Configuration Alarm message: Unable to receive packet from COM port (Unable to receive packet from COM port) |
If you are using a Digi device, there may be a physical device issue. Try swapping equipment to test the following:
|
| Communication Alarm message: Unable to receive packet from COM port (some bytes missing) (Unable to receive packet from COM port(some bytes missing)). | If you are using a vNet device, viewLinc may not detect a data logger attached to it. Check for loose connections, or remove the data logger from the vNet and inspect for broken or bent PINS. If the issue continues, try swapping the data logger or vNet to determine which piece is not functioning. |
| Configuration Alarm message: Sensor failure (Sensor failure). |
HMT140 or RFL100 data loggers: If your device is using an HMP110 probe, it could indicate damage to the probe or the device. We would recommend first powering down the device, then disconnecting the probe to inspect for damage. If the problem continues after reconnecting the probe, try swapping with another functioning probe (to see if the problem follows the probe, or stays with the device). |
| Database Validation Alarm message Database validation failed (Database validation failed). |
If an external application has corrupted any viewLinc files, or has broken the digital locks on the files, viewLinc will attempt to correct the corruption and trigger this alarm. Severe enough corruption could cause viewLinc not to start up, and you should restore the system from a known working and tested backup. Possible software suspects include anti-virus, security or backup applications. Contact your IT team to identify processes that preceded the alarm. |
| Configuration Alarm message: Data sample inconsistency (Data sample inconsistency). | Discrepancy between real-time and historical samples on a device. Check cables, low batteries, or malfunctioning data logger. Make sure that timebase synchronization is enabled (System Preferences), or clear the device (). |
| Historical Data Alarm message: Delayed historical data (Historical data is delayed). |
The delayed historical data alarm indicates that the device is still communicating with the viewLinc server, but it will take some time before the system processes the previously generated data and catches up with the real-time data. RFL100 data logger: This is a normal alarm when first setting up RFL devices, and could last 24 hours or more. If it continues beyond that, this could indicate a wireless issue with the RFL connecting to the AP10. Try moving the RFL100 closer to the AP10. HMT140 data logger: The wireless connectivity may be weak or there is congestion on your network. If the alarm persists, try using the HMT140 Utility software to identify the problem when the device is in an alarm state. |
| Historical Data Alarm message: Unrecoverable historical data (Historical data is unrecoverable). |
The unrecoverable historical data alarm indicates that the system didn’t receive or was unable to process all of the historical data because it is missing or doesn't exist. The system now considers the data as unrecoverable. |
| Failure to generate a report or report generation aborted | Review the number of reports in the queue. Very large reports or excess report generation may slow down performance. Refer to the viewLinc Datasheet for system performance specifications. |
| System running slow | Check for unacknowledged alarms. Removing the acknowledgment requirement can stop the build-up of alarm notifications from re-occurring. |
| Provisional alarm message: (Provisional: Threshold Alarm). |
After the system receives the missing data, the provisional alarm will either:
Provisional alarms are intended as proactive warnings to viewLinc users. Instead of waiting for confirmation of an alarm condition, which could be delayed by a communication problem, users can take action to immediately to check their physical setup for issues. |