Schlage AD400 Quick Manual

Wireless & hardwired readers and pims
Hide thumbs Also See for AD400:
Table of Contents

Advertisement

System Galaxy Quick Guide
SCHLAGE AD400/AD300
635-CPU & 635-DSI Boards are Required
System Galaxy Integration to Schlage AD400/AD300
CONFIGURATION AND OPERATION
WIRELESS
HARDWIRED READERS and PIMS
&
SG 10.2.0
(
)
OR HIGHER
UPDATED
MAY 2015
Page 1

Advertisement

Table of Contents
loading

Summary of Contents for Schlage AD400

  • Page 1 System Galaxy Quick Guide CONFIGURATION AND OPERATION SCHLAGE AD400/AD300 SG 10.2.0 WIRELESS HARDWIRED READERS and PIMS & OR HIGHER UPDATED 635-CPU & 635-DSI Boards are Required MAY 2015 System Galaxy Integration to Schlage AD400/AD300 Page 1...
  • Page 2 Guide No claims are made as to the accuracy or completeness of this document. This document describes how to wire & configure the Schlage PIM to work with the Galaxy DSI RS-485 Board, as well as how to configure wireless Integrating System Galaxy with readers into the System Galaxy software.
  • Page 3: Table Of Contents

    UNSUPPORTED READER OPTIONS ..................6 INTEGRATION OVERVIEW ....................7 UPDATING OR EXPANDING EXISTING SYSTEMS ............. 8 1.4.1 ADDING AD400’s to an existing legacy system ............8 1.4.2 ADDING AD300’s to an existing ad400 System ............8 OVERVIEW OR AD300 & AD400 Integration ............... 9 1.5.1...
  • Page 4 Setting Reader Alarm Options .................. 38 4.2.5 Setting Reader PASSBACK/WHO’S IN Options ............39 4.2.6 UNSUPPORTED Reader Options ................39 5 APPENDIX OF TABLES AND TIPS ..............41 READER MAPPING TO DEVICE ADDRESS TABLE ............41 System Galaxy Integration to Schlage AD400/AD300 Page 4...
  • Page 5 Figure 2 – AD400 DATA FLOW DIAGRAM ....................19 Figure 3 – Diagram of Valid Numbering for AD400’s ................... 22 Figure 4 – MIXED-NETWORK DIAGRAM: AD400 & AD300 Readers on RS-485 Multi-drop ......23 Figure 5 – Example A: SKIP/OMIT A NUMBER is OK/VALID ................. 24 Figure 6 –...
  • Page 6: Introduction & Requirements

    AD400 PIMs and Readers, as well as AD300 Readers. • Schlage Wireless Test Kit • AD400 & AD300 Readers come in ABA and Wiegand formats – you cannot mix card formats on the same network bus (i.e. DSI board section)
  • Page 7: Integration Overview

    Galaxy Panel. The Galaxy Panel returns the access decision to the PIM & logs event with the Comm. Server and SysGal database. Figure 1 – SYSTEM DIAGRAM: AD400 PIM/Readers on RS-485 Multi-drop IMPORTANT  The Card + PIN “high-security mode” is not supported at this time.
  • Page 8: Updating Or Expanding Existing Systems

    MIXED NETWORK: You can install the AD300 hardwired reader onto the same network bus with existing AD400 wireless hardware as long as you do the following: You must address the AD300 Readers to a binary value that is not used by any AD400 readers on the same •...
  • Page 9: Overview Or Ad300 & Ad400 Integration

    1.5.3 AD300 & AD400 “MIXED NETWORKS” RS-485 NETWORK The AD400 PIMs & 300 reader models can be installed on the same 485-channel of the DSI board, which is called a “mixed-network”. While there are programming advantages to installing the AD300 readers on dedicated network, Galaxy offers the “mixed-network”...
  • Page 10: Documentation References

    Chap. 2 Configuration of Schlage and Galaxy Hardware: Instructions to configure the Schlage PIMs & • Readers; linking and connecting them to the SG hardware. Chap. 3 Configuration of Galaxy Software: Instructions to configure the Schlage PIMs and Readers in the • SG hardware.
  • Page 11: System Requirements

     DIO Board = 1: (counts as 1 device regardless of the attached inputs or outputs).  DSI Board for Schlage Readers: You must count every Schlage reader as 1 device. This applies to AD400, AD300, and legacy model ODT PIM to wireless WAPMs.
  • Page 12 1.7.1.3 DSI Board Specifications (SG 10.2.0) 1) The DSI board(s) must be running a minimum of v5.0 to integrate with AD400 & AD300 readers. IMPORTANT: DO NOT INTERRUPT POWER to the while DSI boards are flashing! 3) Each DSI board has two RS-485 Channels per board: Specifications are listed per 485-channel [and per board] a) Jumper wires must be installed between R+ and T+ terminals and between R- and T- terminals.
  • Page 13 1.7.1.4 Addressing AD-Series PIMs & Readers (unit numbering and HI-LO ranges): a) Each AD400 Reader must have a unique number on the 485-channel (1-16 is valid; zero is not valid in Galaxy). Avoid creating duplicate reader numbers as this will cause undesirable behavior.
  • Page 14 If you are mixing AD300 readers with AD400 PIMS, then the reader number you assign to the AD300 must be valid and unique on the network and CANNOT be a number within the HI-LO range of an AD400 PIM. Example (if the AD400 PIM HI-LO Range is 1-5, then AD300 Readers must use 6 and above.
  • Page 15 You must upgrade your Galaxy Software to 10.2.0 and your controllers’ CPU Flash version to 5.0 b) Adding Schlage AD400 Readers: if you have existing older model PIM-485 OTD PIM/Readers, you can add the newer model AD-400 PIM/readers to the same DSI 485-network bus with the following stipulations.
  • Page 16: Schlage Hardware Requirements

    1) Install MS Windows 7 or XP Mobile Device Driver (download free from Microsoft if your PC needs it) 2) Schlage Utility Software (SUS) for HHD (can be download from Schlage and transferred to the HHD) 3) Schlage Hand-Held Device (HHD) with USB cable and Power cable is required (loaded with the SUS).
  • Page 17: System Galaxy Software Requirements

    3) SG Programming Serial Channel: Each DSI Section (channel) must be configured in System Galaxy. Set the correct format “Schlage Wiegand Reader” OR “Schlage ABA Reader” (droplist). IMPORTANT: you cannot mix ABA and Wiegand readers on the same DSI 485 channel.
  • Page 18: Schlage Software Requirements

    1.7.4 SCHLAGE SOFTWARE REQUIREMENTS 1) The Schlage Utility Software (SUS) must be installed on the HHD (typically this comes preinstalled on your HHD) You MUST REMEMBER YOUR PASSWORDS to the HHD • Do not try to couple more than one Hand Held Device to the same door; each door can be coupled to •...
  • Page 19: Overview Of Event Communication

    Example: If the Galaxy panel does not return a response to a card read, several things could be the cause. • the wireless signal/range or channel could be receiving interference, • the Schlage reader may need to be linked or coupled, • the reader or PIM addressing could be invalid, the RS-485 wiring could be the problem, •...
  • Page 20: On-Line Events Explained

    » This can occur if the Communication/Database Server, database engine, or core GCS Services are down. » Access decisions are based on the rules stored in the panel’s memory. » Offline events are available in SG Activity History Reports after the event buffer has been transmitted. System Galaxy Integration to Schlage AD400/AD300 Page 20...
  • Page 21: What Events Come From A Schlage Reader

    2.3 WHAT EVENTS COME FROM A SCHLAGE READER The following events are communicated from the Schlage Readers.  VALID CARD – is generated when a card is presented and is authorized by the Galaxy 635 Controller  INVALID CARD – is generated when a card is presented at the reader that does not have authorization to enter that door/or is not authorized at that time (access group/schedules in the Galaxy panel apply).
  • Page 22: Numbering Schemes For Pims & Wireless Readers

    2.4.1 VALID ADDRESSING OF AN AD400-ONLY NETWORK You must use unique numbers for the PIM ID and Readers. The diagram below shows an example of valid device numbering for Schlage AD-400 PIM & AD-400 Wireless Readers. Figure 3 – Diagram of Valid Numbering for AD400’s...
  • Page 23: Addressing Readers On A Mixed-Network

    • An AD300 Reader address cannot be used as an AD400 PIM address. • AD300 Readers must be given a binary address that is outside of the HI-LO Range of any AD400 PIM on that same network bus. Notice that Readers 5 and 6 are AD300’s – and they are not within the two AD400 PIM ranges of 1-2 and 3-4.
  • Page 24: Device Addressing Exceptions

    Figure 6 – Example B: DUPLICATE or OVERLAPPING NUMBERS ARE INVALID CAUTION: If you need to correct a duplicate, overlapped or incorrectly numbered a reader, you may need to re-link some or all the readers on the network. System Galaxy Integration to Schlage AD400/AD300 Page 24...
  • Page 25: Configuring Hardware

    You can also the manuals them on the Galaxy website www.galaxysys.com. Click on the Support link on the left • side menu, then click Technical Support; then locate the Documentation at the bottom of the Tech Support page. System Galaxy Integration to Schlage AD400/AD300 Page 25...
  • Page 26: Wiring Pims To Galaxy Dsi-485 Board

    You must ground the shielding on for every segment of RS-485 cable on one end. The • following diagram shows shielding grounded on the controller end. The PIM unit should be powered on a separate power supply. • Figure 7 – WIRING DSI 485-Channel to AD-400 PIM System Galaxy Integration to Schlage AD400/AD300 Page 26...
  • Page 27: About Installing The Schlage Hardware

    3.2 ABOUT INSTALLING THE SCHLAGE HARDWARE Installing the Schlage AD-400 hardware requires the use of a Hand Held Device and the SUS (Schlage Utility Software). Schlage Software Utility User Guide covers how to do this in step-by-step instructions. YOU WILL NEED THE FOLLOWING SCHLAGE MANUALS AND DEVICES...
  • Page 28: Configuring System Galaxy Software

    The System Galaxy software must be programmed with the information about the Controller, DSI and Readers. The following subsections describe configuring the System Galaxy software for Schlage Wireless readers. The main SG software manual describes the programming of cards, access rules, schedules, etc.
  • Page 29: Configuring System Registration

    5) Click [Apply] to save changes. Max Readers cannot be less than the Max DSI Readers Max Readers cannot be less than the Max DSI Readers Registration Code must be obtained by an authorized Galaxy Dealer System Galaxy Integration to Schlage AD400/AD300 Page 29...
  • Page 30: Adding The Loop/Cluster In System Galaxy

    Communication Service). you can click the [ This Computer ] button if you are programming this on the communication server.  Click [ Apply ] to save settings. Figure 9 – Loop/Cluster Properties: Configuring the Loop System Galaxy Integration to Schlage AD400/AD300 Page 30...
  • Page 31: Adding The Control Panel & Dsi Board In System Galaxy

    6. Configure Alarm I/O Groups and other Options as needed. You would only use Alarm I/O Groups here if you were monitoring the controller alarm events. 7. Click [ Apply ] to save the configuration. Figure 10 – Controller Properties: Configuring a 635/600-series Controller System Galaxy Integration to Schlage AD400/AD300 Page 31...
  • Page 32: Configuring The Serial Channels In System Galaxy

    7. “check” the appropriate reader numbers ID’s that you have attached to this DSI channel. 8. Then Apply to save changes. Figure 11 – Serial Channel: AD300-ONLY ( HARDWIRED NETWORK ) See the following page to see the mixed-network and wireless only network setup. System Galaxy Integration to Schlage AD400/AD300 Page 32...
  • Page 33: Figure 12 – Serial Channel: Ad400-Only ( Wireless Network )

    Figure 12 – Serial Channel: AD400-ONLY ( WIRELESS NETWORK ) Figure 13 – Serial Channel: AD300 & AD400 ( MIXED NETWORK ) System Galaxy Integration to Schlage AD400/AD300 Page 33...
  • Page 34: Configuring The Reader Properties In System Galaxy

    Figure 14 – Reader Properties: Configuring the PIM Number AD300 ONLY (HARDWIRED) In this screen shot, notice that DSI Board-5 Section-2 Reader-4 automatically takes the PIM ID of 4. Auto-numbering of the PIM ID is only done on dedicated AD300 networks. System Galaxy Integration to Schlage AD400/AD300 Page 34...
  • Page 35: Figure 15 – Reader Properties: Configuring The Pim Number Ad400 Only (Wireless)

    In this screen shot, notice that the PIM Number must be configured by the installer. For an AD400 Reader, the PIM number must match the PIM number that this reader is linked to. For an AD300 Reader, the PIM number must match the actual Reader Address.
  • Page 36: Setting Reader General Properties

    The General Options tab offers a variety of options to control reader events. Figure 17 – Reader Properties: Configuring the General Options Disabled or grayed out options are not supported for Schlage readers System Galaxy Integration to Schlage AD400/AD300 Page 36...
  • Page 37: Setting Reader Schedules

    The Schedules tab contains fields that affect the timing of the locking and unlocking at the reader. Disabled (grayed) features are not available for Schlage Wireless readers in SG 9/10. Auto Unlock Schedule: when selected, the door or Wireless Reader will receive an unlock command from the access control panel when the schedule becomes active.
  • Page 38: Setting Reader Alarm Options

    One .wav file can be selected to play when the alarm event occurs. Figure 19 – Reader Properties: Configuring the Alarm Options Disabled or grayed out options are not supported for Schlage readers System Galaxy Integration to Schlage AD400/AD300 Page 38...
  • Page 39: Setting Reader Passback/Who's In Options

    The following reader options are not supported with Schlage wireless readers. • Relay-2 configuration is unsupported • You cannot use a Schlage reader for an elevator reader when wired through a DSI board • Door Group and Door Interlock features are unsupported •...
  • Page 40 System Galaxy Integration to Schlage AD400/AD300 Page 40...
  • Page 41: Appendix Of Tables And Tips

    The hardware entry (shown above) is an example of how to record hardware addressing. Info in gray is an example of what you expect to see in the SG Reader Properties when you map readers to the Schlage PIM/reader numbers.
  • Page 42 GALAXY HARDWARE APERIO HARDWARE SG SOFTWARE No. of Locks Enabling of DSI Mapping of reader LOOP# / UNIT # BOARD ID SECTION ADDRESS ‘paired’ to HUB Readers numbers System Galaxy Integration to Schlage AD400/AD300 Page 42...

This manual is also suitable for:

Ad300

Table of Contents