Návod k obsluze zabezpečeného routeru TP VIMAR 01506 Plus KNX

A: If the device Certificate is lost, and you cannot retrieve
it, the device can only be used in non-protected mode. Ensure to
keep the removed label part in a secure place to maintain
zabezpečení.

“`

View Fullscreen

Instalační manuál
01506 By-me KNX router

AUTOMATIZACE STAVEB

DOBŘE KONTAKT PLUS

AUTOMATIZACE STAVEB
2

BUILDING AUTOMATION Index
1. Product description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1 .1 Front view of the device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1 .2 LED indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1 .3 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1 .4 Secure Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1 .5 Important notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1 .6 Keeping the device Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 .7 Summary of functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2. The KNX Secure protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3. Description of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 .1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3 .2 Adding the device Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 3 .3 Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3 .3 .1 Programming the individual address (and application) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3 .3 .2 Network backbone configuration with KNX Secure active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3 .3 .3 01548 interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4. Organising the DCA for customising associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4 .1 Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4 .2 Section A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4 .3 Section B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4 .4 Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4 .5 Preliminary procedures on the By-me Plus system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4 .6 Configured By-me Plus system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4 .7 Adding a communication object from By-me Plus data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4 .8 Non-configured By-me Plus system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4 .9 KNX Communication objects present in the By-me Plus island . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4 .10 Assigning By-me data to Communication Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4 .11 Copying Communication Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4 .12 Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4 .13 Copying the By-me/KNX gateway from ETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4 .14 Completing the ETS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4 .15 Cloning a room/area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8. amples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3

AUTOMATIZACE STAVEB
System Requirements – Product description
1. Popis produktu
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 450 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 01506 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 .
1.1 Přední view zařízení

01506

ROUTER By-me KNX

Stát

TP By-me TP KNX

Provoz

G S TP X

BUS Program

KNX

A: By-me BUS line status LED B: KNX line status LED C: Traffic on By-me BUS line LED D: Traffic on KNX line LED E: GA LED F: PA LED G: Push button not used H: By-ME BUS line I: Configuration LED L: Configuration push button M: KNX line

H I LM

1.2 LED indikací
By-me BUS line status LED (A) KNX line status LED (B) Traffic on By-me BUS line LED (C) KNX line traffic LED (D) GA LED (E) PA LED (F) Configuration LED (I)

Green ON: Correct operation ON: Data traffic presence
–

Red ON: Device factory reset
ON: Device not configured ON: Device in the configuration phase

BUILDING AUTOMATION Product description
1.3 Commissioning For commissioning with the default settings, keep the following in mind: · To activate the security function and Secure Commissioning you will need the device Certificate · Security function activation requires a specific minimum ETS version number

0044270

01506

ROUTER By-me KNX State

TP By-me Traffic

TP KNX

S TP X BUS Program

KNX

Art. 01506 X

Serial number: MAC address:

0072031B45CB D0 76 50 00 57 EC
Art. 01506 0072031B45CB Device certificate: ABZAGG-2BZKDF 54SHGN-OIPIXZ RRPF6Z-A5GESR

KNX line By-me Bus
To launch a secure configuration download, you first need to activate the Secure Commissioning in the ETS project . Also read chapter “1 .5 Important notes” before operating the device .
1.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 01506 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 .

BUILDING AUTOMATION Product description
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) . 1.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: 1.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) 1.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 . 1.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 .
6

BUILDING AUTOMATION Product description – KNXnet/IP
1.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) .

0044270

Art. 01506 X
Serial number: 0072031B45CB MAC address: D0 76 50 00 57 EC
Art. 01506 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 certificates 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 the device may only be used in the non-protected mode, like a “normal” device .

1.7 Summary of functions · The device Certificate guarantees that only authorised persons may access device 01506 . · 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 .

AUTOMATIZACE STAVEB
Protokol KNX Secure
2. 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 .
8

Close the window or
select Cancel

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

Secure disabled

5. No certificate is associated to the project .

BUILDING AUTOMATION Description of operation
3. Popis provozu
In KNX network systems, router 01506 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 01506 works with its default settings . A valid individual address must be set . 3.1 General Information
When it receives data which use group addresses, router 01506 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 . 3.2 Adding the device Certificate Each KNX Secure device uses its own Certificate . The device Certificate must be entered in ETS before activating or using the KNX security functions .
The device Certificate is printed on a label affixed to the side of the casing . The device Certificates can be entered manually or by scanning the QR code with the webcam . After the project has been opened, the list of device Certificates can be edited in the Security tab of Project Overview .
If the device Certificate has not been added to the list yet, when a protected download is launched, the following window appears .
10

BUILDING AUTOMATION Description of operation
3.3 Programming 3.3.1 Programming the individual address (and application) To download the individual address in a device, the Programming mode must be active . Press the programming button to activate or deactivate the programming mode . A red lit configuration LED (I) indicates the programming mode is active . When the download from ETS is activated and you press the programming button, the device stores the new individual address in the memory . The security settings are updated by downloading the individual address and application (L) . The KNX address can be assigned to the device by setting the desired address in the ETS properties window . At the end of download from ETS, the device will restart .
The device is supplied with the individual address 15 .15 .255 (default factory setting) . We advise against using this address for normal operation of a system and recommend assigning a different address when commissioning . If the configuration LED (I) flashes red, this means the Ethernet cable is not connected correctly or that a connection with an IP network is not available . The ETS database is available on the company website and in the ETS on-line catalogue .
11

BUILDING AUTOMATION Description of operation
3.3.2 Network backbone configuration with KNX Secure active. If you want to use KNX Secure we recommend you set the Backbone IP to Secure (by default ETS sets it to “Automatic”) . To set the backbone to secure, display the Topology and edit the “Security” property .
This means that all the IP/KNX devices connected to the system support and are configured with KNX Secure . In the presence of IP/KNX devices that are not configured in KNX Secure, ETS will display the following warning:
N.B. If reset devices are present, the default physical address 15 .15 .255 is not read by the ETS diagnostics because it is transmitted unencrypted when the Backbone is Secure . Once the Backbone secure is activated, the configuration status of the various Secure devices will show as not up to date and so the application programmes will have to be downloaded again . 3.3.3 01548 interface configuration For the correct operation of the router 01506 configuration procedure, the physical addresses on the secondary line (TP) must be filtered .
12

BUILDING AUTOMATION Organising the DCA for customising associations
4. Organising the DCA for customising associations
To simplify the definition of the association between By-me group and KNX group, there is a tab called DCA available (as in the figure below) .

4.1 Ovládací prvky

Import rostliny By-me

Obnovit

Kopírovat komunikační objekt

Přidat komunikační objekt (nikoli By-me)

4.2 Section A Displays the By-me Plus system organised in a navigation tree: · the “Environments” nodes are present at level I; · the “Applications” nodes are present at level II; · the “Group” nodes are present at level III; · the “Group address” nodes are present at level IV . The “Group” nodes are only displayed in the presence of applications which need several groups (see temperature control operation) . If this is not the case, Level III is not displayed whereas information of Level IV Group addresses is presented .
4.3 Section B Displays the list of all the By-me Plus/KNX associations which the installer has defined (max 450) . In the above figure, the area reserved for By-me information (on the left) is clearly distinguished from the area for the KNX data (on the right) . The “Common” column contains the direction of group messages which cross the Router .
Each communication object defined can be deleted by tapping the icon , which activates the deletion function .

BUILDING AUTOMATION Organising the DCA for customising associations

4.4 Tab This is the section of ETS which contains all the default “Tab Group Object” and “Parameters” . A specific “DCA” tab is dedicate to “01506 Router By-me KNX” for the definition of the routing rules .

4.5 Preliminary procedures on the By-me Plus system After configuring the By-me Plus system using the View Pro App, importujte informace do xml file (see the By-me Plus manual) .

4.6 Configured By-me Plus system Allows you to import the By-me Plus system into the DCA .

1. Activate the function by clicking on icon

2. Pomocí file průzkumník, vyberte xml file containing the By-me Plus system data .

Section A contains the By-me Plus system data .

4.7 Adding a communication object from By-me Plus data There are two ways to do this: · Drag&Drop the “Group” node from Section A to the area reserved for Communication objects; · Double-click on the “Group” node in Section A Before adding the new Communication Object to the “By-me Plus KNX SECURE Router” a check is carried out for any error conditions: · addition of a Communication Object when the By-me Plus KNX SECURE Router table has already reached 450 rows; · duplicate Communication object name . The installer can always customise the “Direction” and “Name” by double-clicking on the routing table row .

BUILDING AUTOMATION Organising the DCA for customising associations

4.8 Non-configured By-me Plus system

Před importem souboru By-me Plus xml file, ručně přidejte všechny komunikační objekty na straně KNX pomocí ikony

Once you have done this, you can import the By-me Plus system and complete the definition of associations .

In this case the name of the communication object is not automatically prompted by the procedure but is left up to the installer, who can also set the direction of the messages and the type of data transported (1 .xxx will be valid for 1 .001, 1 .002, 1 .003, etc .) .
4.9 KNX Communication objects present in the By-me Plus island With the “Extra KNX Communication Object” option, you can manage the KNX devices (not By-me Plus) connected inside the By-me Plus island . In this case, the device is not present in the By-me Plus xml file vyvezeno z View Pro App .

BUILDING AUTOMATION Organising the DCA for customising associations

To complete configuration, you need to specify the KNX format that the By-me Plus KNX SECURE Router should adopt; the options are: · 2 levels · 3 levels . Next, the installer can set the KNX group address of the communication object they have just defined . The group address is inserted in the “By-me Addr” column in the chosen KNX format .

4.10 Assigning By-me data to Communication Objects After adding the KNX communication objects to the By-me Plus KNX SECURE Router device, proceed as follows:
1. Configure the By-me system with the home automation system gateway;
2. Export the system in xml format;
3. Access the “DCA” of the By-me/KNX gateway;
4. Import the xml file;
5. Drag&Drop the By-me Plus node to the row associated with the By-me Plus KNX SECURE Router of the routing table .
In this case the DCA should check the consistency of the “Data Type of the By-me DPTx” selected with what is already set in the destination row (Main DPT) . Only if the respective Main DPTs match will the Drop be permitted (permitting the same format of the Main DPT on the By-me side with respect to the one on the KNX side: e .g . By-me Data Type 1 .001 KNX Main Data Type 1 .xxx) .

4.11 Copying Communication Objects

The Copy function

allows you to make a copy of a Communication Object for those which only have KNX data .

Once you have selected a row in the Communication Objects table, you can duplicate the related Communication Object, whose window appears with the “Direction” and “Data Type” fields already set . You will need to edit the “Name” (which must be different) .

4.12 Errors The following errors are envisaged: · “Copy Communication Object is disabled when there is no row in the By-me/KNX Gateway or it hasn’t been selected · “Addition” of a Communication Object when the By-me/KNX Gateway table has already reached 450 rows . · Communication Object selected has all the By-me parameters defined: in this case only the KNX part is duplicated (the name changes everywhere) whereas the By-me part stays empty and has to be associated starting with a node of the By-me tree .
N.B.: In the event that the By-me parameters are defined, the copy function is disabled .

BUILDING AUTOMATION Organising the DCA for customising associations
4.13 Copying the By-me/KNX gateway from ETS After defining the By-me/KNX Gateway, ETS can be used to duplicate the device inside the same KNX system and set its characteristics (see figure below) .
4.14 Completing the ETS configuration On completion of the By-me Plus KNX SECURE Router definition, tap the “Group Objects” tab to associate the group address with each communication object defined . This way, the information is managed similarly to the system KNX device information .
17

BUILDING AUTOMATION Organising the DCA for customising associations
4.15 Cloning a room/area This option allows you to clone a room (or area) already configured in another . In the following example, room 101 is copied to room 102 .
You can now rename Room 101 Copy in Room 102 and attribute the physical address of the Gateway .
18

BUILDING AUTOMATION Usage examples
5. Použití napřamples
5.1 Mixed system with 01506 TP/IP, configuration
přepínač

By-me bus

sběrnice KNX

01548

01548 ROUTER IP KNX

Stát

Provoz

GA PA Function

Naprogramovat

01506

ROUTER By-me KNX State

TP By-me Traffic

TP KNX

S TP X BUS Program

KNX

By-me

KNX

strana

5.2 Mixed system with 01506 TP/IP, supervision

By-me bus

sběrnice KNX

01548

01548 ROUTER IP KNX

Stát

Provoz

GA PA Function

Naprogramovat

01506

ROUTER By-me KNX State

TP By-me Traffic

TP KNX

S TP X BUS Program

KNX

By-me

KNX

strana

přepínač

WCS

By-me bus

sběrnice KNX

01548

01548 ROUTER IP KNX
State IP TP
Traffic GA PA Function
Naprogramovat

01506

ROUTER By-me KNX State

TP By-me Traffic

TP KNX

S TP X BUS Program

KNX

By-me

KNX

strana

By-me bus

sběrnice KNX

01548

01548 ROUTER IP KNX
State IP TP
Traffic GA PA Function
Naprogramovat

01506

ROUTER By-me KNX State

TP By-me Traffic

TP KNX

S TP X BUS Program

KNX

By-me

KNX

strana

01506 IT 05 2511

Viale Vicenza 14 36063 Marostica VI – Itálie
www.vimar.com

Dokumenty / zdroje

VIMAR 01506 Plus KNX Secure TP Router [pdfNávod k obsluze
01506 Plus KNX Secure TP Router, 01506, Plus KNX Secure TP Router, KNX Secure TP Router, Secure TP Router, TP Router

Reference

Uživatelská příručka

Návod k obsluze zabezpečeného routeru TP VIMAR 01506 Plus KNX

01506 Plus KNX Secure TP Router

Specifikace

Popis produktu

Přední View zařízení

Návod k použití produktu

Systémové požadavky

Keeping the Device Certificate

Device Security Caution

KNX Secure Protocol

FAQ

Q: What should I do if I lose the device Certificate?

Dokumenty / zdroje

Reference

Zanechte komentář

Zrušit odpověď