EN

EN

Installation and Configuration

AEOS - Intrusion
Version 21 | 21-09-2022
Installation and Configuration | AEOS - Intrusion EN

Date Version Changes

Added Detector test and Detector input test to the

21-09-2022 21
Intrusion terminal Configuration menu
21-07-2022 20 Updated screenshots for Detector AEbc properties
12-07-2022 19 Removed references to calculation sheets.
04-07-2022 18 Added Menu Detector test Timeout to Intrusion Terminal properties
16-06-2022 17 Added Masking reset output to Detector AEbc properties.
19-10-2021 16 Removed all references to AEOS Intrusion Stand alone.
09-03-2021 15 Added new default value for dialer property 'listen to all areas'.
27-01-2021 14 Removed RemoteLogbook AEbc reference
21-01-2021 13 Minor corrections
04-06-2020 12 Minor correction
23-10-2017 11 Lay-out
Added procedure when detector is overruled and after that inhibited – uninhibited
29-08-2017 10
(chapter 20.6)
09-12-2015 9 Iris 640NG added as dialler (successor of Iris 640)
23-09-2015 8 New functionality: Monitor centre accounts
12-12-2014 7 Updated for AP3006 (PMS D) with two RS485 channels
Updated to AEOS 3.1.1. New functionality: Installer login changed, scrolling
information on Terminal changed to full screen info, for each alarm date and time
01-07-2014 6 added, new detector type added, detector delay added, simplified arm/disarm
menu, first/last detector, follower zones, logging to ARC extended, silent mode for
reporters, etc.
Updated to AEOS 3.1 screenshots, new functionality added:
‘No Alarm’ as sensor alarm type; PIN code as verification and identification for both
Installers and Users; limited time for test mode; repeat signaller for every new
08-01-2014 5
event; alive message for dialler; added display detector status; restore all alarms
with one button (only installers); clean –i and clean –ia specific for removing
intrusion data.
07-10-2013 4 Chapter 17.4 the stop – start is added
Dialler commands changed for adding area number, OG.CG changed to OP/CL,
ZA/ZR to UA/UR, detailed information for Chiron added.
For older hardware (fixed EOL) added the R1 and R3 must be 0
25-01-2013 3
Alarm device (naming) changed to System device.
Omit (= isolate) and bypass (= inhibit) added as text
Free definable SIA codes added, SIA codes for override/inhibit added
Dialler AEpu connection: only with dedicated Nedap cable, removing only Intrusion
alarms added
21-11-2012 2
Added: all detectors are counted in license, also those not connected
More information about system area, TEST mode, Technical alarms
New document
Database not mandatory any longer, InterAEpu remarks added, EN61000-6-3
15-10-2012 1
changed to 2007
Erase Intrusion data on AEpu, Belongs to in Detector and Area AEbc, XML added

Manual version 21 2
Installation and Configuration | AEOS - Intrusion EN

Manual version 21 3
Installation and Configuration | AEOS - Intrusion EN

Contents
1. GENERAL INFORMATION 9
1.1. SYSTEM OVERVIEW 9
1.2. INTRUSION COMPONENTS 10
1.2.1. REMARKS 10
1.3. INTRUSION FUNCTIONS 11
1.4. MULTIPLE AEPUS 12
1.5. AP3006 BASE PCB 13

2. NAMING CONVENTIONS 14
2.1. AREAS 15
2.1.1. DETECTORS IN MULTIPLE AREAS 15
2.1.2. SYSTEM AREA 16
2.1.3. AREA NAMING (AEOS 3.0.2 AND HIGHER) 16
2.2. ALARM TYPES 17
2.3. RESTORING ALARMS 18
2.3.1. RESTORE ALARM MESSAGE TO EVENTS / LOG 18
2.4. INTRUSION USERS 19

3. BEFORE STARTING INSTALLATION 20

4. MECHANICAL INSTALLATION 21
4.1. DIMENSION OF THE PANELS (470 X 460 X 110 MM) 21
4.2. MOUNTING THE PANELS 23
4.3. DIMENSIONS I/O UNIT (230 X 190 X 54 MM) 24
4.4. MOUNTING THE I/O UNIT 25
4.5. DIMENSIONS LCD KEYPAD READER (170 X 75 X 26 MM) 26
4.6. MOUNTING THE LCD KEYPAD READER 26

5. ELECTRICAL INSTALLATION 27
5.1. PREPARATIONS 27
5.2. CONNECTION MAINS POWER 28
5.3. INSTALLING THE DIALLER AT BASE PANEL 29
5.3.1. CONNECTIONS 30
5.4. INSTALLING BATTERIES AT BASE PANEL AND EXTENSION PANEL 32
5.4.1. CONNECTION OF BATTERIES TO AP3006 PCB 33
5.4.2. ADDITIONAL BATTERY INFORMATION 34
5.5. CONNECTIONS TO AP3006 PCB 35
5.5.1. TAMPER SWITCHES 35
5.5.2. CONNECTING INTRUSION LCD KEYPAD READER 35
5.5.3. SWITCHING OUTPUTS ON AP3006 PCB 37
5.5.4. POWER OUTPUT ON AP3006 PCB FOR SUPPLYING SENSORS 38
5.5.5. INPUTS (SENSORS) ON AP3006 PCB 39
5.6. INPUTS FROM OTHER AEPACKS 40
5.7. AEBUS CONNECTIONS 41
5.7.1. EXTERNAL AEBUS CONNECTIONS TO EXTERNAL AP3006S 41
5.7.2. AEBUS CONNECTIONS: GENERAL 42
5.7.3. AEBUS CONNECTIONS DETAIL 43

Manual version 21 4
Installation and Configuration | AEOS - Intrusion EN

6. CONFIGURATION BASICS 44
6.1. BUILDING EXAMPLE 45
6.2. AEMON VS. AEOS WEB-APPLICATION 46
6.3. AEBC (AEMON) INTERACTION WITH WEB-APPLICATION 46
6.3.1. SENSORS: DETECTOR AEBC 47
6.3.2. OUTPUTS: SIGNALLING AEBC 48
6.3.3. USED AEBCS FOR INTEGRATED INTRUSION SYSTEM 48

7. AEMON 49
7.1. MAKING IP CONNECTION TO INTRUSION BASE PANEL AEPU 49
7.2. STARTING AEMON 50
7.3. AEMON: CHECK AVAILABLE HARDWARE 51
7.4. AEMON: INTRUSION CONFIGURATION 51
7.5. INTRUSION LCD KEYPAD 52
7.5.1. INTRUSIONTERMINAL PROPERTIES 52
7.5.2. INTRUSIONTERMINAL BEEPER 53
7.5.3. INTRUSIONTERMINAL BACKLIGHT 53
7.5.4. INTRUSION LCD KEYPAD: TAMPER 53
7.5.5. INTRUSION LCD KEYPAD: VERIFICATION (UP FROM AEOS 3.1) 53
7.5.6. INTRUSION LCD KEYPAD: IDENTIFICATION BY PIN CODE (UP FROM AEOS 3.1) 54
7.5.7. INTRUSION LCD KEYPAD: INSTALLER BADGES VS. USER BADGES (UP FROM AEOS 3.1) 54
7.6. INTRUSION PANEL TAMPER 54
7.7. INPUTS: SENSORS – DETECTORS 55
7.7.1. DETECTOR PROPERTIES 56
7.8. OUTPUTS: SIGNALLING 59
7.8.1. SIGNALLING PROPERTIES 59
7.8.2. SIGNALLING TEST SITUATIONS 61
7.9. OUTPUTS: DIALER 62
7.9.1. COMPORTINTEGRATOR PROPERTIES 62
7.9.2. DIALER SETTINGS 62
7.10. BATTERY AND POWER CONTROL 63
7.10.1. POWERSENSE PROPERTIES 64
7.10.2. POWERSENSE CHECKING POWER RELATED ITEMS 65
7.10.3. POWERSENSE MANUAL ACTIVATE BATTERY CAPACITY 66
7.11. CONTROLLING AREAS BY HARDWARE INPUTS: AREACONTROL 67
7.12. GENERATING AEMON CONFIGURATION BY XML 67

8. AEOS: INTRUSION SETTINGS 68

8.1. GENERAL OVERVIEW 68
8.1.1. REPRESENTATION OF INTRUSION AEBCS FOR INTRUSION 69
8.2. SET SYSTEM PROPERTIES FOR INTRUSION 70
8.3. INTRUSION LICENSES 71
8.4. MAINTAIN AREAS 71
8.4.1. SYSTEM AREA 72
8.4.2. REPORTERS 72
8.4.3. SYSTEM DEVICES (BEFORE AEOS 3.02: ALARM DEVICES) 72
8.4.4. MONITOR CENTRE ACCOUNTS (FROM AEOS 3.1.7) 73
8.5. MAINTAIN ROUTES 74
8.6. MAINTAIN DETECTORS / REPORTERS / SYSTEM DEVICES 75
8.7. MAINTAIN INTRUSION TEMPLATES 76
8.8. MAINTAIN CARRIERS 77
8.8.1. USING PIN AS IDENTIFICATION (UP FROM AEOS 3.1) 78

Manual version 21 5
Installation and Configuration | AEOS - Intrusion EN

9. AEOS INTRUSION: GRAPHICAL ALARM HANDLER 79

9.1. GENERAL INFORMATION 79
9.2. MULTIPLE DISCIPLINES TO CONTROL INTRUSION AND SHOW ACTUAL STATUS 79
9.3. INTRUSION ALARM RESTORING VS ALARM HANDLING IN ALARM HANDLER 80
9.4. TAMPER AND FAULT ALARMS 80
9.5. CONFIGURATION ASPECTS 81
9.5.1. AVAILABLE STATUSES FOR AREAS (COMPONENT: AREAS) 81
9.5.2. AVAILABLE STATUSES FOR DETECTOR (COMPONENT: DETECTOR) 82
9.5.3. AVAILABLE STATUSES FOR STANDARDALARMITEMS 83
9.5.4. AVAILABLE ALARMS (ADDING ALARMPOINTS) 83
9.5.5. ADDING STATEPOINTS 84
9.5.6. COMMANDS 84
9.6. EXAMPLE CONFIGURATION 85
9.6.1. INTRUSION AREA EXAMPLE 86
9.6.2. INTRUSION DETECTOR EXAMPLE 87
9.6.3. GENERATING ALARM / STATE POINTS TO MAPS 89
9.6.4. INTRUSION FACE EXAMPLE 89

10. INTRUSION LCD KEYPAD READER 93

10.1. USING INTRUSION LCD KEYPAD READER 93
10.2. GENERAL 93
10.2.1. INTRUSION LCD KEYPAD LAYOUT 93
10.2.2. MENU INFORMATION 94
10.2.3. KEY FUNCTIONS 95
10.2.4. INTRUSION LCD SOFT KEY USAGE 95
10.3. MENU STRUCTURE 97
10.3.1. HOME MENU (MAIN MENU) 97
10.3.2. ARM MENU 97
10.3.3. DISARM MENU 98
10.3.4. SIMPLIFIED ARM AND DISARM MENU 98
10.3.5. ALARM MENU 99
10.3.6. LOGS MENU 99
10.3.7. CONFIGURATION MENU 100

11. CONFIGURATION EXAMPLES 104

11.1. WARNING DEVICE (EXTERNAL) 104
11.2. BURGLARY DETECTOR WITH TAMPER SWITCH ON ONE INPUT 106
11.2.1. PROPERTIES FOR DETECTORS AEBC 106
11.3. BURGLARY DETECTOR WITH TAMPER SWITCH ON TWO INPUTS 107
11.3.1. PROPERTIES FOR DETECTORS AEBC 107

12. MAINTENANCE INSTRUCTIONS 108

12.1. CLOCK BATTERY 108
12.2. SYSTEM BATTERIES 108

13. TESTING THE SYSTEM 109

13.1. AEPACK LOCAL TEST (ALT BUTTON) 109

14. DIALLER AEBC SIA EVENTS (AEOS 3.0.2 AND HIGHER) 110
14.1. SIA DATA FORMAT 110
14.1.1. EVENT BLOCK 110

Manual version 21 6
Installation and Configuration | AEOS - Intrusion EN

14.1.2. ASCII BLOCK 110

14.1.3. AREA NAME AND NUMBER 110
14.1.4. INTRUSION PANEL GENERATED SIA EVENT CODES 111
14.1.5. SIA FORMAT ADDED DESCRIPTIONS 112
14.2. CHIRON IRIS SECURE APPS POLLING ENGINE GENERATED EVENT 112
14.3. DIALLER DATA EXAMPLES 113
14.3.1. ARM AREA 113
14.3.2. BURGLARY ALARM 113
14.3.3. TECHNICAL ALARM 114

15. QUICK SETUP CHIRON DIALLER WITH NEDAP INTRUSION PANEL 115
15.1. HOW IT WORKS 115
15.2. PRE-REQUISITES FOR INSTALLING 116
15.3. FITTING THE SIM CARD 117
15.4. CONFIGURATION 117
15.5. DEBUGGING TOOL CHIRON 118

16. DIALLER AEBC SIA EVENTS (AEOS 3.0.1 ONLY) 122

16.1. SIA DATA FORMAT 122
16.1.1. EVENT BLOCK 122
16.1.2. ASCII BLOCK 122
16.1.3. INTRUSION PANEL GENERATED SIA EVENT CODES 123
16.1.4. SIA FORMAT ADDED DESCRIPTIONS 123
16.2. CHIRON IRIS SECURE APPS POLLING ENGINE GENERATED EVENT 123
16.3. DIALLER DATA EXAMPLES 124
16.3.1. ARM AREA 124
16.3.2. BURGLARY ALARM 124
16.3.3. TECHNICAL ALARM 125

17. ADVANCED STETTINGS 126

17.1. MAKING EXACT COPY OF INTRUSION AEPU 126
17.2. STARTING A NEW CLEAN INTRUSION AEPU 126
17.3. REMOVING INTRUSION DATA 127
17.4. REMOVING INTRUSION DATA VERSION BEFORE 3.1 127
17.5. ERASING ALL DATA FROM THE INTRUSION AEPU 127
17.6. AEMON USER RIGHTS 128
17.7. AEMON USERS 128
17.7.1. DEFAULT AEMON USERS SETTINGS 129
17.7.2. CHANGE / ADD AEMON USERS 129
17.8. AEMON SERIAL PORT 130
17.9. EOL RESISTORS DETAILED INFORMATION 130
17.9.1. ALARM, MASKING AND TAMPER ON ONE INPUT 130
17.9.2. ALARM AND TAMPER ON ONE INPUT, NO MASKING 131
17.9.3. ONLY INPUT, NO EOL RESISTORS 131
17.9.4. EOL PREFERRED RESISTOR VALUES 131

18. SAFETY PRECAUTIONS 132

18.1. GENERAL 132
18.2. WARNING 132

19. HARDWARE SPECIFICATIONS 133

Manual version 21 7
Installation and Configuration | AEOS - Intrusion EN

19.1. GENERAL 133

19.2. CERTIFICATION CONFORMITIES 133
19.2.1. INTRUSION BASE PANEL AND INTRUSION EXTENSION PANEL 133
19.2.2. INTRUSION I/O UNIT 134
19.2.3. INTRUSION LCD KEYPAD READER 134
19.3. RADIO EQUIPMENT TEST ON INTRUSION LCD KEYPAD READER 134
19.4. MAXIMUM AMOUNT OF EQUIPMENT CONNECTED 134
19.5. POWER CONSUMPTION 135
19.5.1. POWER CONSUMPTION EXAMPLES 135
19.5.2. POWER CONSUMPTION CONFORM GRADE 3 137
19.6. POWER SUPPLY 137
19.7. POWER SUPPLIED AND CHECKING BY AP3006 137
19.8. FUSES 138
19.9. BATTERIES 139
19.10. DIALLER 139
19.11. AP3006 PCB CHARACTERISTICS 140
19.12. CABLING 140

20. SOFTWARE SPECIFICATIONS 141

20.1. AMOUNT OF ATTEMPTS TO GET ACCESS TO INTRUSION LCD KEYPAD READER 141
20.2. USE OF PIN CODES 141
20.3. COLD BOOT SITUATION 141
20.4. METHODS OF SETTING AND UN-SETTING 141
20.5. CONDITIONS FOR SET STATE (ENTRY AND EXIT PROCEDURE) 141
20.6. OVERRULING DETECTORS AND UN-INHIBITING / UN-ISOLATING 142
20.7. AUTOMATIC LOG OFF 142
20.8. LEVEL 3 ACCESS WITHOUT LEVEL 2 AUTHORIZATION 142
20.9. LOG FILES 142
20.10. AUDIBLE ALARMS GENERATED BY TERMINAL 142

21. APPENDIX A: DETAILED INFORMATION INCLUDED POWER SUPPLY 143

21.1. POWER SUPPLY SPECIFICATIONS 143
21.2. POWER SUPPLY MECHANICAL SPECIFICATIONS AND BLOCK DIAGRAM 145

Manual version 21 8
Installation and Configuration | AEOS - Intrusion EN

1. General information
This document describes the configuration and use of the AEOS Intrusion system as integrated at the AEOS
environment. A dedicated AEpack (the AP3006) is used for sensing and controlling detectors, activating
outputs and checking the power supply including batteries.
In this document following parts are handled:

• Mechanical installation aspects

• Electrical connections
• Configuration aspects with AEmon
• AEOS Intrusion settings
• Graphical Alarm Handler usage and hints

1.1. System overview

A typical AEOS system could be built up as below, where a combination of the different AEOS disciplines is
made and all these disciplines can be controlled from the same platform:

AEOS web application

AEOS
Server

IP network

Combined Access Control and Access Control Combined Access Control and
Intrusion AEbus AEbus Intrusion AEbus

3 3
2
Intrusion
4
AEbus

1 2 3

Only
Intrusion
components
RS485
230 IP 230 230
VAC VAC 4 VAC Intrusion LCD
keypad reader
Monitoring
centre

The AP3006 based Intrusion components can be added directly to the IP-network (Intrusion Base Panel) or
to an existing AEpu by AEbus (Intrusion Extension Panel and Intrusion I/O Unit). For local functions (e.g.,
arming and disarming) the Intrusion LCD Keypad reader is used. This reader must always be connected to
the AP3006.
Via the dialler alarms are sent to the Monitoring centre, using an IP connection (with a GPRS link as
backup).

Manual version 21 9
Installation and Configuration | AEOS - Intrusion EN

Integrating AEOS and Intrusion in the same system gives:

• Easy and powerful Intrusion detection in AEOS

• Fully leverages of AEOS security controller (easily be combined with access control and video)
• Almost unlimited scalability of zones, areas and users
• Easy integration to the graphical alarm handler for showing actual live status and activation
• Central management of users and credentials
• Components used complies with EN50131-3 grade 3

1.2. Intrusion components

Following specific intrusion parts are available:

1. Intrusion Base Panel

o Processing unit (AEpu)
o Room for dialler
o Intelligent power supply 230VAC
o AP3006 for sensing detectors and controlling power supply
o Room for batteries
o Ruggedized housing (including tamper switches)

2. Intrusion Extension Panel

• Must always be connected to processing unit as, e.g., Intrusion Base Panel:
o Intelligent power supply 230 VAC
o AP3006 for sensing detectors and controlling power supply
o Room for batteries
o Ruggedized housing (including tamper switches)

3. Intrusion I/O Unit

• Must always be connected to processing unit as, e.g., Intrusion Base Panel:
o AP3006 for sensing detectors and controlling power supply
o Ruggedized housing (including tamper switches)

4. Intrusion LCD Keypad reader

• For, e.g., arming/disarming, making small changed, checking the logfile,
etc.:
o Graphical LCD display with backlight
o High-quality touch keys, software controlled, light only up when
needed
o Housing including tamper switch

1.2.1. Remarks
• AEpu:
The Intrusion Base Panel contains by its included AEpu the software (AEbcs) that takes care about the
Intrusion process. If required these AEbcs could also be added to an existing AEpu, where already access
control is running. For small Intrusion systems this should be no problem, always take care to the
memory use and performance of this AEpu.
One AEpu can handle 512 detectors (max 16 pro AP3006), 128 outputs (2 relays and 8 Open Collector
pro AP3006) and 8 Intrusion LCD keypad readers.

Manual version 21 10
Installation and Configuration | AEOS - Intrusion EN

• Detectors:
Detectors (inputs) are connected to the AP3006 for further handling.
The AP3006 can handle single inputs showing multiple states by using variable EOL resistors (sensor
present/idle – sensor not present/Tamper – short circuit – masking – Alarm/detection).
SIA commands belonging to Detectors are fixed, but for some types (Panic, 24H, Technical) they can be
defined by the installer.
Beside to the AP3006 the detectors can also be connected to other (unused) inputs of available AEpacks
in the AEOS system with following restrictions:
o EOL values are determined by the used AEpack and not by the Detector AEbc
o Only detection (alarm) and sabotage are possible, no masking
• Intrusion LCD Keypad reader:
The Intrusion LCD Keypad reader must be connected to the AP3006 and not to, e.g., APx003, due to the
intrusion menus and amount of data handling.
The Intrusion LCD Keypad reader can only be deployed on a AX8008 AEpu (or successor).
• Power Supply:
The Intrusion Panels (Base Panel and Extension Panel) are equipped with a dedicated power supply that
together with the AP3006 PCB takes care of the power management needed for intrusion, such as
controlling and loading the batteries.
The AP3006 can also be powered by AEbus (as in the Intrusion I/O Unit) or by any other suitable power
supply (just as all other AEpacks).

1.3. Intrusion functions

Beside all AEOS functions following Intrusion specific functions are available. Actions can be performed
either by the Intrusion LCD keypad reader, by contacts or by, e.g., the Graphical Alarm Handler:

• Arm / forced arm:

o Activate areas for burglary (all / partial)
o Overrule pending alarms (depending on user rights)
o Overrule active inputs (depending on user rights)
• Disarm:
o De-activate areas for burglary (all / partial)
o Only burglar alarms will be ignored, other alarms not
o Actual alarming stops immediately at disarming
• Restore alarms (on detectors):
o Acknowledge (remove) an alarm (depending on user level)
o Only when alarm is in default state (no function key enabled
• Inhibit: Disable detector for one arm/disarm period (inhibit is also known as ‘bypass’)
• Isolate: Disable detector for unknown period (isolate is also known as ‘omit’)
• Automatic inhibit detector after x alarms

Manual version 21 11
Installation and Configuration | AEOS - Intrusion EN

• Routes: Walk In – First Detector: Detector marked as first must be activated as first to start
Walk In, otherwise an alarm is generated. (First detector may never be inhibited.)
Walk Out – Last detector: Detector marked as last will (after activation –
deactivation) directly arm the system
Follower: In a route the sequence the detectors must be detected can optional be
stated, an incorrect sequence will generate an alarm.
• Area test mode: Set all detectors in an area in test mode

And using AEOS intrusion:

• Link to ATS (Alarm center) by dialler

• Locally all necessary actions can be executed at the Intrusion LCD Keypad reader
• Different user levels (installer, system, with free choice of functions and areas to control) can be
used at the Intrusion LCD Keypad reader)
• For each individual user the applicable language for the Intrusion LCD keypad reader can be selected
• Same detector can be used in multiple areas
• Easy link between, e.g., Access control and Intrusion is available: if, e.g., an area is armed, doors can
now automatically be blocked.

1.4. Multiple AEpus

As Intrusion is integrated in AEOS, is can be used over multiple AEpus with following restrictions:

• Areas and Routes cannot be spread over multiple AEpus.

All Detector AEbcs must be located on the same AEpu. Detectors (hardware) located on other AEpus can
be linked to the correct AEpu using the inter-AEpu functionality. On an Intrusion Terminal Areas located
on other AEpus can be controlled.
The server front-end checks for this when adding detectors and system devices.
• Every AEpu containing detectors and/or system devices must also have a TaggedServiceManager and a
SystemMonitor AEbc
• Events for arming/disarming an area are linked to the host-name of the AEpu where the
arming/disarming in initiated (and not to the host-name where the area is located). If all components
are on the same AEpu this is no problem, but in systems with multi AEpus this could sometimes give
some misunderstanding.
• Only for AEOS 3.0.1 keep all functions including the Intrusion LCD keypad reader on the AEpu with its
belonging areas. Error recovery with inter-AEpu connections are not 100% stable in this version.
• To check the communication between AEpus the NetworkMonitorAEbc can be used. The output of this
AEbc must connected to a Detector input which is set to Tamper.

Detectors and signallers have each their unique number pro AEpu (host). So when using multiple AEpus
identical detector numbers can be defined. To prevent this, use a range of numbers pro AEpu (e.g., first
AEpu range 1001-1999, second AEpu 2001-2999, etc.)

Manual version 21 12
Installation and Configuration | AEOS - Intrusion EN

1.5. AP3006 base PCB

In each panel and I/O unit the AP3006 PCB is the central part for controlling the connected sensors and
controlling the batteries. Schematic the AP3006 is shown below:

Detectors Output 12V Out1

12V power power 12V Out4
supply protection

27V DC Power Power-out

GND input monitor
BAT. LOW circuit
16 x In 1
AC OK
Processor inputs In 16
Battery Battery
check control Tamper Cover +
input Wall

2x Relay 1
Intrusion LCD Relais
2x Relay 2
keypad 1..2
RS485
8x OC 1
Intrusion base
panel
AEbus OC output OC 8

The AP3006 consists of following parts:

• AEbus communication (Isolated, Bitrate: high/low ( + non isolated: only for internal use))
Communication with the central Intrusion base panel
• RS485 communication (2 x) (2 channels available up from AP3006 PMS D)
The Intrusion LCD Keypad is communicating over RS485
To maintain certification only channel 1 can be used
• Power input and battery control
The dedicated power supply is controlled for correct functioning. Batteries are periodically checked.
All power outputs are short cut protected
• Power Output (4 outputs)
12V power for sensors are controlled for overload and shortcut
• Sensor inputs (16 inputs)
The analogue inputs are capable of detecting the various states a detector can be (alarm, fault, masking,
etc.)
• Tamper input
A wall tamper and cover tamper are connected to one input
• Relays outputs
2 relays with dry contact are available, outputs are user definable
• Open collector outputs
8 open collector outputs (short cut and overload protected) are available for user needs.

Manual version 21 13
Installation and Configuration | AEOS - Intrusion EN

2. Naming conventions
AEOS Intrusion uses following names:

• Sensors
Sensors are linked directly to the hardware of the AP3006 (e.g., PIRs). Each output of a sensor requires
one hardware input on the AP3006.
If the device (PIR) has separate outputs for, e.g., Alarm, Masking and Sabotage each signal needs a
separate input on the AP3006. For devices having only one output (using different EOL resistors) only
one input is needed on the AP3006.
One or more sensors can be linked to one detector.
• Detectors
Detectors can be compared to zones in other intrusion systems. A detector is an item linked to one or
more inputs on the AP3006. To one single detector multiple sensors (inputs) can be linked. This is useful
if, e.g., the PIR uses different outputs for the different states (as explained above).
The type of detector determines the SIA code sent by the dialler (for some detectors free definable).
• Areas
In an Area the different Detectors are grouped. Together with the LCD keypad readers, Reporters and
System devices.
Areas can be combined with time schedules and user rights to Profiles. These profiles are assigned to
the users who must operate the Intrusion system.
• Reporters
All items that have something to ‘tell’ are named reporters. E.g., signallers, with the signaller settings
you can define when an output must be activated. The outputs of the signaller can be linked to the
hardware outputs to control, e.g., a siren.
The Intrusion LCD keypad reader, dialler, system monitor (checking for general exceptions) are also
identified as an reporter.
• System devices (were called Alarm devices in AEOS versions before 3.0.2)
In the AEOS Intrusion system some hardware related messages are generated, e.g., if the AEpu
generates an NPE (System_Monitor) or if a hardware fails. By adding these System devices to an Area
the user can determine on which Intrusion LCD keypad reader these messages must be shown.

Detectors, Areas and reporters become active only after they are linked to one (or more) area(s).

Detectors, Reporters and System devices can be added to multiple Areas

Manual version 21 14
Installation and Configuration | AEOS - Intrusion EN

As example we use the building layout as below:

S1 S2 S3 Area 1
D1 D2 D3

Web-application

Area 3 D6 D7 Warning device

S7 Area 4 4S8

Area 2
D4 D5
S4 T4 M4 S5 S6

Topology: Sensors Detectors Areas

Reporters Areas

The sensors (S1 to S8) are connected to the hardware (AP3006), with AEmon sensor specific settings’(e.g.,
EOL values) are made. These sensors are linked to Detectors (D1 to D7). With the web-application the use
of the detectors over the areas and their functionality is determined. Reporters (e.g., the Alarm notification
device and LCD Keypad) must also be linked to areas to activate their functionality.

2.1. Areas
Areas are very useful to group several detectors and to get a better overview. A
single Detector can be used in more than one Area. D1 D2 D3
Example: Area 1 = D1+D2+D3, Area 3 = D1+D4+D6.
Area 1
D6
2.1.1. Detectors in multiple areas
The detector in common can only cause an Alarm if BOTH areas are armed D4
(AND function): Area 3
• Area 1 AND 3 armed:
All detectors will generate an alarm
D1 activated: for both areas an alarm is generated (Area 1 and Area 3)
• Area 1 is armed and Area 3 NOT:
D2, D3 activated Alarm Area 1
D1, D4, D6 activated NO Alarm (as D1 is in one of the areas that is NOT armed)
• Area 3 is armed and Area 1 NOT:
D4, D6 activated Alarm Area 3
D1, D2, D3 activated NO Alarm (as D1 is in one of the areas that is NOT armed)

Manual version 21 15
Installation and Configuration | AEOS - Intrusion EN

2.1.2. System area

A special area is the System area. This area is checked by those terminals added as Reporter in this System
area when areas are armed.
The System area is used to collect alarms and detectors which must be correct before the system can be
armed. Following system devices are advisable to be put into the system area: D-Dialler, D-SystemMonitor
(controlling the software), D-PowerSense for AEpu and dialler (for the power supply), D-IntrusionTerminal
where system area is controlled.
Fault signals of the System area will be presented on the corresponding Intrusion LCD keypad reader (the
Intrusion LCD keypad reader that is used for arming).

A System area is only checked if the Intrusion LCD Keypad reader from where the arming is
performed is added as Reporter to this system area.

It is allowed to use multiple System areas if so required.

Adding detectors and other reporters in the System area is not forbidden, but is not commonly used.

Example: 5 Areas (A1 .. A5) , 3 Terminals (T1.. T3), 1 system area (S1 with above mentioned system devices).
T1: A1, A2, A3, A4, A5 S1 is added as reporter
T2: A1, A2, A3, A5 S1 is added as reporter
T3: A5

When the system is armed at T1 or T2, the system area S1 is checked for alarms (faults). Arming at T3
will not check the system area S1. This results that when, e.g., there is a dialler problem you still could
arm at T3 but not at T1 and T2 (because at the system areas there is a fault.)
Arming at T3 with, e.g., a dialler fault could result that NO alarms can be sent to the ARC (there is a
dialler failure, but it was not noticed when arming at T3.

The system area must be added to the applied Intrusion Templates, to make is visible at the
terminal.

2.1.3. Area naming (AEOS 3.0.2 and higher)

If the Area name is starting with a number and a space (e.g., 146 Area1), this number is automatically
transferred to the corresponding part for the dialler (see chapter 14: Dialler AEbc SIA events (AEOS 3.0.2
and higher)

Manual version 21 16
Installation and Configuration | AEOS - Intrusion EN

2.2. Alarm types

Sensors are linked in AEmon to the Detector AEbc. For each sensor the alarm type that must be represented
can be selected. Depending on the alarm type it can be restored (handled) by a level 2 (System user) or a
level 3 Installer) users. Alarms can be generated by detectors according their alarm selection, but some
alarm types are generated directly from the system (technical alarms: Tamper and Fault).

• Tamper (generated by Detector and system)

Used for indicating a device is been tampered, including Sabotage. Also for Device connections (an
AEpack loses connection with the AEpu). (Restore by level 3 users)
• PAC and Log (generated by Detector)
Generates a message to the Monitoring centre (PAC) but will not generate an alarm (useful for, e.g.,
secured key-boxes. (Restore by level 2 and level 3 users)
• Panic (generated by Detector)
Electronic device designed to assist in alerting somebody in emergency situations where a threat to
persons or property exists Panic indication. (Restore by level 2 and level 3 users)
• Burglary (generated by Detector)
Burglary. (Restore by level 2 and level 3 users)
• 24H (generated by Detector)
24 Hours alarm are on at all times. (Restore by level 2 and level 3 users)
• Hold-up (generated by Detector)
Hold-up alarms are alarms that require a person under duress to covertly trigger the alarm to summon
the proper authorities. (Restore by level 2 and level 3 users)
• Technical (generated by Detector)
Technical alarm. (Restore by level 2 and level 3 users)
• Mask (generated by Detector)
Masking alarm: detector is been masked. (Restore by level 2 and level 3 users)
• No Alarm (generated by Detector)
When the No-Alarm alarm type for a sensor is set, that sensor will not generate an alarm when it is
active. It can generate sabotage and/or mask alarms when configured. detector is been masked. (As it
generates no alarm, it has not to be restored)
• Fault (generated by Detector and system)
Mains failure and dialler failure (Restore by level 2 and level 3 users)
Power failure (e.g., Battery fault, sensor power failure), generally system faults. (Restore by level 3
users.)

The defined alarm type is linked to the type of alarm that will be generated when this detector becomes
active. All alarm types except for the Burglary alarm will always generate an alarm at activation. A detector
with alarm type Burglary will only generate the burglary alarm when the corresponding area(s) are armed.

Main differences between the alarms above is: why they are generated, their description, the SIA event
code and the user rights for restoring them. For some alarm types the SIA code can be suppressed or user-
defined.

Manual version 21 17
Installation and Configuration | AEOS - Intrusion EN

2.3. Restoring alarms

With Restoring an alarm is meant that the alarm is acknowledged / confirmed. This results that the alarm
signals are reset.
Alarms can only be restored if they are no active signals for this alarm point.

For a PowerSense all alarms are checked, so ALL alarm causes must be solved at this PowerSense
AEbc before the PowerSense alarm can be restored.

Alarms can be restored locally at the Intrusion LCD Keypad reader or at the Graphical Alarm Handler.

2.3.1. Restore alarm message to events / log

Two different flows are used for the restore message. The Technical and Fault alarms use a different flow:

• Default restore flow:

Start detection: SIA alarm message
+ alarm event/log
Alarm restore command: SIA alarm end message
+ end alarm event/log
+ alarm restore event/log
• Technical and Fault restore flow:
Start detection: SIA alarm message
+ alarm event/log
End detection: SIA alarm end message
+ end alarm event/log
Alarm restore command: alarm restore event/log

This second flow makes it easier to check if the detector is not active anymore, e.g., if a power
supply is only very short interrupted or if it still fails (it can give an important indication how serious
this fault is)

To protect the system against overload the number of alarms persistently stored FOR EACH
ALARM POINT (detector / system device) is limited to 20. So after a AEpu restart only the 20
most recent alarms are known for each alarm point.

Manual version 21 18
Installation and Configuration | AEOS - Intrusion EN

2.4. Intrusion Users

At any Intrusion system different user levels are available:

• Level 2 users System users: ‘Standard’ intrusion rights (arming, disarming, inhibiting, etc.)
• Level 3 users Installer: As system user, but with some more technical rights
Needs always System user to get access to the system
• Level 4 users Manufacturer: No intrusion rights, only access to manufacture part
• Level 1 users Not registered users: Unknown users, having no rights

With the AEOS Integrated Intrusion solution only the difference between System users and Installers can be
made when issuing a badge to a person. All other functions can freely be added to a profile / users.
If requested specific Manufacturer aspects can be added to AEmon (see chapter 17.7, AEmon users)

As for all AEOS menus the AEOS administrator is free to choose the user rights (what functions may any
user perform):

• LCD Keypad terminal: Possible functions must be added to the Intrusion profile together with the
applicable areas. The Profile is assigned to the carrier.
• AEOS front end: Menu functionality is determined by the AEOS administrator

Up from AEOS 3.1 it is possible to use the PIN code as identification (instead of badges), enabling now
following choices for entering the Intrusion terminal:

• Badges only
• Badge together with verification (needs additional AccessPoint)
• PIN code only
• Mix of above (e.g., for users only the badge, for installers a PIN code)

Manual version 21 19
Installation and Configuration | AEOS - Intrusion EN

3. Before starting installation

Always pay attention to the (local) safety regulations, see also chapter 18: Safety precautions.

It is important to create a comprehensive system plan prior the installation of the Intrusion system. This
plan should include a site map, a component and equipment list, detector list, area list, region list and the
number of users.

Start

Make system Power & EOL

plan calculations

No
Hardware Hardware Software System
Installation Configuration Configuration Pass
test
(AEmon) (web appl.)
Yes

End

Complete installation consists of:

• Hardware installation:
Mounting the panels, sensors, EOL resistors, cabling
• Hardware configuration:
Check pre-defined settings for sensors and reporters (outputs), check EOL values
• Software configuration:
Assign sensors to detectors, areas, reporters, etc. assign users

Manual version 21 20
Installation and Configuration | AEOS - Intrusion EN

4. Mechanical installation
Both Intrusion Base Panel and Intrusion Extension Panel share the same housing.

4.1. Dimension of the panels (470 x 460 x 110 mm)

Release front cover release by one unscrewing the screw in middle. Top cover can be lift off. When closing
top cover lift up bottom side a little.

01
1

2
02

Front view with cover closed Front view with cover removed Side view with cover opened

Manual version 21 21
 Installation and Configuration | AEOS - Intrusion EN

A 460

430
B

35
24
Ø19
25 75 37

200

30

5 x 10 170 170 65
470 8
110

Manual version 21 22
Installation and Configuration | AEOS - Intrusion EN

4.2. Mounting the panels

Pay attention to the (local) safety regulations.

The wall tamper switch is protected by an additional protector that must be mounted separately behind the
panels.

Mounting instructions:

1. Make sure the wall is flat

2. Mount panel with only one screw in middle top
(point in previous figure)
3. Line out the panel both horizontal and vertical
4. Mark mounting locations and cable outlets
5. Mark mounting points for ‘wall tamper protector’
(point in previous figure and figure beside)
6. Remove panel
7. Mount Wall tamper protector with 2 screws
8. Mount panel with at least 4 screws (or 6 for big batteries)

Wall tamper housing

Wall tamper
protector

2 mounting screws

Manual version 21 23
Installation and Configuration | AEOS - Intrusion EN

4.3. Dimensions I/O Unit (230 x 190 x 54 mm)

Release front cover of the I/O Unit release by one unscrewing the screw in middle.
Top cover can be lift off. When closing top cover lift up bottom side a little.

1
01

02
2

Front view, cover closed Front view, cover removed Side view, cover open

202

30

70

B 80
5 x 10
70

60 31

190 25 8
30
230 54

Manual version 21 24
Installation and Configuration | AEOS - Intrusion EN

4.4. Mounting the I/O Unit

Pay attention to the local safety regulations.

The wall tamper switch is protected by an additional protector that must

be mounted separately behind the I/O Unit.

Mounting instructions:

1. Make sure the wall is flat

2. Line out the panel both horizontal and vertical
3. Mark mounting locations and cable outlets
4. Mark mounting points for ‘wall tamper protector’
(point in previous and figure beside)
5. Remove panel
6. Mount Wall tamper protector with 2 screws
7. Mount panel with the 3 screws.

Wall tamper housing

2 mounting
screws

Wall tamper
protector

Manual version 21 25
Installation and Configuration | AEOS - Intrusion EN

4.5. Dimensions LCD Keypad reader (170 x 75 x 26 mm)

The Intrusion LCD keypad reader is used to get access to the Intrusion system (arming, disarming, etc.).

Dimensions ‘Front’ view ‘Back’ view

6.8

20.3
4.8

2.0
40
120

170.5
8

A
30

52 1.5
75.2 26.5
Wall tamper
protection

4.6. Mounting the LCD Keypad reader

The wall tamper switch of the LCD keypad reader is protected by an additional protector that must be
mounted separately behind the LCD Keypad reader.

Mounting instructions:
1. Make sure the wall is flat
2. Open the reader (see figure beside, take care of the additional tamper switch at the
backside), the back plane must be mounted first
3. Line out the panel both horizontal and vertical
4. Mark mounting locations and cable outlets
1 2
5. Mark mounting points for ‘wall tamper protector’ 3
4 5 6
(point in previous figure) 7 8 9
6. Remove panel C 0 E
7. Mount Wall tamper protector with 2 screws
8. Mount panel with the 4 screws.
9. Connections must be made on the connector on the backside of the front part
10. After making the connections, replace the front (take care of the additional tamper 02
switch at the backside) and tighten up the two screws at the bottom of the LCD
Keypad reader.

01
The additional tamper switch at the back side must gently be pushed in a little
Un screw
during removing and mounting the panel.

Manual version 21 26
Installation and Configuration | AEOS - Intrusion EN

5. Electrical installation
After mechanical mounting the electrical connections can be made. Following parts must be installed:
• Mains power connections
• Installing the dialler in the Intrusion base panel
• Installing the batteries in both Intrusion base panel and Intrusion extension panel
• Connect the Intrusion LCD keypad reader to the AP3006
• Connect sensors and other equipment to each AP3006
• Make connections between AP3006s (base panel – extension panel / I/O unit)

It is not possible to make changes to the hardware or wiring of the Intrusion equipment when
the hardware is connected to a live power supply or battery (the hardware is not hot-
swappable). Always switch off the power supply before starting work on the equipment. Take
special care that also the battery is disconnected.
The Intrusion panels contain components that may be damaged by electrostatic discharge. In
order to prevent ESD damage when working on the devices, we advise using an antistatic wrist
strap that is connected to the housing or of any other earthed device.

5.1. Preparations
During installation local safety regulations must be taken in account. Always power down equipment during
installation activities at the equipment.

Take care of the local safety regulations, changes and installation only by certified installers.

Manual version 21 27
Installation and Configuration | AEOS - Intrusion EN

5.2. Connection mains power

Take care of the local safety regulations and see also chapter 18: Safety precautions

Power N Cable clamp Power cable

connector PE
Power Fuse L N: Neutral
Fuse PE: Protective Earth
L: Line

For continued protection against risk of fire replace fuse only with the same type and rating of
fuse.

Manual version 21 28
Installation and Configuration | AEOS - Intrusion EN

5.3. Installing the dialler at Base panel

The dedicated dialler must be built in by the installer.
The dialler PCB must be mounted on the plate above the AEpu, see figure beside.
Needed:

• Dialler (optional with GPRS antenna), TCP/IP cable included

• USB cable between dialler and AEpu (Nedap art. nr 5526663)
• Power cable between AP3006 and dialler
• Optional Surge protector on TCP/IP cable (not included)

We recommend to use the Nedap USB cable (nr 5526663) and not a standard USB cable between AEpu and
dialler (only for demo purpose an standard USB cable will fit). Make correct setting at the dialler AEbc.

Dialler is not included and must be supplied by the installer.

USB cable is not included, can separately be ordered at Nedap (Art. nr 5526663)

Manual version 21 29
Installation and Configuration | AEOS - Intrusion EN

5.3.1. Connections
Unpack the dialler and check the delivered materials.

For more detailed information check the manual as delivered with the dialler.

Steps to follow:

Step Secure the dialler onto the plastic mounting plate above the AEpu, using the self-adhesive feet
01 01
Fit the Ethernet cable into the Ethernet output on the PCB and 02
connect the other end into a
Step
IP surge protector. The outside of the surge protector must go to the local IP router or the
02 Ethernet socket allocated by the client.
Step
Connect the antenna to the PCB (when using GPRS) 03
03
Step
Fit the SIM card (when using GPRS) 04
04
Step Connect the AEpu (at base panel) with the special cable (USB to serial connector) to the dialler)
05
Step 05
Connect a power cable between AP3006 PCB and dialler
06
06
Step
Before configuration, position the antenna for optional GSM signal strength (see dialler
07 installation manual)

Step Configuration settings of dialler must be done at AEmon, see appropriate chapter 7.9.2: Dialer
08 settings.

03
GPRS antenna
to ATS
Dialler PCB
Dedicated cable 05 01
to AEpu 4 self-adhesive feet

06
Power from 04 SIM card
AP3006 for GPRS

02
TCP/IP
to ATS

Manual version 21 30
Installation and Configuration | AEOS - Intrusion EN

The ATS (Alarm Transmission System) connection between the Intrusion Base Panel and the ARC
(Alarm receiving centre) is primary by TCP/IP connection on the dialler
02PCB. As backup the
GPRS can be used. 03
The Ethernet cable to the ATS (Alarm Transmission System) 02 be connected to a surge
must
protector before leaving the housing (e.g., the SB24540 from MTL Surge Technologies, available
at RS components under number 624-2890). Suppressor must be suitable mounted. If not
applied the certification is not valid any longer.

Dialler PCB is mounted with self-adhesive feet above the AEpu.

03
Power to dialler
AP3006 GPRS antenna
06

Dialler PCB

Alternative USB
cable

Self-adhesive feet
Mounting plate
TCP/IP cable to surge AEpu
protector before 07
leaving housing
02
Dedicated cable
TCP/IP cable to 05
to AEpu
ATS network

06 Power connections between

AP3006 and dialler
+

TCP/IP connection on the AEpu 07

is NOT for the ATS Alarm transmission system, but only for
programming purposes. (ATS connection is made to dialler PCB .) 02

Manual version 21 31
Installation and Configuration | AEOS - Intrusion EN

5.4. Installing batteries at Base panel and Extension panel

The batteries are to be built in by the installer. At the bottom of panels there is sufficient room for two
batteries.

The AP3006 checks at regular times the condition of the batteries. For this an external load is connected to
the Load connector. Loading of the batteries is regulated by the external (dedicated) power supply.

Example
battery

Needed:
• Batteries (not included)
• Cables and fuse (included with the panels)
• Connectors for mounting the cable to the battery (not included)
• E.g., tyraps to secure the batteries against movements (not included)

Batteries are not included and must be supplied by the installer.

The batteries must be secured against movements (by, e.g., tyraps).

Manual version 21 32
Installation and Configuration | AEOS - Intrusion EN

5.4.1. Connection of batteries to AP3006 PCB

Use the cables as supplied with the panels. Shorten these to correct length and firmly mount connections to
the battery. The electrical diagram is shown below. Fasten cables using tyraps to the housing.
Between both batteries the fuse must be applied. For continued protection against risk of fire replace fuses
only with the same type and rating of fuse (see chapter 19.8: Fuses).

Between both batteries the fuse must be applied. For continued protection against risk of fire
replace fuses only with the same type and rating of fuse.

- +
Battery 1 Battery 2
+ -
Fuse

Manual version 21 33
Installation and Configuration | AEOS - Intrusion EN

5.4.2. Additional battery information

Battery handling is a process from AP3006 in combination with the dedicated power supply, see below:

AP3006
Power POW BAT AEbus K2
In BAT LOW AC OK Isolated
Power K11 Battery
AC In Battery K17
Supply In Battery
Out
Power
K14 check K3
Battery check Load

• Charging the batteries is regulated by the dedicated power supply

• Checking batteries is controlled by the AP3006, for this the load (Resistance) as connected on K3 is
used:
o Check if batteries are connected (each x seconds)
o Check if battery charge electronics is ok (each x seconds)
o Check battery voltage (each x seconds)
o Check batteries capacity (periodically, at least once a day)
• Signals from the dedicated power supply are checked and further handled by the AP3006 firmware
Indicators:
o BAT LOW: Battery capacity below secure level (controlled by power supply)
o AC OK: AC input for power supply OK (controlled by power supply)
o POW: Power AP3006 retrieved from Vin (Power supply K11 or AEbus)
o BAT: Power AP3006 retrieved from battery (K11)

Battery supply will only operate after power up with mains supply. The AP3006 will never power
up from batteries only.

Manual version 21 34
Installation and Configuration | AEOS - Intrusion EN

5.5. Connections to AP3006 PCB

5.5.1. Tamper switches
The Intrusion base panel, extension panel and I/O unit have two tamper switches, one for the front cover
and one for the wall tamper.

Tamper
switches

The Tamper switches are connected to K18 pin 1-2 and 3-4. If only one tamper switch is used, an
interconnection must be made for the other tamper switch (internal on the AP3006 PCB the tamper
switches are handled as one input).

Tamper switch is of type Normally Closed (cover closed means switch contact closed).

5.5.2. Connecting Intrusion LCD keypad reader

The Intrusion LCD keypad reader is connected to AP3006 (Reader input) for communication and power.
(Power can also be retrieved from one of the Sensor Power outputs.)

Steps to follow:

Step
Open Intrusion LCD keypad reader (by unscrewing two bottom screws)
01
Step
Gently push the reader upwards (take care of the tamper switch)
02
Step
At the back of the reader the shielded cable must be connected.
03
Step Shielding of cable must be connected at reader pin 2 and at metal housing using the metal clamps.
04

Manual version 21 35
Installation and Configuration | AEOS - Intrusion EN

Step
Re-mount the reader at backside.
05

Backside Intrusion LCD reader

1 5 6 10
1 1

Sensor Power (12V)

Reader +V G +V G
+12 G A B N N
N 1 D 3 D
V D (-) (+)
Connectors AP3006 PCB

5.5.2.1. Connections:
Intrusion LCD reader Function AP3006
1 Power Power in (10-30VDC) +12V
2 POWER GND / Shield Power Ground GND
3 A (-) RS485 Reader A (-)
4 B (+) RS485 Reader B (+)
2 Cable shield Cable shielding Metal clamp

Cable shield must be connected to pin 2 of Intrusion LCD reader, together with GND connection.

Manual version 21 36
Installation and Configuration | AEOS - Intrusion EN

5.5.3. Switching outputs on AP3006 PCB

The AP3006 has two different output types:
• 2 relays outputs with dry contacts (normally open – common – normally closed)
• 8 Open collector outputs (to GND), shortcut and overload protected, max 1000 mA load.

For both type of outputs the power for the device to be activated must be supplied external or from the
Sensor Power outputs.

LED indicators show the status for each output.

Relais OC 1 .. 8
NC
COM V+
V+ Device to be activated
Device to be
1 .. 2 NO
activated OC1 .. 8
GND
GND

GND on connector for Open Collector outputs must be used as return for the V+ (external supply).

Manual version 21 37
Installation and Configuration | AEOS - Intrusion EN

5.5.4. Power output on AP3006 PCB for supplying sensors

On the AP3006 4 separate power outputs (SENSOR POWER) supplying 12V DC, max 200 mA are available,
each shortcut and overload protected.

If 200 mA is not sufficient, power outputs can be put to parallel to increase maximum current.

For each output a LED is indicating the state:

ON (green) = OK.

External devices may only be supplied using these 4 Sensor Power outputs. Do not use other
power outputs from the AP3006 PCB.
When calculate total power consumption include also the sensor power.

Manual version 21 38
Installation and Configuration | AEOS - Intrusion EN

5.5.5. Inputs (sensors) on AP3006 PCB

16 sensors (inputs) can be connected to the AP3006 PCB. For each individual input the EOL (End Of Line)
resistor value can be chosen during installation.

Each input (sensor) has its own corresponding LED showing the status of this input:

INPUT 1..16 (red)

ON Active / alarm event (unsafe)
OFF Not active / present (safe)
Flashing 5 Hz Sabotage (shortcut)
Flashing 15 Hz Sabotage (open/tamper)
ON–ON-OFF Sabotage (masking)

Functionality of the inputs is determined during installation. Due to the variable EOL resistors for multiple
alarm states from the sensor only one input is needed.

During installation select the proper EOL resistor value for the used inputs. These values must be
according the used sensor.

Manual version 21 39
Installation and Configuration | AEOS - Intrusion EN

5.5.5.1. EOL resistors on AP3006 PCB

Each input of the AP3006 PCB can have its own individual EOL resistor value. EOL values other than
standard must be stated during installation.

The AP3006 is capable of handling different states to one hardware input.

Not configured inputs can be left unconnected. Configured un-used inputs can be connected with R=3K3 to
GND.

InX

R=3K3
R1 Alarm

R=8K2
R2 Masking

Tamper
GND
R=1K5
R3

Optimal values for the EOL resistors (see figure beside) are: 3K3, 8K2, 1K5. Other values are
possible, their values must be set during the configuration part at AEmon. Detailed information
can be found at chapter 7.7.1: Detector properties.

5.6. Inputs from other AEpacks

Detectors can be connected to any free unused input at any suitable AEpack in the AEOS system.
Check the corresponding AEpack Installation sheet for detailed information.

Only for the AP3006 the variable EOL values can be set at AEmon (Detector AEbc), all other AEpacks (unless
otherwise specified) have fixed EOL resistors (4K7) and are not capable of handling the masking alarm.

InX
R=4K7

R1 Alarm

Tamper
GND
R=4K7
R3

Manual version 21 40
Installation and Configuration | AEOS - Intrusion EN

5.7. AEbus connections

On the AP3006 there are two AEbus connections available: one as isolated AEbus (K2) and one as non-
isolated AEbus (K5):
AEbus connection on the AP3006 (K2) is providing the isolated AEbus (as on, e.g., the AP4000 series). A
second AEbus connector for internal use (K5) is available to connect local AEpacks using non-isolated AEbus
communication:

External isolated AEbus

Internal non isolated to AP3006s (K2)
AEbus, e.g., to AEpu (K5)

• K2 for connecting to other AEpacks outside the housing, using the isolated AEbus communication
K2 is the default screw AEbus connector and is used to connect other AEpacks.
• K5 for connecting to other AEpacks inside the same housing, using non-isolated AEbus
communication
K5 is a special plug on connector, needs a special cable to connect it to other AEpacks.
K5 is normally used for connecting the AEpu inside the Intrusion Base Panel.

5.7.1. External AEbus connections to external AP3006s

If additional AP3006s are connected to the Intrusion Base Panel (with power supply: Intrusion Extension
Panel, without power supply: Intrusion I/O unit) they are connected by the AEbus on each AP3006 PCB to
the AEpu in the Intrusion Base Panel.

AEbus

AP3006 AP3006 AP3006 AP3006 AP3006

I/O units I/O unit

Base Panel Extension Panel

Power supplied by Base panel Power supplied by first Extension panel

Manual version 21 41
Installation and Configuration | AEOS - Intrusion EN

The AEbus communication bus is controlled by the AEpu at the Intrusion Base Panel. The AEbus from the
AEpu is (fixed cabling) connected to K5 of the AP3006 in the Intrusion Base Panel. Other AP3006 are
connected in a loop on connecter K2 on the AP3006.

AEbus to AP3006s
AEbus to AEpu (K5) (K2)
(Intrusion Base Panel)

Termination
jumper

On the first AP3006 and the last AP3006 the AEbus termination jumper must be set to ON. For all
other AP3006s in between this jumper must be put OFF.
First versions of AP3006 PCB can have a different jumper position for On and Off. Always check
installation sheet for the correct information.

5.7.2. AEbus connections: General

AEbus connections must always be to the identical connector point of the other AP3006 PCB.
If power is locally supplied (e.g., by the Intrusion Extension Panel), connect only CG, CL and CH (+ and – are
not connected). The AP3006 has a single AEbus connector, so two cables must be mounted on one
connector.

Always shielded cable must be used; CH and CL must be one twisted pair. From other pair one
conductor is used for CG( GND). Cable shield must be connected to metal housing at outgoing
and incoming side.

Cabling example using configuration on page before:

Fuse Fuse

On On On On
On
Off Off Off Off
Off

Base Panel I/O unit I/O unit Extension Panel I/O unit
Only AEbus communication, no power
(supplied by next extension panel)

AEbus termination ON for first

AP3006 and last AP3006

Manual version 21 42
Installation and Configuration | AEOS - Intrusion EN

5.7.3. AEbus connections detail

Depending on where additional Intrusion Extension Panels (for extra power supplies) are added, the AEbus
cabling will be different (communication including power versus only communication).

5.7.3.1. External AEbus including power supply

If no extra power supply is needed the additional Intrusion I/O units connected are supplied from the
previous power supply.
All 5 connector points from K2 on each AP3006 are connected to each other.

Fuse

If the Power over the AEbus goes outside the housing, an additional line fuse must be added in
the + line inside the housing.
The value of this fuse can be found in (see chapter 19.8: Fuses). It is calculated so that total
maximal 800mA current can be supplied behind this fuse.

5.7.3.2. External AEbus without power supply

If no additional power supply is needed the extra Intrusion I/O units connected are supplied from the
previous power supply.
Only 3 connector points from K2 (CG, CL and CH) on the AP3006s are connected to each other.

Always shielded cable must be used; CH and CL must be one twisted pair. From other pair one
conductor is used for CG (GND). Cable shield must be connected to metal housing at outgoing
and incoming side.

Manual version 21 43
Installation and Configuration | AEOS - Intrusion EN

6. Configuration basics
After hardware installation (see chapters before) the connected PCBs must be configured. This is done by
the software tool AEmon and the (integrated) web-application.

Start

Make system Power & EOL

plan calculations

No
Hardware Hardware Software System
Installation Configuration Configuration Pass
test
(AEmon) (web appl.)
Yes

End

Procedure:
1. Be sure that no alarm will be generated by opening the alarm panels
2. Make connection to Intrusion base panel AEpu (IP settings, use AEconf or HyperTerminal)
3. Use AEmon to check and /or change the hardware configuration and the hardware related settings
4. With the AEOS web-application the correct settings can be linked together (detectors, reporters to
areas, users, routes, etc.)
5. After the system is configured (ready for use), with the Intrusion LCD Keypad reader the intrusion
system can be operated now (arming, disarming, etc.).

Physical sensors (e.g., PIRs) are linked to logical Detector AEbcs. Detectors together with areas and
rules result in controlling signals. The logical outputs of these controlling signals are connected to
physical outputs (e.g., relays for activating alarm lamp)

Manual version 21 44
Installation and Configuration | AEOS - Intrusion EN

6.1. Building example

As example we use the building layout as below:

S1 S2 S3 Area 1
D1 D2 D3

Web-application

Warning device
Area 3 D6 D7
S7 4 S8
LCD keypad

Area 2
D4 D5
S4 S5 S6

Topology: Sensors → Detectors → Areas.

The sensors (S1 to S8) are connected to the hardware (AP3006), with AEmon sensor specific settings’(e.g.
EOL values) are made. Sensors are linked to Detectors (D1 to D7). With the web-application the use of the
detectors over the areas and their functionality is determined. Example: Area 1 = D1+D2+D3, Area 3 =
D1+D4+D6.

Manual version 21 45
Installation and Configuration | AEOS - Intrusion EN

6.2. AEmon vs. AEOS web-application

Settings related to the hardware are made by AEmon during installation, all other settings by the AEOS
web-application:

AEmon Web-application

Routes Schedules
Detectors
One or more Area Functions User type and
Area Functions
sensor inputs

Dialler Profile

Signalling Reporters /
Alarm type with System Devices
rules
Users
Intrusion Panel
LCD keypad
Identifier type Identifier type Identifier nr

This Detectors can be compared to zones in other intrusion systems, having some additional
features.

6.3. AEbc (AEmon) interaction with web-application

Relations and actions on the AEpu are controlled by the Area information on the AEpu. The area content is
the binding link between the Intrusion AEbcs:

Input
(AP3006)

Input Area
(AP3006) information
Output
(AP3006)

Detector =
x sensors Set:
Sensor type / Alarm type /
EOL / NO-NC Sensor Mode

Manual version 21 46
Installation and Configuration | AEOS - Intrusion EN

6.3.1. Sensors: Detector AEbc

For each sensor connected to the Detector AEbc an alarm type can be selected, (see chapter 2.2: Alarm
types for a complete list), e.g., Tamper, Panic, Burglary, Technical, etc.

The defined alarm type is linked to the type of alarm that will be generated when this detector becomes
active. All alarm types except for the Burglary alarm (and NoAlarm, PAC_and_Log) will always generate an
alarm at activation. A detector with alarm type Burglary will only generate the burglary alarm when this
area is armed.

Additional for each input the input settings can be defined:

• SIA code for begin and end of activation (for Panic, 24H, Technical)
• Delay (during this time the detector is ignored after arming)
• Type of contact: Normally open / normally closed
• Alarm state + EOL resistor value
• Tamper (sabotage / fault) + EOL resistor value
• Masking + EOL resistor value
• Output to indicate the logic state (true - false) of the corresponding input

InX
R=3K3

R1 Alarm
R=8K2

R2 Masking

GND Tamper
R=1K5
R3

The Detector AEbc can handle sensors (PIRs, etc.) with one combined output and sensors having
separate outputs for, e.g., Alarm, Masking and Tamper. Detector number and name is identical
for these separate inputs on the AP3006 PCB, the alarm state can differ. A detector can only be
used after it is added to one of the areas.

Manual version 21 47
Installation and Configuration | AEOS - Intrusion EN

6.3.2. Outputs: Signalling AEbc

At the Signalling AEbc one (or more) Alarm rule(s) can be made which will affect an output on the AEbc
related to the Area as determined at the web-application (or LCD keypad reader).

Example:
There are three detectors: One Burglary, one Technical and one area_state:

Signal name Type Alarm type Mode Corresponding rule

1 Burglary Signal ALARM Burglary ARMED BUR → Armed
2 Technical Signal ALARM Technical (none) TEC
3 Walk In AREA_STATE WALK-IN TIME ACTIVE WalkIn Time Active

At the web-application (Area menu) these Signals can now be added to one or more Areas (as Reporters)
As soon as the Alarm rule becomes true for this Detector type in the corresponding Area the Output (alarm)
of the AEbc is activated.

Reporters and
Detectors Area Output
alarm rules

6.3.3. Used AEbcs for integrated intrusion system

For an Intrusion system following specific AEbcs are available:
• Detectors AEbc
At the Detector AEbc the sensors (inputs) are connected.
Each input will have an unique number, to each number one or more alarm types can be defined.
Input state (Normally Open / Closed) and (optional) EOL resistor values must be entered here.
• Signalling AEbc
At the Signalling AEbc one (or more) Alarm rule(s) can be made which will affect an output in
combination with the Area or Route as been determined at the web-application. Signalling outputs
will be shown as Reporter in the web-application.
• IntrusionTerminal AEbc
For connecting the LCD Keypad reader the IntrusionTerminal AEbc is required. Here the used
identifier is chosen.
• PowerSense AEbc
Checks all relevant power related information and generates an alarm if a value exceeds the stated
value. Includes power supply and sensor related alarms.
• Dialler AEbc
Messages to the Monitoring centre are sent by the Dialler AEbc.
• AreaControl AEbc
Arming / disarming areas using hardware contacts.
• Additional service AEbcs
Some additional AEbcs are needed to complete the configuration:
o SystemMonitor (monitors all system information)
o Tagged Service Manager (link between different Intrusion AEbcs)

Manual version 21 48
Installation and Configuration | AEOS - Intrusion EN

7. AEmon
Functionality and properties of detectors, sensors and outputs are configured by AEmon. Here the low level
settings are made, these are all settings near related to the hardware.

If required it is possible to add in AEmon user groups including specific rights, which can be linked to the
AEmon users:
• Level 3 group users (Installer)
• Level 4 group users (Manufacturer)
On each group different rights (for having access to the AEmon menus) are linked.

Steps to perform:
• Make IP connections between PC and AEpu (Intrusion Base Panel)
• Start AEmon
• AEmon: Check available hardware and optional update firmware
• AEmon: Intrusion configuration:
o Intrusion LCD keypad
o Sensors – detectors
o Signalling (outputs)
o System devices
o Dialler
o Battery control – Sensor power monitoring

Before getting access to the Intrusion base panel (and opening it) be sure the tamper switch is
overruled by an authorized user otherwise an alarm can be generated.
Login in to AEmon will not have any effect on the normal operation of the Intrusion system. It is
not made visable to the Intrusion LCD Keypad readers or the front end other than a message into
the logfile.

More detailed information about the Intrusion AEbc can be found in the corresponding AEbc Descriptions,
as available in AEmon.

Due to the limited messages as sent by the dialler (64 characters max) use short names for AEbcs
and descriptions, otherwise data will not be complete received at the ARC (relevant information
can be missed.

7.1. Making IP connection to Intrusion base panel AEpu

Use serial connection (Hyperterminal) or AEConf to make the correct IP settings for this AEpu.

Check if the battery at the AEpu is activated (plastic strip between the battery poles must be
removed).
During installation/ configuration the database on the AEpu can be activated (Not mandatory).

Manual version 21 49
Installation and Configuration | AEOS - Intrusion EN

7.2. Starting AEmon

After activating AEmon after some seconds the start-up screen is shown:

When AEmon is started the default AEmon view will show up.

Depending on rights for this user several settings and checks can be made in AEmon. Default all menu
options are available.

To get access to an AEpu just click on the AEpu name in the left pane and use the correct Password to log in
to this AEpu. Login and password are determined by the installer.

The user name is linked to the AEmon user levels. The user levels determine the functions this
user has access. Not allowed functions are disabled.
If the user is not logged in, most menu items at the AEmon menus are disabled.

Manual version 21 50
Installation and Configuration | AEOS - Intrusion EN

7.3. AEmon: Check available hardware

All hardware connected to the Intrusion Base Panel will be shown in AEmon (View Hardware):

For each hardware unit its name (e.g., AP8001), AEbus address and used firmware is shown:
• AP8001: Intrusion Base Panel (AEpu)
• AP3006: Intrusion Extension unit / Intrusion I/O units
Here 2 AP3006 are connected (hardware address 31 and 32)
• IVXSCR: Intrusion LCD Keypad reader (connected to AP3006 with address 31)

7.4. AEmon: Intrusion configuration

At typical intrusion configuration as shown in chapter 6.1 can be built in AEmon using uses following AEbcs:

Manual version 21 51
Installation and Configuration | AEOS - Intrusion EN

In this example only one AP3006 is shown, in most situations multiple AP3006 PCBs are used, but in general
the connections are identical as above. Each separate AEbc will be explained below:

When making changes with AEmon to detectors that are already in an alarm state, these alarms
will automatically been restored at the deployment phase of AEmon. (If the detector is still active
after the change a new alarm will be generated.

7.5. Intrusion LCD keypad

Use the IntrusionTerminal AEbc to connect to the Intrusion LCD Keypad (represented in AEmon as IVXSCR)
The IntrusionTerminal can only be deployed on a AX8008 AEpu (or successor).

7.5.1. IntrusionTerminal properties

1. Applies to: Represents the Areas this AEbc are linked to at the front end. (Data is only represented
here, no changes can be made.)
2. Identifier types: The identifier type must be identical as the identical to the identifier type used at the
web-application. (3 different identifier types can be selected, primary is first checked, etc.)
3. Menu Timeout: Time after LCD Keypad logs off and the user must offer his badge again to login.
4. Menu Detector test Timeout (from AEOS version 2022.2): This timeout value is used when the
Detector test list screen is active. This way an increased value can be used during this test. The
terminal logs out and returns to the start screen when during this time no button is pressed. When
set to 0, no log out is done.
Default value = 30s. Allowed range = 1...32767s, 0= auto log out disabled.
5. Test duration: The duration of a test mode in hours. The time is started for every area individually
when it is put into test mode. When the time expires the area is set to disarmed mode.
6. PIN identification: A PIN identifier can be entered instead of offering a badge. If activated the E button
on the terminal lights up. When the E is pressed all numeric buttons light up to enter the PIN identifier.
7. Initialization priority: set to 10 instead of 50 (default). This prevents that the Intrusion Terminal starts
up to fast (before all other items are ready)

Manual version 21 52
Installation and Configuration | AEOS - Intrusion EN

7.5.2. IntrusionTerminal Beeper

The beeper on the Intrusion Terminal is be used e.g. to indicate the Walk-In or Walk-Out activity. The
binding beep must be connected to the Beep of the Intrusion LCD keypad reader.
For a list of available sounds and their purpose see chapter 20.10: Audible alarms generated by terminal.
The beep on key-press can be activated at the configuration file of the Intrusion Terminal reader (NR file) by
setting the option NA/UL beep.

7.5.3. IntrusionTerminal Backlight

The backlight on the Intrusion Terminal is activated as soon as the terminal is active (e.g. after a badge is
been offered). The binding bl must be connected to the MD of the Intrusion LCD keypad reader for
controlling the backlight. The backlight is automatically set off after the Menu Timeout time.

7.5.4. Intrusion LCD keypad: Tamper

The Tamper switch of the Intrusion LCD keypad can be linked to
• a Detector input, with alarm type TAMPER. Settings: Alarm type: TAMPER, Normally Open, No
Sabotage, No Masking.
or to
• the Tamper input of the IntrusionTerminal AEbc. No settings can be applied here.

7.5.5. Intrusion LCD keypad: Verification (up from AEOS 3.1)

Default the Intrusion LCD keypad reader is activated by offering a badge. With AEOS 3.1 verification (PIN,
verifier type = Pin Port)) can be used by adding an additional AccessPoint AEbc with Verification AEbc and
linking the Inhibit input of the AccessPoint to the Busy output of the IntrusionTerminal AEbc. The badge
number for the IntrusionTerminal AEbc is retrieved from the badge output of the AccessPoint.

The identifier types of the StandardDoor and IntrusionTerminal need to be identical.

Manual version 21 53
Installation and Configuration | AEOS - Intrusion EN

7.5.6. Intrusion LCD keypad: Identification by PIN code (up from AEOS 3.1)
By activating the property PIN identification a PIN identifier can be entered instead of offering a badge. The
PIN identifier is retrieved by the badge input.

As identifier at the IntrusionTerminal the Generic Identifier must be selected, with settings as below:
• Sub type: User definable (use not used number)
• Badge number: Format: Ascii-AlphaNumeric, Bit position: 0, Length: 0 bytes
• Customer code: Format: Ascii-AlphaNumeric, Bit position: 0, Length: 0 bytes (customer code
not used)
For the server the settings as defined at AEmon for the IntrusionTerminal must be copied.

7.5.7. Intrusion LCD keypad: Installer badges vs. user badges (up from AEOS 3.1)
By using the PIN Identifier AEOS enables the option to use badges for all users, but a double PIN identifier
for the installers: a first PIN identifier for the Installer mode, the second PIN identifier for the user
acknowledge. Both numbers must be issued at AEOS with the correct identifier type.
On the IntrusionTerminal screen there is no difference between offering a badge or entering a PIN
identifier, the text and the screen is identical. The keyboard “E” lights up (is active) in case a PIN identifier
can be used.

7.6. Intrusion Panel Tamper

The Tamper switches for the Intrusion Panels and Intrusion I/O units are connected to connector K18 on the
AP3006 PCB . Detection and generating an event can be achieved by linking the Tamp output of the
AP3006s to a Detector Input with alarm type TAMPER.
Settings: Alarm type: TAMPER, Normally Closed, No Sabotage, No Masking.

The Intrusion panels and I/O units have two separate tamper switches (if one of them fails the Tamper
Alarm output OC2 as defined at the Signalling AEbc will be activated):
• Wall tamper
• Cover tamper

Manual version 21 54
Installation and Configuration | AEOS - Intrusion EN

7.7. Inputs: Sensors – detectors

For each sensor connected to the Detector AEbc an alarm type that is related to this input can be selected:
• Alarm type: Tamper, Panic, Burglary, 24H, Hold-up, Technical, etc.

Additional for each input settings for the alarm state must be made (see also chapter 17.9: EOL Resistors
detailed information):
• Type of contact: Normally open / normally closed
• For R1: Alarm state EOL resistor value
• For R2: Masking EOL resistor value
• For R3: Tamper (fault) EOL resistor value
• Output to indicate the logic state (true - false) of the corresponding input

InX

R=3K3
R1 Alarm
R=8K2

R2 Masking

Tamper
GND
R=1K5
R3

The Detector AEbc can handle sensors (PIRs, etc.) using one combined output and sensors having
separate outputs for, e.g., Alarm, Masking and Tamper. Detector number and name is
automatically identical for these separate inputs on the AP3006 PCB.

Manual version 21 55
Installation and Configuration | AEOS - Intrusion EN

7.7.1. Detector properties

Main properties:

• Detectors: Detector specific information (amount and numbering, type alarm, EOL, etc.)
• Automatic inhibit threshold: Amount of input changes that generate an alarm in one arm-disarm
period before this detector is automatically been inhibited.

If the detector is automatically set to inhibit, the corresponding alarms will automatically been reset.
If a value other than 0 is used, certification is no longer valid (use 0 for certified systems).

After selecting Detectors the specific information about the applied detectors can be applied:

• Detector range: Unique number for the detectors over the intrusion system. Use Apply to add the new
range.
The unique number is used in the web-application.

For each number an entry is added where the type and state of connected input can be defined.

Default ‘new’
sensor setting

Edit box

• Default 'new' sensor settings: Sets the default values for the new detectors to be applied (same
settings as below at Sensor settings but here used as default for the new added detectors).
• Description can be used to specify, e.g., the location of this detector. If no description is entered, the
chosen alarm type (in capitals) is automatically used.

Manual version 21 56
Installation and Configuration | AEOS - Intrusion EN

• Sensor settings: Specific settings for each connected sensor can be adjusted with the Edit box ([…]).
E.g., when selecting the first detector: Type is Burglary

Specific settings: Normally closed, Sabotage and Masking enabled, EOL resistors are default
(R1=3300, R2=8200, R3=1500 Ohm). For this input the Output is activated (D1.1)
If as above multiple states are used the MASK and TAMPER alarms will be generated automatically if
applicable. The main AlarmType still is BURGLARY.
SIA begin / end can be used at the types: PANIC, 24H and TECHNICAL to use specific (user definable)
SIA codes:
o Empty field: Use default (Nedap dialler defined) code
o ‘-‘ Skip remote notification (send no code)
o 2 letter code: Use this code
E.g., SIA begin=‘FA’, SIA end=’-‘ will result in SIA code ‘FA’ when the alarm is started and no
remote notification when the alarm is restored. While begin=’-’, end=’-‘ will skip all remote
notifications for this sensor.
With the Set delay this detector will during this time (after arming) not generate alarms.
Buttons Move up and Move down are only used to move the sensor in the list.
For Detector 4 there are two inputs used, one for Burglary and one for Sabotage.

When Sabotage is activated and R1 and R3 are set to 0, the EOL values are determined by the used
firmware (default 4K7).

For more information about EOL resistors see chapter 17.9: EOL Resistors detailed
information.
For older hardware with fixed EOL R1 and R3 must always be set to 0 (even if no sabotage is
used).

• Output: Enabling this checkbox results in an additional output on this Detector AEbc. This output
represents the logical state of the connected sensor at the corresponding input. This output can be
used, e.g., to link to other AEbcs.

Manual version 21 57
Installation and Configuration | AEOS - Intrusion EN

• Masking reset output (from AEOS version 2022.2)

In the Detector AEbc properties, the masking reset output can be enabled. The output will be added
to the AEbc with the matching sensor number (Mx.x).

When a masking alarm occurs:

• In the terminal, in the "restore alarms" screen, select the masking alarm.
• The middle softkey will display an "R" when the reset output can be activated. Pressing the button
will make the output active for 1 second.
• The middle softkey will display a "V" when the masking signal is no longer active and the masking
alarm can be acknowledged.
• The middle softkey changes from "R" to "V" dynamically when the masking signal ends. No need to
exit the screen.

Manual version 21 58
Installation and Configuration | AEOS - Intrusion EN

7.8. Outputs: Signalling

At the Signalling AEbc one (or more) Alarm rule(s) are made which will affect an output in combination with
the Area as determined at the web-application. This Alarm rule is the combination of an alarm type and the
sensor mode when this alarm type must become valid.
The outputs of the Signalling AEbc can be linked to the available hardware outputs to, e.g., activate an
alarm light or buzzer.

Signallers are independent to alarms. The signallers can be programmed by approved user,
alarms are determined by the system itself and cannot be changed.

7.8.1. Signalling properties

The edit box ([…]) behind Signals opens the Signals screen for adding and changing the signals.

01

03
04 02

Following settings can be made:

01 Signal range: Unique range over the intrusion system. Use Apply to add this range.
This number (e.g., Signal 4) together with the Description is shown in the web-application as Reporter.

Alarm rule(s): Activated by the edit box ([…]):

02 First select the type of signal that must be used: This can be ALARM or AREA-STATE

Manual version 21 59
Installation and Configuration | AEOS - Intrusion EN

Now the rules for the chosen type can be composed:

The Alarm Type together with the Mode determines the activation of this alarm,
• ALARM for Alarm Types: e.g. :
o TAMPER
o PAC AND LOG
o PANIC
o BURGLARY
o 24H
o HOLD-UP
o TECHNICAL
o MASKED
o NO ALARM
o FAULT
• Mode determines the condition the Alarm Type must be in to activate the Rule:
o ARMED
o TEST
o empty
The mode determines in which situation the Rule must be checking the detector (e.g.,
detector becomes active in TEST)
A mix of several rules (OR function) can be achieved by using the Add button (see Signal Nr
3):
• Ignore in installer mode: If activated this signaller will not become active when the
installer is logged in. So during maintenance some signallers can easily be disabled.

In this example the rule becomes true if:

sensors of the type Burglary during the
armed state becomes true
OR
sensors of the type Technical during the
armed state becomes true.

Alarms can be generated by the detectors or by the system. E.g., if the dialler fails, a FAULT alarm
will be generated.

Only the Burglary alarm is depending on the armed / disarmed state. All other alarms
will in all situations (armed AND disarmed) always be generated.

• AREA_STATE: e.g.:
o ARMED
o DISARMED
o WALK-IN TIME ACTIVE
o WALK-OUT TIME ACTIVE
o TEST
Area_States presents the state of an area. These are valid for all detectors in this area (at the
web-application the link between the signal and the area is determined).

Manual version 21 60
Installation and Configuration | AEOS - Intrusion EN

03 Output settings: Must the output be Inverted, Activation time (0 means continuously activated) or
Toggle time can be stated here.
Output inverted: If checked the output will be active low (no rule active results in
activated output)
Active time (ms): Time during which output will be activated
(0 means continuously activated, till rule becomes false
Toggle time (ms): During active time the output can be toggled (set on/off) with this on/off
time.
Restart signal: If set output is reactivated for every new event that matches a rule.

An output for a warning device must be minimal 90 seconds and may not exceed the
activation time of 15 minutes (900 sec). If the active time exceeds these values, the
certification is no longer valid.

04 Applies to: Represents the Areas and Routes these signals are linked to at the front end.
Data is only represented here, no changes can be made.

7.8.2. Signalling Test situations

Only an complete Area can be set in Test by the user.
• An area that is put to test can be indicated by adding next rule:
Type AREA_STATE with Mode TEST

• If an output must be activated when a detector (e.g., a Burglary detector) becomes active during the
test a signaller can be added as:
Type: ALARM, Alarm Type: BURGLARY with Mode Test

Of course this Signaller must still be add to the corresponding Area(s)

If an Area is in Test, alarms are NOT sent to the ARC, but still are logged into the alarm log.

Manual version 21 61
Installation and Configuration | AEOS - Intrusion EN

7.9. Outputs: Dialer

Sending messages to the Monitoring centre is controlled by the Dialer AEbc (communication by the
ComPortIntegrator to the dedicated dialer).
To connect the dialer over USB to the AEpu the ComPortIntegrater AEbc expands the USB port of the AEpu
to a serial communication channel. The dialer must be connected to show the ComPrt.

Due to the limited messages as sent by the dialer (64 characters max) use short names for AEbcs
and descriptions, otherwise data will not be complete received at the ARC (relevant information
can be missed.

7.9.1. ComportIntegrator properties

No settings have to be made. At Properties the Address offset can be changed (only needed for situations
where several serial ports are connected by ComportIntegrator AEbcs.) After deployment the additional
serial channel is visible in AEmon. In example above: ComPrt on address 408.

7.9.2. Dialer settings

• Dialer configuration: Dialer used is ChironIrisTouch. (see chapter 19.10 : Dialler)
Activate edit box for detailed settings related to the dialer (Account name, IP addresses, GPRS
information, etc.

Supplementary to the unique dialer

account number you set in this
dialer configuration, monitor
centre account numbers can be
used for reporting area specific
events (from AEOS 3.1.7, see
section 8.4.4).

The GPRS enabled is optionally for

situations where the GPRS
connection is wished for back up to
the main communication channel

Polling failed alarm time (30): Between ATS and dialer

Ethernet failed alarm time (30): Between dialer and ATS
GPRS failed alarm time (30): Between dialer and ATS

Manual version 21 62
Installation and Configuration | AEOS - Intrusion EN

USB enabled is only to be used for non-certified systems, where the USB connection between
dialer and AEpu is used instead of the certified RS232 communication on the dialer.
Software version: Must be at least 1.14.1

Settings for Polling failed alarm time (30),Ethernet failed alarm time (30), GPRS failed
alarm time (30) and USB enabled (off) must be left unchanged, to apply to the
certification regulations.

• Communication logging enabled: Adds debug information in the AEpu logfile, only for debug purposes.
• Alive message period time: If enabled (value > 0) the dialer periodically transmits an alive message (SIA
event RP0000) to the alarm centre.
• Alive message start time: The time in hours and minutes the first alive message should be transmitted.

All dialer related settings are made in this AEbc, there are no specific settings to be made in the dialer itself.
Transmissions between AEpu and dialer is repeated every 5 seconds in case of communication problems
between AEpu and dialer, this value cannot be changed.

• Dialer AEbc property 'Listen to all areas'

If enabled, the dialer listens to all areas in the system when no area assignments have been
configured in the server. While this is practical feature for small systems, it may cause performance
problems for large systems. If disabled the dialer listens only to server configured areas: without
configured areas, the dialer will not operate.
Default value:
enabled in AEOS version 2021.1 and older versions
disabled from AEOS version 2021.2
See also the AEbc Intrusion Descriptions manual

7.10. Battery and Power control

Battery and power is checked by the PowerSense AEbc and generates alarm events in case of irregularities
(and its corresponding outputs are activated). The generated alarms are of the type FAULT and will activate
the corresponding Signal if so configured
On the AP3006 LED indicators are available for indicating mains available (AC OK), Battery low (BAT LOW)
and Battery operation (BAT).

If no batteries or the dedicated power supply is not used connected this must be set at the
PowerSense Properties (see below)
Battery supply will only operate after power up with mains supply. The AP3006 will never power
up from batteries only.

Manual version 21 63
Installation and Configuration | AEOS - Intrusion EN

7.10.1. PowerSense Properties

With the properties of the PowerSense some control items can be disabled, e.g., for the Intrusion I/O unit
there is no Power Supply including batteries used, so these checks can be skipped. The corresponding items
will not be tested.

1. Check mains: Must mains be checked (only when power supply is

connected)
2. Mains loss minimum duration: Time that is allowed for mains power to be interrupted
3. Check battery: Must battery be checked (only when batteries are
connected)
4. Battery capacity check time: Time (once a day) when the battery capacity test is
activated.
5. Battery capacity check duration: Set to 10 sec. (max. time is limited by AP3006 PCB to 17
seconds)
6. Battery capacity check threshold: Voltage below during battery capacity test will cause
alarm
7. Battery voltage threshold: Voltage during Battery operation (no Mains power is
available)
8. Battery empty threshold: Used to check if a new battery is present
9. Raw voltage threshold: Internal voltage where, e.g., AEbus voltage is retrieved
from
10. Output voltage threshold: Voltage of the sensor power output for feeding sensors

Use above settings for an EN-compliant installation.

Manual version 21 64
Installation and Configuration | AEOS - Intrusion EN

7.10.2. PowerSense checking power related items

Following items are checked:
• Mains supply (230VAC)
No settings required, test continuously active
At failure: Event (AT/AR: AC power trouble) is generated and output mfal is activated
• Battery low voltage (= SD low voltage)
Battery voltage threshold must be specified.
If mains supply is not present, this test is continuously performed, otherwise each 4 minutes.
At failure: Event (YT/YR: Battery failure) is generated and output bval is activated
When battery is changed (see note 1) or mains is reconnected, Battery low voltage is not monitored for
24 hours.
• Battery present
No settings required, test continuously every 4 minutes (battery load is very short activated every 4
minutes to perform this test)
At failure: Event (YM/YR: Battery missing) is generated and output bval is activated
• Battery capacity
Voltage for threshold, time and duration of the test (once a day) must be specified. Test can also be
performed manually at AEmon (see below)
Once a day at the Battery check time (battery load is activated during stated Battery check duration time
to perform this test).
At failure: Event (YT/YR: Battery failure) is generated and output bval is activated
If during this test the mains supply fails, this test is immediate stopped.
This test can only be executed max 10..15 minutes after the last time this test is performed.
When battery is changed (see Note 1) or mains is reconnected, Battery capacity is not monitored for 24
hours.
• Battery loading circuit correct
No settings required, test runs continuously.
At failure: Event (YT/YR: Battery failure) is generated and output bval is activated
• Vraw (including AEbus voltage) (= low output voltage 24 VDC output)
• Raw voltage threshold must be specified, test continuously active
At failure: Event (YP/YQ: Power supply trouble) is generated and output ival is activated
• Sensor Power outputs (= low output voltage 12 VDC output)
Output voltage threshold (lower value) must be specified, test continuously active
At failure: Event (YP/YQ: Sensor power supply trouble n) is generated and output sval is activated
• Fixed settings:
o 12 VDC overvoltage protection voltage value: 14,7 VDC.
If exceeded the Sensor Power outputs (including LCD keypad reader) are terminated (tested
every 10 seconds for automatic recovery).
o 24 VDC overvoltage protection voltage value: 31 VDC.
If exceeded the 24 VDC Power outputs is terminated, re-power to recover.
o Deep discharged protection to the batteries is checked/regulated by the power supply at 20 VDC
± 1V

For detecting a new battery state the battery must be disconnected for at least 5 minutes.
Property ‘Battery empty threshold’ is used to check for a new battery.

Manual version 21 65
Installation and Configuration | AEOS - Intrusion EN

7.10.3. PowerSense manual activate battery capacity

The Battery capacity test is performed once a day at the stated time. In some situations it can be useful to
manually start this test (e.g. by the installer). This can be done at the hardware view at AEmon (only for
persons having the level 3 rights).
At AEmon go to the Hardware view, open the AP3006, open PowerCheck, select Check battery now and at
the right part of the screen, at the Property Value fill in 10 and click on the Set button.

The Battery capacity test will be performed in a short time from now, depending on the last test performed
(delay could be around 2 minutes).
State: digital representation of PowerCheck state: (0xb = 01011, see explanation below):
Bit 0: Mains presence (1)
Bit 1: Battery presence (1)
Bit 2: Emergency supply present (0, not applicable for AP3006)
Bit 3: Battery charging (1)
Bit 4: Battery capacity failure (0)
Values at Input Values are: Vraw, Vbat, VSensor1, VSensor2, VSensor3, VSensor4 (VRead1, VRead2). The
represented values are the actual values, so measured at moment from opening these screen. (VRead up
from AP3006 PMS D)
Overvoltage protection: only for experienced users: by setting a 0 the corresponding VSensorX is not
checked.

Only to be used after consulting the manufacturer.

Manual version 21 66
Installation and Configuration | AEOS - Intrusion EN

7.11. Controlling Areas by hardware inputs: AreaControl

By the AreaControl AEbc the assigned areas (at the AEOS front end) can be controlled by means of
hardware contacts. (See also AEbc Intrusion Descriptions)

Inputs:
• Switch:
Arm / disarm the related area(s).
Normal or Pulsed (toggles).
Outputs
• On:
Indicate the arm state of the assigned area(s).
• NotOk:
Indicates that the assigned area(s) cannot be armed because of a detection and / or alarm.

By means of the AEbc properties forced arming can be made possible (override alarms).
With Forced arming it is possible to automatically restore open alarms, preventing detectors been inhibited
because there are still open alarms).:

The Area control is represented as a Reporter in AEOS (and of course must be added to one or more areas).

7.12. Generating AEmon configuration by XML

At AEmon it is possible to save the AEpu configuration and also separate AEbcs in XML format (Save as
.XML). The saved file can be changed and re-loaded again at AEmon to complete your configuration.

Manual version 21 67
Installation and Configuration | AEOS - Intrusion EN

8. AEOS: Intrusion settings

Hardware related configurations and settings are made by AEmon.
The devices (AEbcs) added at AEmon will automatically be discovered by the AEOS system and can be used
by AEOS now (e.g., added to Profiles and Users/Carriers to get control over the Intrusion system).

8.1. General overview

AEmon Web-application

Routes Schedules
Detectors
One or more Area Functions User type and
Area Functions
sensor inputs

Dialler Template

Signalling Reporters /
Alarm type with System Devices
rules
Users
Intrusion Panel
LCD keypad
Identifier type Identifier type Identifier nr

Step to follow (assuming card credentials and schedules are already available in AEOS):

Define Areas
Step
Detectors, Reporters and system devices that are automatically detected can be selected and
01 added
For each areas must be defined if this area has additional functionality as an system area.

Step Define Templates

Combination of areas and time schedules, with for each individual area the area functions (arm,
02 disarm, etc.) that a user may perform by the Intrusion LCD keypad reader on this area.

Step Link Intrusion template to a carriers

At the carrier screens the intrusion templates can be added to the carriers, together with the
03 setting of system user / installer and if this user is authorized to view locally the intrusion
logfile.

Manual version 21 68
Installation and Configuration | AEOS - Intrusion EN

After the Intrusion specific settings are made the Intrusion parts can be used as part of the overall AEOS
system:

Step Graphical Alarm Handler

At the graphical alarm handler a total overview of the Intrusion parts and Access Control can be
04 shown on the same map.
Cameras can be activated as soon as an Intrusion alarm is detected, the Intrusion system can be
controlled (arming, disarming, restoring alarms, isolate detectors, etc.) from the Graphical
Alarm Handler.

Step Use responses to events

As the Intrusion components acts like other AEOS components the existing features of AEOS
05 can easily be extended with the specific needs for the Intrusion parts.

Step Use other AEOS functions

As Intrusion is part of the total AEOS system, many other AEOS features can also be used for the
06 Intrusion related items.

8.1.1. Representation of Intrusion AEbcs for Intrusion

The Intrusion components (AEbcs) as added with AEmon can be used at different items in AEOS for the
Intrusion related menus. However their name (representation) is not always exactly the same:

• Area: (generated by the user at AEOS, no AEbc)

o As AlarmItemArea: for events (alarm handler, responses)
o As Areas: for statuses (alarm handler-Status Rule Templates / Command Templates)
• Detector
o As Intrusion Detector: each individual detector is shown as its unique number (1, 4, 231)
Notifies sensor detection / tamper
o As AlarmItemDetector: for events (alarm handler, responses)
o As Detectors: for statuses (alarm handler-Status Rule Templates / Command Templates)
o As Detectors: for device messages
• Signalling
o As Intrusion Reporter each individual Signal is shown with unique number (Signal 1, Signal
4)
Responds on detector and system device notifications
o As Intrusion AlarmDevice: D-name (D-Signal 1, D-Signal 4)
Notifies signal device tamper alarm
o As AlarmItemSignaller: for events (alarm handler, responses)
o As Signallers / StandardAlarmItems: for statuses (alarm handler-Status Rule Templates /
Command Templates)
o As Signalling: for device messages
• IntrusionTerminal
o As Intrusion Reporter: D-name (IntrusionTerminal.1.terminal)
Responds on detector and system device notifications
o As Intrusion AlarmDevice: D-name (D- IntrusionTerminal.1)
Notifies terminal tamper alarm
o As AlarmItemTerminal: for events (alarm handler, responses)
o As Terminals / StandardAlarmItems: for statuses (alarm handler-Status Rule Templates /
Command Templates)
o As IntrusionTerminal: for device messages
• Dialler
o As Intrusion Reporter (Dialler.1.dialler)

Manual version 21 69
Installation and Configuration | AEOS - Intrusion EN

Responds on detector and system device notifications

o As Intrusion AlarmDevice: D-name (D-Dialler.1)
Notifies dialler fault alarms
o As AlarmItemDialler: for events (alarm handler, responses)
o As Diallers / StandardAlarmItems: for statuses (alarm handler-Status Rule Templates /
Command Templates)
o As Dialler: for device messages
• PowerSense
o As Intrusion AlarmDevice: D-name (D-PowerSense.1)
Notifies mains, power supply and battery fault alarms
o As AlarmItemPowerMonitor: for events (alarm handler, responses)
o As PowerMonitors / StandardAlarmItems: for statuses (alarm handler-Status Rule
Templates / Command Templates)
o As PowerSense: for device messages
• SystemMonitor
o As Intrusion Reporter: name.StateLogger (SystemMonitor.1.StateLogger)
Responds on detector and system device notifications
o As Intrusion AlarmDevice: D-name (D-SystemMonitor.1)
Notifies ‘processing failure’ fault alarms
o As AlarmItemSystemMonitor: for events (alarm handler, responses)
o As SystemMonitors / StandardAlarmItems: for statuses (alarm handler-Status Rule
Templates / Command Templates)
o As SystemMonitor: for device messages
• AreaControl is not shown in AEOS
• TaggedServiceManager: is not shown in AEOS

8.2. Set system properties for Intrusion

With AEOS it is possible to use the existing intrusion system (AP5002 based) and / or the new intrusion
system (Intrusion (2)).
Not all customers are using Intrusion, even not all customers are using the combination of the old and new
intrusion into the same AEOS system.

The two System Properties(21.01 and 21.02) at Administration – Maintenance – Settings – System
properties) are used to enable the corresponding Intrusion menus and the visibility or the corresponding
intrusion templates on the carrier screens (also at least one Intrusion – Zone must be in the license).

Manual version 21 70
Installation and Configuration | AEOS - Intrusion EN

8.3. Intrusion Licenses

For Intrusion (2) the detectors are licensed under license number 8014930 (Intrusion – Zone), each unique
detector is counted as zone. Combination with existing intrusion zones is possible, all zones + detectors are
counted.

For Intrusion (2) only the used detectors are licensed, all other items are license free.

All detectors are counted in the license, also the detectors that are not connected.

8.4. Maintain Areas

At menu Configuration – Intrusion (2) – Maintain Areas the Areas including the corresponding Detectors,
Reporters, System devices (former alarm devices) and Monitor centre accounts can be generated.

At the Areas screen the Detectors, Reporters and System devices can be changed by use of the Add and Del
buttons. With the Add button all available items will be shown, multiple selection is possible.

If the Area name is starting with a number and a space (e.g., 146 Area1), this number is
automatically transferred to the corresponding part for the dialler (see appropriate chapter for
the dialler).

Manual version 21 71
Installation and Configuration | AEOS - Intrusion EN

8.4.1. System Area

With the check box behind is system area this area can be updated to a system area, which means that
when on one of the added Terminals (as Reporter) one of the areas is armed all items from this system area
are also checked (More information about the system area is at chapter 2.1.2: System area).

8.4.2. Reporters
At the Reporter part the Intrusion LCD keypad readers (Intrusion Terminal) can be added belonging to this
area. From these Intrusion Terminals this area can be armed / disarmed, and the alarm messages belonging
to this area will be shown here.

Beside adding the correct terminals to an area also this area must be added to the Template
complete with the correct areas functions, otherwise the user cannot operate by this terminal.

8.4.3. System Devices (before AEOS 3.02: Alarm Devices)

System devices are almost identical to Detectors, the main difference is that the System devices are mostly
hardware related alarms, e.g., device connections when an AEpack is missing, or PowerSense alarms in case
the power supply fails.

Manual version 21 72
Installation and Configuration | AEOS - Intrusion EN

8.4.4. Monitor centre accounts (from AEOS 3.1.7)

It is possible to send intrusion alarms from different areas to different dialler accounts. This means you can
monitor the alarms for individual intrusion areas and still use a single dialler. This can be activated in the
AEOS front end, by enabling the Use multiple monitor centre account system property (no. 21.03).

In the Intrusion (2) section, you can now create different 'monitor centre accounts' and add these accounts
to individual intrusion areas. The account numbers (1 to 6 digits) will be included in the ARC messages.

The 'monitor centre account' number can be used for reporting area specific events. Events that occur in
system areas or in areas without a configured 'monitor centre account' number are reporting using the
dialler’s own account number. This is the account number that has been configured in AEmon (Dialler
configuration, see section 7.9.2). This will also apply to events that occur in overlapping area parts with
different account numbers.

Manual version 21 73
Installation and Configuration | AEOS - Intrusion EN

8.5. Maintain Routes

At menu Configuration – Intrusion (2) – Maintain Routes detectors and reporters can be assigned to a
Route.

At the Reporters the IntrusionTerminal must be selected where this Route must be indicated (on the display
and by the buzzer), the Signal can be used to activate an output if this route is active.

First/Last detector is used for making the selection for starting the Walk in (First), or ending the Walk out
(Last). Optional an order for detectors can be added (Follower detectors). If this order is not exactly
followed an alarm is generated.

By overlapping routes do not use the follower function (except for matching walk-in and walk-
out routes.

Manual version 21 74
Installation and Configuration | AEOS - Intrusion EN

8.6. Maintain Detectors / Reporters / System devices

At menu Configuration – Intrusion (2) – Maintain Detectors / Reporters / System devices items can be
checked and removed if not longer used. It provides also an overview where an item is used (in which area).
At column Last time seen the time when this item was discovered for the last time is filled in.

Items that are not discovered any longer at the AEOS network are not automatically been
removed.

Manual version 21 75
Installation and Configuration | AEOS - Intrusion EN

8.7. Maintain Intrusion Templates

An Intrusion Template is a combination of:
• Areas
Defined at Configuration – Intrusion (2) – Maintain Areas
An area can be used at several templates
• Area functions
The functions that the user is allowed to perform at the Intrusion LCD Keypad reader (e.g., Arm,
disarm, View alarms, Inhibit, etc.)
• Schedule
Time schedule as defined at Authorisation - Maintenance – Day/time schedules
These schedules are also used for access control.

At Authorisation - Maintenance – Intrusion (2) templates the templates can be added / changed.

Selecting an Intrusion (2) templates shown the overview of added Areas, Area functions and used Schedule.

Manual version 21 76
Installation and Configuration | AEOS - Intrusion EN

After selecting one or more of the areas the functions and Schedule for this selection can be changed:

Multiple selection of areas to make changes for area functions and/or the time schedule is
possible.

The template is now ready to be added to a carrier (at the carrier screens).

8.8. Maintain carriers

At the carrier screens an Intrusion Template can be added to this carrier.

Manual version 21 77
Installation and Configuration | AEOS - Intrusion EN

At the Intrusion (2) part beside the Intrusion (2) template also the selection if this user is a:
• SYSTEMUSER
The system user cannot restore all alarms, some technical alarms can only be restored by the
Installer.
• INSTALLER
The installer can restore all alarms (both technical and normal alarms) and can isolate detectors,
but for getting access to the Intrusion LCD Keypad reader the Installer needs confirmation by a
System user.
Up from AEOS 3.1.1:
The system user can activate in the configuration menu of the Intrusion Terminal the ‘Installer
Login’ mode. If active any installer with correct rights for this Intrusion Terminal will gain access by
offering his installer badge (no system user badge is needed). A timer is also added, limiting the
maximum access time for the installer. The installer can during this timer log in as often as required.
Starting and stopping the installer mode is logged to AEOS.
During installer mode sirens can be inhibited, helping the installer in his work without disturbing
other people. To activate this mode the installer must activate the ‘Installer mode’ at the
terminal. The signallers where the option Ignore in installer mode is checked will now not be
activated (setting in Signaller AEbc at AEmon).
Before AEOS 3.1.1:
The Installer presents his badge, Intrusion LCD Keypad reader asks for ‘Present System User
badge’, a system user presents his badge and after that the Intrusion LCD keypad reader can be used
by the Installer.
For each new login to the terminal this procedure must be used.
With the View Log checkbox this user is enabled to check the Intrusion logfile at the Intrusion LCD Keypad
reader.

8.8.1. Using PIN as identification (up from AEOS 3.1)

For INSTALLERS it can be useful to use PIN identifier instead of badges. This means that for the installer and
the corresponding system user a PIN identifier must be issued. (see also chapter 7.5.7), the identifier
settings at AEOS must be identical as defined at the properties of the IntrusionTerminal AEbc.
Advantage is that the Installer can handle the login procedure on its own, without having a system users
badge. The installer must have two PIN identifiers: one for activating the installer function, the second for
acknowledge as system user. As the display on the IntrusionTerminal asks for Present System User badge
the installer can enter then the system users PIN identifier.
By issuing the PIN identifiers only for a short period this option makes it flexible to give Installers only
temporary access to the Intrusion Panels, instead of handing over badges.

Up from 3.1.1 this is not needed any longer because of the changed installer mode.

Manual version 21 78
Installation and Configuration | AEOS - Intrusion EN

9. AEOS Intrusion: Graphical Alarm Handler

For the Graphical Alarm Handler Intrusion acts like all other AEOS components. Their live status can be
represented, commands can be given and alarms can be generated. See also documentation about the
Graphical Alarm Handler.
For showing the live status or executing a command the name of the Intrusion component can differ, see
chapter 8.1.1: Representation of Intrusion AEbcs for Intrusion.
This chapter describes some aspects for adding the intrusion components into the graphical alarm handler.

There are two different locations where alarms must be handled: At Intrusion and at the Alarm handler.

9.1. General information

At the status rule templates (Configuration – Alarm Handler – Status Rule Template) the different intrusion
component groups can be selected (only components that are available on the AEpus are shown) for
showing their statuses.

The group StandardAlarmItems is a group for Diallers, PowerMonitors, Signallers,

SystemMonitors and Terminals. These devices can only show their live status (idle, fault and
maybe in the future also tampered) For configuration purposes it is easier to have only one
group to defined, instead of each individual item of this group

Alarms can be activated by different situations. As soon as an alarm is activated, it stays active (even if the
cause is gone) till this alarm is restored. (there is no automatic end of an alarm).

For Detectors and Signallers each individual item (each unique number) is seen as separate
component. There can be identical numbers on different AEpus.

9.2. Multiple disciplines to control Intrusion and show actual status

The Intrusion system can be controlled by different disciplines, all controlled by AEOS:
• Intrusion Terminal
• Graphical Alarm Handler face
• AreaControl AEbc

For AEOS it does not matter where the action to e.g. arm or disarm is activated. The correct status is always
available at all items been involved with intrusion.

At the graphical alarm handler the actual status of the Intrusion parts (and all other AEbcs) is shown. As the
actual (live) status is shown, it results that changes made at the Intrusion Terminal (e.g., arming or override
a detector) or by arming by means of hardware inputs (AreaControl AEbc) will be directly presented at the
Alarm Handler face.

Manual version 21 79
Installation and Configuration | AEOS - Intrusion EN

9.3. Intrusion Alarm restoring vs alarm handling in alarm handler

Alarm restoring for intrusion is a separate action to alarm handling in the alarm handler.

Alarms from Intrusion can be made visible into the (graphical) alarm handler (by adding them as Alarm
point together with the correct event definition of this alarm), but closing these alarm will not
automatically restore the alarm at the Intrusion part.

Alarms generated by Intrusion always must be handled as Intrusion alarm (restoring at the Intrusion
Terminal or by the component (e.g. detector) at the Graphical alarm handler.)
If these alarms are also added as an alarm at the Graphical alarm handler, these alarms must also be
handled for the Alarm handler part. There is no direct link (AEOS 3.0.1) between these two different type of
alarms.

E.g., Burglary alarm becomes active:

• Intrusion
Alarm is generated and is be handled at the Intrusion part as an Intrusion (burglary) alarm. This
alarm can be restored at the Intrusion Terminal or a the Graphical Alarm Handler using the right
mouse button option to restore this alarm.
• Graphical alarm handler
If defined that an event (in this example the Burglary alarm) should also generate an Alarm at
the Graphical Alarm Handler, this alarm event has no connection / link with the above intrusion
handling.
If the alarm event occurs, the Graphical Alarm Handler will pop up the alarm in the Alarm
Handler, and handles as defined at the Graphical Alarm Handler.
When the Alarm is closed at the Graphical Alarm Handler is it not automatically been restored at
the Intrusion part.
To prevent that an alarm is closed at the Alarm Handler before it is restored at Intrusion, the
Is idle option at the Status can be used. If active, this particular alarm can only be closed if the status
of this alarm point is idle (e.g., as idle take the default state where the detector is inactive).

9.4. Tamper and Fault alarms

Tamper and fault alarms are handled differently:
Tamper: Tamper is generated at the detectors (by selecting the alarm type: Tamper) or by devices
when the connection is lost. Tamper sub types are:
• Sabotage, open
• Sabotage, shortcut
• Enclosure opened
• Device connection

Tamper as generated by wall tamper and/or cover tamper must be linked to an detector. (Here
the alarm type Tamper is selected). For checking the current state of this tamper input you must
check the detection.

Manual version 21 80
Installation and Configuration | AEOS - Intrusion EN

Fault: Fault are system messages, e.g., battery failure, dialler failure, masking. Sub types:
• AC power
• Battery missing
• Battery low
• Power supply trouble
• Sensor supply trouble
• Dialler not polled
• Dialler no Ethernet
• Dialler no GSM
• Dialler no communication

9.5. Configuration aspects

At Configuration / Alarm Handler / Status rule template: Maintain status rule template – Status rules the
different statuses for the individual components that must be shown are defined.
In the lists below the grey items are shown in the AEOS menus but have no function for this item.

9.5.1. Available statuses for Areas (Component: Areas)

For areas the status can be for the total area (*Mode) or for at least one of the detectors in this area
(*Signal):

Status: *24hour alarm / *Burglary alarm / *Fault alarm / *HoldUp alarm / *Masked alarm /
*Panic alarm / *Tamper alarm / *Technical alarm
Represents: Detector in this area its alarm status or the alarm that is generated by an device
in this area (Tamper, Fault)
Value:
• xxxxx alarm is active
• (xxxxx alarm is passive will never occur, alarm is ended with restore)
*Mode
Represents: the mode this area is in.
Value:
• Armed
• Test Area in test mode
• Disarmed
*Signal
Represents: Status of the detectors in this area
Value:
• Idle No detectors are active (having a value as below)
• Detection At least one detector is active
• Fault At least one detector is in Fault (Mask is a fault)
• Tampered At least one detector is Tampered
Fault and Tampered will result directly into an alarm.

Manual version 21 81
Installation and Configuration | AEOS - Intrusion EN

9.5.2. Available statuses for Detector (Component: Detector)

Here the different statuses a detector can become are stated. Some statuses are directly related to the
detector, other more to the area the detector is belonging to.

Status: *24hour alarm / *Burglary alarm / *Fault alarm / *HoldUp alarm / *Masked alarm /
*Panic alarm / *Tamper alarm / *Technical alarm
Represents: Detector as defined for this status its alarm status (activate or passive)
Value:
• xxxxx alarm is active
• (xxxxx alarm is passive will never occur, alarm is ended with restore)
*Mode
Represents: Mode of this detector
Value:
• Isolated Detector is isolated
• Armed Detector is armed (Area for this detector is armed)
• Test Detector is in test
• Inhibited Detector inhibited
• WalkinRouteArmed Detector armed for WalkIn route
• Disarmed Detector is disarmed (Area for this detector is
disarmed)
• Overridden Alarm for the sensor of this detector is overridden
*Signal
Represents: Status of this detector
Value:
• Idle No detectors are active (having a value as below)
• Detection At least one detector input is active
• Fault At least one detector is in Fault (Mask is a Fault)
• Tampered At least one detector is Tampered
Fault and Tampered will result directly into an alarm.
Detection is the representation of the input(s) of the detector (active or passive).

The definition at the Detector how the inputs are checked is resulting in the Signal: A detector
with multiple input statuses will result in a Tamper if this detector is removed (alarm type is, e.g.,
Burglary). If at the detector as alarm type ‘Tamper’ is selected, the status Detection must be used
to show this status.

Manual version 21 82
Installation and Configuration | AEOS - Intrusion EN

9.5.3. Available statuses for StandardAlarmItems

These statuses are valid for this group, but also for the individual items as been covered by this group.

Status: *Fault alarm

Represents: Fault status of this device (e.g., connection is lost with this AEbc)
Value:
• Fault alarm is active
• (Fault alarm is passive will never occur, alarm is ended with restore)
*Tamper alarm
Represents: Tamper status of this device
Values:
• Tamper alarm is active
• (Tamper alarm is passive will never occur, alarm is ended with restore)
*Signal
Represents: Actual status of this device
Value:
• Idle
• (Fault Device is in fault state (e.g., no connection) )
• (Tampered Device is tampered: not available yet)
Fault and Tampered will result directly into an alarm.

9.5.4. Available alarms (adding alarmpoints)

For activating an alarm at the alarm handlers following Intrusion (2) components can be selected. They are
divided into two different types: The AlarmDevices (these can generate alarms) and the AEbcs (these have
only the device connection events):

• AlarmItemArea
Alarms as generated by a status change of an area.
Event:
o Alarm not available
Status: Begin (- End)
Alarm type: 24 hour – Burglary – Fault – Holdup – Masked –
Panic –Tamper - Technical
o Alarm restore not available(is actually the end of an alarm)
Alarm type: 24 hour – Burglary – Fault – Holdup – Masked –
Panic –Tamper - Technical
o Arm/Disarm
Forced arm: Forced - Unforced
Arm/disarm: Arm - Disarm
o Test
Start/stop : Start - Stop

Manual version 21 83
Installation and Configuration | AEOS - Intrusion EN

• AlarmItemDetector
Alarms as generated by a status change of a detector
Event:
o Alarm
Status: Begin (- End)
Alarm type: 24 hour – Burglary – Fault – Holdup – Masked –
Panic –Tamper - Technical
o Alarm restore (is actually the end of an alarm)
Alarm type: 24 hour – Burglary – Fault – Holdup – Masked –
Panic –Tamper - Technical
o Inhibit
Start/stop : Start - Stop
o Isolate
Start/stop : Start - Stop

• AlarmItemDialler / AlarmItemPowerMonitor / AlarmItemSignaller / AlarmItemSystemMonitor /

AlarmItemTerminal
Event:
o Alarm
Status: Begin (- End)
Alarm type: (24 hour) – (Burglary) – Fault – (Holdup) – (Masked)
– (Panic) –Tamper – (Technical)
o Alarm restore (is actually the end of an alarm)
Alarm type: (24 hour) – (Burglary) – Fault – (Holdup) – (Masked)
– (Panic) –Tamper – (Technical)

• ComPortIntegrator / Detectors / Dialler / IntrusionTerminal / PowerSense / Signalling /

SystemMonitors
Event:
o Device connection
o Device IO
o Device network

9.5.5. Adding statepoints

For state points only the corresponding component must be selected (and the state rule template added).

9.5.6. Commands
Commands are defined at (Configuration – Alarm Handler – Command Template) for the different
component groups. The groups are the same as at the status templates.
Commands can be activated at the Graphical Alarm Handler by clicking with the right mouse button on the
corresponding icon.

9.5.6.1. Commands Area (Component: Areas)

Command: Arm
Disarm
Force arm
Stop test
Test

Manual version 21 84
Installation and Configuration | AEOS - Intrusion EN

9.5.6.2. Commands Detector (Component: Detector)

Here the different statuses a detector can become are stated. Some statuses are directly related to the
detector, other more to the area the detector is belonging to.
Command: Inhibit
Isolate
Restore alarms
Uninhibit
Unisolate

9.5.6.3. Commands StandardAlarmDevice

These statuses are valid for this group, but also for the individual items.
Command: Restore alarms

9.6. Example configuration

Configuring the graphical alarm handler for intrusion items is identical to other items (e.g., AccessPoints).
Implementing and handling with Faces and Graphical Alarm Handler is not been described in detail in this
document as this is to be supposed as common AEOS knowledge. See the appropriate documents for more
information.

At least following steps should be taken:

• Add Statuses (Configuration – Alarm Handler – Status)
First make a selection of the statuses making sense for this user to be shown.
• Status Templates (Configuration – Alarm Handler – Status Template)
• Status Rule Templates (Configuration – Alarm Handler – Status Rule Template)
• Command Templates (Configuration – Alarm Handler – Command Template)
• Add Alarm points / state points (Configuration – Alarm Handler – Alarm points / State points)
• Put the points into the alarm definitions / state point filters

For each item to be presented in the graphical alarm handler it is important to think what information
should be shown: e.g., is it sufficient to show only that there is an alarm, or will you shown each individual
alarm (e.g., Area can have Burglary alarm, Fault alarm, Tamper alarm, Technical alarm, etc. these can be
combined in one icon but it is also possible to show for each alarm a separate icon.)

In this part for some items some screenshots and additional information will be given.

Manual version 21 85
Installation and Configuration | AEOS - Intrusion EN

9.6.1. Intrusion area example

9.6.1.1. Intrusion area status template
At Alarm Handler – Status Template the following images with priority are added to the area status
template:

9.6.1.2. Intrusion area status rule template

At Alarm Handler – Status Rule Template the rules when an image should be presented are composed.

For each defined state (the number is equal to the priority) the rules are added, see below,
1. Areas . *Burglary alarm = Burglary alarm is active

2. Areas . *Tamper alarm = Tamper alarm is active

3. (Areas . *24hour alarm = 24hour alarm is active
OR Areas . *Holdup alarm = Holdup alarm is active
OR Areas . *Panic alarm = Panic alarm is active
OR Areas . *Technical alarm = Technical alarm is active )
4. Areas . *Masked alarm = Masked alarm is active

5. (Areas . *Mode = Armed

AND Areas . *Signal = Detection )
6. (Areas . *Mode = Armed
AND Areas . *Signal = Idle )
7. (Areas . *Mode = Disarmed
AND Areas . *Signal = Tampered )

Manual version 21 86
Installation and Configuration | AEOS - Intrusion EN

8. (Areas . *Mode = Disarmed

AND Areas . *Signal = Detection )

9. Areas . *Signal = Fault

10. Areas . *Mode = Test
11. Areas . *Mode = Disarmed
12. Not used yet

9.6.1.3. Intrusion area command template

At Alarm Handler – Command Template the following commands are allowed to be executed at an area:

In this example all commands are possible, of course can the AEOS administrator make a command
template where, e.g., only the area can be armed and disarmed.

9.6.2. Intrusion detector example

9.6.2.1. Intrusion detector status template
At Alarm Handler – Status Template the following images with priority are added to the detector status
template:

Manual version 21 87
Installation and Configuration | AEOS - Intrusion EN

9.6.2.2. Intrusion detector status rule template

At Alarm Handler – Status Rule Template the rules when an image should be presented are composed.

For each defined state (the number is equal to the priority) the rules are added, see below,
1. Detectors . *Burglary alarm = Burglary alarm is active

2. Detectors . *Masked alarm = Masked alarm is active

3. Detectors . *Tamper alarm = Tamper alarm is active

4. Detectors . *Fault alarm = Fault alarm is active

5. Detectors . *Technical alarm = Technical alarm is active
6. Detectors . *Mode = Inhibit

7. Detectors . *Mode = Isolated

8. Detectors . *Mode = Overridden
9. Detectors . *Mode = Test
10. Detectors . *Signal = Detection
11. Detectors . *Signal = Idle
12. Not used yet
13. Detectors . *Signal = Tampered
14. Not used yet

By making combinations and using logical expressions at the rule template the status can be
made active only when a detector is armed or when the signal is idle, etc.

9.6.2.3. Intrusion detection command template

At Alarm Handler – Command Template the following commands are allowed to be executed at an area:

Manual version 21 88
Installation and Configuration | AEOS - Intrusion EN

9.6.3. Generating Alarm / State points to Maps

After all preparations are made alarm points and state points can be added.
• Alarm points will show the live status and will generate an alarm according to the added alarm
condition, commands can be executed
Go to Configuration - Alarm Handler – Alarm points, select at the component type the corresponding
AlarmItems and add the alarm condition (see also chapter 9.5.4: Available alarms (adding
alarmpoints).
Select the correct status rule template for representing the correct icons at the maps.
• State points will only show the live status, commands can be executed
Go to Configuration - Alarm Handler – State points, select at the component type the corresponding
AlarmItems.
Select the correct status rule template for representing the correct icons at the maps.
Add the defined points to the Alarm definitions / State point filters and place them on the Maps.
Further following the known way to compose and start the face.

9.6.4. Intrusion face example

An example of the Intrusion face could be as below, this face uses the status rule templates as described
above.
On this face there are three different areas and one IntrusionTerminal added.
• Area 1: Detectors 1, 2, 10
• Area 2: Detectors 3, 4
• Area 3: Detectors 3, 5, 6

Above all Areas are disarmed (Green) and all detectors inactive. When, e.g., detector 3 becomes active,
both Area 2 and Area 3 will change their status to Disarmed and Signal Detection (it is made visible that
some detectors for these areas are active).

Manual version 21 89
Installation and Configuration | AEOS - Intrusion EN

Arming, e.g., Area 2 is not possible, it can only be Forced armed:

(use right mouse button on Area icon to get possible commands)

9.6.4.1. Arming
As Area 2 is forced armed, Detector 3 is directly Overridden (because it was active during arming).

Manual version 21 90
Installation and Configuration | AEOS - Intrusion EN

9.6.4.2. Generating alarm

If Detector 4 is activated, the Area goes into the alarm state, and also Detector 4.
Changing detector 4 to inactive will not change this view, because there is still an alarm pending for this
detector and Area.

9.6.4.3. Disarming
After Disarming the area the alarms still are shown, because in an Intrusion system the alarms must be
removed before the status returns to default.

9.6.4.4. Restore alarms at disarmed state

If the detector is default (inactive) the pending alarm(s) for this detector can be restored (Restore Alarms).

After restoring the alarms the view is default. (Area is in disarmed state)

Manual version 21 91
Installation and Configuration | AEOS - Intrusion EN

9.6.4.5. Restore alarms at armed state

If the detector is default (inactive) the pending alarm(s) for this detector can be restored (Restore Alarms).

After restoring the alarms the view is default.

(Area is still in armed state)

9.6.4.6. Alarms at Intrusion Terminal

This Intrusion Terminal (in this example) is added as System device to area 1 and area, these area also
change their state if there is an alarm at the Intrusion terminal.
So the state of areas where this Terminal is added as System device is changed and of course the state of
the Intrusion Terminal itself is changed (here the connection is lost with the terminal, resulting in a Tamper
alarm)

At the Intrusion Terminal, only the Restore Alarms can be executed.

Manual version 21 92
Installation and Configuration | AEOS - Intrusion EN

10. Intrusion LCD keypad reader

10.1. Using Intrusion LCD keypad reader

This chapter briefly describes how to use the Intrusion LCD keypad reader.
Using the LCD keypad authorized users can control their areas (arming, disarming, isolating, etc.). With the
LCD keypad also alarms can be handled and users can be added.

The Intrusion LCD keypad uses ‘soft keys’, depending on the possibilities for the shown menu
one or more keys will light up. The bottom row of the display explains their function.

10.2. General
10.2.1. Intrusion LCD keypad layout
Default no data is displayed on the LCD keypad reader. To get access to the menus a badge (identifier) with
the correct rights have to be offered.
Depending on the rights belonging to this identifier the menu options are now shown.

HOME-2/5 Menu title + line/total HOME-2/5

ARM ARM
DISARM Menu items, including DISARM
ALARM ! additional information ALARM !
LOGS Actual selection is marked LOGS
CONFIGURATION CONFIGURATION
(DISARM)
Soft keys function

Keypad

Manual version 21 93
Installation and Configuration | AEOS - Intrusion EN

10.2.2. Menu information

Indications such as an alarm are shown on the Intrusion LCD keypad reader to users who are allowed to see
these messages. As soon as this user is logged out on the Intrusion LCD keypad reader the messages are not
shown on the display in case the system is armed.
In un-armed situation following indications are visible for each user:
• ! Alarms pending
• Walk In time active
• Walk Out time active

In armed situation there are no indications visible. Only if access is granted to the Intrusion LCD keypad
reader more information for the authorized users is shown.

After login-in to the Intrusion LCD keypad terminal more information is given:
• Home Menu name
HOME-1/5 !
• 1/5 Line number of the actual selected line / total amount of lines ARM
• All areas armed (for this user on this LCD keypad reader) DISARM
• Not all areas armed (for this user on this LCD keypad reader) ALARM !
LOGS
• Area is disarmed
CONFIGURATION
• X Area not reachable (no connection to this area) ▼ ▲
• ? Unknown state of area
• Detector in isolate state
• Detector in inhibit state
• Detector for Walk In and is armed
• Detector is armed but overruled
• Detector in idle state (passive)
• Detector in detection state (active)
• Detector in fault state
• Detector in tampered state
• X Detector not reachable (no connection to this detector)
• ▼ Go one line down
• ▲ Go one line up
• Acknowledge data
• Terminal waiting for data (hourglass)
• Installer mode active

Not all information is always represented. Data shown is related to user rights, being logged in,
etc.

At the other lines the menu information is presented, optional with additional information (e.g., ALARM ….
!).
If the information to be shown does not fit on one line, this line will be horizontally scrolled as soon as it is
selected.

Manual version 21 94
Installation and Configuration | AEOS - Intrusion EN

10.2.3. Key functions

The keys on the keypad will only light up when they can be used. Keys can act as:
• Numeric input
• Function key (soft key), the function of these keys who light up are shown in the bottom line of the
menu. (In the left figure above for clearness all keys are light up, in the right figure the keys that can
be used in the shown menu are activated.)
• Activation of numeric input incase PIN for identification is activated (E key lights up at idle)

There are some special keys:

• E: Confirms an action
• C: Clears the input, cancel action, go back to previous menu
• 0: Switch keypad function from function keys to numeric input (e.g., for selecting a detector
number)

The Intrusion LCD keypad reader is only accessible after offering a valid identifier.

10.2.4. Intrusion LCD soft key usage

The bottom line of the LCD display shows the function of the soft keys. For each individual menu these
functions can differ.

10.2.4.1. Scrolling in data

At menus with a lot of data, scrolling up and down thru the list is possible in steps of 1, 10 and 100. The
keys to be used will only light up if it is useful.

LOGS-122/437 SOFT KEY FUNCTIONS:

04/06/2014 16:29 1: Scroll down 1 item
SET SEQUENCE 4: Scroll down 10 items LOGS-122/437
ABORTED BY 7: Scroll down 100 items 04/06/2014 16:29
DETECTOR 7001: 3: Scroll up 1 item
SET SEQUENCE
ABORTED BY
REMOTEDET1 BECAUSE 5: Show upper part of item DETECTOR 7001:
▼ ▲
6: Scroll up 10 times REMOTEDET1 BECAUSE
8: Show lower part of item
9: Scroll up 100 items

C: Go back one menu

Up from AEOS 3.1.1 the alarms and logs are displayed on the complete screen. (before one line was used
for one message, horizontal scrolling was applied)
If more information is available, key 8 will light up to shown next part of the info.

Manual version 21 95
Installation and Configuration | AEOS - Intrusion EN

10.2.4.2. Switching to numeric input

At some menus it is possible to fill in directly the detector number instead of scrolling through the list. E.g.,
to Isolate or Inhibit a detector.
At menus where this is made possible the 0 key is used to switch to the numeric input mode.
For each key entered the screen will directly be updated.

The menu will normally start with scrolling options on:

INHIBIT-3/7 SOFT KEY FUNCTIONS:

223 ROOM 2 1: Go to next item
234 ROOM 3 2: = Switch inhibit state (ON <-> OFF)
236 ROOM 4 3: Go to previous item
456 ROOM 5
623 LOBBY BACK 0: Switch to numeric input
C: Go back one menu

After entering 0, the soft keys will be removed and the data can be entered. In the example below number
238 is entered.

INHIBIT-3/7
223 ROOM 2
234 ROOM 3
236 ROOM 4
237 ROOM 5
238 LOBBY BACK
238

So following actions are performed:

Step
Select correct function (in this example Inhibit). The list of detectors will be shown
01
Step
With 0 the numeric input is activated (soft keys are not possible to use)
02
Step Enter the detector number (max 4 digits), the number is presented at the middle soft key location
03
Step
End with Enter
04
Step
Now the original menu is shown, with possibility of scrolling up / down
05
Step
Use soft key 2 to toggle this detector
06

Manual version 21 96
Installation and Configuration | AEOS - Intrusion EN

10.3. Menu structure

The items shown to the user are determined by the user profile that is added to this user. In the examples
below we assume the user has maximum rights.

HOME MENU: SUB MENU: FUNCTION:

ARM ARM ALL
ARM area
DISARM DISARM ALL
DISARM area
ALARM Show and acknowledge alarms
LOGS Show logs
CONFIGURATION INHIBIT Detector nr+name
ISOLATE Detector nr+name
INPUT STATE Detector nr+name
WALK THROUGH TEST Area
INSTALLER LOGIN / MODE Activate installer menu / mode
DETECTOR INPUT TEST

10.3.1. Home menu (main menu)

After a valid card is offered, the backlight is activated and the Home menu is presented.

HOME-1/5 ! SOFT KEY FUNCTIONS:

ARM 1: Go to next item
DISARM 3: Go to previous item
ALARM !
LOGS C: Go back one menu (log out)
CONFIGURATION
E: Go to selected menu
▼ ▲

For some sub menus an attention sign can be shown (in this example for ALARM menu).

10.3.2. Arm menu

The Arm menu will show all areas including the actual state for this user.

ARM-1/4 SOFT KEY FUNCTIONS:

ARM ALL 1: Go to next item
AREA 123 3: Go to previous item
LOBBY 2: ARM item selected
BACKDOOR
C: Go back one menu
▼ ▲

Behind each area the current status of this area is presented by icons:
• Area armed: locked
• Area disarmed: unlocked

Manual version 21 97
Installation and Configuration | AEOS - Intrusion EN

If an area cannot be armed the fault issues are presented and can be overruled (if this user has the correct
rights for this):

UNABLE TO ARM-1/3 In this example detector D1 is still open during arming.

21/04/2014 06:32 Detector D1 can be inhibited for this arming period by pressing
1: D1 DETECTION the arm function key (2) and the areas will be armed directly.
The 1/3 implies that more detectors are active during arming
(this can be the same detector, but for another area)
▼ ▲

10.3.3. Disarm menu

The Disarm menu will show all areas including the actual state for this user.

DISARM-1/4 SOFT KEY FUNCTIONS:

DISARM ALL 1: Go to next item
AREA 123 3: Go to previous item
LOBBY 2: DISARM item selected
BACKDOOR
C: Go back one menu
▼ ▲

Behind each area the current status of this area is presented by icons:
• Area armed: locked
• Area disarmed: unlocked

10.3.4. Simplified Arm and Disarm menu

If the user has only permissions to arm and / or disarm a simplified menu is presented after getting access.
The screen will show the actual state (armed or disarmed) and only two choices are possible.

SOFT KEY FUNCTIONS:

1: ARM
3: DISARM

C: Go back one menu

Manual version 21 98
Installation and Configuration | AEOS - Intrusion EN

10.3.5. Alarm menu

The Alarm menu will show all alarms.

ALARM 5/7 ! SOFT KEY FUNCTIONS:

24/05/2014 13:35 1: Go to next item
7001: BACKDOOR HALL 3: Go to previous item
BURGLARY 2: RESTORE the alarm selected

0: Restore all alarms

▼ ▲ C: Go back one menu

Shown is the number selected and amount of alarms (5/7), date and time of the alarm, unique detector
number (7001), the description (Backdoor hall) and the type of alarm (Burglary).
(Before AEOS 3.1.1 alarms where shown on one line using horizontal scrolling.)

Alarms can only be restored if they are no active signals for this alarm point.
All alarms can be restored at once by pressing the 0 button (if user has corresponding rights).

10.3.6. Logs menu

Show logged data. Show all data or only one specific type of log data.
At the logs menu the log information is presented. It is not possible to remove data.

LOGS-122/437 SOFT KEY FUNCTIONS: LOGS 1/1493

04/06/2014 16:29 1: Scroll down 1 item 12/28/11 1:29 PM CONN
SET SEQUENCE 4: Scroll down 10 items 12/28/11 1:29 PM CONN
ABORTED BY 7: Scroll down 100 items 12/28/11 4:15 PM SYSTE
DETECTOR 7001: 3: Scroll up 1 item 12/25/11 3:10 PM SYSTE
REMOTEDET1 BECAUSE
5: Show upper part of item
▼ ▲ ▼ ▲
6: Scroll up 10 times
8: Show lower part of item Before AEOS 3.1.1
9: Scroll up 100 items

C: Go back one menu

Up from AEOS 3.1.1 the alarms and logs are displayed on the complete screen, (before one line was used
for one message, horizontal scrolling was applied, see picture on right)
If more information is available, key 8 will light up to shown next part of the info.

Manual version 21 99
Installation and Configuration | AEOS - Intrusion EN

10.3.7. Configuration menu

The configuration menu can be used to make changes to the configuration. Most changes can be made
here, however it is preferable to make the changes using the web-application.
CONFIGURATION SOFT KEY FUNCTIONS:
INHIBIT
ISOLATE
1: Go to next item
INPUT STATE 3: Go to previous item
WALK THROUGH TEST
DETECTOR TEST C: Go back one menu
DETECTOR INPUT TEST E: Go to selected item
INSTALLER LOGIN
▼ ▲

10.3.7.1. Configuration submenu: Inhibit (bypass)

The available detectors with their unique number and current status are presented. With the soft key
(=Switch) the Inhibit state can be toggled. Behind the detector name a symbol indicates it this detector is in
the inhibit state.

INHIBIT SOFT KEY FUNCTIONS:

2 ROOM 2 1: Go to next item
3 ROOM 3 2: = Switch inhibit state (ON <-> OFF)
4 ROOM 4 3: Go to previous item
5 ROOM 5
6 LOBBY BACK 0: Switch to numeric input
▼ ▲ C: Go back one menu

Inhibit means: Inhibit a detector for this activation period. This means state changes of this detector are
ignored until the next disarm action. So changes on this detector are not passed (except the technical states
changes).

Detectors that are Inhibited are always shown on top of the list. So if the user inhibits a detector,
this detector is automatically placed on top of the list. Un-inhibiting results that this detector
directly moves to its original location in the list.

10.3.7.2. Configuration submenu: Isolate (omit)

The available detectors with their unique number and current status are presented. With the soft key
(=Switch) the Isolate state can be toggled. Behind the detector name a symbol indicates it this detector is in
the isolate state.

ISOLATE SOFT KEY FUNCTIONS:

4 ROOM 4 1: Go to next item
2 ROOM 2 2: = Switch isolate state (ON <-> OFF)
3 ROOM 3 3: Go to previous item
5 ROOM 5
6 LOBBY BACK 0: Switch to numeric input
▼ ▲ C: Go back to Configuration menu

Isolate means: Isolate a detector until it is un-isolated. Isolating means it is ignored, so changes on this
detector are not passed (also technical states changes are ignored).

Manual version 21 100

Installation and Configuration | AEOS - Intrusion EN

Detectors that are Inhibited are always shown on top of the list. So if the user inhibits a detector,
this detector is automatically placed on top of the list. Un-inhibiting results that this detector
directly moves to its original location in the list. Isolate is only permitted for level 3 users.

10.3.7.3. Configuration submenu: Input state (check)

The defined detectors with their unique number and current status are presented. Behind the detector
name a symbol indicates the state of this detector (idle, detection, fault, tampered and connection lost). See
section 10.2.2 for an explanation of the symbols.

INPUT STATE SOFT KEY FUNCTIONS:

2 ROOM 2 1: Go to next item
3 ROOM 3 3: Go to previous item
4 ROOM 4
5 ROOM 5 0: Switch to numeric input
6 LOBBY BACK C: Go back one menu
▼ ▲

Active detectors are always shown at the top of the list.

10.3.7.4. Configuration submenu: Walk through test

With the Walk through test all detectors of one or more areas can be put into Test mode. For this the
correct reporter type (Signaller on an area for status: Test) must be added to this area.

WALK THROUGH TEST SOFT KEY FUNCTIONS:

AREA 123 T 1: Go to next item
LOBBY 2: T = Switch TEST state (ON <-> OFF)
BACKDOOR 3: Go to previous item

C: Go back one menu

▼ T ▲

Manual version 21 101

Installation and Configuration | AEOS - Intrusion EN

Walk through test can only be activated if the corresponding area is disarmed.

When the area is put into Test mode, you can use the Detector test mode as described in section 10.3.7.5.

10.3.7.5. Configuration submenu: Detector test

When an area is put into Test mode as described in section 10.3.7.4, installers can use the Detector test
mode and select this area. A list of detectors in this area will be shown.

When the burglary alarm of the detector is triggered during this test, the detector will be removed from the
list.

If necessary, increase the Menu Detector test Timeout value in the IntrusionTerminal AEbc (see section
7.5.1) to make sure that the screen stays visible until the test is complete. If the menu time-outs, or the
screen is exited in another way, the list of detectors will be full again the next time this menu is opened.

When testing is completed, the installer must go back to the Walk through test menu and switch the Test
mode off again.

DETECTOR TEST SOFT KEY FUNCTIONS:

AREA 1 T 1: Go to next item
AREA 2 T 3: Go to previous item
AREA 3 T
C: Go back one menu

10.3.7.6. Configuration submenu: Detector input test

Installers can select the area that contains the detector they want to test. The menu only shows the
disarmed areas that are configured to the terminal. All detectors in the selected area are shown with their
status at the time the area was selected.

Behind the detector name a symbol indicates the state of this detector (idle, detection, fault, tampered and
connection lost). See section 10.2.2 for an explanation of the symbols.

The status icon on the right is updated when the detector is highlighted and the detector input signal
changes. When the highlighted detector input signal changes, also a beep can be heard.

If necessary, increase the Menu Detector test Timeout value in the IntrusionTerminal AEbc (see section
7.5.1) to make sure that the screen stays visible until the test is complete.

DETECTOR INPUT TEST SOFT KEY FUNCTIONS:

AREA 1 1: Go to next item
AREA 2 3: Go to previous item
AREA 3
0: Switch to numeric input
C: Go back one menu

Manual version 21 102

Installation and Configuration | AEOS - Intrusion EN

10.3.7.7. Configuration sub menu: Installer login

A system user can enable the intrusion terminal to be used by installers. The number of hours (1-23) must
be entered, during this time the installer can get access to the terminal.

INSTALLER LOGIN SOFT KEY FUNCTIONS:

TO START INSTALLER
LOGIN TIMER, ENTER E:
NUMBER OF HOURS C: Go back one menu
AND PRESS E.

10.3.7.8. Configuration sub menu: Installer mode

The installer can enable the Installer mode, preventing (before selected) signallers to become active. If the
installer mode is activated, this will be shown in the top menu line by the Installer mode icon ( ).

INSTALLER MODE SOFT KEY FUNCTIONS:

PRESS E TO START
INSTALLER MODE E: Start installer mode
C: Go back one menu

Manual version 21 103

Installation and Configuration | AEOS - Intrusion EN

11. Configuration examples

This chapter describes some configuration examples for common used solutions.

11.1. Warning device (External)

The external warning device is connected to the outputs of the AP3006, either connected to one of the 8
Open Collector Output or to one of the two relays. See chapter 5.5.3: Switching outputs on AP3006 PCB for
connection details.

V+
Warning
device

OC5

As example:
• The external warning device is controlled by OC5
• Its tamper switch is connected to IN15 (with sabotage enabled)

Connections to warning devices must contain sabotage detection, also tamper is mandatory.

Steps to be taken:

Step Make hardware connections to OC5 and IN15

Power can optional be retrieved from the AP3006 (Power Outputs, see chapter 5.5.4: Power
01 output on AP3006 PCB for supplying sensors)

Step Add Signaller for controlling the warning device (add a new Signalling AEbc or add Signals on
02 existing Signalling AEbc)

Manual version 21 104

Installation and Configuration | AEOS - Intrusion EN

Step Add Detector for checking the tamper switch (add a new Detector AEbc or add detectors on
03 existing Detector AEbc)

Step Make correct bindings as in figure beside (Detectors.3 and Signalling.2) and adjust for both AEbcs
04 their properties.

Step At the Detector Properties add this input as AlarmType=Tamper, and make the other settings
corresponding the tamper switch (Normally open or closed, EOL resistor values, etc.)
05

Connections to warning devices must contain sabotage detection.

Step At the Signalling Properties add the Signal as presented in the table above (Alarm Type and Mode)
and make the other settings corresponding the connected signaller and how this signaller should
06 act (Activation time, Toggle time).

Manual version 21 105

Installation and Configuration | AEOS - Intrusion EN

Step The new added warning device must be added to one or more Areas where to it belongs. Only
messages belonging to the linked Areas will activate the defined signaller.
07 This is done at the web-application.

Step Also the new added detector for the tamper switch of the device must be added to one or more
08 Areas where to it belongs

Step
The warning device is now ready for use.
09

11.2. Burglary detector with tamper switch on one input

Burglary detector with different EOL resistors for Alarm and Tamper.
Detector is connected to Input IN4 of the AP3006
Used EOL resistors: 4K7

11.2.1. Properties for Detectors AEbc

Only one input is used with the AlarmType BURGLARY, by activating the Sabotage checkbox the correct
resistor values (if different from the default values) must be filled in at R1 and R3.

After adding the detector in AEmon it has to be added to one or more areas at the web application.

Manual version 21 106

Installation and Configuration | AEOS - Intrusion EN

11.3. Burglary detector with tamper switch on two inputs

Burglary detector with two outputs, one for Alarm and one for Tamper.
Alarm is connector to Input IN4 of the AP3006, Tamper to IN5
No EOL resistors are used.

11.3.1. Properties for Detectors AEbc

Two different inputs on the AP3006 are used, one for the BURGLARY alarm, the other for the TAMPER
alarm. Both must be added at the Properties.

After adding the detector in AEmon it has to be added to one or more areas at the web application.

Manual version 21 107

Installation and Configuration | AEOS - Intrusion EN

12. Maintenance instructions

12.1. Clock battery
At the Intrusion Base Panel (AEpu) a Lithium (type CR2032) coin battery provides backup for time and date
information. When replacing this battery always switch off the power. Take care not to touch the battery
with bare hands to prevent corrosion on the contacts in the long term.

12.2. System batteries

Depending on the type and manufacturer of the lead batteries, these batteries may need replacing in due
time. Faulty batteries will be reported by the Intrusion Base Panel (the AP3006 checks connected batteries).
For replacing these batteries always switch off the mains power. Batteries may have different connectors.
Always use the proper and suitable connectors recommended by the manufacturer. Always dispose of used
batteries in the proper way according to local regulations.

Manual version 21 108

Installation and Configuration | AEOS - Intrusion EN

13. Testing the system

13.1. AEpack local test (ALT button)
Helpful for testing most of the wired connections is the AEpack Local Test (ALT mode). This test mode is
entered by pushing the ALT button for at least 3 seconds. State 1 is entered and every following push on the
ALT button will progress to the next state:
1. All relays are off, open collector outputs off, all sensor power outputs off, automatic battery test off
2. Sensor power 1 activates (fault is created)
3. Sensor power 2 activates (fault is created)
4. Sensor power 3 activates (fault is created)
5. Sensor power 4 activates (fault is created)
6. Activate relay 1
7. Activate relay 2, deactivate relay 1
8. Activate OC1, deactivate relay 2
9. Activate OC2, deactivate OC1
10. Activate OC3, deactivate OC2
11. Activate OC4, deactivate OC3
12. Activate OC5, deactivate OC4
13. Activate OC6, deactivate OC5
14. Activate OC7, deactivate OC6
15. Activate OC8, deactivate OC7
16. Deactivate all

During every active ALT state any input short shall activate relay 1.
The ALT state is left when pushing the ALT button for at least 3 seconds, after 5 minutes of no ALT button
activating or power off.

Manual version 21 109

Installation and Configuration | AEOS - Intrusion EN

14. Dialler AEbc SIA events (AEOS 3.0.2 and higher)

Events from Intrusion are sent by dialler using SIA events and also dialler itself can sent some events. At
AEOS 3.0.1. dialler messages were differently handled (see appropriate chapter).
Users can define own SIA codes for some detector types, or suppress these codes. Overridden / Inhibiting
an alarm or detector will generate a SIA code.

Due to the limited characters as sent by the dialler (63 characters max) use short names for
AEbcs and descriptions, otherwise data will not be complete received at the ARC (relevant
information can be missed).

14.1. SIA data format

Each message consists of an Event Block (e.g. Nri123/BA254) and optionally one Ascii Block. (e.g., AOffice).
This results in [#001234 | Nri123/BA254 | AOffice].
Total message length is max 63 bytes. The pipe symbol is not visible for the user.

14.1.1. Event block

The Event Block (e.g., Nri123/BA254) has the following format:
NriSSSS/ccaaaa
“N” identifies the Event block
“riSSSS/” optional Area ID modifier, SSSS is the area number 0..9999 (without leading zeroes)
which is retrieved from the area name, see 14.1.3.
“cc” is the SIA Event code see table below
“aaaa” is the address field, its value and meaning depends on the SIA event code

14.1.2. Ascii block

The Ascii Block (part that always starts with the A: e.g. AOffice) is always sent together with an Event Block
and contains additional text information. It’s format is:
A[part-1],[part-2],[part-3]
“A” identifies the Ascii Block
“[part-1]” Event source name if appropriate
“[part-2]” Area name(s)
“[part-3]” see table below (Ascii Block part-3) used for descriptions and additional
information

Ascii block parts are separated by a comma (,).

14.1.3. Area name and number

In AEOS there are no separate area numbers, but when the area name is started with a number this
number will be automatically been used in the dialler protocol.
If an area name starts with a number this will be included in the Area ID modifier and removed from the
name.
The following rules are used:
• Number range: 0..9999
• Number must be separated by a space
• Leading zeroes are removed
• If an event contains multiple area names the area number will be taken from the first name containing
a valid number

Manual version 21 110

Installation and Configuration | AEOS - Intrusion EN

• The SIA standard (SIA-DC03) allows a 4 digit area number but the alarm centre software might limit
the number range to 3 digits, or sometimes only 2 digits.
Examples: Area name Area number Area name in ascii block
Office - Office
123 Office 123 Office
12345 Office - 12345 Office
123Office - 123Office
Office 123 - Office 123
0001 Office 1 Office

14.1.4. Intrusion Panel generated SIA event codes

EVENT BLOCK
EVENT TYPE ASCII BLOCK Part-3
Start End
Burglary NBAdddd NBRdddd “Description”
Burglary override/inhibit NBBdddd NBUdddd “Description”
Masked NBTdddd NBRdddd “Description”
Masked override/inhibit NBBdddd NBUdddd “Description”
24 hour NBAdddd NBRdddd “Description” *
24 hour override/inhibit NBBdddd NBUdddd “Description”
Hold-up NHAdddd NHRdddd “Description”
Hold-up override/inhibit NHBdddd NHUdddd “Description”
Panic NPAdddd NPRdddd “Description” *
Panic override/inhibit NPBdddd NPUdddd “Description”
Fault NUAdddd NURdddd “Fault” “Description”
Technical NUAdddd NURdddd “Technical” “Description” *
Technical override/inhibit NUBdddd NUUdddd “Technical” “Description”
Tamper:
Sabotage, open NTAdddd NTRdddd "Sabotage, open" “Description”
Sabotage, shortcut NTAdddd NTRdddd "Sabotage, shortcut" “Description”
Enclosure opened NTAdddd NTRdddd "Alarm equipment tampered" “Description”
Device connection NTAdddd NTRdddd "Sabotage connection lost"
Tamper override/inhibit NTBdddd NTUdddd “Technical” “Description”
Faults:
AC power NAT0000 NAR0000 "AC power trouble"
Battery missing NYM0000 NYR0000 "Battery missing"
Battery low NYT0000 NYR0000 "Battery low voltage"
Battery failure NYT0000 NYR0000 "Battery failure"
Power supply trouble NYP0000 NYQ0000 "Power supply trouble"
Sensor supply trouble NYP0000 NYQ0000 "Sensor power trouble n"
Dialler not polled NYS0000 NYK0000 "Dialler not polled "
Dialler no Ethernet NYS0000 NYK0000 "Dialler has no Ethernet connection"
Dialler no GSM NYS0000 NYK0000 "Dialler has no GSM registration"
Dialler no comm NYS0000 NYK0000 "No communication with dialler"
Area armed NCL “Carrier name”
Area disarmed NOP “Carrier name”
Area fail to close NCI “Carrier name”
Area exit alarm, NEA “Carrier name”
exit initiated by user
Area exit error, NEE
exit initiated by system
Area start installer mode NLB “Carrier name”

Manual version 21 111

Installation and Configuration | AEOS - Intrusion EN

Area stop installer mode NLX “Carrier name”

Alive message NRP0000
dddd : Detector number 1..9999 without leading zeroes or 0000
“Description”: Optional, only added if a description is added in AEmon.

Overriding an alarm or inhibiting a detector will be notified by using the Bypass and Unbypass SIA
codes.
* For Event Type: PANIC, 24H and TECHNICAL the user can define own defined SIA codes or
suppress the SIA code (see chapter: 7.7.1 Detector properties), above codes are the default used
Nedap codes.

14.1.5. SIA format added descriptions

Detector description will be added to the SIA message in an ascii block, if there is already an alarm reason in
this block the description will be appended:<reason>: <description>.
Example: Technical alarm from detector 24 in area 'Panel' with description 'Overload':
[#002312 | NUA24 | APanel , Technical: Overload]

14.2. Chiron IRIS Secure Apps polling engine generated event

Beside the events generated by the Intrusion Panel, also the dialler itself can generate some events.

EVENT TYPE EVENT BLOCK ASCII BLOCK

Start End
Polling overdue NYC0000 NYK0000 none
Communication trouble NNT0000 NNR0000 none

For more information about IRIS Secure Apps generated event codes see the appropriate IRIS manual.
For some events the 0000 is replaced: NNT9001, NNT9003 (GPRS Fail), NNT9004 (Ethernet fail), NNT9017.

Manual version 21 112

Installation and Configuration | AEOS - Intrusion EN

14.3. Dialler data examples

For each event the area(s) where this event occurs is sent and the source of this event (can be the detector
but also the AEbc name).

As dialler account number we use number 001234 (see chapter 7.9.2: Dialer settings)

14.3.1. Arm area

Arming an area “123 TestArea” by user “UserAll” will produce the following message:

[#001234 | Nri123/CL | ATestArea , UserAll]

#001234 Dialler account number
N Event block
Nri123/ Area ID modifier, area number 123 (retrieved from area name)
CL CL = Area armed
A Ascii block
TestArea TestArea= name of area that is armed (number is removed and used in
Area ID modifier)
UserAll UserAll = name of the user that armed this area.

If multiple areas are armed one line for each area will be sent. E.g. the user UserAll armes areas “1
TestArea”, “2 MainArea” and “3 Office”:
[#001234 | Nri1/CL | ATestArea , UserAll]
[#001234 | Nri2/CL | AMainArea , UserAll]
[#001234 | Nri3/CL | AOffice , UserAll]

14.3.2. Burglary alarm

Burglary alarm is detected at detector number 254 in Area “Office 12”
[#001234 | NBA254 | AOffice 12]
Note that the area in this example does not start with a number

If an alarm is detected at a detector that is used in multiple areas, all areas are added to this message (till
total length is reached): e.g. Burglary alarm is detected at detector number 56 that is used in Areas “01
Office”, “02 MainArea” and “03 Hall”:
[#001234 | Nri1/BA56 | AOffice MainArea Hall ]

In case a description is added to the detector (e.g. Right Wall), this description is added with a comma
separator.
[#001234 | NBA254 | AOffice 12 , Right Wall ]
[#001234 | Nri1/BA56 | AOffice MainArea Hall , Right Wall ]

Manual version 21 113

Installation and Configuration | AEOS - Intrusion EN

14.3.3. Technical alarm

E.g., the battery located at the area “0034 MainArea”
[#001234 | Nri34/YT0000 | AD_PowerSense.1, MainArea , Battery low voltage]
MainArea Name of area that where this technical alarm occurs
D_PowerSense.1 Name of the AEbc component where this alarm is detected (the
AEbc name is PowerSense.1)
Battery low voltage Additional text

Sensor Power Out 1 is sabotaged in Area Office

[#001234 | NYQ0000 | AD_PowerSense.1, Office , Sensor power trouble 1]

Detector 1602 is removed in Area Office

[#001234 | NTA1602 | AOffice , Sabotage connection lost]

Signaller 22 has lost connection with AP3006 (AEbus), belonging to Area Office
[#001234 | NTA0000 | AD_Signal 22, Office , Sabotage, connection lost]

Manual version 21 114

Installation and Configuration | AEOS - Intrusion EN

15. Quick setup Chiron dialler with Nedap Intrusion panel

This part is only for helping to setup the Chiron dialler in combination with the Nedap Intrusion panel.
Detailed information can be found at the Chiron manuals.

15.1. How it works

See for more information: Chiron IRIS System Overview for Customer IT Managers.
The IRIS system is designed to work with existing IP networks with the minimum of setup being required.
An example is shown in the diagram below:

Manual version 21 115

Installation and Configuration | AEOS - Intrusion EN

There are a number of backup options as shown, including backup over GPRS and backup to an alternative
central station. The important points to note are:
• The IRIS diallers by default use Dynamic IP Addressing (DHCP). Fixed addressing can also be configured
if required.
• All IP communications from the dialler is by outgoing calls, including traffic for Polling, Alarm
Transmission and Remote Management and Diagnostics. No port forwarding is required in the
network gateway.
• No port mapping or DNS required.

15.2. Pre-requisites for installing

Prior to installation, you must ensure you have the following:
o The IP address for the Monitoring Centre.
o Confirmation that the Monitoring Centre is set up and ready for the account number or name to be
used for this IRIS dialler.
Also confirm that Monitoring Centre has activated checked “Serial” at “Peripheral Connections” in
“Iris Secure Apps.”. This needs to be enabled to monitor the AEpu - Dialler connection. (Message
NNT9017)

o The type of IP address “either automatic (DHCP) or fixed” for the installation site.
If the site has a fixed IP address, you should get this information from the customer in advance,
together with the Gateway Address and the Subnet Mask for the IRIS dialler.
Make sure that customer outgoing firewall settings are correct: IP and port number (TCP port
53165 polling and alarm signals, from Firmware 1.14 and higher, TCP port 51292 Remote
management and diagnostics)

Manual version 21 116

Installation and Configuration | AEOS - Intrusion EN

o SIM Card Requirements

If the system is using GPRS then SIM cards will be needed to be fitted to each of the IRIS diallers. In
general any SIM card from any provider will work, but the following should be noted:
1. Pay-as-you-go SIM cards should not be used.
2. The SIM card should not have a PIN enabled. If it does, this will need to be cleared in a
phone before the SIM is installed in the IRIS dialler.
3. The SIM should have GPRS (for data/internet) enabled (which is almost always the case).
This is different from WAP, although a SIM card can support both. SIM cards that only
support 3G operation cannot be used.
4. The installer will need to know the Access Point Name (APN) which is a name that the
service provider gives for its gateway from GPRS to the wider IP environment. This name
will be entered into the IRIS dialler. Sometimes the service provider also issues a User Name
and Password and this information will also be required by the installer.
5. The SIM card should be activated before it is sent to site.
6. Also note that the geographical coverage provided by service providers is different and
should be taken into consideration. The IRIS diallers contain a network scanning facility so
the installer can verify that the service provider chosen is acceptable on a particular site.

15.3. Fitting the SIM card

Power must not be applied to the PCB while the SIM card is being fitted or removed or it may be damaged.

15.4. Configuration
See also chapter 7.9.2: Dialer settings
o Unit account number/name, as provided by the Monitoring Centre. Tick “Use 6 digit account
number” to enable auto leading zeroes
o IP address of the Monitoring Centre.
o Ethernet enabled, should be standard active.
o IP address for the dialler (if fixed, not DHCP). If fixed enter “Subnet mask” and “Gateway IP
address”
o APN (and optionally User Name and Password) as provided by the GPRS operator.
o Enable the “Factory reset” to be sure that settings are configured properly.

After configuration, check the following:

• The Ethernet LED is on steady to show Ethernet connected.

Manual version 21 117

Installation and Configuration | AEOS - Intrusion EN

• The SERIAL LED shows Not Configured (1.5s on, 1.5s off) or Normal (1s on, 9s off) to confirm dialler
is communicating with the panel.
• The GPRS LED goes steady to show GSM registered.
• The POLL LED is on steady to show Dialler is polled.

15.5. Debugging tool Chiron

If any fails above, configuration can be checked with Chiron’s IRIS Dialler Configuration software running on
a PC or Laptop connected to the dialler via the USB interface.
Download the latest software from: http://www.chironsc.com/downloads_software.html
Install the software and make connection with USB interface, following screen will appear.

Press “Connect” button:

Manual version 21 118

Installation and Configuration | AEOS - Intrusion EN

Leave “factory default” Password as it is and press “Continue..” button:

= test account

= test account

= test account

Check the input fields for correct settings.

If correct / not correct go to TAB “Remote Touch Screen” to check communication and/or update the
firmware.

Go to Installers Menu

Manual version 21 119

Installation and Configuration | AEOS - Intrusion EN

Press 6 times “1” and confirm with “OK”

Start “Installers Menu” and follow instructions.

For further diagnose when established a connection go to “Diagnostics” TAB.

This will give you information that messages are received by “Iris Secure Apps” at the monitor centre.

Manual version 21 120

Installation and Configuration | AEOS - Intrusion EN

Manual version 21 121

Installation and Configuration | AEOS - Intrusion EN

16. Dialler AEbc SIA events (AEOS 3.0.1 only)

Events from Intrusion are sent by dialler using SIA events and also dialler itself can sent some events.

Due to the limited characters as sent by the dialler (64 characters max) use short names for
AEbcs and descriptions, otherwise data will not be complete received at the ARC (relevant
information can be missed).

16.1. SIA data format

Each message consists of an Event Block (e.g. NBA0254)and optionally one or more Ascii Blocks. E.g.
(AOffice). This results in [#001234 | NBA0254 | AOffice].
Total message length is max 63 bytes.

16.1.1. Event block

The Event Block has the following format:
Nccaaaa “N” identifies the Event block
“cc” is the SIA Event code see table below
“aaaa” is the address field, meaning the source of the event. For a detector this is
the unique detector number 0001..9999. If the source is not a detector the aaaa
will be set to “0000” and an Ascii Block will be appended containing the event source
name.

16.1.2. Ascii block

The Ascii Block is always sent together with an Event Block and contains additional text information. Its
format is: The Event Block has the following format:
Aaa…aa “A” identifies the Ascii Block
“aa..aa” is the text

Manual version 21 122

Installation and Configuration | AEOS - Intrusion EN

16.1.3. Intrusion Panel generated SIA event codes

EVENT BLOCK ASCII ASCII
EVENT TYPE
Start End BLOCK 1 BLOCK 2
Burglary NBAaaaa NBRaaaa Area name(s) “Description”
Masked NBTaaaa NBRaaaa Area name(s) “Description”
24 hour NBAaaaa NBRaaaa Area name(s) “Description”
Hold-up NHAaaaa NHRaaaa Area name(s) “Description”
Panic NPAaaaa NPRaaaa Area name(s) “Description”
Fault NZAaaaa NZRaaaa Area name(s) “Fault” “Description”
Technical NZAaaaa NZRaaaa Area name(s) “Technical” “Description”
Tamper:
Sabotage, open NTAaaaa NTRaaaa Area name(s) "Sabotage, open" “Description”
Sabotage, shortcut NTAaaaa NTRaaaa Area name(s) "Sabotage, shortcut" “Description”
Enclosure opened NTAaaaa NTRaaaa Area name(s) "Alarm equipment tampered"
“Description”
Device connection NTAaaaa NTRaaaa Area name(s) "Sabotage connection lost"
Faults:
AC power NAT0000 NAR0000 Area name(s) "AC power trouble"
Battery missing NYM0000 NYR0000 Area name(s) "Battery missing"
Battery low NYT0000 NYR0000 Area name(s) "Battery low voltage"
Battery failure NYT0000 NYR0000 Area name(s) "Battery failure"
Power supply trouble NYP0000 NYQ0000 Area name(s) "Power supply trouble"
Sensor supply trouble NYP0000 NYQ0000 Area name(s) "Sensor power trouble n2"
Dialler not polled NYS0000 NYK0000 Area name(s) "Dialler not polled "
Dialler no Ethernet NYS0000 NYK0000 Area name(s) "Dialler has no Ethernet connection"
Dialler no GSM NYS0000 NYK0000 Area name(s) "Dialler has no GSM registration"
Dialler no comm NYS0000 NYK0000 Area name(s) "No communication with dialler"
Area armed NCG0000 Area name “Carrier name”
Area disarmed NOG0000 Area name “Carrier name”

Description: Optional, only added if a description is added in AEmon

16.1.4. SIA format added descriptions

Detector description will be added to the SIA message in an ascii block, if there is already an alarm reason in
this block the description will be appended:<reason>: <description>.
Example: Technical alarm from detector 24 in area 'Panel' with description 'Overload':
[#002312 | NZA0024 | APanel | ATechnical: Overload]

16.2. Chiron IRIS Secure Apps polling engine generated event

Beside the events generated by the Intrusion Panel, also the dialler itself can generate some events.

EVENT BLOCK ASCII ASCII

EVENT TYPE
Start End BLOCK 1 BLOCK 2
Polling overdue NYC0000 NYK0000 none None
Communication trouble NNT0000 NNR0000 none None

For more information about IRIS Secure Apps generated event codes see the appropriate IRIS manual.

Manual version 21 123

Installation and Configuration | AEOS - Intrusion EN

16.3. Dialler data examples

For each event the area(s) where this event occurs is sent and the source of this event (can be the detector
but also the AEbc name). This means that in most situations at least two events are made (one for the area
and one for the source).

As dialler account number we use number 001234 (see chapter 7.9.2: Dialer settings)

16.3.1. Arm area

For arming an area following data is sent”:
[#001234 | NCG0000 | ATestArea | AUserAll]
#001234 Dialler account number
N Event block
CG0000 CG = Area armed, no detector number (0000)
A Ascii blocks
TestArea TestArea= name of area that is armed
UserAll UserAll = name of the user that armed this area.

If multiple areas are armed one line for each area will be sent. E.g., the user UserAll arms areas TestArea,
MainArea and Office:
[#001234 | NCG0000 | ATestArea | AUserAll]
[#001234 | NCG0000 | AMainArea | AUserAll]
[#001234 | NCG0000 | AOffice | AUserAll]

16.3.2. Burglary alarm

Burglary alarm is detected at detector number 254 in Area Office
[#001234 | NBA0254 | AOffice]

If an alarm is detected at a detector that is used in multiple areas, all areas are added to this message (till
total length is reached): e.g., Burglary alarm is detected at detector number 56 that is used in Areas Office,
MainArea and Hall:
[#001234 | NBA0056] | AOffice MainArea Hall ]

In case a description is added to the detector (e.g., Right Wall), this description is added as new ascii block.
[#001234 | NBA0254 | AOffice | ARight Wall ]
[#001234 | NBA0056] | AOffice MainArea Hall | ARight Wall ]

Manual version 21 124

Installation and Configuration | AEOS - Intrusion EN

16.3.3. Technical alarm

E.g. the battery located at the area MainArea
[#001234 | NYT0000 | AMainArea | ABattery low voltage]
[#001234 | NYT0000 | AD_PowerSense.1 | ABattery low voltage]
MainArea Name of area that where this technical alarm occurs
D_PowerSense.1 Name of the AEbc component where this alarm is detected (the
AEbc name is PowerSense.1)
Battery low voltage Additional text

Sensor Power Out 1 is sabotaged in Area Office

[#001234 | NYQ0000 | AD_PowerSense.1 Office | ASensor power trouble 1]

Detector 1602 is removed in Area Office

[#001234 | NTA1602 | AOffice | ASabotage connection lost]

Signaller 22 is lost connection with AP3006 (AEbus), belonging to Area Office

[#001234 | NTA00002 | AD_Signal 22, Office | ASabotage, connection lost]

Manual version 21 125

Installation and Configuration | AEOS - Intrusion EN

17. Advanced stettings

In this chapter some advanced settings are given.

These settings may only be performed by experienced AEOS Intrusion users

17.1. Making exact copy of Intrusion AEpu

All specific intrusion information is stored in the /var/data/intrusion directory. If an exact copy must be
made from this intrusion AEpu this file must also be copied to a new AEpu (beside the configuration file). In
this file, e.g., the settings for the detectors as Inhibit, Isolate, etc. are stored.

17.2. Starting a new clean Intrusion AEpu

For getting connection to an AEpu with AEmon, the AEpu must be added in AEmon: File-Connections part of
AEmon (or there must be a lookup server available, e.g., by deploying the lookup AEbc on the AEpu)
Go to File-Connections and Add this AEpu at Always connect to:

Now the user can login to this AEpu with the correct Username and Password.

Manual version 21 126

Installation and Configuration | AEOS - Intrusion EN

17.3. Removing Intrusion data

The AEpu can be completely cleaned up (clean –a, see chapter17.5), but in most situations only parts of the
data has to be deleted, e.g. in situations where after a testing period all unneeded Intrusion data must be
removed, or in case of unexpected problems alarms must be removed. The commands below must be
checked careful before execution!

Login to the AEpu, start the secure shell:

• clean –i Removes all Intrusion alarms
Statuses as inhibit, etc. will be as before. It deletes the alarms.dat in the
subdirectories of /var/data/intrusion
• clean –ia Removes all Intrusion alarms and detector/area modes
For removing all Intrusion data (including statuses as inhibit, etc.). Action
deletes /var/data/intrusion directory
After these commands a stop - start must be given to activate the removals.

17.4. Removing Intrusion data version before 3.1

Before AEOS 3.1 the clean –i and clean –ia where not available. With the commands below data can be
removed directly from the corresponding directory.
The AEpu can be completely cleaned up (clean –a, see chapter 17.5), but in some situations only parts of
the data has to be deleted, e.g. in situations where after a testing period all unneeded Intrusion data must
be removed, or in case of unexpected problems alarms must be removed. The commands below must be
checked careful before execution.
Login to the AEpu, start the secure shell:
• For removing only the Intrusion alarms (statuses as inhibit, etc. will be as before) delete alarms.dat
in the subdirectories of /var/data/intrusion:
execute: rm /var/data/intrusion/ * / * / alarms.dat
• For removing all Intrusion data (including statuses as inhibit, etc.): delete /var/data/intrusion
directory:
execute : rm – rf /var/data/intrusion.
After these commands a stop - start must be given to activate the removals.

17.5. Erasing all data from the Intrusion AEpu

In case all data must be erased from an AEpu: make connection to this AEpu and:
• stop
• clean –a
• start

Manual version 21 127

Installation and Configuration | AEOS - Intrusion EN

17.6. AEmon user rights

Actions in AEmon are linked to user levels. An AEmon user is linked to one of the levels:

LEVEL 3 LEVEL 4
Hardware View Y Y
Configuration View Y
Log View Y
AEpu View Y Y
ProgramLog View Y
EventView Y
Firmware Update Y
AEpu Update Y
AEpu Lookup Y
Show Hardware Y
ReportComponentStatistics Y
ReportDeviceStatistics Y
ReportSystemConsistency Y
ReportHostNameResolving Y
SecureCommunication Y
AEpuPassword Y Y
ReportRemoteBindings Y
ReportAEpuInfo Y
DeviceInfo Y
AEpuTerminal Y
AEpuRestart Y
ClearError Y
AEpuEditTags Y
BatchProcessing Y
PortScan Y
SetDeviceProperty Y

17.7. AEmon users

AEmon users can be of level 3 or level 4 users. Users can:
• Change only their own password for using AEmon
• Add new or delete existing users of the same level (level 3 users may only add new level 3 users)

For using a new login at AEmon use the function File – Reset Password to reset the AEpus password. Now
the new password can be entered.

Manual version 21 128

Installation and Configuration | AEOS - Intrusion EN

17.7.1. Default AEmon users settings

Default AEmon user settings:

LEVEL 3 LEVEL 4
User name level3 level4
Password level3 level4

17.7.2. Change / add AEmon users

For adding a new user select the AEpu and go to AEpu – Secure shell… (or use right mouse button on this
AEpu). Selecting Secure shell … will open a new window where the commands must be entered.
After entering the user data close this new window (cross at upper right corner) or enter <exit>.

With the commands addlevel3user <username> a new user can be added. After adding a new user its
password must be given.

Commands:
• addlevel3user <username>
Changing password for test3
New password:
Retype password:
• addlevel4user <username>
• deluser <username>
• exit

As level 3 users are also allowed to use the front-end, it can be useful to keep both logins and
passwords the same for AEmon and the front-end.
Username: length max 32 characters: 0..9, A..Z, a..z
Password: length min 5, max 8 characters: 0..9, A..Z, a..z

Manual version 21 129

Installation and Configuration | AEOS - Intrusion EN

17.8. AEmon Serial port

The serial port for the dialler is the USB port on the AEpu. Before connecting the USB cable the
ComPortIntegrator AEbc (group Integrators) must be added (and deployed). After connecting the USB cable
this serial port will be visible in AEmon and the binding (link) with the Dialler AEbc can be made.

17.9. EOL Resistors detailed information

For each sensor connected to the AP3006 there are several settings at the Detector AEbc.
• Type of contact (Normally open / normally closed)
• Alarm types used
• EOL resistor value
• Output indicating status input

The Detector AEbc can be applied to the AP3006 hardware (using variable EOL resistor values) and to
(older) hardware for fixed EOL resistors (4K7):
• Masking can only be applied to hardware using multiple input states (as the AP3006)
• Sabotage can be applied to all hardware using supervised inputs

When using older hardware (EOL values are fixed by firmware: normally 4K7), even when no
sabotage is used always set R1 and R3 to 0 (R3 is not applicable: masking is not possible).

Following possibilities:

17.9.1. Alarm, masking and tamper on one input

Normally Closed Normally Open
Contact type
Alarm type Closed Open R R
Idle R3 R1+R2+R3 1 Alarm 1 Alarm
Alarm R1+R3 R2+R3
Masking R2+R3 R1+R3 R R
2 2
Masking + Alarm R1+R2+R3 R3 Masking Sab. Masking
Sab.
Sabotage open >> >> closed closed
Sabotage closed 0 0
Sab open Sab open
R3 R3

Normally closed or normally open applies to all used contacts. It is not permitted to use for, e.g.,
Alarm Normally open and for masking normally closed.

Manual version 21 130

Installation and Configuration | AEOS - Intrusion EN

17.9.2. Alarm and tamper on one input, no masking

Normally Closed Normally Open
Contact type
Alarm type Closed Open R R
1 Alarm 1 Alarm
Idle R3 R1+R3
Alarm R1+R3 R3
Sab. Sab.
Sabotage open >> >> closed closed
Sabotage closed 0 0 Sab open Sab open
R3 R3

17.9.3. Only input, no EOL resistors

Normally Closed Normally Open
Contact type
Alarm type Closed Open
Idle 0 >> Alarm Alarm
Alarm >> 0

17.9.4. EOL preferred resistor values

Preferred Rule Alternatives Rough rule: R3 must be between 1K and 5K,

R1 3K3 2 x R3 4K7 4K7 R2 is 3 to 4 times R3, R1 is 2 to 3 times R3.
R2 8K2 4 x R3 4K7+4K7 6K8 Maximum total R (R1+R2+R3) < 25K
R3 1K5 1K – 5K 2K2 2K2

Manual version 21 131

Installation and Configuration | AEOS - Intrusion EN

18. Safety precautions

18.1. General

The equipment should be installed, operated, serviced, and repaired by qualified personnel only.

The installation and interconnection of this equipment to facility wiring and other equipment must be done
by a competent, qualified craftsperson who is familiar with applicable standards and codes governing the
installation.
Installation methods, practices, or procedures that are unauthorised or done improperly are dangerous and
could result in serious personal injury or damage to property and equipment.

18.2. Warning
Power Supply: Ensure the source voltage matches the voltage of power supply before turning ON the
power.

Power Cord and Plug: To prevent an electric shock or fire, be sure to use the power cord as described
below:
Maximum 4.5 m (14.76 ft.) long. UL/CSA approved, rated minimum 250 V, 10 A, having a 3 x 18 AWG, Type
SJT flexible cord. One end terminates with a parallel blade (120V units) or tandem blade (240V units)
grounding, moulded-on, attachment plug with a 10 A, 110/240 V NEMA 5-15P/NEMA 1-15P configuration.
The socket-outlet shall be installed near the equipment and shall be easy accessible.

Fixed Power Connection: In the case of a fixed connection to the mains a disconnect from mains must be
available near the equipment.

Protective Grounding: The protective grounding terminal must be connected to ground to prevent an
electric shock before turning ON the power.

Fuse: For continued protection against risk of fire replace fuses only with the same type and rating of fuse.
Before replacing the fuses, turn off the power and disconnect the power source. Do not use a different fuse
or short-circuit the fuse holder.

Do Not Operate Near Flammable Materials: Do not operate the equipment in the presence of flammable
liquids or vapours. Operation of any electrical equipment in such environment constitutes a safety hazard.

Opening the covers: Do not open the top cover when active since lethal voltages do exist inside. Always
first disconnect from mains supply and make sure maintenance is safe.

Do Not Modify: To be sure of safety, do not modify or add anything to the equipment other than
mentioned in this installation guide or indicated by NEDAP NV.

Batteries: Under certain conditions storage batteries will expel explosive hydrogen gas. Do not allow
smoking, welding or sparks in the vicinity of any storage battery. Adequate ventilation must be provided
around batteries. Battery racks must also be grounded to minimise static charges.

Manual version 21 132

Installation and Configuration | AEOS - Intrusion EN

19. Hardware specifications

19.1. General

INTRUSION BASE INTRUSION INTRUSION I/O UNIT LCD KEYPAD

PANEL EXTENSION PANEL READER
Supplier N.V. Nederlandsche Apparatenfabriek “Nedap”, NL-7141DC Groenlo, the Netherlands
Nedap article nr 9962972 9962999 9850090 9963006
Dimensions (mm) 470 x 460 x 110 470 x 460 x 110 230 x 190 x 54 170 x 75 x 26
Weight (kg) ± 9500 gr ± 9000 gr ± 2100 gr ± 250 gr
(excl. batteries) (excl. batteries)
Environment -10 – 55 °C -10 – 55 °C -10 – 55 °C -10 – 55 °C
Operating
Environment -30 – 65 °C -30 – 65 °C -30 – 65 °C -30 – 65 °C
Storage
Humidity range 10-93% non- 10-93% non- 10-93% non- 10-93% non-
Operating/storage condensing condensing condensing condensing
Power 230VAC 230VAC AEbus (22-30VDC) AP3006 (12-
28VDC)
Security EN 50131-3 EN 50131-3 EN 50131-3 EN 50131-3
grade 3 grade 3 grade 3 grade 3
Environmental Class II Class II Class II Class II
Certified by Telefication bv NL-6902PK Zevenaar, the Netherlands

19.2. Certification conformities

Below the EN document numbers towards the Intrusion equipment is been certified.

19.2.1. Intrusion Base Panel and Intrusion Extension Panel

The Intrusion Base Panel is intended to be used in security grade 3, environmental class II applications.
There is a variant control panel is called Intrusion Extension Panel. This extension panel is equivalent to the
Intrusion Base Panel only the AEpu controller with IP connection and alarm dialler are not equipped:
• Security alarm testing
EN 50131-3: 2009 tests for Control and Indicating Equipment
Included are the EN 50131-1: 2006 incl. A1:2009 functional requirements (security grade 3),
EN50131-6 and Environmental requirements tests (environmental class II) according EN 50130-5
• Intruder alarm testing
EN 50130-4:2011 EMC requirements tests for Alarm equipment
• Security alarm testing
EN 50136-2-1:1998 General requirements tests for alarm transmission equipment
The tests include the functional requirements, EMC, climatic and mechanical environmental tests.
Included are the EN 50136-1-1:1998 incl. A1:2001 and table 10 & 11 of EN 50131-1:2006
requirements. Included is EN 50136-2-1 Amendment 1 from 2001.
• Security alarm testing
EN 50136-2-3 (1998)
Requirements for equipment used in systems with digital communicators using the public switched
telephone network
• EMC Europa
EMC test according to EN 61000-6-3 (2007)

Manual version 21 133

Installation and Configuration | AEOS - Intrusion EN

Part 6: Generic standards – Section 3: Emission standard for residential, commercial and light-
industrial environments
• European Safety
Safety test according EN 60950-1:2006

19.2.2. Intrusion I/O Unit

The Intrusion I/O unit is intended to work with the Intrusion Base Panel. This I/O unit is identical to the I/O
unit integrated in the Intrusion Base Panel. It therefore has been decided that testing on this unit will be
limited to mechanical and tamper security tests on the enclosure:
• Environmental Alarm
Environmental test according to EN 50130-5 (indoor equipment):2011
• Security alarm testing
EN 50131-3: 2009 tests for Control and Indicating Equipment

19.2.3. Intrusion LCD Keypad reader

The Intrusion LCD Keypad reader is intended to work with the Intrusion Base Panel and extension panel in a
security grade 3, environmental class II application:
• Intruder alarm testing
Coders, keyboards or devices for switching tests according to EN 50131-3
Tests according to EN 50131-3:2009
Included are the EN 50131-1 general requirements, the EN 50130-4:2011 EMC tests and the EN
50130-5:2011 environmental tests. Security Grade 3 Environmental class II.
• European Safety
Safety test according EN 60950-1:2006

19.3. Radio equipment test on Intrusion LCD Keypad reader

Intrusion LCD Keypad reader is also tested on:
• Radio Europa
ETSI EN 300 330-2 V1.3.1 (2006-04)
Radio equipment in the frequency range 9 kHz to 25 MHz and inductive loop systems in the
frequency range 9 kHz to 30 MHz (R&TTE essential requirements)
• EMC Europa
EMC test according to EN 301 489-1 V1.8.1 &EN 301 489-3 V1.4.1
Part 1/3: Specific conditions for Short-Range Devices (SRD) operating on frequencies
between 9 kHz and 40 GHz.

19.4. Maximum amount of equipment connected

To one AEOS Intrusion Base Panel a maximum of 31 AP3006 PCBs can be connected, used in Intrusion
Extension Panel or in Intrusion I/O Unit, resulting in a total max of 32 AP3006 PCBs.
To these 32 AP3006 PCBs can be connected:
• 512 Detector inputs (max. 16 inputs on one AP3006)
• 128 Outputs (max. 2 relais outputs and 8 Open Collector outputs on one AP3006)
• 8 Intrusion LCD keypad readers (on one AP3006 only one LCD keypad reader can be
connected)
• 1 dialler (connected by USB to the AEpu)

On one Intrusion Base Panel or Intrusion Extension Panel powered from this Panel:
• Max 4 Intrusion I/O Unit (due to power requirements and fuse ratings)

Manual version 21 134

Installation and Configuration | AEOS - Intrusion EN

19.5. Power consumption

Table below shows power consumption on 24VDC. As Sensors and Reporters are supplied with 12VDC, the
calculated current must be converted to 24VDC (amount of current at 12V multiplied by 0,625).

STAND BY (IDLE) ACTIVE (ALARM)

VOLTAGE
24VDC 24VDC
AEpu 24VDC 140 mA 190 mA
Dialler Chiron Iris 640 (640NG) 12VDC 100 mA 100 mA
AP3006 PCB 24VDC 80 mA 100 mA
Intrusion LCD Keypad reader 12VDC 40 mA 70 mA
Sensors (Power) 12VDC Calculate Calculate
Indicators (Outputs, reporters) 12VDC Calculate Calculate

External devices may only be connected to the appropriate power outputs (Sensor Power 1 – 4).

19.5.1. Power consumption examples

Below an example how total power consumption can be calculated.
As the sensors and indicators are supplied with 12VDC, and the batteries are 24VDC, the 12V current is
recalculated to 24V (multiply by 0,625 (= 12V/24V /80%).
Battery capacity is calculated as the sum of:
• Stand by current x 30 hours
• Additional Alarm current during 15 minutes ( = 0,25 hour)

Battery capacity decreases after some time. An additional ‘safety factor’ (1 .. 1,25) can be used to
implement this at the calculations below.

19.5.1.1. Intrusion I/O Unit with LCD keypad reader, 10 sensors and 2 indicators connected:

STAND BY (IDLE) 24VDC ACTIVE (ALARM) 24VDC

AP3006 PCB 80 mA 80 mA 100 mA 100 mA
Intrusion LCD Keypad reader 40 mA 40 mA 70 mA 70 mA
10 Sensors (Power) 10 x 20 mA x 0,625 125 mA 10 x 28 mA x 0,625 175 mA
2 Indicators (Outputs, reporters) 0 0 2 x 40 mA x 0,625 50 mA
Total 245 mA 395 mA

Battery capacity: 30 x 0,245 + 0,25 x (0,395 - 0,245) = 7,35 + 0,04 = 7,39 Ah

Manual version 21 135

Installation and Configuration | AEOS - Intrusion EN

19.5.1.2. Intrusion Base Panel with LCD Keypad reader, 6 sensors and 2 indicators:

STAND BY (IDLE) 24VDC ACTIVE (ALARM) 24VDC

AEpu 140 mA 140 mA 190 mA 190 mA
Dialler Chiron Iris 640 (640NG) 100 mA 100 mA 100 mA 100 mA
AP3006 PCB 80 mA 80 mA 100 mA 100 mA
Intrusion LCD Keypad reader 40 mA 40 mA 70 mA 70 mA
6 Sensors (Power) 6 x 20 mA x 0,625 75 mA 6 x 28 mA x 0,625 105 mA
2 Indicators (Outputs, reporters) 0 0 2 x 40 mA x 0,625 50 mA
Total 0 435 mA 615 mA

Battery capacity: 30 x 0,435 + 0,25 x (0,615 - 0,435) = 13,05 + 0,045 = 13,1 Ah

19.5.1.3. Intrusion Extension Panel with LCD keypad reader, 14 sensors and 4 indicators:

STAND BY (IDLE) 24VDC ACTIVE (ALARM) 24VDC

AP3006 PCB 80 mA 80 mA 100 mA 100 mA
Intrusion LCD Keypad reader 40 mA 40 mA 70 mA 70 mA
14 Sensors (Power) 14 x 20 mA x 0,625 175 mA 14 x 28 mA x 0,625 245 mA
4 Indicators (Outputs, reporters) 0 0 4 x 40 mA x 0,625 100 mA
Total 0 295 mA 515 mA

Battery capacity: 30 x 0,295 + 0,25 x (0,515 - 0,295) = 8,85 + 0,055 = 8,9 Ah

If Intrusion I/O units are connected to the panels the total current of the I/O Extension Units must be added
to the power consumption of the Panels where these units are connected.

19.5.1.4. Intrusion Extension Panel and I/O unit with 2 LCD keypad readers, 24 sensors and 6
indicators:

STAND BY (IDLE) 24VDC ACTIVE (ALARM) 24VDC

AP3006 PCB 80 mA 80 mA 100 mA 100 mA
Intrusion LCD Keypad reader 40 mA 40 mA 70 mA 70 mA
16 Sensors (Power) 16 x 20 mA x 0,625 200 mA 16 x 28 mA x 0,625 280 mA
4 Indicators (Outputs, reporters) 0 0 4 x 40 mA x 0,625 100 mA
1 Intrusion I/O Unit as below 1 x 225 220mA 1 x 375 mA 360 mA
Total 0 540 mA 910 mA

Intrusion I/O Unit with LCD keypad reader, 8 sensors and 2 indicators connected:

STAND BY (IDLE) 24VDC ACTIVE (ALARM) 24VDC

AP3006 PCB 80 mA 80 mA 100 mA 100 mA
Intrusion LCD Keypad reader 40 mA 40 mA 70 mA 70 mA
8 Sensors (Power) 8 x 20 mA x 0,625 100 mA 8 x 28 mA x 0,625 140 mA
2 Indicators (Outputs, reporters) 0 0 2 x 40 mA x 0,625 50 mA
Total 220 mA 360 mA

Battery capacity: 30 x 0,540 + 0,25 x (0,910 - 0,540) = 16,20 + 0,37 = 16,6 Ah

Manual version 21 136

Installation and Configuration | AEOS - Intrusion EN

Currents for indicators and sensors must be filled in corresponding to the applied equipment.
19.5.2. Power consumption conform grade 3
To comply to the 30 hours (prime power source fault is notified to alarm receiving centre) battery
operation according the EN 50131-3 grade 3, take care to the total current that can be supplied by the
panels related to the different batteries used. Absolute maximum with 17Ah battery = 567 mA (24V) and
12Ah battery = 400 mA (24V).
See chapter 19.5: Power consumption for different panel configurations:
• Intrusion Base Panel with 17Ah batteries (including Intrusion LCD Keypad reader):
Total current left for external devices is 200 mA (24V).
• Intrusion Extension Panel with 17Ah batteries (without Intrusion LCD Keypad reader)
Total current left for external devices is 480 mA. (24V)
• Intrusion Extension Panel with 12Ah batteries (without Intrusion LCD Keypad reader)
Total current left for external devices is 310 mA. (24V)

This current left for external devices may be divided over the panel power outputs AEbus(24V)
and outputs (Sensor Power 1..4)(12V), for the 12 Volt outputs a conversion factor 0.625 is used.

19.6. Power supply

Power supply is integrated in Intrusion Base Panel and Intrusion Extension Panel. More detailed info about
the integrated power supply can be found at chapter 21: Appendix A: Detailed information included power
supply.
The Power supply regulates the charging of the batteries. The AP3006 checks the batteries on capacity,
loading and presence.

Type power supply Type A (according EN 50131-6)

Input voltage range 230VAC, +10%, -15%
Frequency range 47 ~ 63 Hz
AC Current (typical) 1.2A @ 230VAC
Environment, operating -20 – 70 °C
Humidity, operating 20 - 90% non-condensing
Protection Battery Cut Off 20 ±1V
Alarm function Battery low Battery low voltage: < 22V
Output voltage on PSC-100B: 27.6V, 2.4A (electronics) 27.6V, 1.25A (battery)
Ripple & noise 100 mVpp
Voltage tolerance 1%
Safety standards UL:60950-1, TUV EN60950-1 approved
Protection Overload 105 ~150% related output power, Protection type: Hiccup mode,
recovers automatically after fault condition is removed
Protection Over voltage 28.98 ~ 37.26V Protection type: shut down o/p voltage, re-power on to
recover
Power Outputs on AP3006:
Sensor Power (4 x) 12VDC ± 10% max 200mA (each output) max ripple: 100 mVpp
LCD Keypad reader (2 x) 12VDC ± 10% max 200mA (each output) max ripple: 100 mVpp
AEbus 22 - 27,6VDC max 800mA max ripple: 1200 mVpp
Power Input on AP3006 22 – 30 VDC
19.7. Power supplied and checking by AP3006
On the AP3006 following power is supplied and monitored:

Manual version 21 137

Installation and Configuration | AEOS - Intrusion EN

NOMINAL FAULT
Sensor power 12VDC ± 10% < 11VDC > 14,7 VDC
AEbus power (Vraw) 27,6VDC ± 10% < 22VDC > 31 VDC
Mains supply 230VAC Failure
Battery voltage 24VDC < 20VDC
Battery capacity 27VDC < 23VDC
Battery present Yes No
Battery charging Yes No

If the power gets below the stated value (Fault) a fault signal is generated. This value can be overruled with
the settings at the applied AEbc (see chapter 7.10.1: PowerSense Properties). Sensor power and AEbus
power are also checked at over-voltage.

The threshold value for the battery capacity measurement is depending on the capacity of the
used batteries (during 10 seconds this threshold is measured). Below the threshold values for the
different battery types: 12 Ah: 22VDC, 17 Ah: 23VDC

19.8. Fuses
Fuses can be found in in the Intrusion base panel and Intrusion Extension panel

VALUE TYPE
Power supply 1,6A SB Littlefuse type: LF2181.6
Between batteries 3,15A SB Littlefuse type: LF2183.15
AEbus Power 1,0A F Schurter D1 fast (7010.3410)

The Intrusion I/O unit and Intrusion LCD keypad reader do not contain replaceable fuses. The four Sensor
Power outputs and the Reader output are automatic recovering after the failure is removed.

For continued protection against risk of fire replace fuses only with the same type and rating of
fuse. Before replacing the power supply fuse, turn off the power and disconnect the power
source. Do not use a different fuse or short-circuit the fuse holder.

Manual version 21 138

Installation and Configuration | AEOS - Intrusion EN

19.9. Batteries
Batteries are not included, recommended batteries are:

TYPE CAPACITY MAX TIME TO RECHARGE TO 80%

Yuasa NP12-12 (2 pieces) 12 Ah 12 hours
Yuasa NP17-12 (2 pieces) 17 Ah 17 hours

More info about the recommended Yuasa batteries can be found on: http://www.yuasa-battery.de

If other batteries are used: the maximum battery load current is 1.25 A. From this value the max
time to recharge to 80% can be calculated

19.10. Dialler
As dialler now only the Chiron dialler can be used.
This dialler is certified and compliant with EN50131, EN50136 Security Grade 4, ATS 6:

DIALLER
Chiron IRIS Touch 640 (www.chironsc.com)
Chiron IRIS Touch 640NG (www.chironsc.com)
Chiron IRIS Touch 620 (www.chironsc.com)

IRIS Touch 640 and its successor the IRIS Touch 640NG are equipped with GPRS backup module, 620
communicates only over IP.
Firmware version of dialler: at least version 1.14.1 (can be checked at AEmon – Dialler AEbc Properties)

All relevant dialler settings are set by the Dialler AEbc. More detailed information about the dialler can be
found in the dialler manuals at above internet sites and at the appropriate chapters in this manual.

Manual version 21 139

Installation and Configuration | AEOS - Intrusion EN

19.11. AP3006 PCB characteristics

At the Intrusion Base Panel, the Intrusion Extension Panel and the Intrusion I/O unit the AP3006 PCB is used
for connecting the inputs and outputs and communication to the AEpu.

AP3006 CHARACTERISTICS
Power input 22-30 VDC
Power 4 x Sensor Power: 12VDC ± 10% max 200mA (each output), max ripple: 100 mVpp
outputs 2 x Reader: 12VDC ± 10% max 200mA (each output), max ripple: 100 mVpp
AEbus: 22 - 27,6VDC max 800mA max ripple: 1200 mVpp
Outputs 2 x Relais with dry contact (normally open, common, normally closed).
Contact ratings: (Suitable for switching inductive loads, clean relay contacts)
Switching voltage: 24VAC, 30VDC (max 60 W)
Continuous current and switching current: 2A (AC and DC)
Contact lifetime: min 100.000 times at given ratings
8 x Open Collector outputs (Open drain Mosfets with internal power protection), max 1000
mA
Status Sensor input (red), Sensor power (green), Outputs (green), Battery status
indications
Communicati 2 x RS485 (+12V,A, B, GND) for Nedap reader connections (to maintain certification only
ons channel 1 can be used)
AEbus for communication between AEpu and AP3006 PCBs
Battery Controlled and checked by AP3006, indicators for Battery Low and Battery Powered
backup Checks involves voltage, capacity, charging.
Loading batteries by dedicated power supply (build in the Intrusion Panels)

AEbus voltage is derived directly from the Power Supply (normally 27,6 VDC). At battery
operation this voltage will be lower (24 VDC).

19.12. Cabling
FROM TO FUNCTION TYPE MAX LENGTH
Mains Power connector Power supply 3 x 0,75mm² 100 m
Base Panel Extension Panel AEbus communication: 300m / 1000m
(AEbus between - with power 3 x 2 x 0,5mm² total AEbus
AP3006 PCBs) shielded / length
- without power 2 x 2 x 0,5mm² (High /Low
shielded bitrate)
AP3006 LCD Keypad reader RS485 communication 2 x 2 x 0,25mm² 1000 m
shielded
Base Panel Dialler USB communication USB master –slave 10 cm
AP3006 Sensors / detectors Power and sensor X x 0,25mm² 100 m
AP3006 Outputs Reporters X x 0,25mm² 100 m

For large cable distances the internal resistance of the applied cable is important. In case power
is supplied over longer distances, the total voltage drop over the cable by the used cable
diameters must be checked. This can result that larger cable diameters must be chosen or an
additional power unit must be added.
Cabling to Sensors/Detectors and Reporters is depending on the used hardware. Check the
supplier of these items for more detailed cabling information.

Manual version 21 140

Installation and Configuration | AEOS - Intrusion EN

20. Software specifications

20.1. Amount of attempts to get access to Intrusion LCD keypad reader
For getting access to the Intrusion LCD keypad reader the presented badge must off course be valid for this
reader.
If 9 times behind each other an invalid identifier is been offered, the Intrusion LCD keypad reader is been
blocked for 90 seconds (for both valid and invalid identifiers) and will be blocked again for 90 seconds if
another invalid identifier is been offered.

20.2. Use of PIN codes

PIN codes are not applied for the AEOS Intrusion system, only the before-mentioned identifiers can be used
to get access.

20.3. Cold boot situation

A cold boot situation is defined as when the Intrusion Base Panel power is interrupted including battery
backup failure. (AEpu and AP3006 of the Intrusion Base Panel had some time no power):
• Failure is indicated by the dialler (no communication)

After power is returned:

• Application restarted
• Return is indicated by the dialler (no communication)
• State of the Intrusion system is as on the moment the power failed, all statuses are recovered as before.
(No relevant data is been stored in volatile memory.)

20.4. Methods of setting and un-setting

Setting (arming) and un-setting (disarming) can only be performed by the menu on one of the Intrusion LCD
keypad readers. Access rights for these menus are programmed using the configuration software (PC with
browser that connects to the Intrusion base panel). Details and programming instructions can be found at
the AEOS Intrusion SA User Manual.
Setting and unsetting is only allowed for individuals having
1. Correct access rights to the corresponding Intrusion LCD keypad reader
2. AND access rights for the corresponding areas
3. AND access rights to perform Arming and/or disarming for these areas

If during the setting/ unsetting irregularities are detected these are clearly reported to the user,
preventing the user to make any failures or causing unintentionally alarms.

20.5. Conditions for set state (entry and exit procedure)

Setting (arming) and un-setting (disarming) can only be performed through the menu on one of the
Intrusion LCD keypad readers.
An area can only be armed if:
• All related detectors are not active
• No alarms for this area are pending (not restored)
• No fault situations for this area
Error conditions can be overruled by the correct user.

Manual version 21 141

Installation and Configuration | AEOS - Intrusion EN

20.6. Overruling detectors and un-inhibiting / un-isolating

When an area is armed and some detectors are still active, they can be overruled, so these detectors are
temporarily not active during this current arm period.
If during this arm period these detectors will be inhibited or isolated AND after that un-inhibited or un-
isolated, the state for these detectors will go back to the armed state (and not overruled).
If this detector is still active, it will then directly generate an alarm.

20.7. Automatic log off

Indications on the Intrusion LCD keypad readers are automatically made inaccessible for level 1 users when
level 2, 3 or 4 user is no longer accessing the information by:
• Automatic log off after the specified time (Menu Timeout at IntrusionTerminal AEbc), default 30
seconds
• Manually log off by entering the ‘C’ button in the main menu.

20.8. Level 3 access without level 2 authorization

There is no level 3 access without level 2 authorization possible. After offering a badge with access for
level3 always a level 2 badge must be offered to allow access for the level 3 user.
This is indicated on the Intrusion LCD keypad reader on the screen as: ‘Present system user badge’

20.9. Log files

The event log in AEOS Intrusion is split up into:
• Mandatory events: (default 1000 mandatory events can be stored)
• Other events: (default 4000 other events can be stored)

Total 5000 events can be recorded, using first in first out mechanism
The number of events recorded from any single source shall is limited to 5 during any set or unset period.

20.10. Audible alarms generated by terminal

At each Intrusion LCD Keypad reader a build in beeper is used to give audible indications about the status
the system is in. Each indication is build up from: Frequency, beep length, beep pattern, On length (length
one ON period).

Next statuses are available:

STATUS FREQUENCY BEEP LENGTH BEEP PATTERN 1 ON LENGTH

Arming 3873 Hz 2 sec On – Off – On – Off (0x55) 82 msec
Dis-arming 800 Hz 1 sec Off – Off – On – On (0x66) 82 msec
Route set stopped 2080 Hz 2 sec On – Off – On – Off (0x55) 82 msec
Route active 800 Hz During route active On – Off – On – Off (0x55) 524 msec

Manual version 21 142

Installation and Configuration | AEOS - Intrusion EN

21. Appendix A: Detailed information included power

supply
Power supply (type PSC-100B) is included in the Intrusion base panel and Intrusion Extension
panel. Detailed specification can be found below.

21.1. Power supply specifications

Manual version 21 143

Installation and Configuration | AEOS - Intrusion EN

Manual version 21 144

Installation and Configuration | AEOS - Intrusion EN

21.2. Power supply mechanical specifications and block diagram

Manual version 21 145

Installation and Configuration | AEOS - Intrusion EN

Copyright
Copyright © Nedap N.V. All rights reserved. The information in this document is subject to
change without notice, it is not to be reproduced in any way, in whole or in part, without the
written consent of Nedap N.V. Nedap AEOS is a registered trademark of Nedap N.V. All
trademarks referenced belong to their respective owners.

Disclaimer
Nedap N.V. has made every effort to ensure the accuracy of the information contained in this
document. However, Nedap N.V. makes no representations or warranties whatsoever whether
express or implied as to the accuracy, correctness, completeness or fit-for-purpose or suitability
for the purpose of this product. You use the products at your own risk. Nedap N.V. excludes any
liability to the maximum extent permitted by applicable law for the damages caused by errors or
failures made during the installation or improper use of this product or by not applying the
instructions stated in this document.
Nedap N.V. reserves the right to make improvements or amendments to this document and/or
the products described therein at any time without any notification. The latest version of this
document can be found on portal.nedapsecurity.com. Please download the latest version of this
document and keep a copy for your own records.
This document can be published in various languages but only the English version will prevail.
Nedap N.V. assumes no responsibility for any errors due to translations into other languages.

Nedap Security Management

P.O. Box 103
NL - 7140 AC Groenlo
+31 (0)544 471 111
[email protected]
www.nedapsecurity.com

Manual version 21 146