NXT-MSC Controller - Controller Setup Guide

NXT-MSC Controller - Controller Setup Guide

1.0 Introduction

MSC Controller

This document covers the basic setup of an NXT Mercury Powered (NXT-MSC) controller in Doors.NET or Borealis. It assumes your Doors.NET or Borealis system has already been setup.

 

Important Notes:

  • A Doors.NET system should be licensed and the MSC gateway should be setup and online.
  • A Borealis system should be setup and a hub should already be added and configured for Keri MSC or Mercury controllers.
  • Once the NXT-MSC controller has been added to Borealis it will not be functional until the cloud subscription for the readers has been purchased.
  • The new black-coloured PCB also has a QR code this can be used to add the controller to Borealis using the Borealis Connect app (covered in section 4.0).


Before adding the MSC controller, you should make a note of the controller's MAC address. The MAC address can be found on the white sticker in the lower left corner of the controller (near to the Ethernet port). The MAC address begins 00-14-34.

 

MSC Controller MAC Address


2.0 Important Note:  
Keri Public Statement on the Amazon Key 


3.0 Adding the NXT-MSC Controller to Doors.NET

3.1 DHCP Address Assignment

When the NXT-MSC controller is powered-up and connected to the local area network (or
directly to your host PC via a patch cable). It will initially try and obtain a DHCP IP address.
If no DHCP address is assigned to the controller (i.e. if DHCP is not enabled on the network), then the controller will automatically set itself to a static IP address that begins 169.254. To import the controller using its default static IP address you would need to configure the host PC with an IP address in the same range as 169.254.x.x. You would then import the controller, set the controller to its required IP address and then set the host PC back to its original IP setting.

 

  1. Ensure the controller is powered-on and connected to the network.
  2. Near the lower-left corner of the controller PCB there are 2 network LEDs.
    When the controller is connected to a network, LED D21 should be quickly flashing green, D22 should be solid red.

       MSC Status LEDs

  3. Open the Doors.NET login window by clicking the client icon on the desktop.

    Client Icon

  4. Login using the default username and password of admin/admin.
  5. Once logged in, go to Setup >> Hardware Setup then the All tab.

    MSC Setup - All

  6. You will see the MSC gateway at the top of the hardware tree.
  7. Right-click the gateway and select Scan or click the scan icon on the hardware ribbon bar.

    Scan Icon

  8. There is a utility built into the MSC gateway that will scan for all MSC
    controllers.
  9. As long as the host PC has an IP address in the same range as the controller's DHCP address, the MSC controller should appear almost immediately.
  10. If there are multiple controllers look for the MAC address that matches the one you have noted down.


    MSC controller detected


3.2 Importing the Controller

  1. Select the controller from the list.
  2. Click the IMPORT button.



  3. Click Yes to confirm you wish to go ahead with importing the controller.
  4. The controller will be added to the system and will appear on the hardware tree.
  5. Click OK to complete the controller import.

 

3.3 Configure the Controller with a Static IP Address

Because the controller has been added to Doors.NET with a DHCP address it is now highly recommended that you configure the controller with a static IP address.

 

Note: Before assigning the controller with a static IP address you should ensure that the IP address is available and not already assigned to a different device on the network. This can be done by opening a command prompt on the host PC and then pinging the IP address that you wish to assign the controller. If you do not get a reply from the entered IP address then you will be able to assign it to the controller.

 

Doors.NET has a feature that allows you to program the controller's internal configuration (including the assigned IP address) and this feature is accessed via Design Mode.

 

  1. From Doors.NET, click the Design Mode icon in the upper-left corner of the admin client.



  2. The client title bar will indicate that Design Mode is enabled.



  3. Return to the hardware tree (Setup >> Hardware Setup >> All) if it is not already open.
  4. Right-click the new controller and select Internal Controller Configuration.

    Internal Configuration

  5. From the Web Page selection drop-down list, select Network.



  6. Click the refresh icon.



  7. The controller's programmed network settings will appear on the right side of the window.
  8. You will see that the controller is set to DHCP and the assigned DHCP address is also displayed.

    DHCP Address Assigned

  9. Change the Network Method to Static.
  10. Enter the Static IP address that you wish to assign to the controller.



  11. Click the blue save  icon located above the controller network properties to save the network settings.
  12. Click the APPLY and REBOOT button which will have appeared.



  13. Click YES to proceed.
  14. The static IP address will be assigned to the controller. The controller will reboot and within a few seconds will come back online in Doors.NET with the new static IP address.
  15. You can now close down the controller internal configuration window.

 

3.4 Update the Controller Firmware

A brand new controller will not require a firmware update but you may need to update the
firmware on an older controller.

 

If a controller does need a firmware upgrade you will see the following message in live events:

 

 

  1. Go to the Doors.NET hardware setup screen.
  2. Press the <F1> key on the keyboard.
  3. The built-in help file will be initialized.
  4. Select English as the language. Then OK.
  5. The help file will open up on the Controllers page.
  6. From the table of contents on the left, expand Hardware Setup.
  7. Expand Firmware Upgrading.
  8. Click on Controller Firmware Upgrading.
  9. Scroll down to the NXT-MSC controllers and you will see the instructions for upgrading the controller firmware.

 

 

4.0 Adding the NXT-MSC Controller to Borealis

The following steps explain how to add an NXT-MSC controller to Borealis. It assumes that you have already followed the steps to add an NXT-MSC site to your system. During the steps to claim the hub you will select the site that the hub will be associated with.

 

dhcp notification

 

  1. From the main menu, click on Hubs.



  2. Your hub will appear in the list.

  3. Click the Actions drop-down menu on the right and select Scan. Or click the SCAN button.



  4. The scan function will scan the local network for controllers.

  5. After a few seconds, controllers will appear in the list.
  6. IMPORTANT NOTE: When adding NXT-MSC controllers they will be assigned with a DHCP IP address.

  7. Place a check mark against the controllers that you wish to claim.
  8. Enter a name for each of the controllers that you wish to add.



  9. Click the CLAIM button.



  10. At the top of the screen you should see a message stating that the controller(s) has been successfully claimed.

  11. The controller can be viewed via Hardware >> Controllers. Within a few seconds the controller should be online.

 

5.0 Adding a Controller Using the Borealis Connect App

Borealis also has an app that allows you to easily add a controller to your system using the QR code printed on the lower right corner of the controller.

 

 

  1. Download the app to your Android or iOS device (scan the following QR code or search for Borealis Connect).
  2. When you open the app, you will be prompted to login to your Borealis system.
  3. Enter your registered Borealis e-mail address and password. Then click SIGN IN.
  4. Select your system.
  5. Next, click the ‘QR enroll’ button.

    QR Enroll

  6. Scan the QR code on your NXT-MSC controller.
  7. A controller import form will appear.



  8. Enter a name for the new controller.
  9. Leave the IP address field blank (as a DHCP address will automatically be assigned to an NXT-MSC controller).
  10. The controller's unique MAC address will be displayed.
  11. Beneath the MAC address, is the specific controller type.
  12. Tap the target hub name field, and select your Borealis hub.
  13. Click the ADD button.
  14. You will see a message stating the controller has been successfully added.
  15. You can now log into Borealis via a web browser (either from your smart device or a PC).
  16. Within a short period of time, the controller will be online. If the controller does not come online within a few seconds click the SCAN button on the Hub screen. Once the scan is complete the controller will be online.

 

6.0 Update the Controller Firmware

The following steps explain how to update the firmware on an NXT-MSC controller in Borealis. If a controller requires a firmware upgrade you will see a firmware update required event in live events.

 

             

 

  1. From the main menu, click on Hardware>> Controllers.
  2. On the right side of the screen use the controller's Actions menu and select Flash.
  3. Select the latest firmware file from the drop-down list (for example, v1.296).
  4. Click the SAVE button.
  5. The new firmware will now be sent to the controller.
  6. During the upgrade the controller will go offline for a few seconds.
  7. The firmware upgrade will be completed within a couple of minutes.
  8. The new firmware version will then be displayed on the right side of the Controllers screen.

    New Firmware Displayed

 

7.0 Modifying the RTE Input Setting

If you are not using Request-to-Exit (RTE) inputs you will notice that the lock relays will activate when the controller has a memory reset. The reason is because by default, the RTE inputs are set to Normally-Closed. When the controller does a Power-On-Self-Test it checks the status of the inputs and if the circuits are open then the RTE function will activate. To prevent this from happening you should do the following on each reader:

 

  1. Expand the controller and then the controllers bus.
  2. Highlight one of the controller's readers.
  3. In the reader properties located on the right, locate the REX 1 Properties.
  4. In the Circuit Type field change the setting from Unsupervised, Normally-Closed to Unsupervised, Normally-Open.
  5. Then save the reader properties.



  6. The next time the controller has a memory reset the lock relays will remain inactive.

 

8.0 Factory Reset Procedure

  1. Ensure the J3 jumper is across both pins.
  2. Press the white S1 button - the D MODE LED will go solid green.

    Reset LEDs

  3. While the D MODE LED is still green, down power the controller.
  4. Press and hold the white S1 button and apply the power.
  5. The following LEDs will be flashing in an alternating sequence (Reset + ULED2 + ULED4) then DMODE + ULED4.
  6. Continue to hold down the S1 button for approximately 20 seconds.
  7. Release the S1 button and the all LEDs will initially go off.
  8. You will see various LEDs go on and off for a few seconds then only the Reset LED will be flashing on and off.
  9. The controller's ram is now reset. The 4 green LEDs to the right of the J3 jumper should also now be on.
  10. The controller will either be set to a DHCP address or it will automatically be set to a static address in the range of 169.254.99.X if it does not receive a DHCP address within 1 minute.

 

 

9.0 Further Setup and User Information

9.1 Doors.NET Help File

Once the controller is added to the Doors.NET software you are ready to start configuring other aspects of the system, such as; setting up access groups and time schedules and adding cardholders. All these topics and more are covered in the comprehensive help file which is included with Doors.NET.

The quickest and easiest way to access the help file is to press the F1 key while on any of these screens. If you are on the cardholders screen for example (Home >> Cardholders) then press F1, the help file will automatically open up on the Cardholders section.


 

9.2 Guided Support

Keri Systems has a Guided Support platform that intuitively guides you to appropriate setup information for Doors.NET, Borealis and hardware setup of all controller and reader types. Guided Support also has useful sections troubleshooting:

 

Guided Support URL: https://kerisys.com/guided-support

 

 

9.3 Knowledge Base

There is also the knowledge base which has setup and installation guides as well as data sheets, product specifications, training videos and application notes.

 

Knowledge Base URL: help.kerisys.com

 

 

Note: Guided Support and the Knowledge Base can also be quickly access from the Borealis client via the question-mark icon located in the lower-right corner.





    
P/N:01238-003 Rev D
   


    • Related Articles

    • NXT-MSC Controller - Setup an Airlock/Mantrap

      1.0 Introduction The airlock features is available on NXT-MSC or Mercury SCP controllers when Area Control is enabled on the license. This is so that you can set up two or more areas as 'airlock' areas. Anti-passback is not required for airlocks to ...
    • How do I Setup an NXT-MSC Controller?

      How do I setup an NXT-MSC 2-door or 4-door controller in the Doors.NET software? An NXT Mercury-powered (NXT-MSC) controller is added to Doors.NET via an Ethernet connection and there are two options; either the controller obtains its IP address ...
    • NXT-MSC - Controller Internal Configuration

      Effective from Doors.NET v4.0.3 it is now possible to make various controller configuration changes within Doors.NET rather than via a web browser. This section explains how to access the controller internal configuration and which configuration ...
    • NXT-MSC 2D/4D Controller Hardware Installation Guide

      1.0 Introduction This document contains basic information for the installation of the NXT-MSC 2D and 4D controllers. The NXT-MSC controller has recently been updated from a green PCB to a black colored PCB. All NXT controllers and Keri peripherals ...
    • NXT-MSC Controller - Setup Anti-Passback

      The Anti Passback (APB) feature provides one-way card access into and out of a secure area. It prevents a cardholder from using their card and then passing that card back to someone in order for them to gain unauthorized access. Local APB is ...