1. Prerequisite

To use Suprema devices with Mercury boards in a Genetec Security Center (GSC), the Suprema device must be assigned as a Reader on a Door in the GSC configuration.

❗ Reasons

There are two key reasons for this requirement:

  1. No Support Server Authentication for biometric
    GSC and Mercury controller do not support biometrics. Therefore, users must be synchronized directly to the Suprema device to enable local biometric matching.

  2. AC Rule-Based User Synchronization
    The Suprema Plugin synchronizes users to devices based on Access rules. This synchronization logic only applies to devices that are mapped as readers on Doors. As a result, if the device is not linked to a Door as a reader, users can not be synchronized to devices.

⚠ Limitations Caused by This Design

This prerequisite introduces the following limitations:

  1. Two Logical Doors Required per Physical Door 

    • One for the Mercury board (decision-making)

    • One for the Suprema device (user synchronization)

  2. Duplicate Events in Security Desk and Reports
    When a user authenticates at the Suprema device, two events will be generated:

    • One from the Suprema device (biometric scan)

    • One from the Mercury board (access decision)
      Although the Suprema door can be excluded from real-time monitoring in Security Desk, both events will still appear in reports, potentially causing confusion or duplication in event log


2. Wiegand Configuration

Suprema devices can be configured to communicate with Mercury boards via Wiegand interface, which is commonly used for transmitting card or credential data. The Wiegand settings must be properly configured in the Suprema Device Plugin within Genetec Security Center.

? Configuration Location

Wiegand settings can be found under:

Suprema Device Plugin → Device → Device Settings → Advanced Tab

⚙ Required Settings

When integrating with Mercury controllers, the following parameters must be configured:

  • Wiegand Input/Output Mode

    • For communication from Suprema to Mercury, set it as Wiegand Output.

  • Wiegand Format
    Define the format of the Wiegand data. This must match the Wiegand format expected by the Mercury board (e.g., 26-bit, 34-bit, HID 37-bit custom, etc.).

  • Pulse Width & Pulse Interval
    These define the timing of the Wiegand signal:

    • Pulse Width: Duration of each data pulse (typical: 50–100 µs)

    • Pulse Interval: Time between pulses (typical: 1,000–2,000 µs)
      These values must be compatible with what the Mercury board is configured to accept.

✅ Additional Notes

  • Ensure the bit length and parity structure of the Wiegand output matches the Mercury input settings.

  • You may need to refer to the Mercury controller documentation to confirm supported formats.

  • If the Mercury controller doesn't recognize the signal, try adjusting pulse width/interval or checking the wiring polarity.


3. OSDP Configuration

Suprema devices also support communication with Mercury boards via OSDP (Open Supervised Device Protocol), which enables secure, bi-directional communication between readers and controllers. For proper OSDP integration, both Suprema device settings and Mercury panel settings must be aligned.

? Suprema Device Settings

OSDP settings can be configured from:

Suprema Device Plugin → Device → Device Settings → Network Tab

Configure the following parameters:

  • RS-485 Mode:
    Set to Standalone 

  • Baud Rate:
    Choose a supported value (typically 9600 or 115200) to match the Mercury board configuration.

  • OSDP ID:
    Assign a unique OSDP address (ID) to each device. This ID must match the reader address in the Mercury panel configuration.

⚙ Mercury Panel Settings

To add and configure an OSDP reader on a Mercury panel, follow these steps:

  1. Go to Access Control → Peripherals Tab in Security Center.

  2. Select the Mercury reader port where the Suprema device is connected.

  3. Under Type of Reader, choose OSDP 2.

  4. Set the Baud Rate to match the one configured on the Suprema device.


? LED Behavior Adjustment (Cloud Link Portal)

By default, Mercury panels may not properly control the LED indicators of third-party OSDP readers. To enable LED control for Suprema devices:

  1. Access the Cloud Link Portal for the Mercury panel.

  2. Navigate to:

    Advanced OSDP → LED Settings

  3. Upload the provided configuration file (attachment required).

    • This ensures proper LED feedback for access granted/denied events.

⚠ Optional: Transmitting Card Data on Authentication Failure

By default, Suprema devices send only an exception code for to the Mercury panel when authentication fails. If you want to send actual card data regardless of the authentication result (e.g., for logging or backup matching):

  • Apply the custom firmware CISF3118 to the Suprema device.

  • This firmware enables card data transmission even on failed authentication attempts.