access_control

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
Next revisionBoth sides next revision
access_control [2019/12/11 08:55] – [ViaVai Access Control] ingridaccess_control [2020/07/21 15:52] – [Phase 1: Thinknx Configurator] ingrid
Line 42: Line 42:
   * **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 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.   * **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.
 +  * **Zero included** Permits to choose if zero (0) should be part of the code or not. If code number is 3, and zero is included, the numbers used inside the code are 0,1,2. If zero is not included, the numbers are 1,2,3.
   * **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.   * **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.   * **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. +    * **Number of attempts** Maximum number of attempts with wrong codes allowed before triggering an event if tried within a certain guard time
-    * **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.+    * **attempts interval (s)** duration in seconds used to count the number of wrong code 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 === === Keypad prototypes ===
Line 57: Line 58:
 If "Generic KNX" was selected as **Technology**, the below parameters are available: 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 digits. Each 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.   * **KNX Data Type** Data type used on the KNX buttons to send the access code digits. Each 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.+  * **Delete Key** if enabled, this option will delete the inserted sequence and start a new one before the "confirm time" expiration.
   * **Confirm tone** if enabled, the system will generate an event "confirm tone" in case of successful attempt.   * **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**.   * **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**.
Line 84: Line 85:
   * **Success exit command** Command to execute in case of successful exit 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.   * **Nobody command** //only visit if **Count persons** is enabled.// Command to execute in case nobody is in the area.
 +  * **Somebody command** //only visible if **Count persons** is enabled.// Command to execute in case somebody enters the area first.
   * **KNX group force closed** KNX group (1 bit DPT1) to force all doors/checkers to refuse any code.   * **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 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 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.   * **KNX group valide exit** KNX group (1bit DPT1) to signal a valid exit from the area.
 +  * **KNX group someone inside** //only visit if **Count persons** is enabled.// KNX group (1bit DPT1) to signal somebody is inside the area.
 +  * **KNX group nobody inside** //only visit if **Count persons** is enabled.// KNX group (1bit DPT1) to signal that nobody is inside the area.
 +  * **KNX group n.persons** KNX group (2byte unsigned integer - DPT7) to signal the number of persons in the area.
  
 === Timing === === Timing ===
Line 112: Line 117:
   - Save the code. A new entry will show in the table above with the added information. The admin will be able to edit this entry or delete it altogether.   - Save the code. A new entry will show in the table above with the added information. The admin will be able to edit this entry or delete it altogether.
  
-===== Application 1: Hospitality ===== +===== Application 1: Offices =====
-The Thinknx Access Control brings more value to the Hospitality sector,  enhancing the overall experience of the guests while maintaining communication between the different systems installed. Using the Thinknx server, the automation in guest rooms can be based on any technology supported by the server such as KNX, Zwave, Modbus, and more. The hotel can also take advantage of the fully fledged application proposed by Thinknx, which will be branded with the content from the hotel and used by the guests to control the different gates as well as explore all the facilities and amenities.+
  
-{{ :access_control_hotels1.png?direct&900 |}} 
-<WRAP center 60%> <WRAP centeralign> Figure 4: Access Control - Hospitality </WRAP>  </WRAP> 
  
-==== How it works? ==== 
  • access_control.txt
  • Last modified: 2023/06/06 10:28
  • by ingrid