Mercury EP1501 and EP1502 controllers
EP1501 and EP1502 power supply
EP1501 and EP1502 can ether be powered by power supply or POE. If the controller will be powered by supply power, the “power selector jumper” has to be connected on 12V and the middle section, if POE – on POE and middle section.
1. EP1501 and EP1502 configuration process
A video tutorial on how to configure and add a Mercury controller to CredoID can be found here.
Controller network setup depends on the configuration of your network. You may use either DHCP server or assign static IP addresses to controllers. If the controller is on a different segment of the network, you must enter gateway addresses as well.
Connect an ethernet cable to the controller and enable controllers default settings, by turning ON first (“1”) switch in DIP switches.
Open an internet browser (preferably internet explorer or mozilla firefox) and enter the controllers web configuration page with IP 192.168.0.251. Login in:
- User name: admin
- Password: password
Configure network settings in “Network” tab and Host communications in “Host Comm”. After configuring network settings, create a new user admin in “User” tab. Enter username and password, and then click “Save”.
After the user has been created, go to “Apply settings” tab. Before applying the settings, turn OFF first switch (“1”) in DIP switches and then apply a reboot for the controller.
2. Controller configuration in CredoID software
In CredoID software, controllers and readers are either added automatically by clicking Search for new devices button in device tab or adding the controller manually. To be able to add Mercury controllers automatically, Bonjour software has to be installed on the system.
a) Configuring Mercury controller with Search for new devices function:
b) Adding controller without Bonjour installed, manually:
- Device MAC address. MAC address can be found in devices web configuration settings (connecting through a web browser), network tab. The MAC address is displayed in “Host name of this device”.
- Device IP address. Enter devices IP. Mercury’s devices default IP address is 192.168.0.251.
- TCP service port. By default, Mercury controllers use 3001 port.
- Here I am interval(s). Identifies Here I am interval. By default, it is set on 20 seconds.
- User name & Password. The login credentials that are used to login to Mercury's controllers. These credentials are configured on Mercury's controllers web configuration screen.
- Use 1st reader port for slave devices. Enables use of slave devices for EP1501 controller through the first reader port.
Warning! If PIN only reader is used with Mercury devices, card must be added manually to the user, otherwise device will go into corrupt state during "Device upload". It is not required to have physical card, unique numbers can be used at card information.
Configuring slave devices
Mercury controllers supported slave devices:
- Assa Abloy Aperio Hub.
How to add slave devices to Mercury controllers:
- Click Slave devices button on the Details panel to open up Slave devices window.
- Select the Baud rate that will be used to connect with the slave devices.
Important! If Baud rate is changed, the devices settings have to be saved in order for Baud rate to fully change on the device.
- Click Detect slave devices button to search for any devices that are connected to the Mercury controller. This will add any devices it can pick automatically, setting up the correct Panel number and Device type. It is also possible to add slave devices manually, by clicking Add button and then configuring the slave devices.
- After slave devices have been configured, click OK and then save the Mercury settings.
Assa Abloy support
Mercury controllers support Assa Abloy Aperio Hubs, able to connect them as slave devices by connecting them through RS-485. For more information on how Aperio Hubs should be connected with the Mercury controllers, please read the user manuals of the EP1501, EP1502 and AH30 devices.
To be able to successfully connect a Aperio Hubs with Mercury, these steps has to be taken:
- Correct RS-485 connection between the devices.
- Mercury's controllers Baud rate has to be set on 38400.
- The Aperio Hub has to be configured and linked with its readers and locks. Aperio Programming application with the Wireless lock technology USB is used for this process, which can be received from the Assa Abloy or from your installer.
- Aperio Hub's panel number address has to be set correctly. This is done by turning different DIP switches on the Hub.
After the preparations are made, it can be connected to CredoID as a Mercury's slave device. The Mercury controller should be able to pick up AssaAbloy slave device automatically, by clicking Detect slave devices button. If it doesn't pick it up, you can add the device manually (note, that it doesn't mean that it would fully connect with the device).
Note #1. If Mercury controller EP1501 is used, the checkbox Use 1st reader port for slave devices has to be checked on Device tab to be able to connect slave devices to EP1501. This does not apply to EP1502.
Note #2. If Baud rate is changed, the devices settings have to be saved in order for Baud rate to fully change on the device.
When an AssaAbloy slave device is added to the Mercury controller, Aperio readers and lock sensors can be assigned to doors on Doors tab. On how to configure doors on Doors tab, follow Door configuration manual.
When configuring an Assa Abloy Aperio Hub, 2 lines on the doors Details panel change: Reader address and Door sensor address. In this fields an address is selected from 0-7 (total of 8 addresses) whom are assigned to readers or door sensors. To which address the readers are assigned to, can be viewed on Aperio Programming application.
Reader address describes which readers open doors while Door sensor address describes door sensors who monitor doors activity. Door sensor address is not mandatory to be configured for the door settings, but without it, the door won't be monitored, as in events such as Door open/closed, Door held open and Door forced open won't be received.
After the last configuration process, it works like a normal reader.
Note #3. If an Aperio reader has an exit button/handle, it can be configured as an Exit button. This allows to receive events, indicating when the Exit button has been pressed.