Comm-Tec EIB Manuale utente

- 1 -

User Manual

for the

COMM-TEC EIB Gateway

CTG-KNX/IP (v1.0.1)

- 2 -

Table of contents

1 Introduction.....................................................................................................................................3

1.1 Aims?..........................................................................................................................................3

1.2 Role of the EIB installer..............................................................................................................3

1.3 EIB from the AMX programmer’s point of view...........................................................................3

1.4 EIB details when using the Gateway..........................................................................................5

2 Hardware........................................................................................................................................6

2.1 Interfaces, Indication and Operating Devices.............................................................................6

2.2 Installation ..................................................................................................................................6

2.2.1 Connection Gateway – TCP/IP Interface............................................................................6

3 Programming..................................................................................................................................7

3.1 Integrating the Module................................................................................................................7

3.2 Analyzing feedback signals........................................................................................................8

3.3 The NetLinx module interface.....................................................................................................9

3.3.1 Commands for module .......................................................................................................9

Description .........................................................................................................................................9

3.3.2 Feedback from module.....................................................................................................11

Description .......................................................................................................................................11

3.3.3 Terminal Mode..................................................................................................................11

3.3.4 Channels and levels .........................................................................................................14

4 Data Types...................................................................................................................................14

5 Appendix A – Sample program.....................................................................................................15

5.1 Notes EIB table.........................................................................................................................15

5.2 Notes for programming.............................................................................................................15

5.2.2 Example 2 - Structure of EIB table with SEND_COMMANDS..........................................17

5.2.3 Example 3 – Enter addresses from file.............................................................................18

5.2.4 Example 4 – Main program...............................................................................................19

6 Appendix B – EIB_Tools.AXI........................................................................................................20

7 Appendix C – Comparison with previous version.........................................................................21

7.1 Structure / Generation of filter table in gateway .......................................................................21

7.2 Controllling actuators................................................................................................................21

7.3 Feedback..................................................................................................................................21

8 Appendix D – What to do if it does not work?...............................................................................22

Siemensstrasse 14

D-73066 Uhingen

Tel.: +49 (0)7161/3000-0

Fax: +49 (0)7161/3000-400

- 3 -

1 Introduction

1.1 Aims

The software module is being used to connect AVIT and AMX control systems to the "European

Installation Bus" EIB ("Instabus"). It provides an easy to use interface for developers to comfortably

access the

bus.

1.2 Role of the EIB installer

It can not be expressed strongly enough: when connecting to an EIB system, solid knowledge of the

EIB and close contact to experienced EIB installers is strongly recommended. A faulty set Reading

flag in an actuator, or a restrictively programmed line coupler can be really hard to find without good

analysis tools.

There is now way the Netlinx module is able to configure an EIB system. The package is used to

connect to a working EIB, and can access only those bus elements whose usage is permitted.

Because of that, it should be planned together with the EIB installers if all desired functions are

allowed to the bus components.

1.3 EIB from the AMX programmer’s point of view

Analog to AMX systems is the European Installation Bus – as the name implies – a bus system: all

components are in principle connected to the same wire and share the available bandwidth.

The bus itself is a 2-wire cable, used to supply 24VDC to the devices, as well as transferring data

between them.

Unlike AMX, the EIB system is a decentralized structure – there is no special master controlling the

communication, but any device can send data to any other device.

A sophisticated protocol ensures that only one device is sending at any time, and collisions are

avoided as much as possible.

All communication happens in the form of telegrams. A telegram is a data packet, that consists of the

following parts:

• Source ID – Hardware address of the transmitting device

• Destination address – Group address of the receiving devices

• User data

A telegram can be transmitted to several destination devices at the same time, i.e. to switch off all

lamps in a room simultaneously.

So there is a fundamental difference between both source and destination addresses:

A source address is a hardware address, describing the device that is transmitting the telegram.

A destination address is a group address, describing the function to be influenced.

Thus each device connected to EIB has exactly one hardware address, but may have several group

addresses.

Furthermore, it is possible and common for several devices to respond to the same group address.

The EIB installer assigns both address types – the hardware addresses describing type and number

of utilized devices and assigned during planning and installation. Hardware addresses are of no

concern for the gateway.

The much more important addresses for AMX are the group addresses.

They define the functions an EIB installation can perform. So functions are simply used by

transmitting specified values to group addresses.

- 4 -

Figure 1 – Process of Communication

NetLinx Master

EIB

Gateway

NetLinx

Module

NetLinx

Program Virtual

Device

- 5 -

1.4 EIB details when using the Gateway

In principle, the EIB gateway CTG-KNX/IP is a normal EIB device, and can therefore be connected at

any location to the EI bus. Unlike simple actuators or sensors it can be responsible for a large amount

(up to 3000) of group addresses – a normal dimmer for example, just reacts to four addresses.

So one must be very careful to ensure that the gateway has a real chance to react to all bus

telegrams of interest. Especially when using line couplers, solid planning is absolutely necessary. The

following points should be seriously considered:

On the one hand all telegrams should reach the gateway. If line couplers are inserted between

gateway and controlled components, their filter tables are to be programmed in such a way that all

relevant telegrams are really passed through.

On the other hand the EI bus couplers are slow – upon receipt of a telegram, an EIB device needs

some time until the next telegram can be accepted. Especially scene modules can generate a flood

of telegrams, which are transmitted to all actuators participating in the scene.

Because these are usually different devices, the down time of the bus couplers does not matter –

each coupler has enough time to recreate before the next telegram gets received.

The situation with the gateway is different: normally all participating group addresses of a scene are of

interest – the gateway needs a recovery time and can read all telegrams, even with high bus load.

However, with the activation attention has to be paid, that the activated actuators are given enough

time!

CTG-

KNX/IP

CTG-

KNX/IP

- 6 -

2 Hardware

2.1 Interfaces, Indication and Operating Devices

Connections :

230 V EIB

RJ45

LEDs : Busspannung flashes when bus voltage drops below 15V

Bustelegramm indicates telegrams on the EIB

TX indicates data transmission from Gateway to AVIT / AMX

RX indicates data transmission from AVIT / AMX to Gateway

Betrieb is lightened when voltage feed is being impressed

Prog.-LED flashes when the Gateway is being set to programming mode on

the EIB-side

Push-button : Prog.-Key sets Gateway to programming mode (on EIB-Side)

2.2 Installation

2.2.1 Connection Gateway – TCP/IP Interface

The Gateway is being connected to the network by a standard network cable.

- 7 -

3 Programming

3.1 Integrating the Module

At first, the program needs to get the information, what the Gateway’s IP-Address is.

This can be done by the Online_Event of the virtual Devices:

DATA_EVENT[vdvEIB]

{

ONLINE :

{

SEND_COMMAND vdvEIB,'IP=172.16.100.123'

}

(also see Appendix)

The Port for the Gateway has been set to 10002, which can not be edited.

The IP-Address will be set by the included gateway software.

On delivery, the Ethernet Address of the Gateway is set to 192.168.1.106.

The interface for the module, and for the communcation with the EIB-Gateway provides the virtual

device vdvEIB. Communication with the gateway is ONLY via the virtual device.

A complete documentation of available commands and string feedback is contained in chapter

„NetLinx module interface“.

The communication module (COMM module) translates between standard command interface on

NetLinx side and the protocol for EIB connection.

The communication module for EIB connection is integrated with the following source code line:

DEFINE_MODULE 'CTEIB7_mod' EIB7( vdvEIB,

dvEIB,

lEIB_Value)

The parameters are as follows:

•vdvEIB - is the virtual device for communication with the module

•dvEIB - is the physical interface for EIB connection (gateway)

•lEIB_Value - is the central value array of the EIB actuators (type LONG!)

This Array hast to be defined in the section DEFINE_VARIABLE, and has to have a size of 3000:

DEFINE_VARIABLE

...

LONG lEIB_Value[3000]

...

The module also attends to the correct initialization of the serial interface, thus it is not necessary to

set the baud rate, for instance.

To access/analyze actuators on the bus, the EIB group addresses must be introduced to the program.

This is done in an external file, mapping group address, type, poll conjunction and additional features

- 8 -

on an „AMX number between 1 and 3000. Communication with the actuators concerned is only made

via this number.

This tabel is integrated with the following source code line:

#INCLUDE 'EIB_Table.axi'

An example for such a file and a sample program is contained in Appendix A.

In addition, the file EIB_Tools.AXI should be integrated to have easy access to commonly used

functions (see Appendix B).

#INCLUDE 'EIB_Tools.axi'

3.2 Analyzing feedback signals

All feedback signals should be analyzed in a Data_Event. One DATE_EVENT is being released for

each feedback signal – so there is exactly one feedback in DATA.TEXT ! In case of several feedback

signals, the same amount of Events will be released accordingly.

- 9 -

3.3 The NetLinx module interface

3.3.1 Commands for module

Commands to the module always take place per SEND_COMMAND to the virtual device.

The module knows the following commands:

Command Description

ADD=<No>:

<Type>:

[:Flags]

Add an EIB group address to list

Note: Flags are optional

<No> - 1_3000 = AMX number of actuator

<Type> - Actuator type (Switch, Dim4, 1Byte, 2Byte, 3Byte, 4Byte)

<GrpAdr> - EIB group address in 2 or 3 grouped display

<Flags> - EIS5 - value is reported additionally as ASCII float value. The EIB value is converted

according to EIS5 standard (only valid for 2Byte actuators)

- Time - value is reported additionally as ASCII time (hh:mm:ss) (only valid for 3Byte

actuators)

- Date - value is reported additionally as ASCII date (Caution: AMX format: MM/DD/YY)

(only valid for 3Byte actuators)

- PS – actuator is automatically polled with Start of AMX system

Flags are separated by commas

Examples:

SEND_COMMAND vdvEIB,’ADD=13:Switch:1/0/11’

SEND_COMMAND vdvEIB,’ADD=17:1BYTE:4/7/12:PS’

SEND_COMMAND vdvEIB,’ADD=45:2BYTE:3/0/11:EIS5’

SEND_COMMAND vdvEIB,’ADD=12:3BYTE:2/1/101:TIME,PS’

DATE=<No>:

<Date> Setting the date

Note: Only valid for actuators type 3Byte

<No> - 1 … 3000 = AMX number of actuator

<Date> - date in format dd/mm/yy

Example: SEND_COMMAND vdvEIB,’DATE=17:14/08/06’

DATE? <No> Inquiry date value

Note: Only valid for actuators type 3Byte

<No> - 1 … 3000 = AMX number of actuator

Example: SEND_COMMAND vdvEIB,’DATE?17’

DEBUGON=<Level> Activating the debug reports

<Level> - (… upcoming …)

With activated debug report all actuators of the terminal are listed, which can be accessed via

EIB. This allows simple diagnostics.

Example: SEND_COMMAND vdvEIB,’DEBUGON=1’

DEBUGOFF Deactivating the debug reports

Example: SEND_COMMAND vdvEIB,’DEBUGOFF’

EIS5=<No>:

<floating point

value>

Setting an EIS5 value

Converts a floating-point value mapped in ASCII into 2Byte EIS5 value before transfer.

<No> - 1 … 3000 = AMX number of actuator

<Floating Point Value> - number in the range of –671088,64 and 670760,96

Note: Only valid for actuators type 2Byte

Example: SEND_COMMAND vdvEIB,’EIS5=12:24,3’

- 10 -

Command Description

EIS5? <No> Inquiry EIS5 value

Converts the 2Byte raw data into ASCII string with floating point

Note: Only valid for actuators type 2Byte

<No> - 1_3000 = AMX number of actuator

Example: SEND_COMMAND vdvEIB,’EIS5:12’

GET=<No>

GET? <No> Inquiry of actuator value stored in the module

Note: Creates no telegram on EIB (for synchronization of master-to-master connection only use

POLL command)

<No> - 1 … 3000 = AMX number of actuator

Example: SEND_COMMAND vdvEIB, ’GET=17’

POLL=<No>

POLL? <No> Inquiry current value of actuator (for synchronization of master-to-master connection only use

POLL command)

<No> - 1 … 3000 = AMX number of actuator

Examples:

SEND_COMMAND vdvEIB,’POLL=17’

SEND_COMMAND vdvEIB,’POLL?17’

POLLDELAY=<Value> Set pause between (automatic) value inquiries

<Value> - 0-2 (default=1)

Note: 0 stands for very fast and should not be used, because otherwise the gateway would

create a high bus load. For installations with slow bus couplers (BCU1), the value 2 should be

selected.

Example: SEND_COMMAND vdvEIB,’POLLDELAY=2’

SENDDELAY=<Value> Delay between commands to EIB. Value is the time in 1/10 sec. The value 0 deactivated the

delay

SET=<No>:<Value> Set actuator

Note: Observe actuator type in value range! The module limits the value range automatically to

max valid range of the accessed actuator

<No> - 1 … 3000 = AMX number of actuator

<Value> - value to be set

Example: SEND_COMMAND vdvEIB,’SET=5:1’

STARTDELAY=<Value

>Sets point in time, when the module is activated, time for booting of master.

<Value> - time in seconds (default = 30, value should not be changed)

Example: SEND_COMMAND vdvEIB,’STARTDELAY=40’

STATE? Output of current module status in terminal

TIME=<No>:<Time> Set current time

Note: Only valid for actuators type 3Byte

<No> - 1 … 3000 = AMX number of actuator

<Time> - time in format hh:mm:ss

Example: SEND_COMMAND vdvEIB,’TIME=8:13:15:00’

TIME=<No> Inquiry of time

Note: Only valid for actuators type 3Byte

<No> - 1 … 3000 = AMX number of actuator

Example: SEND_COMMAND vdvEIB,’TIME?8’

UPLOAD Synchronizing internal tables – gateway

Writes the current internal table to gateway – only for debugging

VERSION Output of current module version on monitor

Example: SEND_COMMAND vdvEIB,’VERSION’

Command Description

WHEN=<No>:<No2> Definition of poll triggers

Note: The trigger is activated when the first address is accessed, not when changing a value

for an address.

<No> - 1_3000 = AMX number of actuator activating the polling

<No2> - 1_3000 = AMX number of actuator to be polled

Example: SEND_COMMAND vdvEIB,’WHEN=32:12’

Questo manuale è adatto per i seguenti modelli

Indice

Altri manuali Comm-Tec Portale

Comm-Tec

Comm-Tec CTG-KNX/IP Manuale utente

Manuali Portale popolari di altre marche

LST

LST M500RFE-AS Manuale utente

Kinnex

Kinnex Media Gateway Manuale utente

2N Telekomunikace

2N Telekomunikace 2N StarGate Manuale utente

Mitsubishi Heavy Industries

Mitsubishi Heavy Industries Superlink SC-WBGW256 Manuale utente

ZyXEL Communications

ZyXEL Communications ZYWALL2 ET 2WE Manuale utente

Telsey

Telsey CPVA 500 - SIP Manuale utente

RTA

RTA 460A-NNA4 Scheda tecnica

Shaw

Shaw Gateway HDPVR Manuale utente

ABB

ABB VSN900 Guida rapida

Commander

Commander Pulse Manuale utente

2N Telekomunikace

2N Telekomunikace ATEUS EasyGate 501309E Manuale utente

NETGEAR

NETGEAR C6300BD Manuale utente

Amit

Amit CDW531AM Manuale utente

HMS

HMS Netbiter EasyConnect EC150 Manuale utente

Huawei

Huawei EchoLife HG620 Manuale utente

AT&T

AT&T U-verse 3801 Manuale per l'uso e la cura

Logic IO

Logic IO RTCU MX2 turbo Manuale utente

Suttle

Suttle MediaMAX MXM-521 Manuale utente