Components of the Mx-1 Controller
Components of the Mx-1 Controller
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 |
|---|---|
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.
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.
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 backup battery which provides the required duration of standby power for that standard. For more information, see the table about Standby Power Requirements for Various UL Standards in section “General UL Information”. 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 24V battery pack.) 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 24V battery 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 by RS-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.
|
Buzzer | This component generates an audible alarm during certain conditions. This buzzer’s functionality has not yet been defined. |
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. Otherwise, an Mx-1 controller can communicate directly with the Velocity Server across a network using the PoE+ Ethernet connector. For more information, see “Network Configuration Options for the Built-In SNIB3”. The RS-485 cable linking the first (master) controller to the second (downstream) controller in the chain must cross over the RX± and TX± wires. The cable for each subsequent downstream controller is wired straight through. For details, see “RS-485 Cabling for SNIB3s”. |
RS-485 Controller Bus Address rotary switch | 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”.)
Only do this as a last resort. For more information, see “Resetting the Controller” . |
Door Tamper | 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 | 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. For more information, see “Connecting Expansion Boards” . |
Memory Battery | 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. For more information, see “Replacing the Mx-1 or Mx-1-ME Controller’s Memory Battery”. |
Wiegand Entry Reader terminal | 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. The maximum simultaneous current draw for this Wiegand Entry Reader terminal and the Wiegand Exit Reader terminal is 0.75 Amps. |
Wiegand Exit Reader | 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.) The door’s entry reader and optional exit reader can use different protocols. 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. The maximum simultaneous current draw for this Wiegand Exit Reader terminal and the Wiegand Entry Reader terminal is 0.75 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.) For information about this set of LEDs, see “SNIB3 Status LEDs on the Mx-1-ME”. |
Controller Status | 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.) For information about this set of LEDs, see “Controller Status LEDs on the Mx-1-ME”. |
OSDP RS-485 | 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). Because the door’s entry reader and optional exit reader can use different protocols, this terminal can be used to attach an OSDP entry reader, and the Wiegand Exit Reader terminal can be used to attach a Wiegand exit reader. |
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). For more information, see “Line Modules” and “Connecting Line Module Inputs”. |
Aux. Input terminal | This 3-pin white connector can be used for a second analog input. For more information, see “Connecting Line Module Inputs”. |
Door Relay terminal | 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.
UL has only evaluated this relay for 30VDC at 2 Amps for resistive and inductive loads. For more information, see “Connecting Outputs”. |
Aux. Relay terminal | 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.
UL has only evaluated this relay for 30VDC at 2 Amps for resistive and inductive loads. For more information, see “Connecting Outputs”. |
Wet or Dry Mode jumpers | 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.
When configuring a relay for wet mode at 24V, make sure that the connected device will not draw more than the max limit of 0.5 Amps (which equals 12 Watts), and that the device is rated for 24VDC.
When configuring a relay for wet mode at 12V, make sure that the connected device will not draw more than the max limit of 1.0 Amps (which equals 12 Watts), and that the device is rated for 12VDC.
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:
For more information, see “DIP Switches on an Mx-1 Controller” |
Ethernet / PoE+ connector | This Ethernet connector provides up to Gigabit data connectivity for secure communication with the Velocity server.
For more information, see “Supplying Power to an Mx-1 Controller”. |
Status LEDs | 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.) For information about this set of LEDs, see “Status LEDs on the Mx-1”. |
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 |
|---|---|
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:
For information about this set of LEDs, see “Status LEDs on the Mx-1”.
The Mx-1-ME model (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):
For information about this set of LEDs, see “Controller Status LEDs on the Mx-1-ME”.
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):
For information about this set of LEDs, see “SNIB3 Status LEDs on the Mx-1-ME”.
Status LEDs on the Mx-1
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
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)