CC9K v2 90 HWConfigGd 8200 1950 08 A0 en
CC9K v2 90 HWConfigGd 8200 1950 08 A0 en
2.90 8200-1950-08
A0
July 2020
C•CURE and Software House are registered trademarks of Johnson Controls.
The trademarks, logos, and service marks displayed on this document are registered in the United States [or other
countries]. Any misuse of the trademarks is strictly prohibited and Johnson Controls will aggressively enforce its
intellectual property rights to the fullest extent of the law, including pursuit of criminal prosecution wherever necessary. All
trademarks not owned by Johnson Controls are the property of their respective owners, and are used with permission or
allowed under applicable laws.
Product offerings and specifications are subject to change without notice. Actual products may vary from photos. Not all
products include all features. Availability varies by region; contact your regional sales manager. This manual is proprietary
information of Johnson Controls. Unauthorized reproduction of any portion of this manual is prohibited. The material in this
manual is for information purposes only. It is subject to change without notice. Johnson Controls assumes no
responsibility for incorrect information this manual may contain.
© 2020 Johnson Controls. All rights reserved. JOHNSON CONTROLS, TYCO and Software House are trademarks of
Johnson Controls.
Table of Contents
Preface 17
Finding More Information 18
Conventions 19
Software House Customer Support Center 20
Chapter 13 - Configuring Reader LCD Messages, LED Colors, LED Patterns, and Beep
Patterns 525
LCD Message Set 526
Accessing the Reader LCD Message Set Editor 526
Changing the Language for the Default LCD Messages 531
Reader LCD Message Set Editor 532
Reader LCD Message Set Tasks 532
Configuring a Reader LCD Message Set 534
LED Colors, LED Patterns and Beep Patterns 538
Limitations 538
LED Color Configuration 539
LED Pattern Configuration 539
Beep Pattern Configuration 540
This C•CURE 9000 Hardware Configuration Guide is designed for new and experienced security system users. The
manual describes the various hardware objects in the C•CURE 9000 application program and presents procedures for
configuring and using them.
The manual assumes that you have already installed C•CURE 9000 and have familiarized yourself with the basic
C•CURE 9000 information provided in the C•CURE 9000 Getting Started Guide.
In this preface
Manuals
C•CURE 9000 software manuals are available in Adobe PDF format on the C•CURE 9000 installation media. You can
access the manuals if you copy the appropriate PDF files from the C•CURE 9000 installation media Manuals\CCURE
folder.
The available C•CURE 9000 and Software House manuals are listed in the C•CURE 9000 Installation and Upgrade Guide.
These manuals are also available from the Software House Member Center website
(http://www.swhouse.com/TechnicalLibrary/TechLibSW.aspx).
Online Help
You can access C•CURE 9000 Help by pressing F1 or clicking Help from the menu bar in the Administration/Monitoring
Station applications.
Conventions
This manual uses the following text formats and symbols.
Convention Meaning
Bold This font indicates screen elements, and also indicates when you should take a direct action in a procedure.
Bold font describes one of the following items:
• A command or character to type, or
• A button or option on the screen to press, or
• A key on the keyboard to press
• A screen element or name
blue color text Indicates a hyperlink to a URL, or a cross-reference to a figure, table, or section in this guide.
Indicates a note. Notes call attention to any item of information that may be of special importance.
NOTE
Indicates a caution. A caution contains information essential to avoid damage to the system. A caution
can pertain to hardware or software.
Indicates a warning. A warning contains information that advises users that failure to avoid a specific
action could result in physical harm to the user or to the hardware.
Indicates a danger. A danger contains information that users must know to avoid death or serious injury.
Qualified Integrators can register to access the Technical Support Portal at http://www.swhouse.com. Click Support and
select Support Portal to access the Support Portal log in page.
The email address you use to register for access to the portal must be the same one you used for the certification course.
If the request is approved, log in credentials are emailed twenty-four to forty-eight hours after received.
Before Calling
Ensure that you:
■ Are the Dealer of record for this account.
■ Are certified by Software House for this product.
■ Have a valid license and current Software Support Agreement (SSA) for the system.
■ Have your system serial number available.
■ Have your certification number available.
Hours Normal Support Hours Monday through Friday, 8:00 a.m. to 8:00 p.m., EST. Except holidays.
Phone For telephone support contact numbers for all regions, see http://www.swhouse.com/support/contact_technical_support.aspx.
EMEA
Hours: 8:00 a.m. to 6:00 p.m. CET
■ Toll Free: +800 CALLTYCO or +800-2255 8926
■ Direct: +31 475 352 722
Asia Pacific
Hours: 9:00 a.m. to 5:00 p.m. CST
■ Toll Free: +800 CALLTYCO or (+800-2255 8926)
■ Direct: +86 21 61916510
■ China only Hotline: 4006711528
■ India only Hotline: 1-800-1082-008
■ Australia: 02-9684-3980
Latin America
■ Colombia: + 57 1 344-1422 +57 2 8912476 +57 4 2040519
■ Costa Rica: + 506 4000-1655
■ República Dominicana: +1 8292353047
■ El Salvador: + 503 21368703
■ Guatemala: + 502 22681206
■ Panamá: + 507 836-6265
■ Mexico: + 52 5585261801
■ Perú: + 511 6429707
■ Venezuela: + 58 212-720-2340
■ Buenos Aires: + 54 11 5199 3104
This chapter describes the requirements and configuration for IPv6 on C•CURE 9000 servers, C•CURE 9000 clients,
iSTAR controllers, and IP-ACMs.
In this chapter
IPv6 Configuration 24
IPv6 Configuration
To configure the system running the C•CURE Server or client to use IPv6:
1. Open the Control Panel.
2. Select Network and Sharing Center.
3. Select Local Area Connection.
Set the IP address as the host address for the iSTAR controllers in the Options & Tools > System Variables > iSTAR
Driver>Specified Host IPV6 Address field. Then restart the driver.
iSTAR Controller Configuration
The IP Address Family selection for the iSTAR controller, in C•CURE 9000, is located in the iSTAR Controller Editor
General tab.
This setting must match the IP Address Family selected in the ICU. The ICU must be used to switch the controller's
Address Family.
ICU
The IP Address Family is selected on the Controller editor Ethernet Adapter tab in the ICU. The ICU must be used to
switch the controller's Address Family.
IP-ACM Configuration
The IP-ACM Configuration/Status web page is used to configure the Address Family.
l From a browser:
This chapter explains how to use the C•CURE 9000 Hardware pane to configure and manage the hardware components
that are connected to the C•CURE 9000 server.
In this chapter
You can use the Hardware Tree to navigate to hardware components you want to view or edit, or to create new hardware
components, such as a reader you want to add to a controller.
The Hardware Tree displays, by default, folders for Digital Certificates, Floors, Reader LCD Message Sets, and a
Hardware Folder called Company Name.
The folder called Company Name is the default container for apC Comm Ports and the Controllers, Readers, Doors,
Elevators, Inputs, and Outputs.
This folder is re-namable so that you can customize the C•CURE 9000 Hardware Tree to your site's needs.
You can click on the to the left of a folder or object to expand the tree.
When you select a folder or object in the tree, you can right-click to display a context menu that shows the objects you can
create under the selected folder or object.
Example:
If you right-click on the Company Name folder, the context menu shows that you can create a wide variety of
Hardware Tree objects in this folder.
Figure 1: Hardware Tree Context Menu
The following topics provide more information about using the Hardware pane.
■ Partitions on Page 29
■ Hardware Tree on Page 30
■ Hardware Tree Objects on Page 30
■ Hardware Tree Tasks on Page 31
Partitions
If you partition the C•CURE 9000, a new Hardware folder is created for each Partition you create, and given the same
name as the Partition.
You can also create additional Hardware folders to contain hardware devices if you need to separately group hardware to
reflect, for example, a multi-tenant building, a campus, or a multi-site company.
You can use Partitioning and Privileges to control Operator access to each tenant's hardware folder(s) if you don't want
one tenant to be able to view another tenant's security access hardware and personnel.
The New Object Partition setting in the Administration Workstation determines the Partition in which an Operator can
create objects, in addition to Hardware Tree objects such as Floors that reside at the root of the Hardware Tree. You can
use the Privilege Editor to grant or deny an Operator access to a Partition, which affects whether they can view or create
objects in that Partition.
For example, you could create a privilege that has no access to the Partition (and Hardware folder) called Company A, but
with full access to Company B, and assign it to Operators from Company B, so that they can view their configuration but
not the configuration for Company A. See the C•CURE 9000 Software Configuration Guide for more information about the
Privilege Editor.
You can also drag and drop objects to move them in the Hardware Tree. For example, you can move C•CURE Mobile
objects from one Hardware folder to another. See Using Drag and Drop in the Hardware Tree on Page 35 for more
information.
Hardware Tree
The Hardware pane displays a tree structure that shows how you have configured the hardware on the C•CURE 9000
system. For example, the hardware tree shows you which readers, inputs, and outputs are configured for each controller.
You can use the Hardware Tree to navigate to hardware components you want to view or edit, or to create new hardware
components, such as a reader you want to add to a controller.
The Hardware Tree displays, by default, folders for Floors, Digital Certificates, and a Hardware Folder called Company
Name.
The folder called Company Name is the container for your Comm Ports, Controllers, Readers, Doors, Elevators, Inputs,
and Outputs.
This folder is re-namable so that you can customize the C•CURE 9000 Hardware Tree to your site's needs.
You can click on the to the left of a folder or object to expand the tree.
When you select a folder or object in the tree, you can right-click to display a context menu that shows the objects you can
create under the selected folder or object. For example, if you right-click on the Company Name folder, the context menu
shows that you can create a wide variety of Hardware Tree objects in this folder.
If you Partition your C•CURE 9000, a new Hardware folder is created for each Partition you create. This hardware folder is
given the same name as the Partition.
You can also create additional Hardware folders to contain hardware devices if you need to separately group hardware to
reflect, for example, a multi-tenant building, a campus, or a multi-site company.
You can use Partitioning and Privileges to control Operator access to each tenant's hardware folder(s) if you don't want
one tenant to be able to view another tenant's security access hardware and personnel.
For example, you could create a privilege that has no access to the Partition (and Hardware folder) called Company A, but
with full access to Company B, so that Operators from Company B can view their configuration but not the configuration
for Company A.
You can also drag and drop objects to move them in the Hardware Tree. For example, you can move C•CURE Mobile
objects from one Hardware folder to another. See Using Drag and Drop in the Hardware Tree on Page 35 for more
information.
■ Hardware Tree Objects on Page 30
■ Hardware Tree Tasks on Page 31
Object Description
Object Description
Digital Certificate These objects reside in the Hardware Tree but they are created using Encryption Options from the Options & Tools
pane. See the C•CURE 9000 System Maintenance Guide for more information.
apC Comm Port See apC Comm Port Editor on Page 322.
CCURE Mobile These objects reside in the Hardware Tree but they are documented in the C•CURE Mobile Handheld Reader User
device Guide.
NOTE: C•CURE Mobile cannot be used in UL applications.
The right-click Context Menu for an object has selections for objects that you can create under that object.
For example, if you want to create an iSTAR Cluster in a Hardware Folder, right-click on the Hardware Folder and select
iSTAR Cluster from the menu.
3. Select the object you wish to create and select New from the menu.
4. The Editor for the object opens and you can configure the object.
3. Click and a Dynamic View listing the object type appears in the content area.
4. You can filter, sort, group, and add columns to the list. See the C•CURE 9000 Data Views User Guide chapter on
Dynamic Views for more information.
The Dynamic View for an object type includes a column that displays the Time Zone in which the object resides. This can
be useful in determining when an Event or Trigger is activated for an object in a different Time Zone than the C•CURE
90000 Server.
If you right-click a row in the Dynamic View, a context menu is displayed. This menu contains a number of standard
selections, as well as selections that are specific for different object types. See Using the Object List Context Menu in
the C•CURE 9000 Getting Started Guide for more information about the object context menu.
The context menu for iSTAR, apC, ASSA ABLOY, Connected Program readers allows you to select one or more readers
and Add or Remove Cards formats. See Add or Remove Reader Card Formats on Page 33 for more information.
The context menu actions are equivalent to opening each of the selected readers and adding/removing the card format
from each reader.
The limits for card formats allowed for apC (8 per reader) and iSTAR (10 per reader) are enforced when using these menu
actions.
If the selected Card Formats cannot be added or removed from the selected readers, the confirmation dialog box for the
Add/Remove displays "Already has card format" or or "Nothing to remove...". Errors that occur are shown in the
confirmation dialog box as well.
Example:
If you select iSTAR Reader, the Dynamic View displays multiple types of iSTAR Reader. If you select
iSTAR Aperio Reader, only that type of reader is displayed.
2. Select one or more readers from the list (you can use multiple selection keystrokes such as CTRL+Left-click and
SHIFT+Left-click to select more than one reader).
3. Right-click the selected readers to display the context menu.
4. Select Add Card Format or Remove Card Format from the menu.
5. The Card Format Name Selection dialog box appears. Select ( ) each Card Format that you want to add or remove
from the readers, then click OK.
6. If you added readers, a confirmation dialog box appears, showing the formats added:
7. If you removed readers, a confirmation dialog box appears, show the formats removed:
Some objects cannot be moved to another partition via drag and drop. For example, you cannot move an
NOTE iSTAR Controller to a different Partition via drag and drop, nor can you move a non-partitionable object.
Also, you cannot move an iSTAR Cluster to a different Partition if the Cluster is Enabled.
To determine if you can drag and drop an object, click on the object and then drag to the right with the mouse. If the
cursor appears, you can drag and drop the object. If you try to drop the object in an invalid location, the object instead
remains in its original location. For example, if you tried to drop an apC Comm Port in an iSTAR Cluster, the object is not
be moved, and an error message “Invalid Hardware Folder” appears.
3. Drag to the right with the mouse. The drag and drop cursor appears. (If it does not appear, you cannot drag and drop
the object.)
4. Drag the object to the location you want and release the mouse button. If you have chosen a valid location for the
object, it then appears in the new location.
Example
If you drag an apC Controller to a different Hardware Folder, the apC and all its child objects are moved to that
Hardware Folder.
Figure 2 on Page 36 shows the Groups tab for an iSTAR Input, which is typical for a Hardware device.
Figure 2: Typical iSTAR Group Tab
Hardware Groups Tab Definitions on Page 36 provides definitions for the fields and buttons on an iSTAR Device Group
tab.
Group Click to enable Grouping of the list. You can drag a column heading to the area labeled Drag columns to
group by here to group the list by that heading.
Filter Click to display the filter bar. See the C•CURE 9000 Data Views Guide for more information about filtering
a Dynamic View list.
Name This column lists the names of the Groups of which this device is a member.
Description This column lists the descriptions of the Groups of which this device is a member.
Hardware Folders
You can create additional Hardware Folders if you need to organize the Controllers and access hardware into separate
folders.
When you create a new Partition, a new Hardware Folder is automatically created to contain objects that reside in that
Partition.
A Hardware Folder pane displays a tree structure that shows how you have configured the hardware on the C•CURE 9000
system. For example, the hardware tree shows you which readers, inputs, and outputs are configured for each controller.
You can use the Hardware Tree to navigate to hardware components you want to view or edit, or to create new hardware
components, such as a reader you want to add to a controller.
For iSTAR controllers, a cluster object encompasses a system of one or more iSTAR controllers, determining
communications between individual controllers. To configure an iSTAR controller in the
C•CURE 9000 system, you must first create a cluster. Each cluster is configured as either Non-encrypted (iSTAR
Classic/Pro and Ultra) or Encrypted (iSTAR eX/Edge and Ultra) controllers. The cluster must have a controller that is the
primary communication path to the host and may have an optional secondary communication path. The secondary
communication path can be set to the same controller as the primary path.
In the instance of apC controllers, a communications port must be set up before these controllers and their dependent
objects can be configured.
Elevators are similar to doors, but have many exit points which are determined by the floor objects. Floors are created
independently but are added into the system through the selection of elevator buttons. Elevators also require readers,
inputs, and outputs. The inputs are used to determine at which floor the cardholder exited and the outputs are used to
control the elevator buttons.
Elevators (configured on iSTAR or apC controllers) have not been evaluated by UL.
NOTE
Doors which are configured as part of an apC or iSTAR controller have properties that are unique to each controller,
whereas a Door object is a base class that recognizes only those properties which are common to all controllers.
Accordingly, door objects are created last because each door object requires the controller-specific dependent objects to
exist for the door. Doors typically require readers, inputs and outputs. The inputs are used for door state monitors and exit
devices. The outputs are used for locks and automatic door openers.
Example:
C•CURE 9000 dependent object hierarchy examples:
In a template, you can fill in field values that will have the same values for all Hardware Folders, and then use the template
when you are creating new Hardware Folders.
3. Click on the name of the Hardware Folder Template you wish to use as the basis for the new Hardware Folder.
4. Type the name for the new folder into the Name field.
5. Optionally type a description for the new folder into the Description field.
6. Click Save and Close to save the new folder.
7. Right-click on Hardware and select Refresh Tree from the context menu. The Hardware Tree is updated to display
the new folder.
Templates
The C•CURE 9000 Hardware pane supports the concept of Templates for almost all objects in the Hardware Tree. A
Template is a re-usable object you can create and configure with settings that you would like to use when creating other
objects. For example, if all of the iSTAR Readers are the same reader type, using the same card format, you could create a
Reader Template that contained those settings, and apply that Template to any iSTAR Reader object that you create, to
make Reader configuration faster and more consistent. The Template objects you create do not appear in the Hardware
Tree, but they are available to be applied when you create an object of the same type as the Template.
The following topics provide more information about using the Hardware Templates.
■ Creating a Template on Page 41
■ Editing a Template on Page 42
■ Creating an Object from a Template on Page 43
■ Using Templates for Controller Inputs, Outputs, and Readers on Page 44
■ Viewing a List of Templates on Page 45
■ Deleting a Template on Page 45
Creating a Template
To create a new Template for an object, it is necessary to create an instance of the parent object for the object so that the
object type for the Template appears in the Hardware Tree. For example, to create a Template for the iSTAR eX Controller
object type, you need to create an iSTAR Cluster that can contain iSTAR eX Controllers first, then create the iSTAR eX
Controller Template.
To Create a Template
1. In the Navigation pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Navigate to the Hardware folder that contains the object type for which you want to create a new Template.
Example:
If you want to create a Template for an iSTAR eX Controller, navigate to a folder that contains an iSTAR Cluster
for iSTAR eX Controllers.
3. Select the parent object type (in this case, iSTAR Cluster) and right-click to display the context menu.
4. Select the object type for the Template from the context menu, then select New Template. See the example in Figure
3 on Page 42.
The new template appears under ---- Templates in that object type’s context menu drop-down list in the Hardware tree. For
example, in Figure 3 on Page 42, an iSTAR Controller Template named controller template appears in the context menu.
Editing a Template
If you have created a Template and need to make changes to it, you need to locate the Template to edit it. Because you
cannot view Templates in the Hardware Tree, and most default Dynamic Views do not list Templates, you may need to
create a new Dynamic View that shows the Templates you have created.
This section will use Inputs as an example, and show you how to create a Dynamic View that lists the Input Templates
along with the Controller Inputs.
Note that you can create a Dynamic View that shows only apC Inputs or iSTAR Inputs by choosing that object type, or you
can create a View that lists all Input (or Door or Reader) objects, then filter that view to show only the Inputs (or Doors or
Readers) of a particular type.
Example:
Inputs Dynamic View (with Templates)
4. Type a description of the view in the Description field.
5. Click in the View Type field. A dialog box appears listing the object types you can choose for your Dynamic View.
6. Click on ‘Click here to filter data’ and type the first letter of the name of the object type for which you wish to create a
Dynamic View. The list of object types is filtered to show only the types that begin with that letter.
Example:
To create a list of Inputs, type ‘i’ then click on Input.
7. Click Add to add a column to the Dynamic View.
8. Click in Column Property, then click Name to add the Name Property to display in the column.
9. Click Add to add a column to the Dynamic View.
10. Click in Column Property, then click Template to add the Template Property to display in the column.
11. You can click Add again to add more columns as needed.
12. Click Save and Close to save the Dynamic View.
13. In the Data Views pane, click to display a list of your Dynamic Views.
14. Double-click on the Dynamic View you just created. When it appears, it will list all of the objects of the object type you
specified, and the Template column identifies which objects are Templates.
15. Find the Template you wish to edit, and double-click it to open the editor to edit the Template.
16. When you have completed making changes to the Template, click Save and Close to save your changes.
Typically, you create these objects from a tab within the Controller editor. The tab where you create such an object
contains a table that includes a Template column for you to identify a Template to use as a basis for the objects you create.
Example:
The apC Controller editor has tabs for Inputs, Outputs, and Readers. On each of these tabs, there is a Template
column that lets you select a Template to use for creating new objects.
Figure 4 on Page 44 shows an example of an apC Outputs tab with an apC Template selected in the Template
column.
Figure 4: apC Outputs Template
By default, when you select a Template for one object in the list, the same Template is added as the basis for each object.
You can use more than one Template by configuring the objects for which you want to use one Template, then choosing
one or more different Templates for the remaining objects.
In the apC Editor, click the Outputs tab to configure Outputs on this apC.
3. To specify a Template for an object you want to configure, click in the Template column of an object that is not yet
configured (Configured column value is ).
4. Click to select a Template. A dialog box opens listing the available Templates. See Figure 4 on Page 44 for an
example.
5. Click on a Template in the list to select it. That Template is added to every object in the table that is not already
configured.
6. Select the Configured column for each object you want to configure with the selected Template.
7. If you want to select a different Template for any of the remaining objects in the table that you have not yet configured
(Configured column value is ):
a. Click in the Template column of that object, then click to select a Template. A dialog box opens listing the
available Templates.
b. Click on a Template in the list to select it. That Template is added to every object in the table that is not already
configured.
c. Select the Configured column for each object you want to configure with the selected Template.
8. Repeat Step 7 for any additional objects for which you want to choose a different Template.
9. To edit any of the objects, click in the Edit column for that object. The editor for that object opens. The fields that
were configured in the Template are already configured in the object you are editing.
10. When you have completed configuring an object from the Template, click Save and Close in the object editor to save
the object.
11. Click Save and Close in the Controller editor to save the your changes to the Controller.
Deleting a Template
You can delete a template that you have created by using the right-click context menu in a Dynamic View.
To Delete a Template
1. In the Navigation pane, select the type of object you want to delete from the drop-down list. (For example, in the
Hardware pane, choose apC Comm Port from the drop-down list.)
2. Click the Search pane.
3. Select the Template check box
4. Click to display a list of the objects that includes the Templates you have defined.
5. Select the Template(s) from the list that you wish to delete.
6. Right-click on a selected Template to bring up the context menu for the object.
7. Select Delete from the menu to delete the Template.
Typically the Dynamic View for an object type does not include Template objects. You can use the Template check box to
cause the Dynamic View to list all the Templates you have created.
1. In the Navigation pane, select the type of object you wish to view from the drop-down list. (For example, in the
Hardware pane, choose apC Comm Port from the drop-down list.)
2. Click the Search pane.
3. Select the Template check box
4. Click to display a list of the objects that includes the Templates you have defined.
Example:
Create the new Clusters and Controllers with -Bldg appended to all of the objects. While Copying and Pasting you can
use Search and Replace to change -BLDG-Copy-datetime to -BLDG-A. See Using Search and Replace on Page
50.
The Export and Import of Clusters does not include all the doors, elevators and events (configured via
NOTE triggers). Copy & Paste includes all of those objects.
When an iSTAR Cluster is selected and Copy & Paste is used, the following objects that belong to that cluster are copied
and pasted:
■ All configured Controllers plus the following components of each Controller:
• Boards (all the boards including GCM, ACMs, Aperio Hubs or Schlage PIMs, etc.)
• Inputs (including I/8s, I/8-CSIs)
• Outputs (including R/8s)
• Readers (all types)
• Doors
• Elevators
• Triggers, including their associated Events and actions
When an iSTAR Controller is selected and Copy & Paste is used, the following objects that belong to that Controller are
copied and pasted:
■ Boards (all the boards including GCM, ACMs, Aperio Hubs or Schlage PIMs, etc.)
■ Inputs (including I/8s, I/8-CSIs)
■ Outputs (including R/8s)
■ Readers (all types)
■ Doors
■ Elevators
■ Triggers, including their associated Events and actions
Privileges
To use the Copy & Paste, Copy To, Copy From and Rename features, you must be an Administrator or an operator that
has a Privilege with those Permissions granted for iSTAR Controller and iSTAR Cluster.
The iSTAR Controller and iSTAR Cluster Privilege Permission features are located in the Privileges dialog box
Defaults tab. Click on the Hardware>Controllers>iSTAR. Locate the iSTAR Controller and iSTAR Cluster for the
Permissions for the Privilege.
See the C•CURE 9000 Software Configuration Guide 'Privileges' chapter for more information.
You can perform the following tasks using Copy & Paste:
■ Copying and Pasting on the Same System on Page 48
■ Copying to a Mapped Drive or Another System Using a Flash Drive on Page 51
■ Copying and Pasting from Partition to Partition on Page 55
The same procedures can be used to copy and paste individual Controller configurations.
NOTE
■ A Cluster, plus all the objects within that Cluster with the same names as the existing ones with -Copy [date-time]
appended to their names.
■ A Controller with -Copy [date-time] appended to its name, plus all the objects within that Controller.
Example:
For a Cluster named Cluster5, the new cluster's name will be Cluster5-Copy [date-time], and if the Cluster has a
Controller named Controller7, the new name will be Controller7-Copy [date-time].
For a Controller named Controller6, the new name will be Controller6-Copy [date-time].
The Search and Replace dialog box, as shown in Figure 6 on Page 50, appears.
If the Copy & Paste operation is stopped before it completes, the entire operation is
NOTE canceled.
2. Click OK. If you selected to search and replace, the system searches for the string and performs the replace while
copying the Cluster or Controller.
The Copying Status Window, shown in Figure 7 on Page 50, appears. The time required depends on the complexity
of the Cluster or Controller. The time is 10 to 60 seconds for most Clusters.
Figure 7: Copying Status Window
3. Click OK when the object is displayed as copied, as shown in Copying Status Window on Page 50.
Figure 8: Copying Status Window - Complete
When the copy is complete, shown side-by-side in Figure 9 on Page 51, all Readers, Inputs, Outputs, Doors, etc. have
-Copy [date-time] appended to their names.
Figure 9: Hardware Tree - Copy Complete
3. Click Save.
The Copy To Status Window, shown in Figure 12 on Page 53, appears.
Figure 12: Copy To Status Window
The Search and Replace dialog box appears. For information about Search and Replace, see Using Search and
Replace on Page 50
8. Click OK in the Search and Replace dialog box. If you selected to search and replace, the system searches for the
string and performs the replace while copying the objects.
The Pasting Status Window, shown in Figure 14 on Page 54, appears.
Figure 14: Pasting Status Window
9. Click OK in the Pasting Status Window when the object is displayed as pasted.
The copied Cluster appears under the simulated folder in the Hardware tree on the system.
3. Select the other partition where you want to copy the object.
4. Right-click on the Hardware folder in the partition and select iSTAR Cluster>Paste from, as shown in Figure 16 on
Page 56Figure 16 on Page 56
The following procedure renames -Copy [date-time] that was appended to the end of a Cluster and its objects during
Copy & Paste to -Bldg-C.
3. Enter the new name in the Replace with field (in this example it's -Bldg-C).
4. Optional selections
• Click on the Match case check box to match the case entered.
• Click in the Ignore Trigger Targets check box to ignore Trigger target events.
Use caution if renaming original Events. The Events may be linked to other objects. Use the
Show Association feature to determine if they are. See the C•CURE 9000 Getting Started
Guide for information about using Show Association.
5. Click OK.
An informational dialog box appears displaying all the objects that were modified with the new name.
6. Click OK.
7. Verify that the rename changes are complete. Click on the tabs in Renaming dialog box.
Because Ignore Trigger Targets was selected in the Search and Replace dialog box, the
NOTE original Trigger Target Events were not renamed, but another copy of the Events exist with the
-Copy [date-time] appended to the end.
Rename Results
The next series of graphics illustrate the effect of the Rename operation.
Figure 20: Controller Tab and Input Tab
Use caution if renaming original Events. The Events may be linked to other objects. Use the
Show Association feature to determine if they are. See the C•CURE 9000 Getting Started
Guide for information about using Show Association.
In this chapter:
Placing an object into Maintenance Mode does not prevent actions from occurring. For example, if an event assigned to an
intrusion zone in Maintenance Mode activates an output that turns on the building-wide evacuation alarm, the activation of
the output will still occur.
Arming and disarming of inputs and events do not affect what is reported when the object is activated. In other words,
arming of an event by an event assigned to a Maintenance Mode intrusion zone will be reported as activity.
Maintenance Mode is only reported in Journal messages when an object is tagged Maintenance Mode. When the object is
taken out of Maintenance Mode it is not reported in a Journal message.
Operator Privilege and Application Layout Filtering assignments determine whether or not an object in Maintenance Mode
is viewable as being in Maintenance Mode on the Monitoring Station. Only Monitoring Station operators with the correct
privilege and Application Layout Filtering can view objects in Maintenance Mode.
The following procedure describes how to configure the privilege to include Maintenance Mode.
The following procedure describes how to configure the application layout to allow Maintenance Mode filtering. The
Operator must have the correct privileges to use filtering. See Configuring Privileges to Turn Maintenance Mode On and
Off on Page 67.
See the C•CURE 9000 Data Views Guide for more information about configuring the application layout.
iSTAR Cluster
Putting Objects (Doors, Readers, Events, Elevators, etc.) into Maintenance Mode
See Configuring Privileges to Turn Maintenance Mode On and Off on Page 67 and Configuring the Application Layout for
Maintenance Mode Filtering on Page 67
This chapter explains how to configure dial up for use with the iSTAR Pro and the iSTAR Ultra SE (Pro Mode only).
In this chapter
iSTAR Dialup 72
iSTAR Dialup Configuration Sequence 73
Configuring the iSTAR Comm Port 74
Configuring the Host Modem 77
Creating a Cluster for Dialup 80
iSTAR Dialup
Dialup enables you to connect the C•CURE 9000 to the iSTAR Pro and iSTAR Ultra SE (in Pro Mode with a USB-based
modem card) controllers at remote locations using modems and standard telephone lines.
The C•CURE host and iSTAR phone line/modem connection is based primarily on Windows standard telephony
communications and Routing and Remote Access Service (RRAS).
■ The lowest level of the communications, which deals with modem states, is handled by the Microsoft Windows
Telephony Application Programming Interface (TAPI). TAPI supports the use of any type of standard modem on the
host.
■ The higher level of the communications, which deals with the transmission of C•CURE relevant data, is handled by
Microsoft RRAS. RRAS treats dial-up connections as if they were network connections. Consequently, the C•CURE
host views the connection established between the iSTAR and itself via a phone line and modem as any other network
connection.
■ Serial port-based dialup modems and USB port based modems are supported.
Dialup Limitations
■ Dialup is only supported on Windows Server 2008 R2, 2012, and 2012 R2.
■ Dialup is not supported in configurations using redundancy.
■ Dialup can be used only as the primary connection method or the secondary communication method, not as both.
Example:
— Dialup is used as the primary communication method and there is no secondary communication method.
— TCP/IP is used as the primary communication method and Dialup is used as the secondary communication
method.
■ A cluster used for dialup can only contain one iSTAR controller.
■ Fast Personnel download is not supported.
■ Dialup is not supported on a separate RRAS server.
1 Configure the Comm ports to which the host modems are attached in C•CURE 9000 Configuring the iSTAR Comm
using the iSTAR Comm Port Editor. Port on Page 74
2 Configure the host modems in C•CURE 9000 using the Host Modem editor. Configuring the Host Modem
on Page 77
3 Create an iSTAR Cluster. Click the Dialup tab to configure dialup settings. Creating a Cluster for Dialup
on Page 80
6 Configure/Grant Privileges for the iSTAR Controller dialup permissions using the C•CURE 9000 Software
Privilege editor. Configuration Guide
7 Configure Events to download to the controller and select the dial up conditions using the C•CURE 9000 Software
Event editor. Configuration Guide
Select the Dialup settings from the Event Editor General tab.
8 Configure the System Variables Dialup settings (dial-up user name, password, domain, C•CURE 9000 System
grace seconds, cycle seconds) to use RRAS. Maintenance Guide
See Table 4 on Page 74 for descriptions of the fields on the Comm Port editor General Tab.
Field Description
Name The Name field will reflect the Comm Port you select.
Description Enter a textual comment about the controller, such as its location or purpose. This text is for information only.
Field Description
Enabled This setting determines whether or not the iSTAR Comm Port is able to provide communication between the iSTAR Controller
and the C•CURE 9000 Server. Select Enabled to set the Comm Port online. To take the Comm Port offline, clear the Enabled
selection.
If the iSTAR Comm Port is currently in use by iSTAR controllers, you must disable all the controllers before you attempt to take the
Comm Port offline. If any iSTAR controllers are enabled when you attempt to take the iSTAR Comm Port offline, an error
message is displayed - "Port cannot be disabled with enabled controllers. Please disable controllers first. When the controllers are
re-enabled they will do a full personnel download."
The message explains that when you re-enable the iSTAR Comm Port and then re-enable the iSTAR controllers, each controller
will perform a full personnel download.
NOTE: Fast Personnel Download is not supported.
Maintenance Click to put the iSTAR Comm Port into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Communications Type
Port Settings
Port Timeout The Port Timeout Delay Time is the extra interval that the host waits for a response from the iSTAR panel after sending a
Delay Time message to the panel. If the host does not receive a response in the specified time, the host re-transmits the message or declares
(1/10 sec) a communications failure. This field allows you to set the timeout delay for all panels that use a specific port.
Software House recommends that you set this period to 20 (2 seconds). However, if you require additional delay time because
iSTAR controllers run on a Digiboard, Equinox board, or over a network, you may need to increase this value. Keep this value as
small as possible, or system performance may be affected. If your panel goes into communications failure often, try setting this
value between 30 (3 seconds) and 50 (5 seconds).
Range: 0 through 99.
Default: 0.
Comm Port Select the Communications Serial Port from the drop-down list. The Name field will reflect the port number that you select. The
range is COM1 to COM256.
5. You can set a Port Timeout Delay Time in tenths of a second units by entering it in the field or by using the up/down
arrows.
6. Select the Comm Port from the drop-down list.
7. Select the Enabled check box to put the Comm Port online after you have completed the configuration procedure.
8. Click Save and Close.
9. Go to Configuring the Host Modem on Page 77.
The Host Modem dialog box definitions are described in Table 5 on Page 77.
Figure 28: Host Modem Dialog Box
Field Description
Enabled Select Enabled to set the host modem online. To take the host modem offline, clear the
Enabled selection.
Field Description
Maintenance Mode Click to put the iSTAR Comm Port into Maintenance Mode. See Chapter 3: Maintenance
Mode for more information.
Partition This read-only field identifies the Partition in which this Controller resides.
Communication Port
Click to open the Name Selection dialog to select the iSTAR Comm Port.
NOTE: The iSTAR communication ports must already be configured. See Configuring
the iSTAR Comm Port on Page 74
Phone numbers that Displays the list of phone numbers that reach this host modem. Use the buttons to the
reach this modem right of the list to modify the numbers in the list.
• The phone number can be up to 35 characters long.
• Hyphens, parentheses, and spaces are not allowed in phone numbers.
• If Dial out only is selected in the Direction box, this box and the Add Dial In, and
Remove buttons are unavailable.
6. Click in the Port field to open the Name selection dialog box and click the iSTAR Comm Port you want to use.
7. Select the dial Direction: Dial out only, Dial in only, or Dial in and Dial out.
8. In the Phone numbers that reach this modem box:
a. Click Add Dial In to add a new row.
b. Click in the new row and enter a phone number.
c. Repeat step a and step b for each phone number you want to add.
The Dialup Configuration tab in the iSTAR Cluster Editor dialog box, shown in Figure 29 on Page 80, lets you select pre-
configured host modems and specify other dial-up configurations.
This tab is only available for unencrypted clusters and for use with the iSTAR Pro or iSTAR Ultra SE in Pro Mode.
■ You can only have one controller in a cluster that uses dialup.
NOTE
■ To enable a cluster, a dial-in and a dial-out phone number must be configured.
■ Alternate master is not supported.
Field Description
Dial In Tab
Host Modem/Host Click to Add to open the Name Selection dialog box host to select the host modems and host phone numbers that the
Phone Number host can use to contact this controller.
• The host calls the modems in the order that they are listed.
• A modem/phone combination can be listed more than once, but you cannot enter more than 8 modem/phone
combinations.
Number of times to try Specify the number of times the controller dials each telephone number in the list when the controller cannot contact
connections the host.
Example:
If 2 is entered in this field, the controller dials each telephone number in the list two times. If the requisite connection
attempts with all the phone numbers in the list fail, the controller is considered to be in Comm fail.The system will
use the Retry interval during communication failure value to set the timing of communication attempts.
Default: 2
Range: 0-99
Host Modems/ Remote Click Add to add host modems and remote phone numbers that the host can use to dial out.
Phone Number • The host calls the modems in the order that they are listed.
• A modem/phone combination can be listed more than once, but you cannot enter more than 8 modem/phone
combinations.
Automatically initiate Specify the time to automatically download configuration changes to the dial-up controller. Then, click on the check box
connection when to enable the download time.
configuration changes Example:
after hh:mm
Cardholder additions and deletions.
NOTE:
- Leaving this unselected means that configuration changes will not be downloaded until the next normal
connection with the controller.
- Selected with a time of 00.00 indicates immediate download.
- Changes to the controller, such as change to an object’s name or description, do not cause a download to the
controller.
Range: 0 to 23 hours 59 minutes.
Periodic Tab
NOTE: To make changes to the Periodic tab you must clear the Enabled, click Save and Close and then reopen the Cluster editor.
Redial interval during Specify the interval of time the host waits to redial the controller when there is a communication failure. Enter the time in
communications failure hh:mm format.
• Default: 30 minutes.
• Range: 0 minutes to 24 hours 59 minutes.
Field Description
Schedule
Click to open the Name Selection dialog box to select a non-recurring schedule for periodic dialing, and
downloading configuration changes and cardholder information.
NOTE: If the predefined 'Always' schedule is selected, the controller will only use the time interval specified by Dial
interval outside of schedule.The Dial interval during schedule setting will be ignored.
Dial interval during Specify the frequency that the host dials the controller when the time specification is in effect.
schedule • Enter the time in hh:mm format.
• Range: 0 to 24:00 hours.
Dial interval outside Specify the frequency that the host dials the controller when the time specification is not in effect.
schedule • Enter the time in hh:mm format.
• Range: 0 to 24:00 hours.
This chapter explains how to configure iSTAR Clusters in the C•CURE 9000 system.
In this chapter
The Alternate Master capability cannot be configured in newly-created iSTAR clusters in version 2.20 or
NOTE later.
iSTAR Clusters that already have an Alternate Master, when upgraded to version 2.20 or later, retain the
Alternate Master, but if the cluster is edited and the Alternate Master is removed, this change will
permanently remove the ability to configure an Alternate Master for this cluster.
See the iSTAR Cluster Communications Tab on Page 99 for more information.
Communications among iSTAR controllers provide distributed functionality at the controller level that is not typically
available on security management systems.
A cluster can only contain controllers that support compatible methods of encryption (or do not use encryption).
■ You can create a Non-Encrypted Cluster containing iSTAR Classic, iSTAR Pro, or iSTAR Ultra Controllers.
■ You can create an Encrypted Cluster containing iSTAR eX, iSTAR Edge, or iSTAR Ultra Controllers.
Previously, clusters were categorized by Controller Type rather than Encryption Setting. The
NOTE composition of clusters and the models of controllers they contain has not changed. When C•CURE 9000
is upgraded, cluster types are changed to reflect Encryption Settings, but existing controllers remain in
the same clusters.
Master controllers use the primary or secondary communications path to communicate with the C•CURE System host.
Establishing and maintaining a connection with the host involves the following administrative actions through the use of
iSTAR Clusters:
■ Establishing connections via the primary communications path. You set up a primary communications path for a
cluster when configuring controllers and clusters.
■ Downloading cardholder and configuration information from the host to the controller.
■ Maintaining communications via the primary communications path. If a communications failure occurs on the primary
communications path, controllers can re-establish communications via a secondary communications path.
The Master is the one controller in a cluster that is responsible for passing messages between the host and cluster
members. Cluster members do not communicate with the host directly; they communicate with the host through the
master. Connections are established in the following bottom-to-top order:
■ The Master is responsible for establishing a connection with the host. The host does not establish a connection with
the master.
■ Cluster Members are responsible for establishing connections with the master. The master never tries to establish a
connection with a cluster member, as shown in Figure 31 on Page 87.
The Connection type is how the master connects to the host: TCP/IP over Ethernet. Cluster members are connected to
the master via Ethernet only. Figure 32 on Page 87 shows the Primary Communications Path for Cluster Member A. The
master/host connection type is TCP/IP over Ethernet.
Figure 32: Primary Communications Path
Connections are established in a bottom-to-top order. Thus, clusters members are responsible for establishing
connections with the master, and the master is responsible for establishing a connection with the host.
The C•CURE 9000 Server downloads cardholder and configuration information to the controller under the
NOTE following conditions:
■ Initial configuration
■ Each time the controller is powered on
■ Each time the cluster is taken offline/online
Changes to personnel, clearances, inputs, outputs, readers, and events are immediately downloaded.
Maintaining Communications
Although a communications link may be open between two devices, long periods of time can exist when devices do not
communicate because of low system activity. In the absence of this type of communications, devices send “keep-alive”
messages, called Connection Verification messages, to verify that connections are alive.
Example:
The master and host send these messages to each other to confirm that the connection between them is open. If the
host does not receive a connection verification message from the master in a specified amount of time, the host
closes the communications link with the master and waits for a connection attempt from the cluster. When the master
does not receive a connection verification message from the host in the specified amount of time, it also declares a
communications failure for the primary communications path and then notifies its cluster members of the
communications failure. At this time, cluster communications revert to the secondary communications path.
Use the Communications and Cluster tabs in the C•CURE 9000 Administration Application, iSTAR Cluster dialog box,
to configure connection verification messages for the master, host and cluster members. See Configuring iSTAR Clusters
on Page 91 for more information.
While communicating via the secondary path, the cluster attempts to re-establish communications with the host on the
primary communications path. When a connection is re-established on the primary path, communications revert to the
primary path and the communications link on the secondary path is closed.
Use the Communications tab in the Cluster dialog box in the C•CURE 9000 Administration Application to configure the
secondary communications path (see iSTAR Cluster Communications Tab on Page 99).
Figure 33 on Page 89 shows an example of a secondary communications path on the host using an Ethernet connection
and a secondary communications path on another network card, using an Ethernet connection.
Figure 33: Primary and Secondary Communications Path to Host
Distributed cluster management lets a controller perform many actions locally and share information with other cluster
members even when the controller is not communicating with the host, during a communications failure for example.
Cluster members communicate with each other through the master. Although a communications failure
NOTE with the host may not affect cluster communications, a communications failure with the master can cause
communications problems in the cluster.
Unassigned Folder
The Unassigned folder is a repository for iSTAR controllers that have been configured for an iSTAR cluster, in an existing
partition, but which have been removed from the iSTAR cluster, or the cluster has been deleted. Such controllers will be
listed under the Unassigned folder until they are reassigned to another iSTAR cluster or deleted.
This field becomes Read-only once you add iSTAR controllers to the Cluster and save it, because
NOTE changing this setting while there are controllers in the cluster would cause problems.
If you need to change this setting, you must remove all controllers from the Cluster, change the
Encryption Settings on the Cluster Encryption tab (see iSTAR Cluster Encryption Tab on Page 108),
then add controllers of the appropriate type.
6. Click Save and Close to save the Cluster. The new iSTAR Cluster icon displays in the tree, one level below the folder
that you selected.
Example
If you want all of your iSTAR Clusters to use 60 seconds instead of the default 10 seconds for the Connection to Host
Interval, you can create an iSTAR Cluster Template with Connection to Host Interval set to 60 seconds, and every
iSTAR Cluster you create from this Template will inherit that setting.
Alternatively, select iSTAR Cluster in the Hardware pane drop-down list, click the down-arrow next to the New
button, then select iSTAR Cluster>New Template from the menu.
The iSTAR Cluster Editor opens a new Template that you can configure and save.
4. Enter a unique name for the Template in the Name field (required) and type a textual description for the Template in the
Description field (optional).
5. Select the Encryption Setting for the Cluster Template. Only controllers of the types supported by this setting can
subsequently be added to Clusters created from this Template. (This field becomes read-only after you save the
Cluster Template).
6. Navigate to the Communications, Cluster, Miscellaneous, Encryption, Triggers, and State Images tabs and configure
any settings that you would like to be included in your Template. See iSTAR Cluster Editor on Page 95 for more
information about the iSTAR Cluster Editor tabs.
7. Click Save and Close. The Cluster Template is saved with your settings. You can now use the Template as the basis
of new iSTAR Clusters you subsequently create.
A Cluster Template is not saved inside of a Hardware folder, and it is not visible in the Hardware tree. To
NOTE
edit a Cluster Template, select iSTAR Cluster from the Hardware drop-down list and click to display
a Dynamic View listing all iSTAR Clusters, including Cluster Templates. Double-click on a Cluster
Template in the Dynamic View to edit it.
The iSTAR Cluster Editor and you can edit the new Cluster.
4. Enter a unique name for the Cluster in the Name field (required) and type a textual description for the Cluster in the
Description field (optional).
5. Select the Encryption Setting for the Cluster Template. Only controllers of the types supported by this setting can
subsequently be added to Clusters created from this Template. (This field becomes read-only after you save the
Cluster Template).
6. Navigate to the Communications, Cluster, Miscellaneous, Encryption, Triggers, and State Images tabs and configure
any settings that you would like to be included in your Cluster. See iSTAR Cluster Editor on Page 95 for more
information about the iSTAR Cluster Editor tabs.
7. Click Save and Close. The iSTAR Cluster is saved with your settings.
See iSTAR Cluster General Tab Definitions on Page 98 for definitions of the fields and buttons on the iSTAR Cluster
If the Cluster is Enabled, you cannot remove a Controller that is selected on the Communications tab as either the
controller having primary communications with the host (C•CURE 9000 Server) or the controller having secondary
communications with the host. The Remove button becomes unavailable if you select such a controller.
3. Click Remove. The Controllers you selected are deleted from the Controller(s) list of this Cluster.
4. Click Save and Close to save your changes. The Controllers you removed from this Cluster now appear in the
Unassigned folder in the Hardware tree, and can be re-assigned to another Cluster with the same Encryption Setting.
Field/Button Description
Name Enter a name (up to 100 characters long) of the iSTAR Cluster that you are configuring.
Description Type a description of the iSTAR Cluster that you are configuring.
Maintenance Click to put the Cluster or iSTARs and/or their components into Maintenance Mode. See Chapter 3: Maintenance
Mode Mode for more information.
Partition This read-only field identifies the Partition in which this iSTAR Cluster resides.
Select the Encryption Setting for the Cluster Template. Only controllers of the types supported by this setting can
subsequently be added to Clusters created from this Template. (This field becomes read-only after you save the
Cluster Template). you want to change the Partition of a Cluster, see Using Drag and Drop in the Hardware Tree
on Page 35.
Encryption A read-only field displaying the Encryption Setting for the Cluster.
Setting
Controllers
Add To add an iSTAR Controller to your Cluster, click Add to display the iSTAR Controller selection dialog box. Select
one or more controllers and click OK to add it to the iSTAR Cluster.
Remove To remove an iSTAR Controller from your Cluster, select the iSTAR Controller you want to remove in the list, then
click Remove.
If you are using iSTAR Pro dialup, the cluster must be configured for dialup communication.
For a cluster that existed prior to version 2.20, you can have one controller configured for the Primary
NOTE communications path as a Master controller, and a second, different, controller configured for the
Secondary communications path as an Alternate Master.
However, if you remove the Alternate Master from the cluster, you will no longer be able to configure an
Alternate Master for the cluster. A message box appears when you change Controller having secondary
communications with host to None, informing you that the change will remove the Alternate Master.
For a new cluster created in version 2.20 or later, you cannot configure an Alternate Master. If you
configure both a Primary and Secondary communications path, you must use the same controller, which
must have two onboard Ethernet Adapters.
Dialup can be used only as the primary connection method or the secondary communication method, not
NOTE as both.
Example:
■ Dialup is used as the primary communication method and there is no secondary communication
method.
■ TCP/IP is used as the primary communication method and Dialup is used as the secondary
communication method.
Number of Failed Attempts Before Connection Fails on Page 102 explains how to configure the cluster's controllers to
attempt to connect to the cluster, and resolve communications failures.
2. Controllers having primary/secondary communication with host allows you to select the controller in the cluster
that has primary or secondary communications with the host (C•CURE 9000 server). Choose a controller using the
drop-down selection.
3. Method of communication between host and controller allows a selection of the communication type designated
for the iSTAR controller that communicates with the host. Choose the connection type of Onboard Ethernet or
Dialup (iSTAR Pro or iSTAR Ultra Pro Mode only) using the drop-down selection.
4. In the Connection to Host Interval entry field, specify the number of seconds that a controller waits between
attempts to connect to the host.
UL requires a maximum of 200 seconds supervision on the Communications link between the protected premise
equipment and the central station.
5. In the Number of failed attempts before connection fails field, specify the number of attempts that a controller
makes to first connect to the host before the controller is declared to be in communications failure. See Number of
Failed Attempts Before Connection Fails on Page 102 for more information.
6. In the Reconnect Interval after connection failure field, specify the number of seconds that controllers wait
between attempts to re-connect to the host. This field sets the rate at which controllers attempt to reconnect or
connect to the host after a communications failure occurs between the host and the controller. The default interval is
40 seconds. The maximum value is 9999 seconds and the minimum is 1 second.
7. In the Connection Inactivity Interval field, specify the number of seconds that a controller waits between attempts to
connect to the host. The default interval is 80 seconds. The possible values are between 15 and 80 seconds.
8. Navigate to the iSTAR Cluster - Cluster Tab on Page 103 or click Save and Close to save the cluster and begin
configuring iSTAR Controllers.
Table 8: iSTAR Cluster Communications Tab Definitions
Field Description
Controllers This field allows you to select the controller that has primary or secondary communications with the host. Choose a controller
having primary using the drop-down selection.
or secondary
communication
with host
Method of This field allows you to select the communication type designated for the iSTAR controllers, PCMCIA Ethernet, Onboard
communication Ethernet or Dialup (iSTAR Pro/iSTAR Ultra SE Pro Mode only).
between host
and controller
Connection to Specify the number of seconds that a controller waits between attempts to connect to the host. Use the Number of failed
Host Interval attempts before connection fails field in the Communications tab to specify the number of connection attempts a
[seconds] controller makes before a communications failure is declared for the controller. The maximum value is 9999 seconds and the
minimum is 1 second. The default value is 20 seconds.
Number of failed Specify the number of attempts that a controller makes to first connect to the host before the controller is declared to be in
attempts before communications failure. See Number of Failed Attempts Before Connection Fails on Page 102. The default value is 4
connection fails attempts.
Reconnect Specify the number of seconds that controllers wait between attempts to re-connect to the host. This field sets the rate at
Interval after which controllers attempt to reconnect or connect to the host after a communications failure occurs between the host and the
connection controller. The default interval is 40 seconds. The maximum value is 9999 seconds and the minimum is 1 second.
failure [seconds]
Connection Specify the number of seconds that a controller waits between attempts to connect to the host. The default interval is 80
Inactivity Interval seconds. The possible values are between 15 and 80 seconds.
[seconds]
If a connection is established, the controller and host use connection verification messages to maintain the connection.
If a connection is not made in the specified number of attempts, a communications failure is declared for the controller, and
the following connections are attempted:
■ If the secondary communications path uses an alternate host, the controller attempts to connect to the alternate host,
which passes the controller’s messages to the host. At the same time, the controller tries to re-establish a connection
with the host at the rate specified in the Reconnect Interval after connection failure field.
■ If the secondary communications path does not use an alternate host, the controller attempts to connect to the host
forever, or until a connection is established. The controller attempts to connect to the host at the rate specified in the
Reconnect Interval after connection failure field.
■ The controller broadcasts a request across its subnet for the host’s IP Address. The host responds to the request. If
the host does not respond in a set amount of time and the iSTAR Configuration Utility is configured for auto-response,
the utility responds to the controller. See the iSTAR eX Installation and Configuration Guide for information.
3. Enter the number of instances after which the primary controller transmits a connection failure in the Number of failed
attempts for controllers to declare a connection failure entry field. The range is from 1 to 99; the default value is 4.
4. Specify the number of seconds after which the primary controller attempts to reconnect after a connection failure in the
Reconnection Interval after connection failure entry field. The range is from 1 to 9999 seconds; the default value is
40 seconds.
5. Enter the number of seconds after which the primary controller transmits a connection failure if there is no message
while it is connected, in the Connection Inactivity Interval entry field. The range is from 15 to 80 seconds; the default
value is 80 seconds
6. Navigate to the Miscellaneous tab or Save and Close to save the cluster and begin configuring iSTAR Controllers.
2. In the Unacknowledged Messages box specify the maximum number of unacknowledged messages that are
allowed for each iSTAR Controller in the Maximum number of unacknowledged messages for each controller
field.
If you have a network with high latency, you may want to set this value to a higher number; if the network has low
latency, the default value (10) should be sufficient.
3. Navigate to the Antipassback tab or Save and Close to save the cluster and begin configuring iSTAR Controllers.
Modifying either of these options can only be done if the Cluster is not Enabled.
NOTE
You configure how Global Antipassback works during a communications failure through a system variable in the iSTAR
Driver section, "iSTAR Global Antipassback Communication Failure Mode". For more information, see the C•CURE 9000
System Maintenance Guide.
For iSTAR Cluster Areas, all Doors and Readers must be within the same iSTAR Cluster. Adjacent Areas can be on any
Cluster and can also be Cross-Cluster Areas.
The violation triggered when personnel enter a specified Area is called an entry violation. The violation triggered when
personnel exit a specified Area is an exit violation.
To ensure that personnel are always appropriately prevented from entering Lockout Areas, make sure that
NOTE you configure the Communications Failure Mode for the Area’s iSTAR Cluster as No access Mode,
instead of Local Mode.
For more information on Areas and Antipassback, see the C•CURE 9000 Areas and Zones Configuration Guide.
To Configure the iSTAR Cluster - Area Tab for Cluster Antipassback Communications Failure Mode
1. From the iSTAR Cluster dialog box, click the Area tab. The Area tab opens, shown in Figure 40 on Page 106.
2. In the Cluster Antipassback Communication Failure Mode box, click to select either the No access or Local
option.
Make sure that you leave the Cluster enforces iSTAR Global antipassback as well as iSTAR Cluster
NOTE antipassback check box unselected.
To Configure the iSTAR Cluster - Area Tab for both Global Antipassback and Cluster Antipassback
1. From the iSTAR Cluster dialog box, click the Area tab. The Area tab opens, shown in Figure 40 on Page 106.
2. In the Global Antipassback box, click to select the Cluster enforces iSTAR Global antipassback as well as
iSTAR Cluster antipassback option.
Fields Description
No access (Hard) Select this option to configure No access as the Communications Failure mode for this Cluster.
• Access is denied by any member Controller in the Cluster in communications failure.
• Member Controllers still in communications with the Master continue to request normal
antipassback decisions for entry to the Area.
• Master Controllers need no communication to make antipassback decisions and always do so
regardless of host or member communication.
(In this mode, the person is presumed to be in violation, unless proven otherwise.)
Local (Soft) Select this option to configure Local as the Communications Failure mode for this Cluster.
• The Controller uses locally available information to grant or deny access. Even if this information
is insufficient, the Controller admits the person presenting the card.
(In this mode, the person is presumed not-in-violation, unless proven otherwise.)
When Local mode is configured, the person is allowed in unless the Controllers making the decision
determine beyond doubt that he/she is guilty of an antipassback violation.
Global Antipassback
Cluster enforces iSTAR Global Select this check box to indicate that this Cluster shares data with all the other Clusters that use
antipassback as well as iSTAR Cluster iSTAR Global Antipassback. (The default is cleared indicating that the Cluster does not share data
antipassback with any other Clusters.)
NOTE: When this option is selected, the Cluster Antipassback Communication Failure Mode
box options become unavailable.
To use FIPS 140-2 Validate mode, the Encryption Options must be configured in the Options and Tools pane before
you can configure Cluster encryption.
■ This tab is Read-only for a Non-encrypted Cluster, and does not apply. Non-encrypted Clusters do not
NOTE use 256-bit AES (FIPS 197) encryption. The iSTAR eX, iSTAR Edge, and encrypted iSTAR Ultra LT,
iSTAR Ultra, iSTAR Ultra SE (in Ultra Mode) controllers use 256-bit AES (FIPS 197) encryption by
default.
■ Encryption is supported on IP-ACM v2 when connected to a controller with firmware v6.6.5 and higher.
If you are already using custom certificates on the controller, you need to upgrade to firmware v6.6.5
and generate a new certificate.
■ The 256-bit AES (FIPS 197) encryption method satisfies the Proprietary Burglar Alarm application
requirements.
■ Software House recommends that you configure the Tamper Input for a 'dark mode' controller to trigger
an Alarm Event that will be displayed on the Monitoring State if the input changes state.
FIPS 140-2 mode requires a custom certificate key, either host based or controller based. Software House recommends a
controller based certificate key. Once you set the cluster to FIPS 140-2 compliant mode, the iSTAR encrypted controllers
and IP-ACM v2s will be in “dark mode.” They will not be visible on the network.
5. In the iSTAR Cluster dialog box, click the Encryption tab. The Encryption options are shown in Figure 41 on Page
109.
Figure 41: iSTAR Cluster Encryption Tab
6. Select from the available Encryption modes: Non-FIPS 140-2 or FIPS 140-2 Validate mode for iSTAR Ultra,
iSTAR Edge, iSTAR eX, and IP-ACM.
7. Navigate to the Triggers tab or Save and Close to save the cluster and begin configuring iSTAR Controllers.
Communication Failure
This section applies if you selected FIPS 140-2 Validate mode for iSTAR Ultra, iSTAR Edge, iSTAR eX, and IP-
ACM.
If any of the controllers are disabled or in communication failure after the change in policy, use one of the following
methods to re-establish communication:
■ If the C•CURE 9000 server is the Certificate Authority, use the ICU to initiate the Signature Request process. If the
request fails, clear the controller memory, reboot the controller, and then use ICU to reinitate the Signature Request
process.
■ If a third-party is the Certificate Authority, export the controller certificate to a USB drive, insert the USB drive into the
controller, and then reboot the controller.
The Triggers tab is not available for iSTAR Pro or iSTAR Ultra SE Pro Mode dialup configurations.
NOTE
This tab provides you with ability to define the activation/deactivation, enable/disable, and arm/disarm, etc. of such
objects as: events, inputs, outputs, camera actions, door status changes, etc. Triggers can also be used to launch
events which also can be used to launch imports and exports, email and reports, viewer and message displays,
personnel ID number state changes, controller downloads, sound activation, communication notifications, etc.
2. Click Add in the Triggers tab to create a new trigger.
a. Click within the Property column to display .
When you select this button, the Property browser opens presenting properties available for the controller.
b. Click a Property to select it and add it to the column (see Figure 43 on Page 111).
c. Click within the Value column to display a drop-down list of Values associated with the Property that you have
selected. Then click on a Value that you want to include as a parameter for the trigger to add it to the column (see
Figure 44 on Page 112).
When a Trigger is added, an Action must be configured in the Action column. This is the Action that will occur
when the object’s selected Property receives the selected Value.
d. Click within the column to display a drop-down list of valid actions. Click an Action that you want to include as a
parameter for the trigger to add it to the column (see Figure 45 on Page 113).
As the Action is selected, the lower pane in the Triggers box displays a corresponding entry field, or group of entry
fields, specific to the selected Action, such as an Event or Output (see Figure 46 on Page 113).
In the case of the Primary Communications Status Property, the available Action is to activate an event.
Figure 46: iSTAR Cluster TriggersTab - Action Event
e. In the Event field, click to select a Event that you want to associate with the trigger (see Figure 47 on Page
114). Events are created in the Configuration Pane. See the C•CURE 9000 Software Configuration Guide for more
information.
Figure 47: iSTAR Cluster Triggers Tab - Event Selection
Once the field (or group of fields) is completed, the Details column will show information about how the Action has
been configured.
To activate or arm iSTAR Cluster events by a trigger condition, the schedule value is restricted to Always.
NOTE
3. To Remove a Trigger, select the row using the button and click Remove.
A completed Trigger that notifies you of communications failure in the cluster is shown in Figure 48 on Page 115.
4. Navigate to the Status tab or Save and Close to save the cluster and begin configuring iSTAR Controllers.
See Chapter 4: Configuring Dialup for the dial-up configuration sequence to follow and configuration information.
The Details of the selected controller section displays the same status fields that are displayed on that controller's
Status tab. For more information on the status fields that are displayed for each controller type, see the iSTAR Controller
Status Tab on Page 162.
To Change an Image
1. Double-click the existing image.
A Windows Open dialog box appears allowing you to browse for a folder in which you have placed replacement
images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click the new image and select Restore Default.
4. Click Save and Close to save changes to the cluster state images.
The C•CURE iSTAR controller is an intelligent controller for networked security systems. C•CURE iSTAR controllers
communicate with the C•CURE 9000 server (acting as a database and journal host) and the system security hardware,
providing direct control of events and system activity. This chapter explains how to configure iSTAR controllers, and the
devices related to them, in the C•CURE 9000 System.
In this chapter
To install and configure the controller hardware and its connected devices see the following manuals:
■ iSTAR Pro Installation and Configuration Guide
■ iSTAR eX Installation and Configuration Guide
■ iSTAR Edge Installation and Configuration Guide
■ iSTAR Ultra Installation and Configuration Guide
■ iSTAR Ultra SE Installation and Configuration Guide
■ iSTAR Ultra LT Installation and Configuration Guide
For information on configuring host and panel Events for an iSTAR controller, see the Events chapter in the C•CURE 9000
Software Configuration Guide.
The following sections provide the information you need to configure the iSTAR Controllers.
■ iSTAR Controller Tasks on Page 127
■ Configuration Overview for iSTAR Controllers on Page 121
■ iSTAR Controller Editor on Page 145
■ Before configuring a controller, make sure you know the MAC address of the controller NIC you are
NOTE using. The MAC address is built into the GCM and cannot be changed. You can find a controller’s
MAC address(es) on a label attached to the GCM.
■ If you configuring the iSTAR Ultra Video controller, the MAC address is the MAC Address of the
iSTAR Ultra Video device.
When using a multi-homed 9000 standalone server with multiple network adapters on multiple networks,
NOTE use a selected IP address for IP communication to ensure consistent communication with the iSTAR fast
personnel download. Set the IP address as the host address for the iSTAR controllers and in the Options
& Tools > System Variables > iSTAR Driver> Specified Host IPV4 Address and/or Specified Host
IPV6 Address field. Then restart the driver.
1. Create and save an iSTAR Pro Cluster for the Controller. Creating an iSTAR Cluster on
Page 92
2. Create an iSTAR Pro Controller under the iSTAR Cluster in the Hardware Tree. Creating an iSTAR Controller on
Page 127
3. Use the iSTAR Controller General tab to configure the basic communications iSTAR Controller General Tab on
settings for the Controller and to assign Reader LCD Message Sets. Page 150
4. Use the Boards tab to create and configure Inputs, Outputs, and ACM boards for iSTAR Controller Boards Tab
the Controller. (iSTAR Classic/Pro) on Page 167
5. If you have Schlage Wireless PIMs and Readers, use the Schlage Wireless PIMs iSTAR Schlage Wireless PIMs Tab
tab to configure these devices. on Page 165
6. From the Hardware Tree, create iSTAR Door objects for the Controller. iSTAR Door Editor on Page 397
7. From the Hardware Tree, create iSTAR Elevator objects for the Controller. iSTAR Elevators on Page 557
8. Use the iSTAR Triggers tab to create new triggers for the Controller. iSTAR Controller Triggers Tab on
Page 162
9. Use the iSTAR State Images tab to customize the state images that are displayed iSTAR Controller State Images
on the Monitoring Station for the iSTAR Controller. Tab on Page 164
1. Create and save an iSTAR eX/Edge Cluster for the Controller. Creating an iSTAR Cluster on
Page 92
2. Create an iSTAR eX/Edge Controller under the iSTAR Cluster in the Hardware Tree. Creating an iSTAR Controller on
Page 127
3. Use the iSTAR Controller General tab to configure the basic communications settings for the iSTAR Controller General Tab on
Controller and to assign Reader LCD Message Sets. Page 150
4. Use the iSTAR Controller Inputs tab to create the Inputs on the Controller. iSTAR eX and Edge Controller
Inputs Tab on Page 170
5. Use the iSTAR Controller Outputs tab to create the Outputs on the Controller. iSTAR Edge/eX Controller Outputs
Tab on Page 174
6. Use the iSTAR Controller Wiegand tab to create the direct connect Wiegand Readers on the iSTAR eX Controller Wiegand Tab
Controller. on Page 180
7. Use the iSTAR Controller tabs to create the Input Boards, Output Boards, and Readers on the iSTAR eX COM1/COM2 Tabs on
Controller. Page 182
iSTAR Edge COM1/COM2/COM3
Tabs on Page 176
8. If you have Schlage Wireless PIMs and Readers, open the iSTAR PIM-485 Board editor to iSTAR PIM-485 Board Editor on
configure these devices. Page 236
9. From the Hardware Tree, create iSTAR Door objects for the Controller. iSTAR Door Editor on Page 397
From the Hardware Tree, create iSTAR Elevator objects for the Controller. iSTAR Elevators on Page 557
10.
Use the iSTAR Triggers tab to create new triggers for the Controller. iSTAR Controller Triggers Tab on
11. Page 162
Use the iSTAR State Images tab to change the images that display on the Monitoring Station for iSTAR Controller State Images
12. the iSTAR Controller. Tab on Page 164
1 Create and save an iSTAR Ultra Cluster for the Controller. Creating an iSTAR Cluster on
Page 92
2 Create an iSTAR Ultra Controller under the iSTAR Cluster in the Hardware Tree. Creating an iSTAR Controller on
Page 127
3 Use the iSTAR Controller General tab to configure the basic communications settings for the iSTAR Controller General Tab on
Controller and to assign Reader LCD Message Sets. Page 150
4 Use the Boards tab to create and configure Inputs, Outputs, and ACM boards for the Controller. iSTAR Ultra Controller Boards
Tab on Page 187
5 Open the iSTAR IP-ACMs tab to create Inputs, Outputs, and Readers for the Controller. iSTAR Ultra Controller IP-ACMs
Tab on Page 189
6 Click the Com1 and Com2 tab to configure Aperio Hubs and Schlage PIMs iSTAR Ultra COM1/COM2 Tabs
on Page 189
7 From the Hardware Tree, create iSTAR Door objects for your Controller. iSTAR Door Editor on Page 397
8 From the Hardware Tree, create iSTAR Elevator objects for your Controller. iSTAR Elevators on Page 557
9 Use the iSTAR Triggers tab to configure the triggers for controller events.. iSTAR Controller Triggers Tab on
Page 162
10 Use the iSTAR State Images tab to customize the state images that are displayed on the iSTAR Controller State Images
Monitoring Station for your iSTAR Controller. Tab on Page 164
2 Create an iSTAR Ultra Video Controller under the iSTAR Cluster in the Hardware Tree. Creating an iSTAR Controller on
Right-click on the Cluster and select iSTAR Ultra Video Controller. Page 127
3 Use the iSTAR Controller General tab to configure the basic communications settings for the iSTAR Controller General Tab on
Controller. Page 150
4 Use the iSTAR Controller Boards tab to create and configure Inputs, Outputs, and Readers. iSTAR Ultra Controller Boards
NOTE: Ensure that iSTAR Ultra ACM is selected as the ACM type. Tab on Page 187
1. Create the ACM Boards that you need by clicking Create All ACMs, or by selecting the
Configured check box for only the ACMs you wish to create.
2. Click in the Edit column to configure an ACM. iSTAR Ultra Controller ACM
Board Editor on Page 202
5 Use the iSTAR Controller IP-ACMs tab to configure the IP-ACMs Inputs, Outputs, Readers and Configuring the IP-ACM on Page
Triggers. 294
1. Create the IP-ACM Boards that you need by clicking Create All IP-ACMs, or by selecting the
Configured check box for only the ACMs you wish to create.
2. Click in the Edit column to configure an IP-ACM.
6 Use the iSTAR Controller Triggers tab to configure the triggers for controller events. Triggers Tab for iSTAR Devices
on Page 278
7 Use the iSTAR Controller State Images tab to customize the state images that are displayed on the iSTAR Controller State Images
Monitoring Station for your iSTAR Controller. Tab on Page 164
8 From the Hardware Tree, create iSTAR Door objects for your Controller. iSTAR Door Editor on Page 397
1 Create and save an iSTAR Ultra LT Cluster for the Controller. Creating an iSTAR Cluster on
Page 92
2 Create an iSTAR Ultra LT Controller under the iSTAR Cluster in the Hardware Tree. Creating an iSTAR Controller
on Page 127
3 Use the iSTAR Controller General tab to configure the basic communications settings for the iSTAR Ultra LT Controller
Controller and to assign Reader LCD Message Sets. General Tab on Page 156
4 Use the Inputs tab to create and configure Inputs for the Controller. iSTAR Ultra LT Controller
Inputs Tab on Page 191
5 Use the iSTAR IP-ACM tab to open the configure offline mode of IP-ACMs and open the IP- Configuring the IP-ACM on
ACM Board Editor and create Inputs, Outputs, and Readers for the Controller. Page 294
6 Click the COM Port tab to configure Aperio Hubs or Schlage Wireless PIMs. iSTAR Ultra LT Controller
COM Port Tab on Page 192
7 From the Hardware Tree, create iSTAR Door objects for your Controller. iSTAR Door Editor on Page
397
8 From the Hardware Tree, create iSTAR Elevator objects for your Controller. iSTAR Elevators on Page 557
9 Use the iSTAR Triggers tab to configure the triggers for controller events. iSTAR Controller Triggers Tab
on Page 162
10 Use the iSTAR State Images tab to customize the state images that are displayed on the Monitoring iSTAR Controller State Images
Station for your iSTAR Controller. Tab on Page 164
Creating an iSTAR Controller
You can create a new iSTAR Controller only within an iSTAR Cluster of the appropriate type.
The iSTAR Ultra S1-1 encryption switch enables FIPS 197 AES 256-bit encryption. The switch setting
NOTE must match the software configuration of the cluster and the controller. See the iSTAR Ultra Installation
and Configuration Guide for more information.
• iSTAR Ultra LT >New
■ For a Non-encrypted Cluster, you can select:
• iSTAR Classic Controller>New
• iSTAR Pro Controller>New
• iSTAR Ultra Controller>New
• iSTAR Ultra Video Controller>New
• iSTAR Ultra LT >New
The iSTAR Controller Editor opens to allow you to configure the Controller. See iSTAR Controller Editor on Page 145
You set the password in the iSTAR Controller editor dialog box. You can also use the iSTAR Controller Dynamic View to
set a password on a controller and to set the same password on multiple controllers.
You are not required to set a diagnostic password for the iSTAR Ultra Video controller.
NOTE
The new Controller template appears under ---- Templates in the iSTAR Controller context menu drop-down list in the
Hardware tree.
• Email to send the deletion message to the email address you have configured in the Customer Support section of
the C•CURE 9000 System Variables.
This setting overrides the SNMP setting in the iSTAR Configuration Utility.
Once you select Serial Number Status the serial numbers are visible whenever the iSTAR GCM
NOTE Board Dynamic View is displayed.
Encrypted SD cards, and firmware upgrades to v6.6.B and higher, are controller specific and cannot be used in any other
controller.
The selections described in Table 15 on Page 134 are not available for all controllers. Selections available are also based
on the privileges granted.
Table 15: iSTAR Controller Context Menu
Selection Description
Edit Click this menu selection to edit the selected iSTAR Controller. The iSTAR Controller editor opens. You can rename the
iSTAR Controller, change its description, and any other attributes.
Delete Click this menu selection to delete the selected iSTAR Controller(s). A prompt appears asking you to confirm that you want to
delete the iSTAR Controller. Click Yes to delete the Input or No to cancel the deletion.
When you delete an iSTAR Controller, all of the child objects you have defined for the Controller are also deleted.
Set Property Click this menu selection to change the value of a property in the selected controller(s).
A dialog box appears asking you to select a property to change. Click to open a selection list and click the property you
wish to change.
See Using Set Property for an iSTAR Controller on Page 137.
Selection Description
Add to Group Click this menu selection to add the iSTAR Controller to a Group. .A dialog box listing the iSTAR Controller Groups in the
system appears. Click on a Group in the list to add the iSTAR Controller(s) to that Group. See Add a Hardware Device to
Group from a Dynamic View on Page 383.
Export Opens an Export dialog box from which you can export one or more records displayed in a Dynamic View to either an XML or
Selection... a CSV file. This allows you to quickly and easily create XML/CSV reports on selected C•CURE 9000 data.
NOTE: Although XML is the initial default file type, once you choose a type in the Save as type field, whether XML or CSV,
that becomes the default the next time this dialog box opens.
CSV-formatted exports cannot be imported. If you require importing functionality, export to XML.
• When you export to an XML file, all available data for the selected object(s), whether displayed in the Dynamic View or not,
as well as all the child objects of the selected record(s), is exported.
• When you export to a CSV file, only data in the columns displaying in the Dynamic View is exported, and in the order
displayed. This allows you to both select and arrange data fields for your report. In addition, exporting to a CSV file allows
you to view the exported data in an Excel spreadsheet and further manipulate it for your use.
NOTE: When you click Export Selection, you are running the export on the client computer. Consequently, the system does
not use the Default Export Directory Path—which is on the server. It opens a directory on the client, reverting to the
last directory used. You can navigate to the default export server directory, if you wish. Or to avoid confusion or use the
same destination folder for both client and server computers, you can use UNC (Universal Naming Convention)
paths.
Example:
\\Computer Name\Program Files\Software House\SWHouse\SWHSystem\Export.
Find in Audit Opens a Query Parameters dialog box in which you can enter prompts and/or modify the query criteria to search for entries in
Log... the Audit Log that reference the selected iSTAR Controller. The results display in a separate Dynamic View. This selection is
not available if you select multiple Controllers.
Find in Journal... Opens a Query Parameters dialog box in which you can enter prompts and/or modify the query criteria to search for entries in
the Journal that reference the selected iSTAR Controller. The results display in a separate Dynamic View. This selection is not
available if you select multiple Controllers.
Associate Tag Associates the object with a tag configured in the Tag Manager.
Perform Full Downloads configuration and personnel records appropriate to the controller.
Controller
Download
Update Updates the firmware for an iSTAR controller. See Updating iSTAR Firmware (Ethernet Connections) on Page 137 and
Firmware... Updating iSTAR Firmware (Dial-up Connections) on Page 139.
NOTE: If you are using dial-up to update the firmware, you must manually connect to the iSTAR before Update Firmware is
visible in the context menu.
Diagnostics... • Opens the iSTAR Controller Diagnostics System web page for the iSTAR eX, Edge and Pro Controllers.
• Opens the iSTAR Ultra Web Diagnostics page for the iSTAR Ultra, Ultra SE, and Ultra LT Controllers.
• Opens the iSTAR Ultra Video log in page for the iSTAR Ultra Video Controller.
Selection Description
Turn Opens the Maintenance Mode dialog box to put the iSTAR Controller and/or its components into Maintenance Mode. See
Maintenance Chapter 3: Maintenance Mode for more information.
Mode On
Turn Opens the Maintenance Mode dialog box to take the iSTAR Controller and/or its components out of Maintenance Mode. See
Maintenance Chapter 3: Maintenance Mode for more information.
Mode Off
Disable/Enable Click to enable or disable SNMP on the controller. This setting overrides the SNMP settings in the iSTAR
SNMP Configuration Utility.
Copy and Used to make a duplicate of a Cluster and its Child Objects on the same partition on the same system. See Copying, Pasting,
Paste... and Renaming Clusters and Controllers on Page 47.
Copy To... Used to make a duplicate of a Cluster and its Child Objects on a different partition on the same system, using Paste From.
See Copying, Pasting, and Renaming Clusters and Controllers on Page 47.
If there are multiple monitors attached to your system you can use the monitor icon, located at the end of the Monitor and
Associations context menu selections, to display the activity on a selected monitor.
NOTE: The monitors displayed is based on the monitor configuration settings.
Monitor Click this menu selection to view activity for the selected iSTAR Controller(s), and any Add-on Board, Door, Elevator, Input,
Output, Reader, and Trigger-with-target-Event children, on an Admin Monitor Activity Viewer.
NOTE: Which Add-on Boards display on the Monitor—as well as which of their Input, Output, Reader, and Trigger-with-
target-Event children—Depends on the Controller type and what is turned on.
For more information, see "Monitoring an Object from the Administration Station" in the C•CURE 9000 Getting Started Guide.
Connect Dialup This menu selection is only available for an iSTAR using dialup (Pro/Ultra SE Pro Mode).
Panel Click to open the Manual Action dialog box to enter a starting time, ending time, and priority to connect using dialup. It is
recommended that you set the Start and End time to maintain a connection for a minimum of two hours.
Reset Dial-up This menu selection is only available on an iSTAR Master using dialup (Pro/Ultra SE Pro Mode).
Panel Click to reboot the iSTAR controller.
Show Opens a Show Association dialog box that lists all the security objects associated with the object selected.
Associations
Selection Description
You cannot update the iSTAR Ultra Video controller firmware from C•CURE 9000. See the iSTAR Ultra
NOTE Video Installation and Configuration Guide for upgrade information.
Update Firmware will not appear on the context menu if the iSTAR is not Enabled or is off-line.
NOTE
The Firmware Download dialog box, shown in Figure 52 on Page 138, opens.
Figure 52: Firmware Download Dialog Box
The Manual Actions dialog box, shown in Figure 54 on Page 140, opens.
2. Ensure that the Start and End Time is set to a minimum of two hours.
3. Click Save and Close.
4. After the connection is established, right-click on the controller and select Update Firmware as shown in Figure 55 on
Page 140.
Update Firmware will not appear on the context menu if the iSTAR is not Enabled or is off-line.
NOTE
The Firmware Download dialog box, shown in Figure 56 on Page 141, opens.
These procedures use default passwords. If you changed the default passwords, then you must use those.
NOTE
You cannot use the ICU to upgrade the iSTAR Ultra Video Controller. See the iSTAR Ultra Video
NOTE Installation and Configuration Guide for upgrade information.
If you are downloading firmware to a controller using dialup, perform the following steps before you
NOTE download the firmware:
2. Monitor the connection in the Monitoring Station. Once complete, proceed to Step 1 below.
6. Click Start Download to initiate the download to all controllers in the Download Firmware list.
The firmware is downloaded simultaneously to all controllers in the list. The Progress bar on each line indicates when
the download is complete for each controller.
The controller may reboot more than once during the upgrade process.
NOTE
• To cancel a download, select the controller and right-click to select Cancel Download from the context menu.
• If a Controller returns a Download Failed message, you can select the controller and right-click to select Retry from
the context menu to restart the firmware download.
9. When all of the downloads have completed, click Exit to close the Firmware Download dialog box.
If you change the Time Zone of the iSTAR controller, the Time Zone settings of all child objects of that iSTAR controller are
changed as well. A warning message appears if you change the Time Zone and any Events or Triggers have controller-
based actions on this iSTAR controller and the Event is configured to use a different Time Zone than this iSTAR controller.
Host-based actions with Schedules respect the controller Time Zone: a host-based Event that unlocks doors according to
a Schedule uses the controller Time Zone to determine when the Schedule is active for devices on that controller.
However, if a Time Zone is assigned to the host-based Event itself, the Event actions will activate on the Schedule based
on the host Time Zone.
Example:
With a C•CURE 9000 Server in the Eastern US Time Zone (GMT -5:00) and an iSTAR controller in the Central
US Time Zone (GMT -6:00):
■ A host Event that does not include an Event Time Zone unlocks specific Doors by Schedule on an iSTAR
controller according to the controller Time Zone.
■ A host Event that includes an Event Time Zone unlocks specific doors by Schedule on an iSTAR controller
according to the C•CURE 9000 Server Time Zone.
1. From the Hardware pane, select the iSTAR controller you wish to change. Right-click and select Edit.
2. Clear the Enabled field (change to ).
3. Click Save and Close to save the change.
4. From the Hardware pane, select the iSTAR controller again. Right-click and select Edit.
5. When the iSTAR controller editor opens, the Time Zone field can be changed.
6. Click Save and Close to save the change.
The iSTAR Ultra SE configuration data (doors, personnel, etc.) is held in volatile RAM during normal operation (IP settings
are stored in the controller’s onboard flash memory). This data is backed up to non-volatile SD Card memory on a periodic
basis during normal operation. Data is automatically backed up after a fast download to the panel, and, upon a soft reset on
the GCM board.
The non-rechargeable lithium coin cell battery maintains the controller’s clock only during a power outage
NOTE for up to 30 days.
To ensure that the database backup is always current, Software House recommends that you create an event to trigger a
database backup when the Low Battery or AC Fail input is activated on the GCM board. An event with the action
“Backup iSTAR Database” can trigger the event from the Low Battery or AC Fail input. If your power supply does not
support the Low Battery or AC fail, then you can trigger the database backup event using a schedule. For example, set a
schedule to run every Monday at 2AM.
When power is restored after an outage, the controller first attempts to connect to its host server. If successful, the host
will download the current time to the controller, and download the current database. However, if the host is not present,
then the controller will use its local backed-up time, and it will use the last saved database from the SD card.
When the host is offline, transaction buffers of card activity and other activity are automatically written to non-volatile
memory, and do not require database backup configuration.
You use the iSTAR Controller editor to configure the Controller settings and specify the Inputs, Outputs, and Readers that
are connected to the Controller.
For information about the iSTAR Controller editor for a specific iSTAR model, see:
■ iSTAR Classic Controller Editor on Page 145
■ iSTAR Pro Controller Editor on Page 146
■ iSTAR eX Controller Editor on Page 146
■ iSTAR Edge Controller Editor on Page 147
■ iSTAR Ultra Controller Editor on Page 148
■ iSTAR Ultra LT Controller Editor on Page 149
■ iSTAR Ultra Video Controller Editor on Page 148
The iSTAR Classic Controller Editor has the tabs listed in Table 16 on Page 145.
Table 16: iSTAR Classic Controller Editor Tabs
Tab See...
Schlage Wireless PIMs iSTAR Schlage Wireless PIMs Tab on Page 165
User Defined Fields iSTAR Controller User Defined Fields Tab on Page 164
The iSTAR Pro Controller Editor has the tabs listed in Table 17 on Page 146.
Table 17: iSTAR Pro Controller Editor Tabs
Tab See...
Schlage Wireless PIMs iSTAR Schlage Wireless PIMs Tab on Page 165
User Defined Fields iSTAR Controller User Defined Fields Tab on Page 164
The tabs for the iSTAR eX Controller Editor are listed in Table 18 on Page 146.
Table 18: iSTAR eX Controller Editor Tabs
Tab See...
Tab See...
User Defined Fields iSTAR Controller User Defined Fields Tab on Page 164
Tab See...
User Defined Fields iSTAR Controller User Defined Fields Tab on Page 164
Tab See...
User Defined Fields iSTAR Controller User Defined Fields Tab on Page 164
Tab See...
Tab See...
User Defined Fields iSTAR Controller User Defined Fields Tab on Page 164
Tab See...
User Defined Fields iSTAR Controller User Defined Fields Tab on Page 164
The iSTAR Controller editor basic tabs and iSTAR specific tabs are listed below.
Basic Tabs
■ iSTAR Controller General Tab on Page 150
■ iSTAR Controller Boards Tab (iSTAR Classic/Pro) on Page 167
■ iSTAR Controller Triggers Tab on Page 162
■ iSTAR Controller Status Tab on Page 162
■ iSTAR Controller Network Status Tab on Page 163
■ iSTAR Controller State Images Tab on Page 164
■ iSTAR Controller User Defined Fields Tab on Page 164
Starting in C•CURE 9000 v2.70, iSTAR Ultra family controllers with firmware version 6.6.x must use the
NOTE iSTAR Configuration Utility (ICU) or the iSTAR Ultra Web pages to configure network settings. The IP
address and IP family settings will not be displayed and are not configurable in C•CURE 9000.
See iSTAR Controller General Tab Definitions on Page 153 for field descriptions.
Figure 57: iSTAR Controller General Tab (iSTAR Ultra shown)
4. Enter the last six hexadecimal characters after the vendor portion of the address in the MAC Address entry field for
the controller. The first six characters of a controller’s MAC address are set at 00-50-F9. The last six characters of a
controller’s MAC address must be within the range of hexadecimal values (for example, 0-9 and a-f).
5. To select a particular customized set of LCD messages for the RM Readers, click to display a Reader LCD
Message Set selection list. If you leave this field blank (the default), the Readers use the default messages. See LCD
Message Set on Page 526 for more information. (Edge, eX, Ultra, Ultra SE, Ultra LT, Pro)
6. If you are configuring iSTAR controllers that are located in different time zones, you can use the Time Zone entry
field. Click to display a time zone selection. Greenwich Mean Time is equivalent to Zulu or Universal Time. If you
leave the Time Zone field blank, the iSTAR is considered to be in the C•CURE 9000 server's Time Zone.
You can only change the Time Zone setting for the iSTAR controller when the controller is not Enabled ( ). See
Changing the Time Zone of an iSTAR Controller on Page 142.
7. To use the Automatic Door Unlock Control feature, select the check box.
With this feature, the controller turns the strike relay off when the door opens, or if a delay relock is configured, after
the delay relock time expires. Then if a second person swipes while door is open, the controller normally does not re-
activate the relay, under the assumption that if the door is open, the relay activation is not needed.
8. You can type an IP Address in the Onboard Ethernet IP Address field, although it is recommended that you select
Use DCHP to use the Dynamic Host Configuration Protocol (DHCP) option to automatically assign an IP address to
the Controller.
9. For an iSTAR eX Controller, you can enter an IP Address for the Onboard Ethernet Adapter #2. Alternatively, you
can select Use DHCP.
The supervision method for Inputs on the iSTAR Ultra is configured for each separate Input on the Input
NOTE Editor.
Since selecting this option causes a full Personnel download to the controller (including all credentials
NOTE except for Lost, Stolen Not Active, and Expired), a warning displays about the 250,000-record-download
limit.
14. To support Innometriks High Assurance readers attached to this controller (Ultra and Ultra SE in Ultra Mode), see
.iSTAR Ultra Controller High Assurance Tab on Page 162.
15. You can optionally click other tabs on the iSTAR Controller Editor to configure other settings prior to saving the
Controller.
16. Click the Enabled check box to put the controller online when you are finished configuring the iSTAR Controller
General tab. You must have entered a valid MAC Address and a setting for the IP Address before enabling the
Controller or you will receive an error message if you try to save the Controller settings with Enabled selected.
17. Click Save and Close to save your settings for the Controller and close the iSTAR Controller Editor.
Field Description
Name Enter a unique name up to 50 characters long for the controller. If you enter the
name of an existing object, the system returns an error message indicating there is
a conflict.
Description Enter a textual comment about the controller, such as its location or purpose. This
text is for information only.
Enabled Click the Enabled check box to put the Controller online. You must specify the
MAC address and IP address for the Controller prior to selecting Enabled or you
will receive an error message when you save the Controller.
Maintenance Mode Click to put the iSTAR Controller and/or its components into Maintenance Mode.
See Chapter 3: Maintenance Mode for more information.
Partition This read-only field identifies the Partition in which this Controller resides.
If you are creating a new Controller, the Partition that is currently the New Object
Partition for your Operator account is automatically assigned to each Controller
you create.
If you want to change the Partition of a Controller, you must move the Cluster in
which the Controller resides. See Using Drag and Drop in the Hardware Tree on
Page 35.
General
Controller Type This field displays the controller type: iSTAR Classic/Pro, iSTAR Edge, iSTAR
eX, iSTAR Ultra, Ultra LT,or iSTAR Ultra Video.
The Controller Type is determined when you initially create the controller object.
When you save the controller object, this field becomes read-only for all
subsequent editing sessions.
Field Description
Hardware (MAC) Address The Hardware/Adapter MAC address for the controller. The MAC address is built
Adapter #1 MAC Address into the GCM and cannot be changed. You can find a controller’s MAC address on
a label attached to the GCM or view the address using the iSTAR Configuration
Utility. The first six nibbles (or characters) of a controller’s MAC address are set at
00-50-F9. The last six nibbles (or characters) of a controller’s MAC address must
hexadecimal numbers between 0-9 and A-F.
NOTE: The iSTAR Ultra Video controller does not use the MAC address format
described above. The MAC address displayed is the MAC address of the
iSTAR Ultra Video device.
Reader LCD Message Sets If you want customized LCD messages to display on the RM Readers, specify a
(Classic/Pro, Edge, eX, Reader LCD Message Set. Click to display a Reader LCD Message Set
Ultra, Ultra SE, Ultra LT) selection list. By default, this field is blank indicating that the Readers are use the
default messages. For more information, see LCD Message Set on Page 526.
Time Zone If you are managing controllers in different time zones, specify a time zone for the
controller. Click to display a time zone selection.
The following objects are associated with the controller’s time zone:
• Inputs, outputs, and readers on the controller.
• Doors and door groups with inputs, outputs, or readers on the controller.
• Elevators and elevator groups with inputs, outputs, or readers on the
controller.
NOTE: Only Schedules and clearances that use the same time zone as the
controller are downloaded to the controller. If you change the controller’s
time zone after a Schedule or clearance has been downloaded to the
controller, a matching violation occurs. The time zone is downloaded to the
controller, and the clearance is deleted from the controller. See the
C•CURE 9000 Software Configuration Guide for more information.
Automatic Door Unlock Select this check box to enable the Automatic Door Unlock Control feature for the
Control controller.
If enabled, the controller turns the strike relay off when the door opens, or if a delay
relock is configured, after the delay relock time expires. Then if a second person
swipes while door is open, the controller normally does not re-activate the relay,
under the assumption that if the door is open, the relay activation is not needed.
You can use this feature to cover the case where you require the relay activation.
• If you clear the check box, the behavior of the controller is normal, and an admit
processed while the door is open means the relay is not activated.
• If you select the check box, the relay activates for the configured unlock time
selected in the iSTAR Door editor.
You need to select this check box for every controller you want to use this feature.
You can set this value on the Dynamic View from the Set Property selection. This
selection is audited in the Audit Log.
The default setting is disabled.
Field Description
Onboard Ethernet Adapter Enter the unique IP address for Onboard Ethernet as 4 numbers between 0 and
(1/2) 255, separated by periods, such as 100.10.10.1.
Use DHCP Select this check box to obtain an IP Address from a DHCP Server for the iSTAR
Controller’s Onboard Ethernet Adapter.
Adapter Installed Select this check box to indicate that an PCMCIA Ethernet adapter is installed.
IP Address Enter the unique IP address for the PCMCIA Ethernet Adapter as 4 integers
between 0 and 255, separated by periods, such as 100.10.10.1.
Use DHCP Select this check box to obtain an IP Address from a DHCP Server for the PCMCIA
Ethernet Adapter.
Use as Primary Ethernet Select this check box to indicate that the PCMCIA Ethernet Adapter is to be used as
Adapter the Primary Ethernet Adapter.
Bluetooth enabled Select this check box to allow troubleshooting messages to appear on the
Bluetooth device.
NOTE: Software House recommends to disable this feature after use.
Turn off LEDs and LCD You can to configure the LCD backlight and various status LEDs to always be off by
backlight selecting ( ), regardless of tamper state. Selecting this option does not affect the
(Edge, Ultra, Ultra SE (Ultra Power LED or the bright white external power indicator.
Mode), Ultra Video, Ultra
LT)
Onboard reader LED control Specify the method used on this controller to drive the direct connect reader LEDs:
(iSTAR Edge) • 3-wire (Red, Green, Yellow)
• External Bi-Color (2-wire Red, Green)
• 1-wire (A, B, C)
Field Description
Supervising resistor All iSTAR eX GCM Inputs and iSTAR Edge inputs must be wired in the same way
configuration and use the same supervision method. All supervised settings assume either one
(iSTAR eX and iSTAR Edge) or two end of line (EOL) resistors. You can use the Reverse Sense option if you
need a particular Input to differ from the selected setting (for example, if you
choose a NO setting here, but you need a door switch monitor Input to be NC, you
can set that Input for Reverse Sense in the iSTAR Input Editor (see iSTAR Input
Editor on Page 240 for more information).
• NO = Normally Open
• NC = Normally Closed
• EOL = End of Line
Select one of the resistor values in the drop-down list.
NO/NC Double EOL 1K is the default, and the traditional Software House method
Cluster Info
Communications Path These read-only fields display the Communications Path and the name of the
iSTAR Cluster through which this controller communicates with the C•CURE 9000
Server.
Diagnostic Password
Set Password For security, a password must be set for the controller. Click Set Password to
open the Set Diagnostic Password for this Controller dialog box.
Password requirements:
• Password length: >= 10
• Contains at least one uppercase letter (A-Z)
• Contains at least one lowercase letter (a-z)
• Contains at least one digit (0-9)
• Contains a special character
Enter the password, confirm the password and click OK.
See Setting the iSTAR Controller Diagnostic Password on Page 128
Starting in C•CURE 9000 v2.70, iSTAR Ultra family controllers with firmware version 6.6.x must use the
NOTE iSTAR Configuration Utility (ICU) or the iSTAR Ultra Web pages to configure network settings. The IP
address and IP family settings will not be displayed and are not configurable in C•CURE 9000.
• If you switch from 16 readers to 8 readers, all hardware configured beyond the eight reader version support will be
deleted.
— Everything configured under IP-ACMv1-9 to IP-ACMv1-16 boards will be deleted
— Everything configured under IP-ACMv2-9 to IP-ACMv2-16 boards will be deleted
— Everything configured under Hub9 to Hub16 for Aperio protocol will be deleted
— Everything configured under PIM9 to PIM16 for Schlage protocol will be deleted
4. Enter the last six hexadecimal characters after the vendor portion of the address in the MAC Address entry field for
the controller. The first six characters of a controller’s MAC address are set at 00-50-F9. The last six characters of a
controller’s MAC address must be within the range of hexadecimal values (for example, 0-9 and a-f).
5. To select a particular customized set of LCD messages for the RM Readers, click to display a Reader LCD
Message Set selection list. If you leave this field blank (the default), the Readers use the default messages. See LCD
Message Set on Page 526 for more information.
6. If you are configuring iSTAR controllers that are located in different time zones, you can use the Time Zone entry
field. Click to display a time zone selection. Greenwich Mean Time is equivalent to Zulu or Universal Time. If you
leave the Time Zone field blank, the iSTAR is considered to be in the C•CURE 9000 server's Time Zone.
You can only change the Time Zone setting for the iSTAR controller when the controller is not Enabled ( ). See
Changing the Time Zone of an iSTAR Controller on Page 142.
7. To use a Static IP address, deselect the DHCP check box and enter the IP address.
8. Select the radio button for the IP Address family of the controller, either IPv4 or IPv6. See IPv6 Configuration on Page
24 for IPv6 configuration requirements and configuration information.
9. You can optionally click other tabs on the iSTAR Controller Editor to configure other settings prior to saving the
controller.
10. Click the Enabled check box to put the controller online when you are finished configuring the iSTAR Controller
General tab. You must have entered a valid MAC Address and a setting for the IP Address before enabling the
controller or you will receive an error message if you try to save the controller settings with Enabled selected.
11. Click Save and Close to save your settings for the controller and close the iSTAR Controller Editor.
Field Description
Name Enter a unique name up to 50 characters long for the controller. If you enter the name of an
existing object, the system returns an error message indicating there is a conflict.
Field Description
Description Enter a textual comment about the controller, such as its location or purpose. This text is for
information only.
Enabled Click the Enabled check box to put the Controller online. You must specify the MAC address
and IP address for the Controller prior to selecting Enabled or you will receive an error
message when you save the Controller.
Maintenance Mode Click to put the iSTAR Controller and/or its components into Maintenance Mode. See
Chapter 3: Maintenance Mode for more information.
Partition This read-only field identifies the Partition in which this Controller resides.
If you are creating a new Controller, the Partition that is currently the New Object Partition for
your Operator account is automatically assigned to each Controller you create.
If you want to change the Partition of a Controller, you must move the Cluster in which the
Controller resides. See Using Drag and Drop in the Hardware Tree on Page 35.
General
Supports 16 Readers Deselected, the default, supports the 8 reader Ultra LT board. Select the check box if the
Ultra Lt board supports 16 readers.
MAC Address The Hardware/Adapter MAC address for the controller. The MAC address is built into the
GCM and cannot be changed. You can find a controller’s MAC address on a label attached
to the GCM or view the address using the iSTAR Configuration Utility. The first six nibbles (or
characters) of a controller’s MAC address are set at 00-50-F9. The last six nibbles (or
characters) of a controller’s MAC address must hexadecimal numbers between 0-9 and A-
F..
RM LCD Message Sets If you want customized LCD messages to display on the RM Readers, specify a Reader LCD
Message Set. Click to display a Reader LCD Message Set selection list. By default, this
field is blank indicating that the Readers are use the default messages. For more
information, see LCD Message Set on Page 526.
Time Zone If you are managing controllers in different time zones, specify a time zone for the controller.
Click to display a time zone selection.
The following objects are associated with the controller’s time zone:
• Inputs, outputs, and readers on the controller.
• Doors and door groups with inputs, outputs, or readers on the controller.
• Elevators and elevator groups with inputs, outputs, or readers on the controller.
NOTE: Only Schedules and clearances that use the same time zone as the controller are
downloaded to the controller. If you change the controller’s time zone after a
Schedule or clearance has been downloaded to the controller, a matching violation
occurs. The time zone is downloaded to the controller, and the clearance is deleted
from the controller. See the C•CURE 9000 Software Configuration Guide for more
information.
Field Description
IP Address Deselect the Use DHCP check box to enter a static IP address or select UseDHCP (the
default).
Address Family Select the radio button for the IP Address family of the controller, either IPv4 or IPv6.
NOTE: See IPv6 Configuration on Page 24 for IPv6 requirements and configuration
information.
Bluetooth enabled Select this check box to allow troubleshooting messages to appear on the Bluetooth device.
NOTE: Software House recommends to disable this feature after use.
Suppress Power
Turn off LEDs and LCD You can to configure the LCD back light and various status LEDs to always be off by selecting
backlight ( ), regardless of tamper state. Selecting this option does not affect the Power LED or the
bright white external power indicator.
Cluster Info
Communications Path These read-only fields display the Communications Path and the name of the iSTAR Cluster
through which this controller communicates with the C•CURE 9000 Server.
Diagnostic Password
Set Controller For security, a password must be set for the controller. Click Set Controller Password to
Password open the Set Diagnostic Password for this Controller dialog box.
Enter the password, confirm the password and click OK.
Password Requirements:
• Password length: >= 10
• Contains at least one uppercase letter (A-Z)
• Contains at least one lowercase letter (a-z)
• Contains at least one digit (0-9)
• Contains a special character
Enter the password, confirm the password and click OK.
See Setting the iSTAR Controller Diagnostic Password on Page 128 for more information.
Conditional Access
If any Doors on this controller need to be configured for Conditional Access, select the Include Personnel Without
Clearance in Personnel Downloads option in the Conditional Access box. The Conditional Access tab is available on
the iSTAR Doors Editor only if this option is selected. For information, see iSTAR Door Conditional Access Tab on Page
405.
Selecting this option causes a full Personnel download to the controller. This includes all credentials,
NOTE except for Lost, Stolen Not Active, and Expired. There is a 250,000-record-download limit.
When numerous controllers require fast download, the download starts with controllers configured with High priority.
Table 25: iSTAR Controller Editor Advanced Tab Fields
Field Description
Conditional Access
Include Personnel If you want to enable conditional access for Doors on this Controller, allow entry to Personnel without Clearances, click to
Without Clearance in select this option. The Conditional Access tab is available on the iSTAR Doors Editor only if this option is selected. For
Personnel Downloads more information, see iSTAR Door Conditional Access Tab on Page 405.
NOTE: Since selecting this option causes a full Personnel download to the controller (including all credentials except for
Lost, Stolen Not Active, and Expired), a warning displays about the 250,000-record-download limit.
Fast download When numerous controllers require fast download, the download starts with controllers configured with High priority.
Priority The download priority can be set to High, Normal, or Low.
Threshold to use fast The number of personnel records in the queue when personnel download starts.
download
See Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
on Page 162 provides definitions of the fields and buttons on the iSTAR Controller Status tab.
iSTAR Controller Status Tab Definitions
Field/Button Description
Dynamic Status
Online Status Indicates whether the controller has been Enabled (see the General tab).
Firmware Version The version of the firmware currently in use by the controller.
Boot Time The last date/time the controller was restarted (GMT or Zulu time)
Field/Button Description
Reader Security This field applies only to iSTAR eX controllers. It displays whether or not the eX 8-Reader Security Key is in place. Possible
Key Status status values are:
(eX only) Detected – the key is plugged in and 8 readers are operational on the iSTAR eX.
NotDetected – the key is not plugged in, and only four Readers will be operational.
Unknown – the key status cannot be determined (for example, the status is Unknown if the controller is out of
communication with C•CURE 9000). You can determine the status by observing the LCD on the iSTAR eX.
Encryption Setting A Read-only field that displays the Encryption Setting. Encryption settings are Encrypted (AES), Unknown, or Not
Status Encrypted.
(Edge,
Classic/Pro)
Total RAM (Ultra/ Total storage memory available to the microprocessor in megabytes.
Ultra Video)
PoE Board The field displays whether the Power over Ethernet (PoE) Board is installed. Possible status values are True or False.
Installed
(iSTAR Edge)
Edge Model Status The field displays the iSTAR Edge Model Status, either 2-door or 4-door.
Advanced
SNMP The check box is enabled (checked) if SNMP was enabled in the ICU for the controller.
Web Diagnostics The check box is enabled (checked) if Web Diagnostic was enabled in the ICU for the controller.
eX8 Reader USB The check box is enabled (checked) if the iSTAR eX 8-Reader USB key was enabled in the ICU for the controller.
Key
(iSTAR eX only)
To change the controller configuration, use the iSTAR Configuration Utility (ICU) or the iSTAR Ultra Web Utility
(iSTAR Ultra, Ultra SE, Ultra LT).
Field Description
Host IP Address The IP address or name of the Primary connection to the C•CURE host or to the master controller for the cluster.
NAT IP Address The Network Address Translator (NAT) address for the server used to download firmware to the controller.
Host IP Address If the check box is selected, indicates the controller does not accept an IP address from any source.
Locked
Use NAT If the check box is selected, indicates that Network Address Translator (NAT) address for the server is used to download
firmware to the controller.
Default The IP address of the default gateway router for the controller.
Gateway
Primary DNS The IP address of the primary domain name server for this Ethernet card.
Secondary DNS The IP address of the secondary domain name server for this Ethernet card.
DNS query The domain name of the DNS server for which you supplied the IP address.
suffix
Lock IP Address If the check box is selected, indicates the controller can accept a translated address downloaded from a Network Address
Translator, C•CURE system, or other remote device.
See the C•CURE 9000 Software Configuration Guide for more information.
The state images shown in the table do not apply to all iSTARS.
NOTE
An iSTAR controller can support up to 16 Schlage Wireless readers. The number of PIM boards needed to support your
readers can vary, depending upon Reader type and the physical location of the reader/lock hardware. You could connect
16 readers to a single PIM if all readers are within the range/distance specifications for wireless readers. If some readers
are farther away, additional PIMs may be needed to place a PIM within wireless range of each reader. You can configure
no more than 16 PIMs and 16 Readers per controller.
The AD300 series readers have an integrated PIM in the reader/lock hardware - these readers require you to configure an
iSTAR PIM board with only that reader attached to the PIM.
Support for the following Schlage features requires C•CURE 9000 2.10 R2 Patch 1 or later, and iSTAR
NOTE firmware 5.2.1 or later.
■ Wake on Radio
■ Keypad support
■ Manual Lock Override
■ Push Button
Each Reader has a reader address between 0 (zero) and 15. On an iSTAR, readers are numbered starting at 1, not 0. As a
result, a reader with address 0 is configured on the iSTAR as reader #1.
Example
If you have PIMs with addresses of 4, 8, 12, and 15, you should configure these PIMs on the iSTAR as PIM5, PIM9,
PIM13, and PIM16.
If you have readers with addresses 0 through 5, you should configure these readers on the iSTAR as iSTAR PIM 485
Reader1 through iSTAR PIM 485 Reader6.
Once you have assigned a reader address to one PIM, that reader address will be unavailable on all other PIM boards on
the iSTAR.
Example
You configure Reader address #1 on PIM Board #1. On every other PIM Board you configure on this iSTAR, Reader
address #1 is unavailable (grayed out).
The address ranges for readers connected to PIMs cannot overlap. If you set up your PIM hardware so that a specific PIM
controls reader addresses 0 through 5, you cannot assign a different PIM to control any of the addresses in between.
Example
You have two PIMs. You set one to control Reader addresses 0 through 5 (readers 1 through 6 on the iSTAR). You
other PIM must be setup to control readers outside this range, such as Reader addresses 8 through 11 (Readers 9
through 12 on the iSTAR).
If you add another PIM, that PIM cannot be assigned to control any of the already assigned addresses, even if the
address are not in use at this time by one of the two existing PIMs. The new PIM could only be assigned Reader
addresses 6 and 7 (Readers 7 and 8) and/or Reader addresses 12 through 15 (Readers 13 through 16).
Field/Button Description
Create All Click to create all 16 PIMs. When you click Create All PIMs the Configured column check boxes are selected, and you can click
PIMs in the Edit column to open the iSTAR PIM-485 Board Editor to configure a PIMs.
Delete All When you click Delete All PIMs, the check boxes in the Configured column are cleared for all 16 PIMs, and all 16 PIM boards
PIMs are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR PIM-485 Board Editor to configure a PIM. See iSTAR PIM-485 Board Editor on
Page 236.
Name column Displays the name for this PIM Board The name is system-generated by default, but you can edit this name by clicking in this field.
Save and Click to save your configuration changes and close the iSTAR Controller editor.
Close
The Boards tab in the iSTAR Controller Editor lets you configure the following inputs, outputs, and ACM boards.
■ Main Board Inputs on the GCM.
• Tamper - this input activates when the controller cabinet is opened.
• Power Failure - this input monitors for AC power failure of the apS or UPS supplying power to the controller. When
this alarm input activates, it specifies that the GCM has lost its primary power source, and is operating on
batteries.
• External Battery Low (iSTAR Ultra/Classic/Pro) - this input activates when the external emergency battery (from
the apS or UPS) is running low on power.
• Internal Battery Fault (iSTAR Ultra only) - this is a logical input that reports the state of the onboard battery.
• General (iSTAR Ultra only) - this input is a general purpose Supervised Input on the GCM.
■ Main Board Output on the GCM (iSTAR Classic only).
■ ACM 1 and ACM 2 Boards for the Controller (iSTAR Classic/Pro only).
Add-on Access Control Modules (ACM Boards) provide access control functionality by supporting readers, outputs
and inputs.
■ ACM 1 and ACM 2 Boards on SPI port 1 (iSTAR Ultra only) - used to configure Inputs, Outputs, and Readers on an
iSTAR ACM Board attached to SPI port 1 on an iSTAR Ultra Controller.
■ ACM 1 and ACM 2 Boards on SPI port 2 (iSTAR Ultra only) - used to configure Inputs, Outputs, and Readers on an
iSTAR ACM Board attached to SPI port 2 on an iSTAR Ultra Controller.
7. Create the ACM Boards that you need by clicking Create All ACMs or by selecting the Configured check box for
only the ACMs you wish to create.
8. Click in the Edit column to configure an ACM. See iSTAR Classic/Pro Controller ACM Board Editor on Page 208
for configuration instructions.
9. Click Save and Close to save the settings you have configured on the iSTAR Controller Boards tab, or click another
tab in the iSTAR Controller Editor to perform additional configuration.
Field/Button Description
Create All Inputs Click to create the three Main Board Inputs. When you click Create All Inputs the Configured
column check boxes are selected, and you can click in the Edit column to open the iSTAR
Input Editor to configure an Input.
Delete All Inputs When you click Delete All Inputs, the check boxes in the Configured column are cleared for
all three Main Board Inputs, and all three Inputs are immediately deleted (any settings you have
configured are lost).
Tamper The Tamper input activates when the controller cabinet is opened or removed from its mounting
surface.
NOTE: For UL applications, this field must be enabled.
Select the check box in the Configured column and click located in the Edit column to
open the iSTAR Input Editor General tab to configure the Tamper input. From the Input Editor
you can configure the Options, Triggers, Groups, Status and State Images that are associated
with the Tamper Input.
The Template column shows the template name chosen if you selected a Template prior to
creating the Input.
Power Failure The AC power failureinput monitors the AC power failure output of a battery backup unit, such
as the Advanced Power System (apS). When this alarm input activates, it specifies that the GCM
has lost its primary power source, and is operating on batteries.
NOTE: For UL applications, this field must be enabled.
Select the check box in the Configured column and click located in the Edit column to
open the iSTAR Input Editor General tab to configure the AC Power Fail Input. From the Input
Editor you can configure the Options, Triggers, Groups, Status and State Images that are
associated with the AC Power Fail Input.
The Template column shows the template name chosen if you selected a Template prior to
creating the Input.
External Battery Low The External Battery Low input activates when the emergency battery is running low on power.
(iSTAR Classic/Pro) NOTE: For UL applications, this field must be enabled.
NOTE: This field for iSTAR Pro and Classic is on the Boards Tab. For iSTAR eX and Edge, this
field is on the Inputs Tab.
Field/Button Description
External Battery Low Select the check box in the Configured column and click located in the Edit column to
(iSTAR open the iSTAR Input Editor General tab to configure the Options, Triggers, Groups, Status and
eX/Edge/Ultra) State Images that are associated with the Battery Low Input.
The Template column shows the template name chosen if you selected a Template prior to
creating the Input.
Internal Battery Fault A logical input that reports the state of the onboard battery. This Input is configured ( ) by
(iSTAR Ultra) default when the controller is created.
General A physical input that can be used to monitor a condition, particularly useful for Ultra
(iSTAR Ultra) configurations that are GCM only.
Create Click to create the Main Board Output. When you click Create the Configured column check
box is selected, and you can click in the Edit column to open the iSTAR Output Editor to
configure the Output.
Delete When you click Delete, the check box in the Configured column is cleared for the Main Board
(iSTAR Classic/Ultra) Output, and the Output is immediately deleted (any settings you have configured are lost).
1 Select the check box in the Configured column and click located in the Edit column to
open the iSTAR Output Editor General tab to configure the Options, Groups, Status and State
Images that are associated with the Main Board Output.
The Template column shows the template name chosen if you selected a Template prior to
creating the Output.
ACMs
Create All ACMs Click to create all the ACM Boards. When you click Create All ACMs the Configured column
(iSTAR Classic/Pro check boxes are selected, and you can click in the Edit column to open the iSTAR ACM
only) Board Editor to configure an ACM Board.
Delete All ACMs When you click Delete All ACMs, the check boxes in the Configured column are cleared for
(iSTAR Classic/Pro both Main Board ACM Boards, and both ACM Boards are immediately deleted (any settings you
only) have configured are lost).
Board1 Select the check box in the Configured column and click located in the Edit column to
open the iSTAR ACM Editor General tab to configure the Inputs, Outputs, and Readers that are
associated with the first ACM board.
Board2 Select the check box in the Configured column and click located in the Edit column to
open the iSTAR ACM Editor General tab to configure the Inputs, Outputs, and Readers that are
associated with the second ACM board.
The Inputs tab lets you define the Special Purpose and General Purpose Inputs for the Controller.
All of the inputs support event triggers based on their active or inactive states. These triggers can activate alarms, send
emails, run a Roll Call Report, etc.
iSTAR eX Controller Inputs
Special Purpose Inputs
■ Tamper input – Activates when the controller cabinet is opened.
■ Power Failure input – Monitors the AC power failure output of the PMB. When this alarm input activates, it indicates
that the PMB has had an AC Power Failure and is now supplying battery power to the controller.
Similarly, if the eX is the NPS (No Power Supply) version, the Power Fail output of the UPS or apS is monitored with
the same result.
■ External Battery Low input – Activates when the battery connected to the PMB emergency battery has reached a
yellow warning level. This will be followed, after some further use, with a Backup Now condition (Battery really low)
which will backup the configuration and data and then shut down the controller.
If the eX is the NPS (No Power Supply) version, the Battery Low output of the UPS or apS is monitored and will signal
low battery. It is recommended to shut down the unit being powered by the low battery.
Tamper, AC power fail, and Low battery inputs must be programmed for UL applications.
NOTE
Tamper, AC power fail, and Low battery inputs must be programmed for UL applications.
NOTE
■ Onboard Battery Low input – This input activates when the voltage of all four onboard AA alkaline batteries in series
reaches 4.6 volts, or if a battery is missing or disconnected.
The following Fire Alarm Interface (FAI) features are only supported on these iSTAR Edge models:
NOTE
n 0312-5010-02
n 0312-5010-04
■ FAI Supervision State input – This input represents the F (Fire) Input State - the state of the F (Fire) input coming into
J40 of the iSTAR Edge. In other words, this is the fire alarm. The Fire Alarm Interface activates the relays on the
iSTAR Edge when the F input goes True. This input is supervised as NC (Normally Closed).
■ FAI Relay Control input – The FAI relay control is a pseudo input that indicates the state of the Relay Drive signal
that activates or latches the selected relays when the F (Fire) input is True.
■ FAI Key Supervision Stateinput – This input represents the K (Key) Input State. The K input is used to unlatch the
latched relays, which removes the relay drive signal, once it is clear that the fire emergency is over. The K (Key) input
is usually a momentary contact key switch. The K input is supervised as NO (Normally Open).
All three of the FAI Inputs support Event triggers based on their active or inactive states. These Event triggers can be
configured to activate alarms, send emails, run a Roll Call Report, etc based on the state changes of the three FAI inputs.
FAI Modes
There are two basic FAI modes that can be configured at the controller.
n FAI without Latch - This method requires the F (Fire) input (NC) of J40 plus the individual enable switches for each
relay (SW2 through SW5).
n FAI with Latch and subsequent Unlatch - This method requires the F (Fire) input of J40 plus the individual enable
switches for each relay (SW2 through SW5), plus SW6 to enable the Latch and J40 K (Key) input (NO) to reset the
Latch.
The Key input is usually a key switch that momentarily closes when the key is inserted and rotated.
The FAI mode chosen at the controller will determine how you might want to use the Triggers and Actions available in the
software to provide notification of a fire alarm and related actions. See the iSTAR Edge Installation and Configuration
Guide for detailed information about wiring the FAI inputs.
5. Click in the Edit column to configure individual General Purpose Inputs. See the definitions of the General
Purpose Inputs in Table 30 on Page 173 and see iSTAR Input Editor on Page 240.
6. Click Save and Close to save the settings you have configured on the iSTAR Controller Inputs tab, or click another
tab in the iSTAR Controller Editor to perform additional configuration.
Field/Button Description
Create All Inputs Click to create all the Special Purpose Inputs. When you click Create All Inputs the Configured column check boxes are
selected, and you can click in the Edit column to open the iSTAR Input Editor to configure an Input.
Delete All Inputs When you click Delete All Inputs, the check boxes in the Configured column are cleared for all Special Purpose Inputs,
and all these Inputs are immediately deleted (any settings you have configured are lost). You will need to confirm each
deletion.
Edit column Click in the Edit column to open the iSTAR Input Editor to configure a Special Purpose Input. See iSTAR Input Editor on
Page 240.
Input Type This column displays the type of each Special Purpose Input.
column
Name column Displays the name for this Input. The name is system-generated by default, but you can edit this name by clicking in this field.
Template column Click in this column, then click to select an Input template to use for creating this Input from the list of available Input
templates. You can only select a Template prior to creating the input.
Tamper The Tamper input activates when the controller cabinet is opened or removed from its mounting surface.
Select the check box in the Configured column and click in the Edit column to open the iSTAR Input Editor. From the
Input Editor you can configure the settings and link to events through triggers.
Power Failure The Power Failure input monitors the AC power failure output of a battery backup unit, such as the Advanced Power
System (apS). When this alarm input activates, it specifies that the GCM has lost its primary power source, and is operating
on batteries.
Battery Low The Battery Low input activates when the emergency DC battery is running low on power.
FAI Supervision (iSTAR Edge only) – This is the F (Fire) Input State. Indicates the state of the F (Fire) input coming into J40 of the iSTAR
State Edge. In other words, this is the fire alarm.
FAI Key (iSTAR Edge only) – This is the K (Key) input state. Indicates the state of the K (Key) switch at J40 of the iSTAR Edge.
Supervision State
Field/Button Description
FAI Relay Control (iSTAR Edge only) – This pseudo input indicates the state of the Relay Drive signal that activates or latches the selected
relays when the F (Fire) input is true,
Onboard Battery The Onboard Battery Low activates when the voltage of all four onboard AA alkaline batteries in series reaches 4.6 volts,
Low (iSTAR Edge or if a battery is missing or disconnected.
only) Upon loss of external or PoE power to the Edge, data is written to onboard flash. Four onboard non-rechargeable alkaline
AA batteries provide power for the backup process and maintaining the clock.
Backup is valid for the period the onboard batteries can maintain the clock. The period has been tested for >3 days, but
should reasonably last for 2 weeks.
Create All Inputs Click to create all the General Purpose Inputs. When you click Create All Inputs the Configured column check boxes are
selected, and you can click in the Edit column to open the iSTAR Input Editor to configure an Input.
Delete All Inputs When you click Delete All Inputs, the check boxes in the Configured column are cleared for all General Purpose Inputs,
and all these Inputs are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Input Editor to configure a General Purpose Input. See iSTAR Input Editor
on Page 240.
Index column This column displays the number of each General Purpose Input.
Name column Displays the name for this Input. The name is system-generated by default, but you can edit this name by clicking in click in
this field.
Template column Click in this column, then click to select an Input template to use for creating this Input from the list of available Input
templates. You can only select a Template prior to creating the input.
Index 1 - 8 (iSTAR The General Purpose Inputs can be configured in an iSTAR Door as door switch monitor or request to exit inputs.
Edge)
Select the check box in the Configured column and click in the Edit column to open the iSTAR Input Editor. From the
Index 1 - 16 editor you can configure the settings for a General Purpose Input.
(iSTAR eX)
The Outputs tab in the iSTAR Controller Editor lets you define four Relay Outputs and four Open Collector Outputs (on the
iSTAR eX only).
2. Create the Relay Outputs that you need by clicking Create All Outputs or by selecting the Configured check box
for only the Outputs you wish to create.
3. Click in the Edit column to configure individual Relay Outputs. See the definitions of the Relay Outputs in Table
31 on Page 175 and see iSTAR Output Editor on Page 248 for configuration instructions.
4. On an iSTAR eX, create the Open Collector Outputs that you need by clicking Create All Outputs or by selecting
the Configured check box for only the Outputs you wish to create.
5. Click in the Edit column to configure individual Open Collector Outputs. See the definitions of the Open Collector
Outputs in Table 31 on Page 175 and see iSTAR Output Editor on Page 248 for configuration instructions.
6. Click Save and Close to save the settings you have configured on the iSTAR Controller Outputs tab, or click another
tab in the iSTAR Controller Editor to perform additional configuration.
Box Description
Create All Click to create all the Relay Outputs. When you click Create All Outputs the Configured column check boxes are selected, and
Outputs you can click in the Edit column to open the iSTAR Output Editor to configure an Output.
Delete All When you click Delete All Outputs, the check boxes in the Configured column are cleared for all Relay Outputs, and all these
Inputs Outputs are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Output Editor to configure a Relay Output. See iSTAR Output Editor on Page
248.
Index column This column displays the number of each Relay Output.
Name column Displays the name for this Output. The name is system-generated by default, but you can edit this name by clicking in this field.
Template Click in this column, then click to select an Output template to use for creating this Output from the list of available Output
column templates. You can only select a Template prior to creating the Output.
Relay Outputs Select the check box in the Configured column and click located in the Edit column to open the iSTAR Output Editor. From
1-4 the editor you can configure the settings for the Relay Output.
Create All Click to create all the Open Collector Outputs. When you click Create All Outputs the Configured column check boxes are
Outputs selected, and you can click in the Edit column to open the iSTAR Output Editor to configure an Output.
Delete All When you click Delete All Outputs, the check boxes in the Configured column are cleared for all Open Collector Outputs, and
Outputs all these Outputs are immediately deleted (any settings you have configured are lost).
Box Description
Edit column Click in the Edit column to open the iSTAR Output Editor to configure an Open Collector Output. See iSTAR Output Editor
on Page 248.
Index column This column displays the type of each Open Collector Output.
Name column Displays the name for this Output. The name is system-generated by default, but you can edit this name by clicking in this field.
Template Click in this column, then click to select an Output template to use for creating this Output from the list of available Output
column templates. You can only select a Template prior to creating the Output.
Open Select the check box in the Configured column and click located in the Edit column to open the iSTAR Output Editor. From
Collector the editor you can configure the settings for an Open Collector Output.
Outputs 5 - 8
The iSTAR Edge can support either two or four Readers, depending on the model.
These Readers can be configured on either the Readers tab or on the COM1, COM2, or COM3 tabs in any combination, as
long as the total number of Readers does not exceed the maximum allowed.
The number of I/8 and R/8 bus modules that are supported on the COMx ports depend upon the model:
■ Four I/8 s and four R/8s are supported on the two-reader model.
■ Eight I/8 s and eight R/8s are supported on the four-reader model.
7. Click in the Edit column to configure individual Readers. See the definitions of the Readers in Table 35 on Page
185 and see iSTAR Reader Editor on Page 496 for configuration instructions.
8. Click Save and Close to save the settings you have configured on the iSTAR Controller COM tabs, or click another
tab in the iSTAR Controller Editor to perform additional configuration.
Box Description
Input Boards
Create All Click to create all the Input Boards. When you click Create All Input Boards the Configured column check boxes are selected,
Input and you can click in the Edit column to open the iSTAR Input Board Editor to configure an Input Board.
Boards
Delete All When you click Delete All Input Boards, the check boxes in the Configured column are cleared for all Input Boards, and all these
Inputs Input Boards are immediately deleted (any settings you have configured are lost).
Boards
Edit column Click in the Edit column to open the iSTAR Input Board Editor to configure an Input Board. See iSTAR Input Board Editor on
Page 215.
Configured Click in this column to create an Input Board (make it available to be edited) .
column
Name Displays the name for this Input Board. The name is system-generated by default, but you can edit this name by clicking in this field.
column
Input Select the check box in the Configured column and click in the Edit column to open the iSTAR Input Board Editor. From the
Boards 1 - editor you can configure the settings for the Input Board.
8
Output Boards
Create All Click to create all the Output Boards. When you click Create All Output Boards the Configured column check boxes are selected,
Output and you can click in the Edit column to open the iSTAR Output Board Editor to configure an Output Board.
Boards
Delete All When you click Delete All Output Boards, the check boxes in the Configured column are cleared for all Output Boards, and all
Output these Output Boards are immediately deleted (any settings you have configured are lost).
Boards
Output Select the check box in the Configured column and click in the Edit column to open the iSTAR Output Board Editor. From the
Boards 1 - editor you can configure the settings for the Output Board.
8
Readers
Box Description
Create All Click to create all the Readers. When you click Create All Readers the Configured column check boxes are selected, and you
Readers can click in the Edit column to open the iSTAR Reader Editor to configure a Reader.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all Readers, and all these Readers
Readers are immediately deleted (any settings you have configured are lost).
Readers 1 - Select the check box in the Configured column and click in the Edit column to open the iSTAR Reader Editor. From the
4 editor you can configure the settings for the Reader.
You can create up to four Readers in this table for an iSTAR Edge, but if your iSTAR Edge is not a 4-reader model, Readers 3 - 4
will not function.
The Template column shows the template name if you selected a Template prior to creating the Reader.
The Readers can be configured on either the Wiegand tab or on the COM1, COM2, or COM3 tab in any combination, as
long as the total number of Readers does not exceed the maximum allowed.
The iSTAR Edge supports a maximum of either two readers or four readers depending on the model.
You can configure up to two Readers on the Wiegand tab, and the remaining Readers, in any combination, on the COM1,
COM2, and COM3 tabs. See the iSTAR Edge Installation and Configuration Guide for more information about the two
models.
Example:
If you configure two Readers on the iSTAR Edge Wiegand tab, the iSTAR Edge Controller Editor makes the Reader 1
- 2 objects on the COM1 and COM2 tabs unavailable (shaded gray) leaving Reader 3 - 4 objects available.
Box Description
Create All Click to create all the Readers. When you click Create All Readers, the Configured column check boxes are selected, and you
Readers can click in the Edit column to open the iSTAR Reader Editor to configure a Reader.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all Readers, and all these Readers
Readers are immediately deleted (any settings you have configured are lost).
Edit Click in the Edit column to open the iSTAR Reader Editor to configure a Reader. See iSTAR Reader Editor on Page 496.
column
Index This column displays the number for each reader. This number is the physical port number for a Direct Connect Wiegand reader.
column
Configured
Click in this column to create a reader (make it available to be edited) .
column
Name Displays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in this field.
column
Template Click in this column prior to creating the Reader, then click to select a Reader template from the list of available Reader
column templates.
The Template column shows the template name chosen if you selected a Template prior to creating the Reader.
Box Description
Readers 1 Select the check box in the Configured column for a Reader and click located in the Edit column to open the iSTAR Reader
-2 Editor General tab to configure the Options, Triggers, Groups, Status and State Images that are associated with a Reader. See
iSTAR Reader Editor on Page 496 for detailed instructions for configuring iSTAR Readers.
If the row in this table for a particular reader is unavailable for selection (shaded gray) it indicates that this reader number is
configured on one of the COM tabs in the iSTAR Controller Editor.
The Name column displays a name comprised of the Reader Type and the iSTAR Controller name. You can click in this column to
edit the Reader name.
The iSTAR eX can support up to a total of eight Readers if an iSTAR eX Security Key is installed, or four Readers without
the Security Key.
These Readers can be configured on either the Readers tab or on the COM1 or COM2 tabs in any combination, as long as
the total number of Readers does not exceed the maximum allowed.
For iSTAR eX, you can configure up to four of these Readers on the iSTAR eX Wiegand tab, and the remaining Readers, in
any combination, on the COM1 and COM2 tabs. See the iSTAR eX Installation and Configuration Guide for more
information about the iSTAR eX Security Key.
Example:
If you configure Readers 1 and 2 on the iSTAR eX Wiegand tab, the iSTAR eX Controller Editor makes the Reader 1
and 2 objects on the COM1 and COM2 tabs unavailable (shaded gray). Conversely, when you add Readers 3 and 4 to
one of the COMx tabs, the corresponding readers on the Wiegand tab are unavailable.
Box Description
Create All Readers Click to create all the Readers. When you click Create All Readers, the Configured column check boxes are
selected, and you can click in the Edit column to open the iSTAR Reader Editor to configure a Reader.
Delete All Readers When you click Delete All Readers, the check boxes in the Configured column are cleared for all Readers, and all
these Readers are immediately deleted (any settings you have configured are lost).
Box Description
Edit column Click in the Edit column to open the iSTAR Reader Editor to configure a Reader. See iSTAR Reader Editor on
Page 496.
Index column This column displays the number for each reader. This number is the physical port number for a Direct Connect
Wiegand reader.
Configured column Click in this column to create a reader (make it available to be edited).
Name column Displays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in
this field.
Template column Click in this column prior to creating the Reader, then click to select a Reader template from the list of available
Reader templates.
The Template column shows the template name chosen if you selected a Template prior to creating the Reader.
Readers 1 - 8 Select the check box in the Configured column for a Reader and click located in the Edit column to open the
Readers 5 - 8 are only iSTAR Reader Editor General tab to configure the Options, Triggers, Groups, Status and State Images that are
available if the 8 reader associated with a Reader. See iSTAR Reader Editor on Page 496 for detailed instructions for configuring iSTAR
USB key is present in Readers.
the GCM. If the row in this table for a particular reader is unavailable for selection (shaded gray) it indicates that this reader
number is configured on one of the COM tabs in the iSTAR Controller Editor. In Figure 61 on Page 181, for example,
Reader #4 is configured on another tab.
The Name column displays a name comprised of the Reader Type and the iSTAR Controller name. You can click in
this column to edit the Reader name.
The iSTAR eX Contoller COM1 and COM2 tabs have a Protocol drop-down list that lets you choose the type of serial
communications board is connected to the controller:
■ COM1 or COM2 Schlage Wireless PIM on Page 182
■ COM1 or COM2 RM Communications on Page 183
The options available on the COM1 or COM2 tab depend upon which Serial Communications option you select.
To Configure the iSTAR eX COM1 or COM2 Tab for Schlage Wireless PIMs
1. From the iSTAR Ex Controller Editor, click one of the COM tabs.
2. Select Schlage Wireless from the Protocol drop-down list.
3. In the Schlage Wireles PIMs table that appears, create the PIMs that you need by clicking Create All PIMs or by
selecting the Configured check box for only the PIMs you wish to create.
4. Click in the Edit column to configure individual PIMs. See:
■ iSTAR Schlage Wireless PIMs Tab Definitions on Page 166 for definitions for the PIM board fields and buttons.
■ iSTAR PIM-485 Reader I/O Tab on Page 513 for configuration instructions.
5. Click Save and Close to save the settings you have configured on the iSTAR Controller COM tabs.
Figure 62 on Page 183 shows the COM1 and COM2 tabs for an iSTAR eX.
Figure 62: iSTAR eX Controller COM Tabs
The iSTAR eX can support up to four Readers, and an additional four Readers if equipped with an iSTAR eX Security Key.
These Readers can be configured on either the Readers tab or on the COM1 or COM2 tabs, in any combination, as long as
the total number of Readers does not exceed the maximum allowed.
Example:
If you configure two Readers on the iSTAR eX Controller Readers tab and two Readers on the COM1 tab, the Editor
makes the remaining Reader connections on the Reader, COM1, and COM2 tabs unavailable. Sections of the COM
tab are shaded gray (unavailable) to signify that these devices are configured on another tab.
If you select the RM option from the Protocol drop-down list, COM1 and COM2 are configured to support RM bus readers.
The iSTAR eX can support up to four RM reader devices (or eight Readers if the iSTAR eX Security Key is installed). A
total of eight I/8 and eight R/8 devices can also be configured on the iSTAR eX on COM1 and/or COM2.
However you configure iSTAR eX Readers, they must match the setting of the S1 switch on the PMB. The
NOTE S1 switches define which COM port the RM ports are connected to in the hardware. See the iSTAR eX
Installation and Configuration Guide.
Box Description
Input Boards
Create All Click to create all the Input Boards. When you click Create All Input Boards the Configured column check boxes are selected,
Input and you can click in the Edit column to open the iSTAR Input Board Editor to configure an Input Board.
Boards
Delete All When you click Delete All Input Boards, the check boxes in the Configured column are cleared for all Input Boards, and all these
Inputs Input Boards are immediately deleted (any settings you have configured are lost).
Boards
Edit column Click in the Edit column to open the iSTAR Input Board Editor to configure an Input Board. See iSTAR Input Board Editor on
Page 215.
Configured Click in this column to create an Input Board (make it available to be edited) .
column
Name Displays the name for this Input Board. The name is system-generated by default, but you can edit this name by clicking in this field.
column
Input Select the check box in the Configured column and click in the Edit column to open the iSTAR Input Board Editor. From the
Boards 1 - 8 editor you can configure the settings for the Input Board.
Output Boards
Create All Click to create all the Output Boards. When you click Create All Output Boards the Configured column check boxes are selected,
Output and you can click in the Edit column to open the iSTAR Output Board Editor to configure an Output Board.
Boards
Delete All When you click Delete All Output Boards, the check boxes in the Configured column are cleared for all Output Boards, and all
Output these Output Boards are immediately deleted (any settings you have configured are lost).
Boards
Output Select the check box in the Configured column and click in the Edit column to open the iSTAR Output Board Editor. From the
Boards 1 - 8 editor you can configure the settings for the Output Board.
Readers
Create All Click to create all the Readers. When you click Create All Readers the Configured column check boxes are selected, and you
Readers can click in the Edit column to open the iSTAR Reader Editor to configure a Reader.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all Readers, and all these
Readers Readers are immediately deleted (any settings you have configured are lost).
Readers 1 - Select the check box in the Configured column and click in the Edit column to open the iSTAR Reader Editor. From the
8 editor you can configure the settings for the Reader.
You can create up to eight Readers in this table for an iSTAR eX, but if your iSTAR eX does not have an iSTAR eX Security key,
Readers 5-8 will not function.
The Template column shows the template name if you selected a Template prior to creating the Reader.
All of the inputs support event triggers based on their active or inactive states. These triggers can activate alarms, send
emails, run a Roll Call Report, etc.
The Input tab fields and buttons are described in Table 36 on Page 186.
Table 36: Ultra Inputs Tab Definitions
Field/Button Description
Create All Click to create all the Main Board Inputs. When you click Create All Inputs the Configured column check boxes are selected,
Inputs and you can click in the Edit column to open the iSTAR Input Editor to configure an Input.
Delete All When you click Delete All Inputs, the check boxes in the Configured column are cleared for all Main Board Inputs, and all
Inputs these Inputs are immediately deleted (any settings you have configured are lost). You will need to confirm each deletion.
Edit column Click in the Edit column to open the iSTAR Input Editor to configure a Main Board Input. See iSTAR Input Editor on Page
240.
Input Type This column displays the type of each Main Board Input.
column
Name column Displays the name for this Input. The name is system-generated by default, but you can edit this name by clicking in this field.
Template Click in this column, then click to select an Input template to use for creating this Input from the list of available Input
column templates. You can only select a Template prior to creating the input.
Input Type
Tamper Activates when the controller cabinet is opened or removed from its mounting surface.
Select the check box in the Configured column and click in the Edit column to open the iSTAR Input Editor. From the Input
Editor you can configure the settings and link to events through triggers.
Power Failure Monitors the AC power failure output of a battery backup unit. When this alarm input activates, it specifies that the GCM has lost
its primary power source, and is operating on batteries.
Port Power Activates if there is a problem with the power on the port.
RS 485 Port
1/2
CPNI Alarm Activates if the CPNI (Centre for the Protection of National Infrastructure) switch S1-2 is changed.
Tamper, AC power fail, and Low battery inputs must be programmed for UL applications.
NOTE
You must select the correct ACM type used by the controller:
NOTE
■ iSTAR Ultra - select iSTAR Ultra ACM.
■ iSTAR Ultra SE - select iSTAR Ultra ACM SE.
The ACMs listed in the table are not configurable until the ACM type is selected.
Field/Button Description
ACM Type Select the iSTAR ACM type from the ACM Type drop-down menu.
• iSTAR Ultra - select iSTAR Ultra ACM.
• iSTAR Ultra SE - select iSTAR Ultra SE ACM
Create ACM When you click Create ACM the Configured column check boxes are selected, and you can
click in the Edit column to open the iSTAR Ultra ACM Editor to configure the ACM.
Delete ACM When you click Delete ACM, the check boxes in the Configured column are cleared for all
ACMs, and are deleted (all configuration settings are lost).
Index Select the check box in the Configured column and click located in the Edit column to
open the iSTAR Ultra ACM Editor to configure the Inputs, Outputs, and Readers that are
associated with the ACM board.
Field/Button Description
Create ACM When you click Create ACM the Configured column check boxes are selected, and you can click in the Edit column to open
the iSTAR Ultra ACM Editor to configure the ACM.
Delete ACM When you click Delete ACM, the check boxes in the Configured column are cleared for all ACMs, and are deleted (all
configuration settings are lost).
Field/Button Description
Configured The check box in this column must be selected to be able to configure the ACM.
Index Select the check box in the Configured column and click located in the Edit column to open the iSTAR Ultra ACM Editor to
configure the Inputs, Outputs, and Readers that are associated with the ACM board.
See Chapter 7, Configuring the IP-ACM for information about configuring the IP-ACM.
The iSTAR Ultra can support up to 32 Readers. There can be up to 16 ACM Readers and up to 32 Aperio Readers or
Schlage Readers, but the total number of readers cannot exceed 32. If you try to configure any additional readers, an error
message appears. The iSTAR Ultra supports either Aperio or Schlage Wireless Readers. There cannot be a mixture of the
two readers on one iSTAR Ultra.
The ACM Readers can be configured as Wiegand direct connect or RM bus as long as the total number of Readers does
not exceed eight per ACM or sixteen per iSTAR Ultra.
The Aperio Readers can be configured on any of the possible 30 Hubs, in any combination, as long as the total number of
Readers does not exceed 32.
There can be up to 15 Aperio Hubs per COMx port, allowing for a total of 30 Hubs per iSTAR Ultra. Each Hub can support
up to 8, or 1, Assa Abloy Readers with a maximum of 16 readers per COMx port. This provides for a maximum of 32
readers per iSTAR Ultra.
If using a 1 Reader Hub, the maximum is 30 Aperio Readers (i.e., 1 Reader per Hub).
NOTE
Box Description
Aperio Hubs
Create All Click to create all the Aperio Hubs. When you click Create All Hubs the Configured column check boxes are selected, and you
Hubs can click in the Edit column to open the iSTAR Aperio RS-485 Hub Board Editor to configure an Aperio Hub.
Box Description
Delete All When you click Delete All Hubs, the check boxes in the Configured column are cleared for all Hubs, and all these Hubs are deleted
Hubs after you confirm each deletion (any settings you have configured are lost).
Edit Click in the Edit column to open the iSTAR Aperio RS-485 Hub Board Editor to configure an Aperio Hub. See iSTAR Aperio
column RS-485 Hub Board Editor (iSTAR Ultra only) on Page 232.
Index This column displays the number of each Hub (from 1 to 15).
column
Configured Click in this column to create an Aperio Hub (make it available to be edited).
column
Name Displays the name for this Aperio Hub. The name is system-generated by default, but you can edit this name by clicking in this field.
column
Hubs 1 - 15 Select the check box in the Configured column and click in the Edit column to open the iSTAR Aperio RS-485 Hub Board
editor. From the editor you can configure the settings for the Hub.
Schlage PIMs
Create All Click to create all the Schlage PIMs. When you click Create All PIMs the Configured column check boxes are selected, and you
PIMs can click in the Edit column to open the iSTAR Schlage RS-485 PIM Board Editor to configure a Schlage PIM.
Delete All When you click Delete All PIMs, the check boxes in the Configured column are cleared for all PIMs, and all these PIMs are
PIMs deleted after you confirm each deletion (any settings you have configured are lost).
Edit Click in the Edit column to open the iSTAR Schlage RS-485 PIM Board Editor to configure a Schlage PIM.
column
Index This column displays the number of each PIM (from 1 to 16).
column
Configured Click in this column to create a Schlage PIM (make it available to be edited).
column
Name Displays the name for this Schlage PIM. The name is system-generated by default, but you can edit this name by clicking in this field.
column
PIMs 1 - 16 Select the check box in the Configured column and click in the Edit column to open the iSTAR Schlage RS-485 PIM Board editor.
From the editor you can configure the settings for the PIM.
All of the inputs support event triggers based on their active or inactive states. These triggers can activate alarms, send
emails, run a Roll Call Report, etc.
The Input tab fields and buttons are described in Table 40 on Page 192.
Field/Button Description
Create All Click to create all the Main Board Inputs. When you click Create All Inputs the Configured column check boxes are selected,
Inputs and you can click in the Edit column to open the iSTAR Input Editor to configure an Input.
Delete All When you click Delete All Inputs, the check boxes in the Configured column are cleared for all Main Board Inputs, and all
Inputs these Inputs are immediately deleted (any settings you have configured are lost). You will need to confirm each deletion.
Edit column Click in the Edit column to open the iSTAR Input Editor to configure a Main Board Input. See iSTAR Input Editor on Page
240.
Input Type This column displays the type of each Main Board Input.
column
Name column Displays the name for this Input. The name is system-generated by default, but you can edit this name by clicking in this field.
Template Click in this column, then click to select an Input template to use for creating this Input from the list of available Input
column templates. You can only select a Template prior to creating the input.
Input Type
Tamper Activates when the controller cabinet is opened or removed from its mounting surface.
Select the check box in the Configured column and click in the Edit column to open the iSTAR Input Editor. From the Input
Editor you can configure the settings and link to events through triggers.
Power Failure Monitors the AC power failure output of a battery backup unit. When this alarm input activates, it specifies that the GCM has lost
its primary power source, and is operating on batteries.
Port Power Activates if there is a problem with the power on the port.
RS 485 Port 1
CPNI Alarm Activates if the CPNI (Centre for the Protection of National Infrastructure) switch S1-2 is changed.
Tamper, AC power fail, and Low battery inputs must be programmed for UL applications.
NOTE
The iSTAR Ultra LT can support up to 8 or 16 readers, with connection to a maximum of sixteen IP-ACM Ethernet Door
Modules.
If you try to configure any additional readers, an error message appears. The iSTAR Ultra LT supports either Aperio or
Schlage Wireless Readers. There cannot be a mixture of the two readers on one iSTAR Ultra LT .
The Aperio Readers can be configured on any of the possible 8 Hubs, in any combination, as long as the total number of
Readers does not exceed 8.
There can be up to 8 or 16 Aperio Hubs for the COM port, allowing for a total of 8 or 16 Hubs per iSTAR Ultra LT . Each Hub
can support up to 8 or 16, ASSA ABLOY Readers with a maximum of 8 or 16 readers per COM port. This provides for a
maximum of 8 or 16 readers per iSTAR Ultra LT .
If using a 1 Reader Hub, the maximum is 8 Aperio Readers (i.e., 1 Reader per Hub).
NOTE
Box Description
Aperio Hubs
Create All Click to create all the Aperio Hubs. When you click Create All Hubs the Configured column check boxes are selected, and you
Hubs can click in the Edit column to open the iSTAR Aperio RS-485 Hub Board Editor to configure an Aperio Hub.
Delete All When you click Delete All Hubs, the check boxes in the Configured column are cleared for all Hubs, and all these Hubs are deleted
Hubs after you confirm each deletion (any settings you have configured are lost).
Edit Click in the Edit column to open the iSTAR Aperio RS-485 Hub Board Editor to configure an Aperio Hub. See iSTAR Aperio
column RS-485 Hub Board Editor (iSTAR Ultra only) on Page 232.
Index This column displays the number of each Hub (from 1 to 15).
column
Configured Click in this column to create an Aperio Hub (make it available to be edited).
column
Name Displays the name for this Aperio Hub. The name is system-generated by default, but you can edit this name by clicking in this field.
column
Hubs 1 - 15 Select the check box in the Configured column and click in the Edit column to open the iSTAR Aperio RS-485 Hub Board
editor. From the editor you can configure the settings for the Hub.
Schlage PIMs
Create All Click to create all the Schlage PIMs. When you click Create All PIMs the Configured column check boxes are selected, and you
PIMs can click in the Edit column to open the iSTAR Schlage RS-485 PIM Board Editor to configure a Schlage PIM.
Delete All When you click Delete All PIMs, the check boxes in the Configured column are cleared for all PIMs, and all these PIMs are
PIMs deleted after you confirm each deletion (any settings you have configured are lost).
Box Description
Edit Click in the Edit column to open the iSTAR Schlage RS-485 PIM Board Editor to configure a Schlage PIM.
column
Index This column displays the number of each PIM (from 1 to 16).
column
Configured Click in this column to create a Schlage PIM (make it available to be edited).
column
Name Displays the name for this Schlage PIM. The name is system-generated by default, but you can edit this name by clicking in this field.
column
PIMs 1 - 16 Select the check box in the Configured column and click in the Edit column to open the iSTAR Schlage RS-485 PIM Board editor.
From the editor you can configure the settings for the PIM.
Table 42 on Page 195 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Board Outputs tab.
Table 42: iSTAR Ultra IP-ACM Outputs Tab General Tab Definitions
Field/Button Description
Name Displays the name for this Output board. The name is system-generated by default, but you can edit this name by clicking this
field.
Description Enter a textual comment about the Output board, such as its location or purpose. This text is for information only.
Partition This read-only field identifies the Partition in which this Output board resides.
Maintenance Click to put the iSTAR Outboard Board into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Location
Controller This read-only field identifies the iSTAR Controller to which this Output is attached.
Board This read-only field identifies the iSTAR Controller board to which this Output board is attached.
Board Index This read-only field identifies the board index (which represents the SW1 address switch setting on the R/8 board) for this Output
board.
Outputs
Create All Click to create all Outputs. The check boxes in the Configured column are set to .
Outputs
Field/Button Description
Delete All Click to delete all Outputs. The check boxes in the Configured column are set to .
Outputs
Edit column Click in this column to open the iSTAR Output Editor to edit this Output.
NOTE: The Configured check box must be selected to open the Output Editor.
Index column This read-only field identifies the position of each Output (1 - 2) on the IP-ACM board.
Name column Displays the system-generated name for this Output. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Output. If the Output is not yet configured, you can click in this column, then click to
column select an Output Template. If the Configured column displays , this field cannot be edited.
Field/Button Description
Maintenance Mode Click to put the IP-ACM into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Board Location
Offline Mode
Disable offline mode Click the check box to disable offline mode on this IP-ACM.
NOTE: This selection will override the Offline Mode of all IP-ACMs selections in the iSTAR Controller Editor IP-
ACMs tab for this IP-ACM.
See IP-ACM Offline Mode Configuration Information on Page 288.
If using online mode, all components of the door must come from the same IP-ACM board.
Switch Port (J5) Options Select the check box to enable the J5 Switch Port. Clear this check box to disable this port. This check box is selected by
(option for IP-ACM v2 default.
only)
Table 44 on Page 198 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Wiegand tab.
Table 44: iSTAR Ultra IP-ACM Wiegand Tab Definitions
Box Description
Create All Click to create all the Readers. When you click Create All Readers, the Configured column check boxes are selected, and you
Readers can click in the Edit column to open the iSTAR Reader Editor to configure a direct connect Wiegand Reader.
Box Description
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all Readers, and all these Readers
Readers are immediately deleted (any settings you have configured are lost).
Edit Click in the Edit column to open the iSTAR Reader Editor to configure a Reader. See iSTAR Reader Editor on Page 496.
column
Index This column displays the number for each reader. This number is the physical port number for a Direct Connect Wiegand reader.
column
Name Displays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in this field.
column
Template Click in this column prior to creating the Reader, then click to select a Reader template from the list of available Reader
column templates.
The Template column shows the template name chosen if you selected a Template prior to creating the Reader.
Readers 1 Select the check box in the Configured column for a Reader and click located in the Edit column to open the iSTAR Reader
-2 Editor General tab to configure the Keypad, Triggers, Groups, Status and State Images that are associated with a Reader. See
iSTAR Reader Editor on Page 496 for detailed instructions for configuring iSTAR Readers.
The Name column displays a name comprised of the Reader Type and the iSTAR Controller name. You can click in this column to
edit the Reader name.
The iSTAR Device Port Editor, accessed by clicking in the Configured check box of the port and click Edit, allows you to
select the RM, BLE, or OSDP protocols. See IP-ACM iSTAR Device Port Dialog Box on Page 302
Table 45 on Page 199 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM RS-485 tab.
Table 45: iSTAR Ultra IP-ACM Board RS-485 Tab Definitions
Field/Button Description
Create All Click to create the RS-485 Ports. When you click Create All Ports the Configured column check boxes are selected, and you
Ports can click in the Edit column to open the iSTAR Device Port Editor to configure an RS-485 Port.
Delete All When you click Delete All Ports, the check boxes in the Configured column are cleared for all Ports, and all Ports are
Ports immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Device Port Editor to configure Device Ports for the IP-ACM. See iSTAR Ultra
ACM RS-485 Device Port Editor on Page 204.
Index column This column displays the number for each Device Port.
Field/Button Description
Configured Click in this column to create a Device Port (make it available to be edited).
column
Name column Displays the name for this Device Port. The name is system-generated by default, but you can edit this name by clicking in click in
this field.
Device Ports 1 Select the check box in the Configured column for a Device Port and click located in the Edit column to open the iSTAR
-2 Device Port Editor General tab to configure the Readers and ACM extensions that are associated with the Device Port. See
iSTAR Reader Editor on Page 496 for detailed instructions for configuring iSTAR Device Ports.
The Name column displays a name comprised of the Device Port and the iSTAR Controller name. You can click in this column to
edit the Device Port name.
You can use an existing Input Template to create one or more of the IP-ACM Board Inputs. Click in the Template Column,
then click . A list of available iSTAR Input Templates appears. Click on the Template you wish to use. See Using
Templates for Controller Inputs, Outputs, and Readers on Page 44 for more detailed information about using Templates to
create Inputs.
Table 46 on Page 200 provides definitions for the buttons and fields on the iSTAR Ultra IP-ACM Inputs tab.
Table 46: iSTAR Ultra IP-ACM Board Inputs Tab Definitions
Field/Button Description
Tamper The Tamper input activates when the controller cabinet is opened or removed from its mounting surface.
NOTE: For UL applications, this field must be enabled.
Select the check box in the Configured column and click located in the Edit column to open the iSTAR Input Editor
General tab to configure the Tamper input. From the Input Editor you can configure the Options, Triggers, Groups, Status and
State Images that are associated with the Tamper Input.
The Template column shows the template name chosen if you selected a Template prior to creating the Input.
Communication A logical unsupervised input that reflects the state of the communication between the GCM board and Processor-A on this IP-
Fail ACM board.
Field/Button Description
Lock Power IP-ACM can provide power for the locks directly from the 2 Output connectors (Lock Power 1 & 2). There are automatic over-
Alarm Status 1 current shut-off switches on each Lock Power. The Lock Power Alarm Status inputs go Active when the over-current shut-off
Lock Power switches are active (i.e., when Lock Power has been shut off).
Alarm Status 2
Inputs 1 These standard general purpose supervised inputs are available on iSTAR Ultra IP-ACM boards.
through 4
Table 47 on Page 201 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Board Status tab.
Table 47: iSTAR Ultra IP-ACM Board Status Tab Definitions
Field/Button Description
The iSTAR Ultra ACM Board dialog box is accessed from the iSTAR Controller editor Boards tab.
For more information see the iSTAR Controller Installation and Configuration Guide.
Box Description
Create All Click to create all the Readers. When you click Create All Readers, the Configured column check boxes are selected, and you
Readers can click in the Edit column to open the iSTAR Reader Editor to configure a direct connect Wiegand Reader.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all Readers, and all these Readers
Readers are immediately deleted (any settings you have configured are lost).
Edit Click in the Edit column to open the iSTAR Reader Editor to configure a Reader. See iSTAR Reader Editor on Page 496.
column
Index This column displays the number for each reader. This number is the physical port number for a Direct Connect Wiegand reader.
column
Box Description
Name Displays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in this field.
column
Template Click in this column prior to creating the Reader, then click to select a Reader template from the list of available Reader
column templates.
The Template column shows the template name chosen if you selected a Template prior to creating the Reader.
Readers 1 Select the check box in the Configured column for a Reader and click located in the Edit column to open the iSTAR Reader
-8 Editor General tab to configure the Keypad, Triggers, Groups, Status and State Images that are associated with a Reader. See
iSTAR Reader Editor on Page 496 for detailed instructions for configuring iSTAR Readers.
The Name column displays a name comprised of the Reader Type and the iSTAR Controller name. You can click in this column to
edit the Reader name.
Field/Button Description
RS-485 Ports
Create All Click to create the RS-485 Ports. When you click Create All Ports the Configured column check boxes are selected, and you
Ports can click in the Edit column to open the iSTAR Device Port Editor to configure an RS-485 Port.
Delete All When you click Delete All Ports, the check boxes in the Configured column are cleared for all Ports, and allPorts are
Ports immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Device Port Editor to configure Device Ports for the iSTAR Ultra. See iSTAR
Reader Editor on Page 496.
Index column This column displays the number for each Device Port.
Configured Click in this column to create a Device Port (make it available to be edited).
column
Name column Displays the name for this Device Port. The name is system-generated by default, but you can edit this name by clicking in click in
this field.
Field/Button Description
Device Ports 1 Select the check box in the Configured column for a Device Port and click located in the Edit column to open the iSTAR
-8 Device Port Editor General tab to configure the Readers and ACM extensions that are associated with the Device Port. See
iSTAR Reader Editor on Page 496 for detailed instructions for configuring iSTAR Device Ports.
The Name column displays a name comprised of the Device Port and the iSTAR Controller name. You can click in this column to
edit the Device Port name.
Field Description
Controller This field identifies the controller for this ACM RS-485 Device Port.
Port Number This field identifies the index number of the Device Port on the ACM for the Readers.
You can use an existing Reader Template to create one or more of the RS-485 Readers. Click in the Template Column,
then click . A list of available iSTAR Reader Templates appears. Click on the Template you wish to use. See Using
Templates for Controller Inputs, Outputs, and Readers on Page 44 for more detailed information about using Templates to
create Readers.
Field/Button Description
Create All Click to create all the readers. When you click Create All Readers the Configured column check boxes are selected, and you
Readers can click in the Edit column to edit that reader.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all readers, and all these readers
Readers are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Reader Editor to configure an Reader. See iSTAR Reader Editor on Page 496.
Name column Displays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in click in this
field.
Template The Template column shows the template name if you selected a Template prior to creating the Readers.
column
Click in this column, then click to select a Reader template to use for creating this Reader from the list of available Reader
templates. You can only select a Template prior to creating the Reader.
Configuring the iSTAR Ultra RS-485 Device Port ACM Ext Tab
When you configure the iSTAR Ultra RS-485 Device Port ACM Ext tab, you are defining the Input boards and Output
boards that are attached to the port. You can then click to open the Input Boards Editor to configure individual Input Boards,
or open the Output Boards Editor to configure individual Output Boards.
2. Click to open the iSTAR Ultra ACM Board editor. Access the Input Board Editor for the Input Board you wish to
edit (see iSTAR Ultra Controller ACM Board Editor on Page 202).
3. Click the RS-485 tab.
4. Create an RS-485 port by clicking in the Configure column, then click to open the iSTAR Ultra Device Port editor.
5. Click the ACM Ext tab.
6. Create an Input board by clicking in the Configure column for one of the Input Boards (1-8), then click to open the
iSTAR Input Board editor. See the iSTAR Input Board Editor on Page 215 for configuration instructions.
7. Create an Output board by clicking in the Configure column for one of the Output Boards (1-8), then click .to open
the iSTAR Output Board editor. See the iSTAR Output Board Editor on Page 220 for configuration instructions.
8. When you have finished configuring the Inputs on the iSTAR Ultra RS-485 Device Port ACM Ext tab, click Save and
Close to save the settings you have configured.
Field/Button Description
Input Boards
Create All Click to create all the Input Boards. When you click Create All Boards the Configured column check boxes are selected, and
Boards you can click in the Edit column to edit that Input Board.
Delete All When you click Delete All Boards, the check boxes in the Configured column are cleared for all Input Boards, and all these
Boards Input Boards are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Input Board Editor. See iSTAR Input Board Editor on Page 215.
Index column This column displays the number of each Input Board.
Configured Click in this column to create an Input Board (make it available to be edited).
column
Name column Displays the name for this Input board. The name is system-generated by default, but you can edit this name by clicking in click in
this field.
Output Boards
Create All Click to create all the Output Boards. When you click Create All Boards the Configured column check boxes are selected, and
Boards you can click in the Edit column to edit that Output Board.
Delete All When you click Delete All Boards, the check boxes in the Configured column are cleared for all Output Boards, and all these
Boards Output Boards are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Output Board Editor. See iSTAR Output Board Editor on Page 220.
Index column This column displays the number of each Output Board.
Table 52: iSTAR Ultra RS-485 Device Port ACM Ext Tab Definitions (continued)
Field/Button Description
Configured Click in this column to create an Output Board (make it available to be edited).
column
Name column Displays the name for this Output board. The name is system-generated by default, but you can edit this name by clicking in click
in this field.
Field/Button Description
Reader Power Voltage reported for Readers. Reader power is the basic power to the GCM and ACMs.
Typically reads about 13.8V.
The ACM Board dialog box is accessed from the iSTAR Controller editor Boards tab.
For more information see the iSTAR Pro Installation and Configuration Guide.
Field/Button Description
Name Displays the name for this ACM board. The name is system-generated
by default, but you can edit this name by clicking in this field.
Description Enter a textual comment about the ACM board, such as its location or
purpose. This text is for information only.
Maintenance Mode Click to put the iSTAR ACM board into Maintenance Mode. See
Chapter 3: Maintenance Mode for more information.
Partition This read-only field identifies the Partition in which the iSTAR Controller
for this ACM Board resides.
Board Location
Field/Button Description
Controller This read-only field identifies the Controller to which this board is
attached.
ACM Number/IP-ACM Number This read-only field displays the number of the ACM board or the
iSTAR Ultra IP-ACM number.
Board Type This read-only field displays the iSTAR ACM type.
You can use an existing Input Template to create one or more of the ACM Board Inputs. Click in the Template Column,
then click . A list of available iSTAR Input Templates appears. Click on the Template you wish to use. See Using
Templates for Controller Inputs, Outputs, and Readers on Page 44 for more detailed information about using Templates to
create Inputs.
Field/Button Description
Create All Inputs Click to create all the Inputs. When you click Create All Inputs the Configured column check
boxes are selected, and you can click in the Edit column to edit that Input.
Delete All Inputs When you click Delete All Inputs, the check boxes in the Configured column are cleared for
all Inputs, and all these Inputs are immediately deleted (any settings you have configured are
lost).
Edit column Click in the Edit column to open the iSTAR Input Editor to configure an Input. See iSTAR
Input Editor on Page 240.
Configured column Click in this column to create an Input (make it available to be edited) .
Name column Displays the name for this Input. The name is system-generated by default, but you can edit
this name by clicking in this field.
Field/Button Description
Template column The Template column shows the template name if you selected a Template prior to creating
the Input.
Click in this column, then click to select an Input template to use for creating this Input
from the list of available Input templates. You can only select a Template prior to creating the
input.
Inputs These standard general purpose supervised inputs are available on iSTAR Pro ACM boards.
Field/Button Description
Special Purpose Inputs (iSTAR Ultra/ Ultra SE/ Ultra Video only)
Tamper The Tamper input activates when the controller cabinet is opened or removed from its
mounting surface.
NOTE: For UL applications, this field must be enabled.
Select the check box in the Configured column and click located in the Edit column to
open the iSTAR Input Editor General tab to configure the Tamper input. From the Input Editor
you can configure the Options, Triggers, Groups, Status and State Images that are
associated with the Tamper Input.
The Template column shows the template name chosen if you selected a Template prior to
creating the Input.
Comm Fail Processor A logical unsupervised input that reflects the state of the communication between the GCM
1 board and Processor-A on this ACM board.
Comm Fail Processor A logical unsupervised input that reflects the state of the communication between the GCM
2 board and Processor-B on this ACM board.
FAI Relay Control FAI Relay Control. When the FAI signal is true, the HW drives all selected relays to activate.
Each relay has a switch indicating whether it is selected to behave in this way.
FAI Interlock Key The FAI K input is usually a key switch. It is supervised as NO. It is used in conjunction with
Latch mode. If latching is enabled, the F signal will turn on all selected outputs. They will stay
that way until the Fire Chief inserts the key in the key switch and announces all clear.
Table 56: iSTAR Ultra / Ultra SE/ Ultra Video ACM Board Inputs Tab Definitions (continued)
Field/Button Description
Inputs 1 through 24 These standard general purpose supervised inputs are available on iSTAR Ultra ACM
(Ultra and Ultra Video) boards.
Inputs 1 though 16
Ultra SE (Ultra Mode)
You can use an existing Output Template to create one or more of the ACM Board Outputs. Click in the Template Column,
then click . A list of available iSTAR Output Templates appears. Click on the Template you wish to use. See Using
Templates for Controller Inputs, Outputs, and Readers on Page 44 for more detailed information about using Templates to
create Outputs.
Field/Button Description
Create All Click to create all the outputs. When you click Create All Outputs the Configured column check boxes are selected, and you
Outputs can click in the Edit column to edit that output.
Delete All When you click Delete All Outputs, the check boxes in the Configured column are cleared for all outputs, and all these outputs
Outputs are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Output Editor to configure an Output. See iSTAR Output Editor on Page 248.
Name column Displays the name for this Output. The name is system-generated by default, but you can edit this name by clicking in this field.
Template The Template column shows the template name if you selected a Template prior to creating the Outputs.
column
Click in this column, then click to select an Output template to use for creating this Output from the list of available Output
templates. You can only select a Template prior to creating the Output.
Field/Button Description
Outputs 1 These outputs can be used for a Fire Alarm Interface (FAI). They are rated at 5 Amps, and are socket mounted.
through 8
Click in the Configure column, then click in the Edit column to open the iSTAR Output Editor to configure a Primary
Output. See iSTAR Output Board Editor on Page 220
Outputs 1 These outputs cannot be used for a Fire Alarm Interface (FAI). They are rated at 0.75 or 1 Amp, and are permanently soldered
through 8 to the ACM.
Click in the Configure column, then click in the Edit column to open the iSTAR Output Editor to configure a Secondary
Output. See iSTAR Output Board Editor on Page 220
You can use an existing Reader Template to create one or more of the ACM Board Readers. Click in the Template
Column, then click . A list of available iSTAR Reader Templates appears. Click on the Template you wish to use. See
Using Templates for Controller Inputs, Outputs, and Readers on Page 44 for more detailed information about using
Templates to create Readers.
Field/Button Description
Create All Click to create all the readers. When you click Create All Readers the Configured column check boxes are selected, and you
Readers can click in the Edit column to edit that reader.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all readers, and all these readers
Readers are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Reader Editor to configure an Reader. See iSTAR Reader Editor on Page 496.
Name column Displays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in this field.
Template The Template column shows the template name if you selected a Template prior to creating the Readers.
column
Click in this column, then click to select a Reader template to use for creating this Reader from the list of available Reader
templates. You can only select a Template prior to creating the Reader.
Field/Button Description
Input Boards
Create All Click to create all the Input Boards. When you click Create All Boards the Configured column check boxes are selected, and
Boards you can click in the Edit column to edit that Input Board.
Delete All When you click Delete All Boards, the check boxes in the Configured column are cleared for all Input Boards, and all these
Boards Input Boards are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Input Board Editor. See iSTAR Input Board Editor on Page 215.
Index column This column displays the number of each Input Board.
Field/Button Description
Configured Click in this column to create an Input Board (make it available to be edited).
column
Name column Displays the name for this Input board. The name is system-generated by default, but you can edit this name by clicking in this
field.
Output Boards
Create All Click to create all the Output Boards. When you click Create All Boards the Configured column check boxes are selected, and
Boards you can click in the Edit column to edit that Output Board.
Delete All When you click Delete All Boards, the check boxes in the Configured column are cleared for all Output Boards, and all these
Boards Output Boards are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Output Board Editor. See iSTAR Output Board Editor on Page 220.
Index column This column displays the number of each Output Board.
Configured Click in this column to create an Output Board (make it available to be edited).
column
Name column Displays the name for this Output board. The name is system-generated by default, but you can edit this name by clicking in this
field.
The iSTAR Input Board editor (see Figure 68 on Page 216) has the following tabs:
■ iSTAR Input Board General Tab
Lists the Inputs and Status Inputs on an I/8 board that is connected to an iSTAR Classic/Pro, iSTAR eX, or iSTAR
Edge. See iSTAR Input Board General Tab on Page 218.
■ iSTAR Input Board Group Tab
If you have created a Group containing iSTAR Input Boards and added this Input Board to it, the iSTAR Input Board
editor also displays a Group tab.
This tab lists the Input Board groups to which this Input Board belongs. See Groups Tab for Hardware Devices on
Page 36 for information on using the Group tab for the iSTAR Input board.
2. In the ACMs table on this tab, click in the Edit column for the ACM that contains the Input board you want to Edit.
The ACM Board Editor opens.
3. Click the ACM Ext tab.
4. In the Input Boards table on this tab, click in the Edit column for the Input board you want to Edit.
5. The iSTAR Input Board Editor opens.
To Access the iSTAR Input Board Editor from the Hardware Tree
1. Navigate from your iSTAR Controller in the Hardware Tree to the appropriate COM Board (on an iSTAR eX or iSTAR
Edge Controller) or ACM Board (iSTAR Classic/Pro Controller).
2. Click on Input Boards, as shown in Figure 69 on Page 217. This figure shows the hardware tree for an iSTAR eX on
the left and an iSTAR Pro on the right.
Figure 69: iSTAR Input Board in the Hardware Tree
3. Double-click on the Input Board you wish to edit. The iSTAR Input Board Editor opens.
4. Click in the Edit column to open the iSTAR Input Editor to configure individual Inputs. See the iSTAR Input Editor
on Page 240 for configuration instructions.
5. If you wish to use an Input Template to configure one or more of the I/8 board Status Inputs, click in the Template
column, then click to open a dialog box listing the available Input Templates. See Using Templates for Controller
Inputs, Outputs, and Readers on Page 44 for more information.
6. Create the Status Inputs that you need by clicking Create All Inputs or by selecting the Configured check box for
only the Inputs you wish to create.
7. Click in the Edit column to configure individual Status Inputs. See the definitions of the Status Inputs in Table 60
on Page 218 and see iSTAR Input Editor on Page 240.
8. When you have finished configuring the Inputs on the Input Board Editor General tab, click Save and Close to save
the settings you have configured on the iSTAR Input Board editor.
Field/Button Description
Identification
Name Displays the name for this Input board. The name is system-generated by default, but you can edit this name by clicking in this
field.
Description Enter a textual comment about the Input Board, such as its location or purpose. This text is for information only.
Maintenance Click to put the Input Board into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Partition This read-only field identifies the Partition in which this Input board resides.
Controller This read-only field identifies the iSTAR Controller to which this Input board is attached.
Location
Board This read-only field identifies the iSTAR Controller board to which this Input board is attached.
Board Index This read-only field identifies the board index (which represents the SW1 address switch setting on the I/8 board) for this Input
board.
Field/Button Description
Inputs
Create All Click to create all eight Inputs. The check boxes in the Configured column are set to .
Inputs
Delete All Click to delete all eight Inputs. The check boxes in the Configured column are set to .
Inputs
Edit column Click in this column to open the iSTAR Input Editor to edit this Input.
Index column This read-only field identifies the position of each Input (P1 - P8) on the I/8 board.
Name column Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to select
column an Input Template. If the Configured column displays , this field cannot be edited.
Status Inputs
Create All Click to create the Tamper and Communications Fail Inputs. The check boxes in the Configured column are set to .
Inputs
Delete All Click to delete the Tamper and Communications Fail Inputs. The check boxes in the Configured column are set to .
Inputs
Edit column Click in this column to open the iSTAR Input Editor to edit this Input.
Name column Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to select
column an Input Template. If the Configured column displays , this field cannot be edited.
The iSTAR Output Board editor (see Figure 70 on Page 220) has the following tabs:
■ iSTAR Output Board General Tab
Lists the Outputs and Status Inputs on an R/8 board that is connected to an iSTAR Classic/Pro, iSTAR eX, or iSTAR
Edge. See iSTAR Output Board General Tab on Page 222.
■ iSTAR Output Board Group Tab
If you have created a Group containing iSTAR Output Boards and added this Output Board to it, the iSTAR Output
Board editor also displays a Group tab.
This tab lists the Output Board groups to which this Output Board belongs. See Groups Tab for Hardware Devices on
Page 36 for information on using the Group tab for the iSTAR Output Board.
Figure 70: iSTAR Output Board Editor
■ To Access the iSTAR Output Board Editor (iSTAR Classic/Pro Controller) on Page 221
■ To Access the iSTAR Output Board Editor from the Hardware Tree on Page 221
To Access the iSTAR Output Board Editor from the Hardware Tree
1. Navigate from your iSTAR Controller in the Hardware Tree to the appropriate COM Board (on an iSTAR eX or iSTAR
Edge Controller) or ACM Board (iSTAR Classic/Pro Controller).
2. Click on Output Boards, as shown in Figure 71 on Page 221. This figure shows the hardware tree for an iSTAR eX on
the left and an iSTAR Pro on the right.
Figure 71: iSTAR Output Board in the Hardware Tree
3. Double-click on the Output Board you wish to edit. The iSTAR Output Board Editor opens (see iSTAR Output Board
Editor on Page 220).
Field/Button Description
Identification
Name Displays the name for this Output board. The name is system-generated by default, but you can edit this name by clicking this
field.
Field/Button Description
Description Enter a textual comment about the Output board, such as its location or purpose. This text is for information only.
Maintenance Click to put the iSTAR Outboard Board into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Partition This read-only field identifies the Partition in which this Output board resides.
Location
Controller This read-only field identifies the iSTAR Controller to which this Output board is attached.
Board This read-only field identifies the iSTAR Controller board to which this Output board is attached.
Board Index This read-only field identifies the board index (which represents the SW1 address switch setting on the R/8 board) for this Output
board.
Outputs
Create All Click to create all eight Outputs. The check boxes in the Configured column are set to .
Outputs
Delete All Click to delete all eight Outputs. The check boxes in the Configured column are set to .
Outputs
Edit column Click in this column to open the iSTAR Output Editor to edit this Output.
Index column This read-only field identifies the position of each Output (P1 - P8) on the R/8 board.
Name column Displays the system-generated name for this Output. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Output. If the Output is not yet configured, you can click in this column, then click to
column select an Output Template. If the Configured column displays , this field cannot be edited.
Status Inputs
Create All Click to create the Tamper and Communications Fail Inputs. The check boxes in the Configured column are set to .
Inputs
Delete All Click to delete the Tamper and Communications Fail Inputs. The check boxes in the Configured column are set to .
Inputs
Edit column Click in this column to open the iSTAR Input Editor to edit this Input.
Field/Button Description
Name column Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to select
column an Input Template. If the Configured column displays , this field cannot be edited.
The protocol cannot be changed while any Schlage PIM or Aperio Hub exists.
NOTE
Schlage addresses are one less than the C•CURE index. For example, if you setup a reader on Schlage
NOTE address 1, then it's C•CURE index 2.
The iSTAR eX and iSTAR Pro support the same PIMs and Locks through the RS-485 ports on the Pro
NOTE GCM and the eX PMB board. The RM ports on the eX PMB are multiplexed to the COM1 and COM2 ports
that are visible in the C•CURE 9000 software.
Summary Tables
The tables in this section provides a matrix of the possible connections between Schlage devices and iSTARs and apCs.
AD400 Wireless
Controller/Panel Locks RS485 RSI Wiegand Signal (D0/D1) to Magnetic Signal (CLK/DATA) to
Supported Chain Panel Panel
iSTAR Ultra AD400 (All styles) PIM400-485 PIM400-TD2 to ACM Wiegand PIM400-TD2 to RM4x to ACM RM
iSTAR Pro RSI to GCM PIM400-TD2 to RM4x to ACM
iSTAR Classic RM
iSTAR eX AD400 (All styles) PIM400-485 PIM400-TD2 to GCM Wiegand PIM400-TD2 to RM4x to PMB RM
RSI to PMB PIM400-TD2 to RM4x to PMB
RM
iSTAR Edge AD400 (All styles) PIM400-TD2 to Edge Wiegand PIM400-TD2 to RM4x to Edge RM
PIM400-TD2 to RM4x to Edge
RM
apC/8X AD400 (All styles) PIM400-TD2 to WPSC Wiegand PIM400-TD2 to RM4x to apC RM
PIM400-TD2 to RM4x to apC RM
apC/L AD400 (All styles) PIM400-TD2 to RM4x to apC/L PIM400-TD2 to RM4x to apC/L RM
RM
The AD401 (FIPS-201) configuration only supports a Multi-technology reader with Keypad and Wiegand
NOTE signaling.
Controller/Panel Locks Supported RS485 RSI Wiegand Signal (D0/D1) Magnetic Signal (CLK/DATA)
Chain to Panel to Panel
iSTAR Ultra AD300 (All Built in PIM400-485 RSI PIB300-TD2 to ACM Wiegand PIB300-TD2 to RM4x to ACM RM
iSTAR Pro styles) to GCM PIB300-TD2 to RM4x to ACM
iSTAR Classic RM
iSTAR eX AD300 (All Built in PIM400-485 RSI PIB300-TD2 to GCM Wiegand PIB300-TD2 to RM4x to PMB RM
styles) to PMB PIB300-TD2 to RM4x to PMB
RM
iSTAR Edge AD300 (All PIB300-TD2 to Edge Wiegand PIB300-TD2 to RM4x to Edge RM
styles) PIB300-TD2 to RM4x to Edge
RM
The AD301 (FIPS-201) configuration only supports a Multi-technology reader with Keypad and Wiegand
NOTE signaling.
Controller/Panel Locks Supported RS485 RSI Wiegand Signal (D0/D1) Magnetic Signal (CLK/DATA)
Chain to Panel to Panel
Controller/Panel Locks Supported RS485 RSI Wiegand Signal (D0/D1) Magnetic Signal (CLK/DATA)
Chain to Panel to Panel
iSTAR Pro Direct TD2, PIB to ACM 16 16 16 2 Readers per TD2 or PIB
iSTAR Edge 1 door TD2, PIB to Edge 1 1 1 2 Readers per TD2 or PIB
Direct board
iSTAR Edge 2 door TD2, PIB to Edge 2 2 2 2 Readers per TD2 or PIB
Direct board
iSTAR Edge 4 door TD2, PIB to Edge 4 4 4 2 Readers per TD2 or PIB
Direct board
You select the type of Hub you want to configure by choosing a type from the HUB Type drop-down list. That selection
determines the options that are available on the other tabs.
To access the iSTAR Aperio RS-485 Hub Board editor General tab, click on the COM 1 or COM 2 tab in the iSTAR
Controller editor dialog box. Then, click on Edit in the row name of the RS-485 Port that you want to edit.
Figure 73 on Page 233 shows the iSTAR Aperio RS-485 Hub Board General tab.
Field/Button Description
Description You can enter a textual description of the Aperio Board in the Description field.
Maintenance Mode Click to put the Aperio RS-485 Hub Board into Maintenance Mode. See Chapter 3: Maintenance Mode for more
information.
HUB Type This drop-down list allows you to select the type of Aperio board you are configuring. The default selection is 8 Port Hub
HUB Number This read-only field contains the HUB number - the same HUB Index number as shown on the iSTAR Ultra COM1/COM2
Tabs on Page 189.
Field/Button Description
Communication This read-only field displays whether the controller is in Online, Offline or Unknown state.
Status
Save and Close Click to save your configuration changes and close the iSTARAperio Hub Board editor.
Field/Button Description
Create All Click to create the Communication Fail Input. When you click Create All Inputs, the Configured column check box is selected,
Inputs and you can click in the Edit column to open the iSTAR Input editor (see iSTAR Input Editor on Page 240.
Delete All When you click Delete Input, the check box in the Configured column is cleared for the Communications Fail Input, and the
Inputs Input is deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the Input Editor to configure the Communications Fail Input. See iSTAR Input Editor on
Page 240.
Input type This column displays the input type (Communications Fail).
column
Configured Click in this column to create the Communications Fail Input (make it available to be edited) .
column
Name column Displays the name for this Input. The name is system-generated, but you can edit the name.
Save and Click to save your configuration changes and close the Aperio Hub Board editor.
Close
The following Aperio Reader types can be configured: C100, E100, L100, PR100, IN100, A100, H100, K100, M100,
KS100, R100, AS100, and Generic types.
Field/Button Description
Create All Click to create all 8 readers. When you click Create All Readers the Configured column check boxes are selected, and you can
Readers click in the Edit column to open the iSTAR Aperio Reader Editor to configure a Reader. See iSTAR Aperio Reader Editor
on Page 516.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all 8 Readers, and all 8
Readers Readers are deleted (any settings you have configured are lost).
NOTE: If you Delete all Readers on this tab, the Aperio Door objects that were created automatically for these readers are also
deleted.
Edit column Click in the Edit column to open the iSTAR Aperio Reader editor to configure a Reader. See iSTAR Aperio Reader Editor
on Page 516.
Name column Displays the name for this Reader. The name is system-generated, and the Name field is editable.
Save and Click to save your configuration changes and close the iSTAR Aperio Hub Board editor.
Close
If you choose the AD300 (AD300 Series Locks), the Input tab is removed, because the AD300 does not support a Tamper
Input.
Figure 74 on Page 237 shows the iSTAR PIM-485 Board General tab.
Field/Button Description
Description You can enter a textual description of the PIM Board in the Description field.
Maintenance Click to put the iSTAR PIM-485 Board into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
PIM Type This drop-down list allows you to select the type of PIM board you are configuring.
• PIM400-485 (AD400 Series Locks)
• AD300 (AD300 Series Locks)
• PIM-485 (WA Series Locks)
Field/Button Description
PIM Number This read-only field contains the PIM number - the same PIM Index number as shown on the iSTAR Schlage Wireless PIMs Tab
on Page 165 or the iSTAR eX COM1/COM2 Tabs on Page 182.
Wake on Wake on Radio allows a battery-powered lock device to receive an immediate command from the iSTAR panel that is out of
Radio sequence with the regular heartbeat communications between the panel and the lock (the default heartbeat interval is 10
minutes). The Wake on Radio interval is 10 seconds.
Enabling this feature allows the reader and lock to respond more quickly (within ten seconds rather than within ten minutes) to
manual actions. Typically the command from the iSTAR panel to the device will be for a lock or unlock.
Save and Click to save your configuration changes and close the iSTAR PIM-485 Board editor.
Close
If you select the AD300 series lock in the PIM Type Drop-down list on the General tab, the Input tab is removed because
the AD300 series does not have a Tamper Input.
Field/Button Description
Create Input Click to create the Tamper Input. When you click Create Input, the Configured column check box is selected, and you can click
in the Edit column to open the iSTAR Input editor (see iSTAR Input Editor on Page 240.
Delete Input When you click Delete Input, the check box in the Configured column is cleared for the Tamper Input, and the Tamper Input is
immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the Input Editor to configure the Tamper Input. See iSTAR Input Editor on Page 240.
Configured Click in this column to create the Tamper Input (make it available to be edited) .
column
Name column Displays the name for this Input. The name is system-generated and is read-only.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to select
Column an Input Template. If the Configured column displays , this field cannot be edited.
Save and Click to save your configuration changes and close the iSTAR PIM-485 Board editor.
Close
Field/Button Description
Create All Click to create all 16 readers. When you click Create All Readers the Configured column check boxes are selected, and you
Readers can click in the Edit column to open the iSTAR PIM-485 Board Editor to configure a Reader. See iSTAR PIM-485 Reader
Editor on Page 512.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all 16 Readers, and all 16
Readers Readers are immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR PIM-485 reader Editor to configure a Reader. See iSTAR PIM-485 Reader
Editor on Page 512.
Name column Displays the name for this Reader. The name is system-generated, and the field is read-only.
Save and Click to save your configuration changes and close the iSTAR PIM-485 Board editor.
Close
The iSTAR Input editor (see Figure 75 on Page 241) has the following tabs:
■ iSTAR Input General Tab on Page 244
Identifies the Controller and Board this Input is configured on, the type of the Input (such as Door Switch), and the
object the Input is assigned to, such as a Door.
■ iSTAR Input Intrusion Zone Tab on Page 245
This tab appears only if you have included this iSTAR Controller in an Intrusion Zone and added this Input as a
Controlled Input.
■ iSTAR Input Triggers Tab on Page 246
This tab lets you define Triggers that can activate C•CURE 9000 Events and activate outputs.
See Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
■ Groups Tab for Hardware Devices on Page 36
If you have created a Group containing iSTAR Inputs and added this Input to it, the iSTAR Input editor also displays a
Group tab.
This tab lists the Input groups to which this Input belongs. for information on using the Group tab for your iSTAR Input.
■ iSTAR Input Status Tab on Page 246
This tab displays several read-only fields that report the Active, Armed, Hardware, and Supervision status of the Input.
■ iSTAR Input State Images Tab on Page 246
This tab shows the images that are displayed in the Monitoring Station to represent this input. You can change the
image used for any of the Input states.
3. Click the Edit button for the Input you want to edit.
• To edit a Main Board or General Purpose Input from the Inputs tab, click in the Edit column for the Input you
want to edit.
• To edit I/8 Inputs from the COM1/COM2/COM3 tab, click in the Edit column for the Input Board containing the
Input you want to Edit. The iSTAR Input Board Editor opens. Click in the Edit column for the Input you want to
edit.
The iSTAR Input Editor opens (see iSTAR Input Editor on Page 240).
3. Click on the Input board that contains the Input you wish to edit.
6. Click the Input State Images tab to view the state images for this Input. If you wish to customize the state images for
this Input, follow the steps in State Images Tab for iSTAR Devices on Page 281.
7. When you have finished configuring this Input in the Input Editor, click Save and Close to save the settings you have
configured.
Field/Button Description
Name Displays the name for this Input. The name is system-generated by default, but you can edit this name by clicking in this
field.
Description Enter a textual comment about the Input, such as its location or purpose. This text is for information only.
Maintenance Mode Click to put the iSTAR Input into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Partition This read-only field identifies the Partition in which this Input resides.
Identification
Controller This read-only field identifies the iSTAR Controller to which this Input is attached.
Board This read-only field identifies the iSTAR Controller board to which this Input is attached.
Type Reflects whether the Input has been assigned to a Door or other object. These include:
• General
• Door Switch
• Request to Exit
• Elevator
Assigned to Displays the Elevator or Door object name with which this Input is configured.
Connection Identifies the Input number on the hardware board to which this Input is connected.
Field/Button Description
Options
Debounce Threshold In this field, enter the time that an input must be in a particular state before it is reported as a state change. It is used to
(1/10 sec) filter out spurious changes. The units range from 0 – 60 seconds, the default is 0.
NOTE: For Proprietary Burglar Alarm applications, the Debounce Threshold field must be programmed for a
maximum of 90 seconds.
Supervised This field indicates that the inputs on the board are Supervised. This is a read-only field.
NOTE: For Proprietary Burglar Alarm applications, the Supervised check box must be selected.
Send state changes to To have a notification of changes in state of the Input sent to the guard station, select the Send state changes to the
monitoring station monitoring station check box.
NOTE: For Proprietary Burglar Alarm applications, the Send state changes to the monitoring station option must
be selected.
Send state change to To have a notification of changes in state of the Input sent to the journal, select the Send state changes to journal
journal check box. This option will be selected by default.
Reverse sense When this option is selected, the interpretation of the board’s Supervised Resistors is reversed.
Activate on Supervision When this option is selected, the Input will be activated on a Supervision error.
Error
Default State
Armed When this option is selected, the Input is armed by default. This is useful if you are not providing arming via an event.
An Input assigned as an iSTAR Intrusion Zone Controlled or Protected Input displays read-only assignment information on
the Intrusion Zone tab of the Input Editor. This tab only displays when the Input is assigned to a zone. At the same time,
the value in the Type field on the Input General tab changes from ‘General’ to ‘Intrusion Zone’.
The iSTAR Input Intrusion Zone tab displays read-only fields that give Intrusion Zone assignment information for this Input.
Field/Button Description
Display Name Displays the name you entered for this Input on the iSTAR Intrusion Zones Editor Inputs tab in the Controlled Inputs table.
NOTE: This is the unique LCD display name for this Input that is used whenever the Intrusion Zone needs to display this door as
an ‘offnormal’ point on the Reader LCD.
The Dynamic View for iSTAR Inputs also allows you to add a column that identifies the Intrusion Zone to
NOTE which the Inputs belong.
For iSTAR Main Board and Special Purpose Inputs such as Tamper, Power Failure, and Battery Low, you can only create
Triggers for the Active Status property.
Table 76: iSTAR Input Trigger Properties
Property Description
Active Status Values that you can use for Triggers are “Active” and “Inactive”.
Armed Status Values that you can use for Triggers are “Armed” and “No Error”.
Supervision Error Status Values that you can use for Triggers are “Error” and “No Error”.
See Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
Field/Button Description
Hardware Status Displays the Hardware Status value for the Input. Possible values are Secure, Active, Open Loop, Shorted Loop, Fault, or
Ground.
Supervision Displays the Supervision Status value for the Input. Possible values are:
Status • Unknown - the host has not received the input status reported from the panel yet.
• Uninitialized - the panel reports no error on the input.
• Error - the input is in error state, and the detail can be seen in the Hardware Status field.
See State Images Tab for iSTAR Devices on Page 281 for information on using the State Images tab for an iSTAR Input.
Icon Description
Unknown
Active
Armed Enabled
Disarmed Enabled
Supervision Error
Disabled
Update Disabled
The iSTAR Output editor (see on Page 248) has the following tabs:
■ iSTAR Output General tab
Identifies the Controller and Board this Output is configured on, the type of the Output (such as Alternate Shunt Relay),
and the object the Input is assigned to, such as a Door. See iSTAR Output General Tab on Page 252.
■ iSTAR Output Groups tab
If you have created a Group containing iSTAR Outputs and added this Output to it, the iSTAR Output editor also
displays a Group tab.
This tab lists the Output groups to which this Output belongs. See Groups Tab for Hardware Devices on Page 36 for
information on using the Group tab for the iSTAR Output.
■ iSTAR Output Status tab
This tab displays several read-only fields that report the Active, Armed, Hardware, and Supervision status of the
Output. See iSTAR Output Status Tab on Page 253.
■ iSTAR Output State Images tab
See iSTAR Output State Images Tab on Page 253.
Figure 77: iSTAR Output Editor
To Access the iSTAR Output Editor (iSTAR Classic/Pro ACM Board Outputs Tab)
1. From the iSTAR Controller Editor, click on the Boards tab.
2. Click in the Configured column of the ACMs table to create an ACM Board.
3. Click in the Edit column for the ACM Board that contains the Input you want to Edit. The ACM Board Editor
opens.
4. Click the Outputs tab on the ACM Board Editor.
5. Click in the Configured column to create an Output.
6. In the Outputs table on this tab, click in the Edit column for the Output you want to Edit.
The iSTAR Output Editor opens (see iSTAR Output Editor on Page 248).
To Access the iSTAR Output Editor (iSTAR Classic/Pro ACM Board ACM Ext Tab)
1. From the iSTAR Controller Editor, click on the Boards tab.
2. Click in the Configured column of the ACMs table to create an ACM Board.
3. Click in the Edit column for the ACM Board that contains the Input you want to Edit. The ACM Board Editor
opens.
4. Click the ACM Ext tab on the ACM Board Editor.
5. Click in the Configured column of the Output Boards table to create an Output Board.
6. In the Output Boards table on this tab, click in the Edit column for the Output Board you want to Edit.
The iSTAR Output Board Editor opens (see iSTAR Output Board Editor on Page 220).
7. Click in the Configured column of the Outputs table to create an Output .
8. In the Output Boards table on this tab, click in the Edit column for the Output Board you want to Edit.
The iSTAR Output Editor opens (see Figure 77 on Page 248).
3. Click on the Output board that contains the Input you wish to edit.
Field/Button Description
Identification
Name Displays the name for this Output. The name is system-generated by default, but you can edit this name by clicking in click in
this field.
Description Enter a textual comment about the Output, such as its location or purpose. This text is for information only.
Maintenance Click to place the iSTAR Output into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Partition This read-only field identifies the Partition in which this Output resides.
Output Identification
Controller This read-only field identifies the iSTAR Controller to which this Output is attached.
Board This read-only field identifies the iSTAR Controller board to which this Output is attached.
Type Reflects whether the Output has been assigned to a Door or other object. These include:
• General
• Door Lock
• Shunt Expiration Relay
• Alternate Shunt Relay
• Elevator Button
NOTE: The Elevator output assignment has not been evaluated by UL.
Assigned to Displays the Elevator or Door object name with which this Output is configured.
Connection Identifies the Input number on the hardware board to which this Output is connected.
Options
Pulse Duration This is a momentary activation which is entered in second intervals with a default of 0 seconds.
(1/10 sec)
Field/Button Description
Normally This field is used to specify whether the Output is wired such that current is normally on or not. The default setting (not
energized selected) signifies that the Output is wired so that the current is normally off and when the Output is in an On state, the circuit
is energized.
Send state To have a notification of changes in state of the Output sent to the Monitoring station, select the Send state changes to the
changes to monitoring station check box.
monitoring station NOTE: For Proprietary Burglar Alarm applications, the Send state changes to the monitoring station option must be
selected.
This selection is unavailable for an iSTAR Door Output. State changes for a Door Output are not sent to the Monitoring
Station.
Send state To have a notification of changes in state of the Output sent to the journal, select Send state changes to journal. This
changes to journal option is selected by default.
This selection is unavailable for an iSTAR Door Output. State changes for a Door Output are not sent to the journal.
Field/Button Description
Active Status Displays the status of the Output - either Active or Inactive.
See State Images Tab for iSTAR Devices on Page 281 for information on using the State Images tab for an iSTAR Output.
Unknown Inactive
Active Disabled
Flashing
The iSTAR Reader editor (see Figure 79 on Page 256) has the following tabs:
■ iSTAR Reader General tab
Lists the Reader name, connections, and card formats for a reader connected to an iSTAR. See iSTAR Reader
General Tab on Page 498.
■ iSTAR Reader I/O tab
This tab lets you configure the available Inputs and Outputs for the Reader. See iSTAR Reader I/O Tab on Page 500.
■ iSTAR Reader Keypad tab
This tab lets you configure the settings and options for the Reader Keypad. See iSTAR Reader Keypad Tab on Page
501.
■ iSTAR Reader Triggers tab
See Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
■ iSTAR Reader Groups tab
If you have created a Group containing iSTAR readers and added this Reader to the Group, the iSTAR Reader editor
displays a Group tab.
This tab lists the Reader groups to which this Reader belongs. See Groups Tab for Hardware Devices on Page 36 for
information on using the Group tab for the iSTAR Reader.
■ iSTAR Reader Options tab
Use this tab to enable two factor authentication on the reader and to configure LED Control and Beep on Card Read for
Wiegand Readers. See iSTAR Reader Options Tab on Page 505.
■ iSTAR Reader Status tab
This tab displays several read-only fields that report the Communications, PIN Required, and Keypad Command
Allow Status of the Reader. See iSTAR Reader Status Tab on Page 504.
■ iSTAR Reader After-Hours tab
This tab enables the After-Hours Readers Group feature. See After-Hours on Page 506 for further information and
procedures to configure this feature.
Use this tab to select the Innometriks reader high assurance settings. See High Assurance Tab on Page 509
■ Touchscreen tab
Use this tab to set the TST-100 Touchscreen Terminal Reader's Automatic Dim brightness and time. This tab also
displays the card types supported and allows you to reporder the card type priority. See iSTAR Reader Touchscreen
Tab on Page 508.
■ iSTAR Reader State Images tab
This tab displays the default images used to depict this reader in the Monitoring Station. You can use this tab to
customize these state images. See iSTAR Reader State Images Tab on Page 510.
You can add or remove Card Formats from multiple Readers on the iSTAR Reader Dynamic View. See Add or Remove
Reader Card Formats on Page 33 for more information.
In each case, you must select the Configure column to configure the reader, then click to open the iSTAR Reader
editor.
Field/Button Description
Identification
Name Displays the name for this Reader. The name is system-generated by default, but you can edit
this name by clicking in click in this field.
Description Enter a textual comment about the Reader, such as its location or purpose. This text is for
information only.
Field/Button Description
Maintenance Mode Click to put the iSTAR Reader into Maintenance Mode. See Chapter 3: Maintenance Mode for
more information.
Partition This read-only field identifies the Partition in which this reader resides.
Controller This read-only field identifies the iSTAR Controller to which this reader is attached.
Board This read-only field identifies the iSTAR Controller board to which this reader is attached.
Assigned to Displays the Elevator or Door object name with which this reader is configured.
Connection Identifies the Reader number on the hardware board to which this reader is connected.
Card Format
If the card format you desire is not in the Name Selection dialog box list, click in the Select
Type field to select a card format.
Remove
Click the row selector to select one or more Card Format rows (hold down SHIFT or Ctrl to
select multiple rows), then click Remove to delete the row(s) for this field.
Name Displays the Name of each Card Format you have chosen for this Reader.
Description Displays the Description for the Card Format. This field is read-only.
Clearance Filter
Default Clearance Select a Clearance Filter Level for the reader from the drop-down list. The available Clearance
Filter Level Filter Levels are numbered 1 through 6. Personnel assigned with lower Clearance Filter Levels,
in the Personnel than the reader configuration are denied access.
• Level 6 is the highest level.
• Level 1 is the lowest level and the default setting.
Field/Button Description
Beep on Key Press Select this check box for the TS-100 Touchscreen Terminal reader to beep when pressing a key.
Beep on Card Read Select this check box for the TS-100 Touchscreen Terminal reader to beep on a card read.
Date Format Select the date format and/or the time format to use.
Time Format
Definitions for the Inputs on the iSTAR Aperio Reader I/O Tab are described in iSTAR Aperio Reader I/O Tab on Page 518.
The fields on this tab vary depending upon the type of Reader you are configuring. For example, a Direct Connect Wiegand
Reader displays only the Communications Fail Input on the I/O tab.
Table 83: iSTAR Reader I/O Tab Definitions
Field/Button Description
Inputs
Create All Inputs Click to create all eight Inputs. The check boxes in the Configured column are set to .
Delete All Inputs Click to delete all eight Inputs. The check boxes in the Configured column are set to .
Edit Click in this column to open the iSTAR Input Editor to edit this Input.
Connection This read-only field identifies the position of each Input on the I/O tab.
Name Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to
select an Input Template. If the Configured column displays , this field cannot be edited.
Supervised 1 Represents Supervised Input #1 on iSTAR Readers. Not available on direct connect Wiegand Readers.
Field/Button Description
Supervised 2 Represents Supervised Input #2 on iSTAR Readers. Not available on direct connect Wiegand Readers.
Tamper Represents the Tamper Input on iSTAR Readers. Not available on direct connect Wiegand Readers.
Outputs
Create All Click to create all Outputs. The check boxes in the Configured column are set to .
Outputs
Delete All Click to delete all Outputs. The check boxes in the Configured column are set to .
Outputs
2 Represents Output #2 on iSTAR Readers. Not available on direct connect Wiegand Readers.
Field/Button Description
PIN is not If selected, only a card swipe is required for successful access to the door connected to this reader.
required
PIN only If selected, this reader can be used for PIN-Only access.
NOTE: PIN only cannot be used as a Query filter value for the PIN Required Status field.
Card and PIN If selected, this reader requires both a card swipe and a PIN entry at the keypad for access.
required
Schedule If Card and PIN Required is selected, you can select a Schedule object to determine when Card and PIN Required is
enforced. When the Schedule is active, both Card and PIN are required for access. When the Schedule is inactive, only a card
swipe is required.
Allow PIN If Card and PIN Required is selected, Personnel records configured with PIN Exempt (ADA) are exempt from having to
Exempt (ADA) enter a PIN for access.
Field/Button Description
Allow card If you have selected PIN is not required or Card and PIN required, you can enable Allow card numbers to be entered
numbers to be from the keypad by selecting the check box. If you chose PIN Only, this option is unavailable because the Keypad must be
entered from used to enter a PIN.
keypad
Use PIN+1 as If you have selected PIN is not required or Card and PIN required, you can enable Use PIN+1 as duress code by
duress code selecting the check box. If you chose PIN Only, this option is unavailable.
Keypad Indicates whether or not Keypad Commands can be entered on this Reader’s Keypad and when. Select one of the following
Commands options from the drop-down list. The default is Not Allowed.
Allowed • Not Allowed – Keypad Commands cannot be used at the Reader
• Always Allowed – Keypad Commands can always be used at the Reader
• Allowed during specified schedule – Keypad Commands can be used at the Reader during the period specified in the
following field. When you select this option, the Schedule for Keypad Commands field becomes available.
Scramble TST-100 Touchscreen Terminal Reader using the Smart Protocol only.
Keypad If the reader is using the Smart protocol on the reader, you must select this check box to enable Scramble Keypad on the reader.
When the PIN is being entered, the LED displays a randomly allocated set of numbers from 0 to 9. The position of the numbers
changes every time the keypad is activated.
NOTE: This field is not visible if the reader is using the RM Protocol. To enable Scramble Keypad on a reader using the RM
protocol, place the TST-100 Touchscreen Terminal Reader S2-5 switch to the ON position.
Schedule for Select a Schedule from the list to specify when Keypad Commands can be used at this Reader. When the Schedule is active,
Keypad Keypad Commands can be used. When the Schedule is inactive, Keypad Commands cannot be used.
Commands
See Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
For iSTAR Readers you can create Triggers for the properties shown in Table 85 on Page 262.
Table 85: iSTAR Reader Trigger Properties
Property Description
PIN Required Status Possible values are Not Required or Card and PIN Required, based on the setting for PIN Requirements on the
Keypad tab.
Tamper Status Boolean value; True if the Tamper input has been activated, or False if the Tamper Input has not been activated.
Field/Button Description
Communications Communications displays the value Normal if the Controller can communicate with the Reader or Comm Fail if the
Controller cannot communicate with the Reader.
PIN Required PIN Required displays the value True if PIN Required has been selected on the Keypad tab or False otherwise.
Tamper Displays the status of the Tamper Input. Not available on Direct Connect Wiegand readers.
Keypad Command This field displays status of the Keypad Commands Allowed setting from the Reader Editor Keypad tab:
Allow Status • Not Allowed
• Allowed
• Allowed during specified schedule.
Field/Button Description
Communications Communications displays the value Normal if the Controller can communicate with the Reader or Comm Fail if the
Controller cannot communicate with the Reader.
PIN Required PIN Required displays the value True if PIN Required has been selected on the Keypad tab or False otherwise.
Tamper True if a Tamper status is detected for the PIM Reader, or False if no Tamper condition is detected.
Keypad Command This field displays status of the Keypad Commands Allowed setting from the Reader Editor Keypad tab:
Allow Status • Not Allowed
• Allowed
• Allowed during specified schedule.
Field/Button Description
[PIM1-pro 1] - PIM True if a Tamper status is detected for the PIM-485 board to which this reader is attached, or False if no Tamper condition
Tamper is detected.
Motor Stall True if a Motor Stall condition (a problem with the latching mechanism of the door strike) is detected, or False if no Motor
Stall condition is detected.
Available only for PIM-485 WA Series Locks, not for other AD Locks.
Low Battery True if a Low Battery condition is detected for the PIM Reader, or False if no Low Battery condition is detected. Available
only for PIM-485 connected Readers.
Manual Lock True if the Manual Lock Overrride has been activated (unlocked by a physical key), or False if the Manual Lock Override
Override has not been activated. Available only for PIM-485 connected Readers.
Push Button True if the Push Button on the lock panel (inside the room) has been pressed, or False if the Push Button has not been
pressed. Available only for PIM-485 connected Readers.
Field/Button Description
Communications Communications displays the value Normal if the Controller can communicate with the Reader or Comm Fail if the Controller
cannot communicate with the Reader.
Tamper True if a Tamper status is detected for the Reader, or False if no Tamper condition is detected.
Low Battery True if a Low Battery condition is detected for the Reader, or False if no Low Battery condition is detected.
Field/Button Description
Dual Authentication
OSDP Options
Installation Mode Enabled When enabled, allows C•CURE 9000 to communicate securely with a new reader that does not have encryption
keys. The OSDP Secure Channel Enabled check box must be also selected.
• If OSDP Secure Channel Enabled is On (selected) and Installation Mode Enabled is Off (deselected)
and a new reader is presented, it will not communicate with C•CURE 9000.
• If OSDP Secure Channel Enabled is Off (deselected), then communication is always available and the
installation mode is disabled.
• If Installation Mode Enabled is On (selected), then the keys will be exchanged and communication will
begin.
Default: Enabled.
Software House recommends that you disable (clear) this feature for maximum security.
OSDP Secure Channel When enabled, the 485 communication port is encrypted using keys exchanged between the panel and the
Enabled readers. See Installation Mode Enabled.
IMPORTANT:
Enabling or disabling the OSDP Secure Channel requires the reader to be restarted for the changes take
effect. This can be accomplished by power cycling the reader, resetting the ACM, or by resetting the
controller.
Default: Enabled
Beep on Key Press Select this check box for the TS-100 Touchscreen Terminal reader to beep when pressing a key.
Beep on Card Read Select this check box for the TS-100 Touchscreen Terminal reader to beep on a card read.
Date Format Select the date format and/or the time format to use.
Time Format
After-Hours
When configured, the After-Hours Reader feature defines a schedule, an enabling reader, and an iSTAR reader group.
Cardholders with clearance gain access by an enabling door to normally restricted, secure spaces after business hours.
Within this schedule, readers configured as members of an After-Hours Reader Group will reject access to all
cardholders that have not first presented their card to the enabling reader for that particular reader group, even when those
cardholders have valid clearance to member readers. Once a card has been presented and accepted at the enabling
reader, it will then have access to any members of the associated After-Hours group to which it has a valid clearance for
the remainder of the schedule.
The After-Hours feature supersedes clearance restrictions only relative to admission during the schedule. Outside of the
defined schedule, cardholders will have the normally expected access to readers within the After-Hours Reader Group.
Refer to After-Hours Readers Under Offline State Conditions on Page 267 for information regarding After-Hours enabled
readers during offline conditions.
The After-Hours restriction can be overridden for certain cardholders by using the AntiPassback Exempt Flag to indicate
After-Hours Exemption. The AntiPassback Exempt Flag is on the General tab of the Personnel record. Use of the
AntiPassback Exempt Flag to override After-Hours is set in System Variables. Refer to Setting the AntiPassback
Exempt Flag on Page 267 for instructions on setting the AntiPassback Exempt Flag.
For proper functionality, when configuring an After-Hours Reader feature, the After-Hours Reader Group, the enabling reader, and
NOTE the schedule that is assigned to these units must all be configured in the same time zone.
If required, follow the instructions for creating and configuring an After-Hours Schedule as explained in the C•CURE 9000 Software
NOTE Configuration Guide.
Once communication with the host is restored, the panel controlling the enabling reader resumes normal operation.
High assurance is supported on the iSTAR Ultra, Ultra SE (Ultra Mode), and Ultra LT controllers.
CAK, PIN, and Biometrics are single factor authentications when used alone. Any two together are a double factor
authentication, and all three together are a triple factor authentication.
See Innometriks High Assurance Reader Configuration on Page 480 for configuration information.
Field/Button Description
Support High Assurance Reader When selected (enabled), the High Assurance Operation Modes become available for selection.
Default: Disabled (clear)
PAK Physical Access Control System (PAK). Card plus PIN authentication.
NOTE: If you select PAK, Card PIN is automatically selected.
See State Images Tab for iSTAR Devices on Page 281 for information on using the State Images tab for an iSTAR
Reader.
See Table 90 on Page 268 for default State Images for an iSTAR RM reader
See Table 91 on Page 269 for default State Images for an iSTAR PIM-485 reader (Schlage wireless lock and reader).
Unknown Tampered
Comm Fail Motor Stall (Schlage Wireless Only) Manual Lock Override (Schlage Wireless
Only)
Normal
The iSTAR PIM-485 Reader editor dialog box has the following tabs.
■ iSTAR Reader General tab
Lists the Reader name, connections, and card formats for a reader connected to an iSTAR Classic/Pro, or iSTAR eX.
See iSTAR Reader General Tab on Page 498.
■ iSTAR PIM-485 Reader I/O tab
This tab lets you configure the available Inputs and Outputs for the Reader. See the iSTAR PIM-485 Reader I/O Tab
on Page 513.
■ iSTAR Reader Keypad tab
This tab lets you configure the settings and options for the Reader Keypad on iSTAR Schlage Readers. See iSTAR
Reader Keypad Tab on Page 501.
Only Schlage Keypad Mode 1 keypad output format (4 data bits per key with no parity) is supported. The mode is
configured on the Schlage device.
■ iSTAR Reader Triggers tab
See the Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
You can define triggers for the following Properties of the iSTAR PIM-485 Reader:
Property Value
You can add or remove Card Formats from multiple Readers via an iSTAR PIM-485 Reader Dynamic View. See Add or
Remove Reader Card Formats on Page 33 for more information.
You can configure these inputs and outputs by clicking on in the Edit column. You can then create triggers that can
activate Events based on state changes.
Example:
You can create a trigger to activate an Event if the Low Battery Input status changes to Active (indicating that the
reader battery charge is low). See Triggers Tab for iSTAR Devices on Page 278.
Definitions for the fields and buttons on the Reader I/O tab are described in Table 93 on Page 272.
Field/Button Description
Inputs
Create All Inputs Click to create all eight Inputs. The check boxes in the Configured column are set to .
Delete All Inputs Click to delete all eight Inputs. The check boxes in the Configured column are set to .
Edit Click in this column to open the iSTAR Input editor to edit the Input.
Connection This read-only field identifies the position of each Input on the I/O tab.
Name Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to
select an Input Template. If the Configured column displays , this field cannot be edited.
Wireless DSM Represents the Wireless Door Switch Monitor (DSM) for the door.
Wireless REX Represents the Wireless Request To Exit (REX) for the door.
Wireless Reader Represents the Communications Failure Input on the Wireless Reader.
Communications
Fail
Motor Stall Represents the Motor Stall Input on the Wireless Reader.
Low Battery Represents the Low Battery Input on the Wireless Reader.
Manual Lock When this input is active, it indicates that the lock has been unlocked by a physical key.
Override The Manual Lock Override status is available on the Status tab for this reader. This property is available for use in triggers.
Push Button When this input is active, it indicates that the push button on the lock panel (inside the room) has been pushed.
The Push Button Input status is available on the Status tab for this reader. This property is available for use in triggers.
Outputs
Create All Outputs Click to create all Outputs. The check boxes in the Configured column are set to .
Delete All Outputs Click to delete all Outputs. The check boxes in the Configured column are set to .
Door Latch Relay Represents the Door Latch Relay Output that is used to unlock the door.
Edit Click in this column to open the iSTAR Output editor to edit the Output.
Field/Button Description
Connection This read-only field identifies the position of the Output on the I/O tab.
Name Displays the system-generated name for this Output. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Output. If the Output is not yet configured, you can click in this column, then
click to select an Output Template. If the Configured column displays , this field cannot be edited.
When you add an iSTAR Aperio Reader, Enable it in the Aperio Reader editor, and Save and Close the editor, a Door
object for that reader is added to the parent Ultra controller in the iSTAR Aperio Doors folder in the Hardware tree.
If you delete an iSTAR Aperio Reader, the iSTAR Aperio Door associated with the reader is also deleted.
If you display a list of iSTAR Doors, the new Aperio Door appears on the list. See iSTAR Aperio Door Editor on Page 420
for more information on Aperio Doors.
The iSTAR Aperio Reader editor dialog box has the following tabs.
■ iSTAR Reader General tab
Lists the Ultra controller name, Hub board, Assigned to Door, Reader number, Device ID, and Reader type. See
iSTAR Reader General Tab on Page 498.
■ iSTAR Aperio Reader I/O tab
This tab lets you configure the available Inputs and Outputs for the Reader. See the iSTAR Aperio Reader I/O Tab on
Page 518.
■ iSTAR Reader Keypad tab
This tab lets you configure the settings and options for the Reader Keypad on iSTAR Aperio Readers. See
iSTAR Aperio Reader Keypad Tab on Page 277.
■ iSTAR Reader Triggers tab
See the Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR Ultra device.
You can define triggers for the following Properties of the iSTAR Aperio Reader:
Property Value
You can add or remove Card Formats from multiple Readers via an iSTAR Aperio Reader Dynamic View. See Add or
Remove Reader Card Formats on Page 33 for more information.
The number of inputs available on this tab varies, depending upon the reader model configured on the General tab in the
Reader Type field.
When an Aperio reader input is changed from active to inactive while the iSTAR Controller is offline, the
NOTE controller continues to report the input as active when the controller comes back online.
Workaround: Activate and then deactivate the input to synchronize the input with the controller.
You can configure these inputs by clicking on in the Edit column. You can then create triggers that can activate
Events based on state changes.
Example:
You can create a trigger to activate an Event if the Lock Low Battery Input status changes to Active (indicating that
the reader battery charge is low). See Triggers Tab for iSTAR Devices on Page 278.
Definitions for the fields and buttons on the Reader I/O tab are described in Table 94 on Page 276.
Definitions for the input types are described in Table 95 on Page 277.
Table 94: iSTAR Reader I/O Tab Definitions
Field/Button Description
Create All Click to create all Inputs. The check boxes in the Configured column are set to .
Inputs
Delete All Click to delete all Inputs. The check boxes in the Configured column are set to .
Inputs
Edit Click in this column to open the iSTAR Input editor to edit the Input.
Connection This read-only field indicates the three standard inputs (Comm Fail, Low Battery, and Lock State Jammed.
Name Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to select
an Input Template. If the Configured column displays , this field cannot be edited.
Field/Button Description
Lock Reader Tamper Represents the state of the Tamper input on the lock.
Handle State / Request to Exit Represents the state of the Request to Exit input associated with the door handle.
Key Cylinder Override Represents the state of the Key Cylinder Override.
Door Position State Represents state of the Door Switch Monitor for the door associated with this reader.
Lock Communications Fail Represents the Lock Communications Failure Input on the Aperio Reader.
Lock State Jammed Represents the Lock State Jammed Input on the Aperio Reader.
Lock Low Battery Represents the Lock Low Battery Input on the Aperio Reader.
Field/Button Description
PIN is not required If selected, only a card swipe is required for successful access to the door connected to this reader.
PIN only If selected, this reader can be used for PIN-Only access.
NOTE: PIN only cannot be used as a Query filter value for the PIN Required Status field.
Card and PIN If selected, this reader requires both a card swipe and a PIN entry at the keypad for access.
required
Schedule If Card and PIN Required is selected, you can select a Schedule object to determine when Card and PIN Required is
enforced. When the Schedule is active, both Card and PIN are required for access. When the Schedule is inactive, only a
card swipe is required.
Allow card If you have selected PIN is not required or Card and PIN required, you can enable Allow card numbers to be
numbers to be entered from the keypad by selecting the check box. If you chose PIN Only, this option is unavailable (because the
entered from Keypad must be used to enter a PIN).
keypad
Use PIN+1 as If you have selected PIN is not required or Card and PIN required, you can enable Use PIN+1 as duress code by
duress code selecting the check box. If you chose PIN Only, this option is unavailable.
Example:
To provide an audible and visible alarm for a power failure condition, you can create two triggers for the AC Power Fail
Input on an iSTAR controller that are activated when the Input's status changes:
Activate Output that energizes an audible sounder.
Activate Output that energizes an LED alarm light installed near an arming/disarming keypad reader.
Active Status Active Activate Event iSTAR Input Event Always Time Zone of the iSTAR
controller
You cannot assign a Schedule to an iSTAR Controller trigger. Effectively, iSTAR Controller triggers use an
NOTE Always Schedule.
From the Triggers tab of an iSTAR device (such as a Controller, Input, or Reader), you can perform the following tasks.
■ Defining a Trigger for an iSTAR Device on Page 278.
■ Removing a Trigger on Page 279.
iSTAR Triggers Tab Definitions on Page 280 provides definitions for the fields and buttons on an iSTAR Device Triggers
tab.
Example:
When an iSTAR Tamper Input changes from the Inactive (normal) to Active (abnormal) state, you wish to activate an
Event and activate an audible alarm (an iSTAR Output).
Example:
If you have iSTAR controllers that are in different Time Zones than your C•CURE 9000 server, you may want to have
some Triggers activate according to the iSTAR controller's Time Zone, while other Triggers are activated according to
the server Time Zone.
When you specify the Time Zone for a Trigger definition to be the same as the iSTAR controller Time Zone, the
Schedule activation times for the Trigger occur according to the iSTAR controller Time Zone.
If you have an iSTAR controller in the Pacific Time Zone (GMT - 08:00) and a server in the Eastern Time Zone (GMT -
05:00), a Schedule that is active from Midnight to 6:00 AM is activated from Midnight to 6:00 AM in Pacific Time (GMT
- 08:00) rather than Eastern time (three hours later).
Removing a Trigger
If you no longer need a Trigger defined for a Device, you can remove the Trigger.
To Remove a Trigger
1. Click the Triggers tab for your device.
Field/Button Description
Remove
Click the Row Selector , then click Remove in the Triggers tab to delete a trigger.
Property Click within the Property column, and then click . The Property browser opens presenting properties available for the
Comm Port. Click a Property to select it and add it to the column.
Value Click within the Value column to display a drop-down list of Values associated with the Property that you have selected. Click a
Value that you want to include as a parameter for the trigger to add it to the column.
Action Click within the Action column to display a drop-down list of valid actions. Click an Action that you want to include as a
parameter for the trigger to add it to the column.
As you select an Action, a corresponding entry field, or group of entry fields, appear at the bottom of the dialog box.
Click to select entries for these fields.
Time Zone Click within the Time Zone column to select a Time Zone for Schedule activation.
Click to select a Time Zone that you want to associate with the trigger Schedule. Typically you can chose either the
C•CURE 9000 server (host) Time Zone or the Time Zone of the iSTAR controller.
If you specify a Time Zone, the Schedule start and end times are calculated using that Time Zone.
Example:
A Schedule that becomes active at 3:00 AM would become active at 3:00 AM in the Pacific Time Zone, if that Time Zone was
specified. Refer to the C•CURE 9000 Software Configuration Guide for more information on Time Zones and Events.
From the State Images tab of an iSTAR device (such as a Controller, Input, Output, or Reader), you can perform the
following tasks.
■ Customizing State Images for an iSTAR Device on Page 281
■ Restore a Default State Image on Page 282
You can replace the default images with JPG formatted files of your choice, to uniquely identify your objects when
activities are displayed on the Monitoring Station Client.
iSTAR State Images Tabs Definitions on Page 281 provides definitions for the fields and buttons on an iSTAR Device
State Images tab.
Field/Button Description
State This column lists the states that are defined for this iSTAR device. These are the states that are reported on the Monitoring
Station to reflect the status of this iSTAR device.
Image This column shows the images that are assigned to each of the iSTAR device states. There are images assigned by default to
every iSTAR device you create. For any individual iSTAR device, you can use the State Images tab to substitute a
different.JPG/JPEG image for the default image. See Customizing State Images for an iSTAR Device on Page 281 for
instructions.
Save and After you have made changes to any settings for the iSTAR device, click Save and Close to save those changes and Close the
Close editor for the device.
The iSTAR Ultra SE configuration data (doors, personnel, etc.) is held in volatile RAM during normal operation (IP settings
are stored in the controller’s onboard flash memory). This data is backed up to non-volatile SD Card memory on a periodic
basis during normal operation. Data is automatically backed up after a fast download to the panel, and, upon a soft reset on
the GCM board.
The non-rechargeable lithium coin cell battery maintains the controller’s clock only during a power outage
NOTE for up to 30 days.
To ensure that the database backup is always current, Software House recommends that you create an event to trigger a
database backup when the Low Battery or AC Fail input is activated on the GCM board. An event with the action
“Backup iSTAR Database” can trigger the event from the Low Battery or AC Fail input. If your power supply does not
support the Low Battery or AC fail, then you can trigger the database backup event using a schedule. For example, set a
schedule to run every Monday at 2AM.
When power is restored after an outage, the controller first attempts to connect to its host server. If successful, the host
will download the current time to the controller, and download the current database. However, if the host is not present,
then the controller will use its local backed-up time, and it will use the last saved database from the SD card.
When the host is offline, transaction buffers of card activity and other activity are automatically written to non-volatile
memory, and do not require database backup configuration.
In this chapter
IP-ACM Overview
The IP-ACM provides connection and management of readers. There are two types of IP-ACM boards:
■ IP-ACM v1 - contains one Ethernet port
■ IP-ACM v2 - contains two Ethernet ports
The IP-ACM, when configured in Offline mode (enabled), acts as its own entity if it becomes disconnected from the
iSTAR. Readers will remain active, with limitations. Offline access operation is buffered, and will be reported to the
iSTAR Controller when communication is restored (determined by available memory.) Refer to IP-ACM Offline Mode
Configuration Information on Page 288 for further details regarding the offline mode of the IP-ACM.
Limitations
■ C•CURE 9000 only supports four readers (any combination of RM, Wiegand, Smart and OSDP readers) or up to two
BLE readers connected to an IP-ACM.
■ The IP-ACM is supported on the iSTAR Ultra, the iSTAR Ultra SE in Ultra Mode, the iSTAR Ultra Video, and the
iSTAR Ultra LT.
■ Offline mode is not supported for two RM readers. Two reader configuration for a single door must be: one RM for entry
and one Wiegand for exit.
■ Offline mode is not supported for BLE or OSDP readers connected to the IP-ACM v1.
■ Offline mode is not supported for BLE, RM, Smart or OSDP readers connected to the IP-ACM v2.
3 Ensure that the iSTAR Controller (Ultra or Ultra SE in Ultra Mode) is configured in the C•CURE 9000. Creating an
iSTAR Controller on
Page 127
5 Configure a door with the readers connected to the IP-ACM. iSTAR Door Editor
on Page 397
Offline Mode is configured in the iSTAR Controller dialog box in the IP-ACMs tab.
Card + PIN access is not supported in Offline Mode. Card-only access is supported.
Stored Credentials
Predefined Credentials
Predefined credentials are downloaded from the iSTAR controller in the form of raw data (Static Card Data). When the IP-
ACM is offline, access is granted when the predefined credentials (from the Static Card Data stored on the IP-ACM) are
presented to the readers.
Example:
If you set the "Maximum Cards Per Person" value to 3, then only 1000 - 100 x 3 = 700 is allowed in the "Admit the
last admitted cards" field for configuration.
Door Configuration
■ In Offline Mode, all components of the door must come from the same IP-ACM board.
NOTE
In Offline Mode, the readers, inputs, and outputs must be configured on the IP-ACM as detailed below:
■ Wiegand:
• A reader configured on Wiegand Port 1 as the entry reader.
• A reader configured on Wiegand Port 2 as the exit reader.
■ RS-485 (used for OSDP readers):
• A reader configured on RS-485 Port 1 assigned to OSDP address 0 as the entry reader.
• A reader configured on RS-485 Port 2 assigned to OSDP address 0 as the exit reader.
■ An input configured on Input 1 as the DSM (Door State Monitor).
■ An input configured on Input 2 as the REX (Request to Exit).
■ An output configured on Output 1 as the Door lock.
■ Door configurations not complying with the above restrictions may result in unexpected operation
between online and offline modes.
■ If the readers, in the list above, inputs/outputs are configured for a different purpose in C•CURE, the
Offline Mode door controller will use them for the door control functions listed above, even if they are
not configured for the door in C•CURE.
The door operation parameters are fixed when the IP-ACM goes into offline mode and cannot be changed. The door
parameters revert to their configured settings when the IP-ACM goes back online.
If there is only one controller in the cluster, you can disable the cluster.
NOTE
d. Select the IP-ACM v1 board you want to convert to an IP-ACM v2 board and click Edit.
e. Under Upgrade Options, click Upgrade.
The Upgrade button is only enabled if the controller or the cluster is disabled.
NOTE
f. Enter the MAC address of the new board in the prompt and click OK.
A prompt appears to confirm that you want to perform the upgrade.
g. Click Yes to confirm the upgrade.
h. Click OK in the dialog box displaying the results of the conversion.
— If the conversion is successful, the iSTAR Controller dialog box automatically closes.
— If the conversion is not successful, the iSTAR Controller dialog box remains open.
i. If there are additional IP-ACM v2 boards you want to convert for this controller, and other controllers in the same
cluster, repeat steps b through step i.
3. Open the iSTAR Controller editor (for each controller disabled in the cluster), or the Cluster dialog box, and click
Enabled.
4. Repeat Step 1 through Step 3 on each IP-ACM v1 board you want to convert.
2. Click on the Configured check box in the Index row where you want to add, or edit, an IP-ACM.
3. Click in the Edit column of the Index row to open the iSTAR Ultra IP-ACM Editor on Page 297. The iSTAR Ultra
IP-ACM editor is used to configure the inputs, outputs, and readers (Wiegand, RM, BLE, OSDP, and Smart).
4. Configure the Offline Mode of All IP-ACM's configured on this controller.
See Table 101 on Page 295 for descriptions of the fields.
5. When the IP-ACMs configuration is complete, click in the Enabled check box, and click Save and Close.
Field/Button Description
IP-ACMs
Create All IP-ACMv1s Click to create the IP-ACMs. When you click Create All IP ACMv1s, or Create All IP ACMv2s, the
Create All IP-ACMv2s Configured column check boxes are selected,
Click in the Edit column to open the iSTAR Ultra IP ACM Editor to configure the IP ACM.
Delete All IP-ACMv1s When you click Delete All IP-ACMv1s,or Delete All IP-ACMv2s, the check boxes in the Configured
Delete All IP-ACMv2s column of the table are cleared for all IP-ACMs.
When the configuration is saved, a prompt appears to confirm deletion of each IP-ACM.
NOTE: The selections made in the Offline Mode of All IP-ACMs section will apply to all IP-ACMs (iP-ACMv1s and IP-ACMv2s) configured on the
controller.
In offline mode, the IP-ACM board will admit cards that are among the last xxx previous admitted cards in addition to a pre-defined personnel group.
- A total of 1000 credentials (not personnel) for both previous admitted credentials and credentials in the personnel group.
- Maximum 100 personnel in the personnel group.
- If you set the Personnel system variable "Maximum Cards Per Person", then that value must be taken into consideration.
Example: If you set the "Maximum Cards Per Person" value to 3, then only 1000 - 100 x 3 = 700 is allowed in the "Admit the last admitted
cards" field for configuration. This is true, even if the personnel count in the personnel group selected is less than 100.
Admit the last admitted cards Select a number from the menu that will apply to the previous cards that were admitted.
Default: 0
Value: 0 to 1000
Card Format used for Offline Mode Select a card format to be used for personnel when in offline mode. Only individual card formats are
selectable. The card format is used to determine the card data stream for each person in the personnel
group. All personnel will use the same card format. The first facility code and site code in the list will be used
if that format has multiple values.
Number of seconds before Offline The time in seconds that the IP ACM waits to enter offline mode after it loses communication with the GCM
Mode is enabled. board.
This setting will apply to all IP ACMs on this controller unless specified in the iSTAR Ultra IP ACM Editor
General tab.
Default: 10 seconds.
Range: 5 to 30 seconds.
Number of Days to Keep The number of days a credential is kept while in offline mode.
Credentials in Offline Mode A value of 0 indicates not to keep a credential when in offline mode.
Default: 30 days
Range: 0 to 9999 days
Field/Button Description
High Latency Threshold in The number of milliseconds that will cause a round-trip latency alarm. This value will apply to all IP-ACM's
milliseconds configured for this controller.
Default: 200 milliseconds (0.2 seconds)
Range: 100- 2000 milliseconds (0.1 to 2 seconds)
Field/Button Description
Maintenance Mode Click to put the IP-ACM into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Board Location
Offline Mode
Disable offline mode Click the check box to disable offline mode on this IP-ACM.
NOTE: This selection will override the Offline Mode of all IP-ACMs selections in the iSTAR Controller Editor IP-
ACMs tab for this IP-ACM.
See IP-ACM Offline Mode Configuration Information on Page 288.
If using online mode, all components of the door must come from the same IP-ACM board.
Switch Port (J5) Options Select the check box to enable the J5 Switch Port. Clear this check box to disable this port. This check box is selected by
(option for IP-ACM v2 default.
only)
You can use an existing Input Template to create one or more of the IP-ACM Board Inputs. Click in the Template Column,
then click . A list of available iSTAR Input Templates appears. Click on the Template you wish to use. See Using
Templates for Controller Inputs, Outputs, and Readers on Page 44 for more detailed information about using Templates to
create Inputs.
Table 103 on Page 299 provides definitions for the buttons and fields on the iSTAR Ultra IP-ACM Inputs tab.
Field/Button Description
Tamper The Tamper input activates when the controller cabinet is opened or removed from its mounting surface.
NOTE: For UL applications, this field must be enabled.
Select the check box in the Configured column and click located in the Edit column to open the iSTAR Input Editor
General tab to configure the Tamper input. From the Input Editor you can configure the Options, Triggers, Groups, Status and
State Images that are associated with the Tamper Input.
The Template column shows the template name chosen if you selected a Template prior to creating the Input.
Communication A logical unsupervised input that reflects the state of the communication between the GCM board and Processor-A on this IP-
Fail ACM board.
Lock Power IP-ACM can provide power for the locks directly from the 2 Output connectors (Lock Power 1 & 2). There are automatic over-
Alarm Status 1 current shut-off switches on each Lock Power. The Lock Power Alarm Status inputs go Active when the over-current shut-off
Lock Power switches are active (i.e., when Lock Power has been shut off).
Alarm Status 2
Inputs 1 These standard general purpose supervised inputs are available on iSTAR Ultra IP-ACM boards.
through 4
Table 104 on Page 299 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Board Outputs tab.
Table 104: iSTAR Ultra IP-ACM Outputs Tab General Tab Definitions
Field/Button Description
Name Displays the name for this Output board. The name is system-generated by default, but you can edit this name by clicking this
field.
Description Enter a textual comment about the Output board, such as its location or purpose. This text is for information only.
Partition This read-only field identifies the Partition in which this Output board resides.
Maintenance Click to put the iSTAR Outboard Board into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Location
Field/Button Description
Controller This read-only field identifies the iSTAR Controller to which this Output is attached.
Board This read-only field identifies the iSTAR Controller board to which this Output board is attached.
Board Index This read-only field identifies the board index (which represents the SW1 address switch setting on the R/8 board) for this Output
board.
Outputs
Create All Click to create all Outputs. The check boxes in the Configured column are set to .
Outputs
Delete All Click to delete all Outputs. The check boxes in the Configured column are set to .
Outputs
Edit column Click in this column to open the iSTAR Output Editor to edit this Output.
NOTE: The Configured check box must be selected to open the Output Editor.
Index column This read-only field identifies the position of each Output (1 - 2) on the IP-ACM board.
Name column Displays the system-generated name for this Output. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Output. If the Output is not yet configured, you can click in this column, then click to
column select an Output Template. If the Configured column displays , this field cannot be edited.
Table 105 on Page 300 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Wiegand tab.
Table 105: iSTAR Ultra IP-ACM Wiegand Tab Definitions
Box Description
Create All Click to create all the Readers. When you click Create All Readers, the Configured column check boxes are selected, and you
Readers can click in the Edit column to open the iSTAR Reader Editor to configure a direct connect Wiegand Reader.
Delete All When you click Delete All Readers, the check boxes in the Configured column are cleared for all Readers, and all these Readers
Readers are immediately deleted (any settings you have configured are lost).
Edit Click in the Edit column to open the iSTAR Reader Editor to configure a Reader. See iSTAR Reader Editor on Page 496.
column
Box Description
Index This column displays the number for each reader. This number is the physical port number for a Direct Connect Wiegand reader.
column
Name Displays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in this field.
column
Template Click in this column prior to creating the Reader, then click to select a Reader template from the list of available Reader
column templates.
The Template column shows the template name chosen if you selected a Template prior to creating the Reader.
Readers 1 Select the check box in the Configured column for a Reader and click located in the Edit column to open the iSTAR Reader
-2 Editor General tab to configure the Keypad, Triggers, Groups, Status and State Images that are associated with a Reader. See
iSTAR Reader Editor on Page 496 for detailed instructions for configuring iSTAR Readers.
The Name column displays a name comprised of the Reader Type and the iSTAR Controller name. You can click in this column to
edit the Reader name.
The iSTAR Device Port Editor, accessed by clicking in the Configured check box of the port and click Edit, allows you to
select the RM, BLE, or OSDP protocols. See IP-ACM iSTAR Device Port Dialog Box on Page 302
Table 106 on Page 301 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM RS-485 tab.
Table 106: iSTAR Ultra IP-ACM Board RS-485 Tab Definitions
Field/Button Description
Create All Click to create the RS-485 Ports. When you click Create All Ports the Configured column check boxes are selected, and you
Ports can click in the Edit column to open the iSTAR Device Port Editor to configure an RS-485 Port.
Delete All When you click Delete All Ports, the check boxes in the Configured column are cleared for all Ports, and all Ports are
Ports immediately deleted (any settings you have configured are lost).
Edit column Click in the Edit column to open the iSTAR Device Port Editor to configure Device Ports for the IP-ACM. See iSTAR Ultra
ACM RS-485 Device Port Editor on Page 204.
Index column This column displays the number for each Device Port.
Configured Click in this column to create a Device Port (make it available to be edited).
column
Name column Displays the name for this Device Port. The name is system-generated by default, but you can edit this name by clicking in click in
this field.
Field/Button Description
Device Ports 1 Select the check box in the Configured column for a Device Port and click located in the Edit column to open the iSTAR
-2 Device Port Editor General tab to configure the Readers and ACM extensions that are associated with the Device Port. See
iSTAR Reader Editor on Page 496 for detailed instructions for configuring iSTAR Device Ports.
The Name column displays a name comprised of the Device Port and the iSTAR Controller name. You can click in this column to
edit the Device Port name.
Limitations
■ C•CURE 9000 only supports up to two readers (any combination of RM/Wiegand/OSDP readers, and up to two BLE
readers) connected to an IP-ACM.
■ Offline mode is not supported for BLE readers or OSDP readers connected to the IP-ACM.
■ One I8 input module and one R8 module may be assigned to each device port when the port is assigned as an
RM protocol.
■ If you select OSDP, you can select a supported Baud Rate. In most cases, the default, 9600
NOTE baud, is acceptable.
■ Readers that are configured with the wrong Baud Rate may cause communication problems with
other readers. Connecting a chain of readers with any mismatched Baud Rate can keep the entire
chain offline.
For the iSTAR Ultra IP-ACM, you can create the IP-ACM High Latency Alarm Trigger for an iSTAR.
Table 107 on Page 304 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Board Status tab.
Table 107: iSTAR Ultra IP-ACM Board Status Tab Definitions
Field/Button Description
Once you select Serial Number Status the serial numbers are visible whenever the iSTAR Ultra IP-
NOTE ACM Dynamic View is displayed.
This chapter explains how to configure the apC, apC/8X, and apC/L software components to work with C•CURE 9000.
In this chapter
The apC/L is a smaller version of the apC, making it ideal for parking garages and small office buildings. All apC/8Xs and
some apC/Ls provide Flash ROM support, which lets you download firmware from the server to the panel. Up to three
versions of firmware are available for download. See the Monitoring Station User’s Guide for information about
downloading firmware.
Each apC, apC/8X, or apC/L in the system supports Wiegand, proximity, magnetic stripe, and RFID card technologies.
The apC (apC/8X) configuration supports eight card readers wired in a daisy-chain arrangement. The apC/L configuration
supports two card readers.
apC Panel
The basic apC panel has eight supervised inputs, eight relay outputs and one reader port, capable of handling a maximum
of eight readers, which are wired in a multi-drop configuration. Expansion boards can add reader ports, supervised inputs
and additional outputs. By using expansion boards, bus modules and RM-4s, an apC can have as many as 128 inputs and
192 outputs. Depending on the amount of available memory, an apC panel can hold up to 40,000 cards in its database. See
Table 108 on Page 309 for a listing of the standard apC panel’s inputs, outputs and readers. Total indicates that this is the
total number of inputs, outputs or readers for the apC panel.
There are three Star Coupler expansion boards that can be used with the apC panel to add inputs, outputs and readers :
■ Star Coupler – 8 RM readers, 8 relay outputs, 8 unsupervised inputs (see apC Add-On Board Star Coupler Tab on
Page 355 for more information)
■ Mini-Star Coupler – 8 RM Readers (this is the same board as Star Coupler but inputs and outputs are not populated)
■ WPSC – Wiegand Prox Star Coupler includes 2 boards:
• Lower board – 4 Wiegand signaling readers and 4 supervised inputs
• Upper board – 4 Wiegand signaling readers and 4 supervised inputs (the upper board plugs into lower board)
A Star Coupler Reader is an RM reader connected to a Star Coupler. The Mini Star Coupler Reader is an RM reader
connected to the Mini Star Coupler and it differs from the Star Coupler only due to its having no inputs or outputs. The
readers used by these Star Coupler expansion boards are RM or Wiegand signaling readers that are connected to a Star
Coupler.
Table 108: apC Inputs, Outputs and Readers Available
Tamper Input 1
Supervised Inputs 8
Outputs 8
Readers 8 total
Add-On Boards
R8 Output Board 64
Wiegand Proximity Star Coupler Reader Supervised Inputs [Upper and Lower Boards] 8
apC/L Panel
A basic apC/L panel has two readers and two relay outputs. An apC/L is expandable up to 36 inputs and 38 outputs using
RM-4s and bus modules. Depending on the amount of available memory, an apC/L panel can hold up to 40,000 cards in its
database. apC/L panels with Flash EPROMS installed can have firmware upgrades downloaded from the host system.
Tamper Input 1
Outputs 2
Readers 2
Reader Outputs 4
Add-On Boards
R8 Output Board 32
apC/8X Panel
A basic apC/8X panel has eight supervised inputs, eight relay outputs and one reader port, capable of handling a maximum
of eight readers, which are wired in a multi-drop configuration. Expansion boards can add reader ports, supervised input
and additional outputs. Depending on available memory, an apC/8X panel can hold up to 160,000 cards in its database.
apC/8X panels with Flash EPROMS installed can have firmware upgrades downloaded from the host system. See Table
108 on Page 309 for a listing of the apC/8X panel’s inputs, outputs and readers. Total indicates that this is the total number
of inputs, outputs or readers for the apC panel.
A supervised input reports on the status of the wiring between the panel and the alarm device when changes in circuit
resistance are detected. If wiring is cut, the system reports an open circuit. If someone attempts to create a jumper across
the wiring (to prevent the device from reporting), the system reports a shorted circuit. Supervised inputs can report a total
of five conditions to the apC: Short, Open Loop, Line Fault, Inactive or Active. The main board on the apC has eight
supervised inputs.
An unsupervised input does not monitor the wiring. Unsupervised inputs can report two conditions to the panel: Active or
Inactive. With the star couplers, the apC has eight unsupervised inputs available. See To Configure apC Controller Inputs
on Page 333 for more information.
Outputs
An output is an object that associates an alarm device with an output on the panel board or add-on module. The output
turns alarm devices, such as closed circuit TV or alarm dialers, on or off. See apC Controller Outputs Tab on Page 334 for
more information.
Readers
A reader is a hardware device that accepts access requests. To make an access request, a person swipes or presents a
card at the reader. The card reader scans the information encoded on the card and sends it to the apC panel, which grants
or denies access. See apC Controller Readers Tab on Page 334 for more information.
Optional Boards
apCs and apC/8X panels support these optional (add-on) boards and controller:
■ 8 apC I/8 - input modules and 1 apC I/32 input board, and
■ 8 apC R/8 - output modules and 2 apC R/48 output boards, and
Star couplers enable you to wire the apC panel’s 8 readers in a star, daisy-chain, or combination configuration. Star
couplers also provide unsupervised inputs and additional outputs and readers for the apC and apC/8X.
apC/L controllers and Mini Star Couplers have not been evaluated by UL.
NOTE
The apC/L supports two types of optional boards: four I/8 - input modules and four R/8 - output modules.
NOTE
See apC Controller Add-On Board Tab on Page 334 for more information.
Before you configure apC panels, the apC Hardware Interface must be started using the Server
NOTE Management application - Server Components tab. Right-click the apC Hardware Interface and click Start
Server Component.
Example:
If you specify that an apC panel is in the Pacific Time Zone (GMT- 08:00), and the C•CURE 9000 server is in the
Eastern Time Zone (GMT- 05:00), a timed-based action that occurs at the apC panel, such as unlocking a Door,
happens at local time (Pacific Time Zone) for the apC panel.
Example:
If you specify that an apC panel is in the Pacific Time Zone (GMT- 08:00), and the C•CURE 9000 server is in the
Eastern Time Zone (GMT- 05:00), a server-based Journal message shows the server date/time (EST), while a panel-
based Journal Message shows the panel date/time (PST) as highlighted in Figure 88 on Page 312.
Figure 88: Journal Message Showing Local Date/Time
Example:
If you specify that an apC panel is in the Pacific Time Zone (GMT- 08:00), and the C•CURE 9000 server is in the
Eastern Time Zone (GMT- 05:00), a Credential with an Expiration Date set as today at 5:00 PM will expire at 5:00
PM Eastern time, rather than Pacific Time, because the expiration occurs at the server, which is in the Eastern Time
Zone.
The Time Zone setting is configured on the apC controller General tab by selecting a Time Zone from the Time Zone field.
See apC Controller General Tab on Page 331 for more information.
You can change the value of the apC controller Time Zone field only when the apC Controller is not enabled (Enabled field
is blank ). See Changing the Time Zone of an apC Controller on Page 314 for more information.
This is flexible, but also potentially complicated if you have controllers in different Time Zones.
Example:
You create a Schedule to manage Clearances for your night shift. When downloaded to an apC in another Time Zone,
the Schedule works as expected. However, if you apply the Schedule to a C•CURE 9000 Server-based Event ("Lock
all Doors" using the All Doors Group) that affects the Pacific Time Zone apC, the Event's actions would be triggered
in the Server's Time Zone, rather than the Time Zone where the apC resides, perhaps causing Doors to be locked at
the wrong time.
However, if you create separate Schedules and name them to make it clear which Time Zone (or which controller) they are
intended to be used with, you can avoid problems with Time Zone differences.
Example:
You create a Schedule to assign to Door and Elevator Clearances on your apC in the Pacific Time Zone called "Doors
& Elevators - Pacific" and only use this Schedule for Pacific Zone. The Door and Elevator Clearances are downloaded
to the apC controller
The schedules used in an apC panel for timed actions are primarily associated with Door or Elevator clearances.
When a Schedule becomes active, the Journal Message that is displayed identifies the Time Zone associated with the
object (such as an apC panel) to which the Schedule is related.
You can see the active/inactive status of your Schedules with the Schedule by Time Zones Dynamic View, accessible
from the Configuration pane. See the Schedules chapter in the C•CURE 9000 Software Configuration Guide for more
information.
See Defining a Trigger for an apC Device on Page 363 for more information about specifying a Time Zone for an
apC Trigger.
Example:
The C•CURE 9000 server is in the Eastern Time Zone (GMT - 05:00). The apC Panel is in the Pacific Time Zone (GMT
- 08:00). If the Event is activated by a Schedule at 10:00 AM, it will be activated at 10:00 AM Pacific Time (the apC
panel's Time Zone), not 10:00 AM Eastern Time.
For an apC time-based action defined in a Event, if a Time Zone is specified in the Event, the apC driver only downloads
the action to apC controllers with the same time zone as the Event.
If the apC panel is online when the Event is activated by the Schedule, the apC driver sends the timed Action command to
the apC panel.
If the apC Panel is offline when the Event is activated by the Schedule, the apC panel performs the timed Action.
However, the apC does not have the capability, after communication is re-established, to display activation and
deactivation messages for an Event that occurred while the apC was offline.
However, if the Time Zone of the Event Schedule and the Time Zone of the apC panel are different, a warning message
appears to inform you of the discrepancy, called a Time Zone Mismatch, so that you will be aware that the timed Action will
be activated according to the host Time Zone, not the apC panel Time Zone.
Example:
The C•CURE 9000 server is in the Eastern Time Zone (GMT - 05:00). The apC Panel is in the Pacific Time Zone (GMT
- 08:00). If the Event is activated by a Schedule at 10:00 AM, it will be activated at 10:00 AM Eastern Time (server
time), not 10:00 AM Pacific Time.
If the apC panel is online when the host Event is activated by the Schedule, the apC driver sends the timed Action
command to the apC panel.
If the apC Panel is offline when the host Event is activated by the Schedule, the apC panel does not perform the timed
Action, because the Event was not downloaded to the apC panel, and the panel is offline from the host.
If you change the Time Zone of the apC controller, the Time Zone settings of all child objects of that apC controller are
changed as well. A warning message appears if you change the Time Zone and any Events have controller-based actions
on this apC controller and the Event is configured to use a different Time Zone than this apC controller.
1. From the Hardware pane, select the apC controller you wish to change. Right-click and select Edit.
2. Clear the Enabled field (change to ).
3. Click Save and Close to save the change.
4. From the Hardware pane, select the apC controller again. Right-click and select Edit.
5. When the apC controller editor opens, the Time Zone field can be changed.
6. Click Save and Close to save the change.
Report Query
SWH 72 - apC Time Zone Mismatch Actions SWHrep72 - apC Time Zone Mismatch Actions
SWH 74 - Actions with Time Zone Mismatch SWHrep74 - Actions with Time Zone Mismatch Query
See the Reports chapter of the C•CURE 9000 Data Views Guide for more information about these Reports and Queries.
If a Report Query is not specified, the report lists all the apC Controllers and all the actions, noting each action is Online
Only - performed only if the apC panel is Online - if the custom fields in the Action Item class are selected.
Specifying a Report Query allows you to select any apC Controller field and any Action Item field, including these custom
fields:
■ Online Only - whether the action can occur only on an online apC)
■ Online Only Reason - the reason that an action can only occur on an online apC. Possible values are:
• Time Zone Mismatch - The Time Zone of the timed action is different from the Time Zone of the controller.
• No Firmware Support - The action is not supported by the controller, so it must be executed on the host.
• Cross Panel Action - The action is activated by one controller and modifies an object on another controller.
• Invalid Configuration - The action cannot be activated (for example, a change in Comm Fail status should cause an
Event to activate an Output on the same controller, but the Comm Fail prevents the Event from communicating
with the Output.)
1. From the Data Views pane, select Report from the drop-down list of objects, then click .
2. Select either:
■ SWH70 - apC Input Groups with Time Zones
■ SWH71 - apC Door Groups with Time Zones
3. Right-click and choose Edit. The Report editor opens.
4. Click Create Copy. A new Report opens in the Report editor, based on the pre-defined Report you chose.
5. Click in the Report form field if you want to select a different Report From.
6. Click in the Report query field if you want to select a Query for the Report.
7. Select Prompt for Query if you want to display a Query Parameter Prompt when the report is run.
8. Click the drop-down list for the Layout style if you want to change the Report layout.
9. Change the fields in the Class selector and the Field selector if you want to change the fields displayed on the
Report.
10. Click the Layout Design tab if you want to manually change the Report design.
11. Click the Layout Preview tab to see a preview of how the Report will look.
12. Click Save and Close to save the Report.
13. The Report is added to the Reports Dynamic View. You can double-click the Report to run it.
The Update Firmware selection does not appear if the apC is not Enabled or is off-line.
NOTE
3. The apC Firmware Download dialog box opens (see Figure 90 on Page 319).
4. Select the firmware version that you want to download from the list in the dialog box.
5. Click Start firmware download. A progress bar shows you the when the download is completed.
6. When the download has completed, click Close to close this dialog box.
Do not attempt to download firmware to more than one apC panel on a chain at one time, and do not
TIP attempt to download firmware if that chain is busy doing a personnel download.
The following summary gives you an outline of the configuration process, with links to topics that provide the details.
Table 111: apC Configuration Summary
Configuration See...
1. Create and configure an apC Comm Port. apC Comm Port Editor on Page
322
3. Use the apC Controller General Tab to configure the Connection Type, Comm Port, Reader LCD apC Controller General Tab on
Message set, apC Type, Time Zone, and apC Address. Page 331
4. Use the apC Controller Communications Tab to configure communications parameters for the apC. apC Controller Communications
Tab on Page 333
5. Use the apC Controller Inputs Tab to configure Panel Status Inputs and Supervised Inputs. apC Controller Inputs Tab on
Page 333
Edit each apC Input on the apC Input Editor Triggers tab, and State Images tab, and view the Input's apC Input Editor on Page 340
status on the Status tab.
6. Use the apC Controller Outputs Tab to configure apC Outputs. apC Controller Outputs Tab on
Page 334
Edit each apC Output on the apC Output General Tab and State Images tab, and view the Input's apC Output General Tab on Page
groups and status on the Groups tab and Status tab. 343
7. Use the apC Controller Readers Tab to configure apC Readers and options. apC Controller Readers Tab on
Page 334
Edit each apC Reader on the apC Reader General Tab, I/O tab, Keypad tab, Triggers tab, and State apC Reader General Tab on Page
Images tab, and view the Input's status on the Status tab. 520
8. Use the apC Controller Add-On Board Tab to create and configure an apC add-on board. apC Controller Add-On Board Tab
on Page 334
Edit each apC Add-on Board from the apC Add-on Board Editor, configuring Input Boards, Output apC Add-on Board Editor on Page
boards, and Star Couplers. 350
Edit the apC Input boards from the apC Input Editor, creating I/32 and I/8 Input boards, as needed. apC Input Editor on Page 340
Edit each apC Input from the apC Input Editor, configuring Supervised Inputs and Status Inputs.
If you created a Star Coupler, use the apC Star Coupler Board Editor to create Readers, apC Star Coupler Board Editor on
unsupervised inputs, and outputs. Page 360
If you created a Mini Star Coupler, use the Mini Star Coupler Board Editor to create apC Readers. Mini Star Coupler Board Editor on
Page 366
Configuration See...
If you created a WPSC, use the Wiegand Proximity Star Coupler Editor to create Readers and Wiegand Proximity Star Coupler
Inputs. Editor on Page 367
9. Use the apC Controller Triggers Tab to set up triggers for Actions based on apC controller property apC Controller Triggers Tab on
states. Page 335
10. Use the apC Controller Holiday Groups Tab to add Holiday Lists to the apC. apC Controller Holiday Groups
Tab on Page 335
11. You can view Controller Status from the apC Controller Status Tab. apC Controller Status Tab on
Page 335
12. You can change the state images that appear in the Monitoring Station to represent this controller on apC Controller State Images Tab
the apC Controller State Images Tab. on Page 338
13. You can view the apC Controller groups to which this apC belongs on the Groups Tab for Hardware Groups Tab for Hardware Devices
Devices on. on Page 36
An apC panel can communicate with serial port connections, using RS-232 connections to an RS-485 converter, or via an
Ethernet-connected network.
For general instructions about the Hardware pane see Using the Hardware Pane on Page 28.
The apC Comm Port editor appears (see Figure 92 on Page 323). See Table 112 on Page 325 for definitions of the
fields on the Comm Port editor General Tab
.
You may also choose New Template. For further information about creating Templates, see Creating a Template on
Page 41.
2. Enter a unique Host Communications Port Name (required).
3. Optionally, enter a textual description of the apC Comm Port in the Description field.
4. Select the Enabled check box if you want the Comm Port online after you have completed the configuration
procedure.
5. Select the Communications Type.
• For an apC Controller that uses a network communications path, click Network Port. See Configuring an apC
Comm Port Network Connection on Page 324.
• For an apC that uses a serial connection to the C•CURE 9000 server, click Serial Port. See Configuring an apC
Comm Port Serial Port on Page 324
• For an apC that uses a redirected serial connection to the C•CURE 9000 server, click Redirect Serial Port. See
Configuring an apC Comm Port Redirect Serial Port on Page 325.
6. You can set a Port Timeout Delay Time in tenths of a second units by typing it within the entry field or by using the
selection arrows. The range is 0 through 99; the default entry is 0.
7. When you have completed configuring the apC Comm Port General tab, you can click Save and Close to save your
changes, or you can click the Triggers tab (see apC Comm Port Triggers Tab on Page 327) to continue configuring the
apC Comm port.
The Fields on the apC Comm Port General tab are described in Table 112 on Page 325.
Table 112: apC Comm Port Field Definitions
Field Description
Name Enter a unique name up to 50 characters long for the controller. If you enter the name of an existing object, the system returns an
error message indicating there is a conflict.
Description Enter a textual comment about the controller, such as its location or purpose. This text is for information only.
Field Description
Enabled This setting determines whether or not the apC Comm Port is able to provide communication between the apC Controller and the
C•CURE 9000 Server. Select Enabled to set the Comm Port online. To take the Comm Port offline, you can clear the Enabled
selection.
NOTE: If the apC Comm Port is currently in use by apC controllers, you must disable all of the controllers before you attenpt to
take the Comm Port offline. If any apC controllers are enabled when you attempt to take the apC Comm Port offline, an
error message is displayed - "Port cannot be disabled with enabled controllers. Please disable controllers first. When the
controllers are re-enabled they will do a full personnel download."
The message explains that when you re-enable the apC Comm Port, then re-enable the apC controllers, each controller
will perform a full personnel download.
Maintenance Click to put the apC Comm Port into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Partition This read-only field identifies the Partition in which this Controller resides.
If you are creating a new Controller, the Partition that is currently the New Object Partition for your Operator account is
automatically assigned to each Controller you create.
If you want to change the Partition of a Controller, you must move the Cluster in which the Controller resides. See Using Drag and
Drop in the Hardware Tree on Page 35.
Communications Type
Network Select Network Port if you are using a terminal server to connect your apC to C•CURE 9000.
Port
Serial Port Select Serial Port if you are using a serial connection for your apC.
Redirect Select Redirect Serial Port if you are redirecting the serial connection for an apC to a serial port that is physically on a Terminal
Serial Port Server, but logically on the C•CURE 9000 Server.
Port Settings
Port Timeout The Port Timeout Delay Time is the extra interval that the host waits for a response from the apC panel after sending a
Delay Time message to the panel. If the host does not receive a response in the specified time, the host retransmits the message or declares a
(1/10 sec) communications failure. This field allows you to set the timeout delay for all panels that use a specific port.Software House
recommends that you set this period to 20 (2 seconds). However, if you require additional delay time because apC panels run on a
Digiboard, Equinox board, or over a network, you may need to increase this value. Keep this value as small as possible, or system
performance may be affected. If your panel goes into communications failure often, try setting this value between 30 (3 seconds)
and 50 (5 seconds).
Re- Re-connection Retry Period is the duration that the host waits to declare an unresponsive panel to be in failure. Software
connection House recommends that you set this period to 300 (30 seconds) which is the default value.
Retry Period
(1/10 sec)
IP Address The IP address of the terminal server C•CURE 9000 that is being used to communicate with the C•CURE 9000 system.
TCP Port The address of the node from which the apC Host TCP Port communicates with the C•CURE 9000 system. The values range
from 0 through 9999. The default entry is 3001.
Field Description
COM Port Select the Communications Type Serial Port from the drop-down list. The Name field will reflect the port number that you select.
The range is COM1 through COM256.
This tab provides you with ability to activate an event based on the Comm Status of the apC Comm Port. If the Comm
Status property of the apC Comm Port changes, you can specify the event you want to activate.
A typical use for a Comm Port trigger would be to warn the Monitoring Station of a communications failure. You can
configure an event that would send a message requiring acknowledgment when the apC panels are unable to
communicate with the host.
1. Click the apC Comm Port Triggers tab to provide a means to link the Comm Port to an event.
Example:
A typical use for a Comm Port trigger would be to warn the Monitoring Station of a communications failure. You can
configure an event that might send a message requiring acknowledgment when the apC panels are unable to
communicate with the host, as shown in Figure 95 on Page 327.
Figure 95: apC Comm Port Triggers Tab
2. Choose a Property for the Trigger from the Property drop-down list.
3. Select the value that you want to activate the Trigger from the Value drop-down list.
4. Pick the Action you want the Trigger to perform from the Action drop-down list.
5. Depending upon the Action you chose, you may need to select the Action details from the Details field. For example, if
you chose to Activate an Event with the Action, you need to select an Event from the Details field. Click and
select an Event from the selection box that appears.
6. Click Save and Close to save the Trigger settings for the apC Comm Port.
To restore the default image, right-click on the new image and select Restore Default.
2. From the Hardware context menu, choose apC Controller and New. The apC Controller General tab appears, as
shown in Figure 99 on Page 331.
You may also choose New Template. For further information about creating Templates, see Templates on Page 41.
If the New and New Template selections are unavailable, you may be trying to create an apC in a Partition that is not
your New Object Partition, or you do not have Privileges to create objects in this Partition. Check the C•CURE 9000
Menus to verify that your New Object Partition setting is correct, and check with your C•CURE 9000 administrator
that you have the correct Privileges.
The apC Comm Port you choose in Step 5 must also be Enabled; otherwise, the apC cannot remain
NOTE enabled. If you save the apC controller after assigning a disabled apC Comm Port, the apC will go
offline and when you open the apC object again in the apC editor, the Enabled check box will no longer
be checked.
4. Select Direct Connect as the type of connection between the host and the apC. Use the Port field in this dialog box
to specify a port to which the apC chain is connected.
5. To select a host communications Port for the apC controller, click in the Port field to select an apC Comm Port.
Software House strongly recommends that you select an apC comm port that is in the same partition
NOTE as your apC.
The example in Figure 99 on Page 331 shows the selection of a Serial Port connection.
6. To select a particular customized set of LCD messages for the RM Readers, click to display a Reader LCD
Message Set selection list. If you leave this field blank (the default), the Readers use the default messages.
7. Select the Time Zone in which your apC panel resides by clicking and selecting the Time Zone from the list that
appears. If you leave this field blank, the apC panel Time Zone defaults to the C•CURE 9000 server setting. You can
only change the value of the apC controller Time Zone when the apC Controller is not enabled (Enabled field is blank
). See Changing the Time Zone of an apC Controller on Page 314.
8. Select the type of apC panel you are configuring from the apC Type and Address box:
• apC
• apC/8X
• apC/L
9. Rotary switch settings can also be set on the apC panels using the two Switch entry fields.
For apC/L panels, the rotary switches are labeled 3-8 and 1. For all the other apC types, switches 4 and 5 are
displayed. The range of settings is 0 through 9 or A through F for all but Switch 3-8, which has a range of 0 or 1.
The values you enter for Switch 4, Switch 5, Switch 1, and Switch 3-8 should match the switch settings on the
physical apC controller.
10. The Panel is nearly full when it reaches the percent of capacity field allows you to enter a range from 0% to 99%.
11. The final entry field on the apC Controller - General tab is in the Priority box. Select a numeric value to assign a Base
Priority for Cause. The range is from 0 to 255.
When configuring an Event, you can assign an Event Priority. The Event Priority allows you to rank the importance of
a particular Event relative to other Events in the system. If Events occur simultaneously, Event Priorities enable the
system to execute responses in the proper sequence.
C•CURE 9000 provides eight priority ranges, each containing 25 priority settings, for a total of 200 possible Event
Priorities.
12. Click the Communications tab to display it, as shown in on Page 333.
You can also click Save and Close to return to the Hardware Pane and finish the apC Controller configuration later.
Setting the poll period to more than 30 will result in up to a 3 or 4 seconds delay between reading the card
NOTE and opening the door.
2. Enter the extra interval in tenths of a second that the host waits for a response from this panel after sending a message
to the panel in the Poll Timeout delay time field. If the host does not receive a response in the specified time, the
host retransmits the message or declares a communications failure.
Software House recommends that you set this period to 80 (8 seconds). However, if you require additional delay time
because the panel runs on a Digiboard, Equinox board, or over a network, you may need to increase this value. Keep
this value as small as possible, or system performance may be affected. If your panel goes into communications
failure often, try setting this value between 80 to 110. The range is 0 - 999.
3. Enter the interval in tenths of a second that the host waits to declare an unresponsive panel to be in failure in the Panel
communications failure delay time. A message appears on the Monitoring Station in the case of a panel failure.
Software House recommends that you set this period to 200 (20 seconds). The range is 0 - 850.
4. Enter the interval in tenths of a second that the system polls the panel while it is in communications failure in the Poll
period while in communications failure entry field. Typically, you should set this value higher than the value for the
initial poll period to avoid slowing down polling of other units on the chain.
Software House recommends that you set this period to 200 (20 seconds). The range is 0 - 999.
5. Enter the time period in minutes and seconds (mm:ss format) that the panel waits for a message from the host after
receiving the communications failure message from the host in the Host communications failure delay time entry
field. If the panel does not receive a message in the specified time, the panel declares a communications failure.
Software House recommends that you set this period to 1:00 (1 minute).
6. Click the Inputs tab to display it.
To configure Inputs, select the check box in the Configured column and click located in the Edit column to display
the apC Input editor General tab. See the apC Input Editor on Page 340.
Click the Delete All check box where ever it appears and then click Save and Close if you want to
NOTE eliminate all the Inputs, Outputs, or Readers that you have configured in a given dialog box.
To take an apC panel offline, remove the check from the Enabled option check box located below each
Reader, Input, or Output board Description entry field (located in General tabs).
Use the Template column to quickly configure all in a particular set of inputs, outputs or readers.
TIP
You may configure an apC Reader from the apC panel Readers tab or from the Add-on Board tab. A
NOTE reader index configured on one tab will be unavailable on the other tab. The location chosen will affect the
possible reader type and reader input/output option selection.
To start the configuration of Add-On Boards, select the check box in the Configured column in the apC Add-On Board
tab and click located in the Edit column to display the apC Add-On BoardGeneral tab (see apC Add-on Board Editor
on Page 350).
You can click Save and Close after configuring apC triggers, or navigate to the Status tab.
You can include a Holiday in a Holiday Group and assign a Holiday Group to a schedule.
You need to configure the Holiday Groups that should apply to each apC, so that schedules on that apC respect the correct
Holidays. If a Holiday Group is not listed on this tab, the Holidays it contains are not applied to this apC.
If a schedule downloaded to the apC has a Holiday Group assigned, and that Holiday Group is listed on this tab, the
activation times in the Holiday Group are evaluated. If the schedule is active and one of the Holidays in the Holiday Group
is active, the start time and end time assigned with the Holiday Group become the schedule’s start time and end time.
For more information about apC Holiday Groups, see the C•CURE 9000 Software Configuration Guide.
To use the Holiday Groups tab, see Configuring Holiday Groups for an apC Panel on Page 336 for more information.
A Holiday Group downloaded to an apC panel acts as an override to prevent activation of normally scheduled clearances
on the Holidays defined in the Holiday Group. You can configure up to 8 holiday groups for each apC panel.
Only Holiday Groups that are downloaded to an apC panel will affect access control at that panel.
5. To remove one or more Holiday Groups, click a Holiday Group to select it (use CTRL+Left-click to select multiple
Groups), then click Remove to remove the selected Holiday Groups from the panel.
6. Click the State Images tab to display it, as shown in on Page 338.
- Or -
Click Save and Close to return to the Hardware Pane to finish the apC Controller configuration.
See the C•CURE 9000 Software Configuration Guide for more information.
To Change an Image
1. Double-click the existing image.
A Windows Open dialog box appears allowing you to browse for a folder in which you have placed replacement
images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click on the new image and select Restore Default.
4. Click Save and Close to finish the apC Controller configuration and return to the Hardware Pane.
■ Tamper
■ Comm Fail
■ General
Assigned To - displays the name of an associated Door or Elevator Button. If the Input is used for a door, then the
Name field is read-only displaying the name of the controlled door.
Connection - specifies the input connection point on the Input Board and is assigned when the Board is configured.
The Supervised check box must be selected for Proprietary Burglar Alarm applications.
NOTE
2. To have a notification of changes in state of the Input sent to the guard station, select the Send state changes to the
monitoring station check box.
The Send state changes to the monitoring station option must be selected for Proprietary Burglar
NOTE Alarm applications.
3. To have a notification of changes in state of the Input sent to the journal, select the Send state changes to journal
check box. This option will be selected by default.
You may limit the transmission of state change messages to the journal exclusively, when you click to
NOTE de-select the Send state changes to the monitoring station option and instead, select the Send
state changes to journal option. Use of the latter option can decrease the messaging traffic derived
from the apC Input during normal operations. To further limit messaging, you may also leave both
check boxes unselected.
You may select multiple Inputs in a dynamic view and use the Set Property option to limit the
transmission of state changes. See Using Set Property for an iSTAR Controller on Page 137, for more
information.
4. Activate on Supervision Error – Select this check box if the input is supervised and you want it to activate when a
supervision error occurs.
5. Click Save and Close or the Triggers tab to display it, as shown in on Page 341.
To Change an Image
1. Double-click the existing image.
A Windows Open dialog box appears allowing you to browse for a folder in which you have placed replacement
images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click on the new image and select Restore Default.
4. Click Save and Close.
The apC Output General tab lists the following read-only fields:
Type - reflects whether the Output has been assigned to a Door or other object. For apC panels, General is the un
assigned output type.
Assigned To - displays the Elevator or Door object name. For any Output, the Connection field indicates the index
number on the board.
Figure 103: apC Controller Outputs General Tab
a. Pulse Duration – (momentary activation) is entered in tenths of a second intervals with a default of 0 seconds. The
range is 0 to 1000.
b. Normally Energized – When checked, the output is energized (power is supplied to the relay) when it is inactive.
When the output is activated, power is removed.
c. To have a notification of changes in state of the Output sent to the Monitoring station, select the Send state
changes to the monitoring station check box. This selection is unavailable for an apC Door Output. State
changes for a Door Output are not sent to the Monitoring Station.
d. To have a notification of changes in state of the Output sent to the journal, select the Send state changes to
journal check box. This option is selected by default. This selection is unavailable for an apC Door Output. State
changes for a Door Output are not sent to the journal.
You may limit the transmission of state change messages to the journal exclusively, when you click
NOTE to de-select the Send state changes to the monitoring station option and instead, select the Send
state changes to journal option. Use of the latter option can decrease the messaging traffic derived
from the apC Output during normal operations. To further limit messaging, you may also leave both
check boxes unselected.
You may select multiple Outputs in a dynamic view and use the Set Property option to limit the
transmission of state changes. See Using Set Property for an iSTAR Controller on Page 137, for
more information.
2. Click Save and Close or the apC Outputs - Status tab to display it, as shown in on Page 344.
For further information about the use of the Groups tab, see Groups Tab for Hardware Devices on Page 36.
To Change an Image
1. Double-click the existing image.
A Windows Open dialog box appears allowing you to browse for a folder in which you have placed replacement
images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click the new image and select Restore.
You can add or remove Card Formats from multiple Readers via an apC Reader Dynamic View. See Add or Remove
Reader Card Formats on Page 33 for more information.
You may configure an apC Reader from the apC panel Readers tab or from the Add-on Board tab. A
NOTE reader index configured on one tab will be unavailable on the other tab. The location chosen will affect
the possible reader type and reader input/output option selection.
See the C•CURE 9000 Getting Started Guide - Table 1-5 for a list of UL approved card formats and
readers.
3. Click the applicable row in the Card Format browser to select Card Format. Repeat for multiple formats.
4. Navigate to the Input/Output (I/O) tab (see on Page 521).
You can click Save and Close after configuring apC Reader triggers, or navigate to the Status tab.
To Change an Image
1. Double-click the existing image. A Windows Open dialog box appears allowing you to browse for a folder in which you
have placed replacement images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click on the new image and select Restore Default.
4. Click Save and Close.
To Configure the I32 Input Board Using the apC Input Boards Tab
■ To configure the I32 Input Board, select the check box in the Configured column in the apC Add-On Board - Input
Boards tab and click located in the Edit column of the Supervised I32 Input Board box to display the apC I32
Input BoardGeneral tab.
1. To configure the R48 Output Board, select the check box in the Configured column in the apC Add-On Board Output
Boards tab and click located in the Edit column of the R48 Output Boards box to display the apC R48 Output
Board General tab.
The apC R48 Output Board General tab displays three read-only fields:
■ Controller
■ Board
■ Board Index
These fields locate the Output that you have chosen to configure. As you configure more Add-On Board Outputs for
this controller, the Board Index field reflects the output placement on the R48 output board, ranging from 1 through 2.
2. To configure Outputs, select the apC R48 Output 1-16 Outputs tab.
3. To configure the Outputs on the Add-On Board R48 Outputs 1-16 Outputs, 17-32 Outputs and 33-48 Outputs tabs,
follow the instructions given in To Configure apC Outputs on Page 334.
4. Once you have finished configuring the R48 Outputs, click Save and Close to return to the apC Add-On Board Output
Boards tab.
R8 Output Board
The apC R8 Output Board General tab displays three read-only fields:
■ Controller
■ Board
■ Board Index
These fields locate the Output that you have chosen to configure. As you configure more Add-On Board Outputs for
this controller, the Board Index field will reflect the output placement on the R8 output board, ranging from 1 through 8.
There are also two Status inputs available for the R8 Output Board:
You will not see comm fail or tamper until at least one of the inputs or outputs is configured.
NOTE
2. To configure the R8 Output, select the check box in the Configured column in the apC R8 Output Board General tab
and click located in the Edit column of the R8 Outputs box, as shown in Figure 106 on Page 353.
3. To configure each R8 Output, follow the instructions given in To Configure apC Outputs on Page 334.
4. Once you have finished reader the R8 Outputs, click Save and Close to return to the apC Add-On Board Output
Boards tab.
5. Click the Star Coupler tab to configure Star Coupler Readers, Inputs and Outputs, Mini Star Readers and WPSC
(Wiegand Proximity Star Coupler) Readers and Supervised Inputs.
Because the apC can only support 8 readers, some of the Reader ports on the Star Coupler may be
NOTE unavailable to configure on C•CURE 9000 if readers are configured directly on the apC Readers tab. For
example, if Readers 1 and 6 are configured on the Readers tab, Readers 1 and 6 will be unavailable on the
Star Coupler (Configured check box is read-only). Conversely, if Readers 1 and 6 are configured on the
Star Coupler, then Readers 1 and 6 on the Readers tab will be unavailable.
The Mini Star Reader has not been evaluated by UL and cannot be used in UL Listed applications.
NOTE
or
■ WPSC (Wiegand Proximity Star Coupler) with up to 8 WPSC Readers and 8 Supervised Inputs on upper and lower
boards. See the Wiegand Proximity Star Coupler Editor on Page 367.
If you select a Star Coupler and then try to enable a different one, a message appears
NOTE asking "Are you sure you want to delete the Star Coupler object ,object-name>?"
because you can only have one Star Coupler configured.
Click Yes if you want to delete the Star Coupler you configured and replace it with your
new choice.
Click No if you want to keep the Star Coupler you configured and cancel this action.
Field/Button Description
Edit Column Click in the Edit column to open the editor for the Star Coupler you have enabled.
Star Coupler This column displays the type of each Star Couplers you can enable and configure.
Column
Configured Click in this column to enable a Star Coupler, Mini Star, or WPSC (make it available to be edited) .
Name Displays the name for this Star Coupler. The name is system-generated by default, but you can edit this name by clicking in click
in this field.
Star Coupler The Star Coupler is a single expansion board that attaches to the apC/8X or apC to allow the RM readers, I/8 inputs, and R/8
outputs to be wired in a Star topology.
Mini Star A Mini Star is a single expansion board that attaches to the apC/8X or apC panels to allow the RM readers to be wired in a star
topology.
WPSC The Wiegand/Proximity Star Coupler (WPSC) consists of a two board set that attaches to the apC or apC/8X to allow direct
connection of up to 8 read heads using Wiegand signaling.
These fields identify the Input board that you have chosen to configure. The Board Index field reflects the position of the
I32 input board on the apC.
The apC Input General tab displays the Input Location - Controller, Board and Connection fields. These are read-
only fields that display the apC panel, the apC Add-On Board and Input Number associated with an I32 Supervised
Input. These fields locate the Input that you have chosen to configure.
2. To configure the Inputs on the I32 Input Board - 1-16 Inputs tab, follow the instructions given in To Configure apC
Controller Inputs on Page 333.
3. Navigate to the 17-32 Inputs tab.
Star Couplers are single expansion boards that attach to the apC/8X or apC to allow the RM readers, I/8 inputs, and R/8
outputs to be wired in a Star topology. The Star Coupler Board allows addition of:
■ 8 MRM/RM Reader ports
■ 8 Unsupervised Inputs
■ 8 dry contact, form C, relay Outputs
The Star Coupler can be installed on apC and apC/8X panels. For more information, see the Star Coupler - Mini Star
Coupler Quick Start Installation Guide.
This editor is accessed from the apC Add-on Board Editor Star Coupler tab (see apC Add-On Board Star Coupler Tab on
Page 355).
2. Click the Readers tab to configure the Star Coupler readers. See Star Coupler Readers Tab on Page 361 for the Star
Coupler Readers tab.
3. Click the Unsupervised Inputs tab to configure the Star Coupler unsupervised inputs. See Star Coupler
Unsupervised Inputs Tab on Page 361 for the Star Coupler Unsupervised Inputs tab.
4. Click the Outputs tab to configure the Star Coupler outputs. See Star Coupler Outputs Tab on Page 362 for the Star
Coupler Outputs tab.
5. When you have completed configuring the Star Coupler and its attached devices, you can click Save and Close to
save your changes.
A triggers tab provides you with the ability to define the activation/deactivation, enable/disable, and arm/disarm, etc. of
such objects as: events, inputs, outputs, camera actions, door status changes, etc. Triggers can also be used to launch
imports and exports, email and reports, viewer and message displays, personnel ID number state changes, controller
downloads, sound activation, communication notifications, etc.
Active Status Active Activate Event apC Input Event Always (Time Zone of apC or C•CURE 9000
Server)
From the Triggers tab of an apC device (such as a Controller, Input, or Reader), you can perform the following tasks.
■ Defining a Trigger for an apC Device on Page 363.
■ Removing a Trigger on Page 279.
apC Triggers Tab Definitions on Page 364 provides definitions for the fields and buttons on an apC Device Triggers tab.
This tab provides you with the ability to define the activation/deactivation, enable/disable, and arm/disarm, etc. of such
objects as: events, inputs, outputs, camera actions, door status changes, etc. Triggers can also be used to launch imports
and exports, email and reports, viewer and message displays, personnel ID number state changes, controller downloads,
sound activation, communication notifications, etc.
Example:
When an apC Tamper Input changes from the Inactive (normal) to Active (abnormal) state, you wish to activate an
Event and activate an audible alarm (an apC Output).
Example:
If you have apC panels that are in different Time Zones than your C•CURE 9000 server, you may want to have some
Triggers activate according to the apC panel's Time Zone, while other Triggers are activated according to the server
Time Zone.
When you specify the Time Zone for a Trigger definition to be the same as the apC Panel Time Zone, the Schedule
activation times for the Trigger occur according to the apC Panel Time Zone.
If you have an apC panel in the Pacific Time Zone (GMT - 08:00) and a server in the Eastern Time Zone (GMT - 05:00),
a Schedule that is active from Midnight to 6:00 AM is activated from Midnight to 6:00 AM in Pacific Time rather than
Eastern time (three hours later).
For example, if an Event field is displayed in Details, you can click to select an Event that you want to associate with
the Trigger.
9. If the Triggers tab includes a Schedule column, click within the Schedule column to display a drop-down list of pre-
configured schedules. Click to select a Schedule that you want to associate with the trigger. Schedules are
created in the Configuration Pane. See the C•CURE 9000 Software Configuration Guide for more information.
10. If the Triggers tab includes a Time Zone column, click within the Time Zone column to display a drop-down list of
available Time Zones. If the Time Zone column is blank, or you do not select a Time Zone, the Time Zone of the
C•CURE 9000 server is used by default.
11. Click Save and Close to save the apC trigger.
Triggers related to apC objects cannot activate an Event that is downloaded to an iSTAR controller.
NOTE
Field/Button Description
Remove
Click the Row Selector , then click Remove in the Triggers tab to delete a trigger.
Property Click within the Property column, and then click . The Property browser opens presenting properties available for the
Comm Port. Click a Property to select it and add it to the column.
Value Click within the Value column to display a drop-down list of Values associated with the Property that you have selected. Click a
Value that you want to include as a parameter for the trigger to add it to the column.
Action Click within the Action column to display a drop-down list of valid actions. Click an Action that you want to include as a
parameter for the trigger to add it to the column.
As you select an Action, a corresponding entry field, or group of entry fields, appear at the bottom of the dialog box.
Click to select entries for these fields.
Time Zone Click within the Time Zone column to select a Time Zone for Schedule activation.
Click to select a Time Zone that you want to associate with the trigger Schedule. If you specify a Time Zone, the Schedule
start and end times are calculated using that Time Zone. For example, a Schedule that becomes active at 3:00 AM would
become active at 3:00 AM in the Pacific Time Zone, if that Time Zone was specified. Refer to the C•CURE 9000 Software
Configuration Guide for more information on Time Zones.
Mini Star Coupler Boards have not been evaluated by UL and cannot be used in UL Listed applications
NOTE
Readers that are unavailable have already been configured on the apC panel Readers tab.
NOTE
4. Click Save and Close to return to the apC Controller - Add-On Board - Star Coupler tab.
Be sure that the Mini Star Coupler Board is installed correctly on the apC or apC/8X. For more information, see the
Star Coupler - Mini Star Coupler Quick Start Installation Guide.
5. Click Save and Close to return to the apC Controller - Add-On Board tab.
When using the WPSC Add-On Board, the standard Star Coupler cannot be used because the WPSC board set attaches
to the same bus connector as the Star Coupler.
Each board provides one supervised input for each reader, which should be used in conjunction with one of the 8
supervised inputs on the apC main board to provide a total of two supervised inputs for each reader.
The supervised inputs on the WPSC remain inactive in the Monitoring Station unless readers are configured
NOTE in the WPSC editor.
Since the WPSC board set does not provide output relays, it is recommended that the 8 on-board apC relays be used. For
more information, see the WPSC Quick Start Installation Guide.
Chapter 9 - Floors
This chapter explains how to configure Floors in C•CURE 9000. Floors are part of Elevator access control. An Elevator
associates a Floor with an Input or Output.
In this chapter
Floors Overview
Floors are configured to define Elevator control. Floors are paired with inputs and outputs to control floor access through
elevators. Before you can configure elevators, you must configure floors and/or floor groups. See Elevator Configuration
Overview on Page 552 for more information.
When a person presents a card at an elevator, the system checks the clearances associated with the card for the elevator
and associated floors. If the person’s clearances do not allow access, the access attempt is rejected before the person
presses an elevator button. If the person has access to a floor, the system grants access to the person and activates the
output attached to the button for that floor.
A Floor has only Name, Description and Enabled properties. If the Floor has been assigned to any Elevators, they will
appear in a read-only list on the Floor General tab.
Configuring Floors
8. Maintenance Mode - Click to put the Floor into Maintenance Mode. See Chapter 3: Maintenance Mode for more
information.
9. Click Save and Close when you are finished.
10. When you create a Floor group, a Group tab will appear with the Floor General tab, as shown in Figure 110 on Page
372.
Figure 110: Floor Groups Tab
Floor Definitions
The definitions for the fields and buttons on the Floor General tab are listed in Table 116 on Page 372.
Table 116: Floor General Tab
Field/Button Description
Maintenance Mode Click to put the floor into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Field/Button Description
Enabled Check this box to put the floor online. When the floor is offline, the C•CURE 9000 System ignores the floor.
Accessed Displays a list of elevators with buttons associated with this floor. These associations are set when you configure the
Elevators Elevators.
Save and Close Click Save and Close to accept your changes to the Floor configuration.
Creating a Floor
You can create a new Floor.
To Create a Floor
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Select Floor from the Hardware pane drop-down list.
3. Click New to create a new Floor. The Floor Editor opens and you can configure the Floor.
4. To save your new Floor, click Save and Close.
Alternatively, if you want to save the Floor and then create a new one, click Save and New. The current Floor is
saved and closed, but the Floor Editor remains open to allow you to create a new Floor.
The new Floor template appears under Templates in the Template drop-down list.
Deleting a Floor
You can delete a Floor.
To Delete a Floor
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Select Floor from the Hardware pane drop-down list.
3. Click to open a Dynamic View showing all Floor objects.
4. Right-click the Floor in the list that you want to delete and select Delete from the context menu.
5. Click Yes on the “Are you sure you want to delete the selected Floor?” message box.
Modifying a Floor
You can edit a Floor.
To Edit a Floor
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Select Floor from the Hardware pane drop-down list.
3. Click to open a Dynamic View showing all Floor objects.
4. Double-click the Floor in the list that you want to modify and select Edit from the context menu. The Floor Editor
opens.
Chapter 10 - Doors
A Door in C•CURE 9000 provides access control by specifying the controllers, readers, inputs, and outputs associated
with an entrance. From the application’s hardware tree, you will configure the specific controller type first, then configure
the associated readers, inputs, and outputs, and then configure the Door. This sequence of reader the security
components is necessary because each door requires the associated components to operate with their apC or iSTAR
controllers.
In this chapter
Door Overview
In general, a door is a logical structure that ties together a controller and its associated readers, inputs, and outputs for
access control. In C•CURE 9000, before you configure the door you must first configure the type of controller that is to be
used for the readers, input, and outputs. Then you can configure the door associated with the components.
Figure 112 on Page 378 represents the way readers, inputs, outputs, events, and areas are related to Doors in C•CURE
9000, while Table 117 on Page 378 describes typical door components.
Figure 112: Typical Door Configuration
Component Description
RTE Input A Request To Exit (RTE) input sends a signal that lets C•CURE 9000 know that someone is going to open the door to exit.
Typically this device is a motion sensor or a press to exit button.
DSM Input A Door Switch Monitor (DSM) sends a signal that lets C•CURE 9000 know whether the door is open or closed.
DLR Output A Door Latch Relay (DLR) is used to send a signal from C•CURE 9000 to a door latch to lock or unlock the door.
ADA Output An output that activates a door assistance mechanism, usually installed for compliance with the Americans with Disabilities Act
(ADA).
Reader Defines the card readers that control entry or egress through this door.
In/Out
Events Door events are usually triggered by state changes in the Door inputs and outputs. You specify the Event you want to activate
when a change, such as “Door held open,” occurs.
Area In/Out Defines the Area a cardholder enters and the area a cardholder leaves through this door.
Example:
A cardholder passing through a door named “Sales” is leaving an Area called “Lobby” and entering an Area called “Sales
Office.”
Door Tasks
You can perform the following general tasks to configure iSTAR and apC Doors.
■ Creating a Door on Page 379
■ Creating a Door Template on Page 380
■ Deleting a Door on Page 381
■ Modifying a Door on Page 381
■ Viewing a List of Doors on Page 381
■ Using Set Property to Configure Doors on Page 382
■ Add a Hardware Device to Group from a Dynamic View on Page 383
Creating a Door
A door object must be configured for the type of controller to which it is connected: iSTAR or apC controllers. The process
is essentially the same when creating each door object type. First you must create the controller, then configure the
controller’s General tab and Board tab to configure inputs, outputs and readers. One exception is that with the iSTAR
controllers, you are required to first create an iSTAR cluster and then create controllers within that cluster.
Once you have created and configured the door controller, you may create as many doors as that type of controller can
accommodate.
To Create a Door
Follow the steps below to create a door for an apC controller. To create an iSTAR door, first refer to the next set of steps
for reader the iSTAR Cluster and Controller before reader the iSTAR door.
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. In the Hardware tree, expand the facility folder where you want to create a door. You must create a door by highlighting
a controller icon, board icon, or door icon in the hardware tree:
• apC - highlight the apC controller icon, right click, and select apC Door > New.
• iSTAR - highlight the iSTAR controller icon, right click, and select iSTAR Door > New.
You can also create a new door from the door icon in a folder: highlight the door icon, right click, and select Door >
New. A new Door Dialog box opens. When the Door Dialog box opens on the General tab, configure the Door.
3. Enter a Name and Description.
4. Maintenance Mode - Click to put the door into Maintenance Mode. See Chapter 3: Maintenance Mode for more
information.
5. Configure the fields on the General tab, as needed. The fields listed below are on the apC and iSTAR Door dialog
boxes.
• Controller - This is a read-only field that indicates the controller associated with the door.
• Door Switch Monitor - Click to display a list of inputs available for the controller. This signal is true when the
door is open. It is used to determine Admit Unused, Door Held, and Door Forced. Click an Input to select it and
assign it to the Door Switch Monitor field.
• Door Lock Relay - Click to display a list of outputs available for the controller. T his output is used to open the
door. Click an Output to select it and assign it to the Door Lock Relay field.
• Alternate Shunt Relay - Click to display a list of outputs available for the controller. Alternate Shunt is used
for cardholders with disability and sometimes for aircraft loading doors. Click an Output to select it and assign it to
the Alternate Shunt Relay field .
• Shunt Expiration Relay - Click to display a list of outputs available for the controller. This output will indicate
the expiration of the shunt. Click an Output to select it and assign it to the Shunt Expiration Relay field.
• Inbound Reader - Click to display a list of Readers available. Inbound and Outbound Readers are required for
Area related functions such as Occupancy and Anti-Passback Click a Reader to select it and assign it to the
Inbound Reader field.
• Outbound Reader - Click to display a list of Readers available. Inbound and Oubound Readers are required
for Area related functions such as Occupancy and Anti-Passback Click a Reader to select it and assign it to the
Outbound Reader field.
• Readers are continuously active - Click this check box to enable continuous reader activity. Continuously Active
is not normally used. It is typically used for subway gates and other high volume applications.
• Request to Exit Input - Click to display a list of Inputs available. Click an Input to select it and assign it to the
field.
• Unlock Door on RTE - Click this check box to unlock the door at a Request to Exit. This is usually checked, but
certain high security areas may use the REX as a signal to the Security Officer who verifies the person and opens
the door.
• Shunt DSM while RTE is active - Click this check box to Shunt Door Switch Monitor While Request to Exit is
Active. This is frequently used to correct a race condition between REX and DSM.
6. To save your new Door, click Save and Close.
To save the Door and create a new one, click Save and New. The current Door is saved and closed, but the Door
Editor remains open to allow you to create a new Door.
The following controller creation provides a sample of the steps involved in the creation of an iSTAR Cluster and
Controller. For more detailed information about the creation of iSTAR Clusters, refer to Configuring iSTAR Clusters on
Page 91. For more detailed information about the creation of controllers, refer to:
■ Creating an iSTAR Controller on Page 127
■ Configuration Overview for iSTAR Controllers on Page 121
■ apC Panel Overview on Page 308.
The new Door template appears in the Template drop down list under Templates.
Deleting a Door
You can delete a Door from a controller.
To Delete a Door
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Select either an apC or iSTAR Door from the Hardware pane drop-down list.
3. Click to open a Dynamic View showing Door objects of the same type.
4. Right-click the Door in the list that you want to delete and select Delete from the context menu.
5. Click Yes on the “Are you sure you want to delete the selected Door?” message box.
Modifying a Door
You can edit a Door.
To Edit a Door
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Select either an apC or iSTAR Door from the Hardware pane drop-down list.
3. Click to open a Dynamic View showing Door objects of the same type.
4. Double-click the Door in the list that you want to modify, and the Door Editor opens. Or, you can select the door in
the list, right click, and select Edit from the context menu.
In the Dynamic View, you can right-click the column header and select new columns from the list to add
NOTE them to the Dynamic View. (For iSTAR Doors you can add a column that identifies the Intrusion Zone to
which the Doors belong.)
If you right-click a row in the Door Dynamic View, a context menu is displayed. This menu contains a number of standard
selections, as well as selections that are specific for Doors.
See Using the Object List Context Menu in the C•CURE 9000 Getting Started Guide for more information about the
object context menu.
See Table 118 on Page 382 for context menu selections that are specific to Doors.
There are additional context menu selections for Advanced Door monitoring. See Advanced Door Monitoring Details on
Page 459 for more information.
Table 118: Doors Context Menu Selections
Selection Description
Lock Opens a Manual action dialog box that lets you lock the selected Door.
Unlock Opens a Manual action dialog box that lets you unlock the selected Door.
Momentary Opens a Manual action dialog box that lets you momentarily unlock the selected Door.
Unlock
Door Opens the Doors Monitoring Screen for the Door you selected.
Monitoring See Door Monitoring Screen on Page 461 for information about the Doors Monitoring screen.
Show Click this menu selection to view a list of Security Objects associated with this iSTAR or apC Door. For more information, see
Association "Showing Associations for an Object" in the C•CURE 9000 Getting Started Guide.
Monitor Click this menu selection to view activity for the selected iSTAR and apC Door(s), and any Input, Output, Reader, and Trigger-
with-target-Event children, on an Admin Monitor Activity Viewer.
For more information, see "Monitoring an Object from the Administration Station" in the C•CURE 9000 Getting Started Guide.
Example:
If you wanted to change an unlock property setting for 20 apC Doors, you could select all of them listed in the dynamic
list and do it in one step.
The apC and apC/L controllers have not been evaluated by UL.
NOTE
5. Configure the door on the General tab and any other tabs, as needed. You will need to have already configured the
apC Readers, Inputs, and Outputs to fully configure an apC door.
6. Configure remaining tabs for this door, or click Save and Close. The new door displays under the Doors directory in
the Hardware tree.
The following section documents the tasks required to configure a basic Door object for apC panel access control. The
Door Reader buttons and entry fields on the Door General tab, shown in Figure 114 on Page 386, allow you to specify the
card readers associated with this Door, and to configure door-specific settings for these readers.
3. Click for the Door Lock Relay. When you click this button to select an output to assign to the Door Lock Relay,
a browser opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the
entry field.
4. Click for the Alternate Shunt Relay. When you click this button to select an output to assign to the Alternate
Shunt Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it and
add it to the entry field.
5. Click for the Shunt Expiration Relay. When you click this button to select an output to assign to the Shunt
Expiration Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it
and add it to the entry field.
6. Click for the Request to Exit Input. When you click this button to select an input to assign to the Request to
Exit, a browser opens presenting a list of inputs available for the controller. Click an RTE Input to select it and add it
to the entry field.
7. Select the Unlock Door on RTE check box to unlock the door at a Request to Exit.
8. Select the Shunt DSM While RTE is Active check box to Shunt Door Switch Monitor While Request to Exit is
Active.
9. Navigate to the Readers tab, or click Save and Close to return to the Hardware pane.
The Readers tab also lets you configure doors as "ordinary" or turnstile for escorted access for visitors by selecting the
Readers Are Continuously Active check box.
card is entering the area in the Must Activate Within entry field. The range for this field is from 0 to 99.99 seconds in
units of 0.1 seconds.
If the input changes state within the specified time, the panel determines that the card is moving into the inbound area.
6. Click to select an input for the apC Bi-directional Reader in the Activation of the Input Determines Outbound
Movement entry field. When you click this button to select an input to assign to the outbound input, a browser opens
presenting a list of inputs available for the panel. Click an Input to select it and add it to the entry field.
The selected input tests for outbound movement at the apC controlled door. When this input activates within the
directional link time, the system determines that the card is moving in the outbound direction. The apC uses this
information for access control.
The outbound input must be on the same apC as the bi-directional readers on this door.
7. If the door has an outbound input defined in the Activation of This Input Determines Outbound Movement field,
enter the time in tenths of seconds that the panel waits between card reads and input state changes to determine that
the card is entering the area in the Must Activate Within entry field. The range for this field is from 0 to 99.99 seconds
in units of 0.1 seconds.
If the input changes state within the specified time, the panel determines that the card is moving into the outbound
area.
8. Navigate to the Timing tab, or click Save and Close to return to the Hardware pane.
7. Door Open Grace Time – Also known as Door Open Debounce Time. Setting this value to 0 indicates that there is
no timer; as soon as the door opens, door forced open is reported. The range for this field is from 0 to 25.5 seconds in
units of 0.1 seconds.
8. Navigate to the Triggers tab, or click Save and Close to return to the Hardware pane.
You can click Save and Close after configuring apC Door triggers, or navigate to the Status tab.
To Change an Image
1. Double-click the existing image.
A Windows Open dialog box appears allowing you to browse for a folder in which you have placed replacement
images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click the new image and select Restore Default.
4. Click Save and Close to return to the Hardware pane.
For more information about Check-in and Check-out of a Visitor via Visitor Management, and access requests via Access
Management and the C•CURE Portal, see the C•CURE 9000 Visitor and Access Management Guide.
This presumes that a Badge Return mechanism is set up at the Check-out reader.
1. In the C•CURE 9000 Admin Client, navigate to the Door you wish to configure.
Field/Button Description
Name Use the Identification box to enter a name (up to 50 characters long) and brief description of the door you are configuring.
Maintenance Click to put the apC door into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Partition The Partition label indicates to which partition the door belongs.
Hardware
Door Switch Click for the Door Switch Monitor. When you click this button to select inputs to assign to the Door Switch Monitor, a
Monitor browser opens presenting a list of inputs available for the controller. Click a Switch or other pre-configured Input to select it and
add it to the entry field.
Door Lock Click for the Door Lock Relay. When you click this button to select an output to assign to the Door Lock Relay, a browser
Relay opens presenting a list of outputs available for the controller. Click a Lock or other pre-configured Output to select it and add it
to the entry field.
Alternate Click for the Alternate Shunt Relay. When you click this button to select an input to assign to the Alternate Shunt Relay,
Shunt Relay a browser opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the entry field.
Shunt Click for the Shunt Expiration Relay. When you click this button to select an output to assign to the Shunt Expiration
Expiration Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the entry
Relay field.
Request to Exit
Request to Click for the Request to Exit Input. When you click this button to select an input to assign to the Request to Exit Input,
Exit Input a browser opens presenting a list of inputs available for the controller. Click an Input to select it and add it to the entry field.
Unlock Door Select the Unlock Door on RTE check box to unlock the door at a Request to Exit.
on RTE
Shunt DSM Select the Shunt DSM While RTE is Active check box to Shunt Door Switch Monitor While Request to Exit is Active.
while RTE is
active
Field/Button Description
Access Readers
Field/Button Description
Inbound Access When you click to select an Inbound Access Reader, a browser opens presenting a list of readers available for the panel.
Reader Click a Reader to select it and add it to the entry field.
Outbound When you click to select an Outbound Access Reader, a browser opens presenting a list of readers available for the
Access Reader panel. Click a Reader to select it and add it to the entry field.
Readers are Select the Readers Are Continuously Active check box if you want readers to read and process cards even when the
Continuously doors associated with them are unlocked or open because of another card access request.
Active
Bi-directional Readers
Activation of the Click to select an input for the apC Bi-directional Reader in the Activation of the Input Determines Inbound Movement
Input entry field. When you click this button to select an input to assign to the inbound input, a browser opens presenting a list of
Determines inputs available for the panel. Click an Input to select it and add it to the entry field.
Inbound
The selected input tests for inbound movement at the apC controlled door. When this input activates within the directional link
Movement
time, the system determines that the card is moving in the inbound direction. The apC panel uses this information for access
control decisions.
The inbound input must be on the same apC as the bi-directional readers on this door.
Must Activate If the door has an inbound input defined in the Activation of This Input Determines Inbound Movement field, enter the time in
Within tenths of seconds that the panel waits between card reads and input state changes to determine that the card is entering the
area in the Must Activate Within entry field. The range for this field is from 0 to 99.99 seconds in units of 0.1 seconds.
If the input changes state within the specified time, the panel determines that the card is moving into the inbound area.
Activation of the Click to select an input for the apC Bi-directional Reader in the Activation of the Input Determines Outbound Movement
Input entry field. When you click this button to select an input to assign to the outbound input, a browser opens presenting a list of
Determines inputs available for the panel. Click an Input to select it and add it to the entry field.
Outbound
The selected input tests for outbound movement at the apC controlled door. When this input activates within the directional link
Movement
time, the system determines that the card is moving in the outbound direction. The apC uses this information for access control.
The outbound input must be on the same apC as the bi-directional readers on this door.
Must Activate If the door has an outbound input defined in the Activation of This Input Determines Outbound Movement field, enter
Within the time in tenths of seconds that the panel waits between card reads and input state changes to determine that the card is
entering the area in the Must Activate Within entry field. The range for this field is from 0 to 99.99 seconds in units of 0.1
seconds.
If the input changes state within the specified time, the panel determines that the card is moving into the outbound area.
Field/Button Description
Timers
Field/Button Description
Delay Relock Type the number of seconds to delay door relock after the door is opened (after a request to exit, for example). The range in
seconds is 0:0:0 to 0:16:39 (999 seconds); the default is 0:0:0.
Shunt Time Shunt Time – type the number of seconds that the door can remain open before a door held open alert is generated within the
range of 0:0:0 to 0:16:39 (999 seconds); the default is 0:0:10 (10 seconds).
Unlock Time Unlock Time – type the number of seconds the Door remains unlocked after a valid card swipe, RTE activation, or momentary
unlock within the range of 0:0:0 to 0:4:15 (255 seconds); the default is 0:0:5 (5 seconds).
Alternate Alternate Shunt Time – type the number of hours, minutes, and seconds the Door can remain open before a door held open
Shunt Time alert is generated after a valid card swipe by a cardholder with the Alternate Shunt flag set in their personnel record (This value
is used only if it is set to a greater time than the Shunt time value) within the range of default/minimum: 0:0:0; maximum:18:0:0
(18 hours).
Shunt If set, the Shunt expiration relay fires regardless of the shunt time used. If set to 0 (the default), the Shunt expiration relay fires
Expiration only if the Alternate shunt time is used. The Shunt Expiration Warning has a range of 0:0:0 to 0:4:0 (4 minutes).
Warning Time
Door Close Specifies the time (in 1/10th of a second intervals) that the C•CURE 9000 ignores DSM inputs, to allow for bouncing doors.
Debounce Setting this value to 0 indicates that there is no timer. The range for this field is from 0 to 25.5 seconds in units of 0.1 seconds.
Time
Door Open Specifies the time (in 1/10th of a second intervals) that the C•CURE 9000 waits for an RTE, card admit, or momentary unlock
Grace Time signal after receiving the signal from the DSM. Setting this value to 0 indicates that there is no timer; as soon as the door opens,
door forced open is reported. The range for this field is from 0 to 25.5 seconds in units of 0.1 seconds.
Field/Button Description
Triggers
Remove
Click the row selector , then click Remove to delete a trigger.
Property Click within the Property column to display , When you select this button, the Property browser opens presenting
properties available for the controller. Click a Property to select it and add it to the column.
Value Click within the Value column to display a drop-down list of Values associated with the Property that you have selected. Click on
a Value that you want to include as a parameter for the trigger to add it to the column.
Field/Button Description
Action Click within the Action column to display a drop-down list of valid actions. Click on an Action that you want to include as a
parameter for the trigger to add it to the column.
When a Trigger is added, an Action must be configured in the Action column. This is the Action that will occur when the object’s
selected Property receives the selected Value. As the Action is selected, the lower pane in the Triggers box will show a
corresponding entry field, or group of entry fields, specific to the selected Action. Click to select entries for these fields. Once
the field (or group of fields) is completed, the Details column will show information about how the Action has been configured.
Details Displays details concerning the security objects that are associated with the selected Action.
Schedule Click within the Schedule column to display a drop-down list of pre-configured schedules. Click to select a Schedule that
you want to associate with the trigger. Schedules are created in the Configuration Pane. See the C•CURE 9000 Software
Configuration Guide for more information.
Property Description
Admit Status For any one of the Admit Status values (see the Value column list) you can choose one of the following Actions to create a
Values are: Trigger:
AdmitReject Activate Event – When this status occurs and the Schedule is Active (you can choose any Schedule).
Duress Activate Event Outside Schedule – An event is activated when this status occurs while the Schedule is Inactive (choose any
Schedule).
Noticed
Admit Activate Output – When this status occurs (only works with the Always Schedule).
Noticed Only these three Actions are supported for Admit Status.
Reject
Alarm 1. Choose a value for the Property from the Values column.
StateStatus 2. Select an Action from the Action drop-down list:
Values are: Activate Event - Select an Event to activate when this status occurs.
Forced Activate Event Outside Schedule - Select an Event to activate when this status occurs while the Schedule is inactive.
Held Open Activate Output - Select an Output to activate when this status occurs. Must use the Always Schedule.
3. Select a Schedule by clicking in the Schedule column, then click to select the Schedule that you want to associate with
the trigger.
For example, if you chose Forced as an Alarm State Status for which you want to define an action, you could then select
Activate Event. In Details, select the Event you want to activate. Then select a Schedule to determine during what time
periods you want the Forced Alarm State Status to activate an Event.
Field/Button Description
Groups
For more information about the use of the Toolbar buttons, see Chapter 2, “Dynamic Views” in the C•CURE 9000
Data Views Guide
Name This column displays the name entered for the group when it was configured. The selected door is a member of any
group(s) listed in this column.
Description This column displays the description entered for the group when it was configured.
Field/Button Description
Alarm Status Displays the values Normal, Forced, Held Open, or Unknown.
Admit Status Displays the values Admit, Reject Admit, Duress, Admit Visitor, Reject Visitor, Request To Exit, Reject No Escort, Reject No PIN,
Reject Not Time, Reject Unknown, Reject Unknown PIN, or Reject Duress.
Unknown Locked
Forced Unlocked
If the first Input, Output, or Reader you assign is a Shlage Wireless I/O component, a message box
NOTE appears asking if you wish to auto-fill the remaining objects for the door. If you click Yes the remaining
objects are selected automatically. This option only appears if all of the options are blank when you assign
the first object. See iSTAR PIM-485 Reader I/O Tab on Page 513 for information about Schlage Wireless
Reader I/O components.
An iSTAR Aperio Door does not have the following tabs: Areas & Zones, Double Swipe, and Door
NOTE Monitoring. Also, for Aperio Doors, some of the General tab settings are unavailable because these Inputs
and Outputs are integral to the reader and not user-selectable.
The Controller that you have chosen to operate the door is listed in the Controller read-only field.
2. Click for the Door Switch Monitor. When you click this button to select an input to assign to the Door Switch
Monitor, a browser opens presenting a list of inputs available for the controller. Click an Input to select it and add it to
the entry field (see Figure 115 on Page 398).
3. Click for the Door Lock Relay. When you click this button to select an input to assign to the Door Lock Relay, a
browser opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the
entry field.
4. Click for the Alternate Shunt Relay. When you click this button to select an input to assign to the Alternate
Shunt Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it and
add it to the entry field.
5. Click for the Shunt Expiration Relay. When you click this button to select an output to assign to the Shunt
Expiration Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it
and add it to the entry field.
6. Click to select a reader for the Inbound Reader. A selection dialog box opens presenting a list of readers
available for the controller. Click a reader to select it and addit to the entry field.
7. Click to select a reader for the Outbound Reader. A selection dialog box opens presenting a list of readers
available for the controller. Click a reader to select it and add it to the entry field.
The Secondary Inbound Reader and Secondary Outbound Reader fields only allow BLE
NOTE readers. These fields are only available for online doors and if the primary readers are
configured.
8. Click to select a reader for the Secondary Inbound Reader. A selection dialog box opens presenting a list of
readers available for the controller. Click a reader to select it and add it to the entry field.
9. Click to select a reader for the Secondary Outbound Reader. A selection dialog box opens presenting a list of
readers available for the controller. Click a reader to select it and add it to the entry field.
10. Select the Readers are Continuously Active check box to enable continuous reader activity, enabling readers to
read and process cards even when the doors associated with them are unlocked or open because of another card
access request. This mode is typically used for turnstiles or other high traffic situations that would result in
unacceptable delays if the reader went through its normal sequence of read-open-close for each cardholder.
Example:
Suppose a user swipes their card and unlocks a door. Before the door opens and closes, another person swipes his
card. If this box is checked, the system treats the second swipe as an access request. If you leave this box cleared,
the system ignores the second swipe. This feature is useful at high volume doors where you don’t want to wait for the
door to close after every access.
• "Ordinary" doors — multiple person access on each access cycle — select the Readers Are Continuously
Active check box.
• "Turnstiles" (or Mantraps) — one person access only on each access cycle — clear the Readers Are
Continuously Active check box.
Selecting this option for a Reader on an iSTAR Area Door permits the Area to be configured for Escorted Access in
Companion mode. Leaving this option unselected causes Escorted Access to operate in Remote Escort (or Turnstile)
mode.
11. Click for the Request to Exit Input. When you click this button to select an input to assign to the Request to
Exit, a browser opens presenting a list of inputs available for the controller. Click an Input to select it and add it to the
entry field.
12. Select the Unlock Door on RTE check box to unlock the door at a Request to Exit.
13. Select the Shunt DSM While RTE is Active check box to Shunt Door Switch Monitor While Request to Exit is
Active.
14. Select the Send non-alarms input status to the host check box to instruct the system to send non-alarm input
status to the host.
Leaving the checkbox unselected (the default setting) instructs the system not to send non-alarm input status to the
host. Doing this reduces network traffic demand when expecting large volumes of non-critical activity notifications.
15. Select the Requires Manual Action Instructions check box to prompt the user to enter instructions whenever a
momentary unlock manual action is performed. The instructions must be entered before a momentary unlock manual
action can be performed. The information entered in the Instruction dialog box is displayed in the journal in the
Message Text column.
16. Select the Enable Random Screening check box to activate the Random Screening feature, which rejects a
selected percentage of card access requests.
Example:
An airport has a security entrance that passengers must go through before boarding. A selected percentage of access
requests from individuals are denied for subsequent random screening. When their access request is rejected, an
event is activated. This event can be associated with an output, such as a light or buzzer which notifies the guard or
operator for further action. This feature is useful at high volume access points where random screening of personnel is
required.
To configure the Percent field, increase or decrease the percentage of card swipes randomly screened. Click to
associate this feature with an event. When you click this button selecting an event to associate with Random
Screening, a browser opens presenting a list of configured events. Select an event and add it to the field.
Random Screening is supported on the iSTAR Ultra and Ultra SE (in Ultra Mode) with firmware version
NOTE 6.5 or later.
The following timers and check boxes appear on the iSTAR Door Timing tab:
1. Delay Relock – Type the number of seconds to delay door relock after the door is opened (after a request to exit, for
example). The range in seconds is 0 to 999 seconds (0:16:39); the default is 0.
2. Shunt Time – Type the number of seconds that the door can remain open before a door held open alert is generated
within the range of 00.00.00 to 2:46:00 (2 hours and forty-six minutes), the default is 00.00.00.
3. Unlock Time – Type the number of seconds the Door remains unlocked after a valid card swipe, RTE activation, or
momentary unlock within the range of 0 to 255 seconds (0:4:15); the default is 5seconds.
A value of 0 actually represents a token unlock time (300 microseconds) that can be used, for example, to
NOTE unlock a turnstile so that one person may pass, but tailgating is not possible.
Also, a setting of 0 disables Momentary Unlock manual actions, so choose a non-zero Unlock Time if you
need to use Momentary Unlock with this Door.
4. Alternate Shunt Time – Type the number of hours, minutes, and seconds the Door can remain open before a door
held open alert is generated after a valid card swipe by a cardholder with the Alternate Shunt flag set in their
personnel record (see the C•CURE 9000 Personnel Configuration Guide) within the range of default/minimum:
00:00:00; maximum: 18:00:00 (18 hours). This value is used only if it is set to a greater time than the Shunt time
value.
5. Shunt Expiration Warning Time – If set, the Shunt expiration relay is fired regardless of the shunt time used. If set
to 0 (the default), the Shunt expiration relay will only be fired if the Alternate shunt time was used. The Shunt Expiration
Warning has a range of 0:0 to 15:0 (15 minutes).
6. Door Close Debounce Time - Setting this value to 0 indicates that there is no timer. The range is from 0 to 25.5
seconds in units of 0.1 seconds.
7. Door Open Grace Time – Also known as Door Open Debounce Time. Setting this value to 0 indicates that there is
no timer; as soon as the door opens, door forced open is reported. The range is from 0 to 25.5 seconds in units of 0.1
seconds.
8. Door Unlock Grace Time – Specifies the time that the system waits for a door open signal after the door unlock time
has expired. This timing prevents a false door forced message in situations where signals are nearly simultaneous.
The range is from 0 to 100 seconds in units of 0.1 seconds.
9. Always Use Shunt Expire Output – If this check box is selected, the Shunt expiration relay is fired regardless of the
shunt time used. If the Shunt Expiration Warning Time is set to 0 (the default), the Shunt expiration relay shall only
be fired if the Alternate shunt time was used.
10. Delay Relock While Door Open After Valid Access - If access is valid, delays the relock of the door until the door
closes, if this check box is selected. This differs from standard relock operations, where relock occurs when the door
opens and the relock delay expires. If the door is open, the lock is energized. The C•CURE 9000 system sends an
alarm when the shunt time expires.
11. Shunt Door for full Shunt Time - If this check box is selected, the door is shunted for the full shunt time. If selected
with Delay relock while door open for valid access, the lock is energized and the door unlocked for the full shunt time,
regardless of whether the door is open or closed.
If the Door is not assigned to either an iSTAR Cluster Area or Intrusion Zone, the relevant box is blank.
The Dynamic View for iSTAR Doors allows you to add a column that identifies the Intrusion Zone to which
NOTE the Doors belong.
The Areas & Zones tab has the read-only fields shown in iSTAR Door Definitions on Page 411.
Toggle Mode configures a door to enable its reader to interpret a double card swipe as a means to toggle the door’s lock
state until a subsequent double swipe resets the lock state. For example, this can be used when a guard double swipes
their card to unlock the common area door at the beginning of the day and then double swipes at the end of the day to lock
the common area door.
Two Person Mode for iSTAR Ultra hardware requires the swipe of two personnel with clearance before they can unlock a
door. This mode can be configured to require personnel card swipes from two different Personnel Groups to allow entry.
For instance, if an employee requires entrance into a restricted area, the door requires the swipe of the employee and a
supervisor to allow entry.
• If the door being configured is assigned a Schlage Wireless Reader, the contents of this tab are disabled because the Schlage
NOTE readers do not support this feature.
• Do not configure Toggle mode or Two Person mode on a Door that is used with Antipassback, Escort, Conditional Access,
Areas, Area Counting, or Intrusion Zone functionality.
• Toggle Mode requires iSTAR firmware version 4.3 or later for Classic, Pro, or eX.
• Two Person Mode requires version 6.5 or later for Ultra.
• The iSTAR Ultra SE does not support Two Person Mode while configured in Pro mode.
• Aperio doors do not support Two Person Mode.
• A Double Swipe to Lock or Unlock a door also may be configured to trigger an Event. This is configured on the Triggers tab (see
Using Double Swipe to Trigger an Event on Page 407).
Field Description
None If None is selected, Double Swipe is not enabled at the door. If Double Swipe is active at the door, you
may turn off Double Swipe by selecting None on this tab. Normal card swipe access at the reader is still in
effect, if so configured. This is the default setting.
Toggle Mode Selecting this option enables the Double Swipe feature. This is configured in the Permission to
cardholders section.
Two Person This option enables entry to a door only when personnel from the selected Personnel Groups both swipe
their cards. This feature is only available for the Ultra with firmware version 6.5 or later.
Permission to cardholders
With clearance Selecting this option enables the door to require that cardholders who use Double Swipe at the reader
must have a clearance for access to this particular door configured for them in the Personnel screen,
Clearances tab.
With clearance and in personnel Selecting this option will require that cardholders who use Toggle mode or Two Person mode at the
group(s) reader must have a clearance for access to this door configured for them in the Personnel screen,
Clearances tab, and they also must be in the personnel group whose members have access to this
door.
Personnel Group Click to select a personnel group. If a group is selected for Double Swipe, each cardholder who
uses Double Swipe at the reader must be a member of the selected Personnel Group. The personnel
group may be configured in the Configuration pane, Group dialog box. If selecting groups for Two
Person mode, ensure two groups are selected.
Options
NOTE: The Options section is not available when configuring the Double Swipe tab if configuring Two Person mode.
Priority (0 - 200) Select a Priority for Double Swipe requests at the door. The default is 75.
In the case of a manual action with higher priority than the priority configured for the door, the manual
action takes precedence. If the door’s priority is higher, the double swipe takes precedence. For two
actions with the same priority, the most recent one takes precedence.
NOTE: If you change the Priority setting on the Double Swipe tab while a double swipe cause is active
for the door, that cause will be removed from the cause list, and any the double swipe action is canceled.
Double Swipe Cancellation Click to select a schedule. The cancelling schedule will delete any existing double swipe causes on
Schedule the door at the start of the schedule. Any double swipe actions currently in effect will be canceled.
Follow the steps to access the door editor in the Admin application, as described in Creating a Door on Page 379.
1. In the Door editor, select the Double Swipe tab and then select the Toggle Mode radio button.
2. In the Permission to cardholders section, select either With clearance or With clearance and in personnel
group(s) radio button. If selecting With clearance and in personnel group(s), click to select a personnel group.
3. If required, select a priority setting in the Options section. In the case of a manual action with higher priority than the
priority configured for the door, the manual action takes precedence. If the door’s priority is higher, the double swipe
takes precedence. For two actions with the same priority, the most recent one takes precedence.
4. Click to select a Double Swipe Cancellation Schedule.
For the Monitoring Station’s Activity Viewer to display Double Swipe lock/unlock messages, the Application Layout must
have an Activity Viewer pane configured to display Double Swipe messages. The Activity Viewer pane may be added, if
needed, as described below.
Follow the steps to access the door editor in the Admin application, as described in Creating a Door on Page 379.
1. In the Door editor, select the Double Swipe tab and then select the Two Person Mode radio button.
2. Select the With clearance or With clearance and in personnel group(s) radio button depending on configuration. If
selecting With clearance, the Personnel Groups section is unavailable.
3. In the Personnel Groups section, click to select personnel groups. If a group is selected, each cardholder who
uses this feature at the reader must be a member of the selected Personnel Group. The personnel group may be
configured in the Configuration pane, Group dialog box.
4. Save and close the door editor.
For the Monitoring Station’s Activity Viewer to display Double Swipe lock/unlock messages, the Application Layout must
have an Activity Viewer pane configured to display Double Swipe messages. The Activity Viewer pane may be added, if
needed, as described below.
a. Select the Double Swipe check box to display Double Swipe messages at the Monitoring Station. If the box is clear,
messages will not display at the Monitoring Station. By default, the Activity Viewer displays all these Message
Types.
b. Click Save and Close .
- or -
n the cardholder(s) having a clearance to the specific door and being a member of the personnel group, if the “With
clearance and in personnel group” option is selected on the Double Swipe tab.
The following steps describe how a double swipe at the card reader toggles the door lock, to lock or unlock the door.
Cardholder swipes the card twice at the reader, within the shunt time.
If the cardholder has the correct clearance set for access to the door or has the correct clearance and is in the correct
personnel group, the door toggles to Unlock. The card reader displays the state of the door, and the door remains
unlocked until it is locked again by another double swipe, or by other causes such as manual action, scheduled
events, and so forth.
If the cardholder swipes only once, a Momentary Unlock occurs for an authorized cardholder.
Cardholder swipes the card twice at the reader, within the shunt time.
If the cardholder has the correct clearance set for access to the door or has the correct clearance and is in the correct
personnel group, the door toggles to Lock. The card reader displays the state of the door, and the door remains locked
until it is unlocked by another double swipe, or by other causes such as manual action, scheduled events, and so forth.
For continuous card reader activity, make sure that the Readers are Continuously Active check box is selected in the
Readers section of the General tab.
To associate Double Swipe with a trigger to cause an event, refer to Using Double Swipe to Trigger an Event on Page 407.
This tab is available on the iSTAR Doors Editor only if the Include Personnel Without Clearance in Personnel
Downloads option in the Conditional Access box is selected on the General tab of the door's iSTAR controller editor.
The Conditional Access process can only be started by Personnel Credentials rejected for having no
NOTE Clearance at the door. Rejections for Lost, Stolen, Not Active, Expired, or Unknown Card or for
Antipassback, Occupancy, Lockout, or PIN cause immediate rejection.
This feature is usually used on doors into iSTAR Areas where a person inside can grant entry to the Area to personnel
lacking clearance, after validating their identities. (In the latter situation, it can also be used in conjunction with Dynamic
Area Manager. See the Areas chapter in the C•CURE 9000 Areas and Zones Guide.)
Example:
A bank has a secure area that it uses for counting cash. Two authorized employees with clearance for the entry door
(Susan and Tom) have already entered the room and are working. A third employee without clearance (Martin) needs
to confer with them and swipes his card at the door. Since the door is configured for Conditional Access, a
Conditional Access event is activated and triggers an output inside the room, such as a flashing light or bell, to
announce that someone wants to enter. Through the glass pane in the door, Susan sees that it is Martin waiting
there. She pushes the button on the wall, activating a 'Conditional Access Response' event whose action opens the
door. Martin enters the room. (The iSTAR Area Status tab would show that there were currently a total of three
people in the area and that one of them had been admitted conditionally.)
The iSTAR Area Status tab keeps track of the number of Personnel currently in the area who were admitted via
Conditional Access. See the Areas chapter in the C•CURE 9000 Areas and Zones Guide. The iSTAR Door Status tab
indicates whether or not Conditional Access is configured for an iSTAR door. See iSTAR Door Status Tab on Page 408.
This feature could also be used on any door to allow a guard at a Monitoring Station, with video capability to validate a
person's identity, to activate the 'Conditional Access Response' event and let that person through the door.
■ Conditional Access is only supported on doors on iSTAR Pro, eX, Edge, and Ultra Controllers.
NOTE
■ The controller must also have the Include Personnel Without Clearance in Personnel Downloads
option in the Conditional Access box selected on the General tab. (Normally credentials for personnel
without clearance for any doors on the controller are not downloaded to the controller.)
■ Conditional Access should not be configured on a door that is used with Escort or Double Swipe
functionality.
See iSTAR Door Conditional Access Tab Definitions on Page 414 for definitions of the fields on the Conditional Access
tab.
a buzzer or flashing light, that notifies appropriate personnel that someone without the requisite clearance wants to
go through this door.
b. Configure a host or panel event with the action Allow Conditional Access Cycle to be activated to open the door
conditionally.
For information, see the Events Chapter in the C•CURE 9000 Software Configuration Guide.
4. Follow the steps to access the iSTAR Door editor in the Administration application, as described in Creating a Door on
Page 379, and then open the Conditional Access tab.
5. Click for Conditional Access Schedule to select the schedule during which Conditional Access is enabled for
this door.
6. Click for Conditional Access Event to select the event that requests Conditional Access at this door for a
person without Clearance. (Only panel events within this controller's cluster are available for selection.)
7. In the Conditional Access Response Time field, enter the number of seconds that the door will wait for the 'Allow
Conditional Access Cycle' event action to open the door after the Conditional Access event entered in the preceding
field has been activated. (The range is 1 - 150 seconds with a default of 10 seconds.)
8. Click Save and Close to save the settings and close the window, or click Save and New to save the settings and
configure a new door.
Selecting the Reject Limit Reached property requires setting the System Variables iSTAR Driver
NOTE "Number of Consecutive Rejects Cause Event" and "Reader Consecutive Rejects Timer". Otherwise, the
default values of 0 is used. See the C•CURE 9000 System Maintenance Guide or "Consecutive Rejects
Activate an Event" on page 464 for more information.
4. Click in the Value column to display the list of Values associated with the Double Swipe Property. Select either
Locked or Unlocked as the value for the trigger and add it to the column. Do not select “Unknown” as a value because
it is not a valid option and would be ignored.
5. Click in the Action column to display a drop-down list of actions. Select Activate Event as the action for the trigger
and add it to the column. The other actions in the list are not valid for the double swipe trigger and will be ignored. The
lower pane on the Triggers tab will display an event entry field that is specific to the selected Action.
For the combination of Double Swipe Property and Locked or Unlocked Value, Activate Event is currently the only
action supported.
6. In the Event field, click to display a list of pre-configured Events. Click on an event in the list to add it to the field.
This Event will occur when the conditions of the trigger are met.
Events may be created from the Configuration pane and “Event” in the drop-down menu on the Administration
application. See the C•CURE 9000 Software Configuration Guide for more information.
7. Click in the Schedule column, then click to select a Schedule to associate with the trigger. Notice that when you
click in the Schedule column, the details of the Event you selected display in the Details column. If the event has no
description entered, the Details cell will remain empty.
Schedules may be created from the Configuration pane and “Schedule” in the drop-down menu on the Administration
application.
8. Navigate to another tab or click Save and Close to save the trigger, or click Save and New to open a new door
editor.
See Advanced Door Monitoring Definitions on Page 425 for definitions of the fields on the Door Monitoring tab.
To Change an Image
1. Double-click the existing image.
A Windows Open dialog box appears allowing you to browse for a folder in which you have placed replacement
images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click the new image and select Restore Default.
4. Click Save and Close to return to the Hardware pane.
For more information about Check-in and Check-out of Visitor via Visitor Management, and Access Requests via Access
Management, see the C•CURE 9000 Visitor and Access Management Guide
Field/Button Description
Name Use the Identification box to enter a name (up to 100 characters long) and brief description of the door you are configuring.
Maintenance Click to put the iSTAR door into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Location
Controller This read-only field displays the iSTAR Controller that is connected to the Door.
Hardware
Door Switch Click for the Door Switch Monitor. When you click this button to select an input to assign to the Door Switch Monitor, a
Monitor browser opens presenting a list of inputs available for the controller. Click an Input to select it and add it to the entry field.
Door Lock Click for the Door Lock Relay. When you click this button to select an input to assign to the Door Lock Relay, a browser
Relay opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the entry field.
Alternate Click for the Alternate Shunt Relay. When you click this button to select an output to assign to the Alternate Shunt
Shunt Relay Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the entry
field. Timing for this output is set on the iSTAR Door Timing Tab on Page 400. Cardholders with the Alternate Shunt ADA setting
enabled on the Personnel General tab (See the C•CURE 9000 Personnel Configuration Guide) are granted the additional
Alternate Shunt time before a door held alarm is generated.
Shunt Click for the Shunt Expiration Relay. When you click this button to select an output to assign to the Shunt Expiration
Expiration Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the entry
Relay field.
Readers
Entrance Click for the Entrance Reader. When you click this button to select a reader to assign to the Entrance Reader, a browser
Reader opens presenting a list of readers available for the controller. Click a Reader to select it and add it to the entry field.
Exit Reader Click for the Exit Reader. When you click this button to select a reader to assign to the Exit Reader, a browser opens
presenting a list of readers available for the controller. Click a Reader to select it and add it to the entry field.
Readers are Select the Readers are Continuously Active check box to enable continuous reader activity.
Continuously Selecting this option for a Reader on an iSTAR Area Door permits the Area to be configured for Companion mode Escorted
Active Access. Leaving this option unselected causes Escorted Access to operate in Remote Escort (or Turnstile) mode.
Request to Exit
Request to Click for the Request to Exit. When you click this button to select an input to assign to the Request to Exit, a browser
Exit opens presenting a list of inputs available for the controller. Click an Input to select it and add it to the entry field.
Field/Button Description
Unlock Door Select the Unlock Door on RTE check box to unlock the door at a Request to Exit.
on RTE
Shunt DSM Select the Shunt DSM While RTE is Active check box to Shunt Door Switch Monitor While Request to Exit is Active.
While RTE is
Active
Field/Button Description
Timers
Delay Relock Type the number of seconds to delay door relock after the door is opened (after a request to exit, for example). The range in
seconds is 0:0:0 to 0:16:39 (999 seconds); the default is 0:0:0.
Shunt Time Shunt Time – type the number of seconds that the door can remain open before a door held open alert is generated within the
range of 0:0:0 to 2:46:00 (9999 seconds); the default is 0:0:10 (10 seconds).
Unlock Time Unlock Time – type the number of seconds the Door remains unlocked after a valid card swipe, RTE activation, or momentary
unlock within the range of 0:0:0 to 0:4:15 (255 seconds); the default is 0:0:5 (5 seconds).
Alternate Alternate Shunt Time – type the number of hours, minutes, and seconds the Door can remain open before a door held open
Shunt Time alert is generated after a valid card swipe by a cardholder with the Alternate Shunt flag set in their personnel record (This value
is used only if it is set to a greater time than the Shunt time value) within the range of default/minimum: 0:0:0; maximum:18:0:0
(18 hours).
Shunt If set, the Shunt expiration relay fires regardless of the shunt time used. If set to 0 (the default), the Shunt expiration relay fires
Expiration only if the Alternate shunt time is used. The Shunt Expiration Warning has a range of 0:0:0 to 0:15:0 (15 minutes).
Warning Time
Door Close Specifies the time (in 1/10th of a second intervals) that the C•CURE 9000 ignores DSM inputs, to allow for bouncing doors.
Debounce Setting this value to 0 indicates that there is no timer. The range is 0 - 25.5 seconds.
Time
Door Open Specifies the time (in 1/10th of a second intervals) that the C•CURE 9000 waits for an RTE, card admit, or momentary unlock
Grace Time signal after receiving the signal from the DSM. Setting this value to 0 indicates that there is no timer; as soon as the door opens,
door forced open is reported. The range is 0 - 25.5 seconds.
Door Unlock Specifies the time (in 1/10th of a second intervals) that the C•CURE 9000 waits for a door open signal after the door unlock time
Grace Time has expired. This timing prevents a false door forced message in situations where signals are nearly simultaneous. The range is
0 - 100 seconds.
Options
Always Use if this option is selected, the Shunt expiration relay is fired regardless of the shunt time used. If the Shunt Expiration Warning
Shunt Expire Time is set to 0 (the default), the Shunt expiration relay shall only be fired if the Alternate shunt time was used.
Output
Field/Button Description
Delay Relock If access is valid, delays the relock of the door until the door closes, if this check box is selected.
While Door This differs from standard relock operations, where relock occurs when the door opens and the relock delay expires
Open After
Valid Access If the door is open, the lock is energized. The C•CURE 9000 sends an alarm when the shunt time expires.
Shunt Door If this option is selected, the door is shunted for the full shunt time. If selected with Delay relock while door open for valid access,
for full Shunt the lock is energized and the door unlocked for the full shunt time, regardless of whether the door is open or closed.
Time
Box/Fields Description
Areas
Entry Area Name of Area to which this Door is an ‘Access In’ Door.
Exit Area Name of Area to which this Door is an ‘Access Out’ Door.
Intrusion Zones
Zone Direction I n indicates that this Door is assigned as an Entrance Door for the Intrusion Zone.
Out indicates that this Door is assigned as an Exit Door for the Intrusion Zone.
Display Name Displays the name you entered for this Door on the iSTAR Intrusion Zones Editor General tab.
Field/Button Description
Permission to Cardholders
None If this option is selected, Double Swipe is not enabled at the door. If Double Swipe is active at the door, you may turn off Double
Swipe by selecting None on this tab. Normal card swipe access at the reader is still in effect, if so configured.
With clearance Selecting this option will enable the door to require that a cardholder who uses Double Swipe also has Double Swipe clearance
configured for them in the Personnel screen, Clearances tab.
Field/Button Description
With clearance Selecting this option will require that a cardholder who uses Double Swipe at the reader have a Double Swipe clearance set
and in and also be in the personnel group that may be selected in the next fields
personnel
group
Personnel Click to select a personnel group whose members may be admitted on Double Swipe as long as each member has the
group proper clearance set for them in the Personnel screen, Clearances tab.
Options
Priority Select a priority (from 0 - 200) for Double Swipe requests at the door.
In the case of a manual action with higher priority than the priority configured for the door, the manual action takes precedence.
If the door’s priority is higher, the double swipe takes precedence. For two actions with the same priority, the most recent one
takes precedence.
Double Swipe Click to select a schedule. The cancelling schedule will delete any existing double swipe causes on the door at the start of
Cancellation the time spec. Any double swipe actions currently in effect will be cancelled.
Schedule
Field/Button Description
Conditional Access Click to select the schedule during which the door is 'Conditional Access-enabled'. This can be any schedule in the
Schedule same time zone as the controller.
The iSTAR Door Status tab will indicate whether Conditional Access is enabled or not.
Conditional Access Click to select the event that requests 'Conditional Access' at this door for a person without Clearance.
Event
Only panel events within this controller's cluster are available for selection. This event cannot be the same one that
targets this door with the 'Allow Conditional Access Cycle' action—lets the person through the door.
Conditional Access Specifies the time (in seconds) that the door waits for an 'Allow Conditional Access Cycle' event action in response to
Response Time the activation of the Conditional Access event. The range is 1 - 150 seconds with a default of 10 seconds.
NOTE: You can choose to display columns on the iSTAR Door Dynamic View that indicate for a given door:
• Whether or not Conditional Access is enabled.
• The selected Conditional Access schedule, event, and response (delay) time.
Field/Button Description
Triggers
Remove
Click the row selector , then click Remove to delete a trigger.
Property Click within the Property column to display , When you select this button, the Property browser opens presenting
properties available for the controller. Click a Property to select it and add it to the column.
Value Click within the Value column to display a drop-down list of Values associated with the Property that you have selected. Click on
a Value that you want to include as a parameter for the trigger to add it to the column.
Action Click within the Action column to display a drop-down list of valid actions. Click on an Action that you want to include as a
parameter for the trigger to add it to the column.
When a Trigger is added, an Action must be configured in the Action column. This is the Action that will occur when the object’s
selected Property receives the selected Value. As the Action is selected, the lower pane in the Triggers box will show a
corresponding entry field, or group of entry fields, specific to the selected Action. Click to select entries for these fields. Once
the field (or group of fields) is completed, the Details column will show information about how the Action has been configured.
Details Displays details concerning the security objects that are associated with the selected Action.
Schedule Click within the Schedule column, then click to select a Schedule that you want to associate with the trigger. Schedules
are created in the Configuration Pane. See the C•CURE 9000 Software Configuration Guide for more information.
Property Description
Admit Status For any one of the Admit Status, Mode Status, or Open Status values (see the Value column drop-down list) you
Admit can choose one of the following Actions to create a Trigger:
Admit Visitor Activate Event – When this status occurs and the Schedule is Active (you can choose any Schedule). You must set a
Minimum Activation Time in the Event or the actions in the Event will not activate.
Reject Visitor
Activate Event Outside Schedule – An event is activated when this status occurs while the Schedule is Inactive
Reject (choose any Schedule).
Duress Activate Output – Activate an Output when this status occurs (only works with the Always Schedule).
Noticed Admit
Noticed Reject Pre-Admit status is a special case used to activate a panel Event on a card swipe before the door is opened. It is used
Pre-Admit with the Activate Event action to activate an Event that can, for example, change the state of an output on the
iSTAR panel.
Mode Status
Unlocked
Locked
No Access
Momentary
Unlock
Open Status
Open
Closed
Double Swipe Status For any one of the Double-Swipe Status values (see the Value column drop-down list) you can choose one of the
Locked following Actions to create a Trigger:
Unlocked Activate Event – When this status occurs and the Schedule is Active (you can choose any Schedule). You must set a
Minimum Activation Time in the Event or the actions in the Event will not activate.
Activate Event Outside Schedule – An event is activated when this status occurs while the Schedule is Inactive
(choose any Schedule).
Alarm State Status 1. Choose a value for the Property from the Values column.
Normal 2. Select an Action from the Action drop-down list.
Forced See iSTAR Trigger Actions in Table 134 on Page 417.
Held Open 3. Select a Schedule by clicking in the Schedule column, then click to select the Schedule that you want to associate with
the trigger.
For example, if you chose Forced as an Alarm State Status for which you want to define an action, you could then select
CCTV Action if you wanted to send a command to a CCTV Switch, then in Details, select the Switch and the Command
(such as Call Up Camera) that you wanted to activate when a Forced status occurred.
Action Description
Activate Select an Event to activate when this status occurs while the Schedule is inactive.
Event
Outside
Schedule
Activate Select an Output to activate when this status occurs. Must use the Always Schedule.
Output
Arm Event Select an Event to arm. An armed Event can be activated; a disarmed Event cannot be activated.
Arm Input Select an Input to arm. An armed Input can be activated. A disarmed Input cannot be activated.
CCTV Action Select a CCTV Action to perform by choosing a CCTV Switch and Command from the Details area, and filling in one or more
Values for the Command's parameters.
Control Select an Elevator Button which you want the Action to set for controlled access, turning on security restrictions on the use of this
Access button.
Deactivate Select an Event to be deactivated. If the Event is Active when this action occurs, the action deactivates the Event.
Event
Deactivate Select an Output to be deactivated. If the Output is Active when this action occurs, the action deactivates the Output.
Output
Disable PIN Set the Reader you select to no longer require that a cardholder perform a card swipe, then enter a PIN to be granted access.
Disarm Select an Event to disarm. A disarmed Event cannot be activated; an Event must be armed to be activated.
Event
Disarm Input Select an Input to disarm. A disarmed Input cannot be activated; an Input must be armed to be activated.
Enable Set the Reader you select to accept Keypad Commands on the reader.
Keypad
Commands
Enable PIN Set the Reader you select to require that a cardholder perform a card swipe, then enter a PIN to be granted access.
Lock Door Select a Door to Lock from the Door field in the Details area.
Momentary Select a Door to Momentarily Unlock from the Door field in the Details area.
Unlock Door
Action Description
Pulse Output Select an Output to activate for the duration specified in the Output's Pulse Duration field.
Secure Door Select a Door that you want to secure. A secure Door cannot be unlocked; this action disarms the reader associated with the
Door.
Send Email Send an email message to the email address specified in the Details area Recipient Email Address field. You can designate an
Event to activate if the email attempt fails. You can click the Message tab to type the text of the message and optionally choose to
send the date, time, and name of the Event triggered. For Send Email to work, you must configure the Email Server and the
Sender Email Address in Options & Tools>System Variables in the Customer Support area.
Uncontrol Select an Elevator Button which you want the Action to set for uncontrolled access, turning off security restrictions on the use of
Access this button.
Unlock Door Select a Door to unlock from the Door field in the Details area.
Video Select a Video Camera Action to perform by choosing a Video Server and Camera from the Details area Camera tab, and
Camera choosing one of the following Action Types.
Action • Record Camera lets you set a Pre Alarm Time and Post Alarm Time for retrieving recorded video.
• Camera Preset Command allows you to designate a Camera Preset to activate when this action is triggered.
• Camera Pattern Command lets you designate a Camera Pattern to activate when this action is triggered.
Field/Button Description
Groups
For more information about the use of the Toolbar buttons, see Chapter 2, “Dynamic Views” in the C•CURE 9000
Data Views Guide
Name This column displays the name entered for the group when it was configured. The selected door is a member of any
group(s) listed in this column.
Description This column displays the description entered for the group when it was configured.
Field/Button Description
Alarm State Displays the values Normal, Forced, Held Open, or Unknown.
Field/Button Description
Double Swipe Lock Status Indicates the current status of a door configured for Double Swipe access: Locked, Unlocked, or Unknown.
If the door is not configured for double swipe access, the field displays Unknown.
Unknown Locked
Forced Unlocked
iSTAR Aperio Doors are created automatically when you configure and enable an iSTAR Aperio Reader (see iSTAR
Aperio Reader Editor on Page 516). You cannot manually create an iSTAR Aperio Door.
If you delete an iSTAR Aperio Door, the iSTAR Aperio Reader associated with the door is also deleted.
iSTAR Aperio Doors do not support manual actions for Lock, Unlock, and Momentary Unlock.
NOTE
You cannot create Door Groups that combine iSTAR Aperio Doors with other types of iSTAR Doors.
This chapter explains the concepts of Advanced Door monitoring, and also includes the procedures that are used to create
various types of monitored doors.
In this chapter
Advanced Doors support additional monitoring inputs and lock sensing equipment. Advanced Doors also integrate with
third-party lock release inputs, such as fire and crash bar devices, that control emergency exit from C•CURE 9000 doors.
Features
Use Advanced Door Monitoring to configure:
■ Multiple inputs – Advanced Doors provide up to 16 inputs, 14 more than on a standard door configuration.
■ More complex door configurations – including single- and double-leaf doors with multiple DSM or Request To Exit
(RTE) inputs.
■ Lock sensing devices – to monitor locking on magnetic bonds, bolts, and cams.
■ Integrated lock releases – to integrate door unlocking with fire, crash bar, power fail, and key switch inputs.
■ Special events and actions – to create keypad commands that lock, unlock, and secure doors for a specific time
period.
■ Alarm Suppression and RTE control on a per door basis.
■ Enhanced Shunt control.
■ Grace and change timing options – to fine tune C•CURE 9000 timing to avoid the effects of ‘door bounce’ and to
correct other door timing situations at the site.
■ Journal reports and Monitor Station activities – to manage the system and monitor door activity.
■ Additional Event Actions related to Advanced Doors.
Example:
Figure 116 on Page 423 shows a double-leaf Advanced Door, configured into A and B sides. Each side contains a
maglock, bond sensor, and DSM input that connects to RM4 modules in a nearby junction box. Access on the
public side of the door is controlled using the public-side read head. This read head is also configured to accept
keypad commands that allow personnel to lock and unlock the door for specific time intervals. Exit from the secure
side of the door is controlled by the secure-side read head.
Locks can be released for fire alarm, crash bar, power failure, or manual key switch. Inputs from the fire pull and key
switch over-ride are shown connected to an I/8 board in the local junction box.
Figure 116: Typical Advanced Door Configuration
Hardware Requirements
The following guidelines apply to Advanced Doors:
■ Advanced Door monitoring is available only on iSTAR configurations.
■ Advanced Door inputs can be any mix of lock sensors, lock releases, or DSM or RTE connections.
■ Each Advanced Door supports up to 16 input connections. However, the number of available inputs per door is limited
by the number of doors in the configuration and the input capacity of the fully loaded iSTAR controller.
■ All Door components, Readers, Inputs, and Outputs, must reside on the same Controller. The table below shows that
some controllers may not have enough Inputs for the maximum configuration. In actual practice, these limits will
rarely, if ever, be reached.,
Table 138: Maximum Inputs per iSTAR
■ Advanced Doors support the same number and types of outputs as standard doors—which are as follows:
• Door Latch Relay (1)
• Alternate Shunt (ADA) Relay (1)
• Shunt Expiration warning Relay (1)
1 = True or Active
Table 139: Lock Sensor States
1. When the door is Closed and Locked, none of the sensors are active.
2. When the door is Closed and Unlocked, all of the sensors are active except for the DSM because the Door is still
closed.
3. When the door is Open and Unlocked, all of the sensors are active including the DSM because the Door is now open.
4. When the door is Open and Locked, all of the sensors are active except for the Cam Detector because the Door is
Locked.
In this case, the Latch Bolt Detector is active because the door is Locked. When the Latch Bolt Detector is active,
along with the door being open, there is a possibility of damaging the door frame. The Latch Bolt lock is like a dead bolt
in that the bolt is extended when the door is locked.
Table 140 on Page 427 shows the types of lock sensing devices that can be configured on an Advanced Door.
Table 140: Lock Sensing Devices
Cam detector Monitors the condition of the cam on an electric strike on a door.
Latch bolt detector Monitors the condition of a latch bolt on an electric strike on a
door.
To inter-operate, the lock release device has an output, called a lock release input, that is input to the C•CURE 9000. The
C•CURE 9000 uses the lock release input to:
■ Monitor the lock release activities on a door
■ Monitor lock sensor activity
■ Decide if an open door is reported as door forced open, door open, or door open by one of the lock release inputs.
Table 141 on Page 427 and Figure 117 on Page 428 show the types of lock release devices that can be configured on an
Advanced Door.
Table 141: Lock Release Devices
Crash bar lock release Input to C•CURE 9000 from crash bar or panic hardware
Key override switch lock Input to C•CURE 9000 from a key override switch
release
Power failure lock release Input to C•CURE 9000 from power fail hardware
General Lock Release Input to C•CURE 9000 from a Fire Alarm System or iSTAR.
Fire alarm lock release Input to C•CURE 9000 from a Fire Alarm System
Alarm Description
Door Open Door opens without valid card or RTE, and one of the lock release devices is active.
Lock Unsecured A lock sensor activates when it should be inactive. Indicates that the hardware failed to return to the
locked position after a valid lock release.
Lock Tamper A lock sensor is inactive when it should be active. Indicates lock tampering while the door is open, or
failure of lock hardware.
DSM Tamper For doors with multiple DSM devices on a single side. Indicates that one DSM changed state, and
that the corresponding change did not occur to other DSMs devices on the same side of the door.
Configuration Guidelines
You must specify the first RTE in the Request to Exit field of the Configure Door dialog box. This activates other
request to exit options on the Configure Door dialog box. Specify additional RTEs by adding them on the Configure
Advanced Door Monitoring dialog box.
If a door has multiple RTEs and is configured to shunt the DSM while RTE is active, the C•CURE 9000
NOTE will shunt the DSM when any RTE on the door is active.
All DSMs on a single side must activate and deactivate together. If the DSMs do not activate together, C•CURE 9000
issues a DSM Tamper alarm and identifies the DSM that did not change state.
Because double-leaf door configurations with one DSM per side are designed to operate with one leaf open and the other
leaf closed, C•CURE 9000 does not issue DSM tamper alarms for this configuration.
All DSMs on a single side must activate and deactivate together. If the DSMs do not activate together, the C•CURE 9000
issues a DSM Tamper alarm and identifies the DSM that did not change state.
Figure 125: Double-leaf Door with DSM Top and Bottom of Each Side
If you specify a DSM in the Door Switch Monitor field of the Configure Door dialog box, C•CURE 9000 uses that input
as the DSM for side A of the door. DSM inputs that are added using the configure Door Monitoring dialog box can be
either A or B side.
Unlike multiple RTEs, you do not have to use the General Tab for DSM 1. Although the examples show two DSMs and two
RTEs, it is possible to have more than two of each.
Configuration Overview
Although Advanced Door configuration procedures vary based on site requirements, most configurations involve the tasks
and activities described in Table 143.
1. Configure Hardware Pane > Cluster > Configure inputs, readers, and outputs See Configuring RM4-1 and
Monitoring Controller > Boards > 1st on the iSTAR controller using standard RM4-2 Reader, Inputs, and
Inputs, ACM/2nd ACM procedures and dialog boxes. Output on Page 438
Readers, and
Outputs.
2. Configure Hardware Pane > Cluster > Configure lock release components on See Configuring Lock
Lock Releases Controller > Boards > 1st the iSTAR controller using standard Releases on the I/8 on Page
ACM/2nd ACM controller configuration procedures 441
and dialog boxes.
3. Configure Hardware Pane > Cluster > Configure the first RTE and the door See Configuring the
the Advanced Controller > Doors > Door Name latch relay using the standard Door Advanced Door on Page 442
Door dialog box (required). You can also use
the Door dialog box to configure the
DSM for side A.
Hardware Pane > Cluster >
Controller > Doors > Door Name Add additional components using the
> Door Monitoring Configure Advanced Door
Monitoring dialog box.
4. Configure Hardware Pane > Cluster > Specify timing requirements for unlock See Understanding Timing on
Grace and Controller > Doors > Door Name grace timers. Also specify the change Page 445
Change Time > Door Monitoring time options for individual door
parameters components, and for door shunts.
Sample Door
The configuration for this example, shown in Figure 127 on Page 438, is a double-leaf door with multiple read heads, lock
sensors, DSMs, and lock release inputs.
Figure 127: Door Configuration Example
Software House recommends that the Communication failure option be configured for all security
NOTE devices that connect to the iSTAR. Select the I/O Tab from the Reader Editor, to configure this option.
For consistency, Advanced Doors that include more than one instance of the same input (two
NOTE DSMs, for example) should use a naming convention that indicates the area of the door that the
device monitors.
Example:
DSM-Lobby-sideA.
8. In the Outputs box, select an output and configure it. Enter at least the following:
■ Name - the name of the output
9. Click Save and Close until you return to the Controller editor.
10. Repeat steps 1 through 7 to configure the RM4-2 for the B side of the door.
You must also specify how C•CURE 9000 annunciates the lock release inputs. For configuration guidelines, see the next
section.
To reduce message traffic, most configurations will choose to annunciate lock release inputs to test or troubleshoot the
system, but will not annunciate them for normal door operations.
6. Click Save and Close until you return to the main menu.
3. Enter the Readers for the Inbound and Outbound reader fields.
4. Click Save and Close until you return to the main menu.
To configure the door in Figure 131 on Page 443, enter the name of the side A DSM and the door latch relay. The sample
door uses a read head instead of an RTE. However, doors that use one or more RTE devices must configure the first RTE
on the Door Editor.
Figure 131: Sample Door
Understanding Timing
Time Delays
Use timing options to prevent false alerts caused by nearly simultaneous inputs to C•CURE 9000, and also to fine tune
timing to meet specialized door and site requirements.
In addition to the normal door de-bounce and grace times, on the Timing Tab, there are seven other timing tweaks that are
used to avoid race conditions. The Timers default to zero but it is good practice to set them all at 0.2 or 0.3, and then
adjust, as necessary. See Figure 133 on Page 445.
Since input changes cannot occur simultaneously, and if almost simultaneous may be read by our hardware in any order,
some input change time values are provided. This change time will be used whenever one of the inputs changes, to allow
the system to wait and see if any of the normally accompanying inputs is also going to change.
For example, every time the door is open (meaning the DSM input is active), the latch bolt or bond sensor input should also
be active. Therefore, every time the door opens, if the input is not already active, a timer will be started with the value of the
lock sensor change value. If the timer times out without the lock sensor input activating, then a Lock Tamper alarm will be
reported. Then when the door closes and locks, this time value will be the time we allow the lock sensor input to change
from active to secure before reporting Lock Unsecured.
Use the Timers box on the Configure Advanced Door Monitoring dialog box to fine tune timing delays for Advanced
Door components.
■ Shunt /Delay Relock times - a wait period that defines the number of seconds the door can remain open before
relock or before an alert is sounded.
Unlock Grace Time Specifies the time that C•CURE 9000 waits for a Personnel who are granted card access delay
door open signal after the door unlock timer has opening a door until unlock time is nearly expired,
expired. thereby causing nearly simultaneous DSM and
Prevents a false “door forced” message in unlock timer expiration inputs to C•CURE 9000.
situations where the signals are nearly If configured, C•CURE 9000 waits the number of
simultaneous. seconds you specify for a door open input, thereby
preventing a false “door forced open” message.
Door Open Grace Time Specifies the time that C•CURE 9000 waits for Personnel lean on a door release mechanism while
an RTE, card admit, or momentary unlock signal pressing the RTE switch, causing nearly
after receiving the signal from the DSM. simultaneous door open and RTE inputs to
Prevents a false “door forced open” message in C•CURE 9000.
situations where signals are nearly If configured, C•CURE 9000 waits the number of
simultaneous. seconds you specify for the RTE, card admit, or
For additional information, see Special Timing momentary unlock signal, thereby preventing a
Considerations on Page 448. false “door forced open” message.
Door Close De-bounce Time Specifies the time that C•CURE 9000 ignores Unintended door movement (bouncing) can
DSM inputs, to allow for bouncing doors. activate a DSM input to C•CURE 9000 and cause
false “door forced open” messages.
If configured, the Door close de-bounce time option
ignores DSM inputs for the time specified after the
door closes to allow for bouncing doors.
Change time is specified in units of 1/10 second. Enter 1 to specify 1/10 second, 5 to specify 5/10 (1/2)
NOTE second and so forth.
Software House recommends that you set all change times to at least 5/10 second and make
adjustments only as necessary.
Table 145 on Page 447 describes how change time options work for lock releases, lock sensors, and DSM and RTE
devices.
Table 145: Change Timing Options
Crash bar Specifies the amount of time C•CURE C•CURE 9000 uses the crash bar Activated by the bond sensor, latch bolt,
change time 9000 allows, after a crash bar state change time to determine changes to or cam sensor.
change, for a lock sensor change corresponding:
• Bond sensors
• Latch bolts
• Cam sensors
Bond sensor Specifies the amount of time C•CURE C•CURE 9000 uses the greatest The bond sensor should be active if:
change time 9000 allows for a bond sensor state value of the following: • Door is open
change. • Door open grace time • Door latch relay is active
C•CURE 9000 uses this time, and the • Door close de-bounce time
time of the other door inputs, to • Lock release input(s) are active
determine the wait before issuing a • Crash bar change time The bond sensor should be inactive
“lock tamper” or “lock unsecure” alarm. • Bond sensor change time when:
• RTE change time • Latch relay is inactive, the door is
closed, and the lock release inputs
are inactive
Latch bolt Specifies the amount of time C•CURE C•CURE 9000 uses the greatest The latch bolt should be active if the
change time 9000 allows for a latch bolt state value of the following: door is open.
change. • Door open grace time The latch bolt should be inactive if:
C•CURE 9000 uses this time, along • Door close de-bounce time • Door is closed
with the time of the other door inputs, to
determine the wait before issuing a • Crash bar change time • Door latch relay is inactive
“lock tamper” or “lock unsecure” alarm. • Latch bolt change time • Lock release inputs are inactive
• RTE change time The latch bolt can be active or inactive if:
• Door latch relay is active
• Lock release input(s) are active
Cam sensor Specifies the amount of time C•CURE C•CURE 9000 uses the greatest The cam sensor should be active if:
change time 9000 allows for a cam sensor state value of the following: • Door latch relay is active
change. • Crash bar change time • Lock release input(s) are active
C•CURE 9000 uses this time, along • Cam sensor change time
with the time of the other door inputs, to The cam sensor should be inactive if the
determine the wait before issuing a • RTE change time door latch relay is inactive and all lock
“lock tamper” or “lock unsecured” releases are inactive
alarm.
DSM side A Specifies the amount of time C•CURE Additional DSM inputs on the same DSM change time is active when the first
change time 9000 allows for a DSM state change. door side DSM in a group changes state. (DSMs
- or - C•CURE 9000 uses this value to must be located on the same side of the
determine the wait period before door).
DSM side B
change time activating a DSM tamper for multiple
DSM devices on one side of the door.
RTE change Specifies the amount of time C•CURE C•CURE 9000 uses the RTE change Activated by the bond sensor, latch bolt,
time 9000 allows, before or after an RTE time to determine changes to or cam sensor.
state change, for a lock sensor change. corresponding:
For additional information, see "Special • Bond sensors
Timing Considerations" below • Latch bolts
• Cam sensors
Option Description
Delay relock while door open after valid access If access is valid, delays the relock of the door until the door closes. This differs from
standard relock operations where relock occurs when the:
• Door opens.
• Door opens and the relock delay expires.
If the door is open, the lock is energized.
C•CURE 9000 sends an alarm when the shunt time expires.
Shunt door for full shunt time Activates the shunt for the full time specified.
If selected with Delay relock while door open after valid access, the lock is
energized and the door unlocked for the full shunt time, regardless of whether the door
is open or closed.
■ Adjusting the timing of door components – use the RTE change time option to specify timing for incoming traffic
and also to change the function of the Door open grace time option.
The RTE change time option specifies the amount of time that C•CURE 9000 ignores RTE inputs after the door is closed.
Use this value to prevent false door forced reports caused by door components (slow bolts or sensors, bouncing door, for
example) for outgoing traffic.
The RTE change time option also changes the function of the Door open grace time option. If you specify a value for
RTE change time, the Door open grace time option now specifies the time C•CURE 9000 ignores RTE changes before
the door open occurs. This prevents RTE signals from the motion detector that are caused by door mechanics rather than
human access. If C•CURE 9000 sees an RTE on a closed door, and then sees the door open within the period you
specify, it cancels the RTE and issues a door forced alarm.
To Display Information about Alarms, Alarm Causes, and Door Component Status
1. Select Doors from the Non-Hardware Pane on the Monitoring Station Explorer Bar.
2. Right click on a Door and select Door Monitoring.
3. Use Door Monitoring to Show Locked Causes and various Alarm States.
4. Door Monitor Inputs are also shown at the top of the Door Monitoring Editor. Right click on an input for further context
menu options.
Alarms
This section describes how C•CURE 9000 manages alarm traffic and contradictory component reports that can
sometimes accompany Advanced Door configurations.
Door Open Alarm - this alarm occurs whenever the door opens without benefit of card or request to exit access, and one
of the lock release devices is active. This alarm indicates that some kind of emergency unlock is occurring. The alarm
message includes the name of the lock release device as the reason for the door open alarm. In the case that none of the
lock release devices is active, this is a normal door forced open alarm.
Lock Unsecured Alarm - this alarm occurs whenever a lock sensor is active when it should be inactive. This indicates
that the lock hardware failed to return to locked position after being unlocked by one of the lock release devices or by
regular door control. The alarm message includes the name of the lock sensor input that caused the alarm.
Lock Tamper Alarm - this alarm occurs whenever one of the lock sensors is inactive when it should be active. This is
whenever one of the lock release devices is active or the door latch relay has been activated by the door or the DSM
indicates that the door is open. This may indicate that someone is tampering with the lock sensor while the door is opening
or that the lock hardware has failed. The alarm message includes the name of the lock sensor input that caused the alarm.
DSM Tamper Alarm - this alarm is reported if multiple DSM inputs monitor the same door and one of them does not
become active when it should. The alarm message includes the name of the input that is not active.
The example in Figure 134 on Page 453 shows the General Activity Monitor for a simplified door that includes two bond
sensor inputs and a DSM. The following actions occurred:
1. Door closed (no inputs inactive).
2. Card admitted, door open (DSM activates, bond sensor 1 activates as expected, bond sensor 2 does not activate).
3. Door Lock unsecured reported (bond sensor 1).
4. Bond sensor 1 deactivates while the door is open, causing a second input to the lock tamper alarm.
C•CURE 9000 does not display an additional alarm report for bond sensor 2 on the General Activity window.
Figure 135 on Page 455 shows the Monitoring Status for the example door activities. C•CURE 9000 reports the first lock
tamper (bond sensor 2) and does not clear the alarm. The second lock tamper (bond sensor 1) on the same door does not
display on the General Activity Monitor.
Figure 135: General Activity Alarms Reports Example
Clearing Alarms
Advanced Door alarms may occasionally appear “stuck” because C•CURE 9000 waits for the input to change state before
clearing the alarm. This is to reduce unnecessary alarm traffic. If all inputs are functioning properly, you can clear all door
and input alarms by performing a normal door access cycle (opening and closing the door).
Door Triggers
In addition to the usual five Door Triggers:
■ Admit Status - Admit, Reject, Noticed Admit, Noticed Reject, Duress
■ Double Swipe Status - Locked, Unlocked
■ Mode Status - Unlocked, Locked, No Access
■ Open Status - Open, Closed
■ Alarm State Status - Normal, Forced, Held Open
There are four additional Advanced Door Triggers shown in Figure 136 on Page 456.
Privilege Modifications
Reports
A standard iSTAR Door Report can be used to list all of the Advanced Door components.
Each of these selections let you initiate a Manual Action to enable or disable the selected function.
See Viewing a List of Doors on Page 381 for more information about the context menu for Doors.
Advanced Door Monitoring has 7 Cause List type states, and 14 possible manual actions that may be associated with
these:
■ RTE enable/disable,
■ door forced alarm enable/disable,
■ door held open alarm enable/disable,
■ door open alarm enable/disable,
■ lock tamper alarm enable/disable,
■ lock unsecured alarm enable/disable,
■ DSM tamper alarm enable/disable.
Enter the Door Monitoring Status screen for iSTAR doors by right clicking on the Door and selecting Door Monitoring
from the context menu. You can also execute the Manual Actions listed above, from this context menu.
Figure 138: Door Context Menu
See Door Monitoring Screen on Page 461 for more information about the Door Monitoring screen.
The upper dynamic view displays Door Monitoring Inputs status. The bottom part displays cause lists and all ‘cause list’
standard functionality is available (right mouse click on selected row will activate "Details/Cancel" context menu).
Figure 139 on Page 461 shows an example of the Door Monitoring Screen.
Table 147 on Page 462 provides definitions for the fields and selections on the screen.
Also see Table 142 on Page 429 for an explanation of the Alarms.
Figure 139: Door Monitoring Screen
The availability of manual actions depends on input assignments. The rules to show/hide manual action on the Door
Monitoring Screen and show/hide executors on iSTAR Door Dynamic Views are:
■ If there is an RTE input then show Enable/Disable RTE;
■ If there is a DSM input then show Enable/Disable Door Forced Alarms, Enable/Disable Door Held alarms, if there is
also any DSM side A inputs, then Enable/Disable DSM Tamper
■ If there is a Bond Sensor input then show Enable/Disable Lock Tamper alarms, Enable/Disable Lock unsecured
alarms;
■ If there is a Latch Bolt Detector input then show Enable/Disable Lock Tamper alarms, Enable/Disable Lock unsecured
alarms;
■ If there is a CAM detection input then show Enable/Disable Lock Tamper alarms, Enable/Disable Lock unsecured
alarms;
■ If there is a DSM Side A input then show Enable/Disable Door Forced Alarms, Enable/Disable Door Held alarms, if
there is also a main DSM, or another DSM side A, then Enable/Disable DSM Tamper;
■ If there is a DSM Side B input then show Enable/Disable Door Forced Alarms, Enable/Disable Door Held alarms, if
there is more than one DSM side B, then Enable/Disable DSM Tamper;
■ If there is an RTE2 input then show Enable/Disable RTE.
Table 147: Doors Monitoring Screen Definitions
Field/Button Description
Click this button to refresh the values of all Inputs on the screen.
Refresh All
This toolbar lets you perform Dynamic View functions on the list of Door Inputs, such as filtering, printing, and
switching to Card View.
Input type This column displays the function that the Input serves in Door Monitoring.
Armed Status This column displays the Armed Status of the Input. Inputs associated with Doors are automatically Armed and
are reported as unknown.
Active Status This column displays the Active Status of the Input.
Cause Selection This drop-down list lets you choose the Cause type to display in the Status Information and Cause List section of
the screen.
Status Information This read-only field displays the current state of the selected Input.
Cause This read-only field displays the Cause State for the Input.
Action This read-only field displays the Lock and Unlock actions that are in effect on the door.
DateTime This read-only field displays the Date and Time the cause occurred.
Priority This read-only field displays the Event Priority of the cause.
Lock Click this button to initiate a manual action to lock the Door.
Unlock Click this button to initiate a manual action to unlock the Door for a defined period.
Momentary Unlock Click this button to momentarily unlock the Door for the Door Unlock period (usually 5 seconds).
Field/Button Description
Enable _____ The Enable button changes to match the selected Cause Selection in the drop-down list. Click this button to
enable the selected Cause type.
Example:
If the Cause Selection is Door Forced Alarms, then the button reads Enable Door Forced Alarms.
Disable _____ The Disable button changes to match the selected Cause Selection in the drop-down list. Click this button to
disable the selected Cause type.
Example:
If the Cause Selection is Door Forced Alarms, then the button reads Disable Door Forced Alarms.
If a door has one IN and OUT reader, rejects are counted separately for each direction.
The reject count and timer are reset when the following occurs:
■ a subsequent reject does not happen in the configured time period. For example, if the configured time period expires
after the first reject, then the configured number of rejects and time period are reset to zero.
■ the reject timer expires.
■ if there is a good card swipe (access granted) following rejects.
■ when the iSTAR is rebooted.
The number of consecutive rejects is set to 3, and the timer is set to 30 seconds. A single cardholder is rejected three
times in a row within 30 seconds.
1. Cardholder A presents a card at the door reader and is rejected, reject count = 1.
2. Five seconds later, cardholder A presents the card again and is rejected, reject count = 2.
3. Five seconds later, cardholder A presents the card again and is rejected, reject count = 3.
When the number of consecutive rejects reaches 3, a configured event is activated and sent to the Monitoring Station. The
reject count and the reject timer resets to 0.
The number of consecutive rejects is set to 3, and the timer is set to 30 seconds. Multiple cardholders (cardholder A with
credential X, cardholder B with credential Y, and cardholder C with credential Z) present their cards at the door reader. All
three cardholders are rejected within 30 seconds.
1. Cardholder A with credential X presents a card at the door reader and is rejected, reject count = 1.
2. Five seconds later, cardholder B with credential Y presents a card at the door reader and is rejected, reject count = 2.
3. Five seconds later, cardholder C with credential Z presents a card at the door reader and is rejected, reject count = 3.
When the number of consecutive rejects reaches 3, a configured event is activated and sent to the Monitoring Station. The
reject count and the reject timer resets to 0.
The number of consecutive rejects is set to 3, and Area Occupancy is configured with maximum 3 and minimum 2.
1. Cardholders A, B, C, and D plan to enter the area.
2. Cardholder A presents card at the door reader to enter. Cardholder A is rejected because area occupancy minimum set
to 2. Reject count = 1.
3. Cardholder B present card at the door reader and both cardholder A and cardholder B enter the area (area occupancy
minimum set to 2).
4. Cardholder C presents card at the door reader and enters the area (area occupancy maximum set to 3).
5. Cardholder D present card at door reader and is rejected. Area occupancy maximum was reached with cardholder C.
Reject count = 2.
6. Cardholder D presents the card again at the door reader and is rejected, and the reject count = 3.
When the number of consecutive rejects reaches 3, a configured event is activated and sent to the Monitoring Station. The
reject count resets to 0.
The number of consecutive rejects is set to 3. A single cardholder is rejected three times within 30 seconds.
1. Cardholder A enters the wrong PIN and is rejected, reject count =1.
2. Five seconds later, cardholder A enters the wrong PIN again, and is rejected, reject count = 2.
3. Five seconds later, cardholder A enters the wrong PIN again and is rejected, reject count = 3.
A configured event is activated and sent to the Monitoring Station. The reject count and reject timer are reset to 0.
The number of consecutive rejects is set to 3. The timer is set to 60 seconds. Two cardholders swipe their cards at a door
IN and OUT reader and gets rejected three times within 60 seconds.
1. Cardholder A swipes the IN direction reader and is rejected, the IN door reader reject count = 1.
2. Five seconds later, cardholder A swipes the IN direction reader again and is rejected, IN door reader reject = 2.
3. Five seconds later, cardholder B swipes the OUT direction reader and is rejected, OUT door reject count = 1.
4. Five seconds later, cardholder B swipes again at the OUT direction reader and is rejected, OUT door reject count = 2.
5. Five seconds later, cardholder A swipes at the IN direction reader again and is rejected, the IN door reader reject count
= 3.
6. Five seconds later, cardholder B swipes the OUT direction reader again and gets rejected, OUT door reader reject
count = 3.
Configured IN and OUT direction events are activated and sent to the Monitoring Station. The IN and OUT direction reject
count and reject timers are reset to 0.
In C•CURE 9000, before you configure a Reader, you must first create and configure the type of controller to which the
Reader is connected. Then you can create and configure the Reader from the controller component the Reader is
associated with.
In this chapter
Reader Overview
A Reader is a hardware device that accepts access requests. To make an access request, a person presents a card at the
Reader; the card reader scans the information encoded on the card and sends it to the controller, which grants or denies
access. The controller reports the activity to the C•CURE 9000 Server.
In C•CURE 9000, before you configure a Reader, you must first create and configure the type of controller to which the
Reader is connected. Then you can create and configure the Reader from the controller component the Reader is
associated with.
There is a Reader Editor for each type of Reader object in C•CURE 9000:
■ apC Reader Editor
■ iSTAR Reader Editor
■ iSTAR Aperio Reader Editor
OSDP is supported on the iSTAR Ultra and Ultra SE (Ultra Mode) with firmware 6.4.2 and later, and the IP-ACM.
■ The OSDP Restrictions and Limitations on Page 472 also apply to Innometriks readers.
NOTE
■ To configure Innometriks High Assurance Phase 2 Readers, see Innometriks High Assurance Reader
Configuration on Page 480
OSDP chains that contain readers from different manufacturers may experience intermittent communications failure. For optimum
performance, configure OSDP chains to only contain readers from a single manufacturer.
Readers Supported
■ HID iCLASS SE
■ Allegion aptiQ
■ INID
■ Innometriks Cheetah
■ Innometriks Rhino
■ Innometriks Cheetah SE (supported on C•CURE 9000 v2.70 SP2 and higher with iSTAR firmware v6.6.5 and higher)
The readers ship with the OSDP installer key (default key). The readers automatically switch from the
NOTE default key (installer mode) to a new key when the reader is powered on.
Features
■ Secure channel encryption, AES128, enabled by default.
■ Card data and keypad commands.
■ Intrusion zones and keypad commands.
■ Reader tamper indication.
■ Supports up to 8 OSDP readers daisy chain on each iSTAR Ultra/Ultra SE RS-485 device port. See information about
Speed selection.
Each reader on a chain must have a unique address. However, the factory default address for all
NOTE OSDP readers is 0. Ensure that you change the address for the second reader and each subsequent
reader in the chain. Refer to the reader’s manufacturer for the address setting process.
Readers configured with the wrong Baud Rate may cause communication problems with other
NOTE readers. Connecting a chain of readers with any mismatched Baud Rate can keep the entire chain
offline.
■ Ensure the reader baud rate and reader address match the baud rate on the RS485 port and the reader address
configured in C•CURE. Connecting a chain of readers with any mismatched Baud Rate can keep the entire chain
offline.
■ To utilize the customizable LED/Beep/Message features, the OSDP reader must support the full set of LED/Beep
commands in the OSDP specification.
■ Innometriks Readers only:
• The new LED and beep patterns are supported on the Cheetah SE. They are not supported on the older Cheetah
and Rhino classic readers.
• If one of the readers in a multi-drop configuration reboots or performs an initial boot, the rest of the readers in that
multi-drop will experience brief communication loss during that time.
■ In an OSDP multi-drop environment, use the higher baud rate (38.4K or 115K.) for the customizable LED patterns,
Beep patterns, and LCD message set features.
■ The double-swipe beep configurations supersede all other beep configurations. Avoid using the ninth pattern (400 ms
on/200 off/100 on) and the 10th pattern (100 ms on/200 off/400 on/200 off/100 on/200 off/100 on) if you are using
double-swipe for other purposes.
■ If you are using LED colors, ensure that the reader supports the colors you choose for the configuration. Check the
reader documentation.
You may need to use a HID configuration card to enable Secure Channel if you do not purchase HID
NOTE readers through Software House.
Model Description
AQ-MT11-485 Mullion
For Wiegand readers, the conversion process creates a new device port and moves the Wiegand reader to that port.
For RM readers, you select a single reader for conversion, but you can convert the entire chain of RM readers. When you
select a single reader, if it is the only reader on the device port then you can select the current device port to be converted
to OSDP. If there are other readers on the device port, you must select a different device port. When you select to convert
the entire chain of readers, you can either convert the current device port to OSDP or you can select a different device port.
Prerequisites
■ Reader and controller firmware must be at version 6.6.B or later. The Convert reader to OSDP option is not available
for devices with incompatible firmware.
■ The cluster must be disabled before you start the conversion. You can manually disable the cluster then run the
conversion, or the conversion will automatically disable it for you.
From the OSDP Reader Conversion page, you can select an option to re-enable the cluster after the conversion
NOTE process is complete.
If you select an empty OSDP device port from the list, the baud rate is set automatically, and you cannot change
NOTE this value.
If you select an empty OSDP device port from the list, the baud rate is set automatically, and you cannot change
NOTE this value.
OSDP Troubleshooting
If OSDP readers do not come online immediately, check the following:
■ Wiring – check the wiring of the reader (HID’s brown and tan wires look very similar).
■ Configuration – ensure the port is set to OSDP, and that the limit of 8 readers per ACM was not exceeded.
■ Check the port’s green TX and RX lights – they should be flashing constantly. If not, the port may not be configured
properly.
■ Ensure the readers are set for secure channel encryption. Check the reader part number to verify. You may need to
use configuration cards to enable secure channel encryption.
HA is supported on C•CURE 9000 v2.70 with v2.70 SP2 installed, and higher.
In this section:
■ Hardware and Firmware Requirements on Page 480
■ Reader Configuration Requirements Checklist on Page 480
■ Importing the Enrollment Service XML file on Page 482
■ Configuring the FICAM Plugin User-Defined Field on Page 482
■ CHUID Templates for use with Card Formats on Page 483
■ Enrolling Users on Page 486
■ Reader Configuration on Page 486
Supported Modules
USB-ACM, SE USB-ACM, or the IP-ACM v2.
• Innometriks Cheetah SE reader: press F1 and F4 simultaneously, then press the 2 key.
• Innometriks Cheetah and Innometriks Rhino readers: press and the F1 key at the same time.
3. Install and configure the Innometriks Identity Server. See the Innometriks Identity Server User Guide for installation
and configuration information.
4. Install the following Innometriks software services:
• FICAM High Assurance Services (on the same computer as the C•CURE 9000)
• FICAM Enrollment Client (can be installed on a different server or desktop system)
• FICAM Enrollment Plugin (on the same computer as the C•CURE 9000)
a. Go to http://www.swhouse.com/Support/SoftwareDownloads.aspx. You must be a registered user to access this
site.
b. Select Innometriks High Assurance to access and download the installation files.
c. See the Innometriks High Assurance Solution Installation and Configuration Guide for extraction and installation
instructions.
The following XML files used are installed to the following locations:
NOTE
■ Program Files (X86)\Tyco\CCURE Client\HA_Card Formats
• Card-Format-Government-200-bit-FASC-N.xml
• Card-Format--PIV-I.xml
CAUTION: Do not use the CHUID xml files.
5. Attach a smart card enrollment reader device to the operating system where C•CURE 9000 is installed. The reader
device is required to read the personnel enrollment data from the cards. See the manufacturer’s documentation.
6. Ensure the Innometriks reader is directly connected to the configured ACM or the IP-ACM v2.
7. Ensure the C•CURE license file is applied, and the following information is verified in the License Manager (C•CURE
9000 tab):
a. System Wide Capabilities:
— HA Assurance Readers lists the correct number of licensed readers.
b. Licensed Features:
— Innometriks Enrollment - Plugin
— Innometriks HA Enrollment Service
— Innometriks HA Panel Service
8. Ensure the cluster and the controller is configured.
9. Ensure that FICAM High Assurance is enabled on the controller to which the reader is connected:
a. Open the iSTAR Controller editor dialog box and select the General tab.
b. Click Enable FICAM High Assurance.
c. Click OK.
10. The Enrollment Service XML file is imported using the C•CURE Data Import Utility.
See Importing the Enrollment Service XML file on Page 482.
11. A User Defined Field (UDF) is created for the FICAM plugin.
See Configuring the FICAM Plugin User-Defined Field on Page 482
12. The HA card format XML files are imported.
See CHUID Templates for use with Card Formats on Page 483
13. Configure the reader in C•CURE.
See Reader Configuration on Page 486
Available CHUID templates:
Do not use the CHUID.xml files that were installed along with the card templates.
Extending the time ensures all cards will remain valid for the period of time selected after the Source of Authority
Certificate (Not valid after) expires, if the connectivity between the MAS/SAS be down for an extended period of time.
This section describes how to locate the system ID, add the ID to the card format template, and how to import the file.
3. Click the drop-down arrow next to New and select Full FASC-N CHUID Format (200-bit) Template (for Card Format
Government 200-bit FASC-N).
The CHUID Format dialog box opens.
4. Enter a Name for the CHUID Format.
5. Click Enabled.
6. Click Save and Close.
7. Click next to CHUID Format to open a Dynamic view listing all CHUID Formats.
8. Right-click on the CHUID format you created from the template you selected in Step 3 and select Export Selection.
9. Browse to a location to save the file and click Open. The Exporting CHUID Data Format dialog box opens.
10. Click OK when the export is complete is displayed in the dialog box.
11. Navigate to the exported CHUID format file.
12. Open the file with Notepad.
13. Locate <objectID> in the file and note the number.
Example: <objectID>5004</objectID>
14. Close the file.
15. Navigate to C:\Program Files (x86)\Tyco\CCURE Client\HA_Card_Formats.
16. Locate the Card-Format-Government-200-bit-FASC-N.xml file and open it in Notepad.
17. Locate <CHUIDFormatID> in the file and replace the number with the number you noted in step 13.
Example: <CHUIDFormatID>5004</CHUIDFormatID>
18. Save the file.
19. Click the Configuration pane.
20. Select Data Import from the Configuration drop-down menu. The Data Import dialog box opens.
21. Enter a name for the Card Format.
This section describes how to locate the system ID, add the CHUID ID to your template, and how to import the template.
7. Click next to CHUID Format to open a Dynamic view listing all CHUID Formats.
8. Right-click on the CHUID format you created from the template and select Export Selection.
9. Browse to a location to save the file and click Open. The Exporting CHUID Data Format dialog box opens.
10. Click OK when the export is complete is displayed in the dialog box.
11. Navigate to the exported CHUID format file.
12. Open the file with Notepad.
13. Locate <objectID> in the file and note the number.
Example: <objectID>5004</objectID>
14. Close the file.
15. Navigate to C:\Program Files (x86)\Tyco\CCURE Client\HA_Card_Formats.
16. Locate the Card-Format-PIV-I-Card-Format.xml file and open it in Notepad.
17. Locate <CHUIDFormatID> in the file and replace the number with the number you noted in step 13.
Example: <CHUIDFormatID>5004</CHUIDFormatID>
18. Save the file.
19. Click the Configuration pane.
20. Select Data Import from the Configuration drop-down menu. The Data Import dialog box opens.
21. Enter a name for the Card Format.
26. Select the Card-Format-PIV-I-Card-Format.xml file and click Open. The Importing data dialog box opens.
27. Click OK when "Import complete" is displayed in the dialog box.
28. Click Save and Close.
The PIV I Card Format is now available.
Enrolling Users
After the services are installed, you must edit existing Personnel records, or create a new Personnel record, to enroll
users. The Personnel record uses the HA XML files you manually imported to add the Card Reader tab which allows HA
enroll configuration.
To Enroll Users
1. Ensure that the smart card enrollment reader is connected to the operating system.
2. Click the Personnel pane.
3. Select Personnel from the drop-down menu list and click to open a Dynamic View displaying all configured
Personnel records.
or,
Select Personnel from the drop-down menu list and click New to create a new personnel record.
4. Select Ficam Enrollment from the Current View drop-down list, located at the top of the screen.
5. Click the Card Reader tab.
6. Select the card reader from the drop-down list of available card readers.
7. Place the configured card on, or in, the smart card enrollment reader and click Read Card.
All information on the card is read into the personnel record and overrides all previous information. Information can be
edited once the process is complete.
8. Complete configuration updates.
9. Click Save and Close when done.
Reader Configuration
See the following:
■ Configuring the HA Reader connected to an IP-ACM v2 on Page 486
■ Configuring the HA Reader connected to an ACM on Page 488
The iSTAR Reader dialog box opens. See iSTAR Reader Editor on Page 496 for more information about the tabs and
fields.
The iSTAR Reader dialog box name field displays the following information about the reader:
NOTE
■ Reader number
■ Port number
■ IP-ACMv2 number
■ Controller name
The iSTAR device Port dialog box opens. See iSTAR Ultra ACM RS-485 Device Port Editor on Page 204 for more
information about the tabs and fields.
9. Select OSDP from the Protocol drop-down menu.
10. Select the Baud Rate from the drop down menu. The baud rate must match the baud rate configured on the reader.
11. Click the Readers tab.
12. Click on the Configured check box in the Index row of the reader attached to the port on the controller.
13. Click in the Edit column in the Index row of the reader.
The iSTAR Reader dialog box opens. See iSTAR Reader Editor on Page 496 for more information about the tabs and
fields.
The iSTAR Reader dialog box name field displays the following information about the reader:
NOTE
■ Reader number
■ Port number
■ IP-ACMv2 number
■ Controller name
a. Select the Support High Assurance Reader check box. The High Assurance Operation Mode selections become
available for selection.
b. Select the High Assurance Operation Mode.
c. Click Save and Close to save the settings and close the dialog box.
RM Mode Configuration
In RM mode, you can connect the reader to iSTAR Classic, Pro, eX, Edge, Ultra, Ultra SE (Ultra Mode or Pro Mode), or
Ultra LT controller.
Ensure the reader S2-1 DIP switch is in the OFF position and S2-2 is in the ON position.
NOTE
Ensure the reader S2-1 and S2-2 DIP switch are in the OFF position.
NOTE
The Smart protocol will not be available if offline mode is enabled on the IP-ACM.
NOTE
This procedure updates the firmware on all TST-100 Touchscreen Terminals connected to the iSTAR.
Update Firmware will not appear on the context menu if the iSTAR is not Enabled or is off-line.
NOTE
Touchscreen Reader only appears on the drop-down menu if there are Smart mode TST-100 Touchscreen
NOTE Terminal readers configured on the panel.
3. Select the firmware version that you want to download from the list in the dialog box.
4. Click Start firmware download.
A progress bar indicates the firmware download to the controller is complete.
5. When the download has completed, click Close to close the dialog box.
After the download is successful, the controller updates all Smart mode TST-100 Touchscreen Terminal readers
connected to the controller, if needed.
The TST-100 Touchscreen Terminal reader firmware update can be verified in the iSTAR Reader Status Tab on Page 504
Reader Editor
The Reader Editor in C•CURE 9000 lets you configure and edit Reader objects to control entrances and exits within your
facility.
Readers are created as child objects under a controller, rather than directly from the Hardware Tree.
Each Controller type has Reader settings that are Controller-specific. Therefore, there is a Reader Editor for each
Controller type.
The following topics give more information about the various Controller-based Reader objects and how to use them.
■ Reader Overview
■ apC Reader Editor
■ iSTAR Reader Editor
■ iSTAR PIM-485 Reader Editor
■ iSTAR Aperio Reader Editor
■ Accessing the Reader Editor
Alternatively, you can view Readers connected to a specific controller by clicking the pointer ( ) to open the
Hardware Tree for a Controller, navigating in the tree to open a Reader folder under that Controller, showing a
list of Readers.
3. Double-click on the Reader in the list of Readers that you want to edit, and the Reader Editor opens.
apC Readers
l apC Reader General Tab
l apC Reader Input/Output Tab
l apC Reader Keypad Tab
l apC Reader Triggers Tab
l apC Reader Status Tab
iSTAR Readers
l iSTAR Reader General Tab
l iSTAR Reader Input/Output Tab
l iSTAR Reader Keypad Tab
l iSTAR Reader Triggers Tab
l iSTAR Reader Status Tab
l iSTAR Reader After-Hours Tab
The iSTAR Reader editor (see Figure 143 on Page 497) has the following tabs:
■ iSTAR Reader General tab
Lists the Reader name, connections, and card formats for a reader connected to an iSTAR. See iSTAR Reader
General Tab on Page 498.
■ iSTAR Reader I/O tab
This tab lets you configure the available Inputs and Outputs for the Reader. See iSTAR Reader I/O Tab on Page 500.
■ iSTAR Reader Keypad tab
This tab lets you configure the settings and options for the Reader Keypad. See iSTAR Reader Keypad Tab on Page
501.
■ iSTAR Reader Triggers tab
See Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
■ iSTAR Reader Groups tab
If you have created a Group containing iSTAR readers and added this Reader to the Group, the iSTAR Reader editor
displays a Group tab.
This tab lists the Reader groups to which this Reader belongs. See Groups Tab for Hardware Devices on Page 36 for
information on using the Group tab for the iSTAR Reader.
■ iSTAR Reader Options tab
Use this tab to enable two factor authentication on the reader and to configure LED Control and Beep on Card Read for
Wiegand Readers. See iSTAR Reader Options Tab on Page 505.
■ iSTAR Reader Status tab
This tab displays several read-only fields that report the Communications, PIN Required, and Keypad Command
Allow Status of the Reader. See iSTAR Reader Status Tab on Page 504.
■ iSTAR Reader After-Hours tab
This tab enables the After-Hours Readers Group feature. See After-Hours on Page 506 for further information and
procedures to configure this feature.
Use this tab to select the Innometriks reader high assurance settings. See High Assurance Tab on Page 509
■ Touchscreen tab
Use this tab to set the TST-100 Touchscreen Terminal Reader's Automatic Dim brightness and time. This tab also
displays the card types supported and allows you to reporder the card type priority. See iSTAR Reader Touchscreen
Tab on Page 508.
■ iSTAR Reader State Images tab
This tab displays the default images used to depict this reader in the Monitoring Station. You can use this tab to
customize these state images. See iSTAR Reader State Images Tab on Page 510.
You can add or remove Card Formats from multiple Readers on the iSTAR Reader Dynamic View. See Add or Remove
Reader Card Formats on Page 33 for more information.
In each case, you must select the Configure column to configure the reader, then click to open the iSTAR Reader
editor.
Field/Button Description
Identification
Name Displays the name for this Reader. The name is system-generated by default, but you can edit
this name by clicking in click in this field.
Description Enter a textual comment about the Reader, such as its location or purpose. This text is for
information only.
Field/Button Description
Maintenance Mode Click to put the iSTAR Reader into Maintenance Mode. See Chapter 3: Maintenance Mode for
more information.
Partition This read-only field identifies the Partition in which this reader resides.
Controller This read-only field identifies the iSTAR Controller to which this reader is attached.
Board This read-only field identifies the iSTAR Controller board to which this reader is attached.
Assigned to Displays the Elevator or Door object name with which this reader is configured.
Connection Identifies the Reader number on the hardware board to which this reader is connected.
Card Format
If the card format you desire is not in the Name Selection dialog box list, click in the Select
Type field to select a card format.
Remove
Click the row selector to select one or more Card Format rows (hold down SHIFT or Ctrl to
select multiple rows), then click Remove to delete the row(s) for this field.
Name Displays the Name of each Card Format you have chosen for this Reader.
Description Displays the Description for the Card Format. This field is read-only.
Clearance Filter
Default Clearance Select a Clearance Filter Level for the reader from the drop-down list. The available Clearance
Filter Level Filter Levels are numbered 1 through 6. Personnel assigned with lower Clearance Filter Levels,
in the Personnel than the reader configuration are denied access.
• Level 6 is the highest level.
• Level 1 is the lowest level and the default setting.
Field/Button Description
Beep on Key Press Select this check box for the TS-100 Touchscreen Terminal reader to beep when pressing a key.
Beep on Card Read Select this check box for the TS-100 Touchscreen Terminal reader to beep on a card read.
Date Format Select the date format and/or the time format to use.
Time Format
Definitions for the Inputs on the iSTAR Aperio Reader I/O Tab are described in iSTAR Aperio Reader I/O Tab on Page 518.
The fields on this tab vary depending upon the type of Reader you are configuring. For example, a Direct Connect Wiegand
Reader displays only the Communications Fail Input on the I/O tab.
Table 150: iSTAR Reader I/O Tab Definitions
Field/Button Description
Inputs
Create All Inputs Click to create all eight Inputs. The check boxes in the Configured column are set to .
Delete All Inputs Click to delete all eight Inputs. The check boxes in the Configured column are set to .
Edit Click in this column to open the iSTAR Input Editor to edit this Input.
Connection This read-only field identifies the position of each Input on the I/O tab.
Name Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to
select an Input Template. If the Configured column displays , this field cannot be edited.
Supervised 1 Represents Supervised Input #1 on iSTAR Readers. Not available on direct connect Wiegand Readers.
Field/Button Description
Supervised 2 Represents Supervised Input #2 on iSTAR Readers. Not available on direct connect Wiegand Readers.
Tamper Represents the Tamper Input on iSTAR Readers. Not available on direct connect Wiegand Readers.
Outputs
Create All Click to create all Outputs. The check boxes in the Configured column are set to .
Outputs
Delete All Click to delete all Outputs. The check boxes in the Configured column are set to .
Outputs
2 Represents Output #2 on iSTAR Readers. Not available on direct connect Wiegand Readers.
Field/Button Description
PIN is not If selected, only a card swipe is required for successful access to the door connected to this reader.
required
PIN only If selected, this reader can be used for PIN-Only access.
NOTE: PIN only cannot be used as a Query filter value for the PIN Required Status field.
Card and PIN If selected, this reader requires both a card swipe and a PIN entry at the keypad for access.
required
Schedule If Card and PIN Required is selected, you can select a Schedule object to determine when Card and PIN Required is
enforced. When the Schedule is active, both Card and PIN are required for access. When the Schedule is inactive, only a card
swipe is required.
Allow PIN If Card and PIN Required is selected, Personnel records configured with PIN Exempt (ADA) are exempt from having to
Exempt (ADA) enter a PIN for access.
Field/Button Description
Allow card If you have selected PIN is not required or Card and PIN required, you can enable Allow card numbers to be entered
numbers to be from the keypad by selecting the check box. If you chose PIN Only, this option is unavailable because the Keypad must be
entered from used to enter a PIN.
keypad
Use PIN+1 as If you have selected PIN is not required or Card and PIN required, you can enable Use PIN+1 as duress code by
duress code selecting the check box. If you chose PIN Only, this option is unavailable.
Keypad Indicates whether or not Keypad Commands can be entered on this Reader’s Keypad and when. Select one of the following
Commands options from the drop-down list. The default is Not Allowed.
Allowed • Not Allowed – Keypad Commands cannot be used at the Reader
• Always Allowed – Keypad Commands can always be used at the Reader
• Allowed during specified schedule – Keypad Commands can be used at the Reader during the period specified in the
following field. When you select this option, the Schedule for Keypad Commands field becomes available.
Scramble TST-100 Touchscreen Terminal Reader using the Smart Protocol only.
Keypad If the reader is using the Smart protocol on the reader, you must select this check box to enable Scramble Keypad on the reader.
When the PIN is being entered, the LED displays a randomly allocated set of numbers from 0 to 9. The position of the numbers
changes every time the keypad is activated.
NOTE: This field is not visible if the reader is using the RM Protocol. To enable Scramble Keypad on a reader using the RM
protocol, place the TST-100 Touchscreen Terminal Reader S2-5 switch to the ON position.
Schedule for Select a Schedule from the list to specify when Keypad Commands can be used at this Reader. When the Schedule is active,
Keypad Keypad Commands can be used. When the Schedule is inactive, Keypad Commands cannot be used.
Commands
See Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
For iSTAR Readers you can create Triggers for the properties shown in Table 152 on Page 503.
Table 152: iSTAR Reader Trigger Properties
Property Description
PIN Required Status Possible values are Not Required or Card and PIN Required, based on the setting for PIN Requirements on the
Keypad tab.
Tamper Status Boolean value; True if the Tamper input has been activated, or False if the Tamper Input has not been activated.
Field/Button Description
Communications Communications displays the value Normal if the Controller can communicate with the Reader or Comm Fail if the
Controller cannot communicate with the Reader.
PIN Required PIN Required displays the value True if PIN Required has been selected on the Keypad tab or False otherwise.
Tamper Displays the status of the Tamper Input. Not available on Direct Connect Wiegand readers.
Keypad Command This field displays status of the Keypad Commands Allowed setting from the Reader Editor Keypad tab:
Allow Status • Not Allowed
• Allowed
• Allowed during specified schedule.
Field/Button Description
Communications Communications displays the value Normal if the Controller can communicate with the Reader or Comm Fail if the
Controller cannot communicate with the Reader.
PIN Required PIN Required displays the value True if PIN Required has been selected on the Keypad tab or False otherwise.
Tamper True if a Tamper status is detected for the PIM Reader, or False if no Tamper condition is detected.
Keypad Command This field displays status of the Keypad Commands Allowed setting from the Reader Editor Keypad tab:
Allow Status • Not Allowed
• Allowed
• Allowed during specified schedule.
Field/Button Description
[PIM1-pro 1] - PIM True if a Tamper status is detected for the PIM-485 board to which this reader is attached, or False if no Tamper condition
Tamper is detected.
Motor Stall True if a Motor Stall condition (a problem with the latching mechanism of the door strike) is detected, or False if no Motor
Stall condition is detected.
Available only for PIM-485 WA Series Locks, not for other AD Locks.
Low Battery True if a Low Battery condition is detected for the PIM Reader, or False if no Low Battery condition is detected. Available
only for PIM-485 connected Readers.
Manual Lock True if the Manual Lock Overrride has been activated (unlocked by a physical key), or False if the Manual Lock Override
Override has not been activated. Available only for PIM-485 connected Readers.
Push Button True if the Push Button on the lock panel (inside the room) has been pressed, or False if the Push Button has not been
pressed. Available only for PIM-485 connected Readers.
Field/Button Description
Communications Communications displays the value Normal if the Controller can communicate with the Reader or Comm Fail if the Controller
cannot communicate with the Reader.
Tamper True if a Tamper status is detected for the Reader, or False if no Tamper condition is detected.
Low Battery True if a Low Battery condition is detected for the Reader, or False if no Low Battery condition is detected.
Field/Button Description
Dual Authentication
OSDP Options
Installation Mode Enabled When enabled, allows C•CURE 9000 to communicate securely with a new reader that does not have encryption
keys. The OSDP Secure Channel Enabled check box must be also selected.
• If OSDP Secure Channel Enabled is On (selected) and Installation Mode Enabled is Off (deselected)
and a new reader is presented, it will not communicate with C•CURE 9000.
• If OSDP Secure Channel Enabled is Off (deselected), then communication is always available and the
installation mode is disabled.
• If Installation Mode Enabled is On (selected), then the keys will be exchanged and communication will
begin.
Default: Enabled.
Software House recommends that you disable (clear) this feature for maximum security.
OSDP Secure Channel When enabled, the 485 communication port is encrypted using keys exchanged between the panel and the
Enabled readers. See Installation Mode Enabled.
IMPORTANT:
Enabling or disabling the OSDP Secure Channel requires the reader to be restarted for the changes take
effect. This can be accomplished by power cycling the reader, resetting the ACM, or by resetting the
controller.
Default: Enabled
Beep on Key Press Select this check box for the TS-100 Touchscreen Terminal reader to beep when pressing a key.
Beep on Card Read Select this check box for the TS-100 Touchscreen Terminal reader to beep on a card read.
Date Format Select the date format and/or the time format to use.
Time Format
After-Hours
When configured, the After-Hours Reader feature defines a schedule, an enabling reader, and an iSTAR reader group.
Cardholders with clearance gain access by an enabling door to normally restricted, secure spaces after business hours.
Within this schedule, readers configured as members of an After-Hours Reader Group will reject access to all
cardholders that have not first presented their card to the enabling reader for that particular reader group, even when those
cardholders have valid clearance to member readers. Once a card has been presented and accepted at the enabling
reader, it will then have access to any members of the associated After-Hours group to which it has a valid clearance for
the remainder of the schedule.
The After-Hours feature supersedes clearance restrictions only relative to admission during the schedule. Outside of the
defined schedule, cardholders will have the normally expected access to readers within the After-Hours Reader Group.
Refer to After-Hours Readers Under Offline State Conditions on Page 508 for information regarding After-Hours enabled
readers during offline conditions.
The After-Hours restriction can be overridden for certain cardholders by using the AntiPassback Exempt Flag to indicate
After-Hours Exemption. The AntiPassback Exempt Flag is on the General tab of the Personnel record. Use of the
AntiPassback Exempt Flag to override After-Hours is set in System Variables. Refer to Setting the AntiPassback
Exempt Flag on Page 508 for instructions on setting the AntiPassback Exempt Flag.
For proper functionality, when configuring an After-Hours Reader feature, the After-Hours Reader Group, the enabling reader, and
NOTE the schedule that is assigned to these units must all be configured in the same time zone.
If required, follow the instructions for creating and configuring an After-Hours Schedule as explained in the C•CURE 9000 Software
NOTE Configuration Guide.
Once communication with the host is restored, the panel controlling the enabling reader resumes normal operation.
Field/Button Description
Touchscreen Configuration
Automatic Dim Select the time the LCD display timeouts and goes dark after no motion is detected in front of the reader.
Timeout The default is 2 minutes.
Brightness during Select the percentage of screen brightness when the reader is in use and before the LCD display goes dark due to the
Auto Dim Automatic Dim Timeout.
The default is 0.
Card Types
Lists the supported card types, and allows you to select and reorder the priority of the card type to the card type(s) used.
To reorder the priority:
1. Click on the card type row to select it.
2. Click Up or Down to move the card type to the priority in the list.
High assurance is supported on the iSTAR Ultra, Ultra SE (Ultra Mode), and Ultra LT controllers.
CAK, PIN, and Biometrics are single factor authentications when used alone. Any two together are a double factor
authentication, and all three together are a triple factor authentication.
See Innometriks High Assurance Reader Configuration on Page 480 for configuration information.
iSTAR Reader High Assurance Tab Definitions
Field/Button Description
Support High Assurance Reader When selected (enabled), the High Assurance Operation Modes become available for selection.
Default: Disabled (clear)
Field/Button Description
PAK Physical Access Control System (PAK). Card plus PIN authentication.
NOTE: If you select PAK, Card PIN is automatically selected.
See State Images Tab for iSTAR Devices on Page 281 for information on using the State Images tab for an iSTAR
Reader.
See Table 158 on Page 510 for default State Images for an iSTAR RM reader
See Table 159 on Page 510 for default State Images for an iSTAR PIM-485 reader (Schlage wireless lock and reader).
Unknown Tampered
Comm Fail Motor Stall (Schlage Wireless Only) Manual Lock Override (Schlage Wireless
Only)
Normal
The iSTAR PIM-485 Reader editor dialog box has the following tabs.
■ iSTAR Reader General tab
Lists the Reader name, connections, and card formats for a reader connected to an iSTAR Classic/Pro, or iSTAR eX.
See iSTAR Reader General Tab on Page 498.
■ iSTAR PIM-485 Reader I/O tab
This tab lets you configure the available Inputs and Outputs for the Reader. See the iSTAR PIM-485 Reader I/O Tab
on Page 513.
■ iSTAR Reader Keypad tab
This tab lets you configure the settings and options for the Reader Keypad on iSTAR Schlage Readers. See iSTAR
Reader Keypad Tab on Page 501.
Only Schlage Keypad Mode 1 keypad output format (4 data bits per key with no parity) is supported. The mode is
configured on the Schlage device.
■ iSTAR Reader Triggers tab
See the Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
You can define triggers for the following Properties of the iSTAR PIM-485 Reader:
Property Value
You can add or remove Card Formats from multiple Readers via an iSTAR PIM-485 Reader Dynamic View. See Add or
Remove Reader Card Formats on Page 33 for more information.
You can configure these inputs and outputs by clicking on in the Edit column. You can then create triggers that can
activate Events based on state changes.
Example:
You can create a trigger to activate an Event if the Low Battery Input status changes to Active (indicating that the
reader battery charge is low). See Triggers Tab for iSTAR Devices on Page 278.
Definitions for the fields and buttons on the Reader I/O tab are described in Table 161 on Page 514.
Field/Button Description
Inputs
Create All Inputs Click to create all eight Inputs. The check boxes in the Configured column are set to .
Delete All Inputs Click to delete all eight Inputs. The check boxes in the Configured column are set to .
Edit Click in this column to open the iSTAR Input editor to edit the Input.
Connection This read-only field identifies the position of each Input on the I/O tab.
Name Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to
select an Input Template. If the Configured column displays , this field cannot be edited.
Wireless DSM Represents the Wireless Door Switch Monitor (DSM) for the door.
Wireless REX Represents the Wireless Request To Exit (REX) for the door.
Wireless Reader Represents the Communications Failure Input on the Wireless Reader.
Communications
Fail
Motor Stall Represents the Motor Stall Input on the Wireless Reader.
Low Battery Represents the Low Battery Input on the Wireless Reader.
Manual Lock When this input is active, it indicates that the lock has been unlocked by a physical key.
Override The Manual Lock Override status is available on the Status tab for this reader. This property is available for use in triggers.
Push Button When this input is active, it indicates that the push button on the lock panel (inside the room) has been pushed.
The Push Button Input status is available on the Status tab for this reader. This property is available for use in triggers.
Outputs
Create All Outputs Click to create all Outputs. The check boxes in the Configured column are set to .
Delete All Outputs Click to delete all Outputs. The check boxes in the Configured column are set to .
Door Latch Relay Represents the Door Latch Relay Output that is used to unlock the door.
Edit Click in this column to open the iSTAR Output editor to edit the Output.
Field/Button Description
Connection This read-only field identifies the position of the Output on the I/O tab.
Name Displays the system-generated name for this Output. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Output. If the Output is not yet configured, you can click in this column, then
click to select an Output Template. If the Configured column displays , this field cannot be edited.
When you add an iSTAR Aperio Reader, Enable it in the Aperio Reader editor, and Save and Close the editor, a Door
object for that reader is added to the parent Ultra controller in the iSTAR Aperio Doors folder in the Hardware tree.
If you delete an iSTAR Aperio Reader, the iSTAR Aperio Door associated with the reader is also deleted.
If you display a list of iSTAR Doors, the new Aperio Door appears on the list. See iSTAR Aperio Door Editor on Page 420
for more information on Aperio Doors.
The iSTAR Aperio Reader editor dialog box has the following tabs.
■ iSTAR Reader General tab
Lists the Ultra controller name, Hub board, Assigned to Door, Reader number, Device ID, and Reader type. See
iSTAR Reader General Tab on Page 498.
■ iSTAR Aperio Reader I/O tab
This tab lets you configure the available Inputs and Outputs for the Reader. See the iSTAR Aperio Reader I/O Tab on
Page 518.
■ iSTAR Reader Keypad tab
This tab lets you configure the settings and options for the Reader Keypad on iSTAR Aperio Readers. See
iSTAR Aperio Reader Keypad Tab on Page 277.
■ iSTAR Reader Triggers tab
See the Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR Ultra device.
You can define triggers for the following Properties of the iSTAR Aperio Reader:
Property Value
You can add or remove Card Formats from multiple Readers via an iSTAR Aperio Reader Dynamic View. See Add or
Remove Reader Card Formats on Page 33 for more information.
The number of inputs available on this tab varies, depending upon the reader model configured on the General tab in the
Reader Type field.
When an Aperio reader input is changed from active to inactive while the iSTAR Controller is offline, the
NOTE controller continues to report the input as active when the controller comes back online.
Workaround: Activate and then deactivate the input to synchronize the input with the controller.
You can configure these inputs by clicking on in the Edit column. You can then create triggers that can activate
Events based on state changes.
Example:
You can create a trigger to activate an Event if the Lock Low Battery Input status changes to Active (indicating that
the reader battery charge is low). See Triggers Tab for iSTAR Devices on Page 278.
Definitions for the fields and buttons on the Reader I/O tab are described in Table 162 on Page 518.
Definitions for the input types are described in Table 163 on Page 519.
Table 162: iSTAR Reader I/O Tab Definitions
Field/Button Description
Create All Click to create all Inputs. The check boxes in the Configured column are set to .
Inputs
Delete All Click to delete all Inputs. The check boxes in the Configured column are set to .
Inputs
Edit Click in this column to open the iSTAR Input editor to edit the Input.
Connection This read-only field indicates the three standard inputs (Comm Fail, Low Battery, and Lock State Jammed.
Name Displays the system-generated name for this Input. You can edit this name by clicking in the field.
Template Displays the Template used for creating this Input. If the Input is not yet configured, you can click in this column, then click to select
an Input Template. If the Configured column displays , this field cannot be edited.
Field/Button Description
Lock Reader Tamper Represents the state of the Tamper input on the lock.
Handle State / Request to Exit Represents the state of the Request to Exit input associated with the door handle.
Key Cylinder Override Represents the state of the Key Cylinder Override.
Door Position State Represents state of the Door Switch Monitor for the door associated with this reader.
Lock Communications Fail Represents the Lock Communications Failure Input on the Aperio Reader.
Lock State Jammed Represents the Lock State Jammed Input on the Aperio Reader.
Lock Low Battery Represents the Lock Low Battery Input on the Aperio Reader.
You can add or remove Card Formats from multiple Readers via an apC Reader Dynamic View. See Add or Remove
Reader Card Formats on Page 33 for more information.
You may configure an apC Reader from the apC panel Readers tab or from the Add-on Board tab. A
NOTE reader index configured on one tab will be unavailable on the other tab. The location chosen will affect
the possible reader type and reader input/output option selection.
See the C•CURE 9000 Getting Started Guide - Table 1-5 for a list of UL approved card formats and
readers.
3. Click the applicable row in the Card Format browser to select Card Format. Repeat for multiple formats.
4. Navigate to the Input/Output (I/O) tab (see on Page 521).
You can click Save and Close after configuring apC Reader triggers, or navigate to the Status tab.
To Change an Image
1. Double-click the existing image. A Windows Open dialog box appears allowing you to browse for a folder in which you
have placed replacement images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click on the new image and select Restore Default.
4. Click Save and Close.
This chapter explains how to customize sets of messages, such as “Present Card” or “Access Granted,” for your RM, non-
RM, and OSDP readers to meet the specific needs of your facility or site. It also explains how to customize OSDP reader
LED and beep patterns.
In this chapter
Example:
You could change the “Access Granted” message to “Please Enter Now”.
When you assign a set of messages to an iSTAR Controller or an apC Panel, all those types of readers (RM or OSDP) on
that controller use the same messages.
The Reader LCD Message Set Editor allows you to configure message sets. You can also use the Reader LCD
Message Set Editor to change the language in which your messages appear. See Changing the Language for the Default
LCD Messages on Page 531.
Only ASCII characters 0 to 125 are supported for display on the reader.
NOTE
■ There are 94 printable characters. (Code 1 to 31 are non-printing, mostly obsolete characters that
affect how text is processed.)
■ No accented characters are supported.
Click to open a Dynamic View showing a list of all existing Reader LCD Message Sets, right-click the Reader
LCD Message Set you want to change, and click Edit from the context menu that appears.
The Reader LCD Message Set Editor opens. Figure 149 on Page 527 shows the Reader LCD Message Set Editor,
the default setting.
Click to open a Dynamic View showing a list of all existing Reader LCD Message Sets, right-click the Reader
LCD Message Set you want to change, and click Edit from the context menu.
3. In the Reader Message Set editor, click Support OSDP LED Control to access OSDP readers configurable message
sets and LED control.
Figure 150 on Page 528 shows the OSDP Reader LCD Message Set and LED Control Editor.
See LED Colors, LED Patterns and Beep Patterns on Page 538 for configuration information.
Field/Button Description
Description Enter a brief description for this Reader LCD Message Set.
Partition This read-only field identifies the Partition to which this Reader LCD Message Set belongs. (This field is visible only if the
C•CURE 9000 system is partitioned.)
Display Formats
Date Select the format for the date display: MM/DD/YY (the default) or DD/MM/YY
Time: Hour Clock Select the format for the time display: 12 hour (the default) or 24 hour.
Support OSDP LED Opens the configurable options for message, LED, and Beep Patterns.
Control
Messages
Field/Button Description
Enter PIN ENTER PIN Enter PIN prompt–general use Yes Yes
Enter next card ENTER NEXT Enter next card prompt–used for occupancy and visitor/escort features Yes Yes
CARD
Please wait PLEASE WAIT Text displayed while access decision pending–general use Yes Yes
Wait - busy WAIT - BUSY Text displayed when door busy processing a previous access–general use Yes Yes
Enter floor ENTER FLOOR apC display for elevator admit–general use No Yes
Reader not READER NOT Text displayed when reader disabled–general use Yes Yes
ready READY
Present card PRESENT CARD Locked Door mode text–general use Yes Yes
Enter command ENTER Intrusion entrance delay text–intrusion zone feature Yes No
COMMAND
Misread card MISREAD Visitor/escort misread card feedback text–visitor/escort feature Yes No
All secure ALL SECURE Intrusion zone all inputs secure text–intrusion zone feature Yes No
Exit now EXIT NOW Intrusion exit delay text–intrusion zone feature Yes No
Ready to arm READY TO ARM Intrusion zone ready to arm status text–intrusion zone feature Yes No
Not ready to arm NOT READY TO Intrusion zone not ready to arm status text–intrusion zone feature Yes No
ARM
Door in alert DOOR IN ALERT iSTAR reader tampered text, or apC reader tamper or door held forced Yes Yes
open text–general use
Area armed AREA ARMED Intrusion zone armed mode text–intrusion zone feature Yes No
Area disarmed AREA DISARMED Intrusion zone disarmed mode text–intrusion zone feature Yes No
Secure pending SECURE Intrusion zone disarm pending text–intrusion zone feature Yes No
PENDING
Keypad CMD ISSUED Keypad command issued text–keypad commands feature Yes No
Command
Issued
Keypad CMD FAILED Keypad command failed text–keypad commands feature Yes No
Command
Failed
Keypad ENTER ACCESS Keypad command prompt 1 text–keypad commands feature Yes No
Command
Prompt 1
Keypad ENTER TARGET Keypad command prompt 2 text–keypad commands feature Yes No
Command
Prompt 2
Acknowledged ACKNOWLEDGED Enter next card acknowledgement text–occupancy and visitor/escort Yes No
features
Enter escort ENTER ESCORT Request Escort prompt–occupancy and visitor/escort features Yes No
Secure violated SECURE Intrusion zone armed and violated status text–intrusion zone feature Yes No
VIOLATED
Secure SECURE Intrusion zone armed but not ready to re-arm status text–intrusion zone Yes No
offnormal OFFNORMAL feature
Lockout LOCKOUT & T Area lockout reject & T will be replaced with remaining lockout time Yes No
HHH:MM HHH:MM–area lockout feature
Reject REJECT Occupancy reject indicates that supervisor/escort cannot leave Yes No
unattended UNATTEND supervisees/visitors unattended–occupancy feature
Door held open DOOR HELD iSTAR door held open status text–STAR only (apC displays Door in Alert Yes No
OPEN instead)
Door forced DOOR FORCED iSTAR door forced open status text–iSTAR only (apC displays Door in Alert Yes No
open OPEN instead)
Example:
You chose English as the primary system language and configured all the sets of English messages your Boston site
needs; you may now want to customize some message sets in French for your Montreal site.
The C•CURE 9000Multilingual User Interface (MUI) Editor, available as a licensed option when
NOTE purchasing C•CURE 9000, allows you to localize the C•CURE 9000 user interface for a broad range of
languages and cultures. When installed and enabled, the C•CURE 9000 MUI Editor allows anyone with
appropriate access permissions to localize individual screens and system messages, including the Reader
LCD Message Sets, from within C•CURE 9000 at any time. For information on the MUI Editor see the
chapter, “Displaying the C•CURE 9000 in Multiple Languages” in the C•CURE 9000 System Maintenance
Guide.
In addition, the editor lets you select the way the date and time display on the Reader. The Reader LCD Message Set
Editor has only one tab—the General tab.
■ Assigning New Message Sets and Reassigning Updated Message Sets on Page 534
■ Viewing a List of Reader LCD Message Sets on Page 535
■ Deleting a Reader LCD Message Set on Page 536
■ Using Set Property to Configure Reader LCD Message Set on Page 537
4. Click .
5. Select the message set in the list. Message sets using OSDP control will not appear if the controller does not support
OSDP.
6. Click Save and Close.
2. Select Reader LCD Message Set from the Hardware drop-down list and click to open a Dynamic View
showing a list of all existing Reader LCD Message Sets, as shown in Figure 152 on Page 535. (You can also click the
down-arrow of this button to either view the list in the current tabbed view or open a new tabbed view).
Figure 152: Reader LCD Message Set List
Menu Description
Selection
Edit Click this menu selection to edit the selected Reader LCD Message Set. The Reader LCD Message Set Editor opens. You can
rename the message set and change any of its attributes.
Delete Click this menu selection to delete the selected Reader LCD Message Set. A prompt appears asking you to confirm that you want to
delete the Reader LCD Message Set. Click Yes to delete the Reader LCD Message Set or No to cancel the deletion.
NOTE: You cannot delete a Reader LCD Message Set if it is being used by an iSTAR and/or apC Controller.
Set Click this menu selection to change the value of the selected properties in the selected Reader LCD Message Set(s).
property
A dialog box appears asking you to select a property to change. Click to open a selection list and click the property you wish to
change. You can then change the value of the following property:
• Description – You can change the textual description of the Reader LCD Message Set(s) by selecting this property and typing
in a new value.
Export Click this menu selection to Open an Export...to XML or CSV file dialog box to export one or more of the selected Reader LCD
selection Message Set records to either an XML or a CSV file. This allows you to quickly and easily create XML/CSV reports on the selected
data.
NOTE: Although XML is the initial default file type, once you choose a type in the Save as type field, whether XML or CSV, that
becomes the default the next time this dialog box opens.
CSV-formatted exports cannot be imported. If you require importing functionality, export to XML.
• When you export to an XML file, all available data for the selected object(s), whether displayed in the Dynamic View or not—as
well as all the child objects of the selected record(s), is exported.
• When you export to a CSV file, only data in the columns displaying in the Dynamic View is exported, and in the order displayed.
This allows you to both select and arrange data fields for your report. In addition, exporting to a CSV file allows you to view the
exported data in an Excel spreadsheet and further manipulate it for your use.
For more information, see the Dynamic Views chapter in the C•CURE 9000 Data Views Guide.
NOTE: When you click Export Selection, you are running the export on the client computer. Consequently, the system does not
use the Default Export Directory Path—which is on the server. It opens a directory on the client, reverting to the last directory
used. You can navigate to the default export server directory, if you wish. Or to avoid confusion or use the same destination
folder for both client and server computers, you can use UNC (Universal Naming Convention) paths, for example:
\\Computer Name\
Program Files\Software House\SWHouse\SWHSystem\Export.
Find in Click this menu selection to Open a Query Parameters dialog box in which you can enter prompts and/or modify the Query criteria
Audit Log to search for entries in the Audit Log that reference the selected Reader LCD Message Set. When found the results display in a
separate Dynamic View.
Find in Click this menu selection to Open a Query Parameters dialog box in which you can enter prompts and/or modify the Query criteria
Journal to search for entries in the Journal that reference the selected Reader LCD Message Set. When found the results display in a
separate Dynamic View.
RM and Wiegand readers do NOT support the new colors and patterns.
NOTE
Click the Support OSDP LED Control check box in the Reader LCD Message Set dialog box to access OSDP readers
configurable messages and LED control.
LED colors, LED patterns, and beep patterns are supported with the following messages:
■ Present Card
■ Access granted
■ Access denied
■ Unlocked
■ Secure
■ Door held open
■ Door forced open
The remaining messages can be used, and their text modified. However, customized LED color, LED pattern and beep
pattern are not supported on them in this release.
Limitations
■ Changes to patterns do not take effect until there is a new reader transaction or if the reader is restarted.
■ To utilize the customizable LED/Beep/Message features, the OSDP reader must support the full set of LED/Beep
commands in the OSDP specification.
■ In an OSDP multi-drop environment, use the higher baud rate (38.4K or 115K.) for the customizable LED patterns,
Beep patterns, and LCD message set features.
■ The double-swipe beep configurations supersede all other beep configurations. Avoid using the ninth pattern (400 ms
on/200 off/100 on) and the 10th pattern (100 ms on/200 off/400 on/200 off/100 on/200 off/100 on) if you are using
double-swipe for other purposes.
■ If you are using LED colors, ensure that the reader supports the colors you choose for the configuration. Check the
reader documentation.
■ Occasionally, OSDP readers when configured, not connected to a door, may display unstable LED status information
the first time the reader is powered on. This condition should only last 30 seconds.
■ When the ACM/IP-ACM is busy and/or the Baud rate set on the port is low, LED and beep patterns may not reproduce
perfectly.
■ Setting both the LED and beep to the same pattern will not always synchronize. The buzzer and LED in the OSDP
protocol requires two different protocol messages, and at 9600 baud there is a minimum of 28 ms space between
those, and possibly up to 225 ms between the two requests. When the reader starts the beep pulse and when it starts
the LED flash is based on the reader manufacturer.
■ The double-swipe beep configurations supersede all other beep configurations. Avoid using the ninth pattern (400 ms
on/200 off/100 on) and the 10th pattern (100 ms on/200 off/400 on/200 off/100 on/200 off/100 on) if you are using
double-swipe for other purposes.
■ Some readers do not support the blue LED color. Check the reader manufacturer documentation.
Supported colors accessed from the LED Color (#1, #2) drop-down menu in the Message Name row:
■ Off (dark)
■ Red
■ Green
■ Amber
■ Blue
Ensure that your reader supports the colors you choose for the configuration. Most readers do not support
NOTE the blue LED color.
The LED patterns start with color #1, alternating between color #1 and color #2, if applicable. Table 167 on Page 539
LED color patterns are access from the LED Pattern drop-down menu in the Message Name row.
If either color # is not defined, then the LED for that color # will be off for the specified time.
NOTE
Color #2 X X
1000 ms On Color #1 X X X X X X X X X X
Color #2
Color #2 X X X X
Color #2 X X X X X X X
700 ms On Color #1 X X X X X X X
Color #2
LED #2 X X X
LED #2 X X
Table 168 on Page 541 describes the beep pattern actions for each selection.
100 ms On, Beeps for 100 ms, turns off for 200 ms, beeps for 400 ms, and stops.
200 Off,
400 ON
600 ms On, Beeps for 600 ms, turns off for 400 ms, then repeats the sequence.
400 Off, Repeat
400 ms On, 700 Off, Repeat Beeps for 400 ms, turns off for 700 ms, then repeats the sequence.
400 ms On, 300 Off, Repeat Beeps for 400 ms, turns off for 300 ms, then repeats the sequence.
400 ms On, 200 Off, 100 On Beeps for 400 ms, turns off for 200 ms, beeps for 100 ms, then stops.
100 ms On, 200 Off, 400 On, 200 Off, 100 Beeps for 100 ms, turns off for 200 ms, beeps for 400 ms, turns off for 200 ms, beeps for 100 ms,
On, 200 Off, 100 On turns off for 200 ms, beeps for 100 ms, then stops.
300 ms On, 300 Off, Repeat Beeps for 300 ms ,turns off for 300 ms, then repeats the sequence.
800 ms On, 800 Off, Repeat Beeps for 800 ms, turns off for 800 ms, then repeats the sequence.
500 ms On, 500 Off, Repeat Beeps for 500 ms, turns off for 500 ms, then repeats the sequence.
This chapter explains how to configure Two Factor Authentication in C•CURE 9000.
In this chapter
The two factor authentication feature in your C•CURE 9000 platform is applied through Duo services. This third party
company and its APIs are integrated to provide you with the utmost security from the beginning to the end of access
requests by providing the following services:
• Signals a mobile phone that a new authentication request is pending.
• An application or automated call on the mobile phone that you can use to approve or deny the authentication
request.
There are two ways Duo services perform the second authentication process for two factor authentication:
• When the cardholder swipes at a two factor authentication protected door and enabled reader, they receive a
notification on their mobile phone requesting approval. They can approve or deny the request from the Duo
application.
• If a user does not have the Duo application but has a registered phone, they receive an automated call prompting
them to press a key to approve the request or terminate the call to deny the request.
Prerequisites
The following components are required to apply two factor authentication to your C•CURE 9000 system and security
objects:
• You need to add a license to the server you are using to host the two factor authentication plugin that has:
— Tyco Web Bridge enabled.
— 2-Factor Mobile Authentication per Door Annual Subscription License option enabled.
— The limit you require for the number of personnel that can be enrolled and the number of doors that participate in
the two factor authentication process.
• A valid account with Duo that requires access to both the Auth API and Admin API. The Admin API is not available
unless you request it directly from Duo.
— For more information see Enabling Two Factor Authentication for C•CURE through DUO APIs on Page 545.
When successful, the status of Web Bridge State in and Application Server Dynamic View appears as Connected.
Supporting Hardware
Two factor authentication depends on the firmware version applied to the iSTAR family devices you are using in your
system. Table 169 on Page 545 lists the devices and firmware versions that support the use of the two factor
authentication feature. If the device is not listed, it does not support two factor authentication.
Table 169: Supported Hardware
The Duo service provides documentation that describes the process of adding these applications in Duo at the following
locations:
• For information about getting started with a Duo account, refer to https://duo.com/docs/getting-started.
• For information about the Auth API, refer to https://duo.com/docs/authapi#first-steps.
— When you access the Auth API, you are provided with the Integration Key, Secret Key, and API hostname.
You can use these to securely communicate between the C•CURE host and Duo for the two factor
authentication process.
— In regards to the Username normalization section, you can choose the radio button for Simple. This
provides you with greater flexibility in establsihing how C•CURE personnel maps to a Duo user.
• For information about the Admin API, refer to https://duo.com/docs/adminapi#first-steps.
— When you access the Admin API, you are provided with an Integration Key and Secret Key. These are
different from the Auth API but the API hostname is the same.
— In the Permissions section, you must grant read permissions at a minimum. If your C•CURE host is creating
and removing new users as you enable them for two factor authentication, you must also grant write
permissions. However, if you manage users through another process you can deny write permissions to
guarantee C•CURE cannot alter user information.
The Auth API and Admin API information can be located on C•CURE system here: C:\Program Files (x86)
\Tyco\CrossFire\ServerComponents\ACVS.Enterprise.WebBridge.exe This is an important integration and the
security information in this file should only be accessed by trusted personnel.
For information about configuring personnel for two factor authentication see the C•CURE 9000 Personnel
NOTE Configuration Guide.
When you complete these configurations, two factor authentication is initiated at the reader and the door upon a card
swipe.
You can define a trigger and event to maintain security while communications are being fixed in order to do this.
Configuring fallback when the C-CURE host and two factor authentication provider fail to
communicate
The C-CURE host periodically confirms connectivity to the two factor authentication provider. If communication fails for
any reason the value in the Web Bridge State field of the Application Server Dynamic View does not appear as
Connected and the Web Bridge Connected check box is clear, which means it is false and not connected.
Configuring fallback to one factor authentication when the C-CURE host and two factor authentication provider
fail to communicate
1. Click the Configuration pane and select Event from the drop-down list.
2. Click New to create a new event.
3. In the Event editor, click the Action tab.
4. Click Add to add a row for the action you want to configure.
5. In the Action drop-down list, select Set Clearance Filter to Level <x>, where x is a level below the pre-configured
Clearance Filter Level the reader uses for two factor authentication.
6. In the Reader field, click the ellipsis and select the reader you want to apply this action to if there is communications
loss between C-CURE and the access control panel.
7. Complete any other configuration options in the Event editor you want to pair with this event in the situation it is
triggered. Ensure that you select the Enable and Armed check boxes.
8. Click Save and Close. You have created an event that sets the chosen reader to a lower clearance level. To finalize
this configuration, you must apply this event to the Application Server in case there is a communication failure.
9. Open the editor for your Application Server and click the Triggers tab.
10. In the Property section, select Web Bridge Connected or Web Bridge State. This depends on which field you want
to base this trigger on.
11. In the Value section, select the value you want to use to trigger the event you configured.
• If you choose Web Bridge State you can choose several options such as, but not limited to: Disconnected, An
unexpected error occurred on the connection, or Not Licensed.
• If you choose Web Bridge Connected you can choose the check box value of selected, True, or clear, False.
12. In the Action section, select Activate Event.
13. In the Event field, click the ellipsis and select the event that you configured which lowers the Clearance Filter Level
of the reader.
14. Click Save and Close. The Application Server is now configured to trigger an event that lowers the clearance level of
a reader in case the server has a connection problem.
Configuring fallback to one factor authentication when the C•CURE host and the access control panel fail to
communicate
1. Click the Configuration pane and select Event from the drop-down list.
2. Click New to create a new event.
3. In the Event editor, click the Action tab.
4. Click Add to add a row for the action you want to configure.
5. In the Action drop-down list, select Set Clearance Filter to Level <x>, where x is a level below the preconfigured
Clearance Filter Level the reader uses for two factor authentication.
6. In the Reader field, click the ellipsis and select the reader you want to apply this action to if there is a communication
loss between C-CURE and the access control panel.
7. Complete any other configuration options in the Event editor you want to pair with this event in the situation it is
triggered. Ensure that you select the Enable and Armed check boxes.
8. Click Save and Close. You have created an event that sets the chosen reader to a lower clearance level. To finalize
this configuration, you must apply this event to the access control panel in the case there is communication failure.
9. Open the editor for your access control panel cluster and click the Triggers tab.
10. Click Add to add a row to the Triggers section.
11. In the Property section, select Primary Communication Status.
12. In the Value section, select Offline.
13. In the Action section, select Activate Event.
14. In the Event field, click the ellipsis and select the event that you configured which lowers the Clearance Filter Level
of the reader.
15. Click Save and Close. The access control panel is now configured to trigger an event that lowers the clearance level
of a reader in case the panel has an offline status.
Valid Less than the reader Two factor authentication • The request is approved and the door is
request initiated. used.
• The request is approved but the door is
not used.
• The request is denied. The door is never
unlocked.
• The user is not enrolled with Duo and two
factor authentication. The door is never
unlocked.
In this chapter
A cardholder is given access to an elevator by assigning a Personnel Clearance that includes the Elevator to the
cardholder.
Outputs are used to control the elevator buttons. When the Output is energized, the button for a floor in the Elevator
becomes available for use.
Inputs can be configured to determine at which floor the cardholder exited. When the Elevator door opens at a Floor, an
Input state change indicates that the door has opened.
Elevators or elevator groups are configured through the use of buttons that represent floors with inputs and outputs. You
can then add elevators to clearances that are used to control which cardholders can access the elevators and floors and at
what times.
Elevators are associated with the time zone that is used by the elevator’s inputs, outputs, and readers.
NOTE
Elevator controls and Clearances for Elevators have not been evaluated by UL, and cannot be used in UL
NOTE Listed applications.
Elevator Tasks
You can perform the following general tasks to configure iSTAR and apC Elevators.
■ Creating an Elevator on Page 553
■ Creating an Elevator Template on Page 553
■ Deleting an Elevator on Page 554
■ Modifying an Elevator on Page 554
■ Viewing a List of Elevators on Page 554
■ Using Set Property for Elevators on Page 555
■ Adding Elevators to a Group on Page 555
Creating an Elevator
You can create a new Elevator.
To Create an Elevator
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Select Elevator from the Hardware pane drop-down list.
3. Right-click the Elevator folder and select New to create a new Elevator. The Elevator Editor opens and you can
configure the Elevator.
4. Type an identification for the Elevator in the Name and Description entry fields.
5. To save your new Elevator, click Save and Close.
Alternatively, if you want to save the Elevator and then create a new one, click Save and New. The current Elevator is
saved and closed, but the Elevator Editor remains open to allow you to create a new Elevator.
Deleting an Elevator
You can delete an existing Elevator.
To Delete an Elevator
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Select Elevator from the Hardware pane drop-down list.
Modifying an Elevator
You can edit an Elevator to modify its buttons (Floors and Outputs) and state images.
To Edit an Elevator
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Select Elevator from the Hardware pane drop-down list.
You can right-click the column header to add columns—Enabled, Controller, Comm Status, and so forth.
NOTE
If you right-click a row in the Elevator Dynamic View, a context menu is displayed. This menu contains a number of
standard selections, as well as selections that are specific for elevators.
See Using the Object List Context Menu in the C•CURE 9000 Getting Started Guide for more information about the
object context menu.
Example:
To change the setting for Send to Monitoring Station for 10 specific Elevators, display a Dynamic View of Elevators
(see Viewing a List of Elevators on Page 554), the use multiple selection (typically SHIFT+LEFT-CLICK to select a
range or CTRL+LEFT-CLICK to select multiple items) to select the 10 Elevators, then right-click to display the context
menu. Choose Set Property from the context menu, then click to see a list of Elevator properties. Select Send to
Monitoring Station, then select or for the Value setting. When you click OK the property will be set for these
elevators.
iSTAR Elevators
A cluster of iSTAR controllers can be used to manage elevator access. A cluster consists of a system of one or more
iSTAR controllers which determine communications between individual controllers. Each cluster is configured for either
iSTAR Classic/Pro or iSTAR eX controllers. For more information see Configuring iSTAR Clusters on Page 91.
After configuring the parent objects, iSTAR Clusters and Controllers, iSTAR Elevators require floors, iSTAR Readers,
Inputs, Outputs and Doors. The iSTAR Inputs are used to determine at which floor the cardholder exited and the iSTAR
Outputs are used to control the elevator buttons, which are set in the Buttons tab. These dependent objects must be set up
before you can configure an iSTAR Elevator. For more information, see the references listed below.
1. Cluster and Controller - for more information see:
■ iSTAR Cluster Editor on Page 95
■ iSTAR Controller Editor on Page 145
2. Floor - for more information see:
■ Floors Overview on Page 370
■ Configuring a Floor for an iSTAR Elevator on Page 557
3. Boards with Readers, Inputs, Outputs - for more information see:
■ iSTAR Controller Boards Tab (iSTAR Classic/Pro) on Page 167
■ iSTAR eX and iSTAR Edge Configuration Summary on Page 122
Once these parent and dependent objects are created, you can continue the elevator configuration process:
1. Elevator name (for more information see iSTAR Elevator General Tab on Page 558).
2. Elevator Buttons (for more information see iSTAR Elevator Buttons Tab on Page 562).
3. Elevator Triggers (see iSTAR Elevator Triggers Tab on Page 564
4. Groups tab (see Groups Tab for Hardware Devices on Page 36).
When you add a floor to a group, the Groups tab will be displayed with the Floor - General tab.
4. Click Save and Close. The new floor name displays below the Floors folder in the Hardware tree.
Continue this creation process until your facility’s floors, which you want to access via an elevator, have been
assigned to a C•CURE 9000 Floor object.
The next task that must be completed before you can configure an iSTAR Elevator is to complete the configuration of
an iSTAR Cluster, Controller(s), Readers, Inputs, Outputs and Doors. For more information, see the references listed
above.
4. If you have configured Elevators, double-click the Elevator listing for the selected controller to open a Dynamic View
showing all existing Elevator objects (see Figure 154 on Page 559).
5. Double-click the Elevator in the list that you want to edit, and the Elevator - General tab opens, shown in Figure 155
on Page 560.
Figure 154: Hardware Pane Elevator Selection
To Configure Elevators
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Right-click the Elevators folder in the Hardware tree and select New to create a new Elevator. The Elevator -
General tab, shown in Figure 155 on Page 560 opens.
3. Enter a Name and description (for example, its location or function) for the elevator.
4. Select Enabled to put the Elevator online once you click Save and Close.
The iSTAR Controller is displayed within the Location box.
5. Click to select a Reader in the Location area. The Reader list shown in the Reader browser is restricted to
unassigned readers on the parent Controller.
6. Choose an Elevator Floor Selection Mode for the elevator from the listed options. The possible choices include:
• No Input
• Single Input
• Multiple Inputs
7. If you choose the Single Input option, click the browse button to select an Input from the Input browser (see
Figure 156 on Page 561).
4. Click within the Outputs column to display and select an Output from the Outputs browser, shown in Figure 159
on Page 563, that you want to associate with the iSTAR Elevator.
5. Continue to add Floors and Outputs until you have finished creating Elevator Buttons for each floor that you want to
manage with the iSTAR Elevator.
6. Navigate to the Status tab or click Save and Close.
See iSTAR Elevator Status Tab Definitions on Page 568 for descriptions of the fields on this tab.
See Triggers Tab for iSTAR Devices on Page 278 for information on creating Triggers for an iSTAR device.
See iSTAR Elevator Triggers Tab Definitions on Page 568 for descriptions of the fields on this tab.
4. Click Save and Close to finish the iSTAR Elevator configuration and return to the Hardware Pane.
Field/Button Description
Identification
Field/Button Description
Maintenance Click to put the elevator into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Mode
Enabled Select this check box to put the elevator online. For an elevator to be put online, it must selected.
Location
No Input Click on No Input to indicate that no inputs are connected to the elevator buttons. However, the system cannot tell if a person
presses a floor button after being granted access.
Single Input Click on Single Input to indicate that one input is connected to all buttons on this elevator.
Click and select an Input from the Input list that displays.
When a person presses an elevator button, the system detects an elevator button has been pressed, but cannot determine
which button.
Multiple Inputs Click on Multiple Inputs to indicate that multiple inputs are associated with this elevator. Each elevator button will be connected
to a different input. Select the inputs by clicking Elevator Buttons to open the Elevator Buttons dialog box.
When a person presses an elevator button, the system determines which button the person pressed.
Field Description
Add Fields are added to Elevator Button Components by clicking Add, which adds an empty row to the grid.
Remove
Click the row selector , then click Remove to delete a trigger.
Field Description
Floors This displays a list of available floors for the elevator. Use Add to add a floor to the list and click to display the Floor selection
browser.
Outputs This displays a list of available Outputs for the elevator. Click to select an Output from the Output selection browser.
Field/Button Description
Field Description
Add Fields are added to Elevator Button Components by clicking Add, which adds an empty row to the grid.
Remove
Click the row selector , then click Remove to delete a trigger.
Property Click within the Property column to display browse button. When you click this button, the Property browser opens, presenting
properties available for the controller. Click a Property to select it and add it to the column.
Value Click within the Value column to display a drop-down list of Values associated with the Property that you have selected. Click on a
Value that you want to include as a parameter for the trigger to add it to the column.
Action Click within the Action column to display a drop-down list of valid actions. Click on an Action that you want to include as a parameter for
the trigger to add it to the column.
When a Trigger is added, an Action must be configured in the Action column. This is the Action that will occur when the object’s
selected Property receives the selected Value. As the Action is selected, the lower pane in the Triggers box will show a corresponding
entry field, or group of entry fields, specific to the selected Action. Click the browse button to select entries for these fields. Once
the field (or group of fields) is completed, the Details column will show information about how the Action was configured.
Details The Details column displays information about how the Action was configured. This field is read-only.
Schedule Click within the Schedule column, then click to select a Schedule that you want to associate with the trigger. Schedules are
created in the Configuration Pane.
Property Description
Admit Status For any one of the Admit Status values (see the Value column drop-down list) you can choose one of the following Actions to
Values are: create a Trigger:
- Admit Activate Event – When this status occurs and the Schedule is Active (you can choose any Schedule).
- Reject Activate Event Outside Schedule – An event is activated when this status occurs while the Schedule is Inactive (choose
any Schedule).
- Duress
Activate Output – When this status occurs (only works with the Always Schedule).
- Noticed
Admit Only these three Actions are supported for Admit Status.
- Noticed
Reject
Comm Status 1. Choose a value for the Property from the Value column.
Values are: 2. Select an Action from the Action drop-down list:
- Normal See Table 175 on Page 569.
- Comm For example, if you chose Comm Fail as a Comm State Status for which you want to define an action, you could then select
Fail Activate Event if you wanted to send a command to a CCTV Switch, then in Details, select the Event that you wanted to
activate when a Comm Fail status occurs.
Tamper
Status
Values are:
Action Description
Activate Event Outside Schedule Select an Event to activate when this status occurs while the Schedule is inactive.
Activate Output Select an Output to activate when this status occurs. Must use the Always Schedule.
Field/Button Description
Unknown
Field/Button Description
Active
Comm Fail
Tampered
apC Elevators
This section illustrates the configuration process for the apC - controlled elevator. The advanced processing Controller
(apC), apC/8X, and apC/L are access control field panels that coordinate communication between the C•CURE 9000
server and the system security hardware.
The function of these tabs is covered in the description of configuring the apC Elevator in the following sections. To
configure an elevator controlled by a reader on an apC panel, you must first create and configure the following objects:
1. Floor (for more information see Floors Overview on Page 370)
2. apC panel(s) (for more information see apC Panel Overview on Page 308)
3. Readers, Inputs, Outputs
Once these parent and dependent objects are created, you can continue the elevator configuration process:
1. Elevator name (for more information see apC Elevator General Tab on Page 572)
2. Elevator Buttons (for more information see apC Elevator Buttons Tab on Page 574)
3. Personnel Clearance for cardholders who will use the Elevator (for more information see the C•CURE 9000 Personnel
Configuration Guide).
4. Groups tab (see Groups Tab for Hardware Devices on Page 36).
2. Click Save and Close. The new floor name displays below the Floors folder in the Hardware tree.
Continue this creation process until your facility’s floors, which you want to access via an elevator, have been
assigned to a C•CURE 9000 Floor object.
To Configure Elevators
1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane.
2. Right-click the Elevators folder in the Hardware tree and select New to create a new Elevator. The Elevator -
General tab, shown in Figure 165 on Page 574 opens.
3. Enter a Name and description (for example, its location or function) for the elevator.
4. Select Enabled to put the Elevator online once you click Save and Close.
The apC panel name is displayed within the Location box.
5. Click to select a Reader in the Location area. The Reader list shown in the Reader browser is restricted to
unassigned readers on the parent Controller.
6. Choose an Elevator Floor Selection Mode for the elevator from the listed options. The possible choices include:
• No Input
• Single Input
• Multiple Inputs
7. If you choose the Single Input option, click the browse button to select an Input from the Input browser.
8. Enter a Button Activation Time in seconds.
9. Navigate to the Buttons tab or click Save and Close.
3. Click within the Floors column to display and select a Floor from the Floor browser, shown in Figure 166 on Page
575, that you want to associate with the apC Elevator.
Figure 166: apC Elevator Buttons Tab Floor Selection
4. Click within the Outputs column to display and select an Output from the Outputs browser, shown in Figure 167
on Page 576, that you want to associate with the apC Elevator.
5. Continue to add Floors and Outputs until you have finished creating Elevator Buttons for each floor that you want to
manage with the apC Elevator.
6. Navigate to the Status tab or click Save and Close.
You can click Save and Close after configuring apC Elevator triggers, or navigate to the Status tab.
To Change an Image
1. Double-click the existing image.
A Windows Open dialog box appears allowing you to browse for a folder in which you have placed replacement
images.
2. When you locate the replacement image, select it to add it to the image listing.
3. To restore the default image, right-click on the new image and select Restore Default.
Figure 169: apC Elevator - State Images Tab
4. Click Save and Close to finish the apC Elevator configuration and return to the Hardware Pane.
Field/Button Description
Identification
Field/Button Description
Enabled Select this check box to put the elevator online. For an elevator to be put online, it must selected.
Maintenance Mode Click to put the apC Elevator into Maintenance Mode. See Chapter 3: Maintenance Mode for more information.
Partition This read-only label shows what partition the elevator is in. If the system is not partitioned, the label indicates that the
elevator is in the “Default” partition.
Location
No Input Select this option when no inputs are needed for the apC Elevator.
Multiple Inputs Select this option when more than one input is needed for the apC Elevator.
Button Activation Time Enter the interval at which the apC Elevator button activates.
(seconds)
Field Description
Add Fields are added to Elevator Button Components by clicking Add, which adds an empty row to the grid.
Remove
Click the row selector , then click Remove to delete a trigger.
Field Description
Property Click within the Property column to display a button. When you click this button, the Property browser opens, presenting
properties available for the controller. Click a Property to select it and add it to the column.
Value Click within the Value column to display a drop-down list of Values associated with the Property that you have selected. Click on a
Value that you want to include as a parameter for the trigger to add it to the column.
Action Click within the Action column to display a drop-down list of valid actions. Click on an Action that you want to include as a parameter for
the trigger to add it to the column.
When a Trigger is added, an Action must be configured in the Action column. This is the Action that will occur when the object’s
selected Property receives the selected Value. As the Action is selected, the lower pane in the Triggers box will show a corresponding
entry field, or group of entry fields, specific to the selected Action. Click to select entries for these fields. Once the field (or group of
fields) is completed, the Details column will show information about how the Action was configured.
Details The Details column displays information about how the Action was configured. This field is read-only.
Schedule Click within the Schedule column, then click the browse button to select a Schedule that you want to associate with the trigger.
Schedules are created in the Configuration Pane.
Property Description
Admit Status For any one of the Admit Status values (see the Value column drop-down list) you can choose one of the following Actions to
Values are: create a Trigger:
Admit Activate Event - When this status occurs and the Schedule is Active (you can choose any Schedule).
Reject Activate Event Outside Schedule - An event is activated when this status occurs while the Schedule is Inactive (choose
any Schedule).
Admit
Duress Activate Output - When this status occurs (only works with the Always Schedule).
Reject Only these three Actions are supported for Admit Status.
Duress
Noticed
Admit
Noticed
Reject
Field/Button Description
Unknown
Field/Button Description
Active
Comm Fail
Tampered