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:

 

 

 

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.

3.0 Feature Summary

Once you are licensed to support non-Keri Mercury hardware:

1) There will be no incompatibility messages when logging into the software or requesting controller status.
2) You can import Mercury controllers with any OEM code.
3) You can upgrade the OEM code on the controller. This is not required, but enabling it applies Keri branding to the web configuration UI and Keri default settings on a factory reset controller (uses Keri's OEM profile).



Note: You cannot update the OEM codes of downstream modules (i.e MR16IN, MR16OUT and MR52).

4) Downstream devices configured with other OEM codes will be allowed.