Description

The FCP270 flattens and simplifies the I/A Series architecture. The I/A Series architecture only requires field enclosures plus workstations and Ethernet switches. For more information on The MESH control network architecture, refer to PSS 21H-7C2 B3.
The field-mounted FCP270 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.
The FCP270 is packaged in a rugged, die cast aluminum housing that does not require venting due to its efficient design. The FCP270 is CE certified, and it can be mounted without expensive special cabinets to prevent electronic emissions. The FCP270 can be mounted in Class G3 harsh environments.
ENHANCED RELIABILITY (FAULTTOLERANCE)The unique and patented fault-tolerant operation of the FCP270 greatly improves reliability relative to other process controllers. The fault-tolerant version of the FCP270 consists of two modules operating in parallel, with two Ethernet connections to The MESH control network. The two FCP270 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 controller when both controllers 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.
This fault-tolerant solution has the following major advantages over controllers that are merely redundant: No bad messages are sent to the field or to applications using controller data because no message is allowed out of the controller unless both modules match bit for bit on the message being sent.