Key Notes:
Remote Input Component's section includes design notes on the following devices:
ScramblePads
MATCH Reader Interface
Readers
Line Modules
RQE Devices
Door Contacts
Surveillance Cameras
Remote Output Component's section includes design notes on the following devices:
Locks/Strikes
Doors
Gates
Turnstiles
Elevators
HVAC/Lighting
Printers
Remote Input Components
This section includes design notes on the following devices:
ScramblePads
MATCH Reader Interface
Readers
Line Modules
RQE Devices
Door Contacts
Surveillance Cameras
ScramblePads
The ScramblePad can be used to:
Unlock doors
Mask alarms
Trigger relays for equipment or process control
Pull cable runs from the controller to ScramblePads for each door. Make sure you select the correct ScramblePad mounting box for the applications and conditions specific to each door. Pay special attention to the specified mounting height for the ScramblePad. If it’s not right, the ScramblePad will be difficult to use properly.
Table 1-11 shows the many types of ScramblePads that are available
Table 1-11: ScramblePad Types
The DS47L can be used in applications where an MRIB or an MRIA is used because it has the same bezel and physical tamper switch. The DS47L-SPX ScrambleProx provides a single device for card and code entry. The ScrambleProx also has a second reader port which can be used to connect a second reader to the other side of the door. This means that the ScrambleProx can be used to place dual technology on one side of the door and card access on the other side.
If you plan to use either the DS47L or the DS47L-SPX, you have several different configurations possible at the door site. Figure 1-31 through Figure 1-34 provide examples of several keypad configurations.
Figure 1-31: Possible DS47L Configurations
Figure 1-32: Possible ScrambleProx Configurations
Figure 1-33 and Figure 1-34 show the typical ScramblePad-to-Controller connections for DS47L-series ScramblePads.
Figure 1-33: Typical ScramblePad to Controller Connection
Figure 1-34: DS47L ScramblePad/DS47L-SPX ScrambleProx Connections to Controller/Reader
ScramblePad Mounting
The DS47L is ideal for normal lighting, such as interior walls and doorways. Mounting boxes for these keypads come in two main types: surface-mounted and flush-mounted.
Surface mounted boxes project from the wall on which they are mounted. Flush boxes are set into the wall so that they are flush with the wall.
Hirsch offers several varieties of each mounting box as shown in Figure 1-35. The dimensions for each of these boxes is shown in Table 1-12 in section “ScramblePad Mounting”. In addition, the Universal Mounting Kit (UMK) can be used with the MB2 and MBS2S to position the face at three different aspects: flush, semi-flush, and tilted (for handicapped).
For more information about installing mounting boxes, see “Installing the Mounting Box”. When ScramblePads must be installed on exterior walls or on gate posts, select the MB5 Exterior Mounting Box.
For exterior locations, consider one of these ScramblePad model options:
DS47L-HI
DS47L-SPX-HI
In high-ambient light conditions (which may occur indoors as well as outdoors), use the DS47L-HI or DS47L-SPX-HI. The standard ScramblePad uses Red LEDs which become unreadable in bright or direct sunlight. When ScramblePads are installed on east- or westfacing walls or gates, the display washes out in the morning or afternoon hours.
The high-intensity DS47L-HI or DS47L-SPX-HI uses the same off-white incandescent display used in commercial aircraft instrumentation. They are readable even in direct sunlight and highly reliable. The viewing restriction on the DS47L-HI or DS47L-SPX-HI is less restrictive: approximately 12° horizontally to help see the display or when installed in the MB5.
Figure 1-35 shows the ScramblePad and its available mounting boxes. For directions on mounting the ScramblePad, see “ScramblePad Installation”.
Figure 1-35: ScramblePads and Mountings
Dimension (Face): 5.75”H x 4.37”W (14.6cm x 11.11cm)
Dimension (Body): 4.5”H x 3.5”W x 2.25”D (11.43cm x 8.89cm x 5.71cm)
Shipping Weight: 2 lbs (0.9 kg)
The mounting height for each of these boxes is shown in Table 1-12 as measured from ground or floor level to the middle (centerline) of the ScramblePad in inches (and meters).
Table 1-12: Mounting Heights for ScramblePads and Mounting Boxes
Most states require strict compliance with ADA (Americans with Disabilities Act) in addition to many local and regional code requirements. Consult your local codes for exact height requirements.
Select a mounting box which provides a convenient viewing angle for personnel confined to wheelchairs. The UMK provides several angles. The MB8, MB9, and MB20 are also tiltable for easy reading. To accommodate state and federal disabilities statutes, a tilted box may prove necessary. For information about installing mounting boxes, see “Installing the Mounting Box”.
See Figure 1-83 through Figure 1-88 for close-ups of ScramblePad Mounting Box types and dimensions.
Mounting Extensions
Hirsch mounting boxes can be fitted with two extensions:
MBX – A ½- inch extension for surface-mounted boxes used with ScramblePad or bezel-mounted reader assemblies in cases where the mounting box depth is too shallow for the electronics, as with some of the ScrambleSmart products. The MBX package includes four extra long screws and is suitable for use with the MB2, MB2S, MB2SL, or UMK/MB2 (either sloped or semi-flush).
MBX-FL – A ½-inch extension for flush-mounted boxes used with ScramblePad or bezel-mounted reader assemblies in cases where the mounting box depth is too shallow for the electronics, as with some of the ScrambleSmart products. The MBXFL includes four extra long screws and is suitable for use with the MB1.
Firestops for Mounting Boxes
Many installers are concerned about fire rating for their mounting boxes, particularly the MB2. The MB2 is not fire-rated; however, the box and its contents can be made fire-resistant using a hole-plug-type firestop. The firestop restores the wall’s fire rating.
To install it, simply mount the MB2 over a firestop. Firestops are available in many sizes and shapes and can be purchased from many suppliers. You can find most firestop manufacturers listed in the Thomas Register or through its webpage www.thomasregister.com.
SPSH-1: Heated Back Cover for a DS47L ScramblePad
If you are using a DS47L ScramblePad in an environment where the temperature may drop below freezing or where condensation may be an issue, you can replace the reader’s standard back cover with the SPSH-1 heated back cover. For example, an SPSH-1 is recommended for outdoor applications (such as controlling access to a restricted parking area) in cold climates where a DS47L ScramblePad is enclosed in an MB5 mounting box and mounted on a pole.
The use of the SPSH-1 is not evaluated by UL.
The SPSH-1 draws its power from the G and the + connections of the DS47L (as shown in the following diagram), and it consumes 0.33 Amps at 28VDC.
When the DS47L is powered by a controller:
There can be only one DS47L with an SPSH-1 per door,
There can be no more than two DS47Ls with an SPSH-1 per controller, and
The maximum cabling distance between the controller and a DS47L with an
SPSH-1 is half of the values shown in Table 1-6 in section “ScramblePad/MATCH Inputs”.
If you need to have more than two DS47Ls with an SPSH-1 connected to a controller, then
MATCH Reader Interface
The MATCH Reader Interface is required by all DIGI*TRAC controllers if you plan to attach any readers, unless one of these conditions exists:
You are only using a ScramblePad without a reader.
You are using a DS47L-SPX ScrambleProx which includes both a reader and a MATCH.
You are using a DS47L-series ScramblePad which includes a MATCH and a standard 26-bit card reader.
You are only using a Wiegand card reader which is directly wired to a Wiegand terminal on an Mx series controller.
You are using keypads/readers which are wired to the RS-485 OSDP terminal on an Mx-1 or Mx-1-ME controller.
The MATCH Reader Interface enables a large number of reader technologies to communicate successfully with a DIGI*TRAC or Mx controller.
Hirsch provides three MATCH Reader Interface configurations:
MATCH2 Reader Interface Board (MRIB)
MATCH2 Reader Interface Assembly (MRIA)
DS47L-series ScramblePad with integrated MATCH
he MATCH2 replaces the older MATCH reader models. All drawings that follow apply to MATCH2 specifications.
The new MATCH2 board has fewer components than the old MATCH, but includes more functionality. The MATCH2 provides a second switch bank which can be programmed to accept a large selection of custom readers.
Figure 1-36: MATCH2 Board and Package
The MRIB consists of a printed circuit board mounted between two protective metal plates with keyhole mounting slots. The MRIA includes the MRIB which is attached to a mounting base and bezel. The bezel is the same as the one included with a ScramblePad and includes a physical tamper switch. The MRIA is designed for installation on a Hirsch mounting box. For a description of available mounting boxes, see “MRIA/MRIB Mounting”.
The MATCH is also integrated into the DS47L-series ScramblePads. These keypads can be used in much the same manner as a MATCH. But there are differences: while a DS47L ScramblePad can support one or two readers for dual entry or dual entry-card only exit, a MATCH can support two readers and two ScramblePads for dual entry and dual exit. Another and often better solution is to use DS47L ScramblePads, each with an associated reader.
The MRIB is normally located in close proximity to the readers it will connect to, as shown in Figure 1-37. The MRIB is usually installed above the ceiling line. A junction box (J-box) is often used to house and protect the board above the ceiling line. An MRIA in a Hirsch mounting box can also be used.
Figure 1-37: MATCH Location Example
Whether integrated or separate, the MATCH can supply 250mA to each reader using 5VDC. Readers which require more than 250 mA current (or other voltage levels) must always use a separate power supply. In addition, one or two ScramblePads can be connected to each MATCH. The MATCH should be located at the door or control location.
Each MATCH includes two reader connectors with 12-inch flying leads. The allowed maximum distance between the MATCH and a connected reader varies according to the reader. For example, the Hirsch CR11L Mag Stripe Card Reader can be located up to 500 feet (152 meters) from the MATCH to which it is connected. For maximum allowed distances between the MATCH and your selected reader(s), see “MATCH
Reader Installation” or refer to the literature shipped with your reader(s).
To increase the length beyond the prescribed maximum, the MATCH or attached reader must be powered locally. This eliminates the need for power from the controller and increases the allowed wire length. For more about powering a MATCH or reader, see Figure 1-110, “Powering the MATCH Locally (Schematic)”.
The dimensions and weight of the MATCH board and assembly are listed below:
Dimension (MRIA): 5.75”H x 4.5”W x 2”D (14.6cm x 11.4cm x 5.1cm)
Dimension (MRIB): 4.5”H x 3.5”W x 1.75”D (11.4cm x 8.9cm x 4.4cm)
Shipping Weight: 2 lbs (0.9 kg)
Figure 1-38 provides an example of the connections between the MATCH, the reader, the ScramblePad, and the controller:
Figure 1-38: MATCH Connections (MATCH2 Shown)
The flying lead which connects the reader to the MATCH through one of two connectors on the board must conform to the wiring standards shown in Figure 1-38.
With a DS47L-series ScramblePad, a reader can be connected at a door without using an additional MATCH. The reader connects to the DS47L (and its integrated MATCH) and the ScramblePad then connects to the controller, as shown in Figure 1-39.
Figure 1-39: Using a DS47L-Series ScramblePad Instead of a Separate MATCH
For more about setting up the MATCH and installing it, see “MATCH Reader Installation”. When installing a DIGI*TRAC MATCH Enrollment Station (DMES), locate the ScramblePad/Reader tandem close to the controller and its printer. The maximum distance allowed between the DMES and the controller can be calculated using Table 1-7 (refer to the maximums for a MATCH and ScramblePad).
For more information about Enrollment Stations, see “Enrollment Station Installation”.
MRIA/MRIB Mounting
There are four mounting boxes available for the MRIA: the MB1, MB2, MB3 and MB4. The MRIB is usually mounted in a separate J-Box using the keyhole slots (see Figure 1-38). Choose the box that fits your system requirements.
The MRIA in a Hirsch mounting box supports physical tamper monitoring.
Figure 1-40 shows the available MRIA mounting boxes. For directions on mounting the MRIA in an MB1, MB2, MB3, or MB4 mounting box, see “Installing the Mounting Box”. For instructions on mounting the MRIB, see “MATCH Interface Installation”.
Figure 1-40: Available MRIA Mounting Boxes
MATCH-Compatible Readers
Readers are a general category of access control devices that include:
Mag Stripe Card Readers (insertion and swipe)
Proximity Card Readers
Wiegand Card Readers
Biometric Readers (e.g. Hand Geometry, Retinal Scanner)
Barcode Readers
Infrared Readers
Wiegand-Compliant Keypads
When used in conjunction with the MATCH Reader Interface, most readers can communicate with Hirsch DIGI*TRAC or Mx controllers. Hirsch’s MR11LA includes an MRIA. The MR11LA consists of a CR11L magnetic stripe card reader mounted on an MRIA. The CR11L is small enough to fit within the MRIA bezel.
An example of how an MR11LA might work at a door is shown in Figure 1-41.
Figure 1-41: MR11LA Example
In addition, the DS47L family of ScramblePads includes an integrated MATCH which can support one or two readers (the D47L-SPX ScrambleProx also includes a built-in proximity reader). All other readers require the purchase of a separate MATCH and the connection of the reader to the MATCH Interface.
A complete list of ScramblePad DS47L readers with the MATCH already installed is shown in Table 1-13.
Table 1-13: DS47L ScramblePad Types
Older readers require the purchase of a separate MATCH and the connection of the reader to the MATCH Interface. Newer readers which have a Wiegand or an RS-485 OSDP interface can be connected directly to the appropriate terminals on an Mx, Mx-1, or Mx-1- ME controller.
Line Modules
Line Modules are a necessary component of the line module input circuits from the controller. In addition to providing supervision of the wiring from a controller, the line module also supports a request to exit (RQE) input and a tamper input.
Line Modules provide supervision by indicating when a circuit is shorted, opened, noisy, and/or out-of-spec. These conditions are usually considered attempts to breach the security of the system and are therefore monitored and reported on an input-by-input basis at all times for enabled inputs. The controller digitally processes the analog measurement of the circuit resistance at an effective 100 times per second rate. The circuit measures variation in conditions (±2% with the DTLM3 Line Module and ±4% with the DTLM1/2 Line
Modules) then reports any appropriate alarms upon detection.
Hirsch provides two types of line modules:
DTLM (Screw Terminals)
MELM (Flying Leads)
There is also a door contact with integral line module:
SBMS3-2707A
Each line module type is explained in this section. For detailed information about setup, mounting, and installation of line modules, see “Line Module Installation”.
DTLM
The DIGI*TRAC line module (DTLM) provides terminal block connections. It is recommended that DTLMs be limited to a single sensor per input. The DTLM is used for the RQE, Auto-Relock, Door Forced, and Door Open Too Long (DOTL) functions. There are three types of DTLM:
The DTLM1 has one input and is used for alarm applications with ±4% sensitivity.
The DTLM2 has two inputs and is used when an RQE device is required to mask the line module input and, optionally, trigger the door lock with ±4% sensitivity.
The DTLM3 has three inputs and is used in high security applications where alarm, RQE, and tamper detection are required with ±2% sensitivity.
DTLM inputs are labeled 1, 2, and 3 for simplicity in which 1 normally connects to the door contact or alarm sensor, 2 connects to the RQE, and 3 monitors a Tamper switch.
Table 1-14: DTLM Wiring
Model | Terminals & Functions | |||
---|---|---|---|---|
HI LO | INPUT 1 | INPUT 2 | INPUT 3 | |
DTLM1 | DIGI*TRAC | Alarm | ||
DTLM2 | DIGI*TRAC | Alarm | RQE | |
DTLM3 | DIGI*TRAC | Alarm | RQE | Tamper |
As shown in Figure 1-42, the default configuration for line module input circuits is normally closed. For a closed circuit, the controller instantly reports an alarm for any attempt to tamper with or cut the circuit. For a normally open circuit, the circuit cannot be monitored and tampering goes undetected. All input devices must be isolated ‘dry contact’ types. (A dry contact is a switch or relay which provides no power to the circuit.)
Figure 1-42 DTLM Wiring
Confirm the polarity of the HI / LO terminals at both ends of the DTLM cable run. HI must be linked to HI; LO must be linked to LO. Connect the shield at the controller terminal and let it float (don’t connect it) at the DTLM end.
A separate cable is required from the controller to the DTLM. ScramblePad/MATCH reader cable (2-pair stranded, twisted overall shield) and DTLM cable (1-pair stranded, twisted, overall shield) can be run together in the same conduit; however, each pair must be individually shielded.
It is recommended that the DTLM should be as close to the sensor(s) it connects as possible for optimum performance.
The dimensions and shipping weight for each DTLM is shown in Table 1-15:
Table 1-15: DTLM Dimensions
Model | Dimensions (Length x Width x Height) for each |
---|---|
DTLM1 | 2-1/8” x 1-3/8” x 3/8” (5.5cm x 3.5cm x 1.1cm) |
DTLM2 | 2-7/8” x 1-1/2” x 3/8” (7.5cm x 3.7cm x 1.1cm) |
DTLM3 | 3-5/8” x 1-1/2” x 3/8” (9.3cm x 3.7cm x 1.1cm) |
Shipping Weight: 1 lb (0.45 kg) |
For maximum cable lengths between the controller and each DTLM module, see “Typical Line Module Inputs”. For detailed information about installation of DTLM, see “Wiring the DTLM Line Module”.
MELM
The MELM (Miniature Embedded Line Module) performs the same functions as a DTLM, except it is much smaller and has flying leads instead of terminal connections. It is ideal for installation inside the RQE or alarm device housing. MELMs provide a pair of flying leads per input:
The MELM1 has one input and is used for alarm applications.
The MELM2 has two inputs and is used when an RQE device is required to mask the line module input and, optionally, trigger the door lock.
The MELM3 has three inputs and is used in high security applications where alarm, RQE, and tamper detection are required with ±2% sensitivity.
Instead of marked terminals, the MELM has colored wires (flying leads) as shown in Table 1-16.
Table 1-16: MELM Wiring
Model | Wire Pair Colors & Functions | |||
---|---|---|---|---|
HI (white) LO (black) | Orange | Blue | Green | |
MELM1 | DIGI*TRAC | Alarm | ||
MELM2 | DIGI*TRAC | Alarm | RQE | |
MELM3 | DIGI*TRAC | Alarm | RQE | Tamper |
As shown in Figure 1-43, “MELM Wiring”, in section “MELM”, the default configuration for line module input circuits is normally closed. For a closed circuit, the controller instantly reports an alarm for any attempt to tamper with or cut the circuit. For a normally open circuit, the circuit cannot be monitored and tampering goes undetected.
The dimensions and shipping weight for the MELM is shown in Table 1-17:
Table 1-17: MELM Dimensions
Model | Dimensions (Length x Diameter) for each |
---|---|
MELM1–3 | 1” x 1/2” (2.5cm x 1.3cm) |
Shipping Weight: 1 lb (0.45 kg) |
For maximum cable lengths between the controller and each MELM module, see “Typical Line Module Inputs”. For detailed information about installation of MELM, see “Wiring the MELM Line Module”.
Wiring for the MELM line modules is shown in Figure 1-43:
Figure 1-43: MELM Wiring
SBMS3
The SBMS3-2707A consists of a balanced magnetic switch (Sentrol Model #2707A-L14) with an MELM3 factory installed. This door contact is tamper protected and wiring is supervised all the way to the unit without an external line module. External wires are available for connecting the controller and an RQE device.
For more about the SBMS3, see “Door Contacts”. For information about the setup and installation of the SBMS3, see “Mounting and Wiring the SBMS3”.
Request-To-Exit Devices (RQE)
RQEs are for doors that are either:
1.Being monitored by the access control system, or
2.Equipped with a magnetic lock.
There are several types of RQE devices which include:
Exit Bar with switches built into the door hardware
Push Buttons
Motion or Presence Sensors
The purpose of an RQE is to mask the alarm on an authorized exit and unlock the lock if required. They can be setup to trigger once only, or to continually retrigger while actuated (for use with motion detector RQE devices).
An RQE may also be used as a remote door release at a receptionist station permitting the entry of visitors requesting access.
Make certain that the use of RQE devices are in compliance with local building safety codes.
An alternative to an RQE is a ScramblePad or Reader. A ScramblePad/Reader can be used as an exit device that logs users out of the secure area. It is slower than an exit bar or sensor, but provides an audit trail, recording the identity of personnel who exit a room or facility. Exit ScramblePads or Readers are also required for specialized passback control as well as occupancy tracking and control applications.
For maximum cable lengths between the controller and each RQE, see “Typical Door Relay Outputs” .
Door Contacts
Door Contacts are devices which sense whether the door is open or closed. Most modern door contacts are two-piece magnetic devices, with one part installed on the door frame and the other part installed on the door itself. For normally closed contacts, when the door is closed, the contact is closed; when the door is open, the contact is open. Because the door contact is usually a simple circuit, any attempt to tamper with the contact will also produce an open condition and trigger the device.
All door contacts must be connected to line modules and may be either normally open or normally closed devices.
Hirsch provides a very secure door contact, the SBMS3, which includes an integrated MELM3 module. Because the line module is combined with the door contact, any attempt to tamper with the door contact will trigger the MELM3’s tamper alarm.
Figure 1-44 provides an illustration of the most common door contact.
Figure 1-44: RQE and Door Contact Devices
For maximum cable lengths between the controller and each door contact, see “Typical Door Relay Outputs”.
Remote Output Components
This section includes design notes on the following devices:
Locks/Strikes
Doors
Gates
Turnstiles
Elevators
HVAC/Lighting
Printers
Locks/Strikes
Installing electric strikes or magnetic locks requires specific training and skills. In new construction projects, electrified hardware is often supplied by hardware distributors and installed by the general contractor. Be aware that often these devices are not properly installed and checked out by the contractor. If these devices do not work properly, the entire security system will not be acceptable.
If you are not comfortable with installing a locking device, the best choice might be to subcontract the lock work to a qualified industrial locksmith. There are many choices in electrified hardware depending on door and frame conditions. It is possible to violate building and fire codes by substituting improper electric locks for existing mechanical hardware. If you have any doubts, get help.
For detailed information about installation of locks and strikes, see “Door Relay Installation: Strikes and Locks”.
Figure 1-45: Lock-to-Controller Wiring
To determine the maximum distance for lock power cable in feet and (meters) for a
particular application, see “Typical Door Relay Outputs”.
Alarm Relays
Alarm relays are dedicated relays for interface to local alarm annunciators or remote monitoring stations.
Mx | As shown in Figure 2-2 in section “Mx Controller Main Board”, the Mx controller has four alarm relays—one each for general alarms, duress alarms, tamper alarms and trouble alarms. |
---|---|
Mx-1 | An Mx-1 or Mx-1-ME controller has one Aux. Relay terminal, which is described in Table 3-1 in section “Mx-1 Controller”. The four alarm types that can trigger this relay are: general alarms, duress alarms, tamper alarms and trouble alarms (see Table 1-2 in Section “Alarm Relay Connections” for alarm descriptions). All alarms are fully programmable. |
When an alarm condition occurs, a controller can activate the alarm relay for a programmable time based on default settings or operator-selected control settings.
In addition to routing alarm conditions to alarm relays, the user can also route alarm conditions to unused on-board door relays or expansion board relays, as required. For example, an alarm condition can be programmed to trigger a control zone, thereby causing special control conditions or annunciation to take place.
Doors
Doors can be thought of as a grouping of relays, alarm inputs, and readers/keypads. In most configurations, a door is comprised of one relay, one alarm input, and an entry and/or exit reader/keypad. When defining these three components for a door, make sure they are wired to the controller in a logical manner. For example, when connecting the components of Door 1 to the controller, make sure to wire the alarm input to Input 1 on the controller and the relay for that door to Relay 1 on the controller. You wouldn’t want to connect the relay for Door 2 to Relay 1 on the controller anymore than you would want to connect Input 2 on the controller to the input on Door 1.
Hirsch controller firmware makes certain assumptions about door logic, the most important being that relays, inputs, and readers are grouped by door. In fact, the concept of control zones does not work properly unless you have wired the components for each door to the controller in a logical manner.
The electrical ratings of the door relays vary for the different controllers:
The M2 and M8 controllers used large heavy-duty socketed relays rated for 24V DC, 10 Amp loads.
The Mx controller uses Form C relays rated for 30V DC, 5 Amp loads.
The Mx-1 and Mx-1-ME controllers have a Door Relay terminal which can be configured (using jumpers) for either:
Wet Mode at 24V DC, providing a maximum of 0.25 Amps
Wet Mode at 12V DC, providing a maximum of 0.5 Amps
Dry Mode, providing a maximum of 2.0 Amps at either 30V DC or 250V AC
For details, see the description of the Door Relay terminal in Table 3-1 in section “Mx-1 Controller”.
If a door must be kept locked, there are typically two types of locks utilized:
Electric Strikes
Magnetic Locks
Electric Strikes can be either 12- or 24-VDC and are either fail safe (unlocked when deenergized) or fail secure (locked when de-energized), though most are fail secure. Magnetic locks can also be either 12- or 24-VDC and are fail safe devices only. Both types require installation of either an MOV (for AC and DC) or diode (DC only) at the lock unless the lock provides its own power suppression. The following figure provides examples of Electric Strike and Magnetic Lock Doors.
Figure 1-46: Electric and Magnetic Lock Wiring
For more about doors, see “Door Contacts”.
For a door managed by an Mx controller, see “Wiring for a Door”.
For a door managed by an Mx-1 or Mx-1-ME controller, see “Wiring for the Door”.
Gates
The relay from the controller is normally tied into a self-powered input on the gate control system. Do not run gate motor voltages of 50V AC or higher through the relays in a DIGI*TRAC Controller. Instead, use an interposing relay when controlling the gate control system’s gate motor directly.
Figure 1-47: Typical Parking Gate
Entering Gates
For a vehicle gate entrance, when choosing the location for the ScramblePad or MATCH and Reader, keep the following issues in mind:
Does the location accommodate a Hirsch mounting post and MB5 mounting box?
If the gate in question is used by both high cab trucks and passenger vehicles, you have the option to install double ScramblePads (or MATCHs and Readers) – one at normal vehicle height (curb or street mounting) and one at truck height. A custom mounting post would have to be fabricated for the truck height.
An alternative to dual ScramblePads (or dual MATCHs and Readers) is one ScramblePad (or MATCH and Reader). This means truck drivers must get out of their vehicle to use it. This alternative can cause an inconvenience, especially in bad weather areas.
The high-intensity version of the ScramblePad is always recommended for exterior gate control applications. It has less viewing restriction and a brighter display, which makes viewing easier from a vehicle.
Exiting Gates
In most cases exiting from a controlled gate is automatic. The presence of the vehicle is detected by a magnetic loop buried in the asphalt or concrete on the approach side of the gate. This loop is tied into the gate controller and opens the gate for free exit. In other cases, where higher security is required, an exit ScramblePad (or MATCH and Reader) can be installed requiring a code (or card) for exit as well as for entry.
On personnel gates in fence lines, ScramblePads or MATCH readers are often mounted on fence posts adjacent to the personnel gate. The gates sometimes use special types of electrified
hardware, although magnetic locks are being used more often in these applications.
An RQE device or exit ScramblePad are normally used on personnel gates for exit control. They must be properly protected from someone reaching through the fence to unlock the gate to gain unauthorized entry.
Turnstiles
Turnstiles can be used as alternatives to doors or gates. There are several types of turnstiles:
Full Height Turnstile
Half Height Turnstile
Optical Turnstile
Turnstiles, Gates, and Doors share most of the same power and wiring specifications. Each is discussed in this section.
Full Height Turnstile
Full height turnstiles are for facilities that require single person access. They are usually installed outdoors or in lobbies of large facilities and are locked from rotation by a solenoid.
A common access control application can have the turnstile locked for entry only and free for exit. In other applications, it is locked in both directions.
Figure 1-48: Full Height Turnstile
A ScramblePad/MATCH reader can be installed for entry and exit control. However, special mounting brackets may have to be fabricated to mount any of the ScramblePad mounting boxes.
If you’re installing a turnstile outdoors with a ScramblePad, you have the option to use the DS47L-HI or the DS47L-SPX-HI along with the MB5 mounting box.
Figure 1-49: Full Height Turnstile Mounting
Half Height Turnstile
Half height turnstiles are typically used for two-way pedestrian control. However, it may be locked from rotation (by a solenoid) for entry only and free for exit. Other applications might have the turnstile locked in both directions.
Figure 1-50: Half Height Turnstile
A ScramblePad/MATCH reader can be installed for entry and exit control. However, special mounting brackets may have to be fabricated to mount any of the ScramblePad mounting boxes.
If you’re installing a turnstile outdoors with a ScramblePad, you have the option to use the DS47L-HI or the DS47L-SPX-HI along with the MB5 mounting box.
Figure 1-51: Half Height Turnstile Mounting
Optical Turnstile
Another type of turnstile is the optical turnstile, or “passageway.” It is an attractive turnstile, used in lobby installations, and is a little faster than traditional rotating devices. It does use more floor space, however, and is not designed for exterior use. An invisible barrier created by an infrared beam activates an audible and visual alarm when broken.
Figure 1-52: Optical Turnstile
The design allows a large number of authorized users into and out of a facility with little delay. Authorized users simply mask alarm detection when they enter their codes or present their cards, thus allowing free passage through the passageway.
If unauthorized users walk through an active passageway without entering a valid code, the alarm will not be masked when the beam is broken. Typically these turnstiles are under observation by guards so they can respond to the audible and visual alarms produced by any unauthorized access attempts. Installing ScramblePads/MATCH readers on passageways will require close cooperation between the passageway manufacturer, the system installer, and the owner to optimize the throughput for the controlled facility.
HVAC, Lighting, and Elevator Control
Heating, ventilation, air conditioning, lighting, and elevator control are generally handled by the smaller 24 VDC, 2A relays found on expansion boards and M64 controllers. The M64 is specifically designed for this kind of control switching. One of the chief uses for the M64 is elevator control. Other uses include HVAC, lighting, prison door control, interlock, and CCTV.
For more information about setting up and installing these components, see “HVAC, Lighting, and Elevator Control”.
Elevator Control
When controlling access to an elevator, there are typically two modes of operation:
Day Mode (Free Access)
Night Mode (Restricted Access)
The mode is usually controlled by a time schedule. There are three primary ways to control access to an elevator. Each way provides a different level of security, cost, and convenience:
Hall Call Button Control
Floor Restriction Control
Automatic Floor Selection
Hall Call Button Control requires that you install a reader adjacent to the Hall Call Button (Up and Down Arrow buttons outside the cab). In Secure Mode, pressing either the Up or Down Arrow button will do nothing until a valid code or card is presented to the reader.
The user will then have a limited period of time, usually 10 seconds, to press one of the buttons. After the cab arrives, the user gets on and selects the floor they need. This option provides the lowest level of security, but is also the least expensive form of elevator control.
Floor Restriction Control enables the user to select the floor button they require. This option requires installation of a ScramblePad or reader in the elevator cab. During Night Mode, a user gets on the elevator, enters a valid code or presents a valid card to the reader. He/she then has a limited amount of time (usually 10 seconds) to press the button associated with the floor he/she wants. The Velocity software is used to define which floor(s) they are authorized to access and at what times. This option is usually selected when a user can access multiple floors in a building and needs to manually select which floor they are authorized to access and when. It provides a higher level of security but costs more in equipment and installation than the first option.
Automatic Floor Selection requires installation of a reader in the elevator cab. During Night Mode, a user gets on the elevator, enters a valid code or presents a valid card to the reader, and the floor button is automatically selected as defined by the user’s Control Zone. This should be used when the user only has access to one floor.
If a user has a requirement to access multiple floors, a modified version of the third option is possible. From a ScramblePad in the elevator cab, the user can enter his/her base code followed by a 1- or 2-digit floor number they wish to access. Alternatively, users can also utilize previously-defined function groups for this purpose.
If authorized, the specific floor requested is selected. This option provides a higher degree of security than the first option and has the same security as the second option. As an added benefit, this option creates an audit trail—recording which people have accessed which floors.
Printers
In a modern physical access control system, all programming and system activity is managed and recorded using security management software such as Velocity. Relevant information can be viewed online, or printed on a standard printer. Some customers also use special badge printers to create their own security badges.
For more information, see the Velocity Basics > Velocity Preferences > Preferences dialog - Printers page topic in the Velocity online help.
Card Enrollment Stations
Card Enrollment Stations are used to enroll a card into the controller’s database. Enrollment is the process of associating the unique number on each card with a user number in the controller. There are two steps involved:
The card is assigned to a specific employee, either by entering the required user number at a ScramblePad or at a Host PC.
The new card is run through the reader. Information is read off the card by the reader and is sent to a database.
When a MATCH code enrollment cross-reference list is provided and a PC with appropriate software is available, the code (as well as user name and other information) can be used to enter the numeric information by PC keyboard. An enrollment station is not required in this situation.
Network Components
Before the existence of the Internet and standardized networking gear, the network for a large physical access control system often had to be custom built. Now it is typical for the security system to be integrated with an organization’s existing network infrastructure (which is controlled by the IT department).
An Mx series controller is designed to operate in a networked environment, so the communication devices have been reduced to a SNIB2 or SNIB3 expansion board (or the equivalent functionality built onto the controller’s main board). The Mx controller can be ordered with either SNIB2 or SNIB3 capability, while the main board of an Mx-1 or Mx-1-ME controller includes SNIB3 capability.
For information about older network devices such as a modem, transceiver, NET*MUX4, or X-Box, see the DIGI*TRAC Systems Design & Installation Guide.
Secure Network Interface Boards (SNIB2 or SNIB3)
There are three generations of the Secure Network Interface Board:
SNIB (which has been discontinued)
SNIB2
SNIB3
SNIB2 Design
The SNIB2 is a drop-in replacement for the original SNIB. It is intended for those installations that require high security over Ethernet.
The SNIB2’s major components are shown in Figure 1-53:
Figure 1-53: SNIB2 Call-Out
The SNIB2 is a controller-resident communication board that enables a host PC running Velocity to program, monitor, and control up to 63 SNIB2-resident controllers per SNIB2 Ethernet port. A NET*MUX4 is required whenever there are more than 16 controllers. Additional NET*MUX4s may be required to ensure that there are never more than 16 controllers on a single hard copper wire segment.
Figure 1-54: SNIB2 Controller Limits
For more information see, “SNIB2 Cabling”.
When using one or more NET*MUX4s, maximum SNIB2 speed is 9600 bps.
Each connected controller must have its own SNIB2 board installed. The SNIB2 provides an RS-485 port as well as a 10/100BaseT Ethernet port. The SNIB2 supports the XNET 2 protocol.
X*NET2 requires Velocity version 2.6 with Service Pack 1, or higher. CCM/CCMx firmware version 7.3.0 or higher is also required.
Physically, the SNIB2 board differs from the original SNIB in three obvious respects. The SNIB2 has:
Three switch banks (SW1, SW2, and SW3)
An Ethernet RJ-45 connector with its accompanying daughterboard
Three pairs of status LEDs
The SNIB2 provides these functional advantages over the SNIB:
AES-Rijndael encryption
Globalization functionality without an XBox
Higher serial communication speeds
Ethernet connectivity
Communications become less robust as baud rates increase, wire gauge decreases, and distances increase. Most tables in the DIGI*TRAC Systems Design and Installation Guide for wire gauge and distance are based on 9600 baud. At higher baud rates, maximum distances are decreased and minimum wire gauge is increased.
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 followed: total wire run per port is not to exceed acceptable total capacitance of 100,000 pf.
To use the SNIB2, your controller must be running CCM/CCMx firmware version 7.3.08 or higher; use version 7.4.00 or higher if your computer has Velocity 3.0 or higher.
The Mx controller can be ordered with either SNIB2 or SNIB3 capability. The Mx-1 and Mx-1-ME controllers include SNIB3 capability.
The SNIB2’s Ethernet port provides high-speed TCP/IP communication over an Ethernet network between the host computer and the controller.
You can mix SNIBs and SNIB2s in your configuration; however, be aware that the speed of the network will be determined by the slowest of the network components.
The Ethernet connection enables communication between the controller with the master SNIB2 and host PC at 10/100BaseT. Speeds between the master SNIB2 and other connected downstream slave SNIB2s range up to 115200 bps.
A multidropped run of controllers is only as fast as its slowest component. Therefore, if you set a SNIB2 in the run to 19200, the maximum speed for any other SNIB2 in the run is limited to 19200 and addresses 1- 31.
A simple configuration connecting a single SNIB2-installed controller to the host might look like the example in Figure 1-55.
Figure 1-55: Host-to-Single SNIB2 Example
A more typical configuration that connects multiple controllers to the host, might look like the example in Figure 1-56:
Figure 1-56: Host-to-Multiple SNIB2s Configuration Example
For more information, see “SNIB2 Cabling”. Before the Velocity server can communicate over Ethernet with a SNIB2, you must first configure the SNIB2 through Velocity.
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 XNET port. No matter how many master SNIB2s are assigned Address 1, Velocity will be able to identify them appropriately using the SNIB2’s ROM ID and IP addresses assigned to them.
When the host is connected to a SNIB2 using Ethernet, Velocity views the first (master) SNIB2 as both a DIGI*TRAC 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 Figure 1-57:
Figure 1-57: Host-to-Multiple SNIB2s using NET*MUX4s
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.
Any installation with cascaded NET*MUX4s cannot use SNIB2 speeds higher than 9600 bps, no matter what cable or distance is involved.
For information about setting up and installing the SNIB2, refer to “Installing the SNIB2”.
SNIB3 Design
The Secure Network Interface Board v3 (SNIB3) is an update to the previous SNIB2 board. The main components of the SNIB3 are shown in Figure 1-26 in section “SNIB3”. The SNIB3 is based on a new, more powerful hardware platform that supports:
Faster Ethernet speeds. The SNIB3’s RJ-45 Ethernet port is capable of 10BaseT, 100BaseT, or 1000BaseT (gigabit) speeds.
Version 6 of the Internet Protocol, which uses 128-bit addresses to identify and locate devices on the Internet. (The previous IPv4 used 32-bit addresses.)
More robust encryption (with a 256-bit key length) through the XNET3 protocol.
(For compatibility with older SNIB2-equipped controllers, the SNIB3 can run in XNET2 mode using 128-bit AES encryption.)
When installed in a DIGI*TRAC or Mx controller, the SNIB3 communications board enables a host PC running Velocity to program, monitor, and control up to 63 controllers per SNIB3 Ethernet port. Each controller must have its own SNIB2 or SNIB3 board.
The SNIB3 is not backwards compatible with the original SNIB. You cannot use the SNIB3 with the M1N controller, because it does not support any expansion boards.
The Mx controller can be ordered with either SNIB2 or SNIB3 functionality. To upgrade an Mx controller which has the SNIB2 daughterboard to use a SNIB3 expansion board, you must first remove the SNIB2 daughterboard from the Mx controller’s main board, as explained in “Preparing an Mx Controller with a SNIB2 to Use a SNIB3”.
(SNIB3 capability is built onto the main board of an Mx-1 or Mx-1-ME controller.)
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 in section “SNIB3”).
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 in section “SNIB3”).
The SNIB3 also supports connections to the NET*MUX4, as explained in “Using NET*MUX4s with SNIB3s”.
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 total capacitance of 11-17 pf and a total of 100,000 pf.
A NET*MUX4 is required whenever there are more than 16 controllers. Note that using a NET*MUX4 enables more controllers to be managed through a single network port, but it limits the data communication speed to 9600 baud.
Whenever an Ethernet connection is employed between the host and the SNIB3, Velocity views the SNIB3 as an XNET port because the SNIB3 includes XBox functionality. The host communicates with the Ethernet-connected SNIB3 using either XNET 2 or XNET 3. For each string of controllers, the first (master) SNIB3 with the Ethernet connection must be assigned the same address as the XBox port.
Prerequisites for the SNIB3
The SNIB3 board has the following prerequisites or dependencies:
The CCM/CCMx firmware must be version 7.5.37 (or later).
The Velocity software must be version 3.6 SP1 (or later).
The Mx controller can be ordered with either SNIB2 or SNIB3 functionality. To upgrade an Mx controller which has the SNIB2 daughterboard to use a SNIB3 expansion board, you must first remove the SNIB2 daughterboard from the Mx controller’s main board. For more information, see “Preparing an Mx Controller with a SNIB2 to Use a SNIB3”.
Although the SNIB3 supports 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 your SNIB3 boards.
IPv6 is generally not compatible with IPv4, so if you want to use IPv6 addressing for a SNIB3, it must be installed on a network which supports IPv6.
Upgrading the firmware of downstream SNIB3s must be done one at a time. In a master-slave configuration, you must upgrade the master SNIB3 board’s firmware first, and then upgrade each slave SNIB3 board’s firmware in sequence. Don’t start the download for the next SNIB3 board until the firmware upgrade for the previous SNIB3 board has completed.