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
system_objs [2019/10/28 09:31]
ingrid [System Objects]
system_objs [2020/04/17 10:53] (current)
ingrid
Line 45: Line 45:
     * [[#​universal_gateway| Universal Gateway]]     * [[#​universal_gateway| Universal Gateway]]
     * [[#​sms_gateway| SMS Gateway]]     * [[#​sms_gateway| SMS Gateway]]
-    * [[#Lutron_project| Lutron Project]]+    * [[#Lutron| Lutron Project]]
     * [[#​Gateway_tiemme| Gateway Tiemme]]     * [[#​Gateway_tiemme| Gateway Tiemme]]
     * [[#​serial_gateway| Serial Gateway]]     * [[#​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.   * **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.   * **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.   * **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.   * **Location** Name of the location where the system is installed.
Line 606: Line 611:
  
 ===== Access Control ===== ===== Access Control =====
-This section ​is coming soon.+The Thinknx Access Control object permits to enhance the level of automation and security of the home/​building where it is applied. It can be adapted to sectors where long term expirations are required such as service and industry sectors, but also applies to the hospitality sector where credentials are usually short term, and remote management is required. 
 + 
 +The Access Control object can communicate directly with the KNX system because of the bus connector on the Thinknx server, making the integration very easy and flexible. Any standard KNX keypad can be used as an access keypad, and the buttons as code entries. Once the code is inserted, any lock or switch connected to a KNX actuator can be operated. In addition, communication with Wiegand technology is possible through the Thinknx-Wiegand adapter, making it possible to install a suitable RFID or biometric reader. 
 + 
 +{{ :​access_control_diagram.png?​direct&​800 |}} 
 +<WRAP center 60%> <WRAP centeralign>​ Access Control Solution </​WRAP> ​ </​WRAP>​ 
 + 
 +  * **Label** Text to identify the object 
 +  * **Code length** Number of digits inside the access codes. All codes should have the same number of digits. If length of codes is 6, a valid code will be 123456. 
 +  * **Code numbers** Numbers contained inside the code, starting from 0. This depends on the number of buttons in keypads. If code numbers ​is 5, codes can contain the numbers 0,​1,​2,​3,​4. 
 +  * **Confirm time (ms)** Maximum time between two consecutive keypress. Once the confirm time has been exceeded, the start of a new code will considered on keypress. This time is useful to start a new sequence if a mistake has been made when entering the code. 
 +  * **Guard wrong codes** if enabled, it is possible to monitor wrong codes attempts, and generate events once a threshold has been reached. 
 +    * **Number of attempts** Maximum number of attempts with wrong codes allowed before triggering the event. 
 +    * **attempts interval (s)** duration in seconds used to count the number of wrong attempts before triggering the event. If the number of wrong attempts exceeds the number of attempts set previously during the attempt interval, then the event for wrong codes will be fired. 
 + 
 +==== Keypad prototypes ====  
 +Collection of prototypes used for the installed keypads. To add and configure a prototype, click on the small button to the right to access the prototype creator window. For each added prototype, the following properties are available:​ 
 +  * **Name** label of the prototype used. 
 +  * **Technology** technology used for the created protoype. The available options are: 
 +    * Doory (Blumotix) 
 +    * Generic KNX 
 +    * Generic Wiegand //coming soon// 
 +    * Wiegand over network //coming soon// 
 +If "​Generic KNX" was selected as **Technology**,​ the below parameters are available:​ 
 +  * **KNX Data Type** Data type used on the KNX buttons to send the access code digitsEach button can be configured to send a 1bit object to a different KNX group, or send a certain value on a 1byte object corresponding to the digit on the same KNX group. 
 +  * **Delete Key** if enabled, this option will delete the inserted sequence and start a new one before the "​confirm time" exipration. 
 +  * **Confirm tone** if enabled, the system will generate an event "​confirm tone" in case of successful attempt. 
 +  * **Keys** //only visible if **KNX Data Type** is DPT 1 (bit).// This parameter holds the keys collection used to enter a code. Clicking on the small right button will open the Keys Manager. From there, it is possible to configure every single key. Each key has a **name**, **key type** and a **group address**. 
 +  * **KNX group for keys** //only visible if **KNX Data Type** is DPT 5 (Unsigned byte).// It holds the group address used on the keypad to sen the different code digits. A telegram with value 4 means that button 4 has been pressed on the keypad. 
 + 
 + 
 +==== Keypads ==== 
 +This parameter holds the collection of keypads used and installed on the plant. At least one keypad protocol must be created prior adding the keypads. Clicking on the small button to the right will open the Keypads Manager. Each added keypad will have the following parameters:​ 
 +  * **Name** device label 
 +  * **Prototype** communication prototype used for this device. A prototype must be created in **Keypads Prototype** in order to view it in the list here. 
 +  * **KNX physical address** physical address of the device. 
 +  * **KNX group for code enabled** KNX group used by keypad to signal that the code is enabled (1 bit data type). 
 +  * **KNX group for storing/​deleting codes** KNX group to store and delete codes from the keypad (10 bytes data type). 
 +  * **KNX group for erase request** KNX group to erase codes from the keypad (1 bit data type). 
 +  * **Command if fail** command to execute in case of failed entry attempt. 
 +  * **Command if success** command to execute in case of successful entry. 
 +  * **command for tone** command to execute to play tone. 
 +==== Areas ==== 
 +This parameter holds the collection of all the areas (rooms or part of the building) limited by one or more access control keypads. By clicking on the small button to the right, the Area Manager is accessible. Each added area will have the following parameters:​ 
 +  * **Name** label of the area. 
 +  * **Entrance doors** allows you to select the checkers that are used on site to enter this specific area. The checkers should be created first in the **Keypads** collection. 
 +  * ** Dual flow** id disabled, the entrance checkers will be considered for both entrance and exit. If enabled, it means the area has differet doors/​checkers for entrance and exit. It permits to distinguish entrance and exit events and eventually count the people inside the area. 
 +  * **Exit doors** //only visible if **Dual flow** is enabled.// allows you to select the checkers that are used on site to exit this specific area. The checkers should be created first in the **Keypads** collection. 
 +  * **Count persons** //only visible if **Dual flow** is enabled.// If enabled, the system will count the number of persons inside the area based on the entrance and exit events. 
 +  * **Success enter command** Command to execute in case of successful entrance event. 
 +  * **Success exit command** Command to execute in case of successful exit event. 
 +  * **Nobody command** //only visit if **Count persons** is enabled.// Command to execute in case nobody is in the area. 
 +  * **KNX group force closed** KNX group (1 bit DPT1) to force all doors/​checkers to refuse any code. 
 +  * **KNX group force open** KNX group (1 bit DPT1) to force all doors/​checkers to accept any code. 
 +  * **KNX group valid enter** KNX gorup (1bit DPT1) to signal a valid entrance into the area. 
 +  * **KNX group valide exit** KNX group (1bit DPT1) to signal a valid exit from the area. 
 + 
 +==== Timing ==== 
 +// information coming soon// 
 +==== Roles ==== 
 + 
 +// information coming soon//
  
 ====== Logic ====== ====== Logic ======
Line 1104: Line 1170:
  
   * **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:   * **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 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     * Baud Rate: Modbus Baud Rate
     * Data Length: Number of bits for data     * Data Length: Number of bits for data
Line 1149: Line 1219:
  
   * **IP Address** IP address of the device or of the serial server   * **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 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   * **Lights** Collection of lights
   * **Automation** ​   * **Automation** ​
Line 1256: Line 1330:
 {{ :​system_obj_-_zwave.png?​nolink&​100 |}} {{ :​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.+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:   * **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 1528: Line 1604:
 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. 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 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.   * **Baud Rate** Serial port baud rate.
   * **Data Length** Number of bits for data.   * **Data Length** Number of bits for data.
Line 1789: Line 1869:
      * IP address: Device IP address.      * 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:      * 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 ==== ==== Object commands ====
Line 1826: Line 1910:
     * IP address: Device IP address.     * 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:     * 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.   * **Mute KNX Group** KNX group for mute command.
  
Line 1869: Line 1957:
     * //TV brand LCD//     * //TV brand LCD//
     * //TV brand NEC//     * //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 ==== ==== Object Commands ====
Line 1911: Line 2003:
     * IP address: Device IP address.     * 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:     * 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 ==== ==== Object commands ====