To have the Transit Output the OSDP Protocol you will need to purchase and install an additional OSDP board.
- 9229078 OSDP Installation Board (includes PCC485)
- 9565817 PCC485 OSDP Protocol Converter Board.
Wiring:
Configuration.
TRANSIT firmware requirements
The OSDP Interface Board / PCC485 requires to use one of the following TRANSIT firmware versions, since these support the manual LED and relay control function.
• P80 v3.00 (no configuration required, use default settings)
• P81 v3.35
• P82 v3.08
• P83 v3.04
• P84 v3.06
• P85 v3.01
Newer versions are also supported as they will be backwards compatible.
When Configuring the Nedap Readers, you will need to have a USB to RS485 Converter to make changes to LED functionality, Polling interval, etc. Some limited features such as Device Address Settings can be done in the OSDPTool. When Connected to the USB Port, the Serial communication is blocked.
Configuration settings
The relay activation and LED control must both be set to manual mode.
This is best done using the NEDAP P81TEST software. Download this software from our partner portal https://portal.nedapidentification.com.
Start NEDAP P81TEST software and connect to the reader using the USB or RS232 interface.
1. Click Options, Digital I/O.
2. Disable automatic relay activation.
3. Disable automatic LED control.
OSDP Output format.
The Window Buttons, Booster ID, Compact Clamshell Tag and HD tags will output one event in Raw hex format without a Facility Code and parity Bits. The Facility Code and parity bits are set at the reader level with the Transit Product Line.
Example Window button read event:
01000011001110011110 Hex: 4339E Decimal: 275358
For a Prox Booster application, the booster ID will be sent without the FC but the card information will have the FC, as it passes the card information as it is configured on the card*.
*The card information will be sent with the leading and trailing parity bit in accordance to the Wiegand Protocol so you will need to offset the bit structure to get the card ID.
If the packet of information is sent “as is” in raw hex string, it will not output the UID printed on the tag. There is an additional bit at the end of the hex string. This is the bit for parity in Wiegand. You will need to set up your panel with an offset of 1 bit. You will need to set up the panel to know where to look for the ID printed on the credential (Typically FC 72-79 and TID located in bit 80-95).
Prox 2G Read example Dual event:
Booster ID
00100110100111101001 Hex: 269E9 Dec: 158185
Card ID
000101000110101100110011 Hex: 146B33
0010100011010110011001 Dec: 13721 W26 bit format
Prox 2G Read example Single event:
The Booster Info is sent 1st 269E9 then the card info 146B33 in raw hex
You would need to configure your Panel to receive the message properly if this was the set up chosen.
Smartcard Booster read example:
For the Smart Card Booster, the default setting is to read the portion of the Card Serial Number (CSN) and output it as a UID.
The 1st two reads are sent in Dual Id format
The 3rd read is in one event message Booster ID followed by card ID.
If you configure the MiFARE card to read the exact card ID through the Smart Card Booster configuration Software, you will have to make sure you set up the panel to the correct offset. Information available for download “Booster 2G installation guide”