SNAP PAC Redundancy Option User’s Guide
17
17
3: 3: Configuring a Control SystemChapter 3
3: Configuring a Control
System
This chapter describes how to use PAC Control and the PAC Redundancy Manager to configure the
controllers and arbiter.
In This Chapter
........................................................................................................
Assigning a Primary IP Address to ENET 1 on each Controller
....................
Assigning an IP Address to the Arbiter
..................................................................
Creating a Control Engine for Controller Redundancy
...................................
Commissioning the Controllers for Redundancy
..............................................
........................................................................................................
What You Will Need
•
Two PAC S-series controllers and the components included with the Redundancy Option Kit
connected as described in
“2: Connecting the Hardware” on page
•
PAC Project Professional 9.0 installed on a PC connected to the control network
Assigning a Primary IP Address to ENET 1 on each Controller
Each device must have a valid IP address and subnet mask so that it can communicate on the
network. If your controllers already have valid primary IP addresses, you can skip to the next section,
“Assigning an IP Address to the Arbiter” on page
When you start a SNAP PAC S-series controller that does not have an IP address, it starts in BootP
mode, which means it sends out a BootP broadcast requesting an IP address. This is indicated by a
quickly blinking status light.
You respond to the BootP broadcast by using the PAC Redundancy Manager or PAC Manager to
assign a
static
IP address and subnet mask. If the network you're using has a Dynamic Host
Configuration Protocol (DHCP) server, either assign a static IP address before connecting the device
to the network (preferred), or disable the server. (These servers may respond to BootP requests and
assign a dynamic address.)