*iProtect™ SimonsVoss Wireless Online Keypad reader
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. Introduction
This article explains how you can implement the Simons Voss SI pincode reader based on Wireless online communication and describes the functions and settings.
The keypad reader can be used as an alternative access or as additional authentication for an SV wireless online reader by entering a PIN code into the keypad reader.
The access management of the PIN code cards takes place entirely in iProtect.
2. Support and license
Below is an overview of support for both the hardware and the software, including the necessary license:
Software Name | Version | License |
---|---|---|
iProtect | 10.04.x | iProtect basic license |
| ||
SmartIntego Tool Application | 3.1.7760.17076 |
|
3. Implementation
3.1 Configure the pincode length in the pincode reader.
The implementation of the keypad reader takes place in several areas. First you must determine how many characters the PIN code should contain.
Keep in mind that an extra character must be reserved for the PIN code only option (alternative access) as a leading number. so, if the PIN code only card has 4 characters, a PIN code length of 5 characters must be set in the keypad reader.
If the keypad reader is used as additional authentication with a SimonsVoss wireless online reader, 4 or 6 characters must be set in the keypad reader.
These settings must be made on the keypad reader itself, for this you must follow the instructions of the keypad reader (see the enclosed manual that comes with the product).
For the authentication method, iProtect supports a 4 or 6 digit PIN code.
3.2 Add the pincode reader to the SmartIntego configuration.
If the pincode length configuration is in the keypad reader, you must add the keypad reader to the SimonsVoss gateway node, which you must do in the SmartIntego tool from SimonsVoss
Go to Tools > Smartintego manager, right-click on the existing gateway node where the keypad reader is to be deployed.
There will be a new pop-up screen, select the option “search master segment” and press on the ok button.
The new node (keypad reader) should be found and is shown in the right column, the keypad reader starts with node type PN_R.
You need to double-click on the keypad reader to add it to the Gateway node, the keypad reader will move from the right column (new nodes) to the left column (nodes in this segment).
Press on the exit button to close this screen and check if the keypad reader is visible below the gateway node in the SmartIntego Manager list.
Close the SmartIntego Manager by using the exit button and save the topology, now the configuration procedure will start.
When the configuration pop-up disappears, you are back to the main screen.
The keypad reader has been successfully added to the SmartIntego project, now we need to make an export of the configuration so that we can add the keypad reader to iProtect.
Go to file > Export > WO Configuration and save the csv file on the local machine.
If you open the CSV file you will see the PIN code reader added to the list of devices
If the entire configuration is spread over multiple plutos, you must adjust the xml so that there is one configuration file per pluto.
3.3 Add the pincode reader to the iProtect configuration.
In iProtect go to Installation > hardware >line in the menu structure.
Search for the pluto line where the existing SimonsVoss gateway node is located, select the line in the tree view to get the detail page of this line.
On the detail page in the “Configuration file” section, press the upload button and select the SimonsVoss configuration file.
If the file has been uploaded successfully, you should press the import button. If the import was successful, the status field will say "import successful".
The keypad reader should be now visible below the gateway node in the tree view, The detail page of the keypad reader will be shown when clicking on the keypad reader in the tree view.
On the detail page of the keypad reader, you can change the name of the reader and select the desired online reader which should be controlled by the keypad reader.
3.3.1 fields descriptions.
Label | Description |
---|---|
Name | Logical name of the keypad reader |
Nodeid | SimonsVoss gateway node where the keypad reader is linked to. |
Readerid | SimonsVoss Reader which receives the pressed key from the keypad. |
Type | Keypad type |
Communication status | Last reported communication status |
Version | Firmware version of the keypad |
Local address | Local address of this Keypad |
Below the keypad reader in the tree structure there are two keypad sensors that can be monitored. these are the battery sensor and the signal strength sensor.
4. Card configuration and usage.
4.1 Alternative access by using a pincode.
To gain access with the keypad reader as alternative access to an SV wireless online reader, a separate card configuration must be created in iProtect for the PIN code cards. also, a leading number (Pincode only start key) must be set in the existing card configuration, which is set on the corresponding SV reader controlled by the keypad reader. You can use the manual below to set this up.
*How to setup access with pincode-only (i80P) - Knowledge Base - Confluence (atlassian.net)
Once the PIN only card has been created, you can gain access to the linked reader by first entering the leading number on the keypad reader, followed by the card number.
4.1 Use the keypad as additional authentication.
To enable extra authentication, you must set this on the linked reader on which the card is presented.
Go to Installation > hardware > reader and search for the reader on which you want to perform the additional authentication.
Select the reader in the tree view and go to the tab “general” at the reader detail page.
Here you can change the authentication method to “Pincode required”.
To gain access, each card must have a PIN code, which you can set on the detail page of the relevant card.
Once this has been set, after presenting the card, you must enter your personal 4 or 6-digit pincode on the keypad reader to gain access.
5. Events
Event ID | Event name | Description |
---|---|---|
4 | Subscriber card no access {Error} Authentication timeout | The reader did not receive the Pincode {in time}. |
125 | User presented unknown rcn card | The typed Pincode card for the alternative access is not in the systems database. |
200 | Authentication failed | The additional authentication on the keypad reader was incorrect. {pincode did not match with the card} |
201 | Authentication successful | The additional authentication on the keypad reader was correct. |