FOXBORO FCP280 Process Automation System

FOXBORO FCP280  Process Automation  System

DESCRIPTION

The Field Control Processor 280 is a distributed, optionally fault-tolerant, field-mounted controller that  performs process control and alarming functions according to a user-defined control strategy.

The FCP280 requires Foxboro Evo Control Core  Services v9.0 or later. A system with the FCP280 and  this software is called a Foxboro Evo Process  Automation System.

FEATURES 

 Performs regulatory, logic, timing, and sequential  control together with connected Fieldbus  Modules (FBMs) 

 Performs data acquisition and alarm detection  and notification 

 Supports up to 128 Compact or standard  200 Series FBMs, or up to 128 of a combination  of 100 Series FBMs and 200 Series FBMs (with  no more than 64 100 Series FBMs in this  configuration) No Fieldbus Communication Module is required. 

 No Fieldbus Expansion Module is required for  Expanded fieldbus support.

 Supports self-hosting mode, which allows the  FCP280 to boot itself with a valid control  database even without its host workstation 

 Offers unique, patented, fault-tolerant operation  using two control modules to greatly improve  reliability relative to other process controllers 

 Offers on-line image upgrade (OLUG) of a faulttolerant FCP280 without shutting down the  process 

 Liquid Crystal Display (LCD) displays letterbug  and real-time roles and statuses 

 Connects to The Mesh control network via  standard fiber optic or copper 100 Mbps  Ethernet cables

 Uses a rugged, die cast aluminum housing for  mounting in a non-vented field enclosure 

 Can operate in Class G3 harsh environments 

 CE certified for field mounting in enclosures 

 Each Fieldbus port on FCP280 baseplates  supports either a 2 Mbps or 268 Kbps HDLC  fieldbus exclusively 

 Uses versatile control algorithms and a wide  variety of FBMs to provide control capabilities for  a broad range of process applications 

 Supports time synchronization using optional  external time from GPS satellites 

 Uses soft letterbugs configurable via the keys on  the FCP280 faceplate.

FIBER AND COPPER NETWORK ADAPTERS

FCP280 modules connect to a pair of fiber or copper  adapters (see Figure 4) which each connect to one  Ethernet switch in The Mesh control network. The  FCP280 baseplate passes inbound traffic from either  of the two switches to both FCP280s, and pass  outbound traffic from the primary FCP280 module to  either switch.

REMOTE MOUNTING

The FCP280 simplifies the Foxboro Evo Process  Automation System architecture, maintaining control  while only requiring housing (via field enclosures),  host workstations with Foxboro Evo Control Core  Services v9.0 or later, and Ethernet switches for  communication via The Mesh control network  architecture, described in PSS 21H-7C2 B3.

The field-mounted FCP280 is an integral part of the  highly-distributed control network where controllers  are closely aligned to specific process units mounted  in close proximity to their I/O and the actual  equipment being controlled. Coordination between  process units takes place via a fiber optic 100 Mbps  Ethernet network.

ENHANCED RELIABILITY (FAULTTOLERANCE)

The unique and patented fault-tolerant operation of  the FCP280 improves reliability relative to legacy  process controllers. The fault-tolerant version of the  FCP280 consists of two modules operating in  parallel, with two Ethernet connections to The Mesh  control network. The two FCP280 modules, married  together as a fault-tolerant pair, provide continuous  operation of the controller in the event of virtually any  hardware failure occurring within one module of the  pair.

Both modules receive and process information  simultaneously, and faults are detected by the  modules themselves. One of the significant methods  of fault detection is comparison of communication  messages at the module external interfaces.  Messages only leave the FCP280 when both  FCP280s agree on the message being sent (bit for  bit match). Upon detection of a fault, self-diagnostics  are run by both modules to determine which module  is defective. The non-defective module then assumes  control without affecting normal system operations.