USING CONTROLLER REDUNDANCY – DEBUG OPTIONS
SNAP PAC Redundancy Option User’s Guide
60
Using Controller Redundancy – Debug Options
With a control engine associated with your strategy and configured for redundant controllers (see
“Step 2. Adding a Redundant Control Engine to a PAC Control Strategy” on page
), PAC Control will
automatically select which controller to use for downloading and debugging. While in this
automatic mode, PAC Control downloads to the non-active controller whenever possible so that the
active controller can keep running during the download.
In order to handle a variety of download and debug scenarios, PAC Control also provides other
debug options.
To access the debug options:
1.
Make sure you have turned on the redundancy options in PAC Control. For more information,
see
“Step 1. Enabling the PAC Control Redundancy Features” on page
2.
Right-click the control engine you configured previously for controller redundancy, and select
Controller Redundancy – Debug Options to see the available options.
3.
Choose one of the following settings.
Automatic Controller Selection
: This setting is selected by default because it is the least
disruptive to your system. It should be used when you have connected and configured an
arbiter and at least one controller. With this setting PAC Control will select which controller to
use for downloading and debugging. If possible, it downloads to the non-active controller, so
that the active controller can keep running during the download.
Use Controller 1 (or 2) with Arbiter
: Use this option when there is an arbiter connected and
you want to download to or debug a specific controller during development or
troubleshooting. Possible scenarios for using this option include demonstrating the control
system, diagnosing a problem, network sniffing, and so on. When using this option, the arbiter
manages the other controller by turning it off during the download.
Use Controller 1 (or 2) without Arbiter
: You can use this option when there is there is no
arbiter connected and you want to download to or debug a specific controller during
development or troubleshooting. In this case, you must make sure that the other controller is
turned off
. One possible use of this option is in a deployed system where the arbiter is not
working.
CAUTION: In order to avoid having two active controllers at the same time or unpredictable behavior
from your system, make sure that the other controller is off.
Debug Backup Controller
: Use this option only if you want to debug the current qualified
backup controller. No downloads are allowed.