Smooth Troubleshooting Date/Time Change in FingerTec Terminals to Ensure Accurate Data Accumulation


Introduction

These tips are to assist users to determine the root cause of the time change issue on the terminals so that they  will know how to tackle the situation effectively.


Since it is related to the users’ attendance data, an inaccurate time and date in the devices needs to be solved at the soonest. This is because if the time and date shown on the screen is incorrect, users willl encounter faulty attendance recording as the r transactions operates based on the time set in the respective device.

Benefits

This troubleshooting tips will:
-   Ease the user to determine the cause of this issue, whether it is a setting issue, or a
    faulty hardware.
-   Save the troubleshooting time. If it is setting issue, users may directly check the setting
     via their Software. If it is hardware issue, user can directly check the physical
     device.

Process

There are 3 possibilities that can cause the date and time to change in the terminals. Kindly refer to the checklist below.


1)   CMOS battery is weak. If you encounter the time changes to 00:00 after restarting the
       terminal, there is a possibility that the CMOS’s battery is weak. You can replace
       a new CMOS battery in this scenario.
 In other cases, if you set in the software to automatically synchronize the PC time and
 date into the device, you need to check the PC’s time and date, if the PC time and date
  is incorrect, you need to change new a CMOS battery for the PC.

  You can get the CMOS Battery in the electronic shop nearest you. The CMOS battery
   code is CR1220 - 3 volt.
 
 
2)   The terminal is connected to Webster/Webserver. Terminal time will change based on
       the time zone of the server. You need to check back the server and the configuration,
       whether the terminal is connected to any Webster/Webserver. You will also need to
       check the time zone setting in the software (Webster/Webserver/TimeTec TA).
 


 
3)   Faulty Timer Crystal. A MCU board consists of a crystal component, which controls the
 
time displayed in the terminal. If the crystal component is faulty, you need to
 
change  the MCU board. Normally if these component is faulty, you will see that the
 time on the terminal is delayed or faster from the original time that you have
 configured. If your device is still under warranty, you can claim
the warranty for the
 faulty MCU board at
http://warranty.fingertec.com.

Understand How To Troubleshoot Connection Error When Using TCP/IP


Introduction

FingerTec software is specifically designed to centralize, store and manage all data extracted from FingerTec terminals to create an easily managed and networked attendance solution. There are several ways to connect to FingerTec terminals, including TCP/IP, USB and Serial Port (RS485 or RS232), where TCP/IP is the most commonly used connection type due to its stability.

Benefits

Adhering to the steps below, you can learn how the device communicates with the software and how it will inevitably shortened your troubleshooting time.

Solution

You may encounter these error messages in the software if there is no connection between the device and the software.

 

Troubleshooting Steps:

1.       Ping the IP Address
            -  Use Windows Command Prompt to ping the Device’s IP Address.
                  -  Type ping<space><ip address of the device><space>-t, then press Enter.

You will get this reply if the connection is up and running:
 
And this if there is no connection, you will get this message, as shown below:
 2.       Check IP Address,  Gateway, Subnet Mask setting on Device
             
-   Make sure the IP Address, Subnet mask and the Gateway setting in the
                  FingerTec device tallies with the Local Network.
           
             -   You can check your network information by using Command Prompt > type
                  ipconfig > press Enter button, or refer to your IT personnel who’s in charge of
                 
the office’s network setting.
 
 3.       Check COM Key and Ethernet setting on Device
            -   If you can ping the Device’s IP Address, but still unable connect to the software,
                 you may checkup the COM Key and Ethernet (for Black and White screen model
                 only) setting in the device.
            -   The use of Com Key is to avoid any unauthorized person to use another copy of
                 TCMS v2 or BioBridge SDK to connect to FingerTec Device to carry out any
                 operation.
            -   The connection will fail if there is a mismatch of Com Key in the terminal and in
                 the software.
           -    Also you can set the COM  Key at :
                 ·         Black and White screen Device:
                             Press Menu > Option > Comm Option > COM
                 ·         Colour Screen Device
                             Press Menu > Com option > TCPIP / Security > Password
           -   For Black and White Device such as R2 and Kadex, there is a function called
               Ethernet which can be turned off to disable the TCP/IP connection. You can check
               it at Menu > Option > Comm Option > Ethernet. Make sure the Ethernet is set Y to
               enable the TCP/IP function.
 
4.       Check network cable and network switch.
           -   You can check the LED status on the router or network switch.  If the port’s LED
               that you have connected the device to has no light, it means that there is a
               faulty part, which could be the devices’ hardware or the network cable (CAT5/
               CAT6). Proceed by trying to swap the network cable with a working one to see if
               you are able to establish a connection. If it still fails, please move on to the next s
               step.
 
5.       Change device’s part
           -   The parts that interferes with the network communication function of a FingerTec
               devices is either the oreboard or the MCU Board.
           -   Coreboard is where the Network IC and Network Chip is located at. Usually if
                there is a lightning strike, or power surge, these components will
                be damaged.
           -   MCU Board is where the Network Port is located. If there is any physical damage
                on the network port, it will affect the Network communication.
            -   Kindly claim the faulty part at http://warranty.fingertec.com , if valid.

Easily Resolve OLE Error when downloading data into TCMS v2.2.027 to Correct Download Process


Introduction
Recently, there have been multiple cases where users encountered an error while downloading data from terminals into TCMS v2.2.027. This is identified as the “OLE error” where the software is not able to read and retrieve the data due to incompatibility of the BioBridge SDK that is bundled with TCMS v2 software.

Benefits
By adhering to these tips, users will be able to clarify and solve the OLE error when downloading clocking data from FingerTec terminals.

Process

To resolve your issue, kindly follow these steps:
1) Close TCMS v2 software
2) Download the latest ft.exe file from HERE.
3) Rename the downloaded file to "ft.exe" (remove all the numbers in the file name, and
    
leave it as ft.exe or ft depending on your PC's setting).
4) Copy the above file, and paste it in TCMS v2 folder (Local Disk C > Program Files (x86) >
    
FingerTec Worldwide > TCMSv2) to replace the existing ft.exe file.
5) Download SDK Installer from this HERE.
6) Unzip the downloaded file and run the installer accordingly. Please note that there are 2
    
files in this folder, kindly select the one with .exe format.
7) Restart PC
8) The OLE error will not re-appear once you relaunch the TCMSv2 Software.

Turning On Group Verify Type for Face ID 4 series terminal for Better Authenticity of Attendance Recording


Introduction

Most of the FingerTec terminals come with multiple verification method, such as card verification, password verification, fingerprint verification or face verification. The credentials of the users is very important - The credentials of the users are very important. Either verification for time attendance or door access, each user will have their own identification credentials, where it can only be verified by the user alone. However, there are cases where access card or password is being shared among users, which leads to the issue of buddy- punching.

Benefits

Group verify type function will give the administrator an option to perform verification using combination of credentials. Combination of different credentials will give the administrator an advantage, to make sure that users access to a door or record their attendance truthfully, without cheating. Cases such as stolen cards or leaked passwords can be prevented if this feature is activated, where users need to verify their different credentials, in order for the log to be recorded, or to release the door lock.

Process:

1.  To turn on this feature for Face ID 4, kindly download the tool from HERE.
      Run the tool and insert the terminal IP address and click at the "Connect" button.


2.   The tool will list out the terminal information. Please check the terminal information
       shown on the screen, and make sure that the information belongs to the terminal

       that you want to update. Click the “Update” button if confirmed.


3.   The tool will prompt a message if the setting successfully updated.


4.   Please restart the terminal by clicking the “Restart” button.

 

5.   You will see the Group Verify Type configuration at Menu > Systems > Log Settings >
       Default Authority in the Face ID 4/Face ID 4d terminal.

Resolving “Required Active X is not registered properly or is outdated” Error in TCMS V2



Introduction
Using the TCMS V2 on a PC that is running on Windows Vista, Windows 7, Windows 8, and Windows 10, can occasionally cause some glitches. Due to the extra security features that are built into the newer operating systems, an error message will pop up regularly when you launch TCMS V2 software. This is because the program files and system registry files on these Operating System (OS) are protected, and running the TCMS V2 requires access to these protected files. To prevent the prompting of the error messages and to ensure that the TCMS V2 is running smoothly on your OS, there are a few steps that need to be taken.




Benefits
By performing these steps, users will be able to launch TCMS V2 software without encountering the “Required Active X is not registered properly or is outdated” error message.


Process
1)    Close TCMS V2 software
2)    Go to TCMSv2 folder ( Local Disk C > Program Files (x86) > Fingertec Worldwide > TCMSv2
3)    Run Vistareg.exe as Administrator



 4)    Once done, return to your desktop, and right-click at TCMS V2 icon, then select “Properties”.

5)    Go to “Compatibility” tab, and click on “Change settings for all users”.

6)    Check the “Run this program as an administrator” option, then click “Apply” and “OK”, and the problem will be out of your site.

Update Your Firmware and Fully Utilize Door Access Features in Ingress for AC900 FEM565 - R2 FEM565 – Kadex FEM500


Introduction

Most of our clients have switched from TCMS V2 to Ingress.  Therefore, for those who are using door access terminals such as AC900 FEM565 / R2 FEM565 / KADEX FEM500, they will need to update their devices with a unique firmware to fully utilize the door access features in Ingress.

Benefit
The firmware update will let users utilize the door access features on their existing terminals through Ingress.

Process
1)   Download the firmware update tool*
2)   Close PC’s Wifi connection / anti virus / firewall before running the .exe file
3)   Key-in the IP Address
4)   Choose the GroupVerType timer with Ingress.
5)   Click Connect > Update > Restart.


*Please refer to your Reseller for this firmware update. 

In case you want to switch back from Ingress to TCMS V2, you can roll-back the update by choosing the GroupVerType timer with TCMS V2.