1.0 Introduction

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

• Each bus can support up to 19 panels (either MR16IN or MR16OUT) with a maximum of 31 panels per controller.  Address 0 is reserved for the onboard 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.
  
• Once you have added an MR16INM or MR16OUT the reader for that bus will automatically be deleted.
  
• For Elevator Control, add the MR16IN or MR16OUT module after you have configured the controller as an elevator controller.
  
• The relays on the controller are not used for elevator control when using the MR16 modules for elevator control.

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). The shield drain can connect to the earth
  at pin 3 of the power connector or the ground lug screw as shown in the above diagram.

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

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

5.0 Elevator Control - With Floor Select

6.0 Elevator Control - No Floor Select

7.0 Verify the Doors.NET License

8.0 Controller Configuration

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 Set the Reader Floor Select Time and Output Time

9.1 Set the Floor Output Time

1. From the hardware tree select the Elevator Control reader.
   
2. Scroll down the reader properties and locate the Primary/Secondary (In/Out) settings.
   
3. Set the Floor Output Time (this determines how long the elevator output will be active after a button has been pressed).
   
   
   
   
4. For most installations this will need to be set at 1 second (to provide a momentary pulse to the elevator control system). The default setting is 1 second.
   

9.2 Set the Floor Select Time

10.0 Add an MR16IN Module (with Floor Select)

1. Double-click the controller that the MR16IN will be added to.
   
2. Select the bus that the MR16IN is wired to.
   
3. Click the MR16IN-S3 icon in the hardware select ribbon bar.
   
   
   
4. The module will appear on the hardware tree.
   
5. Confirm the prompt to reset the controller.
   
   Note: At this point you will see that the reader has been removed from the bus, that is because you cannot have access control and the MR16IN operating on the same bus of the NXT-MSC controller (because they use a different communication protocol).
   
   
6. Select the module and the properties will be displayed on the right.
   
7. Verify that the module is showing as online.
   
8. In the properties, locate the Comm address field - this is a non-editable field. This is the address that needs to be set to the module using the S1 switch.
   
   
   

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.

11.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. Click the MR16OUT-S3 icon in the hardware select ribbon bar.
   
   
   
   
4. The module will appear on the hardware tree.
   
5. Confirm the prompt to reset the controller.
   
   Note: At this point you will see that the reader has been removed from the bus - because you cannot have access control and the MR16OUT operating on the same bus as the NXT-MSC controller because they use a different communication protocol.
   
   
6. Select the module and the properties will be displayed on the right.
   
7. Verify that the module is showing as online.
   
8. In the properties, locate the Comm address field - this is a non-editable field. This is the address that needs to be set to the module using the S1 switch.
   

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.

12.0 Configure the Controller's Onboard Module

1. In Doors.NET enable Design Mode (click the design mode icon in the title bar).
   
   
   
   
2. Design Mode will now be enabled (the title bar will display [Design Mode]).
   
   
   
   
3. Close and re-open the hardware tree if it is already open.
   
4. Expand the controller and you will see an entry named 'Onboard MR52'.
   
5. Select the MR52.
   
   
   
   
6. The properties of the module will be displayed on the right.
   
7. Enable Advanced View.
   
   
   
   
8. Locate the Elevator Control settings.
   
9. Set 'Continue Inputs On'... the MR16IN module that you added in step 9.
   
   
10. Save the onboard module settings.

13.0 Test a Temp Unlock on All Floors

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.
   
   

Related Documentation

1. Setup Elevator Access Groups
   
2. Scheduled Override of Floors