IntesisBox KNX TP-1 (EIB) User Manual

IntesisBox® BACnet/IP Server

KNX TP-1 (EIB)

User's manual

Issue Date:2014/12/16

r18 eng

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

2 / 31

© Intesis Software S.L. All Rights Reserved.

Information in this document is subject to change without notice. The software described in
this document is furnished under a license agreement or nondisclosure agreement. The
software may be used only in accordance with the terms of those agreements. No part of
this publication may be reproduced, stored in a retrieval system or transmitted in any form
or any means electronic or mechanical, including photocopying and recording for any
purpose other than the purchaser’s personal use without the written permission of Intesis
Software S.L.

Intesis Software S.L.
Milà i Fontanals, 1 bis - 1º
08700 Igualada
Spain

TRADEMARKS
All trademarks and tradenames used in this document are acknowledged to be the copyright of their respective holders.

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

3 / 31

Gateway for the integration of KNX TP-1 (EIB)
devices into BACnet/IP control systems.

Models available for this gateway, with their following Order codes:

IBOX-BAC-KNX-100
Tiny model supporting connection to up to 100 internal data points.

IBOX-BAC-KNX-A
Basic model supporting connection to up to 500 internal data points.

IBOX-BAC-KNX-B
Extended model supporting connection to up to 3000 internal data points.

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

4 / 31

INDEX

1.

Description ...................................................................................................... 5

1.1 Introduction ................................................................................................. 5

1.2 Functionality ................................................................................................. 6

1.3 Capacity of IntesisBox ................................................................................... 7

2.

Interfaces ........................................................................................................ 8

2.1 BACnet ........................................................................................................ 8

2.2 KNX TP-1 (EIB) ............................................................................................. 8

3.

Quick Setup ................................................................................................... 11

4.

Connection .................................................................................................... 12

4.1 Power device .............................................................................................. 12

4.2 Connect to KNX ........................................................................................... 13

4.3 Connect to BACnet ...................................................................................... 13

4.4 Connect to PC (LinkBoxBacnet) ..................................................................... 13

5.

LinkBoxBacnet. Configuration & monitoring of IntesisBox BACnet series ................ 14

5.1 Project configuration .................................................................................... 14

5.1.1 Connection configuration ........................................................................ 14

5.1.2 Signals configuration ............................................................................. 17

5.1.3 BBMD configuration ............................................................................... 23

5.1.4 Saving the configuration ........................................................................ 25

6.

IntesisBox® and ETS ....................................................................................... 27

6.1 Integration of IntesisBox® in ETS .................................................................. 27

6.2 Import ETS files to LinkBoxBacnet ................................................................. 28

7.

Mechanical & electrical characteristics ............................................................... 30

8.

Dimensions.................................................................................................... 31

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

5 / 31

1. Description

1.1 Introduction

This document describes the integration of KNX TP-1 (EIB) systems with BACnet ASHRAE
135 – 2001 Annex J - BACnet protocol compatible devices or systems using the gateway
IntesisBox BACnet/IP Server - KNX.

This document assumes that the user is familiar with KNX and BACnet/IP technology and
technical terms.

From now on, and with the aim of easy the read of this document, the words "gateway" or
“IntesisBox” are used instead of IntesisBox BACnet/IP Server - KNX. Any other use of the
word "gateway" not meaning IntesisBox BACnet/IP Server - KNX will be specifically
indicated.

The aim of this integration is to make accessible KNX system signals and resources from a
BACnet/IP based control system or device, as if it was a part of the own BACnet system and
vice-versa. For this, the gateway acts as a BACnet/IP Server device in its BACnet interface,
allowing other BACnet/IP devices to perform subscription (COV) requests, and also read and
write its internal points. From the KNX system point of view, the gateway simulates a KNX
device and acts as if it was one more device into the KNX system.

Figure 1.1 Integration of KNX and BACnet/IP using IntesisBox BACnet/IP Server -

KNX gateway

BACnet/IP

SYSTEM

Ethernet

IntesisBox BACnet/IP Server

LinkBoxBacnet

Configuration

Software

Only needed for configuration

KNX

KNX

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

6 / 31

1.2 Functionality

The integration operation is as follow:

From the KNX system point of view, in the startup process of the gateway and also after a
detection of a KNX bus reset, the gateway polls the KNX signals configured to be updated in
this situation and maintain the received values in memory to be served to the BACnet
system when requested. Also listen for any KNX telegram related to the internal points
configured in it and acts accordingly to the configuration of the related point.

From the BACnet system point of view, after the startup process, the gateway listens for
any subscription (COV) request, serves any polling request or performs any writing request
of its internal points received from BACnet system. The values received from BACnet
become available to be read (and when applicable, written) by the KNX system and vice­versa.

If a signal has been configured as of type “T” Transmit (in the KNX part), any new value for
the signal coming from the BACnet system is notified to the KNX system with the
corresponding telegram.

When, from the KNX system, a signal is changed (written from any other KNX device for
example), the new value is updated in the gateway's memory and, if this signal is
associated to a BACnet active subscription then the new value will be sent to the
subscripted BACnet device(s).

Also the following functionality is supported by the gateway:

For every point, in the KNX part, one main group address and different listening group
addresses can be defined. With this, from KNX, every point can be addressed not only using
its main group address but also using the other defined listening addresses for the point.

Any change in a gateway's point with the feature “T” activated (in the KNX part), will force
the transmission of this point value with the corresponding telegram to the KNX system.

When the gateway starts up, or after an KNX bus reset, all the points with the feature “U”
or "U2" activated (in the KNX part) will be forced to be read in the KNX system to update its
values in the gateway’s internal memory.

Any point with the feature “W” activated (in the KNX part), can be written in any moment
from the KNX system.

Any point with the feature “R” activated (in the KNX part), can be read in any moment from
the KNX system.

All the mentioned features (W,R,T,U) related to the KNX interface are deeply explained in
section 5.1.2.

KNX EIS (data types) supported are: switching (1 bit), dimming (4 bit), float (16 bit),
scaling (8 bit), drive control (1 bit), priority (2 bit), float IEEE (32 bit), counter (8 bit),
counter (16 bit), counter (32 bit), ASCII char (8 bit).

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

7 / 31

1.3 Capacity of IntesisBox

Element Tiny

version

Basic

version

Extended

version

Notes

Type of BACnet
devices

Only those supporting BACnet/IP.

Number of BACnet
points

100 500 3000

Maximum number of points that can be

defined in the virtual BACnet

device

inside the gateway.

Number of BACnet
subscribers

8 8 8 Maximum number of BACnet

subscribers accepted by the gateway.

Number of BACnet
subscriptions
(COV) requests

1000 1000 6000 Maximum number of BACnet

subscriptions (COV) requests accepted

by the gateway.

KNX
groups

500 500 3000

Maximum number of different KNX

group addresses that can be defined.
KNX
listening
addresses

1000 1000 1000

Maximum number of different KNX

group addresses that can be defined as

listening addresses, one or more of

these listening addresses can be

assigned to every point. With this,

more than one KNX group address of

the KNX system can actuate on the

same gateway's point.

There are two different models of IntesisBox BACnet/IP Server - KNX, with different
capacity every one of them.

• Tiny model supporting connection to up to 100 internal data points.

Ref.: IBOX-BAC-KNX-100.

• Basic model supporting connection to up to 500 internal data points.

Ref.: IBOX-BAC-KNX-A.

• Extended model supporting connection to up to 3000 internal data points.

Ref.: IBOX-BAC-KNX-B.

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

8 / 31

2. Interfaces

This section gives the reader an idea on how a KNX system/installation is integrated with
IntesisBox BACnet. It is not meant to provide an in-depth explanation on how BACnet or
KNX technology work as understanding the protocol principles is assumed throughout this
document.

The IntesisBox behaves as a regular BACnet device inside the BACnet system integrating all
the KNX devices. Note that each datapoint defined on IntesisBox will have two associated
data types:

• One data-type, related to the BACnet/IP protocol of the IntesisBox

• And another data-type, related to KNX side of IntesisBox

Conversions of data values from KNX to BACnet/IP data-types (and vice versa) are
internally performed at application level of IntesisBox, and keeping the highest possible
level of precision, with the restrictions of the data-type itself. Further detail on behavior and
data-types of the BACnet/IP and KNX interfaces of IntesisBox is given in the following
sections.

All configuration of IntesisBox BACnet is done using software tool LinkBoxBacnet. This tool,
covered in depth in section 5, is used to define the KNX and BACnet related parameters on
each of the datapoints defined in IntesisBox.

2.1 BACnet

The IntesisBox integrates all the KNX devices in a single BACnet device. The communication
with the other BACnet devices is done via the Ethernet port of the gateway which
implements the BACnet ASHRAE 135 – 2001 Annex J - BACnet protocol.

In addition, IntesisBox can be configured to be a BBMD (BACnet Broadcast Management
Device). See details in section 5.1.3.

The supported BACnet Objects and Building Blocks can be found in the PICS document
available on the web:

http://www.intesis.com/pdf/IntesisBox_BACnet_IP_Server_KNX_PICS.pdf

Configuration of all BACnet/IP parameters of IntesisBox and their links to KNX using
LinkBoxBacnet software tool is covered in section 5.1.

2.2 KNX TP-1 (EIB)

IntesisBox BACnet/IP Server - KNX supports the KNX TP-1 physical layer, as defined in the
KNX standard. It behaves as one more device of the KNX system, with the same
configuration and functional characteristics as other KNX devices.

KNX TP-1 (EIB) bus provides a 30V DC current, which can even directly power certain low­consumption KNX devices. IntesisBox does not drain any significant current from the KNX
bus - it has a separate own power supply. Another important electrical aspect is that the
KNX TP-1 (EIB) port of IntesisBox is optically isolated (~2500Vrms AC) from all its other
ports (EIA232, EIA485, Ethernet) and power supply.

At logical level, all KNX devices feature an interface of communication objects, by which
their functionality is abstracted. As a basic example, a KNX interface of an AC indoor unit

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

9 / 31

would typically consist of an interface of datapoints such as “On/Off”, “Setpoint
temperature”, “Operating mode”, etc.

Associations between communication objects from different KNX devices are actually done
by means of so-called group addresses.

KNX telegrams within a working KNX installation are always addressed to a certain KNX
group address. Typically, whenever a communication object on a KNX device changes its
value, the new value is updated to the bus, by sending a “write” telegram addressed to its
associated group address. The rest of KNX devices in the installation that have a
communication object associated to this group address will act accordingly on reception of
the new value.

Other operations are possible. KNX devices can also decide to read the current value of the
communication objects, by sending a “read” telegram to a certain group address (previously
known to be associated to the targeted comm. object). This operation is performed by many
devices on bus start-up or recovery – in this way, the device gets the latest value of the
group addresses it has associated right from its start-up.

Each datapoint defined in IntesisBox KNX configuration needs to have at least a single KNX
group address associated with it. This group address will be used either for sending updates
to KNX of the datapoint value (that have been generated on the other BACnet/IP interface
of the IntesisBox), or receiving updates from KNX of the datapoint value (that will be
propagated to the BACnet/IP side in this case)

From the point of view of KNX functionality, each datapoint of IntesisBox can hold following
group address associations:

• A single KNX group address with which update/write telegrams will be sent,

whenever the datapoint changes (as a result of a change coming from the other
interface of IntesisBox, BACnet/IP in this case).

• One or more KNX group addresses from which this datapoint of IntesisBox will be

updated/written from the KNX installation (resulting in a change to the other side of
IntesisBox, BACnet/IP in this case).

• A single KNX group address from which IntesisBox will read the object value on KNX

bus recovery / IntesisBox start-up.

Behavior of IntesisBox’ datapoints with regard to their associated group addresses is
defined by means of flags (R, W, T, U and U2), explained in section 5.1.2.

Additional to the binding aspect commented above, it is also important to notice that each
KNX communication object has a defined EIS type. The EIS type of a communication object
defines the bit length and coding of the data it represents. Communication objects
associated by means of a group address need to match the same EIS type, in order to
communicate consistently.

So, at configuration time it is required that for each datapoint configured on IntesisBox an
EIS type is defined. Datapoints on IntesisBox BACnet support the following EIS-types:

• EIS1 - Switching (1bit raw)

• EIS2 - Dimming (4bit raw)

• EIS5 – Value (16bit – floating type)

• EIS6 – Scaling (8bit – scaled 0%-100% in values 0-255)

• EIS7 – Drive Control (1bit raw)

• EIS8 – Priority (2bit raw)

• EIS9 – IEEE 754 float (32bit – floating type)

• EIS10 – 16bit Counter (16bit raw)

IntesisBox® BACnet/IP Server - KNX

User’s Manual r18 eng

© Intesis Software S.L. - All rights reserved

This information is subject to change without notice

IntesisBox® is a registered trademark of Intesis Software SL

URL
Email
tel

http://www.intesis.com

[e-mail]
[phone]

10 / 31

• EIS11 – 32bit Counter (32bit raw)

• EIS13 – ASCII char (8bit raw)

• EIS14 – 8bit Counter (8bit raw)

ETS3 or ETS4 software tools are not used to configure IntesisBox. Though, it’s typical that
the choice of which KNX group addresses to use is restricted or defined by an ETS-based
project. If that’s the case, the KNX installer/integrator needs to provide the set of group
addresses prior to doing the configuration of datapoints in LinkBoxBacnet.

Also, a dummy ETS application is provided by Intesis Software (section 6), which can be
imported into ETS. This application is nor downloadable into IntesisBox BACnet neither
usable for IntesisBox configuration. Rather, it poses as a means of having a device in the
ETS project representing the IntesisBox BACnet and its own datapoints/communication
objects, and to which group addresses are associated.