10.07.2015 Views

C•CURE 800/8000 Hardware Configuration Guide - Tyco Security ...

C•CURE 800/8000 Hardware Configuration Guide - Tyco Security ...

C•CURE 800/8000 Hardware Configuration Guide - Tyco Security ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

IndexapC/L, continuedevent to activatewhen panel nearly full 3-14main panel layout 3-11, 5-13 to 5-17on network ports 7-6panel communicationfailure delay time 3-8poll period 3-8during communications failure 3-9poll timeout delay time 3-8reader LCD messages 3-7readers per 4-2supervised input conditions 3-2time zone 3-6unsupervised input conditions 3-2apC/L dialog box 3-5, 3-6, 9-7apC/L Events dialog box 3-13apC/L FlashRom 3-2apC/L Panel Layout dialog box 3-11Arming an input 5-5Automatic dial out, host dialing panel 9-13,10-15Automatic dialout 9-3Automatically download panels 9-15, 10-16BBoardsadd-on 6-2 to 6-16connecting optional to ACM 1-5connecting optional to PMB 2-5optional 3-3CC•CURE SystemapC, apC/8X, apC/L 3-2C•CURE System Administration Applicationconfiguring connection verificationmessages 2-30configuring secondary communications path1-34, 2-31using to set up primary communicationspath 1-32, 2-28Card Format dialog box 4-27Card formatscard number A-2company code A-2configuring 4-5, 4-26, 4-32encrypted magnetic A-8expiration date A-3facility code A-2fieldsto define 4-31, A-3within a card A-2fixed data A-2issue code A-2Longitudinal Redundancy Check (LRC) A-3magnetic 4-27, A-5offset value A-9parity 4-31, A-2site code A-2Wiegand A-6Card number A-2entry, configuring a reader keypad for 4-9Card readerscard formats for 4-5configuring 1-26, 4-2, 4-15configuring on first, second ACM 1-24connecting to ACM 1-5connecting to GCM 2-5C•CURE <strong>800</strong>/<strong>800</strong>0 <strong>Hardware</strong> <strong>Configuration</strong> <strong>Guide</strong>Index–3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!