Open

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

Open

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.

1 SimonsVoss and iProtect Aurora

iProtect™ Aurora version 09.05.12 or higher can control SimonsVoss Smartintego, by means of a connection
between a Pluto network device and a SimonsVoss Gateway node.

1.1 System architecture

iProtect: The security management system from TKH security.
Pluto: The network controller from TKH security.
Gateway node: The wireless online node from SimonsVoss.
Cylinder/smarthandle: The wireless online lock/cylinder of SimonsVoss.
Card: The access control card of the end user.

1.2 System requirements

2 System design and installation

Design and install the SimonsVoss system as stipulated in the SimonsVoss manual. Please keep the following
in mind:

• Connect at most 32 locks per Pluto.

• Max 16 locks for each SV gateway node.

• Max 16 gateway nodes on one Pluto.

• The lock can have a maximum distance of 20 meter from a Gateway Node (GN). Please notice that
  this distance is an indication which can differ due to location specific circumstances.

• Analyze the radio frequency signal between the lock and node with a signal tester.

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.

2.1 Specific setting SV gateway node

• In the SV gateway node settings, the setting “SV connection timeout [s]” should be set to 0.

• Optional an AES encryption key can be set in the SV gateway node by browsing to the gateway node
  using HTTPS. This will enable encrypted communication with the Pluto. See the SV gateway node
  manual for more details.

3 Installing SimonsVoss software

Be sure before starting to integrate the solution, that the following software is installed as described in the
SimonsVoss manual.

• SimonsVoss Smartintego WO

• SimonsVoss SMART.CD

A new project file should be created in the SimonsVoss Smartintego WO software, it is also possible to start
a new project by opening a template file (see 3.2). The SimonsVoss Smartintego WO software is necessary
to configure all the gateway nodes on forehand.

Please contact your consultant or the TKH service and support department for the
“TKH_security_default_cardconfig_MF_DES.ikt” template file or the KEY information.

3.1 Password handling

Project password: The Smartintego tool stores the locking system configuration in a project .ikp file. The
project password protects the file access. This password is changeable in the tool itself.

Lockingsystem password: The configuration of the locks will be secured with the locking system password.
The password will be written into every lock and is not changeable afterwards. With this password it is possible for example to do emergency opening or resets the locks. Keep this password protected!

Wavenet password: The Wavenet password secures the Wavenet configuration (topology, addresses e.g.).
Starting the Smartintego tool the first time, the password must be generated. Afterwards this password cannot be changed.

3.2 Card coding settings

Depending on the card type and encryption method, card specific coding settings must be entered into the
SimonsVoss software. These settings will determine how the SimonsVoss handles and/or cylinders will handle and process the card number.

From Smartintego WO version 3.0.7249.19977 it is also possible to use a template file. This template
file already has the card coding settings so there is no need to create card coding settings anymore.
There is a template available for the TKH Mifare classic and TKH Mifare DESFire card coding. This
template file can be opened using the Smartintego WO software version 3.0.7249.19977, from than
the project can be created

3.2.1 If coding is 4 Byte UID

3.2.2 If coding is 7 Byte UID

3.2.3 If coding is TKH Mifare Classic

When using Smartintego WO version 3.0.7249.19977: Use the
“TKH_security_default_cardconfig_MF_DES.ikt” template file. Password is: 12345678

When using Smartintego WO: 2.1.6411.25403 use the table below to make the card coding settings

3.2.4 If coding is TKH Mifare DESFire

When using Smartintego WO version 3.0.7249.19977: Use the
“TKH_security_default_cardconfig_MF_DES.ikt” template file. Password is: 12345678

When using Smartintego WO: 2.1.6411.25403 use the table below to make the card coding settings.

4 Configuration iProtect for SimonsVoss WO

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

5 Supported features

This chapter will describe the supported functionalities and features.

5.1 SimonsVoss doors (lock nodes)

SimonsVoss doors, which can be Smarthandles or cylinders, are locations, at which persons move from one
area to another area and are identified, controlled and registered with cards. Lock Nodes are access control
units, which consist of a card reader and are able to latch a door.

5.1.1 Name

Logical name of the lock node.
Type: Text
· Default: empty
· The name is mandatory
· Max value: 32 characters

5.1.2 Unlock time

Default door open time used when a valid card is presented.
Type: Time setting
· Step size: 0.1 second.
· Max value: 250
· Default value: 30

5.1.3 Alternate door unlock time

Depending on card settings an alternate door <unlock time> can be used.
Common used for logistic employees, persons with disabilities or other persons who needs more time to pass a door.

Type: Time setting
· Step size: 0.1 second.
· Max value: 250
· Default value: 50

5.1.4 Unlock once

Action button for unlatching a lock once.
Type: button
· Follows the unlock time

5.1.5 Reader mode

Drop down menu to set the desired reader state.

5.1.6 (time) anti-passback

Settings for anti-pass back.

5.1.7 Office mode time zone

Setting which determine if a lock can be set in office mode or not.

Type: drop down menu

Standard: Reader cannot be set in office mode
Time zone selected: Reader can be set in office mode during that time zone

5.1.8 SV WO lock monitoring

When the door monitoring in the SV Smartintego WO is enabled on a lock, the settings are shown in iProtect
at the reader details tab “door monitoring”. Currently iProtect supports door to long open with 2 transactions:
· Open too long
· Door closed (alarm resolved)

5.1.9 Technical monitoring

To monitor the technical status of a lock, 2 analogue inputs are automatically created when a lock is connected.

Quality of signal: This is a “one time” signal strength notification. After creation, this value will not be constantly updated.

Battery status: Battery status of the lock, this value will be updated according to the battery status of the lock
at that moment. This also can be used to visualize the battery status on a Keymap.

From iProtect version 10.00.32 also a separate transaction is created when the battery status of a lock is
changed. The transaction is “READER BATTERY ALERT” and can have the warning levels: Okay, Warning
and Alarm

5.2 Whitelist

The Lock Nodes, cylinders as well Smarthandles makes use of a whitelist. This list contains a maximum of
250 calamity access cards, which keep access in case of any failure in the (wireless) communication.

Although the maximum amount of whitelisted cards is 250 it is strongly recommended to keep this number as low as possible. It takes a long time and uses battery live to get a card uploaded to the lock using wireless
communication, also a card can only be deleted from the whitelist by restarting the Pluto (Checkbox “Clear
calamity list” must be on at the reader settings in iProtect).

The calamity priority can be determined per access card in the card dialog, only the access cards with the
priority “always” and access rights to the lock will be programmed on the whitelist of a lock.