.png?version=1&modificationDate=1730820440901&cacheVersion=1&api=v2)
Installation Manual | TM-20230511 iProtect Access / Security | Functionalities |Voxio-A-3100-A 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.
1. Introduction
This article explains how you can implement the VOXIO-A-3100-A reader based on OSDP communication and describes the functions and settings
2. Support and license
Below is an overview of support for both the hardware and the software, including the necessary license:
Version | License |
|---|---|
Version 10.4.14 | iProtect basic license |
Sufficient reader license |
2.1 Supported cards
3. What is OSDP
Open Supervised Device Protocol (OSDP) is an access control communications standard developed by the Security Industry Association (SIA) to improve interoperability among access control and security products.
OSDP was approved as an international standard by the International Electrotechnical Commission in May 2020 and has been published as IEC 60839-11-5.
OSDP V2.2 which is based on the IEC 60839-11-5 standard, was released in December 2020.
OSDP readers are only supported by stacked Orions (RS485 connection)
4. Installation
4.1 Connecting the reader
PHG connector | Signal | CAT5 cable > Orion PRT 1 or 2 |
|---|---|---|
Pin 1 | Not in use | |
Pin 2 | Not in use | |
Pin 3 | B | White/Orange & White/Green |
Pin 4 | A | Orange&Green |
Pin 5 | Not in use | |
pin 6 | GND | Brown |
Pin 7 | VCC 8-30V DC | Blue |
Max. cable distance between Orion and the PHG reader = 30 Mtr. This is based on CAT5E - 24AWG
This cable distance is based without installing an external power supply.
5. Implementation
5.1 General
OSDP readers are completely handled by the nodemanager, so the nodemanager should run to obtain access by a OSDP card reader.
The readermanager is not involved by handling the OSDP protocol
5.2 Configure the reader in iProtect
Follow the steps below to configure an OSDP reader:
Connect the reader (see chapter “Connecting the reader”)
Press the discover button in the line dialog of the Pluto.
Wait until the discover process is ready: Read-in event=> Read-in event: Stop, Line: xxx…
Refresh the line dialog of the Pluto, if an OSDP device is detected it will be shown as a Node below the Port of the Orion where the reader is connected to.
Change the OSDP compatibility setting at the OSDP node to “No reader in capabilities”
Right mouse click at the OSDP reader in the treeview and click on “add reader”
Fill in the logic unique name of the reader.
Click on the save button.
If an rs485 reader has already been connected to the PRT port, the pluto must first be restarted before the discover is executed and the OSDP node can be created.
The discover function for OSDP devices checks for the following settings:
Baudrate: 9600, 19K2, 115K2 baud, They are all non-parity, 8 bit, 1 stop bit
Device address: 0, 1, 2, 3, 4, 5, 6, 7, 8, 13, 14, 24
If other settings are necessary, set these settings manually.
5.3 OSDP reader settings
For OSDP readers there are some specific settings.
It’s possible to setup the buzzer time when a card is recognized, this can be done at the door behavior tab of the reader.
Buzzer time | card recognized | |
|---|---|
Setting | Behavior |
Empty | No buzzer when card is recognized |
1 - 15 | buzzer time (1/10 sec) |
Most used setting for buzzer time = 2
5.4 Keypad buttons
Keypad | Description |
|---|---|
0-9 | Numeric numbers |
C | On keypad is used as restore key to re-enter the PIN on the pending access request. |
E | On keypad is used for reset pincode (do not use as pincode only key). |
By reset pincode when using the pincode only function an reader error event occurs, with Error description: “Error: Wrong numbers of characters received”
The Voxio-A-3100-A reader can be used in three different access modes, depending on the authentication mode setting on the reader and the card data interpretation setting of the cards being used.
The reader authentication method can be set at the general tab on the reader detail page.
Mode | Reader authentication method | How to link |
|---|---|---|
Card only | Not required | *Assign cards to people - Knowledge Base - Confluence (atlassian.net) |
Card+Pincode | Pincode required | *Assign cards to people - Knowledge Base - Confluence (atlassian.net) |
Card / Pincode only | Not required | *How to setup access with pincode-only (i80P) - Knowledge Base - Confluence (atlassian.net) |
6. Secure channel
OSDP v2 with Secure Channel has AES-128 encryption to ensure that communication between the targeted devices is strict and secure.
All OSDP devices have a known standard Secure Channel Base Key (SCBK), according to the OSDP specification. The SCBK is a key shared between the peripheral/reader and the controller, which is used once to initiate encryption. The SCBK allows the controller (Pluto/ApolloN) to send a challenge command (critical information that the peripheral/reader can use to initiate a Secure Channel session). Note that OSDP security is not limited to the Secure Channel Base Key. The SCBK is used only once at the start of the session before auto-generated session keys are used to encrypt the OSDP data.
If the security status is “Active scbkd” at the node you can set a random key with the button <Set keys (SC)>. If pressed the key is set into the reader and stored in the controller (Pluto / ApolloN)
Refresh the page to see the results.
The button <Set keys (SC)> generates and stores a key into the reader
The OSDP secure channel key himself is only visible for Root and Installer users
Once a key is set into the reader it cannot be cleared or rewritten by the system if the current key is not known. (not allowed in the OSDP protocol, security risk). If the key must be cleared (Reset) follow the procedure what is delivered by the reader manufacturer.