OEM Device Configuration Guide

7.2
OEM Device Configuration Guide
Lenel® OnGuard® 7.2 OEM Device Configuration Guide
This guide is item number DOC-603, revision 6.007, October 2015.
© 2015 United Technologies Corporation, Inc. All rights reserved.
Lenel® and OnGuard® (Registered trademarks of UTC Fire & Security Americas Corporation, Inc.) Lenel is a
part of UTC Building & Industrial Systems, a unit of United Technologies Corporation.
All trademarks are the property of their respective owners.
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 UTC Fire & Security Americas Corporation, 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.
Crystal Reports for Windows is a trademark of Crystal Computer Services, Inc.
OnGuard includes ImageStream® Graphic Filters. © 2002 eBT International, Inc. (f/k/a Inso Corporation).
All rights reserved. ImageStream Graphic Filters and ImageStream are registered trademarks of eBT
International, Inc. (f/k/a Inso Corporation).
Integral and FlashPoint are trademarks of Integral Technologies, Inc.
Portions of this product were created using LEADTOOLS ©1991-2011, LEAD Technologies, Inc. ALL
RIGHTS RESERVED. Portions of this product are licensed under US patent 5,327,254 and foreign
counterparts.
Active Directory, Microsoft, SQL Server, Windows, and Windows Server are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
Other product names mentioned may be trademarks or registered trademarks of their respective companies
and are hereby acknowledged.
Warranty
UTC Fire & Security Americas Corporation, Inc. ("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 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 lifecritical control applications. Lenel 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.
OEM Device Configuration Guide
Table of Contents
OEM Devices ....................................................................... 9
1. Destination Dispatch ............................................................................ 11
1.1 Hardware Setup .................................................................................................. 11
1.2 OnGuard Configuration ...................................................................................... 12
2. Fire Panels ........................................................................................... 13
2.1 Pyrotronics Fire Panel ........................................................................................ 13
2.2 Notifier Fire Panels ............................................................................................. 16
2.3 Tateco Fire Panel ............................................................................................... 20
3. HID EdgeReader and EdgePlus .......................................................... 23
3.1 Wiring the EdgeReader ...................................................................................... 23
3.2 Configuring the EdgeReader .............................................................................. 23
4. Iris Recognition .................................................................................... 25
4.1 Installing an iCAM4000 with ICU4000 Controller ................................................ 25
4.2 Installing an iCAM4000V .................................................................................... 31
4.3 Installing an iCAM7000 ....................................................................................... 34
4.4 Enrollment .......................................................................................................... 37
4.5 Verification .......................................................................................................... 38
4.6 Software Upgrades ............................................................................................. 38
5. Onity Programmer ............................................................................... 41
5.1 Configuration for Onity ........................................................................................ 41
6. Personal Safety ................................................................................... 43
6.1 Visonic SpiderAlert ............................................................................................. 43
6.2 OnGuard Configuration ...................................................................................... 44
7. Receivers ............................................................................................. 45
7.1 Bosch D6100, D6500, D6600 Receiver .............................................................. 45
7.2 Osborne-Hoffman OH-2000 ............................................................................... 53
7.3 AES-IntelliNet 7000 ............................................................................................ 53
7.4 Verex HSC-IP Receiver ...................................................................................... 54
8. Cypress Timer ..................................................................................... 55
8.1 System Level Wiring ........................................................................................... 56
8.2 DIP Switches ...................................................................................................... 57
8.3 Time Displays: Functional Description ................................................................ 58
8.4 Wall Mounting ..................................................................................................... 61
9. TVS TVC-2100 Series Video Text Inserter .......................................... 63
9.1 Firmware ............................................................................................................. 63
revision 6 — 5
Table of Contents
9.2 TVC-2104 Hardware ........................................................................................... 63
9.3 TVC-2104 Operation .......................................................................................... 65
10. Corex CardScan ................................................................................ 67
10.1 Corex CardScan Installation and Configuration ................................................ 67
11. RFIDeas Readers .............................................................................. 71
11.1 HID iCLASS AIR ID (Model: RDR-7081BKU) and AIR ID Playback (Model:
RDR-7585AKU) Readers ...................................................................................... 71
11.2 HID Prox Reader (Model: RDR-6081AKU) ....................................................... 72
11.3 AWID Prox (Model: RDR-6981AKU) ................................................................ 74
11.4 MAG Swipe (Model: MS3-00M1AKU) ............................................................... 74
12. Assa Abloy Aperio Locks ................................................................... 77
12.1 Hardware Installation ........................................................................................ 77
12.2 OnGuard Configuration .................................................................................... 79
13. Schlage Reader and Lock Solutions .................................................. 83
13.1 Locks and Readers ........................................................................................... 83
13.2 Hardware Installation ........................................................................................ 84
13.3 Access Control Features .................................................................................. 86
13.4 OnGuard Configuration .................................................................................... 88
13.5 Wiegand Only Integration ................................................................................. 97
13.6 Place the PIM400/401-TD2 into Link Mode .................................................... 104
13.7 Connect the HHD to the Lock ......................................................................... 105
13.8 Use the HHD to Couple with the Lock ............................................................ 105
14. Cypress Wedge ............................................................................... 107
14.1 Cypress Wedge WDG-4413 ........................................................................... 107
14.2 Cypress Wedge WDG-5912 ........................................................................... 108
15. DigiOn24 Encoder ........................................................................... 111
15.1 Installation ...................................................................................................... 111
15.2 Configuration of the Encoder .......................................................................... 111
16. HID CP1000 Encoder ...................................................................... 113
16.1 Use Asure ID to Configure the Encoder for Use in OnGuard ......................... 113
16.2 Configure the Encoder in OnGuard ................................................................ 114
17. ActivIdentity ActivEntry .................................................................... 117
17.1 Install the ActivEntry Module .......................................................................... 117
17.2 Access Readers ............................................................................................. 118
17.3 Set up ActivEntry ............................................................................................ 119
17.4 Configure the Badge ID .................................................................................. 119
17.5 Invalid Credentials .......................................................................................... 120
17.6 Configure the Card Format ............................................................................. 121
17.7 Badge ID and Card Format Example ............................................................. 121
17.8 Enrollment ...................................................................................................... 122
18. Fingerprint Enrollment and Verification ............................................ 125
6 — revision 6
OEM Device Configuration Guide
18.1 Cross Match ................................................................................................... 125
18.2 Sagem Morpho ............................................................................................... 127
19. GemPlus EasyAccess 332 Encoder ................................................ 129
19.1 Encoder Installation ........................................................................................ 129
19.2 Software Configuration ................................................................................... 130
20. iCLASS Encoders ............................................................................ 131
20.1 iCLASS RKL55 Programmer .......................................................................... 131
20.2 iCLASS RW400Prgm Programmer ................................................................. 134
21. Integrated Engineering .................................................................... 139
21.1 SmartID/SmartPro/SmartLOGON ................................................................... 139
22. OMNIKEY 5125 Prox/Contact and 5325 Prox USB Readers .......... 141
22.1 Installation ...................................................................................................... 141
22.2 Configuration of the 5125/5325 Readers ........................................................ 141
23. ScanShell and SnapShell Scanners ................................................ 143
23.1 CSSN ScanShell and SnapShell Installation .................................................. 143
23.2 OnGuard Configuration .................................................................................. 144
24. Topaz SignatureGem Pen Tablet .................................................... 145
24.1 SignatureGem Installation .............................................................................. 145
HID pivCLASS .................................................................. 149
25. pivCLASS Authentication Module (PAM) ......................................... 151
25.1 Install the pivCLASS Authentication Module .................................................. 152
25.2 Wiring ............................................................................................................. 152
25.3 Configure PACS Reader Services .................................................................. 154
IP Support ........................................................................ 157
26. LNL-ETHLAN (MSS1/MSS100 Ethernet Controller) ........................ 159
26.1 Establish Serial Communication with the ETHLAN ........................................ 159
26.2 Establishing Network Communications .......................................................... 160
26.3 Configuring the ETHLAN ................................................................................ 161
26.4 Device Configuration ...................................................................................... 162
27. Security Settings (SDS1100) ........................................................... 164
27.1 Supported Controller Types Over Encrypted Connection ............................... 164
28. IP Cameras ...................................................................................... 166
revision 6 — 7
Table of Contents
Index ................................................................................................................ 167
8 — revision 6
OEM DEVICES
OEM Device Configuration Guide
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 6 — 11
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
12 — revision 6
OEM Device Configuration Guide
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 6 — 13
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
14 — revision 6
OEM Device Configuration Guide
Connect the wires accordingly.
W17
S1
A
W8
W9
A B C D E
A B C
W15
W19
A B C
A B C
A B C D E
W16
B C D E
Black Box IC108A
W5
A B C
BIAS
TERM.
S3
S2
Rx A -
Tx B +
Tx A -
110 VAC
Transformer
Rx B+
XW1B
XW1A
25-Pin Serial Connector
7
3
2
TB1
1 2 3 4
5 6
(max. 4000 feet)
NIM-1R
7 8 9 10 11 12 13 14 15 16
(max.
50 feet)
DO
NOT
USE
RTS
Rx
Tx
SUPERVISED
MOM-4
1 2 3 4 5 6
5
2
3
DB 9 Pin Male
NIM-1R
7 8 9 10 11 12 13 14 15 16
E.O.L.R.
120 OHM
DO
NOT
USE
7
3
2
DB 25 Pin Female
9 or 25 Pin Connector
Workstation (PC)
TB3
revision 6 — 15
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)
16 — revision 6
OEM Device Configuration Guide
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/ID3000 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.
The ID3000 is a modular fire alarm panel intended for large facilities such as shopping malls, schools, office
buildings, hospitals, hotels, factories, and large warehouses. It connects to the LAN via a serial DB25-DB9
cable.
revision 6 — 17
Fire Panels
Connecting the NFS-640/ID3000 Panel
Use a serial cable to connect the fire panel to the host. Wire the cable directly to the panel using terminal
TB14.
18 — revision 6
OEM Device Configuration Guide
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/ID3000 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 6 — 19
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.
20 — revision 6
OEM Device Configuration Guide
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 6 — 21
Fire Panels
22 — revision 6
OEM Device Configuration Guide
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 builtin 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:
3.2
For more information, refer to the manufacturer documentation.
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 6 — 23
HID EdgeReader and EdgePlus
24 — revision 6
OEM Device Configuration Guide
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 6 — 25
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.
b.
If you are using iCLASS:
i.
Set the SmartCard Type to iCLASS.
ii.
Enter the authentication key.
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].
26 — revision 6
OEM Device Configuration Guide
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. Select the Iris data format (GSC-IS Format or Lenel Format) from the drop-down. Make sure
to choose the same format that will be used to encode the smart card.
iv. Choose the memory configuration.
When Book 1/16kbits/2 Application Areas or Book 1/16kbits/16 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.
Note:
If you are using the Lenel Format, the IrisICUAdmin4000 software does not support writing
the IrisAccess application to Book 1/16kbits/2 Application Areas or Book 1/16kbits/16
Application Areas.
v.
Next to the Iris Data Encryption Method, click [Change].
vi. Select the encryption algorithm (AES, DES, or DES3) from the drop-down.
vii. Click [Generate New Key].
viii. 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.
2.
Click [OK] to save the changes.
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
1.
Wiring a WIB4000 to LNL-1320
The WIB4000 is used to control access to a facility door. Connect this to the LNL-1320 Dual Reader
Interface Module.
revision 6 — 27
Iris Recognition
WIB4000 and LNL-1320 connection
TB9
READER 1
READER 2
GND DAT CLK BZA LED VO GND DAT CLK BZA LED VO
D0 D1
D0 D1
TB8
Dual Reader
Interface Module
NO C
RLY 6
NC
NO
C NC
RLY 5
NO C
RLY 4
NC
NO
C NC
RLY 3
TB11
Wiegand OUT 1
NO C
RLY 2
NC
NO
GND
C NC
RLY 1
TB10
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.
28 — revision 6
OEM Device Configuration Guide
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:
e.
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.
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:
8.
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.
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 6 — 29
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, set the Data format in Smart Card to either GSC-IS Format
or Lenel Format.
iii. For Book, select the same type (Book 0 or Book 1) configured for the IrisAccess card format in
the access control software. However, if you are using Lenel Format as the Data format in
Smart Card, the IrisICUAdmin4000 software does not support writing to Book 1.
iv. For the Encryption Algorithm, select the same type (AES, DES, DES3, or None) configured
for the IrisAccess card format in the access control software.
v.
b.
Click [Get Keys]. Select the key file. (This should have been generated using the access
control software and stored to a file.)
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 a stand-alone DESFire encoder, (like SmartID/Pro or Digion 24 (Mifare/
DESFire), set the Data format in Smart Card to GSC-IS Format.
iii. For the Encryption Algorithm, select None.
9.
On the Access Panel tab:
•
•
For iCAM iCLASS:
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.
Set Active State to Low.
g.
Set Pulse Duration to 120 and the Bit Period to 1000.
For iCAM DESFire:
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 Output the signal with Facility Code and Card ID for only Accept.
f.
Select Lenel FASC-N Format.
g.
Set Active State to Low.
h. Set Pulse Duration to 40 and the Bit Period to 2148.
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.
30 — revision 6
OEM Device Configuration Guide
Note:
4.2
For more information on IrisICUAdmin4000 settings, refer to the IrisAccess Software
Installation Manual. This is installed along with the EAC software.
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.
iCAM4000V and Reader Interface connection
TB9
READER 1
READER 2
GND DAT CLK BZA LED VO GND DAT CLK BZA LED VO
D0 D1
D0 D1
TB8
Wiegand OUT
GND
DATA 1
DATA 0
Reader Interface
Module
(LNL-1320
shown)
iCAM4000V
Important:
4.2.1
Verify that the wiring is done according to this drawing. Incorrect wiring might
cause hardware damage.
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.
revision 6 — 31
Iris Recognition
For more information about camera installation and configuring the following settings, refer to the
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.
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).
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.
Set the Data Format to the same format (GSC-IS Format or Lenel Format) that will be used to
encode the iris data onto the smart card.
g.
Set Book to the same format (Book 0 or Book 1) as required.
Note:
h.
If you are using the Lenel Format, the IrisICUAdmin4000 software does not support writing to
Book 1/16kbits/2 Application Areas or Book 1/16kbits/16 Application Areas.
Set the Encryption Algorithm and Encryption Key File as required by the site.
32 — revision 6
OEM Device Configuration Guide
Note:
2.
The Encryption Algorithm and Encryption Key File settings must match the Card Format
settings. For more information, refer to Card Formats on page 33.
Click [OK] to save the changes.
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 Card or 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.
6.
Click [OK] to save the changes.
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
4.
Click [OK] to save the changes.
Wiegand Settings
1.
On the iCAM web page, click [Wiegand Settings].
2.
Under Wiegand In, for the Interface, select Enable.
3.
Under Wiegand Out:
4.
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.
Click [OK] to save the changes.
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).
revision 6 — 33
Iris Recognition
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.
Set the Iris data format to the same format (GSC-IS Format or Lenel Format) that will be used to encode
the iris data.
4.
Select the Memory configuration.
Note:
If you are using the Lenel Format, the IrisICUAdmin4000 software does not support writing
the IrisAccess application to Book 1/16kbits/2 Application Areas or Book 1/16kbits/16
Application Areas.
5.
Next to the Iris Data Encryption Method, click [Change].
6.
Select the Iris Data Encryption Method (AES, DES, or DES3) from the drop-down.
7.
Click [Generate New Key].
8.
Click [Store Key to File]. Note the location of this file. It will be used for configuration in the
iCAM4000V Web user interface.
9.
Click [OK] to save the changes.
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.
4.3
Installing an iCAM7000
The iCAM7000 can be configured to emulate either the iCAM4000 or the iCAM4000V.
Note:
1.
For OnGuard compatibility, the iCAM7000 requires firmware version 7.05.01 or later.
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.
34 — revision 6
OEM Device Configuration Guide
WIB4000 and Reader Interface Wiegand connection to support iCAM4000 emulation
TB9
READER 1
READER 2
GND DAT CLK BZA LED VO GND DAT CLK BZA LED VO
D0 D1
D0 D1
TB8
Dual Reader
Interface Module
WIB4000
NO C
RLY 6
NC
NO
C NC
RLY 5
NO C
RLY 4
NC
NO
C NC
RLY 3
TB11
Wiegand OUT 1
NO C
RLY 2
NC
NO
GND
C NC
RLY 1
TB10
TB12
revision 6 — 35
Iris Recognition
iCAM7000 and Reader Interface Wiegand connection to support iCAM4000V emulation
TB9
READER 1
READER 2
GND DAT CLK BZA LED VO GND DAT CLK BZA LED VO
D0 D1
D0 D1
TB8
Wiegand OUT
GND
DATA 1
DATA 0
Reader Interface
Module
(LNL-1320
shown)
iCAM7000
Important:
4.3.1
Verify that the wiring is done according to this drawing. Incorrect wiring might
cause hardware damage.
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.
For more information about camera installation and configuring the following settings, refer to the
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.
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.100, 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:
36 — revision 6
OEM Device Configuration Guide
•
Username: iCAM7000 (case sensitive)
•
Password: iris7000
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.100).
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).
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 25.
b.
To configure the iCAM7000 to emulate an iCAM4000V, select Option 2. For more information,
refer to Configuring the iCAM4000V on page 31.
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 perform 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).
revision 6 — 37
Iris Recognition
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:
The HID Access Control (iCLASS) application must be present on the card in order to verify
the IRIS ID credential at the reader. The HID application may be encoded from OnGuard or
comes pre-encoded on cards purchased as such from HID.
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. In the card format
application, set the Iris data format to the same format that will be used to encode the smart card and the
Encryption method to AES/DES/DES3.
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:
4.6
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”.
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.
38 — revision 6
OEM Device Configuration Guide
Firmware upgrades, if applicable, are performed to the iCAM4000V or iCAM7000 using the Web user
interface.
revision 6 — 39
Iris Recognition
40 — revision 6
OEM Device Configuration Guide
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 6 — 41
Onity Programmer
42 — revision 6
OEM Device Configuration Guide
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:
6.1.1
The ID numbers for bus devices can be found printed on the circuit boards, the back of the
plastic housing, or on the packaging.
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 6 — 43
Personal Safety
6.1.2
Supported Transmitters
The following transmitters are currently 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
6.2
OnGuard Configuration
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.
44 — revision 6
OEM Device Configuration Guide
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 D6100, D6500, D6600
•
Osborne-Hoffman OH-2000
•
AES-IntelliNet 7000
OnGuard supports alarm communication over Ethernet or standard telephone lines. Alarm panels can send
full data messages via the LAN or telephone lines to a receiver.
7.1
Bosch D6100, 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 or a networked computer running the D6200 configuration software.
The receiver connects via COM 3 or COM 4 on the back of the unit. Up to eight (8) phone line termination
cards can be connected to 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 6 — 45
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.
Notes:
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 D6100/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 using the following steps.
1.
On the D6600/D6500, press the [M/E] button on the front of the receiver.
On the D6100, press the [MENU] button.
2.
You will be prompted for a password. Enter the password configured for the receiver.
On the D6600/D6500, press [M/E] again. On the D6100, press the [ENTER] button.
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.
On the D6600/D6500, press the [M/E] button. On the D6100, press the [ENTER] button.
5.
Once again use the down arrow to go to the Automation Configuration item.
On the D6600/D6500, press the [M/E] button. On the D6100, press the [ENTER] button.
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 on the D6600/D6500 ([ENTER] on the D6100), then
press either 1 or 2 for the output desired. Then press [M/E] again ([ENTER] on the D6100).
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] ([ENTER] on the D6100).
b.
Next, navigate to 6.3.7 Device. Press [M/E] ([ENTER] on the D6100).
46 — revision 6
OEM Device Configuration Guide
c.
8.
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
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.
Log out of the system. To do this, press the [CAN] button ([CANCEL] on the D6100) 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
three 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
•
Dial-up connection via optional telephone line termination cards
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.
revision 6 — 47
Receivers
For more information, refer to the Bosch Communications Receiver/Gateway manual.
7.1.4
Software Configuration
The following sections show how to configure the receiver in the D6200 receiver software and in the
OnGuard software, and how to configure the Lantronix device if connected to the receiver.
D6200 Receiver Software Configuration
1.
In the D6200 Receiver Software, go to the COM3 Automation Configuration section.
The program items in this section configure the input and output format for the receiver when a
computer automation system is connected to COM port 3 on the receiver. For more information on these
program items, refer to the documentation provided with the receiver.
COM3 Automation Configuration in D6200 Receiver Software
2.
Make the following settings:
•
Baud Rate: Set to 7 (9600) to match the Lantronix device.
•
Data Bit: Set the data transmission bit value for COM port 3 to 8.
•
Parity: Set the parity for COM port 3 to 0 (none).
•
Stop Bit: Set the stop bit value for COM port 3 to 1.
•
Output Format: Set to 1 (6500 format) or 2 (SIA Computer Interface Standard format).
48 — revision 6
OEM Device Configuration Guide
Note:
3.
The Output Format setting must match the Receiver Output Format setting made in the
OnGuard software on the Receivers > Location tab.
Go to the Network Automation Connection section.
This section details connecting the receiver to the network using COM port 4 or an integrated Ethernet
port. For more information on these program items, refer to the documentation provided with the
receiver.
COM3 Automation Configuration in D6200 Receiver Software
4.
Make sure that the IP address field is empty and that the Network Automation Output Format is set
to 0.
Note:
If an IP address or network automation output format is entered in the D6200 software, these
settings will override the equivalent settings made in the OnGuard software. As a result,
OnGuard will not be able to connect to the receiver.
revision 6 — 49
Receivers
5.
To allow the D6200 software to program the receiver, go to the D6200 Network Connection section
and make the following settings using the receiver’s built-in keypad:
•
In the IP Address 1 field, enter the IP address of the computer running the D6200 software. Use
the receiver’s built-in keypad to enter the IP address. Use the “UP” key to enter a . (IPv4) and the
“DOWN” key to enter a : (IPv6).
One receiver can communicate with three different computers running the D6200 software. Enter
additional IP addresses as necessary in the IP Address 2 and IP Address 3 fields.
•
Set Network Programming Enable to 1 (Enable network programming).
OnGuard Software Configuration
To configure the receiver in OnGuard:
1.
Open System Administration and go to Additional Hardware > Receivers.
2.
To add a new receiver, click the Add button.
3.
On the Location tab:
a.
Enter a name for the receiver in the Name field.
b.
Enter (or browse for) a workstation in the Workstation field.
c.
In the Receiver output format field, make sure the selection made here matches the setting made
in the Output Format field in the COM3 Automation Configuration section of the D6200 receiver
software.
Note:
Once set, the Receiver output format in OnGuard cannot be changed.
Receivers > Location Tab in the OnGuard Software
50 — revision 6
OEM Device Configuration Guide
4.
On the Connection tab:
a.
Enter the port number for the Lantronix device connected to COM port 3 on the receiver.
b.
Enter the IP address for the Lantronix device connected to COM port 3 on the receiver.
Receivers > Connection Tab in the OnGuard Software
5.
Leave the Options tab at the default settings. The Options tab is for advanced configuration.
6.
Click OK to save your changes.
7.
In the Monitor Zone Assignments dialog, select the desired monitor zone for the receiver. Click OK.
The receiver is now configured in the OnGuard software.
revision 6 — 51
Receivers
Lantronix Device Configuration
To configure the Lantronix device connected to the receiver:
1.
From the workstation connected to the receiver, open a Telnet session with the Lantronix device.
Telnet Session Window
2.
Configure Channel 1 by pressing 1 and then [Enter] on the workstation’s keyboard.
3.
Make the following settings:
- Baud Rate: 9600
-
This must match the setting made in the COM3 Automation Configuration section of the D6200
Receiver Software.
I/F Mode: 4C
Flow: 00
Port No: 3001
-
This must match the port number setting made in OnGuard on the Receivers > Connection tab.
Connect Mode: C0
4.
Make sure all other options are set to No or 0 as shown in figure above.
5.
Select 9 to save the settings made and exit the Telnet session.
52 — revision 6
OEM Device Configuration Guide
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 the 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
revision 6 — 53
Receivers
For more wiring information, refer to the AES IntelliNet 7000 Series Receiver Installation and Operation
Manual.
Pin number
7000/2
Signal
I/O
At 9-pin
At 25-pin
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:
54 — revision 6
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.
OEM Device Configuration Guide
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 6 — 55
Cypress Timer
8.1
System Level Wiring
RS-485
power
Power Supply
Multi-Drop,
Central Power
ISC
RS-485
12 VDC
12 VDC
Multi-Drop, Local Power
ISC
RS-485
Multi-Drop, Daisy-Chain and Home-Run
Power Supply
ISC
56 — revision 6
12 VDC
OEM Device Configuration Guide
Front of unit
5.3
3.5
1.3
1.0
3.25
3.4
Back of unit with base plate removed
YELLOW
GREEN
BLACK
RED
+
+12 VDC
GND
+
+
+
ISC
TR1+
TR1R1 +
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 6 — 57
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.
58 — revision 6
OEM Device Configuration Guide
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 6 — 59
Cypress Timer
Cover
5.3
.55
3.5
.90
1.3
3.25
1.4
60 — revision 6
.90
OEM Device Configuration Guide
8.4
Wall Mounting
Mount enclosure to wall with electrical box (single gang).
Top View
wall
harness
CCK-1201
Top View
wall
revision 6 — 61
Cypress Timer
62 — revision 6
OEM Device Configuration Guide
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 6 — 63
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
64 — revision 6
OEM Device Configuration Guide
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 6 — 65
TVS TVC-2100 Series Video Text Inserter
66 — revision 6
OEM Device Configuration Guide
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 6 — 67
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
is assigned to by
default
FormsDesigner form(s) the
field is located on
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.
68 — revision 6
OEM Device Configuration Guide
b.
3.
Click [OK].
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 6 — 69
Corex CardScan
70 — revision 6
OEM Device Configuration Guide
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-7081BKU) 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 6 — 71
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
•
Facility Code number of bits = 8
•
Badge ID start bit = 9
•
Badge ID number of bits = 48
•
Issue Code Start Bit = 56
•
Issue Code number of bits = 8
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:
•
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
72 — revision 6
OEM Device Configuration Guide
•
Odd parity bit = 26 (there is one parity bit at the end)
If you need to configure the reader for another Wiegand bit format, use the pcProxConfig and AIR ID Enroll
software:
1.
Install and open the pcProxConfig software.
2.
Select the Connect tab.
3.
Reset the reader by clicking [Reset to defaults].
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 rechecked.
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
•
Facility Code number of bits = 8
•
Badge ID start bit = 9
•
Badge ID number of bits = 48
•
Issue Code Start Bit = 56
•
Issue Code number of bits = 8
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 6 — 73
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:
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 checkbox.
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)
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.
74 — revision 6
OEM Device Configuration Guide
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 6 — 75
RFIDeas Readers
76 — revision 6
OEM Device Configuration Guide
12
Assa Abloy Aperio Locks
Aperio locks can communicate wirelessly with the access control system to read credential information and
send access decisions. The Aperio hub is connected to a controller (LNL-3300/2220/2210) which
communicates with the Aperio wireless lock. The Aperio Hub 1-1 supports one wireless lock. The Aperio
Hub 1-8 supports up to eight wireless locks.
12.1
Hardware Installation
In order for the controller to communicate with the hub, it requires firmware version 1.187 or later. For more
detailed information, refer to the manufacturer documentation.
12.1.1
Aperio Hub
Install the Aperio hub in the best possible location for a stable and reliable radio link. Connect the hub to the
controller. The hub may only be connected to the LNL-3300, 2220, or 2210. Use a twisted-pair cable with
characteristic impedance between 90 Ohm and 120 Ohm.
Controller-Hub Connections
From Controller
To Aperio Hub
Power (V 5-30 VDC)
Power (24 VDC)
Ground (GND)
Ground (GND)
TR–
RS-485 B
TR+
RS-485 A
Set the address for the hub using DIP switches 1-4. For more information, refer to the Addressing Table in
the Aperio Reference Manual.
DIP Switches
Switch
Description
1-4
Address – switch 1 (bit-0) through 4 (bit-3). Addresses
1-15 are supported. Address zero should never be used.
5
Not used
6
Controls use of an RS-485 B pull down resistor.
ON = 620 Ohm pull down connected.
7
Controls use of an RS-485 A pull up resistor.
ON = 620 Ohm pull up connected.
8
Terminating resistor - should be switched on only on the
last hub connected on the line.
9
Not used
revision 6 — 77
Assa Abloy Aperio Locks
DIP Switches (Continued)
Switch
Description
10
Select internal antenna (INT) or external antenna (EXT)
12.1.2
Communication Hub LED Indication
The communication hub has a single LED. It supports an optical scheme with red, green and yellow. The
indication scheme is described by the two figures below:
Note:
EAC refers to the Electronic Access Control System.
Some special LED indication schemes are used during lock maintenance actions:
12.1.3
Aperio Locks
To pair and configure the Aperio locks, use the Aperio programming application included with the
hardware. The devices are identified by their MAC address. You will need the USB radio dongle (to be
installed with its driver) and an encryption key file. Follow the instructions provided in the Aperio
documentation to configure the devices.
Status Report Interval
Be sure to set the hub status interval time to be twice that of the locks so that the locks do not incorrectly
report their status as offline. For example, if you set the hub status report interval to be 60 minutes, you
should set the lock status report interval to be 30 minutes.
78 — revision 6
OEM Device Configuration Guide
Failure to do so may cause false offline lock alarms. Setting the status interval time this way will allow a
lock to report offline only if it was not detected after two check-in cycles. There is separate configuration for
the hub versus the lock.
Using the Aperio programming application:
1.
Right-click on the Hub and select Configure (make sure there is more than one lock in the list).
2.
Click Next until you are presented with the Status Report Interval configuration.
3.
Click Change and change it to be twice the time you will set for the lock.
4.
Click Next until the change is confirmed.
5.
Repeat this procedure for the Lock, setting the interval time to be half the time set for the hub.
6.
You may need to present a credential to the reader to complete this operation.
Once the application confirms the changes, then there should be no false offline lock alarms.
12.2
OnGuard Configuration
Before adding the Aperio lock, a controller must already be configured in System Administration. Only the
LNL-3300, 2220, or 2210 are supported.
12.2.1
Add the Aperio Lock
The configuration for this device is done in System Administration, in the Readers and Doors folder.
1.
On the General form of the Readers and Doors folder, click [Add].
2.
Type in a name for the Aperio lock being configured.
3.
Choose the Panel to which the hub is connected.
4.
For the Reader Type, select either an Aperio Hub 1-1 (Wiegand/Prox) or Aperio Hub 1-8 (Wiegand/
Prox), depending on the hub you are using.
5.
For Aperio Hub 1 - 1: Enter the Port and Address. (Reader number is pre-configured to “0” because
Hub 1- 1 supports a single reader, only.)
6.
For Aperio Hub 1 - 8: Enter the Port, Address, and Reader number.
7.
Configure the Online Reader Mode.
8.
Assign a Card Format.
9.
Click [OK].
Some options are not available because they are not features of the Aperio locks. For more information, refer
to the System Administration User Guide.
12.2.2
First Card Unlock for Aperio
An unsecured reader mode is supported by Aperio locks only when there is a special feature enabled (First
Card Unlock or Double Card Unlock/Toggle). For first card unlock, there must be a predetermined time and
duration for this particular mode. This is done through configuration of the First Card Unlock option and
setting up a timezone for the reader mode change. During the configured time interval, the first card with a
valid access grant causes the Aperio lock to enter into an unlocked state. The Aperio lock is then
automatically relocked at the end of the configured time interval.
revision 6 — 79
Assa Abloy Aperio Locks
To configure this reader mode, you must enable first card unlock, configure the timezone, and then assign
the timezone reader mode in System Administration.
This feature supports the Override Reader Mode feature. For more information, refer to Override Reader
Mode on page 81.
Configure First Card Unlock
1.
2.
3.
Configure First Card Unlock on the access panel.
a.
In the Access Panels folder, on the form for the controller to which the hub was connected, navigate
to the Options tab.
b.
Click [Modify].
c.
Select the check box, First card unlock.
d.
Click [OK].
Configure the Timezone.
a.
In the Holidays/Timezones folder, on the Timezones form, create a new timezone with the desired
start and end times.
b.
On the Timezones form, click [Add].
c.
Type in the name for the timezone.
d.
Enter the start and end times for interval 1. The Aperio lock will become unlocked with the first
card (resulting in a valid access grant) used within the time interval. It will automatically be
relocked at the end time. Only the first time interval is used for controlling the relock time for the
Aperio lock.
e.
Click [OK].
Configure the Timezone Reader Mode.
a.
In the Holidays/Timezone folder, on the Timezone/Reader Modes form, configure the Aperio lock
for the unlocked mode and timezone.
b.
On the Timezone/Reader Modes form, click [Modify].
c.
Choose the Aperio lock listed under Reader.
d.
Choose the Timezone that was configured under Timezone.
e.
Select the check box, First Card Unlock.
f.
Click [Assign].
g.
Click [OK].
Limitations
•
Only the first time interval for a given timezone is used for controlling the relock time for the Aperio
lock. Assigning additional timezones will not affect the relock time.
•
If this timezone is changed, the new time interval will not become effective until the next time the lock
enters the unlocked state.
•
An Aperio lock may be removed from its unlocked state by changing the reader mode in Alarm
Monitoring. Note that the relock will not occur immediately. It will occur at the next scheduled check in
time (based on the status report interval that was configured) or when there is access activity at the lock.
•
If the Communication Server and/or panel communications go offline then are brought back online, any
updates made to the timezone/timezone reader mode will be in effect only after performing a download
to the panel or reassigning the timezone reader mode to the Aperio lock.
80 — revision 6
OEM Device Configuration Guide
•
The Aperio scheduled relock will only work for the Start timezone assigned to the reader. If First Card
Unlock is selected for the End timezone reader mode association, it will not unlock the reader
immediately when an access grant occurs. In this case, the lock will unlock the next time the reader
checks in with the hub.
12.2.3
Override Reader Mode
Available on LNL and Lenel M series controllers and access panels.
Some commands in OnGuard utilize what is referred to as the “Override Reader Mode.” The Override
Reader Mode is as an “additional” reader mode that overrides the standard reader mode. While an Override
Reader Mode is active, any changes to the standard reader mode are not applied to the reader (but are
tracked by the panel in the background). Commands that use the override will expire after a configured time
or must be aborted before the standard reader mode will be restored. When override is aborted or expires, the
current state of the standard reader mode (as tracked by the panel) is restored.
Once an Override Reader Mode is entered, the only way to return the readers to normal operation is to
manually change the Reader Access Mode in Alarm Monitoring (which allows you to abort the override for
the reader or readers selected). Optionally, you can “Pulse” the function which automatically aborts all of the
readers. The Override Reader Mode will also end at the end of the time specified in the function.
OnGuard commands that support the Override Reader Mode include All Reader Lock/Set Mode (Local I/O),
Double Card Unlock/Toggle, and First Card Unlock. For more information, refer to the System
Administration User Guide.
revision 6 — 81
Assa Abloy Aperio Locks
82 — revision 6
OEM Device Configuration Guide
13
Schlage Reader and Lock Solutions
OnGuard 6.6 SP1 or later supports the following Schlage reader and lock solutions:
•
Schlage PIM-485 (AD-400/401) wireless locks and Schlage Wired-485 (AD-300) hard-wired locks can
communicate via Panel Interface Modules (PIM400-485s) that are directly connected to the controller
(LNL-3300/2210).
When you configure a Schlage PIM that is connected to a Lenel controller port (LNL-3300/2210), the
controller will communicate using the Schlage protocol on its communication port. This port will then
only support Schlage devices and cannot be shared with standard Lenel downstream devices.
The LNL-2220 does not support the Schlage protocol as this controller only supports a single
communication port which would sacrifice its capacity.
•
A PIM400/401-TD2 is required for Wiegand communication between the AD-400 wireless locks and
the reader interface (LNL-2220/1320/1300). For more information, refer to Wiegand Only Integration
on page 97.
Note:
13.1
New Schlage PIM devices do not require the use of the LNL-500W gateway.
Locks and Readers
The following Schlage Wireless Access Point Modules (WAPMs) are supported:
•
AD-400/401 Wireless Lock - A networked, wireless electronic lock. Has built-in intelligence that
allows you to monitor the status at each door in OnGuard via Alarm Monitoring. For more information,
refer to the Alarm Monitoring User Guide.
•
AD-300/301 Hardwired Lock - A networked hardwired electronic lock. Direct RS-485 or Wiegand
connection. The AD-300 lock is essentially a PIM supporting one (1) lock (WAPM). It is wired directly
to the access panel similar to a traditional single-reader interface.
•
WRI400 Wireless Reader Interface - The WRI400 is a networked access point controller designed to
provide real-time wireless access control to traditional electronic access control components, as well as
creating wireless access control solutions for remote gates and elevators. It extends the AD-400 access
control platform to applications that require networked control of wall-mounted credential readers and
traditional electronic access control technology such as electronic strikes or magnetic locks.
•
WPR400 Wireless Portable Reader - The WPR400 was designed to extend a facility’s access control
to remote locations, at a moment’s notice. The WPR400 is a portable device that utilizes the same
credential reader module as an AD-Series electronic lock. The WPR400 can be held by hand or placed
in a convenient temporary location to allow for credential verification.
The WRI400, WPR400, as well as the AD-400 communicate data via 900 MHz radio frequency back to
either a PIM400-485 or PIM400-TD2.
Notes:
Readers: The WRI400 does not support magnetic readers.
Strike time: Although editable in OnGuard, Strike time has no effect on the reader. You must
configure strike time using the Schlage Utility Software.
Reader modes: With the default WRI400 settings and Reader mode set to “Lock” or
“Unlocked” in OnGuard, the reader connected to the WRI400 will lock or unlock when any
badge is presented to it, and then return to the secured mode when the badge is presented again.
revision 6 — 83
Schlage Reader and Lock Solutions
(The reader also returns to secured mode automatically after 10 minutes.) Therefore, configure
this timeout period for two (2) seconds using the HHD (Handheld Device) and Schlage Utility
Software.
13.1.1
Inputs, Outputs, and Readers
Each WAPM has two (2) inputs and (1) one output. The first input is the door contact and the second input is
the REX. The output is the door strike. If MKO (Mechanical Key Override) is detected, it is mapped
internally to REX-1 for that reader. For more information, refer to Mechanical Key Override Detection on
page 87.
The number of readers configured per PIM should match the actual number of readers configured in the
PIM.
13.2
Hardware Installation
Three configurations are available with LNL-3300/2210 firmware revision 1.187 or later, including:
1.
Schlage PIM wired to LNL-3300: The AD-400 locks are then paired with the PIM. Up to 16 PIMs can
be attached per downstream port. A total of 16 PIMs can be attached per controller with a maximum of
64 locks across the entire controller. Each PIM can support up to 16 AD-400 wireless locks (WAPMs).
Select “Schlage PIM-485” as the Reader type for this configuration.
Note:
2.
3.
For performance reasons, a maximum of 8 PIMs per downstream port is recommended.
Schlage PIM wired to LNL-2210: The AD-400 locks are then paired with the PIM. One (1) PIM can
be attached to the LNL-2210 with up to 16 wireless locks. Select “Schlage PIM-485” as the Reader type
for this configuration. This option is available in either of the following hardware configurations:
a.
Install the PIM400-1501-LC and LNL-2210 as separate units.
b.
Install the PIM400-1501 as a single unit (includes a built-in LNL-2210 in same enclosure). For
more information, refer to PIM400-1501 on page 86.
Schlage AD-300 wired to Lenel controller (LNL-3300/2210): Select “Schlage Wired-485” as the
Reader type for this configuration. You can mix Schlage Wired-485 locks and Schlage PIM-485 based
wireless locks on the same downstream port. Up to eight (8) AD-300 locks are supported by the
LNL-2210.
Note:
84 — revision 6
Once you configure a Schlage PIM-485 or Schlage Wired-485 device on a given downstream
port, other device types cannot be mixed on that port. You can only add more Schlage devices.
OEM Device Configuration Guide
For example, Lenel devices (such as the LNL-1320) and Schlage devices cannot share the
same downstream port.
System Capabilities
Features
AD-400
AD-300
PIM400-485
PIM400-1501
Direct RS-485
Maximum number of readers supported by
controller
64
16
16
Maximum number of devices per PIM400-485
16
16
N/A
Maximum number of devices per PIM400-1501
N/A
16
N/A
Maximum number of devices per RS-485 port
8
N/A
8
Communications to and from controller
RS-485
TCP/IP
RS-485
Note:
Communication within the PIM400-1501 is actually RS-485, whereas communication from
OnGuard to the PIM400-1501 is TCP/IP. Wireless communication between the PIM and AD400 is accomplished via RF protocol.
Lenel controllers override the following functions:
•
AD-400 (Schlage PIM-485) heartbeat
•
Relatch later (number of seconds, timer only, on door open or timer, on door close or timer)
•
Wake-up on Radio (WoR)
Limitations
Request-to-Enter and Serial Number Polling from the lock are not supported.
13.2.1
PIM400-485
Install the PIM400-485 in the best possible location for a stable and reliable radio link. Connect the PIM to
the controller (LNL-3300 or LNL-2210). Use a twisted-pair cable with characteristic impedance between 90
Ohm and 120 Ohm.
When clear line-of-sight is available, communication with the lock may be possible up to 1000 feet. For
further considerations, refer to the manufacturer’s PIM400 and PIM401 USER GUIDE.
Controller-PIM Connections
From Controller
To PIM
Power (V 5-30 VDC)
Power (12 VDC or 24 VDC)
Ground (GND)
Ground (GND)
TR–
RS-485 (RB+)
TR+
RS-485 (TA-)
revision 6 — 85
Schlage Reader and Lock Solutions
Wiring diagrams are available at the manufacturer’s web site at www.schlage.com/support for the AD-Series
Locks. For example: http://us.allegion.com/IRSTDocuments1/105273.pdf
13.2.2
PIM400-1501
The PIM400-1501 is a plastic enclosure containing one LNL-2210 and one PIM400-485. Although
OnGuard treats both of these components as separate units, the PIM400-1501 provides a compact solution
that simplifies installation and cost of implementation.
The PIM400-1501 is pre-wired with external RJ-45 and USB connections. To further simplify installation,
the device can be Powered over Ethernet (PoE) or receive a 12VDC power supply.
13.3
Access Control Features
Interior pushbutton, mechanical key override, and deadbolt detection are only available when the lock is
linked via PIM400-485.
Remote linking only applies to the Schlage PIM-485 readers.
13.3.1
Wake-Up on Radio (WoR)
This feature is automatically enabled when wiring a PIM to a Lenel controller. If you switch Wake Up on
Radio (WoR) to OFF using the Handheld Device (HHD), this setting will be overridden to ON once the PIM
begins communicating with the Lenel controller.
When Wake-up on Radio is enabled, the lock will respond within 10 seconds or less to a command from the
access control panel. When Wake-up on Radio is disabled, the lock will respond only during its heartbeat.
13.3.2
Multi-Dropped PIMs
The PIM must be configured with a unique RS-485 communication address within each downstream port.
The “low door” and “high door” range for the PIM allocates the number of readers that will communicate
with the PIM. Valid reader addresses include 0 - 254. Reader address 170 must not be used.
It is recommended that the reader address range within each PIM be defined as a range of 16. This allows for
a reader to be added in the future without having to re-address the address ranges on other PIMs.
86 — revision 6
OEM Device Configuration Guide
Important:
There are not enough reader addresses to support a full complement of 16 readers
on all 16 PIMs. Therefore, care must be used not to overlap or duplicate readers
addresses on each of the communication ports.
Example: The following reader addresses are only suggested addresses.
PIM Communication
Address
Low Lock Address
High Lock
Address
PIM-0
door low = 0
door high = 15
PIM-1
door low = 16
door high = 31
PIM-2
door low = 32
door high = 47
PIM-3
door low = 48
door high = 63
PIM-4
door low = 64
door high = 79
PIM-5
door low = 80
door high = 95
PIM-6
door low = 96
door high = 111
PIM-7
door low = 112
door high = 127
13.3.3
Mechanical Key Override Detection
If the key is used to open the door from the outside, the “Door Open by Key” alarm is reported.
13.3.4
Deadbolt Detection
If you have a Schlage lock with the deadbolt wired, it can perform various functions, as follows:
•
When “throwing” the deadbolt, an “Internal Deadbolt” alarm will be generated.
•
When the deadbolt is removed, an “Internal Deadbolt Off” alarm will be reported.
•
When the deadbolt is “thrown” it changes the reader access mode to Locked. If you present a card to the
reader, it will generate an “Access Denied: Reader Locked” alarm.
•
When you remove the deadbolt, the access mode that was in place prior to the deadbolt being thrown
will be restored.
13.3.5
Low Battery Indications
When a low battery condition is detected for the PIM-485 based wireless lock, a “Low Battery” event is
sent. The lock will still operate for several hundred operations, but the lock batteries should be replaced
immediately to avoid failure.
When a “Battery Failure” condition occurs, the lock will send the “Battery Critical” event. Almost
immediately after that, OnGuard will receive a “Communication Lost” event and then the lock will assume
the offline condition configured from the Handheld Device (HHD). OnGuard offline reader modes do not
affect PIM-485 based wireless locks.
revision 6 — 87
Schlage Reader and Lock Solutions
Note:
The behavior of a lock with a low battery condition depends on which reader and battery pack
is installed on the lock. Typically, when “Low Battery” is indicated, there will be
approximately 500 cycles remaining before the lock reaches the “Battery Critical” level and
shuts down into a pre-configured mode (set via the HHD) of fail secure, fail unsecure, or Fail
as is.
Use SUS to Check Battery Voltage
During a Low Battery condition, the AD-400 wireless lock may operate but not have sufficient power to
communicate with the SUS. When initiating SUS communication, the Schlage button on the lock will light
solid RED for one second to indicate insufficient battery power. If this occurs, replace the batteries
immediately.
Note:
Battery replacement does not affect any programmed data.
Condition
Indicator
Solution
Low Battery
No LED or beeps
Replace batteries immediately
to avoid failure.
Low Battery condition is
reported to the PIM400-485.
Battery Failure
(configure by SUS)
13.3.6
No LED or beeps
Replace batteries immediately.
Valid credentials do not grant
access.
Mechanical override key must
be used to unlock the lock.
Pairing Schlage PIM-485 Wireless Locks
Two options are available for linking the Schlage PIM-485 based wireless locks.
•
From Alarm Monitoring, put the PIM400-485 into Link Mode, and then put the door (lock) into Link
Mode. For more information, refer to Remote Linking from Alarm Monitoring on page 91.
•
Use the Schlage Utility Software (SUS) on the Handheld Device (HHD) to put the PIM400-485 into
Link Mode, and then put the door (lock) into Link Mode. For more information, refer to the Schlage
Utility Software User Guide at www.schlage.com/support.
13.4
OnGuard Configuration
Before adding a Schlage lock, an access control panel must already be configured in System Administration.
Only the LNL-3300 and LNL-2210 intelligent controllers support Schlage PIM-485 and Schlage Wired-485.
13.4.1
Add the Schlage Lock
From System Administration, complete the following steps:
1.
From the Access Control menu, select Readers and Doors.
88 — revision 6
OEM Device Configuration Guide
2.
On the General tab, click [Add].
3.
Type in a name for the lock being configured.
4.
Choose the Panel to which the PIM is connected.
5.
Click [OK].
Reader Number, Port, and Type
Schlage wireless locks are configured similar to readers in System Administration. When configuring the
lock in OnGuard, a unique reader number will be specified according to the port and address of the PIM. The
first reader on a PIM must always be present and identified as reader number 0.
6.
Specify the Reader type.
a.
b.
7.
8.
9.
For AD-400 wireless locks, choose either:
–
Schlage PIM-485 (Wiegand / Prox)
–
Schlage PIM-485 (Mag w/Wiegand output)
For AD-300 locks, choose either:
–
Schlage Wired-485 (Wiegand / Prox)
–
Schlage Wired-485 (Mag w/Wiegand output)
Specify the Port.
a.
For locks connected to the LNL-2210: Select “Reader 1”.
b.
For locks connected to the LNL-3300: Select the port where the PIM is connected (2,3).
Specify the Address and Reader number.
a.
For Schlage Wired-485, enter the Address, only. Use the RS-485 address of the AD-300. Reader
number is not required because the AD-300 is a reader and a PIM, and the same RS-485 address
applies to both components.
b.
For Schlage PIM-485, enter the Address and Reader number. Choose a reader number from 0-15
for each PIM. The Address must be the RS-485 address of the PIM. For more information, refer to
Multi-Dropped PIMs on page 86.
Configure the Online Reader Mode.
10. Assign a Card Format.
11. Click [OK].
Some options are not available because they are not features of the Schlage locks. For more information,
refer to the System Administration User Guide.
13.4.2
Interior Push Button Mode (IPB)
Pressing the Interior Push Button (IPB) on the inside housing of the lock may be used to communicate
various IPB lock and unlock requests.
revision 6 — 89
Schlage Reader and Lock Solutions
Note:
This feature supports the Override Reader Mode feature. For more information, refer to
Override Reader Mode on page 91.
Inside
Interior Push Button (IPB)
The manner in which the IPB communication is used by OnGuard is configured in System Administration.
A description of the expected lock behavior for each IPB mode follows:
Prior to pressing the IPB, the reader is normally secure and the inside lever / REX always allows free egress.
•
None - The Interior Push Button (IPB) function is not in use.
•
Classroom - The interior push button may be used to select a classroom status. Valid toggle credentials
on the exterior may be used to change to a passage (unlocked) or secured status. In order for the
Classroom mode to work, the reader also needs to have the Double card unlock/toggle option selected
from the Readers and Doors Settings form in System Administration.
•
Privacy - The interior push button may be used to select a privacy status. When the lock is in privacy
mode, electronic access from the exterior is disabled (changed to locked). Opening the door from the
inside or pressing the interior push button a second time deactivates the privacy feature.
•
Office - The interior push button may be used to select a passage (unlocked) or secured status.
•
Apartment - The interior push button may be used to select a passage (unlocked) or secured status.
Opening the door or pressing the interior push button causes the lockset to toggle unsecured. While
toggled unsecured, the lock can only be secured while the door is closed by pressing the interior push
button or by using a valid credential on the exterior. Normal electronic access from the exterior is
always allowed.
AD-400/300 IPB activity is reported to the OnGuard software. When you press the interior push button, an
“Interior Pushbutton: X” alarm is reported where “X” is the mode currently assigned to the push button. For
example, if “Privacy” is assigned in OnGuard for the lock, then the alarm reports “Interior Pushbutton:
Privacy.”
90 — revision 6
OEM Device Configuration Guide
Assign an Interior Push Button Mode to the Lock
From System Administration, complete the following steps:
1.
From the Administration menu, select Readers and Doors.
2.
On the Controls tab, click [Modify].
3.
Select the lock.
4.
Choose the Interior pushbutton mode you want to assign to the lock.
5.
Click [OK].
13.4.3
Override Reader Mode
Some commands in OnGuard utilize what is referred to as the “Override Reader Mode.” The Override
Reader Mode is as an “additional” reader mode that overrides the standard reader mode. While an Override
Reader Mode is active, any changes to the standard reader mode are not applied to the reader. Commands
that use the override will expire after a configured time or must be aborted before the standard reader mode
will be restored. When override is aborted or expires, the current state of the standard reader mode is
restored.
OnGuard commands that support the Override Reader Mode include All Reader Lock/Set Mode (Local I/O),
Double Card Unlock/Toggle, and Interior Pushbutton (IPB) Mode support. For more information, refer to
the System Administration User Guide.
13.4.4
Remote Linking from Alarm Monitoring
You can initiate the link mode for Schlage PIM-485 wireless locks from Alarm Monitoring.
Important:
Only one (1) Schlage PIM-485 can be linked at a time. Ensure no other Schlage
PIM-485 units are in link mode during this process.
Initiate Link Mode from Alarm Monitoring
From Alarm Monitoring, complete the following steps:
1.
From the View menu, select System Status > New System Status Window.
2.
Expand the controller to which the Schlage PIM-485 lock is assigned.
3.
Right-click on the lock, and then select Remote Link Mode > Start. When the remote linking process
begins, you will receive a “Remote Link Active” alarm.
Note:
If necessary, you can abort the link process only for a lock has already been set to start linking
by selected Abort from the Remote Link Mode menu.
4.
At the door corresponding to the lock selected in Alarm Monitoring, perform the lock linking operation.
For instructions, refer to the manufacturer's AD-400/AD-401 NETWORKED WIRELESS LOCK
USER GUIDE.
5.
When the linking process is completed, the “Remote Link Inactive” alarm is reported.
revision 6 — 91
Schlage Reader and Lock Solutions
13.4.5
PIM400-485
13.4.6
Configuration Software
The RS-485 address of the PIM400-485 needs to be set to 0. This may also be referred to as the ‘PIM Addr.”
Each reader communicating with the PIM400-485 also has an address. This range cannot exceed 16
addresses. The first address must be set to 0. The PIM400-485 should be configured using the Schlage
Utility Software as 0 for “Addr Lo” and 15 for “Addr Hi.”
The Schlage Utility Software (SUS) is a software application that runs on a Windows CE-based handheld
device (the HHD). It is used to transfer data files between the access control software and locks and
controller. From the SUS, you can configure, edit, and program the PIM400-485 and locks.To begin using
the SUS, complete the instructions in the following sections:
1.
Download and Install Synchronization Software on page 93
2.
Connect the Handheld Device to the Computer on page 93
3.
Configure the Synchronization Software on page 93
4.
Install/Update the Schlage Utility Software on page 94
5.
Start the Schlage Utility Software on page 94
92 — revision 6
OEM Device Configuration Guide
For additional information about connecting to and programming the locks, refer to Connect the HHD to the
Lock on page 105.
Synchronization Software
Synchronization software is required to interface and synchronize with the HHD device on your computer.
You can use it to install or update software applications on your HHD device. When installed and configured
properly, files will be automatically transferred between your computer and the HHD device when the HHD
device is connected to the computer.
Note:
This software may already be installed on your computer.
Handheld Device (HHD)
A Windows CE-based handheld device (HHD) installed with Schlage Utility Software is used to configure
the PIMs links and outputs, transfer data files between the access control software and the AD-400/401
locks and controllers. For detailed information about the HHD, refer to the Schlage Utility Software User
Guide on the Schlage web site: http://www.schlage.com/support.
13.4.7
Download and Install Synchronization Software
1.
Browse to www.microsoft.com/windowsmobile/en-us/downloads.
2.
For Windows 7, Windows 8, or Windows 8.1, download Microsoft Windows Mobile Device Center.
13.4.8
Configure the Synchronization Software
Microsoft Windows Mobile Device Center:
1.
Open the Windows Mobile Device Center from the computer.
2.
Connect the HHD device to your computer’s USB port.
3.
Click Setup your device.
4.
Deselect all check boxes except Files. Click [Next].
5.
Type a name for the device in the Device name field.
6.
Click [Set Up].
Synchronization Folder
The synchronization software looks in the synchronization folder for files that should be synchronized with
the HHD device. When you configure your access control software, you will need to know the location of
this file on your computer.
13.4.9
Connect the Handheld Device to the Computer
1.
Locate the HH-USB cable that came in the box with the handheld device. Insert the USB end into the
computer’s USB port.
2.
Power on the handheld device.
revision 6 — 93
Schlage Reader and Lock Solutions
3.
Insert the other end of the cable into the bottom of the handheld device.Install/Update the Schlage
Utility Software.
13.4.10
Install/Update the Schlage Utility Software
Although SUS is already installed on your handheld device, you should make sure you have the latest
revision of the software.
1.
Run the installer and follow the on-screen instructions.
a.
Download the installer (Schlage Utility Setup Ver x.x.xx.exe; the version may vary) from
www.schlage.com/support.
b.
Make sure you have already installed and configured the synchronization software.
c.
Make sure the HHD is connected to the computer’s USB port and is powered on.
d.
Start the installer.
e.
Perform the on-screen instructions. The synchronization software will automatically transfer the
software to the HHD.
Note:
13.4.11
When updating Schlage Utility Software, all passwords are reset to their defaults.
Start the Schlage Utility Software
1.
On your handheld device, from the Start menu, select Programs.
2.
Touch the Schlage Utility Software icon.
3.
Log on as either a Manager or an Operator.
4.
If you are starting the SUS for the first time, change the Manager and Operator passwords, and the
Coupling Password, to maintain security.
For more information, refer to the Schlage web site.
13.4.12
Configure the PIM400-485 and Lock Address Range
1.
Connect the HHD to the PIM400-485.
2.
On the HHD, log onto SUS.
94 — revision 6
OEM Device Configuration Guide
3.
On the Main Screen, select Device Options.
4.
On the Device Options screen, click [PIM Properties].
5.
The RS-485 Address of the PIM400-485 must be set to 0 (the default). Each AD-400/401 wireless lock
that communicates with the PIM400-485 also has an address. The range of available lock addresses
cannot exceed 16. The first address must be set to 0. The PIM400/401 should be configured for a Low
Door address of 0 and a High Door address of 15.
revision 6 — 95
Schlage Reader and Lock Solutions
13.4.13
Link the Wireless Lock to the PIM400-485
The Link tab is used to link a wireless lock to the Panel Interface Module. Before performing any other
operation, you must first place both the Panel Interface Module and the wireless lock into Link mode.
13.4.14
Use the HHD to Couple to the PIM400-485
1.
Remove the PIM400-485 cover.
2.
Connect the HHD to the PIM400-485 using the HH-USB cable. The PIM400-485 will be displayed on
the HHD screen.
3.
On the HHD, select Device Options.
13.4.15
1.
Put the PIM400-485 into Link Mode
On the PIM400-485, press and hold the LINK 1 button (S2), and then press the LINK 2 (S3) button
three (3) times.
MOUNT
THIS
SIDE
UP
J4
J9
+
RX TX
12-24 VOLTS
DC ONLY
-
J20
J2
RS485
GRD
TB +
POWER /TAMPER
Link 1 Button (S2)
Link 2 Button (S3)
J18
RB+
TA RA-
RESET
S1
J1
J5
DOOR 1
STRIKE D1/
STRIKE D1/
REQ. TO
STATUS
INPUT CLK DATA GRD INPUT CLK DATA GRD ENTER TROUB LE
J8
J7
REQ. TO
EXIT
J10
ACCESS POINT 1
2.
DOOR 2
REQ. TO
STATUS
ENTER TROUB LE
REQ. TO
EXIT
J11
ACCESS POINT 2
Continue holding the LINK1 (S2) button (at least 15 seconds) until communication is established. This
will be indicated when the PIM device name is displayed on the SUS main screen and the LED begins
to flash red. This places the PIM400-485 in the SUS communication mode. A status message will be
displayed (example: PIM Connected on COM1).
96 — revision 6
OEM Device Configuration Guide
Note:
3.
If the SUS is closed and restarted, you must reset the PIM400/401 as indicated in this
procedure to return to the SUS communication mode.
On the HHD, select Couple HHD to Device. When coupling is successful, a message to that effect is
displayed on the HHD screen.
Note:
13.4.16
When the HHD is coupled with the PIM, any previously connected locks will lose
communication with the OnGuard software. The lock will be displayed in Alarm Monitoring
with a yellow “X” with its status as “Gateway online, PIM Offline.”
Put the Wireless Lock in Link Mode
While the PIM is in Link mode (up to 30 minutes), place the lock into Link mode. (The PIM will
automatically exit Link mode once linking is complete.)
1.
Open the lock's back cover.
2.
Open the door.
3.
Push down the lock’s interior door handle, and then present a badge. The LED on the lock will begin
flashing to indicate the linking process.
4.
After the address and link are established, you can continue to configure the other properties using SUS.
13.5
Wiegand Only Integration
A PIM400-TD2 is required for Wiegand communication between the AD-400 wireless lock and the
controller. The Schlage PIM400-TD2 is basically an adapter that connects Schlage wireless readers to
Wiegand interfaces.
revision 6 — 97
Schlage Reader and Lock Solutions
Note:
The Wiegand only integration provides basic lock support. It does not provide the advanced
lock support of the previously described OnGuard integration.
PIM400/401-TD2 Specifications
Model
Maximum
Number of
Locks (Access
Points)
Access Control Panel
Interface
Access Control Panel Connections
PIM400-TD2/
PIM401-TD2
2
Wiegand (data 1/data 0)
Connects up to 2 locks to a controller
as follows:
•
Door 1 connects to the access
control panel through Access
Point 1 connections on J8 and
J10.
•
Door 2 connects to the access
control panel through the Access
Point 2 connections on J7 and
J11.
For connections to the LNL-1300/
1320/2220, refer to the section Wiring
the PIM-TD2 to a Controller on
page 98.
13.5.1
Wiring the PIM-TD2 to a Controller
This section contains information for wiring the PIM-TD2 to a controller (LNL-1300/1320/2220).
•
LNL-1300 Single Reader Interface Connections on page 99
•
LNL-1320 Dual Reader Interface Connections on page 101
•
LNL-2220 Dual Door Controller Connections on page 102
Wiring diagrams are available at the manufacturer’s web site at http://us.allegion.com/services/techsupport/
for the AD-Series Locks. For example: http://us.allegion.com/IRSTDocuments1/105272.pdf
Notes:
Use shielded cables for the signal wiring between the PIM400/401-TD2 and the access control
panel.
Must be used with a UL 294 Listed power supply capable of sourcing at least 250mA @ 12 or
24 VDC.
98 — revision 6
OEM Device Configuration Guide
LNL-1300 Single Reader Interface Connections
From LNL-1300
To PIM400/401-TD2
Description
Connector
Pin
Pin
Connector
Door strike relay
connection
TB3
K1 - C
STRIKE INPUT - 1
J8
K1 - NO
STRIKE INPUT - 2
(GROUND)
Reader connection
TB4
CLK/D1
D1/CLK
DAT/DO
DATA
GND
GND
I1+
DOOR 1 STATUS
I2+
REQ. TO EXIT
Door contact 1K, 1%
Use pin with lowest
voltage.
Door exit request 1K, 1%
Use pin with lowest
voltage.
TB2
J10
revision 6 — 99
Schlage Reader and Lock Solutions
1K
Door A - DOOR STAT
1K
Door A - EXIT REQ
Door A - CLK
Door A - DATA
Door A - GROUND
1K
Door B - DOOR STAT
1K
Door B - CLK
Door B - DATA
Door B - GROUND
Door B - EXIT REQ
Door A - GROUND
Door A - STRIKE
Door B - GROUND
Door B - STRIKE
100 — revision 6
Panel Interface Module (PIM) Connections
Panel Interface Module (PIM) Connections
Wiring the PIM400-TD2/PIM401-TD2 to the LNL-1320
OEM Device Configuration Guide
LNL-1320 Dual Reader Interface Connections
From LNL-1320
To PIM400/401-TD2
Description
Connector
Pin
Pin
Connector
Door A strike relay
connections
TB10
RLY 1 - C
Door A - GROUND
J8
RLY 1 - NO
Door A - STRIKE
READER 1 connections
TB8
CLK/D1
CLK
DAT/DO
DATA
GND
GROUND
IN1 - 1
Door A - DOOR STAT
Door A door contact input
1K, 1%
Use pin with lowest voltage.
TB1
IN1 - 2
IN2 - 1
Door A exit request input
1K, 1%
Use pin with the lowest
voltage.
TB11
READER 2 connections
TB9
Door B exit request input
1K, 1%
Use pin with the lowest
voltage.
Door A - EXIT REQ
IN2 - 2
Door B strike relay
connections
Door B door contact input
1K, 1%
Use pin with lowest voltage.
J10
TB3
RLY 4 - C
Door B - GROUND
RLY 4 - NO
Door B - STRIKE
CLK/D1
CLK
DAT/DO
DATA
GND
GROUND
IN5 - 1
Door B - DOOR STAT
J7
J11
IN5 - 2
IN6 - 1
Door B - EXIT REQ
IN6 - 2
revision 6 — 101
Schlage Reader and Lock Solutions
LNL-2220 Dual Door Controller Connections
From LNL-2220
To PIM400/401-TD2
Description
Connector
Pin
Pin
Connector
Door 1 strike relay
connection
TB10
OUT 1 - C
STRIKE INPUT - 1
J8
OUT 1 NO
STRIKE INPUT - 2
(GROUND)
READER 1 connection
TB8
GND
GND
DAT/DO
DATA
CLK/D1
D1/CLK
IN1 - 1
DOOR 1 STATUS
Door 1 contact 1K, 1%
Use pin with lowest
voltage.
TB4
IN1 - 2
Door 1 exit request 1K, 1%
Use pin with lowest
voltage.
Door 2 strike relay
connection
TB11
READER 2 connection
TB9
Door 2 contact - 1K, 1%
Use pin with lowest
voltage.
TB6
Door 2 exit request 1K, 1%
Use pin with lowest
voltage.
13.5.2
J10
IN2 - 2
REQ. TO EXIT
OUT 4 - C
STRIKE INPUT - 1
OUT 4 NO
STRIKE INPUT - 2
GND
GND
DAT/DO
DATA
CLK/D1
CLK/D1
IN5 - 1
DOOR 2 STATUS
J7
J11
IN5 - 2
IN6 - 1
REQ. TO EXIT
IN6 - 2
OnGuard Configuration
Add the Schlage Lock as a Wiegand Reader in OnGuard
Before adding a Schlage lock, the access control panel (LNL-2220/1320/1300) must already be configured
in System Administration.
From System Administration, complete the following steps:
1.
From the Access Control menu, select Readers and Doors.
2.
On the General tab, click [Add].
3.
Type in a name for the lock being configured.
102 — revision 6
OEM Device Configuration Guide
4.
Choose the Panel to which the PIM is connected.
5.
Click [OK].
Reader Number, Port, Type, and Output
Schlage wireless locks are configured similar to readers in System Administration. When configuring the
lock in OnGuard, a unique reader number will be specified according to the port and address of the PIM. The
first reader must always be present and identified as reader number 0. For more information, refer to the
System Administration User Guide.
6.
Specify the reader Type. With the PIM400/401-TD2, select one of the following reader types:
•
LNL-1300 (Single Interface)
•
LNL-1320 (Dual Interface)
•
LNL-1300e (IP Interface)
•
OnBoard Reader
7.
Specify the reader Output.
8.
If required, specify the Port and Address.
Note:
9.
For IP interface readers, choose the network addressing mode from Port, and then enter the
Mac Address for DHCP or IP Address for Static IP.
Configure the Online Reader Mode.
10. Assign a Card Format.
11. Click [OK].
Some options are not available because they are not features of the Schlage locks. For more information,
refer to the System Administration User Guide.
13.5.3
Strike Time
Strike times cannot be configured from OnGuard; these need to be configured using the Schlage Wireless
Software (SUS) if you want to have values other than the default values. However, the strike time in
OnGuard MUST be configured to match the setting in the SUS. The valid range for the strike time for a
Schlage wireless lock is from 1 - 255 seconds with a default of 3 seconds. For more information, refer to
Configuration Software on page 92.
13.5.4
Alarms and Events in Alarm Monitoring
The “Granted access” event is generated when a valid badge is presented (with an access level recognized by
the lock), the exterior door handle is pushed down, and the door is opened.
The “Door forced open” alarm is generated if no badge is presented when the door’s exterior handle is
pushed down.
revision 6 — 103
Schlage Reader and Lock Solutions
13.5.5
Integrate the Schlage Wireless Access Devices with OnGuard
Use the HHD for the PIM400/401 to integrate the Schlage wireless devices with OnGuard as follows:
1.
Perform a link to reader number 0 on the PIM and test using the diagnostic tool to confirm the link is
established, and the reader, door position switch, and door handles operate properly.
2.
Add the reader (lock) in System Administration, and assign an access level to the lock. For more
information, refer to Reader Number, Port, Type, and Output on page 103.
3.
Program a test card and set up a trace window.
4.
Read the test badge and check the trace for the activity.
13.6
Place the PIM400/401-TD2 into Link Mode
1.
Power up the PIM400/401-TD2.
2.
On the PIM400/401-TD2, press the LINK button(s):
a.
LINK 1 button (SW2): Press 2 - 3 seconds, and then release to link Access Point 1. The
corresponding LED (LED1 for LINK1) flashes red and green. This indicates that the PIM400/401TD2 is in Link Mode. To abort Link Mode, press the same switch again.
b.
LINK 2 button (SW3): Press 2 - 3 seconds, and then release to link to Access Point 2. The
corresponding LED (LED2 for LINK2) flashes red and green.
When the PIM400/401-TD2 is powered, and in Link Mode, the system is ready for the wireless lock to
initiate linking.
3.
While the PIM is in Link Mode (up to 30 minutes), push down on the interior door handle and present
the badge. The LED on the lock will begin blinking rapidly (approximately 20 - 30 seconds).
4.
After the LED stops blinking, release the interior door handle back into the horizontal position.
Access Point Links and Status
The PIM400/401-TD2 overall status is communicated by a red/green LED for each Access Point. A red
LED communicates Real Time and Trouble status:
•
Real Time status: D40 = Access Point 1, D43 = Access Point 2
•
Trouble status: D1 = Access Point 1, D2 = Access Point 2
Each Access Point has clock (CLK) and data (DATA) LEDs that indicate card and keypad data
communication from the PIM400/401-TD2 to the access control panel.
104 — revision 6
OEM Device Configuration Guide
13.7
Connect the HHD to the Lock
1.
Connect the USB cable to the HHD and then plug the HHD USB cable into the lock’s USB port located
in the bottom of the exterior housing.
2.
Press the Schlage button twice. The Schlage button will flash green while the lock is waiting to
communicate with the HHD. The Schlage button will begin to flash red when communication between
the lock and the HHD is established. When communication is established, the device name will be
displayed on the SUS main screen.
13.8
Use the HHD to Couple with the Lock
AD-400 locks can be coupled, or authenticated, using the HHD. This provides enhanced security by
ensuring that the lock will only communicate with HHD to which it has been coupled.
1.
Connect the HHD to the lock using the HH-USB cable.
2.
Press the Schlage button twice. The lock will be displayed on the screen.
3.
On the HHD, select Device Options.
4.
Remove the top inside lock cover.
revision 6 — 105
Schlage Reader and Lock Solutions
5.
Press and hold the Inside Push button. Then press and release the tamper switch three times.
6.
Release the Inside Push button. On the lock, the Inside Push button LED will illuminate.
7.
On the HHD, select Couple HHD to Device. When coupling is successful, a message to that effect will
be displayed on the screen.
106 — revision 6
OEM Device Configuration Guide
14
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.
14.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 6 — 107
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.
14.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:
108 — revision 6
External power should NOT be applied to +5 VDC connection on wedge.
OEM Device Configuration Guide
14.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.
14.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 6 — 109
Cypress Wedge
110 — revision 6
OEM Device Configuration Guide
15
DigiOn24 Encoder
The DigiOn24 (D24) encoder is available as a standalone or inline contactless encoder commonly used in
direct card printers. It can support iCLASS, MIFARE, or DESFire technology.
15.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.
15.1.1
Installing the Standalone Encoder
1.
Obtain the driver either from the Supplemental Materials 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 an available COM port number. Click [OK]. (This COM port number will be used in the
OnGuard configuration of the encoder.)
15.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:
d.
4.
Firmware version 4.92 or later is required for encoding the DESFire TWIC application.
Select the credential technology.
On the Location sub-tab:
revision 6 — 111
DigiOn24 Encoder
5.
6.
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.
On the Communications 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
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.
Once the card format is configured, assign the smart card format application to the badge type. This can be
done in the Badge Types folder, on the Encoding Form.
For more information, refer to the System Administration or ID CredentialCenter User Guides.
15.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 check boxes Map CD to DSR and Map 2 stop bits to 1.
5.
Click [OK].
112 — revision 6
OEM Device Configuration Guide
16
HID CP1000 Encoder
The HID CP1000 iCLASS SE encoder is available as a standalone or inline contactless encoder commonly
used in direct card printers (Fargo DTC4500e). This encoder can be use to encode the Open Encoding
Standard (DESFire) application or the Custom Data Object (DESFire) application to the DESFire EV1
credential.
Encoding with the CP1000 can be performed either inline or standalone.
•
Inline - Encode the Open Encoding Standard (DESFire) application inline with badge printing using the
CP1000 encoder integrated into a Fargo DTC4500e card printer. Install the printer first. After
installation, the printer will then be selectable when configuring an inline encoder in OnGuard. For
more information please refer to Configure the Encoder in OnGuard on page 114.
•
Standalone - Encode the Open Encoding Standard (DESFire) application as a separate step using a
desktop CP1000 encoder. Connect the CP1000 encoder directly to a multimedia capture workstation via
a USB port, and then install the Windows USB drivers. For more details, refer to the manufacturer
documentation.
Supported version: HID CP1000 iCLASS SE Encoder Sam SIO firmware version 1.117. The Main
Firmware Version is 01000021. Configuration of the CP1000 encoder requires Asure ID Card
Personalization Software version 7.6.
16.1
Use Asure ID to Configure the Encoder for Use in OnGuard
When the CP1000 encoder is connected to the workstation, use Asure ID to modify the encoder’s default
Administrative Keys and upload credential credits for card transactions.
Note:
16.1.1
The application keys (PICC master key, Application master key, and File read key) configured
for the Open Encoding Standard (DESFire) smart card format are stored on the CP1000
encoder each time the encoder is used to encode a card. Therefore, although unlikely, you may
receive an error during encoding that there is not enough space on the encoder to store more
keys. In this case, use Asure ID to clear the keys on the encoder.
Modify the Default Administrative Keys
The CP1000 encoder comes from the factory with default Administrative Keys that secure the
communication between the encoder and OnGuard.
revision 6 — 113
HID CP1000 Encoder
During the initial installation of the encoder, you will be prompted in Assure ID to change the encoder
Administrative Keys (Auth Key, Privacy Key, and Secure Channel Key). This action is recommended for
security reasons, and can be performed at this time.
Important:
16.1.2
Make sure to record the keys in a secure location for future reference because this
is the only time you will see them unprotected. Without these keys, you will not
be able to operate the encoder. In addition, you will need them to configure the
encoder in OnGuard. The keys in OnGuard must match the keys set for the
encoder. For more information please refer to Configure the workstation and
encoder: on page 7.
Upload Credential Credits
The CP1000 Encoder uses a credit system for controlling encoding through the device. These credits are
based on the type of credential being encoded (DESFire, iCLASS, etc.), the origin of the credential being
encoded (HID or other), and data type (HID or custom).
Credential credit refers to purchased tokens that enable all card transactions. The CP1000 encoder will
continue encoding until the authorized credential credits are exhausted. When you order additional credits,
upload them to the encoder via Asure ID. For information about ordering credentials, refer to the iCLASS
SE How to Order Guide at www.hidglobal.com.
Note:
When the badge is encoded in OnGuard, the number of remaining encoding operations
(credential credits) is displayed.
16.2
Configure the Encoder in OnGuard
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.
114 — revision 6
OEM Device Configuration Guide
c.
4.
5.
Select "HID SE Encoder (CP1000)" as the Device type and "DESFire" for the Credential
technology. The Supported applications list should display the Open Encoding Standard (DESFire)
and Custom Data Object (DESFire) applications.
On the Location sub-tab:
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 CP1000 encoder is
installed, and/or the encoder station.
On the Communications sub-tab:
a.
Select the relevant USB device from the Encoder drop-down.
b.
Configure the communication keys. Maximum key length is 32 hexadecimal characters. Permitted
characters are 0-9 and A-F. Key entry is not case-sensitive. These keys are secure fields and are
only displayed when you enter the key values. After the keys are stored, they are displayed as
predefined numbers of "*".
Important:
Make sure the communication keys match the administrative keys configured on
the CP1000 encoder in Asure ID. For more information please refer to Modify
the Default Administrative Keys on page 113.
Key in OnGuard
Key on CP1000
Encoder
Description
Authentication key
Auth Key
The 16-byte SNMP signing key used for the encoder.
Privacy key
Privacy Key
The 16-byte SNMP encrypting key used for the
encoder.
revision 6 — 115
HID CP1000 Encoder
Key in OnGuard
Key on CP1000
Encoder
Description
Secure channel key
Secure Channel Key
The channel session key that provides secure
communications between the credential and the
encoder.
6.
c.
(Optional) Click [Restore Defaults] to restore the default communication key values of the CP1000
encoder.
d.
Click [Test Connection] to verify that the connection to the encoder is successful.
e.
Click [OK].
Click [OK].
After this is done, configure a smart card format for encoding either the Open Encoding Standard (DESFire)
application or Custom Data Object (DESFire) application to the DESFire EV1 credential. This can be done
in System Administration or ID CredentialCenter in the Card Formats folder. For this purpose, OnGuard
supplies the ANSI INCITS 378 fingerprint templates or biometric PIN and Badge ID to be encoded into the
credential. Prior to encoding, the cardholder fingerprints are captured using a supported Open Capture
device, such as the SAGEM Morpho MSO 350. This can be done in the Multimedia folder, on the
OpenCapture Form.
Once the card format is configured, assign the smart card format application to the badge type. This can be
done in the Badge Types folder, on the Encoding Form. The Mapping Table feature is used to import the
Badge ID.
For more information, refer to the System Administration or ID CredentialCenter User Guides.
116 — revision 6
OEM Device Configuration Guide
17
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 the
OnGuard software. The ActivEntry Manager provides centralized control of assurance level settings and
distribution of validation data.
17.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
Wiegand 1 or
2 Pin/Label
LNL-1300
(TB4)
LNL-1320
(TB8 or
TB9)
LNL-2220
(TB8 or
TB9)
LNL-1300-U
(J10 & J13)
LNL-1320-U
(J10 & J13 or J15 &
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 6 — 117
ActivIdentity ActivEntry
Wiring the ActivEntry Module and Security (NGP) Series Hardware
ActivEntry Wiegand
1 or 2 Pin/Label
NGP-1320
(TB2 or TB11)
NGP-2220
(CN10 & CN11 or CN17 &
CN18)
NGP-3320
(CN10 & CN11 or CN17 &
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.
17.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.
17.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.
118 — revision 6
OEM Device Configuration Guide
17.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.
17.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
supported using a PC/SC reader.)
For the badge ID, set FASC-N to AC + SC + CN. For the issue
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
supported using a PC/SC reader.)
For the badge ID, set FASC-N to AC + SC + CN + CS. For the
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 6 — 119
ActivIdentity ActivEntry
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).
17.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.
4.
Click [OK] to save the change.
17.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.
4.
Click [OK] to save the change.
17.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.
4.
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.
Click [OK] to save the changes.
17.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.
17.5.1
1.
Configure a Cardholder with an Invalid Badge
Add a cardholder in the OnGuard software. It may be helpful to enter “Invalid Card” for the name.
120 — revision 6
OEM Device Configuration Guide
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.
17.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.
5.
Click [OK] to save the changes.
17.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 6 — 121
ActivIdentity ActivEntry
17.8
Enrollment
The badge must be enrolled in both the ActivEntry software and in the OnGuard software. The following
sections describe how to configure and enroll badges into the OnGuard software. 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 a 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.
17.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:
3.
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.
Click [OK] to save the changes.
17.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].
5.
•
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.
Place the badge in the reader.
122 — revision 6
OEM Device Configuration Guide
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:
9.
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.
Assign the appropriate access levels. Click [OK].
When the enrollment has been completed, verify that the cardholder information has been imported
correctly.
17.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 Materials disc. 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 pcProxConfig documentation (also included on the Supplemental Materials disc), configure
the ID of the reader’s outputs by modifying the fields on the CHUID tab.
Note:
5.
Confirm that all fields are listed together without any return or separator characters.
Confirm that the updated settings are written to the reader.
revision 6 — 123
ActivIdentity ActivEntry
124 — revision 6
OEM Device Configuration Guide
18
Fingerprint Enrollment and Verification
Fingerprinting can be made easier with a simple fingerprint scanning device.
18.1
Cross Match
OnGuard supports a number of Cross Match devices.
18.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.
•
6.
In Windows, open the Programs and Features application and go to “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.
For more information, refer to “Using OnGuard in the Supported Operating Systems” in the
Installation Guide.
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.
revision 6 — 125
Fingerprint Enrollment and Verification
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.
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.
18.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
1.
When enrolling a cardholder, click [Capture].
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:
3.
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.
The image is displayed and the fingerprint minutiae is generated.
126 — revision 6
OEM Device Configuration Guide
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].
18.2
Sagem Morpho
The MORPHOSMART MSO 300 series fingerprint scanners are capable of capturing a high-resolution (500
dpi) fingerprint image and allow viewing of low-resolution bitmap images. You can also use these scanners
for verification.
OnGuard supports the following models: MSO 300, MSO 350, MSO 350 PIV, MSO 1300, and MSO 1350.
18.2.1
Installation of the MSO Scanner
Install the device driver. The driver is provided on the Supplemental Material 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:
18.2.2
For more information, refer to the manufacturer documentation.
OnGuard Enrollment
1.
When enrolling a cardholder, click [Capture].
2.
On the OpenCapture tab, select your Device, and then check that the device status indicates it is
connected. If this is not indicated, check your connection.
3.
If there are any fingers that are NOT being enrolled, select the Missing checkbox for that finger.
4.
Click [Capture]. Follow the instructions on the screen. It will guide you through the process of
capturing fingerprints.
5.
Click [Finish] when you are done.
revision 6 — 127
Fingerprint Enrollment and Verification
128 — revision 6
OEM Device Configuration Guide
19
GemPlus EasyAccess 332 Encoder
This unit is a contactless reader, uses an RS-232 connection, and is compatible with ISO14443 A and Mifare
cards.
19.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 6 — 129
GemPlus EasyAccess 332 Encoder
19.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
130 — revision 6
OEM Device Configuration Guide
20
iCLASS Encoders
20.1
iCLASS RKL55 Programmer
The HID iCLASS RKL55 programmer supports the following smart card applications:
•
HID Access Control (iCLASS)
•
IrisAccess (iCLASS)
•
Lenel (iCLASS)
•
V-Smart (iCLASS)
•
GSC (iCLASS)
•
Handkey (iCLASS)
•
Badge ID Import
•
Credential Agent
To use the programmer, 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 device (RKL55/6171BKT000000PRGL) operates at 9-12 VDC. The average current draw is 160-250
mA.
revision 6 — 131
iCLASS Encoders
20.1.1
Programmer Wiring
Connect the programmer to the serial port on the host computer. Due to timing issues with the programmer,
this unit cannot be connected to a multi-port serial adapter.
Terminal
Description
DB9 pin-out
P1-1
Beeper Input
Not used
P1-2
Green (GRN) LED input
Not used
P1-3
Ground (RTN)
DC Ground
P1-4
+VDC
+DC (9-12 VDC)
P1-5
Shield ground
Pin 5
P1-6
Red LED Input
Not used
P1-7
Hold Input
Not used
P2-7
GPIO1 (RS232-T/RS485-A/HADP-OSDP-A/
USB-5V/UART-T)
Pin 2
P2-6
GPIO2 (RS232-R/RS485-B/HADP-OSDP-B/
USB-D+/UART-R)
Pin 3
P2-5
Open Collector Output
Not Used
P2-4
Wiegand Data 1/Clock
Not Used
P2-3
Wiegand Data 0/Data
Not Used
P2-2
GPIO3 (RS485-Z/USB-D-)
Not used
P2-1
GPIO4 (RS485-Y)
Not Used
Note:
For more detailed information, refer to the manufacturer documentation.
20.1.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:
5.
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.
On the Location sub-tab, select the radio button indicating This is a standalone device attached to
this workstation.
132 — revision 6
OEM Device Configuration Guide
6.
7.
On the Communications 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
Click [OK].
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.
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].
Smart Card Format
To configure the Smart Card format in System Administration:
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 6 — 133
iCLASS Encoders
Smart Card format configuration
Encoding Form
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 the Iris badge type, assign two card formats, encode the credential twice — first with HID Access
Control (iCLASS), then with IrisAccess (iCLASS).
For more information, refer to the System Administration or ID CredentialCenter User Guides.
20.2
iCLASS RW400Prgm Programmer
The HID iCLASS RW400Prgm encoder supports the following smart card applications:
•
Credential Agent
•
GSC (iCLASS)
•
HID Access Control (iCLASS)
•
IrisAccess (iCLASS)
•
Bioscrypt (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.
20.2.1
Encoder Wiring
Due to timing issues with the encoder, this unit cannot be connected to a multi-port serial adapter.
134 — revision 6
OEM Device Configuration Guide
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
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
20.2.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.
revision 6 — 135
iCLASS Encoders
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 Communications sub-tab, select the comm. port to which the unit is connected and enter the
following communication settings:
7.
•
Baud rate: 57600
•
Data bits: 8 bit
•
Parity: Even
•
Stop bits: 2
Click [OK].
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.
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].
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].
136 — revision 6
OEM Device Configuration Guide
Smart Card format configuration
Encoding Form
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.
revision 6 — 137
iCLASS Encoders
138 — revision 6
OEM Device Configuration Guide
21
Integrated Engineering
OnGuard supports the Integrated Engineering (IE) SmartID, SmartPro, and SmartLOGON™.
21.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.
21.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 6 — 139
Integrated Engineering
140 — revision 6
OEM Device Configuration Guide
22
OMNIKEY 5125 Prox/Contact and 5325 Prox USB
Readers
The OMNIKEY 5125/5325 USB PC/SC smart card proximity readers are used for automatic visitor sign in/
sign out. They automatically add Wiegand data to badging workstations.
The OMNIKEY 5125/5325 support HID proximity 125 kHz technology. The 5125 also reads and writes to
any contact-based smart card.
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
22.1
Installation
The OMNIKEY 5125/5325 readers use 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:
https://partner.lenel.com/downloads/onguard/compatibility-charts. (You will need your Lenel login to gain
access to this site.)
Note:
22.2
When accessing the Downloads section at https://partner.lenel.com, make sure to select the
version of OnGuard that is currently installed.
Configuration of the 5125/5325 Readers
The OMNIKEY 5125/5325 units send transaction results through the USB port. The device driver is used to
configure the connection of this device. There is no setup required.
revision 6 — 141
OMNIKEY 5125 Prox/Contact and 5325 Prox USB Readers
The 5125/5325 readers use 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.
142 — revision 6
OEM Device Configuration Guide
23
ScanShell and SnapShell Scanners
The information on a driver's license, driver's license barcode, business card, or other card IDs can be
imported using ScanShell and SnapShell scanners in System Administration and Front Desk.
Depending on which OnGuard application you are using, ScanShell and SnapShell device support and
functionality varies.
Refer to the Lenel Web site to review the current device support. The Third Party Capture Devices
Compatibility Chart can be accessed at:
https://partner.lenel.com/downloads/onguard/compatibility-charts. (You will need your Lenel login to gain
access to this site.)
Note:
23.1
When accessing the Downloads section at https://partner.lenel.com, make sure to select the
version of OnGuard that is currently installed.
CSSN ScanShell and SnapShell Installation
For System Administration: The installation of OnGuard automatically installs the ScanShell/SnapShell
SDK.
For Front Desk: Complete the following steps to install the CSSN SDK:
1.
Close all OnGuard applications. (OnGuard services do not need to be stopped.)
2.
Run the Card Scanning Solutions setup file located on the Supplemental Materials disc in the
Credential Center Device Drivers > Card Scanning Solutions folder.
During the installation process, use the default settings except for the SDK components. In this case,
ensure the following components are selected at a minimum:
•
Driver License, ID & Passports
•
Business Card
Refer to the Card Scanning Solutions web site for more detailed SDK installation instructions.
3.
Connect the ScanShell or SnapShell scanner to the workstation using the supplied USB cable.
4.
Start OnGuard applications.
Important:
Do NOT use the manufacturer disc to install the drivers.
If required, the scanners should be properly calibrated. Refer to the manufacturer documentation. In order to
calibrate the scanners, the domain user should be made a member of the Administrators group.
revision 6 — 143
ScanShell and SnapShell Scanners
23.2
OnGuard Configuration
By default, FormsDesigner should have the proper DMV or passport 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 the ScanShell and SnapShell devices
enabled. The ability to use ScanShell and SnapShell devices 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].
3.
a.
Enter the name of the unit (this is user-configurable).
b.
Select the workstation on which the ScanShell or SnapShell is installed.
c.
For the device type, choose CSS Scanner.
d.
The location and communication tabs are automatically configured.
Click [OK].
23.2.1
Import Data Using the ScanShell or SnapShell
You can import data using the ScanShell or SnapShell scanner 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.
3.
a.
Select the primary segment and any additional segments that this badge type will be assigned to.
b.
Click [OK].
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.
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.
144 — revision 6
OEM Device Configuration Guide
24
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-TS261USB/Z-TS261-HSB) and serial kit (Z-TS261-B).
24.1
SignatureGem Installation
The Topaz SignatureGem pen tablet can be installed on any multimedia capture workstation running
Windows 7, Windows 8, or Windows 8.1. It is also compatible with Citrix.
Note:
24.1.1
Do NOT connect the signature tablet to the serial or USB port until prompted to do so.
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.20 Setup program window displays.
Click [Next].
revision 6 — 145
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.
24.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 Add New Hardware wizard should automatically start. If it does not, manually start the wizard.
For more information, refer to “Using OnGuard in the Supported Operating Systems” in the Installation
Guide.
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.
24.1.3
1.
Install the Topaz software
When the PC reboots, the Found New Hardware Wizard automatically displays. Select the Install the
software automatically (Recommended) radio button and click [Next].
146 — revision 6
OEM Device Configuration Guide
Note:
If the Add New Hardware wizard does not automatically start you can manually start it. For
more information, refer to “Using OnGuard in the Supported Operating Systems” in the
Installation Guide.
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 7, Windows 8, or
Windows 8.1 operating system.
3.
Click [Finish] when the wizard has finished installing the software.
revision 6 — 147
Topaz SignatureGem Pen Tablet
148 — revision 6
HID PIVCLASS
OEM Device Configuration Guide
25
pivCLASS Authentication Module (PAM)
A pivCLASS Authentication Module (PAM) is required for communication between a pivCLASS reader
and panel or door controller in order to authenticate FIPS 201 credentials at the door.
Install the PAM between a standard single/dual access control panel and pivCLASS contact, contactless, and
biometric readers used in U.S. Federal Government buildings that require the use of use smart card
technology. Each PAM can process up to two pivCLASS readers at one or two doors. The pivCLASS
readers pass the card information to the PAM which performs the required authentication to validate (or
invalidate) the cardholder's credentials. If validated, the PAM derives and sends the badge ID/extended ID to
the controller as Wiegand output for the access authorization decision.
Note:
Make sure the pivCLASS reader is configured to operate in the PAM reader mode. In this
mode the reader uses RS-485 communication protocol to communicate with the PAM.
The PAM...
•
Validates PKI-based smart cards. The PAM authenticates PIV, PIV-I, CIV (PIV-C), TWIC, and CAC
credentials, and performs path validation and certificate revocation checking using CRL, OCSP or
SCVP.
•
Supports multiple authentication modes including FASC-N, CHUID, CAK, PIV + PIN, CHUID + BIO,
CAK + BIO, and PIV + PIN + BIO.
•
Communicates via Ethernet TCP/IP with the pivCLASS Validation Server (PVS) which, in turn,
communicates with external trust authorities, imports updated credential information, and sends that
information to the PAMs for enforcement. Since the PAM receives and caches the credentials and
cardholder status, the result is next to real-time, PKI-based, high level security at the door. With the
validation data cached on the PAM, the PAM can function offline if required.
•
Enables your facility to perform single-, two- and three-factor authentication to meet all recommended
authentication modes and assurance levels specified in NIST SP 800-116 and the TWIC Reader
Specification. For more information, refer to “NIST Recommendations for Using PIV Credentials in
PACS” in the System Administration User Guide.
revision 6 — 151
pivCLASS Authentication Module (PAM)
25.1
Install the pivCLASS Authentication Module
The PAM is installed between the door controller/reader interface module and the access reader. The
following modules are supported:
•
LNL-1300
•
LNL-1320
•
LNL-2220
•
NGP-1300-U
•
NGP-1320-U
25.2
Wiring
25.2.1
Downstream Reader Communication
The pivCLASS Authentication Module (PAM) communicates with up to two (2) pivCLASS card readers via
RS-485.
Notes:
PAM-connected readers must be specified as “authenticated readers” in the OnGuard software.
An authenticated reader’s name must be the same as the name described in the pivCLASS
Validation Service software. For more information, refer to “Configure Authenticated Readers
and Authentication Modes” in the NIST SP800-116 Support appendix of the System
Administration User Guide.
Since the PAM is not intended to connect to standard Wiegand type readers, the normal reader signals are
not shown in the following wiring table.
From PAM to Downstream Reader
PAM Terminal
(Reader 1 or 2)
HID Pigtail
Color Code
HID pivCLASS
Reader Terminal
Signal Name
TR+
Red/Green
GPIO1
RS485-A
TR-
Tan
GPIO2
RS485-B
R+
Gray
GPIO3
RS485-Y
R-
Pink
GPIO3
RS485-Z
GND
Black
RTN
Ground
VO
Red
+12 VDC
+12 VDC
152 — revision 6
OEM Device Configuration Guide
25.2.2
Wiring the PAM and Access (LNL) Series Hardware
From LNL-1300
To PAM (Wiegand Port)
Reader Terminals
Pin
Description
TB4
1 (GND)
GND
2 (BZR)
BZR
3 (LED)
LED
4 (CLK/D1)
D1
5 (DAT/D0)
D0
6 (VO)
Not Used
From LNL-1320
To PAM (Wiegand Port)
Reader Terminals
Pin
Description
TB8 or TB9
1 (GND)
GND
2 (DAT/D0)
D0
3 (CLK/D1)
D1
4 (BZR)
BZR
5 (LED)
LED
6 (VO)
Not Used
From LNL-2220
To PAM (Wiegand Port)
Reader Terminals
Pin
Description
TB8 or TB9
1 (GND)
GND
2 (DAT/D0)
D0
3 (CLK/D1)
D1
4 (BZR)
BZR
5 (LED)
LED
6 (VO)
Not Used
revision 6 — 153
pivCLASS Authentication Module (PAM)
25.2.3
Wiring the PAM and Security (NGP) Series Hardware
From NGP-1300-U
To PAM (Wiegand Port)
Reader Terminals
Pin
Description
J10 (Reader 1)
J11 (Reader 2)
1 (CLK D1)
D1
2 (DAT D0)
D0
3 (GND)
GND
1 (VO)
Not Used
2 (BZR)
BZR
3 (LED2)
LED
J13
From NGP-1320-U
To PAM (Wiegand Port)
Reader Terminals
Pin
Description
J10 (Reader 1)
J11 (Reader 2)
J15 (Reader 3)
J16 (Reader 4)
1 (CLK D1)
D1
2 (DAT D0)
D0
3 (GND)
GND
J13 (Reader 1 and 2)
J18 (Reader 3 and 4)
1 (VO)
Not Used
2 (BZR)
BZR
3 (LED2)
LED
25.3
Configure PACS Reader Services
25.3.1
PACS State Machine Setting
The PACS state machine settings must be configured in order for the PAM to receive the LED and buzzer
signals from the reader interface.
Enter the state machine string for your particular panel into the PACS state machine text field. For more
information please refer to “Understanding the 'State Machine' Fields” in the manufacturer’s PACS Service
Manual.
1.
Log onto the PIVCheck PACS Plug-in. The PACS Service Administration window is displayed.
2.
From the Tools menu, select PACS Service Configuration.The Server Configuration window is
displayed.
3.
On the Reader Services tab:
154 — revision 6
OEM Device Configuration Guide
a.
Select the PAM sub-tab, and then select Panels node in the Services tree.
b.
For panels/controllers with readers/reader interfaces, type the following string in the PACS state
machine field:
1,2G,2D,1000:2,2,F,350
Important:
4.
If you have altered the standard LED and Buzzer outputs via an entry in the
acs.ini file, this PACS state machine value may not result in expected LED and
Buzzer behavior for Lenel or NGP panels. For more information, refer to the
PACS Service Manual.
Click [OK] to save the setting.
25.3.2
Associate OnGuard Readers with PAM-Connected Readers
In order to associate a reader in OnGuard with a PAM-connected reader, ensure the following steps are
completed in System Administration:
•
The authentication modes are downloaded.
•
The corresponding reader is specified as an Authenticated reader. For more information, refer to
“Configure Authenticated Readers and Authentication Modes” in the System Administration User
Guide.
•
The reader name matches the PAM and reader descriptions entered in the pivCLASS Management
Station and is entered using the following format:
[PAM Description].[Reader Description]
revision 6 — 155
pivCLASS Authentication Module (PAM)
For example: If the PAM description is “Vault PAM” and the reader description is “Vault Bio Reader,”
then the OnGuard reader name should be “Vault PAM.Vault Bio Reader.” (In the following example, the
OnGuard reader name should be “MyPAM.pivCLASS CAK Reader.”)
pivCLASS Management Station
Important:
156 — revision 6
If the reader names do not match the PAM and reader descriptions, then
authentication mode changes made to readers in OnGuard will not be updated in
the pivCLASS PACS Service software.
IP SUPPORT
OEM Device Configuration Guide
26
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)
26.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 6 — 159
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).
6.
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.
You will be prompted for a user name. Enter any name.
26.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.
160 — revision 6
OEM Device Configuration Guide
26.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 6 — 161
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.
26.4
Device Configuration
For wiring between the hardware and the Lantronix box, a straight through RS-232 cable is used. Also, a 25pin/9-pin adapter may be required for certain hardware. The Lantronix box is equipped with a 25 pin male
connector.
Device
access
parity
stop
bits
byte
size
flow
control
baud rate
AES IntelliNet (Bosch 6500
output mode)1
remote
odd
2
7
CTS/RTS
1200
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
162 — revision 6
OEM Device Configuration Guide
Device
access
parity
stop
bits
byte
size
flow
control
baud rate
Galaxy 8, 18, 60, 128, 500,
504, or 512
remote
none
1
8
none
1200/2400/4800/9600/
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 6 — 163
Security Settings (SDS1100)
27
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.
27.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
164 — revision 6
OEM Device Configuration Guide
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,
19200, 38400, 57600, 115200
78
00
(Personal safety) Visonic SpiderAlert
9600
4C
02
(Receiver) Bosch 6500
1200, 2400, 4800, 9600,
19200, 38400
4C
00
(Receiver) Bosch SIA
1200, 2400, 4800, 9600,
19200, 38400
4C
00
(Intrusion) Bosch D7412G / D9412G
9600
4C
00
(Intrusion) Bosch DS7400Xi /
DS7400XIV4
2400, 9600
5C
02
(Intrusion) Galaxy 8, 18, 60, 128, 500,
504 and 512
1200, 2400, 4800, 9600,
19200, 38400
4C
00
9600
4C
02
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
revision 6 — 165
IP Cameras
28
IP Cameras
IP cameras supported by Lenel Digital Video can be found on the Lenel website (You will need your Lenel
login to gain access to this site): https://partner.lenel.com/downloads/lnvr/software. Select Compatibility.
Note:
When accessing the Downloads section at https://partner.lenel.com, make sure to select the
version of Lenel NVR that is currently installed.
Be sure to check here for the latest updates.
166 — revision 6
OEM Device Configuration Guide
Index
A
ActivEntry
access readers............................................. 118
authentication methods .............................. 118
badge id...................................................... 119
badge id derivation rules............................ 119
card format................................................. 121
enrollment .................................................. 122
invalid credentials...................................... 120
module ....................................................... 117
ActivIdentity ..................................................... 117
AES intellinet receiver...................................... 162
Aperio first card unlock ...................................... 79
B
Biotouch............................................................ 125
Bosch D6600/D6500......................................... 162
Bosch D7412/D9412......................................... 162
Bosch receiver..................................................... 45
C
CardScan ............................................................. 67
Corex................................................................... 67
Cross match....................................................... 125
Cypress....................................................... 71, 107
Cypress timer ...................................................... 55
D
D6500.................................................................. 45
D6600.................................................................. 45
Destination dispatch............................................ 11
DigiOn24 .......................................................... 111
downstream reader communication .................. 152
DS7400Xi ......................................................... 162
E
EasyAccess ....................................................... 129
EdgePlus ............................................................. 23
EdgeReader ......................................................... 23
Elevator dispatch................................................. 11
Enrollment ........................................................ 122
ESPA (Tateco) .................................................. 162
ESPA protocol .................................................... 20
ETHLAN (MSS1/MSS100 ethernet controller) 159
F
Fingerprint
biotouch ..................................................... 125
cross match ................................................ 125
enrollment .................................................. 125
sagem morpho............................................ 127
Fire panels........................................................... 13
First card unlock ................................................. 79
G
Galaxy panel ..................................................... 163
GemPlus............................................................ 129
H
HID CP1000 encoder........................................ 113
HID EdgeReader................................................. 23
HID pivCLASS Authentication Module........... 152
overview .................................................... 151
wiring......................................................... 152
I
iCAM .................................................................. 25
Install
CSSN ScanShell and SnapShell ................ 143
Topaz software .......................................... 146
Integrated Engineering...................................... 139
Interior Push Button Mode (IPB)........................ 89
Intrusion detection panel DS7400Xi................. 162
Invalid credentials............................................. 120
Iris recognition.................................................... 25
IrisAccess............................................................ 25
M
MOM-4 ............................................................... 13
Multi-dropped PIMs ........................................... 86
N
Notifier
AM2020....................................................... 16
ID3000 ......................................................... 17
NFS-640....................................................... 17
panel connection .......................................... 16
programming ............................................... 19
Notifier panel .................................................... 163
O
OEM devices......................................................... 9
OEM devices supported over IP ....................... 157
OMNIKEY 5125 Prox/Contact and 5325 Prox USB
Readers ...................................................... 141
Onity programmer............................................... 41
revision 6 — 167
Index
Osborne-Hoffman oh-2000 receiver ................. 163
Override reader mode .................................. 81, 91
P
Parsing information............................................. 21
Personal safety .................................................... 43
PIM400-1501 ...................................................... 86
Point of sales ....................................................... 63
Put lock in link mode remotely........................... 91
Pyrotronics ................................................. 13, 163
Pyrotronics Fire Panel......................................... 13
R
Receivers............................................................. 45
S
Sagem morpho .................................................. 127
ScanShell and SnapShell .................................. 143
Schlage Interior Push Button (IPB) .................... 89
Schlage locks
assign interior push button mode................. 91
deadbolt detection........................................ 87
Interior Push Button (IPB)........................... 89
mechanical key override .............................. 87
multi-dropped PIMs..................................... 86
PIM-485 and PIM-Wired-485 system
capabilities............................................ 85
remote linking from Alarm Monitoring....... 91
Wake-Up On Radio (WOR) ........................ 86
Schlage PIM-485 and Wired-485
OnGuard configuration................................ 88
Security settings ................................................ 164
SignatureGem pen tablet
installation checklist .................................. 145
SmartID readers ................................................ 139
T
Tateco
connection.................................................... 20
data converter power.................................... 20
fire panel ...................................................... 20
test mode...................................................... 21
Topaz signaturegem .......................................... 145
TVC-2100 ........................................................... 63
TVS ..................................................................... 63
V
Video text inserter............................................... 63
Visonic .............................................................. 163
Visonic SpiderAlert ............................................ 43
168 — revision 6
W
Wake-Up On Radio (WOR) ............................... 86
Wedge reader ............................................. 71, 107
Wiegand integration, only................................... 97
Wiring PIM to controller .................................... 98
OEM Device Configuration Guide
revision 6 — 169
UTC Fire & Security Americas Corporation, Inc.
1212 Pittsford-Victor Road
Pittsford, New York 14534 USA
Tel 866.788.5095 Fax 585.248.9185
www.lenel.com
docfeedback@lenel.com
Download PDF
Similar pages
CVX-OPTS
Schlage Bright Blue Users Guide
User Manual Version: 5.03
slotbadgeds
www.electrolux.com Control Panel Door Door Safety Switch Button
ES System - Lenel.com
Features:
Features: