Both the Mx-1 and the Mx-1-ME models of the Mx-1 controller include a main board with various components and connectors, as shown in Figure 3-2 in section “Mx-1 Controller Main Board”. The Mx-1-ME model’s secure metal enclosure also includes a power supply, a standby battery, a locking door with a tamper switch, and room for optional expansion boards, as shown in the following figure.
Figure 3-1 Components of the Mx-1-ME Controller
Because the Mx-1-ME model includes a power supply, its Ethernet connection does not include the Power over Ethernet (PoE+) functionality which is included on the standard Mx-1 model.
Mx-1 Controller Main Board
The Mx-1 controller’s main board contains the main connectors to the surrounding system. Through it, you can connect to readers with Wiegand or OSDP interfaces, input devices, output devices, an Ethernet network (for communication with the Velocity server), other controllers (using RS-485 chaining), and power sources.
For the Mx-1 model, all connectors, LEDs, DIP switches, and the RS-485 chaining address knob are right angled (facing outward) so they can be accessed while the plastic case is closed.
For the Mx-1-ME model, all connectors, DIP switches, and the RS-485 chaining address knob are vertical, and the mini LEDs will be like those on the Mx-2/4/8 controller. Note that the new bank of 8 green and 8 yellow status LEDs (in the lower left corner) are not included on the Mx-1-ME’s main board.
Figure 3-2 shows the connectors (and other key components) of an Mx-1 controller’s main board which are for customer use. (Figure 3-3 shows the connectors which are used by Identiv for testing, debugging, and programming.)
Figure 3-2 Mx-1 Controller Main Board Connectors and Components for Customer Use
The following table describes the connectors and components identified in Figure 9-2, starting at the lower left corner of the board and moving clockwise. (The detailed pin out information for the terminals is provided in Table 3-2.)
Table 3-1 Description of the Mx-1 Controller’s Connectors and Components for Customer Use
Connector or Component
Description
Connector or Component
Description
Replaceable Fuses
These small replaceable fuses (behind the Power and the Battery input terminals) protect the main board from power surges, and excessive current draw. They are 2 Amp 125 VAC/VDC fuses, part number 0451002.MRL, by Littelfuse, Inc.
Power
This 2-pin green connector is used to supply 24V - 28V DC power to the Mx-1 controller, from a 2 Amps external power supply.
For the Mx-1-ME model, this connector is wired at the factory to the included power supply. (Because the Mx-1-ME model includes a power supply, its Ethernet connection does not include the Power over Ethernet functionality.)
For the Mx-1 model, you can either use this connector to supply DC power, or you can use the PoE+ Ethernet connector to supply a nominal 25.5 Watts of power.
If the Mx-1 controller will be part of an access control system which must meet a particular UL standard, you must use a UL-listed power source which provides the required duration of standby power for that standard. For more information, see Standby Power Requirements for Various UL Standards in section “General UL Information”.
If you are using the PoE+ Ethernet connector to supply power, you should not use this connector to supply additional power.
Battery
This 2-pin green connector is used to attach a 24V DC backup battery pack to the Mx-1 controller.
For the Mx-1-ME model, this connector is wired at the factory to the included 7.2 Ah backup battery pack.
For the Mx-1 model, you can use this connector for an external backup battery pack or an uninterruptible power supply. (This capability was not evaluated by UL.)
When using a 24V battery pack, the DC power source should be 28V at 2 Amps, to charge the batteries. (A PoE+ power source cannot be used to charge a 24Vbattery pack.)
RS-485 Controller Bus Termination DIP Switches
If you are adding an Mx-1 controller (which has built-in SNIB3 functionality) to a chain of controllers connected byRS-485 wiring, this bank of four DIP switches is used to indicate whether the controller is located at the beginning, middle, or end of the chain.
This is just like SW1 on the SNIB2, the Mx-2/4/8 controller's main board (with built-in SNIB2 functionality), and the SNIB3.
When the Mx-1 controller is in the middle of a chain, all 4 switches must be OFF.
When the Mx-1 controller is either the first (master) or last (termination) one in a chain, all 4 switches must be ON.
Buzzer
This component generates an audible alarm during certain conditions.
RS-485 Controller Bus terminal
This 6-pin yellow connector can be used to create a chain of controllers, where the first (master) controller communicates directly with the Velocity Server across a network using the PoE+ Ethernet connector, and the other (downstream) controllers communicate along the chain using RS-485 wiring.
This 16-position rotary switch is used to set the address of an Mx-1 controller when it is part of a chain of controllers connected using RS-485 wiring. The valid values are 1 through F (1-15).
Reset button
This recessed button performs three types of reset, depending on how long you hold down the button. (On previous DIGI*TRAC or Mx controllers, this was also known as the “blue button”.)
Press the button for 1 second if you have a problem that won’t clear within a few minutes. All alarm conditions in the alarm buffers will be deleted, and any alarm relays that are currently active will be turned off and reset.
Press the button for 5 seconds to reset the system code to the factory default of 123, and to reset ScramblePads to their original programming parameters.
Press the button for 30 seconds if a major and persistent problem occurs. This resets the entire controller, clears all controller memory, and returns all settings to the original factory default values.
For the Mx-1-ME model only, this 5-sided 3-pin connector attaches to the corresponding connector for the wiring of the plunger-style contact switch that indicates whether the door of the metal enclosure is closed or open. When the door is opened, the plunger is extended, and a “door tamper” alarm is generated in Velocity.
(The Mx-1 model uses an optical tamper mechanism with its plastic case.)
Case Tamper
For the Mx-1 model only, this component provides an optical tamper mechanism that indicates whether the plastic case is closed or open. When the case is opened, the Case Tamper LED (in the group of large Status LEDs) is lit, and a “door tamper” alarm is generated in Velocity.
(The Mx-1-ME model uses the Door Tamper connector to attach to a switch that is part of its enclosure.)
Expansion Boards connector
This connector is used to attach the EBIC5 flat ribbon cable that provides power to and communicates with any optional expansion boards installed in an Mx-1-ME.
This rechargeable Li-ion coin cell battery supplies backup power to the Mx-1 controller’s memory, so critical information is not lost during a power outage of up to 10 days. That information includes user credentials, configuration, and date/time. This battery is model PD3048 by Route Jade (formerly Route JD or Korea Power Cell), which provides 3.7 VDC, and has a 300 mAh capacity. Its dimensions are 30.0 mm in diameter by 4.9 mm thick.
This 8-pin blue connector is used to attach the door’s entry reader when it is one that uses the Wiegand protocol. For more information, see “Wiring Diagram for Wiegand Readers”.(If your readers use the Open Supervised Device Protocol (OSDP), then they will be attached using the OSDP RS-485 Readers terminal.) This terminal is fused and resettable, and provides 12VDC power for the entry reader. On the Mx-1, this terminal provides up to 0.5 Amps; on the Mx-1-ME, this terminal provides up to 0.355 Amps.
Wiegand Exit Reader terminal
This 8-pin blue connector is used to attach the door’s optional exit reader when it is one that uses the Wiegand protocol. For more information, see “Wiring Diagram for Wiegand Readers”.
(If your readers use the Open Supervised Device Protocol (OSDP), then they will be attached using the OSDP RS-485 Readers terminal.)
This terminal is fused and resettable, and provides 12VDC power for the exit reader. On the Mx-1, this terminal provides up to 0.5 Amps; on the Mx-1-ME, this terminal provides up to 0.355 Amps.
SNIB3 Status LEDs
This set of small LEDs displays the current status of the Mx-1-ME controller’s built-in SNIB3. (The Mx-1 uses a set of larger green and yellow LEDs which is visible when the plastic case is closed.)
This set of small LEDs displays the current status of the Mx-1-ME controller. (The Mx-1 uses a set of larger green and yellow LEDs which is visible when the plastic case is closed.)
This 5-pin dark blue connector is used to attach the door’s entry reader when it is one that uses OSDP. (When the door has an optional exit reader that uses OSDP, it is wired “through” the entry reader.) For more information, see “Wiring Diagram for OSDP Readers”.
This terminal is fused and resettable, and provides up to 0.75 Amps at 12VDC for the attached readers.
The Open Supervised Device Protocol (OSDP) is a standard adopted by the Security Industry Association (SIA). OSDP is a secure bi-directional protocol that replaces the traditional Wiegand protocol, and manages the communication between access control panels and card readers (or other peripheral devices).
Door Input terminal
This 3-pin white connector is used for an analog input, such as the multi-state alarm inputs provided by the line module that detects changes in the status of a door’s components (for example the position of the door contacts and the press of a Request to Exit button or the triggering of a motion detector).
This 3-pin red connector is used to control the door’s access device, such as a magnetic lock or an electric strike. The Wet or Dry Mode jumpers (described later in this table) determine the power mode for the Door Relay and the Aux.Relay terminals.
When this door relay is configured for Wet Mode at 24V, the Mx-1 supplies regulated power at 24 Volts, with a maximum output current of 0.25 Amps. (At 24V, the maximum simultaneous current draw for this Door Relay and the Aux Relay is 0.5 Amps.)
When this door relay is configured for Wet Mode at 12V, the Mx-1 supplies regulated power at 12 Volts, with a maximum output current of 0.5 Amps. (At 12V, the maximum simultaneous current draw for this Door Relay and the Aux Relay is 1.0 Amps.)
When this door relay is configured for Dry Mode, its maximum output current is 2.0 Amps, and the voltage is either 30VDC or 250VAC.
This 3-pin red connector is used to control external alarm or auxiliary devices, such as activating an audible alarm, turning on lights, or initiating the recording of surveillance video. The Wet or Dry Mode jumpers (described next in this table) determine the power mode for the Door Relay and the Aux. Relay terminals.
When this auxiliary relay is configured for Wet Mode at 24V, the Mx-1 supplies regulated power at 24 Volts, with a maximum output current of 0.25 Amps. (At 24V, the maximum simultaneous current draw for this Aux Relay and the Door Relay is 0.5 Amps.)
When this auxiliary relay is configured for Wet Mode at 12V, the Mx-1 supplies regulated power at 12 Volts, with a maximum output current of 0.5 Amps. (At 12V, the maximum simultaneous current draw for this Aux Relay and the Door Relay is 1.0 Amps.)
When this auxiliary relay is configured for Dry Mode, its maximum output current is 2.0 Amps, and the voltage is either 30VDC or 250VAC.
This set of pins and jumpers determines whether the devices connected to the Door Relay terminal and the Aux. Relay terminal are wired in wet mode at 24V, wet mode at 12V, or dry mode.
In Wet mode at 24V, the Mx-1 supplies regulated power at 24 Volts, with a maximum output current of 0.25 Amps per port.
In Wet mode at 12V, the Mx-1 supplies regulated power at 12 Volts, with a maximum output current of 0.5 Amps per port.
In Dry mode, the device is powered by an external power source.
The jumper settings for these modes are printed on the top cover of the Mx-1’s plastic case, in the bottom right corner:
Configuration DIP switches
This bank of 6 DIP switches is used to configure the Mx-1 controller’s built-in SNIB3:
The first 4 DIP switches are used to configure certain functionality of the built-in SNIB3 (just like SW2 on the SNIB3), including resetting its encryption keys, resetting it to the factory default settings, and indicating whether this controller is the first (master) in a chain of controllers and is connected to the Velocity Server via Ethernet.
The last 2 DIP switches correspond to the first 2 DIP switches on the SNIB3’s SW3 bank, and are used to configure the communications speed when this controller is part of a chain of controllers connected to each other using RS-485 wiring.
This Ethernet connector provides up to Gigabit data connectivity for secure communication with the Velocity server.
On the Mx-1 model, this connector can be used to power the controller (and some attached devices) through PoE+ with a nominal 25.5 Watts of input power.
Because the Mx-1-ME model includes a power supply, its Ethernet connection does not include the Power over Ethernet functionality.
This set of LEDs provides information about the current status and operation of the Mx-1 controller, which is visible from the outside of the closed plastic case. (These LEDs do not appear on the Mx-1-ME’s main board.)
Table 3-2 provides the detailed pin-out information for the various connectors which snap into the corresponding terminals on the Mx-1 controller’s main board (which is shown in Figure 3-2). (The Mx-1-ME has the same connectors, which are mounted vertically.)
Table 3-2 Pin Out Information for the Mx-1 or Mx-1-ME Controller’s Terminals
The following figure shows the connectors which are used by Identiv for testing, debugging, and programming.
Figure 3-3: Mx-1 Controller Main Board Connectors for Testing and Debugging
The following table describes the connectors identified in Figure 3-3, starting at the lower left corner of the board and moving clockwise.
Table 3-3: Description of the Mx-1 Controller’s Connectors for Testing and Debugging
Connector
Description
Connector
Description
STM Debug jack
This jack (or the STM Debug pins) is used by Identiv to debug the STM32 processor.
STM JTAG pins
This set of 20 pins is used by Identiv to program the STM32 processor.
iMx Debug jack
This jack is used by Identiv to debug the built-in SNIB3.
STM Debug pins
This set of 3 pins (or the STM Debug jack) is used by Identiv to debug the STM32 processor.
Status LEDs
The groups of status LEDs appearing on the Mx-1 controller’s main board (as indicated on Figure 3-2) vary by model.
The Mx-1 model (but not the Mx-1-ME) has two adjacent blocks of large Status LEDs near the lower left corner of its main board, providing a row of 8 green LEDs on the top and a row of 8 yellow LEDs on the bottom:
The Mx-1-MEmodel (but not the Mx-1) has a set of 12 miniature Controller Status LEDs near the middle of its main board (like those on the Mx-2/4/8 controller’s main board):
The Mx-1-ME model (but not the Mx-1) has a set of 6 miniature SNIB3 Status LEDs near the middle of its main board (like those on the Mx-2/4/8 controller’s main board for its built-in SNIB2):
This block of 16 larger LEDs, which appear only on the Mx-1 model’s main board, provides information about the current status and operation of the Mx-1 controller which is visible outside of the closed plastic case. (This block of LEDs is not included on the Mx-1-ME, because it is not visible when the metal enclosure’s door is closed.)
The following graphic includes ID numbers for the LEDs, which are used in the table describing their meanings.
Table 3-4: Meanings of the Status LEDs on the Mx-1
LED #
Purpose
Description (as of CCM/CCMx firmware version 7.6.20)
LED #
Purpose
Description (as of CCM/CCMx firmware version 7.6.20)
G1
Host Tx
If this controller is connected to an Ethernet network, this LED indicates when this controller’s built-in SNIB3 is transmitting data to the Velocity Server.
When this LED is on, it means this controller is transmitting data to the Velocity Server.
When this LED is off, it means this controller is not currently transmitting data to the Velocity Server.
Y1
Host Rx
If this controller is connected to an Ethernet network, this LED indicates when this controller’s built-in SNIB3 is receiving data from the Velocity Server.
When this LED is on, it means this controller is receiving data from the Velocity Server.
When this LED is off, it means this controller is not currently receiving data from the Velocity Server.
G2
Bus Tx
Indicates when data is being transmitted (either upstream or downstream) by this controller along a chain of controllers connected using RS-485 wiring.
When this LED is on, it means data is being transmitted by this controller along a chain of controllers connected using RS-485 wiring.
When this LED is off, it means data is not currently being transmitted by this controller along a chain of controllers connected using RS-485 wiring. (This LED is also off when this controller is not part of a chain of controllers connected using RS-485 wiring.)
Y2
Bus Rx
Indicates when data is being received by this controller along the RS-485 wiring that connects a chain of controllers.
When this LED is on, it means data is being received by this controller along the RS-485 wiring that connects a chain of controllers.
When this LED is off, it means data is not currently being received by this controller along the RS-485 wiring that connects a chain of controllers. (This LED is also off when this controller is not part of a chain of controllers connected using RS-485 wiring.)
G3
Readers Tx
Indicates when the controller is transmitting commands or data to a connected reader.
When this LED is on, it means the controller is transmitting commands or data to a connected reader.
When this LED is off, it means the controller is not currently transmitting commands or data to any of the connected readers.
Y3
Readers Rx
Indicates when the controller is receiving data from a connected reader.
When this LED is on, it means the controller is receiving data from a connected reader.
When this LED is off, it means the controller is not currently receiving data from any of the connected readers.
G4
Door Relay
Indicates when the door relay is active.
When this LED is on, it means the door relay is active.
When this LED is off, it means the door relay is not currently active. A Normally Open (NO) circuit is open, and a Normally Closed (NC) circuit is closed.
Y4
Aux. Relay
Indicates when the alarm (a.k.a. auxiliary) relay is active.
When this LED is on, it means the alarm relay is active.
When this LED is off, it means the alarm relay is not currently active. A Normally Open (NO) circuit is open, and a Normally Closed (NC) circuit is closed.
G5
Door Alarm
Indicates whether a door alarm is active.
When this LED is on, it means there is an active Door Forced Open alarm.
When this LED is off, it means there is not an active door alarm.
When this LED isflashing, it means there is an active Door Open Too Long alarm.
Y5
Fault Alarm
Indicates whether a fault condition exists on the supervised line input.
When this LED is on, it means there is a fault (such as a cut line or a short circuit).
When this LED is off, it means the supervised line is within normal specifications.
G6
Processing Events
Indicates when event information is being transmitted to the Velocity Server by the controller’s built-in CCMx.
When this LED is on, it means the controller is transmitting event information to the Velocity Server.
When this LED is off, it means the controller is not currently transmitting event or configuration information to the Velocity Server.
When this LED is flashing, it means the controller is transmitting configuration information to the Velocity Server.
Y6
Processing Cred/Cfg
Indicates when user credentials or configuration information is being received by the controller’s built-in CCMx.
When this LED is on, it means user credentials are being received by the controller.
When this LED is off, it means user credentials or configuration information is not currently being received by the controller.
When this LED is flashing, it means configuration information is being received by the controller.
G7
Case Tamper
Indicates when the controller’s enclosure is open.
When this LED is on, it means the controller’s enclosure is open. (Either an optical tamper device indicates that the Mx-1 model’s plastic case is open, or a plunger switch indicates that the door is open on the Mx-1-ME model’s metal enclosure.)
When this LED is off, it means no enclosure tamper is currently detected.
When this LED is flashing, it means multiple instances of an enclosure tamper have been detected (because the previous alarm was not cleared).
Y7
Reader Tamper
Indicates when a tamper condition exists at a reader attached to the controller.
When this LED is on, it means there is a reader tamper or a code tamper.
When this LED is off, it means no reader tamper or code tamper is currently detected.
G8
PSU/PoE Power
Indicates when the controller has adequate power, and whether it is 24 V - 28 V DC from an external power supply or from POE+ (via the Ethernet jack).
When this LED is on, it means the controller is being powered by DC input through the Power terminal), and its voltage is at least 22 V.
When this LED is off, it means the controller's power is either low (between 11 V and 13 V) or has failed (less than 11 V).
When this LED is flashing, it means the controller is either being powered by POE+ (via the Ethernet jack), or its voltage is between 13 V and 22 V.
Y8
Battery Power
Indicates when the connected standby battery pack is low or bad.
When this LED is on, it means the battery is bad, with a voltage of less than 6 V (and should be replaced).
When this LED is off, it means the battery is good, and its voltage is at least23 V.
When this LED is flashing, it means the battery is either low (with its voltage between 17 V and 23 V), or is charging (with its voltage between 6 V and 17 V) if AC power is available.
Controller Status LEDs on the Mx-1-ME
This set of 12 miniature LEDs (on the Mx-1-ME controller’s main board) displays the current status of the controller.
The meanings of all these controller status LEDs in version 7.5.70 of the CCM/CCMx firmware are explained in the following table.
Table 3-5: Meanings of the Controller Status LEDs on the Mx-1-ME (as of CCMx 7.5.70)
Name and Purpose of row of status LEDs
Meaning of First LED
Meaning of Second LED
Name and Purpose of row of status LEDs
Meaning of First LED
Meaning of Second LED
AC = AC Power
ON = AC Power is OK
ON= AC Power Failure
Both LEDs BLINKING = AC Power is Low (orMx-1-ME controller is using Power over Ethernet+)
Battery = Standby Battery
ON = Battery is OK (at 24V - 28V)
ON = Battery Failure (less than 21V)
Both LEDs BLINKING = Battery is Low (at 21V - 23V); if AC Power is available, the Battery is Charging
System = Controller’s Status
BLINKING (and second LED is OFF) = Controller is OK
ON (and first LED is OFF) = Controller Failure
Keypad = Controller’s communication with all of its connected readers
Flash = Controller is sending data to one of its connected readers
Flash = Controller is receiving data from one of its connected readers
Network = Controller’s communication with the Velocity Server
ON = Transmitting an event to the Velocity Server Flash = Transmitting some other message to the Velocity Server
ON = Receiving credentials Flash = Receiving configuration or other commands
Test = Door Alarm or Controller’s Power-On Self Test
ON = A door is in an alarm state SLOW BLINKING = A door is held open too long FAST BLINKING = Controller is running its Power-On Self Test
(no second LED on this row)
Alarm = Line Fault Alarm
ON= A fault condition (Out Of Spec, Open, Short, or Noisy) exists on the supervised line input for a door
(no second LED on this row)
The meanings of these controller status LEDs in version 7.6.20 of the CCM/CCMx firmware are explained in the following table.
Table 3-6: Meanings of the Controller Status LEDs on the Mx-1-ME (as of CCMx 7.6.20)
Name and Purpose of row of status LEDs
Meaning of First LED
Meaning of Second LED
Name and Purpose of row of status LEDs
Meaning of First LED
Meaning of Second LED
AC = AC Power
ON (and second LED is OFF) = AC Power is OK
ON (and first LED is OFF) = AC Power Failure
Both LEDs BLINKING = AC Power is Low (or Mx-1-ME controller is using Power over Ethernet+)
Battery = Standby Battery
ON (and second LED is OFF) = Battery is OK
ON (and second LED is OFF) = Battery is OK
Both LEDs BLINKING = Battery is Low (at 21V - 23V); if AC Power is available, the Battery is Charging
System = Controller’s Status
Flashing (and second LED is OFF) = Controller is OK
ON (and first LED is OFF) = Controller Failure
Keypad = Controller’s communication with all of its connected readers
Flash = Controller is sending data to one of its connected readers
Flash = Controller is receiving data from one of its connected readers
Network = Controller’s communication with the Velocity Server
ON = Transmitting an event to the Velocity Server Flash = Transmitting some other message to the Velocity Server
ON = Receiving credentials Flash = Receiving configuration or other commands
Test = Door Alarm or Controller’s Power-On Self Test
During the controller’s POST: ON = Controller is running its Power-On Self Test During normal operations: ON = A door is in an alarm state Slow Blinking = A door is held open too long
(no second LED on this row)
Alarm = Line Fault Alarm
ON = A fault condition (Out Of Spec,Open, Short, or Noisy) exists on the supervised line input for a door
(no second LED on this row)
SNIB3 Status LEDs on the Mx-1-ME
This set of 6 miniature LEDs (on the Mx-1-ME controller’s main board) displays the current status of the controller’s built-in SNIB3. For information about them, see “Controller and SNIB3 LED Diagnostics”.
Internal Power Supply
The internal power supply included with the Mx-1-ME model can use either a 110 or 240VAC supply (or 100 VAC for Japan) to provide 30VDC power to the Mx-1 controller’s main board, optional expansion boards, and readers. For additional input and output devices requiring substantial power - such as electric strikes and magnetic locks, motion detectors, retinal scanners, and surveillance cameras - auxiliary power supplies often must be used.
Standby Battery
The standby battery pack included with theMx-1-ME model supplies 24VDC of backup power to the controller’s main board even if the primary power supply fails. This 7.2 Ah rechargeable sealed lead-acid battery pack is capable of supplying power to the controller board for several hours. The standby time is dependent on the connected devices.
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-1 or Mx-1-ME Controller”.
Tamper Detection
The Mx-1 controller provides a tamper detection feature. The mechanism varies depending on the type of enclosure.
For the Mx-1 model, tamper detection uses an optical tamper mechanism that indicates whether the plastic case is closed or open. When the case is opened, the Case Tamper LED (in the group of large Status LEDs) is lit, and a “door tamper” alarm is generated in Velocity.
For the Mx-1-ME model, tamper detection uses a plunger-style contact switch that indicates whether the door of the metal enclosure is closed or open. When the door is opened, the plunger is extended, and a “door tamper” alarm is generated in Velocity.
Expansion Boards for an Mx-1-ME Controller
Optional expansion boards increase the capabilities of Mx-1-ME 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.
The Mx-1 controller is packaged in a compact plastic case which does not have room for any optional expansion boards.
The Mx-1-ME controller is packaged in a traditional metal enclosure which has room for optional expansion boards. Table 3-7 provides an overview of the available expansion boards. An Mx-1-ME controller can accommodate up to 5 expansion boards, subject to the restrictions explained in this table. (The Mx-1 and Mx-1-ME controllers include the functionality of a SNIB3, so you don’t need a separate communications expansion board.)
Table 3-7 Expansion Boards for the Mx-1-ME Controller
Model #
Description
Comments
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 28VDC.
Velocity supports up to 4 of these boards in an Mx-1-ME 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 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-1-ME 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 10 days by the controller memory battery.
An MEB draws 8 mA at 5VDC.
Velocity supports only 1 memory expansion board in an Mx-1-ME 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 10 days by the controller memory battery.
An MEB draws 8 mA at 5VDC.
Velocity supports only 1 memory expansion board in an Mx-1-ME 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.
All expansion boards have the same dimensions and shipping weight:
The ribbon cable used to connect these boards to the controller’s main 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”.
Data Capacity of an Mx-1 Controller
An Mx-1 or Mx-1-ME controller includes a base amount of memory which is dedicated to storing data about credentials, events, and alarms. (This memory enables a controller to continue performing its functions even when it is temporarily unable to communicate with the Velocity server.) The data capacity of an Mx-1-ME controller can be increased by adding optional memory 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-1-ME controller in its base configuration and with various optional expansion boards configured either way.
An Mx-1-ME controller has the following replaceable parts.
Power Supply Input Fuses: 2 Amp 125 VAC/VDC fuses, part number 0451002.MRL, made by Littelfuse, Inc.
Memory Battery: Rechargeable Li-ion coin cell battery, model PD3048 by Route Jade (formerly Route JD or Korea Power Cell), 3.7 VDC, 300 mAh capacity. Dimensions: 30.0 mm diameter by 4.9 mmthick. See “Replacing the Mx-1 or Mx-1-ME Controller’s Memory Battery”.
Standby Battery (included with the Mx-1-ME model): 7.2 Ah 12V rechargeable sealed lead-acid battery, made by Hitachi Chemical Energy Technology, part# GP1272 (Two of these are wired in series to provide 24V).
