Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules

Size: px

Start display at page:

Download "Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules"

Jeffrey Carpenter
5 years ago
Views:

1 Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules This guide supplements the Synergis Master Controller Configuration Guide and explains how to configure Mercury interface modules attached to Synergis Master Controller (SMC). It is assumed that you have read the Synergis Master Controller Configuration Guide and are familiar with the terminology and concepts used in SMC Portal and Security Center. For specific information regarding Mercury Security products, refer to the manufacturer s web site. Click here for the most recent version of this document. This section includes the following topics: "Supported Mercury interface modules" on page 2 "Supported Mercury features" on page 3 "Supported SMC features" on page 4 "Supported Security Center features" on page 5 "Enrolling the Mercury modules connected to SMC" on page 7 "Address and baud rate settings on the Mercury panel" on page 11 "Decimal to binary conversion table" on page 12 IMPORTANT Topics appearing in this guide that reference information found on third-party websites were accurate at the time of publication, however, this information is subject to change without prior notice to Genetec. gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 1

2 Supported Mercury interface modules Supported Mercury interface modules SMC 2.2 supports the following Mercury interface modules. Model Description Supported firmware MR50 MR52 MR16IN MR16OUT Single card reader interface panel with two general purpose input monitor points and two control relays. Provides the I/O needed for controlling a single door. Dual card reader interface panel with 8 general purpose input monitor points and 6 control relays. Provides the I/O needed for controlling two doors. Multi-device interface panel with 16 general purpose input circuits (individually set to rmally open or rmally closed, and declared as Supervised or n-supervised) and two programmable relay outputs. Multi-device interface panel with 16 general purpose outputs as Form-C relay contacts. All All All All An interface module is a third party security device that communicates with SMC over IP, USB, or RS-485, and provides input, output, and reader connections to the controller module. In the context of Mercury integration, each Mercury panel is viewed as an interface module. gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 2

3 Supported Mercury features Supported Mercury features SMC 2.2 supports the following Mercury interface module features. Legend: (N/A) t applicable Features Category of interface module Communication protocol Encrypted communication Online operation Dependent mode a Supervised mode b Offline operation Degraded mode c Autonomous mode d Wireless operation Maximum number of credentials (for autonomous decision making) Maximum credential length (in bits) Maximum number of interface modules per RS-485 channel Supported Interface panel RS-485 N/A N/A See note e 32 f Recommended maximum number of interface modules per SMC unit 64 a. SMC makes all the access control decisions. b. The interface module makes all the access control decisions and reports them in real time to SMC. SMC overrides all decisions to deny access that contradict the access control logic currently in effect in SMC. c. The interface module grants access to all credentials matching a specified facility code. d. The interface module makes unsupervised decisions and defers the event reporting until the connection to SMC is reestablished. e. The maximum credential length depends on the reader attached to the interface module. The maximum tested at Genetec labs is 104 bits. The actual limit might be higher. f. Up to 32 Mercury interface modules can be connected to the same channel in daisy-chain. However, the more interface modules you connect to the same channel, the longer the response time becomes. For optimal performances, we recommend that you do not exceed 16 interface modules per channel. gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 3

4 Supported SMC features Supported SMC features The Mercury integration supports the following SMC 2.2 features. For a description of these features, see Synergis Master Controller Configuration Guide. Legend: (N/A) t applicable; () Dependent mode only. SMC features (SMC Portal) Hardware configuration Manual enrollment (Add hardware dialog box) Automatic enrollment (Scan button) Property configuration Configuration cloning (Clone button) I/O diagnostics (Live monitoring of inputs, relays, and readers) Interface module firmware display Interface module firmware upgrade Primitive key store Dual-swipe lock toggle Access control behavior Beep on door held open Beep on door forced open Beep on access denied Interlock setting (Single door unlock or Single door open) Reader setting (Card or PIN or Card only) Maximum PIN length in digits a Degraded mode settings Lock relay (After door opens or When door closes) Logging options Reader activity Input activity Output activity Access granted reasons Access denied reasons I/O linking Security clearance Supported N/A See note b 15 a. For interface modules that support mode-00 readers. b. Only applies to MR50 and MR52. gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 4

5 Supported Security Center features Supported Security Center features The Mercury integration supports the following Security Center access control features. For a description of these features, see Security Center Administrator Guide. Legend: (N/A) t applicable; () Dependent mode only. Security Center features Live event monitoring in Security Desk Module running state (Online, Offline) AC fail Battery fail Deadbolt (Secured, Released) Key override Door open/closed Door forced open Door held open too long Door properties (pushed from Security Center) Standard grant time Extended grant time Entry sensor b Standard access time Extended access time Maintenance mode (ignore all access events) Time to ignore REX after access is granted (in sec.) Unlock on REX (On/Off) Ignore REX events while door is open (On/Off) Time to ignore REX after door closes (in sec.) Enforce minimum security clearance level on areas Automatic credential enrollment using custom card format Unlock schedules Unlock schedule override Maintenance mode Activate/deactivate reader in Security Desk (reader shunting) Antipassback Soft (only logs antipassback violations without denying access) Hard (logs and deny access on antipassback violations) Timeout (automatically forgive violations after a certain time) Strict (antipassback checked on both area entrance and exit) Supported a See note c gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 5

6 Supported Security Center features Security Center features Interlock Priority (Override or lockdown) Zone management (hardware zone) Zone arming input Zone arming schedule Supported a. Only MR52, MR16IN, and MR16OUT support this event. b. The entry sensor is required to accurately detect entry into an area. In the absence of the entry sensor, the door sensor is used, and the entry is assumed when the door sensor is triggered. c. Only apply to MR50 and MR52. gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 6

7 Enrolling the Mercury modules connected to SMC Enrolling the Mercury modules connected to SMC For SMC to communicate with the Mercury interface modules connected to it, you must enroll them with SMC Portal. Before you begin Connect the Mercury modules to the RS-485 channels (A, B, C, or D) as follows: The local echo switches for all RS-485 channels must be set to the ON position, except when you expect to use the physical address 7 (see "About the RS-485 local echo switches" on page 10). To enroll the Mercury interface modules connected to SMC: 1 Log on to SMC (see the Synergis Master Controller Configuration Guide). 2 On the Home page, click Hardware. 3 Click Add ( ). 4 In the Add hardware dialog box, select Mercury Security as the Hardware type. 5 Select the Channel (A, B, C, or D) and its baud rate (Bits per second). All interface modules connected to the same channel must be from the same manufacturer. NOTE The baud rate is a channel property. The channel follows the baud rate of the last interface module added to the channel. The baud rate of the selected channel must match the settings on the interface module. The default baud rate is 38,400 bps. 6 In the same dialog box, add all interface modules connected to the same channel. IMPORTANT If you use the physical address 7, you must set the local echo switch corresponding to the selected channel to the OFF position (see "About the RS-485 local echo switches" on page 10). You can enroll the interface modules automatically or manually. TIP If you know the physical addresses of the modules and you only have a few to enroll, it would be faster to enroll them manually. Do one of the following: To enroll automatically, click Scan ( ). The scan feature finds and enrolls all interface modules from the same manufacturer that are connected to the same channel. IMPORTANT For this to work, all of the interface modules must use the same baud rate and be configured with a different physical address. If SMC Portal does not find all attached interface modules, verify their baud rate and physical address. For more information, see "Address and baud rate settings on the Mercury panel" on page 11. gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 7

Enrolling the Mercury modules connected to SMC To enroll manually, enter the physical address (0 to 31) configured on the Mercury panel, select the model type, and then click Add ( ).

8 Enrolling the Mercury modules connected to SMC To enroll manually, enter the physical address (0 to 31) configured on the Mercury panel, select the model type, and then click Add ( ). Repeat as necessary to enroll all modules attached to the same channel. 7 Click Save ( ). The hardware type, channel, and interface modules you just added appear in the hardware tree. gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 8

Enrolling the Mercury modules connected to SMC 8 For each interface module you just added, select it from the hardware tree, and configure its settings in the Properties tab.

9 Enrolling the Mercury modules connected to SMC 8 For each interface module you just added, select it from the hardware tree, and configure its settings in the Properties tab. For the description of these settings, refer to the manufacturer s documentation. Make the changes as needed. 9 At the bottom of the page, click Save ( ). 10 Test your interface module connection and configuration with the I/O diagnostics page (see the Synergis Master Controller Configuration Guide). After you finish Enroll the SMC unit in Security Center (see "Enrolling the SMC unit in Security Center" in the Synergis Master Controller Configuration Guide). gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 9

10 Enrolling the Mercury modules connected to SMC About the RS-485 local echo switches All RS-485 channels support the local echo feature. The local echo can be turned on/off with the switches SW3 to SW6 found on the Four-port RS-485 module (see the following diagram for the location of those switches on the board). The ON position is when the switch is aligned with its vertical marker (to the right). SW3 and SW4 Local echo switches for channel A and B SW5 and SW6 Local echo switches for channel C and D IMPORTANT For Mercury interface modules, the local echo switches must be set to the ON position, except when the physical address 7 is in use (see "Address and baud rate settings on the Mercury panel" on page 11). gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 10

11 Address and baud rate settings on the Mercury panel Address and baud rate settings on the Mercury panel The address and baud rate are set with a DIP switch found on the Mercury interface panel. The meaning of the switches are as follows: Switches 1 to 5 are used to set the device address. Switches 6 and 7 are used to set the baud rate. 00 = 2,400 bps 01 = 9,600 bps 10 = 19,200 bps 11 = 38,400 bps Switch 8 is not used. On the MR52 panel, the position of the switch that corresponds to the ON position (binary 1) is the side where the switch numbers are indicated. On other models of Mercury panel, it is indicated by the label ON. To convert from decimal to binary, use the Windows calculator (set to Programmer view), or refer to the "Decimal to binary conversion table" on page 12. For more information, see the documentation from Mercury Security corresponding to your specific device. gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 11

12 Decimal to binary conversion table Decimal to binary conversion table The dip switches represent a numeric value in binary format. Each switch represents a single digit (0 or 1). Use the following table to determine the positions of the switches to set for the given decimal value, from 0 to 31. Switch number 1 corresponds to the least significant bit. Decimal Binary (1 = ON) Decimal Binary (1 = ON) gtap.genetec.com Synergis Master Controller 2.2 Integration Guide for Mercury Interface Modules 12

Synergis Master Controller 2.2 Integration Guide for Axis Interface Modules

Synergis Master Controller 2.2 Integration Guide for Axis Interface Modules This guide supplements the Synergis Master Controller Configuration Guide and explains how to configure Axis interface modules