635/600-SERIES HARDWARE INSTALL GUIDE
Chapter-Page
1-28
Figure 7 – 600/635-Model Controller Configuration Example:
This
example
shows of how the Controllers/CPUs are grouped into
Loop
/
Clusters
and configured
connect to the
System Galaxy Event Service
using the TCP/IP Ethernet network (
LAN
/
WAN
).
Every
600/635-Model Controller (CPU)
is assigned a unique/valid
Loop/Cluster ID
(i.e. 1, 2, 3 …).
Each
Control Panel CPU
is assigned a unique/valid
Unit ID
(1, 2, 3 …) within its loop/cluster.
Each Daughter Board (DPI/DRM, DIO, DSI) is given a unique/valid
Board ID
(1, 2, 3 …) within its panel.
NOTE:
Software programming must match exactly to the configuration of the hardware (see Appendix for Templates to
record your actual CPU and Board configuration as you install. This helps you keep track when programming software.
NOTE: See Chapter-2 for step-by-step instructions for the CPU and Board configuration.
NOTICE: The panels behave as if they are on the same loop/cluster based on the assigned Loop/Cluster ID. Each
controller/panel connects to the SG Communication/Event Server using the TCP/IP Ethernet network. The SG Software
will identify and treat the panels as being on the same Loop/Cluster when logging events, issuing loop-level commands,
and loading/managing system configuration, (i.e. adding/deleting cards, managing access privileges, schedules, etc.).
