You can configure the settings for your Mercury controllers in the Synergis™ Appliance Portal.
What you should know
Procedure
- Log on to the Synergis unit.
-
Click Configuration > Mercury controller settings.
-
Click the PIN settings tab from the side menu, 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 four 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.
Perform a software restart if you change this setting.
For more information, see Configuring PINs with leading zeros for Mercury integrations.
-
Click the Door settings tab from the side menu, 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.
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.
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.
Perform a software restart if you change this setting.
- Disable host decision handoff (offline mode)
- By default, this setting is disabled, meaning that Mercury host decision handoff is enabled, and that the Synergis Cloud Link unit makes the access control decisions.
- When this setting is enabled, Mercury host decision handoff is disabled,
meaning that the Mercury controllers make their own decisions as though they
are disconnected from the Synergis Cloud Link unit. In this case, some
advanced features and cards that are not yet synchronized to the Mercury
controller do not work, however, the door becomes much more responsive.Best Practice: Leave the Disable host decision handoff (offline mode) setting disabled, unless there is a bad network connection between the Synergis Cloud Link and the 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.
Perform a software restart if you change this setting.
- Inhibit 'Motor Fault' events from Schlage locks
-
Motor Fault events from Schlage locks are disabled.NOTE: This option does not affect Motor Fault events from other devices.
Perform a software restart if you change this setting.
- Inhibit 'RF loss' events from Schlage locks
-
RF loss events from Schlage locks are disabled.NOTE: This option does not affect RF loss events from other devices.
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.
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.
NOTE: You can also configure this setting on a per door basis. - Live 'Request to exit' events
- Changes the way that Synergis™ Softwire processes Request to exit
events from Mercury LP controllers, so that the timestamps on the events are
accurately reported.NOTE: This option is off by default.
Perform a software restart and then reset the Mercury controllers if you change this setting.
- 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.
Perform a software restart and then reset the Mercury controllers if you change this setting.
-
Click the Card conversions tab from the side menu, and
enable the following card conversions as required:
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 bits to 64 bits might have issues.
- 200 bits FASC-N to 128 bits
- All cards report the 128-bit version. This setting is used with FICAM or Long credential database layouts.
- Add F2F to Wiegand translator
- Add or configure other translators.
-
Click the Long credential formats tab from the side menu,
and configure the following setting:
- Wiegand format length (bits)
- Long credential formats for Mercury units are not automatically configured
in Security Center. Manually set the format by entering a value from 64 to
240, and then clicking Add. This setting is used with
FICAM or Long credential database
layouts.
Perform a software restart if you change this setting.
-
Click the Advanced settings tab from the side menu, and
enable the following settings as required:
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.Best Practice:
- Limit bulk upgrades to 10 SIO boards under a single EP controller.
- Before upgrading multiple SIO boards, disable the SIO Encryption Control option.
- 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 setting removes issues where more than 64 reader ports are enrolled under a Mercury controller or cases where readerless doors are being used and also go over the 64 limit.
- Two OSDP readers per reader port
- Enables LP1502, LP4502, MR50-S3, and MR52-S3 units to support two OSDP readers per port. This requires a minimum of Synergis Softwire 11.3.1 and Security Center 5.10.4.0.
-
Click the Over-Watch settings tab from the side menu, and
select the LP4502 Over-Watch plugin setting to enable the
Over-Watch plugin on all the LP4502 controllers under the Synergis Cloud Link unit.
The Over-Watch plugin is only required for the BEST Wi-Q integration through
Mercury.
For more information, see Configuring the Over-Watch plugin for the BEST Wi-Q integration.
-
Click the Auxiliary authentication module tab from the side
menu, and select Disabled, PivClass, or
TIEntryPoint.
This setting is used with FICAM database layout and the appropriate plugin for the LP4502 controller.
- Click the Mercury SCP logging tab from the side menu, and click Start logging for additional Mercury-specific logging, and enter the number of days after which you want the logging to end.
- Click the Buses tab from the side menu, and click Reset for each controller or Reset all to ensure that new settings are pushed to all the controllers.
-
Click the Database layout settings tab from the side menu,
and configure the following settings:
-
Select a database layout from the list.
The Feature rich (default) layout fits most use cases. The other database layouts address specific needs. Reset the controllers after changing the database layout.
For more information about what each database layout supports, see Database layouts for Mercury controllers.
-
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 the selected database layout supports causes your Mercury controllers to stop functioning, and PINs longer than the configured Maximum PIN length do not work.Perform a software restart if you change this setting.
-
Select a database layout from the list.
-
Click the OSDP-reader-specific settings tab from the side
menu, and configure the following settings:
- Nexus and Veridt OSDP LED correction
- Fixes an LED issue that occurs in certain Nexus and Veridt OSDP readers.
- Override LED programming
- Fixes an issue on OSDP readers where the LED turns off for a few seconds when the door re-locks after being opened.
-
Click the Visitor
escort rule and two-person rule tab from the side menu, and configure
the following setting:
- Maximum delay between card presentations
- Applies to all the doors controlled by the Mercury controllers.
Perform a software restart and then reset the Mercury controllers if you change this setting.
-
Click the Door behavior for offline
SIO boards tab from the side menu, and select one of the
following:
This setting only applies to doors that have their reader and lock on the same Mercury SIO board. Readerless doors are not affected. When the setting is changed, the reader LED behavior does not follow door lock states.
- Default (locked)
- When the Mercury controller goes offline, the states of the doors it controls become locked, regardless of the state that the doors were in before the controller went offline.
- Unlocked
- When the Mercury controller goes offline, the doors it controls become unlocked, regardless of the state that the doors were in before the controller went offline.
- Locked
- When the Mercury controller goes offline, the doors it controls become locked, regardless of the state that the doors were in before the controller went offline.
-
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.
- Click Save.