1. Prerequisites

1.1 Custom Build

The general build of the Suprema Plugin is designed for standalone operation, prioritizing communication with the Cloud Link over OSDP/Wiegand communication
The typical authentication flow is as follows:

  1. The user authenticates at the device.

  2. The device sends user data to the Plugin.

  3. The Plugin forwards the user's credential(First, Active, and supported) to the Cloud Link.

  4. The Cloud Link verifies access rights for the credential and sends the result back to the Plugin.

  5. The Plugin returns the access result to the device, which then displays it (grant/deny).

A delay may occur at step #3 for the following reason:
If the device is not mapped to a Door, the Cloud Link will not generate an access decision result.
In this case, the OSDP sequence does not operate until the Plugin process times out and completes.

? Note: In Cloud Link–centric architectures, all access decisions are handled by the Cloud Link itself.
However, when using Suprema devices with a Mercury board, this behavior should be disabled, allowing the controller (Mercury) to perform access verification and decision instead.

1.2 Custom Firmware

When a Suprema device operates as an OSDP peripheral connected to a 3rd-party controller (such as a Mercury board), the standard firmware has the following limitations:

  • On Access Denied events, only an Exception Code is transmitted — card data is not included.
    → Use custom firmware if card data transmission is required.

  • User ID / Name display is not supported

1.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.

1.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.

    5.  LED Behavior Adjustment (Cloud Link Portal)

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

                            - Navigate to

                               Advanced OSDP → LED Settings

                            - 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.

2. Configuration Guideline

2.1 Access Rule Setup 

  • Create an Access Rule named SUPREMA_WHITELIST. 

    (Config Tool _ Access Control _ Access Rule)


  • Map All Cardholders to this Access Rule.

    (Config Tool _ Access Control _ Cardholders)

2.2 Cardholder synchronization

  • Needs to click Sync now button 

  • Suprema devices do not need to be mapped to Doors.

  • However, Cloud Link mapping is required.

? Result: All active cardholders will be synchronized to all Suprema devices,
ensuring consistent operation even when the access decision is made at the controller side.