sys_arch

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
sys_arch [2019/05/14 11:55] wikiadminsys_arch [2023/05/18 07:34] (current) – [System Architecture] ingrid
Line 1: Line 1:
- 
 ====== System Architecture ====== ====== System Architecture ======
-<WRAP  round important center 80%> **Thinknx has launched Thinknx UP, a completely redesigned version of the Classic Thinknx software. To learn more about the migration, click [[migration_to_thinknxup|here]]. ** </WRAP> 
  
-  * [[#introduction| Introduction]] +  * [[#introductionsystem_components|Introduction: System Components]]  
-  * [[#thinknx_solution_components| Thinknx Solution Components]] +  * [[#thinknx_servers| Thinknx Servers]]  
-    * [[#Thinknx_serversThinknx Servers]] +    * [[#pro_linePro Line]]  
-    * [[#thinknx_clients| Thinknx Clients]] +    * [[#trend_line| Trend Line]]  
-    * [[#thinknx_cloud| Thinknx Cloud]] +  * [[#thinknx_clients| Thinknx Clients]]  
-    * [[#thinknx_configurator| Thinknx Configurator]] +  * [[#thinknx_cloud| Thinknx Cloud]]  
-  * [[#communication_between_componentsCommunication Between Components]]+  * [[#thinknx_configurator| Thinknx Configurator]]  
 +  * [[#server_-_client_connectionServer - Client Connection]]  
 +  * [[#network_requirements_for_thinknx_services| Network Requirements for Thinknx Services]]
  
-===== Introduction =====+===== Introduction: System Components ===== 
 + 
 +ThinKnx is a supervision system for home and building automation based on client-server architecture. 
 + 
 +The **[[#thinknx_servers|server]]** consists of one ThinKnx device (Compact, Micro, Rack or Touch) that represents the logical unit of the system and controls all the equipment connected to it.  
 +The **[[#thinknx_clients|client]]**consists of any PC, touch screen, tablet or smartphone connected to the LAN via Ethernet or WiFi: all these devices, through the ThinKnx software, communicate with the server to control the plant.  
 +The **[[#thinknx_cloud|Thinknx cloud]]**is also an important part of the system architecture and is used for multiple purposes that serve both the integrator and the end user.  
 +The **[[#thinknx_configurator|Configurator]]**is provided as the indispensable tool to build complete Thinknx solutions. It is a software used by the integrator to create attractive and customizable graphical interfaces and deploy them on the servers and clients to control the different systems installed in the plant. 
 + 
 +{{  :edited-disegno1.png?direct&500  |Scheme of a typical integrated installation }} 
 + 
 +<WRAP center 60%> <WRAP centeralign> Figure 1: Scheme of a typical integrated installation </WRAP> </WRAP> 
 + 
 +The picture above 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 systems can be integrated with server through RS232 or TCP. For example, anti-theft systems, audio or video matrix, home theater 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. The clients, on the other hand, send their commands to the server which forwards them to the remaining devices allowing the communication between both parties. 
 + 
 +The Gateway feature inside the server allows to control and integrate different devices and systems: 
 + 
 +  * For example, Sonos Player or IR transmitter can be controlled from KNX keypads by simply configuring server logic. 
 +  * Anti-theft system can also send telegrams on KNX or launch scenes on particular events.  
 +  * When an intercom door station makes a call to a Thinknx client, the server can perform actions on other devices or KNX.
  
-ThinKnx is a supervision system for home and building automation based on 
-client-server architecture.  
-  * The **[[#Thinknx_servers| server]]**  consists of one ThinKnx device (Compact, Micro, Rack or Touch) that represents the logical unit of the system and controls all the equipment connected to it.  
-  * The **[[#thinknx_clients| client]]** consists of any PC, touch screen, tablet or smartphone connected to the LAN via Ethernet or WiFi: all these devices, through the ThinKnx software, communicate with the server to control the plant. 
-  * The **[[#thinknx_cloud| Thinknx cloud]]** is also an important part of the system architecture and is used for multiple purposes that serve both the integrator and the end user. 
-  * The **[[#thinknx_configurator| Configurator]]** is provided as the indispensable tool to build complete Thinknx solutions. It is a software used by the integrator to create attractive and customizable graphical interfaces and deploy them on the servers and clients to control the different systems installed in the plant. 
-\\ 
-<WRAP Group> 
-<WRAP column half> 
-{{ :edited-disegno1.png?direct&600 |Scheme of a typical integrated installation }} 
-<WRAP center 60%> <WRAP centeralign> Figure 1: Scheme of a typical integrated installation </WRAP>  </WRAP> 
-</WRAP> 
-<WRAP column half> 
-\\ 
-The picture to the left 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 systems can be integrated with server through RS232 or TCP. For example, anti-theft systems, 
-audio or video matrix, home theater 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. The clients, on the other hand, send their commands to the server which forwards them to the remaining devices allowing the communication between both parties. 
-\\ 
-\\ The Gateway feature inside the server allows to control and integrate 
-different devices and systems: 
-  * //For example, Sonos Player or IR transmitter can be controlled from KNX keypads by simply configuring server logic.// 
-  * //Anti-theft system can also send telegrams on KNX or launch scenes on particular events. // 
-  * //When an intercom door station makes a call to a Thinknx client, the server can perform actions on other devices or KNX.// 
 With a powerful tool such as the Thinknx server, the possibilities are endless. With a powerful tool such as the Thinknx server, the possibilities are endless.
 +
 +===== ThinKnx Servers =====
 +
 +During normal runtime, ThinKnx server is the logical unit of the supervision system and communicates directly with the ThinKnx clients. The ThinKnx servers range was born to cover all the possible installation cases of a supervision system.
 +The products are divided into two lines based on the project requirement: the **<color #6e99c7> [[#pro_line| Pro Line]] </color>** and the **<color #6e99c7> [[#Trend_line| Trend Line]] </color>**.
 +
 +==== Pro Line ====
 +
 +The **Pro Line** includes a professional range of servers able to interact with complex systems. These servers can 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 addition to the basic functions that are included on every server model, more functionalities can be activated by means of licenses.
 +<WRAP tip center round 80%> When using a Pro Line server, the end-user can benefit from a highly customizable interface through the Thinknx UP application, available on all platforms. </WRAP>
 +
 +The models included in the Pro Line are listed below:
 +
 +  * [[#thinknx_micro_20_micro_din|Micro_20/Micro_DIN]] 
 +  * [[#thinknx_compact_20_compact_din| Compact_20/Compact_DIN]] 
 +  * [[#thinknx_envision7_20| Envision7_20]] 
 +  * [[#thinknx_envision7r_20_retrofit| Envision7R (Retrofit)]] 
 +  * [[#thinknx_envision10_20| Envision10_20]] 
 +  * [[#thinknx_rack| Rack]]
 +
 +=== ThinKnx Micro_20 / Micro_DIN ===
 +
 +This very small device has the ability to completely control KNX systems. Can be enhanced with VoIP function for intercom communication or with Z-wave dongle for wireless integration. 
 +<WRAP group> <WRAP column half>
 +
 +  * Fanless processing device optimized for continuous operation 
 +  * Mass memory on MicroSD 
 +  * Power: 9-24 VDC - 1A Max 
 +  * 1x EIB/KNX port with direct connection through clips 
 +  * 1x network port 
 +  * 1x USB port (for Z-wave dongle) 
 +  * KNX telegrams led 
 +  * Consumption 1 Watt
 +
 +</WRAP> 
 +<WRAP column half> {{  :micro.png?direct&200| Micro_20 / Micro_DIN }}</WRAP> </WRAP>
 +For more information about the Micro_20/Micro_DIN, visit [[https://www.thinknx.com/v4/en/micro.php| this page]].
 +
 +=== ThinKnx Compact_20 / Compact_DIN ===
 +
 +A completely re-engineered version of the Compact, the Compact_20 and Compact_DIN offer an extended set of I/O's and two serial ports, in addition to a small monitor allowing the integrator to easily control the inputs and outputs. This server is the perfect fit for all types of projects, and can be upgraded with all available licenses such as Z-Wave, Lutron, Modbus, Intercom, Security and more.
 +
 +<WRAP GROUP> <WRAP column half>
 +
 +  * Fanless processing device optimized for continuous operation
 +  * Power: 9-24 VDC - 1A Max 
 +  * Memory on chip eMMC
 +  * 1x EIB/KNX port with direct connection through clips 
 +  * 1x network port 
 +  * 1x RS-232 and 1x RS-485 serial ports
 +  * 2x USB ports
 +  * 4x Output relays (6A)
 +  * 3x digital outputs open collector
 +  * 4x Analog/Digital inputs
 +  * 2x Digital inputs
 +  * 1x Display
 +
 +</WRAP> 
 +<WRAP column half> {{  :compact.png?direct&200| Compact_20 / Compact_DIN }}</WRAP> </WRAP>
 +
 +For more information about the Compact_20/Compact_DIN, visit [[https://www.thinknx.com/v4/en/compact.php| this page]].
 +
 +=== ThinKnx Envision7_20 ===
 +
 +All-in-one Touch Server which allows control of the home or building using a high resolution touch screen. <WRAP GROUP> <WRAP column half>
 +
 +  * Octa-core Cortex A53 CPU 
 +  * Capacitive touch screen 
 +  * 7” screen 155×87 mm visible area, 1024×600 resolution 
 +  * Linux embedded operating system 
 +  * Power: 12-24 VDC - 1.5A Max 
 +  * 1x EIB/KNX port with direct connection through clips
 +  * Consumption: 10 W Max 
 +  * 1x network port 
 +  * 1x RS-232 and 1 RS-485 serial ports 
 +  * Sensors: 1x temperature sensor, 1x humidity sensor, 1x ambient luminosity sensor
 +
 +</WRAP> 
 +<WRAP column half> {{  :envision.png?direct&180| Envision_20 }}</WRAP></WRAP>
 +
 +For more information about the Envision, visit [[https://www.thinknx.com/v4/en/envision.php| this page]].
 +=== ThinKnx Envision7R_20 (Retrofit) ===
 +
 +All-in-one Touch Server which allows control of the home or building using a high resolution touch screen. 
 +<WRAP GROUP> <WRAP column half>
 +  * Octa-core Cortex A53 CPU 
 +  * Capacitive touch screen 
 +  * 7” screen 155×87 mm visible area, 1024×600 resolution 
 +  * Linux embedded operating system 
 +  * Power: 12-24 VDC - 1.5A Max 
 +  * 1x EIB/KNX port with direct connection through clips 
 +  * Consumption: 10 W Max 
 +  * 1x network port 
 +  * 1x RS-232 and 1 RS-485 serial ports 
 +  * Sensors: 1x temperature sensor, 1x humidity sensor, 1x ambient luminosity sensor
 +
 +</WRAP> 
 +<WRAP column half> {{  :envision.png?direct&180| Envision_20 }}</WRAP>
 </WRAP> </WRAP>
-</WRAP>+For more information about the Envision, visit [[https://www.thinknx.com/v4/en/envision.php| this page]].
  
 +=== ThinKnx Envision10_20 ===
  
 +All-in-one Touch Server which allows control of the home or building using a high resolution touch screen. 
 +<WRAP GROUP> <WRAP column half>
  
 +  * Octa-core Cortex A53 CPU 
 +  * Capacitive touch screen 
 +  * 10” screen 217×136 mm 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 
 +  * Consumption: 12 W Max 
 +  * 1x network port 
 +  * 1x RS-232 and 1 RS-485 serial ports
 +  * Sensors: 1x temperature sensor, 1x humidity sensor, 1x ambient luminosity sensor
  
-===== ThinKnx Solution Components ===== +</WRAP>  
-==== ThinKnx Servers ==== +<WRAP column half> {{  :envision.png?direct&200| Envision_20 }}</WRAP></WRAP> 
-During normal runtime, ThinKnx server is the logical unit of the supervision system and communicates directly with the ThinKnx clients+For more information about the Envision, visit [[https://www.thinknx.com/v4/en/envision.php| this page]].
-\\ +
-The ThinKnx servers range was born to cover all the possible installation cases of a supervision systemAll 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 reliabilityIn 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 of all, and supports all kind of functions (Security, VoIP, Audio/Video). IT is the ideal device for the majority of plants. +=== ThinKnx Rack ===
-    * 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 out the related [[http://www.thinknx.com/v3/en/compact.html|page]] on our website.// +
-\\ +
-  * **ThinKnx Micro** It is a very small device with the ability to completely control KNX systems. 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 [[http://www.thinknx.com/v3/en/micro.html|page]] on our website.// +
-\\ +
-  * **ThinKnx Micro ZWave** It is a very small device with the ability to completely control KNX and Zwave systems. 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 [[http://www.thinknx.com/v3/en/micro-zwave.html|page]] on our website.// +
-\\ +
-  * **ThinKnx Envision** All-in-one Touch Server which allows control of the home or building using a high resolution touch screen. +
-    * Quad-core ARM Cortex A9 CPU +
-    * 1 GB DDR3 SDRAM +
-    * Capacitive touch screen +
-    * 7” screen 158x93mm visible area, 1024x600 resolution or 10” screen 217x136mm visible area, 1280x800 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 [[http://www.thinknx.com/v3/en/envision.html|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 [[http://www.thinknx.com/v3/en/rack.html|page]] on our website.//+
  
-==== ThinKnx Clients ==== +It is the most powerful and expandable devicedesigned for large buildings or demanding applications.  
-Thinknx clients are all the devices connected to the network and using the Thinknx application to connect to a Thinknx server. +<WRAP GROUP> <WRAP column half>
-ThinKnx offers a wide range of native applications to allow tabletssmartphones, 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, resize the application window and visualize the mouse cursor, adapting the application to the device which the application is installed on and improving the user’s experience.  +  * Fanless processing device optimized for continuous operation 
-  * **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. +  * Mass memory on industrial Compact-Flash 
-<WRAP round important center 80%> ThinKnx 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/. </WRAP>+  * 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
  
-  * **ThinKnx for iPad** This is the app for iPad that, connecting to ThinKnx serversallows to manage automation directly from iOS tablets. It allows to control several buildings using a quick and intuitive project selector. +</WRAP> <WRAP column half> {{  :rack.png?direct&200| Rack }}</WRAP></WRAP> 
-  **ThinKnx Pocket for iPhone** This is the app for iPhone that, connecting to ThinKnx serversallows to manage automation directly from iOS phones. It allows to control several buildings using a quick and intuitive project selector. +For more information about the Rack, visit [[https://www.thinknx.com/v4/en/rack.php| this page]]. 
-  * **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.+ 
 +==== Trend Line ==== 
 + 
 +The Trend Line was designed to integrate with the KNX system and its most needed functionalities quickly and easily. It is the perfect entry level solution for residential buildings, apartments or hospitality. Certain devices in the Trend Line such as K and K2 embed stand-alone servers, allowing control of the KNX system through mobile application without the need to install a Pro Line server. Other devices such as the Piccolo operates just as smart clients and require the installation of a server (can be either Pro or Trend Line server). 
 + 
 +<WRAP tip center round 80%>All Trend Line devices can be integrated in a plant where a Pro Line server is installed, allowing the user to to operate them as client devices.</WRAP> 
 + 
 +The following devices are available in the Trend Line: 
 + 
 +  [[#thinknx_k|K]] 
 +  [[#thinknx_k2| K2]]  
 +  [[#thinknx_piccolo| Piccolo]] 
 + 
 +=== ThinKnx K === 
 + 
 +This capacitive screen can operate as a Trend Line server or as a client in an installation where a Pro Line server is the main hub. <WRAP GROUP> <WRAP column half> 
 + 
 +  * Capacitive 4.3" touch screen 
 +  * Resolution 480×720 
 +  * Temperature sensor 
 +  * Humidity sensor 
 +  * 1x KNX port 
 +  * 1x Network port 
 +  * 1x USB port 
 +  * 12-24VDC - 1A Max 
 +  * Standard automation control 
 +  * Widgets list view 
 +  * Unlimited KNX group addresses 
 +  * Unlimited clients 
 +  * Dedicated Trend Line application 
 +  * Camera monitoring 
 + 
 +</WRAP> <WRAP column half> {{  :k.png?direct&150| K}}</WRAP></WRAP> 
 + 
 +=== ThinKnx K2 === 
 + 
 +This capacitive screen can operate as a Trend Line server or as a client in an installation where a Pro Line server is the main hub. <WRAP GROUP> <WRAP column half> 
 + 
 +  * Capacitive 5.5" touch screen 
 +  * Resolution 720×1280 
 +  * Temperature sensor 
 +  * Humidity sensor 
 +  * 1x KNX port 
 +  * 1x Network port 
 +  * 12VDC - 1A Max or PoE 
 +  * Standard automation control 
 +  * Widgets list view 
 +  * Unlimited KNX group addresses 
 +  * Unlimited clients 
 +  * Dedicated Trend Line application 
 +  * Camera monitoring 
 +  * Doorcom functionality 
 + 
 +</WRAP> <WRAP column half> {{  :k2.png?direct&150| K}}</WRAP></WRAP> 
 + 
 +=== ThinKnx Piccolo === 
 + 
 +This capacitive screen operates only as a client device and requires a ThinKnx server (either Pro or Trend Line server) to control the system through a ThinKnx application. <WRAP GROUP> <WRAP column half> 
 + 
 +  * Capacitive 4" touch screen 
 +  * Resolution 480×480 
 +  * Temperature sensor 
 +  * Humidity sensor 
 +  * 1x Network port 
 +  * Power 230VAC 
 +  * Standard automation control 
 +  * Widgets list view 
 +  * Camera monitoring 
 + 
 +</WRAP> <WRAP column half> {{  :piccolo.png?direct&150| Piccolo}}</WRAP></WRAP> 
 + 
 +==== ThinKnx Brickbox ==== 
 + 
 +Using the same hardware as the Pro Line, but with completely different functionalities, the **<color #6e99c7>Brickbox</color>** is a Thinknx gateway without UI functionalities. In addition to the ports available on the Micro, Brickbox has two serial ports: one RS232 and one RS485. 
 + 
 +===== ThinKnx Clients ===== 
 + 
 +Thinknx clients are all the devices connected to the network and using the Thinknx application to connect to a Thinknx server. 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 UP Player for Windows** This application allows to control the building from any Windows device. It is an upgraded version of the Classic Thinknx Player with a totally redesigned interface and many additional features. The UP Player only works with servers using firmware 1.1.10 or above, and can only view projects created with the UP Configurator (with extension .tup). 
 + 
 +**ThinKnx Player for Windows (Classic)** 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, resize the application window and visualize the mouse cursor, adapting the application to the device which the application is installed on and improving the user’s experience. The Classic Player only works with servers using firmware 1.1.9 or below, and can only view projects created with the Classic Configurator (with extension .erg).  
 + 
 +**Thinknx UP 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 Player for Mac (Classic)** 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. This player only works with servers using firmware 1.1.9 or below, and can only view projects created with the Classic Configurator (with extension .erg). 
 + 
 +<WRAP round important center 80%> ThinKnx Player for Mac (Classic) 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/|https://get.adobe.com/air/]]. </WRAP> 
 + 
 +**Thinknx UP for iOS** This application allows to control the building from any iOS device (iPad / iPhone). It is an upgraded version of the Thinknx Pocket with a totally redesigned interface and many additional features. Thinknx UP for iOS only works with servers using firmware 1.1.10 or above, and can only view projects created with the UP Configurator (with extension .tup).  
 + 
 +**ThinKnx for iPad (Classic)** This is the app for iPad that connects to ThinKnx servers and allows to manage the automation directly from iOS tablets. It allows to control several buildings using a quick and intuitive project selector. It only works with servers using firmware 1.1.9 or below, and can only view projects created with the Classic Configurator (with extension .erg).  
 +**ThinKnx Pocket for iPhone (Classic)** This is the app for iPhone that connects to ThinKnx servers and allows to manage the automation directly from iOS phones. It allows to control several buildings using a quick and intuitive project selector. It only works with servers using firmware 1.1.9 or below, and can only view projects created with the Classic Configurator (with extension .erg).  
 + 
 +**Thinknx UP for Android** This application is used on Android tablets and smartphones to control the building automation. It is an upgraded version of the classic Thinknx for Android app with a totally redesigned interface and many additional features. It only works with servers using firmware 1.1.10 or above, and can only view projects created with the UP Configurator (with extension .tup).  
 + 
 +**ThinKnx for Android (Classic)** 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 Cloud =====
  
-==== ThinKnx Cloud ==== 
 Thinknx Cloud is used for several services in the Thinknx system: Thinknx Cloud is used for several services in the Thinknx system:
-  - **Modifying and updating the project remotely on server and clients**. Using the Thinknx Configurator, the integrator or installer can deploy the modified project to the Cloud. The server will automatically be alerted and will reboot once the new version is downloaded, and all the clients will get a notification that a newer version of the project is available to download on their devices. For more information regarding Thinknx Cloud, check out [[thinknx_cloud| this section]]. 
-  - **Automatic client connection**. In the absence of a fixed external IP address at the automated location, it is possible to use Thinknx Cloud to allow remote access to the project for all clients. They will be able to monitor their entire house from anywhere using only the Internet at no additional cost. However, some services might not be available for this option, such as answering a SIP call remotely or viewing a local IP camera from outside the house. For more information regarding Thinknx Cloud, check out [[thinknx_cloud| this section]]. 
-  - **Database for live data storage**. Every project will require to save some data for continuous monitoring, chart visualization, or monthly reporting. This data will be saved for each single server in a dedicated space on the cloud. Every time a Thinknx application is launched, the server will contact the cloud to retrieve this data, and update them as they change. Only a small amount of values is saved locally on the server. For more information regarding Thinknx Cloud, check out [[thinknx_cloud| this section]]. 
-  - **Dynamic DNS**. This option is used in the absence of a //fixed// external IP address at the automated location. Instead, the public IP address is accessible but changes after each connection renewal or on router reboot. Thinknx offers a free dynamic DNS service configurable from the server’s web page. With this service, a host name (such as //myhome.my.thinknx.net//) is associated to the public IP address of the router and the server will always be reachable through this host name no matter what the public IP address is. For more information regarding Thinknx Cloud, check out [[thinknx_cloud| this section]]. 
  
 +**Modifying and updating the project remotely on server and clients**. Using the Thinknx Configurator, the integrator or installer can deploy the modified project to the Cloud. The server will automatically be alerted and will reboot once the new version is downloaded, and all the clients will get a notification that a newer version of the project is available to download on their devices. For more information regarding Thinknx Cloud, check out [[:thinknx_cloud|this section]].
  
-{{ :sys_arch_cloud.png?direct |Thinknx Cloud Services }} +**Automatic client connection**In the absence of a fixed external IP address at the automated location, it is possible to use Thinknx Cloud to allow remote access to the project for all clients. They will be able to monitor their entire house from anywhere using only the Internet at no additional cost. However, some services might not be available for this option, such as answering a SIP call remotely or viewing a local IP camera from outside the house. For more information regarding Thinknx Cloud, check out [[:thinknx_cloud|this section]]. 
-<WRAP center 60%> <WRAP centeralign> Figure 2: Thinknx Cloud Services </WRAP>  </WRAP>+
  
-==== ThinKnx Configurator ====+**Database for live data storage**. Every project will require to save some data for continuous monitoring, chart visualization, or monthly reporting. This data will be saved for each single server in a dedicated space on the cloud. Every time a Thinknx application is launched, the server will contact the cloud to retrieve this data, and update them as they change. Only a small amount of values is saved locally on the server. For more information regarding Thinknx Cloud, check out [[:thinknx_cloud|this section]].  
 + 
 +**Dynamic DNS**. This option is used in the absence of a //fixed// external IP address at the automated location. Instead, the public IP address is accessible but changes after each connection renewal or on router reboot. Thinknx offers a free dynamic DNS service configurable from the server’s web page. With this service, a host name (such as //myhome.my.thinknx.net//) is associated to the public IP address of the router and the server will always be reachable through this host name no matter what the public IP address is. For more information regarding Thinknx Cloud, check out [[:thinknx_cloud|this section]]. 
 + 
 +{{  :sys_arch_cloud.png?direct&  |Thinknx Cloud Services }}<WRAP center 60%> <WRAP centeralign> Figure 2: Thinknx Cloud Services </WRAP> </WRAP> 
 + 
 +===== 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. 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.
Line 142: Line 290:
 Finally, the same tool allows to upload the project on client devices and ThinKnx servers with differentiated exports based on the specific user. Finally, the same tool allows to upload the project on client devices and ThinKnx servers with differentiated exports based on the specific user.
  
-For a detailed explanation of the Configurator, please refer to [[main_cons_ui| Thinknx Configurator]] chapter, or visit our [[quickguide| quick guide]] to learn how to create the first project.+For a detailed explanation of the Configurator, please refer to [[:main_cons_ui|Thinknx Configurator]] chapter, or visit our [[:quickguide| quick guide]] to learn how to create the first project.
  
-===== Communication Between Components =====+===== Server - Client Connection =====
  
-All the clients can connect to the server using two IP addresses, one local address to use inside the LAN and one host name or external address to use outside the LAN for remote access. +All the clients can connect to the server using two IP addresses, one local address to use inside the LAN and one host name or external address to use outside the LAN for remote access. It is highly recommended to configure the local IP address of the server to be fixed and not use DHCP service. Otherwise, it is possible to run into client-server connection problems when the DHCP lease expires. The fixed local address can be configured by accessing the server’s web interface using port 5051 TCP. This can be done by inputting <nowiki> http://server_ip_address:5051 </nowiki> into the web browser. In addition to **port 5051** TCP used for the web interface, the client-server connection is possible through **port 7550** TCP. **Port 5050** is used to deploy a Thinknx project from Configurator to a client’s device when using the local network instead of Thinknx Cloud. 
-\\ It is highly recommended to configure the local IP address of the server to be fixed and not use DHCP service. Otherwise, it is possible to run into client-server connection problems when the DHCP lease expires. + 
-\\ The fixed local address can be configured by accessing the server’s web interface using port 5051 TCP. This can be done by inputting <nowiki> http://server_ip_address:5051 </nowiki> into the web browser. +To allow clients a remote access to the server, multiple scenarios can be considered depending on the actual situation: 
-\\ In addition to **port 5051** TCP used for the web interface, the client-server connection is possible through **port 7550** TCP.  +  * **The existence of a static external IP address** which is directly accessible from the Internet. This option is usually sold at an additional cost by the Internet provider. In that case, the external IP address can be set inside the Configurator, and clients will try to connect directly to this IP. Since the server is usually behind a router, the router has to be configured to forward connections to the server. 
-\\ **Port 5050** is used to deploy a Thinknx project from Configurator to a client’s device when using the local network instead of Thinknx Cloud. + 
-\\ +{{  :sys_arch_remote1.png?direct&950  |Static External IP Address }} 
-\\ To allow clients a remote access to the server, multiple scenarios can be considered depending on the actual situation: +<WRAP center 60%> <WRAP centeralign> Figure 3: Static External IP Address </WRAP> </WRAP>  
-  * __The existence of a **static external IP address**__ which is directly accessible from the Internet. This option is usually sold at an additional cost by the Internet provider. In that case, the external IP address can be set inside the Configurator, and clients will try to connect directly to this IP. Since the server is usually behind a router, the router has to be configured to forward connections to the server. + 
-\\ {{ :sys_arch_remote1.png?direct&950 |Static External IP Address }} +  * **The existence of a dynamic external IP address** which is directly accessible from the Internet but changes at router reboot or after a connection renewal. In that case, and to overcome the problems tied to not having a static IP, Thinknx offers a free Dynamic DNS service configurable from the server’s web interface. With this service, a hostname will be associated to the public IP address of the router and will always be translated to the actual IP address.  
-<WRAP center 60%> <WRAP centeralign> Figure 3: Static External IP Address </WRAP>  </WRAP>\\ +{{  :sys_arch_remote2.png?direct&950  |Dynamic External IP Address }}<WRAP center 60%> <WRAP centeralign> Figure 4: Dynamic External IP Address </WRAP> </WRAP>  
-  * __The existence of a **dynamic external IP address**__ which is directly accessible from the Internet but changes at router reboot or after a connection renewal. In that case, and to overcome the problems tied to not having a static IP, Thinknx offers a free Dynamic DNS service configurable from the server’s web interface. With this service, a hostname will be associated to the public IP address of the router and will always be translated to the actual IP address. + 
-\\ {{ :sys_arch_remote2.png?direct&950 |Dynamic External IP Address }} +  * **The absence of a public IP address**. In that case, the IP given from the Internet provider is not directly reachable from the Internet because it is part of a sub-network or behind a NAT. By enabling and using Thinknx Cloud, remote clients can establish a connection to the server using a tunnel created by means of the Cloud. {{  :sys_arch_remote3.png?direct&950  |No Public IP Address }}<WRAP center 60%> <WRAP centeralign> Figure 5: No Public IP address </WRAP> </WRAP>
-<WRAP center 60%> <WRAP centeralign> Figure 4: Dynamic External IP Address </WRAP>  </WRAP>\\ +
-  * __The **absence of a public IP address**.__ In that case, the IP given from the Internet provider is not directly reachable from the Internet because it is part of a sub-network or behind a NAT. By enabling and using Thinknx Cloud, remote clients can establish a connection to the server using a tunnel created by means of the Cloud. +
-\\ {{ :sys_arch_remote3.png?direct&950 |No Public IP Address }} +
-<WRAP center 60%> <WRAP centeralign> Figure 5: No Public IP address </WRAP>  </WRAP>\\+
  
 ===== Network requirements for Thinknx services ===== ===== Network requirements for Thinknx services =====
Line 168: Line 312:
  
 <WRAP center 80%><WRAP tablewidth 100%> <WRAP center 80%><WRAP tablewidth 100%>
-^ Service                  ^ Host port and protocol                     ^ Comments                                          ^ Note ^ 
-| NTP                      | 123 (TCP and UDP) \\ outbound/inbound        | Used to sync clock with NTP servers.              |  1  | 
-| Thinknx cloud            | cloud.thinknx.eu \\ 80, 443, 24532 (TCP) outbound     | Used to connect to Thinknx cloud service          |  2  | 
-| Thinknx projects sync    | data.thinknx.eu \\ 80, 443 (TCP) outbound    | Used to download project updates from cloud        2  | 
-| Thinknx clients          | 7550 (TCP) inbound                        | Used by client to connect to server for control    3  | 
-| Internal webpage         | 5051 (TCP) inbound                        | Used to connect to server webpage for maintenance |  4  | 
-| Remote assistance        | www.pulsareng.it \\ 80, 443 (TCP) outbound   | Used to sync with remote assistance service        5  | 
-</WRAP></WRAP> 
-Notes: 
- 
-  - This service is mandatory to sync clock with internet services. Server can act as NTP server as well (inbound connection) and it is advised to use just for local network (not exposed to the internet) 
-  - These services are required when cloud connection is used. 
-  - Port 7550 inbound is only required when direct client connection is adopted. It usually requires to create port forwarding rules on router/firewall depending on network infrastructure 
-  - Access to webpages is not required and it is advised not to expose to the internet. 
-  - Remote assistance service used on request to obtain factory support 
  
 +^Service  ^Host port and protocol  ^Comments  ^Notes|
 +|NTP  |123 (TCP and UDP) \\ outbound/inbound  |Used to sync clock with NTP servers.  | ((This service is mandatory to sync clock with internet services. Server can act as NTP server as well (inbound connection) and it is advised to use just for local network (not exposed to the internet) ))  |
 +|Thinknx cloud  |*.thinknx.eu \\ 80, 443, 24532 (TCP) outbound  |Used to connect to Thinknx cloud service  | ((These services are required when cloud connection is used)) |
 +|Thinknx projects sync  | data.thinknx.eu \\  projects.thinknx.cloud \\ 80, 443 (TCP) outbound  |Used to download project updates from cloud  | ((These services are required when cloud connection is used))  |
 +|Thinknx clients  |7550 (TCP) inbound  |Used by client to connect to server for control  | ((Port 7550 inbound is only required when direct client connection is adopted. It usually requires to create port forwarding rules on router/firewall depending on network infrastructure))  |
 +|Thinknx clients (cloud)  |cloud.thinknx.eu \\ 24531 (TCP) outbound  |Used by client to connect to server using cloud for control  | ((These services are required when cloud connection is used))  |
 +|Internal webpage  |5051 (TCP) inbound  |Used to connect to server webpage for maintenance| ((Access to webpages is not required and it is advised not to expose to the internet))  |
 +|Remote assistance  |[[http://www.pulsareng.it|www.pulsareng.it]] \\  80, 443 (TCP) outbound  |Used to sync with remote assistance service  | ((Remote assistance service used on request to obtain factory support))  |
  
 +</WRAP></WRAP> 
  • sys_arch.1557827741.txt.gz
  • Last modified: 2019/05/14 11:55
  • by wikiadmin