Differences

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

--- system_objs [2019/11/19 10:55] – [Roles] ingrid
+++ system_objs [2020/07/09 14:02] – [Sonos Manager] ingrid
@@ Line 45: / Line 45: @@
     * [[#universal_gateway| Universal Gateway]]
     * [[#sms_gateway| SMS Gateway]]
-    * [[#Lutron_project| Lutron Project]]
+    * [[#Lutron| Lutron Project]]
     * [[#Gateway_tiemme| Gateway Tiemme]]
     * [[#serial_gateway| Serial Gateway]]
@@ Line 84: / Line 84: @@
   * **Server client port** Number of the TCP port needed to remotely connect with the server (outside the server network). The default port is 7550.
   * **Local IP address** IP address (for example 192.168.X.X) needed to connect with the server from clients that operate in the server LAN.
+  * **KNXNet/IP interface** if enabled, the Thinknx server can be used as a KNXNet/IP interface, allowing KNX programming from the ETS software for example. More information are available on the [[knxnet_ip| KNXnet/IP]] guide.
+  * **KNXNet/IP different IP** if enabled, permits to choose a different KNXNet/IP interface to connect and access the KNX bus.
+  * **Clients Ph. Address Base** base physical address for the clients connections.
+  * **Client number** number of supported client tunnel connections.
+  * **KNXNet/IP router** If enabled, the server will also route traffic from TP to multicast IP and vice versa, allowing to connect different parts of a KNX system together over IP. More information are available on the [[knxnet_ip| KNXnet/IP]] guide.
   * **System name** Name to identify the project once it has been uploaded to the server.
   * **Location** Name of the location where the system is installed.
@@ Line 244: / Line 249: @@
   * **Controller type** Selection among three possible models:
-    * //Mitsubishi AG 150:// Device IP address has to be typed in the empty slot to use this controller.
+    * //**Mitsubishi AG 150:**// This controller permits to interact with Mitsubishi G50, AG150 and newer controllers with Mitsubishi XML protocol (this protocol needs to be enabled on the Mitsubishi side).
-    * //KNX interface simple:// This controller allows to set mode and speed using standard 1 byte objects.
+    * //**KNX interface simple:**// This controller allows to set mode and speed using standard 1 byte objects.
-    * //KNX interface extended:// This controller allows to set mode and speed using 1 bit objects.\\
+    * //**KNX interface extended:**// This controller allows to set mode and speed using 1 bit objects.\\
+    * //**CoolMaster Net:**// This controller permits to talk with CoolAutomation devices via Ethernet.
-  If Controller type is ”Mitsubishi AG 150” the following property will appear to define the device address:\\
+Select the ”Devices” property and click on the button displayed on the right to open the devices editor window; click on ”Add” button and adjust the properties in the grid.
-      * **IP address** HVAC controller IP address.\\
+==== CoolMaster Net ====
+CoolAutomation devices permits to directly talk with many Air conditioning brands including Daikin and many others. It is connected directly to the AC bus and can control with a single interface all the units connected to the bus.
+Integration with Thinknx is directly through the network and permits to control devices under CoolMaster directly within Thinknx. It is not required that the CoolMaster has KNX port. The communication with the KNX devices will be through the server and the server itself will act as gateway to and from KNX. The control of all the split units connected with CoolMaster will be possible using standard HVAC pop-ups in Thinknx.
+{{ :cmn.png?direct&400 |CoolMaster Net}}
+On the system node the following properties will appear:\\
+    * **IP address** HVAC Controller IP address.
+    * **Port number** TCP/IP port for Ethernet connection. For example, 10102.
   * **Devices** List of HVAC devices linked to the system.
-==== Adding a HVAC device ====
+These are the properties for the single device:
+    * //**Name:**// Device label
+    * //**Internal unit ID:**// unit identification from CoolMasterNet manual. The format should be Ln.xyz. For example, for indoor unit 3 on line 2, ID will be L2.003. To control multiple units on the line, "*" can be used. Please refer to CoolAutomation documentation for more details on the internal devices naming conventions.
+    * //**KNX On/Off command group**// 1-bit group to switch the device on/off from KNX
+    * //**KNX On/Off feedback group**// 1-bit group to receive feedback regarding on/off status of the device
+    * //**KNX Fan command group:**// 1-byte group to switch device fan speed from KNX.
+    * //**KNX Fan feedback group:**// 1-byte group to receive feedback regarding fan speed status of the device
+    * //**KNX Temperature setpoint command group**// 2-byte DPT9 group to set the setpoint temperature for the device from KNX
+    * //**KNX Temperature setpoint feedback group**// 2-byte DPT9 group to receive feedback regarding actual setpoint from the device.
+    * //**KNX Mode command group:**// 1-byte group to switch device modality from KNX.
+    * //**KNX Mode feedback group:**// 1-byte group to receive feedback regarding modality of the device.
+    * //**Actual temperature from internal unit KNX group**// 2-byte DPT9 group to receive actual temperature read from the device (only available if supported by the device)
+    * //**Value fan min:**// value for minimum fan speed. It will be sent to fan command group to set speed and, if received in fan feedback group, minimum speed will be recognized (1-byte value).
+    * //**value fan middle:**// value for middle fan speed. It will be sent to fan command group to set speed and, if received in fan feedback group, middle speed will be recognized (1-byte value).
+    * //**value fan max:**// value for maximum fan speed. It will be sent to fan command group to set speed and, if received in fan feedback group, maximum speed will be recognized (1-byte value).
+    * //**Value Cool Mode:**// value that corresponds to Cool Modality for mode group (1-byte).
+    * //**Value Heat Mode:**// value that corresponds to Heat Modality for mode group (1-byte).
+    * //**Value Dry Mode:**// value that corresponds to Dry Modality for mode group (1-byte).
+    * //**Value Fan Mode:**// value that corresponds to Fan Modality for mode group (1-byte).
+    * //**Enable regulator:**// if enabled, the regulator features will be active. This way, the object will act as a thermostat.
-Select the ”Devices” property and click on the button displayed on the right to open the devices editor window; click on ”Add” button and adjust the properties in the grid.
 ==== Mitsubishi device ====
+If Controller type is ”//**Mitsubishi AG 150**//” the following property will appear to define the device address:\\
+    * **IP address** HVAC controller IP address.\\
+These are the properties for the single device:
   * **Name** Device name.
   * **Device index** Index associated to the device inside the controller.
@@ Line 1162: / Line 1201: @@
 {{ :system_obj_-_modbus.png?nolink&100 |}}
-It allows to integrate Modbus devices.
+It allows to integrate Modbus devices when Thinknx server is used as Master.
   * **Communication Type** Define the method and mean of communication. Serial over TCP is used when a Serial Server is used.\\ If in the property ”Communication Type” is selected the setting ”Modbus Serial”, the following properties will appear:
-    * Port Number: Serial port number. It can be between 0 and 3. For USB use 10.
+    * Port Number: Serial port number that changes depending on the server used:
+      * Compact: use 0.
+      * Rack: for the 2 RS-232 ports use 0 and 1. For the additional green ports use 2 and 3.
+      * Brickbox: for RS-232 use 4. For RS-485 use 5.
+      * When using a USB port, use 10.
     * Baud Rate: Modbus Baud Rate
     * Data Length: Number of bits for data
@@ Line 1202: / Line 1245: @@
     * **Selected bits mask** mask value of the selected bits to be changed.
 ++++
+===== Gateway Modbus Slave=====
+{{ :system_obj_-_modbus.png?nolink&100 |}}
+It allows to integrate Modbus devices when Thinknx server is used as Slave.
+  * **Communication Type** Define the method and mean of communication. Serial over TCP is used when a Serial Server is used.\\ If in the property ”Communication Type” is selected the setting ”Modbus Serial”, the following properties will appear:
+    * Port Number: Serial port number that changes depending on the server used:
+      * Compact: use 0.
+      * Rack: for the 2 RS-232 ports use 0 and 1. For the additional green ports use 2 and 3.
+      * Brickbox: for RS-232 use 4. For RS-485 use 5.
+      * When using a USB port, use 10.
+    * Baud Rate: Modbus Baud Rate
+    * Data Length: Number of bits for data
+    * Parity: Parity check modality
+    * Stop Bits: Number of stop bits.
+    * Custom Timing: if enabled, it allows to change the waiting times below:
+      * waiting time after enabling RTS before the writing begins.
+      * waiting time after writing before disabling RTS.
+      * waiting time after disabling RTS before the reading begins.
+  *  **Device Address** Address of the slave device (1byte) to be used on the bus for identification.
+  *  **Modbus Type** variant of the Modbus protocol to use for communication. Select between RTU (mostly used) and ASCII.
+  *  **Datapoints** Datapoints collection
 ===== Gateway MyHome =====
@@ Line 1210: / Line 1280: @@
   * **IP Address** IP address of the device or of the serial server
-  * **Port Number** Serial port number. It can be between 0 and 3. For USB use 10
+  * **Port Number** Serial port number that changes depending on the server used:
+      * Compact: use 0.
+      * Rack: for the 2 RS-232 ports use 0 and 1. For the additional green ports use 2 and 3.
+      * Brickbox: for RS-232 use 4. For RS-485 use 5.
+      * When using a USB port, use 10.
   * **Lights** Collection of lights
   * **Automation**
@@ Line 1317: / Line 1391: @@
 {{ :system_obj_-_zwave.png?nolink&100 |}}
 It allows to integrate Z-Wave devices. Without any gateway, the result is a reliable and easy-to-use system with a bidirectional connection between Z-Wave and other standards such as KNX.
+<WRAP important center round 60%> For a full list of all the compatible Z-wave devices with Thinknx server, visit this link here http://www.thinknx.com/v3/php/products.php. </WRAP>
   * **Use internal controller** If enable, it will be used the server internal Z-Wave controller. If disabled it will be possible to use an external Z-Wave controller. This option is only used during configuration phase. If disabled, following properties will appear:
@@ Line 1589: / Line 1665: @@
 This object represents the interface between ThinKnx system and a third-party device connected through serial port. It makes possible to send commands through the serial port to the device.
-  * **Port Number** Serial port number. It can be between 0 and 3. For USB use 10.
+  * **Port Number** Serial port number that changes depending on the server used:
+      * Compact: use 0.
+      * Rack: for the 2 RS-232 ports use 0 and 1. For the additional green ports use 2 and 3.
+      * Brickbox: for RS-232 use 4. For RS-485 use 5.
+      * When using a USB port, use 10.
   * **Baud Rate** Serial port baud rate.
   * **Data Length** Number of bits for data.
@@ Line 1850: / Line 1930: @@
      * IP address: Device IP address.
      * Port number: TCP/IP port number for ethernet connection.\\ If the property ”Use serial port” is set to ”Enabled”, the following property will be displayed:
-     * Serial port: Server serial port number.
+     * Serial port: Serial port number that changes depending on the server used:
+      * Compact: use 0.
+      * Rack: for the 2 RS-232 ports use 0 and 1. For the additional green ports use 2 and 3.
+      * Brickbox: for RS-232 use 4. For RS-485 use 5.
+      * When using a USB port, use 10.
 ==== Object commands ====
@@ Line 1887: / Line 1971: @@
     * IP address: Device IP address.
     * Port number: TCP/IP port number for ethernet connection.\\ If the property ”Use serial port” is set to ”Enabled”, the following property will be displayed:
-    * Serial port: Server serial port number.
+    * Serial port: Serial port number that changes depending on the server used:
+      * Compact: use 0.
+      * Rack: for the 2 RS-232 ports use 0 and 1. For the additional green ports use 2 and 3.
+      * Brickbox: for RS-232 use 4. For RS-485 use 5.
+      * When using a USB port, use 10.
   * **Mute KNX Group** KNX group for mute command.
@@ Line 1930: / Line 2018: @@
     * //TV brand LCD//
     * //TV brand NEC//
-  * **Serial port** Server serial port number.
+  * **Serial port** Serial port number that changes depending on the server used:
+      * Compact: use 0.
+      * Rack: for the 2 RS-232 ports use 0 and 1. For the additional green ports use 2 and 3.
+      * Brickbox: for RS-232 use 4. For RS-485 use 5.
+      * When using a USB port, use 10.
 ==== Object Commands ====
@@ Line 1972: / Line 2064: @@
     * IP address: Device IP address.
     * Port number: TCP/IP port number for ethernet connection.\\ If the property ”Use serial port” is set to ”Enabled”, the following property will be displayed:
-    * Serial port: Server serial port number.
+    * Serial port: Serial port number that changes depending on the server used:
+      * Compact: use 0.
+      * Rack: for the 2 RS-232 ports use 0 and 1. For the additional green ports use 2 and 3.
+      * Brickbox: for RS-232 use 4. For RS-485 use 5.
+      * When using a USB port, use 10.
 ==== Object commands ====
@@ Line 2218: / Line 2313: @@
 This object represents the complete integration of Sonos systems in ThinKnx, it allows to control and receive feedbacks from Sonos players directly through network without creating more traffic on KNX. In this way, all the commands and feedbacks can be available on KNX only if the installer really need them.
+<WRAP important center align round 80%> This object is currently tested with Sonos S1 system. For more information on S2, contact our support team. </WRAP>
   * **Players** Sonos players configured in ThinKnx system.