EIB/KNX Data - EIBMARKT® GmbH Holding

© EIBMARKT GmbH, 1997-2005 

www.eibmarkt.de 

info@eibmarkt.de


Topic overview: 

English - Manual 4 

Introduction 6 

Preconditions 8 

Examples of applications 12 

User manual 15 

Elvis structure 16 

Installation 19 

Start up and terminate 21 

Operation 23 

Administration 27 

Diagnosis 29 

Terminal 30 

Error messages 31 

Appendix 32 

Installation 33 

Project software 35 

Basic Version 36 

Load project... 37 

Datapoints 40 

Datapoint groups 43 

RS232/USB-Port 45 

Datapoint Requests 49 

User management 50 

Alarm management 54 

Message ports 56 

Message recipients 58 

Messages 59 

Professional Version 60 

Support 64 

Navigation 65 

Start screen 67 

Burglar alarm system 71 

Purpose 72 

Features 73 


Topology 80 

Central terminal 82 

Alarm outputs 88 

Reference contact 91 

Inputs (contacts) 93 

Inputs (detectors) 96 

EIB/KNX Data 101 

Info-Alarm-Message 109 

Purpose 110 

Features 111 


Function description 114 


Outside lighting matrix 126 

Purpose 127 

Features 129 




Operating Console 144 

Purpose 145 

Page 1


Features 146 




Reminder function 159 

Purpose 160 

Features 161 




4-Side blind automatics 170 

Purpose 171 

Features 173 




EIB/KNX Blind JA001 184 




EIB/KNX Inputs 192 

Climate Console 193 

Purpose 194 

Features 195 




Media Console 209 

Scenario-Manager 210 

Purpose 211 

Features 212 




Audio Console 223 

Purpose 224 

Features 225 




Sensor System Toolbar 235 

Purpose 237 

Features 238 




Time Switches 246 

Purpose 247 

Features 248 




Weather station / sensors 255 

Purpose 256 

Features 257 




Central Command Terminal 267 

Purpose 269 

Page 2


Features 270 




Page 3


English-Manual 

Version 05/10 


Page 5


Introduction 

How much the software costs? ---> Click here...! 

Unique visualization package can be easily adapted to the 

environment by the user – even without programming 

EIBMARKT GmbH has put a new generation of their visualization software package IQHOME.NET V2.4.xxx, former „ 

Genius Modular“, on the market. 

EIBMARKT GmbH has put a new generation of their visualization software package 

IQHOME.NET V2.4.xxx, former „Genius Modular“, on the market. 

>>IQHOME.NET is unique because it represents the only visualization tool at a reasonable 

price that can be used without disposing of any programming knowledge Equipped with a „Server Configurator“ in its Basic version the 500 available 

communication objects (group addresses, bus connections, protocols, users etc..), bus 

connections/protocols etc. are managed). Thus, all project modules provided are ready for 

operation within a relatively short time.


IQHOME.NET can be installed on any standard PC (also fanless design PCs or pannel PCs with 

touch) with 32 Bit Microsoft operating systems (NT, 2000, XP). User release is provided by a 

hardware dongle (USB or Parallel) which permits independence of the users and installation 

of the software as often as they like. 

According to Mr. Labahn most visualization software consists of complex program languages 

and can often be modified by programmers only. 

IQHOME.NET is modular and open. All program modules provided can be put into operation 

using a simple „Server Configurator“ (Basic version). By means of a visualization interface 

all module parameters are adapted online to the application conditions. 

Thanks to the Professional version IQHOME.NET is open and can be viewed completely, 

reprogrammed, modularly extended and graphically modified by users who dispose of the 

respective knowledge. Extension possibilities are almost unlimited. The extra charge for the 

Professional version is approx. EUR 300.00. It can be ordered separately at any later time. 

With ©IQHOME.NET you buy a valuable product that incorporates many years of expertise 

and represents functionality and design. The functions and designs included in ©IQHOME.NET 

are individual developments of EIBMARKT GmbH (calculations, scripts, programmings, 

graphics) and are available in the project software ELVIS only if ©IQHOME.NET is used. 

By opening a physical medium (CD-ROM, DVD, or other medium) or by downloading © 

IQHOME.NET & ELVIS files and their use the buyer accepts the special contract and license 

conditions. 

Do not forget to fill in and return the license certificate/s. Otherwise you are not entitled to 

updates and support! 

-o--o--o-- 

Page 7


Preconditions 

Es sind zwei verschiedenen Versionen verfügbar: 

(Basic) und (Professional) 

©IQHOME.NET is always delivered with at least one license for the runtime software, LAN 

operating terminal (local or to be used in the network) and 500 communication objects (to 

enter the group addresses) as well as, depending on the bundle version, with a limited ( Basic 

) or fully applicable (Professional) project software, if you have not made another selection. 

Both versions can be ordered either with or without Support Service. The upgrade for the 

project license from Basic to Professional must be ordered directly at IT GmbH 

(www.it-gmbh.de). 

The ELVIS project software (Professional) must be ordered directly at IT GmbH 

(www.it-gmbh.de). This is due to the specific license rights. Purchase of a project software 

full license must be proven (by sending the invoice number of IT GmbH by mail). Only then 

you will receive the key to release the full project version of IQHOME.NET. 

©IQHOME.NET is based on the Profi-Software ELVIS (IT-GmbH). 

Using the Professional Version with IOCOMP control elements the project engineer has full 

access to all possible project data of the database and the operating terminal. In its Basic 

version use of the supplied project software is limited. The difference between this version 

and the Professional version is that there is no project access to the operating terminal 

(visualization). Thus, in the Basic Version the visualization cannot be extended. The 

Professional version is recommended for professional users who dispose a of lot of 

experience. 

With regard to content and function both versions are equal in ©IQHOME.NET. 

In its Basic version the project software cannot access the visualization surface. This version 

is recommended for non-professionals, Standard EIB/KNX users (It is always possible to 

upgrade Basic to Professional). In the Basic version access to the database includes the 

following: 

� Manage data points (their project-specific group addresses) 

� Communication objects cannot be deleted or added 

� Edit data point text, data point group 

� Data point connections, communication ports (COM interfaces, bus protocols etc.) 

� Data point requests (cyclical, demand, run-up etc.) 

� Add users, user groups, grant rights etc. 

� Define alarm data points and their characteristics etc. 

� Define message connections and their characteristics etc. 

� Define messages and their characteristics etc. 

Thus, an immediate start and use of ©IQHOME.NET is possible within a very short time and 

without any problems. Similar to the ETS you just fill in your group addresses and adjust the 

EIB connection and the protocol type (BCU, FT1.2) and off we go. If you want to make 

comprehensive modifications or extensions later, you can order an upgrade to Professional at 

Page 8

any time. 


Hardware preconditions (minimum requirements & recommendations): 

1. 

©IQHOME.NET is a software and consists of several program modules. The software can be 

installed on any standard PC, Design PC (www.hushtechnologies.net), Server or Panel PC 

incl. Touch with 32-Bit-Windows operating system (XP, 2000, NT) and the following 

minimum requirements to the hardware: 

� IP3/CELERON, 1Ghz, 256 MBRAM, 16 MB graphics board with resolution 1024x768 Pixel 

(XGA) True Color (32Bit), RS232 interface or USB and visual display unit (Monitor, 

Touch, Beamer etc.). 

Recommendation: 

� IP4/CELERON, 3Ghz, 512 MBRAM, 32 MB graphics board with resolution 1024x768 Pixel 

(XGA) True Color (32Bit), RS232 interface or USB, network controller, sound board and 

visual display unit (Monitor, Touch, Beamer etc.). 

2. 

The PC used must be connected to the EIB/KNX bus by means of a communication interface 

RS232 or USB, e.g. JUNG 2130, 2130 USB or 2130 USB REG, to ensure that the runtime 

software (process server with ©IQHOME.NET database) has a bidirectional access to the EIB 

bus system to transmit the data to the operating terminal (visualization) and vice versa. 

INFO: 

There is a multitude of options for central visualization and operation such as a touch screen 

monitor (from 15") parallel to the standard PC with the operating terminal (visualization © 

IQHOME.NET), that has an elegant and fashionable stainless steel design and can be used as 

concealed operating panel (up to 100 m from the PC with 2 pcs. Cat5 lines and 

Line-Extenders). 

Example Touchscreen 17" 

or 

Example Touchscreen 15" combined with Panel PC 

Another option is the integration in a concealed combined PC-Touch with screen types of 

15"-17". Another interesting multimedia possibility to use ©IQHOME.NET would be the 

integration in a fancy Hush Design PC (fanless) for the living room. 

Page 9


www.hushtechnologies.net 

The ©IQHOME.NET operating terminal (visualization) can also be called from another PC 

integrated in the network. To do so, you will need a network controller. 

EIBMARKT GmbH special: 

Ref. No.: N510000_IQs 

(To the input in the search mask under www.eibmarkt.com) 

Manufacturer: EIBMARKT 

©IQHOME.NET 

Intelligent EIB/KNX visualization software package for your house, incl. communication 

server for EIB/KNX! 

Product version: 500 DP Special Edition (DP= data points / communication objects) with 

USB licence dongle. The bundle is licensed for max. 1 project with a runtime licence for a 

maximum of 500 communication objects (each object can be combined with several group 

addresses [up to 255 characters], see data point list in Download center) as well as 1 unit 

LAN operating terminal and includes no support, incl. project planning software "Server 

Configurator" to manage the EIB/KNX communication objects (group addresses), bus 

connections, protocols, users etc.. 

Design PC [silver] as communication server for EIB/KNX visualizations, completely fanless 

for continuous operation. Not only high-quality and exquisite design but also extremely silent 

(fanless). Depending on equipment and type, this system combined with IQHOME.NET 

represents an absolute highlight for intelligent lifestyle, multimedia communication and a 

variety of functions! Being the size of a normal DVD player, this device can easily be 

integrated into an existing multimedia system or used as additional separate working 

terminal. In connection with IQHOME.NET and a LCD/TFT television and/or separate touch 

screen or standard monitor it is a strong communication console. (provided DVI or VGA 

connection with 1024x768 to board and TV) 

The communication server as integrated component of each EIB/KNX system can be 

extended to a complete management & multimedia system. However, this basic 

configuration already represents a sophisticated equipment optimized and tested for the 

Page 10


application of ambitious EIB/KNX communication server solutions such as IQHOME.NET. 

Hush Mini ITX PC system fanless, consisting of: VIA EPIA MII 12000 Board 1,2GHz incl. 

CardBus Controller Type I/II and Compact Flash Slot, integrated 32MB VIA Castlerock 

AGP onboard graphics board (max. 1280x1024 Pixel), 1x DIMM socket DDR 512 MB, max. 

1GB interfaces onboard: 2x USB 2.0 Ports, 1x IEEE 1394, S-Video out, 1x RCA Port, 6 

channel audio VT1616, 10/100 Base-T Ethernet LAN Adapter VIA VT6103, serial, mouse and 

keyboard connection, 40GB Seagate hard disk 7200 RPM, Teac CD ROM drive SlimLine, 

Hush Mini ITX aluminium case completely fanless, 90 Watt ext. power supply unit fanless, 

Microsoft XP Professional Multilingual pre-installed, MS Works Suite 2005, Computer 

Associates eTrust Antivirus v7.1 OEM Edition for Windows. 

-o--o--o-- 

Page 11

Example version 1: 



Examples of applications 

Page 12



Page 13


-o--o--o-- 

Page 14

1 Welcome 

1.1 Introduction 


User manual 

Congratulations on purchasing Elvis, a very efficient visualisation system for modern building 

system technology. This manual describes the main program parts, their installation and 

operation. In order to understand the contents, knowledge of the use of current Microsoft 

operating systems is required. 

1.2 Conventions 

The following conventions were used for this manual: 

Bold print either highlights important terms, denotes a menu command or pressing a 

button. Italic print indicates a variable text, e.g. Project file indicates that the name of your 

project file is mentioned here. > and >> The symbol > in a brief description denotes an 

operational sequence. In 

front of the sequence symbol > there may be a site specification e.g. main menu or context 

menu. 

Example: main menu > Edit > Properties properties page > General means that in the 

main menu you should first select the Edit menu 

command and in it the Properties command, then proceed in the dialogue which has 

opened up to the General properties page. 

If a double mouse click is necessary the sequence symbol will be doubled >>. The terms 

left/right mouse button refer to the standard W indows setting. Screen images and operating 

sequences refer to a Windows 2000 operating system. If you use another operating system, 

your display or operation may deviate from the illustrations in this manual. 

1.3 Latest information 

Information that could no longer be included in this manual may possibly be found in a 

readme file in the installation directory. Announcements, tips, answers to FAQs as well as 

current Elvis documentation may be found in the Internet: http://www.it-gmbh.de. 

1.4 If you require further help 

If you have queries about this product please contact the designer of your Elvis visualisation. 

Please read the diagnosis and error messages chapter first. 

-o--o--o-- 

Page 15

2 Elvis structure 

2.1 Modules 


Elvis structure 

In Elvis not all jobs are performed by a single program, instead the various tasks are 

completed by several different modules (program parts). The modules may be flexibly 

distributed in networks. 

2.1.1 Elvis terminal 

The terminal module features a user-friendly graphic user interface to display and change 

the system status. The name of this module is Elvis terminal. The number of Elvis terminals 

that may be started simultaneously is only limited by your license (see Software protection). 

The application name is: elvisrun.exe. 

2.1.2 Elvis process server 

The central module contains a process image (the current process values). As such it can 

inform the command modules about the current system status at any time. Moreover, the 

central module can further process the process data in the form of calculations, perform 

schedules, create records and issue messages. The central module is called the Elvis 

process server. The application name is: elvissvr.exe. 

2.1.3 Ports 

These connection modules supply the communication between the Elvis process server and 

the processes and are called bus connections. Possible servers for bus connections are: 

Elvis EIB Port (for EIB access, library: elvisei3.dll) 

Elvis System Port (for system resources, library: elvissys.dll) 

Elvis Simulator Port (for simulation of all ports, application: elvissim.exe) 

Elvis Custom Port (serial scriptable port, library: elviscpd.dll) 

OPC Server (for LON, Profibus etc) 

All servers with the exception of the OPC server are supplied with Elvis. The latter may be 

obtained from other suppliers. The bus connections required in the project are automatically 

started on the Elvis process server start-up and are also closed when it is closed. OPC 

servers may be an exception to this. 

2.1.4 Message ports 

These connection modules supply the communication between the Elvis process server and 

the output devices for messages and are called message ports. Possible servers for 

communication are: 

ElvisMsg SMS Connection (SMS/Pager services, library: portsms.dll) 

ElvisMsg SMTP Connection (Email, library: portsmtp.dll) 

ElvisMsg MAPI Connection (Email and fax, library: portmapi.dll) 

ElvisMsg Print Connection (output on printer, library: portprint.dll) 

ElvisMsg TAPI Connection (Voice, library: porttapi.dll) 

ElvisMsg File Connection (File, library: portfile.dll) 

Special settings must be made on the computer for some servers or special hardware (e.g. 

modem) and applications/drivers be featured: 

ElvisMsg SMS Connection ->Modem, service configuration with MMCfg.exe 

ElvisMsg SMTP Connection 

ElvisMsg MAPI Connection -> MS Exchange / Outlook / other MAPI suppliers 

Page 16


ElvisMsg Print Connection -> printers (e.g. addressable via LPT1) 

ElvisMsg TAPI Connection -> Voice modem that supports TAPI2 

ElvisMsg File Connection 

The required message port servers are started and closed automatically as necessary. 

2.1.5 Administration console 

Configuration settings for users, bus and message ports may be made via the administration 

console. The console document is: ElvisAdm.msc. 

2.1.6 Remote server control 

The remote server control is used to check the status of the process server and its 

components, display the logged-in users as well as start and close the process server 

(remotely). The database may also be replaced via the remote server control without losing 

the current settings (e.g, switching times in the schedules). The application name is: 

elvisrsc.exe. 

2.1.7 Elvis debugger 

The debugger may be used to display and change the process image contained in the 

process server and to examine process server calculations (see Elvis debugger). The 

application name is: elvisdbg.exe. 

2.1.8 Elvis runtime 

The process server, the bus connections and the terminals are called Elvis runtime. The 

module used to create the visualization is called the Elvis developer. The Elvis developer is 

not part of the Elvis runtime. 

2.2 Files 

2.2.1 Project files 

The data for the terminals, i.e. user interfaces with drawings, pictures and control elements 

are stored in the project file. This project file has the file extension „iep“ (i = IT GmbH / e = 

Elvis / p = project). The data for the process server, i.e. the datapoints, schedules, history 

and requesting intervals, calculations etc. are stored in a database. This database has the 

file extension „db“. To access the database the database manager 

„Sybase SQL Anywhere Database Engine“ is used. The database manager is started and 

closed automatically by the process server. The Elvis developer is used to create and change 

the project file and database. 

2.2.2 Protocol files 

Three different protocol files (ending: „elf“ = Elvis Log File) may be created, administered 

and used. They are stored in the log directory. Whether protocol files are created or not 

depends on the project planning. Protocol file names are generated automatically. The file 

name format is: xyyyy.elf. The x denotes the protocol type (A, H, S), the yyyy an 

alphanumerical counter (0001 to zzzz - thus max. 1,679,616 files). The alarm files (A = 

Alarm) contain the time, datapoint names, alarm status and if necessary the user who has 

acknowledged the alarm along with their comments. The history files (H = History) contain 

the time, datapoint name, its property and value. 

The system files (S = System) contain the time the user logged in and out. All information in 

the protocol files is included as binary data. Thus, the protocol files are protected against 

manipulation and very compact. New protocol files are created regularly after 24 hours as 

well as on starting the process server. If a protocol file becomes larger than 256 Kbyte a new 

Page 17


file is also commenced. The protocol files may be opened by the protocol viewer, viewed and 

exported as a csv file. The current files in each case are opened by the process server. If 

their contents are to be viewed, new files must be created. To do so, please use the remote 

server control (> Properties > General) 

2.2.3 Diagnosis files 

elvissvr.log und elvisrun.log files may be created for the diagnosis of the process server and 

terminal. These files are only required for error location. The diagnosis chapter describes how 

diagnosis files are created. 

-o--o--o-- 

Page 18

3 Installation 

3.1 Software protection 


Installation 

One dongle is required for each runtime license regardless of how many terminals are 

featured. The dongle is simply plugged into the PC on which the Elvis server is run. How 

many datapoints are maximally possible and how many terminals may be operated 

simultaneously by the server is entered in the dongle whereby the number of terminals 

installed in the network is immaterial, only the active terminals (= floating licences ) count. 

Special devices such as the debugger or remote server control are not counted here and may 

always be started. 

The installation of the Elvis runtime also includes that of drivers for the dongle 

(=WIBU-KEY). The information in the WIBU-KEY may be read and also changed via these 

drivers. To do so use the control panel of your operating system. If you acquire additional 

terminals the information in the dongle may be updated by email. 

3.2 Process server installation 

3.2.1 Installation 

To install the process server simply install the entire Elvis run time including the debugger 

on your computer. Doing so you also install a terminal which you are bound to need for test 

purposes. In addition to installation the project database (*.db) must be copied to the 

computer on which the process server is installed. 

3.2.2 Configuration for access by network 

In order to register terminals with the process server via a network, settings for DCOM must 

be performed. Start the DCOM configuration (as administrator of your computer) by: 

Start>Execute... > Open: dcomcnfg > OK 

The following settings must be checked and set: 

Activate DCOM on the computer: 

Standard properties: activate DCOM on this computer 

Configure the security settings for the process server: 

Application: Elvis Server > Properties... 

General: Authentication level: (none) 

Security: use standard access authorisations 

Security: use user-defined start authorisations 

Process... > Allow anyone to start 

Determine a specific user under whose account the Elvis server should run: 

Identity: this user User: 

3.2.3 Configuration of ports for bus access via network 

If bus ports (e.g. Falcon) are to be accessed via the network, their DCOM-setting should be 

performed analogously to the Elvis process server settings. 

3.3 Terminal installation 

To install a terminal just select the equivalent option during setup. In addition to installation, 

the project file (*.iep) must be copied to the computer in which the terminal is installed. 

3.4 Uninstall 

Page 19


To uninstall the Elvis runtime use the Windows installer (control panel > software). 

-o--o--o-- 

Page 20


Start up and terminate 

4 Start up and terminate 

4.1 Start menu 

Default entries in the start menu/programs/Elvis are created for the process server, terminal 

and administration console modules during installation. 

4.2 Shortcuts 

Shortcuts may also be created for the process server and terminals to permit user-friendly 

module starting. As link target besides the name of the module the file to be opened 

(database or project file) may also be specified. 

Example for the terminal: 

Link>Properties>Link>Target: 

D:\Programs\Elvis\ElvisRun.exe D:\projects\.iep 

4.3 Process server 

4.3.1 Start up 

If the process server is started via the start menu an open file dialogue is displayed to 

specify the database. Once specified, the database manager (SQL Projectname) and the 

process server (two gear wheels) are indicated in the symbol bar. Only one process server 

should always be started on a computer. Note: a process server may load and administrate 

several projects (databases). This should not be used in practice. 

4.3.2 Command line parameters 

If the process server is started via Start>Execute... or a shortcut, command line parameters 

may be specified: 

/regserver -> COM registration 

/install -> Registration as service 

/unregserver -> Unregistration of the COM and service registration 

If the process server is started as a service, it features no user interface. The database is 

specified via the administration console or manually registered in Windows: 

HKEY_LOCAL_MACHINE\SOFTWARE\IT GmbH\Elvis\ElvisSvr\Database = Databasepath 

4.3.3 Terminate 

The process server may be terminated via the context menu (click symbol with right mouse 

button) or the remote server control may be opened. 

To terminate the process server the user name and password must be specified. Not every 

user is authorized to terminate the process server. 

4.4 Terminal 

4.4.1 Start up 

W hen the terminal is started via the start menu an open file dialogue is displayed to specify 

the project file. Once specified a log-in dialogue is opened for logging into a process server. 

Here the user name and password must be entered. The terminal may be protected against 

unauthorized closing, to do so set „password must be specified to close“. 

4.4.2 Logging into a non-local process server 

Page 21


If the process server has not been started locally (on this computer) the computer on which 

the process server runs must be additionally selected (computer name or IP address). 

Depending on the user group (user profile) users have various rights to open pages as well 

as to view and change status, schedules, histories. The user groups are created by the 

visualization designer. 

4.4.3 Command line parameters 

If the terminal is started via Start>Execute... or a shortcut, command line parameters may 

be specified: 

/regserver -> COM registration 

/mdi -> terminal with several pages (multiple document interface) 

/k -> full screen image (kiosk mode) 

/nologo -> start without banner (splash screen) 

/s=computername or IPaddress -> if process server not local 

/u=username 

4.5 Remote server control 

The remote server control is started via the start menu (Start > Program > Elvis > Remote 

control) or if the process server is started locally via the process server symbol (Context 

menu > Status...). 

Note: the remote server control is not required in normal operation. 

-o--o--o-- 

Page 22

5 Operation 

5.1 General 


Operation 

The Elvis terminal is used to operate the visualization. The terminal indicates: 

a main window with title bar 

the menu bar 

the symbol bar 

the status bar 

the operating range within which the project planner’s pages are displayed 

The display of these elements may be set via the view menu options. 

5.2 Terminal menu commands 

5.2.1 File menu 

Log on as... By entering a user name and password another user may log on. Optionally a 

password may be requested when the new user wishes to log off. Open page... A specific 

page may be selected and opened from the page list. Print... Prints the current view. Page 

display Print preview 

Print setup... Close 

5.2.2 View menu 

Symbol bar display or hide the symbol bar 

Status bar display or hide the status bar 

Alarm bar display or hide the alarm bar 

Full screen change to full screen mode 

Update update the display 

Options...> Alarm determine the terminal reactions when an alarm occurs 

Options...> Diagnosis activate and determine the scope of the terminal diagnosis 

5.2.3 Help menu 

About... display information (especially version information) on the terminal and system. 

5.3 Page structure 

5.3.1 General 

In the main window graphic elements, images and controls are displayed on pages created 

by the project planner. Additional operations such as changing to another screen page or 

dialogue window may be planned. Only one screen page at a time is displayed as default. 

5.3.2 Graphic elements and pictures 

The project planner may have created graphic elements (vector graphics) or embedded 

pictures in the pages. These are used for design purposes. The graphic elements are depicted 

by the Elvis terminal. The embedded images (e.g. BMP, JPG, GIF formats etc.) are depicted 

via OLE (object linking and embedding). To display these elements programs are required 

that are not supplied with Elvis, but for common formats are in 

most cases installed and registered on a PC. 

5.3.3 Controls 

Page 23


A control is an element that permits the display and change of data point values in the 

terminal. Controls are buttons, analogue inputs, status displays, analogue outputs, digital 

tools, x/t writers, text elements, video image displays or schedules. 

5.3.4 Change page 

Screen pages may contain elements by means of which you may jump to other screen 

pages. In order to perform such a change, click the appropriate element with the mouse. In 

order to change to a specific screen page execute the following command Open File or click 

the button in the symbol bar. The Open page dialogue will be displayed in which you may 

select the screen page you wish to activate. Via the button you may jump between the last 

two screen pages displayed. If you press function key F5 or the button the screen page 

currently displayed will be 

5.4 Alarm list 

The alarm file entries (see 2.2.2) are displayed (see view menu for opening) in the alarm 

list. You can filter which alarms are to be displayed: 

all: All alarm messages are displayed in the list. 

active: Only currently active alarm messages are displayed in the list. 

unacknowledged: Only unacknowledged alarm messages are displayed in the list. 

when: Date from which point the entries are displayed. 

The following symbols are used to display the alarm status: 

the upper limit value has been exceeded 

the lower limit value has not be reached 

the alarm has been acknowledged 

the value is (back) in the valid range 

In addition to that, the time and a designation are specified in the list. In case of 

acknowledgements the user is also specified and possibly the acknowledgement comments. 

Alarms may only be acknowledged as long as the alarm is issued. Double click on an alarm 

in the list to open the dialogue for acknowledgement. Comments may be entered here. 

5.5 Schedules 

5.5.1 General 

A schedule effects the change of datapoint values to specified times at specified values. W ith 

Elvis all manner of variables (buttons, values, texts etc.) may be changed via schedules. The 

project planner determines which datapoints may be changed by a schedule. The times and 

values are determined by the user. The switching times and values for the datapoints are 

stored centrally in a database and may be accessed from each terminal. Schedules are also 

subject to user administration supervision and may only be viewed and changed with the 

appropriate authorization. 

Schedules are day-based. At midnight all schedules for the new day are started. 

Three types of day are differentiated: 

Page 24


Weekday is a day on which the respective default schedule for the day (Monday to Sunday) 

is to be started. Special date is a special date on which each year the same special schedule 

is to be started. It will be a fixed date or a date relating to Eastertide. Special day is a special 

day on which once only a particular special program is to be started. The default and special 

days are determined in the schedules respectively. These 

specifications do not influence other schedules. The special dates are determined via the 

administration console and apply to all schedules. Several special dates may also be grouped 

together there. 

5.5.2 Schedule control 

The schedule control (ElvisScd.ocx) is used to enter and change the required values at the 

respective time. A schedule control element may be opened via the schedule symbol. 

The schedule control element displays a calendar by means of which the day is selected. The 

selected day is shaded in grey. In the example the 8th of January 2005 has been selected. 

Underneath the required values may be entered under the switching times for the listed 

datapoints. By entering or changing values a special day is first of all created. If you only 

wish the entered value to be on this day you have finished. You have 

created a special day. Special days are displayed in bold in the calendar. If you wish the 

entered values for this week day or other week days to be a default, actuate the „Define as 

standard Schedule...“ button . The required week days may now be entered in a dialogue 

window. The special day thus becomes a standard day. If you also wish to determine the 

entered values for other days, but not related to weekdays, actuate the „Copy schedule..“ 

button. You may select the days that are to be identical in a dialog window with a calendar. 

By dragging the mouse a block of several days may also be selected. If you wish to put back 

a special day a standard day actuate the „Return to standard 

program“ button. If you have made changes to the current day on closing the control 

element you will be asked whether the schedule for the present day is to be restarted. If you 

wish so, the value immediately before the current time will be set for each datapoint. 

Telegrams may also be sent in this way. 

Page 25

5.6 Histories 

5.6.1 General 


A history effects the cyclical storing of values in files (see: Protocol files) . W hich values are 

recorded as well as the time intervals between recordings is determined by the project 

planner. The data is centrally stored with the time in protocol files (see 2.2.2) by the process 

server and is accessible from each terminal. The histories are subject to user administration 

supervision and may only be viewed with the appropriate authorization. 

5.6.2 History control 

The history control (ElvisHis.ocx) is used to display the recorded values. The display may be 

changed via a symbol bar. 

� 

Button functions: 

Left cursor: scroll back (shifts the display back in time by approx. 2/3) 

Calendar: day selection 

Right cursor: scroll forward (shifts the display forward in time by approx. 2/3) 

Graph: graphical illustration 

Table: tabular illustration 

Pen: for online / offline control element change (the history itself cannot be interrupted) 

Magnifying glass: for zooming (+ = zoom in, - = zoom out) 

Printer: for printing the current display. 

-o--o--o-- 

Page 26

6 Administration 

6.1 Administration console 

6.1.1 General 


Administration 

The administration console is opened via the start menu (Start > Programs > Elvis > Admin 

Console). An entry „ElvisAdmSnapin“ is featured in the console master data. Here settings 

for the process server and terminal are possible. The active projects (databases) are featured 

under the process server. A special authorization is required to open a project. Logging-in is 

by user name and password. 

6.1.2 Users 

Here all users with Elvis access are registered. New users may be created and existing users 

cancelled. Users may be inserted in or excluded from user groups. User groups define a user 

profile with special rights for viewing and changing datapoints and performing special 

actions. The visualization designer defines the user groups. Note: changes in user groups 

and their authorization rights for Elvis objects are only possible in the Elvis developer module. 

6.1.3 Ports (process connections) 

Ports may be configured here. In particular the assignment of the ports to the computer 

connections and the computer on which the port is started may be specified here. 

6.1.4 Message port 

The message ports may be configured here. 

-o--o--o-- 

Page 27


Page 28

7 Diagnosis 

7.1 General 


Diagnosis 

The visualization diagnosis is generally only necessary if incorrect behaviour is remarked. If 

error messages are displayed it is essential that the error text be noted exactly so that the 

error may be pinpointed. Please also check your computer’s behaviour via the task manager 

(processes and system performance). Elvis module settings may be used for diagnostic 

purposes. In most cases to achieve a thorough diagnosis not only information on the error is 

required but also the environment. It is therefore useful for diagnosis purposes to select the 

maximum scope (all). These settings should be reset for normal operation (maximum at: 

errors and warnings) as the diagnosis slows down the program sequence and files created 

reach a considerable size. For error diagnoses the information acquired will have to be 

forwarded to the project planner for further evaluation in the majority of cases. 

7.2 Process server 

The process server can create a diagnosis file. The name is elvissvr.log. The file is stored in 

the same directory as elvissvr.exe. The scope of the diagnosis may be set in four stages: 

Off no diagnosis file is created 

Errors only all errors are recorded 

Errors and warnings all errors and warnings are recorded (default setting). 

All errors, warnings and all other important processes are recorded 

The scope of the diagnosis is set via the remote server control. A copy of the diagnosis file 

may thus also be created and the diagnosis file deleted 

without stopping the process server. 

-o--o--o-- 

Page 29

7.3 Terminal 


Terminal 

The terminal can create a diagnosis file. The name is elvisrun.log. The file is stored in the 

same directory as elvisrun.exe. The scope of the diagnosis may be set in five levels: 

Off no diagnosis file is created 

Major errors only major errors only are recorded 

Errors only all errors are recorded 

Errors and warnings all errors and warnings are recorded (default setting). 

All errors, warnings and all other important processes are recorded 

The scope of the diagnosis is set via the main menu (View > Options... > Diagnosis). The 

terminal version information may found under >Help>about... in the main menu. There you 

can also display information about the system and all active modules on that PC and save it 

as a file. 

7.4 Elvis debugger 

The Elvis debugger provides a thorough insight into the process image status. The debugger 

should only be operated by trained personnel with extensive knowledge of the project and 

structure of Elvis objects, in particular the datapoint. To open a project with the debugger 

you must log in with the user name and password. The user must have the authorization to 

start the debugger. The debugger is started via the remote 

server control. 

-o--o--o-- 

Page 30

8 Error messages 


Error messages 

The most important error messages are listed below together with a description of how the 

cause may be eliminated. 

8.1 On starting the terminal 

Access is denied 

Check your user name and password entry. Check whether the computer on which you have 

attempted to log in locally is identical to the computer on which the process server is active. 

If you are not logging in locally: check the DCOM configuration of the Elvis process server 

(see: Configuration for access by network). Error on opening the document A non-existent or 

incorrect project file (.iep) may have been specified for the 

terminal. The database is not loaded. Your process server module database does not suit the 

terminal module project file. Please ensure that the process server has been started with the 

correct database file and that you specified the correct project file on starting the terminal 

(the file may also be stored in a link). The process server is down or not ready with start up. 

8.2 On the process server computer 

The database manager symbol is not displayed (instead of „elvis“ the name of your database 

is displayed). The connection to the database is interrupted. The active database connection 

may be recognized by the program symbol in the task bar. 

(1) Close all terminals still active. 

(2) Close the process server. 

(3) Restart the process server. 

(4) Start the terminals 

After a process server program crash. 

(1) Close all terminals still active. 

(2) Open the Windows task manager. 

(3) Close process rtdsk50.exe. 

(4) Close process Falcon.exe. 

(5) Close all processes beginning with „Elvis“ (e.g. ElvisSvr.exe, ElvisRun.exe, etc ). 

(6) Restart the process server. 

(7) Restart the terminals. Or: shut down and restart the computer. 

-o--o--o-- 

Page 31

9 Appendix 

9.1 Key assignment 


Appendix 

The following keyboard functions are generally available: 

Alt+space bar Open system menu. 

Alt+F4 Close dialogue field or quit program. 

Ctrl+F4 Close the active document window. 

Ctrl+Tab/Esc Change to next document window. 

Shift+Ctrl+Tab/Esc Change to previous document window. 

F1 Call up help system. 

Alt oder F10 Activate menu. 

Shift+F10 or Menu key Display context menu. 

Alt+ Select menu item or control via underlined letters. 

Alt+Tab/Esc Change to next application. 

Ctrl+Esc Open Windows start menu. 

-o--o--o-- 

Page 32


Installation 

1. Installation of the ELVIS runtime software (1) 

- Start application from CD: "Setup_Run.exe" in folder and follow 

the instructions. 

2. Register the IOCOMP control elements (1) 

- Copy content of the folder < Laufzeit_Runtime \IoComp_enu> into the ELVIS program 

directory (standard path is C:\Programme\Elvis) 

- Start the file"reg_iocomp.bat" just copied in your ELVIS program directory and confirm 

the registrations. 

3. Project data integration (3) 

Page 33


- Copy the project data from CD: \Projekt_data\EN ("iqhome_en.db", "iqhome_en.iep", " 

iqhome.chm") into your ELVIS program directory. 

4. Installation of the project planning software (2) 

Start application"Setup_SvrConfig.exe" in folder and follow the 

instructions. 

Now, you can start planning the group addresses, bus connections etc. (Before that, create a 

backup of the project data in another folder). Start the >Server Configurator< now. You will 

be asked to select the database *.db . Select file "iqhome_en.db" from your ELVIS program 

directory. For the first login you will be asked to enter a user name and password. You have 

received this data with your confirmation of order and delivery date. The admission data has 

administrative rights for full project planning. User name and password can be modified 

using the menu >UserProcess serverTerminal< (visualization) must be started. The > Terminal< provides 

the connection between the visualization project ("iqhome_en.iep") and the database 

("iqhome_en.db"). Start the software >Terminal


Project software 

Project planning 

Basic & Professional 

Please select submenu... 

-o--o--o-- 

Page 35


Basic Version 


Basic 


-o--o--o-- 

Page 36


Load project... 


Basic 

You must save the original project in a separate folder on your 

hard disk or on CD before accessing the project for the first time! 

After installation, start "Server Configurator" via programs\Elvis\Server configurator. After 

that, load the delivered "iqhome*.db". After successful registration with user 

name/password (first registration with ©IQHOME.NET access data given in the 

Acknowledgement of order and delivery date confirmation by mail) you can now access the 

server of ©IQHOME.NET and execute your putting into operation process. 

Page 37


In the Basic version fields that cannot be edited are marked grey. 

In the menu point "Data points" all available communication objects EIB/KNX with their 

group addresses can be entered under "Address" (approx. 450). Under "request" you can 

define when the group address is to be read (run-up = Start Process server, Demand = Start 

of visualization page with control elements). Using "Place" you can identify your desired 

module with the respective communication objects quickly. 

Modules: Description: 

AA001-010 Alarm system as burglar alarm system 

AB001 Outside lighting control (Matrix) 

AL001 Alarm and information message system 

EE001 Reminder editor 

JA001 4-side blind automatics front 1 (O) 

JA002 4-side blind automatics front 2 (S) 

JA003 4-side blind automatics front 3 (W) 

Page 38


JA004 4-side blind automatics front 4 (N) 

KL001 Climate Console 01 

KL002 Climate Console 02 

LI001 Operating Console & Simulation Ch. 01-40 

LI002 Operating Console & Simulation Ch. 41-80 

MS001 Media Console - Scenario Manager 

MS002 Media Console - Audio 

SE001 Weather data 

SD001 Sensor System Toolbar 

TI001 Time Switches (Clocks) 

ZA001 Central Command Terminal 

ZD001 Definition of Central Commands 

System System data (date and time) 

Virtual Internal datapoints (output on EIB possible) 

-o--o--o-- 

Page 39

Data points: 


Datapoints 


Basic 

EIB/KNX Group address administration (data points) 

Page 40


It is possible to assign several group addresses to one communication object. If you preset 

the character ">", the second group address instead of the first is read first which might be 

useful and important for actuator feedback addresses. If no symbol is given, the first group 

address is always read first when "Request" is activated. The group addresses can be given 

as 2-fold or 3-fold notations. A mixture must absolutely be avoided! 

To plan the data point list use the separate central communication object overview 

(PDF) for the individual project modules. 

It is possible to enter several group addresses after the other. To separate them use the 

semicolon (;). The sum of all characters must not exceed 255. There must be no blank 

characters. If several addresses are given after each other, the first address is used to send 

(ValueWrite) and request (ValueRead), all addresses are used to receive (ValueWrite, 

ValueResponse). We will call this an address string. 

Example: 03/5/017;03/5/018;03/5/019 

meaning: send to 03/5/017, receive from 03/5/017,...018 und ...019, request from 03/5/017 

This behaviour can be changed: 

If you omit the first address (the sender), i.e. the address string starts with a semicolon, this 

data point will not send. 

Example: ;03/5/017 means not sending, receiving and requesting on 03/5/017 

If there is a greater-than-symbol (>) before the first address, the first address is only the 

sender address. The data point does not respond to telegrams with this address. 

Example: >03/5/017;03/5/018;03/5/019 means sending on 03/5/017, receiving on 

03/5/018 and 03/5/019, requesting on 03/5/018 

Important: Always enter the complete group addresses: 

2-fold notation (**/****): 

Wright: 08/0062, 

Wrong: 8/62 

3-fold notation (**/*/***): 

Page 41

Right: 08/0/062, 

Wrong: 8/0/62 


C A U T I O N: 

When you use a communication object for the EIB/KNX,, the port "EIB" must be selected at 

the respective object and at least one group address must be given which must also be 

assigned to another EIB component in your facility. 

If this group address is not used by any other component in your EIB facility, the "EIB" port 

must not be activated since this may lead to malfunctions due to missing values 

(ActualValue) within the ©IQHOME.NET calculations. 

When filling in your group addresses, m ake sure that the readable (read) group address 

(without algebraic sign always the first address) filled in ©IQHOME.NET corresponds to the 

readable address in the EIB/KNX device of your project (as a standard, in ETS also the first 

group address given). 

-o--o--o-- 

Page 42

Datapoint groups: 


Datapoint groups 


Basic 

To design the access rights (see user rights), the data points can be matched to a data 

point group each. For protection of this data we distinguish between read access (L) and 

write access (S). The read or write right for this data can be given to the user groups 

individually. If a user is not authorized to access this data they cannot view the respective 

data at any place in the runtime modules. With a read right they can view the data but not 

change it. The write right permits the user to change the data. An exception are those 

records that cannot be modified. 

Page 43


-o--o--o-- 

Page 44

Datapoint ports: 


RS232/USB-Port 


Basic 

To ensure communication with the EIB/KNX via your connected EIB RS232 or USB interface, 

the "Server" must be set from "Elvis Simulator Port" to "Elvis Eib Port/Falcon" and the 

correct COM connection as well as the protocol of your EIB RS232 or USB interface must be 

selected. 

Hints when using a USB data interface with Windows 2000/XP: 

If required, disconnect the interface (USB-cable to interface). Start the PC. Connect the 

interface (USB-cable to interface). Open the device Manager. Do you find the entries 

(marked red in the picture) for the USB interface? 

Page 45


If you do not find these entries your interface is not detected. Possible causes: faulty plug, 

defective able, defective interface, Windows driver surface problem. Try to locate the cause 

using another PC / another interface. 

If you find the entries, the interface should also appear in the ETS Connection Manager 

under communication parameters "USB-device" (The tool ETS Connection Manager is 

supplied in the ©IQHOME.NET download area): 

Start the enclosed ETS Connection Manager: 

Create a new connection (name e.g.: "KNX-USB") 

Page 46


Adjustment in ©IQHOME.NET visualization 

under "Data point connections": 

..... ready: 

Page 47


-o--o--o-- 

Page 48

Datapoint requests: 

Data point requests: 


Datapoint Requests 


Basic 

The most common and most efficient request method is the one depending on demand. 

Here the load on the bus system is the least since only the values needed are really 

requested as soon as you open a page or perform a calculation. The request is not executed 

when the value is already available in the process image. Each request that is defined in 

Elvis is a request „on demand“. In addition to that, the attributes „during run-up“ and 

„cyclical“ can be added to the request. Then, Elvis will try to read the value already when the 

process server is run up or at a specific time interval. Please consider that this may lead to a 

heavy bus load and, in general, is not necessary. Special cases are such devices that, in case 

of a value change, cannot send the values or devices that are to be monitored cyclically. 

-o--o--o-- 

Page 49

User management: 


User management 


Basic 

Using the menu "User", "User Groups" and "User Rights" specific access rights can be 

defined in the visualization. Within the visualization the access rights are not ensured by a 

password protection of pages but of data points! That is why you will find in the menu " Data 

points" the assignment "Group", i.e. each data point can be put in a data point group. 

Depending on whether a registered user (with password to log in at the operating terminal) 

has been assigned to this group, this user has the rights defined by you (read, write etc.) for 

this data point. However, if no rights have been granted, everything is displayed within the 

visualization but changing a push-button or regulator etc. will be of no effect and will not be 

executed. 

The ELVIS access protection defines the rights to execute specific activities and protects 

important data from unauthorized view or modification. In order to generate an efficient and 

user friendly administration of rights, the rights are not directly given to the users but to 

user groups. One user group is granted specific rights to an object to be protected or to carry 

out specific actions. One user can belong to one or more user groups possessing their 

respective rights. A similar easy group structure was chosen for the huge number of data 

points. Each user group is not granted the right to access individual data points but to access 

a data point group. Thus, administration of the rights is clearer and can be modified faster. 

The user is important only in connection with the access protection. To grant different 

Elvis-users different rights the user names have to be fed into the system and their rights 

must be defined. To do so, a user list must be generated and user groups must be formed. If 

one user belongs to several user groups, the rights from the different user groups add up. To 

prevent misuse of user rights a password can be used in addition to the user name. 

Page 50


Page 51


Among the data to be protected are: data points (all attributes), time programmes (the 

switching times), records (the values recorded). To protect this data we distinguish between 

the read access (L) and the write access (S). The read and write right to this data can be 

given individually to the different user groups. If one user has no right to the data, he cannot 

view the respective data anywhere in the runtime modules. W ith a read right he can view the 

data but cannot modify it. The write right permits the user to modify the data. An exception 

are the recordings that cannot be modified. 

-o--o--o-- 

Page 52


Page 53

Alarm: 


Alarm management 


Basic 

If data points with alarm monitoring (column "Alarm") have been activated in the data point 

list: 

these will be managed under "Alarm". The alarm value completes the alarm condition 

„Alarm“. It permits to distinguish between excess and shortfall. If the upper limit has been 

exceeded the alarm value contains a 1, if there is a value below the lower limit a – 1. 

Otherwise (in the „Normal“ condition) the alarm value is 0. During the project planning 

period the alarm value is important only for calculations. Limits can be fixed for each data 

point. To recognize in the data point list whether limits have been fixed for a data point, the 

data point list disposes of a checkbox in the „Alarm“ column. By ticking the alarm checkbox 

the data point is included in the list of alarms. By removing the check the respective data 

point entry is deleted from the alarm list. Next to the checkbox there is a box to open the 

alarm list. An upper and a lower limit can be given for each data point. However, it is not 

absolutely necessary to enter both limits. 

Principle: 

The alarm goes off when the upper limit is exceeded or the lower value is fallen short of. The 

limits themselves belong to the admissible range. 

The indication of limits for truth values (Boolean) is different from all other formats. Here, we 

do not have a value range that could be limited but only two possible values. Thus, the limits 

only indicate which of the two values has to release the alarm. In the following we will use 

„on“ and „off“ as designation for the two values and thus also represent 1/0, up/down 

True/False, -1/0 etc. If the alarm is to be set off at the value „on“, both alarm limits must 

be set to „off“. „Off“ is the only admissible value and thus, at the same time, forms the 

limits (see above principle). If the alarm is to be released at the value „off“, both alarm 

Page 54


limits must be set to „on“ (opposite the above case). For truth values it is not useful to set 

the alarm limits to different values. 

The message groups ("Messages") are defined in the menu >Messages

Message ports: 


Message ports 


Basic 

Message ports combine all outputs that serve as information about alarm conditions and that 

are not given by the operating terminal or data point connections. Possible message types 

are for example: print, send e-mail, send SMS, write in a file etc. Project planning of the 

different message types is done in the same way. Thus, we achieve a clear and easy to 

handle project planning. The most important data required for project planning are given by 

answering the following questions: 

What will release the message? 

What information does the message give? 

Who receives the message? 

How is the message transmitted? 

When is the message transmitted? 

To save time during the project planning and to permit quick and easy modifications the data 

required for the messages is divided into three lists. Each of these lists includes one part of 

the essential data each. Establishing references between the entries in the different lists 

permits flexible messages. To illustrate the procedure just consider the list entries and their 

references a chain which as a whole contains all information required to send messages. 

When planning the messages it is recommended to start with the message ports continues 

with the message recipients and the messages and finally, in the alarm list, assigns the 

messages to the data points. 

Depending on the message type special servers for Elvis messages will be delivered and 

installed. Their selection and adjustment is made in the list of the message ports. Message 

ports are similar to data point connections. One recipient is assigned to precisely one 

message port. Parameters can be used to make individual adaptations. Each port has the 

format parameter, it defines the output format. 

Format / The format consists of the following elements: 

- fixed text 

- $(Text) the message text 

- $(Time,) that is the UTC 

- $(LocalTime,) that is the local time 

Example: 

Format=Elvis-Message $(LocalTime,DD.MM.YY hh:mm:ss) $(Text) 

Due to the information $(Text) the text stored in the "Text" field under "Data points" at the 

Page 56


communication objects "Alarm message 01..." is sent as SMS when the alarm is set off. 

-o--o--o-- 

Page 57

Message recipients: 


Message recipients 


Basic 

The list of recipients defines who can be reached how. Here, you can define the address or 

number of the recipient (who) as well as the transmission type by selecting a message port ( 

how). A message delay time and a cyclical message repetition can also be put into the list 

of recipients. 

-o--o--o-- 

Page 58

Messages: 


Messages 


Basic 

The list of messages defines what message is sent to whom and through which. Activation 

(through which) can be an excess or shortfall of the limits but also its acknowledgement 

and the return to the normal range. The same applies to the deactivation. However, 

deactivation only plays a role if a delayed or cyclical message is demanded. Then, a 

deactivation terminates the messages or message trials. The message text (what) consists 

of fixed and variable parts. Variable parts are the data point attributes of the data point that 

has set off the alarm (see 6.2.2 and 32.4.2). They are just inserted as place holders into the 

fixed text parts. Place holders are: 

$(Name), $(Type), $(TechnicalAddress), $(Text), $(ActualValue), $(NominalValue) or 

$(Value(Location)). Even defined attributes can be accessed via $(Value(Name of the 

attribute)). The recipient/s (to whom) must be put into the list of recipients. Several 

recipients can be assigned to one message. In addition to that, a data point in a message 

can control whether the message is sent (columns „Control-Data point“ and „Control-Value“). 

Extended configuration of the alarm console for SMS: see description of alarm and 

information message console! 

-o--o--o-- 

Page 59


Professional Version 


Professional 

The ELVIS project software (Professional) must be ordered directly from IT GmbH 

(www.it-gmbh.de). This is due to licence rights. Purchase of a project software full licence 

must be proven (send invoice no. of IT GmbH by mail). Only then you will receive the release 

key for the complete project of ©IQHOME.NET. 

Because of its complex structure we will not describe project planning in this help. 

Please refer to the separate and very comprehensive technical ELVIS manual! 

Do not forget to save the original project in a separate folder on your hard disk or 

on CD before you access the project for the first time! 

Never change the data point names "Name" of the communication objects 

since this will lead to faulty script processing and calculations! 

Examples from the Elvis project planning: 

Page 60

Excerpt of "Data point connections" 


(01) Menu adapt data point connections 

(02)(03) Adapt parameters (COM Port, BCU Protocol [BCU1, FT1.2] etc.) 

Page 61

Excerpt of "Data points" 


(04) Menu data points 

(05) Data point name 

(06) Select data point type (EIS communication objects EIB/KNX) 

(07) Select data point connection 

(08) Assign group address to data point (double or triple notation possible) 

(09) Adapt data point request (when server runs up, on demand [page call], cyclical etc.) 

(10) Data point description/information or message texts (e.g. SMS) 

(11) Assign data point to a user group 

Page 62


Excerpt of "Operating terminal", here visualization interface (only possible for 

project version of ©IQHOME.NET Professional) 

(12) Menu operating terminal 

(13) Attribute window of control element (18) 

(14) Individual text display on the button if value changes 

(15) Individual colour for text display and background 

(16) Integration of any picture/symbol 

(17) Currently integrated picture 

(18) Currently processed control element 

-o--o--o-- 

Page 63


Support 

Support Service 

When purchasing the product without support you will receive access to our ©IQHOME.NET 

service area. The difference between this version and the version with support is that you 

cannot send questions to us but may only view given information. After finishing the 

purchase process each customer receives the link for software download by mail as well as 

the access data for the service area. 

The download link is free for a limited time. The method of payment determines when you 

will receive the respective mail after purchase. For direct debiting or credit card payment you 

will receive the download link immediately after purchase. For cash in advance the link is 

released as soon as we have received payment. 

If you have decided to buy the version with support we will answer your individual 

questions concerning installation and project problems by mail. You will receive a special 

mail address showing your order number. We will do our best to answer your questions as 

soon as possible, however, we are not obliged to answer your questions or solve your 

problem within a certain time. Support is limited to one year. 

After we have received your order, the licence dongle (USB or Parallel for NT) will be sent to 

you by mail within a few days together with the licence certificate/s. Till that time the 

process server is limited to a runtime of 2 hours per start. 

In general, your questions will be answered on the same day from Monday to Friday between 

8 a.m. and 5 p.m. Our technical support may even be contacted at weekends and on public 

holidays depending on availability. The content of your questions and the solution will be 

made available to all registered customers in the service area but we will not include names, 

e-mail addresses or other personal data. 

The ©IQHOME.NET service area is not a platform but a list of questions, problems and 

solutions listed according to topics and selected by EIBMARKT GmbH. 

©IQHOME.NET is constantly being optimised and extended. However, there is no claim to a 

specific update. Basically, updates are free and not limited in time for buyers of 

©IQHOME.NET. Even years later, a buyer of ©IQHOME.NET, with or without support, can 

download available updates free of charge. Precondition is that a buyer returns the signed 

licence certificate/s. For a global version change a fee might possibly be charged. 

Many modules such as counter administration, timetable module, energy optimisation etc. 

can be purchased as options and extensions. Later extensions are also always possible. (see 

version "Individual"). 

-o--o--o-- 

Page 64


Navigation 

Main menu 

(01)(02)(03)(04)(05)(06) 

Base menu 

(07)(08)(09) 

Submenu 

(10)(11)(12)(13)(14)(15) 

The main menu consists of links to the modules: 4-side blind automatics (01), Outside 

lighting matrix (02), Media Console (03), Climate Console (04), Tools (05), Operating 

terminal light (06). 

The base menu contains the integrated online help (07), the link to the start page (08) and 

the page-related label editor (09). 

In the submenu, all available program modules of a selected main menu are displayed for 

selection. An active element is marked by a small LED flashing white at the lower edge of the 

button. Our example shows the main menu "Tools" (05). "Central commands" (10) is being 

activated in the submenu. As examples, you will find further available program modules of 

"Tools" in this submenu: Definition of central commands (11), Alarm and information 

message console (12), Weather station sensor system (13), Memory editor (14), Clocks 

(15), Alarm system (17). 

It is possible that each submenu is divided into its own program modules such as weather 

station sensor system\sensor system toolbar. Using the arrow keys you can browse through 

the submenu (continue, back). A free navigation field (16) can be used for further links 

(©IQHOME.NET Professional project planning). 

Page 65


-o--o--o-- 

Page 66


Start screen 

Start page 

(01) Display of the current PC system time, date and day 

(02) Display of the current wind speed in m/s and standard steps 

(03) Display of the current rain situation 

(04) Display of currently active alarms from the alarm console 

(05) Display of the current outside temperature with frost warning 

(06) Display of the current twilight situation 

(07) ©IQHOME.NET Link (www.eibmarkt.de) 

(08) Individual module labelling, two-line, using the label editor 

(09) Label editor 

(10) Online help 

(11) Main menu 4-side blind automatics 

(12) Main menu outside lighting matrix 

(13) Main menu media console (Scenario Manager & Audio Console) 

(14) Main menu climate console 

(15) Main menu tools (Central Terminal & Definition, Alarm system, Alarm and information 

message console, Memory editor, Clock program, Sensor system) 

(16) Main menu operating console with presence simulation 

(17) Runtime menu 

Page 67


chirm gliedert sich in mehrere Bereiche. Im Ken befindet sich das 

Informationsdisplay mit folgenden Daten: 

Time and date (01) are sent cyclically (EIS3 and EIS4 format cyclical 1 min.) to the EIB/KNX 

bus and, thus can be used for the most different applications and synchronization tasks 

within your facility (e.g. as master clock, display for room controller or temperature 

regulator, timer clock for alarm systems etc.). The display of the current PC system time, 

date and day is always active and is always on. 

INFO: Integration of a USB DCF PC radio-controlled clock (good value at the shops) into 

your PC, permit automatic switch-over to summer and winter daylight saving time as well as 

a 100% precision. When purchasing the clock outside Germany pay attention to the 

reception of the DCF radio signal in your region. The data points are given cyclically as type 

EIB Date (3 Byte), EIS 4, (data point "Datum extern", see project planning in 

©IQHOME.NET) and as type EIB Time (3 Byte), EIS 3, (data point "Uhrzeit extern", see 

project planning in ©IQHOME.NET) to the EIB. If required, the cycle time can be modified in 

the project. 

In (02) the current wind speed in m/s (in weather station area – sensor system also in km/h 

and wind speed), as well as the exact designation of the weather service are displayed as 

text. Below the text there is an analogue value display of the current wind speed in m/s. You 

will find all sensor inputs that can be connected in the data point list EIB/KNX or under the 

topic Weather station sensor system. 

The following values are calculated automatically by ©IQHOME.NET from the data of the 

Page 68


EIB/KNX wind sensor (if available) and displayed as text: 

> 118 km/h = "Hurricane" 

> 103 km/h = "Violent storm" 

> 089 km/h = "Heavy storm" 

> 075 km/h = "Storm" 

> 062 km/h = "Stormy wind" 

> 050 km/h = "Stiff breeze" 

> 039 km/h = "Strong wind" 

> 029 km/h = "Fresh breeze" 

> 020 km/h = "Moderate breeze" 

> 012 km/h = "Weak breeze" 

> 006 km/h = "Light breeze" 

> 001 km/h = "Light draught" 

= 000 km/h = "Calm" 

Both displays are only active if your facility contains an EIB/KNX wind sensor and values are 

sent to the bus. Here it is not important whether the data is given in m/s or km/h. As a 

standard ©IQHOME.NET is set to m/s. However, with the sensor system toolbar you can 

select your own units using conversion factors (Offset/Factor). ©IQHOME.NET offers this 

option for all integrated sensor inputs in the sensor system toolbar. The EIB communication 

object must be of type EIB Wert-16 (2 Byte), EIS 5 (Float), (data point "Sensor Wind", 

see project planning in ©IQHOME.NET) and is generally supported by all weather stations. 

If no data is received, these elements are completely blank. 

This position (03) indicates the current rain situation. The display (symbol clouds with rain) 

is only on if your facility disposes of a EIB/KNX rain sensor and the value logical "1" of the 

type EIB Schalter (1 Bit) Boolean, EIS 1, (data point "Sensor Regen", see project 

planning in ©IQHOME.NET) is active on the bus. 

If no data is received, these elements are completely blank. 

The text "Alarm!" (flashing) is indicated in this position (04), if one of the 13 alarm 

messages from the alarm console has been released (value logical "1" of type EIB Schalter 

(1 Bit) Boolean, EIS 1, (data "Alarmmeldung 01-13", see project planning in 

©IQHOME.NET)). Above the text message, the current number (not flashing) of incoming 

and not yet acknowledged alarm messages is indicated. By clicking on the number or the 

text you go directly to the alarm console to view all active alarms. If no alarm message has 

been released, the displays are automatically blinded out. 

The current temperature is given in °C (05). The display is only active, if your facility 

disposes of a EIB/KNX temperature sensor and values are sent to the bus. The symbol "Star" 

is automatically (flashing) displayed when the current temperature value is smaller 

than/equal 3°C and there is a danger of frost. These calculations are made automatically in 

©IQHOME.NET and can be modified using the project software if required. The EIB 

communication object must be of type EIB Wert-16 (2 Byte), EIS 5 (Float), (data point " 

Sensor AT", see project planning in ©IQHOME.NET) and is generally supported by all 

weather stations. 

This position (06) gives the current twilight situation. The display is only active, if your 

facility disposes of a EIB/KNX twilight sensor and values are sent to the bus. The symbol 

(cloud with crescent moon and active outside lamp at the house) is only displayed when 

twilight is active. The twilight value can be evaluated in ©IQHOME.NET in 2 ways: 

The EIB communication object can be of type EIB Wert-16 (2 Byte), EIS 5 (Float), (data 

point "Sensor HellD", see project planning in ©IQHOME.NET) and is generally supported by 

all weather stations. Here, the twilight limit value is parameterised in ©IQHOME.NET by 

means of a slide switch (in outside lighting matrix). 

Page 69

or 


The EIB communication object can also be of type EIB Schalter (1 Bit) Boolean, EIS 1, 

whereas limit value parameterisation is not done via ©IQHOME.NET (outside lighting 

matrix), but directly by the EIB twilight switch or a conventional twilight switch that has 

been connected by means of a binary EIB input. In this case, the display is on when a 

telegram value logical "1" of type EIB Schalter (1 Bit) Boolean, EIS 1 on the 

communication object "Sensor HellDS" (see project planning in ©IQHOME.NET) is sent. 

The main navigation menu is grouped around the core (information display): 

Link to the www.eibmarkt.de website (07) to get news directly from the service area. To do 

so, a connection must be established. If there is no connection this link is without any 

importance. 

Your project designation (08) is displayed in two separate text elements that can be edited. 

Using the label editor (09) this label can be edited directly during the runtime. You will find 

the label editor (09) on every ©IQHOME.NET page to edit all available labels for the 

currently active page quickly and flexibly during the runtime. Click on this element to 

activate it and you will come to a copy of the current page. Here, all text elements that can 

be edited are marked "yellow". Click directly on a yellow text element to modify the text. 

After the modification you use an "arrow key" to return to the original page and the new 

labels will appear. 

You will find the online help (10) on every ©IQHOME.NET page to access required 

information quickly. The main navigation (11)(12)(13)(14)(15)(16) navigates you 

directly to the topics. 

In the runtime menu (17) you can also open all pages using the "Open page" symbol. 

Further options are "Back to the last active page", "Update", "Full screen mode", "Basic 

adjustments for alarm list", "Print function" and the Elvis help. 

You will find all descriptions of the individual communication objects EIB/KNX in 

the central data point list! 

-o--o--o-- 

Page 70


Burglar alarm system 


-o--o--o-- 

Page 71


Purpose 


The burglar alarm system (EMA) serves as active building protection. The EMA does not 

dispose of a VdS certification but serves as alarm centre for simple requirements in 

one-family houses and apartment houses with high-quality equipment. The EMA disposes of 

3 activation areas (EMA for absence). In addition, each area is equipped with monitoring 

during presence (night) and separate activation option. Thus, it is possible to use the system 

during presence with other characteristics than those for absence without a new 

configuration. Area 1 (EMA) for example serves to monitor the ground floor and upper floor 

of your house. When you are absent you might want to activate all message lines (window 

contacts, door contacts, glass break detector, motion detector etc.). However, during night 

operation, certain motion detectors should not be integrated in the monitoring (hall in front 

of the bedroom) or window contacts (bedroom window) but only the whole ground floor and 

certain areas on the upper floor. This is achieved with the night system area 1 (night). In 

each area (EMA/night) the connected message lines can be activated or deactivated 

individually. The night system for example can be activated by means of a push-button near 

the bed (bedroom, children’s room, guest room) (see function description). There is a 

multitude of combination options via matrix with always one matrix for a maximum of 15 

motion detector inputs, one matrix for max. 22 window, door and other closing messages, 

one matrix to assign the alarm outputs and one matrix to define a reference contact, which 

represents for example the exit of an alarm area. The reference contact serves to exclude the 

collect information message "Activation possible ", which is made available externally and 

separately for each area on the EIB/KNX to be integrated in a push-button switch (LED) or a 

panel near the respective activation device (within the building). Many other functions such 

as countdown to activation or alarm delay for alarm outputs (siren, switch-off delay) are 

integrated. 

-o--o--o-- 

Page 72


Features 


EIB/KNX Alarm system as burglar alarm system (EMA): 

� Burglar alarm system with three activation areas (EMA) 

� Each area with additional monitoring while present (night) and separate activation option 

� 37 message inputs (lines) 22 of which are message inputs for window and door contacts 

as well as 15 motion detector inputs 

� General alarm outputs (siren, flashlight, sound etc.) 

� Area-related alarm outputs (alarm, SMS etc.) 

� Matrix for free message input assignment for areas 1-3, EMA (E)/night (N) 

� Cycle monitoring of the message inputs (can be switched on individually) with freely 

definable time intervals and status information 

� 6 separate activation inputs to activate the areas 1-3 EMA (E)/night (N) 

� Countdown function for activation delay of the areas 1-3 EMA (E)/night (N) 

� Operating mode switch-over for motion detector (lighting- ,message mode) 

� Status display for activation stand-by, LED activation/deactivation message and 

operating mode 

� Matrix for alarm output assignment for the areas 1-3 EMA (E)/night (N) 

� Matrix for system functions of the areas 1-3 (panic, alarm output delays, SMS etc.) 

� Extended panic function with logics for outside lighting matrix and optional twilight 

switch-off function 

� Released detector display / contacts after alarm and registration in alarm list with time 

and date stamp 

� Quit function for released detectors and reset of the alarm outputs 

� Safety thanks to logic scripts in server, operating terminal does not have to be activated 

� Remote access administrative or data point related 

� Message function by means of SMS can be configured freely (3 SMS alarm outputs area 

1-3) 

� User-defined access rights 

� User-defined labelling of the alarm outputs, message inputs and modules 

-o--o--o-- 

Page 73


Preconditions 


To make use of this module the following is required or recommended: 

� To transmit SMS information the modem recommended under www.eibmarkt.com must 

be used (Microlink 56k Fun USB). 

� Pre-configurated for D1/D2/EPlus (GSM/UMTS) networks, other networks can be 

integrated in a "Services" file that is also delivered. 

Note: 

Basically, it might be necessary to adapt your operating system & modem to ensure SMS. 

We cannot grant any support for these specifications. 

In our shop (www.eibmarkt.com) we recommend for example: 

V.92-Internet-Modem with USB 

Ref. No.: N490020 

(To the input in the search mask) 

Manufacturer: Microlink 

Manufacturer Nr.: 56k Fun USB 

IQHOME.NET is equipped with an alarm and information message console which has already 

been pre-configurated for the SMS dispatch of 13 single alarm messages and 1 collective 

error message with services for the GSM/UMTS D1/D2 and E-PLUS networks. Other networks 

can also be integrated but have not been tested. Due to the complex activations and the fact 

that the parameters do not have a uniform standard for all modem types, the comprehensive 

tests have been run for one modem type which can thus be recommended here: Microlink 

56k Fun USB (analog). 

Extract from the alarm and information message console IQHOME 

Page 74


Activation device EMA (outside) 

concealed or surface mounted 

Art.Nr.: N157941 


Manufacturer: GIRA 

Manufacturer Nr.: 0135 00 

Switch keys/VdS radio-controlled alarm system/VdS concealed shaped semi-cylinder not 

included in delivery! To activate or deactivate alarm centres. Wire-connected. Sealed casing 

to be used inside or outside, selectable continuous or pulse contact, two freely switchable 

LED displays and buzzer to indicate acknowledgement or rejection, arcing and lift-off contact 

against sabotage. The casings disposes of a protection against front drilling. For installation 

acc. to VdS, a VdS shaped semi-cylinder is required (not included in delivery!). Operating 

voltage: 9 to 15 V DC Nominal voltage: 12 V DC, current consumption per LED: approx. 10 

mA, buzzer current consumption: approx. 25 mA signal transmitter: buzzer 12 V 85 dB/10 

cm load capacity of all contacts: max. 60 V / 0,5 A operating temperature: - 20 C to + 60 C 

protection: IP 54 surface-mounted casing, front plate: Aluminium die casting, colour: white 

RAL 9010, dimensions casing: W x H x D 79 x 113 x 54 mm VdS-certificate: G 197 707, 

concealed casing, front plate: Aluminium precision casting, dimensions front plate: W x H x 

D 101 x 135 x 3 mm, dimensions casing: W x H x D 79 x 113 x 54 mm, VdS-certificate: G 

197 707 Reference no. 0135 00 concealed 

4-channel push button interface 

for 

activation device EMA (inside assembly) 

Ref. No.: N370360 




Page 75


The 4-channel push button interface has 4 independent channels which – depending on 

parameterization – can be used as inputs or alternatively as outputs (only channels 1 or 2). 

The push button interface can therefore be used to poll its inputs for the switching state of 

up to 4 potential-free push buttons/switches with a common reference potential and send 

the corresponding telegrams to the instabus. These may be telegrams for switching or 

dimming, shutter/blind control or value transmitter applications (dimming value transmitter, 

light-scene extension, temperature or brightness value transmitter). Moreover, 2 switching 

event counters or 2 pulse counters are available. Channels 1 and 2 can be used alternatively 

as independent outputs for controlling up to two LEDs. To increase the output current (cf. 

Technical Data), the channels can also be connected in parallel if they are parameterized 

alike. The outputs are short-circuit-proof and protected against overloading and false 

polarity. Connecting 230 V signals or other external voltages to the inputs is not permitted. 

The available inputs and outputs are connected as follows: 

Signalgeberkombination 

Blitzlicht/Sirene 

Ref. No.: N157980 




Outside siren with flashlight/VdS radio alarm system/VdS white, acoustic/optical signal 

transmitter unit for inside or outside. To be connected directly to the radio alarm centre/VdS 

or the radio sub-centre. With sabotage contact, i.e. an alarm signal is given when the casing 

is opened. The casing consists of corrosion resistant stainless steel V2A, is powder-varnished 

Page 76


and very robust. The edges of the casing are welded and thus it cannot be bent open or 

opened with a lever. Weather resistant siren: voltage supply: 12 V DC (9 to 13,8) current 

consumption: 500 mA bei 12 V DC sound pressure: 124 dB flashlight: voltage supply: 12 V 

DC current consumption: 300 mA at 12 V DC flashlight: approx. 1 W s temperature range: - 

20 C to + 70 C dimensions: W x H x D 185 x 380 x 140 mm Protection: IP 64 

VdS-certificate: G 195 093 (with flashlight), G 195 094 (w/out flashlight) reference no. 0956 

00 white 

Topology example: 

Alarm movement detector 

Universal-Comfort 

Ref. No.: N167568 


Manufacturer: JUNG 

Manufacturer Nr.: 3180-1A 

Page 77


The automatic switch 180° Universal with alarm message is designed for interior application 

and is plugged onto a concealed bus coupler (UP-BA). It works with a passive infrared sensor 

(PIR) and responds to heat movement released by people, animals or objects and sends 

telegrams to the instabus EIB depending on the operating mode adjusted. Possible operating 

modes are a lighting operation and a more 'insensitive' message operation. In lighting 

operation the automatic switch can transmit switch, value indicator or light scene call 

telegrams to the bus. In message operation, the automatic switch transmits a message 

telegram to a terminal such as the alarm centre only after a repeated request of the motion 

signal. The automatic switch Universal can be used as single instrument, main instrument or 

extension station. Thus, the use of several automatic switches Universal in one room – to 

extend the capture range – is possible when you combine one device that has been 

parameterised as main instrument with several devices parameterised as extension stations. 

Here, the automatic switch Universal can be connected with automatic switches Standard 

concealed with extension station application or with presence detectors Universal as 

extension station. Using a slide switch the automatic switch Universal can be operated 

manually. Furthermore, the device can be adapted to the local conditions by means of three 

potentiometers. The device disposes of an alarm function in case of its removal from the bus 

coupler. Comprehensive separate parameters for alarm system operation (message 

operation) permit a detailed fine adjustment of the detector sensitivity. Thus, false alarms 

are reduced considerably. 

Application 

Lock Bolt Switching Contact 

(for monitoring locks on doors and windows) 

Ref. No.: a290103 


Manufacturer: ABB 

Manufacturer Nr.: WRK/W 

The lock bolt switching contact is used for monitoring locks on doors and windows. 

Function 

The switching element of the lock bolt switching contact is a micro-switch with a two-way 

contact. The switching point can be adjusted with a three-way latching disc. The device is 

supplied in switch position 2 (notch of the latching disc in the centre of the operating lever). 

For switch position 1 or 3, lift the latching disc and snap into place after turning it to the 

required switch position according to the markings. In addition, the operating lever can be 

extended by 6 or 12 mm by attaching the supplied plastic clip. 

Design and installation 

Page 78


Due to its compact design, the lock bolt switching contact can simply be mounted behind any 

strike plate. The printed circuit board that is attached to the micro-switch enables the 

connection cables to be soldered on and offers additional soldering terminals for any required 

resistors. The lock bolt switching contact is mounted inside the strike plate of the door or 

window frame using 3 countersunk screws. The opening may need to be enlarged under 

certain conditions. 

Magnetic contact MK4W VdS 

(for monitoring doors and windows) 

Ref. No.: e166-3 



Manufacturer Nr.: MK4W 

Magnetic contact and magnet to be installed in window and door frames to monitor opening. 

Magnetic contact and magnet are installed facing each other or in parallel in the window 

frame/door panel and window base/door base. Series connection of magnetic contacts in the 

reporting line possible. Type of contact: 1-pole closing contact, switching voltage: max. DC 

100 V Capacity: max. 10 W Operating voltage: max. 40 V Connecting cable white: 2,5 

m/10m LIYY 4 x 0,14 qmm, VdS-No.: G 191 556 Color: white, Delivery volume: magnetic 

contact, magnet, Option: 2 pcs. casings, white (AGW ) Info: In order to analyze the contact 

information in the EIB the magnetic contact has to "be prepared" for bus use first. This can 

be done in different ways. For example, if you want to connect the contact locally to the EIB, 

that means you do not want to put the line directly to a central evaluation center (such as 

electrical distribution) the best way is a connection using a push button interface (2-fold, 

4-fold, 8-fold). For central registration the binary inputs REG (series buit-in device for 

electrical distribution) are suited best. In general, these are 24 V-AC/DC binary inputs, that 

means a voltage (24V) is sent to the contact which is then analysed at the binary input 

(edge analysis). For example: leading edge (window closed) there are 24 V at the binary 

input ---> "OFF" bus telegram and decreasing edge (window open) there aren´t 24 V at the 

binary input ---> "ON" bus telegram. You can use this information to regulate the heating 

when the window is open to ensure frost protection or alert and display messages. In 

general, these contacts are registered room by room that means one binary input contact per 

room. 

Various further sensors are available in the shop for integration (ex. broken glass or 

ultrasound sensors etc.). 

-o--o--o-- 

Page 79


Topology 


Inputs EIB/KNX Outputs 

Page 80


-o--o--o-- 

Page 81


Central terminal 


The surface of the alarm system (EMA) consists of several operating pages (ModuleAA001 - 

Module AA008): 

The main module is the alarm system information display (AID), Module AA001: 

(01) Information display alarm system area 1 

(02) Operating console alarm system area 1 





(07) Standby display for area 1-3 each and divided into EMA as well as night operation 

(08) Activation button alarm system (EMA) 

(09) Input mask for switch-on delay (countdown) till activation EMA with remaining time 

display 

(10) Activation button alarm system (night) 

(11) Input mask for switch-on delay (countdown) till activation night with remaining time 

display 

(12) Acknowledgement button after alarm (reset of message lines and alarm outputs) 

(13) Individual labelling of the alarm system areas by means of the label editor 

(14) Navigation link main menu (button pressed with active, flashing white LED below, if 

selected, our example "Tools") 

(15) Navigation link submenu Tools 

(button pressed with active, flashing white LED below, if selected, our example "Alarm 

system") 

(16) Navigation link to label editor (base menu) 

(17) Navigation link to system settings of the alarm system 

(18) Navigation link to message line matrix with the lock monitoring contacts 01-10 

(windows/doors) 





(21) Navigation link to message line matrix with the motion detector inputs 01-10 

(22) Navigation link to message line matrix with the motion detector inputs 11-15 

(23) Navigation link back to main menu "Tools" 

Page 82


Each alarm system area can be used as EMA-system when absent or night alarm system 

when present. Each of the 3 alarm areas in IQHOME.NET disposes of a alarm system 

information display. 

The individual alarm system information displays 1-3 show the current condition of the 

subordinate system areas EMA/night. The upper section displays the EMA area (Einbruch 

(burglar) Melde (alarm) Anlage (system)). The function block EMA is only activated in case 

of absence. The lower section shows the condition of the alarm system area night. 

Page 83


Furthermore, there are 3 general symbols for released alarm outputs in the display: 

1. Acoustic alarm output set off (siren, symbol in the top left middle, bell) 

2. Optical alarm output set off (flashlight/rotating flashlight, symbol in the bottom left 

middle, rotating flashlight) 

3. Area-related alarm output set off (symbol in the top right middle, globe with mail) 

All information is stored in the alarm list including time and date of release: 

Basically, only the EMA-system for absence or the night alarm system for presence can be 

active. That is why only one lock symbol (symbol door with lock) stands for the EMA and 

night area. This symbol shows the status of the alarm system being active. The symbol 

appears when the system is activated. This information is important for access via a 

Terminal Client Server in case of absence. 

For the area EMA and night the following separate status displays are generated: 

4. Activation possible .... 

5. Activation impossible! 

6. Activation failed! 

7. Countdown running .... 

8. Alarm system is active! 

9. Burglar alarm! 

10. Deactivation after alarm 

With an EMA-area below and a night area above this display the first message line that sets 

off the alarm is displayed. With every additional released message line this display will be 

updated according to the endangered area, if required. (remote monitoring/access). These 

and all other released message lines are stored in the alarm list indicating date and time and 

can be analysed or printed. 

You can view all available EIB/KNX communication objects in the EIB/KNX data point list. 

The visualization terminal of the alarm system mainly serves the investigation when alarms 

are set off and the system has to be adapted. Generally, the alarm system areas 1-3 are 

activated by means of an external activation device for EMA operation and by means of a 

night switch (EIB key) for night operation. All necessary EIB/KNX communication objects are 

provided in IQHOME.NET. Of course, you can also activate the alarm areas directly by means 

Page 84


of a touch screen monitor near the exit when you leave the building. However, despite of the 

specifically defined user rights/access data for the visualization, the PC/communication 

server and the touch screen monitor should be installed in a monitored area. 

A direct activation is executed by means of the respective buttons. "E" represents the EMA 

system and "N" the night operation of the specific area. When you click on the field for 

switch-on delay input (countdown) you can enter an individual delay time in seconds for the 

respective system (EMA/night). The max. delay time amounts to 32767 seconds (approx. 9 

hours). If you enter bigger values, the system works only with the given maximum value of 

32767. 

The activation devices EMA/night are blocked against each other e.g. if one area is open 

activation of the other is not possible. 

Button symbols: 

E/U - EMA system not activated 

E/S - EMA system activated 

N/U - night system not activated 

N/S – night system activated 

Integration of the external EIB/KNX activation device for EMA operation (when absent) is 

done according to the following topology example: 

Page 85


(LED colours may vary depending on the manufacturer of the activation device. In IQHOME.NET we use yellow and 

green.) 

The required communication objects to be entered in a universal interface 4-fold are 

provided separately in IQHOME.NET for all 3 areas: 

11. LED triggering, activation device, area 1, 2 or 3 EMA 

SSB1LEDge (communication object name in IQHOME.NET, for example for area 1 EMA) 

- This LED is switched on for a few seconds only after activation by means of switch key 

(activation countdown) and indicates the successful countdown start to activate the 

alarm system in the respective area. If this LED is not switched on after key switch 

activation, the system is not ready for activation that means at least one of the message 

lines you defined is not ready (door or window open etc.). To avoid such a situation we 

have created a separate communication object SSB1EMAbereit. Using a group address 

you can connect this object with a push button switch near the exit (LED display). Thus, 

you will be informed before activation whether an activation is possible or not. In addition 

to that, it is possible to exclude information inputs you defined at this communication 

object using the reference contact matrix (see further function description of modules 

AA008, AA009 und AA010) (exclusion in display only, not in monitoring), e.g. the exit 

door to avoid that the push button near the door permanently shows the information 

"Activation impossible". 

12. LED triggering, activation area 1, 2 or 3 EMA 

SSB1LEDgn (communication object name in IQHOME.NET, for example for area 1 EMA) 

- This LED is switched on for a few seconds after the countdown has been completed and 

indicates the successful activation of the alarm system in the respective area. 

The LEDs are switched on for 3 seconds only and then switched off to avoid that third 

parties, or potential burglars, view your current alarm system condition. 

When deactivated, a short flash of the green LED SSB1LEDgn indicates the successful 

deactivation of the alarm area and you can enter the building area that is not monitored 

now. 

13. Activation/deactivation (A/D) is carried out using the communication object SSB1EMA 

(communication object name in IQHOME.NET, for example for area 1 EMA). The 

communication object is of type 1Bit. A "1" signal activates the system. A "0" signal 

deactivates an active system. If, after a burglar alarm, the system is deactivated 

(deactivation after alarm), you can acknowledge this area (same function as 

Page 86


acknowledgement key in visualization "Ackn.") using the switch key and sending a new 

"0" signal. Thus, all alarm outputs (siren, flashlight etc.) and message lines (active 

displays of released message lines, motion detectors etc.) are reset. After 

acknowledgement, the released message lines are shown in the alarm list. 

Info: In our example with 4 channels of a universal interface activation/deactivation is 

possible with only one input (UM-Function). However, all dispose of a parameter to detect 

a long pulse for instance to generate a "0" signal for the extended acknowledgement 

function. As an alternative, activation/deactivation (active/not active) can also be 

realized with two input channels (one input only "1" [On] signal, the other only "0" [Off] 

signal). 

The sabotage contact of the activation device is connected with one of the 22 available 

message inputs for lock monitoring contacts (Infomeldung 01 to Infomeldung 22) 

-o--o--o-- 

Page 87


Alarm outputs 


(17) Navigation link to the system settings module AA007 of the alarm system: 

(24) Selection of the alarm outputs in ©IQHOME.NET that can be activated 

(25) General, area-related alarm outputs (for free application) 

(26) General alarm outputs (flashlight/siren) 

(27) General alarm output sound 

(28) General alarm output panic light 

(29) Area assignment for areas 1-3 (EMA [E] and night [N]) 

(30) Selection matrix to assign the alarm outputs to the areas 

(31) Input mask switch-off delay in seconds for alarm output siren with remaining time 

display 

(32) Status display of alarm outputs with direct activation option 

(33) Navigation link back to main module alarm system information display (AID), module 

AA001 

(34) Navigation link to matrix to define a reference contact collective message "Activation 

possible..." 

(S1) General alarm output sound activation of repeat function 

(S2) General alarm output sound path indication of sound file (*.wav) 

(S3) General alarm output sound path display of selected sound file 

Page 88


With module AA007 (system setting of the activation areas) you can assign the available 

alarm outputs to your activation areas (29) as you like. Simply ticking (Yes/No) in the 

matrix (30) determines whether, in case of a burglar alarm, the alarm output is to be 

released in a respective activation area or not. Therefore, the EIB/KNX provides 3 individual, 

area-related alarm outputs SSB1Alarm, SSB2Alarm and SSB3Alarm (25) for free 

selection (area flash light, message etc.). This alarm output is also used internally to send 

SMS: 

See also: Function description Information message console and Project planning! 

The general alarm outputs flashlight/siren (26) can also be assigned to any activation area. 

The alarm output sound (27) generates the call of any wav-file, that can be selected by 

means of file search (S2). The path display (S3) shows the current path of the selected file. 

If you dispose of a sound system, you can create a scenario using your sound board. Thanks 

to the repeat function (S3) the sound file can be repeated endlessly. (The sound function is 

programmed in the operating terminal and works only when the operating 

terminal is active! (It was not possible to consider this function in the server.) The alarm 

output panic light (28) activates the panic function in the outside lighting matrix. In this 

function, all output channels that are not set to "No function" in the outside lighting matrix 

Page 89


are switched on. Ticking yes for the alarm output "Panic DÄ Auto Off" means that an active 

panic function is taken back automatically by the twilight switch (only if available), i.e. the 

next morning the outside lighting is switched off when the twilight is switched off and works 

as usual according to the automatic functions (useful for longer absence such as holidays). 

Normally, with an active panic function the outside lighting is separated from all other 

automatic functions (blocked) i.e. the outside lighting stays on in case of a burglar alarm and 

active panic function until the released area is acknowledged. 

The communication object Panik is provided by the EIB/KNX to be integrated in a key/panel 

(e.g. near bed in bedroom) for direct panic function activation. 

Example of a key 4-fold Universal/Multifunction near bed in bedroom: 

Utilization example: 

Top left key bedroom mains disconnection 

Top right key siren deactivation (useful with activated alarm output "siren" and burglar 

alarm night, sends only "0") 

Key in the top left middle activation area status night (area 1, 2 or 3) 

Key in the top right middle standby display night (activation possible/not possible) 

Key in the bottom left middle night rest "On" (call of a central command in ©IQHOME.NET 

module ZA001 "central commands") 

Key in the bottom right middle night rest "Off" (call of a central command in ©IQHOME.NET 

module ZA001 "central commands) 

Bottom left key panic function "On" (activation panic function outside lighting matrix or 

additional internal lamps) 

Bottom right key panic function "Off" (deactivation panic function outside lighting matrix or 

additional internal lamps) 

Using the input mask (31) the deactivation delay (AVZ) of the alarm output "siren" can be 

fixed. Click on the marked field to modify the value. The value is given in seconds. When the 

siren is active, the current remaining time is displayed. 

Note: 

In Germany, the maximum runtime of a siren is fixed by the law and may vary (In general 

max. 180 seconds). 

The status displays (32) indicate the current condition of the alarm outputs and can be 

switched on or off directly by pressing the key (ON/OFF-function). 

-o--o--o-- 

Page 90


Reference contact 


(34) Navigation link to matrix to define a reference contact for collective message 

"Activation possible..." 

(35) Selection of the available contact inputs 01-10 of 22 

(36) Area assignment area 1-3 (EMA [E]) 

(37) Selection matrix to define (a) reference contact/s per area 

(38) Navigation link to system settings module AA007 of the alarm system 

(39) Navigation link to the next matrix with the contact inputs 11-20 (AA009) and 21-22 ( 

AA010) 

Page 91


The reference contact serves to exclude the collective information message "activation 

possible" SSB1EMAbereit (e.g. communication object EMA area 1), that is provided 

externally for each separate area on the EIB/KNX to be integrated in a key (LED) or panel 

near the respective activation device (within the building). The contact chosen here is then 

excluded from the display of the available standby communication objects ( 

SSB1EMAbereit-SSB3EMAbereit, SSB1Nachtbereit-SSB3Nachtbereit. If a selected 

contact is also included in a message line, the monitoring function stays active. Only the 

standby display is concerned. This has the advantage that when leaving the building, 

contacts that are „open“ like the front door contact do not constantly generate the message 

„activation impossible” in your standby display (key-LED/display). 

-o--o--o-- 

Page 92


Inputs (contacts) 


(18, 19, 20) Navigation link to matrix of the message lines with the lock monitoring 

contacts 01-22 (windows/doors): 

(40) Selection of the available contact inputs 01-10 of 22 

(41) Area assignment, area 1-3 (EMA [E] and night [N]) 

(42) Selection matrix to assign the message lines (contact inputs) to the alarm areas 

(43) Status display of the contact inputs 

(44) Status display, individual with different display options 

(closed/open/malfunction/released) 

(45) Cycle monitoring of the contact inputs (can be switched on individually as an option) 

(46) Input mask for cycle monitoring of the contact inputs in seconds 

(47) Status display of the cycle monitoring (o.k./malfunction-LED flashes when monitored 

telegram fails) 

(48) Navigation link to matrix of the message lines with the lock monitoring contacts 11-20 


(49) Navigation link to matrix of the message lines with the lock monitoring contacts 21-22 


(50) Navigation link back to the main module alarm system information display (AID), 

module AA001 

Module AA002 (ditto AA003 contacts 11-20 and AA004 contacts 21-22) 

Page 93


©IQHOME.NET disposes of 22 contact inputs defined in the module alarm and information 

message console: 

22 pcs. inputs, information messages: 

Module name: AL001 

Name communication object: Infomeldung 01 - Infomeldung 22 

EIB/KNX data point type: EIS1 (1Bit) 

All connected contact inputs are automatically made available in this alarm system module 

AA002 to be selected (40) in the matrix (42). By simply ticking (Yes/No) in the matrix (42) 

you define whether the contact is to be assigned to an activation area (41) in the alarm 

system or not. If you tick Yes for one area, this contact will be monitored. Contacts can also 

be applied several times and for other areas. 

The status display (43) indicates the current condition of the contact. The following status 

information (44) can be given: 

1. Closed ("0" signal EIB-telegram 1Bit) 

2. Open ("1" signal EIB-telegram 1Bit) 

3. Malfunction (formed internally by cycle monitoring) 

4. Activated! (if a "1" signal EIB-telegram 1Bit is detected with the alarm system being 

Page 94

activated) 


The cycle monitoring (45) is an extended monitoring function for high-priority message lines 

(e.g. when bus line is interrupted etc.). Enter a value greater „0“ (seconds) into the input 

mask (46) to activate the cycle monitoring. For example, when you enter "10" at the contact 

input 08, the binary input must send at least one EIB telegram of the contact with the value 

„0“ or „1“ within 10 seconds. (cyclical sending must be set in the ETS at the binary input). If 

the value is not sent within the cycle time, there is a malfunction message for the sensor. ( 

Malfunction). If a cyclically monitored input is assigned to an activation area which is 

active, such a malfunction will lead to an alarm (Activated) and the message "Burglar alarm" 

of the respective area is transmitted. When cycle monitoring sends a malfunction message, 

the malfunction LED (47) of the contact input flashes. 

-o--o--o-- 

Page 95


Inputs (detectors) 


(21, 22) Navigation link to matrix of the message lines with the motion detector inputs 

01-15: 

(51) Selection of the available motion detector inputs 01-10 of 15 

(52) Area assignment, area 1-3 (EMA [E] and night [N]) 

(53) Selection matrix to assign the message lines (motion detector inputs) to the alarm 

areas 

(54) Status display of the motion detectors 

(55) Status display individual with different display options (o.k. [no 

motion]/motion/malfunction/set off) 

(56) Cycle monitoring of the motion detector inputs (can be switched on individually as an 

option) 

(57) Input mask for cycle monitoring of the motion detector inputs in seconds 

(58) Status display of the cycle monitoring (o.k./malfunction LED flashes when monitored 

telegram fails) 

(59) Navigation link to matrix of the message lines with motion detector inputs 11-15 

(motion detector) 

(60) Navigation link back to the main module alarm system information display (AID), 

module AA001 

Module AA005 (ditto AA006 motion detector inputs 11-15) 

Page 96


©IQHOME.NET disposes of 15 motion detector inputs. Using the available communication 

objects any motion detectors (even conventional motion detectors over 230VAC binary input 

"bus-compatible") can be connected. An advantage of EIB is the double use of motion 

detectors for lighting and message operation. Thus, it is not necessary to install additional 

detectors for alarm systems. This is achieved by so-called "Comfort motion 

detectors/Universal motion detectors" with additional ETS application for lighting and 

message purposes. 

Example: 

Alarm motion detector 

Universal-Comfort 

Page 97


Ref. No.: N167568 



Manufacturer Nr.: 3180-1A 

It is of special importance to be able to parameterise different sensitivity for message 

operation. This is especially useful because you can respond to the different ambient 

conditions of different installation place. Furthermore, false alarms are almost impossible. 

The EIB has to inform these motion detectors of the change from lighting operation into 

message operation. This is done by a separate communication object. (Designation in the 

ETS "operating mode"). When the alarm system is "active", the motion detector is to go over 

into message operation. ©IQHOME.NET provides this switch-over for all areas by means of 

the communication objects: 

Output status area-3 EMA and 1-3 night (active/not active): 

Module name: AA001 

Name communication object: SSB1EMAStatus 


"1" = system area 1 EMA is active 

"0" = system area 1 EMA is not active 


Name communication object: SSB1NachtStatus 


"1" = system area 1 night is active 

"0" = system area 1 night is not active 





















Simply connect the communication objects of ©IQHOME.NET with the communication 

objects (operating mode) of the motion detectors by means of group addresses. If one 

motion detector has a multiple assignment in one area EMA and night, both status addresses 

(EMA+night S/U) provided by ©IQHOME.NET have to be entered at the motion detector 

object "operating mode". 

Page 98

15 pcs. inputs, motion detectors: 



Name communication object: Melder01 - Melder10 





Depending on their type (lighting operation only or lighting and message operation), the EIB 

motion detectors are connected with the following ©IQHOME.NET communication objects by 

means of the ETS object "Switching" or "Message/Alarm". Using the ETS, the ©IQHOME.NET 

acknowledgement object of the respective activation area (SSB1Quitt, SSB2Quitt, 

SSB3Quitt) must be entered into the "Switching" or "Message/Alarm" objects. 

All connected motion detector inputs are provided in the matrix (53) for selection (51). By 

simply ticking Yes in the matrix (53) you define whether the contact is assigned to an 

activation area (52) in the alarm system or nor. When you tick yes in one area, this motion 

detector input will be monitored. 

Different from the matrix of the contact inputs, motion detector inputs can not be set 

several times for different areas! 

Multiple assignment are only possible within one area (EMA/night). If you do try to assign 

one motion detector input to more than one activation area, a message window with the 

following text pops up: 

"This motion detector input has already been assigned to one activation area. Do you want to 

overwrite these settings? Please consider possible parameterisations at the motion detectors 

by means of ETS!" 

If the question is answered with "OK", previously made selections are deleted and the new 

selection is set. 

The status display (54) shows the current contact condition. The following status 

information (55) can be given: 

1. o.K. ("0" signal EIB-telegram 1Bit) 

2. Movement ("1" signal EIB-telegram 1Bit) 

3. Malfunction (formed internally by cycle monitoring) 

4. Activated! (when a "1" signal EIB-telegram 1Bit is detected with the alarm system being 

active) 

The cycle monitoring (56) is an extended monitoring function for high-priority message lines 

(e.g. when bus line is interrupted etc.). Enter a value greater „0“ (seconds) into the input 

mask (57) to activate the cycle monitoring. For example, when you enter "10" at the contact 

input 10 (40), the binary input must send at least one EIB telegram of the contact with the 

value „0“ or „1“ within 10 seconds. (cyclical sending must be set in the ETS at the binary 

input). If the value is not sent within the cycle time, there is a malfunction message for the 

sensor. (Malfunction). If a cyclically monitored input is assigned to an activation area which 

is active, such a malfunction will lead to an alarm(Activated) and the message "Burglar 

alarm" of the respective area is transmitted. When cycle monitoring sends a malfunction 

message, the malfunction LED (58) of the contact input flashes. 

Page 99


-o--o--o-- 

Page 100


EIB/KNX Data 


Within the project panning software the two-digit or three-digit EIB/KNX notation for group 

addresses can be used. 

EIB/KNX Alarm system data point list: 

Module AL001: 

The contact inputs 01-22 are available via module AL001 (information message inputs): 

Page 101


When delivered, there are already assigned group addresses, which you can adapt to your 

facility by using the project software to delete and replace them. Several group addresses 

can be assigned to one communication object. For details please refer to the technical 

manual "Project planning". 

Information message inputs (windows/doors/sabotage message etc.): 





Module AA002-AA003 

Motion detector inputs: 

Page 102

15 pcs. inputs, motion detectors: 


Module name: AA002-AA003 



Module AA001 

Area-related inputs and outputs: 

Area 1: 

Page 103


01 pc. input/output, activation/deactivation area EMA: 


Name communication object: SSB1EMA 


"1" = Activation 

"0" = Deactivation 

01 pc. area-related alarm output area1: 


Name communication object: SSB1Alarm 


"1" = Alarm 

01 pc. output, standby display area EMA: 


Name communication object: SSB1EMAbereit 


"1" = Activation possible 

"0" = Activation impossible 

01 pc. output, status area EMA (active/not active): 




"1" = System is active 

"0" = System is not active 

01 pc. output, LED-triggering at the activation device (yellow/ge) area1 EMA: 


Name communication object: SSB1LEDge 

EIB/KNX data point type: EIS1 (1Bit), pulse 3 seconds "1", when activation successful 

"1" = activation (countdown) has been successful (3 seconds "1", after that "0") 

01 pc. output, LED-triggering at activation device (green/gn) area1 EMA: 


Name communication object: SSB1LEDgn 

EIB/KNX data point type: EIS1 (1Bit), pulse 3 seconds "1", when deactivation successful 

"1" = deactivation has been successful (3 seconds "1", after that “0") 

01 pc. input/output, activation/deactivation area1 night: 


Name communication object: SSB1Nacht 




01 pc. output, standby display area1 night: 


Name communication object: SSB1Nachtbereit 




Page 104


01 pc. output, status area1 night (active/not active): 






01 pc. input/output, acknowledgement key (valid for EMA and night): 


Name communication object: SSB1Quitt 


Only "0" is sent and evaluated. 

Area 2: 

01 pc. input/output, activation/deactivation area2 EMA: 










"1" = Alarm 

01 pc. output, standby display area2 EMA: 






01 pc. output, status area2 EMA (active/not active): 






01 pc. output, LED-triggering at activation device (yellow/ge) area2 EMA: 




"1" = activation (countdown) has been successful (3 seconds "1", after that "0") 


Page 105





"1" = deactivation has been successful (3 seconds "1", after that "0") 













01 pcs. output, status area2 night (active/not active): 











Area 3: 

01 pc. input/output, activation/deactivation area3 EMA: 










"1" = Alarm 

01 pc. output, standby display area3 EMA: 




Page 106




01 pc. output, status area3 EMA (active/not active): 






01 pc. output, LED-triggering at activation device (yellow/ge) area3 EMA: 




"1" = Activation (countdown) has been successful (3 seconds "1", after that "0") 





"1" = Deactivation has been successful (3 seconds "1", after that "0") 













01 pc. output, status area3 night (active/not active): 









EIB/KNX data point output: EIS1 (1Bit) 


01 pc. output, flashlight (general): 


Page 107

Name communication object: SSBOptisch 


"1" = Active 

"0" = Not active 

01 pc. output, siren (general): 



Name communication object: SSBSirene 


"1" = Active with freely definable switch-off delay 


01 pc. output, sound (generally available for other applications, too): 


Name communication object: SSBSound 


"1" = Active 


1 pc. input/output, panic key (module outside lighting matrix) 

Module name: AB001 

Name communication object: Panik 


"1" = Active 


You will find all descriptions of the individual EIB/KNX communication objects in 


-o--o--o-- 

Page 108


Info-Alarm-Message 

Alarm- and Info-Message System 

-o--o--o-- 

Page 109


Purpose 


On your premises (house, flat, garden house) there will always be information about 

important equipment and facilities that are only available as status information. However, a 

careful check of even the most important messages is often neglected. (daily round). In 

addition to that, this information is often hard to access and check (within the heating 

control panel, at the pump operating panel behind the boiler, at the coarse surge protection 

under the house connection box or even in shafts). 

All this information can be put on the EIB/KNX system by means of binary inputs EIB/KNX 

(10V, 24V, 230V) or other suitable interfaces and transmitted for central visualization. 

Thus, a check round is no longer necessary. Reading the alarm list you can even see when a 

message was received or when and by whom this message was acknowledged. Furthermore, 

in case of an alarm, an SMS or mail can be sent to your mobile phone. 

-o--o--o-- 

Page 110


Features 


� Integrated message system for 13 alarm messages, incl. alarm manager with history 

administration (alarm list) and a pre-alarm as well as collective alarm output (master 

alarm) with variable delay (retriggerable) 

� All 13 alarm messages are administered separately in the alarm list 

� Acknowledgement function for single alarms and collective alarms 

� Automatic alarm list pop-up in case of alarm can be parameterized 

� Alarm status and number of incoming alarms are also displayed by the front start page of 

IQHOME.NET 

� 14 SMS alarm messages can be activated individually (13 single and one collective alarm) 

� Individual parameterizing of phone numbers by means of Admin Console possible during 

runtime 

� Status display for 22 info-messages, e.g. windows and doors 

� User-defined labelling of alarms and messages 

-o--o--o-- 

Page 111


Preconditions 


To use this module, especially the alarm console, the following is required: 

� To transmit SMS information the modem type recommended under www.eibmarkt.com 

should be used (Microlink 56k Fun USB). 

� Pre-configurated for D1/D2/EPlus (GSM/UMTS) networks, other networks can be 

integrated in the "Services" file that is also supplied. 

There are no other preconditions to use this module. However, there should be alarms & 

messages (1Bit) connected via binary inputs in your EIB/KNX facility (malfunction, alarm, 

status and operating messages), to display and process information. 

Note: 

Basically, it might be required to make special adjustments in your operating system & 

modem to permit SMS. We cannot give any support for this kind of specification. 


V.92-Internet-Modem with USB 

Ref. No.: N490020 


Manufacturer: Microlink 

Manufacturer Nr.: 56k Fun USB 

IQHOME.NET is equipped with an alarm and information message console which has already 

been pre-configurated for the SMS dispatch of 13 single alarm messages and 1 collective 

error message with services for the GSM/UMTS D1/D2 and E-PLUS networks. Other networks 

can also be integrated but have not been tested. Due to the complex activations and the fact 

that the parameters do not have a uniform standard for all modem types, the comprehensive 

tests have been run for one modem type which can thus be recommended here: Microlink 

Page 112


56k Fun USB (analog). Extract from the alarm and information message console 

IQHOME.NET. 

-o--o--o-- 

Page 113


Function description 


The surface of the alarm and und information message console consists of an operating page 

(Module AL001) with 13 alarm messages (inputs), 1 collective alarm (output) and 22 single 

messages (inputs, information messages): 

(01) Display of the 13 single alarm messages 

(02) Display of the respective individual labels of the single alarm messages 

(03) Condition of the alarm inputs 

(04) Display of the current delay time for the collective alarm 

(05) Nominal value for delay time (0-900 sec.) for the collective alarm 

(06) Remaining time display in % when delay and status LED are active 

(07) Remaining time display as text when delay and status LED of the collective alarm are 

active 

(08) Button to restart the alarm delay when delay is active 

(09) Administration menu for alarm bar (symbol "bell") 

(10) Display of the 22 information messages and the respective individual labels 

(11) Condition of the information message inputs 

(12) User-defined labelling of the alarm and information message console 

(13) Module designation for internal project planning (Designation is used in database for 

quick identification) 

(14) Navigation link main menu (button being pressed with active, flashing white LED 

below, if selected, our example "Tools") 


(button being pressed with active, flashing white LED below, if selected, our example " 

Alarm and information message console") 


(17) Display of alarm bar after call by means of administration menu for alarm bar (symbol 

"bell") (09) 

(18) Display of the active alarm messages with date and time 

(19) Display of the data point name (fixed) 

(20) Display of the user, who has eventually acknowledged 

(21) Display of a possibly integrated acknowledgement text 

(22) Call of the administration console (Start>Programmes>Elvis>Administration) to edit 

the message ports during runtime 

(23) Display of the currently integrated message recipients for SMS messages 

(24) Attribute window of an integrated message recipient in general (number input... [25]) 

(26) Attribute window of an integrated message recipient notification (assignment of the 

alarm messages to the message recipients) 

(27) Definition of the message assignments to the selected message recipients: MG1 = 

message group1 = alarm message01 

Page 114


Page 115


Page 116

Alarm console function logic (01) 


In the alarm console the connected alarm inputs (01) (see EIB/KNX data point list) are 

monitored with a leading edge (logic "1" [Bit]). It is not important whether the alarm inputs 

are completely occupied or only a single alarm message is connected. The alarm messages 

must be set to "read" at the binary input (read flag ETS). W hen the input is sent (logic "1" 

[Bit]), the respective red LED (03) flashes and the alarm console with the collective alarm 

starts the following functions: 

A possibly adjusted delay time (04)(05) starts and the message LED "Alarm is coming" 

(pre-alarm) (06) is activated. This pre-alarm is sent on the EIB/KNX. The current remaining 

time until master alarm activation (collective alarm) is indicated (06). By pressing the 

button "Restart alarm console (Retrigger)" (08) the delay stage with the current parameters 

(04)(05) is restarted. This data point is also available via EIB/KNX (Quitttung SSM 

Alarmkonsole). The acknowledgement by means of an external EIB key must be 

parameterised in the ETS as follows (press "On", let go "Off" or adjust "Off only" (value logic 

"0" [Bit] for each transmission). 

After delay time completion the master alarm (collective alarm) (07) is activated and a 

telegram (logic "1" [Bit]) is sent on the output object SSM Alarmkonsole. The message 

"collective alarm" is now indicated in the alarm list together with time and date (17). 

For the master alarm output (collective alarm) it is not important whether an alarm input is 

sent cyclically or not. A master alarm modification (collective alarm) on the EIB/KNX Bus 

only occurs in case of a value modification of the total linkage result for the master alarm 

(collective alarm). 

W hen the alarm list is set to automatic display in case of alarm (09), this is indicated on 

every visualization page in form of an alarm list (17) for active single or master alarm. In 

addition to that, a sound or *wav file can be played. 

An active single alarm message (logic "1" [Bit]) is immediately entered in the alarm list and, 

if required, a respective message port (e.g. SMS) (22) is activated to send a message to a 

message recipient (23). 

The following SMS message ports were provided with standard message texts (can be 

changed freely) and be assigned to two (when delivered) or any number of message 

recipients. The SMS function is not active when the unit is delivered and must be 

parameterised by means of the admin console, if required. 

The following assignments have already been defined: 

1. Alarm message 01 = message group 01 (MG 01), message text: "IQHOME.NET: Alarm 

message 01 is active!" 













Page 117














14. Collective alarm = message group 14 (MG 14), message text: "IQHOME.NET: Alarm 

message 14 (main alarm) is active!" 

15. Sensor SSM = message group 00 (MG 00), message text: "IQHOME.NET: Alarm message 

00 (weather sensor system) is active!" This alarm output is not integrated in the alarm 

and information message console. Thus, the message is only shown optically in the alarm 

list or on the start page. The alarm output "Sensor SSM" is not considered in the delay 

stage of the function logic. The alarm output "Sensor SSM" is released and sen on the 

EIB/KNX when at least one cycle monitoring of an activated sensor input has been 

switched on in the sensor system toolbar and the monitored sensor input has not sent a 

telegram within the cycle time adjusted. 

16. Alarm message 15 = message group 15 (MG 15), message text: "Alarm Message 

area_01" (burglar alarm area 1) 

17. Alarm message 16 = message group 15 (MG 16), message text: "Alarm Message 

area_02" (burglar alarm area 2) 

Alarm message 17 = message group 15 (MG 17), message text: "Alarm Message area_03" 

(burglar alarm area 3) 

Page 118


(22) Calling the administration console (Start>Programmes>Elvis>Administration) to edit 

the message ports during runtime 

(23) Display of the currently integrated message recipients for SMS messages 

(24)Attribute window of an integrated message recipient in general (number input... [25]) 

(26) Attribute window of an integrated message recipient notification (assignment of the 

alarm messages to the message recipients) 

(27) Definition of the message assignments to the selected message recipients: MG1 = 

message group1 = alarm messge01 

Alarm list (17) 

In the alarm list (open see: view-menu) the alarm file entries are indicated. You can filter 

which alarms are shown: 

� all: all alarm messages are shown in the list 

� active: only currently active alarm messages are shown in the list 

� not acknowledged: only alarm messages that have not been acknowledged are shown in 

the list 

� Since: date starting from which the entries are shown. To display the alarm 

status the following symbols are used: 

Page 119


the upper limit has been exceeded 

the lower limit has been fallen short of 

the alarm has been acknowledged 

the value is (again) within the admissible range 

In addition to that, the time and a designation are given in the list. For acknowledgements 

the user and perhaps the acknowledgement text are given. An alarm can only be 

acknowledged as long as it is active. Double-click on an alarm in the list to open the 

acknowledgement dialogue. Here you may also enter a comment message text. 

Information message console (10)(11) 

The information message console serves as a central and clear display of any message such 

as status message (doors, windows etc.). A maximum of 22 EIB/KNX information message 

inputs can be administrated. The information messages must be set to „Read“ at the binary 

input (read flag ETS). In case of release, the integrated status displays (yellow LEDs) 

respond (logic "1" [Bit]) as active brightly shining yellow LED (11). These messages are not 

processed in the alarm console or shown in the alarm list. However, integration in the alarm 

list or SMS can be realized using the project planning software in the database. All 

information message texts (10) can be created as you like by means of the label editor 

(separate page) (16). 

Labelling the alarm and information message inputs (16) 

Labelling the alarm and information message inputs permits orientation of the user. The 

label can be modified on another page. 

-o--o--o-- 

Page 120


Page 121




Within the project panning software the two-digit or three-digit EIB/KNX notation for group 


EIB/KNX data point list alarm and info message console: 

Module AL001: 

Alarm inputs: 

Page 122


When supplied, all group addresses are entered as standard, which you can adapt to your 

facility conditions by deleting or replacing using the project planning software. Several group 

addresses can be assigned to one communication object. You will find detailed information in 

the technical manual "Project planning". 

13 pc. inputs, alarm messages: 


Name communication object: Alarmmeldung 01 - Alarmmeldung 13 


Information message inputs: 

Page 123






Acknowledgement input (restart alarm console (Retrigger)): 

1 pc. input, acknowledgement alarm console (restart alarm console [Retrigger]): 


Name communication object: Quitttung SSM Alarmkonsole 


Alarm outputs: 

Page 124

1 pc. output, "Pre-alarm": 


Name communication object: Alarm kommt 


1 pc. output, "Master alarm": 



Name communication object: SSM Alarmkonsole 




-o--o--o-- 

Page 125


Outside lighting matrix 


-o--o--o-- 

Page 126


Purpose 

Outside Lighting Matrix 

The outside lighting matrix serves for function administration of a 10 channel- outside 

lighting control with variable function combination. Here we use 4 internal timer clocks, 1 

twilight switch from a selection of max. 7 sensor inputs, 5 motion detectors with or without 

brightness influence and 1 panic function. 

When building their own house many owners are worried about problems other than their 

electrician’s question: where to put which outside lamps, and how and from are these lamps 

to be switched on and on which conditions? 

The answer: .(...) it does not matter because we are using the EIB advantages and can 

change programming at any time.(...). But also the programmer wants to start his work 

because when the owners move into their new home, the outside light should work 

„somehow“. 

Subsequent modifications are often made as follows: 

The owner does not like the function of the gate lamps and contacts the EIB-programmer. 

They fix an appointment, the modifications are made and cost money. Two days later the 

lady of the house thinks it was somehow better as it was before but we should. (...), the 

story starts again! 

That is why we have looked for a possibility to change the „programming“ without any 

programming tools or any special knowledge at any time. The result is a „Matrix“ (linkage 

table) where all usual functions of up to 10 outside lights can be administrated. The operator 

defines linkages with „Yes/No“ which would otherwise include a great deal of work. 

The following modifications can be made by the operator themselves: 

� Changing the switching times with a better operating comfort than before 

� Changing the twilight limit 

� Changing the switch-off delay of the twilight switch 

� Changing the twilight/clock function 

� Variable assignment of 4 twilight/clock functions to the outside lamps (matrix 40 

channels) 

� Variable assignment of max. 5 motion detectors to the outside lamps (matrix 50 

channels) 

� Changing the motion detector function 

� Using the panic function (alarm system control) 

-o--o--o-- 

Page 127


Page 128


Features 


Control of up to 10 different switching groups with the following functions and attributes: 

� 10 channel outside lighting matrix with 9 control channels each (4 automatic programs & 

5 motion detector programs). Thus, complex, individual scenes are possible. 

� Total scene memory as back up memory (Load from or to Standard) 

� Each of the 10 outside lighting channels can be assigned to a selection of control 

channels, these always represent an „OR“- link 

� Each of the 10 outside lighting channels has an operating mode switch with the operating 

modes „Automatic“, „Manual operation ON“, „Manual operation OFF“ and „No function“ as 

well as a clock program for automatic switch-over of the operating modes. 

� Status display of the basic situation and direct switching possibility 

� 4 separate control channels „Time switch/Twilight“ with the functions „ON“, „OFF“, 

„Twilight only“, „Clock only“ as well as „Clock + Twilight“ 

� 5 separate control channels Motion/Twilight with the function „Motion“, „Motion + 

External twilight sensor“, „Motion + Twilight sensor of the motion detector“ and „OFF“ 

� User-defined labelling of the outside lighting channels 

-o--o--o-- 

Page 129


Preconditions 


Preconditions for the function of this control matrix are as manifold as their own functions. If 

you intent to use the integrated twilight function, you either need an EIB/KNX brightness 

sensor in lx or klux or a EIB/KNX (2Byte) twilight switch or a twilight switch of the 1Bit type. 

If you do not need a twilight function, these inputs are not significant. The same refers to the 

max. 5 motion detector inputs. If you want to control your facility only depending on time 

and light, no motion detectors are required. Without all inputs (brightness/twilight and 

motion detector) the matrix still represents a 4 to 10 channel clock distributor with panic 

function (alarm system). 


Description 

Weather station EIB/KNX 

Ref. No.: N300057 


Manufacturer: THEBEN 

Manufacturer Nr.: 132 9 200 

• Records wind speed, rain, brightness and temperature 

• The measured variables can be transmitted directly on the bus. 

• Wind speed, brightness, temperature are transmitted as values, rain as 1 bit 

• Wind speed can be transmitted either in m/s or km/h 

• The data are evaluated in the device itself 

• Powered from bus voltage, 230 V are required if rain sensors are used 

• Brightness range 1–100,000 lux 

• Temperature range –20 °C ... +55 °C 

• 4 universal channels (AND linked) 

• 3 sun protection channels (specifically for blind and shutter application) 

• A teach-in feature for the brightness threshold is available. It enables thresholds to be set 

retrospectively by the push of a button without the device having to be reconfigured. 

• Integrated bus coupler 

• Integrated heater for rain sensor 

Page 130


• Automated sun protection mechanism for independent control of blind, awning etc. 

• The teach-in features are user-friendly and enable the customer to retrospectively define 

the threshold with the touch of a button. This does not require the weather station to be 

re-configured. 

• The automated sun protection mechanism independently controls the blind 

(shutter/awning) during the day, no manual intervention necessary. When a threshold is 

reached, two separate messages can be sent, e.g. for height and slat of a blind or a value 

and switching message. 

• The different channels can have any configuration 

Benefits 

• The only EIB/KNX weather station that records and evaluates all variables in one housing. 

• Device is connected directly to the bus, no other cables need be laid. 

-o--o--o-- 

Page 131




(01) Sensor selection for twilight function 

(02) Current value of the control channels „Timer clock" programmes 1-4 (call via [19]), 

by pressing the key, manual operation of the clock till the next switching telegram 

possible 

(03) current value of the control channels "Motion detector inputs" 1-5, by pressing the key, 

manual motion detector operation till the next 

switching telegram possible 

(04) Function definition of the control channels "Timer clock/twilight", can be switched over 

by pressing the key: "Permanent off", "Permanent 

on", "Timer clock-controlled", "Twilight-controlled", "Timer clock and twilight-controlled" 

(05) Function definition of the control channels "Motion detector", can be switched over 

by pressing the key: „Motion“, „Motion + Twilight sensor“, 

„Motion + Twilight sensor of motion detector“ and „OFF“ 

(06) Function matrix to assign the outside lighting channels to the function definitions 

(07) User-defined labelling of the outside lighting channels 1-10 

(08) Operating mode switch of the outside lighting channels 1-10, can be switched over 

by pressing the key: „Automatic“, „Manual operation ON“, „Manual operation OFF“ 

and „No function“ 

(09) Status displays of the outside lighting channels with manual direct switching 

(10) Current value display with limit value adjustment 

(11) Setting the switch-off delay (AVZ 0-900s) in case of limit shortfall 

(twilight), the display above serve to indicate a sensor malfunction 

(12) Remaining time display in % with active delay and status LED when twilight is active 

(13) Remaining time display as text with active delay 

(14) Tools for using the matrix: "Reset" the matrix table (empty), "Save" the matrix table 

(saves the current setting), "Load" the matrix table 

(loads the last saved ("Save") matrix data and ("Panic") 

(Man. release of the panic function at the outputs 1-10) 

(15) Module designation for internal project planning 

(Designation is used in the database for quick identification) 

(16) Navigation link main menu 

(Button being pressed with active, flashing white LED below, 

if selected, our example "Outside light") 

(17) Navigation link submenu outside light 


if selected, our example "Matrix") 

(18) Navigation link submenu settings 


if selected, our example "Sensor system toolbar") 

(19) Calling the timer clock programmes for the control channels „Timer clock" programmes 

1-4 (base menu) 

(20) Calling the timer clock programmes for the automatic operating mode control (08) 

of the outside lighting channels 1-10 


Page 132


Sensor selection for outside lighting control (01) 

Individual input values (brightness sensors EIB/KNX) can be used for the outside lighting 

matrix. Selection is made using the drop down menu (01). Depending on the number of 

sensors in your EIB/KNX facility and the sensors that have been connected as inputs to the 

sensor system toolbar, these sensors are provided for selection in the drop down menu. If 

there is no active sensor, the twilight is set internally to active (safety reasons). It is only the 

initialisation of a measured value that starts a new calculation and a current linkage result is 

sent. 

Labelling the outside lighting channels (07) 

The label of the outside lighting channels serves for user orientation. The label is modified on 

another page. 

Function matrix (06) 

With the function matrix the real connection between the control channels (02),(03) and 

the outside lighting channels (09) is established. A control channel can only influence an 

outside channel after it has been ticked accordingly in the matrix. Several ticks per outside 

channel represent an OR function, i.e. as soon as a ticked control channel is active the 

outside channel can be controlled. An outside channel can only become inactive, when all 

Page 133

ticked control channels are inactive. 


Operating mode switch of the outside lighting channels (08) 

The operating mode switches are applied to influence the channel operating mode without 

constant changes of the function matrix. The operating modes include: „Automatic“, „Manual 

Off“, „No function“ and „Manual On“ and are switched in the following sequence as soon as 

the key is pressed: 

The operating modes (08) have the following functions: 

Automatic 

The output (08) follows the conditions of the control channels (02)(03) as defined in the 

matrix. The panic function (14) can also access the output channel. 

Manual Off 

The output is always off, but the panic function still has access to the output channel. 

Manual On 

The output is always on. 

No function 

The output is no longer triggered by the outside lighting matrix. If other sensors (push 

button switches etc.) in the EIB system that for instance do not have direct access to the 

respective actuator channel and do not respond via matrix, the switching commands are 

overwritten by the matrix without fixed cycle. This results from the fact that modification at 

the inputs (twilight switch, clock, motion detector) lead to new calculations of the matrix. If 

the status of the external sensor (push-button switch or similar) at the actuator is to be 

kept, this operating mode must be chosen. 

Time-depending operating mode switch-over 

A second timer clock (20) was provided for the matrix to control the operating modes of the 

individual channels. The applicable value range is 0..3. The values correspond to the 

following operating modes: 

Value 0 = manual Off, 

Value 1 = No function 

Value 2 = Manual On 

Value 3 = Automatic 

Values outside this value range will be ignored. The operating mode set at last remains 

unchanged. 

Page 134


Examples for the use of the operating mode timer clock for repeated processes: 

The lighting (neon lamps) of a loading bay in a small company is switched on by means 

of a control channel (Timer clock/twilight) from the beginning of twilight until 10 p.m. 

After 10 p.m. a second control channel (motion detector) takes over this function. On 

Mondays and Wednesdays a delivery service delivers goods at 11 p.m. Unloading takes 

approx. 30 minutes. The constant motion detector switching disturbs. Using an operating 

mode timer clock the operating mode „Manual On“ (9.55 p.m.) and after that „Automatic“ 

(10.35 p.m.) could be selected at the respective times. 

Status display of the output (09) 

This display is in direct connection with the actuator and indicates, as far as no other 

addresses have been programmed at the actuator channel, the switching condition of the 

actuator. To ensure a correct status message of the actuator its read flag must have been 

set. If the actuator disposes of status feedback messages, this group address must also be 

entered at this object as sending and with read flag. In this specific case the read flag at the 

input object of the actuator must be deleted. If you generate a separate group address for 

the feedback message, it must be entered in the respective communication object in the 

project database as second group address and set to reading by giving the sign ">" At the 

communication object "Feedback" of the actuator the read flag must be activated. 

The output status display was designed to be operated. Thus, a user may also access the 

actuator directly. 

Control channel/ timer clock/twilight (02)(04) 

There are 4 similar, freely definable control channels timer clock/twilight to trigger the 

matrix. 

Example clock active (LED on, flashing) and inactive (LED off) 

The inputs „On“, „Off“ and „Twilight“ of all control channels are identical. A difference of 

the control channels lies only in the use of different timer clocks (19). Furthermore, 

there is the option to set the function of each control channel separately. Using different 

timer clocks and setting the different function of the control channel separately permits 

to control outside lighting areas in a different ways (entrance area, inner court, garage 

driveway etc.). 

Description of the functions 

Page 135

Function „Timer clock/twilight“: 


The most common outside lighting function is „Timer clock/twilight“. 

The switching times for this function could be as follows: daily 6 a.m. On, 10 p.m. Off. 

The outside lighting would have the following functions: 

6 a.m. timer clock switches on ---> light On 

in the morning, twilight switch sends „Day“ ---> light Off 

in the evening, twilight switch sends „Night“ ---> light On 

10 p.m., timer clock switches off ---> light Off 

If the twilight switch sends „Day“ before 6 a.m., no light is switched on in the morning. 

Function „Twilight only“ 

An outside lighting operated in this way would switch on in the evening and off in the 

morning (e.g. number at entrance gate). 

Function „Timer clock only“ 

An outside lighting operated in this way would switch on and off according to the switching 

times defined in the respective timer clock channel (e.g. illuminated Christmas tree in 

garden). 

Function „On“, „Off“ 

These functions are only meant to complete the range and can be used to switch whole areas 

(all outside lightings that are connected with this control channel) immediately on or off (e.g. 

to check the function of all lights by day etc.). 

Control channels „Motion/Twilight“ (03)(05) 

There are 5 similar control channels Motion/twilight to trigger the matrix. 

Example motion detector active (LED on, flashing) and inactive (LED off) 

Page 136


An outside lamp group (1-10) connected with this control is controlled additionally or 

separately depending on the motion detector. It is possible to set the function of each 

individual control channel separately. 

Function „Motion“ 

For matrix activation the output signal of a motion detector or a motion detector group 

(Master- Slave) is used directly. For control, the setting of the local motion detector (with or 

without twilight function) is taken. 

Function „Motion/Twilight“ 

The output signal of a motion detector or a motion detector group (Master- Slave) is AND 

linked with the matrix-own twilight switch. 

Only as soon as the twilight switch signalises „Night“, a motion signal leads to the activation 

of the control channel output (1-10). 

Function „Off“ 

The control channel in inactive. 

Why are there the two functions „Motion“ and „Motion/Twilight“? 

If all outside lighting channels are to work starting from a uniform twilight value (because it 

looks better), the function „Motion/Twilight“ must be selected. This function has 

another advantage: the motion detectors can be operated irrespective of the brightness and, 

thus, also be used by day to capture any motion (presence function).However, if it is 

necessary to activate a lamp in a certain area, such as roofed outside area with not much 

natural light, earlier than the other outside lamps, you can make use of the motion detector ’ 

s own brightness function. Since the twilight function is already included in the input 

signal of the control channels, the channel function must be set to „Motion“. 

Twilight switch (10) 

The twilight switch consists of a combination device to display the current value (yellow bar) 

and the nominal value (red triangle) as well as the nominal value adjustment. The scale 

readings have been designed according to the expected value with up to 1000 lx. Each 

modification of the nominal or current value results in a new calculation of the output value, 

Page 137


which is given to the delay stage for further processing. The delay stage consists of a 

switch-off delay, which can be adjusted by means of the rotary regulator (11) from 0..900 

seconds. With active twilight (12), the current remaining time in % is indicated by a status 

LED the delay being active. Furthermore, the remaining time is also given as current text 

(13). 

Switch–off delay means: If outside brightness gets higher than the set nominal value, the 

twilight switch will switch off and, thus, the respective connected outside lighting channels 

will switch off as well. However, this only happens later after completion of the delay time. If 

brightness falls below the set nominal value, the outside lighting channels assigned in the 

matrix are switched on at once. 

with the switch-off delay brightness fluctuations (dark clouds etc.) are efficiently 

compensated. The LED bar (12) indicates the current status of the delay. The LED (12) 

shows the output status of the delay stage. Its output status corresponds to the signal that 

all control channels receive as signal „Twilight“ for further processing. The current delay is 

shown by switched on LED’s in the LED row. The switched on LED’s give the remaining time 

in %. Under (13) the remaining time is shown as text. 

If a user/owner has chosen the slightly cheaper version with a simple (1 Bit) or conventional 

twilight switch to be connected to a binary input, the system also includes this option. Here, 

we have to work without the luxury to parameterise the brightness limit. The delay stage 

remains but the limit must be set as fixed using the ETS. 

Tools to use the matrix (14) 

Because of the complex adjustment options, we have integrated a scenery memory for the 

matrix (04)(05)(06)(08), to protect its standard settings from unintentional modifications 

or to load temporary modification with the standard matrix again. 

The following options are provided: 

"Reset" of the matrix table (empty the matrix table), "Save" the matrix table (stores all 

current settings), "Load" the matrix table(loads ("Save") the matrix data stored last, "Panic" 

(Man. release of the panic function at the outputs 1-10, basically, an existing or future EIB 

alarm system matrix responds to this function) 

The function influences the following matrix components: 

(04) Function definition of the control channels "Timer clock/Twilight", can be switched over 

by pressing the key: "Permanent Off", "Permanent On", "Timer clock-controlled", 

"Twilight-controlled", "Timer clock and twilight-controlled" 

(05) Function definition of the control channels "Motion detector", can be switched over by 

pressing the key: „Motion“, „Motion + Twilight sensor“, „Motion + Twilight sensor of the 

motion detector“ and „OFF“ 

(06) Function matrix to assign the outside lighting channels to the function definitions 

(08) Operating mode switch of the outside lighting channels 1-10, can be switched over by 

pressing the key: „Automatic“, „Manual ON“, „Manual OFF“ and „No function“ 

Page 138

Additional technical information: 


Under „Sensor system toolbar“ you can also adjust whether the cyclical signal of a sensor is 

to be monitored (see also „Sensor system toolbar“). If the set monitoring time is exceeded, 

the status of the respective sensor channel reports a malfunction. If there is a malfunction of 

the sensor selected in the matrix, a measured value of 0 lx is indicated and processed (i.e. 

anyway it is "too dark" and the respective outside lights should go on) and the display (11) 

shows „Sensor malfunction“. If you now use the sensor selection to choose a functioning 

sensor, its measured values as well as malfunction status will be displayed and processed. 

Furthermore, it should be considered that all measured values have the same base, see 

„Sensor system Toolbar“ 

-o--o--o-- 

Page 139




Within the project planning software the two-digit or three-digit EIB/KNX notation for group 


EIB/KNX data point list outside lighting matrix: 

Module AB001: 

Inputs: 

Page 140






5 pc. inputs, motion detector: 


Name communication object: AUB BM1 - AUB BM5 


Panic key (to be connected to panic functions, e.g. alarm system): 

1 pc. input/output, panic key: 


Name communication object: Panik 


Outputs: 

Outside lighting channels (1-10) and timer clock channels for automatic operating mode 

change-over: 

Page 141

10 pc. outputs, outside lighting channels: 



Name communication object: AUB Leuchte 1 - AUB Leuchte 10 


10 pc. Outputs Timer clock channels operating mode change-over: 


Name communication object: AUB Leuchte 1 BAext - AUB Leuchte 10 BAext 

EIB/KNX data point type: EIS14.000 (1 Byte) 

Sensors: 

You will find the available EIB/KNX inputs (sensors) on the page "Sensor system toolbar" 

under "EIB/KNX data point list". 

Hint: 

If you want to use the timer clock outputs (delivery condition "virtual", that is internal data 

points) of the programmes 1-4 (02) also for processing on the EIB, do not forget to activate 

the EIB Port "Connection" for this data point first. When output on the EIB is activated for 

this data point, a group address must be entered and a recipient must exist in the EIB 

system (key or similar) to acknowledge the telegrams. If there is no recipient, the timer 

clock is always switched off. 

For EIB output the "Type" must be set to "EIB Schalter" or "EIB Schalter CO" (each action is 

sent), the "Port" must be set to "EIB" and under "Address" there must be an EIB group 

address (must absolutely be present in the system when used!). 

Page 142

Condition when delivered 




-o--o--o-- 

Page 143


Operating Console 

Operating Console & Presence Simulation 

-o--o--o-- 

Page 144


Purpose 


The operating terminal permits direct operation, display and control of a maximum of 80 pcs. 

switchable (1Bit) devices (lamps, sockets etc.) and 6 pcs. dimmable devices (1Byte) by 

means of a push-button switch/rotary regulator, timer clock or presence simulation 

programme. With its central and clear display up to 40 switching groups can be operated per 

page. Using a navigation arrow you can jump to the next page to administrate the other 40 

switching groups or dimmable lighting groups. 

In a high-quality one-family house with EIB/KNX, depending on its size (100m² to 300m²), 

an average of approx. 300-500 data points (group addresses) are processed during the 

visualization. About 40-80 of these group addresses are required for indirect, local switching 

actions (lighting, sockets etc.). 

The operating terminal with presence simulation can be applied to carry out certain switching 

actions, to display the current situation or to integrate automatic functions. The presence 

simulations simulates usual activities in your house while you are absent to protect your 

property from potential burglars. 

-o--o--o-- 

Page 145


Features 


Direct operation, display and control of max. 80 pcs. switchable (1Bit) devices (lights, 

sockets etc.) by means of push-button switch, timer clock or presence simulation programme 

with the following functions: 

� Operation and status display for 80 switchable outputs (lights/sockets etc.) 

� Operation and status display for 6 dimmable outputs 

� All dimmable and 8 defined switchable groups are integrated in the scenario manager 

with 8 scenes 

� A clock channel is assigned to each switching channel that can be activated in the special 

program >presence simulation< 

� The clock channels of the dimmable outputs are also dimmable 

� Each of the 80 switching and 6 dimming groups disposes of its own time switch program 

� Here, different operating modes can be activated, e.g. the presence simulation with freely 

editable switching dates and activities. 

� Once parameterized, the presence simulation program can be started automatically when 

you are away (holidays etc.) and acts according to your instructions only. It is also 

possible to provide other specific programs according to your wishes and requirements. 

� User-defined labelling of the switching outputs 

-o--o--o-- 

Page 146


Preconditions 


There are no specific requirements to use this module. There must only be switchable (1Bit) 

devices, controlled by switching actuators (binary outputs) in your EIB/KNX facility. 


8-fold switch actuator EIB/KNX SA.8.16, 

MDRC, (6x16A man., 2x8A) 

Ref. No.: N000200 



Very high quality and unique price-/ performance relationship! 

The binary actuator SA.8.16 receives data frames via EIB and, with its potential-free, 

independent relay contacts, switches up to 10 groups of electric devices. Different outer 

conductors can be connected to the outputs A1-A6. The channels A1-A6 contain polarized 

latching relays (for capacitive load up to max. 140 µF and lamp load up to max. 2500 

W, further details see data sheet relay).One outer conductor each can be connected to 

the outputs A7 and A8. The channels A7 and A8 dispose of a change-over contact each 

(Opener/Closer). 

Comprehensive functions permit several possibilities for parmeterization, such as: 

� Switching behaviour of the relays (Open/Close) 

� Operating mode of the relays (switching, switching with feedback) 

� Definition of switching condition in case of bus failure and recovery 

(unchanged/open/closed) 

Page 147


� Characteristics of the feedback objects (Status, Send, Inverting) 

� Logical connections (AND, OR) 

� Inverting the connected object (Yes/No) 

� Definition of the input objects for bus voltage recovery (logical "0", "1" or read "via EIB") 

� Time function On and/or switch-off delay 

� Time function staircase lighting (retriggerable) with optional switch-off warning 

and service function (Cleaning light) 

� Time function staircase lighting with abort option by means of "0" frames 

(for currently active time function) 

� etc. 

Using the slide switches 6 relays (output 1-6) can be switched on or off directly by hand 

parallel to EIB, KNX TP1 or even without EIB, KNX TP1. In addition to that, these slide 

switches serve to show the current switch position. The 8-fold binary actuator SA.8.16 is a 

device to be fixed on a 35mm DIN-bar and to be installed in electric distributors. In 

combination with the product database and the ETS-Software the actuator serves to switch 

up to 10 independent groups of electric devices with different functions each. Several 

different software settings permit application of logical connections, switch-on and off delays 

and staircase lighting functions with adjustable switch-off warning. Besides the option to 

switch the connected devices in a defined way in case of a bus malfunction, it is possible to 

update the current object values in case of a bus recovery. Power supply of the device is 

provided exclusively via the EIB, no other power supply is required. Connection to the 

bus (EIB, KNX TP1) is ensured by means of the supplied bus terminal. Connection of the 

devices is ensured by means of integrated screw terminals. The outputs A1 to A6 are capable 

of switching loads with a current of up to 16 A by means of potential-free contacts. Using the 

switch position displays of the outputs A1 to A6 it is also possible to switch the connected 

load circuits manually - even in case of bus failure. The outputs A7 and A8 switch loads with 

a current of max. 8 A. Doing so, two groups of devices each can be switched potential-free 

with one opener and one closer. (change-over contact). 

EIB basic set 64 channel, incl. logic module 

and power supply 

Ref. No.: e160 



The basic set has been designed for basic equipment with the most important 

components at a reasonable price! 

The basic kit can be programmed very normally with the ETS2 and ETS3 PRO. 

EIB basic set 1 plus consists of: 

Page 148


1 pc. Power supply unit with throttle, 

1 pc. Power supply unit to supply the interface modules, 

2 pcs. Universal input and output concentrator 32-fold EIB (EIB-Interface), 

"n" pcs. Binary outputs 8-fold 230V,manual operation, RM, 16A/10A, 

"n" pcs. Binary inputs 8-fold 24V-AC/DC, 

"n" pcs. Binary inputs 8-fold 230V-AC, 

2 pcs. Connecting lines VL-1 (to connect the interface modules with the concentrator) 

1 pcs. Logic modul (For complex control functions.) 

8 pcs. Connecting comb 8-fold 

Info: 

With this set you dispose of hardware to install a complete EIB line as well as the above 

delivery volume. The package includes 64 pcs. channels to operate devices (lamps, sockets, 

heating valves etc.), or 64 pcs. channels as bus inputs (window contacts, malfunction 

indicators, push-buttons etc.), or a mixed configuration of binary inputs and binary outputs 

because from now on you can determine yourself the type and quantity of binary inputs 

8-fold or binary outputs 8-fold you require without any extra costs. 

Universal Dimming actuator 

2-fold, MDRC 

Ref. No.: N167607 



Manufacturer Nr.: 3602REG 

The universal dimming actuator receives telegrams for switching or dimming purposes. It 

can work with the principle of trailing or leading edge control. That means either low voltage 

halogen lamps with TRONIC transformer or conventional (inductive) transformer can be 

controlled. The max. capacity can be extended by using power amplifiers (see main 

catalogue).Depending on the parameter it is possible to activate various additional functions. 

-o--o--o-- 

Page 149




The surface of the operating terminal consists of several operating pages (Module LI001 & 

LI001_D as well as LI002), whereas the modules LI001 % LI002 consist of 40 pcs. keys with 

assigned LED, label text and separate timer clock programme as well as presence simulation. 

The dimmable lighting groups are assigned to the module LI001_D. 

(01) Texts describing the individual switching groups 

(02) Key with status LED for the respective switching group 

(03) This switching group (special colour) is included as additional function in the scenery 

control (Scenario Manager). 

(04) Additional advice 

(05) Calling the timer clock channels for lighting groups 01-40, incl. presence simulation 

(06) Calling the timer clock channels for lighting groups 41-80, incl. presence simulation 

(07) Navigation link to the next module page with the switching groups 41-80 

(08) User-defined labelling 

(09) Display of the current system time & date 

(10) Module designation for internal projects (designation is used in the database for quick 

identification) 

(11) Information about the current page 

(12) Navigation link main menu (button being pressed with active, flashing white LED 

below, if selected, our example " Lighting") 

(13) Navigation link submenu switchable and dimmable lighting groups 

(button being pressed with active, flashing white LED below, if selected, our 

example "Operating terminal & presence simulation") 


The function to operate the push-button switches is self-explanatory. The push-button 

switches are designed in "ON/OFF" function. That means pressing the push-button switch 

reverses the previously active condition. Press "On", press "Off", Press "On" ... and so on. 

When delivered, the group addresses are read by each switching group as soon as the page 

is called (demand) to give the real facility condition. To control an additional switching group 

by the timer clock, the respective timer clock must be called (05, 06). In the timer clock 

programme (05) the channels of the switching groups 01-40 and in the timer clock 

programme (06) the channels 41-80 are provided (This programme is also applied to select 

and activate the presence simulation for the respective channel). The presence simulation 

events must be defined once for the whole day. To start (e.g. holidays or longer absence) 

this specific programme is simply activated using the menu point "Select time programme". 

Starting from this time, normal timer clock programmes are inactive for all switching groups. 

Only the simulation programmes are valid. 

Page 150


Page 151


The assigned channel names in the timer clock programmes can be changed by means of the 

project software (data point text). They are not taken over automatically via the label editor. 

This refers to all timer clock programmes. 

Page 152


Page 153


-o--o--o-- 

Page 154




Within the project planning software the two-digit or three-digit EIB/KNX notation for group 

addresses can be used, whereas you may enter several group addresses. The "sending" 

address is always the first address. Separation is achieved with a semicolon ";". 

Page 155


EIB/KNX Data point list operating console & presence 

simulation: 

Module LI001 - LI0002: 

When supplied, group addresses are entered as standard, which you can adapt to your 




As a standard, it is always the first group address that is read on "Demand" (page call) or 

"Running -up" (server start). However, if for example an assigned feedback address is to be 

read, a ">" sign must be set. In this specific case the second group address is read instead 

of the „sending“ address: 

Page 156


40 pcs. outputs with status LED & clock programme module LI001: 

Module name: LI001 

Name communication object: Leuchte S01 - Leuchte S40 


40 pcs. outputs with status LED & timer clock programme module LI002: 


Page 157


Name communication object: Leuchte S41 - Leuchte S80 




-o--o--o-- 

Page 158


Reminder function 


-o--o--o-- 

Page 159


Purpose 


The integrated reminder editor serves to show recurring actions. This could be any reminder 

that is important to you. The reminder editor manages max. 10 reminder texts. A free text 

as well as a year timer clock with the respective date definition is assigned to each reminder. 

When the reminder date is reached, a message (new window) appears showing your 

personal text. 

W hen ©IQHOME.NET is applied on a touch screen monitor (e.g. wall installation), such a 

reminder can be viewed immediately by everyone. As an option it is also possible to give the 

reminder text as a spoken text (Elvis Tel programme extension module required) by means 

of the sound board and perhaps to transmit this message to an existing sound system in the 

house (example WHD). 

-o--o--o-- 

Page 160

Message of 10 arbitrary reminders: 


Features 


� 10 channel reminder editor 

� A free reminder text is assigned to each reminder 

� A year time switch is assigned to each reminder to permit date definition 

� In the editor, a test button for manual date release is assigned to each reminder 

� Automatically generated message window (New Window) when reminder date(s) is/are 

reached 

� Active reminders are shown in the reminder window with time and date stamp 

� Using the button you can browse through several active reminders 

� Automatic linking to the previous active visualization page after acknowledgement of the 

last active reminder 

-o--o--o-- 

Page 161


Preconditions 


There are no other requirements to use this module since this module does not require any 

EIB/KNX hardware. Only when the data points are activated as EIB Port, the reminders are 

also sent as EIB telegram on the bus. In this case you will need a "recipient" in your bus 

system. When delivered the memory editor data points are "virtually" pre-adjusted, i.e. they 

are not given on the EIB/KNX but processed within the visualization. It goes without saying 

that the operating terminal (visualization) must have been started to use its functions 

(message windows display). 

-o--o--o-- 

Page 162




The surface of the reminder editor consists of an operating page (Module EE001) with an 

additional window (message window) that pops up automatically as soon as the defined date 

has been reached. 

(01) Reminder channels 

(02) Freely definable reminder text (can be edited by clicking on the text field) 

(03) Test button for manual release of a date and display 

(04) 10 channel year timer clock to fix a date 

(05) User-defined labelling 01 

(06) User-defined labelling 02 

(07) Display of the current system time and date 

(08) Module designations for internal project planning 

(designation is used in the database for quick identification) 



example "Tools") 

(10) Navigation link submenu lighting tools 


example "Reminder editor") 

(11) Navigation link back to tool submenu 


(13) The label editor has been activated, all texts that can be modified are marked yellow. 

Click to edit these texts. 

(14) ditto (13) 

(15) ditto (13) 

(16) Time programme of the 10-channel year timer clock 

(17) Display of the individual reminder channels 

(18) Time frame of a reminder 

(19) Definition of a reminder date 

(20) Year timer clock calendar 

(21) Comprehensive tools of the timer clock 

(22) Export function of the dates (*.csv-file) 

(23) Automatic message window with your personal reminder text 

(24) Automatic message window with time and date stamp for reminder 

(25) Automatic message window with acknowledgement button for active reminders 

Page 163


Page 164


The reminder editor (10) is used to define the personal texts (02) and the respective 

reminder dates (04). To enter text you must go into the label editor (12). Here, in addition 

to the reminder texts (14) the other module labels that can be edited are marked yellow 

(13). All yellow texts can be modified by a simple mouse click. 

Click within the text to open a work box (14)(15) with the current text. Now, the text can 

be modified as you like within the maximum given length. 

Page 165


Use the button (15) to confirm or quit the text. After having completed the text, use 

the "Back" button in the visualization page submenu to return to the reminder editor. 

Now, the changes you have just made are displayed. After having defined the reminder 

texts, it is now necessary to fix the reminder dates by means of the integrated 10-channel 

year timer clock (04). Do not forget that only "On" ("1") dates (18)(19) must be used to 

fix dates. Otherwise reminders might be reset without acknowledgement. Now, enter into the 

timer clock all reminder dates (17) in the calendar (20) together with the desired reminder 

time (19) by entering an "On" command. 

If the reminder date is reached and the operating terminal has been started (visualization), a 

message window pops up showing the current reminder (23) (your text) as well as the date 

and time stamp (24) of the reminder day. Use the button (25) to acknowledge the 

message and to set it internally to "Off" ("0"). Should there be more messages, these are 

Page 166


displayed one after the other (using the button) with their reminder text and the date 

and time stamp. 

If there is no other reminder, the following text appears: "No more reminder is active! 

Back through button." (23) By pressing the button (25) again you return 

automatically to your last active visualization page. The message window does not dispose of 

a navigation bar to view and acknowledge the reminder intentionally. If the server or the 

operating terminal were not on at the reminder time the reminder window will automatically 

appear as soon as server or operating terminal are started. 

-o--o--o-- 

Page 167




Within the project software a two-digit or three-digit EIB/KNX notation can be used for the 

group addresses. 

When delivered, the data points of the reminder editor are "virtually" preset, 

that means they are not given on the EIB/KNX but only processed within the visualization. 

Only when data points are activated as EIB port (connection) and a group address is given 

(address) the reminders are sent as EIB telegram on the EIB. 

Page 168




-o--o--o-- 

Page 169


4-Side blind automatics 


-o--o--o-- 

Page 170


Purpose 


The blind automatics in the ©IQHOME.NET visualization controls automatically (per side) the 

position of your blinds or shutters depending on brightness and timer clock programme (year 

timer clock). Comprehensive parameters permit individual adjustments to your building 

requirements without additional efforts and programming! 

The automatic blind control serves as fully automatic control of shading facilities with up to 4 

independent blind groups. Basically, these are assigned to the four directions but can also be 

used in other versions (such as 3 x blind, 1 x awning). This is permitted by the freely 

definable dependencies (sensor selection), nominal values (limit value, slat height and slat 

angle) as well as the integrated 4- channel timer clock. 

The devices of your EIB system (blind actuators, blind push-button switches) have already 

been provided with a certain „intelligence“ by the manufacturers which is completely 

sufficient for a normal „on site“ operation. You can very often realize efficient automatic 

processes with these devices. However, control options and parameterisation of this facility 

are limited. Setting new parameters is difficult (brightness values, slat height and slat angle 

etc.) and can sometimes only be carried out by means of ETS. This can only be done by a 

superior control that disposes of the required „intelligence“ on the one hand and a (e.g. 

visual) user interface on the other. 

The ©IQHOME.NET 4-side blind automatics consists of 4 operating pages for one blind side 

each. Each module is clearly identified within the project and the following description: 

Blind side 1 (East) 

Example: Module JA001 

The blind automatics control the blinds, if necessary parallel to a possibly existing decentral 

on-site control, to avoid overheating of rooms by intensive sunshine (especially when owner 

is absent) or to go automatically into comfort positions. 

Precondition for the use of the ©IQHOME.NET 4-side blind automatics is at least one EIB 

(2Byte) brightness sensor! Generally, this is backed by all weather stations. 

All other components such as parameter memory, limit value switch, timer clock are 

integrated in the software. Apart from 1Byte communication objects for slat height/slat angle 

or a 1Bit preset positioning object there are no other special requirements on the applied 

blind actuators. 

Page 171

Note: 


The ©IQHOME.NET 4-side blinds automatics is based on an existing and correctly functioning 

EIB blind facility. A single operation is not part of this blind automatics. Safety functions 

(wind, rain, freezing point etc) have to be provided as usual (EIB weather station actuator). 

-o--o--o-- 

Page 172


Features 


Control of up to 4 different blind groups with the following functions per side (direction): 

� 4- side blind automatics for brightness-controlled shading 

� Each side can be parameterized separately 

� Each side disposes of a separate operating mode selection 

� Time switch control release for each side (direction) 

� Sensor selection out of 6 available sensor inputs (brightness) 

� Display of the brightness value by the selected sensor 

� Switching point of the brightness value 

� Variable switch-on and off delay in limit value situation 

� Remaining time display of the delays 

� Adjustable blind position (segment height, segment angle) 

� Status display of the control outputs (segment height, segment angle) 

� User-defined labelling of the sides 

-o--o--o-- 

Page 173


Preconditions 


The control requires the application of at least one EIB/KNX brightness sensor. All other 

component such as parameter memory, limit value switch, timer clock are integrated in the 

software. There are no special requirements on the blind actuators used. Apart from the 

usually applied actuators with „Byte“- objects for position control you may also use 

actuators with „Preset“- control (Bit positioning) in the system. However, in the latter case 

you would not be able to use the comfortable position adjustments by means of 

©IQHOME.NET. These must then be defined in the actuator by means of the ETS as fixed 

values (modification of slat height and slat itself can then only be made with the ETS). 

As an option up to 4 other measured brightness values can be processed in ©IQHOME.NET 

for example to control each side with its own sensor. Each blind front has a selection box 

(Drp Down) with the available brightness values to calculate the control. However, the blind 

automatics is also able to control all sides of a building with only one brightness sensor. For 

this purpose separate limit values and blind timer clocks are provided to define an individual 

release of the different sides. 


blind actuator 230 V AC, 6 A 

with "local control", 8-fold and 1Byte 

position objects for segment height, segment angle 

Ref. No.: N164408 


Manufacturer: BUSCH/JAEGER 

Manufacturer Nr.: 6196/82 

To control 8 independent drives. Separate locking (UP position) e.g. possible using W ind 

Watchdog Without additional voltage supply The following applications are provided for the 

outputs: Outputs: Blind, Position, Security function, W ind alarm, Rain alarm, Frost alarm, 

Automatic sun protection, Automatic heating/cooling, Status, Position check-back signal, 

Scenes, Ventilation-flap operation, Run to pre-set and set, "local operation" Connections: 

Page 174


Outputs: screw terminals, 0.2 - 4.0 mm² multiple-wire: 0.2 -2.5 mm² EIB-line: Bus terminal 

Dimensions: (L x W x D): 90 mm x 72 mm x 64 mm Installation depth: 68 mm module 

width: 8 TE Design: per M-Design Technical data: Rated voltage: 230 V~, +10 % / -15 % 

Rated frequency: 50 Hz - 60 Hz Outputs: 8, Change-over switch Switching capacity: 

AC1/AC3 Rated current: 6 A Physical properties: Protection class (Device): IP 20 

Temperature range (Device): -5 °C - 45 °C 

Description 


Ref. No.: N300057 



























Benefits 



-o--o--o-- 

Page 175


Page 176




The surface of the blind control consists of four operating pages (Module JA001-JA004), with 

one page being assigned to each blind group (side). 

(01) Sensor selection brightness 

(02) Current value display with limit value regulator 

(03) Switch to activate/deactivate the automatic function 

(04) Manual operation of the clock channel 

(05) Adjustment of the switch-on delay (EVZ 0-1800s) when limit value is exceeded 

(brightness) with remaining time display in % when delay is active 

(06) Adjustment of the switch-off delay (AVZ 0-1800s) when limit value is fallen short of 

(brightness) with remaining time display in % when delay is active 

(07) Adjustment of the slat height for active shading depending on 

automatic programme 

(08) Slat angle adjustment for active shading depending on 

automatic programme 

(09) Information display with status display for limit value situation with remaining time 

display in seconds, sensor malfunction etc. 

(10) Status information about currently calculated output status of the automatics for slat 

height (symbol display at one window) 

(11) Status information about currently calculated output status of the automatics for slat 

angle 

(12) Status information about current positioning 

(sun = positioning is active, positioning commands have been sent to the actuators) 


(14) Module designation for internal projects 

(designation is used in the database for quick identification) 

(15) Internal control cycle 

(16) User-defined labelling of the blind side 

(17) Current side selection blind control 

(18) Current value display in klux of the active (01) brightness sensor 

(19) Calling up the Online-help (base menu) 

(20) Navigation link to start page (base menu) 


(22) Navigation link main menu blind 

(Button being pressed with active, flashing white LED below, if selected, 

our example "Blind") 

(23) Navigation link submenu blind 01 

(Button being pressed with active, flashing white LED below, if selected, 

our example "East") 

(24) Navigation link submenu blind 02 (Example West) 

(25) Navigation link submenu blind 03 (Example South) 

(26) Navigation link submenu blind 04 (Example North) 

(27) Calling the clock programme for the blind automatics 

(28) Navigation link to sensor system toolbar (sensor definition) 

Page 177


The brightness limit values for each side can be set individually by means of the red limit 

value regulator (02) of the module. To do so, simply push the limit value regulator to the 

desired value (given in klx). The yellow display bar represents the current brightness value 

in klx. Another individual adjustment of the limit value can be made by setting a switch-on 

or off delay between 0-900 sec. to avoid that the blinds open or close as soon as there are a 

few clouds. 

Individual input values (brightness sensors) can be used for each side. Selection is made 

using the Drop Down Menu (01). Thus, it is also possible to control all sides with only one 

brightness value. 

Furthermore, each side disposes of its own timer clock channel in the blind timer clock that 

can be called up using the clock symbol (27). 

The automatic function of each side is activated or deactivated by means of the button „ Auto 

“ (03). The desired blind or shutter positioning that means which slat height and which slat 

angle (blinds only) has to be realized with the active automatic function is set by means of 

the rotary regulators (07, 08). There is a rotary regulator for the slat height ([07] 0% = 

completely up, 100% = completely down) and one for the slat angle ([08] 0° = horizontal 

slat, 90° = vertical slat, i.e. closed). Switching off the automatic function using the button „ 

Auto“ (03) with the positioning being active does not immediately lead to an opening 

(quitting the positioning). Only after the brightness value has fallen below the limit value 

(brightness) including a possibly existing switch-off delay or after the clock has switched off, 

the current positioning is deactivated. Only when the limit value is exceeded the next time 

Page 178


with the automatics being inactive (button „Auto“ (03) is off ) this will not lead to a 

positioning. 

The following conditions must be fulfilled to permit a transmission of positioning commands 

to the blind actuators: 

1. The brightness limit must have been exceeded at the respective side. (02) 

(A possibly adjusted delay time must have been completed. EVZ [05]) 

2. The blind automatics for the respective side must have been switched on. (03) 

3. The clock for the respective side must be on (Time programme must be active). 

(27, 04) 

Note: 

Output of the positioning commands (group addresses) is not cyclical but occurs 

only when the limit value situation changes to avoid a constant closing and opening 

of the blinds through the positioning process. 

Using an existing local blind push button you can make adjustments at any time. The 

behaviour of the applied blind actuators in case of positioning/automatic commands (direct 

movement from any position into the position parameterised in the ©IQHOME.NET for 

height/slat or reference movement or movement always directly from top or bottom etc.) is 

set at the actuators by means of the ETS. 

Additional technical information: 

If your blind actuators do not dispose of EIB communication objects of the 1Byte type for 

slat height (runtime) and 1Byte type for the slat itself, nominal positioning values cannot be 

set by means of ©IQHOME.NET. In this case, the positions must be set directly by means of 

the actuator as fixed values i.e. slat height and slat itself can only be modified by means of 

the ETS. Such actuators usually have an EIB communication object of the 1Bit (PRESET) type 

to start/finish the positioning at the blind actuator. This 1Bit data point is also integrated in 

this blind terminal and is sent on the bus when positioning is being carried out (see EIB/KNX 

data). 

Hint: 

When adjusting the motor running times at the blind actuator you will have to observe the 

exact blind running times for one movement (is often parameterised in seconds per output at 

actuator) since slat adjustment is only made after motor running time is off (long-time 

movement, slat height) at the actuator. If, for example, the motor running time is set longer 

than the time required for the blind/shutter to move down, this leads to an unintentional 

darkening (The blinds usually go down with the slats being closed (90° vertical) and up with 

the slats being open) of the room before the slat can move into the set position. 

Sensor selection (1) 

Depending on your existing EIB/KNX project, up to a maximum of 4 direction-dependant 

brightness sensor (at the sides) or other sensors can be integrated. All sensors can serve as 

input value for the limit value switch. The respective selection is made with the sensor 

selection. The sensors defined in the “Sensor system toolbar” are presented for selection. 

The current measured value of the selected sensor is displayed together with the measuring 

Page 179


instrument (18). A sensor monitoring set in the sensor system toolbar is also active here 

since sensors with a malfunction are set to zero by the system (0 klux/lux measured value 

means „too dark“, meaning blind „up“). The malfunction of the selected sensor is indicated 

by a flashing red display (09). 

Limit value switch (2) 

The limit value switch consists of a combination device to display the current value (yellow 

bar) and the nominal value (red triangle) as well as the nominal value adjustment. The scale 

readings have been designed according to the expected value with up to 1000 lx. Each 

modification of the nominal or current value result in a new calculation of the output value 

which is given to the delay stage for further processing. The delay stages consist of a 

switch-on and a switch-off delay (ON/OFF), that can be adjusted variably by means of the 

rotary regulators (5, 6) between 0..1800 seconds. 

Operating mode (3) 

It is used to activate or deactivate the automatic function. It is available for further 

processing on the EIB or can be influenced via the EIB , see "EIB/KNX data". 

Manual operation timer clock (4) 

In normal operation, the timer clock is responsible for the release of its assigned blind group 

(e.g. blind south = 10 a.m. to 3 p.m.). If fast, temporary interventions are required, the 

switch (4) can be used to switch over the output of the clock (27). This can be reset by the 

user or is reset by the timer clock itself with the next programmed switching. As an option 

(project planning), this function is also available on the EIB for further processing or can be 

influenced via EIB, see "EIB/KNX data". Here, it is important that the EIB port for this data 

point is activated since this data point is an internal (virtual) data point when delivered. 

When activating the EIB output for this data point, a group address must be entered and a 

recipient must exist in the EIB system (push button or similar) to acknowledge the 

telegrams. If there is no recipient, this leads to the clock being permanently switched off. 

Switch-on delay (ON) (5), Switch-off delay (OFF) (6) 

The switch-on delay fixed the time that must pass before the exceeding of the defined 

brightness limit leads to a release (switch on) of the positioning mechanisms. The switch-off 

delay fixes the time that must pass before the shortfall of the defined brightness limit leads 

to a blocking (switch off) of the positioning mechanisms. W ith this switch-off delay 

brightness fluctuations (clouds) are compensated efficiently. 

(Recommended adjustment: EVZ: 300 s, AVZ: 1800 s) 

Slat height (7), slat angle (8) 

Using these parameters the desired height and the slat angle to be realized during the 

positioning of a blind side can be fixed. For an inactive positioning height and slat angle are 

given with the value "0". The current output of the parameterised positioning commands is 

represented by a symbol window for height (10) with the slat angle position next to it (11). 

When the positioning is active, regulator adjustments are put on the bus immediately after 

release. 

For „Preset“- controlled blind actuators a positioning command (1 Bit) positioning = "1" is 

sent while positioning is in progress. 

The parameters height and slat angle are not important for „Preset“- controlled blind 

Page 180


actuators. Both actuator types can be used in the facility at the same time. 

Labelling the blind side (16) 

The label of the blind side only serves for user orientation. The label can be modified on 

another page that is called up with button (21). 

-o--o--o-- 

Page 181




Within the project planning software, the two-digit or three-digit EIB/KNX notation for group 


Page 182


©IQHOME.NET disposes of 8 pcs. 1Byte EIB communication objects and 4 pcs. 1Bit EIB 

communication objects, per blind control module always 1 x for the height and 1 x for the 

slat angle as well as 1 x Preset positioning for blind actuators without 1Byte communication 

objects. You will find all other EIB/KNX communication objects under "EIB/KNX data". 



-o--o--o-- 

Page 183


EIB/KNX Blind JA001 


EIB/KNX data point list blind automatics side 1: 

Module JA001 (Example East): 





Input, release/blocking automatic operation: 

Module name: JA001 

Name communication object: Jalo A Automatik 


Output, positioning command height 0-100%: 


Name communication object: Jalo A Pos Behang 

EIB/KNX data point type: EIS14 Type 1Byte (EIB Zähler-8u) 



Name communication object: Jalo A Pos Lamelle 


Output, positioning command Preset: 


Page 184

Name communication object: Jalo A Fahrt 





-o--o--o-- 

Page 185





Module JA002 (Example South): 







Name communication object: Jalo B Automatik 




Name communication object: Jalo B Pos Behang 




Name communication object: Jalo B Pos Lamelle 




Page 186

Name communication object: Jalo B Fahrt 





-o--o--o-- 

Page 187





Module JA003 (Example West): 







Name communication object: Jalo C Automatik 




Name communication object: Jalo C Pos Behang 




Name communication object: Jalo C Pos Lamelle 




Page 188

Name communication object: Jalo C Fahrt 





-o--o--o-- 

Page 189





Module JA004 (Example North): 







Name communication object: Jalo D Automatik 




Name communication object: Jalo D Pos Behang 




Name communication object: Jalo D Pos Lamelle 




Page 190

Name communication object: Jalo D Fahrt 





-o--o--o-- 

Page 191


EIB/KNX Inputs 


EIB/KNX data point list sensor inputs: 

You will find the available EIB/KNX inputs (sensors) on the page "Sensor system toolbar" 

under "EIB/KNX data point list". To use the ©IQHOME.NET 4-side blind automatics there 

must be at least 1 EIB/KNX brightness sensor in your facility and it must be connected with 

©IQHOME.NET by means of group addresses (see project planning advice). 



-o--o--o-- 

Page 192


Climate Console 


-o--o--o-- 

Page 193


Purpose 


The climate console serves for central administration, control and display of EIB/KNX single 

room temperature controllers as well as a heat generator with water treatment and EIB/KNX 

interface (e.g. Viessmann or Buderus). Using the climate console in ©IQHOME.NET all 

parameters of the individual rooms can be viewed and operating mode switch-over (1Byte) 

can be controlled comfortably with individual programmes. For this purpose, two 

visualization pages have been integrated, one page for a group of six rooms. 

Modify the heating curve of your heat generator (level/shape) and have all other important 

information displayed (hot water preparation, boiler), provided there is an optional interface, 

or expand your facility with a solar system (Professional Version). The comprehensive 

long-term history management permits to evaluate all relevant data in form of tables or 

graphics and to export the data for further use. 

When you are absent for a longer period of time, just enter the number of days you are not 

at home and that’s it. Now, the system regulates standby and night operation automatically. 

Hint (for users of Professional project planning with Iocomp control elements only): 

Simply copy a whole page, modify the data points in the event processing and select the new 

data points at the elements to integrate any number of temperature controllers. W ithin a 

few minutes you can create additional modules. However, it is essential that there is a 

licence for the required additional data points (group addresses) to create further group 

addresses for additional controllers. 

If you are not familiar with Professional version or do not have enough time to plan the 

project for your facility, we will be pleased to prepare your personal visualization. Just ask 

for your personal offer of under www.eibmarkt.com before you come to a decision. 

-o--o--o-- 

Page 194


Features 


Administration and control of up to 12 room temperature controllers, heat generator and hot 

water generator with the following functions and features: 

� Status display (operating mode, desired and current temperature and control signal) of 

up to 12 room temperature regulators 

� Operating mode switch-over manual 

� Operating mode switch-over by means of individual time switch channels 

� Status display (operating mode, malfunction, desired and current temperature, heating 

curve, operating hours) of the heat generator (VIESSMAN interface, Buderus on demand) 

� Status display (switching conditions, malfunction, desired and current temperature) of 

the water supply system 

� Recording/history of operating mode, desired and current temperature and control signal 

of the room temperature regulators 

� Recording/history of desired and current temperature of heat generator and water supply 

system 

� Histories with different representation filters, variable time segments and print function 

� Set point adjustment at heat generator for holidays, level, curve behaviour (heating 

curve) and desired temperature of the water supply system 

� User-defined labelling of the room temperature regulators 

-o--o--o-- 

Page 195


Preconditions 


If, for example, you do not integrate an interface with your heat generator, no heat 

generator or hot water generator data will be evaluated. But you will be able to manage the 

comprehensive information given by the single room temperature controllers. All EIB/KNX 

room temperature controllers with operating mode control (1Byte) and switching or steady 

control signal can be integrated (see data point list EIB/KNX). Older room temperature 

controllers do not dispose of a communication object of the 1Byte type but a separate Bit 

switch-over for the operating mode. This can be adapted in the Professional version by 

selecting a Bit-operating mode change-over switch. ©IQHOME.NET is best suited for the 

connection of the EIB Viessmann interface (Vitocom) but can also be parameterised for any 

other interface without any problems. (Professional version). 


Room Controller EIB/KNX 

Ex. Room temperature controller with push buttons (EIB/KNX Room Controller, GIRA, JUNG) 

Manufacturer: available from almost all manufacturers. Selection differs depending on 

customers’ wishes (design/function/price) 

Vitocom 200 (EIB) 

Page 196


Ref. No.: N164334-1 


Manufacturer: VIESSMANN 

Manufacturer Nr.: 7450539 

Gateway for the direct connection to the EIB of heating systems with Vitotronic 300 (type 

KW3), wall models Vitodens, Vitopend and Vitoplus with closed-loop regulation/control for 

weather run mode (with Comfortrol) and post-connected Vitotronic 050 (type HK1M) or 

Dekamatik system. 

Functions: 

� Remote control of heating systems e.g. switch, change set points () 

� Remote monitoring of heating systems (e.g. desired/current temperature, heating curve, 

operating mode) 

� Passing of error or disturbing messages 

� Passing of data points of all bus users 

� Remote switch-over of the operating program over telephone (at regulation/control for 

wall models only with server Comfortrol) 

-o--o--o-- 

Page 197




(01) Terminal with display of room, operating mode switch, current (thermometer) 

and nominal value 

(arrow) temperature and control signal status (Bit or Byte) 

(02) Operating mode switch Comfort, Standby, Night, Frost (K, S, N, F) 

(03) Current and nominal value display room temperature 

(04) Display of the current valve status or controller result output as steady signal 

or switching signal 

(05) Timer clock programme call for automatically controlled operating mode switch-over 

of the room temperature controllers 

(06) Navigation link to the next page (rooms 07-12) of the climate console 

(07) Navigation link to history administration 

(08) Terminal: heat generator data 

(09) Terminal: influencing the heating curve 

(10) Additional parameter and status information of heat generator 

(11) Terminal: hot water generator 

(12) User-defined labelling of this active page of the climate Console by means 

of label editor (16) 

(13) Module designation for internal project planning (designation is used in the 

database for fast identification) 


(button being pressed with active, flashing white LED below, if selected, 

our example "Climate") 

(15) Navigation link submenu climate 

(button being pressed with active, flashing white LED below, if selected, 

our example "Heating") 


(17) Current climate console page selection 

Page 198

Room terminal (01) 


In the room terminal with its display of room name (01), operating mode switch (02), 

current (thermometer) and nominal value (red arrow) (03), temperature and control signal 

status (Bit or Byte) (04) all important data is indicated. With a mouse click the operating 

mode switch (02) can be set vertically to the different operating modes comfort operation, 

standby operation, night operation and frost protection. Using the integrated timer clock (05) 

these functions can also be controlled automatically. Thus, difficult and time-consuming 

parameterisations at the timer clock displays of room controllers are a thing of the past. In 

the timer clock programme (05) complete year or vacation programmes can be entered and 

standard programmes can be defined. 

Page 199


The small red arrow (03) shows the current desired temperature you have set by means of 

ETS depending on the operating mode selected. The arrow varies in its horizontal scale 

reading and points to the current desired temperature in the thermometer display next to it. 

The thermometer itself shows the current temperature (03) of the room temperature 

controller. The LED displays (04) shows the current status of the heating valve or the 

nominal value output of the controller to the valve. Here, you can chose whether the 

switching output at the controller (1Bit) or the steady output (1Byte) is used, see also 

EIB/KNX data point list of ©IQHOME.NET. If you use the switching output, the LED band only 

shows 0% or 100%. All this data (operating mode, valve status, nominal and current 

temperature) can be evaluated as table or graphics in the integrated history administration 

(07) and it can be exported. 

The controllers 07-12 are on the next page that can be called up by means of the navigation 

arrow (06) in the submenu. 

Heat generator and hot water generator (08)(09)(10)(11) 

With its Viessmann interface, ©IQHOME.NET is designed for the integration of different 

information. 

Page 200


(Example Viessmann interface with function module REG) 

Part of this are for example: 

In the heat generator data terminal the nominal temperature and the current temperature, 

the outside temperature, current malfunctions and pump data (08) are displayed. The 

nominal temperature input for the hot water generator can be modified by a simple mouse 

click in the text field.: 

Page 201


In the terminal for heating curve manipulation, level and heating curve shape (09) can be 

changed. Click on the text field to open a box for current value modification. After having 

entered the new value, this value is transmitted on the EIB/KNX via the interface to the heat 

generator. 

Heating curve acc. to DIN 

The heating curve describes the connection between outside temperature (TA) and heating 

feed temperature (TV). 

Heating curve shape (EF) (09) 

The heating curve shape defines the proportional connection between outside temperature 

(TA) and feed temperature (TV). This parameter is mostly used in cold seasons. An input of, 

for example, 1.3 means that in case of a outside temperature change of 1K the feed 

temperature is adapted by 3K. 

Heating curve level (KH) (09) 

Using the parameter „Level“ the curve can be displaced in parallel (Offset). This parameter is 

mostly used during in the inter-seasonal period. 

In the display for additional parameters and status information of the heat generator (10) 

current malfunctions are shown (operating condition) and the current operating time of the 

heat generator (operating hours* factor) can also be displayed. In the vacation day text field 

you may enter the number of days you are absent (vacation etc.) and the heat generator has 

to work with a minimum performance or with protection functions (frost protection). Click on 

the text field to open a box for current value modification. After having entered the new 

value, this value is transmitted on the EIB/KNX via the interface to the heat generator. 

In the terminal for the hot water generation (11) nominal and current temperature of the 

hot water generator (boiler) are displayed together with current status information about 

pumps (circulation pump, charge pump,) and malfunctions. 

Page 202


Each terminal page can be labelled individually (12). To do so, you have to call up the 

integrated label editor (16). In the label editor, all texts that can be edited are marked 

yellow. After having finished the labels, use the arrow key to return to the climate console. 

-o--o--o-- 

Page 203




Within the project planning software the two-digit or the three-digit EIB/KNX notation for 

group addresses can be used. 

EIB/KNX data point list climate console: 

Module KL001-KL002: 

Room controller: 


Page 204





06 pcs. Inputs Current temperature: 

Module name: KL001 

Name communication object: RTR01_Isttemperatur - RTR06_Isttemperatur 

EIB/KNX data point type: EIS 5 (1 Byte, Float) 

06 pcs. inputs, nominal temperature: 


Name communication object: RTR01_Solltemperatur - RTR06_Solltemperatur 


06 pcs. inputs, valve (signal steady): 


Name communication object: RTR01_Ventil - RTR06_Ventil 


06 pcs. inputs, valve (signal switching): 


Page 205


Name communication object: RTR01_Ventil_S - RTR06_Ventil_S 

EIB/KNX data point type: EIS 1 (Bit) 

06 pcs. inputs, current temperature: 


Name communication object: RTR07_Isttemperatur - RTR12_Isttemperatur 


06 pcs. inputs, Nominal temperature: 


Name communication object: RTR07_Solltemperatur - RTR12_Solltemperatur 


06 pcs. inputs, valve (signal steady): 


Name communication object: RTR07_Ventil - RTR12_Ventil 


06 pcs. inputs, valve (signal switching): 

Page 206



Name communication object: RTR07_Ventil_S - RTR12_Ventil_S 


Heat generator & hot water generator: 

10 pcs. inputs: 


Name communication object: HZG_WE_SM 



Name communication object: HZG_WE_Tist 



Name communication object: HZG_WE_Tsoll 



Name communication object: HZG_WE_UP 



Name communication object: HZG_WWB_Tist 



Name communication object: HZG_WWB_LP 



Name communication object: HZG_WWB_ZIP 



Page 207

Name communication object: HZG_WWB_E 




Name communication object: HZG_WWB_SM 



Name communication object: HZG_WWB_BS 

EIB/KNX data point type: EIS 10.000 (1Byte) 

04 pcs. outputs: 


Name communication object: HZG_WE_Neigung 



Name communication object: HZG_WE_Niveau 



Name communication object: HZG_WWB_Tsoll 



Name communication object: HZG_WWB_FE 

EIB/KNX data point type: EIS 10.000 (1Byte) 



-o--o--o-- 

Page 208


Media Console 

Media Console 


-o--o--o-- 

Page 209


Scenario-Manager 


-o--o--o-- 

Page 210


Purpose 


The scenario manager serves to store and call up to 8 scenes in which switching, dimming 

and blind conditions can be managed. Up to 8 switching channels (for example for lighting 

Off/No/On or blind Up/No/Down or Preset) or up to 6 dimming channels (set 1 Byte value, 

also suitable for long-time blind positioning (slat height)). The definition of the desired 

brightness value or switching condition in the individual scenes can be modified by means of 

the integrated rotary regulator and selector switch and can then be stored anew in a scene. 

To prevent unintentional overwriting of scenes, safety questions will be asked. Modified 

values are kept even with a new initialisation of the process server. The individual scenes are 

called using the integrated scene call keys or by means of telegrams sent, for example, by 

any push button switch (send value). 

The available communication objects for the outputs (binary outputs, dimmer) are provided 

in the module operating terminal (LI001). 

-o--o--o-- 

Page 211


Features 


The scenario manager serves to store and call up to 8 scenes with the following functions 

and features: 

� 8 scenes 6 dimming groups (Byte) and 8 switching groups (1Bit) 

� Function selection switching groups: Off/No/On 

� Function selection dimming groups: rotary-type regulator 0-100% 

� Special function „No“ also ideal for blind preset functions, thus no change in case of 

scene modification 

� 8-fold status-sensitive scene memory with security request 

� 8-fold scene activation internal and external by means of push button or motion detector 

(send value) possible 

� Automatic adoption of the scene names on the buttons „scene memory“ and „scene 

activation“ 

� Display of the currently selected scenario 

� All functions in IQHOME.NET are persistent (adjustments are kept even when the server 

is shut down) 

� Individual labelling of the switching and dimming groups as well as scene names by 

means of the label editor 

-o--o--o-- 

Page 212


Preconditions 


To use this module at least two outputs (switching actuators, dimming actuators, blind 

actuators) must be connected via the available communication objects to form a scenario. 


8-fold switch actuator EIB/KNX SA.8.16, 

MDRC, (6x16A man., 2x8A) 

Ref. No.: N000200 



Very high quality and unique price-/ performance relationship! 

The binary actuator SA.8.16 receives data frames via EIB and, with its potential-free, 

independent relay contacts, switches up to 10 groups of electric devices. Different outer 

conductors can be connected to the outputs A1-A6. The channels A1-A6 contain polarized 

latching relays (for capacitive load up to max. 140 µF and lamp load up to max. 2500 

W, further details see data sheet relay).One outer conductor each can be connected to 

the outputs A7 and A8. The channels A7 and A8 dispose of a change-over contact each 

(Opener/Closer). 

Comprehensive functions permit several possibilities for parmeterization, such as: 

� Switching behaviour of the relays (Open/Close) 

� Operating mode of the relays (switching, switching with feedback) 

� Definition of switching condition in case of bus failure and recovery 

(unchanged/open/closed) 

Page 213


� Characteristics of the feedback objects (Status, Send, Inverting) 

� Logical connections (AND, OR) 

� Inverting the connected object (Yes/No) 

� Definition of the input objects for bus voltage recovery (logical "0", "1" or read "via EIB") 

� Time function On and/or switch-off delay 

� Time function staircase lighting (retriggerable) with optional switch-off warning 

and service function (Cleaning light) 

� Time function staircase lighting with abort option by means of "0" frames 

(for currently active time function) 

� etc. 

Using the slide switches 6 relays (output 1-6) can be switched on or off directly by hand 

parallel to EIB, KNX TP1 or even without EIB, KNX TP1. In addition to that, these slide 

switches serve to show the current switch position. The 8-fold binary actuator SA.8.16 is a 

device to be fixed on a 35mm DIN-bar and to be installed in electric distributors. In 

combination with the product database and the ETS-Software the actuator serves to switch 

up to 10 independent groups of electric devices with different functions each. Several 

different software settings permit application of logical connections, switch-on and off delays 

and staircase lighting functions with adjustable switch-off warning. Besides the option to 

switch the connected devices in a defined way in case of a bus malfunction, it is possible to 

update the current object values in case of a bus recovery. Power supply of the device is 

provided exclusively via the EIB, no other power supply is required. Connection to the 

bus (EIB, KNX TP1) is ensured by means of the supplied bus terminal. Connection of the 

devices is ensured by means of integrated screw terminals. The outputs A1 to A6 are capable 

of switching loads with a current of up to 16 A by means of potential-free contacts. Using the 

switch position displays of the outputs A1 to A6 it is also possible to switch the connected 

load circuits manually - even in case of bus failure. The outputs A7 and A8 switch loads with 

a current of max. 8 A. Doing so, two groups of devices each can be switched potential-free 

with one opener and one closer. (change-over contact). 

EIB basic set 64 channel, incl. logic module 

and power supply 

Ref. No.: e160 



The basic set has been designed for basic equipment with the most important 

components at a reasonable price! 

The basic kit can be programmed very normally with the ETS2 and ETS3 PRO. 

EIB basic set 1 plus consists of: 

Page 214


1 pc. Power supply unit with throttle, 

1 pc. Power supply unit to supply the interface modules, 

2 pcs. Universal input and output concentrator 32-fold EIB (EIB-Interface), 

"n" pcs. Binary outputs 8-fold 230V,manual operation, RM, 16A/10A, 

"n" pcs. Binary inputs 8-fold 24V-AC/DC, 

"n" pcs. Binary inputs 8-fold 230V-AC, 

2 pcs. Connecting lines VL-1 (to connect the interface modules with the concentrator) 

1 pcs. Logic module (For complex control functions.) 

8 pcs. Connecting comb 8-fold 

Info: 

With this set you dispose of hardware to install a complete EIB line as well as the above 

delivery volume. The package includes 64 pcs. channels to operate devices (lamps, sockets, 

heating valves etc.), or 64 pcs. channels as bus inputs (window contacts, malfunction 

indicators, push-buttons etc.), or a mixed configuration of binary inputs and binary outputs 

because from now on you can determine yourself the type and quantity of binary inputs 

8-fold or binary outputs 8-fold you require without any extra costs. 

Universal Dimming actuator 

2-fold, MDRC 

Ref. No.: N167607 



Manufacturer Nr.: 3602REG 

The universal dimming actuator receives telegrams for switching or dimming purposes. It 

can work with the principle of trailing or leading edge control. That means either low voltage 

halogen lamps with TRONIC transformer or conventional (inductive) transformer can be 

controlled. The max. capacity can be extended by using power amplifiers (see main 

catalogue).Depending on the parameter it is possible to activate various additional functions. 

-o--o--o-- 

Page 215




(01) Nominal value regulator 0-100 % (set value) for max. 6 channels dimming function 

(02) Selector switch for the scenario switching groups 07-10 with the possible functions 

"Off", "No" and "On" 

(03) Selector switch for the scenario switching groups 11-14 with the possible functions 

"Off", "No" and "On" 

(04) Key block "Scene memory" to store the scenes 

(05) Key block "Scene call" to call up the stored scenes 

(06) Information display to show the current scene 

(07) User-defined dimming group labelling by means of the label editor 

(08) User-defined module labelling by means of the label editor 




(11) Display of the current page in the media console 


(Button being pressed with active, flashing white LED below, if selected, our example " 

Media Console") 

(13) Navigation link submenu media console 


Scenario Manager" 


Page 216


Using the scenario manager you can handle your desired scenes conveniently. You can 

execute the scene call (05) directly from the scenario manager or externally by using the 

push-button switch (send value) installed in the room. The scenes can be called externally 

(Universal or Multi-function key) by means of the following values (EIS 14, 1Byte): 

Scene/value: 

Call scene 01: Send value "0" 








The operating terminal does not need to be on for "Lichtszene aufrufen extern". Only the 

process server must be active on the bus. 

The module is graphically divided into several areas. First, all available channels and the 

scene names should be labelled individually using the label editor (14) to get a good 

overview. After having completed all labels and entered all group addresses at the available 

communication objects, you can adjust the scenes. 

Page 217


In the centre there are the 6 rotary regulators (01) for the dimmable lighting groups that 

communicate via a 1Byte object with your dimming actuators (set value). Here, the nominal 

value can be set individually from 0 to 100 % for each scene. This corresponds to 0-255 

possible dimming levels. The rotary regulators do not send their value to the bus until the 

set regulator has been released. 

(Info: Each of these channels (set value 1Byte) disposes of its own clock programme in the 

operating terminal.) In every scene, three conditions can be assigned to the switching 

groups in the scenario manager (group 07-14) (02)(03) "Off", "No", "On". For 

motor-controlled applications this would be "Up", "No", "Down" (value 1Bit: "0", "-", "1"). 

Thanks to the condition "No" it is possible not to make any transmission on the bus for the 

selected group in the current scene. This is also the ideal application for motor-controlled 

processes (blind) to avoid a constant up and down movement or new positioning for devices 

such as blinds as soon as the scene is changed (keeps the current blind position for the next 

scene). 

After having made all adjustments as desired, the scene can be stored (04). To do so, 

simply press the desired scene memory and the following safety question pops up: 

This question (15) can only be confirmed or cancelled. 

Hint: 

Do not leave this active question window (15) in the operating terminal open without 

confirmation since this might lead to a blocking of other calculation processes. 

After having assigned the scenes, they can also be started directly in the scenario manager 

Page 218


using the key block "Call scene" (05) or by means of the communication object for external 

scene call. A big information display (06) informs you about the currently selected scenario. 

-o--o--o-- 

Page 219




Within the project software the two-digit or three-digit EIB/KNX notation for group addresses 

can be used. 

EIB/KNX data point list scenario manager: 

Module MS001: 

Inputs: 

Page 220






External scene call: 

Module name: MS001 

Name communication object: Lichtszene aufrufen extern 

EIB/KNX data point type: EIS 14 (1 Byte) 

Outputs: 

06 pcs. outputs, set value (dimmer): 


Name communication object: Leuchte D01W - Leuchte D06W 


08 pcs. outputs, switching: 


Name communication object: Leuchte S09, S10, S19, S20, S29, S30, S39, S40 

EIB/KNX data point type: EIS 1 (1 Bit) 

Page 221




-o--o--o-- 

Page 222


Audio Console 

Audio Console 

-o--o--o-- 

Page 223


Purpose 

Audio Console 

The audio console was integrated to control audio systems (e.g. WHD) by means of an 

operating console for multi room stereo sound via two separate stereo channels (4 outputs) 

for any desired room assignment. Several concealed power amplifiers can be connected to 

the 2 stereo channels of the audio actuator to permit loudspeaker installation (depending on 

the planned room number). You can, for example, assign one channel to the rooms: kitchen, 

utility room, child, bathroom, terrace etc.. and the other output to the bedroom in order to 

use also additional functions (wake-up). By means of a push-button switch near the bed the 

system can, for example, be set in parallel (On/Off, Volume etc.). If several, separately 

controlled rooms are to be handled, the number of audio actuators must be increased 

accordingly. 

In ©IQHOME.NET it is possible to connect the different available communication objects with 

external EIB/KNX audio systems to make specific adjustments comfortable. From booster 

activation via source selection (sound source) up to the volume adjustments for individual 

areas, many parameters can be modified. Automatic controls by means of clock programmes 

for booster On/Off, source selection and volume adjustment offer additional comfort. 

-o--o--o-- 

Page 224


Features 

Audio Console 

The audio console serves as comfortable and automatic control of an audio system with 2 

stereo outputs and has the following functions and features: 

� Activation of EIB audio systems (e.g. WHD, see www.eibmarkt.com) 

� Operating console for one Multi Room Stereo acoustic irradiation (audio actuator) 

� 2 separate stereo channels (4 outputs) for any room assignment 

� Both boosters can be activated separately and each is equipped with a separate clock 

program 

� 4-fold source selection (e.g. TV, TU, CD, PC) each controlled separately and equipped 

with clock program 

� Volume regulator 0-100% for each booster with separate clock program 

� Clock programs permit automatic wake-up functions (cyclical volume increase) and 

atmosphere 

� Highness, lowness, balance, area call, mute functions etc. can be parameterized for each 

stereo output 

� Output of any *wav files with the most different activities (wake-up, fire alarm, burglar 

alarm, presence simulation) 

� Audio signal output from PC to any audio system possible (e.g. WHD), sound board 

required 

� In the „Tel“ version even computer animated audio output (sound board - source PC) in 

case of data point modification possible 

� Individual labelling of the room names 

-o--o--o-- 

Page 225


Preconditions 

Audio Console 

To use this module an EIB audio actuator must be connected via the available 

communication objects. 


EIB Audio-Actuator AM 840 

Ref. No.: N460003 


Manufacturer: WHD 

Manufacturer Nr.: AM 840 

By using the Audio Actuator AM 840, you can create a complete multi-room audio system 

controlled by EIB. Audio sources, volume and tone can be controlled individually in every 

room. The AM 840 is able to take up to 8 mono or 4 stereo sources, which can be 

independently directed to outputs of 4 mono or 2 stereo zones. It can also be cascaded to 

give additional zones. The AM 840 is a DIN rail mounted device with a metal case that 

provides good electrical and mechanical shielding. 

Technical data 

� Audio-inputs: 8 Mono or 4 Stereo 

� Input voltage: 5 V AC 

� Input impedance: 100 kOhm 

� Audio-outputs: 4 Mono or 2 Stereo 

� Output voltage: 5 V AC 

� Output impedance: 47 Ohm 

� Control outputs: 4x 0-10 VDC 

� Switched outputs: 4x 24 VDC, max. 10 A 

� Terminals: Screw type + D-Sub 

� Tone control: Bass, Highs: +/- 14 dB; Mids: - 4 dB / 3,5 kHz 

� Power supply: 24 VDC, 180 mA + 0,8 A per Amp 10 DC 

Page 226


� Dimensions: 208 x 89 x 60 mm (DIN rail case) 

� Weight: 0,7 kg 

� Operating features: Amplifier on/off, volume, source selection, mandatory-/ zone 

broadcast 

� Tone control: Bass, Mids, Highs 

� Frequency range:Mikrophone: 30-16 000 Hz (-1,5 dB) 

� Line: 30-20 000 Hz (-1,5 dB) 

� Distortion: < 0.1% 

-o--o--o-- 

Page 227



Audio Console 

(01) Button to activate (On/Off) the booster 01 

(02) Sound source selection (source 01-04) VS 01 

(03) Nominal value input treble booster 01 (each alternatively 0-100% or bit by bit) 

(04) Nominal value input bass booster 01 (each alternatively 0-100% or bit by bit) 

(05) Nominal value input balance booster 01 (each alternatively -100 100% or bit by 

bit) 

(06) Nominal value input volume booster 01 (0-100%) 

(07) Nominal value input for midrange filter (MI), mute (MU) and zone call (ZC) of the 

booster 01 

(08) User-defined labelling of the stereo output booster 01 by means of label editor 

(09) Button to activate (On/Off) booster 02 

(10) Sound source selection (source 01-04) booster 02 

(11) Nominal value input treble booster 02 (each alternatively 0-100% or bit by bit) 

(12) Nominal value input bass booster 02 (each alternatively 0-100% or bit by bit) 

(13) Nominal value input balance booster 02 (each alternatively -100 100% or bit by 

bit) 

(14) Nominal value input volume booster 02 (0-100%) 

(15) Nominal value input for midrange filter (MI), mute (MU) and zone call (ZC) of the 

booster 02 

(16) User-defined labelling of the stereo output booster 02 by means of label editor 

(17) User-defined labelling 01 of the module by means of label editor 

(18) User-defined labelling 02 of the module by means of label editor 

(19) Display of current system time & date 



(21) Obligatory call of all channels On/Off 


(Button being presses with active, flashing white LED below, if selected, our example " 

Media Console") 

(23) Navigation link submenu media console 


Audio Console" 

(24) Navigation link to submenu scenario manager of the media console 


(26) Clock programme for automatic booster activation (On/Off) of both stereo outputs (one 

separate clock channel each) 

(27) Clock programme for automatic volume regulation (Volume) of both stereo outputs 

(one separate clock channel each) 

(28) Clock programme for automatic source selection (1-4) of both stereo outputs (one 

separate clock channel each) 

Page 228


Activate the respective stereo output by means of the button marked with the symbol „Mains 

switch“ (01)(09). This function can also be controlled automatically by the respective clock 

programme (26). Use the source selector switch (02)(10) to choose the connected sound 

source. This function can also be controlled automatically by the respective clock programme 

(26). 

The rotary regulator and Plus/Minus (03)(04)(05)(11)(12)(13) keys serve to adjust 

treble, bass and balance. Depending on the type of audio system connected, the rotary 

regulator or the plus/minus key can be used alternatively. Using the rotary regulators the 

nominal values are given as absolute (1 Byte). Using the plus/minus keys the data is given 

"bit by bit". Press the key once to increase (+) or decrease (-) the nominal value by one 

step. Sending a "0" (+) key increases the nominal value, with a "1" (-) key it decreases until 

a limit is reached. This is applicable for the treble and bass nominal values. For balance 

nominal value adjustment the value is given as Byte value (EIS 14.001) (-100% 100% 

= output value -128 127, converted into -127 127). Internally, the conversions 

are already included at the regulator. However, it is also possible to adjust the balance “bit 

by bit” using the respective available EIB communication object as follows: Sending a "0" 

(+) key the volume of the right output increases by the value "1", the volume of the left 

output decreases by the value "1". Sending a "1" (-) key inverts the process. 

Use the keys (07)(15) to call the additional functions (On/Off) for the midrange filter (MI), 

mute (MU) and zone call (ZR) at the respective stereo output. An LED (blue) shows the 

current output status. 

Page 229


The volume regulator (volume) (06)(14) can be used to set the volume of the respective 

booster to a fixed value. Sending the value "0" (0-100%) the booster is switched off, for any 

other value the volume is immediately set to this value. In addition to that the balance is 

reset. Respective feedback addresses should always be entered at these available 

©IQHOME.NET communication objects to update external modifications. The volume 

regulators can also be controlled automatically with the given clock programme (27). 

Use this key (21) to switch the obligatory call on or off. W hen the obligatory call is active, 

the text "PR" in the key flashes red. The obligatory call serves to make announcements that 

can be heard in the entire building. After activation, the gong of the obligatory call is played 

first and then each booster is switched over to the obligatory call channel and obligatory call 

volume. As long as the obligatory call is active the boosters do not respond to other 

commands. 

The module labels (17)(18) can be made as desired using the label editor (25). 

The Professional version offers many more options to integrate additional functions such as: 

� Output of any *.wav, *.mp3 files for the most different activities (wake-up, fire 

alarm, burglar alarm, presence simulation) 

� The additional module "Tel" permits a computer-controlled voice output (sound board 

- source PC) for data point modifications 

-o--o--o-- 

Page 230



Audio Console 


can be used. 

EIB/KNX data point list audio console: 

Module MS002: 

Outputs: 

Page 231






02 pcs. mute control (Mute): 


Name communication object: AUDIO_S01 Mute - AUDIO_S02 Mute 


02 pcs. source selection: 


Name communication object: AUDIO_S01 Quelle 1-4 - AUDIO_S02 Quelle 1-4 

EIB/KNX data point type: EIS 14 (1Byte) 

02 pcs. balance: 


Name communication object: AUDIO_S01 Quelle Balance - AUDIO_S02 Quelle Balance 

EIB/KNX data point type: EIS 14 (1Byte, signed, regulator -100 % 100 %, output -128 

127) 

02 pcs. balance step: 

Page 232



Name communication object: AUDIO_S01 Quelle Balance Step - AUDIO_S02 Quelle 

Balance Step 


02 pcs. bass: 


Name communication object: AUDIO_S01 Quelle Bass - AUDIO_S02 Quelle Bass 


02 pcs. bass step: 


Name communication object: AUDIO_S01 Quelle Bass Step - AUDIO_S02 Quelle Bass 

Step 


02 pcs. treble: 


Name communication object: AUDIO_S01 Quelle Höhen - AUDIO_S02 Quelle Höhen 


02 pcs. treble: 


Name communication object: AUDIO_S01 Quelle Höhen Step - AUDIO_S02 Quelle 

Höhen Step 


02 pcs. midrange: 


Name communication object: AUDIO_S01 Quelle Mitten E/A - AUDIO_S02 Quelle 

Mitten E/A 


02 pcs. source step (option, not included in visu surface [Terminal]): 


Name communication object: AUDIO_S01 Quelle Step - AUDIO_S02 Quelle Step 


02 pcs. zone call: 


Name communication object: AUDIO_S01 Quelle Zonenruf - AUDIO_S02 Quelle 

Zonenruf 


02 pcs. booster On/Off: 


Name communication object: AUDIO_S01 Verstärker EA - AUDIO_S02 Verstärker EA 


02 pcs. volume: 


Page 233


Name communication object: AUDIO_S01 Volume - AUDIO_S02 Volume 




-o--o--o-- 

Page 234


Sensor System Toolbar 


Page 235


-o--o--o-- 

Page 236


Purpose 


The sensor system toolbar serves to prepare and scale the sensor data that are processed for 

all other function in ©IQHOME.NET (outside lighting, 4-side blind automatics, climate 

console etc.) as well as to monitor sensor information. 

Because some of the function modules provided in ©IQHOME.NET need this information for 

calculations, the connected sensors must be prepared accordingly. 

Example: You have integrated a wind sensor in your EIB/KNX system and this wind sensor 

disposes of a type 2 Byte communication object but sends the data only in km/h. Since 

©IQHOME.NET works with m/s, the sensor must be prepared first. This is done by means of 

an offset & factor. To convert the value from km/h into m/s, offset must be set to "1" and 

the factor to "0,36", and that’s it. 

This module also permits a multitude of other possibilities such as the parallel translation 

(adding / subtracting fixed values to / from the sensor input value) or the mistake correction 

of sensor inputs by multiplying with any given factor etc.. A cycle monitoring for each 

sensor, that can be switched on separately, can also be activated. 

All available sensor inputs are defined in the module weather station sensor system and are 

provided in the sensor system toolbar provided that EIB/KNX sensors are connected via the 

communication objects. 

Depending on the desired function combinations, up to 10 sensors can be connected. To use 

the 4-side blind automatics at least one brightness sensor is required which can be defined 

and selected as current value for all four sides. If you prefer separate brightness sensors for 

each side, you can also connect them. For the outside lighting matrix, for example, at least 

one twilight sensor switching (1Bit) or as 2Byte sensor value (resolution 0-255 o. 1000lux) is 

required for control unless you refuse the integration of sensor-controlled functions. 

That means, the minimum requirements to make full use of the available ©IQHOME.NET 

functions are one brightness and one twilight sensor. 

-o--o--o-- 

Page 237


Features 


Sensor administration of up to 10 sensor inputs with the following functions & features: 

� Scalable measured value processing for one brightness sensor in general 

� Scalable measured value processing for one twilight sensor 

� Scalable measured value processing for one wind sensor in m/s, km/h and wind speed in 

standard steps and text 

� Status display of a rain sensor 

� Scalable measured value processing for 4 brightness sensors assigned to the building 

sides 

� Weather data recording 

� Display in tables or charts with different representation filters, variable time periods, 

print function 

� Definable sensor monitoring (cyclical time monitoring) 

� Connectable frame indicator 

� Display of all sensor system measured values 

� User-defined labelling of the sensors 

-o--o--o-- 

Page 238


Preconditions 


To use this module, at least one sensor must be connected via the available communication 

objects. To use the functions provided in ©IQHOME.NET we recommend at least one 

brightness sensor and one twilight sensor or a brightness sensor with a very high resolution. 

If you want to make use of all functions and tools we recommend the additional connection, 

of a wind, rain and temperature sensor. However, this is not absolutely necessary for the 

functions in ©IQHOME.NET. The outside temperature, for example, can be connected directly 

via the available communication object if a Viessmann interface is integrated. Now, the 

existing outside temperature sensor of the heating is provided as communication object of 

the interface. 


Description 


Ref. No.: N300057 
















Page 239













Benefits 



-o--o--o-- 

Page 240




(01) Display of the 10 possible sensor inputs, consecutive numbers 

(02) Display of the unscaled measured value of the sensor (current value input) 

(03) Input of the factor for measured value scaling (Standard = 1) for possible 

conversions/mistake corrections 

(04) Free designation text for each sensor by means of the label editor 

(05) Input of an offset value for measured value scaling (Standard = 0, addition-subtraction 

to/from current value) 

(06) Current toolbar sensor output value for all other calculations 

(07) Slide regulator for manual value transmissions (current value input), represents also 

the current value 

(08) Activating the cycle monitoring for the sensor input by entering a monitoring time in 

seconds 

(09) Status display (malfunction) when cycle monitoring is active 

(10) Navigation link to the next module with the sensors 07-10 

(11) Navigation link back to the weather station sensor system 

(12) User-defined module labelling 







Tools") 

(17) Navigation link submenu tools 


Weather station sensor system " 

(18) Navigation link submenu tools/weather station sensor system 

(Button being pressed with active, flashing white LED below, if selected, our example 

"Sensor system toolbar" 


Page 241


The sensor system toolbar mainly serves to prepare the measured values of the sensor 

system for further internal calculations in ©IQHOME.NET since, meanwhile, there are many 

different EIB/KNX weather stations with different measured value resolutions. For the 

brightness sensors, for example, ©IQHOME.NET calculates with values/resolutions of 

0-100000 lux and displays in klux. The provided communication objects for the brightness 

sensors are of type 2Byte (EIS 5 Float). If the weather station you use can work with an 

output in lux, no adaptations have to be made. But if the weather station sends only in klux, 

this value must be multiplied by 1000, i.e. the value must be entered. 

as "Factor" (03). 

The input "Sensor Wind" serves only as a display in ©IQHOME.NET. The provided 

communication object is also of type 2Byte (EIS 5 Float) and has a value range/resolution of 

0-40 m/s. If your weather station can work with the output in m/s, no adaptations have to 

be made. If it works with km/h, the value must be entered as "Factor" (03). 

That means, the weather station you use (analogue value) regards every incoming current 

value as rough value which can be scaled as desired by entering a "Factor" (03) and "Offset" 

(05). Thus, comprehensive conversions, mistake corrections and other adaptations of the 

sensor inputs are possible. The value "Offset" (05) serves to add /subtract fixed values 

to/from incoming rough values. The respective rough value (sensor input) is shown under 

"Measured value" (02) (unscaled). The scaled value (after factor/offset) is shown under 

"curr. value" (06). 

Using the cycle monitoring function (08) in the toolbar each sensor can be time-monitored 

Page 242


separately. It is monitored whether, within a set period such as 600 seconds, a telegram is 

received from the weather station. If there is no telegram within this period, a sensor 

malfunction (09) is indicated by all displays as well as in the alarm list and the alarm output 

"Sensor SSM" is set to logic "1". This function is active when at least one cycle monitoring 

is on. This object is also backed by the SMS Port (MG 00). 

Each sensor can get any label by means of the label editor (19) which is then provided for 

all other displays and drop down menus within ©IQHOME.NET. Using the slide switch (07) 

you can simulate manual sensor values of a weather station. Incoming telegrams can also be 

viewed by means of the telegram indicator in the module weather station sensor system. At 

the same time, this regulator represents the current sensor input value provided a sensor 

input has been connected (slide switch shifts with every incoming telegram). 

-o--o--o-- 

Page 243




Sensor inputs, see data point list EIB/KNX 

or weather station sensors! 


can be used. 

Page 244


EIB/KNX data point list sensor system toolbar: 

Module SD001: 

Output: 





Alarm output sensor system collective malfunction message: 

Module name: SD001 

Name communication object: Sensor SSM 




-o--o--o-- 

Page 245


Time Switches 

Time Switches 

-o--o--o-- 

Page 246


Purpose 

Time Switches 

The clock module in ©IQHOME.NET replaces the otherwise required EIB/KNX timer clocks in 

form of hardware to be installed in the distribution (REG). The Basic version already disposes 

of 22 free available timer clock channels with endless switching dates/times. A time and 

date synchronization of other bus components (e.g. EIB auxiliary clocks, displays, mini 

panels, function modules, regulating systems etc.) is ensured through the cyclical (variably 

adjustable) output of PC system time/date on the EIB. A radio-controlled synchronization by 

means of DCF signal can be realized using a conventional PC-USB DCF radio-controlled clock 

that is available on the market. Thus, for example, an automatic switch-over from summer 

and winter daylight saving time and a 100% precision are guaranteed. When you buy this 

device outside Germany, make sure that the DCF radio signal can be received in your region. 

In addition to the standard week and year programme any other programme can be added 

and defined as standard. Holiday programmes, single day programmes etc. can be handled 

as easily as copy and reset functions. Each clock channel disposes of a manual operation 

option by means of push button. An integrated LED shows the current clock status. 

The clock channels permit to realize any time combinations for your facility functions and 

applications. The timer clocks are available in all EIS types (Professional version, Basic 

version only 1Bit "On/Off") and can be defined individually. For example, one clock can 

switch on the well and the other can carry out dimming functions or send specific values at 

specific times. 

Thanks to a user-friendly and easy operation, time and date management is quick and 

uncomplicated. In the Professional version any number of clocks can be adapted, 

theoretically one for each single data point. The limit of clock channels with an endless 

number of switching dates is only limited by the licence you acquired for the data point 

number (group addresses). 

-o--o--o-- 

Page 247


Features 

Time Switches 

Control of up to 22 free available timer clock channels with unlimited switching dates/times 

and the following features and functions: 

� 22 time switch channels for free application (in addition to the clock channels already 

used for blind and outside lighting control) 

� Day, week and year program 

� Manual operation possible with status display for each channel 

� Special days and individual programs 

� Display and output of current time/date as EIB-frame (cycl. variably adjustable) on the 

bus in EIB format, if a PC-DCF clock is used even prepared to receive date/ time by radio 

signal. 

� User-defined labelling of the time switch channels 

-o--o--o-- 

Page 248


Preconditions 

Time Switches 

To use this module there are no further requirements since this module does not call for 

specific EIB/KNX hardware. 

-o--o--o-- 

Page 249



Time Switches 

(01) Display of the 22 timer clock channels, continuously numbered 

(02) Free designation text for each channel by means of label editor 

(03) Call of the date administration assigned to the clock channel 

(04) Channel-related manual operation switch ("On/OFF" function) with LED status display 

(05) Current PC system time 

(06) Current PC system date (day & date) 

(07) User-defined module designation 





Tools") 

(10) Navigation link submenu tools 

(Button being pressed with active, lashing white LED below, if selected, our example " 

Clocks" 


(12) Current date management of the sample clock 18 

(13) Zoom function (magnifying glass) for a higher resolution in the time line window 

(14) Time line window 

(15) Event editor to enter a date/time 

(16) Calendar for date management 

(17) Programme tools of the timer clock (programme selection and definition, copy functions 

etc.) 

(18) Export function of the switching dates in *.txt format 

Page 250


The clock module is very easy to use. The clock channels on the module are continuously 

numbered (01). A freely definable text (02) that can be modified by means of the label 

editor (11) is assigned to each clock channel. Furthermore, you will find one manual 

operation switch each ("ON/OFF" function) with status LED (04) and the respective clock 

programme (03) at each channel. The LED shows the current output status of the clock 

which can also be switched directly using push-button (04). The push-button works with 

"ON/OFF" function, i.e. each time you press the key it inverts the previous key operation 

(press "On", press "Off", press "On" ... etc.). A manual manipulation by means of the key will 

always be overwritten by subsequent clock telegrams. Thus, manual operation is only 

temporary. Start the clock programme by clicking on the clock symbol (03). Now, the 

date/time window of the selected clock channel opens (12). Click on the time line window 

(14) to enter any time/date. A yellow bar indicates the activated period. Any number of 

switching times/dates (15) can be set whereas you can also administrate only "On" or only 

"Off" dates/times. The calendar function (16) can be used to define specific programmes. 

Arrangements that occur frequently can be handled with the function "Standard programme" 

(17). You can, for example, prepare one day with the switching times and assign it 

automatically to each weekday. This is also possible for single days or the weekend. In 

addition to that, you can copy complete days into other days using the copy function. By 

means of the function "Back to the standard programme" and a simple mouse click you can 

reset all special switching arrangements you made for one day to the standard programme 

without giving any new dates. Using the export function you can export all switching dates of 

the respective clock programme as *.txt file. 

The cyclical output of the system time/date can be modified variably in the project software 

or even switched off. To do so, simply remove the EIB port for these data points (group 

Page 251


addresses). Should you wish to have this information again, the port can be selected again 

and the data will be put on the bus and sent to the group addresses at the communication 

objects for time and date. 

-o--o--o-- 

Page 252



Time Switches 


can be used. 

EIB/KNX data point list clocks: 

Module TI001: 

Outputs: 

Page 253






22 pcs. clock channels: 

Module name: TI001 

Name communication object: Uhr 01 - Uhr 22 




-o--o--o-- 

Page 254


Weather station / sensors 

Weather Data & System Toolbar 

-o--o--o-- 

Page 255


Purpose 


The module weather station sensor system serves to display analogue measured values such 

as those of a weather station in a clear and central way. The module disposes of different 

measuring and display instruments. Using the integrated telegram indicator you can check 

whether measured values are received. Thanks to the history administration the measured 

values can be evaluated, printed or exported as graphics or table. 

-o--o--o-- 

Page 256


Features 


Sensor display with additional functions and history administration of 10 sensors (module 

provided for max. 15 sensors) with the following features: 

� Scalable measured value processing for one brightness sensor in general Scalable 

measured value processing for one twilight sensor 

� Scalable measured value processing for one wind sensor in m/s, km/h and wind speed in 

standard steps and text 

� Status display of a rain sensor 

� Scalable measured value processing for 4 brightness sensors assigned to the building 

sides 

� Weather data recording, Display in tables or charts with different representation filters, 

variable time periods, print function 

� Definable sensor monitoring (cyclical time monitoring) 

� Connectable frame indicator 

� Display of all sensor system measured values 

� User-defined labelling of the sensors 

-o--o--o-- 

Page 257


Preconditions 


To use this module at least one sensor must be connected via the available communication 

objects. To use the functions provided in ©IQHOME.NET we recommend at least one 

brightness sensor and one twilight sensor or a brightness sensor with a very high resolution. 

If you want to use all displays and tools we recommend the additional connection, of a wind, 

rain and temperature sensor. However, this is not absolutely necessary for the 

©IQHOME.NET functions. 


Description 


Ref. No.: N300057 




















Page 258









Benefits 



-o--o--o-- 

Page 259




The weather station sensor system is a display panel for different measured values. 

Resolution is scaled automatically. When the available communication objects are connected 

with a weather station or an analogue input via the group addresses, these measured values 

are ready for display in this terminal and can be used for other internal calculations & 

functions (outside lighting matrix, 4-side blind automatics) as well as other displays. A 

EIB/KNX communication object is assigned to each measured value display (see data point 

list EIB/KNX), e.g. the brightness sensor 01 (Sensor Hell1) (02) or the outside temperature 

sensor (Sensor HellAT) (01). Using the slide regulators (03) or keys (04), assigned to the 

measured value displays you can test (simulate) the values even without connected sensors. 

Sensor connections of the type EIS1 (1Bit) are represented as graphics (05). This refers, for 

example, to the sensors rain (Sensor Regen) (04) and twilight switch (Sensor HellDS) 

(05). When there is a wind sensor, different displays are activated in the wind sensor 

information display (06). At the same time the following values are displayed: 

� Display of the current wind situation in standard steps: 

> 118 km/h = "Hurricane" 

> 103 km/h = "Violent storm" 

> 089 km/h = "Heavy storm" 

> 075 km/h = "Storm" 

> 062 km/h = "Stormy wind" 

> 050 km/h = "Stiff breeze" 

> 039 km/h = "Strong wind" 

> 029 km/h = "Fresh breeze" 

> 020 km/h = "Moderate breeze" 

> 012 km/h = "Weak breeze" 

> 006 km/h = "Light breeze" 

> 001 km/h = "Light draught" 

= 000 km/h = "Calm" 

� Display of the current wind situation in m/s and km/h 

� Display of the current wind situation as wind speed 

All possibly required scalings and measured value preparations can be made by means of the 

sensor system toolbar. Using the integrated telegram indicator (09), that can be switched 

on separately, you can check the data flow of the individual sensors. Incoming telegrams are 

then represented by means of LED (08) at the measured value display of the respective 

sensor. 

Page 260


Telegram indicator 

The timers for the telegram indicators are fixed in the programme. An activated sensor 

monitoring function (by means of the sensor system toolbar) is also indicated directly by a 

flashing „Malfunction“ message at the measured value display as soon as there is a 

malfunction (exceeding the cycle monitoring function). 

Display "Sensor malfunction" (flashing) 

Using the history function (17) all measured values can be administrated as table or chart 

(21) with different representation filters, time ranges and print function (24). In the legend 

(23) the graphics for the sensors that have possibly been connected are defined. Use the 

menu (24) to call the different representations (table, graphics), time ranges and other 

functions. The zoom function can be used to define the resolution of the time line. Use the 

"Back" (25) key to return to the module weather station sensor system. 

The module (10) can be labelled using the label editor (18). To do so, a separate page is 

called. 

(01) Measured value display of a sensor 

(02) Individual labelling of the sensors by means of the label editor of the sensor system 

toolbar 

(03) Slide regulator to simulate measured values and parallel status display 

(04) Operating key to simulate measured values (Bit) and parallel status display (example 

rain sensor) 

(05) Operating key to simulate measured values (Bit) and parallel status display (example 

twilight switch) 

(06) Information display for wind situation as text in standard steps, wind speed, m/s and 

km/h 

(07) Connectable telegram indicator for data flow display of individual sensor telegrams 

(08) Telegram indicator display for sensor data flow display 

(09) Timer for telegram indicator display 


(11) Display of current system time&date 



(13) Navigation link back to "Tools" 



Tools") 

Page 261



(Button being pressed with active, flashing white LED below, if selected, our example 

"Weather station sensor system " 

(16) Navigation link submenu to tools/sensor system toolbar 

(17) Navigation link submenu to tools/weather station sensor system/history 


Page 262


-o--o--o-- 

Page 263





can be used. 

EIB/KNX data point list weather station sensor system: 

Module SE001: 

Inputs: 

Page 264






Sensor input, outside temperature: 

Module name: SE001 

Name communication object: Sensor AT 

EIB/KNX data point type: EIS 5 (2 Byte Float) 

Sensor input, brightness 01: 


Name communication object: Sensor Hell1 


Sensor input, brightness 02: 




Sensor inpu,t brightness 03: 




Sensor input, brightnesse 04: 




Sensor input, brightness in general: 


Name communication object: Sensor HellA 

Page 265


Sensor input, twilight: 


Name communication object: Sensor HellD 


Sensor input, twilight switch: 


Name communication object: Sensor HellDS 


Sensor input, wind: 


Name communication object: Sensor Wind 


Sensor input, rain: 


Name communication object: Sensor Regen 





-o--o--o-- 

Page 266


Central Command Terminal 

Central Command Terminal and Definition 

Page 267


-o--o--o-- 

Page 268


Purpose 


The central terminal serves to execute 16 freely definable central building functions of type 

1Bit (On/Off) with individual labelling of the central commands. The central terminal 

manages up to 10 central commands for E/O-functions such as lighting and up to 6 central 

commands Up/Down for blind, roof light and/or garage door controls. 

Always 3 out of a total of 10 different central commands can be assigned to up to 80 

switching and 6 dimming channels of the operating console with presence simulation. The 

central command assignment for blind applications is executed directly at the actuators by 

means of ETS. 

-o--o--o-- 

Page 269


Features 


Administration and control of up to 16 central building functions with the following functions 

and features: 

� Free definition of 10 On/Off central functions and 6 Up/Down central functions for 

motor-controlled applications 

� Direct activation of the actuator single addresses, thus, no other central address at 

actuator required 

� Thus, difference between the switching mode of the actuators and e.g. the LED- display 

at the key sensor is prevented 

� User-defined labelling of the central commands 

� Free assignment of max. 3 central commands to each of the 80 individual switching 

groups of the operating console 

� Simple Drop Down menus to select one central command out of max. 10 definable 

commands 

� Definition of the switch-on brightness (0-100%) with central „On“ functions for 6 

dimmable lighting groups 

� Comprehensive combinations 

-o--o--o-- 

Page 270


Preconditions 


To use this module there are no special requirements. If you do not want to use a central 

function, do not use the available communication objects. To do so, just remove the existing 

group addresses at these objects. 

-o--o--o-- 

Page 271

General 




Using the terminal for „Central commands“ you can prepare any number of central building 

functions (max. 10 for switching and dimming groups) and assign these to the respective 

switching and dimming groups from the operating console (80 switching and 6 dimming 

groups) by means of the module "Central command definition ". All central commands can 

be further used in the EIB/KNX system e.g. for a central push-button or a lock switch contact 

at the front door etc.. Communication objects of this module that are assigned to external 

binary inputs etc. will then release the following actions. 

Central command module: 

In the central command operating field for On/Off functions (01), you will find the 

continuous numbers of the commands with label texts that can be edited (02) using the 

label editor (14) as well as the operating keys to call the individual commands (03) divided 

into either only "On" or "Off" command. When the key is pressed again the commands are 

sent again on the bus (Command Befehl). This also refers to the motor central commands 

(04) such as blind, awning, roof light and/or garage door control etc.. Here, the operating 

keys are divided into only "Up" ("0" telegram) or "Down" ("1" telegram) (05). These 

commands too are sent on the bus again when the key is pressed again. (Command Befehl). 

Using the navigation key in the submenu (19) you go to the assignment pages (Terminal 

Definition). 

The integrated operating hour counter (02) was integrated in this central module. It serves 

to count the operating hours of any switchable (1Bit) appliance (lamp, pump, valve etc.) in 

your facility. It always counts the time during which the appliance is "On" ("1" telegram). 

You can enter the name of the monitored appliance in the label editor (14). The display 

shows the current operating time in seconds:minutes:seconds, whereas the display is only 

updated after every 10 seconds. The values are persistent. Thus, when the latest data is 

loaded again when the system is started next. Use the reset key (07) to set the operating 

counter to "Zero". The key next to it (08) shows the current status of the monitored 

appliance and can also be controlled directly (On/Off). 

The surface consists of several operating pages, the central terminal (module ZA001) and 

the terminal for central command definition (assignment to the switching and dimming 

groups), including the modules ZD001-ZD006: 

Central terminal (module ZA001): 

(01) Display of the 10 On/Off central building functions 

(02) Designation of the 10 On/Off central building functions with individual label option 

(03) Key to call the central function, divided into "On" and "Off" command 

(04) Display of the 6 Up/Down central building functions 

(05) Personal designation of the central building functions with key to call the central 

function, divided into "Up" and "Down" command 

Page 272


(06) Information display of the integrated operating hour counter 

(07) Reset key of the operating hour counter 

(08) Operating button for the appliance counted with the operating hour counter 

(09) User-defined central terminal labelling 




(12) Navigation link main menu (Button being pressed with active, flashing white LED 

below, if selected, our example "Tools") 

(13) Navigation link submenu tools (Button being pressed with active, flashing white LED 

below, if selected, our example "Central Terminal") 


In the label editor you can change the name of the console (16) as well as all 16 central 

building functions and the designation of the appliance for the operating hour counter. 

Generally, all texts that are marked yellow can be modified in the label editors of the 

individual modules by simply clicking on the text (15). Use the arrow key (18) to return to 

the main module the labels of which have just been modified. 

Page 273

Module central command definition: 


Here, up to 3 central commands (03)(04)(05) can be assigned to the switching and 

dimming channels. Marked channels (02) only show the assignment to the scenario 

manager. 

After having set the functions in the central command module, these are now available in the 

drop down menus (06) for free selection and assignment to the individual switching and 

dimming groups (01). The individual labels of the switching and dimming group channels 

(01-80) are automatically taken from the label editor of the operating console module and, 

thus, cannot be modified with the label editor (14) of this module page. Using the label 

editor of this page you can change the console name (09). Use the arrow key/s in the 

navigation submenu (07) to go to the next or previous page. 

By means of a drop down menu each individual group can be matched with one or max. 

three of the central commands you defined. For example, you have defined the central 

command "Central Total Off ". This command can be entered at all desired groups using the 

assignment page "Central command definition". However, the central command "Central off 

basement" is to be entered only at all switching and dimming groups in the basement. For 

this application, only switching and dimming groups of the basement are assigned to this 

command. 

Special cases are the slide regulators of the dimmable lights. These can be used to fix the 

switch-on values for sample command „Central ON“. At „Central OFF“ the dimmable lights 

Page 274


switch off, at „Central ON“ the lights go on with the fixed value. 

The central commands send their commands directly to the communication objects of the 

linked channels (switching and dimming groups), which makes is unnecessary to enter 

further group addresses at the actuators and sensors. Thus, a difference between the 

actuator switching status and, for example, the LED display at the push-button sensor is 

excluded. 

Page 275


-o--o--o-- 

Page 276





can be used. 

EIB/KNX data point list central commands & definition: 

Module ZA001: 

Outputs: 

Page 277






06 pcs. outputs, central command motor system Up/Down: 

Module name: ZA001 

Name communication object: Zentral Jalousie 01 - Zentral Jalousie 06 


10 pcs. outputs, central command On/Off 

Module name: ZA001 

Name communication object: Zentral E-A 01 - Zentral E-A 10 




-o--o--o-- 

Page 278

- 4 - 

4-Side blind automatics 170 

- A - 

Administration 27 

Alarm management 54 

Alarm outputs 88 

Appendix 32 

Audio Console 223 

- B - 

Basic Version 36 

Burglar alarm system 71 

- C - 

Central Command Terminal 267 

Central terminal 82 

Climate Console 193 

- D - 

Datapoint groups 43 

Datapoint Requests 49 

Datapoints 40 

Diagnosis 29 


Index 

- E - 





EIB/KNX Data 182, 253, 264, 277, 101, 155, 140, 168, 122, 204, 220, 231, 244 

EIB/KNX Inputs 192 

Elvis structure 16 

English - Manual 4 

Error messages 31 

Examples of applications 12 

- F - 

Features 173, 146, 257, 270, 73, 129, 161, 111, 195, 212, 225, 238, 248 

- I - 

Info-Alarm-Message 109 

Inputs (contacts) 93 

Inputs (detectors) 96 

Installation 19, 33 

Installation 19, 33 

Introduction 6 

- L - 

Load project... 37 

Page 279

- M - 

Media Console 209 

Message ports 56 

Message recipients 58 

Messages 59 

- N - 

Navigation 65 

- O - 

Operating Console 144 

Operation 23 

Outside lighting matrix 126 


- P - 

Preconditions 8, 174, 147, 258, 271, 74, 130, 162, 112, 196, 213, 226, 239, 249 

Professional Version 60 

Project software 35 

Purpose 171, 145, 256, 269, 72, 127, 160, 110, 194, 211, 224, 237, 247 

Purpose 171, 145, 256, 269, 72, 127, 160, 110, 194, 211, 224, 237, 247 

- R - 

Reference contact 91 

Reminder function 159 

RS232/USB-Port 45 

- S - 

Scenario-Manager 210 

Sensor System Toolbar 235 

Start screen 67 

Start up and terminate 21 

Support 64 

- T - 

Terminal 30 

Time Switches 246 

Topology 80 

- U - 

User management 50 

User manual 15 

- W - 

Weather station / sensors 255 

Page 280

The details and data contained in this documentation are subject to modification without 

prior notice. Without the express written consent of EIBMARKT GmbH and IT GmbH no part 

of this documentation may be duplicated for any purpose whatsoever or transcribed 

regardless of the manner or means, electronic or mechanical, by which this is performed. 

Copyright © 1997-2005 EIBMARKT GmbH. All rights reserved. 

Windows is a trademark of the Microsoft Corporation. 

EIB and ETS are registered trademarks of EIBA s.c. Brüssel 

The logo is a registered word- and picture mark of EIBMARKT GmbH and KNX/EIBA s.c. 

Brussels. 

07/2005 

EIBMARKT GmbH

EIB/KNX Data - EIBMARKT® GmbH Holding

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?