Open

Installation Manual | IM-20210309-TP-07 iProtect Access / Security | Integrations | Intrusion Detection |

Open

This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.

1 Introduction

1.1 This document

This document describes the link between an Alpha-ML/XL intrusion panel and iProtect™.
Before getting started, please read the installation manual of the intrusion panel carefully.

1.2 Required versions

The table below shows the necessary software and hardware which is needed:

2 Configuring the Alpha-ML/XL

2.1 Standard configuration

The configuration of the panel like intrusion detection zone’ s and area’ s should be done locally in the intrusion panel.

2.2 Settings in the Alpha-ML/XL intrusion panel

Provide the intrusion panel of the following settings (by using the AlphaTool):

• Go to IP settings and enter the following settings:

• Generic interface menu:
  Generic interface: Full encryption
  Transport protocol: UDP
  Encryption key: as desired
  Local port: 6502
  Refresh rate: 3

• Save and send this data to the intrusion panel

3 Network settings

When connecting the intrusion panel into the network and link the panel with iProtect™ Aurora, the following network ports are being used:

*Depends on hardware version
**Depending of the port setup. See chapter 2.2

4 Settings in iProtect

4.1 Add line

• Click in iProtect on the menu item Installation | Hardware | Line.

• Right-click in the browse window and select ‘Add line’. The detail window opens.

• Enter these data:
  Name: Type a logical name
  Type: ‘server’
  Active: (check)
  Active with node’ s: (check)
  Mode: ‘Virtual line’

• Save the data.

4.2 Add node

• Right-click on the virtual line that just is made and select Add node.

• Enter the following data:
  Name: Enter a logic name
  Type: ‘General intrusion’
  Driver name: ‘Alphavision API driver’
  Manager code: the manager code of the panel.
  Encryption key: Enter the encryption key which is entered or used in chapter 2.2
  Active: (check)
  Port: Enter the local port number (6502) of the intrusion panel, see chapter 2.2.
  IP-addres: enter the IP-address of the intrusion panel

• Save the data.

• After a successful connection press on the field Read-in for taking over the programmed configuration from the Alpha-ML panel (groups and points). When the read-in starts or stops, an event will be generated.

4.3 Add alarm group

Normally alarm groups are added automatically when the read-in button is pressed. If desired it is also possible to add alarmgroups manually.

• Right-click on the General intrusion node that just is made and select add alarm group

• Enter the following data:
  Name: Enter a logical name (same name as the intrusion area in the panel)
  No. at the line: The number of the intrusion area
  Alarm group mode: Select ‘Disarm’
  Point changes when group off: Select a time zone (example: Office)
  < In other words, during which time zone must iProtect monitor the alarm points
  for e.g. displaying these statuses on the Keymap™>
  Write point events to database: Select a time zone (example: Office)
  < In other words, during which time zone must iProtect register the alarm points
  for e.g. logging these statuses as event and triggering procedures>

• Save the record

4.4 Add alarm point

Normally alarm points are added automatically with the read in button. If desired it is also possible to add alarm points manually.

• Open the Alarm group that just is made and right click on Alarm point list, select add alarm point.

• Enter the following data:
  Name: Enter a logical name (same name as the intrusion zone in the panel)
  Omit: ‘off’
  Addr. No.: The number of the intrusion zone.

• Enter Save the record.

5 Visualisation in Keymap

5.1 Placing Widgets for visualization and control

• Create under General | Settings | Keymap a floor plan / Keymap™.

• Click in the frame of the detail window and load a picture of the building or from a floor where detectors are installed. Save the record. The image will now be displayed as a background image for the alarm visualization.

• In the tree view underneath the new record of the floor map the record “Widget positioning” has appeared. Click on this record. The detail window ‘Widget positioning’ opens.

• By means of Widgets you can now display each sort status of each / each alarm point. Repeat for each Widget the next steps:

1. Right-click on the background image and choose ‘Security message (third party)’.
   Choose ‘alarm point’ and then the sort status, which you want to have displayed.
   See for this the next chapter about ‘alarm point statuses’.

2. The default symbol for the momentary status of a default alarm point appears.
   Drag with the mouse the Widget on the desired place and set the size of the
   Widget.

3. Click on the tab sheet ‘Widget control’. Select at ‘column value’ the alarm point, of
   which the status has to be shown. – You can adapt at ‘column name’ the status
   once more (you see here a bigger number statuses and parameters from which you
   can choose). On top of this on the tab sheets you can set or determine the size and
   position of the Widget exactly, that the status is not displayed with a symbol, but
   textual.

• You can set comparable statuses of alarm groups.

• Which default symbols represents which value of a alarm point or alarm group status,
  can you view at General | Settings | Keymap | Icon assignment.

• Open at General | Overviews the new floor map. Check whether changes at the detectors are shown in the right way.

5.2 Alarm point status

You can have 3 sorts status of an alarm point (detector) shown:

• Physical status (or ‘point status’ in the detail window of the alarm point)

• Logical status

• Calculating status (or ‘alarm status’ in the detail window of the alarm point)

5.2.1 Physical status

The physical status can be separated thus into 3 groups:

• Extreme resistance values which can only be explained by sabotage of the detector (‘Sabotage closed’/‘Sabotage opened’), this alarm situation will be notified with the highest priority – independent of e.g. the detector operation

• Unusual resistance values which cannot be explained by normal detector operation and e.g. can hint on cable contact (‘Low resistance’/‘High resistance’)

• Resistance values, which the detector can assume at regular function (‘Normal’/ ‘Open’)

5.2.2 Logical status

The logical status is a first interpretation of the resistance value based on the sort detector and entered parameters (e.g. ‘bypassed’ on ‘yes’):

• Idle: the detector does not notice an insecure situation

• Active: the detector notices an insecure situation, but his alarm group does not stand on ‘armed’

• Alarm: the detector notices an insecure situation and his alarm group stands on ‘armed’

• Bypassed: the messages of this detector will be ignored by the system

• Sabotage: e.g. someone opens the housing of the detector without permission

• Local alarm

• Hold-up alarm

• Unknown

5.2.3 Calculated status

The calculated status is a combination of the logical status of the detector and the en de arming of the alarm group of the alarm point:

• Idle: the alarm group of the alarm point is not standing anymore on “armed’ and the alarm point does not send an alarm message

• Activated: the alarm group of the alarm point stands on “armed’ and the alarm point sends no alarm message

• Active: the alarm group of the alarm point does not stand on ‘armed’, the alarm point has passed an alarm message and the alarm group has not been reset

• Alarm: the alarm group of the alarm point stands on armed’, the alarm point has passed an alarm message and the alarm group has not been reset

• Bypassed: the alarm group of the alarm point stands on ‘bypassed’

6 General

6.1 Maximum number of items in iProtect

6.2 Intrusion events in iProtect

Within iProtect the next event types can appear regarding the intrusion detection panel

• Alarm point: Status changed

• Alarm point: Bypass status changed

• Alarm point: Mode changed

• Alarm group: Status changed

• Alarm group: Mode changed

• Alarm group: Alarm changed

• Security device message

• Read-in event