Configuring Mercury controller settings in Synergis™ Appliance Portal - Synergis™ Softwire 11.1

You can configure the settings for your Mercury controllers in Synergis™ Appliance Portal.

1. Log on to the Synergis™ unit.
2. Click Configuration > Mercury controller settings.
   
3. Expand the PIN settings section, and configure the following settings:

   Add leading zeros for PINs

   To define the number of zeros to be added before PINs, select Custom, and enter a value for Leading zeros. For example, the maximum PIN length is 4 digits long, and you enter 3 as the Leading zeros value. If your original PIN was 9, the PIN becomes 0009. If your original PIN was 123, the PIN becomes 0123.

   You must perform a software restart if you change this setting.

   For more information, see Configuring PINs with leading zeros for Mercury integrations.

4. Expand the Door settings section, and enable the following settings as required:

   Single held open mode

   Ignore subsequent Door open too long events after the first event is generated, as long as the door remains open.

   You must perform a software restart if you change this setting.

   Raise card read events with the source event timestamp

   The timestamp from the Synergis™ Cloud Link is used instead of the timestamp from the Mercury controller.

   You must perform a software restart if you change this setting.

   Hide unlock events when 'Unlock on REX' is off

   The Mercury controller sends unlock events on REX activations regardless of whether or not it actually unlocks the door. Enable this option to hide these unlock events. Enabling this setting causes a delay on all events received so that false unlock events can be filtered out.

   You must perform a software restart if you change this setting.

   Host decision handoff (offline mode)

   Mercury controllers make their own decisions as though they are disconnected from the Synergis™ Cloud Link. When the setting is enabled, some advanced features and cards that are not yet synchronized to the Mercury controller do not work, however, the door becomes much more responsive if there is lag or a bad network connection between the Synergis™ Cloud Link and Mercury controllers.

   Silent access granted

   Readers do not beep when access is granted.

   Silent access denied

   Readers do not beep when access is denied.

   Inhibit Door forced open event

   Door forced open events are disabled.

   You must perform a software restart if you change this setting.

   Reader LED off when locked

   Reader LEDs on OSDP readers are turned off if the associated door is in a normal lock state.

   Mercury native area control

   Enables Mercury's native antipassback, max occupancy, and interlock features on the Mercury panel.

   You must perform a software restart if you change this setting.

   Extended grant time REX mode

   Doors remain unlocked for as long as the REX input is active and for the normal grant time afterward. If no door sensor is present, the door remains unlocked either for as long as the REX input is active or for the normal grant time, whichever period is longer.

   This is useful for preventing doors that are controlled by a motion sensor from locking and unlocking every few seconds. This feature requires Mercury firmware 1.29.1 or later.

   You must perform a software restart if you change this setting.

   NOTE: You can also configure this setting on a per door basis.

   Program door alarm LED procedures

   Causes the readers associated with Mercury controllers to follow Synergis™ Softwire LED and buzzer patterns instead of Mercury LED and buzzer patterns for door alarms.

   NOTE: If this option is disabled, when Door forced open and Door open too long events are generated, the LEDs on the associated readers do not flash.

   You must perform a software restart and then reset the Mercury controllers if you change this setting.

5. Expand the Card conversions section, and enable the following card conversions as required:
   You must perform a software restart if you change any of these settings.
   • Casi M5 56 -> 40
   • Ambiguous HID 1441 -> 56

   Lossy conversion for credentials longer than 52 bits

   Fixes a bug in versions of Synergis™ Softwire earlier than 10.10, where credentials from 52 to 64 bits might have issues.

   200 bits FASC-N to 128 bits

   All cards report the 128 bit version. This setting is used in conjunction with FICAM or Long credential database layouts.

   Add F2F to Wiegand translator

   Add or configure other translators.

6. Expand the Long credential formats section, and configure the following setting:

   Wiegand format length (bits)

   Long credential formats for Mercury units are not automatically configured in Security Center. You must manually set the format by entering a value from 64 to 240, and then clicking Add. This setting is used in conjunction with FICAM or Long credential database layouts.

   You must perform a software restart if you change this setting.

7. Expand the Advanced settings section, and enable the following settings as required:
   You must perform a software restart if you change any of these settings.

   SIO Encryption Control

   Enables encryption on the RS-485 between EP or Honeywell controllers and their downstream SIO boards, or LP controllers and older SIO boards. LP controllers with S3 SIO boards use encryption on the channel regardless of this setting.

   No ACR without door

   Readers are not pre-configured as SIO units are added, and I/O diagnostics do not report card reads from unassociated readers. This settings removes issues where more than 64 reader ports are enrolled under a Mercury controller or cases where readerless doors are being used that also go over the 64 limit.

8. Expand the Auxiliary authentication module section, and select Disabled, PivClass, or TIENtryPoint.
   This setting is used in conjunction with FICAM database layout and the appropriate plugin for the LP4502 controller.
9. Expand the Mercury SCP logging section, click Start logging for additional Mercury-specific logging, and enter the number of days after which you want the logging to end.
10. Expand the Buses section, and click Reset for each controller or Reset all to ensure new settings are pushed to all the controllers.
11. Expand the Database layout settings section, and configure the following settings:
    1. Select a database layout from the list.
       The Feature rich (default) layout fits most use cases. The other database layouts address specific needs. You must reset the controllers after changing the database layout.

       For more information about what each database layout supports, see Database layouts for Mercury controllers.

    2. Enter the Maximum PIN length.
       The default value for all database layouts is 6. Lowering this value is commonly used to eliminate having to press the # key at the end of four-digit PINs when only four-digit PINs are used in the system.

       NOTE: Setting the Maximum PIN length to a number higher than what is supported by the selected database layout causes your Mercury controllers to stop functioning, and PINs longer than the configured Maximum PIN length do not work.
       You must perform a software restart if you change this setting.
12. Expand the OSDP-reader-specific settings section, and configure the following settings:

    Nexus and Veridt OSDP LED correction

    Fixes an LED issue that occurs in certain Nexus and Veridt OSDP readers.

13. Click Reset to default to reset all settings to default, except for the database layout settings.
    NOTE: There is no way to recover the previous settings.
14. Click Save.