There are currently two versions of the Thinknx Configurator:
Both versions can be downloaded from Thinknx website on this link.
System requirements for Thinknx UP Configurator:
The Thinknx project created inside the Configurator is defined as a folder containing all the configuration files and 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.
A Thinknx project exported using the Classic Configurator (version 1.2.25) has the extension .erg, while a projet exported using the new UP Configurator (version 1.3.0.8) has the extension .tup.
ThinKnx Configurator's main window consists of the following elements:
ThinKnx Configurator's Interface
Clicking on an interface object inside the graphic editor or selecting it from the tree view will show the list of properties related to this object to the right and allow the user to edit it. It is possible to select multiple objects by clicking on them while 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. In the UP version of Configurator, it is possible to edit the common properties for the selected objects at once. When arranging multiple objects selected (for example, Align Left operation), the first object will always be used as reference.
The toolbar is a set of commands to manage and edit the project as well as the elements inside it, search for items within the project and deploy the project to server and client.
Project Manager Window
Figure 3: Project Backup Points
Objects arrange tool
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 show at the top of 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).
Clipboard
Search and Replace
It is important to set one of the languages configured as default before deploying, in order to allow the users to select their own language from the Thinknx UP application. Setting a language as default can be done by clicking on the Languages menu item and selecting “Set Default”.
Translator
Select Language
It is the work place where the users can build their graphical interface and preview how it will look on the clients. It allows them to add, select and move the objects as desired. 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
The user interface is basically composed of the following elements:
Once objects are added inside the UI, it can be easy to select and move them with the mouse cursor. Clicking and dragging from left to right will select all the objects that are entirely enclosed in the selection border. This is called the Window Selection. Clicking and dragging from right to left will select any object crossed by the selection border. This is called Cross Selection.
Selection Tool
Pro Line Tab
Trend Line Tab
System Tab
The licence editor displays the list of available licences that can be purchased and selected by the customer; bundles or single licences can be selected by ticking the box next to the item. Clicking on any licence will show a brief explanation of the selected item on the right side of the window.
To access the license editor, click on the System tab, and select licenses from the properties window as seen in figure 10. The license editor will also show up when creating a new project inside the wizard (for more details refer to this section).
Accessing the license editor
License editor
With the UP configurator version 1.3.0.16, the standard licenses are automatically selected based on the server model configured in the System tab. Any additional license added to the server will have to be manually selected in the optional licenses section as seen in figure 15.
When using previous versions of the UP Configurator (version 1.3.0.15 or before), it is strongly advised to set licenses in the Configurator according to the real available licenses on the server. This will guarantee that a project exported without warning from configurator will run at once on the server.
Example: Suppose that for a particular server the enabled licenses are: Security and Intercom package, Audio/Video licence and Web licence with 4 clients. These licenses should be ticked in the licence editor 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
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.
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 ”Users and Groups” property. Click on the button on the right to access the editor.
Users and groups editor
To create a new group, click on the ”New group” button. A new item with a default name will be displayed in the users tree. To edit the name, click on the item and adjust the properties in the grid to the right.
Adjusting the properties for a Group will apply to all the users under this particular group.
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 property values from the group. To rename the user, select it from the user tree and adjust the ”Name” property in the grid to 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.
When 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 deletion is confirmed, restrictions for the group or user are removed too.
Add a new user to a group
To export the user information or share them by email or QR code, click on the User Data Summary button. A new window will open allowing you to enter the email addresses you wish to share the information with or export the file as PD by clicking on the Export PDF button. A QR code is also available and can be scanned directly from the Thinknx application to download the project automatically with the correct user profile.
View and export user information
Sometimes it is requested that a group of users are prevented from viewing and accessing certain functions, pages or elements inside a page. This is possible by first creating the users in System tab, then going to the function in the interface tree, selecting the ”Restrictions” property in the grid and clicking on the button to the right.
Restrictions editor for functions/pages/objects
In the restrictions editor all previously created users and groups are displayed. By default, all objects do not have any restrictions created, that's why when the editor is launched for the first time, all items are checked to enable the users to access the object selected.
Suppose that all the users who are part of the ”Operators” group have to be blocked; un-checking the box displayed next to the group name and clicking “OK” would be enough to create this restriction. When the project is exported to the users under Operators, the selected function will not be visible for them. 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.
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.
If all objects inside the project must be visible to all the users but some of them still requires some protection, it is possible to use a protection PIN on the desired object.
Inside the project, it is possible to create a list of PIN codes 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 to the right to access the editor.
Protection PIN editor
To create a new PIN, click on the ”Add” button. A new item with a default name will be displayed in the list. To edit the name, click on the item and adjust the properties in the list to the right.
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 the list of pins previously created in the System node will appear.
The default value of the PIN code is 12345
One PIN code can be associated to different objects but an object can only contain 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's 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.
In the client's application, at the first press of the object, the keypad will appear; once the code is inserted, the switch will unlock. 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.
Security passwords are safety passwords stored on the server, used for cameras. The system integrator can configure any security password, and on the user side (with an admin user), it can later be changed to maintain a high level of security.
Security Password
Another way to protect the elements inside the project is through the Biometric Protection parameter. When enabled, the object will remain visible in the application, but will require face or fingerprint verification in order for the user to activate the command.
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. For each write group address, it is possible to disable the sending on the KNX bus by either ticking the option inside the ETS window, or by placing an asterisk before the group address. This will allow the user to run a simulation mode where it is possible to change the status of this group without generating a traffic on the KNX bus. The group will only be seen on the KNX monitor of the Thinknx server.
Disabling the sending on the bus
Disabling the sending on the bus