Beruflich Dokumente
Kultur Dokumente
Notice
This document contains Honeywell proprietary information. Information
contained herein is to be used solely for the purpose submitted, and no part of this
document or its contents shall be reproduced, published, or disclosed to a third
party without the express permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate,
Honeywell disclaims the implied warranties of merchantability and fitness for a
purpose and makes no express warranties except as may be stated in its written
agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential
damages. The information and specifications in this document are subject to
change without notice.
Copyright 2009 – Honeywell International Sàrl
Honeywell trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant® and TDC 3000® are U.S.
registered trademarks of Honeywell International Inc.
Honeywell Enterprise Buildings Integrator™ is a trademark of Honeywell
International Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the
trademark owner, with no intention of trademark infringement.
2 www.honeywell.com
Contents
3
CONTENTS
4 www.honeywell.com
CONTENTS
5
CONTENTS
6 www.honeywell.com
Getting started with an AXSS-II
controller 1
This guide describes how to:
• Set up and configure AXSS-II controllers.
• Configure access control and security.
• Configure optional access control features, such as Integrated PhotoID.
7
1 – GETTING STARTED WITH AN AXSS-II CONTROLLER
Tips
• Make a photocopy of each checklist before you start.
• Check that you have satisfied the Prerequisites before you start any task.
• Complete the tasks in order shown, unless specified otherwise.
• When you complete each task, return to the checklist and insert a tick in the
Done column.
8 www.honeywell.com
SPEEDING UP YOUR WORK WITH CHECKLISTS
9
1 – GETTING STARTED WITH AN AXSS-II CONTROLLER
10 www.honeywell.com
RELATED EBI DOCUMENTS
11
1 – GETTING STARTED WITH AN AXSS-II CONTROLLER
12 www.honeywell.com
Setting up an AXSS-II controller
2
This section describes how to set up and configure an AXSS-II controller so that
it can communicate with the server.
Attention Use the “AXSS-II setup and configuration checklist” on page 14 to guide
you through the tasks, and to avoid configuration problems.
13
2 – SETTING UP AN AXSS-II CONTROLLER
Tasks
Complete the tasks in the following order.
14 www.honeywell.com
AXSS-II CONTROLLER-TO-SERVER CONNECTION GUIDELINES
For: Go to:
Connecting to the server page 16
Communication settings page 20
15
2 – SETTING UP AN AXSS-II CONTROLLER
Multi-dropping
Up to 8 AXSS-II main controllers can be multi-dropped on one RS-485 bus. The
RS-485 connection port is provided on each main controller. To connect to the
Honeywell server computer COM port, an RS232-RS485 converter is required.
Multi-dropping requires each AXSS-II controller on the same channel to have a
unique controller ID. The ID for AXSS-II controller is set from the DIP switches
on the main controller board.
The server performs serial communications using either on-board serial ports
(COM1, COM2, and so on) or by using a serial interface board such as DigiBoard
or RocketPort.
Every AXSS-II controller in the system is assigned an ID, a value between 1 and
8, which is used to address the AXSS-II. The ID of each AXSS-II on a single
channel must be unique.
16 www.honeywell.com
AXSS-II DATA TYPES
Access points
Access information about AXSS-II access readers is stored in an server access
point. Each point corresponds to a single AXSS-II access reader.
Status points
Status points are used to store inputs with discrete values such as ON, OFF,
OPEN, and FORCED.
The following table show status point address types.
17
2 – SETTING UP AN AXSS-II CONTROLLER
18 www.honeywell.com
CONNECTING AND CONFIGURING AN AXSS-II CONTROLLER
To configure a controller:
1 Connect the cables.
2 Set the address on the main controller board using the DIP switches.
3 Use Quick Builder to define channels, controllers, and points and download
definitions to the Honeywell server.
4 Follow the AXSS-II Installation Manual and the AXSS-II User Guide.
5 Use an emulator application to connect to the main controller and use the
Serial Configuration Utility to configure the AXSS-II.
19
2 – SETTING UP AN AXSS-II CONTROLLER
Setting Value
Baud rate 9600bps
Data bits 8
Parity None
Flow control None
20 www.honeywell.com
Defining a channel, controller
and points for an AXSS-II
controller
3
This section describes how to configure AXSS-II channels, controllers and to
build points using Quick Builder.
For: Go to:
Defining an AXSS-II channel page 22
Defining an AXSS-II controller page 27
Defining an address for a point parameter value page 30
Optimizing scanning performance page 38
Troubleshooting AXSS-II scanning errors page 41
21
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
Related topics
“AXSS-II channel Main tab properties” on page 23
“AXSS-II channel Port tab properties” on page 25
22 www.honeywell.com
DEFINING AN AXSS-II CHANNEL
Property Description
Name The unique name of the channel. A maximum of 10
alphanumeric characters (no spaces or double quotes).
Description A description of the channel. 30 characters maximum,
including spaces.
Marginal Alarm Limit The communications alarm marginal limit at which the
channel is declared to be marginal. When this limit is
reached, a high priority alarm is generated. A channel
barometer monitors the total number of requests and the
number of times the controller did not respond or
response was incorrect. The barometer increments by 2
or more, depending on the error and decrements for each
good call.
To calculate an acceptable limit, multiply the square root
of the number of controllers on the channel by the
Marginal Alarm Limit defined for those controllers.
(Normally, you specify the same value for all controllers
on a channel). For example, if there are 9 controllers on
the channel and their Marginal Alarm Limit is set to
25, the value would be [ 3 is square root ] x 25= 75.
Fail Alarm Limit The communications alarm fail limit at which the
channel is declared to have failed. When this barometer
limit is reached, an urgent alarm is generated.
Set this to double the value specified for the channel
Marginal Alarm Limit.
Response Time Enter the maximum amount of time, in seconds, that the
server will wait, after issuing a control, for a response
from the controller if you do not want the default, 10. If
there is no response within the specified time, the server
raises an alarm. For example, an OP Fail alarm would be
raised on a point when an OP is being controlled and
there is no response within the specified time.
For Dialup channels the suggested value for Response
Time is 60 seconds.
Exception Scan Rate If exception scanning has been configured, enter the
amount of time, in seconds, the server will automatically
scan the device if you do not want the default, 2.
23
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
Property Description
Diagnostic Scan Rate Enter the amount of time, in seconds, the server will
automatically initiate a scan of the controller to verify
communications integrity with the controller if you do
not want the default, 60.
One hardware diagnostic scan is automatically created
per scan packet.
Connect Timeout The time (in seconds) the server waits to connect to the
controller before abandoning the connection. The
default value is 10 seconds.
Use the default value unless the communications line
has a high error rate or unless you are using modems.
Read Timeout The time (in seconds) that the server waits for a reply
from the controller. The default value is 2 seconds.
Use the default value unless the communications line
has a high error rate or unless you are using modems.
Item Type Shows the type channel type.
Last Modified Shows the date of the most recent modification to this
channel’s property details.
Last Downloaded This shows the date that the item was last downloaded to
the server.
Item Number The unique item number currently assigned to this item.
You can change the item number if you need to match
your current server database configuration. The number
must be between 1 and the maximum number of
channels allowed for your system.
24 www.honeywell.com
DEFINING AN AXSS-II CHANNEL
Property Description
Serial Port Name The device name of the serial port.
Baud Rate The number of data bits per second. Always set to 9600
for AXSS-II.
Number of Data Bits The number of data bits used for transmission. Always
set to 8 for AXSS-II.
Stop Bits The number of stop bits used for transmission. Always
set to 1 for AXSS-II.
Parity The parity verification used on the port. Always set to
NONE for AXSS-II.
Checksum The type of checksum error detection used for the port.
Always set to None for AXSS-II.
Property Description
Terminal Server TCP Host The name and port number of terminal server to which
Name the channel is connected.
Terminal Server TCP Port No You can specify either a TCP host name or an IP
address, but it must match the TCP host name used when
you installed and internally configured the terminal
server.
25
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
Property Description
Idle Timeout The time, in seconds, the channel waits for a successful
connection to the server before closing the connection.
A value of 0 indicates that the connection is never
closed.
Checksum Always set to None for AXSS-II.
Property Description
Port Name The name of the TCP port used as defined in the \
%windir%\system32\drivers\etc\services file.
This is a text file and can be edited to add new Port
Names to match the controllers programmed port
number.
Note: All controllers on the same channel must be
configured to use the same port number.
26 www.honeywell.com
DEFINING AN AXSS-II CONTROLLER
Related topics
“AXSS-II controller Main tab properties” on page 28
27
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
Property Description
Name The unique name of the controller. A maximum of 10
alphanumeric characters (no spaces or double quotes).
For LAN connected controllers, the name must not
contain underscore ( _ ) characters. This name is used to
look up the IP address in the TCP/IP database if you do
not specify an IP Address property.
Description A description for this controller. A maximum of 30
characters, including spaces.
Channel Name The name of the channel on which the controller
communicates. You need to have already defined the
channel in order for its name to appear in the list.
Marginal Alarm Limit The communications alarm marginal limit at which the
controller is declared to be marginal. When this value is
reached, a high priority alarm is generated. This limit
applies to the controller barometer which monitors the
total number of requests to the controller and the number
of times the controller did not respond or response was
incorrect. The barometer increments by 2 or more,
depending on the error and decrements for each good
call. The default value is 25.
Fail Alarm Limit The communications alarm fail limit at which the
controller is declared to have failed. When this value is
reached, an urgent alarm is generated.
Set this to double the value specified for the controller
Marginal Alarm Limit.
Controller ID Enter the device ID as configured by DIP switches on
the AXSS-II main controller. To communicate with the
AXSS-II, the server needs this ID. The controller
address on the channel must match the AXSS-II ID set
the main controller.
Item Type Shows the controller’s type.
Last Modified Shows the date of the most recent modification to this
channel’s property details.
Last Downloaded This shows the date that the item was last downloaded to
the server.
28 www.honeywell.com
DEFINING AN AXSS-II CONTROLLER
Property Description
Item Number The unique item number currently assigned to this
item.You can change the item number if you need to
match your current server database configuration. The
number must be between 1 and the maximum number of
channels allowed for your system.
29
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
Entering an address
For source and destination addresses the format for an AXSS-II controller address
is:
ControllerName Address
Part Description
ControllerName The name of the AXSS-II controller.
Address The address in the controller where the value is
recorded.
If you would like help when defining an address, click next to Address to
display the Address Builder.
Property Description
Address Type Select Controller.
Controller Select the appropriate AXSS-II controller. You need to have defined the
controller for the name to appear in this list.
Address The address in the controller where the value is recorded. See “Address
syntax” on page 30.
Address syntax
The format for the address is:
AddressCode AddressNumber
Part Description
AddressCode The code used for the address parameter. See “AXSS-II
Status Point addressing” on page 32.
AddressNumber The number configured for the address parameter.
30 www.honeywell.com
DEFINING AN AXSS-II ADDRESS FOR A POINT PARAMETER VALUE
The specific address format will depend on the type of point, and the type of
address.
Access point
CNTAX2 ACCESS 1
31
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
32 www.honeywell.com
DEFINING AN AXSS-II ADDRESS FOR A POINT PARAMETER VALUE
33
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
34 www.honeywell.com
DEFINING AN AXSS-II ADDRESS FOR A POINT PARAMETER VALUE
35
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
36 www.honeywell.com
DEFINING AN AXSS-II ADDRESS FOR A POINT PARAMETER VALUE
37
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
38 www.honeywell.com
OPTIMIZING SCANNING PERFORMANCE
Exception scanning
Data from the AXSS-II history journal is read at regular intervals and this does
not require point parameter scan periods as it is a server system-wide scanning
feature.
The server acquires status values from the AXSS-II using exception reporting.
Every exception scan rate period, the server sends a poll to each AXSS-II. The
AXSS-II will reply with all unreported status changes or attempted access events
in its history database. The server will use this information to update any related
points in its own database.
The exception poll is automatically scheduled by the server for every AXSS-II
controller.
Periodic scanning is not used for AXSS-II scanning as all changes of state are
read using exception scanning. No scan period should be assigned to points.
39
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
Initialization scanning
In addition to periodic and exception scanning, all configured points in the
server’s database are scanned by polling the AXSS-II controller upon
initialization. Initialization occurs at the following times:
• Server startup
• Start of day
• Controller/Channel in-service
• Recovery after communication failure
During initialization the following is performed:
• Download server time and date to AXSS-II
40 www.honeywell.com
TROUBLESHOOTING AXSS-II SCANNING ERRORS
41
3 – DEFINING A CHANNEL, CONTROLLER AND POINTS FOR AN AXSS-II CONTROLLER
42 www.honeywell.com
Configuring an AXSS-II
controller in Station 4
This section describes configuration tasks for an AXSS-II controller that you
perform in Station.
Attention Use the “AXSS-II setup and configuration checklist” on page 14 to guide
you through the tasks, and to avoid configuration problems.
43
4 – CONFIGURING AN AXSS-II CONTROLLER IN STATION
Related topics
“AXSS-II controller System Parameters tab properties” on page 45
44 www.honeywell.com
COMPLETING THE CONFIGURATION OF AN AXSS-II CONTROLLER IN STATION
Property Description
Controller Definition
Name An intuitive name given to the controller.
Description Up to 32-character description of the controller.
Location Click the ellipsis button to select a location from the
Location Browser.
---------------------
PIN grace period The PIN grace period, in seconds. See the AXSS-II
User’s Manual for more information.
Enable Duress Enables duress entries on pinpad readers.
---------------------
Passback Auto Forgive Time The time intervals when passback violations are
Periods forgiven.
Building Closed Time Periods The time intervals when the controller is expected to be
in building closed mode.
Report Mode Assignments
Report modes are defined to report the following events.
Tamper report mode The report mode for tamper circuit detection.
Power Fail report mode The report mode for power fail detection.
Duress report mode The report mode for a duress situation detection.
---------------------
Facility code A common number associated with all access cards as
set by the card manufacturer. Only cards with the facility
code matching this setting can gain access at readers
connected to this controller.
Copy Details From Copy details from another downloaded controller by
selecting the controller name from the drop down list
and clicking Copy.
45
4 – CONFIGURING AN AXSS-II CONTROLLER IN STATION
Notes
• If you modify the default report mode 1 (SE-RPT1), be careful because it is
the default report for door and monitor alarms.
• If you select an action for all three building modes, selecting time periods
serves no purpose because the AXSS-II ACU is always is in one of the three
modes.
Action Description
Send to Host Reports the event to the server.
Close Latch This feature is not currently supported by AXSS-II.
Close Output Contact Energizes the output contact specified in the Output
contact property.
46 www.honeywell.com
CONFIGURING AXSS-II REPORT MODES
Related topics
“Report mode properties” on page 48
47
4 – CONFIGURING AN AXSS-II CONTROLLER IN STATION
Property Description
Report Mode Definition
Name The report mode’s name, which can consist of up to 16
characters. It can be used for calling up the Report
Mode display, as well as for associating the report mode
with other access objects like AXSS-II door
configuration, AXSS-II monitor point configuration, or
AXSS-II system level configuration.
Description The description, which can consist of up to 32
characters.
Location Click the ellipsis button to select a location from the
Location Browser.
---------------------
Building open Building Limited mode is not supported by AXSS-II.
Building limited Building Limited selection is ignored by AXSS-II
Building closed controllers unless you want the report to be valid at all
times and have enabled the other two selections,
Building Open and Building Closed. For this case, you
should also enable the report during Building Limited
mode.
Time periods #1-3 Select the time periods from the drop down lists that
correspond with the action.
---------------------
Output contact The relay output contact to be energized when the report
mode action takes place.
Relay number and module:
• 1 to 4 - Main Controller
• 5 & 6 - RIO with ID 1
• 7 & 8 - RIO with ID 2
• 9 & 10 - RIO with ID 3.
Print * with log This feature is not supported by AXSS-II and this
configuration is ignored by AXSS-II controller.
Prevent building closure This feature is not supported by AXSS-II and this
configuration is ignored by AXSS-II controller.
Report mode to copy Copy details from another report mode by selecting the
report mode name from the drop down list and clicking
Copy.
48 www.honeywell.com
CONFIGURING THE DOOR DEFINITION OF AN AXSS-II ACCESS POINT
Related topics
“AXSS-II access point Door Definition tab properties” on page 50
49
4 – CONFIGURING AN AXSS-II CONTROLLER IN STATION
Property Description
Anti-passback The type of anti-passback action required for the door,
either None, Entry or Exit.
On a valid access, this entry checks the card in/out
status, and if valid for the attempted access, updates the
status of the card.
If you have not configured entry/exit doors, set this to
None.
Passback type The type of anti-passback checking to be performed:
• Hard. Access is denied if passback violation is
detected.
• Soft. Allows access anyway, but passback violation
is reported in either case.
VIP enable Enable the VIP pinpad.
Read key while door open AXSS-II ignores this configuration and reads keys every
time, even when the door is open.
Reverse action lock Puts the lock in reverse action mode. This option is
generally used if magnetic locks are used. Enable this if
you are using a fail safe door.
Notes:
• Fail safe doors are connected between NO and COM
points of the relay outputs.
• Fail safe doors open in case of controller failure.
• If the door is on a RIO and there is a communication
failure between RIO and the Main Controller, the
RIO grants an access on a failsafe door by simply
checking the facility code of the card.
• Fail secure doors mapped on the RIO remain closed
in case of communication failure.
• Fail safe doors are opened in case a fire input
connected and configured for AXSS-II Main
controller becomes active.
• Fail secure doors remain locked even in case of fire.
50 www.honeywell.com
CONFIGURING THE DOOR DEFINITION OF AN AXSS-II ACCESS POINT
Property Description
REX unlock Enables unlocking using a request to the Exit switch.
Many facilities require only entry through a door to be
checked by a card reader, whereas for exit through the
door, a simple Push button switch known as ‘Request to
Exit’ switch is used.
To enable an exit on REX switch active event, select this
option.
Door unlock time The length of time after which a door is re-locked after a
valid access/exit.
Door open time The maximum time the door can remain open after a
valid access/exit. If the door does not close after this
time, an “OPEN TOO LONG” alarm is generated.
Door switch The monitor number where the door sense switch is
connected. The monitor numbers are as follows.
Monitor Input number and location:
• 01 to 08 - Main Board
• 09 to 16 - RIO with ID 1
• 17 to 24 - RIO with ID 2
• 25 to 32 - RIO with ID 3.
REX switch The monitor number where the REX switch for the door
is connected. Monitor numbers are determined as for the
door switch.
Report Modes
The report mode defines what action is taken when a door-related event occurs.
Door Forced When forced door is detected by ACU.
Open Too Long When a door held open too long is detected by ACU.
Access Granted When valid access is granted through the door.
Access Denied When an attempted access through the door is denied by
ACU.
Exit Granted When a valid “REX” (that is, a request to exit) is granted
by ACU.
Exit Denied When an attempted “REX” request is denied by ACU.
Key Trace When a card with trace enabled is presented on the door
“sensor”.
Time Periods
Auto unlock A list of up to four AXSS-II time periods defining the
time intervals when the door is automatically opened.
51
4 – CONFIGURING AN AXSS-II CONTROLLER IN STATION
Property Description
Valid REX A list of up to four AXSS-II time periods defining the
time intervals when Exit (REX) requests is accepted for
that door by the ACU.
VIP Enable Enable time periods for the VIP pinpad to be active.
VIP Enable check boxes
Building open Enable VIP pinpad when the building is in open mode.
Building limited Enable VIP pinpad when the building is in limited mode.
Building closed Enable VIP pinpad when the building is in closed mode.
Relay Configuration
Door relay The relay number to which the lock of this door is
connected. The relay numbering will be as follows.
Relay number and location:
• 01 to 04 - Main Board
• 05 & 06 - RIO with ID 1
• 07 & 08 - RIO with ID 2
• 09 & 10 - RIO with ID 3.
52 www.honeywell.com
CONFIGURING AN AXSS-II MONITOR POINT
Property Description
Monitor Point Report Mode The report mode that is initiated when the monitor
becomes active. By default, the server sets this property
to the default report mode 1.
You must have MNGR security level to change the
monitor point report mode.
Download Use this button to download the monitor point
configuration to the relevant AXSS-II controller.
Note: If the specified report mode inhibits the “Send to
Host” action, then changes to the monitor point state are
not reported by exception to the server. Default period
background scanning does, however, continue to take
place.
53
4 – CONFIGURING AN AXSS-II CONTROLLER IN STATION
54 www.honeywell.com
Configuring access control and
security for AXSS-II controllers 5
This section describes how to configure access control and security for AXSS-II
controllers.
Attention Use the “AXSS-II access control and security configuration checklist” on
page 56 to guide you through the tasks, and to avoid configuration
problems.
55
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Prerequisites
• You have performed the basic configuration tasks for your system, for
example, you have defined the Facility and Organization Models, and, if
applicable, configured DSA and redundancy.
Tasks
Complete the tasks in the following order.
56 www.honeywell.com
SETTING UP A SYSTEM TO USE MULTIPLE CREDENTIALS CHECKLIST
Task Go to Done
Configure the credential type in Station. page 58
In Quick Builder configure the server to use multi- page 60
credentials.
Add reader points and specify the credential type the page 61
reader is to read
Add cards and specify the credential type for the card
as described in the Operator’s Guide.
Related topics
“About multiple credential systems” on page 62
57
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
58 www.honeywell.com
SETTING UP A SYSTEM TO USE MULTIPLE CREDENTIALS CHECKLIST
12 Make a note of the credential type IDs and descriptions so that you can
duplicate these in your Quick Builder project.
59
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
8 In the Add box, type the credential description for your other credential types
to match the credentials you added in Station and click Add.
For example, if you have MagStripe with an ID of 1 (as configured in Station),
type MagStripe = 1 and click Add.
9 Save your Quick Builder project.
10 Download the DefaultServer item from Quick Builder to the server.
60 www.honeywell.com
SETTING UP A SYSTEM TO USE MULTIPLE CREDENTIALS CHECKLIST
61
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
62 www.honeywell.com
CONFIGURING THE CARDHOLDER DATABASE FOR AXSS-II CONTROLLERS
Related topics
“Configuring fields” on page 64
“Defining a new field” on page 66
“Defining a cardholder template” on page 88
63
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Configuring fields
You can configure fields so that they meet your requirements. For example, you
could change the label of the LastName field from “Last Name” to “Family
Name”.
Note that if you have a redundant or DSA system, you must perform this task on
the primary/publishing server, that is, the primary server of a redundant server
pair, and the publishing server in a Cardholder DSA system.
Prerequisites
You have backed up your database. See “Backing up EBI Server data using
fullbkup” in the Backup and Restore Guide.
To configure fields
1 If you have redundant or DSA servers, on the primary/publishing server:
a. Choose Start > Programs > Accessories > Command Prompt.
A Command Prompt window opens.
b. Type stoprepl all uninstall and press ENTER.
c. Close the Command Prompt window.
If the command is successful, you will receive feedback that all replication
has been stopped.
2 Log on to Station with a security level of MNGR.
3 Choose Configure > Cardholder Management > Cardholder Database to
call up the Cardholder Database display.
4 Click the tab of the cardholder type you want to view and configure.
If you only want to view the vehicle fields, for example, click the Vehicle tab.
5 Select the field you want to modify by clicking on the field.
The field’s properties appear below in the Selected Field definition section.
6 Change the properties listed in the following table, as appropriate.
Note that the properties you can change vary from field to field. For many
system fields (inbuilt fields which have predefined uses), you can only change
the Label property.
7 Repeat steps 5 and 6 for other fields you want to configure.
8 If you have redundant servers, resynchronize them.
9 If you have a DSA system, resynchronize with the other servers.
64 www.honeywell.com
CONFIGURING THE CARDHOLDER DATABASE FOR AXSS-II CONTROLLERS
Property Description
Searchable If selected, the field is included in the Advanced Search
display. Note that if the number of fields enabled for
searching is large, the time that searches take to
complete can increase. Do not set unnecessary fields to
be searchable.
Required If selected, the field is mandatory, that is, it must be
filled in when adding a cardholder.
In displays, mandatory fields are marked with an
asterisk (*).
Tool tip The tool tip can only be set to one field. The contents of
the specified field are displayed as a tool tip when the
mouse pointer hovers over the cardholders in the search
results listed in the Navigation pane.
Visible If selected, the field is displayed.
Label The label that appears next to the field in displays.
Data Type The type of data that is stored in the field.
Caution: Do not change the data type because it may
have unpredictable affects on your system. If the data
type is not suited to your needs, define a new field with
the required data type.
Default Value The default value given to the field when adding a
cardholder.
Note that, in general, you use cardholder templates to
define default values.
Related topics
“Defining a new field” on page 66
“Defining a cardholder template” on page 88
65
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Prerequisites
You have backed up your database. See “Backing up EBI Server data using
fullbkup” in the Backup and Restore Guide.
Property Description
Searchable If selected, the field is included in the Advanced Search
display. Note that if the number of fields enabled for
searching is large, the time that searches take to
complete can increase. Do not set unnecessary fields to
be searchable.
66 www.honeywell.com
CONFIGURING THE CARDHOLDER DATABASE FOR AXSS-II CONTROLLERS
Property Description
Required If selected, the field is mandatory, that is, it must be
filled in when adding a cardholder.
In displays, mandatory fields are marked with an
asterisk (*).
Tool tip The tool tip can only be set to one field. The contents of
the specified field are displayed as a tool tip when the
mouse pointer hovers over the cardholders in the search
results listed in the Navigation pane.
Visible If selected, the field is displayed.
Label The label that appears next to the field in displays.
Data Type The type of data that is stored in the field:
• boolean
• datetime
• list (If you select this, you must define each value in
the list and then click Add.)
• number
• text
• decimal
Default Value The default value given to the field when adding a
cardholder.
Note that you can also use cardholder templates to
define default values.
67
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Related topics
“Cardholder preferences properties” on page 69
68 www.honeywell.com
CONFIGURING CARDHOLDER PREFERENCES FOR AXSS-II CONTROLLERS
Property Description
Cardholder Preferences for Site Shows the server (site) to which these preferences apply.
Default Employee expiry The default expiry period or date for new employee
setting cardholders.
You can specify the date as either an offset from the date
when the cardholder or card is added (for example, 10
years), or as a fixed date.
Default External Personnel The default expiry period or date for External Personnel
expiry setting cardholders.
Default Vehicle expiry setting The default expiry period or date for Vehicle
cardholders.
Default Card expiry setting The default expiry period or date for new cards.
Show names by Specifies the default order in which names are listed in
displays.
Limit results returned by Specifies the maximum number of results that are
searches to returned from a search. The default is 1000.
Resize cardholder images to If cleared, the cardholder images are cropped to the size
show the entire image with no of the image window. For example, if an image is wider
cropping than the image window, the sides of the image that
exceed the image window are not visible. The image on
a printed card is also cropped.
If selected, the cardholder images are resized to fit
within the image window. The image on a printed card is
also resized.
The following displays contain an image window:
• Cardholder detail display
• Image capture display
• Image capture settings display
• Card print preview
• Event Summary detail pane
• Faceplate of an access point detail display
69
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Property Description
Display the details of each new This property controls whether the details of a newly-
Card or Cardholder added entity (that is, cardholders, templates, unissued
immediately after they are cards or external companies) are shown immediately
added after the entity is added to the system (if the property is
True), or if the Add page is shown again after adding a
new entity to the system (if the property is False,
allowing faster adding of multiple entities).
If details are being shown, and a range of unissued cards
is assigned in one go, then the details for all the new
multi-selected cards will be shown.
Remove Cardholder from If selected, deleting a cardholder deletes the
database on delete cardholder’s record from the database.
If cleared, deleting a cardholder marks the cardholder as
“deleted”, but retains the cardholder’s record in the
database.
Automatically append wildcard If selected, a wildcard character is automatically added
characters to search to the search string. For example, if the operator types
smi as a search string, cardholders Smith and Smithers
would be returned in the search results.
Limit number of active cards The maximum number of active cards that can be
per cardholder to assigned to a cardholder.
Auto Card Commencement and Expiry
Enable auto card If selected, the cardholder’s card(s) automatically
commencement and expiry commence and expire.
Validation interval The interval at which the system checks for cards and
cardholders that are about to commence or expire.
Warning time The number of days before a card is due to expire that
the card expiry warning is displayed. For example, if
this is set to 1, then the card expiry warning appears on
the card one day before the card is due to expire.
Cards will expire if not used for If selected, a card will automatically expire if it has not
been used for the specified number of days.
PIN Configuration
70 www.honeywell.com
CONFIGURING CARDHOLDER PREFERENCES FOR AXSS-II CONTROLLERS
Property Description
Number of PIN digits The number of digits in the card’s PIN (either 4, 5 or 6
digits). All access controllers support a 4 digit PIN code.
NexSentry Star II controllers support 6 digit PINs.
If some controllers in your system only support 4 digit
PINs, you can only use 4 digit PINs, even if you also
have some Star II controllers. For example, if you have
an SE only site with 5 or 6 digit PINs and want to add a
different controller technology (for example, Temaline),
you must change the PIN code length down to 4 digits.
Note: Changing the number of digits in a working
system will change every PIN, by either adding or
removing digits. Increasing the number of digits will add
zeros to the beginning of the PIN. For example, if the
current PIN is “1234”, changing to 6 digits will change
the PIN to “001234”. Decreasing the number of digits
will remove the most significant digit(s). For example, if
the current PIN is “123456”, changing to 4 digits will
change the PIN to “3456”.
If you have a DSA SE only system, ensure that the PIN
code lengths are consistent across the DSA servers to
ensure cardholders can move between servers with the
same card and PIN code working on each server in the
system.
71
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Tasks
Complete the tasks in the following order.
Related topics
“About access levels” on page 84
“About zones” on page 85
“About anti-passback and Perimeter Global Anti-Passback (PGAP)” on page 87
“Deleting a zone” on page 79
“Modifying an access level” on page 82
“Deleting an access level” on page 83
72 www.honeywell.com
CONFIGURING ACCESS LEVELS FOR AXSS-II CONTROLLERS
Prerequisites
• You have read the naming rules for access levels, time periods and zones.
Related topics
“Configuring access levels for AXSS-II controllers” on page 72
“Naming rules for access levels, time periods, and zones” on page 78
73
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Enabling PGAP
If you want to use Perimeter Global Anti-Passback (PGAP), you must enable it.
Note that all access points must have an Exit Zone configured.
To enable PGAP
1 Log on to Station with a security level of MNGR.
2 Choose Configure > Access Control > Zone Enforcement/Anti-passback
to call up the Zone Enforcement and Anti-Passback display.
3 Click Enable (in the Perimeter Global Anti-Passback (PGAG) section).
Related topics
“About anti-passback and Perimeter Global Anti-Passback (PGAP)” on page 87
“Configuring access levels for AXSS-II controllers” on page 72
74 www.honeywell.com
CONFIGURING ACCESS LEVELS FOR AXSS-II CONTROLLERS
Configuring zones
You configure zones in Station, after you have downloaded their names (and
associated points) from Quick Builder.
To configure zones
1 Log on to Station with a security level of SUPV (or higher).
2 Choose Configure > Access Control > Zones to call up the Zones display.
3 Click a zone to call up the Zone Definition display.
The access points that are listed in the display represent the card readers that
control entry to the zone.
4 If you want to base this zone definition on an existing zone definition:
a. In the Zone to copy from list, click the existing zone.
b. Click Copy.
The details are copied from the existing zone.
5 In the Description box, type a suitable description for the zone.
6 In the Location box, browse and select the location to which the zone is
attached.
7 If you have enabled PGAP and this is the outside zone, select the Outside
Zone check box.
A site can have more than one outside zone. This provides nested anti-
passback. The only requirement for an access level change is a transition from
outside to inside, or inside to outside.
8 Click Save.
9 If you want to configure other zones, return to the Zones display and repeat
steps 3 to 8.
Related topics
“Configuring access levels for AXSS-II controllers” on page 72
“Naming rules for access levels, time periods, and zones” on page 78
“About zones” on page 85
75
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Prerequisites
• You have read the naming rules for access levels, time periods, and zones.
Related topics
“Configuring access levels for AXSS-II controllers” on page 72
“Naming rules for access levels, time periods, and zones” on page 78
“About access levels” on page 84
76 www.honeywell.com
CONFIGURING ACCESS LEVELS FOR AXSS-II CONTROLLERS
Prerequisites
• You have read the naming rules for access levels, time periods and zones.
Related topics
“Configuring access levels for AXSS-II controllers” on page 72
“Naming rules for access levels, time periods, and zones” on page 78
“About access levels” on page 84
“About zones” on page 85
77
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
78 www.honeywell.com
CONFIGURING ACCESS LEVELS FOR AXSS-II CONTROLLERS
Deleting a zone
Deleting a zone involves first checking that it is not assigned to any access levels,
and then deleting the access points associated with the zone.
To delete a zone
1 Log on to Station with a security level of SUPV (or higher).
2 Choose Configure > Access Control > Access Levels to call up the Access
levels display.
3 Check that the zone is not assigned to any access level.
If you have many access levels, it may be simpler to configure an Access
Level report to determine if the zone has been assigned any access levels.
Type the zone name in the report’s Zone field. See “Access level report” in the
Configuration and Administration Guide.
4 If the zone is assigned to an access level, you must modify the access level so
that it no longer uses the zone.
5 In Quick Builder, delete all the access points that are defined as entering the
zone.
6 Download the deletions to the server.
The zone is then automatically deleted.
79
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Related topics
“Configuring zones” on page 75
80 www.honeywell.com
CONFIGURING ACCESS LEVELS FOR AXSS-II CONTROLLERS
81
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
82 www.honeywell.com
CONFIGURING ACCESS LEVELS FOR AXSS-II CONTROLLERS
83
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Related topics
“About zones” on page 85
“About anti-passback and Perimeter Global Anti-Passback (PGAP)” on page 87
“Configuring access levels for AXSS-II controllers” on page 72
84 www.honeywell.com
CONFIGURING ACCESS LEVELS FOR AXSS-II CONTROLLERS
About zones
A zone represents a physical part of your site, to which entry is controlled by one
or more card readers.
If necessary, you can “nest” zones, providing the parent zone entirely encloses the
child zone(s). For example, in the following figure, zones 1, 2 and 3 are entirely
enclosed within zone 4 (which represents the whole floor).
Access to a zone can be controlled by more than one card reader. In the following
figure, the card readers for doors C and D both belong to Zone 3. Note, however,
that each card reader can only belong to one zone and this is called zone
enforcement.
Zone 1 Zone 3
Computer Room Door B Engineering Department
Door C
Door A
Zone 2
Laboratory Door D
Door F
Zone 4
First Floor
Elevator Door E
You should carefully plan your zone definitions so that they meet your security
needs and are easy to maintain. For example:
• Only create a zone if it has specific security needs, either in terms of who can
access it, or when people can access it. For example, you may need close the
laboratory on weekends, or to limit access to the computer room to IT
personnel.
• Try to create zones that are controlled by just one or two card readers. Such
zones are easier to configure and manage.
Related topics
“About access levels” on page 84
85
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
86 www.honeywell.com
CONFIGURING ACCESS LEVELS FOR AXSS-II CONTROLLERS
Related topics
“About zones” on page 85
“Configuring access levels for AXSS-II controllers” on page 72
87
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
88 www.honeywell.com
CONFIGURING TIME AND ATTENDANCE TRACKING
Related topics
“Time and attendance batch file (timatd.bat)” on page 90
89
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Example
This batch file outputs the data to the server’s COM1 port.
@echo off
rem #Time and Attendance Batch File
set param1=%1
set param2=%2
set param3=%3
set param4=%4
set param5=%5
set param6=%6
set param7=%7
set param8=%8
set param9=%9
rem #remove double quotes from parameters
set cardnumber=%param1:"=%
set cardholder=%param2:"=%
set index1=%param3:"=%
set index2=%param4:"=%
set index3=%param5:"=%
set index4=%param6:"=%
set readername=%param7:"=%
set date=%param8:"=%
set time=%param9:"=%
rem #select the suitable employee code
set employeecode=%index1%
rem #set up device port name for the Time and Attendance system
port
rem #note the "//./" is necessary for higher com ports.
set dev=//./COM1
90 www.honeywell.com
CONFIGURING TIME AND ATTENDANCE TRACKING
rem #set up baud rate for the Time and Attendance system port
set baudrate=9600
rem #set up data bits for the Time and Attendance system port
set databits=8
rem #set up parity for the Time and Attendance system port.
Options available are
rem parity=e
rem parity=o
rem parity=n
set parity=n
MODE %dev% BAUD=%baudrate% PARITY=%parity% DATA=%databits% > NUL
set cmdstr=%date% %time% %cardnumber% %cardholder%
%employeecode% %readername%
echo %cmdstr% > %dev%
Related topics
“Configuring time and attendance tracking” on page 89
91
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
92 www.honeywell.com
DEFINING A CARDHOLDER MANAGEMENT PROFILE
93
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Notes
• The download indicator has three modes:
- Flashing yellow means a download is in progress
- Solid yellow means that one or more downloads had errors
- No color with the word ‘Download’ indicates that a download is pending.
This can be a local download or a remote download of a card that was
initiated locally.
• The action bar for a cardholder will display a ‘Download Pending’ label and a
link to the Download Summary display if the last download was
unsuccessful.
• To find out why the download failed, click the Downloads box to call up the
Download Summary display. The status provides a direct link to the
download report and may indicate several different statuses, such as Failed,
Retry Pending and Cancelled. If a card is marked as Failed, for example, click
Failed to see more information about why the download failed.
The following table describes the three ways you can manually initiate a
download.
94 www.honeywell.com
DOWNLOADING ACCESS INFORMATION FOR AXSS-II CONTROLLERS
95
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Downloading cards
This section describes how to force individual cards to be downloaded, regardless
of whether any changes have been made.
Card and cardholder changes are downloaded automatically when Save is clicked
(or when you navigate away from the Cardholder Management display). There is
a Download Card button on the Cards tab of the Cardholder Management
display that allows you to select one or more cards and force them to be
downloaded, regardless of whether any changes have been made.
If PGAP is enabled, there are also two Forgive buttons that will force either the
selected card(s) or all of the cards belonging to the selected cardholder(s) to be
downloaded without PGAP restrictions.
96 www.honeywell.com
DOWNLOADING ACCESS INFORMATION FOR AXSS-II CONTROLLERS
Attention This procedure may take some time. The amount of time depends on the
number of controllers you select, the complexity of your system and the
amount of modified information that needs to be downloaded.
97
5 – CONFIGURING ACCESS CONTROL AND SECURITY FOR AXSS-II CONTROLLERS
Attention This procedure may take some time, and should only be performed during
off-peak times, so that cardholders are not unnecessarily denied access.
(The time depends on the number of controllers you select and the
complexity of your system.)
98 www.honeywell.com
Configuring Integrated PhotoID
for AXSS-II controllers 6
This section describes how to configure Integrated PhotoID, and how to create the
card layouts that are used when printing security cards.
You use Integrated PhotoID to:
• Capture photographs and signatures of cardholders from a variety of sources
and store them directly in the CMS database.
• Design the layout of photo-identification cards (badges).
• Print photo-identification cards.
Related topics
“Integrated PhotoID configuration checklist” on page 100
“About the Integrated PhotoID components” on page 113
99
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
Prerequisites
• You have installed the Integrated PhotoID hardware in accordance with the
Installation Guide.
Tasks
100 www.honeywell.com
SETTING UP THE ENVIRONMENT FOR TAKING PORTRAITS
The lighting you use to illuminate the subject and the backdrop
Lighting has a major effect on portrait quality, especially if you are using a video
camera as the image capture device. For best results, follow these guidelines:
• Use photographic or incandescent lights. The lights you use should be ones
that produce natural looking pictures. Use photographic (incandescent) lights
produce “warm” looking tones because they produce more natural skin colors.
Avoid fluorescent lights because they often produce skin colors with a
greenish tinge.
• Select a suitable lighting intensity. You need to adjust the lighting intensity,
so that the portraits are neither too dark or too bright.
• Use diffused (soft) lighting. Diffused lighting produces a more acceptable
result and avoids dark shadows. You can diffuse lighting by for, example:
- Reflecting the light off the ceiling or a wall
- Using a diffusing umbrella
- Using a frosted globe
- Moving the light further away from the subject
• Adjust the amount of lighting on the background. Adjust the lighting on
the background so that it is acceptable in the images you capture. Too much
lighting will make the portrait appear too dark; whereas too little lighting will
make the background appear too dark.
101
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
102 www.honeywell.com
CONFIGURING THE IMAGE CAPTURE SETTINGS
Prerequisites
You must have the Image Capture Operator Profile task selected in order to
configure the Integrated PhotoID image capture settings. This is set in the Card
Management Tasks/Card holder Tasks section of the Cardholder Management
Operator Profiles display.
103
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
Results
• The capture settings you have configured are applied to all images captured on
this computer.
Related topics
“Defining a cardholder management profile” on page 93
“Image capture settings” on page 105
“Enhanced security with ghosting and chromakey (AXSS-II)” on page 114
“Integrated PhotoID image file naming conventions” on page 107
104 www.honeywell.com
CONFIGURING THE IMAGE CAPTURE SETTINGS
Property Description
Image Capture Source The source used to capture portraits, signatures or
documents:
• None. Disables image capture.
• MCI. Images are captured from a live video camera,
via a video capture board installed in the computer.
• TWAIN. Images are captured from devices such as
scanners, digital cameras and also some video
capture boards.
• Mouse. Cardholders “write” their signatures using a
graphics tablet that supports mouse emulation.
• Wintab. Wintab in name only. EBI uses third party
vendors software to interface with signature capture
tablets. Integrated PhotoID presently supports the
ePad ink series from Interlink Electronics and SigLite
series from Topaz.
File Format The format in which portrait or signatures are stored.
Note that the format you choose is restricted by the
capture source as follows:
• MCI capture supports JPG and BMP.
• TWAIN capture supports JPEG and BMP.
• Mouse/Wintab capture only supports BMP.
Ghosting Sets the ghosting properties for images captured using
this computer.
Chromakey Sets the chromakey properties for images capture using
this computer
Red Changes the amount of red color that appears in the
image captured using this computer.
Green Changes the amount of green color that appears in the
image captured using this computer.
Blue Changes the amount of blue color that appears in the
image captured using this computer.
Card Printer Sets the printer you want to use to print cards. The
printer you choose is automatically set as the printer in
the Print dialog box when you print a card.
Double Sided Printing Sets whether cards are printed double-sided.
105
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
The installation wizard also creates the following folders under PhotoID:
• CardLayouts
• HolderImages
• Signatures
The installation wizard creates a virtual directory with read and browse
permissions for the PhotoID directory. Client computers can access the directory
through the following path: http://<server name>/cms/photoID, where <server
name> is the name of the EBI server.
106 www.honeywell.com
CONFIGURING THE IMAGE CAPTURE SETTINGS
107
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
2 Choose File > Save As and save the layout with a different name.
3 Select the card layout and ungroup it into its subcomponents.
4 Modify the card layout as required.
5 If you want to include a database field in the layout, the name of the
associated object must be in the format <TableName>_<FieldName>
where <TableName> is the name of the database table that the field is coming
from, and <FieldName> is the name of the field to include.
Examples of system fields are Employee_Name or ExternalRegular_Surname.
Examples of user fields are EmployeeUserFields_UF15 or
VehicleUserFields_UF4.
(You can use any field listed in “Cardholder database tables” on page 110 plus
any user defined fields.)
6 When you have finished creating your new layout, select all objects and group
them into a single object. (You must do this for the card layout to function
properly.)
7 Save and close the layout.
108 www.honeywell.com
CREATING CARD LAYOUTS
109
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
110 www.honeywell.com
CREATING CARD LAYOUTS
ExpiryDateTime
111
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
Prerequisites
• Cumulative security update for Internet Explorer 7 (KB947864) or later is
installed
112 www.honeywell.com
ABOUT THE INTEGRATED PHOTOID COMPONENTS
For: Go to:
Cards and card printers page 114
Cameras and lighting page 116
Image capture devices page 120
Card printers page 115
113
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
Table 5 A typical photo ID card that uses both ghosting and chromakey
Printing options
You can print cards in a number of ways. For example:
• You can print cards on paper, cut them out and laminate them. This is a cost-
effective, but labor-intensive approach.
• You can print cards directly onto correctly sized plastic blanks.
114 www.honeywell.com
ABOUT THE INTEGRATED PHOTOID COMPONENTS
• You can print cards directly onto some access control cards. If you want to do
this, you need to ensure that the cards are qualified by the printer
manufacturer, and that they have the correct surface for dye sublimation
printing. (Some cards, especially those used for access control, are thicker
than normal cards, which may mean that you will have to make adjustments to
the printer.)
Card printers
You can use any suitable Windows-compatible printer to print PhotoID cards.
Unlike other EBI printers, you do not need to define a card printer in Quick
Builder. Instead, you install the printer driver onto the computer you use for
printing cards, and then use it as you would any other printer connected to the
computer.
Handling cards
Cards must be absolutely clean, unscratched, and free of dust before being placed
in the printer hopper. We recommend that you wear a pair of cotton gloves while
handling the cards, to prevent damage from fingerprints. You should not open
new packets until they are needed, and store unused cards in a sealed container
away from dust and dirt.
If you have to punch holes in the cards, you should do this after they have been
printed.
115
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
Video cameras
Video cameras are a more popular choice for the image capture device. They have
the advantage that the image can be previewed before being captured. The
operator freezes the live video image and saves it if the subject is happy with the
portrait. This process is a lot faster than uploading an image from a digital
camera.
The disadvantage is that video cameras are very susceptible to variations in the
lighting conditions. Often some tuning needs to be done to get the video camera
to perform optimally.
The following types of video cameras are typically used:
• CCTV cameras (as used in the security industry) are cheap, generally very
sensitive to the level of light, and can operate in quite low light. For this
reason, the light source may need to be diffused to prevent blooming. Ensure
that the camera does not have a fish-eye lens as is commonly installed on
security cameras.
116 www.honeywell.com
ABOUT THE INTEGRATED PHOTOID COMPONENTS
Color balance
The light from a fluorescent light appears white but is actually slightly green. The
light from an incandescent light bulb is very yellow. The light coming from an
open window on a bright day is usually blue from the blue sky. The brain and the
human eye correct for these different lighting conditions, however a video camera
117
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
does not. When an image is captured the resultant image will sometimes have a
color “cast” on it unless care is taken to balance out the color cast that has resulted
from the lighting.
118 www.honeywell.com
ABOUT THE INTEGRATED PHOTOID COMPONENTS
to person. In the above example, the person with the blue shirt will have a red face
and the background will appear pale. A person with a white shirt will appear less
red and the background more blue.
When color-balancing a camera, be sure to use true white paper; some paper is
off-white. Ensure that the area where subjects are to have their image taken is
evenly lit and free of shadows. This is good general photography practice.
Ensure that the lighting around the portrait area is not subject to change. For
example, an area near an open window is not good. The lighting levels and color
balance will change from day to day as the weather and time of day changes.
Ideally, the photo taking area should be set aside for this purpose so that correct
lighting and camera positioning can be established. It should not have a window,
or at least be able to have the window covered so that external light sources don’t
affect the taking area.
Use a professional photographer quality lighting and camera tripod assembly.
These units provide a stable mount for the camera as well as supporting a halogen
lamp and umbrella for correct light diffusion.
119
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
120 www.honeywell.com
ABOUT THE INTEGRATED PHOTOID COMPONENTS
121
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
122 www.honeywell.com
CONFIGURING THE CARDHOLDER COMPARISON DISPLAY
Next steps
• If you want an operator to manually unlock a door after they have verified a
cardholder, modify the controller so that the door is not automatically
unlocked whenever a cardholder is granted access at a card reader.
Related topics
“Cardholder comparison” on page 125
“Preventing a door from automatically unlocking” on page 124
123
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
Caution
Before you perform this procedure, ensure that there is another mechanism, for example a
REX switch for unlocking the door in case communications between EBI and the
controller is lost.
Prerequisites
• The Cardholder Comparison display must be configured with lock and unlock
buttons as this procedure prevents access to the door. When you complete this
procedure, the cardholder comparison display is the only means by which the
door can be unlocked.
124 www.honeywell.com
CONFIGURING THE CARDHOLDER COMPARISON DISPLAY
Cardholder comparison
You may have secure areas in your site where you want to verify that the person
who has presented a card at a reader is in fact the owner of the card before they
are given access. The Cardholder Comparison display can be configured to
appear in Station whenever a card is presented to a reader. Live video from a
Honeywell DVM camera located at the reader can be compared to the image that
has been captured for the cardholder. If the images match, then the operator can
unlock the door to provide access to the cardholder.
Alternatively, you may want to configure the Cardholder Comparison display to
appear when a card or cardholder is denied access to a door. Live video from a
Honeywell DVM camera located at the reader can be used by the operator to
decide whether video of the event needs to be recorded.
The cardholder comparison can be used only if you use integrated photo ID and
Honeywell Digital Video Manager.
125
6 – CONFIGURING INTEGRATED PHOTOID FOR AXSS-II CONTROLLERS
126 www.honeywell.com
Index
127
INDEX
Integrated PhotoID
background 101
cameras 116
card layouts
defining 108
ghosting and chromakey 114
guidelines for 109
cards 114
checklist 100
chromakey 114
color balance 117
components 113
database tables, cardholder 110
128 www.honeywell.com