Information needed for using Mercury downstream controllers with Access Expert
EcoStruxure Access Expert
Access Expert V3 Hosted
List of Mercury downstream controller and configuration information
Mercury controllers are an open architecture controller made by Mercury Security. Access Expert supports the series 2 and series 3 SIO boards.
Controller Equivalent Features
Single-card reader interface panel and supports Wiegand, clock and data, magnetic stripe, F2F, Supervised F2F, OSDP, keypad, and biometrics reader technologies.
The MR52 is a dual-card reader interface panel. Each unit can connect two card readers, eight general-purpose input monitor points and six control relays to any Mercury EP series intelligent controller.
The MR16IN interface panel can support 16 general-purpose input circuits and two dedicated programmable relay outputs.
The MR16OUT interface panel provides 16 general-purpose outputs as Form C relay contacts.
The MR51e is a single-door, network-ready interface panel.
- Disconnect the power supply from the downstream and the controller.
- Set the RS485 jumper to the 2 wire position.
- Wire the RS485 communication from the downstream to the controller.
- Downstream Controller
TR+ CLK/Data1 TR- DAT/Data0 GND GND
- Downstream Controller
- Apply power to the downstream and the controller.
- In Access Expert, from the top bar menu (located at the top left corner of the screen) click on the ‘View All Hardware’ button to open the 'Hardware tree'.
- In the 'Hardware Tree', double click on the controller or right-click and select ‘Open’ top open the controller page.
- Alternatively, click on the 'Hardware Provisioning' tab (located a the top of the screen) to open the menu.
- Click on the 'Controllers' icon(located to the left of the 'Hardware Provisioning' menu to open the 'Controllers' page).
- Double click or right-click and select 'Open' on the controller, to open that controllers 'Controller Configuration' page.
- Click on the ‘Add downstream’ button (located at the top of the controller page) to add a downstream.
- From the drop-down menu, select the appropriate downstream model.
- Enter a unique ‘Display Name’ for the downstream.
- Set the ‘Panel Address’ of the downstream.
- Example: To set devices address to 3, DIP switch 1 and 3 must be ON and 2,3 and 4 OFF and 'Panel Address' in Access Xpert must be set to 3. The DIP switches on the downstream must match the ‘Panel Address’ in the 'Downstream Configuration' page.
Note: DIP switches 1 through 5 sets the device address of the downstream and is binary.
DIP switch 1 = 1, DIP switch 2 = 2, DIP switch 3 = 4, DIP switch 4 = 8, DIP switch 5 = 16
- Confirm that DIP switch 6 and 7 are in the ON position to enable for 38.400BPS communication.
- Leave DIP switch 8 in the OFF position.
- Click on the ‘Save’ button (located at the bottom of the page) to apply changes to the downstream.
Downstreams are added to Access Expert from the Controller page. When adding a downstream, you will need to select the downstream type from the drop-down list. If the downstream you are trying to add does not match one of the types listed, it is either not supported on that port or not supported by that controller.
|The EP/LP1501 has no SIO port||The EP/LP1501 uses the CLK and DATA on Reader 1 to communicate to downstreams. This means that if you are leveraging a downstream device, the EP/LP1501 only supports 1 onboard reader.|
|My MR52 is toggling on and offline.||
The MR52 has a conflicting address with another downstream. Confirm your dipswitches are set to the correct address.
Addressing is done on dipswitch 1-5 and baud rate is set on dipswitch 6 and 7 (suggested both on). Dipswitch 8 should always be off.
J3 - The jumper for 2 wire and 4 wire RS-485 also needs to be set. By default is set to 2 and should not need changing but this does happen.
J5 is the Termination jumper that needs to be set on the last unit in the series.
|My MR51e is programmed for Static IP but won't connect||
Check the dip switches on the board. Make sure the dip switches are set back to static IP mode after programming.
Check to make sure the static IP address programmed in is valid.
Make sure the Downstream can be seen by the controller.
|My downstream will not come online but my other downstream did.||
If you have a Mercury downstream on the same port as an Engage Gateway, the Mercury downstream will not be able to come online. Engage Gateway's and Mercury downstreams cannot share a port.
Confirm the addressing on your downstream is correct.
|My downstream device says "Timeout"||
This is due to incorrect addressing or incorrect baud rate set on the downstream.
Dipswitches 1-5 set the address in a binary fashion and dipswitches 6 and 7 set the baud rate. We suggest leaving both 6 and 7 on.
|My downstream device says it is in "loader mode" and will not leave that mode||
Follow the steps below to correct the loader mode: