1.0 Introduction
OSDP readers are supported in Borealis when using NXT-MSC or True Mercury controllers.
Note: Currently Borealis will support one OSDP reader per controller bus.
OSDP (Open Supervised Device Protocol) is an access control communication standard developed by the Security Industry Association (SIA) to improve interoperability among access security products and is being endorsed by all leading access control manufacturers.
OSDP Main Features
- OSDP - Two-way AES 128-bit encrypted communications.
- OSDP - The reader (communication status) is supervised - you will know immediately in the software if the reader is compromised and goes offline.
- OSDP reader cable runs can span long distances (up to 4,000 feet).
- Open standard - Proprietary solutions are often not favored by modern enterprises.
- When readers are OSDP it enables better interoperability among different access control products.
- A trusted standard that is actively being developed by the SIA (Security Industry Association).
2.0 Reader Extension Cable Requirements
The recommended cable type for the reader extension cable is:
- Belden 9841 or equivalent (one twisted pair) for data combined with Belden 8461 or equivalent for the 18x2 power cable. This is physically two separate two conductor cables.
- Belden 9842 or equivalent (two twisted pairs in one jacket).
AWG 24 wire or larger. The total cable run length is 4,000 feet/1,000 meters.
Note: Increasing the wire gauge does not increase the total network length.
3.0 OSDP Reader Wiring
Note: OSDP readers will not always follow the same wire color conventions as shown in the image below. The TX+ and TX- wires may be a different color. Refer to the reader's installation guide to be sure.
4.0 Reader Addressing
IMPORTANT NOTES:
- By default, most OSDP readers will be addressed as 0.
- Some of the older OSDP reader types do not support auto-discovery and so you will need to refer to the manufacturers supporting documentation for details about manually setting the reader address and the BAUD rate locally at the reader.
- Once a reader has been configured as an OSDP reader nothing else can be connected to that bus (for example; an NXT 4X4 module) - because OSDP uses a different RS-485 protocol.
5.0 Setup Instructions
The following steps explain how to setup an OSDP reader in Borealis:
- Connect the OSDP reader to the controller bus.
- In Borealis, go to Hardware >> All.
The hardware tree will be displayed.
Click the controller which has the OSDP reader connected.
Click the arrow next to the bus that the OSDP reader is connected.
Expand the reader and then select the reader on the hardware tree.
The reader properties will be displayed on the right.
Click the EDIT button.
Scroll down the reader settings and locate the LED and Buzzer setting.
Use the drop-down menu and select OSDP.
- Leave the address at the default of 0.
- Set the OSDP baud rate to that configured on the reader. Note: Most OSDP readers are, by default, set to 9,600 baud rate.
- Save the OSDP reader settings.
- Within a few seconds the reader's status should show as online.
6.0 OSDP Secure Channel
6.1 OSDP Secure Channel Overview
The OSDP Secure Channel ties the reader to a specific NXT-MSC controller using a unique encryption key. The encryption key, once created is stored on the OSDP reader and on the NXT-MSC controller. Once enabled you will not then be able to use the OSDP reader on a different controller.
6.2 Enabling OSDP Secure Channel on an OSDP Reader
Multiple OSDP reader vendors have the option to configure an OSDP reader with a secure channel. This is typically done using a third-party utility, such as HID's Reader Manager app. To configure the reader with an OSDP channel you must first establish communication using OSDP v2 Install Mode. Install mode is the factory default mode of an HID reader enabled with OSDP.
Notes:
- The following steps assume you have installed the HID Reader Manager app on your phone and have registered and verified your HID account.
- As well as enabling the OSDP Secure Channel, the app allows you to configure other OSDP settings, such as; the address number and OSDP baud rate.
- The steps may differ slightly for other OSDP vendors - refer to the reader vendor's documentation for specific OSDP Secure Channel setup instructions.
The following steps explain how to enable the OSDP Secure Channel on an HID Signo or iClass SE reader using the HID Reader Manager app.
- Ensure NFC or Bluetooth is enabled on your smart device (depending on which method you wish to use to connect to the reader).
- Log into the HID Reader Manager app (with your registered e-mail and password).
- Once connected, the reader summary will be displayed.
- Scroll down the reader details and select Detailed Configuration.
- If prompted, power-cycle the reader by physically disconnecting the reader terminal block from the controller.
- Select Communication Protocol.
- Scroll down and turn on the Secure Mode option.
Note: Near the OSDP Mode setting you will also see the reader address and OSDP baud rate. The default address is 00 and the default baud rate is 9,600. These are also the default address and baud rate settings in Borealis.
- Select Add to Template then select Apply Selected Items.
- Within a few seconds the secure channel settings will be written to the OSDP reader.
- You must now go to the OSDP reader settings in Borealis and enable the OSDP Secure Channel option.
- You should also verify that the address and the baud rate matches what is displayed in the Reader Manager app.
- Once the reader status shows online in Borealis, the OSDP reader will be communicating with the NXT-MSC controller using the unique encryption key.
6.3 Transferring the OSDP Reader to a Different Controller
Important Note: If the reader needs to be transferred to a different controller you would need to use the app to reset the OSDP channel which will remove the encryption key. The reader should be set back to the factory default Install Mode using the HID Reader Manager App and you then configure the Secure Channel again while the reader is connected to the new/different controller.