4.0 Reader Addressing

IMPORTANT NOTES:

• By default, most OSDP readers will be addressed as 0 (so they will be seen by the controller as a standard entry reader). This means if you were to initially connect 2 new readers to the same bus they would both be addressed as reader 0 and will not communicate.
• 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 (except for a second OSDP reader).

5.0 Adding a Single OSDP Reader

This assumes you already have a Mercury controller added and online in Doors.NET and it also assumes both readers support auto-discovery.

1. From within Doors.NET, go to Setup >> Hardware Setup >> All to display the hardware tree.
2. Expand the controller and select the reader that is an OSDP reader. The reader properties will be displayed on the right.
3. Ensured that Advanced View is enabled for the reader properties.
4. Scroll down the properties until you locate LED/Buzzer. Set this to 'OSDP reader'.
   
   
   
   
5. The reader's Manufacturer Model at the top of the properties will automatically set the model as Generic OSDP reader.
   
   
   
   
6. Save the reader settings.
7. As you will see, in the previous image, the default address number is 0 - so if you only have a single reader connected, the controller will start communicating with the reader as soon as the reader settings have been saved.
8. In live events, you should see a reader online event.
   
   
   

6.0 Adding an OSDP Exit Reader

When adding a second reader to the bus you should setup the readers individually as per the following instructions - (because communication will not be possible when both readers have the same default address 0). The following steps require you to be logged into Doors.NET as a system administrator. If the system will be using multiple entry and exit readers you could configure (and label) all the readers as either exit readers or entry readers prior to going to site.

6.1 Add and Configure the OSDP Exit reader

When adding two OSDP readers to the same bus (to control the same door), the easiest method is to add and configure the Exit reader and for the Entry reader to initially be disconnected.

1. Connect ONLY the exit reader into the controller's bus.
2. Add the reader following the steps defined in the previous section.
3. When the reader is online, in the reader properties, set the reader to address 1.
4. Save the reader settings.
5. The reader will go offline.
6. Right-click the reader in the hardware tree and select OSDP >> Auto-Discovery.
   
   
   
   
7. Wait a few seconds and then the reader will come back online and will be addressed as number 1.
8. Next, click the Design Mode icon to enable design mode.
   
   
   
   
9. Right-click the entry reader and select OSDP >> Polling Disabled.
   
   
   
   
10. The OSDP Exit reader will then be offline.

6.2 Setup and Add the Entry Reader Second

Once the exit reader has been addressed as number 1 and is online, you can do the following:

1. In Doors.NET, select the 'Onboard MR52'
2. From the hardware browser ribbon bar at the top of the screen, select Add ACR.
3. A dialog box will appear.
4. Leave the default selected reader selected (Reader 1, Secondary).
5. Click the ACCEPT button.
6. At the bottom of the dialog box you will see in red text that the controller will require a memory reset.
   
   
   
   
7. Confirm the prompt to reset the controller.
8. The additional reader will be added to the hardware tree.
   
   
   
   
9. Select the new reader that has been added.
10. In the reader properties, ensure advanced view is enabled.
11. Scroll down to the OSDP reader settings.
12. The reader should already be configured as address 0.
    
    
    
    
13. Connect the entry reader to the same bus that the exit reader is connected.
14. Right-click the entry reader again and select OSDP >> Normal Polling.
15. Both OSDP readers should now be online.
    
    

7.0 Auto-Discovery Change Address

The newer OSDP readers support 'auto-discovery' this will allow you to change the reader's address from the Doors.NET soft ware (again, this requires you to be logged into Doors.NET as a system administrator and you will need to momentarily enable Design Mode).

1. Enable Design Mode (via the Design Mode icon):
   
   
   
   
2. Select the reader in the hardware tree.
3. In the reader properties, change the reader address number.
4. Save the reader settings.
5. Right-click the reader in the hardware tree and select OSDP >> Auto-Discovery.
   
   
   
   
6. The reader will momentarily go offline. Once it is back online it will be configured with its new address.

8.0 Set the Correct LED Modes

When you add an OSDP reader, the default LED mode (when the reader is locked) is slowly flashing red. The following steps explain how you can set a different LED mode to the readers (for example, to match a Standard Wiegand reader which will typically display an amber LED when locked.

1. Ensure Design Mode is enabled.
2. Close and re-open the hardware tree if it is already open.
3. On the hardware tree you will see a node named 'LED Modes'.
4. Select this new node.
5. From the ribbon bar at the top, click Add LED icon.
   
   
   
   
6. Select the Undefined entry that appears on the hardware tree.
7. The LED Mode properties will be on the right.
8. From the LED mode drop-down list, select Mode 2.
9. From the Reader Function drop-down list, select Locked.
10. Set the ON color to amber.
11. Set the ON time to 500 ms.
12. Set the OFF color to amber.
13. Set the OFF time to 500 ms.
    
    
    
    
14. Save the LED Mode settings.
15. When the reader is locked, the LED will then be solid amber.
16. You can then configure how you wish for the LED to behave for each of the other reader functions.
17. For example, when the reader is unlocked you could either have a solid green LED or if the reader is in Card + PIN mode you could configure the reader LED to alternate between flashing red and green.

9.0 OSDP Reader Supervision

Because the OSDP readers are fully supervised, if the reader is disconnected there will be an event displayed in live events.

You can configure this event type to generate a sound alert at the PC or you could configure an e-mail or SMS message to be immediately sent out to a designated recipient.

10.0 OSDP Status Information

1. The Doors.NET software will detect the reader vendor, the model, the version number and the reader serial number (which you can view by selecting the reader in the hardware tree). The reader properties display on the right.
2. Scroll down the reader properties and locate OSDP Status.
3. The reader vendor and model details will be displayed.
   
   
   
   

11.0 OSDP Reader Firmware Upgrading

To be implemented in a future Doors.NET release.