Table Of Contents:

This portion of this chapter provides information about how to set up and install certain Hirsch security devices. (Information about older devices which have been discontinued is still available in the DIGI*TRAC Systems Design & Installation Guide.)

This portion does not cover installation instructions for any devices not manufactured by Hirsch/Identiv. For installation instructions on non-Hirsch devices, refer to the installation manual for that specific product.

General Connection Rules and Procedures

When installing or working with Hirsch by Identiv controllers, line modules, or input/ output devices, follow these rules:

• Locate the controller in a safe and secure area. They are often installed in electrical rooms, telephone equipment rooms, or closets. An environmentally managed room is not required if the temperature ranges don’t exceed the controller’s specifications.

• Make sure the power is off at the main circuit breaker before installing or connecting any part of the physical access control system.

• Make sure the building’s electrical system is properly grounded. This means the building wiring should be connected to ground via a pipe embedded in the earth – not grounded to a conduit or left completely ungrounded.

• Connect power last (primary AC input lines) after all other devices have been installed, wired, and connected.

• Follow cable specifications for the controller, reader, line module, and lock installation exactly. This will minimize any related cabling problems. Major cable manufacturers make cable that meets Hirsch’s specs of common, low-voltage, noise-resistant cable.

• Cable splices can cause trouble. Fortunately, most installations should have cable runs that are short enough, or straightforward enough, to allow unspliced runs. Make sure you measure your runs and order sufficient cable for unspliced runs. If splicing is required, solder the splices together, rejoin the shielding the best you can, and restore (heat shrink) the cable insulation. Make all terminations accurately and neatly to prevent any ‘whiskers’ from shorting between lines at terminal blocks and connectors.

• Label each cable run and each individual wire. Make sure you don’t cross cables at splices or junctions. Color-coded cable makes life easier and assures straight through connections.

• Carefully lay, tie, and dress cables when they enter the controller, power systems, and reader mounting boxes. There are a number of different types of cable ties and holders with self-adhesive backing that can make your installation neat and professional.

• Always allow for service loops, especially in the reader boxes. Don’t make service loops too long in the controller cabinet, because too much cabling can get in the way when closing the door.

• Wherever possible and available, install the controllers on the building’s emergency power circuits.

Tools and Equipment

No special tools and equipment are required for installing Hirsch systems. However, installing electric locks or strikes can require unique cutters, jigs, and fixtures for steel frames or doors. If the door and frame condition on any specific job are difficult, consider subcontracting the lock work to a qualified industrial locksmith who has experience in similar situations.

Connecting the Power Supply for an Mx or Mx-1-ME Controller

This topic applies to an Mx or Mx-1-ME controller, which has a metal enclosure and an internal power supply. For an Mx-1 controller, see “Supplying Power to an Mx-1 Controller”. Locate the controller near a dedicated AC power source. A 15-Amp circuit with isolated ground is required. Make sure the building(s) and corresponding electrical system(s) are properly grounded.

The controller’s internal power supply is a dual range, auto-sensing, switching power supply, which means it senses whether the power source is 110V or 230V AC and adjusts accordingly; however they do require different harnesses, as indicated in Table 1-18. To protect the controller, a dedicated circuit breaker is recommended.

To Connect the Power Supply:

1. Remove the protective cover next to the power supply, by removing the two hex screws and washers which are attached to bolts on the bottom of the controller’s metal enclosure. The terminal block for the controller’s power is revealed:

Open

2. Remove the lower center knock-out from the back or bottom (as required) of the controller enclosure, and install the power conduit to it. Examine the connector leading from the terminal block into the power supply. The color of the connector indicates the voltage range for which this controller is configured.

Figure 1-59 shows the connections that will already be made when you remove the protective cover.

Open

3. Pull the power cable through the knock-out hole, and strip the wires.
The following figure shows the wiring scheme for the controller’s terminal block.

The typical color coding for the wiring is:

• Ground = Green

• Neutral = White (or Blue)

• Hot = Black (or Brown)

4. Attach the power wiring to the appropriate connector, and tighten the screws until secure. Spade lugs or ring tongues are recommended.
5. Replace the protective cover.

Connecting Wires to the Controller Boards

Connecting wires to a controller board is accomplished by attaching the appropriate wires to the correct terminal blocks. Terminal blocks located on expansion boards, ScramblePads, and MATCHs are removable, while those located on the controller board itself are not. For instructions on wiring a specific controller, refer to “Wiring to the Controller”.

To Connect Wires to Terminal Blocks on the Controller Board:

1. Punch out the knockout(s) through which you plan to route the wires. Primary AC power cables are typically brought in through the bottom or lower back of the enclosure; all other cables (including low voltage power runs) are brought in from the top or sides. Those other cables must be separated from the AC power input wires and the standby battery pack’s wires by at least 0.25 inches.

2. Route the wires in their conduit or sleeve through the knockout hole. The wire/cable should always be protected; don’t route a bare cable through the knockout hole.

3. Loosen the screws on each terminal block you plan to use.

4. Remove insulation from the end of the wire and insert the specified wires into the green connectors, as shown in Figure 1-61, “Connecting Wires to the Connector Slots”.

• If this is a ScramblePad or MATCH terminal, connect four wires and the shield. ScramblePad/MATCH input connectors have five slots available: G (Ground), +(Plus Voltage), A (Data A), B (Data B), and S (Shield). Always observe polarity.

• If this is a line module terminal, connect two wires and the shield. Input connectors,such as from the DTLM, have three possible slots available marked HI, LO, and S. Always observe polarity: HI must go to HI; LO must go to LO. The shield connects to the S terminal of the controller but floats at the line module.

• If this is an output line, connect two wires. Output relays, which control electric strikes, magnetic locks, or audible alarms, have three possible slots available marked NO (Normally Open), C (common), and NC (Normally Closed). Connect one wire to the common slot and the other to either the NO or NC slot, depending on whether the device’s state is normally open or normally closed.

For more information about which wires to connect, refer to the installation instructions for the specific device.

5. Tighten the screws until the wire is securely fastened in the slot.
6. Repeat this process for each wire you need to connect.

Connecting Expansion Boards

The capabilities of an Mx or Mx-1-ME controller can be expanded using the many expansion boards designed for use with them. (The Mx-1’s compact plastic case does not have room for any expansion boards.)
All expansion boards are mounted on the left side of the controller enclosure. If more than one board is installed, use the supplied standoffs to stack them. You may stack up to five expansion boards in each enclosure.
To install the board, you must perform these steps:

1. Configure the expansion board by setting jumpers and DIP switches.

2. Remove the power from the controller.

3. Mount the board in the controller’s enclosure.

4. If this is an AEB8, REB8, RREB, SNIB2, or SNIB3 board, connect the board to its assigned inputs/outputs. If a SNIB2 or SNIB3 board is included, make sure it is mounted on top.

5. Restore power to the controller.

Mounting and Connecting Expansion Boards to the Controller

Because of the space limitation, make sure you connect an expansion board to the EBIC5 cable before you mount the board in the box.
To mount and connect an expansion board:

1. Turn all system power off, remove connectors to the standby battery, and then remove
   connectors to the AC power.

2. Configure the board by setting jumpers and DIP switches.

3. Connect the first (bottom) expansion board to one end of the EBIC cable, as shown in Figure 1-63. The first expansion board is the one that mounts to the left inside enclosure wall. Each board is shipped with its own EBIC5 Expansion Board Interface Cable. The EBIC5 connects up to five boards. If an acceptable cable is already in your system, save the new cable as a spare.

4. Mount the bottom board to the left inside of the controller’s enclosure wall. Use standoffs to secure the board to the studs mounted on the enclosure, as shown here.

5. Connect the second board to the second EBIC5 cable connector.
6. Use the standoffs to connect the second expansion board to the first board, as shown in Figure 1-62.
7. Follow the procedure in the preceding steps until all the expansion boards are mounted. The topmost (last) board is mounted to the controller with screws rather than standoffs.
8. Connect the other end of the cable into the connector on the upper left side of the controller board, as shown in Figure 1-63.

If a SNIB2 or SNIB3 expansion board is included in the stack, this should be the last (topmost) board installed. For detailed expansion board setup instructions, refer to the specific expansion board later in this chapter.

Connecting Wires to Expansion Boards

If you are installing an AEB8, REB8, RREB, SNIB2, or SNIB3 board, you must also connect the board to its assigned input/output wires. Unlike the controller board, expansion boards use terminal blocks that detach from the board; otherwise, these are similar to the controller board’s terminal blocks as to how wires are connected.
To Connect Wires to the Expansion Board Connector Blocks:

1. Turn all system power off, remove connectors to the standby battery, and then remove connectors to the AC power.

2. Punch out the knockout in the controller enclosure where you plan to route the wires. Either route these wires through the same opening used for controller board connections, or knock out a new opening for wires going to the expansion boards.

3. Route the wires through the opening.

4. Loosen the screws on each connector plug you will be using.

5. Remove (strip) insulation from the wire and connect the specified wires into the green connectors at the required slots, as described in Step 4 in section “Connecting Wires to the Controller Boards”.

6. Tighten the screws until the wire is securely fastened in the slot.

7. Push the green connector into the appropriate socket until it locks into place. The connector and socket are designed so there is only be one way to plug it in.

8. Repeat this procedure for each wire you need to connect.

Controller Installation

This section provides general information about installing Mx series controllers.

Controller Set Up

Mx controllers can be ordered with either SNIB2 or SNIB3 functionality.

• SNIB2 functionality is provided by a daughterboard on the main board, with associated DIP switches that must be configured before installation. For information about setting those DIP switches, refer to “Configuring the Integrated SNIB2”.

• SNIB3 functionality is provided by the SNIB3 expansion board. For information about setting its DIP switches, refer to “Setting the DIP Switches on a SNIB3”.

Mx-1 and Mx-1-ME controllers have integrated SNIB3 capability, with associated DIP switches that must be configured before installation. For information about setting those DIP switches, refer to “Configuring the Built-In SNIB3”.

Mounting an Mx or Mx-1-ME Controller

The Mx-1 controller is packaged in a compact plastic case. Its light weight and small size provides flexibility when deciding where to install it. The Mx and Mx-1-ME controllers are packaged in a traditional metal enclosure.
To Mount an Mx or Mx-1-ME Controller:

1. If it makes the job easier, remove the controller door by lifting it straight up off its hinges.

2. Punch out the knockouts needed for the conduits and cables. In most installations the top entry knockouts are used for conduit and cable installation. Side entry knockouts may be more convenient for expansion boards. Bottom or back knockouts are recommended for power cabling. For an illustration of this principle, see Figure 2-3, “Cable Inlets of the Mx Controller’s Enclosure”, in section “Separation of Circuits”.

3. Use the three keyhole mounting holes along the top of the controller cabinet to hang the controller. Holes are 4¾ inches (12cm) apart.

4. Because the controller cabinet is too narrow to mount on a pair of wall studs, use the center keyhole to catch a stud. Use molly bolts or similar hardware in the other two keyholes to secure the cabinet to the wall. Use the bottom mounting holes for further mounting security.

Wiring to the Controller

This section provides general information about wiring components to an Mx series controller.

• For more information about wiring various components to an Mx controller, see the Mx Quick Installation Guide sticker on the inside of the controller enclosure’s door, Figure 2-2, and “Separation of Circuits”.

• For more information about wiring various components to an Mx-1 controller, see the Mx-1 Quick Installation Guide provided with the controller, Figure 3-2, and “Separation of Circuits”.

• For more information about wiring various components to an Mx-1-ME controller, see the Mx-1-ME Quick Installation Guide sticker on the inside of the controller enclosure’s door, Figure 3-2, “Separation of Circuits”.

During operation, the Status LEDs that reside on the Mx and Mx-1-ME controller boards can prove useful in diagnosing problems that may occur. For more information, see “Controller Status LEDs on the Mx-1-ME”.

For the Mx-1 controller, see “Status LEDs on the Mx-1”.

Connecting Line Module Inputs

The typical line module input features a connection between a Door Contact or Alarm Sensor, an RQE button, a line tamper, and the Controller. The Controller uses a line supervision module device called a line module to supervise the input circuit. It should be located as close to the door contact or alarm sensor as possible.

• The DIGI*TRAC Line Module (DTLM) uses terminal blocks for connections.

• The Miniature Embedded Line Module (MELM) uses flying leads. The MELM is normally small enough to fit inside the monitored device.

To Connect Line Module Inputs to the Controller’s Line Module Input Terminals:

1. Turn all system power off, remove connectors to the standby battery, and then remove connectors to the AC power.

2. Run the HI, LO, and Shield wire from the Line Module to the Controller.

3. Punch out the knockout(s) in the enclosure through which you plan to route the wires. Typically cables are brought in from the top.

4. Route the wires through the knockout hole.

5. Loosen the screws on each connector block you plan to use.

6. Remove excess insulation from the wire and insert the specified wires into the green
connectors at the required slots, as shown in Figure 1-61.

7. Connect the HI, LO, and shield wires at the controller.

8. Connect the HI and LO wires at the line module. Make sure you observe polarity: HI must go to HI; LO must go to LO.

The line module connected to an input terminal block on the Controller is automatically assigned the door ID to which it is connected. For example, if a line module is connected to the Door 1 terminal block, it is associated with the ScramblePad/MATCH assigned an ID of 1 or 9; a line module connected to Door 2 is associated with the ScramblePad/ MATCH assigned ID 2 or 10.

The ID of a ScramblePad/MATCH is not associated with the terminal block to which it’s connected; IDs for ScramblePads/MATCHs are assigned by their DIP switches, and are independent of their physical connection to the Controller board. For example, a ScramblePad assigned an ID of 3 on an M2 Controller can be connected to the Door 2 terminal block and still control the relay for Door 3. However, connecting the proper ScramblePad/ MATCH to the same group of Door Terminals as the associated line module input makes troubleshooting much easier.

For more about installing and wiring Line Modules, refer to “Line Module Installation”.

Connecting Outputs

The typical output requires a connection between an output device (such as a door lock/strike) and an output relay on the controller board. An example of such a connection is shown in this figure.

To Connect Outputs to the Controller:

1. Turn all system power off, remove connectors to the standby battery, and then remove connectors to the AC power.

2. Run the control wires (N.O. or N.C. and Common) from the Output device to the Controller.

3. Punch out the appropriate knockout(s) in the enclosure to route the wires. Typically, output cables are brought in from the top.

4. Route the wires through the knockout hole.

5. Loosen the screws on each terminal block to be used.

6. Remove excess insulation from the wire and insert the specified wires into the green connectors at the required slots, as shown in Figure 1-61 in section “Connecting Expansion Boards”.

7. Connect the two wires. N.O. connects to N.O., N.C. to N.C., and C to C. Never connect to both NO and NC. An output device is either Normally Open or Normally Closed, but not both.

To determine which set of contacts to connect to (N.O. or N.C.), refer to the device’s installation manual. The choice is usually determined by the type of lock it is.

8. Install MOV suppression at the lock end. If this is a DC lock, you can use a diode instead. Use a 1A, 400V diode.
Many locks come with suppression included. Make sure your lock does not have built-in suppression before adding an MOV or diode to the circuit.

The terminal block to which the device is connected determines the device’s ID assignment. For example, if an electric strike is connected to Door 2, it is associated with ID 2.
If connected to Door 1, it is associated with ID 1.

Connecting ScramblePad and MATCH Interfaces

The traditional MATCH input on an Mx controller features a connection between a ScramblePad keypad or MATCH Interface and the controller. An example is shown in Figure 1-67.

To Connect ScramblePad/MATCH Interfaces to an Mx Controller:

1. Turn all system power off, remove connectors to the standby battery, and then remove connectors to the AC power.

2. Run the black, red, green, white, and shielded wires from the DIGI*TRAC connectors on the back of the ScramblePad or MATCH (MRIA or MRIB) to the corresponding terminals on the Mx Controller’s MATCH terminal blocks.
   Terminals are color-coded as shown in Table 1-19:

3. Punch out the knockout(s) in the Controller enclosure to route the wires. Typically ScramblePad/MATCH cables are pulled in from the top.

4. Route the wires through the knockout hole.
5. Loosen the screws on each connector block to be used.
6. Remove excess insulation from the wire and insert the specified wires into the green connectors at the required slots, as shown in Figure 1-61 in section “Connecting Expansion Boards”.
7. Connect the five wires to the appropriate ScramblePad/MATCH terminal blocks: G (Ground), + (Plus Voltage), A (Data A), B (Data B), and S (Shield). Always observe polarity.

For more about connecting to the ScramblePad, refer to “ScramblePad Installation”. For more about connecting to the MATCH, refer to “MATCH Interface Installation”.

The ID of a ScramblePad/MATCH is not associated with the terminal block to which it’s connected; IDs for ScramblePads/MATCHs are assigned by their DIP switches and are independent of their physical connection to the Controller board. For example, a ScramblePad assigned an ID of 3 on an M2 Controller can be connected to the DOOR 2 terminal block and still control the relay for DOOR 3. However, connecting the appropriate ScramblePad/ MATCH to its associated line module input makes troubleshooting much easier.
If two ScramblePads are installed at the same door – one for entry and the other for exit – they can share the same terminal block connection; however, the ScramblePads must have different IDs. The Controller’s firmware recognizes that IDs 1-8 are for entry, and IDs 9-16 are for exit.

Resetting the Controller

In addition to the connectors and LEDs on the controller board, there is also a reset button.

• On an Mx controller, the Reset button is located at the lower left corner of the main board.

• On an Mx-1 controller, the Reset button is located near the top along the left side of the main board (as shown in Figure 3-2 in section “Components of the Mx-1 Controller”).

• Because the main board of an Mx-1-ME controller is rotated 90 degrees counter clockwise (as shown in Figure 3-1 in section “Components of the Mx-1 Controller”), its Reset button is located near the left along the bottom side of the main board.
  This button performs three types of reset, depending on how long you hold down the button, as shown in Table 1-20 below.

The normal procedure for using the reset button is:

• 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.

• 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. Only do this as a last resort.

• You can also use this option on a new system. Many installers will perform a cold start before they begin programming a new system. For more about controller cold starts, refer to “Hardware Cold Start Procedure”.

Upgrading the CCM

On DIGI*TRAC controllers, the Command and Control Module (CCM) is easily removed and replaced. The upgrade procedure required for a CCM varies according to its version number. To determine the version number of the current CCM on this controller:

• If there is a firmware version label on the CCM, it can only show the version that was originally installed. To determine the currently installed version of the CCM firmware on a controller, right-click on that controller in the system tree of the Administration module in Velocity’s main window, and select Properties from the pop-up menu. The CCM Firmware version is displayed in the Firmware Revision
  section on the General tab of the resulting Controller Properties dialog:

• Specify the Date, Time, Version Number printout by issuing Command 88*1 in the Diagnostic Window.

Preparing For Update

Before removing and replacing the CCM, you must first print out all setups, ACBs, and Codes so that you’ll have a complete blueprint of the controller’s configuration. To do this:

1. If you don’t have a printer attached to the controller, obtain an 80-column dot-matrix parallel printer and plug it into the printer parallel connector on the side of the cabinet.

2. Enter programming mode at a ScramblePad connected to this controller. Enter these commands:

After the update, you should request the same printouts so you can compare the two. Because of electrical charges and computer chips, it’s always possible that your configuration will change unexpectedly. These printouts are your template, enabling you to reconfigure the controller, if required, and restore it.

Removing and Replacing the CCM

After you’ve documented the configuration, it’s time to change the CCM. Most of you will have to replace the old CCMs (V6.x) on your Hirsch controller boards with the new V7.0 CCMs.

To upgrade your CCM to V7.0:

1. Ground yourself by touching the controller enclosure or power supply to remove any potential static electricity.

2. Turn all controller system power off by removing connectors for both AC power and the standby battery.
a. Disconnect the DC battery.

b. Disconnect the main power to the controller.

c. Remove the AC fuse located on the power supply in the lower left corner of the enclosure.

3. Locate the CCM.

The CCM is a separate daughter board like the two shown in these M1N and M2 examples:

4. Carefully remove the old CCM.
a. Remove the screws anchoring the CCM circuit board.
b. Grab the CCM circuit board by the edges. Pull it up and away from the controller board.
Normally you should be able to perform this operation with your fingers.

5. Find the RAM memory chips which are located, in most cases, just to the right of the CCM socket on the controller board.

• If the memory chip is soldered, continue with step 6. The new memory chips onboard the new CCM will assume the duties of the old chips.

• If the memory chip is not soldered, remove it.

6. Install the new CCM daughterboard.

7. Reconnect the AC power then the standby DC battery.
The LEDs on the controller board alternate ON and OFF in different patterns while the controller performs a startup and self-test procedure. After the startup has finished, the lights should appear in their normal pattern. Refer to “Troubleshooting” for more information.
The line printer will print out some information including a header block showing the new CCM’s version number.

8. Print out a new list of configuration values and compare them to the old values.
Reprogram any functions that require it.

9.You’re now finished. For information about troubleshooting potential problems with CCM updating, refer to “DIGI*TRAC Troubleshooting Guide”.

Expansion Board Installation

Set up and installation for each of the expansion boards available for an Mx series controller is explained on the following pages.

Memory Expansion Boards Installation

The MEB/CB64 and MEB/CB128 boards provide an Mx or Mx-1-ME controller with enhanced capacity to store events and codes.

Memory Board Setups

Memory expansion boards do not require any setup before installing.

Memory Board Mounting & Wiring

To install any of the memory expansion boards:

1. Turn all system power off and remove connectors for both AC power and the standby battery.

2. Install the board on the supplied standoffs and connect the EBIC cable, as described in “Connecting Expansion Boards”.

Because a memory board only communicates with the controller board, it has no inputs or outputs other than the EBIC cable. After a Memory Expansion Board (MEB) has been installed, removing it will instantly delete all codes or logged history records. Furthermore, a cold restart will be required, which will erase all additional information in memory and require complete system reprogramming or restoration from a backup.

Alarm Expansion Board (AEB8) Installation

The AEB8 is an 8-input Alarm Expansion board where each input is supervised like the inputs on the Controller Board.
A Line Module is required for each input. For more about the Line Modules, refer to “Line Module Installation”.

AEB8 Setup

The AEB8 has four jumper positions in the middle of the board which control board addressing:

AEB8 Mounting

To install the AEB8 expansion board(s):

1. Turn all system power off, remove connectors to the standby battery, then remove connectors to the AC power.

2. Install the board on the supplied standoffs and connect the EBIC5 cable as described in “Connecting Expansion Boards”.

3. If you are installing two or more AEB8s, it is recommended that you install the AEB8 set to J1 on top of the AEB8 set to J2 and so on.

4. After each board is installed, connect the appropriate EBIC5 connector.

AEB8 Wiring

To connect inputs to this board:

1. Turn all system power off, remove connectors to the standby battery, then remove connectors to the AC power.

2. Punch out the knockout in the enclosure where you plan to route the wires. Either route these wires through the same opening you’re using for controller board connections, or knock out a new opening for wires going to the expansion boards.

3. Route the wires through the opening or knockout.

4. If it makes wiring easier, detach each green connector from the board as you need it.

5. Loosen the screws on each connector plug you will be using.

6. Remove insulation from the wire and connect the alarm wire to the designated pin on the green connector. If the device goes low to signal an alarm, connect the wire to the LO pin on the green connector. If the device goes high to signal an alarm, connect the wire to the HI pin on the green connector. For more about this, refer to “Connecting Wires to the Controller Boards”.
   If you need to, connect the shielded wire to the S pin on the green connector.

7. Tighten the screws until the wire is securely fastened in the slot.

8. Push the green connector into the appropriate socket until it locks into place. The connector and socket are keyed, so there is only one way to plug it in.

9. Repeat this procedure for each wire you need to connect.

RS-485 Readers Expansion Board (RREB) Installation

When installing an RREB, you will typically also be installing a SNIB3 (unless one was previously installed in your controller) as part of upgrading your traditional Velocity system to a FICAM-capable solution. Here is the general procedure for installing an RREB and a SNIB3.

1. Power down the controller.
   a. Disconnect the battery backup power from the controller.
   b. Disconnect the AC power cables to the controller.

2. If this is an existing controller which still has a SNIB or SNIB2 board installed, remove it.

3. If this is an existing controller which is wired to traditional readers that are being upgraded, disconnect the wires from the MATCH and/or Wiegand terminals (on the controller's main board).

4. If you are upgrading an existing system, there might be enough slack in the wire runs that you can reuse the existing wires. Otherwise, run the necessary wires from thenew readers to the controller.

5. Connect the appropriate wires to the male end of the RS-485 connectors, as shown in “Example Wiring Diagram for an RREB”. Here is a close-up diagram of an RS-485 connector:

6. Install the RREB on the supplied standoffs, and attach it to the next-to-last connector on the EBIC5 ribbon cable. When an Mx-2/4/8-S3OB controller is used, attach the RREB to the last connector on the EBIC5 ribbon cable. If you need more details, see “Connecting Expansion Boards”.

7. Plug the wired male end of each RS-485 connector that is used into the female end of the correct door’s port on the RREB.

8. Check whether your SNIB3 is a current version which includes surge protection, or whether it is the initial version (sold only to a few US federal government agencies) which did not include surge protection.

When using the initial version of the SNIB3 board (which has a serial number of the form SNIB3-S-nnnnn), surge protection must be provided for the master SNIB3 in each chain of connected controllers, using the Sankosha Guardian Net LAN-CAT5e-P+ surge protection device. For details, see “Providing Surge Protection for a Master SNIB3”.

9. Connect the 8-wire data cable between the RREB and the SNIB3, as shown in the following diagram.

10. Install the SNIB3 on the supplied standoffs, and attach it to the last connector on the EBIC5 ribbon cable, so it is the topmost board on this controller’s stack of expansion boards.

11. Route the incoming Ethernet cable through a knockout hole in the controller’s cabinet and connect it to the RJ-45 jack on the SNIB3 board (which is colored blue on the previous diagram).

12. Restore power to the controller.
a. Reconnect the AC power cables to the controller.
b. Reconnect the battery backup power to the controller.

13. At the Velocity host, use Velocity to configure the SNIB3, as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”.

Relay Expansion Board (REB8) Installation

To expand the output relay capacity of the controller, install the Relay Expansion Board (REB8). This board provides 8 additional 2-Amp (at 24VDC) Form C relay outputs.

REB8 Setup

The REB8 provides a set of jumpers (J1 through J8) to configure the address range assigned to these additional relays. The jumper is configured in this way:

Amongst other things, these jumpers can be used for elevator control - where each address corresponds to an individual floor. Jumpers J6 through J8 specify virtual relays.

The REB8 is also equipped with a master relay override DIP Switch. This switch can override all relays to either the ON or OFF positions.

REB8 Mounting

To install the REB8 expansion board:

1. Turn all system power off, remove connectors to the standby battery, then remove connectors to the AC power.

2. Install the board on the supplied standoffs and connect the EBIC5 cable as described in “Connecting Expansion Boards”.

REB8 Wiring

To connect outputs to this board:

1. Turn all system power off, remove connectors to the standby battery, then remove connectors to the AC power.

2. Punch out the knockout in the enclosure where you plan to route the wires. Either route these wires through the same opening you’re using for controller board connections, or knock out a new opening for wires going to the expansion boards.

3. Route the wires through the opening or knockout. If it makes wiring easier, detach each green connector from the board as you need it.

4. Loosen the screws on each connector plug you will be using.

5. Remove insulation from the wire and connect the specified wires into the green connectors at the required slots as described in “Connecting Wires to the Controller Boards”.

6. Tighten the screws until the wire is securely fastened in the slot.

7. If you detached the green connectors from the board in Step 3, push the connector into the appropriate socket until it locks into place, as shown in Figure 1-72. The connector and socket are keyed, so there is only one way to plug it in.

8. Repeat this procedure for each wire you need to connect.

Secure Network Interface Board (SNIB2 or SNIB3) Installation

When installed, the SNIB2 or SNIB3 expansion board enables an Mx series controller to be programmed, monitored, and controlled from a properly-configured IBM-compatible host PC running the Velocity software. Communication is secured by Hirsch’s proprietary Hirsch Encrypted Standard (HES) protocol SCRAMBLE*NET network.

• An optically isolated RS-232 port is provided on the original SNIB and the SNIB2.

• An optically isolated RS-485 port (required for multi-drop or long hardwired connections) is provided on the original SNIB, the SNIB2, and the SNIB3.

• An RJ-45 Ethernet port (which requires a host-to-master controller TCP/IP connection) is provided on the SNIB2 and the SNIB3.

The Mx controller can be ordered with either SNIB2 or SNIB3 functionality.

• SNIB2 functionality is provided by a daughterboard on the main board, as shown in Figure 2-2 in section “MX Controller Main Board”.

• SNIB3 functionality is provided by the SNIB3 expansion board.
  You can upgrade an Mx controller which has the SNIB2 daughterboard to use a SNIB3 expansion board; for details, see “Preparing an Mx Controller with a SNIB2 to Use a SNIB3” .
  The Mx-1 and Mx-1-ME controller’s main board includes SNIB3 capability.
  The following subsections provide installation instructions for the SNIB2 “Secure Network Interface Board (SNIB2 or SNIB3) Installation” and the SNIB3 “Installing and Configuring the SNIB3” .

Installing the SNIB2

This section includes setup and installation instructions for the SNIB2.

To install the SNIB2:

1. If necessary, download CCM 7.3.08 or later firmware to the required controllers.

For instructions about doing this, refer to “Firmware Updates > Updating CCM Firmware” in the main Velocity help.

2. Make sure each controller in the sequence shows the CCM version as 7.3.08 or later, and the BIOS as Version 7.2.19 or later.

If these version numbers do not appear, replace the controller’s CCM.

3. Remove the original SNIBs from each required controller.

4. Run the required network cable to the controller(s) with the master SNIB2s.

The Ethernet cable you are connecting to each master SNIB2 should be connected to the Velocity host through a hub or switch.
5. Run RS-485 cable downstream from the master SNIB2.

The run between the master SNIB2 and the second SNIB2 should be wired according to the instructions in “SNIB2 Cabling”.

6. Set the DIP switches on each SNIB2, which vary depending on whether it is the master, one in the middle, or the last one.

In general, use the settings shown in the following tables.

Refer to “Setting Up the SNIB2” for more configuration options.

7. Install the new SNIB2s into their controllers. For detailed instructions, see “SNIB2 Mounting”.

8. Plug the RJ-45 connector from the cable into the Ethernet connector on the SNIB2.

9. Connect the RS-485 cables to their respective SNIB2.

10. Reconnect and power up the controllers.

11. At the host, open Velocity and configure the new SNIB2s.

For more about this, refer to the Velocity online help.

SNIB2 Mounting

To mount the SNIB2 expansion board:

1.Turn all system power off: remove the connector for the standby battery, and then disconnect the AC power connector or the power supply fuse.

2.Install the new SNIB2 board into the upper left corner of the enclosure using the supplied screws. If there are additional expansion boards to install, install them first using the supplied standoffs. Install the SNIB2 board last so that it is at the top of the stack, as shown in Figure 1-73. (This enables you to wire the board, configure its DIP switches, view the status LEDs, and more easily access the Ethernet connector.)

3. Connect the EBIC5 connector, as described in “Connecting Expansion Boards”.
4. Reconnect the AC power connector (or power supply fuse), then reconnect the standby battery connector. The controller board’s yellow test LED should light; the other lights go through a start up sequence. When the sequence is complete, the yellow test LED goes out and the other lights stabilize.
5. If required, connect an RJ-45 network cable to the SNIB2 Ethernet connector.

SNIB2 Cabling

The cable linking the first controller (master) to the second (subordinate) in a multidropped RS-485 series must crossover the RX± and TX± wires in this manner:

If more than two controllers are connected in the series, the wiring would look like this:

At 9600 baud, the maximum allowed cable run between controllers is shown in the following table:

In general, communications become less robust as baud rates increase, wire gauge decreases, and distances increase. For this reason, it may not be possible to implement the higher baud rates supported by the SNIB2 if you have long wire runs or small wire gauges.

Higher baud rates are also more dependent on the number of twists per foot, so capacitance specifications must be strictly adhered to: total wire run per port is not to exceed acceptable capacitance of 11-17 pf and a total of 100,000 pf.

Setting Up the SNIB2

Switch Bank 1 (SW1)

The SNIB2 includes three DIP switch banks. The first bank (SW1) and second bank (SW2) have four DIP switches each. The third bank (SW3) possesses eight DIP switches.

SNIB2s can be used throughout a multidrop run; however, you must specify whether a specific SNIB2 is connected to a controller that is in the beginning, middle, or at the end of a run.

To do this, set S1-S4 on switch bank SW1 to all ON or all OFF in this way:

Switch Bank 2 (SW2)

The second switch bank at SW2 has 4 switches which configure such properties as the type of XNET protocol you are using, and the SNIB2’s location in the multidrop run.

Switch Bank 3 (SW3)

Switch bank SW3 is used to specify the SNIB2 speed (S1-S2) and the SNIB2 address (S3-S8). DIP switch settings for this are:

This controls the baud rate for the RS-485 multi-drop line and the RS-232 connection. 57,600 and 115,200 bps are only available if your RS-485 cables are made from Cat5/Cat6 data grade wire. These speeds are not recommended for installations using:

• RS-232 connections to host

• 18-gauge to 22-gauge shielded twisted-pair cable

• NET*MUX4s

• Mixed SNIBs/SNIB2s

Baud rates only apply to the SNIB2’s RS-485 and RS-232 ports. The SNIB2’s Ethernet port is used for host-to-controller connections and runs at 10/100 BaseT speeds. All SNIBs/SNIB2s in an RS-485 multi-drop sequence must be set to the same speed, and if connected to a host PC using RS-232 direct connection, the same speed must also be used. For example, if one SNIB2 in the sequence is set to 9600, all other SNIBs and SNIB2s (and the RS-232 host connection, if used) must be set to the same baud rate.

The remaining DIP switches on SW3 set the SNIB2’s address:

SNIB2 Network Configuration Options

The SNIB2’s Ethernet port provides high-speed TCP/IP communication over an Ethernet network between the host computer and the controller.

In a multiple controller sequence, the configuration can look like this example:

For more information, see “SNIB2 Cabling”. This enables communication between the controller with the master SNIB2 and host PC at 10/100BaseT. Speeds between the master SNIB2 and other connected downstream SNIB2s range up to 115200 bps when using Cat5/Cat6 cable. Speeds between a master
SNIB2 and downstream SNIBs are limited by the top speed of the older SNIBs (38400 bps).

Higher baud rates are also more dependent on the number of twists per foot, so capacitance specifications must be strictly followed: total wire run per port is not to exceed acceptable capacitance of 11-17 pf and a total of 100,000 pf.

Before the Velocity server can communicate over Ethernet with a SNIB2, you must first configure the SNIB2 through Velocity. For more about this, refer to “Configuring a Master SNIB2 on the Same Subnet” .

Whenever an Ethernet connection is employed between the host and the SNIB2, Velocity views the SNIB2 as an XNET port because the SNIB2 includes XBox functionality. The host communicates with the Ethernet-connected SNIB2 using AES-encrypted XNET 2.

Controller-to-controller speeds range from 9600 to 115200 bps. For each string of controllers, the first (master) SNIB2 with the Ethernet connection must be assigned the same address as the XBox port.

When the host is connected to a SNIB2 using Ethernet, Velocity views the first (master) SNIB2 as both a controller and an XBox residing on an XNET port. Subsequent multidropped controllers in the sequence do not appear as XBox controllers.

You can also use the SNIB2 with the NET*MUX4. The NET*MUX4 consists of a single input for either RS-232 or RS-485 and four outputs to which a series of controllers or additional NET*MUX4s can be wired, as shown in the following illustration:

For more information, see “SNIB2 Cabling”. If required, you can add a second level of NET*MUX4s to create additional controller runs; however, Hirsch does not support more than two levels of NET*MUX4s.

NET*MUX4 speeds are dictated by wire gauge and distance. We recommend using Cat5/ Cat6 cable.

Deploying the SNIB2

Each master SNIB2 (Velocity port) must be assigned a unique IP address so it can communicate with Velocity on the host PC. Depending on the network location of the master SNIB2, this is accomplished in one of two ways:

• If the SNIB2 is located within the same subnet as the host PC, then you can use Velocity to assign the IP address. For more about this, refer to “Configuring a Master SNIB2 on the Same Subnet”.

• If the master SNIB2 is located outside the host PC’s subnet, you must use the SNIB2 Configuration Utility. For more about this, refer to “Configuring a Master SNIB2 in a Different Subnet”.

What is a subnet? Put simply, a subnet is any group of PCs and other devices, such as printers and scanners, connected by network cable to a network router. Anything behind the router is considered part of the subnet. Anything beyond this router is not part of the subnet.

In the preceding illustration, the master SNIB2 and controller labeled 1 is located in the same subnet as the host PC (Subnet A). This SNIB2 can therefore be configured using Velocity; however, the master SNIB2 and controller labeled 2 is located behind a different router, in a different subnet (Subnet B), and must be configured using the SNIB2 Configuration Utility.

Any number of computers and devices can be behind a single router, but for reasons of security and speed, a company network often incorporates many routers. It isn’t uncommon to find that each department within a company has its own router. Routers not only find the quickest way to ferry packets of information between two points, but also could serve as a rudimentary firewall against potential intrusion.

Configuring a Master SNIB2 on the Same Subnet

When a master SNIB2 is connected via Ethernet to the host PC sharing the same subnet, configure and assign a new IP address through the Velocity port properties dialog.

To do this:

1.Open Velocity.

2. In the System Tree pane, click and expand the DIGI*TRAC Configuration system folder, .

Three port folders are currently available: SNET, XNET, or Dial-Up.
3. Expand the XNET Port folder.
When the Velocity host is connected to a SNIB2 via Ethernet, it treats it as an XNET port.
4. Double-click Add New XNET Port in the Components pane.
The Port Properties dialog appears:

5. Click to select the TCP/IP radio button.
The dialog changes to show the ‘IP Address’, ‘Port’, and ‘Max Attempts’ fields.

6. Check the XNET 2 Protocol checkbox, to indicate this port is using encrypted
XNET 2 protocol.

7. Click the Search button.
Velocity searches on the subnet for all SNIB2s that Velocity is not using.

A dialog listing all new SNIB2s appears:

Although a newly-detected SNIB2 does not possess an IP address, port number, or name, it should have a unique MAC address. To see this MAC address, drag the slide bar at the bottom of the dialog to the right. The MAC address for each SNIB2 is printed on a white label located on the left side of the SNIB2’s daughterboard. This label contains both a barcode and a six-digit number. This number is the last six digits of the MAC address.

8. From this list, double-click the SNIB2 entry you want to configure.
The SNIB Configuration dialog appears:

9. In the ‘Name’ field, enter the name you want to assign to the SNIB2.

10. In the ‘IP Address’ field, enter the IP address for the SNIB2 connected to this Velocity PC.
In version 5.95 and later, all SNIB2s have a factory default IP address in the format 10. x.y.z where the variables are supplied from a hash of the MAC address. For versions earlier than that, you must enter the required IP address.

11. In the ‘Port’ field, enter the correct port number.
All network ports possess an address used to identify the SNIB2’s physical port address. The default Velocity port is 10001.

12. Click OK. The Searching screen reappears.

13. Click OK.
The Port Properties screen reappears with the Name, IP Address, and IP Port fields populated.

14. In the ‘Max retry attempts’ field, specify the maximum number of retries this PC will attempt. Increment or decrement the value using the counter buttons.
If you get port errors, increase this number.

15. Check the ‘Enable this Port’ box if this port is currently active. Clear this box if the port is not currently active.

16. If required, click the Advanced button to access the Advanced Settings dialog to specify additional options for this port.

17. When you’re finished, click OK.
The new SNIB2 port appears in the Components pane.

Configuring a Master SNIB2 in a Different Subnet

To connect a master SNIB2 via Ethernet to a host PC residing outside the host PC’s subnet, configure and assign a new IP address for the master SNIB2 on its own subnet using the SNIB2 Configuration Utility.

To configure a master SNIB2 using the SNIB2 Configuration Utility:

1. If you haven’t already done so, install the SNIB2 Configuration Utility on a PC in the same subnet as the master SNIB2 you want to configure. To do this:
   a. Insert the Velocity CD or DVD in your PC’s optical drive, or go to the \Velocity folder.
   b. Using Windows Explorer, navigate to the \SNIB2 folder. The file SNIB2CONFIG.EXE should be located here.

2. Double-click SNIB2CONFIG.EXE.
   The SNIB2 Configuration Utility appears:

3. Select one of these radio buttons:

4. Click the Search for SNIB2 button.
The utility scans the network within the current subnet, and returns a list of all devices meeting the criterion specified by the radio button.

5. Click the ‘Devices’ pick list to display all devices currently detected by the utility, like the following example:

6. Select the correct SNIB2.

You can identify which SNIB2 you need by its MAC address (id=). The MAC address for each SNIB2 is printed on a white label located on the left side of the SNIB2’s daughterboard. This label contains both a barcode and a six-digit number. This number is the second half of the MAC address.

7. Select the Get Configuration From Device button.
A list of variables specific to this SNIB2 appear in the ‘Variable Name’ window.
The three options used for SNIB2 configuration are: Device_IP_Address, Device_Port, and Device_Hostname, as shown in the following example:

8. From the ‘Variable Name’ pick list, select Device_IP_Address.
A screen like this appears:

9. In the ‘Value’ field, enter the IP address you require for this SNIB2.
A screen like this appears:

Consult your IT or Security Administrator for the proper address.

10. From the ‘Variable Name’ pick list, select Device_Port.

11. In the ‘Value’ field, enter a port address for this SNIB2.
All network ports possess an address used to identify the SNIB2’s physical port address. The default Velocity port is 10001.

12. From the ‘Variable Name’ pick list, select Device_Hostname.

13. In the ‘Value’ field, enter a name for this SNIB2.

14. Click the Send Configuration to Device button to send the information to the SNIB2.

15. Click the Search for SNIB2 button again to verify that the SNIB2 has correctly received the information.

Make sure to write down the address, port, and host name you assigned for each SNIB2.
These values are required when you configure the SNIB2 in Velocity.

After the installer has assigned the remote master SNIB2 an IP address and port, use Velocity on the host PC to identify it to the system. To do this:

1. Create a new XNET port, as specified in Steps 1–5 of “Configuring a Master SNIB2 in a Different Subnet”.

2. The ‘Name’ field, enter the name you assigned to the SNIB2 using the SNIB2 Configuration Utility (Device_Hostname).

3. In the ‘IP Address’ field, enter the IP address you assigned to this device using the SNIB2 Configuration Utility (Device_IP_Address).

4. In the ‘Port’ field, enter the port number you assigned to this device using the utility (Device_Port). The default value is 10001.

5. Make sure the ‘Enable this Port’ box is checked.

6. Click OK.
This enables Velocity to find and monitor the remote SNIB2.

Resetting SNIB2 Encryption Keys

After Velocity creates the encryption keys required for secure Host-to-SNIB2 communication, it continues to use those keys. If for some reason you need to change these keys, there are several ways to do it.

After you have reset the encryption key to its default value (set SW2-1 to ON, recycle controller power, then reset SW2-1 to OFF), you must assign a new key so that Velocity and the master SNIB2 can talk to each other. To do this:

1. From the Velocity Administrator system tree, click and expand the DIGI*TRAC
   Configuration system folder until the master SNIB2 port you require appears.

2. Right-click on the SNIB2 port and select Properties.

The Port Properties dialog appears. The master SNIB2 Properties should look like this:

3. Check the ‘Reset encryption’ box, and click OK.
This resets and syncs the encryption key at host SNIB2.

Resetting the SNIB2 to its Factory Default Values

Starting with version 6.42 of the SNIB2 firmware, a SNIB2 board can be reset to the factory default values for its encryption keys and network settings. To reset a SNIB2 board to have an IP address based on its unique MAC address, perform the following steps:

1. Set all four DIP switches in Switch Bank 2 to ON, and set all eight DIP switches in Switch Bank 3 to OFF.

2. Cycle power to the controller containing this SNIB2 board.

3. Watch the status LEDs on the SNIB2 board, to ensure that they display the Lamp Test start up pattern, and then display the following SNIB2/CCM Synchronization pattern:

4. Turn off power to the controller.
You can then reconfigure the SNIB2 board as needed, using its DIP switches and Velocity.

Controller and SNIB2 LED Diagnostics

The SNIB2 has three pairs of LEDs that show you how the SNIB2 is communicating with the Velocity Server.

Special Light Patterns: Start Up

This consists of the following light patterns during start up.

First comes the Lamp Test.

Power-up might include the first two patterns. If you’ve just reflashed the SNIB2, the sequence starts with the ones in the box.

This pattern is followed by:

This is the SNIB2/CCM Synchronization. This pattern repeats until the CCM and SNIB2 are synchronized. This light pattern should not persist longer than four minutes if there are no memory expansion boards on the controller.

Normal Operation

This table illustrates the various light patterns displayed during normal operation for both the master and subordinate SNIB2s:

For more about the status LEDs, especially for the patterns displayed during a firmware reflash or during data trouble, refer to the SNIB2 Troubleshooting Guide included with the SNIB2.

The SNIB2 also causes certain changes to the way the controller LEDs display as shown below:

Installing and Configuring the SNIB3

This section includes installation and configuration instructions for the SNIB3.

Because the SNIB3 board is sensitive to discharges of static electricity, you must observe the normal anti-static precautions (of using grounded wrist straps and anti-static devices) when handling the board.

Providing Surge Protection for a Master SNIB3

The current version of the SNIB3 board (which has a serial number of the form SNIB3- nnnnn) includes protection against extreme power surges, such as those caused by nearby lightning strikes, which might damage the Ethernet port. This surge protection is provided on a small printed circuit board which is mounted on the underside of the communications daughterboard. The presence of the surge protection is indicated by a jumper wire on the lower back of the SNIB3’s main board:

If a SNIB3 board does not have this jumper wire, then it is the initial version (sold only to a few US federal government agencies) which did not include surge protection. When using the initial version of the SNIB3 board (which has a serial number of the form SNIB3-S-nnnnn), surge protection must be provided for the master SNIB3 in each chain of connected controllers, using the Sankosha Guardian Net LAN-CAT5e-P+ surge protection device.

The specifications for this device are shown in the following table:

To be effective, this surge protection device (hereafter referred to as the “Guardian Net SPD”) must be properly installed so it is securely grounded to the controller’s metal enclosure. If this was not already done by Identiv, you can do it by performing the following steps.

1. Make sure the controller shows its CCM/CCMx firmware version as 7.5.37 or later.
   (This information can be found in the controller’s Properties dialog within Velocity.)
   If necessary, update the CCM/CCMx firmware. For details, see the “Firmware Updates > Updating CCM Firmware” topic in the Velocity help system.

2. Power down the controller.
   a. Disconnect the battery backup power from the controller.
   b. Disconnect the AC power cables to the controller.

3. If this controller still has a SNIB or SNIB2 board installed, remove it.

4. Install the SNIB3 board using the last connection on the EBIC5 ribbon cable, so it is the topmost board on this controller’s stack of expansion boards.

5. Connect one end of the green ground wire to the underside of the Guardian Net SPD (using its ground screw), and connect the other end of the green ground wire to one of the controller’s mounting screws.

• For a small controller cabinet (used for an M2, M16, MSP, Mx-2, Mx-4, or Mx-8), see Figure 1-76.

• For a large controller cabinet (used for an M8 or M64), see Figure 1-77.

6. Connect one end of the included Cat5 STP Ethernet cable to the Ethernet connector 1 RJ-45 jack on the SNIB3 board, and connect the other end of the cable to the RJ-45 jack marked EQUIP of the Guardian Net SPD.

7. Peel the protective covering off one side of the adhesive-backed Velcro strip, and press the exposed adhesive firmly against the appropriate side of the Guardian Net SPD, as shown in either Figure 1-76 or Figure 1-77.

8. Peel the protective covering off the other side of the adhesive-backed Velcro strip, and press the exposed adhesive firmly against either the:

• inner top side of a small controller cabinet, or the

• inner left side of a large controller cabinet.

9. Route the incoming Cat5 Ethernet cable through a knockout hole in the controller's cabinet and connect it to the RJ-45 jack marked LINE of the Guardian Net SPD.

Figure 1-77: Installing a Guardian Net SPD for a SNIB3 in a Large Controller Cabinet

10. Restore power to the controller.
a. Reconnect the AC power cables to the controller.
b. Reconnect the battery backup power to the controller.

11. At the Velocity host, use Velocity to configure the SNIB3 as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”.

Installing the SNIB3 in a Controller without a SNIB or a SNIB2

The SNIB3 can be used with most DIGI*TRAC or Mx series controllers, except for the Mx-1 (which has a compact plastic case without room for any expansion boards). If you want to use a SNIB3 with an Mx controller that has a SNIB2 daughterboard, be sure to see “Preparing an Mx Controller with a SNIB2 to Use a SNIB3”.

To install the SNIB3 in a controller which does not already have a SNIB or a SNIB2, perform the following steps:

1. Make sure each controller in the sequence shows its CCM/CCMx firmware version as 7.5.37 or later. (This information can be found in the controller’s Properties dialog within Velocity.)
   If necessary, update the CCM/CCMx firmware. For details, see the “Firmware Updates > Updating CCM Firmware” topic in the Velocity help system.

2. Power down the controller.
   a. Disconnect the battery backup power from the controller.
   b. Disconnect the AC power cables to the controller.

3. Run a network cable to the controller. Make sure that:

• The network cable is in good condition and is Cat 5 at a minimum; otherwise, run new cable.

• The network cable is properly connected to the Velocity host through a hub or switch.

4. Set the DIP switches on the SNIB3 to its appropriate address and other parameters.
For details, see “Setting the DIP Switches on a SNIB3”.

5. If necessary, run RS-485 cable downstream from the master or slave SNIB3.
For details, see “RS-485 Cabling for SNIB3s”.

6. Connect the necessary cables and wires to the controller and the SNIB3, including:

• The EBIC5 ribbon cable between the SNIB3 and the controller

• The network cable into the SNIB3’s RJ-45 Ethernet 1 port

• Any RS-485 wires connecting to a downstream controller

7. Mount the SNIB3 on the expansion board standoffs and secure the screws.
For details, see “Mounting and Connecting Expansion Boards to the Controller”. Restore power to the controller.
a. Reconnect the AC power cables to the controller.
b. Reconnect the battery backup power to the controller.

8. At the Velocity host, use Velocity to configure the SNIB3 as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”.

Replacing a Controller’s SNIB or SNIB2 by a SNIB3

SNIB3s can communicate with SNIB2s, but they cannot communicate with original SNIBs. Any SNIBs existing on your security system must be replaced with SNIB2s or SNIB3s to use the faster speeds and greater encryption available with SNIB3s.

If you have an M1N controller (which has built-in SNIB functionality and does not support any expansion boards), you must replace it with a different model of controller.

If you want to use a SNIB3 with an Mx controller that has a SNIB2 daughterboard, be sure to see “Preparing an Mx Controller with a SNIB2 to Use a SNIB3”.

To replace a controller’s existing SNIB or SNIB2 board by a SNIB3, perform the following steps:

1. Make sure the controller shows its CCM/CCMx firmware version as 7.5.37 or later.
   (This information can be found in the controller’s Properties dialog within Velocity.)
   If necessary, update the CCM/CCMx firmware. For details, see the “Firmware Updates > Updating CCM Firmware” topic in the Velocity help system.

2. Power down the controller.
   a. Disconnect the battery backup power from the controller.
   b. Disconnect the AC power cables to the controller.

3. Disconnect the cables and wires attached to the existing SNIB or SNIB2 board, including:

• The EBIC5 ribbon cable between the controller and the SNIB or SNIB2

• The network cable into the SNIB2’s RJ-45 Ethernet port

• Any RS-485 wires connecting to a downstream controller

4. Unscrew the expansion board standoff screws, and remove the existing SNIB or SNIB2 board.

5. If necessary, run a network cable to the controller. Make sure that:

• The network cable is in good condition and is Cat 5 at a minimum; otherwise, run new cable.

• The network cable is properly connected to the Velocity host through a hub or switch.

6. If necessary, run RS-485 cable downstream from the master or slave SNIB3.
For details, see “RS-485 Cabling for SNIB3s”. Note that in an RS-485 array that includes a SNIB3, the master must be a SNIB3.

7. Set the DIP switches on the SNIB3 to its appropriate address and other parameters.
For details, see “Setting the DIP Switches on a SNIB3”.

8. Connect the necessary cables and wires to the controller and the SNIB3, including:

• The EBIC5 ribbon cable between the SNIB3 and the controller

• The network cable into the SNIB3’s RJ-45 Ethernet 1 port

• Any RS-485 wires connecting to a downstream controller

9. Mount the SNIB3 on the expansion board standoffs and secure the screws.
For details, see “Mounting and Connecting Expansion Boards to the Controller”.

10. Restore power to the controller.
a. Reconnect the AC power cables to the controller.
b. Reconnect the battery backup power to the controller.

11. At the Velocity host, use Velocity to configure the SNIB3 as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”.

SNIB3 Network Configuration Options

Be aware that the SNIB3 is backwards compatible with the SNIB2, but not with the original SNIB. Each connected DIGITRAC or Mx controller must have its own SNIB2 or SNIB3 board installed. (The Mx-1 and Mx-1-ME controllers provide built-in SNIB3 functionality.)

The SNIB3 provides both an RS-485 port and a 10/100/1000BaseT RJ-45 Ethernet port, which enables you to choose the security network configuration that is most appropriate for your situation:

• If you are using only SNIB3 boards in all of your controllers, you can use either the XNET2 or the XNET3 protocol, and the downstream controllers in your security network can either be connected directly using the RJ-45 Ethernet port, or be connected to a master SNIB3 using the RS-485 port. (These options are shown in Figure 1-27, “Example Network Configurations Using Only SNIB3 Boards”).

• If you are using SNIB2 boards in some of your controllers, you cannot use the XNET3 protocol, and those controllers must be downstream slaves to a master SNIB3, connected using the RS-485 port. (This option is shown in Figure 1-28, “Example Network Configuration Using SNIB2 and SNIB3 Boards”).

• The SNIB3 also supports connections to the NET*MUX4, as explained in “Using NET*MUX4s with SNIB3s”.

Using Ethernet

The SNIB3’s RJ-45 Ethernet port provides high-speed TCP/IP communication over an Ethernet network between the Velocity host computer and the controller, using either IPv4 or IPv6. With multiple controllers, each one can have an independent communication path with a unique IP address, as shown in Figure 1-78:

After an Ethernet connection has been established between the Velocity host and the SNIB3, Velocity views the SNIB3 as an XNET3 port. By default, the host communicates with the Ethernet-connected SNIB3 using AES 256-bit encrypted XNET3. However, before the Velocity server can communicate over Ethernet with a SNIB3, the SNIB3 must be configured through Velocity, as explained in “Configuring a SNIB3”.

Using Serial RS-485

The SNIB3’s RS-485 port provides support for downstream serial connectivity, where the master of each chain must be a SNIB3 which is connected to the Velocity host using Ethernet. This master SNIB3 must be assigned the same address as the XBox port.

Velocity views the master SNIB3 as both a controller and an XBox residing on an XNET port. (Subsequent multidropped controllers in the sequence do not appear as XBox controllers.)

• If every controller has a SNIB3, the XNET3 protocol can be used.

• If any downstream controller has a SNIB2, the XNET2 protocol must be used, and the top speed is limited to 38,400 bps.

The SNIB3’s RS-485 connector enables wire runs of up to 4000 feet (1220 meters). Higher baud rates are more dependent on the number of twists per foot, so capacitance specifications must be strictly followed: total wire run per port is not to exceed acceptable capacitance of 11-17 pf and a total of 100,000 pf .

An example of connecting downstream slave controllers using serial RS-485 is shown in Figure 1-79:

RS-485 Cabling for SNIB3s

As noted in Figure 1-79, the RS-485 cable linking the first (master) controller to the second (slave) controller in a multidropped RS-485 series must cross over the RX± and TX± wires. The cable for each subsequent slave controller is wired straight through. The details of this wiring is shown in Figure 1-80:

For an RS-485 chain, the maximum total cable run (from the master SNIB3 to the last downstream SNIB2 or SNIB3) is 4,000 feet (1,220 m). Higher baud rates are more dependent on the number of twists per foot, so capacitance specifications must be strictly followed: total wire run per port is not to exceed acceptable capacitance of 11-17 pf and a total of 100,000 pf.

In general, communications become less robust as baud rates increase, wire gauge decreases, and distances increase. For this reason, it may not be possible to implement the higher baud rates supported by the SNIB3 if you have long wire runs or small wire gauges.

Using NET*MUX4s with SNIB3s

Like the SNIB2, the SNIB3 can be used with NET*MUX4s to enable a host PC running Velocity to program, monitor, and control up to 63 controllers on a port. This type of network configuration is shown in Figure 1-81:

Note that:

• The master SNIB3 is connected to the Velocity host using Ethernet.

• All of the cables leading into and out of a NET*MUX4 are crossovers, where the RX± and TX± wires must be swapped.

• Only two levels of NET*MUX4s are supported.

• Each connected controller must have its own SNIB3 board installed.
  The NET*MUX4 has a single RS-485 input and four RS-485 outputs to which a series of controllers or additional NET*MUX4s can be wired. However, the baud rate is limited to only 9600 bps.

Setting the DIP Switches on a SNIB3

Switch Bank 1 (SW1)

The SNIB3 includes three DIP switch banks. The first bank (SW1) and second bank (SW2) have four DIP switches each. The third bank (SW3) has eight DIP switches.

SNIB3s can be used throughout an RS-485 multidrop run; however, you must specify whether a specific SNIB3 is connected to a controller that is at the beginning, middle, or end of a run.

To do this, set S1-S4 on switch bank SW1 to either all ON or all OFF in this way:

Switch Bank 2 (SW2)

The second switch bank at SW2 has four switches, where S1 configures encryption properties and S4 configures the SNIB3’s location in the multidrop run. (S2 and S3 are used to reset a SNIB3 to its factory default settings.)

Switch Bank 3 (SW3)

Switch bank SW3 is used to specify the SNIB3 speed (S1-S2) and the SNIB3 address (S3-S8). The DIP switch settings for the speed are:

This controls the baud rate for the RS-485 multi-drop line. 57,600 and 115,200 bps are only available if your RS-485 cables are made from Cat5/Cat6 data grade wire. These speeds are not recommended for installations using:

• 18-gauge to 22-gauge shielded twisted-pair cable

• NET*MUX4s

Baud rates only apply to the RS-485 ports for SNIB2s and SNIB3s. The SNIB3’s Ethernet port is used for host-to-controller connections and runs at 10/100/1G BaseT speeds. All SNIB2s and SNIB3s in an RS-485 multi-drop sequence must be set to the same speed.

The remaining DIP switches (S3-S8) on SW3 set the SNIB3’s address, just like for the SNIB2:

Configuring a SNIB3

The location of a SNIB3 on your network relative to the Velocity host will determine the method you must use for configuring that SNIB3:

• If the SNIB3 is on the same subnet, then you will configure it using Velocity. See “Using Velocity to Configure a SNIB3 on the Same Subnet”.

• If the SNIB3 is on a different subnet, then you will configure it using the SNIB Configuration Tool. See “Configuring a SNIB3 on a Different Subnet”.

Overview of Network Subnets

Each SNIB3 that is connected to the network using Ethernet (instead of being a downstream controller in a serial RS-485 chain) must be assigned a unique IP address so it can communicate with the Velocity host. The method for doing that depends on the location of that SNIB3 on your network relative to the Velocity host. The determining factor is whether they are both on the same subnet.

What is a subnet? Put simply, a subnet is any group of PCs and other devices, such as printers and scanners, connected by network cable to a network server, router, or hub. Anything behind the router/hub is considered part of the subnet. Anything beyond this router/hub is not part of the subnet. This concept is illustrated in Figure 1-82.

In Figure 1-82, the SNIB3 and its attached controller labeled 1 are located in the same subnet as the host PC (Subnet A). This SNIB3 can therefore be configured using Velocity;however, the SNIB3 and controller labeled 2 are located behind a different router, in a different subnet (Subnet B), and must be configured using the SNIB Configuration Tool.

Any number of computers and devices can be behind a hub or router, but for reasons of security and speed, a company network often incorporates many network servers, hubs, and routers. It is fairly common to find that each department within a company has its own server connected to its own hub and/or router. Routers and hubs not only find the quickest way to ferry packets of information between two points, but also can serve as a rudimentary firewall against potential intrusion.

Using Velocity to Configure a SNIB3 on the Same Subnet

If a SNIB3 is on the same subnet as the Velocity host, then you will configure it using Velocity. (If the SNIB3 is on a different subnet, then you will configure it using the SNIB Configuration Tool, as explained in “Configuring a SNIB3 on a Different Subnet”).
To configure a SNIB3 which is on the same network subnet as the Velocity host:

1. If you have not yet done so, install the SNIB3 board in the controller. For details, see either:

• “Installing the SNIB3 in a Controller without a SNIB or a SNIB2”,
  or

• “Replacing a Controller’s SNIB or SNIB2 by a SNIB3”.

2. If you have not yet done so, connect the controller to the network. For guidance, see “SNIB3 Network Configuration Options”.

3. In Velocity’s Administration window, double-click the Add New XNET Port item.

The resulting Port Properties dialog varies according to whether your network is using IPv4 or IPv6 addressing. For IPv4 addressing:

For IPv6 addressing:

4. On the Port Properties dialog:
a. If necessary, for the ‘Network Type’ select either the IPv4 or the IPv6 option.
b. For the ‘Protocol’, select either the XNET2 or XNET3 option.
c. Click the Search button.

The results depend on the options you specified for the Network Type and the Protocol. Here is an example for an IPv4 network using the XNET2 protocol:

Here is an example for an IPv6 network using the XNET3 protocol:

Note that although the SNIB2 and the SNIB3 support dynamic IP addressing using the Dynamic Host Configuration Protocol (DHCP) for both IPv4 and IPv6, Identiv strongly recommends using static or reserved IP addresses. For this reason, all SNIB2s and SNIB3s that have the value of Yes in the DHCP Enabled column should be changed to have assigned fixed IP addresses before they are added to the Velocity
network.

5. To change the settings for one of the displayed ports, perform these steps:
a. Double-click on an entry in the Searching dialog’s results table.

b. In the resulting SNIB Configuration dialog, make the necessary changes.

For example:

• If you need to change the Port number from the default value of 10001, then make sure to stay within the range from 1024 to 32767. Outside of this range, SNIB3 cannot communicate with the Velocity host.

• If you plan to assign a fixed address to this port, then clear the check box for the ‘DHCP Enabled (ignored for SNIB2)’ option.

c. When you are finished, click OK to close this dialog.

6. Back in the Searching dialog, click on the appropriate row to select the desired SNIB3 board, and click OK.

Velocity starts communicating with the specified SNIB3, and its port appears in the Ports folder within the Administration window.

Configuring a SNIB3 on a Different Subnet

If a SNIB3 is on a different subnet than the Velocity host, you will configure it using the SNIB Configuration Tool. (If the SNIB3 is on the same subnet, then you will configure it using Velocity, as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”).

To configure a SNIB3 which is on a different network subnet than the Velocity host:

1.If you have not yet done so, install the SNIB3 board in the controller. For details, see either:

• “Installing the SNIB3 in a Controller without a SNIB or a SNIB2”,

or

• “Replacing a Controller’s SNIB or SNIB2 by a SNIB3”.

2. If you have not yet done so, connect the controller to the network. For guidance, see “SNIB3 Network Configuration Options”.

3. If you have not yet done so, download the SNIB Configuration Tool to a PC which you will use to configure the SNIB3:

On that PC, download the SNIBConfigTool.exe file from the Identiv website. (Use your Web browser to go to the identiv.com/support page, click the Support: Hirsch Products link, click the SNIB3 - Documents and Downloads link, and click on the link to download the SNIB Configuration Tool.)

4. Connect that PC to the same network subnet as the SNIB3 being configured.

5. Locate and double-click the SNIBConfigTool.exe file.

6. On the resulting SNIB Hunt and Configure window:

a. Select one of these options:

• All Devices in network, to search for all SNIB2s or SNIB3s on this network subnet. (If a SNIB2 or SNIB3 is currently logged on, this utility will not detect it.)

• Specific Device in network, to search for a specific SNIB2 or SNIB3 on this network subnet. If you select this option, enter a search term such as an IP address in the text field which appears after this option. (This option works for both IPv4 and IPv6.)

b. Click the Search button.
c. From the resulting list of previously-undetected SNIB2s or SNIB3s displayed in the Devices list, double-click on the entry for the desired SNIB3, so its information appears in the subsequent fields on this window.

Note that the Device_IP_Address, Device_Subnet_Mask, and Device_Default_Gateway fields are specific to IPv4. The Device_IPv6_Multicast_Address, Device_IPv6_Address, Device_IPv6_Prefix_Len, and Device_IPv6_Gateway fields are specific to IPv6.

d. Enter the values required for this SNIB3 in the relevant fields. For example:

• In the Device_Hostname field, enter the SNIB3 name that the Velocity host will use to identify this SNIB3.

• In the Device_Port field, enter the network port number for this SNIB3. If you need to change this from the default value of 10001, then make sure to stay within the range from 1024 to 32767. Outside of this range, SNIB3 cannot communicate with the Velocity host.

• Enter the necessary IP address in either the Device_IP_Address field (for IPv4) or in the Device_IPv6_Address field (for IPv6).

• If you follow our recommendation to use static or reserved IP addresses, then clear the check box for the Enable DHCP Mode option.

e. Click the Send to Device button, to send the updated values to this SNIB3.
f. Click the Search button again, to verify that the SNIB3 has correctly received the updated information.
g. Record this SNIB3’s device hostname, port number, and IP address.
You will need this information to finish configuring the SNIB3 in Velocity.
h. When you are finished, click the Close button.

After you have used the SNIB Configuration Tool to assign the device hostname, port number, and IP address to a remote SNIB3, you must use Velocity to assign that SNIB3 to a new port.

To assign a remote SNIB3 to a new port on Velocity:

1. In Velocity’s Administration window, double-click the Add New XNET Port item.

The resulting Port Properties dialog varies according to whether your network is using IPv4 or IPv6 addressing. For IPv4 addressing:

For IPv6 addressing:

2. On the Port Properties dialog:
a. If necessary, for the ‘Network Type’ select either the IPv4 or the IPv6 option.
b. For the ‘Protocol’, select either the XNET2 or XNET3 option.
c. In the ‘Name’ field, enter the value you assigned as the Device_Hostname (when using the SNIB Configuration Tool).

d. In the ‘IP address’ field, enter the value you assigned as either the Device_IP_Address or the Device_IPv6_Address (when using the SNIB Configuration Tool).
e. In the ‘IP Port’ field, enter the value you assigned as the Device_Port (when using the SNIB Configuration Tool).
f. Make sure the ‘Enable this Port’ option is checked.
g. Click OK.

Velocity should then be able to find and monitor this remote SNIB3.

Resetting SNIB3 Encryption Keys

After Velocity creates the encryption keys required for secure Host-to-SNIB3 communication, it continues to use those keys. If for some reason you need to change these keys, there are several ways to do it.

After you have reset the SNIB3’s encryption key to its default value (by setting SW2-1 to ON, recycling controller power, then resetting SW2-1 to OFF), you must perform the following steps to assign a new key:

1. In the Velocity Administration system tree, expand the DIGI*TRAC Configuration system folder until the master SNIB3 port you require appears.

2. Right-click on that SNIB3 port, and select Properties from the pop-up menu.

3. On the resulting Port Properties dialog, check the box for the ‘Reset encryption’ option, and then click OK.

This resets the encryption key at the Velocity host.

Resetting a SNIB3 to its Factory Default Values

A SNIB3 board can be reset to the factory default values for its encryption keys and network settings. To reset a SNIB3 board to have an IP address based on its unique MAC address, perform the following steps:

1. Set all four DIP switches in Switch Bank 2 to ON, and set all eight DIP switches in Switch Bank 3 to OFF.

2. Cycle power to the controller containing this SNIB3 board.

3. Watch the status LEDs on the SNIB3 board, to ensure that they display the Lamp Test start up pattern, and then display the following SNIB2/CCM Synchronization pattern:

4. Turn off power to the controller.
You can then reconfigure the SNIB3 board as needed, using its DIP switches and Velocity.

Controller and SNIB3 LED Diagnostics

The SNIB3 has three pairs of LEDs that show you how the SNIB3 is communicating with the Velocity Server.

Special Light Patterns at Startup

At startup, the following pattern may be observed:

This indicates the SNIB3/CCM Synchronization. This pattern repeats until the CCM and SNIB3 are synchronized. This light pattern should not persist longer than four minutes if there are no memory expansion boards on the controller.

Light Patterns for Normal Operations

This table illustrates the various light patterns displayed during normal operation for SNIB3s:

Like the SNIB2, the SNIB3 also causes certain changes to the way the controller LEDs display, as shown below:

For more information, see “Troubleshooting the Controller Using Status LEDs”.