Enrolling Mercury controllers on the Synergis unit

2022-07-04Last updated

To have the Synergis™ unit communicate with the Mercury controllers connected to it, you must enroll them using Security Center Config Tool.

Before you begin

Prepare the Mercury controller for enrollment.

What you should know

Mercury controllers enrolled on a Synergis™ unit are not visible from the Synergis™ Appliance Portal Hardware page.

On the Synergis unit, each Mercury controller must be assigned a unique channel ID. All Mercury controllers have RS-485 buses to which the interface panels (MR50, MR52, MR16IN, and MR16OUT) are connected. Each interface panel connected to the same RS-485 or Ethernet bus must have a unique physical address.

Procedure

  1. From the Config Tool homepage, open the Access control task.
  2. Click Roles and units, and then click the Synergis unit.
  3. Click Peripherals, and then click Add an item ().
    Dialog box that opens in Config Tool when you add peripherals to a Synergis unit.
  4. Enter the following information:
    Model
    Model of the controller.
    IP address
    Static IP address assigned to the controller by your IT department.
    Hostname
    Click the blue link to identify the controller by its hostname. This option is only available if you’re running Security Center 5.12.0.0 or later.
    Note: When enrolling a Mercury controller with its hostname, you must append the hostname with .local if the controller is not registered to DHCP and DNS on the network.
    Port
    Communication port. The default value is 3001. The port must match the value configured on the Mercury Device Manager web page.
    Channel
    Channel ID corresponding to this controller. The channel ID can be any value 0 - 63, and must be unique within the Synergis unit. After it’s assigned, it must not be changed.
  5. If the selected controller model supports downstream panels, add them.
    Note: Consider the following:
    • For MR51e PoE panels, add them after enrolling the controller.
    • For EP1501, LP1501, and MP1501 controllers, do not to exceed the limit of eight downstream panels per controller, as recommended by Mercury.
    • The M5-20IN panel occupies two consecutive addresses on the communication bus. To have the 20 inputs of the M5-20IN panel, you must add two M5-20IN panels in Config Tool to your M5-IC controller. The address of the first panel must match the physical address on the M5-20IN panel, and the address of the second panel must be set to the address of the first panel plus one.
    • MR62e units can have an IPv6 address, but cannot communicate with Mercury controllers through IPv6.
    1. Under the Interfaces list, click Add an item ().
    2. In the dialog box that opens, select the downstream panel's Model, the Port, the Address (0 - 31), and when applicable, the IP address.
      All panels connected to the same port must use a different address.
    3. Click OK.
    4. Repeat as necessary.
  6. (Optional) Click Advanced settings to change the advanced settings.
    The available settings depend on the selected controller model. You can typically change the baud rate of the available serial port, the custom supervised input values, and the power input event configuration.
    Advanced settings dialog box for a Mercury controller in Config Tool.
    Note: You can set up to four different custom presets on your Mercury controller's inputs. For users upgrading from earlier Security Center versions who have a custom value configured, that preset is listed as Custom 1 in the AD limit rows list.
  7. Click OK at the bottom of the dialog box.
  8. Click Apply.
    The Mercury controller with all its connected downstream panels and peripheral devices are displayed on the Peripherals page.
    Peripherals page of a Mercury controller in Config Tool.
    Adding interface modules to the Synergis unit causes the unit to perform a software restart. During this process, the Synergis unit and all peripherals attached to it appear offline (in red).
  9. Select each of the discovered I/O devices and readers, and configure their properties as necessary.
    For OSDP (Secure Channel) readers, see Adding OSDP (Secure Channel) readers to a Mercury controller.
  10. Test your wiring and configuration by triggering the inputs and outputs.
    The triggered I/O changes state in real time on screen.
    Note: Reader activities are not shown on the Peripherals page.

After you finish

If applicable, add the MR51e panels to the Mercury controller, and then map the physical wiring of the interface modules to the doors and zones in Security Center.