Wiki

System Architecture

ThinKnx is a supervision system for home and building automation based on client-server architecture. The server part consists of one ThinKnx device (Compact, Micro, Rack or Touch) that represents the logical unit of the system and controls all the equipments connected to it. The client part consists of PCs, touch screens, tablets and smartphones connected to the LAN via Ethernet or WiFi: all these devices, through the ThinKnx software, communicate with the server to control the plant.

Scheme of a typical integrated installation

Figure 1.1: Scheme of a typical integrated installation



Figure 1.1 shows a standard installation of ThinKnx system in a KNX or Modbus plant. The ThinKnx server interfaces with KNX plant through its dedicated bus connector. It is also possible to interface with Modbus or other buses through RS232 or TCP . Additional functions can be added connecting devices to server through RS232 or TCP. For example, anti-theft systems, audio or video matrix, home theatre systems, etc. The ThinKnx server controls all the devices connected to it and, working as a gateway, allows interactions between the connected devices even if they are using different technologies. Indeed, clients don’t communicate directly with devices but sends commands to ThinKnx server that forwards them to devices.

The gateway feature is a powerful tool that allows to control and integrate different devices and systems. Therefore, for example, Sonos Player or IR transmitter can be controlled from KNX plates simply configuring server logics. Anti-theft system, for example, can send telegrams on KNX or launch sceneson particular events. When an intercom door station makes a call, ThinKnx clients ring and the server can perform actions on other devices or KNX. The power of these interactions between devices enhance the advantages and comfort of smartbuildings.


ThinKnx Solution Components

The solution proposed by ThinKnx is composed by hardware and software that represent the supervision system. During normal runtime, ThinKnx server is the logical unit of the supervision system and communicates with ThinKnx clients. The client part of ThinKnx solution consists of software applications for PCs, smartphones, tablets and touch screens.

During design phase, graphics and logics (the supervision ”project”) are configured using ThinKnx Configurator software. This tool is easy to use and permits to create and to customize the user interface, to define system logics and services and to commit the created project, loading logics on server and graphical interface on clients.


ThinKnx Servers

The ThinKnx servers range was born to cover all the possible installation cases of a supervision system. All the devices are able to interface directly with the KNX plant and have several communication ports to connect to the Ethernet and to other buses (like Modbus etc.) or to other devices like anti-theft systems (through RS232 or TCP/IP). They are also accurately designed for 24/7 operation and optimized for high reliability. In respect to the basic functions - that are included on every server model - additional facility can be activated by means of licenses.

  • ThinKnx Compact It is the most versatile device. Support all kind of functions (Security, VoIP, Audio/Video). The right devices for the majority of plants.
    • Fanless processing device optimized for continuous operation
    • Mass memory on industrial Compact-Flash
    • Power: 12-18 VDC - 1A Max
    • 1x EIB/KNX port with direct connection through clips
    • 1x network port
    • 1x standard RS232 serial port with DE9P connector
    • 2x USB port
    • KNX telegrams led
      For more info about ThinKnx Compact server please check the related page on our website

  • ThinKnx Micro In a very small device the ability to completely control KNX. Can be enhanced with VoIP function for intercom communication.
    • Fanless processing device optimized for continuous operation
    • Mass memory on MicroSD
    • Power: 12-24 VDC - 1A Max
    • 1x EIB/KNX port with direct connection through clips
    • 1x network port
    • KNX telegrams led
    • Consumption 1 Watt
      For more info about ThinKnx Micro server please check the related page on our website.

  • ThinKnx Micro ZWave In a very small device the ability to completely control KNX and Z-Wave. Can be enhanced with VoIP function for intercom communication.
    • Fanless processing device optimized for continuous operation
    • Mass memory on MicroSD
    • Power: 12-24 VDC - 1A Max
    • Z-Wave transceiver
    • 1x EIB/KNX port with direct connection through clips
    • 1x network port
    • KNX telegrams led
    • Consumption 1 Watt
      For more info about ThinKnx Micro ZWave server please check the related page on our website.

  • ThinKnx Envision All-in-one Touch Server which allows to control the home or building using a high resolution touch screen.
    • Quad-core ARM Cortex A9 CPU
    • GB DDR3 SDRAM
    • Capacitive touch screen
    • 7” screen 158x93mm visible area, 1024×600 resolution or 10” screen 217x136mm visible area, 1280×800 resolution
    • Linux embedded operating system
    • Power: 12-24 VDC - 1.5A Max
    • 1x EIB/KNX port with direct connection through clips
    • 1x network port
    • Consumption: 10 W Max (for 7” screen) or 12 W Max (for 10” screen)
      For more info about ThinKnx Envision server please check the related page on our website.

  • ThinKnx Rack It is the most powerful and expandable device, designed for large buildings or demanding applications.
    • Fanless processing device optimized for continuous operation
    • Mass memory on industrial Compact-Flash
    • External power supply 220V AC
    • 1x EIB/KNX port with direct connection through clips
    • 2x serial ports configurable for RS232 or RS485
    • 1x serial port RS232 9 pins
    • 4x USB ports
    • 2x Ethernet ports
      For more info about ThinKnx Rack server please check the related page on our website.


ThinKnx Clients

ThinKnx offers a wide range of native applications to allow tablets, smartphones, touch screens and PCs to interface with the supervision system. The choice to create native applications comes from the necessity to obtain the best possible performances during the Wi-Fi or 3G connection to ThinKnx servers, providing the user with an unprecedented experience.

  • ThinKnx Player for Windows This application allows to control the building from any Windows device. Suitable even for the Windows 10 operating system, it includes settings that allows to disable the full-screen mode, to resize the application window and to visualize the mouse cursor, adapting the application to the device which the application is installed on, improving the user’s experience. Usually used on Windows based touch screens.
  • ThinKnx Player for Mac This application allows to control the building from any computer running Mac operating system. It offers the same functions of the Player for Windows application.
  • ThinKnx for iPad This is the app for iPad that, connecting to ThinKnx servers, allows to manage automation directly from iOS tablets. It allows to control several buildings using a quick and intuitive project selector.
  • ThinKnx Pocket for iPhone This is the app for iPhone that, connecting to ThinKnx servers, allows to manage automation directly from iOS phones. It allows to control several buildings using a quick and intuitive project selector.
  • ThinKnx for Android This is the app for Android tablet and smartphone that coordinates the intelligent building through a Wi-Fi or 3G connection to ThinKnx servers. The interface is designed with attention to the smallest detail to adapt the graphics to the display size of the employed device.

ThinKnx Configurator

The ThinKnx Configurator software is the indispensable tool for the creation and development of a supervision project. It makes possible to create all the connections between the graphical user interface and all the devices integrated into the plant.

Following some simple steps and intuitive parameters, graphic interfaces can be deeply customized and are accessible from every client and device. Just as efficiently, it is possible to create logics and to set up all the system elements to obtain deep integrations between all the existing devices.

Finally, the same tool allows to upload the project on client devices and ThinKnx servers with differentiated exports based on the specific user.

Starting from the next chapter of this manual, all the features of ThinKnx Configurator will be explained.


How to Start

Always referring to figure 1 as a standard installation, this section explains the first steps to follow when installing ThinKnx server in the plant.

Once the server is connected to LAN it acquires an IP address provided from the DHCP service. To discover the IP address assigned to the server use the ”Servers Manager” tool installed with ThinKnx Configurator software (see figure 2 ). This software provides a list of all the ThinKnx server (ordered by serial number) detected on the LAN and for each of them shows its IP settings. After selecting the ThinKnx server installed, it is possible to disable the DHCP service and provide it with a static IP. Click on the ”Apply server setup” to confirm the changes. This step is recommended to avoid the loss of the ip address in case the connection is lost: in fact on connection recovery, the DHCP server could not assign the same address, causing problems between server and clients.

If the server is connected on a network not served by a DHCP service, it will acquire as default address: 192.168.0.200

It is highly recommended to disable DHCP service and use a static IP address. Otherwise, it is possible to run into clients connection problems when the DHCP lease expires.


The server can be reached and configured from its web interface. To open the server web interface just launch your preferred internet browser (Firefox or Chrome are tested browser) and digit: http:\\serverip:5051

Server Manager: tool to discover servers on the network

Figure 1.2: Server Manager: tool to discover servers on the network



You will be prompted for login. At the first access the following credentials must be used:
username: service
password: password

You will be request to change the password for the next access. Please take note of the new password as it will require an hard reset to recover it.

In addition to port 5051 TCP used for web interface, clients connect to the server through port 7550 TCP. If the final user requires remote control of the plant, it is mandatory to configure port forwarding on router. To allow clients to reach the server from outside the LAN open the port 7550 TCP on router and forward it to the server IP. If the user wants to manage the server remotely from its web page, also port 5051 must be opened on router and forwarded to the server.

The next step consists in creating the supervision project with the ThinKnx Configurator (for more details refer to section 3.1 ).

To enhance network performances and avoid errors, all the clients can connect to the server using two addresses, one local address to use inside the LAN and one host name or external address to use outside the LAN. In this way the problems regarding routers without NAT loopback are avoided. This two addresses can be set in the Configurator, in the wizard during project creation (for more details refer to Step 3 on section 3.1 ) or in the System object properties in a second time (for more details refer to section 4.1 ).

To interface objects with KNX plans, it is very useful to import the ETS project into Configurator project. In this way, all the groups configured in ETS will be shown in Configurator in a treeview. The ETS project must be exported in CSV format and imported in Configurator adding ”ETS Project” object, following instructions in section 4.2 .

The final step after configuring graphics and logics in Configurator, consists in loading the project on server and clients. If the PC running the Configurator is in the same LAN of the ThinKnx server, it is possible to directly upload the project on ThinKnx server and iOS clients (for more details refer to Figure 3.13 ). Otherwise, it is always possible to export the project in a file and then upload it on server or clients manually (for more details refer to Figure 3.14 ).

After uploading the project on ThinKnx server, the server needs a short time to restart. The first time clients try to connect to server they need authentication. This operation can be done on server web page (for more details refer to Figure 3.12 ).


Installing ThinKnx Player on Mac computers

Adobe AirThinKnx Player for Mac is an Air application, thus to be installed on Mac computers it requires Adobe Air software installed. Adobe Air sotfware can be found at https://get.adobe.com/air/ .

The ThinKnx Player for Mac can be found in the download page of www.thinknx.com and, after downloading and unzipping it, double click on the .air file to launch the installation. To know how to load projects on Mac clients refer to item 3.4.


Main Concepts and User Interface


Main Concepts


Configurator

Configurator software is the dedicated tool used to design graphical user interface, clients behaviour and to configure all the ThinKnx server services and functions.


Project definition

A project can be defined as a folder containing all the configuration files and all the settings related to a specific plant. All files imported in the project (such as ETS, images, etc.) are copied and stored in the project folder. For more details refer to chapter 3 .


Licences

The licences editor displays the list of selectable licences that can be purchased by the customer; bundles or single licences can be selected by ticking the box next to the item and, by clicking on any licence, a brief explanation of the selected item is displayed on the right side of the window.

Licenses selection form

Figure 2.1: Licenses selection form



Licences selection can be adjusted in the editor contained in the wizard tool while creating the project (for more details refer to section 3.1in particular to step 5). Any subsequent required modification can be performed from the main System object (for more details refer to section 4.1 ).

It is strongly advised to set licenses accordingly to the real available licenses. This will grant that a project exported without warning from configurator will run at once on the server. Suppose that for a particular project are available the following licenses: Security and Intercom package, Audio/Video licence and Web licence with 4 clients. Matching voices have to be ticked in the licences tree and the number of clients has to be typed in the box in the upper right.

If an IR transmitter object is added to the project, a window with the following warning is displayed on the screen:

Not supported device for selected licenses warning

Figure 2.2: Not supported device for selected licenses warning



This warning indicates that the object at issue will not be working once the system will be activated but it will not block project exportation.



Creating, editing and deleting users

Users and groups allow to generate different settings and interface profiles in the same project. To create, edit or delete users or groups, select the ”System” object and then click on the ”Authorizations” property. Click on the button on the right to access the editor.

Users and groups editor form

Figure 2.3: Users and groups editor form



To create a new group, click on the ”New group” button. A new item with a fake name will be displayed in the users tree. To edit the name, click on the item and adjust the properties in the grid on the right.

All properties can be adjusted in the grid; they will be taken by each user added to this group.

  • Name Group or user name.
  • ThinknxCloud password Password associated to this user in the ThinknxCloud service.
  • Display cursor If disabled, the cursor is will not displayed (valid only for Windows/MacOs clients).
  • Full screen If enabled, the application will be displayed full screen (valid only for Windows/MacOs clients).
  • Sound on click If enabled, a beep will be emitted at every mouse click.
  • Block swipe Determines whether advanced gestures are supported by touch devices (not valid for iOS clients).
  • Show status bar Determines if a status bar is displayed in client applications (only for iOS clients).
  • Reduce long press If disabled, the user can interact with the client using the default longpress (f.e. 4 sec for iPad, 3 sec for Android); if enabled, the longpress activation time will be reduced to 1.5 sec.
  • SIP client Determines if the VoIP function is enabled. If enabled, the following properties will be displayed:
  • SIP Ringtone Allows to set the ringtone to be played on the client device when the device is called from another SIP device.
  • Use client random port If enabled, use random listening port on clients in order to avoid any possible conflict between VoIP applications.
  • SIP protocol Determines the protocol to be used for SIP messages sending. TCP is mandatory for iOS devices to work in background mode. The UDP protocol is mandatory for some PBX servers.
  • Register Determines if the client will register on an SIP register (PBX). If enabled, the following properties will be displayed:
    • PBX system: If enabled, the ThinKnx internal PBX will be used and the client will be one of the PBX user created on the PBX system object (refer to section 4.8 ). If disabled, the client will try to register to a third party PBX and the following properties will be displayed:
    • SIP username: SIP client username used during registration process.
    • SIP password: SIP client password used during registration process.
    • Register address: IP address or hostname of the third party registrar (PBX).
    • Register port: UDP port number of the third party registrar (PBX).

  • Inactivity timer If enabled, this properties allows to configure a specific page that will be automatically reloaded by the client after a pre-set time interval if the user doesn’t interact with the client; the ”Inactivity interval”, ”Inactivity function” and ”Inactivity page” properties will be displayed.
  • Inactivity interval User’s inactivity time interval after which the system automatically redirects to the selected page. (If the user taps the screen the inactivity timer is automatically reset.)
  • Inactivity function Index of the function which the default page belongs to. (starting from 0)
  • Inactivity page Index of the default page. (starting from 0)

To create a user already associated to a previously created group, select the destination group and click on the ”New user” button. Doing so, the user takes the properties values from the group. To rename the user, select it from the users tree and adjust the ”Name” property in the grid on the right.

To create an independent user, click on the ”New user” button without selecting any group.

Users can be associated to a group at a later moment by dragging them on the desired group.

To delete a group or a user, click on the ”Delete object” button after selecting it. Configurator requires a deleting confirmation; click on ”Yes” if the item has to be cancelled.

Deleting a group, all associated users are automatically turned into independent users. If some objects integrated into the plant contain restrictions for the specific group or user, which has to be deleted, a warning message with the list of objects containing a restriction is displayed; if deleting is confirmed, restrictions for the group or user are removed too.

Figure 2.4: Add a new user to a group

Figure 2.4: Add a new user to a group




KNX Groups

Within Thinknx system KNX groups can be divided into two main categories: read and write groups.
Read groups can contain many KNX addresses: addresses must be divided by “;”. The status of the object will assume the value passed by the last telegram received by one of the addresses in the group.
Write groups have just one address. An asterisk placed before the group address set the simulation mode: in this mode the status of the object change, but no traffic will be generated on the KNX bus.


Restrictions setting

Suppose that a group of users has to be blocked in order to be prevented to visualize a specific function on clients. Select the function in the interface tree, select the ”Restrictions” property in the grid and click on the button on the right.

Restrictions editor for functions/pages/objects

Figure 2.5: Restrictions editor for functions/pages/objects



In the restrictions editor all previously created users and groups are displayed. As default setting, any object does not contain restrictions on users so, when the editor is launched for the first time, all items are checked.

Suppose that all the users part of the ”Operators” group have to be blocked, so unchecking the box displayed next to the group name is enough. Then click on ”OK” button. Doing so, a restriction on ”Operators” group will be set in the selected function hence when the project is exported, the selected function will not be visible for users belonging to the ”Operators” group.

Two more buttons, useful to speed the configuration process up, can be found in the editor: ”Block all users”, which sets a total restriction on the object (removes all ticks) and ”Unlock all users”, which removes any restriction previously set on the object.

Suppose that the ”Administrator 3” user can only visualise one page in the selected function. A block on the other pages has to be set for ”Administrator 3”. To do that, place the cursor on single pages and open the restrictions editor. Set the restriction by unchecking the box near ”Administrator 3”.

Blocks can be set on all the objects contained in pages. The procedure is exactly the same: select the desired object in the interface tree, select the ”Restrictions” property, open the editor and set the blocks.

All restrictions have a priority order: function, page, single object. If a restriction for a group of users is set on one function, the whole function will not be exported even if the same restriction is not set for the objects contained in that function.



Protection PINs

When all the project’s objects must be visible to all the users but some of them still need protection, it is possible to apply a protection PIN on the object.

In the same project is possible to create a list of PINs to use in the client application to protect interface objects. To create, edit or delete PIN codes, select the ”System” object and then click on the ”Protection PINs” property displayed in the grid below; then click on the button on the right to access the editor.

Protection PIN editor

Figure 2.6: Protection PIN editor



To create a new PIN, click on the ”Add” button. A new item with a fake name will be displayed in the list. To edit the name, click on the item and adjust the properties in the grid on the right.

  • Label Name of the PIN code.
  • Use grace time If enabled the inserted code will be valid for the period set in the ”Grace period” property and it won’t be asked until grace period expires.
  • Grace period (sec.) Period in seconds during which the inserted code is valid.
  • Retriggering If enabled, every time the user taps on the object while the grace period is valid, the grace time is renewed.

To associate PIN codes to functions, pages or interface objects, select the desired object in the interface tree, select the ”Pin Protection” property in the grid and enable it. The ”PIN code” property will appear and just select the desired PIN code among the ones previously created in the System node.

The default value of the PIN code is 12345


One PIN code can be associated to different objects but an object can contain only one PIN code.


PIN protection is valid only with user driven actions; actions like automatic page change are not subjected to PIN protection.


The user can change the PIN code directly from the client app. To reset all pins to the default values, connect to the server web page and press the “Reset all pins” button inside the “Server→Users” page


When “PIN protection” is set to “Enabled” and the “Switching type” property of the switch object assume one of following values, the grace time must be enabled and set.

  • OFF on pression
  • OFF on pression, ON on release
  • ON on pression
  • ON on pression, OFF on release
  • Value on pression
  • Value on pressione and on release

In the client app, at the first pression of the object the keypad will appear; once inserted the correct code, the switch unlocks. To execute the desired action, the user has to press the switch a second time, after the unlock procedure. The switch will stay unlocked within the “Grace period”. After the “Grace period”, since the switch will lock, the “PIN code” will be requested again.


User Interface

ThinKnx Configurator main window contains a toolbar with the main feature of project management, a working area that reproduce the final graphical interface and two treeview to manage interface and system objects. In the sections below all these components are explained in detail.

ThinKnx Configurator main window and its parts

Figure 2.7: ThinKnx Configurator main window and its parts



Clicking on an interface object inside the graphic editor or from tree views it will become the focus of the operations and the list of its properties is shown on the right side of the window. It is possible to select multiple objects by clicking on them holding the SHIFT button down. The first selected object will appear with a white bounding box whilst the following selected objects will be bounded with a blue box. The first object will always be used as reference in every arrangement operation.


Toolbar

This bar is a menu that contains all the commands to manage and edit the project and the objects, search items within a project and export on clients or servers.

  • New Create a new project by clicking on this button and a wizard tool will be automatically launched. For more details refer to section 3.1 .
  • Open By clicking on this button, a pop up window with the following functions will be displayed:
    • Open: Open the selected project.
    • Import: Import a previously save project file (with .erg extension).
    • Remove: Remove the selected project from the list.
    • Rename: Rename the selected project .

  • Save Save the current project.
  • Close Close the current project.
  • Rename Rename the current project.
  • Add Add graphic objects to the project.
  • Delete Remove the selected object.
  • Move Activate the moving function. A selected object can be moved just if this button is pressed.
  • Arrange Arrange graphic objects. This function allows to move groups of selected objects; by clicking on this button, the following window will be displayed:

Objects arrange tool

Figure 2.8: Objects arrange tool



  • Bring to front: Move an object or a page before all the others.
  • Send to back: Move an object or a page behind all the others.
  • Bring frontward: Move an object frontward.
  • Send backward: Move an object backward.
  • Dispose horizontally: Equally distribute horizontal space between the first and the last selected object.
  • Dispose vertically: Equally distribute vertical space between the first and the last selected object.
  • Align lefts: Align all the objects to the left edge of the reference object.
  • Align centers: Align all the objects to the vertical middle line of the reference object.
  • Align rights: Align all the objects to the right edge of the reference object.
  • Align bottoms: Align all the objects to the lower edge of the reference object.
  • Align middles: Align all the objects to the horizontal middle line of the reference object.
  • Align tops: Align all the objects to the upper edge of the reference object.

Some arrange tool actions require the selection of multiple objects. To select more than one object it is necessary to hold the SHIFT button down while clicking on the objects to select.

It is very important that the background images, such as floor plans or photographs, are always positioned on the far back (they always have to be on the first place of the objects list of the function in the Interface tree view). This is just to ensure that all the command objects such as light switches or shutter controls are in the foreground and are not covered by the picture (if the picture covers the button you will not be able to use them, even if it is a transparent part of the picture and you see the buttons).


  • Copy/Paste Copy or paste pages or objects. They can be selected either on the interface preview or in the interface tree structure and can be pasted in a empty screen portion. Keyboard commands ”Ctrl+C” and ”Ctrl+V” can be used instead of the icon in the toolbar or the right click.
  • Search Search group addresses within the project; shows a list of objects containing a specific KNX group.
  • Tablet Activate tablet upload.
  • Demo Activate demo mode; a project preview is displayed.
  • Export Open export menu. For more details refer to section 3.4 .

Interface editor

It provides the user with the option to graphically compose the user interface and to preview how it will look like on clients. It allows to select and move the objects in the interface. Every interface part has its own properties that can be modified from the property editor on the right-bottom side of the configurator window.

Interface main elements

Figure 2.9: Interface main elements



User interface is basically composed by the following elements:

  • Functions Function is a sort of chapter that can collect several graphical pages. The name of the selected function is always shown on the right-bottom side of the user interface. Properties can be easily adjusted from the settings window that is displayed on the right side by selecting and item from the list:
    • Status: Permits to disable the function and to hide it from sidebar.
    • Label: Name of the function.
    • Icon: Select the desired icon file, this will show up automatically on the left side of the function description, with a standard resolution of 60×60 pixels.
    • Show in website: Indicates if the function will be visualized on the web page. For more details refer to section 4.12 .
    • Restrictions: Permits to restrict the access to the function for specific users.
    • PIN Protection: If enabled, the function is protected and the user must insert a PIN code to see the function. For more details refer to section 2.1.7 .
    • PIN Code: Pin code associated to the object.

  • Functions sidebar This bar appears by touching the blue tag located on the left side of the screen or dragging it to the right; a list of all the functions added to the project is displayed with the function name and the corresponding selected icon.
  • Pages Each function can contain different editable pages, each one labeled by a tab displayed on the upper side of the screen. Each page created, automatically shows up on the top bar starting from the left, the only limitation on the number of pages you can create is the number of characters that can be shown on the top bar. The longer the names of the pages, the less pages you can create. Properties can be easily adjusted from the settings window that is displayed on the right side by selecting and item from the list:
    • Label: Name of the page.
    • Show in website: Indicates if the page will be visualized on the web page. For more details refer to section 4.12 .
    • Restrictions: Permits to restrict the access to the function for specific users.
    • PIN Protection: If enabled, the page is protected and the user must insert a PIN code to see the page. For more details refer to section 2.1.7 .
    • PIN Code: Pin code associated to the object.

  • Objects Each page can contain different editable objects. There are a number of graphical objects that represents standard operations that can be exerted (like switching on/off lights, commanding blinds, controlling HVAC). Every object has its own properties that can be customized. For more details refer to Chapter 5 .

Interface tab

Displays a treeview containing all the interface objects added to the current project; the main node represents the entire user interface while every first level child is a function. Children of a function are pages and objects are grouped inside their parent page. By right-clicking on one node it is possible to add all other interface objects, delete, copy or arrange the object (for more details refer to Chapter 5).

Selecting an object from interface editor or interface tab, all its properties will be visualized in the property grid below the tab.

Interface objects and system objects tree views

2.10: Interface objects and system objects tree views




Functions

Each function can be characterizezd by the following properties:

  • Status Enable or disable function visualization
  • Label Label of text that identify the function
  • Icon Image to display ina the functions menu
  • Show in website Enable or disable the function visualization into website.
  • Hide label on page Hide the function label normally present on the bottom right corner of the screen, when the client is in landscape mode. In portrait mode, since the label works as a button, will appear anyway.
  • PIN protection If enabled, object will require a PIN code to be operated. If “Enabled” the following property will appear:
    • PIN code to be used to protect the object

  • Restrictions Restriction policies for exporting process.
  • Index The index of the function. Cannot be modified.

System tab

Displays the system tree main node that contains all the most important data related to the project; by right-clicking on it, it is possible to add all other system objects, which represent all customizable services provided by the system. For more details refer to Chapter 4 .


Project Management

A project can be defined as a folder containing all the configuration files related to a specific plant and all the settings needed to reconstruct user interface and system logics. New projects can be easily created directly using the Configurator software. Previously existing projects can be imported and edited (they can be renamed, optimised, deleted, etc).


Creating a project

Projects can be created using a dedicated wizard tool, which will be automatically launched by clicking on the ”New” button in the toolbar above.

  • Step 1 Enter the project name without spaces or diacritic signs (mandatory).

New project button and wizard first step

Figure 3.1: New project button and wizard first step



  • Step 2 Select the server type (mandatory) and enter the device serial number (optional); go to the next phase by clicking on ”Next” or conclude the wizard by clicking on ”End”; all the following steps are optional .

Step 2: server selection

Figure 3.2: Step 2: server selection



  • Step 3 Enter IP address to connect to the server using the local network or host name and port (if different from the predefined one) to use remote connection.

Step 3: connection settings

Figure 3.3: Step 3: connection settings



  • Step 4 The name and even the geographic coordinates of the location where the server is installed should be typed in this section. These data will be used on clients when the geolocalization feature is active. These settings are mandatory if the sun calculator object is added to system. Check the box ”Enable Time Server” to use the server as time and date source for KNX devices. Server will synchronize with NTP time server if an internet connection is available.

Step 4: server location settings

Figure 3.4: Step 4: server location settings



  • Step 5 If the plant will be managed by different users and different user interfaces for each user has to be created than it is necessary to create users and groups to be used for export policies. It is possible clicking on the ”Edit” button to access the users editor window. For more details about users creation refer to section 3.1.4.

Step 5: users creation for restrictions

Figure 3.5: Step 5: users creation for restrictions



Once all users and groups are set, a summary is displayed in the empty window. Click on “Next” to move to the next step.

  • Step 6 Selecting the active licences for the project permits that configurator checks while exporting whether objects and functions configured into the project will properly work once the project will be exported and uploaded on the server. In fact, if the project contains objects that are not included in licences purchased by the customer, they will not be working in the real installation.

Step 6: project active licenses editor

Figure 3.6: Step 6: project active licenses editor



Click on “Edit” button to access the licences editor. Single licences, and packages can be selected in the licences editor window. For more details refer to section 2.1.3.

To adjust the information set included into the wizard at a later stage, select the “System” object in the Configurator system tree and all the object properties will be displayed in the property grid below.


Managing a project

After a project has been successfully created, it can be managed using various buttons displayed in the configurator upper toolbar.

Project related buttons on configurator toolbar

Figure 3.7: Project related buttons on configurator toolbar



  • Save Changes applied to the project will be saved.
  • Close Current project will be closed, while the Configurator homepage stays open.
  • Rename Current project name can be edited.
  • Open By clicking on this button, the following window will be displayed:

Figure 3.8

Figure 3.8



Project management form

Figure 3.9: Project management form



Existing projects can be renamed, opened or deleted. Previously created files can be imported in the Configurator.


Cloud

To enable the use of ThinKnxCloud, open the server web page, select Server menu item and then select ThinKnxCloud. In the cloud page, click “Enable ThinKnxCloud” button. A popup will appear to set the maintainer password for the cloud. After the user fills these fields and clicks on the Enable button, the server enables the Cloud features which means project upload and data storage. After the enabling procedure is completed, the status of the cloud must change to Enabled and the user can see how much storage space is using on the cloud.


System object properties to set

  • Serial number: serial number of the ThinKnx server, it is mandatory to use all the cloud features
  • ThinknxCloud: it must be enabled
  • Password for ThinknxCloud: it must contain the maintainer password previously set in the server web page
  • User’s ThinKnxCloud password: if the project requires the use of groups and users, each user configured must have a password associated to it. All the users passwords for the cloud must be different. To create the password, open the Authorizations property, select a user and fill the ThinKnxCloud password property with the password assigned to the user.

Uploading the project on ThinKnx Cloud

Once the cloud properties are set, to upload the project on the cloud, save the project, click on the Export button in the toolbar menu and select “Upload to the Cloud” menu item. All the clients versions of the project (one for each user) are uploaded to the ThinknxCloud server. If the project doesn’t contain any users, only the main version is uploaded. A popup indicating the progress of the upload will appear.


Downloading the project from ThinKnx Cloud

To download the project, open ThinKnx or ThinKnx Pocket app and open the Settings page. Select the Cloud tab and fill the two fields below with the server serial number and the cloud password. If the projects contains multiple user, to download a specific version of the project insert the password associated to the user otherwise use the maintainer password (the one created in the server web page). When the user taps the Download button, the download starts. Different icons indicates whether the project has been downloaded from the Configurator or from the ThinKnx Cloud. To simplify the download procedure from Cloud, the serial number will be displayed for each project under the project name.


Dynamic DNS configuration

In case a fixed public ip address is not available this service grants to access your server even out from the local network. To configure the server open the server webpage from local address:
http://<server_ip_address>:5051.

Figure 3.10

Figure 3.10



From the main menu, select “Server” and click on “ThinKnxCloud”. To add a “ThinKnx ID”, click on the button “Change MyThinKnx settings”. It will appear a windows where to add the name of the device.

Figure 3.11

Figure 3.11



Clicking on the “Enable” button will set the new ThinKnx ID.


Exporting a project

When the project is complete it has to be deployed on the various devices like the server and the clients. The configurator has a special part dedicated to project exporting with several file formats depending on the addressee device. Project can also be exported simply to back it up or to transfer to another PC.

By right clicking on the ”Deploy” button, the following options will be displayed:

  • Upload to local server The project is uploaded to the server so that configurations can be saved and memory can be allocated for objects that require to be configured by the user.

When the project is modified, even sligthly, it is important to transfer it to the server and to the clients. Only in this way you will be granted of the functioning of all the features.


  • Web server for Thinknx Apps Using this option the configurator will publish locally a version of the project that can be downloaded from Thinknx Apps. When you select this option a form will ask you for which user (refer to section 2.a) you want to publish the project. Inside the app (Ios, Android and Windows version) you can go to the settings page and use the “Configurator” section to download the project. The url to put inside the app is published on the bottom of the configurator window like in the image below.

Figure 3.12

Figure 3.12



When you export the project for the Apps using this feature, the configurator will create a snapshot of the project at the time you press the button. If you make modifications to the project and you want to actualize the apps content you need to press again the deploy button so that you will be able to download the new snapshot with all the modifications.


This feature will work only when the PC running the configurator is on the same network of the device running the App. It is useful when internet is not available or during the test phase of the project. When the project is finished it is advisable to use the Cloud feature that will grant that all the client will use the same project version.


  • Web server for Android Touch (obsolete) Select this option if the project has to be uploaded on Thiknx Android touch screen devices. It is not intended for transferring project to generic Android devices.
  • Upload to the Cloud All the clients versions of the project (one for each user) are uploaded to the ThinknxCloud server. If the project doesn’t contain any users, only the main version is uploaded. A popup indicating the progress of the upload will appear. After this step you can download the project inside any app in any moment. You need to go the the settings page of the app and inside the Cloud section fill in the fields with the server serial number and with the cloud password for the user you want to get the project.

By clicking on ”Export” button, the following options will be displayed:

  • Export project Export procedure allows to save the project created with the Configurator as a .erg file; it is particularly useful to store back up copies in a folder and to send projects from a Configurator to another.
  • Optimize project Whenever an image or any kind of file is imported in the Configurator, it is automatically copied in a dedicated project folder so that the software does not operate on the original item, risking to affect the project if it is moved or deleted. Doing so, several unused files roll by the project folder; by clicking on this button they will be automatically removed, remarkably improving and simplifying clients performances.
  • Export for server on file If the PC which the Configurator is running on is not in the same LAN as the server one, the software automatically creates a .srv file that can be manually uploaded to the web page.

Server Uploading procedure

  1. After launching the browser and typing http://’external IP’:5051 the login page is displayed.
  2. Login as service user (default password: ”pass”).
  3. In the homepage, click on ”Upload” button.
  4. Click on ”Select file” and then ”Upload”.

Figure 3.14

Figure 3.14



  1. The server restarts automatically.
  • Export for touch screen/Windows (old clients) this procedure allows to generate a file with .tou extension that is asked from the Windows client and is used to configure it. The generated file has to be transferred to the Windows pc where the Windows Player is installed. Double clicking on the file causes the installation of the new project.
  • Export for Android (old clients) this procedure allows to generate a config.android file that is used from old Android client apps and from MacOS app.

Uploading procedure for Android devices

  1. Connect the device to the PC via USB
  2. Create a folder named ”Thinknx” in the root folder of the device
  3. Copy the config.android file in the folder just created

Uploading procedure for Mac computers

  1. Create a folder named ”Thinknx” in the user’s ”Documents” folder
  2. Copy the config.android file inside the folder just created

Export for user

Export for user allows to configure different versions of the project to be uploaded to clients; the peculiar characteristics of each version can be defined by setting restrictions for users (for more details refer to section 2.1.6 ). The Configurator, if users have been configured in the project (for more details refer to section 2.1.4 ), requires to select which user will be the project exportation final addressee. Select the desired user and click on ”OK”.


Export procedure

After selecting one export modality, the Configurator automatically checks system properties to confirm that an IP address valid for the server has been set; otherwise the export cannot be finished. If components not corresponding to the selected licences have been configured in the project, the Configurator displays a warning message. The export can still be finished but the commands related to unlicensed objects will not be working. If the file has to be exported for touch-screen and Android, is required to specify where the file has to be saved. If the file has to be exported on iPad, the Configurator directly exports the project and launches the web server so that the user can immediately connect.


Client Authentication


Authentication through server web pages

Once the project is loaded on the server and on clients, the client software opens a connection with the ThinKnx server. The first time the project is loaded on the client, it requires to be authenticated on the server.

Figure 3.15

Figure 3.15



The client authentication is done on the server web page, browse in the “Server→Licenses & Codes” and copy the “Last connected client code” and check the “Enabled” box, as shown in the following figure:

Figure 3.16

Figure 3.16




Authentication through ThinKnx app (new procedure)

The procedure to authenticate client devices always requires the effort of installers to access the server web pages and to manually add the last connected client code to the table of enabled clients. To save time to installers and leave more indipendence to final users, it is now possible to authenticate the client directly from the app through a simple popup. To use this feature the ThinKnxCloud must be enabled and the users must be configured (each user with its own cloud password) in the project. It is enough to enable the “Automatic authentication” property in the System node and to upload the project to the cloud (if the Automatic server update is disabled, remember to upload it also on the server!). Then, when an unauthenticated client connects to the ThinKnx server, a popups appears in the app asking for credentials. If the credentials provided by the users are correct, a new row will be automatically added in the table of enabled clients in the server web pages.

Figure 3.17

Figure 3.17




Example

Four clients have to be used for four different functions: three of them shares the same needs, the fourth has fewer enabled functions. First of all, two groups have to be created: the first one contains the three users with similar needs, the other one will contain the user with limited functions; once users have been configured, restrictions have to be manually set on objects. Suppose that the example project has no external server address and contains the following elements:

Figure 3.17

Figure 3.17



Figure 3.18

Figure 3.18



In the project have been only selected ”Modbus and Automation” and ”IR Audio and Video ” licenses.

Figure 3.19

Figure 3.19



Launching the exportation, the Configuration displays the error window containing messages that warns about the empty IP address slot and the missing licences.

Figure 3.20

Figure 3.20



Since the IP address has not been set, the export cannot be continued. To set the IP address, select the ”System” node from the system tree and type the external server address in the empty slot near the property name.

Once the missing information have been added, launching the export again, the error window is still displayed but it contains only the messages related to missing licences. In this case, click on ”Yes” to proceed with the export anyway.

The Configurator, if users have been configured in the project, requires to select which user will be the project exportation final addressee. Select the desired user, for example ”Operator User”, and click on ”OK”.

Figure 3.21

Figure 3.21



Once the project has been downloaded to client, for example to an iPad, that specific client will be allowed to display only a ”reduced” project version, which has been exported for Operator User.

Of all configured functions, Operator User cannot visualise Rollers, Heating and Cameras since they contain a restriction.





Онлайн калькулятор стоимости "Под ключ"

Расчет трех ценовых категорий одновременно
X ЗАКАЗАТЬ