Open

Installation Manual | TM-20231105 iProtect Access / Security | Functionalities | OSDP

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.

Introduction

This document is the installation and operation manual for OSDP readers.

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.

https://www.securityindustry.org/industry-standards/open-supervised-device-protocol/

Materials

• Card reader with OSDP protocol

• Card reader must be provided with key material to be able to read the desired cards.

General

OSDP readers are completely handled by the nodemanager, so the nodemanager should run to obtain access by a OSDP card reader.

Support and license

Below is an overview of support for both the hardware and the software, including the necessary license:

Setup an OSDP reader using auto discovery           

1. Connect the reader (see the documentation of the specifik reader)

2. Press on the discover button in the line dialog of the Pluto.

3. Wait until the discover process is ready
   (Read-in event=> Read-in event: Stop, Line: xxx…)

4. Refresh the line dialog, if an OSDP device is detected it will be shown as a Node below port 1 or 2 of the Orion.

5. If the <OSDP compatibility>  

6. Badge 2 times a card at the reader, now the reader will be added below the OSDP node in iProtect (adding the reader manually is also possible)

Detection of capabilitties:

When a OSDP reader is connected the first task of the OSDP driver is to ask the so called capabilities, depending on the reported capabilities functionalities will be actived or not.
The fist time that the reader is connected the most importand capabilities will be reported in the event: New node disvoverd=>

More detailed information is avaible in the system log files
example log:

Dec 9 13:46:37 Server48 kp77db: [kp77db] [9/13:46:37] Line=33: OSDP reader
Dec 9 13:46:37 server48 kp77db: [kp77db] [9/13:46:37] Line=33: Non compliant OSDP fixes:4
Dec 9 13:46:37 Server48 kp77db: [kp77db] [9/13:46:37] Line=33: - card data type bit array (max 1024)
Dec 9 13:46:37 Server48 kp77db: [kp77db] [9/13:46:37] Line=33: - 1 leds per reader: timed, tricolor
Dec 9 13:46:37 Server48 kp77db: [kp77db] [9/13:46:37] Line=33: - 1 audible annunciators per reader: timed
Dec 9 13:46:37 Server48 kp77db: [kp77db] [9/13:46:37] Line=33: - reader checksum: CRC16
Dec 9 13:46:37 Server48 kp77db: [kp77db] [9/13:46:37] Line=33: - reader encryption: AES 128
Dec 9 13:46:37 Server48 kp77db: [kp77db] [9/13:46:37] Line=33: - reader buffer size: 256 bytes

Setup an OSDP reader manually

1. Connect the reader (see chapter “Connecting the reader”)

2. Select the line to which the OSDP reader is connected

3. Select the Orion port to which the OSDP reader is connected

4. Add a node of type <OSDP>

5. Fill in the standard things like, name, code, etc

6. Set the desired OSDP address

7. Select OSDP compatibility
   a.    Fully compliant (default)
   b.    IDESCO (as non compliant)
   c.     IDESCO V2 (as non compliant)
   d.    No reader in capabilities (for OSDP card readers, reporting that no card reader is present.)

8. Select the desired baud rate and port settings

   1. Most used speed is: 9600, 19200 or 115K2  baud

   2. Port setting: N81

9. Activate the node

10. Press <SAVE>

11. Refresh page and check the points below.

    1. Check <Transmission Quality (%):)>   should be >= 95%

    2. Check <Version:>  version info should be available

12. Select the created node in the tree view.

13. Click on the right mouse button and select <Add reader>

10.  Set up the reader as usual

11.  For secure channel see chapter “Using the secure channel”

Using the 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.

When the reader communicates, a value is displayed in the <Security status>

If the status is “Active scbk” 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.

If the reader has allready a key, you can enter the key in the <password field> and save.

Reader settings :

For OSDP readers there are some specific reader settings.

Buzzer time card recognized: (Reader details- tab <Door behavior>)>

           
Tested readers

The readers below have been tested and can be implemented.