IS2000: Mercury: Hardware Setup Guide

following guide provides steps to configure and initialize the Mercury IP controller panel in the IS2000 Software. Use this guide as a quick reference. Please contact IMRON Corporation for questions.

Considerations Prior to Setup

Please ensure that you are NOT using a legacy Mercury panel (i.e. you are NOT using the SCP-C, SCP-E, or SCP-S panel). This guide will assist you in setting up the EPC-1, SCP-2, or SCP-M controller.

Setting Up the Mercury IP Hardware

I. Accessing the Network Page of the Mercury Controller

  1. Disconnect power to the Mercury Controller (SCP-2, SCP-M, and EPC-1).
  2. Flip all DIP switches to the ON position and connect power to the controller.
  3. From a PC or Laptop, connect directly to the controller via a cross-over cable.
  4. Open a web browser and type: (See Figure 1)

Note: In order for a connection to be established, the computer must be on the same subnet as the controller. Please see the example below for an example for the computer network settings.


Figure 1:


5. Enter the username and password as follows: (see Figure 2)

User Name: admin

Password: password

Note: For firmware version 1.90 and later, you must complete steps 4-5 within five (5) minutes of flipping all DIP switches to the ON position. If not, toggle dip switch #1 from ON to OFF to ON three (3) times and you will have another five (5) minutes to complete steps 4-5. Each time you flip dip switch #1 from ON to OFF to ON, doing so counts as one time. This needs to be completed three times total.

Figure 2:


6. Click on “Network” on the left of the page to configure the network settings. IMRON recommends that the user NOT use DHCP. (See Figure 3)

Figure 3:


7. Select “Use Static IP Configuration” and enter the correct network parameters. Click “Accept”. From the menu (on the left), click “Apply Settings”. (See Figure 4)

Figure 4:


8. Click “Apply Settings, Reboot”. (See Figure 5)

Figure 5:


9. After clicking on the “Apply Settings, Reboot” button, a new webpage will load that confirms a) that the user understands that all the dip switches are not set to the normal position, and b) no user account has been defined. Check both boxes and click “Yes” to proceed. (See Figure 6)

Figure 6

10. The save and reboot process takes about 1-2 minutes. Once this is complete, disconnect power to the controller and flip all 4 DIP switches to the OFF position and re-connect power to the controller.

11. Proceed by adding the controller via IS2000 using the programmed IP address.

II. Setting Up the Mercury Controller in IS2000

  1. Launch IS2000 and navigate to the Hardware Manager module. Unlock the module by clicking the lock in the command toolbar. Right click in the hardware tree and select “Edit” to display the “Add Driver” command from the popup menu. Click on “Add Driver” to view the “Add a New Driver” popup menu. (See Figure 7)

Figure 7:


  1. From the “New Driver” popup menu, click on the “Access Control Drivers” category. Select the “EPC/SCP Mercury Access Control” driver. Click the OK (See Figure 8)

Figure 8:


  1. Set the “Service username” and “Service Password” for the Driver. This is typically a local Windows user account that will be used to run the driver as a Windows Service. Click Save. (See Figure 9)

Note: The “Service User” needs to have rights to run Windows services. Usually, an Admin account will have the rights. If using a domain account, enter the full name. In the example below, the full name would be: (DOMAINNAME\Abdul).

Figure 9:


  1. Select the Mercury driver from the hardware tree. Right click on the driver to bring up the popup menu. Select “Edit” and then “Add Controller.” (See Figure 10)

Figure 10:


  1. There are two ways to add a controller. Controller(s) can be added manually one at a time or you can scan the network and add controllers.

a. To scan the network to add controllers, use auto setup and check the box next to the controller with the proper IP address that you wish to add.

Note: More than one controller can be added simultaneously using the Auto Setup tool.

Note: If using the auto setup tool, controllers can be viewed in the auto setup tool if they are in the same subnet. If you scan for the controllers with the auto setup tool but cannot see the controller, it is likely that the controller’s IP address is set out of the server’s reach because they are not on the same subnet. If this is the case, you will have to add the controller manually.


In the alternative, you can manually add controllers by using the manual setup. Select the controller type (here, the appropriate Mercury Controller).  Select the Controller Address from the drop down menu and the Controller Group from the drop down menu.

Note: When adding a Mercury panel, the IP address and the model type needs to be added MANUALLY in the properties section of the Mercury controller.

Click the “OK” button below to continue. (See Figure 11)

Figure 11:


  1. Mercury currently offers three (3) types of controllers. If you added the controller using the auto setup feature, IS2000 will ask you which type you are using when adding the controller(s) to the hardware tree for the correct model.

Note: If you added the controller manually, skip to step 7.

IS2000 will ask if the controller is an EPC-1. Click “Yes” if this is an EPC-1 or “No” to continue. (See Figure 12)

Figure 12:


If this controller is NOT an EPC-1, IS2000 will ask if the controller is a SCP-2. Click “Yes” if the controller is a SCP-2 or “No” if the controller is a SCP-M. (See Figure 13)

Figure 13:


  1. If you are using sub-controllers, you will need to add the sub-controllers separately. To add sub-controllers, right click on the Mercury controller. Click on “Edit” and then click on “Add Sub-Controller”. (See Figure 14)

Once you have the driver running and the controller online, you can use the auto scan tool. IMRON highly recommends using the “Auto Scan” tool to add sub-controllers to verify that the sub-controllers are online and communicating.

In the alternative, you can also also add sub-controllers manually, regardless of whether the driver is running and whether the controller is online.

For information regarding adding a sub-controller with the auto setup tool or manually, please refer to step 5.

Figure 14:


  1. Starting the Driver:

Select the Mercury Driver in the hardware tree, right click on the driver, and select the “Start Driver” item from the “Driver Commands” menu. (See Figure 15)

Figure 15:

  1. Once the driver starts, a green box showing “EPC” will appear in the information window in the top right. The Driver Status Screen should display “Running” in green along with the Time Date of the Driver, the Driver version, and the DLL Version. (See Figure 16)

Figure 16:

  1. Expand the hardware tree and select each device to set properties. Click on the Save command from the command toolbar. The Controller Status screen should appear with a green “ONLINE” status. (See Figure 17)

Figure 17:


  1. Once you are ready to download to the controller(s), click on the Download button located on the command toolbar. Select the Mercury controller(s) to download to. Ensure that the database items are checked. Click on “Begin Download” to initiate a download to the selected controller(s). (See Figure 18)

Figure 18:


  1. Right click on a Reader to test Unlock/Lock Commands. Events will now appear in real-time on the Event Manager. (See Figure 19)

Figure 19:

III. Mercury Controller Properties in Hardware Manager

Below is a list the properties for Mercury hardware. Each hardware device has its own set of properties that can be configured to allow the operator to customize the hardware to meet their needs.

To access the controller properties, go to the Hardware Manager. Click on the pad to unlock the Hardware module to view the controller properties box. Highlight the controller from the hardware tree. (See Figure 20)

Note: Without unlocking the Hardware module, you will NOT be able to view the controller properties box.

Figure 20:


  • Ping Test – This function a one-time Ping test to the controller to see if the controller is online and communicating.
  • Address– The Address field displays the driver number the controller is assigned to in the first digit and the controller address in the second digit.  For example, 2.0 would be driver 2 controller 0.
  • Physical_Address– This is the physical address of the controller, which you can set up within the controller’s web page. Typically, IMRON recommends using a physical address of “0” for all controllers. This number should not be changed.
  • Controller_Type– This value will be automatically selected if the controller was added using the Auto-Setup feature.  If the controller has been added using this feature, the field will be grayed out and will not be configurable.  If the controller has been added manually, the operator must designate the type of device to add.
  • Poll– Check box value to determine whether or not communication attempts to be made to this controller.  With the box checked, communication will be attempted.
  • Connection_Type– The type of connection that will be used to communicate to the controller (Serial, Ethernet, Dial up).  For best performance, Ethernet is the recommended connection type.  To select the connection type, click on the drop down arrow to the right of the Connection_Type tag.  Highlight the desired connection type from the list provided and click OK to save the changes.
  • Sub_Controller_Baud_Rate– The speed in which the controller will communicate to its sub-controllers.  This speed is always set to 38400. This value must match the value programmed into the controller device.  If the two values do not match, communication to the sub-controller will not be available.  To select the baud rate, click on the drop down pick list located to the right of the Sub_Controller_Baud_Rate tag and select the baud rate.
  • Channel– Defines the communication pathway between a driver and a controller.  (Multi-drop is achieved by assigning the same channel to 2 controllers.) To configure the Channel, please follow the steps below:
  • Channel – Click the drop down arrow to the right of the Channel tag to select the channel number.
  • Port – The port should be set to port 3001.
  • Baud Rate – Select the baud rate by clicking on the drop down arrow to the right of the Baud Rate tag.
  • Time out – the Time out value should be set to 1000, it is not recommended that this value is changed.  Should the value be set to something other than 1000, communication issues may occur.
  • Retry – This value should be set to 10000.
  • Click the green check mark to save changes and return to the Hardware Manager screen.
  • Retry_Count– The number of attempts a controller will make before reporting a sub-controller offline.  This value is generally set to a value of three (3), but can be modified.  To modify the Retry_Count, click in the text box to the right of the Retry_Count tag and type the numeric value.  Click the floppy disc icon to save changes.
  • Poll_Delay– The frequency at which the controller will poll the network in milliseconds.  Normally this value is set to 1500. It is not recommended to modify this value; if this value is modified, communication issues may be reported.
  • Password– SCP password –  set only when the controller has dip switch 8 to the ON position.
  • Card_Format– A card format is a set of values programmed in the controller to accept certain bit or data structures and facility codes. Up to eight (8) card formats can be added per SCP / EPC controller.  To add a card format, click on the drop down arrow to the right of the Card_Format tag.  Eight (8) tabs will be displayed allowing the operator to configure one (1) card format per tab. Highlight the first available tab and click on the credential icon.  This icon appears as a book with a magnifying glass and allows the operator to copy a card format from an existing library.  After clicking on the Copy Card Format icon select the card type: Wiegand or Magnetic.  By clicking on the card type, a library of card formats will be displayed.  Click on the format that matches the cards purchased.  Once the format has been selected, the operator can make changes to any of the format fields to customize the format for the customers use.  For example, if using a 37-bit format with a facility code of 19, the operator would modify the 37-bit format’s facility code to reflect 19.  Click the floppy disc to save the changes.
  • IP_Address– Host name or IP address for the Serial to Ethernet converter.  The IP address field will automatically be populated if the controller was added using the Auto-Setup feature.  To modify the IP address the software sees, type the IP value in the text box to the right of the IP_Address tag.
  • Network Configuration– Click on the drop down arrow to the right of the (Network Configuration) tag to be taken directly to the controller’s configuration page.  This page allows the operator to configure the hardware with values such as IP address and passwords.
  • Max_Cards– The maximum amount of cards allowed for this controller.  This value will vary depending on the controller type and controller memory available.  To modify this value, click on the drop down arrow to the right of the Max_Cards tag.
  • Max_Time_Schedules– The maximum amount of Time Schedules for this controller.  This number is defaulted to a hard limit of 100 Time Schedules per controller.
  • Max_Events– The maximum amount of events that can be stored in the controller.  By default, this value is set to 5000.  This number will change depending on the controller type and controller memory available.  To change the Max_Events, click on the drop down arrow to the right of the Max_Events tag.
  • Max_Pin_Digits– This value allows the user to set the maximum amount of pin digits for the controller.  This number must be between 0-15. If nothing is displayed in the property field, the default of eight (8) digits will be assigned. To assign a Max_Pin_Digit amount, click on the drop down arrow to the right of the Max_Pin_Digits tag and select numeric value required.
  • Daylight_Savings– This property will enable / disable the observance of daylight savings in the controller’s internal clock.  To modify the Daylight_Savings property, click on the drop down arrow to the right of the Daylight_Savings tag and select the Daylight_Savings option the controller should follow.
  • GMT_Offset– Allows the controller to operate in different time zones from the server.  To configure the GMT_Offset, click on the drop down arrow to the right of the GMT_Offset tag and select correct GMT_Offset for the controller’s location.
  • Auto_Disconnect_Time– This property allows the controller to automatically disconnect after a period of inactivity.  This option is used for dial-up installations.
  • Offline Time– This property allows you to set the time in seconds (0 – 65) that the driver will NOT report a controller as going offline. This feature is beneficial for sensitive networks.
  • Model– The Model will be within the EPC based series (e.g. EPC-1, SCP2, SCP-Extended or SCP-Compact).  The proper model type is based on the controller used at your site. If the Auto-Setup feature is used, the Model property will be automatically populated.  To select the Model type, click on the drop down arrow to the right of the Model tag and select the Model type for the installed controller.
  • Occupancy Control– This property allows the operator to control how many card holders may be in an area at one time.  This property can be configured for a maximum and minimum number of occupants.  Please see help section Occupancy Control for configuration options.
  • 128 Bit Encryption– Enable or disable 128 Bit Encryption between the host and the controller.  If this option will be used, special firmware must be flashed into the controller.  To select 128 Bit Encryption, click in the check box field to the right of the (128 Bit Encryption) tag.  Please note the controller must be reset each time encryption is enabled or disabled.
  • Biometric Configuration– Opens the Biometric Configuration window which allows for more specific Biometric configuration.  This option is generally used for legacy Mercury Biometric readers.
  • Card Bits – This field specifies the card bit format. Select the card bits consistent with the card format that you are using at your site.
  • Restore to Last Known State on Re-Connect – This restores the controller to the previous state in the event the controller goes offline (i.e. such as a power failure).
  • Dialect – This toggles between Mercury and Honeywell platforms.