A100K10602 Alphacom XE User Guide

2013
OEM Device Configuration Guide
PERPETUAL INNOVATION
Lenel OnGuard® 2013 OEM Device Configuration Guide, product version 6.6
This guide is item number DOC-603, revision 3.005, July 2012
Copyright © 1997-2012 Lenel Systems International, Inc. Information in this document is subject to change without
notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose, without the express written permission of Lenel Systems International, Inc.
Non-English versions of Lenel documents are offered as a service to our global audiences. We have attempted to
provide an accurate translation of the text, but the official text is the English text, and any differences in the
translation are not binding and have no legal effect.
The software described in this document is furnished under a license agreement and may only be used in accordance
with the terms of that agreement. Lenel and OnGuard are registered trademarks of Lenel Systems International, Inc.
Microsoft, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries. Integral and FlashPoint are trademarks of Integral
Technologies, Inc. Crystal Reports for Windows is a trademark of Crystal Computer Services, Inc. Oracle is a
registered trademark of Oracle Corporation. Other product names mentioned in this User Guide may be trademarks or
registered trademarks of their respective companies and are hereby acknowledged.
Portions of this product were created using LEADTOOLS © 1991-2012 LEAD Technologies, Inc. ALL RIGHTS
RESERVED.
OnGuard includes ImageStream® Graphic Filters. Copyright © 1991-2012 Inso Corporation. All rights reserved.
ImageStream Graphic Filters and ImageStream are registered trademarks of Inso Corporation.
Warranty
Lenel warrants that the product is free from defects in material and workmanship under normal use and service with
proper maintenance for one year from the date of factory shipment. Lenel assumes no responsibility for products
damaged by improper handling, misuse, neglect, improper installation, over-voltages, repair, alteration, or accident.
This warranty is limited to the repair or replacement of the defective unit. In no event shall Lenel Systems
International be liable for loss of use or consequential damages of any kind, however occasioned.
There are no expressed warranties other than those set forth herein. Warranty expressly excludes third party additions,
deletions and/or upgrades to this product, including those contained herein. Lenel does not make, nor intends, nor
does it authorize any agent or representative to make any other warranties or implied warranties, and expressly
excludes and disclaims all implied warranties of merchantability or fitness for a particular purpose.
Returned units are repaired or replaced from a stock of reconditioned units. All returns must be accompanied by a
return authorization number (RMA) obtained from the Lenel customer service department prior to returning or
exchanging any product. The RMA number must appear on the outside of the shipping box and on the packing slip.
Any items returned without an RMA number will not be accepted and will be returned at the customer’s expense. All
returns must have transportation, insurance, and custom brokers’ fees prepaid.
Liability
It is expressly understood and agreed that the interface should only be used to control exits from areas where an
alternative method for exit is available. This product is not intended for, nor is rated for operation in life-critical
control applications. Lenel Systems International is not liable under any circumstances for loss or damage caused by
or partially caused by the misapplication or malfunction of the product. Lenel’s liability does not extend beyond the
purchase price of the product.
Table of Contents
OEM Devices ....................................................................... 7

1. Destination Dispatch .............................................................................. 9
1.1 Hardware Setup .................................................................................................... 9
1.2 OnGuard Configuration ...................................................................................... 10
2. Fire Panels ........................................................................................... 11

2.1 Pyrotronics Fire Panel ........................................................................................ 11
2.2 Notifier Fire Panels ............................................................................................. 14
2.3 Tateco Fire Panel ............................................................................................... 18
3. HID EdgeReader and EdgePlus .......................................................... 21

3.1 Wiring the EdgeReader ...................................................................................... 21
3.2 Configuring the EdgeReader .............................................................................. 21
4. Iris Recognition .................................................................................... 23

4.1 Installing an iCAM4000 with ICU4000 Controller ................................................ 23
4.2 Installing an iCAM4000V .................................................................................... 28
4.3 Installing an iCAM7000 ....................................................................................... 32
4.4 Enrollment .......................................................................................................... 34
4.5 Verification .......................................................................................................... 35
4.6 Software Upgrades ............................................................................................. 35
5. Onity Programmer ............................................................................... 37

5.1 Configuration for Onity ........................................................................................ 37
6. Personal Safety ................................................................................... 39

6.1 Visonic SpiderAlert ............................................................................................. 39
6.2 OnGuard Configuration ...................................................................................... 40
7. Receivers ............................................................................................. 41
7.1 Bosch D6500/D6600 Receiver ........................................................................... 41
7.2 Osborne-Hoffman OH-2000 ............................................................................... 44
7.3 AES-IntelliNet 7000 ............................................................................................ 44
7.4 Verex HSC-IP Receiver ...................................................................................... 45
8. Cypress Timer ..................................................................................... 47

8.1 System Level Wiring ........................................................................................... 48
8.2 DIP Switches ...................................................................................................... 49
8.3 Time Displays: Functional Description ................................................................ 50
8.4 Wall Mounting ..................................................................................................... 53
9. TVS TVC-2100 Series Video Text Inserter .......................................... 55

9.1 Firmware ............................................................................................................. 55
revision 3 — 3
Table of Contents
9.2 TVC-2104 Hardware ........................................................................................... 55

9.3 TVC-2104 Operation .......................................................................................... 57
10. Corex CardScan ................................................................................ 59

10.1 Corex CardScan Installation and Configuration ................................................ 59
11. RFIDeas Readers .............................................................................. 63

11.1 HID iCLASS AIR ID (Model: RDR-7081AKU) and AIR ID Playback (Model:
RDR-7585AKU) Readers ...................................................................................... 63
11.2 HID Prox Reader (Model: RDR-6081AKU) ....................................................... 64
11.3 AWID Prox (Model: RDR-6981AKU) ................................................................ 66
11.4 MAG Swipe (Model: MS3-00M1AKU) ............................................................... 66
12. Cypress Wedge ................................................................................. 69

12.1 Cypress Wedge WDG-4413 ............................................................................. 69
12.2 Cypress Wedge WDG-5912 ............................................................................. 70
13. DigiOn24 Encoder ............................................................................. 73

13.1 Installation ........................................................................................................ 73
13.2 Configuration of the Encoder ............................................................................ 73
14. ActivIdentity ActivEntry ...................................................................... 75

14.1 Install the ActivEntry Module ............................................................................ 75
14.2 Access Readers ............................................................................................... 76
14.3 Set up ActivEntry .............................................................................................. 77
14.4 Configure the Badge ID .................................................................................... 77
14.5 Invalid Credentials ............................................................................................ 78
14.6 Configure the Card Format ............................................................................... 79
14.7 Badge ID and Card Format Example ............................................................... 79
14.8 Enrollment ........................................................................................................ 80
15. Fingerprint Enrollment and Verification .............................................. 83

15.1 Cross Match ..................................................................................................... 83
15.2 Sagem Morpho ................................................................................................. 85
16. GemPlus EasyAccess 332 Encoder .................................................. 87

16.1 Encoder Installation .......................................................................................... 87
16.2 Software Configuration ..................................................................................... 88
17. iClass Programmer ............................................................................ 89

17.1 Encoder Wiring ................................................................................................. 89
17.2 Configuration of the iClass Programmer ........................................................... 90
18. Integrated Engineering ...................................................................... 93

18.1 SmartID/SmartPro/SmartLOGON ..................................................................... 93
19. Intelli-Check ID-Check ....................................................................... 95

19.1 IDC1400 Configuration ..................................................................................... 95
19.2 OnGuard Configuration .................................................................................... 96
20. OMNIKEY 5125 Wedge ..................................................................... 99
4 — revision 3
20.1 Installation ........................................................................................................ 99

20.2 Configuration of the 5125 Reader .................................................................... 99
21. ScanShell 800/1000 ......................................................................... 101

21.1 ScanShell Configuration ................................................................................. 101
21.2 OnGuard Configuration .................................................................................. 101
22. Topaz SignatureGem Pen Tablet .................................................... 103

22.1 SignatureGem Installation .............................................................................. 103
IP Support ........................................................................ 107

23. LNL-ETHLAN (MSS1/MSS100 Ethernet Controller) ........................ 109
23.1 Establish Serial Communication with the ETHLAN ........................................ 109
23.2 Establishing Network Communications .......................................................... 110
23.3 Configuring the ETHLAN ................................................................................ 111
23.4 Device Configuration ...................................................................................... 112
24. Security Settings (SDS1100) ........................................................... 114

24.1 Supported Controller Types Over Encrypted Connection ............................... 114
25. IP Cameras ...................................................................................... 116
Index ................................................................................................................ 117
revision 3 — 5
Table of Contents
6 — revision 3
OEM DEVICES
1 Destination Dispatch
OnGuard has the capability to integrate with the Otis Elevator Destination Dispatching System (DDS). The
DDS controls elevator cab routing and traffic flow within a building. Cardholders may use credentials that
are authorized for specific floors in their facility. Whenever a credential is presented for access, that
information is sent from OnGuard to the DDS.
This will be done through the following:

• Configure and communicate with a Destination Entry Redirector (DER). This is a server associated
with all elevator groups in a building.
• Configure and communicate with a Destination Entry Server (DES). This is a server that controls a
group of elevators and is responsible for communicating with Destination Entry Computer (DEC)
keypad terminals.
• Configure and communicate with one or more Destination Entry Computers (DEC) associated with a
DES or DER. The DEC is a keypad terminal that acts as an interface between the user and the elevator
system. The user enters the floor they wish to go at the DEC terminal.
• Configure a DEC to reader association. If an access attempt occurs for a reader associated with a DEC,
credential information is sent to the DEC. This information is then used by the DDS to grant or deny
access to certain elevator floors. This configuration will be stored in the OnGuard database.
• Configure the operational mode and allowed floors for a DEC. Allowed floors are floors that are
accessible to the general public and do not require authorization.
• Configure which authorized floors a cardholder will be allowed to access.
• Establish communications between the Communication Server and the DER, DES and DEC.
• Grant/deny access to floors when access attempts occur and send this information to a DEC.
• Display the DER, DES and DEC(s) in Alarm Monitoring with status(es) for these devices.
1.1 Hardware Setup
OnGuard communicates with the Otis components via an Ethernet switch. The DDS consists of third-party
hardware. OnGuard only transmits information to the DDS, and is not responsible for the operation, setup,
or configuration of these third-party hardware devices. Nor does OnGuard receive feedback or events from
the DDS.
revision 1 — 9
Destination Dispatch
Communication between the Otis (left) components and OnGuard (right) components
1.2 OnGuard Configuration
The Otis components must be configured in OnGuard in order for the Destination Dispatching to work
properly. For detailed information, refer to “Elevator Dispatching Configuration” the System Administration
User Guide.
For the Communication Server workstation that is integrated with the Otis system, the following default
information must be assigned to the Network Interface Card (NIC):
• IP Address 192.168.50.250
• Subnet Mask 255.255.255.0
• Default Gateway 192.168.50.254
10 — revision 1
2 Fire Panels
Currently, these types of panels are supported: Pyrotronics (MXL series), Notifier, and Tateco.
Before continuing, verify that you have a license for OnGuard with fire panels enabled. The ability to use
fire panels is a count-based licensed feature.
2.1 Pyrotronics Fire Panel
Communication to the fire panel must be established through an RS-485 4-wire connection to a NIM-1R
module. Firmware version 10.24 is supported. The NIM-1W may also be used (with the same wiring and
firmware version).
Use the following settings to configure this.
Black Box Settings:
Jumpers:
W5 should be on B-C to set RTS/CTS/CD.
W8 should be on A-B to set 4-wire.
W9 should be on D to set ON.
W15 should be on A-B to set RTS/CD Enabled.
W16 should be on A to set 0 ms Turn Around Delay.
W17 should be on E to set 0.15 ms Driver Enable Hold.
W19 - NO JUMPER. This is for testing purposes only.
XW1A - Jumper-block must be installed here to set DCE Emulation Mode.
XW1B - Jumper-block must NOT be installed here (this would change mode to DTE Emulation).
Switches:
S1 - Out to set Normal
S2 - ON to set Terminated or OFF to set Not Terminated
S3 - OFF to set Not Biased.
revision 1 — 11
Fire Panels
Notes: 18 AWG minimum

80 Ohms maximum per pair
Use twisted pair or shielded twisted pair
Terminate the shields at the NIM-1R enclosure only
Maximum voltage: 9 V
Maximum current: 150 mA
12 — revision 1
Connect the wires accordingly.
S1
W17
Black Box IC108A
B C D E
W16
A
A B C D E
W8
A B C
A B C
W19
A B C
W15
A B C D E
W9
A B C
W5
BIAS TERM.
S3 S2
XW1B XW1A
110 VAC 25-Pin Serial Connector
Rx B+
Rx A -
Tx B +
Tx A -
Transformer
7 3 2
TB1
1 2 3 4
(max. 4000 feet)

5 6
7 8 9 10 11 12 13 14 15 16
(max.
DO
NOT
50 feet)
NIM-1R
USE
RTS Rx Tx
SUPERVISED
MOM-4
5 2 3 7 3 2
1 2 3 4 5 6
DB 9 Pin Male DB 25 Pin Female

7 8 9 10 11 12 13 14 15 16
E.O.L.R.
9 or 25 Pin Connector
120 OHM
NIM-1R
DO Workstation (PC)
NOT
USE
TB3
revision 1 — 13
Fire Panels
2.1.1 Pyrotronics Debug Settings
In order to investigate issues/events of fire panels from Alarm Monitoring, the following setting is required
in the ACS.INI file:
[Pyrotronics]
PyroDebug=1
2.2 Notifier Fire Panels
The fire panel must be programmed in order to recognize downstream devices. This is the only way to
configure the panel to report events.
Downstream devices that are directly connected to the fire panel (such as loops and annunciators for the
AM2020 panel; loops, annunciators, bell circuits, and panel modules for the NFS-640) must be configured
in System Administration (Additional Hardware > Fire Panels > Fire Devices) with unique name and
addressing.
Loop modules and loop detectors (connected to the loops) must also be configured in System Administration
(Additional Hardware > Fire Panels > Fire Inputs/Outputs) with unique name and addressing.
For more information, refer to the Notifier documentation.
2.2.1 Notifier AM2020 Fire Panel
The Notifier panel requires a serial interface board in order to function. The SIB-232 or SIB-2048A may be
used.
Connecting the AM2020 Panel
The serial interface board is used to connect to the printer serial port (pins 1, 2, and 4 on P3) on the fire
panel.
• Pin 1 is EIA-232 Reference.
• Pin 2 is Transmit to PRN.
• Pin 4 is Receive from PRN.
A DB-25 or DB-9 cable may also be used. Connect the pins as follows:
SIB pin DB-25 pin DB-9 pin

Pin 1 Pin 7 (GND) Pin 5 (GND)
Pin 2 Pin 3 (RXD) Pin 2 (RXD)
Pin 4 Pin 2 (TXD) Pin 3 (TXD)
14 — revision 1
Programming the AM2020 Panel
The fire panel must be programmed in order to recognize downstream devices such as intelligent/
addressable detectors and modules, Panel Circuits, and Notification Appliance Circuits (NACs). Use the
keypad connected to the panel for programming. For more information, refer to the Notifier documentation.
1. To begin programming, press [Prog.].

2. You will then be prompted for a password. Enter 00000. This is the default password and should be
changed to a secure password upon initial programming.
3. Select the type of programming to be performed from the menu. Refer to the Notifier documentation.
2.2.2 Notifier NFS-640 Fire Panel
The NFS-640 is a fire panel integrating a CPU, power supply (6 A), and battery charger, combined with a
mounting chassis and cabinet. It connects to the host via a standard serial cable.
The NFS-640 panel has been approved for use with firmware version 002.000.002B/002.001.009A.
Important: Due to hardware limitations, the connection of this device is unable to be

monitored. Therefore, OnGuard reports the status of the Notifier NFS-640 panel
as being online (even when it is offline). It may be necessary to physically verify
that the panel is indeed online.
revision 1 — 15
Fire Panels
Connecting the NFS-640 Panel
Use a serial cable to connect the fire panel to the host. Wire the cable directly to the panel using terminal
TB14.
16 — revision 1
A DB-25 or DB-9 cable may be used. Connect the pins as follows:
TB14 DB-25 pin DB-9 pin

TX 3 (Receive) 2
RX 2 (Transmit) 3
REF 7 (Ground) 5
Programming the NFS-640 Panel
The fire panel must be programmed in order to recognize downstream devices such as intelligent/
addressable detectors and modules, Panel Circuits, and Notification Appliance Circuits (NACs). Use the
keypad connected to the panel for programming. For more information, refer to the Notifier documentation.
1. To begin programming, press [ENTER.].

2. Press [1] to enter the programming menu. At this point, if the panel starts beeping, you may silence it by
pressing the [ACKNOWLEDGE SCROLL DISPLAY] button.
3. You will then be prompted for a password. Enter 00000.
4. Press [1] to enter the Basic Program menu.
5. Press [1] to start Auto-programming. This option identifies all addressable devices connected to the
panel. You will be prompted to accept or remove the device from memory as they are found by the
panel.
6. After this process is complete, a summary of programmed devices will be displayed. Press [Enter] to
continue. If any alarms are generated, you may silence them again. Configuration of the panel is
complete.
2.2.3 Notifier Debug Settings
In order to investigate issues/events of fire panels from Alarm Monitoring, the following setting is required
in the ACS.INI file:
For both the Notifier AM2020 and Notifier NFS-640:
revision 1 — 17
Fire Panels
[Notifier]
NotifierDebug=1
2.3 Tateco Fire Panel
OnGuard integrates with the Tateco fire panel using ESPA protocol. This protocol allows for the reporting of
alarms with the use of a data converter.
2.3.1 Connecting the Panel
The data converter communicates via serial or LAN connection.
For a serial connection, use a null modem cable to connect the data converter to a workstation.
For a LAN connection, use a null modem cable to connect to a Lantronix device. Plug the null modem cable
into the 9-pin male connector labeled K5. Configure the Lantronix device as follows:
• access=remote
• parity=even
• stop bits=2
• byte size=7
• flow control=none
• baud rate=4800
2.3.2 Power
The data converter requires 24 VDC. On terminal block P1, connections 1 and 2 are for power: +24 VDC
connects to the terminal block P1, terminal 1 and 0 V connects to the terminal block P1, terminal 2.
18 — revision 1
2.3.3 Test Mode
Jumper BY4 can be used to put the data converter into test mode. In test mode, messages will be sent out
roughly once per second.
2.3.4 Software Configuration
To configure a device using the ESPA protocol, configure a fire panel and select the type as ESPA. If you are
also parsing the ESPA messages, you can optionally configure downstream devices for this panel.
If the ESPA device is capable of generating a heartbeat, it can be monitored. In the Options sub-tab,
configure this setting. If there is no support for a heartbeat signal on the device, set the heartbeat interval to
0 so that the heartbeat is not monitored.
Parsing Information
Fire devices and fire inputs/outputs can also be defined. This would be useful if you are planning on parsing
out the data in the ESPA messages. Doing so will cause a message, such as “BR062-08,” to be parsed into
event description BR, device 62, and input 8.
To parse out the Tateco messages, the following format settings can be specified in the ACS.INI file.
[ESPA]
EnableParsing=1
ParseSeparatorLocations=5
ParseSeparator=-
ParseEventTextStart=0
ParseEventTextEnd=1
ParseDeviceStart=2
ParseDeviceEnd=4
ParseInputStart=6
ParseInputEnd=7
Different parsing schemes can also be handled based on the panel ID. This is for cases in which you are
integrating to multiple ESPA devices and wish to parse in a different manner. In order to do this, the same
settings would be used but with the device ID specified in the settings. The settings listed above would be
the default settings, and then the settings that included the panel ID would be used to override the default
settings.
For example, if the panel ID is 6 and you want to parse out the device information, in the ACS.INI file, use
ParseDeviceStart_6
and
ParseDeviceEnd_6
revision 1 — 19
Fire Panels
20 — revision 1
3 HID EdgeReader and EdgePlus
The HID EdgeReader is a device that houses both a controller and reader. The EdgePlus has the option of
connecting to an iCLASS reader/writer, LCD keypad, or biometric reader devices. Since it doesn’t require a
physical connection to a separate controller, the device can connect to the host on an IP network. With built-
in 802.3af Power over Ethernet (PoE), it does not require a separate power supply.
3.1 Wiring the EdgeReader
Use a CAT 5 cable to connect the reader to the network. For instructions for wiring the reader, inputs, and
outputs, refer to the manufacturer documentation.
After the reader is connected, use the Discovery Client to configure it. You may download the Discovery
Client from the HID website, www.hidcorp.com.
Note: For more information, refer to the manufacturer documentation.
3.2 Configuring the EdgeReader
1. Install the Discovery Client and start the program, Discovery GUI. Any EdgeReader or EdgePlus
devices on the sub-network will be detected.
2. The MAC address of the controller is displayed in the window. The unit also has a label with the MAC
address on it. Go to the basic configuration web page by clicking Configure Unit.
3. Enter the Host IP Address or Host Name. This should be the host IP address or host name of the
OnGuard Communication Server.
4. Type in the Here I Am Interval (in seconds). The recommended time is 30 seconds.
5. Click [Submit]. A page will be displayed with a confirmation of the settings.
6. Verify that the settings are correct and then click [Save]. You may click [Cancel] to go back and adjust
the settings.
Basic setup of the EdgeReader/EdgePlus is complete. The device must be configured as an access panel in
OnGuard as well. For OnGuard configuration, refer to the System Administration User Guide.
revision 1 — 21
HID EdgeReader and EdgePlus
22 — revision 1
4 Iris Recognition
The iris of every human eye exhibits a distinctive pattern. A captured image of the iris can be used to verify
identity.
With a device activated by proximity sensor, or by a card, a subject positioned 12 to 14 inches from the
Enrollment iCAM is guided by a mirrored, audio-assisted interface to allow a camera to take a digital video
of the iris (the colored ring around the pupil).
Individual images from the live video are taken, then the highest quality images from the multiple images
that have been captured are used. The algorithm of the iris recognition process analyzes the patterns in the
iris visible between the pupil and sclera and converts them into a digital template. This value can be stored
on the SmartCard and communicated to access control panels associated with portals where the subject has
access privileges.
The iCAM is activated by placing the SmartCard with stored iris template against the iCAM. The same
mirror-assisted, audio-prompted interface helps ensure proper positioning and quick recognition. The
camera unit uses a methodology to create, select, and digitize an image to be compared against the value
obtained at enrollment.
4.1 Installing an iCAM4000 with ICU4000 Controller
1. Wire the ICU4000 controller. If you are using an external smart card reader, establish a serial
connection between the reader and the iCAM4000.
2. Install the iris camera.
3. Wire the WIB4000 (Wiegand Interface Board inside the ICU4000 Wiegand OUT 1) and the LNL-1320
Dual Reader Interface Module.
4. Install the IrisICUAdmin4000 software provided by the manufacturer. This software is used to
configure the IrisAccess devices.
4.1.1 Wiring the ICU4000 to WIB4000
Connect the Iris ICU (part number ICU4000R-W) to the Ethernet network. Connect the WIB4000 (housed
in the ICU). For more information, refer to the IrisAccess ICU4000 Hardware Guide. This can be found in
the documentation accompanying the unit or on the manufacturer’s Web site: http://www.irisid.com/ss/
documentation.htm.
4.1.2 External Reader
If the iCAM does not include a reader inside the unit, an external reader must be installed along with the
iCAM. Connect the reader to the Wiegand In and Smart Card ports of the iCAM. For wiring details, refer to
the IrisAccess Smart Card Integration documentation (included with the unit or on the manufacturer Web
site).
4.1.3 Configuring the iCAM4000
The iCAM 4xxx Series for iCLASS and DESFire are iris cameras supported by the OnGuard system.
However, PIN pad functionality is not supported. Each iCAM unit requires an Ethernet network connection
and 12 VDC @ 2.5A power.
revision 3 — 23
Iris Recognition
For more information about camera installation and configuring the following settings, refer to the
iCAM4000 Hardware Guide and the IrisAccess Web Configuration Interface Guide for iCAM Series.
Camera Network Settings
Once the camera is connected, log into the camera and set the IP address, subnet mask, and default gateway
for the iCAM. Be sure to use IrisAccess EAC Software version 3.01. Each iCAM must be changed
individually. Do not connect more than one unconfigured iCAM to the network at any one time to avoid IP
address conflicts.
1. Wire the iCAM for network and power.

2. Connect the iCAM to the network and connect the power adapter.
3. Set the computer to the static IP address of 192.168.5.250, subnet 255.255.255.0.
4. Open the web browser and go to http://192.168.5.100. The iCAM login screen appears.
5. Log in by entering:
• Username: iCAM4000 (case sensitive)
• Password: iris4000
6. Click [Network Settings].
7. Enter a new IP address for the iCAM (default = 192.168.5.100).
8. Enter the new Subnet Mask for the iCAM (default = 255.255.255.0).
9. Enter the new Default Gateway for the iCAM (default = 192.168.5.254).
10. Click [OK] to save changes and open the network settings verify screen.
After a few seconds the web browser will resolve to the new IP address and open the login screen (only if the
iCAM IP address is on the same subnet as the computer).
Smart Card Configuration
Perform the following steps for smart card configuration:
1. On the iCAM web page, click [SmartCard Configuration].

2. Select the smart card type:
a. If you are using iCLASS:
i. Set the SmartCard Type to iCLASS.
ii. Enter the authentication key.
b. If you are using DESFire:
i. Set the SmartCard Type to DESFire.
ii. For DESFire, specify Lenel for Communication.
iii. Enter the authentication key. This should be one of the three keys that make up the composite
master key.
3. Click [OK] to save the changes.
Wiegand Settings
1. On the iCAM web page, click [Wiegand Settings].
24 — revision 3
2. Under Wiegand In, for the Interface Type, select General Wiegand.
3. Under Wiegand Out, for the Interface Type, select Disable (if applicable, based on iCAM software
version).
4.1.4 Card Formats
The following should be configured in System Administration on the Card Formats form.
1. Choose the application.

a. If you are using iCLASS:
i. Set the Application to IrisAccess (iCLASS).
ii. The application key should be configured using the IrisAccess Web page.
iii. Choose the memory configuration.
When Book 1/16kbits/16 Application Areas or Book 1/16kbits/2 Application Areas is
selected, the IrisAccess application will be written to Book 1 according to the selected card
layout. Book 0 remains untouched. If Book 0 is selected, Book 1 remains untouched.
iv. Next to the Iris Data Encryption Method, click [Change].
v. Select the encryption algorithm (AES, DES, or DES3) from the drop-down.
vi. Click [Generate New Key].
vii. Click [Store Key to File]. Note the location of this file. It will be used for configuration in
IrisICUAdmin.
b. If you are using DESFire:
i. Set the Application to DESFire (TWIC 1.02 Data Model).
ii. For the Biometrics option, select either IrisAccess or INCITS 378 & IrisAccess.
iii. Click [Enter/Modify CKMC] and enter the three parts of the composite master key.
Once the card format is configured, assign the smart card format application to the badge type. This can be
done in System Administration or ID CredentialCenter in the Badge Types Folder, on the Encoding Form.
For more information, refer to the System Administration or ID CredentialCenter User Guides.
4.1.5 Wiring a WIB4000 to LNL-1320
1. The WIB4000 is used to control access to a facility door. Connect this to an LNL-1320 Dual Reader
Interface Module.
revision 3 — 25
Iris Recognition
WIB4000 and LNL-1320 connection
TB8
GND DAT CLK BZA LED VO GND DAT CLK BZA LED VO
READER 1
D0 D1
READER 2
D0 D1
TB9
Dual Reader
Interface Module
TB10
C NC
RLY 1
GND
NO
Wiegand OUT 1
NC
RLY 2
NO C
TB11
C NC
RLY 3
NO
NC
RLY 4
NO C
C NC
RLY 5
NO
NC
RLY 6
NO C
TB12
Important: Verify that the wiring is done according to this drawing. Incorrect wiring might
cause hardware damage.
2. On the dual reader interface module, set J2 to Unregulated and set J3 to 2W.
3. Connect the WIB4000 to the ICU4000 according to the IrisAccess ICU4000 Hardware Guide.
26 — revision 3
4.1.6 IrisICUAdmin4000
To use this software, establish a serial connection between the host workstation and the ICU4000. Using a
serial configuration cable, plug the connector (DB 9F) into serial port 1 (CH1) of the ICU. Set the DIP
switch next to CH1 to RS-232 mode.
1. Start the IrisICUAdmin4000 application. (IrisAccess EAC software should already be installed on the
computer with IrisICUAdmin4000 installed.)
2. Connect the ICU4000 to the network. Using the supplied ICU configuration cable, connect to channel
one in the ICU making sure the red pins to the right are in the RS-232 position. (By default, these pins
should already be in the correct position.) Connect the other end of the cable to the serial port of the
server, making sure to use the COM1 port.
a. Make sure the ICU is powered off.
b. Start the IrisICUAdmin4000 application on the server.
c. Select New Installation.
d. Follow the prompts and fill in data as needed, entering the correct IP address for the ICU. Enter the
correct server IP address. Additionally, enable all four channels by selecting them and providing
each with a unique security ID.
Note: Do not use 1111111111111111 as a security ID in the ICU as that security ID is often used for
the Iris Enroll application. Do not lose this information. Make note of the CH1-CH4 security
ID data. They will be needed later in the setup, for future setting changes, and for
troubleshooting or upgrading as needed.
e. When prompted, power the ICU On and press Start. After approximately 65-90 seconds the ICU
begins to update and then the process finishes. Continue following the prompts, and when asked to
configure the channels, make sure only the desired channels are selected.
3. Click [Configuration]. When prompted, enter the IP address and password (the default password for the
ICU4000 is iris4000).
4. Select the following check boxes (where “x” is the channel you are using):
• Channel x
• Use Access Panel x
5. Select the option for iCAM + SmartCard.
6. Click [Configure Channel x].
7. On the iCAM tab:
a. Enter the IP address of the iCAM.
b. For Eye Selection, choose the option Get from Card.
c. Select the check box Detect iCAM tamper on connect to iCAM if needed.
d. For External Hardware Interface, select DCU/WIB.
e. Enter the number of seconds for the Verification Timeout. When configuring iCAM devices with a
smart card reader, the timeout value should be higher than the default of 5 seconds.
8. On the SmartCard tab:
a. If using iCLASS (for iCAM units with SmartCard readers only):
i. For the Block Offset (hexidecimal), enter 13 (this is the default setting).
revision 3 — 27
Iris Recognition
ii. When encoding with the iCAM, set the Data format in Smart Card to GSC-IS Format. If you
are using a stand-alone encoder, select Lenel Format.
iii. For the Encryption Algorithm, select the same type (AES, DES, DES3, or None) as the
IrisAccess card format configured in the access control software.
iv. Click [Get Keys]. Select the key file. (This should have been generated using the access
control software and stored to a file.)
b. If you are using DESFire (for iCAM units with MIFARE/DESFire card readers only):
i. Make sure Use as Prox Card is not selected. The Book and Block Offset settings do not apply.
ii. When encoding with the iCAM, set the Data format in Smart Card to GSC-IS Format. If you
are using a stand-alone encoder, select Lenel Format.
iii. For the Encryption Algorithm, select None.
9. On the Access Panel tab:
a. Select The Access Control System checks user’s rights.
b. Make sure Wait for Access Panel Response is not selected.
c. Select Use Wiegand as output.
d. Click [Wiegand Settings].
e. Select Bypass the input signal through Wiegand IN into the output signal with no change.
f. Select Output the signal with Facility Code and Card ID for only Accept.
g. Select Lenel FASC-N Format.
h. Set Active State to Low.
i. Set Pulse Duration to 40 and the Bit Period to 2148.
j. Click [OK].
10. For the Access Door tab, configure the settings as desired.
11. For the GPO tab, configure the settings as desired.
12. When this configuration is completed, click [OK].
13. Under After Settings, click [Send to ICU]. This will send the configuration settings to the ICU4000
using its IP address and password. Enter the password when prompted. The new settings are in effect
after restarting.
Note: For more information on IrisICUAdmin4000 settings, refer to the IrisAccess Software
Installation Manual. This is installed along with the EAC software.
4.2 Installing an iCAM4000V
1. Wire the network connection for the iCAM4000V.

2. Install the iris camera.
3. Wire the iCAM4000V (Wiegand OUT 1) to the reader interface module.
28 — revision 3
iCAM4000V and Reader Interface connection

TB8
READER 1
D0 D1
READER 2
D0 D1
TB9
Reader Interface
Module
(LNL-1320
shown)
DATA 1
DATA 0
GND
Wiegand OUT
iCAM4000V
4.2.1 Configuring the iCAM4000V
The iCAM4000V is an iris camera supported by the OnGuard system. However, PIN pad functionality is not
supported. Each iCAM4000V unit requires an Ethernet network connection for iCAM configuration, and
12 VDC +/-10% @ 2.5 A maximum power.
iCAM4010V-H1 Hardware Guide and the IrisAccess Web Configuration Interface Guide for iCAM Series.
iCAM Network Settings
Once the iCAM is connected, log into the camera and set the IP address, subnet mask, and default gateway
for the iCAM. Each iCAM must be changed individually. Do not connect more than one unconfigured
iCAM to the network at any one time to avoid IP address conflicts.

revision 3 — 29
Iris Recognition
SmartCard Configuration
Perform the following steps for SmartCard configuration:
1. On the iCAM web page, click [SmartCard Configuration].

a. Set the SmartCard Type to HID iClass.
b. Set the Transmission Protocol to ISO 15693 (Longer Range).
c. Set Book to Book 0.
d. Set Offset (hexadecimal) to 13.
e. Set the Application Key (hexadecimal) as required by the site.
f. If you encoded the SmartCard with a stand-alone encoder, set the Data Format to Lenel Format.
If you encoded the SmartCard with an iCAM4000, set the Data Format to GSC-IS Format.
g. Set the Encryption Algorithm and Encryption Key File as required by the site.
Note: The Encryption Algorithm and Encryption Key File settings must match the Card Format
settings. For more information, refer to Card Formats on page 31.
iCAM Configuration
1. On the iCAM web page, click [iCAM Configuration].

2. Set the Volume and VFD Message as required by the site.
3. Set the Verification Time Out to 10 sec.
4. Set Which Eye to Get from Cardor Either Eye, depending on customer requirements.
Note: Customers might notice improved verification speed if Which Eye is set to Either Eye.
5. Set Countermeasure, Tamper Detection, and Auto Tilt as required by the site.
30 — revision 3
Relay Configuration
1. On the iCAM web page, click [Relay Configuration].

2. Set Relay 1 - Door Control to Disable.
3. Set Relay 2 - Tamper Notification to Disable
Wiegand Settings
1. On the iCAM web page, click [Wiegand Settings].

2. Under Wiegand In, for the Interface, select Enable.
3. Under Wiegand Out:
a. Set Interface to Enable.
b. Set Pulse Duration to 40 usec.
c. Set Bit Period to 2140 usec.
d. Set Data output to Bypass mode.
4.2.2 Card Formats
The following should be configured in System Administration on the Card Formats form.
1. Click [Modify].
2. Set the Application to IrisAccess (iCLASS).
Note: When encoding with the iCAM, the application key and memory configuration in OnGuard are
not used. Instead, the application key should be configured using the IrisAccess Web page.
3. Next to the Iris Data Encryption Method, click [Change].

4. Select the Iris Data Encryption Method (AES, DES, or DES3) from the drop-down.
5. Click [Generate New Key].
6. Click [Store Key to File]. Note the location of this file. It will be used for configuration in the
iCAM4000V Web user interface.
Once the card format is configured, assign the SmartCard format to the badge type. This can be done in
System Administration or ID CredentialCenter in the Badge Types Folder, on the Encoding Form. For more
information, refer to the System Administration or ID CredentialCenter User Guides.
revision 3 — 31
Iris Recognition
4.3 Installing an iCAM7000
The iCAM7000 can be configured to emulate either the iCAM4000 or the iCAM4000V.
Note: For OnGuard compatibility, the iCAM7000 requires firmware version 7.05.01 or later.
1. Run the wiring for the iCAM7000.

• If the installation will emulate the iCAM4000, then this wiring will include an ethernet connection
between the iCAM7000 and the ICU.
• If the installation will emulate the iCAM4000V, then this wiring will include a Wiegand connection
between the iCAM7000 and the reader interface module.
2. Prepare the mounting location for the iCAM7000.
3. Use the following two diagrams to wire the iCAM7000. Use the first diagram if the installation will
emulate the iCAM4000. Use the second diagram if the installation will emulate the iCAM4000V.
WIB4000 and Reader Interface Wiegand connection to support iCAM4000 emulation

TB8
READER 1
D0 D1
READER 2
D0 D1
TB9
Dual Reader
Interface Module
TB10
C NC
RLY 1
GND
NO
Wiegand OUT 1
NC
RLY 2
NO C
TB11
C NC
RLY 3
NO
NC
RLY 4
NO C
WIB4000
C NC
RLY 5
NO
NC
RLY 6
NO C
TB12
32 — revision 3
iCAM7000 and Reader Interface Wiegand connection to support iCAM4000V emulation

TB8
READER 1
D0 D1
READER 2
D0 D1
TB9
Reader Interface
Module
(LNL-1320
shown)
DATA 1
DATA 0
GND
Wiegand OUT
iCAM7000
4.3.1 Configuring the iCAM7000
The iCAM7000 is an iris camera supported by the OnGuard system. However, PIN pad functionality is not
supported. Each iCAM7000 unit requires an Ethernet network connection for iCAM configuration, and 12
to 24 VDC +/-10% @ 2.0 A maximum power.
iCAM7000 Hardware Guide and the IrisAccess Web Configuration Interface Guide for iCAM Series.
iCAM Network Settings
Once the iCAM is connected, log into the camera and set the IP address, subnet mask, and default gateway
for the iCAM. Each iCAM must be changed individually. Do not connect more than one unconfigured
iCAM to the network at any one time to avoid IP address conflicts.

revision 3 — 33
Iris Recognition

iCAM Operational Mode
Perform the following procedure to make the iCAM7000 emulate either an iCAM4000 or an iCAM4000V:
1. Log into the iCAM7000 configuration Web page.

2. From the main menu, select Operational Mode.
a. To configure the iCAM7000 to emulate an iCAM4000, select Option 1. For more information,
refer to Configuring the iCAM4000 on page 23.
b. To configure the iCAM7000 to emulate an iCAM4000V, select Option 2. For more information,
refer to Configuring the iCAM4000V on page 29.
c. OnGuard does not support Option 3.
4.4 Enrollment
Note: Enrollment must be done with an iCAM4000, or an iCAM7000 configured for Option 1. You
cannot do enrollment with an iCAM4000V.
To use the iCAM for capturing iris data and enrolling, it should be connected to the network, but should not
be connected to an ICU. Use a workstation to access the iCAM for enrollment.
To disconnect the iCAM from the ICU:
1. Open IrisICUAdmin4000.
2. Uncheck the channel to which the iCAM is connected.
3. Click [Send to ICU].
In addition to the configuration that was done through the IrisAccess Web interface, the iCAM unit must be
configured in the access control software:
1. On the Encoders/Scanners form, on the General tab, enter a name for the iCAM.
2. Select the workstation name.
3. For the Device type, select IrisAccess iCAM (iCLASS).
34 — revision 3
4. For the Credential technology, select iCLASS.

5. On the Communications tab, enter the IP address. This IP address must match what was set up for the
iCAM network settings.
Iris capture and verification can then be performed from Multimedia Capture, accessed on the Cardholders
form. For detailed information, refer to the System Administration User Guide or ID CredentialCenter User
Guide.
Note: Encode the card twice: once to encode the eyes on the card, and again to encode the cardholder
badge information.
Limitations
The current system architecture does not permit the use of a camera for both enrollment and verification
purposes. When connecting to an iris camera, connect only one workstation at a time.
4.5 Verification
In System Administration, configure IrisAccess biometric and HID (iCLASS) AccessControl smart card
formats for encoding cardholder data. The reader’s card format should be Wiegand. Set the Encryption
method to AES/DES/DES3 in the card format application.
Biometric and access control data must be encoded on the badge. Connect and configure an HID (iCLASS)
RW4000 Prog encoder. Assign the configured smart card formats to a badge type (for instance, to
Employee) for the encoding procedure. Choose a cardholder with a valid badge and iris biometric templates
and encode the cardholder's data to blank 16K/2 or 16K/16 Application Areas.
Verify the data encoded by presenting the encoded badge to the HID iCLASS reader inside the iCAM, or an
external reader wired to the iCAM.
The current system architecture does not permit the use of a camera for both enrollment and identification/
verification purposes.
Note: When presenting the card for verification, keep the card positioned on the reader after it beeps
and announces “Please center your eyes in the mirror.” Do not remove the card until instructed
to “look into the camera”.
4.6 Software Upgrades
Refer to the manufacturer documentation included with the device to upgrade the software for the ICU
(iCAM4000), or use the iCAM Web page to upgrade an iCAM4000V or iCAM7000. The upgrade procedure
might vary depending on your current version of the software, so use the appropriate documentation.
Firmware upgrades, if applicable, are performed to the iCAM4000V or iCAM7000 using the Web user
interface.
revision 3 — 35
Iris Recognition
36 — revision 3
5 Onity Programmer
The Integra extended portable programmer (XPP) is used to transfer data to electronic locks. For
information about operation of the programmer, refer to the manufacturer documentation.
5.1 Configuration for Onity
Setup of the programmer should be performed according to the manufacturer’s instruction. The device must
be configured in OnGuard as well. For OnGuard configuration, refer to the System Administration User
Guide.
To transfer data between the computer and the XPP, use a 9-pin null modem RS-232 cable (40 feet
maximum). The 9-pin RS-232 port is located at the top of the device. Connect this to the serial port of the
computer.
revision 1 — 37
Onity Programmer
38 — revision 1
6 Personal Safety
Visonic SpiderAlert can be utilized with the OnGuard system. It is an emergency communication and
signaling system for personal security and property protection.
Before continuing, verify that you have a license for OnGuard with the personal safety feature enabled. The
ability to use personal safety controllers is a count-based licensed feature.
6.1 Visonic SpiderAlert
The SLC-5 (SpiderAlert Local Controller) is the main controller designed for the SpiderAlert 5 signaling
network.
The SLC-5 can have up to 255 downstream bus devices (Receivers and Input/Output units). The SLC-5 can
also have one input as well as two outputs.
A standard RS-232 cable can be used to connect the host computer to the SLC-5 via the SLC-TO-SSK
Adapter. A six-wire cable with RJ-11 connectors at both ends is used to connect the SLC-TO-SSK Adapter
to the SLC-5.
A connection can also be made via LAN using a Lantronix device. When using a Lantronix device, the
following settings must be configured.
• Baudrate = 9600
• I/F Mode = 4C
• Flow Control = 02
Type in the encryption key as it is in the Encryption Controller form in System Administration.
Note: The ID numbers for bus devices can be found printed on the circuit boards, the back of the
plastic housing, or on the packaging.
6.1.1 DIP Switches
The SLC-5 has two DIP switches, SW1 and SW2. The correct settings for the DIP switches depends on the
action the SLC-5 is performing. The various DIP switch settings are:
• Programming the SLC-5 (SW1 and SW2 OFF)
• Single-Site Direct Connection to Computer (SW1 and SW2 ON)
• Multi-Site Connection via Short-Range Fast Modems (SW1 OFF, SW2 ON)
• Multi-Site Connection via Telephone-Line Modems (SW1 ON, SW2 OFF)
OnGuard currently supports the “Single-Site Direct Connection To Computer” operating mode. For this
mode, SW1 & SW2 DIP switches need to be set to the ON position on the SLC-5. When configuring a
Spiderbus Controller (SLC-5), the SW1 and SW2 DIP switches must be set to OFF. After programming of
the Spiderbus Controller (SLC-5) is complete, SW1 and SW2 must be set back to ON.
revision 1 — 39
Personal Safety
6.1.2 Supported Transmitters
The following transmitters are curently supported.
MCT-101 S MCT-102 S MCT-104 S
MCT-201 S MCT-201 AT S MCT-201 WP S
MCT-211 S MCT/IR-201 S MCT-100 S
MCT-302 S MCT-101 MD S MDT-122 S
MCPIR-2000 S MCPIR-3000 S SPD-2000
SPD-1000 SPD-3000 MCT-501 S
MCT-432 MCT/IR-252WPS MCT-425 S
The configuration for this device is done in System Administration, on the Personal Safety Devices (PSD)
folder. For more information, refer to the System Administration User Guide.
40 — revision 1
7 Receivers
Receivers expand the number of localized security and safety systems that can be monitored from an Alarm
Monitoring workstation. Follow the instructions for setting up receivers below. For additional information,
refer to the manufacturer documentation.
Supported Receivers:
• Bosch 6500
• Bosch 6600
• Osborne-Hoffman OH-2000
• AES-IntelliNet 7000
Alarm communications over a network are supported. Alarm panels can send full data messages via the
LAN to a receiver.
7.1 Bosch D6500/D6600 Receiver
These receivers are configurable for the following output formats: SIA, 6500, Modem II/IIE/III a2, and
BFSK. Each of these modes handles the default and SIA event code templates stored in the database
differently. Therefore, an event that is generated in 6500 mode would be reported in Alarm Monitoring
differently than an event in SIA mode.
A NULL modem cable is required to connect a host computer to the D6500/D6600 receiver. The receiver is
programmed using the Bosch keypad. The receiver connects via COM 3 on the back of the unit. For more
information, refer to the manufacturer manual.
Note: For a list of supported protocols, refer to the Bosch documentation.
7.1.1 Firmware Requirements
In order to work with OnGuard, the Bosch D6500 requires a minimum firmware, based on the Main
Processing Unit (MPU).
MPU number Minimum firmware requirement
D6510 8.03
D6511 1.06
revision 3 — 41
Receivers
In order to determine the MPU number and firmware version, perform the following procedure:
1. Disconnect the backup battery in the receiver.

2. Turn the receiver power off.
3. Wait 10 seconds.
4. Turn the receiver back on.
5. The LCD will display the line card, MPU, printer version, and firmware version.
D6500 receivers with a firmware that is lower than what is specified are not supported. If you attempt to
connect a receiver not meeting these specified requirements, the receiver will fail to come online in Alarm
Monitoring.
For the D6600 receiver to work with OnGuard, there is no minimum firmware requirement.
7.1.2 Bosch Receiver Configuration
The following must be configured on the receiver in order for it to work properly.
Note: For more information, refer to the Program Entry Guide which is included with the receiver.
Output Mode
In order to configure the different output modes for the receiver, enter into the Automation Configuration
menu on the receiver. In order to do this you need to do the following:
1. Press the [M/E] button on the front of the receiver.

2. You will be prompted for a password. Enter the password configured for the receiver and press [M/E]
again.
3. A message will appear indicating that you are logged in. Use the up and down arrows to navigate to
different sections.
4. Using the down arrow, go to CPU Configuration. Press [M/E] again.
5. Once again use the down arrow to go to the Automation Configuration item and press [M/E].
6. In the menu, go to the entry labeled Output Format. One or two formats will be listed, depending on
the current format: one for the 6500 output mode and one for the SIA format.
• To change this setting, press the [M/E] button, then press either 1 or 2 for the output desired. Then
press [M/E] again.
7. Ensure that the proper automation configuration reporting is configured for the receiver. To check this:
a. Use the arrow to navigate to 6.0 Network Configuration. Press [M/E].
b. Next, navigate to 6.3.7 Device. Press [M/E].
c. This menu item must be set to 2 to use the COM3 port for RS-232 automation output and event
reporting. If this value is set to 1, automation output and event reporting will be routed through the
42 — revision 3
COM4 Network Adapter. If this value is not set to 2 then the receiver will not come online and
events will never be received by the Communication Server.
8. Log out of the system. To do this, press the [CAN] button until the standard screen with date and time is
displayed.
When in the Automation Configuration section of the receiver settings in this screen, you can modify the
Heartbeat Interval, Start Character (HEX) and End Character (HEX) as well as communication settings
(such as baud rate, byte size, parity, and stop bits). These items are listed in the receiver menu under
Automation Configuration as follows:
Baud Rate Default = 1200
Data Bit Default = 8
Parity Default = none
Stop Bit Default = 1
Link Test Default = 30-second heartbeat interval
Header Default = 0x0
Trailer Default = 0x14
7.1.3 Configuring Receiver Communications
The Bosch receiver can be connected to a host computer and can communicate through OnGuard in one of
two ways:
• Direct connection of the host machine and the receiver using a null modem cable
• Connection of the receiver through a Lantronix box using a null modem cable
If a LAN connection will be used, configuration of the communication settings in the Lantronix box will
differ from configuration for use with Lenel hardware.
You can also gather debug information when connected to the Bosch panel in 6500 or SIA modes. These
debug files can be turned on by creating a new section in the acs.ini file. These settings are as follows:
For Bosch 6500, add the following to ACS.INI
[6500]
6500Debug=1
The file generated will be “6500Debug.txt” and will be located in the logs directory.
For Bosch SIA, add the following to ACS.INI
[SIA]
SIADebug=1
The file generated will be “SIADebug.txt” and will be located in the logs directory.
For more information, refer to the Bosch Communications Receiver/Gateway manual.
revision 3 — 43
Receivers
7.2 Osborne-Hoffman OH-2000
When connecting to the OH-2000, use a straight through 9-pin serial cable. Connect one end of this cable to
the computer automation port of the OH-2000. This port is located at the top left in the back of the receiver.
You may connect the other end of the cable either directly to an OnGuard server or to a Lantronix box,
configuring a connection to the panel over the network.
Many different types of downstream devices can be used to report into this receiver. The output format for
the OH-2000 receiver can be Bosch SIA 1, SIA 2, SIA 2000, Bosch Modem II, IIE, III a2, or Bosch BFSK.
7.3 AES-IntelliNet 7000
OnGuard integrates to the AES-IntelliNet receiver when programmed to output using the Bosch 6500 output
format.
The AES-IntelliNet receiver can be connected to a host computer and can communicate through the
software. A direct connection can be made by making a serial connection between the host automation port
of the receiver and an available COM port on the host computer. For direct connections, the flow control
cannot be configured. This is hard-coded in the software.
For builds later than 5.10.309, the following changes are NOT needed. For build 5.10.309 and earlier, if you
are using a direct connection, a change must be made to the ACS.INI file. Make the following modification
to this file:
[Radionics6500]
DtrControl=1
Note: With this setting in the ACS.INI file, a Bosch D6600 receiver cannot be used with the 6500
output mode.
The AES-IntelliNet receiver must be configured for Bosch 6500 output mode. Also note that since the AES
receiver does not have a start character, zero (0) should be used. The end character must be 0x0014. For
more detailed instructions, refer to the AES-IntelliNet manual.
A LAN connection can also be made by using a 9-pin to 25-pin connector and connecting this to the
Lantronix unit. For more information, refer to IP Support.
It is possible to integrate with the AES IntelliNet receiver model 7750-UL and subscriber transceiver unit
model 7450 RF or model 7750-F.
A LAN connection can be also encrypted by using a Lantronix device SDS1100 or SDS1101; the encryption
connection settings should be configured as follows:
• Baud rate = 1200
• I/F Mode = D8
• Flow = 02
44 — revision 3
For more wiring information, refer to the AES IntelliNet 7000 Series Receiver Installation and Operation
Manual.
Pin number Signal I/O At 9-pin At 25-pin

7000/2
2 Transmit data O 2 3
3 Receive data I 3 2
4 Data term ready I 4 20
5 Signal ground - 5 7
6 Data set ready O 6 6
7.4 Verex HSC-IP Receiver
OnGuard integrates to the Verex HSC-IP receiver when the receiver is configured as follows using HSC-IP
Setup.
7.4.1 Program Section: A0001 (Accounts)

• A0001:00 (Keypad Selections)
- Account Defined must be yes.
- Account Suspended must be no.
- LCD Name is not required, but can be up to 12 characters long.
• A0001:01 (Keypad Selections)
- Account ID must be filled in with the accounts that are identified for an intrusion panel. For NGP
panels, the account number configured in IP Central Station > Reporting > Account Number
must be defined in HSC-IP setup.
- Main Controller Serial Number is limited to five digits, but the NGP serial number contains more
than five digits. This requires converting the NGP serial number to fit into 16 binary digits. Take
the panel’s serial number and convert it into binary, then take the last 16 binary digits and convert it
back into decimal. Enter this number into the Main Controller Serial Number field.
a. For example, if the NGP serial number is 237560, the binary conversion is
111001111111111000.
b. Take the last 16 digits (1001111111111000) and convert it back into decimal (40952).
c. Enter this number into the Main Controller Serial Number field.
Note: OnGuard 6.5 and later contains an IP account number field for areas other than the Default
Area. This field is located on the Access Control > Areas > Intrusion Detection tab. If an IP
account number is configured here, then this account number/serial number combination must
be configured in HSC-IP Setup.
revision 3 — 45
Receivers
46 — revision 3
8 Cypress Timer
The Cypress Timer (LNL-CCK-1201-M/LNL-CCK-1204-M/LNL-CCK-1401) is ideal for Time and

Attendance applications where the Access Control System’s time must be displayed. Up to 32 clocks can be
driven from one time source over a single twisted pair network. The enclosure is weather resistant making it
ideal for exterior installation.
CYPRESS
Computer Systems, Inc.
• Adds time of day displays to Access Control and Time & Attendance Systems
• Low profile facilities mounting at reader location
• Can be used indoor or outdoor
• Standard or Military Time Formats
• FCC Part 15
revision 1 — 47
Cypress Timer
8.1 System Level Wiring
RS-485
power
Power Supply Multi-Drop,

Central Power
ISC
RS-485
12 VDC 12 VDC 12 VDC
Multi-Drop, Local Power

ISC
RS-485
Multi-Drop, Daisy-Chain and Home-Run
Power Supply
ISC
48 — revision 1
Front of unit
5.3
3.5
1.3 1.0
3.25
3.4
Back of unit with base plate removed

+12 VDC
ISC
RED
GND
BLACK
+ +
GREEN
TR1+
YELLOW
TR1-
R1 +
R1 -
GND
+ + Note: Timer cannot be

on a port without
devices defined in the
software application
RED
Note: When attaching connector, red wire

must be on red terminal
8.2 DIP Switches
DIP switches are used to control the protocol. OnGuard uses Mercury Protocol 2. This means that DIP
switches 1 and 2 should be in the ON position. DIP switches 3, 4, 5, 6, and 7 should be off.
revision 1 — 49
Cypress Timer
DIP switch 8 is used for the time mode. Turn DIP switch 8 ON for 24-hour mode; off for 12-hour mode.
1 2 3 4 5 6 7 8
If an undefined format is selected, the display will read --:--.
8.3 Time Displays: Functional Description
The clocks are used to display the time from the ISC. When the ISC sends a time stamp to the clock, the
clock’s internal time base is updated; however, the clock’s time stamp is not used. The time stamp that
comes directly from the ISC is still used. In other words, the clock's internal time base is updated but is not
used unless nothing is received from the ISC or there is a loss of clock information. In order to use DST
(Daylight Savings Time), this option must be turned on in the software application for that panel.
ISC
RS-485
If there is a communication loss between the ISC and the clock, the clock uses its internal time base to
update the clocks. A loss of communication is defined as 1 minute and 10 seconds without receiving a valid
time stamp from the ISC. In normal operation, the colons “:” blink at 1 second intervals. This indicates that
the clock is communicating with its Clock Driver. If the colons are steady, this indicates a communication
failure.
50 — revision 1
Base plate
5.164
4.264 .45
1.45
0.50
0.16 0.16
2.90
3.114
.932 1.65 .20

2.582
3.30
0.80
0.50
revision 1 — 51
Cypress Timer
Cover
5.3
.55
3.5
.90 1.3 .90
3.25
1.4
52 — revision 1
8.4 Wall Mounting
Mount enclosure to wall with electrical box (single gang).

Top View
wall
harness
CCK-1201
Top View
wall
revision 1 — 53
Cypress Timer
54 — revision 1
9 TVS TVC-2100 Series Video Text Inserter
The Multiple Register Text Inserter is designed to communicate with up to 10 register interfaces. It
superimposes transaction information onto corresponding video of the cashier on a one register per channel
basis. The text inserter is installed between the cameras and the video processor, may be used with analog or
digital recorders, multiplexers, quads, etc. The composite image with the text overlay can be viewed live or
reviewed later from a video recorder. Questionable transactions such as VOID and NO SALE can be
reviewed easily by using the flashing text alarm features. In addition, both the single and multiple interface
text inserters are compatible with the CYA Management Software Package.
This system can be integrated with OnGuard through the TVC-2104.
9.1 Firmware
Two types of firmware have been tested so far: version 5I and version 13.
Version 5I requires a special cable to communicate to the TVC-2104.
Version 13 firmware allows you to connect the TVC-2104 to a TVC-1030A unit. A standard serial cable can
be used for receiving transactions; however, a different cable must be used initially. In order to start
receiving the transactions, you need to send the unit a request for the version information using a different
cable. Once this is done, the standard cable can be used.
9.2 TVC-2104 Hardware
The TVC-2104 communicates with a workstation via serial or LAN connection. Use the connectors on the
back of the unit.
• COMPUTER Used to connect the unit to a host computer. It is required in order to connect to the
Communication Server.
• ALARMS Can be used to provide an alarm output per channel. The outputs are open-collector outputs
that simulate a normally open dry contact relay. These connectors are not required for OnGuard integration.
• 12VDC Supplies power to the unit.
• VIDEO OUT There are four NTSC video outputs (one per channel). This video from these connectors
is a result of input video with text inserted over it.
revision 1 — 55
TVS TVC-2100 Series Video Text Inserter
• VIDEO IN There are four NTSC video input connections (one per channel). For a video out signal, a
camera must be connected!
• TERMINAL STRIP This is the terminal strip that is located above the ALARMS connector. Connect
the 2100 Series Text Inserter with the register interfaces here.
9.2.1 Serial Connection
Use a standard serial cable to connect the TVC-2104 and the host. (If you are using version 5I firmware you
will need to use a special cable.) The back of the TVC-2104 has a 25-pin female connector labeled
COMPUTER, so you will need a cable that has a 25-pin male end and most likely will require that the other
end has a 9-pin female connector to plug into the serial port of the computer.
Cable pinouts
DB-9 female DB-25 male
2 3 (Receive)
3 2 (Transmit)
5 7 (Ground)
If version 5I firmware is being used, a special cable is required. This cable has two connections on one end,
one of which will be labeled “DVR/1036A.” Use this cable to connect to the host PC running the
Communication Server.
Cable pinouts
DB-9 female DB-25 male
2 19 (Receive)
3 20 (Transmit)
5 7 (Ground)
9.2.2 LAN Connection
The TVC-2100 Series units can communicate with the Communication Server via LAN with the use of a
Lantronix device.
A serial cable is required, but you will need a different connector to plug into the Lantronix box.
You will also need to configure the Lantronix box with the appropriate settings:
• Baud rate: 9600
• Flow control: CTS/RTS
• Byte size: 8
• Stop bits: 1
• Parity: none
56 — revision 1
9.3 TVC-2104 Operation
Before powering up the TVC-2104, make sure all the register interfaces are powered up. Otherwise, the
TVC-2104 may not recognize all the register interfaces.
The message, “Interfaces Attached,” will appear on the monitor after the TVC-2104 has completed
initialization (this will take approximately 10 seconds). Make sure the number of interfaces is correct. If
there are too few, a register interface may not be responding.
The message, “No Interfaces Attached,” indicates that when the TVC-2104 powered up, it did not receive a
response from any of the register interfaces.
Front of TVC-2104 unit
• PROGRAM Plug in a touch-tone telephone for programming the device here. The normal
programming that is specified in the TVC-2100 Series Video Text Inserter Operation and Installation
Manual is not available when the unit has version 5I firmware installed.
• DIAGNOSTIC LED Indicates errors and other diagnostic conditions.
• LINE LED Flashes when the unit is communicating with the register interface.
• POWER LED Indicates that the unit is properly connected to power.
revision 1 — 57
TVS TVC-2100 Series Video Text Inserter
58 — revision 1
10 Corex CardScan
These instructions are for installing and configuring either the Corex CardScan 300 or the Corex CardScan
600c.
10.1 Corex CardScan Installation and Configuration
1. Install the CardScan software on your PC. This must be done before connecting your scanner. To install
the scanner, refer to the Corex documentation.
2. Connect the AC adapter to the scanner. Plug the AC adapter into a power outlet.
3. Using the included USB cable, connect the scanner to the USB port on your PC.
4. Start the CardScan software and make sure that the business card scanner is functional. Note that after
the CardScan software has been run initially, it does not need to be running in order for the business
card scanner to work with the OnGuard software.
5. Calibrate the business card scanner. Refer to the Corex documentation on how to calibrate the scanner.
6. In FormsDesigner, assign the vCard value to user-defined fields (UDF).
7. Use the business card scanner in the Cardholders folder in System Administration, ID CredentialCenter,
Digital Video, or Visitor Management.
revision 1 — 59
Corex CardScan
10.1.1 Assign the vCard Value to UDF Fields
1. Start and log into FormsDesigner. When prompted, open the Cardholder or Visitor form, depending on
which you wish to map fields for. For more information, please refer to the Introduction chapter in the
FormsDesigner™ User Guide.
2. The scanner will only recognize fields that are currently assigned the vCard value. The vCard value is
assigned by simply double-clicking on a field and selecting the field’s name in the vCard drop-down
list.
3. The following vCard fields are currently mapped to the Corex CardScan scanner fields:
vCard value Field vCard value FormsDesigner form(s) the

is assigned to by field is located on
default
First Name First name Cardholder, Visitor
Home Telephone Phone Cardholder
Internet Email E-mail Cardholder
Last Name Last name Cardholder, Visitor
Middle Name Middle name Cardholder, Visitor
Organization Name Organization Visitor
Title Title Cardholder, Visitor
Work City City Cardholder, Visitor
Work State State Cardholder, Visitor
Work Street Address Cardholder, Visitor
Work Telephone Office phone Cardholder, Visitor
Work Zip Zip code Cardholder, Visitor
If a vCard property is not assigned to any field on a FormsDesigner form by default (i.e., Name Prefix,
Name Suffix, Work Country, Fax, and Organization Name), a field can be added and assigned that
particular vCard property.
10.1.2 Import Data Using the Corex CardScan
You can import data using the Corex CardScan whenever you are asked to manually enter cardholder or
visitor information. This includes adding, modifying, or searching for cardholder or visitor records. You can
also import in the Visits folder when you are searching for a visitor or cardholder. This example describes
how to import data when adding a cardholder.
1. In the Cardholders folder, click [Add].

2. If segmentation is not enabled, skip this step. If segmentation is enabled, the Segment membership
window opens.
a. Select the primary segment and any additional segments that this badge type will be assigned to.
60 — revision 1
b. Click [OK].
3. In the Person type field, select whether the record will be cardholder or a visitor record.
• If “Cardholder” is selected, the Cardholder form is displayed.
• If “Visitor” is selected, the Visitor form is displayed.
4. Place a business card, face down, in the business card scanner.
5. Click [Import].
6. The Select Import Source window opens. Select “Corex CardScan scanner,” then click [OK].
7. The scanner will scan the business card, and the fields on the Cardholder or Visitor form will be
populated with whatever information can be determined.
8. Make sure that the information is correct, then click [OK]. The record will then be added.
revision 1 — 61
Corex CardScan
62 — revision 1
11 RFIDeas Readers
This chapter describes the configuration of RFIDeas wedge readers.
Download the configuration software from http://www.rfideas.com/Software (address is case sensitive).

• For the HID iCLASS AIR ID, AIR ID Playback, AWID Prox, and HID Prox readers, download
pcProxConfig.exe.
• For the MAG Swipe reader, download pcSwipeConfig.exe.
Before performing the configuration steps described in the following sections, connect the device to the PC
and wait for Windows to indicate that the installation was successful. No additional software or drivers are
required.
11.1 HID iCLASS AIR ID (Model: RDR-7081AKU) and AIR ID Playback

(Model: RDR-7585AKU) Readers
These readers authenticate with the secret HID key, and then read Book 0, Page 0, and app1. They then read
the data encoded into the HID iCLASS Access Control Application.
When reset to factory defaults, these readers do not send the badge ID when a badge is swiped. To configure
the reader for the typical 26-bit badge card format:
1. Install and open the pcProxConfig software.

2. Select the Connect tab.
3. Reset the reader by clicking [Reset to defaults].
4. Select the Set Keystroke Data tab.
5. Select the Send ID Code check box.
6. Click [Write to pcProx or AIR ID].
The following configuration is sent to the reader:

• Even parity bit = bit 0 (there is one parity bit at the beginning)
• Facility Code start bit = 1
• Facility Code number of bits = 8
• Badge ID start bit = 9
• Badge ID number of bits = 16
• Issue Code start bit = 0
• Issue Code number of bits = 0
• Odd parity bit = 26 (there is one parity bit at the end)
revision 3 — 63
RFIDeas Readers
To test the reader configuration:
1. Open Notepad.
2. Swipe an iCLASS badge from the lot of encoded cards.
The badge ID that was encoded on the card should now appear in Notepad. If so, the reader is ready for
operation with OnGuard System Administration and ID Credential Center.
3. Open the Cardholder form and swipe a badge at the reader. OnGuard should automatically open a
Wedge Reader dialog filled with the badge ID, and then a search is started. If 0 of 0 cardholders is
presented then no cardholder has that badge. If there is a match then that cardholder is shown.
When working with a non-26 bit card, you might need to use pcProxConfig to configure the Leading Parity
or Trailing Parity to mask out the bits that are not part of the Badge ID, and also modify the Bit count of ID
portion only.
For example, if this 64-bit format is encoded on the card:

• Even Parity Bit resides at bit 0
• Facility Code start bit=1
• Issue Code Start Bit = 56
Then the reader would require this configuration:

• Strip parity bit count: Leading Parity = 1
• Send ID Code is selected
• Bit count of ID Portion only = 48
• Strip parity bit count: Trailing Parity = 9
11.2 HID Prox Reader (Model: RDR-6081AKU)
This reader reads the Wiegand Data load of a HID Prox/Prox2 badge.
When set to factory default, this reader will output the badge ID of the typical 26-bit card format with the
following parameters:
64 — revision 3
If you need to configure the reader for another Wiegand bit format, use the pcProxConfig and AIR ID Enroll
software:

Note: pcProxConfig version 4.4.6 has a defect. On the Set Keystroke Data tab, the Bit count of ID
portion only field is not editable until the Send ID Code check box is unchecked and then re-
checked.
When working with a non-26 bit card, you might need to set the Leading Parity or Trailing Parity to mask
the bits that are not part of the badge ID.
For example, if this 64-bit format is encoded on the card:

• Even Parity Bit resides at bit 0
• Facility Code start bit=1
• Issue Code Start Bit = 56
Then the reader would require this configuration:

• Strip parity bit count: Leading Parity = 1
• Send ID Code is selected
• Bit count of ID Portion only = 48
• Strip parity bit count: Trailing Parity = 9
revision 3 — 65
RFIDeas Readers
11.3 AWID Prox (Model: RDR-6981AKU)
When reset to factory defaults, this reader does not send the badge ID when a badge is swiped. To configure
the reader for the typical 26-bit badge card format:

4. Select the Set Keystroke Data tab.
5. Select the Send ID Code checkbox.
6. Click [Write to pcProx or AIR ID].
The following configuration is sent to the reader:

11.4 MAG Swipe (Model: MS3-00M1AKU)
This reader reads from Tracks 1, 2, and 3. By default, OnGuard uses Track 2 for access control data. By
default, the reader outputs all data from tracks 1and 2 with a carriage return (<Enter>) between each track of
data.
• The default Mag card format in OnGuard is a 12-character Mag format.
• The format starts with five digits of facility code data, followed by six digits of badge data.
66 — revision 3
If you want to capture Badge ID data from Track 2, configure the device as follows:
1. Connect the MAG Swipe reader to a USB port on your PC.

2. Install and open the pcSwipeConfig software.
3. The software opens with the Connect tab selected. Click [Scan/Connect] to find the connected reader.
4. Click [Factory] at the top of the window. This sets the reader to factory defaults.
5. Select the Fields tab.
6. Swipe an encoded badge. Data populates the shaded area of the window.
Also, in the left column of buttons, [User Field 1] and [User Field 2] are active, and are colored green.
7. Click [User Field 1]. The data that populated the shaded area highlights in yellow on the first row.
8. Notice that [User Field 1] has a data selection of Track = 1 and Field = 0.
Using the Track field’s arrow buttons, change the value from 1 to 2. Notice how the highlighted data
changed from the first row of data to the second row of data.
9. Using the Field field’s arrow buttons, change the value from 0 to 1. Notice that some additional
configuration fields appear.
This highlighted data contains the Facility code, Badge ID and Issue Code from Track 2 of the Mag
badge.
10. To isolate only the badge ID, change the Offset field so that the highlighted data begins immediately
after the facility code value.
Change the Offset field’s value to 5, and change the Length field’s value to 6. The highlighted data now
contains only the Badge ID.
11. Click [User Field 2]. Deselect the Enable check box.
12. Send this configuration to the reader by clicking [Flash] at the top of the window. The reader beeps
when complete.
13. Open Notepad, and then swipe the badge. Only the badge ID, with leading zeros if present, is displayed.
14. Open OnGuard System Administration or ID Credential Center, and then select the cardholder form and
swipe your Mag badge. A Keyboard Wedge Scan Data popup opens, and the badge ID data is
populated. Click [OK] to search for a cardholder with that badge ID.
revision 3 — 67
RFIDeas Readers
68 — revision 3
12 Cypress Wedge
The wedge reader can be used to aid the enrollment process. It automatically adds Wiegand data to badging
or enrolling workstations. It converts badge information into keystrokes.
12.1 Cypress Wedge WDG-4413
The Cypress Wedge WDG-4413 uses the PS/2 keyboard interface.
Connect the terminal, keyboard, and reader to the wedge. For detailed information, refer to the Cypress
documentation.
When a badge is swiped, the five digit facility code and five digit badge number are converted to equivalent
keystrokes. When enrolling a cardholder (after clicking [Add]), the cursor should be placed in the correct
revision 1 — 69
Cypress Wedge
field for the data to be populated. If this is not done prior to swiping a badge, a Search dialog will open,
allowing for a search on the badge ID.
In order for the wedge reader to function properly, a change must be made in the ACS.INI file. Under the
section [WEDGESCAN], specify the value for StartByte.
12.2 Cypress Wedge WDG-5912
The Cypress Wedge WDG-5912 uses a USB keyboard interface. Connect it to the PC using the USB port. If
you are programming, an additional connection to the COM port on the PC is also needed.
To USB Port on PC
To Com Port on PC (Only used for Programming )
Reader
Connections
LED (Brown )
Data 1 (W hite)
D ata 0 (Green )
+5 VDC (Red )
GND (Black)
N/C
Power
Supply voltage: 5 VDC from USB interface.
Supply current: 100 mA.
Readers requiring more than 100 mA for current or more than 5 VDC for power will require an external
power supply. When using an external power supply, there must be a common ground between the wedge
and reader.
Important: External power should NOT be applied to +5 VDC connection on wedge.
70 — revision 1
12.2.1 Device Drivers
There are no drivers to install in order to use this device. The WDG-5912 is installed as a USB Human
Interface Device, which already has a driver available in Windows.
12.2.2 Resetting the Unit
If it is necessary to reset the WDG-5912 to factory default parameters:
1. Remove the cover.

2. Unplug the USB cable from the wedge.
3. In-stall a jumper on J5.
J4 J5
4. Plug the USB cable back in to apply power to the wedge.

5. Wait at least 30 seconds.
6. Unplug the USB cable again and remove the jumper from J5. (You may store the jumper on one pin of
the header if you wish.)
Factory default parameters of the WDG-5912
revision 1 — 71
Cypress Wedge
72 — revision 1
13 DigiOn24 Encoder
The DigiOn24 (D24) encoder is available as a standlaone or inline contactless encoder commonly used in
direct card printers. It can support iCLASS, MIFARE, or DESFire technology.
13.1 Installation
If you are using the inline encoder, it is located inside the card printer. The printer must be installed first.
After installation, the printer will then be selectable when configuring an inline encoder.
If you are using the standalone encoder, it connects to the computer via USB and you will need to install the
USB to Serial driver. For more details, refer to the manufacturer documentation.
13.1.1 Installing the Standalone Encoder
1. Obtain the driver either from the Supplemental disc or by downloading it from http://
www.ftdichip.com/Drivers/VCP.htm and extracting it on the computer where the encoder will be
installed.
2. Connect the encoder to the computer.
3. When prompted, specify the location of the driver on the computer (this may have to be performed
twice). Once it is installed successfully, it will show up as a serial device named “USB Serial Port”
under the Ports section of the Device Manager.
4. In the Device Manager, under Ports, right-click on the device and select Properties.
5. On the Port Settings tab, click [Advanced].
6. Select a COM port number that is available. Click [OK]. (This COM port number will be used in the
OnGuard configuration of the encoder.)
13.2 Configuration of the Encoder
To configure the encoder in System Administration or ID CredentialCenter:
1. From the Administration menu, select Workstations.

2. On th e Encoders/Scanners tab, click [Add].
3. On the General sub-tab:
a. Type in a unique name for the encoder.
b. Enter the name of the workstation to which it is connected.
c. For the device type, select Digion24 (iCLASS) if you are encoding iCLASS or Digion24
(MIFARE) for MIFARE or DESFire.
Note: Firmware version 4.92 or later is required for encoding the DESFire TWIC application.
d. Select the credential technology.

4. On the Location sub-tab:
revision 1 — 73
DigiOn24 Encoder
a. For standalone encoders, select the radio button indicating This is a standalone device.
b. For inline encoders, select the radio button indicating This is an inline device that resides within
a card printer. From the drop-down list, select the card printer in which the DigiOn24 encoder is
installed, and/or the encoder station.
5. On the Communucations sub-tab, select the COM port to which the unit is connected and use the
default settings. The default communication settings are as follows:
• Baud rate: 9600
• Data bits: 8 bit
• Parity: Even
• Stop bits: 2
6. Click [OK].
After this is done, configure a card format for the smart card application. This can be done in System
Administration or ID CredentialCenter in the Card Formats folder.
done in the Badge Types folder, on the Encoding Form.
13.2.1 RocketPort Connection
Encoding while the device is connected via a RocketPort PCI card sometimes produces a communication
error.
If this occurs, changes must be made in the Device Manager.
1. In the Device Manager, expand Multi-port serial adapters.

2. Right-click RocketPort-PCI, PCI-BUS and select Properties.
3. On the Main Setup tab, select the COM port being used and click [Properties].
4. Select the checkboxes Map CD to DSR and Map 2 stop bits to 1.
5. Click [OK].
74 — revision 1
14 ActivIdentity ActivEntry
Integration of the ActivEntry solution with OnGuard allows organizations to upgrade existing OnGuard
access control systems to compliance with the functionality defined in FIPS 201, National Institute of
Standards and Technology (NIST) Special Publications (SP) 800-116, and the TWIC Reader Hardware and
Card Application Specification. It supports verification of the PIV, PIV-I, TWIC, and CAC End Point (EP)
cards without requiring the replacement or significant modification of the existing system.
The ActivEntry module, installed between an access panel and a supported reader, validates the badge,
extracts the badge ID, and passes it along to the panel for an access decision which is controlled in OnGuard.
The ActivEntry Manager provides centralized control of assurance level settings and distribution of
validation data.
14.1 Install the ActivEntry Module
The ActivEntry module is installed between the door controller/reader interface module and the access
reader. The following modules are supported:
• LNL-1300
• LNL-1320
• LNL-2220
• LNL-1300-U
• LNL-1320-U
• NGP-1320
• NGP-2220
• NGP-3320
Connect the hardware according to the following tables.
Wiring the ActivEntry Module and Access (LNL) Series Hardware

ActivEntry LNL-1300 LNL-1320 LNL-2220 LNL-1300-U LNL-1320-U
Wiegand 1 or (TB4) (TB8 or (TB8 or (J10 & J13) (J10 & J13 or J15 &
2 Pin/Label TB9) TB9) J18)
1 GND GND GND GND (J10) GND (J10 or J15) GND
2 D0 DAT/D0 DAT/D0 DAT/D0 (J10) DAT/D0 (J10 or J15) DAT/D0
3 D1 CLK/D1 CLK/D1 CLK/D1 (J10) CLK/D1 (J10 or J15) CLK/D1
4 BZR BZR BZR BZR (J13) BZR (J13 or J18) BZR
5 LED LED LED LED (J13) LED1 (J13 or J18) LED1
revision 1 — 75
ActivIdentity ActivEntry
Wiring the ActivEntry Module and Security (NGP) Series Hardware

ActivEntry Wiegand NGP-1320 NGP-2220 NGP-3320
1 or 2 Pin/Label (TB2 or TB11) (CN10 & CN11 or CN17 & (CN10 & CN11 or CN17 &
CN18) CN18)
1 GND 6 GND (CN11 or CN18) 4 GND (CN11 or CN18) 4 GND
2 D0 5 R1D0 (CN11 or CN18) 3 D0 (CN11 or CN18) 3 D0
3 D1 4 R1D1 (CN11 or CN18) 2 D1 (CN11 or CN18) 2 D1
4 BZR 3 RED (CN10 or CN17) 1 BZ (CN10 or CN17) 1 BZ
5 LED 2 GRN (CN10 or CN17) 3 GR (CN10 or CN17) 3 GR
The ActivEntry module should not be powered from the panel. Connect the ActivEntry module to an
external power supply. Once the ActivEntry module is wired, configure it using the documentation provided.
14.2 Access Readers
Currently, the Veridt MultiMode and Veridt GuardDog II readers are supported.
When wiring the readers to the ActivEntry module, Reader 1 corresponds to Wiegand 1 and Reader 2
corresponds to Wiegand 2. For detailed information, refer to the ActivEntry documentation.
14.2.1 Authentication Methods
The Veridt MultiMode reader supports the following authentication modes:

• Federal Agency Smart Credential Number (FASC-N)
• Cardholder Unique Identifier (CHUID)
• Card Authentication Key (CAK)
• Public Key Infrastructure and Personal Identification Number (PKI + PIN)
• CHUID + Fingerprint (TWIC)
• CAK + Fingerprint (TWIC)
• PKI + PIN + Fingerprint
The Veridt GuardDog II reader supports the following authentication modes:

• Federal Agency Smart Credential Number (FASC-N)
• Cardholder Unique Identifier (CHUID)
• Card Authentication Key (CAK)
Note: For detailed descriptions of the authentication modes, refer to the ActivEntry documentation.
76 — revision 1
14.3 Set up ActivEntry
OnGuard should already be installed and configured. For detailed information on installing and configuring
the ActivEntry solution, refer to the ActivEntry documentation.
14.4 Configure the Badge ID
Before enrollment into OnGuard, the badge ID import settings must be configured to match the Badge ID
Rules defined in the ActivEntry Management Station.
1. In FormsDesigner, open the Cardholder form.

2. On the Badge tab, right-click on the field for Badge ID. The Badge ID Properties are displayed.
3. For most card types, a card’s unique identifier (badge ID) is based on the Federal Agency Smart
Credential Number, or FASC-N. PIV-I cards use Universally Unique Identifiers (UUID). This
configuration should match the badge ID derivation rules in ActivEntry. Refer to the following Badge
ID Derivation Rules for the appropriate selection.
4. Click [OK] to save the change.
Badge ID Derivation Rules
The badge ID derivation rules configure in ActivEntry must match the OnGuard setting configured in
FormsDesigner.
Badge ID derivation rule OnGuard setting
FASC-N ID For the badge ID, set FASC-N to AC + SC + CN.
FASC-N ID + ICI For the badge ID, set FASC-N to AC + SC + CN + ICI.
FASC-N ID with Issue Code (This is only For the badge ID, set FASC-N to AC + SC + CN. For the issue
supported using a PC/SC reader.) code, set FASC-N to Individual Credential Issue # (ICI).
DoD CAC For the badge ID, set FASC-N to AC + SC + CN + CS + ICI.
DoD CAC with Issue Code (This is only For the badge ID, set FASC-N to AC + SC + CN + CS. For the
supported using a PC/SC reader.) issue code, set FASC-N to Individual Credential Issue #
(ICI).
DoD EDIPI Not supported
GSA (75-bit) Not supported
TWIC 48-bit Not supported
TWIC 75-bit Not supported
UUID (7-bytes) For the badge ID, set PIV-I to GUID (7-Byte).
UUID (8-bytes) Not supported
UUID (16-bytes) Not supported
For more information on badge ID derivation rules, refer to the ActivEntry documentation.
revision 1 — 77
If you want to configure both PIV and PIV-I cards at the same time, for the badge ID, set FASC-N to the
desired value and set PIV-I to GUID (7-Byte).
14.4.1 Increase the Badge Number Length
Before enrollment, the badge number length must be increased to at least 16 digits to accommodate the card
data.
1. From the Administration menu in System Administration or ID CredentialCenter, select System

Options.
2. On the Hardware Settings tab, click [Modify].
3. Change the Maximum badge number length to at least 16.
14.4.2 Allow Manual Entry of the Badge ID in Cardholder Options
The badge ID must be configured for manual entry. This configuration can be done in Cardholder Options.
1. From the Administration menu in System Administration or ID CredentialCenter, select Cardholder

Options.
2. On the Badge ID Allocation tab, click [Modify].
3. For Generate Badge ID, select Manual Entry.
14.4.3 Allow Manual Entry of the Badge ID in Badge Types
The badge ID must be configured for manual entry. This configuration can also be done in Badge Types.
1. From the Administration menu in System Administration or ID CredentialCenter, select Badge Types.
2. On the Badge ID Allocation tab, select a badge type.
3. On the ID Allocation sub-tab, configure the badge type for manual entry.
a. If the system setting is already configured for manual entry, you may select Use system settings
for badge ID allocation (the system setting is displayed in parentheses).
b. Otherwise, select Use different settings for badge ID allocation of this badge type.
c. For Generate badge ID, choose Manual Entry.
14.5 Invalid Credentials
OnGuard must be configured to handle invalid credentials properly. By default, a badge ID of

9999999999999999 is sent by ActivEntry when an invalid credential is presented to a reader.
14.5.1 Configure a Cardholder with an Invalid Badge
1. Add a cardholder in OnGuard. It may be helpful to enter “Invalid Card” for the name.
78 — revision 1
2. Enter the number for the badge ID to be used to represent an invalid card. This badge ID should match
the preconfigured invalid badge ID in the ActivEntry software.
3. Make sure that the badge has no assigned access levels.
When an invalid badge is presented to the reader, this configuration will ensure that access is denied.
14.6 Configure the Card Format
The card format must be configured in OnGuard to match the Wiegand format configured in the ActivEntry
Management Station (see Badge ID and Card Format Example).
1. From the Administration menu in System Administration or ID CredentialCenter, select Card

Formats.
2. On the Card Format tab, click [Add].
3. You will be asked to choose the card format type. Select Wiegand and click [OK].
4. Type in a name for the card format. Configure the card format as it is configured for the ActivEntry
Wiegand format.
14.7 Badge ID and Card Format Example
The following examples are based on using FASC-N with Issue Code for the badge ID derivation rule (the FASC-N
Identifier is used as the badge ID, and the ICI is used as the Issue Code).
Badge ID Configuration
In FormsDesigner, configure the badge ID and issue code to match the badge ID derivation rule configured
in ActivEntry. For the badge ID, set FASC-N to AC + SC + CN. For the issue code, set FASC-N to Individual
Credential Issue # (ICI).
Card Format Configuration
The following is an example of settings when configuring the Wiegand card format for a PIV or TWIC card
in the OnGuard software to match ActivEntry.
• Facility Code: 0
• Badge Offset Number: 0
• Total Number of Bits On Card: 52
• Facility Code Starting Bit: 0, Facility Code Number of Bits: 0
• Card Number Starting Bit: 0, Card Number Number of Bits: 48
• Issue Code Starting Bit: 48, Issue Code Number of Bits: 4
• Number of Event Parity Bits: 0
• Number of Odd Parity Bits: 0
revision 1 — 79
14.8 Enrollment
The badge must be enrolled in both the ActivEntry software and in OnGuard. The following sections
describe how to configure and enroll badges into OnGuard. For ActivEntry enrollment, refer to the
manufacturer documentation.
The following devices are supported for enrolling the badge in OnGuard:
• OmniKey 3121 PC/SC reader — supports PIV, PIV-I, TWIC, and CAC EP cards.
• RFIDeas AIR ID Enroll FIPS201 (RDR-7P71AKU) reader — supports PIV, TWIC, and CAC EP cards.
Connect the reader to an OnGuard client workstation and install the drivers according to the manufacturer
documentation.
Note: The reader can communicate with only one of the systems at a time. If you have finished
enrolling into one system, be sure to close the application before using the other to connect to
the reader. Failure to do so may cause communication errors.
14.8.1 Configure the Enrollment Device
The device must be attached to the workstation. If you are using the PC/SC reader, you must configure it as
an encoder in the OnGuard software (the RFIDeas reader emulates a keyboard and does not need to be
configured in OnGuard). To configure an encoder:
1. From the Administration menu in System Administration or ID CredentialCenter, select

Workstations.
2. On the Encoders/Scanners tab, click [Add]. For ActivEntry integration, you must select the following
settings:
a. On the General tab, be sure to enter a Name and select PC/SC Encoder in the Device type field.
b. On the Communications sub-tab, select the correct PC/SC device.
14.8.2 Enroll the Badge in OnGuard
To enroll the badge in OnGuard:
1. From the Administration menu in System Administration or ID CredentialCenter, select Cardholders.

2. On the Cardholders tab, click [Add]. To enroll the badge for an existing cardholder, search for the
cardholder and click [Modify].
3. To import the badge information, click [Import].
4. You will be prompted for your import source. Choose the appropriate import source. Click [OK].
• PIV Card - Use PIV Card for PIV, PIV-I, and TWIC cards.
• TWIC Card - If you are using the TWIC privacy key, select TWIC Card.
5. Place the badge in the reader.
80 — revision 1
6. Enter the correct PIN and click [Import]. The badge ID will be imported as specified in FormsDesigner.
If you have forgotten your PIN, you may still import the badge ID. Select the Forgot PIN check box.
The badge ID will be imported without the cardholder name and photo.
7. Once the import is complete, click [OK].
8. Select the badge type for the cardholder.
Note: The badge deactivate date and issue code are based on badge type configuration. Since data
was imported from a badge, you will be asked if you want to overwrite the imported
information with the default data configured for the badge type.
9. Assign the appropriate access levels. Click [OK].
When the enrollment has been completed, verify that the cardholder information has been imported
correctly.
14.8.3 Configure RFIDeas FIPS201 AIR ID Enroll Reader
To configure the RFIDeas FIPS201 AIR ID Enroll Reader:
1. Using the workstation connected to the RFIDeas AIR ID Enroll reader, browse the contents of the
Supplemental DVD Revision 12. Open the Credential Center Device Drivers\RFIDeas\ directory.
2. Copy the pcProxConfig 5.0.4f.exe file to the hard drive, and then launch the file.
3. Connect to the reader using the USB connection type.
4. Using the pxProxConfig documentation (also included on the Supplemental DVD), configure the ID of
the reader’s outputs by modifying the fields on the CHUID tab.
Note: Confirm that all fields are listed together without any return or separator characters.
5. Confirm that the updated settings are written to the reader.
revision 1 — 81
82 — revision 1
15 Fingerprint Enrollment and Verification
Fingerprinting can be made easier with a simple fingerprint scanning device.
15.1 Cross Match
OnGuard supports a number of Cross Match devices.
15.1.1 Cross Match ID 500
The Cross Match ID 500 is a fingerprint scanner. It has the capability to capture slap fingerprints, which are
are taken by simultaneously pressing the four fingers of one hand onto the scanner. They are also know as
multiple-finger simultaneous plain impressions. This device provides real-time feedback for such factors as
finger alignment, ridgelines, rotation, and pressure. It can capture all ten fingerprints in three basic slaps: the
four right hand fingers, four left hand fingers, and both thumbs.
Installation of the Cross Match ID 500
A FireWire (IEEE 1394) card and cable, and a power supply are included with the Cross Match ID 500
scanner, as well as the driver.
1. Copy the file vhpd1394.inf from the OnGuard Supplemental disc to C:\WINDOWS\inf.
2. Copy the file vhpd1394.sys from the OnGuard Supplemental disc to C:\WINDOWS\System32\drivers.
3. Create a temporary directory. Copy the files CMReset.inf, CMReset.sys, CMResetInstall.exe, and
CMResetTest.exe from the OnGuard Supplemental disc into that temporary directory.
4. Run the CMResetInstall.exe file from within the temporary directory.
5. Determine if your system has the .NET runtime environment version 1.1.
• To do this, go to Start > Control Panel > Add or Remove Programs for “Microsoft .NET
Framework 1.1.” If the .NET Framework is not installed, install the .NET Framework version 1.1,
which can be found on the Microsoft web site.
6. Run the Cross Match SDK 3.7.0 installation program located on the OnGuard Supplemental disc,
“LiveScan 3.7.0 setup.msi.”
a. Install to C:\Program Files\Cross Match Technologies.
b. Install the SDK for everybody who uses the computer.
7. Install the FireWire card in the computer.
8. Connect the Cross Match ID 500 to the workstation’s FireWire card using the FireWire cable.
9. Plug the power supply into the back of the Cross Match ID 500. Plug the power cable into a power strip
with surge suppression capabilities, and connect that to an electrical outlet.
10. Once the computer detects the scanner, have the computer add drivers for the new device automatically.
11. If System Administration was running, you may need to restart System Administration for the scanner
to work.
Upon using this scanner for the first time, the capture software will automatically calibrate it. In order for
this to occur, the platen cover needs to be installed. Once calibration is complete, you may use the scanner.
revision 3 — 83
Fingerprint Enrollment and Verification
OnGuard Enrollment
Once the driver is installed, the Cross Match ID 500 is ready for use.
1. When enrolling a cardholder, click [Capture].

2. Navigate to the OpenCapture tab.
3. Check that the device status indicates that it is connected. If this is not indicated, re-check your
connection.
4. If there are any fingers that are NOT being enrolled, select the checkbox for that finger.
5. Click [Capture]. Follow the instructions on the Cross Match ID 500 screen. It will guide you through
the process of taking fingerprints and correct finger positions.
6. Add an annotation for an individual fingerprint(s), if you wish (up to 128 characters of data per finger),
by double-clicking on the fingerprint image.
7. Click [Finish] when you are done.
15.1.2 Cross Match Verifier 300
The Cross Match Verifier 300 is a fingerprint scanner. This device provides real-time feedback for such
factors as finger alignment, ridgelines, rotation, and pressure. It is capable of scanning a single, flat
fingerprint.
Up to two fingerprints may be stored per person. Captured images are stored in bitmap format so that they
may be displayed more easily. They are also converted to ANSI-INCITS 378 minutiae format for storage in
the database.
Installation of the Verifier 300
Only one Verifier 300 unit may be connected at a time. Connect the scanner to the host workstation using a
USB cable. It must be connected to a USB 2.0 port. Additional configuration of communication settings is
not needed.
OnGuard Enrollment

2. Have the cardholder place a finger on the platen for fingerprint capture. A live image of the fingerprint
on the scanner is shown. Once all quality components are met, the image will automatically be captured.
Note: Minimum requirements: the fingerprint size must be at least 175 pixels wide by 250 pixels
high on the platen. There must be a minimum of 15 horizontal ridges present and a minimum
of 15 vertical ridges present.
3. The image is displayed and the fingerprint minutiae is generated.

4. Click [OK].
• If you would like to stop the fingerprint capture at any time, click [Cancel].
• If you would like to remove the fingerprint image and minutiae, click [Clear].
84 — revision 3
15.2 Sagem Morpho
The MSO fingerprint scanner has the capability to capture a high-resolution (500 dpi) image of a fingerprint
and allow viewing of a low-resolution bitmap image. It can also be used for verification.
The following models are supported by OnGuard: MSO 300, MSO 350, MSO 350 PIV, MSO 1300, and
MSO 1350.
15.2.1 Installation of the MSO Scanner
Install the device driver. This can be found on the Supplemental Disc. Connect the MSO scanner to the USB
port of the host computer. The device will be automatically detected. It is not necessary to configure
communication settings. Only one scanner may be connected to the computer.
Note: For more information, refer to the manufacturer documentation.
15.2.2 OnGuard Enrollment

2. Navigate to the OpenCapture tab.
3. Check that the device status indicates that it is connected. If this is not indicated, re-check your
connection.
4. If there are any fingers that are NOT being enrolled, select the checkbox for that finger.
5. Click [Capture]. Follow the instructions on the screen. It will guide you through the process of
capturing fingerprints.
6. Click [Finish] when you are done.
revision 3 — 85
Fingerprint Enrollment and Verification
86 — revision 3
16 GemPlus EasyAccess 332 Encoder
This unit is a contactless reader, uses an RS-232 connection, and is compatible with ISO14443 A and Mifare
cards.
16.1 Encoder Installation
Connect the GemPlus EasyAccess 332 encoder to the PC’s serial port.
To Com Port on PC
White to Pin 2
Green to Pin 3
Blue to Pin 5
To +12VDC
To Ground 12 VDC
revision 1 — 87
GemPlus EasyAccess 332 Encoder
16.2 Software Configuration
In order to use this encoder, it must be added to the Workstations folder in System Administration.
1. In the Encoders/Scanners tab, click [Add].

2. Type in a unique name for the device.
3. Select the workstation to which the EasyAccess 332 encoder is attached.
4. For the Device Type, select GemEasyLink680S/GemEasyAccess.
5. If not already done, select MIFARE card technology.
6. Select the location. The encoder can be either a standalone device or an inline device.
7. Configure the communications settings as follows:
a. Comm. port: user configurable
b. Baud rate: 9600
c. Data bits: 8 bit
d. Parity: none
e. Stop bits: 1
88 — revision 1
17 iClass Programmer
The HID iClass RW400Prgm encoder supports the following smart card applications:
• Credential Agent
• GSC (iClass)
• HID Access Control (iClass)
• IrisAccess (iClass)
• V-Smart (iClass)
To use the encoder, wire and connect the device to a workstation COM port. Then create the smart card
format application. Assign these smart card format applications to the badge types for encoding.
This programmer (RW400Prgm/6121AKN0000PRGM) operates at 10-16 VDC. The average current draw
is 80-260 mA. When communication to the unit is successful, the LED remains solid green.
17.1 Encoder Wiring
Due to timing issues with the encoder, this unit cannot be connected to a multiport serial adapter.
PIN 2
PIN 3
PIN 5
To DB9 Serial
Communication
Port on PC HID
Wiring Function DB9 pin-out (female)
Yellow Speaker Not used
Blue Hold Not used
Violet Open collector Not used
White Data 1 Not used
Green Data 0 Not used
Orange Green LED Not used
Brown Red LED Not used
revision 1 — 89
iClass Programmer
Wiring Function DB9 pin-out (female)
Red +DC (10-16 VDC) +DC (10-16 VDC)
Black Ground DC Ground
Gray RX (serial receive) Pin 3
Red/Green DSR Not used
Pink TX (serial transmit) Pin 2
Red/Yellow DTR Not used
Drain Shield ground Pin 5
17.2 Configuration of the iClass Programmer
To configure the iClass programmer in System Administration:
1. From the Administration menu, select Workstations.

2. Click the Encoders/Scanners tab.
3. Click [Add].
4. On the General sub-tab:
a. Type in a unique name for the programmer.
b. Enter the name of the workstation to which it is connected.
c. Select HID iCLASS for the device type and iClass for the credential technology.
5. On the Location sub-tab, select the radio button indicating This is a standalone device attached to
this workstation.
6. On the Communucations sub-tab, select the comm. port to which the unit is connected and enter the
following communication settings:
• Baud rate: 57600
• Data bits: 8 bit
• Parity: Even
• Stop bits: 2
7. Click [OK].
17.2.1 Card Formats
Create a card format for one of the smart card applications mentioned earlier in this chapter. The following
procedures are for configuring a Wiegand card format and a Smart Card format for the iClass programmer.
For more details, refer to the System Administration or ID CredentialCenter User Guides.
Wiegand Format
To configure the Wiegand card format:
1. From the Administration menu, select Card Formats.
90 — revision 1
2. Click [Add].
3. In the dialog box that appears, choose Wiegand and click [OK].
4. Type in a unique name for the Wiegand card format
5. Enter the required information.
6. Click [OK].
Wiegand card format configuration
Smart Card Format
To configure the Smart Card format in:
1. From the Administration menu, select Card Formats.

2. Click [Add].
3. In the dialog box that appears, choose Smart Card and click [OK].
4. Type in a unique name for the Smart Card format
5. Enter the required information.
6. Click [OK].
revision 1 — 91
iClass Programmer
Smart Card format configuration
17.2.2 Encoding Form
done in System Administration or ID CredentialCenter in the Badge Types Folder, on the Encoding Form.
92 — revision 1
18 Integrated Engineering
OnGuard supports the Integrated Engineering (IE) SmartID, SmartPro, and SmartLOGON™.
18.1 SmartID/SmartPro/SmartLOGON
The SmartID/SmartPro/SmartLOGON™ ISO 14443 encoder supports DESFire card applications. The
device communicates with the workstation via USB port and requires the FTD2XX driver.
18.1.1 Configuration
Configuration of the device is accomplished in System Administration, in the Workstations folder, on the
Encoders/Scanners form.
1. Under the General tab:

a. Type in a name for the device.
b. Select the workstation to which the encoder is connected. Note that the IE SmartID/SmartPro can
only be configured locally on the workstation to which it is connected.
c. For the Device type, select IE SmartID/Pro.
d. The Credential technology, DESFire, will automatically be chosen. Supported applications include
Credential Agent.
2. Under the Location tab, select the radio button to specify that This is a standalone device.
3. Under the Communications tab, all IE SmartID/Pro devices attached to the workstation are listed in the
drop-down field, with its serial number.
For configuration of card formats, refer to the System Administration User Guide.
revision 1 — 93
Integrated Engineering
94 — revision 1
19 Intelli-Check ID-Check
The information on a driver’s license, military ID, or passport can be imported using an ID-Check IDC1400
terminal. ID-Check can read, analyze, and verify the information encoded in the bar codes and magnetic
stripes on state and provincial driver licenses, identification cards, military and government IDs including
those that conform to the standards of the American Association of Motor Vehicle Administrators
(AAMVA), American National Standards Institute (ANSI) and International Organization for
Standardization.
Note: The IDC1400 must be running firmware version 5.4 or later.
Connect the IDC1400 to the workstation using a serial cable.
19.1 IDC1400 Configuration
Once the unit is connected and powered, the terminal will immediately display “ID-CHECK SETUP
REQUIRED.” To access the setup menu, press SETUP [F6]. Key in your four-digit master password and
press [Enter].
Once you access the Setup menu, selections can be made by pressing [Enter]. Use the up and down buttons
to scroll through options. Use any of the arrow keys to toggle settings.
19.1.1 Configure the Host Port
Configure the IDC1400 to send transaction results through the printer port.
1. In the SETUP [F6] menu use the UP and DOWN arrows to scroll through the options. Select
FEATURES by pressing [Enter], then scroll through and select PRINTER. Press [Enter]. Set the
following attributes as follows:
a. MODE: Enabled (to enable the printer)
b. BUSY CHECK: Disabled
c. PRE LINES = 00 (number of line feeds to send before each transaction result)
d. POST LINES = 03 (# of line feeds to send after each transaction result)
e. PRINT TEXT = LEFT MARGIN (parser friendly format for applications)
2. In the SETUP [F6] menu, under FEATURES > PRINTER > HOST PORT, set BAUD RATE,
PARITY, WORD LENGTH, and FLOW CONTROL to the appropriate values to match your OnGuard
communication settings.
3. In the SETUP[F6] menu, under SYSTEM, set PROCESS MODE to COMPLETE ID.
4. In the SETUP[F6] menu, under SYSTEM > TRANSACTIONS > SHOW FLAGS, set PRINTER to
FULL CONTROL. Then for all other sub-menu settings, such as DL/ID, DOB, NAME, ADDRESS,
revision 1 — 95
Intelli-Check ID-Check
CITY, POSTAL CODE, AGE, EXP, DRIVER CLASS, SOCIAL SEC#, ISSUE DATE, WEIGHT,
HEIGHT, JURISDICTIO, EYE COLOR, HAIR COLOR,GENDER, set to ENABLED.
5. In the SETUP[F6] menu, under FEATURES, set NAME FORMAT to F M L. Set HEIGHT FORMAT
to FEET/INCHES and WEIGHT FORMAT to POUNDS for US ID/DL.
Note: For access to the menu, enter the password (by default, 1234).
19.1.2 Configure the Display
If the results do not need to be displayed on the terminal, disable this option to speed up the transaction time.
When a license is swiped or scanned, the IDC1400 will beep (if enabled) and transfer the data (if the printer
is enabled) and return back to the idle screen.
1. In the SETUP [F6] menu use the UP and DOWN arrows to scroll through the options. Select
FEATURES by pressing [Enter].
2. Scroll through and select DISPLAY TIME.
3. Set the DISPLAY TIME = 00.
Before continuing, verify that you have a license for OnGuard with ID-Check Terminals enabled. The ability
to use ID-Check Terminals is a licensed feature. The ID-Check Terminals license is count-based; you are
licensed to have a certain number of ID-Check Terminals. The number of terminals you are licensed to use is
displayed in the “Maximum Number of ID-Check Terminals” setting in the ID CredentialCenter section of
the license.
The ID-Check scanner must also be added in the OnGuard software. This is done in System Administration
or ID CredentialCenter on the Encoders/Scanners form in the Workstations folder. The encoder/scanner that
is added must have a Device Type of “ID-Check Terminal.”
Use FormsDesigner to map the proper DMV values to the data fields for enrollment.
The settings for the software must match the communication parameters configured on the IDC1400 unit.
Configure the communication parameters in System Administration as follows:
• BAUD RATE: 38400
• DATA BITS: 8 bit
• PARITY: None
• STOP BITS: 1
• FLOW CONTROL: None
19.2.1 Import Data Using the ID-Check Scanner
You can import data using the ID-Check Scanner whenever you are asked to manually enter cardholder or
96 — revision 1

window opens.
b. Click [OK].
4. Click [Import].
5. The Select Import Source window opens. Select “ID-Check Terminal”, then click [OK].
6. An ID-Check message is displayed. Follow the instructions on the message.
• If a magnetic stripe is present, swipe the driver’s license through ID Check’s Magnetic Stripe Slot
Reader.
• If a barcode (2D or 1D) is present, scan the driver’s license using the barcode scanner.
7. After the ID has been scanned, the message automatically closes. The fields on the Cardholder or
Visitor form will be populated with whatever information can be determined.
8. Make sure that the information is correct, then click [OK]. The record will then be added.
revision 1 — 97
Intelli-Check ID-Check
98 — revision 1
20 OMNIKEY 5125 Wedge
The OMNIKEY 5125 PC/SC smart card proximity reader is used for automatic visitor sign in/sign out. It
automatically adds Wiegand data to badging workstations.
The OMNIKEY 5125 supports HID proximity 125 kHz techology.
Supported card formats include the following (Wiegand only):

• HID Corporate 1000 35-bit (CIC+CN)
• HID H10301 26-bit (FAC+CN)
• HID H10302 37-bit (CN)
• HID H10320 32-bit clock/data card
Data on card Description
FAC Facility Code
CN Card Number (Badge ID)
CIC Customer Identifier Code
20.1 Installation
The OMNIKEY 5125 reader uses a USB keyboard interface. Connect the reader to the workstation using the
supplied USB cable. When the reader is connected, you will be prompted to install the required device
driver.
Obtain the device driver from the HID Web site, http://www.hidglobal.com/
driverDownloads.php?techCat=19.
For more information, refer to the Third Party Encoders Compatibility Chart, which can be accessed at:
http://www.lenel.com/support/downloads/onguard#compatibility-charts. (You will need your Lenel login to
gain access to this site.)
20.2 Configuration of the 5125 Reader
The OMNIKEY 5125 unit sends transaction results through the USB port. The device driver is used to
configure the connection of this device. There is no setup reuired.
The 5125 reader uses an optical sensor for automatic card detection (it automatically detects when material
is being present for scanning). Although it looks like an LED, it is NOT an indicator of any status for the
device.
revision 1 — 99
OMNIKEY 5125 Wedge
100 — revision 1
21 ScanShell 800/1000
The information on a business card, driver’s license, or military ID can be imported using the ScanShell 800.
Passports can also be read by the ScanShell 1000. ScanShell can read the information using OCR to extract
data.
The CSS1000 scanner is no longer available and has been replaced by the CSS1000-A scanner which
requires version 9.42.0 of the ScanShell SDK to be installed.
The CSS800 scanner is no longer available and has been replaced by the CSS800-R scanner. The CSS800-R
scanner supports USB 2.0 which allows faster response.
21.1 ScanShell Configuration
Install the device driver located on the OnGuard Supplemental disc. Connect the ScanShell to the
workstation using the supplied USB cable.
The ScanShell unit sends transaction results through the USB port. The device driver is used to configure the
connection of this device. There is no setup required.
Important: Do NOT use the manufacturer disc to install the driver.
The scanner should be properly calibrated. Refer to the manufacturer documentation. In order to calibrate
the scanner, the domain user should be made a member of the Administrators group.
The ScanShell 800-R uses an optical sensor for automatic card detection (it automatically detects when
material is being present for scanning). Although it looks like an LED, it is NOT an indicator of any status
for the device.
By default, FormsDesigner should have the proper DMV values mapped to the data fields for enrollment.
For more information, refer to the FormsDesigner User Guide.
Before continuing, verify that you have a license for OnGuard with ScanShell scanners enabled. The ability
to use ScanShell scanners is a licensed feature. The license is count-based; you are licensed to have a certain
number of scanners. The number of scanners you are licensed to use is displayed in the “Maximum number
of Card Scanning Solutions ID Scanners” setting in the ID CredentialCenter section of the license.
1. Using System Administration, in the Workstations folder, go to the Encoders/Scanners tab.

2. Click [Add].
a. Enter the name of the unit (this is user-configurable).
b. Select the workstation on which the ScanShell is installed.
c. For the device type, choose CSS Scanner.
revision 1 — 101
ScanShell 800/1000
d. The location and communication tabs are automatically configured.

3. Click [OK].
21.2.1 Import Data Using the ScanShell 800/1000
You can import data using the ScanShell scanner whenever you are asked to manually enter cardholder or

window opens.
b. Click [OK].
4. Click [Import].
5. The Select Import Source window opens. Select “CSS Scanner,” then click [OK].
6. Follow the instructions on the message displayed.
7. After the ID has been scanned, the message automatically closes. The fields on the Cardholder or
Visitor form will be populated with whatever information can be determined.
8. Make sure that the information is correct. Both the Badge Type and Badge ID fields should be
populated. If not, enter this information manually. If you fail to do so, the DMV/Passport information
will not be imported.
9. Click [OK]. The record will then be added.
102 — revision 1
22 Topaz SignatureGem Pen Tablet
The Topaz SignatureGem™ hardware is used to electronically capture cardholder signatures and connects
directly to a multimedia capture workstation via a USB or serial port.
These installation instructions and driver information are for the Topaz 1 x 5 SignatureGem USB (Z-TS261-
USB/Z-TS261-HSB) and serial kit (Z-TS261-B).
22.1 SignatureGem Installation
The Topaz SignatureGem pen tablet can be installed on any multimedia capture workstation running
Windows 2003 or XP. It is also compatible with Citrix.
Note: Do NOT connect the signature tablet to the serial or USB port until prompted to do so.
22.1.1 Load the Wintab Driver
The Wintab driver information for the pen tablet is located in the Topaz SignatureGem Pen Template
Driver folder on the OnGuard Supplemental disc. You can also download the driver information from the
Topaz website, located at http://www.topazsystems.com/Software/index.htm#6.
1. Run the Wintab15.exe file located in the Topaz SignatureGem Pen Template Driver folder on the
OnGuard Supplemental disc.
2. The welcome screen for the Topaz 1x5 Tablet Win Tab Driver v2.12 Setup program window displays.
Click [Next].
revision 1 — 103
Topaz SignatureGem Pen Tablet
3. The Topaz Wintab Installation window displays. Select the port for the signature tablet: serial, USB, or
HSB. If necessary, check the back of the device for the model number to determine whether it is USB or
HSB.
4. Verify the Signature tablet is UPLUGGED. Click [OK].

5. The next screen explains what you should do after the driver installation is complete. Click [OK].
Note: If you are asked to specify the driver location you can download the latest driver from http://
www.topazsystems.com/Software/index.htm#6.
6. When the driver has been successfully installed, click [Finish].

7. You will be prompted to restart the PC. Click [OK] to automatically restart the computer.
22.1.2 Connect the Signature Pad
1. After the driver is installed, the PC will reboot. Connect the SignatureGem pen tablet to the correct port.
2. The Found New Hardware wizard should automatically start. If it does not, manually start the wizard by
selecting Start > Settings > Control Panel > Add Hardware.
3. Complete all the steps in the Found New Hardware wizard.
4. The SignatureGem pen tablet can now be used with the Multimedia Capture module.
22.1.3 Install the Topaz software
1. When the PC reboots, the Found New Hardware Wizard automatically displays. Select the Install the
software automatically (Recommended) radio button and click [Next].
104 — revision 1
Note: If Found New Hardware wizard does not automatically start you can manually start it by
selecting Start > Settings > Control Panel > Add Hardware.
2. You may receive a message stating the hardware has not passed Windows Logo testing. Click [Continue
Anyway] if you are installing the hardware on a machine that uses the Windows 2003 or XP operating
system.
3. Click [Finish] when the wizard has finished installing the software.
revision 1 — 105
Topaz SignatureGem Pen Tablet
106 — revision 1
IP SUPPORT
23 LNL-ETHLAN (MSS1/MSS100 Ethernet Controller)
This procedure can also be used for the MSS-VIA network adapter.
This Ethernet controller is a network device, and not a part of the UL certification. This device must have
transient protection.
(A NULL MODEM CABLE IS REQUIRED)
23.1 Establish Serial Communication with the ETHLAN
The controller-to-MSS100 or MSS1-T cable is now available, part number HOC-ETHLAN.
UL requirement: this device must be on the recommended UPS (#HO2070) or equivalent
1. With the power OFF to the ETHLAN devices, establish a serial connection from the ETHLAN to the
PC’s Serial Communication Port, for example, using the HyperTerminal. (A Null Modem cable is
required).
2. Start HyperTerminal.
3. Change the Communication settings to 9600 Baud, 8 data bits, 1 stop bit, and Parity None.
4. Plug in power to the ETHLAN. The following messages should appear in the terminal window.
Lantronix Telnet session
5. At this point, press the <Enter> key. (It may take a few seconds to complete booting).
• Power should be cycled to the device while connected to it in order to see the “Load Completed...”
message.
• If it appears that nothing changes after pressing the <Enter> key, it is possible that the Lantronix
MSS1 or MSS100 device was already configured once. If this occurs, you need to press the
revision 3 — 109
LNL-ETHLAN (MSS1/MSS100 Ethernet Controller)
<Enter> key before the phrase, “Load Completed-Boot in Progress” appears. If this still does not
allow you to enter into the command mode, you may also telnet into the Lantronix device.
• If the device was configured previously, it may be best to do a hard reset and configure it from
scratch. To do this:
a. Using the end of a paper clip, or a similar small object, hold down the reset button.
b. Cycle power to the device.
• A prompt that says Local_1> should appear. If the prompt says Boot>, then the Ethernet
Address has not been defined and you must enter one.
a. At the Boot> prompt, type:
change hardware n
where n represents the last three digits of the Ethernet Address located on the bottom of the
Lantronix box (Example: change hardware 21-01-65).
b. Reboot for the change to take effect.
c. Wait for it to finish loading. Once it’s done, you should see a screen resembling the picture on
the previous page.
6. You will be prompted for a user name. Enter any name.
23.2 Establishing Network Communications
After a factory default reset, the following changes must be made:
1. At the prompt, type:

set privileged and press <Enter>.
2. Type in the password:
system and press <Enter>.
3. Determine and set the IP address. Type:
change ipaddress [IP ADDRESS] and press <Enter>.
4. Set the Gateway. Type:
change gateway [GATEWAY] and press <Enter>.
5. Set the boot flags. Type:
change bootp disabled and press <Enter>
change dhcp disabled and press <Enter>
change rarp disabled and press <Enter>
6. Set the access type to remote. Type:
change access remote and press <Enter>
7. At the prompt, type:
logout and press <Enter>.
8. Exit from HyperTerminal and cycle power to the device.
110 — revision 3
23.3 Configuring the ETHLAN
Any additional changes specific to the hardware that the Lantronix box is connecting to should be made
now. These may include, but are not limited to, baud rate, parity, stop bit, byte size, and flow control.
1. Make sure the device is powered, completely booted, and connected to the network. Start
HyperTerminal.
2. You will be prompted for a session name. Enter a name of your choice.
3. Connect to the device using the IP address, port address of 7000.
4. A HyperTerminal session starts. Type:

access
and press <Enter>. The access command will not echo.
5. You will be prompted for a user name. Enter any name. There should be a command prompt.
6. Type:
set privileged
and press <Enter>.
7. The password prompt will appear. The password is system.
8. For baud rate, type:
change speed [SPEED]
and press <Enter> where [SPEED] = the baud rate (9600, 2400, etc.)
9. For parity, type:
change parity [PARITY]
and press <Enter>, where [PARITY] = none, even, odd, mark, or space.
10. For stop bits, type:
change stopbits [BITS]
and press <Enter>, where [BITS] = 0, 1, or 2.
revision 3 — 111
LNL-ETHLAN (MSS1/MSS100 Ethernet Controller)
11. For byte size, type:

change charsize [SIZE]
and press <Enter>, where [SIZE] = 7 or 8.
12. For flow control, type:
change flow control [FLOW CONTROL]
and press <Enter>, where [FLOW CONTROL] = xonoff, ctsrts, slowcts, or none.
13. Type
change dedicated tcp port=3001
and press <Enter>.
14. (Optional) If you are going to connect to the device from across subnets or routers, you will need to
program the subnet mask and gateway. The commands are:
• change subnet mask [your subnet mask]
• change gateway [your gateway]
15. Type in the following to disable BOOT and RARP, depressing the <Enter> key after each line.
LOCAL>>CHANGE BOOTP DISABLE
LOCAL>>CHANGE RARP DISABLE
16. Type change access remote and press <Enter>.
17. Disconnect from the device and exit.
18. If a subnet mask and gateway was programmed (step 9), you must recycle power to the device (the
device must be rebooted) in order for the settings to take effect.
19. At this point, make sure that switch 5 on the ISC is configured correctly for hardware flow control. It
should be set to “ON.”
20. To verify that the device is talking on the network you can “ping” the device from a command prompt
by typing ping <IP address>.
At this point, the Lantronix box should be ready to act as a gateway between a LAN and a serial device. It is
also necessary to wire and configure each individual device.
23.4 Device Configuration
For wiring between the hardware and the Lantronix box, a straight through RS-232 cable is used. Also, a 25-
pin/9-pin adapter may be required for certain hardware. The Lantronix box is equipped with a 25 pin male
connector.
Device access parity stop byte flow baud rate

bits size control
AES IntelliNet (Bosch 6500 remote odd 2 7 CTS/RTS 1200

output mode)1
Bosch D6600/D6500 remote none 1 8 none 38400/19200/9600/

4800/2400/1200
Bosch D7412/D94122 remote none 1 8 none 9600
Bosch DS7400Xi remote odd 1 8 CTS/RTS 2400/9600
ESPA (Tateco) remote event 2 7 none 4800
112 — revision 3
Device access parity stop byte flow baud rate

bits size control
Galaxy 8, 18, 60, 128, 500, remote none 1 8 none 1200/2400/4800/9600/

504, or 512 19200/38400
Notifier panel remote even 1 7 none 2400/9600
Osborne-Hoffman OH-2000 remote none 1 8 CTS/RTS 9600
Pyrotronics3 remote even 1 7 none 115200/57600/38400/

19200/9600/4800/
2400/1200
Visonic remote none 1 8 CTS/RTS 9600
Note: Be sure to match the baud rate setting with the baud rate for which the hardware is configured.
1. A start character of 0 should be used, with an end character of 0x0014.

2. SDI Automation must be enabled on this panel. This is done via the RAM IV software in RADAUX1 >
SDI Automation > Enable SDI Automation = Yes. When using a D9133 with this device, the D9133
should be connected to the host with a null modem cable.
3. For Pyrotronics, an additional RS-232/RS-485 adapter is needed.
revision 3 — 113
Security Settings (SDS1100)
24 Security Settings (SDS1100)
In the Change Setup menu, there is a menu option that can be used to configure an encrypted connection
when using the SDS1100. Note that there are other options under this menu. Refer to the appropriate
Lantronix User Guide for more information regarding these options.
You can change security settings by means of telnet or serial connection only. The Web Manager cannot be
used for this. We recommend that you set security over the dedicated network or over the serial setup. If you
set parameters over the network (telnet 9999), someone else could capture these settings.
Enable Encryption. Rijndael is the block cipher algorithm chosen by the National Institute of Science and
Technology (NIST) as the Advanced Encryption Standard (AES) to be used by the US government. The
SDS supports 128-, 192-, and 256-bit encryption key lengths. Currently only 128-bit encryption is supported
for communications with our third party hardware devices.
Follow these instructions to configure AES encryption on the SDS1100.
Note: This configuration should be done through a local connection to the serial port of the device, or
via a secured network connection. Initial configuration information including the encryption
key are sent in clear text over the network.
1. In the Change Setup menu, select 6 for Security.

2. Press <Enter> until you arrive at the Enable Encryption menu item.
3. To enable encryption for the SDS press Y for yes. To disable it, press N for no.
4. If encryption is enabled the Key length in bits (128) prompt will be displayed. You must enter 128 for
the key length.
5. After entering the key length, the Change Key (N) prompt will be displayed. Press Y if you want to
enter a new key or N if you want to keep the existing key. Note that N is the default value.
6. If you selected Y to change the key, you will be prompted to enter the key. At the Enter Keys prompts,
enter your encryption key. The encryption keys are entered in hexadecimal. The hexadecimal values are
echoed as asterisks to prevent onlookers from seeing the key. Since only 128-bit keys are currently
supported the encryption key will consist of 32 hexadecimal characters.
7. Once the key has been entered, the next menu option will be displayed. Leave the current value for this
menu option.
8. When finished configuring encryption settings be sure to select option 9 Save and Exit to save the
settings.
24.1 Supported Controller Types Over Encrypted Connection
The following controller types support communication over an encrypted connection via the SDS1100.
Configuration Information
Controller Type Baud Rate I/F Mode Flow Control
(Fire) ESPA 4800 F8 00
114 — revision 3
Configuration Information
Controller Type Baud Rate I/F Mode Flow Control
(Fire) Notifier AM2020 2400/9600 78 00
(Fire) Notifier NFS-640 9600 78 00
(Fire) Pyrotronics 1200, 2400, 4800, 9600, 78 00

19200, 38400, 57600, 115200
(Personal safety) Visonic SpiderAlert 9600 4C 02
(Receiver) Bosch 6500 1200, 2400, 4800, 9600, 4C 00

19200, 38400
(Receiver) Bosch SIA 1200, 2400, 4800, 9600, 4C 00

19200, 38400
(Intrusion) Bosch D7412G / D9412G 9600 4C 00
(Intrusion) Bosch DS7400Xi / 2400, 9600 5C 02

DS7400XIV4
(Intrusion) Galaxy 8, 18, 60, 128, 500, 1200, 2400, 4800, 9600, 4C 00
504 and 512 19200, 38400
Note: Note: This will not be supported

if the Galaxy panel is
configured to use the separate
standalone Galaxy Ethernet
module.
(Point of sale) TVC-2100 series 9600 4C 02
revision 3 — 115
IP Cameras
25 IP Cameras
IP cameras supported by Lenel Digital Video can be found on our website:

https://customer.lenel.com/?q=var/video-tools
Be sure to check here for the latest updates.
116 — revision 3
Index
A sagem morpho.............................................. 85
ActivEntry Fire panels........................................................... 11
access readers............................................... 76
authentication methods ................................ 76 G
badge id........................................................ 77 Galaxy panel ..................................................... 113
badge id derivation rules.............................. 77 GemPlus.............................................................. 87
card format................................................... 79
enrollment .................................................... 80 H
invalid credentials........................................ 78 HID EdgeReader................................................. 21
module ......................................................... 75
ActivIdentity ....................................................... 75 I
AES intellinet receiver...................................... 112
iCAM .................................................................. 23
B ID-check.............................................................. 95
Install
Biotouch.............................................................. 83 Topaz software .......................................... 104
Bosch D6600/D6500......................................... 112 Integrated Engineering........................................ 93
Bosch D7412/D9412......................................... 112 Intelli-check ........................................................ 95
Bosch receiver..................................................... 41 Intrusion detection panel DS7400Xi................. 112
Invalid credentials............................................... 78
C Iris recognition.................................................... 23
CardScan ............................................................. 59 IrisAccess............................................................ 23
Corex................................................................... 59
Cross match......................................................... 83 M
Cypress......................................................... 63, 69 MOM-4 ............................................................... 11
Cypress timer ...................................................... 47
N
D
Notifier
D6500.................................................................. 41 AM2020....................................................... 14
D6600.................................................................. 41 NFS-640....................................................... 15
Destination dispatch.............................................. 9 panel connection .......................................... 14
DigiOn24 ............................................................ 73 programming ............................................... 17
DS7400Xi ......................................................... 112 Notifier panel .................................................... 113
E O
EasyAccess ......................................................... 87 OEM devices......................................................... 7
EdgePlus ............................................................. 21 OEM devices supported over IP ....................... 107
EdgeReader ......................................................... 21 OMNIKEY 5125 Wedge .................................... 99
Elevator dispatch................................................... 9 Onity programmer............................................... 37
Enrollment .......................................................... 80 Osborne-Hoffman oh-2000 receiver ................. 113
ESPA (Tateco) .................................................. 112
ESPA protocol .................................................... 18 P
ETHLAN (MSS1/MSS100 ethernet controller) 109
Parsing information............................................. 19
F Personal safety .................................................... 39
Point of sales....................................................... 55
Fingerprint Pyrotronics ................................................. 11, 113
biotouch ....................................................... 83 Pyrotronics Fire Panel......................................... 11
cross match .................................................. 83
enrollment .................................................... 83
revision 3 — 117
Index
R
Receivers............................................................. 41
S
Sagem morpho .................................................... 85
ScanShell .......................................................... 101
Security settings ................................................ 114
SignatureGem pen tablet
installation checklist .................................. 103
SmartID readers .................................................. 93
T
Tateco
connection.................................................... 18
data converter power.................................... 18
fire panel ...................................................... 18
test mode...................................................... 19
Topaz signaturegem .......................................... 103
TVC-2100 ........................................................... 55
TVS ..................................................................... 55
V
Video text inserter............................................... 55
Visonic .............................................................. 113
Visonic SpiderAlert ............................................ 39
W
Wedge reader ............................................... 63, 69
118 — revision 3
Lenel Systems International, Inc.
1212 Pittsford-Victor Road
Pittsford, New York 14534 USA
Tel 585.248.9720 Fax 585.248.9185
www.lenel.com
docfeedback@lenel.com

A100K10602 Alphacom XE User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

A100K10602 Alphacom XE User Guide

Uploaded by

Copyright:

Available Formats

2013

OEM Device Configuration Guide

OEM Devices ....................................................................... 7

2. Fire Panels ........................................................................................... 11

3. HID EdgeReader and EdgePlus .......................................................... 21

4. Iris Recognition .................................................................................... 23

5. Onity Programmer ............................................................................... 37

6. Personal Safety ................................................................................... 39

8. Cypress Timer ..................................................................................... 47

9. TVS TVC-2100 Series Video Text Inserter .......................................... 55

9.2 TVC-2104 Hardware ........................................................................................... 55

10. Corex CardScan ................................................................................ 59

11. RFIDeas Readers .............................................................................. 63

12. Cypress Wedge ................................................................................. 69

13. DigiOn24 Encoder ............................................................................. 73

14. ActivIdentity ActivEntry ...................................................................... 75

15. Fingerprint Enrollment and Verification .............................................. 83

16. GemPlus EasyAccess 332 Encoder .................................................. 87

17. iClass Programmer ............................................................................ 89

18. Integrated Engineering ...................................................................... 93

19. Intelli-Check ID-Check ....................................................................... 95

20. OMNIKEY 5125 Wedge ..................................................................... 99

20.1 Installation ........................................................................................................ 99

21. ScanShell 800/1000 ......................................................................... 101

22. Topaz SignatureGem Pen Tablet .................................................... 103

IP Support ........................................................................ 107

24. Security Settings (SDS1100) ........................................................... 114

25. IP Cameras ...................................................................................... 116

Index ................................................................................................................ 117

This will be done through the following:

1.1 Hardware Setup

1.2 OnGuard Configuration

• Subnet Mask 255.255.255.0

• Default Gateway 192.168.50.254

2.1 Pyrotronics Fire Panel

Use the following settings to configure this.

Black Box Settings:

W5 should be on B-C to set RTS/CTS/CD.

W8 should be on A-B to set 4-wire.

W9 should be on D to set ON.

W15 should be on A-B to set RTS/CD Enabled.

W16 should be on A to set 0 ms Turn Around Delay.

W17 should be on E to set 0.15 ms Driver Enable Hold.

W19 - NO JUMPER. This is for testing purposes only.

XW1A - Jumper-block must be installed here to set DCE Emulation Mode.

S1 - Out to set Normal

S2 - ON to set Terminated or OFF to set Not Terminated

S3 - OFF to set Not Biased.

Notes: 18 AWG minimum

Connect the wires accordingly.

110 VAC 25-Pin Serial Connector

(max. 4000 feet)

DB 9 Pin Male DB 25 Pin Female

2.1.1 Pyrotronics Debug Settings

2.2 Notifier Fire Panels

For more information, refer to the Notifier documentation.

2.2.1 Notifier AM2020 Fire Panel

Connecting the AM2020 Panel

SIB pin DB-25 pin DB-9 pin

Pin 2 Pin 3 (RXD) Pin 2 (RXD)

Pin 4 Pin 2 (TXD) Pin 3 (TXD)

Programming the AM2020 Panel

1. To begin programming, press [Prog.].

2.2.2 Notifier NFS-640 Fire Panel