...
...
PUBLIC
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 NVITE reader based on OSDP communication and describes the functions and settings.
The NVITE reader can be used with multiple identification technologies for variety of users, such as staff, tenants and visitors. Identification is depending on the userenabled technologies: presenting a card, scanning a barcode or activating a smartphone credential. Typical applications are access control to car parks, perimeter gates, office buildings and warehouses.
...
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.3.15 | iProtect basic license |
Sufficient reader license |
2.1 Supported
...
Card type
...
Description
...
cards
TKH coded
...
DESFire cards
QR code
...
| Note |
|---|
The card reader must be provided with key material to be able to read the desired cards. |
Other cards or custom keys on request.
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.
...
| Info |
|---|
OSDP readers are only supported by stacked Orions (RS485 connection) |
4. Installation
4.1 Connecting the reader
Nedap cable pigtail | CAT5 cable > Orion PRT 1 or 2 | Signal |
|---|---|---|
Brown | Orange&Green | RS485 A |
Green | White/Orange & White/Green | RS485 B |
Black | Brown | 0VDC |
Red | External Power supply | 12-24VDC |
| Info |
|---|
Max. cable distance between Orion and the NVITE reader = 120 Mtr. This is based on CAT5E - 24AWG cable. |
Reader must be powered by 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.1 Configure the reader in iProtect
Follow the steps below to configure an OSDP reader:
...
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.2.2 NVITE OSDP defaults
OSDP address | 0 |
Communication speed | 9600 baud |
Port setting | N81 |
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) |
| Info |
|---|
Most used setting for buzzer time = 2 |
6. Secure channel
OSDP v2 with Secure Channel has AES-128 encryption to ensure that communication between the targeted devices is strict and secure.
...
| Note |
|---|
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. |
7. Settings card
...
coding
7.1 NVITE DESFire
This below cardata interpretation can be linked to the existing DESFire card number presentation.
In iProtect browse to the menu Access → Settings → Card coding → Card data interpretation. Right mouse click in the treeview dialogue and click Add card data interpretation.
Enter the following data:
Name: | OSDP NVITE DESfire |
Card number presentation: | Select the existing DESFire presentation |
Format: |
|
Reader communication protocol: | ABA |
Card type: | None |
Data Length: | 16 |
System code: |
|
Start: | 5 |
Code: | 002974 (for demo cards) |
Facility: |
|
Start: | 1 |
Code: | 0600 |
Card number: |
|
Start | 11 |
Length: | 6 |
Modulo: |
|
Offset: |
|
Interpretation selection |
|
Start: | 1 |
Length: | 0 |
Code: |
|
Expire date: |
|
Start | 1 |
Length: | 0 |
Date control: | No expire date check |
Format: | YYMMDD |
Keypad | Do not change |
Offline Validity: | Do not change |
SV WO: | Do not change |
Consistency: | Do not change |
7.2 NVITE Crypted QR
The card data interpretation below can be linked to a standard QR code presentation, which can be generated using the card number presentation wizard.
In iProtect, navigate to the menu Access → Settings → Card coding → Card number presentation.
Right-click in the treeview dialog and select 'Wizard card number presentation.'
Enter a logical name and choose the QR code option from the default card data interpretation list.
Click the OK button.
After refreshing the page, you will see a new card number presentation and a corresponding card data interpretation. Modify the card data interpretation settings as follows:
Name: | OSDP NVITE QR crypted |
Format: |
|
Reader communication protocol: | Hexadecimal |
Card type: | QR barcode |
Encryption: | Aes128 |
Encryption key: | your key |
Data Length: | 32 |
System code: |
|
Start: | 1 |
Length: | 6 |
Code: | 000b9e (for demo cards) |
Facility: |
|
Start: | 1 |
Length: | 11 |
Code: | 00000000000 |
Card number: |
|
Start | 7 |
Length: | 6 |
Modulo: |
|
Offset: |
|
Interpretation selection |
|
Start: | 0 |
Length: | 0 |
Code: |
|
Expire date: |
|
Start | 13 |
Length: | 8 |
Date control: | Expire date check, including date |
Format: | YYYYMMDD |
Keypad | Do not change |
Offline Validity: | Do not change |
SV WO: | Do not change |
Conssistancy: | Do not change |
Filter: |
|
Start tag: | 0300 |
End tag: |
|