Schlage AD-400 User manual

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

System Galaxy
AD-400/AD-300
Guide
Integrating System Galaxy with
AD-400 Wireless & AD-300 Wired
using Galaxy 635- DSI Board
RS-485 Serial Communication
Information in this document is subject to change without notice.
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
readers into the System Galaxy software. This guide does not supersede
the manufacturer’s documentation for products
not manufactured by
Galaxy Control Systems.
3rd Edition – Republished for 10.4
Copyright © 2013

Galaxy Control Systems

All rights reserved
Galaxy Control Systems
3 North Main Street
Walkersville MD 21793
301-845-6600
www.galaxysys.com
No part of this document may be reproduced, copied, adapted, or
transmitted, in any form or by any means, electronic or mechanical,
for any purpose, without the express written consent of Galaxy
Control Systems. Copyright protection claims include all forms and
matters of copyrighted material and information, including but not
limited to, material generated from the software programs, which
are displayed on the screen such as icons, look and feel, etc.
Microsoft®, Windows®, Windows NT®, Active Directory®, MS-DOS®,
SQL Server®, and Windows Server System®, are registered
trademarks of the Microsoft Corporation in the U.S. and other
countries.
IR, Ingersoll-Rand, Schlage®, Schlage Wireless™ are trademarks
and/or registered trademarks of their respective owners. Adobe®
and Acrobat®are registered trademarks of Adobe Systems Inc.
Technical illustrations are creations of the technical author.
System Galaxy Integration to Schlage AD400/AD300 Page 2

Table of Contents
1Introduction & Requirements ............................................................................. 6
1.1 VERSIONS & COMPATIBILITY.............................................................................................. 6
1.2 UNSUPPORTED READER OPTIONS.................................................................................... 6
1.3 INTEGRATION OVERVIEW.................................................................................................... 7
1.4 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
1.5 OVERVIEW OR AD300 & AD400 Integration ....................................................................... 9
1.5.1 AD300-ONLY “dedicated hardwired” RS-485 network...............................................9
1.5.2 AD400-ONLY “dedicated wireless” RS-485 network..................................................9
1.5.3 AD300 & ad400 “mixed networks” RS-485 network...................................................9
1.6 DOCUMENTATION REFERENCES .....................................................................................10
1.6.1 OUTLINE OF THIS GUIDE.......................................................................................10
1.6.2 RELATED DOCUMENTATION ................................................................................10
1.7 SYSTEM REQUIREMENTS..................................................................................................11
1.7.1 GALAXY HARDWARE REQUIREMENTS ...............................................................11
1.7.2 SCHLAGE HARDWARE REQUIREMENTS ............................................................16
1.7.3 SYSTEM GALAXY SOFTWARE REQUIREMENTS................................................17
1.7.4 SCHLAGE SOFTWARE REQUIREMENTS.............................................................18
2OVERVIEW OF EVENT COMMUNICATION...................................................... 19
2.1 ON-LINE EVENTS EXPLAINED........................................................................................... 20
2.1.1 ACCESS DECISIONS AT THE PANEL....................................................................20
2.1.2 UNINTERRUPTED EVENT LOGGING....................................................................20
2.2 OFF-LINE EVENTS EXPLAINED .........................................................................................20
2.3 WHAT EVENTS come from a SCHLAGE READER ...........................................................21
2.4 NUMBERING SCHEMES FOR PIMS & WIRELESS READERS.........................................22
2.4.1 Valid Addressing of an AD400-only Network............................................................22
2.4.2 Addressing Readers on a Mixed-Network................................................................23
2.4.3 Device Addressing Exceptions .................................................................................24
3Configuring Hardware....................................................................................... 25
3.1 About Installing the 635-series Hardware.........................................................................25
3.1.1 The Galaxy Hardware Panel & CPU.........................................................................25
3.1.2 Wiring PIMs to Galaxy DSI-485 Board .....................................................................26
3.2 About Installing the Schlage Hardware.............................................................................27
3.2.1 Schlage Process Outlined ........................................................................................27
4CONFIGURING SYSTEM GALAXY SOFTWARE.............................................. 28
4.1 Configuring the 635 Controller and DSI in the software..................................................28
System Galaxy Integration to Schlage AD400/AD300 Page 3

4.1.1 About using System Galaxy Software ......................................................................28
4.1.2 Signing-in to the System Galaxy Software ...............................................................28
4.1.3 CONFIGURING System REGISTRATION...............................................................29
4.1.4 Adding the Loop/Cluster in System Galaxy..............................................................30
4.1.5 Adding the Control panel & DSI Board in System Galaxy........................................31
4.1.6 Configuring the Serial Channels in System Galaxy..................................................32
4.2 Configuring the Reader Properties in System Galaxy.....................................................34
4.2.1 Setting Reader Properties in System Galaxy...........................................................34
4.2.2 Setting Reader General Properties...........................................................................36
4.2.3 Setting Reader Schedules........................................................................................37
4.2.4 Setting Reader Alarm Options..................................................................................38
4.2.5 Setting Reader PASSBACK/WHO’S IN Options ......................................................39
4.2.6 UNSUPPORTED Reader Options............................................................................39
5APPENDIX OF TABLES AND TIPS ................................................................... 41
5.1 READER MAPPING TO DEVICE ADDRESS TABLE..........................................................41
System Galaxy Integration to Schlage AD400/AD300 Page 4

List of Tables and Figures
Figure 1 – SYSTEM DIAGRAM: AD400 PIM/Readers on RS-485 Multi-drop..................................................... 7
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 – Example B: DUPLICATE or OVERLAPPING NUMBERS ARE INVALID ...............................................24
Figure 7 – WIRING DSI 485-Channel to AD-400 PIM....................................................................................26
Figure 8 – Sign On/Off: Logging into System Galaxy ...................................................................................28
Figure 9 – Loop/Cluster Properties: Configuring the Loop........................................................................... 30
Figure 10 – Controller Properties: Configuring a 635/600-series Controller.................................................. 31
Figure 11 – Serial Channel: AD300-ONLY ( HARDWIRED NETWORK ) ........................................................... 32
Figure 12 – Serial Channel: AD400-ONLY ( WIRELESS NETWORK )................................................................ 33
Figure 13 – Serial Channel: AD300 & AD400 ( MIXED NETWORK ) ............................................................... 33
Figure 14 – Reader Properties: Configuring the PIM Number AD300 ONLY (HARDWIRED)............................34
Figure 15 – Reader Properties: Configuring the PIM Number AD400 ONLY (WIRELESS) ................................35
Figure 16 – Reader Properties: Configuring the PIM Number AD300 & 400 (MIXED NETWORK)....................35
Figure 17 – Reader Properties: Configuring the General Options.................................................................36
Figure 18 – Reader Properties: Configuring the Timing/Schedules .............................................................. 37
Figure 19 – Reader Properties: Configuring the Alarm Options ................................................................... 38
Figure 20 – Reader Properties: Configuring the Passback/Who’s In............................................................. 39
Figure 21 – MAPPING PIMS AND READERS IN SYSTEM GALAXY SOFTWARE.................................................41
DOCUMENT HISTORY
DATE
HISTORY
APR 2013 1st Edition published with SG 10.2 release which introduced the AD300 AND AD400 product
integration.
OCT 16, 2014 2
nd
Edition published for SG10.4 Release, included a requirements and instructions about the
system registration for branded wireless locks.
System Galaxy Integration to Schlage AD400/AD300 Page 5

1Introduction & Requirements
This guide provides requirements and installation/configuration instructions for integrating Schlage AD400
wireless technology and AD300 Hardwired Readers with System Galaxy.
1.1 VERSIONS & COMPATIBILITY
System Galaxy version 10.2 supports Schlage AD400 Wireless PIMs/Readers and AD300 Hardwired Readers.
•System Galaxy software v10.2.0
•635 panels running Flash V5.0; including 635-CPU & 635-DSI Boards
•AD400 PIMs & Wireless Readers (can install on a dedicated 485-bus or mixed with AD300’s)
•AD300 Hardwired Readers (can install on a dedicated 485-bus or mixed with AD400’s)
•Schlage Utility Software (SUS) and Hand Held Device (HHD) are needed for addressing and
linking 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)
For information about integrating with legacy Schlage PIMs/WAPMs, see the Galaxy 485 ODT PIM Guide.

For complete list of requirements, see the Requirements section of this guide .
1.2 UNSUPPORTED READER 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
•Duress is not supported
•Pin Schedule Mode is not supported
•High security mode (card plus pin) is not supported
•Any grayed option is not supported – See the section in this guide that covers Reader Properties programming.
System Galaxy Integration to Schlage AD400/AD300 Page 6

1.3 INTEGRATION OVERVIEW
The Galaxy 635 Dual Serial Interface (DSI) board connects to the AD-400 PIM using RS-485 two-wire, multi-
drop configuration. The AD-400 PIM maintains a wireless connection to the AD-400 Readers (door units) on
one side of the system. The AD-400 PIM connects to the Galaxy access control panel via the DSI 485 board
on the other side of the system. The AD-400 PIM converts the data from wireless protocol to RS-485 and
visa-versa. The door events and credentials presented at the wireless door are sent thru the PIM to the
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.
Each section of the DSI board can support the same card format (i.e. either all Wiegand Readers or
all ABA Reader). The diagram above shows a system that has mixed card technology. You can see
how you must install the ABA readers on a different 485-network bus (DSI section).
System Galaxy Integration to Schlage AD400/AD300 Page 7

1.4 UPDATING OR EXPANDING EXISTING SYSTEMS
NOTICE: Legacy Wireless 485-PIM-ODT & WAPMs are still supported in SG 10.2; however the Galaxy
CPU must be flashed up to 5.0 – if you are upgrading from SG 8 or 9, you may want to contact dealer
technical support to ensure you properly step through the hardware flash upgrade.
1.4.1 ADDING AD400’S TO AN EXISTING LEGACY SYSTEM
a) DEDICATED NETWORK: You can install AD400 wireless hardware onto a separate DSI section. In this case
you must configure the Serial Channel programming (in SG software) to use the Network Type = AD400
(wireless only) for the both new AD400 network bus as well as the legacy Schlage ODT bus. The addressing
requirements must meet specifications – see the following sections on addressing AD400 PIMs and Readers.
b) SHARED NETWORK: You can install the AD400 wireless hardware onto the same network bus with the
existing legacy PIMs and Readers as long as you do the following:
•You must assign unique AD400 PIM addresses that do not duplicate the ODT PIM addresses.
•You must assign unique addresses to AD400 Readers that do not duplicate the legacy readers on the
network bus.
•You cannot cross-link the equipment: Legacy readers can only link to legacy PIMs and visa-versa, AD400
readers can only link to AD400 PIMs.
•You must set the Network Type to “AD400 (wireless only)” on the Serial Channel (in SG software).
1.4.2 ADDING AD300’S TO AN EXISTING AD400 SYSTEM
a) DEDICATED NETWORK: You can install AD300 hardwired readers onto a separate DSI section. In this case
you must set the Network Type to “AD300 (hardwired only)” the Serial Channel (in SG software) for the new
AD300 network bus. Note: It is a requirement that even hardwired readers have a PIM address. Thereforethe
SG software auto-assigns a PIM number to the Reader that matches the binary address of the AD300 Reader.
b) 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
network bus.
•You must use treat the binary address of an AD300 reader its own PIM number; and therefore you cannot
give the same binary address to an AD300 Reader and an AD400 PIM.
[Example: if an AD300 Reader is addressed to “4”, then there cannot be any AD400 PIMs addressed to 4].
•You must set the Network Type to “AD300 & 400 (mixed-network)” on the Serial Channel (in SG software).

See other sections in this guide for diagrams of the mixed-networks and dedicated networks. Also
See Creating a “Mixed-Network” Channel and Creating an AD300-Only Channel for step-by-step
instructions.
System Galaxy Integration to Schlage AD400/AD300 Page 8

1.5 OVERVIEW OR AD300 & AD400 INTEGRATION
The AD-series readers can be installed separately or in mixed-networks. The following paragraphs give you
and overview of the installation types.
SG 10 software supports the following network types for Schlage Wireless Readers:
•AD300-Only (dedicated) = the 485-Channel is connected only to AD300 hardwired readers.
•AD400-Only (dedicated) = the 485-Channel is connected only to AD400 wireless readers.
•AD300 & AD400 (Mixed Network)= 485-Channel is connected to both Wireless and Hardwired Readers.
1.5.1 AD300-ONLY “DEDICATED HARDWIRED” RS-485 NETWORK
The AD300 Reader is hard-wired to the 485-network section of the Galaxy DSI board in a two-wire, multi-
drop configuration. There is no PIM unit to install. In the System Galaxy Serial Channel programming, the
DSI section must be set to use AD300 Only. Also, System Galaxy will automatically assign the PIM number in
the Reader Properties screen to be the same value as the AD300 Reader ID (e.g. Reader 1 would assume PIM
1, Reader 4 would assume PIM 4).
1.5.2 AD400-ONLY “DEDICATED WIRELESS” RS-485 NETWORK
The AD400 PIM is hard-wired to the 485-network section of the Galaxy DSI board in a two-wire, multi-drop
configuration. The PIMs are then linked to the wireless AD400 Readers using the Hand Held Device. In the
System Galaxy Serial Channel programming, the DSI section must be set to use AD400 Only. In the Reader
Properties screen, the operator must assign the correct PIM number to each reader according to what was
programmed into the PIM.
Why make an ‘AD300-only’ channel?
» Convenient programming - the SG software automatically sets the PIM numbers (in the software) for
every AD300 reader that you add to the software from the Serial Channel screen.
» Eliminate potential conflicts with wireless PIM addresses – PIM addressing can be tricky in “mixed
network” mode. It is easy to create a duplicate PIM or address conflict with
» Simplify hardware installation/configuration – especially if the existing PIMs will need to be reconfigured
to accommodate the AD300 readers.
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” configuration for convenience. You must keep in
mind that the AD300 Reader must assume a phantom PIM ID that is the same value as the reader ID.
Therefore any address that has been assigned to an AD300 Reader cannot be assigned to an AD400 PIM or
AD400 reader on that same section. In the System Galaxy Reader Properties screen, you must take care to
assign the PIM numbers correctly.
Why make a ‘MIXED NETWORK’ channel?
» Feasibility and convenience – it may not be feasible to dedicate a channel to one type of reader due to
placement of PIMS and panels.
System Galaxy Integration to Schlage AD400/AD300 Page 9

1.6 DOCUMENTATION REFERENCES
1.6.1 OUTLINE OF THIS GUIDE
•Chap. 1 Overview:overview of the system integrationwith Schlage AD-400 Wireless and AD-300 Wired.
•Chap. 1 Requirements: Galaxy and Schlage requirementsfor integrating Schlagewith System Galaxy.
•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.
1.6.2 RELATED DOCUMENTATION
The latest versions ofthese manuals are found online.
System Galaxy http://www.galaxysys.com/index.php?tpl=support/index
SG v10 System Specification Guide System specifications for the database, software, hardware, operating
system; and guidelines for system architecture, as well as 3rd Party
integrations.
SG v10 Software User Guide Describes how to configure and operate most features of the software
635-series Hardware Guide Describes how to install and configure the hardware and its peripheral
devices (readers, inputs, outputs, etc.).
SG Integration to Schlage AD400 Describes wiring the AD-400 PIM to the DSI in the Galaxy panel and
how to configure the DSI & Door properties in System Galaxy. Includes
information on using the Schlage HDD (hand-held) and SUS to re-link
and re-couple the wireless door lock.
Schlage Documentation www.schlage.com/support Look for the row that pertains to AD-400
Schlage Utility Software User Guide
Describes how to use the SUS Software. You must use this Schlage document
to perform the Linking PIMs to Wireless Readers and Coupling the Hand Held
Device to the Wireless Readers
System Galaxy Integration to Schlage AD400/AD300 Page 10

1.7 SYSTEM REQUIREMENTS
The requirements for the Galaxy to Schlage interface is organized by sections; covering Galaxy hardware,
Schlage hardware, Galaxy software, and Schlage Software.
DOCUMENTATION:In addition to this guide, you must also use the Schlage documentation; especially the
Schlage Guide for the SUS Software and the Schlage Hand Held Device. Contact Galaxy Technical
Support for questions beyond the scope of documentation.
1.7.1 GALAXY HARDWARE REQUIREMENTS
1.7.1.1 Minimum CPU FLASH Requirements
System Galaxy SG 10.2.0 with Flash v 5.0 supports both AD400 Wireless and/or AD300 Hard-wired Readers.
Note: support for Schlage AD-400 Wireless Readers/locks began with SG 10.0.0 (came with Flash v 4.75).
IMPORTANT: DO NOT INTERRUPT POWER to the controller unit, CPU, or to any daughter boards
during the flashing process.
IMPORTANT: Make sure all daughter boards have finished flashing before attempting to load boards
or connect devices.
ALSO SEE: See the Appendix of this guide for tips and/or the Galaxy 600-635 Hardware Guide for
detailed flashing instructions.
1.7.1.2 Maximum CPU Device Load
A Galaxy 635-series controller can support up to 64 devices (per CPU board).
The device count (by board type) is listed below:
DPI Board = 2: (i.e supports 2 readers).
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.
DSI Board for ‘other use’ = 2: (i.e. each 485-channel counts as 1 device). This applies to supporting LCD
Modules, Cypress Clocks, and Relay Boards, or if the 485-channels is not in use.
IMPORTANT: DO NOT EXCEED the maximum CPU device load when installing Schlage Readers.
Excessive device-load can cause undesirable behavior of the panel or it’s devices.
System Galaxy Integration to Schlage AD400/AD300 Page 11

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.
2) 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.
b) Each 485-channel operates independently from the other 485-channel. This gives the installer the advantage
of splitting the types of Schlage readers; or installer can use one section for readers while using the other
section for a completely different purpose (such as General Purpose Relay boards, LCD’s, etc.)
c) Each RS485-port supports RS-485 two-wire communication using a multi-drop network configuration.
d) Schlage Readers can be installed in a mixed-network or dedicated network.
Mixed-Network:is when a DSI 485-Channel that has both AD300 Hard-wired Readers installed along with
AD400 wireless readers. Ensure correct addressing of readers/PIMs and setting of HI-
LO reader ranges.
See section on addressing readers for mixed networks.
Dedicated-Network:when a 485-
Channel is dedicated to communicating with only one model of reader.
Thus, the wireless and wired readers are installed on separate 485-channels.
e) Each RS485-port supports up to 16 Schlage Readers (doors) per 485-channel [total 32 Readers per DSI board].
f) Each RS485-port supports up to 16 PIMs per 485-channel [the number of PIMs needed will be based on how
many PIMs it takes to provide reliable RF coverage].
NOTE: Schlage specs an RF signal radius of “up to 200-feet”; but this distance may be reduced by
interference from physical structures, overlapping PIM RF ranges, or other reasons.
4) Galaxy continues to support the older model Schlage PIM-485 OTD readers/PIMs for upgrades. See the older
PIM-485 OTD Guide for requirements and installation of that product line.
System Galaxy Integration to Schlage AD400/AD300 Page 12

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.
b) Each AD400 PIM must have a unique number on the 485-channel (1-16 is valid; zero is not valid in Galaxy).
Avoid creating duplicate PIM numbers as this will cause undesirable behavior.
You must install at least 1 PIM per 485-Network (one PIM can support up to 16 readers).
Test kits are available to determine best PIM placement - see Schlage manuals for details about PIM
placement.
c) All AD400 PIMs require a HI and LO range to be defined.
d) Do not overlap the ranges of one PIM with other PIMs.

The HI Number defines the highest reader number that can link to the PIM.

The LO Number defines the lowest reader number that can link to the PIM.

When numbering and linking readers you can skip or omit using a reader number, but you can’t link
readers that are outside of the HI-LO Range.
e) Each AD300 Reader must have a unique number on the 485-channel (1-16 is valid; zero not valid in Galaxy);
Avoid creating duplicate numbers as this will cause undesirable behavior.
AD300 Readers wire directly to the 485-channel of the DSI. See requirements on Mixed-Networks in this
section.
Since there is no PIM, you must define the HI-LO Range of the AD300 reader in the Reader programming.
This is done using the HHD, which can plug into the bottom of the AD300 reader.
f) REMEMBER! There is a max device load of 64 devices per CPU Board/control panel.
System Galaxy Integration to Schlage AD400/AD300 Page 13

1.7.1.5 Requirements for Mixed-Networks (mixing AD400 & AD300 on same channel)
a) Galaxy supports mixing AD-400 PIMs and AD-300 hardwired Readers on the same DSI 485- Channel.This is
known as a ‘mixed network’. Likewise you can put your AD300’s & AD400s on separate 485-channels, or even
on separate DSI boards in the same or separate controllers where wiring distance or simpler networking is a
factor.
b) 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. AD300 Readers must set a
HI-LO Range as well even though a PIM is not involved – it is configured using the HDD. See section on AD300
Configuration instructions for details.
c) Galaxy also supports a non-mixed or dedicated network for AD400-ONLY and AD300-ONLY, which may be to
your liking.
d) You must set the appropriate Network Type in the Serial Channel Programming screen (in the System Galaxy
software) to match the installation (i.e. Mixed-Network or dedicated network for AD400-ONLY and AD300-
ONLY).
1.7.1.6 Reader Formats for AD-Series
Wiegand and ABA Readers cannot be mixed on the same 485-channel (see System Concept Diagram).
Put ABA readers on a separate 485-channel from the Wiegand readers.
The DSI 485-channels operate independently, so the same board can support one Wiegand channel and one
ABA channel.
1.7.1.7 Stipulations on Termination Resisters
Device terminating resisters may need to be installed on both extreme line ends to dampen line impedance.
Symptoms of line impedance will include intermittent or spotty communications – which will affect the behavior
of the lockset, such as door not unlocking when it should, door unlock schedule not taking effect – provided all
other logical reasons have been eliminated (i.e. programming, configuring and addressing is correct; also wiring
and or RF signal testing is good, all requirements are met, etc.)
System Galaxy Integration to Schlage AD400/AD300 Page 14

1.7.1.8 RS-485 Network Field Wiring Specifications
Connection Max Dist. Wire
DSI to PIM device: 4,000 ft. *; 22 AWG, shielded/twisted pair (ground onone end only)
* RS-485 4,000 ft. to thelast PIM on the DSI 485 channel.
1.7.1.9 Ethernet Network (LAN) Wiring Specifications for 635 Access Control Panel
Connection Max Distance Wire
Galaxy Control Panel: 100 m (328 ft.) Cat 5e Unshielded, port to port LAN twisted-pair (UTP)
to network switch
1.7.1.10 Upgrading existing 485-Networks (older model ODT 485 PIM/Readers):
a) 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.
(1) You cannot cross-link AD400 Readers to the legacy model PIMs, or visa-versa.
(2) You must still meet requirements for unique PIM & Reader addressing and HI-LO ranges of the PIMs
on the network.
Newly added PIMs must meet wiring distance requirements
Newly added PIMs must use a unique address on the 485-channel not already taken by an existing
PIM.
Newly added PIMs must declare a HI-LO Range that does not overlap an existing PIM’s HI-LO
Range.
Newly added AD400 Readers must use a valid and unique address on the 485-channel that is not
already in use by an existing Reader. See Stipulations for Addressing PIMs and Readers in this
section.
Newly added AD400 Readers cannot be linked to existing legacy PIMs
New PIMs and Readers must not interfere with existing RF reliability of existing PIMs
IMPORTANT: It may be advisable to put new readers on separate 485-network and avoid changing
the addressing of existing PIMs or overhauling their configuration since the existing RF channels and
RF ranges are calibrated and working.
System Galaxy Integration to Schlage AD400/AD300 Page 15

1.7.2 SCHLAGE HARDWARE REQUIREMENTS
www.schlage.com/support - download SUS, and installation documentation (PDF Reader required)
www.youtube.com/schlageAD - view training videos that demonstrate installation
SUPPORT: 877-671-7011
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).
IMPORTANT: YOU MUST REMEMBER YOUR PASSWORDS (Operator, Manager and Coupling
passwords must be set up). Be aware that the operator login can only ‘tour’ the doors. Coupling the
HHD to a door (for the sake of configuring it), is only allowed under the Manager login.
IMPORTANT: Keep your coupling password secure.
IMPORTANT: DO NOT SHARE DOORS WHEN YOU COUPLE THE HHD to doors.
4) AD-400 Wireless Firmware Package (download v2.17 Firmware Package from Schlage and transfer to HHD)
5) AD-400 PIM:
PIM must ship with appropriate flash for RS-485 communication; (PTD-2 wiring uses a different flash therefore
you cannot just swap between them);
unit number must be valid in Galaxy (1-16 is supported; zero is not valid to Galaxy);
RS-485 two-wire communication (jumpers installed; see Figure-6 in Section 2.1.2);
IMPORTANT: Galaxy still supports the Legacy PIM 485/WAPMs. You can put AD400’s on a 485-
channel with legacy ODT PIMs/Readers, but you cannot link new AD400 readers with the old ODT
PIMs. You must match wireless reader models the PIM it was designed to work with. All the same
rules apply for unique addressing and HI-LO range whether they coexist on the same 485-network or
on separate channels. See diagram examples in the installation instructions of this guide
6) Credential types supported are card code and keypad code. The keypad must be configured for Type-7 (26bit
Wiegand) using the HHD.
IMPORTANT: The Card + PIN known as “high-security mode” is not supported at this time.
7) AD-400 Wireless Readers:door number must be valid (1-16 is supported; zero is not valid to Galaxy)

Each Wireless Reader must be properly ‘linked’ to a PIM. You can use up to 16 PIMs on a 485-channel in a
multi-drop configuration. Additional PIMs are only needed where one PIM ceases to support the RF ranged
needed. Schlage establishes the RF reliability specifications.
IMPORTANT: Do not duplicate or overlap the door numbers of the Wireless Readers when installing
more than one PIM to cover a 485-channel. If you have to correct a duplicate, overlap or incorrectly
numbered a reader, you must re-link every reader to its correct PIM (see Figure-5 in Section 1.4.2).
8) AD-300 Wired Readers:door number must be valid (1-16 is supported; zero is not valid to Galaxy). The HDD is
physically plugged into the bottom of the AD300 reader in order to configure it.
9) AD-401 Wireless Readers use Wiegand wiring from the PIM TD2 connector to a Galaxy DPI (not DSI)
System Galaxy Integration to Schlage AD400/AD300 Page 16

1.7.3 SYSTEM GALAXY SOFTWARE REQUIREMENTS
1) System Galaxy Software (SG) version 9.6 (or higher )
2) System Registration must including setting the Max DSI-based Reader count.
3) SG Programming Serial Channel: Each DSI Section (channel) must be configured in System Galaxy.
a) Set the correct format “Schlage Wiegand Reader” OR “Schlage ABA Reader” (droplist).
b) IMPORTANT: you cannot mix ABA and Wiegand readers on the same DSI 485 channel.
c) Enable (“check”) the exact same door numbers that you actually installed. You should “uncheck” any door
numbers that you did not actually install.
4) SG Programming Door/Reader: Each Door Reader must be configured in System Galaxy.
a) Set the correct PIM number that the door was linked to during hardware installation.
5) The following Door/Reader options ARE supported for wireless readers:
a) PASSBACK/WHO’S IN feature is supported.
b) Door Groups are supported (but not Man Traps)
6) The following Reader options are NOT supported for wireless readers:
a) GENERAL OPTIONS that are NOT Supported
» Disable Request to Exit Message
» Enabling Duress
» Two Person Rule
» Energize Relay 1 on Pre-Arm delay
» Elevator Reader
» Lock when Door Closes – this is
controlled by the wireless reader.
b) TIMING / SCHEDULE OPTIONS that are NOT Supported
» PIN Required Schedule
» Require Valid Card before auto-unlock
(AKA snow-day rule)
» PIN Mode “High Security”
» Unlock Delay time
» Unlock Duration time
» 2-digit PIN for reclose time
NOTE: PIN Mode ‘Information Only’ is supported for Time & Attendance.
c) RELAY 2 SETTINGS are NOT Supported
» Relay 2 settings do not apply to
wireless readers
» Relay 2 settings only apply to a DPI
NOTE: all Schlage readers use a DSI board
d) GROUP/INTERLOCK OPTIONS that are NOT Supported
» MAN TRAP IS NOT SUPPORTED
» Disable by Door Group
» Notify Group when unsecure
e) ALARM OPTIONS that are NOT Supported
» Duress Alarm I/O
» Reader Heartbeat Alarm I/O
NOTICE: Reader heartbeat is supported and
controlled by the PIM configuration. Reader
Heartbeat frequency is set at the PIM and does
impact battery life on the Reader Unit.
» Any option that is grayed or non-selectable is not available.
System Galaxy Integration to Schlage AD400/AD300 Page 17

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
only one Hand Held Device. If you couple a second Hand Held Device to the door, then it will no longer
work with the first Hand Held Device.
2) The Windows Mobile Synchronization software must be installed on your PC : this is used to transfer Schlage
firmware and software files from your PC, the Schlage HHD and PIM/Schlage devices
If Mobile Synchronization software is not on your PC, go to www.microsoft.com/windowsmobile/en-
us/downloads and download the Mobile Device software that matches your Windows OS.
•Download and install Microsoft ActiveSync = Windows XP
•Download and install Microsoft Windows Mobile Device Center = Windows-7 & Vista.
System Galaxy Integration to Schlage AD400/AD300 Page 18

2OVERVIEW OF EVENT COMMUNICATION
For troubleshooting purposes, it is helpful to understand the data transmission between each component in
the two systems.
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,
•the there could be a maintenance problem with the PIM, Reader or Galaxy ACP
•additionally, the card may not be enrolled or been given access to the door in question, or has not
been loaded to the access control panel
•hardware failure of the components in the system is also a consideration
Figure 2 – AD400 DATA FLOW DIAGRAM
1. Events (card swipe, door lever, etc.) aretransmitted via RF signal from thewireless reader to the AD-400 PIM.
2. The AD-400 PIMsends the event to theGalaxy 635-series Panel using the RS-485 two-wire protocol.
3. The Galaxy 635-series Panellogs the event and returns an access decision (valid or invalid) back to the PIM,
provided thecard has been enrolled/given permission to the Loop &Door for the time period the card was used; and
has been in and loaded to theGalaxy accesscontrol panel.
4. The PIM receives & transmits the access decision to the wirelessreader over wireless protocol.
5. The Galaxy panel also sendsthe event to the Communication Server over TCP/IP to belogged to the SysGal
database anddisplayed on the Monitoring screen of the System Galaxy software.
6. If the SystemGalaxy softwaremonitoring screen isopen, theevents willbe displayed real-time. The System Galaxy
operator can also send doorcommands to the wirelessreader. System Galaxy operatorscan also send door
commands to the reader from the Hardware Tree.
7. Wiring, connections, network equipment and IP setup; wireless RF signal strength/range, PIM channel, PIM linking,
and power all need to be considered when troubleshooting the system.
System Galaxy Integration to Schlage AD400/AD300 Page 19

2.1 ON-LINE EVENTS EXPLAINED
To Galaxy, “Online events” means the Galaxy access control panel is able to communicate with the System
Galaxy database and communication server.
2.1.1 ACCESS DECISIONS AT THE PANEL
The panel always makes the access control decisions based on access privileges and cardholder programming
that is stored in the memory of the panel, regardless of whether the server/database is online or not.
When the panel is online with the Server and Database, it immediately transmits the access decision (granted
or denied) to the Software monitoring screen where the SG operator can monitor the event as well as logging
the event the database for system reporting.
2.1.2 UNINTERRUPTED EVENT LOGGING
Since SG uses true background services, Operators can sign in & out of SG software, or sign in & out of PC
user account, without interrupting the event communication between the panels and the SG Database. The
core GCS services continue operation as long as the PC is powered on. Therefore events that occur while the
SG software is logged out/shut down, or while the user is logged out of the PC OS, will be available from
System Reports based on the logging to the database.
2.2 OFF-LINE EVENTS EXPLAINED
“Offline events” means the Galaxy panel is unable to communicate with the System Galaxy database.
The Galaxy 635 panel is designed to remain fully operational during an ‘off-line’ condition and continues to
provide uninterrupted access control decisions. Events are stored at the panel until the connection to the
database is restored; at which time the panel retransmits all buffered events to the database.
»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