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.

Table of contents

1. Introduction

This article explains how you can implement the Nedap target reader based on OSDP communication and describes the functions and settings.

Open

2. Support and license

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

2.1 Supported cards

• UHF DNA cards for specific project

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.

4. Installation

4.1 Connecting the reader

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.

5.2 Configure the reader in iProtect

Follow the steps below to configure an OSDP reader:

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

2. Press 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 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.

5. Change the OSDP compatibility setting at the OSDP node to “No reader in capabilities”
   (Not full compliant with OSDP)

6. 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.

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.

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.

7. General notes

By normal operation:

• The red led ON, Idle situation

• The red led is Blinking, Access denied

• The green led is ON, Access granted

• The led is purple when the connection is lost with the stacked Orion

8. iProtect settings

8.1 Card data presentation

Nedap target, with DNA tags:

8.2 Card data interpretation