Alarms and Events
Table 16
Event reference, by source and tab.
Source | Event in maintenance, | Cause: an alarm or log entry |
| except where noted | could indicate … |
|
|
|
outside | System: no video recording* | a cut cable, dead camera, power |
world |
| outage |
| Inputs: activate, input ports 1 | security sensor has been triggered or |
| to 16 | the |
| Inputs: deactivate, input | security sensor has been reset or the |
| ports 1 to 16 | unit is booting |
| Video: signal unlock, | cut cable, hardware failure in a Rapid |
| cameras 1 to 16 | Eye Multi |
|
| camera… Can be momentary. |
| Video: lock†, cameras 1 to 16 | a buggy camera; time since video |
|
| unlock helps troubleshooting |
| Motion: Not on Event tab; on |
| the Video tab. |
customer- | user defined: Not on Event |
device | tab; on Serial Devices tab. |
View | Session: connect, reject and |
operator | disconnect |
| Maintenance: changes to |
| configuration, security, time, |
| storage and so on…‡ |
| Outputs: activate, output |
| ports 1 to 8 |
| Outputs: deactivate, output |
| ports 1 to 8 |
| System: no video recording* |
| System: reboot |
System: failure, | |
unit | reboot† |
| System: No video recording* |
| System: time server, |
| no synch, clock drift… |
| System: disk failure |
intruder, a change in lighting, fire, an explosion, vermin, and so on.
transaction made using hardware at a customer’s facility
use/misuse of View to connect to or disconnect from a site. Session rejections can also be watched
use/misuse of maintenance by an operator or Multi SA; for example to monitor Clear storage or Synchronize time by operator of View
use/misuse of an onsite device by a View operator ex.: locking a gate at a site, by remote control
use/misuse of an onsite device by a View operator
ex.: unlocking a gate at a site, by remote control
camera disabled by View operator
use/misuse of Reboot command by operator
power failure or catastrophic failure of unit
failure of unit’s video hardware
failure of network or network’s time server
warning of imminent failure of storage
*Some events are repeated in the table: their source can vary. For example: an alarm triggered by an “outside world” events can also be triggered by rebooting a unit.
† A Multi SA can set a Video lock event to be only logged rather than trigger an alarm.
‡ Some configuration settings can be changed onsite, using LocalView. These changes are not logged nor do they trigger an alarm when the configuration event is set tot do so.
