Showing posts with label R2. Show all posts

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 [email protected], we will update it as soon as possible.

Access Combo and Anti Passback Settings for R2 & R2c



Introduction
Access Combo is an access control function that requires verifications to be done by a combination of different users. This function is suitable for highly-secured rooms or vaults that need more than senior-level employees from different departments to verify their identities before the door can be accessed. This tip will explain how to set this function in case your company would want to use it.

Steps and Procedures
To set up an access combo for two persons, each person must be assigned to a different group and a different combination
To set up a group and assign a user into a group.
Menu > Options > Access options > User acc opts > ”define user pin” example (101) > Belong to GRP “1”.


Repeat Step 1 for the second user: -
Menu > Options > Access options > User acc opts > “define user pin” example (102) > Belong to GRP “2”.


To assign two persons for an operation combo
2.1 We need to create a combo name, in this example is Combo No 1.
Menu > Options > Access Options > Access Comb > Comb No 1 > OK.


Next, we need to assign two persons in this Operation Combo:-
Person number one belongs to GROUP “1” and Person number two belongs to GROUP “2”.


3. Access Combo For three Persons
Below is an example of Access Combo for three persons but the access can be granted by only two persons at one time: -
3.1 Repeat Step 1 for User Number 3 that belongs to Group 3:-
Menu > Options > Access options > User acc opts > “define user pin” example (103) > Belong to GRP “3”


3.2 Create another combo named as Combo No 2:-
Menu > Options > Access options > Access Comb > Comb No 2 > OK: -


In Combo No 2, the users must be assigned as:-
Person number one belongs to GRP “1” and Person number three belongs to GRP “3”.


3.3 Create another combo named as Combo 3: -
Menu > Options > Access options > Access Comb > Comb No. 3 > OK: -


In Combo No. 3, the users must be assigned as:-
Person number one belongs to GRP “2” and Person number two belongs to GRP “3”.
When the settings have been done, and the door access is assigned with Access Combo function, the relevant people’s fingerprints have to be presented at the door in order to access it.

Anti Passback for One Time IN, One Time Out for R2c (Slave) and R2

Anti Passback is a feature that 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 been entered and can only enter an area that they have been previously exited.

How to Use
First, we need to determine which device will be assigned as IN and OUT, depends on the installation of the device.

If the R2 has been determined as IN for the door, you can change the configuration as below: -



Menu > Access Options > Slave Unit “Y”
If the R2c (Slave) has been determined as IN for the door, you can change the configuration as below: -

Menu > Access Options > Slave Unit “N”

The configuration for an Anti Passback can be set as below: -
Menu > Options > System opt > Adv Option > Anti Passback NoA 

Menu > Options > System opt > Adv option > Anti Passback “In Out” > OK > Esc > Save

If the configuration doesn't work, it means that the CMOS battery inside the R2 has already drained. To fix this, change the battery CR11220 inside the R2 and all enrolled users have to be *deleted. Then, re-enroll the users via Ingress software. 

*Please make sure to do the back up from the device before you delete the enrolled users.

NOTE: For R2 Firmware, the version is 5114-07. Once you have checked the firmware version,  key in the number “6 1 6 1” and then press the “Up” button.


If you find the firmware version is different from the picture above, please contact [email protected] to request for an assistance to update the firmware.

Note: If any of the screenshots or steps in this manual are different from the current system, it is due to our continuous effort to improve our system from time to time. Please notify us at [email protected]. We will update it as soon as possible.






How To Pair QR110 (MiFare) With FingerTec Master Readers




Introduction
FingerTec QR110 is a slave QR code reader for door access, and recently this model has been designed to also read MiFare card. This is a quick guide on how to pair QR110 (MiFare) with FingerTec Master Readers.

For information on QR110 (RFID) please refer to this post:
How to pair FingerTec QR110 Slave Reader with FingerTec Master Readers

QR110 (MiFare) Compatible Device -
Below are the list of FingerTec device models that are compatible with QR110 (MiFare):
1.       R2
2.       R3
3.       Q2i (FEM 800 only)
4.       Kadex
5.       M-Kadex
6.       Ingressus Controller

Note that QR110 (MiFare) is using 34-bit Wiegand signal to communicate with the master readers.

Requirement -
The main requirements needed for pairing QR110 (MiFare) with the master readers are:
1.       Wiegand-In Port
2.       Wiegand 34-bit Communication
3.       MiFare Card

Connection between QR110 and FingerTec Master Readers -
The connection for QR110 (MiFare) with the Master Readers is the same with QR110 (RFID). You may find the connection details as shown in the diagram below:

1. Pairing With Ingressus Controller
 

2. Pairing With FingerTec Master Readers.
 

QR110 MiFare Setting -
As QR110 MiFare reader is a very simple and convenient reader to begin with, no configuration or setting is required from the device. All users need to do is just plug in the device and the process is complete.

Master Readers Setting -
Before pairing the Master Readers with QR110, the devices on the other hand, will first need to be enabled in Wiegand 34-bit format as per the setting below:

1. R2 and Kadex:
Menu > option > system option > Wiegand input setting > FP device > Input format = WG34 Without ID  > Restart.

2. R3 and Q2i:
Menu > Comm > Wiegand > input option > Define = 34 > Bit counts = 34 > Input = NO. > Restart.

3. Face ID 3:
Menu > comm > Wiegand input > Wiegand Format =  Wiegand 34 > Input = Card No. > Save > Restart.

4. m-Kadex:
Requires a tool update as provided below (also works with R2 and Kadex):
https://s3.amazonaws.com/files.fingertec.com/Azim+Tools/Tools/FTEnableWG34_BWdevice.exe

 5. Ingressus:
Connect 3 Wiegand cables between QR110 (MiFare) reader and Ingressus (no other settings required).

Once done, FingerTec Master Readers will thus be paired up with the QR110 (MiFare) reader.

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 [email protected], we will update it as soon as possible.


Kadex & R2(FEM565) Latest Firmware And Feature Explained



FingerTec has updated Kadex and R2(FEM 565) firmware from the previous version 3544-05 to the latest version 5114-07 which now includes the new feature to support 99 Access Groups.

Feature Description
Previously, the maximum Access Group that is allowed for 3544-05 firmware is limited to 5 access groups. Hence to further benefit users, the updated firmware now allows the users to include up to 99 access groups. This improvement is perfectly suitable for big companies that have a huge number of employees as well as intend to restrict their employees’ access into certain areas within certain time zones.

Example:
During Weekdays, Door A in a company can be accessed by User A within 12.00 am to 09.00 am and User B within 09.00 am to 6.00 pm. In this case, Admins can create 2 different access groups with 2 different Access Level settings as shown below:

Access Group 1: Door A, Night (12.00 am to 09.00 am), User A
Access Group 2: Door B, Morning (09.00 am to 6.00 pm), User B

Feature Settings
Configuration of Access Group can be done in Ingress software, at Access Level module. You can download the latest Ingress software from the link provided below:

To configure the settings under Access Level, please first ensure that the terminal is connected with Ingress and added as a device to the door.
Next, add Time Set. When Time Set is added, 3 Time Zones will be created. In Time Set 1, first interval represents Time Zone 1, second interval represents Time Zone 2 and third interval represents Time Zone 3. The same goes for other Time Set when it is created.

Edit the Access Time in the Time Zone accordingly.
Add Access Group under Access Level.

After creating a new Access Group, select the Time Zone with the appropriate timing. Users can also be added into the Access Group under the User tab.


Remarks: 1 User can ONLY be added into 1 Access Group.

FingerTec Authorized Reseller can now login and download the latest firmware at http://tips.fingertec.com/tips-download-firmware.php. For end users, please contact your local reseller or FingerTec Support Team to acquire this latest firmware update.

How to pair FingerTec QR110 Slave Reader with FingerTec Master Readers


Introduction
QR110 QR Code Scanner is FingerTec latest product that comes with a new verification method: QR Code along with the capabilities to scan RFID/MiFare access cards as well. As a slave reader, QR110 will need to be paired with FingerTec Ingressus controllers and master readers such as R3,  R2, Q2i and etc before the whole system works.
Supported model:
Q2i, R3, R2, Face ID 3, Kadex, m-Kadex, Ingressus I/II/IV
QR110 is built with a 26-bit Wiegand communication. Even though FingerTec master devices comes with 34-bit and 26-bit Wiegand, by default all FingerTec Master Devices is set with 26-bit Wiegand Communication.

For information on QR110 (MiFare), please refer to this post:
How To Pair QR110 (MiFare) With FingerTec Master Readers

Please follow the steps below for QR110 (RFID) installation:
Process:
1) Connect the wirings between QR110 and FingerTec Controller and Biometrics Devices
  • For Ingressus I,II, and IV, please connect the respective devices to the following QR110 ports (D1, D0, GND, VCC) as shown in the circuit diagram below:   


QR 110 to Ingressus

For Master Readers (R2, R3, Kadex, m-Kadex, Q2i, Face ID 3), please connect the respective
devices to the following QR110 ports (D1, D0, GND, VCC) as shown in the circuit diagram below:




Example : R2 Connection to QR110
2) If there is no response on Master device when you wave card or scan QR code on QR110, please check the Wiegand bit Format in FingerTec Device
  • In R2 and Kadex, please go to Menu > Option > System Option > Wiegand Input Setting > FP device > Input Format = WG26 Without ID  > OK > Input = ID > OK > Restart


  • In R3 and Q2i, please go to Menu > Comm > Wiegand > Input Option > Define = 26 > Bit counts = 26 > Input = NO. > Restart
*QR110 is not compatible with Q2i (FEM 510)
  • In Face ID 3, please go to Menu > Comm > Wiegand Input > Wiegand Format =  Wiegand 26 > Input = Card No. > Save > Restart.
  • In m-Kadex, this model does not come with an interface design. Therefore, a software tool is required to enable it into a Wiegand 26-bit format. Please download the software tool here


and proceed to input the IP address of m-Kadex into the software tool. Once updated, the
m-Kadex device will now accept 26-bit Wiegand Connection. (This method can also be applied
to R2 and Kadex) Please refer to the screenshot below for more information:


  • In Ingressus I, II, and IV, the devices will automatically detect and configure its Wiegand Connection once connected to QR110. Therefore, removing the need for any manual setting.


After the configuration is done, the FingerTec devices will then be paired with QR110.

R2, R3 & FaceID3 - Time Zone Setting Group Transfer from Ingress



Introduction
Access level configuration is a function that could help clients secures their property. Clients are able to set different Access Level for each authorized user according to the time zone, with combination of verification type. With this function, you can enhance security by limiting user access to your premises with specific time zone and group verification type.

Benefits
By configuring the Access Level, the security mechanism for your premises is tightened to prevent it from being invaded by any unauthorized individuals.

Process
1. Add a door > add your R3 and FaceID3 device to the door

2. Define the start and end time applicable for this Time Set. You can configure up to 3 different time sets in a day. Access Level > Time Set > Create a time set. Take note that the time access periods need to set continuously without overlapping, as shown in picture below. Following the example below, users will be granted access from 9am to 6pm and 8pm to 10pm every day.

3. Access Group > Create a new access group > Add the door that which to upload the access level > Choose the time set created in step 2 > Select group verify type


4. Add user into the access group > Transfer to device
*Note that this step will transfer the access group to the terminal along with the users in the group; user(s) that are not in any access group will be deleted from the terminal.



Replacing R2i with H2i to Solve Fingerprint Incompatibility Problem in FingerTec R2 version 565



INTRODUCTION
Previously FingerTec R2 was paired with the slave device R2i.  Due to major improvements carried out on the slave, R2c was introduced as a replacement to R2i. However, with the improvements, the new R2c can only support R2 with Biobridge VX10.0 algorithm and incompatible to R2 version 565 with Biobridge VX9.0 algorithm. The differences in algorithm versions disallow transfer of fingerprint templates between the previous R2 and the latest R2. And to use the new R2, users need to reenroll all user fingerprint templates again, a very impractical solution for organizations that have a large number of employees. As an alternative solution, we suggest the pairing of the old R2 unit (565) with H2i unit to work as master-slave in-out readers. This combination can be configured to work with Biobridge VX9.0 algorithm smoothly.

BENEFITS 
By choosing this method, you can skip the reenrollment of users’ fingerprint templates and use the existing fingerprint templates (BioBridge VX9.0) from the old device to be transferred into the new units.

PROCESS
To set up this R2-H2i combination, you need to connect these 2 terminals according to the connection diagram below.


Terminal configurations: 

AT R2 (565) MASTER

Change BioBridge Algorithm Version from Vx10 to Vx9.0
Press Menu > Option > System Option > Adv Option > Alg Ver > 9.0 > Ok > Esc & Save

Setting For Wiegand Input For R2.
Press Menu > Option > System Option > Wiegand > Input setting > FP device > Input format = WG26 with ID > Esc > Input = User > Esc & Save

AT H2i SLAVE

Download the FingerTec Terminal Function Tools at http://www.fingertec.com/download/terminal-func.zip

Change AdapTec Plus to Off
Start up the FingerTec Terminal Function Tool and connect to the H2i terminal and change the AdapTec Plus to OFF at Access Control menu.


Change BioBridge Algorithm Version to Vx 9.0
Start up the FingerTec Terminal Function Tool and connect to the H2i terminal and change the BioBridge Algorithm to Vx 9.0 at General Menu.


And now you’re done. By pairing old R2 565 version with the latest H2i, it could save you tonnes of time enrolling the new templates for all users. If you found yourself stumbled upon this predicament, give this suggestion a serious consideration. Contact us at [email protected] for further information.

Steps to rectify Terminals turning ON and OFF on its own (for AC900, Kadex and R2)

Due to the wear and tear of terminal parts, some of the terminals will automatically turn ON and OFF on its own at times without any command given.

Below are the steps that you can take to rectify this issue on your own.

·        Sleep and Automatic OFF Settings (For AC900 only)

If these settings are configured, the terminal will automatically turn off or go into sleep mode.

To disable this setting, go to Menu > Option > Power Management > Change the Idle Minute to ‘0’.

·        Webserver IP Setting

When this setting is used, the reader will attempt to connect to the Webserver IP and restart after it fails to find the IP which has been set.

To disable this setting, go to Menu > Option > Comm Option > Change the Webserver IP to 0.0.0.0

When both of these settings has been turned off, the reader will not automatically turn ON and OFF on its own anymore.

New Firmware Update for Kadex and R2


Previously, it was reported that it would be a delay in door release when the card was produced in front of the R2 and  Kadex terminal.  

FingerTec has released the new firmware for both R2 and Kadex to solve this issue. 

You can now download the Kadex's & R2’s latest firmware here.

FingerTec R2 HID Reader: Now You Can Use Two Types of Card in One System!



Now, the FingerTec R2 HID reader can be customised to read 2 types of HID cards in one system. No matter if you use HID 26-bit Prox II card or HID 34-bit PX-4-H card to report attendance or gain access, R2 HID can accept both. 

However, do not try this at your existing R2 HID because you need to update the firmware before the feature can be used.

This new development is definitely a good news for users who fancy R2 HID system. Due to  this flexibility, if they have adopted a card system before, it still can be used without having to invest in one type of card only.

To get your firmware, email [email protected]. To order your R2 HID, contact [email protected]

New Firmware Update for R2’s FEM 565 - Opens Door from Software, Improves Data Transfer

Everytime an R2 verified an employee, it will output an encrypted 26-bit Wiegand code to AdapTec Plus. A successful verification code received by AdapTec Plus will cause it to unlock the door and a failed verification code will keep the doot shut.

However R2 cannot output any code to the AdapTec Plus if the administrator presses the virtual Door Open button from TCMS or Ingress software. Therefore, an administrator cannot unlock any door remotely from the software.


This firmware has been improved to allow another output code to be sent to AdapTec Plus to unlock door. Now an administrator can press the virtual Door Open button from FingerTec software to unlock door(s) remotely.


The new firmware also improves the rate of data transfer between R2 and TimeTec Web and Cloud. 


Download the firmware here 

Door Open/Close Configuration With 5 Time Zones

FingerTec Worldwide has improved the Door Open/Close Configuration tool from 1 time zone to 5. Access control terminals such as R2, Kadex and AC900 now can have up to 5 different time zones. Read more for the download link and instructions on how to use it. 

FingerTec Access Control with an Automatic Sliding door


The automatic sliding door can be opened by activating control methods such as motion detectors, push buttons, key switches and access control readers.

There are three types of input that can be used by the automatic sliding door controller/motor if you want to implement access control as the activating control method. Read more to see the three inputs. 

New Firmware Update for Face ID 4, R2 and m-Kadex!

The latest firmware update for Face ID 4, R2 and m-Kadex has now been released to include bug fixes, new features and enhancements. To download them, click here. Read below for an overview of what is included in each update:

Face ID 4
Firmware version:Ver 8.0.0 (Build 359)
- Upgrade Door Event Function to support offline mode
- Integrate False Log Function
- Resolved bugs found when connected with TimeTec
R2
Firmware version: Ver 2702-04
- Resolved device transaction data's slow return time to TimeTec
- Resolved R2c's no response issue
m-Kadex
Firmware version: Ver 6.23 (build 2880-01)
- Upgrade to support usage of Period Door Open function with Adaptec Plus

Initiated & written by: Jazz

R2 (565) – R2 (565) Master - Slave Wiring Diagram & Settings

Previously we have discussed on how to modify the setup for 2 master terminals to use it as master-slave terminals. You can read the full article here. Today we will be demonstrating how to connect the 2 units of R2 (565) terminals to work as master-slave terminals. To use 2 units of R2 as master-slave terminal, you will need to connect the 2 terminals together according to the connection diagram below: Terminal configurations:


At R2 (565) Master

  • Press Menu > Option > System Option > Wiegand > Input setting > FP device > input format = WG26 with ID > Esc > Input = User > Esc & Save


At R2 (565) Slave

  • Press Menu > Option > System Option > Wiegand > Output setting > Output format = WG26 with ID > Esc > Output = User > Esc & Save
  • Press Menu > Option > Comm Option > Adaptec Plus = N > Esc & Save


Note: If the Wiegand option does not appear, please confirm that your R2 terminal is FEM 565 and not FEM 500. If the Wiegand Option is still not appearing, please check the settings at Menu > Option > Access Option > 485 Reader Function = N > Esc & Save > Restart Terminal, or contact [email protected] for further assistance.



Initiated & Written by Azim

Ingress Trial Version


With the launch of the Ingress software just around the corner, FingerTec has released the Ingress Trial Version for our resellers as well as end-users to test out the software before actually making a purchase. The trial version is strictly accessible only to FingerTec’s Authorized Resellers & Distributors and End-Users of FingerTec only.

The instructions below are intended to help you understand the workflow, types of testing environment, and what you need to prepare before you start the test. 

Supported Models:
Multimedia Models: AC100C, TA100C, TA100TC, TA200 Plus.
Access Control & Time Attendance Models: Ingressus, Q2i, i-Kiosk 100 Plus, AC900, R2, H2i, R2c.
Face Recognition Models: Face ID 2, Face ID 3, Face ID 4, Face ID 4d.
Card Reader Models: TimeLine 100, Kadex, m-Kadex, k-Kadex, i-Kadex.

Please make sure that the FingerTec terminal you use for testing is listed above. Any terminals excluded from the list will not work with the Ingress Software. Next up, go to Ingress’s trial version page to fill in the request form and submit it back to us. You are required to insert your FingerTec terminal’s serial number for us to generate the trial product key. 

If you are not using a FingerTec terminal for testing, you are still required to insert the testing terminal’s serial number, and we will process it accordingly. If you do not have a terminal to test the Ingress software, just leave the serial number text box empty and we will provide you with an 8-digit device serial number and the trial product key. We will email you once your Ingress trial application has been approved. 
You can access Ingress’s trial version page by clicking this link.

Once your application has been approved, you may download the Ingress Trial Version software installer here. Unzip the file, right click the installation file and select Run as administrator to prompt the installation. Follow the onscreen instructions to complete the installation.

Upon the Ingress installation, it is mandatory to activate the device before you can use it to perform testing. There are 2 ways to activate the device. While adding new devices to the software, tick the checkbox for Device Online Activation.


Once the activation is completed, you can see a “Successful Activation” message at the bottom left corner of the window. 



As mentioned above, if you do not have any terminals to perform testing, please insert the given serial number at the IP Address / URL text box and tick the checkbox for Device Online Activation. Click Add to activate the serial number and then you may start to use the Ingress software for testing.



Another way to activate the terminal is in Devices. Click on the device that you want to activate and click Activate Device.


At the Activate Device window, there are 2 methods to activate the device; either Online or Offline. If you choose to activate the device online, select Online and click Activate. The Ingress Software will connect to our database server to verify and activate the device accordingly. You will see the device’s activation status as well as the expiry date.



If you choose to activate the device offline, kindly contact us at [email protected] to request for the trial product key. Then insert the given product key into the text box. Select Offline and click Activate to proceed with the activation.



Written by Vincent