*Hardware control applet
- Tom Polman
- Mickael van der Schoot
Installation Manual | IM-20210309-TP-47 Access Control | Controllers | Polyx™ Controllers | |  |
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 Introduction
With the hardware control applet, it is possible to configure the reader ports available in the Pluto- or Polyx reader manager.
Configuring is being done by loading a configuration file. This file includes data as:
The sort of card reader(s) which are controlled by the reader manager.
The protocol, in which the reader manager communicates with the card reader(s).
The function of the LED’s on the reader(s).
These data are determined by the lay-out of the access control system, the existing situation, necessities and the wishes of the customer. The configuration can be different per reader port.
2 Before using
2.1 Required software
Check, whether JAVA is installed on your pc/laptop or not. If this is not the case, install JAVA
first. See http://www.java.com
2.2 Required firmware
To guarantee proper communication between the reader manager and the card reader, it is
strongly recommended to make use of the latest reader manager firmware available.
For Polyx, see chapter 2.2.1. For Pluto, see 2.2.2.
2.2.1 If Polyx
Check whether the Polyx is supplied with a correct firmware version. The firmware version can
be found in the iProtect security management system or directly via diagnostics.
2.2.1.1 Automatically update of the firmware
Depending of the iProtect version, the Polyx reader manager firmware will be automatically
updated through provisioning.
2.2.1.2 Manually update of the firmware
If the reader manager firmware is not up-to-date, please execute the following steps:
Open a web browser on your PC or laptop:
Enter the IP address of the Polyx (e.g. http://192.168.1.195).
The upload of the page appears:
2.2.2 If Pluto
The Pluto reader manager firmware will be automatically updated through provisioning.
2.3 Loading Applet
Download the compressed applet file from the knowledge bank of TKH Security.
Double click on the file you have downloaded. Subsequently it will be executed in the
directory, where the downloaded file is located. Place the files in a directory on your pc or
laptop.
3 Using the Applet
Double click on the KpController-externaluse.jar.
The following main page will appear:
Choose if the configuration concerns a Polyx device or Pluto device.
2. If Polyx, please go to chapter 4
3. If Pluto, please go to chapter 5
4 Configuration Polyx device
This chapter will describe how to configure the Polyx device.
Press on “Polyx device” in the main page
Press on “configure device”
The Polyx configuration window will appear:
4.1 Tab sheet independent functions
This chapter describes the functions which apply to all tab sheets.
Open:
It is possible to open earlier created by this applet .taz files with the “open” button.
Press “open”.
Browse to the correct file and select it.
Press “open”.
Save the information into the configuration file:
With this checkbox it is possible to determine separately for each tab sheet, whether the data must be saved or not. By disabling this checkbox, the tab sheet will not be saved.
For example: if the tab sheet from reader 1 is not saved. The Polyx will keep the previous
configuration.
Save:
This function will save the tab sheets where “save the information into the configuration file” is enabled.
Press “save”
Specify a logical name
Press “save”
Navigate:
This menu will allow the user to within the Keyprocessor hardware control application. The following menus are available:
Polyx device main page
Pluto device main page
Main menu
4.2 Tab sheet General
Here the password can be defined to make use of remote diagnostics.
Note! Depending of the iProtect version, this password will be overruled by iProtect. |
4.3 Tab sheets Reader 1, Reader 2, Reader 3
In the reader tab sheets, it is possible to define which reader and corresponding protocol must be used.
Protocol:
Choose at “reader protocol” the protocol of the reader, which is connected to the Polyx.
You can choose the following protocols to communicate with the reader:
STX/ETX – A serial version of the ABA-CLK/DAT protocol. This protocol is only suitable for readers (SmartID) with one-way data communication from the reader.
Here, the Polyx should be provided with a card protocol.SmartID t=cl – The reader is fully managed by the Polyx. Here, the Polyx should be provided with a card protocol and keystore.
Sirius (801-5050) – The reader is fully managed by the Polyx. Here, the Polyx should be provided with a card protocol and keystore.
Sirius i-series – The reader is fully managed by the Polyx. Here, the Polyx should be provided with a card protocol and keystore.
Vandal proof (801-501x) – The reader is fully managed by the Polyx. Here, the Polyx should be provided with a card protocol and keystore.
Sirius LEGIC – Protocol to handle Sirius LEGIC readers.
Aperio – Protocol for Aperio fittings. Here the Polyx should be provided with a card protocol.
Sallis – Protocol for Sallis fittings. Here the Polyx should be provided with a card protocol
OSDP – open standard protocol.
PHG Legic – Protocol for PHG Legic card readers. Here, the Polyx should be provided with a card protocol.
PHG Rs485 – Protocol for PHG finger scan reader. Here, the Polyx should be provided with a card protocol.
Press on the dropdown menu from the “protocol”
Select the desired reader protocol
Baudrate:
Depending on the selected type of reader, the default baud rate will be loaded (do not change this setting!).
Card protocol:
Here the available card protocols are visible. The protocols available depends on the reader protocol.
Press on the dropdown menu from the “card protocol”
Select the desired protocol.
Active LED:
Here the default LED color can be defined. The active LED color is the default LED color of the card reader.
Access LED:
Here the access LED color can be defined. The access LED is the alternate LED color of the card reader.
4.4 Tab sheet Diagnostics settings
In the tab sheet Diagnostics, debug settings can be made.
Select debug level:
The debug level defines the kind of information which will be printed of the selected debug traces.
Debug traces
The different traces which can be enabled to generate debug data.
Note: We recommend too set the debug level on “off” under normal circumstances and |
5 Configuring a Pluto device
This chapter will describe how to configure the Pluto device.
Press on “Pluto device” in the main page
Press on “configure device”
The Pluto configuration window will appear:
5.1 Tab sheet independent functions
This chapter describes the functions which apply to all tabs.
Open:
It is possible to open earlier created by this applet .taz files with the “open” button.
Press “open”.
Browse to the correct file and select it.
Press “open”.
Save the information into the configuration file:
With this checkbox it is possible to determine separately for each tab sheet, whether the data
must be saved. By disabling this checkbox, the tab sheet will not be saved.
For example: if the tab sheet from Orion 1, PRT1 is not saved. The Pluto will keep the previous
configuration on that specific PRT.
Save:
This function will save the tab sheets where “save the information into the configuration file” is enabled
Press “save”.
Specify a logical name.
Press “save”.
Navigate:
This menu will allow the user to within the Keyprocessor hardware control application. The
following menus are available:
Polyx device main page
Pluto device main page
Main menu
5.2 Tab sheets Orion 1 - 4
In the reader tab sheets, it is possible to define which reader and corresponding protocol must be used.
Protocol:
Choose at “reader protocol” the protocol of the reader, which is connected to the PRT interface.
You can choose the following protocols to communicate with the reader:
STX/ETX – A serial version of the ABA-CLK/DAT protocol. This protocol is only suitable for readers with one-way data communication from the reader. Here, the Polyx should be provided with a card protocol.
Sirius (801-5050) – The reader is fully managed by the Polyx. Here, the Polyx should be provided with a card protocol and keystore.
Sirius i-series – The reader is fully managed by the Polyx. Here, the Polyx should be provided with a card protocol and keystore.
Sirius LEGIC – Protocol to handle Sirius LEGIC readers.
Wiegand converter – Protocol to handle Wiegand converters.
Sallis – Protocol for Sallis fittings. Here the Polyx should be provided with a card protocol
PHG – Protocol for PHG finger scan reader. Here, the Polyx should be provided with a card protocol.
OSDP – open standard protocol.
Press on the dropdown menu from the “protocol”
Select the desired reader protocol
Baudrate:
Depending on the selected type of reader, the default baud rate will be loaded (do not change it!).
Card protocol:
Here the available card protocols are visible. The protocols available depends on the reader protocol.
Press on the dropdown menu from the “card protocol”
Select the desired protocol
Active LED
Here the default LED color can be defined. The active LED color is the default LED color of the card reader.
Access LED
Here the access LED color can be defined. The access LED is the alternate LED color of the card reader.
Use Orion for kpBus
If the Orion PRT2 interface is used for the kpBus, no readers can be connected to this PRT2.
5.3 Tab sheet Diagnostics settings
In the tab sheet Diagnostics, debug settings can be made.
Select debug level:
The debug level defines the kind of information which will be printed of the selected debug traces.
Debug traces
The different traces which can be enabled to generate debug data.
Note: We recommend too set the debug level on “off” under normal circumstances and |