Honeywell HC900 Manual Do Utilizador
Components and Architecture - Ethernet Devices/Considerations
14
HC900 Hybrid Controller Installation and User Guide
Revision 5
9/03
The Ethernet Hubs used in the I/O expansion network (C50 CPU only)are available from Honeywell.
I/O implementation requirements include:
•
Constructing a configuration file, and loading it into the Controller Module. This file includes I/O
numbering assignments for each I/O Function Block regarding Rack Number, Module Number ("slot"
number, or position in the rack, starting from the left), and Channel Number.
numbering assignments for each I/O Function Block regarding Rack Number, Module Number ("slot"
number, or position in the rack, starting from the left), and Channel Number.
•
Physically assigning Rack Numbers, by positioning jumpers in the Scanner Module for each rack.
•
Placing the appropriate module type in each slot in each rack.
The I/O expansion network uses Honeywell private protocol that optimizes I/O performance and security.
The configuration and operation of the I/O expansion network is automatic, it is entirely under control of
built-in private software that resides in the Controller Module and in each Scanner Module included in the
HC900 system. The controller examines the control strategy stored in its memory, verifies that the physical
configuration (Rack Numbers, and I/O Module type- by Module Number) matches the stored control
strategy, and establishes communication with each of the I/O modules in each of the I/O racks.
built-in private software that resides in the Controller Module and in each Scanner Module included in the
HC900 system. The controller examines the control strategy stored in its memory, verifies that the physical
configuration (Rack Numbers, and I/O Module type- by Module Number) matches the stored control
strategy, and establishes communication with each of the I/O modules in each of the I/O racks.
Ethernet Open Connectivity Network
The configuration of the Ethernet Open Connectivity Network varies with specific applications in purpose
and in complexity. In some applications, configuration is straightforward and within the capabilities of
experienced installation technicians. In other applications (for example, those that include inter-connection
to other networks such as Intranet and Internet), a working knowledge of networking is required.
and in complexity. In some applications, configuration is straightforward and within the capabilities of
experienced installation technicians. In other applications (for example, those that include inter-connection
to other networks such as Intranet and Internet), a working knowledge of networking is required.
The Ethernet Open Connectivity Network for a given HC900 Controller enables:
• Peer-to-peer communication with up to eight other HC900 Controllers
• Connection to up to five PC hosts (for example, PCs that include HMI supervisory software and/or
Hybrid Control Designer configuration software)
• Inter-connection to other networks (such as for sending Alarm/Event messages via e-mail.)
Communications lockout is possible in high network traffic conditions.
When inter-connecting your HC900 controller sub-net to a plant network where there may be significant
network traffic not directed to the HC900 controllers or to related supervisory control or data acquisition
software interfaces, we highly recommend you use a router to protect the controller from this extraneous
traffic.
Failure to do so could, in high traffic cases, result in communications lockout requiring the
controller to be power-cycled. See Figure 59 on page 178 for an example of an installation for a typical
interface to another network sub-net.
When inter-connecting your HC900 controller sub-net to a plant network where there may be significant
network traffic not directed to the HC900 controllers or to related supervisory control or data acquisition
software interfaces, we highly recommend you use a router to protect the controller from this extraneous
traffic.
Failure to do so could, in high traffic cases, result in communications lockout requiring the
controller to be power-cycled. See Figure 59 on page 178 for an example of an installation for a typical
interface to another network sub-net.
Peer-to-Peer Communication
Peer-to-peer communication enables any given HC900 Controller to exchange signal and variable data with
up to eight other HC900 Controllers. Peer-to-peer communication uses the Ethernet Open Connectivity
network and employs standard User Datagram Protocol (UDP) for fast and efficient transfer of information.
Peer-to-peer communication is based on fail-safe and data expiration mechanisms that provide for fault and
loading considerations without requiring reserved network bandwidth allocation. Peer-to-peer is designed
to be easy to configure as part of a device's standard configuration and does not require the distribution of a
global database.
up to eight other HC900 Controllers. Peer-to-peer communication uses the Ethernet Open Connectivity
network and employs standard User Datagram Protocol (UDP) for fast and efficient transfer of information.
Peer-to-peer communication is based on fail-safe and data expiration mechanisms that provide for fault and
loading considerations without requiring reserved network bandwidth allocation. Peer-to-peer is designed
to be easy to configure as part of a device's standard configuration and does not require the distribution of a
global database.