Showing posts with label Anti-Passback. Show all posts

M-Kadex & K-Kadex Anti Passback Setup



Introduction
Anti-passback is a security system feature that is primarily used to prevent users from passing their credentials (such as access cards) back for another user to borrow and to stop users from entering an area by simply following or tailgating another user.   
For this article, we will guide you on the anti-passback setup for model m-Kadex and k-Kadex.

Requirement
    - M-Kadex (Master)
    - K-Kadex (Slave)
    - Power Supply 12VDC
    - Electromagnetic lock (EM Lock)
    - Ingress/TCMS V3 software

Wiring Diagram


Steps           
    -Please refer to the diagram above for the Master-Slave connection.
    -Connect the master reader to the server or PC using TCP/IP port.
    -Connect with Ingress/TCMS V3 software.
    -At the software, select DEVICE -> select device -> Access Control -> Edit -> Select Anti-        Passback Option.

    - Save and synchronize.
 
How does it work?
    -When a user accessed the Master device (IN door), you can see ‘Access Denied’ sign             appeared when the user tries to enter at the same door again. 


    -You can only access the Master device again when you leave the area or access the Slave     device (OUT/exit door)
   


Note: If some of the screenshots or steps viewed here are different from the ones in the current system, this is due to our continuous effort to improve our system from time to time. Please notify us at info@fingertec.com, we will update it as soon as possible.

R3 - R3 Master -Slave Anti-Passback 2 Doors Wiring Diagram & Setting



Some companies look for full control of their own premises. Requirements such as having just one way in and out with two doors to control the access movement within the building. This can be done by setting in our R3 device using the anti-passback feature. This setting will not have any problem with our current device and can be done easily with our Master-slave connection. Due to the distinct requirements raised by certain customers, the Master-Slave setup for door access solution using the Master-Master setup is still valid. In this tips we provide, we are using two R3 devices as an example for this Master-slave Anti-passback setting configuration and connection, please follow the instructions below:

1) Configure both R3 to change its function to support the Master slave setting by following the previous tip “Modifying Setup from Master-Master to Master-Slave”

2) Connect the R3 ( MASTER) - R3 (SLAVE) follow the connection diagram below:

For your better understanding, here is the connection block diagram:

3) For this connection, the External Relay 12VDC required for controlling the EM lock only opens accordingly with an anti-passback setting.


Note: If some of the screenshots or steps viewed here are different from the ones in the current system, this is due to our continuous effort to improve our system from time to time. Please notify us at info@timeteccloud.com, we will update it as soon as possible.

R3 Anti-Passback Bug Fixed!


Screen Shot 2017-06-15 at 1.40.50 PM.png


Introduction

As per our customers’ feedback, users would fail to verify at R3 after using the terminal for some time. Our technical team has run a series of tests on the device and found the bug, which is related to anti-pass back feature.

Bug Description
R3 with anti-pass back feature turned on, after an anti-pass back verification is recorded, the device can not verify user anymore.

Solution

To solve the bug, please update device’s firmware to latest version.
Please contact your local reseller or Fingertec Support team to retrieve latest firmware update.


Benefits of Anti-Pass Back Feature in R3


The anti-pass back feature of the R3 device allows the admin to prevent users from tailgating behind other people. It does this by denying access to users that verify at the same terminal consecutively. For example, if the user enters a zone without verifying at the entrance terminal, they will not be able to leave that zone when they verify themselves at the exit terminal. This feature requires a slave device (usually R2c) in conjunction with R3 to function. Both will control the same door, one for the entrance and one for the exit.







Configure Anti-Passback Mode Using Ingress


In FingerTec's integrated access control application, Ingress, there is a function called anti-passback. This function is primarily used to prevent the misuse of access control systems by establishing a specific sequence in which access cards must be used in order for the system to grant access. For instance, users can be stopped from entering an area a second time without first leaving it.

If you would like to move straight to configuring the anti-passback feature in Ingress, do skip to the ‘Configuration Steps (Standalone Device)’ section below for a step-by-step guide. Those steps are applicable when you are using standalone devices e.g R2, Kadex and etc. However, if you are using Ingressus controller, please refer to another post here.

Before we proceed to the configuration steps though, let’s look at some of the basic questions users may have on this feature:
Q1:  If I have “X” number of doors and require the Anti-passback function, how many devices should I use?
One Door: Install 2 standalone devices that must be configured with a Master and slave connection for entry and exit at the door. Also, please be informed that for standalone devices, anti-passback can only be configured on one door.
2 to 4 doors: Install Ingressus II (up to 2 doors) or Ingressus IV (up to 4 doors) with slave readers. e.g. If there are 2 doors, after activating the anti-passback between Door 1 and Door 2, users must have an Out record from Door 1, before granted access to Door 2. For more information on how to use an Ingressus controller for this, refer here.
More than 4 doors: Currently, the available devices do not support anti-passback for more than 4 doors. However, please write in to us at support@fingertec.com with your requirements for us to provide you with our recommendations.

Q2: Then which are the models that support the Anti-passback function? 
Fingerprint models: R2, R3, H2i, Q2i and the R2c slave device
Card: Kadex, m-Kadex with k-Kadex, i-Kadex slave
Facial Recognition: Face ID3
Controller: Ingressus I, Ingressus II, Ingressus IV
For more information on the features available for all of our devices, please click here.

Q3: For the configuration on one door, can we use 2 master devices, e.g. 2 Kadex devices, one Kadex will be 'In' and the other 'Out'?
You must configure the first reader as Master and second reader as Slave before you can set the anti-passback function in Ingress. For more information, refer to tips here.

Configuration Steps (Standalone Device):
1. Click Device > Click on the terminal where you wish to apply the anti-passback mode.


2. Click Access Control > Edit.


3. Choose the anti-passback mode you wish to apply and click Save. Click here for more info on anti-passback modes.


4. Click OK to confirm the changes you have made.


5. Click Upload Device Settings > Click Yes to confirm your selection.


6. Click Start Synchronize.


7. Click Close.


8. Click at Other > Reboot Device > Click Yes to confirm your selection. After the reboot, the selected terminal will function according to the configurations you have made. Voila!




Antipassback Explained



Anti-Passback prevents users from tailgating through controlled areas by tracking the entry and exit counts. A user can only exit an area that they have already entered and can only enter an area that they previously exited. If a user tailgates onto a site, the exit keypad will deny them exit from the site because they are not logged into the area. If a user is onsite and tailgates off of the site, they will be denied entrance next time they try to enter. Anti-Passback is a function that should only be used on High Security sites where users can be trained on its use.

It is recommendable to install the slave terminal outside the premises while the master terminal at the inside. The aforementioned installation is to prevent the master terminal from any unnecessary access and also prolong its life span. The slave terminal is a lot cheaper and easier to replace if any mishap occurs.

The slave terminal will be recording all the IN transactions (In terminal) while the master is capturing the OUT transactions (Out terminal). The master terminal will record all the transaction logs with the terminal ID, hence there will not be any confusion which transaction is taken from which terminal. The administrator can identify which terminal the user uses to verify and also gain access in to or out of the premises. Please refer to the table below before you apply the antipassback settings.




Written by Henry Pang