{"efta_number": "EFTA01225932", "page_count": 500, "url": "https://epstein-data.com/EFTA01225932", "pdf_url": "https://epstein-data.com/pdf/EFTA01225932.pdf", "pages": [{"efta_number": "EFTA01225932", "page_number": 0, "text_content": "SOFTWARE HOUSE \nFrom Tyco Security Products \nC•CURE 9000 \nVersion 2.50 \nHardware Configuration Guide \nSOFTWARE Hous \nREVISION R0 \nUM-I30 RO \nEFTA01225932\n", "char_count": 154}, {"efta_number": "EFTA01225932", "page_number": 1, "text_content": "C•CURE and Software House are registered trademarks of Tyco Security Products. \nThe trademarks, logos, and service marks displayed on this document are registered in the United States [or \nother countries]. Any misuse of the trademarks is strictly prohibited and Tyco Security Products will aggressively \nenforce its intellectual property rights to the fullest extent of the law, including pursuit of criminal prosecution \nwherever necessary. MI trademarks not owned by Tyco Security Products are the property of their respective \nowners, and are used with permission or allowed under applicable laws. \nProduct offerings and specifications are subject to change without notice. Actual products may vary from photos. \nNot all products include all features. Availability varies by region; contact your regional sales manager. \nC•CURE 9000 version: 250 \nDocument Number: UM-130 \nRevision: RO \nRelease Date: December 2015 \nThis manual is proprietary information of Software House. Unauthorized reproduction of any portion of this \nmanual is prohibited. The material in this manual is for information purposes only. It is subject to change \nwithout notice. Software House assumes no responsibility for incorrect information this manual may contain. \n2015 Tyco Security Products. \nMI rights reserved. \nEFTA01225933\n", "char_count": 1309}, {"efta_number": "EFTA01225932", "page_number": 2, "text_content": "Table of Contents \nPreface \n15 \nFinding More Information \n16 \nConventions  \n17 \nSoftware I louse Customer Support Center \n18 \nChapter 1 - The Hardware Pane \n19 \nUsing the Hardware Pane \n20 \nPartitions  \n21 \nHardware Tree \n22 \nHardware Tree Objects  \n22 \nHardware Tree Tasks \n23 \nCreating a New Object in the Hardware Tree \n23 \nDeleting an Object in the Hardware Tree  \n24 \nViewing a List of Hardware Tree Objects  \n24 \nAdd or Remove Reader Card Formats \n25 \nUsing Drag and Drop in the Hardware Tree \n27 \nGroups Tab for Hardware Devices  \n28 \nEditing a Hardware Device Group \n28 \nAdding a Hardware Device to a Group \n28 \nHardware Groups Tab Definitions  \n29 \nAdd a Hardware Device to Group from a Dynamic View  \n29 \nRefreshing the Hardware Tree \n30 \nHardware Folders  \n31 \nControllers and Dependent Objects  \n31 \nCreating a New Hardware Folder \n32 \nCreating and Using a New Hardware Folder Template  \n32 \nRenaming a Hardware Folder  \n33 \nTemplates  \n34 \nCreating a Template  \n34 \nEditing a Template  \n35 \nCreating an Object from a Template  \n36 \nUsing Templates for Controller Inputs, Outputs, and Readers \n37 \nDeleting a Template  \n38 \nViewing a List of Templates  \n39 \nCopying, Pasting, and Renaming Clusters and Controllers  \n40 \nC•CURE 9000 Hardware Configuration Guide \n3 \nEFTA01225934\n", "char_count": 1290}, {"efta_number": "EFTA01225932", "page_number": 3, "text_content": "Privileges  \n41 \nImportant Copy and Paste Process Information  \n41 \nCopy & Paste Tasks \n41 \nRenaming Clusters and Controllers  \n51 \nTrigger Target Events \n54 \nChapter 2 - Maintenance Mode \n57 \nMaintenance Mode Dialog Box \n58 \nMaintenance Mode Overview \n59 \nMaintenance Mode Objects Supported \n60 \nMaintenance Mode Configuration Tasks  \n61 \nConfiguring Privileges to Turn Maintenance Mode On and Off \n61 \nConfiguring the Application Layout for Maintenance Mode Filtering  \n62 \nTurning Maintenance Mode On and Off \n62 \nSTAR Cluster  \n63 \nSTAR Controller or apC Controller  \n64 \nTaking an STAR or apC Controller Out of Maintenance Mode.  \n64 \nViewing Maintenance Mode Objects in the Dynamic View  \n65 \nFiltering Partitions and Maintenance Mode Objects in the Dynamic View \n65 \nChapter 3 - Configuring Dialup \n67 \niSTAR Dialup  \n68 \nDialup Limitations  \n68 \niSTAR Dialup Configuration Sequence \n69 \nConfiguring the iSTAR Comm Port \n70 \nSTAR Comm Port State Images Tab \n72 \nConfiguring the Host Modem \n73 \nCreating a Cluster for Dialup  \n76 \nChapter 4 - Configuring CCURE iSTAR Clusters \n79 \nCluster Communications Overview  \n80 \nCluster Configuration and Distributed Management \n80 \nNetworked STAR Controllers (Clusters)  \n81 \nEstablishing Connections Via the Primary Communications Path  \n83 \nSetting Up the Primary Communications Path  \n84 \nDownloading Cardholder and Configuration Information \n84 \nMaintaining Communications  \n84 \nEstablishing a Secondary Communications Path  \n85 \nDistributed Cluster Management \n86 \nUnassigned Folder \n86 \nConfiguring iSTAR Clusters  \n87 \nCreating an iSTAR Ouster \n88 \nCreating and Using an iSTAR Ouster Template  \n89 \n4 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225935\n", "char_count": 1711}, {"efta_number": "EFTA01225932", "page_number": 4, "text_content": "iSTAR Cluster Editor \n91 \nSTAR Cluster Editor Tabs \n91 \nAccessing the STAR Cluster Editor  \n91 \niSTAR Cluster General Tab \n93 \nSTAR Cluster General Tab Tasks \n93 \nAdding a Controller to a Cluster  \n93 \nRemoving a Controller from a Cluster  \n93 \nSTAR Cluster General Tab Definitions  \n94 \niSTAR Cluster Communications Tab \n95 \nNumber of Failed Attempts Before Connection Fails  \n98 \niSTAR Cluster - Cluster Tab \n99 \niSTAR Cluster Miscellaneous Tab \n101 \niSTAR Cluster Area Tab \n102 \nCluster Antipassback Communications Failure Mode \n102 \nGlobal Antipassback for the Cluster  \n102 \nArea Tab Field Definitions  \n103 \niSTAR Cluster Encryption Tab \n105 \niSTAR Cluster Triggers Tab \n107 \niSTAR Cluster Dialup Configuration Tab \n113 \niSTAR Cluster Status Tab \n114 \niSTAR Cluster State Images Tab \n115 \nChapter 5 - Configuring C•CURE iSTAR Controllers \n117 \nUnderstanding C•CURE iSTAR Controllers  \n118 \nConfiguration Overview for iSTAR Controllers  \n119 \nSTAR Pro Configuration Summary  \n119 \nSTAR eX and STAR Edge Configuration Summary \n121 \nSTAR Ultra Configuration Summary  \n122 \niSTAR Controller Tasks  \n124 \nCreating an STAR Controller  \n124 \nCreating a Controller Template  \n125 \nDeleting an STAR Controller  \n126 \nEditing an STAR Controller  \n126 \nViewing a List of STAR Controllers  \n127 \nUsing the STAR Controller Context Menu  \n127 \nUsing Set Property for an STAR Controller  \n130 \nUpdating STAR Firmware (Ethernet Connections)  \n130 \nUpdating STAR Firmware (Dial-up Connections)  \n132 \nSTAR Firmware Updates Using ICU  \n135 \nChanging the Time Zone of an STAR Controller  \n136 \niSTAR Controller Editor \n137 \nSTAR Classic Controller Editor  \n137 \nC•CURE 9000 Hardware Configuration Gukie \n5 \nEFTA01225936\n", "char_count": 1707}, {"efta_number": "EFTA01225932", "page_number": 5, "text_content": "STAR Pro Controller Editor  \n137 \nSTAR eX Controller Editor  \n138 \nSTAR Edge Controller Editor  \n139 \nSTAR Ultra Controller Editor  \n139 \niSTAR Controller Editor Tabs  \n141 \nBasic Tabs  \n141 \nSTAR Specific Tabs  \n141 \nSTAR Controller General Tab  \n141 \nSTAR Controller Triggers Tab  \n147 \nSTAR Controller Status Tab  \n147 \nSTAR Controller User Defined Fields Tab  \n151 \nSTAR Controller State Images Tab  \n152 \nSTAR Schlage Wireless PIMs Tab \n153 \nSTAR Controller Boards Tab (STAR Classic/Pro)  \n156 \nSTAR eX and Edge Controller Inputs Tab  \n159 \nSTAR Edge/eX Controller Outputs Tab  \n164 \nSTAR Edge COMI/COM2/COM3 Tabs \n167 \nSTAR Edge Controller Wiegand Tab  \n169 \nSTAR eX Controller Wiegand Tab  \n171 \nSTAR eX COMI/COM2 Tabs \n173 \niSTAR Ultra Controller Editor Inputs Tab \n178 \nSTAR Ultra Controller Boards Tab  \n179 \nSTAR Ultra Controller IP-ACMs Tab \n181 \nSTAR Ultra COMI/COM2 Tabs  \n181 \niSTAR Ultra Controller ACM Board Editor \n184 \nSTAR Ultra ACM Board Editor  \n184 \nSTAR Ultra ACM Board Wiegand Tab  \n184 \nSTAR Ultra ACM Board RS-485 Tab  \n186 \nSTAR Ultra ACM RS-485 Device Port Editor  \n188 \nSTAR Ultra ACM RS-485 Device Port Tabs  \n189 \nSTAR Ultra RS-485 Device Port Readers Tab  \n190 \nSTAR Ultra RS-485 Device Port ACM EXT Tab \n192 \nSTAR Ultra ACM Board Status Tab  \n195 \niSTAR Classic/Pro Controller ACM Board Editor \n197 \nSTAR Classic/Pro ACM Board Editor  \n197 \nSTAR ACM Board General Tab  \n197 \nSTAR ACM Board Inputs Tab  \n198 \nSTAR ACM Board Outputs Tab  \n199 \nSTAR ACM Board Readers Tab  \n200 \nSTAR ACM Board ACM Ext Tab  \n201 \niSTAR Input Board Editor \n203 \nAccessing the STAR Input Board Editor  \n204 \nConfiguring STAR Input Boards \n205 \nSTAR Input Board General Tab  \n.206 \niSTAR Output Board Editor \n208 \nAccessing the STAR Output Board Editor  \n208 \n6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225937\n", "char_count": 1829}, {"efta_number": "EFTA01225932", "page_number": 6, "text_content": "Configuring STAR Output Boards  \n.210 \nSTAR Output Board General Tab  \n210 \niSTAR Ultra Wireless Readers  \n213 \nAssa Abby AperioTM Hubs and Wireless Readers  \n213 \nIR SchlageTM PIMs and Wireless Readers  \n213 \nSTAR Ultra Schlage Wireless Types of Connections  \n.214 \nWireless - PIM400 and PIM400-TD2 \n214 \nSummary Tables  \n215 \nReaders per Controller/Panel  \n218 \niSTAR Aperio RS-485 Hub Board Editor (iSTAR Ultra only) \n220 \nSTAR Aperio RS-485 Hub Board Editor General Tab  \n.220 \nSTAR Aperio Hub Board Editor Input Tab  \n222 \nSTAR Aperio Hub Board Editor Input Tab Definitions  \n223 \nSTAR Aperio Hub Board Editor Readers Tab  \n223 \nSTAR Aperio RS-485 Board Hub Editor Readers Tab Definitions  \n224 \niSTAR PIM-485 Board Editor \n226 \nSTAR PIM-485 Board Editor General Tab  \n226 \nSTAR PIM-485 Board Editor General Tab Definitions  \n227 \nSTAR PIM-485 Board Editor Input Tab  \n228 \nSTAR PIM-485 Board Editor Input Tab Definitions  \n229 \nSTAR PIM-485 Board Editor Readers Tab  \n229 \nSTAR PIM-485 Board Editor Readers Tab Definitions  \n230 \niSTAR Input Editor  \n.232 \nAccessing the STAR Input Editor  \n233 \nConfiguring an STAR Input  \n235 \nSTAR Input General Tab  \n.236 \nSTAR Input Intrusion Zone Tab  \n237 \nSTAR Input Triggers Tab  \n239 \nSTAR Input Status Tab  \n.239 \nSTAR Input State Images Tab  \n239 \niSTAR Output Editor  \n241 \nAccessing the STAR Output Editor  \n242 \nConfiguring an STAR Output  \n244 \nSTAR Output General Tab  \n245 \nSTAR Output Status Tab  \n246 \nSTAR Output State Images Tab  \n.246 \niSTAR Reader Editor \n248 \nAccessing the STAR Reader Editor  \n249 \nConfiguring STAR Readers  \n.250 \nSTAR Reader General Tab  \n250 \nSTAR Reader I/O Tab \n252 \nSTAR Reader Keypad Tab  \n253 \nSTAR Reader Triggers Tab  \n255 \nSTAR Reader Status Tab  \n256 \nSTAR Reader State Images Tab  \n.258 \niSTAR PIM-485 Reader Editor  \n260 \nC•CURE 9000 Hardware Configuration Gukie \n7 \nEFTA01225938\n", "char_count": 1876}, {"efta_number": "EFTA01225932", "page_number": 7, "text_content": "STAR PIM-485 Reader I/O Tab \n261 \niSTAR Aperio Reader Editor \n264 \nSTAR Aperio Reader I/O Tab \n266 \nSTAR Aperio Reader Keypad Tab \n268 \nTriggers Tab for iSTAR Devices  \n270 \nDefining a Trigger for an STAR Device  \n.271 \nRemoving a Trigger  \n.272 \nSTAR Triggers Tab Definitions  \n272 \nState Images Tab for iSTAR Devices  \n274 \nSTAR State Images Tabs Definitions  \n.274 \nCustomizing State Images for an STAR Device  \n274 \nRestore a Default State Image \n275 \nChapter 6 - Configuring the IP-ACM \n277 \nIP-ACM Overview  \n278 \nLimitations  \n278 \nIP-ACM Offline Mode \n279 \nStored Credentials  \n279 \nDoor Configuration  \n280 \nIP-ACM Configuration Sequence  \n280 \nConfiguring the IP-ACM \n282 \niSTAR Ultra IP-ACM Editor \n285 \nAccessing the STAR Ultra IP-ACM Editor  \n285 \nSTAR Ultra IP-ACM Outputs Tab  \n286 \nSTAR Ultra IP-ACM Wiegand Tab \n288 \nSTAR Ultra IP-ACM RS-485 Tab \n290 \nSTAR Ultra IP-ACM Inputs Tab  \n291 \nSTAR Ultra IP-ACM Status Tab \n293 \nChapter 7 - Configuring Advanced Processing Controllers (apC) \n295 \napC Panel Overview  \n296 \nFeatures of apC Panels  \n296 \nInputs and Alarm Device States  \n299 \nOutputs and Readers \n299 \nOptional Boards \n300 \napC Time Zones  \n.300 \nChanging the Time Zone of an apC Controller  \n.303 \napC Time Zone Reports  \n.303 \napC Firmware Update  \n306 \napC Controller Configuration Summary \n308 \napC Comm Port Editor \n310 \napC Comm Port Triggers Tab  \n315 \napC Comm Port Status Tab  \n316 \n8 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225939\n", "char_count": 1476}, {"efta_number": "EFTA01225932", "page_number": 8, "text_content": "apC Comm Port State Images Tab  \n.316 \napC Controller Editor \n318 \napC Controller General Tab  \n319 \napC Controller Communications Tab  \n321 \napC Controller Inputs Tab  \n322 \napC Controller Outputs Tab  \n323 \napC Controller Readers Tab  \n323 \napC Controller Add-On Board Tab  \n324 \napC Controller Status Tab  \n325 \napC Controller Triggers Tab  \n326 \napC Controller Holiday Groups Tab  \n.327 \nConfiguring Holiday Groups for an apC Panel  \n327 \napC Controller User Defined Fields Tab  \n329 \napC Controller State Images Tab  \n330 \napC Input Editor \n332 \napC Input General Tab  \n332 \napC Input Board Triggers Tab  \n333 \napC Input Board - Status Tab  \n334 \napC Inputs State Images Tab \n335 \napC Output Editor \n336 \napC Output General Tab  \n336 \napC Output Status Tab  \n337 \napC Output State Images Tab  \n338 \napC Reader Editor  \n340 \napC Reader General Tab  \n340 \napC Reader Input/Output Tab  \n341 \napC Reader Keypad Tab  \n342 \napC Reader Triggers Tab  \n344 \napC Reader Status Tab  \n344 \napC Reader State Images Tab  \n345 \napC Add-on Board Editor \n347 \napC Add-On Board General Tab  \n347 \napC Add-On Board Input Boards Tab \n348 \napC Add-On Board Output Boards Tab  \n349 \napC Add-On Board Star Coupler Tab \n354 \napC Input Board Editor (132 and 18) \n357 \napC 132 Input Board General Tab  \n357 \napC 132 Input Board 1-16 Inputs Tab  \n358 \napC 132 Input Board 17-32 Inputs Tab  \n360 \napC 18 Input Board General Tab  \n362 \napC Star Coupler Board Editor \n365 \nStar Coupler Readers Tab  \n366 \nStar Coupler Unsupervised Inputs Tab  \n367 \nStar Coupler Outputs Tab  \n367 \nTriggers Tab for apC Devices  \n369 \nC•CURE 9000 Hardware Configuration Gulls \n9 \nEFTA01225940\n", "char_count": 1650}, {"efta_number": "EFTA01225932", "page_number": 9, "text_content": "Defining a Trigger for an apC Device  \n370 \napC Triggers Tab Definitions  \n371 \nMini Star Coupler Board Editor \n373 \nWiegand Proximity Star Coupler Editor \n376 \nChapter 8 - Configuring RM Reader LCD Messages \n381 \nReader LCD Message Set Overview  \n382 \nReader LCD Message Set Editor \n383 \nAccessing the Reader LCD Message Set Editor  \n383 \nReader LCD Message Set Tasks  \n388 \nCreating a Reader LCD Message Set  \n.388 \nCreating a Reader LCD Message Set Template  \n388 \nConfiguring/Modifying a Reader LCD Message Set  \n389 \nViewing a List of Reader LCD Message Sets  \n389 \nDeleting a Reader LCD Message Set  \n391 \nUsing Set Property to Configure Reader LCD Message Sets  \n392 \nChanging the Language for the Default RM LCD Messages  \n393 \nChapter 9 - Floors \n395 \nFloors Overview \n396 \nConfiguring Floors  \n397 \nCreating a Floor  \n.399 \nCreating a Floor Template  \n399 \nDeleting a Floor  \n400 \nModifying a Floor  \n400 \nViewing a List of Floors  \n400 \nUsing Set Property to Configure Floors  \n400 \nAdd Floors to a Group \n401 \nChapter 10 - Doors \n403 \nDoor Overview \n404 \nDoor Tasks  \n405 \nCreating a Door \n405 \nCreating a Door Template  \n406 \nDeleting a Door \n407 \nModifying a Door \n407 \nViewing a List of Doors \n408 \nUsing Set Property to Configure Doors \n409 \nAdd a Hardware Device to Group from a Dynamic View  \n409 \napC Door Editor \n410 \nConfiguring an apC Door \n410 \napC Door General Tab  \n411 \napC Door Readers Tab  \n413 \napC Door Timing Tab  \n415 \n10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225941\n", "char_count": 1510}, {"efta_number": "EFTA01225932", "page_number": 10, "text_content": "apC Door Triggers Tab  \n416 \napC Door Status Tab  \n416 \napC Door State Images Tab  \n417 \napC Door Visitor Management Tab  \n418 \napC Door Definitions  \n421 \napC Door Readers Tab Definitions  \n421 \napC Door Tuning Tab Definitions  \n422 \napC Door Triggers Tab Definitions  \n423 \napC Door Trigger Properties  \n424 \napC Door Groups Tab Definitions  \n425 \napC Door Status Tab Definitions  \n425 \napC Door State Images Tab Fields and Icons  \n425 \niSTAR Door Editor \n427 \nSPAR Door General Tab  \n427 \nSTAR Door Timing Tab \n429 \nSTAR Door Areas & Zones Tab  \n431 \nSTAR Door Double Swipe Tab \n432 \nSTAR Door Conditional Access Tab  \n436 \nSTAR Door Triggers Tab  \n438 \nSTAR Door Status Tab  \n440 \niSTAR Door Monitoring Tab \n442 \nSTAR Door State Images Tab  \n442 \nSTAR Door Visitor Management tab  \n443 \niSTAR Door Definitions  \n446 \nSTAR Door Timing Tab Definitions  \n447 \nSTAR Door Areas and ZonesTab Definitions  \n448 \nSTAR Door Double Swipe Tab Definitions  \n448 \nSTAR Door Conditional Access Tab Definitions  \n449 \nSTAR Door Triggers Tab Definitions  \n450 \nSTAR Triggers Properties  \n451 \nSTAR Triggers Actions  \n452 \nSTAR Door Groups Tab Definitions  \n453 \nSTAR Door Status Tab Definitions:  \n454 \nSTAR Door State Images Tab Definitions:  \n454 \niSTAR Aperio Door Editor  \n455 \nChapter 11 - Configuring Advanced Door Monitoring \n457 \nUnderstanding Advanced Door Monitoring  \n458 \nFeatures  \n458 \nHardware Requirements  \n460 \nAdvanced Door Monitoring Definitions  \n461 \nNew Definitions, Acronyms, and Abbreviations  \n461 \nAdvanced Door Monitoring Components  \n463 \nLock Sensor Devices  \n463 \nC•CURE 9000 Hardware Configuration Guide \n11 \nEFTA01225942\n", "char_count": 1642}, {"efta_number": "EFTA01225932", "page_number": 11, "text_content": "Lock Release Devices  \n463 \nExpanded Door Inputs  \n464 \nAdvanced Door Alarms \n465 \nExpanded Event Actions  \n466 \nAdvanced Door Monitoring Configurations  \n467 \nMultiple RTE Configurations  \n467 \nMultiple DSM Configurations  \n468 \nDSM Configuration Guidelines  \n471 \nConfiguration Overview \n473 \nConfiguring an Advanced Door \n474 \nSample Door \n474 \nConfiguring RM4-1 and RM4-2 Reader, Inputs, and Output  \n474 \nConfiguring Lock Releases on the I/8 \n477 \nConfiguring the Advanced Door \n478 \nUnderstanding Timing \n481 \nKinds of Timing Options  \n481 \nGrace Time Options  \n482 \nChange Time Options  \n482 \nShunt Time Options  \n484 \nSpecial Timing Considerations  \n484 \nMonitoring Door Activity  \n486 \nUsing Monitoring Station Commands \n486 \nUsing Journal Reports  \n486 \nUnderstanding Door Alarms  \n487 \nAlarms \n487 \nNew Activity / Journal Reports  \n487 \nManaging Message Traffic  \n487 \nClearing Alarms \n491 \nDoor Triggers  \n491 \nPrivilege Modifications  \n492 \nReports  \n493 \nAdvanced Door Monitoring Details  \n495 \nDoor Monitoring Screen \n496 \nChapter 12 - Configuring Elevators \n499 \nElevator Configuration Overview \n500 \nElevator Tasks  \n501 \nCreating an Elevator  \n501 \nCreating an Elevator Template  \n501 \nDeleting an Elevator  \n502 \nModifying an Elevator  \n502 \nViewing a List of Elevators  \n.502 \nUsing Set Property for Elevators  \n.503 \nAdding Elevators to a Group \n503 \n12 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225943\n", "char_count": 1431}, {"efta_number": "EFTA01225932", "page_number": 12, "text_content": "iSTAR Elevators  \n505 \nConfiguring a Floor for an STAR Elevator  \n505 \nSTAR Elevator General Tab  \n506 \nSTAR Elevator Buttons Tab  \n.510 \nSTAR Elevator Status Tab  \n511 \nSTAR Elevator Triggers Tab  \n512 \nSTAR Elevator State Images Tab  \n513 \nSTAR Elevator Definitions  \n514 \napC Elevators  \n519 \nConfiguring a Floor for an apC Elevator  \n519 \napC Elevator General Tab  \n.520 \napC Elevator Buttons Tab  \n522 \napC Elevator Status Tab  \n.524 \napC Elevator Triggers Tab  \n525 \napC Elevator State Images Tab  \n525 \napC Elevator Definitions \n526 \nIndex \n531 \nC•CURE 9000 Hardware Configuration GukM \n13 \nEFTA01225944\n", "char_count": 611}, {"efta_number": "EFTA01225932", "page_number": 13, "text_content": "14 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225945\n", "char_count": 59}, {"efta_number": "EFTA01225932", "page_number": 14, "text_content": "Preface \nThis C•CURE 9000 Hardware Configuration Guide is designed for new and experienced security system users. The \nmanual describes the various hardware objects in the C•CURE 9000 application program and presents procedures \nfor configuring and using them. \nThe manual assumes that you have already installed C•CURE 9000 and have familiarized yourself with the basic \nC•CURE 9000 information provided in the C•CURE 9000 Getting Started Guide. \nIn this preface \nFinding More Information \n16 \nConventions  \n17 \nSoftware House Customer Support Center \n18 \nC•CURE 9000 Hardware Configuration Guide \nPreface \n15 \nEFTA01225946\n", "char_count": 625}, {"efta_number": "EFTA01225932", "page_number": 15, "text_content": "Finding More Information \nFinding More Information \nYou can access C•CURE 9000 manuals and online Help for more information about C•CURE 9000. \nManuals \nC•CURE 9000 software manuals are available in Adobe PDF format on the C•CURE 9000 DVD. \nYou can access the manuals if you copy the appropriate PDF files from the C•CURE 9000 Installation DVD \nEnglish \\ Manuals folder. \nThe available C• CURE 9000 and Software House manuals are listed in the C• CURE 9000 Installation and Upgrade \nGuide, and appear as hyperlinks in the online.pdf file on the C•CURE 9000 DVD English \\ Manuals folder. \nThese manuals are also available from the Software House Member Center website \nOnline Help \nYou can access C•CURE 9000 Help by pressing Fl or clicking Help from the menu bar in the \nAdministration/Monitoring Station applications. \n18 \nPreface \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225947\n", "char_count": 888}, {"efta_number": "EFTA01225932", "page_number": 16, "text_content": "Conventions \nConventions \nThis manual uses the f Aiming text formats and symbols. \nConvention \nMeaning \nBold \nThis font indicates screen elements, and also indicateswhen you should take a direct action in a procedure. \nBold font describes one of the following items: \n• A command or character to type, or \n• A button or option on the screen to press, or \n• A keyon the keyboard to press \n• A screen element or name \nblue color text \nIndicates a hyperlink to a UR L. or a cross-reference to a figure. table. or section in th is g u ide. \nRegularitakfonf \nIndicates a new term. \n<text> \nIndicates a variable. \nThe following items are used to indicate important information. \nNOTE \nTIP \nSTOP \nIndicates a note. Notes call attention to any item of information that may be of special importance. \nIndicates an alternate method of performing a task. \nIndicates a caution. A caution contains information essential to avoid damage to the system. A \ncaution can pertain to hardware or software. \nIndicates a warning. A warning contains information that advises users that failure to avoid a \nspecific action could result in physical harm to the user or to the hardware. \nIndicates a danger. A danger contains information that users must know to avoid death or serious \ninjury. \nC•CURE 9000 Hardware Configuration Guide \nPreface \n17 \nEFTA01225948\n", "char_count": 1337}, {"efta_number": "EFTA01225932", "page_number": 17, "text_content": "Software House Customer Support Center \nSoftware House Customer Support Center \nTelephone Technical Support \nDuring the period of the Agreement, the following guidelines apply: \n• Software House accepts service calls only from employees of the Systems integrator of Record for the installation \nassociated with the support inquiry. \nBefore Calling \nEnsure that you: \n• Are the Dealer of record for this account. \n• Are certified by Software House for this product. \n• Have a valid license and current Software Support Agreement (SSA) for the system. \n• Have your system serial number available. \n• Have your certification number available. \nHours \nNormal Support Hours \nMonday through F riday. 8:00 IMI. to 8:00 \n. EST. Except holidays. \nEmergency Support Hours \n24 hours/day, seven days a week. 365 days/year. \nRequires Enhanced SW? x2r Standby Telephone Support \n(emergency) provided to Certified Technicians. \nFor allother customers. billable on time and materials basis. \nMinimum charges apply- See MSRP. \nPhone For telephone support contact numbers for all regions. see \n18 \nPreface \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225949\n", "char_count": 1144}, {"efta_number": "EFTA01225932", "page_number": 18, "text_content": "The Hardware Pane \nThis chapter explains how to use the C•CURE 9000 Hardware pane to configure and manage the hardware \ncomponents that are connected to the C•CURE 9000 server. \nIn this chapter \nUsing the Hardware Pane \n20 \nHardware Tree \n22 \nGroups Tab for Hardware Devices  \n28 \nHardware Folders  \n31 \nTemplates  \n34 \nCopying, Pasting, and Renaming Clusters and Controllers  \n40 \nC•CURE 9000 Hardware Configuration Guide \nChapter 1 \n19 \nEFTA01225950\n", "char_count": 452}, {"efta_number": "EFTA01225932", "page_number": 19, "text_content": "Using the Hardware Pane \nUsing the Hardware Pane \nThe Hardware pane displays a tree structure that shows how you have configured the hardware on the C•CURE \n9000 system. For example, the hardware tree shows you which readers, inputs, and outputs are configured for each \ncontroller. \nYou can use the Hardware Tree to navigate to hardware components you want to view or edit, or to create new \nhardware components, such as a reader you want to add to a controller. \nThe Hardware Tree displays, by default, folders for Digital Certificates, Floors, Reader LCD Message Sets, and a \nHardware Folder called Company Name. \nThe folder called Company Name is the default container for apC Comm Ports and the Controllers, Readers, Doors, \nElevators, Inputs, and Outputs. \nThis folder is re-namable so that you can customize the C•CURE 9000 Hardware Tree to your site's needs. \nYou can create additional Hardware Folders as needed. \nYou can click on the E to the left of a folder or object to expand the tree. \nWhen you select a folder or object in the tree, you can right-click to display a context menu that shows the objects \nyou can create under the selected folder or object. \nExample: \nIf you right-click on the Company Name folder, the context menu shows that you can create a wide variety of \nHardware Tree objects in this folder. \nFigure 1: Hardware Tree Context Menu \n• iKw \nwe \n• liencti4nEwe\n•we \nTree\nDLL> caravv\n081W CK-14\n,inctaos \n:ea dune( le \n1. X \nLI unnoired \nLti \nEde \nblew \nfMnhdl 1.09 \nCORE rtbk \neo< Com•Port \nIFC \nAMI \n \nNew \nTerwtab \naoC Controls \nThe following topics provide more information about using the Hardware pane. \n• Partitions on Page 21 \n• Hardware Tree on Page 22 \n• Hardware Tree Objects on Page 22 \n• Hardware Tree Tasks on Page 23 \n20 \nChapter! \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225951\n", "char_count": 1834}, {"efta_number": "EFTA01225932", "page_number": 20, "text_content": "Using the Hardware Pane \nPartitions \nIf you partition the C•CURE 9000, a new Hardware folder is created for each Partition you create, and given the \nsame name as the Partition. \nYou can also create additional Hardware folders to contain hardware devices if you need to separately group \nhardware to reflect, for example, a multi-tenant building, a campus, or a multi-site company. \nYou can use Partitioning and Privileges to control Operator access to each tenant's hardware folder(s) if you don't \nwant one tenant to be able to view another tenant's security access hardware and personnel. \nThe New Object Partition setting in the Administration Workstation determines the Partition in which an Operator \ncan create objects, in addition to Hardware Tree objects such as Floors that reside at the root of the Hardware Tree. \nYou can use the Privilege Editor to grant or deny an Operator access to a Partition, which affects whether they can \nview or create objects in that Partition. \nFor example, you could create a privilege that has no access to the Partition (and Hardware folder) called Company \nA, but with full access to Company B, and assign it to Operators from Company B, so that they can view their \nconfiguration but not the configuration for Company A. See the C•CURE 9000 Software Configuration Guide for more \ninformation about the Privilege Editor. \nYou can also drag and drop objects to move them in the Hardware Tree. For example, you can move \nC•CURE Mobile objects from one Hardware folder to another. See Using Drag and Drop in the Hardware Tree on \nPage 27 for more information. \nC•CURE 9000 Hardware Configuration Guide \nChapter! \n21 \nEFTA01225952\n", "char_count": 1672}, {"efta_number": "EFTA01225932", "page_number": 21, "text_content": "Hardware Tree \nHardware Tree \nThe Hardware pane displays a tree structure that shows how you have configured the hardware on the C•CURE \n9000 system. For example, the hardware tree shows you which readers, inputs, and outputs are configured for each \ncontroller. \nYou can use the Hardware Tree to navigate to hardware components you want to view or edit, or to create new \nhardware components, such as a reader you want to add to a controller. \nThe Hardware Tree displays, by default, folders for Floors, Digital Certificates, and a Hardware Folder called \nCompany Name. \nThe folder called Company Name is the container for your Comm Ports, Controllers, Readers, Doors, Elevators, \nInputs, and Outputs. \nThis folder is re-namable so that you can customize the C•CURE 9000 Hardware Tree to your site's needs. \nYou can click on the \na\n \nto the left of a folder or object to expand the tree. \nWhen you select a folder or object in the tree, you can right-click to display a context menu that shows the objects \nyou can create under the selected folder or object. For example, if you right-click on the Company Name folder, the \ncontext menu shows that you can create a wide variety of Hardware Tree objects in this folder. \nIf you Partition your C•CURE 9000, a new Hardware folder is created for each Partition you create. This hardware \nfolder is given the same name as the Partition. \nYou can also create additional Hardware folders to contain hardware devices if you need to separately group \nhardware to reflect, for example, a multi-tenant building, a campus, or a multi-site company. \nYou can use Partitioning and Privileges to control Operator access to each tenant's hardware folder(s) if you don't \nwant one tenant to be able to view another tenant's security access hardware and personnel. \nFor example, you could create a privilege that has no access to the Partition (and Hardware folder) called Company \nA, but with full access to Company B, so that Operators from Company B can view their \n... [truncated, 2580 chars — for the full page use /api/corpus/document/EFTA01225932/21 or ?id=EFTA01225932&page=21]", "char_count": 2580}, {"efta_number": "EFTA01225932", "page_number": 22, "text_content": "Hardware Tree \nTable 1: Hardware Tree Objects \nObject \nDescription \nHardware Folder \nSee Hardware Folders on Page 31. \nDigital Certificate \nThese objects reside in the Hardware Tree but they are aeated using Encryption Options from the Options& Tools \npane. See the C•CURE 9000 System Maintenance Guide for more information. \nFloor \nSee Floors Overview on Page 396. \nReader LCD \nMessage Set \nSee Reader LCD Message Set Overview on Page 382 \napC Comm Port \nSee apC Comm Port Editor on Page 310. \nCCURE Mobile \ndevice \nThese objects reside in the Hardware Tree but they are documented in the C• CURE Mobile Handheld Reader User \nGuide. \nNOTE: C•CURE Mobile cannot be used in UL applications. \nSTAR Cluster \nSee Configuring iSTAR Clusterson Page 87. \napC Controller \nSee apC Panel Overview on Page 296. \nHardware Tree Tasks \n■ Creating a New Object in the Hardware Tree on Page 23 \n■ Deleting an Object in the Hardware Tree on Page 24 \n■ Viewing a List of Hardware Tree Objects on Page 24 \n■ Using Drag and Drop in the Hardware Tree on Page 27 \n■ Refreshing the Hardware Tree on Page 30 \n■ Creating a New Hardware Folder on Page 32 \n■ Creating and Using a New Hardware Folder Template on Page 32 \n■ Creating a New Hardware Folder on Page 32 \n■ Renaming a Hardware Folder on Page 33 \nCreating a New Object in the Hardware Tree \nMost objects in the Hardware Tree support a right-click Context Menu that shows you the actions you can perform \non that object. \nThe right-click Context Menu for an object has selections for objects that you can create under that object. \nFor example, if you want to create an iSTAR Cluster in a Hardware Folder, right-click on the Hardware Folder and \nselect iSTAR Ouster from the menu. \nC•CURE 9000 Hardware Configuration Guide \nChapter! \n23 \nEFTA01225954\n", "char_count": 1783}, {"efta_number": "EFTA01225932", "page_number": 23, "text_content": "Hardware Tree \nTo Create a New Object in the Hardware Tree \n1. Select the Folder or Object that will contain the object you want to create. \n2. Right-click on the object and you should see in the Context menu a list of the objects that you can create. \n3. Select the object you wish to create and select New from the menu. \n4. The Editor for the object opens and you can configure the object. \nDeleting an Object in the Hardware Tree \nYou can delete objects from the Hardware Tree if they are no longer needed. If you delete an object that has a child \nobject (such as a Door or Reader) below it, those objects are also deleted. \nTo Delete an Object in the Hardware Tree \n1. Select the Folder or Object that you wish to delete. \n2. Right-click on the object and select Delete. \n3. A confirmation dialog box appears to confirm that you want to delete the object. Click Yes to delete the object, or \nNo to cancel the deletion. \n4. A dialog box appears to confirm the deletion. You can click: \n• OK to close the dialog box. \n• Print to print the deletion message. \n• Email to send the deletion message to the email address you have configured in the Customer Support \nsection of the C•CURE 9000 System Variables. \nViewing a List of Hardware Tree Objects \nYou can view a list of any type of Hardware Tree object. \nTo View a List of Hardware Tree Objects \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Use the drop-down list in the Hardware pane to select the object type that you want to list. \n3. Click pa\n and a Dynamic View listing the object type appears in the content area. \n4. You can filter, sort, group, and add columns to the list. See the C•CURE 9000 Data Views User Guide chapter on \nDynamic Views for more information. \nThe Dynamic View for an object type includes a column that displays the Time Zone in which the object resides. \nThis can be useful in determining when an Event or Trigger is activated for an object in a different Time Zone than \nthe C\n... [truncated, 2421 chars — for the full page use /api/corpus/document/EFTA01225932/23 or ?id=EFTA01225932&page=23]", "char_count": 2421}, {"efta_number": "EFTA01225932", "page_number": 24, "text_content": "Hardware Tree \nThe context menu for iSTAR, apC, ASSA ABLOY, Connected Program readers allows you to select one or more \nreaders and Add or Remove Cards formats. See Add or Remove Reader Card Formats on Page 25 for more \ninformation. \nAdd or Remove Reader Card Formats \n'the context menu for for \napC, ASSA ABLOY, and Connected Program readers allows you to select one or \nmore readers and add or remove Cards formats. For iSTAR, the APERIO, Schlage Wireless, Direct Connect Wiegand, \nand RM readers offer this selection. \nThe context menu actions are equivalent to opening each of the selected readers and adding/removing the card \nformat from each reader. \nThe limits for card formats allowed for apC (8 per reader) and iSTAR (10 per reader) are enforced when using these \nmenu actions. \nIf the selected Card Formats cannot be added or removed from the selected readers, the confirmation dialog box for \nthe Add/Remove displays \"Already has card format\" or or \"Nothing to remove...\". Errors that occur are shown in the \nconfirmation dialog box as well. \nTo Add or Remove Card Formats from a Reader via a Dynamic View \n1. From the Hardware pane, use the drop-down menu to select the type of Reader you want to display in a \ndynamic View, and click giai. \nExample: \nIf you select iSTAR Reader, the Dynamic View displays multiple types of iSTAR Reader. If you select \niSTAR Aperio Reader, only that type of reader is displayed. \n2. Select one or more readers from the list (you can use multiple selection keystrokes such as CTRL+Left-click and \nSHIFT+Left-click to select more than one reader). \n3. Right-click the selected readers to display the context menu. \nX Debts \na \nEx psrt selectices.. \n9terAssecietcns \nItnitor \nAdd teed Format \nRemove C&d FOrrnbt \nEnable Keypad Gormands—\nDeg& Keypad Cunmands... \nSec...text,* Keypad Coward causes \nStew Ceara. Flter Causes \n4. Select Add Card Format or Remove Card Format from the menu. \n5. The Card Format Name Selection dialog box appears. Select (0) each\n... [truncated, 2149 chars — for the full page use /api/corpus/document/EFTA01225932/24 or ?id=EFTA01225932&page=24]", "char_count": 2149}, {"efta_number": "EFTA01225932", "page_number": 25, "text_content": "Hardware Tree \nOtesd Sam \nSeabee had Fcaml \nHem *ma \nI \nmp~Y \nCng co nnt \nGum hylwe\n41 \nNem \n1 I \nPaelkoNane \nI \nDemote \n• A \nI \nOa \nAID Gamete 10:0 \nDela& \nHO Capal0:0 St4 lone \nllIDNemxd \nCaul \nSabo 1•1 Kemal deka It. \nHID Seal Gael \nDMA \nSeal Gael 36 tiWiemd \nWAN Said /Mb Dela& \nDMA 32 SHORE Cod Ft. \n5-ea  law426 DMA \n26 blWaamdma \nSaMoobeaf \naka \nSiva 35 IS Ward pcme-• \nSere* Cad Sal Nu US \nNW • bi ad note \nSAWN Howe37 \nDOM \nSame Rose rat how r. \nSteardWand 2 Oat \nSward Waved 26t* lona. \nr \nr \nar \n6. If you added readers, a confirmation dialog box appears, showing the formats added: \nAdded cad bat to STAR Readerfla 1 \nAdded cad keret Sake Woad 26 (Ddeut) \nAdded cad facet Same Have 37 [DMA \n:71 Added cad keel to 67AR Aped° Reake141•7•S 465 Pal kal 2222 \n- Added cad lora Sawa Mcleod 26 (Dthoulti \nAdded cad lash: Selate Rae 37 Pela• \n7L-} Added cad foist to C01416TAR Realed•• t \nAdded mauls.: Sinc•abegar4 26 [NW) \nAdded cad toms: Son**. Howe 37 (RSA \n7. If you removed readers, a confirmation dialog box appears, show the formats removed: \n• \nRamon.d cad fame MO Seam Greed 36 (chit \n- Ronyfed cad tame: Item rear 16TAR FIM416Reeder2f1MIC0142•• \nRemoved cad kern* 'Same House 37 pdadr \nRemoved cad Sent 'HID Service Gael 36 [Default \ne Raved cad leas hem reeds SSTAR FIM485 Reeda341M1113142-uthe 1' \nRemoved cad last HID Sicr0cc Rowel 36 Peladf \nAswer•esd iedIMIS 110M teak. WAR PIM4E6Readea•micomu• \nReeved cad sweet MID Sinkre Gamed 36 NWT \n2 Nand 0,0 koMWS11001(6,401 iSTAR FIM-485ReadiSPN1COMNAa \nRimovoi cad Iota MID sins Gerd 36 B•180I \nO Raved cad tame: la ado %STAR PIM.405R•444:1/114:0•24re \nRemoved cad kat 'HID Sitar Gad 36 (Waif \nHothig to remove ham leS2I STAR FW.4\n Recale0•141COM2tthe I' \n.±J \nroc \nI II \n! \nI \nFold \n8. Click OK to complete the Add/Remove. \n26 \nChapter 1 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225957\n", "char_count": 1858}, {"efta_number": "EFTA01225932", "page_number": 26, "text_content": "Hardware Tree \nUsing Drag and Drop in the Hardware Tree \n(,11 can drag and drop objects to move them in the Hardware Tree, within certain restrictions. \n■ You cannot move Root level objects such as Folders and Floors. \n■ You cannot move objects in Hardware Folders to the Root level. \n■ You cannot move objects that are Folders, such as a folder named C•CURE Mobile (but you can move their \ncontents to another C•CURE Mobile folder). \n■ You cannot move child objects of one Controller to another Controller. \nNOTE \nSome objects cannot be moved to another partition via drag and drop. For example, you cannot move \nan iSTAR Controller to a different Partition via drag and drop, nor can you move a non-partitionable \nobject. Also, you cannot move an iSTAR Ouster to a different Partition if the Cluster is Enabled. \nTo determine if you can drag and drop an object, click on the object and then drag to the right with the mouse. If the \ncursor appears, you can drag and drop the object. If you try to drop the object in an invalid location, the object \ninstead remains in its original location. For example, if you tried to drop an apC Comm Port in an iSTAR Ouster, the \nobject is not be moved, and an error message \"Invalid Hardware Folder\" appears. \nTo Drag and Drop an Object in the Hardware Tree \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Click on an object to select it (the object will be highlighted when selected). \n3. Drag to the right with the mouse. The drag and drop cursor lig appears. (If it does not appear, you cannot drag \nand drop the object.) \n4. Drag the object to the location you want and release the mouse button. If you have chosen a valid location for the \nobject, it then appears in the new location. \nExample \nIf you drag an apC Controller to a different Hardware Folder, the apC and all its child objects are moved to \nthat Hardware Folder. \nC•CURE 9000 Hardware Configuration Guide \nChapter! \n27 \nEFTA01225958\n", "char_count": 1978}, {"efta_number": "EFTA01225932", "page_number": 27, "text_content": "Groups Tab for Hardware Devices \nGroups Tab for Hardware Devices \nThe Groups tab for a Hardware device lists all of the Groups to which the Hardware device currently being edited \nbelongs. The Groups in the list are lists of Hardware devices of the same type (such as Inputs, Readers, and so on). \nFigure 2 on Page 28 shows the Groups tab for an iSTAR Input, which is typical for a Hardware device. \nFlgu re 2: Typical iSTAR Group Tab \n-]here and Cb:e \nName: \naelaiOixr \nTanpertyo4 \nEntle4 \n1%“•••• I\n•Matti CimiemleiffilMinmem. \n••••• •• IL:=1/1•\n••• ••••li \nGroups \nY, \nPisan Deka \nCart 1 \nComo column: to grout) b/ ham \nNam• \nD•wirAon \nHardware Groups Tab Definitions on Page 29 provides definitions for the fields and buttons on an iSTAR Device \nGroup tab. \nEditing a Hardware Device Group \nYou can edit any of the Groups in the list on the Groups tab by double.clicking on the Group's name in the list of \nGroups. \nAdding a Hardware Device to a Group \nTo add a Hardware device to a Group, you need to either: \n■ Edit the Group by opening the Configuration pane and using the Group Editor. \nOr \n■ Display a list of devices of that type and use the context menu Add to Group selection. You cannot add the \nHardware device to a Group from the Groups tab (the device is already a member of every Group that is listed \nhere). \nSee Add a Hardware Device to Group from a Dynamic View on Page 409 for more information. \n28 \nChapter 1 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225959\n", "char_count": 1487}, {"efta_number": "EFTA01225932", "page_number": 28, "text_content": "Groups Tab for Hardware Devices \nHardware Groups Tab Definitions \nTable 2 on Page 29 provides definitions of the fields and buttons on the Groups tab for a Hardware pane device. \nTable 2: Groups Tab Definitions \nFlekUButton \nIcon \nDescription \nCard View \nit\ni\nDisplays the list of Groups in Card View. \nPrint \na\nl.\n/4—\n±\n/.\nPrints the list of Groups. \nGroup \nIt\ni\nClick to enable Grouping of theist. You can drag a column heading to the area labeled Drag columns to \ngroup by here to group theist by that heading. \nFite( \nV \nClick to display the (her bar. See the C. CURE 9000 Data Views Guide for more information about filtering \na Dynamic View fist. \nRow Selector \n• \nClick to sektcla row in the table. \nCount \nThis field displays the number of Groups in the list. \nName \nThis column lists the names of the Groups of which this device is a member. \nDescription \nThis column lists the descriptions of the Groups of which this device is a member. \nAdd a Hardware Device to Group from a Dynamic View \nWhen you select a I lardware device from a Dynamic View and then right-click for the context menu, Add to group \nappears as a menu selection. This function enables you to add the object(s) to a Group. More more information about \nthe Group function see Groups Tab for Hardware Devices on Page 28. \nTo Add a Hardware Device To a Group \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select a Hardware device from the Hardware pane drop-down list. \n3. Click mai to open a Dynamic View showing all objects of that type. \n4. Right-click on the object that you want to add to a Group and select Add To Group. A list of Groups is \ndisplayed. \n5. Select the Group from the list, and the object is added to that group. \n6. Click OK to confirm your choice. \nC•CURE 9000 Hardware Configuration Guide \nChapter 1 \n29 \nEFTA01225960\n", "char_count": 1880}, {"efta_number": "EFTA01225932", "page_number": 29, "text_content": "Groups Tab for Hardware Devices \nRefreshing the Hardware Tree \nTo make sure that all the folders and objects in the Hardware Tree are accurately displayed on the screen, you can \nRtfivsh the Hardware Tree. \nTo Refresh the Hardware Tree \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Right-click on Hardware and select Refresh Tree from the context menu. The Hardware Tree is updated. \n30 \nChapter 1 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225961\n", "char_count": 492}, {"efta_number": "EFTA01225932", "page_number": 30, "text_content": "Hardware Folders \nHardware Folders \nYou can create additional Hardware Folders if you need to organize the Controllers and access hardware into \nseparate folders. \nWhen you create a new Partition, a new Hardware Folder is automatically created to contain objects that reside in \nthat Partition. \nA Hardware Folder pane displays a tree structure that shows how you have configured the hardware on the \nC•CURE 9000 system. For example, the hardware tree shows you which readers, inputs, and outputs are configured \nfor each controller. \nYou can use the Hardware Tree to navigate to hardware components you want to view or edit, or to create new \nhardware components, such as a reader you want to add to a controller. \nThe following topics provide more information about Hardware folders. \n■ Controllers and Dependent Objects on Page 31 \n■ Creating a New Hardware Folder on Page 32 \n■ Creating and Using a New Hardware Folder Template on Page 32 \n■ Renaming a Hardware Folder on Page 33 \nControllers and Dependent Objects \nDependent (child) objects that are managed under iSTAR and apC controllers include inputs, outputs, readers, \nboards, elevators, floors and doors. Controllers are parent objects to thee and are created first. The parent objects are \ncreated within the company name folder in the hardware tree and must be created before the child objects in their \nrespective classes, such as apC and iSTAR. \nFor iSTAR controllers, a cluster object encompasses a system of one or more iSTAR controllers, determining \ncommunications between individual controllers. To configure an iSTAR controller in the \nC• CURE 9000 system, you must first create a cluster. Each cluster is configured as either Non-encrypted (iSTAR \nClassic/Pro and Ultra) or Encrypted (iSTAR eX/Edge and Ultra) controllers. The cluster must have a controller that \nis the primary communication path to the host and may have an optional secondary communication path. The \nsecondary communication path can be set to the same contr\n... [truncated, 3080 chars — for the full page use /api/corpus/document/EFTA01225932/30 or ?id=EFTA01225932&page=30]", "char_count": 3080}, {"efta_number": "EFTA01225932", "page_number": 31, "text_content": "Hardware Folders \nexist for the door. Doors typically require readers, inputs and outputs. The inputs are used for door state monitors \nand exit devices. The outputs are used for locks and automatic door openers. \nExample: \nC•CURE 9000 dependent object hierarchy examples: \n■ iSTAR Cluster>iSTAR Controller>Readers, Inputs, Outputs> \niSTAR Doors \n■ apC Comm Port>apC Controller>Readers, Inputs, Outputs>apC Doors \nCreating a New Hardware Folder \nPerform the following steps to create a new Hardware Folder. \nTo Create a New Hardware Folder \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Right-click on Hardware in the tree and select Hardware Folder>New from the context menu. The Hardware \nFolder dialog box opens. \n3. Type the name for the new folder into the Name field. \n4. Optionally type a description for the new folder into the Description field. \n5. Click Save and Close to save the new folder. \n6. Right-click on Hardware and select Refresh Tree from the context menu. The Hardware Tree is updated to \ndisplay the new folder. \nCreating and Using a New Hardware Folder Template \nYou can create a Hardware Folder Template that you can use as a basis for creating additional Hardware Folders. \nIn a template, you can fill in field values that will have the same values for all Hardware Folders, and then use the \ntemplate when you are creating new Hardware Folders. \nTo Create a New Hardware Folder Template \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Right-click on Hardware in the tree and select Hardware Folder>New Template from the context menu. The \nHardware Folder dialog box opens. \n3. Type the name for the new folder into the Name field. \n4. Optionally type a description for the new folder into the Description field. \n5. Click Save and Close to save the new folder template. \nTo Use a Hardware Folder Template to Create New Hardware Folders \n1. Click the Hardware button in the Navigation Pane to open th\n... [truncated, 2088 chars — for the full page use /api/corpus/document/EFTA01225932/31 or ?id=EFTA01225932&page=31]", "char_count": 2088}, {"efta_number": "EFTA01225932", "page_number": 32, "text_content": "Hardware Folders \n2. Right-click on Hardware in the tree and select Hardware Folder from the context menu. The next level menu \nappears listing the Hardware Folder Templates you have previously created under the — Templates category. \n3. Click on the name of the Hardware Folder Template you wish to use as the basis for the new Hardware Folder. \n4. Type the name for the new folder into the Name field. \n5. Optionally type a description for the new folder into the Description field. \n6. Click Save and Close to save the new folder. \n7. Right-click on Hardware and select Refresh Tree from the context menu. The Hardware Tree is updated to \ndisplay the new folder. \nRenaming a Hardware Folder \nYou can rename a I lardware Folder to customize it to your site's needs. Typically, you will want to rename the \ndefault folder, Company Name, with a more suitable name. \nTo Rename a Hardware Folder \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Right-click on the folder that you want to rename, and select Edit from the context menu. The Hardware Folder \nEditor dialog box opens. \n3. Type the new name for the folder into the Name field. \n4. Optionally type a description for the folder into the Description field. \n5. Click Save and Close to save the renamed folder. \nC•CURE 9000 Hardware Configuration Guide \nChapter! \n33 \nEFTA01225964\n", "char_count": 1372}, {"efta_number": "EFTA01225932", "page_number": 33, "text_content": "Templates \nTemplates \nThe C•CURE 9000 Hardware pane supports the concept of Templates for almost all objects in the Hardware Tree. A \nTemplate is a re-usable object you can create and configure with settings that you would like to use when creating \nother objects. For example, if all of the iSTAR Readers are the same reader type, using the same card format, you \ncould create a Reader Template that contained those settings, and apply that Template to any iSTAR Reader object \nthat you create, to make Reader configuration faster and more consistent. The Template objects you create do not \nappear in the Hardware Tree, but they are available to be applied when you create an object of the same type as the \nTemplate. \nThe following topics provide more information about using the Hardware Templates. \n■ Creating a Template on Page 34 \n■ Editing a Template on Page 35 \n■ Creating an Object from a Template on Page 36 \n■ Using Templates for Controller Inputs, Outputs, and Readers on Page 37 \n■ Viewing a List of Templates on Page 39 \n■ Deleting a Template on Page 38 \nCreating a Template \nTo create a new Template for an object, it is necessary to create an instance of the parent object for the object so that \nthe object type for the Template appears in the Hardware Tree. For example, to create a Template for the iSTAR eX \nController object type, you need to create an iSTAR Cluster that can contain iSTAR eX Controllers first, then create the \niSTAR eX Controller Template. \n\"MI\nTo Create a Template \n1. In the Navigation pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Navigate to the Hardware folder that contains the object type for which you want to create a new Template. \nExample: \nIf you want to create a Template for an iSTAR eX Controller, navigate to a folder that contains an iSTAR \nCluster for iSTAR eX Controllers. \n3. Select the parent object type (in this case, iSTAR Cluster) and right-click to display the context menu. \n4. Select the obj\n... [truncated, 2187 chars — for the full page use /api/corpus/document/EFTA01225932/33 or ?id=EFTA01225932&page=33]", "char_count": 2187}, {"efta_number": "EFTA01225932", "page_number": 34, "text_content": "Templates \nFigure 3: Creating a New Controller Template \nA ID New Redeem Fade( \nt \nepC ComrePoite \nCCURE Mobile \nha ape ill \n• ej  \n21 Doom \n_ __, Data VieW \nEck \nDelete \nSe property \nAdd to gap \nEyed selection.. \nFed in Audt loo.. \nFed inJoumat.. \n'STAR Contiolei \n• \nIJ ronfigurallon \nvideo \n° \nK  \nNew Template \ncontrelei template \n5. The editor for the object opens the new Template. \n6. Configure any settings you want to include in the Template. \n7. To save the new Template, click Save and Close. \nThe new template appears under — Templates in that object type's context menu drop-down list in the Hardware \ntree. For example, in Figure 3 on Page 35, an iSTAR Controller Template named controller template appears in the \ncontext menu. \nEditing a Template \nIf you have created a Template and need to make changes to it, you need to locate the Template to edit it. Because \nyou cannot view Templates in the Hardware Tree, and most default Dynamic Views do not list Templates, you may \nneed to create a new Dynamic View that shows the Templates you have created. \nThis section will use Inputs as an example, and show you how to create a Dynamic View that lists the Input \nTemplates along with the Controller Inputs. \nNote that you can create a Dynamic View that shows only apC Inputs or iSTAR Inputs by choosing that object type, \nor you can create a View that lists all Input (or Door or Reader) objects, then filter that view to show only the Inputs \n(or Doors or Readers) of a particular type. \nTo View Templates in a Dynamic View \n1. Navigate to Data Views and choose Dynamic View from the Data Views drop-down list. \n2. Click New. The Dynamic View editor opens. \n3. Type a name for your Dynamic View in the Name field. Include 'with Templates' in the name of the Dynamic \nView so that you can find the view again easily. \nC•CURE 9000 Hardware Configuration Guide \nChapter! \n35 \nEFTA01225966\n", "char_count": 1901}, {"efta_number": "EFTA01225932", "page_number": 35, "text_content": "Templates \nExample: \nInputs Dynamic View (with Templates) \n4. Type a description of the view in the Description field. \n5. Click 0 \nin the View Type field. A dialog box appears listing the object types you can choose for your Dynamic \nView. \n6. Click on 'Click here to filter data' and type the first letter of the name of the object type for which you wish to \ncreate a Dynamic View. The list of object types is filtered to show only the types that begin with that letter. \nExample: \nTo create a list of Inputs, type 'r then click on Input \n7. Click Add to add a column to the Dynamic View. \n8. Click 0 \nin Column Property, then click Name to add the Name Property to display in the column. \n9. Click Add to add a column to the Dynamic View. \n10. Click 0 \nin Column Property, then click Template to add the Template Property to display in the column. \n11. You can click Add again to add more columns as needed. \n12. Click Save and Close to save the Dynamic View. \n13. In the Data Views pane, click ea t to display a list of your Dynamic Views. \n14. Double-click on the Dynamic View you just created. When it appears, it will list all of the objects of the object \ntype you specified, and the Template column identifies which objects are Templates. \n15. Find the Template you wish to edit, and double-click it to open the editor to edit the Template. \n16. When you have completed making changes to the Template, click Save and Close to save your changes. \nCreating an Object from a Template \nYou can create objects such as Controllers, Doors, and Elevators from Templates. \nTo Create an Object from a Template \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Navigate to the Hardware folder that contains the parent object in which you want to create the new object from \na Template. \n3. Select the parent object and right-click to display the context menu. \n4. Select the object type and click the Template you want to use from the context \n... [truncated, 2365 chars — for the full page use /api/corpus/document/EFTA01225932/35 or ?id=EFTA01225932&page=35]", "char_count": 2365}, {"efta_number": "EFTA01225932", "page_number": 36, "text_content": "Templates \n7. '1'o\n \n save the new object, click Save and Close. \nUsing Templates for Controller Inputs, Outputs, and Readers \nYou can use templates as the basis for objects that you create while configuring Controllers in C•CURE 9000. For \nexample, if you are configuring an iSTAR Controller that has an 1/8 board, you can create an Input template and use \nthat template as the basis for one or more iSTAR Inputs on that 1/8 board. \nTypically, you create these objects from a tab within the Controller editor. The tab where you create such an object \ncontains a table that includes a Template column for you to identify a Template to use as a basis for the objects you \ncreate. \nExample: \nThe apC Controller editor has tabs for Inputs, Outputs, and Readers. On each of these tabs, there is a Template \ncolumn that lets you select a Template to use for creating new objects. \nFigure 4 on Page 37 shows an example of an apC Outputs tab with an apC Template selected in the Template \ncolumn. \nFigure 4: apC Outputs Template \n' et. Carman • meal \njriSen•rdOut \nE.ad \nPon. Dwst \nCOT.M.3C\" If pit Ou:ds Rea*, 4,310, Stn i SWsa \nSyeaw)ei \nCluleASOkipis _ Ogivom Dips \nIndex \nS \n 16\nCakand \nO \net 0•Serape \nO \nI  itC Del -al\nn \nmccup...scri \nO \nat Illturncil \n• \n.tasSect \no \n_s•ccvon<ix \n- \n4\nm.. \nO \n.pc ciao tens. ID \nIOC INN Tana,. ID \n at  Oa/ iferOde ID \nSCOW. Tonle.. ID \nIOC la w Tenn. ID \nCC \n7nWe ID \n,RC CUD/ \n• ID \nhalo \nCIO In tan ckes \n4, \n&*E hecia \nDAY \nPalm \n-\nen* nin \nBy default, when you select a Template for one object in the list, the same Template is added as the basis for each \nobject. You can use more than one Template by configuring the objects for which you want to use one Template, then \nchoosing one or more different Templates for the remaining objects. \nTo Use Templates for Controller Inputs, Outputs, or Readers \n1. From the Hardware pane, open the Controller Editor for the Controller you want to configure. \nC•CURE 9000 Hardware Configuration Guide \nChapter! \n37 \nEFTA\n... [truncated, 2009 chars — for the full page use /api/corpus/document/EFTA01225932/36 or ?id=EFTA01225932&page=36]", "char_count": 2009}, {"efta_number": "EFTA01225932", "page_number": 37, "text_content": "Templates \n2. Click the tab in the Controller Editor for the objects you want to configure. \nExample: \nIn the apC Editor, click the Outputs tab to configure Outputs on this apC. \n3. To specify a Template for an object you want to configure, click in the Template column of an object that is not \nyet configured (Configured column value is D. \n4. Click 0 \nto select a Template. A dialog box opens listing the available Templates. See Figure 4 on Page 37 for an \nexample. \n5. Click on a Template in the list to select it. That Template is added to every object in the table that is not already \nconfigured. \n6. Select the Configured column 2 for each object you want to configure with the selected Template. \n7. If you want to select a different Template for any of the remaining objects in the table that you have not yet \nconfigured (Configured column value is 0): \na. Click in the Template column of that object, then click 0 \nto select a Template. A dialog box opens listing the \navailable Templates. \nb. Click on a Template in the list to select it. That Template is added to every object in the table that is not \nalready configured. \nc. Select the Configured column 2 for each object you want to configure with the selected Template. \n8. Repeat Step 7 for any additional objects for which you want to choose a different Template. \n9. To edit any of the objects, click 0 \nin the Edit column for that object. The editor for that object opens. The fields \nthat were configured in the Template are already configured in the object you are editing. \n10. When you have completed configuring an object from the Template, click Save and Close in the object editor to \nsave the object. \n11. Click Save and Close in the Controller editor to save the your changes to the Controller. \nDeleting a Template \nYou can delete a template that you have created by using the right-click context menu in a Dynamic View. \nTo Delete a Template \n1. In the Navigation pane, select the type of object you want to delete f\n... [truncated, 2538 chars — for the full page use /api/corpus/document/EFTA01225932/37 or ?id=EFTA01225932&page=37]", "char_count": 2538}, {"efta_number": "EFTA01225932", "page_number": 38, "text_content": "Templates \nViewing a List of Templates \nYou can include Templates in a list of objects of a type. \nTypically the Dynamic View for an object type does not include Template objects. You can use the Template check \nbox to cause the Dynamic View to list all the Templates you have created. \nTo View a List of Templates \n1. In the Navigation pane, select the type of object you wish to view from the drop-down list. (For example, in the \nHardware pane, choose apC Comm Port from the drop-down list.) \n2. Click the Search pane. \n3. Select the Template check box \n4. Click 0 \nto display a list of the objects that includes the Templates you have defined. \nC•CURE 9000 Hardware Configuration Guide \nChapter! \n39 \nEFTA01225970\n", "char_count": 718}, {"efta_number": "EFTA01225932", "page_number": 39, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \nCopying, Pasting, and Renaming Clusters and Controllers \nThe C•CURE 9000 supports the ability to duplicate an existing configured iSTAR Cluster with all of its included \nSecurity Objects - Controllers, Boards, Inputs, Outputs, Readers, Doors, Elevators, Triggers (plus associated Events). \n■ The Copy & Paste context menu selection can be used to make a duplicate of a Ouster and its Child Objects on \nthe same partition on the same system. \n■ The Copy To context menu selection can be used to make a duplicate of a Ouster and its Child Objects on a \ndifferent partition on the same system, using Paste From. \n■ With a flash drive or other portable memory device or shared drive, the Copy To and Paste From context menu \nselections can be used to duplicate the Ouster and Children on another system. \n■ The Rename context menu selection is used to give these duplicated Objects new names. \n■ If you are extensively using the Copy & Paste and Rename features, it is good practice to establish a naming \nconvention for the site and then rename based on that convention. \nExample: \nCreate the new Clusters and Controllers with -Bldg appended to all of the objects. While Copying and Pasting \nyou can use Search and Replace to change -BLDG-Copy-datelime to -BLDG-A. See Using Search and Replace \non Page 43. \nNOTE \nThe Export and Import of Clusters does not include all the doors, elevators and events (configured via \ntriggers). Copy & Paste includes all of those objects. \nWhen an iSTAR Cluster is selected and Copy & Paste is used, the following objects that belong to that cluster are \ncopied and pasted: \n■ All configured Controllers plus the following components of each Controller: \n• Boards (all the boards including GCM, ACMs, Aperio Hubs or Schlage PIMs, etc.) \n• Inputs (including I/8s, I/8-CSIs) \n• Outputs (including R/8s) \n• Readers (all types) \n• Doors \n• Elevators \n• Triggers, including their associated Events and actions \nWhen a\n... [truncated, 2456 chars — for the full page use /api/corpus/document/EFTA01225932/39 or ?id=EFTA01225932&page=39]", "char_count": 2456}, {"efta_number": "EFTA01225932", "page_number": 40, "text_content": "Copying, Pasting, and Renaming Clusters and Controllers \nPrivileges \nTo use the Copy & Paste, Copy To, Copy From and Rename features, you must be an Administrator or an operator \nthat has a Privilege with those Permissions granted for iSTAR Controller and iSTAR Cluster. \nThe iSTAR Controller and iSTAR Cluster Privilege Permission features are located in the Privileges dialog box \nDefaults tab. Click on the Hardware>Controllers>iSTAR. Locate the iSTAR Controller and iSTAR Cluster for the \nPermissions for the Privilege. \nSee the C•CURE 9000 Software Cori figuration Guide Privileges' chapter for more information. \nImportant Copy and Paste Process Information \n■ All the child objects that are copied and pasted follow the same naming convention (i.e., Copy [date-time] will \nbe appended to their original names.) \n■ If copying and pasting on the same system, the objects are pasted in the same partition as the source objects. If \nyou are pasting on another system, the pasted objects will have the same partition as the object or folder on \nwhich user right-clicked and selected Paste From. \n■ MI the export files are .xml files. \n■ During import, the secondary objects must exist on the destination system. If not, then the import of object that \nrefers to secondary object will be aborted. For example, Event A is configured to activate Event B. Here Event B is \nthe secondary object and it must already exist otherwise the import will be aborted. \n■ Copy & Paste copies all triggers assigned to the object, including the events and event actions, but not all of the \nevent action targets, such as a sound object. \n■ When copying a panel which has panel events associated with it, the panel events are copied but not assigned \nto the panel. The panel must be assigned manually after the copy is complete and host events must be \nreconfigured. \nCopy & Paste Tasks \n0 \nWhen you copy a Controller, or a Controller in a Cluster, the MAC address is also copied. \nThe copied Controller MAC address \n... [truncated, 2596 chars — for the full page use /api/corpus/document/EFTA01225932/40 or ?id=EFTA01225932&page=40]", "char_count": 2596}, {"efta_number": "EFTA01225932", "page_number": 41, "text_content": "Copying, Pasting, and Renaming Clusters and Controllers \n• A Ouster, plus all the objects within that Ouster with the same names as the existing ones with -Copy [date-\nlime] appended to their names. \n• A Controller with -Copy [date-time] appended to its name, plus all the objects within that Controller. \nExample: \nFor a Cluster named Ouster5, the new cluster's name will be Cluster5-Copy [date-time], and if the Ouster has a \nController named Controller/, the new name will be Controller/-Copy [date-time]. \nFor a Controller named Controlleth, the new name will be Controller6-Copy [date-time]. \nTo Create a Copy of an Existing Cluster or Controller on the Same System \n1. Right-click on an existing Ouster, or Controller, in the Hardware tree and select Copy & Paste from the context \nmenu. Figure 5 on Page 42 shows selecting to copy and paste a Ouster. \nFigure S: Copy& Paste Context Menu Selection \nC'CURE 9000 Administration Station \nOperator Help \nHardware \nit! \n• lam ante \nHiram' Tree \n• Hardware \nEl Digdal Certificates \nLi CompanyName \n• Lj ISTAR Container \n• j-j Cluster-\n. \nE \nEck \nE \nX \nDelete \ntie\nset property \nzJ \n - \n1 \nSeed. \nLJ Unassigned rx\nAdd to gray \nFeint stem—\nOptions It Took \n-• \nVideo \n,j ) Card Fomwts a \n1.O \nconfiguration \nData News \nill' Hardware \nFnd ii keit Log... \nFS In mum4... \nTum Maintenance Mode On \n1'1 \nRename \nSTAR Edge Controler \n6TARe%CantroIe \ni \nSTAR Lida Contr0ler \nThe Search and Replace dialog box, as shown in Figure 6 on Page 43, appears. \n42 \nChapter! \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225973\n", "char_count": 1563}, {"efta_number": "EFTA01225932", "page_number": 42, "text_content": "Copying, Pasting, and Renaming Clusters and Controllers \nFigure 6: Search and Replace Dialog Box \nan. \n,49.1.2_41 \nOared berg coped Chafer-1 \nSearch For. \nReplace web \nOK \nCancel\nUsing Search and Replace \nPrior to the paste operation, the system provides the ability to replace a particular string in the names of objects \nbeing copied in the objects being pasted. Normally, the pasted objects will have the string -Copy [date-time] \nappended to the names. The Search and Replace dialog box allows you to replace the name. \n- \nAny string can be entered in the Search for field, and the string that it will replace in the Replace with \nfield. \n- \nObjects in conflict will have -Copy [date-time] appended to their names \n- \nPartial matches are considered. For example, if Door is entered in the search field and Dr in the replace \nfield with an object named FrontDoorReader then it is renamed as FrontDrReader. Selecting the Cancel \nbutton will abort the Paste operation. \n- \nIf both the Search for and Replace with fields are left blank, the object names are appended with -Copy \n[date-time\" \n- \nBoth Search for and Replace with fields must have a string entered or both fields must be blank. Leaving \none field blank is not allowed by the C•CURE 9000 software. \nNOTE \nIf the Copy & Paste operation is stopped before it completes, the entire operation is \ncanceled. \n2. Click OK. If you selected to search and replace, the system searches for the string and performs the replace while \ncopying the Cluster or Controller. \nThe Copying Status Window, shown in Figure 7 on Page 44, appears. The time required depends on the \ncomplexity of the Cluster or Controller. The time is 10 to 60 seconds for most Clusters. \nC•CURE 9000 Hardware Configuration Guide \nChapterl \n43 \nEFTA01225974\n", "char_count": 1780}, {"efta_number": "EFTA01225932", "page_number": 43, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \nFigure 7: Copying StatusWindow \n3. Click OK when the object is displayed as copied, as shown in Copying Status Window on Page 44. \nFigure 8: Copying Status Window - Complete \nWhen the copy is complete, shown side-by-side in Figure 9 on Page 45, all Readers, Inputs, Outputs, Doors, etc. \nhave -Copy [date-limel appended to their names. \n44 \nChapter! \nCCURE 9000 Hardware Configuration Guide \nEFTA01225975\n", "char_count": 462}, {"efta_number": "EFTA01225932", "page_number": 44, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \nFigure 9: Hardware Tree - Copy Complete \n• [3 CompanyName \n• ]1 Clusterl \n• \nCluster4 \n• n Edge1 \n• C] Edge1-Copy-2014-11-07-15-23-55 \n• rift Doors \n• \nDoors \n• \ndoorl \ndoor1-Copy-2014-11-07-15-23-55 \n• ED Inputs \n• it Inputs \n• \niSTAR Inputl-Edge1 \nL \niSTAR Input1-Edge1-Copy-2014-11-07-15-23-55 \n• \nTamper-Edge1 0 \nE Tamper-Edge1-Copy-2014-11-07-15-23-55 \n• CyY Outputs \n• \nOutputs \n• Output1-Edge1 \nOutput1-Edge1-Copy-2014-11-07-15-23-55 \n• Output2-Edge1 \n)10.) Output2-Edge1-Copy-2014-11-07-15-23-55 \n• La Readers \n• IA Readers \nN \nSTAR Reader1-Edge1 \nN \nSTAR Reader1-Edge1-Copy-2014-11-07-15-23-55 \nN \nCOM1-Edge1 \nN Egg COM1-Edge1-Copy-2014-11-07-15-23-55 \nN \nCOM2-Edge1 \nCOM2-Edge1-Copy-2014-11-07-15-23-55 \ngig COM3-Edge1 \nCOM3-Edge1-Copy-2014-11-07-15-23-55 \nagg GCMain-Edge1 \nN \nGCMain-Edge1-Copy-2014-11-07-15-23-55 \nCopying to a Mapped Drive or Another System Using a Flash Drive \nTo Copy a Cluster or a Controller to a Mapped Drive or Another System \n1. Right-click on the Cluster and select Copy to. \nC•CURE 9000 Hardware Configuration Guide \nChapter 1 \n45 \nEFTA01225976\n", "char_count": 1141}, {"efta_number": "EFTA01225932", "page_number": 45, "text_content": "Copying. Pasting, and Renaming Clusters and Contraliars \nFigure 10: Copy To Menu Selection \nDU \n• iSTAR Cluster \nvla • \nHardware Tree \nl \nSearch\n• Hardware \nN Ej Digital Certificates \nN \nFloor \n• IM CompanyName \n- Clusterl \n- Cluster2 \n- Cluster3 \n- CI \n- Clu \nClu \nUnassi \na \nEdit \nX \nDelete \nSet property \nSri \nAdd to group \nExport selection... \nFind in Audit Log... \nFind in Journal... \nTurn Maintenance Mode On \nCopy & Paste... \nCopy To... \nla Rename \nThe Export Window, shown in Figure 11 on Page 47, opens. \n2. Select the Flash Drive (or the mapped drive), and edit the He name if desired. \n48 \nChapter 1 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225977\n", "char_count": 667}, {"efta_number": "EFTA01225932", "page_number": 46, "text_content": "Copying, Pasting, and Renaming Clusters and Controllers \nFigure 11: Copyto Flash Drive \ner4 to XML or C \ntl r This PC r Removable Disk IF:) \nSearch Removable Disk Rl \nP \nOrganize \nNew folder \n- • \nName \nDate mocifted \nType \nThis PC \nm Dattop \nI \nboot \n6/24/2014 1226PM \nFile folder \nI \neh \n6/21/2014 1226PM \nFile folder \nDocuments \nI \nsources \n6/24/20141243 PM \nFile folder \n. Downloads \nMusic \n• \nJa support \n6/24/20141244 PM \nFile folder \n- pictures \nVideos \nLocal Disk (C:) \nISRemovable Disk\nDATAPART I (D \n}\nTechpubs (Warp \nFile name \n• \nSTAR Chaster Cluctra \nSave as type MIL lie Caen° \nHide FNders \nSave \nCancel \n3. Click Save. \nThe Copy To Status Window, shown in Figure 12 on Page 47, appears. \nFigure 12: Copy To StatusWindow \nto the file 'STAR Cluster C \noX \nBin \nLOP \n4. Click OK when the object is displayed as copied. \n5. Insert the Rash drive into the system where you want to copy the objects. Or, browse to the mapped drive on the \nsystem. \nIn this example, a simulated hardware folder is representing the other system. \n6. Right-click on the target folder in the new system's Hardware tree and select 'STAR Cluster>Paste From. \n7. Select the Flash Drive (or the mapped drive), the .xml file, and click Open as shown in Figure 13 on Page \n48Figure 13 on Page 48 \nC•CURE 9000 Hardware Configuration Guide \nChapter 1 \n47 \nEFTA01225978\n", "char_count": 1349}, {"efta_number": "EFTA01225932", "page_number": 47, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \nFigure 13: Paste From Window \nr II* PC r Removable Mine \nv C. \nSearch Removable Dick (DI \nATI \nOrganize - \nNew folder \nyes Techpubs OxilprlOISIsaredl \nName \n- EJI • \nDate modified \nL boot \n6/24,20141126 PM \n:U Dm PC \n6/24/20141L26 Ph• \n• Dattop \nj Documents \nSOU/CH \n6/24/20141L43 PM \nA. support \n6/24/20141L44 PM \n• Download: \n■ I/5)MR Chute. Clusteribri4 I \n11/20/2014 3415PM \nre Music \nj. Pictures \nj Videos \n♦V Local Disk (Cl/ \nDATAPARTI \ndi Removable Disk IL) \nY Techpubs f‘(lideelODShared) (Pd \nFreeiconfig fl‘bos2dtwood \\ TED \\ 2/10.Hal \nfide name \n• \niSTAR Citrate Cluster/am! \nXML Ides (•amp \nCanter \nThe Search and Replace dialog box appears. For information about Search and Replace, see Using Search and \nReplace on Page 43 \n8. Click OK in the Search and Replace dialog box. If you selected to search and replace, the system searches for the \nstring and performs the replace while copying the objects. \nThe Pasting Status Window, shown in Figure 14 on Page 48, appears. \nFigure 14: Pasting Status Window \n1ST \nCopyPaste-2014.11-20.1S•19.12xml \nOK \nPnat \nCo \n9. Click OK in the Pasting Status Window when the object is displayed as pasted. \nThe copied Cluster appears under the simulated folder in the Hardware tree on the system. \n48 \nChapter! \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225979\n", "char_count": 1369}, {"efta_number": "EFTA01225932", "page_number": 48, "text_content": "Copying, Pasting, and Renaming Clusters and Controllers \nCopying and Pasting from Partition to Partition \nTo Copy and Paste for a Partition to a Partition \n1. Right-click on the Cluster or Controller and select Copy To. \nThe Export Window appears. \n2. Select a folder on the system to save the .xml file, and click Save, as shown in Figure 15 on Page 49. \nFigure 15: EXp0etWindOW \nJr; 44 Local Disk (C) a foidte_for_copy_paste \nOrganize f• \nNew folder \n• i s Local Disk (C) \n,ja 9000 Projects \n0 k  American Dyne \no ja del \nI \ndes k \nCj foldufoccom \n0 J. HP Universal Pr \njs ICU \ninetpub \n0 j  KtyCodePacka \n0 \nLicenseGenerai \nMSOC ache \nFile named \nSave as type \nHide Folders \nName \nv <  \n'STAR Cluster Oustedma \nMI files Caen° \nSearch folder for. \nDate modified \nType \nNo dems match your search. \n3. Select the other partition where you want to copy the object. \n4. Right-click on the Hardware folder in the partition and select iSTAR Cluster>Paste from, as shown in Figure 16 \non Page 50Figure 16 on Page 50 \nC•CURE 9000 Hardware Configuration Guide \nChapter 1 \n49 \nEFTA01225980\n", "char_count": 1082}, {"efta_number": "EFTA01225932", "page_number": 49, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \nFigure 16: Partition Selection \nOperator Help \nServer Options \ni\ngen Obiect Partition: \noffice A_partition \nlit \nHardware Folder \nHardware Tree \n• Hardware \nLi Digital Certificates \nFloor \n• Li CompanyName \nClusterl \nClsku2 \nCluster3 \nay Clustet4 \nay Ouster6 \nausierScoprke-tildp-C \n~\nmo dkoAfter-. \nPJ simulate_anc yt. \nEdit \nLi Unassigned X Delete \nra, \nExport selection... \nFind in Audit log... \nFind in Journal... \nV C \nSearch \nA Options • Tools \n4,^deo \ndik Hardware \nri\nP AnNtit and Tames \nThe Paste From Window appears. \n5. Browse to the .xml file you saved on the system. \n6. Select the .xml file and click Open. \napC Comm Port \nPartttba xL \nViews • Filter r e\nDrag columns b grot \nDefault \nNan \n• \nSTAR Cluster \nNew \nPaste From—\nThe Search and Replace dialog box appears. For information about Search and Replace, see Using Search and \nReplace on Page 43 \n7. Click OK in the Search and Replace dialog box. If you selected to search and replace, the system searches for the \nstring and performs the replace while copying the objects. \nThe Pasting Status Window appears. \n8. Click OK in the Pasting Status Window when the object is displayed as pasted. \nThe copied object appears in the Partition. \n50 \nChapter 1 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225981\n", "char_count": 1333}, {"efta_number": "EFTA01225932", "page_number": 50, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \nRenaming Clusters and Controllers \nIf you did nut use the Search and Replace option in the Copy & Paste procedure, you can use the Rename selection \non the Context menu. \nThe following procedure renames -Copy Ida te-timej that was appended to the end of a Cluster and its objects during \nCopy & Paste to -Bldg-C. \nTo Rename Clusters and Controllers \nI . Right-click on the object and select Rename, as shown in Figure 1 on Page 51. \nFigure 1: RenameCluster \nCluster4 \nCluster6 \n• \na Edit \nX \nDelete \n• \nSet property \nj \nAdd to group \nt. \nExport selection... \nFind in Audit Log... \nFind in Journal... \nTurn Maintenance Mode On \nCopy & Paste... \nCopy To... \n7-47 \n7 \n• \nRename \niSTAR Edge Controller \n► \niSTAR eX Controller \n► \niSTAR Ukra Controller \n► \n0-12-\nItra6-\nItra6-\nItra6-\nItra6-\nCop \nOutputl-iSTAR Ultra ACM1-Ultra6-Copy \nThe Renaming dialog box appears. \n2. Click Search and Replace to open the Search and Replace dialog box, as shown in Figure 2 on Page 52. \nC•CURE 9000 Hardware Configuration Guide \nChapter 1 \n51 \nEFTA01225982\n", "char_count": 1095}, {"efta_number": "EFTA01225932", "page_number": 51, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \nFigure 2: Cluster Renaming \n(STAR Cluster Renaming - Cluster6-Copy-2014-11 -20-12-57-4 \nI \na Save and Close \nName \nCloae4-Carg-2014-11- \n-5747 \niepr40141140424747 \nSwab \nRaplaaelt 46;4 \ng, um, am \nw inn tango T•ires \nac \n3. \n4. \n5. \nEnter the \nOptional \n• Click \n• Click \nClick OK. \nAn informational \nnew name in the Replace with field (in this example it's -Bldg-C). \nselections \non the Match case check box to match the case entered. \nin the Ignore Trigger Targets check box to ignore Trigger target events. \nUse caution if renaming original Events. The Events may be linked to other objects. Use \nthe Show Association feature to determine if they are. See the C•CURE 9000 Getting \nStarted Guide for information about using Show Association. \ndialog box appears displaying all the objects that were modified with the new name. \n52 \nChapter 1 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225983\n", "char_count": 957}, {"efta_number": "EFTA01225932", "page_number": 52, "text_content": "Copying. Pasting. and Renaming Clusters and Controllers \nFigure 3: Rename Results \nSearch and Replace \nX  1 \n0\n The following objects were modified: \n(1) iStarController. \n(1) iStarGCBoard. \n(5) iStarInput. \n(3) iStarComBoard. \n(2) iStarAperioHubBoard. \n(1) iSTARAperioReader. \n(1) iStarUltraACMBoard. \n(1) iStarinputBoard. \n(1) iStarOutputBoard. \n(2) iStarReader. \n(4) Output. \n(1) iStarDoor. \n(1) Elevator. \nOK \n6. Click OK. \n7. Verify that the rename changes are complete. Click on the tabs in Renaming dialog box. \nNOTE \nBecause Ignore Trigger Targets was selected in the Search and Replace dialog box, the \noriginal Trigger Target Events were not renamed, but another copy of the Events exist \nwith the -Copy [date-lime] appended to the end. \nRename Results \nThe next series of graphics illustrate the effect of the Rename operation. \nFigure 4: Controller Tab and Input Tab \nNMI \nClateaStoPytad¢C \nUlnE•Bklg-C \nGabran6-Bit< \n• \nINCO011irberrEalg-C \n▪ \n13/4.614RS 185 Pon laa6-131:1,C \n• \ni \nC0182-LbseG-Eldg-C \nI3/461A5 CZ Pat 24.1frafrelcirC \n• \ni \nSTAR Ur, ACMI•barrEelgt \nI. STAR Dace Patl.STAR UlnACMI-Ulent6444-C \nMI STARInn Sown-STAR Dew* PatlISTAR Ur, ACMI•AraGalg-C \nOM STAR Gaut SaardhSTAR Demos F1/441.67AR lib% ACM I•Utre.-81:1}C \nni Matson GCMarvitraGa:19-C \nTtope•iitnitachre \nMi Motes on COtli.USBIOL \nivies cellublaS 4185 Pon 1-libabillS}C \nhiPiats OA C01121.26-816K \n• \nkW. ced401.0.5 485 Poi 241•1441,44 \nA \nIII Urea CV1 STAR Ulna ACM1krise64.4-C \nLt STAR InP41.61014 Ube ACIAlandad9C \nSTAR InPANSAA Ube ACM14.**640{ \na STAR 10043-41AR We ACM witra6404 \na STAR Ime441014 lb. XM14111,46-el®-C \n▪ \nInOS cm STAR Urn Porll•STAIR Via ACIII4Ate6-B1094 \n▪ \nWPM ce STAR leout Beardl-g5174‘ Demo Pall-ISTAR W. ACIII-Ubtek4C \n▪ \nce STAR CUM sachnoa (*ice PerthS-TAR  Uln ACIII4ftfre6a9C \nC•CURE 9000 Hardware Configuration Guide \nChapter 1 \n53 \nEFTA01225984\n", "char_count": 1870}, {"efta_number": "EFTA01225932", "page_number": 53, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \nFigure 5: Outputs Taband Readers Tab \nConvokes l Inpuni  Outputs \nWas on GO4on-Ulta6-810g-C \na \nCuoas m comtasSeme-C \nIM Damn on HublaS 485 Pon 1110444:4C \nOaos on C0112-Ultia61314-C \nIn Q.Von on Hubl-R5 4E6 Pon 2-Uta6-Eldg{ \n• \nNab* \non STAR UNta ACMI-Vitnealo-C \n0.44•14$TAR \nACM14.4016-EWC \nt \n04p424STAR IN* ACI4I-UtaGE44-C \nt OupasEkSTAR Utra ACM14.11webairC \n004,4104STAR IIee ACM1-1.1ba6-Eldg-C \nI. Das* on STAR Dow. PcollISTAR Se A041-1.0146-140g-C \nOa* on STAR Oita S000lliSTAA DOW* nixtuSTARI.40 A0/1•Ukc•64:309-C \nReeds, I Dora Bova° I Trelno I \nI Caftan \nDOOM Ebro,. \nit Readers on GCMon-UNIa6-B1:1K \ne Ratans on CC.41-Utre6-81dg-C \n• \nIQ Radon on 1-1.011:$ 485 PC•114/4/46-810O{ \nI STAR Agno R•Eloil+kt.1425 485 Pat 1-UW41-146K \nReaders on 03142-Utro6434-C \nIII Realms on lit I-RS 485 Pat 2411n6-B1AK \n• \nMI Rados on WARM. AC141-L1n5-81do-C \nSTAR Reedr1STARVbe ACM14.1tra6-8142-C \n• \na \nRadon on STAR Dna Poen .STAR Den ACAII-Uloa6462-C \nSTAR ReaderneSTAR Donne Pont STAR Uba 4041-UtreGairC \nFigure 6: Doors Taband Elevators Tab \n&OS= I Mow I Was I Rookies Don lEknoloto frown \n• \nti Donn*, UlOa6-162C \n• \nGI ckoiG416pC \nIrtand Roeder STAR Anew Rooderl-HublaS 485 Pon 1-UOn6.14:loC \na \nDow Sava Wooed STAR wsd4TAR Mrs AC/11•Ultadg-C \na \nDoor Lock Roby QµWiWSTAR Ube ACM1-1.16a6-146,C \nCatalan I Int I Oulptto I Reads, I Dom \n• \naerators on lAsa6-Elth,C \n• \nla aleton4-1,O24 \nInband Roadie STAR Roadul -STAR Is. ACMnUbsialcipC \nFigure 7: Triggers Tab \nCcattolsrs hrouts I OutPitsj Readers I-Doors IElevatca ing\nrn\ness\n \nSource \nPieleny \nValue \nAction \nUtra6-Bldg-C OnlmeStatus \nOffline \nAavateEve \ncootraler_nactive-Coor2014-11-20-12-57-t7) \ndoc.6-8Idg•C AlarmStateStatus Forced \nAcbvateEve \nDosr_foroed-Copt2014.11.20-12-57-47 \ndocr6-Eklg-C AlarmStateStatus Ask/Open AdrvateEve \nDoor_Keld-Copy-2014.11.20-12.57.47 \nDead \nTrigger Target Events \nNotice that the original Trigger Target Events were not renamed, but another copy of t\n... [truncated, 2433 chars — for the full page use /api/corpus/document/EFTA01225932/53 or ?id=EFTA01225932&page=53]", "char_count": 2433}, {"efta_number": "EFTA01225932", "page_number": 54, "text_content": "Copying, Pasting, and Renaming Clusters and Controllers \nFigure 8: Trigger Targets \nBattery Low Journal Trigger Event \nThe default \nInactive \nBattery Low \nJournal Trigger \nevent \nMned \nIntrusion Zone Error Journal Trigger \nEvent \nThe default \nInactive \nIntrusion Zone \nError Journal \nTrigger event \nMned \nTamper \nInactive \nMned \nDoor_Held \nInactive \nArmed \nDoor forced \nInactive \nAimed \ncontroller_ inactive \nInactive \nArmed \ncontroller_inactive-Copy-2014-11-20- \n12-57-47 \nInactive \nArmed \nDoor forced-Copy-2014-11-20-12-57- \n47 \nInactive \nMned \nDoor_Held-Copy-2014-11-20-12-57- \n47 \nInactive \nMned \nC•CURE 9000 Hardware Configuration Guide \nChapter 1 \nSS \nEFTA01225986\n", "char_count": 671}, {"efta_number": "EFTA01225932", "page_number": 55, "text_content": "Copying. Pasting, and Renaming Clusters and Controllers \n56 \nChapter 1 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225987\n", "char_count": 127}, {"efta_number": "EFTA01225932", "page_number": 56, "text_content": "2 \nMaintenance Mode \nThis chapter describes how to configure and use Maintenance Mode. \nIn this chapter: \nMaintenance Mode Dialog Box \n58 \nMaintenance Mode Overview \n59 \nMaintenance Mode Objects Supported \n60 \nMaintenance Mode Configuration Tasks  \n61 \nC•CURE 9000 Hardware Configuration Guide \nChapter 2 \n57 \nEFTA01225988\n", "char_count": 323}, {"efta_number": "EFTA01225932", "page_number": 57, "text_content": "Maintenance Mode Dialog Box \nMaintenance Mode Dialog Box \nThe Maintenance Mode dialog box, shown in Figure 1 on Page 58, opens when Maintenance Mode \nis selected or deselected. \nSee the following for more information: \n■ Maintenance Mode Overview on Page 59 \n■ Maintenance Mode Objects Supported on Page 60 \n■ Maintenance Mode Configuration Tasks on Page 61 \nFigure 1: Maintenance Mode Dialog Box (Cluster) \nid Saw aro, Owe \nCheek to otgects b te :laced m Martenrce Mae \nUntied' P. atom to be Veen o CM:ffittaYee Mc* \nSOW al \n0weint NI \n?STAR Edge \np \nGPew \ng •Poem Felum-STAREdoeil \np \nTeneg4TAR Ethpe \np \n&tonal Baby LconSTAR Edges \nplIEFAJ MenenSTAR Ete tl \np \n6TC.R hvANSTAR Edge SI \np \nosef.se. \nP \n.STAR ires3-STAP (*en \n• lajamikewistait UP 11\ng \nFA, Reby CasbokSTAII Edge tt \nr.7 \nFN Had , KertSTAR Edge II \n• \nkernel Peery CaA.STAREcte gl \np \ncvo.i.sTAR Edossi \nliettp424STAR Edge tl \n:J \n58 \nChapter 2 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225989\n", "char_count": 968}, {"efta_number": "EFTA01225932", "page_number": 58, "text_content": "Maintenance Mode Overview \nMaintenance Mode Overview \nMaintenance Mode is used to limit information about an object displayed on the Monitoring Station. \nMaintenance Mode only affects what is reported at the Monitoring Station. \nSome examples for using Maintenance Mode: \n■ To Not display information about: \n• Parts of the system being installed by an integrator \n• Hardware being serviced, requiring maintenance, or being tested. \n■ To only monitor information about hardware being serviced, requiring maintenance, or being \ntested. \n■ To view information about all objects, including those tagged Maintenance Mode. \nPlacing an object into Maintenance Mode does not prevent actions from occurring. For example, if \nan event assigned to an intrusion zone in Maintenance Mode activates an output that turns on the \nbuilding-wide evacuation alarm, the activation of the output will still occur. \nArming and disarming of inputs and events do not affect what is reported when the object is \nactivated. In other words, arming of an event by an event assigned to a Maintenance Mode intrusion \nzone will be reported as activity. \nMaintenance Mode is only reported in Journal messages when an object is tagged Maintenance \nMode. When the object is taken out of Maintenance Mode it is not reported in a Journal message. \nOperator Privilege and Application Layout Filtering assignments determine whether or not an object \nin Maintenance Mode is viewable as being in Maintenance Mode on the Monitoring Station. Only \nMonitoring Station operators with the correct privilege and Application Layout Filtering can view \nobjects in Maintenance Mode. \nSee the following for more information: \n■ Maintenance Mode Objects Supported on Page 60 \n■ Maintenance Mode Configuration Tasks on Page 61 \nC•CURE 9000 Hardware Configuration Guide \nChapter 2 \n59 \nEFTA01225990\n", "char_count": 1847}, {"efta_number": "EFTA01225932", "page_number": 59, "text_content": "Maintenance Mode Objects Supported \nMaintenance Mode Objects Supported \nThe following objects are supported in Maintenance Mode: \n■ apC Comm Ports \n■ apC Controllers \n■ apC Add-On Boards \n■ apC 132 Input Boards \n■ apC 18 Input Boards \n■ apC R48 Output Boards \n■ apC R8 Output Boards \n■ apC Inputs \n■ apC Readers \n■ apC Doors \n■ Areas \n■ C•CURE Mobile \n■ Elevators \n80 \nChapter 2 \n■ Events \n■ Floors \n■ Intrusion Zones \n■ Keypad Commands \n■ iSTAR Clusters \n■ iSTAR Controllers \n■ iSTAR Doors \n■ iSTAR Inputs \n■ iSTAR Readers \n■ iSTAR Aperio Hub \n■ iSTAR Aperio Readers \n■ iSTAR Aperio Doors \n■ iSTAR Comm Ports \n■ iSTAR PIM-185 Readers \n■ iSTAR Schlage Readers \n■ iSTAR Schlage Doors \n■ iSTAR Device Ports \n■ iSTAR ACM Boards \n■ iSTAR GCM Boards \n■ iSTAR Input Boards \n■ iSTAR Output Boards \n■ iSTAR Ultra ACMs \n■ Outputs \n■ Star Coupler Ministar \n■ Star Coupler Star \n■ Star Coupler WPSC \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225991\n", "char_count": 944}, {"efta_number": "EFTA01225932", "page_number": 60, "text_content": "Maintenance Mode Configuration Tasks \nMaintenance Mode Configuration Tasks \nOperator privileges and application layout assignments must be configured to use, view, or filter \nobjects in maintenance mode. \nThe following tasks are described: \n■ Configuring Privileges to Turn Maintenance Mode On and Off on Page 61 \n■ Configuring the Application Layout for Maintenance Mode Filtering on Page 62 \n■ Turning Maintenance Mode On and Off on Page 62 \n■ Viewing Maintenance Mode Objects in the Dynamic View on Page 65 \n■ Filtering Partitions and Maintenance Mode Objects in the Dynamic View on Page 65 \nConfiguring Privileges to Turn Maintenance Mode On and Off \nOnly operators who have the Turn Maintenance Mode On and/or Turn Maintenance Mode Off \nprivilege assigned to them can put an object into Maintenance Mode and take an object out of \nMaintenance Mode. \nThe following procedure describes how to configure the privilege to include Maintenance Mode. \nTo Configure the Privilege \n1. Click the Configuration pane. \n2. Select Privilege from the Configuration drop-down menu to open the Privileges dialog box. \n3. Click the Defaults tab. \n4. Under Classes, click an object to view the permissions for that object. \n5. Scroll down to locate Turn Maintenance Mode On and Turn Maintenance Mode Off. \n6. Click in the Grant column next to Turn Maintenance Mode On and/or Turn Maintenance \nMode Off to enable the permission(s) for this Privilege configuration. \n7. See the C•CURE 9000 Software Configuration Guide for complete Privilege configuration \ninformation. \n8. Click Save and Close when done with the configuration. \nC•CURE 9000 Hardware Configuration Guide \nChapter 2 \n81 \nEFTA01225992\n", "char_count": 1684}, {"efta_number": "EFTA01225932", "page_number": 61, "text_content": "Maintenance Mode Configuration Tasks \nConfiguring the Application Layout for Maintenance Mode Filtering \nApplication layouts can be configured to allow operators to filter objects in Maintenance Mode in the \nMonitoring Station and the Administration application Dynamic Views. \nThe following procedure describes how to configure the application layout to allow Maintenance \nMode filtering. The Operator must have the correct privileges to use filtering. See Configuring \nPrivileges to Turn Maintenance Mode On and Off on Page 61. \nSee the C• CURE 9000 Data Views Guide for more information about configuring the application \nlayout. \nTo Configure Maintenance Mode Filtering in the Application Layout \n1. Click the Data Views pane. \n2. Select Application Layout from the Data Views drop-down menu. \n3. Edit or add an Application Layout. \n4. Click the Filtering tab. \n5. See the C•CURE 9000 Data Views Guide \"Application Layout chapter\" for information about the \nFiltering tab fields. \n6. Click Save and Close when done with the configuration. \nTurning Maintenance Mode On and Off \nNOTE \nTo use Maintenance Mode, operators must have the correct privilege permissions \nassigned to them. See Configuring Privileges to Turn Maintenance Mode On and Off \non Page 61 \nThere are several ways to turn Maintenance Mode on and off: \n■ Right-click on an object in the object tree and select Turn Maintenance Mode On or Turn \nMaintenance Mode Off. \n■ Right-click on an object in the Dynamic View and select Turn Maintenance Mode On or Turn \nMaintenance Mode Off. \n■ Click in the Maintenance Mode column check box in the Dynamic View. \n82 \nChapter 2 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225993\n", "char_count": 1692}, {"efta_number": "EFTA01225932", "page_number": 62, "text_content": "Maintenance Mode Configuration Tasks \n■ Open the object editor and select the Maintenance Mode check box. Deselect the check box to \nturn it off. \niSTAR Cluster \nTo Put a Cluster Into Maintenance Mode \n1. Click the Hardware pane. \n2. Locate the Ouster in the Hardware nee, or in the Dynamic View. \n3. Right-click on the Ouster name and select Turn Maintenance Mode On to open the \nMaintenance Mode dialog box. \n4. The Maintenance Mode dialog box opens with the Ouster and all of its components/objects \nselected. \n5. Click Save and Close. \nTo Take a Cluster Out of Maintenance Mode \n1. Click the Hardware pane. \n2. In the Hardware tree, or in the Dynamic View, right-click on the Ouster and select Turn \nMaintenance Mode Off to open the Maintenance Mode dialog box. \n3. Click Deselect All. \n4. Click Save and Close. \nTo Add an iSTAR to a Cluster in Maintenance Mode \n1. Right-click on the Ouster name and select Turn Maintenance Mode Off to open the \nMaintenance Mode dialog box. \n2. Select the check box next to the iSTAR name. \n3. Click Save and Close. \nC•CURE 9000 Hardware Configuration Guide \nChapter 2 \n63 \nEFTA01225994\n", "char_count": 1126}, {"efta_number": "EFTA01225932", "page_number": 63, "text_content": "Maintenance Mode Configuration Tasks \niSTAR Controller or apC Controller \nTo Put iSTAR or apC Components/Objects into Maintenance Mode \n1. Click the Hardware pane. \n2. Locate the controller in the Hardware tree or in the Dynamic View. \n3. Right-click on the iSTAR or apC, controller and select Turn Maintenance Mode On to open the \nMaintenance Mode dialog box. \n4. Click the iSTAR or apC, controller name, or click Select All to select all components and objects \nbelonging to the controller. Or, click on the separate components and/objects that you want to \nput into Maintenance Mode. \n5. Click Save and Close. \nTaking an iSTAR or apC Controller Out of Maintenance Mode. \nTo Take an iSTAR or apC Components/Objects Out of Maintenance Mode \n1. Click the Hardware pane. \n2. In the Hardware tree, click on the Cluster where the iSTAR, or apC, controller belongs. \n3. Right-click on the controller and select Turn Maintenance Mode Off to open the Maintenance \nMode dialog box. \n4. Deselect the controller, components and/or objects. \n5. Click Save and Close. \nPutting Objects (Doors, Readers, Events, Elevators, etc.) into Maintenance Mode \nTo Put Objects into Maintenance Mode \n1. Click the Hardware pane. \n2. Locate the object, right-click on it and select Turn Maintenance Mode On. \nTo turn off Maintenance Mode, right-click on the object and select Turn Maintenance Mode Off. \n64 \nChapter 2 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225995\n", "char_count": 1449}, {"efta_number": "EFTA01225932", "page_number": 64, "text_content": "Maintenance Mo0e Configuration Tasks \nViewing Maintenance Mode Objects in the Dynamic View \nThe Dynamic View can be customized to display objects that are in Maintenance Mode. See the \nC• CURE 9000 Data Views User Guide for information about adding the Maintenance Mode column to \nthe Dynamic View. \nFiltering Partitions and Maintenance Mode Objects in the Dynamic View \nApplication Layout Filtering configuration allows Operators to filter a Dynamic View to show only \nselected partitions and/or to view objects that are in Maintenance Mode in the Administration \napplication and in the Monitoring Station. Only Operators with the correct privilege and Application \nLayout assigned to them are allowed to use filtering. \nSee Configuring Privileges to Turn Maintenance Mode On and Off on Page 61 and Configuring the \nApplication Layout for Maintenance Mode Filtering on Page 62 \nC•CURE 9000 Hardware Configuration Guide \nChapter 2 \n65 \nEFTA01225996\n", "char_count": 949}, {"efta_number": "EFTA01225932", "page_number": 65, "text_content": "Maintenance Mode Configuration Tasks \n66 \nChapter 2 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225997\n", "char_count": 108}, {"efta_number": "EFTA01225932", "page_number": 66, "text_content": "3 \nConfiguring Dialup \nThis chapter explains how to configure dial up for use with the iSTAR Pro and the iSTAR Ultra SE (Pro Mode only). \nIn this chapter \niSTAR Dialup \n68 \niSTAR Dialup Configuration Sequence \n69 \nConfiguring the iSTAR Comm Port \n70 \nConfiguring the Host Modem \n73 \nCreating a Cluster for Dialup \n76 \nC•CURE 9000 Hardware Configuration Guide \nChapter 3 \n67 \nEFTA01225998\n", "char_count": 388}, {"efta_number": "EFTA01225932", "page_number": 67, "text_content": "STAR Dialup \niSTAR Dialup \nDialup enables you to connect the C•CURE 9000 to the iSTAR Pro (with a 56K PCMCIA modem card) and \niSTAR Ultra SE (in Pro Mode with a USB-based modem card) controllers at remote locations using modems and \nstandard telephone lines. \nThe C•CURE host and iSTAR phone line/modem connection is based primarily on Windows standard telephony \ncommunications and Routing and Remote Access Service (RRAS). \n■ The lowest level of the communications, which deals with modem states, is handled by the Microsoft Windows \nTelephony Application Programming Interface (TAN). TAPI supports the use of any type of standard modem on \nthe host. \n■ The higher level of the communications, which deals with the transmission of C•CURE relevant data, is \nhandled by Microsoft RRAS. RRAS treats dial-up connections as if they were network connections. Consequently, \nthe C•CURE host views the connection established between the iSTAR and itself via a phone line and modem as \nany other network connection. \n■ Serial port-based dialup modems and USB port based modems are supported. \nDialup Limitations \n■ Dialup is only supported on Windows Server 2008 R2, 2012, and 2012 R2. \n■ Dialup is not supported in configurations using redundancy. \n■ Dialup can be used only as the primary connection method or the secondary communication method, not as \nboth. \nExample: \n- \nDialup is used as the primary communication method and there is no secondary communication \nmethod. \n- \nTCP/IP is used as the primary communication method and Dialup is used as the secondary \ncommunication method. \n■ A cluster used for dialup can only contain one iSTAR controller. \n■ Fast Personnel download is not supported. \n■ Dialup is not supported on a separate RRAS server. \n68 \nChapter 3 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01225999\n", "char_count": 1821}, {"efta_number": "EFTA01225932", "page_number": 68, "text_content": "STAR Dialup Configuration Sequence \niSTAR Dialup Configuration Sequence \nNOTE \nThe configuration information in this section only applies to the C•CURE 9000, and assumes that \nyou completed the operating system setup as described in the Operating System Setup for Dial up \nGuide. This guide is located in the C•CURE 9000 Installation DVD English \\ Manuals folder. \nThe dialup configuration sequence is described in Table 3 on Page 69. \nTable 3: STAR Dialup Configuration Sequence \nStep \nTask \nSee... \n1 \nConfigure the Comm ports to which the host modems are attached in C•CURE 9000 \nusing the STAR Comm Port Editor. \nConfiguring the STAR Comm \nPort on Page 70 \n2 \nConfigure the host modems in C•CURE 9000 using the Host Modem editor. \nConfiguring the Host Modem \non Page 73 \n3 \nCreate an STAR Cluster. Click the Dlalup tab to configure dialup settings. \nCreating a Cluster for Dialup \non Page 76 \n4 \nConfigure the STAR controller. \nSTAR Pro Controller Editor \non Page 137 \n5 \n1. Open the STAR Cluster you created in Step 3. \n2. Click the Communications tab. \n3. Add the controller you configured in Step 4. \n4. Configure the communication with the host. \nConfiguring iSTAR \nClusters on Page 87 \n6 \nConfigure/Grant Privileges for the STAR Controller dialup permissions using the \nPrivilege editor. \nC•CURE 9000 Software \nConfiguration Guide \n7 \nConfigure Events to download to the controller and select the dial up conditions using the \nEvent editor. \nSelect the Dialup settings from the Event Editor General tab. \nC•CURE 9000 Software \nConfiguration Guide \n8 \nConfigure the System Variables Dlalup settings (dial-up user name. password. domain. \ngrace seconds. cycle seconds) to use RRAS. \nC•CURE 9000 System \nMaintenance Guide \nC•CURE 9000 Hardware Configuration Guide \nChapter 3 \n69 \nEFTA01226000\n", "char_count": 1799}, {"efta_number": "EFTA01225932", "page_number": 69, "text_content": "Configuring the STAR Comm Port \nConfiguring the iSTAR Comm Port \nUse the iSTAR Comm Port dialog box, shown in Figure 17 on Page 70, to communicate with a serial port connection. \nSee Table 4 on Page 70 for descriptions of the fields on the Comm Port editor General Tab. \nNOTE \n• The iSTAR Comm Port only supports a serial port. \n• Triggers are not supported. \nFigure 17: STAR Comm Port Editor Dialog Box \nName \nDesamtion \nA \nr &Sod \nr- Simenance Mode \nGeneral I Grows I Ste maps I \n—Communications Type \n6' Sent{ Pat \nPetition. Defect \nPat Settings \nPon Timeout Delay Time (1110 sec) \nQuist) Pon. \nlo \nii\nICOM2 \nTable 4: STAR Comm Port Field Definitions \nField \nDescription \nName \nThe Name field will reflect the Comm Port you select. \nDescription \nEnter a textualcomment about the controller, such as its location or purpose. This text is for information onty. \n70 \nChapter 3 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226001\n", "char_count": 933}, {"efta_number": "EFTA01225932", "page_number": 70, "text_content": "Configuring the STAR Comm Port \nSTAR Comm Port Field Definitions (continued) \nField \nDescription \nEnabled \nThis setting determines whether or not the STAR Comm Port is able to providecommunication between the STAR Controller \nand the C•CURE 9000 Server. Select Enabled to set the Comm Port online. To take the Comm Port offline, clear the Enabled \nselection. \nIf the STAR Comm Port is currentty in use by STAR controllers, you must disable all the controllers before you attempt to take the \nComm Port offline. If any STAR controllers are enabled when you attempt to take the STAR Comm Port offline, an error \nmessage isdisplayed -'Port cannot be disabled with enabled controllers. Please disable controllers first. When the controllers are \nre-enabled they willdo a full personneldownload' \nThe message explains that when you re-enable the STAR Comm Port and then re-enable the STAR controllers, each controller \nwill perform a full personnel download. \nNOTE: Fast Personnel Download is not supported. \nMaintenance \nMode \nClick to put the STAR Comm Port into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nPartition \nThis read-onty field identifies the Partition. \nCommunica ions Type \nSerial Port \nSelected bydefault. \nPort Settings \nPort Timeout \nDelay Time \n(1/10 sec) \nThe Port Tlmoout Delay Time is the extra interval that the host waits for a response from the STAR panel after sending a \nmessage to the panel. If the host does not receive a response in the specified time, the host re-transmits the message or declares \na communications failure. This field allows you to set the timeout delay for all panels that use a specific port. \nSoftware House recommends that you set this period to 20 (2 seconds). However, d you require additionaldelay time because \nSTAR controllers run on a Digiboard, Equinox board, or over a network, you may need to increase this value. Keep this value as \nsmall as possible, or system performance may be affected. If your panelgoes into\n... [truncated, 2959 chars — for the full page use /api/corpus/document/EFTA01225932/70 or ?id=EFTA01225932&page=70]", "char_count": 2959}, {"efta_number": "EFTA01225932", "page_number": 71, "text_content": "Configuring the ISTAR Comm Port \n5. You can set a Port Timeout Delay Time in tenths of a second units by entering it in the field or by using the \nup/down mows. \n6. Select the Comm Port from the drop-down list. \n7. Select the Enabled check box to put the Comm Port online after you have completed the configuration procedure. \n8. Click Save and Close. \n9. Go to Configuring the Host Modem on Page 73. \niSTAR Comm Port State Images Tab \nThe State images tab, shown in Figure 1 on Page 72, provides a means to change the default images used to indicate \ncommunication port states. These images appear on the Monitoring Station and change according to the state of the \nobject that they represent. \nFigure 1: ISTAR Comm Port State Images Tab \nTo Change a State Image \n1. Double-click the existing image. A Windows Open dialog box appears allowing you to browse for a folder in \nwhich you have placed replacement images. \n2. When you locate the replacement image, select it and click Open to add it to the image listing. \n3. If you are done editing the iSTAR Comm Port, click Save and Close to save the Comm Port's configuration. \nAlternatively, if you want to save the Comm Port and create a new one, click Save and New. The Comm Port \nEditor remains open to allow you to create a new Comm Port. \nTo Restore to the Default Image \n■ Right-click on the new image and select Restore Default \n72 \nChapter 3 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226003\n", "char_count": 1456}, {"efta_number": "EFTA01225932", "page_number": 72, "text_content": "Configuring the Host Modem \nConfiguring the Host Modem \nThe Host Modem dialog box, shown in Figure 18 on Page 73, lets you specify the communication port, the dialing \ndirection, and the phone numbers the i51'AR Pro/SE Pro Mode can use. \nNOTE \nHyphens, parentheses, and spaces are not allowed in phone numbers. \nThe Host Modem dialog box definitions are described in Table 5 on Page 73. \nFigure 18: Host Modem Dialog Box \na Mom Modem \n0,11 In Modem \n\"Raven:1Om 'ine end Net \nan = \nencrao,\nEPObbi \n. MINIIMICCO Mg* \nGerd \nCorny-air Pen \nfcm C0M2 \nDreeta \nOM Rio* \nEl PM \nP/ma40Wmt \nFlute vein ea moth - roan \n•!. add P.M. ? • &mem \nDam,\nTable 5: Host Modem Dialog Box Definitions \nField \nDescription \nName \nEnter a unique name for the host modem configuration. \nDescription \nA textua I comment for information only. \nEnabled \nSelect Enabled to set the host modem online. To take the host modem offline, clear the \nEnabled selection. \nC•CURE 9000 Hardware Configuration Guide \nChapter 3 \n73 \nEFTA01226004\n", "char_count": 1003}, {"efta_number": "EFTA01225932", "page_number": 73, "text_content": "Configuring the Host Modem \nTable 5: Host Modem Dialog Box Definitions (continued) \nField \nDescription \nMaintenance Mode \nClick to put the STAR Comm Port into Maintenance Mode. See Chapter 2: Maintenance \nMode for more information. \nPartition \nThis read-only field dentifies the Partition in which this Controller resdes. \nCommunication Port \nClick 0 \nto open the Name Selection dialog to select the STAR Comm Port. \nNOTE: The iSTAR communication ports must already be configured. See Configuring \nthe STAR Comm Port on Page 70 \nDirection \nDial out only \nSelect this option to specify that this modem is used onty for dialing out to \npanelstoontrollers \nDial In only \nSelect this option to specify that this modem is used only for dialing into the host. \nDial In and Dial out \nSelect this option to specify that this modem is used for both incoming and outgoing \ncalls. \nPhone numbers that \nreach this modem \nDisplays the list of phone numbers that reach this host modem. Use the buttons to the \nright of the list to modify the numbers in the list. \n• The phone number can be up to 35 characters long. \n• Hyphens. parentheses, and spaces are not allowed in phone numbers. \n• If Dial out only is selected in the Direction box. this box and the Add Dial In. and \nRemove buttons are unavailable. \nTo Configure Modems for the Host \n1. Ensure that the iSTAR communication ports are configured. See Configuring the iSTAR Comm Port on Page 70. \n2. Open the C•CURE 9000 Administration Hardware Pane, select the Hardware Folder in which you want the \niSTAR modem configuration to reside. \n3. Right-click the folder to display the context menu, click Host Modem, and then click New. \nThe Host Modem dialog box, shown in Figure 18 on Page 73, appears. \n4. Enter a unique Host Modem name in the Name field (required). \n5. Enter a textual description (optional) of the Host Modem configuration in the Description field. \n6. Click Ei in the Port field to open the Name selection dialog box and click the iSTAR Comm\n... [truncated, 2391 chars — for the full page use /api/corpus/document/EFTA01225932/73 or ?id=EFTA01225932&page=73]", "char_count": 2391}, {"efta_number": "EFTA01225932", "page_number": 74, "text_content": "Configuring the Host Modem \n9. Click Enabled to put the Host Modem online. \n10. Optional. Click on the State Images tab to change the default images used to indicate communication port states \non the Monitoring Station. \n11. Click Save and Close. \n12. Go to Creating a Cluster for Dialup on Page 76. \nC•CURE 9000 Hardware Configuration Guide \nChapter 3 \n75 \nEFTA01226006\n", "char_count": 371}, {"efta_number": "EFTA01225932", "page_number": 75, "text_content": "Creating a Cluster for Dialup \nCreating a Cluster for Dialup \nThis section describes how to create a cluster to use dial-up on the iSTAR Pro or Ultra SE Pro Mode controller. \nThe Dialup Configuration tab in the iSTAR Cluster Editor dialog box, shown in Figure 2 on Page 76, lets you select \npre-configured host modems and specify other dial-up configurations. \nThis tab is only available for unencrypted clusters and for use with the iSTAR Pro or iSTAR Ultra SE in Pro Mode. \nNOTE \n• You can only have one controller in a cluster that uses dialup. \n• To enable a cluster, a dial-in and a dial-out phone number must be configured. \n• Alternate master is not supported. \nFigure 2: STAR Cluster Dialup Configuration Tab \ntie 41ARCAs - Wimp Oust \nLye and One \nNNW Oda Oa \nt9 Irate. \nNode \nCMS C-an \no.. 1.30•••• \n01•C•41-ala halid liana \n449a. \n'osi • toads I so* \nHod Won v... on be awattip.114 to mini \nTAN.. \n!goat Yin -loam \n0, \nDar tk.d.. \nMet. eft... teen, egiel tenon., 1 \n: \nThere are three tabs under Configuration: \n• Dial In lets you select host modems that the controller can call when dialing the host. \n• Dial Out lets you select host modems that the controller can use to dial out. \n• Periodic lets you specify a controller to periodically upload activity to the host, receive download \nconfiguration changes, and cardholder information from the host at that time. \n78 \nChapter 3 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226007\n", "char_count": 1447}, {"efta_number": "EFTA01225932", "page_number": 76, "text_content": "Creating a Cluster for Dialup \nTable 1: STAR Cluster Dialup Configuration Tab Definitions \nField \nDescription \nDial In Tab \nHost Modem/Host \nPhone Number \nClick to Add to open the Name Selection dialog box host to select the host modems and host phone numbers that the \nhost can use to contact thiscontroller. \n• The host calls the modems in the order that they are listed. \n• A modem/phone combination can be listed more than once, but you cannot enter more than 8 modem/phone \ncombinations. \nNumber of times to try \nconnections \nSpecify the number of times the controller dials each telephone number in the list when the controller cannot contact \nthe host. \nExample: \nIf 2 is entered in this field, the controller dials each telephone number in the list two times. If the requisite connection \nattempts with all the phone numbers in the list fail, the controller is considered to be in Comm fail.The system will \nuse the Retry interval during communication failure value to set the timing of communication attempts. \nDefautt: 2 \nRange: 0-99 \nDial Out Tab \nHost Modems! Remote \nPhone Number \nClick Add to add host modems and remote phone numbers that the host can use to dial out. \n• The host calls the modems in the order that they are listed. \n• A modem/phone combination can be listed more than once, but you cannot enter more than 8 modem/phone \ncombinations. \nAutomaticalty initiate \nconnection when \nconfiguration changes \nafter hh:mm \nSpecify the time to automaticalty download configuration changes to the dial-up controller. Then, click on the check box \nto enable the download time. \nExample: \nCardholder additions and deletions. \nNOTE: \n- Leaving this unselected means that configuration changeswill not be downloaded until the next normal \nconnection with the controller. \n- Selected with a time of 00.00 indicates immediate download. \n- Changes to the controller, such as change to an object's name or description, do not cause a download to the \ncontroller. \nRange: 0 to 23 hours 59 m\n... [truncated, 2475 chars — for the full page use /api/corpus/document/EFTA01225932/76 or ?id=EFTA01225932&page=76]", "char_count": 2475}, {"efta_number": "EFTA01225932", "page_number": 77, "text_content": "Creating a Cluster for Dialup \nTable 1: STAR Cluster Dialup Configuration Tab Definitions (continued) \nField \nDescription \nSchedule \nClick Q \nto open the Name Selection dialog box to select a non-recurring schedule for periodicdialing. irld \ndownloading configuration changes and cardholder information. \nNOTE: If the predefined 'Always' schedule is selected. the controlie, will onty use the time interval specified by Dial \nInterval outside of schedule.The Dial Interval during schedule setting will be ignored. \nDial intentalduring \nschedule \nSpecify the frequency that the host dials the controller when the time specification is in effect. \n• Enter the time in hh:mm format. \n• Range: 0 to 24:00 hours. \nDial interval outside \nschedule \nSpecify the frequency that the host dials the controller when the time specification is not in effect. \n• Enter the gins lo hh:mm format. \n• Range: 01024:00 hours. \nTo Configure a Cluster for Dialup \n1. Click on the Dialup Configuration tab in the iSTAR Ouster Editor dialog box. \n2. See Table 1 on Page 77 for Dial In, Dial Out, and Periodic tab configuration information. \n3. Click Save and Close when done. \n4. Go to iSTAR Pro Controller Editor on Page 137 to configure the controller. \n78 \nChapter 3 \nC•CURE 9000 Hardware Con figuration Guide \nEFTA01226009\n", "char_count": 1303}, {"efta_number": "EFTA01225932", "page_number": 78, "text_content": "4 \nConfiguring C•CURE iSTAR Clusters \nThis chapter explains how to configure iSTAR Clusters in the C•CURE 9000 system. \nIn this chapter \nOuster Communications Overview \n80 \nConfiguring iSTAR Ousters  \n87 \nCreating an iSTAR Ouster \n88 \nCreating and Using an iSTAR Cluster Template \n89 \niSTAR Ouster Editor  \n91 \niSTAR Ouster General Tab \n93 \niSTAR Ouster Communications Tab \n95 \niSTAR Ouster - Cluster Tab \n99 \niSTAR Ouster Miscellaneous Tab \n101 \niSTAR Ouster Area Tab \n102 \niSTAR Ouster Encryption Tab \n105 \niSTAR Ouster Triggers Tab \n107 \niSTAR Ouster Dialup Configuration Tab \n113 \niSTAR Ouster Status Tab \n114 \niSTAR Ouster State Images Tab \n115 \nC•CURE 9000 Hardware Configuration Guide \nChapter.. \n79 \nEFTA01226010\n", "char_count": 721}, {"efta_number": "EFTA01225932", "page_number": 79, "text_content": "Cluster CommunicationsOverview \nCluster Communications Overview \niSTAR controllers are organized for network communications into user-defined, logical groups called Clusters. \nClusters contain one or more iSTAR controllers. A C•CURE 9000 server (host) can be connected to multiple iSTAR \nclusters. An iSTAR Controller must belong to a Cluster. \nNOTE \nA Ouster can have a maximum of 16 controllers. \n■ Cluster Configuration and Distributed Management on Page 80 \n■ Networked iSTAR Controllers (Clusters) on Page 81 \n■ Establishing Connections Via the Primary Communications Path on Page 83 \n■ Setting Up the Primary Communications Path on Page 84 \n■ Downloading Cardholder and Configuration Information on Page 84 \n■ Maintaining Communications on Page 84 \n■ Establishing a Secondary Communications Path on Page 85 \n■ Distributed Cluster Management on Page 86 \n■ Unassigned Folder on Page 86 \nCluster Configuration and Distributed Management \nOne or more controllers can be configured for communications purposes into user-defined groups called Clusters. \nClusters have a primary communication path to the host that use Masters to control communications among cluster \nmembers and the host over the network. Clusters also support a backup communications path, the secondary \ncommunications path. The cluster can use the secondary path to communicate with the host when a \ncommunications failure occurs on the primary path. Secondary paths can only exist on the Master. \nNOTE \nNOTE \nThe Alternate Master capability cannot be configured in newly-created iSTAR clusters in version 2.20 \nor later. \niSTAR Clusters that already have an Alternate Master, when upgraded to version 2.20 or later, retain \nthe Alternate Master, but if the cluster is edited and the Alternate Master is removed, this change will \npermanently remove the ability to configure an Alternate Master for this cluster. \nSee the iSTAR Ouster Communications Tab on Page 95 for more information. \nSecondary communications paths have not be\n... [truncated, 2575 chars — for the full page use /api/corpus/document/EFTA01225932/79 or ?id=EFTA01225932&page=79]", "char_count": 2575}, {"efta_number": "EFTA01225932", "page_number": 80, "text_content": "Cluster Communications Overview \nNOTE \nPreviously, clusters were categorized by Controller Type rather than Encryption Setting. The \ncomposition of clusters and the models of controllers they contain has not changed. When \nC•CURE 9000 is upgraded, cluster types are changed to reflect Encryption Settings, but existing \ncontrollers remain in the same clusters. \nThis change has the following additional effects: \n• Existing Reports: ControllerType field is ignored. \n• Existing Queries: If ControllerType is included, the query cannot run until the Query is edited and \nControllerType is removed. \n• Dynamic Views: ControllerType is replaced by EncryptionSetting. \n• Existing Imports: ControllerType is marked as an Import Only property and used to set the \nEncryption Setting value. \nMaster controllers use the primary or secondary communications path to communicate with the C•CURE System \nhost. Establishing and maintaining a connection with the host involves the following administrative actions through \nthe use of iSTAR Clusters: \n■ Establishing connections via the primary communications path. You set up a primary communications path for \na cluster when configuring controllers and clusters. \n■ Downloading cardholder and configuration information from the host to the controller. \n■ Maintaining communications via the primary communications path. If a communications failure occurs on the \nprimary communications path, controllers can reestablish communications via a secondary communications \npath. \nNetworked iSTAR Controllers (Clusters) \nControllers are organized for network communications into user-defined or logical groups called Clusters. This \nsection describes the key elements of clusters. \nMaster and Cluster Members \nEach cluster has one controller that serves as the Master with all other controllers in the cluster acting as Cluster \nMembers. The master manages all communications between the cluster and a host computer. Cluster members can \ncommunicate with each other via t\n... [truncated, 2365 chars — for the full page use /api/corpus/document/EFTA01225932/80 or ?id=EFTA01225932&page=80]", "char_count": 2365}, {"efta_number": "EFTA01225932", "page_number": 81, "text_content": "Cluster CommunicationsOverview \nFigure 19: Cluster Members \nMaster \nHost \nEthernet \nCluste \nMembe A \nCluste \nMember B \nCluster Member A communicates \nwith Host via Master \nMaster \nEthernet \nCluste \nMember A \nCluster \nMember B \nCluster Member A communicates \nwith Cluster Member B via \nMaster \nThe Primary Communications Path \nThe Primary Communications Path is the first communications path that master controllers use to establish \ncommunications with the host. Controllers communicate with the host directly. The Connection type is TCP/IP over \nEthernet. \nThe Master is the one controller in a cluster that is responsible for passing messages between the host and cluster \nmembers. Cluster members do not communicate with the host directly; they communicate with the host through the \nmaster. Connections are established in the following bottom-to-top order: \n■ The Master is responsible for establishing a connection with the host. The host does not establish a connection \nwith the master. \n■ Cluster Members are responsible for establishing connections with the master. The master never tries to \nestablish a connection with a cluster member, as shown in Figure 20 on Page 83. \n82 \nChapter< \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226013\n", "char_count": 1252}, {"efta_number": "EFTA01225932", "page_number": 82, "text_content": "Cluster CommunicationsOverview \nFigure 20: Cluster Communication Path \n1, \n • \nCluster \nMember A \nMaste \nHos: \ne \nO \nCluster \nMember B \nThe Connection type is how the master connects to the host: TCP/IP over Ethernet. Cluster members are connected \nto the master via Ethernet only. Figure 21 on Page 83 shows the Primary Communications Path for Cluster Member \nA. The master/host connection type is TCP/IP over Ethernet. \nFigure 21: PrimaryCommunIcations Path \n- \nMaster \nost \nCluster \nMember A \nEthernet \nCluster \nMember B \nPrimary Communications Path for Cluster Member A \nEstablishing Connections Via the Primary Communications Path \nThe primary communications path is comprised of the following connections: \n■ The master connects directly to the host using a network connection. \n■ Cluster members connect to the master using a network connection. After connections are established, the master \nmanages cluster communications by passing messages between cluster members and the host. \nC•CURE 9000 Hardware Configuration Guide \nChapter < \n83 \nEFTA01226014\n", "char_count": 1060}, {"efta_number": "EFTA01225932", "page_number": 83, "text_content": "Cluster CommunicationsOvervlow \nConnections are established in a bottom-to-top order. Thus, clusters members are responsible for establishing \nconnections with the master, and the master is responsible for establishing a connection with the host. \nSetting Up the Primary Communications Path \nBefore controllers can establish any connections, you must configure the cluster's primary communications path by \nperforming the following tasks: \n■ Use the C•CURE 9000 Administration Application to first configure the cluster and then the iSTAR Controllers. \nSee Configuring iSTAR Clusters on Page 87 and Configuration Overview for iSTAR Controllers on Page 119 for \ninformation. \n■ Use the iSTAR Configuration Utility (KU) to manually configure the master. After you configure the master, it \nreboots and then establishes a connection with the C•CURE 9000 Server. The server downloads cardholder and \nconfiguration information to the master. \nAfter downloading information from the host, the master auto-configures its cluster members. Cluster members \nthen reboot and establish connections with the master. \nDownloading Cardholder and Configuration Information \nThe following information is downloaded to the master and its cluster members from the host: \n■ Cardholder data for personnel with clearances on the controller. \n■ Configuration information for inputs, outputs, and readers on the controller. \n■ Events that are controlled by the controller. \n■ Cluster information that the controller uses to communicate with other cluster members. \nNOTE \nThe C•CURE 9000 Server downloads cardholder and configuration information to the controller \nunder the following conditions: \n■ Initial configuration \n■ Each time the controller is powered on \n■ Each time the cluster is taken offline/online \nChanges to personnel, clearances, inputs, outputs, readers, and events are immediately downloaded. \nMaintaining Communications \nAlthough a communications link may be open between two devices, long periods of tim\n... [truncated, 2874 chars — for the full page use /api/corpus/document/EFTA01225932/83 or ?id=EFTA01225932&page=83]", "char_count": 2874}, {"efta_number": "EFTA01225932", "page_number": 84, "text_content": "Cluster Communications Overview \nmembers of the communications failure. At this time, cluster communications revert to the secondary \ncommunications path. \nUse the Communications and Cluster tabs in the C•CURE 9000 Administration Application, iSTAR Cluster dialog \nbox, to configure connection verification messages for the master, host and cluster members. See Configuring iSTAR \nClusters on Page 87 for more information. \nEstablishing a Secondary Communications Path \nif a communications failure occurs on the primary communications path, communications can be re-established via \nthe cluster's secondary communications path. The secondary communications path must be a second connection \nbetween the master and the host. The network connection must be one that is not already being used as the primary \npath. \nWhile communicating via the secondary path, the cluster attempts to re-establish communications with the host on \nthe primary communications path. When a connection is re-established on the primary path, communications revert \nto the primary path and the communications link on the secondary path is closed. \nUse the Communications tab in the Cluster dialog box in the C•CURE 9000 Administration Application to configure \nthe secondary communications path (see iSTAR Cluster Communications Tab on Page 95). \nThe Secondary Communications Path \nA Secondary Communications Path is the host communications path that is used by a controller if a \ncommunications failure occurs on the primary communications path. The secondary path is activated by the iSTAR \nController's dual network capability. \nFigure 22 on Page 85 shows an example of a secondary communications path on the host using an Ethernet \nconnection and a secondary communications path on another network card, using an Ethernet connection. \nFigure 22: Primary and Secondary Communications Path to Host \nHost \nPrimary \nCommunications \nPath \n'STAR Master \nCo droller \nEthernet \nSwitch \n4 —\nSecondary \nCommunications \nPath \nC•CURE \n... [truncated, 2063 chars — for the full page use /api/corpus/document/EFTA01225932/84 or ?id=EFTA01225932&page=84]", "char_count": 2063}, {"efta_number": "EFTA01225932", "page_number": 85, "text_content": "Cluster CommunicationsOverview \nDistributed Cluster Management \nCluster communications allow iSFAR controllers to share information and control actions throughout a cluster \nwithout host intervention. Distributed Cluster Management is the distribution of system functionality from the host \nto cluster members. \nDistributed cluster management lets a controller perform many actions locally and share information with other \ncluster members even when the controller is not communicating with the host, during a communications failure for \nexample. \nNOTE \nCluster members communicate with each other through the master. Although a communications \nfailure with the host may not affect cluster communications, a communications failure with the \nmaster can cause communications problems in the cluster. \nUnassigned Folder \nThe Unassigned folder is a repository for iSTAR controllers that have been configured for an iSTAR cluster, in an \nexisting partition, but which have been removed from the iSTAR cluster, or the cluster has been deleted. Such \ncontrollers will be listed under the Unassigned folder until they are reassigned to another iSTAR cluster or deleted. \n88 \nChapter < \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226017\n", "char_count": 1233}, {"efta_number": "EFTA01225932", "page_number": 86, "text_content": "Configuring STAR Clusters \nConfiguring iSTAR Clusters \nBefore you can create and configure iSTAR Controllers, you must create an iSTAR Cluster. The Cluster dialog box lets \nyou configure clusters by performing the following tasks: \n■ Add controllers to the cluster. \n■ Configure a primary communications path for the cluster. \n■ Configure a secondary communications path for the cluster. \n■ Configure communications between cluster members and the master. \n■ Configure the number of unacknowledged messages for controllers. \n■ Set Triggers for the cluster. \n■ Evaluate cluster status. \n■ Change state images that appear on the Monitoring Station. \nFigure 23: Hardware Pane- Creation of an iSTAR Cluster \nC•CURE 9000 Hardware Configuration Guide \nChapter 4 \n87 \nEFTA01226018\n", "char_count": 774}, {"efta_number": "EFTA01225932", "page_number": 87, "text_content": "Creating an STAR Cluster \nCreating an iSTAR Cluster \nYou can create an iSTAR Cluster in a Hardware Folder in the Hardware tree. You can either select a folder, then pick \niSTAR duster from the Hardware tree drop-down list, or right-click on the folder and select iSTAR duster from the \ncontext menu. \nTo Create an iSTAR Cluster \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Expand the Hardware tree and select the folder where you want to create the iSTAR Cluster. \n3. Right-click on the folder and select iSTAR Cluster>New to create a cluster for one or more iSTAR controllers. \nThe iSTAR Cluster Editor dialog box opens, as shown in Figure 26 on Page 92. \nSee iSTAR Cluster Editor on Page 91 for instructions on configuring the Cluster. \n4. Enter a Name (required) and Description (optional). \n5. Select an Encryption Setting \n■ Encrypted for a Cluster that will contain iSTAR eX, iSTAR Edge, or iSTAR Ultra controllers that will use an \niSTAR encryption method. \n■ Non-Encrypted for a Cluster that will contain iSTAR Pro, iSTAR Classic, or iSTAR Ultra controllers that will \nnot use an iSTAR encryption method. \nNOTE \nThis field becomes Read-only once you add iSTAR controllers to the Ouster and save it, because \nchanging this setting while there are controllers in the cluster would cause problems. \nIf you need to change this setting, you must remove all controllers from the Cluster, change the \nEncryption Settings on the Ouster Encryption tab (see iSTAR Cluster Encryption Tab on Page \n105), then add controllers of the appropriate type. \n6. Click Save and Close to save the Cluster. The new iSTAR Cluster icon displays in the tree, one level below the \nfolder that you selected. \n88 \nChapter < \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226019\n", "char_count": 1822}, {"efta_number": "EFTA01225932", "page_number": 88, "text_content": "Creating and Using an STAR Cluster Template \nCreating and Using an iSTAR Cluster Template \nYou can create an iSTAR Cluster Template that you can use as the basis for creating new iSTAR Clusters with \nspecific settings that you choose when creating the Template. \nExample \nIf you want all of your iSTAR Clusters to use 60 seconds instead of the default 10 seconds for the Connection to \nHost Interval, you can create an iSTAR Cluster Template with Connection to Host Interval set to 60 seconds, and \nevery iSTAR Cluster you create from this Template will inherit that setting. \nTo Create an iSTAR Cluster Template \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Expand the Hardware bee and a hardware folder. \n3. Right-click on the folder and select iSTAR Cluster>New Template from the context menu (see Figure 24 on Page \n89). \nFigure 24: New Cluster Template from Hardware Folder Context Menu \npc tau 9000 Adm•norshon %/Ace. \nServer Options \n• 11,loare \nOvisiCeoforin \n12 C0, 00,0bnekParinonC.I.sit \n• 12 *TAR Comore (Paver  \ntot \ntof Comm Pees \na Host Mocem \nPaitobcal (Paftdon Parlacl \nHMOS \nid \nRC Catboat, \nSIR Caren Pal \nI \nnag Nada. \nn C•ant %kJ* \nnn-itt... \n4000 \n• \nPage ' ,ca. \nSOFTWARE HOM \nAlternatively, select iSTAR Cluster in the Hardware pane drop-down list, click the down-mow next to the New \nbutton, then select iSTAR Cluster>New Template from the menu. \nThe iSTAR Ouster Editor opens a new Template that you can configure and save. \n4. Enter a unique name for the Template in the Name field (required) and type a textual description for the \nTemplate in the Description field (optional). \nC•CURE 9000 Hardware Configuration Guide \nChapter < \n89 \nEFTA01226020\n", "char_count": 1739}, {"efta_number": "EFTA01225932", "page_number": 89, "text_content": "Creating and Using an STAR Cluster Template \n5. Select the Encryption Setting for the Ouster Template. Only controllers of the types supported by this setting can \nsubsequently be added to Clusters created from this Template. (This field becomes read-only after you save the \nOuster Template). \n6. Navigate to the Communications, Ouster, Miscellaneous, Encryption, Triggers, and State Images tabs and \nconfigure any settings that you would like to be included in your Template. See iSTAR Cluster Editor on Page 91 \nfor more information about the iSTAR Ouster Editor tabs. \n7. Click Save and Close. The Ouster Template is saved with your settings. You can now use the Template as the \nbasis of new iSTAR Clusters you subsequently create. \nNOTE \nA Ouster Template is not saved inside of a Hardware folder, and it is not visible in the Hardware \ntree. To edit a Ouster Template, select iSTAR Cluster from the Hardware drop-down list and click \n• to display a Dynamic View listing all iSTAR Clusters, including Ouster Templates. Double-click \non a Ouster Template in the Dynamic View to edit it. \nTo Create an iSTAR Cluster from a Template \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Expand the Hardware tree and a hardware folder. \n3. Right-click on the folder and select iSTAR Cluster>New from the context menu (see Figure 25 on Page 90). \nFigure 25: New STAR Cluster from a Template \nEd \nD\n. \n(man selectort \nred iiAudl Loct \nrnd inJounal. \ncoC Caren Pot \n• \nCksttei \n• L \nUSCG:Mob \n• \nCC 0:Cilkit. \n• \nWAS Fat* \n• \nCOJRE Mott \n• \nNew \nNew lenvive \n—rent: \ncattle t 44,00 e \ngio \nAnita tarciate la eX \nThe iSTAR Ouster Editor and you can edit the new Cluster. \n4. Enter a unique name for the Ouster in the Name field (required) and type a textual description for the Ouster in \nthe Description field (optional). \n5. Select the Encryption Setting for the Ouster Template. Only controllers of the types supported by this setting can \nsubse\n... [truncated, 2542 chars — for the full page use /api/corpus/document/EFTA01225932/89 or ?id=EFTA01225932&page=89]", "char_count": 2542}, {"efta_number": "EFTA01225932", "page_number": 90, "text_content": "STAR Cluster Editor \niSTAR Cluster Editor \nThe iSTAR Cluster Editor is used to configure iSTAR Ousters for your C•CURE 9000 system. All iSTAR Controllers \nmust be contained in an iSTAR Ouster in order to communicate with a C•CURE 9000 Server. You need to create at \nleast one iSTAR Ouster before you can create any iSTAR Controllers. \niSTAR Cluster Editor Tabs \nThe iSTAR Ouster Editor includes the following tabs: \n■ iSTAR Ouster General Tab on Page 93 \n■ iSTAR Ouster Communications Tab on Page 95 \n■ iSTAR Ouster - Ouster Tab on Page 99 \n■ iSTAR Ouster Miscellaneous Tab on Page 101 \n■ iSTAR Ouster Area Tab on Page 102 \n■ iSTAR Ouster Encryption Tab on Page 105 \n■ iSTAR Ouster Triggers Tab on Page 107 \n■ iSTAR Ouster Dialup Configuration Tab on Page 113 \n■ iSTAR Ouster Status Tab on Page 114 \n■ iSTAR Ouster State Images Tab on Page 115 \nAccessing the iSTAR Cluster Editor \nl'ertorm the following steps to access the iSTAR Ouster Editor. \nTo Access the iSTAR Cluster Editor \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane (see \nFigure 23 on Page 87). \n2. Expand the Hardware tree and select the Cluster that you want to configure. \n3. Right- click and select iSTAR Cluster>Edit to open the selected Ouster in the iSTAR Ouster Editor (see Figure 26 \non Page 92). \nC•CURE 9000 Hardware Configuration Guide \nChapter< \n91 \nEFTA01226022\n", "char_count": 1394}, {"efta_number": "EFTA01225932", "page_number": 91, "text_content": "STAR Cluster Editor \nFigure 26: STAR Cluster Editor \n=1_11.1€ \nE\nl\nm\n \nI \nDosages' \nr \nr \nG\". I ConasogeSaa I GoeW I iebalswass I Me I fowl moral snail assos• I \nOats Gams. \nC visas( g \nfitanike Set\" >.:rn$ \nzi \n92 \nChapter 4 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226023\n", "char_count": 282}, {"efta_number": "EFTA01225932", "page_number": 92, "text_content": "STAR Cluster General Tab \niSTAR Cluster General Tab \nThe iSTAR Cluster General Tab provides an interface to manage controllers that you have configured for a cluster. \nFrom the General tab, you can add or remove iSTAR Controllers from a Ouster. An example of an iSTAR Ouster \nGeneral tab is shown in Figure 26 on Page 92. \nSee iSTAR Ouster General Tab Definitions on Page 94 for definitions of the fields and buttons on the iSTAR Ouster. \niSTAR Cluster General Tab Tasks \nYou can perform the following tasks from the iSTAR Ouster General Tab. \n■ Adding a Controller to a Ouster on Page 93. \n■ Removing a Controller from a Ouster on Page 93. \nAdding a Controller to a Cluster \nTo Add a Controller to a Cluster \n1. Open the iSTAR Ouster editor for the Cluster to which you wish to add a Controller. See To Access the iSTAR \nCluster Editor on Page 91. \n2. Click Add. \nThe iSTAR Controller selection dialog box opens. This dialog box lists all iSTAR Controllers that can be added to \nthis Ouster. Only iSTAR Controllers with the same Encryption Setting as the Ouster (Encrypted or Non-\nencrypted) that are currently Unassigned (not currently attached to an iSTAR Ouster) appear in this dialog box. \n3. Select one or more iSTAR Controllers from the dialog box. You can use multiple selection keystrokes such as \nCTRL+Left-click and SHIFT+Left-click to select more than one Controller. \n4. Click OK to add the selected iSTAR Controllers to the list of Controllers in the iSTAR Ouster. \n5. Click Save and Close to save your changes. \nRemoving a Controller from a Cluster \nYou can remove iSTAR Controllers from an iSTAR Ouster using the iSTAR Cluster General tab. Once you remove a \nController from an iSTAR cluster, the Controller is moved to the Unassigned folder and can subsequently be added \nto a different iSTAR Ouster with the same Encryption Setting. \nTo Remove a Controller from a Cluster \n1. Open the iSTAR Ouster Editor for the Ouster to which you wish to add a Controller. See To Access the iSTAR\n... [truncated, 2567 chars — for the full page use /api/corpus/document/EFTA01225932/92 or ?id=EFTA01225932&page=92]", "char_count": 2567}, {"efta_number": "EFTA01225932", "page_number": 93, "text_content": "STAR Cluster General Tab \nsecondary communications with the host. The Remove button becomes unavailable if you select such a \ncontroller. \n3. Click Remove. The Controllers you selected are deleted from the Controller(s) list of this Cluster. \n4. Click Save and Close to save your changes. The Controllers you removed from this Cluster now appear in the \nUnassigned folder in the Hardware tree, and can be re-assigned to another Cluster with the same Encryption \nSetting. \niSTAR Cluster General Tab Definitions \nThe iSTAR Cluster General tab includes the fields and buttons described in Table 6 on Page 94. \nTable 6: iSTAR Cluster General Tab Definitions \nField/Button \nDescription \nName \nEnter a name (up to 10O characters long) of the STAR Cluster that you are configuring. \nDescription \nType a description of the STAR Cluster that you are configuring. \nEnabled \nEnabled isgrayed out until: \n1. The controller's are configured. See Chapter 5. Configuring C•CURE STAR Controllers \n2. A Controller having primary communications with host isselected on the !STAR Cluster \nCommunications tab. \n3. Click Enabled to put the cluster online. \nMaintenance \nMode \nClick to put the Cluster or STARS and/or their components into Maintenance Mode. See Chapter 2: Maintenance \nMode for more information. \nPartition \nThis read-onty field identifies the Partition in which this STAR Cluster resides. \nSelect the Encryption Setting for the Cluster Template. Onty controllers of the types supported by this setting can \nsubsequentty be added to Clusters created from this Template. (This field becomes read-onty after you save the \nCluster Template). you want to change the Partition of a Cluster, see Using Drag and Drop in the Hardware Tree \non Page 27. \nEncryption \nSetting \nA read-onty field displaying the Encryption Setting for the Cluster. \nControllers \nAdd \nTo add an STAR Controller to your Cluster, click Add to display the STAR Controller selection dialog box. Select \none or more controllers and click OK \n... [truncated, 2361 chars — for the full page use /api/corpus/document/EFTA01225932/93 or ?id=EFTA01225932&page=93]", "char_count": 2361}, {"efta_number": "EFTA01225932", "page_number": 94, "text_content": "STAR Cluster Communications Tab \niSTAR Cluster Communications Tab \nThe Communications tab in the iSTAR Cluster dialog box lets you configure communications from the Controllers in \na cluster to the C•CURE 9000 Server (Host). Primary and Secondary communications can be configured for an \niSTAR controller that has two Onboard Ethernet Adapters. When one adapter is chosen as primary, the other can \nbecome the secondary. \nIf you are using iSTAR Pro dialup, the cluster must be configured for dialup communication. \nNOTE \nNOTE \nFor a cluster that existed prior to version 220, you can have one controller configured for the Primary \ncommunications path as a Master controller, and a second, different, controller configured for the \nSecondary communications path as an Alternate Master. \nHowever, if you remove the Alternate Master from the cluster, you will no longer be able to configure \nan Alternate Master for the cluster. A message box appears when you change Controller having \nsecondary communications with host to None, informing you that the change will remove the \nAlternate Master. \n'kW \n4.. \nIf this change is maide, it mil no longer be possible to configure an \ni.lik Alternate Master controller. Click OK to continue mth change. \nOK \nFor a new cluster created in version 220 or later, you cannot configure an Alternate Master. If you \nconfigure both a Primary and Secondary communications path, you must use the same controller, \nwhich must have two onboard Ethernet Adapters. \nDialup can be used only as the primary connection method or the secondary communication method, \nnot as both. \nExample: \n■ Dialup is used as the primary communication method and there is no secondary communication \nmethod. \n■ TCP/IP is used as the primary communication method and Dialup is used as the secondary \ncommunication method. \nCommunications tab definitions are listed in Table 7 on Page 97. \nNumber of Failed Attempts Before Connection Fails on Page 98 explains how to configure the cluster's cont\n... [truncated, 2224 chars — for the full page use /api/corpus/document/EFTA01225932/94 or ?id=EFTA01225932&page=94]", "char_count": 2224}, {"efta_number": "EFTA01225932", "page_number": 95, "text_content": "STAR Cluster Communications Tab \nTo Configure the iSTAR Cluster - Communications Tab \n1. From the iSTAR Controller dialog box, click the Communications tab. The Communications tab opens, shown in \nFigure 27 on Page 96. \nFigure 27: iSTAR ClusterCommunications Tab \nOf 41•Aank. • 0.00ap Orly \nBye \nour \nbin O.\n Me \nClocno. \nEntati \ntmenv•ce We* \nGess •----Agen \n[ Hoots& I Pao linw.lTIM= \n60•0021•••••• I \n[ Mumps.\nNW/ \nCo•t•A.,..r.pw,,,eraand.kat Vireo \nmeta \nsui \nceranOe *10 \nCc\"can°00•WO, Wash) 20 \n•: \nNue, el Yid SO. Son examien lob \nReconso Ismo te. <wear Oave (mank) 40 \nCanceve kw...0mnd Oom!.1 tO \nCray \ntmom, connneatow wk. SY Yes \n1./of d onreces brow Ica. met. \nCarman nestkoorg occedo 20\nMoen a/ Wed mina b•ke4 ccen414.1444 I \n/4011•KIIMerli \nbarrea• att. (Scads) 40 \nCaoloca, hack.> 01,..11(matos, 10 \n2. Controllers having primary/secondary communication with host allows you to select the controller in the cluster \nthat has primary or secondary communications with the host (C•CURE 9000 server). Choose a controller using \nthe drop-down selection. \n3. Method of communication between host and controller allows a selection of the communication type \ndesignated for the iSTAR controller that communicates with the host. Choose the connection type of Onboard \nEthernet or Dialup (iSTAR Pro or iSTAR Ultra Pro Mode only) using the drop-down selection. \n4. In the Connection to Host Interval entry field, specify the number of seconds that a controller waits between \nattempts to connect to the host. \nUL requires a maximum of 200 seconds supervision on the Communications link between the protected premise \nequipment and the central station. \n5. In the Number of failed attempts before connection fails field, specify the number of attempts that a controller \nmakes to first connect to the host before the controller is declared to be in communications failure. See Number of \nFailed Attempts Before Connection Fails on Page 98 for more information. \n6. In the Reconnect Interval after \n... [truncated, 2262 chars — for the full page use /api/corpus/document/EFTA01225932/95 or ?id=EFTA01225932&page=95]", "char_count": 2262}, {"efta_number": "EFTA01225932", "page_number": 96, "text_content": "STAR Cluster Communications Tab \nconnect to the host after a communications failure occurs between the host and the controller. The default \ninterval is 40 seconds. The maximum value is 9999 seconds and the minimum is 1 second. \n7. In the Connection Inactivity Interval field, specify the number of seconds that a controller waits between \nattempts to connect to the host. The default interval is 80 seconds. The possible values are between 15 and 80 \nseconds. \n8. Navigate to the iSTAR Cluster - Cluster Tab on Page 99 or click Save and Close to save the cluster and begin \nconfiguring iSTAR Controllers. \nTable 7: STAR Cluster Communications Tab Definitions \nField \nDescription \nControllers \nhaving primary \nor secondary \ncommunication \nwith host \nThis field allows you to select the controller that has primary or secondary communicationswith the host. Choose a controller \nusing the drop-down selection. \nMethod of \ncommunication \nbetween host \nand controller \nThis field allows you to select the communication type designated for the iSTAR controllers, PC MC IA Ethernet, Onboard \nEthernet or [Halal) (iSTAR Pro/iSTAR Ultra SE Pro Mode only). \nConnection to \nHost Interval \n(seconds) \nSpecify the number of seconds that a controller wads between attempts to connect to the host. Use the Number of failed \nattempts before connection falls field in the Communications tab to specify the number of connection attempts a \ncontroller makes before a communications failure isdedared for the controller. The maximum value is 9999 seconds and the \nminimum is 1 second. The default value is 20 seconds. \nNumber of faded \nattempts before \nconnection fats \nSpecify the number of attempts that a controller makes to first connect to the host before thecontroller is dedared to ben \ncommunications failure. See Number of Failed Attempts Before Connection Faison Page 98. The default value is 4 attempts. \nReconnect \nIntervalafter \nconnection \nfaiure [seconds) \nSpecify the number of seconds that controllersw\n... [truncated, 2612 chars — for the full page use /api/corpus/document/EFTA01225932/96 or ?id=EFTA01225932&page=96]", "char_count": 2612}, {"efta_number": "EFTA01225932", "page_number": 97, "text_content": "STAR Cluster CommunicationsTab \nNumber of Failed Attempts Before Connection Fails \nThe Number of failed attempts before connection fails field in the Communications tab specifies the number of \nconnection attempts a controller makes before a communications failure is declared for the controller. The default is 4 \nattempts. The maximum is 99 attempts and the minimum is 1 attempt. \nIf a connection is established, the controller and host use connection verification messages to maintain the \nconnection. \nIf a connection is not made in the specified number of attempts, a communications failure is declared for the \ncontroller, and the following connections are attempted: \n■ If the secondary communications path uses an alternate host, the controller attempts to connect to the alternate \nhost, which passes the controller's messages to the host. At the same time, the controller tries to reestablish a \nconnection with the host at the rate specified in the Reconnect Interval after connection failure field. \n■ If the secondary communications path does not use an alternate host, the controller attempts to connect to the \nhost forever, or until a connection is established. The controller attempts to connect to the host at the rate \nspecified in the Reconnect Interval after connection failure field. \n■ The controller broadcasts a request across its subnet for the host's IP Address. The host responds to the request. If \nthe host does not respond in a set amount of time and the iSTAR Configuration Utility is configured for auto-\nresponse, the utility responds to the controller. See the iSTAR eX Installation and Cm0gumtion Guide for \ninformation. \nIf a communications failure occurs, the following connections are attempted simultaneously: \n■ If the secondary communications path uses an alternate host, the controller attempts to connect to the alternate \nhost, which passes the controller's messages to the host. At the same time, the controller tries to reestablish a \nconnection with th\n... [truncated, 3048 chars — for the full page use /api/corpus/document/EFTA01225932/97 or ?id=EFTA01225932&page=97]", "char_count": 3048}, {"efta_number": "EFTA01225932", "page_number": 98, "text_content": "STAR Cluster Cluster Tab \niSTAR Cluster - Cluster Tab \nThe Cluster tab regulates the connection and reconnection intervals between the primary iSTAR Controller and those \ncontrollers which are cluster members. \nNOTE \nThe Cluster tab has not been evaluated by UL. \nTo Configure the iSTAR Cluster - Cluster Tab \n1. From the iSTAR Controller dialog box, click the Cluster tab. The Cluster tab opens, shown in Figure 28 on Page \n99. \n2. Specify the number of seconds that the primary controller attempts to connect with the host server in the \nControllers attempt to connect to cluster master interval entry field. The range is from 1 to 9999 seconds; the \ndefault value is 20 seconds. \nFigure 28: iSTAR Cluster Cluster Tab \niel$l.t VC CO'S \nti•-• ISl Rase.Canovi \nClunres l\nremongL4 \nr \nr yonterox. Wee \nPros\"- se.. Wag \nGran I Covrv-hcercns Cute I lascelre:us I Av. I &cam^ • rod.l Salo I %toms« I \nCul« \n,c•w(nen se ti (*.nay Ova+ onsw mothseccaOs) \nhinted Mb: =Ws b <orcrolen to f.mise carecie tblin \nRO:411•Xl ken. Mp cansttiotlablaft•csail \n(saws.. IrAchitz atonal (act) \nn \n3. Enter the number of instances after which the primary controller transmits a connection failure in the Number of \nfailed attempts for controllers to declare a connection failure entry field. The range is from 1 to 99; the default \nvalue is 4. \n4. Specify the number of seconds after which the primary controller attempts to reconnect after a connection failure \nin the Reconnection Interval after connection failure entry field. The range is from 1 to 9999 seconds; the default \nvalue is 40 seconds. \nC•CURE 9000 Hardware Configuration Guide \nChapter< \n99 \nEFTA01226030\n", "char_count": 1650}, {"efta_number": "EFTA01225932", "page_number": 99, "text_content": "'STAR Cluster - Cluster Tab \n5. Enter the number of seconds after which the primary controller transmits a connection failure if there is no \nmessage while it is connected, in the Connection Inactivity Interval entry field. The range is from 15 to 80 \nseconds; the default value is 80 seconds \n6. Navigate to the Miscellaneous tab or Save and Close to save the cluster and begin configuring iSTAR \nControllers. \n100 \nChapter < \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226031\n", "char_count": 483}, {"efta_number": "EFTA01225932", "page_number": 100, "text_content": "STAR Cluster Miscellaneous Tab \niSTAR Cluster Miscellaneous Tab \nThe iSTAR Cluster Miscellaneous tab allows you to set the maximum number of unacknowledged messages that are \nallowed for each iSTAR Controller \nTo Configure the iSTAR Cluster - Miscellaneous Tab \n1. From the iSTAR Controller dialog box, click the Miscellaneous tab. The Miscellaneous tab opens, shown in \nFigure 29 on Page 101. \nFigure 29: STAR Cluster MiscellaneousTab \nas\n int cow \nhies )1 TAR 3.4e., ClfeA I \nnews. \nr frakd \nha*. So\"Wirep \nr 19.101inte we. \nGerbil I Cranctcra lace werAargoA I Ma I Ercnotad 1.0.1 I saes l 9.stenson I \nUnictraslastpd Mr tape \nWomen lure. (0 ,nacluomieVed messages b wh crvots \n2. In the Unacknowledged Messages box specify the maximum number of unacknowledged messages that are \nallowed for each iSTAR Controller in the Maximum number of unacknowledged messages for each controller \nfield. \nIf you have a network with high latency, you may want to set this value to a higher number; if the network has \nlow latency, the default value (10) should be sufficient. \nNOTE \n• This setting does not result in lost messages. \n• For Proprietary Burglar Alarm applications, the Send state changes to the monitoring station \noption must be selected. \n• The range is from 1 to 99 and the default value is 10. For UL applications, set the range to 99. \n3. Navigate to the Antipassback tab or Save and Close to save the cluster and begin configuring iSTAR \nControllers. \nC•CURE 9000 Hardware Configuration Guide \nChapter 0 \n101 \nEFTA01226032\n", "char_count": 1531}, {"efta_number": "EFTA01225932", "page_number": 101, "text_content": "STAR Cluster Area Tab \niSTAR Cluster Area Tab \nThe iSTAR Ouster Area tab allows you to configure the following \n■ How Ouster Antipassback works for iSTAR Ouster Areas during a communications failure when the Ouster \nmembers lose communication with the Ouster master. \n■ Whether or not the Ouster is configured for both Global Antipassback and Ouster Antipassback or solely for \nOuster Antipassback. \nNOTE \nModifying either of these options can only be done if the Cluster is not Enabled. \nYou configure how Global Antipassback works during a communications failure through a system variable in the \niSTAR Driver section, \"iSTAR Global Antipassback Communication Failure Mode. For more information, see the \nC•CURE 9000 System Maintenance Guide. \nCluster Antipassback Communications Failure Mode \nAs long as the communication within the Ouster is good, the Ouster members do not store any antipassback \ninformation. During communications failure, the Ouster members (the Controllers) begin to enforce antipassback \nlocally, based on the Failure Mode you configure for the Area's Ouster on this tab. \nFor iSTAR Ouster Areas, all Doors and Readers must be within the same iSTAR Ouster. Adjacent Areas can be on \nany Ouster and can also be Cross-Cluster Areas. \nUsing Antipassback restricts access to Ouster Areas as follows: \n• Regular antipassback - Personnel cannot exit an Area they are not in, nor re-enter an Area without exiting it \nfirst. \n• Timed antipassback - Personnel cannot re-enter an Area until a specified amount of time has passed. \nThe violation triggered when personnel enter a specified Area is called an entry violation. The violation triggered \nwhen personnel exit a specified Area is an exit violation. \nNOTE \nTo ensure that personnel are always appropriately prevented from entering Lockout Areas, make sure \nthat you configure the Communications Failure Mode for the Area's iSTAR Ouster as No access \nMode, instead of Local Mode. \nGlobal Antipassback for the Cluster \niSTAR Glob\n... [truncated, 2788 chars — for the full page use /api/corpus/document/EFTA01225932/101 or ?id=EFTA01225932&page=101]", "char_count": 2788}, {"efta_number": "EFTA01225932", "page_number": 102, "text_content": "STAR Cluster Area Tab \nFigure 30: STAR Cluster Area Tab \naw.t.sone \nlima 'STAR Wag C.o. \nDPICtlebta \nrfpatkd \nPanion So. Vey \nr \nHod. \nGrail I Cooeuwelor IoM I liKelneaa \naar Moseick Conn...coon Naar safe \nI &a$0. 30 I Tratie I 2a• I 9dowle• I \nr Ho saes \n6. Local \nGIS* Arsgented \nr \netc...STAR Global attosseted a ma a STAR Claassonsbeth \n2. In the Cluster Antipassback Communication Failure Mode box, click to select either the No access or Local \noption. \nNOTE \nMake sure that you leave the Cluster enforces iSTAR Global antipassback as well as iSTAR Cluster \nantipassback check box unselected. \nTo Configure the iSTAR Cluster - Area Tab for both Global Antipassback and Cluster Antipassback \n1. From the iSTAR Cluster dialog box, click the Area tab. The Area tab opens, shown in Figure 30 on Page 103. \n2. In the Global Antipassback box, click to select the Cluster enforces iSTAR Global antipassback as well as \niSTAR Cluster antipassback option. \nArea Tab Field Definitions \nArea tab definitions are listed in 'able 8 on Page 104. \nC•CURE 9000 Hardware Configuration Guide \nChapter 4 \n103 \nEFTA01226034\n", "char_count": 1110}, {"efta_number": "EFTA01225932", "page_number": 103, "text_content": "STAR Cluster Area Tab \nTable 8: Area Tab Definitions \nFields \nDescription \nCluster Antipassback Communication Failure Mode \nThe options in this box are avertable only if the Cluster enforces !STAR Global antlpassback as well as !STAR Cluster antlpassback \noption in the Global Antipassback box is not selected. \nNo access (Hard) \nSelect this option to configure No access as the Communications Failure mode for this Cluster. \n• Access is denied by any member Controller in the Cluster in communications failure. \n• Member Controllers still in communications with the Master continue to request normal \nantipassbackdecisions for entry to the Area. \n• Master Controllers need no communication to make antipassback decisions and always do so \nregardlessof host or member communication. \n(In this mode, the person is presumed to be in violation. unless proven otherwise.) \nLocal (Soft) \nSelect th is option to configure Local as the Communications Failure mode for this Cluster. \n• The Controller uses locally available information to grant or deny access. Even if this information \nis insufficient, the Controller admits the person presenting the card. \n(In this mode, the person is presumed not-In-violation. unless proven otherwise.) \nWhen Local mode is configured, the person is allowed in unless the Controllers making the decision \ndetermine beyond doubt that he/she is guilty of an antipassback violation. \nGlobal Antipassback \nCluster enforces STAR Global \nantipassback aswell as STAR Cluster \nantipassback \nSelect thischeck box to indicate that this Cluster sharesdata with all the other Clusters that use \nSTAR Global Antipassback. (The default is cleared indicating that the Cluster does not share data \nwith any other Clusters.) \nNOTE: When thisoption is selected, the Cluster Antipassback Communication Failure Mode \nboxoptions become unavailable. \n104 \nChapter 0 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226035\n", "char_count": 1929}, {"efta_number": "EFTA01225932", "page_number": 104, "text_content": "STAR Cluster Encryption Tab \niSTAR Cluster Encryption Tab \nThis tab allows you to configure the encryption mode for an Encrypted Cluster. \nNOTE \nThis tab is Read-only for a Non-encrypted Cluster, and does not apply. Non-encrypted Clusters do not \nuse 256 bit AES (FIPS 197) encryption. \nThe iSTAR eX, iSTAR Edge, and encrypted iSTAR Ultra controllers always use 256-bit AES (FIPS 197) encryption by \ndefault. \nThe Encryption options on the iSTAR Cluster Encryption tab let you choose the FIPS 140-2 method for an Encrypted \nCluster. The options on the iSTAR Cluster Encryption tab are only available for iSTAR Encrypted Clusters. \nNOTE \nThe 256 bit AES (FIPS 197) encryption method satisfies the Proprietary Burglar Alarm application \nrequirements. \nFIPS 140-2 mode requires a custom certificate key, either host based or controller based. Software House recommends \na controller based certificate key. Once you set the cluster to FIPS 140-2 compliant mode, the iSTAR encrypted \ncontrollers will be in \"dark mode.\" They will not be visible on the network. \nNOTE \nSoftware House recommends that you configure the Tamper Input for a 'dark mode' controller to \ntrigger an Alarm Event that will be displayed on the Monitoring State if the input changes state. \nTo Configure FIPS 140.2 Encryption for an iSTAR Encrypted Cluster \n1. Open the Encryption Options dialog box in the Options and Tools pane and select from the following options: \n• Controller-Based Encryption Mode \n• Host-Based Encryption Mode \n2. To use FIPS 140-2 mode, Software House recommends that you use the Controller-Based Encryption Mode. \nNOTE \nSoftware House recommends Controller-based Encryption for 2 reasons: \n1. Host-based Encryption requires a private key to be transmitted to the controllers non-encrypted. \nController-based Encryption does not. The tradeoff is that the controller-based method requires a \nsignature at the host that recognizes the iSTAR to be valid. \n2. The second reason is that it is much easier to recov\n... [truncated, 2462 chars — for the full page use /api/corpus/document/EFTA01225932/104 or ?id=EFTA01225932&page=104]", "char_count": 2462}, {"efta_number": "EFTA01225932", "page_number": 105, "text_content": "STAR Cluster Encryption Tab \nFigure 31: 'STAR Cluster Encryption Tab \n/SIMONS. • \na Yard Ow \ns-s \n2044.0to,\n14.1. \nrye \navareien Uwe. Malan, Ira \nfruxtonCsecn \nI ' a go.° Ikon I SS I ilsinp. \n• **VS tO2 rale \nr. 110$1402yobseuroStr4101•X PIA msb 4TAII rYnTMIIN \nI-\n6TMJlmwbewOS.flVMS by SSTb WS 1102 \n61M &In amiss an ma bled %MOWS la Iss my ass rasa whin IST AA a orinlin w ap \n1.110•00••••• \n• 457M \ntaidtioir \nFPS\nIOWAN \n20.1.0e, nem; n en7,01.0 sat \ncane n(kosnoes MAP ea \naredissiniti APS \nS vet. \n5. Select from the available Encryption modes: Non-FIPS 140-2 and FIPS 140-2. \n6. Navigate to the Triggers tab or Save and Close to save the cluster and begin configuring iSTAR Controllers. \nNOTE \nFIPS 140-2 compliant mode has not been evaluated by UL. \n106 \nChapter < \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226037\n", "char_count": 828}, {"efta_number": "EFTA01225932", "page_number": 106, "text_content": "STAR Cluster TriggersTab \niSTAR Cluster Triggers Tab \nC•CURE 9000 uses Triggers, which are configured procedures used for activating security actions. A Trigger \nautomatically executes a specified Action when a particular predefined condition occurs. When a Trigger is defined, \nthe Actions available depend on the property selected. This section illustrates the use of Triggers to monitor a cluster \nmaster power failure. \nNOTE \nThe Triggers tab is not available for iSTAR Pro or iSTAR Ultra SE Pro Mode dialup \nconfigurations. \nTo Configure the iSTAR Cluster Triggers Tab \n1. Navigate to the Triggers tab, shown in Figure 33 on Page 108. \nFigure 32: ISTARClusterTriggersTab \nU.-. \n*Oa \nCercvs \nQL-4,,coat voregeng — \nr Ws,' \nr 21~4,14* MC40 \nPorttne Saner \nC.reli I Convict.\" I Coate I \neareas I M. I Erna:. IV O. I taus I 'se innes \ninmost \nLi\nRopes', \n'MA \nDetwi• \nThis tab provides you with ability to define the activation/deactivation, enable/disable, and arm/disarm, etc. of \nsuch objects as: events, inputs, outputs, camera actions, door status changes, etc. Triggers can also be used to \nlaunch events which also can be used to launch imports and exports, email and reports, viewer and message \ndisplays, personnel ID number state changes, controller downloads, sound activation, communication \nnotifications, etc. \n2. Click Add in the Triggers tab to create a new trigger. \na. Click within the Property column to display C. \nWhen you select this button, the Property browser opens presenting properties available for the controller. \nb. Click a Property to select it and add it to the column (see Figure 33 on Page 108). \nC•CURE 9000 Hardware Configuration Guide \nChapter< \n107 \nEFTA01226038\n", "char_count": 1703}, {"efta_number": "EFTA01225932", "page_number": 107, "text_content": "STAR Cluster Triggers Tab \nFigure 33: STAR Cluster Triggers Tab• PropertySelection \nEnoreerrl \nCbck Nis To ilia arla \nPrimer/ C.rv.car4 \nPnrwy Oorrmac.40O, Stela of to ,SLR clyM \nc. Click within the Value column to display a drop-down list of Values associated with the Property that you \nhave selected. Then click on a Value that you want to include as a parameter for the bigger to add it to the \ncolumn (see Figure 34 on Page 109). \n108 \nChapter< \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226039\n", "char_count": 506}, {"efta_number": "EFTA01225932", "page_number": 108, "text_content": "STAR Cluster TriggersTab \nFigure 34: 'STAR Cluster TriggersTab- Value \nsILJ \nasinteeco. \ntin \nQtecopeco \nnavy \naspioing %AD \ntidied \nROW e/M \nr \nGenteel ICannrsabre I Outhed lbedenewskes 1 Encrpst NW. IRSPA I SWIM,* I \nTrigor. \n\"\" A04 \nObtrove \nPreprb \np I Re- 41V Conruncawn \nValue \nnO\n' \nAm= \nDetsls \n1 \nWhen a Trigger is added, an Action must be configured in the Action column. This is the Action that will \noccur when the object's selected Property receives the selected Value. \nd. Click within the column to display a drop-down list of valid actions. Click an Action that you want to include \nas a parameter for the trigger to add it to the column (see Figure 35 on Page 110). \nC•CURE 9000 Hardware Configuration Guide \nChapter< \n109 \nEFTA01226040\n", "char_count": 754}, {"efta_number": "EFTA01225932", "page_number": 109, "text_content": "STAR Cluster Triggers Tab \nF Ig u re 35: 'STAR Cluster T riggers Tab-Action \ns_LJ LI< \na;s ,r end Coat \nHams \nQescnptal \nOaeA \nulinsay ado \ng ERAS \nr airteneact Node \nPenton Dial \nGa-es I Conra.ncetcns I One I Mackey).* I Arta I 6-crwan Troro I Sign I Sta. \nTriggers \n•\" \n,t,Reven \nProws \nVoss \nOffie• \nAmon \nteats \nI Prowy Csowuncatal Siam \n:ayes Feet \nAs the Action is selected, the lower pane in the Triggers box displays a corresponding entry field, or group of \nentry fields, specific to the selected Action, such as an Event or Output (see Figure 36 on Page 110). \nIn the case of the Primary Communications Status Property, the available Action is to activate an event. \nF !gum 36: (STAR Cluster TriggersTab - Action Event \nSent end Cost \nteen \nQescripeco \nCluteA \nvv.'s,' ado \nEtaltd \nr Wobwrince Mode \nPineon Dela \nGerel I Conn.ncaxer l ri ser I ileceIncus I Atte I &cover, NW, I Stems I State tram I \ninsets \nAdd \n'Retch* \nPrivet)*\ntf I Prey\" Contrunicaz4e \nvalw \nAmyxEvent \nOsais\nAnita \nI \neve,' I \nnal \n110 \nChapter 4 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226041\n", "char_count": 1085}, {"efta_number": "EFTA01225932", "page_number": 110, "text_content": "STAR Cluster Triggers Tab \ne. In the Event field, click 0 \nto select a Event that you want to associate with the trigger (see Figure 37 on Page \n111). Events are created in the Configuration Pane. See the C•CURE 9000 Software Configuration Guide for more \ninformation. \nFigure 37: STAR Cluster Triggers Tab• Event Selection \n,IJ \na ssn. end (kis< \n• \nnitne l)xe, A \nP &Sod \nPant Doha \ntiiinl•Wee Me* \nGarai I Connitealive I PAW I Meeellmes hem 1Enaeeee. TKO= I SSA I Salelese I \nr Tryon \n'AM a• Resort \nPoor/\nConort.o.tir 9nt \npaves Ewa \nc._ Stlectro, \nSOW lyto \nKr. itseta \nI\nkea Y \na \nMap colons to co. o‘o by l'<e• \nNate \nI \nPalen \nI \nGoes\nClick Ws so Alb 044 A.\nAll Ewets Glop \nCeba \nOefe.lt SI evens crag \nRevco< Report Re. Waal: \nTM eon It \nobtolaw reptc \nme Cels..li a:1< for back. msni \nAwn loAoci up Es \nWool, \n:eon& loser kw Ev Waal \nTie defrolt nomel log bam, eve \nDence Era Joni T OSA \nns Pee ea Device Ent\" Jame t \nSystem Eno Jared Ott \nTte debit System Enc.bang T \nfinery Loy Journal Ye US! \nThe &lath eery Low Journal To \nke.a Z0O* WO J OSA \nThe *hal hire Zone Enel.:o \nDm Oren \nNISI \n&heft \nMIA \nred \nNISI \nOnce the field (or group of fields) is completed, the Details column will show information about how the \nAction has been configured. \nC•CURE 9000 Hardware Configuration Guide \nChapter 4 \n111 \nEFTA01226042\n", "char_count": 1329}, {"efta_number": "EFTA01225932", "page_number": 111, "text_content": "STAR Cluster Triggers Tab \nFigure 38: STAR Cluster Triggers Tab- Finished \no (\"—I \nI now \nI \nI \nI \n...<4.1 \nVale \nC\ny\n-\nS\nEy.. 1......v 10«...., \nN OTE \nTo activate or ann iSl'AR Cluster events by a trigger condition, the schedule value is restricted to \nAlways. \n3. To Remove a Trigger, select the row using the LL button and click Remove. \nA completed Trigger that notifies you of communications failure in the cluster is shown in Figure 38 on Page \n112. \n4. Navigate to the Status tab or Save and Close to save the cluster and begin configuring iSTAR Controllers. \n112 \nChapter < \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226043\n", "char_count": 639}, {"efta_number": "EFTA01225932", "page_number": 112, "text_content": "iSTAR Cluster Dialup Configuration Tab \niSTAR Cluster Dialup Configuration Tab \nThe Dialup Configuration tab is used to configure a cluster to use dial-up on the iSTAR Pro or Ultra SE Pro Mode \ncontroller. \nSee Chapter 3: Configuring Dialup for the dial-up configuration sequence to follow and configuration information. \nC•CURE 9000 Hardware Configuration Guide \nChapter< \n113 \nEFTA01226044\n", "char_count": 392}, {"efta_number": "EFTA01225932", "page_number": 113, "text_content": "STAR Cluster Status Tab \niSTAR Cluster Status Tab \nThe Status tab provides a read-only listing of critical information about the operational status of the iSTAR \ncontrollers associated with the cluster. Such information include: \n• Cluster Name \n• Comm State \n• Controller Name \n• Conn Path \n• IP Address \n• Boards State \n• IP Address 2 \n• Panel State \n• Type \n• Firmware Version \n• Comm Path \n• Board Type \nThe Details of the selected controller section displays the same status fields that are displayed on that controller's \nStatus tab. For more information on the status fields that are displayed for each controller type, see the iSTAR \nController Status Tab on Page 147. \nThe Status tab is shown in Figure 39 on Page 114. \nF ig u re 39: iSTAR Cluster Status Tab \nLyn. hmo. \nLitwin*. >yr...Ty 9-6, \n&Wed \nNew DOM \nr a.m.< \nMods \n001191 I COMMOSTO WS I 14“.....0J1 I MO I &MOM I \"a- \nStow how mewl \now Smas \nNine\nPew acruiceen \ndala\ntensectai \nI VIA \n0440t \nUSaysT, \n- taselon Sus \nadir Nis \nI Care, Nast \nIP Ales \nIP Alta 2 \nbt• \nConn Ply \n0,4 \n(SW. \n'SW Fay in \n101011 \nMemel \nwirr v.v., \nUt \nQ..• \nEdw.) \n101012 \nNab+ \n.ATten• \nL.kt \nCUP.. \nUral \n101013 \n11-k \nO-.A \nan \n10101A \nirk \nOS* a the solecled caeca. \nN.. \nIw. \nIN, \nIw1.. \n:at \nPenned nab \n0 \nkw. R-rica Wrenn) \n0 \n'cis , \n-... • Itenr, %CI \n0 \n1.... Prone. Yee, XIII \n0 \n, nts Pant W.\" rrs) \n0 \n..e 4trer livre,000 \n0 \n'ad R.'s.% ',rot >00 \n0 \nII I \n—.\n-\na\nUsing the Cluster Status Tab \n1. The Cluster Status box displays Communications Status values for the iSTAR Cluster. \n2. When you select an iSTAR Controller within the Controllers Status list, its status values are displayed in the \nDetails of selected controller box. \n3. Navigate to the State Images tab or Save and Close to save the cluster and begin configuring iSTAR Controllers. \n114 \nChapter < \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226045\n", "char_count": 1882}, {"efta_number": "EFTA01225932", "page_number": 114, "text_content": "'STAR Cluster State Images Tab \nISTAR Cluster State Images Tab \nThe State Images tab, shown in Figure 40 on Page 115, provides a means to change the default images used to \nindicate Cluster states that are displayed in the Monitoring Station. \nFigure 40: ISTAR Cluster State Images Tab \np.15.,•e ..foie \n-NM \nDMedollet uvvena Sub* \nfretikpd \nr \nlade \nPS \nNon \nGrell kteartnotans l osl ilsaihraus Pon I G•cncw l 'VW, l Ion Rae nice. I \nTo Change an Image \n1. Double-click the existing image. \nA Wmdows Open dialog box appears allowing you to browse for a folder in which you have placed \nreplacement images. \n2. When you locate the replacement image, select it to add it to the image listing. \n3. To restore the default image, right-click the new image and select Restore Default \n4. Click Save and Close to save changes to the cluster state images. \nC•CURE 9000 Hardware Configuration Guide \nChapter 4 \n115 \nEFTA01226046\n", "char_count": 921}, {"efta_number": "EFTA01225932", "page_number": 115, "text_content": "STAR Cluster State Images Tab \n116 \nChapter 4 \nC•CURE 9000 Hardware Con figuration Guide \nEFTA01226047\n", "char_count": 103}, {"efta_number": "EFTA01225932", "page_number": 116, "text_content": "5 \nConfiguring C•CURE iSTAR Controllers \nThe C•CURE iSTAR controller is an intelligent controller for networked security systems. C•CURE iSTAR controllers \ncommunicate with the C•CURE 9000 server (acting as a database and journal host) and the system security \nhardware, providing direct control of events and system activity. This chapter explains how to configure iSTAR \ncontrollers, and the devices related to them, in the C•CURE 9000 System. \nIn this chapter \nUnderstanding C•CURE iSTAR Controllers  \n118 \nConfiguration Overview for iSTAR Controllers  \n119 \niSTAR Controller Tasks  \n124 \niSTAR Controller Editor \n137 \niSTAR Controller Editor Tabs  \n141 \niSTAR Ultra Controller Editor Inputs Tab \n178 \niSTAR Ultra Controller ACM Board Editor \n184 \niSTAR Classic/Pro Controller ACM Board Editor \n197 \niSTAR Input Board Editor \n203 \niSTAR Output Board Editor \n208 \niSTAR Ultra Wireless Readers  \n213 \niSTAR Aperio RS-485 Hub Board Editor (iSTAR Ultra only) \n220 \niSTAR PIM-485 Board Editor \n226 \niSTAR Input Editor  \n.232 \niSTAR Output Editor \n241 \niSTAR Reader Editor \n248 \niSTAR PIM-485 Reader Editor \n260 \niSTAR Aperio Reader Editor \n264 \nTriggers Tab for iSTAR Devices  \n270 \nState Images Tab for iSTAR Devices  \n274 \nC•CURE 9000 Hardware Configuration Guide \nChapters \n117 \nEFTA01226048\n", "char_count": 1293}, {"efta_number": "EFTA01225932", "page_number": 117, "text_content": "Understanding C•CURE iSTAR Controlers \nUnderstanding C•CURE iSTAR Controllers \nThe iSTAR controller is an intelligent, network-ready controller for security systems. The heart of the iSTAR controller \nis the General Controller Module ( GCM) - an embedded microprocessor-based controller card. Add-on Access \nControl Modules (ACM Boards) provide access control functionality by supporting readers, outputs, and inputs. The \niSTAR Ultra, Pro, and eX also support Schlage wireless readers and the Ultra also supports Assa Abloy Aperio \nwireless readers. \nTo install and configure the controller hardware and its connected devices see the following manuals: \n• iSTAR Pro Installation and Configuration Guide \n• iSTAR eX Installation and Configuration Guide \n• iSTAR Edge Installation and Configuration Guide \n• iSTAR Ultra Installation and Configuration Guide \n• iSTAR Ultra SE Installation and Configuration Guide \nFor information on configuring host and panel Events for an iSTAR controller, see the Events chapter in the \nC•CURE 9000 Software Configuration Guide. \nThe following sections provide the information you need to configure the iSTAR Controllers. \n• iSTAR Controller Tasks on Page 124 \n• Configuration Overview for iSTAR Controllers on Page 119 \n• iSTAR Controller Editor on Page 137 \n118 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226049\n", "char_count": 1365}, {"efta_number": "EFTA01225932", "page_number": 118, "text_content": "Configuration Overview for STAR Controllers \nConfiguration Overview for iSTAR Controllers \nConfiguring the iSTAR controllers involves setting up the hardware and configuring the software components. See \nthe iSTAR Hardware Installation Guides for instructions about setting up controllers and related hardware. \nNOTE \nBefore configuring a controller, make sure you know the MAC address of the controller NIC you are \nusing. The MAC address is built into the GCM and cannot be changed. You can find a controller's \nMAC address(es) on a label attached to the GCM. \nTo Configure an iSTAR Controller \n1. Create an iSTAR Controller (see Creating an iSTAR Controller on Page 124) or edit an existing iSTAR Controller \n(see Editing an iSTAR Controller on Page 126. The iSTAR Controller General tab appears, as shown in Figure 47 \non Page 142. \n2. On the iSTAR Controller General tab, configure the basic communications settings for the Controller, such as the \nMAC address, the primary and optional secondary network connections, and the Controller Time Zone. \n3. Click on each of the tabs for attached devices, such as the Boards tab for iSTAR Classic/Pro Controllers, or the \nReaders tab for iSTAR eX Controllers, and configure the devices and their settings. \n• For iSTAR Classic/Pro Controllers, refer to the iSTAR Pro Configuration Summary on Page 119. \n• For iSTAR eX/Edge Controllers, refer to the iSTAR eX and iSTAR Edge Configuration Summary on Page 121. \n• For iSTAR Ultra, refer to the iSTAR Ultra Configuration Summary on Page 122. \n4. Click on the iSTAR Triggers tab to configure actions that can activate Events, lock or unlock Doors, sound \naudible alarms, or a wide range of other security functions. \n5. Click on the iSTAR State Images tab to customize the images that are displayed on the Monitoring Station to \nrepresent the Controllers. \n6. Click Save and Close to save your settings. \nNOTE \nWhen using a multi-homed 9000 standalone server with multiple network adapters on multiple \nnet\n... [truncated, 2696 chars — for the full page use /api/corpus/document/EFTA01225932/118 or ?id=EFTA01225932&page=118]", "char_count": 2696}, {"efta_number": "EFTA01225932", "page_number": 119, "text_content": "Configuration Overview for STAR Controllers \nTable 9: STAR Pro Configuration Summary (continued) \nStep \nTask \nReference \n2. \nCreate an STAR Pro Controller under the STAR Cluster in the Hardware Tree. \nCreating an STAR Controller on \nPage 124 \n3. \nUse the STAR Controller General tab to configure the basiccommunications \nsettings for the Controller and to assign Reader LCD Message Sets. \nSTAR Controller General Tab on \nPage 141 \n4. \nUse the Boards tab to create and configure Inputs, Outputs, and ACM boards for \nthe Controller. \nSTAR Controller Boards Tab \n(STAR ClassidPro) on Page 156 \n5. \nOpen the STAR ACM Board Editor tocreate Inputs, Outputs, and Readers for the \nController. \nSTAR Classic/Pro Controller ACM \nBoard Editor on Page 197 \n6. \nUse the ACM Board Inputs tab to create Inputs. \n'STAR ACM Board Inputs Tab on \nPage 198 \nSTAR Input Editor on Page 232 \n• Click el to open the STAR Input Editor to configure each Input. \n7. \nUse the ACM Board Outputs tab to create Outputs. \nSTAR ACM Board Outputs Tab on \nPage 199 \n• Click[] to open the STAR Output Editor to configure each Output. \nSTAR Output Editor on Page 241 \n8. \nUse the ACM Board Readers tab to create Readers. \nSTAR ACM Board Readers Tab \non Page 200 \n• Click[l to open the STAR Reader Editor to configure each Reader. \nSTAR Reader Editor on Page 248 \n9. \nUse the ACM Board ACM EXT tab to create Input and Output Boards. \nSTAR ACM Board ACM Ext Tab \non Page 201 \n10. \nUse the STAR Input Board Editor to Configure an STAR Input Board. \nSTAR Input Board Editor on Page \n203 \n• Click n \nto open the STAR Input Editor to configure each Input. \nSTAR Input Editor on Page 232 \n11. \nUse the STAR Output Board Editor to Configure an STAR Output Board. \nSTAR Output Board Editor on \nPage 208 \n• Click n \nto open the STAR Output Editor to configure each Output. \nSTAR Output Editor on Page 241 \n12. \nIf you have Schlage Wireless PIMs and Readers, use the &Wage Wireless PIMs \ntab to configure these devices. \nSTAR Schlage Wireless PIMs \n... [truncated, 2603 chars — for the full page use /api/corpus/document/EFTA01225932/119 or ?id=EFTA01225932&page=119]", "char_count": 2603}, {"efta_number": "EFTA01225932", "page_number": 120, "text_content": "Configuration Overview for STAR Controllers \niSTAR eX and iSTAR Edge Configuration Summary \n'Fable 10 on Page 121 provides a summary of the tasks involved in configuring an iSTAR eX or iSTAR Edge \nController. \nTable 10: STAR eX/Edge Configuration Summary \nStep \nTask \nReference \n1. \nCreate and save an STAR eX/Edge Cluster for the Controller. \nCreating an STAR Cluster \non Page 88 \n2. \nCreate an STAR eX/Edge Controller under the STAR Cluster in the Hardware Tree. \nCreating an \nSTAR Controller on Page \n124 \n3. \nUse the STAR Controller General tab to configure the basic communications settings for the \nController and to assign Reader LCD Message Sets. \nSTAR Controller General \nTab on Page 141 \n4. \nUse the STAR Controller Inputs tab to create the Inputson the Controller. \nSTAR eX and Edge \nController Inputs Tab on \nPage 159 \n• Click[] to open the STAR Input Editor to configure each Input. \nSTAR Input Editor on Page \n232 \n5. \nUse the STAR Controller Outputs tab to create the Outputs on the Controller. \nSTAR Edge/eX Controller \nOutputs Tab on Page 164 \n• Click ... to open the STAR Output Editor to configure each Output. \nSTAR Output Editor on \nPage 241 \n6. \nUse the STAR Controller Wiegand tab to create the direct connect Wiegand Readerson the \nController. \nSTAR eX Controller \nWiegand Tab on Page 171 \n• Click ... to open the STAR Reader Editor to configure each Reader. \nSTAR Reader Editor on \nPage 248 \n7. \nUse the STAR Controller tabs to create the Input Boards. Output Boards, and Readers on the \nController. \nSTAR eXCOM1/COM2 \nTabs on Page 173 \nSTAR Edge \nCOM1/COM2/COM3 Tabs \non Page 167 \n8. \nUse the STAR Input Board Editor to Configure an STAR Input Board. \nSTAR Input Board Editor on \nPage 203 \n• Click[i to open the STAR Input Editor toconfigure each Input. \nSTAR Input Editor on Page \n232 \n9. \nUse the STAR Output Board Editor to Configure an STAR Output Board. \nSTAR Output Board Editor \non Page 208 \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n121 \nEFTA01226052\n", "char_count": 1996}, {"efta_number": "EFTA01225932", "page_number": 121, "text_content": "Configuration Overview for STAR Controllers \nTable 10: STAR eX/Edge Configuration Summary (continued) \nStep \nTask \nReference \n• Mk in to open the STAR Output Editor to configure each Output. \nSTAR Output Editor on \nPage 241 \n10. \nClick [—Ito open the STAR Reader Editor to configure each Reader. \nSTAR Reader Editor on \nPage 248 \n11. \nIf you have &Maga Wireless PIMs and Readers, open the STAR PIM-485 Board editor to configure \nthese devices. \nSTAR PIM-485 Board Editor \non Page 226 \n12. \nFrom the Hardware Tree, create STAR Door objects for the Controller. \nSTAR Door Editor on Page \n427 \n13. \nFrom the Hardware Tree. create STAR Elevator objects for the Controller. \nSTAR Elevatorson Page \n505 \n14. \nUse the STAR Triggers tab to create new triggers for the Controller. \niSTAR Controller Triggers \nTab on Page 147 \n15. \nUse the STAR State Images tab to change the images that displayon the Monitoring Station for the \niSTAR Controller. You can substitute a .JPG image for anyof the default state images. \niSTAR Controller State \nImages Tab on Page 152 \niSTAR Ultra Configuration Summary \nTable 11 on Page 122 provides a summary of the tasks involved in configuring a iSTAR Ultra Controller. \nTable 11: STAR Ultra Configuration Summary \nStep \nTask \nReference \n1 \nCreate and save an iSTAR Ultra Cluster for the Controller. \nCreating an STAR Cluster on Page 88 \n2 \nCreate an STAR Ultra Controller under the STAR Cluster in the Hardware Tree. \nCreating an STAR Controller on Page 124 \n3 \nUse the STAR Controller General tab to <>colligate the basicoommunications settings for \nthe Controller and to assign Reader LCD Message Sets. \nSTAR Controller General Tab on Page 141 \n4 \nUse the Boards tab to create and configure Inputs, Outputs, and ACM boards for the \nController. \nSTAR Controller Boards Tab (STAR \nClassic/Pro) on Page 156 \n5 \nOpen the STAR ACM Board Editor to create Inputs. Outputs. and Readers for the \nController. \nSTAR Classic/Pro Controller ACM Board \nEditor on Page 197 \n6 \nUse the ACM \n... [truncated, 2446 chars — for the full page use /api/corpus/document/EFTA01225932/121 or ?id=EFTA01225932&page=121]", "char_count": 2446}, {"efta_number": "EFTA01225932", "page_number": 122, "text_content": "Configuration Overview for STAR Controllers \nTable 11: STAR Ultra Configuration Summary (continued) \nStep \nTask \nReference \n10 \nUse the ACM Wiegand tab to create Wiegand-connected Readers. \nSTAR Ultra ACM Board Wiegand Tab on \nPage 184 \n11 \nClick[i to open the STAR Reader Editor to configure each Reader. \nSTAR Reader Editor on Page 248 \n12 \nUse the ACM Board RS-485 tab to create RS-485 Ports for Readers. \nSTAR Ultra ACM Board RS-485 Tab on \nPage 186 \n13 \nClick ri  to open the STAR Device Port Editor to configure each RS-485 Reader and \nrelated Inputs. \nSTAR Ultra ACM RS-485 Device Port \nEditor on Page 188 \n14 \nUse the ACM Board RS-485 Device Port Reader tab to configure RS-485 Readers. \nSTAR Ultra RS-485 Device Port Readers \nTab on Page 190 \n15 \nUse the ACM Board RS-485 Device Port ACM Ext tab to configure Input and Output \nBoards. \nSTAR Ultra RS-485 Device Port ACM EXT \nTab on Page 192 \n16 \nUse the STAR Input Board Editor to Configure an STAR Input Board. \nSTAR Input Board Editor on Page 203 \n17 \nClick rito open the STAR Input Editor to configure each Input. \nSTAR Input Editor on Page 232 \n18 \nUse the STAR Output Board Editor to Configure an STAR Output Board. \nSTAR Output Board Editor on Page 208 \n19 \nClick n \nto open the STAR Output Editor toconfigure each Output. \nSTAR Output Editor on Page 241 \n20 \nClick the Com1 and Com2 tab to configure Aperio Hubs \nSTAR Ultra COM1/COM2 Tabson Page \n181 \nClidC toopen the STAR Aperio RS-485 Hub Board editor to configure the \nCommunications Fail Input and STAR Aperio Readers. \nSTAR Aperio RS-485 Hub Board Editor \n(STAR Ultra only) on Page 220 \nClick[i to open the STAR Aperio Reader editor to configure STAR Aperio readers. \niSTAR Aetna Reader Editor on Page 264 \nFrom the Hardware Tree. create iSTAR Door objects for your Controller. \nSTAR Door Editor on Page 427 \nFrom the Hardware Tree. create STAR Elevator objects for your Controller. \nSTAR Elevatorson Page 505 \nUse the STAR Triggers tab to create new triggers for your Controlle\n... [truncated, 2299 chars — for the full page use /api/corpus/document/EFTA01225932/122 or ?id=EFTA01225932&page=122]", "char_count": 2299}, {"efta_number": "EFTA01225932", "page_number": 123, "text_content": "STAR Controller Tasks \niSTAR Controller Tasks \nYou can perform the following tasks to manage iSTAR Controllers. \n■ Creating an iSTAR Controller on Page 124 \n■ Creating a Controller Template on Page 125 \n■ Deleting an iSTAR Controller on Page 126 \n■ Editing an iSTAR Controller on Page 126 \n■ Viewing a List of iSTAR Controllers on Page 127 \n■ Using Set Property for an iSTAR Controller on Page 130 \n■ Add a Hardware Device to Group from a Dynamic View on Page 409 \nCreating an iSTAR Controller \nYou can create a new iSTAR Controller only within an iSTAR Cluster of the appropriate type. \nNOTE \nThe iSTAR Ultra S1-1 encryption switch enables FIPS 197 AES 256-bit encryption. The switch setting \nmust match the software configuration of the cluster and the controller. See the iSTAR Ultra \nInstallation and Configuration Guide for more information. \nTo Create a iSTAR Controller \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Navigate to the Hardware folder that contains the iSTAR Cluster in which you want to create the new Controller. \n3. Select the iSTAR Cluster and right-click to display the context menu. \n4. Select the controller you wish to create: \nNOTE \nFor an iSTAR Ultra SE in Pro Mode, select iSTAR Pro Controller. \n■ For an Encrypted Ouster, you can select: \n• iSTAR Edge Controller>New \n• iSTAR eX Controller>New \n• iSTAR Ultra Controller>New \n■ For a Non-encrypted Cluster, you can select: \n• iSTAR Classic Controller>New \n• iSTAR Pro Controller>New \n• iSTAR Ultra Controller>New \nThe iSTAR Controller Editor opens to allow you to configure the Controller (see iSTAR Controller General Tab on \nPage 141). \n5. Type a unique name for the controller in the Name field. \n6. Type a textual description (optional) in the Description field. \n124 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226055\n", "char_count": 1882}, {"efta_number": "EFTA01225932", "page_number": 124, "text_content": "ISTARControier Tasks \n7. Enter the MAC Address of the iSTAR Controller in the MAC Address field (if you do not, you will receive an \nerror when you try to save the Controller). \n8. To save the new iSTAR controller, click Save and Close. \nCreating a Controller Template \nYou can create a template for an iSTAR Controller. A Controller Template saves you time because you can save the \nconfiguration settings and re-use the template to create new Controller objects with the those settings pre-defined. \nTo Create a Controller Template \n1. In the Navigation pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Navigate to the Hardware folder that contains the iSTAR Cluster in which you want to create the new Controller \nTemplate. \n3. Select the iSTAR Cluster and right-click to display the context menu. \n4. Select the iSTAR controller you wish to create a template for: \n■ iSTAR Edge Controller>New Template. \n■ iSTAR eX Controller>New Template. \n■ iSTAR Classic Controller>New Template. \n■ iSTAR Pro Controller>New Template. \n■ iSTAR Ultra Controller>New Template. \n5. The iSTAR Controller Editor opens a new Template. \n6. Configure any settings you want to include in the Template. \n7. To save the new iSTAR Controller Template, click Save and Close. \nThe new Controller template appears under — Templates in the iSTAR Controller context menu drop-down list in the \nHardware tree. \nTo Create an iSTAR Controller from a Template \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Navigate to the Hardware folder that contains the iSTAR Cluster in which you want to create the new Controller. \n3. Select the iSTAR Cluster and right-click to display the context menu. \n4. Select iSTAR Controller and click the Template you want to use from the context menu. \n5. The iSTAR Controller Editor opens so that you can edit the new Controller. The settings from your Template are \nalready configured. \n6. Configure a\n... [truncated, 2240 chars — for the full page use /api/corpus/document/EFTA01225932/124 or ?id=EFTA01225932&page=124]", "char_count": 2240}, {"efta_number": "EFTA01225932", "page_number": 125, "text_content": "STAR Controller Tasks \nDeleting an iSTAR Controller \nYou can delete an iSTAR Controller from the Hardware tree, or one or more iSTAR Controllers from a Dynamic \nView. \nTo Delete an iSTAR Controller from the Hardware Tree \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Navigate to the iSTAR Cluster that contains the Controller that you want to delete. \n3. Right-click on the iSTAR Controller that you want to delete and select Delete from the context menu. \n4. Click Yes in the \"Are you sure you want to delete the selected iSTAR Controller object?\" message box. A \ndialog box appears showing the progress of the deletion. \n5. When the object has been deleted, click one of the following buttons: \n• OK to close the dialog box. \n• Print to print the deletion message. \n• Email to send the deletion message to the email address you have configured in the Customer Support \nsection of the C•CURE 9000 System Variables. \nTo Delete iSTAR Controllers from a Dynamic View \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select iSTAR Controller from the Hardware pane drop-down list. \n3. Click L i to open a Dynamic View showing all iSTAR Controller objects. \n4. Select one or more iSTAR controllers from the Dynamic View list of iSTAR Controllers. \n5. Right-click one of the Controllers in the list that you want to delete and select Delete from the context menu. \n6. Click Yes in the \"Are you sure you want to delete the selected iSTAR Controller object(s)?\" message box. A \ndialog box appears showing the progress of the deletion(s). \n7. When the object(s) have been deleted, click one of the following buttons: \n• OK to close the dialog box. \n• Print to print the deletion message. \n• Email to send the deletion message to the email address you have configured in the Customer Support \nsection of the C•CURE 9000 System Variables. \nEditing an iSTAR Controller \nYou can edit an iSTAR\n... [truncated, 2369 chars — for the full page use /api/corpus/document/EFTA01225932/125 or ?id=EFTA01225932&page=125]", "char_count": 2369}, {"efta_number": "EFTA01225932", "page_number": 126, "text_content": "'STAR Controls( Tasks \n3. Click i s  to open a Dynamic View showing all iSTAR Controller objects. \n4. Double-click the Controller in the list that you want to modify and select Edit from the context menu. The iSTAR \nController editor opens (see iSTAR Controller Editor on Page 137). \n5. See Configuration Overview for iSTAR Controllers on Page 119 for information about how to use the iSTAR \nController Editor to configure your iSTAR Controller. \nViewing a List of iSTAR Controllers \nYou can view a list of iSTAR Controllers in a Dynamic View. \nTo View a List of iSTAR Controllers \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select iSTAR Controller from the Hardware pane drop-down list. \n3. Click i s  to open a Dynamic View showing all iSTAR Controller objects \n4. You can filter, group, and print the list of iSTAR Controllers in the Dynamic View. See the C•CURE 9000 Data \nViews Guide for more information about using the features provided by Dynamic Views. \n5. You can select one or more Controllers in the list (using CTRL+Left-click or SHIFf+Left-click for multiple \nselection) and right-click to display a context menu (see Viewing a List of iSTAR Controllers on Page 127). \nUsing the iSTAR Controller Context Menu \nTo access the controller context menu, right-click on a controller in the Hardware tree or in the Dynamic View. \nThe selections described in Table 1 on Page 127 are not available for all controllers. \nTable 1: 'STAR Controls( Context Menu \nSelection \nDescription \nEdit \nClick this menu selection to edit the selected iSTAR Controller. The iSTAR Controller editor opens. You \ncan rename the iSTAR Controller, change its description, and any other attributes. \nDelete \nClick this menu selection to delete the selected iSTAR Controller(s). A prompt appears asking you to \nconfirm that you want to delete the iSTAR Controller. Click Yes to delete the Input or No to cancel the \ndeletion. \nWhen you delete an iSTAR Co\n... [truncated, 2161 chars — for the full page use /api/corpus/document/EFTA01225932/126 or ?id=EFTA01225932&page=126]", "char_count": 2161}, {"efta_number": "EFTA01225932", "page_number": 127, "text_content": "STAR Controller Tasks \nTable 1: STAR Controller Context Menu (continued) \n.... \nSelection \nDescription \nSet Property \nClick this menu selection to change the value of a property in the selected controller(s). \nA dialog box appears asking you to select a property to change. Click ri  to open a selection list and \nclick the property you wish to change. You can change the value of the following STAR Controller \nproperties: \n• Description - You can change the textual description of the STAR Controller(s) by selecting this \nproperty and typing in a new value. \n• Enabled - You can determine whether or not the STAR Controller(s) are enabled to \ncommunicate to the Administration or Monitoring Station by selecting this property and \nselecting/clearing the value check box. \n• Power Suppression -Allows you to select or clear this value for the selected controller. \nSee Using Set Property for an iSTAR Controller on Page 130. \nAdd to Group \nClick this menu selection to add the STAR Controller to a Group.A dialog boxlisting the STAR \nController Groups in the system appears. Click on a Group in the list to add the STAR Controller(s) to \nthat Group. See Add a Hardware Device to Group from a DynamicView on Page 409. \nExport Selection \nOpens an Export dialog box from which you can export one or more records d ispLayed in a Dynamic \nView to either an XML or a CSV file. This allows you to quickly and easitycreate XML/CSV reportson \nselected C•CURE 9000 data. \nNOTE: Although XML is the initial default file type, once you choose a type in the Save as type field. \nwhether XML or CSV, that becomes the default the next time this dialog box opens. \nCSV-formatted exports cannot be imported. If you require importing functionality, export to \nXML. \n• When you export to an XML file, all available data for the selected object(s), whether displayed in \nthe Dynamic View or not—aswellasallthechild objects of the selected record(s), is exported. \n• When you export to a CSV file, ontydata in the oalum\n... [truncated, 3590 chars — for the full page use /api/corpus/document/EFTA01225932/127 or ?id=EFTA01225932&page=127]", "char_count": 3590}, {"efta_number": "EFTA01225932", "page_number": 128, "text_content": "STAR Controller Tasks \nTable 1: STAR Controller Context Menu (continued) \nSelection \nDescription \nFind in Journal \nOpens a Query Parameters dialog box in which you can enter prompts and/or modify the query criteria \nto search for entries in the Journal that reference the selected STAR Controller. The resuttsdisplay in a \nseparate Dynamic View. This selection is not available if you select multiple Controllers. \nPerform Full \nController \nDownload \nDownloads configuration and personnel records appropriate to the controller. \nDiagnostics \nOpens the STAR Diagnostics System web page for this Controller, providing you with the controller's \nstatus. This selection is not available d you select multiple Controllers. \nTurn \nMaintenance \nMode On \nOpens the Maintenance Mode dialog box to put the STAR Controller and/or its oom ponents into \nMaintenance Mode. See Chapter 2: Maintenance Mode for more information. \nTurn \nMaintenance \nMode Off \nOpens the Maintenance Mode dialog box to take the STAR Controller and/or its components out of \nMaintenance Mode. See Chapter 2: Maintenance Mode for more information. \nCopy & Paste \nUsed to make a duplicate of a Cluster and its Child Objects on the same partition on the same system. \nSee Copying. Pasting, and Renaming Clusters and Controllers on Page 40. \nCopy To \nUsed to make a duplicate of a Cluster and its Child Objects on a different partition on the same system. \nusing Pasta From. See Copying. Pasting, and Renaming Clusters and Controllerson Page40. \nPaste From \nThe Copy To and Pasta Fromcontext menu selectionscan be used to duplicate Clusters and \nChildren on another system. See Copying, Pasting, and Renaming Clusters and Controllerson Page \n40. \nMonitor \nClick this menu selection to view activity for the selected STAR Controller(s). and any Add-on Board. \nDoor. Elevator, Input. Output. Reader, and Trigger-with-target-Event children, on an Admin Monitor \nActivity Viewer. \nNOTE: Which Add-on Boards display on the Monitor—as well as whi\n... [truncated, 2922 chars — for the full page use /api/corpus/document/EFTA01225932/128 or ?id=EFTA01225932&page=128]", "char_count": 2922}, {"efta_number": "EFTA01225932", "page_number": 129, "text_content": "STAR Controller Tasks \nTable 1: STAR Controller Context Menu (continued) \nSelection \nDescription \nSTAR Door \nClick t000nfigure a new door or a door template. \nElevator \nClick to configure a new elevator or an elevator template. \niSTAR Input \nClick to configure a new input or an input template. \nOutput \nClick toconfigure a new output or an output template. \niSTAR Reader \nClick to configure a new reader or a reader template. \nUsing Set Property for an iSTAR Controller \nYou can use Set Property to quickly set a property for a Controller without opening the iSTAR Controller Editor. Set \nProperty allows you to select multiple Controllers in a Dynamic View and right-click to set a specific property for all \nof them. So, for example, if you wanted to change a setting for 20 Controllers, you could select all of them and do it \nin one step. \nTo Set a Property for an iSTAR Controller \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select iSTAR Controller from the Hardware pane drop-down list. \n3. Click mai to open a Dynamic View showing all iSTAR Controller objects. \n4. Select the iSTAR Controllers in the list for which you want to set a property, using multiple selection (CTRL+Left-\nclick to select more than one Controller, or SHIFT+Left-click to select a range of Controllers) as needed. \n5. Right-click a selected iSTAR Controller and select Set Property from the context menu. \n6. Click 0 \nin the Property field to open a selection dialog box and select the property you want to set. \n7. Enter the value for the property in the Value field and click OK. \nUpdating iSTAR Firmware (Ethernet Connections) \nYou can update the iSTAR firmware on iSTAR panels using Ethernet connections from either the Administration \nClient or the Monitoring Station client. \nYou can initiate a firmware update by right-clicking on the iSTAR controller: \n■ In the Hardware Tree \n■ In a Dynamic View in the Administration Client \n■ In the Status Lis\n... [truncated, 2113 chars — for the full page use /api/corpus/document/EFTA01225932/129 or ?id=EFTA01225932&page=129]", "char_count": 2113}, {"efta_number": "EFTA01225932", "page_number": 130, "text_content": "STAR Contro!er Tasks \nTo Update Firmware on an iSTAR Controller \nRight-click on the controller and select Update Firmware from the context menu as shown in Figure 41 on Page \n?I .\nFigure 41: 'STAR Context Menu \nNOTE \nEdit \nx \nD. \nDelete \nSet property \nAdd to group \nExport selection... \nFind in Audit log... \nAnd in Journal... \nPerform Full Controller Download \nUpdate Firmware... \nDiagnostics... \nTurn Maintenance Mode On \nCopy and Paste... \nCopy To... \nMonitor \nConnect Dialup Panel—\nReset Di*, Panel \nShow Associations \nUpdate Firmware will not appear on the context menu if the iSTAR is not Enabled or is off-line. \nThe Firmware Download dialog box, shown in Figure 42 on Page 132, opens. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n131 \nEFTA01226062\n", "char_count": 765}, {"efta_number": "EFTA01225932", "page_number": 131, "text_content": "STAR Controller Tasks \nFigure 42: Firmware Download Dialog Box \nFirmware Doamioad \nController Herne real real ear \nCurrentVersion: 5.1.3.1910534 \nAvalable Won \n5.1O19007A \n5.1.3,1910534 \n5.1.5.19109N \n5.1.6.1911034 \n5.1.7.19201)4 \n5.1.8.1930234 \n5.1519403)4 \n5201960234 \n52.1.1970534 \n•l\nSattirmwara doveload \n2. Select the firmware version that you want to download from the list in the dia og box. \n3. Click Start firmware download. A progress bar shows you when the download is completed. \n4. When the download has completed, click Close to close the dialog box. \nUpdating iSTAR Firmware (Dial-up Connections) \nYou can update the iSTAR firmware on iSTAR Pro and iSTAR Ultra SE Pro Mode panels using dial-up from either \nthe Administration Client or the Monitoring Station client. \nYou can initiate a firmware update by right-clicking on the iSTAR controller: \n■ In the Hardware Tree \n■ In a Dynamic View in the Administration Client \n■ In the Status List - Controller in the Monitoring Station \nTo Update Firmware on an iSTAR Controller \nI. Manually connect to the dial-up iSTAR controller. Right-click on the dial-up iSTAR controller and select Connect \nDialup Panel as shown in Figure 43 on Page 133. \n132 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226063\n", "char_count": 1278}, {"efta_number": "EFTA01225932", "page_number": 132, "text_content": "STAR Controller Tasks \nFigure 43: STAR Context Menu• Dialup Connection \nEdit \nDelete \nSet property \nAdd to group \nExact seleclicc... \nAnd it Audit log... \nAnd in Journal... \nPerform Full Contraer Dowrioad \nDiagnostic... \nTurn Maintenance Mode On \nCopy and Paste... \nCopy To... \nMonitor \nConnect Dialup Panel... \n I \nReset DIalup Panel \nThe Manual Actions dialog box, shown in Figure 44 on Page 133, opens. \nFigure 44: ManualAction Dialog Box \ndi:nein:Moue \nwt \nitini)15 1233PM \nEnd I n1320150 33PM \nnary \nTorre ;w I \ninoucbcns \n2. Ensure that the Start and End Time is set to a minimum of two hours. \n3. Click Save and Close. \n4. After the connection is established, right-click on the controller and select Update Firmware as shown in Figure \n45 on Page 134. \nNOTE \nUpdate Firmware will not appear on the context menu if the iSTAR is not Enabled or is off-line. \nC•CURE 9000 Hardware Con figutation Guide \nChapter 5 \n133 \nEFTA01226064\n", "char_count": 936}, {"efta_number": "EFTA01225932", "page_number": 133, "text_content": "STAR Controller Tasks \nF igu re 45: STAR Context Menu - Update Firmware \nEdit \nX \nFif \n0. \nDelete \nSet property \nAdd to group \nExport selection... \nFind in Audit Log... \nFind in Journal... \nPerform Full Controller Download \nUpdate Firmware... \nDiagnostics... \nTurn Maintenance Mode On \nCopy and Paste... \nCopy To... \nMonitor \nConnect Dialup Panel... \nReset Dialup Panel \nShow Associations \nThe Firmware Download dialog box, shown in Figure 46 on Page 134, opens. \nFigure 48: Firmware Download \nAyala* *mons \n5.1019007A \n5.1.3.19105A \n5.1.5.19109A \n5.1.6.19110A \n5.1.7.19101 a \n5.1819002i \n5.1.9.19403t4 \n2 0 19602A \n5 2 1 19705,4 \n5. Select the firmware version that you want to download from the list in the dialog box. \n6. Click Start firmware download. A progress bar shows you when the download is completed. \n7. When the download has completed, click Close to close the dialog box. \n134 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226065\n", "char_count": 959}, {"efta_number": "EFTA01225932", "page_number": 134, "text_content": "STAR Controller Tasks \niSTAR Firmware Updates Using ICU \nYou can use the ICU (iS'FAR Configuration Utility) to quickly download firmware updates to one or more controllers. \nCopy the new firmware file to C:\\Program Files (x86) Tyco WrossHre \\ ServerComponents istar \\ICU \\Firmware \n(the default folder location) before starting the download process. \nBefore starting the firmware download, note the following: \n• If you moved the ICU folder, then you must go back to the Controller dialog box and change the Server Root \nDirectory to match that path. See the ICU help for information about changing the Server Root Directory. \n• If the default Server HTTP Port (9701) that is used for firmware downloads is in use by another application, you \nhave to specify another port to use for firmware downloads. See the ICU help for information about changing the \nServer Root Directory. \nNOTE \nThese procedures use default passwords. If you changed the default passwords, then you must use \nthose. \nTo Download Firmware to the Controller Using the ICU \nNOTE \nIf you are downloading firmware to a controller using dialup, perform the following steps before you \ndownload the firmware: \n1. Right-click on the controller an select Connect to Controller. \n2. Monitor the connection in the Monitoring Station. Once complete, proceed to Step 1 below. \n1. Click the Options & Tools pane. \n2. Click ICU. \n3. Enter the ICU password and click OK. The default password is manager. The ICU starts and the main window \nopens. \n4. Select the controller(s) that you want to update. You can select multiple controllers by pressing the Ctrl key while \nyou are selecting them. \n5. After selecting the controller(s), right-click in the ICU window and select Download Firmware from the context \nmenu. \n6. You are prompted for a password if the iSTAR controller is an Ultra or Ultra SE. \nEnter iSTAR, the default password and click OK. \n7. Click Browse and navigate to C:\\Program Files (x86) Tyco \\ CrossHre ServerComponents \\ist\n... [truncated, 2517 chars — for the full page use /api/corpus/document/EFTA01225932/134 or ?id=EFTA01225932&page=134]", "char_count": 2517}, {"efta_number": "EFTA01225932", "page_number": 135, "text_content": "STAR Controller Tasks \nNOTE \nThe controller may reboot more than once during the upgrade process. \n• To cancel a download, select the controller and right-click to select Cancel Download from the context menu. \n• If a Controller returns a Download Failed message, you can select the controller and right-click to select Retry \nfrom the context menu to restart the firmware download. \n9. When all of the downloads have completed, click Exit to close the Firmware Download dialog box. \nChanging the Time Zone of an iSTAR Controller \nYou can change the value of the iSTAR controller Time Zone field only when the iSTAR Controller is not enabled \n(Enabled field is blankO). You must edit the controller, clear the Enabled field, save the controller, then re-open it to \nchange the Time Zone. \nIf you change the Time Zone of the iSTAR controller, the Time Zone settings of all child objects of that \niSTAR controller are changed as well. A warning message appears if you change the Time Zone and any Events or \nTriggers have controller-based actions on this iSTAR controller and the Event is configured to use a different Time \nZone than this iSTAR controller. \nHost-based actions with Schedules respect the controller Time Zone: a host-based Event that unlocks doors according \nto a Schedule uses the controller Time Zone to determine when the Schedule is active for devices on that controller. \nHowever, if a Time Zone is assigned to the host-based Event itself, the Event actions will activate on the Schedule \nbased on the host Time Zone. \nExample: \nWith a C•CURE 9000 Server in the Eastern US Time Zone (GMT -5:00) and an iSTAR controller in the Central \nUS Time Zone (GMT -6:00): \n■ A host Event that does not include an Event Time Zone unlocks specific Doors by Schedule on an iSTAR \ncontroller according to the controller Time Zone. \n■ A host Event that includes an Event Time Zone unlocks specific doors by Schedule on an iSTAR controller \naccording to the C•CURE 9000 Server Time Zone. \nTo Chang\n... [truncated, 2521 chars — for the full page use /api/corpus/document/EFTA01225932/135 or ?id=EFTA01225932&page=135]", "char_count": 2521}, {"efta_number": "EFTA01225932", "page_number": 136, "text_content": "STAR Controller Editor \niSTAR Controller Editor \nThe iSTAR Controller editor dialog box allows you to configure an iSTAR Controller and its attached devices. \nYou use the iSTAR Controller editor to configure the Controller settings and specify the Inputs, Outputs, and Readers \nthat are connected to the Controller. \nFor information about the iSTAR Controller editor for a specific iSTAR model, see: \n■ iSTAR Classic Controller Editor on Page 137 \n■ iSTAR Pro Controller Editor on Page 137 \n■ iSTAR eX Controller Editor on Page 138 \n■ iSTAR Edge Controller Editor on Page 139 \n■ iSTAR Ultra Controller Editor on Page 139 \niSTAR Classic Controller Editor \nOn iSTAR Classic Controllers, you can configure the GCM and any installed ACM Boards. Two ACM Boards can be \ninstalled on an iSTAR Classic Controller. \nThe iSTAR Classic Controller Editor has the tabs listed in Table 12 on Page 137. \nTable 12: STAR Classic Controller Editor Tabs \nTab \nSee... \nGeneral Tab \nSTAR Controller General Ta b on Page 141 \nBoards Tab \nSTAR Controller Boards Tab (STAR ClassidPro) on Page 156 \n&Maga Wireless PIMs Tab \nSTAR Schlage Wireless PIMs Tab on Page 153 \nTriggers Tab \nSTAR Controller Triggers Tab on Page 147 \nGroups Tab \nGroups Tab for Hardware Devices Oil Page 28 \nStatus Tab \nSTAR Controller Status Tab on Page 147 \nUser Defined Fields Tab \nSTAR Controller User Defined Fields Tab on Page 151 \nState Images Tab \nSTAR Controller State Images Tab on Page 152 \niSTAR Pro Controller Editor \nOn iSTAR Pro Controllers, you can configure the GCM and any installed ACM Boards. Two ACM Boards can be \ninstalled on an iSTAR Pro Controller. \nThe iSTAR Pro Controller Editor has the tabs listed in Table 13 on Page 138. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n137 \nEFTA01226068\n", "char_count": 1772}, {"efta_number": "EFTA01225932", "page_number": 137, "text_content": "STAR Controller Editor \nTable 13: STAR Pro Controller Editor Tabs \nTab \nSee... \nGeneral Tab \nSTAR Controller General Tab on Page 141 \nBoards Tab \nSTAR Controller BoardsTab (iSTAR Classic/Pro) on Page 156 \n&Wage Wireless PIMs Tab \nSTAR &Maga Wireless PIMs Tab on Page 153 \nTriggers Tab \nSTAR Controller Triggers Tab on Page 147 \nGroups Tab \nGroupsTab for Hardware Deviceson Page 28 \nStatus Tab \nSTAR Controller Status Tab on Page 147 \nUser Defined FieldsTab \nSTAR Controller User Defined Fields Tab on Page 151 \nState Images Tab \nSTAR Controller State Images Tab on Page 152 \niSTAR eX Controller Editor \nOn iSTAR eX Controllers, you can configure the GCM and any boards connected to the Power Management Board \n(PM B). \nThe tabs for the iSTAR eX Controller Editor are listed in Table 14 on Page 138. \nTable 14: STAR eX Controller Editor Tabs \nTab \nSee... \nGeneral Tab \nSTAR Controller General Tab on Page 141 \nInputs Tab \nSTAR eX and Edge Controller Inputs Tab on Page 159 \nOutputs Tab \nSTAR Edge/eX Controller Outputs Tab on Page 164 \nWiegand Tab \nSTAR eX Controller Wiegand Tab on Page 171 \nCOM1 Tab \nSTAR eX COM1/COM2 Tabson Page 173 \nCOM2 Tab \nSTAR eX COM1/COM2 Tabson Page 173 \nTriggers Tab \nSTAR Controller Triggers Tab on Page 147 \nGroups Tab \nGroups Tab for Hardware Deviceson Page 28 \nStatus Tab \nSTAR Controller Status Tab on Page 147 \nUser Defined FieldsTab \nSTAR Controller User Defined Fields Tab on Page 151 \nState Images Tab \nSTAR Controller State Images Tab on Page 152 \n138 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226069\n", "char_count": 1557}, {"efta_number": "EFTA01225932", "page_number": 138, "text_content": "STAR Controller Editor \niSTAR Edge Controller Editor \n\"lhe tabs for the iSTAR Edge Controller Editor are listed in Table 15 on Page 139. \nTable 15: iSTAR Edge Controler Editor Tabs \nTab \nSae... \nGeneral Tab \niSTAR Controler General Tab on Page 141 \nInputs Tab \niSTAR eX and Edge Controller Inputs Tab on Page 159 \nOutputs Tab \niSTAR Edge/eX Controler Outputs Tab on Page 164 \nWiegand Tab \niSTAR Edge Controler Wiegand Tab on Page 169 \nCOM1 Tab \nSTAR Edge COM1/COM2/COM3 Tabs on Page 167 \nCOM2 Tab \niSTAR Edge COM1/COM2/COM3 Tabs on Page 167 \nCOM3 Tab \niSTAR Edge COM1/COM2/COM3 Tabs on Page 167 \nTriggers Tab \niSTAR Controler Triggers Tab on Page 147 \nGroups Tab \nGroups Tab for Hardware Devices on Page 28 \nStatus Tab \niSTAR Controler Status Tab on Page 147 \nUser Defined Fields Tab \nSTAR Controler User Defined Fields Tab on Page 151 \nState Images Tab \niSTAR Controller State Images Tab on Page 152 \niSTAR Ultra Controller Editor \nThe tabs for the iSTAR Ultra Controller Editor tabs are listed in Table 16 on Page 139. \nTable 16: STAR Ultra Controler Editor Tabs \nTab \nGeneral Tab \niSTAR Controler General Tab on Page 141 \nInputs \nSTAR Ultra Controller Editor Inputs Tab on Page 178 \nBoards Tab \niSTAR Ultra Controller Boards Tab on Page 179 \nIP ACM's Tab \nSTAR Ultra Controller IP-ACMs Tab on Page 181 \nCOM1 Tab \niSTAR Ultra COM1/COM2 Tabs on Page 181 \nCOM2 Tab \niSTAR Ultra COM1/COM2 Tabs on Page 181 \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n139 \nEFTA01226070\n", "char_count": 1477}, {"efta_number": "EFTA01225932", "page_number": 139, "text_content": "STAR Controller Editor \nSTAR Ultra Controller Editor Tabs (continued) \nTab \nSee... \nTriggers Tab \niSTAR Controller Triggers Tab on Page 147 \nGroups Tab \nGroupsTab for Hardware Deviceson Page 28 \nStatus Tab \nSTAR Controller Status Tab on Page 147 \nUser Defined Fields Tab \nSTAR Controller User Defined Fields Tab on Page 151 \nState Images Tab \nSTAR Controller State Images Tab on Page 152 \n140 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226071\n", "char_count": 460}, {"efta_number": "EFTA01225932", "page_number": 140, "text_content": "STAR Controller Editor Tabs \niSTAR Controller Editor Tabs \nThe iSTAR Controller editor tabs available depend on the iSTAR Controller type. \nThe iSTAR Controller editor basic tabs and iSTAR specific tabs are listed below. \nBasic Tabs \n■ iSTAR Controller General Tab on Page 141 \n■ iSTAR Controller Boards Tab (iSTAR Classic/Pro) on Page 156 \n■ iSTAR Controller Triggers Tab on Page 147 \n■ iSTAR Controller Status Tab on Page 147 \n■ iSTAR Controller State Images Tab on Page 152 \n■ iSTAR Controller User Defined Fields Tab on Page 151 \niSTAR Specific Tabs \n■ iSTAR Schlage Wireless PIMs Tab on Page 153 \n■ iSTAR eX and Edge Controller Inputs Tab on Page 159 \n■ iSTAR Edge/eX Controller Outputs Tab on Page 164 \n■ iSTAR Edge COM1/COM2/COM3 Tabs on Page 167 \n■ iSTAR Edge Controller Wiegand Tab on Page 169 \n■ iSTAR eX Controller Wiegand Tab on Page 171 \n■ iSTAR eX COM1/COM2 Tabs on Page 173 \n■ iSTAR Ultra Controller Editor Inputs Tab on Page 178 \n■ iSTAR Ultra COM1/COM2 Tabs on Page 181 \n■ iSTAR Ultra Controller IP-ACMs Tab on Page 181 \niSTAR Controller General Tab \nThe iSTAR Controller General tab provides a means to set the controller's Onboard and PCMCIA Ethernet adapters, \nMAC address, RM LCD Messages, and Time Zone. \nNOTE \nPCMCIA Ethernet adapters have not been evaluated by UL. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n141 \nEFTA01226072\n", "char_count": 1361}, {"efta_number": "EFTA01225932", "page_number": 141, "text_content": "STAR Controller Editor Tabs \nFigure 47: 'STAR Controller General Tab \nMUIR *X COMMIS Gann! Tab \nCAA lags Contraasr oe.n \nTab \n5 CPA Catnap • \nuf \nIn \nCa 1•P eY C tot $ dm • \nYazara, \nbale \n.7 Noss's*. \ns..:.. \nG..\" Ye\" I OM\" %Wend 10:4111\n1.1 Timm 'Gala \nOwl1bielfslalkimmie\"1 \nsea \nCaell• Typ. .1.4v .m \nb.' Aeon 10t01 \nel KZ Nessop. \nOs_ \nT.. bar rail cbaata.a. N • calaiLL \n*Yoe el \nfosses \nCftemil gifting Maw* \neMeni \nCs. Conn T. Erin Pao \nSir \nimam. earato. \nCseraral.fts \nMw Rwn Same Cyan artreavelCioatilbil \n• Jel Coe0.44 • almiCapOssla•I \nIra .MOM \nIFr tVAR file:tweet.\" \nDWAMO. \nClaus \nrilinon.bee \nTynan \nGeV  Was I Iliad \ni COS i ON9 \n Tyr.. own_ %%oh. Dom rathapempt\nGera \nCMS rot CaR \n-S \nNEM \nfN 0.0 maaas \nIJ \n(00.50aEaba ab us taaiajl \n• \nOboe &we \ntp lama \nMm. 'roar aD)Coes \nLI Lao LECoMIXO host.,\nPaeans MD (OOP iheflutElaY\"..1\nOillstanis \nrai- :or- • \nliwproon woe, ,••••••.. NaMo.fiblit \nCan••••••• \n• c•• \nCaranit ham \nOfIlitke 40 4.b.M Dents% \n142 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226073\n", "char_count": 1040}, {"efta_number": "EFTA01225932", "page_number": 142, "text_content": "STAR Controller Editor Tabs \n'STAR Utr• COntro•of General rob \nlin int.. \n' \nr DOW \nr \nrwerot 01,0046 IP tern Inv; iterkt \nhead I•my. togoethsoni.l Tonsil Oat.' Saha I the De•wl.nl SalaamI \nGesseCilai \nPISOIOnt \nI • - • • \ntlie *Aka IvaSena. \ndlnaem.I\nIrnaw $tsii \nr \nr u. a niFeCwooten44.0. \nanal. \nCsansops \nr kludipPommaawd Mae •Paraillhosibap \nP IL•DWP \nG t. \n \n _tu \nben,. \nr toes \nr •S•Ireceitse \niancotattweran:154C.4341 \ntad I Von I impel Me I Mt?' f earn Emes I lanai P. D41. 0 . 1•1 iPmen I \nA\n. M let Arum itt \n \n=LJ \nAS te0MominelAst...n.,  \nI \nI \nTs, no I \nP 1.1.00 \nlE14)1.0 I \nCassaaps\"fit \nIatalP10•001.00141. \n• \nINIA•noik \nCoduoWAccos \nr 104/PeoWe41100.4 MM. •Powt0004:•• \nTo Configure the iSTAR Controller General Tab \n1. Create or edit an iSTAR Controller. See either: \n• Creating an iSTAR Controller on Page 124 \n• \nEditing an iSTAR Controller on Page 126. \n2. Enter a unique controller name in the Name field at the top of the iSTAR Controller dialog box. \n3. Enter a textual description (optional) in the Description field. \n4. Enter the last six hexadecimal characters after the vendor portion of the address in the MAC Address entry field \nfor the controller. The first six characters of a controller's MAC address are set at 00-50-F9. The last six characters \nof a controller's MAC address must be within the range of hexadecimal values (i.e., 0-9 and a-f). \n5. To select a particular customized set of LCD messages for the RM Readers, click El to display a Reader LCD \nMessage Set selection list. If you leave this field blank (the default), the Readers use the default messages. See \nReader LCD Message Set Overview on Page 382 for more information. \n6. If you are configuring iSTAR controllers that are located in different time zones, you can use the Time Zone \nentry field. Click El to display a time zone selection. Greenwich Mean Time is equivalent to Zulu or Universal \nTime. If you leave the Time Zone field blank, the iSTAR is considered to be in the C•CURE 9000 s\n... [truncated, 2264 chars — for the full page use /api/corpus/document/EFTA01225932/142 or ?id=EFTA01225932&page=142]", "char_count": 2264}, {"efta_number": "EFTA01225932", "page_number": 143, "text_content": "STAR Controls( Editor Tabs \n7. You can type an IP Address in the Onboard Ethernet IP Address field, although it is recommended that you \nselect Use DCHP to use the Dynamic Host Configuration Protocol (DHCP) option to automatically assign an IP \naddress to the Controller. \n8. For an iSTAR eX Controller, you can enter an IP Address for the Onboard Ethernet Adapter #2. Alternatively, \nyou can select Use DHCP. \nNOTE \nThe DHCP Server has not been evaluated by UL. \n9. For an iSTAR Classic/Pro Controller: \na. If you have a PCMCIA Ethernet Adapter, select Adapter Installed. \nb. You can either enter an IP Address for the PCMCIA adapter or select Use DHCP. \nc. If you are using the PCMCIA Ethernet Adapter as the primary connection to the host, select Use as Primary \nCommunications Adapter. \n10. If you are configuring an iSTAR eX or iSTAR Edge Controller, you need to select the supervising resistor \nconfiguration for the GCM Inputs. The default setting is NO/NC Double EOL 1K. See Table 17 on Page 145 for \nmore information. \nNOTE \nThe supervision method for Inputs on the iSTAR Ultra is configured for each separate Input on the \nInput Editor. \n11. If any Doors on this controller need to be configured for Conditional Access, select the Include Personnel \nWithout Clearance in Personnel Downloads option in the Conditional Access box. The Conditional Access tab \nis available on the iSTAR Doors Editor only if this option is selected. See iSTAR Door Conditional Access Tab on \nPage 436. \nNOTE \nSince selecting this option causes a full Personnel download to the controller (including all \ncredentials except for Lost, Stolen Not Active, and Expired), a warning displays about the 250,000-\nrecord-download limit. \n12. You can optionally click other tabs on the iSTAR Controller Editor to configure other settings prior to saving the \nController. \n13. Click the Enabled check box to put the controller online when you are finished configuring the iSTAR Controller \nGeneral Tab. You must have entere\n... [truncated, 2587 chars — for the full page use /api/corpus/document/EFTA01225932/143 or ?id=EFTA01225932&page=143]", "char_count": 2587}, {"efta_number": "EFTA01225932", "page_number": 144, "text_content": "STAR Controller Editor Tabs \nTable 17: STAR Controller Editor General Tab Fields \nField \nDescription \nName \nEnter a unique name up to 50 characters long for the controller. If you enter the name of an existing object, the system returns \nan error message indicating there is a conflict. \nDescription \nEnter a textual com ment about the controller. such as its location or purpose. This text is for information only. \nEnabled \nClick the Enabled check box to put the Controller online. You must specify the MAC address and IP address for the Controller \nprior to selecting Enabled or you will receive an error message when you save the Controller. \nMaintenance \nMode \nClick to put the STAR Controller and/or its components into Maintenance Mode. See Chapter 2: Maintenance Mode for more \ninformation. \nPartition \nThis read-only field identifies the Partition in which this Controller resides. \nIf you are creating a new Controller, the Partition that iscurrentty the New Object Partition for your Operator account is \nautomatically assigned to each Controller you create. \nIf you want to change the Partition of a Controller, you must move the Cluster in which the Controller resides. See Using Drag \nand Drop in the Hardware Tree on Page 27. \nGeneral (All Controller Types) \nController Type \nThis field displays the controller type: !STAR Classlc/Pro. (STAR Edge. (STAR eX. or (STAR Ultra. \nThe Controller Type is determined when you initially create the controller object. When you save the controller object, this field \nbecomes read-only for all subsequent editing sessions. \nHardware \n(MAC) Address \nEnter the Hardware MAC address for the controller. The MAC address is built into the GCM and cannot be changed. You can \nfind a controller's MAC addresson a label attached to the GCM or view the address using the STAR Configuration Utility. The \nfirst six nibbles (or characters) of a controller's MAC address are set at 00-50-F9. The last six nibbles (or characters) of a \ncontroller's MAC addres\n... [truncated, 3650 chars — for the full page use /api/corpus/document/EFTA01225932/144 or ?id=EFTA01225932&page=144]", "char_count": 3650}, {"efta_number": "EFTA01225932", "page_number": 145, "text_content": "STAR Controller Editor Tabs \nTable 17: STAR Controller Editor General Tab F ields (continued) \nField \nDescription \nOnboard Ethernet Adapter #2 (iSTAR eX and ISTAR Ultra only) \nIP Address \nEnter the unique IP address for Onboard Ethernet 62 as 4 numbers behveen 0 and 255, separated by periods, such as \n100.10.10.1. \nUse DHCP \nSelect this check box to obtain an IP Address (roma DHCP Server for the STAR Controller'sOnboard Ethernet #2 Adapter. \nPCMCIA Ethernet (iSTAR Classic/Pro only) \nAdapter Installed \nSelect thischeck box to indicate that an PCMCIA Ethernet adapter is installed. \nIP Address \nEnter the unique IP address for the PC MC IA Ethernet Adapter as 4 integers between 0 and 255, separated by periods, such \nas 100.10.10.1. \nUse DHCP \nSelect th is check box to obtain an IP Address from a DHCP Server for the PC MC IA Ethernet Adapter. \nUse as Primary \nEthernet \nAdapter \nSelect this check box to indicate that the PC MC IA Ethernet Adaptor is to be used as the Primary Ethernet Adapter. \nSuppress Power / LED Control (iSTAR Edge and iSTAR Ultra only) \nTurn off LEDs \nand LCD \nbacklight \nYou can to configure the LCD backlight and various status LEDs to ahvays be off by selecting (0), regardless of tamper state. \nSelecting this option does not affect the Power LED or the bright white external power indicator. \nOnboard reader \nLED control \nSpecify the method used on this controller to drive the direct connect reader LEDs: \n• 3-wire (Red, Green. Yellow) \n• External Bi-Color (2-wire Red, Green) \n• 1-wire (A, B, C) \nOption Common To Entire Panel (iSTAR eX and iSTAR Edge only) \nSupervising \nresistor \nconfiguration \nAll STAR eX GCM Inputs and STAR Edge inputs must be wired in the same way and use the same supervision method. All \nsupervised settings assume either one or two end of line (EOL) resistors. You can use the Reverse Sense option if you need \na particular Input to differ from the selected setting (for example, if you choose a NO setting here, but you need a door swit\n... [truncated, 2428 chars — for the full page use /api/corpus/document/EFTA01225932/145 or ?id=EFTA01225932&page=145]", "char_count": 2428}, {"efta_number": "EFTA01225932", "page_number": 146, "text_content": "STAR Controller Editor Tabs \nTable 17: STAR Controller Editor General Tab Fields (continued) \nField \nDescription \nCluster Info (All Controller Types) \nCluster Info \nCommunications \nPath \nThese reackonty fields display the Communications Path and the name of the iSTAR Cluster through which this controller \noommunicates with the C•CURE 9000 Server. \nConditional Access (All Controller Types) \nInclude \nPersonnel \nWithout \nClearance in \nPersonnel \nDownloads \nIf you want toenable ocinditionalaccess for Doorson this Controller—allow entry to Personnelwithout Clearances, click to \nselect this option. The Conditional Access tab is availa ble on the STAR Doors Editor only if th is option is selected. For \ninformation, see STAR Door Conditional Access Tab on Page 436. \nNOTE: Since selecting thisoption causesa ful Personneldownload to the controller (including all credentialsexcept for Lost, \nStolen Not Active, and Expired), a warning displays about the 250,000-record download limit. \niSTAR Controller Triggers Tab \nC•CURE 9000 uses Triggers, which are configured procedures used for activating security actions. A Trigger \nautomatically executes a specified Action when a particular predefined condition occurs. When a Trigger is defined, \nthe Actions available depend on the property selected. The Triggers are usually used to activate an Event which can \nactivate numerous actions. \nSee Triggers Tab for iSTAR Devices on Page 270 for information on creating Triggers for an iSTAR device. \niSTAR Controller Status Tab \nThe Status tab, as shown in Figure 48 on Page 149 provides a read-only listing of critical information about the \noperational status of the selected iSTAR controller. Such information includes: \n• Online Status - indicates whether the controller has been enabled (see the General tab). \n• Firmware Version - the version of the firmware used by the controller. \n• Boot Time - the last time the controller was restarted (GMT or Zulu time). \n• Memory Usage for the controller's m\n... [truncated, 2522 chars — for the full page use /api/corpus/document/EFTA01225932/146 or ?id=EFTA01225932&page=146]", "char_count": 2522}, {"efta_number": "EFTA01225932", "page_number": 147, "text_content": "STAR Controller Editor Tabs \n■ iSTAR Edge Controller Status Tab Definitions on Page 150 \n■ iSTAR Ultra Controller Status Tab Definitions on Page 151 \n148 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226079\n", "char_count": 221}, {"efta_number": "EFTA01225932", "page_number": 148, "text_content": "STAR Controller Editor Tabs \nFigure 48: iSTAR Controller Status Tab \niSTAR eX Controller Status Tab \niSTAR Edge Controller Status Tab \n4 \nPew \n'fen. au \nr \n01/1•95t.S.1.718C•WO \n(1.•• I 100104a \nC081 “:.Leah.. \nYr lem,00•Pal lidansmi \na.-. be. \n..440. 'Sao* IP \n&be. • \n• \n• \n• \n• \nALIA\nDOS \nPa \ndal \nr \n1\"...2••• OWirantolvo \nI \n00•100.... I can 101•211.... I 6.. \n1110 Iii•00•Pal \nproestaa \nt•flOs \nft\n•VPIT \n\u0013\nwI\n•••••••••yr \nr \nunown••••• \nr \n.WIII•S•••• \nr \n• \nISTAR Pro Controller Status Tab \niSTAR Ultra Controller Status Tab \n••• \nCisons \nPO0 \nIns. NW \nr 2••••••• \nCantela team 10014C00., \n.6.0 Om. I 101. Far 0Thl tr...10... \ntow lu•tkbp.SII \na.-.r \n170-0 0 %•• fro \n••• \n4 \nISTAR Controller Status Tab Definitions \nN.,* \nsee. \nP oar \nrms. Oda \nr \n1-.01a Cle.••••• \nworn glean \niss I 8.0aI can caul Immo 6.0. ••••• 1...0••••••••12.••••• I \nGrails& \nOselln• \nOasevwwo \n(to a \nI \n \n ea \np \nf••••••.. \np \nNalio~1.4erev,in \nII\n• \nInno..10.0a4 \nTable 18 on Page 150 provides definitions of the fields and buttons on the iSTAR Controller Status tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n149 \nEFTA01226080\n", "char_count": 1125}, {"efta_number": "EFTA01225932", "page_number": 149, "text_content": "STAR Controller Editor Tabs \nTable 18: STAR Controller Status Tab Definitions \nField/Button \nDescription \nOnline Status \nIndicates whether the controller has been Enabled (see the General tab). \nFirmware \nVersion \nThe version of the firmware currently in use by the controller. \nBoot Time \nThe last date/time the controller was restarted (GMT or Zulu time) \nFree Program \nMemory \nUnused program memory in the controller's microprocessor. in kilobytes. \nTotal Program \nMemory \nTotal storage memory in the controller's microprocessor, in kilobytes. \nFree Storage \nMemory \nUnused storage memory in the controller's microprocessor, in kilobytes. \nTotal Storage \nMemory \nTotal storage memory in the controller's microprocessor, in kilobytes. \nFree Physical \nMemory \nUnused physical memory in the controller's microprocessor, in kilobytes. \nTotal Physical \nMemory \nTotal physical memory in the controller's microprocessor, in kilobytes. \nReader \nSecurity Key \nStatus \n(eXonty) \nThis field appliesonty to iSTAR eXcontrollers. It displayswhether or not the eX 8-Reader Security Key is in place. Possible status \nvalues are: \nDetected - the key is plugged in and 8 readers are operational on the iSTAR eX. \nNotDetected - the key isnot plugged in, and onty four Readers will be operational. \nUnknown - the key statuscannot be determined (for example, the status is Unknown if the controller isout of communication \nwith C•CURE 9000). You can determine the status by observing the LCD on the STAR eX. \nEncryption \nSetting Status \n(STAR Edge. \nclassic/Pro) \nA Read-onty field that displays the Encryption Setting. Encryption settings are Encrypted (AES), Unknown, or Not Encrypted. \niSTAR Edge Controller Status Tab Definitions \nFable 19 on Page 150 provides definitions of the fields and buttons unique to the iSTAR Edge Controller Status tab. \nTable 19: STAR Edge Controller Status Tab Definitions \nField/Button \nDescription \nPoE Board Installed \nThe field displayswhether the Power over Ethernet (PoE) Board i\n... [truncated, 2219 chars — for the full page use /api/corpus/document/EFTA01225932/149 or ?id=EFTA01225932&page=149]", "char_count": 2219}, {"efta_number": "EFTA01225932", "page_number": 150, "text_content": "STAR Controller Editor Tabs \niSTAR Ultra Controller Status Tab Definitions \nTable 20 on Page 151 provides definitions of the fields and buttons unique to the iSTAR Ultra Controller Status tab. \nTable 20: iSTAR Ultra Controller Status Tab Definitions \nField/Button \nDescription \nFree RAM \nUnused program memory avaiable to the microprocessor in megabytes. \nTotal RAM \nTotal storage memory available to the microprocessor in megabytes. \nFree Nand Flash Database \nMemory \nUnused flash memory in megabytes. \nTotal Nand Flash Database \nMemory \nTotal flash memory in megabytes. \nPoE Board Installed \nThe field displays whether the Power over Ethernet (PoE) Board is installed. Possible status values are \nTrue or False. \niSTAR Controller User Defined Fields Tab \nThe User Defined Fields tab, shown in Figure 1 on Page 152, displays user-defined fields in the system for hardware. \nUser-defined fields are configured in the Configuration pane. If there are no user-defined fields configured, then the \ntab is empty. \nSee the C•CURE 9000 Software Configuration Guide for more information. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n1St \nEFTA01226082\n", "char_count": 1153}, {"efta_number": "EFTA01225932", "page_number": 151, "text_content": "STAR Controller Editor Tabs \nFigure 1: iSTAR User Defined Fields Tab \niiitowaso.• \nA \n(nese \nr tworavevot \nPaler. Goa• \nGonad I We l Moat CCM I WW2] tigeti I films Sus. UpalNinSF.M. I Shier•P*I \n(.•d•10 \n0— k• \nUfa) \netnnain \nA \niSTAR Controller State Images Tab \nThe State Images tab provides a means to change the default images that are displayed on the C•CURE 9000 \nMonitoring Station to indicate controller states. See State Images Tab for iSTAR Devices on Page 274 for information \non using the State Images tab for your iSTAR Controller. \niSTAR Controller State Images Tab Definitions \nTable 21 on Page 152 shows the iSTAR Controller States and the default State Images. \nTable 21: iSTAR Controller State Images Tab Definitions \nIcon \nDescription \nIcon \nDescription \nUnknown \nDownload in Progress \n— \n_ \nfe. \nOnline \nComm Fail \nIQ \n152 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226083\n", "char_count": 910}, {"efta_number": "EFTA01225932", "page_number": 152, "text_content": "STAR Controller Editor Tabs \nSTAR Controller State Im ges Tab De nrbons (continued) \nIcon \nDescription \nIcon \nDescription \nDisabled \nDatabase Back Up \nPower Faiure \nFite Alarm \nSupervision State \n(Used only by iSTAR Edge) \n—\nr \n:I P\nBattery Low \nFAI Relay Control \n(iSTAR Edge/Ultra) \nII \nOr \n:OP\nFAI Key Supervision State \n(Used only by iSTAR Edge) \nul\nTamper \n0r\ni \nze\nDownload Error \nInternal Battery Fault \n(iSTAR Edge and Ultra) \nI V O \nISTAR Schlage Wireless PIMs Tab \nThis tab allows you to configure up to 16 Schlage Wireless Panel Interface Modules (PIMs) on an iSTAR Classic/Pro. \nAn iSTAR controller can support up to 16 Schlage Wireless readers. The number of PIM boards needed to support \nyour readers can vary, depending upon Reader type and the physical location of the reader/lock hardware. You \ncould connect 16 readers to a single PIM if all readers are within the range/distance specifications for wireless \nreaders. If some readers are farther away, additional PIMs may be needed to place a PIM within wireless range of \neach reader. You can configure no more than 16 PIMs and 16 Readers per controller. \nThe AD300 series readers have an integrated PIM in the reader/lock hardware - these readers require you to \nconfigure an iSTAR PIM board with only that reader attached to the PIM. \nNOTE \nSupport for the following Schlage features requires C•CURE 9000 2.10 R2 Patch 1 or later, and iSTAR \nfirmware 52.1 or later. \n• Wake on Radio \n• Keypad support \n• Manual Lock Override \n• Push Button \nPIM and Reader Addresses \nEach PIM has an address between 0 (zero) and 15. On an iSTAR, boards are numbered starling at 1, not 0. As a \nresult, a PIM with address 0 is configured on the iSTAR as PIM #1. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n153 \nEFTA01226084\n", "char_count": 1787}, {"efta_number": "EFTA01225932", "page_number": 153, "text_content": "ISTAR Controller Editor Tabs \nEach Reader has a reader address between 0 (zero) and 15. On an iSTAR, readers are numbered starting at 1, not 0. \nAs a result, a reader with address 0 is configured on the iSTAR as reader #1. \nExample \nIf you have PIMs with addresses of 4, 8, 12, and 15, you should configure these PIMs on the iSTAR as PIM5, \nPIM9, PIM13, and PIM16. \nIf you have readers with addresses 0 through 5, you should configure these readers on the iSTAR as iSTAR PIM \n485 Readerl through iSTAR PIM 485 Reader6. \nOnce you have assigned a reader address to one PIM, that reader address will be unavailable on all other \nPIM boards on the iSTAR. \nExample \nYou configure Reader address #1 on PIM Board #1. On every other PIM Board you configure on this iSTAR, \nReader address #1 is unavailable (grayed out). \nThe address ranges for readers connected to PIMs cannot overlap. If you set up your PIM hardware so that a specific \nPIM controls reader addresses 0 through 5, you cannot assign a different PIM to control any of the addresses in \nbetween. \nExample \nYou have two PIMs. You set one to control Reader addresses 0 through 5 (readers 1 through 6 on the iSTAR). \nYou other PIM must be setup to control readers outside this range, such as Reader addresses 8 through 11 \n(Readers 9 through 12 on the iSTAR). \nIf you add another PIM, that PIM cannot be assigned to control any of the already assigned addresses, even if \nthe address are not in use at this time by one of the two existing PIMs. The new PIM could only be assigned \nReader addresses 6 and 7 (Readers 7 and 8) and/or Reader addresses 12 through 15 (Readers 13 through 16) \nFigure 49 on Page 155 shows the iSTAR Schlage Wireless PIM tab. \n154 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226085\n", "char_count": 1776}, {"efta_number": "EFTA01225932", "page_number": 154, "text_content": "STAR Controller Editor Tabs \nFigure 49: STAR Schlage Wireless PIMs Tab \naLJ- x \ndr.. h.mh \nI .k \nDin. \nMein Wel \nr Hanna Mado \nTn Zan Gilt<15EQ Caton t2se NS 1O>n) \nGI \neo.d. S.656 Mein In I Loa l GRhel 92ius I In 0nd Folds I Stange I \nSal.,. 566462 Rib \nI Ct. Ann \nnts NPR, \nWI \n. \nl\nit \nPow \n*And \nr \nr \nIn \nPIN' Po 41 \np...w..in \nr \nPimin 01 \nr \nPnn al \nr \nPitnewl \nr \np.s...o, \nr \nPwan, \nr \nF Nan 51 \nr \nNiemen \no \nr \np.4.1/4..1 \nI \nr \nnillAnl \n2 \nr \nP al I no All \n3 \nr \n100341011 \na \nr \nPSIMPoll \n5 \n6 \nr \n0116154,11 \nr \nnemwol \n• than.> or.e ne nee enn 2,51 onn \niSTAR Schlage Wireless PIMs Tab Definitions \nThe fields and buttons on the iSTAR Schlage Wireless PIMs tab are described in Table 22 on Page 155. \nTable 22: STAR Schlage Wireless PIM Tab \nField/Button \nDescription \nCreate All \nPiMs \nClick to create al116 PiMs. When you click Create An PiMs the Configured column check boxes are selected. and you can click \nri  in the Edit column to open the STAR PIM-485 Board Editor to oonfig ure a PiMs. \nDelete All \nPiMs \nWhen you click Delete An PiMs. the check boxes in the Configured column are cleared for all 16 PiMs, and all 16 PIM boards \nare immediatetydeleted (any settings you have configured are lost). \nEdit column \nClick® in the Edit column to open the STAR PIM-485 Board Editor to configure a PIM. See STAR PIM-485 Board Editor on \nPage 226. \nPIM index \ncolumn \nThisoolumn displays the number of each PIM Board. \nConfigured \ncolumn \nClick \nin thisoolumn to create a PIM Board (make it available to be edited). \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n155 \nEFTA01226086\n", "char_count": 1604}, {"efta_number": "EFTA01225932", "page_number": 155, "text_content": "STAR Controller Editor Tabs \nField/Button \nDescription \nName column \nDisplays the name for this PIM Board The name is system-generated by default, but you can edit this name by clicking in this field. \nSave and \nClose \nClick to save your configuration changes and dose the iSTAR Controller editor. \niSTAR Controller Boards Tab (iSTAR Classic/Pro) \nThe Boards tab is available for iSTAR Classic and iSTAR Pro Controllers only. \nThe Boards tab in the iSTAR Controller Editor lets you configure the following inputs, outputs, and ACM boards. \n■ Main Board Inputs on the GCM. \n• Tamper - this input activates when the controller cabinet is opened. \n• Power Failure - this input monitors for AC power failure of the apS or UPS supplying power to the controller. \nWhen this alarm input activates, it specifies that the GCM has lost its primary power source, and is operating \non batteries. \n• External Battery Low (iSTAR Ultra/Classic/Pro) - this input activates when the external emergency battery \n(from the apS or UPS) is running low on power. \n• Internal Battery Fault (iSTAR Ultra only) - this is a logical input that reports the state of the onboard battery. \n• General (iSTAR Ultra only) - this input is a general purpose Supervised Input on the GCM. \n■ Main Board Output on the GCM (iSTAR Classic only). \n■ ACM 1 and ACM 2 Boards for the Controller (iSTAR Classic/Pro only). \nAdd-on Access Control Modules (ACM Boards) provide access control functionality by supporting readers, \noutputs and inputs. \n■ ACM 1 and ACM 2 Boards on SPI port 1 (iSTAR Ultra only) - used to configure Inputs, Outputs, and Readers on \nan iSTAR ACM Board attached to SPI port 1 on an iSTAR Ultra Controller. \n■ ACM 1 and ACM 2 Boards on SPI port 2 (iSTAR Ultra only) - used to configure Inputs, Outputs, and Readers on \nan iSTAR ACM Board attached to SPI port 2 on an iSTAR Ultra Controller. \nThe iSTAR Controller Boards tab is shown in Figure 50 on Page 157. \n158 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFT\n... [truncated, 2010 chars — for the full page use /api/corpus/document/EFTA01225932/155 or ?id=EFTA01225932&page=155]", "char_count": 2010}, {"efta_number": "EFTA01225932", "page_number": 156, "text_content": "STAR Controller Editor Tabs \nFigure 50: STAR Controller Editor Boards Tab \nid Sort ird \nten iht \nfivelse \nP. \nOSA \nr Einlamo Yale \nr.. u. \nGln[03 DM fawn meet, IOrai \nGINS %IS I SCIII•011W•011011P108 I NOP* I Gas I sans I UN. Nero, Fetid Are [rye [ \n1ton Bon Povb \nr Croce W,00 \nOen Ai /an \nEd. \nl[ol ter \n[re ran \nErn,r1 844,4 \n• \nTen.. ht \n\u0013 \nPars \n\u0013 \nbons Ihney to.-ne so \nVas Bard alkali \nCwt• _0411110 \nAOAr \nI. Create or &Oft \nWoe \nThis output is only available on the iSTAR Classic. \nTo Configure the iSTAR Controller Boards Tab \n1. From the iSTAR Controller editor, click the Boards tab. \n2. Create the Main Board Inputs that you need by clicking Create All Inputs or by selecting the Configured check \nbox for only the Inputs you wish to create. \n3. To use an existing Input Template to create one or more of the Main Board Inputs, click in the Template \nColumn, then click 0. A list of available iSTAR Input Templates appears. Click on the Template you wish to \nuse. See Using Templates for Controller Inputs, Outputs, and Readers on Page 37 for more detailed information \nabout using Templates to create Controller Inputs. \n4. Click 0 \nin the Edit column to configure individual Main Board Inputs. See the definitions of the Main Board \nInputs in Table 23 on Page 158. \n5. Create the Main Board Output if needed by clicking Create Output or by selecting the Configured check box for \nthe Main Board Output. \n6. Click 0 \nin the Edit column to configure the Main Board Output. See the definition of the Main Board Output in \nTable 23 on Page 158 and see iSTAR Output Editor on Page 241 for configuration instructions. \n7. Create the ACM Boards that you need by clicking Create All ACMs or by selecting the Configured check box for \nonly the ACMs you wish to create. \n8. Click \nin the Edit column to configure an ACM. See iSTAR Classic/Pro Controller ACM Board Editor on Page \n197 for configuration instructions. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n157 \nEFTA01226088\n", "char_count": 1993}, {"efta_number": "EFTA01225932", "page_number": 157, "text_content": "STAR Controller Editor Tabs \n9. Click Save and Close to save the settings you have configured on the iSTAR Controller Boards tab, or click \nanother tab in the iSTAR Controller Editor to perform additional configuration. \niSTAR Controller Boards Tab Definitions \nThe iSIAR Controller Boards tab includes the fields and buttons described in Table 23 on Page 158. \nTable 23: STAR Controller Boards Tab Definitions \nField/Button \nDescription \nMain Board Inputs \nCreate All Inputs \nClick to create the three Main Board Inputs. When you click Create All Inputs the Configured \ncolumn check boxes are selected. and you can dial ... ] in the Edit column to open the iSTAR \nInput Editor to configure an Input. \nDelete All Inputs \nWhen you click Delete All Inputs. the check boxes in the Configured column are cleared for \nall three Main Board Inputs, and all three Inputs are immediatety deleted (any settings you have \nconfigured are lost). \nTamper \nThe Tamper input activates when the controller cabinet is opened or removed from its mounting \nsurface. \nNOTE: For UL applications, this field must be enabled. \nSelect the check box in the Configured column and dick ri  located in the Edit column to \nopen the STAR Input Editor General tab to configure the Tamper input. From the Input Editor \nyou can configure the Options, Triggers, Groups, Status and State Images that are associated \nwith the Tamper Input. \nThe Template column shows the template name chosen if you selected a Template prior to \ncreating the Input. \nPower Failure \nThe AC power faiure input monitors the AC power failure output of a battery backup unit, such \nas the Advanced Power System (apS). When this alarm input activates, it specifies that the GCM \nhas lost its primary power source, and is operating on batteries. \nNOTE: For UL applications. this field must be enabled. \nSelect the check box in the Configured column and dick n\n located in the Edit column to \nopen the STAR Input Editor General tab to configure the AC Power Fail\n... [truncated, 3052 chars — for the full page use /api/corpus/document/EFTA01225932/157 or ?id=EFTA01225932&page=157]", "char_count": 3052}, {"efta_number": "EFTA01225932", "page_number": 158, "text_content": "STAR Controller Editor Tabs \nTable 23: STAR Controller Boards Tab Definitions (continued) \nFielcUButton \nDescription \nInternal Battery Fault \n(STAR Uttra) \nA logical input that reports the state of the onboard battery. This Input is configured (e) by \ndefault when thecontroller isaeated. \nGeneral \n(STAR Ultra) \nA physical input that can be used to monitor a condition. particutarty useful for Ultra \nconfigurations that are GC M on y. \nMain Board Output Classic and Ultra only) \nCreate \nClick toccata the Main Board Output. When you clickCreate the Configured column check \nbox is selected, and you can click el in the Edit column to open the STAR Output Editor to \nconfigure the Output. \nDelete \n(STAR Classic/Uttra) \nWhen you click Delete, the check box in the Configured column is cleared for the Main Board \nOutput, and the Output is immediatety deleted (any settings you haveconfigured are lost). \n1 \nSelect the check boxy the Configured column and click[ located in the Edit column to \nopen the STAR Output Editor General tab to configure the Options, Groups, Status and State \nImages that are associated with the Main Board Output. \nThe Template column shows the template name chosen if you selected a Template prior to \ncreating the Output. \nAC Ms \nCreate AllACMs \n(STAR Classic/Pro \nonty) \nClick toccata all the ACM Boards. When you dick Create All ACMs the Configured column \ncheck boxes are selected, and you can dick(] in the Editcolumn to open the STAR ACM \nBoard Editor to configure an ACM Board. \nDelete AllACMs \n(STAR Classic/Pro \nonty) \nWhen you click Delete All ACMs. the check boxes in the Configured column are cleared for \nboth Main Board ACM Boards. and both ACM Boards are immediatety deleted (any settings you \nhaveconfigured are lost). \nBoardl \nSelect the check boxy the Configured column and dick[ located in the Edit column to \nopen the STAR ACM Editor General tab to configure the Inputs, Outputs, and Readers that are \nassociated with the first ACM board. \nBoard2 \nSele\n... [truncated, 2746 chars — for the full page use /api/corpus/document/EFTA01225932/158 or ?id=EFTA01225932&page=158]", "char_count": 2746}, {"efta_number": "EFTA01225932", "page_number": 159, "text_content": "STAR Controller Editor Tabs \nISTAR eX Controller Inputs \nSpecial Purpose Inputs \n■ Tamper input - Activates when the controller cabinet is opened. \n■ Power Failure input - Monitors the AC power failure output of the PMB. When this alarm input activates, it \nindicates that the PMB has had an AC Power Failure and is now supplying battery power to the controller. \nSimilarly, if the eX is the NPS (No Power Supply) version, the Power Fail output of the UPS or apS is monitored \nwith the same result. \n■ External Battery Low input - Activates when the battery connected to the PMB emergency battery has reached a \nyellow warning level. This will be followed, after some further use, with a Backup Now condition (Battery really \nlow) which will backup the configuration and data and then shut down the controller. \nIf the eX is the NPS (No Power Supply) version, the Battery Low output of the UPS or apS is monitored and will \nsignal low battery. It is recommended to shut down the unit being powered by the low battery. \nNOTE \nTamper, AC power fail, and Low battery inputs must be programmed for UL applications. \nGeneral Purpose Inputs \n■ iSTAR eX provides 16 general purpose inputs. \nISTAR Edge Controller Inputs \nSpecial Purpose Inputs \n■ Tamper input - Activates when the controller cabinet is opened. \n■ Power Failure input - Monitors the AC power failure output of the UPS (Un-interruptible Power Supply) or apS \nand indicates an AC Power Failure resulting in the UPS or apS supplying battery power to the controller. \n■ Battery Low input - Activates when the UPS or apS emergency battery has reached a yellow warning level. It is \nrecommended to shut down the unit being powered by the low battery. Do not confuse this input with Onboard \nBattery Low. \nNOTE \nTamper, AC power fail, and Low battery inputs must be programmed for UL applications. \n■ Onboard Battery Low input - This input activates when the voltage of all four onboard AA alkaline batteries in \nseries reaches 4.6 volts, or if a b\n... [truncated, 2770 chars — for the full page use /api/corpus/document/EFTA01225932/159 or ?id=EFTA01225932&page=159]", "char_count": 2770}, {"efta_number": "EFTA01225932", "page_number": 160, "text_content": "ISTAR Controller Editor Tabs \n■ FM Key Supervision Stateinput - This input represents the K (Key) Input State. The K input is used to unlatch \nthe latched relays, which removes the relay drive signal, once it is clear that the fire emergency is over. The K \n(Key) input is usually a momentary contact key switch. The K input is supervised as NO (Normally Open). \nGeneral Purpose Inputs \n■ iSTAR Edge provides eight general purpose inputs. \nFire Alarm Interface \nFM (Fire Alarm Interface) is a hardware feature on the iSTAR Edge that is typically used to perform the following \ntasks when a fire alarm signal is present. \n■ Unlock all doors when fire is present. \n■ Remove power from various devices when fire is present. \nAll three of the FM Inputs support Event triggers based on their active or inactive states. These Event triggers can be \nconfigured to activate alarms, send emails, run a Roll Call Report, etc based on the state changes of the three FM \ninputs. \nFAI Modes \nThere are two basic FM modes that can be configured at the controller. \n■ FM without Latch - This method requires the F (Fire) input (NC) of J40 plus the individual enable switches for \neach relay (SW2 through SW5). \n■ FM with Latch and subsequent Unlatch - This method requires the F (Fire) input of J40 plus the individual \nenable switches for each relay (SW2 through SW5), plus SW6 to enable the Latch and J40 K (Key) input (NO) to \nreset the Latch. \nThe Key input is usually a key switch that momentarily closes when the key is inserted and rotated. \nThe FM mode chosen at the controller will determine how you might want to use the Triggers and Actions available \nin the software to provide notification of a fire alarm and related actions. See the iSTAR Edge Installation and \nConfiguration Guide for detailed information about wiring the FM inputs. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n161 \nEFTA01226092\n", "char_count": 1907}, {"efta_number": "EFTA01225932", "page_number": 161, "text_content": "STAR Controller Editor Tabs \nFigure 51: STAR eX and STAR Edge Controller Editor Inputs Tab \nWes \nP \n/Se 0•••• \nr Neseasent \nTeas OISPIOONRISISIONS \nSW Se 1P.+Irwl \nCOMICS) Ts 10s11 Lis I ISSinali \nI 90.”-ea. \nPS — \nSOO \n• Os MS \nM..\".-\ni.\n• as el he. \nCeee•Mbouli \norre.i_Mt \n...an \nIP \nSS.\"' \nnow/moo \nGat \nSe  \nMSS\n \nIS \n• \n‘‘. \nVnePpalevel \nP \nVIA iewiekti \nsieLlri \nr\nin \nVS Seal\nYee iteleni \n...\"•A MAW,. \nr \ncm...wan \n• \n• \nr\n!\".. Steam \n!nee lifell/iern \nVie SU.. al \n^LI \nir ft. LIPP.,\nP POW \nPIS OS \nr \ntinarmr CY141106.sylroat \nSI/ \nSe OS \nPTIIWIPI WPl low l —I SI USISSI \nSS \nSel Nes IS/AteeSessels \nIv M SO \n0.e. • S \nS• \nIs \nTS \nSe• \nc_ \nIS \nSile \nIs \nII \nTsai\n, twig \nes rar. \nP \nlo. raiadMA IS. \nGsSyle• \nP \nEssilsw salIFII Ape, . \n• \nMS \nIA SOU/1000 el \ncild \nr \nr a Prigesidr Styr n \n. \nMoll \n.a n\n. \n1 \nr \nik•SS SITS* \nPi \nse GeSse \ni \nr \n*oral.. 'autos &on \nGesIfs \nSe \nw Gus ass \nSalm \nIa\nWm \nCS.. \nOP \n9 \n6/MI SOW S. \nP \nOW IeSSOP P \nIP \n67IFI•WW•Atri p al \nrnIrcat.WAtif pal \nr \n47rm.o.rfan.....; \nr \nwoo \n. \n.4tMonOWA \nr \naf I •••:%Srlettd.r. \nr \nelm won* taro \nTo Configure the iSTAR eX/Edge Controller Inputs Tab \n1. From the iSTAR Ex/Edge Controller Editor, click the Inputs tab. \n2. Create the Special Purpose Inputs that you need by clicking Create All Inputs or by selecting the Configured \ncheck box for only the Inputs you wish to create. \n3. Click [J  in the Edit column to configure individual Special Purpose Inputs. See the definitions of the Special \nPurpose Inputs in Table 24 on Page 163 and see iSTAR Input Editor on Page 232 for configuration instructions. \n4. Create the General Purpose Inputs that you need by clicking Create All Inputs or by selecting the Configured \ncheck box for only the Inputs you wish to create. \n5. Click [J  in the Edit column to configure individual General Purpose Inputs. See the definitions of the General \nPurpose Inputs in Table 24 on Page 163 and see iSTAR Input Editor on Page 232. \n6. Click Save and Close to save the settin\n... [truncated, 2376 chars — for the full page use /api/corpus/document/EFTA01225932/161 or ?id=EFTA01225932&page=161]", "char_count": 2376}, {"efta_number": "EFTA01225932", "page_number": 162, "text_content": "STAR Controller Editor Tabs \nTable 24: STAR eX and STAR Edge lnputsTab Definitions \nField/Button \nDescription \nSpecial Purpose Inputs \nCreate All Inputs \nClick to create all the Special Purpose inputs. When you click Create All Inputs the Configured column check boxes are \nselected. and you candid( ri\n in the Edit column to open the 'STAR Input Editor to configure an Input. \nDelete All inputs \nWhen you click Delete All Inputs, the check boxes in the Configured column are cleared for all Special Purpose inputs. \nand all these Inputs are im med Latety deleted (any settings you have configured are lost). You will need to confirm each \ndeletion. \nEdit column \nClicks in the Edit column to open the STAR Input Editor to configure a Special Purpose Input. See STAR input Editor on \nPage 232. \nInput Type \ncolumn \nThiscolumn displays the type of each Special Purpose Input. \nConfigured \ncolumn \nClick in this column to create an input (make it available to be edited). \nName column \nDisplays the name for this Input. The name is system-generated by defeat but you can edit this name by clicking in this field. \nTemplate oolumn \nClick in thiscolumn. then click[] to select an input template to use for aeating this input from the list of available input \ntem pLates.You can only select a Template prior to creating the input. \nTamper \nThe Tamper nput activates when the controller cabinet is opened or removed from its mounting surface. \nSelect the check box in the Configured column and click ri\n in the Edit column to open the STAR Input Editor. From the \nInput Editor you can configure the settings and link to events through triggers. \nPower Failure \nThe Power Failure input monitors the AC power failure output of a battery backup unit, such as the Advanced Power \nSystem (a pS). When this alarm input activates, it specifies that the GC M has lust its primary power source, and is operating \non batteries. \nBattery Low \nThe Battery Low input activates when the emergency DC battery is running l\n... [truncated, 3187 chars — for the full page use /api/corpus/document/EFTA01225932/162 or ?id=EFTA01225932&page=162]", "char_count": 3187}, {"efta_number": "EFTA01225932", "page_number": 163, "text_content": "STAR Controller Editor Tabs \nSTAR eX and STAR Edge InputsTab Definitions (continued) \nFlekUButton \nDescription \nGeneral Purpose Inputs \nCreate All Inputs \nCbck tocreateallthe General Purpose Inputs. When you dick Create All Inputs the Configured column check boxes are \nselected, and you can click n \nin the Edit column to open the STAR Input Editor to configure an Input. \nDelete All Inputs \nWhen you click Delete All inputs. the check boxes in the Configured column are Geared for all General Purpose Inputs. \nand all these Inputsare im med lately deleted (any settings you have configured are lost). \nEdit column \nClick[] in the Edit column to open the STAR Input Editor to configure a General Purpose Input. See STAR Input Editor \non Page 232. \nIndexcolumn \nThis column displays the number of each General Purpose Input. \nConfigured \ncolumn \nClick \nn thiscolumn to create an input (make it available to be edited). \nName column \nDisplays the name for this Input. The name is system-generated by defa ult. but you can edit this name byclicking in click in \nthis field. \nTemplate column \nClick in this column, then dick® to select an input template to use for creating this Input from the list of available Input \ntemplates.You can onty select a Template prior to creating the input. \nIndex 1 - 8 (STAR \nEdge) \nIndex 1-16 \n(iSTAR eX) \nThe General Purpose Inputscan be configured in an STAR Door as door switch monitor or request to exit inputs. \nSelect the check boxy the Configured column and click ri\n in the Edit column to open the STAR Input Editor. From the \neditor you can configure the settings for a General Purpose Input. \niSTAR Edge/eX Controller Outputs Tab \nThe iSTAR Controller Outputs tab is available only on the iSTAR eX Controller editor and the iSTAR Edge Controller \neditor. \nThe Outputs tab in the iSTAR Controller Editor lets you define four Relay Outputs and four Open Collector Outputs \n(on the iSTAR eX only). \nThe iSTAR ex and iSTAR Edge Outputs tabs are shown in Figure 52\n... [truncated, 2086 chars — for the full page use /api/corpus/document/EFTA01225932/163 or ?id=EFTA01225932&page=163]", "char_count": 2086}, {"efta_number": "EFTA01225932", "page_number": 164, "text_content": "STAR Controller Editor Tabs \nFigure 52: STAR eX and STAR Edge Controller Editor Outputs Tab \nlimead QM, \n0\" I\"'\nF— \nPAL 01•11 \nr inesrowt \ntriesicanemitnea \n0••• Iv•rdlailalaimITis.jesoli \nsmosno \n0.0•00.4 \nwimp \nmew Al [v. \nCI \nyea \n&Sind \nr \n\u0013 \nfiseWel \n.01•4491111 \n\u0013\n41100.001 \n\u0013 \nNano., \nOuseCailimls Or \n(rale stedati _MtkalPfilitt \nr. \nfi• \nIr \nI bleak \nI \nr \nr \nr \n0.i.voie• \n0,AVJ'ell \n0.9velso \nP \nD'ael \np._ 'IL \nr Illnravelht \nYe &we tall10“06morr. \nUf ICes \nClba W.W.I OW I WWI COMI I...itC.4o I foal w t/feed kiwi sae fly. I \nwows. \nTo Configure the iSTAR eX/Edge Outputs Tab \n1. From the iSTAR Ex/Edge Controller Editor, click the Outputs tab. \n2. Create the Relay Outputs that you need by clicking Create All Outputs or by selecting the Configured check box \nfor only the Outputs you wish to create. \n3. Click 0 \nin the Edit column to configure individual Relay Outputs. See the definitions of the Relay Outputs in \nTable 25 on Page 166 and see iSTAR Output Editor on Page 241 for configuration instructions. \n4. On an iSTAR eX, create the Open Collector Outputs that you need by clicking Create All Outputs or by selecting \nthe Configured check box for only the Outputs you wish to create. \n5. Click 0 \nin the Edit column to configure individual Open Collector Outputs. See the definitions of the Open \nCollector Outputs in Table 25 on Page 166 and see iSTAR Output Editor on Page 241 for configuration \ninstructions. \n6. Click Save and Close to save the settings you have configured on the iSTAR Controller Outputs tab, or click \nanother tab in the iSTAR Controller Editor to perform additional configuration. \niSTAR eX/Edge Controller Outputs Tab Definitions \nThe iSTAR eX and iSTAR Edge Outputs tab includes the fields and buttons detailed in Table 25 on Page 166. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n165 \nEFTA01226096\n", "char_count": 1857}, {"efta_number": "EFTA01225932", "page_number": 165, "text_content": "STAR Controller Editor Tabs \nTable 25: STAR eX and STAR Edge Outputs Tab Definitions \nBox \nDescription \nRelay Outputs (iSTAR ex and iSTAR Edge) \nCreate All \nOutputs \nClick to create all  the Relay Outputs. When you click Create All Outputs the Co nf ig u red column check boxes are selected. and \nyou can click [ ... 1 in the Edit column to open the STAR Output Editor to configure an Output. \nDeleteAll \ninputs \nWhen you click Delete All Outputs. the check boxes in the Co nf ig u red column are cleared for all Relay Outputs. and all these \nOutputs are immediatetydeleted (any settings you haveconfigured are lost). \nEdit column \nClick [—lin the Edit column to open the STAR Output Editor to configure a Relay Output. See STAR Output Editor on Page \n241. \nIndexcolumn \nThis column displays the number of each Relay Output. \nConfigured \ncolumn \nClick in this column to create an Output (make it available to be edited). \nName column \nDisplays the name for this Output. The name is system-generated by dela utt, but you can edit this name by clicking in thisfield. \nTemplate \ncolumn \nClick in th is colu m n. then click [\n] to select an Output template to use for creating this Output from the list of available Output \ntemplates.You can onty select a Template prior to creating the Output. \nRelay Outputs \n1 - 4 \nSelect the check boxy the Configured column and click ...] located in the Editcolumn to open the STAR Output Editor. From \nthe editor you can configure the settings for the Relay Output. \nOpen Collector Outputs (iSTAR eX Only) \nCreate All \nOutputs \nClick to create all the Open Collector Outputs. When you click Create All Outputs the Co nf ig u red column check boxes are \nselected. and you can click ...1 in the Edit column to open the iSTAR Output Editor to configure an Output. \nDelete All \nOutputs \nWhen you click Delete All Outputs, the check boxes in the Conf igu red column are cleared for all Open Collector Outputs, and \nall these Outputs are im med iatety deleted (any settin\n... [truncated, 3020 chars — for the full page use /api/corpus/document/EFTA01225932/165 or ?id=EFTA01225932&page=165]", "char_count": 3020}, {"efta_number": "EFTA01225932", "page_number": 166, "text_content": "STAR Controler Editor Tabs \niSTAR Edge COM1/COM2/COM3 Tabs \nThe COM1, COM2, and COM3 tabs in the iSTAR Edge Controller Editor let you define security objects that are \nconnected to the COM1, COM2, and COM3 ports. RM readers, I/8s, and R/8s can be connected to the COMx ports. \nFigure 53: STAR Edge Controler COM Tabs \nam If\n fop 0' \nP Eratie4 \nFinn. DIY \nr binureo. Notre \nTins Zen 0005 OT Eagan ron, MSC.** \nGad I *pia l Oats I Waged CC  \nCOIO COM I Nor. I Cm.c. \nDow 5.4. I \nMou Sera (BosS. Min d arthale ke244e.teretisi \n.. Ora* 417u1 O.'S \nZ... M IDA balk \na \nSe \nOripat \nNew \nr \n:-.01.15 MA !go Ind I iSTAR fir m \nr \nCOSMOS, Ins Beed.NSTAR Etia• SI \n--, \nr \n1C0111STAR ITO goi.04STAR ala Ill \nI \nr\nICOM1STNI liu lawASTAR few NI \n. \n0 \nIwo. fonts St \nkr Mad. \nipt \nail amiable \nmeld \n.. Cr.c. xi . .4....t neat _O** al Oatutharra \nEde \nSac \n Gripe.; \nMAND \nr \n036114 TM Os. bed14Thill alp II \nr \nCOPII6TMIOJtvi Bard267AR Et* II \n— \nr \nBaTINSIM UV 51\n.00.41.50/40.1“1 \nr \nCON IS TM Oun Brnit,STIA Eepo II \n-I \nProws 0>••••• la an to ....1thle ke Mat, nail) \n1, \ntda \n0,14..\"1 \nNee \nTinale \nI \nr \n0014‘STAR litaderl STAR Fell \n2 \nr \n0)14fST AA Par.ket.S WISP in \nP \nOD•115tAA lissel.5 TAR Ed,. PI \n• \nP \n10314UTAR ReadeftSTIR ECe 1.1 \nThe iSTAR Edge can support either two or four Readers, depending on the model. \nThese Readers can be configured on either the Readers tab or on the COM1, COM2, or COM3 tabs in any \ncombination, as long as the total number of Readers does not exceed the maximum allowed. \nThe number of 1/8 and R/8 bus modules that are supported on the COMx ports depend upon the model: \n• Four 1/8 s and four R/8s are supported on the two-reader model. \n■ Eight 1/8 s and eight R/8s are supported on the four-reader model. \nTo Configure the iSTAR Edge C0M1, C0M2, or COM3 Tab \n1. From the iSTAR Edge Controller Editor, click the COMx tab. \n2. In the Input Boards table, create the Input Boards that you need by clicking Create All Input Boards or by \nselecting the Configured chec\n... [truncated, 2336 chars — for the full page use /api/corpus/document/EFTA01225932/166 or ?id=EFTA01225932&page=166]", "char_count": 2336}, {"efta_number": "EFTA01225932", "page_number": 167, "text_content": "STAR Controller Editor Tabs \n4. In the Output Boards table, create the Output Boards that you need by clicking Create All Outputs or by \nselecting the Configured check box for only the Output boards you wish to create. \n5. Click 0 \nin the Edit column to configure individual Output Boards. See the definitions of the Output Boards in \nTable 29 on Page 176 and see iSTAR Output Board Editor on Page 208 for configuration instructions. \n6. In the Reader Boards table, create the Readers that you need by clicking Create All Readers or by selecting the \nConfigured check box for only the Reader you wish to create. \n7. Click 0 \nin the Edit column to configure individual Readers. See the definitions of the Readers in Table 29 on \nPage 176 and see iSTAR Reader Editor on Page 248 for configuration instructions. \n8. Click Save and Close to save the settings you have configured on the iSTAR Controller COM tabs, or click \nanother tab in the iSTAR Controller Editor to perform additional configuration. \niSTAR Edge COM Tabs Definitions \nTable 26: STAR Edge COM Tabs Definitions \nBox \nDescription \nInput Boards \nCreate All \nInput \nBoards \nChet( to create al the Input Boards. When you dick Create All Input Boards the Configured column check boxes are selected. \nand you can did< El In the Edit column to open the iSTAR Input Board Editor to confgure an Input Board. \nDelete Al \nInputs \nBoards \nWhen you dick Delete All Input Boards, the check boxes in the Configured column are cleared for all Input Boards, and al these \nInput Boards are immediately deleted (any settings you have configured are lost). \nEdit column \nClid< El Wi the Edit column to open the iSTAR Input Board Editor to configure an Input Board. See iSTAR Input Board Editor on \nPage 203. \nIndex \ncolumn \nThis column displays the number of each Input Board. \nConfigured \ncolumn \nCid< \nin thlscolumn to create an Input Board (make it avalable to be edited). \nName \ncolumn \nDisplays the name for this Input Board. The name is system-generat\n... [truncated, 2623 chars — for the full page use /api/corpus/document/EFTA01225932/167 or ?id=EFTA01225932&page=167]", "char_count": 2623}, {"efta_number": "EFTA01225932", "page_number": 168, "text_content": "STAR Controller Editor Tabs \nTable 26: STAR Edge COM Tabs Definitions (continued) \nBox \nDescription \nDelete All \nOutput \nBoards \nWhen you click Delete All Output Boards. the check boxes in the Configured column are cleared for all Output Boards, and all \nthese Output Boards are im med lately deleted (any settings you have confg ured are lost). \nOutput \nBoards 1 - \n8 \nSelect the check box in the Configured column and click ... in the Ed It column to open the STAR Output Board Editor. From the \neditor you can confgure the settings for the Output Board. \nReaders \nCreate All \nReaders \nClick to create all the Readers. When you clickCreate All Readers the Configured column check boxes are selected, and you \ncan click ri\n in the Edit column to open the STAR Reader Editor to configure a Reader. \nDelete All \nReaders \nWhen you click Delete All Readers. the check boxes in the Co nf lgu red column are cleared for all Readers. and all these Readers \nare im med lately deleted (any settings you have confg ured are lost). \nReaders1 - \n4 \nSelect the check boxy the Co nf Ig u red column and cbck n \nin the Edit column to open the STAR Reader Editor. From the \neditor you can configure the settings for the Reader. \nYou can create up to four Readers in this table for an STAR Edge, but if your STAR Edge is not a 4-reader model, Readers 3 - 4 \nwill not function. \nThe Template column shows the template name if you selected a Template prior to creating the Reader. \niSTAR Edge Controller Wiegand Tab \nThe iSTAR Edge Controller Editor Wiegand tab, shown in Figure 54 on Page 170, allows you to configure direct \nconnect Reader devices. Readers that are not connected directly are configured on the COM1, COM2, or COM3 tabs. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n169 \nEFTA01226100\n", "char_count": 1793}, {"efta_number": "EFTA01225932", "page_number": 169, "text_content": "STAR Controller Editor Tabs \nFigure 54: STAR Edge Controller Editor Wiegand and COM1 Tabs \nISICZCar \nj•••• tve r \nfailMa \nr Ihsew•Moa \nway use \n6 . 0l \nb6... \nI CO. \" I COQ COW %Ws Ca. I tral I Om Onvera I \n.\n4••••••• \n•• cf. strewn. \n)Xt••••••••• \nC•••••••• \nDin \n• \n••••• ••••046c titer \n1.0.1 \nrut *We Z, r \n6,7 • \nIse \nr Onoweast \nis:do• \nGeed I MS i Oul•SI \nlig.210:01 1•MMISIMMI \nIsemaal \nealiSMeilor \n..••••••••••••,•••••• _111•1•••••••••••• \nOolong\n\u0013 \n.(niftevouliegn•P*64 \n\u0013\n-crostersiweinatp\n,\n\u0013 \nrartriftly••••0•PAP Lice r \n•••••••••••••••••1441•0••••r \n04••••••••••••••••••••••••••:•••••••••••••• \nI.\nPalla \nGonli \n• \n••••••• Palm 1•••••••••••••••••)••••••••••••) \namps.. \nPin \n\u0013 \nCOMM ...SUMP fen \n\u0013 \nCtindWIIIISSENtimp \n• \n=inn* \nThe Readers can be configured on either the Wiegand tab or on the COM1, COM2, or COM3 tab in any \ncombination, as long as the total number of Readers does not exceed the maximum allowed. \nThe iSTAR Edge supports a maximum of either two readers or four readers depending on the model. \nYou can configure up to two Readers on the Wiegand tab, and the remaining Readers, in any combination, on the \nCOM1, COM2, and COM3 tabs. See the iSTAR Edge Installation and Configuration Guide for more information about \nthe two models. \nExample: \nIf you configure two Readers on the iSTAR Edge Wiegand tab, the iSTAR Edge Controller Editor makes the \nReader 1 - 2 objects on the COM1 and COM2 tabs unavailable (shaded gray) leaving Reader 3 - 4 objects \navailable. \nTo Configure the iSTAR Edge Wiegand Tab \n1. From the iSTAR Edge Controller Editor, click the Wiegand tab. \n2. Create the Readers that you need by clicking Create All Readers or by selecting the Configured check box for \nonly the Readers you wish to create. \n3. Click 0 \nin the Edit column to configure individual Readers. See the definitions of the Readers in Table 27 on \nPage 171 and see iSTAR Reader Editor on Page 248 for configuration instructions. \n4. Click Save and Close to save the settings you\n... [truncated, 2216 chars — for the full page use /api/corpus/document/EFTA01225932/169 or ?id=EFTA01225932&page=169]", "char_count": 2216}, {"efta_number": "EFTA01225932", "page_number": 170, "text_content": "iSTAR Controler Editor Tabs \n(STAR Edge Controller Wiegand Tab Definitions \nThe iSTAR Edge Wiegand tab includes the fields and buttons detailed in Table 27 on Page 171. \nTable 27: iSTAR Edge Wiegand Tab Definitions \nBox \nDescription \nCreate Al \nReaders \nClick to aeate al the Readers. When you dick Create All Readers, the Configured column died( boxes are selected, and you \ncan didc0 in the Edit column to open the iSTAR Reader Editor to configure a Reader. \nDelete Al \nReaders \nWhen you dick Delete All Readers, the died< boxes in the Configured column are cleared for all Readers, and all these Readers \nare immediately deleted (any settings you have configured are lost). \nEdit \ncolumn \nClick =I in the Edit column to open the iSTAR Reader Editor toconfigure a Reader. See STAR Reader Editor on Page 248. \nIndex \ncolumn \nThis column displays the number for each reader. This number is the physical port number for a Direct Connect Wiegand reader. \nConfigured \ncolumn \nClick❑ in this column to create a reader (make it available to be edited). \nName \ncolumn \nDisplays the name for this Reader. The name is system-generated by default, but you can edit this name by decking in this field. \nTemplate \ncolumn \nClick in this column prior to creating the Reader, then did< 0 \nto select a Reader template from the fist of avaiable Reader \ntemplates. \nThe Template column shows the template name chosen if you selected a Template prior to creating the Reader. \nReaders 1 \n• 2 \nSelect the check box in the Configured column for a Reader and did< 0 \nlocated in the Edit column to open the iSTAR Reader \nEditor General tab to configure the Options, Triggers, Groups, Status and State Images that are associated with a Reader. See \niSTAR Reader Editor on Page 248 for detaied instructions for configuring iSTAR Readers. \nIf the row in this table for a particular reader is unavaiable for selection (shaded gray) it indicates that this reader number is \nconfigured on one of the COM tabs in the iSTAR Control\n... [truncated, 3056 chars — for the full page use /api/corpus/document/EFTA01225932/170 or ?id=EFTA01225932&page=170]", "char_count": 3056}, {"efta_number": "EFTA01225932", "page_number": 171, "text_content": "STAR Controller Editor Tabs \nExample: \nIf you configure Readers 1 and 2 on the iSTAR eX Wiegand tab, the iSTAR eX Controller Editor makes the Reader \n1 and 2 objects on the COM1 and COM2 tabs unavailable (shaded gray). Conversely, when you add Readers 3 \nand 4 to one of the COMx tabs, the corresponding readers on the Wiegand tab are unavailable. \nFigure SS: iSTAR eXWiegandand COMx Tabs \nj.te \n-r \nla Wm 0.40ec \nOasis \nhas OS& \nr 198••••••••• \nreata On4•11000.11.•000•001 \nOwed I h. 10.8 Mo, \nRAW Timm Che \nI ;MOW rrl Iswel \nPONS \n.\nC.•••••41••••••• _D•b4•011am.• \nr \n431, 1 1••••),I,\nr \nr \ntra \n‘10~ \nPOSS. \nMOM DIU \nr rose. \nsonfrIllimmaraOliCndil \nCowl i VOA l 0••• *NIS ain IC0.01 Tian i 01.0•11.0•I \nYalta.••••••••••••1 \nPeal na\nfigs \nowe m sua Kee _ pet • FeAbir• \nH \nMOO &Os \nV Z,•••• 040••••••• ,..801.40.8111••• \n:ce. try' 'ow tosi.ave \n:conga rim Issigan \nittepra istsitin \n/ \nGS \nI••• \n[Wes \nis. \nr \nfplaelMNOVINNISPal \nr \n=7•Atro: \nAna Civial Sr* \n&sans 14.174.•10minli \ne \nimocin \nI.8 \nbole \nCaws \nr \nLan \nOW?* gitiOrtOsl \nr \nr \nmann* •iim•ame \nTo Configure the iSTAR eX Wiegand Tab \n1. From the iSTAR eX Controller Editor, click the Wiegand tab. \n2. Create the Readers that you need by clicking Create All Readers or by selecting the Configured check box for \nonly the Readers you wish to create. \n3. Click 0 \nin the Edit column to configure individual Readers. See the definitions of the Readers in Table 28 on \nPage 173 and see iSTAR Reader Editor on Page 248 for configuration instructions. \n4. Click Save and Close to save the settings you have configured on the iSTAR Controller Wiegand tab, or click \nanother tab in the iSTAR Controller Editor to perform additional configuration. \niSTAR eX Controller Wiegand Tab Definitions \nThe iSTAR eX Wiegand tab includes the fields and buttons detailed in Table 28 on Page 173. \n172 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226103\n", "char_count": 1912}, {"efta_number": "EFTA01225932", "page_number": 172, "text_content": "STAR Controller Editor Tabs \nTable 28: STAR eX Wiegand Tab Definitions \nBox \nDescription \nCreate All Readers \nClick to create all the Readers. When you click Create All Readers. the Configured column check boxes are \nselected, and you can click ri\n in the Edit column to open the STAR Reader Editor to configure a Reader. \nDelete All Readers \nWhen you click Delete All Readers. the check boxes in the Co nf igu red column are cleared for all Readers. and all \nthese Readers are im med iate II,de toted (any settings you have configured are lost). \nEdit column \nClick n \nin the Edit column to open the STAR Reader Editor to configure a Reader. See STAR Reader Editor on \nPage 248. \nindexocilumn \nThis column displays the number for each reader. This number is the physical port number for a Direct Connect \nWiegand reader. \nConfigured column \nClick \nn this column to create a reader (make it available to be edited). \nName column \nDisplays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in \nthisfield. \nTemplate column \nClick in thisoolumn prior to creating the Reader, then click[ to select a Reader template from the list of available \nReader templates. \nThe Template column shows the template name chosen if you selected a Template prior to creating the Reader. \nReaders 1 - 8 \nReaders 5 - 8 are only \navailable if the 8 reader \nUSB key is present in \nthe GCM. \nSelect the check box in the Configured column for a Reader and click [- I located in the Edit oakum to open the \nSTAR Reader Editor General tab to configure the Options, Triggers, Groups, Status and State Images that are \nassociated with a Reader. See STAR Reader Editor on Page 248 for detailed instructions for configuring STAR \nReaders. \nIf the row in this table for a particular reader is unavailable for selection (shaded gray) it indicates that this reader \nnumber isocinfigured on one of the COM tabs in the STAR Controller Editor. In Figure 55 on Page 172, for example,\n... [truncated, 2972 chars — for the full page use /api/corpus/document/EFTA01225932/172 or ?id=EFTA01225932&page=172]", "char_count": 2972}, {"efta_number": "EFTA01225932", "page_number": 173, "text_content": "STAR Controller Editor Tabs \nSee Figure 56 on Page 174, which shows the COM1 and COM2 tabs for an iSTAR eX. \nFigure \nISTAR eX Controller COM Tab with Schlage PIM Boards \nten kx•2 \n.:J \nP \nF Sinentrce VON \n\"ay :we \nGr\" \nI Jr\" Ciao r\".\"2 CC*I IC0.221 Tw6.l Oda I Sea I Os Diked roe I Rae nem I \nSod Coarricakto Paccd \nSatyr Men \nScIlepMsels \nr. °wenn, _ Wet AIM; \n60 \nMe \nI ermared \nle••• \nr \n1.1M1.1112 \nr \nPVINXII2 \nr \nfl\nee \nr \n141000.12 \nr \nPIM56.X•2 \n6 \nr \nPIII6a)(12 \n7 \nr \n611/70(62 \n• \nr \n• \nr \n\"see \n•• \nr \n61216082 \nr \nPIN110111 \n12 \nr \n.1102•7012 \n13 \nr \nPVIINX112 \nr \nimus•x•2 \nr \nIf \nr \n1.11164.X.Q \nRemo, on. \n• Tte Met•cmara••••665016661,4 Yee \nTo Configure the iSTAR eX COM1 or COM2 Tab for Schlage Wireless PIMs \n1. From the iSTAR Ex Controller Editor, click one of the COM tabs. \n2. Select Schlage Wireless from the Protocol drop-down list. \n3. In the Schlage Wireles PIMs table that appears, create the PIMs that you need by clicking Create All PIMs or by \nselecting the Configured check box for only the PIMs you wish to create. \n4. Click 0 \nin the Edit column to configure individual PIMs. See: \n• iSTAR Schlage Wireless PIMs Tab Definitions on Page 155 for definitions for the PIM board fields and \nbuttons. \n• iSTAR PIM-485 Reader I/O Tab on Page 261 for configuration instructions. \n5. Click Save and Close to save the settings you have configured on the iSTAR Controller COM tabs. \nCOM1 or COM2 RM Communications \nIf you select the RM option from the Protocol drop-down list, the COM1 or COM2 tab displays 4 Input Boards, 4 \nOutput Boards, and up to 8 RM Readers that you can configure. \nFigure 57 on Page 175 shows the COM1 and COM2 tabs for an iSTAR eX. \n174 \nChapters \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226105\n", "char_count": 1750}, {"efta_number": "EFTA01225932", "page_number": 174, "text_content": "STAR Controller Editor Tabs \nFigure 57: STAR eXControDer COM Tabs \narili \nei≥3•4 arq O,,c \nSr. I., r: \nElsa loco I \nJ \n;LI \nI:, Eprekd \nNato, Odal \nr &we.* Mae \nTune Zr. \nGad I l'aAK I OAKKI I *Cad Call ICI \nTimed I Gaps I adke I Us Odnal link% I Stimigle I \nsiva Cedynuntakent Prated \n•\nPadael IRN \n*den \nM ova, AI 'nut Bove \nMkt Al trout Scads \nEdt \nIt \nI Cortgadi —1I \n2 \nr \nCOMISTAR hat Beed2eXtd \n3 \nr \nco MUM Pp! BealleX re \n... \n4 \n4 \nr \nMUM= \nChita Bee* \n+ 0 Ofte KJ01W Dwds \nOdra al 0,,ta.: Owes \nEck \nMix \n Cody:and \ntine \n_ \nr \ncOMISTARGatEbardleXt2\nI \n,-\n1 \nf \nr \n!COM/STAR Cupd Eteataa N2 \nr \nCatISTAR Mw Elattnad2 \n. \nRabin (Doak, Sievert Kay R4011ffidloe StOSTM allowed \n \n.V. Grata Al Rtadcrs \nWoe AI Riede \nEa \nInds \nCadOdd \nIto. \n1 Marna \n, \nI \nr \nCOW liSTAR Roe:W.0X tI2 \n—. \n2 \nr \nCOMIISTM Reedtr2e,X 12 \n3 \nr \nCOMIISTMI ReedeleX 12 \nThe iSTAR eX can support up to four Readers, and an additional four Readers if equipped with an iSTAR eX \nSecurity Key. \nThese Readers can be configured on either the Readers tab or on the COM1 or COM2 tabs, in any combination, as \nlong as the total number of Readers does not exceed the maximum allowed. \nExample: \nIf you configure two Readers on the iSTAR eX Controller Readers tab and two Readers on the COM1 tab, the \nEditor makes the remaining Reader connections on the Reader, COM1, and COM2 tabs unavailable. Sections of \nthe COM tab are shaded gray (unavailable) to signify that these devices are configured on another tab. \nIf you select the RM option from the Protocol drop-down list, COM1 and COM2 are configured to support RM bus \nreaders. The iSTAR eX can support up to four RM reader devices (or eight Readers if the iSTAR eX Security Key is \ninstalled). A total of eight 1/8 and eight R/8 devices can also be configured on the iSTAR eX on COM1 and/or \nCOM2. \nNOTE \nHowever you configure iSTAR eX Readers, they must match the setting of the S1 switch on the PMB. \nThe S1 switches define which COM port the RM ports are connected to \n... [truncated, 2145 chars — for the full page use /api/corpus/document/EFTA01225932/174 or ?id=EFTA01225932&page=174]", "char_count": 2145}, {"efta_number": "EFTA01225932", "page_number": 175, "text_content": "STAR Controller Editor Tabs \nTo Configure the iSTAR eX COM1 or COM2 Tab \n1. From the iSTAR Ex Controller Editor, click one of the COM tabs. \n2. Select RM from the Protocol drop-down list. \n3. In the Input Boards table, create the Input Boards that you need by clicking Create All Input Boards or by \nselecting the Configured check box for only the Input Boards you wish to create. \n4. Click O \nin the Edit column to configure individual Input Boards. See the definitions of the Input Boards in \nTable 29 on Page 176 and see iSTAR Input Board Editor on Page 203 for configuration instructions. \n5. In the Output Boards table, create the Output Boards that you need by clicking Create All Outputs or by \nselecting the Configured check box for only the Output boards you wish to create. \n6. Click GJ in the Edit column to configure individual Output Boards. See the definitions of the Output Boards in \nTable 29 on Page 176 and see iSTAR Output Board Editor on Page 208 for configuration instructions. \n7. In the Readers Boards table, create the Readers that you need by clicking Create All Readers or by selecting the \nConfigured check box for only the Reader you wish to create. \n8. Click O \nin the Edit column to configure individual Readers. See the definitions of the Readers in Table 29 on \nPage 176 and see iSTAR Reader Editor on Page 248 for configuration instructions. \n9. Click Save and Close to save the settings you have configured on the iSTAR Controller COM tabs, or click \nanother tab in the iSTAR Controller Editor to perform additional configuration. \n'STAR eX COM Tabs Definitions \nTable 29 on Page 176 contains definitions for the fields and buttons on the iSTAR eX COM tabs. \nTable 29: iSTAR eX COM Tabs Definitions \nBox \nDescription \nInput Boards \nCreate Al \nInput \nBoards \nClick tocreate all the Input Boards. When you dick Create All Input Boards the Configured column check boxes are selected. \nand you can did< Oin the Edit column to open the iSTAR Input Board Editor to configu\n... [truncated, 2644 chars — for the full page use /api/corpus/document/EFTA01225932/175 or ?id=EFTA01225932&page=175]", "char_count": 2644}, {"efta_number": "EFTA01225932", "page_number": 176, "text_content": "STAR Controller Editor Tabs \nTable 29: STAR eX COM Tabs Definitions (continued) \nBox \nDescription \nName \ncolumn \nDisplays the name for this Input Board. The name is system-generated by dela utt. but you can edit this name byclicking in this field. \nInput \nBoards 1 - 8 \nSelect the check box in the Configured column and click [—I in the Ed It column to open the STAR Input Board Editor. From the \neditor you can configure the settings for the Input Board. \nOutput Boards \nCreate All \nOutput \nBoards \nClick to create all the  Output Boards. When you click Create All Output Boards the Configured column check boxes are selected. \nand you can click ...din the Edit column to open the STAR Output Board Editor to configure an Output Board. \nDelete All \nOutput \nBoards \nWhen you click Delete All Output Boards, the check boxes in the Configured column are cleared for all Output Boards, and all \nthese Output Boards are im med Late ty deleted (any settings you have configured are lost). \nOutput \nBoards 1 - 8 \nSelect the check box in the Configured column and click [ ... lin the Edlt column to open the 'STAR Output Board Editor. From the \neditor you can configure the settings for the Output Board. \nReaders \nCreate All \nReaders \nClick to create all the Readers. When you clickCreate All Readers the Configured column check boxes are selected, and you \ncan click [- I in the Ed It oplumn to open the STAR Reader Editor to configure a Reader. \nDelete All \nReaders \nWhen you click Delete All Readers. the check boxes in the Configured column are cleared for all Readers, and all these \nReaders are immed lately deleted (any settings you have configured are lost). \nReadersl- \n8 \nSelect the check boxy the Configured column and click[i in the Edlt oplumn to open the STAR Reader Editor. From the \neditor you can configure the settings for the Reader. \nYou can create up to eight Readers in this table for an STAR eX, but if your STAR eXdoes not have an STAR eX Security key. \nReaders 5-8 will not functio\n... [truncated, 2177 chars — for the full page use /api/corpus/document/EFTA01225932/176 or ?id=EFTA01225932&page=176]", "char_count": 2177}, {"efta_number": "EFTA01225932", "page_number": 177, "text_content": "STAR Ultra Controller Editor Inputs Tab \niSTAR Ultra Controller Editor Inputs Tab \nThe Inputs tab (shown in Figure 2 on Page 178) lets you define the Main Board (GCM) inputs for the Controller. \nAll of the inputs support event triggers based on their active or inactive states. These triggers can activate alarms, \nsend emails, run a Roll Call Report, etc. \nThe Input tab fields and buttons are described in Table 2 on Page 178. \nFigure 2: InputsTab \n.LJx \nWe sal Ora \ntiow \nDews.,  \nr paw \nPane*. OAS \nWA. \nTmaate• \nGred •Isa Barth I FJCI. I Will I COW [ \nCroa 19r. [ 1.Yor weal ;Tics' 9aa nape I \nW. Geed les. \nOtare :CMOs \n!JettaInt% \nInapt \nNue \nFronvi ealt•InOt \niv! pme Shea RS 165Pai \n11r. \n• \nTime \n\u0013 \nrawer tab.\" \n• \n(SeaSW Int-\nP \nPot Powe \nRSOS ' \n\u0013 \nPMP.rUVRSµ,2-\nP\nGNI Ma-\n \nPo. Power SOARS al Pe 2 \nAin \nTable 2: Ultra Inputs Tab Definitions \nFiekUButton \nDescription \nMain Board Inputs \nCreate Al \nInputs \nClick to create al the Main Board Inputs. When you dick Create All Inputs the Configured column cteck boxes are selected, \nand you can dick[] in the Edit column to open the iSTAR Input Editor to configure an Input. \nDelete Al \nInputs \nWhen you dick Delete All Inputs, the check boxes in the Configured column are Geared for al Main Board Inputs, and al \nthese Inputs are immediately deleted (any settings you have configured are lost). You will need to confirm each deletion. \n178 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226109\n", "char_count": 1469}, {"efta_number": "EFTA01225932", "page_number": 178, "text_content": "STAR Ultra Controller Editor Inputs Tab \nUltra Inputs Tab Definitions (continued) \nField/Button \nDescription \nEdit column \nClick [ i  in the Edit column to open the STAR Input Editor to configure a Main Board Input. See STAR Input Editor on Page \n232. \nInput Type \ncolumn \nThis column displaysthe type of each Main Board Input. \nConfigured \ncolumn \nClick in this column to create an input (make it available to be edited). \nNamecolumn \nDisplays the name for this Input. The name is system-generated by default, but you can edit this name by clicking in this field. \nTemplate \ncolumn \nClick in this column, then click ...] to select an Input template to use for creating this input from the list of available Input \ntemplates.You can only select a Template prior to creating the input. \nInput Type \nTamper \nActivates when the controller cabinet is opened or removed from its mounting surface. \nSelect the check box in the Configured column and dick Q \nin the Edit column to open the STAR Input Editor. From the Input \nEditor you can configure the settings and link to events through triggers. \nPower Failure \nMonitors the AC power failure output of a battery backup unit. When this alarm input activates, it specifies that the GC M has lust \nits primary power source, and is operating on batteries. \nExternal \nBattery Low \nActivates when the emergency DC battery is running low on power. \nPort Power \nRS485 Port \n1/2 \nActivates if there is a problem with the power on the port. \nCPNI Alarm \nActivates if the CPNI (Centre for the Protection of National Infrastructure) switch S1-2 is changed. \nNOTE \nTamper, AC power fail, and Low battery inputs must be programmed for UL applications. \niSTAR Ultra Controller Boards Tab \nUse the iSTAR Controller Editor Boards tab, shown in Figure 3 on Page 180, to select the ACM type and to open the \niSTAR ACM Board editor to configure readers, outputs and inputs. \nNOTE \nYou must select the correct ACM type used by the controller: \n■ iSTAR Ultra - select iSTAR Ul\n... [truncated, 2128 chars — for the full page use /api/corpus/document/EFTA01225932/178 or ?id=EFTA01225932&page=178]", "char_count": 2128}, {"efta_number": "EFTA01225932", "page_number": 179, "text_content": "STAR Ultra Controller Editor Inputs Tab \nFigure 3: STARController Boards Tab \nx \ntry. l \n0.•cm•er.  \nLeafed \nSnpinrcs .1/40.\ninwiere \nEwa' P X* I coil' I COW imp... I <mad Sint u. DenS^#4. 9a.4I \n:CM \nAO/ Typi, \nr °tote ACA \nDora \nES \nIts \nCalcusd \nNem \nI\nTo Configure the 'STAR Controller Boards Tab \n1. From the iSTAR Controller editor, click the Boards tab. \n2. Select the iSTAR ACM type from the ACM Type drop-down menu. \n• iSTAR Ultra - select iSTAR Ultra ACM. \n• iSTAR Ultra SE - select iSTAR Ultra SE ACM. \n3. Create the ACM Boards that you need by clicking Create All ACMs, or by selecting the Configured check box \nfor only the ACMs you wish to create. \n4. Click 0 \nin the Edit column to configure an ACM. See iSTAR Ultra Controller ACM Board Editor on Page 184 \n5. Click Save and Close. \n180 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226111\n", "char_count": 869}, {"efta_number": "EFTA01225932", "page_number": 180, "text_content": "iSTAR Ultra Controler Editor Inputs Tab \nTable 3: iSTAR Controler Boards Tab Definitions \nField/Button \nDescription \nACM Type \nSelect the STAR ACM type from the ACM Type drop-down menu. \n• 'STAR Ultra- select ISTAR Ultra ACM. \n• STAR Ultra SE - select ISTAR Ultra SE ACM \nCreate ACM \nWhen you dick Create ACM the Configured column check boxes are selected, and you can \ndick 0 \nin the Ed It column to open the iSTAR Ultra ACM Editor to configure the ACM. \nDelete ACM \nWhen you dick Delete ACM, the check boxes in the Configured column are cleared focal \nAC Ms, and are deleted (al configuration settings are lost). \nIndex \nSelect the cteck box in the Configured column and dick 0 \nlocated in the Ed It column to \nopen the iSTAR Ultra ACM Editor to configure the Inputs, Outputs, and Readers that are \nassociated with the ACM board. \nISTAR Ultra Controller IP-ACMs Tab \nThe IP-ACMs tab is used to configure the IP-ACM Offline Mode, readers, inputs, outputs, and triggers. \nSee Chapter 6, Configuring the IP-ACM for information about configuring the IP-ACM. \nISTAR Ultra COM1/COM2 Tabs \nThe COM1 and COM2 tabs in the ISTAR Ultra Controller Editor let you define security objects that are connected to \nthe COM1 and COM2 ports. Aperio Hubs and Schlage PIMs can be configured for the COM1 and COM2 ports. \nFigure 58: iSTAR Ultra Controler COM Tabs \nfa Say car \nNot  IL\nOmani* \nPi DSO \nOnce or. \n01/••••••• Mat \nlOsiel IIMMlria.l \nROSS \n10.•• \n°Sault \nNeal Mobs \nlens I Sas I weer as I as weal \nN \nram \nI \n2 \nI \nsi \nIf \ncast\nIYt \na \n NOM ailha NMI \nK \nw1:43 416.0 Mal \na \nmei la aMt 2USsi \n0 \n0 \na \nnasiASaSNI2+1.1 \n0 \nRe tion 45•a RIM \ni•• UPS tiSPN RIM \nNinfit; MOW Meal \nI Ns. I Gem I steal us wants lialamal \n•—• Leirs \nSNcie Mae His \ny Cigar MI POW \nCola At III1* \n6• \n ▪\n CrOwn• \na 0 \na \nK \nK \nK \nK \nK \nK \nK \nK \nK \na \nH M\n_ \n \nvivo \nWICOWILIBI\n110401414.1.1 \nSOCOSILel \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n181 \nEFTA01226112\n", "char_count": 1942}, {"efta_number": "EFTA01225932", "page_number": 181, "text_content": "'STAR Ultra Controller Editor Inputs Tab \nThe iSTAR Ultra can support up to 32 Readers. There can be up to 16 ACM Readers and up to 32 Aperio Readers or \nSchlage Readers, but the total number of readers cannot exceed 32. If you try to configure any additional readers, an \nerror message appears. The iSTAR Ultra supports either Aperio or Schlage Wireless Readers. There cannot be a \nmixture of the two readers on one iSTAR Ultra. \nThe ACM Readers can be configured as Wiegand direct connect or RM bus as long as the total number of Readers \ndoes not exceed eight per ACM or sixteen per iSTAR Ultra. \nThe Aperio Readers can be configured on any of the possible 30 Hubs, in any combination, as long as the total \nnumber of Readers does not exceed 32. \nThere can be up to 15 Aperio Hubs per COMx port, allowing for a total of 30 Hubs per iSTAR Ultra. Each Hub can \nsupport up to 8, or 1, Assa Abloy Readers with a maximum of 16 readers per COMx port. This provides for a \nmaximum of 32 readers per iSTAR Ultra. \nNOTE \nIf using a 1 Reader Hub, the maximum is 30 Aperio Readers (i.e., 1 Reader per Hub). \nTo Configure the iSTAR Ultra COM1 or COM2 Tab for Aperio \n1. From the iSTAR Ultra Controller Editor, click the COMx tab. \n2. Select Aperio in the Protocol field. This will also select Aperio in the other COMx tab. \n3. In the Aperio Hubs table, create the Aperio Hubs that you need by by selecting the Configured check box for \nonly the Hubs you wish to create. \n4. Click [J  in the Edit column to configure individual Hubs. See the definitions of the Hubs in iSTAR Ultra COM \nTabs Definitions on Page 183 and see iSTAR Aperio RS-485 Hub Board Editor (iSTAR Ultra only) on Page 220 for \nconfiguration instructions. \n5. Click Save and Close to save the settings you have configured on the iSTAR Controller COM tabs, or click \nanother tab in the iSTAR Controller Editor to perform additional configurations. \n a \nTo Configure the iSTAR Ultra COM1 or COM2 Tab for Schlage \n1. From the iSTAR Ultra Control\n... [truncated, 2610 chars — for the full page use /api/corpus/document/EFTA01225932/181 or ?id=EFTA01225932&page=181]", "char_count": 2610}, {"efta_number": "EFTA01225932", "page_number": 182, "text_content": "STAR Ultra Controller Editor Inputs Tab \niSTAR Ultra COM Tabs Definitions \nTable 30: STAR Ultra COM Tabs Definitions \nBox \nDescription \nAperio Hubs \nCreate All \nHubs \nClick to create all the Aperio Hubs. When you dick Create All Hubs the Configured column check boxes are selected, and you \ncandid El in the Edit column to open the STAR Aperio RS-485 Hub Board Editor to config use an Aperio Hub. \nDelete All \nHubs \nWhen you dick Delete All Hubs. the check boxes in the Configured column are dewed for all Hubs, and all these Hubs are deleted \nafter you confirm each deletion (any settings you haveconfigured are lost). \nProtocol \nSelect Aperio. \nEdit \ncolumn \nClick[] in the Edit column to open the STAR Aperio RS-485 Hub Board Editor to configure an Aperio Hub. See STAR Aperio \nRS-485 Hub Board Editor (iSTAR Ultra only) on Page 220. \nIndex \ncolumn \nThis column displays the number of each Hub (from 1 to 15). \nConfigured \ncolumn \nClick \nin this column to create an Aperio Hub (make it available to be edited). \nName \ncolumn \nDisplays the name for this Aperio Hub. The name is system-generated by default, but you can edit this name byclicking in th is fie Id. \nHubs 1 - 15 \nSelect the check box in the Configured column and dicks in the Edit column to open the 'STAR Aperio RS-485 Hub Board \neditor. From the editor you can configure the settings for the Hub. \nSchlage PIMs \nCreate All \nPIMs \nClick to create all the Schlage PiMs. When you click Create All PIMs the Configured column check boxes are selected, and you \ncan dick[[ in the Edit column to open the iSTAR Schlage RS-485 PIM Board Editor to configure a Schlage PIM. \nDelete All \nPIMs \nWhen you dick Delete All PIMs, the check boxes in the Configured column are Geared for all PiMs, and all these PiMs are \ndeleted after you confirm each deletion (any settings you have configured are lost). \nEdit \ncolumn \nChain in the Edit column to open the STAR Schlage RS-485 PIM Board Editor to oonfigure a Schlage PIM. \nindex \ncolumn \nThis column\n... [truncated, 2567 chars — for the full page use /api/corpus/document/EFTA01225932/182 or ?id=EFTA01225932&page=182]", "char_count": 2567}, {"efta_number": "EFTA01225932", "page_number": 183, "text_content": "STAR Ultra Controller ACM Board Editor \niSTAR Ultra Controller ACM Board Editor \nAdd-on Access Control Modules (ACM Boards) provide access control functionality by supporting readers, outputs \nand inputs. \nThe iSTAR Ultra ACM Board dialog box is accessed from the iSTAR Controller editor Boards tab. \niSTAR Ultra ACM Board Editor \nThe iSTAR Ultra ACM Board editor allows you to define and configure inputs, outputs and readers for an ACM \nBoard. The ACM Wiegand tab allows you to configure Wiegand readers, while the ACM RS-485 tab lets you \nconfigure RS-485-connected devices. \nThe iSTAR Ultra ACM Board editor has six tabs: \n■ iSTAR ACM Board General Tab on Page 197 \n■ iSTAR ACM Board Inputs Tab on Page 198 \n■ iSTAR ACM Board Outputs Tab on Page 199 \n■ iSTAR Ultra ACM Board Wiegand Tab on Page 184 \n■ iSTAR Ultra ACM Board RS-485 Tab on Page 186 \n■ iSTAR Ultra ACM Board Status Tab on Page 195 \nFor more information see the iSTAR Ultra Installation and Configuration Guide. \niSTAR Ultra ACM Board Wiegand Tab \nThe iSTAR Ultra ACM Board Wiegand tab, shown in Figure 59 on Page 185, provides configuration for Wiegand \nreaders connected to the iSTAR Ultra ACM Board. \n184 \nChapter 5 \nCCURE 9000 Hardware Configuration Guide \nEFTA01226115\n", "char_count": 1241}, {"efta_number": "EFTA01225932", "page_number": 184, "text_content": "STAR Uttra Controller ACM Board Editor \nFigure 59: STAR Uttra ACM Board Wiegand Tab \nA:929 \nid \nard due \nMn (STAR tin ACM! Via \nParma DafaA \nr Sinleferce Kale \nTeo Zr. GMT050:0 Eamon, Tea VS I Ca) \nGinn, I Ircidd One, NIePMM l RS-4151 Shia. \nCreate Al Roden \nOde* Al Readers \na \nMa \nCc dead \nTeerotate \n_ \n5 \n\u0013 \nISAR RettSTAR las ACM \nt \n\u0013 \nISTAR Meadet6TMuln ,CM1 Urn I \n\u0013 \nSTAR RoolorNSTAR Urn /Om 1.tra 1 \n\u0013 \nGTAR FloodoWAR Vb., ACM 1.1.1fre• 1 \n\u0013 \nGTAR Rx6r5CAR Ulm SCIA1.1in 1 \n\u0013 \nISTAR Ateder661AR lbe AC/Alan,' \n\u0013 \n STAR lindS7SIAR Lira IC/41 lin 1 \n\u0013 \n4TAR ReaderiSTAR lin ACM1 lb \niSTAR Ultra ACM Board Wiegand Tab Definitions \nTable 31 on Page 185 provides definitions of the fields and buttons on the iSTAR Ultra ACM Board Wiegand Tab. \nTable 31: STAR Uttra ACM Board Wiegand Tab.Definitions \nBox \nDescription \nCreate All \nReaders \nClick to create all the Readers. When you dick Create An Readers. the Configured column check boxes are selected. and you \ncan click® in the Edit column to open the STAR Reader Editor to oonfigure a direct connect Wiegand Reader. \nDelete All \nReaders \nWhen you dick Delete All Readers. the check boxes in the Configured column are cleared for all Readers, and all these Readers \nare immediatety de leted (any settings you have configured are lost). \nEdit \ncolumn \nClick El in the Edit column to open the STAR Reader Editor to configure a Reader. See STAR Reader Editor on Page 248. \nIndex \ncolumn \nThis column displays the number for each reader. This number is the physical port number for a Direct Connect Wiegand reader. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n185 \nEFTA01226116\n", "char_count": 1639}, {"efta_number": "EFTA01225932", "page_number": 185, "text_content": "STAR Ultra Controller ACM Board Editor \nTable 31: STAR Ultra ACM Board Wiegand Tab.Definitions (continued) \nBox \nDescription \nConfigured \ncolumn \nClick \nin this column to create a reader (make it available to be edited). \nName \ncolumn \nDisplaysthe name for this Reader. The name is system-generated by default. but you can edit this name by clicking in this field. \nTemplate \ncolumn \nClick in this column prior to creating the Reader, then clicki — I to select a Reader template from the list of available Reader \ntemplates. \nThe Template column shows the template name chosen if you selected a Template prior to creating the Reader. \nReaders 1 \n- 8\nSelect the check box in the Configured column for a Reader and click ri  located in the Edit column to open the STAR Reader \nEditor General tab to configure the Keypad, Triggers, Groups, Status and State Images that are associated with a Reader. See \niSTAR Reader Editor on Page 248 for detailed instructions for configuring STAR Readers. \nThe Name column displays a name comprised of the Reader Type and the STAR Controller name. You can click in this column to \nedit the Reader name. \niSTAR Ultra ACM Board RS-485 Tab \nThe iSTAR Ultra ACM Board RS-485 tab, shown in Figure 60 on Page 187,provides configuration for RS-485 devices \nconnected to the iS1'AR Ultra ACM Board. \n186 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226117\n", "char_count": 1396}, {"efta_number": "EFTA01225932", "page_number": 186, "text_content": "STAR Ultra Controller ACM Board Editor \nFigure 60: STAR Ultra ACM Board RS-485 Tab \n-__ \nMono \nDOeferAga \nISTAA tin AC141,Jt-> \nParaca DeiaA \nr \n..flignrcoAce. \nTire Zoe* 01474:60:6 tam Toe 0.15 &Canada) \nGal I kW* ICI \nWard A5455 (SUS \nFG415 Flab \nCreme Al POI \naloe Al Foes \na \nES \nI hist \nWoad \nNan \na \n'STAR Orme Pot 14TAR Ube /0114.11•1 \n2 \nr\nSTAR Ora PorSiSTAR Len /0414.5rfrl \n3 \nr \n.STAR 0***PeiNSTAR It.t 1410•1 \nr\nisrm Otannat44TAR Ube a \nbllis.1 \ns \nr \nSTAR Demo PaikSTAR Ube /011-Ubikl \n6 \nr \n'STAR Nom Pot‘STNI lab. /04141rfrl \nr \niSTM Dorn PeeMTAR Ora 10114-tra I \n5 \nr \n15TH D.C. KAMM Un/OII.IAn.I \naer \niSTAR Ultra ACM Board RS-485 Tab Definitions \nTable 32 on Page 187 provides definitions of the fields and buttons on the iSTAR Ultra ACM Board RS-485 Tab. \nTable 32: STAR Ultra ACM Board RS-485 Tab Definitions \nField/Button \nDescription \nRS-485 Ports \nCreate All \nPorts \nClick to create the RS-485 Ports. When you click Create All Ports the Configured column check boxes are selected, and you \ncan click[] in the Edit column to open the STAR Device Port Editor to configure an RS-485 Port. \nDelete All \nPorts \nWhen you click Delete All Ports. the check boxes in the Configured column are cleared for all Ports. and &Ports are \nimmediately deleted (any settings you haveconfigured are bst). \nEditcolumn \nClick n \nin the Editcolumn to open the STAR Device Port Editor to configure Device Ports for the STAR Ultra. See STAR \nReader Editor on Page 248. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n187 \nEFTA01226118\n", "char_count": 1540}, {"efta_number": "EFTA01225932", "page_number": 187, "text_content": "STAR Ultra Controller ACM Board Editor \nTable 32: STAR Ultra ACM Board RS-485 Tab Definitions (continued) \nFiekUButton \nDescription \nIndex column \nT h is oolumn displays the number for each Device Port. \nConfigured \ncolumn \nClick in this oolu m n to create a Device Port (make it available to be edited). \nName column \nDisplays the name for this Device Port. The name is syste m-generated by default. but you can edit this name by clicking in click in \nthisfield.\nDevice Ports 1 \n- 8\nSelect the check box in the Configured column for a Device Port and click ri  located in the Edit column to open the STAR \nDevice Port Editor General ta b to configure the Readers and ACM extensions that are associated with the Device Port. See \nSTAR Reader Editor on Page 248 for detailed instructions for configuring STAR Device Ports. \nThe Name column displays a name comprised of the Device Port and the STAR Controller name. You can dick in this column to \nedit the Device Port name. \niSTAR Ultra ACM RS-485 Device Port Editor \nThe iSl'AR Ultra ACM RS-485 Device Port Editor lets you create and configure RM Readers, BLE readers, and direct-\nconnect Wiegand Readers. \n188 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226119\n", "char_count": 1228}, {"efta_number": "EFTA01225932", "page_number": 188, "text_content": "STAR Ultra Controller ACM Board Editor \nF igu re 61: STAR Ultra ACM RS-485 Device Port Editor \niSTAR Ultra ACM RS-485 Device Port Tabs \n■ iSTAR Ultra ACM/IP-ACM RS-485 Device Port General Tab on Page 189 \n■ iSTAR Ultra RS-485 Device Port Readers Tab on Page 190 \n■ iSTAR Ultra RS-485 Device Port ACM EXT Tab on Page 192 \niSTAR Ultra ACM/IP-ACM RS-485 Device Port General Tab \nThe iSFAR Ultra RS-485 Device Port General tab displays three Read-only fields that identify the Controller, Port \nNumber, and Protocol for the RM reader and Wiegand Reader Device Port. Table 33 on Page 190 describes the fields \non this tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n189 \nEFTA01226120\n", "char_count": 690}, {"efta_number": "EFTA01225932", "page_number": 189, "text_content": "STAR Ultra Controller ACM Board Editor \nTable 33: STAR Ultra ACM RS-485 Device Port General Tab Definitions \nField \nDescription \nController \nThis field identifies the controller for th is ACM RS-485 Device Port. \nPort Number \nThis field dentifies the index number of the Device Port on the ACM for the Readers. \nProtocol \nClickon the drop-down menu to select the Protocol type. \n• RM (Software House Reader Protocol) \n• BLE (Bluetooth Low Energy), \n• OSDP (Open Supervised Device Protocol) \nDefault: RM \niSTAR Ultra RS-485 Device Port Readers Tab \nThe iSTAR Ultra RS-485 Device Port Readers tab lets you create and configure the Readers that are attached to an RS-\n485 port on the iSTAR Ultra. \n190 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226121\n", "char_count": 766}, {"efta_number": "EFTA01225932", "page_number": 190, "text_content": "STAR Ultra Controller ACM Board Editor \nFigure 62: iSTAR Ultra RS-485 Device Port Readers Tab \nSr& \nQtlalPICfg \nSTAR Osvc• Pon1STAR Ube /041-Ual \nPartocet DefetA \nMartenance Mat \nTee Dm. OIT-05 DO) Erten Trne \n& Canada) \n9oseni Readers I /01 es\nRoasts\nCreate Al Reader: \nOcktc N React: \n7 \nET \nhiex \nCarivred \nNew \n• \n:STAR Recckri.STAR Devoe P006 \n\u0013 \n'SPA Ree6sr24TAR Dews Patli5 \n\u0013 \nSTAR lisedeeliSTARDSte Pot 1.5 \n\u0013 \n.$10A Rimdet467AR twice Poi 1.S \n\u0013 \n.STAAAali•SESAROvia Pot t S \n\u0013 \nSTAR RudstEASTAR Drip Pot 1.S \n\u0013 \niSTAR Flaseat7iSTARNVIC• held \n\u0013 \niSTAR ReaderNSTAROrace PaitliS \nYou can use an existing Reader Template to create one or more of the RS-485 Readers. Click in the Template \nColumn, then click El. A list of available iSTAR Reader Templates appears. Click on the Template you wish to use. \nSee Using Templates for Controller Inputs, Outputs, and Readers on Page 37 for more detailed information about \nusing Templates to create Readers. \niSTAR Ultra RS-485 Device Port Readers Tab Definitions \nTable 34 on Page 191 provides definitions for the buttons and fields on the iSTAR Ultra RS-485 Device Port Readers \ntab. \nTable 34: STAR Ultra RS-485 Device Port Readers Tab Definitions \nField/Button \nDescription \nC•cate A \nkeade.s \nClick to create all Ins readers. When you dic*Create All Readers the Configured column check boxes are selected. and you \ncan dick el in the Editcolumn toedit that reader. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n191 \nEFTA01226122\n", "char_count": 1492}, {"efta_number": "EFTA01225932", "page_number": 191, "text_content": "STAR Ultra Controller ACM Board Editor \nSTAR Ultra RS-485 Device Port Readers Tab Definitions (continued) \nField/Button \nDescription \nDelete All \nReaders \nWhen you click Delete All Readers, the check boxes in the Configured column are cleared for all readers, and all these readers \nare im med Latety deleted (a ny settings you have oonfig ured are lost). \nEdit column \nClick I ...) in the Edit column to open the STAR Reader Editor to configure an Reader. See STAR Reader Editor on Page 248. \nIndex column \nThis column displays the number of each Reader. \nConfigured \ncolumn \nClick \nin this column to create a Reader (make it available to be edited). \nName column \nDisplays the name for this Reader. The name is system-generated by default, but you can edit this name by clicking in click in this \nfield. \nTemplate \ncolumn \nThe Template column shows the template name if you selected a Template prior to creating the Readers. \nClicks thiscolumn, then click n \nto select a Reader template to use for creating this Reader from the list of available Reader \ntemplates.You can onty select a Template prior to creating the Reader. \niSTAR Ultra RS-485 Device Port ACM EXT Tab \nThe iSTAR Ultra RS-485 Device Port ACM Ext tab lets you create and configure the Input boards and Output boards \nthat are attached to this iSTAR Ultra RS-485 Device Port. \n192 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226123\n", "char_count": 1415}, {"efta_number": "EFTA01225932", "page_number": 192, "text_content": "STAR Ultra Controller ACM Board Edrtor \nFigure 63: STAR Ultra RS-485 Device Port ACM EA Tab \niJJ \narc Otre \nNara \nSTAR Dowa. Por1141AR Ube 1O41 \n.1 \nQ . \nPatten NEPA \nthettenance Mae \nTyre Zeno (641T-05 Oc  Eastern Tee NS d Grad.) \nGonwai I R•40•4 X34 EX\nPPR &orb \nCreate Al Dowels L: Delete Al lords \ni \n611 \nWe \nGASPS \nNM \nI \nA \nr \n6TM 4p4 Boadt4TAR Draw Pc.04STNI \n2 \n;STAR Ws 34441243AR Down PatI4STAR \nr \nSTAR WA 0444034TAR Dram 3.414SIAR \nr \nSTAR Iva Bew044TAR Dr*, Poll4STAX \n$ \nr \n41 AR Fide..t STAR Dela ftelleSTAR \nr \nSTAR Vat (144064STAR Date FS:414TM \nr \n6TAR hat BoathSTAR Down Pot1437412 \n1 \nr \n'STAR Fps Boardt4STAR Demos Pc4367/42 \nOS tads \n2 awe ace* \nWet Meoerds \n• \nFA \nMe \n04,10440 \nNam \nr \nSTAR Oat Boadl4STAR Diva PceliSTA. \nr \nWARW.( Boxd24STAR Dram PatI4STA \n3 \nr \nWAR Otis 34446345TM4 Draw PatI4STA \n4 \nr \n6TAROAxlece444STAR Dina Poll4SA \n$ \nr \n67M0.4841344034TAR Donn PoIl4STA \nc \nr \nSPAWN Be4464ThA Drag Pe414314 \n7 \nr \niSTAROxpx Bow074TAR DrAc• PretleSTA \nB \nr \nSTAR Oat Boxa34STAR Dec. Pal 4STA \nConfiguring the iSTAR Ultra RS-485 Device Port ACM Ext Tab \nWhen you configure the iSTAR Ultra 16-485 Device Port ACM Ext tab, you are defining the Input boards and Output \nboards that are attached to the port. You can then click to open the Input Boards Editor to configure individual Input \nBoards, or open the Output Boards Editor to configure individual Output Boards. \nTo Configure the iSTAR Ultra RS-485 Device Port ACM Ext Tab \n1. From the iSTAR Ultra Boards tab, create an ACM on either SPI Port 1 or SPI Port 2 by clicking in the Configure \ncolumn. \n2. Click 0 \nto open the iSTAR Ultra ACM Board editor. Access the Input Board Editor for the Input Board you \nwish to edit (see iSTAR Ultra Controller ACM Board Editor on Page 184). \n3. Click the RS-485 tab. \n4. Create an RS-485 port by clicking in the Configure column, then click 0 \nto open the iSTAR Ultra Device Port \neditor. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n193 \nEFTA01226124\n", "char_count": 1985}, {"efta_number": "EFTA01225932", "page_number": 193, "text_content": "STAR Uttra Controller ACM Board Editor \n5. Click the ACM Ext tab. \n6. Create an Input board by clicking in the Configure column for one of the Input Boards (1.8), then click ri\n to \nopen the iSTAR Input Board editor. See the iSl'AR Input Board Editor on Page 203 for configuration instructions. \n7. Create an Output board by clicking in the Configure column for one of the Output Boards (1.8), then click ri.to\nopen the iSl'AR Output Board editor. See the iSTAR Output Board Editor on Page 208 for configuration \ninstructions. \n8. When you have finished configuring the Inputs on the iSTAR Ultra RS-485 Device Port ACM Ext tab, click Save \nand Close to save the settings you have configured. \niSTAR Ultra RS-485 Device Port ACM Ext tab Definitions \nTable 42 on Page 202 provides definitions for the buttons and fields on the iSTAR Ultra RS-485 Device Port ACM Ext \ntab. \nTable 35: iSTAR Uttra RS-485 Device Port ACM Ext Tab Definitions \nField/Button \nDescription \nInput Boards \nCreate All \nBoards \nClick to create all the Input Boards. When you click Create All Boards the Configured column check boxes are selected, and \nyou can clickri in the Edit column to edit that Input Board. \nDelete All \nBoards \nWhen you click Delete All Boards. the check boxes in the Configured column are cleared for all Input Boards. and all these \nInput Boards a re im med late ty de toted (a ny settings you have configured are lost). \nEdit column \nClick ... I in the Edit column to open the iSTAR Input Board Editor. See STAR Input Board Editor on Page 203. \nIndex column \nThis column displays the number of each Input Board. \nConfigured \ncolumn \nClick \nin this column to create an Input Board (make it available to be edited). \nName column \nDisplays the name for this Input board. The name is syste m-generated by defa u It. but you can edit this name by clicking in click in \nthis field. \nOutput Boards \nCreate All \nBoards \nClicktocreate all the Output Boards. When you clickCreate All Boards the Configured column c\n... [truncated, 2855 chars — for the full page use /api/corpus/document/EFTA01225932/193 or ?id=EFTA01225932&page=193]", "char_count": 2855}, {"efta_number": "EFTA01225932", "page_number": 194, "text_content": "STAR Uttra Controller ACM Board Editor \niSTAR Ultra ACM Board Status Tab \nThe iSTAR Ultra ACM Board Status tab, shown in Figure 64 on Page 195,provides a read-only listing of information \nabout the operational status of the selected iSTAR Ultra ACM Board. \nFigure 64: STAR Uttra ACM Board Status Tab \nJAI \nre cow \nSo* lupeLaa KMI 44,1 \nPaler, DOS \nr Szwienerceible \nIrma Zone 41414:6 CC) &sum Tao NS &Camila) \nGrind bats I oat* I ffi•pnd I Rs4s5 21.'1 \nthrew Stew \nPICCOB101 1 Cananciece Suns luw \nRecast°, 2 Car...swages Stu.. Itfrino,,, \nPeccessa 7 Femme* Veywn \nPromsa 2 F 'tinware Venga \nF41 Kai Lan, Enabled Smus \nLock I POW \nLa* 2 Pew \nRoo* Pa\nI \nFM Oapas Enoblol laec \nDyke:et() Can 10 \nnode ;re 10 \nVt \nYore \nVots \niSTAR Ultra ACM Board Status Tab Definitions \nTable 36 on Page 195 provides definitions of the fields and buttons on the iSTAR Ultra ACM Board Status tab. \nTable 36: STAR Uttra ACM Board Status Tab Defmaions \nField/Button \nDescription \nProcessor 1 Communications Status \nOffline or Online. \nProcessor 2 Communications Status \nOffline or Online. \nProcessor 1 Firmware Version \nProcessor firmware. such as 00.00.36.00008 \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n195 \nEFTA01226126\n", "char_count": 1214}, {"efta_number": "EFTA01225932", "page_number": 195, "text_content": "STAR Ultra Controller ACM Board Editor \nTable 36. iSTAR Ultra ACM Board Status Tab Definitions (continued) \nFieldeutton \nDescription \nProcessor 2 Firmware Version \nProcessor firmware, such as 00.00.36.00008 \nFAI Key Latch Enabled Status \nEnabled or disabled. \nLock 1 Power (Volts) \nLock power in Volts. \nPossible vales are: 0.0V, 12.0V, 24.0V. \nLock 2 Power (Volts) \nLock power in Volts. \nPossible vales are: 0.0V. 12.0V, 24.0V. \nReader Power \nVoltage reported for Readers. Reader power is the basic power to the GC M and AC Ms. \nTypically reads about 13.8V. \nFAI Outputs Enabled \nList of Outputswith FAl enabled. \n196 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226127\n", "char_count": 686}, {"efta_number": "EFTA01225932", "page_number": 196, "text_content": "STAR Classic/Pro Controller ACM Board Editor \niSTAR Classic/Pro Controller ACM Board Editor \nAdd-on Access Control Modules (ACM Boards) provide access control functionality by supporting readers, outputs \nand inputs. \nThe ACM Board dialog box is accessed from the iSTAR Controller editor Boards tab. \niSTAR Classic/Pro ACM Board Editor \nthe iSTAR Classic/Pro ACM Board editor allows you to define and configure inputs, outputs and readers for the \nACM Board. The ACM Extension (ACM Ext) tab allows you to configure the 1/8 input and R/8 output boards \nconnected to the ACM Board. \nThe iSTAR Classic/Pro ACM Board editor has five tabs: \n■ iSTAR ACM Board General Tab on Page 197 \n■ iSTAR ACM Board Inputs Tab on Page 198 \n■ iSTAR ACM Board Outputs Tab on Page 199 \n■ iSTAR ACM Board Readers Tab on Page 200 \n■ iSTAR ACM Board ACM Ext Tab on Page 201 \nFor more information see the iSTAR Pro Installation and Configuration Guide. \niSTAR ACM Board General Tab \nThe ACM Board General tab identifies the ACM Board. The fields on this tab are read-only. \niSTAR ACM Board General Tab Definitions \nTable 37 on Page 197 provides definitions for the fields on the iSTAR ACM Board General tab. \nTable 37: iSTAR ACM Board General Ta b Definitions \nField/Button \nDescription \nName \nDisplays the name for this ACM board. The name is system generated \nby default, but you can edit this name by clicking in this field. \nDescription \nEnter a textual comment about the ACM board. such as its location or \npurpose. This text is for information only. \nMaintenance Mode \nChola° put the iSTAR ACM board into Maintenance Mode. See \nChapter 2: Maintenance Mode for more information. \nPar than \nThis read-only field identifies the Partition in which the iSTAR Controller \nfor this ACM Board resides. \nBoard Location \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n197 \nEFTA01226128\n", "char_count": 1862}, {"efta_number": "EFTA01225932", "page_number": 197, "text_content": "STAR Classic/Pro Controller ACM Board Editor \nSTAR ACM Board General Tab Definitions (continued) \nField/Button \nDescription \nController \nThis read-only field identifies the Controller to which this board is \nattached. \nACM Number \nThis read-onty field displays the number of the ACM board. \nBoard Type \nThis read-on ty field displays the STAR ACM type. \niSTAR ACM Board Inputs Tab \nThe ACM Board Inputs tab lets you create and configure the Inputs that are attached to this ACM Board. \nYou can use an existing Input Template to create one or more of the ACM Board Inputs. Click in the Template \nColumn, then click El \nA list of available iSTAR Input Templates appears. Click on the Template you wish to use. \nSee Using Templates for Controller Inputs, Outputs, and Readers on Page 37 for more detailed information about \nusing Templates to create Inputs. \niSTAR ACM Board Inputs Tab Definitions \n• Table 38 on Page 198 provides definitions for the buttons and fields on the ACM Board Inputs tab. \n• Table 39 on Page 199 provides definitions for the iSTAR Ultra ACM Board Inputs tab. \nTable 38: STAR Pro/ClassicACM Board Inputs Tab Definitions \nField/Button \nDescription \nCreate All Inputs \nClick to create all the Inputs. When you clickCreate All Inputs the Configured column check \nboxes are selected, and you can click Q \nin the Edit column to edit that Input. \nDelete All Inputs \nWhen you click Delete All Inputs. the check boxes in the Configured column are cleared for \nall Inputs. and all these Inputs are im mediatety deleted (any settings you have configured are \nlost). \nEdit column \nClick ... in the Edit column to open the STAR Input Editor to oonfigure an Input. See STAR \nInput Editor on Page 232. \nIndexcolumn \nT h is column displays the number of each Input. \nConfigured column \nClick \nin thisoolumn to create an Input (make it available to be edited). \nName column \nDisplays the name for this Input. The name is system-generated by defautt, but you can edit \nthis name byclicking in t\n... [truncated, 2515 chars — for the full page use /api/corpus/document/EFTA01225932/197 or ?id=EFTA01225932&page=197]", "char_count": 2515}, {"efta_number": "EFTA01225932", "page_number": 198, "text_content": "iSTAR Classic/Pro Controller ACM Board Editor \niSTAR Ultra ACM Board Inputs Tab Definitions \nTable 39 on Page 199 provides definitions for the buttons and fields on the iSTAR Ultra ACM Board Inputs tab. \nTable 39: STAR Ultra ACM Board Inputs Tab Definitions \nField/Button \nDescription \nSpecial Purpose Inputs (iSTAR Ultra only) \nTamper \nThe Tamper input activates when the controller cabinet is opened or removed from its \nmounting surface. \nNOTE: For UL applications, this field must be enabled. \nSelect the check box in the Configured column and click \nl\na\n \nlocated in the Edlt column to \nopen the iSTAR Input Editor General tab to configure the Tamper input. From the Input Editor \nyou can configure the Options, Triggers, Groups, Status and State Images that are \nassociated with the Tamper Input. \nThe Template column shows the template name chosen if you selected a Template prior to \ncreating the Input. \nComm Fad Processor \n1 \nA logical unsupervised input that reflects the state of the communication between the GCM \nboard and Processor-Aon thisACM board. \nComm Fad Processor \n2 \nA logical unsupervised input that reflects the state of the communication between the GCM \nboard and Processor-Bon this AC M board. \nFAI Alarm \nThis is the Fire Alarm Input signal. It is NC supervised. \nFAI Relay Control \nFAI Relay Control. When the FAI signal is true, the HW drives all selected relays to activate. \nEach relay has a switch indicating whether it is selected to behave in this way. \nFAI Interlock Key \nThe FAI K input is usualty a key switch. It is supervised as NO. It is used in conjunction with \nLatch mode. If latching is enabled, the F signal will turn on all selected outputs. They will stay \nthat way until the Fire Chief inserts the key in the key switch and announces &Wear. \nPort 1 Power Status \nthrough Port 8 Power \nStatus \nPower indicator input for each RM port. \nGeneral Purpose Inputs (iSTAR Ultra only) \nInputs 1 through 24 \n(Ultra) \nInputs 1 though 16 \nUltra SE (Uttra Mode) \n\n... [truncated, 2522 chars — for the full page use /api/corpus/document/EFTA01225932/198 or ?id=EFTA01225932&page=198]", "char_count": 2522}, {"efta_number": "EFTA01225932", "page_number": 199, "text_content": "STAR Classic/Pro Controller ACM Board Editor \nSee Using Templates for Controller Inputs, Outputs, and Readers on Page 37 for more detailed information about \nusing Templates to create Outputs. \niSTAR ACM Board Outputs Tab Definitions \nTable 40 on Page 200 provides definitions for the buttons and fields on the iSTAR ACM Board Outputs tab. \nTable 40: STAR ACM Board Outputs Tab Definitions \nField/Button \nDescription \nCreate All \nOutputs \nClick to create all the outputs. When you dick Create All Outputs the Configured column check boxes are selected, and you \ncan click ... I in the Edit column to edit that output. \nDelete All \nOutputs \nWhen you click Delete All Outputs. the check boxes in the Configured column are Geared for alloutputs. and all these outputs \nare immed Latety de kited (any settings you have configured are lost). \nEdit column \nClick® in the Edit column to open the STAR Output Editor to configure an Output. See STAR Output Editor on Page 241. \nIndex column \nThis column displays the number of each Output. \nConfigured \ncolumn \nClick in thiscolumn tocreate an Output (make it available to be edited). \nName column \nDisplays the name for this Output. The name is system-generated bydefautt, but you can edit this name byclicking in thisfield. \nTemplate \ncolumn \nThe Template column shows the template name if you selected a Template prior to creating the Outputs. \nClick in thiscolumn, then dick (—1 to select an Output template to use for creating this Output from the list of available Output \ntemplates.You can only select a Template prior to creating the Output. \nPrimary Relay Outputs \nOutputs 1 \nthrough 8 \nThese outputs can be used for a Fire Alarm Interface (FAI). They are rated at 5 Amps, and are socket mounted. \nClick \nin the Con( Igure column, then dick® in the Edit column to open the iSTAR Output Editor to configure a Primary \nOutput. See iSTAR Output Board Editor on Page 208 \nSecondary Relay Outputs \nOutputs 1 \nthrough 8 \nThese outputs cannot be used for a F\n... [truncated, 2855 chars — for the full page use /api/corpus/document/EFTA01225932/199 or ?id=EFTA01225932&page=199]", "char_count": 2855}, {"efta_number": "EFTA01225932", "page_number": 200, "text_content": "STAR Classic/Pro Controller ACM Board Editor \niSTAR ACM Board Readers Tab Definitions \nTable 41 on Page 201 provides definitions for the buttons and fields on the iSTAR ACM Board Readers tab. \nTable 41: STAR ACM Board Readers Tab Definitions \nField/Button \nDescription \nCreate Al \nReaders \nCliddocreate all the readers. When you dick Create All Readers the Configured column died( boxesare selected, and you \ncan didC in the Editcolumn to edit that reader. \nDelete All \nReaders \nWhen you dick Delete All Readers, the check boxes in the Configured column are cleared for all readers, and all these readers \nare immediately deleted (any settings you have configured are lost). \nEdit column \nCfick 0 \nin the Edit column to open the iSTAR Reader Editor to configure an Reader. See STAR Reader Editor on Page 248. \nIndex column \nThis column displays the number of each Reader. \nConfigured \ncolumn \nClick in this column to create a Reader (make it available to be edited). \nName column \nDisplays the name for this Reader. The name is system-generated by default, but you can edit this name by decking in this field. \nTemplate \ncolumn \nThe Template column shows the template name if you selected a Template prior to creating the Readers. \nClick in this column, then dick 0 \nto select a Reader template to use for creating this Reader from the fist of avaiable Reader \ntemplates.You can only select a Template prior to creating the Reader. \niSTAR ACM Board ACM Ext Tab \nThe ACM Board ACM Ext tab lets you create and configure the Input boards and Output boards that are attached to \nthis ACM Board. \nConfiguring the ISTAR ACM Board ACM Ext Tab \nWhen you configure the iSTAR ACM Board ACM Ext tab, you are defining the Input boards and Output boards that \nare attached to the ACM. You can then click to open the Input Boards Editor to configure individual Input Boards, or \nopen the Output Boards Editor to configure individual Output Boards. \nTo Configure the iSTAR ACM Board ACM EXT Tab \n1. From the iSTAR c\n... [truncated, 2687 chars — for the full page use /api/corpus/document/EFTA01225932/200 or ?id=EFTA01225932&page=200]", "char_count": 2687}, {"efta_number": "EFTA01225932", "page_number": 201, "text_content": "STAR Classic/Pro Controller ACM Board Editor \n6. Click Q \nin the Edit column to open the iSTAR Output Board editor to configure individual Outputs. See the \niSTAR Output Board Editor on Page 208 for configuration instructions. \n7. When you have finished configuring the Input Boards and Output Boards, click Save and Close to save the \nsettings you have configured. \niSTAR ACM Board ACM Ext Tab Definitions \nTable 42 on Page 202 provides definitions for the buttons and fields on the iSTAR ACM Board ACM Ext tab. \nTable 42: STAR ACM Board ACM Ext Tab Definitions \nFieldMutton \nDescription \nInput Boards \nCreate All \nBoards \nClick to create all the Input Boards. When you did< Create All Boards the Configured column check boxes are selected, and \nyou can click n \nin the Edit column to edit that Input Board. \nDelete All \nBoards \nWhen you dick Delete All Boards, the check boxes in the Configured column are cleared for al Input Boards, and al these \nInput Boards are immediately deleted (any settings you have configured are lost). \nEditcolumn \nClick ILI in the Ed It column to open the iSTAR Input Board Editor. See iSTAR Input Board Editor on Page 203. \nIndex column \nThiscolumn displays the number of each Input Board. \nConfigured \ncolumn \nClick in this column to create an Input Board (make it avalable to be edited). \nName column \nDisplays the name for this Input board. The name is system-generated by default, but you can edit this name by didting in this \nfield. \nOutput Boards \nCreate Al \nBoards \nC 'tido create al the Output Boards. When you dick Create All Boards the Configured column check boxes are selected, and \nyou can dick 0 \nin the Edit column to edit that Output Board. \nDelete Al \nBoards \nWhen you click Delete All Boards, the check boxes in the Configured column are cleared for al Output Boards, and al these \nOutput Boards are immediately deleted (any settings you have configured are lost). \nEdit column \nClick El in the Ed It column to open the iSTAR Output Board Editor. S\n... [truncated, 2436 chars — for the full page use /api/corpus/document/EFTA01225932/201 or ?id=EFTA01225932&page=201]", "char_count": 2436}, {"efta_number": "EFTA01225932", "page_number": 202, "text_content": "STAR Input Board Editor \niSTAR Input Board Editor \nThe iSTAR Input Board editor lets you configure an iSTAR Input Board that you created on the iSTAR Classic/Pro \nACM Board ACM Ext tab or the iSTAR eX and iSTAR Edge COM1, COM2, and COM3 tabs. \nThe iSTAR Input Board editor (see Figure 65 on Page 203) has the following tabs: \n■ iSTAR Input Board General Tab \nLists the Inputs and Status Inputs on an 1/8 board that is connected to an iSTAR Classic/Pro, iSTAR eX, or \niSTAR Edge. See iSTAR Input Board General Tab on Page 206. \n■ iSTAR Input Board Group Tab \nIf you have created a Group containing iSTAR Input Boards and added this Input Board to it, the iSTAR Input \nBoard editor also displays a Group tab. \nThis tab lists the Input Board groups to which this Input Board belongs. See Groups Tab for Hardware Devices \non Page 28 for information on using the Group tab for the iSTAR Input board. \nISTAR Input Board editor Tasks: \n■ Accessing the iSTAR Input Board Editor on Page 204 \n■ Configuring iSTAR Input Boards on Page 205 \nFigure 65: iSTAR Input Board Editor \nCONISTAR IrpitBoeidleal \nPatiocn Oeladl \nI ocibm \nrartage: \nload \n82erti Index \nsm \n'Calla PI \nCtes•Alirput \nDeleNAI Maas \nCS \nindex \nCoe6psed \nWine \nTertptve \n1\n6TAR frOullailISTARItano001 \nJ\n2\nSTAR Wa2C01116TARIrpue Bowl I \nLJ \n3\nK \nSTAR bpil3COLIISTARImiteurdl \n=\n1\nK \nSTAR bp.A4011161AR Input 8cacrl \n5 \nK \nISTAR Irvi5COM16TAR Irtut Spero \n6 \nK \nSTAA Mpa6CON16TMMpaeoaal \n7 \nK \nSTAR IntaCCOM16TARIrouteorecrl \nO \nMM bp1BCON16TMIrpa8oadl \nGnat Al [roues \nA:keenlydi \nEN \nMW pre \nCcetwed \nNane \nTend*, \n \n COINItriOgoll \nEl \nlarpecOHlsIM bpi Bowel, \nComunkalcm FaCONlSTM In.. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n203 \nEFTA01226134\n", "char_count": 1716}, {"efta_number": "EFTA01225932", "page_number": 203, "text_content": "STAR Input Board Editor \nAccessing the iSTAR Input Board Editor \nYou can access the iSTAR Input Board Editor in three ways: \n• To Access the iSTAR Input Board Editor (iSTAR eX/Edge Controller) on Page 204 \n• To Access the iSTAR Input Board Editor (iSTAR Classic/Pro Controller) on Page 204 \n• To Access the iSTAR Input Board Editor from the Hardware Tree on Page 204 \nTo Access the iSTAR Input Board Editor (iSTAR eX/Edge Controller) \n1. From the iSTAR Controller Editor, click on the appropriate COM tab (COM1, COM2, or COM3). \n2. In the Input Boards table on this tab, click 0 \nin the Edit column for the Input board you want to Edit. \n3. The iSTAR Input Board Editor opens. \nTo Access the iSTAR Input Board Editor (iSTAR Classic/Pro Controller) \n1. From the iSTAR Controller Editor, click on the Boards tab. \n2. In the ACMs table on this tab, click 0 \nin the Edit column for the ACM that contains the Input board you want \nto Edit. The ACM Board Editor opens. \n3. Click the ACM Ext tab. \n4. In the Input Boards table on this tab, click ri  in the Edit column for the Input board you want to Edit. \n5. The iSTAR Input Board Editor opens. \nTo Access the iSTAR Input Board Editor from the Hardware Tree \n1. Navigate from your iSTAR Controller in the Hardware Tree to the appropriate COM Board (on an iSTAR eX or \niSTAR Edge Controller) or ACM Board (iSTAR Classic/Pro Controller). \n2. Click on Input Boards, as shown in Figure 66 on Page 205. This figure shows the hardware tree for an iSTAR eX \non the left and an iSTAR Pro on the right. \n204 \nChapter 5 \nCCURE 9000 Hardware Configuration Guide \nEFTA01226135\n", "char_count": 1610}, {"efta_number": "EFTA01225932", "page_number": 204, "text_content": "STAR Input Board Editor \nFigure 66: STAR Input Board in the Hardware Tree \n• STAR IronsBona \n••• \nHadatar bee \ness ant* \ncOp pf \nCy\nex III \nDone \nEladas \nIncas \nly OdP41 \nReadout \nC\nOM COMI as NI \nIna4 Bonds \nCOMISMA broa Boa/las in \nCOMIMAR Iva &swat III \nCaguakzels \nReaden \nMEI COm2.4 m \nI \nsit \n&Wilma Bond \nHadar' bee \nC' essC Co.•Pdds\nC CURE wee \nO\neese\nisrieco\nm  made \n\", \nDoors \nDopats\nfrog\nEltaias \nh\n4 Paden \n0 .1 Adloso 4 \nOn IVA DOI* \n: \nSTAR bp/ Down ALM anal \nSTAR eora Boatadallvo 4 \n02I bah \nId Ma Bowls \n3. Double-click on the Input Board you wish to edit. The STAR Input Board Editor opens. \nConfiguring iSTAR Input Boards \nWhen you configure an iSTAR Input Board, you are defining the Inputs that are attached to a particular 1/8 board. \nYou can then click to open the Inputs Editor to configure individual Inputs. \nTo Configure an iSTAR Input Board Tab \n1. Access the Input Board Editor for the Input Board you wish to edit (see Accessing the iSTAR Input Board Editor \non Page 204). \n2. If you wish to use an Input Template to configure one or more of the 1/8 board Inputs, click in the Template \ncolumn, then click 0 \nto open a dialog box listing the available Input Templates. See Using Templates for \nController Inputs, Outputs, and Readers on Page 37 for more information. \n3. Create the Inputs that you need by clicking Create All Inputs or by selecting the Configured check box for only \nthe Inputs you wish to create. \n4. Click GJ in the Edit column to open the STAR Input Editor to configure individual Inputs. See the STAR Input \nEditor on Page 232 for configuration instructions. \n5. If you wish to use an Input Template to configure one or more of the 1/8 board Status Inputs, click in the \nTemplate column, then click \nto open a dialog box listing the available Input Templates. See Using \nTemplates for Controller Inputs, Outputs, and Readers on Page 37 for more information. \n6. Create the Status Inputs that you need by clicking Create All Inputs or by selecting t\n... [truncated, 2498 chars — for the full page use /api/corpus/document/EFTA01225932/204 or ?id=EFTA01225932&page=204]", "char_count": 2498}, {"efta_number": "EFTA01225932", "page_number": 205, "text_content": "STAR Input Board Editor \niSTAR Input Board General Tab \nThe iSTAR Input Board General tab allows you to configure the Inputs on an 1/8 board attached to your iSTAR \nController, as well as the Status Inputs for Tamper and Communications Failure. \niSTAR Input Board General Tab Definitions \nTable 43 on Page 206 lists the fields and buttons that appear on the iSTAR Input Board General tab. \nTable 43: STAR Input Board General Tab Definitions \nField/Button \nDescription \nIdentification \nName \nDisplays the name for this Input board. The name is system-generated by dela utt. but you can edit this name by choking in this \nfield. \nDescription \nEnter a textual comment about the Input Board. such as its location or purpose. This text is for information only. \nMaintenance \nMode \nClick to put the Input Board into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nPartition \nThis read-only field identifies the Partition in which this Input board resides. \nController \nThis read-onty field identifies the STAR Controller to which this Input board is attached. \nLocation \nBoard \nThis read-only field identifies the STAR Controller board to which this Input board is attached. \nBoard Index \nThis read-only field dentifies the board index (which represents the SW1 address switch setting on the l/8 board) for this Input \nboard. \nInputs \nCreate All \nInputs \nClick to create all eight Inputs. The check boxes in the Conf igu red column are set to V.\nDelete All \nInputs \nClick to delete all eight Inputs. The check boxes in the Configured column are set to \nEdit column \nClick ... in this column to open the STAR Input Editor to edit this Input. \nI ndex oolumn \nThis read-onty field identifies the position of each Input (P1 - P8) on the l/8 board. \nConfigured \ncolumn \nV indicates that the Input has been configured. \nEl indicates that the Input has not been configured. \nName column \nDisplaysthe system-generated name for this Input. You can edit this name by clicking in the field. \n\n... [truncated, 2071 chars — for the full page use /api/corpus/document/EFTA01225932/205 or ?id=EFTA01225932&page=205]", "char_count": 2071}, {"efta_number": "EFTA01225932", "page_number": 206, "text_content": "STAR Input Board Editor \nTable 43: STAR Input Board General Tab Definitions (continued) \nField/Button \nDescription \nTemplate \ncolumn \nDisplays the Template used for creating this Input. If the Input isnot yet configured, you can click in thisoolumn, then click to select \nan Input Tem pLate. If the Configured column displays Q, thisfield cannot be edited. \nStatus Inputs \nCreate All \nInputs \nClick to a eate the Tamper and Communications Fail Inputs. The check boxes in the Co nf Igu red column are set to 2. \nDelete All \nInputs \nChck to delete the Tamper and Communications Fail Inputs. The check boxes in the Co nf lc; u red column are set to \nEdit column \nClick[] in th is colu m n to open the STAR Input Editor to edit this Input. \nInput Type \ncolumn \nThe Input Type Column displays: \nTamper - Represents the Tamper Input on then board. \nNOTE: For UL applications, the Tamper Input on the STAR Input Board General tab must be enabled. \nCommunications Fall - Represents the Communications Fail input on the 1/8 board. \nNOTE: For UL applications, the Communications Failure Input on the STAR Input Board General tab must be enabled. \nConfigured \ncolumn \nV indicates that the Input has been configured. \nindicates that the Input has not been configured. \nNa me oolu m n \nDisplays the system-generated name for this Input. You can edit this name by clicking in the field. \nTemplate \ncolumn \nDisplays the Template used for creating this Input. If the Input isnot yet configured. you can click in this column. then click to select \nan Input Template. If the Co nf igu red column displays V thisfield cannot be edited. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n207 \nEFTA01226138\n", "char_count": 1689}, {"efta_number": "EFTA01225932", "page_number": 207, "text_content": "STAR Output Board Editor \niSTAR Output Board Editor \nThe iSTAR Output Board editor lets you configure an iSTAR Output Board that you created on the iSTAR \nClassic/Pro ACM Board ACM Ext tab or the iSTAR eX and iSTAR Edge COM1, COM2, and COM3 tabs. \nThe iSTAR Output Board editor (see Figure 67 on Page 208) has the following tabs: \n• iSTAR Output Board General Tab \nLists the Outputs and Status Inputs on an R/8 board that is connected to an iSTAR Classic/Pro, iSTAR eX, or \niSTAR Edge. See iSTAR Output Board General Tab on Page 210. \n• iSTAR Output Board Group Tab \nIf you have created a Group containing iSTAR Output Boards and added this Output Board to it, the iSTAR \nOutput Board editor also displays a Group tab. \nThis tab lists the Output Board groups to which this Output Board belongs. See Groups Tab for Hardware \nDevices on Page 28 for information on using the Group tab for the iSTAR Output Board. \nFigure 67: iSTAR Output Board Edit& \n▪ \nOsni•STAROupa \nS1M0..\n\u0013 \n0m342•STMICups ilmoiS1M O..\n\u0013 \nom3.334TAROLaxt BardliSlia 0 \n\u0013 \nOsea4STAROted BoardltSTM O. \n\u0013 \n0..454TAROucte 'Mediated:I o.. \n\u0013 \nCupakSTAROrnat liemll•STAR 0 \n\u0013  O s 4TMO. u kse,4TMo \n\u0013 \n0a3.034TAACupi ksW4STM0 \n. Temse•STMIOsco ltutal.s-\nr \nCOVAXIC46}, rakSTAROap.. \nAccessing the iSTAR Output Board Editor \nYou can access the iSTAR Output Board Editor in three ways: \n• To Access the iSTAR Output Board Editor (iSTAR eX/ Edge Controller) on Page 209 \n208 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226139\n", "char_count": 1502}, {"efta_number": "EFTA01225932", "page_number": 208, "text_content": "STAR Output Board Editor \n• To Access the iSTAR Output Board Editor (iSTAR Classic/Pro Controller) on Page 209 \n• To Access the iSTAR Output Board Editor from the Hardware Tree on Page 209 \nTo Access the iSTAR Output Board Editor (iSTAR eX/Edge Controller) \n1. From the iSTAR Controller Editor, click on the appropriate COM tab (COM1, COM2, or COM3). \n2. In the Output Boards table on this tab, click 0 in the Edit column for the Output board you want to Edit. \n3. The iSTAR Output Board Editor opens (see iSTAR Output Board Editor on Page 208). \nTo Access the iSTAR Output Board Editor (iSTAR Classic/Pro Controller) \n1. From the iSTAR Controller Editor, click on the Boards tab. \n2. In the ACMs table on this tab, click 0 in the Edit column for the ACM that contains the Output board you \nwant to Edit. The ACM Board Editor opens. \n3. Click the ACM Ext tab. \n4. In the Output Boards table on this tab, click 0 in the Edit column for the Output board you want to Edit. \n5. The iSTAR Output Board Editor opens (see iSTAR Output Board Editor on Page 208). \nTo Access the iSTAR Output Board Editor from the Hardware Tree \n1. Navigate from your iSTAR Controller in the Hardware Tree to the appropriate COM Board (on an iSTAR eX or \niSTAR Edge Controller) or ACM Board (iSTAR Classic/Pro Controller). \n2. Click on Output Boards, as shown in Figure 68 on Page 209. This figure shows the hardware tree for an iSTAR \neX on the left and an iSTAR Pro on the right. \nFigure 68: STAR Output Board on the Hardware Tree \nHardware \n• 6TAR Cave Board \nMadaare bee \nCoach \nE won \n01 dune \no edge is \non a. 111 \nija Deal \nDean \nISIIe4 \n0ters \nsa Readers \nCOD C0ml ex es \nIsm) Inas leosva \n0ups Boma \nap C0M I OTAR 0siput Boasted is \nReaders \nMI C0M2acIll \nHardware \n• 6TAR0uloulBeed \nHaden Tees \nseeds \ndessem anis \n6TARD,.. \nDcas \na E*tsa: \nLIR Iran \n0tipas \n41 Ratko \nOM ACMIyoa \na Ian Bart \nagues \nOUPA 8oadt \nIM STAR War RosecaACUIceas \ne 0Uaas \nLit Readers \n*Cm2sxo \n3. Double-click on the Output Board you wish \n... [truncated, 2163 chars — for the full page use /api/corpus/document/EFTA01225932/208 or ?id=EFTA01225932&page=208]", "char_count": 2163}, {"efta_number": "EFTA01225932", "page_number": 209, "text_content": "STAR Output Board Editor \nConfiguring iSTAR Output Boards \nWhen you configure an iSTAR Output Board, you are defining the Outputs that are attached to a particular R/8 \nboard. You can then click to open the Outputs Editor to configure individual Outputs. \nTo Configure an iSTAR Output Board \n1. Access the Output Board Editor for the Output Board you wish to edit (see Accessing the iSTAR Output Board \nEditor on Page 208). \n2. If you wish to use an Output Template to configure one or more of the \nR/8 board Outputs, click in the Template column, then click El to open a dialog box listing the available \nOutput Templates. See Using Templates for Controller Inputs, Outputs, and Readers on Page 37 for more \ninformation. \n3. Create the Outputs that you need by clicking Create All Outputs or by selecting the Configured check box for \nonly the Outputs you wish to create. \n4. Click \nin the Edit column to open the iSTAR Output Editor to configure individual Outputs. See the iSTAR \nOutput Editor on Page 241 for configuration instructions. \n5. If you wish to use an Output Template to configure one or more of the R/8 board Status Inputs, click in the \nTemplate column, then click \nto open a dialog box listing the available Input Templates. See Using \nTemplates for Controller Inputs, Outputs, and Readers on Page 37 for more information. \n6. Create the Status Inputs that you need by clicking Create All Inputs or by selecting the Configured check box for \nonly the Inputs you wish to create. \n7. Click GJ in the Edit column to configure individual Status Inputs. See the definitions of the Status Inputs in \nTable 44 on Page 210 and see iSTAR Input Editor on Page 232. \n8. When you have finished configuring these Outputs and Inputs on the Output Board Editor General tab, click \nSave and Close to save the settings you have configured on the iSTAR Output Board editor. \niSTAR Output Board General Tab \nThe iSTAR Output Board General tab allows you to configure the Outputs on an R/8 board attach\n... [truncated, 2551 chars — for the full page use /api/corpus/document/EFTA01225932/209 or ?id=EFTA01225932&page=209]", "char_count": 2551}, {"efta_number": "EFTA01225932", "page_number": 210, "text_content": "STAR Output Board Editor \nTable 44: STAR Output Board General Tab Definitions (continued) \nFiekUButton \nDescription \nDescription \nEnter a textual oom ment about the Output board, such as its location or purpose. This text is for information onty. \nMaintenance \nMode \nClick to put the STAR Outboard Board into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nPartition \nThis read-on ty field identifies the Partition in which this Output board resdes. \nLocation \nController \nT h is read-onty field identifies the STAR Controller to which this Output board is attached. \nBoard \nThis read-onty field identifies the STAR Controller board to which this Output board is attached. \nBoard Index \nThis read-onty field identifies the board index (which represents the SW1 address switch setting on the R/8 board) for this Output \nboard. \nOutputs \nCreate All \nOutputs \nClick to create a II e ig ht Outputs. The check boxes in the Co nf ig u red column are set toe. \nDelete All \nOutputs \nClick to delete all eight Outputs. The check boxes in the Co nf ig u red column are set to \nEdit column \nClick fl in this column to open the STAR Output Editor to edit this Output. \nIndex oolu m n \nThis read-onty field identifies the position of each Output (P1 - P8) on the R/8 board. \nConfigured \ncolumn \nindicates that the Output has been configured. \nindicates that the Output has not been configured. \nName column \nDisplays the system-generated name for this Output. You can edit this name by choking in the field. \nTemplate \ncolumn \nDisplays the Template used for creating this Output. If the Output is not yet configured. you can click in th is colu m n. then click to \nselect an Output Template. If the Co nf igu red column displays V this field cannot be edited. \nStatus Inputs \nCreate All \nInputs \nClick to aeate the Tamper and Communications Fail Inputs. The check boxes in the Co nf Ig u red column are set to V.\nDelete All \nInputs \nClick to delete the Tamper and Communications Fad Input\n... [truncated, 2218 chars — for the full page use /api/corpus/document/EFTA01225932/210 or ?id=EFTA01225932&page=210]", "char_count": 2218}, {"efta_number": "EFTA01225932", "page_number": 211, "text_content": "STAR Output Board Editor \nTable 44: STAR Output Board General Tab Definitions (continued) \nFieKennon \nDescription \nIndexcolumn \nThe Input Type Column displays: \nTamper- Represents the Tamper Input on the R/8 board. \nNOTE: For UL applications, the Tamper input on the STAR Output Board General tab must be enabled. \nCommunications Fall - Represents the Communications Fail input on the R/8 board. \nNOTE: For UL applications, the Communications Failure Input on the STAR Output Board General tab must be enabled. \nConfigured \ncolumn \nV indicates that the input has been configured. \nindicates that the input has not been configured. \nName column \nDisplays the system-generated name for this input. You can edit this name byclicking in the field. \nTemplate \ncolumn \nDisplays the Template used for creating this input. If the input isnot yet configured, you can click in this column, then click to select \nan Input Template. If the Configured column displays V this field cannot be edited. \n212 \nChapter 5 \nC•CURE 9000 Hardware Con figuration Guide \nEFTA01226143\n", "char_count": 1059}, {"efta_number": "EFTA01225932", "page_number": 212, "text_content": "STAR Ultra Wireless Readers \niSTAR Ultra Wireless Readers \nThe iSTAR Ultra supports either Assa Abloy Aperio or IR Schlage wireless readers. The interface is through the RS-\n485 ports on the Ultra GCM board. The default setting is Aperio, with Schlage as the only other option currently. \nBoth ports must use the protocol, and they are synchronized so that both ports change whenever the protocol \nchanges on either of them. \nNOTE \nThe protocol cannot be changed while any Schlage PIM or Aperio Hub exists. \nAssa Abloy Aperio \nHubs and Wireless Readers \n■ Each RS-485 port (i.e., GCM Porn, Port2) supports up to 15 Hubs. The iSTAR Ultra supports up to 32 readers \npaired to any of the 30 Hubs. \n■ If there are fewer than 32 Aperio readers, there can be up to 16 usual (RM bus or direct Wiegand) readers on the \niSTAR Ultra. If only Aperio readers are used, there is no need for an ACM on the Ultra. \n■ Either 8 Port or 1 Port Hubs can be used, but usually 8 Port Hubs are configured. \n■ There are 11, plus a generic, types of locks that can be configured on the Ultra GCM. \nIR Schlagen?' PIMs and Wireless Readers \n■ Each RS-485 port (i.e., GCM Porn, Port2) supports up to 16 PIMs. The iSTAR Ultra supports up to 32 readers \nconnected to any of the 32 PIMs. Schlage use a proprietary protocol named RS-485 RSI for communication on the \nbus. \n■ If there are fewer than 32 Schlage readers, there can be up to 16 usual (RM bus or direct Wiegand) readers on the \niSTAR Ultra. If only Schlage readers are used, there is no need for an ACM on the Ultra. \n■ When assigning reader numbers, it is best practice to use sequential numbers, If you configure reader 1 and \nreader 5, Schlage will not use readers 2, 3, and 4. Although, those reader numbers are available for the up to 16 \nACM RM or Wiegand readers. \nNOTE \nSchlage addresses are one less than the C•CURE index. For example, if you setup a reader on Schlage \naddress 1, then it's C•CURE index 2. \n■ There are 3 types of PIMs that can be connected to\n... [truncated, 2499 chars — for the full page use /api/corpus/document/EFTA01225932/212 or ?id=EFTA01225932&page=212]", "char_count": 2499}, {"efta_number": "EFTA01225932", "page_number": 213, "text_content": "STAR Ultra Wireless Readers \nFigure 4: Schlage Wireless Connection Methods \nISTAR \nUltra, Pro \nor eX \nRS-485 RSI \nMEW \nWA Series \nPIM-495 \nr\n, \nor\n•\nC \nWA-Series \nVrirekes \nWok \nrecess \n(predecessor to Schlage) \npill \n!/r\n0\ngi= \nAD Series \nPIM400-485 \n*P\nt\n\" • \nIto \n0 \nAD-3C0 \nHardwired \niSTAR Ultra Schlage Wireless Types of Connections \nThe Schlage Readers interface to C•CURE hardware using one of seven basic methods: \n1. PIM400-485 (AD400 Wireless to Ultra GCM, Pro GCM and eX PMB) \n2. PIM400-485 TD2 (AD400 Wireless to all iSTARs and all apCs) (Can use Wiegand or Magnetic signaling) \n3. AD300 Built-in PIM (AD300 Wired to Ultra, Pro and eX) \n4. AD300 PIB300 (AD300 Wired to all iSTARs and all apCs) \n5. PIM485 (Wyreless Wireless to Ultra GCM, Pro GCM and eX PMB) \n6. PIM TD2 (Wyreless Wireless to all iSTARs and all apCs) (2 Reader - Can use Wiegand or Magnetic signaling) \n7. PIM TD4 (Wyreless Wireless to all iSTARs and all apCs) (4 reader - Can use Wiegand or Magnetic signaling) \nEach of the first four methods are repeated for FIPS-201: \n1. PIM401-485 (AD400 Wireless to Ultra, Pro and eX) \n2. PIM401-485 TD2 (AD400 Wireless to all iSTARs and all apCs) \n3. AD301 Built-in PIM (AD300 Wired to Ultra, Pro and eX) \n4. AD301 PIB301 (AD301 Wired to all iSTARs and all apCs) \nWireless - PIM400 and PIM400-TD2 \n• Up to 16 AD400 wireless readers can be associated with 1 PIM400. Up to 2 AD400 wireless readers can be \nassociated with 1 PIM400-TD2. \n214 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226145\n", "char_count": 1525}, {"efta_number": "EFTA01225932", "page_number": 214, "text_content": "STAR Ultra Wireless Readers \n• The PIM400 interfaces with iSTAR Ultra, Pro and eX using RS-485 RSI. \n• The PIM400-TD2 interfaces with either Wiegand signaling or Clock/Data Magnetic ABA2 signaling. The method \nis determined by the type of reader. \n• A magnetic card reader (swipe or insertion) will use Clock and Data which will be passed through the TD2 to \nthe C•CURE hardware. The magnetic signaling must be connected to an RM4/4E and then to an RM port. \n• A Wiegand signaling reader will use Data 1 and Data 0 which will also be passed through the TD2. the \nWiegand signaling can be connected to any direct Wiegand port or to an RM4/4E. \n• In addition to AD400 Readers, the PIM400-485 can also communicate with WRI400, WPR400, and TK400 \ndevices. \nSummary Tables \nThe tables in this section provides a matrix of the possible connections between Schlage devices and i51'ARs and \napCs. \nAD400 Wireless \nTable 4: AD400 Series \nController/Panel \nLocks \nSupported \nRS485 RSI \nChain \nWiegand Signal (DO/D1) to \nPanel \nMagnetic Signal (CLK/DATA) to \nPanel \niSTAR Ultra \niSTAR Pro \nSTAR Classic \nAD400 (All slytes) \nPIM400-485 \nRSI to GCM \nPIM400-TD2 toACM Wiegand \nPIM400-TD2 to RM4xtoACM \nRM \nPIM400-T D2 to RM4xtoACM RM \niSTAR eX \nAD400 (All slytes) \nPIM400-485 \nRSI to PMB \nPIM400-TD2 to GCM Wiegand \nPIM400-TD2 to R 11/444x to PMB \nRM \nPIM400-T D2 to R hil4x to PMB RM \niSTAR Edge \nAD400 (All styles) \nPIM400-TD2 to Edge Wiegand \nPIM400-TD2 to RM4x to Edge \nRM \nPIM400-TD2 to R 11/444x to Edge RM \napC/8X \nAD400 (Al styles) \nPIM400-TD2 toWPSC Wiegand \nPIM400-TD2 to RM4xtoapC RM \nPIM400-TD2 to RM4x to apC RM \napC/L \nAD400 (Al styles) \nPIM400-TD2 to RM4xtoapC/L \nRM \nPIM400-TD2 to RM4xtoapC/L RM \nAD401 Wireless (FIPS-201) \nNOTE \nThe AD401 (FIPS-201) configuration only supports a Multi-technology reader with Keypad and \nWiegand signaling. \nThe reader appears as a standard Wiegand reader connected to: \n• iSTAR ACM Wiegand Port \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n215 \nEFTA01226\n... [truncated, 2004 chars — for the full page use /api/corpus/document/EFTA01225932/214 or ?id=EFTA01225932&page=214]", "char_count": 2004}, {"efta_number": "EFTA01225932", "page_number": 215, "text_content": "STAR Ultra Wireless Readers \n• iSTAR eX GCM Wiegand Port \n• iSTAR Edge Wiegand Port \n• apC/8X WPSC Wiegand Port \n• RM4 or RM4E to any RM Port on iSTAR or apC. \nThe P1B401402 is used for all connections. \nTable 5: AD401 Series \nController/Panel \nLocks Supported \nRS485 RSI \nChain \nWiegand Signal (DO/D1) \nto Panel \nMagnetic Signal (CLK/DATA) \nto Panel \nSTAR Ultra \nSTAR Pro \nSTAR Classic \nAD401 \n(Mufti-Technologywith \nkeypad only) \nN/A \nPIM401-TD2 to ACM \nWiegand \nPIM401-T D2 to R M4x to ACM \nRM \nN/A \niSTAR eX \nAD401 \n(Mufti-Technologywith \nkeypad only) \nN/A \nPIM401-T D2 to GCM \nWiegand \nPIM401-T D2 to R M4x to PMB \nRM \nN/A \nSTAR Edge \nAD401 \n(Mufti-Technologywith \nkeypad only) \nPIM401-T D2 to Edge \nWiegand \nPIM401-T D2 to R M4x to \nEdge RM \nN/A \napC/8X \nAD401 \n(Mufti-Technologywith \nkeypad only) \nPIM401-TD2 to WPSC \nWiegand \nPIM401-T D2 to R M4x to apC \nRM \nN/A \napC/L \nAD401 \n(Mutti-Technologywith \nkeypad only) \nPIM401-T D2 to R M4x to \napC/L RM \nN/A \nAD300 Hard Wired \nTable 6: AD300 Series \nController/Panel \nLocks \nSupported \nRS485 RSI Chain \nWiegand Signal (DO/D1) \nto Panel \nMagnetic Signal (CLK/DATA) \nto Panel \nSTAR Ultra \nSTAR Pro \nSTAR Classic \nAD300 DV \nstyles) \nSuitt in PIM400-485 RSI \nto GCM \nPIB300-TD2 to ACM Wiegand \nPIB300-TD2 to RM4x to ACM \nRM \nPIB300-TD2 to RM4x to ACM RM \nSTAR eX \nAD300 (All \nstyles) \nBuilt in PIM400-485 RSI \nto PMB \nPIB300-TD2 to GCM Wiegand \nPIB300-TD2 to RM4x to PMB \nRM \nPIB300-TD2 to RM4x to PMB RM \n216 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226147\n", "char_count": 1527}, {"efta_number": "EFTA01225932", "page_number": 216, "text_content": "STAR Ultra Wireless Readers \nTable 6: AD300 Series (continued) \nController/Panel \nLocks \nSupported \nRS485 RSI Chain \nWiegand Signal (DO/D1) \nto Panel \nMagnetic Signal (C LK/DATA) \nto Panel \n:SEAR L-i- \nAD300 i A \nstyles) \nPIB300-TD2 to Edge Wiegand \nPIB300-TD2 to RM4x to Edge \nRM \nPIB300- T D2 to Rttilttlx to Edge RM \n,,,,C, _x \nAUs7J A \n,ty _ , i \nPIB300-TD2toWPSC \nWiegand \nPI13300-TD2 to RM4x toapC \nRM \nPIB300- T D2 to Rttilaz to apC RIO \napC/L \nAD300 (All \nstyles) \nPIB300-TD2 to RM4xtoapC/L \nRM \nPIB300-TD2 to RM4xtoapC/L RM \nAD301 Hard Wired FIPS-201 \nNOTE \nThe AD301 (FIPS-201) configuration only supports a Multi-technology reader with Keypad and \nWiegand signaling. \nThe reader appears as a standard Wiegand reader connected to: \n• iSTAR ACM Wiegand Port \n• iSTAR eX CCM Wiegand Port \n• iSTAR Edge Wiegand Port \n• apC/8X WPSC Wiegand Port \n• RM4 or RM4E to any RM Port on iSTAR or apC \nThe PIB301-TD2 is used for all connections. \nTable 7: AD301 Series \nController/Panel \nLocks Supported \nRS485 RSI \nChain \nWiegand Signal (DO/D1) \nto Panel \nMagnetic Signal (C LK/DATA) \nto Panel \nSTAR Ultra \nSTAR Pro \nSTAR Classic \nAD301 \ntrvluit-Technologywith \ncypad only) \nN/A \nPIB301- T D2 to ACM \nWiegand \nPIB301-T D2 to RAil4x to ACM \nRM \nN/A \niSTAReX \nAU301 \nI tvlult-Tecnnologywith \nkeypad only) \nN/A \nPIB301-TD2 to GCM \nWiegand \nPIB301-TD2 to RM4x to PMB \nRM \nN/A \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n217 \nEFTA01226148\n", "char_count": 1441}, {"efta_number": "EFTA01225932", "page_number": 217, "text_content": "STAR Ultra Wireless Readers \nTable 7: AD301 Series (continued) \nController/Panel \nLocks Supported \nRS485 RSI \nChain \nWiegand Signal (DO/D 1 ) \nto Panel \nMagnetic Signal (CLK/DATA) \nto Panel \nSTAR Edge \nAD301 \n(Mufti-Technologywith \nkeypad only) \nPIB301-7 D2 to Edge \nWiegand \nPIB301-7 D2 to RM4x to Edge \nRM \nN/A \napC/8X \nAD301 \n(Multi-Technologywith \nkeypad only) \nPIB301-TD2 to WPSC \nWiegand \nPIB301-TD2 to RM4x to apC \nRM \nN/A \naz.)::. L \nAD301 \n(Mufti-Technologywith \nkeypad only) \nPIB301-7 D2 to RM4x to \napC/L RM \nN/A \nReaders per Controller/Panel \nAperio Wireless Readers \nTable 8: Aperio Wireless Readers \nController/Panel \nInterface \nDevice \nMax # of \nAperio \nHubs \nMax # of Non- \nAperio \nReaders \nMax # of \nAperio \nReaders \nMax # of \nboth \nCombined \nNotes \niSTAR Ultra \nAperio Hub \n(8 Port or 1 \nPort) \n33 \n15 per RS \n485 Porl \n15 \n32 \n32 \niSTAR Ultra is the onty iSTAR \nthat supportsWvelessAperio \nHubs. \nSchlage Wireless Readers \nTable 9: Readers per Controller/Panel- including Schlage Readers \nController/Panel \nInterface Device \nMax # of Non- \nSchlage \nReaders \nMax # of \nSchlage \nReaders \nMax # of \nboth \nCombined \nNotes \nSTAR Ultra \nPIM. AD300 to GCM \n16 \n32 \n32 \nbilaxof 32 PIM(s) and 32 \nReaders \niSTAR Pre \nPIM.AD300 to GCM \n16 \n1E-3 \n16 \nMaxof 16 PIM(s) and 16 \nReaders \nSTAR eX4 door \nPIM. AD300 to PMB \n4 \n16 \n16 \n16, but non-Schlage readers \nmust be numbered 1-4 \n218 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226149\n", "char_count": 1459}, {"efta_number": "EFTA01225932", "page_number": 218, "text_content": "STAR Ultra Wireless Readers \nTable 9: Readers per Controller/Panel- including Schlags Readers (continued) \nController/Panel \nInterface Device \nMax # of Non- \nSchlags \nReaders \nMax # of \nSchlege \nReaders \nMax # of \nboth \nCombined \nNotes \niSTAR eX 8 door \nPIM, AD300 to PMB \n8 \n16 \n16 \n16. but non-Schlage \nReaders must be numbered \n1-8 \nSTAR Pro Direct \nTD2. PIB to ACM \n16 \n16 \n16 \n2 Readers per TD2 or PIB \niSTAR eX4 door \nDirect \nTD2. PIB to GCM or \nPMB \n4 \n4 \n4 \n2 Readers per TD2 or PIB \n'STAR eX 8 door \nDirect \nTD2. PIB to GCM or \nPMB \n8 \n8 \n8 \nRequires USB key \n2 Readers per TD2 or PIB \n'STAR Edge 1 door \nDirect \nTD2. PIB to Edge \nboard \n1 \n1 \n1 \n2 Readers per TD2 or PIB \nSTAR Edge 2 door \nDirect \nT D2. PIB to Edge \nboard \n2 \n2 \n2 \n2 Readers per TD2 or PIB \niSTAR Edge 4 door \nDirect \nT D2. PIB to Edge \nboard \n4 \n4 \n4 \n2 Readers per TD2 or PIG \napC/8X Direct \nTD2. PIB to apC. \nWPSC. or Star \nCoupler \n8 \n8 \n8 \n2 Readers per TD2 or PIB \napC/L Direct \nTD2. PIB to apC/L \n2 \n2 \n2 \n2 Readers per TD2 or PIB \nC•CURE 9000 Hardware Con figuration Guide \nChapter 5 \n219 \nEFTA01226150\n", "char_count": 1089}, {"efta_number": "EFTA01225932", "page_number": 219, "text_content": "STAR Apeno RS-485 Hub Board Edrtor (STAR Ultra onty) \niSTAR Aperio RS-485 Hub Board Editor (iSTAR Ultra only) \nThe iSTAR Aperio RS-485 Hub Board editor allows you to configure wireless Aperio Readers on the Hub. The Hub \nsupports either one or eight Aperio wireless readers. \nThe iSTAR Aperio RS-485 Hub Board Editor has three tabs: \n■ General tab - see iSTAR Aperio RS-485 Hub Board Editor General Tab on Page 220 \n■ Inputs tab - see iSTAR Aperio Hub Board Editor Input Tab on Page 222 \n■ Readers tab - see iSTAR Aperio Hub Board Editor Readers Tab on Page 223 \niSTAR Aperio RS-485 Hub Board Editor General Tab \nThe iSTAR Aperio RS-485 Hub Board editor General tab lets you specify the Aperio RS-485 Hub on which you can \ncreate Aperio readers. \nYou select the type of Hub you want to configure by choosing a type from the HUB Type drop-down list. That \nselection determines the options that are available on the other tabs. \nTo access the iSTAR Aperio RS-485 Hub Board editor General tab, click on the COM 1 or COM 2 tab in the iSTAR \nController editor dialog box. Then, click on Edit in the row name of the RS-485 Port that you want to edit. \nFigure 69 on Page 221 shows the iSTAR Aperio RS-485 Hub Board General tab. \n220 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226151\n", "char_count": 1293}, {"efta_number": "EFTA01225932", "page_number": 220, "text_content": "STAR Aperio RS-485 Hub Board Editor (STAR Ultra only) \nFigure 69: STAR Aped° RS-485 Hub Board General Tab \nrd \nmn• \nQe•Corbart \nGo-Asko Ike:ell \nHUB Iritomobra \nA \nr Moriame Sea \nNM bpi 18 4aro, \nHushing. \nBoast wool I \n</MR'S \n%FAS I \niSTAR Aperio Hub Board Editor General Tab Definitions \nThe fields and buttons on the iSTAR Aperio RS-485 Board editor General tab are described in Table 45 on Page 221. \nTable 45: STAR Apera RS-485 Board Editor General Tab \nField/Button \nDescription \nName \nThis field displays the name of the Aperio Hub \nDescription \nYou can enter a textual description of the Aperio Board in the Description field. \nMaintenance Mode \nClick to put the Aperio RS-485 Hub Board into Maintenance Mode. See Chapter 2: Maintenance Mode for more \ninformation. \nController \nThe name of the STAR Ultra controller: this is a read-onty field. \nHUB Type \nT h is d rop-down list a lbws you to select the type of Aperio board you are configuring. The default selection is 8 Port Hub \nHUB Number \nThis read-onty field contains the HUB number - the same HUB Index number as shown on the STAR Ultra COM1/COM2 \nTabson Page 181. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n221 \nEFTA01226152\n", "char_count": 1203}, {"efta_number": "EFTA01225932", "page_number": 221, "text_content": "STAR Aperio RS-485 Hub Board Editor (STAR Ultra only) \nSTAR Aperio RS-485 Board Editor General Tab (continued) \nField/Button \nDescription \nProduct Version \nDisplays the Product Version. For example, 2.0.0. \nFirmware Version \nDisplays the Firmware Version. For example: 6.2.28176. \nCommunication \nStatus \nThis read-only field displays whether the controlier is in Online. Offline or Unknown state. \nSave and Close \nClick to save your configuration changesand dose the iSTARAperio Hub Board editor. \niSTAR Aperio Hub Board Editor Input Tab \nThis tab allows you to configure a Communications Fail input for the Aperio Hub board. \nFigure 70 on Page 222 shows the iSTAR Aperio Hub Board Input tab. \nFigure 70: iSTAR Aperio Hub Board Input Tab \narhiAl \nErr I i-Lol RS £35 Pat 1 Llys 1 \nsnow \nore* b. I Finnen I \nr SOMling• Mode \nOcege Al Troia \nCelt M PPM \n411 \nlaw. \nI °sow I is \nI Coweancatai FS \nJ \nCs us \nwNO3RS 416 ha I We \n422 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226153\n", "char_count": 994}, {"efta_number": "EFTA01225932", "page_number": 222, "text_content": "STAR Aperio RS-485 Hub Board Editor (STAR Ultra only) \niSTAR Aperio Hub Board Editor Input Tab Definitions \nThe fields and buttons on the iSTAR Aperio Board editor Input tab are described in Table 46 on Page 223. \nTable 46: STAR Aperio RS-485 Board Editor \nField/Button \nDescription \nCreate All \nInputs \nClick to create the Communication Fad Input. When you dick Create All Inputs. the Configured column check box is selected, \nand you can click ri\n in the Edit column to open the STAR Input editor (see iSTAR Input Editor on Page 232. \nDelete All \nInputs \nWhen you click Delete Input. the check box in the Configured column isdeared for the Communications Fail Input, and the \nInput is deleted (a ny settings you have oonfig ured are lost). \nEdit column \nClick in  in the Edit column to open the Input Editor to configure the Communications Fail Input. See STAR Input Editor on \nPage 232. \nInput type \ncolumn \nThis column displays the input type (Communications Fad). \nConfigured \ncolumn \nClick in thiscolumn to create the Communications Fad Input (make it available to be edited). \nName column \nDisplays the name for this Input. The name is system-generated. but you can edit the name. \nSave and \nClose \nClick to save your configuration changes and close the Aperio Hub Board editor. \niSTAR Aperio Hub Board Editor Readers Tab \nThe iSTAR Aperio lub Board editor Readers tab allows you to identify the readers you want to configure, and to \naccess the iSTAR Aperio Reader editor to configure the readers. \nThe following Aperio Reader types can be configured: O100, E100, L100, PR100, IN100, A100, K100, M100, KS100, \n8100, AS100, and Generic types. \nFigure 71 on Page 224 shows the iSTAR Aperio Hub Board Readers tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n223 \nEFTA01226154\n", "char_count": 1791}, {"efta_number": "EFTA01225932", "page_number": 223, "text_content": "STAR Aped() RS-485 Hub Board Editor (STAR Ultra only) \nFigure 71: iSTAR Aperio Hub Board Readers Tab \nEde \n— \n7 \na \nCaltesel \nHas \nTN4 Mule Fleatletl+Lb3R5 435 Pot \n5.4 \nTM Ape Rettl.244.3R5 '35 Pat I UP \niSTAlikee Ftp•Yr344.11 IRS 435 Pet I 1* \n457M Apra Peittlet44104135 435 Pet 1 Ur \nr \niSTM Mr., ree4.5444,3435 435 Pal I IN \nr rr \nEST AA ice, Pewerb.lif)13$ 45 Pal la \n151.13 *Al nestat744.6314S 4.5 Pot Kit \nISTM $SG Paida404b3145 f \nPad RIP \niSTAR Aperio RS-485 Board Hub Editor Readers Tab Definitions \nThe fields and buttons on the iSTAR Aperio RS-485 Board editor Readers tab are described in Table 47 on Page 224. \nTable 47: STAR Apero RS-485 Board Editor Readers Tab \nField/Button \nDescription \nCreate All \nReaders \nClick  to create all 8 readers. When you click Create All Readers the Configured column died< boxes are selected, and you can \nclick — in the Ed It column to open the iSTAR Aperio Reader Editor to configure a Reader. See iSTAR Apart. Reader Editor \non Page 264. \nDelete All \nReaders \nWhen you click Delete All Readers, the died( boxes in the Configured column are cleared for a II 8 Readers. and all 8 \nReaders are deleted (any settings you have configured are lost). \nNOTE: If you Delete all Readers on this tab, the Apart. Door objects that were created automatically for these readersare also \ndeleted. \nEdit column \nClain  in the Edlt column to open the iSTAR Aperio Reader editor to configure a Reader. See STAR Aperio Reader Editor \non Page 264. \n224 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226155\n", "char_count": 1551}, {"efta_number": "EFTA01225932", "page_number": 224, "text_content": "STAR Aperio RS-485 Hub Board Editor (STAR Ultra only) \nSTAR Aperio RS-485 Board Editor Readers Tab (continued) \nField/Button \nDescription \nReader Index \ncolumn \nThisoolumn displays the number of each Reader. \nConfigured \ncolumn \nClick \nin this column to create a Reader (make it available to be edited). \nClearing thischeck boxdeletesthisAperio Reader, and any automaticaltyaeated Aperio Door associated with this Reader, \nafter you click Yes to confirm the deletion in the Warning box that appears. \nNa me °Diu m n \nDisplays the name for this Reader. The name is system-generated. and the Name field is editable. \nSave and \nClose \nClick to save your configuration changes and close the STAR Aperio Hub Board editor. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n225 \nEFTA01226156\n", "char_count": 789}, {"efta_number": "EFTA01225932", "page_number": 225, "text_content": "STAR PIM-485 Board Editor \niSTAR PIM-485 Board Editor \nThe iSTAR PIM-485 Board editor on iSTAR Pro or iSTAR eX allows you to configure Schlage Wireless Readers that \nare connected to a PIM-485 Panel Interface Module (PIM). This board supports up to 16 wireless readers connected \nvia RS-485. \nThe following PIMs are supported: \n■ PIM400-485 (AD400 Series Locks) \n■ AD300 (AD300 Series Locks) \n■ PIM-485 (WA Series Locks) \nThe iSTAR PIM-485 Board Editor has three tabs: \n■ General tab - see iSTAR PIM-485 Board Editor General Tab on Page 226 \n■ Inputs tab - see iSTAR PIM-485 Board Editor Input Tab on Page 228 \n■ Readers tab - see iSTAR PIM-485 Board Editor Readers Tab on Page 229 \niSTAR PIM-485 Board Editor General Tab \n\"the iSIAR\nIv1-185 Board editor General tab lets you specify the type of PIM Board to which you can configure \nSchlage Wireless readers. You select the type of PIM you want to configure by choosing a type from the PIM Type \ndrop-down list. That selection determines the options that are available on the other tabs. \nIf you choose the AD300 (AD300 Series Locks), the Input tab is removed, because the AD300 does not support a \nTamper Input. \nFigure 72 on Page 227 shows the iSTAR PIM-485 Board General tab. \n226 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226157\n", "char_count": 1302}, {"efta_number": "EFTA01225932", "page_number": 226, "text_content": "STAR PIM-485 Board Editor \nFigure 72: STAR PIM-485 Board General Tab \nalga...10os* \ntry MIME \nizewm. \nGas hp \nI tat \nbawl Ithevolic• \nLynn [n.fa \nMDT* I P ivg0 45,10400 \ntad. I \nkids 0. Asia r \n'non Note sae Mn Is V* Wag \nAMINO \niSTAR PIM-485 Board Editor General Tab Definitions \nThe fields and buttons on the iSTAR PIM-485 Board editor General tab are described in Table 48 on Page 227. \nTable 48: STAR PIM-485 Board Editor General Tab \nField/Button \nDescription \nName \nThis field displays the name of the PIM Board \nDescription \nYou can enter a textual description of the PIM Board in the Description field. \nMaintenance \nMode \nClick to put the STAR PIM-485 Board into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nController \nThe name of the controller; this is a read-onty field. \nPIM Type \nThisdrop-down list allows you to select the type of PIM board you areconfiguring. \n• PIM400-485 (AD400 Series Locks) \n• AD300 (AD300 Series Locks) \n• PIM-485 (WA Series Locks) \nC•CURE 9000 Hardware Con figuration Guide \nChap by 5 \n227 \nEFTA01226158\n", "char_count": 1072}, {"efta_number": "EFTA01225932", "page_number": 227, "text_content": "STAR PIM-485 Board Editor \nSTAR PIM-485 Board Editor General Tab (continued) \nFielcilButton \nDescription \nPIM Number \nThis read-only field contains the PIM number - the same PIM Index number as shown on the STAR Schlage Wireless PIMs Tab \non Page 153 or the STAR eX COM1/COM2 Tabs on Page 173. \nWake on \nRadio \nWake on Radio allows a battery-powered lock device to receive an immediate oommand from the STAR panel that is out of \nsequence with the regular heartbeat communications between the panel and the lock (the default heartbeat interval is 10 \nminutes). The Wake on Radio interval is 10 seconds. \nEnabling this feature allows the reader and lock to respond more quickly (within ten seconds rather than within ten minutes) to \nmanual actions. Typically the command from the STAR panel to the device will be for a lock or unlock. \nSave and \nClose \nClick to save your configuration changes and close the STAR PIM-485 Board editor. \niSTAR PIM-485 Board Editor Input Tab \nThis tab allows you to configure a Tamper input for the P1M400-485 and PIM-485. \nIf you select the AD300 series lock in the PIM Type Drop-down list on the General tab, the Input tab is removed \nbecause the AD300 series does not have a Tamper Input. \nFigure 73 on Page 228 shows the i51'AR PIM-485 Board Input tab. \nFigure 73: STAR PIM-485 Board Input Tab \nSr.. eV Oose \nUwe \ntenons,\nPosen Deal \nr lberrvec• Mos \n(Jinni h.. I Parabrij \na. \nv• Clerk VIM \nDeng kat \nhalloo \nUnload \nNils \nFRO* \n228 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226159\n", "char_count": 1536}, {"efta_number": "EFTA01225932", "page_number": 228, "text_content": "STAR PIM-485 Board Editor \niSTAR PIM-485 Board Editor Input Tab Definitions \n[he fields and buttons on the iSTAR PIM-485 Board editor Input tab are described in Table 49 on Page 229. \nTable 49: STAR PIM-485 Board Editor \nField/Button \nDescription \nCreate Input \nClick to create the Tamper input. When you dick Create input, the Configured column check box is selected. and you can click \nri  in the Edit column to open the STAR input editor (see iSTAR input Editor on Page 232. \nDelete input \nWhen you click Delete input, the check box in the Configured column is cleared for the Tamper input, and the Tamper input is \nimmediatetydeleted (any settings you have oonfigured are lost). \nEdit column \nClick(- 1in the Edit column to open the input Editor to configure the Tamper input. See STAR input Editor on Page 232. \nInput type \ncolumn \nThis column displays the input type (Tamper). \nConfigured \ncolumn \nClick in thiscolumn to create the Tamper input (make it available to be edited). \nName column \nDisplays the name for this input. The name is system-generated and is read-onty. \nTemplate \nColumn \nDisplays the Template used for creating this input. If the input isnot yet configured, you can dick in this column, then dick to select \nan input Template. If the Configured column displays V this field cannot be edited. \nSave and \nClose \nClick to save your configuration changes and close the STAR PIM-485 Board editor. \niSTAR PIM-485 Board Editor Readers Tab \nThe iSTAR PIM-485 Board editor Readers tab allows you to identify the readers you want to configure, and to access \nthe iSTAR PIM-485 Reader editor to configure the readers. \nFigure 74 on Page 230 shows the iSTAR PIM-485 Board Readers tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n229 \nEFTA01226160\n", "char_count": 1773}, {"efta_number": "EFTA01225932", "page_number": 229, "text_content": "STAR PIM-485 Board Editor \nFigure 74: iSTAR PIM-485 Board Readers Tab \ndrama-do:sr \nan poi, \n.4t \nQescncan \nLoon Dealt \nr 81•411ex• lkdo \nGov. I VOA \naseles \n11•40os \nv Wm* 4110441•61 \nbay 411140304 \nI aill \nIt \nfail*..d \nIllia \nI \n:4 \n'STAR P•4485Flowler1441114. 01 \nr \nSWIM* anW442-44.141/2411 \nr \nerpermesamo)...twcan \nr \neSTM1 nee Arke441•1111•111 \nJl l \nr \nSTAR me 11•414611011414111 \nr \ncoaremesaasesnann \nr \n4111114111415R4/0/474114.41•4111 \nr \n45M/11111411511444444411141011 \nr \nisuarakissammoosormin \nwi \nr \n30411044161teraHall4W art \nit \nr \nSTAR PONS n \nll.Wlas.l \nla \nr \n4TM1 1411445ResWIN4114Pee SI \n4 \nr \n4LVIPS-146144444414411a,mail \n14 \nr \niSTMposoartnerimmon \nn \nr\num pontanaransonimoin \nr \n'STAR Mae R446/16111111414. al \nli\nr \niSTAR PIM-485 Board Editor Readers Tab Definitions \nThe fields and buttons on the iSTAR PIM-485 Board editor Readers tab are described in Table 50 on Page 230. \nTable 50: iSTAR PIM-485 Board Editor Readers Tab \nField/Button \nDescription \nCreate Al \nReaders \nGilatocreate al 16 readers. When you dick Create All Readers the Configured column check boxes are selected, and you \ncan dick 0 \nin the Ed It column to open the iSTAR PIM-485 Board Editor to configure a Reader. See iSTAR PIM-485 Reader \nEditor on Page 260. \nDelete All \nReaders \nWhen you dick Delete All Readers. the check boxes in the Configured column are deared focal 16 Readers. and all 16 \nReaders are immediately de Med (any settings you haveconfigured are lost). \nEdit column \nCfick 0 \nin the Ed It column to open the iSTAR PIM-485 reader Editor to configure a Reader. See STAR PIM-485 Reader \nEditor on Page 260. \nReader Index \ncolumn \nThis column displays the number of each Reader. \n230 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226161\n", "char_count": 1768}, {"efta_number": "EFTA01225932", "page_number": 230, "text_content": "STAR PIM-485 Board Editor \nSTAR PIM-485 Board Editor Readers Tab (continued) \nField/Button \nDescription \nConfigured \ncolumn \nCid( \nn th is colu mn to create a Reader (make it available to be edited). \nNa me colu m n \nDisplays the name for this Reader. The name is system-generated. and the field is read-only. \nSave and \nClose \nClick to save your configuration changes and close the STAR PIM-485 Board editor. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n231 \nEFTA01226162\n", "char_count": 482}, {"efta_number": "EFTA01225932", "page_number": 231, "text_content": "STAR Input Editor \niSTAR Input Editor \nThe iSTAR Input editor lets you configure an iSTAR Input that you created on an iSTAR Input Board. \nThe iSTAR Input editor (see Figure 75 on Page 233) has the following tabs: \n■ iSTAR Input General Tab on Page 236 \nIdentifies the Controller and Board this Input is configured on, the type of the Input (such as Door Switch), and \nthe object the Input is assigned to, such as a Door. \n■ iSTAR Input Intrusion Zone Tab on Page 237 \nThis tab appears only if you have included this iSTAR Controller in an Intrusion Zone and added this Input as a \nControlled Input. \n■ iSTAR Input Triggers Tab on Page 239 \nThis tab lets you define Triggers that can activate C•CURE 9000 Events and activate outputs. \nSee Triggers Tab for iSTAR Devices on Page 270 for information on creating Triggers for an iSTAR device. \n■ Groups Tab for Hardware Devices on Page 28 \nIf you have created a Group containing iSTAR Inputs and added this Input to it, the iSTAR Input editor also \ndisplays a Group tab. \nThis tab lists the Input groups to which this Input belongs. for information on using the Group tab for your \niSTAR Input. \n■ iSTAR Input Status Tab on Page 239 \nThis tab displays several read-only fields that report the Active, Armed, Hardware, and Supervision status of the \nInput. \n■ iSTAR Input State Images Tab on Page 239 \nThis tab shows the images that are displayed in the Monitoring Station to represent this input. You can change \nthe image used for any of the Input states. \n232 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226163\n", "char_count": 1576}, {"efta_number": "EFTA01225932", "page_number": 232, "text_content": "iSTAR Input Editor \nFigure 75: iSTAR Input Editor \nlint \nCeeenieax \nGT AEI \"tall ADAI dial:MOM \nNation Oeleut \nr iteelearcellcde \nTime Wm SIT45011 Elden Tine f1.61Cenods) \nGenesi I 'bum Zeno IN.= I Gm.' I 9as I law Bind RS,  I 2 golaft,  I \nklereeeabm \nCCOC.5 \nDeaut Sias, \nrpretair \ngam }3O4analical \n;se Noire Fel \ne'as.en*, \nIvo/ 1 \nDeteirce ihrisle14 ono no \nP Sere met datges to nano:erg nice \nr Benne wee \nr Act ote Cr Sukempon Eno,\nArmed \nAccessing the iSTAR Input Editor \nYou can access the iSTAR Input Editor in several ways: \n• To Access the iSTAR Input Editor (iSTAR eX/Edge Controller) on Page 233. \n• To Edit a Main Board Input (iSTAR Classic/Pro Controller) on Page 234. \n• To Edit an ACM Board Input (iSTAR Classic/Pro Controller) on Page 234. \n■ To Edit an Input on an ACM Ext 1/8 Board (iSTAR Classic/Pro Controller) on Page 234. \n■ To Edit a Main Board Input from the Hardware Tree on Page 234. \n■ To Edit a COM1/COM2/COM3 or ACM Input from the Hardware Tree on Page 235 \nTo Access the iSTAR Input Editor (iSTAR eX/Edge Controller) \n1. From the iSTAR Controller Editor, click on the appropriate tab (Inputs, COM1, COM2, or COM3). \n2. Click in the Configured column to create a Main Board or General Purpose Input. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n233 \nEFTA01226164\n", "char_count": 1304}, {"efta_number": "EFTA01225932", "page_number": 233, "text_content": "ISTAR Input Editor \n3. Click the Edit button 0 \nfor the Input you want to edit. \n• To edit a Main Board or General Purpose Input from the Inputs tab, click 0 \nin the Edit column for the Input \nyou want to edit. \n• To edit 1/8 Inputs from the COM1/COM2/COM3 tab, click 0 \nin the Edit column for the Input Board \ncontaining the Input you want to Edit. The iSTAR Input Board Editor opens. Click 0 \nin the Edit column for \nthe Input you want to edit. \nThe iSTAR Input Editor opens (see iSTAR Input Editor on Page 232). \nTo Edit a Main Board Input (iSTAR Classic/Pro Controller) \n1. From the iSTAR Controller Editor, click on the Boards tab. \n2. Click 0 \nin the Edit column for the Input you want to edit. \nThe 'STAR Input Editor opens (see iSTAR Input Editor on Page 232). \n S \nTo Edit an ACM Board Input (iSTAR Classic/Pro Controller) \n1. From the iSTAR Controller Editor, click on the Boards tab. \n2. Click 0 \nin the Edit column for the ACM that contains the Input you want to Edit. The ACM Board Editor \nopens. \n3. Click the Inputs tab. \n4. Click 0 \nin the Edit column for the Input you want to edit. \nThe iSTAR Input Editor opens (see iSTAR Input Editor on Page 232). \nTo Edit an Input on an ACM Ext 1/8 Board (iSTAR Classic/Pro Controller) \n1. From the iSTAR Controller Editor, click on the Boards tab. \n2. Click 0 \nin the Edit column for the ACM that contains the Input you want to Edit. The ACM Board Editor \nopens. \n3. Click the ACM Ext tab. \n4. Click 0 \nin the Edit column for the Input board that contains the Input. \n5. In the Inputs table on this tab, click 0 \nin the Edit column for the Input you want to Edit. \nThe iSTAR Input Editor opens (see iSTAR Input Editor on Page 232). \nTo Edit a Main Board Input from the Hardware Tree \n1. Navigate to your iSTAR Controller in the Hardware Tree and click l> . \n2. Click the Inputs folder. \n3. Double-click on the Input you want to edit. \nThe iSTAR Input Editor opens (see iSTAR Input Editor on Page 232). \n234 \nChapter 5 \nC•CURE 9000 Hardware Conf\n... [truncated, 2030 chars — for the full page use /api/corpus/document/EFTA01225932/233 or ?id=EFTA01225932&page=233]", "char_count": 2030}, {"efta_number": "EFTA01225932", "page_number": 234, "text_content": "STAR Input Editor \nTo Edit a C0M1/COM2/COM3 or ACM Input from the Hardware Tree \n1. Navigate from your iSTAR Controller in the Hardware Tree to the appropriate COM Board (on an iSTAR eX or \niSTAR Edge Controller) or ACM Board (on an iSTAR Classic/Pro Controller). \n2. Click l> on Input Boards, as shown in Figure 68 on Page 209. \nFigure 76: STAR Input Boards in the Hardware Tree \nHardware \nTM \ngoad \n••• \nHagrae TIN \ne.<MM \n5 <dr Ill \nc p expl \n▪ \nDcat \n▪ \nflevalm \nivA \n0tlatz \n: ta Realm \nC0MI *al \nOa IWO*** \nMI C0MISTAR If pa Bann a. al \nCalbSTAR kat DoevRa. M \novivovves \nRoo** \nC0112a11 \nHardware \nit \n6TAFI IrcotOcei \nHoltman Tice \nCCa Pak \n,a c CURE Mobile \n, aincdProckakt \neti 6TAA co, 04 \nC\n \nDOM \nDreMn \nfraud \n°Jon \n11 Realm \nAallao 4 \nOA 1.4I8_& \n6TOR legmBoallaDilfgo \nMAIR Inn Boact2AO.19o1 \nja Iraat \nautosBoa* \nV \n3. Click l> on the Input board that contains the Input you wish to edit. \n4. Click l> on Inputs under that board. \n5. Double-click on the Input you wish to edit. \nThe iSTAR Input Editor opens. \nConfiguring an iSTAR Input \nWhen you configure an iSTAR Input, you use the Input Editor tabs to define the Options, Default State, Triggers, and \nState Images for the Input. \nTo Configure an iSTAR Input \n1. Access the Input Editor for the Input you wish to edit (see Accessing the iSTAR Input Editor on Page 233). \n2. Click the Input General tab: \n• Modify the name of the Input in the Name field, if desired. \n• Add a textual description of the Input to the Description field. \n• Enable the Input by clicking the Enabled field. \n• Modify the Options settings for the Input. See the definitions for the Options fields in on Page 236. \n• Set the Default State for the Input to Armed (J) or not Armed U. \n3. Click the Intrusion Zone tab (if available) to view the name of the Intrusion Zone this Input is part of, and the \nDisplay Name used by the Intrusion Zone for this Input. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n235 \nEFTA01226166\n", "char_count": 1976}, {"efta_number": "EFTA01225932", "page_number": 235, "text_content": "STAR Input Editor \n4. Click the Input Triggers tab. iSl'AR Input Triggers Tab on Page 239 defines the Input Properties you can use in \ntriggers. Configure the triggers you need for this Input by following the steps in Triggers Tab for iSTAR Devices \non Page 270. \n5. Click the Input Status tab to view the Active, Armed, Hardware, and Supervision status of the Input. \n6. Click the Input State Images tab to view the state images for this Input. If you wish to customize the state images \nfor this Input, follow the steps in State Images Tab for iSTAR Devices on Page 274. \n7. When you have finished configuring this Input in the Input Editor, click Save and Close to save the settings you \nhave configured. \niSTAR Input General Tab \nThe iSl'AR Input General tab displays information that identifies the Input and allows you to configure the Options \nand Default State for the input.Figure 75 on Page 233 shows the iSTAR Input General tab. \niSTAR Input General Tab Definitions \nTable 51 on Page 236 lists the fields and buttons that appear on the iSTAR Input General tab. \nTable 51: iSTAR Input General Tab Definitions \nField/Button \nDescription \nName \nDisplays the name for this Input. The name is system-generated by default. but you can edit this name by clicking in this \nfield. \nDescription \nEnter a textua I com ment about the Input. such as its location or purpose. This text is for information only. \nEnabled \nClick cg to enable the Input. \nMaintenance Mode \nClick to put the iSTAR Input into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nPartition \nThis read-only field identifies the Partition in which this Input resides. \nIdentification \nController \nThis read-only field identifies the iSTAR Controller to which this Input is attached. \nBoard \nThis read-only field identifies the iSTAR Controller board to which this Input is attached. \nType \nReflects whether the Input has been assigned to a Door or other object. These include: \n• General \n• Door Switch \n• Re\n... [truncated, 2289 chars — for the full page use /api/corpus/document/EFTA01225932/235 or ?id=EFTA01225932&page=235]", "char_count": 2289}, {"efta_number": "EFTA01225932", "page_number": 236, "text_content": "STAR Input Editor \nTable 51: STAR Input General Tab Definitions (continued) \nFielcUButton \nDescription \nOptions \nDebounce Threshold \n(1/10 sec) \nin this field, enter the time that an input must be in a particular state before it is reported as a state change. It is used to \nfitter out spurious changes. The units range from 0- 60 seconds. the defautt is 0. \nNOTE: For Proprietary Burglar Alarm applications, the Debo u nee Threshold field must be programmed for a \nmaximum of 90 seconds. \nSupervised \nThis field indicates that the in puts on the board are Supervised. This is a read-onty field. \nNOTE: For Proprietary Burglar Alarm applications. the Supervised check box must be selected. \nSend state changes to \nmonitoring station \nTo have a notification of changes in state of the input sent to the guard station, select the Send state changes to the \nmonitoring station check box. \nNOTE: For Proprietary Burglar Alarm applications, the Send state changes to the monitoring station option must \nbe selected. \nSend state change to \njournal \nTo have a notification of changes in state of the input sent to the journal, select the Send state changes to Journal \ncheck box. This option will be selected by dela utt. \nReverse sense \nWhen th is option is selected. the interpretation of the board's Supervised Resistors is reversed. \nActivate on Supervision \nError \nWhen this option is selected. the input will be activated on a Supervision error. \nDefault State \nArmed \nI When th is option is selected. the input is armed by default. This is useful if you are not providing arming via an event. \niSTAR Input Intrusion Zone Tab \nThe iSTAR Input Intrusion Zone tab appears only if the iSTAR Input is included in an Intrusion Zone. Figure 77 on \nPage 238 shows the iSTAR Input Intrusion Zone tab. \nAn Input assigned as an iSTAR Intrusion Zone Controlled or Protected Input displays read-only assignment \ninformation on the Intrusion Zone tab of the Input Editor. This tab only displays when the Input is a\n... [truncated, 2207 chars — for the full page use /api/corpus/document/EFTA01225932/236 or ?id=EFTA01225932&page=236]", "char_count": 2207}, {"efta_number": "EFTA01225932", "page_number": 237, "text_content": "STAR Input Editor \nFigure 77: STAR Input Intrusion Zone Tab \nGi Save zed COSI \nBMW \nDIWit•CM. \nAR 1w \nP • \n• \nPear DOM \nr Martian.\", Mode \nTim* \nallT06,00) Ewan Tone VS &Canada) \nGres \nYampa+ Bre I Turn I Grow I Siam I Um DA'S SS I State laba“ \n%typo Ices \nIretswei Zeno \nwow Nan I \nThe iSl'AR Input Intrusion Zone tab displays read-only fields that give Intrusion Zone assignment information for \nthis Input. \nTable 52: STAR Input Intrusion Zone Tab Definitions \nFieid/Button \nDescription \nIntrusion Zone \nName of STAR Intrusion Zone this Input is assigned to \nDisplay Name \nDisplays the name you entered for this Input on the STAR Intrusion Zones Editor Inputs tab in the Controlled Inputs table. \nNOTE: This is the unique LCD display name for this Input that is used whenever the Intrusion Zone needs to display th is door as \nan 'offnormal' point on the Reader LCD. \nNOTE \nThe Dynamic View for iSTAR Inputs also allows you to add a column that identifies the Intrusion \nZone to which the Inputs belong. \n238 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226169\n", "char_count": 1079}, {"efta_number": "EFTA01225932", "page_number": 238, "text_content": "'STAR Input Editor \niSTAR Input Triggers Tab \nYou can create iSTAR Input Triggers for the properties shown in Table 53 on Page 239. \nFor iSTAR Main Board and Special Purpose Inputs such as Tamper, Power Failure, and Battery Low, you can only \ncreate Triggers for the Active Status property. \nTable 53: STAR Input Trigger Properties \nProperty \nDescription \nActive Status \nValues that you can use for Triggers are\"Active\" and \"Inactive\". \nArmed Status \nValues that you can use for Triggersare\"Armed\" and \"No Error. \nSupervision Error Status \nValues that you can use for Triggersare 'Error' and \"No Error\". \nSee Triggers Tab for iSTAR Devices on Page 270 for information on creating Triggers for an iSTAR device. \niSTAR Input Status Tab \nThe iSTAR Input Status tab displays several Input properties in read-only fields. Table 54 on Page 239 lists the fields \non the iSTAR Input Status tab. \nTable 54: STAR Input Status Tab Definitions \nFiekUButton \nDescription \nActive Status \nDisplays whether the Input is Active or Inactive. \nArmed Status \nDisplays whether the Input is Armed or Disarmed. \nHardware Status \nDisplays the Hardware Status value for the Input. Possible values are Secure, Active, Open Loop, Shorted Loop, Fault, or \nGround. \nSupervision \nStatus \nDisplays the Supervision Status value for the Input. Possible values are: \n• Unknown - the host has not received the input status reported from the panel yet. \n• Uninitiabzed - the panel reports no error on the input. \n• Error - the input is in error state, and the detail can be seen in the Hardware Status field. \niSTAR Input State Images Tab \nThe iSTAR Input State Images tab provides a means to change the default images that are displayed on the C•CURE \n9000 Monitoring Station to indicate iSTAR Input states. \nSee State Images Tab for iSTAR Devices on Page 274 for information on using the State Images tab for an iSTAR \nInput. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n239 \nEFTA01226170\n", "char_count": 1964}, {"efta_number": "EFTA01225932", "page_number": 239, "text_content": "STAR Input Editor \niSTAR input State images Tab Definitions \nTable 55 on Page 240 shows the iSTAR Input States and the default State Images. \nTable 55: STAR Input State Images \nTab Definitions \nIcon \nDescription \nUnknown \ntO \nActive \n. h. \nilla . \nArmed Enabled \nDisarmed Enabled \nfill \nii\nSupervision \nii \nError \nDisabled \nIi\nUpdate Disabled \n240 \nChapter 5 \nC•CURE 9000 Iiiitdmite Conligutation Guide \nEFTA01226171\n", "char_count": 417}, {"efta_number": "EFTA01225932", "page_number": 240, "text_content": "STAR Output Editor \niSTAR Output Editor \nThe iSTAR Output editor lets you configure an iSTAR Output that you created on an iSTAR Output Board. \nThe iSTAR Output editor (see on Page 241) has the following tabs: \n• ISTAR Output General tab \nIdentifies the Controller and Board this Output is configured on, the type of the Output (such as Alternate Shunt \nRelay), and the object the Input is assigned to, such as a Door. See iSTAR Output General Tab on Page 245. \n• ISTAR Output Groups tab \nIf you have created a Group containing iSTAR Outputs and added this Output to it, the iSTAR Output editor \nalso displays a Group tab. \nThis tab lists the Output groups to which this Output belongs. See Groups Tab for Hardware Devices on Page 28 \nfor information on using the Group tab for the iSTAR Output. \n• iSTAR Output Status tab \nThis tab displays several read-only fields that report the Active, Armed, Hardware, and Supervision status of the \nOutput. See iSTAR Output Status Tab on Page 246. \n• ISTAR Output State Images tab \nSee iSTAR Output State Images Tab on Page 246. \nFigure 78: \"STAR Output Edda' \nAS to CO“ \n...77.7813MEMIflIT \nErebied \nMvrteranct Mode \nPennon CdeA \nGertenl I Stabs I LW Mind Fields I Sine imp- I \nOutut Mediae \nOtAcns \ncaeoller \n&ant \nTyr \n&semi:red b. \nCyan= \nKba-I \nSTAR lira KMI.Uba.1 \n'General \npal \nea. duration (1/10 sec) IV \nr llarsy tetrozed \nP Seed stet hsµs to crsortnn; stet*,\nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n241 \nEFTA01226172\n", "char_count": 1481}, {"efta_number": "EFTA01225932", "page_number": 241, "text_content": ".5 I AR O..it;flit L.d tuf \nAccessing the iSTAR Output Editor \nYou can access the iSTAR Output Editor in several ways: \n■ To Access the iSTAR Output Editor (iSTAR eX/Edge Outputs Tab) on Page 242. \n■ To Access the iSTAR Output Editor (iSTAR eX/Edge COM Tabs) on Page 242. \n■ To Edit a Main Board Output (iSTAR Classic/Pro Boards Tab) on Page 242. \n■ To Access the iSTAR Output Editor (iSTAR Classic/Pro ACM Board Outputs Tab) on Page 242 \n■ To Access the iSTAR Output Editor (iSTAR Classic/Pro ACM Board ACM Ext Tab) on Page 243 \n■ To Edit a Main Board Output from the Hardware Tree on Page 243. \n■ To Edit a COM1/COM2/COM3 or ACM Output from the Hardware Tree on Page 243 \nTo Access the iSTAR Output Editor (iSTAR eX/Edge Outputs Tab) \n1. From the iSTAR Controller Editor, click on the Outputs tab. \n2. Click in the Configured column to create a Relay Output or an Open Collector Output. \n3. Click the Edit button 0 \nfor the Output you want to edit. \nThe iSTAR Output Editor opens (see iSTAR Output Editor on Page 241). \nTo Access the iSTAR Output Editor (iSTAR eX/Edge COM Tabs) \n1. From the iSTAR Controller Editor, click on the COM1, COM2, or COM3 (iSTAR Edge only) tab. \n2. Click in the Configured column of the Output Boards table to create an Output Board. \n3. Click \nin the Edit column for the Output board you want to edit. \nThe iSTAR Output Board Editor opens (see iSTAR Output Board Editor on Page 208). \n4. Click in the Configured column of the Outputs table to create an Output. \n5. Click the Edit button 0 \nfor the Output you want to edit. \nThe iSTAR Output Editor opens (see iSTAR Output Editor on Page 241). \nTo Edit a Main Board Output (iSTAR Classic/Pro Boards Tab) \n1. From the iSTAR Controller Editor, click on the Boards tab. \n2. Click in the Configured column to create a Main Board Output. \n3. Click 0 \nin the Edit column for the Main Board Output. \nThe iSTAR Output Editor opens (see iSTAR Output Editor on Page 241). \n S \nTo Access the iSTAR Output Editor (iSTAR Classic/Pro \n... [truncated, 2235 chars — for the full page use /api/corpus/document/EFTA01225932/241 or ?id=EFTA01225932&page=241]", "char_count": 2235}, {"efta_number": "EFTA01225932", "page_number": 242, "text_content": "STAR Output Edrtor \n3. Click 0 \nin the Edit column for the ACM Board that contains the Input you want to Edit. The ACM Board \nEditor opens. \n4. Click the Outputs tab on the ACM Board Editor. \n5. Click in the Configured column to create an Output. \n6. In the Outputs table on this tab, click 0 \nin the Edit column for the Output you want to Edit. \nThe iSTAR Output Editor opens (see iSTAR Output Editor on Page 241). \nTo Access the iSTAR Output Editor (iSTAR Classic/Pro ACM Board ACM Ext Tab) \n1. From the iSTAR Controller Editor, click on the Boards tab. \n2. Click in the Configured column of the ACMs table to create an ACM Board. \n3. Click 0 \nin the Edit column for the ACM Board that contains the Input you want to Edit. The ACM Board \nEditor opens. \n4. Click the ACM Ext tab on the ACM Board Editor. \n5. Click in the Configured column of the Output Boards table to create an Output Board. \n6. In the Output Boards table on this tab, click 0 \nin the Edit column for the Output Board you want to Edit. \nThe iSTAR Output Board Editor opens (see iSTAR Output Board Editor on Page 208). \n7. Click in the Configured column of the Outputs table to create an Output . \n8. In the Output Boards table on this tab, click 0 \nin the Edit column for the Output Board you want to Edit. \nThe iSTAR Output Editor opens (see Figure 78 on Page 241). \nTo Edit a Main Board Output from the Hardware Tree \n1. Navigate to your iSTAR Controller in the Hardware Tree and click r> . \n2. Click the Outputs folder. \n3. Double-click on the Output you want to edit. \nThe iSTAR Output Editor opens (see iSTAR Output Editor on Page 241). \nTo Edit a COM1/COM2/COM3 or ACM Output from the Hardware Tree \n1. Navigate from your iSTAR Controller in the Hardware Tree to the appropriate COM Board (on an iSTAR eX or \niSTAR Edge Controller) or ACM Board (on an iSTAR Classic/Pro Controller). \n2. Click I> on Output Boards, as shown in Figure 79 on Page 244. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n243 \nEFTA01226174\n", "char_count": 1996}, {"efta_number": "EFTA01225932", "page_number": 243, "text_content": "STAR Output Editor \nFigure 79: iSTAR Output Boards in the Hardware Tree \nHardware \n. WARW., Bawl \n•• CI • \nOr\nHoeft* Tree \nSew h \n.; weber. \nLi Heel \n0\n:4 fern \nrens \nDees= \na! row \n0 °Wert \nnee*, \nOEI COW I le al \n0 4 eye eowli \nCCeeldIAR Irpl Band ea NI \nCOMISIAR kw,/ Romp. al \njal Owa lloaW \n4 Ruda* \n1:0112•011 \n• \nHardware \n• draiR Ira, Coed \nv \nHades' Nee \nC. eeC Gametes \nC OJRE Hebb \nO. detwRiodaree \nI(ff:p 6 DA pa 04 \nE\nl\n \nNat \nC (*valve \nkW; \noop.i. \nSeed. \nReedy. \nCal alto 4 \nInpfloods \n6T0.9 lope BoaawC111 iao I \n: t(86TM \nBood2ACIII we I \nCla 'rah \nOutwit Flab \n3. Click C> on the Outpu board that contains the Input you wish to edit. \n4. Click C> on Outputs under that board. \n5. Double-click on the Output you wish to edit. \nThe iSTAR Output Editor opens (see iSTAR Output Editor on Page 241). \nConfiguring an iSTAR Output \nWhen you configure an iSTAR Output, you use the Output Editor tabs to define the Options and State Images for the \nOutput. \nTo Configure an iSTAR Output \n1. Access the Output Editor for the Output you wish to edit (see Accessing the iSTAR Output Editor on Page 242). \n2. Click the Output General tab: \n• Modify the name of the Output in the Name field, if desired. \n• Add a textual description of the Output to the Description field. \n• Enable the Output by clicking the Enabled field. \n• Modify the Options settings for the Output. See the definitions for the Options fields in Table 56 on Page 245. \n3. Click the Output Status tab to view the Active Status of the Output. \n4. Click the Output State Images tab to view the state images for this Output. If you wish to customize the state \nimages for this Output, follow the steps in State Images Tab for iSTAR Devices on Page 274. \n5. When you have finished configuring this Output in the Output Editor, click Save and Close to save the settings \nyou have configured. \n244 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226175\n", "char_count": 1935}, {"efta_number": "EFTA01225932", "page_number": 244, "text_content": "STAR Output Editor \niSTAR Output General Tab \nThe iSTAR Output General tab displays information that identifies the Output and allows you to configure the \nOptions for the Output. Figure 78 on Page 241 shows the iSTAR Output General tab. \niSTAR Output General Tab Definitions \nTable 56 on Page 245 lists the fields and buttons that appear on the iSTAR Output General tab. \nTable 56: STAR Output General Tab Definitions \nField/Button \nDescription \nIdentification \nName \nDisplays the name for this Output. The name is system-generated bydefault. but you can edit this name byclicking in click in \nthis field. \nDescription \nEnter a textual com ment about the Output. such as its location or purpose. This text is for information onty. \nEnabled \nClick 4.,  to enable the Output. \nMaintenance \nMode \nClick to place the iSTAR Output into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nPartition \nThis read-onty field identifies the Partition in which this Output resides. \nOutput Identification \nController \nThis read-onty field identifies the STAR Controller to which this Output is attached. \nBoard \nThis read-onty field identifies the STAR Controller board to which this Output is attached. \nType \nReflects whether the Output has been assigned to a Door or other object. These include: \n• General \n• Door Lock \n• Shunt Expiration Relay \n• Alternate Shunt Relay \n• Elevator Button \nNOTE: The Elevator output assignment has not been evaluated by UL. \nAssigned to \nDisplays the Elevator or Door object name with which this Output is config ured. \nConnection \nIdentifies the Input number on the hardware board to which this Output is connected. \nOptions \nPulse Duration \n(1/10sec) \nThis is a momentary activation which is entered in second intervals with a default of 0 seconds. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n245 \nEFTA01226176\n", "char_count": 1870}, {"efta_number": "EFTA01225932", "page_number": 245, "text_content": "iSTAR Output Editor \nTable 56: STAR Output General Tab Definthons (continued) \nFlekUButton \nDescription \nNormalty \nenergized \nThis field is used to specify whether the Output is wised such that current is normally on or not. The default setting (not \nselected) signifies that the Output is wised so that the current is normally off and when the Output is in an On state. the circuit \nis energded. \nSend state \nchanges to \nmonitoring station \nTo have a notification of changes in state of the Output sent to the Monitoring station. select the Send state changes to the \nmonitoring station died< box. \nNOTE: For Proprietary Burglar Alarm applications, the Send state changes to the monitoring station option must be \nselected. \nThis selection is unavailable for an iSTAR Door Output. State changes fora Door Output are not sent to the Monitoring \nStation. \nSend state \nchanges to pur nal \nTo have a notification of changes in state of the Output sent to the journal. select Send state changes to journal. This \noption is selected by default. \nThis selection is unavailable for an iSTAR Door Output. State changes fora Door Output are not sent to the journal. \niSTAR Output Status Tab \nThe iSTAR Output Status tab displays the State of the Output. \nTable 57: STAR Output Status Tab Definitions \nField/Button \nDescription \nActive Status \nDisplaysthe status of the Output - either Active or Inactive. \niSTAR Output State Images Tab \nThe iSTAR Output State Images tab provides a means to change the default images that are displayed on the \nC•CURE 9000 Monitoring Station to indicate iSTAR Output states. \nSee State Images Tab for iSTAR Devices on Page 274 for information on using the State Images tab for an iSTAR \nOutput. \niSTAR Output State Images Tab Definitions \nTable 58 on Page 246 shows the iSTAR Output States and the default State Images. \nTable 58: iSTAR Outpu State Images Tab Definitions \nIcon \nDescription \nIcon \nDescription \nr\nUnknown \nInactive \n248 \nChapter 5 \nC•CURE 9000 Hardware Configu\n... [truncated, 2027 chars — for the full page use /api/corpus/document/EFTA01225932/245 or ?id=EFTA01225932&page=245]", "char_count": 2027}, {"efta_number": "EFTA01225932", "page_number": 246, "text_content": "STAR Output Editor \nTable 58. STAR Output S ate Images Tab Definitions(con-\ntinued) \nIcon \nDescription \nIcon \nDescription \n. .._ \n1 , \nti \nActive \nDisabled \n1p\nFlashing \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n247 \nEFTA01226178\n", "char_count": 241}, {"efta_number": "EFTA01225932", "page_number": 247, "text_content": "STAR Reader Editor \niSTAR Reader Editor \nThe iSTAR Reader editor lets you configure an iSTAR Reader that you created on an iSTAR Controller. \nThe iSTAR Reader editor (see Figure 80 on Page 249) has the following tabs: \n■ iSTAR Reader General tab \nLists the Reader name, connections, and card formats for a reader connected to an iSTAR. See iSTAR Reader \nGeneral Tab on Page 250. \n■ iSTAR Reader I/O tab \nThis tab lets you configure the available Inputs and Outputs for the Reader. See iSTAR Reader I/O Tab on Page \n252. \n■ iSTAR Reader Keypad tab \nThis tab lets you configure the settings and options for the Reader Keypad. See iSTAR Reader Keypad Tab on \nPage 253. \n■ iSTAR Reader Triggers tab \nSee Triggers Tab for iSTAR Devices on Page 270 for information on creating Triggers for an iSTAR device. \n■ iSTAR Reader Groups tab \nIf you have created a Group containing iSTAR readers and added this Reader to it, the iSTAR Reader editor also \ndisplays a Group tab. \nThis tab lists the Reader groups to which this Reader belongs. See Groups Tab for Hardware Devices on Page 28 \nfor information on using the Group tab for the iSTAR Reader. \n■ iSTAR Reader Status tab \nThis tab displays several read-only fields that report the Communications, PIN Required, and Keypad Command \nAllow Status of the Reader. See iSTAR Reader Status Tab on Page 256. \n■ iSTAR Reader State Images tab \nThis tab displays the default images used to depict this reader in the Monitoring Station. You can use this tab to \ncustomize these state images. See iSTAR Reader State Images Tab on Page 258. \n248 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226179\n", "char_count": 1641}, {"efta_number": "EFTA01225932", "page_number": 248, "text_content": "STAR Reader Editor \nFigure 80: STAR Reader Editor \nSamna-. \nkomuma M1VYrTMW a. \nErase \nPS \nCS \nr \nflee Dr. ST16L Gs la IUS \nSki, \nI **SI a \nPan IS I u.0..p.ilsa I a \nI \ncoma. NO. Sap*, \nflan loan•\n*sat. \nCa \nOrs) \nsw• \nIPP \n^Add r. Prom \nYou can add or remove Card Formats from multiple Readers via an iSTAR Reader Dynamic View. See Add or \nRemove Reader Card Formats on Page 25 for more information. \nAccessing the iSTAR Reader Editor \nYou can access the iSTAR Reader editor in several ways: \n• From the iSTAR eX Controller Wiegand Tab on Page 171 or iSTAR Edge Controller Wiegand Tab on Page 169. \n• From the iSTAR eX COM1/COM2 Tabs on Page 173 or iSTAR Edge COM1/COM2/COM3 Tabs on Page 167 \n• From the iSTAR Classic/Pro Controller iSTAR ACM Board Readers Tab on Page 200. \n• From the iSTAR Ultra iSTAR Controller Boards Tab (iSTAR Classic/Pro) on Page 156, iSTAR Ultra Controller IP-\nACMs Tab on Page 181, and iSTAR Ultra COM1/COM2 Tabs on Page 181. \n• From the iSTAR PIM-485 Board Editor Readers Tab on Page 229. \n• From the Hardware Tree, edit a Reader on a COM board or ACM board. \nIn each case, you must select the Configure column to configure 0 the reader, then click E to open the \niSTAR Reader editor. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n249 \nEFTA01226180\n", "char_count": 1285}, {"efta_number": "EFTA01225932", "page_number": 249, "text_content": "STAR Reader Editor \nConfiguring iSTAR Readers \nWhen you configure an iSTAR Reader, you use the Reader Editor tabs to define the Options and State Images for the \nReader. \nTo Configure an iSTAR Reader \n1. Access the Reader Editor for the Reader you wish to edit (see Accessing the iSTAR Reader Editor on Page 249). \n2. Click the Reader General tab: \n• Modify the name of the Reader in the Name field, if desired. \n• Add a textual description of the Reader to the Description field. \n• Enable the Reader by clicking the Enabled field. \n• For some Readers, you need to select the correct Reader type from the drop-down list. \n• Add the Card Formats that the Reader uses to the Card Format table. See Configuring iSTAR Readers on Page \n250. \n3. Click the Reader Status tab to view the Active Status of the Reader. \n4. Click the Reader State Images tab to view the state images for this Reader. If you wish to customize the state \nimages for this Reader, follow the steps in State Images Tab for iSTAR Devices on Page 274. \n5. When you have finished configuring this Reader in the Reader Editor, click Save and Close to save the settings \nyou have configured. \nNOTE \nSee the C•CURE 9000 Getting Started Guide for a list of UL approved card formats. \niSTAR Reader General Tab \nThe iSTAR Reader General tab displays information that identifies the Reader and allows you to configure the \nOptions for the Reader. Figure 80 on Page 249 shows the iSTAR Reader General tab. \niSTAR Reader General Tab Definitions \nTable 59 on Page 250 lists the fields and buttons that appear on the iSTAR Reader General tab. \nTable 59: iSTAR Reader General Tab Definitions \nField/Button \nDescription \nIdentification \nName \nDisplays the name for this Reader. The name is system-generated by default, but you can edit this name by choking in dick in \nthis field. \nDescription \nEnter a textual comment about the Reader, such as its bcation or purpose. This text is for information only. \n250 \nChapter 5 \nC•CURE 9000 Hardware Config\n... [truncated, 2028 chars — for the full page use /api/corpus/document/EFTA01225932/249 or ?id=EFTA01225932&page=249]", "char_count": 2028}, {"efta_number": "EFTA01225932", "page_number": 250, "text_content": "STAR Reader Editor \nSTAR Reader General Tab Definitions (continued) \nField/Button \nDescription \nEnabled \nClick V to enable the Reader. \nMaintenance \nMode \nClick to put the STAR Reader into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nPartition \nThis read-onty field identifies the Partition in which this reader resides. \nController \nThis read-onty field identifies the STAR Controller to which this reader is attached. \nBoard \nThis read-onty field identifies the STAR Controller board to which this reader is attached. \nAssigned to \nDisplays the Elevator or Door object name with which this reader is configured. \nConnection \nIdentifies the Reader number on the hardware board to which this reader isconnected. \nDevice ID \nThe 15-character ID of the Aperio Reader. (Aperio Reader only.) \nReader Type \nClick on the drop-down menu to select the reader type. \n• RM (Software House Reader Protocol) \n• BLE (Bluetooth Low Energy) \n• OSDP (Open Supervised Device Protocol) \nDefault: RM \nAuthentication \nRequired \nOnly available for BLE readers. \nClick to enable authentication. You will need to be logged into the BLE application on your mobile device for access. \nDefault: Disabled - does not require authorization. \nCard Format \nAdd \nClick Add to add a Card Format. \nIf the card format you desire isnot in the Name Selection dialog box list, dick 0 \nin the Select Type field to select a card \nformat. \nRemove \nClick the row selector ' \nto select one or more Card Format rows (hold down SHIFT or Ctrl to select multiple rows), then \nclick Remove to delete the row(s) for this field. \nName \nDisplays the Name of each Card Format you have chosen for this Reader. \nDescription \nDisplaysthe Description for the Card Format. This field is read-only. \niSTAR General Tab Definitions for iSTAR Ultra Wiegand Readers \nThe iSTAR Reader General tab for readers defined on the Wiegand tab of the iSTAR Ultra ACM Board has additional \nfields that allow you to configure Reader Options. \nTa\n... [truncated, 2209 chars — for the full page use /api/corpus/document/EFTA01225932/250 or ?id=EFTA01225932&page=250]", "char_count": 2209}, {"efta_number": "EFTA01225932", "page_number": 251, "text_content": "STAR Reader Editor \nTable 60: iSTAR Ultra Wiegand Reader General Tab Definitions \nField/Button \nDescription \nReader Options \nLED Control \nYou can select the LED control setting that corresponds with the wiring method used to control the reader LEDs: \n• 3-wire (Red, Yellow, Green) \n• External Bi-color (2-wire Red, Green) \n• 1.wire(A,B, CO) \nBeep on Card Read \nClick to configure the reader to beep when a Card Read occurs. \niSTAR Reader I/O Tab \nThe iSTAR Reader I/O tab displays information that identifies the Reader and allows you to configure the Options \nfor the Reader. Figure 81 on Page 252 shows the iSTAR Reader I/O tab. \nFigure 81: STAR Reader I/O Tab \nWier< wean \nkom rho Rms. )4 tom tare, \nC.M.\nEfetMe \nPS \nDOM \nTee Ur. 0114401 Es T. MICErsW \naims ‘0 liwor I lama I Cpmas i Sas Ipar Dens ti\n l SIN Inn.' \n• Mr a a. \n7\n \nSend] \n \nr... \nColosed \n \n11,111180 \nTA/low I COVIdliallsish \n\u0013 \nSTAR ros • 2 .001061). As.). \n\u0013 \n.T•••• COWISVAliselehiTAA 1 \n\u0013 \nCanneeta \n•COltbSINI Ant \new YagW :ere t \nCoars \nSgin \ni 10. 861\n\u0013 \nCups • .03MYSTM Amoltitk \n\u0013 \nCS. 2.constamr.laTA \niSTAR Reader I/O Tab Definitions \nDefinitions for the fields and buttons on the Reader 1/O tab are described in 'liable 61 on Page 253. \n252 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226183\n", "char_count": 1289}, {"efta_number": "EFTA01225932", "page_number": 252, "text_content": "STAR Reader Editor \nDefinitions for the Inputs on the iSTAR Aperio Reader I/O Tab are described in iSTAR Aperio Reader I/O Tab on \nPage 266. \nThe fields on this tab vary depending upon the type of Reader you are configuring. For example, a Direct Connect \nWiegand Reader displays only the Communications Fail Input on the I/O tab. \nTable et STAR Reader I/O Tab Definitions \nField/Button \nDescription \nInputs \nCreate Al Inputs \nClick to create all eight Inputs. The dieck boxes in the Co nf ig u red column are set to V. \nDelete Al Inputs \nClick to delete all eight Inputs. The check boxes h the Configured column are set to \nEdit \nClick El in this column to open the iSTAR Input Editor to edit this Input. \nConnection \nThis read-only field identifies the position of each input on the I/O tab. \nConfigured \nV indicates that the input has been configured. \nindicates that the input has not been configured. \nName \nDisplays the system-generated name for this Input. You can edit this name by clicking in the field. \nTemplate \nDisplays the Template used for aeating this Input. If the input is not yet configured, you can dick in thisoolumn, then diddo \nselect an input Template. If the Configured column displays V , this field cannot be edited. \nSupervised 1 \nRepresents Supervised Input #1 on iSTAR Readers. Not avaiable on direct connect Wiegand Readers. \nSupervised 2 \nRepresents Supervised Input #2 on iSTAR Readers. Not avaiable on diced connect Wiegand Readers. \nTamper \nRepresents the Tamper input on iSTAR Readers. Not available on diced connect Wiegand Readers. \nCommunications \nFail \nRepresents the Communications Failure Input on iSTAR Readers. \nOutputs \nCreate Al \nOutputs \nClick to create all Outputs. The clued( boxes in the Configured column are set to V.\nDelete Al \nOutputs \nClick to delete all Outputs. The du:id( boxes in the Configured column are set to \n1 \nRepresents Output #1 on iSTAR Readers. \nRepresents Output #2 on iSTAR Readers. Not available On direct connect Wiegand Reade\n... [truncated, 2309 chars — for the full page use /api/corpus/document/EFTA01225932/252 or ?id=EFTA01225932&page=252]", "char_count": 2309}, {"efta_number": "EFTA01225932", "page_number": 253, "text_content": "iSTAR Reader Editor \nFigure 82: iSTAR Reader Keypad Tab \ngine MS • Mil NSW •0.0•COOrel• 411 \nWiasseCia \n*se 3/MAsaNuassCasaa \nrause, \nEsas \nPeas Das \n\"^\". \nPM _W. \n \nn \nOP Ift•IpEn lua•••••••••I \nEi \nMI•1 to. Arnold* \nass anna Mend \n'003.41.• MOW Cowards \nam* IO.J \niSTAR Reader Keypad Tab Definitions \nTable 62: STAR Reader Keypad Tab Definitions \nField/Button \nDescription \nPIN is not required \nif selected, onty a card swipe is required for successful access to the door connected to this reader. \nPIN onty \nif selected. this reader can be used for PIN-Onty access. \nNOTE: PIN only cannot be used as a Query filter value for the PIN Required Status field. \nCard and PIN \nrequired \nif selected. this reader requires both a card swipe and a PIN entry at the keypad for access. \nSchedule \nIf Card and PIN Required isselected, you can select a Schedule object to determine when Card and PIN Required is \nenforced. When the Schedule is active, both Card and PIN are required for access. When the Schedule is inactive, onty a \ncard swipe is required. \nAllow PIN Exempt \n(ADA) \nIf Card and PIN Required isselected, Personnel recordsoonfigured with PIN Exempt (ADA) are exempt from having to \nenter a PIN for access. \n254 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226185\n", "char_count": 1284}, {"efta_number": "EFTA01225932", "page_number": 254, "text_content": "STAR Reader Editor \nTable 62: STAR Reader Keypad Tab Definitions (continued) \nField/Button \nDescription \nAllow card \nnumbers to be \nentered from \nkeypad \nIf you have selected PIN Is not required or Card and PIN required. you can enable Allow card numbers to be \nentered from the keypad by selecting the ched< box. If you chose PIN Only. this option is unavailable (because the \nKeypad must be used to enter a PIN). \nUse PIN+1 as \nduresscode \nIf you have selected PIN Is not required or Card and PIN required, you can enable Use PIN+1 as duress code by \nselecting the check box. If you chose PIN Only. this option is unavatable. \nKeypad \nCommands \nAllowed \nIndicates whether or not Keypad Commands can be entered on this Reader's Keypad and when. Select one of the \nfollowing options from the drop-down fist. The default is Not Allowed. \n• Not Allowed— Keypad Commandscannot be used at the Reader \n• Always Allowed— Keypad Commandscan always be used at the Reader \n• Allowed during specified schedule— Keypad Commands can be used at the Reader during the period specified in \nthe following field. (When you select thisoption. the Schedule for Keypad Commands field becomes evadable.) \nSchedule for \nKeypad \nCommands \nSelect a Schedule from the fist to specify when Keypad Commands can be used at this Reader. When the Schedule is \nactive. Keypad Commands can be used. When the Schedule is inactive. Keypad Commands cannot be used. \niSTAR Reader Triggers Tab \nThe iSTAR Reader Triggers tab allows you to configure triggers for the Reader. You can set up triggers based on \nCommunication Status, PIN Required Status, and Tamper Status. \nFigure 83 on Page 255 shows the iSTAR Reader Triggers tab. \nF Igu re 83: STAR Reader Triggers Tab \n11•••••) \nrvistin. I \n• \n.). JAHOSZOinfit0 I \nis Staid \nes•A \nrote.' I* \nrrRnl “)}. I cum SwF ',up. \nJaw \nben \nILA \n1.1.114. \nSee Triggers Tab for iSTAR Devices on Page 270 for information on creating Triggers for an iSTAR device. \nC•CURE 9000 Hardware Configuration \n... [truncated, 2036 chars — for the full page use /api/corpus/document/EFTA01225932/254 or ?id=EFTA01225932&page=254]", "char_count": 2036}, {"efta_number": "EFTA01225932", "page_number": 255, "text_content": "STAR Reader Editor \nFor iSTAR Readers you can create Triggers for the properties shown in Table 63 on Page 256. \nTable 83: 'STAR Reader Trigger Properties \nProperty \nDescription \nCommunication \nStatus \nPossible values are Normal or Comm Fall. \nPIN Required Status \nPossible values are Not Required or Card and PIN Required. based on the setting for PIN Requirements on the \nKeypad tab. \nTamper Status \nBoolean value; True if the Tamper input has been activated, or False if the Tamper Input has not been activated. \niSTAR Reader Status Tab \nThe iSTAR Reader Status tab displays read-only status fields that allow you to see the current status of the Reader. \nThe type of reader determine the fields displayed on this tab. \n• iSTAR Reader Status Tab Definitions on Page 256. \n• iSTAR PIM-485 Reader Status Tab Definitions on Page 257. \n• iSTAR Aperio Reader Status Tab Definitions on Page 257 \niSTAR Reader Status Tab Definitions \nTable 64: STAR Reader Status Tab Defindions \nField/Button \nDescription \nFirmware Version \nThe version number of the reader firmware. \nCommunications \nCommunications displays the value Normal if the Controller can communicate with the Reader or Comm Fain the \nController cannot communicate with the Reader. \nPIN Required \nPIN Required displays the value True if PIN Required has been selected on the Keypad tabor False othenvise. \nTamper \nDisplays the statusof the Tamper Input. Not available on Direct Connect Wiegand readers. \nKeypad Command \nAliow Status \nThis field displays status of the Keypad Commands Allowed setting from the Reader Editor Keypad tab: \n• Not Allowed \n• Allowed \n• Allowed during specified schedule. \n256 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226187\n", "char_count": 1725}, {"efta_number": "EFTA01225932", "page_number": 256, "text_content": "STAR Reader Editor \niSTAR PIM-485 Reader Status Tab Definitions \nTable 65: STAR PIM-485 Reader Status Tab Definitions \nField/Button \nDescription \nFirmware Version \nThe version number of the reader firmware. \nCommunications \nCommunicationsdisplays the value Normal if the Controller can communicate with the Reader or Comm Fad if the \nController cannot communicate with the Reader. \nPIN Required \nPIN Required displays the value True if PIN Required has been selected on the Keypad tabor False othenvise. \nTamper \nTrue if a Tamper status isdetected for the PIM Reader, or False if no Tamper condition isdetected. \nKeypad Command \nAllow Status \nThis field displays statusof the Keypad Commands Allowed setting from the Reader Editor Keypad tab: \n• Not Allowed \n• Allowed \n• Allowed during specified schedule. \n[PIM1-pro *II - PIM \nTamper \nTrue if a Tamper status is detected for the PIM-485 board to which this reader is attached. or False if no Tamper condition \nisdetected. \nMotor Stall \nTrue if a Motor Stall oandition (a problem with the latching mechanism of the door strike) is detected. or False if no Motor \nStallcondition isdetected. \nAvailable onty for PIM-485 WA Series Locks, not for other AD Locks. \nLow Battery \nTrue if a Low Batterycondition is detected for the PIM Reader, or False if no Low Batterycondition is detected. AvaiLable \nonly for PIM-485 connected Readers. \nManual Lock \nOverride \nTrue if the Manual Lock Overrride has been activated (unlocked by a physical key), or False if the Manual Lock Override \nhas not been activated. Available onty for PIM-485 connected Readers. \nPush Button \nTrue if the Push Button on the lock panel (inside the room) has been pressed, or False if the Push Button has not been \npressed. Available onty for PIM-485 connected Readers. \niSTAR Aperio Reader Status Tab Definitions \nTable 66: STAR Aperio Reader Status Tab Definitions \nFieltUButton \nDescription \nCommunications \nCommunications displays the value Normal if the Controller can communica\n... [truncated, 2385 chars — for the full page use /api/corpus/document/EFTA01225932/256 or ?id=EFTA01225932&page=256]", "char_count": 2385}, {"efta_number": "EFTA01225932", "page_number": 257, "text_content": "STAR Reader Editor \niSTAR Reader State Images Tab \nl'he State Images tab for a Reader provides a means to change the default images used to indicate iSTAR Reader \ndevice states on the Monitoring Station. \nSee State Images Tab for iSTAR Devices on Page 274 for information on using the State Images tab for an iSTAR \nReader. \nSee Table 67 on Page 258 for default State Images for an iSTAR RM reader \nSee Table 68 on Page 258 for default State Images for an iSTAR PIM-485 reader (Schlage wireless lock and reader). \niSTAR Reader State images Tab Definitions \nTable 67: STAR Reader State Images Tab Definitions \nIcon \nDescription \nIcon \nDescription \nUnknown \nTampered \nI T\nT- - \nL \nComm Fai \nNormal \nTable 68: STAR PIM 485 Reader State Images Definibons \nIcon \nDescription \nIcon \nDescription \nIcon \nDescription \nUnknown \nNormal\nLow Battery \nFA\n41.\nENT \nF\nComm Fail \nMotor Stall (Schlage Wireless Only) \nManual Lock Override (Sohlage Wireless \nOnly) \nIllrs, \nI \npi \n4 \nTampered \nPIM Tamper (SohlagsWireless \nOnty) \nPush Button (Sohlags Wireless Only)\nF\nIF\n• Ol \nI \nTable 69: STAR Aperio Reader State Images Definitions \nIcon \nDescription \nIcon \nDescription \nUnknown \ndi \nKey Cylinder Override (Aperio only) \n258 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226189\n", "char_count": 1275}, {"efta_number": "EFTA01225932", "page_number": 258, "text_content": "STAR Reader Editor \nIcon \nDescription \nIcon \nDescription \nComm Fail \nLock State Locked (Aperio only) \nMr ,4 \ni \nrt\nTampered \nLock State Jammed i Acc•O only) \nNormal \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n259 \nEFTA01226190\n", "char_count": 237}, {"efta_number": "EFTA01225932", "page_number": 259, "text_content": "STAR PIM-485 Reader Editor \niSTAR PIM-485 Reader Editor \nThe iSTAR PIM-485 Reader Editor allows you to configure the settings for a Schlage PIM-485 reader/lock wirelessly \nconnected to an iSTAR Pro or eX controller PIM-485 board. \nThe iSTAR PIM-485 Reader editor is shown in Figure 84 on Page 260. \nFigure 84: STAR PIM-485 Reader Editor \nThe iSTAR PIM-485 Reader editor dialog box has the following tabs. \n■ iSTAR Reader General tab \nLists the Reader name, connections, and card formats for a reader connected to an iSTAR Classic/Pro, or iSTAR \neX. See iSTAR Reader General Tab on Page 250. \n■ iSTAR PIM•485 Reader VO tab \nThis tab lets you configure the available Inputs and Outputs for the Reader. See the iSTAR PIM-485 Reader I/O \nTab on Page 261. \n■ iSTAR Reader Keypad tab \nThis tab lets you configure the settings and options for the Reader Keypad on iSTAR Schlage Readers. See iSTAR \nReader Keypad Tab on Page 253. \nOnly Schlage Keypad Mode 1 keypad output format (4 data bits per key with no parity) is supported. The mode \nis configured on the Schlage device. \n■ iSTAR Reader Triggers lab \nSee the Triggers Tab for iSTAR Devices on Page 270 for information on creating Triggers for an iSTAR device. \nYou can define triggers for the following Properties of the iSTAR PIM-485 Reader: \n280 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226191\n", "char_count": 1363}, {"efta_number": "EFTA01225932", "page_number": 260, "text_content": "STAR PIM-485 Reader Editor \nProperty \nValue \nCommunication Status \nNormalor Comm Fad \nLow Battery \nActive Es or inactive • \nManual Lock Override \nActive/go( inactive • \nMotor Stall \nActive/go( inactive • \nParent PIM Tamper \nActive Is or inactive ■ \nPIN Required Status \nNot Required, Card and PN Required, or PIN Only \nPush Button \nActive is or inactive • \nTamper Status \nActive is or inactive ■ \n■ 'STAR Reader Groups tab \nf you have created a Group containing iSTAR readers and added this Reader to it, the iSTAR Reader editor also \ndisplays a Groups tab. \nThis tab lists the Reader groups to which this Reader belongs. See the Groups Tab for Hardware Devices on Page \n28 for information on using the Group tab for the iSTAR Reader. \n■ iSTAR Reader Status tab \nThis tab displays several read-only fields that report the Communications, PIN Required, and Keypad Command \nAllow Status of the Reader. See the iSTAR Reader Status Tab on Page 256. \n■ iSTAR Reader State Images tab \nThis tab displays the default images used to depict this reader in the Monitoring Station. You can use this tab to \ncustomize these state images. See the iSTAR Reader State Images Tab on Page 258. \nYou can add or remove Card Formats from multiple Readers via an iSTAR PIM-485 Reader Dynamic View. See Add \nor Remove Reader Card Formats on Page 25 for more information. \niSTAR PIM-485 Reader I/O Tab \nThe iSTAR PIM-485 Reader I/O tab lets you configure the inputs and outputs for the reader. Each input and output \nis pre-assigned to a specific function for the reader. Typically you can use the Create All buttons to create the inputs \nand outputs, and then click the button in the Edit column to configure each input and output individually. \nYou can configure these inputs and outputs by clicking on 0 \nin the Edit column. You can then create triggers that \ncan activate Events based on state changes. \nExample: \nYou can create a trigger to activate an Event if the Low Battery Input status changes to Active (indicatin\n... [truncated, 2226 chars — for the full page use /api/corpus/document/EFTA01225932/260 or ?id=EFTA01225932&page=260]", "char_count": 2226}, {"efta_number": "EFTA01225932", "page_number": 261, "text_content": "STAR PIM-485 Reader Editor \nFigure 85: STAR PIM-485 Reader ifO Tab \ni mt.t net te, .s. \nt: UR TO ars ens.; mil.. t \nV.61\n8:.. ,,,,,. \nasi 6TAA PlealisidellIMIonl \na.m.. \nnes \nP.M.* WS \nGas It \nI ili\ni\n[a.r..,\n ,,)\nimam \n2 odkaincts :: 0.00/11,03 \nfa \nCanna. \nCoq \nNois \nleoles \nuri \n_..\n0\n—.__. ymisis\nvos.. fte...\n‘rui \n. \n\"dm 001.41N4 POISMS1.1 \nL \n*dm RIM 4SIM P014952•60 . I \nVif••••• Niawr Taw. \nID \nVibes Maio Tons 41.• MA \nWale Pmelt Car. \n0 \nVet Rude Corruceas FS A. \nLa Ikea, \nn \n... ME v ..11/A OM* Amis.1 IC \nMewl laditvons• \nitt \nOlnid La* Owl& .611111404.15. \nIrw \nel \nFtass .a0AIIII46.11=00.. \nGm. \n2 cmikmicetwas Zotkamodoss \nfa. \n— \nGoal \n— \nTmhis \n0 \nOm laddlor \niti \n,C0.41.1.a.CINIMI41111m. \nDefinitions for the fields and buttons on the Reader 1/O tab are described in Table 70 on Page 262. \nTable 70: STAR Reader itO Tab Definitions \nField/Button \nDescription \nInputs \nCreate Al inputs \nClick to create all eight inputs. The check boxes in the Configured column are set to V \nDelete All inputs \nClick to delete all eig ht inputs. The check boxes in the Configured column are set to \nEdit \nClick nin this column to open the iSTAR input editor to edit the input. \nConnection \nT h is read-onty field identifies the position of each input on the ifO ta b. \nConfigured \nV indicates that the input has been configured. \nO indicates that the input has not been configured. \nName \nDisplays the system-generated name for this input. You can edit this name by clicking in the field. \nTemplate \nDisplays the Template used for creating this input. If the input isnot yet configured, you can click in this column, then click to \nselect an input Template. If the Configured column displays V thisfield cannot be edited. \nWireless DSM \nRe presents the Wireless Door Switch Monitor (DSM) for the door. \nWireless REX \nRepresents the Wireless Request To Exit (REX) for the door. \n262 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226193\n", "char_count": 1954}, {"efta_number": "EFTA01225932", "page_number": 262, "text_content": "STAR PIM-485 Reader Editor \nTable 70: STAR Reader I/O Tab Definitions (continued) \nField/Button \nDescription \nWireless Reader \nTamper \nRepresents the Tamper Input on the Wireless Reader. \nWireless Reader \nCommunications \nFail \nRepresents the Communications Failure Input on the Wireless Reader. \nMotor Stall \nRepresents the Motor Stall Input on the Wireless Reader. \nLow Battery \nRepresents the Low Battery Input on the Wireless Reader. \nManual Lock \nOverride \nWhen this input is active, it indicates that the lock has been unlocked by a physical key. \nThe Manual Lock Override status is available on the Status tab for this reader. This property is available for use in triggers. \nPush Button \nWhen this input is active, it indicates that the push button on the lock panel (inside the room) has been pushed. \nThe Push Button Input status is available on the Status tab for this reader. This property is available for use in triggers. \nOutputs \nCreate All Outputs \nClick to create all Outputs. The check boxes in the Configured column are set to V.\nDelete All Outputs \nClick to delete all Outputs. The check boxes in the Co nf igu red column are set to \nDoor Latch Relay \nRepresents the Door Latch Relay Output that is used to unlock the door. \nEdit \nClick[i \nin this column to open the STAR Output editor to edit the Output. \nConnection \nThis read-only field identifies the position of the Output on the I/O tab. \nConfigured \nV indicates that the Output has been configured. \nindicates that the Output has not been configured. \nName \nDisplays the system-generated name for this Output. You can edit this name byclicking in the field. \nTemplate \nDisplays the Template used for creating this Output. If the Output is not yet configured. you can click in this column. then \nclick to select an Output Template. If the Configured column displays V this field cannot be edited. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n263 \nEFTA01226194\n", "char_count": 1945}, {"efta_number": "EFTA01225932", "page_number": 263, "text_content": "STAR Aperio Reader Editor \niSTAR Aperio Reader Editor \nThe iSTAR Aperio Reader editor allows you to configure the settings for an Aperio reader/lock wirelessly connected \nto an iSTAR Ultra controller Aperio RS-485 Hub board. \nThe iSTAR Aperio Reader editor is shown in Figure 86 on Page 264. \nFigure 86: 'STAR Aperio Reader Editor \nI \nOn. iThin \nN.> ,  104,11tr..7) NI ,filS1:•••• • \nteCt•ot r \nA \nA \nelatmeati \nIN. :SA \nr WM. \nS.M./PA) I.10.11 Tows I weal stotrowl \nItImatelbo \nEirixter \nn••• \nWA Fa. \nallele \nes \nI \neletd\n1/4 . I \nCarimas. P•ski \n14400 \nReefaix I:To3 \n1' J \nC.• ea, \nD......... \n4 \nWhen you add an iSTAR Aperio Reader, Enable it in the Aperio Reader editor, and Save and Close the editor, a \nDoor object for that reader is added to the parent Ultra controller in the iSTAR Aperio Doors folder in the Hardware \ntree. \nIf you delete an iSTAR Aperio Reader, the iSTAR Aperio Door associated with the reader is also deleted. \nIf you display a list of iSTAR Doors, the new Aperio Door appears on the list. See iSTAR Aperio Door Editor on Page \n455 for more information on Aperio Doors. \n284 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226195\n", "char_count": 1172}, {"efta_number": "EFTA01225932", "page_number": 264, "text_content": "iSTAR Aperio Reader Editor \nFigure 87: 'STAR Apeno Doors \nSella \n• \n• \nkaal Canty-n es \n• jj Caito,XXix \n4 -j dual* 2 • \nit real edge \n• to dbe le \n• if2 Mors \ngi * I door 1 \nag \"WM \n• ID Star kenoCcas \nuS T AR Apene Fleads•Mt2a5aSPeet Luta \n• t8 COMI4b• 1 \n:• 0.lab2-RS 485 Pal 1-ital. \nanus \nDoor X \n:7..D \nce \nCant \nD \npolo eb croup by hae \nNam I Downie d \nOves SON I Sem AYSS \nI\n<X COW \nNormal \n61Y3 1 \nCoal \nOOP On \nred \nelx \n;\n \nP\nC\n*\n \n,\n \ncoce \nCloud \nHamel \nWaal \nThe iSTAR Aperio Reader editor dialog box has the following tabs. \n• iSTAR Reader General tab \nLists the Ultra controller name, Hub board, Assigned to Door, Reader number, Device ID, and Reader type. See \niSTAR Reader General Tab on Page 250. \n• iSTAR Aperio Reader I/O tab \nThis tab lets you configure the available Inputs and Outputs for the Reader. See the iSTAR Aperio Reader I/O \nTab on Page 266. \n• iSTAR Reader Keypad tab \nThis tab lets you configure the settings and options for the Reader Keypad on iSTAR Aperio Readers. See \niSTAR Aperio Reader Keypad Tab on Page 268. \n• iSTAR Reader Triggers tab \nSee the Triggers Tab for iSTAR Devices on Page 270 for information on creating Triggers for an iSTAR Ultra \ndevice. \nYou can define triggers for the following Properties of the iSTAR Aperio Reader: \nProperty \nValue \nCommunication Status \nNormal or Comm Fai \nKey Cylinder Override \nActive Ea or inactive\nLock State -lammed \nActive Ea or inactive . \nLoa State Locked \nActive Esi or inactive\nLow Battery Status \nActive Esi or inactive\nTamper Status \nActive Esi or inactive\n• iSTAR Reader Status tab \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n265 \nEFTA01226196\n", "char_count": 1650}, {"efta_number": "EFTA01225932", "page_number": 265, "text_content": "'STAR Aperio Reader Editor \nThis tab displays several read-only fields that report the Communications, Tamper, and Low Battery status of the \nReader. See the iSTAR Reader Status Tab on Page 256. \n■ iSTAR Reader State Images tab \nThis tab displays the default images used to depict this reader in the Monitoring Station. You can use this tab to \ncustomize these state images. See the iSTAR Reader State Images Tab on Page 258. \nYou can add or remove Card Formats from multiple Readers via an iSTAR Aperio Reader Dynamic View. See Add \nor Remove Reader Card Formats on Page 25 for more information. \niSTAR Aperio Reader I/O Tab \nThe iSTAR Aperio Reader I/O tab lets you configure the inputs for the reader. Each input is pre-assigned to a specific \nfunction for the reader. Typically you can use the Create All buttons to create the inputs, and then click the button in \nthe Edit column to configure each input individually. \nThe number of inputs available on this tab varies, depending upon the reader model configured on the General tab \nin the Reader Type field. \nYou can configure these inputs by clicking on \nin the Edit column. You can then create triggers that can activate \nEvents based on state changes. \nExample: \nYou can create a trigger to activate an Event if the Lock Low Battery Input status changes to Active (indicating \nthat the reader battery charge is low). See Triggers Tab for iSTAR Devices on Page 270. \nFigure 88 on Page 267 shows a typical iSTAR Aperio Reader I/O tab. \n288 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226197\n", "char_count": 1564}, {"efta_number": "EFTA01225932", "page_number": 266, "text_content": "STAR Aperio Reader Editor \nFigure 88: STAR Aperio Reader I/O Tab \nislAroveavA \n'Wm `WARM. °Pee' ohelfr. qM 1 q, le \nROGRAY! \nA \nr Dam \ncis \nISMrdieldi ISISIN \nI lainigsl \niron\n?Q.rno id ivies \nMai •frpis \nIt \nfana \n0•Igml \nI0. \nj Inside \nIA* CearlOrtraill \nLad lterlanY \nr \nr \nIA.CenneserAil fratatn \n, \nLOS Law 0 alp 610 •00111tia• \nIAASWeArria4 \nr \nUP 9.1.41.1.3. MAI 'aeon,' \nDefinitions for the fields and buttons on the Reader I/O tab are described in Table 71 on Page 267. \nDefinitions for the input types are described in Table 72 on Page 268. \nTable 71: STAR Reader I/O Tab Definitions \nField/Button \nDescription \nCreate All \nInputs \nClick tocreate all Inputs. The check boxes in the Configured column are set to V \nDelete All \nInputs \nClick to delete all Inputs. The check boxes in the Configured column are set ton. \nEdit \nClick [ —] in this column to open the STAR Input editor to edit the Input. \nConnection \nT h is read-onty field indicates the three standard in puts (Com m Fad. Low Battery. and Lock State Jammed. \nConfigured \nV indicates that the Input has been configured. \nindicates that the Input has not been configured. \nName \nDisplays the system-generated name for this Input. You can edit this name by clicking in the field. \nTemplate \nDisplays the Template used for creating this Input. If the Input isnot yet configured, you can click in this column, then click to select \nan Input Template. If the Configured column displays V , this field cannot be edited. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n267 \nEFTA01226198\n", "char_count": 1556}, {"efta_number": "EFTA01225932", "page_number": 267, "text_content": "STAR Aperio Reader Editor \nTable 72: iSTAR Reader I/O Tab Input Definitions \nField/Button \nDescription \nLock Reader Tamper \nRepresents the state of the Tamper input on the lock. \nHandle State / Request to Exit \nRepresents the state of the Request to Exit input associated with the door handle. \nLock State Locked \nRepresents the \nKey Cylinder Override \nRepresents the state of the Key Cylinder Override. \nDoor Position State \nRepresents state of the Door Switch Monitor for the door associated with this reader. \nLock Communications Fail \nRepresents the Lock Communications Failure Input on the Aperio Reader. \nLock State Jammed \nRepresents the Lock State Jammed Input on the Aperio Reader. \nLock Low Battery \nRepresents the Lock Low Battery Input on the Aperio Reader. \niSTAR Aperio Reader Keypad Tab \nThe iSTAR Reader Keypad tab allows you to configure settings for the keypad on the Reader. You can specify how \nthe Reader accepts PIN entries. \nFigure 89: iSTAR Aperio Reader Keypad Tab \nkr. \nr (MIS \ntlini I i 0 \nNom/ I r••.• 9+•l 9r•w \nI \nRN R..\nOita• \na MIN ntt SUM \nr NOW \nr COI VO N  ROM. \nr we• WI *A4411.11-be (*WO •S•Wellef \nr \nJJ \n268 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226199\n", "char_count": 1214}, {"efta_number": "EFTA01225932", "page_number": 268, "text_content": "STAR Aperio Reader Editor \niSTAR Aperio Reader Keypad Tab Definitions \nTable 73: STAR Aperio Reader Keypad Tab Definitions \nField/Button \nDescription \nPIN is not required \nIf selected. onty a card swipe is required for successful access to the door connected to this reader. \nPINonty \nIf selected. this reader can be used for PIN-Onty access. \nNOTE: PIN only cannot be used as a Query filter value for the PIN Required Status field. \nCard and PIN \nrequired \nIf selected, this reader requires both a card swipe and a PIN entry at the keypad for access. \nSchedule \nIf Card and PIN Required is selected, you can select a Schedule object to determine when Card and PIN Required is \nenforced. When the Schedule is active, both Card and PIN are required for access. When the Schedule is inactive, onty a \ncard swipe is required. \nAllow card \nnumbers to be \nentered from \nkeypad \nIf you have selected PIN is not required or Card and PIN required. you can enableAllow card numbers to be \nentered from the keypad by selecting the check box. If you chose PIN Only. thisoption is unavailable (because the \nKeypad must be used to enter a PIN). \nUse PIN+1 as \nduresscode \nIf you have selected PIN is not required or Card and PIN required. you can enable Use PIN*1 as duress code by \nselecting the check box. If you chose PIN Only. thisoption is unavailable. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n269 \nEFTA01226200\n", "char_count": 1417}, {"efta_number": "EFTA01225932", "page_number": 269, "text_content": "T riggers Tab for 'STAR Devices \nTriggers Tab for iSTAR Devices \nC•CURE 9000 uses Triggers, which are configured procedures for activating actions, to activate Events or Outputs \nfor an iSTAR device. A Trigger automatically executes a specified Action when a particular Condition occurs (when \nthe object Property specified in the Trigger reports the Value specified in the Trigger). \nExample: \nTo provide an audible and visible alarm for a power failure condition, you can create two triggers for the \nAC Power Fail Input on an iSTAR controller that are activated when the Input's status changes: \nActivate Output that energizes an audible sounder. \nActivate Output that energizes an LED alarm light installed near an arming/disarming keypad reader. \nFigure 90 on Page 270 shows the Triggers tab for an iSTAR Input, which is typical for an iSTAR device. \nFigure 90: Typical 'STAR TriggersTab \nwit I \nC.,•:nnet  \n_J \ng Inns \nhas. Nwa \nr \nT..2.. Giros= tea a* us scow.) \nOn. I \nI 0••••••1••seei Mtn i COW Mm %am \nF.'s I 9,•••••••• I \nphoto\" \nest inawilitreesi. • vs- \nrms. \nTable 74 on Page 270 provides an example of a configured iSTAR Trigger. \nTable 74: TriggersTab SettingsExample \nThe following Triggers Tab settings: \nProperty \nValue \nAction \nDetails \nSchedule \nTime Zone \nAst ve Status \nAlive \nActivate Event \nSTAR Input Event \nAlways \nTime Zone of the STAR \ncontroller \n270 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226201\n", "char_count": 1448}, {"efta_number": "EFTA01225932", "page_number": 270, "text_content": "T riggers Tab for STAR Devices \nTable 74: Triggers Tab Settings Example (continued) \nWould create the following Trigger: \nAny time (Always Schedule) the Active Status (Property) equalsActive (Value). activate the event (Action) named iSTAR Input Event \n(Details). \nSTAR Input Event is an Event that you would need to create using the Event Editor. \nNOTE \nYou cannot assign a Schedule to an iSTAR Controller trigger. Effectively, iSTAR Controller triggers \nuse an Always Schedule. \nFrom the Triggers tab of an iSTAR device (such as a Controller, Input, or Reader), you can perform the following \ntasks. \n■ Defining a Trigger for an iSTAR Device on Page 271. \n■ Removing a Trigger on Page 272. \niSTAR Triggers Tab Definitions on Page 272 provides definitions for the fields and buttons on an iSTAR Device \nTriggers tab. \nDefining a Trigger for an iSTAR Device \nYou can use the Triggers tab to define a Trigger for an iSTAR device. The typical usage for an iSTAR Trigger is to \nactivate an Event or an Output as the result of a state change of an iSTAR device Property. \nExample: \nWhen an iSTAR Tamper Input changes from the Inactive (normal) to Active (abnormal) state, you wish to \nactivate an Event and activate an audible alarm (an iSTAR Output). \nTime Zones for iSTAR Triggers \nIf you specify a Time Zone in your Trigger definition, you can control when the Schedule for the Trigger is active. \nYou can only select the C•CURE 9000 server Time Zone or the Time Zone of the iSTAR you are editing. \nExample: \nIf you have iSTAR controllers that are in different Time Zones than your C•CURE 9000 server, you may want to \nhave some Triggers activate according to the iSTAR controller's Time Zone, while other Triggers are activated \naccording to the server Time Zone. \nWhen you specify the Time Zone for a Trigger definition to be the same as the iSTAR controller Time Zone, the \nSchedule activation times for the Trigger occur according to the iSTAR controller Time Zone. \nIf you have an iSTAR controlle\n... [truncated, 2486 chars — for the full page use /api/corpus/document/EFTA01225932/270 or ?id=EFTA01225932&page=270]", "char_count": 2486}, {"efta_number": "EFTA01225932", "page_number": 271, "text_content": "Triggers Tab for STAR Devices \n3. Click El within the Property column to open the Property dialog box showing the Properties available for the \ndevice. \n4. Click a Property in the list to select it and add it to the Property column. \n5. Click \nwithin the Value column to display a drop-down list of Values associated with the Property that you \nhave selected. Click a Value that you want to include as a parameter for the trigger to add it to the column. (If \nthere is no set list of Values, you can type in a Value.) \n6. Click \nwithin the Action column to display a drop-down list of valid actions. Click an Action that you want \nto include as a parameter for the trigger to add it to the column. \n7. When you select an Action, the lower pane in the Triggers box displays an entry field or group of entry fields, \nspecific to the selected Action, so that you can configure the Details for the Action. \n8. Once you define the Action details, the Details column displays information about how the Action has been \nconfigured. \n9. For example, if an Event field is displayed in Details, you can click to select an Event that you want to associate \nwith the Trigger. \n10. If the Triggers tab includes a Time Zone column, click within the Time Zone column to display a drop-down \nlist of available Time Zones. Most of the time, you will want to select a Time Zone that is the same as the iSTAR \ncontroller Time Zone. If you do not select a Time Zone, the Time Zone of the C•CURE 9000 server is used by \ndefault. \n11. Click Save and Close to save the iSTAR Trigger. \nRemoving a Trigger \nIf you no longer need a Trigger defined for a Device, you can remove the Trigger. \nTo Remove a Trigger \n1. Click the Triggers tab for your device. \n2. Click the row selector ! \nto select a Trigger row. \n3. Click Remove to delete the selected row. \n4. Click Save and Dose to save the device. \niSTAR Triggers Tab Definitions \nTable 75 on Page 272 provides definitions for the fields and buttons on an iSTAR Triggers tab.\n... [truncated, 2294 chars — for the full page use /api/corpus/document/EFTA01225932/271 or ?id=EFTA01225932&page=271]", "char_count": 2294}, {"efta_number": "EFTA01225932", "page_number": 272, "text_content": "I as for S I AR Du,: sus \nTable 75: STAR Triggers Tab Definitions (continued) \nField/Button \nDescription \nClick the Row Selector to select a row in the Triggers table. \nProperty \nClick with in the Property column, and then click[. The Property browser opens presenting propertiesavailable for the \nComm Port. Click a Property to select it and add it to the column. \nValue \nClick with in the Value column to display a drop-down list of Values associated with the Property that you have selected. Click a \nValue that you want to include as a parameter for the trigger to add it to the column. \nAction \nClick® within the Act Ion column to display a drop-down list of valid actions. Click an Action that you want to include as a \nparameter for the trigger to add it to the column. \nAs you select an Action, a corresponding entry field, or group of entry fields, appear at the bottom of the dialog box. \nClick to select entries for these fields. \nDetails \nDisplays dela its about how the Action was config ured. \nSchedule \nClick within the Schedule column to select a Schedule. \nClick [ji to select a Schedule that you want to associate with the trigger. Schedules are created in the Configuration Pane. \nRefer to the C•CURE 9000 Software Configuration Guide for more information on creating Schedules. \nTime Zone \nClickwithin the Time Zone column to select a Time Zone for Schedule activation. \nClick ri  to select a Time Zone that you want to associate with the trigger Schedule. Typically you can chose either the \nC•CURE 9000 server (host) Time Zone or the Time Zone of the STAR controller. \nIf you specify a Time Zone, the Schedule start and end times are calculated using that Time Zone. \nExample: \nA Schedule that becomes active at 3:00AM would become active at 3:00AM in the Pacific Time Zone, if that Time Zone was \nspecified. Refer to the C•CURE 9000 Software Configuration Guide for more information on Time Zones and Events. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n273 \nEFTA01226\n... [truncated, 2004 chars — for the full page use /api/corpus/document/EFTA01225932/272 or ?id=EFTA01225932&page=272]", "char_count": 2004}, {"efta_number": "EFTA01225932", "page_number": 273, "text_content": "State Images Tab for 'STAR Devices \nState Images Tab for iSTAR Devices \nThe State Images tab provides a means to change the default images used to indicate iSTAR device states on the \nMonitoring Station. \nFrom the State Images tab of an iSTAR device (such as a Controller, Input, Output, or Reader), you can perform the \nfollowing tasks. \n■ Customizing State Images for an iSTAR Device on Page 274 \n■ Restore a Default State Image on Page 275 \nYou can replace the default images with JPG formatted files of your choice, to uniquely identify your objects when \nactivities are displayed on the Monitoring Station Client. \niSTAR State Images Tabs Definitions on Page 274 provides definitions for the fields and buttons on an iSTAR Device \nState Images tab. \niSTAR State Images Tabs Definitions \niSTAR State Images Tabs have the State Images tabs as shown in Table 76 on Page 274. \nTable 76: iSTAR State Images Tabs Definitions \nField/Button \nDescription \nState \nThis column lists the states that are defined for this STAR device. These are the states that are reported on the Monitoring \nStation to reflect the status of this iSTAR device. \nImage \nThis column shows the images that are assigned to eadi of the iSTAR device states. There are images assigned by default to \nevery iSTAR device you create. For any individual iSTAR device, you can use the State Images tab to substitute a \ndifferent.JPG/JPEG image for the default image. See Customizing State Images for an iSTAR Device on Page 274 for \ninstructions. \nSave and \nC Esc \nAfter you have made changes to any settings for the iSTAR device, dick Save and Close to save those changes and Close the \neditor for the device. \nCustomizing State Images for an iSTAR Device \nFrom the State Images tab, you can change the images that appear in the Monitoring Station to represent an iSTAR \ndevice. \nTo Customize an iSTAR Device State Image \n1. Navigate to the State Images tab for the iSTAR device. \n2. Double-click the existing image. \nA Windows Open di\n... [truncated, 2376 chars — for the full page use /api/corpus/document/EFTA01225932/273 or ?id=EFTA01225932&page=273]", "char_count": 2376}, {"efta_number": "EFTA01225932", "page_number": 274, "text_content": "State Images Tab for STAR Devices \nRestore a Default State Image \nYou can restore the default state image for any of the states of an iSTAR device. \nTo Restore the Default State Image \n1. From the State Images tab, select an existing image. \n2. Right-click the image and select Restore Default. \n3. Click Save and Close to save the configuration. \nC•CURE 9000 Hardware Configuration Guide \nChapter 5 \n275 \nEFTA01226206\n", "char_count": 419}, {"efta_number": "EFTA01225932", "page_number": 275, "text_content": "State Images Tab for STAR Devices \n276 \nChapter 5 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226207\n", "char_count": 106}, {"efta_number": "EFTA01225932", "page_number": 276, "text_content": "6 \nConfiguring the IP-ACM \nThis chapter explains how to configure the IP-ACM in C•CURE 9000. \nIn this chapter \nIP-ACM Overview \n278 \nIP-ACM Offline Mode \n279 \nConfiguring the IP-ACM \n282 \niSTAR Ultra IP-ACM Editor  \n.285 \nC•CURE 9000 Hardware Configuration Guide \nChapter 6 \n277 \nEFTA01226208\n", "char_count": 293}, {"efta_number": "EFTA01225932", "page_number": 277, "text_content": "IP-ACM Overview \nIP-ACM Overview \nThe IP-ACM provides connection and management of access control for two doors. Two readers can be configured \non each IP-ACM. \nThe IP-ACM acts as its own entity if it becomes disconnected from the iSTAR. Readers will remain active, with \nlimitations. Offline access operation is buffered, and will be reported to the iSTAR Controller when communication is \nrestored (determined by available memory.) \nLimitations \n■ C•CURE 9000 only supports two readers (any combination of RM/Wiegand/BLE readers) connected to an IP-\nACM. \n■ The IP-ACM is supported on the iSTAR Ultra and the iSTAR Ultra SE in Ultra Mode. \n■ Offline mode is supported for RM readers and Wiegand readers connected to the IP-ACM. \n■ Offline mode is not supported for BLE readers connected to the IP-ACM. \n278 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226209\n", "char_count": 876}, {"efta_number": "EFTA01225932", "page_number": 278, "text_content": "IP-ACM Offline Mode \nIP-ACM Offline Mode \nOffline Mode allows a limited level of access and control if communication is interrupted between the IP-ACM and \nthe iSTAR. Offline Access stores a set of credentials in non-volatile memory on the IP-ACM. Clearances are not \ndownloaded to the IP-ACM and are not stored. IP-ACM \nOffline Mode is configured in the iSTAR Controller dialog box using the IP-ACMs tab. \nSee the following: \n■ Stored Credentials on Page 279 \n■ Door Configuration on Page 280 \nStored Credentials \nPredefined Credentials \nPredefined credentials are downloaded from the iSTAR controller in the form of raw data (Static Card Data). During \noffline, access will be granted when the predefined credentials (from the Static Card Data stored on the IP-ACM) are \npresented to the readers. \nThe following restrictions apply to stored predefined credentials: \n■ Personnel groups configured for Offline Mode must all share the same card format and facility code. \n■ Card formats supported are: \n• Wiegand 26 \n• Wiegand 37 \n• Two-parity bit style formats \n• 32-bit serial number type formats. \n■ Static records can only be deleted from the iSTAR Controller. \nCredentials Last Granted Access \nIn offline mode, the IP-ACM board will admit cards that are among the last xxx previous admitted cards in addition \nto a pre-defined personnel group. \n■ A total of 1000 credentials (not personnel) for both previous admitted credentials and credentials in the \npersonnel group. \n■ Maximum 100 personnel in the personnel group. \n■ If you set the Personnel system variable \"Maximum Cards Per Person\", then that value must be taken into \nconsideration. \nExample: \nIf you set the \"Maximum Cards Per Person\" value to 3, then only 1000 -100 x 3 = 700 is allowed in the \n\"Admit the last admitted cards\" field for configuration. This is true, even if the personnel count in the \npersonnel group selected is less than 100. \nC•CURE 9000 Hardware Configuration Guide \nChapter 6 \n279 \nEFTA01226210\n", "char_count": 1983}, {"efta_number": "EFTA01225932", "page_number": 279, "text_content": "IP-ACM Offline Mode \nDoor Configuration \nDoors must have their readers, inputs, and outputs connected to the 1P-ACM and configured as follows: \n■ Readers that are not IP-ACM readers cannot be used. \n■ Entry reader must be connected as Reader 1 on Serial Port 2. \n■ Exit reader must be connected to Wiegand Port 2. \n■ DSM (Door State Monitor) must be connected to the IP-ACM onboard Input 1. \n■ REX (Request to Exit) must be connected to the IP-ACM onboard Input 2. \n■ Door lock must be connected to the IP-ACM onboard Output 1. \nThe door operation parameters are fixed when the IP-ACM goes into Offline Mode and cannot be changed. The door \nparameters will go back to their configured settings when the IP-ACM goes back online. \nOffline fixed parameters: \n■ Shunt time:10 seconds \n■ Unlock time: 5 seconds \n■ Relock delay time: YI second \n■ Debounce time: 112 second \n■ Unlock on RTE: Enabled \n■ Shunt on RTE: Enabled \n■ DSM shunted full shunt time: Disabled \n■ Delay Relock full shunt time: Disabled \nNOTE \nThe Offline door will not provide access if the Tamper input is active. \nIP-ACM Configuration Sequence \nThe IP-ACM configuration sequence is described in Table 1 on Page 280. \nTable 1: IP-ACM Configuration Sequence \nStep \nTask \nSee... \nConnect the IP-ACM to the nehvork. \n/P-ACM Hardware Con figuration Guide \n2 \nAdd the IP-ACM to the subnet: \n!STAR Configuration UtigyUser Guide \n1. Open the STAR Configuration Utility (ICU). \n2. Click IP-ACM to discover al IP-AC Ms in the subnet. \n3. Right-click on the IP-ACM in the list and select Configure IP-ACM. \n280 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226211\n", "char_count": 1634}, {"efta_number": "EFTA01225932", "page_number": 280, "text_content": "IP-ACM Offline Mode \nTable 1: IP-ACM Configuration Sequence (continued) \nStep \nTask \nSee... \n3 \nEnsure that the STAR Controller (Ultra or Ultra SE in Ultra Mode) is configured in the \nC•CURE 9000. \nCreating an STAR Controller on Page \n124 \n4 \nAccess the STAR Controller dialog box I P-AC Ms tab: \n1. Add the IP-ACM(s) to the controller. \n2. Configure the IP-ACMs Offline Mode. \n3. Configure the readers to connect to the IP-ACM. \n4. Configure the inputs. outputs. and triggers. \nSTAR Controller IP-ACMs Tab on Page \n282\nSTAR Ultra IP-ACM Editor on Page 285 \n5 \nConfigure a door with the readers in the IP-ACM. \nSTAR Door Editor on Page 427 \nC•CURE 9000 Hardware Configuration Guide \nChapter 6 \n281 \nEFTA01226212\n", "char_count": 712}, {"efta_number": "EFTA01225932", "page_number": 281, "text_content": "Configuring the IP-ACM \nConfiguring the IP-ACM \nThe IP-ACM configuration is accessed through the iSTAR Controller dialog box IP-ACMs tab, as shown in Figure 1 \non Page 282. \nSee Table 2 on Page 283 for descriptions of the fields. \nFigural: 'STAR Controller IP-ACMs Tab \n•-••••••••o••• \n11\nr pails/ \nMkt Ofal \nr \nnor ICall I 0)1111 %PIM I .010 I *MP I YeDiersid AM I Welwyn I \n•••. Gem Al IP-AN, _; Mete AP PAO% \nSI \nI•IS \n. OSA* \nl \n. \n,\n111111111111 \nI \n \nr \niST AR Lim 1, 40110a. \nr \ncm us woods \nr \n•STM1 We 0.01310n-\nr \n6TIII Um HOKUM. \nr \nOM UM 11401541 \nr \nt t T HUM •4044.4 \nr \nsun UM HOMO. \nr \nSTMT ..qn \nr \ncum Up Oaken. \nOdiesikagINIP•ACIa• \ncots 1, \nthin•••••adailen••••• 0w \nCan f antisue ta nat.. el Sr Moro tel. I \nguanin na. 'OW Wei:skirls $ • Pranci pap. aoktated *Mn , A penca•el (watts te \n••• 'ix • le ow...n.00> rwaode WW0011/410« n IV 5)!X. wing* \nNay of sad* l•Scro fie \nMode aOlSee \n7rn\nHurls S 01010 iMP Cowin*. Cia•Mgcle \n140 Say Reed TopTlaheld milacont \nis \nTo Configure the IP-ACM \n1. From the iSTAR Ultra Controller editor, click the IP ACMs tab, as shown in Figure 1 on Page 282. \n2. Click on the Configured check box in the Index row that you want to add/edit. \n3. Click El in the Edit column of the Index row to open the iSTAR Ultra IP-ACM Editor on Page 285. The \niSTAR Ultra IP-ACM editor is used to configure the inputs, outputs, and readers (Wiegand, RM, BLE, and OSDP). \n4. Configure the Offline Mode of All IP-ACM's configured on this controller. \nSee Table 2 on Page 283 for descriptions of the fields. \n5. When the IP-ACM(s) configuration is complete, click in the Enabled check box, and click Save and Close. \n282 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226213\n", "char_count": 1722}, {"efta_number": "EFTA01225932", "page_number": 282, "text_content": "Configuring the IP-ACM \nTable 2: STAR Controller IP-ACMs Tab Definitions \nFielcUButton \nDescription \nIP-ACMs \nCreate All lP-ACMs \nClick to create the lP-ACMs. When you click Create All IP AC Ms the Configured column check boxes are \nselected. and you can click n \nin the Edit column to open the STAR Ultra IP ACM Editor to configure the \nIP ACM. \nDelete All IP-ACMs \nWhen you click Delete All IP-AC Ms. the check boxes in the Co nf ig u red column are cleared for all IP-\nAC Ms. When the configuration is save, you are prompted to confirm deletion of each IP-ACM. \nOffline Mode of All IP-ACMs \nNOTE: The selections made in the Offline Mode of All IP-AC Ms section will apply to all IP-AC Ms configured on the controller. \nIn offline mode, the IP-ACM board will admit cards that are among the last )oa previous admitted cards in addition to a pre-defined personnel group. \n- A total of 1000 credentials (not personnel) for both previous admitted credentials and credentials in the personnel group. \n- Maximum 100 personnel in the personnel group. \n- If you set the Personnel system variable 'Maximum Cards Per Person', then that value must be taken into consideration. \nExample:lf you set the \"Maximum Cards Per Person\" value to 3. then onty 1000 -100 x 3 =100 is allowed in the 'Admit the last admitted \ncards' field for configuration. This is true, even if the person nel cou nt in the personnel group selected is less than 100. \nAdmit the last admitted cards \nSelect a number from the menu that will apply to the previous cards that were admitted. \nDefautt: 0 \nValue: 0 to 1000 \nCard Format used by the members \nof the Personnel Group \nSelect a card format to be used for personnel when in office mode. Only individual card formats are \nselectable. The card format is used to determine the card data stream for each person in the personnel \ngroup. Al personnel will use the same card format. The first facility code and site code in the list will be used \nif that format has multiple values. \nAdmit\n... [truncated, 2957 chars — for the full page use /api/corpus/document/EFTA01225932/282 or ?id=EFTA01225932&page=282]", "char_count": 2957}, {"efta_number": "EFTA01225932", "page_number": 283, "text_content": "Configuring the IP-ACM \nTable 2: STAR Controller IP-ACMsTab Definitions (continued) \nField/Button \nDescription \nHigh LatencyThreshold in \nmilliseconds \nThe number of milliseconds thatwillcause a round-trip latency alarm. T his value willappty teal IP-ACM's \nconfigured for thiscontroler. \nDefault: 500 milliseconds (0.5 seconds) \nRange: 100-2000 milliseconds (0.1 to 2 seconds) \n284 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226215\n", "char_count": 450}, {"efta_number": "EFTA01225932", "page_number": 284, "text_content": "STAR Ultra IP-ACM Editor \niSTAR Ultra IP-ACM Editor \nThe iSTAR Ultra IP-ACM editor, shown in Figure 2 on Page 285, is used to configure readers, inputs and outputs. \nSee the following for more information: \n■ Accessing the iSTAR Ultra IP-ACM Editor on Page 285 \n■ iSTAR Ultra IP-ACM Inputs Tab on Page 291 \n■ iSTAR Ultra IP-ACM Outputs Tab on Page 286 \n■ iSTAR Ultra IP-ACM Wiegand Tab on Page 288 \n■ iSTAR Ultra IP-ACM RS-485 Tab on Page 290 \n■ iSTAR Ultra IP-ACM Status Tab on Page 293 \nFigure 2: iSTAR Ultra IP-ACM Editor \n145ave \nad< \nISTAA IAa tP KM, \nPanda Dial \nr VOglaterce Mode \nGeW4 I Ir.\" \nI Osixes 'Wigged I RS451 Albs \n- Bard Lecaboi \nCattuan lukr. 3\niP.agli 'limbo II\nMAC kidnxis \nceckess I \nF Use NCI. \nr \nCA sibl• one neat \nAccessing the iSTAR Ultra IP-ACM Editor \nTo Access the iSTAR Ultra IP-ACM Editor \n1. From the iSIAR Ultra Controller editor dialog box, click the IP ACMs tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 6 \n285 \nEFTA01226216\n", "char_count": 971}, {"efta_number": "EFTA01225932", "page_number": 285, "text_content": "STAR Ultra IP-ACM Editor \n2. Click on the Configured check box in the Index row that you want to add/edit. \n3. Click ri  in the Edit column of the Index row to open the iSTAR Ultra IP-ACM editor. \nTable 3: STAR Ultra Controller IP-ACM Editor General Tab Definitions \nFiskUButton \nDescription \nPartition \nThis read-only field identifies the Partition. \nMaintenance \nMode \nClick to put the IP-ACM into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nBoard Location \nController \nThis field is read-only. \nIP-ACM \nNumber \nThis field is read-only. \nMAC Address \nEnter the MAC address of the IP-ACM. \nNOTE: You will not be able to edit this field after you enter the IP address and save the configuration. To change the MAC \nAddress, you will need to delete the IP-ACM configuration and create a new one. \nIP Address \nThe IP addressof the IP-ACM if not using DHCP. \nUse DHCP \nClick the check box to use DHCP. Deselect the check box to enter an IP Address. \nDefault: DHCP isenabled. \nOffline Mode \nDisable offkne \nmode \nI Cid( the chedc box to disable offline mode on this IP-ACM. \nNOTE: This selection will override the Offline Mode of all IP-ACMs selections h the iSTAR Controls( Editor IP-ACMs tab for \nthis IP-ACM. \niSTAR Ultra P -ACM Outputs Tab \nThe Outputs tab allows you to configure the Outputs for the IP-ACM. \nTable 4 on Page 287 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Board Outputs tab. \n288 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226217\n", "char_count": 1523}, {"efta_number": "EFTA01225932", "page_number": 286, "text_content": "STAR Uttra IP-ACM Editor \nFigure 3: STAR Uttra IP-ACM Outputs Tab \nNW* \n0 6\"nrete \nSTAR lira IP ACM urn I \nramma DAIS \nr SImlenerceMccle \n(Fenn I PPS. Clan w.asN I esats I moms' sm.] \nOSS (CAMIOT EIE MIXEDFOR FIRE ALARM WERFACE) \nOno. Al Outpx. \nOman. Oat, \nCl \nMIMII \nIt \nCaliared \nF\" \nNom \n-,^nate \nQIpAIS TAR U4 IF AM utm \n0.W.12•STiR ,J1-a IF ACMPA-5 1 \nTable 4: STAR Ultra IP-ACM Outputs Tab General Tab Definitions \nField/Button \nDescription \nName \nDisplays the name for this Output board. The name is system-generated bydefautt, but you can edit this name byclicking this \nfield. \nDescription \nEnter a textual com ment about the Output board, such as its location or purpose. This text is for information only. \nPartition \nThis read-onty field identifies the Partition in which this Output board resides. \nMaintenance \nMode \nClick to put the STAR Outboard Board into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nLocation \nController \nThis read-only field identifies the iSTAR Controller to which this Output is attached. \nBoard \nThis read-onty field identifies the STAR Controller board to which this Output board is attached. \nC•CURE 9000 Hardware Configuration Guide \nChapter 6 \n287 \nEFTA01226218\n", "char_count": 1234}, {"efta_number": "EFTA01225932", "page_number": 287, "text_content": "STAR Ultra IP-ACM Editor \nTable 4: STAR Ultra IP-ACM Outputs Tab General Tab Definitions (continued) \nFieldeutton \nDescription \nBoard Index \nThis read-only field identifies the board index (which represents the SW1 address switch setting on the R/8 board) for this Output \nboard. \nOutputs \nCreate All \nOutputs \nClick to create all Outputs. The check boxes in the Configured column are set toe. \nDelete All \nOutputs \nClick to delete all Outputs. The check boxes in the Configured column are set to \nEdit column \nClick® in thiscolumn to open the STAR Output Editor to edit this Output. \nNOTE: The Configured check box must be selected to open the Output Editor. \nIndex column \nThis read-onty field identifies the position of each Output (1 - 2) on the IP-ACM board. \nConfigured \ncolumn \na indicates that the Output has been oonfigured. \nindicates that the Output has not been configured. \nNOTE: The Configured check box must be selected to open the Output Editor. \nName column \nDisplays the system-generated name for this Output. You can edit this name by clicking in the field. \nTemplate \ncolumn \nDisplays the Template used for creating this Output. If the Output isnot yet configured, you can click in thiscolumn, then click to \nselect an Output Template. If the Co nf ig u red column displays V thisfield cannot be edited. \niSTAR Ultra IP-ACM Wiegand Tab \nUse this tab to configure Wiegand readers connected to the IP-ACM board. \nTable 5 on Page 289 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Wiegand tab. \n288 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226219\n", "char_count": 1609}, {"efta_number": "EFTA01225932", "page_number": 288, "text_content": "STAR Ultra IP-ACM Editor \nFigure 4: STAR Ultra IP ACM Wiegand Tab \nlaSave as Cam \nSTAR tAra IP KM1 'Ara 1 \nParvxn. DedaA \nr giolenerco *de \nGeed I *Ss I Oats Ww9end I RS1S5 I Tenn I gay I \nPat \nOnce Al R*116111 \nDein Al Readers \nCelt \nIwkx \nCalwed \nIlene \nTadao \nF \nSTAR Paw14,AR Uha PICWI 0ba \nr \nSTAR PArkw2.51 AR Ulf. P40.11Are 1 \nTable 5: STAR Ultra IP-ACM Wiegand Tab.Definitions \nBox \nDescription \nCreate All \nReaders \nClicktocreate all the Readers. When you click Create All Readers, the Configured column check boxes are selected. and you \ncan click® in the Edit column to open the STAR Reader Editor to configure a direct =inset Wiegand Reader. \nDelete All \nReaders \nWhen you dick Delete All Readers, the check boxes in the Configured column are cleared for all Readers, and all these Readers \nare immediately de kited (any settings you have oonfigured are lost). \nEdit \ncolumn \nClick .. \nin the Edit column to open the STAR Reader Editor to configure a Reader. See STAR Reader Editor on Page 248. \nIndex \ncolumn \nThis column displays the number for each reader. This n umber is the physical port number for a Direct Connect Wiegand reader. \nConfigured \ncolumn \nClick in this column to create a reader (make it available to be edited). \nName \ncolumn \nDisplays the name for this Reader. The name is system-generated bydefault. but you can edit this name by clicking in this field. \nC•CURE 9000 Hardware Configuration Guide \nChapter 6 \n289 \nEFTA01226220\n", "char_count": 1461}, {"efta_number": "EFTA01225932", "page_number": 289, "text_content": "STAR Ultra IP-ACM Edrtor \nTable 5: STAR Ultra IP-ACM Wiegand Tab.Definrtions (continued) \nBox \nDescription \nTemplate \ncolumn \nClain this column prior to creating the Reader, then click® to select a Reader template from the fist of available Reader \ntemplates. \nThe Temp late column shows the template name chosen if you selected a Template prior to creating the Reader. \nReaders 1 \n- 2 \nSelect the dieck box in the Configured column for a Reader and dick 0 \nlocated in the Ed It column to open the iSTAR Reader \nEditor General tab toconfigure the Keypad, Triggers, Groups, Statusand State Images that are associated with a Reader. See \nSTAR Reader Editor on Page 248 for detaled instructions for configuring iSTAR Readers. \nThe Name column displays a name comprised of the Reader Type and the iSTAR Controller name. You can dick in this column to \nedit the Reader name. \niSTAR Ultra IP-ACM RS-485 Tab \nUse this tab, shown in Figure 5 on Page 290, to configure RS-485 ports connected to the iSTAR Ultra IP-ACM Board. \nTable 6 on Page 291 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM RS-485 tab. \nFigure 5: STAR Ultra IP-ACM RS-485 Tab \na \nSave ard Oast \nMn\nhexane \nIST AA Urn IP P041 Uln-1 \nPuler roan \ngeettaxece Mole \nGeneral vats I Wan Ixttara aSerS I Type I Shea I \nRS135 Pan \nX0,111 Al Pub \nDA.* Al Ports \nfee \nIles \nCOeCiPed \nNOM \nr \nMAR DO'S POIUSTAR the •40114An. I \nr \n,STAR Demo PothSTAR Ma P401 lare.1 \n290 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226221\n", "char_count": 1512}, {"efta_number": "EFTA01225932", "page_number": 290, "text_content": "STAR Ultra IP-ACM Editor \nTable 6: iSTAR Ultra IP-ACM Board RS-485 Tab Definitions \nField/Button \nDescription \nCreate Al \nPorts \nClick to create the RS-485 Ports. When you cid< Create All Ports the Configured column dieck boxes are selected, and you \ncan did< 0 \nin the Edlt column toopen the iSTAR Device Port Editor toconfigure an RS-485 Port. \nDelete Al \nPorts \nWhen you dick Delete All Porta, the check boxes in the Configured column are cleared focal Ports, and al Ports are \nimmediately deleted (any settings you have configured are lost). \nEdit column \nClick® in the Edit column toopen the iSTAR Device Port Editor toconfigure Device Ports for the IP-ACM. See iSTAR Ultra \nACM RS-485 Device Port Editor on Page 188. \nIndex column \nThiscolumn displays the number for each Device Port. \nConfigured \ncolumn \nClick in this column to aeate a Device Port (make it avalable to be edited). \nName column \nDisplays the name for this Device Port. The name is system-generated by defautt, but you can edit this name by didong in clidc In \nthis field. \nDevice Ports 1 \n- 2\nSelect the check box in the Configured column for a Device Port and click El  located in the Edit column to open the iSTAR \nDevice Port Editor General tab to configure the Readers and ACM extensions that are associated with the Device Port. See \niSTAR Reader Editor on Page 248 for detaled instructions for configuring iSTAR Device Ports. \nThe Name column displays a name comprised of the Device Port and the iSTAR Controller name. You can did< in this column to \nedit the Device Port name. \niSTAR Ultra IP-ACM Inputs Tab \nThe Ultra IP-ACM Inputs tab lets you create and configure the Inputs that are attached to this Ultra IP-ACM Board. \nYou can use an existing Input Template to create one or more of the IP-ACM Board Inputs. Click in the Template \nColumn, then click C. A list of available iSTAR Input Templates appears. Click on the Template you wish to use. \nSee Using Templates for Controller Inputs, Outputs, and Readers on Pa\n... [truncated, 2256 chars — for the full page use /api/corpus/document/EFTA01225932/290 or ?id=EFTA01225932&page=290]", "char_count": 2256}, {"efta_number": "EFTA01225932", "page_number": 291, "text_content": "STAR Uttra IP-ACM Editor \nFigure 6: STAR Uttra IP-ACM Inputs Tab \nVC STAR Ma W.ACIA - iSTAR \nINACIAl.my ultra \na Sava and Clore \nSo* ISOM** PJCM \nLalocrobca \ntsars • in. twin. lame, l Rif PO l lawn lan \nScat., Irtexa• Feta \nCreate Al Maratt oods.Misysb \nEde\n*Ara, \nCalmed \nNam \nTravails \nImage \nTerper4TM Uba IP-A00 \nCcartneman I al \nQ \nConnataecafal4TAR It. \nPot Apo Mem Rata 1 \nPod Pave Mon SOS IrS7A \nPot Pow Mr $110.• 2 \nI5 \nPat Pow Alm SOY 24TA \ntack Pas Mr Sim 1 \nlack Am. Are Amt \nLack Poor Alm Stow 14/ \nlock Poser Nis Sae 24i \nGerent Ramo Pads \nOrte AIInputs \nDelete All Imparts \nEd. \nMa \nCoritand \nNoe \nE \n \niST AR Intl.ST AA Ulm • fronana, \nQ \n67AR V4124TAR lara F./CIA1,n. \nEl \n cos IntISTAR taro INACM \nutra \no \niST AR loANSTAR Ulm 14CM *vita \nTaws \nTable 7: STAR Ultra IP-ACM Board Inputs Tab Definitions \nField/Button \nDescription \nSpecial Purpose Inputs \nTamper \nThe Tamper input activates when the controller cabinet is opened or removed from its mounting surface. \nNOTE: For UL applications. this field must be enabled. \nSelect the check box in the Configured column and click [—I boated in the Edit column to open the STAR Input Editor \nGeneral tab to configure the Tamper input. From the Input Editor you can configure the Options, Triggers, Groups, Status and \nState Images that are associated with the Tamper Input. \nThe Template column shows the template name chosen if you selected a Template prior to creating the Input. \nCommunication \nFail \nA bgical unsupervised input that reflects the state of the communication between the GC M board and Processor-A on this IP-\nACM board. \n292 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226223\n", "char_count": 1675}, {"efta_number": "EFTA01225932", "page_number": 292, "text_content": "STAR Uttra IP-ACM Editor \nTable 7: STAR Ultra IP-ACM Board Inputs Tab Definitions (continued) \nField/Button \nDescription \nPort Power \nAlarm Status 1 \nPort Power \nAlarm Status 2 \nPower indicator input for each RM /Weigand port. \nLock Power \nAlarm Status 1 \nLock Power \nAlarm Status 2 \nIP-ACM can provide power for the locks directty from the 2 Output oonnectors (Lock Power 1 8,2). There are automatic over-\ncurrent shut-off switcheson each Lock Power. The Lock Power Alarm Status inputsgo Active when the over-current shut-off \nswitches are active (i.e., when Lock Power has been shutoff). \nGeneral Purpose Inputs \nInputs 1 \nthrough 4 \nThese standard general purpose supervised inputs are available on STAR Uttra IP-ACM boards. \niSTAR Ultra IP-ACM Status Tab \nThe Status tab, shown in Figure 7 on Page 294, provides a read-only listing of information about the operational \nstatus of the selected iSTAR Ultra 1P-ACM Board. \nC•CURE 9000 Hardware Configuration Guide \nChapter 6 \n293 \nEFTA01226224\n", "char_count": 995}, {"efta_number": "EFTA01225932", "page_number": 293, "text_content": "STAR Ultra IP-ACM Editor \nFigure 7: STAR Ultra IP-ACM Status Tab \na1J =1 \nas...dame \ntry ISTAct IN IP•KMI ltraSE 1 \nr Hata \nMUM \nGino., I bat I Cucao I Wised I R.5415 I Tees Stew I \nCaretflai \nAnne 'ama I\nMenne \nMO Lawry la \nIFS. \nTable 8 on Page 294 provides definitions of the fields and buttons on the iSTAR Ultra IP-ACM Board Status tab. \nTable 8: STAR Ultra IP-ACM Board Status Tab Definitions \nField/Button \nI Description \nCommunication Status \nUnknown. Offline. or Online. \nFirmware Version \nProcessor firmware. such as 00.00.36.00008 \nIP Address \nThe IP-ACM IP address. \nHigh LatencyAlarm \nPossible status values are True or False. \n294 \nChapter 6 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226225\n", "char_count": 712}, {"efta_number": "EFTA01225932", "page_number": 294, "text_content": "7 \nConfiguring Advanced Processing Controllers (apC) \nThis chapter explains how to configure the apC, apC/8X, and apC/L software components to work with C•CURE \n9000. \nIn this chapter \napC Panel Overview \n296 \napC Controller Configuration Summary \n308 \napC Comm Port Editor \n310 \napC Controller Editor \n318 \napC Input Editor \n332 \napC Output Editor \n336 \napC Reader Editor \n340 \napC Add-on Board Editor \n347 \napC Add-On Board Star Coupler Tab \n354 \napC Input Board Editor (132 and 18) \n357 \napC Star Coupler Board Editor \n365 \nTriggers Tab for apC Devices  \n369 \nMini Star Coupler Board Editor \n373 \nWiegand Proximity Star Coupler Editor \n376 \nC•CURE 9000 Hardware Configuration Guide \nChapter? \n295 \nEFTA01226226\n", "char_count": 714}, {"efta_number": "EFTA01225932", "page_number": 295, "text_content": "apC Pa ne i Overview \napC Panel Overview \nThe advanced processing Controller (apC) panel is an intelligent field device that performs basic access control \ntasks. The apC, apC/8X, and apC/L are access control field panels that coordinate communication between the \nC•CURE 9000 server and the system security hardware, such as card readers. \nThe apC/L is a smaller version of the apC, making it ideal for parking garages and small office buildings. MI \napC/8Xs and some apC/Ls provide Flash ROM support, which lets you download firmware from the server to the \npanel. Up to three versions of firmware are available for download. See the Monitoring Station User's Guide for \ninformation about downloading firmware. \nEach apC, apC/8X, or apC/L in the system supports Wiegand, proximity, magnetic stripe, and RFID card \ntechnologies. The apC (apC/8X) configuration supports eight card readers wired in a daisy-chain arrangement. The \napC/L configuration supports two card readers. \nNOTE \nThe apC and apC/L have not been evaluated by UL. \nSee the following sections for more information: \n■ Features of apC Panels on Page 296 \n■ Inputs and Mann Device States on Page 299 \n■ Outputs and Readers on Page 299 \n■ Optional Boards on Page 300 \n■ apC Time Zones on Page 300 \n■ Changing the Time Zone of an apC Controller on Page 303 \n■ apC Time Zone Reports on Page 303 \n■ apC Firmware Update on Page 306 \n■ apC Controller Configuration Summary on Page 308 \nFeatures of apC Panels \nSeveral different types of add-on module expansion boards can be used for additional inputs and outputs.The apC \nfirmware offers software-controlled features such as timed activation/deactivation commands, 32-bit card numbers, \nelevator access and anti-passback control. An apC panel can use multiple card technologies, site codes, and \ncompany codes. The apCs full-year real time calendar/clock allows activation and deactivation of cards on \nspecified days. The apC panels can be connected via serial RS-232/485 or networked ter\n... [truncated, 2769 chars — for the full page use /api/corpus/document/EFTA01225932/295 or ?id=EFTA01225932&page=295]", "char_count": 2769}, {"efta_number": "EFTA01225932", "page_number": 296, "text_content": "apC Pa nelOve rview \nThere are three Star Coupler expansion boards that can be used with the apC panel to add inputs, outputs and \nreaders : \n■ Star Coupler - 8 RM readers, 8 relay outputs, 8 unsupervised inputs (see apC Add-On Board Star Coupler Tab \non Page 354 for more information) \n■ Mini-Star Coupler - 8 RM Readers (this is the same board as Star Coupler but inputs and outputs are not \npopulated) \n■ WPSC - Wiegand Prox Star Coupler includes 2 boards: \n• Lower board - 4 Wiegand signaling readers and 4 supervised inputs \n• Upper board - 4 Wiegand signaling readers and 4 supervised inputs (the upper board plugs into lower \nboard) \nA Star Coupler Reader is an RM reader connected to a Star Coupler. The Mini Star Coupler Reader is an RM reader \nconnected to the Mini Star Coupler and it differs from the Star Coupler only due to its having no inputs or outputs. \nThe readers used by these Star Coupler expansion boards are RM or Wiegand signaling readers that are connected to \na Star Coupler. \nTable 77: apC Inputs, Outputsand ReadersAvallable \nBoard \nInputs \nOutputs \nReaders \nTamper Input \n1 \nPower Failure Input \nI \nSupervised Inputs \n8 \nOutputs \n8 \nReaders \n8 Iota: \nSupervised Reader Inputs \n16 tutu: \nReader Outputs \n16 Iota. \nAdd-On Boards \n132 Supervised Input Board \n32 \nIlil Supervised Input Board \n6 \nR48 Output Board \nR8 Output Board \nStar Coupler Readers \n8 Iota: \nStar Coupler Reader Supervised Inputs \n16 tutu: \nStar Coupler Reader Outputs \n16 Iota. \nStar Coupler Unsupervised Inputs \n8 \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n297 \nEFTA01226228\n", "char_count": 1584}, {"efta_number": "EFTA01225932", "page_number": 297, "text_content": "apC Panel Overview \nTable 77: apC Inputs. Outputs and ReadersAvailable (continued) \nBoard \nInputs \nOutputs \nReaders \nStar Coupler Outputs \n8 \nStar Coupler - Ministar Readers \n8 total \nStar Coupler - Ministar - Reader Supervised Inputs \n16 total \nStar Coupler - Ministar - Reader Outputs \n16 total \nWiegand Proximity Star Coupler Readers \n[Upper and Lower Boards] \n8 total \nWiegand Proximity Star Coupler Reader Supervised Inputs [Upper and Lower Boards] \n8 \napC/L Panel \nA basic apC/ L panel has two readers and two relay outputs. An apC/L is expandable up to 36 inputs and 38 \noutputs using RM-4s and bus modules. Depending on the amount of available memory, an apC/L panel can hold \nup to 40,000 cards in its database. apC/L panels with Flash EPROMS installed can have firmware upgrades \ndownloaded from the host system. \nNOTE \nThe apC/L has not been evaluated by UL. \nTable 78: apC/L Standard Inputs. Outputs and ReadersAvailable \nBoard \nInputs \nOutputs \nReaders \nTamper Input \n1 \nPower Failure Input \nOutputs \n2 \nReaders \n2 \nSupervised Reader Inputs \n4 \nReader Outputs \n4 \nAdd-On Boards \n18 Supervised Input Board \n32 \nR8 Output Board \n32 \napC/8X Panel \nA basic apC/8X panel has eight supervised inputs, eight relay outputs and one reader port, capable of handling a \nmaximum of eight readers, which are wired in a multi-drop configuration. Expansion boards can add reader ports, \n298 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226229\n", "char_count": 1456}, {"efta_number": "EFTA01225932", "page_number": 298, "text_content": "apC PanelOverview \nsupervised input and additional outputs. Depending on available memory, an apC/8X panel can hold up to 160,000 \ncards in its database. apC/8X panels with Flash EPROMS installed can have firmware upgrades downloaded from \nthe host system. See Table 77 on Page 297 for a listing of the apC/8X panel's inputs, outputs and readers. Total \nindicates that this is the total number of inputs, outputs or readers for the apC panel. \nInputs and Alarm Device States \nAn input is an object that associates an alarm device with an input on the panel or on an input board. There are two \nkinds of inputs: supervised and unsupervised. All alarm devices can be in one of two states: active or inactive. An \ninput reports the state of the alarm device. \nA supervised input reports on the status of the wiring between the panel and the alarm device when changes in \ncircuit resistance are detected. If wiring is cut, the system reports an open circuit. If someone attempts to create a \njumper across the wiring (to prevent the device from reporting), the system reports a shorted circuit. Supervised \ninputs can report a total of five conditions to the apC: Short, Open Loop, Line Fault, Inactive or Active. The main \nboard on the apC has eight supervised inputs. \nAn unsupervised input does not monitor the wiring. Unsupervised inputs can report two conditions to the panel: \nActive or Inactive. With the star couplers, the apC has eight unsupervised inputs available. See To Configure apC \nController Inputs on Page 322 for more information. \nNOTE \nUnsupervised inputs have not been evaluated by UL. \nSupervised inputs can report five states: \n■ Short \n■ Open Loop \n■ Normal \n■ Alert \n■ Line Fault \nOutputs and Readers \nOutputs \nAn output is an object that associates an alarm device with an output on the panel board or add-on module. The \noutput turns alarm devices, such as closed circuit TV or alarm dialers, on or off. See apC Controller Outputs Tab on \nPage 323 for more information. \nReade\n... [truncated, 2399 chars — for the full page use /api/corpus/document/EFTA01225932/298 or ?id=EFTA01225932&page=298]", "char_count": 2399}, {"efta_number": "EFTA01225932", "page_number": 299, "text_content": "apC Panel OV01VI0W \nOptional Boards \napCs and apC/8X panels support these optional (add-on) boards and controller: \n■ 8 apC 1/8 - input modules and 1 apC 1/32 input board, and \n■ 8 apC R/8 - output modules and 2 apC R/48 output boards, and \n■ 1 Standard Star Coupler, or \n■ 1 Mini Star Coupler, or \n■ 1 Wiegand Proximity Star Coupler \nStar couplers enable you to wire the apC panel's 8 readers in a star, daisy-chain, or combination configuration. Star \ncouplers also provide unsupervised inputs and additional outputs and readers for the apC and apC/8X. \nNOTE \nNOTE \napC/L controllers and Mini Star Couplers have not been evaluated by UL. \nThe apC/L supports two types of optional boards: four 1/8 - input modules and four R/8 - output \nmodules. \nSee apC Controller Add-On Board Tab on Page 324 for more information. \nNOTE \nBefore you configure apC panels, the apC Hardware Interface must be started using the Server \nManagement application - Server Components tab. Right-click the apC Hardware Interface and click \nStart Server Component \napC Time Zones \nYou can specify the Time Zone for an apC panel, so that the apC panel can support panel-based operations using \nthe local date/time, and the display of the local date/time at door readers, in controller status screens, in Journal \nMessages, and in Reports. \nExample: \nIf you specify that an apC panel is in the Pacific Time Zone (GMT- 08:00), and the C•CURE 9000 server is in the \nEastern Time Zone (GMT- 05:00), a timed-based action that occurs at the apC panel, such as unlocking a Door, \nhappens at local time (Pacific Time Zone) for the apC panel. \nExample: \nIf you specify that an apC panel is in the Pacific Time Zone (GMT- 08:00), and the C•CURE 9000 server is in the \nEastern Time Zone (GMT- 05:00), a server-based Journal message shows the server date/time (EST), while a \npanel-based Journal Message shows the panel date/time (PST) as highlighted in Figure 91 on Page 300. \n*nag* Type \nFigure 91: Journal Message Showing Local Date/T\n... [truncated, 2258 chars — for the full page use /api/corpus/document/EFTA01225932/299 or ?id=EFTA01225932&page=299]", "char_count": 2258}, {"efta_number": "EFTA01225932", "page_number": 300, "text_content": "apC Panel Overview \nExample: \nIf you specify that an apC panel is in the Pacific Time Zone (GMT- 08:00), and the C•CURE 9000 server is in the \nEastern Time Zone (GMT- 05:00), a Credential with an Expiration Date set as today at 5:00 PM will expire at 5:00 \nPM Eastern time, rather than Pacific Time, because the expiration occurs at the server, which is in the Eastern \nTime Zone. \nThe Time Zone setting is configured on the apC controller General tab by selecting a Time Zone from the Time Zone \nfield. See apC Controller General Tab on Page 319 for more information. \nYou can change the value of the apC controller Time Zone field only when the apC Controller is not enabled \n(Enabled field is blank O). See Changing the Time Zone of an apC Controller on Page 303 for more information. \napC Time Zones and Schedules \nSchedules in C•CURE 9000 are not configured directly with any Time Zone. They are dynamically associated with a \nlocal Time Zone when they are used in the C•CURE 9000 Server or are downloaded to a controller. That means that \nthe same schedule can be activated at different times if it is used in different Time Zones. \nThis is flexible, but also potentially complicated if you have controllers in different Time Zones. \nExample: \nYou create a Schedule to manage Clearances for your night shift. When downloaded to an apC in another Time \nZone, the Schedule works as expected. However, if you apply the Schedule to a C•CURE 9000 Server-based \nEvent (\"Lock all Doors\" using the All Doors Group) that affects the Pacific Time Zone apC, the Event's actions \nwould be triggered in the Server's Time Zone, rather than the Time Zone where the apC resides, perhaps causing \nDoors to be locked at the wrong time. \nHowever, if you create separate Schedules and name them to make it clear which Time Zone (or which controller) \nthey are intended to be used with, you can avoid problems with Time Zone differences. \nExample: \nYou create a Schedule to assign to Door and Elevator Clearances on\n... [truncated, 3193 chars — for the full page use /api/corpus/document/EFTA01225932/300 or ?id=EFTA01225932&page=300]", "char_count": 3193}, {"efta_number": "EFTA01225932", "page_number": 301, "text_content": "apC Pa ne i Overview \nSee Defining a Trigger for an apC Device on Page 370 for more information about specifying a Time Zone for an \napC Trigger. \nUsing apC Panel Time Zones with Events \nYou can add a Time Zone to an Event if you intend to activate a timed Action with that Event. The Event General \ntab includes a Time Zone field that you can use to determine when a Schedule you attach to the Event is Activated. \nSee the Events chapter in the C• CURE 9000 Software Configuration Guide. \nTime Zone for apC Panel Events \nFor timed Actions defined in an Event (the Event is armed and/or activated by a Schedule) that the apC driver \ndownloads to an apC panel to execute , the Time Zone for the Action is automatically set to the Time Zone of the \napC Panel. You cannot change the Time Zone setting to a different Time Zone. \nExample: \nThe C•CURE 9000 server is in the Eastern Time Zone (GMT - 05:00). The apC Panel is in the Pacific Time Zone \n(GMT - 08:00). If the Event is activated by a Schedule at 10:00 AM, it will be activated at 10:00 AM Pacific Time \n(the apC panel's Time Zone), not 10:00 AM Eastern Time. \nFor an apC time-based action defined in a Event, if a Time Zone is specified in the Event, the apC driver only \ndownloads the action to apC controllers with the same time zone as the Event. \nIf the apC panel is online when the Event is activated by the Schedule, the apC driver sends the timed Action \ncommand to the apC panel. \nIf the apC Panel is offline when the Event is activated by the Schedule, the apC panel performs the timed Action. \nHowever, the apC does not have the capability, after communication is re-established, to display activation and \ndeactivation messages for an Event that occurred while the apC was offline. \nTime Zone for apC Host Events \nFor a host Event (an Event that is initiated at the C•CURE 9000 server, without timed Actions downloaded to the \napC Panel), you can specify any Time Zone for the Schedule on the Event General tab. The Time Zone does no\n... [truncated, 3083 chars — for the full page use /api/corpus/document/EFTA01225932/301 or ?id=EFTA01225932&page=301]", "char_count": 3083}, {"efta_number": "EFTA01225932", "page_number": 302, "text_content": "apC Panel Overview \nChanging the Time Zone of an apC Controller \nYou can change the value of the apC controller Time Zone field only when the apC Controller is not enabled \n(Enabled field is blank O). To change the Time Zone, you must edit the controller, clear the Enabled field, save the \ncontroller, then re-open it to change the Time Zone. \nIf you change the Time Zone of the apC controller, the Time Zone settings of all child objects of that apC controller \nare changed as well. A warning message appears if you change the Time Zone and any Events have controller-based \nactions on this apC controller and the Event is configured to use a different Time Zone than this apC controller. \nTo Change the Time Zone of an apC Controller \n1. From the Hardware pane, select the apC controller you wish to change. Right-click and select Edit \n2. Clear the Enabled field (change \nto O). \n3. Click Save and Close to save the change. \n4. From the Hardware pane, select the apC controller again. Right-click and select Edit \n5. When the apC controller editor opens, the Time Zone field can be changed. \n6. Click Save and Close to save the change. \napC Time Zone Reports \nC•CURE 9000 provides several pre-defined Reports (and Queries) that can help you find Time Zone mismatches -\nwhere the C•CURE 9000 server and the apC panel are in different Time Zones, such that a host Event will be unable \nto activate an object on an apC that is offline.) for Events associated with apC panels in different Time Zones than \nthe C•CURE 9000 server. \nTable 79: apC Time Zone Reports/Queries \nReport \nQuery \nSWH70 - apC Input Groups with Time Zones \nSWH71 -apC Door Groups with Time Zones \nSWH 72 - apC Time Zone Mismatch Actions \nSWHrep72 - apC Tine Zone Mismatch Actions \nSWH 73 - apC Online Only Actions \nSWHrep73 - apC Online Only Actions \nSWH 74 - Actions with Time Zone Mismatch \nSWHrep74 - Actions with Tine Zone Mismatch Query \nSee the Reports chapter of the C•CURE 9000 Data Views Guide for more information abou\n... [truncated, 2425 chars — for the full page use /api/corpus/document/EFTA01225932/302 or ?id=EFTA01225932&page=302]", "char_count": 2425}, {"efta_number": "EFTA01225932", "page_number": 303, "text_content": "apC Panel Overview \napC Controller Actions Report \nYou can create a custom Report that lists apC Controller objects and all the actions triggered by the controller and its \nchild objects (like doors, readers and inputs), as well as action items that should be loaded into the apC because they \nare configured in Event objects. \nIf a Report Query is not specified, the report lists all the apC Controllers and all the actions, noting each action is \nOnline Only - performed only if the apC panel is Online - if the custom fields in the Action Item class are selected. \nSpecifying a Report Query allows you to select any apC Controller field and any Action Item field, including these \ncustom fields: \n■ Online Only - whether the action can occur only on an online apC) \n■ Online Only Reason - the reason that an action can only occur on an online apC. Possible values are: \n• Time Zone Mismatch - The Time Zone of the timed action is different from the Time Zone of the controller. \n• No Firmware Support - The action is not supported by the controller, so it must be executed on the host. \n• Cross Panel Action - The action is activated by one controller and modifies an object on another controller. \n• Invalid Configuration - The action cannot be activated (for example, a change in Comm Fail status should \ncause an Event to activate an Output on the same controller, but the Comm Fail prevents the Event from \ncommunicating with the Output.) \nTo Create an apC Controller Actions Report \n1. Create a new Report - From the Data Views pane, select Report from the drop-down list of objects, then click \nNew. \n2. Select apC Controller as the Report type field. \n3. Select apC Controller Actions as the Sub type field. \n4. Click on apC Controller in the Class Selector. \n5. In in the Field Selector, select the fields for the apC Controller class that you want to display in the Report. \n6. Click on Action Item in the Class Selector. \n7. In the Fields Selector, select any fields you want in the repo\n... [truncated, 2883 chars — for the full page use /api/corpus/document/EFTA01225932/303 or ?id=EFTA01225932&page=303]", "char_count": 2883}, {"efta_number": "EFTA01225932", "page_number": 304, "text_content": "apC Pa ne i Overview \n■ Time Zone Mismatch - set to TRUE if the Time Zone of the Action Item is not equal to the Time Zone of the \nSource object and/or not equal to the Time Zone of the Target. \nTo Create an Action Item Time Zones Report \n1. Create a new Report - From the Data Views pane, select Report from the drop-down list of objects, then click \nNew. \n2. Select Action Items as the Report type field. \n3. Select Action Item Time Zone in the Sub type field. \n4. Click on apC Controller in the Class Selector. \n5. In the Field Selector, select the fields for the apC Controller class that you want to display in the Report. \n6. Click on Action Item Time Zone in the Class Selector. \n7. In the Fields Selector, select any fields you want in the report (including the custom fields Online Only and \nOnline Only Reason) for the Action Item Time Zone class. \n8. Optionally, you can click to select a Report Query as the basis of the report. SWHrep74 is available in the Report \nQuery drop-down list for this purpose. \n9. Click Save and Close to save the Report. \n10. The Report is added to the Reports Dynamic View. You can double-click the Report to run it. \napC Door Group and Input Group Time Zones Report \nYou can create a custom Report that lists either apC Door Groups or apC Input Groups and their Time Zones by \nediting the following pre-defined Reports, creating a copy, adding a Query, or customizing the Report Layout: \n■ SWH70 - apC Input Groups with Time Zones \n■ SWH71 - apC Door Groups with Time Zones \nBoth of these pre-defined Reports: \n■ Start with a Group Report \n■ Use the Group Member field Time Zone Name to output the Time Zone of the objects in the Report. \nTo Create an apC Door Group or apC Input Group with Time Zones Report \n1. From the Data Views pane, select Report from the drop-down list of objects, then click gat \n2. Select either: \n■ SWH70 - apC Input Groups with Time Zones \n■ SWH71 - apC Door Groups with Time Zones \n3. Right-click and choose Edit. The Report edi\n... [truncated, 2360 chars — for the full page use /api/corpus/document/EFTA01225932/304 or ?id=EFTA01225932&page=304]", "char_count": 2360}, {"efta_number": "EFTA01225932", "page_number": 305, "text_content": "apC PanelOverview \n7. Select Prompt for Query ❑p if you want to display a Query Parameter Prompt when the report is run. \n8. Click the drop-down list for the Layout style if you want to change the Report layout. \n9. Change the fields in the Class selector and the Field selector if you want to change the fields displayed on the \nReport. \n10. Click the Layout Design tab if you want to manually change the Report design. \n11. Click the Layout Preview tab to see a preview of how the Report will look. \n12. Click Save and Close to save the Report. \n13. The Report is added to the Reports Dynamic View. You can double-click the Report to run it. \napC Firmware Update \nYou can update the apC, apC/8X or apC/L firmware on apC panels from either the Admin Client or the Monitoring \nStation client. You can initiate a firmware update by right-clicking on the apC controller: \n■ In the Hardware Tree. \n■ In a Dynamic View in the Administration Client. \n■ In the Status List - Controller in the Monitoring Station. \nNOTE \nThe UL approved firmware to be used for the apC/8x panel is x.7ZF \nTo Update Firmware on an apC \n1. Right-click on the apC that you want to update. \n2. Select Update Firmware from the context menu that appears (see Figure 92 on Page 306). \nFigure 92: apC Context Menu \nNOTE \nThe Update Firmware selection does not appear if the apC is not Enabled or is off-line. \n3. The apC Firmware Download dialog box opens (see Figure 93 on Page 307). \n308 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226237\n", "char_count": 1525}, {"efta_number": "EFTA01225932", "page_number": 306, "text_content": "apC Panel Overview \nFigure 93: apC Firmware Download Dialog Box \nInwrivoradt Download \nGnaw Nee apc_l \nOsieriYotan B TV \nyalthitortitiri: \n4. Select the firmware version that you want to download from the list in the dialog box. \n5. Click Start firmware download. A progress bar shows you the when the download is completed. \n6. When the download has completed, click Close to close this dialog box. \nTIP \nDo not attempt to download firmware to more than one apC panel on a chain at one time, and do \nnot attempt to download firmware if that chain is busy doing a personnel download. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n307 \nEFTA01226238\n", "char_count": 656}, {"efta_number": "EFTA01225932", "page_number": 307, "text_content": "apC Controller Configuration Summary \napC Controller Configuration Summary \nConfiguring an apC is a multiple task process because of the number of options available on the apC. \nThe following summary gives you an outline of the configuration process, with links to topics that provide the \ndetails. \nTable 80: apC Configuration Summary \nConfiguration \nSee... \n1. Create and configure an apC Comm Port. \napC Comm Port Editor on Page \n310 \n2. Create an apC Controller. \nTo Create an apC Controller on \nPage 318 \n3. Use the apC Controller General Tab to configure the Connection Type, Comm Port, RM LCD Message \nset, apC Type, Time Zone, and apC Address. \napC Controller General Tab on \nPage 319 \n4. Use the apC Controller Communications Tab toconfigurecommunicationsparametersfor the apC. \napC Controller Communications \nTab on Page 321 \n5. Use the apC Controller Inputs Tab to configure Panel Status Inputs and Supervised Inputs. \napC Controller Inputs Tab on \nPage 322 \nEdit each apC Input on the apC Input Editor Triggers tab, and State Images tab, and view the Input's \nstatuson the Status tab. \napC Input Editor on Page 332 \n6. Use the apC Controller Outputs Tab to configure apC Outputs. \napC Controller Outputs Tab on \nPage 323 \nEdit each apC Output on the apC Output General Tab and State Images tab. and view the Inputs \ngroups and statuson the Groups tab and Status tab. \napC Output General Tab on Page \n336 \n7. Use the apC Controller Readers Tab to configure apC Readersand options. \napC Controller Readers Tab on \nPage 323 \nEdit each apC Reader on the apC Reader General Tab,11O tab, Keypad tab, Triggers tab, and State \nImages tab, and view the Inputs statuson the Status tab. \napC Reader General Tab on Page \n340 \n8. Use the apC Controller Add-On Board Tab to create and configure an apC add-on board. \napC Controller Add-On Board Tab \non Page 324 \nEdit each apC Add-on Board from the apC Add-on Board Editor, configuring Input Boards. Output \nboards, and Star Couplers. \napC Add-on Board\n... [truncated, 2633 chars — for the full page use /api/corpus/document/EFTA01225932/307 or ?id=EFTA01225932&page=307]", "char_count": 2633}, {"efta_number": "EFTA01225932", "page_number": 308, "text_content": "apC Controller Configuration Summary \napC Configuration Summary (continued) \nConfiguration \nSee... \nIf you created a WPSC, use the Wiegand Proximity Star Coupler Editor tocreate Readers and \nInputs. \nWieland Proximity Star Coupler \nEditor on Page 376 \n9. Use the apC Controller Triggers Tab to set up triggers for Actions based on apC controller property \nstates. \napC Controller Triggers Tab on \nPage 326 \n10. Use the apC Controller Holiday Groups Tab to add Holiday Lists to the apC. \napC Controller Holiday Groups \nTab on Page 327 \n11. You \nController Status from the \nController Status Tab. \napC Controller Status Tab on \nPage 325 \ncan view \napC \n12. You can change the state images that appear in the Monitoring Station to represent this controller on \nthe apC Controller State Images Tab. \napC Controller State Images Tab \non Page 330 \n13. You can view the apC Controller groups to which this apC belongs on the Groups Tab for Hardware \nDeviceson. \nGroups Tab for Hardware Devices \non Page 28 \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n309 \nEFTA01226240\n", "char_count": 1071}, {"efta_number": "EFTA01225932", "page_number": 309, "text_content": "apC Comm Port Editor \napC Comm Port Editor \nYou need to create and configure an apC Comm Port object for your apC to establish communications with C*CURE \n9000. \nAn apC panel can communicate with serial port connections, using RS-232 connections to an RS-485 converter, or \nvia an Ethernet-connected network. \nFor general instructions about the Hardware pane see Using the Hardware Pane on Page 20. \nTo Configure an apC Comm Port \n1. To configure an apC Comm Port, open the Hardware Pane,select the Hardware Folder in which you want the \napC Comm Port to reside, and right-click to display the Hardware Folder context menu. Click apC Comm Port \nthen click New. \nFigure 94: Creating an apC Comm Port \nHa in Warr \n• amine \n12 Dalai Leta, \nrba \niff ISC Can Pat; \nAndo LCD Mosso Sat \nO [cow. Nano PatinrcDaltd \nO Pathan 1 (PeesnPaaisa 1) \nPallxn 2 retlicetPealon 2) \n1:2 Sollwage Novel paikoDei. \nSanwa* Nou.IA \nCJ Soihrzn Howe 2 PesibT4 \n• 0 \nUnestwed \n6TAR Oust* \n• \nIX Cotrol,* \n• \n40C Controle• \nWAS Peaty \nCOM Hebb \n• )FTWA \nThe apC Comm Port editor appears (see Figure 95 on Page 311). See Table 81 on Page 313 for definitions of the \nfields on the Comm Port editor General Tab \n310 \nChapter? \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226241\n", "char_count": 1251}, {"efta_number": "EFTA01225932", "page_number": 310, "text_content": "apC Comm Port Editor \nFigure 95: apC Comm Port Editor \nYou may also choose New Template. For further information about creating Templates, see Creating a Template \non Page 34. \n2. Enter a unique Host Communications Port Name (required). \n3. Optionally, enter a textual description of the apC Comm Port in the Description field. \n4. Select the Enabled check box if you want the Comm Port online after you have completed the configuration \nprocedure. \n5. Select the Communications Type. \n• For an apC Controller that uses a network communications path, click Network Port. See Configuring an apC \nComm Port Network Connection on Page 312. \n• For an apC that uses a serial connection to the C•CURE 9000 server, click Serial Port. See Configuring an apC \nComm Port Serial Port on Page 312 \n• For an apC that uses a redirected serial connection to the C•CURE 9000 server, click Redirect Serial Port. See \nConfiguring an apC Comm Port Redirect Serial Port on Page 313. \n6. You can set a Port Timeout Delay Time in tenths of a second units by typing it within the entry field or by using \nthe selection arrows. The range is 0 through 99; the default entry is 0. \n7. When you have completed configuring the apC Comm Port General tab, you can click Save and Close to save \nyour changes, or you can click the Triggers tab (see apC Comm Port Triggers Tab on Page 315) to continue \nconfiguring the apC Comm port. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n311 \nEFTA01226242\n", "char_count": 1473}, {"efta_number": "EFTA01225932", "page_number": 311, "text_content": "apC Comm Port Editor \nConfiguring an apC Comm Port Network Connection \nTo Configure an apC Comm Port Network Connection \n1. Type a unique IP Address in the IP Address field. This must be the IP Address of the terminal server being used \nto communicate with the C•CURE 9000 system. \n2. Select a TCP Port, the address of the node from which the apC Host TCP Port communicates with the C•CURE \n9000 system. The values range from 0 through 9999. The default entry is 3001. \n3. Select a Re-connection Retry Period in tenths of a second units by typing it within the entry field or by using the \nselection arrows. The values range from 0 through 99. The default entry is 30 (3 seconds). \nConfiguring an apC Comm Port Serial Port \nTo Configure an apC Comm Port Serial Port \n1. When you choose to configure a Serial Port, select the Communications Type Serial Port from the drop-down \nlist. The Name field will reflect the port number that you select. The range is COM1 through COM256. \n2. As in the Network Comm Port, you can set a Port Timeout Delay Time in tenths of a second. The range is 0 \nthrough 99, the default entry is 0. \nFigure 96: apC Comm Port Editor, Serial Port options \nco \nlin \nI \n12844414b4,\nr E441944 \nPartike. Dthal \nF Hertenar<e Mcde \nGreet I w4944 Green I 944.4 19eo twos I \nCowinacny tn. \ne\" let\n Poe \n• Ser4Pat\n• Reittect Serial Pori \nPort Semro \nPon Ticneo.t Delay Time (1)104•4) \nCaren Pon \nIP \na \n312 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226243\n", "char_count": 1488}, {"efta_number": "EFTA01225932", "page_number": 312, "text_content": "apC Comm Port Editor \nConfiguring an apC Comm Port Redirect Serial Port \nTo Configure a Redirect Serial Port \n1. When you choose to configure a Redirect Serial Port, select the Communications Type Redirect Serial Port \nbutton. In the Port Settings box, select a corn port from the drop-down list. The Name field will reflect the port \nnumber that you select. The range is COM1 through COM256. \n2. As in the Network Comm Port, you can set a Port Timeout Delay Time in tenths of a second. The range is 0 \nthrough 99, the default entry is 0. \nFigure 97: apC Comm Port Editor, Redirect Serial Port Options \nuwi\nasicooloon \nr &ebb! \nPerth:. Nall \nr tfornerarce lkdo \nGalen! I Times I Goss I Stsius I Stzte mom I \nCarmarcaer. Tn. \nr Network Pot \nSae/ Port \na Rent Sergi Poi \nArt Searto \nA \nPat Tom. new Tone (110sec): \nCaren Part \nae-ccenKtirm Pay PericrginOitC) \nIr \nThe Fields on the apC Comm Port General tab are described in Table 81 on Page 313. \nTable 81: apC Comm Port Field Definitions \nField \nDescription \nName \nEnter a unique name up to SO characters long for the controller. If you enter the name of an existing object, the system returns an \nerror message indicating there is a conflict. \nDescription \nEnter a textual oom ment about the controller, such as its location or purpose. This text is for information only. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n313 \nEFTA01226244\n", "char_count": 1395}, {"efta_number": "EFTA01225932", "page_number": 313, "text_content": "apC Comm Port Editor \napC Comm Port Fall Definitions (continued) \nField \nDescription \nEnabled \nThis setting determineswhether or not the apC Comm Port is able to provide communication between the apC Controller and the \nC•CURE 9000 Server. Select Enabled to set the Comm Port online. To take the Comm Port offline, you can clear the Enabled \nselection. \nNOTE: If the apC Comm Port iscurrentty in use by apC controllers, you must disable allof the controllers before you attenpt to \ntake the Comm Port offline. If any apC controllers are enabled when you attempt to take the apC Comm Port offline, an \nerror message is displayed -'Port cannot be disabled with enabled controllers. Please disable controllers fast. When the \ncontrollers are re-enabled they will do a full personnel download' \nThe message explains that when you re-enable the apC Comm Port, then re-enable the apC controllers, each controller \nwill perform a full personnel download. \nMaintenance \nMode \nClick to put the apC Comm Port into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nPartition \nThis read-only field dentifies the Partition in which this Controller resides. \nIf you are creating a new Controller, the Partition that is currentty the New Object Partition for your Operator account is \nautomaticalty assigned to each Controller you create. \nIf you want to change the Partition of a Controller, you must move the Cluster in which the Controller resides. See Using Drag and \nDrop in the Hardware Tree on Page 27. \nCommunications Type \nNetwork \nPort \nSelect Network Port if you are using a terminal sewer to connect your apC to C•CURE 9000. \nSerial Port \nSelect Serial Port if you are using a serial oon nection for your apC. \nRedirect \nSerial Port \nSelect Redirect Serial Port if you are redirecting the serial connection for an apC to a serial port that is physicalty on a Terminal \nServer, but logicalty on the C•CURE 9000 Server. \nPort Settings \nPort Timeout \nDelay Time \n(1/10 sec) \nThe Port\n... [truncated, 3454 chars — for the full page use /api/corpus/document/EFTA01225932/313 or ?id=EFTA01225932&page=313]", "char_count": 3454}, {"efta_number": "EFTA01225932", "page_number": 314, "text_content": "apC Comm Port Editor \napC Comm Port Field Definitions (continued) \nField \nCOM Port \nDescription \nSelect the Communications Type Serial Pon from the drop-down list. The Name field wi reflect the port number thatyou select. \nThe range is COM1 through COM256. \napC Comm Port Triggers Tab \nThe apC Comm Port Triggers tab allows you to set up Triggers - configured procedures used by C•CURE 9000 to \nactivate specific actions when a particular predefined condition occurs. \nThis tab provides you with ability to activate an event based on the Comm Status of the apC Comm Port. If the \nComm Status property of the apC Comm Port changes, you can specify the event you want to activate. \nA typical use for a Comm Port trigger would be to warn the Monitoring Station of a communications failure. You \ncan configure an event that would send a message requiring acknowledgment when the apC panels are unable to \ncommunicate with the host. \n1. Click the apC Comm Port Triggers tab to provide a means to link the Comm Port to an event. \nExample: \nA typical use for a Comm Port trigger would be to warn the Monitoring Station of a communications failure. You \ncan configure an event that might send a message requiring acknowledgment when the apC panels are unable to \ncommunicate with the host, as shown in Figure 98 on Page 315. \nFlours 98: apC Comm Port TriggersTab \n„IAA \nWin <of Comm Path \nDIOCAPKM \n%tack Correruncaos Port A \nErebied \nPinion DOA \nEl:we:Nice tie \nowes Non lawn I stew I &seems I \nM4 as ;team \nPIM* \nCan, Steen \nvrr \nAttla \n \nDade \nCcmmFW \nterse Eve* \n. \n°waft.,\ncc CsPSFi \nSnit \n!Mb \n2. Choose a Property for he Trigger from the Property drop-down list. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n315 \nEFTA01226246\n", "char_count": 1734}, {"efta_number": "EFTA01225932", "page_number": 315, "text_content": "apC Comm Port Editor \n3. Select the value that you want to activate the Trigger from the Value drop-down list. \n4. Pick the Action you want the Trigger to perform from the Action drop-down list. \n5. Depending upon the Action you chose, you may need to select the Action details from the Details field. For \nexample, if you chose to Activate an Event with the Action, you need to select an Event from the Details field. \nClick El and select an Event from the selection box that appears. \n6. Click Save and Close to save the Trigger settings for the apC Comm Port. \napC Comm Port Status Tab \nThe Status tab provides a read-only listing of critical information about the operational status of the selected apC \nComm Port including: \n■ Communications Status - displays the values Unknown or CommFail. \n■ Online Status - displays the values: Online, Disabled or Offline. \nFigure 99: apC Comm Port • Status Tab \napC Comm Port State Images Tab \nThe State Images tab provides a means to change the default images used to indicate communication port \nstates. These images appear on the Monitoring Station and change according to the state of the object that they \nrepresent. \nThe apC Comm Port - State Images tab is shown in Figure 100 on Page 317. \n316 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226247\n", "char_count": 1312}, {"efta_number": "EFTA01225932", "page_number": 316, "text_content": "apC Comm Port Editor \nFigure 100: apC Comm Port State Images Tab \nTo Change a State Image \n1. Double-click the existing image. A Windows Open dialog box appears allowing you to browse for a folder in \nwhich you have placed replacement images. \n2. When you locate the replacement image, select it and click Open to add it to the image listing. \n3. If you are done editing the apC Comm Port, click Save and Close to save the Comm Port's configuration. \nAlternatively, if you want to save the Comm Port and create a new one, click Save and New. The Comm Port \nEditor remains open to allow you to create a new Comm Port. \nTo restore the default image, right-click on the new image and select Restore Default. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n317 \nEFTA01226248\n", "char_count": 777}, {"efta_number": "EFTA01225932", "page_number": 317, "text_content": "apC Controller Editor \napC Controller Editor \nThe apC Controller editor allows you to configure apC, apC/8X, and apC/L panels and their connected Input \nboards, Output Boards, Readers, Inputs, and Outputs in C•CURE 9000. For more detailed information about the apC \npanel and its options, see the apC Panel Overview on Page 296. \nThe apC Controller Editor has the following tabs: \n• apC Controller General Tab on Page 319 \n• apC Controller Communications Tab on Page 321 \n• apC Controller Inputs Tab on Page 322 \n• apC Controller Outputs Tab on Page 323 \n• apC Controller Readers Tab on Page 323 \n• apC Controller Add-On Board Tab on Page 324 \n• apC Controller Status Tab on Page 325 \n• apC Controller Triggers Tab on Page 326 \n• Groups Tab for Hardware Devices on Page 28 \n• apC Controller Holiday Groups Tab on Page 327 \n• apC Controller User Defined Fields Tab on Page 329 \n• apC Controller State Images Tab on Page 330 \nTo Create an apC Controller \n1. To configure an apC controller from the C•CURE 9000 Administration Hardware pane, select the Hardware \nfolder for which you want to configure an apC Controller and right-click to display the context menu, as shown \nin Figure 101 on Page 318. \nFigure 101: Hardware Pane apC Controller Selection \n• \nHardware \n• Hardware \nHerd...ace Folder \nTree \nSearch \nCeetifscates \nRUC—' \nEdit \n4\nX Detete \ntD \nExport selection... \nFind in Audit Log... \nFind in Journal... \ns \nC.CURE Mobile \napC Comm Port \nau \n'STAR Cluster \nj, \nCVO\" \nri \nti \nISC Controller \nIfeleti \napC Controller \nk \nNeve\nNew Template \n• \nCard Formats and Keys \n318 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226249\n", "char_count": 1645}, {"efta_number": "EFTA01225932", "page_number": 318, "text_content": "apC Controller Edda( \nFrom the Hardware context menu, choose apC Controller and New. The apC Controller General tab appears, as \nshown in Figure 102 on Page 319. \nYou may also choose New Template. For further information about creating Templates, see Templates on Page \n34. \nIf the New and New Template selections are unavailable, you may be trying to create an apC in a Partition that \nis not your New Object Partition, or you do not have Privileges to create objects in this Partition. Check the \nC•CURE 9000 Menus to verify that your New Object Partition setting is correct, and check with your C•CURE \n9000 administrator that you have the correct Privileges. \napC Controller General Tab \nThe apC Controller General tab provides a means to select the Communications Port, RM LCD Messages, and to \nidentify the apC panel type. \nFigure 102: apCControler GeneralTab \naid \nSo. • ed nti• \nEns.* \n5w...own... \nNeel. me?... \no••••• \nay. I Amo.pesc. am. I is. I ramldwl\n asserml iraara Pas I sseasl \nGael \nJJ \n70,10\n1111•4 \nsyn. Ir\n.\nIse \nbow \nMS. \nelowl•••••16140W4•••••••••••••••••• \nAl\nim._\nSNI. aigrant r\na \nTo Configure the apC Controller General Tab \n1. In the apC Controller General tab, type a unique controller Name and a corresponding Description (optional) in \nthe identification fields at the top of the apC Controller dialog box. \n2. Maintenance Mode - Click to put the apC Controller and/or its components into Maintenance Mode. See \nChapter 2: Maintenance Mode for more information. \n3. Click the Enabled check box when you are ready for the apC to establish communications with the \nC•CURE 9000 server. You should wait until you have configured the controller settings and some or all of the \nInputs, Outputs, and Readers before enabling the apC. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n319 \nEFTA01226250\n", "char_count": 1830}, {"efta_number": "EFTA01225932", "page_number": 319, "text_content": "apC Controller Edda, \nNOTE \nThe apC Comm Port you choose in Step 5 must also be Enabled; otherwise, the apC cannot \nremain enabled. If you save the apC controller after assigning a disabled apC Comm Port, the \napC will go offline and when you open the apC object again in the apC editor, the Enabled check \nbox will no longer be checked. \n4. Select Direct Connect as the type of connection between the host and the apC. Use the Port field in this dialog \nbox to specify a port to which the apC chain is connected. \n5. To select a host communications Port for the apC controller, click 0 \nin the Port field to select an apC Comm \nPort. \nNOTE \nSoftware House strongly recommends that you select an apC comm port that is in the same \npartition as your apC. \nThe example in Figure 102 on Page 319 shows the selection of a Serial Port connection. \n6. To select a particular customized set of LCD messages for the RM Readers, click 0 \nto display a Reader LCD \nMessage Set selection list. If you leave this field blank (the default), the Readers use the default messages. \n7. Select the Time Zone in which your apC panel resides by clicking \nand selecting the Time Zone from the list \nthat appears. If you leave this field blank, the apC panel Time Zone defaults to the C•CURE 9000 server setting. \nYou can only change the value of the apC controller Time Zone when the apC Controller is not enabled (Enabled \nfield is blank O). See Changing the Time Zone of an apC Controller on Page 303. \n8. Select the type of apC panel you are configuring from the apC Type and Address box: \n• apC \n• \na pC/8X \n• apC/L \n9. Rotary switch settings can also be set on the apC panels using the two Switch entry fields. \nFor apC/L panels, the rotary switches are labeled 3-8 and 1. For all the other apC types, switches 4 and 5 are \ndisplayed. The range of settings is 0 through 9 or A through F for all but Switch 3-8, which has a range of 0 or 1. \nThe values you enter for Switch 4, Switch 5, Switch 1, and Switch 3-8 shoul\n... [truncated, 3054 chars — for the full page use /api/corpus/document/EFTA01225932/319 or ?id=EFTA01225932&page=319]", "char_count": 3054}, {"efta_number": "EFTA01225932", "page_number": 320, "text_content": "apC Controller Editor \napC Controller Communications Tab \nTo Configure the apC Panel Communications Tab \n1. In the Communications tab, as shown in Figure 103 on Page 321 enter the period in tenths of a second that the \npanel driver (on the Server) attempts to communicate with this panel in the Poll Period field. For example, if you \nenter 10, the panel driver communicates with this panel a minimum of once per second. \nYou can set different poll periods for each panel that you configure. This field is not available when Dialup is \nselected in the Connection Type list box. \nSoftware House recommends that you set the poll period to 20 (2 seconds). Setting this value lower than 20 \ncauses the host to receive activity from the panel more quickly but could cause the driver to interfere with other \nprograms running on the server at larger installations. This is especially true if the panel is on a network port. \nThe range is 0 - 850. \nNOTE \nSetting the poll period to more than 30 will result in up to a 3 or 4 seconds delay between reading the \ncard and opening the door. \nFigure 103: apC Controller - Communications Tab \ntwo k\nW.... \nFerro \n1..14.10•441 \nr sirs erase \nes.s c.....sprimiempain.d.itesearsigsrisamierisissistressiimakmals•12.••\n1 \n-Cowman* \n0•••••Maiind Ira \nM3••••••••0191.4•0 It \nPlidaneieSslindthrtims01••••) )0\n1=\n- 3 \nMlOsadoldellailliSPOISH1100.0 05,\n1 \nII•aesalandiftlimOmal \nfl\n2. Enter the extra interva in tenths of a second that the host waits for a response from this panel after sending a \nmessage to the panel in the Poll Timeout delay time field. If the host does not receive a response in the specified \ntime, the host retransmits the message or declares a communications failure. \nSoftware House recommends that you set this period to 80 (8 seconds). However, if you require additional delay \ntime because the panel runs on a Digiboard, Equinox board, or over a network, you may need to increase this \nvalue. Keep this value as small as possible, or system per\n... [truncated, 2217 chars — for the full page use /api/corpus/document/EFTA01225932/320 or ?id=EFTA01225932&page=320]", "char_count": 2217}, {"efta_number": "EFTA01225932", "page_number": 321, "text_content": "apC Controller Editor \n3. Enter the interval in tenths of a second that the host waits to declare an unresponsive panel to be in failure in \nthe Panel communications failure delay time. A message appears on the Monitoring Station in the case of a \npanel failure. \nSoftware House recommends that you set this period to 200 (20 seconds). The range is 0 - 850. \n4. Enter the interval in tenths of a second that the system polls the panel while it is in communications failure in \nthe Poll period while in communications failure entry field. Typically, you should set this value higher than the \nvalue for the initial poll period to avoid slowing down polling of other units on the chain. \nSoftware House recommends that you set this period to 200 (20 seconds). The range is 0 - 999. \n5. Enter the time period in minutes and seconds (mmss format) that the panel waits for a message from the host \nafter receiving the communications failure message from the host in the Host communications failure delay \ntime entry field. If the panel does not receive a message in the specified time, the panel declares a \ncommunications failure. \nSoftware House recommends that you set this period to 30 seconds. \n6. Click the Inputs tab to display it, as shown in Figure 104 on Page 322. \napC Controller Inputs Tab \nTo Configure apC Controller Inputs \nTo configure Inputs, select the check box in the Configured column (see Figure 104 on Page 322) and click \nlocated in the Edit column to display the apC Input editor General tab. See the apC Input Editor on Page 332. \nFigure 104: apC Controller Inputs Tab \nSO= \nlbw \nimuro \nr sown \nAA_ Mao \ncsms I ants \nIvo pupal Aral Allialimii•••11•••itsphidsplirpl immOdiralitiSI Issas.' \nPOISPoili\n[  P\ng oisnerva _ 0 Ss Sled* \n \ni Sam \nCiampi \nI NE. \nleers \nI TCra\"\n\u0013 \n, \n♦04•1•MPOS _C••••••••• \nIN \nIda \nI-. \n\u0013 \naX marmot* \n\u0013 \naPC InIelleC \n• \n..ene \n\u0013 \nart m4,01 \n\u0013 \nPea. C1 \n322 \nChapter 7 \nC•CURE 9000 Hardware Con figuration Guide \nEFTA01226253\n", "char_count": 1973}, {"efta_number": "EFTA01225932", "page_number": 322, "text_content": "apC Controfier Editor \nNOTE \nTIP \nClick the Delete All check box where ever it appears and then click Save and Close if you want to \neliminate all the Inputs, Outputs, or Readers that you have configured in a given dialog box. \nTo take an apC panel offline, remove the check from the Enabled option check box located below each \nReader, Input, or Output board Description entry field (located in General tabs). \nUse the Template column to quickly configure all in a particular set of inputs, outputs or readers. \napC Controller Outputs Tab \nTo Configure apC Outputs \n1. To configure Outputs, select the check box in the Configured column in the apC Outputs tab. \n2. Click [J  located in the Edit column to display the apC Output Board General tab. \n3. Use the apC Output editor to configure the output (See apC Output Editor on Page 336) \nFigure 105: apC Controls( Outputs Tab \napC Controller Readers Tab \nThe apC Controller Readers tab, shown in Figure 106 on Page 324, allows you to configure devices that supply \nWiegand, magnetic stripe and proximity card signaling. \nTo Configure an apC Reader \n1. Select the check box in the Configured column for the apC Reader (Index 1 through 8) you want to configure. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n323 \nEFTA01226254\n", "char_count": 1283}, {"efta_number": "EFTA01225932", "page_number": 323, "text_content": "apC Controller Editor \n2. Click 0 \nlocated in the Edit column to open the apC Readers General tab(see apC Reader General Tab on Page \n340). \n3. Choose either of the following options for all readers on the Readers tab: \n• Allow card numbers to be entered from the keypad. \n• Use PIN+1 as duress code. \n• Always use Shunt Expire Output on Door \nFigure 106: apC Controller ReadersTab \nNOTE \ns_LJLIE \n&vend am \nOm \"'pc' \nDosafloor \nP Enatied \nr 163otcrunct Mode \nPinta Ilan Wag \nGenni ICammcaore Itroas I awl \n8e4ecrs I midOn 85551 Ster.2 I Tom I Gass I Howe/ Grtuas I Ow Delesi ASS I kite mages \nP.M:ma \nr Can al Ittains \n:eels Al Peals \nEat \nh382 \nGalena \nIrk= \nTarobte \nI \nP \narC Roodetlapc tat \n2 \n17 \nWC 14•1812584 too \n3 \nr \napC Ree28.358C-1 \nL_Li \nA \nr \nark Flew.\n, \n5 \nr \napC 5480.0358C-1 \ns \nr \napC ReslakpC4 \n7 \nr \napt Fladiew01 \n8 \nr \n8K Flosa485C-1 \n—Deer end Rader Opiate \nr \naid -tea ..wind Gm braid \nr u.,FINtindinee cede \nr any, we Shwa bgir•Oulostbakce \nYou may configure an apC Reader from the apC panel Readers tab or from the Add-on Board tab. A \nreader index configured on one tab will be unavailable on the other tab. The location chosen will \naffect the possible reader type and reader input/output option selection. \napC Controller Add-On Board Tab \nThe Add-On Board tab, as shown in Figure 107 on Page 325, provides a means to expand the capabilities of the apC \npanels. Expansion boards can add reader ports, supervised inputs and additional outputs. \n324 \nChapter? \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226255\n", "char_count": 1545}, {"efta_number": "EFTA01225932", "page_number": 324, "text_content": "apC Contra!ter Editor \nTo Configure Add-On Boards Using the apC Add-On Board Tab \nTo start the configuration of Add-On Boards, select the check box in the Configured column in the apC Add-On \nBoard tab and click 0 \nlocated in the Edit column to display the apC Add-On BoardGeneral tab (see apC Add-on \nBoard Editor on Page 347). \nFigure 107: apC Coniroler Add-On Boar0Tab \napC Controller Status Tab \nThe Status tab, as shown in Figure 108 on Page 326, provides a read-only listing of critical information about the \noperational status of the selected apC Controller including \n■ Online Status - indicates whether the controller is online and communicating with the system. \n■ Firmware Version - the version of the firmware used by the controller. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n325 \nEFTA01226256\n", "char_count": 819}, {"efta_number": "EFTA01225932", "page_number": 325, "text_content": "apC Controfier Editor \n■ Communications Status - displays the values Unknown, CommFail, Comm. Normal, Comm. Loss, Comm. \nPassword Fail, Firmware Download, Card Download, Comm. Tamper, Comm. Power Fail or Comm. Battery \nLow. \n■ Connection Type Status - displays the values: Unknown, Conn. Normal, Conn. Direct, Conn. Dialup, Conn. \nDialing, Conn. Disconnected, or Conn. Connected. \n■ Current Personnel Records - displays the number of records. \n■ Panel state status - displays the values Unknown, Panel Normal, Panel Tamper, Panel Power Failure, \nConfiguration Download, Full Personnel Download, Full Download, Database Backup or Panel Battery Low. \nFigure 108: apC Controller Status tab \nSere Ix, \narAtCOOr \nP Erie; \nENreArkyce Mere \nPanora Man Wag \nGcnaS IC:rm./x.1n Ihxts I Oicas I Rnees I A:100+ Coal $tilea I hp-ars 1 Gni...4 I Hada/ Gro.od Uw Nene, 40:0 Sae maGei \nDrenc Sulu, \nFam•vt WIst.n I \nCcenracafaCe SOW \nCalebeCbC.1 Type Stn.. \naw RAN I \nCurren Perwevi Reccres \nMantuan PSKr✓tl ReCo \napC Controller Triggers Tab \nSee the following for information on apC Triggers: \n■ Triggers Tab for apC Devices on Page 369. \n■ Defining a Trigger for an apC Device on Page 370. \n■ Removing a Trigger on Page 272. \nYou can click Save and Close after configuring apC triggers, or navigate to the Status tab. \n326 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226257\n", "char_count": 1376}, {"efta_number": "EFTA01225932", "page_number": 326, "text_content": "apC Controller Editor \napC Controller Holiday Groups Tab \nA Holiday is a day or set of days that you configure to allow scheduling access control variations to time-based \nevents and to vary the normal lock and unlock time specifications. \nYou can include a Holiday in a Holiday Group and assign a Holiday Group to a schedule. \nYou need to configure the Holiday Groups that should apply to each apC, so that schedules on that apC respect the \ncorrect Holidays. If a Holiday Group is not listed on this tab, the Holidays it contains are not applied to this apC. \nNOTE \nHoliday Groups were called Holiday Lists in C•CURE 800/8000. \nIf a schedule downloaded to the apC has a Holiday Group assigned, and that Holiday Group is listed on this tab, \nthe activation times in the Holiday Group are evaluated. If the schedule is active and one of the Holidays in the \nHoliday Group is active, the start time and end time assigned with the Holiday Group become the schedule's start \ntime and end time. \nFor more information about apC Holiday Groups, see the C• CURE 9000 Software Configuration Guide. \nTo use the Holiday Groups tab, see Configuring Holiday Groups for an apC Panel on Page 327 for more information. \nConfiguring Holiday Groups for an apC Panel \nYou can download any holiday Group to an apC panel from the Holiday Group Configuration dialog box. \nA Holiday Group downloaded to an apC panel acts as an override to prevent activation of normally scheduled \nclearances on the Holidays defined in the Holiday Group. You can configure up to 8 holiday groups for each apC \npanel. \nOnly Holiday Groups that are downloaded to an apC panel will affect access control at that panel. \nTo Select Holiday Groups for the Panel \n1. On the Holiday Groups tab of the apC Controller dialog box, click the Add button. \nThe Group selection box appears allowing you to choose the Holiday Groups that you have configured, as \nshown in Figure 109 on Page 328. \n2. For each Group that you want to download to the apC pan\n... [truncated, 2296 chars — for the full page use /api/corpus/document/EFTA01225932/326 or ?id=EFTA01225932&page=326]", "char_count": 2296}, {"efta_number": "EFTA01225932", "page_number": 327, "text_content": "apC Controller Editor \nFigure 109: apC Controller HolidayGroups Tab \n \nPr\" \nsILI LIE \nPre •e:: • \nZn•crimor \nP Enatiee \n163.reenwct Mcce \nPallor Ma Mx, \neonI OPTarkaals I 'Mae I oats I Pews, I MOOn Cord I Staled %gen I Gate Moktry Gross I Uw Ddrel Atka I Ise ruces \nHeidi. &awe \n\"I' Add. \n.P.ara,t \nHeft \n \nOtiect Salomon \nSekci Int \n',am< \nbag <On+, ro ert4.01, by here \nNeat \n' I \n Ps \nI \nOescnvocr \nhoe to ilk,  Ave \nI \nHew., Go \nDoli.it \n3. Click OK to save add the selected Holiday Groups. \n4. A selected Holiday Group appears in the Holiday Group(s) box, as shown in Figure 110 on Page 329. \n328 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226259\n", "char_count": 669}, {"efta_number": "EFTA01225932", "page_number": 328, "text_content": "apC Controller Editor \nFigure 110: apC Controller HoklayGroups Tab \nsLJLIE \nOw? \nSr. \nDeltaMOr \nP Erlatled \nr gen:curet MCde \nPence Man Weg \nGeon I Cain...rani I rats I Oats I Reeeen I Moon Goya I Asa I Tape., l Gad Hobe* onkel lute Neva rem I ea. mar, \nWird. G'09 \n5. To remove one or more Holiday Groups, click a Holiday Group to select it (use CTRL+Left-click to select \nmultiple Groups), then click Remove to remove the selected Holiday Groups from the panel. \n6. Click the State Images tab to display it, as shown in Figure 111 on Page 331. \nClick Save and Close to return to the Hardware Pane to finish the apC Controller configuration. \napC Controller User Defined Fields Tab \nThe User Defined Fields tab, shown in Figure 1 on Page 330, displays user-defined fields in the system for hardware. \nUser-defined fields are configured in the Configuration pane. If there are no user-defined fields configured, then the \ntab is empty. \nSee the C• CURE 9000 Software Configuration Guide for more information. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n329 \nEFTA01226260\n", "char_count": 1081}, {"efta_number": "EFTA01225932", "page_number": 329, "text_content": "apC Controller Editor \nFigure 1: ape User Defined Tab \nfjois \nr anws.L. \nMs. D_ \ngad i Lsm.sSs1.I... I Dr I Flabd L.00.0s41 %LAI Inews I I ead IN\n Gee IlimNealA•11•I \nLew \napC Controller State Images Tab \nThe apC Controller State Images tab provides a means to change the default images used to indicate controller states \n(see Figure 111 on Page 331). These images appear on the Monitoring Station and change according to the state of \nthe object that they represent. \nTo Change an Image \n1. Double-click the existing image. \nA Wmdows Open dialog box appears allowing you to browse for a folder in which you have placed \nreplacement images. \n2. When you locate the replacement image, select it to add it to the image listing. \n3. To restore the default image, right-click on the new image and select Restore Default. \n4. Click Save and Close to finish the apC Controller configuration and return to the Hardware Pane. \n330 \nChapter? \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226261\n", "char_count": 990}, {"efta_number": "EFTA01225932", "page_number": 330, "text_content": "apC Controller Editor \nF lgu re 111: apC Controller State Images Tab \nJJJ \nNone [KC' \nP fade, \nSurtenance Mole \nPanty., Galway \nGreat I Coimsocatov I frats l Wats I Palen P6:10n Board I Ram I Top;en I Goss I Hada Grimm I thee Dance Feb 9-\" e‘rAm I \nRae \nin19,\nurc \nbrew \nFaso \nbrig \n1.,rieed I+ Pegs \nmy \nU U\nA \ny\ny \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n331 \nEFTA01226262\n", "char_count": 388}, {"efta_number": "EFTA01225932", "page_number": 331, "text_content": "apC Input Editor \napC Input Editor \nThe apC Input Editor is used to configure apC Inputs that you have created on the apC Controller Inputs tab. \n• apC Input General Tab on Page 332 \n• apC Input Board Triggers Tab on Page 333 \n• Groups Tab for Hardware Devices on Page 28 \n• apC Input Board - Status Tab on Page 334 \n• apC Inputs State Images Tab on Page 335 \napC Input General Tab \nThe apC Input - General Tab, shown in Figure 112 on Page 332, displays five read-only the Identification fields. The \napC Controller name is shown in the Controller field and the Input Board in the Board field. \nFigure 112: apC Controkr Inputs- General Tab \nNOM \nQ•100,01,\na \nle:C hattl- apC RE1 \nP gmeNdi \nr &Menem< Mode \nParbucn man We \nOmni I %On I Gas I Stele' IMe Delred RAO Sts. rages I \nWenidforice \nCows \nDade Selo \nCOOtlidt lacCI \naimed IfknarC-1 \nType 'G-••d \n&waled n I \nCQM0CICa kit 1 \nSang.ed \nP \nsinithwesPOW:falann9•1.:^ \nP Send state chain*: si p.rn.q \nr tavue a. Setivisual Bran \nr Armtd \nThe following Input fields are read-only: \n332 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226263\n", "char_count": 1103}, {"efta_number": "EFTA01225932", "page_number": 332, "text_content": "apC Input Editor \nType - reflects whether the Input has been assigned to a Door or other object or has a special purpose. These \ninclude: \n■ Tamper \n■ Comm Fail \n■ General \nAssigned To - displays the name of an associated Door or Elevator Button. If the Input is used for a door, then \nthe Name field is read-only displaying the name of the controlled door. \nConnection - specifies the input connection point on the Input Board and is assigned when the Board is \nconfigured. \nTo Configure the apC Inputs General Tab \n1. When the Supervised check box is selected, this read-only field indicates that the panel supports input \nsupervision. \nNOTE \nThe Supervised check box must be selected for Proprietary Burglar Alarm applications. \n2. To have a notification of changes in state of the Input sent to the guard station, select the Send state changes to \nthe monitoring station check box. \nNOTE \nThe Send state changes to the monitoring station option must be selected for Proprietary Burglar \nAlarm applications. \n3. To have a notification of changes in state of the Input sent to the journal, select the Send state changes to journal \ncheck box. This option will be selected by default. \nNOTE \nYou may limit the transmission of state change messages to the journal exclusively, when you \nclick to de-select the Send state changes to the monitoring station option and instead, select the \nSend state changes to journal option. Use of the latter option can decrease the messaging traffic \nderived from the apC Input during normal operations. To further limit messaging, you may also \nleave both check boxes unselected. \nYou may select multiple Inputs in a dynamic view and use the Set Property option to limit the \ntransmission of state changes. See Using Set Property for an iSTAR Controller on Page 130, for \nmore information. \n4. Activate on Supervision Error - Select this check box if the input is supervised and you want it to activate when \na supervision error occurs. \n5. Click Save and Close or\n... [truncated, 2459 chars — for the full page use /api/corpus/document/EFTA01225932/332 or ?id=EFTA01225932&page=332]", "char_count": 2459}, {"efta_number": "EFTA01225932", "page_number": 333, "text_content": "apC Input Editor \n■ Defining a Trigger for an apC Device on Page 370. \n■ Removing a Trigger on Page 272 \napC Input Board - Status Tab \nThe Status tab provides a read-only listing of critical information about the operational status of the selected apC \nInput including: \n■ Active Status - displays the values Active or Inactive. \n■ Armed Status - displays the values Armed or Disarmed. \n■ Hardware Status - displays the values: Secure, Active, Open Loop, Shorted Loop, or Fault. \n■ Supervision Status - displays the values: Un-initialized (not in supervision error), Open Loop, Shorted Loop, or \nFault. \nFigure 113: apC Boards Inputs Status Tab \nSyne \nlinattocc \nIrct WW1- apC RE I \np Enabled \nPith ce Wan Yen; \nr .mmsce Mode \nGeneral I Tryon I Goad and I Use Wined fekk I Side •.me I \nAC [we St3ELPS kw,* \n:env! SttituS \n'rawer Fete Ilkicnran \nSavior Statue Ithrdseked \n334 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226265\n", "char_count": 942}, {"efta_number": "EFTA01225932", "page_number": 334, "text_content": "apC Input Editor \napC Inputs State Images Tab \nThe apC Inputs State Images tab provides a means to change the default images used to indicate input states (see \nFigure 114 on Page 335). These images appear on the Monitoring Station and change according to the state of the \nobject that they represent. \nTo Change an Image \n1. Double-click the existing image. \nA Windows Open dialog box appears allowing you to browse for a folder in which you have placed \nreplacement images. \n2. When you locate the replacement image, select it to add it to the image listing. \n3. To restore the default image, right-click on the new image and select Restore Default. \nFigure 114: apC Boards InputsState Images Tab \n=UM! \nki 54 vc and Oa.< \n4. Click Save and Close. \nNa** \nQat' cOOn \nev- Vox? \nAEI \nP Enabled \nr Sirasnart• Mc* \nPt \nMon Wm \nail \nI Teen I Gee) Sr. I a \nDOW NW Singe I \nSAW \n mew \nLl \nkbre \nMood From \nDeemed Eretied \nSuNria.:e EnO,\nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n335 \nEFTA01226266\n", "char_count": 1002}, {"efta_number": "EFTA01225932", "page_number": 335, "text_content": "apC Output Editor \napC Output Editor \nThe apC Output Editor is used to configure apC Outputs that you have created on the apC Controller Outputs tab. \n• apC Output General Tab on Page 336 \n• Groups Tab for Hardware Devices on Page 28 \n• apC Output Status Tab on Page 337 \n• apC Output State Images Tab on Page 338 \napC Output General Tab \nTo Configure Outputs Using the apC Output General Tab \nThe apC Output General tab lists the following read-only fields: \nType - reflects whether the Output has been assigned to a Door or other object. For apC panels, General is the un \nassigned output type. \nAssigned To - displays the Elevator or Door object name. For any Output, the Connection field indicates the \nindex number on the board. \nFigure 115: apC Controls( Outputs General Tab \nName \nrel<WACe \nR El \nP tingled \nPants. liam Vic \nr Manyearce Mode \nCnatinaps I Asa I m,  Ddnod fields I Sloe \"epee I \n0Axst tleakinco \nCoteau Igo-i \nI \nType knoll \n6rit-resb,\nCOamobc\" /Win I \nbise &taco tilOsoc) 17 \nP NOUnally awned \nP Sad sum modes Pnxntono0 stm+te \n1. The following Options are configurable for an Output: \n338 \nChapter? \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226267\n", "char_count": 1179}, {"efta_number": "EFTA01225932", "page_number": 336, "text_content": "ape Output Editor \na. Pulse Duration - (momentary activation) is entered in tenths of a second intervals with a default of 0 seconds. \nThe range is 0 to 1000. \nb. Normally Energized - When checked, the output is energized (power is supplied to the relay) when it is \ninactive. When the output is activated, power is removed. \nc. To have a notification of changes in state of the Output sent to the Monitoring station, select the Send slate \nchanges to the monitoring station check box. This selection is unavailable for an apC Door Output. State \nchanges for a Door Output are not sent to the Monitoring Station. \nd. To have a notification of changes in state of the Output sent to the journal, select the Send state changes to \njournal check box. This option is selected by default. This selection is unavailable for an apC Door Output. \nState changes for a Door Output are not sent to the journal. \nNOTE \nYou may limit the transmission of state change messages to the journal exclusively, when you \nclick to de-select the Send state changes to the monitoring station option and instead, select the \nSend state changes to journal option. Use of the latter option can decrease the messaging traffic \nderived from the apC Output during normal operations. To further limit messaging, you may \nalso leave both check boxes unselected. \nYou may select multiple Outputs in a dynamic view and use the Set Property option to limit the \ntransmission of state changes. See Using Set Property for an iSTAR Controller on Page 130, for \nmore information. \n2. Click Save and Close or the apC Outputs - Status tab to display it, as shown in Figure 116 on Page 338. \nFor further information about the use of the Groups tab, see Groups Tab for Hardware Devices on Page 28. \napC Output Status Tab \nThe Status tab (see Figure 116 on Page 338 provides a read-only listing of critical information about the operational \nstatus of the selected apC Board Output including \n■ Active Status - displays the values Active or In\n... [truncated, 2179 chars — for the full page use /api/corpus/document/EFTA01225932/336 or ?id=EFTA01225932&page=336]", "char_count": 2179}, {"efta_number": "EFTA01225932", "page_number": 337, "text_content": "apC Output Editor \nF igu re 116: ape Outputs Status Tab \n&Ism< ald or \napC Output State Images Tab \nThe State Images tab provides a means to change the default images used to indicate output states. These images \nappear on the Monitoring Station and change according to the state of the object that they represent. \nThe apC Output State Images tab is shown in Figure 117 on Page 339. \nTo Change an Image \n1. Double-click the existing image. \nA Wmdows Open dialog box appears allowing you to browse for a folder in which you have placed \nreplacement images. \n2. When you locate the replacement image, select it to add it to the image listing. \n3. To restore the default image, right-click the new image and select Restore. \n338 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226269\n", "char_count": 794}, {"efta_number": "EFTA01225932", "page_number": 338, "text_content": "apC Output Editor \nF igu re 117: apC Outputs State Images Tab \n4. Click Save and Close. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n339 \nEFTA01226270\n", "char_count": 160}, {"efta_number": "EFTA01225932", "page_number": 339, "text_content": "apC Reader Editor \napC Reader Editor \nThe apC Reader Editor is used to configure apC Readers that you have created on the apC Controller Readers tab. \nThe apC Reader editor has the following tabs: \n■ apC Reader General Tab on Page 340 \n■ apC Reader Input/Output Tab on Page 341 \n■ apC Reader Keypad Tab on Page 342 \n■ Hardware Groups Tab Definitions on Page 29 \n■ apC Reader Triggers Tab on Page 344 \n■ apC Reader Status Tab on Page 344 \n■ apC Reader State Images Tab on Page 345 \nYou can add or remove Card Formats from multiple Readers via an apC Reader Dynamic View. See Add or Remove \nReader Card Formats on Page 25 for more information. \napC Reader General Tab \nTo Configure a Reader Using the apC Reader General Tab \n1. Select a Reader Type: MRM, Direct Connect Wiegand, or RM, as shown in Figure 118 on Page 341. \nThe Reader Type selected should match the connected apC panel since the type will affect the inputs and \noutputs available on the Reader I/O tab. \nExample: \n• The RM has 2 supervised inputs and 2 outputs. \n• the MRM has 2 supervised inputs and 1 output. \nThe Identification area in the Readers - General tab displays read-only, previously-configured information. \n2. To choose a card format for the reader that you have selected, click Add in the Card Format area. The Card \nFormat browser appears, as shown in Figure 118 on Page 341. \nNOTE \nYou may configure an apC Reader from the apC panel Readers tab or from the Add-on Board tab. \nA reader index configured on one tab will be unavailable on the other tab. The location chosen \nwill affect the possible reader type and reader input/output option selection. \nSee the C•CURE 9000 Getting Started Guide - Table 1-5 for a list of UL approved card formats and \nreaders. \n340 \nChapter 7 \nC•CURE 9000 Hardware Con figuration Guide \nEFTA01226271\n", "char_count": 1813}, {"efta_number": "EFTA01225932", "page_number": 340, "text_content": "apC Reader Editor \nFigure 118: apC Controller - Readers- General Tab \nF\n \nA\nM\n\"\n \nReader \napt React,. I api RI I \na sera ad One \nflow \nanC61:6011: \nlogC Reodel.zof RETI \n.:J \nP &tied \nRIMS: MOI Wog \nr ticimenrce Mode \n•-^\"•••• (w \nI twflog I TI\n I way* l au I I.M. loom nom I ase awn \nIfilenalteO \nacotolkr: l.01 \nBard \nAasegotO to lax door) \nC000chon IFkeder \nRwagC-1 \nR•okt \nCard Fail \nlam \nr. gad P.Itnoot \nfl-4 \n3. Click the applicable row in the Card Format browser to select Card Format. Repeat for multiple formats. \n4. Navigate to the Input/Output (I/O) tab (see Figure 119 on Page 342). \napC Reader Input/Output Tab \nDedicated Supervised Inputs and Outputs vary on the apC Readers I/O tab, depending upon the Reader Type \nselected in the Reader General tab. The I/O Tab is shown in Figure 119 on Page 342. \nTo Configure the I/O Tab \n1. To configure the Inputs, follow the instructions given in To Configure apC Controller Inputs on Page 322. \n2. To configure Outputs, follow the instructions given in To Configure apC Outputs on Page 323. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n341 \nEFTA01226272\n", "char_count": 1120}, {"efta_number": "EFTA01225932", "page_number": 341, "text_content": "apC Reader Editor \nFigure 119: apC Controller Reader InpuVOutput Tab \nirgj 2g \n&eve sit:kb. \nkn\n l[ApC Readal-apC RE I \nrboalotlen: \nF pew \nPt \nMain Wro \nr Mpiriennelkde \n*Coital I/O \nIrmpeelTetonI Goa I eas Us Oemed nal I &all MP' I \n' \nas \n3e Cite* M Inn \n_ Intel trouts \nEct \nI amen \nCaned\nNam \nlade \nSown I \nF \napC Fps - I -apC Reeled- apC REI \nkoarriped 2 \nr \nIsC In - 2 -ape Roaderl-ariC RE1 \n, \nChin \nk Create AI Gun. _Delete AI Gni, \nEIS \nCnInt \nI Calingl \n!In, \nt \nus \na \nr \n0404  • 1 AC R••441.ipc RE1 \n0.02 .2 -egC Reeder'. epC REI \n3. Navigate to the Keypad tab to configure the PIN requirements for the reader. \napC \nReader \nKeypad \nTab \nThe apC Readers - Keypad tab provides a means to control reader keypads (see Figure 120 on Page 343). Keypad \nconfiguration on an apC panel allows specification of Card and PIN required. The Schedule is configurable when a \nPIN is required and restricts the time when the PIN must be entered. The default Schedule is Always and is the \ninitial value of the Schedule browser. \n342 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226273\n", "char_count": 1098}, {"efta_number": "EFTA01225932", "page_number": 342, "text_content": "apC Reader Editor \nFigure 120: apC Controller - Readers- Keypad Tab \ndo \na Saw edam \nPC Reader! apt RI I \nSinr \nflealitaix \nlapC Resodel.epC PEI \nI tne$ed \nr Mamenance Mode \nPertibon Man Wm \nemend Lo \nIMOM I Tromrt I Gram I Stets I Um Dined Roos I Stele nom I \nFIII Rm.:erred: \nR PIN is Ka itquitid \nr \nr Card and AN rodweed \n_LI \nTo Configure the apC Readers - Keypad Tab \nI. Choose one of three options for PIN Requirements: \n• PIN is not required - to require a card swipe only; \n• PIN Only \n• Card and PIN required - to require a both a card swipe or presentation with a PIN entry. \n2. Click 0 \nto select a Schedule, which is set up in the Configuration Pane. \nIf you selected PIN is not required or Card and PIN required for PIN Requirements, two choices appear in the \nOptions area. \n3. Choose either of the following options: \n• Allow card numbers to be entered from the keypad. \n• Use PIN+1 as duress code. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n343 \nEFTA01226274\n", "char_count": 987}, {"efta_number": "EFTA01225932", "page_number": 343, "text_content": "apC Reader Editor \napC Reader Triggers Tab \nSee the following for information on apC Triggers: \n■ Triggers Tab for apC Devices on Page 369. \n■ Defining a Trigger for an apC Device on Page 370. \n■ Removing a Trigger on Page 272 \nYou can click Save and Close after configuring apC Reader triggers, or navigate to the Status tab. \napC Reader Status Tab \nThe apC Reader Status tab provides a read-only listing of critical information about the operational status of the \nselected apC Readers including: \nThe apC Reader Status tab is shown in Figure 121 on Page 345 \n■ Communications - displays the values Normal or Comm Fail \n■ Tamper - displays the values True or False. \n■ PIN Required - displays the values True or False. \n344 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226275\n", "char_count": 793}, {"efta_number": "EFTA01225932", "page_number": 344, "text_content": "apC Reader Editor \nFigure 121: apC Controller- Reader Status Tab \nall2I2JE \nSave and Cbx \nHan' \nDinalobeet \nleaC Rea:or I toC \nfretted \nPreen Mal Wro \nr Winmeance Made \nGym\" I V0 \n1 Repel I Tram I Sato gamble\" Defrod ROM Stele mewl \n-porn< Sas \nformers Veneto. \nCommunications: INowt \nEIN Rowlett 'Hat Reamed \nLanier IF** \napC Reader State Images Tab \nThe State Images tab provides a means to change the default images used to indicate reader states (see Figure 122 \non Page 346). These images appear on the Monitoring Station and change according to the state of the object. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n345 \nEFTA01226276\n", "char_count": 648}, {"efta_number": "EFTA01225932", "page_number": 345, "text_content": "apC Reader Editor \nFigure 122: apC Controller - Readers- State Images Tab \n=II DJ 2g \nja Save ed that \nI \nUr* isC Reed. 1 cpC RE I \nQescaco \nEnsued \nr Maimmence Wee \nPate«, Mon Ifing \nGovnil l0 \nI %pad I Tecces I Cam I Saba I Llw Dined raft \nMMO 0‘19n I \nAde \n*ago \nPIM Trace (Sake Macs Oaf) \nLow Boar/ ONdem OrM \nVeal Lath Oren do Mita,  %Waco OM \nPark barn adewwww0s4 \nKay eArdrOowlat Von Orly) \nLack Free bowl Ammo Orly) \nLodi 9ste Awned Vase Orhi \nTo Change an Image \n1. Double-click the existing image. A Windows Open dialog box appears allowing you to browse for a folder in \nwhich you have placed replacement images. \n2. When you locate the replacement image, select it to add it to the image listing. \n3. To restore the default image, right-click on the new image and select Restore Default. \n4. Click Save and Close. \n348 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226277\n", "char_count": 898}, {"efta_number": "EFTA01225932", "page_number": 346, "text_content": "apC Add-on Board Edrtor \napC Add-on Board Editor \nThe apC Add-on Board Editor provides a means to configure boards that expand the capabilities of the apC panels. \nExpansion boards can add reader ports, supervised inputs and additional outputs. \nThe apC Add-On Board Editor displays the following tabs: \n■ apC Add-On Board General Tab on Page 347 \n■ apC Add-On Board Input Boards Tab on Page 348 \n■ apC Add-On Board Output Boards Tab on Page 349 \n■ apC Add-On Board Star Coupler Tab on Page 354 \napC Add-On Board General Tab \nThe apC Add-On Board General tab displays the Board Location Controller field, which is a read-only field that \ndisplays the associated apC panel. Navigate to the Input Boards tab. See Figure 123 on Page 348. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n347 \nEFTA01226278\n", "char_count": 807}, {"efta_number": "EFTA01225932", "page_number": 347, "text_content": "apC Add-on Board Editor \nFigure 123: apC Controller Ad d-On Board General Tab \nCa apC Add-On Board - apC Add-apc test \n1JxI \nSave and Close \nName: \nDescription: \nIaoC Addeoc test \n_J \nJ \nPartition. Man Wile \nr \nMaintenance Mode \nGanda' Haut Boards I Output Borth I Star Gawks\nBoard Location \nController I \napC Add-On Board Input Boards Tab \nThe apC Add-On Board Input Boards tab allows you to add a Supervised 132 Input Board (Index 1) and eight \nSupervised IS Input Boards (Index 1 through 8). \nTo Configure the 132 Input Board Using the apC Input Boards Tab \n■ To configure the 132 Input Board, select the check box in the Configured column in the apC Add-On Board -\nInput Boards tab and click El located in the Edit column of the Supervised 132 Input Board box to display the \napC 132 Input BoardGeneral tab (see Figure 124 on Page 349). \n348 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226279\n", "char_count": 913}, {"efta_number": "EFTA01225932", "page_number": 348, "text_content": "apC Add-on Board Editor \nFigure 124: apC Controller Add-On Board Input Boards Tab \nIDt apC Add-On Board - apC Add-app test \nA save and cicnx. \nName: \nQesaipeon: \napC Addepc test \nParution Man Wing \nI— Maintenance Mode \nGeneral bin Bowie I Output Boards I Star Coupler I \n—Supervised 132 Input Board — \nJ Create \n Delete \nEdt \nkits \nCall9nd \nNana \ntart 132 MA Board leipC Addeipc test \nSupervised IS Input Boards \ncreate all Boats 7 Delete Al Boards \nEdt \nhem \nI Unkind \nName \n1 \nIP' \napC la Foul Bort apC Addyric te• \n2 \nW \nIOC IS krout BoteacciC Addape test \n3 \nr \n.e is Iron Boat3apC Addapc tet \n4 \nr \nape PI kW Board4epC Addepc test \n5 \nr \naPC PI kid Board5tpC Addax teat \n6 \nK \napC 18 !Iva BoardSepC Add-apc ted \n7 \nK \napt 91 kput Bezed7epC Addax tett \n8 \nr \napC IS WA BoangapC Addepc test \napC Add-On Board Output Boards Tab \nThe apC Add-On Board Output Boards tab allows you to add two R48 and eight R8 Output Boards. \n■ R48 Output Board on Page 349 \n■ R8 Output Board on Page 352 \nR48 Output Board \nTo Configure the R48 Output Board \n1. To configure the R48 Output Board, select the check box in the Configured column in the apC Add-On Board \nOutput Boards tab and click 0 \nlocated in the Edit column of the R48 Output Boards box (see Figure 125 on \nPage 350) to display the apC R48 Output Board General tab, as shown in Figure 126 on Page 351. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n349 \nEFTA01226280\n", "char_count": 1424}, {"efta_number": "EFTA01225932", "page_number": 349, "text_content": "apC Add-on Board Editor \nFigure 125: apC Controller Add-On Board Output Boards Tab \nLY apC Add-On Board - apC Add-apc test \n.{4 Save and Close \nName: \nDescription \napC A d aoc test \nPart:non Man ?hie \nMaintenance Mode \nOyler\" I Inn Boards Output Bowls I Star Coupler\nMB Output Boards \nv Create All Boat \nDe'ete NI Boards \nColigured \nName \n2 \n2 \n• I\napC R48 Outp4 BoardlopC Addax teat \n• \ntoC R48 Outiot Beed2opC ticle-apc test \n—FOB Output &ord. \nv Create Al Boards \n Delete AP Boards \nEdt \nint( \nCcriouted \nBre \nW \n1 \nW \n%CRS Curd Boall-apC NM-meted \n2 \nr \napC FPI Baps Board2-apC Addepc teat \n3 \nr \n8 Output BoadlapC ArkFarctert \n4 \nr \nariC Ft8 °trot Board4-apC Pavetest \n5 \nr \napC Ft8 Ottpu Board5apC Arriape tee \n6 \nr \napC 143 Caput likeird&apC irclOarc teat \n7 \nr \nacC RSOutput Bowd7-apC Maya tat \n5 \nr \nrOC MUM 60100840C Fiddler led \nThe apC R48 Output Board General tab displays three read-only fields: \n• Controller \n• Board \n• Board Index \nThese fields locate the Output that you have chosen to configure. As you configure more Add-On Board Outputs \nfor this controller, the Board Index field reflects the output placement on the R48 output board, ranging from 1 \nthrough 2. \n350 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226281\n", "char_count": 1256}, {"efta_number": "EFTA01225932", "page_number": 350, "text_content": "apC Add-on Board Edrtor \nFigure 126: apC Controller Add-On Board Output Boards General Tab \nt \napC R48 Output Board - apC R48 Output Board, apC Add-\n'x \n-I im and Mae \nQtecoplan. \n 1 \nGenesal11.16thApuls 1 17.3200RA: \n33 48 eurws \nLocal \nCalITOSIC \ntoed \nBold 'row \nlac\n• Comm A • RE RI \nneRckl• \n1 \n2. 7•o configure Outputs, select the apC R48 Output 1-16 Outputs tab, as shown in Figure 127 on Page 351. \nFigure 127: apC Controller Add-On Board Output Boards 1-16 Outputs Tab \nKS= [PC R48 CAW (Wadi AK Addipe \n0Brrbdpra \n, o,s 1460Upr: 1I320apUl 33 480.4pis \n.17 All 0403 \nOS% All Clulputs \nFY \nbx \n \n 3 \n \n4 \n \n5 \nU\n76\n[ \n 8\n \n 9\n \n 10 \n[ \n 11 \n \n 12 \n \n 13 \n \n14 \nI= \n15\n \n 16 \nCatpred \nNma \n701'0.1,0 \n• \naPC OUP..41.44C R48 OSA Boeql \nK \napC 0Upa2apCR4GOsJ BAAS, .)0 \nK \nact OusAtlapC RIB Maw Baadl•m..\nK \necC Oup.Al.sCRA800:4 Bordlio \nK \napC Oup45cpC MS OS. Bood1.40 \nK \nmC 00406.44CF4480u0.4Boadlta \nK \n.tioC Ow/47.6C RIB O4AA BoodlAo \nK \napt °JAS.:AC Mass Down* \nK \napC 00:09.apERSOuPpl BoaARAA \nK \nec.0 Otio410-ect RIES OchAA Bosdl \nK \ncc OUral ' ,Ape Ale Clapial Bondi a \nK \napC OUoal 2AAC R48 Os/ EINAR.* \nK \nocCOtAx.13-ecCR480.408oAdIA \nK \n40coap.4144CA4110.1p484.01 a \nK \napC Ot4a415-44:CR480t/pulBordba \nK \n4cC Otio416,<C P48 Dirot Boe.51 \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n351 \nEFTA01226282\n", "char_count": 1326}, {"efta_number": "EFTA01225932", "page_number": 351, "text_content": "apC Add-on Board Editor \n_1= \n3\nK \nE \nK \n- 1 6\nK \n1 6\n0 \n1 \n0 \nIs \n0 \n6\" °ea Ai Iput; \n3. To configure the Outputs on the Add-On Board R48 Outputs 1-16 Outputs, 17-32 Outputs and 33-48 Outputs \ntabs, follow the instructions given in To Configure apC Outputs on Page 323. \n4. Once you have finished configuring the R48 Outputs, click Save and Close to return to the apC Add-On Board \nOutput Boards tab. \nR8 Output Board \nTo Configure an R8 Output Board \n1. To configure the R8 Output Boards, select the check box in the Configured column in the apC Add-On Board \nOutput Boards tab and click C] located in the Edit column of the R8 Output Boards box (see Figure 125 on Page \n350) to display the apC R8 Output Board General tab, as shown in Figure 128 on Page 352. \nFigure 128: apC Controller Add-On Board Output Boards General Tab \nepC RB Output Board \n- apC R8 Output Boardl-apC \nA... ±-\nIbSavo ane Clot* \nIts \njog Re 03003313433322(92 /1•30a3C RE 2 \nCasette.% elf dennE0333 \nComvie• \n*ECRU \n1/0.+3 \n32C 43113of RE 2 \nE333.3 one. \n3 \n3\" 6./ 63 t.3 Al Outputi \n00303 AR Copal \ndex \n[whys! \nRaw \nacC (howl -4cC R8 Out,. Bora) a. \nacc OunAteEC R8 03433 Bounflac,\nE3C 03•0382e3C R803434 earflap \nEEC 03•32334 e3C Re 03443 83.3.03ap \naK 03•3313•3C R130332... 834.313q3 \ncC 03•33.36sC R80330.3 Barfly \n32C 0~7 o3C R80343.2 8,33,33.0 \n32C 03.13.43 erg 000+w 03.33,33. \nEd.k\nirea be. \nteeny*, \nliar \nTarp.. \n0 \nTimpwapC RE °opt* OonslapC A61 \nCessesca \nin \nComonatinfalapC RE Otow Boa \nr.netle  1 \nThe apC R8 Output Board General tab displays three read-only fields: \n• Controller \n• Board \n• Board Index \nThese fields locate the Output that you have chosen to configure. As you configure more Add-On Board Outputs \nfor this controller, the Board Index field will reflect the output placement on the R8 output board, ranging from 1 \nthrough 8. \nThere are also two Status inputs available for the R8 Output Board: \n352 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226283\n", "char_count": 1976}, {"efta_number": "EFTA01225932", "page_number": 352, "text_content": "apC Add-on Board Editor \n■ Board Tampered, which indicates tampering with the Add-On Board \n■ Communications Fail, which detects a communications failure. \nNOTE \nYou will not see comm fail or tamper until at least one of the inputs or outputs is configured. \n2. To configure the R8 Output, select the check box in the Configured column in the apC R8 Output Board General \ntab and click ID located in the Edit column of the R8 Outputs box, as shown in Figure 128 on Page 352. \n3. To configure each RS Output, follow the instructions given in To Configure apC Outputs on Page 323. \n4. Once you have finished reader the R8 Outputs, click Save and Close to return to the apC Add-On Board Output \nBoards tab. \n5. Click the Star Coupler tab to configure Star Coupler Readers, Inputs and Outputs, Mini Star Readers and WPSC \n(Wiegand Proximity Star Coupler) Readers and Supervised Inputs. \nNOTE \nBecause the apC can only support 8 readers, some of the Reader ports on the Star Coupler may be \nunavailable to configure on C•CURE 9000 if readers are configured directly on the apC Readers tab. \nFor example, if Readers 1 and 6 are configured on the Readers tab, Readers 1 and 6 will be \nunavailable on the Star Coupler (Configured check box is read-only). Conversely, if Readers 1 and 6 \nare configured on the Star Coupler, then Readers 1 and 6 on the Readers tab will be unavailable. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n353 \nEFTA01226284\n", "char_count": 1448}, {"efta_number": "EFTA01225932", "page_number": 353, "text_content": "apC Add-On Board Star Coupler Tab \napC Add-On Board Star Coupler Tab \nThe apC Add-On Board Star Coupler tab allows you to add one of the following: \n■ Star Coupler, with up to 8 Star Coupler Readers, 8 Unsupervised Inputs and 8 Outputs. See the apC Star Coupler \nBoard Editor on Page 365. \nOr \n■ Mini Star with up to 8 Mini Star Readers. See the Mini Star Coupler Board Editor on Page 373. \nNOTE \nor \nThe Mini Star Reader has not been evaluated by UL and cannot be used in UL Listed applications. \n■ WPSC (Wiegand Proximity Star Coupler) with up to 8 WPSC Readers and 8 Supervised Inputs on upper and \nlower boards. See the Wiegand Proximity Star Coupler Editor on Page 376. \nNOTE \nUnsupervised inputs cannot be used in Proprietary Burglar Alarm applications. \nFigure 129 on Page 355 shows the apC Add-On Board Star Coupler tab. \n354 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226285\n", "char_count": 901}, {"efta_number": "EFTA01225932", "page_number": 354, "text_content": "apC Add-On Board Star Coupler Tab \nFigure 129: apC Add-on Board Star Coupler Tab \nCa apC Add-On Board - apC Add-apc test \nsIL1 \nand rifle. \nName: \nQescripeon: \napC Addeo° test \nPartition-- Man Wing \nF Maintenance Mode \nGenes I inrm Boss I Output Bost Star Caeler\n—Ste Coupler \nrat \nI 9ar Cater \nCoritand \nI Name \nStarCoupder \nMei Stet \nWPSC \nr \nStar CouplerapC Addapc teal \nMN StetetsC Add-ape test \nWPSCapC Addapctee \nConfiguring the apC Add-On Board Star Coupler Tab \nYou use the apC Add-On Board Star Coupler tab to configure the type of Star Coupler board you have connected to \nyour apC controller. \nTo Configure the apC Add-On Board Star Coupler Tab \n1. Open the apC Add-On Board Editor by navigating in the Hardware Tree to the apC controller you want to edit, \nthen navigating in the tree to the apC Add-On Board you want to edit. \n2. Double-click on the apC Add-On Board. The apC Add-On Board Editor opens. \n3. Click on the Star Coupler tab. \n4. For the Star Coupler board type that is attached to your apC, click in the Configured column to enable that board. \nExample: \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n355 \nEFTA01226286\n", "char_count": 1152}, {"efta_number": "EFTA01225932", "page_number": 355, "text_content": "apC Add-On Board Star Coupler Tab \nIf you have attached a Mini Star Coupler to your apC, click Configured for the Mini Star in the Star Coupler \ntable. \nNOTE \nIf you select a Star Coupler and then by to enable a different one, a message appears \nasking \"Are you sure you want to delete the Star Coupler object ,object-name>?\" \nbecause you can only have one Star Coupler configured. \nClick Yes if you want to delete the Star Coupler you configured and replace it with \nyour new choice. \nClick No if you want to keep the Star Coupler you configured and cancel this action. \napC Add-On Board Star Coupler Tab Definitions \n'!'he apC Add-On Board Star Coupler tab has the (Slowing file and buttons. \nTable 82: apC Add-On Board Star Coupler Tab Definitions \nField/Button \nDescription \nEdit Column \nClick n \nin the Edit column to open the editor for the Star Coupler you have enabled. \nStar Coupler \nColumn \nThis column displays the type of each Star Couplers you can enable and configure. \nConfigured \nClick nin this column to enable a Star Coupler, Mini Star, or WPSC (make it available to be edited). \nName \nDisplays the name for this Star Coupler. The name is system-generated by defautt, but you can edit this name by clicking in click \nin this field. \nStar Coupler \nThe Star Coupler is a single expansion board that attaches to the a pC/8X or apC to a lbw the RM readers. I/8 inputs. and R/8 \noutputs to be wired in a Star topology. \nMini Star \nA Mini Star is a single expansion board that attaches to the a pC/8X or apC panels to allow the RM readers to be wired in a star \ntopology. \nWPSC \nThe Wiegand/Proximity Star Coupler (WPSC) consists of a two board set that attaches to the apC or apC/8X to allow direct \nconnection of up to 8 read heads using Wiegand signaling. \n356 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226287\n", "char_count": 1843}, {"efta_number": "EFTA01225932", "page_number": 356, "text_content": "apC Input Board Editor (132 and 18) \napC Input Board Editor (132 and 18) \nThe apC Input Board editor is used to configure apC Input Boards that you have created on the apC Add-on Boards \ntab. \nThe apC Input Board editor has the following tabs: \n■ apC 132 Input Board General Tab on Page 357 \n■ apC 132 Input Board 1-16 Inputs Tab on Page 358 \n■ apC 132 Input Board 17-32 Inputs Tab on Page 360 \n■ apC 18 Input Board General Tab on Page 362 \napC 132 Input Board General Tab \nThe apC 132 Input Board - General tab, as shown in Figure 130 on Page 358, displays the Input Location -\nController, Board and Board Index fields. These are read-only fields that display the apC panel, the apC Add-On \nBoard and Index (for the 132 Inputs the Index is 1) associated with the 132 Supervised Inputs. \nThese fields identify the Input board that you have chosen to configure. The Board Index field reflects the position of \nthe 132 input board on the apC. \nNavigate to the 1-16 Inputs tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n357 \nEFTA01226288\n", "char_count": 1047}, {"efta_number": "EFTA01225932", "page_number": 357, "text_content": "apC Input Board Editor (132 and III) \nFigure 130: apC Controller 132 Add-On Board General Tab \n0 apC 132 Input Board - apC 132 Input Boardl-apC 2 \nI3 Save and Case \nName: [,oc 132 VDU %aril epC 21 \n12escripfien: \nj \nPanition: Man W1ng \n1-  Maintenance Mode \nGummi 11.16 Inputs 11732 Inixts I Group \nLocation \ncontroller lapC-1 \nBoard 'apC Addapc teat \nBgard Index. 11 \napC 132 Input Board 1-16 Inputs Tab \ntrhe apC 132 Input Board 1-16 Inputs tab allows you to add 16 Supervised Inputs on the 132 Input Board (Board \nIndex 1). \nTo Configure the 1-16 Inputs Board \n1. To configure the 146 Supervised Inputs, select the check box in the Configured column in the apC Add-On \nBoard -132 Input Board - 146 Inputs tab (see Figure 131 on Page 359) and click 0 \nlocated in the Edit column \nof the Supervised Inputs box to display the apC Input (Index Numbers 1 through 16)132 Input Boardl -\nGeneral tab (see Figure 132 on Page 360). \n358 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226289\n", "char_count": 997}, {"efta_number": "EFTA01225932", "page_number": 358, "text_content": "apC Input Board Editor (132 and 18) \nFigure 131: apC Controller 132 Add-On Board 1-16 Inputs Tab \nQ! apC I32 Input Board - apC 132 Input Boardl-apC 2 \na _1212s1 \nSave and Close\nName apC 132 Input Board1-apC 2 \ntiesaipbon.\nPartition: \nGenets \n1-16 Inputs `1732 \nI \nA \nzj \nMain Wing \nr Bateman° Mode \nlepers 1 Goup 1 \nSupervised Inputs \n-%-e- Create es Louie -Li Delete 4. Twigs \nEdt \nbdex \nC408;Nred \nName \nTemplate \n1 \nF \napC Inpu t-apC 132 Input Board l-apC 2 \nF \napC Inpu2-apC 132 Input Bowdl-apC 2 \n3 \nF \napC Ing43-apC 132 Iript4 Boardl-apC 2 \n4 \nF \napC Input4-apC 132 Input Boardl-apC 2 \n5 \nr \nacc Inpti5-apC 132 kta Boardl-apC 2 \n1 \n... \n6 \nr \napC Ing46-apC 132 kilt Boardl-apC 2 \napC Ilya Template... \n7 \nr \napC Input7-apC 132 Input Boardl-apC 2 \napC File Template... \n8 \nr \napC Input8-apC 132 Inca BoardlopC 2 \napC Input Template... \n9 \nr \napC IrextBapC 132 Input BoardlepC 2 \neepC Irput Template... \nr \nepC Input10-apC 132 Fput Board1-apC 2 \napC °put Template.. \nr \napC Iput11-apC 132 Irput Board lopC 2 \napC Input Template.. \nr \napC Iput12epC 132 Irput Board1opC 2 \napC Input Template... \nr \napC Input13-apC 132 Irput Board1opC 2 \napC Input Template.. \n14 \nr \napC Irext14-apC 132 Irput Board1opC 2 \napC Input Template.. \n15 \nr \napC Inixt15-apC 132 Input Board1opC 2 \napC Input Template \n16 \nr \napC Inputlf.apC 132 Input Board1opC 2 \napC Input Template...\nThe apC Input General tab, as shown in Figure 132 on Page 360, displays the Input Location - Controller, \nBoard and Connection fields. These are read-only fields that display the apC panel, the apC Add-On Board and \nInput Number associated with an 132 Supervised Input. These fields locate the Input that you have chosen to \nconfigure. \n2. To configure the Inputs on the I32 Input Board - 1-16 Inputs tab, follow the instructions given in To Configure \napC Controller Inputs on Page 322. \n3. Navigate to the 17-32 Inputs tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n359 \nEFTA01226290\n", "char_count": 1962}, {"efta_number": "EFTA01225932", "page_number": 359, "text_content": "apC Input Board Editor (132 and 18) \nFigure 132: apC Controller 132 Add-On Board 1-16 Inputs General Tab \nU\n \nepC Input - apC Input 1-apC I32 Input Boardl-apC 2 \nA Save and Close \na2ci \nName: \nEiescription. \ntr. \n• \nr..c 6 \naoC \n11.7.  Enabled \nr tAaintenance Mode \nPartition: Maki Wing \nGeneral I Timers I Gays I Status I User Defined Reads I State images I \nIdentification \nOptions \nDefault State \nfpntroller: 'apC-1 \nBooed. 'apC 132 Input BoardlnpC 2 \nType: 'General \n/Assigned to: I \nConnection: Pro_t 1 \n17 Supervised \nF Send at/Andaman jo monitoring station \n17 Send state chances to journal \nr Activate on Supervision Error \nF Armed \nA \napC 132 Input Board 17-32 Inputs Tab \nThe apC 132 Input Board 17.32 Inputs tab allows you to add 16 Supervised Inputs on the 132 Inputs Board (Board \nIndex 1). \n360 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226291\n", "char_count": 876}, {"efta_number": "EFTA01225932", "page_number": 360, "text_content": "ape Input Board Editor (132 and 18) \nTo Configure the 17.32 Inputs Board \n1. To configure the 17-32 Supervised Inputs, select the check box in the Configured column in the apC Add-On \nBoard - 132 Input Board - 17-32 Inputs tab (see Figure 133 on Page 361) and click CI located in the Edit column \nof the Supervised 132 Input Board box to display the apC Input (Index Numbers 17 through 32)132 Input \nBoardl General tab (see Figure 108 on Page 326). \nFigure 133: apC Contrast 132 Add-On Board 17-32 Inputs Tab \nyW apC 132 Input Board - apC 132 Input BoardI.-apC 2 \nSave and Close \napC 132 Mott Boardl-apC 2 \nPartition. Main Wog \nr Maintenance Mode \nGenera 1.16 Inputs 17-32 16441 'Gimp I \nSupervised Inputs \nCreate AP Inputs \nDelete Al Irputh \nEdt \nIndex \nelnalled \nName \nTanulate \n17 \nr \napC Inpt117-apC 132 hput Board1-apC 2 \nIVA t \niii \n•-• \n18 \nr \napC Input18-apC 132 frout B6601-apC 2 \nInput terngkite 1 [D... \n19 \nr \napc Ing4.419-apC 132 tout Board1-apC 2 \nIngot template 1 [D... \n21) \nr \napc Input20-apC 132 Input Boardl-apC 2 \nkat template 1 [D... \n21 \nr \napC Input21-0C1321nput Boardl-apC 2 \nInput template 1 (IL. \n22 \nr \napC Input22-apC 1321rput Board1-epC 2 \nIrput template 1 (IL. \n23 \nr \napC Inp123-apC 132 kat Board1-apC 2 \nIrptil template 1 [IL. \n24 \nr \napC Inp.424-apC 132 hoot Boesd1-apC 2 \nIrput template 1 [IL. \n25 \nr \napC Inp12.5apC 132 Irpot Board1-apC 2 \nIran template 1 [D... \n26 \nr \napC InpU2frapC '32 Input BoadbapC 2 \nbpi template 1 [IL. \n27 \nr \napC Inp127.apC 132 I-put BoardVapC 2 \nInput template 1 [D... \n28 \nr \napC Input28.apC I32 Fput BoardtapC 2 \nInput template 1 [IL. \n29 \nIP \napC Inixt29.apC 132 I-put Boardt.apC 2 \n30 \np \napC Inixt30apC '32 Irput Board1apC 2 \n31 \nP \napC Input31-apC 132 Input Board1.apC 2 \nP \napC Inptt32,apC 132 i-put Coarc11.apC 2 \n2. To configure the Inputs on the 132 Add-On Board - 17-32 Inputs tab, follow the instructions given in To \nConfigure apC Controller Inputs on Page 322. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n361 \nEFTA\n... [truncated, 2009 chars — for the full page use /api/corpus/document/EFTA01225932/360 or ?id=EFTA01225932&page=360]", "char_count": 2009}, {"efta_number": "EFTA01225932", "page_number": 361, "text_content": "apC Input Board Editor (132 and 18) \nFigure 134: apC Controller 132 Add-On Board 17-32 Inputs General Tab \nU\n \nepC Input - epC Input 17-apC 132 Input floardl-a pC 2 \nSave and Close \n.acJJ \nName: \ngescription. \nHI.7 Enabled \nr tAaintenance Mode \nPartition: Man %sting \nGeneml 'Triggers' Status' User Defined Fields' State images \nIdentification \nOptions \nDefault State \nfpntrollet: \n&art \nType: \nAssigned to: \nConnection: \nlapC-1 \nIapC 132 hput Boartl-apC 2 \nheneral \nPrime 17 \n17 Supervised \nrI•o Send state changes p monitoring saltine \nr7 Send state changes to journal \nr Activate on Supervision Error \nr \nArmed \napC 18 Input Board General Tab \nYou can also add-on up to 64 Supervised Inputs (8 Inputs available on 8 18 Input Boards) with Triggers available for \neach input. \n362 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226293\n", "char_count": 849}, {"efta_number": "EFTA01225932", "page_number": 362, "text_content": "apC Input Board Editor (132 and 18) \nTo Configure the 18 Input Board \nI. To configure an IS Input Board, select the check box in the Configured column on the apC Add-On Board -\nInput Boards tab and click 0 \nlocated in the Edit column of the Supervised 18 Input Board box to display the \napC I8 Input Board - General tab (see Figure 135 on Page 363). \nF Ig u re 135: apC Controler18 Add-On Board18 InputsGeneralTab \nICY apC IB Input: • . . \n. \n,\nAdd-apc test\n_ Ir 121 \nSave and Close \nName I..0 18 In. Boardl-a.0 Add-a. test \nPescription \nPartition \nGeneral I Gap I \n_J \n_I \nlain Wing \nF Maintenance Mode \nI \n—Location \nController: lapC•1 \nBoard. lapC Add-apc test \nBOW Index Ii \n—Supervised Inputs \nii i\n-- Create AI Ingots _ Dekte All Inputs \nsae \nI index \nI Corttned \ntime \nI Tardate \n1 \nr \napC ktutt-aoCII3 hoot Boardl-e0C Aid... \n2 \nn \napC Input2-apC18 hput Board' apC Pdd... \n3 \n0 \napC hput3cpCI8 hput Board1cpC Add... \n4 \nri \napC hput4cpC I8 bout BoardhapC Add... \n5 \n0 \napC Input5cpC18 hput Board1 -apC Add... \n0 \napC Input6cpC18 bout Board1 apC Add... \nM \napC Input7cpC18 hput Board1 cpC Add... \n8 \nr \napC IrotItepC18 Input %St 'IOC Md... \nStage Inputs \n17  Create AI Inputs \nErg \nInsults* \nI Certgued \n1 Name \nI Terrciate \nTamper \nFr \nTamperapC 18 Input BoantletpC Addeo... \n... \nCormnricati... \nFr \nCommuncton falureapC18 Input Boar.. \nM_ \n2. To configure Inputs, select the check box in the Configured column in the apC 18 Inputs tab and c wk \nlocated in the Edit column to display the apC Add-On Board - apC 18 Input Board - General tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n383 \nEFTA01226294\n", "char_count": 1622}, {"efta_number": "EFTA01225932", "page_number": 363, "text_content": "apC Input Board Editor (132 and 18) \n3. To configure the Inputs on the 18 Add-On Board - 18 Inputs tab, follow the instructions given in To Configure \napC Controller Inputs on Page 322. \nThere are also two Status inputs available for the 18 Input Board: \n■ Board Tampered, which indicates tampering with the Add-On Board \n■ Communications Fail, which detects a communications failure. \n4. Once you have finished reader the 18 Inputs, click Save and Close. \n384 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226295\n", "char_count": 528}, {"efta_number": "EFTA01225932", "page_number": 364, "text_content": "apC Star Coupler Board Editor \napC Star Coupler Board Editor \nThe apC Star Coupler Board Editor is used to configure apC Star Coupler boards. \nStar Couplers are single expansion boards that attach to the apC/8X or apC to allow the RM readers, 1/8 inputs, \nand R/8 outputs to be wired in a Star topology. The Star Coupler Board allows addition of: \n• 8 MRM/RM Reader ports \n• 8 Unsupervised Inputs \n• 8 dry contact, form C, relay Outputs \nThe Star Coupler can be installed on apC and apC/8X panels. For more information, see the Star Coupler - Mini Star \nCoupler Quick Start Installation Guide. \nThis editor is accessed from the apC Add-on Board Editor Star Coupler tab (see apC Add-On Board Star Coupler Tab \non Page 354). \nTo Configure the Star Coupler Board \n1. To configure the Star Coupler Board, select the check box in the Configured column in the apC Add-On Board \nStar Coupler tab and click \nlocated in the Edit column of the Star Coupler box (see Figure 129 on Page 355) \nto display the Star Coupler General tab, as shown in Figure 136 on Page 365. \nThe apC Star Coupler Board General tab displays three read-only fields: \n— \nController \n— \nBoard \n— \nBoard Index \nThese fields are located on the Star Coupler that you have chosen to configure. As you configure more Add-On \nBoards for this controller, the Board Index field will reflect each placement, to differentiate board locations. \nFigure 136: apC Star Coupler General Tab \nI. Star Coupler Star \nStar Coupler -apC Add • \n\"43ve end Cole \nWas \n9.1100beci \nStar Coorler•e0C 44J \n' • \nRea:leir Untweivned Irotts Woos \nLoftier \n!lard \nBfrudInCe. \nKC Ex • CoomA • RE RI \n2. Click the Readers tab to configure the Star Coupler readers. See Star Coupler Readers Tab on Page 366 for the \nStar Coupler Readers tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter? \n365 \nEFTA01226296\n", "char_count": 1841}, {"efta_number": "EFTA01225932", "page_number": 365, "text_content": "apC Star Coupler Board Editor \n3. Click the Unsupervised Inputs tab to configure the Star Coupler unsupervised inputs. See Star Coupler \nUnsupervised Inputs Tab on Page 367 for the Star Coupler Unsupervised Inputs tab. \n4. Click the Outputs tab to configure the Star Coupler outputs. See Star Coupler Outputs Tab on Page 367 for the \nStar Coupler Outputs tab. \n5. When you have completed configuring the Star Coupler and its attached devices, you can click Save and Close \nto save your changes. \nStar Coupler Readers Tab \n11w Star Coupler Readers tab allows you to configure the readers connected to your Star Coupler. \nTo Configure Star Coupler Readers \n1. Navigate from the apC Controller Add-On Board Tab on Page 324 to the apC Add-On Board Star Coupler Tab on \nPage 354 \n2. Click Star Coupler to open the apC Star Coupler Board Editor on Page 365. \n3. Click the Readers tab to configure readers for the Star Coupler. Refer to the Figure 137 on Page 366 for an \nexample of the Star Coupler Readers tab. \nFigure 137: apC Controller Star Coupler Readers Tab \nStar Coupler Star - Star Coupler-apC Add-apC RE 2 \n_ , \nX \n45ave and Close \nname \n12e:croon \nSq. Cogielace Addwe RE 2 \nGentle/ Readal UnA4xAuedInAn: Out;a: \nkArs \n00403 All Readers \n(dr \nInk \nCafigure0 \nNam, \nTercide \n2 \n4 \n5 \n6 \n0 \n0 \n0 \n2 \nCI \napC Readed Slav C000kraoC AdJaoC \nape ReAft42.SIA CoupitraoCAdiaoC \napC ReadoZSim Cadet-44'141*C \napC ReadontSial CadxapCAddapC \napC Rsacle5.5i4. CoupleruoCAdtacC \napC Reaclet6Siet CovplineCROOAPC \napC Readenis Cais*-soCAdi-toC \nicc Read& e-Siro CoupleproC Add apt \n4. To create all available readers for the Star Coupler, click Create All Readers. apC Readers that have previously \nbeen created on other board connections are unavailable (shaded gray) to be created here. \n5. To create an individual reader, select the check box in the Configured column for the Star Coupler Readers \n(Index 1 through 8) and click EI located in the Edit column. The apC Reader Editor opens to allow you to \ncon\n... [truncated, 2169 chars — for the full page use /api/corpus/document/EFTA01225932/365 or ?id=EFTA01225932&page=365]", "char_count": 2169}, {"efta_number": "EFTA01225932", "page_number": 366, "text_content": "apC Star Coupler Board Editor \n6. When you have finished creating and configuring readers for the Star Coupler, you can click Save and Close to \nsave your changes. \nStar Coupler Unsupervised Inputs Tab \nThe Star Coupler Unsupervised Inputs tab allows you to configure the inputs connected to your Star Coupler. \nTo Configure Star Coupler Unsupervised Inputs \n1. Navigate from the apC Controller Add-On Board Tab on Page 324 to the apC Add-On Board Star Coupler Tab on \nPage 354, and click Star Coupler to open the apC Star Coupler Board Editor on Page 365. \n2. Click the Unsupervised Inputs tab to configure Unsupervised Inputs for the Star Coupler (see Figure 138 on Page \n367). \n3. To create all Unsupervised Inputs for the Star Coupler, click Create All Inputs. \n4. To create an individual input, select the check box in the Configured column for the Star Coupler Inputs (Index \n9 through 16) and click GJ located in the Edit column. The apC Input Editor opens to allow you to configure \nthis input. See apC Input Editor on Page 332 for details on configuring an apC Input \nFigure 138: apC Controller Star Coupler Unsupervised Inputs Tab \nta Star Coupler Star - Star Coupler-apC Add-apC RE 2 \nI X \n-2 .one and Close \nSear CooleeseC AddaPC RE 2 \nfree! Template 1 peed lot Index10.16 \nlinteatented Irene Duna: \n;I. liTA.kt \nDelete All Irpas \nName \nIsPA9Slat CaokseeCAddePC R \nIOC Stud OSte CmeametAdect \napC 'spat 1 des Cowered Aeeent \n.,CC 'spud 24let CosplerapC AddeeC \nfC Iseult 3Ste Caelitea AddepC \n-cC  \nCoanalliC AdclepC \ncop Impel &Ste CoutlenatCAdeleOC\n*CW0,116414 Caslet -.1pC Add q:C \nTeepee \nepC Ira+ \n0 \nasp Iroul T mete_ \napC Input TempLat \nart Iroul Tempe.. \ntOC Wool Tenet. \ntope Iron er r gist .. \napC Iroul Tepplet.. \n5. When you have finished creating and configuring inputs for the Star Coupler, you can click Save and Close to \nsave your changes. \nStar Coupler Outputs Tab \nThe Star Coupler Outputs tab allows you to configure the outputs connected to your Star Coupler. \nC•CURE\n... [truncated, 2065 chars — for the full page use /api/corpus/document/EFTA01225932/366 or ?id=EFTA01225932&page=366]", "char_count": 2065}, {"efta_number": "EFTA01225932", "page_number": 367, "text_content": "apC Star Coupler Board Editor \nTo Configure Star Coupler Outputs \n1. Navigate from the apC Controller Add-On Board Tab on Page 324 to the apC Add-On Board Star Coupler Tab on \nPage 354 \n2. Click Star Coupler to open the apC Star Coupler Board Editor on Page 365. \n3. Click the Outputs tab to configure outputs for the Star Coupler (see Figure 138 on Page 367). \nFigure 139: apC Controller Star CouplerCutouts Tab \nci Star Coupler Star - Star Coupler-apC Add-apC RE 2 \nX \nNew [51es CoatreiCAddePC RE 2\naeide6:a \n \n :1 \nGeneral ReAlava Uravervited Input 0trieor \n(Airrir \nGreate All CaarputS \nDelete All CuTuts \nEdt \nleder* \ned \nNave \nTemplet. \na \nO \nO \nO \nare 0.APASSies CouebkirekklatiC \napC NOM e‘Sun Couobi4oCAdclief \napC GUIDLA11 Srai Cour*, aoC Add act \nI \narerC 0Arraul12.Star CouralerA;C Add net \napC °Argil IStar CouplecraaC eutdapC \napC Gips° IrSter CorykaracC AS\nO \n. 45C 0dputISSIzi CatOnOCAdd414-. \n0C Chiptal 64lai CotaleCCAddAtt.. \nTo create all outputs for the Star Coupler, click Create All Outputs. \n5. To create an individual output, select the check box in the Configured column for the Star Coupler Outputs \n(Index 9 through 16) and click GJ located in the Edit column. The apC Output Editor opens to allow you to \nconfigure this output. See apC Output Editor on Page 336 for details on configuring an apC Output \n6. When you have finished creating and configuring outputs for the Star Coupler, you can click Save and Close to \nsave your changes. \n388 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226299\n", "char_count": 1538}, {"efta_number": "EFTA01225932", "page_number": 368, "text_content": "T riggers Tab for apC Devotes \nTriggers Tab for apC Devices \nC•CURE 90(10 uses Triggers, which are configured procedures for activating actions, to activate Events or Outputs \nfor an apC device. A Trigger automatically executes a specified Action when a particular Condition occurs (when the \nobject Property specified in the Trigger reports the Value specified in the Trigger).Navigate to the Triggers tab. \nFigure 140 on Page 369 shows the Triggers tab for an apC Input, which is typical for an apC device. \nFigure 140: Type:4140C Triggers Tab \nGenera Texea I Goal Ass l Usa Odried Cekle l %se eucae \n'.Rdlli0Vt \nHwy \nIktni Stles• \nA triggers tab provides you with the ability to define the activation/deactivation, enable/disable, and arm/disarm, \netc. of such objects as: events, inputs, outputs, camera actions, door status changes, etc. Triggers can also be used to \nlaunch imports and exports, email and reports, viewer and message displays, personnel ID number state changes, \ncontroller downloads, sound activation, communication notifications, etc. \nTable 83 on Page 370 provides an example of a configured apC Trigger. \nC•CURE 9000 Hardware Configuration Guide \nChapter? \n369 \nEFTA01226300\n", "char_count": 1201}, {"efta_number": "EFTA01225932", "page_number": 369, "text_content": "Triggers Tab for apC Devices \nTable 83: Triggers Tab Settings Example \nThe following Triggers Tab settings: \nProperty \nValue \nAction \nDetails \nSchedule \nTime Zone \nActive Status \nActive \nActivate Event \napC Input Event \nAlways \n(Time Zone of apC or C•CURE 9000 \nServer) \nWould create the following Trigger: \nAny time (Always Schedule) the Active Status (Property) equalsActive (Value), activate the event (Action) named STAR Input Event (Details). \nSTAR Input Event isan Event that you would need toareate using the Event Editor. \nFrom the Triggers tab of an apC device (such as a Controller, Input, or Reader), you can perform the following tasks. \n■ Defining a Trigger for an apC Device on Page 370. \n■ Removing a Trigger on Page 272. \napC Triggers Tab Definitions on Page 371 provides definitions for the fields and buttons on an apC Device Triggers \ntab. \nDefining a Trigger for an apC Device \nYou can use the Triggers tab to define a Trigger for an apC device. The typical usage for an apC Trigger is to activate \nan Event or an Output as the result of a state change of an apC device Property. \nThis tab provides you with the ability to define the activation/deactivation, enable/disable, and arm/disarm, etc. of \nsuch objects as: events, inputs, outputs, camera actions, door status changes, etc. Triggers can also be used to launch \nimports and exports, email and reports, viewer and message displays, personnel ID number state changes, controller \ndownloads, sound activation, communication notifications, etc. \nExample: \nWhen an apC Tamper Input changes from the Inactive (normal) to Active (abnormal) state, you wish to activate \nan Event and activate an audible alarm (an apC Output). \nTime Zones for apC Panel Triggers \nIf you specify a Time Zone in your Trigger definition, you can control when the Schedule for the Trigger is active. \nYou can only select the C•CURE 9000 server Time Zone or the Time Zone of the apC panel you are editing. \nExample: \nIf you have apC panels that are in \n... [truncated, 2740 chars — for the full page use /api/corpus/document/EFTA01225932/369 or ?id=EFTA01225932&page=369]", "char_count": 2740}, {"efta_number": "EFTA01225932", "page_number": 370, "text_content": "-DiggersTab for apC Devices \nTo Define a Trigger for an apC Device \n1. Click on the Triggers tab for your apC device. \n2. Click Add on the Triggers tab to create a new Trigger. \n3. Click 0 \nwithin the Property column to open the Property dialog box showing the Properties available for the \ndevice. \n4. Click a Property in the list to select it and add it to the Property column. \n5. Click 0 \nwithin the Value column to display a drop-down list of Values associated with the Property that you \nhave selected. Click a Value that you want to include as a parameter for the trigger to add it to the column. (If \nthere is no set list of Values, you can type in a Value.) \n6. Click 0 \nwithin the Action column to display a drop-down list of valid actions. Click an Action that you want \nto include as a parameter for the trigger to add it to the column. \n7. When you select an Action, the lower pane in the Triggers box displays an entry field or group of entry fields, \nspecific to the selected Action, so that you can configure the Details for the Action. \n8. Once you define the Action details, the Details column displays information about how the Action has been \nconfigured. \nFor example, if an Event field is displayed in Details, you can click to select an Event that you want to associate \nwith the Trigger. \n9. If the Triggers tab includes a Schedule column, click within the Schedule column to display a drop-down list of \npre-configured schedules. Click 0 \nto select a Schedule that you want to associate with the trigger. Schedules \nare created in the Configuration Pane. See the C•CURE 9000 Software Configuration Guide for more information. \n10. If the Triggers tab includes a Time Zone column, click within the Time Zone column to display a drop-down \nlist of available Time Zones. If the Time Zone column is blank, or you do not select a Time Zone, the Time Zone \nof the C•CURE 9000 server is used by default \n11. Click Save and Close to save the apC trigger. \nNOTE \nTriggers related to a\n... [truncated, 2560 chars — for the full page use /api/corpus/document/EFTA01225932/370 or ?id=EFTA01225932&page=370]", "char_count": 2560}, {"efta_number": "EFTA01225932", "page_number": 371, "text_content": "Triggers Tab for apC Devices \nTable 84: apC Triggers Tab Definitions (continued) \nField/Button \nDescription \nProperty \nClick with in the Property column, and then click ri.\n The Property browser opens presenting properties available for the \nComm Port. Click a Property to select it and add it to the column. \nValue \nClickwithin the Value column to display a drop-down list of Values associated with the Property that you have selected. Click a \nValue that you want to include as a parameter for the trigger to add it to the column. \nAction \nClick(] within the Action column to display a drop-down list of valid actions. Click an Action that you want to include as a \nparameter for the trigger to add it to the column. \nAs you select an Action, a corresponding entry field, or group of entry fields, appear at the bottom of the dialog box. \nClick to select entries for these fields. \nDetails \nDisplays details about how the Action was configured. \nSchedule \nClickwithin the Schedule column to select a Schedule. \nClick [ ... 1to select a Schedule that you want to associate with the trigger. Schedules are created in the Configuration Pane. \nRefer to the C•CURE 9000 Software Configuration Guide for more information on creating Schedules. \nTime Zone \nClick with in the T line Zone column to select a Time Zone for Schedule activation. \nClick El to select a Time Zone that you want to associate with the trigger Schedule.lf you speedy a Time Zone, the Schedule \nstart and end times are calculated using that Time Zone. For example, a Schedule that becomes active at 3:00 AM would \nbecome active at 3:00AM in the Pacific Time Zone, if that Time Zone was specified. Refer to the C•CURE 9000 Software \nConfiguration Guide for more information on Time Zones. \n372 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226303\n", "char_count": 1827}, {"efta_number": "EFTA01225932", "page_number": 372, "text_content": "Mini Star Coupler Board Editor \nMini Star Coupler Board Editor \nMini Star Couplers are single expansion boards that attach to the apC/8X or apC panels to allow the RM readers to \nbe wired in a star topology. For more information, see the Star Coupler - Mini Star Coupler Quick Start Installation \nGuide. \nNOTE \nMini Star Coupler Boards have not been evaluated by UL and cannot be used in UL Listed \napplications \nTo Configure the Mini Star Coupler Board \n1. To configure the Mini Star Coupler Board, select the check box in the Configured column in the apC Add-On \nBoard - Star Coupler tab and click \nlocated in the Edit column of the Star Coupler box (see Figure 129 on \nPage 355) to display the Mini Star Coupler - General tab, as shown in Figure 141 on Page 373. \nThe Mini Star Coupler Board - General tab (see Figure 141 on Page 373) displays three read-only fields: \n— \nController \n— \nBoard \n— \nBoard Index \nThese fields are located on the Mini Star Coupler that you have chosen to configure. As you configure more Add-\nOn Boards for this controller, the Board Index field will reflect each placement, to differentiate board locations. \nFigure 141: apC Controler Add-On Board Mini Star Coupler General Tab \nOFirr:lar \nMrin Star p r \nId \nRat \naelatibre \nnresel Readors I \nI xion \nacC WCamA -RE Ill \neoCAOS \n2. Click the Readers tab to configure readers for the Mini Star Coupler. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n373 \nEFTA01226304\n", "char_count": 1456}, {"efta_number": "EFTA01225932", "page_number": 373, "text_content": "Mini Star Coupler Board Editor \nFigure 142: apC Controller Add-On Board Mini Star Coupler Readers Tab \nNaYt MnSisinC Added RE 2 \nlesocign \nGee s \nRadice: \n,a10803  All Readers \nDOW N Reader \nES \nIran \nCcinVal \ntime \ntenon \n \nI\n \nK \n \napC lindal. I A riStwapC A61 acC RE 2 \n \n12 \n0 \nCC Reede•24InStetCC Added RE 2 \nO \naPC Rndielain9r.apt 46$44 RE 2 \ntcC Readecliln 94.4:C Adel ccC RE 2 \n \n5 \nO \nsC ReedeoMnStewoC iviSeoC RE 2 \n \nG\nK\ntpC ReadafAlii StaraKAddart PI 2 \nEl \nICC P!.:4044r•StwatiCAddipC RE 2 \ntc.0 fte.6AMn•StaracCA6ivirk PC 2 I \n3. Select the check box in the Configured column for the Mini Star Coupler Readers (Index 1 through 8) and click \nlocated in the Edit column to display the Mini Star Coupler Readers - General tab, shown in Figure 143 on \nPage 374. \nThe 8 available Mini Star Coupler Readers allow up to 2 Supervised Inputs and 2 Outputs. For further \ninstructions for reader readers, see To Configure an apC Reader on Page 323. \nNOTE \nReaders that are unavailable (see Figure 142 on Page 374) have already been configured on the \napC panel Readers tab. \nFigure 143: apC Controller Add-On Board Mini Star Coupler Readers General Tab \ntin \nner \nCoca:a \nFlEmblea \nP.eonn \nhat \n(ens*. \n<OC ft< Um C. PE M1 \npas frnSisIPC\nAr•Zed l) \nCcreocia, Pa* \nReukt.toe \nRM \n°elan. \n4. Click Save and Close to return to the apC Controller - Add-On Board - Star Coupler tab. \n374 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226305\n", "char_count": 1453}, {"efta_number": "EFTA01225932", "page_number": 374, "text_content": "Mini Star Coupler Board Editor \nBe sure that the Mini Star Coupler Board is installed correctly on the apC or apC/8X. For more information, see \nthe Star Coupler - Mini Star Coupler Quick Start Installation Guide. \n5. Click Save and Close to return to the apC Controller - Add-On Board tab. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n375 \nEFTA01226306\n", "char_count": 363}, {"efta_number": "EFTA01225932", "page_number": 375, "text_content": "WK:gand Proximity Star Coupler Editor \nWiegand Proximity Star Coupler Editor \nThe Wiegand/Proximity Star Coupler (WPSC) consists of a two board set that attaches to the apC or apC/8X to \nallow direct connection of up to 8 read heads using Wiegand signaling. The WPSC board set consists of a Lower \nBoard and an Upper Board. The Lower Board provides connections for 4 readers indexed 1.4 and 4 inputs indexed \n17-23. The Upper Board provides connections for 4 readers indexed 5.8 and 4 inputs indexed 25-31. \nWhen using the WPSC Add-On Board, the standard Star Coupler cannot be used because the WPSC board set \nattaches to the same bus connector as the Star Coupler. \nEach board provides one supervised input for each reader, which should be used in conjunction with one of the 8 \nsupervised inputs on the apC main board to provide a total of two supervised inputs for each reader. \nNOTE \nThe supervised inputs on the WPSC remain inactive in the Monitoring Station unless readers are \nconfigured in the WPSC editor. \nSince the WPSC board set does not provide output relays, it is recommended that the 8 on-board apC relays be used. \nFor more information, see the WPSC Quick Start Installation Guide. \nTo Configure the Wiegand/Proximity Star Coupler Board \n1. To configure the Wiegand/Proximity Star Coupler (WPSC) Board, select the WPSC check box in the Configured \ncolumn in the apC Add-On Board - Star Coupler tab and click 0 \nlocated in the WPSC Edit column of the Star \nCoupler box. \nThe Wiegand/Proximity Star Coupler Board General tab displays three read-only fields: \n— \nController \n— \nBoard \n— \nBoard Index \nThese fields are located on the Wiegand/Proximity Star Coupler that you have chosen to configure. As you \nconfigure more Add-On Boards for this controller, the Board Index field will reflect each placement, to \ndifferentiate board locations. \nFigure 144: apC Controls( Add-On Board Wiegand Proximity Star Coupler General Tab \n376 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \n\n... [truncated, 2013 chars — for the full page use /api/corpus/document/EFTA01225932/375 or ?id=EFTA01225932&page=375]", "char_count": 2013}, {"efta_number": "EFTA01225932", "page_number": 376, "text_content": "Wiegand Proximity Star Coupler Editor \n2. Click the Lower Board tab to display the 4 available WPSC Readers and 4 Unsupervised WPSC Inputs, as shown \nin Figure 145 on Page 377. \nFigure 145: apC Controls( Add-On Board WPSC Lower Board Tab \nStar Coupler WPSC - WPSC-apC Add-apC RE 2 \nkiln \nand Cbs• \n \n-u••=••••.-\nname \n9eximben \nWPSCA:CAdd.0 RE 2 \ntoy. Boyd um., goad.\n\u0013 Create All Readers \nDelete All Readers \n I2 \n I3 \n4 \nCcalared \nNee \nK \nsoC Reedet1M1250aci:AdlapC RE 2 \nK \naPC Reedet24F5C.acC AddecC RE 2 \nK \n4t/C Reals3AVF5C.acC AddeoC RE 2 \nK \neoC Reader4MFIC.apC M6coC RE 2 \nI 'noble \nwow.,:nitrolt \n•7  CI:E5305 All Irputs \nI:531595 Sl Ircuts \nEde \nIndex \n15 \n15 \n21\nConigkeci \nEl \n2] \nK \nK \nName \nTemplets \nad Inpol7WPSC.40C Rdtratt RE 2 \n4ot lia419WPSCatt Add-a/CCM 2 \ntot IroA2PAC'SCead AdeltC \n2 \nI-123 \n<a Ing.A234/F5C4KA.acC HE 2 \napC IrotA I cook/ \n3. Select the check box in the Configured column for the WPSC Readers (Index 1 through 4) and click 0 \nlocated \nin the Edit column to display the apC Readers - General tab, shown in Figure 146 on Page 378. \nYou can configure the reader keypad and triggers for each of the 4 available WPSC Readers. For further \ninstructions see apC Controller Readers Tab on Page 323. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n377 \nEFTA01226308\n", "char_count": 1304}, {"efta_number": "EFTA01225932", "page_number": 377, "text_content": "Wiegand Proximity Star Coupler Editor \nFigure 146: apC Controller Add-On Board WPSC Lower Board Reader General Tab \n/IS:fledOwe \nYoe anC finces.nnirCC rpC ArIcr \nattea. \nGerd\nEfatrof \nle \nC \n14(4/ItaX*1 \nCobalt \ngood \nAWN.. \nCCP.cato \nAmos Pse \nCos Corns \n?\n/[0:1 r.torown \nICC ([4•CoreA•RE RI \nNoscaccate\nRoth> 2 \nIlene \nCescrVon \n• \nS \n'dytpirti\n4. To configure Inputs, select the check box in the Configured column in the Wiegand/Proximity Star Coupler -\nInputs tab and click \nlocated in the Edit column to display the apC Add-On Board - Wiegand/Proximity Star \nCoupler Input - General tab, as shown in Figure 147 on Page 379. \n378 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226309\n", "char_count": 702}, {"efta_number": "EFTA01225932", "page_number": 378, "text_content": "Wiegand Proximity Star Coupler Editor \nFigure 147: apC Controller Add-On Board WPSC Lower Board Input General Tab \nn dr, Inpu \nInpull 9 Wind \nit\n4,C IroJ1SWPSCIpC \nac, OPX.• \nC`On\" \ncrypt Gaya 9$.a Slate nage \nI truer. \nift DC•COM A • RE ill \nttcl \nWPSC*CAdd-\n()Vern \nWog Stele \nDicsove TP...J11110 sect IOd \nSm. - \ndumps); aria. \nOa\" \nSand von chr91.10Pni \nE Adnalec. \nppnlm \nE hard \n5. To configure the Inputs on the Wiegand/Proximity Star Coupler Add-On Board - Inputs tab, follow the \ninstructions given in To Configure apC Controller Inputs on Page 322. \nC•CURE 9000 Hardware Configuration Guide \nChapter 7 \n379 \nEFTA01226310\n", "char_count": 631}, {"efta_number": "EFTA01225932", "page_number": 379, "text_content": "Wiegand Proximity Star Coupler Editor \nFigure 148: apC Controller Add-On Board WPSC Upper Board Tab \nirpothor \nWFSCapC Adtlap:C RE 2 \nCaramel Lcwo Bowl Um.\" Bcrd \ncreate All Readers ._ Dew All Readers \nEdt \nPew \n5 \n l7\nfB\nCoregkeed \nName \nad Reaclea5MF5C.acC Added RE 2 \nad Reaclea6MPSCapC Added RE 2 \napC fictlet7VPSC.coC Mind RE 2 \nK \n*DC Readei8WPSC.ecCActeeof RE 2 \nO \nTenpLse \nStsper.:NRcor: \nCoate AU [Matt \nDelete all InP.Ra \nEck \n25 \nas \nNape \nad Irput25w1:5C-acC AttpC RE 2 \nad Irps27-wP5C4oC A0PacC RE 2 \napC Irput29WPSCP0C A6PacC RE 2 \napt irput31-WPSC-KC AllPapC RE 2 \nImpale \n1 \n6. Click Save and Close to return to the apC Controller - Add-On Board - Star Coupler tab. \nBe sure that the Wiegand/Proximity Star Coupler Board is installed correctly on the apC or apC/8X. For more \ninformation, see the INPSC Quick Start Installation Guide. \n7. Click Save and Close to return to the apC Controller - Add-On Board tab. \n8. Click the Status tab to display it, as shown in Figure 108 on Page 326. \nClick Save and Close to return to the Hardware Pane and finish the apC Controller configuration later. \n380 \nChapter 7 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226311\n", "char_count": 1181}, {"efta_number": "EFTA01225932", "page_number": 380, "text_content": "8 \nConfiguring RM Reader LCD Messages \nThis chapter explains how to customize sets of LCD messages, such as \"Present Card\" or \"Access Granted,\" for your \nRM readers to meet the specific needs of your facility or site. \nIn this chapter \nReader LCD Message Set Overview \n382 \nReader LCD Message Set Editor \n383 \nReader LCD Message Set Tasks  \n388 \nChanging the Language for the Default RM LCD Messages  \n393 \nC•CURE 9000 Hardware Configuration Guide \nChapter 8 \n381 \nEFTA01226312\n", "char_count": 478}, {"efta_number": "EFTA01225932", "page_number": 381, "text_content": "Reader LCD Message Set Overview \nReader LCD Message Set Overview \nRM readers display LCD messages, such as \"Present Card\" or \"Access Granted\" to indicate different states to \ncardholders. You can customize sets of these messages to meet the specific needs of your facility or site. \nExample: \nYou could change the \"Access Granted\" message to \"Please Enter Now\". \nWhen you assign a set of messages to an iSTAR Controller or an apC Panel, all the RM readers on that controller use \nthose same messages. \nThe Reader LCD Message Set Editor allows you to configure message sets. You can also use the Reader LCD \nMessage Set Editor to change the language in which your messages appear. See Changing the Language for the \nDefault RM LCD Messages on Page 393. \nNOTE \nOnly ASCII characters 0 to 125 are supported for display on the RM Reader. \n■ There are 94 printable characters. (Code 1 to 31 are non-printing, mostly obsolete characters that \naffect how text is processed.) \n■ No accented characters are supported. \n382 \nChapter 8 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226313\n", "char_count": 1081}, {"efta_number": "EFTA01225932", "page_number": 382, "text_content": "Reader LCD Message Set Editor \nReader LCD Message Set Editor \nThe Reader LCD Message Set Editor, shown in Figure 149 on Page 383, lets you create and modify message sets in \nC•CURE 9000 containing replacement texts for the LCD messages that display on the RM Readers. In addition, the \neditor lets you set the way that the date and time display on the Reader. The Reader LCD Message Set Editor has \nonly one tab—the General tab. For more information, see: \n■ Accessing the Reader LCD Message Set Editor on Page 383 \n■ Reader LCD Message Set Definitions on Page 384 \n■ Creating a Reader LCD Message Set on Page 388 \nAccessing the Reader LCD Message Set Editor \nYou access the Reader LCD Message Set Editor from the C•CURE 9000 Hardware pane. \nTo Access the Reader LCD Message Set Editor \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Right-click the Hardware Folder, click Reader LCD Message Set, and click New on the sub-menu that appears, \nas shown in Figure 149 on Page 383. (Once you have created a message set, a Reader LCD Message Set folder \nappears in the Hardware Tree.) \nFigure 149: Hardware Tree Reader LCD Message Sets \n- Or - \nClick the Hardware drop-down list and scroll down to select Reader LCD Message Set. \nISC kid \nISC Rex* \n• \niSTAR AO1Bowd \n3 ,ITTAR\nAR CHM \nDolce Pat \n.STAR ROA \n6TAR Poi Board \n'STAR O.tat Board \n.STAR Ruda \nClick Pi m to open a Dynamic View showing a list of all existing Reader LCD Message Sets, right-click the \nReader LCD Message Set you want to change, and click Edit from the context menu that appears. \nThe Reader LCD Message Set Editor opens with the General tab displayed, as shown in Figure 150 on Page \n384. \nC•CURE 9000 Hardware Configuration Guide \nChapter 8 \n383 \nEFTA01226314\n", "char_count": 1767}, {"efta_number": "EFTA01225932", "page_number": 383, "text_content": "Reader LCD Message Set Editor \nFigure 150: Reader LCD Message Set Editor \n1:1Sfrea aniCke. k:Ses artily \nli n \nkelathiN \nP__ \nOdes \nDor \n.44.0P/M\",-\nIn \n12 \nv \nRv Cbck \nMassage Na. \nAccret great \nMessase Tail \nACCESS GR:NTED \narV.C;iPaN \nINTER Pri \nINTER NEM CARD \ntill.0O ED \nPLEASE Vali \nWAJI Ift6V \nReader LCD Message Set Definitions \nThe Reader LCD Message Set Editor has the buttons described in Table 85 on Page 384 and the fields shown in \nTable 86 on Page 384. 'Fable 87 on Page 385 has detailed information about each of the 34 messages that can be \ncustomized for a message set. \nTable 85: Reader LCD Message Set Editor Buttons \nButton \nDescription \nSave \nand \nClose \nClick this button when you have completed changes to the Reader LCD Message Set and wish to save those changes. The Reader \nLCD Message Set Editor closes. \nSave \nand \nNew \nClick this button when you have completed any changes to the Reader LCD Message Set and wish to save those changes and also \ncreate a new Reader LCD Message Set. The message set you were editing is saved, and a new Reader LCD Message Set opens \n(either blankor including template information if you were using a template to create the message set). \nthis button when you want to close the Reader LCD Message Set Editor without saving your changes. \nAwarning appears asking whether or not you want to save your changes before closing the editor. Click Yes to exit and save and No to \nexit and cancel your changes. \nin\nClick \nTable 86: Reader LCD Message Set Editor- General Tab \n384 \nChapter 8 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226315\n", "char_count": 1599}, {"efta_number": "EFTA01225932", "page_number": 384, "text_content": "Reader LCD Message Set Editor \nReader LCD Message Set Editor - General Tab (continued) \nField/Button \nDescription \nDescription \nEnter a brief description for this Reader LCD Message Set. \nPartition \nThis read-onty field identifies the Partition to which this Reader LCD Message Set belongs. (This field is visible onty if the \nC•CURE 9000 system is partitioned.) \nDisplay Formats \nDate \nSelect the format for the date display: MM/DD/YY (the default) or DD/MM/YY \nTime: Hour \nClack \nSelect the format for the time display: 12 hour (the default) or 24 hour. \nMessages \nMessage \nName \nName of the Reader LCD Message string. \nMessage Text \nDefault text for the Reader LCD Message. \nTable 87: Reader LCD Messages \nMessage \nName \nMessage Text \nDescription \niSTAR \nUses \napC \nUses \nAccessgranted \nACCESS \nGRANTED \nAdmit text-general use \nYes \nYes \nAccessdenied \nACCESS DENIED \nReject text-general use \nYes \nYes \nEnter PIN \nENTER PIN \nEnter PIN prompt-general use \nYes \nYes \nEnter next card \nENTER NEXT \nCARD \nEnter next card prompt-used for occupancy and visitor/escort features \nYes \nYes \nUnlocked \nUNLOCKED \nDoor unlocked mode text-general use \nYes \nYes \nPlease wait \nPLEASE WAIT \nText displayed while access decision pending-general use \nYes \nYes \nWait-busy \nWAIT -BUSY \nText displayed when door busy processing a previous access-general use \nYes \nYes \nEnter floor \nENTER FLOOR \nape display for elevator admit-general use \nNo \nYes \nReader not \nready \nREADER NOT \nREADY \nText displayed when reader disabled-general use \nYes \nYes \nPresent card \nPRESENT CARD \nLocked Door mode text-general use \nYes \nYes \nEnter command \nENTER \nCOMMAND \nIntrusion entrance delay text-intrusion zone feature \nYes \nNo \nC•CURE 9000 Hardware Configuration Guide \nChapter 8 \n385 \nEFTA01226316\n", "char_count": 1763}, {"efta_number": "EFTA01225932", "page_number": 385, "text_content": "Reader LCD Message Set Editor \nReader LCD Messages (continued) \nMessage \nName \nMessage Text \nDescription \niSTAR \nUses \napC \nUses \nMisread card \nMISREAD \nVisitor/escort misread card feedback text-visitor/escort feature \nYes \nNo \nAli secure \nALL SECURE \nIntrusion zone all inputs secure text-intrusion zone feature \nYes \nNo \nExit now \nEXIT NOW \nIntrusion exit delay text-intrusion zone feature \nYes \nNo \nReady to arm \nREADY TOARM \nIntrusion zone ready to arm status text-intrusion zone feature \nYes \nNo \nNot ready to arm \nNOT READY TO \nARM \nIntrusion zone not ready to arm status text-intrusion zone feature \nYes \nYes \nDoor in alert \nDOOR IN ALERT \nSTAR reader tampered text. or apC reader tamper or door held forced \nopen text-general use \nYes \nYes \nArea armed \nAREAARMED \nIntrusion zone armed mode text-intrusion zone feature \nYes \nYes \nArea disarmed \nAREA DISARMED \nIntrusion zone disarmed mode text-intrusion zone feature \nYes \nYes \nSecure pending \nSECURE \nPENDING \nIntrusion zone disarm pending text-intrusion zone feature \nYes \nNo \nSecure \nSECURE \nDoor secure mode text-general use \nYes \nYes \nKeypad \nCommand \nIssued \nCMD ISSUED \nKeypad command issued text-keypad commands feature \nYes \nNo \nKeypad \nCommand \nFailed \nCMD FAILED \nKeypad command failed text-keypad commands feature \nYes \nNo \nKeypad \nCommand \nPrompt 1 \nENTER ACCESS \nKeypad command prompt 1 text-keypad commands feature \nYes \nNo \nKeypad \nCommand \nPrompt 2 \nENTER TARGET \nKeypad command prompt 2 text-keypad commandsfeature \nYes \nNo \nAcknowledged \nACKNOWLEDGED \nEnter next card acknowledgement text-occupancy and visitor/escort \nfeatures \nYes \nYes \nEnter escort \nENTER ESCORT \nRequest Escort prompt-occupancy and visitor/escort features \nYes \nNo \nSecure violated \nSECURE \nVIOLATED \nIntrusion zone armed and violated status text-intrusion zone feature \nYes \nNo \nSecure \noffnormal \nSECURE \nOF F NORMAL \nIntrusion zone armed but not ready to re-arm status text-intrusion zone \nfeature \nYes \nNo \n386 \nChapter 8 \nC•CURE 9000 Hardware Confi\n... [truncated, 2029 chars — for the full page use /api/corpus/document/EFTA01225932/385 or ?id=EFTA01225932&page=385]", "char_count": 2029}, {"efta_number": "EFTA01225932", "page_number": 386, "text_content": "Reader LCD Message Set Editor \nReader LCD Messages (continued) \nMessage \nName \nMessage Text \nDescription \niSTAR \nUses \napC \nUses \nLockout \nHHH:MM \nLOCKOUT 8 T \nArea lockout reject 8 T will be replaced with remaining lockout time \nHHH:MM-area lockout feature \nYes \nNo \nReject \nunattended \nREJECT \nUNATTEND \nOccupancy reject indicates that supervisor/escort cannot leave \nsuperviseestvisitors unattended-occupancy feature \nYes \nYes \nReject \noccupancy \nREJECT \nOCCUPANCY \nOccu pa ncy genera I reject text-occupancy feature \nYes \nYes \nDoor held open \nDOOR HELD \nOPEN \nSTAR door held open status text-STAR onty (apC displays Door in Alert \ninstead) \nYes \nNo \nDoor forced \nopen \nDOOR FORCED \nOPEN \nSTAR door forced open status text-STAR onty (apC displays Door in Alert \ninstead) \nYes \nNo \nC•CURE 9000 Hardware Configuration Guide \nChapter 8 \n387 \nEFTA01226318\n", "char_count": 855}, {"efta_number": "EFTA01225932", "page_number": 387, "text_content": "Reader LCD Message Set Tasks \nReader LCD Message Set Tasks \nYou can perform the following tasks to configure Reader LCD Message Sets. \n■ Creating a Reader LCD Message Set on Page 388 \n■ Creating a Reader LCD Message Set Template on Page 388 \n■ Configuring/Modifying a Reader LCD Message Set on Page 389 \n■ Viewing a List of Reader LCD Message Sets on Page 389 \n■ Deleting a Reader LCD Message Set on Page 391 \n■ Using Set Property to Configure Reader LCD Message Sets on Page 392 \nCreating a Reader LCD Message Set \nYou can create a new Reader LCD Message Set. \nTo Create a Reader LCD Message Set \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Right-click the Hardware Folder, click Reader LCD Message Set, and click New on the sub-menu that appears. \n- or - \nIf Reader LCD Message Sets were already created, right-click the Reader LCD Message Sets Folder and click \nNew on the sub-menu that appears. \n3. The Reader LCD Message Set Editor opens, and you can configure the message set. \n4. To save your new Reader LCD Message Set, click Save and Close. \nOr -\nAlternatively, if you want to save the Reader LCD Message Set and then create a new one, click Save and New. \nThe current Reader LCD Message Set is saved and closed, but the Reader LCD Message Set Editor remains \nopen to allow you to create a new Reader LCD Message Set. \nCreating a Reader LCD Message Set Template \nYou can create a new template for a Reader LCD Message Set. A Reader LCD Message Set template saves you time \nbecause you can reuse the same configuration repeatedly. \nTo Create a Reader LCD Message Set Template \n1. Click the Hardware button in the Navigation Pane to open the Hardware Tree. \n2. Right-click the Hardware Folder, click Reader LCD Message Set, and click New Template on the sub-menu \nthat appears. \n- \n- \nIf Reader LCD Message Sets were already created, right-click the Reader LCD Message Sets Folder and click \nNew Template on the sub-menu that appears. \n388 \nChapter 8 \nC•\n... [truncated, 2053 chars — for the full page use /api/corpus/document/EFTA01225932/387 or ?id=EFTA01225932&page=387]", "char_count": 2053}, {"efta_number": "EFTA01225932", "page_number": 388, "text_content": "Reader LCD Message Set Tasks \nThe Reader LCD Message Set Editor where you can configure the Reader LCD Message Set template opens. \n3. Configure the template to meet your requirements. Any fields you configure values for become part of the \ntemplate; then when you subsequently create a new Reader LCD Message Set from that template, these values \nare already filled in. \n4. In the Name field, enter the name you wish to use for the template. \nExample: \nReader LCD Message Set Templatel \n5. To save the template, click Save and Close. \nThe template will be available as an option on the pull-down Template menu. \nConfiguring/Modifying a Reader LCD Message Set \nYou can configure a new Reader LCD Message Set or modify an existing one using the Reader LCD Message Set \nEditor. \nTo Configure/Modify a Reader LCD Message Set \n1. Create a new Reader LCD Message Set or modify an existing Reader LCD Message Set. \nThe Reader LCD Message Set Editor opens for you to edit the Reader LCD Message Set making changes as you \nwish in the fields on the top of the editor and on the General tab. \n2. Type a Name and Description for the Reader LCD Message Set that sufficiently identifies this message set and \nits purpose. \n3. Select your desired date format—by either leaving the default \nMM/DD/YY or clicking the down-arrow to pick DD/MM/YY. \n4. Select your desired time format—by either leaving the default \n12 Hour Clock or clicking the down-arrow to pick the 24 Hour Clock. \n5. In the Messages box, use the vertical scroll bar to find the message you wish to modify in the Message Name \ncolumn and change its related entry in the Message Text column as desired. \nThere are 34 messages whose text you can modify for your uses. Many of them are used by (can be downloaded \nto) both iSTAR and apC controllers; one of the messages is used only by apCs, while about 15 messages are used \nonly by iSTARs. For detailed information about the messages, see Reader LCD Message Set Definitions on Page \n384. \nViewing a \n... [truncated, 2378 chars — for the full page use /api/corpus/document/EFTA01225932/388 or ?id=EFTA01225932&page=388]", "char_count": 2378}, {"efta_number": "EFTA01225932", "page_number": 389, "text_content": "Reader LCD Message Set Tasks \n2. Select Reader LCD Message Set from the Hardware drop-down list and click gag to open a Dynamic View \nshowing a list of all existing Reader LCD Message Sets, as shown in Figure 151 on Page 390. (You can also click \nthe down-arrow of this button to either view the list in the current tabbed view or open a new tabbed view). \nFigure 151: Reader LCD Message Set List \nI- \nReeder LCDMessage Set X1 \nWS • °el \nY Ce \nQuit \nDreg columns lo group by bete \nNer \nDescry:ton \n0 I ReacNelsegeS6 I \nReeflonceSet le \nlit0.4.5406.11 \nR.Ksintag•Set 2. \n• You can sort, filter, and group items in the list. \n• You can right-click a Reader LCD Message Set in the list to open the Reader LCD Message Set Context menu \n(see Table 88 on Page 390) and perform any of the functions on that menu. \n• You can right-click any column heading to open a context menu of all possible Reader LCD Message Set \nfields that can display as columns and add/remove fields to view certain information. \nFor more information on using Dynamic Views, see the Dynamic Views chapter in the C• CURE 9000 Data Views \nGuide. \nReader LCD Message Set List Context Menu \nThe context menu that opens when you right-click a Reader LCD Message Set in the Reader LCD Message Set \nDynamic View includes the selections described in Table 88 on Page 390. \nTable 88: Reader LCD Message Set List Right-Click Context Menu Options \nMenu \nSelection \nDescription \nLae \nClickthismenu selection to edit the selected Reader LCD Message Set. The Reader LCD Message Set Editor opens. You can \nrename the message set and change any of its attributes. \nDente \nChet( this menu selection to delete the selected Reader LCD Message Set. A prompt appears asking you to confirm that you want to \ndelete the Reader LCD Message Set. Click Yes to delete the Reader LCD Message Set or No to cancel the deletion. \nNOTE: You cannot delete a Reader LCD Message Set if it is being used by an STAR and/or apC Controller. \nSet \nc ! one! ty \nCid( this m\n... [truncated, 2586 chars — for the full page use /api/corpus/document/EFTA01225932/389 or ?id=EFTA01225932&page=389]", "char_count": 2586}, {"efta_number": "EFTA01225932", "page_number": 390, "text_content": "Reader LCD Message Set Tasks \nReader LCD Message Set List Right-Click Context Menu Options (continued) \nMenu \nSelection \nDescription \nExport \nselection \nClick this menu selection to Open an Export...to XML or C SV tile dialog box to export one or more of the selected Reader LCD \nMessage Set records toeither an XML or a CSV Me. This allows you to quickly and easily create XMLJCSV reportson the selected \ndata. \nNOTE: Although XML is the initial default fie type. once you choose a type in the Save as type field. whether XML or CSV, that \nbecomes the default the next time this dialog box opens. \nCSV-formatted exports cannot be imported. If you require importing functionally. export to XM L. \n• When you export to an XML file, al avalable data for the selected object(s), whether displayed in the Dynamic View or not—as \nwell as al the child objects of the selected record(s), is exported. \n• When you export toa CSV file, only data in the oclumnsdisplaying in the DynamicView isexported, and in the order displayed. \nThisalows you to both select and arrange data fields for your report. In addition. exporting tea CSV fie alows you to view the \nexported data in an Excel spreadsheet and further manipulate it for your use. \nFor more information, see the Dynamic Views chapter in the C•CURE 9000 Data Views Guide. \nNOTE: When you dick Export Selection, you are running the export on the dent computer. Consequently, the system does not \nuse the Default Export Directory Path—which is on the server. It opens a directory on the client, reverting to the lastdirectory \nused. You can navigate to the default export server directory, if you wish. Or to avoid confusion or use the same destination \nfolder for both dient and server computers, you can use UNC (Universal Naming Convention) paths, for example: \n%%Computer Name% \nProgram Fies1Sofhvare HouselSWHouselSWHSystemlExport. \nFind in \nAudit Log \nClick this menu selection to Open a Query Parameters dialog box in which you can enter prompts and\n... [truncated, 3579 chars — for the full page use /api/corpus/document/EFTA01225932/390 or ?id=EFTA01225932&page=390]", "char_count": 3579}, {"efta_number": "EFTA01225932", "page_number": 391, "text_content": "Reader LCD Message Set Tasks \nmessage set is currently in use by iSTAR or apC controllers. Please remove the message set from the \ncontroller(s) is displayed. \nUsing Set Property to Configure Reader LCD Message Sets \nYou can use Set Property to quickly set a property for one or more Reader LCD Message Sets without opening the \nReader LCD Message Set Editor, thus making it useful for mass updates. See Table 88 on Page 390 for the \nproperties that can be changed. \n a \nTo Set a Property for a Reader LCD Message Set \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select Reader LCD Message Set from the Hardware pane drop-down list. \n3. Click Or  to open a Dynamic View showing all Reader LCD Message Set objects. \n4. Right-click the Reader LCD Message Set(s) in the list for which you want to set the property and select Set \nProperty from the context menu. \n5. Specify the property for the Reader LCD Message Set(s). Click the drop-down button to see a list of properties. \n6. Enter the value for the property and click OK. \n7. Click OK on the Setting Properties of Reader LCD Message Set message box. \n392 \nChapter 8 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226323\n", "char_count": 1238}, {"efta_number": "EFTA01225932", "page_number": 392, "text_content": "Changing the Language for the Default RM LCD Messages \nChanging the Language for the Default RM LCD Messages \nYou can use the Reader LCD Message Set Editor to easily change the language in which the default messages \nappear. When you first start the C•CURE 9000, the default messages appear in the system-wide primary language \nyou chose during installation. \nExample: \nYou chose English as the primary system language and configured all the sets of English messages your Boston \nsite needs; you may now want to customize some message sets in French for your Montreal site. \nNOTE \nThe C•CURE 9000Multilingual User Interface (MUI) Editor, available as a licensable option when \npurchasing C•CURE 9000, allows you to localize the C•CURE 9000 user interface for a broad range \nof languages and cultures. When installed and enabled, the C•CURE 9000 MUI Editor allows anyone \nwith appropriate access permissions to localize individual screens and system messages, including \nthe Reader LCD Message Sets, from within C•CURE 9000 at any time. For information on the MUI \nEditor see the chapter, \"Displaying the C•CURE 9000 in Multiple Languages\" in the C•CURE 9000 \nSystem Maintenance Guide. \nTo Change the language for the Default Message Set \n1. Exit the C•CURE 9000 Administration Application. \n2. Go to the Windows Control Panel and click Regional and Language Options. \n3. Use the Regional Options tab on the Regional and Language Options dialog box to change to the language and \nculture you need by clicking the down- arrow to scroll to your choice and the Customize button to specify your \nown required formats. \nExample: \nFrench (Canada). \nFigure 152: Windows Regionaland Language OptionsScreen \nRev.) nal and l a np.imps npl ions \nRcgoalOr6:ns Lexpaagss i Monscl I \nSP/alath ard /mats \noclicrolllecli km SG\n CONorn lomat notes. *n at. \ndates. <Stine. \nIdect \nkan to match ki pittances. a da Cusiceree to *coca \nyea monk/matt \nEnOsh CUSS Stall \n(NW/ Zenbebia/1 \nEthan \nFMKRAII \nFrrch \nnodh Becull \n\n... [truncated, 2341 chars — for the full page use /api/corpus/document/EFTA01225932/392 or ?id=EFTA01225932&page=392]", "char_count": 2341}, {"efta_number": "EFTA01225932", "page_number": 393, "text_content": "Changing the Language for the Default RIO LCD Messages \n4. Click Apply and then OK. \n5. Restart the Administration Application, click the Hardware button in the Navigation Pane. \n6. Right-click the Reader LCD Message Sets Folder in the Hardware bee and click New on the sub-menu that \nappears, as shown in Figure 149 on Page 383. \n7. The Reader LCD Message Set Editor opens, and you can customize a set of messages in French. \n394 \nChapter 8 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226325\n", "char_count": 498}, {"efta_number": "EFTA01225932", "page_number": 394, "text_content": "9 \nFloors \nThis chapter explains how to configure Floors in C•CURE 9000. Floors are part of Elevator access control. An \nElevator associates a Floor with an Input or Output. \nIn this chapter \nFloors Overview \n396 \nConfiguring Floors  \n397 \nC•CURE 9000 Hardware Configuration Guide \nChapter 9 \n395 \nEFTA01226326\n", "char_count": 311}, {"efta_number": "EFTA01225932", "page_number": 395, "text_content": "Floors Overview \nFloors Overview \nFloors are configured to define Elevator control. Floors are paired with inputs and outputs to control floor access \nthrough elevators. Before you can configure elevators, you must configure floors and/or floor groups. See Elevator \nConfiguration Overview on Page 500 for more information. \nWhen a person presents a card at an elevator, the system checks the clearances associated with the card for the \nelevator and associated floors. If the person's clearances do not allow access, the access attempt is rejected before the \nperson presses an elevator button. If the person has access to a floor, the system grants access to the person and \nactivates the output attached to the button for that floor. \nA Floor has only Name, Description and Enabled properties. If the Floor has been assigned to any Elevators, they \nwill appear in a read-only list on the Floor General tab. \nNOTE \nElevator controls have not been evaluated by UL. \n396 \nChapter 9 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226327\n", "char_count": 1038}, {"efta_number": "EFTA01225932", "page_number": 396, "text_content": "Configuring Floors \nConfiguring Floors \nAccessing the Floor Editor \nYou can access the Floor editor from the C•CURE 9000 Hardware pane. \nTo Access the Floor Editor \n1. Click the Hardware pane button. \n2. Click the Hardware drop-down list and select Floor. \n3. Click K to open a Dynamic View showing all Floor objects. \n4. Double-click the Floor in the list that you want to edit, and the Floor General tab opens, as shown in Figure 153 \non Page 397. \nFigure 153: Floor General Tab \n®\nS\na\nv\ne\n \nanc Close \nSax and 'iew \n5. Type a name for the Floor in the Floor Name field. \n6. Type a description for the Floor in the Description field. \n7. Select Enable to indicate that the Floor is available for use. Elevators that are assigned to the Floor will be shown \nin the Accessed Elevators box. \nC•CURE 9000 Hardware Configuration Guide \nChapter 9 \n397 \nEFTA01226328\n", "char_count": 862}, {"efta_number": "EFTA01225932", "page_number": 397, "text_content": "Configuring Floors \n8. Maintenance Mode - Click to put the Floor into Maintenance Mode. See Chapter 2: Maintenance Mode for more \ninformation. \n9. Click Save and Close when you are finished. \n10. When you create a Floor group, a Group tab will appear with the Floor General tab, as shown in Figure 154 on \nPage 398. \nFigure 154: Floor Groups Tab \nFloor Definitions \nThe definitions for the fields and buttons on the Floor General tab are listed in Table 89 on Page 398. \nTable 89: Floor General Tab \nFiekUBufton \nDescription \nName \nEnter a name for the floor. \nDescription \nEnter a brief description for this floor. \nMaintenance Mode \nClick to put the floor into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \n398 \nChapter 9 \nC•CURE 9000 Hardware Con figuration Guide \nEFTA01226329\n", "char_count": 808}, {"efta_number": "EFTA01225932", "page_number": 398, "text_content": "Configuring Floors \nTable 89: Floor General Tab (continued) \nField/Button \nDescription \nEnabled \nChedahis box to put the floor online. When the floor isoffline. the C•CURE 9000 System ignores the floor. \nAccessed \nElevators \nDisplays a fist of elevators with buttons associated with this floor. These associations are set when you configure the \nElevators. \nSave and Close \nClick Save and Close toaccept your changes to the Floor configuration. \nCreating a Floor \nYou can create a new Floor. \nTo Create a Floor \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select Floor from the Hardware pane drop-down list. \n3. Click New to create a new floor. The Floor Editor opens and you can configure the Floor. \n4. To save your new floor, click Save and Close. \nAlternatively, if you want to save the floor and then create a new one, click Save and New. The current floor is \nsaved and closed, but the floor Editor remains open to allow you to create a new floor. \nCreating a Floor Template \nYou can create a new template for a Floor. A Floor template saves you time because you can reuse the same \nconfiguration repeatedly. \nTo Create a Floor Template \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select floor from the Hardware pane drop-down list. \n3. Click the drop-down arrow next to New and select Template. \n4. The Floor Template opens and you can configure the Floor template. \n5. To save your new floor Template, click Save and Close. \nThe new Floor template appears under Templates in the Template drop-down list. \nTo Select a Floor Template \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select floor from the Hardware pane drop-down list. \n3. Click the drop-down arrow next to New and select Template. \nC•CURE 9000 Hardware Configuration Guide \nChapter 9 \n399 \nEFTA01226330\n", "char_count": 1962}, {"efta_number": "EFTA01225932", "page_number": 399, "text_content": "Configuring Floors \n4. Select the template you wish to use under Templates. \nDeleting a Floor \nYou can delete a Floor. \nTo Delete a Floor \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select Floor from the Hardware pane drop-down list. \n3. Click Ma  to open a Dynamic View showing all Floor objects. \n4. Right-click the Floor in the list that you want to delete and select Delete from the context menu. \n5. Click Yes on the \"Are you sure you want to delete the selected Floor?\" message box. \nModifying a Floor \nYou can edit a Floor. \nTo Edit a Floor \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select Floor from the Hardware pane drop-down list. \n3. Click toy to open a Dynamic View showing all Floor objects. \n4. Double-click the Floor in the list that you want to modify and select Edit from the context menu. The Floor Editor \nopens. \nViewing a List of Floors \nYou u;1O vices a list of Floors. \n a \nTo View a List of Floors \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select Floor from the Hardware pane drop-down list. \n3. Click \n• to open a Dynamic View showing all Floor objects. \nUsing Set Property to Configure Floors \nYou can use Set Property to quickly set a property for a Floor without opening a Floor. Set Property allows you to \nselect multiple Floors in the dynamic list, and right-click to use Set Property to set a specific property for all of them. \nSo, for example, if you wanted to change a setting for 20 Floors, you could select all of them and do it in one step. \n400 \nChapter 9 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226331\n", "char_count": 1748}, {"efta_number": "EFTA01225932", "page_number": 400, "text_content": "Configuring Floors \nTo Set a Property for a Floor \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select Floor from the Hardware pane drop-down list. \n3. Click s k, to open a Dynamic View showing all Floor objects. \n4. Right-click the Floor in the list for which you want to set the property and select Set Property from the context \nmenu. \n5. Specify the property for the Floor. Click the drop-down button to see a list of properties. \n6. Enter the value for the property and click OK. \n7. Click OK on the Setting Properties of Floor message box. \nAdd Floors to a Group \nYou can use Add To Group for Floors. Add Floors To Group enables you to add the Floor object to the group. When \nyou create a Floor group, a Group tab will appear with the Floor - General tab. \nTo Add Floors To a Group \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select floor from the Hardware pane drop-down list. \n3. Click la  to open a Dynamic View showing all floor objects. \n4. Right-click the floor in the list that you want to add to a group and select Add To Group from the context menu. \nFigure 155 on Page 401 displays the Hardware pane and the context menu from which you can add a floor \nobject to a Group. \nFigure 155: Hardware Pane -Adding a Floor to a Group \nHalefreate Tete \nIIeIOVae \nDOS Coteau \n• eiZ Dca \nit NC RE Fit ni\nt WC RE \ng ISCRE rk X \nl e SCAM \n6TM RE \nAd0 t0 4a9 \nEmat \nPIM \n^e1C and \nDelete \ntE Float \niE ike2 \nFIRE Acc \nR RE Roc \n670A RE \nISC Ca Pa \n&gat LCD Id \nCanon Han \nSet twooerti \nradnark Log.. \nC•CURE 9000 Hardware Configuration Guide \nChapter 9 \n401 \nEFTA01226332\n", "char_count": 1701}, {"efta_number": "EFTA01225932", "page_number": 401, "text_content": "Configuring Fbors \n402 \nChapter 9 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226333\n", "char_count": 90}, {"efta_number": "EFTA01225932", "page_number": 402, "text_content": "10 \nDoors \nA Door in C•CURE 9000 provides access control by specifying the controllers, readers, inputs, and outputs \nassociated with an entrance. From the application's hardware tree, you will configure the specific controller type first, \nthen configure the associated readers, inputs, and outputs, and then configure the Door. This sequence of reader the \nsecurity components is necessary because each door requires the associated components to operate with their apC or \niSTAR controllers. \nIn this chapter \nDoor Overview \n404 \nDoor Tasks  \n405 \napC Door Editor \n410 \napC Door Definitions  \n421 \niSTAR Door Editor \n427 \niSTAR Door Monitoring Tab \n442 \niSTAR Door Definitions  \n446 \niSTAR Aperio Door Editor \n455 \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n403 \nEFTA01226334\n", "char_count": 789}, {"efta_number": "EFTA01225932", "page_number": 403, "text_content": "Door Overview \nDoor Overview \nIn general, a door is a logical structure that ties together a controller and its associated readers, inputs, and outputs \nfor access control. In C•CURE 9000, before you configure the door you must first configure the type of controller that \nis to be used for the readers, input, and outputs. Then you can configure the door associated with the components. \nFigure 156 on Page 404 represents the way readers, inputs, outputs, events, and areas are related to Doors in \nC•CURE 9000, while Table 90 on Page 404 describes typical door components. \nFigure 156: Typical Door Configuration \nInputs \n(RTE, DSM) \nReader \nIn/Out \nTable 90: Typical Door Components \nReader \nIn/Out \nOutputs \n(DLR, ADA) \nEvents \nA re a \nIn/Out \nComponent \nDescription \nRTE Input \nA Request To Exit (RTE) input sends a signal that lets C•CURE 9000 know that someone isgoing to open the door to exit. \nTypicalty this device is a motion sensor or a press to exit button. \nDSM Input \nA Door Switch Monitor (DSM) sends a signal that lets C•CURE 9000 know whether the door is open or closed. \nDLR Output \nA Door Latch Relay (DLR) is used to send a signal from C•CURE 9000 to a door latch to lock or unlock the door. \nADA Output \nAn output that activates a door assistance mechanism. usualty installed for compliance with the Americans with DisabilitiesAct \n(ADA). \nReader \nIn/Out \nDefines the card readers that control entryor egress through thisdoor. \nEvents \nDoor events are usualty triggered by state changes in the Door inputs and outputs. You specify the Event you want to activate \nwhen a change, such as\"Door held open; occurs. \nArea In/Out \nDefines the Area a cardholder enters and the area a cardholder leaves through th door. \nExample: \nAcardholder passing through a door named \"Sales' is leaving an Area called \"Lobby\" and entering an Area called \"Sales \nOffice.\" \n404 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226335\n", "char_count": 1945}, {"efta_number": "EFTA01225932", "page_number": 404, "text_content": "Door Tasks \nDoor Tasks \nYou can perform the following general tasks to configure iSTAR and apC Doors. \n■ Creating a Door on Page 405 \n■ Creating a Door Template on Page 406 \n■ Deleting a Door on Page 407 \n■ Modifying a Door on Page 407 \n■ Viewing a List of Doors on Page 408 \n■ Using Set Property to Configure Doors on Page 409 \n■ Add a Hardware Device to Group from a Dynamic View on Page 409 \nCreating a Door \nA door object must be configured for the type of controller to which it is connected: iSTAR or apC controllers. The \nprocess is essentially the same when creating each door object type. First you must create the controller, then \nconfigure the controller's General tab and Board tab to configure inputs, outputs and readers. One exception is that \nwith the iSTAR controllers, you are required to first create an iSTAR cluster and then create controllers within that \ncluster. \nOnce you have created and configured the door controller, you may create as many doors as that type of controller \ncan accommodate. \nTo Create a Door \nFollow the steps below to create a door for an apC controller. To create an iSTAR door, first refer to the next set of \nsteps for reader the iSTAR Cluster and Controller before reader the iSTAR door. \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. In the Hardware tree, expand the facility folder where you want to create a door. You must create a door by \nhighlighting a controller icon, board icon, or door icon in the hardware tree: \n• apC - highlight the apC controller icon, right click, and select apC Door > New. \n• iSTAR - highlight the iSTAR controller icon, right click, and select iSTAR Door > New. \nYou can also create a new door from the door icon in a folder: highlight the door icon, right click, and select \nDoor > New. A new Door Dialog box opens. When the Door Dialog box opens on the General tab, configure \nthe Door. \n3. Enter a Name and Description. \n4. Maintenance Mode - Click \n... [truncated, 2390 chars — for the full page use /api/corpus/document/EFTA01225932/404 or ?id=EFTA01225932&page=404]", "char_count": 2390}, {"efta_number": "EFTA01225932", "page_number": 405, "text_content": "Door Tasks \n• Door Switch Monitor - Click ID to display a list of inputs available for the controller. This signal is true \nwhen the door is open. It is used to determine Admit Unused, Door Held, and Door Forced. Click an Input to \nselect it and assign it to the Door Switch Monitor field. \n• Door Lock Relay - Click ID to display a list of outputs available for the controller. T his output is used to \nopen the door. Click an Output to select it and assign it to the Door Lock Relay field. \n• Alternate Shunt Relay - Click CI to display a list of outputs available for the controller. Alternate Shunt is \nused for cardholders with disability and sometimes for aircraft loading doors. Click an Output to select it and \nassign it to the Alternate Shunt Relay field . \n• Shunt Expiration Relay - Click CI to display a list of outputs available for the controller. This output will \nindicate the expiration of the shunt. Click an Output to select it and assign it to the Shunt Expiration Relay \nfield. \n• Entrance Reader - Click CI to display a list of Readers available. Entrance and Exit Readers are required for \nArea related functions such as Occupancy and Anti-Passback Click a Reader to select it and assign it to the \nEntrance Reader field. \n• Exit Reader - Click ID to display a list of Readers available. Entrance and Exit Readers are required for Area \nrelated functions such as Occupancy and Anti-Passback Click a Reader to select it and assign it to the Exit \nReader field. \n• Readers are continuously active - Click this check box to enable continuous reader activity. Continuously \nActive is not normally used. It is typically used for subway gates and other high volume applications. \n• Request to Exit Input - Click CI to display a list of Inputs available. Click an Input to select it and assign it \nto the field. \n• Unlock Door on RTE - Click this check box to unlock the door at a Request to Exit. This is usually checked, \nbut certain high security areas may use the REX as a signal\n... [truncated, 3164 chars — for the full page use /api/corpus/document/EFTA01225932/405 or ?id=EFTA01225932&page=405]", "char_count": 3164}, {"efta_number": "EFTA01225932", "page_number": 406, "text_content": "Door Tasks \nTo Create a Door Template \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select either an apC or iSTAR Door from the Hardware pane drop-down list. \n3. Click the drop-down arrow next to New and select Template. \n4. The Door Template opens and you can configure it. \n5. To save your new Door Template, click Save and Close. \nThe new Door template appears in the Template drop down list under Templates. \nTo Select a Door Template \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select either an apC or iSTAR Door from the Hardware pane drop-down list. \n3. Click the drop-down arrow next to New and select Template. \n4. Select the template you wish to use under the Templates list and configure the door as explained in Creating a \nDoor on Page 405. \nDeleting a Door \nYou can delete a Door from a controller. \nTo Delete a Door \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select either an apC or iSTAR Door from the Hardware pane drop-down list. \n3. Click a ds to open a Dynamic View showing Door objects of the same type. \n4. Right-click the Door in the list that you want to delete and select Delete from the context menu. \n5. Click Yes on the \"Are you sure you want to delete the selected Door?\" message box. \nModifying a Door \nYou can edit a Door. \nTo Edit a Door \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select either an apC or iSTAR Door from the Hardware pane drop-down list. \n3. Click Mik to open a Dynamic View showing Door objects of the same type. \n4. Double-click the Door in the list that you want to modify, and the Door Editor opens. Or, you can select the door \nin the list, right click, and select Edit from the context menu. \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n407 \nEFTA01226338\n", "char_count": 1976}, {"efta_number": "EFTA01225932", "page_number": 407, "text_content": "Viewing a List of Doors \nYou J.-J:1 cicw a list of Doors. \nTo View a List of Doors \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select either an apC or iSTAR Door from the Hardware pane drop-down list. \n3. Click gl  to open a Dynamic View showing Door objects of the same type. \nNOTE \nIn the Dynamic View, you can right-click the column header and select new columns from the list to \nadd them to the Dynamic View. (For iSTAR Doors you can add a column that identifies the Intrusion \nZone to which the Doors belong.) \nIf you right-click a row in the Door Dynamic View, a context menu is displayed. This menu contains a number of \nstandard selections, as well as selections that are specific for Doors. \nSee Using the Object List Context Menu in the C•CURE 9000 Getting Started Guide for more information about the \nobject context menu. \nSee Table 91 on Page 408 for context menu selections that are specific to Doors. \nThere are additional context menu selections for Advanced Door monitoring. See Advanced Door Monitoring Details \non Page 495 for more information. \nTable 91: Doors Context Menu Selections \nSelection \nDescription \nLock \nOpens a Manual action dialog box that lets you lock the selected Door. \nUnlock \nOpens a Manual action dialog box that lets you unlock the selected Door. \nMomentary \nUnlock \nOpens a Manual action dialog box that lets you momentarily unlock the selected Door. \nShow \nLocked \nCauses \nOpens the Cause List viewer for this Door. \nDoor \nMonitoring \nOpens the Doors Monitoring Screen for the Door you selected. \nSee Door Monitoring Screen on Page 496 for information about the Doors Monitoring screen. \nShow \nAssociation \nClick this menu selection to view a list of Security Objects associated with this iSTAR or apC Door. For more information, see \n'Showing Associations for an Object' in the C•CURE 9000 Getting Started Guide. \nMonitor \nClick this menu selection to view activity for the selected iSTAR a\n... [truncated, 2321 chars — for the full page use /api/corpus/document/EFTA01225932/407 or ?id=EFTA01225932&page=407]", "char_count": 2321}, {"efta_number": "EFTA01225932", "page_number": 408, "text_content": "uocr I \nUsing Set Property to Configure Doors \nYou can use Set Property to quickly set a property for an iSTAR or apC Door without opening an iSTAR or apC Door \neditor. Set Property allows you to select multiple Doors objects in the dynamic list, and right-click to use Set Property \nto set a specific property for all of them. \nExample: \nIf you wanted to change an unlock property setting for 20 apC Doors, you could select all of them listed in the \ndynamic list and do it in one step. \nTo Set a Property for a Door \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select either an apC or iSTAR Door from the Hardware pane drop-down list. \n3. Click it s to open a Dynamic View showing all Door objects. \n4. Right-click the Door (or set of doors) in the list for which you want to set a property and select Set Property from \nthe context menu. \n5. Specify the property for the Door. Click the Browse button to see a list of properties. \n6. Enter the value for the property and click OK. \n7. Click OK on the Select a property and value for object message box. \nAdd a Hardware Device to Group from a Dynamic View \nWhen you select a Hardware device from a Dynamic View and then right-click for the context menu, Add to group \nappears as a menu selection. This function enables you to add the object(s) to a Group. More more information about \nthe Group function see Groups Tab for Hardware Devices on Page 28. \nTo Add a Hardware Device To a Group \n1. In the Navigation Pane of the Administration Workstation, click Hardware to open the Hardware pane. \n2. Select a Hardware device from the Hardware pane drop-down list. \n3. Click gib to open a Dynamic View showing all objects of that type. \n4. Right-click on the object that you want to add to a Group and select Add To Group. A list of Groups is \ndisplayed. \n5. Select the Group from the list, and the object is added to that group. \n6. Click OK to confirm your choice. \nC•CURE 9000 Hardware \n... [truncated, 2051 chars — for the full page use /api/corpus/document/EFTA01225932/408 or ?id=EFTA01225932&page=408]", "char_count": 2051}, {"efta_number": "EFTA01225932", "page_number": 409, "text_content": "apC Door Editor \napC Door Editor \nThe apC Door editor has the following tabs: \n• apC Door General Tab on Page 411 \n• apC Door Readers Tab on Page 413 \n• apC Door Timing Tab on Page 415 \n• apC Door Triggers Tab on Page 416 \n• Groups Tab for Hardware Devices on Page 28 \n• apC Door Status Tab on Page 416 \n• apC Door Visitor Management Tab on Page 418 \n• apC Door State Images Tab on Page 417 \nConfiguring an apC Door \nTo configure a Door associated with an apC controller, first you must configure an apC panel, along with its readers, \ninput, and outputs. For more information see apC Controller Configuration Summary on Page 308. To configure the \ndoor, perform the following tasks. \nNOTE \nThe apC and apC/L controllers have not been evaluated by UL. \nTo Configure the apC Door \n1. In the C•CURE 9000 Navigation Pane of the Administration Workstation, click Hardware to open the Hardware \npane. \n2. Configure the apC panel's Readers, Inputs, and Outputs. \n3. In the Hardware tree, find the apc Controller to which you want to associate the new apC Door, and click the \n\"+\" to expand the contents of that directory. A list displays that includes Doors, Elevators, Inputs, Outputs, and \nReaders. These objects are also directories. \nIf you already have some apC doors configured, you can display all existing doors for the controller. Highlight \nDoors and click Rai to open a Dynamic View showing all Door objects of this type (see Figure 157 on Page 411). \nEdit an existing door by double-clicking the door in the Dynamic View to open the door's editor window. \n4. Highlight the Doors directory in the Hardware tree, right-click to display the context menu, and select New. A \nnew apC Door editor displays. See apC Door - General tab, as shown in Figure 158 on Page 412. \nAnother way to create the new apC door is to highlight the Controller in the Hardware tree, right click, and select \napC Door>New. \n410 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226341\n", "char_count": 1976}, {"efta_number": "EFTA01225932", "page_number": 410, "text_content": "apC Door Editor \nFigure 157: Hardware Pane - Create an apC Door \nIteromme \nv 2 DuISCatficee. \nto float \nISC Cows Pats \nP a  Rosin LCD MenageSOH \n• la CCOPare. Haas PatkriDttal \nre aPC Cam Pats \nccuRE Mob le \nAOC Cabal 1 Oki; 5 \n• • \n4gC Coracle, 28145 \nllp \nit Eire \nite \ntog coTtenn: to roup \nNano \napC Caftan 1 Biz 5 \nItert \nNew hada, \napC CaRclei 2 Bklg 5\n5. Configure the door on the General tab and any other tabs, as needed. You will need to have already configured \nthe apC Readers, Inputs, and Outputs to fully configure an apC door. \n6. Configure remaining tabs for this door, or click Save and Close. The new door displays under the Doors \ndirectory in the Hardware tree. \napC Door General Tab \nConfigure the door on the General tab and other tabs, as required. You will need to have configured the apC \nReaders, Inputs, and Outputs to configure an apC door. Refer to the apC Controller Configuration Summary on Page \n308 for further information. \nThe following section documents the tasks required to configure a basic Door object for apC panel access control. The \nDoor Reader buttons and entry fields on the Door General tab, shown in Figure 158 on Page 412, allow you to specify \nthe card readers associated with this Door, and to configure door-specific settings for these readers. \nTo Configure the apC Door General Tab \n1. Use the Identification box to enter a Name and brief Description (optional) of the door that you are reader. \nThe Controller that you have chosen to operate the door is listed in the read-only Controller field. \n2. Click ID for the Door Switch Monitor. When you click this button to select an input to assign to the Door \nSwitch Monitor, a browser opens presenting a list of inputs available for the controller. Click an Input to select it \nand add it to the entry field (see Figure 158 on Page 412). \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n411 \nEFTA01226342\n", "char_count": 1914}, {"efta_number": "EFTA01225932", "page_number": 411, "text_content": "apC Door Editor \nFigure 158: apC Door GeneralTab \nInd cost \nanis? \nWM( boc x, \nLIMOS raving Dnr Rule \nParitica Men Wry \nr tirltroxe mak,\nGRAM I RHA<tl Tag l Iran  l Gan  l Rai  I IC Deaf Fah Ra vva \nto t \nRaves/ To Ent \nLain.. rapt., \nDoor Saadi Mak.: \nEta Lea* Rake; \nIcC Pat I , tot PMUr1 cc FtEl (Mc Wag) \nIcC 0.1D-114p: REI Nan Cc) \n&VS Rag Ray I't \nI VC Peat I apC REI \nSOVESSIIKe Par CC Oa/ICC R8040 Eked Nan VMI \n=al \nNest To Shape itoC FRU IcC REI Psi, Wm] \nP IMAM. en RIZ \nP Supt 091 a \nRIES loin \n1 k \n3. Click Ej for the Door Lock Relay. When you click this button to select an output to assign to the Door Lock \nRelay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it and \nadd it to the entry field. \n4. Click Ej for the Alternate Shunt Relay. When you click this button to select an output to assign to the Alternate \nShunt Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it \nand add it to the entry field. \n5. Click [j  for the Shunt Expiration Relay. When you click this button to select an output to assign to the Shunt \nExpiration Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to \nselect it and add it to the entry field. \n6. Click [j  for the Request to Exit Input. When you click this button to select an input to assign to the Request to \nExit, a browser opens presenting a list of inputs available for the controller. Click an RTE Input to select it and \nadd it to the entry field. \n7. Select the Unlock Door on RTE check box to unlock the door at a Request to Exit \n8. Select the Shunt DSM While RTE is Active check box to Shunt Door Switch Monitor While Request to Exit is \nActive. \n9. Navigate to the Readers tab, or click Save and Close to return to the Hardware pane. \n412 \nChapter 10 \nC•CURE 9000 Hardware Con figuration Guide \nEFTA01226343\n", "char_count": 1935}, {"efta_number": "EFTA01225932", "page_number": 412, "text_content": "apC Door Editor \napC Door Readers Tab \nThe apC Door - Readers tab allows configuration of inbound and outbound access readers and for bi-directional \nreaders installed at apC controlled doors. MI the readers on the door must be located on the same apC panel. See \nFigure 159 on Page 413. \nThe Readers tab also lets you configure doors as \"ordinary\" or turnstile for escorted access for visitors by selecting the \nReaders Are Continuously Active check box. \nFigure 159: apC Door Readers Tab \nSoma \namentOca \nla:court \n&V•••.; Derr \nA \nPane\", Wan Wrg \nr Lieritrarce Male \nGAPS Parka I Tina, I Nal I eValt• I as \nI tblitodowd Rids I SISSON I \nAttess Pisan \nKcal Near \n93••••••r•We \nkpcpad.i. apC RE1 pan Yingl \n— \n• I \nrepC Peadel. apC RE1 Man Alp) \nI .1 \nig Reds an monody uipte \n8.-treciael %Wen \nMtnace N Ihs th04 Maris Neal wane \nlecC eat I IcC 32 nu &all to, 2 RA  ...Iv I \nMimi ogroMe rtlin \nli10 secoa Cl encresed \nionise ass MA 00114.*IN Otitald MOYVIX4t \nMancini/10w \n1/10•exads dement \nTo Configure the apC Door Readers Tab \n1. Click \nfor the Inbound Access Reader. When you click this button to select a reader to assign to the Inbound \nAccess Reader, a browser opens presenting a list of readers available for the panel. Click a Reader to select it \nand add it to the entry field. \nWhen specifying an access reader, follow these guideline: \n• Both access readers on the door must be located on the same apC panel. \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n413 \nEFTA01226344\n", "char_count": 1496}, {"efta_number": "EFTA01225932", "page_number": 413, "text_content": "apC Door Editor \n• If you are using a bi-directional reader, specify the same reader in the inbound and outbound access reader \nfields. \n2. Click 0 \nfor the Outbound Access Reader. When you click this button to select a reader to assign to the \nOutbound Access Reader, a browser opens presenting a list of readers available for the controller. Click a \nReader to select it and add it to the entry field. \n3. Select the Readers are Continuously Active check box to enable continuous reader activity, enabling readers to \nread and process cards even when the doors associated with them are unlocked or open because of another card \naccess request. This mode is typically used for turnstiles or other high traffic situations that would result in \nunacceptable delays if the reader went through its normal sequence of read-open-close for each cardholder. \nExample: \nSuppose a user swipes their card and unlocks a door. Before the door opens and closes, another person swipes \nhis card. If this box is checked, the system treats the second swipe as an access request. If you leave this box \nunchecked, the system ignores the second swipe. This feature is useful at high volume doors where you don't \nwant to wait for the door to close after every access. \nFor escorted access for visitors to work at: \n• \"Ordinary\" doors — multiple person access on each access cycle — select the Readers Are Continuously \nActive check box. \n• \"Turnstiles\" (or Mantraps) — one person access only on each access cycle — clear the Readers Are \nContinuously Active check box. \n4. Click 0 \nto select an input for the apC Bi-directional Reader in the Activation of the Input Determines Inbound \nMovement entry field. When you click this button to select an input to assign to the inbound input, a browser \nopens presenting a list of inputs available for the panel. Click an Input to select it and add it to the entry field. \nThe selected input tests for inbound movement at the apC controlled door. When this input activates wi\n... [truncated, 3753 chars — for the full page use /api/corpus/document/EFTA01225932/413 or ?id=EFTA01225932&page=413]", "char_count": 3753}, {"efta_number": "EFTA01225932", "page_number": 414, "text_content": "apC Door Editor \ndetermine that the card is entering the area in the Must Activate Within entry field. The range for this field is \nfrom 0 to 99.99 seconds in units of 0.1 seconds. \nIf the input changes state within the specified time, the panel determines that the card is moving into the \noutbound area. \n8. Navigate to the Timing tab, or click Save and Close to return to the Hardware pane. \napC Door Timing Tab \nA door that is controlled by an apC panel is constrained to a single set of door timing values for each side of the \ndoor. Required apC door sequences use the same set of timing values regardless of schedule. Only one alternate set \nof timer values is used in each door sequence. This corresponds to a personnel record configured to use Alternate \nShunt Time. See the Timing tab in Figure 160 on Page 415. \nFigure 180: apC Door Timing Tab \n.1:J al \neV Oast \nSa.< ad! \nan. \nDOS \n*awl \navyterg D_ Soda \nPaid= lien VAro \nr Monarace Mole \nGent I Rooks bra I Nein I Goa I Sue I Ike OWNS &No I Sub ape I \nDolt Mock iseccoa) \nSLIM rem (seearal: \nLtrezt ids (wak) Is \narra Sent Teo (Worms* Ix 00 00 \nRunt Esweece Worm\" Tire (gm ea) \nD2,r Cbstectarce Time (110 stCI \nDoc, Opun )ace Ton•1110 toc) \nSetting apC Door Timing \n1. Delay Relock - Enter the number of seconds to delay door relock after the door is opened (after a request to exit, \nfor example). The range in seconds is 000 to 0:1639 (999 seconds); the default is 000. \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n415 \nEFTA01226346\n", "char_count": 1508}, {"efta_number": "EFTA01225932", "page_number": 415, "text_content": "apC Door Editor \n2. Shunt Time - Enter the number of seconds that the door can remain open before a door held open alert is \ngenerated within the range of 000 to 0:16:39 (999 seconds); the default is 0:0:10 (10 seconds). \n3. Unlock Time - Enter the number of seconds the Door remains unlocked after a valid card swipe, RTE activation, \nor momentary unlock within the range of 000 to 0:4:15 (255 seconds); the default is 005 (5 seconds). \n4. Alternate Shunt Time - Enter the number of hours, minutes, and seconds the Door can remain open before a \ndoor held open alert is generated after a valid card swipe by a cardholder with the Alternate Shunt flag set in \ntheir personnel record. This value is used only if it is set to a greater time than the Shunt time value within the \nrange of 000 (default) to 18:0:0 (18 hours). \n5. Shunt Expiration Warning Time - If set, the Shunt expiration relay is fired regardless of the shunt time used. If \nset to 0 (the default), the Shunt expiration relay will only be fired if the Alternate shunt time was used. The Shunt \nExpiration Warning has a range of 000 to 0:4:0 (4 minutes). \n6. Door Close Debounce Time - Setting this value to 0 indicates that there is no timer. The range is 0 - 25.5 \nseconds units of 0.1 seconds. \n7. Door Open Grace Time - Also known as Door Open Debounce Time. Setting this value to 0 indicates that \nthere is no timer; as soon as the door opens, door forced open is reported. The range for this field is from 0 to \n25.5 seconds in units of 0.1 seconds. \n8. Navigate to the Triggers tab, or click Save and Close to return to the Hardware pane. \napC Door Triggers Tab \nYou can create Triggers for apC Doors using the apC Doors Triggers tab. A Trigger executes a specified Action when \na particular predefined condition occurs. When a Trigger is defined, the Actions available depend on the property \nselected \nSee the following for information on apC Triggers: \n■ Triggers Tab for apC Devices on Page 369. \n■ Defining a Trigger for an\n... [truncated, 2846 chars — for the full page use /api/corpus/document/EFTA01225932/415 or ?id=EFTA01225932&page=415]", "char_count": 2846}, {"efta_number": "EFTA01225932", "page_number": 416, "text_content": "apC Door Editor \nFigure 161: apC Door Status Tab \narm \n9medeemd \n*owl \n&green; Dem,v, 9u0o \nPriam *Weft \nr 14.0.11cd• \nGino* I tows I lap I %en I Goa SIvroeinawwIsrreosI \nDowns Sou \nMode Stelt IUMenem \nOpen Stens [Ulm., \nMode 'Locked \n■ Navigate to the State Images tab or click Save and Close. \napC Door State Images Tab \nThe State Images tab on the Inputs Board (shown in Figure 162 on Page 418) provides a means to change the default \nimages used to indicate controller states. \nTo Change an Image \n1. Double-click the existing image. \nA Wmdows Open dialog box appears allowing you to browse for a folder in which you have placed \nreplacement images. \n2. When you locate the replacement image, select it to add it to the image listing. \n3. To restore the default image, right-click the new image and select Restore Default. \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n417 \nEFTA01226348\n", "char_count": 900}, {"efta_number": "EFTA01225932", "page_number": 417, "text_content": "apC Door Editor \nFigure 162: apC Door State Images Tab \nSast ard Case \nSa.< and \nWen ke ex, \nCOMIPbei• lagnierg Day\\ ado \nPricks Men Wee \nr Salenswoo Mc* \nGetwid %abet I Tim, I Tryon I Grad I saw I Us PoIrod Fedi Rae masa\nAge \n'nape \n:J \n4. Click Save and Close to return to the Hardware pane. \napC Door Visitor Management Tab \nThe apC Door Visitor Management tab lets you configure Doors with Visitor Management Actions, so that you can \nautomatically Check-in and Check-out Visitors. \nFor more information about Check-in and Check-out of Visitor via Visitor Management, see the C•CURE 9000 \nVisitor Management Guide. \n418 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226349\n", "char_count": 692}, {"efta_number": "EFTA01225932", "page_number": 418, "text_content": "apC Door Editor \nFigure 183: apC Door Visitor Management tab \napC Door - coo door I \na Svc crid Close \nSove and Nett \nMama \nDescription \nCOO dcci 1 \nr Maintenance Mode \nTime Zoom \nGeneral I Readers I Irnrig I Trim's I Groups I Status I Use' Defined Fields Vintel MenageniEn I State images I \n' Add Acton \n> Remove Acton \nWiwi Management Action \nChat. Vcitcy, In \nDitection \nScheckle \nIn \na/nays \nTo Configure a Door Action for Check-In \n1. In the C•CURE 9000 Admin Client, navigate to the Door you wish to configure. \n2. Click the Visitor Management tab. \n3. Click Add Action. \n4. Chose the Visitor Management Action Check Visitors In. \n5. Select the Direction for the action to take place. \n• Choose In for Visitors to Check-in using an inbound reader. \n• Choose Out for Visitors to Check-in using an outbound reader. \n• Choose In and Out for Visitors to Check-in using either the inbound or outbound reader. \n6. Select a Schedule for the action to be active. \n7. Click Save and Close \nTo Configure a Door Action for Check-out \n1. In the C•CURE 9000 Admin Client, navigate to the Door you wish to configure. \n2. Click the Visitor Management tab. \n3. Click Add Action. \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n419 \nEFTA01226350\n", "char_count": 1242}, {"efta_number": "EFTA01225932", "page_number": 419, "text_content": "apC Door Editor \n4. Chose the Visitor Management Action Check Visitors Out \n• Check Out Visitors and Return Badge. \n5. Select the Direction for the action to take place. \n• Choose In for Visitors to Check-out using an inbound reader. \n• Choose Out for Visitors to Check-out using an outbound reader. \n• Choose In and Out for Visitors to Check-out using either the inbound or outbound reader. \n6. Select a Schedule for the action to be active. \n7. Click Save and Close \n a \nTo Configure a Door Action for Check-out \nThis presumes that a Badge Return mechanism is set up at the Check-out reader. \n1. In the C•CURE 9000 Admin Client, navigate to the Door you wish to configure. \n2. Click the Visitor Management tab. \n3. Click Add Action. \n4. Chose the Visitor Management Action Check Visitors Out \n• Check Out Visitors and Return Badge. \n5. Select the Direction for the action to take place. \n• Choose In for Visitors to Check-out and Return the Badge using an inbound reader. \n• Choose Out for Visitors to Check-out and Return the Badge using an outbound reader. \n• Choose In and Out for Visitors to Check-out and Return the Badge using either the inbound or outbound \nreader. \n6. Select a Schedule for the action to be active. \n7. Click Save and Close \n420 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226351\n", "char_count": 1324}, {"efta_number": "EFTA01225932", "page_number": 420, "text_content": "apC Door Definitions \napC Door Definitions \nThe definitions of the various fields and buttons on the apC Door editor are given in the following tables. \napC Door General Tab Definitions \nField/Button \nDescription \nName \nUse the Identification box to enter a name (up to 5O characters long) and brief description of the door you are ocinfig uring. \nDescription \nA description of the door that you are config uring. \nMaintenance \nMode \nClick to put the apC door into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nPartition \nThe Partition label indicates to which partition the door belongs. \nHardware \nDoor Switch \nMonitor \nClick ri  for the Door Switch Monitor. When you dick this button to select inputs to assign to the Door Switch Monitor. a \nbrowser opens presenting a list of inputs available for the controller. Click a Switch or other pre-configured Input to select it and \nadd it to the entry field. \nDoor Lock \nRelay \nClick El for the Door Lock Relay. When you dick this button to select an output to assign to the Door Lock Relay, a browser \nopens presenting a list of outputs ava liable for the controller. Click a Lock or other pre-configured Output to select it and add it \nto the entry field. \nAlternate \nShunt Relay \nClick ri  for the Alternate Shunt Relay. When you dick this button to select an input to assign to the Alternate Shunt Relay. \na browser opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the entry field. \nShunt \nExpiration \nRelay \nClick[] for the Shunt Expiration Relay. When you click this button to select an output to assign to the Shunt Expiration \nRelay. a browser opens presenting a list of outputs available for the controller. Click an Output to select it and add it to the entry \nfield. \nRequest to Exit \nRequest to \nExit Input \nClick  --. I for the Request to Exit input. When you click this button to select an input to assign to the Request to Exit input. \na browser opens\n... [truncated, 2562 chars — for the full page use /api/corpus/document/EFTA01225932/420 or ?id=EFTA01225932&page=420]", "char_count": 2562}, {"efta_number": "EFTA01225932", "page_number": 421, "text_content": "apC Door Definitions \napC Door Readers Tab Definitions (continued) \nFlekUBufton \nDescription \nInbound Access \nReader \nWhen you click in to select an Inbound Access Reader, a browser opens presenting a list of readers available for the panel. \nClick a Reader to select it and add it to the entry field. \nOutbound \nAccess Reader \nWhen you dick[] to select an Outbound Access Reader, a browser opens presenting a list of readers available for the \npanel. Click a Reader to select it and add it to the entry field. \nReaders are \nContinuously \nActive \nSelect the Readers Are Continuously Active check box 4 you want readers to read and process cards even when the \ndoors associated with them are unlocked or open because of another card access request. \nBi-directional Readers \nActivation of the \nInput \nDetermines \nInbound \nMovement \nClick n \nto select an input for the apC Bi-directional Reader in the Activation of the Input Determines Inbound Movement \nentry field. When you click this button to select an input to assign to the inbound input, a browser opens presenting a list of \ninputs available for the panel. Click an Input to select it and add it to the entry field. \nThe selected input tests for inbound movement at the apC controlled door. When this input activates within the directional link \ntime, the system determines that the card is moving in the inbound direction. The apC panel uses this information for access \ncontroldecisions. \nThe inbound input must be on the same apC as the bi-directional readers on this door. \nMust Activate \nWithin \nIf the door has an inbound input (termed in the Activation of This Input Determines Inbound Movement field, enter the time in \ntenths of seconds that the panel waits between card reads and input state changes to determine that the card is entering the \narea in the Must Activate Within entry field. The range for this field is from 0 to 99.99 seconds in units of 0.1 seconds. \nIf the input changes state within the specified time, the pa nel d\n... [truncated, 3515 chars — for the full page use /api/corpus/document/EFTA01225932/421 or ?id=EFTA01225932&page=421]", "char_count": 3515}, {"efta_number": "EFTA01225932", "page_number": 422, "text_content": "apC Door Definitions \napC Door Timing Tab Definitions(continued) \nFieldeutton \nDescription \nDelay Relock \nType the number of seconds to delaydoor rebck after the door isopened (after a request to exit, for example). The range in \nseconds is 0:0:0 to 0:16:39 (999 seconds); the default is 0:0:0. \nShunt Time \nShunt Time - type the number of seconds that the door can remain open before a door held open alert is generated within the \nrange of 0:0:0 to 0:16:39 (999 seconds): the default is 0:0:10 (10 seconds). \nUnlock Time \nUnlock Time - type the number of seconds the Door remains unlocked after a valid card swipe, RTE activation, or momentary \nu n lock with in the range of 0:0:0 to 0:4:15 (255 seconds); the default is 0:0:5 (5 seconds). \nAlternate \nShunt Time \nAlternate Shunt Time - type the number of hours, minutes, and seconds the Door can remain open before a door held open \nalert is generated after a valid card swipe by a cardholder with theAlternate Shunt flag set in their personnel record (This value \nis used onty if it is set to a greater time than the Shunt time value) within the range of defauttiminimum: 0:0:0; maximum:18:0:0 \n(18 hours). \nShunt \nExpiration \nWarning Time \nif set, the Shunt expiration relay fires regardless of the shunt time used. If set to 0 (the default), the Shunt expiration relay fires \nonty if the Alternate shunt time is used. The Shunt Expiration Warning has a range of 0:0:0 to 0:4:0 (4 minutes). \nDoor Close \nDebounce \nTime \nSpecifies the time (in 1/10th of a second intervals) that the C•CURE 9000 ignores DSM inputs. to allow for bouncing doors. \nSetting this value to 0 indicates that there is no timer. The range for thisfield is from 0 to 25.5 seconds in unitsof 0.1 seconds. \nDoor Open \nGrace Time \nSpecifies the time (in 1/10th of a second intervals) that the C•CURE 9000 waits for an RTE, card admit, or momentary unbck \nsignal after receiving the signal from the DSM. Setting this value to 0 indicates that there is no timer; as soon as the \n... [truncated, 2892 chars — for the full page use /api/corpus/document/EFTA01225932/422 or ?id=EFTA01225932&page=422]", "char_count": 2892}, {"efta_number": "EFTA01225932", "page_number": 423, "text_content": "apC Door Definitions \napC Door Triggers Tab Definitions (continued) \nField/Button \nDescription \nAction \nClick with in the Action column to display a drop-down list of valid actions. Click on an Action that you want to include as a \nparameter for the trigger to add it to the column. \nWhen a Trigger is added, an Action must be configured in the Action column. This is the Action that willoccur when the object's \nselected Property receives the selected Value. As the Action is selected, the lower pane in the Triggers box will show a \ncorresponding entry field, or group of entry fields. specific to the selected Action. Click n \nto select entries for these fields. Once \nthe field (or group of fields) is completed, the Details column willshow information about how the Action has been configured. \nDetails \nD isplays data ils concerning the security objects that are associated with the selected Action. \nSchedule \nC lick with in the Schedule column to display a drop-down list of pre-configured schedules. Click n \nto select a Schedule that \nyou want to attariate with the trigger. Schedules are created in the Configuration Pane. See the C•CURE 9000 Software \nConfiguration Guide for more information. \napC Door Trigger Properties \nTable 95: apC Door Trigger Properties \nProperty \nDescription \nAdmit Status \nFor anyone of the Admit Status values (see the Value column list) you can choose one of the following Actions to create a \nValues are: \nTrigger: \nAdmitReject \nActivate Event -When this status occurs and the Schedule isActive (you can choose anySchedule). \nDuress \nActivate Event Outside Schedule -An event is activated when this status occurs while the Schedule is inactive (choose any \nSchedule). \nNoticed \nAdmit \nActivate Output -When this statusoccurs (only works with the Always Schedule). \nNoticed \nOnly these three Actions are supported for Admit Status. \nReject \nAlarm \n1. Choose a value for the Property from the Values column. \nStateStatus \n2. Select an Action from the Action dr\n... [truncated, 2861 chars — for the full page use /api/corpus/document/EFTA01225932/423 or ?id=EFTA01225932&page=423]", "char_count": 2861}, {"efta_number": "EFTA01225932", "page_number": 424, "text_content": "apC Door Definitions \napC Door Groups Tab Definitions \nTable 96: apC Door Groups Tab Definitions \nField/Button \nDescription \nGroups \nFor more information about the use of the Toolbar buttons, see Chapter 2, \"Dynamic Views' in the C. CURE 9000 \nData Views Guide \nZ E l 4\ny ce \nName \nT h is colu m n displays the name entered for the g rou p when it was config u red. The selected door is a member of any \ngroup(s) listed in thiscolumn. \nDescription \nThis column displays the description entered for the group when it was configured. \napC Door Status Tab Definitions \nTable 97: apC Door apC Status Tab Definitions \nField/Button \nDescription \nAlarm Status \nDisplays the values Normal, Forced, Held Open, or Unknown. \nAdmit Status \nDisplays the valuesAdmit, Reject Admit, Duress, Admit Visitor, Reject Visitor, Request To Exit, Reject No Escort, Reject No PIN, \nReject Not Time. Reject Unknown, Reject Unknown PIN, or Reject Duress. \nOpen Status \nDisplays the values Open. Closed. or Unknown. \nMode \nDisplays the values Locked, Unlocked, No Access, or Unknown. \napC Door State Images Tab Fields and Icons \nTable 98: apC Doo State Images Tab Definitions \nField/Button \nDescription \nField/Button \nDescription \nUnknown \nLocked \nE l \nForced \ne \nUnlocked \nUnlocked \nL \ni-_I \nHeld Open \nal \nNo Access \nLi \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n425 \nEFTA01226356\n", "char_count": 1368}, {"efta_number": "EFTA01225932", "page_number": 425, "text_content": "apC Door Definitions \napC Door State Images Tab Definitions (continued) \nField/Button \nDescription \nField/Button \nDescription \nOpen \nMomentary Unlock \n[]\n426 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226357\n", "char_count": 226}, {"efta_number": "EFTA01225932", "page_number": 426, "text_content": "STAR Door Edrtor \niSTAR Door Editor \nYou use the iSTAR Door editor to configure iSTAR Doors. \nTo configure a Door associated with an iSTAR controller, first you must: \n■ Create an iSTAR cluster \n■ Create the iSTAR controller in that cluster \n■ Create the inputs, outputs and readers that are associated with the Door. \nFor a brief explanation see Creating a Door on Page 405. \nFor a more detailed explanation of configuring iSTAR controllers see Understanding C•CURE iSTAR Controllers on \nPage 118. \nThe iSTAR Door Editor includes the following tabs: \n■ iSTAR Door General Tab on Page 427 \n■ iSTAR Door Timing Tab on Page 429 \n■ iSTAR Door Areas & Zones Tab on Page 431 \n■ iSTAR Door Double Swipe Tab on Page 432 \n■ iSTAR Door Conditional Access Tab on Page 436 \n■ iSTAR Door Triggers Tab on Page 438 \n■ Groups Tab for Hardware Devices on Page 28 \n■ iSTAR Door Status Tab on Page 440 \n■ iSTAR Door Monitoring Tab on Page 442 \n■ iSTAR Door Visitor Management tab on Page 443 \n■ iSTAR Door State Images Tab on Page 442 \niSTAR Door General Tab \nPerform the following steps to configure a basic Door object for iSTAR Controller access control. The Door Reader \nbuttons and entry fields on the Door dialog box General tab, shown in Figure 164 on Page 428, allow you to specify \nthe card readers associated with this Door, and to configure door-specific settings for these readers. \nNOTE \nNOTE \nIf the first Input, Output, or Reader you assign is a Shlage Wireless I/O component, a message box \nappears asking if you wish to auto-fill the remaining objects for the door. If you click Yes the \nremaining objects are selected automatically. This option only appears if all of the options are blank \nwhen you assign the first object. See iSTAR PIM-485 Reader I/O Tab on Page 261 for information \nabout Schlage Wireless Reader I/O components. \nAn iSTAR Aperio Door does not have the following tabs: Areas & Zones, Double Swipe, and Door \nMonitoring. Also, for Aperio Doors, some of the General tab settings are\n... [truncated, 2172 chars — for the full page use /api/corpus/document/EFTA01225932/426 or ?id=EFTA01225932&page=426]", "char_count": 2172}, {"efta_number": "EFTA01225932", "page_number": 427, "text_content": "STAR Door Edda( \nTo Configure the iSTAR Door General Tab \n1. Use the Identification box to enter a Name and brief Description (optional) of the door that you are configuring. \nFigure 164: STAR Door General Tab \nVt. IS I AR Dv5a \nIl ltra Door I \nLISarro and Ono ei ca..* red Deo \n[tame \nQrscrebOn \n['Aro Coy \nPaaba Delat \nr Merdensce Mod \nLev Zone GMT.0597) Eastern TmelVS sCavdal \nGeneral I Tan; Heat a Zones I Date Sam I Nan I Gen I Status I Des Mo-tam I user Dead Fees I State neat I \nLoaeon \nComas Iltral \nDow Seittawlor \nOos Loa Paex I \nMimeo 5)unt Reiss I \nRIM Wanda Ras; I \nNeon \nRamer. ES \nSame \nMaenads: r \nOutsold ReetM I \nr \nResselTe Ed leak r \nr ACC, :CC, r P- E: \nr \nr \nr sem rce-agmns SW Matte to the 'at \nThe Controller that you have chosen to operate the door is listed in the Controller read-only field. \n2. Click El for the Door Switch Monitor. When you click this button to select an input to assign to the Door \nSwitch Monitor, a browser opens presenting a list of inputs available for the controller. Click an Input to select it \nand add it to the entry field (see Figure 164 on Page 428). \n3. Click CI for the Door Lock Relay. When you click this button to select an input to assign to the Door Lock \nRelay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it and \nadd it to the entry field. \n4. Click El for the Alternate Shunt Relay. When you click this button to select an input to assign to the Alternate \nShunt Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to select it \nand add it to the entry field. \n428 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226359\n", "char_count": 1705}, {"efta_number": "EFTA01225932", "page_number": 428, "text_content": "STAR Door Editor \n5. Click El for the Shunt Expiration Relay. When you click this button to select an output to assign to the Shunt \nExpiration Relay, a browser opens presenting a list of outputs available for the controller. Click an Output to \nselect it and add it to the entry field. \n6. Click El for the Entrance Reader. When you click this button to select a reader to assign to the Entrance \nReader, a browser opens presenting a list of readers available for the controller. Click a Reader to select it and \nadd it to the entry field. \n7. Click El for the Exit Reader. When you click this button to select a reader to assign to the Exit Reader, a \nbrowser opens presenting a list of readers available for the controller. Click a Reader to select it and add it to the \nentry field. \n8. Select the Readers are Continuously Active check box to enable continuous reader activity, enabling readers to \nread and process cards even when the doors associated with them are unlocked or open because of another card \naccess request. This mode is typically used for turnstiles or other high traffic situations that would result in \nunacceptable delays if the reader went through its normal sequence of read-open-close for each cardholder. \nExample: \nSuppose a user swipes their card and unlocks a door. Before the door opens and closes, another person swipes \nhis card. If this box is checked, the system treats the second swipe as an access request. If you leave this box \nunchecked, the system ignores the second swipe. This feature is useful at high volume doors where you don't \nwant to wait for the door to close after every access. \n• \"Ordinary\" doors — multiple person access on each access cycle — select the Readers Are Continuously \nActive check box. \n• \"Turnstiles\" (or Mantraps) — one person access only on each access cycle — clear the Readers Are \nContinuously Active check box. \nSelecting this option for a Reader on an iSTAR Area Door permits the Area to be configured for Escorted Access \n... [truncated, 3306 chars — for the full page use /api/corpus/document/EFTA01225932/428 or ?id=EFTA01225932&page=428]", "char_count": 3306}, {"efta_number": "EFTA01225932", "page_number": 429, "text_content": "STAR Door Editor \nFigure 165: STAR Door Timing Tab \ngame \nQtroinP4C. \nl'Ara Gay 1 \nParebon Dalai \nr M,rterku-ce /144c \nTwner Zone 04105 CO) Eastern Tine NS 1Crada) \nGinn Tyro I kn. Zones I Double Save I Tnflen I Cet0e I Status I boar Montomg I Use Oenlea Cc•Ws I Slat ewe' I \nTenets \nOtero \nDelay,Relodc (made) \nStan Time (e•cOnde: 10 \n!hock Tore (maxis): IS \nManes Stet Time oilman). I00 CO 00 \nSSA Eipritaos %Wag Tin (rein)' \n0 Ce\nrn\n02:c Owe Oletounce MI*0/10644: \nDOW OW fileCe TIMM° \nDow Wt.:liana Tema/10sec): \nWawa use Shunt EagleOutput \nr Delay Relock *hie [Ica wen ater veiled access \nF Se rt Oar \nShute Time \nJ \nSetting iSTAR Door Timing \nThe following timers and check boxes appear on the iSTAR Door Timing tab: \n1. Delay Relock - Type the number of seconds to delay door Sock after the door is opened (after a request to exit, \nfor example). The range in seconds is 0 to 999 seconds (0:16:39); the default is 0. \n2. Shunt Time - Type the number of seconds that the door can remain open before a door held open alert is \ngenerated within the range of 0 to 999 seconds (0:16:39); the default is 10 seconds. \n3. Unlock Time - Type the number of seconds the Door remains unlocked after a valid card swipe, RTE activation, \nor momentary unlock within the range of 0 to 255 seconds (0:4:15); the default is 5 seconds. \nNOTE \nA value of 0 actually represents a token unlock time (300 microseconds) that can be used, for \nexample, to unlock a turnstile so that one person may pass, but tailgating is not possible. \nAlso, a setting of 0 disables Momentary Unlock manual actions, so choose a non-zero Unlock Time if \nyou need to use Momentary Unlock with this Door. \n430 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226361\n", "char_count": 1741}, {"efta_number": "EFTA01225932", "page_number": 430, "text_content": "STAR Door Edrtor \n4. Alternate Shunt Time - Type the number of hours, minutes, and seconds the Door can remain open before a \ndoor held open alert is generated after a valid card swipe by a cardholder with the Alternate Shunt flag set in \ntheir personnel record (see the C• CURE 9000 Personnel Configuration Guide) within the range of \ndefault/minimum: 0:0:0; maximum:18:0:0 (18 hours). This value is used only if it is set to a greater time than the \nShunt time value. \n5. Shunt Expiration Warning Time - If set, the Shunt expiration relay is fired regardless of the shunt time used. If \nset to 0 (the default), the Shunt expiration relay will only be fired if the Alternate shunt time was used. The Shunt \nExpiration Warning has a range of 000 to 0:4:0 (4 minutes). \n6. Door Close Debounce Time - Setting this value to 0 indicates that there is no timer. The range is from 0 to 255 \nseconds in units of 0.1 seconds. \n7. Door Open Grace Time - Also known as Door Open Debounce Time. Setting this value to 0 indicates that \nthere is no timer; as soon as the door opens, door forced open is reported. The range is from 0 to 255 seconds in \nunits of 0.1 seconds. \n8. Door Unlock Grace Time - Specifies the time that the system waits for a door open signal after the door unlock \ntime has expired. This timing prevents a false door forced message in situations where signals are nearly \nsimultaneous. The range is from 0 to 100 seconds in units of 0.1 seconds. \n9. Always Use Shunt Expire Output - If this check box is selected, the Shunt expiration relay is fired regardless of \nthe shunt time used. If the Shunt Expiration Warning Time is set to 0 (the default), the Shunt expiration relay \nshall only be fired if the Alternate shunt time was used. \n10. Delay Relock While Door Open After Valid Access - If access is valid, delays the relock of the door until the \ndoor closes, if this check box is selected. This differs from standard Sock operations, where Sock occurs when \nthe door opens and the S\n... [truncated, 2968 chars — for the full page use /api/corpus/document/EFTA01225932/430 or ?id=EFTA01225932&page=430]", "char_count": 2968}, {"efta_number": "EFTA01225932", "page_number": 431, "text_content": "STAR Door Edrtor \nFigure 166: STAR Door Areas& Zones Tab \nthese \nilea:mar \n[Are Goy 1 \nProem Oft \nr gentenarce Mode \nTens Zone 3MT05-0% Eastern Tme 0./S &Credal \nGerry I Tnwp Mega Zones I DoLbe Swot I Tet9e3 I Goa l Status I Dose Mcreeire I User Neve Sees I Ass rages \nAmes \nInesece Zones \nEntry Arert\nEwen, I \nsenesce Zone I \nIv* Onesece \nDooley Him I \nI !le Areas & Zones tab has the read-only fields shown in iSTAR Door Definitions on Page 446. \niSTAR Door Double Swipe Tab \nIn addition to the typical, single-swipe use of a card at a door's card reader, the Double Swipe tab (see Figure 167 on \nPage 433) allows you to configure a door to enable its reader to interpret a double card swipe as a means to toggle \nthe door's lock state for an indefinite amount of time. Configure the selected door for Double Swipe by setting a \ncombination of privilege, personnel group, priority level, and schedule. As with other security objects in the system, \nevents, manual actions or causes with higher priorities can override a cardholder's double swipe. The double swipe \nlock/unlock messages display in the journal and in the cause list. \nNOTE \nIf the door being configured is assigned a Schlage Wireless Reader, the contents of this tab are disabled \nbecause the Schlage readers do not support double swipe. \n432 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226363\n", "char_count": 1378}, {"efta_number": "EFTA01225932", "page_number": 432, "text_content": "STAR Door Edrtor \nFigure 167: 'STAR Door Double Swipe Tab \nNOTE \nNOTE \nThe Double Swipe feature requires iSTAR firmware version 43 or later for Classic, Pro, or eX. \nDo not configure Double Swipe on a Door that is used with Antipassback, Escort, Conditional \nAccess, Areas, or Intrusion Zone functionality. \nTo Configure the iSTAR Door Double Swipe Tab \nFollow the steps to access the door editor in the Admin application, as described in Creating a Door on Page 405. \nThe selections below appear on the Door Configuration dialog box - Double Swipe tab (see Figure 167 on Page 433). \nMake the Double Swipe door configuration selections from these options. \n1. Permission to Cardholders area: \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n433 \nEFTA01226364\n", "char_count": 765}, {"efta_number": "EFTA01225932", "page_number": 433, "text_content": "iSTAR Door Editor \na. None - If None is selected, Double Swipe is not enabled at the door. If Double Swipe is active at the door, you \nmay turn off Double Swipe by selecting None on this tab. Normal card swipe access at the reader is still in \neffect, if so configured. \nb. With clearance - Selecting this option enables the door to require that cardholders who use Double Swipe at \nthe reader must have a clearance for access to this particular door configured for them in the Personnel screen, \nClearances tab. \nc. With clearance and in personnel group - Selecting this option will require that cardholders who use Double \nSwipe at the reader must have a clearance for access to this door configured for them in the Personnel screen, \nClearances tab, and they also must be in the personnel group whose members have access to this door. \nd. Personnel Group - Click El to select a personnel group. If a group is selected for Double Swipe, each \ncardholder who uses Double Swipe at the reader must be a member of the selected Personnel Group. The \npersonnel group may be configured in the Configuration pane, Group dialog box. \n2. Options area: \na. Priority (0 - 200)- Select a Priority for Double Swipe requests at the door. The default is 75. \nIn the case of a manual action with higher priority than the priority configured for the door, the manual action \ntakes precedence. If the door's priority is higher, the double swipe takes precedence. For two actions with the \nsame priority, the most recent one takes precedence. \nNOTE \nIf you change the Priority setting on the Double Swipe tab while a double swipe cause is active for the \ndoor, that cause will be removed from the cause list, and any the double swipe action is canceled. \nb. Double Swipe Cancellation Schedule - Click GJ to select a schedule. The cancelling schedule will delete any \nexisting double swipe causes on the door at the start of the schedule. Any double swipe actions currently in \neffect will be canceled. \n3. Click Save a\n... [truncated, 3292 chars — for the full page use /api/corpus/document/EFTA01225932/433 or ?id=EFTA01225932&page=433]", "char_count": 3292}, {"efta_number": "EFTA01225932", "page_number": 434, "text_content": "STAR Door Editor \nb. Select the Double Swipe check box to display Double Swipe messages at the Monitoring Station. If the box is \nunchecked, messages will not display at the Monitoring Station. By default, the Activity Viewer displays all \nthese Message Types. \nc. Click Save and Close . \n5. To edit an existing Activity Viewer pane to display Double Swipe messages at the Monitoring Station, click the \nActivity Viewer tab on the pane, right click and select Properties. The Activity Viewer dialog box displays. \na. Select the Double Swipe check box to display Double Swipe messages at the Monitoring Station. If the box is \nunchecked, messages will not display at the Monitoring Station. By default, the Activity Viewer displays all \nthese Message Types. \nb. Click Save and Close . \nUsing Double Swipe at the Door \nTo Use Double Swipe at a Card Reader: \nDouble Swipe is enabled by: \n■ the cardholder(s) having a clearance to the specific door \n- or - \n• the cardholder(s) having a clearance to the specific door and being a member of the personnel group, if the \n\"With clearance and in personnel group\" option is selected on the Double Swipe tab. \nThe following steps describe how a double swipe at the card reader toggles the door lock, to lock or unlock the door. \nTo Unlock a Door if the Current State is Lock: \nCardholder swipes the card twice at the reader, within the shunt time. \nIf the cardholder has the correct clearance set for access to the door or has the correct clearance and is in the \ncorrect personnel group, the door toggles to Unlock. The card reader displays the state of the door, and the door \nremains unlocked until it is locked again by another double swipe, or by other causes such as manual action, \nscheduled events, and so forth. \nIf the cardholder swipes only once, a Momentary Unlock occurs for an authorized cardholder. \nTo Lock a Door lithe Current State Is Unlock: \nCardholder swipes the card twice at the reader, within the shunt time. \nIf the cardholder has the \n... [truncated, 2686 chars — for the full page use /api/corpus/document/EFTA01225932/434 or ?id=EFTA01225932&page=434]", "char_count": 2686}, {"efta_number": "EFTA01225932", "page_number": 435, "text_content": "STAR Door Editor \niSTAR Door Conditional Access Tab \nThe Conditional Access tab (see Figure 168 on Page 437) allows you to configure a door so that appropriately \nauthorized Personnel can grant access to Personnel without Clearance for that Door. (This tab is available on the \niSTAR Doors Editor only if the Include Personnel Without Clearance in Personnel Downloads option in the \nConditional Access box is selected on the General tab of the door's iSTAR controller editor.) \nNOTE \nThe Conditional Access process can only be started by Personnel Credentials rejected for having no \nClearance at the door. Rejections for Lost, Stolen, Not Active, Expired, or Unknown Card or for \nAntipassback, Occupancy, Lockout, or PIN cause immediate rejection. \nThis feature is usually used on doors into iSTAR Areas where a person inside can grant entry to the Area to \npersonnel lacking clearance, after validating their identities. (In the latter situation, it can also be used in conjunction \nwith Dynamic Area Manager. See the Areas chapter in the C• CURE 9000 Areas and Zones Guide.) \nExample: \nA bank has a secure area that it uses for counting cash. Two authorized employees with clearance for the entry \ndoor (Susan and Tom) have already entered the room and are working. A third employee without clearance \n(Martin) needs to confer with them and swipes his card at the door. Since the door is configured for \nConditional Access, a Conditional Access event is activated and triggers an output inside the room, such as a \nflashing light or bell, to announce that someone wants to enter. Through the glass pane in the door, Susan sees \nthat it is Martin waiting there. She pushes the button on the wall, activating a 'Conditional Access Response' \nevent whose action opens the door. Martin enters the room. (The iSTAR Area Status tab would show that there \nwere currently a total of three people in the area and that one of them had been admitted conditionally.) \nThe iSTAR Area Status tab keeps track of \n... [truncated, 3109 chars — for the full page use /api/corpus/document/EFTA01225932/435 or ?id=EFTA01225932&page=435]", "char_count": 3109}, {"efta_number": "EFTA01225932", "page_number": 436, "text_content": "STAR Door Edrtor \nFigure 168: STAR Door Conditional AccessTab \nt1 \nSa.e expose i,,Sre \ntiane I lib Oca I \nEr-cob:11 1 \nE Mesmence Mode \nIrroZa. IGMTt5.001Eaem Toe (US 6Canedal \nGereSI Tyro Ikea; tart Dade Swve Colchor4 Ames  l 1' mad Gscum i StSus I Doc( Wrong I Wee Definediti \nC ontxrol Axe:: jcMde\nCcndecnel ACCCII LYent \nCont.crol Accen Re:perco I me In :ttor,d: 10 • 1$0t \n10 \nSee iSTAR Door Conditional Access Tab Definitions on Page 449 for definitions of the fields on the Conditional \nAccess tab. \nConfiguring Conditional Access \nTo Configure Conditional Access for this iSTAR Door \n1. Follow the steps to create/edit the iSTAR Pro, eX, Edge, or Ultra controller that this door will be on, as described \nin Creating an iSTAR Controller on Page 124 and in Editing an iSTAR Controller on Page 126. \n2. On the General tab of the iSTAR Controller editor, select the Include Personnel Without Clearance in Personnel \nDownloads option in the Conditional Access box, as described in To Configure the iSTAR Controller General \nTab on Page 143. \n3. Configure the Events needed for the feature: \na. Configure a panel event for this door's controller that will act as the Conditional Access Event on the iSTAR \nDoor Conditional Access tab—and initiate the 'Conditional Access' process. This event should trigger an \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n437 \nEFTA01226368\n", "char_count": 1386}, {"efta_number": "EFTA01225932", "page_number": 437, "text_content": "'STAR Door Editor \noutput, such as a buzzer or flashing light, that notifies appropriate personnel that someone without the \nrequisite clearance wants to go through this door. \nb. Configure a host or panel event with the action Allow Conditional Access Cycle to be activated to open the \ndoor conditionally. \nFor information, see the Events Chapter in the C•CURE 9000 Software Configuration Guide. \n4. Follow the steps to access the iSTAR Door editor in the Administration application, as described in Creating a \nDoor on Page 405, and then open the Conditional Access tab. \n5. Click 0 \nfor Conditional Access Schedule to select the schedule during which Conditional Access is enabled for \nthis door. \n6. Click 0 \nfor Conditional Access Event to select the event that requests Conditional Access at this door for a \nperson without Clearance. (Only panel events within this controller's cluster are available for selection.) \n7. In the Conditional Access Response Time field, enter the number of seconds that the door will wait for the \n'Allow Conditional Access Cycle' event action to open the door after the Conditional Access event entered in the \npreceding field has been activated. (The range is 1 -150 seconds with a default of 10 seconds.) \n8. Click Save and Close to save the settings and close the window, or click Save and New to save the settings and \nconfigure a new door. \niSTAR Door Triggers Tab \nYou can create Triggers for iSTAR Doors using the iSTAR Door Triggers tab. A Trigger executes a specified Action \nwhen a particular predefined condition occurs. When a Trigger is defined, the Actions available depend on the \nproperty selected. The Door Triggers tab is shown in Figure 169 on Page 439. \nSee the following for information on iSTAR Triggers: \n■ Triggers Tab for iSTAR Devices on Page 270. \n■ Defining a Trigger for an iSTAR Device on Page 271. \n■ Removing a Trigger on Page 272 \n438 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226369\n", "char_count": 1975}, {"efta_number": "EFTA01225932", "page_number": 438, "text_content": "STAR Door Edrtor \nFigure 169: STAR Door TriggersTab \nOole bj Sa..e ercir \nWore I \nINOCCIPbCA \nUltra Corr 1 \nAnnan NSA \nr Meontentnce lAxie \nTime Ur* CMT0500)Eadten The (US IC:rola) \nCanna I Teary I Mew & ate Doa Att• TKOSS 'Gavel Sas I Door Wotan; I Us Dined kit I Sae r•9••I \nTn99.1 \n\"Add \nRaton \nPeoparty \nr\nTime Zoe \nI (OW-05 lei Fast I \nUsing Double Swipe to Trigger an Event \nYou can create a trigger to associate Double Swipe activity with the ability to activate an event on a schedule when \nthe door's reader receives a double-swipe to Lock or Unlock. \nTo Create the Trigger for an Event \n1. Navigate to the Triggers tab, as shown in Figure 169 on Page 439. \n2. Click Add on the Triggers tab to create a new trigger. \n3. Click within the Property column to display the browse button C. A window opens, presenting the list of \nproperties for the door. \na. Select the Double Swipe Property to add it to the column. \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n439 \nEFTA01226370\n", "char_count": 994}, {"efta_number": "EFTA01225932", "page_number": 439, "text_content": "'STAR Door Editor \n4. Click in the Value column to display the list of Values associated with the Double Swipe Property. Select either \nLocked or Unlocked as the value for the trigger and add it to the column. Do not select \"Unknown\" as a value \nbecause it is not a valid option and would be ignored. \n5. Click in the Action column to display a drop-down list of actions. Select Activate Event as the action for the \ntrigger and add it to the column. The other actions in the list are not valid for the double swipe trigger and will \nbe ignored. The lower pane on the Triggers tab will display an event entry field that is specific to the selected \nAction. \nFor the combination of Double Swipe Property and Locked or Unlocked Value, Activate Event is currently the \nonly action supported. \n6. In the Event field, click Ei to display a list of pre-configured Events. Click on an event in the list to add it to the \nfield. This Event will occur when the conditions of the trigger are met. \nEvents may be created from the Configuration pane and \"Event\" in the drop-down menu on the Administration \napplication. See the C•CURE 9000 Software Configuration Guide for more information. \n7. Click in the Schedule column, then click [J  to select a Schedule to associate with the trigger. Notice that when \nyou click in the Schedule column, the details of the Event you selected display in the Details column. If the event \nhas no description entered, the Details cell will remain empty. \nSchedules may be created from the Configuration pane and \"Schedule\" in the drop-down menu on the \nAdministration application. \n8. Navigate to another tab or click Save and Close to save the trigger, or click Save and New to open a new door \neditor. \niSTAR Door Status Tab \nThe Door Status tab (see Figure 170 on Page 441) provides a read-only listing of critical information about the \noperational status of the selected Door including: \n■ Alarm State - displays the values Normal, Forced, Held Open, or Unknown. \n■ Open\n... [truncated, 2586 chars — for the full page use /api/corpus/document/EFTA01225932/439 or ?id=EFTA01225932&page=439]", "char_count": 2586}, {"efta_number": "EFTA01225932", "page_number": 440, "text_content": "STAR Door Edrtor \nFigure 170: iSTAR Door Status Tab \nMAR bee . Iteglead Sere \n_m C\" \na She and Clot k!sn red Nes \nbre btrrocrlotke \nberocrace \nPriem Wait \n&Jekeence Mk* \nUwe Odred AMY I Moor Marammm I State .a\nGoma, imp I  Mao Lbw  %Mg &me I CcoMmelkoma IISImni I Goa \nOrr.: gem \nUrn Stet (Kneen \n°pie MMA Urkre, \nMole lkimm \nOade Siam Lock gam Ur known \nCmdmnal Access Mode \nUrkremn \nNavigate to the State Images tab or click Save and Close. \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n441 \nEFTA01226372\n", "char_count": 516}, {"efta_number": "EFTA01225932", "page_number": 441, "text_content": "STAR Door NIonnoring Tab \niSTAR Door Monitoring Tab \nThe iSTAR Door Monitoring tab lets you configure Doors with additional monitoring inputs and lock sensing \nequipment. You can use this tab to integrate with third-party lock release inputs, such as fire and crash bar devices, \nthat control emergency exit from C•CURE 9000 doors. For more information about Door Monitoring, see \nUnderstanding Advanced Door Monitoring on Page 458. \nFigure 171: Door Monitoring Tab \n2S1 \nS. in, \nk !St.* en:11 \nire Coy 1 \nNation os.s \nr \ngam:ere-co Mode \nT.me Zor• 4/4T-05 00) Eastern Tme (US 4 Cavdal \nGrata I Mind ken Zones I Co-as Svc< I Tann I Gaps I Slaw. Nce \nIUserDeewF<tIArera;eaI \ne ra;e: \n' .t4cl \nMpa \nTy* \np \nTimes \ncptah ay Chart, Timallil0 Wont) I \nE•tatl senor Charge Tern (1110 1000.0 f \nLech ear Cheer Time (MO 5CS)\nCan, Setup C hove lime (M0 scant) \nCsSm 5.ie A Charge Time (110 pecceds) \n0531 So% e Chance Tone (V10 scat) I .\nRTE Chanpa Time MO seconds) I \nSee Advanced Door Monitoring Definitions on Page 461 for definitions of the fields on the Door Monitoring tab. \niSTAR Door State Images Tab \nThe State Images tab (shown in Figure 172 on Page 443) provides a means to change the default images used to \nindicate controller states. \nAIM\nTo Change an Image \nI. Double-click the existing image. \n442 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226373\n", "char_count": 1373}, {"efta_number": "EFTA01225932", "page_number": 442, "text_content": "STAR Door NIonnoring Tab \nA Windows Open dialog box appears allowing you to browse for a folder in which you have placed \nreplacement images. \n2. When you locate the replacement image, select it to add it to the image listing. \n3. To restore the default image, right-click the new image and select Restore Default. \nFigure 172: STAR Door State Images Tab \nx \nka Cede And Oare k's Sot ind \npn vox I \nMCA*,  Dna \nItormnarce MS. \nIrmo Zane 411TC/501i Eaton Tree pLIS Knew \nGrint I him I Mailer \nI Cbaks Sr.. I Taxa I Gee I &a.. I Ow \n0girdel Asa Stesona. \n4. Click Save and Close o return to the Hardware pane. \niSTAR Door Visitor Management tab \nThe iSTAR Door Visitor Management tab lets you configure Doors with Visitor Management Actions, so that you \ncan automatically Check-in and Check-out Visitors. \nFor more information about Check-in and Check-out of Visitor via Visitor Management, see the C•CURE 9000 \nVisitor Management Guide. \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n443 \nEFTA01226374\n", "char_count": 1010}, {"efta_number": "EFTA01225932", "page_number": 443, "text_content": "STAR Door Monitoring Tab \nFigure 173: STAR Door Visitor Management tab \nOSTAR Door - door for visits \nMUD \ncaw. snel Eire, \nA \nft-A Now \nRama d:oi to, vt:IS \naecapbon \nF Ran:memo Mode \nGeneral I Timing I Ames & Zones I Dottie Swpe I Tigris' Groups I Slalus I Doot Monlonno I Uset Defined Fields\nVista Management I Siete images I \nAdd Action \n>Remove Action \nVititOlMansgemere Actin, \nDvecton \nSched.le \nTo Configure a Door Action for Check-In \n1. In the C•CURE 9000 Admin Client, navigate to the Door you wish to configure. \n2. Click the Visitor Management tab. \n3. Click Add Action. \n4. Chose the Visitor Management Action Check Visitors In. \n5. Select the Direction for the action to take place. \n• Choose In for Visitors to Check-in using an inbound reader. \n• Choose Out for Visitors to Check-in using an outbound reader. \n• Choose In and Out for Visitors to Check-in using either the inbound or outbound reader. \n6. Select a Schedule for the action to be active. \n7. Click Save and Close \n -GM \nTo Configure a Door Action for Check-out \n1. In the C•CURE 9000 Admin Client, navigate to the Door you wish to configure. \n2. Click the Visitor Management tab. \n444 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226375\n", "char_count": 1233}, {"efta_number": "EFTA01225932", "page_number": 444, "text_content": "STAR Door Monitoring Tab \n3. Click Add Action. \n4. Chose the Visitor Management Action Check Visitors Out. \n• Check Out Visitors and Return Badge. \n5. Select the Direction for the action to take place. \n• Choose In for Visitors to Check-out using an inbound reader. \n• Choose Out for Visitors to Check-out using an outbound reader. \n• Choose In and Out for Visitors to Check-out using either the inbound or outbound reader. \n6. Select a Schedule for the action to be active. \n7. Click Save and Close \nTo Configure a Door Action for Check-out \nThis presumes that a Badge Return mechanism is set up at the Check-out reader. \n1. In the C•CURE 9000 Admin Client, navigate to the Door you wish to configure. \n2. dick the Visitor Management tab. \n3. dick Add Action. \n4. Chose the Visitor Management Action Check Visitors Out. \n• Check Out Visitors and Return Badge. \n5. Select the Direction for the action to take place. \n• Choose In for Visitors to Check-out and Return the Badge using an inbound reader. \n• Choose Out for Visitors to Check-out and Return the Badge using an outbound reader. \n• Choose In and Out for Visitors to Check-out and Return the Badge using either the inbound or outbound \nreader. \n6. Select a Schedule for the action to be active. \n7. dick Save and Close \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n445 \nEFTA01226376\n", "char_count": 1350}, {"efta_number": "EFTA01225932", "page_number": 445, "text_content": "STAR Door Definitions \niSTAR Door Definitions \nThe definitions of the various fields and buttons on the Door dialog box for iSTAR doors are given in the tables \nbelow. \nTable 99: STAR Door General Tab Definitions \nField/Button \nDescription \nName \nUse the Identification box to enter a name (up to 100 characters long) and brief description of the door you are configuring. \nDescription \nAdescription of the door that you are configuring. \nMaintenance \nMode \nClick to put the iSTAR door into Maintenance Mode. See Chapter 2: Maintenance Mode for more information. \nLocation \nController \nThis read-onty field displays the STAR Controller that is connected to the Door. \nHardware \nDoor Switch \nMonitor \nClick ri  for the Door Switch Monitor. When you click this button to select an input to assign to the Door Switch Monitor, a \nbrowser opens presenting a list of inputs available for the controller. Click an Input to select it and add it to the entry field. \nDoor Lock \nRelay \nClick 0 \nfor the Door Lock Relay. When you click this button to select an input to assign to the Door Lock Relay, a browser \nopens presenting a list of outputs available for the controller. Click an Output to select it and add it to the entry field. \nAlternate \nShunt Relay \nClick in\n for the Alternate Shunt Relay. When you click this button to select an output to assign to the Alternate Shunt \nRelay. a browser opens presenting a list of outputsavailable for the controller. Click an Output to select it and add it to the entry \nfield. Timing for thisoutput is set on the STAR Door Timing Tab on Page 429. Cardholderswith the Atternate Shunt ADA setting \nenabled on the Personnel General tab (See the C•CURE 9000 Personnel Configuration Guide) are granted the additional \nAtternate Shunt time before a door held alarm is generated. \nShunt \nExpiration \nRelay \nClicks for the Shunt Expiration Relay. When you click this button to select an output to assign to the Shunt Expiration \nRelay. a browser opens presenting a list \n... [truncated, 3346 chars — for the full page use /api/corpus/document/EFTA01225932/445 or ?id=EFTA01225932&page=445]", "char_count": 3346}, {"efta_number": "EFTA01225932", "page_number": 446, "text_content": "STAR Door Definitions \nTable 99: STAR Door General Tab Definitions (continued) \nField/Button \nDescription \nUnlock Door \non RTE \nSelect the Unlock Door on RTE check box to unlock the door at a Request to Exit. \nShunt DSM \nWhile RTE is \nActive \nSelect the Shunt DSM While RTE is Active check box to Shunt Door Switch Monitor While Request to Exit is Active. \niSTAR Door Timing Tab Definitions \nTable 100: STAR Door Timing Tab Definitions \nField/Button \nDescription \nTimers \nDelay Retook \nType the number of seconds to delay door rebck after the door is opened (after a request to exit, for example). The range in \nseconds is 0:0:0 to 0:16:39 (999 seconds); the default is 0:0:0. \nShunt Time \nShunt Time- type the number of seconds that the door can remain open before a door held open alert is generated within the \nrange of 0:0:0 to 0:16:39 (999 seconds); the default is 0:0:10 (10 seconds). \nUnlock Time \nUnlock Time- type the number of seconds the Door remains unlocked after a valid card swipe. RTE activation, or momentary \nu n lock with in the range of 0:0:0 to 0:4:15 (255 seconds); the default is 0:0:5 (5 seconds). \nAlternate \nShunt Time \nAlternate Shunt Time- type the number of hours, minutes. and seconds the Door can remain open before a door held open \nalert isgenerated after a valid card swipe by a cardholder with theAlternate Shunt flag set in their personnel record (Thisvalue \nis used onty if it is set to a greater time than the Shunt time value) within the range of defauttiminimum: 0:0:0; maximum:18:0:0 \n(18 hours). \nShunt \nExpiration \nWarning Time \nif set. the Shunt expiration relay fires regardless of the shunt time used. If set to 0 (the default). the Shunt expiration relay fires \nonty if the Alternate shunt time is used. The Shunt Expiration Warning has a range of 0:0:0 to 0:4:0(4 minutes). \nDoor Close \nDebounce \nTime \nSpecifies the time (in 1/10th of a second intervals) that the C•CURE 9000 ignores DSM inputs, to allow for bouncing doors. \nSetting thisvalue to 0 in\n... [truncated, 3070 chars — for the full page use /api/corpus/document/EFTA01225932/446 or ?id=EFTA01225932&page=446]", "char_count": 3070}, {"efta_number": "EFTA01225932", "page_number": 447, "text_content": "STAR Door Definitions \nTable 100: STAR Door Timing Tab Definitions (continued) \nField/Button \nDescription \nDelay Relock \nWhile Door \nOpen After \nValid Access \nIf access is vabd, delays the relock of the door until the door closes, if this check box is selected. \nThis differs from standard rebck operations, where rebck occurs when the door opens and the relock delay expires \nIf the door is open, the lock is energized. The C•CURE 9000 sends an alarm when the shunt time expires. \nShunt Door \nfor full Shunt \nTime \nIf this option is selected, the door is shunted for the full shunt time. If selected with Delay rebck while door open for valid access, \nthe lock is energized and the door unlocked for the full shunt time, regardless of whether the door is open or closed. \niSTAR Door Areas and ZonesTab Definitions \nTable 101: STAR Door Areas 8. Zones Tab Fields \nBox/Fields \nDescription \nAreas \nEntry Area \nName of Area to which this Door is an Access In' Door. \nExit Area \nName of Area to which this Door is an 'Access Out' Door. \nIntrusion Zones \nIntrusion Zone \nName of STAR Intrusion Zone this Door is assigned to \nZone Direction \nI n indicates that this Door is assigned as an Entrance Door for the Intrusion Zone. \nOut indicates that this Door is assigned as an Exit Door for the Intrusion Zone. \nDisplay Name \nDisplays the name you entered for this Door on the STAR Intrusion Zones Editor General tab. \niSTAR Door Double Swipe Tab Definitions \nTable 102: STAR Door Double Swipe tabdefinitions \nField/Button \nDescription \nPermission to Cardholders \nNone \nIf this option is selected, Double Swipe isnot enabled at the door. If Double Swipe is active at the door, you may turn off Double \nSwipe by selecting None on this tab. Normalcard swipe access at the reader is still in effect, if so configured. \nWith clearance \nSelecting this option will enable the door to require that a cardholder who uses Double Swipe also has Double Swipe clearance \nconfigured for them in the Personnel screen. Clea\n... [truncated, 2085 chars — for the full page use /api/corpus/document/EFTA01225932/447 or ?id=EFTA01225932&page=447]", "char_count": 2085}, {"efta_number": "EFTA01225932", "page_number": 448, "text_content": "STAR Door Definitions \nTable 102: STAR Door Double Swipe tab definitions (continued) \nField/Button \nDescription \nWith clearance \nand in \npersonnel \ngroup \nSelecting this option will require that a cardholder who uses Double Swipe at the reader have a Double Swipe clearance set \nand also be in the personnel group that may be selected in the next fields \nPersonnel \ngroup \nClick[] to select a person nel grou p whose members may be admitted on Double Swipe as long as each member has the \nproper clearance set for them in the Personnel screen. Clearances tab. \nOptions \nPriority \nSelect a priority (from 0 - 200) for Double Swipe requests at the door. \nIn the case of a manual action with higher priority than the priority configured for the door, the manual action takes precedence. \nIf the door's priority is higher, the double swipe takes precedence. For two actions with the same priority, the most recent one \ntakes precedence. \nDouble Swipe \nCancellation \nSchedule \nClick in to select a schedule. The cancelling schedule will delete any existing double swipe causes on the door at the start of \nthe time spec. Any dou ble swipe actions currently in effect will be cancelled. \niSTAR Door Conditional Access Tab Definitions \nTable 103: STAR ConditionalAccess Tab Definitions \nField/Button \nDescription \nConditionalAccess \nSchedule \nClick ... I to select the schedule during which the door is 'ConditionalAccess-enabled'. Thiscan be any schedule in the \nsame time zone as the controller. \nThe !STAR Door Status tab will indicate whether ConditionalAccess is enabled or not. \nConditionalAccess \nEvent \nClick n \nto select the event that requests 'Conditional Access' at this door for a person without Clearance. \nOnly panel events within this controller's cluster are available for selection. This event cannot be the same one that \ntargets thisdoor with the Allow ConditionalAccess Cycle' action—lets the person through the door. \nConditionalAccess \nResponse Time \nSpecifies the time (in seconds) t\n... [truncated, 2496 chars — for the full page use /api/corpus/document/EFTA01225932/448 or ?id=EFTA01225932&page=448]", "char_count": 2496}, {"efta_number": "EFTA01225932", "page_number": 449, "text_content": "STAR Door Definitions \niSTAR Door Triggers Tab Definitions \nTable 104: STAR Door Triggers Tab Definitions \nField/Button \nDescription \nTriggers \nAdd \nClick Add in the Triggers tab to create a new trigger. \nRemove \nClick the row selector . , then click Remove to delete a trigger. \nProperty \nClick with in the Property column to display(, When you select this button, the Property browser opens presenting \nproperties available for the controller. Click a Property to select it and add it to the column. \nValue \nC lick with in the Value column to display a drop-down list of Values associated with the Property that you have selected. Click on \na Value that you want to include as a parameter for the trigger to add it to the column. \nAction \nClick with in the Action column to display a drop-down list of valid actions. Click on an Action that you want to include as a \nparameter for the trigger to add it to the column. \nWhen a Trigger is added, an Action must be configured in the Action column. This is the Action that will occur when the object's \nselected Property receives the selected Value. As the Action is selected, the lower pane in the Triggers box will show a \ncorresponding entry field, or group of entry fields, specific to the selected Action.Click ri  to select entries for these fields. Once \nthe field tor group of fields) is completed, the Details column will show information about how the Action has been configured. \nDetails \nDisplays details concerning the security objects that are associated with the selected Action. \nSchedule \nClick within the Schedule oolumn, then click[] to select a Schedule that you want to atcnciate with the trigger. Schedules \nare created in the Configuration Pane. See the C•CURE 9000 Software Configuration Guide for more information. \n450 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226381\n", "char_count": 1861}, {"efta_number": "EFTA01225932", "page_number": 450, "text_content": "STAR Door Definitions \niSTAR Triggers Properties \nTable 105: STAR Triggers Properties \nProperty \nDescription \nAdmit Status \nAdmit \nAdmit Visitor \nReject Visitor \nReject \nDuress \nNoticed Admit \nNoticed Reject \nPre-Admit \nFor any one of theAdmit Status. Mode Status. or Open Status values(see the Value column drop-down list) you \ncan choose one of the following Actions to create a Trigger: \nActivate Event -When this status occurs and the Schedule is Active (you can choose any Schedule). You must seta \nMinimum Activation Time in the Event or the actions in the Event wdi not activate. \nActivate Event Outside Schedule -An event is activated when this status occurs while the Schedule is inactive \n(choose any Schedule). \nActivate Output -Activate an Output when this status occurs (onty works with the Always Schedule). \nPre-Admit status is a special case used to activate a panel Event on a card swipe before the door is opened. It is used \nwith the Activate Event action to activate an Event that can, for example, change the state of an output on the \niSTAR panel. \nMode Status \nUnlocked \nLocked \nNo Access \nMomentary \nUnlock \nOpen Status \nOpen \nClosed \nDouble Swipe Status \nLocked \nUnlocked \nFor anyone of the Double-Swipe Status values(see the Value column drop-down list) you can choose one of the \nfollowing Actions to create a Trigger: \nActivate Event -When this status occurs and the Schedule isActive (you can choose any Schedule). You must seta \nMinimum Activation Time in the Event or the actions in the Event will not activate. \nActivate Event Outside Schedule -An event is activated when this statusoccurswhile the Schedule is inactive \n(choose any Schedule). \nAlarm State Status \nNormal \nForced \nHeld Open \n1. Choose a value for the Property from the Valuescolumn. \n2. Select an Action from the Action drop-down list. \nSee iSTAR Trigger Actions in Table 106 on Page 452. \n3. Select a Schedule by clicking in the Schedule column, then click to select the Schedule that you want to ass\n... [truncated, 2419 chars — for the full page use /api/corpus/document/EFTA01225932/450 or ?id=EFTA01225932&page=450]", "char_count": 2419}, {"efta_number": "EFTA01225932", "page_number": 451, "text_content": "STAR Door Definitions \niSTAR Triggers Actions \nTable 106: STAR TriggersActions \nAction \nDescription \nActivate \nEvent \nSelect an Event to activate when this statusoccurs \nActivate \nEvent \nOutside \nSchedule \nSelect an Event to activate when this status occurs while the Schedule is inactive. \nActivate \nOutput \nSelect an Output to activate when this status occu rs. Must use the Always Schedule. \nArm Event \nSelect an Event to arm. An armed Event can be activated: a disarmed Event cannot be activated. \nArm Input \nSelect an Input to arm. An armed Input can be activated. Adis.armed Input cannot be activated. \nCCTV Action \nSelect a CCTV Action to perform by choosing a CCTV Switch and Command from the Details area. and filling in one or more \nValues for the Command's parameters. \nControl \nAccess \nSelect an Elevator Button which you want the Action to set for controlled access, turning on security restrictions on the use of this \nbutton. \nDeactivate \nEvent \nSelect an Event to be deactivated. If the Event is Active when this action occurs. the action deactivates the Event. \nDeactivate \nOutput \nSelect an Output to be deactivated. If the Output isActive when thisaction occurs. the action deactivates the Output. \nDisable \nKeypad \nCommands \nDisable Keypad Commands on the iSTAR Reader you select in Details. \nDisable PIN \nSet the Reader you select to no longer require that a cardholder perform a card swipe, then enter a PIN to be granted access. \nDisarm \nEvent \nSelect an Event to disarm. A disarmed Event cannot be activated; an Event must be armed to be activated. \nDisarm Input \nSelect an Input to disarm. A disarmed Input cannot be activated; an Input must be armed to be activated. \nEnable \nKeypad \nCommands \nSet the Reader you select to accept Keypad Com ma nds on the reader. \nEnable PIN \nSet the Reader you select to require that a cardholder perform a card swipe, then enter a PIN to be granted access. \nLock Door \nSelect a Door to Lock from the Door field in the Details area. \n452 \nC\n... [truncated, 2066 chars — for the full page use /api/corpus/document/EFTA01225932/451 or ?id=EFTA01225932&page=451]", "char_count": 2066}, {"efta_number": "EFTA01225932", "page_number": 452, "text_content": "STAR Door Definitions \nTable 106: STAR TriggersActions (continued) \nAction \nDescription \nMomentary \nUnlock Door \nSelect a Door to Momentarily Unlock from the Door field in the Details area. \nPulse Output \nSelect an Output to activate for theduration specified in the Outputs Pulse Duration Feld. \nSecure Door \nSelect a Door that you want to secure. A secure Door cannot be unlocked: this action disarms the reader associated with the \nDoor. \nSend Email \nSend an email message to the email address specified in the Details area Recipient Email Address field. You can designate an \nEvent to activate if the email attempt fails. You can click the Message tab to type the text of the message and optionaltychoose to \nsend the date. time. and name of the Event triggered. For Send Email to work. you must configure the Email Server and the \nSender Email Address in Options & Tools>System Variables in the Customer Support area. \nUncontrol \nAccess \nSelect an Elevator Button which you want the Action to set for uncontrolled access. turning off security restrictions on the use of \nthis button. \nUnlock Door \nSelect a Door to unlock from the Door field in the Details area. \nVideo \nCamera \nAction \nSelect a Video Camera Action to perform by choosing a Video Server and Camera from the Details area Camera tab, and \nchoosing one of the following Action Types. \n• Record Camera lets you set a Pre Alarm Time and Post Alarm Time for retrieving recorded video. \n• Camera Preset Command allows you to designate a Camera Preset to activate when this action is triggered. \n• Camera Pattern Command lets you designate a Camera Pattern to activate when this action is triggered. \niSTAR Door Groups Tab Definitions \nTable 107: STAR Door GroupsTab Definitions \nField/Button \nDescription \nGroups \nFor more information about the use of the Toolbar buttons. see Chapter 2. \"Dynamic Views' in the C• CURE 9000 \nData Views Guide \nz D Q51 y ce \nName \nThis oolu m n displays the name entered for the group when it was config\n... [truncated, 2246 chars — for the full page use /api/corpus/document/EFTA01225932/452 or ?id=EFTA01225932&page=452]", "char_count": 2246}, {"efta_number": "EFTA01225932", "page_number": 453, "text_content": "STAR Door Definitions \niSTAR Door Status Tab Definitions: \nTable 108: STAR Door Status Tab Definrbons \nField/Button \nDescription \nAlarm State \nDisplays the values Normal. Forced. Held Open. or Unknown. \nOpen Status \nDisplays the values Open. Closed, or Unknown. \nMode \nDisplays the values Locked. Unlocked, No Access. or Unknown. \nDouble Swipe Lock Status \nIndicates the current statusof a door configured for Double Swipe access: Locked. Unlocked, or Unknown. \nIf the door is not configured for double swipe access. the field displays Unknown. \nCond Mona lAccess Mode \nDisplaysthe valuesTrue. False. or Unknown. \niSTAR Door State Images Tab Definitions: \nTable 109: STAR Door S ate Images Tab Definrbons \nField/Button \nDescription \nField/Button \nDescription \nUnknown \nLocked \nForced \nUnlocked \nIllsal \n. \nHeld Open \nNo Access \nUl \nOpen \nMomentary Unlock \n■ \n454 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226385\n", "char_count": 931}, {"efta_number": "EFTA01225932", "page_number": 454, "text_content": "STAR Aperio Door Editor \niSTAR Aperio Door Editor \nYou use the iSTAR Aperio Door editor to configure iSTAR Aperio Doors. \niSTAR Aperio Doors are created automatically when you configure and enable an iSTAR Aperio Reader (see iSTAR \nAperio Reader Editor on Page 264). You cannot manually create an iSTAR Aperio Door. \nIf you delete an iSTAR Aperio Door, the iSTAR Aperio Reader associated with the door is also deleted. \nNOTE \niSTAR Aperio Doors do not support manual actions for Lock, Unlock, and Momentary Unlock. \nYou cannot create Door Groups that combine iSTAR Aperio Doors with other types of iSTAR Doors. \nThe iSTAR Aperio Door Editor includes the following tabs: \n■ iSTAR Door General Tab on Page 427 \n■ iSTAR Door Timing Tab on Page 429 \n■ iSTAR Door Triggers Tab on Page 438 \n■ Groups Tab for Hardware Devices on Page 28 \n■ iSTAR Door Status Tab on Page 440 \n■ iSTAR Door Visitor Management tab on Page 443 \n■ iSTAR Door State Images Tab on Page 442 \nC•CURE 9000 Hardware Configuration Guide \nChapter 10 \n455 \nEFTA01226386\n", "char_count": 1032}, {"efta_number": "EFTA01225932", "page_number": 455, "text_content": "STAR Ardor() Door Edrtor \n456 \nChapter 10 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226387\n", "char_count": 98}, {"efta_number": "EFTA01225932", "page_number": 456, "text_content": "11 \nConfiguring Advanced Door Monitoring \nThis chapter explains the concepts of Advanced Door monitoring, and also includes the procedures that are used to \ncreate various types of monitored doors. \nIn this chapter \nUnderstanding Advanced Door Monitoring \n458 \nHardware Requirements \n460 \nAdvanced Door Monitoring Definitions  \n461 \nAdvanced Door Monitoring Components  \n463 \nAdvanced Door Monitoring Configurations  \n467 \nConfiguration Overview \n473 \nConfiguring an Advanced Door \n474 \nUnderstanding Timing \n481 \nMonitoring Door Activity  \n486 \nUnderstanding Door Alarms  \n487 \nAdvanced Door Monitoring Details  \n495 \nDoor Monitoring Screen \n496 \nC•CURE 9000 Hardware Configuration Guide \nChapter H \n457 \nEFTA01226388\n", "char_count": 719}, {"efta_number": "EFTA01225932", "page_number": 457, "text_content": "Understanding Advanced Door Monitoring \nUnderstanding Advanced Door Monitoring \nAdvanced Doors are C•CURE 9000 doors that provide increased security for sites with complex requirements, like \nairports or hospitals. Standard Doors use the Door State Monitor (DSM) to monitor for Admit Used, Admit Unused, \nDoor Forced and Door Held. \nAdvanced Doors support additional monitoring inputs and lock sensing equipment. Advanced Doors also integrate \nwith third-party lock release inputs, such as fire and crash bar devices, that control emergency exit from C•CURE \n9000 doors. \nFeatures \nUse Advanced Door Monitoring to configure: \n■ Multiple inputs - Advanced Doors provide up to 16 inputs, 14 more than on a standard door configuration. \n■ More complex door configurations - including single- and double-leaf doors with multiple DSM or Request To \nExit (RTE) inputs. \n■ Lock sensing devices - to monitor locking on magnetic bonds, bolts, and cams. \n■ Integrated lock releases - to integrate door unlocking with fire, crash bar, power fail, and key switch inputs. \n■ Special events and actions - to create keypad commands that lock, unlock, and secure doors for a specific time \nperiod. \n■ Alarm Suppression and RTE control on a per door basis. \n■ Enhanced Shunt control. \n■ Grace and change timing options - to fine tune C•CURE 9000 timing to avoid the effects of 'door bounce' and to \ncorrect other door timing situations at the site. \n■ Journal reports and Monitor Station activities - to manage the system and monitor door activity. \n■ Additional Event Actions related to Advanced Doors. \n458 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226389\n", "char_count": 1660}, {"efta_number": "EFTA01225932", "page_number": 458, "text_content": "Understanding Advanced Door Monitoring \nExample: \nFigure 174 on Page 459 shows a double-leaf Advanced Door, configured into A and B sides. Each side \ncontains a maglock, bond sensor, and DSM input that connects to RM4 modules in a nearby junction box. \nAccess on the public side of the door is controlled using the public-side read head. This read head is also \nconfigured to accept keypad commands that allow personnel to lock and unlock the door for specific time \nintervals. Exit from the secure side of the door is controlled by the secure-side read head. \nLocks can be released for fire alarm, crash bar, power failure, or manual key switch. Inputs from the fire pull \nand key switch over-ride are shown connected to an 1/8 board in the local junction box. \nFigure 174: Typical Advanced Door Configuration \n-41 \nTo ISTAR ACM \nJunction Box \nPM Bus RS -485 \nIN \nReader \nSecure Side \nRD • \nRM4 1 \nRDR\nBond MAG Lock \nSensor \nB Side \nDSM \nDSM \nUT \nMAG Lock Bond \nSensor \nA Side \nOM • \n1•• • \nu \n• \nReader \nPublic Side \nFire \nPull \nKey \nOverride \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n459 \nEFTA01226390\n", "char_count": 1118}, {"efta_number": "EFTA01225932", "page_number": 459, "text_content": "Hardware Requirements \nHardware Requirements \nThe following guidelines apply to Advanced Doors: \n• Advanced Door monitoring is available only on iSTAR configurations. \n• Advanced Door inputs can be any mix of lock sensors, lock releases, or DSM or RTE connections. \n• Each Advanced Door supports up to 16 input connections. However, the number of available inputs per door is \nlimited by the number of doors in the configuration and the input capacity of the fully loaded iSTAR controller. \n• All Door components, Readers, Inputs, and Outputs, must reside on the same Controller. The table below shows \nthat some controllers may not have enough Inputs for the maximum configuration. In actual practice, these \nlimits will rarely, if ever, be reached., \nTable 110: Maximum Inputs per STAR \nController \nMax \nDoors \nMax \nAdvanced \nDoor Inputs \nMax Inputs \non Controller \nResult \niSTAR Ultra \n16 \n16 x 16 =256 \n336 \nAdequatelnputs \nSTAR Pro \n16 \n16 x 16 =256 \n192 \n-64 Inputs \niSTAR eX8 Door \n8 \n8 x 16 = 128 \n96 \n- 32 Inputs \niSTAR eX4 Door \n4 \n4 x 16 =64 \n88 \nAdequatelnputs \nSTAR Edge 4 Door \n4 \n4 x 16 =64 \n64 \nAdequate Inputs \nSTAR Edge 2 Door \n2 \n2x16=32 \n32 \nAdequatelnputs \nSTAR Edge 1 Door \n1 \n1x16=16 \n4 \n-12 Inputs \n• Advanced Doors support the same number and types of outputs as standard doors —which are as follows: \n• Door Latch Relay (1) \n• Alternate Shunt (ADA) Relay (1) \n• Shunt Expiration warning Relay (1) \n480 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226391\n", "char_count": 1496}, {"efta_number": "EFTA01225932", "page_number": 460, "text_content": "Advanced Door Monitoring Definitions \nAdvanced Door Monitoring Definitions \nNew Definitions, Acronyms, and Abbreviations \n■ Lock Sensor - An input that monitors the state of the lock on a door. This is not the same as the Door Switch \nMonitor (DSM) that monitors whether the door is physically open or closed. \n• Bond Sensor - A type of lock sensor input that monitors the condition of a magnetic lock on door. A normal \nbond sensor input will be active when the door is unlocked (meaning that the door latch relay is active), \nregardless of whether the door is open or closed, but will also be active when the door is open, regardless of \nwhether the door is unlocked or not unlocked. In other words, it should be active when the door is unlocked \nand/or when the door is open. The bond sensor should not be active when the door is closed and locked. \n• Cam Detector - A type of lock sensor input that monitors the condition of the cam on an electric strike on a \ndoor. A normal cam detector input will be active when the door is unlocked. The Cam detector should not be \nactive when the door is locked. \n• Latch Bolt Detector - A type of lock sensor input that monitors the condition of a latch bolt on an electric \nstrike on a door. A normal latch bolt will be active or inactive while the door is unlocked, and will be active \nwhen the door is open. The latch bolt should not be active when the door is closed and locked. \n■ Lock Release Device - A external device that may unlock a door that is also controlled by the access control \nsystem. Indication that the lock release device is active will be supplied through an input. \n• Fire Alarm Lock Release - An input that indicates that the fire alarm system has unlocked the door. \n• Crash Bar Lock Release - An input that indicates that the door has been unlocked by local crash bar / panic \nhardware. \n• Key Switch Lock Release - An input that indicates that the door has been unlocked by local key switch \noverride. \n• Power Fail Lock Release \n... [truncated, 2659 chars — for the full page use /api/corpus/document/EFTA01225932/460 or ?id=EFTA01225932&page=460]", "char_count": 2659}, {"efta_number": "EFTA01225932", "page_number": 461, "text_content": "Advanced Door Monitoring Definitions \n2. When the door is Closed and Unlocked, all of the sensors are active except for the DSM because the Door is still \nclosed. \n3. When the door is Open and Unlocked, all of the sensors are active including the DSM because the Door is now \nopen. \n4. When the door is Open and Locked, all of the sensors are active except for the Cam Detector because the Door is \nLocked. \nIn this case, the Latch Bolt Detector is active because the door is Locked. When the Latch Bolt Detector is active, \nalong with the door being open, there is a possibility of damaging the door frame. The Latch Bolt lock is like a \ndead bolt in that the bolt is extended when the door is locked. \n482 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226393\n", "char_count": 776}, {"efta_number": "EFTA01225932", "page_number": 462, "text_content": "Advanced Door Monitoring Components \nAdvanced Door Monitoring Components \nIn addition to standard door components, Advanced Doors support: \n■ Lock sensor devices \n■ Lock release devices \n■ Alarms based on lock sensor, lock release, and multiple DSM inputs to the C•CURE 9000 \n■ Expanded Door Triggers \n■ Expanded Event Actions \nLock Sensor Devices \nA lock sensing device monitors the state of a door lock. \nTable 112 on Page 463 shows the types of lock sensing devices that can be configured on an Advanced Door. \nTable 112: LockSensing Devices \nLock Sensing Device \nFunction \nBond sensor \nklon dors the condition of a magnetic lock on a door. \nCam detector \nMonitors the condition of the cam on an electric strike on a door. \nLatch bolt detector \nMonitors the condition of a latch bolt on an electric strike on a \ndoor. \nLock Release Devices \nA lock release device is a third-party device that controls door unlock activities. Lock release devices operate \nindependently from C•CURE 9000 and function even if the C•CURE system is not running. \nTo inter-operate, the lock release device has an output, called a lock release input, that is input to the C•CURE 9000. \nThe C•CURE 9000 uses the lock release input to: \n■ Monitor the lock release activities on a door \n■ Monitor lock sensor activity \n■ Decide if an open door is reported as door forced open, door open, or door open by one of the lock release inputs. \nTable 113 on Page 463 and Figure 175 on Page 464 show the types of lock release devices that can be configured on \nan Advanced Door. \nTable 113: Locic Release Devices \nLock Release Device \nFunction \nCrash bar lock release \nInput to C•C U RE 9000 from crash bar or panic hardware \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n483 \nEFTA01226394\n", "char_count": 1766}, {"efta_number": "EFTA01225932", "page_number": 463, "text_content": "Advanced Door Monitoring Components \nLock Release Devices (continued) \nLock Release Device \nFunction \nKey override switch lock \nrelease \nInput toC•CURE9000from a key override switch \nPower failure lock release \nInput toC•CURE 9000 from power fai hardware \nGeneral Lock Release \nInput toC•CURE 9000 from a Fire Alarm System or iSTAR. \nFire alarm lock release \nInput to C•C URE 9000 from a FifeAlarm System \nF In u re 175: Lock Release Devices in the Door Monitoring Tab \nGeneral I Timing I Areas & Zones \no Add Input = ; Remove Input \nDouble Swipe I Triggers Groups I Status \nDoor Monitoring \nState images \nI \nInput \n• \n1 I Type \n. I. \nzi \niSTAR Input 10-iSTAR Ultra ACM1-gcm_new_cont_10009c \nCrash bar lock release \niSTAR Input 11-iSTAR Ultra ACM1-gcm_new_cont_10009c \nKey ovenide switch lock release \niSTAR Input 12-iSTAR Ultra ACM1-gcm_new_cont_10009c \nPowerfailure lock release \n. 1 \niSTAR Input 13-iSTAR 'Ara ACM1-gcm_new_cont_10009c \nGeneral lock release \n. 1 \n►\ni STAR Input 1NSTAR Ultra ACM1-gcm_new_cont_l 0009c \nAre alarm lock release \nExpanded Door Inputs \nIn addition to the Lock Sensors, there are also additional inputs for multiple DSMs and RTES as shown in Figure 176 \non Page 464. \nFigure 176: Expanded Door Inputs in the Door Monitoring Tab \nGeneral I Timing I Areas & Zones I Double Swipe I Triggers I Groups I Status \nDoor Monitoring I State images I \n'2? Add Input = ; Remove Input \n■ \nI\nInput \nType \niSTAR Input10-iSTAR Ultra ACM1-gcm_new_cont_10009c \nBond Sensor \niSTAR Input11-iSTAR Ultra ACM1-gcm_new_cont_10009c \nLatch bolt detector \niSTAR Input12-iSTAR Ultra ACM1-gcm_new_cont_10009c \nCam detection \niSTAR Input13-iSTAR Ultra ACM1-gcm_new_cont_10009c \nDoor switch monitor (side A) \niSTAR Input 14-iSTAR Ultra ACM1-gcm_new_cont_10D09c \nDoor switch monitor (side B) \niSTAR Input 15-iSTAR Ultra ACM1-gcm_new_cont_10009c \nRTE2 \n464 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226395\n", "char_count": 1922}, {"efta_number": "EFTA01225932", "page_number": 464, "text_content": "Advanced Door Monrtoring Components \nAdvanced Door Alarms \nFable 114 on Page 465 and Figure 177 on Page 465 show the alarm operations available for Advanced Doors. Each \nalarm reports the name of the input (lock sensor, lock release device, DSM) that caused the alarm. \nTable 114: Advanced Door Alarms \nAlarm \nDescription \nDoor Open \nDoor opens without valid card or RTE. and one of the lock release devices is active. \nLoci< Unsecured \nA lock sensor activateswhen it should be inactive. Indicates that the hardware failed to return to the \nlocked position after a valid lock release. \nLock Tamper \nA lock sensor is inactive when it should be active. Indicates lock tampering while the door is open, or \nfaiure of lock hardware. \nDSM Tamper \nFor doors with multiple DSM devices on a single side. Indicates that one DSM ctianged state, and \nthat the corresponding change did not occur to other DSMs devices on the same side of the door. \nExpanded Door Triggers \nThere are four additional Door Triggers for Advanced Doors Alarms in the triggers Tab. \nFigure 177: Additional Door Triggers \nI iming I Areas s Cones I pout* Svope \nI n991a I Groups I Status' D0Cf Monitoring I State Imes I \n!XS \nd = :.Re \niSTAR. Door \nA \nDrag columns to Group ID', here \nF'r \nProperty \nDescription \nIT \nClick here to filter data \na. \nFAithit Status \nThe current icitit status of this door. \nMann State status \nThe current alarm state of this door. \nDoor Open Alarm Status \nOpen Alarm Status \nDouble Swipe Status \nDouble Swipe Status. \nDSM Tamper Status \nDSM Tamper Status \n-re \nLock Tamper Status \nLock Tamper Status \n-ree \nLock Unsecured Status \nLock Unsecured Status \n.40\nMode Status \nThe current mode status of this door. \nOpen Status \nThe current open state of this door. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n465 \nEFTA01226396\n", "char_count": 1827}, {"efta_number": "EFTA01225932", "page_number": 465, "text_content": "Advanced Door Monitoring Components \nExpanded Event Actions \nIn addition to the Triggers on the Door, there are seven pairs of actions that toggle the allowance of the various \nalarms, including Door Held, Door Forced, and RTE Functions. Associate an iSTAR door with each entry. Door \nGroups are not supported. \nFigure 178: Expanded Event Actions \n17—\nGeneral AeknoMedgemern I Overdue I Messages Act \n^? Add FI:*Rermve \nAthal \nDetails \nResetlable \nDisable Dec( Faced Alarms \ndoorl \nr \nDisable Door Held Alarms \nr \nDisable Door Open Alarms \nr \nDisable DSM Tamper Alarms \nr \nDisable Lock Tamper Alarms \nr \n0 \nDisable Lock Unsecured Alarms \n. \nr \nDisable RTE Functions \nr \nEnable Door Forced Alarms \nr \nEnable Door Held Alarms \ndocr2 \nr \nEnable Door Open Alarms \nr\n \nEnable DSM Tamper Alarms \nr \nEnable Lock Tamper Maims \nr \nEnable Lock Unsecured Alarms \nr\n \nEnable RTE Functions \nr \nAssess Configuration I Predefined LOCI Messages I Groups I Stee nage I \niSTAR Door doot2 \nI I \n466 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226397\n", "char_count": 1048}, {"efta_number": "EFTA01225932", "page_number": 466, "text_content": "Advanced Door Monrtoring Configurations \nAdvanced Door Monitoring Configurations \nAdvanced Doors support configurations that include multiple RTE and DSM inputs. These are described in the \nfollowing sections. \nMultiple RTE Configurations \nMultiple RTE devices are typically configured to: \n• Provide tight security screens \n• Increase coverage over wide areas \nConfiguration Guidelines \nYou must specify the first RTE in the Request to Exit field of the Configure Door dialog box. This activates other \nrequest to exit options on the Configure Door dialog box. Specify additional RTEs by adding them on the Configure \nAdvanced Door Monitoring dialog box. \nTo Display the Configure Door Dialog Box \n• Select I lardware Pane >Cluster>iSTAR>Doors>Door Name \nTo Display the Configure Advanced Door Monitoring Dialog Box \n• Select Hardware Pane >Cluster>iSTAR>Doors>Door Name>Door Monitoring \nNOTE \nIf a door has multiple RTEs and is configured to shunt the DSM while RTE is active, the C•CURE \n9000 will shunt the DSM when any RTE on the door is active. \nFigure 179: Door Editor - Door Monitoring Tab \nGeneral I ;ming 1 Areas 8 Zones I Double SwOe i Triflers I. Groups I Status (Doce Montomg) Slate rages \n\" \nAdd Imo \n>Remove Input \nI. \nInput \nType \n!STAR ha.t4 Bind Sensor 2 \nBond Sensor \niSTAR Inpat7-ed cacti bond 'armor \nBond Sensor \niSTAR Irourled conu \nISTAR krixt3Oaah bar \nRTE2 \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n467 \nEFTA01226398\n", "char_count": 1456}, {"efta_number": "EFTA01225932", "page_number": 467, "text_content": "Advanced Door Monitoring Configurations \nFigure 180: Door Editor General Tab \nGeneral Timing I Areas & Zones I Double Swipe I Triggers I Groups I Status I Door Monitoring I State images\nLocation \n—Hardware \nReaders \nController: led cont_l \nDoor Switch Monitor: \nDoor Lock Relay: \nAlternate Shunt Relay: \nShunt Expiration Relay: \nIiSTAR Input2-DSM \nlOutput2-DLR_door_22 \nInbound Reader: \nOutbound Reader: \nOM liSTAR Readerl-Front \n\u0013 Readers are continuously active \n—Request To Exit \n1/4 \n(—Settings \nRequest To Exit Input: CiSTAR Input8-ed_cont_l \nF; Unlock Door on RTE \nP. Shunt DSM while RTE is active \n--\nl=r; \nSend non-alarms input status to the host \nMultiple DSM Configurations \nMultiple DSM configurations are used for double-leaf doors (side by side), and also to provide a tighter security \nscreen (top and bottom). The following sections describe typical multiple DSM configurations. \nSingle-leaf Doors (DSM top and bottom) \nFigure 181 on Page 469 shows a single-leaf door with a DSM at the top and bottom. C•CURE 9000 uses the \nfollowing to determine door state: \n■ If the door is closed, with both DSMs inactive, and then a DSM activates, the door state is open. \n■ If the door is open, with both DSMs active, and then a DSM de-activates, the door state is closed. \nAll DSMs on a single side must activate and deactivate together. If the DSMs do not activate together, C•CURE 9000 \nissues a DSM Tamper alarm and identifies the DSM that did not change state. \n488 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226399\n", "char_count": 1543}, {"efta_number": "EFTA01225932", "page_number": 468, "text_content": "Advanced Door Monaoring Configurations \nFigure 181: Single-leaf Door with DSM Top and Bottom \nr \nMA Bus RS. 485 \nJunction Box \nTo 'STAR ACM \n1/8 \nIN \nRM4-1 \nRDR \nDSM \nOUT \nMAG Lock Bond \nSensor \nMISS \n••• \nINN \nReader \nPublic Side \nDSM \nDouble- Leaf Doors (DSM each side) \nFigure 182 on Page 470 shows a double-leaf door with a DSM on side A and another on side B. C•CURE 9000 uses \nthe following to determine door state: \n• If either DSM is active, the door state is open \n• If both DSMs are inactive, the door state is closed. \nBecause double-leaf door configurations with one DSM per side are designed to operate with one leaf open and the \nother leaf closed, C•CURE 9000 does not issue DSM tamper alarms for this configuration. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n489 \nEFTA01226400\n", "char_count": 805}, {"efta_number": "EFTA01225932", "page_number": 469, "text_content": "Advanced Door Monitoring Configurations \nFigure 182: Double-leaf Door with DSM on Each Side \nJunction Box \nRPA Bus RS • 485 \nRDR \nSecure Side \nRM4 2 \nIN \nIN RM4-1 \nBond MAG Lock \nSensor \nB Side \nDSM \nDSM \nMAG Lock Bond \nSensor \nA Side \n_1\nReader \nPubic Side \nDouble-leaf Doors (DSM top and bottom) \nFigure 183 on Page 471 shows a double-leaf door with a DSM at the top and bottom of both side A and side B. \nC•CURE 9000 uses the following to determine door state: \n■ If the side is closed, and a DSM activates, the side is open \n■ If the side is open, and a DSM de-activates, the side is closed \n■ If either side is open, the door is open \n■ If both sides are closed, the door is closed \nMI DSMs on a single side must activate and deactivate together. If the DSMs do not activate together, the C•CURE \n9000 issues a DSM Tamper alarm and identifies the DSM that did not change state. \n470 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226401\n", "char_count": 956}, {"efta_number": "EFTA01225932", "page_number": 470, "text_content": "Advanced Door Monitoring Configurations \nFigure 183: Double-leaf Door with DSM Top and Bottom of Each Side \nfunction Box \nIN \nTo ISTAR ACM \nRM Bus RS •486 \nVs \nROR \n••• \n••• \nu• \nRead er \nSecure Side \nii\nRM4•2 \nN \nRM4-1 \nROR \nOUT \nBond MAG Lock \nSensor \nB Side \nDSM \nDSM \nDSM \nMAG Lock Bond \nSensor \nA Side \nReeder \nPublic Side \nDSM \nDSM Configuration Guidelines \nYou can configure DSM inputs in the Door Switch Monitor field on the Configure Door dialog box, or by adding \nthem on the configure Door Monitoring dialog box. \nIf you specify a DSM in the Door Switch Monitor field of the Configure Door dialog box, C•CURE 9000 uses that \ninput as the DSM for side A of the door. DSM inputs that are added using the configure Door Monitoring dialog box \ncan be either A or B side. \nUnlike multiple RTEs, you do not have to use the General Tab for DSM 1. Although the examples show two DSMs \nand two RTEs, it is possible to have more than two of each. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n471 \nEFTA01226402\n", "char_count": 1021}, {"efta_number": "EFTA01225932", "page_number": 471, "text_content": "Advanced Door Monitoring Configurations \nFigure 184: Multiple DSM Configuration \n( Genera Owing I Areas & Zoned Do.ble Swipe' Trippers I Gabs I Status I Dow Montatv I Slate images \nLemke \n—Ha amore \n^Readers \nRequest To Bit \nSetongs \nController: led cont_l \n( Door Switch Monitor: iSTAR Irtpu2-DSI4 \nDoor Lock Relay: \nAlternate Shunt Relay: \nShunt Expiration Relay: \nInbound Reader: \nOutbound Reader.\n\u0013 Readers are continuously active \nlOutpit2-DLR_doce 22 \nCONII,STAR Readerl-Front \nRequest To Ecit Input STAR IncktBed_cort_l \nP . Unlock Door co RTE \nP Shunt DSM while RTE \nwave \nF Sand nonsalanns input status to the host \n=IJ \nGenes al I Trnng I Areas b Zones I Double Smpe I Toppers I Groups I State \n• Add Input \nReno.** :rout \nLoot Prcntonng ) State Images I \nType \nBone z,nr.or \n► \n'ST \ntstd-bond_Sensor_2 \n:STAR hpdad_cont l _bond_sensor \nBond Sensor \n(STAR Inptiledsort_t \n:STAR Faxt3Craah bar \nRTE2 \nCrash bar bit nines \nDoor switch motor (side 8)\n:STAR Iroutexed_cont_1 \nzi\n472 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226403\n", "char_count": 1057}, {"efta_number": "EFTA01225932", "page_number": 472, "text_content": "Configuration Overview \nConfiguration Overview \nAlthough Advanced Door configuration procedures vary based on site requirements, most configurations involve the \ntasks and activities described in Table 115. \nTable 115: General Configuration Procedure \nTask \nConfiguration Dialog Box \nDescription \nAdditional Information \n1. Configure \nMonitoring \nInputs, \nReaders, and \nOutputs. \nHardware Pane > Cluster > \nController> Boards > 1st \nACM/2nd ACM \nConfigure inputs. readers, and outputs \non the STAR controller using standard \nprocedures and dialog boxes. \nSee Configuring RM4-1 and \nRM4-2 Reader, Inputs. and \nOutput on Page 474 \n2. Configure \nLock Releases \nHardware Pane > Cluster > \nController > Boards > 1st \nACM/2nd ACM \nConfigure lock release oomponentson \nthe STAR controller using standard \ncontroller configuration procedures \nand dialog boxes. \nSpecify how C•CURE 9000 \nannunciates the lock release inputs. \nSee Configuring Lock \nReleases on the II8 on Page \n477 \nSee Annunciating Lock \nReleases inputson Page 477 \n3. Configure \nthe Advanced \nDoor \nHardware Pane > Cluster > \nController> Doors > Door Name \nHardware Pane > Cluster > \nController> Doors > Door Name \n> Door Monitoring \nConfigure the first RTE and the door \nLatch relay using the standard Door \ndialog box (required). You can also use \nthe Door dialog box to configure the \nDSM for side A. \nAdd add itionalcom ponents using the \nConfigure Advanced Door \nMonitoring dialog box. \nSee Configuring the \nAdvanced Door on Page 478 \n4. Configure \nGrace and \nChange Time \nparameters \nHardware Pane > Cluster > \nController> Doors > Door Name \n> Door Monitoring \nSpecify timing requirements for unlock \ngrace timers. Also specify the change \ntime options for individualdoor \ncomponents, and for door shunts. \nSee Understanding Timing on \nPage 481 \nC•CURE 9000 Hardware Configuration Guide \nChapter 1/ \n473 \nEFTA01226404\n", "char_count": 1883}, {"efta_number": "EFTA01225932", "page_number": 473, "text_content": "Configuring an Advanced Door \nConfiguring an Advanced Door \nThis section provides step-by-step configuration information for a sample Advanced Door configuration. \nSample Door \nThe configuration for this example, shown in Figure 185 on Page 474, is a double-leaf door with multiple read heads, \nlock sensors, DSMs, and lock release inputs. \nFigure 185: Door Configuration Example \nJunction Box \n▪ \nTo\n▪ \n(STAR ACM \nRM Bus RS•NXI \nlea;r \nSean Side \nU\ni N \n1 RM4-2 \nRM4 I \nR0R \nIN \nOUT \nBond MAG Lock \nMAG Lock Bond \nSenso \nSensor \nB Side \nA Side \nRe der \nPubil Slde \nFire \nPull \nel% \nHoy \nOverride \nConfiguring RM4-1 and RM4-2 Reader, Inputs, and Output \nConfiguring RM4 inputs for the door in Figure 185 on Page 474 involves using standard controller configuration \nprocedures to configure the monitoring inputs, door latch relays, and read heads for A and B sides of the door. This \nis detailed in the following procedure. \n474 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226405\n", "char_count": 997}, {"efta_number": "EFTA01225932", "page_number": 474, "text_content": "Cenlqur mg an Advanced Door \nTo Configure RM4 (RS-485) Inputs for the Sample Configuration \n1. From the main menu, select Hardware Pane > Cluster > Controller. From the iSTAR Controller Selection \nbrowser, select the name of the iSTAR that includes Advanced Door components, and select Edit. \n2. Select the tab that includes the inputs to be configured. This will vary, depending on the iSTAR model. In some \ncases you will have to first select the ACMn board and a Port. \nThe RM Readers are configured under the following Tabs: \n■ iSTAR Ultra - Boards > ACM 1 or 2> RS-485 Port> Reader Port > Readers \n■ iSTAR Pro - Boards > ACM 1 or 2> Readers \n■ iSTAR Edge - COM1 or COM2 or COM3 > Readers \n■ iSTAR eX - COM1 or COM2 > Readers \nTo configure the inputs for side A in Figure 185 on Page 474 (on RM 1), create an RM Reader. \nNOTE \nSoftware House recommends that the Communication failure option be configured for all security \ndevices that connect to the iSTAR. Select the I/O Tab from the Reader Editor, to configure this \noption. \n3. In the General tab of the Reader Editor enter the following: \n• Name - the name of the reader \n• Enabled -activated \n4. Go to the I/O Tab \n5. In the Inputs box, select an input and configure it. Enter at least the following: \n■ Name - the name of the input \n■ Enabled - check box checked \n■ Send State changes to Monitoring Station (and Journal) \n■ Armed - check box checked. It's good practice to Ann Inputs, but if the Input is a door component, it will be \nautomatically armed. \nTo configure the inputs for the example in Figure 185 on Page 474, enter information for DSM side A and the \nMagnetic Bond Sensor. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n475 \nEFTA01226406\n", "char_count": 1722}, {"efta_number": "EFTA01225932", "page_number": 475, "text_content": "Configuring an Advanced Door \nFigure 186: STAR Input DSM side A \nName \nDSIAA-Sde \nQuoit:ow \nA \na Enabled I \nPartial: Default \nr Maintenance Mode \nTime Zone. (GM7.0560) Eaten Tine CUSS Canada) \n6ansateggess I Groups I Sirs l User Oersted Rotel Ste rages I \n• Idertficabal \nSattaler led_cort_l \nlord ICOalleSTAA Raeder Pubic A \n;yr IGeneall \nAssigned* I \nConacats Trot I \nOption \nWatt SU* \nDebccpce Threshold IMO eec): IO \nF Supr. 'cr. \nF Send stale changes to monitoring station \nF Send state cl:anoab to icAral \nr Ens. sane \nAcavais on Sugertsion Ent \nF Aimed \n6. Click OK and Close. \n7. Repeat step 5 to configure the Bond Sensor Input. \nNOTE \nFor consistency, Advanced Doors that include more than one instance of the same input (two \nDSMs, for example) should use a naming convention that indicates the area of the door that the \ndevice monitors. \nExample: \nDSM-Lobby-sideA. \n8. In the Outputs box, select an output and configure it. Enter at least the following: \n■ Name - the name of the output \n476 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226407\n", "char_count": 1073}, {"efta_number": "EFTA01225932", "page_number": 476, "text_content": "Configuring an Advanced Door \n• Enabled - check box checked \n• Normally energized - activated or de-activated, depending on site requirements. Magnetic Locks are usually \nNormally Energized. \nTo configure the outputs for the example in Figure 185 on Page 474, enter information for the magnetic lock \noutput. \nFigure 187: Reader 'Knob \nA \nrf717 \nCALA ASO= \nBM ST\n Resaceftede.A \nr\necon1\nraWallIA \n26 5 \n3 eed NDrOp¶Cl2 \nP Ensues \nF \nwtv mese \nin an. GAIT.D5063 Eaten Tine PUS liCa3X4) \nPeen 06/aA \n0•4 \n30 \nI (WWI 0 02An I Goa I 53•1431 Use Weed FAIN I Rae neAes I \nMOS \nCreme 2.3 trims \nraisin/psi \nbl \n_mitMISII• \n CalwA2 \nNine \nSperand I \nSonar' 2 \nTwat \nCaranceen Fol \nP \nWay \nP \nrnAsA.ade \nP \nTwee -031116PAReeterittac \nP \nCutos \n4 Grab Al (Mata \nNine MOAp..b \nEs \nCan-ors” \n9. Click Save and Close until you return to the Controller editor. \n10. Repeat steps 1 through 7 to configure the RM4-2 for the B side of the door. \nConfiguring Lock Releases on the 118 \nConfiguring lock releases for the door in Figure 185 on Page 474 involves using standard controller configuration \nprocedures. \nYou must also specify how C•CURE 9000 annunciates the lock release inputs. For configuration guidelines, see the \nnext section. \nAnnunciating Lock Releases Inputs \nIf the lock release input is configured to annunciate, C•CURE 9000 reports input activation and de-activation. \nAnnunciation of inputs has no impact on door actions or lock release operations. \nTo reduce message traffic, most configurations will choose to annunciate lock release inputs to test or troubleshoot \nthe system, but will not annunciate them for normal door operations. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n477 \nEFTA01226408\n", "char_count": 1713}, {"efta_number": "EFTA01225932", "page_number": 477, "text_content": "Configuring an Advanced Door \nTo Configure Lock Releases for the Sample Configuration \n1. From the main menu, select Hardware>Cluster>Controller. Right-click the iSTAR that includes lock release \ncomponents and then Edit from the context menu. \n2. Select the tab that includes the 1/8 to be configured. This will vary, depending on the iSTAR model. In some \ncases you will have to first select the ACM board and a Port. \nThe 1/8 boards are configured under the following Tabs: \n■ iSTAR Ultra - Boards > ACM 1 or 2> RS-485 Port> ACM Ext > 1/8 >Input \n■ iSTAR Pro - Boards > ACM 1 or 2> ACM Ext > 1/8 >Input \n■ iSTAR Edge - COM1 or COM2 or COM3 > 1/8 >Input \n■ iSTAR eX - COM1 or COM2 > 1/8 >Input \n3. On the 1/8 Editor, select an input and click Edit \n4. On the Input Editor, enter at least the following: \n■ Name - the name of the input \n■ Enabled - check box checked \n■ Armed - check box checked \n■ Send state changes to monitoring station - activated (includes sending to the journal) or deactivated, \naccording to the site requirements \n■ Send state changes to journal - Read only. Will be activated if Send state changes to Monitoring station is \ntrue. \n5. Click Save and Close. Repeat steps 3 to 5 to configure additional inputs. \nFigure 188: 1/8 Inputs for Sample Door \n6. Click Save and Close until you return to the main menu. \nConfiguring the Advanced Door \nConfiguring the Advanced Door involves adding door components using both the standard Door editor and the \nDoor Monitoring Tab editor. \nTo Configure the Advanced Door in the Sample Configuration: \n1. From the Hardware Pane, right click on iSTAR to Configure>Door and select New. Or select an existing door in \nthe controller to edit. \n2. On the iSTAR Door Editor, click the General Tab and enter at least the following: \n■ Door has RTE - the name of RTE input (if required by the door) \n■ Door switch monitor - the name of the side A DSM input \n■ Door latch relay - the name of the door latch relay output \n478 \nChapter 11 \nC•CURE 90\n... [truncated, 2046 chars — for the full page use /api/corpus/document/EFTA01225932/477 or ?id=EFTA01225932&page=477]", "char_count": 2046}, {"efta_number": "EFTA01225932", "page_number": 478, "text_content": "Configuring an Advanced Door \n■ Optional - Send non-alarm input status to the host. Similar to input annunciation, this will increase traffic \nbut it is a good mode to understand Advanced Doors. \n3. Enter the Readers for the Inbound and Outbound reader fields. \n4. Click Save and Close until you return to the main menu. \nTo configure the door in Figure 189 on Page 479, enter the name of the side A DSM and the door latch relay. The \nsample door uses a read head instead of an RTE. However, doors that use one or more RTE devices must configure \nthe first RTE on the Door Editor. \nFigure 189: Sample Door \naU!1 \na Save ore Ocee \nSamoan*. \nNom \nDescnota \nNonce Mut \nr genre*, we. \nrpm. roc, Gar <6 al Eaton Lee NS 6 Canada) \nTrap I key a /tees I Dad. s.o• I TIOnlas I Gays• I 9.0.a I Da° Ilentrat I ue Dered Wee I atm m09•0\nLocate• \n'tweets* \nI:Mama \nSt.et \nLavelle. 'STAR Edge el \ntow 5.1. Worst. IS TAR lip42.DSW \nJ \n=LI \nOca lock Rein, ICkie424)1B.4.22 \nShoe Roy \n=LI \nEneetal Relri \n=LI \nn and a s s \n1:0111,STACI Flethicktiltit \n=L1 \n04 5„,d wick, 1:0111iSTAR Atodebease_e_sde \nr \nate ccffir a:WY actYt \n[ftweatte es \nRes To Silos \n=LJ \nr Elf/06 nrr.. Of !FITE \nr \n051,  \nR- E P3 Adlet \nSowl *maw boststilwe bile him \n5. Select the Door Monitoring tab. \n6. To add door components: \na. Select Add Input and pick the appropriate input to add to the Input list. \n7. To specify component type: \na. In the Input list box, select an input. \nb. Click on the Type field and use the drop-down list to select the component's type. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n479 \nEFTA01226410\n", "char_count": 1599}, {"efta_number": "EFTA01225932", "page_number": 479, "text_content": "Configuring an Advanced Door \nTo configure components and types in Figure 190 on Page 480, add inputs for the key override, fire pull, A and B \nside bond sensors, and B side DSM. Specify the component type for each of the corresponding inputs. This field \nis required. \n8. Click Save and Close. \nFigure 190: Door Monitoring \nASwenl0ose \nord Men \nPartition OEM \nr Sinionne Mab \nImam (211T450:11Eation Tire (US 4 Endo) \nGad I Niro I Ma $ Zinn I Dad* 90.• I %pm I Gap I anal Ika Mat\"; \nOdnansie• I gang's I \nSTAR STA To:1 cad_l_band WOW \nSTAR lat let arcl \nSTAR 29.00ooltiar \nSTAR TEAKS owe 1 \nSTAR apt1 Surd %Key 0vonfe \nnabs \nRTE2 \nOath bat lock Seas \nNet smch nonor \nKey or.terde smith iod< \nCrash Eat Clans Tema (010 sAccals) \ngab Son. CAMAY Ur* (V101. 074 ) \nlath Boll Clitege Time (Ulthecords) \nCom Sees. Charge Time (Msexede) \n0SM Sods A 0102* Time (010 sow& \n09.1 \nCturge Terre WM saxeds) \nRIE ENNA Tyro (1;10 wands) \n480 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226411\n", "char_count": 995}, {"efta_number": "EFTA01225932", "page_number": 480, "text_content": "Understanding Timing \nUnderstanding Timing \nTime Delays \nUse timing options to prevent false alerts caused by nearly simultaneous inputs to C•CURE 9000, and also to fine \ntune timing to meet specialized door and site requirements. \nIn addition to the normal door de-bounce and grace times, on the Timing Tab, there are seven other timing tweaks \nthat are used to avoid race conditions. The Timers default to zero but it is good practice to set them all at 0.2 or 03, \nand then adjust, as necessary. See Figure 191 on Page 481. \nSince input changes cannot occur simultaneously, and if almost simultaneous may be read by our hardware in any \norder, some input change time values are provided. This change time will be used whenever one of the inputs \nchanges, to allow the system to wait and see if any of the normally accompanying inputs is also going to change. \nFor example, every time the door is open (meaning the DSM input is active), the latch bolt or bond sensor input \nshould also be active. Therefore, every time the door opens, if the input is not already active, a timer will be started \nwith the value of the lock sensor change value. If the timer times out without the lock sensor input activating, then a \nLock Tamper alarm will be reported. Then when the door closes and locks, this time value will be the time we allow \nthe lock sensor input to change from active to secure before reporting Lock Unsecured. \nUse the Timers box on the Configure Advanced Door Monitoring dialog box to fine tune timing delays for \nAdvanced Door components. \nTo Display the Configure Advanced Door Monitoring Dialog Box \n• c‘t•Ityt Door>Door Monitoring tab. \nFigure 191: Timms \nTIMM \nBend Sensor Change Time (MO seconds): 3 \nCrash Bar Change Time (1/10 seconds): 3 \nLatch Bolt Change Time (MO seconds): 3 \nCam Sensor Chant Time (1/10 seconds) \n3 \nDSM Side A Change Time (1/10seccnen) 3 \nOSM Side B Change Time (1/10 seconds): 3 \nRTE Change Time (MO seconds) 21 \nKinds of Timing Options \nC•CURE 9000 includ\n... [truncated, 2480 chars — for the full page use /api/corpus/document/EFTA01225932/480 or ?id=EFTA01225932&page=480]", "char_count": 2480}, {"efta_number": "EFTA01225932", "page_number": 481, "text_content": "Understanding Timing \n• Shunt/Delay Relock times - a wait period that defines the number of seconds the door can remain open before \nrelock or before an alert is sounded. \nGrace Time Options \nTable 116 on Page 482 describes grace time options. \nTable 116: Grace Timing Options \nOption \nDescription \n...ii\n, \nExample \nUnlock Grace Time \nSpecifies the time that C•CURE 9000 waits fora \ndoor open signal after the door unlock timer has \nexpired. \nPreventsa false'door forced' message in \nsituations where the signals are nearly \nsimultaneous. \nPersonnel who are granted card access delay \nopening a door unti unlock time is nearly expired, \nthereby causing nearly simultaneous DSM and \nunlock timer expiration inputs to C•CURE 9000. \nIf configured. C•CURE 9000 waits the number of \nsecondsyou specify fora door open input, thereby \npreventing a false \"door forced open\" message. \nDI.R \nI ).-,‘.: \nDoor Open Grace Time \nSpecifies the time that C•CURE 9000 waits for \nan RTE. card admit, or momentary unlock signal \nafter receiving the signal from the DSM. \nPreventsa false \"door forced open\" message in \nsituations where signals are nearly \nsimultaneous. \nFor additional information, see Special Timing \nConsiderationson Page 484. \nPersonnel lean on a door release mechanism white \npressing the RTE switch, causing nearly \nsimultaneousdoor open and RTE inputs to \nC•CURE 9000. \nIf configured. C•CURE 9000 waits the number of \nsecondsyou specify for the RTE. card admit. or \nmomentary unlock signal, thereby preventing a \nfalse \"door forced open' message. \nDSM \nRTE \na-\nDoor Close De-bounce Time \nSpecifies the time that C•CURE 9000 ignores \nDSM inputs. to allow for bouncing doors. \nUnintended door movement (bouncing) can \nactivate a DSM input to C•CURE 9000 and cause \nfalse \"door forced open\" messages. \nIf configured, the Door dose de-bounce time option \nignores DSM inputs for the time specified after the \ndoor doses toallow for bouncing doors. \nin I: \nI\nO,-.\\: \nI \nI \nI \nIlla \nif -0. \nChange Time \n... [truncated, 2282 chars — for the full page use /api/corpus/document/EFTA01225932/481 or ?id=EFTA01225932&page=481]", "char_count": 2282}, {"efta_number": "EFTA01225932", "page_number": 482, "text_content": "Understanding Timing \nNOTE \nChange time is specified in units of 1/10 second. Enter 1 to specify 1/10 second, 5 to specify 5/10 \n(1/2) second and so forth. \nSoftware House recommends that you set all change times to at least 5/10 second and make \nadjustments only as necessary. \nTable 117 on Page 483 describes how change time options work for lock releases, lock sensors, and DSM and RTE \ndevices. \nTable 117: Change Timing Options \nOption \nFunction \nAssociated Inputs \nActivation Criteria \nCrash bar \nchange time \nSpecifies the amount of time C•CURE \n9000 allows, after a crash bar state \nchange. for a lock sensor change \nC•CURE 9000 uses the crash bar \nchange time to determine changes to \ncorresponding: \n• Bond sensors \n• Latch bolts \n• Cam sensors \nActivated by the bond sensor, latch bolt. \nor cam sensor. \nBond sensor \nchange time \nSpecifies the amount of time C•CURE \n9000 allows for a bond sensor state \nchange. \nC•CURE 9000 uses this time, and the \ntime of the other door inputs, to \ndetermine the wait before issuing a \n\"lock tamper\" or \"lock unsecure\" alarm. \nC•CURE 9000 uses the greatest \nvalue of the following: \n• Door open grace time \n• Door dose de-bounce time \n• Crash bar change time \n• Bond sensor change time \n• RTE change time \nThe bond sensor should be active if: \n• Door isopen \n• Door latch relay inactive \n• Lock release input(s) are active \nThe bond sensor should be inactive \nwhen: \n• Latch relay is inactive, the door is \ndosed, and the lock release inputs \nare inactive \nLatch bolt \nchange time \nSpecifies the amount of time C•CURE \n9000 allows for a latch bolt state \nchange. \nC•CURE 9000 uses this time, along \nwith the time of the other door inputs, to \ndetermine the wait before issuing a \n\"lock tamper\" or \"lock unsecure\" alarm. \nC•CURE 9000 uses the greatest \nvalue of the following: \n• Door open grace time \n• Door dose de-bounce time \n• Crash bar change time \n• Latch bolt change time \n• RTE change time \nThe latch bolt should be active if the \ndoor isopen. \n\n... [truncated, 2909 chars — for the full page use /api/corpus/document/EFTA01225932/482 or ?id=EFTA01225932&page=482]", "char_count": 2909}, {"efta_number": "EFTA01225932", "page_number": 483, "text_content": "Understanding Timing \nTable 117: Change Timing Options (continued) \nOption \nFunction \nAssociated Inputs \nActivation Criteria \nDSM side A \nSpecifies the amount of time C•CURE \nAdditional DSM inputs on the same \nDSM change time Isaacs,* when the first \nchange time \n9000 allows fora DSM state change. \nC•CURE 9000 uses Misvalue to \ndoor side \nDSM in a group changes state. (DSMs \nmust be located on the same side of the \nDSM side B \nchange time \ndetermine the wait period before \nactivating a DSM tamper for multiple \ndoor). \nDSM devices on one side of the door. \nRTE change \nSpecifies the amount of time C•CURE \nC•CURE 9000 uses the RTE change \nActivated by the bond sensor. latch bolt. \ntime \n9000 allows. before or after an RTE \nstate change, for a lock sensor change. \ntime todetermine changes to \ncorresponding: \nor cam sensor. \nFor additional information, see See \n• Bond sensors \n'Special Timing Considerations' on \npage 484 \n• Latch bolts \n• Cam sensors \nShunt Time Options \nTable 118 on Page 484 describes options that control shunt time. \nTable 118: Shunt Time Options \nOption \nDescription \nDelay relock while door open after valid access \nIf access is valid. delays the tele& of the door until the door doses. This differs from \nstandard relock operations where tele& occurs when the: \n• Door opens. \n• Door opensand the tele& delay expires. \nIf the door isopen. the lock is energized. \nC•CURE 9000 sends an alarm when the shunt time expires. \nShunt door for full shunt time \nActivates the shunt for the full time specified. \nIf selected with Delay relock while door open after valid access, the lock is \nenergized and the door unlocked for the full shunt time. regardlessof whether the door \nisopen or dosed. \nSpecial Timing Considerations \nSites that use an RTE motion detector angled over a door can cause C•CURE 9000 to report a valid RTE that is \ncaused by door motion, instead of a forced open alarm. This situation occurs because of a race condition in which \nthe RTE caused by forced\n... [truncated, 2442 chars — for the full page use /api/corpus/document/EFTA01225932/483 or ?id=EFTA01225932&page=483]", "char_count": 2442}, {"efta_number": "EFTA01225932", "page_number": 484, "text_content": "Understanding Timing \n■ Adjusting the timing of door components - use the RTE change time option to specify timing for incoming \ntraffic and also to change the function of the Door open grace time option. \nThe RTE change time option specifies the amount of time that C•CURE 9000 ignores RTE inputs after the door is \nclosed. Use this value to prevent false door forced reports caused by door components (slow bolts or sensors, \nbouncing door, for example) for outgoing traffic. \nThe RTE change time option also changes the function of the Door open grace time option. If you specify a value for \nRTE change time, the Door open grace time option now specifies the time C•CURE 9000 ignores RTE changes \nbefore the door open occurs. This prevents RTE signals from the motion detector that are caused by door mechanics \nrather than human access. If C•CURE 9000 sees an RTE on a closed door, and then sees the door open within the \nperiod you specify, it cancels the RTE and issues a door forced alarm. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n485 \nEFTA01226416\n", "char_count": 1071}, {"efta_number": "EFTA01225932", "page_number": 485, "text_content": "Monitoring Door Activity \nMonitoring Door Activity \nYou can monitor Advanced Door activities using: \n■ Door, alarm, and show cause features on the Monitoring Station \n■ Journal reports from the Administration application \nUsing Monitoring Station Commands \nTo Display Information about Alarms, Alarm Causes, and Door Component Status \n1. Select Doors from the Non-Hardware Pane on the Monitoring Station Explorer Bar. \n2. Right click on a Door and select Door Monitoring. \n3. Use Door Monitoring to Show Locked Causes and various Alarm States. \n4. Door Monitor Inputs are also shown at the top of the Door Monitoring Editor. Right click on an input for further \ncontext menu options. \nUsing Journal Reports \nTo Display Journal Messages about Advanced Doors \n1. From the Administration application, select Options & Tools. \n2. Select Journal \n3. Enter a range for Start date/time and End date/time. \n4. Use the Journal Query Assistant to select: \n■ Object Changed State Message Type \n■ iSTAR Doors Object Type \n■ Door Name(s) \n■ You can also use Journal Triggers to get detailed information. \n488 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226417\n", "char_count": 1164}, {"efta_number": "EFTA01225932", "page_number": 486, "text_content": "Understanding Door Alarms \nUnderstanding Door Alarms \nAlarms \nThis section describes how C•CURE 9000 manages alarm traffic and contradictory component reports that can \nsometimes accompany Advanced Door configurations. \nDoor Open Alarm - this alarm occurs whenever the door opens without benefit of card or request to exit access, and \none of the lock release devices is active. This alarm indicates that some kind of emergency unlock is occurring. The \nalarm message includes the name of the lock release device as the reason for the door open alarm. In the case that \nnone of the lock release devices is active, this is a normal door forced open alarm. \nLock Unsecured Alarm - this alarm occurs whenever a lock sensor is active when it should be inactive. This \nindicates that the lock hardware failed to return to locked position after being unlocked by one of the lock release \ndevices or by regular door control. The alarm message includes the name of the lock sensor input that caused the \nalarm. \nLock Tamper Alarm - this alarm occurs whenever one of the lock sensors is inactive when it should be active. This \nis whenever one of the lock release devices is active or the door latch relay has been activated by the door or the \nDSM indicates that the door is open. This may indicate that someone is tampering with the lock sensor while the \ndoor is opening or that the lock hardware has failed. The alarm message includes the name of the lock sensor input \nthat caused the alarm. \nDSM Tamper Alarm - this alarm is reported if multiple DSM inputs monitor the same door and one of them does \nnot become active when it should. The alarm message includes the name of the input that is not active. \nNew Activity / Journal Reports \nNew door activity reports will be added: \n■ Lock Tamper Alarm (reported with input name indicating which input caused the lock tamper alarm condition) \n■ Lock Unsecured Alarm (reported with input name indicating which input caused the lock unsecured alarm \ncondition\n... [truncated, 3031 chars — for the full page use /api/corpus/document/EFTA01225932/486 or ?id=EFTA01225932&page=486]", "char_count": 3031}, {"efta_number": "EFTA01225932", "page_number": 487, "text_content": "Understanding Door Alarms \n3. Door Lock unsecured reported (bond sensor 1). \n4. Bond sensor 1 deactivates while the door is open, causing a second input to the lock tamper alarm. \nC•CURE 9000 does not display an additional alarm report for bond sensor 2 on the General Activity window. \n5. Door closed (DSM deactivates). \n488 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226419\n", "char_count": 394}, {"efta_number": "EFTA01225932", "page_number": 488, "text_content": "Understanding Door Alarms \nFigure 192: GeneralActivityAlarm Reports Example \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n489 \nEFTA01226420\n", "char_count": 149}, {"efta_number": "EFTA01225932", "page_number": 489, "text_content": "Understanding Door Alarms \nI \n0 \n■ \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226421\n", "char_count": 91}, {"efta_number": "EFTA01225932", "page_number": 490, "text_content": "Understanding Door Alarms \nFigure 193 on Page 491 shows the Monitoring Status for the example door activities. C•CURE 9000 reports the first \nlock tamper (bond sensor 2) and does not clear the alarm. The second lock tamper (bond sensor 1) on the same door \ndoes not display on the General Activity Monitor. \nFigure 193: General Activity Alarms Reports Example \n3/32014 .0.47:4 AM \nc\n3/52014 '0:47r4 N4 \nc\n3/5/20141:4721 AM \nc\n3/51201444724 N4 \n11:1 3/52014'0.4724 AM \nc\n3/52014 .448:33 N4 \ntSTAR Doe 1100f 2Z IS deer 13fCed \niSTAR Docr \ndoer lock tamper WAR tp44-Eccid_Sonecc2ASTAR hret3-Bccd_Sterce_1'. \ndoorlodc tamper »erei on IUAR Door 'cixe_22'. \n'STAR Doer docc27 Isdoor dosed \n'STAR Do, doct_22 door lock Li-seared atien1STAR Irp441.0oniSensce2 STAR input 1-Bcnc Sento.. 1' \ndoorlocic Lrisecuncl alarm clewed m ISTPR Dor 'cisce_27. \nClearing Alarms \nAdvanced Door alarms may occasionally appear \"stuck\" because C•CURE 9000 waits for the input to change state \nbefore clearing the alarm. This is to reduce unnecessary alarm traffic. If all inputs are functioning properly, you can \nclear all door and input alarms by performing a normal door access cycle (opening and closing the door). \nDoor Triggers \nIn addition to the usual five Door Triggers: \n• Admit Status - Admit, Reject, Noticed Admit, Noticed Reject, Duress \n• Double Swipe Status - Locked, Unlocked \n• Mode Status - Unlocked, Locked, No Access \n• Open Status - Open, Closed \n• Alarm State Status - Normal, Forced, Held Open \nThere are four additional Advanced Door Triggers shown in Figure 194 on Page 492. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n491 \nEFTA01226422\n", "char_count": 1648}, {"efta_number": "EFTA01225932", "page_number": 491, "text_content": "Understanding Door Alarms \nFigure 194: Advanced Door Triggers \nGem-all Thing I :VMS 1 Zoies I Double SAD( -092en Dews r Status \nI Dco• sAxtrtmg I &ate rrages I \n- Woos \n?'Pali Fa,b Remy! \n(1 Don 0 pm Alan St:us \n• \nGereti I Tama I Acs tames I Cou:t .c.ne \nInggare \nAdd aaascve \nrlifAt 5 I Gram Yeas I her Montro I Sta:e nacres i \nValue \nPai \n-Cg 1 1 nrk I In:enured .kr-eui \nSec:um \nawe I Tired kw 47mes I Wilk kw Naas 'Amens Sam I Derr Nertienr I We inagee \nTrigg= \n'4, AID el. Reinke \nVW* I \nAda, \nI ink \nLock - aroer Setus \n- Triggers \n\"at. Ark ,74 Rerrove \nScat \nWade \ntrr \nDSM Tat imp Skin \n&Liu \nDefiler \nSdexIde \n'cure \nPrivilege Modifications \niSTAR Door Permission list \n• Enable Door forced alarms \n• Disable Door forced alarms \n• Enable Door held alarms \n• Disable Door held alarms \n• Enable RTE functions \n• Disable RTE functions \n492 \nChapter 11 \nCCURE 9000 Hardware Configuration Guide \nEFTA01226423\n", "char_count": 914}, {"efta_number": "EFTA01225932", "page_number": 492, "text_content": "Understanding Door Alarms \n■ Enable Lock Tamper alarms \n■ Disable Lock Tamper alarms \n■ Enable Lock Unsecured alarms \n■ Disable Lock Unsecured alarms \n■ Enable Door Open Tamper alarms \n■ Disable Door Open Tamper alarms \n■ Enable DSM Tamper alarms \n■ Disable DSM Tamper alarms \n■ Door Monitoring Details \nReports \nA standard iSTAR Door Report can be used to list all of the Advanced Door components. \nC•CURE 9000 Hardware Con figuration Guide \nChapter 11 \n493 \nEFTA01226424\n", "char_count": 473}, {"efta_number": "EFTA01225932", "page_number": 493, "text_content": "Understanding Door Alarms \nFigure 195: STAR Door Report \nrt—s_rae • ent \n\" \nV \nV \nV \n• \n• \n. \n, \nreport door mon \nI STAR DOOR \nAdvanced Door Monitoring Inputs \nInput Name \niSTAR Input4-iSTAR Ultra \nACM1-gcm_new_cont_10009c \niSTAR Input5-iSTAR Ultra \nACM1-gcm_new_cont_10009c \niSTAR Input1-iSTAR Ultra \nACM1-gcm_new_cont_10009c \nLink Type \nBond Sensor \nBond Sensor \nLatch bolt detector \nAdvanced Door Monitoring Inputs \nInput Name \niSTAR Input8-iSTAR Ultra \nACM1-gcm_new_cont_10009c \niSTAR Input9-iSTAR Ultra \nACM1-gcm_new_cont_10009c \niSTAR Input18-iSTAR Ultra \nACM1-gcm_new_cont_10009c \niSTAR Input17-iSTAR Ultra \nACM1-gcm_new_cont_10009c \nLink Type \nCam detection \nRTE2 \nGeneral lock release \nFire alarm lock release \nAdvanced Door Monitoring Inputs \nInput Name \niSTAR Input3-Crash_bar \niSTAR Input4-Bond_Sensor_2 \niSTAR Input7-ed_cont_1 \nLink Type \nCrash bar lock release \nBond Sensor \nBond Sensor \n494 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226425\n", "char_count": 974}, {"efta_number": "EFTA01225932", "page_number": 494, "text_content": "Advanced Door hilonrtoring Details \nAdvanced Door Monitoring Details \nIf you have Advanced Door Monitoring, additional selections are displayed on the Door context menu from a \nDynamic View or a Monitoring Station Status List of Doors. \nEach of these selections let you initiate a Manual Action to enable or disable the selected function. \nSee Viewing a List of Doors on Page 408 for more information about the context menu for Doors. \nAdvanced Door Monitoring has 7 Cause List type states, and 14 possible manual actions that may be associated \nwith these: \n■ RTE enable/disable, \n■ door forced alarm enable/disable, \n■ door held open alarm enable/disable, \n■ door open alarm enable/disable, \n■ lock tamper alarm enable/disable, \n■ lock unsecured alarm enable/disable, \n■ DSM tamper alarm enable/disable. \nEnter the Door Monitoring Status screen for iSTAR doors by right clicking on the Door and selecting Door \nMonitoring from the context menu. You can also execute the Manual Actions listed above, from this context menu. \nFigure 196: DoorContext Menu \nFind in Audit Log... \nFind in Journal... \nLock... \nUnlock... \nMomentary Unlock \nShow Locked Causes \nEnable RTE functions... \nDisable RTE Functions... \nEnable Door Forced Alarms ... \nDisable Door Forced Alarms... \nEnable Door Held Open Alarms... \nDisable Door Held Open Alarms ... \nEnable Lock Tamper Alarms ... \nDisable Lock Tamper Alarms ... \nEnable Lock Unsecured Alarms... \nDisable Lock Unsecured Alarms... \n • \nDoor Monitoring \nSee Door Monitoring Screen on Page 496 for more information about the Door Monitoring screen. \nC•CURE 9000 Hardware Configuration Guide \nChapter 11 \n495 \nEFTA01226426\n", "char_count": 1655}, {"efta_number": "EFTA01225932", "page_number": 495, "text_content": "Door Adlonrlonng Screen \nDoor Monitoring Screen \nThe Door Monitoring screen shows all inputs monitored by a door, their state, and any door alarm condition derived \nfrom them as well as the Cause Lists. \nThe upper dynamic view displays Door Monitoring Inputs status. The bottom part displays cause lists and all \n'cause list' standard functionality is available (right mouse click on selected row will activate \"Details/Cancel\" \ncontext menu). \nFigure 197 on Page 496 shows an example of the Door Monitoring Screen. \nTable 119 on Page 497 provides definitions for the fields and selections on the screen. \nAlso see Table 114 on Page 465 for an explanation of the Alarms. \nFigure 197: Door Monkodng Screen \nI\ng\n \nDoors Flo/storing screen for dom_.12 \n'el ▪ Refresh Al \nHews - Fiter ktrirDiti(GYVtla \nDrag column to group by here \nName \nI \nbout Type \nI \nal \nAnasdaras \nI \nAortae Salm \n'STAR Input3Crish bar \nCrash bar lock release \nMood \nActive \n'STAR bps44-BcoO Satsce2 \nBond Sensor \nMood \nInactive \nMAR Ingstill- \ned_ccon_l_bood_senaor \nBond Sensor \nArmed \nPave \niSTAR Input&ed_cooLl \nDoor *Mich nada fide 0) \nMead \nInactive \n'STAR Inputl,d con° \nRTE2 \nMood \nInactive \nSTAR Instal- Boardl Key Cmanide Key override math too release \nPaned \nInactive \nCount: 6 \nPEN Enabled \nRTE Swoons \nDoor Forced sin \nDSM Tamer Alarm \nDar Held Norms \nLodiTamper Maros \nCaw \nlock unsecured sans \nI Prixty\nseoure_22 \nDoor ODe, Ames \n \n75 \nsrOde_22 \nUnbck Door \n3/1020141200A1 PM \n75 \nI:ck_22 \nLack Door \n3/10/ 01411:50ZAM \n75 \nmood \nIblock Door \n3/10201411:58:51 MI \n75 \nCefaii sae \nLocked \nLock \nThe availability of manual actions depends on input assignments. The rules to show/hide manual action on the \nDoor Monitoring Ccieen and show/hide executors on iSTAR Door Dynamic Views are: \n• If there is an RTE input then show Enable/Disable RTE; \n• If there is a DSM input then show Enable/Disable Door Forced Alarms, Enable/Disable Door Held alarms, if \nthere is also any DSM side A inputs, then Enable/Disable DSM Tamp\n... [truncated, 2195 chars — for the full page use /api/corpus/document/EFTA01225932/495 or ?id=EFTA01225932&page=495]", "char_count": 2195}, {"efta_number": "EFTA01225932", "page_number": 496, "text_content": "Door Monitoring Screen \n• If there is a Latch Bolt Detector input then show Enable/Disable Lock Tamper alarms, Enable/Disable Lock \nunsecured alarms; \n• If there is a CAM detection input then show Enable/Disable Lock Tamper alarms, Enable/Disable Lock \nunsecured alarms; \n• If there is a DSM Side A input then show Enable/Disable Door Forced Alarms, Enable/Disable Door Held \nalarms, if there is also a main DSM, or another DSM side A, then Enable/Disable DSM Tamper; \n• If there is a DSM Side B input then show Enable/Disable Door Forced Alarms, Enable/Disable Door Held \nalarms, if there is more than one DSM side B, then Enable/Disable DSM Tamper; \n• If there is an R'1'E2 input then show Enable/Disable RTE. \nTable 119: Doors Monitoring Screen Definitions \nField/Sutton \nDescription \nR.\nAra, Refresh AM \nClick this button to refresh the values of all In puts on the screen. \n.r , tij,\nViews \ny \n• dil \nThis toolbar lets you perform Dynamic View functions on the list of Door Inputs. such as tittering. printing. and\nswitching to Card View. \nName \nThisoolumn displays the name of the Input. \nInput type \nThisoolumn displays the function that the Input serves in Door Monitoring. \nArmed Status \nThis column displays the Armed Statusof the Input. Inputs associated with Doors are automaticallyArmed and \nare reported as unknown. \nActive Status \nThis column displays the Active Status of the Input. \nCause Selection \nThisdrop-down list lets you choose the Cause type to display in the Status Information and Cause List section of \nthe screen. \nStatus Information \nT h is read-onty field displays the current state of the selected Input. \nCause \nThis read-on ty field displays the Cause State for the Input. \nAction \nThis read-onty field displays the Lock and Unlock actions that are in effect on the door. \nDateTime \nThis read-onty field displays the Date and Time the ca use occu rred. \nPriority \nThis read-onty field displays the Event Priority of the cause. \nLock \nClick this button to initiate a \n... [truncated, 2573 chars — for the full page use /api/corpus/document/EFTA01225932/496 or ?id=EFTA01225932&page=496]", "char_count": 2573}, {"efta_number": "EFTA01225932", "page_number": 497, "text_content": "Door Monitoring Screen \nTable 119: Doors Monitoring Screen Definitions (continued) \nField/Button \nDescription \nDisable \nThe Disable button changes to match the selected Cause Selection in the drop-down list. Clickthis button to \ndisable the selected Cause type. \nExample: \nIf the Cause Selection is Door Forced Alarms, then the button reads Disable Door Forced Alarms. \n498 \nChapter 11 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226429\n", "char_count": 442}, {"efta_number": "EFTA01225932", "page_number": 498, "text_content": "12 \nConfiguring Elevators \nThis chapter explains how to configure elevators in C•CURE 9000. \nIn this chapter \nElevator Configuration Overview \n500 \nElevator Tasks  \n501 \niSTAR Elevators  \n505 \napC Elevators  \n519 \nC•CURE 9000 Hardware Configuration Guide \nChapter 12 \n499 \nEFTA01226430\n", "char_count": 286}, {"efta_number": "EFTA01225932", "page_number": 499, "text_content": "Elevator Configuration Overview \nElevator Configuration Overview \nAccess to floors is managed through Elevator control. Elevators are similar to doors, but have many exit points \nwhich are determined by the floor objects. Floors are created independently from controllers, and are integrated into \nElevators through the definition of elevator buttons (see Creating a Floor on Page 399). Elevator control requires \nreaders, inputs, outputs, and Personnel Clearances. \nA reader is used to control access to the elevator by authenticating cardholders. \nA cardholder is given access to an elevator by assigning a Personnel Clearance that includes the Elevator to the \ncardholder. \nOutputs are used to control the elevator buttons. When the Output is energized, the button for a floor in the Elevator \nbecomes available for use. \nInputs can be configured to determine at which floor the cardholder exited. When the Elevator door opens at a Floor, \nan Input state change indicates that the door has opened. \nElevators or elevator groups are configured through the use of buttons that represent floors with inputs and outputs. \nYou can then add elevators to clearances that are used to control which cardholders can access the elevators and \nfloors and at what times. \nYou can configure Elevators for iSTAR and apC controllers. \n■ iSTAR Elevators on Page 505 \n■ apC Elevators on Page 519 \nNOTE \nNOTE \nElevators are associated with the time zone that is used by the elevator's inputs, outputs, and readers. \nElevator controls and Clearances for Elevators have not been evaluated by UL, and cannot be used in \nUL Listed applications. \n500 \nChapter 12 \nC•CURE 9000 Hardware Configuration Guide \nEFTA01226431\n", "char_count": 1698}]}