Vimar 01548 User guide

BUILDING AUTOMATION WELL-CONTACT PLUS
Installer manual
01548
KNX IP media coupler

2

3
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 Certificate................................................................................................. 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 Certificate....................................................................................................... 13
4.5 Programming................................................................................................................ 14
4.5.1 Programming of Individual Address (and Application) ..................................................................................... 14
4.5.2 IP Configuration ................................................................................................................. 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

4
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
2
A
4
6
D
1
3
5
7C
B
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 Traffic IP (Main line) CProgramming Button
4Telegram Traffic 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

5
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
1 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 Traffic IP (Main line) blinking green Telegram traffic extent indicated by blinking
< off > No telegram traffic
4 Telegram Traffic KNX TP (Subline)
blinking green Telegram traffic extent indicated by blinking
blinking red Transmission error (BUSY, NACK, missing IACK)
< off > No telegram traffic
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 defined for routers having an invalid configuration i.e. Individual Address
Product Description

6
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
1 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: filter
orange: route all
red: block all
6 Individual Address Routing
Table 4: LED Status Display for Factory Reset after first Function Button Press
Number LED Color Comment
1 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: filter
orange: route all
red: block all
6 Individual Address Routing
Table 5: LED Status Display for Firmware Update
Number LED Color Comment
1 State IP green blinking, later lighting
01548
Function
IP TP
GA PA
ROUTER IP KNX
State
Traffic
Program
1 2
3
7
2 Bus State KNX TP blinking green
3 Telegram Traffic IP green
7 Programming LED red
Product Description

7
1.4 Commissioning
Please note for commissioning with default settings:
• All telegrams are blocked because the filter table is not defined
• The Manual Function switch-off time is 120 min
• Individual Address is 15.15.0
• Activation of Security and Secure Commissioning require the Device Certificate
• 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 configuration 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

8
1.5 Secure Commissioning
Before the secure download of configuration setting and/or Individual Address can start, the individual Device Certificate 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 Certificate.
Device Certificates 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 Certificate always is enclosed with the KNX Secure product. To keep the product configurable by the user, it is important to make sure the
Device Certificate cannot be lost (please note chapter 1.7 Safekeeping of Device Certificate).
1.6 Important Notes
It is recommended to participate the standardized courses of a KNX-certified 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 first 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 qualified electrician or authorized person
• For planning and construction of electric installations the appropriate specifications, guidelines and regulations in force of the respective country have to be
complied
• For configuring, 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

9
1.7 Safekeeping of Device Certificate
The Device Certificate can be found on a label that is adhered on side of the housing. To avoid unwanted access, the Device Certificate has to be removed from the
device after commissioning. Therefore, the label consists of two parts, one fixed part that must remain on the housing (for identification) 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 Certificate Label
After the Device Certificate was added to the Device Certificate list in ETS, the tear-off part of the Device Certificate label can be archived at a safe place. The Device
Certificate list only needs to contain the certificates of the KNX Secure devices that are used within the ETS project. ETS then automatically uses the correct certificates
for programming the relevant devices.
For clear identification 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 fixed one that
stays on the housing.
When the tear-off part that contains the Device Certificate is lost, only the password-protected ETS project contains the Device Certificate.
Be aware, when the Device Certificate 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 Certificates guarantee only authorized persons can have access to 01548.
• When the ETS “Secure Commissioning” function is activated, configuration 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), configuring 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 traffic are featured.
• IACK sending on sent out messages is configurable.
• Repetition is configurable for both Physical Telegrams and Group Telegrams.
• Telegram filtering 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 filtering after expiry of the configurable suspension period (see Manual Mode). This avoids forgetting to reactivate filtering.
• UPnP Discovery enables discovering 01548 within the IP network.
• ETS recognizes 01548 as bus connection interface by KNXnet/IP Search Request.
• Updating the firmware 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

10
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 defines 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 flash 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
Tool Key cannot be modified. It can only be reset to its FDSK by a Factory Reset (see chapter 4.6.2 Factory Reset).
Mixing unsecure and secure communication on the same Group Address is impossible.
A mix of KNX IP Secure couplers in secure mode with KNX IP Secure devices in plain mode, or simply plain KNX IP devices, does not work.
KNXnet/IP - KNX Secure

11
4. Operational Description
In KNX network installations, 01548 is used as KNX IP line/area coupler to couple KNX IP and KNX TP (see also chapter 2.2 IP (Secure) Routing). It can be used in the com-
mon way without activation of Security and in ETS projects where Security is set to active. After connecting to KNX TP, 01548 operates with its default settings. Setting a
correct Individual Address is necessary. Only Individual Addresses x.y.0 are allowed.
4.1 IP Secure Router Application
When 01548 receives telegrams (for example during commissioning) that use Individual Addresses as destination addresses, it compares the Individual Addresses of
the receiver with its own Individual Address and decides on that whether it has to route the telegrams or not.
When 01548 receives telegrams that use group addresses as destination addresses, it reacts in accordance with the parameter settings. During normal operation (with
Group Telegram routing set to filter), 01548 only routes the telegrams whose group addresses are entered in the group filter table.
If a telegram is routed by 01548 without receiving the corresponding acknowledgement, i.e. due to a missing receiver or to a transmission error, the telegram will be
repeated up to three times (depending on the ETS setting). With the parameters „Repetitions if errors ...“, this function can be configured separately for each line and
both kinds of telegrams. It is recommended to use the default parameter setting.
IP Router is designed for use in 10/100 BaseT networks compliant to IEEE802.3. The AutoSensing function sets the baud rate (10 Mbit or 100 Mbit) automatically. IP
address can be received from a DHCP server. For this, the automatic assignment setting of the IP address can be set by ETS (“obtain an IP address automatically”). If
set so and no DHCP server is found, 01548 starts an AutoIP procedure and autonomously assigns the IP address. If 01548 is supposed to have a fixed IP address (as
well as subnet mask and standard gateway) it can be set by ETS.
4.2 IP Network
01548 sends telegrams from/to the TP network to/from the IP network in accordance with the KNXnet/IP protocol specification. According to the default setting, IP
telegrams are sent as IP Multicast to the IP address 224.0.23.12 port 3671. The Multicast IP address 224.0.23.12 is the defined address for KNXnet/IP by KNX Associa-
tion in conjunction with the IANA. It is recommended to change this address only when it becomes necessary due to the existing network.
Important notes:
• All KNX IP devices that are intended to communicate with each other via IP must have the same IP multicast address.
• Multicast IP address 224.0.23.12 may need to be changed in respect of the network type and of the network components´ settings.
• IGMP (Internet Group Management Protocol) is used for IP Routing and Discovery.
• If problems occur for IP address assignment, please ask your network administrator.
• According to the topology, Individual Addresses that are used for Tunneling channels always have to be assigned in the range of subline addresses. Detailed informa-
tion about additional Individual Addresses for (Secure) Tunneling can be found in chapter 5.4 IP (Secure) Tunneling Address Assignment.
Operational Description

12
Operational Description
4.3 KNX Network Installation
Up to 15 areas and 225 different addresses for line couplers can be defined. For line coupler functionality in a KNX network, 01548 has to use the correct Individual
Address of a line coupler (x.y.0). For backbone coupler functionality in a KNX network, 01548 has to use the correct Individual Address of an area coupler (x.0.0).
It is recommended to make sure the factory default Individual Address 15.15.0 is not used in the installation network.
Defining a correct topology is absolutely mandatory to guarantee proper functioning of an installation.
In a KNX system with 01548 backbone couplers and 01504.2 line couplers, it is necessary to ensure that 01548 has an address assigned from a free addressing area.
Following figure illustrates a possible topology scenario.
01504.2
Bus State
Traffic
Function
LINE COUPLER
Main Sub
GA PA
Sub
Main
1.1.0
01504.2
Bus State
Traffic
Function
LINE COUPLER
Main Sub
GA PA
Sub
Main
1.2.0
01548
State
Traffic
Function
IP TP
GA PA
ROUTER IP KNX
Program
01548
State
Traffic
Function
IP TP
GA PA
ROUTER IP KNX
Program
01548
State
Traffic
Function
IP TP
GA PA
ROUTER IP KNX
Program
01548
State
Traffic
Function
IP TP
GA PA
ROUTER IP KNX
Program
01548
State
Traffic
Function
IP TP
GA PA
ROUTER IP KNX
Program
1.0.0 2.0.0 3.1.0
01548
State
Traffic
Function
IP TP
GA PA
ROUTER IP KNX
Program
3.2.01.X.0 3.0.0
Main Line
TP Area
TP Area
TP Line
IP Backbone
TP Line TP Line
Subline Subline
Figure 5: 01548 Network Topology
Example:
If a KNX IP router with address 1.0.0 already exists on the backbone no KNX IP router with address 1.x.0 can be added here. Even if no line coupler with address 1.1.0
exists on the subline of the 1.0.0 router. Vice versa, when line couplers with addresses 3.x.0 already exist in an installation, an IP router with address 3.0.0 cannot be
added.

13
Operational Description
4.4 Adding Device Certificate
Every KNX Secure device uses its own Device Certificate. Entering this Device Certificate in ETS is mandatory before activating or using KNX Security functions.
The Device Certificate can be found printed on a side label on the housing.
Device Certificates can be entered manually and by taking a QR code webcam picture.
After opening the project, the Device Certificate list can be edited In the Security tab under Project Overview.
Figure 6: Device Certificate List
If not already having the Device Certificate added to the list, on starting a Secure download following window appears.
Figure 7: Adding Device Certificate

14
Operational Description
4.5 Programming
4.5.1 Programming of Individual Address (and Application)
To download the Individual Address (IA) into the device, Programming Mode must be active. Successive pressing the Programming Button switches Programming
Mode on and off. LED 7 lighting red indicates Programming Mode is set active. On activation of the ETS download and pressing the Programming Button, the
device stores the new Individual Address in its memory. Security settings are actualized via both IA download and application download.
When 01548 is the Current Interface, an application download is necessary for actualizing IP settings of 01548.
For downloading, an interface connection to the KNX bus system is required.
To program devices of a line different to which the device used as ETS Current Interface is connected, a correct topology is mandatory.
The Individual Address can be assigned to the device by setting the desired address in the properties window of the ETS. When the ETS download is complete,
the device restarts itself.
Figure 8: ETS Properties Windowt
The device is supplied with the Individual Address 15.15.0 (Factory Default Setting). It is recommended not to use this address for normal operation of an
installation and to assign a different address when commissioning.
A blinking red Programming LED indicates the Ethernet cable is not properly connected or no IP network connection is available.
ETS database is available at the company website and in the ETS Online Catalog.

15
Operational Description
4.5.2 IP Configuration
The IP configuration of 01548 can be set in the Properties window of the ETS. To activate DHCP/AutoIP, the “Obtain an IP address automatically” option must be
set. For more details and information about configuration of IP networks, please ask your local network administrator.
Figure 9: Automatic IP Address Assignment
When the „Use a static IP address“ option is chosen, IP address, Subnet Mask and Default Gateway can be set manually.
Figure 10: Manual IP Address Assignment
KNX IP devices intended to communicate with each other via the IP (Secure) Routing protocol must use the same Multicast Address.
Changing the Multicast Address can only be done under the IP (configuration) tab in the Backbone´s Properties window. It appears after a click on the blue
Topology bar.

16
Operational Description
When 01548 is used as ETS Current Interface and its IP address is changed by a configuration download, ETS tries to maintain the connection to the Cur-
rent Interface having the previous IP address. 01548 (now containing the actualized IP address) must be selected as Current Interface again from the list of
Discovered Interfaces. Until then, the previous IP Address is still visible in the IP Tunneling window and ETS shows the Current Interface is not reachable.
220
Figure 11: IP Address of the Current Interface before and after Actualization
4.6 Special Functions
The Function Button activates 01548´s special functions. Manual Function and Factory Reset can be activated. Device settings of 01548 can be reset to manufacturer
default values with the Factory Reset function. During the Firmware Update procedure, the Function Button has to be pressed. The status of an active special function
is indicated by the LED display (see chapter “1.3 LED Indication of Special Functions”).
4.6.1 Manual Function
During normal operation, a rather short press (≈ 3 sec) activates and deactivates the Manual Function. LED 5 and LED 6 show the current filtering states.
When the Manual Function is active, either all Physical Telegrams or all Group Telegrams or both can pass the 01548 without filtering. When the Switch-off time
has elapsed, 01548 automatically switches back to normal operation. To configure the Manual Function and set the Switch-off time, use the parameter tab
General like shown in chapter 5.1 General. After switching back from Manual Function to normal operation, the latest downloaded parameter setting / filter table
entries are active again.
Table 6: Activation of Manual Functions
Step Manual Function
1 Hold Function button for 3 seconds
2 LED 1 now is orange indicating Manual Function is on
3 After switch-off, normal operation is indicated by LED 1 lighting green
Actual Previous

17
4.6.2 Factory Reset
A long press (≈ 15 sec) of the Function Button soon followed by a short press (≈ 3 sec) executes the Factory Reset. After the first press, the LED display lights
like described in Table 4: LED Status Display for Factory Reset after first Function Button Press. After the second press, all parameters (incl. Individual Address)
will be set to factory default. When Security is activated, also the Tool Key is set back to its FDSK. Subsequently, LEDs show the normal operation display again.
Table 7: Activation of Factory Reset
Step Factory Reset
1 Hold Function button for 15 seconds
2 LEDs 1/2 now are orange
3 Hold Function button for 3 seconds
4 Device restarts
4.6.3 IP Firmware Update Request
During normal operation, a rather short press (≈ 3 sec) activates and deactivates the Manual Function. LED 5 and LED 6 show the current filtering states.
Figure 12: Authorized Update Request
Table 8: Activation of Firmware Update
Step Firmware Update
1 Short press on Program button
2 Short press on Function button
3 Click on “request update” in the web front-end
4 LED2 is blinking green
5 Firmware file can be selected
6 Device restarts
Operational Description

18
5. ETS Database
5.1 General
Figure 13: General Tab Parameters
Table 9: General Tab Parameter Settings
ETS Parameter Settings [Default Parameter] Comment
Slow tunneling connections support
yes
no
[no]
Enable or disable support of slow tunneling connections.
Manual Function
Manual Function
disabled
pass all telegrams
pass all Physical telegrams
pass all Group telegrams
[pass all telegrams]
Configuration setting for telegram routing when the Manual Fun-
ction is active.
Switch-off time for Manual Function
10 min, 1 hour, 4 hours,
8 hours
[1 hour]
After expiry of this time period the Manual Function is switched off
automatically.
Web front-end
Availability when secure mode is activated
available having full functionality
only status info display
web front-end not available
[web front-end not available]
When Security is switched on, the web front-end can be fully
available (read/write), be available for limited usage (only read) or
be deactivated.
HTTP port
80
8080
[8080]
Select the HTTP port.
ETS Database

19
5.2 Main Line (IP)
Setting “transmit all” is intended only for testing use. Please do not use for normal operation.
Figure 14: Main Line (IP) Tab Parameters
Table 10: Main Line (IP) Tab Parameter Settings
ETS Parameter Settings [Default Parameter] Comment
Telegram routing
(Main line -> Subline)
Group: filter, Physical: block
Group and Physical: filter
Group: route, Physical: filter
Group and Physical: route configure
[Group and Physical: filter]
Routing of Physical Telegrams and Group Telegrams can be set to
‘block’ (no routing), ‘filter’ (telegrams are routed according to filte-
ring) and ‘route’ (all telegrams are transmitted). To set parameters
different as available here, use ‘configure’.
Group telegrams:
Main group 0…13
transmit all (not recommended)
block
filter
[filter]
Filtering of Group telegrams (with main groups 0…13) can be
configured to route all telegrams, no telegrams, or only telegrams
entered in the filter table.
Group telegrams:
Main group 14…31
transmit all (not recommended)
block
filter
[filter]
Filtering of Group telegrams (with main groups 14…31) can be
configured to route all telegrams, no telegrams, or only telegrams
entered in the filter table.
Physical telegrams
transmit all (not recommended)
block
filter
[filter]
Filtering of Physical telegrams can be configured to route all
telegrams, no telegrams, or only telegrams depending on their
Individual Address.
ETS Database

20
5.3 Subline (KNX TP)
Setting “transmit all” is intended only for testing use. Please do not use for normal operation.
If the parameter “Send confirmation on own telegrams” is set to “yes”, 01548 systematically sends an ACK on any own routed telegram. For example, since
repeaters do not use filter tables, it is useful to have an ACK sent along with routed telegrams.
Figure 15: Subline (KNX TP) Tab Parameters
Table 11: Subline (KNX TP) Tab Parameter Settings
ETS Parameter Settings [Default Parameter] Comment
Telegram routing
(Subline -> Main line)
Group: filter, Physical: block
Group and Physical: filter
Group: route, Physical: filter
Group and Physical: route configure
[Group and Physical: filter]
Routing of Physical Telegrams and Group Telegrams can be set to
‘block’ (no routing), ‘filter’ (telegrams are routed according to filte-
ring) and ‘route’ (all telegrams are transmitted). To set parameters
different as available here, use ‘configure’.
Group telegrams: Main group 0…13
transmit all (not recommended)
block
filter
[filter]
Filtering of Group telegrams (with main groups 0…13) can be
configured to route all telegrams, no telegrams, or only telegrams
entered in the filter table.
Group telegrams: Main group 14…31
transmit all (not recommended)
block
filter
[filter]
Filtering of Group telegrams (with main groups 14…31) can be
configured to route all telegrams, no telegrams, or only telegrams
entered in the filter table.
Physical telegrams
transmit all (not recommended)
block
filter
[filter]
Filtering of Physical telegrams can be configured to route all
telegrams, no telegrams, or only telegrams depending on their
Individual Address.
Physical telegrams:
Repetition if errors
on subline
no
up to 3 repetitions
one repetition
[up to 3 repetitions]
After subline transmission error (e.g. due to missing receiver)
Physical telegrams can be not repeated, be repeated only once,
or be repeated for max. 3 times.
Group telegrams:
Repetition if errors
on subline
no
up to 3 repetitions
one repetition
[up to 3 repetitions]
After subline transmission error (e.g. due to missing receiver)
Group telegrams can be not repeated, be repeated only once, or
be repeated for max. 3 times.
Telegram confirmation on subline
if routed
always
[if routed]
Either only routed telegrams to IP main line are confirmed by an
ACK on the subline or each telegram on the subline is confirmed
by an ACK.
Send confirmation on own telegrams
yes
no
[no]
Telegrams sent out to the subline can be confirmed by an added
ACK.
Configuration from subline (KNX TP)
allow
block
[allow]
If blocked 01548 can only be configured via the main line.
ETS Database