Using Non-Keri Mercury Hardware

Using Non-Keri Mercury Hardware

1.0 Introduction

From Doors.NET v6.0.0 and onwards you will not be able to communicate to Mercury SPM or downstream modules that have non-Keri OEMs. To use non-Keri Mercury hardware this option must be enabled in your Doors.NET license. Non-Keri Mercury hardware are Mercury SPMs and downstream modules which are provided by other security system manufacturers.

 

The following notification will appear if you attempt to import a non-Keri Mercury controller and the license does not have Non-Keri Mercury hardware enabled:

 

OEM code notification

 

 

2.0 Enable Non-Keri Mercury Hardware

  1. Open the Doors.NET License Manager (type 'License Manager' into the Windows search field).
  2. When the License Manager opens, click on the License tab.
  3. Scroll down to the Supported Hardware section.
  4. You will see that Allow non-Keri Mercury Security Hardware is set to False.

    Non_Keri_Mercury_Setting

  5. At the bottom of the license capacities and settings you will see your unique Doors.NET license key.
  6. Contact Keri Systems inside sales and quote the first 5 characters of your license key.
  7. Keri sales will process your request to have this option enabled.
  8. Once enabled, return to the License Manager, select the Application Server listed on the left side of the screen, then click the ACTIVATE button.
  9. The License Manager will communicate with the license server and the license will be updated.
  10. You will see a confirmation that the license has been re-registered.
  11. Existing non-Keri Mercury SPMs and downstream modules will now be online in Doors.NET.

    • Related Articles

    • Doors.NET - Using Multiple Hardware Platforms

      Doors.NET - Using Multiple Hardware Platforms (PDF) P/N: 01268-001 Rev. C (attached)

    • Using Multiple Hardware Types in Doors.NET

      Doors.NET is capable of running multiple concurrent hardware platforms. The ability to support multiple concurrent hardware platforms was introduced in Doors.NET v3.5.1.19. Support for the Entraguard, the PXL-G and the PXL-LC was introduced in ...

    • Setup a Hardware Gateway Using the Gateway Wizard

      Effective from version 3.5.1.21 of Doors.NET a gateway is typically setup using the License Manager. However, there are situations where the hardware gateway needs to be installed on a remote workstation. The Gateway Wizard allows you to add a remote ...

    • Using 26-Bit Wiegand Format on Different Hardware Types

      1.0 Introduction When using NXT or NXT-MSC controllers, the 26-bit card data is processed using the same 26-bit Wiegand format (which is added to the Doors.NET system, by default).  If you have Credential Types enabled on your Doors.NET system, the ...

    • Mercury EP Controllers Overview

      Introduction In addition to our own Mercury Powered NXT controllers (NXT-MSC), Keri also offers non-proprietary authentic Mercury Security hardware, which is supported by Doors.NET Professional Edition software. The hardware platform consists of the ...