OSDP is a bi-directional protocol that can be used to communicate between devices. When used with readers it has advantages over the typical Wiegand and Clock/Data protocols in that the communication is bi-directional. This allows functionality like clock updates, LCD text updates, and detecting if the device is online.
OSDP Readers require at least Access It! Universal.NET Version 5.2+ to add within the Access It! Universal.NET software.
Functionality for clock and LCD text updates currently exist only on the MR-DT keypad.
The following Mercury-Security panels currently support OSDP version 0.9:
The following Mercury-Security panels currently support OSDP version 2.1.6 w/ secure channel:
*In certain installation environments, OSDP readers are interpreting a non-driven 485-line as data. This interpretation results in a communication fault that is inhibiting the panel and reader from properly communicating. Place a 120Ω +/- 2Ω resistor on the panel side to pull down the Mercury RS485- (D0) to GND line. This will create a communication bias that will keep the reader from improperly interpreting data. To function properly, there must be no ground faults in the installation. Please ensure that the DC Ground (power supply return) is not connected to earth ground.
In order to add an OSDP reader to an Access It! Universal.NET system, the reader must support the following:
Hardware / Wiring References
|HID OSDP Reader||Panel Reader Port|
|Farpointe Data OSDP Reader||Panel Reader Port|
Creating OSDP Format
Within Access It! Universal.NET, the following steps must be taken.
Secure Channel Configuration
Enabling the Secure Channel OSDP setting will encrypt the data communication between the OSDP reader and the SIO reader port. Prior to the following steps, the reader must ready to accept the default key in order to begin using encrypted communication.
Please note that once a reader has been paired to an encrypted reader channel, the reader is married to that specific port for life and will no longer work with any other reader port without first being unpaired. To un-pair a reader RS2 Technical Support needs to be engaged.
Not all OSDP readers support Secure Channel. Consult the reader manufacturer for Secure Channel compatibility.