.png?version=1&modificationDate=1669119156501&cacheVersion=1&api=v2)
Installation Manual | TM-0910023 iProtect Access / Security | Intergration|  |
This manual represents the knowledge at the above-mentioned time. TANLock security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.
1. Introduction
This document is the installation and operation manual of the connection between the iProtect system and the TANLock Rack handle.
2. Support and license
Below is an overview of support for both the hardware and the software, including the necessary license:
Support | Version | Max. readers per line | License number | Per TANLock rack handle | Suported card technologies |
|---|---|---|---|---|---|
iProtect | >= 10.0.xx | 505-3101 online card reader license | |||
Pluto / ApolloN | 32 |
|
|
Only use calamity cards for the purpose for which it was made. It is recommended to use as few emergency cards as possible.
3. TANLock rack handle
The TANLock rack handle is a mechanical server cabinet lock, which is available in various versions for many different cabinets. All rack handle locks are provided with a network connection and are exclusively powered by PoE (Power over Ethernet). iProtect has a deep integration with TANlock locks (TKH rack handle). The TKH rack handles are provided with a card reader (suitable for DESFire cards) and optional with a keypad.
4. Functionalities TANLock rack handle in iProtect
The connection between iProtect and the rack handle system offers the following functionalities:
Details | Comments |
|---|---|
Full integrated, provisioning of TANLock rack handle settings, firmware and keystore | |
Websocket connection | |
Log events from the rack handle in iProtect | If a * is placed in front of the date / time stamp for an event, this means that the time is not certain or old (eg Jan 1, 1970), iProtect will change the time into the current time marked with a *. This in order not to lose these events. |
Local stored cards for calamity openings by lost network connection | |
Support of handle locked and door position input | |
Intrusion detection (guarded area) | |
Remote opening | |
Brings you all the benefits of a normal wired card reader | |
Pincode support (2 factor authentication) | |
Support of FQDN (Full Qualified Domain Name) |
4.1 Expansion of functionalities in iProtect 10.4
Details |
|---|
In Node dialog, the provisioner group can be set to update the lock |
In Reader dialog, the provisioner group can be set to update the configuration |
Multiple card configurations are supported.
|
Automatically added a reboot function of the lock after update (1 hour). |
5. Setup
5.1 TANLock rack handle device
Use the TANlock manual to setup the device
Device | Software | Firmware |
|---|---|---|
TANLock Rack handle | <= 07x28 | |
0.0.4 | >= 07x31b |
5.1.1 TANLock rack handle defaults (depending on order):
IP address | Username | Password |
|---|---|---|
192.168.0.90 | username: tkh | 123 |
DHCP | username: tkh | 123 |
5.2 Configure the TANLock Rack handle
5.2.1 Connect the rack handle to your network and login with your computer.
By using a new device, take care that your computer is in the same subnet as the rack handle device.
When DHCP is enabled it has priority over the static ethernet settings. So if the rack handle is connected to a network with DHCP it will not use the default static address.
5.2.2 Browse to the TANLock rack handle and select Websocket menu
Use a Firefox Browser browser. Then open the TANLock rack handle maintenance page
This menu is used to setup network configuration of the TANLock rack handle.
If DHCP is enabled be aware that in the Pluto the DNS server is assigned.
Changes of network settings requires an reboot of the device
5.2.3 Select Websocket menu
This menu is used to setup the connection between the and iProtect.
Default Web user: tkh
Default socket password: 123
When changing the defaults, iProtect should also be changed
5.2.4 Select Auth menu
This menu is used to setup login credentials for the TANLock rack handle.
Default Web user: tkh
Default socket password: 123
5.2.5 Select Status menu
This menu is used to show the current date / time and the network settings.
5.2.6 Select Reboot menu
This menu is used to reboot the device. Any adjustments will be made after the reboot
5.3 Line
Determine to which Pluto or ApolloN (line) the TANLock rack handle should be connected. If it doesn't already exist, create a new line. Otherwise, continue to chapter 5.3
In iProtect, browse to menu: Installation | Hardware | Line
Field | Content | |
|---|---|---|
Name | Logical name e.g. Pluto | |
Features | Type | Network device |
Host type | Pluto or ApolloN | |
Communication | Active | Selection option to activate |
Active (with nodes) | Selection option to activate | |
Status | Function of the line | Physical line |
Address | IP address | Enter the IP address |
5.4 Node
Determine to which Pluto or ApolloN (line) the TANLock rack handle should be connected.
In iProtect, browse to menu: Installation | Hardware | Line.
Select the controller where the TANLock rack handle should be connected
Right click on the controller and add a Node
Field | Content | |
|---|---|---|
Name | Logical name e.g. TANLock rack handle cabinet 1 | |
Features | Node type | TANLock rack handle |
MAC address | Depending if FQDM (Fully Qualified Domain Name) is used fill in the MAC address | |
Login | tkh (default). Change it if desired | |
Password | 123 (default). Change it if desired | |
Provisioner group | TANlock rack handle (system default) | |
SSL | Use SSL | Default on |
Allow self signed | Default on | |
Allow expired | Default on | |
No Hostname check | Default on | |
Client communication type | Less secure client communication | |
Status | Node online | Selection option to activate |
Address | HTTP port | Port number that is used by the TANLock rack handle (default 443 HTTPS) |
IP address | Mandatory If FQDM (fully qualified domain name) is used the TANLock rack handle must be set to DHCP NOTE: When DHCP is enabled it has priority over the static ethernet settings. So if the TANLock rack handle is connected to a network with DHCP it will not use the default static address. | |
When using iProtect <=10.2 SSL settings are in de Node dialog. These settings can be determined depending on the situation.
When using iProtect > 10.2 SSL settings are moved to: Installation | Hardware | Secure communication type. These settings can be determined depending on the situation.
5.5 Automatic process (provisioner)
At the moment you have pressed save in chapter 5.3, iProtect will try to connect to the TANLock rack handle device. As soon that the connection is established, iProtect will provision the TANLock rack handle with default firmware of:
TANlock rack handle software
TANlock rack handle keystore
TANlock rack handle settings
When the system uploads these files, it may take a few minutes for the lock to register with this version.
If different firmware is required, a new provisioner group must be added with the desired firmware media elements. This group with different firmware must be selected on the Node.
After the provisioner process is ready, present a card to the TANLock rack handle. The following items will be added to the Node:
Hardware | Description | |
|---|---|---|
Reader | Card-reader <logical number>.<reader> | |
Input | Doorposition |
|
Handle locked |
| |
Handle turned |
| |
Motor in lockable position |
| |
Logical number site panel |
| |
In iProtect, it looks like this:
5.6 Guarded area
The purpose of a Guarded area is to monitor a group of inputs e.g. detectors, door contacts, etc.
For more information, please consult the iProtect™ Guarded Area manual
When the items of the TANLock rack handle are created automatically, a Guarded area will also be generated with the name the Lock followed with the IP address. For example: TANLock rack handle cabinet 1, 192.168.3.169
The following inputs are added to the guarded area:
Doorposition (11)
Handle locked
Handle turned
Motor in lockable position
Side panel (13) (default Omitted)