1.0 Introduction

With Doors.NET v4.9.0 and later, you can connect Mercury MR16IN and MR16OUT modules to the RS-485 port of an NXT-MSC controller. Each MR16IN or MR16OUT module has 16 inputs or 16 outputs and therefore offers a very cost-effective elevator control solution.

Notes:

• If you are using an MR16IN or an MR16OUT on a bus you won't be able to use any other RS-485 device on that bus (such as an NXT reader or an NXT RIM or 4x4 module).
• Effective from Doors.NET v5.2.0 there is a change to the setup of MR16 modules on the controller bus. This change requires the Mercury protocol to first be enable on the bus before adding the module.

• Each bus can support up to 19 panels (either MR16IN or MR16OUT) with a maximum of 31 panels per controller. 

• You must have a Doors.NET Professional license to see the options to add the MR16IN or MR16OUT to NXT-MSC.

• The Elevator Control reader, that is located on Bus1...can be RIM, NXT or OSDP.  Nothing else is allowed on Bus1... You cannot actually add the modules to bus 1 because the MR16 icons are grayed-out when the controller is configured for elevator control.
• For Elevator Control, add the MR16IN or MR16OUT module after you have configured the controller as an elevator controller.
• By default, the relays on the controller are assigned for elevator control, but these can be unassigned as used a general control point relays.

• It is possible to use a combination of NXT-4x4 modules and MR16 modules connected to the same controller. The only thing to remember is that an NXT 4x4 and an MR16 module cannot co-exist on the same controller bus as they communicate using a different RS-485 protocol.

2.0 NXT-MSC Controller to MR16IN/MR16OUT Wiring

2.1 Wiring at the NXT-MSC Controller

Notes:

• You should not power the MR16IN or MR16OUT module from the controller's bus. The MR16IN or MR16OUT module should have its own dedicated power supply.
• You should connect the RS-485 shield drain to the earth-ground at the NXT-MSC controller only (to prevent ground loops).

2.2 RS-485 Wiring at the TB10 connector of the MR16IN/MR16OUT

2.3 RS-485 Wiring Specifications

• The recommended cable type for the RS-485 connection (between the NXT-MSC controller and the downstream MR16 modules) is Belden 9501 (or equivalent) - this is a 1-pair shielded, stranded, twisted cable. AWG 24 wire or larger (note that increasing the wire gauge does not increase the total network length) - The total network length is 4,000 feet/1,000 meters.
  
  
• The RS-485 wiring between MR16 modules is a daisy-chain connection.

3.0 Set the MR16IN/MR16OUT RS-485 Address

The address is determined by which bus the module is added to and how many modules already exist on that bus.

Note: The required address number will be displayed in the module properties when it is added to Doors.NET.

Use the S1 DIP switch to configure the controller's RS-485 address. For example: if you add the first MR16OUT module to bus 2, the required address will be #2.

4.0 Set the MR16IN/MR16OUT RS-485 BAUD Rate

The BAUD rate for the MR16 module should be set to 38,400.

5.0 Elevator Control - With Floor Select

The With Floor Select Elevator Control option uses a combination of MR16IN and MR16OUT modules. With Floor Select option is used when you need the software to report the floor that was selected by the cardholder. This is a different behavior than the default option of Elevator - No Floor Select (which simply provides floor access as appropriate) following a valid card read and does not record which floor selection button is pressed.

6.0 Elevator Control - No Floor Select

No Floor Select system behavior is when someone presents a card, the floor buttons in the elevator cab will typically illuminate for the floors to which the cardholder has access to. So if a cardholder has total access, all outputs on the MR16OUT will change state, which will allow any of the floor select buttons to be pressed in the cab (to access any of the floors). When using No Floor Select the system only requires the use of MR16OUT modules.

7.0 Verify the Doors.NET License

Ensure that the Doors.NET license is configured with Elevator Control enabled. To check this, click on Start > All Programs > Doors.Net > License Manager. If it states False instead of True then you need to contact Keri Systems Inside Sales to purchase this feature.

8.0 Controller Configuration

Controller Configuration Warning

Note: Once a controller has been configured for elevator control, it cannot be simply reconfigured back to a standard controller.

You must perform the following steps:

• de-select the elevator facility setting from the controller
• delete the controller from the database
• RAM reset the controller
• scan the system to rediscover the controller
• add it back to the database

Please be sure you have selected the correct controller to use before configuring it for elevator control.

1. Log into your Doors.NET client.

2. Go to the Setup >> Hardware Setup >> All tab. The hardware tree displays the hardware gateway and controllers. The image below shows one NXT-MSC 4-door controller is added.

3. At the bottom of the hardware tree is a node labeled ‘Facilities.’ A Facility needs to be defined and this is where you specify how many floors will be controlled. Generally a facility, in the physical sense, is an elevator shaft.

4. Click on Facilities and then click the Add Facility button on the ribbon bar.

5. Change the description to something appropriate to your site.

6. The new facility defaults to having 2 floors. Change this count by overwriting it with the number of floors desired, in this case 32. The ‘Floor List’ automatically adjusts accordingly. At this time you may also name each of the floors by clicking on the drop-down arrow then double-clicking any of the floor names listed.
   
   
   
   

7. Next step is to configure the controller. Advanced View must be enabled to see all the relevant sections. Click on the desired controller in the hardware tree and view its properties.

8. In the General settings, change the controller function from Normal to Elevator. A confirmation message box appears. Click Yes.

9. Save the controller settings then click YES on the prompt to reset the controller.
   
   
   
   
10. Further down the properties list is the Elevator Control settings. Select the facility you wish to assign to the controller.
    
    
    
    
11. Now assign the Floor Map; selecting which floors this controller will be servicing.
    
    
    
    
12. Save the controller settings. The Floor Count is automatically set according to the information in the Floor Map. The software generates an alert stating the controller needs to be reset. Click Yes to allow the reset.
13. The controller now shows the reader on bus 1 is designated as the elevator reader, the other readers on the controller are removed from the hardware tree. The output relays for each of the buses are changed from Strike Outputs to Elevator Outputs and all are associated with the elevator reader.
    
14. With the Elevator Reader on bus 1 highlighted. Reference the reader properties and look for the Primary/Secondary (In/Out) settings. Set the reader to 'Elevator, No Floor Select' or 'Elevator, With Floor Select' per your application.

9.0 Add an MR16IN Module (with Floor Select)

This section assumes you already have an NXT-MSC controller setup and online.

1. Double-click the controller that the MR16IN will be added to.
2. Select the bus that the MR16IN is wired to.
3. In the bus properties (on the right), locate the Protocol setting.
4. Change the Protocol (Serial) from Keri Systems to Mercury Security.
5. Set the baud rate to match the baud rate that is configured on the controller's S1 dip switch.
   
   
   
   
6. Click the MR16IN-S3 icon in the hardware select ribbon bar.
   
   
   
   
7. The module will appear on the hardware tree.
8. Confirm the prompt to reset the controller.
   
9. Select the module and the properties will be displayed on the right.
10. Verify that the module is showing as online.
11. In the properties, locate the Comm address field. This is the address that needs to be set to the module using the S1 switch. By default, effective from Doors.NET v5.2.0 the address will be 0.
    
    
    

Note: When using 'With Floor Select' when the cardholder presents their card in to cab reader and then presses the floor select button, you will see in live events which floor the cardholder has gone to. No Floor select does not record in Doors.NET which floor has been selected.

10.0 Add an MR16OUT Module

1. Double-click the controller that the MR16OUT will be added to.
2. Select the bus that the MR16OUT is wired to.
3. In the bus properties (on the right), locate the Protocol setting.
4. Change the Protocol (Serial) from Keri Systems to Mercury Security.
5. Set the baud rate to match the baud rate that is configured on the controller's S1 dip switch.
6. Click the MR16OUT-S3 icon in the hardware select ribbon bar.
   
   
   
   
7. The module will appear on the hardware tree.
8. Confirm the prompt to reset the controller.
   
   
9. Select the module and the properties will be displayed on the right.
10. Verify that the module is showing as online.
11. In the properties, locate the Comm address field. This is the address that needs to be set to the module using the S1 switch. By default, effective from Doors.NET v5.2.0 the address will be 0.
    
    
    
    

If you select any of the outputs you will see in the output properties that the output is configured as an Elevator Control output (because you have already configured the controller for Elevator Control).

If the address # is correct you should then see online events appear in live events.

11.0 Test a Temp Unlock on All Floors

Perform a Temp Unlock (All Floors) and verify the controller configuration. When this command is performed all relays should activate for the strike time that the reader is set to.

1. In the hardware tree, right-click the elevator control reader.
2. Select Temp Unlock.
3. All Floors will be selected, by default.
4. Click the UNLOCK button and all relays will be temporarily activated. This confirms your controller has been successfully configured for Elevator Control.