INTRODUCTION... 3 DEVICE S CONFIGURATION... 4 KNX CONFIGURATION. SKX LINKER Hardware Configuration Objects Selection...

Transcription

1 SKX LINKER PRONTO

2 INDEX INTRODUCTION... 3 DEVICE S CONFIGURATION... 4 KNX CONFIGURATION. SKX LINKER... 5 Hardware Configuration... 5 Objects Selection... 6 Control Objects. ZENNIO specific spreadsheet LAN CONFIGURATION ROUTER Configuration PRONTO Configuration NPORT 5110 Configuration KNX RED IP LINK CONFIGURATION KNX INSTALLATION. PLANNING AND IMPLEMENTATION INITIAL INSTALLATION PRONTO PROGRAMMING SKX LINKER AND NPORT 5110 PHYSICAL INSTALLATION SKX LINKER NPORT RECOMMENDATIONS ON/OFF (1 BIT) CONFIGURATION DIMER REGULATION (1 BYTE) CONFIGURATION REGULATION (1 BYTE) CONFIGURATION TEMPERATURE (2 BYTES) CONFIGURATION TIPS EXAMPLE PROJECT SUMMARY APPENDIX I. ZENNIO SCRIPT OBJECTS

3 INTRODUCTION The goal of this document is make the integration of KNX with other interesting control systems easier, in this case with PRONTO products (PHILIPS). It helps to achieve an attractive interface between the user and the control system, so called HMI (Human Machine Interface). This kind of integration depends on a specific device: SKX Linker: SKX Linker. Bus to RS 232 Interface. There are already others documents which are about this topic, but they are oriented from the point of view of PRONTO programming. This is why ZENNIO try to complement this documentation to achieve a comprehensive library of information. The further reading of those other documents are highly recommended nevertheless (i.e. ZENNIO PRONTO SCRIPT v2.6) It is not an aim of this document deal deeply with the PRONTO programming, but explains how the different devices work within the installation, giving to the integrator a high knowledge about this kind of installations. Several tools are provided with this manual: Examples to understand better the explanations. Spreadsheet to arrange the installation s information. 3

4 DEVICE S CONFIGURATION Elements to incorporate into the facility are listed below: SKX Linker of ZENNIO. Bus to RS 232 Interface. Pronto panel of PHILIPS. Other devices that are needed to carry out the integration: NPort 5110 of MOXA. RS 232 to IP Interface. Router. It is understood that a KNX installation is made, which will be the aim to control with this solution. The physical connexions between the different devices are showed in the following diagram. LAN SERIAL BUS KNX PRONTO WIFI RJ 45 ROUTER NPORT 5110 RS232 SKX Linker BUS KNX KNX INSTALLATION Figure 1. Physical Installation In other hand, specific programming tools will be needed to be able to carry out the programming of each device: PRONTO WIFI ROUTER RJ 45 NPORT 5110 RS232 SKX Linker BUS KNX KNX INSTALLATION Pronto Edit Professional Nport Administrator ETS ETS Figure 2. Configuration Tools 4

5 KNX CONFIGURATION. SKX LINKER The tactile and portable PHILIPS panel, due to its good features (WIFI, size), versatility (A/V devices control) and other factors like design, become a very interesting device to control a KNX installation. Owing to the fact that the Pronto is not a KNX device, this paper presents a solution to integrate it into a facility that is based on the KNX standard. To do this, simply equip the KNX installation with a single device: The SKX Linker of ZENNIO. The function of this device is to receive KNX telegrams on one side and transmit serial telegrams on the other side, and vice versa, because it is a device that allows TWO WAY communication. SKX Linker configuration parameters, through the ETS* (see footnote), is very simple. Within its parameters, you can find the following sections: Configuración de Hardware (Hardware configuration). Selección de Objetos (Objects selection). Hardware Configuration Through the hardware configuration section sets out the basic parameters of the communication device: Comunicación (Communication): The type of serial communication is via a RS232 bus type. Velocidad de la comunicación (Communication Speed): This speed may not be greater than the KNX standard bit rate (9600 bits/sg) Paridad (Parity): There is not parity bit correction. Longitud de los datos (Data length): It is a fix data, 8bits. TimeOut (msg): Time to clear the buffer input device, to avoid overlapping of telegrams that for some reason have had an error in transmission. 10 msg is considered an appropriate value. *Note: The current application program version, 0.2, is only in Spanish. The next improved version will be in both languages Spanish and English. 5

6 Figure 3. SKX Hardware Configuration Objects Selection It is here where the explanation of the SKX Linker philosophy has to be done. It is a device that allows "create" a certain number of objects with a default length (in bits). It enables the creation of up to 250 objects in total, with various lengths: 1 bit 2 bits 4 bits 1 byte 2 bytes 3 bytes 4 bytes 14 bytes Note also that these objects of communication have not a specific format; it means they are not defined as objects of communication for the transmission of a temperature value, or a value of regulation, for example. 6

7 Therefore, it is in this step where the integrator must pay special attention to the link of these objects of communication. It could be possible that no ETS errors happen, but the receiving values are not the desired values. An example: 2bytes objects in SKX Linker are enabled, which allow receive a temperature value from the KNX bus. The group address 2/0/10 Current Temp is created, as shown below: Figure 4. Group Address 2/0/10 Current Temp. The purpose of communication 3 (from device 1.1.1) corresponds to a Z38 ZENNIO screen, which is configured to cyclically send the temperature value to the bus. The other object corresponds to the 181 (from the device ), which is an object of communication of 2bytes from the SKX Linker. Linked in a proper way with the PRONTO script, this value will be showed on the PRONTO screen. If, by different reasons, the object 181 was linked to the output of a 2 bytes counter, the link would still be correct, but the screen would not be represented by the desired temperature (for example, a value of 50 from the counter will display a 6 C in the screen) This is an exaggeration, but whose purpose is to demonstrate the importance of paying special attention to addressing such objects. To facilitate the task of programming communication objects of SKX Linker, ZENNIO provides (along with this manual), an application based on spreadsheets, which allows tracking of all communication objects created. This is very useful for creating documentation in a project, since it can store the information needed for future changes in the installation (upgrades, changes in functionality). Due to the large number of objects in the SKX Linker is highly recommended. The next section is to explain the application: 7

8 Control Objects. ZENNIO specific spreadsheet. The application based on spreadsheets is simple but very useful for keeping all the information arranged. This application consists of 4 sheets, which are explained below. Figure 5. Sheet 1: Zennio Applications This sheet shows the basic details of the installation, which allows a simple recap of basic data, such as: SKX Linker Physical Address Moxa Device IP Address Project Summary Underneath these descriptive data, there are shortcuts to the pages of objects. These pages have been named in the same way as to appear in the Script ZENNIO. Page Parameters. Temperature Parameters. Scene Parameters. In these pages communication objects with the spaces to fill in the pages of the ZENNIO script are related. 8

9 Page Parameters Figure 6. Sheet 2: Page Parameters In choosing a subject in Page Parameters, it opens a box which shows the same objects that appear in the ZENNIO script (see Appendix I). Temperature Parameters Figure 7. Sheet 3: Temperature Parameters In choosing a subject in Temperature Parameters, it opens a box which shows the same objects that appear in the ZENNIO script (see Appendix I). 9

10 Scene Parameters Figure 8. Sheet 4: Scene Parameters In choosing a subject in Scene Parameters, it opens a box which shows the same objects that appear in the ZENNIO script (see Appendix I). LAN CONFIGURATION The control panel PHILIPS protocol is based on the IP network to transmit their orders and execute their actions. The panel is equipped with Wi Fi technology, which connects to a router (with Wi Fi protocol). The following table specifies the devices that are part of the IP network, and their link to download the relevant software. Device Manufacturer Programming Tool Download PRONTO PHILIPS Pronto Edit Professional 2.0 PEP NPORT 5110 MOXA NPort Administration Suite NAS ROUTER 1 0

11 ROUTER Configuration The installation of the router is responsible for enabling connections between different devices on the IP network. PRONTO configuration depends on the configuration of the router. panel. The advanced security settings on the router must be used to configure the PRONTO A good way to organize the IP network is to set up a router in the DHCP (Dynamic Host Client Protocol) that automatically assigns IP addresses to devices that have a DHCP client (such as, for example, PRONTO), and some addresses are reserved for the installation of fixed devices (such as device NPORT 5110). An example is shown in the table below for a network with IP address : IP Addresses Device Router Device Device 2 > DHCP Figure 9. Router Configuration. PRONTO Configuration PRONTO configuration is done through software developed by Philips for this product family, called the Pronto Edit Professional. There is already abundant literature, it is not going to make a thorough study of the possibilities of programming, but will focus on some aspects 1 1

12 of programming the ZENNIO script: the objects of communication to be precise (see KNX Installation. Planning and Implementation). Under the Network tab of the system properties several features can be configured: Set up the DHCP Security configuration Figure 10. Network settings. Where security is a critical aspect of the installation, you can perform a filtering MAC addresses (Media Access Control), as each device on the market has a unique MAC address. To obtain the MAC address of the device PHILIPS, simply leave the button tool (over 5 seconds), and open the tab INFO. Figure 11. Technical information about PRONTO unit 1 2

13 NPORT 5110 Configuration This device links the SKX Linker with the IP network. It is basically a transducer that converts telegrams from IP network to serial communication, and vice versa. Therefore, the link between the two networks (KNX and LAN) is achieved through serial communication. SERIAL BUS KNX NPORT 5110 RS232 SKX Linker Figure 12. Link between transducers devices To set the NPORT 5110 requires a management tool which can be downloaded from the manufacturer's website. The tool takes care of finding the device on the network, and allows its configuration. We are not going to pay more attention in this guide to configuring this device, since it was already discussed in other manuals. KNX RED IP LINK CONFIGURATION In the connection of transducers devices, special attention must be paid at the time of making the connection and the power of the serial bus. Due to the KNX standard, the power of the bus has to be different than the KNX bus itself, so to supply an AC / DC external power is needed. In the diagram below clearly shows the connection of the pins of transmission, reception, ground and power: 1 3

14 Figure 13. Diagram connection of SKX Linker 1 4

15 KNX INSTALLATION. PLANNING AND IMPLEMENTATION INITIAL INSTALLATION To facilitate rapid integration, it is recommended to organize the group addresses a clear and concise. The following steps could be defined: Identify the devices you wish to control from the PRONTO. For example, lighting elements, splits, blinds... Within each device, identifying the features you want to control. For example, changing modes of the split, dimming lighting loads... If scenes are include, drawing up a list with the scenes of each device. PRONTO PROGRAMMING Once identified the devices and the features you want to manage remotely, the next step is the programming through the software provided by the manufacturer, the Pronto Edit Professional 2 (PEP2). With the help of the manual attached with the ZENNIO script, you can do this without much problem. Only recommends the following methodology: Configure all the parts of the script which can be configured, except for the ZENNIO objects (identified with the symbol #). Open the ZENNIO application (SKX Linker Objects.xls) and mark with the help of the list box, those ZENNIO communication object boxes that have been left blank and wish to be used. For example, if within the page SCENES 1 scenes want to be configured, and has been left blank in that object, mark it in the application, within the sheet SCENE PARAMETERS, in the Objects column, the following object: o SCENE_PAGE_1_OBJECT_SCENE At the end of the PRONTO programming all the communication objects would have been identified. 1 5

16 NOTE: You can use as many sheets as necessary. Figure 14. Example Application ZENNIO. Step 1 SKX LINKER AND NPORT 5110 PHYSICAL INSTALLATION Once the PRONTO programming is done (which also will set up your access to the network, as seen before in the installation section), the next step is to install physical devices to intercommunicate the different networks. SKX LINKER It is connected to the KNX bus like another device. Once installed, proceed to the download of its physical address, and programming parameters (hardware parameters) as seen in the installation section. But now it must take into account how many items are needed for communication and that length. Although, by default, all the communications objects can be enabled. Figure 15. SKX Linker objects selection 1 6

17 Once the communications objects are enabled, link them in a free way (choosing the number of object you want, whenever the appropriate length) with the group addresses that you want to control. That is, if you want to control an ON / OFF group address of an electric charge, using a 1 bit communication object and link it with that group address. Next, note this change in application of ZENNIO, indicating: Object number. Linked group address. Comments. NPORT 5110 Figure 16. Example Application ZENNIO. Step 2 It connects to the LAN through RJ 45, and is configured using the software tool provided by the manufacturer, called NPort Administration Suite. It is configured using the steps defined in the installation section. Once installed two transducers, they are connected via a RS 232 serial cable, which must take external DC power (see instructions). By ZENNIO Script can check if everything is configured correctly, thanks to an application that verifies the correct installation of the devices. Figure 17. Test Page 1 7

18 RECOMMENDATIONS Here are the most common configurations of an installation (ETS and PEP2 programming) ON/OFF (1 BIT) CONFIGURATION The ON / OFF configuration is the simplest of all can be done. For example, the ON / OFF control of a light load. Within the Script ZENNIO, all types of control carried at least a 1 bit control. For example, if an ON / OFF lighting load want to be controlled, simply associate an 1 bit object of SKX Linker with the group address which is associated with the output of the actuator that controls the load. In this case, the OBJECT 2 is associated in the same group address where the Z38 screen controls the load. Device Physical Address Object Z SKX Linker ACTinBOX MAX In the script, simply indicate the type of control 10, and modify the ZENNIO object, indicating the object 2, which is used in ETS. 1 8

19 DIMER REGULATION (1 BYTE) CONFIGURATION The following configuration example relates to dimming loads. In this case it will be needed to associate more than one subject to such regulation. This control shall include the basic action (1 bit) to perform the function ON / OFF, plus other actions that will regulate the load on the desired percentage of light. The communication is always bidirectional, so ETS is configured in the way that all elements involved in an action must know the state of the elements that control (STATUS). To perform this configuration, create typical group addresses of regulated control of lighting, using 1 bit control objects, is needed: Device Physical Address Object Z LuZen ONE SKX Linker And 4 bits too (within this group address is not involved the Linker SKX) Device Physical Address Object Z LuZen ONE To carry out dimming control from a PRONTO pane, a new group address is implemented, which makes the precise control of 1 byte, as a percentage. Device Physical Address Object LuZen ONE SKX Linker

20 Now, the control is done through different objects, therefore it is necessary to create a new group address to indicate the elements of control (the Z38 and PRONTO in this example) the status of the lighting load. Device Physical Address Object Z LuZen ONE SKX Linker* * 133* * Emphasize that the communication object 133 is being used twice, and since it is allowed send (S activated) only by one group address, it is sent by the group address made for the dimming control, because in the case of updating state does not need to send anything but receive (please, have a look to the column Sending in the figure below, object 133). The last step is writing these communication objects in the boxes of the ZENNIO script, in Pronto Edit Professional 2: 2 0

21 REGULATION (1 BYTE) CONFIGURATION It is the same as in the previous case, but considering it takes an extra group address, since there is a control to stop the blind at the desired point along its length by a short pulse. The first step is to perform a 1 bit control, which allows a long press to send the order to move to the end of the trail to the blind Device Physical Address Object Z ACTinBOX MAX SKX Linker The second step is to create a new group address, with a short pulse, allows the blind to stop at any point of its length. Device Physical Address Object Pantalla Z ACTinBOX MAX SKX Linker The third step is to implement the group address that allows the positioning the blind at any percentage of its length through PRONTO Device Physical Address Object ACTinBOX MAX SKX Linker

22 Finally, as in the case of the lighting regulation, the control is done by different devices (between PRONTO and Z38), therefore create a group address to report the status of the blind is needed. Device Physical Address Object Pantalla Z ACTinBOX MAX SKX Linker* * 134* * Emphasize that the communication object 134 is being used twice, and since it is allowed send (S activated) only by one group address, it is sent by the group address made for the dimming control, because in the case of updating state does not need to send anything but receive (please, have a look to the column Sending in the figure below, object 134). The last step is writing these communication objects in the boxes of the ZENNIO script, in Pronto Edit Professional 2: 2 2

23 TEMPERATURE (2 BYTES) CONFIGURATION Without any complications, just link a device that sends cyclically a temperature value (such as Z38 or a QUAD), with a 2 bytes object of SKX Linker. Device Physical Address Object Z SKX Linker The last step is writing this communication object in the box of the ZENNIO script, in Pronto Edit Professional 2: 2 3

24 TIPS If a ZENNIO script element will not be used, it is best to write the value "0" in its type. Look at the objects 3 and 4 below. Special attention must be paid to the SKX Linker objects, checking through the bus monitor program what values are received. Perform a strict control of the used objects, for example, using the enclosed application for this manual (XLS file extension) 2 4

25 EXAMPLE PROJECT An example project that controls the following installation is attached (PR4 file): KNX: Device (from Zennio) Physical Address Screen Z LuZen ONE ACTinBOX MAX ZN1CL IRSC SKX Linker LOCAL AREA NETWORK: Device IP Address Router MOXA NPort PRONTO TSU6000 DHCP DEVICES: Split. 2 lights loads (no dimmer). 1 dimming load. 2 blinds. FILES: ETS file: ZENNIO.pr4 PEP2 file: KNX Pronto.xcf ZENNIO spreadsheet file: SKX Linker Objects example.xls 2 5

26 SUMMARY This manual explains how to set a general facility that includes a home automation network based on the KNX standard with a control panel PHILIPS (PRONTO product family). It is an overview of how a successful software configuration between KNX standard software (ETS) and PHILIPS (PEP2) to configure the most common elements of a home automation installation. 2 6

27 APPENDIX I. ZENNIO SCRIPT OBJECTS Connection between the following components: ZENNIO script objects Scroll bars in the ZENNIO application, made for arrange the installation s information (FILE SKX Linker Objects.xls) Despite of the fact there are a big amount of objects, the scroll bar is arranged in a very intuitive way, with double separation between objects that are related with each page. PAGE PARAMETERS Object A1 B1 C1 D1 E1 F1 G1 H1 I1 J1 K1 L1 Name PAGE_PARAMETERS_1_OBJECT_NAME_1_ZENNIO PAGE_PARAMETERS_1_OBJECT_NAME_1_DIMMER_BLIND_1 PAGE_PARAMETERS_1_OBJECT_NAME_1_DIMMER_BLIND_2 PAGE_PARAMETERS_1_OBJECT_NAME_2_ZENNIO PAGE_PARAMETERS_1_OBJECT_NAME_2_DIMMER_BLIND_1 PAGE_PARAMETERS_1_OBJECT_NAME_2_DIMMER_BLIND_2 PAGE_PARAMETERS_1_OBJECT_NAME_3_ZENNIO PAGE_PARAMETERS_1_OBJECT_NAME_3_DIMMER_BLIND_1 PAGE_PARAMETERS_1_OBJECT_NAME_3_DIMMER_BLIND_2 PAGE_PARAMETERS_1_OBJECT_NAME_4_ZENNIO PAGE_PARAMETERS_1_OBJECT_NAME_4_DIMMER_BLIND_1 PAGE_PARAMETERS_1_OBJECT_NAME_1_DIMMER_BLIND_1 And for the rest page of Page Parameters: 2 7

28 2 8 Object Name A2 PAGE_PARAMETERS_2_OBJECT_NAME_1_ZENNIO B2 PAGE_PARAMETERS_2_OBJECT_NAME_1_DIMMER_BLIND_1 C2 PAGE_PARAMETERS_2_OBJECT_NAME_1_DIMMER_BLIND_2 D2 PAGE_PARAMETERS_2_OBJECT_NAME_2_ZENNIO E2 PAGE_PARAMETERS_2_OBJECT_NAME_2_DIMMER_BLIND_1 F2 PAGE_PARAMETERS_2_OBJECT_NAME_2_DIMMER_BLIND_2 G2 PAGE_PARAMETERS_2_OBJECT_NAME_3_ZENNIO H2 PAGE_PARAMETERS_2_OBJECT_NAME_3_DIMMER_BLIND_1 I2 PAGE_PARAMETERS_2_OBJECT_NAME_3_DIMMER_BLIND_2 J2 PAGE_PARAMETERS_2_OBJECT_NAME_4_ZENNIO K2 PAGE_PARAMETERS_2_OBJECT_NAME_4_DIMMER_BLIND_1 L2 PAGE_PARAMETERS_2_OBJECT_NAME_4_DIMMER_BLIND_2 A3 PAGE_PARAMETERS_3_OBJECT_NAME_1_ZENNIO B3 PAGE_PARAMETERS_3_OBJECT_NAME_1_DIMMER_BLIND_1 C3 PAGE_PARAMETERS_3_OBJECT_NAME_1_DIMMER_BLIND_2 D3 PAGE_PARAMETERS_3_OBJECT_NAME_2_ZENNIO E3 PAGE_PARAMETERS_3_OBJECT_NAME_2_DIMMER_BLIND_1 F3 PAGE_PARAMETERS_3_OBJECT_NAME_2_DIMMER_BLIND_2 G3 PAGE_PARAMETERS_3_OBJECT_NAME_3_ZENNIO H3 PAGE_PARAMETERS_3_OBJECT_NAME_3_DIMMER_BLIND_1 I3 PAGE_PARAMETERS_3_OBJECT_NAME_3_DIMMER_BLIND_2 J3 PAGE_PARAMETERS_3_OBJECT_NAME_4_ZENNIO K3 PAGE_PARAMETERS_3_OBJECT_NAME_4_DIMMER_BLIND_1 L3 PAGE_PARAMETERS_3_OBJECT_NAME_4_DIMMER_BLIND_2 A4 PAGE_PARAMETERS_4_OBJECT_NAME_1_ZENNIO B4 PAGE_PARAMETERS_4_OBJECT_NAME_1_DIMMER_BLIND_1 C4 PAGE_PARAMETERS_4_OBJECT_NAME_1_DIMMER_BLIND_2 D4 PAGE_PARAMETERS_4_OBJECT_NAME_2_ZENNIO E4 PAGE_PARAMETERS_4_OBJECT_NAME_2_DIMMER_BLIND_1 F4 PAGE_PARAMETERS_4_OBJECT_NAME_2_DIMMER_BLIND_2 G4 PAGE_PARAMETERS_4_OBJECT_NAME_3_ZENNIO H4 PAGE_PARAMETERS_4_OBJECT_NAME_3_DIMMER_BLIND_1 I4 PAGE_PARAMETERS_4_OBJECT_NAME_3_DIMMER_BLIND_2 J4 PAGE_PARAMETERS_4_OBJECT_NAME_4_ZENNIO K4 PAGE_PARAMETERS_4_OBJECT_NAME_4_DIMMER_BLIND_1 L4 PAGE_PARAMETERS_4_OBJECT_NAME_4_DIMMER_BLIND_2

29 TEMPERATURE PARAMETERS Object T11 T12 T13 T14 T15 T16 Name PAGE_TEMPERATURE_1_CONSIGN_OBJECT PAGE_TEMPERATURE_1_INTERNAL_SENSOR_OBJECT PAGE_TEMPERATURE_1_A/C STATE PAGE_TEMPERATURE_1_MODE_OBJECT PAGE_TEMPERATURE_1_FAN_SPEED_OBJECT PAGE_TEMPERATURE_1_SWING_OBJECT 2 9

30 Object T21 T22 T23 T24 T25 T26 T31 T32 T33 T34 T35 T36 T41 T42 T43 T44 T45 T46 Name PAGE_TEMPERATURE_2_CONSIGN_OBJECT PAGE_TEMPERATURE_2_INTERNAL_SENSOR_OBJECT PAGE_TEMPERATURE_2_A/C STATE PAGE_TEMPERATURE_2_MODE_OBJECT PAGE_TEMPERATURE_2_FAN_SPEED_OBJECT PAGE_TEMPERATURE_2_SWING_OBJECT PAGE_TEMPERATURE_3_CONSIGN_OBJECT PAGE_TEMPERATURE_3_INTERNAL_SENSOR_OBJECT PAGE_TEMPERATURE_3_A/C STATE PAGE_TEMPERATURE_3_MODE_OBJECT PAGE_TEMPERATURE_3_FAN_SPEED_OBJECT PAGE_TEMPERATURE_3_SWING_OBJECT PAGE_TEMPERATURE_4_CONSIGN_OBJECT PAGE_TEMPERATURE_4_INTERNAL_SENSOR_OBJECT PAGE_TEMPERATURE_4_A/C STATE PAGE_TEMPERATURE_4_MODE_OBJECT PAGE_TEMPERATURE_4_FAN_SPEED_OBJECT PAGE_TEMPERATURE_4_SWING_OBJECT 3 0

31 SCENE PARAMETERS Object S1 S2 S3 Name SCENE_PAGE_1_OBJECT_SCENE SCENE_PAGE_2_OBJECT_SCENE SCENE_PAGE_3_OBJECT_SCENE 3 1

32 COMMENTS: SUBJECT: SKX LINKER PRONTO 3 2