iridium for HDL-BUS Pro

Transcription

1 iridium for HDL-BUS Pro Fast Start: Connection Setting Manual for HDL-BUS Pro (Smart-Bus) equipment Review of iridium Software Package for HDL-BUS Pro: The iridium software package includes several components for installation on your PC and devices based on the Apple ios operation system. Components for installation on your PC: iridium GUI Editor a Graphic User Interface Editor, which allows you to create your own interfaces and set connection to the HDL-BUS Pro (Smart-Bus) bus. iridium Transfer an application for converting and uploading graphic interfaces created in iridium GUI Editor on Apple ios and Windows based control panels. iridium Client for Windows a component for launching and operating the application on your PC. iridium Gate an application, which allows you to establish connection with the HDL-BUS Pro (Smart-Bus) bus over the Internet. It is a gateway which enables data transfer from the Extranet to the Intranet with converting TCP into UDP. The part of the software package for installation on ios devices is the HDL Client application which is in charge of launching and running GUIs on target ios devices. In order to enable the connection of ios HDL Client to the HDL-BUS Pro (Smart-Bus) bus it is required to purchase and activate an iridium license Key. License files for ios received after the Key activation are stored in the Transfer application and are transferred to target ios devices along with GUIs. Licenses for Windows are stored in the project folder (a received license file is copied into the folder with the Client generated for Windows). iridium supports operation with the following devices: Apple ios devices (ipad, iphone, ipod Touch) Windows XP & Windows 7 based devices Recommendations and Requirements for Operation with iridium Software Package PC under Microsoft Windows XP / 7 HDL application installed on your ios device from the Apple AppStore Wi-Fi network for uploading and updating GUIs on ios devices Internet connection for purchasing and activation of iridium license Keys iridium License file for enabling the connection to the HDL-BUS Pro (Smart-Bus) bus

2 Content 2 INSTALLATION OF IRIDIUM SOFTWARE PACKAGE COMPONENTS... 3 CREATING A GUI IN IRIDIUM GUI EDITOR... 4 SCANNING THE HDL-BUS PRO (SMART-BUS) NETWORK... 5 SETTING OF HDL-BUS PRO (SMART-BUS) CONNECTION... 7 CHANNEL SETTING FOR THE HDL-BUS PRO (SMART-BUS) PROTOCOL... 8 HDL-BUS PRO (SMART-BUS) RELAY MODULE CONTROL... 8 Relay Control (Single Channel Control)... 8 Requesting the Relay State (Single Channel Read Target) Requesting the Current Variable Value (Single Channel Read Actual) Relay Trigger Switch CONTROLLING HDL-BUS PRO (SMART-BUS) DIMMERS Dimming by the Level (Slider) Item Reading the Dimmer State (Single Channel Read Target) Controlling a Dimmer by Up/Down Button Specifying a Fixed Level Value by Button OPERATION WITH HDL-BUS PRO (SMART-BUS) SENSORS Requests for the State of HDL-BUS Pro (Smart-Bus) Sensor Outputs at the Project Launch Displaying Outputs States of an HDL-BUS Pro (Smart-Bus) Sensor Sending IR commands by HDL-BUS Pro (Smart-Bus) Sensors HDL-BUS Pro (Smart-Bus) Sensor Lock CONTROLLING MOTORIZED CURTAINS, SHUTTERS AND ROLLER BLINDS CONTROLLERS State Setting of a Motorized Curtains Controller Switch Requesting the Controller Switch State Displaying a Curtain Controller Switch State Trigger Switch of Driver Direction INTERACTION WITH HDL-BUS PRO (SMART-BUS) DLP-PANELS Description of Floor Heating Commands Operation Floor Heating Commands and Their Setting Controlling Air Conditioners and DLP-panel Properties Requests for the DLP-panel Properties State at the Project Launch Displaying a DLP-panel Properties State Requests for Temperature from DLP-panel Sensors ACTIVATION OF SCENES AND SEQUENCES RECEIPT OF STATUS OF VARIOUS VARIABLES AT PROJECT LAUNCH OPTIMIZATION OF IRIDIUM PROJECTS FOR HDL-BUS PRO (SMART-BUS) CONNECTION TO THE BUS OVER THE INTERNET: IRIDIUM GATE UPLOADING A PROJECT ON A PANEL, CONNECTION TO EQUIPMENT EMULATION MODE CONVERSION OF THE PROJECT FOR ITS LAUNCHING ON THE TARGET DEVICE UPLOADING THE PROJECT ON AN IOS DEVICE DESCRIPTION OF THE LICENSING PROCEDURE FOR THE CONTROL DEVICE Receipt of UDID for Activation of the iridium License for an ios Device Licensing Procedure of an ios Device Activation of the iridium License Key for an ios Device Uploading of the License File for ios to iridium Transfer SETTING UP OF IOS HDL CLIENT CREATION OF IRIDIUM WINDOWS-CLIENT Receipt of HWID for iridium Windows-Client Licensing... 65

3 3 Installation of iridium Software Package Components In order to start your work, it is necessary to install two parts of the iridium software package. The first part, an installation package for your personal computer under Windows XP / 7, can be downloaded from the iridium web-site, in the Download section: Link: The iridium software package for installation on PC includes several components. To operate HDL- BUS Pro (Smart-Bus) equipment you require: iridium GUI Editor a Graphic User Interface Editor, which allows you to create your own interfaces for control panels. iridium Transfer an application for uploading graphic interfaces created in iridium GUI Editor on ios devices. iridium Transfer allows you to convert interfaces into the format for their launching on Windows XP/7 devices. It can also check iridium license availability for ios devices. iridium Client - a part of the iridium software package which launches a ready graphic interface on the ipod/iphone/ipad or Windows device. It is responsible for the interaction between the GUI and equipment. In order to correctly run iridium Client you need to obtain a license. You can download iridium Client for Windows from our web site. The second part of the iridium software package is the Client application for its installation on the devices based on the Apple ios operation system. The application is called HDL and can be downloaded from the official AppStore. itunes Link: The HDL Client application is a software component of iridium that is in charge of launching and using graphic interfaces, forming and sending commands to the controlled equipment.

4 4 Creating a GUI in iridium GUI Editor After the iridium package for your PC and the HDL Client are installed, you can start creating GUI to control the HDL-BUS Pro (Smart-Bus) equipment. Start iridium GUI Editor on your PC.! 1. Do not forget that if you run Windows 7, launch of iridium software components should be performed by Administrator rights through the right-click menu or by using Administrator account. 2. Do not forget to close S-bus Configuration Util before starting work with iridium, as running S-bus can cause the noninteraction between iridium Client and the bus. When launching iridium GUI Editor you can see several workspaces which are responsible for different aspects of GUI creating and setting. Let s start our work with creating a new GUI project. After pressing the New Project button a window for customizing the main project settings (Project Name, resolution and First Page Name) will open. Choose the resolution corresponding to the resolution of the Target device where the project will be launched. You cannot change it while working on the project.

5 5 Scanning the HDL-BUS Pro (Smart-Bus) Network Creation of a project for HDL-BUS Pro (Smart-Bus) starts with your local network scanning. It is performed to find all available HDL-BUS Pro (Smart-Bus) devices in the subnet and import them into the Device Tree for their further interaction settings. Start scanning with pressing the «Scan SmartBus Net» button. After the scanning is completed you will see a list of detected devices.

6 6 When scanning for the first time, not all channels can be detected. That is why you can use the function of multiple scanning - «Scan Count». As you can see some devices contain a list of preset channels by default, which you can use in your project in the unmodified state or with some corrections. You have to form channels for those devices which do not have preset channels with the help of iridium GUI Editor. You can add devices and channels to the project manually when HDL-BUS Pro (Smart-Bus) equipment is not connected or when the project is set remotely. You can add an HDL-BUS Pro (Smart-Bus) device and a freely set HDL-BUS Pro (Smart-Bus) channel template manually from the iridium Base in the Device Tree which contains iridium supported devices and protocols. Addition of devices and channels from the iridium Base can be done by the Drag&Drop method. Then you have to decide on the functional of your project. Create a GUI sample containing the necessary number of pages and popups where HDL-BUS Pro (Smart-Bus) equipment control items and buttons for jumping between pages and popups will be positioned. You can use one of the iridium sample designs which you can download from our web site or Wiki: Link 1: Link 2:

7 7 Besides, you can create a GUI by yourself. You can use the Draw Element tool to create graphic items, the Gallery with graphic images and the Pages Tree where you can add or delete interface pages and popups. There are four types of control items created with the help of the Draw Element tool: Button, Level (slider), Trigger Button, Up/Down Button All of them have different properties which can be set in the Properties tab. The choice of a graphic item type usually depends on the channel type to be bound to the item. Setting of HDL-BUS Pro (Smart-Bus) Connection After creating a necessary number of control items you can start the setting of connection to the HDL-BUS Pro (Smart-Bus) equipment. Connection of a control device to the HDL-BUS Pro (Smart-Bus) bus can be operated through UDP or RS232 protocols. iridium can operate with both types of connection but in the example below we shall examine the most popular connection which uses the UDP protocol. By default connection with HDL-BUS Pro (Smart-Bus) devices is performed through port Connection properties are set in device settings, in the Channel Properties tab in iridium. The connection port and device address in the HDL-BUS Pro (Smart-Bus) bus are indicated here.

8 Channel Setting for the HDL-BUS Pro (Smart-Bus) Protocol 8 After finishing connection setting you can proceed to setting properties for project channels. The bus contains devices with various types and properties, the operation of which is set in a different way. They are relay and dimmer modules, sensors of various types, DLP-panels, curtain drive controllers, etc. Each device type has its control and feedback commands. Setting principles of different devices will be provided in the next sections. HDL-BUS Pro (Smart-Bus) Relay Module Control The following operation codes serve to send commands to HDL-BUS Pro (Smart-Bus) relay modules: Single Channel Control data writing in the relay contact channel, Single Channel Read Actual a request for the relay contact current state Single Channel Read Target a request for the relay contact set value (what state the contact state is aiming for). It is used for reading the future relay state when having an adjusted delay before changing the state. A contact relay state when switching is changed by step from 0 to 100. Actually the same command is used for dimmer control but a relay can take either 0 (OFF) or 100 (ON), there are no intermediate states. Relay Control (Single Channel Control) To control the relay contact (specifying a relay contact state) with two buttons it is necessary to make two channels. The first channel is to lock the relay, the second is to unlock. The following properties are set in the relay control Channel Properties: Type a variable type. Select Signed 32-bit for a relay an information channel - as values 0 and 100 are operated with. Boolean, a logic variable, can be used only when working with 0 and 1.

9 9 Direction a direction of channel data transfer. Select Write for specifying relay value by Button. If it is necessary to display states of the bound variable, you need to bind the Read channel with the way of sending a command (Action): Receive. Two-direction data transfer Read/Write is used for operation with graphic items: Level, Up\Down Button and Trigger Button. When operating with standard Buttons one-direction channels are used (separate channels for reading and writing data about the variable state). Action a way of sending a command: on pressing a button ( Press ), on releasing a button ( Release ), on timer response ( Timer ) and other ways of sending, which are not usually used while operating with a relay). You can select any of the three. Let s select Release. Operation Code it sets a type of the operated variable. As it was mentioned above the Single Channel Control operation code is used. Parameter a number of the device relay contact which state is specified. It can be in the range 1 4, 1 8, 12 etc. depending on the number of relay contacts of a particular controlled relay module. Value a set state of the relay contact. It can take value 0 (to unlock a relay, OFF) or 100 (to lock a relay, ON). Other values are not used for a relay! Option a temporary delay before running a command. It is set when there is a necessity to have a pause before relay response. Zero delay means the immediate response when sending a command. It is set in ms. Repeat a number of command sending repeats. It is used in cases of big losses of UDP connection packets to increase the possibility of delivering a command. In a general way it is enough to send a command once. When all channel properties of Relay On and Relay Off are set, it is necessary to bind them to graphic items. To activate/deactivate a relay the Button item type is used. The type of a graphic item is set in the General tab of the graphic item Properties window ( Properties > General ). The Channel feedback type (for Read/Write and Read channels) which sets the possibility of receiving current channel state data is used for graphic items: sending data and receiving the information from the bus. Momentary and None are used for buttons without feedback ( Write channels). Buttons with the Momentary feedback type change their state on press and return to the previous state on release.. None is used for one-state buttons. To create an item changing the relay state to the opposite one on each pressing you can use the Trigger Button item type (its settings will be described later).

10 Requesting the Relay State (Single Channel Read Target) 10 Single Channel Read Target a request for the relay contact set value. It is used for reading the future relay state the variable is aiming for when having an adjusted delay of state change (it displays its final state). It is recommended to use this type of request to receive states of channels which do not require dynamic images, including relays, dimmers, sensors, etc. This type channels are usually used for forming and sending requests for the device state at the project launch and when jumping between pages and popups. The setting of data receipt at the project launch or when opening a page\popup is made by creating a Write channel. This channel sends a request about relay contacts state at the project launch or when opening an iridium page/popup to the bus (the state of all relay contacts is requested). Request about the relay contacts state at the project launch: The Write channel which sends data to the bus on timer response when starting an iridium project is created. The channel is not bound to graphic items and is activated once, at the project launch, sending a request for receiving data about the state of relays located on the page. Request about the relay contacts state at opening project pages/popups: The Write channel which sends data to the bus on button pressing when jumping between pages/popups (when opening a page/popup) is created. The channel sends a request for receiving data about the state of relays located on the page. It can be used when a long standstill of the system for displaying the actual variable state at opening the page/popup. In both cases the created channel sends a request about receiving the state of all contacts of the selected relay to the HDL-BUS Pro (Smart-Bus) bus. The Write channel is located in the Project Device Tree but it is not bound to graphic items. Data received on the request are displayed by the reading and writing relay state items which were created earlier. Write Channel GUI Read/Write or Read Channel Request for the state States of 8 relay channels HDL bus

11 11 The setting properties of request about the relay contacts state for its displaying on a graphic item are the following: Sending a request for receiving the relay contacts state at the project launch: Type a variable type. Boolean or None are used for sending a request. Direction - a direction of data transfer. Select Write to send a request to the bus. Action: Timer a request for data receipt will be sent in cycles with the interval set in the Timer string (in the example it is set for 0 ms - the data sending is made only once when launching the project). As a reply on the request the relay module sends data on the state of all its contacts to the bus. Thereafter data about the state change will be sent without a request: a relay sends data to the bus automatically. Operation Code Single Channel Read Target is used for requesting a relay state. Parameter the number of a relay contact which a data receipt request is sent for. To receive the states of all contacts set Parameter: 0. Sending a request for receiving the relay contacts state at page/popup opening: Type, Direction similar to the previous case Action a type of response at which the request is sent. Select Press a page/popup is opened on pressing. As a reply on the request the relay module sends data on the state of all its contacts to the bus. Thereafter data about the state change will be sent without a request: a relay sends data to the bus automatically. Operation Code Single Channel Read Target is used. Parameter the number of a relay contact which a data receipt request is sent for. To receive the states of all contacts set Parameter: 0. Channel state change can be displayed by changing an item state for a two-state button - or by displaying numerical value of the channel variable. The channels for sending requests to the bus are not bound to graphic items. To display a value received from the bus on a graphic item, indicate one of the value output templates in the channel text field, for example: $V displaying a current channel value. You can find the table of templates at our Wiki.

12 Requesting the Current Variable Value (Single Channel Read Actual) 12 Single Channel Read Actual a request for the relay contact current state. It serves for dynamic displaying of the variable state change. When changing the state gradually (with the use of the delay set in the Option property) it is not only the final state but all intermediate states of the variable that will be displayed. This operation code can be used for a relay but it is not recommended. Channels using this operation code are set similarly to the ones described in the previous section. Relay Trigger Switch There is often a necessity to change a relay state with one button (and not two buttons sending the opposite values). A Trigger Button graphic item is used to implement a button sending the value opposite to the current channel variable value at each pressing. There have to be a channel sending data to the bus with the Read/Write direction for operation with this item: it has to have a possibility to send data to the bus and receive the current state of a variable (any of the presented below): Its type of response - Action - can be Move, Press or Release. The set channel has to be bound to a graphic item with the following properties:

13 The General tab: 13 Type an item type. Select Trigger Button Trigger Value 1 / Trigger Value 2 values the trigger can take (upper and lower). For a relay they are - OFF: 0 and ON: 100. The Programming tab: Feedback a graphic item feedback type. Select Channel to process the received data and send commands to the bus. This feedback type is obligatory for Trigger Button. Controlling HDL-BUS Pro (Smart-Bus) Dimmers To send commands to HDL-BUS Pro (Smart-Bus) dimmers the same operation codes are used as for relays, namely: Single Channel Control data writing in the dimmer output channel, Single Channel Read Target a request for the dimmer output set value (what state it is aiming for). It is used for reading the future relay state when having an adjusted delay before changing the state. Single Channel Read Actual a request for the dimmer output dynamic state (it is not recommended due to the heavy load of the bus, it is enough to use Single Channel Read Target) Admissible values for a dimmer are in the range from 0 to 100. Dimmer variables can be controlled in a few ways: Control by the Level (slider) graphic item type, Control by Up/Down Button Specifying a set level value by Button (similar to a relay) One of the important conditions when setting a dimmer is receiving its state at the iridium project launch. In order to do this a special channel is formed for reading dimmer output states at the project launch. The channel should not be bound to graphic items.

14 Dimming by the Level (Slider) Item 14 A dimmer can take values in the range from 0 to 100. To regulate the dimmer value in this range a Level (slider) with a slider bar is used; it is one of the graphic item types which can be set in iridium. Variable values can be set and displayed in the given range with the help of Level. For HDL-BUS Pro (Smart- Bus) dimmers the range is from 0 to 100. Setting of operation with a dimmer is performed by the same operation codes which are used for a relay (Single Channel Control, Read Target). But if for relays we set a fixed channel value: 0 or 100, the value for dimmers can change while operating with the project due to regulating the slider bar. A dimmer can only send data to the HDL-BUS Pro (Smart-Bus) bus (Write Channel) or perform a two-direction data exchange send values and display an actual current state (Read/Write Channel): The following properties are set in the dimmer control Channel Properties: Type a variable type. Select Signed 32-bit for a dimmer an information channel - as values 0 and 100 are operated with. Boolean, a logic variable, can be used when working with 0 and 1 only. Direction a direction of channel data transfer. Select Write for setting a dimmer output state without displaying its changes (without reading data about the dimmer state) or Read/Write (recommended) for displaying the dimmer state at any external change (also at the project launch when having a request). Action a way of sending a command. You can select Move as the command is sent when the slider is actuated and also Press (on pressing) or Release (on releasing). Operation Code it sets a type of the operated variable. As it was mentioned above the Single Channel Control operation code is used. Parameter the number of the device dimmer output which state is specified. It depends on the number of outputs of a particular controlled dimmer ( 1 8, 12 or other, 0 is not used for sending). Value a dimmer level (0 100). As it is set by the slider this property is not specified, leave 0.

15 The created channel is bound to a graphic item with the following properties: 15 The General tab: Type an item type: Level (slider) Min Max minimum and maximum values of the Level scale. The other values it takes are limited by these ones. For a HDL-BUS Pro (Smart-Bus) dimmer they are: 0/100. Direction Level positioning: Horizontal or Vertical. The Programming tab: Feedback a graphic item feedback type. It is always Channel for Level. Bind a preset dimmer channel to an item using the Drag&Drop method. It will appear in the Programming tab. Reading the Dimmer State (Single Channel Read Target) As it was mentioned before, to display a dimmer outputs state right after the iridium project launch and also when opening pages/popups, data on which could not be updated because of the standstill of the system, it is necessary to receive data about the dimmer state; and that is impossible without an additional request. To send this request a special channel is created which is not bound to graphic items and operates only at the project launch. You can see its setting below:

16 Request about the dimmer outputs state at the project launch: 16 The Write channel which sends data to the bus on timer response when starting the iridium project is created. The channel is not bound to graphic items and is activated once, at the project launch, sending a request for receiving data about the state of dimmer outputs. Sending a request about the dimmer outputs state at the project launch: Type a variable type. Select Boolean to send a request. Direction a direction of data transfer. Select Write to send the request to the bus. Action: Timer a request for data receipt will be sent in cycles with the interval set in the Timer string (in the example it is set for 0 ms - the data sending is made only once when launching the project). As a reply on the request the dimmer sends data on the state of all its outputs to the bus. Thereafter data about the state change will be sent without a request: a dimmer sends data to the bus automatically. Operation Code Single Channel Read Target is used for requesting a dimmer state. Parameter the number of a dimmer output which a data receipt request is sent for. To receive the states of all outputs set Parameter: 0. Request about the dimmer outputs state at opening project pages/popups: The Write channel which sends data to the bus on button pressing when jumping between pages/popups (when opening a page/popup) is created. The channel sends a request for receiving data about the state of dimmers located on the page. It can be used when a long standstill of the system for displaying the actual variable state at opening the page/popup. Sending a request for receiving the dimmer outputs state at page/popup opening:

17 Type, Direction similar to the previous case 17 Action a type of response at which the request is sent. Select Press a page/popup is opened on pressing. As a reply on the request the dimmer sends data on the state of all its outputs to the bus. Thereafter data about the state change will be sent without a request: a dimmer sends data to the bus automatically. Operation Code Single Channel Read Target is used. Parameter the number of a dimmer output which a data receipt request is sent for. To receive the states of all outputs set Parameter: 0. Channel state change can be displayed by changing an item state for a two-state button - or by displaying numerical value of the channel variable. The channels for sending requests to the bus are not bound to graphic items. To display a value received from the bus on a graphic item, indicate one of the value output templates in the channel text field, for example: $V displaying a current channel value. You can find the table of templates at our Wiki. Controlling a Dimmer by Up/Down Button It is often necessary to change the dimmer value by some fixed value up or down from the current one, for example, to change the dimmer value by 5, 10%, 20% or other. HDL-BUS Pro (Smart-Bus) dimmer values change in the range from 0 to 100. You can set a step of value change within this range and regulate it with two buttons. The same channel is bound to both buttons. Value change direction and change limits are set in the graphic item Properties where the Up/Down Button type is selected which is aimed especially for this type of value regulation. You don t need to create a separate channel for binding to the Up/Down Button type graphic items. You can bind to them the same channel which was set for dimming by Level. Then you can proceed with the setting of graphic items. The properties of Up Button and Down Button are different and are required to set separately:

18 18 The General tab: Type an item type: Up/Down Button Up/Down Value a step of value increase/decrease for a single pressing. To increase the value use positive value, to decrease negative. For example, for Up Button set «10», for Down Button «-10». Max/Min Value maximum or minimum values taken by a variable. For Up Button set dimmer maximum: 100, for Down Button set its minimum: 0. The limits have to correspond with the actual extreme values of the variable or can be less to make a cut-off. The Programming tab: Feedback a graphic item feedback type. It is always Channel Specifying a Fixed Level Value by Button You can set the level value in the range of by Button. The standard dimmer channel, which setting was performed for Level, is used for that. The Single Channel Control operation code and the Button type graphic item are used. Value the value, the dimmer has to be set up by Button.

19 Operation with HDL-BUS Pro (Smart-Bus) Sensors 19 In iridium you can receive states of 8 in 1, 10 in 1 sensors, 4-contact input modules, IR motion sensors, multifunctional sensors, etc. A special request which is sent to the HDL-BUS Pro (Smart-Bus) bus is used to receive outputs states at the project launch. Besides the request for the state you can send ir commands through 8 in 1 sensors or lock/unlock sensor operation (lock/unlock option for some sensor properties). Requests for the State of HDL-BUS Pro (Smart-Bus) Sensor Outputs at the Project Launch To display the correct sensor outputs state right after the iridium project launch it is necessary to receive data about its state at the project launch; and that is impossible without an additional request. To send this request a special channel is created which is not bound to graphic items and operates only once, at the project launch. You can see its setting below: Type a variable type. Select Boolean for requesting the state. Direction a direction of data transfer. Select Write to send a request for receiving data of the sensor state in the bus. Action a way of data sending. Select Timer a request will be sent at a given time. Timer, ms the time for sending a command is set. Set 0 the command is sent right after the project launch. Operation Code the Motion Sensor Read Status operation code is used for requesting a current state of sensor contacts. Parameter the number of the sensor output which state is requested. Usually the states of all outputs are requested, so set - 0. Repeat a number of command repeats. In a general way a command is sent once. The channel should not be bound to graphic items. It is located unbound in the Project Device Tree.

20 Displaying Outputs States of an HDL-BUS Pro (Smart-Bus) Sensor 20 It is necessary to create the channel which receives and displays data coming from the bus about output state change to display the state of one of the sensor outputs. Such channel type only reads data and doesn t send auto requests about a bus devices state. The request is formed only once, when launching the project or when it is necessary to request the state at page/popup opening. Thereafter a device automatically sends data about its state to the bus. Type a variable type. Select Boolean for sensor outputs taking two states: 0 or 1. Direction a direction of data transfer. Select Read for a channel which receives data from the bus and does not send any data back. Action the event at which a channel responds. Select Receive to receive channel state data. Operation Code the Motion Sensor Read Status operation code is used for receiving data about a current state of sensor outputs. Parameter the number of the sensor output which state is requested. For example, set the first sensor output - 1. The channel with such settings is bound to the Button type graphic item with the Channel or None feedback type. A template of value output on graphic items (for example $V, see table of templates) or two states which can also display a sensor output state are selected for the channel.

21 Sending IR commands by HDL-BUS Pro (Smart-Bus) Sensors 21 To send IR commands through emitters which some HDL-BUS Pro (Smart-Bus) sensors have the Universal Control operation code is used which allows you to create a selection command and send an IR command which was previously preset for the sensor. You can see Channel properties settings below: Type a variable type. Select Boolean - for sending value 1 or Signed 32-bit - for sending value 255 Action the event at which a channel responds. Select, for example, Press on pressing the button. Operation Code Universal Control is used to send IR commands. Parameter the number of the IR command which is to be sent. Commands are set beforehand. Their numbers are given to them during the programming of HDL-BUS Pro (Smart-Bus) automation system. Value a signal level. It is necessary to set 1 sending of IR commands (Boolean) or 255 (Siged 32-bit). The command is bound to the Button type graphic item with the None or Momentary feedback type. HDL-BUS Pro (Smart-Bus) Sensor Lock There is a lock option for some sensors (e.g. «8 в 1»). For example, you can lock motion and illumination sensors, operation of dry contact or other external parameter elements of sensors. Such lock is not applicable for sending IR commands. Correspondence of outputs to the parameters actuating sensors can be found in sensor properties in the HDL-BUS Pro (Smart-Bus) configuration program. Settings of a lock command are the following: Type, Direction the same as for sending IR commands. Action the event at which a channel responds. Select Press (on pressing) to send commands.

22 Operation Code Universal Control is used to send lock commands. 22 Parameter a unique property which a sensor lock command is sent at. Example: select 255 for the 8 in 1 motion sensor lock. Parameter values for this sensor lie in the range from 250 to 255. Value a sensor state. Set 0 to lock the sensor or 1 to unlock the sensor. When selecting the Write data transfer direction the command is bound to the Button type graphic item with the None or Momentary feedback type. When selecting the Read/Write data transfer direction you can bind the channel to the Trigger button type graphic item with the following properties: The General tab: Type an item type. Select Trigger Button Value 1 / Value 2 the initial and final trigger values: 0 and 1 The Programming tab: Feedback a feedback type. Select Channel Controlling Motorized Curtains, Shutters and Roller Blinds Controllers Motorized curtain controllers SB-DN-2Motor (a relay) are meant to control any engines which have two-way direction, namely curtains, shutters, screens, gates, elevators, swimming pool coverage, etc. HDL- BUS Pro (Smart-Bus) SB-DN-2Motor provides control of engines which have protection from simultaneous activation of moving in both directions and with a programmable delay of switching the direction. Two operation codes are used for operation with controllers: Curtain Control setting a controller switch state Curtain Read Status receiving a switch state (1 activated in the straight direction, 2 activated in the opposite direction, 0 - stop) The control is usually performed by three buttons: Up, Down and Stop. It can also be performed by two buttons: one Trigger Button for switching the directions and one Stop button.

23 State Setting of a Motorized Curtains Controller Switch 23 Let s create three buttons to control SB-DN-2Motor controller switch: Type a variable type. The information Signed 32-bit is used for a switch which takes three states: 0, 1 and 2. Direction a direction of data transfer. Select Write for sending data to the bus. Action an event of data sending. You can select Press or Release to set a switch state with a button. For example, let s select Release. Operation Code Curtain Control is used to send a switch state. Parameter the number of the switch (the relay group), which state is necessary to set. SB-DN-2Motor controller consists of two relay groups. For example, let s set the operation with the first group. Parameter: 1 Value a switch state which is necessary to set. Three values are used here: 1 straight direction (Up), 2 opposite direction (Down), 0 stop (Stop). The created channels are bound to the Button type graphic item with the None or Momentary feedback type.

24 24 Additional information. There is a possibility of creating a group of three interdependent buttons which enable the visualization algorithm at which when one button is activated the others are deactivated. It allows you to display the current state of the curtain controller switch without creating a separate window. You can use one of the channels specifying the curtain controller state (with the Read/Write type of direction) to create the group of such items. The channel with these properties is bound to three Button type graphic items with two states and the following properties: The feedback type for all items is Channel. The operation principle of such trigger lies in the fact that it is activated only if the state of the variable, which is bound to it and received from the channel, equals to the value limited by the upper and lower state of the trigger (i.e. it is a fixed value). If the channel variable takes the value which is different from the set range the item cannot be activated. Such setting excludes the simultaneous activity of several states of the motorized curtain controller switch and enables the displaying of its state even at the external change (e.g. from another panel).

25 Requesting the Controller Switch State 25 It is necessary to receive the current state of a motorized curtains controller at the iridium project launch just like for the other devices. A channel of data request on timer response, which is not bound to other channels and is activated only once (at launch), is used for it. Thereafter a controller automatically sends its state to the bus. The request is also used sometimes when opening pages/popups, data on which could not be updated because of the standstill of the system. To send this request a special channel is created which is not bound to graphic items and operates only at the project launch. Request about the switch state at the project launch: The Write channel which sends data to the bus on timer response when starting the iridium project is created. The channel is not bound to graphic items and is activated once, at the project launch, sending a request for receiving data about the controller switch state. Type a variable type. Select Boolean to send a request. Direction a direction of data transfer. Select Write to send the request to the bus. Action: Timer a request for data receipt will be sent in cycles with the interval set in the Timer string (in the example it is set for 0 ms - the data sending is made only once when launching the project). As a reply on the request the controller sends data on the state of all its switches to the bus. Thereafter data about the state change will be sent without a request: a controller sends data to the bus automatically. Operation Code Curtain Read Status is used for requesting a state. Parameter the number of a switch which a data receipt request is sent for. The state of each switch is requested separately. The general request is not sent. Request about the switch state at opening project pages/popups: The Write channel which sends data to the bus on button pressing when jumping between pages/popups (when opening a page/popup) is created. The channel sends a request for receiving data about the state of controller switches located on the page. It can be used when a long standstill of the system for displaying the actual variable state at opening the page/popup.

26 26 Type, Direction similar to the previous case Action a type of response at which the request is sent. Select Press a page/popup is opened on pressing. As a reply on the request the controller sends data on the state of all its switches to the bus. Thereafter data about the state change will be sent without a request: a controller sends data to the bus automatically. Operation Code Curtain Read Status is used for requesting a state. Parameter the number of a switch which a data receipt request is sent for. The state of each switch is requested separately. The general request is not sent. Channel state change can be displayed by changing an item state for a two-state button - or by displaying numerical value of the channel variable. The channels for sending requests to the bus are not bound to graphic items. To display a value received from the bus on a graphic item, indicate one of the value output templates in the channel text field, for example: $V displaying a current channel value. You can find the table of templates at our Wiki. Displaying a Curtain Controller Switch State The Curtain Read Status operation code is used to display a controller switch state. Displaying of a controller switch state can be made on the Button type graphic item with a template of value output on a graphic item (See templates at Wiki). Type a variable type. The information Signed 32-bit channel is used for a switch which takes three states: 0, 1 and 2. Direction a direction of data transfer. Select Read for the channel which receives data from the bus but does not send any data back.

27 Action an event of data sending. Select Receive to process the coming data. 27 Operation Code Curtain Read Status is used to send a switch state. Parameter the number of the switch (relay group), which state is necessary to set. SB-DN-2Motor controller consists of two relay groups. Parameter: 1 and 2 Setting of a button for displaying a channel state is made by selecting the Button type and the None feedback type as there is no need to send data and switch a channel state. The button can have a single state only. Additional Variant of Displaying a Switch State: It is the output of the switch value on the Multistate Level graphic item with three images, which reflect the channel variable state: 0, 1 or 2. The slider value range is 0 2, each value corresponds to its own image. Bind a channel reading data about a switch state (its settings are described in the previous section) to a graphic item and set the item as follows: 1. Create a graphic item with three states. 2. Select the Multistate Level item type 3. Set the Level value change range: Min: 0, Max: Select the way of actuating the item: Hit: Display Only 5. Set the image for each Level state (for example, arrows for driver moving and a stop sign for a standstill) 6. Bind it to a data reading channel

28 The item settings are as follows: 28 Item states: State 1, corresponds to Level 0 (Stop) State 2, corresponds to Level 1 (Up) State 3, corresponds to Level 2 (Down) Trigger Switch of Driver Direction The Trigger Button graphic item type is used to switch the direction of driver operation with a single button. The button for a driver stop is set separately. Trigger Button should have a possibility of two-way data exchange with the bus so it could always have data about the current variable state which are necessary for sending a state change command. The Trigger Button channels are set as for the previous case (an information channel of setting the switch state). You can use straight or opposite direction channels with the Read/Write direction of data transfer:

29 Trigger Button has to perform the switch from the straight direction (Value: 1) to the opposite one (Value: 2). Its setting is as follows: 29 Select the Trigger Button type and Trigger Value: 1 and 2 (switching from the straight to the opposite direction). If you set 1 and 0 the trigger will switch from the straight direction to the standstill; if 2 and 0 - from the opposite direction to the standstill. Thus, with such a graphic item type you can implement various control operations of the SB-DN-2Motor controller. Interaction with HDL-BUS Pro (Smart-Bus) DLP-panels HDL-BUS Pro (Smart-Bus) keyboard DLP-panels can control a range of bus devices. iridium allows you to set and send commands for operation with floor heating, conditioners and temperature sensors through DLP-panels and also to receive data from them (for example, temperature value and status). The following operation codes are used for operation with the DLP-panels: Panel Control sending one of the available DLP-panel commands Panel Read Status receiving a state of one of panel properties Floor Heating Read State receiving a state of floor heating properties Floor Heating Set State commands for floor heating control External Temperature Read receiving a temperature string from the floor heating sensor Read Temperature receiving data from the built-in temperature sensor of the DLP-panel All operation codes are used for creating channels for interaction with DLP-panels. They have different settings which should be considered when setting the connection to the HDL-BUS Pro (Smart-Bus) bus. The principles of channel configuration for actuating different bus properties are presented below.

30 Description of Floor Heating Commands Operation 30 These commands have one peculiar feature which is different from commands for operation with other devices: for proper functioning of floor heating commands in iridium the project MUST contain all control properties (i.e. channels) which can be actuated. It is necessary to have the following commands in the project: 1. Temperature Mode: displaying temperature in the Celsius or Fahrenheit scale 2. Sampling Temperature current floor heating temperature value. 3. Floor Heating Switch switching on/off the floor heating 4. Mode Select selecting the mode for floor heating operation 5. Common Mode Temperature selecting a temperature value in the Common mode 6. Day Mode Temperature - selecting a temperature value in the Day mode 7. Night Mode Temperature - selecting a temperature value in the Night mode 8. Away Mode Temperature - selecting a temperature value in the Away mode Presence of all these channels is mandatory, absence of one of them leads to resetting of the corresponding property to zero when sending the other command which uses the «Floor Heating Set State» operation code. It is due to the peculiar feature of making floor heating commands all properties are sent in one string, while data on its content always has to be in the project:

31 Floor Heating Commands and Their Setting 31 The required floor heating commands are set as follows: Type a variable type. Select Boolean - a logic variable - for «Temperature Mode» и «Sampling Temperature» as there are only two states possible. Select Signed 32-bit for other properties which values can be in different ranges. Direction a direction of data transfer. The «Temperature Mode» and «Sampling Temperature» commands use Read as they are responsible only for receiving the current floor heating state without sending data to the bus. For the rest commands select Read/Write for a possibility not only to send a command but also to display data about the current variable state. Action an event of data sending which can be done on press or on release. Receive is used for the commands which only receive data from the bus («Temperature Mode» and «Sampling Temperature»). The data sending channels can use Press or Release (sending on press or on release). Operation Code Floor Heating Set State is used for sending floor heating commands to the bus Parameter a sent floor heating property. Possible properties lie in the range from 1 to 8 in the following sequence: Temperature Mode Parameter: 1 Sampling Temperature Parameter: 2

32 Floor Heating Switch Parameter: 3 Mode Select Parameter: 4 Common Mode Tepmerature Parameter: 5 Day Mode Temperature Parameter: 6 Night Mode Temperature Parameter: 7 Away Mode Temperature Parameter: 8 32 Value a sent value of a property. It can be different and depends on the property. For the «Temperature Mode» and «Sampling Temperature» commands we leave the level value which equals to O as for the data reading channels. The value of the «Floor Heating Switch» can be 0 or 1. The switch between values can be set by two buttons with 1 and 0 values or by the trigger. «Mode Select» can take values from 1 to 4 which correspond to different operation modes. The switch between them is set by four buttons with the double of the channel taking values from 1 to 4 or by triggers set in a particular way which will use one channel with Value: 0. The values of temperature modes are set here by Level with the range from 5 to 35 С. When setting by Level you can leave Value: 0, when setting by Button the Valueis set in the range from 5 to 35. The setting of graphic items for their binding to the channels of floor heating control: 1. To bind the Temperature Mode channel, the Button type graphic item with the «Channel» feedback type is used. It ensures the change of the item state for displaying temperature in the Celsius or Fahrenheit scale when receiving 0 or 1 value from the bus. State 1: the Celsius scale, State 1: the Fahrenheit scale.

33 2. To bind the Sampling Temperature channel, the Button type graphic item with the «None» feedback type and the $V template of output are used (see the table of templates at our Wiki). It ensures the display of the current variable value The Floor Heating Switch channel is bound to the Trigger Button type graphic item for switching states to the opposite at each pressing. The channel should have the Read/Write direction of data transfer. Set initial and final values of the trigger: 0 and 1. Always use the Channel» feedback type for Trigger Button. 4. Bind the «Mode Select» channel to all buttons displaying the current mode of floor heating. The difference in setting will be seen on the graphic items level.

34 34 The feedback type of all items is Channel. The operation principle of such a trigger lies in the fact that it is activated only if the state of the variable, which is bound to it and received from the channel, equals to the value limited by the upper and lower state of the trigger (i.e. it is a fixed value). If the channel variable takes the value which is different from the set range the item cannot be activated. Such setting excludes the simultaneous activity of several modes of the floor heating operation and enables the displaying of its state even at the external change (e.g. from another panel).common Mode corresponds to level 1, Day Mode - to 2, Night Mode - to 3, Away Mode - to 4. Thus the trigger is always active as long as it takes the fixed value which is set by the trigger level. It will not be active with any other value. If one of the floor heating operation modes is selected the rest modes cannot be activated. They are deactivated automatically. 5. The display of the selected operation mode of floor heating can be performed by the «Multistate Level» type graphic item. Each mode described by values from 1 to 4 corresponds to the state of the «Multistate Level» item for displaying the current mode. As the mode can be on the range from 1 to 4, the range of minimum and maximum level value also has to be equal to 4: i.e. from 1 to 4 or from 0 to 3. Then when receiving a variable from

35 35 the channel the Multistate Level takes the corresponding state. In the General Properties tab for the item it is necessary to set Display Only to avoid the possibility of pressing which is not provided by the channel type and item type. 6. Channels of setting temperature in different modes are bound to the «Level» type graphic item with the Channel feedback type and value range from 5 to 35. The range cannot be wider as the values are limited by the controller capabilities. If it is necessary the range can be narrowed. At that the setting of graphic items for operation with floor heating channels is completed.

36 Controlling Air Conditioners and DLP-panel Properties 36 The following operation codes are used to operate the main properties of the DLP-panels: Panel Control sending one of the possible DLP-panel commands Panel Read Status receiving a panel property state There are 18 properties which can be controlled by the Panel Control operation code. Parameter Command Status (1В) 0 Invalid invalid 1 IR Function 0: off ; 1: on 2 Lock Key of Panel 0: off ; 1: on 3 AC Power 0: off ; 1: on 4 Cooling Temp 0 ~ 84 5 Fan Speed 0: auto; 1: high; 2: medium; 3: low 6 AC Mode 0: cooling; 1: Heating; 2: Fan ; 3: auto; Dehumidfy 7 Heating Temp 0 ~ 84 8 Auto Temp 0 ~ 84 9 Rise Temp Decrease Temp LCD Backlight Status 0: off ; 1: on 12 AC Lock 0: off ; 1: on 13 Backlight 0 ~ Status Light 0 ~ Shield Button 1 ~ Shield Page 1 ~ 4 17 Control Button Status 0: off ; 1: on 18 Control Button 1 ~ 16 On the whole, the principles of channel setting to control the above mentioned 18 properties are identical and do not require a separate setting. Channel setting for controlling different variables mainly depends on the selected way of regulation. The channels can be set so as to be bound to Buttons, Trigger Buttons, Levels and Multistate Levels. It influences the channel properties and their initial settings. Setting of Air Conditioner Control: 1. The Panel Control operation code to control logic variables (taking values 1 and 0): commands for switching on/off a conditioner, sending IR commands, key lock and other variables operating with values 1 or 0 (parameters: 1, 2, 3, 11, 12, 17).

37 37 Type a variable type. Select Boolean a logic variable. Direction a direction of data transfer. Select Read/Write for a channel sending data to the HDL-BUS Pro (Smart-Bus) bus with a possibility to display changing of the variable state. Action an event of data sending which can be done on pressing the button - Press or on its releasing - Release. Operation Code Panel Control is used for operation with air conditioners and DLP-panel properties. Parameter a number of the panel property which status is changed. There are 18 properties on the whole; zero value is not used. Logic variables: 1, 2, 3, 11, 12, 17. Value a set value. For logic variables two values are possible: 0 or 1. The variable set like this should be bound to Button or Trigger Button depending on your requirements. The Trigger Button graphic item with two states and two possible values: 1 and 0.

38 38 The Button graphic item with two states (usually the text is the same, state switch is displayed by image effects): To control a logic variable you need two Button items: one with Value: 1 for switching on and the other with Value: 0 for switching off. 2. Control of information variables with a narrow range (taking values within the range from 0 to 3, from 1 to 4, etc.),for example, for setting air conditioner operation mode. Panel Control operation code and Buttons or Trigger Buttons with special settings are used. Parameters:5,6 and 16. Type a variable type. Signed 32-bit - an information variable. Direction a direction of data transfer. Select Read/Write for a channel which has two-way data exchange with the bus. Action an event of data sending which can be done on pressing the button - Press or on its releasing - Release. Operation Code Panel Control is used for operation with air conditioners and DLP-panel properties. Parameter a number of the panel property which status is changed. There are 18 properties on the whole; zero value is not used. Information variables with a narrow value range: Parameter 5, 6 and 16. Value a set value of the channel variable. Select one of the range values for binding to Button and 0 for binding to Trigger Button with special settings.

39 Trigger button for binding to this type channel is set as follows: 39 The feedback type of all items is Channel. The operation principle of such a trigger lies in the fact that it is activated only if the state of the variable, which is bound to it and received from the channel, equals to the value limited by the upper and lower state of the trigger (i.e. it is a fixed value). If the channel variable takes the value which is different from the set range the item cannot be activated. Such setting excludes the simultaneous activity of several modes of air conditioner operation and enables the displaying of its state even at the external change (e.g. from another panel). The «Cooling» mode corresponds to level 0, the «Heating» mode - to 1, the «Fan» mode to 2, the «Auto» mode to 3. Thus the trigger is always active as long as it takes the fixed value which is set by the trigger level. It will not be active with any other value. If one of the air conditioner operation modes is selected the rest modes cannot be activated. They are deactivated automatically.

40 40 3. Control of information variables with a wide range of value change is performed by the Panel Control operation code and Level graphic items. Such are the rest parameters: 4, 7, 8, 9, 10, 13, 14, 15, 18 mainly used for regulation of temperature settings. Type a variable type. Signed 32-bit - an information variable. Direction a direction of data transfer. Select Read/Write for a two way data exchange with the bus. Action an event of data sending which can be done on pressing the button - Press or on its releasing - Release. Operation Code Panel Control is used for operation with air conditioners and DLP-panel properties. Parameter a number of the panel property which status is changed. There are 18 properties on the whole; zero value is not used. Information variables controlled by Level: 4, 7, 8, 9, 10, 13, 14, 15, 18. Value a set value of the channel variable. Leave 0 as the value is regulated by Level. Graphic item properties for binding to the set channel: The upper and lower value level values are limited by the change limits of the control value. The change limits cannot be wider than the tolerable ones but they can be narrowed if it is necessary to make a cutoff.

41 Requests for the DLP-panel Properties State at the Project Launch 41 It is recommended to use channels for the state request for data from the HDL-BUS Pro (Smart-Bus) bus to receive the actual property state at the project launch. The receipt of the state of all DLP-panel properties is impossible. That is why it is necessary to create separate channels for receiving data on each property which needs to be requested at the project launch. The settings of these channels are identical: Type a variable type. Select Boolean a logic variable as the request sending does not depend on data coming from the bus. Direction a direction of data transfer. Select Write for a channel sending the request to the HDL-BUS Pro (Smart-Bus) bus. Action an event of data sending. The sending is made on timer response at the project launch. Timer, ms time of sending a command by timer. Select 0 ms a command is sent immediately at the project launch. Operation Code Panel Read Status is used to send a request for the DLP-panel property state Parameter a number of the panel property which status is required to be displayed. There are 18 properties on the whole; zero value is not used. Displaying a DLP-panel Properties State To display the DLP-panel properties received at the system launch and also its further changes you can use the channels which were set earlier and use the Read/Write direction of data transfer for a two way data exchange with the bus. The channels receive data from the bus and display the state of bus variables on graphic items. It gives the opportunity to display the state with the same items which are used for sending data to the HDL-BUS Pro (Smart-Bus) bus without creating new data reading channels.

42 Requests for Temperature from DLP-panel Sensors 42 To receive temperature from the built-in DLP-panel temperature sensor and also from the floor heating sensor (data are received as float) the following operation codes are used: External Temperature Read receiving temperature from the floor heating sensor Read Temperature receiving data from the built-in DLP-panel temperature sensor Request for temperature from a built-in DLP-panel sensor (the Read Temperature operation code) is made only at the project launch. Thereafter the sensor automatically sends data to the bus: Type a variable type. Select Boolean for sending a request to the bus. Direction a direction of data transfer. Select Read/Write for the channel which is bound to the button and displays values received from the bus. Write is used for sending a request to the bus at the project launch. Read is used for displaying data. Action an event of channel response. Select Timer for requesting the state at the project launch. The timer response interval is set in milliseconds, set as the compulsory request will be sent at the project launch and then each 10 seconds. Operation Code Read Temperature is used to request and display temperature from the DLP-panel. Parameter a parameter for temperature request. Always set 1. The channel for requesting the temperature sensor is bound to the Button type graphic item with one state, the template of value output and the None feedback type:

43 43 Request for temperature from a floor heating sensor (the External Temperature Read operation code) is made similarly: The External Temperature Read operation code is used for requesting and displaying temperature from the external DLP-panel sensor. The requested Parameter is 1. The request is also made on timer response at the project launch. Thereafter the sensor automatically sends data to the bus. The command is bound to the Button type graphic item with one state and the None feedback type. It is necessary to indicate the $F3 template of value output with three symbols after the point into the text field of a graphic item to display temperature with high precision. It is necessary because the floor heating sensor displays temperature in the float format with accuracy to several symbols.

44 Activation of Scenes and Sequences You can activate Scene Control commands by iridium. The channel of scene activation is set as follows: Type a variable type. Select Boolean for sending a command to the bus. Direction a direction of data transfer. Select Write as the channel is responsible for sending the scene command only. Action an event at which the channel responds. Select Press (on pressing) to send commands. Operation Code Select Scene Control to activate scenes. Parameter a number of the area which the scene is activated for. Value a number of the selected scene. 2. You can activate Sequence Control commands by iridium. The channel of sequence activation is set as follows: Type a variable type. Select Boolean for sending a command to the bus. Direction a direction of data transfer. Select Write as the channel is responsible for sending the sequence command only. Action an event at which the channel responds. Select Press (on pressing) to send commands. Operation Code Select Sequence Control to activate sequence. Parameter a number of the area which the sequence is activated for. Value a number of the selected sequence. The command is bound to the Button graphic item with one or several states and None or Momentary feedback type.

45 Receipt of Status of Various Variables at Project Launch 45 In order to display the status of devices of the HDL-BUS Pro (Smart-Bus) bus at the launch of iridium project, it is necessary to create special purpose data request channels for each device which has its own unique Subnet ID / Device ID. Such special purpose channels have some peculiar features and are used for: Requesting states of relay modules, dimmers, curtain controllers, etc. at the launch of iridium project for their further displaying on graphic items; Cyclic requesting of states of the devices which do not send their states automatically: requests of temperature and states of sensors and input modules, Z-Audio and etc. Channels - timers of state request are used together with channels reading (receiving and displaying) data about the variable state: Graphic Elements (GUI) Channels (Project Device Tree) Write [ Timer ] 1 Button [ Channel ] Button [ Channel ] 2 Read [ Receive ] 3 Read/Write [ Timer ] HDL bus According to the scheme channel (1) sends the request for the current state of a variable to the bus. In answer to that the bus sends the requested data which is received by the channel set for monitoring the state changes of the selected variable. Channel (1) is not bound to graphic items and is left in the Channel Tree. Channel (2) is bound to a graphic item and allows you to display the values received from the bus. Channel (3) includes functions of channels (1) and (2): it sends requests to the HDL-BUS Pro (Smart- Bus) bus and receives and displays data on graphic items. Channel (3) in contrast to channel (1) must be bound to a graphic item which the received values should be displayed on. At iridium launch you can send a number of requests in answer to which the selected devices of the bus give information about their state at iridium launch. After the initial request the majority of devices send information about the change of their status automatically. But some devices of the HDL-BUS Pro (Smart-Bus) bus do not send information about the change of their status without request even at its change (sensors, input modules, ) for such devices the cyclic request is used.

46 1. Example of a single request for the state of the bus devices at iridium Client launch 46 1 a single request (Timer: 0) for the state of all outputs (Parameter: 0) of 8 in 1 sensors; 2 a single request (Timer: 0) for temperature state (Parameter: 1) of DLP panels. In contrast to the rest three channels the request with Read/Write direction is bound to the graphic item which the received temperature will be displayed on; 3 a single request (Timer: 0) for the state of all dimmer outputs (Parameter: 0); 4 a single request (Timer: 0) for presence of AC power of the DLP panel(parameter: 3). General properties of commands of the single request for the variable state at iridium launch: Type a variable type. Select Boolean for sending a request to the device. Direction a direction of data transfer. Select Write to send the command to the bus. Action an event of data sending. Select Timer for requesting the state at project launch and indicate 0 interval in the Timer, ms field. As a reply on the request the module will send data about the state of its outputs. Operation Code it depends on the type of the polled module; Parameter a number of output (contact) which state is requested. To receive states of ALL module contacts indicate Parameter: 0 (the request of all outputs is not supported by all devices, for example, it is necessary to request each parameter separately for DLP panels). Timer channels are not bound to graphic items and must be in Device Tree. Channels with the Read direction of data transfer and the Receive event of data sending which are connected to the same variables as timers are responsible for receiving and displaying data received at the start request of timers. Reading channels should be bound to graphic items; usually the items with templates of value output are used.

47 2. Examples of cyclic request of the device in the HDL-BUS Pro (Smart-Bus) bus 47 Here we present the settings for cyclic request of devices which do not send information about the change of their status at its change automatically: requests of temperature from DLP panels, requests for states of sensors and input modules, requests for Z-Audio properties and etc. 1 a cyclic request (Timer: 5000) for Z-Audio status; 2 a cyclic request (Timer: 5000)for the state of all (Parameter: 0) contacts of SB-DRY-4Z sensors; 3 - a cyclic request (Timer: 10000) for temperature value of DLP panels. General properties of commands of cyclic request for variable states: Type a variable type. Select Boolean for sending a request to the device; Direction a direction of data transfer. Select Write to send the command to the bus; Action an event of data sending. Select Timer for requesting the state at the project launch and indicate an interval between the requests in the Timer, ms field. As a reply on the request the module will send data about the state of its outputs. Operation Code it depends on the type of the polled module; Parameter a number of output (contact) which state is requested. To receive states of ALL module contacts indicate Parameter: 0 (the request of all outputs is not supported by all devices, for example, it is necessary to request each parameter separately for DLP panels). Timer channels are not bound to graphic items and they must be in Device Tree. Channels with the Read direction of data transfer and the Receive event of data sending which are connected to the same variables as timers are responsible for receiving and displaying data received at the start request of timers. Reading channels should be bound to graphic items; usually the items with templates of value output are used.

48 Optimization of iridium Projects for HDL-BUS Pro (Smart-Bus) 48 To receive the initial state of bus variables, iridium Client sends requests at its launch. Corresponding devices of the bus send data about their state back to it. When there are cyclic requests which are being processed and a considerable number of devices in the subnet, the HDL-BUS Pro (Smart-Bus) bus may have problems with processing of the transferred data. In this case there may be undelivered commands and partial loss of feedback. If there is high probability of the bus overload, it is necessary to take measures for optimization of your iridium project, namely decrease of the peak load in the bus (the number of simultaneous requests (including cyclic ones)). When using a standard bus request procedure, state requests are sent at the iridium project launch (Timer: 0). Thus the peak load falls on the launch time or the time of reconnection of iridium Client to the bus. The efficient way of decreasing the peak load is cancellation of sending requests to all bus devices at the project launch. A project can be optimized by changing the way of sending requests for receiving states of devices and variables. Requests should be sent not at the project launch (as in a standard way) but at jumping to a page containing items, which display the state of the requested device. At scanning of the HDL-BUS Pro (Smart-Bus) network channels of state requests have the preset event of data sending - Action: Timer (Timer: 0) - for requesting data at connection of Client to the bus. To optimize the project requests about states of separate devices can be sent at jumping to the page containing the items, which display their states. For the request at page jumping, change the event of sending a command - Action: Press and bind the request channel to Button which performs jumping to the required page. The simplified diagram of request allocation looks as follows: Project Start Page. Contains information about Devices Start Page Button 1 Request Page 1 open On Press: Request of Device 4 Page 1 Contains information about Device 4 On Timer: 0 Request of Devices Button 2 Page 2 open Page 2 Contains information about Device 5 Request On Press: Request of Device 5

49 49 Thus, you can considerably decrease the load on the bus at the iridium project launch (at connection of iridium Client to the HDL-BUS Pro (Smart-Bus) bus). The number of data which are sent simultaneously will decrease and the probability of losses will be reduced. Recommendations on project setting: Reduce the number of mass requests about variables states when possible. Such requests activate devices to send state data of a big number of outputs. If it is necessary to display the state of several device outputs, there is no need to send request about all outputs (especially if a device has a considerable number of outputs). Make separate state requests for each required output. Request variable states at jumping to a page containing data about the requested device. It will enable you to receive actual information about a device state and decrease the load on the bus. If the cyclic request of a device is required (e.g. for receiving temperature or dynamic status), maximize the time of the request cycle to decrease the load on the bus as cyclic requests can considerably overload it. If a request of any variable is sent more often than once a second, the bus can be overloaded. It is recommended to send requests for temperature once in 5-10 seconds. Do not exceed the recommended number of HDL-BUS Pro (Smart-Bus) devices in one subnet to avoid a big volume of transferred data which can influence the bus performance and possibility of delivery. There is one more way to optimize your projects so they could be launched and uploaded at faster speed: to reduce the size of the project file. iridium GUI Editor has a tool for deleting unused images and sounds (when working with images there are files which were added to Project Gallery, then changed or deleted and actually they are not used in the project). Unused files are converted together with the used ones, so it is recommended to delete the unused images from time to time. The Delete Unused Files tool is located on the GUI Editor toolbar and looks as follows: * Do not use the Delete Unused Files tool to remove unused channels as it can delete channels which are not bound to graphic items including the channels of data request at Client launch.

50 Connection to the Bus over the Internet: iridium Gate 50 iridium Gate an application, which allows you to establish connection with the HDL-BUS Pro (Smart-Bus) bus over the Internet. It also enables the concurrent connection of numerous Clients (control panels) to the bus. Features of the iridium Gate application for HDL-BUS Pro (Smart-Bus): 1. Connection of several clients to the HDL-BUS Pro (Smart-Bus) bus which does not support multiclient connection in usual conditions; 2. 3G or Wi-fi connection of Clients to equipment connected to PC through RS232 (via COM-port ): TCP to Serial conversion for HDL-BUS Pro (Smart-Bus); 3. Fixing the connection failure of Clients to the bus equipment over the external network (via the Internet). The failure may be caused by operating with the bus through UDP and limitations of UDPport forwarding on the router for connection to the local network externally. Interface of the iridium Gate application: Adding a new Gate (a gateway for data converting and transferring ) Setting of the added Gate Enabling Gate (disabled Gate does not transfer data) Disabling Gate Deleting Gate Creation and setting of Gate for operation with HDL-BUS Pro (Smart-Bus): Create a new gateway for data converting and transferring from the Extranet or Intranet to the HDL-BUS Pro (Smart-Bus) bus by clicking the «Add Gate» button. You can set Gate in several ways. Different settings are used when operating through UDP and RS232: Name Gate name, random Comment Gate description, if required

51 51 Server section: Type a Gate type. Select SmartBus to work with the bus equipment Transport a type of transport which will be used for connection of Clients (control panels with iridium) to Gate. TCP is always used. Port external Gate TCP-port, which iridium HDL-BUS Pro (Smart-Bus) Clients are connected to. It can be set at random Max Connection maximum number of Clients connected to Gate concurrently. It is set at random (do not forget that an abundant number of Clients can overload the bus) Device section: Type a data format which they will be transferred to the bus through Gate in. Data are not converted For HDL-BUS Pro (Smart-Bus); the type of incoming and outgoing data is not altered. Transport a type of transport which will be used for transferring data to the HDL-BUS Pro (Smart-Bus) bus. There are two possible variants: UDP (when Ethernet gateway is used for connection with control panels) and RS232 (when RS232 gateway is used). For SmartBus UDP: Port a UDP-port which is used by HDL-BUS Pro (Smart-Bus) to exchange data with external devices For SmartBus Serial: Port a СОМ-port for connection to the gateway; and its properties: Baudrate, Databits and Parity Time Out sampling frequency of the COM-port, leave 0 by default

52 52 When Gate is set, save the settings. It will have the following view in the iridium Gate application window: Gate enabling/disabling is performed through the application menu (menu buttons on the left). If you want to connect Clients, Gate has to be enabled. The number of the Clients connected at the moment is displayed in the Client window. When the iridium Gate application is set, it is necessary to create or customise the iridium GUI Editor project for HDL-BUS Pro (Smart-Bus), which is aimed for connection with the bus devices. If the project is not set properly it cannot be connected to the iridium Gate application. Setting of the iridium GUI Editor Project for Connection to Gate If you already have the project made for operation with the devices of the HDL-BUS Pro (Smart-Bus) bus and you need to operate several Clients concurrently or operate over the Internet, you have to customize this project (i.e. to add a gateway to it). You need to indicate properties of connection to your PC (server) with the running iridium Gate application in the gateway settings: Host IP-address of your PC with the running iridium Gate application Port a port of iridium Clients connection set in Gate (Client section)

53 53 To add Gate manually to the new project, which is created without scanning the HDL-BUS Pro (Smart-Bus) bus, you should add the gateway into the Project Device Tree from the iridium data base: Thus, we get the following connection diagram of Client to the HDL-BUS Pro (Smart-Bus) bus through the iridium Gate application: iridium Client 1 iridium Client 1 1 iridium Gate 2 2 HDL Smart-Bus iridium Client Connection port of iridium Clients to Gate 2 - Connection port of Gate to the HDL Smart-Bus bus The connection port of Clients to Gate is chosen at random and is set in Gate first and then in GUI Editor. The connection port of Gate to the bus depends on the bus settings and is indicated in the iridium Gate application. For operation over the Internet it is necessary to set the port forwarding on your Wi-Fi router, so the commands could be transferred from the external network to the local network: WAN or LAN NAT iridium ios Client Arbitrary Port External IP:Port Wi-Fi router TCP Port Forwarding Internal IP:Port (10000) PC + Transfer (update server) * refer to your system manager to set the port forwarding

54 Uploading a Project on a Panel, Connection to Equipment 54 When GUI creation is completed it is necessary to check its operation and upload a ready GUI on an ios or Windows control device. 1. Do not forget that if you run Windows 7, launch of iridium software components should be performed by Administrator rights through the right-click menu or by using Administrator account.! 2. Do not forget to close S-bus Configuration Util before starting work with iridium, as S-bus Configuration Util can cause non-interaction of iridium Client with the bus Emulation Mode Emulation mode allows you to check the proper operation of the project graphic interface and connection to the HDL-BUS Pro (Smart-Bus) bus. But the connection with the bus can be established only when having an iridium license whereas the graphic interface is fully functional without the license. Click the Emulator button in the toolbox of the Editor to start the Emulator: The setting of license connection, enabling/disabling sound-on buttons and switching on/off the full screen mode when running the Emulator are performed through the Options window (Tools > Options): When there is a tick in the Demo Mode field there is no connection to the controller and there will be no messages about operation in the demo mode at each start of the Emulator. To operate in the fully functional mode indicate a path to the license which is activated for Windows PC where the Emulator is running in the License Path field.

55 Conversion of the Project for Its Launching on the Target Device 55 When the operation of the project is checked in the Emulation mode you can start its uploading on the ios or Windows target device. Conversion of the project to the format for its launching on the panel is made in iridium Transfer. It is an application for converting and uploading projects on control devices and also for storing and binding iridium licenses. The transfer of the project created in iridium GUI Editor to iridium Transfer can be made in several ways: 1. Transfer of the design by the Send to Transfer buttons in the iridium GUI Editor toolbox a) The first type the Send to Transfer button opens the project in Transfer for the quick upload on an ios device (ipad / iphone / ipod Touch). The window for selecting the ios device, which the design is to be bound, from the list of Panels in Transfer will open when transferring. After selecting the panel you can start design updating on the ios device, additional settings by default. b) The second type the Send to Transfer 1 button adds the project in the list of Designs in Transfer and opens the menu of its basic settings. This transfer type is convenient when creating a Windows project. Right after the design transferring and indicating its basic properties you can click the Generate for Windows button and receive a ready Windows Client. 2. Transfer of the saved design file iridium GUI Editor can save designs in *.irp и *.irpz format. Files of these formats can be uploaded in the list of Designs in Transfer by the Add Design button or by the Drag & Drop method: After the addition of the design a window with its basic settings will open, select the required ones.

56 56 When the GUI is added in the list of Designs in Transfer you can start its conversion and uploading in the ios or Widows target control device. The upload of projects on ios and Widows devices is made differently. To convert a project for Windows you need to press the Generate for Windows button. And for uploading on ios device you have to add the ios device, where the project will be uploaded on, to the list of Panels in Transfer. This process is described in the following section: Uploading the Project on an ios Device In order to upload a design on the control device based on Apple ios operation system, it is necessary to establish connection between the iridium Transfer application installed on your personal computer, and the HDL Client application installed on the ios device. Addition of ios Devices to the Transfer Panels List In order to establish the connection between Transfer and HDL, it is needed to add the control device with the installed HDL Client into the list of Panels in Transfer. Addition of the ios based device into the list of Panels in Transfer is available through the Device Search option. For a successful search, please make sure that your PC and ios device are connected to the same Wi-Fi network (it can be checked with ping request). Discovery of the device cannot be done over USB connection. To start discovery of the devices, press the Search button in the Panels tab of the Transfer application, and open the HDL Client application on your ios device. Please make sure you are opening the application, and not restoring it from the minimized state which is possible on the devices with multitasking support. Before starting the discovery, delete HDL Client from the list of the launched programs. If Wi-Fi is active and the search port for panels in the Transfer application (10000) is not blocked or busy by another application, your ios device will appear in the list of panels in Transfer: Here you can see two fields highlighted red. The first field is for selection of the graphic interface that will be uploaded on the selected panel. It is possible to select a required design from the dropdown list containing all added designs in the Transfer application.

57 57 The second field is for the attaching the license file that will enable the graphic interface to connect to the controlled equipment. In case if a license file is absent, there will be no connection between HDL and equipment, you will not be able to neither send control commands nor receive the feedback. At this stage you can generate your project for Windows but there will be no connection to the equipment without the license. Description of the Licensing Procedure for the Control Device In order to receive a license file, you are required to purchase iridium Activation Key and go through the licensing process. The license process includes an activation of the purchased key, after which you will receive the license file for an ios device that needs to be added into the Transfer application or the license file for a Windows device that needs to be added to the folder with the ready project. Receipt of UDID for Activation of the iridium License for an ios Device For receiving UDID of the ios panel from the list of Panels in Transfer, copy it from the Panels tab in the device parameter line: Besides, UDID of the ios device can be copied from the itunes application. It can be helpful when device is added manually or when you work via Internet:

58 58 Licensing Procedure of an ios Device The licensing procedure of an ios device begins with purchasing iridium Activation Key which will be necessary for creation of the license file. The iridium activation key can be purchased in two ways: 1. You can register at our web site, wait till your registration is approved and purchase Activation Key directly from the web site, in section BUY:

59 59 2. You can contact the official iridium distributor in your country. A list of distributors is located in the Partners section at our web site If you are an independent installer for automation systems, you can also receive demo Activation Keys for free, after filling in a separate registration at our web site: After the purchase is made, you will receive an with Activation Key that will be used to make the iridium license, i.e. to generate a license file for a selected device: Activation of your key is made at the following web site: You will receive login information to access the activation web site in the .

60 60 At this web site: you can also recover your license file in case it was lost: Activation of the iridium License Key for an ios Device In order to activate the Base license key you will be required to enter the following information in corresponding fields: your address where the license file will be sent to, Activation Key that you received in , and identification of the specific device (Device UDID) for which the license is generated: After completing all required fields in the Activation window, you will be asked to fill out a user form. This short form needs to be filled out only once and will be used in the future for activation of new licenses from the same address:

61 61 The next step will be receiving of your License File. You can directly download it from the web site, right after activation: or it can be saved from the that will be automatically sent to the specified address.

62 Uploading of the License File for ios to iridium Transfer 62 The iridium license is the file with the extension.irl received after the key activation. After the license file has been downloaded it is necessary to add it into the list of licenses in the Transfer application (Do not forget that in Transfer you can add licenses for ios devices only. Licenses for Windows devices are stored separately). Addition of the license file is done by the Add License button or by dragging and dropping it into the Transfer application window: After the file has been added to it can be attached to the ios device in the Panels tab. Do not forget that in the Licences tab you can add licenses for ios devices only. You can bind only that license file to the device (in the Panels tab) which was activated for that particular panel. When the design and license are ready they can be uploaded on an ios panel from Transfer.

63 Setting up of ios HDL Client 63 Indication of parameters of the connection to the controller and updating of the design is done in the Settings window of the HDL Client application which can be accessed from the general Settings window of your ios device: Update: GUI update enabling/disabling design update at restart of the HDL application Update host - the IP-address of the PC where the Transfer application is running Update port the design update port (leave by default) Search (by default): Server port a server update port Client port - a Client update port Version: Version- a version of the HDL application. The number of Client version should be the same as the number of the iridium version on PC Other: View GUI orientation (vertical, horizontal, screen auto-rotation) Don t sleep - enabling/disabling the Don t sleep mode at lengthy standby of the running Client You can find the local IP- address of the computer in the right lower corner of Transfer: GUI update can be done via either local network or the Internet. When all the settings are completed all that is required is to restart the HDL Client application on your ios device in order to start the update. Please note that for devices that support multitasking, you need to fully close the software, as minimizing maximizing of the software will not work. In order to do a full close of HDL Client, you need to fully delete it from the list of running applications, as it is shown in our instruction at Wiki Opening of the configured application will start the update process from Transfer. After it s completed your design should be fully functional and you can disable GUI update ability in Settings.

64 Creation of iridium Windows-Client 64 Now let s take a look at the process of creating iridium Windows based Client application file for launching under Windows XP/7. The design added into the Transfer application, and intended to be launched under Windows, is necessary to be selected in the list of designs in Transfer. Then click the Generate for Windows button in the Designs tab: You will receive a file folder with the Windows Client application and additional files: Now in order to make the Client application to be fully functional it is necessary to add a license file for Windows into the same folder. Receipt of a license file is done exactly in the same way as for ios devices described above, except for the process of receiving the unique identification for the panel.

65 Receipt of HWID for iridium Windows-Client Licensing 65 For Windows devices a unique identifier which is required for license file receipt is HWID. It s attached to the computer s hard disk drive. You can find HWID of your computer where the Transfer application is installed through the About menu: Or if you open any iridium project (for example an iridium demo-project without a license) on the control device you will be able to receive HWID of your device from a warning popup window: After the license file has been received and added into the generated project folder the Client application can be opened. If you don t have any warnings when you are opening the Windows based Client, it means your license was accepted and your project will run in a fully functional mode. Additional information about operation with the iridium software package can be found at our Wiki.: