Jung EAM 4000 Product Documentation
  1. Manuals
  2. Brands
  3. Jung Manuals
  4. Security System
  5. EAM 4000
  6. Product documentation
Jung EAM 4000 Product Documentation

Jung EAM 4000 Product Documentation

Knx/eib, central alarm unit, actuator/sensor
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Central alarm unit
Product name:
Central alarm unit (CAU)
Design:
aP (surface-mounted)
Ref.-no.:
EAM 4000
Security/Central alarm unit/Central alarm unit
ETS search path:
Issue:
07.07.2003
Functional description:
This KNX Central alarm unit (CAU) is the heart of an efficient alarm system. Owing to the utilization of the KNX,
expensive additional cabling work can be reduced to a minimum. Both the KNX system and individual detectors
installed can, for example, also be used by other trades.
By many different parameterization options within an ETS plug-in of its own, the KNX Central alarm unit facili-
tates its use in various kinds of buildings – from the detached family house with outer shell and interior room
safeguarding up to the office building where up to four safeguarding areas (SA 1...4) can be protected individu-
ally or as groups linked up with one another. The ETS plug-in will be automatically started when the parameter
setting option is called.
The KNX Central alarm unit stands out for the following performance features:
• Up to 160 detectors can be managed and integrated into up to four separate safeguarding areas.
• All sensors (detectors) are connected to the Central alarm unit via the KNX. This facilitates individual identifica-
tion and monitoring of all detectors.
• All events (arming, alarm, fault) will be logged together with their date and time and saved.
• The alarm indicators (siren, flashlight, alarm transmission device (ATD)) can be directly connected to the Cen-
tral alarm unit or triggered via the KNX.
• A rechargeable emergency battery facilitates uninterrupted operation of the alarm indicators even in the event
of mains failure. An intelligent electronic charging circuit ensures that emergency power supply of at least
12 hours will always be guaranteed.
• Display and operation are exclusively decentralized and can be handled via external KNX devices (info display
unit, pushbutton sensors, etc.). Sometimes, several types of arming devices (AD) can be used within an arming
area (AA 1...AA 4) for arming and disarming.
• A local detector input (wired detector) can be used for safeguarding the place of installation of the Central
alarm unit, e. g. in a distribution cabinet. Thus, the Central alarm unit will be in a position to protect 'itself'.
• An additional relay contact in the form of a potential-free output can, for example, be used for additional alarm
indicator applications.
For fire and attack detectors, separate safeguarding areas are reserved. If a detector from one of such safe-
guarding areas responds an alarm will immediately be raised, regardless of the state of the system.
As a special variant, the Central alarm unit can also be solely used for attack and fire detector applications.
A detector test mode is available, by means of which all detectors of the alarm system can be checked without
raising any alarm.
Particularly large buildings (arcades, extensive factory units) can possibly not be safeguarded by one Central
alarm unit alone but require several Central alarm units, each of them monitoring partial complexes. When sev-
eral KNX Central alarm units are used, such Central alarm units can monitor one another by sending and receiv-
ing telegrams for mutual monitoring. After three missing telegrams from the 'partner Central alarm unit', a sabo-
tage signal will be released (armed: alarm, disarmed: fault).
KNX / EIB
Product Documentation
Page: 1 of 81
Actuator/Sensor
Hardware Description

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EAM 4000 and is the answer not in the manual?

Questions and answers

Related Manuals for Jung EAM 4000

Summary of Contents for Jung EAM 4000

  • Page 1 Actuator/Sensor Product name: Central alarm unit (CAU) Design: aP (surface-mounted) Ref.-no.: EAM 4000 Security/Central alarm unit/Central alarm unit ETS search path: Issue: 07.07.2003 Functional description: This KNX Central alarm unit (CAU) is the heart of an efficient alarm system. Owing to the utilization of the KNX, expensive additional cabling work can be reduced to a minimum.

  • Page 2: Product Documentation

    KNX / EIB Page: 2 of 81 Product Documentation Illustration: Betrieb Melder Sabo R-Sabo 12V / 0,1A ÜG (-) 12V / 0,1A ÜG-R 12V (+) ÜG-S/U Blitz (-) ÜG-E 12V (+) ÜG-F ASIR (-) ÜG-Ü 12V (+) ÜG-S ISIR (-) Prog Dimensions: Width: 210 mm...

  • Page 3: Specifications

    KNX / EIB Page: 3 of 81 Product Documentation Specifications Protective system: IP 20 Mark of conformity: Ambient temperature: -5 °C to +45 °C Storage temperature: -25 °C to +75 °C (storage above +45 °C will shorten the life) Fitting position: Minimum distances: none Type of fixing:...
  • Page 4 KNX / EIB Page: 4 of 81 Product Documentation Bus and mains voltages: The response to bus voltage failure can be set with jumper J1 while the system is in its armed state (refer to "Response to Bus Failure"). In any case, an alarm transmission device fault signal will be immediately re- leased.
  • Page 5 KNX / EIB Page: 5 of 81 Product Documentation Sabotage input: Number: approx. +4.7 VDC (in open state) Signal voltage: (for a sabotage resistance of 0 Ohms) approx. +2.8 VDC (for a sabotage resistance of 12 kOhms) approx. +3.8 VDC (for a sabotage resistance of 47 kOhms) Signal current: approx.
  • Page 6 KNX / EIB Page: 6 of 81 Product Documentation Potential-free relay output: Number: 1 x normally open (NO)/1 x normally closed (NC) with the same base contact Switch type: potential-free relay contacts Switching voltage: 12 VAC/DC max. Switching current: 5 A max. Minimum load: 30 mA Connection:...
  • Page 7 KNX / EIB Page: 7 of 81 Product Documentation Wiring diagram: Terminal assignment: Wired detector Melder The alarm detectors can be connected to the KNX, if necessary, via suitable binary inputs. An additional detector - or even several normally closed contacts connected in se- ries (closed current loop) - can be directly connected to the Central alarm unit.
  • Page 8 KNX / EIB Page: 8 of 81 Product Documentation Wiring diagram: Terminal assignment: Sabotage security ("Central alarm unit wired detector sabotage") Between the "Sabo" (sabotage) and "GND" terminals of terminal strip X2, you can con- nect the sabotage contacts of the wired alarm indicators (siren and flashlight) or of the Sabo wired arming devices (e.
  • Page 9 KNX / EIB Page: 9 of 81 Product Documentation Remarks on the hardware • The maximum current of all devices connected to the Central alarm unit must not exceed 1.8 A. • The Central alarm unit has an overload or short-circuit detection circuit for the alarm indicator outputs. In case of overload of an output, the electronic overload detection circuit will switch off all alarm indicator outputs (termi- nals: Blitz (flashlight), Asir (outdoor siren), Isir (indoor siren) for about 1 second.

  • Page 10: Software Description

    Product Documentation Software Description ETS search path: ETS symbol: Alarm equipment/Central alarm unit/Central alarm unit Berker Security/Central alarm unit/Central alarm unit Gira Security/Central alarm unit/Central alarm unit Jung PEI type Programmable I/O Applications: No. Brief description: Name: Version: Central alarm unit...
  • Page 11 KNX / EIB Page: 11 of 81 Product Documentation Application: 1. Central alarm unit C00402 Runable from screen form version: 7.1 Number of addresses (max.): Dynamic table management Number of assignments (max.): Maximum table length Communication objects: Detector objects: Object Function Name Type...
  • Page 12 KNX / EIB Page: 12 of 81 Product Documentation Armed/disarmed state signalization objects (continued): Object Function Name Type Flag Arming area 1 Static disarmed state signal 1-bit K, Ü, (L) Arming area 2 Static disarmed state signal 1-bit K, Ü, (L) Arming area 3 Static disarmed state signal 1-bit...
  • Page 13 KNX / EIB Page: 13 of 81 Product Documentation System monitoring objects: Object Function Name Type Flag System monitoring ATD checkback input fault 1-bit K, S, (L) All safeguarding areas Detector test 1-bit K, S, (L) Heartbeat check Heartbeat check input 1-bit K, S, (L) Heartbeat check...
  • Page 14 KNX / EIB Page: 14 of 81 Product Documentation Object description 0 - 159 Inputs 1 -160 1-bit object for coupling the KNX detectors to the Central alarm unit. (The polarity of the objects can be parameterized.) Wired sabotage input: 1-bit object for transmitting the state of the wired sabotage input.
  • Page 15 KNX / EIB Page: 15 of 81 Product Documentation 207 - 218 Line 1 – line 3: 14-byte object for the transmission of the display texts to the up to four info display units. 219 - 222 Selection: 1-bit object for the line control of the up to four info display units. This will enable you to select the active lines in the info display unit or to call the display messages, respectively.
  • Page 16 KNX / EIB Page: 16 of 81 Product Documentation Function scope • You can establish up to four different safeguarding areas (circuits, signal groups) dependent on one another (nested) or independent (separate) of one another (configuration). • The "fire" and "attack" safeguarding always exist. •...
  • Page 17 KNX / EIB Page: 17 of 81 Product Documentation Function scope (continued) • A fire fault signal (collective signal from all fire detectors) can be transmitted through an KNX object. • An armed/disarmed state signal can be transmitted through the "armed/disarmed state signal to the ATD" KNX object and a fault signal through the "fault signal to the ATD"...

  • Page 18: Table Of Contents

    KNX / EIB Page: 18 of 81 Product Documentation Functional Description Contents Page Configuring the Safeguarding/Arming Areas Safeguarding areas (SA) Arming areas (AA) Configurations Multi-area configurations Editable Texts Detector and Sabotage Inputs Detector types Connecting detectors Arming Arming devices 4.1.1 Configuring arming devices 4.1.2 Connecting options of arming devices...

  • Page 19: Functional Description

    KNX / EIB Page: 19 of 81 Product Documentation Functional Description 1. Configuring the Safeguarding/Arming Areas 1.1 Safeguarding areas (SA) A safeguarding area is an area which safeguards certain building parts and individual rooms or façade areas, i. e. keeps them under surveillance to detect intrusion or vandalism. Within such safeguarding areas, detectors which can be connected together into groups, form the components which facilitate surveillance.
  • Page 20 KNX / EIB Page: 20 of 81 Product Documentation • Configuration 2.1 (default configuration): 1 x outer shell (SA 1), 1 x indoors (SA 2), nested, e. g. detached family house, flat, workshop, etc. AA 1: SA 1 (outer shell) can be separately armed by AA 1, i. e. by an arming de- vice located within the building.
  • Page 21 KNX / EIB Page: 21 of 81 Product Documentation • Configuration 3.1: 1 x separate safeguarding area (SA 1). 1 x outer shell (SA 3), 1 x indoors (SA 4), nested, e. g. dwelling house with separate summer house, etc. AA 1: SA 1 (separate safeguarding area) can be armed by AA 1.
  • Page 22 KNX / EIB Page: 22 of 81 Product Documentation • Configuration 4.1: 1 x separate safeguarding area (SA 1), e. g. arcade, holiday house, hotel, pension, trade fair/exhibition hall, etc. AA 1: SA 1 (separate safeguarding area) can be armed by AA 1. In the event of AA 1 an alarm, the alarm indicators assigned to AA 1 will be activated.
  • Page 23 KNX / EIB Page: 23 of 81 Product Documentation • Configuration 5.1: 1 x safeguarding area (SA 1), separate. 1 x safeguarding area (SA 4), cascaded, i. e. the arming areas must be armed one by one, e. g. office complexes, industrial buildings, sports halls, etc. AA 1: SA 1 (separate safeguarding area) can be armed by AA 1.
  • Page 24 KNX / EIB Page: 24 of 81 Product Documentation • Configuration 6: 2 x safeguarding area (SA 1 and SA 2), separate. 1 x safeguarding area (SA 4), cascaded, i. e. the arming areas must be armed one by one, 1 x safeguarding area (SA 3), separate and not integrated into the cascading, e.

  • Page 25: Multi-Area Configurations

    KNX / EIB Page: 25 of 81 Product Documentation • Configuration 7.2: 1 x safeguarding area (SA 1), separate. 1 x safeguarding area (SA 4), cascaded, i. e. the arming areas must be armed one by one. 2 x safeguarding area (SA 2 and SA 3), separate and not integrated into the cascading, e.

  • Page 26: Editable Texts

    KNX / EIB Page: 26 of 81 Product Documentation 2. Editable Texts From the ETS plug-in, you can assign an identification text to each of the four arming areas, the four safeguarding areas, and to each integrated detector. In this connection, a maximum of 160 independent texts is available for the identification of the detectors of the up to four safeguarding areas as well as of the "fire detector"...
  • Page 27 KNX / EIB Page: 27 of 81 Product Documentation Immediate detector: A tripping detector will be evaluated immediately and will raise an immediate alarm when it is in the armed state. This setting is recommended for detectors which are not directly located within the entrance area of a building to be safeguarded (e.

  • Page 28: Connecting Detectors

    KNX / EIB Page: 28 of 81 Product Documentation 3.2 Connecting detectors You can connect the detectors of the alarm system to the Central alarm unit through the wired detector input or via suitable KNX components (e. g. binary inputs, pushbutton interfaces). In this connection, such components must correctly evaluate the switching edges, for example, of the magnetic contacts or glass breakage sensors and issue to the bus the telegram corresponding to such edge.

  • Page 29: Arming

    KNX / EIB Page: 29 of 81 Product Documentation 4. Arming 4.1 Arming devices 4.1.1 Configuring arming devices You can assign a maximum of four independent arming devices to each arming area. These arming devices such as key-operated switches, transponder arming devices, code keypads or block connecting links facilitate the acti- vation or deactivation of an arming area, i.

  • Page 30: Connecting Options Of Arming Devices

    KNX / EIB Page: 30 of 81 Product Documentation As a rule, arming devices also have sabotage contacts. Such contacts can be assigned to the safeguarding areas as detectors parameterized to "arming device sabotage". If an arming device is tampered with such device must no longer be authorized to disarm the system. In such case, the Central alarm unit will inhibit all telegrams which have been sent by the bus device 'tampered with' and will raise an alarm when in the armed state.
  • Page 31 KNX / EIB Page: 31 of 81 Product Documentation Example 2: Five arming devices per arming area, two of them being independent of each other (I + V), i. e. they act together on the same input of the pushbutton interface/binary input. Thus, these two arming devices have the same physical address and can no longer be clearly distinguished be- tween by the Central alarm unit.
  • Page 32 KNX / EIB Page: 32 of 81 Product Documentation Example 3: Four arming devices per arming area, two of them being independent of each other (I + II), i. e. they act together on the same input of the pushbutton interface/binary input. Thus, these two arming devices have the same physical address and can no longer be clearly distinguished be- tween by the Central alarm unit.

  • Page 33: Alarm Reset

    KNX / EIB Page: 33 of 81 Product Documentation 4.2 Alarm reset The Central alarm unit has an "alarm reset" ETS object (polarity: "1" = alarm reset/"0" = no response) through which alarms and all fault signals can be reset and messages in the displays acknowledged. To be able to reset fault signals it is assumed that the messages have been called into the display by the user (if any display units have been activated).

  • Page 34: Pre-Alarm

    KNX / EIB Page: 34 of 81 Product Documentation 4.4 Pre-alarm Once a delayed detector in an armed area has tripped, the alarm delay time (parameterizable per arming area from the "arming" parameter branch) will be started and a pre-alarm raised through the "pre-alarm" ETS object. Visual or audible alarm indicators will primarily be triggered by this object.
  • Page 35 KNX / EIB Page: 35 of 81 Product Documentation "Armed" state: You can only arm an area as soon as all detectors assigned to such area are not active, i. e. do not trip, and if there is no fault. The display units will indicate this by reading the "ready for arming" message. In systems with- out display units, this state can be indicated through the "ready for arming"...
  • Page 36 KNX / EIB Page: 36 of 81 Product Documentation "Pre-alarm" state: After a delayed detector has tripped in the armed state because a safeguarded area was, for example, entered before disarming the "pre-alarm" will only be activated if you have parameterized an alarm delay. In this state, you can disarm the area without raising an alarm.

  • Page 37: Arming Behaviour In Dependence Of The Configuration

    KNX / EIB Page: 37 of 81 Product Documentation 4.7 Arming behaviour in dependence of the configuration Arming areas can take different states at the same time and independently of one another. If areas are nested with one another or cascaded (refer to "1.3 Configurations", page 19) their states may possibly influence one another.

  • Page 38: Connecting Components To Implement Forced Arming

    KNX / EIB Page: 38 of 81 Product Documentation 4.8 Connecting components to implement forced arming - Motor-driven locking element and pulse door opener: An authorized person should only be allowed to enter a safeguarded building if no alarm is raised thereby, i.
  • Page 39 KNX / EIB Page: 39 of 81 Product Documentation - Block connecting link: A block connecting link can be installed into the front door or into the door to the flat instead of a conventional bolt lock. You can operate it through a common closing cylinder. You can use a block connecting link to open or close the door and, at the same time, to arm or disarm the alarm system.

  • Page 40: Operating The Central Alarm Unit

    KNX / EIB Page: 40 of 81 Product Documentation 5. Operating the Central alarm unit 5.1 Display units The Central alarm unit can trigger various display units. Thus, the system states of the Central alarm unit can be visualized and signals polled through up to four independent display units. KNX objects, by means of which you can, for example, trigger suitable info display units or display panels, are available for the coupling of the display units.

  • Page 41: Triggering The Display Units

    KNX / EIB Page: 41 of 81 Product Documentation 5.1.2 Triggering the display units (by the example of concealed info display unit 2.0 from version 2.x or later) Through the info display unit, a great variety of information on the general KNX installation can be visualized. To enable info display unit 2.0 to issue information of the Central alarm unit you must have parameterized a page in the ETS plug-in of the display as "page function = Central alarm unit display".

  • Page 42: Readable Information And Text Output Control

    KNX / EIB Page: 42 of 81 Product Documentation Assignment of the ETS objects between the Central alarm unit and the info display units: Link the display objects of the Central alarm unit to the ETS objects of the info display unit 1:1 per display unit. Info-Display Y Alarm Central Unit (Y = 1 to 4)
  • Page 43 KNX / EIB Page: 43 of 81 Product Documentation The following operational chart takes into consideration a configuration with four independent arming areas. Example: AA 1 is ready for arming; AA 2 is not ready because of an open detector; AA 3 is in the "disarmed after alarm"...

  • Page 44: Arming/Disarming And Alarm Acknowledgement Operations

    KNX / EIB Page: 44 of 81 Product Documentation 5.2 Arming/disarming and alarm acknowledgement operations 5.2.1 Arming The corresponding area must be ready for arming in the "disarmed" state. The display units will signal such readi- ness by issuing the "ready for arming message" per arming area. For this purpose, it is assumed that the corresponding arming area has been assigned to at least one display unit in the ETS plug-in.

  • Page 45: Alarm Acknowledgement After Intruder Or Sabotage Alarm

    KNX / EIB Page: 45 of 81 Product Documentation 5.2.3 Alarm acknowledgement after intruder or sabotage alarm For resetting an alarm, a "0" telegram must be received from an 'authorized' bus device through the "arming input" ETS object. In this connection, the audible alarm indicators will be switched off if these are still active. The flash- light and the intruder signal alarm transmission device will remain active if they had been on at the time of reset- ting.

  • Page 46: Alarm Acknowledgement Aft A Fire Alarm

    KNX / EIB Page: 46 of 81 Product Documentation Only in the "disarmed" state, the entire event log, which stores all tripped detectors one after the other, all alarms as well as all arming/disarming commands, can be read out by the ETS plug-in (refer to "9.

  • Page 47: Alarm Acknowledgement After An Attack Alarm

    KNX / EIB Page: 47 of 81 Product Documentation 5.2.5 Alarm acknowledgement after an attack alarm For resetting an attack alarm, a "0" telegram must be received from an 'authorized' bus device of any arming area through the "arming input" ETS object. In this connection, the audible alarm indicators will be switched off if these are still active.

  • Page 48: Fault Acknowledgement Operations

    KNX / EIB Page: 48 of 81 Product Documentation 5.3 Fault acknowledgement operations The Central alarm unit knows various causes of faults. Fault messages will be read in the display units in depend- ence of the areas concerned. A fault can have one of the following causes: Cause of Fault Message Text in the Display Units Remark...
  • Page 49 KNX / EIB Page: 49 of 81 Product Documentation 3) Such causes of faults will lead to 'global' fault messages in all arming areas. You must separately acknowledge such messages in each arming area. In the "fire" and "attack" areas, such fault messages will show no response. Special case for configuration 1: Global fault signals will cause Central alarm unit faults in this configuration.

  • Page 50: Alarming

    KNX / EIB Page: 50 of 81 Product Documentation 6. Alarming 6.1 Types of alarming: In the event of an alarm, alarming (for delayed detectors, after the delay time per arming area has elapsed) will be effected by so-called "alarm indicators". An alarm will be raised if •...

  • Page 51: Alarm Indicators For Remote Alarming

    KNX / EIB Page: 51 of 81 Product Documentation 6.1.2 Alarm indicators for remote alarming: In the event of an alarm, it is possible to trigger alarm transmission devices (depending on the parameterization). For this purpose, the following interfaces are available: •...

  • Page 52: Different Types Of Alarms

    KNX / EIB Page: 52 of 81 Product Documentation 6.2 Different types of alarms 6.2.1 Fire alarm In the event of a fire alarm, the "fire alarm" KNX object (fire alarm = "1") and the wired "ÜG-F" (fire alarm signal to the ATD) output of the Central alarm unit will always be triggered.

  • Page 53: System Monitoring

    KNX / EIB Page: 53 of 81 Product Documentation 7. System Monitoring 7.1 Detector monitoring Within a parameterizable monitoring period, the Central alarm unit will check the detectors created in the safe- guarding areas whether they are still connected to the KNX, thus still being present. In this connection, the Central alarm unit will send a value-reading telegram to the bus device to be checked, e.

  • Page 54: Heartbeat Check

    KNX / EIB Page: 54 of 81 Product Documentation 7.2 Heartbeat check Particularly large objects (arcades, extensive factory units) can possibly not be safeguarded by one Central alarm unit alone but require several Central alarm units, each of them monitoring partial complexes. Such Central alarm units can communicate with one another by sending and receiving telegrams for mutual moni- toring.

  • Page 55: Atd Checkback Input Fault

    KNX / EIB Page: 55 of 81 Product Documentation 7.3 ATD checkback input fault: For remote alarming, alarming by means of an alarm transmission device (telephone dialling device), for example, to a mobile telephone or to a property security company can be raised additionally or as an alternative (for example, for a silent alarm) to activate the local alarm indicators an (refer to "6.

  • Page 56: Event Log

    KNX / EIB Page: 56 of 81 Product Documentation 9. Event Log The Central alarm unit has an event log memory which is non-volatile in the case of mains or bus voltage failure, and in which certain fault messages, events in the "fire detector" and "attack detector" safeguarding areas as well as all events in armed areas will be saved.

  • Page 57: Date/Time

    KNX / EIB Page: 57 of 81 Product Documentation 10. Date/Time The Central alarm unit needs the current time and the current date to mark all events with a "time stamp" and to save them in the event log. It has two KNX objects, "time" and "date", through which, for example, an KNX-DCF77 receiver can transfer time signals (EIS 3) and date signals (EIS 4), thus setting the internal clock of the Central alarm unit.

  • Page 58: Bus Voltage Recovery

    KNX / EIB Page: 58 of 81 Product Documentation 11.2 Bus voltage recovery The Central alarm unit will initialize itself after bus voltage recovery. In this connection, the Central alarm unit will create a defined object state by setting all KNX output objects (alarm indicators, alarm outputs, objects for trigger- ing the alarm transmission device, etc.) to values which correspond to the system state as set after a bus voltage failure.

  • Page 59: Storage Battery Management

    KNX / EIB Page: 59 of 81 Product Documentation During the initialization phase, you can read the version number of the system software in line 1 of the display units, while the text message "initializing" will be displayed in line 2. In addition, the green "Betrieb" (device ON) LED will be blinking for the length of the initialization.

  • Page 60: Battery Replacement

    KNX / EIB Page: 60 of 81 Product Documentation End-of-life detection: In addition to cell monitoring, the battery will be put under load for some period once a month, a voltage difference being determined in this connection. If this difference is < 0.5 V the battery does not show any ageing effect yet and will be kept charging.

  • Page 61: Notes On The Integration Of Various Bus Components

    KNX / EIB Page: 61 of 81 Product Documentation 13. Notes on the Integration of Various Bus Components • komfort detectors/komfort presence detectors Such detectors can be integrated into the Central alarm unit. For the "komfort detector" and the "komfort pres- ence detector", you can change the mode through an KNX object while the Central alarm unit is in operation.
  • Page 62 KNX / EIB Page: 62 of 81 Product Documentation Parameters Description: Values: Comment: Central alarm unit Configurations of the Defines the configuration of the arming areas. safeguarding areas Configuration 1 Exclusively 1 x fire, 1 x attack. (The "fire detector" and "attack detector" areas always exist in parallel with another possibly enabled configuration.) Configuration 2.1...
  • Page 63 KNX / EIB Page: 63 of 81 Product Documentation Configurations of the Configuration 7.1 1 x safeguarding area (SA 1), separate; safeguarding areas 1 x safeguarding area (SA 4), cascaded, i. e. (continued) the arming areas must be armed one by one; 1 x safeguarding area (SA 3), separate and not integrated into the cascading.
  • Page 64 KNX / EIB Page: 64 of 81 Product Documentation Detector/sabotage Fire detector safeguarding area [Detector text] – [fire detector safeguarding area input X], X depends on the number of all detector inputs used (will be automatically created by the ETS plug-in). Input type Defines the type of the selected fire detector input.
  • Page 65 KNX / EIB Page: 65 of 81 Product Documentation Attack detector safeguarding area [Detector text] – [attack detector safeguarding area input X], X depends on the number of all detector inputs used (will be automatically created by the ETS plug-in). Input type Defines the type of the selected attack detector input.
  • Page 66 KNX / EIB Page: 66 of 81 Product Documentation [Detector text] – [Central alarm unit wired detector input] Safeguarding area SA 1 Defines the safeguarding area the wired detec- SA 2 * tor input is assigned to. SA 3 * SA 4 * Important: The wired detector input cannot be assigned to...
  • Page 67 KNX / EIB Page: 67 of 81 Product Documentation [Safeguarding area 1 identification] – [SA 1] The visibility of this area depends on the configuration. Safeguarding area Text Suggests an identification text of the safeguard- identification (no limited number of characters) ing area.
  • Page 68 KNX / EIB Page: 68 of 81 Product Documentation Detector type Defines the type of the selected detector. Only the text message in the display units will be oriented towards this setting. Contact The detector is of contact type, e. g. a window contact.
  • Page 69 KNX / EIB Page: 69 of 81 Product Documentation Arming [Arming area text] – [AA 1] The visibility of this area depends on the configuration. Arming area text 14-character text Defines the identification text of the arming area. This text will be issued in the display units for better identification.
  • Page 70 KNX / EIB Page: 70 of 81 Product Documentation SA 1 arming device If the selected arming device has a sabotage sabotage input number contact, and if such contact is connected to the Central alarm unit through a detector input of the safeguarding area parameterized to "arming device sabotage"...
  • Page 71 KNX / EIB Page: 71 of 81 Product Documentation AA 1 armed/disarmed state acknowledgement Signalization through Defines whether the "armed" state is to be for- 'armed state signal' to the warded to the alarm transmission device for arming area 1. Important: Please note that the "armed state signal to the ATD"...
  • Page 72 KNX / EIB Page: 72 of 81 Product Documentation Acknowledgement by relay You can signalize successful arming or disarm- ing by triggering the potential-free relay output. No acknowledgement by triggering the relay output. The relay output will be triggered upon an arm- ing or disarming operation.
  • Page 73 KNX / EIB Page: 73 of 81 Product Documentation [Arming area text] – [AA 2] The visibility of this area depends on the configuration. Refer to arming area 1. [Arming area text] – [AA 3] The visibility of this area depends on the configuration. Refer to arming area 1.
  • Page 74 KNX / EIB Page: 74 of 81 Product Documentation Alarming by relay Defines whether potential-free relay contact will be triggered in the event of an attack alarm. You can use the parameters in the "alarm indi- cators alarm period" parameter branch to define the triggering period.
  • Page 75 KNX / EIB Page: 75 of 81 Product Documentation Alarm indicators alarm period Flashlight ON period Defines the ON period of the flashlight in the event of an alarm. Always ON The flashlight will stay permanently activated until a change into the "disarmed" state takes place.
  • Page 76 KNX / EIB Page: 76 of 81 Product Documentation Indoor siren ON period Defines the ON period of the indoor siren in the event of an alarm. Always ON The indoor siren will stay permanently activated until the alarm is reset ("disarmed after alarm" state).
  • Page 77 KNX / EIB Page: 77 of 81 Product Documentation Display [Display unit 1 identification] Display unit 1 identification Text Suggests an identification text of display unit 1. (number of characters This text will only be used in the ETS plug-in for unlimited) better identification and will not be downloaded into the device.
  • Page 78 KNX / EIB Page: 78 of 81 Product Documentation Heartbeat check Several KNX Central alarm units can communi- cate with one another by sending and receiving telegrams for mutual monitoring. In this connec- tion, you can interconnect even more than two systems.
  • Page 79 KNX / EIB Page: 79 of 81 Product Documentation ATD checkback input response to attack signal to the ATD Flashlight If the alarm transmission device ("alarm" state) signals a fault in the event of an attack alarm ("ÜG-R" fault input active) subsequent alarming by the flashlight can be effected.
  • Page 80 KNX / EIB Page: 80 of 81 Product Documentation ATD checkback input response to intruder signal to the ATD Flashlight If the alarm transmission device ("alarm" state) signals a fault in the event of an intruder or sabotage alarm ("ÜG-R" fault input active) sub- sequent alarming by the flashlight can be ef- fected.
  • Page 81 KNX / EIB Page: 81 of 81 Product Documentation Remarks on the Software • ETS plug-in system requirements: Operating system: Windows 9x, ME, NT 4.0, 2000, XP ETS: ETS 2 v 1.2 a or later Pentium I processor (or similar), 166 MHz, 32 MB or better recommended. •...

Table of Contents