c•cure 800/8000 hardware configuration guide

6 Technology Park DriveWestford, MA 01886http://www.swhouse.comFax: 878-577-4392 Phone: 978-577-4000

C•CURE 800/8000Version 10.3

Hardware Configuration Guide

REVISION H0

http://www.swhouse.com

C•CURE and Software House are registered trademarks of Tyco International Ltd. and its respective companies.

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 Tyco International Ltd. 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 Tyco International Ltd. 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.

C•CURE 800/8000 Version: 10.3Document Number: UM-112Revision: H0Release Date: July 2012

This manual is proprietary information of Software House. 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. Software House assumes no responsibility for incorrect information this manual may contain.

Copyright © 2012 Tyco International Ltd. and its respective companies.

All rights reserved.

C•CURE 800/8000 Hardware Configuration Guide iii

Table of Contents

Preface

How to Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Finding More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Software House Customer Support Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Chapter 1 Configuring C•CURE iSTAR Pro/Classic Controllers and Clusters

Understanding C•CURE iSTAR Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Network, Dialup, and Serial Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Cluster Configuration and Distributed Management . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Firmware Upgradable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Seamless Integration with Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Access Control Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

ACM8W. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Connecting Security Devices to the ACM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Optional Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Networked iSTAR Controllers (Clusters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Master and Cluster Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6The Primary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6The Secondary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Distributed Cluster Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9System Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Global Antipassback Control by Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Configuration Overview for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . . 1-11

Table of Contents

iv C•CURE 800/8000 Hardware Configuration Guide

Configuring iSTAR Classic & iSTAR Pro Controllers . . . . . . . . . . . . . . . . . . . . . 1-12

Configuring Holiday Lists for a Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

Main Board Tab for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

Configuring the Main Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21

ACM and ACM Ext Tabs for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . 1-25

Configuring ACMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25Configuring I/8 - Input Modules for iSTAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28R/8 - Output Modules for Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31

Cluster Communications Overview for iSTAR Classic & Pro . . . . . . . . . . . . . . 1-33

Establishing Connections Via the Primary Communications Path . . . . . . . . . . . . . . 1-33Setting Up the Primary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34Downloading Cardholder and Configuration Information . . . . . . . . . . . . . . . . . . . . 1-34Maintaining Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35Establishing a Secondary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35

Maintaining Cluster Communications for iSTAR Classic & Pro . . . . . . . . . . . . 1-37

Losing a Connection with the Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37Secondary Connection Between the Master and Host . . . . . . . . . . . . . . . . . . . . . 1-37Connection Between an Alternate Master and the Host . . . . . . . . . . . . . . . . . . . 1-39

Configuring Clusters for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . . . . . 1-42

Primary Tab for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47

Configuring the Primary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47

Secondary Tab for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51

Configuring the Secondary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51

Cluster Tab for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55

Configuring Communications with the Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55

Misc Tab for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

Configuring the Secondary Communications Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58

Global APB Tab for iSTAR Classic & iSTAR Pro . . . . . . . . . . . . . . . . . . . . . . . . . 1-60

Configuring Antipassback for the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60

Table of Contents

C•CURE 800/8000 Hardware Configuration Guide v

Chapter 2 Configuring C•CURE iSTAR eX Controllers and Clusters

Understanding C•CURE iSTAR Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

ISTAR eX Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2GCM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2PMB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

GCM Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Dual Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Cluster Configuration and Distributed Management . . . . . . . . . . . . . . . . . . . . . . 2-3Firmware Upgradable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Seamless Integration with Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Connecting Security Devices to the iSTAR eX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Relay Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5OC Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Optional Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5


Distributed Cluster Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9System Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Global Antipassback Control by Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Configuring iSTAR eX Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11


Main Board Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Configuring the Main Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Special Purpose Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Options Common to the Entire Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19General Purpose Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Onboard Wiegand Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Relay Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Open Collector Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Table of Contents

vi C•CURE 800/8000 Hardware Configuration Guide

Serial Ports Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Configuring the Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Cluster Communications Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Establishing Connections Via the Primary Communications Path . . . . . . . . . . . . . . 2-29Setting Up the Primary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29

Downloading Cardholder and Configuration Information . . . . . . . . . . . . . . . . . . . . 2-30Maintaining Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Establishing a Secondary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Maintaining Cluster Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33


Configuring Clusters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Primary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40


Secondary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44


Cluster Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48


Misc Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51


Global APB Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53


Encryption Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55

Configuring Encryption for the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55

Chapter 3 Configuring C•CURE iSTAR Edge Controllers and Clusters

Understanding C•CURE iSTAR Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

iSTAR Edge Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Cluster Configuration and Distributed Management . . . . . . . . . . . . . . . . . . . . . . 3-3Firmware Upgradable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Seamless Integration with Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Table of Contents

C•CURE 800/8000 Hardware Configuration Guide vii

Connecting Security Devices to the iSTAR Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Relay Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Optional Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6


Distributed Cluster Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10System Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Global Antipassback Control by Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Configuring iSTAR Edge Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12


Main Board Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

Special Purpose Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20FAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Options Common to the Entire Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22General Purpose Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Onboard Wiegand Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Relay Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Main Board Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Serial Ports Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

Configuring the Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

Cluster Communications Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

Establishing Connections Via the Primary Communications Path . . . . . . . . . . . . . . 3-32Setting Up the Primary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

Downloading Cardholder and Configuration Information . . . . . . . . . . . . . . . . . . . . 3-33Maintaining Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34Establishing a Secondary Communications Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

Maintaining Cluster Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36


Table of Contents

viii C•CURE 800/8000 Hardware Configuration Guide

Configuring Clusters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Primary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43


Secondary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47


Cluster Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51


Misc Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54


Global APB Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56


Encryption Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

Configuring Encryption for the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

Chapter 4 Configuring Advanced Processing Panels (apC, apC/8X, apC/L)

Panel Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Inputs and Alarm Device States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Optional Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Configuring Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Configuring Security Objects on Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Configuring Panel Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Configuring Holiday Lists for a Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Viewing the Intrusion Zones on Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

Chapter 5 Configuring Readers, RM Reader LCD Messages, and Card Formats

Configuring Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Configuring Reader Keypad Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Configuring Advanced Options for Readers on Controllers . . . . . . . . . . . . . . . 5-10

Configuring Advanced Options for Readers on apCs . . . . . . . . . . . . . . . . . . . . . 5-13

Table of Contents

C•CURE 800/8000 Hardware Configuration Guide ix

Configuring RM Reader LCD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Changing the Language for the Default RM LCD Messages . . . . . . . . . . . . . . . . . . . 5-23

Configuring Card Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

Defining Field Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27

Chapter 6 Configuring Inputs and Outputs

Inputs Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Configuring Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Input Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Viewing Input Linkages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Configuring Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

Viewing Output Linkages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16

Tamper and AC Power Failure Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Chapter 7 Configuring Add-on Boards for apCs and iSTARs

Configuring Add-On Boards for apCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

I/32 System Input Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

R/48 System Output Boards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Star Couplers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Mini-Star Coupler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Wiegand/Proximity Star Coupler (WPSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

I/8 — Input Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

R/8 — Output Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19

Chapter 8 Configuring Ports

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Configuring COM Ports from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Configuring RS-232 serial COMM ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Configuring Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

apC Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6iSTAR Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Table of Contents

x C•CURE 800/8000 Hardware Configuration Guide

Configuring Ports from C•CURE 800/8000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

Chapter 9 Configuring and Selecting Host Modems for apC Panels and iSTAR Controllers and Clusters

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Host Modems for apCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Host Modems for iSTARs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Configuring Host Modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Adding Phone Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Modifying Phone Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

Configuring Advanced Options for Non-OEM Host Modems . . . . . . . . . . . . . . 9-8

Selecting Host Modems for Dial In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Selecting Host Modems for Dial Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

Chapter 10 Configuring Dialup for apC Panels

apC Dialup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

How Dialup Panels Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Dialing Out to Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3Dialing Into the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

apC Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4apC Dialup Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Configuring apC Dialup Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Configuring Options for apC Dial-up Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10

Configuring Dial In Options for Dialup Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11Configuring Dial Out Options for Host and Panels . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13Configuring Periodic Dial Out Options for Host and Panels . . . . . . . . . . . . . . . . . . 10-15Configuring Modem Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17

Chapter 11 Configuring Dialup for iSTAR Pro Controllers and Clusters

iSTAR Dialup Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

How Dialup Controllers Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2Dialing Out to Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5Dialing Into the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Table of Contents

C•CURE 800/8000 Hardware Configuration Guide xi

iSTAR Pro Dialup Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Configuring iSTAR Clusters for Dialup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8

Configuring Dialup Options for iSTAR Clusters . . . . . . . . . . . . . . . . . . . . . . . . 11-12

Configuring Dial In Options for Dialup Controllers . . . . . . . . . . . . . . . . . . . . . . . . . 11-13Configuring Dial Out Options for Host and Controller . . . . . . . . . . . . . . . . . . . . . . 11-15Configuring Periodic Dial In Options for Controller and Host . . . . . . . . . . . . . . . . 11-17

Appendix A Card Formats Primer

Card Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Card Format Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Sample Card Format for Mag14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Magnetic Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

Wiegand Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Proximity Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Encrypted Magnetic Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

Offset Values for Card Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Offset Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10

Index

Table of Contents

xii C•CURE 800/8000 Hardware Configuration Guide

C•CURE 800/8000 Hardware Configuration Guide xiii

Preface

This C•CURE 800/8000 Hardware Configuration Guide is for new and experienced security system users. The manual describes the software features on the C•CURE 800/8000 Administration application Configure menu and the configuration procedures.

The manual assumes that you have read the installation procedures described in the C•CURE 800/8000 Installation Guide, installed C•CURE 800/8000, and have familiarized yourself with the basic C•CURE 800/8000 information provided in the C•CURE 800/8000 Getting Started Guide.

In this preface:

How to Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Finding More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Software House Customer Support Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Preface

xiv C•CURE 800/8000 Hardware Configuration Guide

How to Use this Manual

This manual is divided into the following sections:

Chapter 1, “Configuring C•CURE iSTAR Pro/Classic Controllers and Clusters”

This chapter describes how you configure the iSTAR Pro and Classic controller software components to work with C•CURE 800/8000. Controllers are organized into groups called Clusters that allow network communications. This chapter also describes how you configure iSTAR Clusters. For information on installing and configuring hardware for the controller, see the C•CURE iSTAR Hardware Installation Guide.

Chapter 2, “Configuring C•CURE iSTAR eX Controllers and Clusters”

This chapter describes how you configure the iSTAR eX controller software components to work with C•CURE 800/8000. Controllers are organized into groups called Clusters that allow network communications. This chapter also describes how you configure iSTAR Clusters. For information on installing and configuring hardware for the controller, see the C•CURE 800/8000 iSTAR eX Installation and Configuration Guide.

Chapter 3, “Configuring C•CURE iSTAR Edge Controllers and Clusters”

This chapter describes how you configure the iSTAR Edge controller software components to work with C•CURE 800/8000. Controllers are organized into groups called Clusters that allow network communications. This chapter also describes how you configure iSTAR Clusters. For information on installing and configuring hardware for the controller, see the C•CURE 800/8000 iSTAR Edge Installation and Configuration Guide.

Chapter 4, “Configuring Advanced Processing Panels (apC, apC/8X, apC/L)”

This chapter describes how you use the C•CURE 800/8000 software to configure a panel (apC, apC/8X, or apC/L). For information on setting switches or physically changing the panel, see the apC Technical Manual, apC/8X Technical Manual.

Preface

C•CURE 800/8000 Hardware Configuration Guide xv

Chapter 5, “Configuring Readers, RM Reader LCD Messages, and Card Formats”

This chapter describes how you define the readers you want to attach to the main apC panel or the iSTAR controller, how you customize sets of LCD messages, such as “Present Card” or “Access Granted,” for RM readers to meet the specific needs of your facility or site, and how you configure different card formats for your panels.

Chapter 6, “Configuring Inputs and Outputs”

This chapter describes how you configure inputs and outputs on the main panel.

Chapter 7, “Configuring Add-on Boards for apCs and iSTARs”

This chapter describes how you configure different add-on boards for apC panels.

Chapter 8, “Configuring Ports”

This chapter explains how you configure the following

COM ports (serial ports on your PC) so that you can communicate with devices, such as panels, controllers, modems, and switchers.

Network ports

Chapter 9, “Configuring and Selecting Host Modems for apC Panels and iSTAR Controllers and Clusters”

This chapter explains how to configure and select host modems for dialup for both apC panels and iSTAR controllers/clusters.

Preface

xvi C•CURE 800/8000 Hardware Configuration Guide

Chapter 10, “Configuring Dialup for apC Panels”

This chapter describes how you configure dialup for remotely located apCs, apC/8Xs, and apC/Ls that communicate with the C•CURE 800/8000 host via telephone lines and modems.For information on setting switches or physically changing the panel, see the apC Technical Manual or the apC/8X Technical Manual.

Chapter 11, “Configuring Dialup for iSTAR Pro Controllers and Clusters”

This chapter describes how you configure dialup for iSTAR controllers and clusters. For information on installing and configuring hardware for the controller, see the C•CURE 800/8000 iSTAR Configuration Guide.

Appendix A, “Card Formats Primer”

This appendix provides a description of the magnetic, Wiegand, proximity, and encrypted magnetic card formats. You can define three card formats per reader. This appendix briefly describes magnetic, Wiegand, proximity cards, encrypted magnetic, and offset values for card numbers.

Preface

C•CURE 800/8000 Hardware Configuration Guide xvii

Conventions

This manual uses the following text formats and symbols.

The following items are used to indicate important information.

Table 1:

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 your keyboard to press

A screen element or name

Regular italic font Indicates a new term, or a book title.

<text> Indicates a variable.

NOTE Indicates a note. Notes call attention to any item of information that may be of special importance.

TIP Indicates an alternate method of performing a task.

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.

Preface

xviii C•CURE 800/8000 Hardware Configuration Guide

Finding More Information

You can access the guides that are online from the C•CURE 800/8000 Help menu after you copy the appropriate PDF files from the C•CURE 800/8000 DVD. See the C•CURE 800/8000 Installation Guide for more information.

You can access C•CURE 800/8000 Help by pressing F1 or clicking Help from the menu bar in the Administration/Monitoring Station application.

Preface

C•CURE 800/8000 Hardware Configuration Guide xix

Software House Customer Support Center

Telephone Technical Support

During the period of the Agreement, the following guidelines apply:

Software House accepts service calls only from employees of the Systems Integrator of Record for the installation associated with the support inquiry.

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.

Table 0-1:

Hours Normal Support Hours Monday through Friday, 8:00 a.m. to 8:00 p.m., EST. Except holidays.

Emergency Support Hours 24 hours/day, seven days a week, 365 days/year.

Requires Enhanced SSA “7 x 24” Standby Telephone Support (emergency) provided to Certified Technicians.

For all other customers, billable on time and materials basis.Minimum charges apply – See MSRP.

Phone U.S.Puerto RicoU.S. Virgin Islands

+1-800-392-2873

For other regions, see www.swhouse.com/support/contact_technical_support.aspx.

www.swhouse.com/support/contact_technical_support.aspx

Preface

xx C•CURE 800/8000 Hardware Configuration Guide

C•CURE 800/8000 Hardware Configuration Guide 1–1

1

Configuring C•CUREiSTAR Pro/Classic

Controllers andClusters

The C•CURE iSTAR controller is an intelligent controller for networked security systems. C•CURE iSTAR controllers communicate with the C•CURE system server (acting as a database and journal host) and the system security hardware, providing direct control of events and system activity. Controllers are organized into groups called Clusters that allow network communications. This chapter explains how to configure the iSTAR Controllers and Clusters in the C•CURE System. To install and configure hardware for iSTAR controllers and clusters, consult the iSTAR Pro Installation and Configuration Guide.

In this chapter

Understanding C•CURE iSTAR Controllers .............................................................. 1-2

Configuration Overview for iSTAR Classic & iSTAR Pro ...................................... 1-11

Configuring iSTAR Classic & iSTAR Pro Controllers ............................................. 1-12

Main Board Tab for iSTAR Classic & iSTAR Pro ..................................................... 1-21

ACM and ACM Ext Tabs for iSTAR Classic & iSTAR Pro ..................................... 1-25

Cluster Communications Overview for iSTAR Classic & Pro ............................... 1-33

Maintaining Cluster Communications for iSTAR Classic & Pro ........................... 1-37

Configuring Clusters for iSTAR Classic & iSTAR Pro ............................................ 1-42

Primary Tab for iSTAR Classic & iSTAR Pro............................................................ 1-47

Understanding C•CURE iSTAR Controllers

1–2 C•CURE 800/8000 Hardware Configuration Guide

Secondary Tab for iSTAR Classic & iSTAR Pro........................................................ 1-51

Cluster Tab for iSTAR Classic & iSTAR Pro ............................................................. 1-55

Misc Tab for iSTAR Classic & iSTAR Pro.................................................................. 1-58

Global APB Tab for iSTAR Classic & iSTAR Pro ..................................................... 1-60


The iSTAR controller is an intelligent, network-ready controller for security systems. The heart of the iSTAR controller is the General Controller Module (GCM) - an embedded microprocessor-based controller card. Add-on Access Control Modules (ACMs) provide access control functionality by supporting readers, outputs, and inputs. GCMs have the following features:

Network, Dialup, and Serial Connections

The GCM includes an RJ-45 jack for access to a 10BaseT Ethernet network, a PC card slot (PCMCIA) for expandable communications, such as an internal modem or network card, expandable memory options, and a configurable serial port for an external modem or a direct connection to the host.

Cluster Configuration and Distributed Management

One or more controllers can be configured for communications purposes into user-defined groups called Clusters. Clusters have primary communications paths to the host that use Masters to control communications among cluster members and the host over the network. Clusters also support a backup communications path, the secondary communications path. The cluster can use the secondary path to communicate with the host when a communications failure occurs on the primary path. Secondary paths can use either the master or an Alternate Master. See “Networked iSTAR Controllers (Clusters)” on page 1-5 for information.

Communications among iSTAR controllers provide distributed functionality at the controller level that is not typically available on security management systems. Global Antipassback by Cluster is an example of an ideal application. See “Distributed Cluster Management” on page 1-8 for information.



iSTAR Pro/Classic controllers must have their own separate clusters while iSTAR eX controllers have their own separate clusters. This is because the method of encryption is different for each type of controller.

Firmware Upgradable

The GCM includes on-board Flash ROM, a non-volatile memory, for storage of the iSTAR’s firmware and communication protocol parameters, such as MAC address, and IP and gateway router IP addresses. Firmware upgrades involve a simple download initiated from a host.

Seamless Integration with Host

The C•CURE journal and database host, networked to iSTAR, provides support for initial setup, managing peripheral hardware and generating activity reports.

This chapter explains how to configure the controller software components to work with C•CURE 800/8000. To install and configure hardware for the controller, see the iSTAR Pro Installation and Configuration Guide.

Access Control Modules

ACM8W

Includes on-board reader processors that can support up to eight direct wired Wiegand read head type modules (Wiegand Card and/or Proximity Card). The ACM8W supports connections of up to eight RM Series Readers or RM-4 Modules and has eight output relays and 16 Class A supervised inputs. The ACM8W can also support up to eight I/8 Input Modules and eight R/8 Output Modules.

Up to two access control modules are supported per GCM providing the following reader configurations:

Eight readers - one ACM8W.



16 readers - two ACM8Ws.

Table 1-1 on page 1-4 summarizes the capabilities of ACM:

Connecting Security Devices to the ACM

The following types of access control devices are supported by the ACM:

Inputs

Outputs

Readers

Optional boards consisting of the I/8 - Input Module and the R/8 - Output Module

Inputs

An input is a software definition that associates a hardware switch, such as an alarm device, with an input on the controller or on an input board. There are two kinds of inputs: supervised and unsupervised. All switches can be in one of two states: active or inactive. An input reports the state of the switch.

A supervised input reports on the status of the wiring between the controller and the switch. If that wiring is cut, the system reports an open circuit. If someone tries to jumper across the wiring (prevent the device from

NOTE The maximum configuration per iSTAR Controller with two ACMs is 16 readers, 195 inputs, 177 outputs, 16 I/8 Input Modules, and 16 R/8 Output Modules.

Table 1-1: ACM Capabilities

ACM Reader Sources Input Sources Output Sources

ACM8W 8 Readers (RM and/or direct Wiegand and/or proximity)

16 Inputs on ACM

2 Inputs per RM Reader

Optional: 8 I/8 Modules (8 inputs each)

max = 80 to 96 inputs

8 Outputs on ACM

2 Outputs per RM Reader (with optional ARM-1 modules)

Optional: 8 R/8 Modules (8 outputs eachmax = 72 to 88 outputs



reporting), the system reports a shorted circuit. Supervised inputs can report a total of five conditions to the controller: Short, Open Loop, Line Fault, Inactive, or Active.

An unsupervised input does not monitor the wiring. Unsupervised inputs can report two conditions to the panel: Active or Inactive. Unsupervised inputs must not be used in the protective circuit.

Outputs

An output is a software definition that associates an event or input to a relay on the controller or add-on module. The relay then activates or deactivates devices, such as flood lights and alarm devices.

Readers

A reader is a hardware device that accepts access requests. To make an access request, a person swipes 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.

Optional Boards

Optional boards let you attach additional inputs and outputs to the controller. iSTAR controllers support these optional boards:

I/8 - Input Modules provide eight additional inputs to the controller. The I/8 - Input Module uses Class-A supervised inputs.

R/8 - Output Modules provide eight additional outputs to the controller.

Networked iSTAR Controllers (Clusters)

Controllers are organized for network communications into user-defined or logical groups called clusters. This section describes the key elements of clusters.

NOTE Unsupervised inputs must not be used in the protective circuit.



Master and Cluster Members

Each cluster has one controller that serves as the Master with all other controllers in the cluster acting as Cluster Members. The master manages all communications between the cluster and a host computer. Cluster members can communicate with each other via the master, over an Ethernet network. Cluster members cannot communicate with each other directly. Figure 1-1 (left) shows how Cluster Member A communicates with the host via the master. The figure (right) shows how Cluster Member A communicates with Cluster Member B via the master.

Figure 1-1: Cluster Members

The Primary Communications Path

The Primary Communications Path is the first communications path that controllers use to establish communications with the host. The path includes the following main elements:

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 never tries to 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.

The Connection type is how the master connects to the host: TCP/IP over Ethernet, a serial connection (RS-232), or dialup (internal or external modem). Cluster members are connected to the master via Ethernet only.

Figure 1-2 shows the Primary Communications Path for Cluster Member A. The master/host connection type is TCP/IP over Ethernet.

Figure 1-2: Primary Communications Path

The Secondary Communications Path

A Secondary Communications Path is the host communications path that is used by a cluster if a communications failure occurs on the primary communications path. The secondary path can be one of the following connections:

A second connection between the master and the host, such as a dialup connection.



A connection between the host and another cluster member, the Alternate Master, that assumes responsibility for communications for the cluster.

The secondary communications path can be an Ethernet, dialup, or serial connection from the master or an Ethernet connection from another cluster member.

Figure 1-3 shows two examples of secondary communications paths: (left) a secondary communications path on the master using a dialup connection and (right) a secondary communications path on the alternate master using an Ethernet connection.

Figure 1-3: Secondary Communications Path

Distributed Cluster Management

Cluster communications allow iSTAR controllers to share information and control actions throughout a cluster without host intervention. Distributed Cluster Management is the distribution of system functionality from the host to cluster members.



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. Current technology, such as the apC/8X, provides local control of only a few actions, and since apC/8Xs cannot be added to clusters or communicate directly with controllers, they cannot share information as iSTAR controllers can. The host controls most actions for the apC/8X.

Example:

If an apC/8X is in communications failure, an input on the panel can activate only one output or output group on the panel; however, if an iSTAR master is in communications failure with the host, any input on any controller in the cluster can activate any output or output group on any controller in the cluster.

Control of the following activities is distributed to clusters:

Events

Controllers can control the activation and deactivation of events and timed actions locally and on other controllers in the cluster.

Example:

If a Forced Door Event activates outputs on another controller in the cluster, the controller with the Forced Door Event, not the host, activates the outputs.

When you configure the Forced Door Event, you must specify the controller to which you want to download the event. Only one controller or the C•CURE 800/8000 server controls an event. See the C•CURE 800/8000 Software Configuration Guide for information.

NOTE Cluster members communicate with each other through the master. Although a communications failure with the host may not affect cluster communications, a communications failure with the master can cause communications problems in the cluster if no alternate master is configured.



System Activity

Controllers control system activity in a cluster. For example, an input on a controller can activate any output on any controller in the cluster without host intervention.

Global Antipassback Control by Cluster

Controllers allow the sharing of cardholder anti-passback status among each other in a area within a cluster. Global anti-passback lets you set up areas with doors on any controller in the cluster. See the C•CURE 800/8000 Software Configuration Guide for information.

Configuration Overview for iSTAR Classic & iSTAR Pro


Configuration Overview for iSTAR Classic & iSTAR Pro

Configuring the iSTAR controllers involves setting up the hardware and configuring the software components.

The Table 1-2 provides a list of tasks for software configuration of iSTAR controllers.

NOTE Before configuring a cluster, make sure you know each cluster member’s MAC address. The MAC address is built into the GCM and cannot be changed.

Table 1-2: Software Configuration Tasks

Stage Task See...

1 Use the Controller dialog box in the C•CURE 800/8000 Administration application to configure iSTAR controllers.

“Configuring iSTAR Classic & iSTAR Pro Controllers” on page 1-12 for information.

2 Use the Cluster dialog box in the C•CURE 800/8000 Administration application to configure clusters.

“Configuring Clusters for iSTAR Classic & iSTAR Pro” on page 1-42 for information.

3 Use the iSTAR Configuration Utility to manually configure the master.

NOTE: After you configure the master, it reboots and then establishes a connection with the C•CURE System Host. The host downloads cardholder and configuration information to the master. The master uses this information to auto-configure its cluster members.

iSTAR Pro Installation and Configuration Guide and/or iSTAR Installation and Configuration Guide (Classic).

Configuring iSTAR Classic & iSTAR Pro Controllers



The Controller dialog box lets you configure the GCM and any installed ACMs. Up to two ACMs can be installed on an iSTAR.

To Configure Controllers

1. From the C•CURE 800/8000 Administration application, choose Hardware->Controller from the menu bar. The iSTAR Controller Selection browser appears, shown in Figure 1-4.

Figure 1-4: STAR Controller Selection Browser

2. Click New to create a new controller The Select Panel Type dialog box appears, shown in Figure 1-5 on page 1-13.

- or -

Select a controller and click Edit to edit a controller’s configuration.The Controller dialog box appears, as shown in Figure 1-6 on page 1-13. Go to Step 3 on page 1-13.



Figure 1-5: Select Panel Type Dialog Box

a. Select iSTARClassic or iSTARPro.

b. Click OK. The Controller dialog box appears, as shown in Figure 1-6.

Figure 1-6: Controller Dialog Box for iSTAR Pro/Classic

3. Provide the information described in Table 1-3 on page 1-14 and click OK to save the controller configuration and close the Controller dialog box.



If your system is using the Distributed Holidays mode and there is no Holiday list assigned to this iSTAR, the system displays a warning message similar to the following, but still allows you to save the controller configuration. (For detailed information, see “Configuring Holiday Lists for a Controller” on page 1-19.)

Table 1-3: Controller Dialog Box Fields

Box Field Description

Identification 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.

Identification, continued Online Click this check box to put the controller online. When a controller is online, C•CURE 800/8000 can communicate with it. If you put a controller offline, the following occurs:

The C•CURE 800/8000 host ignores the controller. For example, the host no longer downloads new/changed data to the controller, and the controller no longer appears at the Guard Station or in journal messages.

The communications path between the controller and the C•CURE 800/8000 host is maintained. If the controller is a master, the master and host continue to exchange connection verification messages. If the controller is not the master, the controller and the master exchange connection verification messages.

The controller continues to operate, responding to access requests for example. However, all action requests to and from offline controllers are canceled, possibly changing a controller’s state. For example, if an input on Controller A activates an output on Controller B and you then put Controller A offline, the cause for the output activation is canceled. However if the input and output are both attached to the same controller, putting the controller offline does not affect the output activation.

If the controller is a cluster member, it continues to communicate with the master.



Online, continued If you delete a controller, it is ignored by the C•CURE 800/8000 host and cannot communicate with other cluster members.

To stop a controller performing access control decisions:

Put any attached readers offline. (Do not put the controller offline until you put these objects offline.

- or -

Erase the controller’s memory.

iSTAR hardware Sub-type A read-only field displaying the controller sub-type: iSTAR Pro/Classic or iSTAR eX.

Description Enter a general comment about the controller. This text is for information only.

General Tab

This controller is Displays whether this controller is the cluster master or a cluster member. Use the Cluster dialog box to specify a master for a cluster. You cannot edit this field.

in cluster Displays the name of the cluster to which this controller is assigned. Use the Cluster dialog box to add controllers to clusters. You cannot edit this field.

The controller is in time zone:

Specify a time zone for the controller. Double-click on this box to display a selection browser for time zones. 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 time specifications 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 time specification 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 800/8000 Software Configuration Guide for more information.

Table 1-3: Controller Dialog Box Fields, continued




Holiday Lists NOTE: This button is available only if your C•CURE 800/8000 system is operating in Distributed Holidays mode—enabled on the System Variables System tab. (If this button is unavailable, the system is operating in Default Holiday mode and any configured Holiday Lists are automatically downloaded to all iSTAR controllers.)

For more information about these modes and how to change them, see “Holiday Lists” in the C•CURE 800/8000 Software Configuration Guide and “Setting System Variables” in the C•CURE 800/8000 System Maintenance Guide.

Click this button to open the Holiday Lists dialog box to choose up to 24 Holiday Lists for this controller. For detailed information, see “Configuring Holiday Lists for a Controller” on page 1-19.

MAC Addresses Hardware (MAC) Address Enter the Hardware 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 of a controller’s MAC address are set at 00-50-F9.

Onboard Ethernet Adapter Obtain an IP Address from a DHCP Server

Select this to have a DHCP server provide an IP address.

IP Address If you do not select DHCP, you must enter a static address. Enter the controller’s IP address as 4 numbers between 0 and 255, separated by periods, such as 128.110.121.45. A unique IP address is required for all computers, including controllers, on TCP/IP networks.

PCMCIA Ethernet Adapter PCMCIA Ethernet Adapter Installed

Select this if the PCMCIA Ethernet Adapter is installed.

Obtain an IP Address from a DHCP Server



Use this as Primary Ethernet Adapter

Select this to use PCMCIA as the primary adapter.





Host activates event

When controller is in communication failure

Enter the name of the event that is activated when this controller goes into communications failure.

Specify an event that is located on the host. If the event is located on a controller, the system displays an error message.

You can double-click on this field to open the Event Selection browser where you select, edit, or create an event.

NOTE: If this controller is a cluster member, the host activates the specified event any time the master goes into communications failure. The event is deactivated when communications are reestablished with the host using either the primary or secondary path.

When controller is in long term communications failure

Enter the name of the event that is activated when this controller exceeds the long term communication loss time limit specified in the Controller tab in System Variables (see “Defining Controller Options” in the CCURE 800/8000 System Maintenance Guide). You can double-click on this field to open the Event Selection browser where you select, edit, or create an event.


NOTE: If this controller is a cluster member, the host activates the specified event any time the master goes into long term communications failure. The event is deactivated when communications are reestablished with the host using either the primary or secondary path.

Other Tabs

Main Board This tab lets you configure the output and inputs on the GCM and RM LCD messages. See “Main Board Tab for iSTAR Classic & iSTAR Pro” on page 1-21 for more information.

1st ACM This tab lets you configure inputs and outputs on the first ACM. “ACM and ACM Ext Tabs for iSTAR Classic & iSTAR Pro” on page 1-25

1st ACM Ext This tab lets you configure I/8 input modules, IR/8 output modules, and Readers on the first ACM attached to the GCM. “ACM and ACM Ext Tabs for iSTAR Classic & iSTAR Pro” on page 1-25





2nd ACM This tab lets you configure inputs and outputs on the second ACM attached to the GCM. “ACM and ACM Ext Tabs for iSTAR Classic & iSTAR Pro” on page 1-25

2nd ACM Ext This tab lets you configure I/8 input modules, R/8 output modules, and Readers on the second ACM attached to the GCM. See “ACM and ACM Ext Tabs for iSTAR Classic & iSTAR Pro” on page 1-25 for more information.





Configuring Holiday Lists for a Controller

You can download any holiday list to an iSTAR controller from a dialog box accessed either from the General tab, or alternatively, from the Holiday List Configuration dialog box.

A Holiday List downloaded to an iSTAR controller acts as an override to prevent activation of normally scheduled clearances and timed-based events on the Holidays defined in the Holiday List. You can configure up to 24 holiday lists for each iSTAR controller.

To Select Holiday Lists for the Controller

1. On the General tab of the Controller dialog box, click the Holiday Lists button.

The Select Holiday Lists dialog box opens, as shown in Figure 1-7 on page 1-20.

NOTE This section is applicable only if your C•CURE 800/8000 system is operating in Distributed Holidays mode—enabled on the System Variables System tab.

For more information about these modes and how to change them and Holiday Lists in general, see the C•CURE 800/8000 Software Configuration Guide and “Setting System Variables” in the C•CURE 800/8000 System Maintenance Guide.



Figure 1-7: Select Holiday List Dialog Box

2. For each Holiday List that you want to download to the controller, click that Holiday List in the Available box and click Add to add it to the Selected box. You can click Add All to include all of the Available Holiday Lists for the controller. You can click Remove or Remove All to remove one or all Holiday Lists from the controller.

3. Click OK to save the selected Holiday Lists and return to the Controller dialog box.

NOTE The Available box includes all existing Holiday Lists in the system not currently used by this controller.

NOTE When you click OK, the system validates that the controller does not have more than the limit of 24 Holidays Lists.

Main Board Tab for iSTAR Classic & iSTAR Pro



Configuring the Main Board

The Main Board tab in the Controller dialog box lets you define the Wyreless Access PIM-485 third party device, the output on the GCM, RM LCD messages for the controller, and the following inputs on the GCM:

Tamper input activates when the controller cabinet is opened or removed from its mounting surface.

AC power fail 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.

Low battery input activates when the emergency battery is running low on power.

To Configure the Main Board

1. From the Controller dialog box, click the Main Board tab. The Main Board tab opens for the controller, shown in Figure 1-8.

Figure 1-8: Main Board Tab

2. Provide the information described in Table 1-4 on page 1-22.



Table 1-4: Main Board Tab Fields

Box Field/Button Description

Inputs Tamper Click this check box to configure the Tamper input. The system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.

If Online is the default setting for the input and you do not deselect this option in the Input dialog box, the input is set online and downloaded after you click OK in the Controller dialog box.

Deselecting the Tamper check box in the Controller dialog box, deletes the Tamper input.

AC power fail input Click this check box to configure the AC power fail input. The system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the AC power fail input check box in the Controller dialog box, deletes the AC powerfail input.

Low battery input Click this check box to configure the Low Battery input. The system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Low Battery input check box in the Controller dialog box, deletes the Low Battery input.



Output Output Click this check box to configure the output on the GCM. The system automatically configures the output using the values from the default output definition. To view or edit the output, click the output’s View button. See “Configuring Outputs” on page 6-13 for more information.

If Online is the default setting for the output and you do not deselect this option in the Output dialog box, the output is set online and downloaded after you click OK in the Controller dialog box.

Deselecting the Output check box in the Controller dialog box, deletes the output.

Third-party Devices

Wyreless Access PIM-485 Click the Configure button

Options common to entire panel

RM LCD messages: Specify the set of RM Reader LCD messages to assign to this controller. Double-click this text box to display a list of message sets. See “Configuring RM Reader LCD Messages” on page 5-15.

GC Port P5 Baud Rate The Baud Rates from which you can choose are:

9600

19200

38400

57600

115200

Include Personnel Without Clearance in Personnel Downloads

When selected, personnel records that would not normally be downloaded to a iSTAR controller due to lack of clearance at any of the doors under its control are downloaded to the iSTAR panel. This selection allows the availability of such personnel records for use with the Conditional Access feature. This option should be selected if the iSTAR panel has any doors configured for Conditional Access. Making this selection means that the iSTAR Pro will store more card.

This selection can be made only when the controller is offline. Making this selection causes a full personnel download to the panel, once it is put back online.

NOTE: iSTAR Classic controllers do not support the Conditional Access feature.

Table 1-4: Main Board Tab Fields, continued




NOTE The first time you configure an input or output, you must do so from the Controller dialog box for the security object. After a security object is defined, you can edit its definition from the Controller dialog box or by selecting the item from the Hardware drop-down menu on the C•CURE 800/8000 Administration application.

ACM and ACM Ext Tabs for iSTAR Classic & iSTAR Pro



Configuring ACMs

The ACM tabs in the Controller dialog box let you define security objects which are connected to the ACMs. The 1st ACM and 2nd ACM tabs let you configure the inputs and outputs on the first and second ACMs respectively. The1st ACM and 2nd ACM Ext tabs let you configure the add-on boards and readers on the ACMs.

To Configure the ACMs

1. From the Controller dialog box, click the 1st ACM tab to configure the first ACM on the GCM.

- or -

Click the 2nd ACM tab to configure the second ACM on the GCM.

The appropriate tab opens. Figure 1-9 shows the 1st ACM tab.

Figure 1-9: 1st ACM Tab




3. Click the 1st ACM Ext tab to configure the readers and add-on boards for the first ACM.

- or -

Click the 2nd ACM EXT tab to configure the readers and add-on boards for the second ACM.

The appropriate tab opens. The 1st ACM Ext tab is shown in Figure 1-10 on page 1-27.

Table 1-5: ACM Tab Fields


Type of module Select the type of ACM. Choices are ACM8 or ACM8W.

Inputs Inputs 1 to Input 16 Click the check box next to the input that you want to configure. The system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.

The input is downloaded to the controller when you click OK in the Controller dialog box.

Deselecting the Input check box in the Controller dialog box deletes the input.

Outputs Outputs 1 to 8 Click the check box next to the output that you want to configure. The system automatically configures the output using the values from the default output definition. To view or edit the output, click the output’s View button. See “Configuring Outputs” on page 6-13, for more information.

The output is downloaded to the controller when you click OK in the Controller dialog box.

Deselecting the Output check box in the Controller dialog box deletes the output.

NOTE The first time you configure an input or output, you must do so from the Controller dialog box for the security object. After a security object is defined, you can edit its definition from the Controller dialog box or by selecting the item from the Hardware drop-down menu on the C•CURE 800/8000 Administration application.



Figure 1-10: 1st ACM Ext Tab


NOTE The first time you configure a reader, you must do so from the Controller dialog box for the reader. After a reader is defined, you can edit its definition from the Controller dialog box or by selecting Reader from the Hardware pull-down menu on the C•CURE 800/8000 Administration application.

Table 1-6: ACM Ext Tab Fields


Type of module Select the type of ACM. Choices are ACM8 or ACM8W.

NOTE: You should select the same type of module that you selected in the 1st ACM or 2nd ACM tab.

Input Boards I/8 #1 to #8 Choose the I/8 - Input Module that you want to configure by clicking the appropriate check box and View button for the board. The I/8 dialog box opens. See “Configuring I/8 - Input Modules for iSTAR” on page 1-28 for information.

Deselecting the I/8 check box in the Controller dialog box, deletes the I/8 Input Module.

Output Boards R/8 #1 to #8 Choose the IR/8 - Output Module that you want to configure by clicking the appropriate check box and View button for the board. The R/8 dialog box opens. See “R/8 - Output Modules for Controllers” on page 1-31 for information.

Deselecting the R/8 check box in the Controller dialog box, deletes the R/8 Input Module.



Configuring I/8 - Input Modules for iSTAR

The I/8 - Input Module provides additional inputs to the controller for monitoring security alarms. The I/8 - Input Module has Class-A supervised inputs; 8 supervised alarm inputs for controllers. You can add up to 16 I/8 - Input Modules to a controller (eight per ACM).

To Add I/8 - Input Modules

1. In the 1st ACM Ext or 2nd ACM Ext tab in the Controller dialog box, choose the I/8 - Input Module you want by clicking the appropriate check box and View button for the board. The I/8 dialog box opens, shown in Figure 1-11 on page 1-29.

Readers Reader #1 to #8 Click the check box next to the reader that you want to configure. The system automatically configures the reader using the values from the default reader definition. To view or edit the reader, click the reader’s View button. See “Configuring Readers” on page 5-2 for more information.

The reader is downloaded to the controller when you click OK in the Controller dialog box.

Deselecting the Reader check box in the Controller dialog box, deletes the reader.

Table 1-6: ACM Ext Tab Fields, continued


NOTE The I/8 - Input Modules are connected to a reader bus port on the ACM.



Figure 1-11: Input Module Dialog Box

2. Choose the input you want to add by clicking the appropriate check box. The system automatically configures the input using the values from the default input definition and an assigned name.

3. To view or edit the input, click the input’s View button. The Input dialog box opens.

4. Edit the input for the add-on board as you would any input on the ACM. See “Configuring Inputs” on page 6-2 for information about configuring inputs.

5. In the I/8 dialog box, provide the information described in Table 1-7 on page 1-30 in the I/8 Status Inputs box and click OK.

NOTE To edit the default input, choose Input from the Hardware menu and click the Edit Default button in the Input Selection browser. The Input dialog box opens. See “Configuring Inputs” on page 6-2 for information about configuring inputs.

NOTE The input is downloaded to the controller when you click OK in the Controller dialog box.



Table 1-7: I/8 Status Inputs box

Box Description

Tamper Click this check box to configure the Tamper input on the I/8 - Input Module. This input activates when the I/8 - Input Module is tampered. If you select this check box, the system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Tamper check box in the I/8 dialog box, deletes the Tamper input.

Communications Failure Click this check box to configure the Communications Failure input on the I/8 - Input Module. This input activates when the I/8 - Input Module goes into communications failure. If you select this check box, the system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Communications Failure check box in the I/8 dialog box, deletes the Communications Failure input.



R/8 - Output Modules for Controllers

The R/8 - Output Modules provide additional outputs to the controller. You can add up to 16 R/8 -Output Modules to a controller (8 per ACM).

To Add R/8 - Output Modules

1. In the 1st ACM Ext or 2nd ACM Ext tab in the Controller dialog box, choose the R/8 - Output Module you want by clicking the appropriate check box and View button for the board. The R/8 dialog box opens, shown in Figure 1-12.

Figure 1-12: R/8 Dialog Box

2. Choose the output you want to add by clicking the appropriate check box. The system automatically configures the output using values from the default output definition and an assigned name.

NOTE The R/8 - Output Modules are connected to a reader bus port on the ACM.

NOTE To edit the default output definition, choose Output from the Hardware menu and click the Edit Default button in the Output Selection browser. The Output dialog box opens. See “Configuring Outputs” on page 6-13 for information about configuring outputs.

NOTE The input is downloaded to the controller when you click OK in the Controller dialog box.



3. To view or edit the output, click the output’s View button. The Output dialog box opens.

4. Edit the output for the add-on board as you would any output on the controller. See “Configuring Inputs” on page 6-2 for information about configuring outputs.

5. In the R/8 dialog box, provide the information described in Table 1-8 on page 1-32 in the R/8 Board Status Inputs box and click OK.

Table 1-8: R/8 Dialog Box

Box Description

Tamper Click this check box to configure the Tamper input on the R/8 - Output Module. This input activates when the R/8 - Output Module is tampered. If you select this check box, the system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Tamper check box in the R/8 dialog box, deletes the Tamper input.

Communications Failure Click this check box to configure the Communications Failure input. This input activates when the R/8 - Output Module goes into communications failure. If you select this check box, the system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Communications Failure check box in the R/8 dialog box, deletes the Communications Failure input.

Cluster Communications Overview for iSTAR Classic & Pro



Controllers use the primary communications path to communicate with the C•CURE System host. Establishing and maintaining a connection with the host involves the following actions:

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.

Establishing Connections Via the Primary Communications Path

The primary communications path is the first path that controllers use to establish communications with the host. The path is comprised of the following connections:

The master connects directly to the host using a network, serial, or dialup connection.

Cluster members connect to the master using a network connection. After connections are established, the master manages cluster communications by passing messages between cluster members and the host.

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.

NOTE The C•CURE System host usually does not try to establish a connection with the master (or alternate master); however, the C•CURE System host will initiate a connection when automatic or periodic dialup is configured for the master.



Setting Up the Primary Communications Path

Before controllers can establish any connections, you must configure the cluster’s primary communications path by performing the following tasks:

Use the C•CURE 800/8000 Administration Application to configure controllers and the cluster. See “Configuring iSTAR Classic & iSTAR Pro Controllers” on page 1-12 and “Configuring Clusters for iSTAR Classic & iSTAR Pro” on page 1-42 for information.

Use the iSTAR Configuration Utility to manually configure the master. After you configure the master, it reboots and then establishes a connection with the C•CURE System Host. The host downloads cardholder and configuration information to the master.

After downloading information from the host, the master auto-configures its cluster members. Cluster members then reboot and establish connections with the master. See the iSTAR Pro Installation and Configuration Guide for more information.

Downloading Cardholder and Configuration Information

The following information is downloaded to the master and its cluster members from the host:

Cardholder data for personnel with clearances on the controller.

Configuration information for inputs, outputs, and readers on the controller.

Events that are controlled by the controller.

Cluster information that the controller uses to communicate with other cluster members.

NOTE The C•CURE System host downloads cardholder and configuration information to the controller under the following conditions:

Initial configuration;

Each time the controller is powered on;

Each time the cluster is taken offline/online.



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 Cluster dialog box in the C•CURE 800/8000 Administration Application to configure connection verification messages for the master, host, and cluster members. See “Configuring Clusters for iSTAR Classic & iSTAR Pro” on page 1-42 for more information.

Establishing a Secondary Communications Path

If a communications failure occurs on the primary communications path, communications can be re-established via the cluster’s secondary communications path. The secondary communications path can be one of the following connections:

A second connection between the master and the host. The connection can be network, serial, or dialup, whichever method that is not already being used as the primary path.

A network connection between another controller in the cluster—the alternate master—and the host.



The configuration of the secondary communications path (alternate master or a secondary connection from the master) determines how controllers re-establish cluster communications when the primary path fails. See “Maintaining Cluster Communications for iSTAR Classic & Pro” on page 1-37 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 Secondary tab in the Cluster dialog box in the C•CURE 800/8000 Administration Application to configure the secondary communications path. See “Configuring the Secondary Communications Test” on page 1-58 for more information.

Maintaining Cluster Communications for iSTAR Classic & Pro



Maintaining cluster communications involves establishing and maintaining connections via the primary communications path. If the primary connection is lost, the secondary communications path can sometimes be used to re-establish cluster communications. This section describes how the configuration of the secondary communications determines the way in which cluster communications are re-established.

Losing a Connection with the Host

If the master loses its connection with the host, the following configurations of the secondary communications path determine how cluster communications are re-established:

Secondary Connection Between the Master and Host

If the master loses its connection with the host and the secondary communications path is another connection between the master and the host, as shown in Figure 1-13 on page 1-38 and Figure 1-14 on page 1-39, the following occurs:

Cluster members continue to communicate with the master.

The master continues to pass cluster members’ messages to the host.

However, the master uses the secondary communications path to communicate with the host.

Example:

If the secondary path is a dialup connection between the master and host, the master uses the dialup connection to communicate with the host.



Figure 1-13: Communications Failure on the Primary Path



Figure 1-14: Communications Wiring on the Secondary Path

Connection Between an Alternate Master and the Host

If the master loses its connection with the host and the secondary communications path is a connection between an alternate master and the host, as shown in Figure 1-15 on page 1-40 and Figure 1-16 on page 1-41, the following occurs:

The alternate master establishes a connection with the host via the secondary communications path.

Cluster members establish connections with the alternate master via the network.

The alternate master sends the cluster members’ messages to the host.



Figure 1-15: Master Unit has Hardware Failure



Figure 1-16: Communications Reestablished via an Alternate Master

Configuring Clusters for iSTAR Classic & iSTAR Pro



The Cluster dialog box lets you configure clusters by performing the following tasks:

Add controllers to the cluster

Configure a primary communications path for the cluster

Configure a secondary communications path for the cluster

Configure communications between cluster members and the master

Configure a test of the secondary communications path

To Configure a Cluster

1. From the C•CURE 800/8000 Administration application, choose Hardware->iSTAR Cluster from the menu bar. The iSTAR Cluster Selection browser appears, shown in Figure 1-17.

Figure 1-17: STAR Cluster Selection Browser

NOTE The Secondary Communications Test is not supported in this version of C•CURE 800/8000.



2. Click New to create a new cluster The Select Cluster Type dialog box appears, shown in Figure 1-18.

- or -

Select a controller and click Edit to edit a cluster’s configuration.The Cluster dialog box appears, shown in Figure 1-19. Go to Step 3 on page 1-44.

Figure 1-18: Select Cluster Type Dialog Box

a. Select either of the iSTAR subtype options:

– iSTAR Classic or Pro

– iSTAR eX

b. Click OK. The Cluster dialog box appears, shown in Figure 1-19 on page 1-44.



Figure 1-19: Cluster Dialog Box

3. Provide the information shown in Table 1-9 on page 1-45 and click OK to save the cluster configuration and close the Cluster dialog box.



Table 1-9: Cluster Dialog Box Fields

Box Fields/Button Description

Identification Name Enter a unique name for the cluster. The name can be up to 50 characters long. If you enter the name of an existing object, the system returns an error message indicating there is a conflict.

Online Click this check box to put the cluster online. When a cluster is online, C•CURE 800/8000 can communicate with the controllers in the cluster. When a cluster is offline, all controllers in the cluster are set offline. Communications paths in the cluster are maintained, and controllers perform access control decisions; however, C•CURE 800/8000 ignores controllers in the cluster, and action requests among cluster members are canceled.

All cardholder and configuration information is downloaded to the cluster each time you put the cluster online.

NOTE: You must put the cluster’s master online before putting the cluster online. If you want to take a master offline, take its cluster offline first.

NOTE: You cannot select the method of communication between host and controller on the Primary or Secondary tabs if the cluster is online. To put the cluster offline, deselect the Online check box, click OK to close the dialog box, and then re-open the dialog box.

Description Enter a general comment about the cluster. This text is for information only.

iSTAR hardware Sub-type A read-only field displaying the controller sub-type:iSTAR Pro/Classic or iSTAR eX.

General Tab

Available Controllers

Displays a list of controllers that you can add to the cluster. A controller can be a member of only one cluster. If a controller is already assigned to a cluster, the controller is not displayed in this list. Use the Add and Add All buttons to add controllers to the cluster by moving them from the Available Controllers box to the Controllers in this cluster box. Use the Remove and Remove All buttons to take controllers out of the cluster.

Edit Controllers Click this button to open the CCURE Controller Selection browser where you can select, edit, or create controllers. See “Configuring iSTAR Classic & iSTAR Pro Controllers” on page 1-12 for information.



Add/AddAll/Remove/Remove All buttons

Click these buttons to move controllers between the Controllers in this cluster and Available Controllers boxes. For example, if you click Add All, all controllers in the Available Controllers box are moved to the Controllers in this cluster box. Controllers listed in the Controllers in this cluster box are members of the cluster.

Controllers in this Cluster

Displays a list of controllers that are assigned to the cluster. A controller must be assigned to a cluster for C•CURE 800/8000 to communicate with the controller. Use the Add and Add All buttons to add controllers to the cluster by moving them from the Available Controllers box to the Controllers in this cluster box. Use the Remove and Remove All buttons to take controllers out of the cluster.

Other Tabs

Primary This tab lets you configure the primary communications path for the cluster. See “Configuring the Primary Communications Path” on page 1-47 for more information.

Secondary This tab lets you configure the secondary communications path for the cluster. See “Configuring the Secondary Communications Test” on page 1-58 for information.

Cluster This tab lets you configure communications between cluster members and the master. See “Configuring Communications with the Master” on page 1-55 for information.

Misc This tab lets you configure a communications test for the secondary communications path and the maximum number of unacknowledged messages allowed for each controller. See “Configuring the Secondary Communications Test” on page 1-58 for information.

Global APB This tab lets you specify if the cluster enforces cluster antipassback and iSTAR Global Antipassback as well as how the cluster handles antipassback during communications failure. See “Configuring Antipassback for the Cluster” on page 1-60 for information.

Encryption This tab is unavailable for the iSTAR Pro/Classic.

Table 1-9: Cluster Dialog Box Fields, continued

Box Fields/Button Description

Primary Tab for iSTAR Classic & iSTAR Pro



Configuring the Primary Communications Path

The Primary tab in the Cluster dialog box lets you configure a primary communications path for the cluster.

To Configure the Primary Communications Path

1. From the Cluster dialog box, click the Primary tab. The Primary tab opens for the cluster, shown in Figure 1-20.

Figure 1-20: Primary Tab

2. Provide the information shown in Table 1-10 on page 1-48.

NOTE You cannot select the method of communication between host and controller on the Primary tab if the cluster is online. To put the cluster offline, deselect the Online check box in the Identification box, click OK to close the dialog box, and then re-open the dialog box.



Table 1-10: Primary Tab Fields

Field/Button Description

Controller having primary communications with host:

Enter the name of the controller from the cluster that you are designating as the master. Double-click on this field to display a list of controllers from which you can make a selection. If you select a controller that is not a cluster member, C•CURE 800/8000 displays an error message telling you to choose another controller.

NOTE: This field is unavailable if the cluster is online. See the note on page 1-45 for the procedure to put the cluster offline.

Method of communication between host and controller:

Specify the type of connection that the master uses to communicate with the host:

TCP/IP. The master communicates with the host using TCP/IP over an Ethernet network.

Serial. The master communicates with the host via a RS-232 connection. Use the Host port used for serial communications with controller field to specify a port on the host for the master. See “iSTAR Dialup Overview” on page 11-2 for more information.

Dialup. The controller communicates with the host via dialup. Click the Configure Dialup button which becomes available when you select this type of connection. See “iSTAR Dialup Overview” on page 11-2 for more information.


Configure Dialup Click this button to configure the primary communication path as dialup. See “Configuring iSTAR Clusters for Dialup” on page 11-8 for more information.

NOTE: If you did not select Dialup in the Method of communication between host and controller field and enter the name of the controller that you are designating as the master in the Controller having primary communications with the host field, this button is unavailable. The button is also unavailable if the cluster is online. See the note on page 1-45 for the procedure to put the cluster offline.

Host port used for serial communications with controller:

If the master uses a serial connection to communicate with the host, enter the port on the host to which the controller is connected. You can double-click on this field to display a list of ports on the C•CURE 800/8000 server. See “Configuring iSTAR Clusters for Dialup” on page 11-8 for more information.

NOTE: If you did not select Serial in the Method of communication between host and controller field and if, in addition, the cluster is online, this field is unavailable. See the note on page 1-45 for the procedure to put the cluster offline.

Controller attempts to connect to host every n seconds

Specify the number of seconds that the master waits between attempts to first connect to the host on the primary communications path. Use the Controller declares connection failure afterXX failed attempts field to specify the number of connection attempts the master makes before a communications failure is declared for the primary communications path.



Controller declares connection failure after n failed attempts

Specify the number of attempts that the master makes to first connect to the host before a communications failure is declared for the primary communications path. If a connection is established, the master and host use connection verification messages to maintain the connection. See the While connected, declare connection failure if no message for XX seconds field in the Primary tab for information.

If a connection is not made in the specified number of attempts, a communications failure is declared for the primary communications path; the master sends a cluster information message to its cluster members telling them that the primary communications path is in communications failure, and the following activity is attempted simultaneously:

The cluster tries to establish a connection with the host on the secondary communications path.

The master attempts to re-connect to the host on the primary communications path at the rate specified in the After connection failure, controller attempts to reconnect every XX seconds field in the Primary tab. The master tries to establish a connection with the host forever or until a connection is established.

The master broadcasts a request across its subnet for the host’s IP Address. If the iSTAR Configuration Utility is configured for auto-response, it responds to the master. See the iSTAR Pro Installation and Configuration Guide for information.

After connection failure, controller attempts to reconnect every n seconds

Specify the number of seconds that the master waits between attempts to reconnect to the host on the primary communications path. This field sets the rate at which the master attempts to reconnect or connect to the host after a communications failure has been declared for the primary communications path.

Table 1-10: Primary Tab Fields, continued




While connected, declare connection failure if no message for n seconds

Specify the number of seconds that the master and host wait for a connection verification message before declaring a communications failure for the primary path. The master and host send these messages to each other during periods of low system activity to confirm that the primary path is operating correctly. You can choose 40 or 80 seconds.

The value you specify in this field determines how often the connection verification message is sent. If you specify 40 seconds, the message is sent every 10 seconds; if you specify 80 seconds, the message is sent every 20 seconds.

For example, if you specify 40 seconds in this field, the master receives a connection verification message every 10 seconds during periods of low system activity. If the master does not receive at least one message within 40 seconds, it declares the primary path to be in communications failure.

If a communications failure occurs, the master sends a cluster information message to its cluster members telling them that the primary communications path has failed. The following activities are attempted simultaneously:


The master attempts to re-connect to the host on the primary communications path at the rate specified in the After connection failure, controller attempts to reconnect every XX seconds field in the Primary tab. The master tries to reestablish a connection with the host forever or until a connection is reestablished.


Controller activates this event while in connection failure:

Enter the event that the master activates when a communications failure occurs between the host and the master. You can double-click on this field to display a list of events.

Specify an event that is located on the master. If the event is located on the host or another controller, the system displays an error message.

Host activates this event while in connection failure:

Enter the event that the host activates when a communications failure occurs between the host and the master. You can double-click on this field to display a list of events.




Secondary Tab for iSTAR Classic & iSTAR Pro



Configuring the Secondary Communications Path

The Secondary tab in the Cluster dialog box lets you configure a Secondary Communications Path for the cluster.

To Configure the Secondary Communications Path

1. From the Cluster dialog box, click the Secondary tab. The Secondary tab opens for the controller, shown in Figure 1-21.

Figure 1-21: Secondary Tab


NOTE You cannot select the method of communication between host and controller on the Secondary tab if the cluster is online. To put the cluster offline, deselect the Online check box in the Identification box, click OK to close the dialog box, and then re-open the dialog box.



Table 1-11: Secondary Tab Fields


Controller having secondary communications with host:

Enter the name of the controller in the cluster that is responsible for communications with the host when a failure occurs on the primary communications path. You can specify the master or another controller in the cluster, the alternate master. Double-click on this field to display a list of controllers from which you can make a selection. If you select a controller that is not a cluster member, C•CURE 800/8000 displays an error message telling you to choose another controller.



Specify the type of connection that the controller uses to communicate with the host:

TCP/IP. The controller communicates with the host using TCP/IP over an Ethernet network.

Serial. The controller communicates with the host via a RS-232 connection. Use the Host port used for serial communications with controller field to specify a port on the host for the controller.

Dialup. The controller communicates with the host via dialup. Click the Configure Dialup button which becomes available when you select this type of connection. See “Configuring iSTAR Clusters for Dialup” on page 11-8 for more information.


Configure Dialup Click this button to configure the secondary communication path as dialup. See “Configuring iSTAR Clusters for Dialup” on page 11-8 for more information.

NOTE: If you did not select Dialup in the Method of communication between host and controller field and enter the name of the controller that you are designating as the master in the Controller having secondary communications with the host field, this button is unavailable. The button is also unavailable if the cluster is online. See the note on page 1-45 for the procedure to put the cluster offline.

Host port used for serial communications with controller:

If the controller uses a serial connection to communicate with the host, enter the port on the host to which the controller is connected. Double-click on this field to display a list of ports on the C•CURE system host. See Chapter 8,” for more information.

NOTE: If you did not select Serial in the Method of communication between host and controller field and if, in addition, the cluster is online, this field is unavailable. See the note on page 1-45 for the procedure to put the cluster offline.




Specify the number of seconds that the controller waits between attempts to first connect to the host on the secondary communications path. Use the Controller declares connection failure after failed attempts field in the Secondary tab to specify the number of connection attempts the controller makes before a communications failure is declared for the secondary communications path.


Specify the number of attempts the controller makes to first connect to the host before a communications failure is declared for the secondary communications path. If a connection is established on the secondary communications path, the following activities occur:

The controller and host use connection verification messages to maintain a connection on the secondary communications path. See the While connected, declare connection failure if no message for XX seconds field in the Secondary tab for more information.

The master attempts to connect to the host on the primary communications path at the rate specified in the After connection failure, controller attempts to reconnect every XX seconds field in the Primary tab. The master tries to establish a connection with the host forever or until a connection is established.


If a connection is not established on the secondary communications path, the following connections are attempted simultaneously:

The cluster tries to establish a connection with the host on the secondary communications path at the rate specified in the After connection failure, controller attempts to reconnect every XX seconds field in the Secondary tab.




Specify the number of seconds that the controller waits between attempts to reconnect to the host on the secondary communications path. This field sets the rate at which the controller attempts to reconnect or connect to the host after a communications failure has been declared for the secondary communications path.

Table 1-11: Secondary Tab Fields, continued





Specify the number of seconds that the controller and host wait for a connection verification message before declaring a communications failure for the secondary path. The controller and host send these messages to each other during periods of low system activity to confirm that the secondary path is operating correctly. You can choose 40 or 80 seconds.


For example, if you specify 40 seconds in this field, the controller receives a connection verification message every 10 seconds during periods of low system activity. If the controller does not receive at least one message within 40 seconds, it declares the secondary path to be in communications failure.

If a communications failure occurs, the following connections are attempted simultaneously:

The cluster tries to re-establish a connection with the host on the secondary communications path at the rate specified in the After connection failure, controller attempts to reconnect every XX seconds field in the Secondary tab.




Enter the event that the controller activates when a communications failure occurs on the secondary communications path. You can double-click on the field to display a list of events.

Specify an event that is located on the controller. If the event is located on another controller, the system displays an error message.

NOTE: This controller is responsible for secondary communications.



Cluster Tab for iSTAR Classic & iSTAR Pro



Configuring Communications with the Master

The Cluster tab in the Cluster dialog box lets you configure communications among cluster members and the master.

To Configure Cluster Communications

1. From the Cluster dialog box, click the Cluster tab. The Cluster tab opens, shown in Figure 1-22.

Figure 1-22: Cluster Tab




Table 1-12: Cluster Tab Fields

Field Description

Controllers attempt to connect to cluster master every n seconds

Specify the number of seconds that a controller waits between attempts to connect to the master. Use the Controllers declare connection failure after failed attempts field in the Cluster tab to specify the number of connection attempts a controller makes before a communications failure is declared for the controller.

Controllers declare connection failure after n failed attempts

Specify the number of attempts that a controller makes to first connect to the master before the controller is declared to be in communications failure. If a connection is established, the controller and master use connection verification messages to maintain the connection. See the While connected, declare connection failure if no message for XX seconds field in the Cluster tab for more information.

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 master, the controller attempts to connect to the alternate master, which passes the controller’s messages to the host. At the same time, the controller tries to re-establish a connection with the master at the rate specified in the After connection failure, controller attempts to reconnect every XX seconds field in the Cluster tab.

If the secondary communications path does not use an alternate master, the controller attempts to connect to the master forever or until a connection is established. The controller attempts to connect to the master at the rate specified in the After connection failure, controller attempts to reconnect every XX seconds field in the Cluster tab.

The controller broadcasts a request across its subnet for the master’s IP Address. The master responds to the request. If the master 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 Pro Installation and Configuration Guide for information.

After connection failure, controllers attempt to reconnect every n seconds

Specify the number of seconds that controllers wait between attempts to re-connect to the master. This field sets the rate at which controllers attempt to reconnect or connect to the master after a communications failure occurs between the master and the controller.




Specify the number of seconds that a controller and the master wait for connection verification messages before the controller is declared to be in communications failure. The master and the controller send these messages to each other during periods of low system activity to confirm that the path between them is operating correctly.

The sum of this value and the value you entered in the While connected, declare connection failure if no message field in the Primary tab must be less than or equal to 85. If you entered 40 seconds in the Primary tab, you can enter a value between 1 and 45 seconds here; if you specified 80 seconds in the Primary tab, you can enter a value between 1 and 5 seconds here.

The value you specify in this field determines how often the connection verification message is sent between the master and controllers — if you specify 40 seconds, the message is sent every 10 seconds — if you specify 5 seconds, the message is sent every 1.25 seconds.

For example, if you specify 40 seconds in this field, controllers receive connection verification messages every 10 seconds during periods of low system activity. If a controller does not receive at least one message within 40 seconds, the controller is declared to be in communications failure.



If the secondary communications path does not use an alternate master, the controller attempts to re-connect to the master forever or until a connection is established. The controller attempts to connect to the master at the rate specified in the After connection failure, controller attempts to reconnect every XX seconds field in the Cluster tab.

The controller broadcasts a request across its subnet for the master’s IP Address. The master responds to the request. If the master does not respond in a set amount of time and the iSTAR Configuration Utility is configured for auto-response, the utility can respond to the controller. See the iSTAR Pro Installation and Configuration Guide for information.

Table 1-12: Cluster Tab Fields, continued

Field Description

Misc Tab for iSTAR Classic & iSTAR Pro



Configuring the Secondary Communications Test

The secondary communications path is periodically tested to verify that the connection will function correctly in the event of a failure on the primary communications path. The Misc tab in the Cluster dialog box lets you configure the test for the secondary communications path.

This tab also lets you configure the maximum number of unacknowledged messages that are permitted for the controllers in the cluster.

To Configure the Test for the Secondary Communications Path

1. From the Cluster dialog box, click the Misc tab. The Misc tab opens, shown in Figure 1-23.

Figure 1-23: Misc Tab


NOTE The Secondary Communications Test is not supported in this version of C•CURE 800/8000.



Table 1-13: Misc Tab Fields

Box Description Action to take

Secondary Communication Test

Controller automatically performs test every n hours

Specify the number of hours that the controller responsible for secondary communications waits between test messages. The controller sends these messages to the host via the secondary communications path to let the host know that the secondary communications path will operate correctly if a failure occurs on the primary communications path.

When test fails, controller will repeat test every (hh:mm:ss)

Specify the time that the controller waits between attempts to retest the secondary communications path. The controller retests the secondary communications path when the first test fails.

Activate this event while secondary test failure

Enter the event that the controller activates when the test of the secondary communications path fails. You can double-click on the field to display a list of events.

Specify an event that is located on the controller responsible for the secondary communications path. If the event is located on another controller, the system displays an error message.

Maximum number of unacknowledged messages for each controller

Specify the maximum number of unacknowledged messages that are allowed for each controller in the cluster.

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.

Global APB Tab for iSTAR Classic & iSTAR Pro



Configuring Antipassback for the Cluster

The Global APB tab in the Cluster dialog box lets you specify if the cluster enforces both cluster antipassback and iSTAR Global Antipassback. It also allows you to specify how the cluster handles antipassback during communications failure.

To Configure Antipassback for the Cluster

1. From the Cluster dialog box, click the Global APB tab. The Global APB tab opens, shown in Figure 1-24.

Figure 1-24: Global APB Tab




Table 1-14: Global APB Tab Fields

Field Description

Cluster antipassback communications failure mode:

If you are using Cluster Antipassback, you can specify how the Controller enforces antipassback when in communications failure. You can select:

No Access: where access is denied if any controller in the cluster is in communications failure, and this controller is not the owner of the presented card.

Local: where the iSTAR uses locally available information to grant or deny access. If this information is insufficient, the iSTAR will admit the presented card.

For information about Global Antipassback, refer to the CCURE 800/8000 Advanced User Guide.

Cluster enforces iSTAR Global antipassback as well as iSTAR Cluster antipassback

Select this option if you want the cluster to share Antipassback information with other antipassback clusters.

NOTE: If you select this option, The Cluster Antipassback Failure Mode will be unavailable. You will need to use the iSTAR Global Antipassback Comm. Failure Mode specified in the System Variables.

For more information about Global Antipassback, refer to the CCURE 800/8000 Advanced User Guide.


2

Configuring C•CUREiSTAR eX Controllers

and Clusters

This chapter explains how to configure the iSTAR eX Controllers and Clusters in the C•CURE System. To install and configure hardware for iSTAR eX controllers and clusters, consult the iSTAR eX Installation and Configuration Guide.

In this chapter


Configuration Overview.............................................................................................. 2-10

Configuring iSTAR eX Controllers............................................................................. 2-11

Main Board Tab ............................................................................................................. 2-19

Serial Ports Tab.............................................................................................................. 2-25

Cluster Communications Overview........................................................................... 2-29

Maintaining Cluster Communications ...................................................................... 2-33

Configuring Clusters .................................................................................................... 2-35

Primary Tab ................................................................................................................... 2-40

Secondary Tab ............................................................................................................... 2-44

Cluster Tab ..................................................................................................................... 2-48

Misc Tab.......................................................................................................................... 2-51

Global APB Tab ............................................................................................................. 2-53

Encryption Tab .............................................................................................................. 2-55




The C•CURE iSTAR eX controller is an intelligent controller for networked security systems. C•CURE iSTAR eX controllers communicate with the C•CURE system server (acting as a database and journal host) and the system security hardware, providing direct control of events and system activity. Controllers are organized into groups called Clusters that allow network communications.

This chapter explains how to configure the controller software components to work with C•CURE 800/8000. To install and configure hardware for the controller, see the iSTAR eX Installation and Configuration Guide.

The core component of the iSTAR controller is the General Controller Module (GCM)- an embedded microprocessor-based controller card that supports Wiegand readers, inputs, and outputs. The Power Management Board (PMB) provides access control functionality by supporting additional RM readers, outputs, and inputs. The PMB also provides power management, battery charging, and system backup capabilities.

ISTAR eX Modules

GCM

The GCM includes on-board reader processors that can support up to four direct-wired Wiegand read head type modules (Wiegand Card and/or Proximity Card). GCM also supports four Relay and Open Collector Outputs, one CF Slot and two Ethernet 100BaseT connections. Table 2-1 summarizes the capabilities of GCM.

PMB

The Power Management Board (also referred to as PMB) includes on-board reader processors that can support up to four RM reader bus connections. The PMB also supports eight I/8 input and R/8 output modules. A total of sixteen Wyreless Readers can be connected to the Power Management Board. Table 2.1 summarizes the capabilities of the PMB.

NOTE The maximum configuration per iSTAR eX Controller is 88 inputs, 80 outputs, 4 readers or 16 Wyreless Readers.



GCM Features

Dual Network Connections

The GCM includes two RJ-45 jacks for access to two 100BaseT Ethernet connections.


One or more controllers can be configured for communications purposes into user-defined groups called Clusters. Clusters have primary communications paths to the host that use Masters to control communications among cluster members and the host over the network. Clusters also support a backup communications path, the secondary communications path. The cluster can use the secondary path to communicate with the host when a communications failure occurs on the primary path. Secondary paths can use either the master or an Alternate Master.

Communications among iSTAR controllers provide distributed functionality at the controller level that is not typically available on security management systems.

iSTAR eX controllers must have their own separate clusters while iSTAR Pro/Classic controllers have their own separate clusters. This is because the method of encryption is different for each type of controller.

Firmware Upgradable

The GCM includes on-board Flash ROM, a non-volatile memory, for storage of the iSTAR’s firmware and communication protocol parameters, such as MAC address, and IP and gateway router IP addresses. Firmware upgrades involve a simple download initiated from a host.


The C•CURE journal and database host, networked to iSTAR, provides support for initial setup, managing peripheral hardware and generating activity reports.



Connecting Security Devices to the iSTAR eX

The following types of access control devices are supported by the iSTAR eX:

Inputs

Relay Outputs

Collector Outputs

Readers

Wyreless Readers


Inputs


A supervised input reports on the status of the wiring between the controller and the switch. If that wiring is cut, the system reports an open circuit. If someone tries to jumper across the wiring (prevent the device from reporting), the system reports a shorted circuit. Supervised inputs can report a total of five conditions to the controller: Short, Open Loop, Line Fault,

Table 2-1: iSTAR eX Module Capabilities

Modules Reader Sources Input Sources Output Sources

GCM 4 Direct Wiegand Readers

16 Special Supervised Inputs (1K, 5K or 10K)

4 Relay Outputs on GCM

4 Open Collector Outputs

2 Ethernet 100BaseT connections

I CF Slot

PMB 4 RM Reader Bus connections

16 Wyreless Readers

8 I/8 Input Modules 8 RM 4/4E Inputs (2 per reader)

8 RM 4/4E Outputs (2 per reader)



Inactive, or Active. The iSTAR eX can supervise with either one or two resistors or not supervise at all. The single resistor can be either 5K or 10K ohm. The double resistors can be 1K, 5K or 10K ohm.

An unsupervised input does not monitor the wiring. Unsupervised inputs can report two conditions to the panel: Active or Inactive. The method of supervision or non-supervision selected is the same for all sixteen inputs on the GCM.

Relay Outputs

An output is a software definition that associates an event or input to a relay on the controller or add-on module. The relay then activates or deactivates devices, such as flood lights and alarm devices. The iSTAR eX GCM provides four Relay and four Open Collector Outputs.

OC Outputs

Open Collector Outputs provide +12 VDC on a common pin and a ground drive on the other pin. The current draw of the circuit is limited to 1.5 amps and 2.5 amps with an external power supply.

Readers


Optional Boards

Optional boards let you attach additional inputs and outputs to the controller. iSTAR eX PMB controllers support these optional boards:











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.







A second Ethernet connection between the master and the host.

A connection between the host and another cluster member, the Alternate Master, that assumes responsibility for communications for the cluster.

The secondary communications path can be an Ethernet connection from the master or an Ethernet connection from another cluster member.

iSTAR eX clusters use AES encryption and are capable of supporting FIPS 140-2.



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. Current technology, such as the apC/8X, provides local control of only a few actions, and since apC/8Xs cannot be added to clusters or communicate directly with controllers, they cannot share information as iSTAR controllers can. The host controls most actions for the apC/8X.

Example:

If an apC/8X is in communications failure, an input on the panel can activate only one output or output group on the panel; however, if an iSTAR master is in communications failure with the host, any input on any controller in the cluster can activate any output or output group on any controller in the cluster.




Events

Controllers can control the activation and deactivation of events and timed actions locally and on other controllers in the cluster. For example, if a Forced Door Event activates outputs on another controller in the cluster, the controller with the Forced Door Event, not the host, activates the outputs. When you configure the Forced Door Event, you must specify the controller to which you want to download the event. Only one controller or the C•CURE server controls an event. See the C•CURE 800/8000 Software Configuration Guide for information.

System Activity



Controllers allow the sharing of cardholder anti-passback status among each other in a C•CURE area within a cluster. Global anti-passback lets you set up areas with doors on any controller in the cluster. See the C•CURE 800/8000 Software Configuration Guide for information.


Configuration Overview



Configuring the iSTAR controllers involves setting up the hardware and configuring the software components. See the iSTAR eX Installation and Configuration Guide for instructions about setting up controllers and related hardware.

The Table 2-2 provides a list of tasks for software configuration of iSTAR controllers:

NOTE Before configuring a cluster, make sure you know each cluster member’s MAC address. The MAC address is built into the GCM and cannot be changed. You can find controller’s MAC address on a label attached to the GCM. See the iSTAR eX Installation and Configuration Guide for information.


Stage Task See...

1 Use the Controller dialog box in the C•CURE 800/8000 administration application to configure iSTAR controllers.

“Configuring iSTAR eX Controllers” on page 2-11 for information.

2 Use the iSTAR Cluster dialog box in the C•CURE 800/8000 administration application to configure clusters.

“Configuring Clusters” on page 2-35 for information.



The iSTAR eX Installation and Configuration Guide.

Configuring iSTAR eX Controllers



The Controller dialog box lets you configure the GCM and PMB.




2. Click New to create a new controller. The Select Panel Type dialog box appears, shown in Figure 2-4 on page 2-12.

- or -





a. Select iSTAReX


Figure 2-5: Controller Dialog Box for iSTAR eX

3. Provide the following information and click OK to save the controller configuration and close the Controller dialog box.



If your system is using the Distributed Holidays mode and there is no Holiday list assigned to this iSTAR, the system displays a warning message similar to the following, but still allows you to save the controller configuration. (For detailed information, see “Configuring Holiday Lists for a Controller” on page 2-17.)




Online Click this check box to put the controller online. When a controller is online, C•CURE 800/8000 can communicate with it. If you put a controller offline, the following occurs:







Identification, continued Online, continued If you delete a controller, it is ignored by the C•CURE 800/8000 host and cannot communicate with other cluster members.

To stop a controller from performing access control decisions:

Put any attached readers offline. (Do not put the controller offline before you put these objects offline.)

- or -


iSTAR hardware Sub-type A read-only field displaying the controller sub-type: iSTAR Pro/Classic or iSTAR eX.


General Tab



The controller is in time zone:










Holidays Lists NOTE: This button is available only if your C•CURE 800/8000 system is operating in Distributed Holidays mode—enabled on the System Variables System tab. (If this button is unavailable, the system is operating in Default Holiday mode and any configured Holiday Lists are automatically downloaded to all iSTAR controllers.)


Click this button to open the Holiday Lists dialog box to select up to 24 Holiday Lists to download to this controller. For detailed information, see “Configuring Holiday Lists for a Controller” on page 2-17.

MAC Addresses Ethernet #1 Hardware (MAC) Address

Enter the Hardware 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 of a controller’s MAC address are set at 00-50-F9.

Onboard Ethernet #1 Obtain an IP Address from a DHCP Server



Onboard Ethernet #2 Obtain an IP Address from a DHCP Server








Host activates this event when controller is in communications failure

Enter the name of the event that is activated when this controller goes into communications failure. You can double-click on this field to open the Event Selection browser where you select, edit, or create an event.



If this controller is a cluster member, the host activates the specified event any time the master goes into communications failure. The event is deactivated when communications are reestablished with the host using either the primary or secondary path.





Other Tabs

Main Board This tab lets you configure the output and inputs on the GCM and RM LCD messages. See “Main Board Tab” on page 2-19 for more information.

Serial Ports This tab lets you configure serial ports for the controller. See “Serial Ports Tab” on page 2-25 for more information.












For more information about these modes and how to change them and Holiday Lists in general, see “Holiday Lists” in the C•CURE 800/8000 Software Configuration Guide and “Setting System Variables” in the C•CURE 800/8000 System Maintenance Guide.

Main Board Tab


Main Board Tab

Configuring the Main Board

The Main Board tab in the Controller dialog box lets you define Readers, Inputs and Outputs on the iSTAR eX and RM LCD messages for the controller. The options available for selection on the Main Board dialog box are as follow:

Special Purpose Inputs

Tamper input activates when the controller cabinet is opened or removed from its mounting surface.

AC power fail input monitors the AC power failure output of a battery backup unit. When this alarm input activates, it specifies that the iSTAR eX has lost its primary power source and is operating on batteries.

Low battery input activates when the emergency battery is running low on power.

Options Common to the Entire Panel

RM LCD messages specifies the set of RM Reader LCD messages to assign to the iSTAR eX controller.

Supervising resistor configuration The iSTAR eX can supervise with either one or two resistors. These resistors can have one resistor with 5K or 10K ohm resistivity and two resistors with 1K, 5K or 10K ohm resistivity.

General Purpose Inputs

General Purpose Inputs 1 to Input 16 are automatically configured using the values from the default input definition. To view or edit the input, click the input’s View button.

Main Board Tab


Onboard Wiegand Readers

Onboard Wiegand Readers 1 to 4 are automatically configured using the values from the default reader definition. To view or edit the input, click the reader’s View button.

Relay Outputs

Relay Outputs 1 to 4 are automatically configured using the values from the default output definition. To view or edit the output, click the output’s View button.

Open Collector Outputs

Open Collector Outputs 1 to 4 are automatically configured on GCM using the values from the default output definition. To view or edit the output, click the output’s View button.


1. From the Controller dialog box, click the Main Board tab. The Main Board tab opens for the controller, shown in Figure 2-7.

Main Board Tab


Figure 2-7: Main Board Tab for iSTAR eX





Tamper Click this check box to configure the Tamper input. The Tamper input activates when the controller cabinet is opened or removed from its mounting surface.The system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Tamper check box in the Controller dialog box, deletes the Tamper input.

Main Board Tab


Special Purpose Inputs (cont.)

AC power fail input Click this check box to configure the AC power fail input. AC power fail input monitors the AC power failure output of a battery backup unit. When this alarm input activates, it specifies that the iSTAR eX has lost its primary power source and is operating on batteries. The system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the AC power fail input check box in the Controller dialog box, deletes the AC powerfail input.

Low battery input Click this check box to configure the Low Battery input. Low battery input activates when the emergency battery is running low on power. The system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.





Main Board Tab




Supervising resistor configuration

Values for resistor configurations are described in terms of NC (Normally Closed) or NO (Normally Open), resistor placement, and supervising resistor value.

Resistor placement refers to how many EOL (End Of Line) resistors are used and where they are placed in relation to the switch. Settings are “Non-supervised”, “Single EOL”, or “Double EOL”.

Non-supervised - the user wires no external resistors.

Single EOL - the user wires a single EOL resistor.

Double EOL - the user wires two EOL resistors, one in parallel and one in series with the switch.

Resistor values are labeled as 1k/5k/10k (in Ohms). In the Double EOL cases, both resistors have the same value.

NO Double EOL 1K is the default value, and the traditional Software House method of supervision.

Options common to entire panel (cont.)


When selected, personnel records that would not normally be downloaded to a iSTAR controller due to lack of clearance at any of the doors under its control are downloaded to the iSTAR panel. This selection allows the availability of such personnel records for use with the Conditional Access feature. This option should be selected if the iSTAR panel has any doors configured for Conditional Access. The iSTAR eX will store more cards when this selection is made.

This selection can be made only when the controller is offline. Making this selection causes a full personnel download to the panel, once it is put back online.


General Purpose Inputs 1 to Input 16

Click the check box next to the input that you want to configure. The system automatically configures the input using the values from the default input definition. To view or edit an input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Input check box in the Controller dialog box deletes the input.



Main Board Tab



Onboard Wiegand Readers 1 to 4

Click the check box next to the reader that you want to configure. The system automatically configures the reader using the values from the default reader definition. To view or edit a reader, click the output’s View button. See “Configuring Outputs” on page 6-13, for more information.


Deselecting the Reader check box in the Controller dialog box deletes the output.

Relay Outputs Relay Outputs 1 to 4 Click this check box to configure the relay output on the GCM. The system automatically configures the relay output using the values from the default output definition. To view or edit the relay output, click the output’s View button. See “Configuring Outputs” on page 6-13 for more information.

If Online is the default setting for the relay output and you do not deselect this option in the Output dialog box, the relay output is set online and downloaded after you click OK in the Controller dialog box.

Deselecting the Output check box in the Controller dialog box, deletes the output.

Open Collector Outputs

Open Collector Outputs 1 to 4

Click this check box to configure the Open Collector (OC) output on the GCM. The system automatically configures the OC output using the values from the default OC output definition. To view or edit the output, click the output’s View button. See “Configuring Outputs” on page 6-13 for more information.

If Online is the default setting for the output and you do not deselect this option in the OC Output dialog box, the output is set online and downloaded after you click OK in the Controller dialog box.

Deselecting the OC Output check box in the Controller dialog box, deletes the output.

NOTE The first time you configure an input, output, or reader, you must do so from the Controller dialog box for the security object. After a security object is defined, you can edit its definition from the Controller dialog box or by selecting the item from the Hardware drop-down menu on the C•CURE 800/8000 Administration application.



Serial Ports Tab


Serial Ports Tab

Configuring the Serial Ports

The Serial Ports tab in the Controller dialog box let you define security objects that are connected to the COM1 and the COM2 ports. COM 1 and COM 2 can be configured to support either RM bus readers or Wyreless readers. If RM is selected, then up to four RM reader devices and eight I/8 and eight R/8 devices can be configured. If Wyreless, then up to sixteen Wyreless Panel Interface Modules (PIMs) can be selected, with a maximum of sixteen Wyreless readers, regardless of the number of PIMS.

To configure the serial port devices

1. From the Controller dialog box, click the Serial Ports tab. The Serial Ports tab opens for the controller, shown in Figure 2-8.

Figure 2-8: Serial Ports Tab

2. Provide the shown in Table 2-5 on page 2-26.

Serial Ports Tab


Figure 2-9: RM Modules on Serial COM1 Dialog Box

3. When you click the Configure Device on COM1 or COM2 button, with the RM bus protocol selected, the RM Modules on Serial COM1 dialog box will appear. Refer to Figure 2-9 which shows the eight I/8 Input and R/8 Output Boards and four Readers. Click the View buttons to configure up to eight input and output boards and up to four readers.

Table 2-5: Serial Ports Tab Fields


COM1 Ports Protocol on COM1 Select the type of connection. The two choices are RM or Wyreless.

Configure port on COM1 If RM is selected, then up to four RM reader devices, eight I/8 and eight R/8 devices can be configured (see Figure 2-9). If Wyreless is selected, then up to sixteen Wyreless Panel Interface Modules (PIMs) can be configured, with a maximum of sixteen Wyreless readers, regardless of the number of PIMs. See Figure 2-10 on page 2-27 and Figure 2-11 on page 2-28.

COM2 Ports Protocol on COM2 Select the type of connection. The two choices are RM or Wyreless.

Configure ports on COM2 If RM is selected, then up to four RM reader devices, eight I/8 and eight R/8 devices can be configured (see Figure 2-9). If Wyreless is selected, then up to sixteen Wyreless Panel Interface Modules (PIMs) can be configured, with a maximum of sixteen Wyreless readers, regardless of the number of PIMs. See Figure 2-10 on page 2-27 and Figure 2-11 on page 2-28.

Serial Ports Tab


4. When you click the Configure Device on COM1 or COM2 button with Wyreless protocol, the Wyreless Access PIM Modules on Serial COM2 dialog box will appear, as shown in Figure 2-10. Click the View buttons to configure up to sixteen PIM devices on Communications Port 2.

Figure 2-10: Wyreless Access PIM Modules on Serial COM2 Dialog Box

5. When you click a View button, the Access Panel Interface on the iSTAR eX Controller dialog box will appear, as shown in Figure 2-11 on page 2-28.

NOTE You can configure four Wiegand Readers on GCM or four RM Readers on the PMB. You can also configure three of one type of reader on GCM and one on the PMB or a pair on each, but never more than a total of four. You can configure up to sixteen Wyreless Readers and the first four use up the RM/Direct Readers slots.

Serial Ports Tab


Figure 2-11: Wyreless Access Panel Interface Dialog Box

6. Select Tamper to enable the View button for the PIM Input Tamper selection.

7. To select Readers to associate with the PIMs on Communications Port 2, click in check box among the sixteen listed readers. If a reader has been configured elsewhere on the board (RM/Direct or another PIM), selection will not be enabled.

8. Click a View button to configure a reader to associate with the PIMs on Communications Port 2.

Cluster Communications Overview









The master connects directly to the host using a network connection.





Use the C•CURE Administration Application to configure controllers and the cluster. See “Configuring iSTAR eX Controllers” on page 2-11and “Configuring Clusters” on page 2-35 for information.




After downloading information from the host, the master auto-configures its cluster members. Cluster members then reboot and establish connections with the master. See the iSTAR eX Installation and Configuration Guide for more information.















Example:


Use the Cluster dialog box in the C•CURE System Administration Application to configure connection verification messages for the master, host, and cluster members. See “Configuring Clusters” on page 2-35 for more information.



A second network connection between the master and the host.

A network connection between another controller in the cluster - the alternate master - and the host.

The configuration of the secondary communications path (alternate master or a secondary connection from the master) determines how controllers re-establish cluster communications when the primary path fails. See “Maintaining Cluster Communications” on page 2-33 for more information.




Use the Secondary tab in the Cluster dialog box in the C•CURE System Administration Application to configure the secondary communications path. See “Configuring the Secondary Communications Path” on page 2-44 for more information.

Maintaining Cluster Communications





If the master fails, the following configurations of the secondary communications path determine how cluster communications are re-established:


If the master loses its connection with the host and the secondary communications path is another connection between the master and the host, the following occurs:





If the master loses its connection with the host and the secondary communications path is a connection between an alternate master and the host, the following occurs:




See Figure 2-12 on page 2-34.



Figure 2-12: Host Communications Reestablished via an Alternate Master

Configuring Clusters



The iSTAR Cluster dialog box lets you configure clusters by performing the following tasks:





Configure a test of the secondary communications path.


1. From the C•CURE 800/8000 Administration application, choose Hardware->iSTAR Cluster from the menu bar. The iSTAR Cluster Selection browser appears, shown in Figure 2-13 on page 2-36.

NOTE The Secondary Communications Test is not supported in this version of C•CURE System.



Figure 2-13: iSTAR Cluster Selection Browser

2. Click New to create a new cluster

- or -

select a cluster and click Edit to edit a cluster’s configuration.

The Cluster dialog box appears, shown in Figure 2-14 on page 2-37.









You cannot select the method of communication between host and controller on the Primary or Secondary tabs if the cluster is online. To put the cluster offline, deselect the Online check box, click OK to close the dialog box, and then re-open the dialog box.


General Tab



Edit Controllers Click this button to open the CCURE Controller Selection browser where you can select, edit, or create controllers. See “Configuring iSTAR eX Controllers” on page 2-11 for information.



Available Controllers cont.

Add/Add All/Remove/Remove All buttons

Click these buttons to move controllers between the Controllers in the cluster and Available Controllers boxes. For example, if you click Add All, all controllers in the Available Controllers box are moved to the Controllers in this cluster box. Controllers listed in the Controllers in this cluster box are members of the cluster.

Controllers in the Cluster

Displays a list of controllers that are assigned to the cluster. A controller must be assigned to a cluster for C•CURE 800/8000 to communicate with the controller. Use the Add or Add All buttons to add controllers to the cluster by moving them from the Available Controllers box to the Controllers in this cluster box. Use the Remove and Remove All buttons to take controllers out of the cluster.

Other Tabs


Secondary This tab lets you configure the secondary communications path for the cluster. See “Configuring the Secondary Communications Path” on page 2-44 for information.


Misc This tab lets you configure a communications test for the secondary communications path and the maximum number of unacknowledged messages allowed for each controller. See “Configuring the Secondary Communications Path” on page 2-44 for information.


Encryption This tab lets you configure encryption for the controller. See “Configuring Encryption for the Cluster” on page 2-55 for information.



Primary Tab


Primary Tab




1. From the Cluster dialog box, click the Primary tab. The Primary tab opens for the cluster, shown Figure 2-15.




Primary Tab


















The master broadcasts a request across its subnet for the host’s IP Address. If the iSTAR Configuration Utility is configured for auto-response, it responds to the master. See the iSTAR eX Installation and Configuration Guide for information.

Primary Tab

















Secondary Tab


Secondary Tab








Secondary Tab












Cluster Tab


Cluster Tab







Cluster Tab



Field Description








The controller broadcasts a request across its subnet for the master’s IP Address. The master responds to the request. If the master 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.



Cluster Tab










The controller broadcasts a request across its subnet for the master’s IP Address. The master responds to the request. If the master does not respond in a set amount of time and the iSTAR Configuration Utility is configured for auto-response, the utility can respond to the controller. See the iSTAR eX Installation and Configuration Guide for information.


Field Description

Misc Tab


Misc Tab




To configure the test for the secondary communications path





Misc Tab



Field Description





Controller activates this event when secondary test fails






Global APB Tab


Global APB Tab


The Global APB tab in the Cluster dialog box lets you specify if the cluster enforces both cluster antipassback and iSTAR eX Global Antipassback. It also allows you to specify how the cluster handles antipassback during communications failure.





Global APB Tab



Field Description










Encryption Tab


Encryption Tab

Configuring Encryption for the Cluster

The Encryption tab in the Cluster dialog box lets you configure encryption for the iSTAR eX cluster.

To Configure Encryption for the Cluster

1. From the Cluster dialog box, click the Encryption tab. The Encryption tab opens, shown in Figure 2-20.

Figure 2-20: Encryption Tab

2. Select the information shown in Table 2-12 on page 2-56.

Encryption Tab


Table 2-12: Encryption Tab Fields

Field Description

Encrypt Traffic You can select:

Encrypt traffic - Select this option to have the cluster encrypt traffic between iSTAR eX controllers. This option is selected by default and is not available in the current release.

Non-FIPS mode uses AES encryption for communications between the Host, Master or Members of the cluster. See the iSTAR eX Configuration Guide for details.

FIPS 140-2 validate mode: The cluster uses AES encryption and operates in “dark” mode, a state in which none of the controllers is visible and ICU will not function on the cluster members. See the iSTAR eX Configuration Guide for details.


3

Configuring C•CUREiSTAR Edge


This chapter explains how to configure the iSTAR Edge Controllers and Clusters in the C•CURE System. To install and configure hardware for iSTAR Edge controllers and clusters, consult the iSTAR Edge Installation and Configuration Guide.

In this chapter


Configuration Overview.............................................................................................. 3-11

Configuring iSTAR Edge Controllers ........................................................................ 3-12

Main Board Tab ............................................................................................................. 3-20

Serial Ports Tab.............................................................................................................. 3-29

Cluster Communications Overview........................................................................... 3-32

Maintaining Cluster Communications ...................................................................... 3-36

Configuring Clusters .................................................................................................... 3-38

Primary Tab ................................................................................................................... 3-43

Secondary Tab ............................................................................................................... 3-47

Cluster Tab ..................................................................................................................... 3-51

Misc Tab.......................................................................................................................... 3-54


Global APB Tab ............................................................................................................. 3-56

Encryption Tab .............................................................................................................. 3-58




The C•CURE iSTAR Edge controller is an intelligent controller for networked security systems. C•CURE iSTAR Edge controllers communicate with the C•CURE system server (acting as a database and journal host) and the system security hardware, providing direct control of events and system activity. Controllers are organized into groups called Clusters that allow network communications.

iSTAR Edge Controller Features


One or more controllers can be configured for communications purposes into user-defined groups called Clusters. Clusters have primary communications paths to the host that use Masters to control communications among cluster members and the host over the network. Clusters also support a backup communications path, the secondary communications path. The cluster can use the secondary path to communicate with the host when a communications failure occurs on the primary path. Secondary paths can use either the master or an Alternate Master. iSTAR Edge only has one Ethernet connection so it cannot support the secondary communication path.

Communications among iSTAR controllers provide distributed functionality at the controller level that is not typically available on security management systems.

iSTAR Edge and iSTAR eX controllers can be mixed within clusters, while iSTAR Pro/Classic controllers can be mixed within clusters. The iSTAR Edge and the iSTAR eX use one type of encryption and the iSTAR Pro and iSTAR Classic use a different type of encryption and therefore cannot be in the same cluster.

The iSTAR Edge is available with two readers or four readers. The two-reader model is not upgradable to a four reader module.



Firmware Upgradable

The iSTAR Edge includes on-board Flash ROM, a non-volatile memory, for storage of the iSTAR’s firmware and communication protocol parameters, such as MAC address, and IP and gateway router IP addresses. Firmware upgrades involve a simple download initiated from a host.


The C•CURE journal and database host, networked to the iSTAR Edge provides support for initial setup, managing peripheral hardware and generating activity reports.

Connecting Security Devices to the iSTAR Edge

The following types of access control devices are supported by the iSTAR Edge:

Inputs

Relay Outputs

Readers (including any device that uses Wiegand or magnetic signaling)


Auxiliary outputs to power passive infrared sensors (PIRS)

Table 3-1: iSTAR Edge Module Capabilities

Module Reader Sources Input Sources Output Sources

Edge 2 Direct Wiegand Ports

3 RM Ports

8 Special Supervised or Unsupervised Inputs

Dual 1K, 1K, 5K, 10K or single

See Table 3-4 on page 3-24 for more information about inputs and outputs.

8 Relay Outputs

1 Ethernet 100BaseT connection

2 Auxiliary Outputs



Inputs


A supervised input reports on the status of the wiring between the controller and the switch. If that wiring is cut, the system reports an open circuit. If someone tries to jumper across the wiring (prevent the device from reporting), the system reports a shorted circuit. Supervised inputs can report a total of five conditions to the controller: Short, Open Loop, Line Fault, Inactive, or Active. The iSTAR Edge can supervise with either one or two resistors or not supervise at all. The single resistor can be either 5K or 10K ohm. The double resistors can be 1K, 5K or 10K ohm.

An unsupervised input does not monitor the wiring. Unsupervised inputs can report two conditions to the panel: Active or Inactive. The method of supervision or non-supervision selected is the same for all inputs on the iSTAR Edge.

Relay Outputs

An output is a software definition that associates an event or input to a relay on the controller or add-on module. The relay then activates or deactivates devices, such as flood lights and alarm devices. The iSTAR Edge provides four dry Form-C relay outputs.

Readers


NOTE Unsupervised inputs must not be used in a protective circuit, such as REX or Door State Monitor.



Optional Boards

Optional boards let you attach additional inputs and outputs to the controller. iSTAR Edge controllers support these optional boards:


I/8 - CSI provides eight additional inputs to the controller providing a variety of input supervision resistance configurations.









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.







A second Ethernet connection between the master and the host (iSTAR eX only).

A connection between the host and another cluster member, the Alternate Master, that assumes responsibility for communications for the cluster (iSTAR Edge or iSTAR eX).

The secondary communications path can be an Ethernet connection from the master or an Ethernet connection from another cluster member (iSTAR eX only).

iSTAR Edge/eX clusters use AES encryption, and are capable of supporting FIPS 140-2.



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. Other technology, such as the apC/8X, provides local control of only a few actions, and since apC/8Xs cannot be added to clusters or communicate directly with controllers, they cannot share information as iSTAR controllers can. The host controls most actions for the apC/8X.

Example: If an apC/8X is in communications failure, an input on the board can only activate the outputs on the same board; however, if an iSTAR master is in communications failure with the host, any input on any controller in the cluster can activate any output or output group on any controller in the cluster. In addition, events within the cluster will continue to function.




Events

Controllers can control the activation and deactivation of events and timed actions locally and on other controllers in the cluster. For example, if a Forced Door Event activates outputs on another controller in the cluster, the controller with the Forced Door Event, not the host, activates the outputs. When you configure the Forced Door Event, you must specify the controller to which you want to download the event. Only one controller or the C•CURE server controls an event. See the C•CURE 800/8000 Software Configuration Guide for information.

System Activity



Controllers allow the sharing of cardholder anti-passback status among each other in a C•CURE area within a cluster. Global anti-passback lets you set up areas with doors on any controller in the cluster. See the C•CURE 800/8000 Software Configuration Guide for information.





Configuring the iSTAR controllers involves setting up the hardware and configuring the software components. See the iSTAR Edge Installation and Configuration Guide for instructions about setting up controllers and related hardware.

The Table 3-2 provides a list of tasks for software configuration of iSTAR controllers:

NOTE Before configuring a cluster, make sure you know each cluster member’s MAC address. The MAC address is built into the unit and cannot be changed. You can find controller’s MAC address on a label attached to the main board. See the iSTAR Edge Installation and Configuration Guide for more information.


Stage Task See...

1 Use the Controller dialog box in the C•CURE 800/8000 administration application to configure iSTAR controllers.

“Configuring iSTAR Edge Controllers” on page 3-12 for information.

2 Use the iSTAR Cluster dialog box in the C•CURE 800/8000 administration application to configure clusters.

“Configuring Clusters” on page 3-38 for information.



The iSTAR Edge Installation and Configuration Guide.

Configuring iSTAR Edge Controllers



The Controller dialog box lets you configure the iSTAR Edge.




2. Click New to create a new controller. The Select Panel Type dialog box appears, shown in Figure 3-4 on page 3-13.

- or -





a. Select iSTAR Edge


Figure 3-5: Controller Dialog Box for iSTAR Edge

3. Provide the information in Table 3-3 on page 3-14, and click OK to save the controller configuration and close the Controller dialog box.



If the system is using the Distributed Holidays mode and there is no Holiday list assigned to this iSTAR, the system displays a warning message similar to the following, but still allows you to save the controller configuration. (For detailed information, see “Configuring Holiday Lists for a Controller” on page 3-18.)




Online Click this check box to put the controller online. When a controller is online, C•CURE 800/8000 can communicate with it. If you put a controller offline, the following occurs:







Identification, continued Online, continued If you delete a controller, it is ignored by the C•CURE 800/8000 host and cannot communicate with other cluster members.

To stop a controller from performing access control decisions:

Put any attached readers offline. (Do not put the controller offline before you put these objects offline.)

- or -


iSTAR hardware Sub-type A read-only field displaying the controller sub-type: iSTAR Pro/Classic, iSTAR eX or iSTAR Edge.


General Tab



The controller is in time zone










Holidays Lists This button is available only if your C•CURE 800/8000 system is operating in Distributed Holidays mode—enabled on the System Variables System tab. (If this button is unavailable, the system is operating in Default Holiday mode and any configured Holiday Lists are automatically downloaded to all iSTAR controllers.)


Click this button to open the Holiday Lists dialog box to select up to 24 Holiday Lists to download to this controller. For detailed information, see “Configuring Holiday Lists for a Controller” on page 3-18.

MAC Addresses Hardware (MAC) Address Enter the Hardware MAC address for the controller. The MAC address is built into the controller and cannot be changed. You can find a controller’s MAC address on a label attached to the unit, displayed intermittently at the on-board LCD screen, or view the address using the iSTAR Configuration Utility. The first six nibbles of a controller’s MAC address are fixed at 00-50-F9.

Onboard Ethernet Obtain an IP Address from a DHCP Server



Suppress Power/LED Control

Turn off LEDs and LCD backlight

If selected, you can configure the LCD backlight and various status LEDs to always be off, regardless of the tamper state. Selecting this option does not affect the Power LED or the bright white external power indicator.

Default: Disabled (unchecked)

Onboard reader LED control Select the method used on this controller to drive the direct connect reader LEDs:

External Bi-Color (2-wire Red-Green)

3-Wire (Red-Green-Yellow)

1-Wire (A-B-C)






Host activates this event when controller is in communications failure

Enter the name of the event that is activated when this controller goes into communications failure. You can double-click on this field to open the Event Selection browser where you select, edit, or create an event.







Other Tabs

Main Board This tab lets you define the outputs, inputs, and options on the iSTAR Edge. See “Main Board Tab” on page 3-20 for more information.

Serial Ports This tab lets you configure serial ports for the controller. See “Serial Ports Tab” on page 3-29 for more information.



Main Board Tab


Main Board Tab

The Main Board tab in the Controller dialog box lets you define Readers, Inputs and Outputs on the iSTAR Edge and RM LCD messages for the controller. The options available for selection on the Main Board dialog box are as follow:


Tamper input - Activates when the iSTAR Edge controller cabinet is opened.

AC power fail input - Monitors the AC power failure output of a battery backup unit. When this input activates, it indicates that the UPS (Un-interruptible Power Supply) or apS has had an AC Power Failure and is now supplying battery power to the controller.

Low battery input - Activates when the UPS or apS emergency battery has reached a yellow warning level. Most UPS units have about 10 to 20 minutes of runtime when this condition occurs. It is recommend to shutdown the unit being powered by the low battery. Do not confuse this input with the Onboard Battery Low input.

Onboard Battery Low input - Activates when the onboard AA alkaline battery voltage is low, or if a battery is missing or disconnected. The Onboard battery voltage is important in that upon loss of external or PoE power, data is written to onboard non-volatile flash. The four onboard non-rechargeable batteries provide power to for the backup process, and maintaining the clock afterwards.

• Onboard battery low occurs when the voltage of all four batteries in series reaches 4.6 volts, or if a battery is missing.

• 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.

FAI State input - This input represents the state of the F (Fire) input coming into J40 of the iSTAR Edge. In other words, this is the fire alarm. The FAI (Fire Alarm Interface) activates the relays on the iSTAR Edge when the F input goes true.

Main Board Tab


FAI Relay Control input - This input 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 State input - This input represents the state of the K (Key) switch at J40 of the iSTAR Edge. The Key input is usually a key switch that momentarily closes when the key is inserted and rotated. The purpose of the key is to Unlatch the relays at the end of an emergency.

FAI

FAI (Fire Alarm Interface) is a hardware feature that is typically used to perform the following tasks when a fire alarm signal is present:

Unlock all doors when a fire is present

Remove power from various devices when fire is present.

The implementation could be a combination of of both scenarios by selecting the correct NO (Normally Open) or NC (Normally Closed) contact of the relay.

Magnetic Door Locks have power applied most of the time with a break in the power to open the door. You have to be aware of NO or NC in those cases.

All three of the FAI inputs (FAI State, FAI Relay Control, FAI Key State) support activating events. These events can be configured to activate alarms, send e-mails, run a Roll Call Report, etc. based on the state changes of the FAI inputs.

FAI Modes

There are two basic modes that can be configured at the controller:

FAI without Latch - This requires the F (Fire) input (NC) of J40 plus the individual enable switches for each relay (SW2 through SW5).

FAI with Latch and subsequent Unlatch - This method requires the F (Fire) input of the J40 plus the individual enable switches for each relay (SW2 though 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.

Main Board Tab


The FAI Mode chosen at the controller will determine how you might want to use the actions and events available in the software to provide modification of a fire alarm and related actions.

See the iSTAR Edge Installation and Configuration Guide for detailed information about wiring the FAI inputs.

Options Common to the Entire Panel

RM LCD messages specify the set of RM Reader LCD messages to assign to the iSTAR Edge controller.

Supervising resistor configuration. The iSTAR Edge can supervise with either one or two resistors. See Table 3-4 on page 3-24 for more information.


General Purpose Inputs 1 to 8 are automatically configured using the values from the default input definition. To view or edit the input, click the input’s View button.


Onboard Wiegand Readers 1 and 2 are automatically configured using the values from the default reader definition. To view or edit the input, click the reader’s View button.

Relay Outputs

Relay Outputs 1 to 4 are automatically configured using the values from the default output definition. To view or edit the output, click the output’s View button.

Main Board Tab


Main Board Configuration


1. From the Controller dialog box, click the Main Board tab. The Main Board tab opens for the controller, shown in Figure 3-7 on page 3-23.

Figure 3-7: Main Board Tab for iSTAR Edge

2. Provide the information shown in Table 3-4.

Main Board Tab






Supervising resistor configuration

Values for resistor configurations are described in terms of NC (Normally Closed) or NO (Normally Open), resistor placement, and supervising resistor value.

Resistor placement refers to how many EOL (End Of Line) resistors are used and where they are placed in relation to the switch. Settings are “Non-supervised”, “Single EOL”, or “Double EOL”.

Non-supervised - the user wires no external resistors.

Single EOL - the user wires a single EOL resistor.

Double EOL - the user wires two EOL resistors, one in parallel and one in series with the switch.

Resistor values are labeled as 1k/5k/10k (in Ohms). In the Double EOL cases, both resistors have the same value.

NO/NC Double EOL 1K is the default value, and the traditional Software House method of supervision.


When selected, personnel records that would not normally be downloaded to a iSTAR controller due to lack of clearance at any of the doors under its control are downloaded to the iSTAR panel. This selection allows the availability of such personnel records for use with the Conditional Access feature. This option should be selected if the iSTAR panel has any doors configured for Conditional Access. The iSTAR Edge will store more cards when this selection is made.

NOTE: This selection can be made only when the controller is offline. Making this selection causes a full personnel download to the panel, once it is put back online.

Main Board Tab



Tamper Click this check box to configure the Tamper input. The Tamper input activates when the iSTAR Edge controller cabinet is opened.

The system automatically configures the input using the values from the default input definition. To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Tamper check box deletes the Tamper input.

AC power fail input Click this check box to configure the AC power fail input. The AC power fail input monitors the AC power failure output of a battery backup unit. When this input activates, it indicates that the UPS (Un-interruptible Power Supply) or apS has had an AC Power Failure and is now supplying battery power to the controller.



Deselecting the AC power fail input check box in the Controller dialog box, deletes the AC power fail input.

Low battery input Click this check box to configure the Low Battery input. The Low battery input activates when the UPS or apS emergency battery has reached a yellow warning level. Most UPS units have about 10 to 20 minutes of runtime when this condition occurs. It is recommend to shutdown the unit being powered by the low battery. Do not confuse this input with the Onboard Battery Low input.






Main Board Tab


Special Purpose Inputs (continued)

Onboard Battery Low input Click this check box to configure the Onboard Battery Low input. The Onboard Battery Low input activates when the onboard AA alkaline battery voltage is low, or if a battery is missing or disconnected. The Onboard battery voltage is important in that upon loss of external or PoE power, data is written to onboard non-volatile flash. The four onboard non-rechargeable batteries provide power to for the backup process, and maintaining the clock afterwards.

Onboard battery low occurs when the voltage of all four batteries in series reaches 4.6 volts, or if a battery is missing.

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.

The system automatically configures the input using the values from the default input definition. Batteries should be replaced immediately when this input is active Onboard battery Low.

To view or edit the input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Onboard Battery Low input check box in the deletes the input from the configuration.

Default: Enabled

FAI State Click this check box to configure the FAI State input. This input indicates the state of the F (Fire) input coming into J40 of the iSTAR Edge. In other words, this is the fire alarm.

The system automatically configures the input using the values from the default input definition.


Deselecting the FAI State input check box in the deletes the input from the configuration.



Main Board Tab


FAI Relay Control Click this check box to configure the FAI Relay Control input. 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,.



Deselecting the FAI Relay Control input check box in the deletes the input from the configuration.

FAI Key State Click this check box to configure the FAI Key State input. This is the K (Key) input state. This indicates the state of the K (Key) switch at J40 of the iSTAR Edge..



Deselecting the FAI Key State input check box in the deletes the input from the configuration.


General Purpose Inputs 1 to Input 8

Click the check box next to the input that you want to configure. The system automatically configures the input using the values from the default input definition.

To view or edit an input, click the input’s View button. See “Configuring Inputs” on page 6-2 for more information.


Deselecting the Input check box in the Controller dialog box deletes the input from the configuration.


Onboard Wiegand Readers 1 and 2

Click the check box next to the reader that you want to configure. The system automatically configures the reader using the values from the default reader definition. To view or edit a reader, click the output’s View button. See “Configuring Outputs” on page 6-13, for more information.


Deselecting the Reader check box in the Controller dialog box deletes the output from the configuration.



Main Board Tab


Relay Outputs Relay Outputs 1 to 4 Click the check box next to the Output that you want to configure on the controller. The system automatically configures the relay output using the values from the default output definition. To view or edit the relay output, click the output’s View button. See “Configuring Outputs” on page 6-13 for more information.

If Online is the default setting for the relay output and you do not deselect this option in the Output dialog box, the relay output is set online and downloaded after you click OK in the Controller dialog box.

Deselecting the Output check box in the Controller dialog box, deletes the output configuration.

NOTE The first time you configure an input, output, or reader, you must do so from the Controller dialog box for the security object. After a security object is defined, you can edit its definition from the Controller dialog box or by selecting the item from the Hardware drop-down menu on the C•CURE 800/8000 Administration application.

You must also delete the an input, output, or reader from the Controller dialog box.



Serial Ports Tab


Serial Ports Tab

Configuring the Serial Ports

The Serial Ports tab lets you define the inputs, outputs, and readers on COM1, COM2, and COM3 devices attached to the iSTAR Edge controller.

To configure the serial port devices

1. From the Controller dialog box, click the Serial Ports tab. The Serial Ports tab opens for the controller, shown in Figure 3-8.

Figure 3-8: Serial Ports Tab


Serial Ports Tab


Table 3-5: Serial Ports Tab Fields


COM1 Devices Protocol on COM1 Connect RM readers to COM1 by choosing the reader protocol from this field's drop-down list. RM is displayed in the Protocol field. iSTAR Edge does not support Wyreless protocol.

Configure Device on COM1 Click this button to configure readers on COM1. If you chose RM reader for the Protocol, the RM Modules on Serial COM1 on Controller dialog box opens, and you can configure Inputs, Outputs and Readers. See Figure 3-9 on page 3-31.


Configure Devices on COM2

Click this button to configure readers on COM2. If you chose RM reader for the Protocol, the RM Modules on Serial COM2 on Controller dialog box opens and you can configure Inputs, Outputs and Readers. See Figure 3-9 on page 3-31.


Configure Devices on COM3

Click this button to configure readers on COM3. If you chose RM reader for the Protocol, the RM Modules on Serial COM3 on Controller dialog box opens, and you can configure Inputs, Outputs and Readers. See Figure 3-9 on page 3-31.

Serial Ports Tab


3. When you click the Configure Device(s) on COM1, COM2 or COM3 buttons, with the RM bus protocol selected, the RM Modules on Serial COM1 dialog box will appear. Figure 3-9 shows the eight I/8 Input and R/8 Output Boards and four Readers.

Figure 3-9: RM Modules on Serial COM1 Dialog Box

4. Click the View button to configure up to eight input and output boards, and up to four readers.










The master connects directly to the host using a network connection.





Use the C•CURE Administration Application to configure controllers and the cluster. See “Configuring iSTAR Edge Controllers” on page 3-12and “Configuring Clusters” on page 3-38 for information.




After downloading information from the host, the master auto-configures its cluster members. Cluster members then reboot and establish connections with the master. See the iSTAR Edge Installation and Configuration Guide for more information.















Example:


Use the Cluster dialog box in the C•CURE System Administration Application to configure connection verification messages for the master, host, and cluster members. See “Configuring Clusters” on page 3-38 for more information.



A second network connection between the master and the host.

A network connection between another controller in the cluster - the alternate master - and the host.

The configuration of the secondary communications path (alternate master or a secondary connection from the master) determines how controllers re-establish cluster communications when the primary path fails. See “Maintaining Cluster Communications” on page 3-36 for more information.




Use the Secondary tab in the Cluster dialog box in the C•CURE System Administration Application to configure the secondary communications path. See “Configuring the Secondary Communications Path” on page 3-47 for more information.






If the master fails, the following configurations of the secondary communications path determine how cluster communications are re-established:


If the master loses its connection with the host and the secondary communications path is another connection between the master and the host, the following occurs:





If the master loses its connection with the host and the secondary communications path is a connection between an alternate master and the host, the following occurs:




See Figure 3-10 on page 3-37.



Figure 3-10: Host Communications Reestablished via an Alternate Master




The iSTAR Cluster dialog box lets you configure clusters by performing the following tasks:





Configure a test of the secondary communications path.


1. From the C•CURE 800/8000 Administration application, choose Hardware->iSTAR Cluster from the menu bar. The iSTAR Cluster Selection browser appears, shown in Figure 3-11 on page 3-39.





2. Click New to create a new cluster

- or -

select a cluster and click Edit to edit a cluster’s configuration.

The Select Cluster Type dialog box appears, shown in Figure 3-12 on page 3-39.

Figure 3-12: Select Cluster Type Dialog Box

3. Choose the iSTAR eX or iSTAR Edge Cluster Type and click OK. The Cluster dialog box displays.



Figure 3-13: iSTAR Edge and eX Cluster Dialog Box










You cannot select the method of communication between host and controller on the Primary or Secondary tabs if the cluster is online. To put the cluster offline, deselect the Online check box, click OK to close the dialog box, and then re-open the dialog box.


General Tab



Edit Controllers Click this button to open the CCURE Controller Selection browser where you can select, edit, or create controllers. See “Configuring iSTAR Edge Controllers” on page 3-12 for information.



Available Controllers cont.

Add/Add All/Remove/Remove All buttons

Click these buttons to move controllers between the Controllers in the cluster and Available Controllers boxes. For example, if you click Add All, all controllers in the Available Controllers box are moved to the Controllers in this cluster box. Controllers listed in the Controllers in this cluster box are members of the cluster.

Controllers in this Cluster

Displays a list of controllers that are assigned to the cluster. A controller must be assigned to a cluster for C•CURE 800/8000 to communicate with the controller. Use the Add or Add All buttons to add controllers to the cluster by moving them from the Available Controllers box to the Controllers in this cluster box. Use the Remove and Remove All buttons to take controllers out of the cluster.

Other Tabs


Secondary This tab lets you configure the secondary communications path for the cluster. See “Configuring the Secondary Communications Path” on page 3-47 for information.


Misc This tab lets you configure a communications test for the secondary communications path and the maximum number of unacknowledged messages allowed for each controller. See “Configuring the Secondary Communications Path” on page 3-47 for information.


Encryption This tab lets you configure encryption for the controller. See “Configuring Encryption for the Cluster” on page 3-58 for information.



Primary Tab


Primary Tab




1. From the Cluster dialog box, click the Primary tab. The Primary tab opens for the cluster, shown Figure 3-14.




Primary Tab










NOTE: iSTAR Edge has one Onboard Ethernet. When iSTAR Edge is selected as master controller, the Method of Communication Between Host and Controller displays Ethernet.

Host port used for serial communications with controller

If the Master uses a serial connection to communicate with the host, enter the port on the host to which the controller is connected. You can double-click in the field to display a list of ports on the C•CURE 800/8000 server.



Primary Tab







The master broadcasts a request across its subnet for the host’s IP Address. If the iSTAR Configuration Utility is configured for auto-response, it responds to the master. See the iSTAR Edge Installation and Configuration Guide for information.





Primary Tab


















Secondary Tab


Secondary Tab







Secondary Tab







NOTE: The same iSTAR Edge cannot be selected for both Primary and Secondary communications with the host.




NOTE: iSTAR Edge has one Onboard Ethernet. When iSTAR Edge is selected as master controller, the Method of Communication Between Host and Controller displays Ethernet.



Secondary Tab















Cluster Tab


Cluster Tab







Cluster Tab



Field Description








The controller broadcasts a request across its subnet for the master’s IP Address. The master responds to the request. If the master 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 Edge Installation and Configuration Guide for information.



Cluster Tab










The controller broadcasts a request across its subnet for the master’s IP Address. The master responds to the request. If the master does not respond in a set amount of time and the iSTAR Configuration Utility is configured for auto-response, the utility can respond to the controller. See the iSTAR Edge Installation and Configuration Guide for information.


Field Description

Misc Tab


Misc Tab




To configure the test for the secondary communications path





Misc Tab



Field Description





Activate this event while secondary test failure






Global APB Tab


Global APB Tab


The Global APB tab in the Cluster dialog box lets you specify if the cluster enforces both cluster antipassback and iSTAR Edge Global Antipassback. It also allows you to specify how the cluster handles antipassback during communications failure.





Global APB Tab



Field Description










Encryption Tab


Encryption Tab

Configuring Encryption for the Cluster

The Encryption tab in the Cluster dialog box lets you configure encryption for the iSTAR Edge cluster.

To Configure Encryption for the Cluster

1. From the Cluster dialog box, click the Encryption tab. The Encryption tab opens, shown in Figure 3-19.

Figure 3-19: Encryption Tab


NOTE iSTAR Edge controllers are not listed under FIPS 140-2, but may operate in clusters where iSTAR eX controllers are using FIPS 140-2 Validate Mode.

Encryption Tab


Table 3-12: Encryption Tab Fields

Field Description

Encrypt Traffic You can select:

Encrypt traffic - Select this option to have the cluster encrypt traffic between iSTAR Edge and iSTAR eX controllers using AES encryption. This option is selected by default and is not modifiable in the current release.

Non-FIPS mode uses AES encryption for communications between the Host, Master or Members of the cluster. See the iSTAR Edge Installation and Configuration Guide for details.

FIPS 140-2 validate mode: The cluster uses AES encryption and operates in “dark” mode, a state in which none of the controllers is visible and ICU will not function on the cluster members. See the iSTAR Edge Installation and Configuration Guide for details.

Encryption Tab



4

Configuring AdvancedProcessing Panels

(apC, apC/8X, apC/L)

This chapter explains how to configure the apC, apC/8X, and apC/L software components to work with C•CURE 800/8000. To install and configure hardware for the apC, apC/8X, and apC/L, consult the apC/8X Installation and Configuration Guide and the apC/L Installation and Configuration Guide.

In this chapter

Panel Overview ............................................................................................................... 4-2

Configuring Panels ......................................................................................................... 4-5

Configuring Security Objects on Panels .................................................................... 4-12

Configuring Panel Events ............................................................................................ 4-14

Configuring Holiday Lists for a Panel ....................................................................... 4-16

Viewing the Intrusion Zones on Panels..................................................................... 4-18

Panel Overview


Panel Overview

The apC (advanced processing Controller), apC/8X, and apC/L are access control field panels that coordinate communication between the C•CURE 800/8000 Server and the system security hardware, such as card readers. You can connect to panels directly or with telephone lines and modems. Dialup panels are remotely located apCs, apC/8Xs, and apC/Ls that communicate with the C•CURE 800/8000 host via standard telephone lines and modems.

The apC/L is a smaller version of the apC, making it ideal for parking garages and small office buildings.

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 daisychain arrangement. The apC/L configuration supports two card readers.

Inputs and Alarm Device States

An input is a software definition that associates an alarm device with an input on the panel or on an input board. There are two kinds of inputs: supervised and unsupervised. All alarm devices can be in one of two states: active or inactive. An input reports the state of the alarm device.

A supervised input reports on the status of the wiring between the panel and the alarm device. If that wiring is cut, the system reports an open circuit. If someone tries to jumper across the wiring (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.

Panel Overview


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 “Configuring Inputs” on page 6-2 for more information.

Outputs

An output is a software definition that associates an alarm device with an output on the panel board or add-on module. The output turns alarm devices, such as a closed circuit TV or alarm dialers, on or off. See “Configuring Outputs” on page 6-13 for more information.

Readers

A reader is a hardware device that accepts access requests. To make an access request, a person swipes a card at the reader; the card reader scans the information encoded on the card and sends it to the apC, which grants or denies access.

Optional Boards

apCs and apC/8Xs 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

1 Standard Star Coupler, or

1 Mini Star Coupler, or

1 Wiegand/Proximity Star Coupler

Star couplers enable you to wire the apC’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.



Panel Overview


See “Configuring Add-On Boards for apCs” on page 7-2 for more information.

NOTE The apC/L supports three types of optional boards: four I/8 - input modules, four R/8 - output modules.

Configuring Panels


Configuring Panels

The apC dialog box lets you configure direct-connect and dialup panels (apCs, apC/8Xs, and apC/Ls).

To Configure Panels

1. From the C•CURE 800/8000 Administration application, select Hardware->apC from the menu bar. The apC Selection browser appears, shown in Figure 4-1.

Figure 4-1: apC Selection Browser

2. Click New. The apC dialog box appears, shown in Figure 4-2 on page 4-6.

Configuring Panels


Figure 4-2: apC Dialog Box

3. Provide the information shown in Table 4-1 on page 4-7 and click OK to save the panel configuration and close the apC dialog box.

If your system is using the Distributed Holidays mode and there is no Holiday list assigned to this apC, the system displays a warning message similar to the following, but still allows you to save the panel configuration. (For detailed information, see “Configuring Holiday Lists for a Panel” on page 4-16.)

Configuring Panels


Table 4-1: apC Dialog Box Fields


Identification Name Enter a unique name up to 50 characters long. If you enter the name of an existing panel (or other security object), the system returns an error message indicating there is a conflict.

Time Zone Specify a time zone for the panel. Double-click on this box to display a selection browser for time zones.

The following objects are associated with the panel’s time zone:

Inputs, outputs, and readers on the panel

Doors and door groups with inputs, outputs, or readers on the panel

Elevators and elevator groups with inputs, outputs, or readers on the panel

Only time specifications and clearances that use the same time zone as the panel are downloaded to the panel. If you change the panel’s time zone after a time specification or clearance has been downloaded to the panel, a matching violation occurs. The time zone is downloaded to the panel, and the clearance is deleted from the panel. See the C•CURE 800/8000 Software Configuration Guide for more information.

Description Enter a general comment about the panel. This text is for information only.

Online Click this check box to put the panel online. While a panel is online, the C•CURE 800/8000 attempts to communicate with it.

If you delete a panel or put a panel offline, it is ignored by C•CURE 800/8000; however, the panel may continue to operate and perform access control decisions. To stop the panel from operating, put any readers that are attached to the panel; or if you are at the panel, erase the panel’s memory by setting switch 1:1 to On and turning off the panel’s power.

General apC Type Select the type of panel you are configuring: apC, apC/8x, or apC/L.

Connection Type Select the type of connection between the host and the apC: Dialup or Direct Connect.

If you select Direct Connect, use the Port field in this dialog box to specify a port to which the apC chain is attached.

See “apC Dialup Overview” on page 10-2 for information about configuring dialup panels.

Configuring Panels


General (cont.) Reader LCD Messages Specify the set of RM reader LCD messages to assign to this panel. Double-click this text box to display a list of message sets. See“Configuring RM Reader LCD Messages” on page 5-15.

Location Port If you are configuring a direct-connect panel, select the port to which the apC, apC/8X, or apC/L chain is connected. Double-click on this box to display a selection browser for ports. You can select a COM or network port.

This field is not available when Dialup is selected in the Connection Type list box.

Address: SW4/SW5(for apCs andapC/8Xs)

- or -

Address:SW3-8/SW1(for apC/Ls)

Enter the setting of the corresponding switches on the apC, apC/8X, or apC/L.

If you are configuring a dialup apC, do not enter 00.

Communications Poll period:1/10th sec.

Enter the period in 1/10ths of a second that the panel driver (on the Server) attempts to communicate with this panel. For example, if you enter 10, the panel driver communicates with this panel a minimum of once per second.

You can set different poll periods for each panel you configure.

This field is not available when Dialup is selected in the Connection Type list box.

Software House recommends that you set the poll period to 20 (2 seconds). Setting this value lower than 20 causes the host to receive activity from the panel more quickly but could cause the driver to interfere with other programs running on the server at larger installations. This is especially true if the panel is on a network port.

Table 4-1: apC Dialog Box Fields, continued


Configuring Panels


Poll timeout delay time: 1/10th sec.

Enter the extra interval in 1/10ths of a second that the host waits for a response from this panel after sending a message to the panel. If the host does not receive a response in the specified time, the host retransmits the message or declares a communications failure. See Panel communications failure delay time in this table for more information.

Software House recommends that you set this period to 20 (2 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 30 (3 seconds) - 50 (5 seconds).

If you want to increase the timeout delay for all panels on a specific port, use the Port timeout delay time field in the Communications Port dialog box. See “Configuring Ports from C•CURE 800/8000” on page 8-8 for more information.

Panel communications failure delay time:1/10th sec.

Enter the time period in 1/10ths of a second that the host waits to declare an unresponsive panel to be in failure and a message appears on the General Activity Monitor.

Software House recommends that you set this period to 200 (20 seconds).

Communications, continued

Poll period while in communications failure:1/10th sec.

Enter the time period in 1/10ths of a second that the system polls the panel while it is in communications failure. 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 205 (20.5 seconds).

Host communications failure delay time:mm:ss

Enter the time period in minutes and seconds (MM:SS format) that the panel waits for a message from the host after receiving the previous message from the host. 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 10 seconds.



Configuring Panels


Configure Panel Click this button to open the Panel Layout dialog box. The Panel Layout dialog box lets you set up inputs, outputs, and readers that are attached to the panel. See “Configuring Security Objects on Panels” on page 4-12 for more information.

Configure

(cont.)

Add-on boards Click this button to open the Add-on Boards dialog box for apC/8Xs and apC/Ls. The Add-on Boards dialog box lets you set up add-on boards for panels. See “Configuring Add-On Boards for apCs” on page 7-2 and the technical manuals for apCs, apC/8Xs, and apC/Ls for more information.

Dialup Click this button to open the Dialup Components dialog box where you configure the dial-in, dial-out, and modem options for dialup panels. This button is unavailable for direct-connect panels. See “Configuring apC Dialup Panels” on page 10-6 for more information.

Events Click this button to open the apC Events dialog box. The apC Events dialog box lets you configure panel events. See “Configuring Panel Events” on page 4-14 for more information.

Configure, continued

Holiday Lists NOTE: This button is available only if your C•CURE 800/8000 system is operating in Distributed Holidays mode—enabled on the System Variables System tab. (If this button is unavailable, the system is operating in Default Holiday mode: configured Holiday Lists (up to a limit of 8) are automatically downloaded to all apC panels if the Download to apC check box is selected on the Holiday List Configuration dialog box.)


Click this button to open the Holiday Lists dialog box to choose up to 8 Holiday Lists for this panel. For detailed information, see “Configuring Holiday Lists for a Panel” on page 4-16.



Configuring Panels


View Intrusion Zones Click this button to open the Intrusion Zones configured on apC dialog box. The Intrusion Zones configured on apC dialog box lets you see which intrusion zones are configured on that specific panel. See “Viewing the Intrusion Zones on Panels” on page 4-18 for more information.

An apC and an apC/8X can each support up to 8 intrusion zones.

An apC/L can support up to 2 intrusion zones.

See the C•CURE 800/8000 Software Configuration Guide for more information about intrusion zones.



Configuring Security Objects on Panels



The Panel button in the apC dialog box lets you define the inputs, outputs, and readers that are attached to the main panel.


1. From the apC dialog box (apC/8X or apC/L dialog box), click the Panel button. The Panel Layout dialog box opens for the apC/8X or apC/L. Figure 4-3 shows the apC Panel Layout dialog box (the apC/8X Panel Layout dialog box is similar to the figure below).

Figure 4-3: apC Panel Layout Dialog Box

If you are defining an apC/L, the apC/L Panel Layout dialog box shown in Figure 4-4 on page 4-13 opens.



Figure 4-4: apC/L Panel Layout Dialog Box

2. Configure readers, supervised inputs, outputs, and Tamper and AC power fail inputs on the main panel. See the following sections in this guide for more information:

• “Configuring Readers” on page 5-2

• “Inputs Overview” on page 6-2

• “Configuring Outputs” on page 6-13

• “Tamper and AC Power Failure Inputs” on page 6-18

3. After configuring objects on the main panel, click OK.

NOTE The first time you configure a reader, input, or output, you must do so from the Panel Layout dialog box on which the security object exists.

Example:

From the apC Panel Layout dialog box.

After a security object is defined, you can edit its definition from the Panel Layout dialog box or by selecting the item from the Hardware pull-down menu on the C•CURE 800/8000 Administration application.

Configuring Panel Events



The Events button in the apC dialog box lets you configure panel events that activate under the following conditions:

When the panel is in communications failure.

When the panel is full.

When the panel is nearly full — has reached a user-defined percent of capacity.

To Configure the Panel Events

1. From the apC dialog box (apC/8X or apC/L dialog box), click the Events button. The apC Events dialog box opens for the apC, apC/8X, or apC/L. Figure 4-5 shows the apC Events dialog box (the apC/8X Events and apC/L dialog boxes are similar).

Figure 4-5: apC Events Dialog Box



2. Provide the information shown in Table 4-2 on page 4-15 and click OK to save the configured panel events.

Table 4-2: apC Events Dialog Box Fields


Events Event to activate on communications failure Enter an event to activate when the panel is in communications failure.

Double-click on this box to display a selection browser for events.

Event to activate when panel becomes full Enter an event to activate when the panel is full and cannot accept any more cardholder records.


Event to activate when panel becomes nearly full Enter an event to activate when the panel exceeds the capacity-used threshold specified in the next field.


NOTE: The system determines the “nearly full” capacity by estimating the maximum number of cardholder records on the panel

Panel is nearly full when it reaches Enter the percent of apC capacity for cardholder records that, when reached, triggers the associated event (entered in the preceding field). For example, if you enter 85, the panel event activates when this panel reaches approximately 85% of capacity. The initial default value is 90.

NOTE: The system generates a journal message when the panel reaches the capacity entered in this field, whether an event is configured or not.

Event to activate on reaching Long term comm. loss time limit



Configuring Holiday Lists for a Panel



You can download any holiday list to an apC panel from a dialog box accessed either from the apC dialog box, or alternatively, from the Holiday List Configuration dialog box.

A Holiday List downloaded to an apC panel acts as an override to prevent activation of normally scheduled clearances and timed-based events on the Holidays defined in the Holiday List. You can configure up to 8 holiday lists for each apC panel.

To Select Holiday Lists for the Panel

1. On the General tab of the apC dialog box, click the Holiday Lists button.







2. For each Holiday List that you want to download to the panel, click that Holiday List in the Available box and click Add to add it to the Selected box. You can click Add All to include all of the Available Holiday Lists for the panel. You can click Remove or Remove All to remove one or all Holiday Lists from the panel.

3. Click OK to save the selected Holiday Lists and return to the apC dialog box.

NOTE The Available box includes all existing Holiday Lists in the system not currently used by this panel.

NOTE When you click OK, the system validates that the panel does not have more than the limit of 8 Holidays Lists.

Viewing the Intrusion Zones on Panels


Viewing the Intrusion Zones on Panels

The Intrusion Zones configured on apC dialog box lets you see which intrusion zones are configured on a specific panel.

To View the Intrusion Zones on a Panel

1. From the apC dialog box (apC/8X or apC/L dialog box), click the Intrusion Zones button. The Intrusion Zones configured on apC dialog box opens for the apC, apC/8X, or apC/L. Figure 4-7 shows the Intrusion Zones configured on apC dialog box.

Figure 4-7: Intrusion Zones Configured on apC Dialog Box

2. View the information and click Close to return to the apC dialog box.


5

Configuring Readers,RM Reader LCD

Messages, and CardFormats

This chapter explains how you define the readers that you attach to an iSTAR controller or the apC main panel; how you customize sets of LCD messages, such as “Present Card” or “Access Granted,” for your RM readers to meet the specific needs of your facility or site; and how you configure different card formats for your controllers and panels.

In this chapter

Configuring Readers....................................................................................................... 5-2

Configuring Reader Keypad Options .......................................................................... 5-6

Configuring Advanced Options for Readers on Controllers.................................. 5-10

Configuring Advanced Options for Readers on apCs............................................. 5-13

Configuring RM Reader LCD Messages.................................................................... 5-15

Configuring Card Formats .......................................................................................... 5-25

Configuring Readers


Configuring Readers

From the Controller dialog box for iSTAR controllers, you can define the readers you want to attach to the controller. You can define up to 16 readers per controller. From the Panel Layout dialog box for apCs, apC/8Xs, or apC/Ls, you can define the readers you want to attach to the main panel. You can define up to 8 readers per apC and apC/8x, and 2 per apC/L.

To Configure Readers Attached to this Controller or Panel

1. From the 1st ACM Ext tab or the 2nd ACM Ext tab of the Controller dialog box or from the Panel Layout dialog box for the apC, apC/8X, or apC/L, select the number of the reader you want to configure by clicking the appropriate check box. This number must correspond to the hardware address on the RM-4 module. The system automatically configures the reader using values from the default reader definition and an assigned name.

2. To view or edit the reader, click the reader’s View button.

3. The Reader dialog box opens, as shown in Figure 5-1 on page 5-3.

NOTE Readers on a controller or panel are associated with the time zone that is specified for that controller or panel.

NOTE To edit the default reader definition, choose Reader from the Hardware menu and click the Edit Default button in the Reader Selection browser. The Reader dialog box opens. See Table 5-1 on page 5-3 for the Reader dialog box in this section for more information.

If Online is the default setting for the reader and you do not de-select this option, the reader is set online and downloaded after you click OK in the Controller dialog box or apC dialog box.

NOTE Deselecting a reader, input, or output causes the security object to be deleted.

Configuring Readers


Figure 5-1: Reader Dialog Box

4. Provide the information shown in Table 5-1 and then continue to Step 5 on page 5-5.

Table 5-1: Reader Dialog Box Fields


Identification Name Displays the reader name as provided by the system. To change the reader name, enter a unique name up to 50 characters long.

Description Enter a brief description of this reader. The text here is for informational purposes only; it does not appear anywhere else.

Online Click this check box if you want to put this reader online. While the reader is online, the controller/apC tries to communicate with it.

Configuring Readers


After Hours Enabling If checked, the configured reader can be used as an after hours enabled reader. You will not be able to deselect this box until you have deselected the After Hours Restrict Readers option in the Reader Group dialog box found under the Configure menu. See the C•CURE 800/8000 Software Configuration Guide for more information.

Reader technology Click the option button next to the type of card that this card reader can accept. Possible values are Magnetic, Wiegand, Proximity, or RFID.

Card formats Enter the card formats this reader will use. To select from a list of possible values, double-click on the text box. You can choose up to three card formats for each reader, up to a maximum of 8 in the system. When specifying card formats for access control readers, follow these guidelines:

Select at least one access control card format for the reader. For example, if you select only asset tracking card formats for an access control reader, the reader detects only assets; cards are not detected and generate a card misread message at the Monitoring Station.

If you specify asset and access card formats for a reader, ensure that the formats are not identical.

See “Configuring Card Formats” on page 5-25 for information.

The C•CURE 800/8000 system supports up to 128 card formats. All 128 card formats can be downloaded to each of your iSTAR controllers. Only 8 of the available 128 card formats can be downloaded to a given apC controller (each controller can have a different subset of card formats, as needed).

To select from a list of card formats that are available on the controller, double-click on the text box.

Each iSTAR reader can be configured with up to 10 of the available 128 formats. Each apC reader can be configured with all 8 of the card formats that are configured on the apC controller to which the reader is connected.

When specifying card formats for access control readers, follow these guidelines:

Select at least one access control card format for the reader.

Example:

If you specify asset and access card formats for a reader, ensure that the formats are not identical.

Table 5-1: Reader Dialog Box Fields, continued


Configuring Readers


5. Click the Keypad button to open the Reader keypad configuration dialog box where you specify PIN options for this reader. See “Configuring Reader Keypad Options” on page 5-6 in this chapter for more information.

6. Click the Advanced button to open the Advanced reader configuration dialog box. There are different versions of this dialog box depending upon whether the reader is on an iSTAR controller or an apC. See “Configuring Advanced Options for Readers on Controllers” on page 5-10 and “Configuring Advanced Options for Readers on apCs” on page 5-13 in this chapter for more information.

7. Click OK.

Reader Type Click the option button next to the reader type you are using. Possible values are MRM or RM.

NOTE: The Direct Connect Wiegand reader type is not supported in this version of CURE 800/8000.

See the iSTAR Pro or iSTAR eX Installation and Configuration Guide or the apC/8X or apC/L Installation and Configuration Guide for details about reader types.

Supervised Inputs Click the check boxes beside these fields to configure the supervised inputs that are on this reader. You can configure up to 2 supervised inputs per reader. See “Configuring Inputs” on page 6-2 for an explanation of input configuration tasks.

Outputs Click the check boxes next to these fields to configure outputs that are attached to this reader. You can configure up to 2 outputs per RM reader and 1 output per MRM reader. See “Configuring Outputs” on page 6-13 for an explanation of output configuration tasks. For each output connected to a reader, you need an Auxiliary Relay Module (ARM).

See the iSTAR Pro or iSTAR eX Installation and Configuration Guide or the apC/8X or apC/L Installation and Configuration Guide for details.

Table 5-1: Reader Dialog Box Fields, continued


Configuring Reader Keypad Options



The Reader keypad configuration dialog box lets you specify different options for requiring or not requiring the entry of PINs to obtain access at readers with keypads. A manual action at the Monitoring Station or an event can configure the PIN requirement. Reader Keypad Configuration lets you specify the following for this reader with a keypad:

Options for requiring or not requiring the entry of a PIN in addition to presentation of a card to obtain access at the reader.

Ability to enter card numbers using the keypad

Options for allowing or disallowing the entry of Keypad commands at this reader.

See the C•CURE 800/8000 Monitoring Station Guide and the C•CURE 800/8000 Software Configuration Guide for more information.

To Configure Reader Keypad Options

1. In the Reader dialog box, click the Keypad button. The Reader keypad configuration dialog box opens, shown in Figure 5-2.

Figure 5-2: Reader Keypad Configuration Dialog Box

NOTE If the reader is configured on an iSTAR controller, this dialog box also allows you to configure the reader keypad to allow users to enter their card numbers to gain access without presenting or swiping their cards.



2. Select one of the options shown in Table 5-2 and click OK:

NOTE Manual actions at the Monitoring Station or an event can change PIN mode or keypad command permissions at this reader.

Table 5-2: PIN Requirements


PIN requirements PIN is not required Select this option if you do not want to require users to enter a PIN number, in addition to presenting or swiping their card, to gain access.

PIN is always required Select this option if you want to require users to enter a PIN number to gain access, in addition to presenting or swiping their card.

PIN is required during time specification:

Select this option if you want to require users to enter a PIN number during a designated time specification, in addition to presenting or swiping their card, to gain access.

NOTE: You must enter a time specification in the next field if you select this check box.

(Time specification) edit field Enter a time specification if the PIN is required during time specification option is selected. Double-click in the field to display a list of time specs to select. Select the Allow card numbers to be entered via keypad check box.

PIN-Only Access If PIN-Only access is selected, access cards presented at this reader are ignored. Only a PIN entered via the keypad can be used for access.

NOTE: If PIN-Only access is selected, neither the (Time specification) edit field nor the Allow card numbers to be entered via keypad check box are available.



PIN requirements (continued) Allow card numbers to be entered via keypad

Click this check box to permit users to enter their card numbers on the keypad to gain access at the reader instead of having to present or swipe their card.

NOTE: To allow users the same option with apCs, you must enable (set to 1) the UseCardEntryThroughKeypad and CardEntryThroughKeypadentries in the Diag System Dialup section.

To enter your card number on the keypad, first press CMD/ENT, then enter your number—from 1 to 10 digits long, and finally press CMD/ENT again.

To use [cmd/enter key] card number [cmd/enter key] to enter a card number at a keypad, you must enter zero (0) before the number: for example, [cmd/enter key]01234[cmd/enter key].

If your card number is 4 digits long or less, you can enter it on the keypad without pressing CMD/ENT at all. However, card numbers that are 3 digits or less require you to enter leading zeroes. For example, if your card number is 123, enter the number as 0123; if your card number is 34, enter the number as 0034; if your card number is 4, enter the number as 0004.

Keypad Command Permissions

Keypad Commands are not allowed Select this option if keypad commands should not be allowed.

Keypad Commands are always allowed

Select this option if keypad commands should always be allowed

Table 5-2: PIN Requirements, continued




Keypad Command Permissions (continued)

Keypad Commands are allowed during time specification

Select this option if you want to allow users to use keypad commands during a designated time specification.

You must enter a time specification in the next field if you select this check box.

(Time specification) edit field Enter a time specification if the Keypad Commands are allowed during time specification option is selected. Double-click in the field to display a list of time specs to select.

Table 5-2: PIN Requirements, continued


Configuring Advanced Options for Readers on Controllers



The Advanced reader configuration dialog box lets you specify status inputs for readers on controllers to activate for tampers and communication failures.

To Configure Advanced Reader Options

1. In the Reader dialog box, click the Advanced button. The Advanced reader configuration dialog box opens, shown in Figure 5-3.

Figure 5-3: Advanced Reader Configuration Dialog Box (for Controllers)

2. Provide the information shown in Table 5-3 on page 5-11 and click OK.



Table 5-3: Controller Status Inputs


Reader Status Inputs Tamper Select Tamper to configure a tamper input for this reader.

To view or edit the input, click the input’s View button.

Communications failure Select failure to configure the Communications Failure input on the I/8 - Input Module. This input activates when the I/8 - Input Module goes into communications failure. When you select this check box, the system automatically configures the input using the values from the default input definition.


Click OK in the Controller dialog box to download the input to the controller.

To delete the Communications failure input, clear the Communications failure option in the I/8 dialog box.

Auxiliary tamper Select Auxiliary tamper to configure tamper on the RS-485 interface to the GCM.


This input is used for configurations that connect 2-Port Enhanced RM readers.

Auxiliary communications failure Select Auxiliary communications failure to configure communications failure on the RS-485 interface to the GCM.


This input is used for configurations that connect 2-Port Enhanced RM readers.



Reader Status Inputs (continued) Motor Stall Click Motor Stall to configure a motor stall alarm. This alarm is available for Wyreless readers connected to an RS-485 port on an iSTAR GCM.


Low Battery Click Low Battery to configure a low battery alarm. This alarm is available for Wyreless readers connected to an RS-485 port on an iSTAR GCM.


Status Messages Double-click in the Status Messages field to open the Reader Status Message selection browser and select a status message for the reader.

NOTE: Status messages are supported on iSTAR configurations. You can configure reader status messages on the Configure Extended Reader Status Messages dialog box.

Table 5-3: Controller Status Inputs, continued


Configuring Advanced Options for Readers on apCs



The Advanced reader configuration dialog box lets you specify outputs and events to activate for communications failures and tampers at readers on apCs.

To Configure Advanced Reader Options

1. In the Reader dialog box, click the Advanced button. The Advanced reader configuration dialog box opens, shown in Figure 5-4.

Figure 5-4: Advanced Reader Configuration Dialog Box (for apCs)




Table 5-4: Advanced Reader Configuration Fields (for apCs)


Communications failures Activate this output during communications failures

Enter the name of the output or output group that you want to activate when the panel loses communications with the reader. You can double-click on the box to display a list of configured outputs.

Activate this event during communications failures

Enter the name of the event or event group that you want to activate when the panel loses communications with the reader. You can double-click on the box to display a list of configured events.

If this reader is on a dialup panel, the specified event’s dialup setting determines whether the panel dials the host for communications failures at this reader. See the C•CURE 800/8000 Software Configuration Guide for more information.

Tampers Activate this output while tampered Enter the name of the output or output group that you want to activate when the system detects a tamper error for this reader. You can double-click on the box to display a list of configured outputs.

When a reader tamper occurs, the panel disables the outputs on that reader.

Activate this event while tampered Enter the name of the event or event group that you want to activate when the system detects a tamper error for this reader. You can double-click on the box to display a list of configured events.

If this reader is on a dialup panel, the specified event’s dialup setting determines whether the panel dials the host for tampers at this reader. See the C•CURE 800/8000 Software Configuration Guide for more information.

Configuring RM Reader LCD Messages



RM readers display LCD messages, such as “Present Card” or “Access Granted” to indicate different states to cardholders. You can customize sets of these messages to meet the specific needs of your facility or site. For example, you could change the “Access Granted” message to “Please Enter Now”. When you assign a set of messages to a panel, all the RM readers on that panel use those same messages.

The RM LCD Messages dialog box allows you to configure message sets. You can use the default RM LCD Messages dialog box to change the language in which your messages appear. See “Changing the Language for the Default RM LCD Messages” on page 5-23.

To Configure an RM LCD Message Set

1. Select Hardware from C•CURE 800/8000 menu bar, then choose RM LCD Messages. The RM LCD Messages Selection browser appears, shown in Figure 5-5.

Figure 5-5: RM LCD Messages Selection

NOTE Only characters in the English character set are supported for display on the RM reader at this time. No accented characters are supported.



2. Click New. The RM LCD Messages dialog box, shown in Figure 5-6, appears with the default messages on the Group 1 tab displayed.

Figure 5-6: RM LCD Messages

3. Enter the information shown in Table 5-5 in the main section of the dialog box.

4. In the Group 1 tab, edit any of the messages according to the information shown in Table 5-6 on page 5-17 (the maximum message text length is 16 characters).

Table 5-5: RM LCD Messages Fields


Identification Name Enter a unique name up to 50 characters long for the message set.

Description Enter a brief description of the message set. This text is for information only.

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 or 24 (the default).



5. Click the Group 2 tab. It opens with the default messages as shown Figure 5-7.

Figure 5-7: Group 2 Tab

6. Edit any of the messages according to the information shown in Table 5-7 on page 5-18 (the maximum message text length is 16 characters).

Table 5-6: Group 1 Fields

Tab Field Description

Group 1 Access granted Indicates access is permitted for the card presented to the reader at this time.

Access denied Indicates access is not permitted for the card presented to the reader at this time.

Enter PIN Indicates that the cardholder must enter a PIN on the keypad before the reader can process the access request.

Unlocked Indicates that the door can be accessed without the cardholder presenting a card.

Please wait Indicates that the card used is not in the panel and is about to be rejected.



7. Click the Group 3 tab. It opens with the default messages as shown in Figure 5-8.


8. Edit any of the messages according to the information shown in Table 5-8 on page 5-19 (the maximum message text length is 16 characters). Click OK when you are finished editing messages on all the tabs.

Table 5-7: Group 2 Tab Fields


Group 2 Wait - busy Indicates that a door whose reader is not configured for continuously active access processing is currently open to grant access to another cardholder.

Reader not ready Indicates that the reader is not configured or is offline.

Present card Indicates that the reader is ready to process card accesses.

Door in alert Indicates that the door is forced or held open or that a a reader on the door has been tampered with.

Secure Indicates that the reader is in access disabled mode.








Group 3 Area armed Indicates that an intrusion zone is in armed mode—the area is protected with all doors locked and all inputs armed. Entering an armed intrusion zone activates the inputs and causes an intrusion zone violation.

Area disarmed Indicates that an intrusion zone is in disarmed mode—the zone’s inputs are disarmed and do not cause intrusion zone violations when the zone is entered.

Exit now Indicates that an intrusion zone whose mode has been changed to armed has an exit delay period set—the zone can be exited before the zone is actually armed.

Not ready to arm Indicates that a disarmed intrusion zone has a status of not ready to arm—an object assigned to the zone is not functioning normally, one of the zone’s inputs is active, or one of the zone’s doors is open.





Group 4 Keypad Command Prompt 1 Keypad Command Prompt 1 defaults to the message Enter Acs Code; it displays after the user enters the Command Code on the RM keypad and prompts the user to enter the second part of the identifier for this keypad command (the access code). This message is displayed for 15 seconds or until the user enters the code.

NOTE: This message does not display on the RM if you entered 0 (zero) in the Maximum Length of Prompt 1 Code field on the Keypad Commands tab in the System Variables dialog box.

Keypad Command Prompt 2 Keypad Command Prompt 2 defaults to the message Enter Trgt Code; it displays after the user enters the Command Code (and possibly the Prompt 1 Code) on the RM keypad and prompts the user to enter the third part of the identifier for this keypad command (the target code). This message is displayed for 15 seconds or until the user enters the code.

NOTE: This message does not display on the RM if you entered 0 (zero) in the Maximum Length of Prompt 1 Code field on the Keypad Commands tab in the System Variables dialog box.

Enter Next Card Enter Next Card indicates that an Escorted Visitor card has been acknowledged by the door’s reader and prompts the next Escorted Visitor or the Escort to present a card for access.

NOTE: This message displays for Escorted Visitors or Escorts at doors that permit multiple person access on each access cycle.

CMD Issued CMD Issued indicates that the keypad command entered on the RM Keypad was sent to the event manager. It does not indicate that the event is active. This message is displayed for one second after the command is issued.






CMD Failed CMD Failed indicates that the keypad command entered on the RM Keypad failed for any of the following reasons:

Command does not exist.

Command is disabled.

Event does not exist.

User entered an incorrect command.

User does not have permission to issue the command.

User does not have clearance at the door.

User’s card is lost, disabled, or expired

Table 5-9: Group 4 Tab Fields, continued








Group 5 Acknowledged Acknowledged indicates that an Escorted Visitor card presented to a door’s reader has passed the checks for clearance, activation, and optionally antipassback.

Enter Escort Enter Escort indicates that an Escorted Visitor card presented to the reader at a turnstile (or mantrap) outside a secured area has been acknowledged and the Escort inside the secured area must now present his card for the Escorted Visitor to be granted access.

NOTE: Turnstiles (or mantraps) are entries that permit only one person access to an area on each access cycle.

Secure Violated Secure Violated indicates that an a secured intrusion zone has a status of violated, which means that the status of the zone changed to offnormal at least once since the zone was last armed.

Secure Offnormal Secure Offnormal indicates that a secured intrusion zone has a status of offnormal—an object assigned to the zone is not functioning normally, one of the zone’s inputs is active, or one of the zone’s doors is open.

Lockout HHH:MM This field provides lockout time in hour and minutes. Default value is Lockout &T, where &T is replaces 6 characters that will indicate the hours and minutes remaining before the person is allowed to enter the area.



14. Edit any of the messages according to the information shown in Table 5-11 (the maximum message text length is 16 characters). Click OK when you are finished editing messages on all tabs.

Changing the Language for the Default RM LCD Messages

You can use the default dialog box for RM LCD messages to easily change the language in which the default messages appear. When you first start the C•CURE System, the default messages appear in the system-wide primary language you chose during installation.

Example:

You chose English as the primary system language and configured all the sets of English messages your site needs; you may now want to customize some message sets in French.

To Change the Language for the Default Message Set

1. Exit the C•CURE 800/8000 Administration Application.

2. Go to the Windows Control Panel and use the Regional Settings option to change the language to French.

3. Restart the Administration Application, select Hardware from the C•CURE 800/8000 menu bar, and then choose RM LCD Messages. The RM LCD Messages Selection browser, shown in Figure 5-5 on page 5-15, appears.

4. Click Edit Default.The default dialog box for RM LCD messages opens, shown in Figure 5-12 on page 5-24.



Group 6 Reject Unattended Indicates that the card holder presenting the card is unattended.

Reject Occupancy Indicates that the occupancy is rejected for the card presented to the reader.



Figure 5-12: RM LCD Messages.

5. Click the Reset Messages button. The default messages change to French.

You can now go to the RM LCD Messages dialog box to customize a set of messages in French.

NOTE Clicking Reset Messages restores the default messages to the initial defaults for the system, but in the current language. Any customizing you may have made to the defaults is lost.

Configuring Card Formats



A panel supports several card format types, with a maximum of 8 different types per system. When setting up card formats for access control, follow these guidelines:

For access control readers, specify at least one access control card format for the reader.

Card formats for assets and cards on the same reader cannot be identical.

Assets and cards cannot use the same numbers. For example, assets can have odd numbers and cards can have even numbers.

You can configure a card format by selecting Card Format from the Hardware pull-down menu or by double-clicking in the Card Format text box on the Reader dialog box

To Define an Access Control Card Format

1. Select Hardware from the C•CURE 800/8000 menu bar, then choose Card Format, or double-click in a Card Format field on the Reader dialog box. The Card Format Selection browser appears, shown in Figure 5-13.

Figure 5-13: Card Format Selection



2. Click New. The Select Card Format Type dialog box appears, shown in Figure 5-14.

Figure 5-14: Select Card Format Type Dialog Box.

3. Select a card format type and click OK to display the Card Format dialog box shown in Figure 5-15.

Figure 5-15: Card Format Dialog Box

4. In the Name field, enter a name for the card format.



5. In the Card characteristics box, select a Format usage option.

If you purchased the C•CURE 800/8000 Asset Manager option, select Asset tracking to use the Asset Tracking transponder. Otherwise, Access control is selected as the default.

Also, if you are editing one of the default card formats, the appropriate Format usage option is selected.

6. The “Defining Field Formats” section provides procedures and information for adding and modifying card formats. For further explanation of card types and their data fields, see Appendix A, “”.

Defining Field Formats

You define or modify the card field format—the fields shown in the Field list box on the Card Format dialog box—on the Add Format Field dialog box (shown in Figure 5-16 on page 5-28) or the Update Format Field dialog box (shown in Figure 5-17 on page 5-29).

Table 5-12 on page 5-30 provides information about the fields and buttons on these dialog boxes, while Table 5-13 on page 5-32 provides information about the card format types.

To Add a Card Format

1. Click the Add button on the bottom of the Card Format dialog box. The Add Format Field dialog box opens on top of the Card Format dialog box, as shown in Figure 5-16 on page 5-28.

NOTE Magnetic and Wiegand refer to the way information is formatted as it is passed from the reader to the apC.

Even if your system does not appear to use one of the four types of formats, it may be compatible with one of them. See Appendix A, “” or consult your dealer representative for more information.



Figure 5-16: Add Format Field Dialog Box

2. Enter data according to the field/button information in Table 5-12 on page 5-30 and the card format type information in Table 5-13 on page 5-32.

3. Select a Start Position that is greater than 1 in the Edit Card Field box and choose a Card Type from the Type drop-down list.

4. For Facility code, Site code, and Fixed data card types, enter a Data Value in the Data value field in the Field Data box and click Add to enter the value in the Data drop-down box. To remove a data value from the Data drop-down box, select the value and click Delete.

5. Click OK to process your entry. The Card Format dialog box reappears with the new card format displayed in the Field list box.

NOTE The Data value field and the Add and Delete buttons are available only for the preceding three card types.



To Edit a Card Format

1. Select a field in the Field list box on the Card Format dialog box and click the Modify button. The Update Format Field dialog box opens on top of the Card Format dialog box, as shown in Figure 5-17.

Example:

If you are editing the Facility code field, Facility code displays in the Type box.

Figure 5-17: Update Format Field Dialog Box

2. Enter data according to the field/button information in Table 5-12 on page 5-30 and the card format type information in Table 5-13 on page 5-32.

3. For Facility code, Site code, and Fixed data card types, enter a Data Value in the Data value field in the Field Data box and click Add to enter the value in the Data drop-down box. To remove a data value from the Data drop-down box, select the value and click Delete.

NOTE The Data value field and the Add and Delete buttons are available only for the preceding three card types.



4. Click OK to save the format and any changes you made. The Card Format dialog box reappears with the new card format displayed in the Field list box.

Table 5-12: Add/Update Format Field Dialog Box Fields


Edit Card Field Type Select the type of data field you are defining from this drop down list box.

See Table 5-13 on page 5-32 which lists Card Formats.

Start Position Start Position indicates the starting position within the encoded information for this data field type. Enter a starting position greater than one within the encoded information for this data field type.

Length Enter the length of the data on this card. For Wiegand or proximity cards, this is the number of bits; for magnetic cards, it is the number of digits.

Complement For Wiegand cards only. Check this box if the field you are configuring requires complementing— that all 1s be changed to 0s and all 0s be changed to 1s. Specify complement for facility, site card number, and issue code field types only.

Parity Start For Wiegand/proximity cards only. This field displays the start of the data to be parity checked. This field applies only if Even Parity or Odd Parity is selected as the field type on the Type drop-down list.

Parity Start indicates the start position (in bits) of the data that should be parity checked.

For example, if the even parity bits are bits 2 through 13, enter 2 in this field for Even Parity. If the odd parity bits are bits 14 through 25, enter 14 in this field for Odd Parity.

Parity Length For Wiegand/proximity cards only. This field applies only if Even Parity or Odd Parity is selected as the field type on the Type drop-down list.

It indicates the number of bits that are to be parity-checked. For example, if bits 2 through 13 are the even parity bits, enter 12 in this field for Even Parity. If bits 14 through 25 are the odd parity bits, enter 12 in this field for Odd Parity.



The possible fields within the card format are described in Table 5-13.

Position Value Position Value determines the location of each field in the card number or CHUID that is constructed from the card data.

Enter this value in digits, with 0 being the right-most digit (position).

If you specify a Position Value of 0 for a field, the field is the right-most digit in the card number or CHUID. If you specify 3, the field is positioned 3 digits to the left of the right-most digit.

Example:

Suppose the personnel card number includes one Card Number field of 6 digits (24 bits) and a second Card Number field of 2 digits (8 bits).

If the order of the fields in the personnel card number is the first Card Number then the second Card Number field, enter 2 as the Position Value for the first (6-digit) Card Number field, and enter 0 as the Position Value for the second (2-digit) Card Number field. This results in the following personnel card number (notice that the right-most digit of the CN1 field is at position 2 and the right-most digit of the CN2 field is at position 0):

CN1-CN1-CN1-CN1-CN1-CN1-CN2-CN2

If the order of the fields in the personnel card number is the second (2-digit) Card Number field then the first (6-digit) Card Number field, enter 6 as the Position Value for the second Card Number field and enter 0 as the Position Value for the first Card Number field. This results in the following personnel card number (notice that the right-most digit of the CN1 field is at position 0 and the right-most digit of the two-digit CN2 field is at position 6):

CN2-CN2-CN1-CN1-CN1-CN1-CN1-CN1.

Field Data Data Value Enter specific data from a list of data for site and facility code, and fixed field types to specify that these fields have certain values associated with them. If a person swipes a card that does not match one of the specified values for each field type, the system does not permit access.

To enter a new value in the Data list, enter the value in this field and click Add.

Data The Data box lists the values that have already been added for the Site Code or Facility Code fields.

Buttons

Add Enter a value in the Data value field, then click Add to add it to the Data list for the field.

Delete In the Data box, highlight the value you want to delete and click Delete.

Table 5-12: Add/Update Format Field Dialog Box Fields, continued




Table 5-13: Card Format Types

Field Description

Facility/Company Code Data field that should contain identification unique to the company.

NOTE: If you are using extended cards and you included Access Facility Code in the CHUID, do not use this field in the card format. Instead, use the Card Number field (see below) to configure Access Facility Code in the card format. Use Facility Code only for non-extended cards.

Site Code Field that identifies the issuing site – for companies that issue cards from several locations.

Card Number NOTE: When configuring extended cards, you can include multiple Card Number fields in the card format. However, when using non-extended cards, you can only configure one Card Number field in the card format.

Extended Card Formats: For extended (256-bit) cards, select this field to specify the location of the following government card fields on the card and in the card data stream. You can only use these fields for extended card formats.

Agency Code

System Code

Credential

Credential Series Code

Credential Issue Code

HMAC

CardInt1-CardInt4: CardInt fields are user-name fields provided for proprietary extended card fields that you may use at your site. If you include a CardInt field in the card format, you must add the field to the Cards tab of the personnel view you are using so that you can enter the appropriate data in the field.

Access Facility Code

Issue Code

NOTE: When configuring extended cards, each Card Number field you configure must have a different Position Value to specify the location of the field in the card data stream.

Other Card Formats: For non-extended card formats, select this field to specify the location of the card number. In this case, the card number is a unique value in the system for each person with the same site or facility code.

Issue Code NOTE: If you are configuring an extended card format, and you are including Issue Code in the card format, use the Card Number field (see above) instead of the Issue Code field to configure the Issue Code. Use Issue Code only for non-extended cards.

This field indicates how many times a card with this card number has been issued. When the card is replaced (original is lost or damaged), this value is incremented by one. The number on the card must match the issue code in the person’s personnel record.



Fixed Data Field within the encoded information that remains the same for all cards used with the particular card format. Similar to facility and site codes.

Even Parity,Odd Parity

Select these field types to specify the location of the even and odd parity bits on the card. Parity bits are included on Wiegand and proximity access cards.

When you select a parity field:

In the Start position field, specify the location of the parity bit

In the Parity start field, specify the first bit to be parity-checked

In the Parity length field, specify the number of bits to be parity-checked

LRC Longitudinal Redundancy Check. This field is only available for extended card Wiegand and Proximity formats.

Expiration Date Field providing a way for a card reader to check whether or not a card is still valid through an expiration date encoded in the card. Once this card format is applied to a given reader, a cardholder whose card has an unexpired data is allowed access at the door. If, on the other hand, the cardholder presents a card with an expired date to a reader, the door stays locked, denying the cardholder access.

If the expiration date encoded on the card is the present date, the panel expires the card at the beginning of the following day.

The Expiration Date can only be one format: 64 bits (8 bytes), with one digit per byte, in the format YYYYMMDD.

NOTE: If the expiration date/time configured in the cardholder’s personnel record precedes the encoded expiration date, the panel expires the card at the earlier of the two dates.

Status Field where you can specify the start position of the Extended Reader Status Message on the card format. The length of the message is fixed to eight bits.

Table 5-13: Card Format Types, continued

Field Description


6

Configuring Inputs andOutputs

This chapter explains how to configure tamper and AC power failure inputs on the main panels and inputs and outputs on the controllers/main panels. For information on how to configure inputs and outputs on add-on boards, see Chapter 7.

In this chapter

Inputs Overview.............................................................................................................. 6-2

Configuring Inputs ......................................................................................................... 6-2

Input Events..................................................................................................................... 6-8

Viewing Input Linkages............................................................................................... 6-11

Configuring Outputs .................................................................................................... 6-13

Viewing Output Linkages............................................................................................ 6-16

Tamper and AC Power Failure Inputs....................................................................... 6-18

Inputs Overview


Inputs Overview

Use the following sections in this chapter to configure inputs. See Chapter 7 for more information.

Configuring Inputs

When you configure the panel or ACM, you also need to configure inputs so that the system can monitor the status of alarm devices.

To Configure Inputs Attached to this Controller/Panel

1. From one of the following dialog boxes select the number of the input you want to configure by clicking the appropriate check box:

• 1st ACM or 2nd ACM tab in the Controller dialog box.

• Panel Layout dialog box for the apC, apC/8X, or apC/L

The system automatically configures the input using the values from the default input definition and an assigned name.

NOTE Inputs on the controller ACMs are supervised inputs. Unsupervised inputs for the controller are located on the GCM. Inputs on the main panel, the WPSC, the I/8 - Input Module, and the I32 system input board are supervised inputs. All inputs on the apC/L are supervised. Unsupervised inputs for the apC and apC/8X are located on the standard star coupler. Unsupervised inputs must not be used in the protective circuit.

NOTE Inputs on a controller/panel are associated with the time zone that is specified for the controller/panel.

Configuring Inputs


2. To view or edit the input, click the input’s View button.

The Input dialog box opens, shown in Figure 6-1 on page 6-4.

NOTE To edit the default input, choose Input from the Hardware menu and click the Edit Default button in the Input Selection browser. The Input dialog box opens. See Table 6-1 on page 6-5 in this section for more information.

If Online is the default setting for the input and you do not de-select this option, the input is set online and downloaded after you click OK in the Controller/apC dialog box.

NOTE Clearing a reader, input, or output causes the security object to be deleted.

Configuring Inputs


Figure 6-1: Input Dialog Box


Configuring Inputs


Table 6-1: Input Dialog Box Fields


Identification Name Displays the input name as provided by the system. To change the input name, enter a unique name up to 50 characters long.

Online Click this check box to put the input online. By placing the input online, you direct the panel to begin monitoring this input and reporting state changes.

Offline inputs are ignored by the system and are not reported.

Description Enter a brief description of this input. The text here is for informational purposes only; it does not appear anywhere else.

Default state Armed Click this check box to specify that the normal operating state of the input is always operational. When you select this option, the C•CURE 800 continuously monitors state changes for the input (from active to inactive or from alert to normal). If the input’s state changes, a message appears on the General Activity Monitor.

You can configure other objects to arm or disarm the input, or you can use manual actions from the Monitoring Station to arm or disarm the input.

If you want to specify times when the input is armed, deselect this option and configure a time specification that activates an event that arms the input.

Supervision errors are reported for disarmed inputs.

NOTE: The default armed state of the input is only used to determine the actual armed state of the input when there are no actions affecting the armed state of the input.

Type Type Displays the type of input and lists the door or elevator to which the input is attached. Possible values are Normal, Door Switch Monitor (DSM), and Request to Exit (RTE), or Elevator. The system provides this value.

Configuring Inputs


Options Input is normally open

Click this check box to reverse the normal state of the monitoring point.

NOTE: This field is unavailable if you are configuring inputs for an apC.

Activate input on supervision errors

Click this check box if you want the system to treat supervision errors as activations as well as supervision errors. The system then initiates both supervision error events and activation events rather than just supervision error events when the input activates.

Send state changes of this event to monitoring station

Displays the event in the Monitoring Station. Click Send state changes of this event to monitoring station if you want the event displayed in the Event Monitor, the General Activity Monitor to display a message, and the Journal to log a message when this event changes state.

Neither the Event Monitor nor the General Activity Monitor will display activation and deactivation for this event should you clear this option. However, these event state changes will automatically be sent to the Journal unless both the Send state changes of this event to monitoring station and Send state changes of this event to journal options are cleared.

NOTE: If Incident ID functionality is enabled and this input is part of an Incident ID group, this check box and the next must be selected to make sure that all monitored activities and activity messages tagged with the Incident ID are sent to both the Monitoring Station and the Journal. For more information about Incident Tracking, see “Journal Reporting” in the C•CURE 800/8000 Reports Guide.

Send state changes of this event to journal

Click Send state changes of this event to journal if you want the journal to log a message when this event changes state.

NOTE: Clicking this option is useful only if you have cleared the Send state changes to monitoring station option. Event state changes are automatically sent to the journal when the Send state changes to monitoring station option is selected. Changes in events that are not sent to the Monitoring Station or to the Journal are not tracked by the system.

Table 6-1: Input Dialog Box Fields, continued


Configuring Inputs


Outputs Activation triggers output

Click this check box if you want this input, when it activates, to trigger an output or output group. Enter the name of the output or group in the text box.

Supervision error triggers output

Click this check box if you want an output or output group to activate when the system detects a supervision error for this input. Enter the output or group name in the text box.

Other screens Configure Events

Click this button to configure this input to activate events. See “Input Events” on page 6-8 for more information.

If this input is on a dialup panel, the events’ dialup setting determines when the panel dials the host and reports activities. See the C•CURE 800/8000 Software Configuration Guide for more information.

NOTE: You can configure an input used as an RTE or a DSM to trigger an event if the door to which the input is assigned has no readers.

You can also assign a “supervision error” event to an input used as a DSM or RTE.

View Linkages

Click this button to see the groups that contain this input. See “Viewing Input Linkages” on page 6-11 for more information.

Table 6-1: Input Dialog Box Fields, continued


Input Events


Input Events

Use the Input - events dialog box to configure events for the input.

To Configure Events for the Input

1. From the Input dialog box, click the Configure Events button. The Input - events dialog box opens, shown in Figure 6-2.

Figure 6-2: Input -Events Dialog Box


Input Events


Table 6-2: Input -Events Dialog Box Fields

Box Description

Supervision error causes event Click this check box to activate a specified event when this input is in supervision error. Double-click on the text box to display a list of events from which you can select. If the input is on a dialup panel, this event’s dialup setting determines whether the panel dials the host when there is a supervision error.

Use the Dialup box in the second Events dialog box to configure the event’s dialup setting.

Deactivation causes event Click this check box to activate a specified event when this input deactivates. Double-click on the text box to display a list of events to select. If this input is on a dialup controller/panel, the events’ dialup setting determines whether the panel dials the host when this input deactivates.


Tamper causes event Click this check box to activate a specified event triggered when the Inovonics transmitter detects a tamper.

Double-click on the text box to display a list of events to select. If this input is on a dialup controller/panel, the events’ dialup setting determines whether the panel dials the host when there is a supervision error. Use the Dialup box in the second Events dialog box to configure the event’s dialup setting.

This option is selected by default.

Battery low causes event Click this check box to activate a specified event triggered by low battery in the Inovonics transmitter.

Double-click on the text box to display a list of events to select. If this input is on a dialup controller/panel, the events’ dialup setting determines whether the panel dials the host when there is a supervision error. Use the Dialup box in the second Events dialog box to configure the event’s dialup setting.


Time-out causes event in n seconds

Click this check box to activate a specified event triggered if the bi-directional gateway does not receive a status message from the Inovonics transmitter within the time specified in the time-out event field. Double-click on the text box to display a list of events to select.

In the second field, enter a time in seconds in which the time-out event is triggered. The default value is 600 seconds and the maximum you can enter is 65535 seconds.

If this input is on a dialup controller/panel, the events’ dialup setting determines whether the panel dials the host when there is a supervision error. Use the Dialup box in the second Events dialog box to configure the event’s dialup setting.


Input Events


Time Spec Enter the time specification to be used for this input. Double-click on the text box to display a list of time specs from which you can select. After selecting a time spec, use the other options in this box to specify events to activate during the time spec and outside the time spec.

$Always is the default time spec.

Activation causes event...during time spec

Click this check box to specify you want an event to activate when the input activates (within the time span of the selected time spec). Enter the name of the event in the text box or double-click on it to choose from a list of possible events. If the input is on a dialup panel, this event’s dialup setting determines whether the panel dials the host when this input activates during the time specification.


Activation causes event...outside of time spec

Click this check box to specify you want an event to activate when the input activates (outside the time span of the selected time specification). Enter the name of the event in the text box or double-click on it to choose from a list of possible events. If the input is on a dialup panel, this event’s dialup setting determines whether the panel dials the host when this input activates outside the time specification.


Table 6-2: Input -Events Dialog Box Fields, continued

Box Description

Viewing Input Linkages



When you configure inputs, you have the option of viewing any groups that contain the input, any events that control the input, and any intrusion zones that contain the input.

To view linkages for inputs

1. From the Input dialog box, click the View Linkages button. The Input - linkages dialog box opens, shown in Figure 6-3.

Figure 6-3: Input Linkages Dialog Box

If you have defined groups for the input, configured an event to perform an action on the input, or included the input in an intrusion zone, the information shown in Table 6-3 on page 6-12 appears. These fields are read-only; you cannot enter any information.

NOTE If you are configuring a new system, there may not be any groups, events, or intrusion zones defined yet. For information about groups, events, and intrusion zones, see the C•CURE 800/8000 Software Configuration Guide.



2. If any information in this screen is not what you expect, check the security objects referencing this input to ensure that they are correctly configured.

3. Click Close to return to the Input dialog box.

Table 6-3: Input Linkages Dialog Box Fields

Box Description

Groups containing thisinput

Displays the groups in which this input is located.

Events controlling thisinput

Displays the events that can arm or disarm this input. If the input is listed in an event’s action list, that event appears here.

Intrusion Zone containing this input Displays the intrusion zone in which this input is located.

Configuring Outputs


Configuring Outputs

Use this section to configure outputs on the controller/main panel. See “Configuring Add-On Boards for apCs” on page 7-2 for more information.

An output turns an external device, such as a bell or siren, on or off. Outputs can also control other security devices such as closed circuit TV switches and alarm dialers.

To Configure the Outputs Attached to this Controller/Panel

1. From one of the following dialog boxes select the number of the output you want to configure by clicking the appropriate check box:

• 1st ACM or 2nd ACM tab in the Controller dialog box

• Panel Layout dialog box for the apC, apC/8X, or apC/L

The system automatically configures the output using values from the default output definition and an assigned name.

2. To view or edit the output, click the output’s View button.

The Output dialog box opens, shown in Figure 6-4 on page 6-14.

NOTE Outputs on a controller/panel are associated with the time zone that is specified for the controller/panel.

NOTE To edit the default output definition, choose Output from the Hardware menu and click the Edit Default button in the Output Selection browser. The Output dialog box opens. See the table for the Output dialog box in this section for more information.

If Online is the default setting for the output and you do not de-select this option, the output is set online and downloaded after you click OK in the Controller/apC dialog box.

NOTE Deselecting a reader, input, or output causes the security object to be deleted.

Configuring Outputs


Figure 6-4: Output Dialog Box

3. Provide the information shown in Table 6-4 and click OK.

Table 6-4: Output Dialog Box Fields


Identification Name Displays the output name as provided by the system. To change the output name, enter a unique name up to 50 characters long.

Description Enter a brief description of this output. The text here is for informational purposes only; it does not appear anywhere else.

Online Click this check box to put this output online. Offline outputs are ignored by the system and are not reported.

Type Type Displays Door, Alternate relay, Elevator, or Normal. If the output in a door’s configuration is a door relay, Alternate relay or elevator, the system shows the door to which it is configured. This field is read-only

Configuring Outputs


Options Pulse duration

1/10th sec.

Enter a value in 1/10ths of a second for the time the output will remain active when it is pulsed.

Send state changes of this event to monitoring station

Displays the event in the Monitoring Station. Click Send state changes of this event to monitoring station if you want the event displayed in the Event Monitor, the General Activity Monitor to display a message, and the Journal to log a message when this event changes state.

Neither the Event Monitor nor the General Activity Monitor will display activation and deactivation for this event should you clear this option. However, these event state changes will automatically be sent to the Journal unless both the Send state changes of this event to monitoring station and Send state changes of this event to journal options are cleared.

Send state changes of this event to journal

Click Send state changes of this event to journal if you want the journal to log a message when this event changes state.

NOTE: Clicking this option is useful only if you have cleared the Send state changes to monitoring station option. Event state changes are automatically sent to the journal when the Send state changes to monitoring station option is selected. Changes in events that are not sent to the Monitoring Station or to the Journal are not tracked by the system

Normally energized Click this check box if the output is normally energized. This means that the output is energized (power supplied to the relay) when it is inactive. When the output is activated, power is removed.

Other screens View Linkages Click this button to see the Output - linkages dialog box. See “Viewing Output Linkages” on page 6-16 for more information.

Table 6-4: Output Dialog Box Fields, continued


Viewing Output Linkages



When you configure outputs, you have the option of viewing any groups that contain the output, any security objects that control the output, and any intrusion zones that contain the output.

To View Linkages for Outputs

1. From the Output dialog box, click View Linkages. The Output - linkages dialog box opens, shown in Figure 6-5.

Figure 6-5: Output - Linkages Dialog Box

If you have defined groups for an output, associated the output with any security objects, or included the output in an intrusion zone, the information shown in Table 6-5 on page 6-17 appears. These fields are read-only; you cannot enter any information.

NOTE If you are configuring a new system, there may not be any groups or intrusion zones defined yet. For information about groups and intrusion zones, see the C•CURE 800/8000 Software Configuration Guide.



2. If any of the information on this screen is not what you expect, check the security objects referencing this output to ensure that they are correctly configured.

3. Click Close to return to the Output dialog box.

Table 6-5: Output -Linkages Dialog Box

Box Description

Groups containing this output

Displays the groups in which this output is located.

Security objects controlling this output

Displays the security objects that control this output.

Intrusion Zone containing this output

Displays the intrusion zone in which this output is located.

Tamper and AC Power Failure Inputs



The Panel status inputs box in the upper-left corner of the Panel Layout dialog box, shown in Figure 6-6, contains two special types of inputs: Tamper and AC power failure. Unlike other inputs to which you can assign any function, Tamper and AC power failure have specific definitions.

Figure 6-6: Panel Layout Dialog Box

The Tamper input activates when the apC, apC/8X, or apC/L cabinet is opened or removed from its mounting surface. If you want your panel to report activations of this input, click the Tamper check box. See the apC/8X or apC/L Installation and Configuration Guide for more information.

The AC 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 apC has lost its primary power source, and is operating on batteries. To use the AC power failure input, click the AC power failure check box. See the apC/8X or apC/L Installation and Configuration Guide for more information.

NOTE Inputs on a panel are associated with the time zone that is specified for the panel.



When you click the Tamper or AC power failure input’s check box, the system configures the input using values from the default input definition and an assigned name. To edit the input, click its corresponding View button. The Input dialog box opens. For an explanation of the fields on this dialog box, see “Configuring Inputs” on page 6-2.

NOTE Options that do not apply to the input are unavailable in the Input dialog box.


7

Configuring Add-onBoards for apCs and

iSTARs

This chapter explains how to configure different add-on boards for C•CURE 800/8000.

In this chapter

Configuring Add-On Boards for apCs......................................................................... 7-2

I/32 System Input Boards.............................................................................................. 7-5

R/48 System Output Boards ....................................................................................... 7-10

Star Couplers ................................................................................................................. 7-12

Mini-Star Coupler ......................................................................................................... 7-14

Wiegand/Proximity Star Coupler (WPSC) ............................................................... 7-15

I/8 — Input Modules ................................................................................................... 7-17

R/8 — Output Modules............................................................................................... 7-19

Configuring Add-On Boards for apCs



The Add-on boards button in the apC dialog box (and apC/8X dialog box) lets you configure the following add-on boards and controller:

8 apC I/8 - input modules and 1 apC I/32 System Input board

8 apC R/8 - output modules and 2 apC R/48 System Output boards

8 C•CURE Trac controllers (CID) with up to 8 readers per panel

1 Standard Star Coupler, or

1 Mini-Star Coupler, or

1 Wiegand/Proximity Star Coupler (WPSC)

The Add-on boards button in the apC/L dialog box lets you configure four I/8 - input modules, four R/8 - output modules.

To Open the Add-on Boards Dialog Box for an apC, apC/8X, or apC/L

1. From the apC dialog box (or apC/8X dialog box), click the Add-on boards button. The Add-on Boards dialog box opens. Figure 7-1 on page 7-3 shows the Add-on Boards dialog box for an apC (the dialog box is similar for apC/8Xs).

Table 7-1: Maximum Number of Boards for apCs, apC/8Xs, apC/Ls and iSTARs

I/32 I/8 R/48 R/8

apC 1 8 2 8

apC/L 0 4 0 4

apC/8X 1 8 2 8

iSTAR/acm 0 8 0 8

iSTAR/2acm 0 16 0 16



Figure 7-1: apC Add-on Boards Dialog Box

- or -

If you click the Add-on boards button in the apC/L dialog box, the apC/L Add-on Boards dialog box opens, shown in Figure 7-2 on page 7-3.

Figure 7-2: apC/L Add-on Boards View Selection

2. When you click in a check box and then click the View button, the Output or Input selection dialog box displays, as shown in Figure 7-3 on page 7-4.



Figure 7-3: Output selection from Add-on Boards Dialog Boxs

3. Once again, click in a check box and then click the View button. The Output or Input selection dialog box displays, as shown in Figure 7-4 on page 7-4.

Figure 7-4: Output View from Add-on Boards Dialog Box

I/32 System Input Boards



The I/32 boards provide additional inputs to the panel for monitoring security alarms. The I/32 Input boards have Class-A supervised inputs and 32 supervised alarm inputs.

To Add I/32 Input Boards

1. From the apC dialog box (or apC/8X window), click the Add-on boards button. The Add-on Boards dialog box opens, shown in Figure 7-5.

Figure 7-5: apC Add-on Boards View Selection Dialog Box

2. In the Supervised input boards box, click the check box and View button for the I/32 board. The I/32 dialog box opens, shown in Figure 7-6 on page 7-6.



Figure 7-6: I/32 Dialog Box

3. Choose the input that you want to add by clicking the appropriate check box. The system automatically configures the input using the values from the default input definition and an assigned name.

4. To view or edit the input, click the input’s View button. The Input dialog box opens, shown in Figure 7-7 on page 7-7.

NOTE To edit the default input, choose Input from the Hardware menu and click the Edit Default button in the Input Selection browser. The Input dialog box opens. See “Configuring Inputs” on page 6-2 for information about configuring inputs.

If Online is the default setting for the input and you do not clear this option, the input is set online and downloaded after you click OK in the apC dialog box.



Figure 7-7: Input on I/32 on apC

5. Edit the input for the add-on board as you would any input on the main panel. See “Configuring Inputs” on page 6-2 for information about configuring inputs.

6. In the I/32 dialog box, click OK to save the input board configuration.

To Open the Events Dialog Box

1. Open the Hardware menu and choose apC, apC/L or apC/8X. The apC dialog box opens.

2. Under Identification, enter the apC Name.

3. Click Events to open an Events dialog box, shown in Figure 7-8 on page 7-8, to configure panel events that activate under the conditions shown in the list that follows the figure.



Figure 7-8: apC Event Dialog Box

• Event to activate on communications failure:

– Enter an event that will be activated when a communications failure occurs on this port. Double-click on this text box to display a selection browser for events.

• Event to activate when panel becomes full:

– Enter an event to activate when the panel is full and cannot accept additional cardholder records. Double-click on this text box to display an Event Selection dialog box for a list of specific events.

• Event to activate when panel becomes nearly full (has reached a user-defined percent of capacity).

– Double-click on this text box to display an Event Selection dialog box for a list of specific events.

• Panel is nearly full when it reaches Enter an event to activate when the panel exceeds the capacity-used threshold specified in the % of capacity field. Double-click on this text box to display an Event Selection dialog box for a list of specific events.

NOTE The system determines the “nearly full” capacity by estimating the maximum number of cardholder records on the panel.



– Enter the percent of apC capacity for cardholder records that when reached, triggers the associated event (entered in the preceding field).

Example:

If you enter 85, the panel event activates when this panel reaches approximately 85% of capacity. The default value is 90.

NOTE The system generates a journal message when the panel reaches the capacity entered in this field, whether an event is configured or not.

R/48 System Output Boards



The R/48 boards provide additional outputs. You can add up to 2 R/48 boards to an apC or apC/8X.

To Add R/48 Output Boards

1. From the apC dialog box (or apC/8X dialog box), click the Add-on boards button. The add-on board dialog box opens (refer to Figure 7-1 on page 7-3).

2. In the Output boards dialog box, select the appropriate check box and click the View button for the R/48 board that you want. The R/48 dialog box opens, shown in Figure 7-9.






5. Edit the output for the add-on board as you would any output on the main panel. See “Configuring Outputs” on page 6-13 for information about configuring outputs.

6. In the R/48 window, click OK.

NOTE To edit the default output definition, choose Output from the Hardware menu and click the Edit Default button in the Output Selection browser. The Output dialog box opens. See “Configuring Outputs” on page 6-13 for information about configuring outputs.

If Online is the default setting for the output and you do not de-select this option, the output is set online and downloaded after you click OK in the apC dialog box.

Star Couplers


Star Couplers

Star couplers provide an alternate way to connect readers to the panel. The main apC board has one port for connecting readers. To connect 8 readers, each reader must be wired in a daisy-chain configuration.

Star couplers let you wire readers in a star (each reader is individually wired to the panel) or daisy-chain configuration. The panel still controls only a maximum of 8 readers.

The apC and apC/8X supports three types of star couplers:

Standard

Mini

Wiegand/Prox

To Add a Standard Star Coupler

1. From the apC dialog box (or apC/8X window), click the Add-on boards button. The Add-on Boards dialog box opens (see Figure 7-10).

Figure 7-10: apC/8X Add-on Boards Dialog Box

2. Select the Star option and click the View button. The Star Coupler dialog box opens, shown in Figure 7-11 on page 7-13.

Star Couplers


Figure 7-11: Star Coupler Dialog Box

3. Select the check boxes next to the readers, inputs and outputs that you want to add. The system automatically configures selected objects.

4. To view or edit selected objects, click the object’s corresponding View button.

5. Configure inputs, outputs and readers for the star coupler as you would any object on the main panel. If you need to refresh your memory about the fields on the dialog boxes, see earlier chapters of this guide.

Mini-Star Coupler


Mini-Star Coupler

The mini-star coupler works the same way as the standard star coupler. However, the mini-star coupler does not provide inputs and outputs.

To Add a Mini Star Coupler

1. From the apC dialog box (apC/8X window), click the Add-on Boards button. The add-on boards dialog box opens.

2. Select the Mini Star option and click the View button. The Mini Star dialog box opens, shown in Figure 7-12.

Figure 7-12: Mini Star Dialog Box

3. Select the readers that you want to configure by clicking the appropriate box. The system automatically configures selected readers.

4. To view or edit selected readers, click the reader’s corresponding View button.

5. Configure readers for the mini star coupler as you would any reader on the main panel. See “Configuring Readers” on page 5-2 for more information.

Wiegand/Proximity Star Coupler (WPSC)



The Wiegand/proximity star coupler is a two board set that allows you to connect proximity and Wiegand readers directly to the apC (apC/8X). The lower WPSC board provides connections for readers 1 - 4 and inputs numbered 17, 19, 21, and 23. The upper WPSC board provides connections for readers 5 - 8 and inputs numbered 25, 27, 29, and 31.

The WPSC lower board has four direct connect Wiegand reader ports and four supervised inputs. The WPSC upper board also has four direct connect Wiegand reader ports and four supervised inputs. The reader ports and inputs are numbered as shown in Table 7-2.

Each reader port and supervised input is a pair. Input 17 is associated with reader 1, input 19 is associated with reader 2, etc. The inputs are not available until the reader is selected, put online, and enabled by SW1. SW1 is an eight position DIP switch that determines whether the reader port is enabled on the WPSC or is available for an RM reader bus port on the apC.

Set SW1-n ON (closed) to use the WPSC reader port.

NOTE The inputs are not available until the reader is selected, put online, and enabled by the switch. See the WPSC Quick Start Installation Guide for more information.

Table 7-2: WPSC Boards - Reader Ports and Inputs

BoardReader Port SW1

Supervised Input

Lower 1 SW1-1 17

2 SW1-2 19

3 SW1-3 21

4 SW1-4 23

Upper 5 SW1-5 25

6 SW1-6 27

7 SW1-7 29

8 SW1-8 31



Set SW1-n to OFF (open) to disable the port on the WPSC and make it available to the apC as an RM reader bus port.

To Add a Wiegand/Proximity Star Coupler

1. From the apC dialog box (apC/8X dialog box), click the Add-on boards button. The Add-on Boards dialog box opens (see Figure 7-10 on page 7-12).

2. Click the option button for WPSC and View to view the panel layout for the Wiegand/Proximity star coupler, shown in Figure 7-13.

Figure 7-13: Wiegand/Proximity Star Coupler Dialog Box

3. If you have an upper board, select the WPSC upper board is installed check box in the upper-right corner.

4. Select the check box next to the item that you want to configure. The system automatically configures the object.

5. To view or edit selected objects, click the object’s corresponding View button.

6. Configure inputs and readers for the Wiegand/proximity star coupler as you would any object on the main panel. If you need to refresh your memory about the fields on the dialog boxes, see earlier chapters of this guide.

I/8 — Input Modules



The I/8 - input module provides additional inputs to the panel for monitoring security alarms. The I/8 - input module has Class-A supervised inputs;8 supervised alarm inputs for apCs, apC/8Xs, and apC/Ls. To configure I/8 - Input Modules on ACMs, see “Configuring I/8 - Input Modules for iSTAR” on page 1-28.

To Add I/8 - Input Modules

1. From the apC dialog box (apC/8X or apC/L dialog box), click the Add-on boards button. The Add-on Boards dialog box opens.

2. In the Supervised input boards box, choose the I/8 - input module you want by clicking the appropriate check box and View button for the board. The I/8 dialog box opens, shown in Figure 7-14.

Figure 7-14: I/8 Dialog Box

NOTE The I/8 - input modules cannot be connected to the WPSC. You must connect these boards to the reader bus port on the panel.



3. Choose the input that you want to add by clicking the appropriate check box. The system automatically configures the input using the values from the default input definition and an assigned name.

4. To view or edit the input, click the input’s View button. The Input dialog box opens.

5. Edit the input for the add-on board as you would any input on the main panel. See “Configuring Inputs” on page 6-2 for information.

6. In the I/8 window, provide the information shown in Table 7-3 on page 7-18 in the Events box and click OK:

NOTE To edit the default input, choose Input from the Hardware menu and click the Edit Default button in the Input Selection browser. The Input dialog box opens. See “Configuring Inputs” on page 6-2 for information.

If Online is the default setting for the input and you do not de-select this option, the input is set online and downloaded after you click OK in the apC dialog box.

Table 7-3: I/8 Dialog Box Events Box Fields

Box Description

Activate this event while board tampered

Enter an event to activate when the board is tampered.

If this board is on a dialup panel, the event’s dialup setting determines whether the panel dials the host when the board is tampered. See the C•CURE 800/8000 Software Configuration Guide for more information.


Enter an event to activate when there is a communications failure between the board and the panel.

If this board is on a dialup panel, the event’s dialup setting determines whether the panel dials the host when a communications failure occurs. “Setting Dialup Options for Events” in the C•CURE 800/8000 Software Configuration Guide for more information.

R/8 — Output Modules



The R/8 - output modules provide additional outputs. You can add up to 8 R/8 -output modules to an apC or apC/8X, and up to 4 R/8 - output modules per apC/L. To configure R/8 - Output Modules on ACMs, see“R/8 - Output Modules for Controllers” on page 1-31.

To Add R/8 Output Modules

1. From the apC dialog box (apC/8X or apC/L dialog box), click the Add-on boards button. The Add-on Boards dialog box opens (see Figure 7-10 on page 7-12).

2. In the Output boards box, choose the R/8 - output module that you want by clicking the appropriate check box and View button for the board. The R/8 dialog box opens, shown in Figure 7-15.


NOTE The R/8 - output modules cannot be connected to the WPSC. You must connect these boards to the reader bus port on the panel.





5. Edit the output for the add-on board as you would any output on the main panel. See “Configuring Outputs” on page 6-13 for information.

6. In the R/8 window, provide the information shown in Table 7-4 on page 7-20 in the Events box and click OK.

NOTE To edit the default output definition, choose Output from the Hardware menu and click the Edit Default button in the Output Selection browser. The Output dialog box opens.See “Configuring Outputs” on page 6-13 for information.

If Online is the default setting for the output and you do not de-select this option, the output is set online and downloaded after you click OK in the apC dialog box.

Table 7-4: R/8 Dialog Box Fields

Box Description

Activate this event while board tampered

Enter an event to activate when the board is tampered.

If this board is on a dialup panel, the event’s dialup setting determines whether the panel dials the host when the board is tampered. See “Setting Dialup Options for Events” in the C•CURE 800/8000 Software Configuration Guide for more information.


Enter an event to activate when there is a communications failure between the board and the panel.

If this board is on a dialup panel, the event’s dialup setting determines whether the panel dials the host when a communications failure occurs. See “Setting Dialup Options for Events” in the C•CURE 800/8000 Software Configuration Guide for more information.


8

Configuring Ports

The C•CURE 800/8000 lets you attach devices, such as controllers, panels, modems, and switchers, to COM ports (serial ports on your PC) and network ports. This chapter explains how to configure both COM and network ports.

In this chapter

Overview .......................................................................................................................... 8-2

Configuring COM Ports from Windows ..................................................................... 8-3

Configuring Network Ports........................................................................................... 8-6

Configuring Ports from C•CURE 800/8000 ............................................................... 8-8

Overview


Overview

To ensure that C•CURE 800/8000 communicates properly with devices such as controllers, panels, modems, and switchers, you use the C•CURE 800/8000 Port Configuration dialog box to configure the ports to which devices are attached. You must also configure the COM ports from the Windows Control Panel.

See the following sections in this chapter for information about configuring COM ports:

“Configuring COM Ports from Windows” on page 8-3

“Configuring Ports from C•CURE 800/8000” on page 8-8

See the following sections in this chapter for information about configuring network ports:

“Configuring Network Ports” on page 8-6

“Configuring Ports from C•CURE 800/8000” on page 8-8

Configuring COM Ports from Windows



Use the Ports icon on the XP Control Panel to configure COM ports for controllers, panels, modems, and CCTV switchers. This is separate from the C•CURE System Administration application; consult your Microsoft Windows System Guide for complete information.

You can configure communications ports using the Hardware menu on the administration application.

There are 3 types of ports that you can configure:

RS-232 serial COMM ports

NET ports for terminal servers

RAS ports for iSTAR dialup and serial connection

Configuring RS-232 serial COMM ports

You can configure up to 255 COMM ports. They are used for apC’s, RS-485 converters, modems, line drivers, Bi-directional devices, and CCTV.

You may try to run an application, like hyper-terminal, on the server machine that requires a certain COM port and it will not run because the C•CURE 800/8000 driver has the port. You can set that port off-line on this screen, as long as the 800 driver is not using it.

It is important to set the port characteristics in Windows when using RS-232 ports.

To configure COM Ports from Windows

1. Right-click My Computer and select Manage>System Tools>Device Manager>Ports>desired port.

2. On the Communications Port Properties dialog box, select the Port Settings tab.

3. Configure the port settings according to the information in the following paragraphs and Table 8-1 on page 8-5.



• Bits per second (Baud rate) indicates the maximum speed of the port. In some cases it must be set to precisely the transfer rate of the device that is connected to it. A Baud rate of 9600 means that the data is transferred at the rate of 960 characters per second.

Example:

9600 / 10

There are 10 bits to each 8 bit character because each has a start bit and a stop bit.

• Data bits are usually 8. There are some devices that you might be interfacing, such as the Stentofon intercom that use 7 bits, but most devices are 8 and 1. (8 for iSTAR controllers, apC panels, and modems. See the CCTV switcher documentation to check this setting for your switcher.)

• Parity varies. Match with the parity for the modem, iSTAR controller, panel, or switcher. (Modems and controllers use None, while panels default to Even. See the CCTV switcher documentation to check this setting for your switcher.)

• Stop bits are usually 1. (1 for iSTAR controllers, panels and modems. See the CCTV switcher documentation to check this setting for your switcher.)

• Flow control varies. (It is None for panels and modems and Hardware for iSTAR controllers. See the CCTV switcher documentation to check this setting for your switcher.)



4. When you finish specifying the settings, click OK.

Table 8-1: Port settings

Device Baud Rate Data bits Parity Stop Flow Control

apC Direct 9,600 8 Even 1 None

apC Dialup 9,600 8 None 1 None

iSTAR Serial 57,600 8 None 1 Hardware

iSTAR terminal session

115,200 8 None 1 Hardware

Stentofon 9,600 7 Even 1 None

APT-2 1,200 8 None 1 None

AD-PTZ 1,200 8 None 1 None

Radionics (6500-6600)

1,200 8 None 1 None

Configuring Network Ports



The Communications Port dialog box, shown in Figure 8-4 on page 8-10, lets you configure TCP/IP network ports for communication with devices, such as apCs and modems. The dialog box also permits you to enable iSTAR dialup and serial communications by configuring Windows Remote Access Service (RAS) on a port.

apC Panels

To attach an apC device to a network port, connect the device to a network server device on the network, and use the Communications Port dialog box to configure the network port. See “Configuring Ports from C•CURE 800/8000” next in this section for configuration instructions.

For example, to attach an apC to a network port, connect it to a terminal server device on the network; use the Communications Port dialog box to configure the network port; and in the apC dialog box, select the network port for the apC. See the terminal server device’s documentation for information about setting up the network server.

Figure 8-1 on page 8-7 shows the typical methods for connecting an apC to a C•CURE 800/8000 Server.

NOTE A different configuration method is used for iSTAR controllers connected to the host over a network. See “Configuring iSTAR Classic & iSTAR Pro Controllers” on page 1-12 for more information.



iSTAR Controllers

Figure 8-1 also shows a typical network iSTAR configuration, using a network connection as the primary connection and a dialup connection as the secondary connection.

Figure 8-1: Typical Network iSTAR and apC Configuration

Configuring Ports from C•CURE 800/8000



The C•CURE 800/8000 Communications Port dialog box lets you configure your system’s ports for communication with C•CURE 800/8000. Use this dialog box to add, edit, and delete ports.

To Add Ports

1. From the C•CURE 800/8000 Administration application, select Hardware->Communications Port from the menu. The Comm Port Selection browser opens, shown in Figure 8-2. The selection browser displays the ports on your computer that are configured for communication with C•CURE 800/8000.

Figure 8-2: Comm Port Selection Browser

2. Click New. The Communications Port dialog box opens (Figure 8-3 on page 8-9).



Figure 8-3: Communications Port Dialog Box.

3. In the Port type list box, select COM Port to specify that this is a serial port attached to the computer.

- or -

Select Network Port to specify that this is a network port.

When you select Network Port, the Name list box changes to an edit field and the Network Port Options box becomes available, as shown in Figure 8-4 on page 8-10.



Figure 8-4: Communications Port Dialog Box with Network Port Options


NOTE Select the port type before changing the name or other configuration information for the port. You cannot change the port type once you have configured this dialog box and clicked OK.



Table 8-2: Network Port Options


Identification Name Specify a name for the port using one of the following methods:

If you are configuring a COM port, select a name for the port from the Name drop-down list. The drop-down list box is available only when COM port is selected in the Port type field. The system assigns names to ports that are attached to PCs using COM# format (where # equals the number for the port). For example, COM1 represents the first port on your system. You can select from COM1 to COM256.

If you are configuring a network port, enter a unique name up to 50 characters long into the Name field. This field is editable only when Network Port is selected in the Port type field. For network ports, do not enter a name that starts with the characters COM, followed by a number.

Example:

Do not enter COM1.

If you enter the name of an existing port (or other security object), the system returns an error message indicating there is a conflict.

If you are editing a port and change the port’s name, the physical address for the port configuration is changed. For example, if an apC chain is attached to COM5 and you rename COM5 to COM6, the configuration for port #5 is deleted, port #6 is configured as COM6, and the apC chain that was originally attached to port #5 must be re-attached to port #6.

Description Enter a general comment about the port. This text is for information only.

Online Select this check box to put the port online. If you do not put the port online, the system ignores devices connected to the port.

NOTE: If you select the Use Windows Remote Access Service (RAS) on this port option, you must click this box and put the port online.

Port type Select the type of port you are configuring: COM Port or Network Port. Select the port type before configuring other fields in the Communications Port dialog box. When you select Network Port, the Network Port Options box becomes available.

NOTE: After you configure a port and click OK in the Port Configuration dialog box, you cannot change the port type for the port. If you edit the port, this field is unavailable.



Identification (cont.) Port timeout delay time:

1/10th sec.

Enter the extra interval in 1/10ths of a second that the host waits for a response from devices on this port after sending a message to the device.

This field applies to ports for apCs only.

The operating system automatically generates a timeout delay based on the communications speed of the port on which the device resides. The Port timeout delay time is added to the system-generated timeout delay and starts after the system-generated timeout expires. If the host does not receive a response before the Port timeout delay time expires, the Poll timeout delay time for the individual apC or switcher starts or the Modem response wait time for the modem starts.

For example, the total timeout delay for an apC is equal to: system-generated delay time + Port timeout delay time + Poll timeout delay time.

The system-calculated timeout delay is usually sufficient. However, if you require additional delay time for a network port, increment the value by 1 up to a maximum of 5. Keep this value as small as possible, or system performance may be affected.

This option lets you specify one timeout delay for all devices attached to the network port.

Example:

If you have several apCs on a network port, use this field to specify one timeout delay for each apC.

See “Configuring Panels” on page 4-5 for information about the poll timeout delay time for apCs; “Configuring Advanced Options for Non-OEM Host Modems” on page 9-8 for information about the Modem response wait time for modems; and the C•CURE 800/8000 CCTV Guide for information about poll timeout delay time for CCTV switchers.

Activate this event during comm failure

Enter an event to activate when a communications failure occurs on this port. Double-click in this box to display a selection browser for events.

NOTE: This field does not apply to iSTAR dialup/serial RAS connections.

Table 8-2: Network Port Options, continued




Identification (cont.) Use Windows Remote Access Service (RAS) on this port(This option is required for iStar dialup/serial connection)

Select this check box to enable RAS. Selecting this option indicates that this communications port is to be used for iSTAR connections to the host.

NOTE: You must select this option to use dialup or serial communications for iStar controllers. See the “iSTAR Dialup Overview” on page 11-2 for more information.

Network Port Options

NOTE: The fields in this box do not apply to iSTAR controllers.

TCP port For network ports, enter the TCP port number of the network server device. This value is set when you configure the device. See the documentation for the network server device for more information.

If COM Port is selected in the Port type list box, this field is unavailable.

IP address For network ports, enter the IP address of the network server device. This value is set when you configure the network server device. See the network server device documentation for more information.

If COM Port is selected in the Port type list box, this field is unavailable.

Network Port Options Reconnection retry period:

1/10th seconds

For network ports, enter the time period in 1/10ths of a second that the system tries to reconnect to this port when the port is in communication failure.Values range from 0 to 99. The default value is 3 seconds.

Depending on your network configuration, it may take some time for the system to detect communication failures with network server devices.

If COM Port is selected in the Port type list box, this field is unavailable

Table 8-2: Network Port Options, continued



9

Configuring andSelecting Host

Modems for apCPanels and iSTAR


This chapter explains how to configure the host modems to work with dialup for apCs and iSTARs. It also describes how you select the host modems for dial in and dial out for both apCs and iSTARs. To install and wire remote modems, consult the apC/8X Installation and Configuration Guide and the apC/L Installation and Configuration Guide for modems for the apC panels and the C•CURE iSTAR Hardware Installation Guide for modems for the iSTAR controllers.

In this chapter

Configuring Host Modems............................................................................................ 9-3

Configuring Advanced Options for Non-OEM Host Modems................................ 9-8

Selecting Host Modems for Dial In ............................................................................ 9-10

Selecting Host Modems for Dial Out ......................................................................... 9-13

Overview


Overview

The procedures in this chapter cover the setting of the modem parameters in the C•CURE 800/8000 Server. Before any of them can be performed, the modem port must be configured as described in Chapter 1.

Host Modems for apCs

The Software House ACD Customer Support Center supports only the OEM host modem, which has been extensively tested with C•CURE 800/8000. While other modems supported by Windows may work, they are not supported by Software House and such modems can have subtle differences in operation that cause undefined problems with your system.

Host Modems for iSTARs

Although any non-OEM host modem supported by Windows may work, Software House ACD Customer Support Center recommends the U.S. Robotics modem for dialup applications. If a direct serial connection is to be used, the Dial-Up Networking Serial Cable modem option is used.

Configuring Host Modems



The Modem dialog box lets you set up host modems for dialup apC panels and directly-connected serial or dialup iSTAR controllers. Configure the host modems before configuring the dialup panels or controllers.

To Configure Modems for the Host

1. From the C•CURE 800/8000 Administration application, select Hardware->Host Modem from the menu bar. The Modem Selection browser opens, shown in Figure 9-1.

Figure 9-1: Modem Selection

2. Click New to configure a new modem. The Modem dialog box appears with the General tab displayed, as shown in Figure 9-2 on page 9-4.



Figure 9-2: Modem Dialog Box

3. In the Identification box, provide the information shown in Table 9-1.

4. In the General tab, provide the information shown in Table 9-2 on page 9-5 and then go to Step 5.

Table 9-1: Identification Dialog Box


Identification Name Enter a unique name up to 50 characters long.

If you enter the name of an existing modem (or other security object), the system returns an error message indicating there is a conflict.

Description Enter a general comment about the modem. This text is for information only.

Online Click this check box to put the modem online.

While a modem is online, C•CURE 800/8000 attempts to communicate with it.

When you place a modem offline, it is ignored by C•CURE 800/8000. The modem may continue to operate, but C•CURE 800/8000 does not attempt to contact dialup panels/controllers via offline modems or answer calls received by an offline modem.



5. In the Phone numbers that reach this modem box, use the following buttons to configure the list of phone numbers that reach this modem:

• Add opens the Enter new phone number dialog box where you specify a number that you want to add to the phone number list. See “Adding Phone Numbers” on page 9-6 for information about using this dialog box.

• Remove removes the selected phone number from the phone number list.

Table 9-2: General Tab Fields


General Port Enter the port to which this modem is connected. Double-click on the box to display a list of ports configured for C•CURE 800/8000. The list includes COM and network ports. See the “iSTAR Dialup Overview” on page 11-2 for more information.

If you select a port that is being used by another device, C•CURE 800/8000 displays an error message.

Modem Use apC Select this option to specify that this modem is used with apC panels. When you select this option, the Advanced tab becomes available.

iSTAR Select this option to specify that this modem is used with iSTAR controllers.

Direction Dial out only Select this option to specify that this modem is used only for dialing out to panels/controllers.

Dial in only Select this option to specify that this modem is used only for dialing into the host.

Dial in and dial out Select this option to specify that this modem is used for both incoming and outgoing calls.

Phone numbers that reach this modem

Phone number list Displays the list of phone numbers that reach this host modem. Use the buttons to the right of the list to modify the numbers in the list. See Step 5 following this table for instructions on configuring this list.

If Dial out only is selected in the Direction box, this box and the Add, Remove, and Modify buttons are unavailable.



• Modify opens the Modify existing phone number dialog box where you edit the selected phone number in the phone number list. See “Modifying Phone Numbers” on page 9-7 for more information.

6. Click the Advanced tab to configure advanced options for the modem.See “Configuring Advanced Options for Non-OEM Host Modems” on page 9-8 for more information. This button is available only if you selected apC as the option in the Modem Use box.

7. Click OK. The configuration for the host modem is saved and the Modem dialog box closes.

Adding Phone Numbers

There is no formatting standard for phone number entry in the C•CURE 800/800 Modem dialog box. You can enter any combination of 35 alphanumeric characters in the Phone number field.

To Add Phone Numbers

1. From the General tab in the Modem dialog box, click the Add button in the Phone numbers that reach this modem box. The Enter new phone number dialog box opens, shown in Figure 9-3.

Figure 9-3: Enter New Phone Number Dialog Box

2. In the Phone number box, enter a phone number for the modem and click OK. The phone number can be up to 35 characters long.

NOTE The Enter new phone number dialog box also opens when you add remote phone numbers for panel modems. See “Selecting Host Modems for Dial Out” on page 9-13 for more information.



Modifying Phone Numbers

To Modify Phone Numbers

1. From the General tab in the Modem dialog box, select a phone number and click the Modify button in the Phone numbers that reach this Modem box. The Modify Existing Phone Number dialog box opens, shown in Figure 9-4.

Figure 9-4: Modify Existing Phone Number Dialog Box

2. In the Phone Number box, change the phone number for the modem and click OK. The phone number can be up to 35 characters long.

NOTE The Modify existing phone number dialog box also opens when you modify remote phone numbers for panel modems. See “Selecting Host Modems for Dial Out” on page 9-13 for information about the second apC Dial-Out Components dialog box.

Configuring Advanced Options for Non-OEM Host Modems



The Software House Customer Support Center supports only the OEM host modem for apCs. If you choose to use a non-OEM host modem, the Advanced tab in the Modem dialog box lets you configure advanced options for your modem.

To Configure Advanced Options for Host Modems

1. In the Modem dialog box, click the Advanced tab, shown in Figure 9-5.

Figure 9-5: Advanced Tab

2. Provide the information shown in Table 9-3 on page 9-9 in the Advanced tab.

NOTE This tab is unavailable if you selected the iSTAR option in the Modem Use box on the General tab.



Table 9-3: Advanced Tab Fields

Field Description

Modem initialization string Enter the string of characters that the host uses to initialize the modem. See your modem’s documentation for information.

Modem response wait time:

seconds

Enter the extra time that the host waits for a response from this modem after sending a message to the modem.

Enter a time from one second to four minutes. The default value is ten seconds.

Connect to host wait time:

mm:ss

Enter the extra time that the host waits for a response from the panel after dialing the panel from this modem.

Enter a time from one second to four minutes using mm:ss format. The default value is one minute.

Redial/reconnect delay time:

seconds

Enter the time that the host waits after losing a host-initiated connection with a panel before trying to recontact the panel. Enter a time from one second to four minutes using mm:ss format. The default value is eight seconds.

Use DTR Enter whether DTR hang-ups are supported by this modem and wiring. If the modem is attached to a network port, do not select this option.

DTR off time:

milliseconds

Enter the time that the host keeps DTR off when hanging up the modem. Enter a time from one to 9999 milliseconds. The default value is one second.

If Use DTR is not selected, this field appears dimmed.

Modem answer delay time:

milliseconds

Enter the time that the host modem waits to answer a ring after getting a ring signal. Enter a time from one to 9999 milliseconds (about 90 seconds). The default value is 200 milliseconds.

Modem status check time period:

mm:ss

Enter a time period at which the host checks this modem when the modem is inactive. For example, if you enter 65 seconds, the host contacts this modem every 65 seconds while the modem is inactive to verify that the modem is operating properly.

Enter a time from one second to 59 minutes using mm:ss format. The default value is 65 seconds.

Selecting Host Modems for Dial In



The apC/Controller Dial-In Components dialog box lets you configure a list of host modems and phone numbers that can be contacted by a panel/controller You must configure host modems and phone numbers in the Modem dialog box before you can select modems/phone numbers for dial in. See “Configuring Host Modems” on page 9-3 for more information about the Modem dialog box.

To Select Host Modems and Phone Numbers for Dial In

1. In the apC dialog box, shown in Figure 9-6, type a name the Identification Name field and choose Online with the Identification Online check box.

2. Next, under the General drop-down selection lists, select the apC Type and Dialup in the Connection Type selection list.

3. When you click the Dialup Configure button, the Dialup Components dialog box will be displayed. The apC dialog box is covered in detail in Chapter 4 and its fields are explained in Table 4-1 on page 4-7.

Figure 9-6: apC Dialog Box.

4. If the iSTAR box is checked, then the selected port must have the RAS option checked in the Port Configuration dialog box.



5. In the Dial In tab on the Dialup Components dialog box, click Modify. The apC/Controller Dial-In Components dialog box, as shown in Figure 9-7, will be displayed. For further information about the Dialup Components dialog box, see “Configuring apC Dialup Panels” on page 10-6.

Figure 9-7: apC/Controller Dial-In Components Dialog Box

6. In the Select host modem and host phone number box, select a host modem and host phone number and click the Add Pair button. The modem/phone number combination is added to the Host modems and host phone numbers which can be contacted by panel box.

You can select any combination of modems and phone numbers. For example, you can enter Modem 1 with three different phone numbers.

NOTE If you are configuring host modems for iSTARs, the title bar of the dialog box that opens reads Controller Dial-In Components.



You can also enter a modem/phone number combination more than once.

7. For each modem/phone number combination that you want to add, repeat Step 2 on page 9-10. The Host modems and host phone numbers which can be contacted by this panel box can hold up to 8 modem/phone number combinations.

8. In the Host modems and host phone numbers which can be contacted by this panel box, use the following buttons to edit the list of host modem/host phone number combinations.

• Remove removes the selected modem/phone number combination from the list.

• Remove All removes all modem/phone combinations from the list.

• Move Up moves the selected modem/phone number combination up one position in the list.

• Move Down moves the selected modem/phone number combination down one position in the list.

• The panel calls the host modems/phone numbers in the order that they are listed in this box.

9. Click OK to save the list of modem/phone numbers.

NOTE To edit or add a modem, click the Edit Modems button. The Modem Selection browser opens. See “Configuring Panels” on page 4-5 for more information.

Selecting Host Modems for Dial Out



The apC/Controller Dial Out Components dialog box lets you configure a list of host modems/phone numbers that the host can dial to contact the dialup panel/controller. Perform the following tasks to configure the list:

Use the Add phone, Modify, and Remove buttons to configure a list of phone numbers that reach the modem attached to this panel/controller. See “To Configure Phone Numbers that Reach this Dialup Panel/Controller” on page 9-13 for instructions.

Use the Add Pair, Remove, Remove all, Move up, and Move down buttons to configure a list of host modem/remote phone number combinations for dial out. See “To Configure a List of Host Modems/Remote Phone Numbers for Dial Out” on page 9-15 in this section for instructions.

To Configure Phone Numbers that Reach this Dialup Panel/Controller

1. In the Dial Out tab on the Dialup Components dialog box, click the Modify button. The apC/Controller Dial-Out Components dialog box opens, shown in Figure 9-8 on page 9-14.

NOTE If you are configuring host modems for iSTARs, the title bar of the dialog box that opens reads Controller Dial-In Components.



Figure 9-8: apC/Controller Dial-Out Components Dialog Box

2. In the Remote phone numbers box, use the following buttons to edit the list of numbers for the panel/controller modem:

• Add phone opens the Enter new phone number dialog box where you add a phone number for the panel/controller modem. See “Adding Phone Numbers” on page 9-6 for more information.

• Modify opens the Modify existing phone number dialog box where you modify the selected phone number. See “Modifying Phone Numbers” on page 9-7 for more information.

• Remove deletes the selected phone number from the list of numbers for the modem.



To Configure a List of Host Modems/Remote Phone Numbers for Dial Out

1. In the apC/Controller Dial-Out Components dialog box, select a modem and remote phone number in the Select host modem and remote phone number box and click the Add Pair button. The modem/phone number combination is added to the Host modems which can contact this panel box.

2. You can select any combination of modems and phone numbers. For example, you can enter Modem 1 with three different phone numbers. Also, you can enter a modem/phone number combination more than once.

3. Repeat Step 1 in this procedure for each modem/phone number combination that you want to add.

4. In the Host modems which can contact this panel box, use the following buttons to edit the list of host modem/remote phone number combinations.

• Remove removes the selected modem/phone number combination from the list.

• Remove all removes all modem/phone combinations from the list.

• Move up moves the selected modem/phone number combination up one position in the list.

• Move down moves the selected modem/phone number combination down one position in the list.

• The host calls the panel modems/phone numbers in the order that they are listed in this box.

5. Click OK to save the list of modem/phone numbers.

NOTE To edit or add a modem to the list of host modems, click the Edit modems button. The Modem Selection browser opens. See “Configuring Panels” on page 4-5 for more information.


10

Configuring Dialup forapC Panels

This chapter explains how to configure the apC panels to work in dialup mode with C•CURE 800/8000. To install and configure hardware for the apC/8X, and apC/L, consult the apC/8X Installation and Configuration Guide and the apC/L Installation and Configuration Guide.

In this chapter

apC Dialup Overview................................................................................................... 10-2

Configuring apC Dialup Panels.................................................................................. 10-6

Configuring Options for apC Dial-up Panels ......................................................... 10-10

apC Dialup Overview


apC Dialup Overview

Dialup apCs let you connect the C•CURE 800/8000 host to panels at remote locations using modems and standard telephone lines.

To set up dialup panels, attach modems to the host and to remote panels. You can attach host modems to the server’s COM ports and also to its network ports. Figure 10-1 shows a typical host/dialup panel configuration.

Figure 10-1: Typical Host/Dialup Panel Configuration

How Dialup Panels Work

Unlike direct-connect panels that are always linked to the host, dialup panels are connected to the host only while a telephone connection is established. Several C•CURE 800/8000 functions are controlled by the panels, not by the C•CURE System host. All panels perform the following operations:

Access control decisions for doors and elevators

Anti-passback: tracks personnel movement, but does not enforce anti-passback

Dialup panels that are not connected to the host and direct-connect panels that are in communications failure perform the following additional functions:

apC Dialup Overview


• Each input can activate at most one output (or output group) on the panel, and each output can be activated by at most one input on the panel

• Time specifications can only activate events that activate and pulse outputs, arm inputs, unlock doors, and cause readers to require PINs.

However, if one of the following options is configured for the event, the event actions are not performed: the event requires acknowledgement, an activation delay or a minimum activation time has been specified, or the time zone of the time specification triggering the event is different from the time zone of the object on which the action is being performed.

• Time specifications that require PINs can be downloaded from the Reader keypad configuration dialog box.

• Either the host or panel can establish a telephone connection. The following sections describe the conditions that cause the host to dial the panel, and the panel to dial the host.

Dialing Out to Panels

The host dials the panel and downloads information under the following conditions:

Periodic and Dial Out The C•CURE 800/8000 provides two dialout configurations that you can use to specify when the host dials panels. Use Periodic to specify that configuration changes and cardholder information are periodically downloaded to panels, and activity is uploaded to the host from the panel. Use Dial Out to specify that configuration changes are automatically downloaded to panels within a specified time. See “Configuring Dial Out Options for Host and Panels” on page 10-13 and “Configuring Periodic Dial Out Options for Host and Panels” on page 10-15 for more information.

Manual actions at the Monitoring Station Users at the Monitoring Station can connect the host to dialup panels using the Connect manual action on the apC dialog box. See the C•CURE 800/8000 Monitoring Station Guide for more information.

Events You can configure actions for events that cause the host to connect to panels. See the C•CURE 800/8000 Software Guide for more information.

State changes If a state change occurs for an object on the host and the panel needs the information, the host dials the panel immediately.

apC Dialup Overview


Dialing Into the Host

Panels dial the host and upload information under the following conditions:

Events. You can configure dialup options for various activities that cause the panel to dial the host when those activities occur. See the C•CURE 800/8000 Software Guide for more information.

The panel’s activity buffer is full. Panels dial the host and upload information when the panel’s activity buffer is close to being full.

apC Encryption

apC encryption is a feature that provides extra security for your system by encrypting messages sent between remote apCs and the server. Use apC encryption to prevent unauthorized personnel from viewing or changing messages. The C•CURE 800/8000 Diagnostics utility lets you set up apC encryption. The entry to edit is EncryptApcMsgs in the [Driver] section of the CCURE.INI file. For information, see the C•CURE 800/8000 Troubleshooting Guide.

apC Dialup Configuration Overview

Configuring dialup panels involves setting up the hardware and configuring the software components. See the apC/8X Installation and Configuration Guide and the apC/L Installation and Configuration Guide for instructions about setting up modems and panels. See the appropriate sections in this manual for instructions on performing the software configuration tasks listed in Table 10-1 on page 10-5.

NOTE The system tracks encrypted messages by counting the messages sent between the apC and the server. You receive an encryption failure message when the apC count does not match the server count. An encryption failure is a severe security breach.

After you determine the cause of the message, you can get out of encryption failure by taking the apC offline and placing the apC online again, or restarting the C•CURE 800/8000 driver.

apC Dialup Overview


Table 10-1: Configuration References

Stage Task See...

1 Configure COM and network ports to which host modems are attached.

See Chapter 8” for more information.

2 Configure host modems. See Chapter 9” for more information.

3 Configure dial-in, dial-out, and modem options for dialup panels.

See “Configuring apC Dialup Panels” on page 10-6 for more information.

4 Configure inputs, outputs, readers, and events. In this guide, see Chapter 6 for information about inputs and outputs, and Chapter 5 for information about readers. See the C•CURE 800/8000 Software Guide for information about configuring dialup options for events.

Configuring apC Dialup Panels



Use the apC/8X or apC/L dialog box to configure dialup panels.

To Configure Dialup Panels

1. From the C•CURE 800/8000 Administration application, select Hardware->apC from the menu bar. The apC Selection browser appears, as shown in Figure 10-2.

Figure 10-2: apC Selection Browser

2. Click New to configure a new apC/8X or apC/L. The apC dialog box opens, shown in Figure 10-3 on page 10-7.



Figure 10-3: apC Dialog Box

3. In the Identification box, specify information for configuring the panel. See “Configuring Panels” on page 4-5 for information.

4. In the General box, in the Connection Type list box, select Dialup. The Port box and Poll period boxes are no longer available, and the Dialup button in the Configure box become available, as shown in Figure 10-4 on page 10-8.



Figure 10-4: apC Dialog Box - Configure Dialup

5. Click the following buttons in the apC dialog box to complete the configuration for the dialup panel:

• Dialup to configure the Dialup panel. See “Configuring Options for apC Dial-up Panels” on page 10-10 for more information.

• Panel to configure readers, inputs, and outputs on the main panel. See “Configuring Readers” on page 5-2, “Configuring Inputs” on page 6-2, and “Configuring Outputs” on page 6-13 for more information.

• Add-on boards to configure readers, inputs, and outputs for add-on boards. See “Configuring Add-On Boards for apCs” on page 7-2 for more information. Also see the apC/8X Installation and Configuration Guide and the apC/L Installation and Configuration Guide.

• Events to configure panel events. See “Configuring Security Objects on Panels” on page 4-12 for more information.

• Intrusion to view the intrusion zones configured on the panel. See “Viewing the Intrusion Zones on Panels” on page 4-18 for more information.

– An apC/L and an apC/8x can each support up to 8 intrusion zones.



– An apC/L can support up to 2 intrusion zones.

See the C•CURE 800/8000 Software Configuration Guide for more information about intrusion zones.

6. Click OK to save the dialup panel configuration.

Configuring Options for apC Dial-up Panels



The Dialup Components dialog box lets you specify the following options for a dialup panel:

Dial-in

Dial-out

Periodic

Modem

To Configure Dialup Options for Dialup Panels

1. From the apC dialog box, click the Dialup button. The Dialup Components dialog box appears with the Dial In tab displayed, shown in Figure 10-5.

Figure 10-5: Dialup Components Dialog Box

There are four tabs labeled Dial In, Dial Out, Periodic, and Modem on the Dialup Components dialog box.

2. Click each tab as needed to complete the configuration of the dialup panel, as follows:



• Dial In tab to configure dial-in options for the dialup panel. See “Configuring Dial In Options for Dialup Panels” on page 10-11.

• Dial Out tab to configure dial-out options for the dialup panel. See “Configuring Dial Out Options for Host and Panels” on page 10-13 for more information.

• Periodic tab to configure intervals and time specifications for communications between host and dialup panel. See “Configuring Periodic Dial Out Options for Host and Panels” on page 10-15for more information.

• Modem tab to configure the modems that are attached to the dialup panel. See “Configuring Modem Options” on page 10-17 for more information.

Configuring Dial In Options for Dialup Panels

The Dial In tab lets you specify the host modems and phone numbers that this panel can call when dialing the host.

To Configure Dial In Options for Dialup Panels

1. From the Dialup Components dialog box, if the Dial In tab is not open already, click the Dial In tab. The Dial In tab opens, shown in Figure 10-6.

Figure 10-6: Dialup Components Dialog Box




Table 10-2: Dialup Components Dialog Box Fields


Host Modems which can be contacted by this panel

Host modems/Host phone numbers

Displays the host modems and phone numbers that this panel can call when attempting to contact the host.

The panel calls the host modems in the order that they are listed in this box. A modem/phone combination can be listed more than once; however, you cannot list more than 8 modem/phone combinations.

Number of times to retry failed connections

Enter the number of times the panel dials the list of telephone numbers when the panel cannot contact the host. For example, if you enter 2 in this field, the panel dials each telephone number in the list once. If a connection is not established at the first attempt, the panel dials the telephone numbers in the list again and then stops dialing.

Modify Click this button to edit the list of host modems and phone numbers. The apC Dial-In Components dialog box opens. See “Selecting Host Modems for Dial In” on page 9-10 for more information.



Configuring Dial Out Options for Host and Panels

The Dial Out tab lets you specify that configuration changes will cause the host to dial the panel and download the configuration changes within a specified time.

To Configure Dial Out Options for Hosts and Dialup Panels

1. From the Dialup Components dialog box, click the Dial Out tab. The Dial Out tab opens, shown in Figure 10-7.

Figure 10-7: Dial Out Tab




Table 10-3: Dial Out Tab Fields


Host modems which can contact this panel

Host modems/Remote phone numbers

Displays the host modems and remote phone numbers that the host can use to contact this panel. Click the Modify button to edit the list.

The host calls the modems in the order that they are listed in this box. A modem/phone combination can be listed more than once.

Automatically initiate connection when configuration changes after:

hh:mm

Click this check box to specify that configuration changes are automatically downloaded to the dialup panel within a specified time. Enter the maximum time that the host waits after a configuration change to download configuration changes to this dialup panel.

Enter the time in hh:mm format.

If the Automatically initiate connection when configuration changes after: check box is not selected, the hh:mm field is unavailable.

Changes that the panel does not need, such as changes to an object’s name or description, do not cause a download to the panel.

Number of times to retry failed connections:

Enter the number of times the host dials the list of telephone numbers when the host cannot contact the panel. For example, if you enter 2 in this field, the host dials each telephone number in the list once. If a connection cannot be established at the first attempt, the host dials the telephone numbers in the list again and then dials at the rate specified in the Redial Interval during communication failure field on the Periodic tab. See “Configuring Periodic Dial Out Options for Host and Panels” on page 10-15 for more information.

Security Password Enter a password up to 16 characters that is downloaded to this dialup panel. Use passwords to discourage unauthorized access to dialup panels.

Modify Opens the apC Dial Out Components dialog box where you edit the list of host modems and phone numbers that can call this panel. See “Selecting Host Modems for Dial Out” on page 9-13 for more information.



Configuring Periodic Dial Out Options for Host and Panels

The Periodic tab lets you specify how often within and outside a time specification, and during a communications failure that the host dials the panel to download configuration changes and cardholder information.

To Configure Periodic Options for Hosts and Dialup Panels

1. From the Dialup Components dialog box, click the Periodic tab. The Periodic tab opens, shown in Figure 10-8.

Figure 10-8: Periodic Tab




Table 10-4: Periodic Tab


Periodic dialup panel

Redial interval during communications failure:

hh:mm

Enter the interval of time the host waits to redial the panel when there is a communications failure. Enter the time in hh:mm format. The default is 30 minutes.

Time specification Enter a time specification for periodic dialing of the panel and downloading configuration changes and cardholder information. The default value is $Always.

NOTE: Do not use the “$Always” default time specification as it causes iSTAR to use time configured in the Dial interval during time specification for periodic dialing.

Use Dial interval during time specification to specify how often during this time specification the host dials the panel; use the Dial interval outside time specification to specify how often outside of this time specification the host dials the panel.

For example, if you specify a time specification called Week (Monday through Friday, 9 a.m. to 5 p.m.), and enter the following values:

Interval between dialing during time specification: 01:00

Interval between dialing outside time specification: 03:00

the host dials the panel every hour between the hours of 9 a.m. and 5 p.m., Monday through Friday; and every three hours 5 p.m. to 9 a.m. Monday through Friday, Saturday and Sunday.

Dial interval during time specification

hh:mm

Enter the frequency that the hosts dials the panel while the time specification is in effect. Enter the time in hh:mm format. The time can be from 0 to 99:59 hours. The default time is 1 hour.

Dial interval outside time specification

hh:mm

Enter the frequency that the host dials the panel while the time specification is not in effect. Enter the time in hh:mm format. The time can be from 0 to 99:59 hours. The default time is 4 hours.



Configuring Modem Options

The Modem tab lets you configure modems that are attached to the dialup panel.

To Configure Modems Attached to the Pane

1. From the Dialup Components dialog box, click the Modem tab. The Modem tab opens, shown in Figure 10-9.

Figure 10-9: Modems Tab

2. Provide the information the information shown in Table 10-5 on page 10-18 and click OK.

NOTE You should not need to change the default values in this dialog box.



Table 10-5: Modems Tab

Field Description

Modem initialization string Enter the string of characters that the panel uses to initialize the modem. See your modem’s documentation for information.

Modem response wait time:

seconds

Enter the time that the panel waits for a response from this modem after sending a message to the modem.

If the wait time expires without a response from the modem, the panel declares an error for the modem, logs a report, and continues to try to contact the modem. When the panel re-establishes communication with the modem, the modem is re-initialized.

Enter a time from one second to four minutes. The default value is ten seconds.

Connect to host wait time:

mm:ss

Enter the time that the panel waits for a response from the host after dialing the host.

If the wait time expires without a response from the host, the panel tries to contact the host using the next available host modem/phone number combination displayed in the Dial In dialog box. If the panel does not receive a response after trying the entire list of phone numbers the specified number of times, the panel declares an error for the host modem.

Enter a time from one second to four minutes using mm:ss format. The default value is one minute.

Redial/reconnect delay time:

seconds

Enter the time that the panel waits after losing a panel-initiated connection with the host before trying to recontact the host. Enter a time from one second to four minutes. The default value is eight seconds.

DTR off time:

milliseconds

Enter the time that the panel keeps DTR off when hanging up the modem. Enter a time from one to 9999 milliseconds. The default value is 1000 milliseconds, or one second.

Although you can enter a time from one to 9999 milliseconds, the panel rounds the DTR off time down to a multiple of 16 milliseconds.



Modem answer delay time:

milliseconds

Specify the time that the panel waits to answer a ring after getting a ring signal. Enter a time from one to 9999 milliseconds (about 90 seconds). The default value is 200 milliseconds.

Although you can enter a time from one to 9999 milliseconds, the panel rounds the Modem answer delay time down to a multiple of 16 milliseconds.

Modem status check time period:

mm:ss

Specify a time period at which the panel checks this modem when the modem is inactive. For example, if you enter 65 seconds, the panel contacts the modem every 65 seconds when the modem is inactive to verify that the modem is operating properly. Enter a time from one second to 59 minutes using mm:ss format. The default value is 65 seconds.

Table 10-5: Modems Tab, continued

Field Description


11

Configuring Dialup foriSTAR Pro Controllers

and Clusters

This chapter explains how to configure the iSTAR Pro/Classic clusters to work in dialup mode with C•CURE 800/8000. To install and configure hardware for iSTAR Pro/Classic controllers and clusters consult the iSTAR Pro Installation and Configuration Guide.

In this chapter

iSTAR Dialup Overview .............................................................................................. 11-2

Configuring iSTAR Clusters for Dialup .................................................................... 11-8

Configuring Dialup Options for iSTAR Clusters ................................................... 11-12

iSTAR Dialup Overview



Dialup iSTARs let you connect the C•CURE 800/8000 host to controllers at remote locations using modems and standard telephone lines.

The C•CURE 800/8000 host and iSTAR phone line/modem connection is based primarily on Windows standard telephony communications and Remote Access Service (RAS).

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 modem on the host.

The higher level of the communications, which deals with the transmission of C•CURE 800/8000 relevant data, is handled by Microsoft RAS. RAS treats dialup connections as if they were network connections. As a result, the C•CURE 800/8000 host views the connection established between the iStar and itself via phone line and modem as any other network connection.

How Dialup Controllers Work

As described above, the host and the iSTAR use a foundation of TAPI and RAS to support their connection. iSTAR controllers are organized into clusters as follows:

One controller designated as the Master provides the primary communications to the host for the cluster.

A backup communications path, the “secondary communications path,” is configured for the cluster to re-establish communications with the host if a communications failure occurs on the primary communications path.

The possible communications paths between the host and the iSTAR cluster are shown in the illustration in Figure 11-1 on page 11-3.



Figure 11-1: Communications Paths

In many cases, the primary communications are configured as network and the secondary communications are configured as dialup. When the Primary path is in a state of failure and the secondary path is dialup, the following occurs:

A user action on the host, such as updating a personnel record in the Administration application or activating an inactive output from the Monitoring Station, initiates a dial out process. The C•CURE 800/8000 driver generates an input file and subsequently launches a new program. The new program dials out to the iStar controller, transfers information provided by the input file to the controller, and then hangs up and closes down.

The controller dials back to the host using one of its host-provided phone numbers. In actuality, the controller dials the Windows RAS server, which may or may not be the C•CURE 800/8000 host. The Windows RAS server answers the call, assigns an IP address to the controller, and then provides a Windows socket connection to a C•CURE 800/8000 host listening socket as if it were a genuine network connection. The host knows that this connection is based on RAS because the IP address used

Master AlternateMaster

Primary - Network Secondary - Network

Primary SecondaryPrimary Secondary

Primary -Network Secondary - None Primary - Dialup Secondary - NonePrimary - Serial Secondary - None

Host

Master

Cluster Cluster

Host - Cluster with a Master

Host

Host - Cluster with a Master and Alternate Master

Communications Path Options Communications Path Options



by the controller is different from the real IP address assigned to the controller by the host configuration on the General tab of the Controller dialog box in the C•CURE 800/8000 Administration application.

Figure 11-2 shows a typical host/dialup cluster/controller configuration.

Figure 11-2: Typical Host/Dialup Cluster/Controller Configuration

Unlike direct network (Ethernet) and serial direct controllers that are always linked to the host, dialup controllers are connected to the host only on demand.

Either the host or controller can establish a telephone connection. The following sections describe the conditions that cause the host to dial a controller, and a controller to dial the host.



Dialing Out to Controllers

The host dials a controller and downloads information under the following conditions:

Dial Out: The C•CURE 800/8000 provides one dialout configuration that you can use to specify when the host dials controllers. Dial Out is used to specify that configuration changes are automatically downloaded to controllers within a specified time. See “Configuring Dial Out Options for Host and Controller” on page 11-15 for more information.

Manual actions at the Monitoring Station: Users at the Monitoring Station can connect the host to dialup controllers using the Connect manual action on the Controllers dialog box. See the C•CURE 800/8000 Monitoring Station Guide for more information.

Events: You can configure actions for events that cause the host to connect to controllers. See the C•CURE 800/8000 Software Configuration Guide for more information.

State changes: If a state change occurs for an object on the host and the controller needs the information, the host dials the controller immediately.

Dialing Into the Host

Controllers dial the host and upload information under the following conditions:

Periodic: The C•CURE 800/8000 provides one dial in configuration that you can use to specify when controllers dial the host. Use Periodic to specify that a controller periodically uploads activity to the host and receives downloaded configuration changes and cardholder information from the host at that time. See “Configuring Dial Out Options for Host and Controller” on page 11-15 for more information.

Events:. You can configure dialup options for various activities that cause a controller to dial the host when those activities occur. See the C•CURE 800/8000 Software Configuration Guide for more information.

The controller’s activity buffer is nearly full:. A Controller dials the host and uploads information when the controller’s activity buffer is close to being full.



Encryption

When an iSTAR connects to the host by dialup, you can still use the network encryption feature that provides extra security for your system. Use encryption to prevent unauthorized personnel from viewing or changing messages.

iSTAR Pro Dialup Configuration Overview

Configuring dialup for the iSTAR Pro involves setting up the hardware and configuring the software components. See the iSTAR Pro Installation and Configuration Guide for instructions on setting up modems and controllers and configuring controllers for cluster communications. See the appropriate sections in this manual for instructions on performing the software configuration tasks listed in Table 11-1:


Stage Task See...

1 Install and set up controller modems. See the iSTAR Pro Installation and Configuration Guide for more information.

2 If dialup is set up as the primary communication path....

Use the iSTAR Configuration Utility to configure the Windows user account that enables iSTAR dialup using RAS. This step configures the controller to talk to the host.

Use the System Variables dialog box within C•CURE 800/8000 to configure the Windows user account that enables iSTAR dialup using RAS.This step configures the host to talk to the controller.

See the iSTAR Pro Installation and Configuration Guide for more information.

See the C•CURE 800/8000 System Maintenance Guide.

If dialup is set up as the secondary communications path....

Use the System Variables dialog box within C•CURE 800/8000 to configure the Windows user account that enables iSTAR dialup using RAS.

See the C•CURE 800/8000 System Maintenance Guide for more information.

3 Configure COM ports to which host modems are attached.

See Chapter 8,” for more information.



4 Configure host modems. See “Configuring Host Modems” on page 9-3 for more information.

5 Configure dial-in, dial-out, and periodic options for dialup controllers.

See “Configuring iSTAR Clusters for Dialup” on page 11-8 for more information.

7 Configure inputs, outputs, readers, and events. In this guide, see Chapter 6, for information about inputs and outputs, and Chapter 5 for information about readers. See the C•CURE 800/8000 Software Configuration Guide for information about configuring dialup options for events.

Table 11-1: Software Configuration Tasks, continued

Stage Task See...

Configuring iSTAR Clusters for Dialup



Use the Cluster dialog box to configure iSTAR dialup.

To Configure a Dialup Cluster

1. From the C•CURE 800/8000 Administration application, choose Hardware:iSTAR Cluster from the menu bar. The iSTAR Cluster Selection browser appears, shown in Figure 11-3.


2. Click New to create a new cluster. The Cluster dialog box appears, shown in Figure 11-4 on page 11-9.




3. In the Identification box, specify information for configuring the cluster and on the General tab assign controllers to the cluster. See “Configuring Clusters for iSTAR Classic & iSTAR Pro” on page 1-42 for information.

4. Click the Primary tab to configure a primary communications path for the cluster.

- or -

Click the Secondary tab to configure a secondary communications path for the cluster.

Depending on the tab you chose, either the Primary tab or the Secondary tab opens, as shown in Figure 11-5 on page 11-10.



Figure 11-5: Controller Having Primary/Secondary Communications with Host .

5. In the Controller having primary communications with host field and in the Controller having secondary communications with host field on the respective tabs, specify information for configuring the cluster. See “Configuring the Primary Communications Path” on page 1-47 and “Configuring the Secondary Communications Path” on page 1-51 for information.

6. In the Method of communication between host and controller field select Dialup. The following changes occur on the tabs:

• Configure Dialup button becomes available.

• The following become unavailable:

– Controller attempts to connect to host every xxxx seconds field

– Controller declares connection failure after xx failed attempts field

– After connection failure, controller attempts to reconnect every xxxx seconds field



– While connected, declare connection failure if no message for xx seconds drop-down box

• Controller activates this event while in connection failure field becomes available.

7. In the Host activates this event while in connection failure field on the Primary tab and in the Controller activates this event while in connection failure field on both the Primary and Secondary tabs, enter an optional event that activates when a communications failure occurs between the host and the master. Double-click on the box to display a selection browser for events. See page 1-47 for more information about configuring the primary communications path and page 1-51 for more information about configuring the secondary communications path.

8. Click the following on the Cluster dialog box to complete the configuration for the dialup cluster:

• Dialup button on the Primary or Secondary tab to configure the Dialup controller. See “Configuring Dialup Options for iSTAR Clusters” on page 11-12 for more information.

• Cluster tab to configure communications among cluster members and the master. See “Configuring Communications with the Master” on page 1-55.

• Misc tab to configure the test for the secondary communications path. See “Configuring the Secondary Communications Test” on page 1-58.

• Global APB tab to configure antipassback for the cluster. See “Configuring Antipassback for the Cluster” on page 1-60.

9. Click OK to save the dialup cluster configuration.

NOTE These procedures do not assume that you are configuring dialup for both primary and secondary communications paths—which is not permitted. The procedures merely illustrate that you configure dialup similarly for both primary and secondary paths.

Configuring Dialup Options for iSTAR Clusters



The iSTAR Dialup Configuration dialog box lets you specify the following options for a dialup cluster:

Dial in

Dial out

Periodic

To Configure Dialup Options for Dialup Clusters

1. From the Primary or Secondary tab on the Cluster dialog box, click the Configure Dialup button. The Dialup Configuration dialog box appears with the Dial In tab displayed, shown in Figure 11-6.

Figure 11-6: Dialup Configuration Dialog Box

There are three tabs labeled Dial In, Dial Out, and Periodic on the Dialup Configuration dialog box.

2. Click each tab as needed to complete the configuration of the dialup controller.



• Dial In tab to configure dial-in options for the dialup controller. See “Configuring Dial In Options for Dialup Controllers” on page 11-13.

• Dial Out tab to configure dial-out options for the dialup controller. See “Configuring Dial Out Options for Host and Controller” on page 11-15 for more information.

• Periodic tab to configure intervals and time specifications for communications between dialup controller and host. See “Configuring Periodic Dial In Options for Controller and Host” on page 11-17 for more information.

Configuring Dial In Options for Dialup Controllers

The Dial In tab lets you specify the host modems and phone numbers that this controller can call when dialing the host.

To Configure Dial In Options for Dialup Controllers

1. From the Dialup Configuration dialog box, if the Dial In tab is not open already, click the Dial In tab. The Dial In tab opens, shown in Figure 11-7.

Figure 11-7: Dial In Tab




Table 11-2: Dial In Tab Fields


Host Modems which can be contacted by this panel

Host modems/Host phone numbers

Displays the host modems and phone numbers that this controller can call when attempting to contact the host.

The controller calls the host modems in the order that they are listed in this box. A modem/phone combination can be listed more than once; however, you cannot list more than 8 modem/phone combinations.

Number of times to retry failed connections

Enter the number of times the controller dials the list of telephone numbers when the controller cannot contact the host. For example, if you enter 3 in this field, the controller dials each telephone number in the list 3 times. If a connection is not established at the first attempt, the controller dials the first telephone number again; if a connection is still not established, the controller dials the telephone number a third time and if that attempt fails, the controller moves to the next telephone number in the list for the number of configured retry attempts. If the requisite connection attempts with all the phone numbers in the list fail, the controller stops dialing—“goes to sleep.”

The controller continues its dial-in attempts after the interval specified in the Redial interval during communications failure: hh:mm field on the Periodic tab.The number of retries for each dial-in iteration is that specified in this field. See “Configuring Periodic Dial In Options for Controller and Host” on page 11-17 for more information.

The number that you enter in this field also sets the number of attempts that the host makes to dial out to the controller, after the length of time set on the Dial Out tab, as a result of the following:

Manual actions at the Monitoring Station

Actions configured for events

State changes

Button

Modify Click this button to edit the list of host modems and phone numbers. The Controller Dial-In Components dialog box opens. See “Selecting Host Modems for Dial In” on page 9-10 for more information.



Configuring Dial Out Options for Host and Controller

The Dial Out tab lets you specify that configuration changes cause the host to dial the controller and download the configuration changes within a specified time.

To Configure Dial Out Options for Hosts and Dialup Controllers

1. From the Dialup Configuration dialog box, click the Dial Out tab. The Dial Out tab opens, shown in Figure 11-8.

Figure 11-8: Dial Out Tab




Table 11-3: Dial Out Tab Fields


Host modems which can contact this panel

Host modems/Remote phone numbers

Displays the host modems and remote phone numbers that the host can use to contact this controller. Click the Modify button to edit the list.

The host calls the modems in the order that they are listed in this box. A modem/phone combination can be listed more than once, but you cannot enter more than 4 modem/phone combinations.

Automatically initiate connection when configuration changes after:

hh:mm

Click this check box to specify that configuration changes made to C•CURE 800/8000 from the Administration application are automatically downloaded to the dialup controller within a specified time.

Example:

Cardholder additions and deletions

Enter the maximum time that the host waits after a configuration change to download configuration changes to this dialup controller.

Enter the time in hh:mm format.

If the Automatically initiate connection when configuration changes after: check box is not selected, the hh:mm field is unavailable.

Changes that the controller does not need, such as changes to an object’s name or description, do not cause a download to the controller.

Modify Opens the Controller Dial Out Components dialog box where you edit the list of host modems and phone numbers that can call this controller. See “Selecting Host Modems for Dial Out” on page 9-13 for more information.



Configuring Periodic Dial In Options for Controller and Host

The Periodic dialog box lets you specify how often within and outside a time specification and during a communications failure that controllers dial the host to upload activity and to allow the host to download configuration changes and cardholder information.

To Configure Periodic Options for Dialup Controllers and Hosts

1. From the Dialup Configuration dialog box, click the Periodic tab. The Periodic tab opens, shown in Figure 11-9.

Figure 11-9: Periodic Tab




Table 11-4: Periodic Tab Fields


Periodic dial Redial interval during communications failure:

hh:mm

Enter the interval of time the controller waits to redial the host when there is a communications failure. Enter the time in hh:mm format. The default is 30 minutes.

NOTE: The number that you enter in this field sets the length of time that the controller’s dialing process “goes to sleep” after attempting to reconnect to the host the number of times configured on the Dial In tab before beginning another cycle of connection attempts. See “Configuring Dial In Options for Dialup Controllers” on page 11-13 for more information.

Time specification Enter a time specification for periodic dialing of the host and uploading activity from the controller to the host and downloading configuration changes and cardholder information from the host. The default value is $Always.

Use Dial interval during time specification to specify how often during this time specification the controller dials the host; use the Dial interval outside time specification to specify how often outside of this time specification the controller dials the host.

Example:

If you specify a time specification called Week (Monday through Friday, 9 a.m. to 5 p.m.) and enter the following values,

Interval between dialing during time specification: 01:00

Interval between dialing outside time specification: 03:00

the controller dials the host every hour between the hours of 9 a.m. and 5 p.m., Monday through Friday; and every three hours 5 p.m. to 9 a.m. Monday through Friday, Saturday and Sunday.

Dial interval during time specification

hh:mm

Enter the frequency that the controller dials the host while the time specification is in effect. Enter the time in hh:mm format. The time can be from 0 to 99:59 hours. The default time is 1 hour.

Dial interval outside time specification

hh:mm

Enter the frequency that the controller dials the host while the time specification is not in effect. Enter the time in hh:mm format. The time can be from 0 to 99:59 hours. The default time is 4 hours.

C•CURE 800/8000 Hardware Configuration Guide A–1

A

Card Formats Primer

The C•CURE 800/8000 lets you set up magnetic, Wiegand, proximity, and encrypted magnetic card formats. You can define three card formats per reader. This appendix briefly describes magnetic, Wiegand, proximity cards, encrypted magnetic, and offset values for card numbers. If you are uncertain about the card format your facility uses, consult your dealer representative.

In this appendix

Card Formats .................................................................................................................. A-2

Magnetic Cards............................................................................................................... A-5

Wiegand Cards ............................................................................................................... A-6

Proximity Cards ............................................................................................................. A-7

Encrypted Magnetic Cards ........................................................................................... A-8

Offset Values for Card Numbers ................................................................................. A-9

A–2 C•CURE 800/8000 Hardware Configuration Guide

Card Formats

When a person presents an access card at a reader, the reader passes the information encoded in it to the apC. This information is generally a string of numbers. Various portions of this string may have specific purposes, which the apC can check while determining if the cardholder should be granted or denied access. For the apC to interpret the numerical string, you must define a card format.

Card Format Fields

The possible fields within the card format are described in Table A-1.

Table A-1: Card Format Fields

Field Description

Facility/company code

Data field that should contain identification unique to the company.

Site code Field that identifies the issuing site--for companies that issue cards from several locations.

Card number Field that contains the identification number, unique to each person using the system, for cards with the same facility and/or site code.

This number is associated with a particular personnel record in the system.

Issue code Number indicating how many times a card with this card number has been issued. When the card is replaced (original is lost or damaged), you must increment this number. The panel supports issue codes from 0 to 7.

The number on the card must match the issue code in the person’s record.

Fixed data Field within the encoded information that remains the same for all cards used with the particular card format. Similar to facility and site codes.

Parity Field providing a way to check whether the card read operation was correct.

Parity bits are included in Wiegand and proximity access cards.

Parity can be even or odd. It can be calculated for the entire length of the card, or for a part of it.

Card Formats


When you define a card format, you must include these fields:

Card number

Card length

Card type

The other field types provide additional information for the system to check before granting access, but they are not required.

LRC Longitudinal Redundancy Check. This field is for informational purposes only.

Expiration date Field providing a way for a card reader to check whether or not a card is still valid through an expiration date encoded in the card. Once this card format is applied to a given reader, a cardholder whose card has an unexpired date is allowed access at the door. If, on the other hand, the cardholder presents a card with an expired date to the reader, the door stays locked, denying the cardholder access.

If the expiration date encoded on the card is the present date, the panel expires the card at the beginning of the following day.

If the expiration date/time configured in the cardholder’s personnel record precedes the encoded expiration date, the panel expires the card at that date/time.

Table A-1: Card Format Fields, continued

Field Description


Sample Card Format for Mag14

Figure A-1: Sample Card Format for Mag14

Table A-2: Card Format for Mag14

Field Starting Position Length Data in Field

Facility Code 2 3 019

Site Code 5 2 01

Card Number 7 6

Issue Code 13 1

B 0 1 9 O 1 1 2 3 4 5 6 O F

FacilityCode

SiteCode

CardNumber

IssueCode

Mag14 Card Format

Card type = Magnetic

Total card length= 14

Magnetic Cards


Magnetic Cards

Magnetic cards have tracks inside a magnetic strip. These tracks contain encoded information, such as an internal card number, that the apC interprets. A user swipes this kind of card through a card reader. The encoded information on a magnetic card may include:

Facility or company code

Issue code

Site code

Card number

Expiration date

Fourteen and 25-digit (one half byte) magnetic cards are common.


Wiegand Cards

Wiegand cards contain encoded information in an internal format that resembles a bar code. A sensing coil inside a Wiegand reader creates a magnetic field so that when the wires inside the card interact with the reader’s magnetic field, they create low voltage impulses in the sensing coil.

Depending on the arrangement of wires in the card, the voltage is either positive or negative. The read head and small circuit board inside the card reader (called a personality board) translate the card’s voltages and transmit the information to the apC.

Some Wiegand cards have an external or emboss number that maps to an internal number. The security manifest you receive with your cards matches a card’s emboss number with its internal number and also provides information about card format. The encoded information on a Wiegand card can include:

Parity information

Facility or company code

Card number

Twenty-six, 36-bit, and 37-bit Wiegand cards are common.

NOTE Wiegand cards can use a variety of different formats. If you are uncertain about what data is encoded in your cards, contact your dealer representative.

Proximity Cards


Proximity Cards

Proximity cards contain an antenna and an IC chip containing stored information. Usually the cards contain the same type of cardholder information as Wiegand cards. Readers and cards are available in a number of frequencies and technologies. Some readers are able to read several different types of cards, while others are limited to a single format.

The most common proximity cards are “passive”; the radio frequency field generated by the card reader energizes the card and allows the IC chip to transmit its data. Most readers require the card to be placed within a few inches of the read head. A few types of “long range” readers have effective ranges out to several feet.

The obvious advantage of the proximity card is that it may remain in a pocket or handbag, hang from a belt, or even be attached to a vehicle and still be effective.

Most modern proximity readers use a Wiegand-style output, with Wiegand 36 and 37 being the most popular. C•CURE 800/8000 users, however, should select the Proximity technology when configuring proximity card formats.


Encrypted Magnetic Cards

These cards are generated using the ELCOM encoder with the Software House algorithm.

Offset Values for Card Numbers


Offset Values for Card Numbers

When you are configuring a card format, you may use offset values to create a card number composed of two or more fields in the card format. This card number is calculated by the apC and is compared to the Card Number specified in the Personnel record. You can specify a offset value for facility code fields, site code fields, and card number fields.

The system uses only those fields with non-zero offset values and the card number field (regardless of offset value) when calculating the card number.

Use the following formula to calculate the card number when offset values are being used.

card_no = facility_code_field x 10 offset_value_facility ORsite_code_field x 10 offset_value_site + card_no_field

It is possible to specify more than one card number field in the card format and apply a different offset value to each of these fields.

For magnetic cards, calculate the card number as follows:

card_no = facility_code_field x 10 offset_value_facility ORsite_code_field x 10 offset_value_site OR card_no_field1 x 10 offset_value_card_no_field1 ORcard_no_field2 x 10 offset_value_card_no_field2 OR ... +card_no_fieldn

For Wiegand/proximity cards, calculate the card number as follows:

card_no = facility_code_field x 10 offset_value_facility ORsite_code_field x 10 offset_value_site OR card_no_field1 x 2offset_value_card_no_field1 ORcard_no_field2 x 2 offset_value_card_no_field2 OR ... +card_no_fieldn

Table A-3 and Table A-4 on page A-10 list allowable offset values for the facility/site code and card number fields.

NOTE The ‘OR’ indicates a binary ‘OR.’


Offset Example

The example in Table A-4 shows how to calculate offset values for a Magnetic 14 card when a facility code of 12 and a card number of 678 is encoded on the card.

Table A-3: Allowable Offset Values

Field Card Type Range

Facility/site code All 3 to 9

Card numbers Magnetic 3 to 9

Card number Wiegand/proximity 2 to 32

NOTE The largest composite card number calculated cannot be greater than 42967295

Table A-4: Calculation of Offset Values

If Facility Code Offset Value Is... Use This Formula...

To Get Logical Card Number...

3 (12 x 103) + 67812000 + 678

12678

4 (12 x 104) + 678120000 + 678

120678

5 (12 x 105) + 6781200000 + 678

1200678

6 (12 x 106) + 67812000000 + 678

12000678

NOTE The calculated card number must be less than 31 bits.

Index

C•CURE 800/8000 Hardware Configuration Guide Index–1

Index

A

AC power fail input on GCM, defined 1-21, 2-19AC power fail input, defined 3-20AC power failure inputs 6-18ACM

configuringfirst ACM on GCM 1-25inputs/outputs on first, second ACM

1-25readers, add-on boards on first, second

ACM 1-26second ACM on GCM 1-25

connecting optional boards to 1-5defined 1-2specifying type See ACM8, ACM8W 1-27specifying type. See ACM8, ACM8W 1-26

ACM8about 1-3selecting 1-26

ACM8Wabout 1-3capabilities 1-4selecting 1-26

Activatingevents

comm failure on panel 4-14when panel is full 4-15when panel is nearly full 4-15

inputon supervision error 6-6

ADA. See Alternate shunt (ADA).Add-on boards

configuring 4-10, 7-2configuring on first, second ACM 1-26I/32 system input board 7-5I8 - input module 7-17maximum number per panel type 7-2mini-star 7-14overviewproximity 7-15R/48 output module 7-10R8 - output module 7-19star coupler 7-12Wiegand 7-15

Add-on Boards dialog box 7-2Address

panels 4-8See also advanced processing Controller

(apC), apC/L, or apC/8XAdvanced tab, Modem dialog box 9-8Advanced options

for host modems 9-8for panel modems 10-15, 10-17, 11-17

advanced processing Controller (apC)configuring 4-5 to 4-11

add-on boards 7-2 to 7-16inputs 6-2outputs 6-13

dialup 10-6, 10-19, 11-8on network ports 8-6

event to activate

Index

Index–2 C•CURE 800/8000 Hardware Configuration Guide

on communications failure 4-15when panel full 4-15when panel nearly full 4-15

main panel layout 4-12, 6-13 to 6-17on network ports 8-6overview 4-2panel communication failure delay time 4-9poll period during comm failure 4-9poll timeout delay time 4-9reader LCD messages 4-8readers per 5-2supervised input conditions 4-2time zone 4-7unsupervised input conditions 4-3

Advanced reader configuration dialog box 5-10, 5-13

Alarm device states 4-2Alternate master controller 1-52, 2-45, 3-48Alternate shunt (ADA)

door relay 6-14Americans with Disabilities Act. See Alternate

shunt (ADA).Antipassback

dialing panels 10-3See also Global Antipassback Control by

Clusterstatus 1-10, 2-9, 3-10

apC Advanced dial dialog box 10-15, 10-17, 11-17apC Dial-In Components dialog box, second

9-10apC dialog box 4-5, 4-6, 10-6apC dialog box for dialup 10-6apC Dial-Out Components dialog box 9-13apC Dial-out Components dialog box 10-13,

11-15apC encryption 10-4apC Events dialog box 4-14apC Panel Layout dialog box 4-12, 6-18apC Type 4-7apC/8X

10-19configuring 4-5 to 4-11

add-on boards 7-2 to 7-16inputs 6-2outputs 6-13

dialup 10-6, 11-8on network ports 8-6

event to activateon communications failure 4-15when panel full 4-15when panel nearly full 4-15

FlashRom 4-2main panel layout 4-12, 6-13 to 6-17on network ports 8-6panel communication failure delay time 4-9poll period 4-8

during communications failure 4-9poll timeout delay time 4-9reader LCD messages 4-8readers per 5-2supervised input conditions 4-2time zone 4-7unsupervised input conditions 4-3

apC/8X dialog box 4-5, 10-6apC/8X Events dialog box 4-14apC/8X Panel Layout dialog box 4-12apC/L

configuring 4-5 to 4-11add-on boards 7-2 to 7-16inputs 6-2outputs 6-13

Index


dialup 10-6, 10-19, 11-8on network ports 8-6

event to activateon communications failure 4-15when panel full 4-15when panel nearly full 4-15

main panel layout 4-12, 6-13 to 6-17on network ports 8-6panel communication

failure delay time 4-9poll period 4-8

during communications failure 4-9poll timeout delay time 4-9reader LCD messages 4-8readers per 5-2supervised input conditions 4-2time zone 4-7unsupervised input conditions 4-3

apC/L dialog box 4-5, 4-6, 10-6apC/L Events dialog box 4-14apC/L FlashRom 4-2apC/L Panel Layout dialog box 4-12Arming an input 6-5Automatic dial out, host dialing panel 10-13,

11-15Automatic dialout 10-3Automatically download panels 10-14, 11-16

B

Boardsadd-on 7-2 to 7-16connecting optional to ACM 1-5connecting optional to iSTAR Edge 3-6connecting optional to PMB 2-5optional 4-3

C

C•CURE SystemapC, apC/8X, apC/L 4-2

C•CURE System Administration Applicationconfiguring connection verification

messages 2-31, 3-34configuring secondary communications path

1-36, 2-32, 3-35using to set up primary communications

path 1-34, 2-29, 3-32Card Format dialog box 5-26Card formats

card number A-2company code A-2configuring 5-4, 5-25, 5-31encrypted magnetic A-8expiration date A-3facility code A-2fields

to define 5-30, A-3within a card A-2

fixed data A-2issue code A-2Longitudinal Redundancy Check (LRC) A-3magnetic 5-26, A-5offset value A-9parity 5-30, A-2site code A-2Wiegand A-6

Card number A-2entry, configuring a reader keypad for 5-8

Card readerscard formats for 5-4configuring 1-28, 5-2, 5-14configuring on first, second ACM 1-26connecting to ACM 1-5connecting to GCM 2-5connecting to main board 3-5

Index


defined 4-3deleting 5-2dialup setting 5-14keypad PIN options 5-7messages.See RM LCD Messagesoutputs attached to 5-5personality board A-6reader technology 5-4supervised inputs on 5-5types of 5-5types of ACM configurations 1-3

Cardholderanti-passback status 1-10, 2-9, 3-10information and C•CURE System host 1-34,

2-30, 3-33Caution symbol xviiCluster

about 1-5, 2-6, 3-7adding, moving, removing controllers 1-45,

1-46, 2-38, 2-39, 3-41, 3-42antipassback control in 1-10, 2-9, 3-10configuring

communications among cluster members and master 1-55, 2-48, 3-51, 11-11

communications test for secondary communications path 1-46, 2-39, 3-42

encryption 2-39, 3-42iSTAR Global Antipassback 1-46, 2-39,

3-42primary communications path 1-46,

1-47, 2-39, 2-40, 3-42, 3-43Secondary Communications Path 1-51,

2-44, 3-47secondary communications path 1-46,

2-39, 3-42control of activities distributed to 1-9, 2-9,

3-10designating master controller for 1-48, 1-52,

2-41, 3-44

displayinglist of controllers assigned to 1-46, 2-39,

3-42list of controllers to add to 1-45, 2-38,

3-41displaying cluster that controller is assigned

to 1-15, 2-14, 3-15events in 1-9, 2-9, 3-10maintaining communications 1-37, 2-33, 3-36members. See cluster members 1-6, 2-6, 3-7naming 1-45, 2-38, 3-41putting online 1-45, 2-38, 3-41selecting, editing, creating controllers 1-45,

2-38, 3-41specifying type of master/host

communication connection 1-52, 2-45, 3-48

system activity 1-10, 2-9, 3-10Cluster dialog box

configuring clusters with 1-42, 2-35, 3-38Cluster members

about 1-6, 2-6, 3-7configuring

communications between master and 1-46, 2-39, 3-42

connections with Alternate Master and 1-39, 2-33, 3-36

distributed cluster management and 1-8, 2-8, 3-9

information downloaded from host 1-34, 2-30, 3-33

primary communications path and 1-7, 2-7, 3-8

using C•CURE Administration Application to configure 1-34, 2-29, 3-32

COM portsconfiguring from Windows XP 8-3event to activate on comm failure 8-12naming 8-11See also ports

Index


Comm failure, event to activatefor panels 4-14for ports 8-12

Communicationsmaintaining 1-37, 2-33, 3-36used by master to connect with host over

ethernet 1-48, 2-41, 3-44Communications failure

activities attempted in response to 1-50, 2-42, 3-46

Communications failure delay timefor panels 4-9

Communications failure input, configuring 1-32Communications paths

clusters 3-3clusters and 1-2, 2-3secondary. See secondary communications

pathCommunications Port dialog box 8-8, 8-9Company code A-2Configuration

information and C•CURE System Host 1-34, 2-30, 3-33

Configuration Utilityauto-response mode 1-49, 1-50, 1-53, 1-54,

1-56, 1-57, 2-41, 2-42, 2-46, 2-47, 2-49, 2-50, 3-45, 3-46, 3-49, 3-50, 3-52, 3-53

configuring cluster master 1-11, 2-10, 3-11configuring

AC power failure inputs on panels 6-18apC, apC/8X, apC/L

dialup 10-6, 10-18card formats 5-31COM ports

from CCURE System 8-8from Windows XP 8-3

connection verification messages 1-35, 2-31, 3-34

controller, list of tasks 1-11, 2-10, 3-11

dialup panels 10-4, 11-6events for apCs, apC/Ls, and apC/8Xs 4-14holiday lists

apCs 4-16in Distributed Holidays mode 1-14, 1-16,

1-19, 2-13, 2-15, 2-17, 3-14, 3-16, 3-18, 4-6, 4-10, 4-16

iSTAR Edge controllers 3-18iSTAR eXs 2-17iSTAR Pro/Classics 1-19

host modems 9-3advanced options 9-8

I/32 system input board 7-5I8 - input module 7-5inputs 6-2master using iSTAR Configuration Utility

1-34, 2-30, 3-33network ports 8-6outputs 6-13panel modems, advanced options 10-15,

10-17, 11-17ports 8-8 to 8-13primary communications path 1-34, 2-29,

3-32R/48 System output board 7-10R8 - output module 7-19reader keypad PIN options 5-6RM LCD messages 5-15secondary communications path 1-36, 2-32,

3-35Secondary Communications Path for cluster

1-51, 2-44, 3-47security objects on panels 4-12supervised inputs 6-2tamper inputs on panels 6-18

Connect to host wait time 9-9, 10-18Connection type for panel 4-7Connection verification messages

master controller and host maintain their communication connection with

Index


1-49, 2-41, 3-45specifying interval before communications

failure for secondary communications path declared 1-54, 2-47, 3-50

used by controller and master to maintain connection 1-56, 2-49, 3-52

used by master controller and host to maintain connection. See Secondary communications path 1-53, 2-46, 3-49

Connectionsconfiguring verification messages 1-35, 2-31,

3-34GCM 1-2losing with host 1-37, 2-33, 3-36types of 1-7, 2-7, 3-8verifying with keep-alive messages 1-35,

2-31, 3-34Controller 1-25, 1-51, 2-25, 2-44, 3-47

configurationfirst/second ACM 1-25task list 1-11, 2-10, 3-11

configuringa cluster 1-42, 2-35, 3-38cluster, designating master controller for

1-48, 1-52, 2-41, 3-44cluster, specifying type of master/host

communication connection 1-52, 2-45, 3-48

connection used by master to communicate with host 1-48, 2-41, 3-44

defining inputs on GCM 1-21, 2-19, 3-20defining output on GCM, RM LCD

messages 1-21, 2-19defining output on iSTAR Edge, RM

LCD messages 3-20event activated by controller if

communications failure occurs on secondary path 1-54, 2-47, 3-50

event activated by host if

communications failure occurs with master 1-50, 2-43, 3-46

event activated by master if communications failure occurs with host 1-50, 2-42, 3-46

Hardware MAC address 1-16, 2-15, 3-16Inputs

default input definition 1-29interval before controller is declared in

communications failure 1-57, 2-50, 3-53

interval between attempts to connect to host on secondary communications path 1-53, 2-46, 3-49

interval between attempts to connect to master 1-56, 2-49, 3-52

interval between attempts to re-connect to master after communications failure 1-56, 2-49, 3-52

interval controller, host wait before declaring failure on secondary communications path 1-54, 2-47, 3-50

IP address 1-16, 2-15, 3-16Main Board 1-21, 2-19, 2-20, 3-20, 3-23maximum unacknowledged messages

1-59, 2-52, 3-55name of communications failure event

1-17, 2-16, 3-17naming 1-14, 2-13, 3-14number of attempts to connect to host on

secondary communications path 1-53, 2-46, 3-49

number of attempts to connect to master before declaring communications failure 1-56, 2-49, 3-52

online and offline behaviors 1-14, 2-13, 3-14

overview of 1-11, 2-10, 3-11R/8 - Output Module, adding 1-31R/8 - Output module, default output

definition 1-31

Index


R/8 - Output Module, Tamper input 1-32

responsibility for communications with host when primary path failure occurs 1-52, 2-45, 3-48

time zone 1-15, 2-14, 3-15creating new 1-12, 1-43, 2-11, 3-12deleting 1-15, 2-14, 3-15displaying

list of controllers assigned to cluster 1-46, 2-39, 3-42

displaying cluster master/member status 1-15, 2-14, 3-15

displaying cluster name 1-15, 2-14, 3-15editing configuration 1-12, 1-43, 2-11, 3-12halting access control decisions 1-15, 2-14,

3-15I/8 - Input Module, described 1-28specifying alternate master 1-52, 2-45, 3-48specifying number of connection attempts

made to master before controller communication failure declared 1-56, 2-49, 3-52

Controller dialog box 1-12, 1-21, 2-11, 2-20, 3-12, 3-23

ACMdefining security objects connected to

1-25ACM tabs

ACM Inputs/Outputs, configuring 1-25ACMs, configuring 1-25defining security objects 1-25, 2-25Main Board tab

defining inputs on GCM 1-21, 2-19, 3-20Mod A tabs

Mod A Inputs/Outputs, configuring 2-25

R/8 - Output Modules, adding to a controller 1-31

Conventions, documentation xvii

D

Danger symbol xviiDefault output definition, configuring R/8 -

Output module using configuration values from 1-31

Dial-in options 9-12, 10-11, 11-13for dialup panels 10-11, 11-13selecting host modems 9-10

Dialing into host, events 10-4, 11-5Dialing out to panels

events 10-3, 11-5manual actions 10-3, 11-5periodic and automatic 10-3

Dial-out options 9-15, 10-13, 11-15selecting host modems 9-13

Dialup connectionsiSTAR system features 1-2

Dialup optionsfor dialup panels 10-10, 11-12

Dialup panelsconfiguring 10-6, 10-18configuring host modems 9-3dial-in options 10-11, 11-13dial-out options 10-13, 10-15, 11-15, 11-17dialup options 10-10, 11-12I8 input module

communications failure 7-18tampers 7-18

input activations 6-9inputs

during, outside time specs 6-10on network ports 8-6overview 10-2, 11-2R8 output module

communications failure 7-20

Index


tampers 7-20readers

communications failures 5-14tampers 5-14

supported features 10-3Distributed management

about cluster 1-9, 2-8, 3-9Documentation, conventions xviiDoor Switch Monitor (DSM) input 6-5Download wait period 10-14, 11-16Downloading

apC Flash ROM 4-2event activations 10-2

DTR off time 9-9, 10-18

E

Edit input, output, reader 3-28Encrypted magnetic card format A-8Encryption on panels 10-4Enter new phone number dialog box 9-6Entry by card number, configuring 5-8Ethernet

cluster members and 1-6, 2-6, 3-7master controller communicates with host

via TCP/IP over 1-48, 1-52, 2-41, 2-45, 3-44, 3-48

Eventsactivate

during com failure on panel 4-14when panel full 4-14when panel nearly full 4-14

activated by controller master if communications failure occurs with host 1-50, 2-42, 3-46

activated by controller when test of secondary communications path fails 1-59, 2-52, 3-55

activated by host if communications failure

occurs on secondary path 1-54, 2-47, 3-50

activated by host if communications failure occurs with master 1-50, 2-43, 3-46

controllers in clusters 1-9, 2-9, 3-10dial into host 10-4, 11-5dial out to panels 10-3, 11-5input 6-7

Expiration dateencoded in card format A-3

F

Facility code A-2FAI

Key Supervision State 3-27Relay Control 3-27Supervised State 3-26typical uses 3-20

FAI Modes 3-21Failed connections

number of retries 10-12, 11-14finding more information xviiifirmware

about 1-3, 2-3, 3-4Fixed card format field A-2FlashRom 4-2

G

GCM 2-2defined 1-2, 2-2features 1-2, 2-2specifying type See RM, Wyreless 2-26

General Controller Module. See GCMGeneral Purpose Inputs 3-22Global Antipassback Control by Cluster

defined 1-10, 2-9, 3-10

Index


Group 1 tab, RM LCD Messages dialog box 5-16Group 2 tab, RM LCD Messages dialog box 5-17Group 3 tab, RM LCD Messages dialog box 5-18,

5-19, 5-21, 5-22

H

Hardware MAC address, specifying for controller 1-16, 2-15, 3-16

Help xviiiHoliday Lists

configuring in Distributed Holidays modeapC 4-16iSTAR Edge 3-18iSTAR eX 2-17iSTAR Pro/Classic 1-19

Host modemsconfiguring 9-3

advanced options 9-8for dial-in 9-10for dial-out 10-13, 11-15phone numbers 9-5, 9-6remote phone number 10-14, 11-16which can be contacted by this panel 10-12,

11-14which can contact this panel 10-14, 11-16

Hostsconnection verification messages with 1-35,

2-31, 3-34information downloaded to master and

cluster members 1-34, 2-30, 3-33losing connection with master 1-37, 2-33,

3-36

I

I/32 dialog box 7-5I/32 system input board 7-5I/8 - Input Module 1-5, 2-5, 3-6, 7-5

adding to a controller 1-28

configuring 1-27, 1-28described 1-28Inputs

Communications Failure input, configuring 1-30

inputsTamper input, configuring 1-30

I/8 dialog box 1-28I/8dialog box 7-5Include Personnel Without Clearance in

Personnel Downloads 1-23, 2-23, 3-24information, finding more xviiiInput - events dialog box 6-8Input - linkages dialog box 6-11Input boards

configuring 1-27Input dialog box 6-3

configuring input for add-on boards 1-29Inputs

AC power failure 4-13, 6-18ACM sources 1-4, 2-4activating on supervision error 6-6alarm 4-2alarm devices 6-2configuring 6-2 to 6-12configuring inputs 1 to 8 3-27configuring inputs 1 to16 1-26, 2-23defined 4-2deleting 6-3dialup setting 6-9DSM 6-5I-8 inputs 1-29links for 6-11normal 6-5offline 6-5reversing normal state 6-6RTE 6-5sources 3-4

Index


supervised 4-2, 5-5, 6-2 to 6-7Tamper 4-13, 6-18types of 1-4, 2-4, 3-5unsupervised 4-3

Intervalfor dialing the panel 10-16, 11-18redialing panel during communications

failure 10-16, 11-18Intrusion Zones configured on apC dialog box

4-18Intrusion zones on panels, viewing 4-11, 4-18IP address 8-13

hostrequested over subnet by master

controller 1-49, 1-50, 1-53, 1-54, 2-41, 2-42, 2-46, 2-47, 3-45, 3-46, 3-49, 3-50

supplied to master controller by Configuration Utility 1-49, 1-50, 1-53, 1-54, 2-41, 2-42, 2-46, 2-47, 3-45, 3-46, 3-49, 3-50

masterrequested over subnet by controller 1-56,

1-57, 2-49, 2-50, 3-52, 3-53supplied to controller by Configuration

Utility 1-56, 1-57, 2-49, 2-50, 3-52, 3-53

specifying for controller 1-16, 2-15, 3-16

Issue code A-2iSTAR Configuration Utility

using to manually configure the master 1-34, 2-30, 3-33

iSTAR EdgeConditional Access 3-24connecting optional boards to 3-6

iSTAR eXConditional Access 2-23

iSTAR ProConditional Access 1-23

K

Keep-alive messages. See Connection Verification

L

Linkagesview for inputs 6-11view for outputs 6-16

Linksinputs 6-11outputs 6-16

Longitudinal Redundancy Check (LRC) A-3Low battery input, defined 1-21, 2-19, 3-20

M

MAC addressobtaining

with Configuration Utility,from GCM label 1-16, 2-15, 3-16

Magnetic cards A-5Main Board

AC power fail input, defined 1-21, 2-19, 3-20configuring 1-21, 2-20, 3-23

Options common to entire panel 1-23, 2-23, 3-24

RM Reader LCD messages, specifying 1-23, 2-23, 3-24

InputsAC power fail input, configuring 1-22,

2-22, 3-25Low battery input, configuring 1-22,

2-22, 3-25Onboard battery Low input, configuring

3-26Tamper input, configuring 1-22, 2-21,

3-25Low battery input, defined 1-21, 2-19, 3-20Onboard battery low input, defined 3-20

Index


Outputconfiguring

Output on GCM 1-23, 2-24Output on main board 3-28

Tamper input, described 1-21, 2-19, 2-21, 3-20, 3-25

Main boardspecifying type See RM, Wyreless 3-30

Master controllerabout 1-6, 2-6, 3-7alternate. See Alternate Mastercommunicates with host via TCP/IP. See also

Ethernet, Serial connection, RS-232, RS-485 1-48, 1-52, 2-41, 2-45, 3-44, 3-48

configuringinterval before controller is declared in

communications failure 1-57, 2-50, 3-53

interval between attempts to connect to host on primary communications path 1-49, 2-42, 3-45

interval between attempts to connect to host on secondary communications path 1-53, 2-45, 3-48

interval controller, host wait before declaring failure on secondary communications path 1-54, 2-47, 3-50

number of attempts to connect to host on secondary communications path 1-53, 2-45, 3-48

time to wait for a connection verification message before declaring primary path communications failure 1-50, 2-42, 3-46

connection verification messages with host 1-35, 2-31, 3-34

information downloaded from host 1-34, 2-30, 3-33

losing connections with host 1-37, 2-33, 3-36

primary communications path and 1-6, 2-7, 3-8

specifying interval between connection attempts made to host on primary communications path 1-48, 2-41, 3-44

specifying number of connection attempts before declaring secondary path communications failure 1-53, 2-46, 3-49

specifying number of connection attempts made to host on primary path before failure declared 1-49, 2-41, 3-45

specifying number of connection attempts to host on primary communications path before declaring failure 1-48, 2-41, 3-44

using iSTAR Configuration Utility to manually configure 1-34, 2-30, 3-33

Messagesconnection verification 1-35, 2-31, 3-34

Mini Star dialog box 7-14Mini-star coupler. See Star Coupler.Modem answer delay time 9-9, 10-18Modem dialog box 9-3, 9-6

Advanced tab 9-8Modem initialization string 9-9, 10-18Modem response wait time 9-9, 10-18

Modem status check time period 9-9, 10-18Modems

host 9-3, 9-8panel 10-15, 10-17, 11-17

Modify existing phone number dialog box 9-7Module

inputsCommunications Failure input 1-32

Modules. See Boards, optional.Monitoring point

reversing normal state 6-6

Index


Monitoring Stationmanual actions 10-3, 11-5

N

Network Ports 8-6attaching a device 8-6configuring 8-8dialup panels and other devices 8-6overview 8-2setting timeout delay time 8-12

NetworksGCM connections 1-2, 2-3

Normal alarm device state 4-2Note symbol xviiNumber

retrying failed connections 10-14

O

Offset value A-9Onboard battery Low 3-26Onboard battery low input, defined 3-20on-board Flash ROM 1-3, 2-3, 3-4Onboard Wiegand Reader

configuring readers 1 and 2 3-28Onboard Wiegand Readers 3-22Online, setting

modem 9-4panel 4-7port 8-11readers 5-3

Optional board. See Add-on boardsOutput - linkages dialog box 6-16Output boards

configuring 1-27

Output dialog box 6-13Output Module

adding to a controller 1-31Outputs 5-5

ACM sources 1-4, 2-4configuring 6-13 to 6-17configuring ACM Outputs 1 to 8 1-26connecting to ACM 1-5connecting to GCM 2-5connecting to main board 3-5defined 4-3deleting 6-13links 6-16normally energized 6-15pulse duration 6-15sources 3-4supervision error 6-7triggered by active inputs 6-7

P

Panel status inputs box 6-18Panel. See advanced processing Controller (apC),

apC/L, or apC/8XParity, in card formats A-2Password for dialup panels 10-14Periodic dialout 10-3

configuring 10-13, 11-15redialing panel during comm fail 10-16,

11-18Phone numbers

adding 9-6modems 9-15modifying 9-7

Physical address 8-11PIN options for reader keypad 5-6

at dialup panels 10-3

Index


PIN requirements 5-7PMB

connecting optional boards to 2-5defined 2-2

Poll periodSee also advanced processing Controller

(apC), apC/L, apC/8Xwhile in communications failure 4-9

Poll timeout delay timefor panels 4-9

Pollingfor apCs, apC/Ls, apC/8Xs 4-8

Port Configuration dialog box 8-2Port timeout delay time 8-12Port type

selecting 8-8, 8-11Port, identifying on host, for master controller

1-48, 1-52Ports

configuring 8-1 to 8-13COM ports from Windows XP 8-3network ports 8-6

for direct-connect panel 4-7overview 8-2

Power fail input monitors 6-18

Primary communications pathcluster configuration and distributed

management 1-2, 2-3, 3-3configuring 1-34, 2-29, 3-32connection verification messages and 1-35,

2-31, 3-34failure

specifying controller responsible for communications with host 1-52, 2-45, 3-48

using C•CURE Administration Application to set up 1-34, 2-29, 3-32

Proximity card formatparity length 5-30parity start 5-30

Proximity cards A-7

R

R/48 dialog box 7-10R/48 System output board 7-10R/8 - Output Module 1-5, 2-5, 3-6, 7-19

configuring 1-27inputs

Communications Failure input, configuring 1-32

Tamper input, configuring 1-32R/8 dialog box 7-19Reader dialog box 5-3Reader keypad

configuring entryvia card number 5-6via PIN 5-6

Reader keypad configuration dialog box 5-6Reader LCD Messages. See RM LCD MessagesReader sources 3-4Readers. See Card readersReconnection retry period 8-13Redial/reconnect delay time 9-9, 10-18Relay Outputs 3-22Remote location 10-2Remote panels. See Dialup panelsRemote phone number 10-14, 11-16Request to Exit (RTE)

input 6-5Retrying failed connections 10-14RM LCD messages

assigning to a panel 4-8

Index


changing the language 5-23configuring 5-15

RM LCD Messages dialog box 5-15

S

Secondary Communications Pathclusters 3-3clusters and 1-2, 2-3configuring

event activated by controller when test fails 1-59, 2-52, 3-55

interval between test messages 1-59, 2-52, 3-55

interval that controller waits between attempts to retest 1-59, 2-52, 3-55

configuring for cluster 1-51, 2-44, 3-47configuring test for 1-58, 2-51, 3-54, 11-11connection verification messages and 1-35,

2-31, 3-34establishing 1-35, 2-31, 3-34types of connections 1-7, 2-8, 3-9using C•CURE Administration Application

to configure 1-34, 2-29, 3-32Security objects, defining 1-25, 2-25Security, encryption on panels 10-4Serial connection

iSTAR 1-2master controller communicates with host

over Ethernet network via RS-232 or RS-485 serial connection 1-48, 1-52

specify port that master controller communicates with host via, 1-48

Site code A-2Special Purpose Inputs 3-20Star coupler

mini-star 7-12, 7-14proximity 7-15standard 7-12unsupervised inputs 4-3

Wiegand 7-15Star Coupler dialog box 7-12Supervised inputs 1-4, 2-4, 3-5, 5-5

configuring 6-2 to 6-12defined 4-2

System activitykeep-alive messages 1-35, 2-31, 3-34

T

Tamper inputs 6-18Tamper inputs, described 1-21, 2-19, 2-21, 3-20,

3-25TCP port 8-13TCP/IP

master controller and host communicate via 1-48, 1-52, 2-41, 2-45, 3-44, 3-48

master controller communicates with host via 1-48, 2-41, 3-44

master controller communicating with host via 1-52, 2-45, 3-48

Time specificationsdownloading to dialup panels 10-3interval for dialing panel 10-16

Time zoneapCs, apC/8Xs, apC/Ls 4-7setting, changing controllers 1-15, 2-14, 3-15

Timeout delaysfor ports 8-12

Index


Tip symbol xvii

U

unsupervised inputs 1-5, 2-5, 3-5Use DTR 9-9

V

Viewing intrusion zones on panels 4-18

W

Warning symbol xviiWiegand card format

complement fields in card 5-30parity length 5-30parity start 5-30

Wiegand cards A-6Wiegand Proximity Star Coupler dialog box 7-16Wiegand/proximity star coupler. See Star

coupler

c•cure 800/8000 hardware configuration guide

Documents