Omnia Installation Manual

ATTENTION The OMNIA 2.
1 software release or successive release

must be used for Control Panel programming.
BENTEL SECURITY srl reserves the right to modify the contents of this manual without prior notice.
via Florida - Z.I. Valtesino

63013 GROTTAMMARE (AP) - ITALY
Installation manual:
Expandable Multifunction Control Panel Omnia
V4.2 BUI 2.0 111298
TABLE OF CONTENTS
INTRODUCTION
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Main features . . . . . . . . . . . . . . . . . . . . . . . . 8
Omnia system . . . . . . . . . . . . . . . . . . . . . .
10
Specifications . . . . . . . . . . . . . . . . . . . . . .
14
2.0 version update and new features . . . . . . . . . .
15
PARTS IDENTIFICATION
17
Main unit . . . . . . . . . . . . . . . . . . . . . . . .
17
Control Keypad . . . . . . . . . . . . . . . . . . . . .
19
Key reader and Electronic key . . . . . . . . . . . . .
22
Input and Output expanders . . . . . . . . . . . . . .
23
INSTALLATION
25
Installation . . . . . . . . . . . . . . . . . . . . . . . .
25
Terminal-board description . . . . . . . . . . . . . . .
31
Main unit . . . . . . . . . . . . . . . . . . . . . . . .
31
BPI devices . . . . . . . . . . . . . . . . . . . . . . .
33
Connection diagrams . . . . . . . . . . . . . . . . . .
34
BPI device connection . . . . . . . . . . . . . . . . . .
35
Bus BPI length limitation . . . . . . . . . . . . . . . .
36
Alarm sensor connection . . . . . . . . . . . . . . . .
37
Fire sensors . . . . . . . . . . . . . . . . . . . . . . .
39
Alarm-device connection . . . . . . . . . . . . . . . .
39
Balanced tamper-line connection . . . . . . . . . . .
40
Telephone-line connection . . . . . . . . . . . . . . .
41
Power-supply connection . . . . . . . . . . . . . . . .
41
PROGRAMMING
43
Customer . . . . . . . . . . . . . . . . . . . . . . . . .
43
Configuration
. . . . . . . . . . . . . . . . . . . . . .
44
. . . . . . . . . . . . . . . . . . . . . . . .
46
Key readers . . . . . . . . . . . . . . . . . . . . . . .
46
Keypads
TABLE OF CONTENTS
Zones . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
Zone chart . . . . . . . . . . . . . . . . . . . . . . .
47
Description . . . . . . . . . . . . . . . . . . . . . . .
49
Type
. . . . . . . . . . . . . . . . . . . . . . . . . .
49
Attributes . . . . . . . . . . . . . . . . . . . . . . . .
50
Balancing . . . . . . . . . . . . . . . . . . . . . . . .
51
Cycles . . . . . . . . . . . . . . . . . . . . . . . . . .
52
Area . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
Sensitivity . . . . . . . . . . . . . . . . . . . . . . . .
52
Voice messages . . . . . . . . . . . . . . . . . . . .
53
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . .
54
Output chart . . . . . . . . . . . . . . . . . . . . . . .
55
Description . . . . . . . . . . . . . . . . . . . . . . .
55
Reserved . . . . . . . . . . . . . . . . . . . . . . . .
56
Type
. . . . . . . . . . . . . . . . . . . . . . . . . .
56
Attribute . . . . . . . . . . . . . . . . . . . . . . . . .
56
Timing . . . . . . . . . . . . . . . . . . . . . . . . . .
56
Off Time . . . . . . . . . . . . . . . . . . . . . . . . .
57
Areas . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
Telephone . . . . . . . . . . . . . . . . . . . . . . . .
60
Answer . . . . . . . . . . . . . . . . . . . . . . . . .
61
Dial . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
Description tones . . . . . . . . . . . . . . . . . . . .
62
Answering machine . . . . . . . . . . . . . . . . . . .
62
Dialler . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
Messages . . . . . . . . . . . . . . . . . . . . . . . .
65
Actions . . . . . . . . . . . . . . . . . . . . . . . . .
66
Pulse communicator . . . . . . . . . . . . . . . . . . .
67
Actions . . . . . . . . . . . . . . . . . . . . . . . . .
68
Teleservice . . . . . . . . . . . . . . . . . . . . . . . .
69
Event-Actions . . . . . . . . . . . . . . . . . . . . . .
71
Event description . . . . . . . . . . . . . . . . . . . .
73
Alarm events . . . . . . . . . . . . . . . . . . . . . .
74
Control-panel General events
. . . . . . . . . . . . .
76
Spot events . . . . . . . . . . . . . . . . . . . . . . .
79
DTMF communicator
. . . . . . . . . . . . . . . . . .
81
Test event
. . . . . . . . . . . . . . . . . . . . . . . .
82
Keypad codes . . . . . . . . . . . . . . . . . . . . . .
83
Parameters to be programmed by the installer . . . . .
83
Parameters to be programmed by the user
. . . . . .
88
Code status . . . . . . . . . . . . . . . . . . . . . . .
88
Programming . . . . . . . . . . . . . . . . . . . . . .
88
Electronic keys . . . . . . . . . . . . . . . . . . . . . .
91
Super keys . . . . . . . . . . . . . . . . . . . . . . . .
91
Filter times . . . . . . . . . . . . . . . . . . . . . . . .
91
Options . . . . . . . . . . . . . . . . . . . . . . . . . .
92
Timer programmer . . . . . . . . . . . . . . . . . . . .
93
LCD strings . . . . . . . . . . . . . . . . . . . . . . . .
93
Clock . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
Installer code . . . . . . . . . . . . . . . . . . . . . . .
94
Programming from local PC
. . . . . . . . . . . . . .
95
Programming from PC via telephone . . . . . . . . .
97
Keypad programming . . . . . . . . . . . . . . . . . .
99
Default reset . . . . . . . . . . . . . . . . . . . . . . .
99
Default setting . . . . . . . . . . . . . . . . . . . . . . 100

A basic system . . . . . . . . . . . . . . . . . . . . . . 102
Connections
. . . . . . . . . . . . . . . . . . . . . . 102
Programming . . . . . . . . . . . . . . . . . . . . . . 102
System use . . . . . . . . . . . . . . . . . . . . . . . 103
KEYPAD OPERATIONS
105
General rules for INSTALLER MENU use

INSTALLER MENU access
. . . . . . . 106
. . . . . . . . . . . . . . . 106
View logger . . . . . . . . . . . . . . . . . . . . . . . . 107

Zones status . . . . . . . . . . . . . . . . . . . . . . . 108
Outs managements . . . . . . . . . . . . . . . . . . . 109
Clear call queue . . . . . . . . . . . . . . . . . . . . . 109
Voice functions
. . . . . . . . . . . . . . . . . . . . . 110
Telephone-number Programming . . . . . . . . . . . 112

Description Programming . . . . . . . . . . . . . . . . 113
Installer code . . . . . . . . . . . . . . . . . . . . . . . 114
User codes . . . . . . . . . . . . . . . . . . . . . . . . 114
TABLE OF CONTENTS
Electronic keys . . . . . . . . . . . . . . . . . . . . . . 117

Enable
. . . . . . . . . . . . . . . . . . . . . . . . . 121
Parameter programming
. . . . . . . . . . . . . . . . 122
Firmware release . . . . . . . . . . . . . . . . . . . . . 122
OmniaVOX
123
Specifications . . . . . . . . . . . . . . . . . . . . . . 123
Identification of the parts . . . . . . . . . . . . . . . . 123
Installation . . . . . . . . . . . . . . . . . . . . . . . . 124
Extension of the Listen-in areas . . . . . . . . . . . . 125
Manual selection . . . . . . . . . . . . . . . . . . . . 126
Automatic selection . . . . . . . . . . . . . . . . . . . 127
Manual and automatic selection . . . . . . . . . . . . 128
OmniaTIMER
129
General characteristics . . . . . . . . . . . . . . . . . 129

Identification of the parts . . . . . . . . . . . . . . . . 130
Installation . . . . . . . . . . . . . . . . . . . . . . . . 130
Programming . . . . . . . . . . . . . . . . . . . . . . . 134
Applications . . . . . . . . . . . . . . . . . . . . . . . 138
Timer Applications . . . . . . . . . . . . . . . . . . . . 140
PC Connection . . . . . . . . . . . . . . . . . . . . . . 140
APPLICATIONS
141
Fast arming . . . . . . . . . . . . . . . . . . . . . . . . 141

Temporary disarming (patrol) . . . . . . . . . . . . . . 142
Management of a common Area . . . . . . . . . . . . 144
Several outputs assigned to the same event . . . . . 146
Multi-output event . . . . . . . . . . . . . . . . . . . . 147
Recognition of multiple codes . . . . . . . . . . . . . 149
Disarming under duress
. . . . . . . . . . . . . . . . 150
Solution no. 1 . . . . . . . . . . . . . . . . . . . . . . 150

Solution no. 2 . . . . . . . . . . . . . . . . . . . . . . 151
Dialler . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Alarm stop by means of Electronic key . . . . . . . . 157
INTRODUCTION
Overview
Omnia is an extremely powerful Control Panel of the latest generation.
This flexible system is more than able to meet the most demanding installation requirements.
Omnia may be expanded, programmed and operated with great ease.
There are 8 input Zones on the Control Panel, expandable to 80, and 4
outputs on the basic board, expandable to 36.
Areas
Omnia can manage 8 Areas, a feature which gives flexibility to system partitioning and shared management. The 8 Areas may be armed or disarmed
individually or as groups by means of Electronic keys, Codes or Controlpanel inputs. It is possible to make Areas dependent on one another, for
automatic management of the "Common Areas",
Events and
actions
Interactions among Inputs, Outputs and Telephone-dialler actions, whether

voice or digital, may be programmed according to requirements; in this
way, the installer is ensured exceptional operational flexibility.
The Omnia Control Panel can manage 443 events, the installer may select
the actions the Control Panel must perform for each event.
There are three basic actions: actions on outputs, actions on digital dialler
and actions on voice dialler.
This resourceful approach to security solutions makes Omnia adaptable to
the most diverse needs. Moreover, factory programming permits installand-go solutions for fast installation.
Telephone
functions
The telephone dialler manages up to 32 telephone numbers.

Four numbers may be assigned to the Pulse digital dialler, each with a
customer code and communication protocol, this makes communication
between several Central Stations possible.
A further four numbers may be assigned to the DTMF digital communicator, each number may be assigned to a customer code and a communication protocol.
4 telephone numbers are available for teleservice, these allow the Control
Panel to communicate with the installer modem, even when it has been
temporarily moved to different premises.
OmniaVOX
The OmniaVOX board offers a telephone-dialler function, which can dial 16

telephone numbers. Up to 14 different Voice messages may be sent by the
Control Panel, these messages must be recorded by the installer.
The OmniaVOX board provides the answering-machine function, one of
the 14 messages may be assigned to this function.
INTRODUCTION
Once in voice contact with the Control Panel (either after receiving a dialler
communication or when making a call to the Control Panel, which in turn is
answering with a recorded message), it is possible to perform many important actions such as: Listen-in, Two-way conversation, Input status inquiry
with voice answer from the Control Panel, remote ON/OFF control of system devices, area arming/disarming, alarm reset, call block and so forth.
All these operations are made possible by entering a secret code which
may be invalidated, if necessary, soon after use.
Programming
A powerful management software in Windows environment, makes Control panel programming extremely flexible, the software permits programming and supervision of the Control Panel, by either connecting to the
RS232 interface or to teleservice.
The Control Panel may be programmed from the Keypads, thus, making
quick maintenance intervention possible.
Timer
programming
The optional Timer-programmer board provides a wide range of functions

for automatic management of the system and permits Area arming/disarming on a daily/weekly basis. 8 fully independent daily timers are available
for the management of all event types, furthermore, management of a parallel or serial printer is also provided for.
Main features
Burglar control panel
r Up to 80 Alarm Zones: 8 on the Main unit, 64 on 16 Input expanders (4
zones each), 8 on 8 Keypads (1 Zone each Keypad).
r Up to 36 outputs: 2 relays and 2 open collectors on the Main unit, 32 on 8
Output expanders (4 outputs each).
r Up to 8 Keypads for system management, each with LCD.
r Up to 16 electronic-Key readers.
r Up to 2 Power stations, of 3 or 5 A, controlled by the Control Panel.
r 4-wire shielded bus for remote device connections, protected against short circuits.
r Bus duplication for protection against tamper.
r All Zones may be programmed as balanced, function and alarm type.
r Each entrance Zone may be programmed to send specific commands to
the Control Panel.
r All outputs are programmable as bistable or cyclic with programmable cycle time and OFF time.
r 8 programmable Areas each with its own Zones, Keypads, Key readers,
outputs and times.
r 31 user codes with programmable display, priority and functions.
r 250 electronic-Key readers each with a programmable display.
Expandable Multifunction Control Panel OMNIA
r Each system object (Zones, Keypads, Key readers, Codes, Electronic

Keys, Areas, etc.) may be identified with a 16-character name, which is
displayed on the Keypad during user operations.
r Storage of the last 200 events with date, time and user.
r RS232 interface for Control Panel programming and monitoring.
r Windows Software for Control Panel programming, teleservice and telecontrol.
Telephone functions
r DTMF and pulse selection.
r 32 telephone numbers available for telecontrol, teleservice and voice calls.
r Built-in Digital multiprotocol communicator for DTMF and pulse protocol
management.
r Possibility to carry out 10 different immediate alarm calls via Keypad.
r Programmable test-call.
r Possibility to enable recall.
r Line sharing with another answering device.
r 1200 baud FSK integrated modem for teleservice management.
Telephone functions with OmniaVOX optional board
r Telephone dialler for the management of 14 different Voice messages, to
be recorded by the installer for message communication to 16 different
telephone numbers.
r Remote-Inquiry to the Control Panel (using secret code) with voice answer.
r Remote output-control, Area arming status and alarm reset from Control
Panel (using secret code).
r Remote listen-in and multipoint telephone-conversation (using secret
code).
r Answering-machine function.
OmniaTIMER time programmer functions and printer interface
r Management on daily, weekly and monthly basis.
r Holiday and standard/summer-time management.
r Overtime and timeout-to-arm management.
r 2 arming and 2 disarming actions per day per Area.
r 8 fully independent daily timer channels.
r Centronics o RS232 parallel printer interface.
INTRODUCTION
Omnia system
Basic Control
Panel
Omnia/S
Omnia
The standard system is provided with the Main unit and a Control Keypad
and is available in two models:
Control Panel with 3 A switching power-supply.
Control Panel with 1.5 linear power-supply.
This manual is valid for both models, however, the differences in the two
power supplies are explained in the following chapter.
Expanders
Omnia can manage up to 16 input expanders, each equipped with 4 Zones

and a maximum of 8 output expanders, each with 4 open-collector type
outputs.
Control devices
These may be connected to the Control Panel by means of up to 16 electronic-key readers, and up to 8-LCD Keypads.
Omnia Vox
This is an optional board for voice call management and telearming functions.
Timer
programmer
This is an optional board for automatic management of the systems and

printer interface.
Management
Software
The management software in Windows environment will prove to be an

indispensable tool in achieving the full capacity of the Omnia system. In
fact, the software makes it possible to carry out Control Panel programming, manage a complete customer file, and also supervise the Control
Panel in real time.
OmniaMod
modem
By using the specific OmniaMod modem, the same software may be used
for the management of both manual and automatic teleservice connections, in this way, it is always possible to have a fully updated Customerfile. With the V2 modem version, it is possible to receive Central-Station
calls for real-time information on events occurring on the systems under
supervision.
Remote power
station
A 5 A capacity power-station is available for connection to the bus, this

supplies the required voltage to the remote devices during mains failure.
The power station is completely controlled by the Control Panel, which
manages the events generated by the remote power station (low or inefficient battery, mains failure); two devices may be connected to the bus.
10
Items
OMNIA
The following are the Omnia system items.

----
OMNIA/S
OMNIA/TAST-R
8-Zone Control Panel with Control Keypad and 1 A linear power-supply.

8-Zone Control Panel with Control Keypad and 3 A switching powersupply.
Additional Keypad with backlit LCD display.
OMNIA/4IN
4-input expander module.
OMNIA/4OUT
4-output expander module.
OMNIA/VOX
Voice function board.
OMNIA/VOX-MS
Microphone and loudspeaker for environmental listen-in.
BPI3
Recess Key-reader model TICINO magic.
BPI3LIV
Recess Key-reader model TICINO living.
BPI3INT
Recess Key-reader model TICINO international.
BPI3LGT
Recess Key-reader model TICINO light.
BPI3GEW
Recess Key-reader model GEWISS.
BPI3GP
Recess Key-reader model GEWISS playbus.
BPI3-GN
Recess Key-reader model GEWISS noir.
BPI3DEL
Recess Key-reader model DELTA.
BPI3-DN
Recess Key-reader model DELTA noir.
BPI3VI
Recess Key-reader model VIMAR idea.
BPI3VIB
Recess Key-reader model VIMAR bianco.
BPI3-AVE
Recess Key-reader model AVE.
BPI3-AN
Recess Key-reader model AVE noir.
BPI3W
DKC
----
Wall mounted Key-reader.

Electronic key.
OMNIA/4R
OMNIA/TIMER
----
4-relay module for the output expanders.

Timer programming and printer interface board.
OMNIA/MOD-V1
OMNIA/MOD-V2
CVSER/9F9F
ADSER/9M25F
OMNIA/SW
-------------
Teleservice modem.
Teleservice and remote monitoring modem.
Serial cable for PC connection.
25-pin adapter for serial ports.
Management software.
BXM12/30
BXM12/50
-------
3 A remote power-station.
5 A remote power-station.
INTRODUCTION
11
Figure 1
The Omnia system.
INTRODUCTION
13
Specifications
Model
OMNIA
Voltage
Max. input
Max. power
Insulation class
Power supply/Battery-charger
Max. current available for
external device supply
Battery
(Make and Model)
Operation temperature range
Dimensions (W x H x D)
Weight (without battery)
Meets CEI standard
Article
OMNIA/S Mother Board
Keypad
Recess Key-reader
Wall mounted Key-reader
Input Expander
Output Expander
4-relay module
Voice board + MicrophoneLoudspeaker board
Timer programming
and Printer interface board
Power station
14
230 V
0.2 A
45 W
13.8 V
OMNIA/S
50 Hz 10%
0.5 A
115 W
Class I
1.5 A
13.8 V
1A
3A
2A
12 V - 7 Ah or 12 V - 17 Ah
YUASA
NP 7-12 FR or NP 17-12 FR or
an equivalent with a case flame class of
UL94-V2 or better
5 40 C
330 x 460 x 100 mm
4.6 Kg
EN 50081-1/1992
EN 50082-1/1992
EN 41003:1997
EN 60950:1992 + A1:1993 + A2:1993 +
A3:1995 + A4:1996
nd
79/2 2 Ed. 1993 - Performance level 2 nd
Absorption
135 mA
50 mA
30 mA
30 mA
15 mA
20 mA
120 mA
Dimensions (WxHxD)
---160 x 73 x 30 mm
---51 x 73 x 28 mm
20 mA
----
40 mA
----
20 mA
234 x 345 x 96 mm
108 x 101 x 34 mm
2.0 version update and new features

The following is a list of the new features, of the Omnia 2.1 Control Panel,
and their descriptions.
The page numbers of the CHAPTERS, PARAGRAPHS and the SUBPAR. 1 are to be found in the TABLE OF CONTENTS, as follows:
CHAPTER
Paragraph
page
. . . . . . . . . . . . . . . . . . . . . . . page
Subpar. 1 . . . . . . . . . . . . . . . . . . . . . . . page
The SUBPAR. 2, however, are presented in the following way:
Subpar. 2
NEW FEATURE
Arming blocked on
remote power supply battery trouble
Factory
default
modifications
Text.
CHAPTER
PARAGRAPH
PROGRAMMING
Options
Default settings
PROGRAMMING
A basic system
Call queue priority

management
Alarm Stop Control
Panel alarm, using
Electronic key
New events
Transmission
of
several
events
during the same
telephone
communication
PROGRAMMING
Event-Actions
PROGRAMMING
Options
PROGRAMMING
Event-Actions
PROGRAMMING
Pulse
Communicator
INTRODUCTION
SUBPAR. 1
SUBPAR. 2
Disable arming
---on battery
trouble
Event-Actions
---Telephone
dialler
Telephone
numbers
Programming
Voice
messages
Priority of
---telephone
actions
Enable alarm
---stop on panel
with valid key
263 - Valid key
on panel
Control Panel
361 General Events
Telephone line
monitor trouble
----
----
15
Figure 2
16
Main unit parts
In this chapter the parts and LEDs of the main components on the Omnia
system are identified. The numbers in boldface in this manual refer to the
charts and diagrams in these pages.
Main unit
PARTS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
DESCRIPTION
Screws (2) for securing front panel to back.
Tamper switch.
Holes (4) for securing back ( 5 mm).
Extractable terminal boards.
Alarm block jumper:
> alarm enabled (default);
> alarm disabled.
DB9 male connector for PC connection with serial cable.
Jumper (MEM) stores the programmed settings during power failure:
> if power fails, programmed settings are lost (default);
> if
power fails, programmed settings are stored.
Make / Break setting jumper.
OmniaVOX board connector.
BPI device connector.
Cable hole.
Housing for buffer battery 12 V - 17 Ah maximum.
Supply block (see fig. 3).
Pull-off block.
Pull-off switch.
BPI1 (F 3.15A 250V) bus terminal 22[+] protection fuse.
BPI2 (F 3.15A 250V) bus terminal 18[+] protection fuse .
Main unit (F 3.15A 250V) terminal [+F] protection fuse .
terminal [+N], [+A] and [+B] (F 3.15A 250V) protection fuse.
LED
MEANING
Mains. ON: supply voltage is present.
Battery. ON: battery discharged or low.
Bus communication. ON: trouble with device communication.
17
Figure 3
18
Parts of the switching and linear power supply units.
PARTS
20
21
22
23
24
25
26
27
DESCRIPTION
Red Led shows mains supply present.
Output voltage (fine) adjustment Trimmer.
External device supply terminals (13.8 V ).
Mains voltage connection terminals (230 V
/ 50 Hz).
Buffer-battery connectors.
Plastic pin, to be removed, in order to open the switching-power supply.
Power supply protection fuse:
Omnia = F 250 mA 250V;
OmniaS = F 2A 250V.
Fuse (F 8A 250V) protection against accidental polarity inversion in the
buffer battery.
Control Keypad
ICONS
MEANING
Armed-Area signalling.
Alarm-memory signalling.
Control-Panel-malfunction signalling.
Control-Panel door open.
Tamper line alarm.
Device tamper.
False key on key reader.
Configured devices cannot be reached.
Teleservice enabled
Answering device enabled
Engaged telephone line.
19
PARTS
DESCRIPTION
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Figure 4
20
Flap.
View window for main LEDs (On, Alarm and Warning).
Screws (4) for securing box to back.
LCD display .
Terminal identification tab in accordance with the device address.
Reference pins (2) for board positioning.
Connection terminals.
Plastic hooks (2) for securing board.
Pull-off switch.
Device identification tab in accordance with dipswitch configuration 38 .
Tamper switch.
Address setting dipswitches.
Plastic hooks (2) for securing board.
Cable hole.
Holes (2) for securing back ( 4 mm).
Hole for securing Pull-off switch.
Buzzer.
Buzzer connector.
Control Keypad parts (external view).
Figure 5
Control Keypad parts (external view).
21
Key reader and Electronic key
The key reader is not provided with the Omnia Control panel. It may be
purchased separately and is available in several versions for recess
mounting, and one version for wall mounting (see "Items").
Figure 6 refers to the Magic-box version.
PARTS
DESCRIPTION
46
47
48
49
50
51
52
53
54
55
Connection terminals.
Device identification tab in accordance with dipswitch configuration 47.
Cable holes.
Fixing holes (2).
Holes for securing the Pull-off switch.
Pull-off switch.
Tamper switch.
Electronic key slot.
Control button (on Electronic key).
In the first column of the following table, the word in inverted commas refers to the colour of the LED.
LED
"red" ON:
"amber" ON:
"green" ON:
Figure 6
22
MEANING
Enabled Areas on the Key reader are armed.
Type A arming.
Type B arming.
Parts of the Magic (a) and wall-mounted (b) Key reader, and Electronic key (c).
Input and Output expanders

PARTS
56
57
58
59
60
61
62
63
DESCRIPTION
BPI Bus connection terminal.
Device identification tab in accordance with dipswitch configuration 59.
Input Zone connection terminal.
Tamper and Pull-off switch bypass jumper:
> switches active.
> switches bypassed (default);
Pull-off switch.
Tamper switch.
Buzzer.
Buzzer operation mode selection jumper:

> bypassed buzzer (default);
64
> the buzzer sounds when the terminal [OC4] is open;
> the buzzer sounds when the terminal [OC4] is earthed.
65 Open-collector output terminal board, 150 mA maximum.
66 Terminal identification tab in accordance with the device address.
Figure 7
Parts of the Input and Output Expanders.
23
PARTS
DESCRIPTION
67
68
69
70
71
72
73
74
75
Figure 8
24
Box screws (4).

Input or Output expander or 4 relay Module.
Expander screws (2).
Opening for cable duct or externally laid cables.
Holes (2) for mounting on the model 503 box.
Opening for cable duct.
Holes (2) for wall mounting.
Hole for the Pull-off block screw.
Tooth for securing the tamper switch.
Parts of the box for the Expanders and the 4 Relay module.
INSTALLATION
Installation
Before installing the security system devices, it is advisable to plan the layout and lay the necessary connection cables.
Main unit
The Main unit must be installed in a protected, and if possible, hidden

place. The chosen position must be within reach of the connection cables
of the other security system devices, the mains voltage supply (including
the earth connection) and, if required, the telephone line.
Drill the necessary holes for the installation of the Main unit, and the pulloff block, 3 and 14 in the diagram.
Pass the connection cables through the cable hole 11 and fix the Main unit
and the pull-off block in place.
Do not over tighten the screws, as this may damage the lugs on the pull-off
block.
Install any supplementary boards (Omnia4IN, Omnia4OUT, OmniaVOX,

OmniaTIMER, etc.) in the Main unit, as described in the relevant paragraphs.
Carry out the necessary connections, leaving the power supply connections to the last.
Control Keypad
The Control Keypad should be positioned in a place that requires complete

control of the security system.
The Keypad should be positioned at about 160 cm. from the ground, in order to allow full view of the display.
INSTALLATION
25
Unscrew the screws 30 and remove the Keypad box.
Remove the connector 45.
Using the thumbs, put pressure on the plastic clips 35 in order to free the
electronic board.
Drill the necessary holes for mounting the Control Keypad, and the pull-off
block , 42 and 43 respectively in the diagram.
Pass the connection cable through the cable hole 41.
Fix the Keypad base and pull-off block in place.
Replace the electronic board and the connector 45.
Assign the identifier number to the keypad, by means of the dipswitches

39, then carry out the connections on the terminal board 34.
Figure 9
26
Replace the Keypad box.
Installation of a Control Keypad.
Recess Key
reader
The Key reader may be installed in a place where limited control of the security system is sufficient.
Assign an identifier number to the Key reader, by means of the dipswitches

Fix the Key reader in place, in the same way as one would a household
light switch or electric socket.
ATTENTION For an installation that meets the Standard required, recess Key readers installed in places outside the protection of the security system, must be equipped with a tamper device (see the
example in figure 10a).
Wall mounted
Key-reader
Figure 10
Wall mounted Key-readers (art. BPI3W) function in the exact same way as
recess Key-readers, however, wall mounted Key-readers have boxes for
wall mounting, whilst recess Key-readers require recess boxes. Wall
mounted Key-readers are designed to allow the keypad and Key reader to
be mounted side by side.
Open the Key reader.
Drill the necessary holes for the installation of the Key reader, and the pulloff block, 50 and 51 respectively in the diagram.
Pass the connection cable through the cable hole 49.
Fix the Key reader and pull-off block in place.
Assign an identifier number to the Key reader, by means of the dipswitches

Close the Key reader.
Installation of a recess Key reader (a) and a wall mounted Key reader (b).
INSTALLATION
27
Expanders and
Relay modules
The Input and Output expanders and the Relay module must be placed as
near as possible to the connected devices. They are equipped with either
an on-view (for wall mounting) or recess box.
unscrew the screws 67 and remove the front cover.
Unscrew the screws 69 and remove the electronic board.
Open hole 70, or 72 depending on the cable layout.
- If on-view mounting of the box is required, drill the necessary holes for
the box, and the pull-off block, 73 and 74 respectively in the diagram, (see
fig. 11b);
- if on-view mounting on a model 503 box is required, it is necessary to
drill the hole for the pull-off block only (fig. 11c);
- it is not necessary to drill any holes for recess installation (fig. 11a).
Pass the connection cables through the cable hole.
Fix the box and pull-off block in place.
The pull-off block must be positioned as shown in figure 11, for both wall
and recess mounting.
Replace the electronic board inside the box.
Assign an identifier number to the expander, by means of the dipswitches

59, then carry out the connections on the terminal boards.
Remove the jumper 60 (activated tamper and pull-off switches).
Set the function mode of the Output-expander buzzer, by means of the

jumper 64.
Close the box.
Be careful not to damage the plastic tooth 75, as this must secure the tamper switch in place.
The Input and Output expanders and the relay module can be installed in
the Main unit, as shown in figure 12, by means of the suitable supports,
supplied on request.
ATTENTION The pull-off and tamper switches, of the Input and Output expanders installed inside the Main unit, must be bypassed by
connecting the jumper 60.
28
Figure 11
Expander installation: (a) recess; (b) on view; (c) inside mod.503 box .
PARTS
76
77
78
79
80
81
82
83
Figure 12
30
DESCRIPTION
Expanders (Omnis4IN, Omnia4OUT, Omnia4R): max. 3.
Loudspeaker.
Printer Interface - Timer Programmer (OmniaTIMER).
Voltage supply.
Battery 12 V - 17 Ah max.
Voice board.
Mother board.
Microphone board.
Maximum configuration of the Main unit.
Terminal-board description
The following is a brief description of the Main unit terminal boards, and
the devices that can be connected to the bus:
the TERMINAL BOARDS column contains the sequential number and (in
square brackets) the initial/s of the described terminal(s);
the DESCRIPTION column contains a brief description of the terminal(s)

listed in the M. column;
the V column shows the voltage on the described terminal(s) (the symbol "/"
shows that a voltage value cannot be specified);
the I column contains the maximum current value (in amperes) that may
circulate on the terminal(s) described (the symbol "/" shows that a voltage
value cannot be specified); in this column the numbers in round brackets
are relevant to the notes at the bottom of the chart.
Main unit
TERMINALS
DESCRIPTION
Connected terminals
(not in the model with switching power-supply).
External device power supply protected by fuse 19 and
supplied by the buffer battery during mains failure.
RL1 output (free voltage exchange):
normal C1 connected with NC1 and NO1 open;
alarm C1 connected with NO1 and NC1 open.
RL1 programmable output (positive):
normal open terminal;
alarm voltage on terminal.
RL1 programmable output :
normal voltage on terminal;
alarm open terminal.
RL2 programmable output (free voltage exchange):
normal C2 connected with NC2 and NO2 open;
alarm C2 connected with NO2 and NC2 open.
RL2 programmable(positive) output:
normal open terminal;
alarm voltage on terminal.
RL2 programmable output:
normal voltage on terminal;
alarm open terminal.
Programmable open-collector output.
Programmable open-collector output.
13.8
(1)
13.8
(1)
13.8
(1)
13.8
(1)
13.8
(1)
0
0
1
1
Ground.
Device connection Bus BPI1 (LCD Keypads, Input Exp.,

Output Exp., Key readers).
(2)
(1)
1-2 [AC]
3-4 [+B-
5-6-7
[NA1-NC1-C1]
8 [+A1]
9 [+N1]
10-11-12
[NA1-NC1-C1]
13 [+A2]
14 [+N2]
15 [OC1]
16 [OC2]
17 [ ]
18-19-20-21
[+-C-R- ]
INSTALLATION
31
TERMINALS
22-23-24-25
[+-C-R- ]
26-27 [
- ASB]
28-31-34-37
40-43-46-49 [ ]
29-32-35-38-41-44
47-50 [L1 L8]
30-33-36-39-42
45-48-51 [+F]
52 [ ]
53-54 [LE]
55-56 [LI]
32
DESCRIPTION
Device connection Bus BPI2 (LCD Keypads, Input Exp.,

Output Exp., Key readers).
(2)
(1)
Balanced tamper line (terminal [ASB]) normally connected

to the ground (terminal [ ) by means of a 10K. heater
Input-line ground.
Programmable input lines.
13.8
(1)
Sensor power supply protected by fuse 18 and supplied by

the buffer battery during mains supply failure.
Ground connection.
Connection terminal for external telephone line.
Connection terminal for further telephone devices on the
same telephone line as Omnia (answering machines,
telephones, fax machines, modems, etc.).
(1)
The sum of the current on terminals [+F], [+B], [+], [+A] and [+N] of the
Main unit should not exceed 2 A with Omnia/S and 1 A with Omnia.
(2)
On the [+] terminals of the Main unit a voltage of 13.8 V is present, protected by fuse 16 for BPI1, and by fuse 17 for BPI2, this voltage is supplied
by the buffer battery during mains supply failure.
(3)
The current absorbed by the terminals [+] of the BPI devices is the following:
- Keypad = 50 mA;
- Key reader = 30 mA;
- Input expander = 15 mA;
- Output expander = 20 mA;
- Power station = 20 mA.
These absorptions do not include those of the power supply to the devices
connected to the BPI devices.
(4)
The sum of the current absorbed by the Input expander terminals [+F]
should not exceed 0.4 A.
BPI devices
The BPI devices are: LCD Keypads, Electronic-key readers, Input expanders, Output expanders and Power stations. The following chart describes the terminals, which are common to all BPI devices, for connection
to the BPI Bus of the Control panel.
TERMINALS
[+]
[R]
[C]
[--]
Key reader
DESCRIPTION
Supply: positive.
"Answer" terminal to be connected to the corresponding
terminal on the Main unit.
"Command terminal to be connected to the corresponding
terminal on the Main unit.
Supply: negative.
DESCRIPTION
tamper switch:
closed if switches 52 and 53 are closed;
open if switches 52 and 53 are open.
[AS]
The Keypad, in addition to the bus connection terminals, has the following
terminals:
TERMINALS
[L1]
DESCRIPTION
Programmable input line.
Input-line ground.
[ ]
Input expander
I
(3)
The recess Key reader has only bus connection terminals whereas the wall
mounted Key reader also has the following terminals:
TERMINALS
Keypad
V
13.8
V
/
0
I
/
/
In addition to the bus connection terminals, the input expander has the following terminals:
TERMINALS
[L1] [L2] [L3] [L4]
DESCRIPTION
Programmable input lines.
V
/
I
/
[ ]
[+F]
Input-line ground.
Sensor supply protected by resettable fuse.
0
13.8
/
(4)
Output expander
In addition to the bus connection terminals the output expander has the following terminals:
TERMINALS
DESCRIPTION
Power supply for any devices that may be connected to
open-collector outputs, protected by resettable fuse.
[+12V]
13.8
0.4
[OC1] [OC2]
[OC3] [OC4]
Programmable open-collector outputs.
0.15
[ ]
Ground terminals.
Power station
Please refer to the manual provided with the device.
INSTALLATION
33
Connection diagrams
The following pages contain the connection diagrams of the Omnia Main
unit, and all the necessary information on the BPI devices and various
other items of an Omnia security system.
In order to make the connections clear, each device group (BPI devices,
sensors, alarms devices etc.), is dealt with separately.
The connections should be made with shielded cable, one end of the cable
must be connected to ground and the other left free.
The examples shown are for reference only, as it would be impossible to illustrate all the applications available.
Diagram
symbols
The diagrams have been simplified to facilitate understanding.
The terminals for the input and open-collector-output zones can be either
Main unit or expander terminals.
The terminals are displayed one by one.

The terminals may not be in the exact same position on the actual board,
differences may occur, as connection crossing in the diagram has been reduced to the minimum.
Figure 13
34
The negative terminals are indicated by the symbol

on the Main unit
mother board, and by the symbol
on all other boards.
Connection example of 3 BPI devices to the bus.
BPI device connection

The Control Panel permits the following connections to the bus:
up to 8 control Keypads;
up to 16 electronic-key readers;
up to 16 input expanders;
up to 8 output expanders;
up to 2 power stations.
Electrical
connections
The BPI devices are all connected to the bus in the same way; all devices
require parallel connection on terminals [+], [C], [R], [ ] of the communication bus.
Double bus
The communication bus is physically doubled, in fact the terminals relative

to the bus are (18-19-20-21 and 22-23-24-25). The two buses are protected by several fuses, in this way, a short-circuit on one bus does not
damage the other.
One bus must be used for the installation of outdoor BPI devices, and the
other for the remaining devices, in this way, any tamper attempt on the outside (signalled by the Control Panel), does not damage the functional capacity of the other line of the bus.
Figure 13 illustrates the connection of 3 devices, which may be Keypads,
key readers, input expanders, output expanders or power stations.
If the system provides for more than one device of the same type, these
must be given different addresses. This operation is called "device coding".
Device coding
The BPI device coding is carried out by means of the dipswitches: 39 for
Keypads, 47 for Key readers and 59 for input and output expanders.
For power stations, see the manual provided.
The address is assigned according to the position of the dipswitches. The
following table shows the 16 possible combinations.
Microswitch N.
1
2
3
4
+
+
+
1
off
off
off
off
2
off
off
off
ON
3
off
off
ON
off
4
off
off
ON
ON
5
off
ON
off
off
6
off
ON
off
ON
7
off
ON
ON
off
Address
8
9
off ON
ON off
ON off
ON off
10
ON
off
off
ON
11
ON
off
ON
off
12
ON
off
ON
ON
13
ON
ON
off
off
14
ON
ON
off
ON
15
ON
ON
ON
off
16
ON
ON
ON
ON
The assigned addresses must be different for each device of the same
type. Although, devices of different types may have the same address.
A maximum of 8 LCD Keypads and Output expanders may be connected to the bus. Dipswitch no.1 does not affect these devices.
It is not necessary to follow any particular order when assigning codes,
however, all codes must be different.
INSTALLATION
35
Bus BPI length limitation

The voltage drops and stray capacitance caused by the BPI bus connections of the Main unit, make length limitation necessary.
Proper functioning of the BPI devices is ensured by a supply voltage between
terminals [+] and [ ] higher or equal to 10 V otherwise, it is possible to:
increase the wire section that carries the power to the device (those wires
connecting terminals [+] and [
the device) respectively;
] of the Main unit, terminals [+] and [ ] of
restore supply by means of a power station;

limit the BPI device current absorption, by supplying the connected devices
by means of a Power station.
In all cases, due to the stray capacitance caused by the connection cable,
a BPI device cannot be connected to the Main unit by a cable of more than
500 m, and the overall length of the cables connected to each BPI bus of
the Main unit must not be longer than 1,000 m.
Figure 14
36
Sensor connection to Normally Closed line.
Alarm sensor connection

Omnia has 8 Zones on the Main unit board, for the connection of sensors,
4 Zones on each input expander and 1 Zone on each Control Keypad. The
total number of Zones is: 8 + 4 x16 + 1 x 8 = 80.
The terminals corresponding to the input Zones are those labelled with [Ln]
(n is the zone number), each Zone has its own supply from the terminals
[+F] and [ ]. All these terminals are available on the Main unit, on the input and output expanders and on the Keypads.
Terminal [+F], which supplies power to the connected sensor, is not present on the Keypad; however, it is possible to use terminal [+] of the communication bus power supply .
Each terminal may be connected to one or more sensors, although, it is
advisable to connect only one sensor to each terminal, in this way, the sensor in alarm status is easily identified.
It is possible to connect sensors with a normally open alarm-switch, and
sensors with a normally closed alarm-switch. All the input Zones are programmable as NC, NO, Balanced or Double balanced.
If Zones are to be used as Balanced or Double Balanced Zones , use the
10 K resistors provided.
If programming of the Zones as NC (Normally Closed) or NO (Normally
Open) is required, balancing resistors are not necessary.
Figure 15
Sensor connection to Balanced line.
INSTALLATION
37
Double
balancing
By means of the double balancing mode, and by connecting 4 wires to the

sensors, it is possible to obtain information on both sensor alarm and tamper. In this way, it is possible to identify the sensor signalling alarm.
The diagrams show the connections for the three balancing types (NC,
Balanced, Double Balanced), required for the connection of an alarm sensor to a Zone.
The sensor supply is protected by fuse 18, burnout of this fuse is shown by
the
38
LED on the LCD Keypad.
The tamper-switch connection (terminals A.S.) is dealt with separately in

the Balanced tamper-line connection" paragraph.
Figure 16
Sensor connection to Double Balanced line.
Figure 17
Connection of three fire detectors.
Fire sensors
Omnia control panel is able to manage fire sensors, providing that these
can operate with 12 V supply voltage and are equipped with an alarm repeat output (for example the BENTEL sensors RT101-102 or RF501).
For the connection of one or more fire sensors proceed as shown in figure 17.
The fire sensor outputs should be connected to an Omnia Zone, programmed as Fire. Sensors are supplied by terminal +F, whilst ground
should be taken from an Omnia output (in the example the auxiliary output
15 [OC1] is used), programmed as 20 seconds, monostable, NC. The output must be assigned to an event intended for fire sensor reset, for example Control Panel Default or "Area Default".
Please remember that terminal 15 [OC1] can support a max. 1 A current

value.
Alarm-device connection
Alarm devices signal alarm conditions, typical alarm devices are self-powered sirens, indoor sirens, telephone diallers and so forth.
These devices may be classified according to their activation mode in the
following way:
stand-alone safety devices, enabled by voltage failure on the specific terminal; self-powered sirens belong to this category.
Positive alarm line devices, enabled by a positive (12 V) on the specific terminal; indoor sirens usually belong to this category.
Negative alarm-line devices, enabled by ground on the specific terminal.

Balanced alarm-line device, enabled by the impedance offset on the specific terminal.
Figure 18
Connection of self-powered siren and indoor siren.
INSTALLATION
39
Omnia is provided with terminals 8 [+A1] and 13 [+A2] for the connection
of two indoor sirens, and terminals 9 [+N1] and 14 [+N2] for the connection
of self-powered sirens (fig. 18).
The free-voltage exchanges of the two alarm relays (terminals 5, 6, 7 and
10, 11, 12) are for the connection of all types of signalling devices.
Although there are two alarm relays with relevant terminals, as described
above, Omnia also has a further 34 open-collector outputs (2 on the
mother board and 4 on each of the 8 connectible output expanders), each
of these may be programmed as an alarm output and may pilot a relay.
The diagram below illustrates a connection example of a self-powered siren and an indoor siren, connected to the first alarm relay.
The connection of tamper switches (terminals [S] and [S1]), is dealt with
separately in the "Balanced tamper-line connection" paragraph.
Balanced tamper-line connection

Omnia is provided with a 24h balanced-type tamper line, for the connection
of the tamper switches on the security-system devices. Connection is to be
carried out as follows (see fig.19):
Connect the tamper switches of the security system in series.

Connect one end of the series to terminal 27[ASB] and the other to terminal 26[
]; connect the balance resistor to the last device.
When making use of the tamper line, the information relevant to the tampered device is not available. If this information is required, when connecting sensors, use the Double Balancing mode or, a 24h zone for tamper
detection on other devices.
Figure 19
40
Connection of tamper switches.
Telephone-line connection
If the telephone communicator functions are used, the telephone line must
be connected to terminals 53, 54 [LE]. If the telephone line is shared with
another telephone, the latter must be connected to terminals 55, 56 [LI], in
this way Omnia always gives priority to the telephone device connected to
the [LI] terminals and commutes it only when necessary.
The ground [ ] terminal must be connected to the ground connector of the
electrical system, in order to protect the electronic card from surges that
may come from the telephone line.
ATTENTION The safety protection of the telecommunication network
depends on the perfect condition of the entire ground protection.
Power-supply connection
The Omnia Control Panel is supplied by a mains voltage of 230 V / 50 Hz
and by means of :
an integrated power supply on the electronic board of the OMNIA model;

a switching power supply located at the bottom of the OMNIA/S model box.
The mains supply wires must be connected to the terminals 23, whilst the
buffer battery must be connected to the connectors 24.
ATTENTION Connect the phase to terminal [L] (marked [F] in the
Omnia control panel) and connect terminal [ ] (marked [ ] in the
Omnia control panel) to ground. Please remember that all the territorial
regulations in force must be respected.
As soon as power is supplied to the Main unit, the green LED
, on the
front panel will switch ON, whereas, after the initial configuration stage the
red LEDs
Figure 20
and
will switch OFF.
The buffer battery should be connected before the mains voltage.
Telephone line connection diagram.
INSTALLATION
41
Auto
configuration
On first startup the Control Panel performs an Auto-configuration cycle.

During this cycle the Control Panel acquires the configuration of the devices connected to the bus. This becomes the basic configuration of the
Control Panel and may only be modified by the installer. This step lasts
about 15 seconds and is indicated by the flashing of the red LED
At the end of this step, which is signalled by the following configuration on

:1 1996/5/3
the Keypad display DDDDDDDD
, insert jumper 7 (MEM) which
enables the non-volatile memory to store the programmed data even during mains supply failure.
ATTENTION On startup the storage memory is completely down.
About 1 hour is required to charge it to a level that will ensure storage
of the programmed data for 1 month of complete power supply failure
(both external supply from the mains network and from the auxiliary
supply, provided by the battery housed at the bottom of the Main unit
container). In order to charge the storage battery jumper 7 (MEM)
must be connected.
There is no Open-Control-Panel alarm on startup, as this is disabled until

the Control Panel cover is closed. Similarly, when quitting a programming
session, either via Keypad or local/remote PC connection, the Open-Control-Panel alarm results disabled until the cover is replaced, after which,
opening of the Control Panel provokes a tamper alarm.
If the network voltage fails, supply is ensured by the buffer battery and failure is signalled:
on the front panel of the Main unit, by the LED

on the Control Keypads, by the LED
switching OFF;
switching ON;
by event no. 223 - Warning mains failure - that may be assigned to an

action on an output or on the communicator (this event may be delayed, by
a programmable timeout).
Causes of malfunction must always be found and eliminated before the
battery runs down. When the buffer battery is low, and therefore requiring
immediate action, if functionality loss is to be avoided, it is signalled by
event no. 224 - Warning low battery, which may be assigned to an action
on an output or on the communicator. However, when power is restored,
the Control Panel regains its previous configuration, this is due to the nonvolatile memory which logs all the status changes that occur during Control
Panel functioning.
42
PROGRAMMING
All Omnia parameters may be defined in the optional program, which runs
in Windows environment, or may be programmed from the Control Panel
Keypad. Programming from the PC is much easier than programming from
the Keypad, therefore, the program in Windows environment is used for
the Omnia parameter descriptions.
For a complete description of the Omnia program, see the "Omnia-NormaCom software" manual.
Omnia parameter programming is divided into several pages, which group
together parameters concerning the same feature. The following paragraphs describe the programming pages, as displayed by the Omnia program.
Customer
This page is for Customer details: the data entered in the Address, City,
Customer tel.num and Installation description fields are for installer
use, and are not fundamental to programming. However, the data entered
in the following fields are essential.
Name
This is the name the program uses to identify a customer, and to display
the data defined in the various pages.
Installation tel.
num.
This is the telephone number the Control Panel is connected to. This number is dialled by the OmniaMOD modem, when the Connecting command
from the Modem menu is selected.
The Installation tel. num. field accepts digits from 0 through 9 and also
the comma (,): the comma is for pauses, for example, between a telephone number and area code.
Customer code
+
Firmware release
When an Omnia Control Panel calls the OmniaMOD modem (for teleservice or the test call) the modem recognizes the Control Panel by the code
entered in this field; therefore, each Control Panel must have a different
Customer Code. If a duplicate Customer Code is assigned, the existence
of the code, and the Control Panel it is assigned to, will be signalled when
an attempt to save modifications is made.
The Customer Code specified in this page is the same as the code in the
{Teleservice} page, therefore, any changes made to either code will affect
the other automatically.
This field cannot be modified within the Customer page; by selecting the
Firmware release command from the Option menu, the field displays the
set value and indicates the parameters that may be defined in the program, according to the version of the connected Control Panel.
PROGRAMMING
43
Date of Last
change
This parameter cannot be modified manually, and it is updated automatically to the date of the last modification for the selected customer.
Notes
This button opens a window for notes on the selected customer and system. These notes do not appear in the Installation description field. If the
note pad is empty, the icon on the button shows an empty page, otherwise,
a full page is shown.
Configuration
The definition of the Control-Panel configuration is essential for proper programming and functioning. The Control Panel must be able to recognize
the communication-bus configuration, and detect the removal of any device from the communication bus, as this may be due to tamper.
On initial Startup the Control Panel performs an auto-configuration cycle,
which sets the configuration of the BPI bus devices (see the "Power supply
connection" paragraph). Any changes in the configuration must be carried
out by the installer.
If the Control Panel is connected to a PC, the configuration may be read by

selecting the Load > Page command on the Programming menu (see the
relevant paragraph).
The configuration programming page is divided into different sections, one
for each device type (Keypads, Key readers, Input expanders, Output expanders, Power stations).
Figure 21
44
Client description page.
Each section has a series of boxes, a number indicating the device address is situated near each box. This address is set by means of the dipswitches on the various peripheral devices (see the "Peripheral device
connection" paragraph).
In order to set the configuration, it is necessary to select the required peripheral devices. If a marker is present, the device is already in the configuration; if not (white box), the device is not in the configuration. Devices not
included in the configuration are not controlled by the Control Panel and
should be considered as "virtually disconnected".
After setting the device configuration, it is possible to program some of the
characteristics in the Details windows. The parameters for all device types
(Keypads, Key readers, Input expanders, Output expanders and Power
Stations) must be specified in the Details window; it is also necessary to
define the Keypad and Key reader parameters, according to the instructions in the relevant paragraphs.
no.
This is the peripheral device ID number (the device address), which depends on the configuration of its dip-switches.
Description
It is possible to assign a name, with a maximum of 16 characters, to each

device, this name is used as the device identifier in all the operations it is
involved in.
Figure 22
System configuration page.
PROGRAMMING
45
Keypads
1 ... 8
This specifies the Areas a Keypad can operate on (Arm, Disarm, etc.).
A Keypad may be unable to operate on any Area, however, it may be used
for programming, display and all other functions that do not involve Areas.
Key readers
Omnia functions may be checked by simply inserting a valid Electronic key
into a Key reader, for functions such as:
Area arming;
Area disarming;
Type A or B arming;
Alarm stop on Areas.
Omnia can manage up to 16 Key readers and up to 250 Electronic keys.
The parameters described in the following paragraphs can be defined for
each Key reader, whereas, Electronic key programming may be carried out
via Keypad, as described in the "Electronic keys" paragraph.
RED spot marker
This indicates the Areas the Key reader can operate on (arm, disarm, and
stop warning signals): Areas are indicated by their identifier number (1
through 8); cells containing "Yes" (where the row indicated by the RED
spot marker slices the Area identifier number row) indicate the Key reader
is enabled on the corresponding Area; by double-clicking or pressing the
ENTER key on the selected cell, the status of the corresponding Area can
be changed.
AMBER spot
marker
This indicates the Areas to be armed (A) and those to be disarmed (D),
among those enabled, on extraction of the Electronic key when the AMBER LED is ON: in order to change an Area status double click or press
the ENTER key on the corresponding cell.
GREEN spot
marker
This indicates the Areas to be armed (A) and those to be disarmed (D),
among those enabled, on extraction of the Electronic key when the
GREEN LED on the Key reader is ON.
46
Zones
Omnia is provided with 8 input Zones on the Main unit, that can be expanded to 80 by means of Keypads, each equipped with 1 Zone, and by 4
Zone Input expanders, these are available on request.
Omnia Zones (terminals [Zx]) may be programmed as Alarm or Command
Zones.
Alarm Zones
Violation of an Alarm Zone generates an alarm event Alarm on zone no..

It is possible to assign one or more actions to an alarm event (activation of
sirens, digital communicator, telephone dialler etc.).
Before generating an alarm event the Control Panel checks whether the Zone
Area is armed (see "Areas").
If the Zone is not an Entry delay or Last exit zone type (see "Type"), the
Control Panel starts alarm status detection as soon as the Zone Area is
armed, otherwise, the alarm starts when the Exit time for the Areas has
expired (see "Areas").
The alarm status occurs when the Zone is unbalanced (see "Balancing")
for the programmed number of times and timeout (see "Sensitivity").
Each Zone can generate the Zone Alarm event for the programmed number of times only (see "Cycles").
Command Zones
When Command Zones are violated (or activated), they generate one of
the following actions:
Area status commutation;

Area arming only;
Area disarming only;
Area reset;
Control Panel reset;
Clear call queue.
In order to acknowledge a Command Zone as activated, it must be unbalanced (see "Balancing") for the programmed number of times and timeout
(see "Sensitivity").
Zone chart
The left side of the programming page holds a chart which shows the
Zones available, in accordance with the expanders indicated in the {Config.} page. Data must be entered on the right side of the page, which
shows the programming relevant to the Zone selected on the left. The following parameters are indicated, on the left, for each Zone.
no.
This is the Zone ID number, that is used instead of the full description (see
"Description"): for example, when performing a Control Panel status enquiry via telephone.
PROGRAMMING
47
Position
This is the description of the hardware component the Zone is assigned to:
this description may be changed in the {Config.} page and may be used,
for example, to indicate the installation position of a device.
Device
This is the device identifier number (address) of the peripheral the Zone is
assigned to.
It is a number from 1 through 8 for Keypad Zones, and a number from 1
through 16 for Input-Expander Zones. This parameter is not present on MainUnit Zones.
Ter.
These are the initials that identify the Zone on the terminal board of the device the Zone resides on. This parameter is also the sequential number of
the Zone on the device.
Description
This field accepts a maximum of 16 characters, and is for the name which
identifies the Zone. This name will be used as Zone identifier, in all parts of
the program and in the event logger.
Area
This indicates the Area the Zone is assigned to (Zone Area). If the Zone
type is a Command Zone, an asterisk is displayed in this field.
All the programmable parameters, of the Zone selected in the Zone Chart
in the programming page, may be modified in the right side.
These parameters are described as follows.
Figure 23
48
Zone programming page.
Description
This modifiable field accepts a maximum of 16 characters, and is for a
name that will identify a Zone. This name will be used in all parts of the
program as Zone identifier. This description is shown in the left side of the
{Zones} page. The sequential number of the Zone is shown to the left of
the description field, by a number from 1 through 80.
Type
This shows the intervention times of the Alarm Zones, that is, whether they
must signal an alarm condition immediately or with a delay, independent of
the status of the latter.
Immediate
This parameter definition determines, amongst other things, if Zone violation will generate Fire, 24h or Burglar type alarm events, at both Area and
Control Panel level. If the Zone is not defined as Fire or 24h type, it will be
implicitly regarded as Burglar type.
When the Zone is violated, the following events are generated immediately:
Alarm on zone no.;

Burglar alarm on area no., Generic alarm on area no. and Generic+Tamper alarm on area no. on the Zone Area;
Burglar alarm on panel, Generic alarm on panel and Generic+Tamper

alarm on panel.
Entry delay
When the Zone is violated, and the Entry time set for the Zone Area is active, no event is generated; if the Area is not disarmed after timeout, or if
the Zone is violated after this period, the events indicated for the Immediate type are generated.
The first Zone that must be violated on the path to a disarm-point of the
Zone Area, should be of this type.
Entry path
When the Zone is violated after an Entry delay Zone, the events specified
for the Immediate type are generated, after the Entry time has expired.
If the Entry time is not active or has expired, the events shown for the Immediate type are generated.
Zones that must be violated on the path to a disarm-point of the Zone
Area, should be of this type.
Exit delay
If a Zone is violated during the Exit time of the Zone Area, no events are
generated; otherwise, the events specified for the Immediate type are generated.
Zones that must be violated in order to exit the Zone Area, should be of
this type.
PROGRAMMING
49
Last exit zone
If a Zone is violated during the Exit time of the Zone Area, no events are
generated, but this modifies the Exit time in accordance with the setting
for the Last exit time of the Zone Area, otherwise, the events indicated for
the Immediate type are generated.
The last Zone violated on Zone Area exit, should be of this type.
24h
When a Zone is violated, whether the Zone Area is armed or disarmed, the following events are generated:
Alarm on zone no.;

24h alarm on area no., Generic alarm on area no. and Generic+Tamper alarm on area no. on the Zone Area;
24h alarm on panel, Generic alarm on panel and Generic+Tamper

alarm on panel.
Fire
When a Zone is violated, whether the Zone Area is armed or disarmed, the
following events are generated:
Alarm on zone no.;

Fire alarm on area no., Generic alarm on area no. and Generic+Tamper alarm on area no. on the Zone Area;
Fire alarm on panel, Generic alarm on panel and Generic+Tamper

alarm on panel.
Attributes
+
Not Bypassable
Chime
The following parameters affect the Alarm Zones only, and do not affect
the Command Zones.
If this attribute is selected, the Zone cannot be bypassed.
If the Zone Area is disarmed, violation generates the Chime on area no.
event, and there is a beep signal on the enabled Keypads of the Zone
Area. If the Zone Area is armed, it performs as specified in the Type parameter.
The Chime attribute does not affect the 24h or Fire Zones.
Test
The Zone is operative to all effects, but instead of generating the event
Alarm on zone no. it stores the message <<Alarm on Zones being
tested>> in the Control Panel event logger: in this way, it is possible to
check the status of a suspect Zone, without provoking alarm signalling. By
means of the Options window in the Programming menu, it is possible to
select whether the event logger should log events only when the Area is
armed (default), or also when the Area is disarmed.
Autobypassable
If this attribute is selected, the Control Panel can bypass the Zone, when
the Zone results violated during Zone Area arming. The Zone is un-bypassed automatically, on the successive disarming of the Zone Area.
+
50
The Autobypassable attribute does not affect the Exit delay Zone types.
Balancing
This specifies the electrical conditions that must be present on the input
terminal, in order for the Control Panel to acknowledge violation on the corresponding Zone.
The following conditions must be present for at least 300 mS (milliseconds

= 0.3 seconds), in order for them to be recognized by the Control Panel.
Normally open
When normal, the Zone must be open; when it is connected to ground the
Control Panel acknowledges Zone violation (e.g. connections to fire detectors).
Normally closed
When normal, the Zone must be connected to ground; when the Zone is
open the Control Panel acknowledges Zone violation.
Balanced 10K
When normal, the Zone must be connected to ground with a 10K (10,000
ohm) resistance; if short-circuited to ground the Control Panel acknowledges tamper and generates the following events:
Tamper on zone no.;

Tamper alarm on area no. and Generic+Tamper alarm on area no. on
the Zone Area;
Tamper alarm on panel and Generic+Tamper alarm on panel.

In all other cases (unbalanced, open Zones etc.) the Control Panel acknowledges Zone violation (see "Type").
Double balanced
The Zone must be connected to ground with two 10 K (10,000 ohm) resistances; if one of these is disconnected, the Control Panel generates events
according to the Zone Type (see the "Type"); in all other cases (open
Zones, Zones connected to ground, etc.), the Control Panel acknowledges
tamper and generates the events indicated for tamper on the balanced
Zone with 10K.
By means of just 2 wires, this balancing type allows detection of both the
opening of the alarm switch and the tamper switch of the connected sensors (see "Alarm sensor connection").
There is no reason to program Double balancing for a Command Line, as

event recognition Tamper on zone no. does not generate any actions.
PROGRAMMING
51
Cycles
This parameter shows the number of times the Zone being programmed
can signal an alarm condition before being bypassed on the analysis. The
following values are possible.
0
1 254
Violations on the Zone are ignored.

The Zone signals the alarm condition for the set number of times, it is then
bypassed until one of the following conditions, which will clear the alarmcycle counter, occurs:
status change of the Zone Area;

reset of the Zone Area;
quitting of the Stop-Alarm condition for the Zone Area (via Keypad by
means of a Code or via Key reader by means of a Electronic key);
quitting of a programming session (via Keypad or by means of local or remote connection).

Repetitive
The number of times the Zone can signal an alarm condition is unlimited.
Zones with a persistent alarm status (e.g. due to a malfunction) generate
only one alarm cycle. This function mode is explicitly required by CEI 79/2
regulations. They may generate a new cycle only if the alarm counters are
cleared or if the Zones are un-bypassed.
Area
Alarm Zone
This shows the Zone Area of the
Zone being programmed and
therefore, the enabled Codes, Keys
and also function times: each Alarm
Zone should be assigned to one Area
only; it is unnecessary to assign a
Zone to several Areas, as Omnia
manages Area dependency (see
"Areas").
Command Zone
This shows the Areas of the
Command Zone in question: each
Command Zone can operate on
more than one Area.
It is not possible to specify the
Areas for the Panel Reset and
Clear Calls commands, as this
parameter is not influential for this
command.
Sensitivity
52
Standard
This shows the number of times the Zone must be violated (see Pulses)
during the programmed delay time (see Within parameter), before the
Control Panel acknowledges alarm status.
Low
In order for the Control Panel to acknowledge the Zone as in alarm status,
it is necessary that violation is detected for the programmed time (see
Pulse length). Please note the time is programmed in full minutes and the
programmable time ranges from 1 through 16 minutes. Although, for the
Keypad Zones, the time is to be estimated with a margin of about 30 seconds less than that actually set.
Voice messages
This parameter permits the assignment of two of the 14 Voice messages,
that Omnia is able to record, to the Zone being programmed; in this way,
by means of the Omnia inputs, it is possible to check the status of an appliance (e.g. heating system) via telephone.
Standby
+
Alarm
+
Messages...
This message is played when the Zone is in standby status.

If there is no Voice message indicated in the Standby field, the standby
status of the Zone is signalled by a beep.
This message is played when the Zone is violated.
If no Voice message is displayed in the Alarm field, the Alarm status of the
Zone is signalled by two beeps.
This button opens a window, similar to that in figure 28, for the 16-character description of each of the 14 messages that Omnia is able to record:
the changes made in this window may be programmed on the Control
Panel by using the Send button on the Messages window.
Recording, playback and deletion of Voice messages is carried out via the
Control Keypad, and requires installation the OmniaVox kit (Voice board +
Microphone board + loudspeaker), available on request.
PROGRAMMING
53
Outputs
Omnia has 4 outputs on the Main unit, that may be expanded to 36, by
means of up to 8 Output expanders of 4 outputs each, these are available
on request.
All outputs are programmable and may be assigned to the events managed by the Control Panel for the signalling of alarm status, by means of
sirens, flashers etc., outputs may also be used for signalling operating or
malfunction conditions, and also to provide control signals for other devices, and so forth.
The outputs may also be programmed for the remote control of appliances
(e.g. the heating system), via telephone.
All the outputs on the expanders are 150 mA open-collectors, that is, terminals
that can earth a maximum current of 150 mA or result open; each expander
board is equipped with a buzzer that may be connected to output 4 (terminal
[OC4]) with positive or negative logic, according to the position of jumper 64.
The Control Panel is equipped with two 1 A open-collector outputs and two
3 A relays.
Each of these forms a Stand-Alone security output, marked +Nx for control
of the 12 V self-powered siren, a positive output marked +Ax for indoor sirens and 12 V flashers and a free exchange on terminals Cx, NCx e NAx
for the connection of those devices that cannot be directly connected to the
above mentioned terminals (e.g. 24 V indoor and self-powered sirens, 24 V
flashers for fire systems).
Outputs and
Events
The description of the action that each activated output will perform, is to
be defined in the {Outputs} page. Specifications as to when an output is to
be armed (or disarmed), are to be made in the {Event-Actions} page. The
programming definition of an output, as shown, coincides with the action
description. Therefore, when assigning an output action in the {Event-Actions} page, it is necessary to indicate the required output only, as the action the output performs is completely defined by its programming.
Several events may activate the same output. When checking programming, it may be helpful to have a list of all the events that activate a given
output.
The Events button, in the {Outputs} page is for this purpose.
On selecting this button the program shows the list of events that activate
the output selected in the output chart (left side of the programming page).
In this way, there are two distinct ways of displaying the allocation of the
Events and Actions to the outputs:
the {Event-Actions} page shows which outputs are activated for each
event;
the {Outputs} page shows which events activate each output.
54
Output chart
The left side of the page shows the Outputs available, according to the expanders shown in the {Config.} page. It is not possible to enter data in this part
of the page. Data may be entered in the right side of the page where the programming of the Output selected in the left side is shown. The following parameters are displayed, for each Output, on the left side of the page.
no.
This is the ID number to be specified in the {Event-Actions} page, in order

to assign the corresponding output to the required events.
Position
This is the description of the hardware device on which the output is located: this description may be changed in the {Config.} page and may be
used, for example, to indicate the installation position of the expander,
making it easy to locate when necessary.
Device
This is the ID number (address) of the device the output resides on.
Therefore, for Output expander Output, this may be a number from 1 to 8.
This parameter is not available for the Main unit Outputs.
Ter.
Description
Shows the initials that identify the output on the terminal, the output resides on. This parameter is also the sequential number of the output on the
device. The 2 relays on the Main unit are generally identified as RL1 and
RL2.
Shows the description given to the Output.
Type
Shows whether the output is programmed as Bistable (B) or Monostable

(M).
Attrib.
Shows whether the output is programmed as Normally closed (NC) or

Normally open (NO).
Reserv.
Shows whether a Output is Reserved for manual use by the user. The
manual arming of an output is available to the user via the system Keypads (USER MENU, Outs management) or via telephone.
Timing
If the output is programmed as Monostable, this field shows the pulse

time the output emits when activated by an event. If the output is programmed as Bistable this field is empty.
All programmable parameters concerning the output selected in the Output
chart of the programming page, may be modified in the right side of this
page. The following is the description of these parameters.
Description
This is a modifiable field, with a maximum of 16 characters, for the name
assigned to each output, this name is used in all other parts of the program
as the output identifier. This description is immediately transferred into the
left side of the {Outputs} page. The sequential number of the output is indicated to the left of the description field, by a number from 1 through 36,
PROGRAMMING
55
Reserved
Omnia outputs may be used for remote control of electrical appliances
(switch ON - switch OFF), both via Keypad or via telephone.
If this option is selected the output cannot be assigned to Omnia events
and therefore, its status is determined exclusively by the commands given
via Keypad or via telephone.
Monostable programming is not necessary, for outputs programmed in
this way, as the output is armed and disarmed by the user.
(Please see the "Output activation" paragraph and the "TELEPHONE OPERATIONS" chapter in the USER MANUAL).
Type
Bistable
This is activated when at least one of the assigned events occurs; it is reset when all the assigned events end.
Monostable
This is activated, if not already so, each time at least one of the assigned
events occurs; it remains active for the programmed On time, then returns
to standby status for the programmed Off Time, at least.
Attribute
This specifies the normal electrical status of the output being programmed.
Normally open
The open-collector outputs (terminals [OCx]) are open; the Stand-Alone

outputs (terminals [+Nx]) are open; on the positive outputs (terminals
[+Ax]) is the positive (13.8 V); the Common contacts of the free voltage exchange of the output relays (terminals [Cx]) are closed on the corresponding Normally open contacts (terminals [NAx]).
Normally closed
Negative is on the open-collector output (terminals [OCx]); positive

(13.8 V) is on the Stand-Alone outputs (terminals [+Nx]); the positive outputs (terminals [+Ax]) are open; the Common contacts of the free voltage
exchange of the output relays (terminals [Cx]) are closed on the corresponding Normally Closed contacts (terminals [NCx]).
Timing
On time
This is the maximum activation time for the output being programmed.
The On time is relevant only to the Monostable programmed outputs, as
the Bistable output is reset when all the assigned events end.
Each Monostable output may have a different On time:
from 0.0 through 25.4 seconds, with steps of 0.2 seconds, if the Sec. option is selected;
from 1 through 128 minutes with steps of 1 minute, if the Min. option is selected.
The default On time for each Monostable output is 3 minutes.
56
Off Time
This is the minimum time that must elapse before the output may be activated again.
There is only one Off Time for all Monostable outputs, which is irrelevant
for Bistable outputs.
It is possible to set an Off Time of 0.0 through 127.5 seconds, with steps
of 0.5 second (default = 6.0 seconds).
Figure 24
Output programming page.
PROGRAMMING
57
Areas
An Area is a group of Zones that Omnia manages separately (Virtual Control Panel). It is possible to define control codes, timers, output actions and
other parameters, for each Area; these may be different to those defined
for other Areas that, however, may interact with one another.
Omnia can manage up to 8 Areas, the composition of which is defined in
the {Zones} page.
Each Area may be made up of many input Zones, however, each Zone
may be assigned to one Area only.
the Area parameters, described in the following paragraphs, are to be defined in this page.
no.
This is the non-modifiable Area ID number, to be used when it is not possible to use the Area description (see following paragraph): e.g. status enquiry via telephone.
Description
This is a modifiable field, with a maximum of 16 characters, for the assigned name of an Area, this name will be used in all other parts of the
program and in the event logger, and will allow clear identification of the
Area.
Entry time
This determines the timeout delay that is generated by Zone violation of a

Entry delay-Zone Type. The Entry time is signalled by:
the event activation Entry time on area no. relevant to the violated Area;
an acoustic signal on every enabled Keypad relevant to the violated Area.
If the Area is disarmed before the timeout expires, no alarm occurs.
Exit time
It is possible to violate an armed Exit delay Zone, during the programmed

delay, without generating an alarm. The Exit time is signalled by:
the event activation Exit time on area no. relevant to the armed Area;
an acoustic signal on the enabled Keypads on the armed Area.
+
Last exit time
Depends on
The Exit time becomes the Last exit time (see following paragraph) as
soon as a Last exit zone Type is violated.
When the Area is armed and the Exit time is active, the violation of a Zone
programmed as Last exit, modifies the Exit time according to the set
value for the Last exit time of the assigned Area. The Exit time set in this
way, continues to be signalled as stated in the previous paragraph.
This shows the dependent Areas of the Area being programmed:
a Dependent Area is armed automatically, as soon as all the Areas it depends on are armed;
a Dependent Area is disarmed automatically, as soon as one of the Areas

it depends on is disarmed.
58
The Dependent Area can always be armed/disarmed manually, by means

of enabled Codes or Electronic keys.
In order to program dependent Areas, just select the Area row, and enter
Yes in the columns that the selected Area must depend on. To activate or
clear the dependence (the word Yes) press ENTER (or "double click") on
the cells.
Figure 25
There is no reason to program an Area as depending on itself.
Area programming page.
PROGRAMMING
59
Telephone
This page is the directory of the 32 telephone numbers that Omnia can
manage, and also holds a series of data relevant to the telephone line utilized.
no.
This is the ID number used when programming via Keypad, and in other
parts of the program to indicate the required telephone number.
Number
Telephone numbers in this field may be called by the Control Panel Pulse
communicator, the telephone Dialler, the DTMF communicator and can
also be used for teleservice requests: digits from 0 through 9 and the
comma (,) may be used. The comma is for pauses (for example, between
a telephone number and area code); the maximum number of digits and
pauses is 16.
Description
It is possible to enter a telephone number description, with a maximum of

16 characters, this is useful for user identification.
Used by
In this column, the program logs telephone number usage, according to

the programming set in the other pages. It shows whether a number has
been used by the telephone Dialler (column Dial.), by the Pulse communicator (column Pulse), by the DTMF communicator (column DTMF) or by
the Teleservice (column Tel.).
Figure 26
60
Telephone-parameter programming page.
Answer
The parameters described in this window define the way in which Omnia
must answer the incoming calls on the number it is connected to.
Omnia will only answer calls if an answer-message has been programmed

(see "Answering machine"), and an authorized user has selected either the
En./Dis. Answer. or En./Dis.Teleser. option in the USER MENU.
In these cases the Control Panel answers the call after the programmed
Rings unless the option Jump other answering devices is set.
Enable answer
This option is not available for the programming of Omnia 2.0 and successive
revisions, as the enable/disable answer function is reserved for the user, by
means of the command En./Dis. Answer and En./Dis.Teleser. on
the USER MENU.
Jump other
answering
devices
This option allows Omnia to share the telephone line with another answering device (answer-machine, fax, etc.). The line is always picked up by the
device with the least number of rings. If this option is selected, Omnia answers on the first ring, that is, if other rings have been detected in the previous minute.
+
+
Rings
The other answering-device must be programmed to answer after 3 or

more rings.
The Jump other answering devices is controlled by the OmniaMOD modem. When remote-control operations via telephone are required, it is necessary to let the telephone ring twice and then hang up, and recall the
Control Panel before 1 (one) minute expires.
This defines the number of rings allowed before the Control Panel answers
the call.
If the Jump other answering devices option is set, this parameter is ignored.
Dial
Disable tones
check
Usually Omnia checks for the dialling tone before dialling a telephone number. If this is not detected, the Control Panel disengages the line and repeats the operation.
By selecting the Disable tones check option, the Control Panel dials the
telephone numbers without checking for the dialling tone: this option is
useful, for example, when Omnia is connected downstream to a switchboard with non-standard tones.
Pulse dial
Usually Omnia calls the programmed telephone numbers by means of tone

dialling, which is faster than pulse dialling. If tone dialling is not provided by
the telephone line connected to the Control Panel, the Pulse dial option
must be enabled.
PROGRAMMING
61
Description tones
By means of this menu, it is possible to select a series of parameters characterizing the national line. Select the name of the country, e.g. "EUROPEAN GENERIC".
Answering machine
Omnia is equipped with the Answering-machine function, which permits
the recording of a Voice message that is played by the Control Panel each
time it receives a call on the connected telephone line, that is, if no other
device answers within the programmed number of rings.
The answer device must be enabled by the user, by means of the repective command in the USER MENU (See "Answering-machine Enable/Disable" in the USER MANUAL).
If, together with the answering-machine, the teleservice function is enabled
by the user, the Control Panel checks if the call is coming from the OmniaMod. This check lasts about 4 seconds, after which, if the call is not
from OmniaMod the answer message starts. The Control Panel signals the
call has been answered, by emitting an acoustic signal when the line is
taken. A high-pitched tone (2400 Hz) indicates that teleservice is enabled,
and a low-pitched tone (1250 Hz) indicates that only the answering-machine is enabled.
The programming of an answer-message gives the authorized user, (see
"User codes"), the possibility to call the Control Panel from a remote telephone and perform several checks on the Control Panel and the connected devices (see the "TELEPHONE OPERATIONS" chapter in the
"USER MANUAL").
In order to set the Omnia answering-machine parameter, it is necessary to
select the Answering machine button, which opens a window containing
the following parameters.
Answer message
+
Message
repetition time
Select the Answer Message from those available. The descriptions that
may be selected are programmable in the Message window in the {Zones}
page or in the {Dialler} page.
If no Answer Message is selected, the Answer machine is disabled and
checks via telephone cannot be performed.
This indicates the time in seconds for Answer-message repetition.
Pause between
repetition
This indicates the time in seconds between each Answer-message repetition.
PIN timeout
This indicates the time (seconds) within which, the user must enter the exact code on the telephone keypad, in order to obtain access to the remote
control functions, before Omnia ends the call.
62
+
DTMF tone
timeout
There are 7 User codes that may be used via telephone on the Control
Panel. These codes are those with a sequential number from 25 through
31 (see {Codes} page).
After User code recognition, if no telephone key is pressed within the time
(seconds) specified in this field, Omnia ends the call automatically.
Dialler
32 actions can be defined for the Omnia Dialler, these can be seen in the
{Event-Actions} page. These actions are used for signalling the start/end of
an event, by means of a Voice message via telephone.
Each telephone dialler action consists of sending one of the 14 Voice Messages, to a maximum of 16 telephone numbers from the 32 programmable
numbers available.
The following parameters must be defined in order to have use of the Dialler.
no.
Used in the Actions window to indicate the corresponding telephone number. This parameter ranges from 1 through 16.
Tel. Num.
This column is for the ID numbers of the telephone numbers (see {Telephone} page) to which Voice messages are to be sent: the description of
the number that has been dialled, is displayed in the Description column.
It is possible to choose up to 16 of the 32 numbers, definable in the {Telephone} page.
+
+
These numbers need not follow the order defined in the {Telephone} page,
however, the order defined here establishes the dialling priority of the telephone numbers assigned to the same telephone-dialler action .
The contents of the Description column can be modified in the {Telephone} page only.
Repetition time
This indicates the time in seconds for the Voice-message repetition: it is

possible to program a different Repetition time for each telephone number.
Pauses between
repetition
This indicates the time in seconds, between each Voice-message repetition.
PROGRAMMING
63
Voice timeout
This indicates the time (seconds) that Omnia waits for an answer before
disengaging the dialled number. This parameter assumes a different
meanings according to the choice made for Send message after as follows.
Voice on line: the parameter description coincides with its meaning; the
Control Panel waits for a voice answer within the set after-dialling-time,
then will disengage.
First ring: the Control Panel waits for the first back-ring, within the set after-dialling-time, then will disengage.
Dial: the parameter is irrelevant in this case.

Attempts
If a telephone call fails, Omnia continues with dialling attempts for, at least,
the number of times specified by this parameter.
Recall on
success
If selected, this shows that the successfully called numbers must be recalled in the following cycles. If not, the numbers that have answered are
excluded in the following cycles.
The parameters for Pause between messages repetition, Voice
timeout, Attempts and the Recall on success option are the same for all
Telephone numbers.
Figure 27
64
Telephone-dialler programming page.
Send message
after
This specifies when the recorded message must be sent:

Voice on line: the message is played on call answer (e.g. on answering
"Hello");
First ring: the message is played after Omnia has acknowledged the first
ring (back ring);
Dial: the message is played after Omnia has dialled the telephone number
required.
Omnia acknowledges the telephone call as successful when the selected

condition occurs, in the first case the call has been undoubtedly answered,
in the second and third cases the call may or may not have been answered, therefore, the Recall on success option is recommended.
Messages
This button opens a window similar to that shown in Figure 28. In this window it is possible to assign a description (maximum 16 characters), to the
14 messages that Omnia can record: the changes made in this window
can be programmed on the Control Panel by means of the Send button on
the Message window.
Figure 28
Voice message recording, playback and deletion can be carried out via
control Keypad and require the OmniaVox kit (Voice board + Microphone
board + loudspeaker) that is supplied on request. See the "OmniaVOX"
chapter for a full description of the Voice functions.
Voice-message description window.
PROGRAMMING
65
Actions
In this window it is possible to define the Dialler actions to be assigned to
events in the {Event-actions} page.
A Dialler action consists of calling of a list of telephone numbers and sending a Voice message to each. All Dialler actions can be repeated for as
many times as set in the Attempts parameter
no.
This is the identifier number of the dialler action. Refer to this number in
the {Event-Actions} page, in order to assign the selected event to the required dialler action.
1 ... 16
This is the telephone numbers that must be called, among those shown in
the Number to be called list: an empty cell indicates that the corresponding number will not be called; to select the numbers to be called double
click or press the ENTER key on the corresponding cell.
Message
This shows the Voice message that must be sent by the Dialler Action that
is being programmed: by entering a number from 1 through 14 in the Message column, the name assigned to the Voice message appears in the
Descr. Mess. column.
The Voice message description can be modified in the Messages window

only.
Descr. Action
In this column it is possible to assign a description to the action in order to simplify programming in the {Event-Actions} page.
Events
After a Dialler Action has been defined, it must be assigned to one or more
events in the {Event-Actions} page. This specifies when the action is to be
performed by the Omnia Dialler.
It is possible that several Events enable the same Telephone Dialler action. When checking programming, it may be useful to have a list of all the
events which generate a particular Dialler action.
The Events button in the Dialler actions window of the {Dialler} page, is
for this purpose. When the Events button is selected, the program shows
the list of events that enable the selected action. In this way, there are two
different ways of displaying the allocation of Events and Actions on the Dialler:
the {Event-Actions} page displays which dialler action is generated by each

event;
the Dialler actions window of the {Dialler} page displays which events activate the selected Dialler action.
66
Pulse communicator
The Omnia Pulse Communicator permits the definition of 256 actions that
can specified in the {Event-Actions} page, in order to signal the start or end
of an event to the Central Stations that supervise this type of communication.
Each Pulse Communicator action consists of sending a code, that identifies the event, to of a maximum of 4 telephone numbers: in this way, it is
possible to send burglar alarm warnings to the Central Station, fire alarms
to the Fire Station, teleassistance requests to the Service Centre and the
trouble alarms to the Installer.
As each event may be assigned to 2 Pulse Communicator actions, it is
possible to indicate 2 different codes, in this way, the same event may be
sent to two separate Security Services, each decoding in their own way (as
in the case of a malfunction warning, that involves both the installer and
the Central Station).
Before ending a communication, the DTMF communicator checks if any

other events must be sent to the telephone number on line, if so, these will
be sent before ending the communication.
In order to have use of the Pulse Communicator, it is necessary to program the following parameters.
Numbers to dial
Figure 29
This list is for the telephone numbers that the Pulse Communicator can
call, these numbers are selected from those programmed in the {Telephone} page.
Pulse-communicator programming page.
PROGRAMMING
67
Customer code
In this field a 3 or 4-digit code must be entered (digits 0 through 9 and

block letters from B to F may be used), this code is generally given to the
customer telephone number by the agency, and is the identifier code of the
system calling (owner, address, etc.).
Protocol
It is necessary to indicate, for each telephone number, the supported protocol of the device connected via telephone. Omnia supports the following
communication protocols in the 3/1, 3/2, 4/1 and 4/2 formats or, with 3 or 4digit Customer Code and 1 or 2-digit Event Code:
ADEMCO / SILENT KNIGHT - Slow 10 baud;

ADEMCO / SILENT KNIGHT - Fast 20 baud;
FRANKLIN / SESCOA / DCI / VERTEX - Fast 20 baud;
RADIONICS - 40 baud;
SCANTRONIC - 10 baud.
Each protocol listed above is available with the Voice Option. The OmniaMOD/V3 modem permits two-way voice sessions and environmental listen-in, both are extremely useful when verifying "Help" requests.
Attempts
If a call ends in an irregular way, Omnia will call the number for as many
times as set in this parameter.
Actions
The Actions of the Pulse Communicator are defined in this window. These
are then assigned to specified events in the {Event-Actions} page. Each
Pulse communicator action is made up of two distinct sub-actions, each of
which consists of sending, to each of the 4 numbers previously programmed, a specific event code using the customer code and the defined
protocol for that number.
no.
68
This is the number to refer to in the {Event-Actions} page.
Event code
This is a 1 or 2-character code (digits 0 through 9 and block letters from B

to F), generally assigned by the connected Central Station Agency, and
which allows the agency to recognize the event that generated the call.
1234
This indicates the phone numbers that must be called, among those listed
under Numbers to dial: an empty cell indicates that the corresponding
number will not be called; to select the required numbers double click or
press the ENTER key on the corresponding cell.
All
Yes specifies that all programmed numbers must be called until they all
answer, otherwise, the calls will be interrupted as soon as one of them is
acknowledged as successful.
Description
In this field a description of the Pulse Communicator action can be entered

(maximum 16 characters).
Events
After a Pulse communicator action has been defined, it is assigned to one

or more events in the {Event-Actions} page. This specifies when the action
is to be performed by the Omnia Pulse communicator.
Several Events can enable the same Pulse communicator action. When
checking programming, a list of all the events that enable a certain dialler
action is recommended.
The Events button in the Pulse communicator actions window of the
{Pulse Comm.} page, is for this purpose. When clicking on this button the
program shows the list of events that activate the selected action. In this
way the allocation of Events and Actions on the Pulse communicator can
be displayed into two different ways:
the {Event-Actions} page shows which Pulse communicator action is activated by each event;
the Pulse communicator actions window of the {Pulse comm.} page

shows which Events activate each Pulse communicator action.
Teleservice
By means of the OmniaMOD/V1 or OmniaMOD/V2 modem and this program, the installer may carry out teleservice on the Omnia Control Panels,
which means, the installer can solve problems or modify parameters via
telephone.
The teleservice call can be made automatically, from the Test event (if enabled) or by the installer, with user authorization.
When the teleservice call comes from the Control Panel (manually, on user
request, or automatically by means of Enable security call or Enable
Test call), it calls the enabled numbers (see Enable), selected from those
in the Numbers to dial list, until a call is successful or the programmed
Attempts number expires.
Enable security
recall
On selecting this option, when Omnia receives a teleservice call, it calls

the enabled numbers (see Enable), selected from those shown in the
Numbers to dial list: this assures that teleservice is performed by authorized personnel only.
Enable Test call
On selecting this option, the teleservice call is performed automatically and

periodically by the Control Panel, according to the programming in the
{Test event} page.
The test Event must be enabled (see {Test event} page), in order to perform the Test call.
Enable
Indicates the numbers to be called, selected from those in the Numbers to

dial list.
Numbers to dial
It is possible to specify up to 4 numbers for teleservice calls, these can be

selected from the 32 programmed in the {Telephone} page: by entering a
number from 1 through 32 in the left cell, the telephone number description
is shown in the right cell.
PROGRAMMING
69
Customer code
This is a 4-digit code that permits the univocal identification of the Control
Panel requesting teleservice (personal data, programmed parameters, etc.).
Each Control Panel must have a different Customer code, otherwise, when
saving changes the program indicates that the programmed code already exists and also shows the Control Panel the code is assigned to .
+
Attempts
Figure 30
70
The Customer code in this page is the same as the code in the {Customer} page, therefore, any modification in this code will affect the {Customer} page and vice versa.
If a telephone call ends in an irregular manner, Omnia calls the number for
as many times as set in this parameter.
Teleservice programming page.
Event-Actions
This page is the core of the Omnia System, as it establishes which actions
activate the events that the Control panel can recognize; therefore, it controls system functioning.
Actions are:
Activation of an Output;
Pulse communicator activation;
telephone Dialler activation.
The page holds a chart indicating the events that Omnia recognizes, according to the detail level selected on the right of the page. The columns
contain the following information.
no.
The ID number of each event. This is the number that must be indicated in
the {DTMF Comm.} page, in order to assign a Communicator DTMF channel to the corresponding event.
Description
The events Omnia recognizes. The number varies according to the detail
level selected in the right side of the page.
Read the "Events description" paragraph for the event description.
Outputs
Figure 31
The ID number of the output to be enabled (see {Outputs} page) when the corresponding event occurs.
Event-Actions assignment programming page.
PROGRAMMING
71
Pulse Comm.
The ON column is for the ID numbers of the actions the Pulse communicator must perform (see {Pulse comm.}) when the corresponding event
starts.
The OFF column is for the ID numbers of the actions the Pulse communicator must perform (see {Pulse comm.}) when the corresponding event
ends.
Dialler
The ON column is for the ID numbers of the actions the Dialler must perform (see {Dialler} page) when the corresponding event starts.
The OFF column is for the ID numbers of the actions the Dialler must perform (see {Dialler} page) when the corresponding event ends.
Telephone
actions priority
Action no.1 on the telephone Dialler and action no.1A of the DTMF communicator have priority over all other telephone actions, therefore, they
suspend all other telephone actions.
These two actions have the same priority level and, if one of them occurs
whilst the other is active, the active action will not be suspended. If the
Control Panel is performing either action no.1 or no.1A, and the same action is requested, it will be queued as if it had no priority whatsoever.
To simplify programming of the {Event-Actions} page, use the right side of
this page, where, for the selected event, 5 menus are shown that define:
the action on the Output;

the action on the Pulse communicator when the action starts;
the action on the Pulse communicator when the action ends;
the action on the Dialler when the action starts;
the action on the Dialler when the action ends.
Using these menus the actions can be selected with the help of their description thus avoiding errors.
+
+
The event-action assignment for the DTMF communicator is performed in

the {DTMF Comm.} page.
It is possible to select the detail level of the displayed events, on the right
side of this page.
Normally only the general events of the Control Panel are shown without
details. When the detail levels are selected, the *Global* events are exploded according to the chosen detail level.
Area detail
Displays all the events relevant to the Areas (alarms, arming, etc.). If this
option is not selected the *Global* events are displayed.
Zone detail
Displays all the events relevant to the system Zones (Alarms, Tamper, Bypass etc.). If this option is not selected the *Global* events are displayed.
Warning detail
Displays the events relative to the troubles Omnia is able to recognize. If

this option is not selected event no. 229 Warning generic is displayed,
which represents all the troubles that the Control Panel recognizes.
72
Code Detail
Displays every event relative to code recognition on the Keypads. If this

option is not selected, only the Global event no. 437 Recognized code
*Global* is displayed.
Super key detail
Displays the events relative to Super keys (press the key for 2 sec.). If this option is not selected, only the no. 397 Super keys *Global* event is displayed.
It is not possible to assign any action to *Global* events, as this type of

event is inexistent. *Global* is the name given to those events which are
not displayed for the selected detail level.
The Global events show two possible situations, in the cells that specify
actions to be carried out, indicated by two strings None and Act.Pres..
For each of the possible type of actions,
- on outputs (Outputs > ON),
- on the Pulse communicator when the event starts (Pulse Comm. > ON),
- on the Pulse communicator when the event ends (Pulse Comm. > OFF),
- on the Dialler when the event starts (Dialler > ON),
- on the Dialler when the event ends (Dialler > OFF),
one of the two strings will be displayed. The meaning of the strings is as
follows.
None: indicates that no event among those grouped by the Global event
has an assigned action of that type. Therefore, if None is on the output column, in correspondence to the Alarm on zone *Global* event, it means
that no Alarm on zone no. event activates an output.
Act.Pres: (Actions Present) one or more events among those grouped by

the Global event has an assigned action of that type. This indicates that
one or more events grouped under Global event is assigned to an action of
that type. Therefore, if for example, the string Act.Pres is present in the
Outputs column, in correspondence to the Alarm on zone *Global*
event, this means that one or more Alarm on zone no. events activate an
output.
Event description
The following paragraphs describe the conditions that generate each event
and those that bring it to an end. Please note that an event does not always end when the cause ceases, as is explained separately for each
group of events.
PROGRAMMING
73
Alarm events
Alarm events are generated by any alarm cause at Zone, Area, or Control
Panel level.
The main events in this category are the Zone events, assigned to the
alarm and tamper of each single Zone.
From these events, the Area events and the Control Panel events are built
up using OR logic.
All alarm events end when the cause ceases, unless they are assigned
to monostable outputs.
If events are assigned to monostable outputs, they end after the programmed On time for the assigned output, even if the cause of activation
has ceased. These events are not generated during the output Off Time,
or when the monostable output they are assigned to is active.
For example, if an alarm event is assigned to an output for a siren programmed as monostable with a 3-minute On time, the siren will carry out
the 3-minute cycle, even if the cause of the alarm has ceased. However, if
disarmed, the alarm event will be forced into standby status.
In the following chart the column IT STOPS WHEN... is valid if the events
are not assigned to monostable outputs.
Zone events
EVENT
1
:
80
81
:
160
OCCURS WHEN ...
Alarm on
... Zone no. is in alarm status*
zone no.
Tamper on
... Zone no. is tampered*
zone no.
ENDS WHEN ...

... Zone no. returns to standby
status.
... tamper on Zone no. ends.
* The conditions causing the Zone alarm and tamper are described in
the {Zones} page.
These events can be forced into standby status in the following ways:
changing the status (Arm / Disarm) of the Area the Zone no. is assigned to;
resetting the Area the Zone no. is assigned to;
inserting an enabled valid Electronic key into a Key reader enabled on the
Area the Zone no. is assigned to.
using the Alarm stop command on an enabled Keypad on the Zone no.
and with an enabled User code on the Zone no.
74
Area events
EVENT
These are the sum of the events of the Zone concerned, therefore, they
occur when one of the events that group them occurs and end only when
all the events that group them cease.
OCCURS WHEN ...
161
Fire alarm
:
on area no.
168
169
24h alarm on
:
area no.
176
ENDS WHEN ...

... all events generated by the Fire
... a Fire Zone assigned to Area no.
Zones assigned to Area no. return
is in alarm status
to standby status.
... all events generated by the 24h
... a 24h Zone assigned to Area no.
Zone assigned to Area no. return to
is in alarm status.
standby status.
... a burglar Zone (Immediate, En... all events generated by the
try delay, Entry path, Exit delay
burglar Zones assigned to Area no.
or Last exit zone) assigned to Area
return to standby status
no. is in alarm status.
... all Alarm events generated by
... a Zone is in alarm status (any
the Zones assigned to Area no.
Type) assigned to Area no.
return to standby status.
... all Tamper events generated by
... a Zone assigned to Area no. is
the Zones assigned to Area no.
tampered.
177
:
184
Burglar
alarm on
area no.
185
:
192
193
:
200
Generic
alarm on
area no.
Tamper
alarm on
area no.
Generic+
... all events (Alarm and Tamper)
Tamper ... a Zone assigned to Area no. is in
generated by the Zones assigned
alarm on alarm or tamper status
to Area no. return to standby status.
area no.
201
:
208
changing Area no. status;

resetting Area no.;
by using an enabled valid Electronic key on Area no., into a Key reader enabled on Area no.;
using the command Alarm Stop from an enabled Keypad on Area no.
and a User code enabled on Area no.
Control panel
events
EVENT
209
Fire alarm
on panel
210
24h alarm on
panel
These are the grouped events of the Zone concerned, and occur when one
of the grouped events occurs and end when all the grouped events end.
ENDS WHEN ...
... all events generated by the Fire
... a Fire Zone assigned to any
Zones of all Areas return to standby
Area is in alarm status.
status
... all events generated by the 24h
... a 24h Zone assigned to any Area
is in alarm status.
status.
PROGRAMMING
OCCURS WHEN ...
75
EVENT
211
212
213
214
215
216
217
218
OCCURS WHEN ...

ENDS WHEN ...
... a burglar Zone (Immediate, EnBurglar
... all events generated by burglar
try delay, Entry path, Exit delay
alarm on
or Last exit zone) assigned to any
panel
status.
Area is in alarm status
Generic
... all Alarm events generated by
... any Zone assigned to any Area
alarm on
the Zones of all Areas return to
is in alarm status.
panel
standby status.
Tamper
... all Tamper events generated by
alarm on
the Zones of all Areas return to
is tampered.
panel
standby status.
Generic+
... all events (Alarm and Tamper)
Tamper alarm
generated by the Zones of all Areas
is in alarm status or tampered.
on panel
Tamper on ... the tamper switch (2) or pull-off .. the tamper and pull-off switches
Main unit switch (15) in the Main unit is open.
are closed.
... terminal 26[ASB] is balanced
Balanced
... terminal 26[ASB] is unbalanced. (connected to ground with a 10,000
tamper
ohm-resistor).
... a tamper switch or a pull-off
Tamper on switch of a device connected to the ... all tamper and pull-off switches
BPI device BPI bus is open (Keypads, Input or of the BPI devices are closed.
Output Expanders, etc.).
False key on ... A false Electronic key is inserted ... false Electronic key is no longer
key reader into a Key reader.
detected.
with the Alarm reset command from any Keypad with any enabled User
code to Panel reset;
with the Alarm Stop command from any Keypad with any enabled User
code to Panel reset.
By inserting a valid Electronic key in any Key reader, if the Enable alarm
stop on panel with valid key option has been programmed.
Control-panel General events
These events are generated by the Control Panel. They are not alarms
with a start and end condition (e.g. "No Mains").
If these events are assigned to a monostable output they perform as
follows:
if the cause that generated the event is still present after the On time of
the output, the latter returns to standby status whereas, the event ends
when the cause ceases;
if the cause that generates the event ends before the On time of the
Monostable output has expired, the output returns to standby status and
the event ends.
76
If these events are not assigned to a Monostable output, they end

when the conditions in the following chart occur.
219
220
221
222
EVENT
Warning
fuse +F
Warning
fuse +B
Warning
fuse BPI1
Warning
fuse BPI2
OCCURS WHEN ...
ENDS WHEN ...
... Fuse 18 burnt.
... fuse 18 is replaced.
... Fuse 19 burnt.
... Fuse 16 burnt.
... Fuse 17 burnt.
... Fuse 17 is replaced.
... after mains power failure for the

Warning
223
programmed time (see Filter times
mains failure
in the Programming menu).
... mains power failure and
Warning low
224
insufficient battery power for
battery
Control Panel functioning.
... the battery supply is insufficient
Warning for Control Panel functioning
225
power trouble (calculated with mains present
only).
... after the power supply of one of
Warning
the Power stations connected to
mains failure
226
the BPI bus fails for the
on Power
programmed time (see Filter times
station
in the Programming menu).
... mains power supply failure on one
Warning low
of the Power stations connected to
battery on
227
the BPI and the battery charge
Power
cannot guarantee proper functioning
station
of the connected devices.
Warning ... the battery of one of the Power
power stations connected to the BPI
228
trouble on bus cannot supply sufficient power
Power to guarantee proper functioning of
station the connected devices.
Warning ... one of the previously described
229
generic troubles starts.
... the Main unit does not detect a
Trouble on
230
device on the BPI bus, because of
BPI
trouble or wire cutting, for example.
231
Area no.
:
... Area no. is armed.
armed
238
PROGRAMMING
... the mains power supply is

restored.
... the battery charge is above the
safety limit.
... the battery or the protection fuse
27 is replaced.
... the mains power supply is

restored on all the Power stations
connected to the BPI bus.
... the battery charge of the Power

station is above the safety level.
... the battery (or the protecting

fuse) is replaced.
... all previously described trouble
ends.
... the Main unit detects all the
programmed devices for the
configuration on the BPI bus.
... Area no. is disarmed.
77
EVENT
239
:
246
247
:
254
255
:
262
Exit time on
area no.
Entry time
on area no.
Valid key on
area no.
263
Valid key on
panel
264
:
271
Alarm stop
on area no.
272
Alarm stop
on panel
OCCURS WHEN ...
ENDS WHEN ...

... after the programmed Exit time
for Area no., unless in the
meantime a Last exit zone is
... Area no. is armed.
violated, in which case it ends after
the programmed Last z.tim. for
Area no.
... after the programmed Entry time
... a Entry delay Zone assigned to
for Area no. or after Area no. is
the armed Area no. is violated.
disarmed.
... a valid Electonic key, assigned to
... the Electronic key is extracted
Area no., is inserted into a Key
from the Key reader.
reader assigned to same Area.
... a valid Electronic key is used on ... there are no valid Electronic keys
any Key reader.
on Key readers.
... the Alarm stop is requested
using an enabled User code and ... alarms are no longer blocked.
from an enabled Keypad on Area no.
... The Alarm stop is requested
using an enabled User code for this ... alarms are no longer blocked.
function.
273
Bypass zone
:
... Zone no. is bypassed.
no.
352
... there is alarm status on at least
353
one Zone that is not delayed, last
Not ready to
:
exit, bypassed or command type.
arm area no.
360
The calculation occurs every 2
seconds.
... the voltage on the telephone line
Telephone
361
is less than 3 V for at least 45
line trouble
seconds.
362
... the timeout-to-arm for automatic
Timeout-to-arm
:
arming of Area no., generated by
area no.
369
OmniaTIMER, starts.
370
371
372
:
379
78
... it is not possible to use the

Error serial
printer connected to the serial port
printer
on the OmniaTIMER.
... it is not possible to use the
Error parallel
printer connected to the parallel
printer
port on the OmniaTIMER.
The Timer no. managed by the
Timer no. OmniaTIMER reaches the hour set
for On.
... Zone no. is unbypassed.
... the alarm status ends on all the

Zones
not delayed, last exit,
bypassed or command type.
... the required voltage on the
telephone line (over 3 V) is restored
for at least 15 seconds.
... the timeout-to-arm for the
automatic arming of Area no.,
generated by OmniaTIMER, ends.
The Area is armed.
... it is possible to use the printer
connected to the serial port on the
OmniaTIMER.
... it is possible to use the printer
connected to the parallel port on
the OmniaTIMER.
The Timer no. managed by the
OmniaTIMER reaches the hour set
for Off .
Spot events
The following events are called spot events because they stop immediately after they have occurred (e.g. after a code recognition) and therefore
require no actions, although:
they cannot be assigned to bistable outputs;

they cannot be assigned to reset actions of the Dialler and the Pulse communicator;
they cannot be assigned to channels of the DTMF communicator.

EVENT
380
Test
381
:
388
Reset on
area no.
389
Reset on
panel
390
Super key
:
no.
399
400
Chime on
:
area no.
407
408
Recognized
:
user code no.
438
OCCURS WHEN ...

ENDS WHEN ...
... programmed in the {Test event}
NOT ALLOWED!
page.
... The Alarm reset is requested
with an enabled User code on Area
NOT ALLOWED!
no. and from an enabled Keypad on
Area no.
... Alarm reset is requested with
a User code enabled for this NOT ALLOWED!
function.
... key no. is pressed for more than
NOT ALLOWED!
3 seconds.
... violation on a Chime Zone
assigned to Area no., which is NOT ALLOWED!
disarmed.
... the PIN of the User code no. is
NOT ALLOWED!
entered.
... the installer PIN is entered. This

Recognized event NEVER causes actions as
439
Installer code access to the Installer menu stops
any current actions.
Teleservice
.. a teleservice call coming from
440 request from
OmniaMOD is answered.
OmniaMod
... the teleservice connection is
Teleservice
441
activated after recognition of the
ON
PIN of the installer.
Teleservice ... a test call or a teleservice action
442
action failed requested by the user fails.
DTMF
...
an action of the DTMF
443 Communicator
communicator fails.
action failed
Dialler ... an action on the telephone dialler
444
action failed fails.
PROGRAMMING
NOT ALLOWED!
NOT ALLOWED!
NOT ALLOWED!
NOT ALLOWED!
NOT ALLOWED!
NOT ALLOWED!
79
EVENT
OCCURS WHEN ...
Pulse
... an action of
445 Communicator
communicator fails.
action failed
Figure 32
80
the
ENDS WHEN ...

Pulse
NOT ALLOWED!
Page for DTMF Communicator programming.
DTMF communicator
By means of the Omnia DTMF communicator 8 events, plus 1 event from
those controlled by the Control Panel, can be communicated to a Central
Station supporting this type of protocol.
When a programmed event changes status, Omnia calls the enabled numbers (see Enable) in the Numbers to dial list, and sends the assigned
Customer code, for each number. In this way, it is possible to identify the
Control Panel calling, and check the status of the 9 communicator channels.
General enable
This option enables or disables the DTMF communicator.
Enable
This specifies the numbers to be called among those in the Numbers to

dial list.
Numbers to dial
Selects the number the Omnia DTMF communicator must call, from the 32
programmed numbers in the {Telephone} page: when a number from 1
through 32 is entered in the left cell, the telephone number description is
displayed in the right cell.
Customer code
It is possible to program a different Customer code for each telephone

number, this code is usually assigned by the Central Station: only 4-digit
numbers are allowed.
Protocol
It is possible to specify the protocol for data sending for each telephone
number, from the following list:
ADEMCO MF;
SCANTRONIC MF.
Channel
definition
In the position indicated by the connected Central Station agencies, enter

the ID number of the event to be supervised.
Polarity change
It is possible to set logic reversal for all channels, except the Aux channel:
in this way, the alarm code is transmitted when the event ends and the reset code is transmitted when the event assigned to the channel in use occurs.
Attempts
This is the maximum number of call attempts that Omnia will make to the
numbers, that result as failed communications.
Recall on
success
Usually the DTMF communicator stops the calls as soon as one is successful.
If this option is selected, every enabled number will be called until each is
successful or they are called as many times as shown in Attempts.
PROGRAMMING
81
Test event
The Test event (380) is performed on regular basis, according to the following parameters and, as for all Omnia-controlled events, it can be assigned to actions in the {Event-Actions} page.
Enable
Select this option for the Test event.
Hour and minute

test event
Specifies the programmed hour of the Test event (see Clock in the Programming menu): a number from 0 through 23 must be entered in the hh
field, for the hour, zero signifies midnight and, a value from 0 through 59
must be entered in the mm field, for the minutes.
First Test delay
Specifies the number of times Omnia ignores the programmed hour before
generating the Test event. Therefore, it specifies the number of days that
must pass, from the moment the Initialize button is selected, before the first
Test event occurs at the scheduled time.
Repeat Test
event
Specifies how often the Test event must be performed.
Initialize
The above-described parameters, when sent to the connected Control

Panel (see Send > Page in the Programming menu), become operative
only when the Initialize button is selected.
Each time a new setting for the Test event is sent to the Control Panel, it
becomes operative only when the Initialize button is selected.
When the Initialize button is selected the Control Panel must be connected (via RS232 or telephone) to the PC, otherwise, the program displays an error message, and does not initialize the system.
ATTENTION To access the following pages, select the Programming
menu, as the note books on the lower part of the screen are not available.
Figure 33
82
Event test programming page.
Keypad codes
If this item is selected, a page opens for user code programming. The
codes and the Electronic keys permit the user (and the installer) to access
the system.
32 available
codes
Omnia Control Panel can control up to 32 codes, 0 through 31 are user

codes, code 32 is for the installer. It is possible to define the enabled functions and the Areas for each code, making user code management extremely flexible.
Keypads and
User codes
As already seen in the {Config.} page, it is possible to define the enabled

Areas for each Keypad. Each action that a code requests affects only the
enabled Areas of the User code and Keypad in question. The uses of
this double level are many. For example, a code can be made to affect certain Areas, when entered on one Keypad and others Areas when entered
on another. The simple programming session permits the user to learn the
operations quickly, as the same arming operation has different effects on
different keypads.
Recognized user
code event
The recognition of a valid code by the Control Panel generates the event
Recognized user code no.. As for any event generated by the Control
Panel, this event can be assigned to an action on an output or on a telephone line, whether the code is enabled or not for the action requests on
the Control Panel. Several problems caused by access checks and/or limitations can be solved by means of the adequate programming of events
and outputs (e.g. see the "Recognition of multiple codes" paragraph in the
"APPLICATIONS" chapter).
Installer code
Code 32 is for the installer. Only the description of this code can be programmed in this page. The Installer code item of the Programming
menu permits programming of the Installer PIN.
Parameters to be programmed by the installer
The following are the parameter descriptions that feature a code and their
meaning.
Available
By means of this parameter only the required codes are made available, in
this way, code programming is greatly simplified. The Omnia Control Panel
can manage up to 31 User codes, but in most cases fewer codes are required for system management.
If a code is not made completely available, it may be considered inexistent.
Once a code has been made available to the user, its Master code can
enable/disable it or change its PIN.
After a code has been enabled by the user (see the "Parameters to be programmed by the user" paragraph), it cannot be made Not Available by the
installer. The code can only be made Not Available after it has been disabled by its Master code.
PROGRAMMING
83
Master code
This parameter is crucial to the setup of code hierarchy. It specifies which code
the code being programmed depends on: a code can also depend on itself.
A Master code can modify the following listed parameters of its Slave
code (see the "Parameters to be programmed by the user" paragraph):
Active: the Master code can enable/disable its Slave code, except when
the Slave code is Master of another Code.
PIN: the Master code can change the PIN of its Slave code.
+
+
+
When a Code is specified as a Master code it becomes Available and

Active (if it is not so already).
A Master code cannot be made Not Active and therefore cannot be made
Not Available. When a Master code is disabled, loss of its Slave code
management occurs.
The Master code cannot be modified on an Active Code. Therefore, before changing a Master code to a code, the Master code must be made
Not Active.
Codes 25 through 31 cannot be Master codes. Therefore, in the Master
code field, Codes 1 through 24 can be used.
All Code types, will always have at least one Available and Active Master
code.
A Code may be the Master of itself, and therefore, able to change its own PIN.
The system is initialized with Code no. 1 (Code
ter of itself, therefore, Code no. 1 is a Master code.
Figure 34
84
001), that is Mas-
Code programming page.
Enable on areas
The first line shows the Area the Code can control (Arm, Disarm, Signal
Block, Bypass Zones): Areas are shown by their ID numbers (from
1 through 8); the cells indicating Yes (where the Area ID number slices the
row immediately under the Area ID numbers), show that the Code is enabled on the corresponding Area; the contents of the cell can be modified
by double-clicking or pressing the ENTER key on the selected cell.
Enabled Areas, are those Areas armed or disarmed, when a Code followed by
or
is entered.
The second line, indicated by A, contains the Areas to be armed (A) or disarmed (D) among those enabled when a Code followed by
is entered
on a Keypad; to change an Area status double-click or press the ENTER
key on the corresponding cell.
The third line, indicated by B, shows the Areas to be armed (A) and disarmed (D) among those enabled, when the Code followed by
is entered on the Keypad; to change an Area status double-click or press the
ENTER key on the corresponding cell.
Enable user
menu
Among the available items for a User code, it specifies the items actually
available for a given code. In this way the menu can be customized according to user requirements. In fact, only the enabled items are displayed
in the user menu. The actions that can be enabled are the:
Arm/Disarm: single Area arming / disarming;

Panel reset: alarms on panel reset / stop;
Areas reset: alarms on Areas reset / stop;
View/Bypass zones: Zone display / bypass;
View: event logger display;
Teleservice: teleservice;
Clear call queue: clears telephone-call queue;
Output management: enable/disable outputs.
The aim of the single options is to make the menu item they refer to available. Some features are valid for the Teleservice and Alarm Reset/Stop
options, and are as follows.
+
+
The status of the Teleservice item (enabled/disabled), affects the menu

items Teleserv.request, En./Dis.Teleser. and En./Dis.Answer.. These are displayed only if the Teleservice item is enabled.
The activation of the items Panel reset and Areas reset, establishes the
actions carried out by the control panel, when Alarm reset or Alarm
stop is selected. If a Code is not enabled for these items, they will not be
displayed in the USER MENU.
PROGRAMMING
85
Alarm reset
When the Alarm reset item is available and is selected by a Code enabled for Panel reset, the following actions occur:
r deletion of the alarm memory relevant to: Main unit opening, balanced
tamper, BPI device tamper, false Electronic key on Key reader;
r return to standby status of outputs activated by the events in the following table.
Fire alarm on panel
24h alarm on panel
Burglar alarm on panel
Generic alarm on panel
Tamper alarm on panel
Generic+Tamper alarm on panel

Tamper on Main unit
Balanced tamper
Tamper on BPI devices
False key on key-reader
If the Code is enabled for Areas reset, the Alarm reset action requested in the USER MENU, affects the enabled Areas of the Code, in the
following ways:
r deletion of the alarm memory relevant to Area alarms and Area tamper;
r return to standby status of outputs activated by the events in the following table.
Fire alarm on area
24h alarm on area
Burglar alarm on area
Alarm stop
Generic alarm on area

Tamper alarm on area
Generic+Tamper alarm on area
When the Alarm stop item is available in the USER MENU, and is selected by a Code enabled for Panel reset, the Outputs activated by the
events in the following table return to standby status.
Fire alarm on panel
24h alarm on panel
Burglar alarm on panel
Generic alarm on panel
Tamper alarm on panel
Generic+Tamper alarm on panel

Tamper on Main unit
Balanced tamper
Tamper on BPI devices
False key on key-reader
If the same Code is also enabled for the Area reset, the Outputs activated
by the events in the following table return to standby status.
Fire alarm on area
24h alarm on area
Burglar alarm on area
Generic alarm on area

Tamper alarm on area
Generic+Tamper alarm on area
Please remember that an Output returns to standby status when all activating events end. For example, if a siren is assigned to two Areas and both
are in alarm status, the Alarm stop must be performed on both Areas.
86
Enable imm.
actions
Besides the actions available in the USER MENU, there are other actions
that a User code can perform.
Arming type A: type A arming can be performed by entering the Code followed by the
key.
Arming type B: type B arming can be performed by entering the Code followed by the
key.;
Arm enabled areas: enabled Area arming can be performed by entering

the Code followed by the
key;
Disarm enabled areas: enabled Area disarming can be performed by entering the Code followed by the
key;
Enable time programmer: enable the timer programmer control;

* Enable / Disable via DTMF: Code enable/disable via DTMF;
* Inputs state via DTMF: Input reading via DTMF;
* Remote listen-in - Telephone function: remote listen-in and two-way
conversation (telephone);
*
The last 3 features refer to the functions available for a Code, via telephone, by means of the DTMF commands. See the "TELEPHONE OPERATIONS" chapter in the "USER MANUAL", in the "Enable/Disable PIN"
and "Reading of input zone status" paragraphs, and the "Remote Listen-in"
and "Telephone". If the OmniaVOX module is installed, codes 25 through
31 are enabled for these functions.
Access to the timer programmer provides the item Overtime request,
this allows the user to request an extension of the arming time. If the Code
is enabled to Panel reset, the timer programmer control enable makes the
Auto-arm En/Dis. available, allowing the Code to enable/disable the
auto-arm/disarm carried out by the timer programmer.
PROGRAMMING
87
Parameters to be programmed by the user

The following are the Code parameters that can be modified by the user.
Only the Master code can modify the parameters of each Code.
PIN
The PIN (Personal Identification Number) is the digit sequence the Control
Panel recognizes as user identifier. This sequence can be 4, 5 or 6-digit long.
Active
Usually a Code is Active, which means it can perform all the programmed
functions. The Master code can make its Slave codes Not-Active.
If a Code is Not-Active it will not be recognized by the Control Panel and
therefore it will not have access to the functions previously available. A
Code cannot be made Not-Active whilst it is Master of any other Code
(or Master of itself).
Code status
A User code may have different statuses according to the Available and
Active parameter status.
Not Available
A Code with this status is not visible in the code list. This status can be
programmed by the installer on Not Active Codes only. Random PINs
should not be assigned to these Codes, as this may jeopardize control
panel security. Only Codes actually required should be programmed.
Available
A Code with this status is available to users. In particular to its Master

code user. A code with this status may be Active (or Not Active). The
Master code of an Available Code may change the Active (Not Active)
status and its PIN.
An Available/Active Code is able to perform all the operations it is programmed for. Its status may be changed to Not-Active by its Master
code, as long as it is not Master of any other Code.
An Available/Not active Code is available to the Master user who can
change its status to Active or can change its PIN. A Code with this status
is also available to the installer who can make it Not Available to the user.
Programming
On the left side of the {Keypad codes} programming page the list of the 32
codes the Control Panel can manage will be displayed. The following parameters will be explained for each of them.
no.
This is the identifier number used during programming via Keypad, to select the Code to be programmed. The first 31 codes are User codes, the
last is the Installer code.
Description
This is a modifiable 16-character max. field, for the assigned name of the
Code, this name will be used to identify the Code in all the actions it is involved in. This name will also be displayed in the welcome message.
Master
88
This specifies the dependencies of the relevant Code.
In the right side of the page, it is possible to define the Installer parameters
and also the User parameters of the Code selected in the left part of the
page.
The parameters programmable by the user can be found in the User parameter section. In order to operate on these parameters (PIN and Active), it is necessary to enter the PIN of the Master code of the Code to be
modified. The PIN must be entered in the PIN Master field of the User parameters section.
The parameters that can be programmed by the installer can be modified
as previously explained. The main rules are the following:
if a Code is Active the installer cannot modify the Master code and the
Available parameter;
a Master code cannot become Not Active, and therefore cannot become
Not Available;
to change the parameters that can be programmed by the user the PIN
Master must be known.
Figure 35
Programmable code data window.
PROGRAMMING
89
Programming
procedure
After code definition, select Send to copy it into the memory of the connected Control Panel. Select Load in order to load the code definition of
the connected Control Panel into the PC. Code programming is rather intricate, this is due to the importance of code functions (system access). The
following notes on the programming procedure may be helpful.
When opening the {Keypad codes} programming page, if no data from a
Control Panel is loaded, the PINs of the 31 User codes are the factory default codes, that is, 0001 for User code no. 1, 0002 for User code no. 2,
and so forth to 0031 for User code 31.
Code programming that starts as stated above, is typical of those situations which require the Control Panel to contain default data or when it is
necessary to program parameters totally independent of the User codes
(descriptions, enabling of functions and Areas). For user parameter programming, the code definitions must be loaded from the Control Panel.
When sending the programming to the Omnia Control Panel, depending on
whether or not all the User PINs memorized on the Control Panel are
known, the following two conditions are possible.
Known user PIN
The code definitions may be factory default or those loaded from the Control Panel: all the data in the {Keypad codes} programming page are sent,
including the modified user parameters (if any).
Unknown user
PIN
The code definitions are not factory default and have not been loaded. In
this case the data sent are:
Description;
Enable on areas;
Enable user menu;
Enable imm. actions;
Available - if the Code in the Control Panel programming is Not Active.
Master code, Active, PIN will be left out.

This programming restriction is justifiable, as it is part of security system
defence and therefore a protection for User codes. Before sending data to
the Control Panel the program displays an information window similar to
that shown in picture 35.
The window shows which parameters will be sent, and those which will
not. The rows refer to 32 Codes, and the columns contain the parameters
that can be programmed for a Code (Programmable data). The cells containing Yes, at the point where the rows slice the columns, indicate, that
when Send is selected, the parameter in that column will be programmed
for the Code in that row. The cells containing No indicate that the parameter will not be programmed on the Control panel.
90
Electronic keys
Opens the {Electronic keys} definition page where a name with a maximum
of 16-character can be assigned to each of the 250 Electronic keys that
Omnia can manage. This name will be used to identify the Electronic key
in any action it is involved in.
no.
This is the identifier number used during Keypad programming, to program

the Electronic key.
Description
The Electronic key description must be entered in this field (max. 16 characters).
En.
This enables the Electronic key. A Electronic key that has not been enabled is regarded as false.
1..8
Use this grid to define which Electronic keys are assigned to which Areas.
After defining the Electronic keys, select Send to copy it into the connected
Control Panel memory. Select Load in order to load the Electronic key
definition of the connected control panel into the PC memory.
Super keys
To obtain a Super key press a Keypad key, for at least 3 seconds. Omnia
can manage all the number keys as Super keys.
By means of this command it is possible to assign a name, with a maximum of 16 characters, to each Super key.
The name will be used to identify the Super key in every action it is involved in.
no.
Description
This is the Super key identifier number from 1 to 10 (the
key stands for 10).
Enter the Super key description (max. 16 characters) in this field.

After defining the Super key, select Send to copy it into the connected
Control Panel memory. Select Load in order to load the Super key definition of the connected Control Panel into the PC memory.
Filter times
Opens the {Filter times} page where it is possible to modify only the Mains
field which shows the delay timeout, before mains failure is acknowledged
and event no. 223 Warning mains failure is generated: set the delay in
seconds; 0.3 sec. through 3,600 sec. (= 1 hour) with steps of 0.1 second.
PROGRAMMING
91
Options
Opens the {Options} page where the following operating functions can be
programmed.
Maintain Zone
Test Attribute
The Test Attribute on Zones is maintained even when the Area is disarmed,
that is, Zone alarms on Test Zones are recorded in the event logger.
Disable welcome
message
The welcome message will not be displayed when a valid Code is recognized.
LEDs OFF on
Key readers
When no valid Electronic key is on a Key reader, the three LEDs will be
OFF.
Bypass tamper
on zone
This option enables Zone-tamper bypass, when the Zone is bypassed.
Disable arming
on battery
trouble
If this option is selected, the system cannot be armed if there is battery

trouble on the Main unit or on the connected Power stations, especially for
these events:
- Warning low battery;
- Warning power trouble;
- Warning low battery on power station;
- Warning power trouble on power station.
Disable tamper
memory reset
with User code
If this option is selected, a User code cannot reset the Zone, Area and
Panel tamper alarm memory, this function can be performed only by the Installer code.
Disable alarm
memory reset
with Installer
code
If this option is selected, the alarm memory cannot be reset by the installer,
this function can be performed by enabled User codes only.
Enable
panel-alarm stop
with valid
Electronic key
If this option is selected, it is possible to stop Control panel alarms by inserting a valid Electronic key in any Key reader.
Lock Installer
code
Once this option is selected, reset of the factory default programming does
not default the Installer PIN.
Please note that if this option is enabled, the Control Panel programming
cannot be accessed without the Installer PIN.
Lock Keypad on
invalid code
If this option is selected, Keypad lock-out occurs, after a programmed

number of wrong Codes.
Attempts
This specifies the number of wrong codes permitted, before lock out: set 1
through 10.
Lock time sec.
This is the Keypad lock-out time (in seconds): set 9 through 1,800 seconds.
92
Timer programmer
This programming page is described in the OmniaTIMER chapter.
LCD strings
By means of this option, it is possible to change the language on the Keypads to that used in the program: the language used in the program is set
by means of the Language command in the Options menu; the selected
language will become active after the subsequent program launch.
In order for this command to be active, the Control Panel must be connected to the PC by means of the serial cable.
Clock
It is possible to define the Omnia clock settings in this page.
Clock
The system date and time can be set in this part of the page.
Date format
The display date format can be set: English (yyyy/mm/dd) or Italian

(dd/mm/yyyy).
Separators
The separator characters of the date and time, can be selected as they appear on the Keypads display.
Figure 36
Options programming page.
PROGRAMMING
93
Installer code
The Installer code is enabled for all the modification procedures of the
Control Panel parameters, from the control Keypad and local or remote PC
connection.
The Installer PIN is therefore, a very important parameter, which can be
modified from the control Keypad by means of the Installer code
item, in the INSTALLER MENU.
When Installer code is selected on the Programming menu of the management software, a window, which permits modifications to the current
PIN, is displayed. The new PIN will be valid for access to Control Panel parameter programming.
Current PIN
It is necessary to enter the Installer PIN, required for data transfer with
the connected Control Panel (local or via telephone), in the Current PIN
field. If the PIN entered in this field does not match the one stored in the
Control Panel memory, data cannot be sent to the Control Panel (the Control Panel cannot be programmed).
PIN change
The Installer PIN can be modified in the lower part of the window, by
means of the two items, New PIN and Check new PIN, and then sent to
the connected Control Panel.
The new PIN must be entered twice in order to avoid errors.
Figure 37
94
Installer Code programming window.
Programming from local PC

Once the function parameters are defined, they must be copied into the
Control Panel memory.
For this purpose, a serial connection between the PC and the connector 6
of Omnia must be made, by means of a serial cable.
Use the CVSER/9F9F cable item, available on request, for the connection
via serial cable. The cable can also be made according to the following
diagram.
If the PC has 25-pin serial-port connectors, the ADSER/9M25F adapter,

should be used, this item is available on request. The cable can also be
made according to the following diagram.
Only authorized personnel can program the Control Panel, as the Main
Unit must be opened to access the serial port, whereas, teleservice is
available, with the approval of the user with Knowledge of the enabled
code.
The serial port used for the connection between the PC and Omnia, must
be specified by means of the Serial ports command in the Options menu.
PROGRAMMING
95
At this point, the programming data can be sent to the Control panel, by
means of the Programming > Send > Page menu item, which sends the
current page only or, the Programming > Send > All menu item, which
sends all programming, this operation takes about 3 minutes.
Programming from the connected Control Panel can be read by means of
the Programming > Load > Page menu item, which loads the current
page only or, the Programming > Load > All menu item, which loads all
programming, this operation takes about 3 minutes.
+
+
+
96
Use the Send and Load buttons on the current programming page, to
send or load the programming pages that cannot be accessed from the
notebooks.
The programming transfer occurs when the Installer code, entered in the
Programming > Installer code menu item, is acknowledged by the Control Panel.
Make sure that the firmware release in the Omnia program, that can be accessed through the Options > Firmware release menu item, is the same
as the firmware release of the Omnia Control Panel being programmed. To
check the firmware release version display the Revision item of the INSTALLER MENU from any control Keypad.
Programming from PC via telephone

To program or read data from a Control Panel connected via telephone,
use the same procedure as when programming from a local PC. Although,
it is necessary to establish the connection between the OmniaMOD modem the PC is connected to, and the Omnia Control Panel.
Connect OmniaMOD to the PC using the serial cable provided (the same
used for local programming), select the PC serial port for the modem, in
the Options > Serial ports menu item.
Connection
Use the Modem > Connecting menu item to access the Connection
management window shown in figure 38. The Telephone number , Jump
answer machine and Security recall are described in the "Customer",
"Telephone" and "Teleservice" paragraphs.
When a customer is active or loaded, the described parameters have the

programmed values. These parameters can be temporarily changed without affecting the parameters of the active customer, in fact, when the window is next opened, the parameters will have the current customer values.
Use the Dial button to start the connection procedure. Its development will
be shown in the bottom window. At this point the OK button cannot be selected, indicating that the connection has not been established. When the
connection has been completed the following messages will be displayed:
OMNIA ACK
Recognized Installer Code
Figure 38
Window for the telephone connection to the Omnia Control Panel.
PROGRAMMING
97
Now the OK button can be selected, indicating that the remote connection
has been established. When this button is selected the connection window
closes, and the condition is similar to that of PC local connection; the difference being that the transfer data command (Send, Load) will affect the
Control Panel connected via telephone.
+
Software
messages
If teleservice calls are to be answered, the user must enable the Teleservice function on the Control Panel (see USER MANUAL).
The bottom window in the Connection management window provides information on the connection status. The following list contains several
messages and their meaning.
Omnia/Norma MODEM v. x.xx

Modem not recognized
Receiving....
RING
BACK RING
NORMA ACK
OMNIA ACK
Installer Code reading error
Lost Connection
This specifies the modem version

connected to the PC serial port.
The modem is not recognized on
the selected serial port. Check the
cable and the selected serial port in
the Options > Serial ports menu
item.
The Modem/PC system is waiting
for an incoming call. This is the
system status when the window
opens.
The modem is detecting rings on
the telephone line.
After the dialling the telephone is
ringing.
An NormaCom Control Panel has
been acknowledged.
An Omnia Control Panel has been
acknowledged.
The PIN sent by the software to the
Control Panel cannot be read,
probably due to the poor quality of
the signal on the telephone line.
Communication to the Control
Panel cannot be established
probably due to the poor quality of
the signal on the telephone line.
See the "Programming with local PC" paragraph, in order to check the
steps for sending or receiving programming from the connected Control
Panel.
Use the menu item Modem > On-hook to end the connection.
98
Keypad programming
All the parameters in this chapter can be programmed via Keypad, using
the following items from the INSTALLER MENU.
r Tel.Numb.Progr. (Telephone Number Programming);
r Descript.Progr. (Description Programming);
r Installer code;
r User codes;
r Parameter progr. (Parameter Programming).
Moreover, the Electronic-key coding and the Voice-message recording
can only be carried out via Keypad. These functions can be accessed from
the INSTALLER MENU in the items:
r Voice functions;
r Electronic keys;
The INSTALLER MENU and its functions are described in the following
chapter (KEYPAD OPERATION).
Default reset
Reset the default setting in the following way:
disconnect the Main unit power (the mains power supply and the buffer
battery must be disconnected);
remove jumper 7 (MEM);

wait for 20 seconds at least;
replace jumper 7 (MEM);
connect the Main unit power supply (see "Power supply connection").
ATTENTION The default setting is not guaranteed, unless jumper
7 MEM is disconnected for at least 20 seconds. Moreover, if this period is not respected, malfunctions may occur when the power supply
is reconnected to the Main unit.
Installer code
locked
If the Lock Installer code option is programmed, the Installer PIN will not
be reset to factory default (see "Lock Installer code" in the "Options" paragraph).
PROGRAMMING
99
Default setting
When the Control Panel leaves the factory, it is programmed for fast and
simple installation.
Configuration
On startup, the Control Panel recognizes every connected device on the

BPI bus and sets the configuration accordingly.
Zones
Each Zone is programmed as: Alarm, Double balanced, single Pulse,

Repetitive.
Zones no. 1 and no. 2 are programmed as Entry delay and Exit delay;
the others are Immediate.
All Zones is assigned to Area no. 1.
Outs
All outputs are Bistable, except the first two, which are Monostable with a
3-minute On time. The two Monostable outputs may be used as bell
alarm outputs. The default Off Time is 6 seconds.
Areas
Each Area has the Entry time set at 30 seconds, the Exit time set at 30
seconds and the Last exit time set at 6 seconds.
Dependency among Areas is not defined.
Keypads and
Key readers
All Keypads are enabled to manage all Areas.

Key readers are enabled for all the Areas and the type A and B arming are
not defined (every Area is disarmed).
Codes
Code no. 1 (Code

001) is the only Avilable and Active User
code set at the factory; its PIN is set at 0001, and it is enabled on all the
Areas and on all functions.
The Installer code PIN is set at 0032.
Event-Actions
The following events are addressed to output no. 1:
Generic alarm on area no.

The following events are addressed to output no. 2:
Tamper alarm on area no.;

Tamper on Main unit;
Balanced tamper;
Tamper on BPI devices;
The following event is addressed to output no. 3:
Warning generic.
The following event is addressed to output no. 4:
Trouble on BPI.
100
Dialler
Action no. 1 sends message no. 1 to the first 16 numbers of the telephone-number list, this action is generated by the following events:
Generic alarm on area no.

Action no. 2 sends message no. 2 to the first 16 numbers of the telephone-number list, this action is generated by the following events:
Tamper alarm on area no.;

Tamper on Main unit;
Balanced tamper;
Tamper on BPI devices;
PROGRAMMING
101
A basic system
The factory programming can be used to set up a simple system. This system can manage a certain number of Zones and will signal alarms by
means of a siren and a telephone dialler. Arming and disarming can be
carried out via Keypad or Key reader.
To startup this simple system carry out the following procedure.
Connections
The following is a description of the main wiring that must be laid.
Zones
If there are more than 8 Zones the Input expanders necessary to reach the
required number of Zones must be connected on the bus. Therefore the
device address code must be carried out as described in the "BPI device
connection" paragraph.
Both for the Zones on the Main unit and the Zones on the Input expanders
(if any) must be connected to the sensors according to the double balancing circuit diagram in the "INSTALLATION" chapter.
Please remember that Zones no. 1 and no. 2 are programmed as Entry
delay and Exit delay, therefore they can be used without any further programming.
Siren
Connect the self-powered siren to Output no. 1 using the terminal [+N1]
and the ground terminal.
Keypads
All the necessary Keypads must be connected to the bus. If more than one
Keypad is used, the device address coding must be carried out as described in the "BPI device connection" paragraph.
Key readers
The required Key readers must be connected to the bus. If more than one
Key reader is used, the device address coding must be performed as explained in the paragraph "BPI device connection".
Telephone dialler
Telephone line
Install the OmniaVOX kit as described in the same chapter.

Connect the telephone line as described in the chapter "INSTALLATION".
Programming
Telephone
numbers
Program the telephone numbers that the telephone dialler must call in the
case of alarm or tamper, according to the procedure in the "Telephone
numbers" paragraph in the "KEYPAD OPERATIONS" chapter. The first 16
numbers are available.
Voice messages
Record the Voice mess. 001 for alarm status, and Voice mess. 002
for tamper status, according to the procedure in the "Voice functions" paragraph in the "KEYPAD OPERATIONS" chapter (a maximum of 15 seconds for
each message).
102
Codes
According to factory settings, User code no. 1 is immediately Active. The

Code no. 1 PIN can be modified by means of the Codes Programm. item
in the USER MENU.
If more than one Code is required, follow the instructions in the "User
codes paragraph" in the "KEYPAD OPERATIONS" chapter, in order to
have use of up to 31 User codes.
Electronic keys
According to the "Electronic keys" paragraph in the "KEYPAD OPERATIONS" chapter, the required number of Electronic keys must be programmed.
Proceed as follows.
Code creation: a number is created randomly from among more than 4

billion combinations.
Programming: the required Electronic keys must be programmed.

System use
Arming and
disarming with
code
The user can arm the system by entering his own Code followed by the
Arming and
disarming with
Electronic key
The user can arm the system by means of a valid Electronic key on a Key
reader. Insert the Electronic key into the Key reader and press the button
on the Electronic key once. The red LED will turn on. When the Electronic
key is extracted the system will arm and the red LED on the Key reader
will be solid. To disarm the system insert the Electronic key into a Key
reader, the red LED will turn off. When the Electronic key is extracted the
system will disarm and the red LED will go off.
Alarm stop on
siren
In order to stop alarm siren signalling generated by an alarm Zone event,

insert a valid Electronic key in any Key reader or carry out a disarm operation. If the alarm is generated by Zone tamper on the Control Panel the
Alarm stop from the USER MENU must be performed. This step is car-
key. Similarly, the
key followed by the Code disarms the system.
ried out by entering the User code followed by

,
and
. After
eliminating the cause the Alarm Stop status can be quitted by pressing the
key. The active Alarm Stop is shown by a flashing message on the
Keypad.
Telephone
dialler stop
To stop the telephone dialler enter the User code from any Keypad and
press
and again
. To quit the USER MENU press
The telephone dialler can be stopped automatically as explained in the

"Alarm stop by means Electronic key" paragraph in the "APPLICATIONS"
chapter.
Alarm memory
reset
To delete the alarm memory enter the User code from any Keypad and
press the
PROGRAMMING
key twice. To quit the USER MENU press
103
104
KEYPAD OPERATIONS
The Installer code gives access to the INSTALLER MENU and all the functions reserved for the installer, including the parameter programming.
The INSTALLER MENU includes the following items:
View logger
Displays the contents of the event logger.
Zones status
Displays the alarm/bypass status of each Zone.
Outs
management
Permits manual control of the Reserved outputs.
Clear call queue

Voice functions
Clears the outgoing telephone call queue.

These functions require the installation of the OmniaVox kit, and include
recording, playback and deletion of Voice messages.
Tel. Numb. progr.
Permits programming of the telephone-number directory.
Descript. progr.
Permits the description programming of each system item.
Installer code
User codes
Electronic keys
Parameter progr.
Revision
Permits programming of the Installer code.

Permits installer parameter programming of programmable user codes.
Permits enable functions and Electronic-key code programming.
Gives access to control panel parameter programming (with the exception
of the timer programmer, which is accessed from the PC).
Displays the firmware revision of the Omnia control panel.
KEYPAD OPERATIONS
105
General rules for INSTALLER MENU use

These keys scroll the menu item.
These keys may be used to move the cursor onto the character to be
modified (flashing character).
This key quits the parameter being programmed, without changing its
value: if pressed from the INSTALLER MENU, the programming mode will
be quitted.
These keys can enable/disable respectively the corresponding item.
This key confirms the setting or the selection made.
+ -- These characters show, respectively, that the corresponding item is enabled/disabled.

Identification
numbers
The identification number should be used when it is not possible to use the
assigned item description.
Boop
This is the low-pitched sound, on the Keypad, when a requested action is

not allowed.
INSTALLER MENU access
Access to programming can be obtained only when all Areas are disarmed, therefore, approval of all the system users is required.
To access the INSTALLER MENU, follow these instructions.
Hour
From the standby status ...
Year Month day
:1 1996/03/05
DDDDDDDD
Areas status: D=Disarmed; A=Armed
106
Enter the Installer code: the default value is

0032.
Input
Code
****XX
Press
INSTALL.MENU
View logger
When entering the INSTALLER MENU the Control Panel will perform the
following operations:
put all the Keypads, with the exception of the one in use, in stand-by (the
Keypads in stand-by signal the description of the Keypad in use);
erase the alarm memory;

place all outputs in standby status;
stop the event evaluation;
interrupt the current telephone call (if any) and hold the queued calls.
Therefore, the Control Panel can be considered as disabled.
Quitting the
INSTALLER
MENU
Press
to quit the INSTALLER MENU; the Control Panel will then perform the following operations:
place the Keypads in standby status;

erase the Zone-cycle counter;
erase the missing BPI device alarm, tamper and false Electronic key alarms;
resume the calls in the telephone queue, starting from the call (if any), interrupted on access to the INSTALLER MENU, except for a teleservice
call;
if the front panel has been opened, the open panel alarm will be disabled
until it is closed again.
View logger
If this item is selected from the INSTALLER MENU, the contents of the
event logger will be displayed.
Each event can be described in a maximum of 5 rows, which give a detailed description of the event type, the place, the time and also the user.
The rows appear in this order:
event type;
event identifier number;
agent;
agent identifier number;
hour, minute, year, month, day.
Please remember that not all events have all these parameters.
The event display is cyclic, therefore, it sends the first event to the second,
the second to the third ......, the last to the first, and vice versa.
KEYPAD OPERATIONS
107
From the installer menu ...
Press
logger.
Press
Use
or
to display the item View
5
6
INSTALL.MENU
View logger
Ev.197 Type
Tamper zone open
to scroll the memory.
Ev.197 Zone
South
4
Use
or
the event .
Ev.198 Type
Mains OFF
or
INSTALL.MENU
View logger
to scroll the lines describing
Ev.197 Inst
17:49 05/03/1996
To return to the INSTALLER MENU press
INSTALL.MENU
View logger
Zones status
Select this item from the INSTALLER MENU to display the alarm, tamper
and bypass status of each Zone, the Zones may then be bypassed or unbypassed.
This function is useful for Control-Panel Zone checks, during installation or
when checking Control Panel functioning.
If a Zone is Double balanced it may have Standby, Alarm, Short or
Tamper status, if Balanced, it may have Standby, Alarm or Short status,
if NC or NO it may have Standby or Alarm status only.
To display the Zones, follow these procedures.
From the INSTALLER MENU ...
Press
or
is displayed.
Press
until the item Zones status
108
Panel will be displayed, use

scroll the Zones.
or
INSTALL.MENU
Zones status
South entrance
Stdby
Active
The status of the first Zone on the Control
INSTALL.MENU
View logger
or
Use
Zone.
to
to bypass or un-bypass the
Stair window
Alarm
Active
Stair window
Alarm
Bypassed
INSTALL.MENU
View logger
Outs managements
Using this item from the INSTALLER MENU, every Output in the system
can be controlled, as follows.
INSTALL.MENU
View logger
Press
or
until
management is displayed.
Press
the
item Outs
INSTALL.MENU
Outs management
Alarm Siren
ON-Act.OFF-Stdby
The description of the first Control Panel
Fire siren
ON-Act.OFF-Stdby
Output will be displayed, use

or
to
scroll the Outputs and to select the required
Output.
By using
or
the displayed Output can
be activated or forced into standby status.
Fire siren
ON-Act.OFF-Stdby
INSTALL.MENU
View logger
Clear call queue

By means of this Installer-menu item, it is possible to erase all the calls in
the call queue. Follow these instructions.
INSTALL.MENU
View logger
Press
or
until the item Clear call
queue is displayed.
Press
The call queue will be erased, and the display

will return to the INSTALLER MENU.
KEYPAD OPERATIONS
INSTALL.MENU
Clear call queue
Clear call queue
D O N E!
INSTALL.MENU
View logger
109
Voice functions
In this session it is possible to record, playback and erase Voice messages.
Omnia can store two 15-second messages, two 10-second messages and
ten 4-second messages; these messages can be assigned to Control
Panel inputs, for input-status checks via telephone, or can be sent to telephone numbers (telephone dialler), and also be used for recording a Nobody-home answer message (answering-machine function).
+
Erase
These functions require the installation of the OmniaVOX kit, otherwise,

ATTENTION !
NO
VOX CARD
the display will show the message
.
This action should be carried out after installation of the OmniaVOX kit,
and before recording the messages; it will erase all Voice messages and
will initialize the voice board memory.
To erase a specific message, it is necessary to record an empty message
in its place, by starting and then stopping recording, as shown in the following procedure (Recording);
To erase all Voice messages follow these instructions.
INSTALL.MENU
View logger
From the INSTALLER MENU...
Press
or
item is displayed.
Press
Press
or
displayed.
Press
: the display will show the deletion of
all voice messages, in sequence, then it will
return to step no. 2.
Recording
until the Voice functions
INSTALL.MENU
Voice functions
VOICE FUNCT.
Play Messages
VOICE FUNCT.
Erase messages
until the Erase messages is
GO BACK TO STEP NO. 2
To record Voice messages follow these instructions.

INSTALL.MENU
View logger
110
Press
or
item is displayed.
Press
Press
or
until the Record Messages
item is displayed.
until the Voice functions
INSTALL.MENU
Voice functions
VOICE FUNCT.
Play Messages
VOICE FUNCT.
Record Messages
4
5
Press
VOICE MESSAGES
Voice mess. 1
Press
or
until the Voice message to
be recorded is displayed, then press
To start message recording press
Speak into the microphone, at a distance of

about 20 cm, paying attention to the timeout . If
the recording ends before timeout expires,
press
Record
Voice mess.
Stop record
Sec.avail.
14
to end the recording.
When the recording of a message ends, it is possible to record another

message or, by pressing
them as required.
Playback
, playback the recorded messages or erase
For message playback, follow these instructions.

From the VOICE FUNCTIONS menu ...
VOICE FUNCT.
Play Messages
Press
or
item is displayed.
VOICE FUNCT.
Play Messages
Press
Press
or
displayed.
Press
Press
again: the voice board will playback
the selected message through the loudspeaker
and the display will show the message length,
it will then return to step no. 3.
Message playback can be stopped by pressing
until the Play Messages
VOICE MESSAGES
Voice mess. 1
.
until the required message is
VOICE MESSAGES
Voice mess. 1
Play
Voice mess.
Stop play
Sec.avail.
14
When playback of a message ends, it is possible to play another message

or by pressing
KEYPAD OPERATIONS
, record or erase other messages as required.
111
Telephone-number Programming
This step permits the programming of the 32 available telephone numbers
in the Omnia telephone directory.
Follow these instructions.
INSTALL.MENU
View logger
Press
or
item is displayed.
Press
until the Tel.Numb.Progr.
By means of
or
number to be modified.
Press
INSTALL.MENU
Tel.Numb.Progr.
TEL. NUMBER
Teleph.numb. 1
.
select the telephone
In this step, if
is pressed, it will return to
the INSTALLER MENU.
TEL. NUMBER
Teleph.numb. 3
Teleph.numb. 3
----------------
Enter the telephone number by means of
112
or
, use
or
to move the cursor. As
well as digits 0 through 9, this step accepts
characters A, B, C, *, # to access special
telephone functions, and also the comma ","
which indicates a 5-second pause.
To confirm the entered number and return to
step 3 press
Teleph.numb. 3
02,12345--------
GO BACK TO STEP NO.3
Description Programming
This item of the INSTALLER MENU allows modifications in the descriptions
assigned to Omnia Zones, Areas, Codes, Electronic keys and so forth.
A description may have a maximum of 16 characters.
Follow these instructions.
INSTALL.MENU
View logger
Press
or
is displayed.
Press
Enter the order number of the description to be

modified. A 5 digit number is required, for
example, 00008. Please refer to the chart
below for the order number.
until the item Descript.Progr.
INSTALL.MENU
Descript.Progr.
Name order numb.

1
Press
to return to the INSTALLER MENU.
Press
Name order numb.

8
Zone
Zone
The upper row contains the current description,

the new description should be entered in the
lower row. Use
or
to select the
8
8
Zone
8
Bedroom sensor
characters and
or
.to move the cursor.
To confirm the operation and return to step 3
press
Order numb.
1..80
81..88
89..104
105..112
113..128
129..136
137..138
Object
Zones (80)
Areas (8)
Key reader (16)
Keypads (8)
Order numb.
Object
Codes (32)
139..170
Electronic keys (256)*
171..426
Super keys (10)
427..436
437..468
Input expanders (16)

Output expanders (8)
Power stations (2)
469..504
505..518
Telephone numbers in
the directory (32)
Outputs (36)
Voice messages (14)
* The key number is actually 250: the programmed description for keys
ranging from 251 to 256 will be ignored.
KEYPAD OPERATIONS
113
Installer code
The Installer code is a 4, 5 or 6-digit code that allows access to the INSTALLER MENU and teleservice.
Default
Procedure
The factory installer default code is: 0032.

The Installer code may be modified as follows.
Press
or
is displayed.
Press
Enter the code. 4, 5 or 6-digit codes can be

entered; digits from 0 through 9 can be used; if
a code with less than 4 digits is entered, the
Keypad will boop and return to step no. 0.
Press
until the Installer code item
INSTALL.MENU
View logger
INSTALL.MENU
Installer code
Code
Code
32
XXXXXX
Code
Code
32
****XX
User codes
The installer may perform the following programming on the User codes.
Define which of the 31 reserved User codes will be Available to the users.
Define the enabled Areas for each Code.
Define the arming mode assigned to key
and key
Define the user-menu functions for each Code:

1
2
3
4
5
6
7
8
114
Single Area Arm/Disarm;

Control Panel alarm stop and reset;
Area alarm stop and reset;
Zone bypassing;
Event logger display.
Answering-machine and teleservice enable/disable;
Clear call queue;
Output management.
Define the enabled actions for each Code:

1
2
3
4
6
7
8
Type A arming:
Type B arming;
Global arming of the Areas for an enabled code;
Global disarming of the Areas for an enabled code;
* Control Panel management via telephone;
* Input reading via telephone;
* Voice function via telephone.
Define the Master code of each Code.

*
These actions may be programmed for Codes no. 25 through no. 31 only,
which cannot be Master codes.
A Code programmed by the installer in this way, is Available for users with
knowledge of the PIN of its Master code. Therefore, authorized users can
make a Code Active and program its PIN.
Procedure
After the Code has been made Active by the user, it cannot be made Not
Available by the installer.
For all the details relevant to programming and code operating mode, see
the "Keypad codes" paragraph in the "PROGRAMMING" chapter.
The following is the procedure for parameter programming by the installer.
The procedure for parameter programming by the user, is described in the
USER MANUAL.
Press
or
displayed.
Press
Press
or
until the Code to be
programmed is displayed.
to
make
the
selected
INSTALL.MENU
User codes
Code
2
Not available
Code
Available or press
to make the selected
Code Not available.
+ If the selected Code is Active it cannot be
Not Available therefore, the Keypad will beep.
Press
: the characters on the lower row of
the display show the Code-controlled Areas
being programmed:
-- shows that the corresponding Area cannot be
controlled;
+ shows that the corresponding Area can be
controlled.
KEYPAD OPERATIONS
Code
Available
Press
until the User codes item is
INSTALL.MENU
View logger
Code
Available
Areas enabled
++++++++
115
Press
or
to select the character to be
modified; then press
to enable the Code on
the corresponding Area; vice versa, press
Areas enabled
--++++++
Press
, the lower row will show the Areas
that will be armed (+) and disarmed (--) when
is pressed, after entering the Code being

programmed.
+ This arming mode is valid only on the Areas
controlled by the Code being programmed (see
steps 5 and 6).
Press
, the lower row will show the Areas
that will be armed (+) and disarmed (--) when
is pressed, after entering the Code being
programmed.
Arming type A
+++-++++
Arming type B
--+-----
Menu item enabl.

+-++++++
Press
, the characters on the lower row on
the display show the user menu items that can
(+) or cannot (--) be accessed by the Code
being programmed.
Out management
Clear call queue
Answer. - Teleservic.
Event logger display
Zone status - bypassing
Area alarm stop - reset
Panel alarm stop - reset
Area arming - disarming
Other act. enab.

--+++---
116
10
Press
, the characters on the lower row on
the display show the actions that can (+) or
cannot (--) be performed by the Code being
programmed.
11
Press
and enter the identification number
of the User code that will be able to modify the
status (Active/Non active), and the PIN of the
Code being programmed.
+ Only the Codes from no. 1 to no. 24 can be
Master Codes.
12
Press
Voice function
Input reading
Management via teleph.
Global disarming
Global arming
Type B arming
Type A arming
Master code
Electronic keys
Electronic keys are to be used on the Key readers, and they allow quick
and easy control of the main Omnia functions such as:
Global Area arming/disarming;

Area partial arming/disarming;
Area alarm block.
False Electronic
key
Each programmed Electronic key stores a 32-binary digit (bit) pseudorandom code, selected from more than 4 billion combinations. When an
Electronic key is inserted into a Key Reader, its code is compared to the
one in the Control Panel memory, if the codes match, the above-mentioned operations can be performed, otherwise, the Control Panel regards
the key as false and generates event no. 218 False key on key-reader .
If an Electronic key is disabled (see "Enable"), it is considered false even
though it may have a valid code.
To program an Electronic key it is necessary to copy the code in the Control Panel into the Electronic-key memory, in this way the key will be valid
and enabled.
Multiple systems
ID number
It is possible to copy an Electronic-key code into the Omnia memory (see

Code reading): in this way, every valid Electronic key on a Omnia Control
panel is valid on other Omnia Control panels, and the user may control different systems (in his own house, in the company etc.), by means of just
one Electronic key.
When an Electronic-key code is copied into the memory of an Omnia Control Panel, all other Electronic keys are disabled automatically, therefore, to
allow further use, they must be enabled one by one (see "Enable"). Usually
only a small percentage of Electronic keys are valid and enabled on several systems (e.g. Electronic keys used by employees are enabled on the
company system only, whereas, the Electronic key used by the owner can
also be valid on the system installed at the owners home).
The memory of each programmed Electronic-key holds the code, which is
the same for all users, and an identifier number which makes each Electronic key unique. Omnia can manage up to 250 keys, although an unlimited number may be programmed: those over 250 will all have the same
identifier number, 250, and therefore, cannot be distinguished one from the
other.
During programming each of the 250 Electronic keys can be assigned a
16-character (max.) description (usually the name of the user), which will
be used instead of the ID number, in all the actions it is involved in.
An Electronic key, valid on more than one system, should maintain the
same description.
KEYPAD OPERATIONS
117
Enable on Areas
Code creation
It is necessary to specify the enabled Areas - of the Control Panel performing programming - for each Electronic key (when an Electronic key
is enabled on an Area, it can perform the actions listed at the beginning of
this paragraph). The enabled Areas of an Electronic key are stored in the
Control Panel memory. It is possible to define a different group of Areas for
each Control Panel; therefore, an Electronic key may be valid on many
systems with Omnia, but it may be enabled on different Areas on each system.
The Areas that an Electronic key can control, depend on the enabled Areas on the Key reader. For example, if the Electronic key is enabled on Areas no. 1 and no. 2, and the Key reader is enabled on Area no. 1, the
Electronic key can control Area no. 1 only.
The following procedure generates the code that will be copied into the
Electronic keys: this is random code chosen from among more than 4 billion possible combinations.
INSTALL.MENU
View logger
Press
or
keys is displayed.
until the item Electronic
Press
Press
or
until the item New random
code is displayed.
Press
INSTALL.MENU
Electronic keys
ELECTRONIC KEY
Program
ELECTRONIC KEY
New random code
GO BACK TO NO. 3
Each time a new code is created, in the above mentioned way, all the
Electronic keys programmed up to that moment will become invalid (false)
on the Control Panel that generated the code (the same Electronic keys,
however, are still valid for all the Control Panels that copied their code with
the "Code reading" procedure).
Programming
Follow these instructions to program the Electronic keys.

INSTALL.MENU
View logger
118
Press
or
keys is displayed.
Press
INSTALL.MENU
Electronic keys
ELECTRONIC KEY
Program
Press
again, then press
or
until
the lower line shows the first Electronic key to
be programmed.
PROGRAMMING
Electr Key
Press
: the characters on the lower row of
the display show the Areas where the
Electronic keys being programmed can (+) or
cannot (--) work.
Areas enabled
++++++++
Press
or
to select the character to be
modified; then, press

to enable the
Electronic keys on the corresponding Area;
vice versa, press
Areas enabled
+++--+++
Press
, and enter the identifier number of
the Key reader required for Electronic-key
programming .
Use Key reader

2
Press
, the display will show the Electronic
key to be programmed, then, insert the
Electronic key into the Key eader indicated on
the display: the three LEDs on the Key reader
will go ON to indicate the positive outcome of
programming, if however, the LEDs flash, the
Electronic key has not been programmed.
Electr key
Key reader
2
2
Repeat step no. 7 for all the Electronic keys that must be programmed with
the same enable type on the Areas, as specified in step no. 5: the upper
line of the display will show the Electronic key to be programmed, and the
lower line will show the Key reader to be used. Press
step no. 3.
to return to the
It is possible to change the Areas that an Electronic key can control, without inserting it into a Key reader, just follow the above described procedure
through step no. 5, and then press
KEYPAD OPERATIONS
119
Code reading
The following procedure makes the Electronic keys, that have been programmed for one Omnia Control Panel, valid for another Omnia Control
Panel.
INSTALL.MENU
View logger
INSTALL.MENU
Electronic keys
Press
or
keys is displayed.
Press
Press
or
displayed.
until the item Read code is
ELECTRONIC KEY
Read code
Press
, then enter the ID number of the
Key reader that will be used for copying the
Electronic-key code.
Use Key reader

2
Press
, then insert the Electronic Key into
the Key reader indicated on the display.
GO BACK TO STEP No. 3
ELECTRONIC KEY
Program
Each time an Electronic-key code is read in the above mentioned way, all
the Electronic keys programmed up until that moment become automatically invalid. However, the Electronic keys that have become valid, will be
disabled on the Control Panel that read the code, and therefore, in order to
permit further use, must be enabled according to the procedure in the following paragraph.
120
Enable
Electronic keys can be enabled selectively, in this way, if an Electronic key
is lost it can be disabled, and as a new code is not required, it is not necessary to program all the Electronic keys again. A disabled Electronic key,
even if it has a valid code, will still be considered false and therefore, when
inserted into a Key reader, will not be acknowledged and will generate
event no. 218 False key on key reader.
An Electronic keys will be enabled on the Control Panel that programmed
it, whilst it will be disabled on the Control Panel reading its code.
Procedure
Follow these instructions to enable or disable an Electronic key.

INSTALL.MENU
View logger
From the INSTALLER MENU...
Press
or
keys is displayed.
Press
Press
displayed.
Press
Press
INSTALL.MENU
Electronic keys
ELECTRONIC KEY
Program
.
or
until the item Enable is
.
or
until the required Electronic
key is displayed, then press
to disable it or
ELECTRONIC KEY
Enable
Electr key
Disabled
Electr key
Enabled
to enable it.
Repeat step no. 5 for every Electronic key to
be disabled or enabled, then

the ELECTRONIC KEYS menu.
to return to
Only the installer (or a person with knowledge of the Installer code) can enable/disable an Electronic key; this operation does not require the Electronic key to be inserted into a Key reader nor does it require the approval
of the user.
KEYPAD OPERATIONS
121
Parameter programming
This INSTALLER MENU item permits the programming of all the parameters
that determine Omnia Control Panel functioning. The complete parameter description can be found in the "PROGRAMMING" chapter.
Parameter programming, due to its complexity, is dealt with separately in
the "KEYPAD PROGRAMMING" manual provided with Omnia.
Parameter programming does not include Timer programming.
Firmware release
This command, from the INSTALLER MENU, displays the Omnia Control
Panel firmware revision in use.
Follow these instructions to display the firmware revision.
122
Press
or
displayed.
until the item Revision is
Press
Press any key to return to the INSTALLER

MENU.
INSTALL.MENU
View logger
INSTALL.MENU
Revision
BENTEL - OMNIA
Rev. 2.1
INSTALL.MENU
View logger
OmniaVOX
The OmniaVOX kit contains a Voice board, a Microphone board and a

loudspeaker , with OmniaVOX it is possible to record and playback vocal
messages. The Voice messages can be assigned to the Omnia inputs for
input-status control via telephone, they may also be sent to telephone
numbers (telephone dialler) or used as answering messages (answering
function). Installation of the OmniaVOX kit increases the resources of the
Omnia system, in the following ways.
Specifications
r Records messages on electronic memory (ChipCorder technology).
r Records 14 Voice messages: 2 of 15 seconds; 2 of 10 seconds and 10 of
4 seconds.
r Loudspeaker for recorded message playback.
r Telephone-dialler function.
r Telephone answering-machine.
r DTMF tones management for Omnia-status control via telephone.
r Management of listen-in and remote two-way conversation (Telerescue).
Identification of the parts

PARTS
84
85
86
87
88
89
90
91
92
93
94
OmniaVOX
DESCRIPTION
Connector for the connection of the loudspeaker to the Microphone
board.
Microphone.
Loudspeaker connector.
Terminal board for Voice board connection.
Microphone board.
Main unit Voice board connector.
Electronic board of the Main unit.
Terminal board for Microphone board connection.
Voice board activity LED.
Voice board.
Loudspeaker.
123
Installation
For the correct installation of the OmniaVOX kit, carefully follow the instructions below, illustrated in figure 39.
A
Fix the loudspeaker 94 in position, on the back of the Main unit.
Fix the Microphone board 88 next to the LEDs and tamper switch board.
Connect the loudspeaker 94 by inserting the plug 84 into the connector 86.
Insert the Voice board 93 into the connector 89 on the electronic board of
the Main unit, indicated by the abbreviation "CARD1".
Shielded cable must be used for the connections between the Microphone
board and the Voice board.
Once the OmniaVOX kit is installed, follow the procedure indicated in the
"Voice functions" paragraph, this will erase any incidental messages recorded on the Voice board memory during installation.
Figure 39
124
Parts identification and installation of the OmniaVOX kit.
Extension of the Listen-in areas

If one Microphone-Loudspeaker board is insufficient for the environment,
due to size or the presence of walls which may muffle sounds, it is possible
to connect other Microphone-Loudspeaker boards to the Voice board, and
position them as required.
The Microphone Boards and loudspeakers installed outside the Main unit,
must be placed as near the point of use as possible and, if sound interference is to be avoided, must be positioned at the proper distance.
The supplementary boards must be connected parallel to the Voice board,
as shown in figure 40. Please remember that the number of boards connected, and the connection lengths, will affect sound quality. For an acceptable level of sound quality follow the instructions below:
do not connect more than 4 Microphone-Loudspeakers to the Voice board;

not more than 50 metres of cable must pass between each Microphoneloudspeaker board and the Voice board.
For message recording, use the Microphone board that is nearest to the
Voice board, and temporarily disconnect all others; this will improve message quality.
When in the Telerescue mode, all Microphone-loudspeaker boards are interconnected, this permits two-way conversation between several users simultaneously.
Figure 40
Diagram for the connection of 4 OmniaVOX-MS boards to the Voice board.
OmniaVOX
125
Manual selection
The connection of several Microphone-loudspeaker boards permits simultaneous environmental listen-in on the sounds coming from several installation positions; in this way, it is possible to control various parts of the
premises at the same time, although, it is not possible to know exactly
where the sounds are coming from.
For sound tracing, carry out the connections shown in figure 41; the diagram
shows the Voice board and 4 Microphone-loudspeaker boards, and also:
a 4-Output expander, Omnia/4OUT;

a 4-Input expander, Omnia/4IN;
two Relay modules, Omnia/4R.
Furthermore, Omnia must be programmed in the following way.
All the Outputs of the Output expander must be Reserved, Bistable and
Normally Open;
Figure 41
126
Diagram for the selection of environmental listen-in.
All the Zones of the Input expander must be Immediate, Repetitive, and
Normally Open, each of them must be assigned a Voice message for
Standby status which identifies the environment they are assigned to.
Moreover, they should belong to an Area, if this is not possible, they must
be programmed as Test.
The user can enable Remote Listen-in, via telephone, by dialling 5, followed by the output number which enables the corresponding Microphoneloudspeaker Board, and then 1 for Remote Listen-in.
For example, as illustrated in figure 41, if the Output-expander address is
no. 01, its hardware outputs OC1, OC2, OC3 and OC4 correspond respectively to the software outputs no. 5, 6, 7 and 8, in order to listen-in on the
environment where the 1st OmniaVOX-MS is installed, the user must dial
505 on the telephone keypad, to enable output no. 5, and then dial 1 for
Remote Listen-in.
To listen-in on sounds detected by another Microphone-loudspeaker
Board, the user must end the Remote Listen-in phase by pressing the #
key, and then dial 405 to disable the output that was previously enabled.
If required, the user may enable Remote Listen-in on different parts of the
premises simultaneously, and by dialling 300 on the telephone keypad,
may identify the places in question (Reading of input-zone status).
Automatic selection
When certain events are verified, the Control Panel is able to select automatically, the environment required for Remote Listen-in. For example,
when an alarm occurs, it may be useful to select the OmniaVOX-VS board
situated nearest to the Zone in alarm status. In order to have this function,
follow the procedure illustrated in figure 41. However, it is necessary to
change the output programming and add some programming to the
{Event-Actions} page.
The 4 outputs used for this application must be Monostable, Normally
open and Not Reserved. The programmed On time, is the time available,
for the enabled board, for environmental Listen-in on the place of alarm.
The input connections illustrated in figure 41, enable one of the OmniaVOX-MS boards.
In the {Event-Actions} page, the Area and/or Control Panel events are
used for signalling and activation of the telephone dialler. In this way, the
zone events are free to manage the outputs. Program all the relevant Zone
events to enable the output that controls the OmniaVOX-MS board of the
environment concerned. Repeat this programming for the 4 outputs and
therefore, for the 4 environments.
In this way, when the user receives a telephone call from the telephone dialler, it is possible to enable environmental listen-in, and listen to the
sounds coming from the environment which is signalling alarm status.
OmniaVOX
127
Manual and automatic selection

Automatic management can be integrated with manual management, this
allows, when in standby status, manual selection of environmental listenin. A simple method, is to use 4 outputs for manual selection of environmental listen-in, and 4 outputs for automatic selection. Connect the outputs
in twos, one manual and one automatic, then proceed as illustrated in figure 41. Obviously, for proper functioning of automatic selection, the manually controlled outputs must be in standby status. This means, that when a
manually controlled listen-in session is over, it is necessary to place the
outputs involved in standby status.
128
OmniaTIMER
The OmniaTIMER board must be housed in the Main unit and connected
to it by means of its serial port: the latter is duplicated on the interface.
The OmniaTIMER is equipped with an interface for the direct connection of
a serial or parallel printer, for the real-time printing of events that occur or,
for the printout of the entire contents of the event logger.
Furthermore, the incorporated Timer Programmer allows time-controlled
Area arm/disarm actions, and enable/disable actions for 8 functions.
ATTENTION The times set, by means of the Timer Programmer,
are guaranteed to 30 seconds.
When Omnia engages the telephone line (indicated by a "T", above
the
icon, on the keypad display), OmniaTIMER stops the programmed actions until the line is free.
During the programming of the Omnia control panel or when Omnia
is connected to a PC via its serial port, all the actions scheduled on the
OmniaTIMER are ignored.
OmniaTIMER settings are carried out by means of the "Timer Programmer" command found in the "Programming" menu of the "Omnia" program,
and cannot be carried out via Keypad.
General characteristics
r Possibility to connect a serial printer or a parallel printer.
r Real-time printout of events and printout of entire event logger by means of
a valid command via Keypad.
r Possibility to program 2 arm and 2 disarm actions per day for each Area.
r Possibility to program up to 8 timers to enable/disable 8 events per day.
r Possibility to program different hours for different day types (working day,
day before holiday, holiday, etc.).
r Possibility, for the enabled user, to postpone the Areas automatic mode
(Overtime Request).
r Possibility to program the automatic switch over from Summer Time to
Standard Time and vice versa.
OmniaTIMER
129
Identification of the parts

The numbers in boldface in the description chart refer to the parts shown in
figure 42, unless otherwise stated. The names of the LEDs and connectors
are silk screened on the Board (see Abbreviations in square brackets).
PARTS
DESCRIPTION
[SPT] 95 Port for the serial printer connection.
96 Terminal Board for connections.
Jumper to select the port in use:
[PRN] 97
> port for parallel printer(default);
> port for serial printer.
[PPT] 98 Port for parallel printer connection.
[PC] 99 "New" serial port for PC connection.
Green LED normally ON. If this LED is OFF it indicates that
[ON] 100 OmniaTIMER is not powered: check that there is voltage between
terminals [+12V] and [ ].
Yellow LED normally OFF. If this LED is ON it indicates that the Main
[CTS] 101 unit is engaged and therefore OmniaTIMER cannot carry out the
programmed actions.
Red LED normally OFF. If this LED is ON it indicates a printing mistake:
[ER.PRN] 102
check that the printer is correctly connected and on line
Yellow LED normally ON. If this LED is OFF it indicates that the serial
[SER] 103
of the Main unit is engaged by OmniaTIMER.
[OMNIA] 104 Connector for the connection to the Main unit serial port.
105 Flat cable for OmniaTIMER connection to the Main unit.
Installation
Choice of printer
PRINTER
Parallel
Serial
A serial or a parallel printer can be connected to the OmniaTIMER. The

choice depends on cost, cable length required for printer connection to the
interface, and the printing speed. The values of these parameters for the
two types of printers are summarised in the following chart:
MAX. CONNECTION LENGTH
10 meters
40 meters
SPEED
High
Low
COST
High
Low
A parallel printer is advisable, as it has a high printing speed, however, the

average cost is higher than that of a serial printer, and it must be located
near to the Main unit.
130
Figure 42
Parts identification and installation of the OmniaTIMER.
OmniaTIMER
131
As the printing speed of the serial printer is low, it may block the TimerProgrammer for some minutes during the printout of the entire event-logger contents. However, the serial printer can be connected by a cable of
up to 40 metres and located in a more practical place for the user (please
note, that for security reasons and also because it is not equipped with signalling devices or the necessary keys for ordinary use, the Main unit
should be installed in a hidden place that is not easily accessible).
+
Serial printer
Setting
If a serial printer is used it must be set as indicated in the following chart:

BAUD RATE
1.200
Connection of
the printer
PARITY
E (even)
DATA BITS
8
STOP BITS
1
PROTOCOL
DTR/DSR
Cables fitted with connectors must be used for printer connection. Usually
these are supplied with the printers, or can easily be found in Personal
Computer shops everywhere.
These cables cannot be canalized, therefore, they must be laid between
the Main unit and the wall and left uncovered until they reach the printer.
It is possible to canalize those cables which are not fitted with connectors,
and connect them according to the following charts, and as illustrated in
figures 43 or 44 (depending on the printer to be connected).
Connection Cable
for serial printer
to interface
Figure 43
132
Interface side: connector DB9, female

3
4
5
6
Cable 4 wires + shield: the shield must be soldered to the metallic casing of both connectors
2
20
7
6
Printer side: connector DB25, male
Cable diagram for the connection of serial printer to interface.
Interface side: connector DB25, male

19
Connection Cable 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
for parallel printer
Cable 18 wires + shield: the shield must be soldered to the metallic casing of both connectors
to interface
1 2 3 4 5 6 7 8 9 10 11 12 13 14 32 31 36 1517/1930
Printer side: Centronics connector, 36 pin, male
Installation
procedure
Figure 44
Lay the printer connection cable between the place chosen for printer installation and that of the Main unit.
Fix the OmniaTIMER to the back of the Main unit, by means of the screws
supplied, and as illustrated in figure 42.
Connect the OmniaTIMER connector 104 to the Main unit connector 6, using the flat cable 105.
Position the jumper 97 according to the type of printer used:

Parallel printer>
; serial printer >
.
Insert the parallel printer plug into the parallel printer connector 98 or the serial printer plug into the serial printer connector 95 of the OmniaTIMER.
Connect terminals [+12V] and [ ] of the OmniaTIMER, respectively to terminals 3[+B] and 4[ ] of the Main unit.
Cable diagram for the connection of parallel printer to interface.
OmniaTIMER
133
Programming
The settings of OmniaTIMER are carried out by means of the Timer Programmer command in the "Programming" menu of the "Omnia" program,
as described below.
The settings are sent to the control panel via a local serial connection or
telephone; all parameters programmed from the PC are sent in the same
way.
Timer
Programmer
+
An type
This command opens the page for the settings of the Timer Programmer
and the Printer Interface parameters described below.
If these settings are to be effective, the OmniaTIMER must obviously be installed.
This indicates that the Area disarm/arm times are being programmed for
the days indicated by An Model: the initials "An" may be customized by
clicking on the Type Description button.
To select the Day Model required for time programming, select the corresponding note book, among those in the lower part of the chart:, use the
and keys to "uncover" the hidden note books.
It is possible to specify 2 different disarm times for each Area (see columns
1st Dis. and 2nd Dis.) and 2 arm times (see columns 1st Arm. and
2nd Arm.):
- times must be entered in a hh.mm. format, hh stands for the hours with
values of 00 through 23, and mm stands for minutes with values of 00
through 59. For example, if the required setting is 7:45 a.m., 07.45 must be
entered, whereas if the required setting is 5:45 p.m., 17.45 must be entered. The program will convey an error message, if an invalid value is entered.
By clicking on the Timers button, it is possible to move from the Area
charts to the Timers charts.
Tn type
In this chart it is possible to define the days indicated by the Tn Model,

both the enable (column "ON") and disable (column "OFF") times, for each
of the eight Timers managed by the Timer Programmer: the initials "Tn"
may be customized by clicking on the Type Description button.
To select the Day Model required for time programming, select the corresponding note book among those in the lower part of the chart: use the
and keys to "uncover" the hidden note books.
Times must be entered in the same format as that described for the Areas.
By clicking on the Areas button it is possible to pass from the Timer charts to
the Area charts.
Models
By means of this chart it is possible to define the days which have the
same Area disarm/arm and the Timer enable/disable times.
no.
134
Reference number cannot be changed.
Day
Month
This field is for the "Number" the day must have, in order to belong to the
Model. It may be 1 through 31 or *.
- if * is specified, the day "Number" is irrelevant for the Model;
- if a day "Number" is specified, it will not be possible to specify the Day
name;
- if an invalid day "Number" is specified, for the Month in question, when
either OK or Send is selected, the program converts it into the highest day
"Number" valid for the specific month.
This field is for the month relative to the Model days:
- if * is specified, the month is irrelevant for the Model.
Year
This field is for the year that the Model days belong to, from 1997 through
2011 or *:
- if * is specified, the year is irrelevant for the Model.
Interval
This field is for the day indicated as the start of a interval, which will end on
the day specified in the successive chart row. When this field is selected,
the Start and Stop value is automatically acquired, that is, if the Start and
Stop interval specified is valid:
- a Interval is valid only when the day "Number" of the month or the Weekday specified, is followed by a successive day "Number" or Weekday in the
successive chart row.
Figure 45
OmniaTIMER programming page.
OmniaTIMER
135
Weekday
This field is for the day "Name", that the day must have in order to belong
to the Model:
- if * is specified, the day "Name" is irrelevant for the Model;
- however, if the day "Name" is specified, it will not be possible to specify
the day "Number".
Type
This field is for the Model name:

- if no name is assigned to the Model described, it will not be stored in the
memory;
- if the row specifies the end of a Interval, this field acquires the * value, because, in this case, the Model is described in two consecutive chart rows,
and the name is indicated in the upper row.
Type Description
Opens a window, where it is possible to assign more significant names to

the Day Models for the Areas (An) and Timers (Tn) day "Types", a maximum of 16 characters is permitted. These names will automatically replace
the corresponding initials on the "Page" note books for time setting, and in
the "Type" column of the "Model" chart.
Areas
Timers
This button is for Area arm/disarm time programming.

This button is for Timer enable/ disable time programming.
Timeout-to-arm
Specifies the delay for Timeout-to-arm area no. (8 events, from no. 360
to no. 367, one for each Area) with respect to the arming times indicated
for the Area no.: if, for example, the timer programmer must arm Area no. 1
at 17:45 with a 15 minute Timeout-to-arm delay, at 17:30 event no. 360 Timeout-to-arm Area 1 [Area 001] - occurs, this warns those present in
Area no. 1 of the imminent arming. The event will end when the set
Timeout-to-arm delay expires, that is, on arming the Area no. or before if
there is an overtime request.
It is possible to specify a Timeout-to-arm delay from 0 to 240 minutes with
1 steps of 1 minute:
- If a higher value is entered, it is converted automatically to 240 minutes.
- If 0 minutes is specified, there will be no Timeout-to-arm delay.
Overtime length
Specifies the overtime delay requested via keypad, by an enabled user, by

means of the specific command in the USER MENU: if, for example, the
timer programmer must arm Area no.1 at 17:45, and a 60 minute overtime
request is made at 17.30, Area 1 will be armed at 18:45 (17:45 + 1 h), that
is, unless other overtime requests are made in the meantime.
It is possible to specify Overtime length of 0 to 60 minutes with steps of 1
minute:
- if a higher value is entered, the program converts it automatically to 60
minutes.
- if 0 minutes is specified, the overtime request will be ineffective.
Max. overtime
requests
Specifies the number of times an Area arming time may be changed: for
example, if the timer programmer must arm Area no.1 at 17:45, and Area
no.1 is set as 60 minute Overtime length with a Max. no. of 2 overtime requests, it will be possible to change the arming time on Area no.1 to 19:45
at the latest (17:45 + 2 h), any further requests will be ineffective.
136
The multiplication of the Overtime length by the Max. overtime requests

cannot result in more than 180 minutes:
- If invalid value is entered, the program will converted to the maximum
value allowed;
- if 0 is entered, the program will convert it automatically to 1;
Overtime requests affect only the arming time which immediately follows
the time of the request, all other arming times remain unchanged. For example, if the timer programmer must perform the first arming of Area no.1
at 12:45 and the second at 15:30, and at 12.30, the enabled user makes 4
1 hour overtime requests (12.45 + 4 h) the arming time will not be 16.45 as
might be expected, but at 15.30 as scheduled for the second arming time.
Standard time
This specifies when the timer programmer must put the Main unit clock 1
hour forward when passing from Summer to Standard time.
The Date must be entered in a dd/mm format, dd is for the day, with values from 00 through 31, whereas, mm is for the month with, values from
00 to 12:
- if 00 is specified for the day or for the month, the automatic increase is
disabled;
- if an invalid value is specified, the program does not allow exit from the
page by means of OK or from the Main unit programming by means of
SEND;
-the Time must be entered in a hh format with values of 00 or 01 through
23:
- if a higher value is specified, the program converts it automatically to 23,
when OK or SEND is selected ;
- if 00 is specified, the automatic increase is disabled.
Summer time
This specifies the date and the time when passing from Standard to Summer time.
Print-out
heading
Real time
print-out
Permits a 16 character max. heading, for the event logger printout.

By selecting this option, it is possible to have a real-time printout of events,
on the printer connected to the printer interface, otherwise, the entire contents of the event logger (the last 200 events) are printed when the Print
logger item in the USER MENU is selected by an enabled user.
ATTENTION When the printer interface is involved in the event printout, the timer programmer is disabled and, as the print of the whole
event logger may require some minutes, the set arm/disarm times are
postponed by the same number of minutes.
Print events
Opens a window where it is possible to specify the events to be printed, on

the printer connected to the interface: by selecting only the required
events, printout takes less time, and this reduces the time subtracted from
the Timer Programmer.
OmniaTIMER
137
Applications
The Timer Programmer permits 2 arm and 2 disarm times for each Area.
Moreover, it is also possible to specify an enable and a disable time for
each timer.
These times need not be the same every day, for this reason it is possible
to program up to 16 Day Models for the Areas and 16 Day Models for the
Timers, specifying the days in which the times are the same.
For a company for instance, it is possible to define the Models for Weekdays, Saturdays, Holidays, Summer Holidays and Christmas Holidays, in
the following way.
Weekdays
no.
Day
9
*
10 *
Month
*
*
Saturdays
no.
Day
8
*
138
Year
*
*
Interval
Weekday
Start
Monday
Stop
Friday
Type
Weekdays
*
This model refers to Saturdays: this day must be entered in the weekday
cell, whereas * must be entered in all the other cells.
Month
Summer
Holidays
no.
Day
1
1
2
15
Every weekday from Monday to Friday, independent of the Number (of the
day), Month and Year. As this represents a interval, two lines must be
used. In the first line * must be entered in the cells concerning the Day,
Month and Year, whereas, Monday is entered in the weekday cell. In the
following line * must be entered in the cells concerning the Day, the Month,
the Year, whereas, Friday is entered in the weekday cell. Finally the Interval cell, in the first line, must be selected: the words Start and Stop appear automatically.
Year
*
Interval
Weekday
*
Saturday
Type
Saturdays
If the company in question, closes for Summer holidays from 1st to 15th
August, then, a Model including all the days requiring different times must
be defined, otherwise, the Timer Programmer would apply the same times
set for the Weekday, Saturday and Holiday Models (unless it is disabled).
The Summer Holiday Model represents an interval: therefore the Start
must be specified by selecting Day 1 and the Month August on the first line
and, Day 15 and the Month August on the following line, whereas, all the
other values must be *. Finally, the Interval cell on the first line must be selected: the words Start and Stop appear automatically, indicating that the
values expressed refer to the extremes of interval.
Month
August
August
Year
*
*
Interval
Weekday
Start
*
Stop
*
Type
Summer Holidays
*
Christmas
Holidays
no.
Day
no 24
no+1 6
As seen in the Summer Holiday Model, it may be necessary to define a

Christmas Holiday Model consisting, for instance, of all the days from 24th
December of a specific year to 6th January of the following year. This
Model is similar to the previous one (Summer Holidays); however, it cannot
be programmed in the same way, due to the fact that the Timer Programmer requires the interval Start number to precede the interval Stop number, in this case, if the year is not specified, the 24th December is successive and not precedent to the 6th January. Therefore, the year must be
specified as indicated in the following chart:
Month
December
January
Year
1997
1998
Interval
Weekday
Start
*
Stop
*
Type
Xmas Holidays
*
in this case the model defines only the days from 24th December 1997 to
6th January 1998; therefore, the extremes indicated in the Year cell will require a yearly updating.
Or the interval is divided into two parts:
Xmas Holidays 1 > the Days from 24th to 31st of December, every Year;
Xmas Holidays 2 > the Days from 1st to 6th of January, every Year.
no.
3
4
5
6
Day
24
31
1
6
Month
December
December
January
January
Year
*
*
*
*
Interval
Start
Stop
Start
Stop
Weekday
*
*
*
*
Type
Xmas Holidays 1
*
Xmas Holidays 2
*
In this case, the model defines only the days from 24th December to 6th
January, independent of the Year.
1st May
no.
Day
7
1
Bank holidays: in this specific case, 1st May.

Month
May
Model Priorities
Year
*
Interval
Weekday
*
*
Type
1st May
From the examples given, it is evident that some days may belong to different Models; in this case, the times of the less frequently used model are
considered. For instance, the 1st May Model is employed only once a year,
therefore, it has a priority over the Weekday Model, which is employed 5
times a week.
OmniaTIMER
139
Timer Applications
The Timer-Programmer Timers permit automatic enable/disable of periodical functions.
For instance, a timer may be employed for the switching ON/OFF of the
heating system, of the above mentioned company.
PC Connection
For PC connection, use connector 99 of the OmniaTimer. In this case, the
Omnia serial port is shared with the OmniaTIMER and the PC with the following implications.
The PC connection has priority over OmniaTIMER connection, that is,

when a PC is connected to the serial port of the Central Unit, the OmniaTIMER cannot perform the requested actions. These actions will not even
be performed at the end of the PC connection because OmniaTIMER is restarted at that time.
When the serial port is engaged by Omnia (CTS warning light ON), the
OmniaTIMER cannot perform the set actions; in other words, if an Area is
scheduled to be armed or disarmed, a Timer enabled or disabled or an
event or the event logger contents printed, these actions will be delayed
until the Main unit frees the serial port.
140
APPLICATIONS
This chapter describes how some of the most frequent security-system applications are performed, by the Omnia system.
Fast arming
If Fast arming of some Areas is required, it is necessary to keep an Omnia
Keypad key pressed for 3 seconds. This function can be performed by using the pulse coming from the recognition of a Super key. There are 10 Super keys, one for each of the number keys. The Super-key events can be
programmed in the {Event-Actions} page and they range from no. 390 (Super key 1) to no. 399 (Super key 0).
Requirements
If the following Omnia items are used:
Event no. 390: Super key 1 [Tast.az.imm. 001];

Output no. 3: corresponding to terminal 15[OC1] of the Main unit;
Zone no. 8: corresponding to terminal 50[L8] of the Main unit.
The necessary connections are shown in figure 46 and the corresponding
programming is shown below and is divided into programming pages.
Event-Actions
Program the event no. 390 Super Key 1 [Tast.az.imm. 001] as follows:
Outputs ON: 3.
Outputs
Program the output no. 3 as follows:
Type: Monostable;
Attribute: Normally open;
Timing: On time - 1 Sec.
Figure 46
Fast arming by means of Super key.
APPLICATIONS
141
Zones
Program Zone no. 8 as follows:
Command;
Command: Only arm;
Balancing: Normally open;
Sensitivity: Standard Pulses 1;
Cycles: Repetitive;
Area: indicates the Areas to be armed, when key 1 of any keypad is
pressed for more than 3 seconds.
As a result of this programming, if key 1 is pressed for 3 seconds, the
specified Areas are armed. Super Key recognition is signalled by a long
beep on the keypad
The Zone is programmed for arming only; therefore, if the Areas concerned are armed, any fast arming operation will have no effect.
The action carried out by the output, enabled by the event generated by
the Super-Key, can also be carried out by means of a key connected to the
command Zone, as shown in figure 47.
Temporary disarming (patrol)

This is a very useful application, especially when one or more Areas are to
be patrolled at night. With this application, one or more Areas can be disarmed, for a programmed period of time, thus, allowing the watchman or
patrol squad to carry out checks without generating any alarms
Requirements
If the following Omnia items are used:
Event no. 417: Recognized user code 10 [Code 010];

Zones no. 6 and 7: corresponding respectively to terminals 44[L6] and
47[L7] of the Main unit. The connections to be carried out are shown in figure 48, and the corresponding programming is shown below and is divided
into programming pages.
Figure 47
142
Fast arming by means of button.
Codes
Program Pr. 10 Code as follows:
Description: Patrol;
Available;
Active;
Enables user menu: none;
Enable imm. action: none.
In this way the code will only be enabled for the patrol function.
Event-Actions
Program event no. 417 - Recognized user code 10 [Code 010] - as follows:
Output ON: 4.
Outputs
Program Output no. 4 as follows:
Type: Monostable;
Attribute: Normally open;
Timing: On time [patrol time + 1] Min.
Zones
Program Zones no. 6 and 7 as follows:
Command:
Balancing:
Sensitivity:
Cycles
Area:
Figure 48
Zone no. 6
Command
Only disarm
Zone no. 7
Command
Only Arm
Normally open
Standard - 1 pulse
Normally open
Low - Pulse length
[tempo di ronda] Min.
Repetitive
Repetitive
Select, for both Zones, the Areas to be disarmed for the
patrol time
Temporary disarming (patrol).
APPLICATIONS
143
In this way, after entering code no. 10 and pressing the Enter key, the Areas programmed for the patrol time will be disarmed and then automatically re-armed.
If the patrol code is entered when the patrol time is active, it will be ignored; this means, disarming of the programmed Areas cannot be extended by using the patrol code. In order to enable the patrol time again, it
must be disabled for at least 1 minute.
Management of a common Area

Figure 49a shows a situation in which access to one or more Areas (1, 2, 3
and 4) is possible, only after passing through a common Area (5). This is
typical of an office building, where more than one office is adjacent to a
corridor; access to this corridor is allowed only to authorized personnel.
It is possible for the Control Panel to arm and disarm Area 5 automatically,
according to the status of Areas 1, 2, 3 and 4, as Area 5 depends on these
Areas.
The command devices can be in various locations, therefore, to arm or disarm Area 5 from a key reader (or keypad) situated outside Area 5, the following programming is necessary.
Enable the command device (Key reader or Keypad) on Areas 1, 2, 3 and 4.

Assign a key (or code) to each user, which is enabled only for the Area the
user must have access to (1, 2, 3 or 4).
Program Area 5 (Common Area) as depending on Areas 1, 2, 3 and 4.
Figure 49
144
Management of common Area.
As a result of this operation, each user will have access to one of the Areas, either Area 1, 2, 3 or 4 and will also have access to Area 5. Area 5,
being dependent on Area 1, 2, 3 and 4 will be armed automatically when
all the Areas it depends on are armed, and it will be automatically disarmed when one of the Areas it depends on is disarmed.
The command device can also be located inside Area 5; in this case its
Zones will be programmed with an entry and exit delay.
The command devices can also be located inside Areas 1, 2, 3 and 4; in
this case, their Zones and the Zones of Area 5 must be programmed with
an entry and exit delay.
It is possible for one of the independent Areas (e.g. Area 1) to have its own
entrance, as shown in figure 49b; in which case, follow the procedure below in order to preserve common management of Area 5.
Enable the command device (key reader or keypad), located at the entrance of Area 5, on Areas 1, 2, 3, 4 and 6.
Area 6 is "virtual".
Enable the command device located on the independent entrance of Area

1 to act only on this Area.
The user operating in Area 1 must have a key reader (or code) enabled on
Area 1 and on the "virtual" Area 6. Other users should have a key reader
(or code) enabled only on their own Area.
Program Area 5 as depending on Areas 2, 3, 4 and 6.
Please note that if all Areas are armed and the independent entrance to
Area 1 is used, Area 5 arming status is still activated, because it depends
on Area 6 and not on Area 1.
In this way, it is possible to manage several independent Areas with independent entrances, provided that not more than 8 Areas, "virtual" Areas included, are used.
If the command devices are to be located inside the various Areas, it is
necessary to program the Zones relative to the Areas, with entry and exit
delays.
APPLICATIONS
145
Several outputs assigned to the same event

Sometimes, especially in noisy environments, Zone alarm signalling requires not only the siren, but also flashers placed in strategic positions. For
this purpose, it is possible to assign several outputs to the same event. In
this way, the event enables the assigned outputs, which can be Physically
distant but must be reachable by the BPI bus.
If output OCx has been assigned to a certain event, and the same event
must provoke signalling on outputs OC1, OC2, OC3, ..., OCn, it is necessary to carry out the connections shown in figure 50, and also the programming described below.
+
Zones
The output OCx and the inputs L1, L2, L3, ..., Ln, should be close together
to facilitate connection.
The Zones corresponding to terminals [L1], [L2], [L3], ..., [Ln] should be
programmed as follows:
Alarm;
Type: 24h;
Balancing compatible with the attribute of output X:
- Normally open if the output X is normally open,
- Normally closed if the output X is normally closed;
Area: all the Zones should be assigned to an Area that is not used by keys,
codes or to enable actions, this Area may be considered a Technical Area.
Outputs
The output corresponding to terminal [OCx] can be programmed according

to requirements, while the outputs corresponding to terminals [OC1],
[OC2], [OC3], ..., [OCn] should be programmed as follows:
Type: Bistable.
Figure 50
146
Multiple output event.
Event-Actions
Program the Zone alarm events of terminals [L1], [L2], [L3], ..., [Ln] as follows:
Alarm on zone (L1):

Alarm on zone (L2):
Alarm on zone (L3):
Alarm on zone (Ln):
Outputs ON
Output (OC1);
Output (OC2);
Output (OC3);
Output (OCn).
If the described connections and programming are carried out, when output (OCx) is enabled, it will generate the following events: 24h alarm on
panel, Generic alarm on panel and Generic+Tamper alarm on panel,
therefore, in order to avoid false alarms, these events must not be assigned to any action.
As a result of the described connections and programming, the signal on
output OCx will also be present on outputs OC1, OC2, OC3, ..., OCn, with
a maximum delay of 2 seconds.
For proper enabling of outputs OC1, OC2, OC3, ..., OCn, the signal should
be present on output OCx for more than 400 mS.
Multi-output event
As seen, several outputs can be assigned to the same event. By using the
hierarchical structure of events, it is possible for an event to enable several
outputs.
For example, when the Generic Alarm event (area no. or panel) or Tamper alarm event (area no. or panel) occurs, the Generic+Tamper alarm
event (area no. or panel) is also generated, as it is the sum of these two
events (see fig. 51).
Figure 51
APPLICATIONS
147
The Generic+Tamper alarm event (area no. or panel) can then be assigned to two outputs, as follows.
Event-Actions
For example, if the x and y outputs are to be enabled when the Generic+Tamper alarm on area no. event occurs, carry out the following
programming:
Generic+Tamper alarm on area no.:

Generic alarm on area no.:
Tamper alarm on area no.:
Outputs ON
Output x;
Output y;
Output y;
The structure shown in figure 52 can also be used to enable several outputs with the same event, if the Zones assigned to an Area are all of the
same type (fire, 24h or burglar).
If the outputs a, b and c are to be enabled when the Generic alarm on
area x event occurs, the following programming is required.
Zones
Event-Actions
Program all the Zones assigned to the Area as burglar (or fire or 24h) type.
Assign output a to the Generic alarm on area x. event;
Assign output b to the Burglar (or Fire or 24h) alarm on area x event;
Assign output c to all the Zone alarm events, for Zones assigned to
Area x.
Therefore, if an alarm occurs on one of the Zones programmed as Immediate type on Area x., outputs a, b and c will be enabled.
The number of outputs that can be referenced by using this system feature
depends on the number of levels in the hierarchical structure. If even more
outputs are to be enabled, refer to the application note in "Multi-output
event".
Figure 52
148
Recognition of multiple codes

If, in order to open the armoured door of a bank, 3 valid codes must be entered within 2 minutes. The connections shown in figure 53, and the programming described below are to be carried out.
Event-Actions
The Recognized user code events related to the used codes are to be
programmed as follows:
Recognized user code 1:

Outputs ON
Output (OC1);
Output (OC2);
Output (OC3).
In addition the Alarm on zone event of terminal [Ly] should be programmed as follows:
Alarm on zone (Ly):

Zones
Outputs ON
Output (OCx).
The Zone corresponding to terminal [Ly] should be programmed as follows:
Alarm;
Type: 24h;
Balancing: Normally closed;
Sensitivity: Standard - Pulses 1;
Area: it must be assigned to an Area that is not used by keys, codes or to
enable actions, this Area may be considered as a Technical Area.
Figure 53
Recognition of multiple codes.
APPLICATIONS
149
Outputs
Outputs corresponding to terminals [OC1], [OC2] and [OC3] should be programmed as follows:
Type: Monostable;
Attribute: Normally closed;
Timing: On time - 2 Min.
In addition, the output corresponding to terminal [OCx] should be programmed as follows:
Type: Monostable;
Attribute and Timing are to be programmed according to requirements.
If the described connections and programming are carried out, when output (OCx) is enabled, it will provoke the following events: 24h alarm on
panel, Generic alarm on panel and Generic+Tamper alarm on panel,
therefore, in order to avoid false alarms, these events should not be assigned to any action.
As a result of the described connections and programming, the previously
mentioned door opens when terminal [Ly] is open; that is, when terminals
[OC1], [OC2] and [OC3] are open simultaneously. These terminals are
open for 2 minutes, each time the codes they are assigned to are entered.
Therefore, these codes must be entered within 2 minutes, otherwise, there
will be an earthed output which will block terminal [Ly] and consequently,
terminal [OCx] which control door opening.
Disarming under duress

Sometimes it is necessary to signal disarming under duress, that is, when
a criminal forces a user to disarm an Area. Two possible solutions are described below.
Solution no. 1
The first option is to enable two codes to disarm Area/Areas; the first code
is normally used to disarm the Areas; the second code is programmed to
manage the Areas in the same way as the first code, but also to generate
a security call.
Therefore, in the case of disarming under duress, the second code will disarm the Areas, and unawares to the criminal also generate a security call.
If code 1 is to be used for normal disarming and code 2 for disarming under duress, carry out the programming described below.
Codes
Event-Actions
150
Enable Code 2 on the same Areas as Code 1.

Assign the Recognized user code 2 event to the requested action on the
Pulse Comm. Dialler and/or DTMF communicator, used for disarm-underduress signalling.
Solution no. 2
The second option is to program an action indicating disarming under duress, that can be detected when the super key of a keypad is not pressed,
within the programmed timeout from Area disarming.
The connections shown in figure 54 and the programming below should be
carried out.
Zones
Program the Zones corresponding to terminals [L1] and [L2] as follows:

Zone (L1)
Outputs
Type:
Balancing:
Sensitivity:
Area:
Zone (L2)
Alarm
Alarm
24h
24h
Normally open
Normally closed
Standard - Pulses 1 Low - Pulse 1 Min.
both must belong to an Area that is not used by Electronic
keys, Codes or to enable actions, this Area may be
considered as a Technical Area.
Program the outputs corresponding to terminals [OC1], [OC2]and [OC3] as

follows :
Output (OC1)
Bistable
Output (OC2)
Monostable
Output (OC3)
Monostable
Type:
Attribute: Normally closed Normally closed Normally open
Timing: -2 Min.
2 Min.
Figure 54
Disarming under duress.
APPLICATIONS
151
Event-Actions
Program the events concerned as follows:
Area no. armed:

Alarm on zone (L1):
Super key no.:
Outputs ON
Output (OC1);
Output (OC2);
Output (OC3).
In addition, assign the Alarm on zone (L2) event to the requested action
on the Pulse Comm., Dialler and/or DTMF communicator to signal disarming under duress.
As a result of the above mentioned connections and programming, if the
programmed Super key no. is not pressed for at least 3 seconds, within 1
minute of Area disarming, an action occurs which communicates disarming
under duress.
Dialler
The Omnia Dialler permits the definition of up to 32 actions which may be
specified in the {Event-Actions} page, to signal, by means of a Voice message via telephone, the start of an event and/or its end.
All dialler actions send a Voice message, selected from the 14 programmable messages available, to a group of no more than 16 Telephone
Numbers, selected from the 32 programmable numbers in the Telephone
page.
The 14 Voice messages and the 16 telephone numbers, may be combined
together and assigned to any event. These features make the Dialler function extremely versatile and useful; especially when it is necessary to send
the appropriate Voice message to the police, the Fire Brigade, the Gas
Company or the installer, and send the same message to trusted persons.
Figure 55 illustrates the parameter programming of the Dialler page, and of
those pages to which it refers.
The first page to be programmed is the Telephone page. In this page,
which functions as a telephone directory, it is possible to store up to 32
telephone numbers, each with a description that identifies the user.
These numbers may also be used by the Pulse Communicator, the DTMF
Communicator and for Teleservice.
Telephone
Program the telephone page in the following way.
Number: this field is for the telephone numbers that the Dialler must call.
In the example, the Police, the Fire Brigade, the Gas Company, the Installer and trusted persons will be dialled.
Description: this field is for the telephone number description (no more
than 16 digits) useful in identifying its user. For example: 999 Police.
Used by: after the Dialler page has been programmed, it will indicate the
directory numbers used by the Dialler.
152
Figure 55
The pages used Telephone Dialler programming.
APPLICATIONS
153
The programming of the other parameters of this page depends on the installation features, and is not relevant in this context.
After the required Telephone Numbers have been stored on the memory,
the Dialler page must be programmed.
Dialler
In this page it is also possible to define: the numbers to call for each event,
the call sequence, the messages to be sent, etc. Moreover, it is possible to
open the Messages window and Actions window from this page.
Firstly, it is necessary to define the messages in the Messages window.
r Messages: in this window it is possible to assign a description of the contents, 16 characters maximum, to the 14 messages that Omnia is able to
record.
Recording, playback and erasing of Voice messages via Keypad, requires

the installation of the OmniaVOX kit, which is available on request.
In the main Dialler page, the following parameters are to be defined:
n.: this is used in the Actions window to indicate the corresponding telephone number.
Tel. Num.: this field is for the Sequential Numbers of the telephone numbers, previously programmed in the {Telephone} page, and are the numbers to which Voice messages are sent.
Please note that these numbers do not necessarily have to follow the sequence defined in the Telephone page. However, the sequence defined
here establishes call priority. As illustrated in figure 55, the burglar alarm
message will be sent firstly to the Police, then, according to the established
sequence, to Patricia, (Summer) House, Nadia and My Mobile Phone. The
telephone number of the Police Department is dialled first, because it is top
of the priority list.
Description: This field displays the description of the number dialled. The
contents of this column may be modified in the {Telephone} page only.
Programming of the other parameters of this page depends on the installation features, and are irrelevant in this context. For a more detailed description of these parameters, see the relevant chapter.
154
As previously stated, access to the Actions window is possible from the

{Dialler} page; programming of this window should be carried out as follows.
r Actions: the parameters for the Dialler Actions are defined in this window.
A Dialler Action dials and sends the Voice message, that is assigned to
the event, to a series of telephone numbers.
n.: this is the identifier number that must be specified in the {Event-Actions}
page, in order to assign the corresponding Dialler action to the event.
The n. row specifies a Dialler action; this row and, therefore, the action are
formed by the following parts:
1...16: shows the telephone numbers that must be called among those
specified in the Dialler page. In the example, number 1 corresponds to the
Police Department, number 2 to the Fire Brigade, number 3 to the Gas
Company, and so forth.
For each action, which can be assigned to 1 or more events in the {EventActions} page, it is possible to specify which telephone numbers (1...16),
stored in the Dialler page, are to be called and which message is to be
sent. An empty cell indicates that the corresponding number will not be
called; click twice to select the numbers to be called or press ENTER on
the corresponding cell.
Message: indicates the Voice message which must be sent for the Dialler
action being programmed: by entering a number from 1 to 14 the Descr.
Message column will show the name previously assigned in the Messages window.
Descr. Action: this column is for the Action description, of a maximum of

16 characters. The descriptions are also used in the {Event-Actions} page,
in order to simplify programming.
According to the example in the figure 55, action 6 (Fuse warning +B)
sends the previously recorded "Fuse warning +B" message, to the telephone numbers identified as 7 (My mobile phone), 9 (Installer Office) and
10 (Installer Mobile).
In the same way, the action identified by number 5 (Flooding Alarm) sends
the "Flooding" event message, to the following telephone numbers: 4 (Patricia), 5 (Summer House), 6 (Nadia), 7 (My mobile phone) and 8 (Branch
Office). Please note that calls are made according to the number priority.
The examples above show how dialler actions function. However, these
actions must be assigned to one or more events in order to be activated.
APPLICATIONS
155
Event-Actions
In this page, the events are assigned to Dialler actions.
Dialler (ON/OFF): as figure 55 illustrates, in the ON and OFF columns of

the Dialler, it is necessary to enter respectively, the identifier numbers of
the actions that the Dialler must perform, when the corresponding event
occurs and ends. In order to facilitate this operation, it is possible to use
the Actions Dialler menu on the right side of the page, in the following
way.
Actions Dialler: this menu has two parts, the upper part is for the actions
the Dialler must perform when a specific event occurs, whereas, the lower
part is for the actions the Dialler must perform when the event ends. Both
the upper and lower parts show the Description of the Dialler Actions, as illustrated in figure 55, in the Actions window of the {Dialler} page.
To assign the "Warehouse Burglar Alarm" event to the Warehouse Burglary action, for alarm start, and to assign the Alarm Reset action, for
alarm end, it is necessary to:
select the event with the mouse;

open the upper part of the Actions Dialler menu and select Warehouse
Alarm;
similarly, open the lower part of the Actions Dialler menu and select
Alarm Reset.
The result of this programming will be:
the "Warehouse Burglary" message is sent to the numbers programmed

for this action (Police, Patricia, Summer House, Nadia, My mobile phone),
when the Warehouse Burglar Alarm event occurs;
when the alarm ends, the Alarm Reset message is sent to the numbers
entered for this action (Police, Patricia, Summer House, Nadia, My mobile
phone).
Similarly, according to the above-mentioned examples, actions 5 and 6 are
to be assigned to 24h alarm on area 1 (Warehouse) and Warning fuse
+B events respectively.
156
By clicking on the Events button on the Dialler actions window it is possible to see the events which provoke the Dialler action selected .
Alarm stop by means of Electronic key

It is possible to provoke an alarm by mistake (false alarm), in this case it is
necessary to stop the outputs (e.g. Sirens), and also the calls generated by
the alarm.
An easy way to stop a false alarm is to use a valid Electronic Key, that is
enabled on the Area in Alarm status.
When a Zone Alarm (Events from 1 to 160) or Area Alarm (Events from
161 to 208) occurs, it is possible to stop the event by inserting a valid Electronic key into a Key reader that is enabled on the Area in alarm status.
This operation stops the outputs that, for example, are connected to Sirens
but does not clear the telephone calls generated by the alarm event.
In order to stop outputs and clear calls, by means of an Electronic key, the
following programming must be carried out.
Introduction
Using the following Omnia objects:
Event no. 255: Valid key on area 1;

Zone no. 6: corresponding to terminal 44[L6] of the Main unit.
The connections to be carried out are those illustrated in figure 56; following is the relative programming, which is divided into programming pages.
Event-Actions
Program event no. 255 - Valid key on area1 - in the following way:
Outputs ON: 4.
Outputs
Program output no. 4 in the following way:
Type: Monostable;
Attributes: Normally closed;
Timing: On Time 1 Sec.
Figure 56
Alarm stop by means of Electronic key.
APPLICATIONS
157
Zones
Program Zone no. 6 in the following way:
Command: Clear call queue;

Balancing: Normally closed;
Sensitivity: Standard;
With this type of programming, by inserting a valid Electronic key, enabled
on a group of Areas, into a Key reader enabled on the same group, all
alarm telephone calls will be cleared and all the Alarm events will be suspended.
+
+
+
158
If alarm conditions persist, after the Electronic Key has been extracted, signalling of Alarm status will restart as programmed, (output activation, telephone calls, etc.).
The suspension of an alarm event, by means of a valid Electronic-key, is
possible only for Zone (Events from 1 to 160) and Area (Events from 161
to 208) alarm events, and not on the Panel alarm events; this is because
the Electronic keys are nor enabled to operate on Panel events.
If both Area and Control Panel alarms are enabled on the same output,
that is, Generic alarm on area no. and Generic alarm on panel, and
both alarms are active, the insertion of an Electronic key will stop the Generic alarm on area no. event, but not the Generic alarm on panel
event; therefore, the output (e.g. Siren) will remain active.
The procedure shown in this paragraph suspends the alarm event and,
therefore, stops any assigned outputs, but it does not clear the alarm
memory. In order to do this, the command Alarm reset in the Keypads
USER MENU must be used. However, the alarm memory will be cleared
automatically, when the Areas are next armed.

Omnia Installation Manual

Uploaded by

Copyright:

Available Formats

Omnia Installation Manual

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Omnia Installation Manual

Uploaded by

Copyright:

Available Formats

ATTENTION The OMNIA 2.

1 software release or successive release

via Florida - Z.I. Valtesino

2.0 version update and new features . . . . . . . . . .

Key reader and Electronic key . . . . . . . . . . . . .

Input and Output expanders . . . . . . . . . . . . . .

BPI device connection . . . . . . . . . . . . . . . . . .

Bus BPI length limitation . . . . . . . . . . . . . . . .

Alarm sensor connection . . . . . . . . . . . . . . . .

Balanced tamper-line connection . . . . . . . . . . .

Control-panel General events

Expandable Multifunction Control Panel Omnia

Parameters to be programmed by the installer . . . . .

Parameters to be programmed by the user

Programming from local PC

Programming from PC via telephone . . . . . . . . .

Default setting . . . . . . . . . . . . . . . . . . . . . . 100

General rules for INSTALLER MENU use

View logger . . . . . . . . . . . . . . . . . . . . . . . . 107

Telephone-number Programming . . . . . . . . . . . 112

Electronic keys . . . . . . . . . . . . . . . . . . . . . . 117

Firmware release . . . . . . . . . . . . . . . . . . . . . 122

General characteristics . . . . . . . . . . . . . . . . . 129

Fast arming . . . . . . . . . . . . . . . . . . . . . . . . 141

Solution no. 1 . . . . . . . . . . . . . . . . . . . . . . 150

Expandable Multifunction Control Panel Omnia

Interactions among Inputs, Outputs and Telephone-dialler actions, whether

The telephone dialler manages up to 32 telephone numbers.

The OmniaVOX board offers a telephone-dialler function, which can dial 16

The optional Timer-programmer board provides a wide range of functions

Expandable Multifunction Control Panel OMNIA

r Each system object (Zones, Keypads, Key readers, Codes, Electronic

Omnia can manage up to 16 input expanders, each equipped with 4 Zones

This is an optional board for automatic management of the systems and

The management software in Windows environment will prove to be an

A 5 A capacity power-station is available for connection to the bus, this

Expandable Multifunction Control Panel OMNIA

The following are the Omnia system items.

8-Zone Control Panel with Control Keypad and 1 A linear power-supply.

4-input expander module.

4-output expander module.

Voice function board.

Microphone and loudspeaker for environmental listen-in.

Recess Key-reader model TICINO magic.

Recess Key-reader model TICINO living.

Recess Key-reader model TICINO international.

Recess Key-reader model TICINO light.

Recess Key-reader model GEWISS.

Recess Key-reader model GEWISS playbus.

Recess Key-reader model GEWISS noir.

Recess Key-reader model DELTA.

Recess Key-reader model DELTA noir.

Recess Key-reader model VIMAR idea.

Recess Key-reader model VIMAR bianco.

Recess Key-reader model AVE.

Recess Key-reader model AVE noir.

Wall mounted Key-reader.

4-relay module for the output expanders.

The Omnia system.