1.0 Introduction

2.0 Power to the Module

The MR16IN accepts 12 to 24VDC for power. Locate power source as close to the unit as possible. Connect power with minimum of 18AWG wires.

3.0 RS-485 Communication Wiring

The MR16IN communicates to the host via 2-wire RS-485 interface. The interface allows multi-drop communication on a single bus of up to 4,000 feet (1,200 m). Use twisted pair(s) (minimum 24 AWG) with shield for the communication.

Notes:

• If the MR16IN module will be the last module on the 485 network set the jumpers across both pins of J1 to engage the 120 OHM line terminating resistor. If the module will not be the last on the network leave the jumper on one of the pins.
• Connect the RS-485 network to the TB10 terminal block.

4.0 S1 Dip Switch Settings

Switches 1 to 5 select the devices communication address. Switches 6 and 7 select the communication baud rate. Communication on the RS-485 serial port is asynchronous, half-duplex with 1 start bit, 8 data bits and 1 stop bit.

5.0 Add an MR16IN to Doors.NET

To add an MR16IN to the system you must already have a Mercury SPM (controller) or NXT-MSC controller added and online in the software.

 5.1 Add the MR16IN to a Mercury EP, LP or MP Controller

1. In the Doors.NET software click on Setup >> Hardware Setup >> All.
   
   
   
   
2. The hardware tree will be displayed. The Mercury gateway will be at the top of the hardware tree and any existing controllers will be listed beneath it.
3. Expand the SPM (controller), then select either TB2 or TB3 depending on which port the MR16IN is connected to.
   
   Note: Some Mercury controllers only have a TB2 port.
   
   
   
   
4. Click the MR16IN icon from the hardware select ribbon bar.
   
   
   
   
5. A dialog box will appear allowing you to add more than one module and to change the default description.
   
   
   
   
6. Click the ACCEPT button and the new module will be added to the TB2/TB3 entry on the controller. Expand TB2 or TB3 then select the new MR16IN module.
   
   
   
   
7. When the MR module is selected the properties will appear on the right. If the S1 DIP switch is set to the correct address and baud rate the module should be showing as online.
   
   Note: The first module added to TB2 or TB3 will have the default comm address of 0.
   
   
   
   
8. If you open up live events you will also see new events generated by the module. These events will also indicate that the module is online.
   
   
   

5.2 Add the MR16IN to an NXT-MSC Controller

1. From the hardware tree, expand the controller which the MR16IN is connected to.
   
2. Expand the specific bus that the module is connected to.
   
   
   
   
3. Select the reader which is automatically added to the controller, by default.
   
4. Click the Hardware Browser tab at the top of the screen.
   
   
   
   
5. Click the Remove icon located on the left.
   
6. Confirm that you wish to go ahead with removing the default reader.
   
7. Select the bus again and the bus properties will be displayed on the right side of the screen.
   
8. In the General properties locate the Protocol setting and change the protocol from Keri Systems to Mercury Security.
   
   
   
   Note: The Mercury MR module use a different RS-485 protocol, so when a Mercury MR module is added to a bus it is then not possible to have a NXT device on that same bus (such as an NXT 4x4 module, an NXT reader or an NXT RIM/Reader Interface Module).
   
   
9. Save the bus properties.
   
10. You will now be prompted to reset the controller so confirm to go ahead with this.
    
11. The NXT-MSC controller will now momentarily go offline. Once it is back online the controller reset is complete.
    
12. With the bus still selected click the MR16IN icon from the hardware select ribbon bar.
    
    
    
    
13. A dialog box will appear allowing you to adjust the quantity of MR16IN modules that you wish to add. You can also change the default description.
    
14. Click ACCEPT and the module will be added to the controller bus.
    
15. Select the new module on the hardware tree and the properties will appear on the right. If the comms address and the baud rate is set correctly on the S1 DIP switch (see section 4.0) then the module will almost immediately come online.
    
    
    
    Note: In the module's properties you will see that the default comms address for the first module added is 0, then next module added will be address 1 and so on.
    
    
16. If you open up live events you will see events generated by the MR16IN module - this further indicates that the module is online.