main_cons_ui

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
main_cons_ui [2019/09/11 17:54] – [Software Download] ingridmain_cons_ui [2023/05/04 11:33] (current) – ingrid
Line 4: Line 4:
   * [[#main_concepts| Main Concepts]]   * [[#main_concepts| Main Concepts]]
     * [[#project_definition| Project Definition]]     * [[#project_definition| Project Definition]]
-    * [[#user_interface| User Interface]]+    * [[#user_interface| User Interface]]  
 +      * [[#toolbar| Toolbar]]  
 +      * [[#interface_editor| Interface Editor]] 
 +      * [[#object_selection| Object Selection]]  
 +      * [[#pro_line/trend_line/system_tabs| Pro Line/Trend Line/System Tabs]] //<color red>new!</color>//
     * [[#licenses| Licenses]]     * [[#licenses| Licenses]]
     * [[#users_and_groups| Users and Groups]]     * [[#users_and_groups| Users and Groups]]
     * [[#restrictions| Restrictions]]     * [[#restrictions| Restrictions]]
     * [[#protection_pins| Protection Pins]]     * [[#protection_pins| Protection Pins]]
 +    * [[#biometric_protection| Biometric Protection]] 
     * [[#KNX_groups| KNX Groups]]     * [[#KNX_groups| KNX Groups]]
  
Line 18: Line 23:
   * The Thinknx Classic version (version 1.2.25)   * The Thinknx Classic version (version 1.2.25)
   * The Thinknx UP version (version 1.3.0.8), which is an updated version of the Classic with a lot of additional features. To see what’s new in Thinknx UP, check out [[migration_to_thinknxup#what_s_new| this section]].   * The Thinknx UP version (version 1.3.0.8), which is an updated version of the Classic with a lot of additional features. To see what’s new in Thinknx UP, check out [[migration_to_thinknxup#what_s_new| this section]].
-Both versions can be downloaded from Thinknx website on [[http://www.thinknx.com/v3/en/downloads.html| this link]].+Both versions can be downloaded from Thinknx website on [[https://www.thinknx.com/v4/en/downloads.html| this link]].
  
 System requirements for Thinknx UP Configurator: System requirements for Thinknx UP Configurator:
Line 35: Line 40:
   * a [[#toolbar| toolbar]] with the main feature for project management   * a [[#toolbar| toolbar]] with the main feature for project management
   * an [[#interface_Editor| interface editor]] considered as the working area that reproduces the final graphical interface   * an [[#interface_Editor| interface editor]] considered as the working area that reproduces the final graphical interface
-  * [[#interface/system_tabs| Interface and System tabs]] represented as tree views to manage the Interface/System objects.+  * Three tabs on the right called [[#Pro_line/Trend_line/system_tabs| Pro Line, Trend Line and System tabs]] to manage the Interface/System objects.
  
 \\ \\
-{{ :conf_ui2.png?direct&800 |ThinKnx Configurator's Interface}}+{{ :conf_ui2a.png?direct&800 |ThinKnx Configurator's Interface}}
 <WRAP center 60%> <WRAP centeralign> Figure 1: ThinKnx Configurator's Interface </WRAP>  </WRAP> <WRAP center 60%> <WRAP centeralign> Figure 1: ThinKnx Configurator's Interface </WRAP>  </WRAP>
  
Line 49: Line 54:
 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. 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.
  
-  * **New** Create a new project by launching the wizard tool for project creation. For more details refer to [[proj_man #creating_a_project|this section]]. +  * **Projects** Access the project manager window. The user can create/open/close/rename/import/export/clone/delete a project. Multiple backup points can be created for the same project if additional tests need to be done without ruining the stable version of the project. Any version can be restored by clicking on the folder icon next to each project and accessing the Backup Points window. For more details on how to create and deploy a Thinknx project, refer to [[proj_man #creating_a_project|this section]]. 
-  * **Open** By clicking on this button, a pop up window with the following functions will be displayed: +{{ :conf_proj_manager.png?direct&800 |Project Manager Window}} 
-    * //Open:// Open the selected project. +<WRAP center 60%> <WRAP centeralign> Figure 2: Project Manager Window </WRAP>  </WRAP> 
-    * //Import:// Import a previously save project file (with .erg extension for Classic, and .tup extension for UP). + 
-    * //Remove:// Remove the selected project from the list. +{{ :conf_proj_backup.png?direct&600 |Project Backup Points}} 
-    * //Rename:// Rename the selected project.+<WRAP center 60%> <WRAP centeralign> Figure 3: Project Backup Points </WRAP>  </WRAP> 
   * **Save** Save the current project.   * **Save** Save the current project.
-  * **Close** Close the current project. +  * **Add** Add objects to the project. The selection of objects changes depending on the tab selected in the right pane (ProLine/TrendLine/System).
-  * **Rename** Rename the current project. +
-  * **Add** Add graphic objects to the project.+
   * **Delete** Remove the selected object.   * **Delete** Remove the selected object.
   * **Move** Activate the moving function for page elements. Only available for the Classic version. For the UP version, a drag and drop on the object will allow the user to move it.   * **Move** Activate the moving function for page elements. Only available for the Classic version. For the UP version, a drag and drop on the object will allow the user to move it.
Line 64: Line 68:
  
 {{ :figura18.png?direct&600 |Objects arrange tool}} {{ :figura18.png?direct&600 |Objects arrange tool}}
-<WRAP center 60%> <WRAP centeralign> Figure 2: Objects arrange tool </WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 4: Objects arrange tool </WRAP>  </WRAP>
  
     * //Bring to front:// Move an object or a page before all the others.     * //Bring to front:// Move an object or a page before all the others.
Line 85: Line 89:
  
   * **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.   * **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. +  * **Clipboard** Any copied item or page will be found inside the Clipboard under section "Live Items". Select the live item then click on Send To Archive. The item will be moved to section "Archived Items", allowing the user to close the project and paste the item into another project or PC. The Clipboard is a great tool that will help speed up the design phase and allow the user to just focus on the implementation. 
-  * **Tablet** Activate tablet upload. This command is integrated in the Deploy button in Thinknx UP. + 
-  * **Demo** Activate demo mode; a project preview is displayed. This command is no longer supported in Thinknx UP. +{{ :conf_clipboard.jpg?direct&500 |Clipboard}} 
-  * **Deploy** Deploy the project to server, Thinknx client devices or Cloud.+<WRAP center 60%> <WRAP centeralign> Figure 5: Clipboard </WRAP>  </WRAP> 
 + 
 +  * **Search** //<color red>new!</color>// Search group addresses within the project; shows a list of objects containing a specific KNX group. Clicking on the newly added Replace tab allows to search and replace one or more group addresses, or part of a group. For example, searching for 0/0/* and replacing it with 0/1/* will replace all group addresses from 0/0/0-255 with 0/1/0-255.  
 +  
 +{{ :search_tool.png?direct&500 |Search and Replace}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 6: Search and Replace</WRAP>  </WRAP> 
 + 
 +  * **Deploy** Deploy the project to server and Thinknx client devices using the local network or Thinknx Cloud. 
 +  * **Translator** //<color red>new!</color>// Open the Translator tool, allowing the integrator to translate the Thinknx project into any language. The end-users will be able to switch between languages directly from the Thinknx UP application. 
 + 
 +<WRAP important round center 80%>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".</WRAP> 
 +{{ :translator_1.png?direct&1000 |Translator}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 7: Translator </WRAP>  </WRAP> 
 + 
 +{{ :translator_2.png?direct&900 |Select Language}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 8: Select Language</WRAP>  </WRAP> 
   * **Export** Open export menu. For more details refer to [[proj_man #Exporting_a_project|this section]] .   * **Export** Open export menu. For more details refer to [[proj_man #Exporting_a_project|this section]] .
  
Line 96: Line 116:
  
 {{ :conf_ui3.png?direct&600 |Interface main elements}} {{ :conf_ui3.png?direct&600 |Interface main elements}}
-<WRAP center 60%> <WRAP centeralign> Figure 3: Interface main elements </WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 9: Interface main elements </WRAP>  </WRAP>
  
 The user interface is basically composed of the following elements: The user interface is basically composed of the following elements:
Line 119: Line 139:
   * **Objects** Each page can contain different editable objects. There is 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 [[inter_objs|Interface Objects]] .   * **Objects** Each page can contain different editable objects. There is 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 [[inter_objs|Interface Objects]] .
  
-=== Interface/System tabs ===+=== Object Selection === 
 +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. 
 +{{ :conf_selection_tool.png?direct&600 |Selection Tool}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 10: Selection Tool </WRAP>  </WRAP> 
 + 
 + 
 +=== Pro Line/Trend Line/System tabs === 
 + 
 +  * **Pro Line tab:** Clicking on the Pro Line tab will show all the user-interface objects added to the current project and supported by the Pro Line application (Thinknx UP); the main node represents the entire user interface while every first level child is a function. Under each function are the pages added and under each page the related objects added to it. Right-clicking on each node will allow the user to add, delete, copy or arrange any interface object (for more details refer to [[inter_objs|Interface Objects]]). Selecting an object from the interface editor or the interface tab will show all the related properties in the property grid below the tabs. 
 + 
 +{{ :proline_tab.png?direct&400 | Pro Line tab}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 11: Pro Line Tab </WRAP>  </WRAP> 
 + 
 +  * **Trend Line tab:** Clicking on the Trend Line tab will show all the Trend Line devices added to the project and permit to configure them. Adding a new Trend Line device is also possible from this tab by right clicking on the title and selecting "add device". Once the device added, right-clicking will permit to add objects to this device such as pages and page elements. 
 + 
 +{{ :trendline_tab.png?direct&400 | Trend Line tab}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 12: Trend Line Tab </WRAP>  </WRAP>
  
-  * **Interface tab:** Clicking on the interface tab will show 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. Under each function are pages added and under each page the related objects added to it. Right-clicking on each node will allow the user to add, delete, copy or arrange any interface object (for more details refer to [[inter_objs|Interface Objects]]). Selecting an object from the interface editor or the interface tab will show all the related properties in the property grid below the tabs. 
   * **System tab:** Clicking on the system tab will show all the system objects added to the current project; the main node represents all the generic and most important data related to the server and project. Right-clicking on the system tab will allow the user to add any system object. Clicking on an existing system object will show all the related properties in the property grid below the tabs. For more details refer to [[system_objs|System Objects]] .   * **System tab:** Clicking on the system tab will show all the system objects added to the current project; the main node represents all the generic and most important data related to the server and project. Right-clicking on the system tab will allow the user to add any system object. Clicking on an existing system object will show all the related properties in the property grid below the tabs. For more details refer to [[system_objs|System Objects]] .
  
-{{ :figura20n.png?direct&600 | Interface objects and system objects tree views}} +{{ :system_tab.png?direct&400 | System tab}} 
-<WRAP center 60%> <WRAP centeralign> Figure 4: Interface objects and system objects tree views </WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 13: System Tab </WRAP>  </WRAP>
  
 ==== Licenses ==== ==== Licenses ====
Line 131: Line 166:
 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. 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 5. The license editor will also show up when creating a new project inside the wizard (for more details refer to [[proj_man#creating_a_project|this section]]). +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 [[proj_man#creating_a_project|this section]]). 
  
 {{ :conf_license.png?direct&300 |Accessing the license editor}} {{ :conf_license.png?direct&300 |Accessing the license editor}}
-<WRAP center 60%> <WRAP centeralign> Figure 5: Accessing the license editor </WRAP>  </WRAP> +<WRAP center 60%> <WRAP centeralign> Figure 14: Accessing the license editor </WRAP>  </WRAP>
- +
-{{ :figura1.png?direct&600 |Licenses editor}} +
-<WRAP center 60%> <WRAP centeralign> Figure 6: License editor </WRAP>  </WRAP>+
  
 +{{ :conf_licenses.png?direct&600 |Licenses editor}}
 +<WRAP center 60%> <WRAP centeralign> Figure 15: License editor </WRAP>  </WRAP>
  
 +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.
  
 \\ \\
-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. +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. \\ //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: If an IR transmitter object is added to the project, a window with the following warning is displayed on the screen:
  
 {{ :figura2.png?direct&600 |Not supported device for selected licenses warning}} {{ :figura2.png?direct&600 |Not supported device for selected licenses warning}}
-<WRAP center 60%> <WRAP centeralign> Figure 7: Not supported device for selected licenses warning </WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 16: Not supported device for selected licenses warning </WRAP>  </WRAP>
  
  
Line 160: Line 195:
 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 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.
  
-{{ :figura3.png?direct&700 |Users and groups editor}} +{{ :conf_users.png?direct&600 |Users and groups editor}} 
-<WRAP center 60%> <WRAP centeralign> Figure 8: Users and groups editor</WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 17: Users and groups editor</WRAP>  </WRAP>
  
  
Line 190: Line 225:
   * **Inactivity function** Index of the function which the default page belongs to. (starting from 0)   * **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)   * **Inactivity page** Index of the default page. (starting from 0)
 +  * **Show scheduler** if enabled, it will show an icon in the client application to open the Scheduler Manager on the top right corner of the interface. When disabled, the icon will not show and the client will not have access to the scheduler.
  
 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 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.
Line 201: Line 237:
 \\ 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. \\ 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.
  
-{{ :figura6.png?direct&500 | Add a new user to a group}} +{{ :conf_add_user.png?direct&600 | Add a new user to a group}} 
-<WRAP center 60%> <WRAP centeralign> Figure 9: Add a new user to a group </WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 18: Add a new user to a group </WRAP>  </WRAP> 
 + 
 +\\ 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. 
 + 
 +{{ :conf_user_summary.png?direct&600 | View and export user information}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 19: View and export user information </WRAP>  </WRAP>
  
  
Line 211: Line 252:
  
 {{ :figura13.png?direct&500 |Restrictions editor for functions/pages/objects}} {{ :figura13.png?direct&500 |Restrictions editor for functions/pages/objects}}
-<WRAP center 60%> <WRAP centeralign> Figure 10: Restrictions editor for functions/pages/objects </WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 20: Restrictions editor for functions/pages/objects </WRAP>  </WRAP>
  
  
Line 233: Line 274:
  
 {{ :figura24.png?direct&500 |Protection PIN editor}} {{ :figura24.png?direct&500 |Protection PIN editor}}
-<WRAP center 60%> <WRAP centeralign> Figure 11: Protection PIN editor </WRAP>  </WRAP>+<WRAP center 60%> <WRAP centeralign> Figure 21: Protection PIN editor </WRAP>  </WRAP>
  
  
Line 244: Line 285:
  
 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.\\ 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.\\
-<WRAP center round important 80%>+<WRAP center round tip 80%>
 The default value of the PIN code is //12345//\\ The default value of the PIN code is //12345//\\
 </WRAP> </WRAP>
Line 274: Line 315:
 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.\\ 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.\\
  
 +==== Biometric Protection ====
  
 +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. 
 ==== KNX Groups ==== ==== KNX Groups ====
  
-Within Thinknx system KNX groups can be divided into two main categories: read and write 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.\\ 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.+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. 
 +{{ :conf_knx.png?direct&700 |Disabling the sending on the bus}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 22: Disabling the sending on the bus </WRAP>  </WRAP> 
 + 
 +{{ :conf_knx2.png?direct&700 |Disabling the sending on the bus}} 
 +<WRAP center 60%> <WRAP centeralign> Figure 23: Disabling the sending on the bus </WRAP>  </WRAP>
  
  
  • main_cons_ui.1568217243.txt.gz
  • Last modified: 2019/09/11 17:54
  • by ingrid