Differences

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

--- access_control [2020/07/22 14:30] – [Application 1: Virtual Keypad] ingrid
+++ access_control [2023/06/06 10:25] – [Application 1: Virtual Keypad] ingrid
@@ Line 70: / Line 70: @@
   * **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 code enabled** //only visible if keypad has **Doory (Blumotix)** as prototype// 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 storing/deleting codes** //only visible if keypad has **Doory (Blumotix)** as prototype// 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).
+  * **KNX group for erase request** //only visible if keypad has **Doory (Blumotix)** as prototype// 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.
+  * **command for tone** //only visible if keypad has **Doory (Blumotix)** as prototype// 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.
+  * ** Dual flow** id disabled, the entrance checkers will be considered for both entrance and exit. If enabled, it means the area has different 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.
@@ Line 95: / Line 96: @@
   * **KNX group n.persons** KNX group (2byte unsigned integer - DPT7) to signal the number of persons in the area.
-=== Timing ===
-This parameter allows to configure timing restrictions for roles. Clicking on the small button to the right will open the Time Manager. Each added element has the following parameter:
-  * **Name** label of timing
-  * **Time slots** time slots applied for the timing schedule created. clicking on the small button to the right will access the Time Slots Manager. For each slot, the below parameters are available:
-    * **Name**
-    * **From** Start of time slot
-    * **To** End of time slot
-    * **Days of week** Days of the week selection to apply the time slot
 === Roles ===
@@ Line 117: / Line 110: @@
   -   Configure a time range for this code's validity.
   - 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.
+To allow direct access to the Access Control page, the Manager can use the link below, making sure to fill the proper IP address and password for the server:
+http://localhost:5051/login.html?login=login&direct_login&username=service&password=password&redirect=access_control_s.html
+{{ :access_control_webpage.png?direct&600 |}}
+<WRAP center 60%> <WRAP centeralign> Figure 4: Access Control Webpage </WRAP>  </WRAP>
 ===== Application 1: Virtual Keypad =====
-This application does not require any additional hardware to be installed on site. With the Access Control module configured inside the Configurator, the integrator will be able to provide the user with an extra level of security for certain scenarios or logic functions. To get a sample of the project that contains the virtual keypad, please contact us on **info@thinknx.com**.
+This application does not require any additional hardware to be installed on site. With the Access Control module configured inside the Configurator, the integrator will be able to provide the user with an extra level of security for certain scenarios or logic functions.
+Click on the button below to get a sample of the project that contains the virtual keyad:
+<WRAP button centeralign> \\ {{:KNX_Virtual_Alarm_Keypad.zip|Download Project}}</WRAP>
 <WRAP group>