Vimar 01507 User guide

Installer manual
BUILDING AUTOMATION WELL-CONTACT PLUS
01507
By-me KNX router

2
BUILDING AUTOMATION

3
BUILDING AUTOMATION
Index
1. System requirements ............................................................................................................ 4
2. Product description ............................................................................................................. 4
2.1 Front view of the device........................................................................................................ 4
2.2 LED indications .............................................................................................................. 4
2.3 Commissioning .............................................................................................................. 5
2.4 Secure Commissioning ........................................................................................................ 5
2.5 Important notes .............................................................................................................. 6
2.6 Keeping the device Certificate ................................................................................................... 7
2.7 Summary of functions ......................................................................................................... 7
3. KNXnet/IP ..................................................................................................................... 7
3.1 Updating the IP firmware ....................................................................................................... 7
4. The KNX Secure protocol ........................................................................................................ 8
5. Description of operation ......................................................................................................... 10
5.1 General information ........................................................................................................... 10
5.2 IP network .................................................................................................................. 10
5.3 Message flow example ........................................................................................................ 10
5.4 Adding the device Certificate .................................................................................................... 11
5.5 Programming................................................................................................................ 12
5.5.1 Programming the individual address (and application)..................................................................................... 12
5.5.2 Network backbone configuration with KNX Secure active.................................................................................. 13
5.5.3 01548 interface configuration ....................................................................................................... 13
5.5.4 IP configuration ................................................................................................................. 14
6. Organising the DCA for customising associations ..................................................................................... 15
6.1 Controls.................................................................................................................... 15
6.2 Section A................................................................................................................... 15
6.3 Section B................................................................................................................... 15
6.4 Tab ....................................................................................................................... 16
6.5 Preliminary procedures on the By-me Plus system ................................................................................... 16
6.6 Configured By-me Plus system .................................................................................................. 16
6.7 Adding a communication object from By-me Plus data ................................................................................ 16
6.8 Non-configured By-me Plus system............................................................................................... 17
6.9 KNX Communication objects present in the By-me Plus island .......................................................................... 17
6.10Assigning By-me data to Communication Objects.................................................................................... 18
6.11Copying Communication Objects ................................................................................................ 18
6.12 Errors ..................................................................................................................... 18
6.13 Copying the By-me/KNX gateway from ETS........................................................................................ 19
6.14Completing the ETS configuration ................................................................................................ 19
6.15 Cloning a room/area.......................................................................................................... 20
7. Front-end Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.1 Protecting the front-end Web of 01507 ............................................................................................ 21
7.2 Accessing the front-end Web of 01507 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.2.1 With the MAC address ............................................................................................................ 21
7.3 Information about the device .................................................................................................... 22
7.4 KNX....................................................................................................................... 22
7.5 Special functions ............................................................................................................. 23
7.5.1 IP firmware update request......................................................................................................... 23
7.5.2 Updating the IP firmware .......................................................................................................... 24
7.5.3 Resetting the device .............................................................................................................. 24
8. Usage examples ................................................................................................................. 25

4
BUILDING AUTOMATION
1. System Requirements
To create the network system, make sure all the devices (switch, router, firewall, etc.) are configured in such a way as to allow the passage of multicast messages the device
sends on IP. We recommend you involve an IT manager to make sure the KNX/By-me system can operate in the IP solution of the connections.
2. Product description
The By-me/KNX router enables communication between parts of a system comprising By-me devices, grouped together within an “island”, with a system comprising KNX
devices. The messages are transmitted in both directions according to criteria which define the correspondence of the communication objects belonging to the specific
domains. The router allows up to 500 routing rules. Each rule is specified by the By-me group address, by the KNX address, by the direction of communication (from KNX
to By-me; from By-me to KNX; both) and by the type of information exchanged (1 bit, 2 bit, …).
The device is equipped with a TP terminal for connection to the By-me BUS, an Ethernet connector and a front push button for configuration via ETS. The power supply is
provided by the By-me BUS.
Router 01507 conforms to the KNX Secure requirements on the datapoints defined in the routing table. A datapoint on the KNX side can be defined for the heartbeat signal.
2.1 Front view of the device
A: Ethernet KNX over IP line connector
B: Ethernet KNX over IP line status LED
C: By-me BUS line status LED
D: Traffic on Ethernet KNX over IP line LED
E: Traffic on By-me BUS line LED
F: GA LED
G: PA LED
H: Reset push button
I: Configuration LED
L: Configuration push button
M: By-ME BUS line
C
B
D
F
E
G
H
I L M
01507
ROUTER IP KNX
IP
State
Traffic
Program
GA
BUS
PA
STP
X
TP
IP
A
2.2 LED indications
System Requirements - Product description
Green Red
Ethernet KNX over IP line status LED (B)ON: Correct operation ON: Device factory reset
By-me BUS line status LED (C)
Ethernet KNX over IP line traffic LED (D)ON: Data traffic presence -
Traffic on By-me BUS line LED (E)
GA LED (F)
-ON: Device not configured
PA LED (G)
Configuration LED (I) - ON: Device in the configuration phase

5
BUILDING AUTOMATION
2.3 Commissioning
For commissioning with the default settings, keep the following in mind:
• The individual address is 15.15.255
• To activate the security function and Secure Commissioning you will need the device Certificate
• Security function activation requires a specific minimum ETS version number
Art. 01507 X
Serial number:
0044270
MAC address:
0072031B45CB
D0 76 50 00 57 EC
Art. 01507
0072031B45CB
Device certicate:
ABZAGG-2BZKDF
54SHGN-OIPIXZ
RRPF6Z-A5GESR
BUS TP
Ethernet
01507
ROUTER IP KNX
IP
State
Traffic
Program
GA
BUS
PA
STP
X
TP
IP
To launch a secure configuration download, you first need to activate the Secure Commissioning in the ETS project.
Also read chapter “2.5 Important notes” before operating the device.
2.4 Secure Commissioning
To launch the secure download of the configuration settings and/or individual address, you first need to add the individual Certificate of device 01507 to the ETS project.
To add it, the ETS project must be password-protected.
Secure download is only possible after Secure Commissioning has been activated.
To activate Secure Commissioning you will need the individual Certificate of the device.
Device certificates can only be added to a password-protected ETS project.
If a password has not been set for the project, Secure Commissioning cannot be activated. ETS projects with Secure Commissioning and/or the Security function set to
active always require a project password. If no project password proves to be set when the Security function is activated, ETS prompts you to enter one.
Product description

6
BUILDING AUTOMATION
The individual Certificate of the device is always included with the KNX Secure product. For the product to be configured by the user, make sure you do not lose
the device Certificate (see chapter 2.6 Keeping the device Certificate).
2.5 Important notes
We recommend you attend standardised courses at a certified KNX training centre before installing, programming and commissioning a KNX system. The participant
will gain the necessary expertise and knowledge also for troubleshooting, thanks to practical exercises.
Read this chapter thoroughly before first use and installation:
2.5.1 Installation and commissioning
• If the device is damaged during storage or transport, repairs must only be carried out by authorised personnel.
• Once connected to the By-me bus system, the device works with its default settings.
• Warning: do not connect to a 230 V mains power supply. The device is powered by the By-me bus and does not require any additional external power
supply.
• The device must be installed and commissioned solely by a qualified electrician or an authorised person.
• For the design and creation of electrical systems, abide by the specifications, guidelines and applicable local regulations in force.
• For configuration, use ETS (or ETS Inside)
2.5.2 Assembly and safety
• For assembly, use appropriate equipment, in compliance with IEC60715.
• Installation on 35 mm DIN rail (TH35)
• Do not damage the electrical insulation while making the connections.
• Only install in a dry place.
2.5.3 Maintenance
• Guarantee accessibility to the device for operation and visual inspection.
• Do not open the external casing.
• Protect the device against moisture, dirt and damage.
• The device does not require any maintenance.
• If necessary, you can clean it with a dry cloth.
Product description

7
BUILDING AUTOMATION
2.6 Keeping the device Certificate
The device Certificate is on the label affixed to the side of the casing. To avoid unauthorised access, the device Certificate should be removed from the device once it
has been commissioned. To this end, the label is divided into two parts, one fixed part which remains affixed to the casing (for identification), and the other removable
part (to be kept).
Art. 01507 X
Serial number:
0044270
MAC address:
0072031B45CB
D0 76 50 00 57 EC
Art. 01507
0072031B45CB
Device certificate:
ABZAGG-2BZKDF
54SHGN-OIPIXZ
RRPF6Z-A5GESR
part to detach
After adding the device Certificate to the dedicated list in ETS, keep the removed part of the label in a safe place. The list of device Certificates must only include certifi-
cates of KNX Secure devices used for ETS projects. ETS will automatically use the correct certificates for device programming.
To identify the device clearly after the detachable part has been removed, the serial number is printed on both parts of the label, the one you have removed and the one
that remains on the casing.
If you lose the removed part with the device Certificate, it will only be available in the password-protected ETS project.
Caution! If the device Certificate is lost and cannot be retrieved, in other words if the part of the label removed can no longer be found and the project password has
also been lost, the device can no longer be used securely (the Security function will no longer be available for activation). If this is the case, even after performing a
factory reset, the device may only be used in the non-protected mode, like a “normal” device.
2.7 Summary of functions
• The device Certificate guarantees that only authorised persons may access device 01507.
• When the ETS “Secure Commissioning” function is active, the configuration data are only downloaded in encrypted KNX Data Secure format.
• The device is powered by the By-me bus.
• The firmware can easily be updated from a web browser.
•Router 01507 supports KNXnet/IP, ARP, ICMP, IGMP, HTTP, UPnP discovery, UDP/IP, TCP/IP, DHCP and AutoIP.
3. KNXnet/IP
The presence of the Internet protocol (IP) has made the definition of the KNXnet/IP protocol possible. As documented in the specifications of the KNXnet/IP protocol, the
KNX data can be transmitted encapsulated in IP packages.
3.1 Updating the IP firmware
Thanks to the IP bootloader function, the firmware can be updated remotely and the contents of the flash memory can be re-written via an IP connection. This is not a
simple application download. The communication stack and application software are downloaded.
The firmware update procedure via IP can be carried out from the front-end Web of router 01507, which is independent of the ETS and which uses special messages
to speed up the process. In order to protect this process, it uses special encryption.
Product description - KNXnet/IP

8
BUILDING AUTOMATION
4. The KNX Secure protocol
The device is used to activate the “KNX SECURE” data encryption protocol, entering the QR code or the digits in ETS and also creating a password associated to the
project.
N.B.: If the QR code printed on the label is too small, take a photo of it with a smartphone and enlarge it.
The password is mandatory in the following cases:
- when enabling the Secure part of the devices in the project
- when entering the certificate of a Secure device in the project
If the Secure part of a device is disabled, it acts exactly like a device that does not support this protocol.
If you do not wish to enable the Secure part, when importing the device into the project close the Secure request window as described in the following procedure.
1. Add the Secure device to the ETS project.

KNX Secure device
2. Ignore the set password request.


Close the window
or
select Cancel
The KNX Secure protocol

9
BUILDING AUTOMATION
3. The device is displayed with the Secure part disabled.

Secure disabled

Transparent icon = Secure disabled
4. No password is associated with the project.
5. No certificate is associated to the project.
The KNX Secure protocol

10
BUILDING AUTOMATION
5. Description of operation
In KNX network systems, router 01507 is used to transfer messages from KNX bus to By-me bus and vice-versa. The message exchange rules are totally defined by the
installer using the dedicated folder (Group objects, Parameters, DCA) created in ETS for the specific device. It can be used normally without activating the Security function
and in ETS projects in which the Security function is active. After connection to KNX IP, router 01507 works with its default settings. A valid individual address must be set.
5.1 General Information
When it receives data which use group addresses, router 01507 behaves in accordance with the settings present in the DCA. During normal operation, it only forward
messages whose group addresses are specified in the routing rules defined in the DCA.
If the messages forwarded by the router do not receive confirmation, for instance because the recipient is missing or due to a transmission error, the messages will be
repeated up to three times.
The router is intended for use in 10/100 BaseT networks conforming to IEEE802.3. The AutoSensing function automatically sets the baud rate (10 Mbit or 100 Mbit).
The IP address can be received by an DHCP server. For this purpose, the setting of the automatic IP address assignment can be set via ETS (“Obtain an IP address
automatically”). If this setting is configured but no DHCP server is found, router 01507 starts an AutoIP procedure and autonomously assigns itself an IP address; the
device must have a fixed IP address (a standard gateway and subnet address), it can be set via ETS.
5.2 IP network
Router 01507 sends messages to/from the TP network to/from the IP network in compliance with the specifications of the KNXnet/IP protocol. Via a supervision soft-
ware, in the case of a default setting, the IP data are sent as IP Multicast to the IP address 224.0.23.12 port 3671. The IP Multicast address 224.0.23.12 is the address
for KNXnet/IP established by the KNX Association together with IANA. We recommend you change this address only if the need arises due to the existing network.
N.B.
• All the KNX IP devices that need to communicate with one another via IP must have the same IP multicast address.
• It may be necessary to change the IP multicast address 224.0.23.12 depending on the type of network and on the settings of the network components.
• For the IP routing and identification, the IGMP protocol (Internet Group Management Protocol) is used.
• In the event of problems assigning the IP address, please contact your network administrator.
5.3 Message flow example
Multicast control
sent by a supervisor
The group address used in
the message is searched for
in the routing table. If found
in the correct direction, the
group message recipient
address is transformed and
forwarded using the cor-
responding address
The message is sent using
the multicast connection to
the By-me router
The message travels along the IP
network to the By-me router
The message is forwarded
to By-me
If it is not blocked by the routing rules, the
message travels along the bus in the opposite
direction until it returns to the supervisor
The relay recognises the
message and the group
address, so it performs the
request and sends the infor-
mation with the new status
Relay
Description of operation