GEH-6721 Vol I PDF

GEH-6721Y
Mark* VIe Control, Volume I

System Guide
GE Proprietary and Internal (Class II) – This document contains proprietary information of GE and is intended for internal use only. It may not be used,
shown, reproduced, or disclosed outside of GE without the express written consent of GE.
These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible
contingency to be met during installation, operation, and maintenance. The information is supplied for informational
purposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications,
and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflected
herein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or to
the document itself at any time. This document is intended for trained personnel familiar with the GE products referenced
herein.
GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this
document does not provide any license whatsoever to any of these patents.
GE provides the following document and the information included therein as is and without warranty of any kind, expressed
or implied, including but not limited to any implied statutory warranty of merchantability or fitness for particular purpose.
For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE Sales
Representative.
Revised: Jan 2014

Issued: 2004-01-20
© 2004 - 2014 General Electric Company, All rights reserved.

___________________________________
* Indicates a trademark of General Electric Company and/or its subsidiaries.
All other trademarks are the property of their respective owners.
We would appreciate your feedback about our documentation.

Please send comments or suggestions to [email protected]
Document Updates
Location Description
Chapter, Control System Overview Section I/O Types, correction to table, Turbine Specific I/O
Section Power Distribution, correction to controller power sources
Chapter, Controllers & Switches Moved to GEH-6721_Vol_II
Chapter, Networks Reorganized and reworded for clarity. Updated information on UDH devices and
third-party interfaces.
Chapter, Communication Protocols Reorganized and new sections: PROFIBUS, OPC, and CANopen
Chapter, Technical Regulations, Updates to the following sections: Safety Standards, Electrical, Elevation
Standards, and Environments New section: Conditions for Compliance
Deleted sections: Clearances, Printed Circuit Board Assemblies
Updated section, Temperature of Components: added DACA to restrictive table
Chapter, Installation Guidelines Updates to the sections: Power Requirements, Equipment Grounding, and Cable
Specifications, and the figure Circuit Diagram
Chapter, Software Tools Reorganized tools sections, and updated some descriptions
Chapter, Maintenance & Moved to GEH-6721_Vol_II

Replacement
GE Proprietary and Internal (Class II) – This document contains proprietary information of GE and is intended for internal use only. It may not be
used, shown, reproduced, or disclosed outside of GE without the express written consent of GE.
Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not

strictly observed, could result in personal injury or death.
Warning
Indicates a procedure, condition, or statement that, if not

strictly observed, could result in damage to or destruction of
equipment.
Caution
Indicates a procedure, condition, or statement that should be

strictly followed to improve these applications.
Attention
GEH-6721Y System Guide 3

To prevent personal injury or damage to equipment, follow all
equipment safety procedures, Lockout Tagout (LOTO), and site
safety procedures as indicated by Employee Health and Safety
(EHS) guidelines.
Warning
This equipment contains a potential hazard of electric shock,

burn, or death. Only personnel who are adequately trained and
thoroughly familiar with the equipment and the instructions
should install, operate, or maintain this equipment.
Warning
Isolation of test equipment from the equipment under test

presents potential electrical hazards. If the test equipment
cannot be grounded to the equipment under test, the test
equipment’s case must be shielded to prevent contact by
personnel.
Warning To minimize hazard of electrical shock or burn, approved

grounding practices and procedures must be strictly followed.
To prevent personal injury or equipment damage caused by

equipment malfunction, only adequately trained personnel
should modify any programmable machine.
Warning
Always ensure that applicable standards and regulations are

followed and only properly certified equipment is used as a
critical component of a safety system. Never assume that the
Human-machine Interface (HMI) or the operator will close a
Warning safety critical control loop.
4 GEH-6721Y Mark VIe Control, Volume I System Guide

Contents
1 Introduction ....................................................................................................................................... 7
1.1 Related Documents ..................................................................................................................................8
1.2 Acronyms and Abbreviations .....................................................................................................................9
2 Control System Overview............................................................................................................. 11
2.1 Controllers ........................................................................................................................................... 11
2.2 IONet Switches ..................................................................................................................................... 13
2.3 Distributed I/O Modules.......................................................................................................................... 14
2.4 Power Distribution................................................................................................................................. 26
2.5 Redundancy Options .............................................................................................................................. 27
2.6 Reliability and Availability ...................................................................................................................... 41
3 Network Layers ............................................................................................................................... 51
3.1 Plant Data Highway (PDH)...................................................................................................................... 54
3.2 Unit Data Highway (UDH) ...................................................................................................................... 56
3.3 UDH Devices........................................................................................................................................ 60
3.4 IONet .................................................................................................................................................. 62
3.5 External communication links .................................................................................................................. 68
4 Communication Protocols ........................................................................................................... 69
4.1 Ethernet GSM ....................................................................................................................................... 69
4.2 OPC.................................................................................................................................................... 70
4.3 Modbus ............................................................................................................................................... 71
4.4 Ethernet Global Data (EGD) .................................................................................................................... 72
4.5 Network Time Protocol (NTP) ................................................................................................................. 74
4.6 FOUNDATION Fieldbus ........................................................................................................................ 80
4.7 PROFIBUS .......................................................................................................................................... 81
4.8 CANopen............................................................................................................................................. 81
5 Technical Regulations, Standards, and Environment .......................................................... 83
5.1 Safety Standards.................................................................................................................................... 83
5.2 Conditions for Compliance ...................................................................................................................... 84
5.3 Electrical.............................................................................................................................................. 85
5.4 Environment ......................................................................................................................................... 87
6 Installation Guidelines .................................................................................................................. 95
6.1 Installation Support ................................................................................................................................ 95
6.2 Equipment Receiving and Handling .......................................................................................................... 98
6.3 Power Requirements .............................................................................................................................100
6.4 Installation Support Drawings .................................................................................................................102
6.5 Grounding ...........................................................................................................................................107
6.6 Cable Separation and Routing .................................................................................................................116
6.7 Fiber-optic Cabling ...............................................................................................................................122
6.8 Cable Specifications..............................................................................................................................131
GEH-6721Y System Guide 5

6.9 Connecting the System ..........................................................................................................................136
6.10 Startup Checks .....................................................................................................................................137
7 Software Tools ..............................................................................................................................139
7.1 ToolboxST Application ..........................................................................................................................139
7.2 WorkstationST Application .....................................................................................................................140
7.3 Human-machine Interface (HMI) .............................................................................................................141
7.4 PI-based or Proficy-based Historian .........................................................................................................143
7.5 Trender Tools for Process Data (Trends)....................................................................................................147
7.6 uOSM ................................................................................................................................................147
Glossary of Terms ..............................................................................................................................149
Index.......................................................................................................................................................153

1 Introduction
The ControlST* software suite The Mark VIe control was designed to serve a wide variety of control and protection
is used with Mark VIe controls applications from steam and gas turbines to power generation balance of plant (BoP)
and related systems for equipment. The control system primarily consists of three hardware components: the
programming, configuration, controllers, I/O network (IONet) switches, and I/O modules. The Mark VIe control
trending, and analyzing provides more options for redundancy, better maintainability, and greater capability for
diagnostics. locating I/O modules closer to the controlled equipment. It provides quality,
time-coherent data at controller and plant level for effectively managing control system
equipment.
Triple Redundant Mark VIe Control System
Introduction GEH-6721Y System Guide 7

1.1 Related Documents
GEH-6722 Mark VIeS Safety Control System Guide
GEH-6723 Mark VIeS Safety Control Safety Instruction Guide
GEH-6700 ToolboxST* User Guide for Mark VIe Control

GEH-6721_Vol_II Mark VIe Control Volume II System Hardware Guide
GEH-6721_Vol_III Mark VIe Control Volume III Diagnostics and Troubleshooting
GEH-6800 Mark VIe Control Migration from Mark V Control & Mark V LM Control System Guide
GEH-6744 PI®-based Historian with ControlST Software Suite

GEH-6745 Proficy*-based Historian with ControlST Software Suite
GEH-6705 ToolboxST User Guide for Mark VIeS Safety Control
GEH-6724 Mark VIe Control Initial Startup Instruction Guide
GEH-6741 Sequential Function Chart Application Guide
GEH-6742 Mark VIe Virtual Controller User Guide

GEH-6743 Mark VIe Control Simulink Translator Tool User Guide
GEH-6757 WorkstationST* GSM 3.0 User Guide
GEH-6760 WorkstationST GSM 3.0 Application Guide
GEH-6761 Mark VIe Control FOUNDATION Fieldbus™ Interface Application Guide
GEH-6762 Mark VIe Control FOUNDATION Fieldbus™ Interface User Guide

GEH-6763 Mark VIe Control PSCH Specialized Serial Communication Module Instruction Guide
GEH-6779 Mark VIe Control Renewable Energy Distributed I/O Modules
GEH-6808 ControlST Software Suite How-to Guides

GEH-6812 Mark Controllers Shared IONet User Guide
GEI-100679 Mark VIe Distributed Control System (DCS) Block Library
GEI-100682 Mark VIe Control Standard Block Library
GEI-100681 Mark VIe Control Legacy Block Library
GEI-100680 Mark VIe Control Turbine Block Library
GEI-100709 Mark VIe Control PPROS1B and PPRAS1x Functional Safety Instruction Guide
GEI-100721 Programmable Logic Controllers with the Mark VIe DCS
GEI-100795 Trender for the ToolboxST Application Instruction Guide
GEI-100620 WorkstationST Alarm Viewer Instruction Guide

1.2 Acronyms and Abbreviations
ASCII America Standard Code for Information Interchange
ASK Automatic Station Keeping
AWG American Wire Gauge
BoP Balance of Plant

BOP Blowout Protector
CDH Control Data Highway
CMOS Complementary Metal-Oxide Semiconductor
COI Computer Operator Interface
CPCI CompactPCI 6U high enclosure
CRC Cyclic Redundancy Code/Check
DAC Digital-to-Analog Converter
DCE Data Communication Equipment
DCS Distributed Control System
DHCP Dynamic Host Configuration Protocol
DRAM Dynamic Random Access Memory
DTE Data Terminal Equipment device
EGD Ethernet Global Data

EMC Electromagnetic Capability
EMI Electromagnetic Interference
ERA Electrical Riser Angle
FE Functional Earth
FTD Flow Totalizer Display (OTEK)
FTI Flow Totalizer Input (XMT868i Panametrics Ultrasonic Flow Transmitter)
GPS Global Position System
GSM GE Standard Messaging
GTS Global Time Source

HMI Human-machine Interface
HRSG Heat Recovery Steam Generator
IEC International Electrotechnical Commission

IEEE Institute of Electrical and Electronics Engineers
KP Keyphasor*
LAN Local Area Network

MPU Magnetic Pickup
MTBF Mean Time Between Failures

MTBFO Mean Time Between Forced Outage
MTTR Mean Time To Repair
NEMA® National Electrical Manufacturer’s Association
Introduction GEH-6721Y System Guide 9

NFPA National Fire Protection Association
NTP Network Time Protocol
NVRAM Non-volatile Random Access Memory
OPC A standard for data exchange in the industrial environment.
PDH Plant Data Highway
PDM Power Distribution Module

PE Protective Earth
PLC Programmable Logic Controller
PMC PCI Mezzanine Card

RLD Relay Ladder Diagram
RTD Resistance Temperature Device
RTU Remote Terminal Unit

SEM Subsea Electronics Module
SIFT Software Implemented Fault Tolerance
SOE Sequence of Events
SRS Signal Reference Structure
TMR Triple Modular Redundancy
TTL Transistor-transistor Logic
UDH Unit Data Highway
UDP User Datagram Protocol
uOSM Universal Onsite Monitor

UPS Uninterruptible Power Supply
UTC Coordinated Universal Time

VLAN Virtual Local Area Network
WAN Wide Area Network

2 Control System Overview
More detailed information on This chapter defines the system hardware components and various levels of redundancy
control system equipment is that are possible. This equipment includes the controllers, IONet switches, I/O modules,
found in GEH-6721_Vol_II. and power distribution. Control system reliability and availability are also discussed.
2.1 Controllers
The Mark VIe controller can be a UCSx stand-alone module that mounts directly inside a
cabinet or a UCCx CompactPCI® (CPCI) 6U high single board computer that mounts in a
rack. The Mark VIe controller is loaded with software specific to its application, which
includes but is not limited to steam, gas, land-marine (LM), or BoP products. It can run
Relay Ladder Diagrams (RLD) or blocks. The IEEE® 1588 protocol is used through the
R, S, and T I/O networks (IONet) to synchronize the clock of the I/O modules and
controllers to within ±100 microseconds. Data is transferred to and from the control
system database in the controller over the I/O network(s). IONet data includes process
inputs/outputs to the I/O packs.
Refer to the section, Controller In a dual system, IONet data also includes:
Redundancy for more
information. • Internal state values and initialization information from the designated controller
• Status and synchronization information from both controllers
In a triple module redundant (TMR) system, IONet data also includes:
• Internal state values for voting and status and synchronization information from all
three controllers
• Initialization information from the designated controller
TMR Mark VIe Controllers
Control System Overview GEH-6721Y System Guide 11

2.1.1 UCSx Controller
The UCSx offers the following advantages:
• Single module
• Built-in power supply
• No jumper settings required
• No battery
• No fan (UCSAH1A and UCSBH1A/UCSBH4A)
• Dual-redundant monitored fans with IS420UCSBH3A
• Smaller cabinet footprint
• Easy access to the UCSA’s CompactFlash® and the UCSB’s NAND flash
Refer to Chapter 5 Networks Two 10/100Base-TX Ethernet ports provide connectivity to the UDH and the CDH. Three
and Communications, the additional 10/100Base-TX Ethernet ports provide connectivity to the IONets.
section, Data Highways.
UCSx Controller Processors
Controller Processor
IS220UCSAH1A 667 MHz PowerQUICC II® Pro Freescale
IS420UCSBH1A 600 MHz EP80579 Intel ®
IS420UCSBH3A 1200 MHz EP80579 Intel
IS420UCSBH4A 1066 MHz EP80579 Intel

2.1.2 UCCx Controller
The UCCx product line of controllers include the UCCAM03 and the UCCCM04. The
UCCAM03 CPCI controller is a single board module. The baseboard contains a 650 MHz
Celeron® processor, 128 MB flash, 128 MB DRAM, two serial ports, and one 10/100
Megabits Ethernet interface. The UCCCM04 contains a 1.6 GHz Pentium® M processor,
128 MB flash, 256 MB DRAM and two 10/100/1000Base-TX Ethernet ports. The
baseboard Ethernet provides the UDH connection.
2.2 IONet Switches

GE’s Industrial Ethernet 10/100 switches (ESWx) provide the performance and features
needed in today’s real-time industrial control systems. Use only ESWx Ethernet switches
in all control system I/O networks to maintain the reliability needed for all I/O module
reception of controller outputs.

2.3 Distributed I/O Modules
The I/O modules contain three basic parts: terminal board, terminal block, and I/O pack.
The terminal board mounts to the cabinet and comes in two basic types: S and T. The I/O
pack mounts to the terminal board J-port connector. Both terminal board types provide the
following features:
• Terminal blocks for I/O wiring

• Mounting hardware
• Input isolation and protection
• I/O pack connectors
• Unique electronic ID
TMR I/O Module
Simplex I/O Module
2.3.1 I/O Pack

I/O packs in the Mark VIe control system have a common processor board and a data
acquisition board that is unique to the type of connected device. I/O packs on each
terminal board digitize the signal, perform algorithms, and communicate with the Mark
VIe controller.
The I/O pack provides fault detection through a combination of special circuitry in the
data acquisition board and software running in the Central Processing Unit (CPU)
board. The fault status is transmitted to and used by the controllers. The I/O pack
transmits inputs and receives outputs on both network interfaces if connected.
Each I/O pack also sends an identification message (ID packet) to the main controller
when requested. The packet contains, the hardware catalog number of the I/O board,
the hardware revision, the board barcode serial number, the firmware catalog number,
and the firmware version. The I/O packs have a temperature sensor that is accurate to
within ±2°C (36 °F). Every I/O pack temperature is available in the database and can
be used to generate an alarm.

2.3.2 Terminal Board
Signal flow begins with a sensor connected to a terminal block on a board. Wide and
narrow terminal boards are arranged in vertical columns of high and low-level wiring. An
example of a wide board is a board that contains magnetic relays with fused circuits for
solenoid drivers. A shield strip is provided to the left of each terminal block. It can be
connected to a metal base for immediate grounding or floated to allow individual ground
wires from each board to be wired to a centralized, cabinet ground strip.
Simplex Terminal Board
Input Output
Screws Screws
I/O Pack
Connector
TMR Terminal Board

Input Output
Screws Screws
I/O Pack
Connector
Vote /
I/O Pack Select
Connector
I/O Pack
Connector

2.3.2.1 T-type
Some application-specific TMR T-type terminal boards typically fan the sensor inputs to three separate I/O packs.
terminal boards do not fan Usually, the TMR board hardware votes the outputs from the three I/O packs. T-type
inputs or vote the outputs. boards contain two, 24-point, barrier-type, removable, terminal blocks. Each point can
accept two 3.0 mm (0.12 in) (#12AWG) wires with 300 V insulation per point with either
spade or ring-type lugs. In addition, captive clamps are provided for terminating bare
wires. Screw spacing is 9.53 mm (0.375 in) minimum and center-to-center.
Barrier-type Terminal Blocks
These terminal blocks have the following features:
• Black in color with white number labels

• Terminal rating is 300 V, 10 A
• UL recognized
• Recommended screw tightening torque is 7 lb-in (0.8 Nm).

2.3.2.2 S-type
S-type boards provide a single set of screws for each I/O point and allow a single I/O
pack to condition and digitize the signal. They are half the size of T-type boards and are
standard base mounted but can also be DIN-rail mounted. These boards can be used for
simplex, dual, or dedicated triple redundant sensors by using one, two, or three modules.
S-type boards have Euro-style, box type terminal blocks. Some boards are available as
either removable or fixed terminal block versions. S-type board terminal blocks accept
one 2.05 mm (0.08 in) (#12AWG) wire or two 1.63 mm (0.06 in) (#14AWG) wires, each
with 300 V insulation per point. Screw spacing is 5.08 mm (0.2 in) minimum and
center-to-center.
Box-type Terminal Blocks
These terminal blocks have the following features:
• Green in color with number labels.

• Terminal rating is 300 V, 10 A
• UL and CSA recognized
• Recommended screw tightening torque is 5 lb-in (0.5 - 0.6 Nm)

2.3.3 I/O Module Types
2.3.3.1 General Purpose

Discrete I/O Types
I/O Pack/Qty Board Discrete I/O Types Type Remova-

per Board ble
PDIAH1A/1, 2, 3 TBCIH1C 24 discrete inputs (DI) (125 V dc, group isolated) Barrier Yes
PDIAH1B/1, 2, 3 sequence of events (SOE)
PDIAH1A/1, 2, 3 TBCIH2C 24 DI (24 V dc, group isolated) SOE Barrier Yes

PDIAH1B/1, 2, 3
PDIAH1B/1, 2, 3
PDIAH1B/1, 2, 3
PDIAH1A/, 2, 3 TICIH1A 24 DI (115/230 V ac, 125 V dc point isolated) SOE Barrier Yes
PDIAH1B/1, 2, 3
PDIAH1A/1, 2, 3 TICIH2A 24 DI (24 V dc, point isolated) SOE Barrier Yes
PDIAH1B/1, 2, 3
PDIAH1A/1 STCIH1A 24 DI (24 V dc, group isolated) SOE Box No
PDIAH1B/1
PDIAH1A/1 STCIH2A 24 DI (24 V dc, group isolated) SOE Box Yes
PDIAH1B/1
PDIAH1B/1
PDIAH1B/1
PDIAH1B/1
PDIIH1A/1 SDIIH1A 16 DI (24, 48, 125, 250 V dc, 115, 230 V ac point isolated, Box Yes
PDIIH1B/1 line-break detection) SOE
WDIIH1A Add 24 V dc, 115/230 V ac wetting voltage
WDIIH2A Add 48 V dc wetting voltage
WDIIH3A Add 125 V dc wetting voltage (group isolation)
PDIOH1A/1 TDBSH2A 24 DI and 12 type C mechanical relays (24 V dc group Box Yes
PDIOH1B/1 isolated) SOE (Refer to Option Boards Note 1, 2, and 3),
SOE for relay outputs
PDIOH1A/3 TDBTH2A 24 DI and 12 type C mechanical relays (24 V dc group Box Yes
PDIOH1B/3 isolated) SOE (Refer to Option Boards Note 1), SOE for
relay outputs

I/O Pack/Qty Board Discrete I/O Types Type Remova-
per Board ble
relay outputs
relay outputs
PDOAH1A/1, 3 TRLYH1B 12 type C mechanical relays with 6 solenoids, coil Barrier Yes
PDOAH1B/1, 3 diagnostics (115/230 V ac, 24/48/125 V dc), SOE for relay
outputs
PDOAH1A/1, 3 TRLYH1C 12 type C mechanical relays with 6 solenoids, voltage Barrier Yes
PDOAH1B/1, 3 diagnostics (115/230 V ac, 125 V dc), SOE for relay
outputs
PDOAH1A/1, 3 TRLYH2C 12 type C mechanical relays with 6 solenoids, voltage Barrier Yes
PDOAH1B/1, 3 diagnostics (24 V dc), SOE for relay outputs
PDOAH1A/1, 3 TRLYH1D 6 type A mechanical relays for solenoids, solenoid Barrier Yes
PDOAH1B/1, 3 impedance diagnostics (24/125 V dc), SOE for relay
outputs
PDOAH1A/1 SRLYH1A 12 type C mechanical relays (115/230 V ac, 24/48/125 V Box No

PDOAH1B/1 dc), SOE for relay outputs
PDOAH1A/1 SRLYH2A 12 type C mechanical relays (115/230 V ac, 24/48/125 V Box yes
PDOAH1B/1 dc) (Refer to Option Boards Note1, 2, and 3), SOE for
relay outputs
PDOAH1A/1, 3 TRLYH1E 12 type A solid-state relays (115/230 V ac), voltage Barrier yes
PDOAH1B/1, 3 diagnostics, SOE for relay outputs
PDOAH1A/1, 3 TRLYH2E 12 type A solid-state relays (125 V dc), voltage Barrier yes
PDOAH1A/1, 3 TRLYH3E 12 type A solid-state relays (24 V dc), voltage Barrier yes
PDOAH1A/3 TRLYH1F 36 mechanical relays, 12 voted type A normally open Barrier yes
PDOAH1B/3 (NO) outputs (115 V ac, 24/48/125 V dc) (Refer to Option
Boards Note 4 and 5), SOE for relay outputs
PDOAH1A/3 TRLYH2F 36 mechanical relays, 12 voted type B normally closed Barrier yes
PDOAH1B/3 (NC) outputs (115 V ac, 24/48/125 V dc) (Refer to Option
Boards Note 4 and 5), SOE for relay outputs
Option Boards
WROBH1A Note 1: Add solenoid interface to first 6 relay circuits
WROFH1A Note 2: Add fuse in COM leg of all 12 relay circuits
WROGH1A Note 3: Add fuse power distribution in COM leg of all 12 relay circuits
WPDFH1A Note 4: Fuses for solenoid power in (+) and (-) legs
WPDFH2A Note 5: Fuses for field solenoid power in top side only for common neutral AC solenoids

Analog I/O Types
I/O Pack/Qty Board Analog I/O Types Type Removable

per Board
PAICH1A/1, 3 TBAIH1C 10 analog inputs (AI) voltage over current (V/I) inputs, Barrier Yes
PAICH1B/1, 3 group isolated and 2 analog outputs (AO) (0-20 mA
outputs, group isolated)
PAICH2A/1, 3 TBAIH1C 10 AI (V/I inputs, group isolated) and 2 AO (0-20/0-200 Barrier Yes
PAICH2B/1, 3 mA outputs, group isolated)
PAICH1A/1 STAIH1A 10 AI (V/I inputs, group isolated) and 2 AO (0-20 mA Box No

PAICH1B/1 outputs, group isolated)
PAICH2A/1 STAIH1A 10 AI (V/I inputs, group isolated) and 2 AO (0-20/0-200 Box No

PAICH2B/1 mA outputs, group isolated)
PAICH1A/1 STAIH2A 10 AI (V/I inputs, group isolated) and 2 AO (0-20 mA Box Yes
PAICH2A/1 STAIH2A 10 AI (V/I inputs, group isolated) and 2 AO (0-20/0-200 Box Yes
PAICH2B /1 mA outputs, group isolated)
PAICH1A/1 SAIIH1A 10 AI (V/I inputs, point isolated) and 2 AO (0-20 mA Box No

PAICH2A/1 SAIIH1A 10 AI (V/I inputs, point isolated) and 2 AO (0-20/0-200 Box No

PAICH1A/1 SAIIH2A 10 AI (V/I inputs, point isolated) and 2 AO (0-20 mA Box Yes
PAICH2A/1 SAIIH2A 10 AI (V/I inputs, point isolated) and 2 AO (0-20/0-200 Box Yes
PAOCH1A/1, 2 TBAOH1C 16 AO (0-20 mA outputs) 8 per I/O pack Barrier Yes

PAOCH1B/1, 2
PAOCH1A/1 STAOH1A 8 AO (0-20 mA outputs) Box No
PAOCH1B/1
PAOCH1A/1 STAOH2A 8 AO (0-20 mA outputs) Box Yes
PAOCH1B/1
PPDAH1A/1 JPDS Power Distribution System Feedback
PPDAH1B/1 JPDM
JPDG
JPDC
PTCCH1A/1, 2, 3 TBTCH1B 12 Thermocouples Barrier Yes
PTCCH1B/1, 2, 3
PTCCH2A/1, 2, 3 TBTCH1B 12 Thermocouples with extended range for EPRI Barrier Yes
PTCCH2B/1, 2, 3 compliance
PTCCH1A/1, 2 TBTCH1C 24 Thermocouples (12 per I/O pack) Barrier Yes

PTCCH1B/1, 2
PTCCH2A/1, 2 TBTCH1C 24 Thermocouples (12 per I/O pack) with extended Barrier Yes
PTCCH2B/1, 2 range for EPRI compliance
PTCCH1A/1 STTCH1A 12 Thermocouples Box No

PTCCH1B/1

I/O Pack/Qty Board Analog I/O Types Type Removable
per Board
PTCCH2A/1 STTCH1A 12 Thermocouples with extended range for EPRI Box No
PTCCH2B/1 compliance
PTCCH1A/1 STTCH2A 12 Thermocouples Box Yes

PTCCH1B/1
PTCCH2A/1 STTCH2A 12 Thermocouples with extended range for EPRI Box Yes
PTCCH2B/1 compliance
PRTDH1A/1, 2 TRTDH1D 16 RTDs 3 wires /RTD (8 per I/O pack) Barrier Yes
PRTDH1B/1, 2
PRTDH1A/1, 2 TRTDH2D 16 RTDs 3 wires /RTD (8 per I/O pack) supports fast Barrier Yes
PRTDH1B/1, 2 scan rate
2.3.3.2 Fieldbus
Fieldbus I/O
I/O Pack/Qty Board Communications Types Type Removable
per Board
PSCHHIA/1, 2 SSCAH1A 6 serial Box No
SSCAH2A 6 serial Box Yes
PRTDH1A/1 SRTDH1A 8 RTDs 3 wires /RTD Box No
PRTDH1B/1
PRTDH1A/1 SRTDH2A 8 RTDs 3 wires /RTD Box Yes
PRTDH1B/1
PSCAH1A/1 SSCAH1A 6 MODBUS Master serial or 1 Modbus Ethernet Box No
PSCAH1B/1
PSCAH1A/1 SSCAH2A 6 MODBUS Master serial or 1 Modbus Ethernet Box Yes
PSCAH1B/1
PCNOH1A/1 CANopen Master Gateway n/a n/a
PCNOH1B/1
PPRFH1A/1 PROFIBUS - DP-V0, Class 1 Master Communications n/a n/a
SPIDG1A
PPRFH1B/1 PROFIBUS - DP-V1 Class 1 Master Communications
(PPRFH1B only)
PFFAH1A/1 FOUNDATION Fieldbus H1 TO HSE Linking Device
PHRAH1A/1 SHRAH1A 10 AI (V/I inputs) and 2 AO (0-20 mA outputs) with Box No

PHRAH1B/1 HART communications
PHRAH1A/1 SHRAH2A 10 AI (V/I inputs) and 2 AO (0-20 mA outputs) with Box Yes
PHRAH1B/1 HART communications

2.3.3.3 Turbine Application
Turbine specific I/O modules provide direct interface to unique turbine field devices,
which reduces or eliminates a substantial amount of interposing instrumentation. As a
result, many potential single-point failures are eliminated for improved running reliability
and reduced long-term maintenance. Direct interface also enables the diagnostics to
directly monitor field devices. This provides more precise messages to minimize
maintenance time.
Turbine Specific I/O
I/O Pack Qty Board Turbine Applications Type Remova-

per Board ble
PAMCH1A/1, 2 SAMBH1A Acoustic Monitor for MS 6, 7, 9 gas turbines: 18 inputs and Box Yes
buffered outputs
PCLAH1A/1 SCLSH2A Core Analog I/O for aero-derivative turbines, simplex, TMR Box Yes
PCLAH1B/1 SCLTH2A Additional I/O with SCLT board for TMR applications
PCAAH1A/1 TCASH2A Core Analog I/O for heavy duty gas turbines, Simplex and Box Yes
PCAAH1B/1 TCATH2A TMR Additional I/O with TCAT board for TMR applications
PEFVH1A/1, 2, 3 TEFVH1A Electric Fuel Valve Gateway to Woodward™ DVP
PGENH1A/1, 3 TGNAH1A Power Load Unbalance: (3) 1-phase PTs, 3 V/I inputs ** **
PVIBH1A/1, 3 TVBAH1A Seismic/Proximitor/Accelerometer/Velometer 8 inputs, 3 Barrier Yes

position, 1 reference, buffered outputs
PSVOH1A/1, 3 TSVCH1 Servos: 2 channels, 2-coil outputs, 8 LVDTs and excitation, 2 Barrier Yes
TSVCH2A pulse rate inputs (heavy duty & aero gas & steam)
PSVPH1A/1 SSVPH1A Steam servo applications: 2 channels, 2-coil outputs, 6 LVDTs Barrier Yes
SSVPH2A and 2 excitation, 1 pulse rate input for speed feedback Box Yes
Trip Protection: Primary and emergency trip protection is available in many combinations, which are too complex to describe
in this table. For descriptions of these combinations, refer to GEH-6721, Mark VIe Control, Volume II System Hardware
Guide.
** Analog inputs are box-type and removable. Current transformer (CT) inputs are barrier-type and not removable.

2.3.3.4 Migration
Mark V & V LM Migration I/O
I/O Pack/Qty Terminal Interface Migration I/O Types Type Remova-

per Board Board Board ble
PIOAH1A/1 N/A JPDV ARCNET I/O (for excitation control) N/A N/A
PMVE/1, 3 QTBA, TCQC, UCSA used as I/O pack controller to interface Box No – H1A,
TBQA, MVRA, with dedicated turbine I/O application boards. Yes - H2A,
TBQB, MVRB, UCSA has 6 communication ports No - G1A,
TBQC, MVRC, (1 –RS-232C, 2 –Ethernet, 3 –HSSL) No - G1B
TBQF, MVRF
TBQD,
TBQG,
CTBA,
TBCA,
TBCB
PMVD/1, 3 DTBA, TCRA 96 contact inputs, Box No – H1A,
DTBB, 60 relay contact outputs Yes – H2A,
DTBC, No –G1A,
DTBD No – G1B
PMVP/3 PTBAG1A Expansion 2 magnetic p.u. speed inputs, Barrier No
PTBAG2A board TCEB 8 flame detector pulse inputs,
and trip Trip solenoid interface relays,
boards Generator breaker synchronizing circuits
TCTE, E-Stop
TCTG,
TCTL,
TCTS,

2.3.3.5 Safety
Safety Controller I/O
I/O Pack / Qty Terminal Safety I/O Types Type Remova-

per Board Board ble
YAICS1A/1, 3 TBAIS1C, 10 analog inputs (voltage, 0-20 mA) Box Yes
/1 STAIS1A, 2 analog outputs (0-20 mA) No
/1 STAIS2A Yes
YDIAS1A/1, 2, 3 TBCIS1, 24 discrete inputs w/ group isolation Box Yes
/1, 2, 3 TBCIS2, (24 V dc, 48 V dc, or 125 V dc) Yes
/1, 2, 3 TBCIS3, Yes
/1 STCIS1A, No
/1 STCIS2A, Yes
/1 STCIS4A, Yes
/1 STCIS6A, Yes
YDOAS1A/1, 3 TRLYS1D, 6 relay outputs Box Yes
YDOAS1A/1, 3 TRLYS1B, 12 relay outputs Box Yes

/3 TRLYS1F, Yes
/3 TRLYS2F, Yes
/1 SRLYS1A, No
/1 SRLYS2A Yes
YHRAS1A/1 SHRAS1A 10 analog inputs (0-20 mA), Box No
SHRAS2A 2 analog outputs (0-20 mA) Yes
(All I/O HART enabled)
YTCCS1A/1 , 2 TBTCS1B, 12 thermocouple inputs Box Yes

/1 , 2 TBTCS1C, Yes
/1 STTCS1A, No
/1 STTCS2A Yes
YVIBS1A TVBAS2A 8 vibration, Box Yes
4 position and
1 Keyphasor
YPROS1A/ 3 TREAS1A, Backup/emergency protection Barrier Yes

/3 TREAS2A, 3 speed inputs Barrier
/3 TREAS3A, 7 contact inputs Box
/3 TREAS4A, 3 monitored trip relay outputs Box
/3 TREGS1B, 1 E-Stop Box
/3 TREGS2B, Box
/1 SPROS1A Barrier
YTURS1A/3 TTURS1C, Primary turbine protection Box Yes
TRPAS1A, 4 speed inputs
TRPAS2A, 8 flame inputs
TRPGS1B, 3 monitored trip relay outputs
TRPGS2B 1 E-Stop

2.3.3.6 Renewables
Renewable Energy I/O
Assembly Individual Renewable I/O Types
Boards
AEPAH1A AEPAH1A Alternative Energy Pitch Axis, special-purpose in 1.5 MW wind pitch control: 8 analog inputs,
BPPB 1 incremental encoder input, 1 absolute encoder input, 1 analog output, 20 discrete inputs, 1
AEPAH1C AEPAH1A discrete output, 8 relay outputs, 2 RS-485 interfaces, 1 brake control output
BPPC
AEPCH1A AEPCH1A Alternative Energy Pitch Center module in 20, 30, and 40 Newton Meters (Nm) wind pitch
BPPB control: 1 24 V dc, 8 A power input, 1 RS-422 interface
AEPCH1B AEPCH1B
BPPB
AEPCH1C AEPCH1C
BPPB
AEPCH1D AEPCH1A
BPPC
WEMDH4
AEPCH1E AEPCH1B
BPPC
WEMDH5
AEPCH1F AEPCH1C
BPPC
WEPAH1A AEPAH1B Wind Energy Pitch Axis special-purpose in 30 and 40 Nm wind pitch control: 8 analog inputs,
BPPB 1 incremental encoder input, 1 analog output, 20 discrete inputs, 2 discrete outputs, 9 relay
WPCI outputs, 2 RS-485 interfaces, 2 PWM control outputs
WEPAH1B AEPAH1B
BPPC
WPCI
WEPAH2A AEPAH1B
BPPB
WEPAH2B AEPAH1B
BPPC
WETAH1A WETAH1A Wind Energy Top Box board A, special-purpose in 1.5 MW ESS turbine: 69 digital inputs; 8
BPPB are pulse-rate counter inputs, 18 analog PT100 temperature sensor inputs, 2 analog
WETAH1B WETAH1B thermistor temperature sensor inputs, 12 analog 4 to 20 mA current inputs, 25 relay contact
BPPC outputs 19 solid-state relay outputs, 1 RS-485 interface
WCBMH1A WCBMH1A Wind Condition Top Box Monitor condition-based monitoring for wind turbines, measures
vibration on main bearing, gearbox, and generator bearings
WEMAH1A WEMA Wind Energy Main converter control for ESS wind turbine: 27 digital inputs, 2 analog
BPPB thermistor temperature sensor inputs, 9 relay contact outputs, 3 solid-state relay outputs
WEMAH1B WEMA
BPPC
WEMAH2A WEMA Wind Energy Main converter control for Brilliance Solar PV inverter: 27 digital inputs, 2 analog
BPPB thermistor temperature sensor inputs, 9 relay contact outputs, 3 solid-state relay outputs
WEMAH2B WEMA
BPPC
WECAH1A MACC Wind power converter interface for the power converter: 27 digital inputs, 9 relay contact
BPPx outputs, 3 solid-state relay outputs
SECAH1A MACC Solar power converter interface for the solar inverter: 27 digital inputs, 9 relay contact outputs,
BPPx 3 solid-state relay outputs

2.4 Power Distribution
Refer to GEH-6721_Vol_II, the The Mark VIe control is designed to operate on a flexible, modular selection of power
chapter PDM Power sources. The power distribution modules (PDM) support 115/230 V ac, 24 and 125 V dc
Distribution Modules. power sources in many redundant combinations. The power applied is converted to 28 V
dc for operation of the I/O packs, controllers, and switches.
RST
Control JPDP
System JPDS or JPDM Power
PPDA
Feedback 28 V Control Power
R S T JPDL
PS PS PS Pack
RST
24/48 V Pwr Supply

JPDE Dc
24/48 V Pwr Supply JPDD
24 V dc Power
24/48 V Pwr Supply
Dc
sources. JPDB , JPDE, and
PS run s fro m one of thre e
JPDD Power
Dc Power
JPDR Distribution Boards
JPDF do not conn ect
Ac Power
Selector Board Select1 of 2
simu lta neously.
Local Ac Power
Distribution Boards
Ac Input
JPDB Ac
115 / 230 V ac JPDA
Power
x2
Ac Input Ac
JPDA
Power
JPDD Dc
JPDF
125 V Battery Power
125 V dc
Dc
JPDD
Power
Core Circuits Branch Circuits

DACA
DACA
Ac to Dc
Converter Modules
PDM Basic Layout

The PDM system can be divided into two substantially different categories, the core
distribution system, and the branch circuit elements. The core pieces share the feature of
cabling into a PPDA I/O pack for system feedback. They serve as the primary power
management for a cabinet or series of cabinets. The branch circuit elements take the core
output and fan it into individual circuits for consumption in the cabinets. They are not part
of the PPDA system feedback. Branch circuits provide their own feedback mechanisms. It
is not expected that all of the core components and branch circuits that make up the PDM
will be used on every system.
2.5 Redundancy Options

The Mark VIe control provides scaleable levels of redundancy. The basic system is a
single (simplex) controller with simplex I/O and one network. The dual system has two
controllers, singular or fanned TMR I/O and dual networks, which provides added
reliability and online repair options. The TMR system has three controllers, singular or
fanned TMR I/O, three networks, and state voting between controllers providing the
maximum fault detection and availability.
2.5.1 Controller Redundancy

Controller redundancy consists of the following:
• Simplex controller
• Dual controllers
• Triple redundant controllers (TMR)

2.5.1.1 Simplex Controller
The simplex control architecture contains one controller connected to an Ethernet
interface through the Ethernet network (IONet). No redundancy is provided and no online
repair of critical functions is available. Online replacement of non-critical I/O (that where
the loss of the I/O does not stop the process) is possible.
Each I/O pack delivers an input packet at the beginning of the frame on its primary
network. The controller sees the inputs from the I/O modules, performs application code,
and then delivers an output packet(s) for all I/O modules. The following diagram displays
typical simplex controller architecture.
Simplex Mark VIe Control System

2.5.1.2 Dual Controllers
For non-redundant UDH The dual control architecture contains two controllers, two IONets, and singular or fanned
networks, there is only one TMR I/O modules. The following diagram displays a dual Mark VIe control system.
UDH switch and both
controllers are connected to it.
Dual Mark VIe Control System
The dual control Mark VIe architecture reliability can be significantly better than the
single controller. All of the network and controller components are redundant and can be
repaired online. The I/O reliability can be mixed and matched meeting reliability needs
described in the I/O option sections below.
In a dual Mark VIe control system, both controllers receive inputs from the I/O modules
on both networks and transmit outputs on their respective IONet continuously. When a
controller or network component fails the system does not require fault detection nor
failover time to continue operating.

In a dual system, the level of The Mark VIe controller or I/O module listens for the data on both networks at power on.
I/O reliability can be varied to The channel that delivers the first valid packet becomes the preferred network. As long as
meet the application needs for the data arrives on that channel the pack/controller uses this data. When the preferred
specific I/O. Not all I/O has to channel does not deliver the data in a frame, the other channel becomes the preferred
be dual redundant. channel as long as valid data is supplied. This prevents a given I/O pack/controller from
bouncing back and forth between two sources of data. This does mean that different I/O
packs/controllers may have separate preferred sources of data but this can also happen if
any component fails.
In a dual control system, the application software in each controller tries to produce the
same results. After many iterations of the application software, it is possible for the
internal data values to differ due to mathematical round off, and different past history
(power-up). To converge this data, the internal data (state) variables are taken from the
designated controller and transmitted to the non-designated controller for its use. This is
known as state exchange.
State variables are any internal variables not immediately derived from input or control
constants. Any variable that is used prior to being re-calculated is an internal state
variable.
This principle can be displayed in the following two equations:
A = B+C
C=3xD
Assume B and D are inputs and A and C are intermediate values. Since C is used prior to
being calculated, the value of C during the previous scan retains some state information.
Therefore, C is a state variable that must be updated in the non-designated controller if
both controllers are to remain synchronized.
In the Mark VIe controller, Boolean state variables are updated on every control frame.
The analog state variable updates are multiplexed. A subset of analog state variables is
updated every control frame. The controller rolls through each subset until all state
variables are transmitted.

2.5.1.3 Triple Redundant Controllers (TMR)
For non-redundant UDH The TMR control architecture contains three controllers, three IONets, and singular or
networks, there is only one fanned TMR I/O Modules.
UDH switch connecting all
three controllers. Reliability and availability are much better with TMR controllers than with dual
controllers due to increased fault detection capability. In addition to all of the dual
redundant features, the TMR controller provides three independent outputs to all TMR
I/O modules and the state variables between controllers are voted rather than jammed.
TMR Mark VIe Control System
In a TMR system, the level of In a TMR Mark VIe control system, all three controllers receive inputs from the I/O
I/O reliability can be varied to modules on all networks and transmit outputs on their respective IONet continuously. If a
meet specific application controller or network component fails, the system does not require fault detection or
requirements. Not all I/O has failover time to continue operating. All controllers transmit their copy of the state
to be dual or triple redundant. variables after the output packet has been transmitted. Each controller takes the three sets
of state variables and votes the data to get the values for the next run cycle.

2.5.2 I/O Redundancy
There are various options available for single and multiple packs and single and dual
networks for I/O redundancy. The following are options for TMR I/O modules:
• Single Pack Dual Network I/O Module (SPDN)

• Two Single Pack, Single Network (2SPSN) I/O Modules
• Dual Pack, Dual Network (DPDN) I/O Module
• Triple Pack, Dual Network (TPDN) I/O Module
• Hot Backup I/O Module
2.5.2.1 Single Pack Dual Network I/O Module (SPDN)

This configuration is typically used for non-critical single sensor I/O. A single sensor
connects to a single set of acquisition electronics which is then connected to two
networks.
• Single data acquisition

• Redundant network
The I/O pack delivers input data on both networks at the beginning of the frame and
receives output data from both controllers at the end of the frame.
2.5.2.2 Two Single Pack, Single Network (2SPSN) I/O Modules

This configuration is typically used for inputs where there are multiple sensors
monitoring the same process points. Two sensors are connected to two independent I/O
modules.
• Redundant sensors
• Redundant data acquisition
• Online repair
Each I/O pack delivers input data on a separate network at the beginning of the frame and
receives output data from separate controllers at the end of the frame.
2.5.2.3 Dual Pack, Dual Network (DPDN) I/O Module

This is a special case for inputs only, using a dual pack, dual network module. A fanned
input terminal board can be populated with two packs providing redundant data
acquisition for a set of inputs.

• Online repair
Each I/O pack delivers input data on a separate network at the beginning of the frame.

2.5.2.4 Triple Pack, Dual Network (TPDN) I/O Module
This is a special case mainly intended for outputs, but also applies to inputs. The special
output voting/driving features of the TMR I/O modules can be used in a dual control
system. The inputs from these modules are voted in the controller.

• Output voting in hardware
• Online repair
Refer to customer specific Two of the I/O packs are connected to separate networks delivering input data and
drawings for connection receiving output data from separate controllers. The third I/O pack is connected to both
information to other networks. This pack delivers inputs on both networks and receives outputs from both
distributed I/O components. controllers.
2.5.2.5 Hot Backup I/O Module

This is a special case mainly intended for a small set of I/O packs used as a gateway to
another network. In this configuration, there are dual I/O packs, dual network but only
one I/O pack is communicating to the gateway network at one time, the other I/O pack
operates in a backup mode. The inputs from active module are used in the controller.

• Online repair
The two I/O packs are both connected to both networks, but only communicates to the
controller and the gateway network. If a failure occurs on the active I/O pack, the backup
I/O pack becomes the active I/O pack, thus maintaining communication with the
connected devices.

2.5.3 Input Processing
All inputs are available to all three controllers, but there are several ways that the input
data is handled. For input signals existing in only one I/O module, all three controllers use
the same value as common input without voting, as displayed in the table below. Signals
that appear in all three I/O channels may be voted to create a single input value. The triple
inputs may come from three independent sensors. They can also be created from a single
sensor by hardware fanning at the terminal board.
Mark VIe Controller Available Topology

Redundancy
Simplex One I/O pack with one IONet*
Dual One I/O pack with two IONets

Two I/O packs with one IONet per pack
Three I/O packs with <R> one IONet to controller <R>, <S> one IONet to controller
<S>, and <T> two IONets with one to controller <R> and one to controller <S>
TMR Fanned – three packs, one IONet/pack with one terminal board
Dedicated – three packs, one IONet/pack with three separates terminal boards
*The number of IONets in a system must equal the number of controllers.
For any of the above input configurations, multiple inputs can be used to provide
application redundancy. For example, three Simplex inputs can be used and selected in
application code to provide sensor redundancy.
The Mark VIe control provides configuration capability for input selection and voting
using a simple, highly reliable and efficient selection/voting/fault detection algorithm to
reduce application configuration effort. This maximizes the reliability options for a given
set of sensor inputs and provides output voting hardware compatibility. All applicable
subsets of reliability options are available on a per terminal board basis for any given
Mark VIe topology. For example, in a TMR controller, all simplex and dual option
capabilities are also provided.
While each IONet is associated with a specific controller that is responsible for
transmitting outputs, all controllers see all IONets. The result is that for a simplex input
the data is not only seen by the output owner of the IONet, it is seen in parallel by any
other controllers. The benefit of this is that loss of a controller associated with a simplex
input does NOT result in the loss of that data. The simplex data continues to arrive at
other controllers in the system.
Simplex – One I/O pack, One IONet

Dual – One I/O pack, Two IONets
Dual – Two I/O Packs, One IONet
Dual – Three I/O Packs with 1, 1, 2 IONets
TMR Fanned – Three I/O Packs with One IONet per I/O Pack
TMR Dedicated – Three simplex I/O modules with One IONet per I/O Pack

A single input can be brought to the three controllers without any voting. This is used for
non-critical, generic I/O, such as monitoring 0-20 mA inputs, contacts, thermocouples,
and resistance temperature devices (RTD). This interconnection can also include the
following gateway devices: CANbus, FOUNDATION Fieldbus®, Profibus, and
Modbus.
Single Input to Three Controllers, Not Voted
One sensor can be fanned to three I/O boards as above for medium-integrity applications.
This is used for sensors with medium-to-high reliability. Three such circuits are needed
for three sensors. Typical inputs are 0-20 mA inputs, contacts, thermocouples, and RTDs.
One Sensor with Fanned Input and Software Voting

Three independent sensors can be brought into the controllers without voting to provide
the individual sensor values to the application. Median values can be selected in the
controller if required. This configuration, displayed in the following figure, is used for
special applications only.
Three Independent Sensors with Common Input, Not Voted
The following figure displays three sensors, each one fanned and then software
implemented fault tolerance (SIFT) voted. This provides a high reliability system for
current and contact inputs, and temperature sensors.
Three Sensors, Each One Fanned and Voted, for Medium-to-High Reliability Applications

Highly reliable speed input applications are brought in as dedicated inputs and SIFT
voted. The following figure displays this configuration. Inputs such as speed control and
overspeed are not fanned so there is a complete separation of inputs with no hardware
cross coupling which could propagate a failure. RTDs, thermocouples, contact inputs, and
0-20 mA signals can also be configured this way.
Three Sensors with Dedicated Inputs, Software Voted for High Reliability Applications
2.5.4 Output Processing

The system outputs are the portion of the calculated data transferred to the external
hardware interfaces and then to the various actuators controlling the process. TMR
outputs are voted in the output voting hardware. Any system can output individual signals
through simplex hardware.
The three voting controllers calculate TMR system outputs independently. Each controller
sends the output to its associated I/O hardware (for example, the R controller sends output
to the R I/O). The three independent outputs are then combined into a single output by a
voting mechanism. Different signal types require different methods of establishing the
voted value.
The signal outputs from the three controllers fall into three groups:
• Outputs are driven as single ended non-redundant outputs from individual I/O
networks
• Outputs exist on all three I/O networks and are merged into a single signal by the
output hardware
• Outputs exist on all three I/O networks and are output separately to the controlled
process. This process may contain external voting hardware.
For normal relay outputs, the three signals feed a voting relay driver, which operates a
single relay per signal. For critical protective signals, the three signals drive three
independent relays, with the relay contacts connected in the typical six-contact voting
configuration.

Relay Output Circuits for Protection
For servo outputs, the three independent current signals drive a three-coil servo actuator,
which adds them by magnetic flux summation, as displayed in the following figure.
Failure of a servo driver is sensed and a deactivating relay contact is closed to short the
servo coil.
TMR Circuit to Combine Three Analog Currents into a Single Output

The following figure displays 0-20 mA signals combined through a 2/3 current sharing
circuit that allows the three signals to be voted to one. Failure of a 0-20 mA output is
sensed and a deactivating relay contact is opened.
TMR Circuits for Voted 0-20 mA Outputs

2.6 Reliability and Availability
2.6.1 Mean Time Between Failure (MTBF)
MTBF is a basic measure of reliability for systems. It is the average failure free operating
time, during a particular measurement period under stated conditions. A failure may or
may not result in a problem with the overall system depending on any redundancy
employed. MTBF is usually specified for each replaceable system component.
MTBF roll up of the system components gives the equipment owner the knowledge
needed to determine how long the equipment can be expected to operate without failure
under given conditions. If it is essential that the equipment does not fail during operation,
the owner can use this data to schedule maintenance/replacement of the equipment prior
to failure. Alternately, redundant applications could be used preventing system problems
when a failure occurs.
MTBF data is also used to determine the weak links in a system. The system engineer
provides contingency options for those weak links to obtain higher reliability.
2.6.2 Mean Time Between Forced Outage (MTBFO)

MTBFO is a measure of system availability, which includes the effects of any fault
tolerance that may exist. This average time between failures causes the loss of system
functions.
The engineer must be very aware of MTBF and MTBFO when designing a reliable
continuous system. To maximize the MTBFO, Mark VIe control systems undergo
evaluation of all system component MTBF values. The effects of failures and contingency
operation are then analyzed to maximizing MTBFO.
To continue operation after a critical system component has failed, a control must have
one or more backups in place (redundancy) to improve the MTBFO significantly above
that of a simplex control. The simplest method is adding a second component that takes
over the critical function when a fault is detected.
The redundancy in the system can be either active or standby. The Mark VIe control uses
active redundancy and has all components operating simultaneously. Standby redundancy
activates backup systems after a failure is detected.
Realizing the full benefits of redundancy, a system failure must be detectable for the
control to bypass it. In a dual control, gross failures are readily detectable while subtle
failures are more difficult to detect. TMR controls, using two out of three voting, are
always able to select a valid value when presented with any single failure.
Depending on the equipment, the time required to detect the fault and switch to the new
component may be hours/minutes/seconds/milliseconds. In the case of fuel-flow control
to a turbine, this is required to be done in milliseconds.

When a redundant control bypasses a failure, it is required that the system annunciate the
presence of the failure and that repairs be completed in a timely fashion. The term, mean
time to repair (MTTR), refers to the time it takes to identify and repair a given failure.
The Mark VIe control is designed to support a MTTR of four hours. This preserves the
MTBFO benefits of redundancy resulting in unequaled system reliability. A control is
used to run the system as well as detect system failures. In a dual control, configured for
one out of two to run, it is often necessary to add dedicated tripping controls for each
critical trip system. This is done to yield running reliability while maintaining required
tripping reliability.
A TMR control normally configures the control for two out of three selection. This yields
high running and tripping reliability from the primary control. Additional dedicated
tripping controls can be used to achieve even higher tripping reliability, but they must also
be TMR to preserve running reliability.
2.6.3 Fault Detection

Refer to GEH-6721, Mark VIe A system offering redundancy can be less reliable than a non-redundant system. The
Control Volume III Diagnostics system must be able to detect and annunciate faults so it can be repaired before a forced
and Troubleshooting, for outage occurs. Fault detection is needed to ensure a component or group of components
further information. are operating properly. Fault detection is achieved through one or more of the following
methods.
• Operator inspection of the process

• Operator inspection of the equipment.
• Special hardware circuits to monitor operation
• Hardware and software watchdogs
• Software logic
• Software heartbeats
Complex control systems have many potential failure points. This can be very costly and
time consuming to create foolproof fault detection. Failure to control the outputs of a
system is the most damaging. Fault detection must be determined as close to the output as
possible to achieve the highest level of reliability. With the Mark VIe control configured
using triple redundant controllers and I/O modules, a high level of detection and fault
masking is provided by voting the outputs of all three controllers and monitoring
discrepancies.

All Mark VIe control systems benefit from the fault detection design of the I/O packs.
Every pack includes function-specific fault detection methods attempting to confirm
correct operation. This is made possible by the powerful local processing that is present in
each input and output pack. Some examples of this include:
• Analog to digital (A/D) converters are compared to a reference standard each

conversion cycle. If the converted calibration input signal falls outside of acceptable
ranges, the pack declares bad health.
• Analog output 0-20 mA signals use a small current-sense resistor on the output
terminal board. This signal is read back through a separate A/D converter and
compared to the commanded value. A difference between the commanded and actual
value exceeding an acceptable level results in the output signal being declared in bad
health.
• Discrete input opto-isolators are periodically forced to an on condition, then forced
off. This is done independently of the actual input signal and is fast enough not to
interfere with the sequence of events (SOE) time capture. If any signal path is stuck
and does not respond to the test command, the signal is declared in bad health.
2.6.4 Online Repair

When a component failure is detected and healed in the control system on a critical path,
a potential failure has been avoided. Subsequent actions can include:
Option 1- Continue running until the backup component fails.
Option 2 - Continue running until the system is brought down in a controlled manner to
replace the failed component.
Option 3 - Replace the component online.
Option 1 is not recommended. A redundant system, where the MTTR is infinite can have
a lower total reliability than a simplex system.
Option 2 is a valid procedure for some processes needing predictable mission times.
Many controlled processes cannot be easily scheduled for a shut down.
Note As MTTR increases from the expected four hours to infinite, the system reliability
can decline from significantly greater down to less than a simplex system reliability.
Repair should be accomplished as soon as possible.
Option 3 is required to get the maximum benefit from redundant systems with long
mission times. In dual or triple redundant Mark VIe controller applications, the
controllers and redundant I/O packs can be replaced online.

To ensure online repair capability, control systems must have their redundancy tested after
installation and after any system modifications. Refer to the requisition specific system
application documentation/control specification (if available) for redundancy testing
procedures.
Forced Outage Probability versus Time (Conventional TMR)
Forced Outage Probability versus Time (Mark VIe TMR)

2.6.5 Designated Controller
Although three controllers, R, S, and T, contain identical hardware and software, some of
the functions performed are unique. A single designated controller can perform the
following functions:
• Supply initialization data to the other two controllers at start-up

• Keep the master time clock
• Supply variable state information to the other controllers if one fails
For the purposes of deciding which controller is to be the designated controller, each
controller nominates itself on a weighting algorithm. The nominating values are voted
among the controllers and the majority value is used. If there is a tie, or no majority, the
priority is R, then S, and then T. If a designated controller is powered down and later
powered up, the designated controller will move and not come back if all controllers are
equal. This ensures that a toggling designated controller is not automatically reselected.
Designated controller selection is based on:
• Control state
• UDH connectivity
• IONet connectivity
• NVRAM health
2.6.6 Communication Loss

Refer to specific pack Each output pack monitors the IONet for valid commands from one or two controllers. In
documentation in GEH-6721, the event that a valid command is not received within an expected time the pack declares
Mark VIe Control Volume II, the communication as being lost. Upon loss of communication the pack action is
System Hardware Guide. configurable. The pack can continue to hold the last commanded value indefinitely or it
can be commanded to go to a specified output state. The default action is to go to a
power-down state, the same as if the power were removed from the pack.
For critical loops, the default action is the only acceptable choice. The other options are
provided for non-critical loops, where running liability may be enhanced by an alternate
output.
2.6.7 State Exchange

To keep multiple controllers in synchronization, the Mark VIe control efficiently
exchanges the necessary state information through the IONet. State information includes
calculated values such as timers, counters, integrators, and logic signals such as bi-stable
relays, momentary logic with seal-in, and cross-linked relay circuits. State information is
voted in TMR controllers and follows the designated controller in dual or faulted TMR
systems.
2.6.8 Voting
Voting in the Mark VIe control is separated into analog and logic voting. Additionally,
fault detection mechanisms directly choose owned inputs and designated states.

2.6.8.1 Median Value Analog Voting
The analog signals are converted to a floating-point format by the I/O pack. The voting
operation occurs in each of the three controller modules (R, S, and T). Each controller
receives a copy of the data from the other two channels. For each voted data point, the
controller has three values including its own. The median value voter selects the middle
value of the three as the voter output. This is the most likely of the three values to be
closest to the true value.
Median Value Voting Examples with Normal and Bad Inputs
2.6.8.2 Two Out of Three Logic Voter

Each of the controllers has three copies of the data for the logic voter. Voting is a simple
logic process, inputting the three values and finding the two values that agree.

2.6.8.3 Disagreement Detector
Failure of one of the three A disagreement detector continuously scans the input prevote input data sets and
voted input circuits has no produces an alarm bit if a disagreement is detected between the three values. Any
effect on the controlled process disagreement between the prevote logical signals generates an alarm. For analog signals,
since the fault is masked by comparisons are made between the voted value and each of the three prevote values. The
SIFT. Without a disagreement delta for each value is compared with a user programmable limit value. The limit can be
detector, a failure could go set as required to avoid nuisance alarms, but give indication that one of the prevote values
unnoticed until a second has moved out of normal range. Each controller is required to compare only its prevote
failure occurs. value with the voted value; for example, R compares only the R prevote value with the
voted value. Nominal, analog voting limits are set at a 5% adjustment range, but can be
configured to any number for each analog input.
2.6.9 Forced Variables

The controller has a feature called Forced Variables. This allows the maintenance
technician using application software to set analog or logical variables to forced values.
Variables remain at the forced value until unforced. Both compute and input processing
respect forcing. Any applied forcing is preserved through power down or restart of the
controller.
Logic Forcing is for offline software checkout and

troubleshooting and should only be used in conjunction with
proper lockout/tag out procedures. Forcing of protective
functions is never permissible for an operating unit.
Warning
2.6.10 Peer I/O

In addition to the data from the I/O modules, there is a class of data coming from other
controllers in other cabinets connected through the UDH network. For integrated systems,
this network provides a data path between multiple turbine controllers and possibly the
controls for the generator, the exciter, or the HRSG/boiler.
Selected signals from the controller database can be mapped into pages of peer outputs
that are broadcast periodically on the UDH I/O to peer controllers. For TMR systems, the
UDH communicator performs this action using the data from its internal database. In the
event of a redundant UDH network failure, the controller will request data over the
remaining network, the IONet.
2.6.11 Rate of Response

Mark VIe control can run selected control programs at the rate of 100 times per second,
(10 ms frame rate) for simplex, dual, and TMR systems. For example, bringing the data
from the interface modules to the control module and voting takes 3 ms, running the
control program takes 4 ms, and sending the data back to the interface modules takes 3
ms. These example times vary depending on type of I/O and complexity of controller
logic used.

2.6.12 Command Action
Using IONet connectivity, the controller copies command traffic from the UDH across all
controllers. This provides fault tolerance for dual UDH networks.
2.6.13 Turbine Protection

Refer to GEH-6721_Vol_II for Turbine overspeed protection is available in three levels; control, primary, and emergency.
more information. Control protection comes through closed loop speed control using the fuel/steam valves.
Primary overspeed protection is provided by the controller. The TTUR terminal board and
PTUR I/O pack bring in a shaft speed signal to each controller where the median signal is
selected. If the controller determines a trip condition, it sends the trip signal to the TRPG
terminal board through the PTUR I/O board. The three PTUR outputs are 2/3 voted in
three relay voting circuits (one for each trip solenoid) and power is removed from the
solenoids. The following figure displays the primary and emergency levels of protection.
Primary and Emergency Overspeed Protection

Emergency overspeed protection is provided by the independent triple redundant PPRO
protection system displayed in the preceding figure. This uses three shaft speed signals
from magnetic pickups (MPU), one for each protection module. These are brought into
SPRO, a terminal board dedicated to the protection system.
Each PPRO independently determines when to trip, and the signals are passed to the
TREG terminal board. TREG operates in a similar way to TRPG, voting the three trip
signals in relay circuits and removing power from the trip solenoids. This system contains
no software voting, making the three PPRO modules completely independent. The only
link between PPRO and the other parts of the control system is the IONet cable, which
transmits status information.
Additional protection for simplex systems is provided by the protection module through
the Servo Terminal Board, TSVC. Plug J1 on TREG is wired to plug JD1 on TSVC, and
if this is energized, relay K1 disconnects the servo output current and applies a bias to
force the control valve closed.

3 Network Layers
The control system is based on a hierarchy of networks used to interconnect the
individual nodes. These networks separate the different communication traffic into layers
according to their individual functions. This hierarchy extends from the I/O modules and
controllers, which provide real-time control of the process, through the HMI, and up to
facility wide monitoring.
Ethernet is used for all data highways and the I/O network. Fiber is just the transmission
medium. The protocol is the same as the copper paths.Each layer uses industry standard
components and protocols to simplify integration between different platforms and
improve overall reliability and maintenance. The layers are designated as the enterprise,
supervisory, unit control, and IONet, and are described in the following sections.
Mark VIe Control as Part of Integrated Control System (ICS)
Network Layers GEH-6721Y System Guide 51

The Enterprise layer serves as an interface from specific process control into a
facility-wide or group control layer. This higher layer is provided by the customer. The
network technology used in this layer is generally determined by the customer and may
include either local area network (LAN) or wide area network (WAN) technologies,
depending on the size of the facility. The Enterprise layer is separated from other control
layers through a router, which isolates the traffic on both sides of the interface. Where
unit control equipment is required to communicate with a facility-wide or DCS system,
GE uses either a Modbus interface or a TCP/IP protocol known as GE Standard
Messaging (GSM).
The Supervisory layer provides operator interface capabilities such as coordination of the
HMI viewer and server nodes, as well as other functions like data collection (Historian),
remote monitoring, and vibration analysis. This layer may be used as a single or dual
network configuration. A dual network provides redundant Ethernet switches and cables
to prevent complete network failure if a single component fails. The network is known as
the Plant Data Highway (PDH).
Other fieldbus based devices The Control layer provides continuous operation of the process equipment. The
may not be restricted to EGD controllers on this layer are highly coordinated to support continuous operation without
data transfers. interruption. The controllers operate at a fundamental rate called the frame rate, which
can be between 6-100 Hz. These controllers use EGD to exchange data between nodes.
Various levels of redundancy for the connected equipment are supported by the
supervisory and control layers. This network is known as the Unit Data Highway (UDH).

The following figure displays network redundancy options.
Redundant Networks for Different Applications

3.1 Plant Data Highway (PDH)
On smaller systems, the PDH The PDH is the plant level supervisory network. The PDH connects the HMI server with
and the UDH may physically remote viewers, printers, historians, and external interfaces. The PDH has no direct
be the same network, as long connection to the control system, which communicate over the unit data highway (UDH).
as there is no peer-to-peer The media is UTP or fiber-optic Ethernet running at 10/100 megabits per second, using
control on the UDH. the TCP/IP protocol. Redundant cables are required by some systems, but these form part
of one single logical network. The hardware consists of two redundant Ethernet switches
with optional fiber-optic outputs for longer distances, such as to the central control room.
Using the Ethernet with the TCP/IP protocol over the PDH provides an open system for
third-party interfaces. The following figure displayed the equipment connections to the
PDH.
Typical Plant Data Highway Layout

PDH Network Features
Feature Description
Type of Network IEEE 802.3 Ethernet in a single or redundant star or ring configuration
Speed 100 megabit per second or with 1000 megabit per second trunks interconnecting switches
Media and Distance Ethernet 100Base-TX is used for switch to controller/device connections. Cable is CAT 5e compliant.
Distance is up to 100 m (328 ft). * Fiber-optic connections, Ethernet 100FX, 1000SX, 1000 LX are
used for distances of 2 km (1.24 mi), 550 m (1804.46 ft), and 5 km (3.11 mi), respectively.
Number of Nodes Up to 1024 nodes supported
Protocols Ethernet-compatible protocol, typically TCP/IP-based. Use GSM or Modbus over Ethernet for external
communications.
Message Integrity 32-bit cyclic redundancy code (CRC) appended to each Ethernet packet plus additional checks in
protocol used.
External Interfaces Various third-party interfaces are available; GSM and Modbus are the most common.
* Fiber-optic cable provides the best signal quality, completely free of electromagnetic interference (EMI) and radio frequency
interference (RFI). Large point-to-point distances are possible, and since the cable does not carry electrical charges, ground
potential problems are eliminated.

3.2 Unit Data Highway (UDH)
The current systems supply The UDH connects to the controller and communicates with the HMI or HMI/Data
UDH and PDH connections on Server. The network media is UTP or fiber-optic Ethernet. Redundant cable operation is
a common set of network optional and, if supplied, unit operation continues to function even if one cable is faulted.
switches and media trunks. Dual cable networks still comprise one logical network. Similar to the plant data highway
(PDH), the UDH can have redundant, separately powered network switches, and
fiber-optic communication. UDH command data can be replicated to three controllers.
The UDH Communicator transmits UDH data.
UDH Network Features
Feature Description
Type of Network Ethernet, full duplex, in a single or redundant star configuration
Media and Distance Ethernet 100Base-TX for switch to controller/device connections. The cable is 22 to 26 AWG
unshielded twisted pair; category 5e EIA/TIA 568 A/B. Distance is up to 100 m. Ethernet
100Base-FX with fiber-optic cable optional for distances up to 2 km (1.24 mi).
Number of Nodes At least 25 nodes, given a 25 Hz data rate. For other configurations, contact the factory.
Type of Nodes Supported Controllers, PLCs, operator interfaces, and engineering workstations
Protocol EGD protocol based on the UDP/IP
Message Integrity 32-bit CRC appended to each Ethernet packet plus integrity checks built into UDP and EGD
Time Sync. Methods Network time protocol (NTP), accuracy ±1 ms.
Refer to the section, UDH The UDH is an Ethernet-based network that provides direct or broadcast peer-to-peer
Communicator. communications between controllers and an operator/maintenance interface. It uses
Ethernet Global Data (EGD), which is a message-based protocol for sharing information
with multiple nodes based on UDP/IP. UDH network hardware is similar to the PDH
hardware. The following figure displays redundant UDH networks with connections to
the controllers and HMI servers.

Typical Unit Data Highway Layout

3.2.1 UDH Communicator
A UDH communicator is a controller selected to provide the panel data to that network.
This data includes both control signals (EGD) and alarms. Each controller has an
independent, physical connection to the UDH. If a UDH network fault where the
controller becomes isolated from its companion controllers, it assumes the role of UDH
communicator for that network fragment. For one panel there can be only one designated
controller, while there could be multiple UDH communicators. The designated controller
is always a UDH communicator.
When a controller does not receive external EGD data from its UDH connection, it may
request the data be forwarded across the IONet from another UDH communicator. One or
more communicators supply the data and the requesting controller uses the last data set
received. Only the external EGD data used in sequencing by the controllers is forwarded
in this manner.
3.2.2 Control Data Highway (CDH)

To configure a CDH, refer to A second UDH or redundant Ethernet Communication known as the Control Data
GEH-6700, ToolboxST User Highway (CDH) allows two separate controllers to communicate with each other. The
Guide for Mark VIe Control, CDH (second UDH) Ethernet port can be added to a control system currently having a
Chapter 2, section, Networks. single UDH Ethernet port. The following table displays options for hardware setup. When
more than two controllers need to communicate over the CDH, the controllers are
connected as listed below, but cables are not used. Network switches should always be
used.
First Second Hardware Setup

Controller Controller
Simplex Simplex Each controller connects though the second Ethernet port using a single cross-over
category 5 network cable.
Simplex Dual The simplex controller connects to the second Ethernet ports of both the <R> and
<S> controllers of the dual system using a category 5 network cable through a
network switch.
Simplex TMR The simplex controller connects to the second Ethernet ports of <R>, <S>, and <T>
controllers of the TMR system using a category 5 network cable through a network
switch.
Dual Dual The <R> and <S> controllers of each system connect using a category 5 network
cable through a network switch.
Dual TMR The <R> and <S> controllers of the dual system connect to the <R>, <S>, and <T>
controllers of the TMR system using a category 5 network cable through a network
switch.
TMR TMR The <R>, <S>, and <T> controllers of each system connect using a category 5
network cable through a network switch.
With the TMR and TMR configuration, the customer does not have to use the
network if all EGD exchanges run at frame rate.

Typical Control Data Highway with Two TMR Control Systems

3.3 UDH Devices
3.3.1 Mark Controller Family
Mark VIeS (UCSBS1A) Safety The Mark VIe controllers (UCSBHxx) are being applied to GE wind, hydro, gas, and
controller is used for steam turbines, and to complete power plant controls, including nuclear power plants. In a
safety-critical SIL applications. combined-cycle application, it provides a common control and protection system for the
gas turbines, steam turbine generators, heat-recovery steam generators (HRSG), and the
balance-of-plant (BOP) equipment. The EX2100e, LS2100e, and Mark Stat controllers
are the same hardware (UCSBHxx) as the Mark VIe controller, but with different
firmware and application. The same ToolboxST application is used for configuration of
the Mark controller family of products.
3.3.1.1 EX2100e Excitation Control

Refer to GEH-6781, EX2100e The excitation control system supplies dc power to the field of the synchronous generator,
Excitation Control User Guide. and controls the generator ac terminal voltage and/or the reactive volt-amperes by means
of the field current. The excitation control system is supplied in NEMA 1 freestanding
floor-mounted indoor type metal cabinets. The cabinet lineup consists of several cabinets
bolted together.
3.3.1.2 LS2100e Static Starter Control

The Static Starter control The Static Starter control is used to start a gas turbine by running the generator as a
cabinet is a ventilated NEMA 1 starting motor. The Static Starter control, the Mark VIe control, and the excitation control
freestanding enclosure made of system form an integrated static start system. The Mark VIe control supplies the run,
12-gauge sheet steel on a rigid torque, and speed setpoint signals to the Static Starter control, which operates in a closed
steel frame designed for indoor loop control mode to supply variable frequency power to the generator stator. The
mounting. excitation control system is controlled by the Static Starter control to regulate the field
current during startup.
Refer to GEH-6798, LS2100e The LS2100e Static Starter control is an adjustable speed ac drive system specifically
Static Starter Control User designed to start a gas turbine generator set. By operating the generator as a synchronous
Guide. motor, the static starter accelerates the turbine set according to a specific speed profile
that provides optimum starting conditions for the gas turbine. The LS2100e control
eliminates the need for separate starting hardware, such as an electric motor or diesel
engine, torque converters, and associated auxiliary equipment, thus opening up critical
space around the turbine base.
The LS2100e control contains a digital control that interfaces seamlessly with various
Mark control system devices, including the Human-machine Interface (HMI) and
Historian products. These devices communicate with each other over an Ethernet-based
data highway to form a fully integrated control system.
3.3.1.3 Mark Stat Control

In this application, the UCSBH4A controller is used to control a GE multi-megawatt wind
turbine power conversion system.

3.3.2 Human-machine Interface (HMI)
Typical Mark control system HMIs are computers running the Windows® operating
system with communication drivers for the data highways, WorkstationST application,
and CIMPLICITY graphical user interface (GUI). The operator initiates commands from
the real-time graphic displays, and views real-time turbine data and alarms. Detailed I/O
diagnostics and system configuration are available.
The HMI can be configured as a server or viewer, containing tools and utility programs. It
can be linked to one data highway, or redundant network interface boards can be used to
link the HMI to both data highways for greater reliability. The HMI can be cabinet,
control console, or table-mounted.
WorkstationST OPC servers collect data on the UDH and use the PDH to communicate
with HMI viewers. Multiple servers can be used to provide redundancy. Configuration
servers, Historian servers, and Alarm Servers are used for large system scaling.
Redundant data servers are optional, and if supplied, communication with the viewers
continues even if one server fails.
3.3.3 Power Conversion Controllers

GE Brilliance* solar inverter and legacy wind converter controls can reside on the Mark
control system UDH and are configured used a common ToolboxST application.

3.4 IONet
Communication between the controller(s) and the I/O modules is through the internal
IONet. This is a 100 MB UTP or fiber-optic Ethernet network available in single, dual,
and triple redundant configurations. EGD and other protocols are used for
communication. The I/O modules send their inputs to the controllers. The controllers send
their outputs to the I/O modules each frame.
The I/O networks (IONet) are IEEE 802.3 100 Megabits full duplex Ethernet networks.
All traffic on each IONet is deterministic UDP/IP packets. TCP/IP is not used. Each
network (red, blue, black) is an independent IP subnet. The IONet is limited to Mark VIe
qualified control devices, I/O devices, Ethernet switches, and cables.
Refer to GEH-6753, The networks are fully switched full-duplex preventing collisions that can occur on
NetworkST 3.0 for Mark VIe non-switched Ethernet networks. The switches also provide data buffering and flow
Controls Application Guide for control during the critical input scan. The IEEE 1588 standard for precision clock
more information. synchronization protocol is used to synchronize frame and time, the controllers, and the
I/O modules. This synchronization provides a high level of traffic flow control on the
networks.
Network communication between the controller and IONet has tightly synchronized
UDP/IP Ethernet packets. The synchronization is achieved using the IEEE 1588 standard
for precision clock synchronization protocol and special hardware/software on the
controller and I/O packs. The Ethernet switches have been qualified for minimum latency
and maximum throughput.
BPPx

3.4.1 Cabling and Specifications
Cable color-coding is used to reduce the chance for cross connecting. Use the following
cables or RJ-45 hoods:
• Red for IONet 1 (R network)

• Black for IONet 2 (S network)
• Blue for IONet 3 (T network)
Maximum IONet Distances Including Field Devices
IONet Specifications
Specification 100BaseTx 100BaseFx

IEEE specification 802.3u 802.3u
Wire speed 100 Mbps 100 Mbps
Cable type UTP Cat 5e Fiber (multi-mode and single-mode)
Connector type RJ-45 SC
Maximum length of a segment at full-duplex 100 m (328 ft) 2 km (6,600 ft)
Maximum taps per segment 2 2
Maximum packets per network 199 199
Maximum number of switches 2 2

Topology Star Star
3.4.2 IONet Switches

Only industrial grade switches that meet the codes, standards, performance, and
environmental criteria for industrial applications are used for the IONet. This also
includes an operating temperature of -30 to 65°C (-22 to 149 °F). Switches have
provisions for redundant 10 to 30 V dc power sources (200/400 mA) and can be DIN-rail
mounted. LEDs indicate the status of the IONet link, speed, activity, and duplex.

Use only GE-approved Ethernet switches in all control system
I/O networks. Unsupported switches can prevent I/O modules
from receiving controller outputs.
Caution
Approved IONet Switches
Ethernet Switch Part # Connections

IS420ESWBH1A 16 copper ports and 1 fiber port
IS420ESWBH2A 16 copper ports and 2 fiber ports
IS420ESWBH3A 16 copper ports
336A4940DNP508TX 8 copper ports
336A4940DNP516TX 16 copper ports
336A4940DNP509FX 8 copper ports and 1 fiber port
336A4940DNP517FX 16 copper ports and 1 fiber port
336A4940DNP508FXE2 6 copper ports and 2 fiber ports (single mode)
336A4940JEP001 Installed within the 1.x ESS wind turbine hub

336A4940JEP002 Installed within the 1.x wind turbine top box
336A4940JEP003 Installed within the 1.x wind turbine DTA

336A4940JEP004 Installed within the 2.x and 1.x non-ESS wind turbine hub
IONet is presently recommended to only pass through five switches in series when going
from I/O pack to main controller (refer to the following figure). Any configured IONet
port on a controller or I/O module is continuously sending data, providing immediate
detection of faulty network cables, switches, or board components. When a fault occurs, a
diagnostic alarm is generated in the controller or I/O module.

3.4.3 Addressing
IONet devices are assigned IP addresses through the DHCP servers in the controllers. The
Host ID presented to the DHCP server is based on the board type and serial number
information stored on a serial EEPROM located on the terminal board. Since the Host ID
is part of the terminal board, the I/O module can be replaced without having to update the
ToolboxST application or controller communication IDs.
Note When a terminal board is replaced, the user must associate the new Host ID to the
configured device. The ToolboxST application presents a list of unrecognized devices that
have requested IP addresses to simplify this process.
IONets are class C networks. Each is an independent network with different subnet
addresses. The IONet IP host addresses for the controllers are fixed. The IP addresses of
the I/O packs are assigned by the ToolboxST application and the controller automatically
distributes the addresses to the I/O packs through a standard Dynamic Host Configuration
Protocol (DHCP) server in the controllers.

3.4.4 Shared IONet
A control set is the group of Beginning with ControlST* V04.06, sharing data between two control sets on a single
controllers (based on Ethernet input/output network (IONet) is available for some Mark* controllers. The
redundancy) with the set of owner controller allows for the configuration of the owned I/O modules, writes outputs,
owned I/O modules. From the reads SOEs, and provides diagnostic information. Owned I/O modules are attached to
ToolboxST* System Editor their owner controller that can configure and write to them, and obtain their IP addresses
Summary View, a control set from their owner controller. Outputs from controllers are received by their owned I/O
displays as a single controller. modules (not shared I/O modules).
A shared I/O module sends field device inputs to both its owner controller and to the
consumer controller. The consumer controller receives the field device inputs from the
shared I/O modules that are owned by the other owner controller. Configuration of the
Refer to GEH-6812, Mark control sets is managed with the ToolboxST application. The computer with the
Controllers Shared IONet User ToolboxST application communicates with the I/O devices through a software gateway
Guide for more information. function residing in the controllers.

3.5 External communication links
External communication links are available to interface with third-party plant controls
(DCS) or devices. This allows operators to have access to real time data, and provides for
discrete and analog commands to be passed to the Mark VIe controller. The Mark VIe
control system can be linked to third-parties in several different ways.
Type of controller processor • OPC UA direct from the Mark VIe controller
effects idle time.
• OPC UA, DA, AE from the WorkstationST server
• Serial Modbus® slave link from the WorkstationST server using the computer
RS-232C port
• Ethernet Modbus Slave direct from the Mark VIe controller to the third-party device
(Ethernet to serial converter device may be used)
• GSM from the WorkstationST server to the DCS.
GEDS Standard Messages (GSM) is a proprietary 100 mbps Ethernet link using TCP/IP.
It supports turbine control commands, Mark VIe control data and alarms, the alarm
silence function, logical events, and contact input sequence of events records with 1 ms
resolution. Ethernet GSM has the advantage of tighter system integration.
OPC UA
Modbus
GSM
WorkstationST Server
PDH
Ethernet
U CS BH1 A
Serial Modbus
UDH
Ethernet
OPC UA Ethernet
Modbus
CDH
Mark VIe Control System Links to Third-party Devices

4 Communication Protocols
4.1 Ethernet GSM
The WorkstationST server is Some applications require transmitting alarm and event information to third-party DCS.
the source of the Ethernet GSM This information includes high-resolution local time tags in the controller for alarms (25
communication. Hz), system events (25 Hz), and SOEs for contact inputs (1 ms). An available Ethernet
link, using TCP/IP, transmits data with the local time tags to the plant level control. The
link supports all alarms, events, and SOEs in the control cabinet. GE supplies an
application layer protocol called GSM, which supports four classes of application level
messages.
4.1.1 GSM Messages

Administration Messages are sent from the HMI to the DCS with a Support Unit
message, describing the systems available for communication on that specific link, and
general communication link availability.
Event Driven Messages are sent from the HMI to the DCS spontaneously when a system
alarm or system event occurs or clears, or a contact input (SOE) closes or opens. Each
logic point transmits with an individual time tag.
Periodic Data Messages are groups of data points, defined by the DCS and transmitted
with a group time tag. All of the 5000 data points in the Mark control are available for
transmission to the DCS at periodic rates down to 1-second. One or multiple data lists can
be defined by the DCS using controller names and point names.
Common Request Messages, including turbine control commands and alarm queue
commands, are sent from the DCS to the Mark VIe control system HMI. Turbine control
commands include momentary logical commands such as raise and lower, start and stop,
and analog setpoint target commands. Alarm queue commands consist of silence, plant
alarm horn, and reset commands as well as alarm dump requests causing the entire alarm
queue to be transmitted from the Mark VIe control system to the DCS.
Communication Protocols GEH-6721Y System Guide 69

4.2 OPC
http://www.opcfoundation.org OPC protocol is used by runtime databases or third-party interfaces. Fundamentally, the
OPC standard defines two software roles, OPC clients and OPC servers. In general,
clients are consumers of automation information and servers are producers of the same
information.
OPC Unified Architecture OPC is a technology standard initially developed by a group of automation industry
(UA) combines OPC DA, AE, companies and now managed by the not-for-profit organization called the OPC
and HDA into one interface. Foundation. The OPC standard provides a common de-coupling mechanism for
automation system software components, which allows for simpler integration of these
components from multiple vendors.
The Mark VIeS Safety With the Mark VIe controller firmware V05.01 or later, an OPC UA server can run
controller and Mark VIe directly from the controller. The number and type of controller application variables, type
Virtual controller do not of controller processor, and the number of and sample rate of connected third-party clients
directly support OPC UA. effect the idle time (CPU usage) of the controller. From the ToolboxST Component Editor
General tab, press F1 for help on this feature, including examples of usage data.
For using OPC with the WorkstationST server, refer to the following documents.
GEI-100621 WorkstationST OPC DA Server

GEI-100624 WorkstationST OPC AE Server
GEI-100828 WorkstationST OPC UA Server
The sections: How To Interface to Third Parties Using WorkstationST OPC DA
GEH-6808
How to Configure OPC AE Capability

4.3 Modbus
http://www.modbus.org Modbus is a standard and widely used protocol for exchanging real time data and
commands between third-party DCS equipment and Mark VIe control system equipment.
Modbus terminology uses Master and Slave device(s). The Master routinely polls each
†Retrieved Nov 21, 2013 from field device (Slave), detecting changes in the data. This continuous detection method does
http://en.wikipedia. consume bandwidth, so configuration of the Modbus application should take this into
org/wiki/Modbus consideration to avoid network lag. In addition, Slave devices must be able to buffer data
so that it is made available at anytime the Master device tries to detect it. †“Modbus
protocol itself provides no security against unauthorized commands or interception of
data.” Using a separate gateway for Modbus rather than a shared resource is a valid
consideration when designing the control system.
4.3.1 Mark VIe Controller Ethernet Modbus Slave

The Mark VIe controller directly supports Ethernet Modbus as a standard Slave interface.
Ethernet establishes high-speed communication between the various portions of the
control system, and the Ethernet Modbus protocol is layered on top of the TCP/IP stream
sockets. The primary purpose of this interface is to allow a third-party Modbus Master
computer or DCS to read and write signals that exist in the controller, using a subset of
the Modbus function codes. The control system will respond to Ethernet Modbus
commands received from any of the Ethernet ports supported by its hardware
configuration.
This Modbus communication link would allow an operator at a remote location to make
an operator command by sending a logical command or an analog setpoint to the
controller. Logical commands are used to initiate automatic sequences in the controller.
Analog setpoints are used to set a target, such as turbine load, and initiate a ramp to the
target value at a ramp rate predetermined by the application software.
To configure a controller's Modbus Slave Holding Register and/or a Holding Coil to

accept a Write command from a Modbus Master, the External Access property of the
connected variable assigned to the targeted Modbus Slave address must be configured as
Read/Write. From the ToolboxST Component Editor, Modbus tab, press F1 for help on
this feature.
4.3.2 PSCA and PSCH Modbus Masters

Refer to GEH-6721_Vol_II for The PSCA I/O module can provide a Modbus master for Ethernet TCP/IP or serial link.
more information. The PSCH I/O module provides a specialized form of Modbus master (PODbus) used in
GE Drilling equipment.
4.3.3 WorkstationST Modbus

Refer to GEI-100696, In the Mark VIe control system, a computer running the WorkstationST Modbus feature
WorkstationST Modbus for can provide a Modbus Master or Modbus Slave interface using Ethernet or serial links. It
more information. is possible to have serial and Ethernet Masters and Slaves all running at the same time,
within the limits of the computer used. Refer to GEH-6746, Testing Third-party Modbus
Data Links with ControlST Software Suite for more information.

4.4 Ethernet Global Data (EGD)
The Ethernet Global Data (EGD) allows sharing of information between controller
components over the IONet and UDH. Controller data configured for transmission over
EGD is separated into groups called exchanges. Multiple exchanges make up pages.
Pages can be configured either to a specific address (unicast), if supported, or to multiple
consumers at the same time (broadcast or multicast), if supported.
Each page is identified by the combination of a Producer ID and an Exchange ID. The
consumer recognizes the data and knows where to store it. EGD allows one controller
component, referred to as the producer of the data, to simultaneously send information at
a fixed periodic rate to any number of peer controller components, known as the
consumers. This network supports a large number of controller components capable of
both producing and consuming information.
The exchange contains a configuration signature, which displays the revision number of
the exchange configuration. If the consumer receives data with an unknown configuration
signature, it makes that data unhealthy.
If a transmission is interrupted, the receiver waits three periods for the EGD message,
after which it times out and the data is considered unhealthy. Data integrity is preserved
by the following:
• 32-bit cyclic redundancy code (CRC) in the Ethernet packet

• Standard checksums in the UDP and IP headers
• Configuration signature
• Data size field

EGD Communications Features
Feature Description
Type of Communication Supervisory data is transmitted periodically at either 480 or 960 ms. Control data is transmitted
at frame rate.
Message Type Broadcast - a message to all stations on a subnet
Unicast - a directed message to one station
Redundancy Pages may be broadcast onto multiple Ethernet subnets or may be received from multiple
Ethernet subnets, if the specified controller hardware supports multiple Ethernet ports.
Fault Tolerance In TMR configurations, a controller can forward EGD data across the IONet to another
controller that has been isolated from the Ethernet.
Sizes An exchange can be a maximum of 1400 B. Pages can contain multiple exchanges. The
number of exchanges within a page and the number of pages within an EGD node are limited
by each EGD device type. The Mark VIe controller does not limit the number of, exchanges, or
pages.
Message Integrity Ethernet supports a 32-bit CRC appended to each Ethernet packet.
Reception timeout is determined by EGD device type. The exchange times out after an
exchange update had not occurred within four times the exchange period, using Sequence ID.
Missing/out of order packet detection
UDP and IP header checksums
Configuration signature (data layout revision control)
Exchange size validation
Function Codes EGD allows each controller to send a block of information to, or receive a block from, other
controllers in the system. Integer, Floating Point, and Boolean data types are supported.
In a TMR configuration, each controller receives UDH/EGD data independently from a

direct Ethernet connection. If the connection is broken, a controller can request the
missing data from the second or third controller through the IONet.
The Device Manager Gateway performs TCP exchanges in its configuration and device
communications. The EGD protocol also applies TCP for configuration messages and
exchanges. Class 1 exchanges are not synchronized by 1588 Synchronization and Class 2
exchanges occur between frames. Flow control is provided only between network
switches.
One controller in a TMR configuration is automatically selected to transmit the EGD data
onto the UDH. If the UDH fractures, causing the controllers to be isolated from each
other onto different physical network segments, multiple controllers are enabled for
transmission. These provide data to each of the segments. These features add a level of
Ethernet fault tolerance to the basic protocol.

Unit Data Highway EGD TMR Configuration
In a dual network configuration, each controller receives UDH/EGD data independently

from a direct Ethernet connection. If the connection is broken, a controller may request
the missing data from the second through the IONet.
One controller in a dual network configuration is automatically selected to transmit the

EGD data onto the UDH. If the UDH fractures causing the controllers to be isolated from
each other onto different physical network segments, each controller is enabled for
transmission, providing data to both segments.
4.5 Network Time Protocol (NTP)

NTP is used to synchronize computer system clocks over packet-switched,
variable-latency data networks. It is designed to resist the effects of variable latency by
using a jitter buffer. NTP uses UDP on port 123.
NTP uses the Marzullo’s algorithm, and includes support for features such as leap
seconds. NTPV4 can usually maintain time to within 10 ms on the internet, and achieve
accuracies of 200 microseconds or better in local area networks. It provides Coordinated
Universal Time (UTC). No information about time zones or daylight saving time is
transmitted and must be obtained separately.
For modern Unix system, the NTP client is implemented as a daemon process that runs
continuously in user space (ntpd). Because of sensitivity to timing, however, it is
important to have the standard NTP clock phase-locked loop implementation in kernel
space. For QNX, in the Mark VIe controller, ntpd runs in kernel space.

4.5.1 Time Synchronization
The time synchronization option synchronizes all turbine controls, generator controls, and
HMIs on the UDH to a Global Time Source (GTS) or master time source. Typical GTS
systems are Global Positioning Satellite (GPS) receivers such as the StarTime GPS Clock
or similar time processing hardware. The preferred time sources are Coordinated
Universal Time (UTC) or GPS.
A time/frequency processor board is placed in the HMI. This board acquires time from
the master time source with a high degree of accuracy. When the HMI receives the time
signal, it makes the time information available to the turbine and generator controls on the
network by way of NTP. The HMI server provides time-to-time slaves either by
broadcasting time, or by responding to NTP time queries, or both methods.
Supplying a time/frequency processor board in another HMI server as a backup can

provide redundant time synchronization. Normally, the primary HMI server on the UDH
is the time master for the UDH, and other computers without the time/frequency board are
time slaves. The time slave computes the difference between the returned time and the
recorded time of request and adjusts its internal time. Each time slave can be configured
to respond to a time master through unicast mode or broadcast mode.
Local time is used for display of real time data by adding a local time correction to UTC.
A node’s internal time clock is normally UTC rather than local. This is done because
UTC time steadily increases at a constant rate while corrections are allowed to local time.
Historical data is stored with global time to minimize discontinuities.
4.5.1.1 Redundant Time Sources

If the master time source or GTS becomes inoperative, the backup is to switch the time
board to flywheel mode with a drift of ±2 ms/hour. In most cases, this allows sufficient
time to repair the master time source without severe disruption of the plant’s system time.
If the time master becomes inoperative, then each of the time slaves picks the backup
time master. This means that all nodes on the UDH lock onto the identical reference for
their own time even if the primary and secondary time masters have different time bases
for their reference. If multiple time masters exist, each time slave selects the current time
master based on whether or not the time master is tracking the master time source, which
time master has the best quality signal, and which master is listed first in the
configuration file.

4.5.1.2 Selection of Time Sources
The time synchronization software does not support all time sources supported by the
time board. A list of time sources supported by both the time board and the time
synchronization software includes:
• Modulated IRIG-A, IRIG-B, 2137, or NASA-36 timecode signals

− Modulation ratio 3:1 to 6:1
− Amplitude 0.5 to 5 V peak-to-peak
• Dc level shifted modulated IRIG-A, IRIG-B, 2137, or NASA-36 timecode signals
− TTL/CMOS compatible voltage levels
• 1PPS (one pulse per second) using the External 1PPS input signal of the BC620AT
board
− TTL/CMOS compatible voltage levels, positive edge on time
• Flywheel mode using no signal, using the low drift clock on the BC620AT board
− Flywheel mode as the sole time source for the plant
4.5.2 Clock Stratum

This stratum is different from The term Stratum defines the levels in the hierarchy of clocks that makeup NTP. Each
the clock strata used in level is assigned a layer number starting with zero at the top. The stratum level defines its
telecommunication systems. distance from the reference clock and prevents cyclical dependencies in the hierarchy.
Note Stratum is not an indication of the quality or reliability, it is common to fine

Stratum 3 time sources that are higher quality than other Stratum 2 time sources.
Stratum 0 are devices such as atomic (cesium, rubidium) clocks, GPS clocks, or other
radio clocks. Stratum 0 devices are usually not attached to the network. Instead, they are
locally connected to computers (for example, through an RS-232 connection using a pulse
per second signal).
Stratum 1 are computers attached to Stratum 0 devices. Normally they act as servers
for timing requests from Stratum 2 servers through NTP. These computers are also
referred to as time servers.
Stratum 2 are computers that send NTP requests to Stratum 1 servers. Normally a
Stratum 2 computer will reference a number of Stratum 1 servers and use the NTP
algorithm to gather the best data sample, dropping any Stratum 1 servers that are wrong.
Stratum 2 computers are grouped with other Stratum 2 computers to provide more stable
and robust time for all devices in the peer group. Stratum 2 computers normally operate
as servers for Stratum 3 NTP requests.
Stratum 3 are computers that use exactly the same NTP functions of peering and data
sampling as Stratum 2, and can be used as servers for lower strata. NTP support up to 256
strata, depending on the version of NTP protocol in use.

4.5.3 NTP Timestamps
The current NTPv4 format The 64-bit timestamps used by NTP consist of a 32-bit seconds part and a 32-bit
supports Era Number and Era fractional second part, giving NTP a time scale of 232 seconds (136 years) and a
Offset, which corrects date theoretical resolution of 2-32 seconds (233 picoseconds). The timescale wraps around
rollover issues. every 232 seconds (136 years). NTP uses an epoch of January 1, 1900. The first rollover
will occur in 2036, prior to the UNIX Year 2038 problem.
Implementations should disambiguate NTP time using a knowledge of the approximate

time from other sources. Since NTP only works with the differences between timestamps
and never their absolute values, the wraparound is invisible as long as the timestamps are
within 68 years of each other. This means that the rollover will be invisible for most
running systems, since they will have the correct time to within a very small tolerance.
However, systems that are starting up need to know the date within no more than 68
years. The Mark VIe control uses a battery powered hardware clock to avoid this
problem.
4.5.4 Clock Synchronization Algorithm

To synchronize its clock with a remote server, the NTP client must compute the
round-trip delay time. The round-trip delay = (t3 - t0) - (t2- t1).
The time of the request packet transmission is t0, the time of the packet reception is t1, the
time of the response packet transmission is t2, and the time of the response packet
reception is t3. The elapsed time on the client side between the emission of the request
packet and the reception of the response packet is t3 - t0. The time the server waited before
sending the answer is t2 - t1.
The offset = ((t1 - t0) + (t2- t3)) / 2.
The NTP synchronization is correct when both the incoming and outgoing routes between
the client and the server have a symmetrical nominal delay. If the routes do not have a
common nominal delay, the synchronization has a systematic bias of half the difference
between the forward and backward travel time.
4.5.5 Types of Clients and Servers

The relationship between NTP servers and clients can be configured to operate in several
ways. Computers using NTP can operate in different modes with respect to different
machines. For example, a single machine could be a client of a machine with a lower
stratum number, while being a peer to a machine on the same stratum, and a broadcast
server to a number of clients at higher stratum numbers.
Servers provide time to clients. Clients send requests to the server and the server sends
back a time stamped response, along with information such as accuracy and stratum.
Clients get time responses from a NTP server or servers, and uses the information to
calibrate its clock. This consists of the client determining how far its clock is off and
adjusting its time to match that of the server. The maximum error is determined based on
the round-trip delay time for the packet to be received.
Peers are members of a group of NTP servers that are tightly coupled. In a group of
two peers, at any given time, the most accurate peer is acting as a server and the other
peers are acting as clients. The result is that peer groups will have closely synchronized
times without requiring a single server to be specified.

4.5.5.1 Broadcast/Multicast
The NTP server can also operate in a broadcast or multicast mode. Broadcast servers send
periodic time updates to a broadcast address, while multicast servers send periodic
updates to a multicast address. Using broadcast packets can greatly reduce the NTP traffic
on a network, especially for a network with many NTP clients.
The NTP broadcast or multicast client listens for NTP packets on a broadcast or multicast
address. When the first packet is received, it attempts to quantify the delay to the server to
better quantify the correct time from later broadcasts. This is accomplished by a series of
brief interchanges where the client and server function as a regular (non-broadcast) NTP
client and server. Once these interchanges occur, the client has an idea of the network
delay and can estimate the time based only on broadcast packets. If this interchange is not
desirable, it can be disabled using NTP’s access control features. The -r option can be
used when xntpd is started to hardwire a delay if the interchange fails because of access
control issues or other problems.
4.5.6 Accuracy and Resolution

NTP may take several minutes or even hours to adjust a system's time to the ultimate
degree of accuracy. There are several reasons for this. NTP averages the results of several
time exchanges to reduce the effects of variable latency, so it may take several minutes for
NTP to even reach consensus on what the average latency is. Generally this happens in
about five minutes. In addition, it often takes several adjustments for NTP to reach
synchronization. Users should not expect NTP to immediately synchronize two clocks.
The ntpdate command can be used if instant synchronization is needed. The peers
command can be used in ntpq to determine if synchronization has been achieved. When a
client has synchronized, the synchronization server is listed with an asterisk in front of it.
To allow clocks to quickly achieve high accuracy, yet avoid overshooting the time with
large time adjustments, NTP uses a system where large adjustments occur quickly and
small adjustments occur over time. For small time differences (less than 128 ms), NTP
uses a gradual adjustment. This is called slewing. For larger time differences, the
adjustment is immediate. This is called stepping. If the accuracy of the clock becomes too
insufficient (off by more than 17 minutes), NTP aborts the NTP daemon, with the
assumption that something is wrong with either the server or client. To accurately
synchronize with a server, the client needs to avoid step adjustments.
The degree of synchronization to a server is dependent primarily on network latency.

Because NTP uses UDP packets, traffic congestion could temporarily prevent
synchronization, but the client can still self-adjust, based on its historic drift. Under good
conditions on a LAN without too many routers or other sources of network delay,
synchronization to within a few milliseconds is normal. Anything that adds latency, such
as hubs, switches, routers, or network traffic, will reduce this accuracy.
If even more synchronization accuracy is required, use the following options:
• Connecting directly to a reference clock. Then, accuracy is limited only by the

accuracy of the reference clock and the hardware and software latencies involved in
these connections.
• Clocks can use pulse per second (PPS) radio receivers, which receive on-the-second
radio pulses from a national standards organization. If the time is within a fraction of
a second, the PPS pulses can be used to precisely synchronize to the tick of the
second. The method achieves accuracies in the tens of microsecond range.

4.5.7 Number of Time Servers
The NTP algorithms for selecting good time servers (truechimers) and separating them
from bad ones (falsetickers) are complex. The algorithms systematically analyze the
currently remaining servers to determine if one of them is statistically an outlier. David L
Mills (the creator of NTP) defines a statistical outliner as insane. The algorithm then
eliminates the insane server, and the cycles repeats. Once all the insane servers are
eliminated, the remaining sane servers go through a similar process.
Once down to the minimum sane servers, the system considers these to be the candidates
for selection as the One True Clock. NTP will then sync to this clock. By default the
minimum required number of good servers (minsane) is three, and the minimum required
numbers of candidates (minclock) is one. However, this has been known to have very
undesired consequences. The NTP Byzantine algorithm needs four sources so that, if one
of them turns falsetick, the remaining three truechimes can vote it out. The recommended
value for minsane is four and minclock is four, and two less than the total number of
servers.
The Mark VIe control’s NTP has a minsane of two and a minclock of one. The minimum
number of servers is three, and four servers would increase the chances of sane servers.
Also, the NTP client of the designated controller (dual or TMR system) drives the time
for the entire system. The non-designated controllers track the designated controller. It is
possible that the NTP status viewer connected to a non-designated controller will not
display the actual time in the devices. However, the time will be correct if that controller
becomes designated.

4.6 FOUNDATION Fieldbus
Refer to GEH-6761, The Mark* VIe control FOUNDATION fieldbus™ interface is a fieldbus protocol based on
FOUNDATION Fieldbus international standards and designed for applications in manufacturing, process
Application Guide and automation, and buildings automation. The guidelines for this fieldbus standard are
GEH-6762, FOUNDATION published by the Fieldbus Foundation™.
Fieldbus User Guide for more
information. FOUNDATION fieldbus technology provides a standardized communications and controls
system. There are a variety of manufacturer’s components that are certified as compatible
with fieldbus technology and therefore can be interchanged for a competitor’s similar
component. This allows GE customers to use a wider variety of equipment in the Mark
VIe control system.
Refer to GHT-200069, How to The ability to replace a certified device from one manufacturer with a certified device
Qualify a FOUNDATION Fieldbus from another manufacturer (interoperability) is made possible by the fact that devices and
Field Device. software are conforming to the same standard. The Fieldbus Foundation tests and
registers the devices to ensure interoperability of registered instruments from multiple
vendors. This enables the end user to select the best instruments for the application
regardless of the host system supplier. Additional compatibility testing for Mark VIe
control applications has been performed by GE. Devices that have been tested have their
device definition (DD) files included in the ToolboxST* application release. If additional
devices are required they can be added to the system. Compatibility testing guidelines are
provided in the How To Guide section of the ToolboxST documentation.
Implementing FOUNDATION fieldbus technology requires the following:
• ControlST* Software Suite Version 04.03 or higher

• ToolboxST Application Version 04.03 or higher
• CIMPLICITY* Advanced Viewer
Benefits of FOUNDATION fieldbus technology include:
• Reduced wiring
• Multi-variables from a single multi-channel field instrument
• Simpler integration
• Easier maintenance
• Device diagnostics
Ultimately, FOUNDATION technology can be the key to greater flexibility and productivity.
This can be achieved by predictive maintenance scheduling and improved upkeep enabled
by the diagnostics, performance analysis data, and operational statistics available.

4.7 PROFIBUS
Refer to GEH-6823, Mark VIe The Mark* VIe control PROFIBUS® interface is a fieldbus protocol based on
Control PROFIBUS Interface international standards and designed for applications in manufacturing, process
Application Guide automation, and building automation. The guidelines for this fieldbus standard are
published by PROFIBUS International and can be found at http://www.profibus.com.
PROFIBUS technology provides a standardized communication interface for control

systems and enables the customer to install components from various manufacturers as
they deem necessary. There are a variety of manufacturer’s components that are certified
as compatible with PROFIBUS technology and therefore can be interchanged for a
competitor’s similar component. This allows GE customers to use a wider variety of
equipment in the Mark VIe control system.
The ability to interchange a certified device from one manufacturer with a certified device
from another manufacturer (interoperability) is made possible by the fact that devices and
software are conforming to the same standard. PROFIBUS International tests and
registers the devices to ensure interoperability of registered instruments from multiple
vendors. This enables the end user to select the best instruments for the application
regardless of the host system supplier.
The PROFIBUS Master Gateway (PPRF) I/O module has been available for the Mark VIe
control system since 2008. The PPRF module has continued to increase in functionality
and internal component upgrades. The addition of PROFIBUS DPV1 messaging for
device management is available in ControlST* V04.06 or higher.
Benefits of PROFIBUS technology include:
• Reduced wiring
• Multi-variables from a single multi-channel field instrument
• Simpler integration
• Easier maintenance
• Device diagnostics
Ultimately, PROFIBUS technology can be the key to greater flexibility and productivity.
This can be achieved by predictive maintenance scheduling and improved upkeep enabled
by the diagnostics, performance analysis data, and operational statistics available.
4.8 CANopen
Refer to GEH-6721_Vol_II, the Mark VIe control systems offer a wide range of native I/O types and I/O bus solutions for
chapter PCNO CANopen flexible integration of instrumentation. This includes a CANopen Master Gateway for
Master Gateway. Woodward GS6/16 fuel metering valves on gas turbines. The valve can be applied as a
single valve (single manifold base turbines) or in a multiple valve configuration (dry low
emission turbines). The CANopen Master Gateway (PCNO) complies with the EN
50325-4 standard for embedded control systems. It includes the application layer, and
communication, application, device, and interface profiles. The protocol specifications are
developed and maintained by the Controller Area Network (CAN) in Automation
standards organization comprising 500 companies.

Notes

5 Technical Regulations, Standards,
and Environment
This chapter describes the technical regulations, standards, and environmental guidelines
used for the design of all printed circuit boards, modules, core components, panels, and
cabinet line-ups in the control system. Requirements for harsh environments, such as
marine applications, are not covered here.
5.1 Safety Standards

EN61010-1:2010 (3rd Edition) Safety Requirements for Electrical Equipment for Measurement, Control, and
Laboratory Use, Part 1: General Requirements
CAN/CSA® 22.2 No. 61010-1-12 Safety Requirements for Electrical Equipment for Measurement, Control, and
Laboratory Use, Part 1: General Requirements
UL 61010-1 (3rd Edition) Safety Standard for Electrical and Electronic Test, Measuring, Controlling, and
Related Equipment – General Requirements
IEC® 60529 Intrusion Protection Codes IP20 minimum (NEMA 1)
Technical Regulations, Standards, and Environment GEH-6721Y System Guide 83

5.2 Conditions for Compliance
If the following conditions for compliance are not met or if unapproved third-party equipment is included in the Mark VIe
control panel, then the user is responsible for obtaining the appropriate Low Voltage Safety and EMC certifications for the
assembled Mark VIe control & IO based panels.
• Mark VIe control equipment must be mounted inside a grounded steel enclosure, with doors that require a tool or key to
open, and 0.86 mm minimum steel thickness. The enclosure must provide a minimum Intrusion Protection of IP 20 and
an internal micro-environment of not more than Pollution Degree 2.
• PE and FE connections must be clearly marked. Customer must connect PE/FE to suitable building ground system
through minimum 120 mm2 (4/0 AWG) gauge wire. Refer to the chapter Installation Guidelines, the section Grounding
for more information.
• Use only Mark VIe family of controllers, IO, switches, and power supplies.
• Customer power supply mains connection terminal boards must be clearly marked with L (Line) and N (Neutral) for each
AC supply feed connection and Hi (+) and Lo (-) for each DC supply feed connection.
• A Power Requirements nameplate with supply source designations, voltage, and rated current shall be located on the
front door of the cabinet with the customer supply mains connections. Refer to the chapter Installation Guidelines, the
section Power Requirements for details and nameplate examples.
• The customer shall provide an easily accessible external disconnect device for each of the mains supplies near the control
panel. The customer shall provide external 30 A two-pole circuit breaker protection for each 120 V ac and 125 V dc
mains and 15 A two-pole circuit breaker protection for each 240 V ac and 220 V dc mains. Circuit breaker can serve as
the Disconnect Device if mounted accessible to the control panel.
• Any accessory outlet / socket must be labeled near the outlet with the max rated current.
• All AC and DC power supply mains must connect thru a Mark VIe Overvoltage Transient Protection and EMI Filter
circuit. These OV and EMI filter circuits are built-in to the JPDB and JPDF Power Distribution Modules. If JPDB/JPDF
are not used to distribute AC and DC power supply mains to the Mark VIe control, then a separate GE Filter Module
246B8279Gx should be used to filter the mains. Refer to GEH-6721 Volume II, the chapter PDM Power Distribution
Modules for more information.
• Elevation shall not exceed 2000 m for compliance to 61010-1.
• Appropriate Warning nameplates shall be applied to the front door of each panel cabinet and shall include appropriate
warning symbols per IEC 61010-1 per Table 1. See examples below. Warning nameplates shall highlight the presence of
electrical circuits that must be disconnected before opening the enclosure for servicing, electrical shock or burn hazard,
Qualified Personnel Only, and include symbols 12 and 14 from IEC 61010-1 Table 1.
! WARNING ! DANGER
This e quipme nt ma y re ce ive e le ctrica l HIGH VOLTAGE
e ne rgy from more tha n one s ource . HAZARD OF ELECTRICAL
S HOCK OR BURN
Additiona l dis conne cts a re loca te d
336A3551P 1, Re v B
outs ide this ca bine t. Ope n a ll REMOVE P OWER FROM

ALL S OURCES BEFORE
a s s ocia te d dis conne cts be fore OP ENING COVERS
s e rvicing e quipme nt. Re fe r to
QUALIFIED
e quipme nt dia gra ms .
P ERS ONNEL ONLY
Complie s with ANS I Z535, IS O 3864. 323A5701P 1, Re v B Complie s with ANS I Z535, IS O 3864.

5.3 Electrical
5.3.1 Electromagnetic Compatibility Directive (EMC)
2004/108/EC
Equipment is not approved for use in a residential,
commercial or light industrial environment and should not be
connected to a residential electric power network. For EMC
Directive compliance, Mark VIe components shipped loose
from the factory must be installed in an enclosure with a
minimum steel thickness of 0.86 mm and have a minimum
Attention
Intrusion Protection (IP) of 20.
The Mark VIe control fulfils the requirements listed in the following table.
Code Description
EN 55011:2009 + A1:2010 ISM equipment - Electromagnetic disturbance characteristics
EN 61000-6-2: 2005 Generic Immunity Industrial Environment
IEC 61000-4-2 Electrostatic Discharge Susceptibility
IEC 61000-4-3 Radiated RF Immunity
IEC 61000-4-4 Electrical Fast Transient Susceptibility
IEC 61000-4-5 Surge Immunity
IEC 61000-4-6 Conducted RF Immunity
IEC 61000-4-11 Voltage Variation, Dips and Interruptions
5.3.2 Low Voltage Directive 2006/95/EC

Under the conditions specified in this document, the Mark VIe control fulfils the
requirements of CAN/CSA-C22.2 No. 61010-1-12, UL Std. No. 61010-1 (3rd Edition),
and EN 61010-1 (3rd edition) Safety Requirements for Electrical Equipment for
Measurement, Control, and Laboratory Use, Part 1: General Requirements.
The protection provided by this equipment may be impaired if

it is used in a manner that is not specified by the manufacturer.
Warning

5.3.3 Supply Voltage
5.3.3.1 Line Variations

Mark VIe control equipment meets the requirements for Overvoltage Category II
equipment (IEC 60664-1:2007) under the Conditions for Compliance specified in this
document.
Ac Supplies – Operating line variations of ±10%

IEEE STD 141-1993 defines the Equipment Terminal Voltage – Utilization voltage.
The above meets IEC 60204-1 2005, and exceeds IEEE STD 141-1993, and ANSI
C84.1-1989.
Dc Supplies – Operating line variations of -30%, 10% or 140 V dc. This meets IEC
60204-1 2005.
5.3.3.2 Voltage Unbalance

Less than 2% of positive sequence component for negative sequence component
Less than 2% of positive sequence component for zero sequence components
This meets IEC 60204-1 2005 and IEEE STD 141-1993.
5.3.3.3 Harmonic Distortion Voltage Unbalance

Voltage: Less than 10% of total rms voltages between live conductors for 2nd through 5th
harmonic
Additional 2% of total rms voltages between live conductors for sum of 6th through 30th
harmonic
This meets IEC 60204-1 2005.
Current: The system specification is not per individual equipment
Less than 15% of maximum demand load current for harmonics less than 11
Less than 7% of maximum demand load current for harmonics between 11 and 17
Less than 6% of maximum demand load current for harmonics between 17 and 23
Less than 2.5% of maximum demand load current for harmonics between 23 and 35
The above meets IEEE STD 519 1992.
5.3.3.4 Frequency Variations

Frequency variation of ±5% when operating from ac supplies (20 Hz/sec slew rate)
This exceeds IEC 60204-1 2005.
5.3.3.5 Surge
Withstand 2 kV common mode, 1 kV differential mode
This meets IEC 61000-4-5 (ENV50142), and ANSI C62.41 (combination wave).

5.4 Environment
5.4.1 Temperature Considerations
Mark VIe control electronics can be packaged in a variety of different configurations and
designed for different environmental conditions. Proper thermal considerations for active
electronics with heat sensitive components must be considered for electronics packaging.
Refer to the table, Mark VIe For internal enclose design considerations, most Mark VIe components have an ambient
Equipment with Restrictive temperature rating of -30 to 65°C (-22 to 149 °F). The allowable temperature change
Ambient Ratings. without condensation is ±15°C (59 °F) per hour. It is recommended that the environment
be maintained at levels less than the maximum rating of the equipment to maximize life
expectancy. Packaging the equipment and selecting an appropriate enclosure to maintain
the desired temperature is a function of the following:
• Internal heat dissipation from the assemblies

• Outside ambient temperature
• Cooling system (if used)
5.4.2 Enclosures
It is recommended that enclosures not be placed in direct sunlight, and locations near heat
generating equipment need to be evaluated. Since the internal temperature increases from
the bottom to the top of the enclosure, limiting the temperature at the top is a key design
objective.
Temperature Considerations in Packaging Electronics

When selecting an enclosure system for Mark VIe hardware, it is the responsibility of the
system designer to select an enclosure which will ensure reliable operation of the
enclosed equipment. The designer must ensure that the local temperatures inside the
enclosure do not exceed the rating of the equipment. For solid door and vented free
convection cooling designs, enclosure level analyses which predict overall temperature
rises are typically insufficient. It is instead necessary to consider the localized hot spots
generated by the distributed heat sources inside the enclosure and verify that those heated
zones do not exceed the temperature rating of equipment located in the hot spot.
For all types of enclosure systems, it is important to highlight the potential effect of
changes from the original design. GE designed enclosure systems are engineered to
maintain the Mark VIe system components within their specified temperature ratings.
Modifying the enclosure or adding additional equipment to the enclosure could
potentially compromise the thermal design.
While effective enclosure cooling can be accomplished in many ways, including active
cooling like air conditioners, thermoelectric coolers, or vortex coolers, most enclosures
are air cooled using one of the following cooling systems. The following are key points to
consider when selecting one of these systems and are not intended to take the place of
proper enclosure thermal analyses.
5.4.2.1 Solid Door

Solid door enclosures are an occasional necessity where environmental conditions
outside the enclosure are potentially harmful to the enclosed equipment. Great care should
be used in applying fully enclosed cabinets without supplemental cooling, however, as
relatively low power can result in significant internal temperature rises. For this reason,
and because the enclosure can also be susceptible to temperature rise due to unanticipated
heat sources outside the enclosure, this type of architecture is only recommended where
additional analysis validates that thermal design requirements are met.
5.4.2.2 Free Convection Cooled

Free convection cooled ventilated enclosures are commonly used for control equipment
and are suitable in many cases for providing sufficient cooling air to internal equipment.
The application of filters to the air vents is also a common practice and can provide
similar Ingress Protection (IP) rating to a solid door. It should be noted, however, that a
filtered cabinet with clogged filters will function like a solid door enclosure and can result
in over-temperature conditions. For this reason, it is recommended that the use of filters
be limited to cases where the additional IP rating is required. In those cases, the filters
must be regularly maintained to ensure proper operation of the cooling system.

5.4.2.3 Fan Cooled
Fan cooled ventilated enclosures are typically used on enclosures where greater thermal
margin is desired or where the ambient temperature outside the enclosure is close to the
operating temperature of the internal equipment. The fan cooled enclosures can also be
provided with filters to improve the IP rating of the enclosure. Again the filters should be
regularly maintained to ensure that the cooled system operates to its required capability.
While fan cooled systems can ideally maintain internal enclosure temperatures within a
few degrees of the external temperature, care must still be used when applying these
systems to ensure that all components receive adequate cooling air. It is possible in forced
cooling systems to have components which experience greater temperature rises than they
would in free convection if the component is located in an area of poor circulation or
recirculation.

5.4.3 Temperature of Components
The equipment can be applied as a distributed system, with multiple enclosures
mounted in remote locations. Temperature sensors and diagnostics are built into the
equipment for continuous monitoring. Each I/O pack’s local processor board contains a
temperature sensor. This sensor is located in close proximity to the main processor on
the I/O pack processor board and is thus positioned to report the approximate
temperature of the main processor itself.
Cabinet
Ambient
Because this sensor is detecting the internal component temperature, reported
temperatures which are above the ambient temperature rating of the component for the
Temp. enclosure design, -30 to 65°C (-22 to 149 °F), are normal and should not be cause for
Sensor concern. These temperatures are continuously available in the database and from the
ToolboxST application. Detection of an excessive temperature (>85ºC [185 °F])
generates a diagnostic alarm, so if there are no temperature alarms, then the equipment
is within acceptable range for normal operations. Even if alarms are present, the
components themselves should continue to operate well above the alarm limit.
Excessive temperatures can however, limit the life of the equipment.
The equipment should be arranged by following normal wiring practices for separation
of high and low levels, but in a few cases, heat should be considered. Some components
dissipate more heat than others. If there is a significant temperature rise from the bottom
of the enclosure to the top, then electronics with significant heat dissipation should be
mounted lower in the enclosure.
Enclosure Example
For internal enclosure design considerations, most Mark VIe components have an
ambient temperature rating of -30 to 65°C (-22 to 149 °F). The following table lists only
the components with more restrictive ambient ratings.
Mark VIe Equipment with Restrictive Ambient Ratings
Equipment Operating Temperature
UCCA controller 0 to 60°C (32 to 140 °F)
UCCC controller 0 to 50°C (32 to 122 °F)
UCSA controller (also PMVE and PAMC) 0 to 65°C (32 to 149 °F)
UCSBH3A controller
PCNO, PPRF -20 to 55°C (-4 to 131 °F)
PFFA 0 to 55°C (32 to 131 °F)
DACA -30 to 60°C (-22 to 140 °F)
5.4.4 Shipping and Storage Temperature

Temperature range during equipment shipping and storage is -40 to 85°C (-40 to 185 °F)
for I/O and controllers, and 0 to 30°C (32 to 86 °F) for control room equipment.

5.4.5 Control Room Operating Environment
To ensure proper performance and normal operational life, the control room environment
should be maintained as follows:
Higher ambient temperature Ambient temperature (preferred): 20 to 30°C (68 to 86 °F)
decreases the life expectancy of
any electronic component. Relative humidity: 5 to 95%, non-condensing
Keeping ambient air in the
Environments that include excessive amounts of any of the following elements reduce
preferred (cooler) range
cabinet performance and life:
should extend component life.
• Dust, dirt, or foreign matter
• Vibration or shock
• Moisture or vapors
• Rapid temperature changes
• Acid or caustic fumes
• Power line fluctuations
• EMI or noise introduced by:
− Radio frequency signals, typically from nearby portable transmitters
− Stray high voltage or high-frequency signals, typically produced by arc welders,
unsuppressed relays, contactors, or brake coils operating near control circuits
Enclosures can be custom The preferred location for the control system cabinet would be in an environmentally
engineered for other locations controlled room or in the control room itself. The cabinet should be mounted where the
if desired. floor surface allows for attachment in one plane (a flat, level, and continuous surface).
The customer provides the mounting hardware. Lifting lugs are provided and if used, the
lifting cables must not exceed 45° from the vertical plane. Finally, the cabinet is equipped
with a door handle, which can be locked for security.
Interconnecting cables can be brought into the cabinet through removable access plates.
Convection cooling of the cabinet requires that conduits be sealed to the access plates. In
addition, air passing through the conduit must be within the acceptable temperature range
as listed previously.
5.4.6 Humidity
The ambient humidity range is 5 to 95% non-condensing. This exceeds EN50178.

5.4.7 Elevation
†Elevation shall not exceed Equipment elevation is related to the equivalent ambient air pressure:
2000 m for compliance to
61010-1. • Normal operation: 0 to 1000 m (0 to 3280.8 ft) at 101.3 to 89.8 kPa
The extended operation and • Extended operation: 1000 to 3000 m† (3280.8 to 6561.7 ft) at 89.8 to 69.7 kPa
shipping specifications exceed • Shipping: 4600 m (15091.8 ft) at 57.2 kPa max
EN50178.
Note For extended altitude operation, the maximum ambient temperature rating of the
equipment should be reduced by 1°C (3.4 °F) for each additional 410 m (1345 ft) above
1000 m (3280.83 ft). Therefore, an I/O pack rated for 65°C (149 °F) at 1000 m (3280.8 ft)
will be rated for 62.6°C (144.7 °F) at 2000 m (6562 ft).
5.4.8 Contaminants
The control equipment withstands the following concentrations of corrosive gases at 50%
relative humidity and 40°C (104 °F):
This meets EN50178 Section Corrosive Gas Concentration
A.6.1.4 Table A.2 (m).
Sulfur dioxide (SO2) 30 ppb
Hydrogen sulfide (H2S) 10 ppb
Nitrous fumes (NO) 30 ppb
Chlorine (Cl2) 10 ppb
Hydrogen fluoride (HF) 10 ppb
Ammonia (NH3) 500 ppb
Ozone (O3) 5 ppb
5.4.9 Vibration
5.4.9.1 Seismic
Universal Building Code (UBC) - Seismic Code section 2312 Zone 4 (Optional)
5.4.9.2 Operating/Installed at Site

Vibration of 1.0 G Horizontal, 0.5 G Vertical at 15 to 120 Hz
Refer to Seismic UBC for frequencies lower than 15 Hz.

5.4.10 Applying Mark VIe Control in Hazardous
Locations (HazLoc)
Certain Mark VIe controllers, I/O packs, terminal boards, option boards, trip boards,
power distribution boards, and IONet switches are designed to operate in hazardous
locations (Class 1, Division 2, Groups A, B, C, and D; Class I, Zone 2; and ATEX II 3 G).
Note For a list of UL Class 1, Division 2 and Class 1, Zone 2 capable modules, go to the
following internet address: http://www.ul.com.
Select the Certifications link, select the Online Certifications Directory link, type
E207685 into the basic search UL File Number field, and click Search.

Notes

6 Installation Guidelines
For initial startup and software This chapter defines installation requirements for the control system. Specific topics
procedures, refer to include GE installation support, wiring practices, grounding, typical equipment weights
GEH-6724, Mark VIe Control and dimensions, power dissipation and heat loss, and environmental requirements.
Initial Startup Instruction
Guide.
This equipment contains a potential hazard of electric shock or
burn. Only personnel who are adequately trained and
Warning
6.1 Installation Support

GE’s system warranty provisions require both quality installation and that a qualified
service engineer be present at the initial equipment startup. To assist the customer, GE
offers both standard and optional installation support. Standard support consists of
documents that define and detail installation requirements. Optional support is typically
the advisory services that the customer may purchase.
6.1.1 Early Planning

To help ensure a fast and accurate exchange of data, a planning meeting with the
customer is recommended early in the project. This meeting should include the
customer’s project management and construction engineering representatives. It should
accomplish the following:
• Familiarize the customer and construction engineers with the equipment

• Set up a direct communication path between GE and the party making the customer’s
installation drawings
• Determine a drawing distribution schedule that meets construction and installation
needs
• Establish working procedures and lines of communication for drawing distribution
Installation Guidelines GEH-6721Y System Guide 95

6.1.2 GE Installation Documents
Installation documents consist of both general and requisition-specific information. The
cycle time and the project size determine the quantity and level of documentation
provided to the customer.
General information, such as this document, provides product-specific guidelines for the
equipment. They are intended as supplements to the requisition-specific information.
Requisition documents, such as outline drawings and elementary diagrams provide data
specific to a custom application. Therefore, they reflect the customer’s specific
installation needs and should be used as the primary data source.
As-Shipped drawings consist primarily of elementary diagrams revised to incorporate any

revisions or changes made during manufacture and test. These are issued when the
equipment is ready to ship. Revisions made after the equipment ships, but before start of
installation, are sent as Field Changes, with the changes circled and dated.
6.1.3 Technical Advisory Options

To assist the customer, GE offers the optional technical advisory services of field
engineers for:
• Review of customer’s installation plan

• Installation support
These services are not normally included as installation support or in basic startup and
commissioning services displayed below. GE presents installation support options to the
customer during the contract negotiation phase.
Startup and Commissioning Services Cycle

6.1.4 Installation Plan and Support
It is recommended that a GE field representative review all installation/construction
drawings and the cable and conduit schedule when completed. This optional review
service ensures that the drawings meet installation requirements and are complete.
Optional installation support is offered: planning, practices, equipment placement, and

onsite interpretation of construction and equipment drawings. Engineering services are
also offered to develop transition and implementation plans to install and commission
new equipment in both new and existing (revamp) facilities.
6.1.5 Customer’s Conduit and Cable Schedule

The customer’s finished conduit and cable schedule should include:
• Interconnection wire list (optional)

• Level definitions
• Shield terminations
The cable and conduit schedule should define signal levels and classes of wiring (refer to
the section, Cable Separation and Routing). This information should be listed in a
separate column to help prevent installation errors.
The cable and conduit schedule should include the signal level definitions in the
instructions. This provides all level restriction and practice information needed before
installing cables.
The conduit and cable schedule should indicate shield terminal practice for each shielded
cable (refer to the section, Connecting the System).

6.2 Equipment Receiving and Handling
GE inspects and packs all equipment before shipping it from the factory. A packing list,
itemizing the contents of each package, is attached to the side of each case.
Only personnel who are adequately trained and thoroughly

familiar with the equipment and instructions should install,
operate, or maintain the equipment. To prevent damage to the
equipment, personnel injury, or death, safe equipment lifting
practices must be followed. For example, use adequate tie-off,
load-spreading mechanisms, precise lifting control, managed
Warning acceleration, the correct forklift/crane rated for equipment
tonnage, and so forth.
Upon receipt, carefully examine the contents of each shipment and check them with the
packing list. Immediately report any shortage, damage, or visual indication of rough
handling to the carrier. Then notify both the transportation company and GE. Be sure to
include the serial number, part (model) number, GE requisition number, and case number
when identifying the missing or damaged part.
Immediately upon receiving the system, place it under

adequate cover to protect it from adverse conditions. Packing
cases are not suitable for outdoor or unprotected storage.
Shock caused by rough handling can damage electrical
equipment. To prevent such damage when moving the
equipment, observe normal precautions along with all
Attention
handling instructions printed on the case.
If technical assistance is required beyond the instructions provided in the documentation,

contact the nearest GE Sales or Service Office or an authorized GE Sales Representative.

6.2.1 Storage
If the system is not installed immediately upon receipt, it must be stored properly to
prevent corrosion and deterioration. Since packing cases do not protect the equipment for
outdoor storage, the customer must provide a clean, dry place, free of temperature
variations, high humidity, and dust.
Use the following guidelines when storing the equipment:
• Place the equipment under adequate cover with the following requirements:
− Keep the equipment clean and dry, protected from precipitation and flooding.
− Use only breathable (canvas type) covering material – do not use plastic.
• Unpack the equipment as described, and label it.
• Maintain the following environment in the storage enclosure:
− Recommended ambient storage temperature limits for the Mark VIe controller
are from -40 to 85°C (-40 to 185 °F).
− Surrounding air free of dust and corrosive elements, such as salt spray or
chemical and electrically conductive contaminants
− Ambient relative humidity from 5 to 95% with provisions to prevent
condensation
− No rodents, snakes, birds or insects
− No temperature variations that cause moisture condensation
Moisture on certain internal parts can cause electrical failure.
Attention
Condensation occurs with temperature drops of 15°C (59 °F) at 50% humidity over a
four-hour period, and with smaller temperature variations at higher humidity.
If the storage room temperature varies in such a way, install a reliable heating system that
keeps the equipment temperature slightly above that of the ambient air. This can include
space heaters or cabinet space heaters (when supplied) inside each enclosure. A 100 W
lamp can sometimes serve as a substitute source of heat.
To prevent fire hazard, remove all cartons and other such

flammable materials packed inside units before energizing any
heaters.
Attention

6.3 Power Requirements
The control cabinet can accept power from multiple power sources. Each power input
428 Rev A Released 10/3/2013 Page 2 of 10
source (30 A / 120
DWG Number 109T7428 Rev AV ac, 15 A
Released / 240 V
10/3/2013 ac,6 ofor1030 A / 125 V dc) should feed through its own
Page
external, two-pole, thermal, magnetic circuit breaker before entering the control system
enclosure. The breaker should be supplied in accordance with required site codes. The
A
REV
circuit breaker must be included in the installation. If used as the panel disconnect, it must
SHEET
6
be suitably located and easily reachable. The circuit breaker must be marked as the
disconnecting device and suitably located near the equipment for servicing.
Mark VIe control panels / systems may use up to three mains supplies; two for redundant
control power (ac and / or dc) and one auxiliary ac supply for accessories such as panel
109T7428
lights and fans. The following are example mains power supply rating labels used on the
(100 [3.94]) (100
front cabinet door where the panel mains power is to be[3.94])
connected.
DWG NO.
A
SIZE
(75 [2.95]) (75 [2.95])
P0006
Referencing the designators from the rating label, AC1 and optional AC2 may be 120 V
P0002
ac or 240 V ac, 50/60 Hz. DC1 and optional DC2 are 220 V dc supplies that may be used
instead of AC1 and AC2. DC is an optional floating source 125 V dc supply, usually a
battery. AUXAC is used only to supply internal auxiliary appliances, such as fans,
heaters, lights, or socket outlets. The AC1, AC2, DC, DC1, or DC2 mains supplies may
feed one or more Switch Mode Power Supplies to provide 28 V dc control power, or 24 or
48 V dc wetting for contact I/O circuits.
Refer to GEH-6421, Mark VI AC1 and AC2 may also feed one or two optional DACA Line Rectified Power Supplies.
©COPYRIGHT 2013 GE GE CLASS II (INTERNAL CRITICAL)
2013 GE Control, Volume II System Each DACA
ENERGY (USA), is
LLCfactory-set
GEAND/OR
CLASS for eitherCRITICAL)
ITS AFFILIATES.
II (INTERNAL
All rights reserved. The information contained
120 or 240 V ac input, and provides a floating 107 V
A), LLC AND/OR ITS AFFILIATES. GENERAL ELECTRIC COMPANY
Guide, the chapter, Power
ved. The information contained dc output. The DACA
GENERAL
Technical Information belongsDC
herein is GE Energy C & PE COE Proprietary
thatELECTRIC output may be connected through an internal diode SALEM,
COMPANY
to the General with the
VA.
nergy C & PE COE Proprietary
mation that belongs to the General
Distribution Modules GE
(PDM). DC
Electric Company, GE Energy (USA),
optional 125 hasV dc
LLC
supply
and/or
SALEM, VA.
to provide GE OR’d
diode Energydc redundancy to feed Switch Mode
any, GE Energy (USA), LLC and/or
which has been provided solely for
Energy the express reason of restricted private use. All
their affiliates, which been provided solely for
ason of restricted private use. All Power

persons,Supplies, external
firms, or corporations loads
who receive such such as solenoids, and /or wetting for contact I/O circuits.
or corporations who receive such information shall be deemed by the act of their
GE PROPRIETARY
receiving the same to have agreed to make no
DATA NAMEPLATE
all be deemed by the act of their
ame to have agreed to make no
GE PROPRIETARY DATA NAMEPLATE INFORMATION
duplication, or other disclosure, or use whatsoever
for any, or all such information except as expressly MARK VI LINE
other disclosure, or use whatsoever INFORMATION MARK VI LINE
authorized in writing by the General Electric
uch information except as expressly
riting by the General Electric
Note For compliance to Low Voltage
SIZE Directive
CAGE CODE 2006/95/EC,
Company, GE Energy (USA), LLC and/or its DWG NO.all ac and dc power supply REV
Energy (USA), LLC and/or its SIZE CAGE CODE DWGaffiliates.
NO. REV 109T7428
mains must connect through a MarkAVIe Overvoltage Transient Protection and EMI Filter A
A 109T7428 A
SCALE NONE SHEET 6 of 10
circuit. These OV and EMI filter circuits are built-in to the JPDB and JPDF Power
SCALE NONE SHEET 2 of 10
Distribution Modules. If JPDB/JPDF are not used to distribute ac and dc power supply
GE Proprietary Information - Class II (Internal) US EAR - NLR
mains to the Mark VIe control, then a separate GE Filter Module 246B8279Gx should be
GE Proprietary Information - Class II (Internal) US EAR - NLR
used to filter the mains. Refer to GEH-6721 Volume II, the chapter, PDM Power
Distribution Modules.

Power requirements for a typical large, four-cabinet turbine control containing controllers,
I/O, and terminal boards are displayed in the following table. The total panel current
ratings must include the current supplied to external loads, such as solenoids and ignition
transformers as described in the notes below the table. Heat dissipation in a typical TMR
turbine control is about 1600 watts. However, power supply mains and heat dissipation
requirements must be calculated for each Mark VIe panel application based on the
number and mix of controllers, I/O modules, IONet switches, power supplies, and
external loading.
Power Requirements for Cabinets
Cabinet Voltage Frequency Current Requirements
Large, 125 V dc ± 10% N/A N/A 15.0 A dc (Note 1)
four-cabinet 120 V ac ± 10% 50/60 Hz ±3 Hz 20.0 A rms (Notes 2, 4)
turbine control 240 V ac ± 10% 50/60 Hz ±3 Hz 10.0 A rms (Notes 3, 4)
1. Add 0.5 A dc † continuous for each 125 V dc external solenoid powered.
2. Add 6.0 A rms † for a continuously powered ignition transformer (2 maximum).
3. Add 3.5 A rms † for a continuously powered ignition transformer (2 maximum).
4. Add 2.0 A rms † continuous for each 120 V ac external solenoid powered (inrush 10 A).
Note † These are external and do not create cabinet heat load.

6.4 Installation Support Drawings
This section describes GE installation support drawings. These drawings are usually
B-size AutoCAD® drawings covering all hardware aspects of the system. A few sample
drawings include:
• System Topology
• Cabinet Outline
• Cabinet Layout
• Circuit Diagram
In addition to the installation drawings, site personnel will need the I/O Assignments (I/O
Report).
Junction boxes can weigh well over 45.36 Kg (100 lb).

Installation should be planned to protect both the box and the
personnel. The use of an overhead crane may be required.
Consult the site specific shipping and junction box documents.
Follow all standard safety practices.
Only personnel who are adequately trained and thoroughly

Warning
familiar with the equipment and the instructions should install,
operate, or maintain this equipment.

Typical System Topology Showing Interfaces

Typical Cabinet Outline with Dimensions

Typical Cabinet Layout

Circuit Diagram

6.5 Grounding
This section defines grounding and signal-referencing practices for the control system.
This can be used to check for proper grounding and signal reference structure (SRS) after
the equipment is installed. If checking the equipment after the power cable has been
connected or after power has been applied to the cabling, be sure to follow all safety
precautions for working around high voltages.
To prevent electric shock, make sure that all power supplies to

the equipment are turned off. Then discharge and ground the
equipment before performing any act requiring physical
contact with the electrical components or wiring. If test
equipment cannot be grounded to the equipment under test, the
Warning test equipment's case must be shielded to prevent contact by
personnel. Be sure to follow the site LOTO and safety practices.
6.5.1 Equipment Grounding

Equipment grounding and signal referencing have two distinct purposes:
• Equipment grounding protects personnel from risk of serious or fatal electrical shock,
burn, fire, and/or other damage to equipment caused by ground faults or lightning.
• Signal referencing helps protect equipment from the effects of internal and external
electrical noise, such as lightning or switching surges.
Installation practices must simultaneously comply with all codes in effect at the time and
place of installation, and with all practices that improve the immunity of the installation.
Code requirements for safety of personnel and equipment must take precedence in the
case of any conflict with noise control practices.
Note In addition to technical regulations, guidance from IEEE Std 142-2007 IEEE
Recommended Practice for Grounding of Industrial and Commercial Power Systems, and
IEEE Std 1100-2005 IEEE Recommended Practice for Powering and Grounding
Electronic Equipment are provided by the design and implementation of the system.

The control system has no special or non-standard installation requirements, if installed in
compliance with all of the following:
• The NEC or local codes

• With SRS designed to meet IEEE Std 1100
• Interconnected with signal/power-level separation as defined later
This section provides equipment grounding and bonding guidelines for control and I/O
cabinets. These guidelines also apply to motors, transformers, brakes, and reactors. Each
of these devices should have its own grounding conductor going directly to the building
ground grid.
• Ground each cabinet or cabinet lineup to the equipment ground at the source of
power feeding it.
− See NEC Article 250 for sizing and other requirements for the
equipment-grounding conductor.
− For dc circuits only, the NEC allows the equipment-grounding conductor to be
run separate from the circuit conductors.
• With certain restrictions, the NEC allows the metallic raceways or cable trays
containing the circuit conductors to serve as the equipment grounding conductor:
− This use requires that they form a continuous, low-impedance path capable of
conducting anticipated fault current.
− This use requires bonding across loose-fitting joints and discontinuities. See
NEC Article 250 for specific bonding requirements. This chapter includes
recommendations for high-frequency bonding methods.
− If metallic raceways or cable trays are not used as the primary equipment-
grounding conductor, they should be used as a supplementary equipment
grounding conductor. This enhances the safety of the installation and improves
the performance of the SRS.
• The equipment-grounding connection for the control cabinets is plated copper bus or
stub bus. This connection is bonded to the cabinet enclosure using bolting that keeps
the conducting path’s resistance at 1 ohm or less.
• There should be a bonding jumper across the ground bus or floor sill between all
shipping splits. The jumper may be a plated metal plate.
• The non-current carrying metal parts of the equipment covered by this section should
be bonded to the metallic support structure or building structure supporting this
equipment. The equipment mounting method may satisfy this requirement. If
supplementary bonding conductors are required, size them the same as
equipment-grounding conductors.

6.5.2 Building Grounding System
This section provides guidelines for the building grounding system requirements. For
specific requirements, refer to NEC article 250 under the heading Grounding Electrode
System.
The guidelines below are for metal-framed buildings. For non-metal framed buildings,
consult the GE factory.
The ground electrode system should be composed of steel reinforcing bars in building
column piers bonded to the major building columns.
• A buried ground ring should encircle the building. This ring should be interconnected
with the bonding conductor running between the steel reinforcing bars and the
building columns.
• All underground, metal water piping should be bonded to the building system at the
point where the piping crosses the ground ring.
• NEC Article 250 requires that separately derived systems (transformers) be grounded
to the nearest effectively grounded metal building structural member.
• Braze or exothermically weld all electrical joints and connections to the building
structure, where practical. This type of connection keeps the required good electrical
and mechanical properties from deteriorating over time.

6.5.3 Signal Reference Structure
The provisions covered in this On modern equipment communicating at high bandwidths, signals are typically
document may not apply to all differential and/or isolated electrically or optically. The modern Signal Reference
installations. Structure (SRS) system replaces the older single-point grounding system with a much
more robust system. The SRS system is also easier to install and maintain.
The goal of the SRS is to hold the electronics at or near case potential to prevent
unwanted signals from disturbing operation. The following conditions must all be met by
an SRS:
• Bonding connections to the SRS must be less than 1/20 wavelength of the highest
frequency to which the equipment is susceptible. This prevents standing waves. In
modern equipment using high-frequency digital electronics, frequencies as high as
500 MHz should be considered. This translates to about 30 mm (1 in).
• SRS must be a good high-frequency conductor. (Impedance at high frequencies
consists primarily of distributed inductance and capacitance.) Surface area is more
important than cross-sectional area because of skin effect. Conductivity is less
important (steel with large surface area is better than copper with less surface area).
• SRS must consist of multiple paths. This lowers the impedance and the probability of
wave reflections and resonance
In general, a good signal referencing system can be obtained with readily available
components in an industrial site. All of the items listed below can be included in an SRS:
• Metal building structural members

• Galvanized steel floor decking under concrete floors
• Woven wire steel reinforcing mesh in concrete floors
• Steel floors in pulpits and power control rooms
• Bolted grid stringers for cellular raised floors
• Steel floor decking or grating on line-mounted equipment
• Galvanized steel culvert stock
• Ferrous metallic cable tray systems
• Raceway (cableway) and raceway support systems
• Embedded steel floor channels

Connection of the protective earth (PE) terminal to the installation ground system must
first comply with code requirements and second provide a low-impedance path for
high-frequency currents, including lightning surge currents. This grounding conductor
must not provide, either intentionally or inadvertently, a path for load current. The system
should be designed so that there is no way possible for the control system to be an
attractive path for induced currents from any source. This is best accomplished by
providing a ground plane that is large and low impedance, so that the entire system
remains at the same potential. A metallic system (grid) will accomplish this much better
than a system that relies upon earth for connection. At the same time all metallic
structures in the system should be effectively bonded both to the grid and to each other, so
that bonding conductors rather than control equipment become the path of choice for
noise currents of all types.
In the control cabinet, the base is insulated from the chassis and bonded at one point. The
grounding recommendations, displayed in the following figure, call for the equipment
grounding conductor to be 120 mm2 (4/0 AWG) gauge wire, connected to the building
ground system. The Functional Earth (FE) is bonded at one point to the PE ground using
two 25 mm2 (6 AWG or larger) green/yellow bonding jumpers.
Grounding Recommendations for Single Control Cabinet
If acceptable by local codes, the bonding jumpers may be removed and a 4/0 AWG
identified insulated wire run from FE to the nearest accessible point on the building
ground system, or to another ground point as required by the local code.

The grounding method for a larger system is displayed in Figure B. Here the FE is still
connected to the control electronics section, but the equipment-grounding conductor is
connected to the center cabinet chassis. Individual control and I/O bases are connected
with bolted plates.
For armored cables, the armor is an additional current carrying braid that surrounds the
internal conductors. This type cable can be used to carry control signals between
buildings. The armor carries secondary lightning-induced earth currents, bypassing the
control wiring, thus avoiding damage or disturbance to the control system. At the cable
ends and at any strategic places between, the armor is grounded to the building ground
through the structure of the building with a 360° mechanical and electrical fitting. The
armor is normally terminated at the entry point to a metal building or machine. Attention
to detail in installing armored cables can significantly reduce induced lightning surges in
control wiring.
Grounding Recommendations for Control Cabinet Lineup

6.5.3.1 Notes on Grounding
Bonding to building structure - The cable tray support system typically provides many
bonding connections to building structural steel. If this is not the case, supplemental
bonding connections must be made at frequent intervals from the cable tray system to
building steel.
Connected equipment - Cable tray installations for connected equipment should pay
special attention to good high-frequency bonding between the cable tray and the
equipment.
Cable spacing - Maintain cable spacing between signal levels in cable drops, as
recommended in the section, Cable Separation and Routing.
Conduit sleeves - Where conduit sleeves are used for bottom-entry cables, the sleeves
should be bonded to the floor decking and equipment enclosure with short bonding
jumpers.
Embedded conduits - Bond all embedded conduits to the enclosure with multiple
bonding jumper connections following the shortest possible path.
Galvanized steel sheet floor decking - Floor decking can serve as a high-frequency
signal reference plane for equipment located on upper floors. With typical building
construction, there will be a large number of structural connections between the floor
decking and building steel. If this is not the case, then an electrical bonding connection
must be added between the floor decking and building steel. The added connections need
to be as short as possible and of sufficient surface area to be low impedance at high
frequencies.
High-frequency bonding jumpers - Jumpers must be short, less than 500 mm (20 in)
and good high-frequency conductors. Thin, wide metal strips are best with length not
more than three times width for best performance. Jumpers can be copper, aluminum, or
steel. Steel has the advantage of not creating galvanic half-cells when bonded to other
steel parts.
Jumpers must make good electrical contact with both the enclosure and the signal
reference structure. Welding is best. If a mechanical connection is used, each end should
be fastened with two bolts or screws with star washers backed up by large diameter flat
washers.
Each enclosure must have two bonding jumpers of short, random lengths. Random
lengths are used so that parallel bonding paths are of different quarter wavelength
multiples. Do not fold bonding jumpers or make sharp bends.
Metallic cable tray - System must be installed per NEC Article 318 with signal level
spacing per the section, Cable Separation and Routing. This serves as a signal reference
structure between remotely connected pieces of equipment. The large surface area of
cable trays provides a low impedance path at high frequencies.
Metal framing channel - Metal framing channel cable support systems also serve as
parts of the SRS. Make certain that channels are well bonded to the equipment enclosure,
cable tray, and each other, with large surface area connections to provide low impedance
at high frequencies.

Noise-sensitive cables - Try to run noise-sensitive cables tight against a vertical support
to allow this support to serve as a reference plane. Cables that are extremely susceptible
to noise should be run in a metallic conduit, preferably ferrous. Keep these cables tight
against the inside walls of the metallic enclosure, and well away from higher-level cables.
Power cables - Keep single-conductor power cables from the same circuit tightly bundled
together to minimize interference with nearby signal cables. Keep 3-phase ac cables in a
tight triangular configuration.
Woven wire mesh - Woven wire mesh can serve as a high-frequency signal reference
grid for enclosures located on floors not accessible from below. Each adjoining section of
mesh must be welded together at intervals not exceeding 500 mm (20 in) to create a
continuous reference grid. The woven wire mesh must be bonded at frequent intervals to
building structural members along the floor perimeter.
Conduit terminal at cable trays - To provide the best shielding, conduits containing
level L cables (see Leveling channels) should be terminated to the tray's side rails (steel
solid bottom) with two locknuts and a bushing. Conduit should be terminated to ladder
tray side rails with approved clamps.
Where it is not possible to connect conduit directly to tray (such as with large conduit
banks), conduit must be terminated with bonding bushings and bonded to tray with short
bonding jumpers.
Leveling channels - If the enclosure is mounted on leveling channels, bond the channels
to the woven wire mesh with solid-steel wire jumpers of approximately the same gauge as
the woven wire mesh. Bolt the enclosure to leveling channel, front and rear.
Signal and power levels - Refer to section, Cable Separation and Routing, for
guidelines.
Solid-bottom tray - Use steel solid bottom cable trays with steel covers for low-level
signals most susceptible to noise.

Enclosure and Cable Tray Installation Guidelines

6.6 Cable Separation and Routing
This section provides recommended cabling practices to reduce electrical noise. These
practices include signal/power level separation and cable routing guidelines.
Note Electrical noise from cabling of various voltage levels can interfere with
microprocessor-based control systems, causing a malfunction. If a situation at the
installation site is not covered in this document, or if these guidelines cannot be met,
please contact GE before installing the cable.
Early planning enables the customer’s representatives to design adequate separation of

embedded conduit. On new installations, sufficient space should be allowed to efficiently
arrange mechanical and electrical equipment. On revamps, level rules should be
considered during the planning stages to help ensure correct application and a more
trouble-free installation.
6.6.1 Signal and Power Level Definitions

Signal and power carrying cables are categorized into four defining levels; low, medium,
high, and power. Each level can include classes.
6.6.1.1 Low-level Signals (Level L)

Low-level signals are designated as level L. In general these consist of:
• Analog signals 0 through ±50 V dc, < 60 mA

• Digital (logic-level) signals less than 28 V dc
• 4 to 20 mA current loops
• Ac signals less than 24 V ac
The following are specific examples of level L signals used in the control cabling:
Signal input to analog and • All analog and digital signals including LVDTs, Servos, RTDs, Analog Inputs and
digital blocks or to Outputs, and Pyrometer signals
programmable logic control
• Thermocouples are in a special category (Level LS) because they generate millivolt
(PLC)-related devices should
signals with very low current.
be run as shielded twisted-pair
(for example, input from • Network communication bus signals: Ethernet, IONet, UDH, PDH, RS-232C, and
RTDs). RS-422
• Phone circuits

6.6.1.2 Medium-level Signals (Level M)
Level M and level L signals Medium-level signals are designated as level M. MPU signals are examples of level M
may be run together only signals used in the controller. These signals consist of:
inside the control cabinet.
• Analog signals less than 50 V dc with less than 28 V ac ripple and less than 0.6 A
current
• 28 V dc light and switching circuits
• 24 V dc switching circuits
• Analog pulse rate circuits
6.6.1.3 High-level Signals (Level H)

High-level signals are designated as level H. These signals consist of:
• Dc switching signals greater than 28 V dc

• Analog signals greater than 50 V dc with greater than 28 V ac ripple
• Ac feeders less than 20 A, without motor loads
The following are specific examples of level H signals used in cabling:
• Contact inputs
• Relay outputs
• Solenoid outputs
• Potential transformer (PT) and current transformer (CT) circuits
Note Flame detector (GM) type signals, 335 V dc, and Ultraviolet detectors are a special
category (Level HS). Special low capacitance twisted shielded pair wiring is required.
6.6.1.4 Power (Level P)

Power wiring is designated as level P. This consists of ac and dc buses 0 – 600 V with
currents 20 A – 800 A. The following are specific examples of level P signals used in
plant cabling:
• Motor armature loops

• Generator armature loops
• Ac power input and dc outputs
• Primary and secondary wiring of transformers above 5 kVA
• SCR field exciter ac power input and dc output
• Static exciters (regulated and unregulated) ac power and dc output
• 250 V shop bus
• Machine fields

6.6.1.5 Class Codes
Certain conditions can require that specific wires within a level be grouped in the same
cable. This is indicated by class codes, defined as follows:
S Special handling of specified levels can require special spacing of conduit and trays.
Check dimension chart for levels. These wires include:
• Signals from COMM field and line resistors

• Signals from line shunts to regulators
U High voltage potential unfused wires over 600 V dc
PS Power greater than 600 V dc and/or greater than 800 A
If there is no class code, there are no grouping restrictions within designated levels
6.6.1.6 Marking Cables to Identify Levels

Mark the cableway cables, conduit, and trays in a way that clearly identify their
signal/power levels. This helps ensure correct level separation for proper installation. It
can also be useful during equipment maintenance.
Cables can be marked by any means that makes the level easy to recognize (for example,
coding or numbering). Conduit and trays should be marked at junction points or at
periodic intervals.
6.6.2 Cableway Spacing Guidelines

Spacing (or clearance) between cableways (trays and conduit) depends on the level of the
wiring inside them. For correct level separation when installing cable, the customer
should apply the general practices along with the specific spacing values for tray/tray,
conduit/tray, conduit/conduit, cable/conduit, and cable/cable distances as discussed below.

6.6.2.1 General Practices
The following general practices should be used for all levels of cabling:
• All cables of like signal levels and power levels must be grouped together in like
cableways.
• In general, different levels must run in separate cableways, as defined in the different
levels. Intermixing cannot be allowed, except as noted by exception.
• Interconnecting wire runs should carry a level designation.
• If wires are the same level and same type signal, group those wires from one cabinet
to any one specific location together in multiconductor cables.
• When unlike signals must cross in trays or conduit, cross them in 90° angles at
maximum spacing. Where it is not possible to maintain spacing, place a grounded
steel barrier between unlike levels at the crossover point.
• When entering terminal equipment where it is difficult to maintain the specific
spacing guidelines displayed in the following tables, keep parallel runs to a
minimum, not to exceed 1.5 m (5 ft) in the overall run.
• Where the tables display tray or conduit spacing as 0, the levels can be run together.
Spacing for other levels must be based on the worst condition.
• Trays for all levels should be solidly grounded with good ground continuity. Conduit
should provide shielding.
The following general practices should be used for specific levels of cabling:
• When separate trays are impractical, levels L and M can be combined in a common
tray if a grounded steel barrier separates levels. This practice is not as effective as
tray separation, and may require some rerouting at system startup. If levels L and M
are run side-by-side, a 50 mm (1.97 in) minimum spacing is recommended.
• Locate levels L and M trays and conduit closest to the control panels.
• Trays containing level L and level M wiring should have solid galvanized steel
bottoms and sides and be covered to provide complete shielding. There must be
positive and continuous cover contact to side rails to avoid high-reluctance air gaps,
which impair shielding.
• Trays containing levels other than L and M wiring can have ventilation slots or
louvers.
• Trays and conduit containing levels L, M, and H(S) should not be routed parallel to
high power equipment enclosures of 100 kV and larger at a spacing of less than 1.5 m
(5 ft) for trays, and 750 mm (2.5 ft) for conduit.
• Level H and H(S) can be combined in the same tray or conduit but cannot be
combined in the same cable.
• Level H(S) is listed only for information since many customers want to isolate
unfused high voltage potential wires.
• Do not run levels H and H(S) in the same conduit as level P.
• Where practical for level P and/or P(S) wiring, route the complete power circuit
between equipment in the same tray or conduit. This minimizes the possibility of
power and control circuits encircling each other.

6.6.2.2 Tray and Conduit Spacing
The following tables display the recommended distances between metal trays and metal
conduit carrying cables with various signal levels, and the cable-to cable distance of
conduit and trays.
Cable, Tray, and Conduit Spacing

6.6.3 Cable Routing Guidelines
6.6.3.1 Pullboxes and Junction Boxes

Keep signal and power levels separate inside pullboxes and junction boxes. Use grounded
steel barriers to maintain level spacing. Tray-to-conduit transition spacing and separation
are a potential source of noise. Be sure to cross unlike levels at right angles and maintain
required separation. Use level spacing. Protect transition areas according to the level
spacing recommendations.
6.6.3.2 Transitional Areas

When entering or leaving conduit or trays, ensure cables of unlike levels are not mixed. If
the installation needs parallel runs over 1.5 m (5 ft), grounded steel barriers may be
needed for proper level separation.
6.6.3.3 Cabling for Retrofits

Reducing electrical noise on retrofits requires careful planning. Lower and higher levels
should never encircle each other or run parallel for long distances. It is practical to use
existing conduit or trays as long as the level spacing can be maintained for the full length
of the run. Existing cables are generally of high voltage potential and noise producing.
Therefore, route levels L and M in a path apart from existing cables when possible. Use
barriers in existing pullboxes and junction boxes for level L wiring to minimize noise
potential. Do not loop level L signals around high control or level P conduit or trays.
6.6.3.4 Conduit Around and Through Machinery Housing

Care should be taken to plan level spacing on both embedded and exposed conduit in and
around machinery. Runs containing mixed levels should be minimized to 1.5 m (5 ft) or
less overall. Conduit running through and attached to machinery housing should follow
level spacing recommendations. This should be discussed with the contractor early in the
project.
Trunnions entering floor mounted operator station cabinets should be kept as short as
possible when used as cableways. This helps minimize parallel runs of unlike levels to a
maximum of 1.5 m (5 ft) before entering the equipment. Where different signal/power
levels are running together for short distances, each level should be connected by cord
ties, barriers, or some logical method to prevent intermixing.
6.6.3.5 RF Interference
To prevent radio frequency (RF) interference, take care when routing power cables near
radio-controlled devices (for example, cranes) and audio/visual systems (public address
and closed-circuit television systems).
6.6.3.6 Suppression
Unless specifically noted otherwise, suppression (for example, a snubber) is required on
all inductive devices controlled by an output. This suppression minimizes noise and
prevents damage caused by electrical surges. Standard relay and solenoid output boards
have adequate suppression.

6.7 Fiber-optic Cabling
Fiber-optic cable is an effective substitute for copper cable, especially when longer
distances are required, or electrical disturbances are a serious problem.
The main advantages of fiber-optic transmission in the power plant environment are:
• Fiber segments can be longer than copper because the signal attenuation per foot is
less.
• In high-lightning areas, copper cable can pick up currents, which can damage the
communications electronics. Since the glass fiber does not conduct electricity, the use
of fiber-optic segments avoids pickup and reduces lightning-caused outages.
• Grounding problems are avoided with optical cable. The ground potential can rise
when there is a ground fault on transmission lines, caused by currents coming back to
the generator neutral point, or lightning.
• Optical cable can be routed through a switchyard or other electrically noisy area and
not pick up any interference. This can shorten the required runs and simplify the
installation.
• Fiber-optic connections normally have higher signal levels and decreased chances of
packet discard from noise corruption. Typical differences in error rate is 10000 lower
for fiber-optic cables.
• The cost per connection for fiber may now be less than copper cables. Large,
multifiber trunk cables contain many fibers, so cost per foot for each connection may
actually cost less than multiple copper cables.
• Fiber-optic cable with proper jacket materials can be run direct buried in trays or in
conduit.
• High-quality fiber-cable is light, tough, and easily pulled. With careful installation, it
can last the life of the plant.
Disadvantages of fiber optics include:
• The cost, especially for short runs, may be more for a fiber-optic link.
• Inexpensive fiber-optic cable can be broken during installation, and is more prone to
mechanical and performance degradation over time. The highest quality cable avoids
these problems.
6.7.1 Basics
Each fiber link consists of two fibers, one outgoing and the other incoming, to form a
duplex channel. A LED drives the outgoing fiber, and the incoming fiber illuminates a
phototransistor, which generates the incoming electrical signal. 1000SX and 1000LX use
laser diodes instead of LEDs.
Multi-mode fiber, with a graded index of refraction core and outer cladding, is
recommended for the optical links. The fiber is protected with buffering that is the
equivalent of insulation on metallic wires. Mechanical stress is bad for fibers so a strong
sheath is used, sometimes with pre-tensioned Kevlar® fibers to carry the stress of pulling
and vertical runs.

Connectors for a power plant should be fastened to a reasonably robust cable with its own
buffering. The square connector (SC) type connector is recommended. This connector is
widely used for LANs, and is readily available.
6.7.2 Multi-mode Fiber-optic Cable
Never look directly into a fiber. Although most fiber links use
LEDs that cannot damage the eyes, some longer links use lasers,
which can cause permanent damage to the eyes.
Warning
Multi-mode fibers are rated for use at 850 nm and 1300 nm wavelengths. Cable
attenuation is between 3.0 and 3.3 dB/km at 850 nm. The core of the fiber is normally
62.5 µ in diameter, with a gradation of index of refraction. The higher index of refraction
is at the center, gradually shifting to a medium index at the circumference. The higher
index slows the light, therefore, a light ray entering the fiber at an angle curves back
toward the center, out toward the other side, and then back toward the center. This ray
travels further but goes faster because it spends most of its time closer to the
circumference where the index is less. The index is graded to keep the delays nearly
equal, thus preserving the shape of the light pulse as it passes through the fiber.
The inner core is protected with a low index of refraction cladding, which for the
recommended cable is 125 µ in diameter. 62.5/125 fiber-optic cable is the most common
type of cable and should be used.
6.7.2.1 Guidelines on Cables Usage

• Gel filled (or loose tube) cables should not be used because of difficulties making
installations, terminations, and the potential for leakage in vertical runs.
• Use a high-quality breakout cable, which makes each fiber a sturdy cable, and helps
prevent bends that are too sharp.
• Sub-cables are combined with more strength and filler members to build up the cable
to resisting mechanical stress and the outside environment.
• Two types of cable are recommended, one with armor and one without. Rodent
damage is a major cause of optical cable failure. If this is a problem in the plant, the
armored cable should be used, although it is heavier, has a larger bend radius, is more
expensive, attracts lightning currents, and has lower impact and crush resistance.
• Optical characteristics of the cable can be measured with an optical time domain
reflectometer (OTDR). Some manufacturers will supply the OTDR printouts as proof
of cable quality. A simpler instrument is used by the installer to measure attenuation,
and they should supply this data to demonstrate the installation has a good power
margin.
• Cables described here have four fibers, enough for two fiber-optic links. This can be
used to bring redundant communications to a central control room. The extra fibers
can be retained as spares for future plant enhancements. Cables with two fibers are
available for indoor use.

6.7.2.2 Connectors
The 100Base-FX fiber-optic cables for indoor use in the control system have SC type
connectors. The connector, displayed in the following figure, is a keyed, snap-in
connector that automatically aligns the center strand of the fiber with the transmission or
reception points of the network device. An integral spring helps to keep the SC
connectors from being crushed together, avoiding damage to the fiber. The two plugs can
be held together as displayed, or they can be separate.
SC Connector for Fiber-optic Cables
The process of attaching the fiber connectors involves stripping the buffering from the
fiber, inserting the end through the connector, and casting it with an epoxy or other
plastic. This requires a special kit designed for that particular connector. After the epoxy
has hardened, the end of the fiber is cut off, ground, and polished. An experienced person
can complete the process in five minutes.
6.7.2.3 System Considerations

Redundancy should be considered for continuing central control room (CCR) access to
the turbine controls. Redundant HMIs, fiber-optic links, Ethernet switches, and power
supplies are recommended. The link design can deliver greater than 6 dB signal to noise
ratio from GE design process and component selection. This makes control systems more
reliable against minor defects in field installations and component aging over a 20-year
plant life.
Installation of the fiber can decrease its performance compared to factory-new cable.
Installers may not make the connectors as well as experts can, resulting in more loss than
planned. The LED light source can get dimmer over time, the connections can get dirty,
the cable loss increases with aging, and the receiver can become less sensitive. For all
these reasons, there must be a margin between the available power budget and the link
loss budget, of a minimum of 3 dB. Having a 6 dB margin is more comfortable, helping
assure a fiber link that will last the life of the plant.

6.7.2.4 Installation
Planning is important for a successful installation. This includes the layout for the
required level of redundancy, cable routing distances, proper application of the distance
rules, and procurement of excellent quality switches, UPS systems, and connectors.
• Install the fiber-optic cable in accordance with all local safety codes. Polyurethane
and PVC are two possible options for cable materials that might NOT meet the local
safety codes.
• Select a cable strong enough for indoor and outdoor applications, including direct
burial.
• Adhere to the manufacturer's recommendations on the minimum bend radius and
maximum pulling force.
• Test the installed fiber to measure the losses. A substantial measured power margin is
the best proof of a high-quality installation. Use trained people for the installation. If
necessary, hire outside contractors with fiber LAN installation experience.
• The fiber switches and converters need reliable power, and should be placed in a
location that minimizes the amount of movement they must endure, yet keep them
accessible for maintenance.
6.7.3 Single-mode Fiber-optic Cabling

Single-mode fiber-optic (SMF) cabling is approved for the Mark VIe control system,
including both IONet and UDH/PDH network applications. This extends the distance of
the control system beyond the traditional multi-mode fiber-optic (MMF) cabling limit of
2000 m to 15000 m (6561.7 to 49212.6 ft)
The following figure displays the differences between multi-mode and single-mode cable
types with a typical 62.5/125 µm MMF segment.

Since the cladding material Light (typically from a LED) enters through an aperture at the left, 62.5 µm in diameter.
has a different index of This aperture is many times the dimension of the typical 1500 µm wavelength used for
refraction than the core, these transmission. This difference between the aperture and the wavelengths allows waves to
waves will be reflected due to enter at multiple angles. Because of different angles, there are many paths the light can
the large angle of incidence make through the fiber with each taking a different time to arrive at the detector. This
(Snells Law). difference between the minimum time and maximum time for light transmission through
the fiber is known as dispersion. Dispersion is the main property that degrades the signal
through multi-mode fiber and limits the useful limit to 2 km (1.24 mi).
In the SMF cable, the aperture is reduced to ~9 µm, comparable to the 1500 µm
wavelength of transmission. In this small aperture, there is little difference in the angle of
incidence of the light and as such, the light propagates with little dispersion. The
attenuation is the main property that degrades the signal and as such, much greater
distances are achievable. The main advantage of SMF cable over traditional MMF cable
in the power plant environment is that fiber-optic segments can now be longer than 2000
m (6561.68 ft) because the signal attenuation per foot is less.

6.7.3.1 IONet Components
For the control system IONet topologies, the following rules apply for deploying SMF
systems:
• Must use either of the following switches:

− GE ESWx switch with 65G2100–008 IR SFP single-mode transducer installed
− N-TRON® 508FXE2-SC-15 switch
• No more than five switches should be placed in series and be maintained.

• The topology should be kept as flat and balanced as possible (star topology).
Only the GE ESWx switch with 65G2100–008 IR SFP

single-mode transducer installed or the N-TRON
508FXE2-SC-15 switch are validated and approved for this
application. Use of any other switch in this application may
cause miss operation and/or damage to the associated
Caution equipment.
GE ESWx Switch
N-TRON 508FXE2-SC-15 Switch

6.7.3.2 UDH/PDH Components
For PDH/UDH topologies, apply the following rules for installing SMF systems:
• SMF is validated on the UDH/PDH networks using the

− AT-8624T/2M (with AT-A45/SC-SM15 module )
− AT-8724 ( with AT-A41/SC module )
• SMF cable lengths can be zero to 15 km (9.32 mi) in length
• SMF cables MUST be terminated and/or spliced by a certified fiber-optic cable
installer, not by installation engineers.
In a typical SMF application, each 8624 switch is connected to its local network by
multi-mode fiber (could be copper 10/100Base-T/TX.) Each switch has a SMF interface
that is used to connect to the single-mode fiber link. The distance between the two
switches can then be up to 15 km (9.32 mi). The topology would be identical if AT-8724
switches are used, except that AT-A41/SC modules are used for the SMF interfaces.
Typical SMF Application

6.7.4 Component Sources
The following are typical sources for fiber-optic cable, single mode fiber-optic,
connectors, converters, and switches.
Fiber-optic Cable:
Optical Cable Corporation

5290 Concourse Drive
Roanoke, VA 24019
Phone: (540)265-0690
Part Numbers (from OCC)
Each of these cables are SMF 8.3/125 um Core/Cladding diameter with a numeric
aperture of 0.13.
OC041214-01 4 Fiber Zero Halogen Riser Rated Cable.

OC041214-02 4 Fiber Zero Halogen with CST Armor.
OC041214-03 4 Fiber with Flame Retardant Polyurethane.
OC041214-04 4 Fiber with Flame Retardant Polyurethane with CST Armor
Corning Cable Systems

PO Box 489
Hickory, NC 28603-0489
Phone: (800)743-2671
Fiber-optic Connectors:
3M® - Connectors and Installation kit

Thomas and Betts - Connectors and Assembly polishing kit
Amphenol - Connectors and Termination kit

6.8 Cable Specifications
• Maximum length (unless specified) 300 m (984.25 ft)
• Individual minimum stated wire size is for electrical needs
• Clamp-type terminals accept two 14 AWG wires or one 12 AWG wire
• Terminal blocks accept two 12 AWG wires
• PTs and CTs use 10 AWG stranded wire
Note Wires with appropriate temperature ratings must be used, especially in applications
where the internal panel ambient temperature can exceed 60°C (140 °F).
It is standard practice to use shielded cable with control equipment. Shielding provides
the following benefits:
• Generally, shielding protects a wire or combination of wires from its environment.

• Low-level signals may require shielding to prevent signal interference due to the
capacitive coupling effect between two sources of potential energy.
6.8.1 Wire Sizes

The recommended current carrying capacity for flexible wires up to 1,000 V, PVC
insulated, based on DIN VDE 0298 Part 4, is displayed in following table. Cross section
references of mm2 versus AWG are based on EN 60204 Part 1, VDE 0113 Part 1. NFPA
70 (NEC) may require larger wire sizes based on the type of wire used.
Recommended Wire Sizes
Wire Area (mm2) Wire Area Max Current Wire Size AWG
(Circular mils) (Approx. Amp) No.
0.75 1,480 15
0.82 1,618 16 18
1 1,974 19
1.31 2,585 22 16
1.5 2,960 24
2.08 4,105 29 14
2.5 4,934 32
3.31 6,532 37 12
4 7,894 42
5.26 10,381 50 10
6 11,841 54
8.36 16,499 65 8
10 19,735 73
13.3 26,248 87 6
16 31,576 98
21.15 41,740 116 4
25 49,338 129
33.6 66,310 154 2
35 69,073 158
42.4 83,677 178 1

Wire Area (mm2) Wire Area Max Current Wire Size AWG
(Circular mils) (Approx. Amp) No.
50 98,676 198
53.5 105,584 206 1/0
67.4 133,016 239 2/0
70 138,147 245
85 167,750 273 3/0
95 187,485 292
107 211,167 317 4/0
120 236,823 344
127 250,000 354 250 MCM
150 296,029 391
185 365,102 448
240 473,646 528
253 500,000 546 500 MCM
300 592,058 608
400 789,410 726
6.8.2 Low-voltage Shielded Cable

This section defines the minimum requirements for low-voltage shielded cable. These
guidelines should be used along with the level practices and routing guidelines provided
previously.
Note The specifications listed are for sensitive computer-based controls. Cabling for less
sensitive controls should be considered on an individual basis.

6.8.2.1 Single-conductor Shielded Cable, Rated 300 V
• 18 AWG minimum, stranded single-conductor insulated with minimum 85% to 100%
coverage shield
• Protective insulating cover for shield
• Wire rating: 300 V minimum
• Maximum capacitance between conductor and shield: 492 pF/m (150 pF/ft)
6.8.2.2 Multi-conductor Shielded Cable, Rated 300 V

• 18 AWG minimum, stranded conductors individually insulated per cable with
minimum 85 to 100% coverage shield
• Mutual capacitance between conductors with shield grounded: 394 pF/m (120 pF/ft)
maximum
• Capacitance between one conductor and all other conductors and grounded shield:
213 pF/m (65 pF/ft)
6.8.2.3 Shielded Twisted Pair (STP) Cable, Rated 300 V

• Two 18 AWG minimum, stranded conductors individually insulated with minimum
85 to 100% coverage shield
• Mutual capacitance between conductors with shield grounded: 394 pF/m (120 pF/ft)
maximum
• Capacitance between one conductor and the other conductor and grounded shield:
213 pF/m (65 pF/ft) maximum
6.8.2.4 Unshielded Twisted Pair (UTP) Cable (for Data

Highways and IONet)
• High-quality, category 5e UTP cable, for 10/100Base-TX Ethernet
• Four pairs of twisted 22 AWG or 24 AWG wire
• Protective plastic jacket
• Impedance: 75 – 165 Ω
• Connector: RJ45 UTP connector for solid wire

6.8.2.5 Serial Modbus RS-232C Communications
• Serial Modbus communication from the WorkstationST computer: for short distances
use RS-232C cable; for distances over 15 m (49.21 ft) add a modem
• Serial Modbus communication from the UCCA controller COM2 port: for use on
small systems, RS-232C cable with Micro-D adapter cable (GE catalog No.
336A4929G1). For longer distances over 15 m (49.21 ft), add a modem.
6.8.2.6 Instrument Cable, 4 – 20 mA

• With Tefzel® insulation and jacket: Belden® catalog no. 85231 or equivalent
• With plastic jacket: Belden catalog no. 9316 or equivalent
6.8.2.7 Fiber-optic Cable, Outdoor Use (Data Highways)

• Multi-mode fiber, 62.5/125 µ core/cladding, 850 nm infrared light
• Four sub-cables with elastomeric jackets and aramid strength members, and plastic
outer jacket
• Cable construction: flame retardant pressure extruded polyurethane. Cable diameter:
8.0 mm (0.31 in). Cable weight: 65 Kg/km
• Optical Cable Corporation part number: RK920929-A
Never look directly into a fiber. Although most fiber links use
light-emitting diodes, which cannot damage the eyes, some
longer links use lasers, which can cause permanent eye damage.
Warning
6.8.2.8 Fiber-optic Cable, Heavy Duty Outdoor Use

• Four sub-cables with elastomeric jackets and aramid strength members, and armored
outer jacket
• Cable construction: flame retardant pressure extruded polyurethane. Armored with
0.155 mm (0.01 in) steel tape, wound with 2 mm (0.08 in) overlap, and covered with
polyethylene outer jacket, 1 to 1.5 mm (0.04 to 0.06 in) thick. Cable diameter: 13 mm
(0.51 in). Cable weight: 174 Kg/km
• Optical Cable Corporation part number: RK920929-A-CST

6.8.2.9 Fiber-optic Cable, Indoor Use (Data Highways)
• Twin plastic jacketed cables (Zipcord) for indoor use
• Cable construction: tight-buffered fibers surrounded by aramid strength members
with a flexible flame retardant jacket. Cable dimensions: 2.9 mm (0.11 in) diameter x
5.8 mm (0.23 in) width. Cable weight: 15 Kg/km
• Corning Cable Systems part number: 002K58-31141–24
Media converters should not be used on the network to

convert between copper and fiber media because they use a
store and forward type of mechanism that introduces time
delays into the packet transmission. This would cause a
deviation from system design assumptions and possibly result
Attention in erratic network operation.
6.8.2.10 Single-mode Fiber-optic Cable (SMF), Indoor Use

(UDH Only)
• Single-mode fiber-optic cable is validated for use on the UDH network.
• SMF cable lengths can be zero to 15 km (9.32 mi) in length.
• SMF cables MUST be terminated and/or spliced by a certified fiber-optic cable
installer. SMF cable CANNOT be terminated and/or spliced by installations
engineers.
• SMF cables are 8.3/125 µm Core/Cladding diameter with a numeric aperture of 0.13.
• Optical Cable Corporation part numbers: OC041214-01, -02, -03, and -04.

6.9 Connecting the System
The cabinets come complete with internal cabling. Power cables from the power
distribution module to the control modules, interface modules, and terminal boards are
secured by plastic cable cleats located behind the riser brackets. The mounting brackets
and plates cover most of this cabling.
6.9.1 I/O Wiring

I/O connections are made to terminal blocks on the control system terminal boards.
Shielding connections to the shield bar located to the left of the terminal board are
displayed in the following figure.
I/O Wiring Shielding Connections to Ground Bar at Terminal Board
The grounded shield bars provide an equipotential ground plane to which all cable shield
drain wires should be connected, with as short a pigtail as practical. The length should not
exceed 5 cm (2 in) to reduce the high-frequency impedance of the shield ground.
Reducing the length of the pigtail should take precedence over reducing the length of
exposed wire within the cabinet. Pigtails should not be connected except at the grounding
bars provided, to avoid loops and maintain a radial grounding system. Shields should be
insulated up to the pigtail. In most instances, shields should not be connected at the far
end of the cable, to avoid circulating power-frequency currents induced by pickup.
A small capacitor can be used to ground the far end of the shield, producing a hybrid
ground system, improving noise immunity. Shields must continue across junction boxes
between the control and the turbine, and should match up with the signal they are
shielding. Avoid hard grounding the shield at the junction boxes, but small capacitors to
ground at junction boxes may improve immunity.

6.9.2 Installing Ethernet
Refer to the section, Cable The data highways use a number of 100Base-TX segments and some fiber-optic
Separation and Routing. segments. These guidelines comply with IEEE 802.3 standards for Ethernet. For details
on installing individual Ethernet LAN components, refer to the instructions supplied by
the manufacturer of that equipment.
If the connection within a building and the sites share a common ground, it is acceptable
to use 100Base-TX connections. If connecting between buildings, or there are differences
in ground potential within a building, or distances exceed 100 m (328 ft), then
100Base-FX fiber is required.
6.10 Startup Checks

All control system panels have cables pre-installed and factory-tested before shipment.
However, final checks should be made after installation and before starting the
equipment.
This equipment contains a potential hazard of electrical shock

or burn. Power is provided by the control system to various
input and output devices. External sources of power may be
present in the control system that are NOT switched by the
control power circuit breaker(s). Before handling or connecting
Warning any conductors to the equipment, use proper safety precautions
to ensure all power is turned off.
For equipment grounding Inspect the cabinet components for any damage possibly occurring during shipping.
instructions, refer to the Check for loose cables, wires, connections, or loose components, such as relays or
section, Grounding. retainer clips. Report all damage that occurred during shipping to GE Product Service.
Deposits containing ionic contaminants such as salt are

difficult to remove completely, and may combine with
moisture to cause irreparable damage to the boards.
Attention

6.10.1 Power Wiring and Circuit Checks
The IS220JPDF module must The 125 V dc supply must be installed and maintained so that it meets requirements of
provide the single, monitored, IEC 61010-1 cl. 6.3.1 to be considered Not Hazardous Live. The BJS berg jumper must
ground reference point for the be installed in the JPDF to provide the monitored ground reference for the 125 V dc. If
125 V dc system. there are multiple JPDFs connected to the dc mains, only one should have the Berg
jumper installed. The dc mains must be floated (isolated from ground) if they are
connected to a 125 V dc supply (battery).
This equipment contains a potential hazard of electric shock or

burn. Only personnel who are adequately trained and
Warning
The following steps should be completed to check the cabinet wiring and circuits.
Ø To check the power wiring

1. Ensure that all incoming power wiring agrees with the electrical drawings, supplied
with the panel, and is complete and correct.
2. Ensure that the incoming power wiring conforms to approved wiring practices as
described previously.
3. Ensure that all electrical terminal connections are tight.
4. Ensure that no wiring has been damaged or frayed during installation. Replace if
necessary.
5. Check that incoming power (125 V dc, 115 V ac, 230 V ac) is the correct voltage and
frequency, and is clean and free of noise. Make sure the DACA converters, if used,
are set to the correct voltage by selecting the JTX1 (115 V ac) or JTX2 (230 V ac)
jumper positions on the top of the converter.
6. If the installation includes more than one JPDF on an interconnected 125 V dc
system, the BJS jumper must be installed in one and only one JPDF. This is because
the parallel connection of more than one ground reference circuit will reduce the
impedance to the point where the 125 V dc no longer meets the not hazardous live
requirement.
Verifying that the 125 V dc is properly grounded. A qualified person using appropriate
safety procedures and equipment should make tests. Measure the current from first the
P125 V dc, and then the N125 V dc, using a 2000 Ω, 10 W resistor to the protective
conductor terminal of the Mark VIe control in series with a dc ammeter. The measured
current should be 1.7 to 2.0 mA, (the tolerance will depend on the test resistor and the
JPDF tolerances). If the measured current exceeds 2.0 mA, the system must be cleared of
the extra ground(s). A test current of about 65 mA, usually indicates one or more hard
grounds on the system, while currents in multiples of 1 mA usually indicate more than
one BJS jumper is installed.
Note At this point the system is ready for initial application of power.

7 Software Tools
This chapter summarizes the tools used for configuring, loading, and operating the Mark
VIe control system. These include the ToolboxST application, WorkstationST application,
HMI, and the Historian.
7.1 ToolboxST Application

Refer to GEH-6700, ToolboxST The ToolboxST application is a Windows-based software for configuring and maintaining
User Guide for Mark VIe the Mark VIe control. The software must run on a Pentium 2.8 GHz or faster with 3 GB
Control. RAM or more.
Features include:
• System component layout

• Configure, edit, and view real-time Mark VIe control application code
• EGD editor
• Hardware diagnostic alarm viewer
• Password protection
• Trending
Software Tools GEH-6721Y System Guide 139

7.2 WorkstationST Application
The WorkstationST application is used to managing the HMI, Historian, and Alarm
Viewer, as well as provides an interface to third-party devices.
7.2.1 Alarm Viewer

This is a valuable tool to aid in the analysis of the system, especially after an upset. It
displays and manages live and historical alarm and event information from a computer
configured with the WorkstationST application and running the Alarm Server. Alarm and
event information is displayed using advanced filtering and sorting capabilities, and
functions are available including Acknowledging, Locking, and Silencing alarms and
events. The following information can be generated:
• Alarms
• Events
• Holds
• SOE
• Diagnostics
7.2.2 OPC Server

The WorkstationST OPC server provides a standards-based interface to the runtime
database or third-party interfaces. The OPC server conforms to the 2.0 data access
standards. Fundamentally, the OPC standard defines two software roles, OPC clients and
OPC servers. In general, clients are consumers of automation information and servers are
producers of the same information.
OPC is a technology standard initially developed by a group of automation industry

companies and now managed by the not-for-profit organization called the OPC
Foundation. The standard was developed to provide a common de-coupling mechanism
for automation system software components. OPC provides for simpler integration of
automation software components from multiple vendors.

7.3 Human-machine Interface (HMI)
The Human-machine Interface (HMI) is the main operator interface to the Mark VIe
control system. The HMI is a computer with a Windows operating system, WorkstationST
application, and CIMPLICITY graphics user interface (GUI), communicating with the
Mark VIe controllers over Ethernet.
7.3.1 Basic Description

The HMI for Mark VIe controls consists of two distinct elements:
• WorkstationST Server
• Signal database
The WorkstationST server is the hub of the system, channeling data between the UDH
and the PDH, and providing data support and system management. The server also has
the responsibility for device communication for both internal and external data
interchanges.
The Signal database establishes signal management and definition for the control system,
provides a single repository for system alarm messages and definitions, and contains
signal relationships and correlation between the controllers and I/O. It is used for system
configuration, but not required for running.

7.3.2 Product Features
The HMI contains a number of product features important for plant control:
• Dynamic graphics
• Alarm displays
• Process variable trending
• Point control panel right-click menu
• HMI access security
The graphic system performs key HMI functions and provides the operator with real time
process visualization and control using the following:
CimEdit is an object-oriented program that creates and maintains the users graphic
screen displays. Editing and animation tools, with the familiar Windows environment,
provide an intuitive, easy to use interface. Features include:
• Standard shape library

• OLE
• Movement and rotation animation
• Filled object capabilities, and interior and border animation
Optional features include the CimView is the HMI runtime portion, displaying the process information in graphical
Web Gateway that allows formats. In CimView the operator can view the system screens, and screens from other
operators to access HMI data applications, using OLE automation, run scripts, and get descriptions of object actions.
from anywhere in the world Screens have a one-second refresh rate, and a typical graphical display that takes only one
over the Internet. second to repaint.
Alarm Viewer provides alarm management functions, such as sorting and filtering by
priority, by unit, by time, or by source device. Also supported are configurable alarm field
displays, and embedding dynamically updated objects into CimView screens.
Third-party interfaces allow Trending, based on ActiveX® technology, gives users data analysis capabilities. Trending
the HMI to exchange data with uses data collected by the HMI, or data from other third-party software packages or
DCS systems, PLCs, I/O interfaces. Trending includes multiple trending charts per graphic screen with unlimited
devices, and other computers. pens per chart, and the operator can resize or move trend windows to convenient locations
on the display.
Point control panel is a right-click menu, which is normally used during troubleshooting
to access variables for trends and watch windows.

7.4 PI-based or Proficy-based Historian
Refer to GEH-6744 (PI-based The Historian is a data archival system based on client-server technology. This provides
Historian) or GEH-6745 data collection, storage, and display of power island and auxiliary process data.
(Proficy-based Historian) for Depending on the requirements, the product can be configured for just turbine-related
more information. data, or for broader applications that include BoP process data. Flexible tools enable the
operator to quickly generate custom trends and reports from the archived process data.
The Historian combines high-resolution digital event data from the turbine controller with
process analog data, creating a sophisticated tool for investigating cause-effect
relationships.
7.4.1 System Configuration

The Historian provides historical data archiving and retrieval functions. When required,
the system architecture provides time synchronization to ensure time coherent data.
Turbine controller data is accessed through the UDH as displayed in the following figure.
Data Transmission to the Historian and HMI
Additional Historian data acquisition is performed through Modbus and/or Ethernet-based

interfaces. Data from devices such as Bently Nevada* condition monitors, or third-party
programmable logic controllers (PLCs) is usually obtained through Modbus, while
Ethernet is the preferred communication channel for GE Intelligent Platforms PLC
products. The HMI and other operator interface devices communicate to the Historian
through the PDH. Network technology provided by the Windows operating system allows
interaction from network computers, including query and view capabilities, using the
Historian Client Tool Set. The interface options include the ability to export data into
spreadsheet applications.

7.4.2 System Capability
The Historian provides an Packages of 1,000, 5,000, or 10,000 point tags* can be configured and collected from
online historical database for multiple process controllers. A typical turbine control application uses less than 1,000
collecting and storing data points of time-tagged analog and discrete data per unit. The length of time that the data is
from the control system. stored on disk, before offline archiving is required, depends upon collection rate,
dead-band configuration, process rate of change, and the disk size.
7.4.3 Data Flow

The Historian has three main functions:
Function Description
Data collection Data is collected over the UDH and Modbus.
Data storage Stored in the Exception database for SOE, events, and alarms
Stored in the archives for analog and Boolean values
Data retrieval Data can be retrieved through a web browser or a standard trend
screen.

Data Flow Overview

7.4.3.1 Data Collection Details
The Historian is configured to collect data from every device in its Consumed Device
List. A variable is configured for collection if its Historian Deadband property is defined
and its EGD Page property is assigned. For Boolean variables, the Deadband property
must be changed from Not Logged to Logged on Change. When the data value for a
Boolean variable changes, the data value is stored by the Historian. For variables with
numeric data types, the Deadband property must be changed from Not Logged to a
non-negative number. When the data value for a numeric data type variable changes by
the defined Historian Deadband, the value is written to the Historian.
Time synchronization and time The Historian is typically configured to be the Alarm Server and stores alarm and event
coherency are extremely data from every device in its Consumed Device List. When an alarm or event state change
important, especially when an occurs, it is sent to the Historian's Alarm Server. Contact inputs or SOE changes are
operator or maintenance scanned, sent to the Historian, and stored in the Alarm Server database with the alarms
technician is attempting to and event state changes. These data points are time-tagged by the controller, which offers
analyze and determine the root system time-sync functions as an option to ensure that total integrated system data remain
cause of a problem. time-coherent.
Data points that are configured for collection in the archives are sampled once per second
from the OPC® DA Server. Analog data that exceeds an exception Deadband and digital
data that changes state is sent to the archives. A third-party compression algorithm is used
to determine when to save a value. This allows the Historian to keep orders of magnitude
and more available data online than in conventional scanned systems.

7.5 Trender Tools for Process Data (Trends)
This is the graphical interface for trending analog or digital points. It is fully configurable
and can auto-range the scales or set fixed indexes. For accurate read out, the trend cursor
displays the exact value of all points trended at a given point in time. It can be set up to
mimic strip chart recorders, analyze the performance of particular parameters over time,
or help troubleshoot root causes of issues.
Trender Tool for Real-time and Historical Data
7.6 uOSM
The Universal Onsite Monitor (uOSM) is a separate computer module that is the GE
Services portal to provide warranty and contractual service offerings. The uOSM has no
operator interface and does not expose its data directly to the end user. The uOSM
monitors turbine-operating data and periodically uploads the data to the GE Services
Operations Center for analysis. Fleet analysis data is collected to improve overall system
availability, performance, and individual event information for root cause analysis.

Notes

Glossary of Terms
application code Software that controls the machines or processes, specific to the
application.
Balance of Plant (BOP) Plant equipment other than the turbine that needs to be
controlled.
baud A unit of data transmission. Baud rate is the number of bits per second
transmitted.
bit Binary Digit. The smallest unit of memory used to store only one piece of
information with two states, such as One/Zero or On/Off. Data requiring more than two
states, such as numerical values 000 to 999, requires multiple bits (see Word).
block Instruction blocks contain basic control functions, which are connected together
during configuration to form the required machine or process control. Blocks can perform
math computations, sequencing, or continuous control. The toolbox receives a description
of the blocks from the block libraries.
board Printed wiring board.
Boolean Digital statement that expresses a condition that is either True or False. In the
toolbox, it is a data type for logical signals.
broadcast In computer networking broadcast is traffic that is simultaneously

addressed to all computers connected to the network. This type of addressing is used in
legacy control applications.
bus An electrical path for transmitting and receiving data.
byte A group of binary digits (bits); a measure of data flow when bytes per second.
CIMPLICITY Operator interface software configurable for a wide variety of control

applications.
Computer Operator Interface (COI) Interface that consists of a set of product and
application specific operator displays running on a small cabinet computer hosting
Embedded Windows NT®.
configure To select specific options, either by setting the location of hardware jumpers
or loading software parameters into memory.
Control Data Highway (CDH) Redundant Ethernet communication network allows

two separate controllers to communicate with each other.
Cyclic Redundancy Check (CRC) Detects errors in Ethernet and other

transmissions.
data server A computer that gathers control data from input networks and makes the
data available to computers on output networks.
GEH-6721Y Glossary of Terms 149

device A configurable component of a process control system.
Distributed Control System (DCS) Control system, usually applied to control of

boilers and other process equipment.
Ethernet LAN with a 10/100 M baud collision avoidance/collision detection system

used to link one or more computers together. Basis for TCP/IP and I/O services layers that
conform to the IEEE 802.3 standard, developed by Xerox®, DEC®, and Intel®.
Ethernet Global Data (EGD) Control network and protocol for the controller.
Devices share data through EGD exchanges (pages).
EX2100 Excitation Control Latest version of GE generator exciter control; regulates

the generator field current to control the generator output voltage.
fanned input An input to the terminal board that is connected to all three TMR I/O
boards.
firmware The set of executable software that is stored in memory chips that hold their
content without electrical power, such as EEPROM.
flash A non-volatile programmable memory device.
forcing Setting a live signal to a particular value, regardless of the value blockware or
I/O is writing to that signal.
frame rate Basic scheduling period of the controller encompassing one complete
input-compute-output cycle for the controller. It is the system-dependent scan rate.
function The highest level of the blockware hierarchy, and the entity that corresponds
to a single .tre file.
gateway A device that connects two dissimilar LANs or connects a LAN to a

wide-area network (WAN), computer, or a mainframe. A gateway can perform protocol
and bandwidth conversion.
I/O device Input/output hardware device that allows the flow of data.
I/O drivers Interface the controller with input/output devices, such as sensors, solenoid
valves, and drives, using a choice of communication networks.
IONet The Mark VIe I/O Ethernet communication network.
IP Address The address assigned to a device on an Ethernet communication network.
item A line of hierarchy of the outline view of the toolbox application, which can be
inserted, configured, and edited (such as Function or System Data).
logical A statement of a true sense, such as a Boolean.
LS2100 Static Starter control GE’s current state-of-the-art control for static starter
control systems, used to bring a gas turbine up to starting speed.
150 Mark VIe Control, Volume I System Guide

macro A group of instruction blocks (and other macros) used to perform part of an
application program. Macros can be saved and reused.
Modbus A serial communication protocol developed by Modicon for use between

PLCs and other computers.
module A collection of tasks that have a defined scheduling period in the controller.
multicast The delivery of a message or Information to a group of destination

computers simultaneously in a single transmission from the source.
online Online mode provides full CPU communications, allowing data to be both read
and written. It is the state of the toolbox when it is communicating with the system for
which it holds the configuration. Online is also, a download mode where the device is not
stopped and then restarted.
period The time between execution scans for a Module or Task. Also a property of a
Module that is the base period of all of the Tasks in the Module.
pin Block, macro, or module parameter that creates a signal used to make
interconnections.
Plant Data Highway (PDH) Ethernet communication network between the HMI
Servers and the HMI Viewers and workstations.
Potential Transformer (PT) Measures voltage in a power cable.
Programmable Logic Controller (PLC) Designed for discrete (logic) control of

machinery. It also computes math (analog) function and performs regulatory control.
QNX A real time operating system used in the controller.
Relay Ladder Diagram (RLD) A ladder diagram that represents a relay circuit.
Power is considered to flow from the left rail through contacts to the coil connected at the
right.
Sequence of Events (SOE) A high-speed record of contact transitions taken during

a plant upset to allow detailed analysis of the event.
server A computer that gathers data over the Ethernet from plant devices, and makes
the data available to computer-based operator interfaces known as viewers.
signal The basic unit for variable information in the controller.
simplex Operation that requires only one set of control and I/O, and generally uses
only one channel. The entire Mark VIe control system can operate in simplex mode.
simulation Running a system without all of the configured I/O devices by modeling
the behavior of the machine and the devices in software.
Software Implemented Fault Tolerance (SIFT) A technique for voting the three
incoming I/O data sets to find and inhibit errors. Note that control also uses output
hardware voting.
GEH-6721Y Glossary of Terms 151

TCP/IP Communication protocols developed to inter-network dissimilar systems. It is a
de facto UNIX standard, but is supported on almost all systems. TCP controls data
transfer and IP provides the routing for functions, such as file transfer and e-mail.
ToolboxST A Windows-based software package used to configure the control systems,

exciters, and drives.
trend A time-based plot to show the history of values, similar to a recorder, available
with the ControlST Historian and the ToolboxST application.
Triple Module Redundancy (TMR) An operation that uses three identical sets of
control and I/O (channels R, S, and T) and votes the results.
Unit Data Highway (UDH) Connects the controllers, static starter control system,
excitation control system, PLCs, and other GE provided equipment to the HMI Servers.

E
Index Electrical 85
Electromagnetic Compatibility
Directive (EMC) 85
A Elevation 92
Environment 85
Acronyms and Abbreviations 9
Operating 91
Applications 7
Ethernet
Global Data (EGD) 72
C GSM 69
cable
fiber-optic 122–125, 135 F
Guidelines 123
Fiber-Optic Cables 122
Installation 125
Forcing 47
Instrument 134
Frequency Variations 86
Routing Guidelines 121
RS-232C 134
Separation and Routing 116 G
shielded 131–132 Grounding 107
SMF 135 Notes on 113
UTP 133 System 109
codes 83 Guidelines
Command Action 49 Cableway Spacing 118
Communication
Loss 45
Communications 60 H
RS-232C 134 Harmonic Distortion 86
Component Sources 130 Historian 143
configuration configuration 143
dual 74 Data collection 146
dual network 52 Human-machine Interface (HMI) 61
TMR 73
Contaminants 92
Control Data Highway (CDH) 58
I
controller I/O 62
overview 12 Pack 14
Controller Peer 47
UCCx 13 Wiring 136
ControlST Installation 95
Historian 143 Support Drawings 102
CPCI 11 IONet Components 127
D L
Data Highway Line Variations 86
Plant 54 Low Voltage Directive 85
Directive
Electromagnetic Compatibility 85 M
Disagreement Detector 47
Dual Controller 29 Median Value Analog 46
MTBF 41
GEH-6721Y Index 153

N W
NEMA 60 Wire Sizes 131
network
layers 51
redundancy 53
Network Time Protocol (NTP) 74
O
overspeed protection 49
P
Power Requirements 100
Power Sources 26, 100
Processing
Input 34
Output 38
R
Rate of Response 47
redundancy
network 53
Redundancy Options 27
S
Safety Standards 83
Simplex Controller 28
standards 83
State Exchange 45
Storage 99
Supply Voltage 86
system
Considerations 124
T
Terminal Board 15
Turbine Protection 49
Two Out of Three Logic 46
U
UDH Communicator 56
V
Vibration 92
Voltage Unbalance 86
Voting 45

1501 Roanoke Blvd. GE Proprietary and Internal (Class II) – This document contains proprietary information of GE and
Salem, VA 24153 USA is intended for internal use only. It may not be used, shown, reproduced, or disclosed outside of GE
without the express written consent of GE.

GEH-6721 Vol I PDF

Uploaded by

Copyright:

Available Formats

GEH-6721 Vol I PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GEH-6721 Vol I PDF

Uploaded by

Copyright:

Available Formats

GEH-6721Y

Mark* VIe Control, Volume I

Revised: Jan 2014

© 2004 - 2014 General Electric Company, All rights reserved.

We would appreciate your feedback about our documentation.

Section Power Distribution, correction to controller power sources

Chapter, Controllers & Switches Moved to GEH-6721_Vol_II

Chapter, Maintenance & Moved to GEH-6721_Vol_II

Indicates a procedure, condition, or statement that, if not

Indicates a procedure, condition, or statement that, if not

Indicates a procedure, condition, or statement that should be

GEH-6721Y System Guide 3

This equipment contains a potential hazard of electric shock,

Isolation of test equipment from the equipment under test

Warning To minimize hazard of electrical shock or burn, approved

To prevent personal injury or equipment damage caused by

Always ensure that applicable standards and regulations are

4 GEH-6721Y Mark VIe Control, Volume I System Guide

GEH-6721Y System Guide 5

6 GEH-6721Y Mark VIe Control, Volume I System Guide

Triple Redundant Mark VIe Control System

Introduction GEH-6721Y System Guide 7

GEH-6723 Mark VIeS Safety Control Safety Instruction Guide

GEH-6700 ToolboxST* User Guide for Mark VIe Control

GEH-6721_Vol_III Mark VIe Control Volume III Diagnostics and Troubleshooting

GEH-6744 PI®-based Historian with ControlST Software Suite

GEH-6705 ToolboxST User Guide for Mark VIeS Safety Control

GEH-6724 Mark VIe Control Initial Startup Instruction Guide

GEH-6741 Sequential Function Chart Application Guide

GEH-6742 Mark VIe Virtual Controller User Guide

GEH-6761 Mark VIe Control FOUNDATION Fieldbus™ Interface Application Guide

GEH-6762 Mark VIe Control FOUNDATION Fieldbus™ Interface User Guide

GEH-6779 Mark VIe Control Renewable Energy Distributed I/O Modules

GEH-6808 ControlST Software Suite How-to Guides

GEI-100682 Mark VIe Control Standard Block Library

GEI-100681 Mark VIe Control Legacy Block Library

GEI-100680 Mark VIe Control Turbine Block Library

GEI-100721 Programmable Logic Controllers with the Mark VIe DCS

GEI-100795 Trender for the ToolboxST Application Instruction Guide

GEI-100620 WorkstationST Alarm Viewer Instruction Guide

8 GEH-6721Y Mark VIe Control, Volume I System Guide

ASK Automatic Station Keeping

AWG American Wire Gauge

BoP Balance of Plant

CMOS Complementary Metal-Oxide Semiconductor

COI Computer Operator Interface

CPCI CompactPCI 6U high enclosure

CRC Cyclic Redundancy Code/Check

DAC Digital-to-Analog Converter

DCE Data Communication Equipment

DCS Distributed Control System

DHCP Dynamic Host Configuration Protocol

DRAM Dynamic Random Access Memory

DTE Data Terminal Equipment device

EGD Ethernet Global Data

EMI Electromagnetic Interference

ERA Electrical Riser Angle

FTI Flow Totalizer Input (XMT868i Panametrics Ultrasonic Flow Transmitter)

GPS Global Position System