...

...

Installation Manual | IM-20210309-TP-18 iProtect Access / Security | Functionalities | Image Added

View file name

SV_WO_IM_17022021

IM-20210309-TP-18.pdf

This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.

Table of content

...

1 SimonsVoss and iProtect Aurora

...

Important note:
As there are limitations for the 868 Mhz wireless network, be aware that the network can be overloaded if
there are many wireless events at the same time. For example, access request using a card, reader state
changes, reader pulse requests and upload of calamity cards at the same time. This could lead to delays, in
some cases to no access after presenting a card and/ or reader error messages in the iProtect log. To prevent
this is advised to use this solution on doors that are not often used, like doors to an office room or closet. For
doors that are often used like main entrance or department doors we advise a solution with non-wireless
readers.

...

4.1 Configuring SimonsVoss WO Line

1. Click in iProtect on the menu item “Installation” > “Hardware” > “Line”.

2. Right-click in the browse window and select ‘add line’. The detail window opens.

3. Enter the following data.
   Name: “specify a logical name”
   Type: Network device
   Host Type: Pluto
   Active: check
   Active with nodes: check
   Function of the line: Keyprocessor
   IP-address: Enter the IP address of the Pluto

4. Save the data.

4.2 Configuring SimonsVoss WO node (by import)

Be sure that before the node will be configured in iProtect. The configuration of the SimonsVoss gateway
nodes and SimonsVoss handles/cylinder must be done by the SimonsVoss software. The result of this
configuration will be imported during the configuration of the SimonsVoss WO node into iProtect.

1. Click on configuration data at the SimonsVoss Smartintego Manager software at “file”> “export”.

2. Save the .csv file.

3. When using more than 1 Pluto the .csv file needs to be split into a separate import file per Pluto containing:
   a. The Gateway nodes for a specific Pluto
   b. The Lock nodes for a specific Pluto

4. Click in iProtect at the menu item “installation” > “hardware” > “line”.

5. Click on the desired Pluto created at chapter 5.1.

6. Click on “upload” and select the saved .csv file.

7. Click on “import”.

8. When an AES encryption key is programmed in the SV gateway node the exact same key needs to be
   entered at the “password” section of the node details in iProtect.
   The import automatically generates programmed Gateway Nodes and Locks. Automatically the following
   names will be generated:

...

4.3 Configuring card data interpretation

Depending on the card coding (chapter 4.2), the used card data interpretation needs to be modified for
SimonsVoss WO usage.

1. Click in iProtect on the menu item “access”> “settings” > “card coding” > “card data presentation”.

4.3.1 If UID 4 Byte

For UID 4 byte, an extra card data interpretation is needed underneath the default UID 4 byte presentation.
Default card data interpretation name: “32 bit number DECIMAL”

1. Enter the following data at format:
   · Reader communication protocol = Hexadecimal
   · Data length: 8

2. Enter the following data at card number:
   · Start: 1
   · Length: 8

3. Enter the following data at SV WO:
   · Length calamity card: 4
   · Calamity card setup number: 0
   · Byteswap:
   o checked for straight
   o unchecked for byteswap (default)

4.3.2 If UID 7 Byte

For UID 7 byte, an extra card data interpretation is needed underneath the default UID 7 byte presentation.
Default card data interpretation name: “32 bit number DECIMAL”

1. Enter the following data at format:
   · Reader communication protocol = Hexadecimal
   · Data length = 14

2. Enter the following data at card number:
   · Start 1
   · Length 14

3. Enter the following data at SV WO:
   · Length calamity card = 7
   · Calamity card setup number = 0
   · Byteswap:
   o checked for straight
   o unchecked for byteswap (default)

4.3.3 If TKH Security Mifare Classic

For Mifare Classic, an extra card data interpretation is needed underneath the default KP Mifare classic
presentation.
Default card data interpretation name: “KP Magstripe”

1. Enter the following data at format:
   · Reader communication protocol = Hexadecimal
   · Data length: 12

2. Enter the following data at system code:
   · Start: 1
   · Length: 4
   · Code: Hexadecimal system code

3. Enter the following data at card number:
   · Start: 9
   · Length: 4
   · Modulo and offset can be used if programmed on the card

4. Enter the following data on SV WO:
   · Length calamity card: 6
   · Calamity card setup number: 0
   · Byteswap: checked

4.3.4 If TKH Security DESFire

IFor DESFire an adjustment of the default KP DESFire interpretation is needed.
Default card data interpretation name: “KP DESFire”

1. Enter the following data at SV WO:
   · Whitelist bytes = 6
   · Calamity card setup number:

• When the “TKH_security_default_cardconfig_MF_DES.ikt” is used: 1

• When the cardcoding is manually entered: 0
  · Byteswap = checked

...