Rus |
---|
For the Access Control and Detection Tools alarm groups, by default no data is sent from Agent of Control. These alarm groups, as well as Hardware and Fire/Security System, can be used for designating their respective alarm types.
To classify events of an object as belonging to a particular alarm group, create an object (if it does not exist already) in the device tree. For example, if you want for the signal from the Abandoned Object Detection Tool to be displayed in Monitoring in the Detection Tools alarm group, create a Detector Zone object and configure it (select the Abandoned Object Detection Tool type, specify the detection area and sensitivity, etc.; for more details, see the document Intellect Software Package: Administrator's Guide.
To associate various events with particular alarm groups:
It is possible to get confirmation of alarm acceptance from the Server of Control. Select the type of confirmation in the Confirmation dropdown list (5):
The Agent of Control sends the "Confirmed: Monitoring event" message to Intellect core when there is the confirmation of alarm acceptance on the Server of Control. Scripts that use this event can be created in Intellect – see Sample scripts for processing alarm confirmations. |
Confirmation sending can be disabled on the side of the Server of Control – see Sending confirmations of alarm acceptance. |
If the object identifier (2) is not specified, the following variables can be used in the Message field to detail the message:
<id> – identifier of the object from which the event came.
<name> – the object name.
<id> and <name> are to be in lower case. After substitution of variables values the message must not be longer than 40 characters. If the resulting message is longer, extra characters will be dropped. |
When the Disarmed event appears at the Camera 1, the “Camera [1] disarmed” message is sent.![]() |
This means that when integrating a new device into Intellect, if a developer wants to be able to send more detailed information to Monitoring, when generating an event from the device, the developer should add detail in the param0<> parameter. For example, if there is a Motherboard Control module that has the Alarm event, the following values could be included in param0<>: "processor cooler", "BIOS battery", etc. If you enter "Motherboard" in the Message field and select Capture detailed data, the following text may appear in the Device column of the Alarm Reaction dialog form: "Motherboard (CPU cooler)".
Example of how to configure the message for the Abandoned Object Detection Tool.
In the example shown with the Abandoned Object Detection Tool, when the detection tool is triggered a indicator corresponding to the Detection Tools alarm group becomes red in the Control Panel.
Click this indicator to view the Alarm Reaction window, which indicates that the Abandoned Object Detection Tool has been triggered.
Similarly, it is possible to monitor messages from other objects created in the Intellect device tree, on the Hardware tab.
Configuration for associating different events with certain alarm groups is now complete.