User manual

User Manual ADPRO
®
XOa Client Software
114 21796_05_preliminary
Detector type
Detail 1
(alarm type)
Detail 2
(alarm type)
Detail 3
(alarm type)
PRO 50 / PRO-E 50
Left
Centre
Right
PRO 85 / PRO-E 85
PRO 85H / PRO-E 85H
13.6 Arm/Disarm Switch
Events on the server can be classified in the following groups:
 system messages: these are internal events (e.g. hard disk error, power supply fault, communication
error…);
 camera messages (e.g. video signal missing, contrast level too low, motion detected…);
 network inputs: alarm inputs connected to external Net I/O modules
 inputs: alarm inputs connected to the OTB I/O card, accessible at the back of the video system;
 virtual inputs: events detected on interconnected S3100 security panels.
 workbits: calculated bits that provide alarm information. A combination of inputs can trigger a workbit.
Events have to be handled in a different way when the building is left unattended. Therefore, the building has
to be armed. Arming can be done in three ways:
1. automatically according to a schedule;
2. manually, by a user who has to activate a switch;
3. by the CMS, executing the DN command line in Telnet (hint: type HE for syntax help).
To define the behaviour of an alarm input during armed and disarmed state, modify the alarm profile that is
assigned to this input.
Note
It is possible for other software developers to use the SDK (software development kit) in order
to arm/disarm a building.
To define an arm/disarm switch, open System > Behaviour > Input/output behaviour. Select an input from
the list.
Note
You can use only real inputs (USB I/O), network inputs (Net I/O), or workbit inputs.
Apply a filter to reduce the list.