HC900 Controller Redundant Overview
HC900 Controller Redundant Overview
Warranty/Remedy
Honeywell warrants goods of its manufacture as being free of defective materials and faulty workmanship. Contact
your local sales office for warranty information. If warranted goods are returned to Honeywell during the period of
coverage, Honeywell will repair or replace without charge those items it finds defective. The foregoing is Buyer's sole
remedy and is in lieu of all other warranties, expressed or implied, including those of merchantability and fitness for a
particular purpose. Specifications may change without notice. The information we supply is believed to be accurate
and reliable as of this printing. However, we assume no responsibility for its use.
While we provide application assistance personally, through our literature and the Honeywell web site, it is up to the
customer to determine the suitability of the product in the application.
Abstract
This manual gives an overview of the HC900 Redundancy architecture and products.
References
The following list identifies all documents that may be sources of reference material for topics discussed in this
publication.
Corporate http://www.honeywell.com
Telephone
Contact us by telephone at the numbers listed below.
Symbol Definition
WARNING
PERSONAL INJURY: Risk of electrical shock. This symbol warns the user of a
potential shock hazard where HAZARDOUS LIVE voltages greater than 30 Vrms,
42.4 Vpeak, or 60 Vdc may be accessible. Failure to comply with these
instructions could result in death or serious injury.
Protective Earth (PE) terminal. Provided for connection of the protective earth
(green or green/yellow) supply system conductor.
Functional earth terminal. Used for non-safety purposes such as noise immunity
improvement. NOTE: This connection shall be bonded to protective earth at the
source of supply in accordance with national local electrical code requirements.
Earth Ground. Functional earth connection. NOTE: This connection shall be bonded
to Protective earth at the source of supply in accordance with national and local
electrical code requirements.
Introduction ............................................................................................. 1
Overview.......................................................................................................................1
Purpose of this document.......................................................................................................1
What’s in this document .........................................................................................................1
Documentation .............................................................................................................1
Networking .............................................................................................. 7
System Network ...........................................................................................................7
System Network Supervisory Functions.......................................................................8
To PC Applications.................................................................................................................8
To Peer HC900 Controllers ....................................................................................................9
Connection options ................................................................................................................9
I/O Network to Remote Racks....................................................................................10
Device Network (Serial)..............................................................................................11
Modbus Master ....................................................................................................................11
Modbus Slave ......................................................................................................................11
Modbus Master and/or Slave ...............................................................................................11
Remote Access ..........................................................................................................11
Configuration......................................................................................... 12
Lead Controller configuration .....................................................................................12
Configuration & Setup Parameters for Redundant Controllers.............................................12
Reserve Controller configuration................................................................................12
Software .....................................................................................................................13
Operation .............................................................................................. 15
Overview.....................................................................................................................15
Start-Up ......................................................................................................................15
Modes of operation.....................................................................................................15
RUN Mode (Locked) ............................................................................................................16
RUN/PROGRAM Mode (Unlocked)......................................................................................16
PROGRAM Mode (Locked)..................................................................................................16
Steady State Operations ............................................................................................16
Execution time......................................................................................................................17
Execution sequence.............................................................................................................17
Lead/Reserve controller synchronization .............................................................................17
Failover.......................................................................................................................18
Automatic Failover ...............................................................................................................18
Manual Failover....................................................................................................................19
Failover Performance ...........................................................................................................19
Redundancy Diagnostic Monitoring......................................................................................19
Installation ............................................................................................. 20
Installing the Redundant Controller Rack...................................................................20
Installing the I/O Racks...............................................................................................20
Installing Networking Equipment ................................................................................21
I/O Network ..........................................................................................................................21
Supervisory / Peer Network..................................................................................................21
Installing a Panel-Mounted Operator Interface ..........................................................21
Honeywell OI-1042 & OI-559 ...............................................................................................21
3rd Party Panel-Mounted OI.................................................................................................21
Installing PC Hosts .....................................................................................................22
Honeywell HC Designer & HC Utilities Software ..................................................................22
Honeywell Vista Software.....................................................................................................22
3rd Party PC Application Software .......................................................................................22
Troubleshooting .................................................................................... 23
Diagnostic Indicators ..................................................................................................23
Diagnostic Monitoring from HC Designer and HC Utilities PC Software....................23
Status data available via Supervisory PC ..................................................................23
Servicing.....................................................................................................................24
Module Replacement ...........................................................................................................24
C70R Module Replacement .................................................................................................24
Redundancy Switch Module Replacement...........................................................................24
Introduction
Overview
Purpose of this document
Provide an overview of the Redundant HC900 product.
Topic Page
Product Architecture 2
Key Components 3
Networking 7
Configuration 12
Operation 15
Installation 20
Troubleshooting 23
Documentation
See References on page iii.
The HC900 Controller with redundancy minimizes the impact on a process resulting from a single failure
of a critical component of the control system. Availability is improved with:
• Redundant Controller Processors - Provides redundant controllers with seamless failover under fault
conditions,
• Independent power supplies for each of the Redundant Controllers,
• Redundant host networks - Provides interfaces to survive a single network failure,
• Redundant I/O Power – Provides redundant power for I/O racks on a per rack basis.
Product architecture
The Redundant HC900 controller uses a separate rack for controller processors mounted separately from
I/O Racks
Redundant
Controller
1042, 559 or 3rd
Party
Rack
Operator Interface Ethernet
Switch A
Redundant
Power
B 100 base-T
I/O Racks
Key components
Lead
RS232/RS485
Reserve
Serial Ports 1 & 2
Run/ Run
Pgm
Pgm . .Fail-
E2 E2
I/O Port
I/O I/O
• Holds two redundant C70R CPUs, two power supplies, and one Redundancy Switch Module (RSM).
• Contains the back-plane for C70R-to-C70R communications, power, and interface to RSM.
• The C70R Controller Rack does not support any I/O Modules; I/O Modules are read from and written to
directly from a Scanner2 CPU.
• Cannot be used with C30 or C50 CPU’s.
CPU
• Requires Scanner2 module(s)
• Reads inputs from I/O Racks through Scanner2 modules
• Executes control strategy (5000 function blocks)
• Writes outputs to I/O Racks through Scanner2 modules
• Dual Ethernet communication ports to host systems
• Each C70R Controller CPU has a dedicated, single Ethernet communication port to I/O racks
• Two serial ports – each is RS-232 or 485 configurable; Modbus or ELN protocols for interface to OI,
Modbus Host, or Modbus Slaves
• Lead Controller CPU – writes to the physical outputs; serves as the single external interface to other
devices and systems (i.e., responds to requests from PC Hosts, a local Operator Interface, communicates
to HC900 peers, and polls network slave devices)
• Reserve Controller CPU – executes control strategy in sync with Lead but does not write to physical
outputs; does not respond to Hosts or OI.
• Reserve Controller CPU receives configuration updates and run-time data (operator entries, supervisory
changes) from the Lead CPU with no manual user interaction. Configuration changes to a Reserve CPU
are not permitted, except through the Lead CPU where both CPUs receive the change.
• The C70R is not recommended for non-redundant applications.
Power
• Each C70R CPU has a dedicated Power Supply (two in the controller rack). Failure of the Lead CPU
power supply will cause a failover condition.
• The same power supply model(s) are used for the controller rack and the I/O racks.
• The same power supply models(s) are used for the redundant and non-redundant systems.
I/O Modules
• The full complement of HC900 Analog and Digital I/O modules are available for use in I/O racks using
the Scanner2 module connected to redundant C70R Controller CPU’s.
• Requires Digital I/O modules with model numbers 900xxx-0102 or later with enhanced I/O back-plane
performance and shield modification.
• Requires Analog Input modules 900A01-0102 or later with shield modifications.
• Requires Analog Output modules 900B01-0101 or later with shield modifications.
• Any module may be inserted into any rack slot location.
• Redundant I/O modules are not supported in the HC900 system.
Networking
System Network
Each C70R CPU provides two 10/100base T Ethernet Host ports with Modbus TCP protocol. A total of 10
sockets are available and are shared by the two ports of the CPU for host device interfacing. Either port
may be used in a non-redundant connection for host systems that do not support redundant network
communications.
• Requires Honeywell (PN 50008930-001) or commercially available industrial switches, routers, etc for
10/100-baseT connection to the host/peer network. See Figure 3.
• Supports single or dual network interface to PC Hosts.
• Supports single or dual network interface to peer HC900 Redundant Controllers.
• Supports single network interface to peer HC900 Non-Redundant Controllers or other Modbus/TCP
devices.
• Network changes such as setting IP addresses must be made with the controller in the Program mode.
See Modes of operation on page 15.
• Maximum distance of system network (per 10/100 baseT specification, 100 meters per segment).
Ethernet
Switch
10/100 base-T
RS-485
A
Twisted Pair B
100 base-T
Up to 100m
For applications where the host supports redundant networks, two separate Ethernet switches are required,
one for each port of the CPUs. See Figure 4.
RS-485
A
Twisted Pair B
100 base-T
Up to 100m
In this configuration a second communication path is available between the Host and the controller in the
event of a switching hub or connection failure.
Connection options
To Host
Ethernet
Switch
To Host Ethernet
Switch
Non-Redundant Controller
Redundant Controller
To Host
Ethernet
Switch
A A
B B
100 base-T 100 base-T
Up to 100m Up to 100m
Modbus Slave
• The two serial ports of the C70R CPU may each be set to RS 485 or RS 232 and Modbus slave
operation.
• Supports data exchange with an external Modbus master such as a local operator panel or PC
application.
• Port connections to redundant C70R CPUs should be made to both CPUs in the rack.
• Uses same local Modbus unit address for both RS 485 serial ports of the two C70R CPUs.
• A modem configuration selection extends the 3-character timeout limit of Modbus protocol for remote
access.
Remote Access
• Requires an external modem.
• Available with HC Designer software.
• Lead Controller provides communications.
Configuration
Lead
Reserve
To PC
Software
HC Designer & HC Utilities PC Software
• Redundant configurations require version 3.0 or later of the Designer and Utilities Software
− The version number of the software should be equal to or greater than the version number of the
controller CPU being configured.
• The same software is used to configure both redundant and non-redundant HC900 controllers.
• Supports forward migration of existing C30 and C50 configurations to the C70R.
• Software Version 3.xx or later may be used to create or modify configurations for earlier controller
versions.
Configuration storage
• Controller configurations downloaded to the controller are stored in battery backed RAM memory and
non-volatile Flash memory.
− The controller CPU executes its program from RAM memory. The battery backed RAM memory
also stores the controller dynamic status during a loss of power to allow graceful resumption of
controller operation following the interruption. If the battery is not available, startup following a
power loss will use the configuration stored in Flash memory.
Configuration edits
• On-line edits to the configuration may be downloaded to the controller.
− On-line edits made to C70R CPU configurations are stored in both RAM and Flash memory.
− HC Designer software lets you monitor the controller’s live configuration to verify edits. All edits are
made to the configuration of the Lead controller. The Reserve controller’s configuration is
automatically updated following a change to the Lead controller’s configuration.
Configuration backup
• Controller configurations may be uploaded and saved as Backup Files.
− Backup files contain all of the information needed to restore a CPU to the operating conditions at the
time the backup file was created, eliminating the need to for separate manual entries.
− Useful facility to quickly get a controller back on-line following CPU replacement.
− Backup configuration files use file extension .cbk.
Configuration conversion
• Configurations built for use with C30 and C50 CPUs may be downloaded into C70 CPUs following a
file conversion performed using HC Designer software, version 3.xx or later.
− To convert a C30 or C50 configuration files for used with C70R CPUs, open the files to be converted
using HC Designer and perform a “Save As” operation and select a C70R file type.
Monitoring configurations
• Monitoring the configuration of the Lead Controller may be performed using Hybrid Control Designer
software.
• Controller connection via Ethernet or serial.
• When Ethernet is used, HC Designer consumes one network socket.
• While in the monitor mode, viewing the function block diagram allows the user to view the input and
output values for each function block.
• Watch windows allow viewing data by parameter type and in a user specified group.
• System Monitor (ASYS) function blocks provide an output to indicate the Reserve status of the CPU.
• Redundant controller status may be monitored from HC Designer.
• A redundancy icon is provided to allow access to information in the monitor menu.
• Selections under the Utilities Tab allow users to view diagnostic status and perform maintenance level
activities.
Operation
Overview
In a redundant HC900 system, the Lead Controller performs all primary tasks including interfacing with
remote I/O racks, communicating with a local HMI, exchanging data with peer controllers, interfacing with
Modbus slave devices, and communicating with a Host PC application. Detection of a fault or removing
power from a Reserve Controller will initiate a diagnostic prompt in the Lead Controller, but will have no
impact on the process under control. The detection of a fault or removing power from a Lead Controller
will initiate failover, that is, transfer all primary tasks to the Reserve Controller, establishing this controller
as the new Lead. Following a failover, the new Lead Controller will remain the Lead, even if the condition
that caused the failover is corrected.
Start-Up
• Assignment of Lead and Reserve status is determined at start-up
− First available C70R assumes Lead
− In case of a tie, CPU mounted in the left position of the rack will Lead
− No user configuration or manual operations required to establish Lead / Reserve status
• Lead Controller assumes control of I/O and all external communication interfaces.
• Reserve Controller receives the configuration from the Lead Controller
Modes of operation
The modes of operation are:
• Run
• Run/Program
• Program
You can change modes with:
• key-switch on the redundancy control module
• HC Designer software
• HC Utilities software
• local 1042 or 449 operator interfaces.
• a command from a supervisory host
Both Lead and Reserve Controllers maintain the same mode. Placing the Lead Controller into the Program
mode will also place the Reserve Controller in the Program mode.
Reserve
Run/ Run
Pgm
Redundancy Fail-
Pgm Over
Switch
Module E1
(RSM)
E2
I/O
Execution time
HC900 Controllers are designed to execute control functions within fixed scan cycles for analog data types
and logic data types. In redundant controllers, the minimum scan time is 533ms for analog data types and
53ms for logic data types; scan time varies depending on configuration.
Execution sequence
• The type of control functions executed during a scan is determined by the system configuration.
− Controller configurations contain a series of algorithms in the form of function blocks that get
executed in a fixed sequence. The first 100 function blocks are pre-assigned by the system to handle
communication tasks, alarm processing, system monitoring functions, etc. and cannot be changed by
the user. Starting with function block number 101, the user may select the type of function to be
executed.
• The sequence of function block execution is initially determined by the sequence in which the function
blocks are placed on the graphic diagram in HC Designer.
− Final desired sequence must be set by the user to achieve proper and optimum performance.
− Incorrect execution sequences can contribute to delays in processing outputs and/or improper or
unexpected operation.
• The HC900 controller samples all inputs before the start of a controller scan.
− Each input being used in the configuration must be assigned to a function block. The sequence order
of the function block determines when in time the actual value will be updated. It is important that
algorithms that need updated input values for their calculations have the inputs execute first in the
sequence.
• Except for Time Proportioning Output (TPO), Three-Position-Step-Control (TPSC) and Position
Proportional Output (PPO) function block types that update their physical output values while the
function blocks are being executed, all physical outputs are updated at the end of a scan.
SYNC SYNC
Write Outputs
Communications
Failover
Automatic Failover
• Triggered on any of the following conditions of the Lead Controller:
− Loss of communications with I/O Rack(s)
− Processor exception conditions
• Error conditions that occur in the following areas will not cause a failover:
− Loss of communications to a Host on a network
− Loss of communications to Modbus Slave devices
− Loss of communications to Operator Interface
− Loss of communications with a Peer controller
• During the transition from the Lead to the Reserve, analog and digital output status is maintained at the
I/O racks.
Manual Failover
• Via Key Switch on the Redundancy Switch Module in the Redundant Controller Rack
• Via Software Command from HC Designer & HC Utilities PC Software
• Via Software Command from Modbus / TCP & Serial Modbus RTU Hosts
• Via Software Command from OI-1042 & OI-559 Operator Interfaces
Failover Performance
Failure condition detection and failover from Lead to Reserve CPU executed in 4 analog control cycles or
less.
Installation
Installing PC Hosts
Honeywell HC Designer & HC Utilities Software
• Operating Systems supported: Windows 2000, NT, XP Professional
• PC hardware requirements:
− Pentium 200 MHz with 64 MB of RAM
− Screen resolution – SVGA (1024x768 recommended)
− CD ROM drive (for loading software)
• Connects to the C70R Controllers using Ethernet, RS-232, Modbus RTU, or Modem
• Available on CD
Troubleshooting
Diagnostic Indicators
• LEDs on the front of each module are provided to indicate the module’s health. These include:
− C70R Controller Status LEDs
− Scanner2 Status LEDs
− I/O Module Status LEDs
• The HC900 modules use a combination of color and flashing patterns to indicate fault conditions and the
type of fault detected. See the HC900 controller manual for a detailed explanation of fault conditions.
• LEDs on the front of the Redundancy Switch Module indicate the Lead/Reserve status of the two
redundant C70R Controllers
− Reserve indicator will flash while Reserve CPU is being updated by Lead.
− Reserve controller is not available during this period.
• LEDs on the front of the Power Status Module indicate the status of the redundant Power Supplies for an
I/O Rack
− ON if the power supply if functioning properly
− Off if either the 5 volt or the 24 volt source of a power supply has a fault.
Servicing
Module Replacement
• Servicing a failed module is accomplished by replacing only that module