635/600-SERIES HARDWARE INSTALL GUIDE
Chapter-Page
1-27
1.13
Board Programming Requirements
1. 635- model boards can be configured using the Galaxy 635 Web Configuration Tool.
The 635 Web Tool opens in a standard Web Browser. The Tool automatically finds all Galaxy CPUs by their
MAC address, provided the panels are online/on the same network segment as the Web Tool – and provided
the controller cabinet door is open (tamper switch open).
OPTIONALLY: If the installer cannot access the network/segment and connect to the 635-model boards via the
Web Tool, the installer can connect directly to the boards via the RS-232 Programming Port using a Standard Serial
Programming Cable. In this method, the installer uses a Terminal Emulator (i.e. Putty, HyperTerminal
®
, etc.) to
connect to the panel CPU - and program the 635-CPU Network IP Settings, Cluster ID, Controller Unit ID, and GCS
Event Server IP Address, as well as other CPU options. Be aware all 635-Model Daughter Boards have a dipswitch
to configure the Board ID and other options. [600-model CPUs and Daughter Boards can also be programmed via
the Terminal Emulator].
The RS-232 Programming Serial Cable comes with controller enclosure:
•
Cable Pin-out
must be:
Pin 2 to Pin 2, Pin 3 to Pin 3, Pin 5 to Pin 5.
•
The cable must have a DB9 female connector on one end and a DB9 male connector
on the other end
•
Connect the programming serial cable to the
J4
serial port on the CPU Board and the
standard 9-pin serial port on the PC or laptop that is running a Terminal Emulator.
Putty / Terminal Emulator Session parameters:
BAUD Bits per Second
=
57,600 K BPS
Parity
=
None
Data Bits
=
8
Stop Bits
=
1
Flow Control
=
None
See
the Web Configuration Tool Guide for information on how to use the tool to configure and test the controller, boards
and communication ports.
2. Each Controller must have a unique Unit ID number within the Loop/Cluster
(see Figure 6).
3.
The CPU Board ID
is “0” by default – this value cannot be changed.
4. The CPU Number should be set to “1”.
If a second (dual) CPU board is installed, its CPU number
should be set to “2”.
5. All daughter boards (DPI, DIO, DSI, etc.) must have a unique Board ID
within their Unit
(controller/panel). Board numbers 1 through 16 are valid for each controller.
The 635 DPI must be addressed to a unique binary value on the controller bus using the on-board dip switch located on the
back edge of the board. The 635 DPI is compatible with either 635 or 600 CPU and can coexist with 600 DPIs, DIO, DSI.
6. Unique/Valid IP Addresses must be used for 6xx-series controllers.
The CPU can have a static
IP Address or non-routable IP Address.
6xx-series also supports DHCP Addressing; however, it is
not recommended for the stability of the Access Control System. Note: a static IP Address cannot be
blank or zeros. You must program a private IP address even if using the DHCP.
7. The controllers communicate with the Event Server on port 3001.
Port 3001 must be open and
unblocked at firewalls, routers and switches, etc. for communications to occur.
NOTICE:
The 6xx-series board settings must match the software programming for proper operation (see Figure 6).
Hardware is usually installed and configured before the software. If the software is already programmed, you must
use the Loop, Unit, and Board ID’s set in the software – these settings are found in the Loop and Controller
Properties screens.
TIP
:
Use Hardware Programming Templates from Appendix A
(
which can be copied as
needed
)
to record panel settings and locations for use when the software is being programmed
.
