Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Live Search

Table of Contents

Like the DIGI*TRAC Controllers, a Hirsch Mx Controller consists of several components in a secure enclosure, as shown in the following figure.

Figure 2-1: Mx Controller Components (in Secure Enclosure)

The Controller enclosure contains the following major components:

  • Controller main board

  • Power supply

  • Standby battery

  • Tamper switch

  • Optional expansion boards

Each of these components is explained briefly.

Mx Controller Main Board


The Mx Controller Main Board contains the main connectors to the surrounding system. Through it, you can connect to ScramblePads, MATCH, and Wiegand reader interfaces, input devices, output devices, an Ethernet network, other controllers, and power sources.

The following figure shows the connectors (and other key components) of an Mx Controller’s main board.

Figure 2-2: Mx Controller Main Board Connectors and Components

Relays come in two sizes:

  • Larger (5 ampA, Form C) relays for controlling door access devices, such as magnetic locks and electric strikes, and

  • Smaller (1 ampA, Form C) relays for executing various types of alarm events.

Terminal Blocks are the green plastic components into which wires are inserted from input/output devices. An Mx Controller provides a certain number of terminal blocks - and through them connections to input/output devices - which you can increase by adding optional expansion boards.

  • The 3-wire (Door Input, Door Relay, and dedicated Alarm Relay) terminal blocks are used for analog inputs, such as multi-state alarm inputs through the line modules, and two-state outputs such as magnetic locks and electric strikes.

  • The 5-wire MATCH terminal blocks are used for connecting the wiring from ScramblePad keypads or readers (through the MATCH2 Reader Interface). These are digital circuits which support daisy-chain connections to multiple devices on the same circuit.

  • The 6-wire terminal blocks are used for connecting the wiring from a 12VDCkeypad or reader with a Wiegand interface. These are designed to support a variety of 125 kHz and 13.56 MHz readers and credentials.

AUX RS485 Terminal was originally planned to later enable you to communicate with RS485 RS-485 serial devices (such as readers and other interfaces), using protocols such as the Open Supervised Device Protocol (OSDP). This capability is now provided by the RREB; see “RS-485 Readers Expansion Board (RREB)”.

SNIB2 RS485 Terminal (and DIP switches) enables you to securely communicate with downstream Mx series or DIGI*TRAC controllers (managed by the same computer).

Ethernet Connector (and DIP switches) enables you to connect to a LAN/WAN and communicate with a computer running Velocity.

Fuses are mounted by the power supply connector and the standby battery connector. (All reader terminals are protected with resettable fuses.)

Expansion Board Connector links any expansion boards mounted in the Controller enclosure to the Controller Main Board.

Status LEDs provide quick visual diagnostics on the current operation of the Controller.

Reset Button performs three types of reset depending on how long you hold down the button, as explained in “Resetting the Controller”.

Command and Control Module (CCMx) contains the firmware that embodies the logic and control functions of the controller, including the DIGI*TRAC Control Language. Firmware can be downloaded from Velocity, or the CCMx can be reprogrammed on a Flashmaster device.

Different models of the CCMx are available, which determine whether the Mx Controller is configured to control up to 2, 4, or 8 doors (and an equivalent number of alarm inputs).

Power Supply Connector provides cable connection to the Internal Power Supply.

Standby Battery Connector provides cable connection to the backup battery.

Enclosure Tamper Switch Connector provides a cable connection to the Tamper Switch on the Controller enclosure. Whenever the enclosure door is opened, the tamper switch alarm is activated.

Mx-S3OB Controller Main Board


The Mx-S3OB Controller Main Board contains the main connectors to the surrounding system. Through it, you can connect to Scramble Pads, MATCH, and Wiegand reader interfaces, input devices, output devices, an Ethernet network, other controllers, and power sources.

The following figure shows the connectors (and other key components) of an Mx-S3OB Controller’s main board.

Image RemovedImage Added

Figure 2-3: Mx -S3OB Controller Main Board Connectors and Components

Relays come in two sizes:

  • Larger (5 ampA, Form C) relays for controlling door access devices, such as magnetic locks and electric strikes, and

  • Smaller (1 ampA, Form C) relays for executing various types of alarm events.
    Terminal Blocks are the green plastic components into which wires are inserted from input/output devices. An Mx Controller provides a certain number of terminal blocks - and through them connections to input/output devices - which you can increase by adding optional expansion boards.

  • The 3-wire (Door Input, Door Relay, and dedicated Alarm Relay) terminal blocks are used for analog inputs, such as multi-state alarm inputs through the line modules, and two-state outputs such as magnetic locks and electric strikes.

  • The 5-wire MATCH terminal blocks are used for connecting the wiring from Scramble Pad keypads or readers (through the MATCH2 Reader Interface). These are digital circuits which support daisy-chain connections to multiple devices on the same circuit.

    • The 6-wire terminal blocks are used for connecting the wiring from a 12VDC keypad or reader with a Wiegand interface. These are designed to support a variety of 125 kHz and 13.56 MHz readers and credentials.

AUX RS485 Terminal was originally planned to later enable you to communicate with RS485 RS-485 serial devices (such as readers and other interfaces), using protocols such as the Open Supervised Device Protocol (OSDP). This capability is now provided by the RREB; see “RS-485 Readers Expansion Board (RREB)”.

SNIB3 RS485 Terminal (and DIP switches) enables you to securely communicate with downstream Mx series or DIGI*TRAC controllers (managed by the same computer).

Ethernet Connector (and DIP switches) enables you to connect to a LAN/WAN and communicate with a computer running Velocity.

Fuses are mounted by the power supply connector and the standby battery connector. (All reader terminals are protected with resettable fuses.)

Expansion Board Connector links any expansion boards mounted in the Controller enclosure to the Controller Main Board.

Status LEDs provide quick visual diagnostics on the current operation of the Controller.

Reset Button performs three types of reset depending on how long you hold down the button, as explained in “Resetting the Controller”.

Command and Control Module (CCMx) contains the firmware that embodies the logic and control functions of the controller, including the DIGI*TRAC Control Language. Firmware can be downloaded from Velocity, or the CCMx can be reprogrammed on a Flashmaster device.

Different models of the CCMx are available, which determine whether the Mx Controller is configured to control up to 2, 4, or 8 doors (and an equivalent number of alarm inputs).

Power Supply Connector provides cable connection to the Internal Power Supply.

Standby Battery Connector provides cable connection to the backup battery.

Enclosure Tamper Switch Connector provides a cable connection to the Tamper Switch on the Controller enclosure. Whenever the enclosure door is opened, the tamper switch alarm is activated.

Internal Power Supply


The Internal Power Supply can use either a 110 or 240 VAC 240VAC supply (or 100 VAC 100VAC for Japan) to provide DC power to the Controller Main Board and attached Expansion Boards. Depending on your controller, this means support for up to 16 ScramblePads or combination of ScramblePads and readers. For input and output devices requiring power - such as electric strikes and magnetic locks, motion detectors, retinal scanners, and surveillance cameras - auxiliary power supplies must be used.

Standby Battery


This component supplies 24 VDC24VDCof backup power to the Controller Board even if primary AC power fails. This battery is capable of supplying power to the Controller Board for several hours. The standby time is dependent on the connected devices and can be calculated by using the formula found in “Mx Controller Standby Battery Capacity”.

Info

The size of the 7.2 Ah battery pack provided with an Mx-4 or Mx-8 controller is approximately 3.69” H x 5.94” W x 5.13” D (94 mm H x 151 mm W x 130 mm D).

Under normal conditions, the standby battery has a life span of 4 to 5 years. Its status can be interrogated using Velocity’s Diagnostic Window. For more information, see the topics in the section about “Performing Periodic Maintenance for an Mx Controller”.

Tamper Switch


The tamper switch is a contact switch that is normally closed while the door to the controller enclosure is closed. Opening the enclosure door opens a circuit, which generates a message that is sent to Velocity, enabling the event to be viewed in real-time and logged for later analysis.

Expansion Boards for the Mx Controller


Optional expansion boards increase the capabilities of Mx Controllers. For example, the Alarm Expansion Board increases the number of line module inputs that the controller can accept, and the Relay Expansion Board extends the number of control outputs that a controller can accommodate. The MEB series increases the controller’s available memory, expanding the number of alarm and event buffers or codes the controller can hold.

Table 2-1 provides an overview of the available expansion boards. An Mx Controller can accommodate up to 5 expansion boards, subject to the restrictions explained in this table.

Table 2-1: Expansion Boards for the Mx Controller

Expand
titleSee Table Table 2-1: Expansion Boards for the Mx Controller

Model #

Description

Comments

AEB8

Alarm Expansion Board with


8 Inputs

Adds 8 additional high security alarm inputs, and features


removable connectors. Each input requires an appropriate


Line Module.

An AEB8 draws 15 mA at

28 VDC

28VDC.

Velocity supports up to 4 of these boards in an Mx Controller.

REB8

Relay Expansion Board with


8 Relays

Adds 8 additional 2 Amp Form C dry mode relays. Features


status LEDs and removable connectors.

An REB8 draws 15 mA at

28 VDC

28VDC when idle, and a maximum


of 80 mA when all relays are active.

Velocity supports up to 5 of these boards in an Mx Controller.

MEB/CB64

Memory Expansion Board -


Code Expansion of 64,000
with Buffer Option

Expands Code Memory by approximately 64,000 (from


4,352 to 71,424) on Velocity. A portion of the Code Memory may be allocated to alarm and event Buffers, which will reduce the number of users. Protected from data loss during power failures for up to 30 days by controller memory battery.

An MEB draws 8 mA at

5 VDC

5VDC.

Velocity supports only 1 memory expansion board in an


Mx Controller.

MEB/CB128

Memory Expansion Board -


Code Expansion of 128,000
with Buffer Option

Expands Code Memory by approximately 128,000 (from


4,352 to 135,424) on Velocity. A portion of the Code


Memory may be allocated to alarm and event Buffers,


which will reduce the number of users. Protected from data loss during power failures for up to 30 days by controller memory battery.

An MEB draws 8 mA at

5 VDC

5VDC.

Velocity supports only 1 memory expansion board in an


Mx Controller.

RREB

RS-485 Readers Expansion


Board

Adds eight independent RS-485 communication ports, for


fast processing of PIV or PIV-I credentials at FICAM compliant smart card readers (which are part of a physical


access control system) using the bi-directional Open Supervised Device Protocol (OSDP). Each port is capable of supporting a door with both an entry reader and an exit reader.

SNIB

SCRAMBLE*NET Interface


Board

Adds two optically isolated serial ports, one a multidrop


RS-485 channel, the other a direct connect RS-232. Both


can be active concurrently. When the RS-485 port is used


for connection to other controllers, the RS-232 port can


connect to a host PC locally or by modem.

Velocity supports only 1 SNIB, SNIB2, or SNIB3 expansion


board in an Mx Controller. The Mx Controller does


not include an RS-232 port, so adding an original SNIB


expansion board enables you to connect using a modem.

SNIB2

Secure Network Interface


Board 2

Adds a 10/100 Ethernet (TCP/IP) port with an RJ45 connector, and two optically isolated serial ports, one a multidrop RS-485 channel, the other a direct connect RS-232.

Uses the X*NET2 protocol, which supports AES (128 bit


Rijndael) encryption between host PC and Master SNIB2,


and between Master SNIB2 and downstream SNIB2. Master SNIB2 supports integral XBox functionality for globalization (no globalization between SNIB2 Masters).

A SNIB2 draws 450 mA at

5 VDC

5VDC during normal operation,


and draws a maximum of 500 mA at

5 VDC

5VDC when starting up.

Velocity supports only 1 SNIB, SNIB2, or SNIB3 expansion


board in an Mx Controller. Although the Mx Controller


has integrated SNIB2 capability, it does not include an


RS-232 port, so adding a SNIB2 expansion board enables


you to connect using a modem, leased line module, or fibre optic converter.

SNIB3

Secure Network Interface


Board 3

Adds a 10/100/1000 Ethernet (TCP/IP) port with an RJ45


connector, and an optically isolated multidrop RS-485


serial port. Supports either IPv4 or IPv6 addressing.

Can use either the X*NET2 protocol which supports 128-


bit AES encryption (and a mixed network of SNIB2s and


SNIB3s), or the X*NET3 protocol which supports 256-bit


AES encryption (if every controller has a SNIB3).

The SNIB3 is not compatible with the original SNIB, and


cannot be used with the M1N controller (because it does


not support any expansion boards).

A SNIB3 draws 550 mA at

5 VDC

5VDC during normal operation,


and draws a maximum of 850 mA at

5 VDC

5VDC when starting up.

Velocity supports only 1 SNIB, SNIB2, or SNIB3 expansion


board in an Mx Controller. If you want to use a SNIB3


expansion board, see

“Preparing

Preparing an Mx Controller with a


SNIB2 to Use a

SNIB3”

SNIB3.

Although Velocity enables you to reconfigure an unused door so you can use its inputs and relay components for other purposes, the addition of alarm or relay expansion boards does not increase the supervised door capacity of an Mx Controller.

All expansion boards have the same dimensions and shipping weight:

Info

Dimensions: 6”H x 4.25”W x 0.75”D (15.2cm x 10.8cm x 1.9cm)
Shipping Weight: 1 lb (0.5 kg)

The ribbon cable used to connect these boards to the Controller board is the EBIC5, which can link up to five expansion boards. For detailed information about the setup and installation of expansion boards, see “Expansion Board Installation”.

If you will be using the Ethernet connector to connect your Mx controller to a LAN/WAN so it can communicate with a computer running Velocity, and you plan to install multiple expansion boards, you should plug in the network cable before installing the expansion boards (while it is easier to access the Ethernet connector).

Data Capacity of an Mx Controller


An Mx controller includes a base amount of memory which is dedicated to storing data about credentials, events, and alarms. (This memory enables the controller to continue performing its functions even when it is temporarily unable to communicate with the Velocity server.)

The data capacity of an Mx controller can be increased by adding optional expansion boards. An expansion board can be configured so that its memory is dedicated either solely to additional credentials, or to a mixture of additional credentials, events, and alarms.

The following table shows the maximum data capacity of an Mx controller in its base configuration and with various optional expansion boards configured either way.

Table 2-2: Data Capacity of an Mx Controller

Controller configuration

maximum

Maximum Credentials

maximum

Maximum Events

maximum

Maximum Alarms

Base (no expansion boards)

4,352

1,560

1,560

With MEB/CB64 and 20% reduction Enabled

55,200

37,440

5,460

With MEB/CB64 and 20% reduction Disabled

69,888

1,560

1,560

With MEB/CB128 and 20% reduction Enabled

106,400

65,520

17,160

With MEB/CB128 and 20% reduction Disabled

135,424

1,560

1,560

Note that your system’s actual capacity could be less, as explained in “Velocity Features that Reduce Available Memory”.

Replaceable Parts of an Mx Controller


The following table provides specifications for the replaceable parts of the different models of the Mx controller.

Note

There is a risk of explosion if the battery is replaced by an incorrect type.

Table 2-3: Replaceable Parts for the Different Models of the Mx Controller

Part

Mx-2

Mx-4

Mx-8

Standby Battery

1.3 Ah 12V rechargeable


sealed lead-acid; made by


Prism, part# GH1213

7.2

9 Ah 12V rechargeable


sealed lead-acid;

made

manufactured by

Panasonic

ZEUS, part#

LCR127R2P
(or LCR127R2P1)7.2

PC9-12S (Two of these are wired in series to provide 24V)

9 Ah 12V rechargeable


sealed lead-acid;

made

manufactured by

Panasonic

ZEUS, part#

LCR127R2P
(or LCR127R2P1

PC9-12S (Two of these are wired in series to provide 24V)

Memory Battery

80 mAh 3.6V rechargeable


nickel-metal hydride; made


by House of Batteries, part#


XVN-H80BC-L3C

80 mAh 3.6V rechargeable


nickel-metal hydride; made


by House of Batteries, part#


XVN-H80BC-L3C

80 mAh 3.6V rechargeable


nickel-metal hydride; made


by House of Batteries, part#


XVN-H80BC-L3C

Power Supply


Input Fuse

5 A 250V 5 mm x 20 mm;


made by Little Fuse Inc.,


part# 0218005.HXP

5 A 250V 5 mm x 20 mm;


made by Little Fuse Inc.,
part# 0218005.HXP

5 A 250V 5 mm x 20 mm;


made by Little Fuse Inc.,
part# 0218005.HXP