Vimar 01548 Guida utente

BUILDING AUTOMATION WELL-CONTACT PLUS

Installer manual

01548

KNX IP media coupler

Contents

1. Product Description ............................................................................................................. 4

1.1 Front Panel ................................................................................................................. 4

1.2 LED Indication ............................................................................................................... 5

1.3 LED Indication of Special Functions............................................................................................... 6

1.4 Commissioning .............................................................................................................. 7

1.5 Secure Commissioning ........................................................................................................ 8

1.6 Important Notes ............................................................................................................. 8

1.6.1 Installation and Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.6.2 Mounting and Safety ............................................................................................................. 8

1.6.3 Maintenance.................................................................................................................... 8

1.7 Safekeeping of Device Certiﬁcate................................................................................................. 9

1.8 Feature Summary ............................................................................................................ 9

2. KNXnet/IP ..................................................................................................................... 10

2.1 IP (Secure) Tunneling .......................................................................................................... 10

2.2 IP (Secure) Routing ........................................................................................................... 10

2.3 IP Firmware Update........................................................................................................... 10

3. KNX Secure ................................................................................................................... 10

4. Operational Description .......................................................................................................... 11

4.1 IP Secure Router Application .................................................................................................... 11

4.2 IP Network ................................................................................................................. 11

4.3 KNX Network Installation ...................................................................................................... 12

4.4 Adding Device Certiﬁcate....................................................................................................... 13

4.5 Programming................................................................................................................ 14

4.5.1 Programming of Individual Address (and Application) ..................................................................................... 14

4.5.2 IP Conﬁguration ................................................................................................................. 15

4.6 Special Functions ............................................................................................................ 16

4.6.1 Manual Function ................................................................................................................ 16

4.6.2 Factory Reset ................................................................................................................... 16

4.6.3 IP Firmware Update Request ....................................................................................................... 17

5. ETS Database.................................................................................................................. 18

5.1 General .................................................................................................................... 18

5.2 Main Line (IP) ................................................................................................................ 19

5.3 Subline (KNX TP) ............................................................................................................ 20

5.4 IP (Secure) Tunneling Address Assignment ......................................................................................... 21

6. Web Front-end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6.1 Protection of the 01548 Web Front-end............................................................................................ 22

6.2 Accessing the 01548 Web Front-end ............................................................................................. 22

6.2.1 via Windows Explorer ............................................................................................................ 22

6.2.2 via IP Address .................................................................................................................. 23

6.2.3 via MAC Address ................................................................................................................ 23

6.3 Device Info.................................................................................................................. 23

6.4 KNX....................................................................................................................... 24

6.5 IP Firmware Update........................................................................................................... 24

7. Glossary ...................................................................................................................... 26

8. Technical...................................................................................................................... 27

8.1 State of Delivery.............................................................................................................. 27

8.2 Datasheet .................................................................................................................. 28

9. FAQ .......................................................................................................................... 29

1. Product Description

The basic function of the 01548 router is to ensure KNX IP/Ethernet devices (main line) interact with KNX TP bus devices (secondary line). It is powered by the TP bus and

does not require an external power supply. The router is designed to route traffic based on the type of installation in the bus system hierarchy and according to the filter tables

incorporated for communication towards groups. The secondary line configuration can be deactivated. When used as an interface, the device has configuration, commis-

sioning, display, protocol and diagnostics functions. The operating and filter statuses, the faults and the communication errors are indicated via LEDs. The device supports

messages with up to 240 bytes APDU length and it features the “Function” button to deactivate the filter temporarily during commissioning or troubleshooting.

The device is for KNXnet/IP (Secure) Routing and Tunnelling and it is equipped with a dedicated QR code to be used with ETS (version 5.5 and later) during configuration.

The Secure Tunnelling, Secure Commissioning and IP Backbone Protection can be activated.

The 01548 router is displayed on the network; the device settings can be set, the functions activated and the 60-minute busload history can be displayed via web. Moreover,

the “bootloader” function enables the remote updating of the firmware via IP/Ethernet.

1.1 Front Panel

01548

State

Traffic

Function

IP TP

GA PA

ROUTER IP KNX

Program

Figure 1: Front View

Table 1: Front Panel Elements

LEDs Buttons / Connectors

1State IP (Main line) AEthernet Connector

2Bus State KNX TP (Subline) BFunction Button

3Telegram Trafﬁc IP (Main line) CProgramming Button

4Telegram Trafﬁc KNX TP (Subline) DKNX TP Connector

5Group Address Routing*

6Individual (Physical) Address Routing

7Programming LED

* only group telegrams with main groups 0…13

Product Description

1.2 LED Indication

Following overview table gives a description of the LED display during normal operation. The display during an active special function is described in next chapter.

Table 2: Normal LED Display

Number

LED Color

Explanation / Range

State IP (Main line)

green IP line OK (connection established)

orange Manual Function active

< off > No IP connection

2 Bus State KNX TP (Subline) green Subline OK

< off > Subline not connected

3 Telegram Trafﬁc IP (Main line) blinking green Telegram trafﬁc extent indicated by blinking

< off > No telegram trafﬁc

4 Telegram Trafﬁc KNX TP (Subline)

blinking green Telegram trafﬁc extent indicated by blinking

blinking red Transmission error (BUSY, NACK, missing IACK)

< off > No telegram trafﬁc

5 Group Address Routing

green Filter table active

orange Route all

red Block all

< off > Routing of Group Telegrams is different on main line and subline

6 Individual (Physical) Address Routing*

green Filtering active

orange Route all

red Block all

< off > Routing of Physical telegrams is different on main line and subline

7 Programming LED

red Programming Mode active

blinking red No IP connection

< off > Programming Mode not active

* behavior is not deﬁned for routers having an invalid conﬁguration i.e. Individual Address

Product Description

1.3 LED Indication of Special Functions

Only LEDs described here are lighting during an active special function. Other LEDs are off.

Table 3: LED Status Display for Manual Function

Number

LED Color

Comment

State IP orange Lights red if not connected

01548

Traffic

Function

IP TP

ROUTER IP KNX

Program

State

GA PA

1 2

5 6

2 Bus State KNX TP green

5 Group Address Routing green: ﬁlter

orange: route all

red: block all

6 Individual Address Routing

Table 4: LED Status Display for Factory Reset after ﬁrst Function Button Press

Number

LED Color

Comment

State IP orange Lights red if not connected

01548

Traffic

Function

IP TP

ROUTER IP KNX

Program

State

GA PA

1 2

5 6

2 Bus State KNX TP orange

5 Group Address Routing green: ﬁlter

orange: route all

red: block all

6 Individual Address Routing

Table 5: LED Status Display for Firmware Update

Number

LED Color

Comment

State IP green blinking, later lighting

01548

Function

IP TP

GA PA

ROUTER IP KNX

State

Traffic

Program

1 2

2 Bus State KNX TP blinking green

3 Telegram Trafﬁc IP green

7 Programming LED red

Product Description

1.4 Commissioning

Please note for commissioning with default settings:

• All telegrams are blocked because the ﬁlter table is not deﬁned

• The Manual Function switch-off time is 120 min

• Individual Address is 15.15.0

• Activation of Security and Secure Commissioning require the Device Certiﬁcate

• Activation of Security requires a minimum ETS version

Art. 01548 X

Serial number:

0044270

MAC address:

0072031B45CB

D0 76 50 00 57 EC

Art. 01548

0072031B45CB

Device certificate:

ABZAGG-2BZKDF

54SHGN-OIPIXZ

RRPF6Z-A5GESR

01548

State

Traffic

Function

IP TP

GA PA

ROUTER IP KNX

Program

KNX TP

Ethernet

Figure 2: Connection Scheme

To start a secure conﬁguration download, Secure Commissioning must be activated in the ETS project before. Without activation, 01548 will behave like 01547.1

(without support of KNX Secure).

Please also read chapter “1.6 Important Notes” before putting the device into operation.

Product Description

1.5 Secure Commissioning

Before the secure download of conﬁguration setting and/or Individual Address can start, the individual Device Certiﬁcate of 01548 must have been added to the ETS

project. To add it, the ETS project must be password-protected.

A Secure download is only possible after activation of Secure Commissioning.

Activation of Secure Commissioning demands the individual Device Certiﬁcate.

Device Certiﬁcates can only be added to an ETS project when it is password-protected.

When no project password is set, Secure Commissioning cannot be activated. ETS projects with having Secure Commissioning and/or Security set to active always

require pre-setting a project password. Having no project password set on activation of Security, the ETS then asks to type it in.

Figure 3: Set Project Password

The individual Device Certiﬁcate always is enclosed with the KNX Secure product. To keep the product conﬁgurable by the user, it is important to make sure the

Device Certiﬁcate cannot be lost (please note chapter 1.7 Safekeeping of Device Certiﬁcate).

1.6 Important Notes

It is recommended to participate the standardized courses of a KNX-certiﬁed training center before installing, programming, and commissioning a KNX system. Here,

the participant gains the necessary knowledge and skills, also required for troubleshooting, by practical exercises.

Please read this chapter carefully before ﬁrst use and installation:

1.6.1 Installation and Commissioning

• In the case of damage (at storage, transport) no repairs may be carried out by unauthorized persons

• After connection to the KNX bus system, the device works with its default settings

•Warning: Do not connect to 230 V. The device is supplied by the KNX bus and does not require any additional external power supply

• The device may only be installed and put into operation by a qualiﬁed electrician or authorized person

• For planning and construction of electric installations the appropriate speciﬁcations, guidelines and regulations in force of the respective country have to be

complied

• For conﬁguring, use the ETS (or ETS Inside)

1.6.2 Mounting and Safety

• For mounting use an appropriate equipment according to IEC60715

• Installation on a 35 mm DIN rail (TH35)

• Connect the KNX bus line as for common KNX bus connections with a KNX bus cable, to be stripped and plugged into a KNX TP connector

• Do not damage electrical insulations during connecting

• Installation only in dry locations

1.6.3 Maintenance

• Accessibility of the device for operation and visual inspection must be provided

• The housing must not be opened

• Protect the device from moisture, dirt and damage

• The device needs no maintenance

• If necessary, the device can be cleaned with a dry cloth

Product Description

1.7 Safekeeping of Device Certiﬁcate

The Device Certiﬁcate can be found on a label that is adhered on side of the housing. To avoid unwanted access, the Device Certiﬁcate has to be removed from the

device after commissioning. Therefore, the label consists of two parts, one ﬁxed part that must remain on the housing (for identiﬁcation) and one tear-off part that can

be removed (for keeping at a safe place).

Art. 01548 X

Serial number:

0044270

MAC address:

0072031B45CB

D0 76 50 00 57 EC

Art. 01548

0072031B45CB

Device certificate:

ABZAGG-2BZKDF

54SHGN-OIPIXZ

RRPF6Z-A5GESR

tear-off part

Figure 4: Device Certiﬁcate Label

After the Device Certiﬁcate was added to the Device Certiﬁcate list in ETS, the tear-off part of the Device Certiﬁcate label can be archived at a safe place. The Device

Certiﬁcate list only needs to contain the certiﬁcates of the KNX Secure devices that are used within the ETS project. ETS then automatically uses the correct certiﬁcates

for programming the relevant devices.

For clear identiﬁcation of the device after removing the tear-off part, the serial number is printed on both label parts, on the one that was removed and the ﬁxed one that

stays on the housing.

When the tear-off part that contains the Device Certiﬁcate is lost, only the password-protected ETS project contains the Device Certiﬁcate.

Be aware, when the Device Certiﬁcate is completely lost, meaning the tear-off part is unavailable and the project password is lost, too, the device cannot be used in

Secure mode (Security cannot be activated) anymore! From then, also after carrying out a Factory Reset, the device can only be used unsecured, as “plain” device.

1.8 Feature Summary

• Device Certiﬁcates guarantee only authorized persons can have access to 01548.

• When the ETS “Secure Commissioning” function is activated, conﬁguration data is downloaded only in encrypted KNX Data Secure format.

• Activation of “IP Backbone Security” for protection of IP routing.

• When additional protection becomes necessary (for example, the subline is located outside the building), conﬁguring 01548 from the subline can totally be switched off.

• 01548 supports long telegrams with up to 240 bytes APDU length. (Devices of both product series, the MEC couplers and UIM interfaces, can process long messages

e.g. for energy metering applications and visualization purposes.)

• 01548 favorably replaces a common TP line/area coupler. The great advantage is using KNX IP as a fast KNX backbone medium.

• 01548 works without external power supply.

• For IP (Secure) Tunneling, four tunneling connections can be realized in parallel. On activation of Secure Tunneling, the password protection becomes available.

• Settings to increase the data throughput / decrease a high bus trafﬁc are featured.

• IACK sending on sent out messages is conﬁgurable.

• Repetition is conﬁgurable for both Physical Telegrams and Group Telegrams.

• Telegram ﬁltering can be temporary suspended by only pressing the Function button. Filtering then is limited to ease commissioning, troubleshooting or fast on-site

diagnostics and access to other lines becomes possible without additional ETS download.

• Automatic switch back to run-time telegram ﬁltering after expiry of the conﬁgurable suspension period (see Manual Mode). This avoids forgetting to reactivate ﬁltering.

• UPnP Discovery enables discovering 01548 within the IP network.

• ETS recognizes 01548 as bus connection interface by KNXnet/IP Search Request.

• Updating the ﬁrmware can easily be accomplished by a web browser.

• The available web front-end provides informative settings and enables to remotely switch the device into Programming Mode without using the Programming Button.

• With the web front-end, a diagram of a 60 min busload history can be watched.

• When Security is active, the web front-end can also be used limited or fully disabled.

• 01548 supports KNXnet/IP, ARP, ICMP, IGMP, HTTP, UPnP discovery, UDP/IP, TCP/IP, DHCP and AutoIP.

Product Description

2. KNXnet/IP

The presence of the Internet Protocol (IP) has led to the definition of the KNXnet/IP protocol. As documented in the KNXnet/IP protocol specifications, KNX telegrams can

be transmitted encapsulated in IP packets. Ethernet networks can be used to route and tunnel KNX telegrams.

KNX IP routers are highly similar to TP line couplers. Only difference is they use the IP communication medium instead of TP and the KNXnet/IP communication protocol.

According to this, IP interfaces and IP routers are an excellent alternative to USB data interfaces and TP line/area couplers. A TP backbone can be completely be replaced

by a fast Ethernet based IP Backbone line. KNX end devices can be integrated directly via IP. This makes the Ethernet a real KNX medium.

2.1 IP (Secure) Tunneling

KNXnet/IP offers the possibility for point-to-point connections for the ETS (IP Tunneling connections) or, for example, between supervisory system and KNX installation.

On activation of “Secure Tunneling”, these connections become IP Secure Tunneling connections. They are protected by encryption and usage of extra passwords.

2.2 IP (Secure) Routing

IP Routing is the KNXnet/IP protocol for interconnecting KNX lines and areas by IP networks. Hereby, the KNXnet/IP protocol deﬁnes the KNX IP communication. Using

IP Secure Routing means runtime communication on KNX IP is entirely encrypted according to the KNX IP Secure mechanism.

2.3 IP Firmware Update

The IP bootloader function makes it possible to remotely carry out Firmware Updates and rewrite the ﬂash memory content via an IP connection. This is not just a simple

application download. Both communication stack and application software are downloaded.

The Firmware Update procedure via IP can be executed by 01548´s web front-end, which is independent from ETS, and makes use of special messages to speed up

the process. To be protected, this process makes use of a special encryption.

3. KNX Secure

The KNX Secure technology adds extra security to a KNX installation, during commissioning as well as for KNX installations at runtime. Difference between normal KNX

devices and KNX Secure devices is KNX Secure devices have the ability to encrypt and decrypt telegrams.

Every KNX Secure device supports a secure mode. Only when this secure mode is activated, the KNX Secure device will be able to encrypt/decrypt telegrams. For activation,

device certificates are necessary (see chapter 1.5 Secure Commissioning).

KNX telegrams encrypted by KNX Secure devices are called KNX Secure telegrams. Regarding both KNX Security mechanisms, KNX IP Secure and KNX Data Secure, two

types of encryption can be distinguished:

• KNX IP Secure can only be applied upon the KNX IP medium. KNX telegrams are sent as encrypted IP Secure frames, also called entirely encrypted telegrams (no matter

if KNX Data Secure is used or not).

• KNX Data Secure can be applied on any KNX communication medium. End-to-end communication between end devices is encrypted. Due to an individual security key,

end devices encrypt/decrypt parts of their telegrams. Then, only devices having identical Group Addresses can encrypt/decrypt the telegrams.

For programming a KNX Secure device, ETS must know both its factory key (FDSK) and its serial number. But it is not necessary entering factory key or serial number. The

ETS generates this information from the Device Certificate.

A Device Certificate is a device-specific 32-character code which contains serial number and FDSK (Factory Default Setup Key). Serial number and FDSK cannot be modified.

ETS retrieves the FDSK via the device certificate (see chapter 1.5 Secure Commissioning).

After a KNX Secure device has been added to an ETS project and after its Device Certificate has been added too, ETS automatically sets the Tool Key for the project. This