Sonatrach Mark - VI Maintenance VOL - I PDF

GE
Oil & Gas
Speedtronic Mark VI
Maintenance
Course Description
This course is designed to enable engineers to confidently calibrate the controls and troubleshoot
related to the Speedtronic Mark VI Control Systems.
Prerequisite:
- Personnel must have already completed Mark V Operation 5 days
Expected Audience:
 Maintenance-Control-ING (Nouveaux & Anciens)
Course Content
1. INTRODUCTION TO SPEEDTRONIC MARK VI

 General overview of control system
 TMR and Simplex Control overview
 Control Panel architecture
 Operator Interface HMI
 Panel Documentation
2. SPEEDTRONIC MARK VI HARDWARE DESCRIPTION

 Network topology
 Power distribution
 Racks, Processors, I/O cards and termination boards
 Most used I/O cards detailed descriptions
 Abbreviations and conventions
3. GENERAL SOFTWARE DESCRIPTION

 Operating System & Software Structure
 Toolbox, Cimplicity and TCI descriptions
GE
Oil & Gas
4. TOOLBOX SOFTWARE CONFIGURATION

 General I/O signals configuration
 Sequences view and investigation
 Control constants
 Compiling Configuration Program
 Trend recorder
5. DOWNLOAD FUNCTIONS
 Flash Memory Programming
 Product code
 Application code
 IO configuration
 Firmware
6. CIMPLYCITY
 Screens Navigation
 Applications
 Alarm display
7. OPERATING PROCEDURES AND INVESTIGATION

 Permissive to Start/ Crank/ Fire
 Startup and Shutdown Sequence
 Practice
8. TROUBLESHOOTING
 LVDT Calibration (AUTOCAL)

 Process Alarm investigation
 Diagnostic Alarms
 Board replacement procedure
 Ground fault detection
9. QUESTION AND ANSWER
Course Duration: 5 Days

GE
Oil & Gas
SPEEDTRONIC MARK* VI - Maintenance

TRAINING MANUAL - VOL I
Customized for: SONATRACH (ALGERIA)

GE
Oil & Gas
GE Oil & Gas
Customer Training Job: 0622457
Customer : SONATRACH (ALGERIA)
This manual contains proprietary information of GE Oil & Gas – Nuovo Pignone
S.p.A. (“GE Oil & Gas”), and is furnished to its customers solely for customer
training courses purposes.
This manual shall not be reproduced in whole or in part nor shall its contents
be disclosed to any third party without the written approval of GE Oil & Gas.
The instructions and information contained in the manual do not purport to
cover all details or variations in equipment, or to provide for every possible
contingency to be met during installation, operation, and maintenance.
Should further information be desired or should particular problems arise that

are not covered sufficiently for the purchaser’s purpose, the matter should
be referred to GE Oil & Gas.
Reviewed Verified Validate

Marco Saya Sandro Fantini
Massimiliano Romizi Control Customer Training
Manual Specialist Instructor Leader Manager
07/15/2013 07/18/2013 07/18/2013
GE Oil & Gas
GE
Oil & Gas
SPEEDTRONIC MARK* VI
INDEX
VOL. 1
SEZ .1 Training documents
- GEH-6421 : Mark* VI Control System Guide, Volume I
- GEH-6421 : Mark* VI Control System Guide, Volume II
- GEH-6403 : Control System Toolbox For a Mark VI Turbine
Controller
- GEH-6126 Volume I : Human-Machine Interface for
Speedtronic Turbine Control
- GEH-6126 Volume II : Human-Machine Interface for
- GEI-100278 : Data Historian
VOL. 2
SEZ. 1 Training Slides
SEZ .2 Drawings - FR. 5 C - 1605987 Page 161
SEZ .3 Drawings - PGT25+ - 1608994 Page 173

GE Oil & Gas
GE
Oil & Gas
SPEEDTRONIC MARK* VI
INDEX
VOL. 1
SEZ .1 Training documents
- GEH-6421 : Mark* VI Control System Guide, Volume I
- GEH-6421 : Mark* VI Control System Guide, Volume II
- GEH-6403 : Control System Toolbox For a Mark VI Turbine
Controller
- GEH-6126 Volume I : Human-Machine Interface for
- GEH-6126 Volume II : Human-Machine Interface for
- GEI-100278 : Data Historian

GE Oil & Gas
GE Energy
Mark* VI Control
System Guide, Volume I
GEH-6421L
g
Summarized 11 of 1016
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.
This document contains proprietary information of General Electric Company, USA and
is furnished to its customer solely to assist that customer in the installation, testing,
operation, and/or maintenance of the equipment described. This document shall not be
reproduced in whole or in part nor shall its contents be disclosed to any third party
without the written approval of GE Energy.
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.
If further assistance or technical information is desired, contact the nearest GE Sales or

Service Office, or an authorized GE Sales Representative.
© 2004 - 2007 General Electric Company, USA. All rights reserved.

Revised: 080130
Issued: 040120
* Trademark of General Electric Company

ARCNET is registered trademark of Datapoint Corporation.
AutoCAD is a registered trademark of Autodesk, Inc.
Belden is a registered trademark of Belden Electronic Wire and Cable of Cooper.
Celeron is a trademark of Intel Corporation.
CIMPLICITY is a registered trademark of GE Fanuc Automation North America, Inc.
Flamarrest is a trademark of Akzo Nobel N.V.
IEEE is a registered trademark of Institute of Electrical and Electronics Engineers.
Intel and Pentium are registered trademarks of Intel Corporation.
Kevlar is a registered trademark of E. I. du Pont de Nemours Company.
Keyphasor is a registered trademark of Bently Nevada Corporation.
Modbus is a registered trademark of Schneider Automation.
NEC is a registered trademark of the National Fire Protection Association.
PI DataLink is a registered trademark of OSI Software Inc.
POSIX is a registered trademark of the Institute of Electrical and Electronic Engineers (IEEE).
Proximitor and Velomitor are registered trademarks of Bently Nevada.
QNX is a registered trademark of QNX Software Systems, Ltd. (QSSL).
Siecor is registered trademark of Corning Cable Systems Brands, Inc.
Tefzel is a registered trademark of E I du Pont de Nemours Company.
Summarized
ThinWire is a trademark of Xerox Corporation.
Vibro-meter is a registered trademark of Vibro-Meter, Inc.
Windows and Windows NT are registered trademarks of Microsoft Corporation.
3M is a trademark of 3M Company.
12 of 1016
Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not

strictly observed, could result in personal injury or death.

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

strictly followed in order to optimize these applications.
Note Indicates an essential or important procedure, condition, or statement.
This equipment contains a potential hazard of electric shock
or burn. Only personnel who are adequately trained and
thoroughly familiar with the equipment and the instructions
should install, operate, or maintain this equipment.
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.
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.
Summarized
14 of 1016
Contents
Chapter 1 Overview 1-1

Introduction ...............................................................................................................................................1-1
Related Documents ...................................................................................................................................1-2
How to Get Help .......................................................................................................................................1-3
Acronyms and Abbreviations ....................................................................................................................1-3
Chapter 2 System Architecture 2-1

Introduction ...............................................................................................................................................2-1
System Components ..................................................................................................................................2-1
Control Cabinet ..............................................................................................................................2-1
I/O Cabinet.....................................................................................................................................2-1
Unit Data Highway (UDH) ............................................................................................................2-2
Human-Machine Interface (HMI) ..................................................................................................2-3
Control Operator Interface (COI)...................................................................................................2-3
Link to Distributed Control System (DCS)....................................................................................2-4
Plant Data Highway (PDH)............................................................................................................2-4
Operator Console ...........................................................................................................................2-4
EX2100 Exciter..............................................................................................................................2-5
Generator Protection ......................................................................................................................2-5
Static Starter Control System .........................................................................................................2-5
Control Module ..............................................................................................................................2-6
Interface Module ............................................................................................................................2-8
Controller .......................................................................................................................................2-9
VCMI Communication Board......................................................................................................2-10
IONet............................................................................................................................................2-11
I/O Boards....................................................................................................................................2-11
Terminal Boards...........................................................................................................................2-13
Power Sources..............................................................................................................................2-16
Turbine Protection Module ..........................................................................................................2-17
Operating Systems .......................................................................................................................2-18
Levels of Redundancy .............................................................................................................................2-18
Control and Protection Features ..............................................................................................................2-19
Triple Modular Redundancy ........................................................................................................2-19
TMR Architecture ........................................................................................................................2-20
TMR Operation ............................................................................................................................2-22
Designated Controller ..................................................................................................................2-22
Output Processing ........................................................................................................................2-23
Input Processing...........................................................................................................................2-25
State Exchange.............................................................................................................................2-27
Median Value Analog Voting ......................................................................................................2-28
Two Out of Three Logic Voter ....................................................................................................2-28
Disagreement Detector.................................................................................................................2-28
Forced Variables ..........................................................................................................................2-29
Peer I/O ........................................................................................................................................2-29
Command Action .........................................................................................................................2-29
Rate of Response..........................................................................................................................2-29
Failure Handling ..........................................................................................................................2-30
Turbine Protection...................................................................................................................................2-31
Reliability and Availability .....................................................................................................................2-32
Online Repair for TMR Systems..................................................................................................2-32
Summarized
Reliability.....................................................................................................................................2-33
GEH-6421L Mark VI Control System Guide Volume15

I of 1016 Contents • i
Third-Party Connectivity.........................................................................................................................2-34
Chapter 3 Networks 3-1

Introduction ...............................................................................................................................................3-1
Network Overview ....................................................................................................................................3-1
Network Layers ..............................................................................................................................3-2
Data Highways ..........................................................................................................................................3-4
Plant Data Highway (PDH)............................................................................................................3-4
Unit Data Highway (UDH) ............................................................................................................3-5
Data Highway Ethernet Switches...................................................................................................3-6
Selecting IP Addresses for UDH and PDH ....................................................................................3-7
IONet.........................................................................................................................................................3-7
IONet - Communications Interface ................................................................................................3-8
I/O Data Collection ........................................................................................................................3-9
Ethernet Global Data (EGD) .....................................................................................................................3-9
Modbus Communications........................................................................................................................3-11
Ethernet Modbus Slave............................................................................................................................3-12
Serial Modbus Slave................................................................................................................................3-13
Modbus Configuration .................................................................................................................3-14
Hardware Configuration...............................................................................................................3-15
Serial Port Parameters ..................................................................................................................3-16
Ethernet GSM..........................................................................................................................................3-17
PROFIBUS Communications..................................................................................................................3-18
Configuration ...............................................................................................................................3-19
I/O and Diagnostics......................................................................................................................3-20
Fiber-Optic Cables...................................................................................................................................3-20
Components..................................................................................................................................3-21
Component Sources......................................................................................................................3-23
Single-mode Fiber-optic Cabling ............................................................................................................3-24
IONet Components (Single-Mode Fiber) ................................................................................................3-25
Time Synchronization .............................................................................................................................3-26
Redundant Time Sources .............................................................................................................3-26
Selection of Time Sources............................................................................................................3-26
Chapter 4 Codes, Standards, and Environment 4-1

Introduction ...............................................................................................................................................4-1
Safety Standards ........................................................................................................................................4-1
Electrical....................................................................................................................................................4-1
Printed Circuit Board Assemblies ..................................................................................................4-1
Electromagnetic Compatibility Directive (EMC) 2004/108/EC ....................................................4-1
Low Voltage Directive 2006/95/EC...............................................................................................4-2
Supply Voltage...............................................................................................................................4-2
Environment ..............................................................................................................................................4-3
Storage ...........................................................................................................................................4-3
Operating........................................................................................................................................4-4
Elevation ........................................................................................................................................4-5
Contaminants..................................................................................................................................4-5
Vibration ........................................................................................................................................4-6
Packaging .......................................................................................................................................4-6
UL Class 1 Division 2 Listed Boards .............................................................................................4-6
Chapter 5 Installation and Configuration 5-1

Introduction ...............................................................................................................................................5-1
Installation Support ...................................................................................................................................5-1
Early Planning................................................................................................................................5-1
Summarized
GE Installation Documents ............................................................................................................5-1
ii • Contents 16 of 1016
GEH-6421L Mark VI Control System Guide Volume I
Technical Advisory Options ..........................................................................................................5-2
Equipment Receiving and Handling..........................................................................................................5-3
Weights and Dimensions...........................................................................................................................5-3
Cabinets..........................................................................................................................................5-3
Control Console (Example)............................................................................................................5-7
Power Requirements..................................................................................................................................5-8
Installation Support Drawings...................................................................................................................5-9
Grounding ...............................................................................................................................................5-11
Equipment Grounding..................................................................................................................5-12
Building Grounding System.........................................................................................................5-13
Signal Reference Structure (SRS) ................................................................................................5-13
Cable Separation and Routing .................................................................................................................5-18
Signal and Power Level Definitions.............................................................................................5-18
Cableway Spacing Guidelines......................................................................................................5-20
Cable Routing Guidelines ............................................................................................................5-22
Cable Specifications ................................................................................................................................5-23
Wire Sizes ....................................................................................................................................5-23
General Specifications .................................................................................................................5-24
Low Voltage Shielded Cable .......................................................................................................5-25
Connecting the System............................................................................................................................5-27
I/O Wiring....................................................................................................................................5-30
Terminal Block Features ..............................................................................................................5-31
Power System...............................................................................................................................5-31
Installing Ethernet ........................................................................................................................5-31
Startup Checks.........................................................................................................................................5-33
Board Inspections.........................................................................................................................5-33
Wiring and Circuit Checks...........................................................................................................5-36
Startup and Configuration .......................................................................................................................5-37
Topology and Application Code Download.................................................................................5-38
Online Download .........................................................................................................................5-39
Offline Download ........................................................................................................................5-40
Post-Download TMR Test ...........................................................................................................5-40
Controller Offline While System Online......................................................................................5-40
Offline Trip Analysis ...................................................................................................................5-41
Chapter 6 Tools and System Interface 6-1

Introduction ...............................................................................................................................................6-1
Toolbox .....................................................................................................................................................6-1
Configuring the Application ..........................................................................................................6-2
CIMPLICITY HMI ...................................................................................................................................6-3
Basic Description ...........................................................................................................................6-3
Product Features.............................................................................................................................6-4
Computer Operator Interface (COI) ..........................................................................................................6-5
Interface Features...........................................................................................................................6-6
Turbine Historian ......................................................................................................................................6-6
System Configuration.....................................................................................................................6-7
System Capability ..........................................................................................................................6-7
Data Flow.......................................................................................................................................6-7
Turbine Historian Tools .................................................................................................................6-8
Chapter 7 Maintenance and Diagnostics 7-1

Introduction ...............................................................................................................................................7-1
Maintenance ..............................................................................................................................................7-1
Modules and Boards.......................................................................................................................7-1
Component Replacement ..........................................................................................................................7-2
Replacing a Controller ...................................................................................................................7-2
Summarized
Replacing a VCMI .........................................................................................................................7-3
Replacing an I/O Board in an Interface Module ............................................................................7-3

I of 1016 Contents • iii
Replacing a Terminal Board...........................................................................................................7-4
Cable Replacement.........................................................................................................................7-5
Alarms Overview.......................................................................................................................................7-5
Process Alarms ..........................................................................................................................................7-6
Process (and Hold) Alarm Data Flow ............................................................................................7-6
Diagnostic Alarms .....................................................................................................................................7-7
Voter Disagreement Diagnostics....................................................................................................7-8
Totalizers ...................................................................................................................................................7-9
Troubleshooting.........................................................................................................................................7-9
I/O Board LEDs .............................................................................................................................7-9
Controller Failures .......................................................................................................................7-11
Power Distribution Module Failure..............................................................................................7-12
Online Download ....................................................................................................................................7-12
Preliminary Checks for Online Download ...................................................................................7-12
Control State.................................................................................................................................7-13
TMR Test Procedure ....................................................................................................................7-16
Chapter 8 Applications 8-1

Introduction ...............................................................................................................................................8-1
Generator Synchronization ........................................................................................................................8-1
Hardware ........................................................................................................................................8-1
Application Code ...........................................................................................................................8-3
Algorithm Descriptions ..................................................................................................................8-4
Configuration .................................................................................................................................8-7
VTUR Diagnostics for the Auto Synchronous Function................................................................8-9
VPRO Diagnostics for the Auto Synchronous Function ..............................................................8-10
Hardware Verification Procedure.................................................................................................8-10
Synchronization Simulation .........................................................................................................8-10
Overspeed Protection Logic ....................................................................................................................8-11
Power Load Unbalance............................................................................................................................8-34
Early Valve Actuation .............................................................................................................................8-38
Intercept Valve Trigger (IVT)......................................................................................................8-39
Early Valve Actuation (EVA) ......................................................................................................8-39
Fast Overspeed Trip in VTUR.................................................................................................................8-39
Compressor Stall Detection .....................................................................................................................8-42
Ground Fault Detection Sensitivity .........................................................................................................8-46
Analysis of Results.......................................................................................................................8-47
Glossary of Terms G-1
Index I-1
Summarized
iv • Contents 18 of 1016
CHAPTER 1
Chapter 1 Overview
Introduction
This document describes the Mark* VI turbine control system. Mark VI is used for
the control and protection of steam and gas turbines in electrical generation and
process plant applications.
The main functions of the Mark VI turbine control system are as follows:
• Speed control during turbine startup

• Automatic generator synchronization
• Turbine load control during normal operation on the grid
• Protection against turbine overspeed on loss of load
The Mark VI system is available as a simplex control or a triple modular redundant
(TMR) control with single or multiple racks, and local or remote I/O. The I/O
interface is designed for direct interface to the sensors and actuators on the turbine,
to eliminate the need for interposing instrumentation, and to avoid the reliability and
maintenance issues associated with that instrumentation.
Note To obtain the highest reliability, Mark VI uses a TMR architecture with
sophisticated signal voting techniques.
Summarized
I of 1016 Chapter 1 Overview • 1-1
The following figure shows a typical Mark VI control system for a steam turbine
with the important inputs and control outputs.
RS-232C
Mark VI I/O Board Rack

PC Interface
Laptop
Comm Controller VCCC
VSVO VTUR VAIC or VVIB VRTD VTCC VGEN
VCMI UCVX VCRC
Ethernet Data Highway
(48) Contact Inputs. 1 ms SOE
(24) Relays
(2) 3-Phase Gen/Line Voltage, (1) 3-Phase Gen. Current

(16) RTDs
Proximitors: (16) Vibration, (8) Position, (2) KP
(24) Thermocouples
Actuator
Actuator
Inlet Pressure
Trip
Generator
Speed
Extraction Pressure
Exhaust Pressure
Shaft Voltage & Current Monitor
Automatic Synchronizing
Vibration, Thrust, Eccentricity
Temperature (RTDs)
Temperature (Thermocouples)
Generator 3-Phase PTs & CT
Typical Turbine Control System
Related Documents
For additional information, refer to the following documents:
• GEH-6403 Control System Toolbox for a Mark VI Controller (for details of

configuring and downloading the control system)
• GEH-6422 Turbine Historian System Guide (for details of configuring and using
the Historian)
• GEH-6408 Control System Toolbox for Configuring the Trend Recorder (for
details of configuring the toolbox trend displays)
• GEI-100534, Control Operator Interface (COI) for Mark VI and EX2100
Systems
®
• GEI-100535, Modbus Communications
• GEI-100536, Profibus Communications
• GEI-100189, System Database (SDB) Server User's Guide
• GEI-100271, System Database (SDB) Browser
Summarized
1-2 • Chapter 1 Overview 20 of 1016
How to Get Help
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.
Acronyms and Abbreviations

ADL Asynchronous Device Language
ASCII America Standard Code for Information Interchange
BOP Balance of Plant
BIOS Basic Input/Output System
CCR Central Control Room
CMOS Complementary Metal-Oxide Semiconductor
COI Computer Operator Interface
CPU Central Processing Unit
CRC Cyclic Redundancy Code/Check
CT Current Transformer
DCE Data Communication Equipment
DCS Distributed Control System
DDE Data Distribution Equipment
DHCP Dynamic Host Configuration Protocol
DRAM Dynamic Random Access Memory
DTD Data Terminal Equipment Device
EGD Ethernet Global Data
EMC Electromagnetic Capability
EMI Electro-Magnetic Interference
EVA Early Valve Actuation
FE Functional Earth
FFT Fast Fourier Transform
FIT Failures in Time
GPS Global Position System
GSM GE Standard Messaging
GTS Global Time Source
HMI Human-Machine Interface
HRSG Heat Recovery Steam Generator
ICS Integrated Control System
® Institute of Electrical and Electronics Engineers
IEEE
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
® National Electrical Code
NEC
NEMA National Electrical Manufacturer’s Association
Summarized NFPA National Fire Protection Association

I of 1016 Chapter 1 Overview • 1-3
NTP Network Time Protocol
PDH Plant Data Highway
PE Protective Earth
PLU Power Load Unbalance
PDM Power Distribution Module
PLC Programmable Logic Controller
PPS Pulse per Second
PT Potential Transformer
RFI Radio Frequency Interference
RLD Relay Ladder Diagram
RPM Revolutions Per Minute
RPSM Redundant Power Supply Module
RTD Resistance Temperature Device
RTU Remote Terminal Unit
SDB Systems Database
SIFT Software Implemented Fault Tolerance
SOE Sequence of Events
SOF Start of Frame
SRS Single Reference Structure
TMR Triple Modular Redundant
UART Universal Asynchronous Receiver/Transmitter
UDH Unit Data Highway
UTC Coordinated Universal Time
VLAN Virtual Local Area Network
WAN Wide Area Network
Summarized
1-4 • Chapter 1 Overview 22 of 1016
CHAPTER 2
Chapter 2 System Architecture
Introduction
This chapter defines the architecture of the Mark VI turbine control system,
including the system components, the three communication networks, and the
various levels of redundancy that are possible. It also discusses system reliability and
availability, and third-party connectivity to plant distributed control systems.
System Components
The following sections define the main subsystems making up the Mark VI control
system. These include the controllers, I/O packs or modules, terminal boards, power
distribution, cabinets, networks, operator interfaces, and the protection module.
Control Cabinet
The control cabinet contains either a single (simplex) Mark VI control module or
three TMR control modules. These are linked to their remote I/O by a single or triple
high speed I/O network called IONet, and are linked to the Unit Data Highway
(UDH) by their controller Ethernet port. Local or remote I/O is possible. The control
cabinet requires 120/240 V ac and/or 125 V dc power. This is converted to 125 V dc
to supply the modules.
I/O Cabinet
The I/O cabinet contains either single or triple interface modules. These are linked to
the controllers by IONet, and to the terminal boards by dedicated cables. The
terminal boards are in the I/O cabinet close to the interface modules. Power
requirements are 120/240 V ac and/or 125 V dc power.
Summarized
I of 1016 Chapter 2 System Architecture • 2-1
Unit Data Highway (UDH)
The UDH connects the Mark VI control panels with the human machine interface
(HMI) or HMI/Data Server. The network media is unshielded twisted pair or fiber-
optic Ethernet. Redundant cable operation is optional and, if supplied, unit operation
continues even if one cable is faulted. 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.
Single mode cable (SMF) is now approved for the Mark VI UDH system. The
advantage of SMF over multi-mode cable (MMF) is the cables can be longer because
the signal attenuation per foot is less.
UDH command data is replicated to all three controllers. This data is read by the
master communication controller board (VCMI) and transmitted to the other
controllers. Only the UDH communicator transmits UDH data (refer to the section,
UDH Communicator).
Note The UDH network supports the Ethernet Global Data (EGD) protocol for
communication with other Mark VIs, HRSG, Exciter, Static Starter, and Balance of
Plant (BOP) control.
To Optional Customer Network Enterprise Layer
Router
HMI HMI HMI Field
Viewer Viewer Viewer Support
Supervisory Layer
PLANT DATA H IGHWAY
PLANT DATA H IGHWAY
HMI Servers
Control Layer
U NIT
D ATA H IGHWAY
U NIT DATA H IGHWAY
Gas Turbine Steam Turbine Generator

Control TMR Control Protection BOP Exciter
Mark VI Mark VI Gen. 90-70 PLC EXCITER
Protect
Mark VI
Mark VI
Genius
IONet IONet
Bus
I/O Boards I/O Boards I/O Boards
Typical Mark VI Integrated Control System
Summarized
2-2 • Chapter 2 System Architecture 24 of 1016
Human-Machine Interface (HMI)
®
Typical HMIs are computers running the Windows operating system with
®
communication drivers for the data highways, and CIMPLICITY operator display
software. The operator initiates commands from the real-time graphic displays, and
views real-time turbine data and alarms on the CIMPLICITY graphic displays.
Detailed I/O diagnostics and system configuration are available using the toolbox
software. An HMI can be configured as a server or viewer, containing tools and
utility programs.
An HMI 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.
Servers
CIMPLICITY servers collect data on the UDH and use the PDH to communicate
with viewers. Multiple servers can be used to provide redundancy.
Note Redundant data servers are optional, and if supplied, communication with the
viewers continues even if one server fails.
Control Operator Interface (COI)

The COI consists of a set of product and application specific operator displays
running on a small panel computer (10.4 or 12.1 inch touch screen) hosting
embedded Windows operating system. The COI is used where the full capability of a
CIMPLICITY HMI is not required. The embedded Windows operating system uses
only the components of the operating system required for a specific application. This
results in all the power and development advantages of a Windows operating system
in a much smaller footprint. Development, installation or modification of requisition
content requires the toolbox. For details, refer to the appropriate toolbox
documentation.
The COI can be installed in many different configurations, depending on the product
line and specific requisition requirements. The only cabling requirements are for
power and for the Ethernet connection to the UDH. Network communication is
through the integrated auto-sensing 10/100BaseT Ethernet connection. Expansion
possibilities for the computer are limited, although it does support connection of
external devices through floppy disk drives (FDD), intelligent drive electronics
(IDE), and universal serial bus (USB) connections.
The COI can be directly connected to the Mark VI or Excitation Control System, or
it can be connected through an EGD Ethernet switch. A redundant topology is
available when the controller is ordered with a second Ethernet port.
Summarized
Interface Features
EGD pages transmitted by the controller are used to drive numeric data displays. The
refresh rate depends on the rate at which the controller transmits the pages, and the
rate at which the COI refreshes the fields. Both are set at configuration time in the
toolbox.
The COI uses a touch screen, and no keyboard or mouse is provided. The color of
pushbuttons is driven by state feedback conditions. To change the state or condition,
press the button. The color of the button changes if the command is accepted and the
change implemented by the controller.
Touching an input numeric field on the COI touch screen displays a numeric keypad
for entering the desired number.
An Alarm Window is provided and an alarm is selected by touching it. Then

Acknowledge, Silence, Lock, or Unlock the alarm by pressing the corresponding
button. Multiple alarms can be selected by dragging through the alarm list. Pressing
the button then applies to all selected alarms.
Link to Distributed Control System (DCS)

External communication links are available to communicate with the plant DCS. A
serial communication link, using Modbus protocol (RTU binary), can be supplied
from an HMI or from a gateway controller. This allows the DCS operator access to
real time Mark VI data, and provides for discrete and analog commands to be passed
to the Mark VI control. In addition, an Ethernet link from the HMI supports periodic
data messages at rates consistent with operator response, plus sequence of events
(SOE) messages with data time tagged at a 1 ms resolution.
Plant Data Highway (PDH)

The optional PDH connects the CIMPLICITY HMI/data server with remote operator
stations, printers, historians, and other customer computers. It does not connect
directly to the Mark VI control. The media is UTP or fiber-optic Ethernet running at
10/100 Mbps, using 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. On smaller systems, the PDH and the
UDH may physically be the same network, as long as there is no peer-to-peer control
on the UDH.
Operator Console
The turbine control console is a modular design, which can be expanded from two
monitors, with space for one operator, to four monitors, with space for three
operators. Printers can be table-mounted, or on pedestals under the counter. The full
size console is 5507.04 mm (18 ft 0 13/16 in) long, and 2233.6 mm (7 ft 3 15/16 in)
wide. The center section, with space for two monitors and a phone/printer bay, is a
small console 1828.8 mm (6 ft) wide.
Summarized
EX2100 Exciter
The excitation control system supplies dc power to the field of the synchronous
generator. The exciter controls the generator ac terminal voltage and/or the reactive
volt-amperes by means of the field current.
The exciter is supplied in NEMA 1 freestanding floor-mounted indoor type metal

cabinets. The cabinet lineup consists of several cabinets bolted together.
Generator Protection
The generator protection system is mounted in a single, indoor, freestanding cabinet.
The enclosure is NEMA 1, and weighs 2500 lbs. The generator panel interfaces to
the Mark VI control with hard-wired I/O, and has an optional Modbus interface to
the HMI.
Static Starter Control System

The static starter control system is used to start a gas turbine by running the
generator as a starting motor. The static starter system is integrated into the control
system along with the excitation control system. The control supplies the run, torque,
and speed setpoint signals to the static starter, which operates in a closed loop control
mode to supply variable frequency power to the generator stator. The excitation
control system is controlled by the static starter to regulate the field current during
startup.
The control cabinet contains an Innovation Series controller in a Versa Module

Eurocard (VME) control rack. The controller provides the Ethernet link to the UDH
and the HMI, and communication ports for field control I/O and Modbus. The field
control I/O are used for temperature inputs and diagnostic variables.
The static starter cabinet is a ventilated NEMA 1 free-standing enclosure made of

12-gauge sheet steel on a rigid steel frame designed for indoor mounting.
Summarized
Control Module
The control module is available as an integrated control and I/O module, or as a
stand-alone control module only. The integrated control and I/O rack can be either a
21-slot or 13-slot VME size. The 13-slot rack can accommodate all the boards for
control of a small turbine. The backplane has P1 and P2 connectors for the VME
boards. The P1 connectors communicate data across the backplane, and the P2
connectors communicate data between the board and DC-37 pin J3 and J4
connectors located directly beneath each board. Cables run from the J3 and J4
connectors to the terminal boards.
There can be one control module (simplex) or three TMR control modules. Each of
these configurations supports remote I/O over IONet. The simplex control modules
can be configured to support up to three independent parallel IONet systems for
higher I/O throughput. Multiple communication boards may be used in a control
module to increase the IONet throughput.
The following figure shows a 21-slot rack with a three-IONet VCMI communication
board, and a UCVx controller. The UCVx must go in slot 2. The remaining slots are
filled with I/O boards.
Controller UCVx Fan I/O Processor

(slot 2) Boards
x x x x x x x x x x x x x x x x x x x x x
VME Chassis,
21 slots
Power
Supply
UDH
Port
VCMI
Communication
Board, with
One or Three
IONet Ports
x x x x x x x x x x x x x x x x x x x x x
Note: This rack is for the UCVx controller, connectors Connectors for Cables to
J302 and J402 are not present. UCVB and UCVD Terminal Boards (J3 & J4)
controllers can be used in this rack.
Control Module with Control, Communication, and I/O Boards
Summarized
The I/O racks and the I/O processor boards are shielded to control EMI/RFI
emissions. This shielding also protects the processor boards against interference from
external sources.
Do not plug the UCVx controller into any rack that has
J302 and J402 connectors.
The stand-alone controller module is a VME rack with the UCVx controller board,
VCMI communication board, and VDSK interface board as shown in the following
figure. This version is for remote I/O systems. The rack is powered by an integrated
power supply.
VDSK supplies 24 V dc to the cooling fan mounted under the rack, and monitors the
Power Distribution Module (PDM) through the 37-pin connector on the front. The
VDSK board is ribbon-cabled in the back to the VCMI to transmit the PDM
diagnostics.
VCMI Communication Board with Controller Interface Board

Three IONet Ports (VCMI with One UCVx VDSK
IONet is for Simplex systems)
x x x x
VME Rack
POWER
SUPPLY
Power Supply
x x x x
Cooling Fan Fan 24 Vdc

behind Panel Power
Rack with Controller, VCMI, and VDSK (No I/O Boards)
Summarized
Controller
The controller is a single-slot VME board, housing a high-speed processor, DRAM,
flash memory, cache, an Ethernet port, and two serial RS-232C ports. It must always
be inserted in slot 2 of an I/O rack designed to accommodate it. These racks can be
identified by the fact that there are no J3 and J4 connectors under slot 2. The
controller provides communication with the UDH through the Ethernet port, and
supports a low-level diagnostic monitor on the COM1 serial port. The base software
includes appropriate portions of the existing Turbine Block Library of control
functions for the steam, gas, and Land-Marine aero-derivative (LM) products. The
controller can run its program at up to 100 Hz, (10 ms frame rate), depending on the
size of the system configuration.
External data is transferred to/from the controller over the VME bus by the VCMI
communication board. In a simplex system, the data consists of the process I/O from
the I/O boards, and in a TMR system, it consists of voted I/O. Refer to GEH-6421,
Volume II.
Typical Mark VI Controller (UCVx)
Status LEDs
STATUS
VMEbus SYSFAIL
Monitor Port for GE use
Flash Activity
S
V
Power Status
G
Keyboard/mouse port A
for GE use
M
/
COM1 RS-232C Port for K
Initial Controller Setup; C
COM2 RS-232C Port for O
M
Serial communication 1:2 Ethernet Status LEDs
L Active
A
N
Ethernet Port for Unit Data Link
RST
Highway Communication
P
C Notice: To connect
M batteries, user to set jumper
I E8 to pins 7-8 ("IN") and
P
jumper E10 to ("IN")
M
E
Z
Z
A
N
I
N
E
UCVE
H2A
x
UCVx Controller Front Cabinet
Summarized
VCMI Communication Board
The VCMI board in the control and interface module communicates internally to the
I/O boards in its rack, and to the other VCMI boards through the IONet. There are
two versions, one with one Ethernet IONet port for simplex systems, and the other
with three Ethernet ports for TMR systems. Simplex systems have one control
module connected to one or more interface modules using a single cable. The VCMI
with three separate IONet ports is used in TMR systems for communication with the
three I/O channels Rx, Sx, and Tx, and with the two other control modules. This is
shown in the following figure.
Software Implemented Fault Tolerance (SIFT) voting is implemented in the VCMI

board. Input data from each of the IONet connections is voted in each of the R, S,
and T VCMI boards. The results are passed to the control signal database in the
controllers (labeled UCVx in the diagram) through the backplane VME bus.
Control Module R0
VCMI Board
with V U
Three IONet C C I/O
Ports M V Boards
I X
IONet - T to other Control, Interface, & Protection Modules
IONet - S to other Control, Interface, & Protection Modules
IONet - R
Interface Module R1
VCMI Board with V
One IONet Port C I/O
M Boards
I
IONet to other
Interface Modules &
Protection Module
VCMI Boards providing I/O Communication and I/O Voting
In TMR mode, the VCMI voter in the control module is always the master of the
IONet and also provides the IONet clock. Time-synchronous messages from the time
source on the UDH are sent to the controllers and then to the VCMIs. All input data
from a single rack is sent in one or more IONet packets (approximately 1500 bytes
per packet maximum). The VCMI in the control module broadcasts all data for all
remote racks in one packet, and each VCMI in the remote rack extracts the
appropriate data from the packet.
Summarized
IONet
The IONet connection on the VCMI is a BNC for 10Base2 Ethernet. The interface
circuit is high impedance that allows T tap connections with a 50 Ω terminal at the
first and last node. The cabling distances are restricted to 185 meters (607 ft) per
segment with up to eight nodes, using RG-58C/U or equivalent cable.
The Link Layer protocol is IEEE 802.3 standard Ethernet. The application layer
protocol uses Asynchronous Device Language (ADL) messaging with special
adaptations for the input/output handling and the state exchanges.
The VCMI board acts as IONet master and polls the remote interface module for
data. The VCMI master broadcasts a command to all slave stations on a single IONet
causing them to respond with their message in a consecutive manner. To avoid
collisions on the media, each station is told how long to delay before attempting to
transmit. Using this master/slave mechanism, and running at 10 Mb/s, the IONet is
capable of transmitting a 1000 byte packet every millisecond (8 MHz bit rate).
Note IONet supports control operation at up to 100 times per second.
In a multiple module or multiple cabinet system, powering down one module of a

channel does not disrupt IONet communication between other modules within that
channel. If one IONet stops communicating then the I/O boards, in that channel, time
out and the outputs go to a safe state. This state does not affect TMR system
operation. If two IONets stop, the I/O boards in both channels go to a safe state that
results in a turbine trip, if the turbine was generating.
I/O Boards
Most I/O boards are single width VME boards, of similar design and front cabinet,
using the same digital signal processor (TMS320C32).
The central processing unit (CPU) is a high-speed processor designed for digital
filtering and for working with data in IEEE 32-bit floating-point format. The task
scheduler operates at a 1 ms and 5 ms rate to support high-speed analog and discrete
inputs. The I/O boards synchronize their input scan to complete a cycle before being
read by the VCMI board. Contact inputs in the VCCC and VCRC are time stamped
to 1 ms to provide an SOE monitor.
Each I/O board contains the required sensor characteristic library, for example
thermocouple and resistance temperature devices (RTDs) linearizations. Bad sensor
data and alarm signal levels, both high and low, are detected and alarmed. The I/O
configuration in the toolbox can be downloaded over the network to change the
program online. This means that I/O boards can accept tune-up commands and data
while running.
Certain I/O boards, such as the servo and turbine board, contain special control
functions in firmware. This allows loops, such as the valve position control, to run
locally instead of in the controller. Using the I/O boards in this way provides fast
response for a number of time critical functions. Servo loops, can be performed in
the servo board at 200 times per second.
Each I/O board sends an identification message (ID packet) to the VCMI 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. Also each I/O board identifies the connected terminal
boards through the ID wire in the DC-37 pin cable. This allows each connector on
Summarized
each terminal board to have a separate identity.

No. per I/O
I/O Processor Terminal Processor Type of Terminal
Board Board I/O Signal Types Board Board Comments
VAIC TBAI (2) Analog inputs, 0−1mA, 4−20 20 TMR, simplex

mA, voltage 4
Analog outputs, 4−20 mA,
0−200 mA
VAOC TBAO Analog outputs, 4−20 mA 16 TMR, simplex
VCCC and TBCI (2) Contact inputs 48 TMR, simplex (VCCC is two slots)
VCRC TRLY (2) Relay Outputs (note 1)* 24 TMR, simplex
VCCC TICI (2) Point Isolated Contact 48 TMR, simplex VCCC-only in place of TBCI.
inputs (optional)
VGEN TGEN Analog inputs, 4−20 mA 4 TMR, simplex
Potential transformers 2
Current transformers 3
TRLY Relay outputs (optional) 12 for FAS (PLU)
VPRO (3) TPRO Pulse rate 3 TMR Emergency Protect
Potential transformers 2
Thermocouples 3
Analog inputs, 4−20 mA 3
TREG (2) Solenoid drivers 6 TMR Gas turbine
Trip contact inputs 7
Emergency stop 2 Hardwire, Trip, Clamp
TREL Solenoid drivers 3 TMR Large steam
TRES Solenoid drivers 3 TMR, simplex Small/medium steam
VPYR TPYR Pyrometers (4 analog inputs 2 TMR, simplex
each)
KeyPhasor shaft position 2
sensors
VRTD TRTD, Resistance Temperature 16 TMR, simplex 3 wire
Devices (RTD)
VSVO TSVO (2) Servo outputs to valve 4 TMR, simplex Trip, Clamp, Input
hydraulic servo
LVDT inputs from valve 12
LVDT excitation 8
Pulse rate inputs for flow 2
monitoring
Pulse rate excitation 2
VTCC TBTC Thermocouples 24 TMR, simplex
VTUR TTUR Pulse rate magnetic pickups 4 TMR, simplex
Potential transformers, gen. 2
and bus
Shaft current and voltage 2
monitor
Breaker interface 1
TRPG Flame detectors 8 TMR, simplex Gas turbine
(Geiger Mueller)
Solenoid drivers (note 2)* 3
Summarized
TRPL Solenoid drivers
2-12 • Chapter 2 System Architecture

3
33 of 1016
TMR Large steam

No. per I/O
I/O Processor Terminal Processor Type of Terminal
Board Board I/O Signal Types Board Board Comments
Emergency stop 2
TRPS Solenoid drivers 3 TMR, simplex Small/med. steam
Emergency stop 2
VVIB TVIB (2) Shaft vibration probes 16 TMR, simplex Buffered using BNC
(Bently Nevada)
Shaft proximity probes 8
(Displacement)
Shaft proximity reference 2
(KeyPhasor)
*Note 1: Refer to the table in the section Relay Terminal Boards.
*Note 2: VTURH2 occupies two slots and supports two TRPG boards, with flame
detector support on only the first TRPG.
Terminal Boards
The terminal board provides the customer wiring connection point, and fans out the
signals to three separate DC-37 pin connectors for cables to the R, S, and T I/O
boards. Each type of I/O board has its own special terminal board, some with a
different combination of connectors. For example, one version of the thermocouple
board does not fan out and has only two connectors for cabling to one I/O board. The
other version does fan out and has six connectors for R, S, and T. Since the fan out
circuit is a potential single point failure, the terminal board contains a minimum of
active circuitry limited primarily to filters and protective devices. Power for the
outputs usually comes from the I/O board, but for some relay and solenoid outputs,
separate power plugs are mounted on the terminal board.
TBAI Terminal Board

DC-37 pin
x x connectors with
x x JT1 latching fasteners
x x
x x
x x
x x
x x
Customer Wiring x x
x x
x x
x x JS1 Cable to VME Rack T
x x
x x
x
Shield Bar
x
x x
x x
x
x
x Cable to VME Rack S
x JR1
x x
x
Customer Wiring x
x x
x x
x x
x x
x x
BarrierType Terminal x x
Blocks can be x Cable to VME Rack R
x
unplugged from board
for maintenance
Typical Terminal Board with Cabling to I/O Boards in VME Rack
Summarized
DIN-rail Mounted Terminal Boards
Smaller DIN-rail mounted terminal boards are available for simplex applications.
These low cost, small size simplex control systems are designed for small gas and
steam turbines. IONet is not used since the D-type terminal boards cable directly into
the control chassis to interface with the I/O boards. The types of DIN-rail boards are
shown in the following table.
DIN–Rail Mounted Terminal Boards
DIN Euro Size Number Associated I/O
Terminal Board of Points I/O Description Processor Board
DTTC 12 Thermocouple temperature inputs with one cold junction VTCC
reference
DRTD 8 RTD temperature inputs VRTD
DTAI 10 Analog current or voltage inputs with on-board 24 V dc power VAIC
supply
2 Analog current outputs, with choice of 20 mA or 200 mA
DTAO 8 Analog current outputs, 0-20 mA VAOC
DTCI 24 Contact Inputs with external 24 V dc excitation VCRC (or VCCC)
DRLY 12 Form-C relay outputs, dry contacts, customer-powered VCRC (or VCCC)
DTRT ------- Transition board between VTUR and DRLY for solenoid trip VTUR
functions
DTUR 4 Magnetic (passive) pulse rate pickups for speed and fuel flow VTUR
measurement
DSVO 2 Servo-valve outputs with choice of coil currents from 10 mA to VSVO
120 mA
6 LVDT valve position sensors with on-board excitation

2 Active pulse rate probes for flow measurement, with 24 V dc
excitation provided
DVIB 8 Vibration, Position, or Seismic, or Accelerometer, or Velomiter VVIB
4 Position prox probes
1 KeyPhasor (reference)
DSCB 6 Serial communication ports supporting RS-232C, RS-422 and VSCA
RS-485
Relay Terminal Boards
The following table compares the features offered by the different relay terminal
boards.
Relay Terminal Boards
Power
Board Relays Distribution Feedback Relay type Redundancy Suppression Terminals
12 form C relays
soldered
24 dc @ 10 A
sealed
DRLYH1A 125 dc @ 0.5 A none none none, simplex only No 72 Euro-box
mechanical
120 ac @ 10 A
relays
240 ac @ 3 A
12 form C relays
soldered
24 dc @ 2 A
sealed
DRLYH1B 125 dc @ 0.5 A none none none, simplex only No 72 Euro-box
mechanical
120 ac @ 1 A
relays
240 ac @ 0.5 A
Summarized
Power
Board Relays Distribution Feedback Relay type Redundancy Suppression Terminals
12 form C relays 6 fused socketed

Coil drive = voted
24 dc @ 3 A branches, voted coil sealed
TRLYH1B TMR input or MOV 48 Barrier
125 dc @ 0.6 A 1 special drive mechanical
simplex input
120/240 ac @ 3 A unfused relays
6 fused isolated socketed
12 form C relays Coil drive = voted
branches, contact sealed
TRLYH1C 125 dc @ 0.6 A TMR input or MOV & R-C 48 Barrier
1 special voltage mechanical
120/240 ac @ 3 A simplex input
unfused feedback relays
6 fused isolated socketed
Coil drive = voted
12 form C relays branches, contact sealed
TRLYH2C TMR input or MOV & R-C 48 Barrier
24 dc @ 3 A 1 special voltage mechanical
simplex input
unfused feedback relays
ohm meter
socketed
6 form A relays (dc Coil drive = voted
6 fused sealed
TRLYH1D 24 dc @ 3 A 125 solenoid TMR input or MOV 24 Barrier
branches mechanical
dc @ 0.6 A integrity simplex input
relays
monitor)
isolated
soldered Coil drive = voted
12 form A relays contact
TRLYH1E none solid-state TMR input or No 24 Barrier
120/240 ac @ 6 A voltage
relays simplex input
feedback
isolated
24 dc @ 7 A voltage
feedback
isolated
125 dc @ 3 A voltage
feedback
soldered
none without non-voted sealed Relay contact 48 Barrier
TRLYH1F 12 form A relays No
WPDF coil drive mechanical voting, TMR only (24 used)
relays
soldered
With WPDF,
non-voted sealed Relay contact
TRLYH1F 12 form A relays 12 fused No 48 Barrier
coil drive mechanical voting, TMR only
outputs
relays
soldered
none without non-voted sealed Relay contact 48 Barrier
TRLYH2F 12 form B relays No
WPDF coil drive mechanical voting, TMR only (24 used)
relays
soldered
With WPDF,
non-voted sealed Relay contact
TRLYH2F 12 form B relays 12 fused No 48 Barrier
coil drive mechanical voting, TMR only
outputs
relays
Summarized
Trip Terminal Boards
The following table compares the features offered by the different trip terminal
boards.
Output Output
Contacts, 125 Contacts, 24 V Input Contacts Input Contacts Economy
Board TMR Simplex V dc, 1 A dc, 3 A ESTOP Dry 125 V dc Dry 125 V dc Resistor
TRPGH1A* Yes No Yes No No No No No
TRPGH1B Yes No Yes Yes No No No No
TRPGH2A* No Yes Yes No No No No No
TRPGH2B No Yes Yes Yes No No No No
TREGH1A* Yes No Yes No Yes Yes No Yes
TREGH1B Yes No Yes Yes Yes Yes No Yes
TREGH2B Yes No Yes Yes Yes No Yes Yes
TRPLH1A Yes No Yes Yes Yes No No No
TRELH1A Yes No Yes Yes No Yes No No
TRELH2A Yes No Yes Yes No No Yes No
TRPSH1A Yes Yes Yes Yes Yes No No No
TRESH1A Yes Yes Yes Yes No Yes No No
TRESH2A Yes Yes Yes Yes No No Yes No
* These boards will become obsolete
Power Sources
A reliable source of power is provided to the rack power supplies from either a
battery, or from multiple power converters, or from a combination of both. The
multiple power sources are connected as high select in the PDM to provide the
required redundancy.
A balancing resistor network creates a floating dc bus using a single ground

connection. From the 125 V dc, the resistor bridge produces +62.5 V dc (referred to
as P125) and -62.5 V dc (referred to as N125) to supply the system racks and
terminal boards. The PDM has ground fault detection and can tolerate a single
ground fault without losing any performance and without blowing fuses. Since this
fault is alarmed, it can be repaired.
Summarized
Turbine Protection Module
The Turbine Protection Module (VPRO) and associated terminal boards (TPRO and
TREG) provide an independent emergency overspeed protection for turbines that do
not have a mechanical overspeed bolt. The protection module is separate from the
turbine control, and consists of triple redundant VPRO boards, each with their own
on-board power supply, as shown in the following figure. VPRO controls the trip
solenoids through relay voting circuits on the TREG, TREL, and TRES boards.
VPRO R8 VPRO S8 VPRO T8

x x x x x x x x x x x
x x
I RUN I RUN I RUN

IONet R O FAIL O FAIL O FAIL
IONet S N STAT N STAT N STAT
E 8 X E 8 X E 8 X
IONet T T 4 Y T 4 Y T 4 Y
T 2 Z T 2 Z T 2 Z
R 1 R 1 R 1
C C C
S S S
E E E
Ground R J R J R J
6 J 6 6
J P5 P5 J P5
COM 5 COM COM
5 5
P28A P28A P28A
P28B P28B P28B
E E E
T T T
To TPRO H H H
R R R
J J J J J J
To TPRO x P
4
P P x
3 4 A P
3 A P
3 4 A P
R O R O R O
A W A W A W
F N L E F N L E F N L E
To TREG VPRO R VPRO R VPRO R
x x x x x x x x x x x
To TREG
Power In
125 Vdc
Turbine Protection Module with Cabling Connections
The TPRO terminal board provides independent speed pickups to each VPRO, which
processes them at high speed. This high speed reduces the maximum time delay to
calculate a trip and signal the ETR relay driver to 20 ms. In addition to calculating
speed, VPRO calculates acceleration, which is another input to the overspeed logic.
TPRO fans out generator and line voltage inputs to each VPRO where an
independent generator synchronization check is made. Until VPRO closes the K25A
permissive relay on TTUR, generator synchronization cannot occur. For gas turbine
applications, inputs from temperature sensors are brought into the module for
exhaust over temperature protection.
The VPRO boards do not communicate over the VME backplane. Failures on TREG
are detected by VPRO and fed back to the control system over the IONet. Each
VPRO has an IONet communication port equivalent to that of the VCMI.
Summarized
Operating Systems
All operator stations, communication servers, and engineering workstations use the
Windows operating system. The HMIs and servers run CIMPLICITY software, and
the engineer's workstation runs toolbox software for system configuration.
The I/O system, because of its TMR requirements, uses a proprietary executive
system designed for this special application. This executive is the basis for the
operating system in the VCMI and all of the I/O boards.
®
The controller uses the QNX operating system from QNX Software Systems Ltd.
®
This is a real time POSIX -compliant operating system ideally suited to high-speed
automation applications such as turbine control and protection
Levels of Redundancy
The need for higher system reliability has led vendors to develop different systems of
increasing redundancy.
Simplex systems have only one chain, and are the least expensive. Reliability is
average.
TMR systems have a very high reliability, and since the voting software is simple,
the amount of software required is reasonable. Input sensors can be triplicated, if
required.
Simplex System Redundancy Reliability

Type (MTBF)
Input Controller Output
Simplex Average
Triple Redundant System

Triple Very
Input Controller (TMR) High
Vote
Input Controller Vote Output
Vote
Input Controller
Single and Triple Redundant Systems
Summarized
Simplex systems in a typical power plant are used for applications requiring
normal reliability, such as control of auxiliaries and balance of plant (BOP). A single
PLC with local and remote I/O might be used in this application. In a typical Mark
VI, many of the I/O are non-critical and are installed and configured as simplex.
These simplex I/O boards can be mixed with TMR boards in the same interface
module.
Triple Modular Redundant (TMR) control systems, such as Mark VI, are used
for the demanding turbine control and protection application. Here the highest
reliability ensures the minimum plant downtime due to control problems, since the
turbine can continue running even with a failed controller or I/O channel. In a TMR
system, failures are detected and annunciated, and can be repaired online. This
means the turbine protection system can be relied on to be fully operational, if a
turbine problem occurs.
Control and Protection Features

This section describes the fault tolerant features of the TMR part of the control
system. The control system can operate in two different configurations:
• Simplex configuration is for non-redundant applications where system operation

after a single failure is not a requirement.
• TMR configuration is for applications where the probability of a single failure
causing a process shutdown has to be taken to an extremely low value.
Triple Modular Redundancy

A TMR system is a special case of N-modular redundancy where N=3. It is based on
redundant modules with input and output voting.
Input signal voting is performed by software using an approach known as Software

Implemented Fault Tolerance (SIFT). Output voting is performed by hardware
circuits that are an integral part of the output terminal boards.
The voting of inputs and outputs provides a high degree of fault masking. When
three signals are voted, the failure of any one signal is masked by the other two good
signals. This is because the voting process selects the median of the three analog
inputs. In the case of discrete inputs, the voting selects the two that agree. In fact, the
fault masking in a TMR system hides the fault so well that special fault detection
functions are included as part of the voting software. Before voting, all input values
are compared to detect any large differences. This value comparison generates a
system diagnostic alarm.
In addition to fault masking, there are many other features designed to prevent fault
propagation or to provide fault isolation. A distributed architecture with dc isolation
provides a high degree of hardware isolation. Restrictions on memory access using
dual-port memories prevent accidental data destruction by adjacent processors.
Isolated power sources prevent a domino effect if a faulty module overloads its
power supply.
Summarized
TMR Architecture
The TMR control architecture has three duplicate hardware controller modules
labeled R, S, and T. A high-speed network connects each control module with its
associated set of I/O modules, resulting in three independent I/O networks. Each
network is also extended to connect to separate ports on each of the other controllers.
Each of the three controllers has a VCMI communication board with three
independent I/O communication ports to allow each controller to receive data from
all of the I/O modules on all three I/O networks. The three protection modules are
also on the I/O networks.
Control Module R0 Control Module S0 Control Module T0

VCMI Board TMR System with
with Three V U V U V U Local & Remote I/O,
IONet Ports C C I/O C C I/O C C I/O Terminal Boards not
M V Boards M V Boards M V Boards shown
I X I X I X
IONet - R
IONet - S
IONet - T
Interface Module R1 Interface Module S1 Interface Module T1

VCMI Board
with One V V V
IONet Port C I/O C I/O C I/O IONet Supports
M Boards M Boards M Boards Multiple Remote
I I I I/O Racks
VPRO VPRO VPRO Protection

R8 S8 T8 Module
TMR Architecture with Local & Remote I/O, and Protection Module
Summarized
Each of the three controllers is loaded with the same software image, so that there are
three copies of the control program running in parallel. External computers, such as
the HMI operator stations, acquire data from only the designated controller. The
designated controller is determined by a simple algorithm.
A separate protection module provides for very reliable trip operation. The VPRO is
an independent TMR subsystem complete with its own controllers and integral
power supplies. Separate independent sensor inputs and voted trip relay outputs are
used.
Redundant
Unit Data
Highway Control Cabinet Termination Cabinet
Power
1 Serial <R x > Interface Module Supply
Terminal
V
I I I DC
Boards
Power DC C
V C I I I /
Supply / M U
C
V
D IONET M / / / 21 SLOT / / /
DC
<R> I O O O VME RACK O O O DC
I V S H
H X K Ethernet 1
2
10Base2
<R> Control Module Thin
Coax
Power
1 Serial <S x > Interface Module Supply
V DC
Power DC V U V C I I I I I I
/
Supply / C D IONET M / / / 21 SLOT / / /
DC M C I O O O VME RACK O O O
DC
I V S <S>
H X K H
2 Ethernet 1
10Base2
<S> Control Module
Thin
Coax
Power
1 Serial <T x > Interface Module Supply
V DC
Power DC V U V C I I I I I I
/
Supply / C
M C D IONET M / / / 21 SLOT / / /
DC
DC I O O O VME RACK O O O
I V S <T> H
H X K Ethernet 1
2 10Base2
<T> Control Module Thin
Coax
Input
+125Vdc
Power <R> Internal
Power Protection V V V
Converter <S> Buss Modules P P P
Input to R R R
Input T
Power <T> Power IONET Power O O O
Supplies Interface <R8> <S8><T8> R
Converter Converter
to I
Input other I/O <R> P
Input
Power Cabinet Power <S>
Lineups +125Vdc
Converter Converter <T> Internal Power
(Optional)
Busses to
Input <R8> Power Supplies &
Power <S8> Terminal Boards
Converter <T8>
To
Input Contact Input Excitatn. Terminal
Power Solenoid Power
Cond. Boards
Customer
Customer Supplied Sensor Cables
Power Input(s)
Summarized
Typical Cabinet Layout of Mark VI TMR System

TMR Operation
Voting systems require that the input data be voted, and the voted result be available
for use on the next calculation pass. The sequential operations for each pass are
input, vote, calculate, and output. The time interval that is allotted to these operations
is referred to as the frame. The frame is set to a fixed value for a given application so
that the control program operates at a uniform rate.
For SIFT systems, a significant portion of the fault tolerance is implemented in

software. The advantage to this approach is software does not degrade over time. The
SIFT design requires little more than three identical controllers with some provision
of transferring data between them. All of the data exchange, voting, and output
selection may be performed by software. The exception to the all software approach
is the modification to the hardware output circuitry for hardware voting.
With each controller using the same software, the mode control software in each
controller is synchronizing with, and responding to, an identical copy of itself that is
operating in each of the other controllers. The three programs acting together are
referred to as the distributed executive and coordinate all operations of the controllers
including the sequential operations mentioned above.
There are several different synchronization requirements. Frame synchronization

enables all controllers and associated I/O modules to process the data at the same
time for a given frame. The frame synchronization error is determined at the start of
frame (SOF) and the controllers are required to adjust their internal timing so that all
three controllers reach SOF of the same frame at the same time.
The acceptable error in time of SOF is typically several microseconds in the 10 to 25

Hz control systems that are encountered. Large errors in SOF timing will affect
overall response time of the control since the voter will cause a delay until at least
two controllers have computed the new values. The constraining requirement for
synchronization comes from the need to measure contact SOE times with an
accuracy of 1 ms.
Designated Controller
Although three controllers R, S, and T contain identical hardware and software, some
of the functions performed are individually unique. A single designated controller is
automatically selected to perform the following functions:
• Supply initialization data to the other two controllers at boot-up

• Keep the master time clock
• Calculate the control state data for the cabinet if one of the other controllers
fails.
The VCMIs determine the designated controller through a process of nomination and
voting based upon local visibility of the IONet and whether a designated controller
currently exists. If all controllers are equal, a priority scheme is used favoring first
R, then S, and then T. If a controller, which was designated, is powered down and
then 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.
Summarized
UDH Communicator
Controller communications takes place across the UDH. A UDH communicator is a

controller selected to provide the cabinet data to that network. This data includes
both control signals (EGD) and alarms. Each controller has an independent, physical
connection to the UDH. In the event that the UDH fractures and a controller becomes
isolated from its companion controllers, it assumes the role of UDH communicator
for that network fragment. While for one cabinet there can be only one designated
controller, there may be multiple UDH communicators. The designated controller is
always a UDH communicator.
Fault Tolerant EGD
When a controller does not receive expected external EGD data from its UDH
connection, (for example, due to a severed network) it will request that the data be
forwarded across the IONet from another UDH communicator. One or more
communicators may supply the data and the requesting controller uses the last data
set received. Only the EGD data used in sequencing by the controllers is forwarded
in this manner.
Output Processing
The system outputs are the portions of the calculated data that have to be transferred
to the external hardware interfaces and then to the various actuators controlling the
process. Most of the outputs from the TMR system are voted in the output hardware,
but the system can also output individual signals in a simplex manner. Output voting
is performed as close to the final control element as possible.
Outputs from the TMR system are normally calculated independently by the three
voting controllers, and each controller sends the output to its associated I/O hardware
(for example, R controller sends to 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:
• Signals exist in only one I/O channel, and are driven as single-ended non-
redundant outputs
• Signals exist in all three controllers, and are sent as output separately to an
external voting mechanism
• Signals exist in all three controllers, but are merged into a signal by the output
hardware
For normal relay outputs, the three signals feed a voting relay driver, which operates
a single relay per signal. For more critical protective signals, the three signals drive
three independent relays with the relay contacts connected in the typical six-contact
voting configuration. The following figure shows two types of output boards.
Summarized
Terminal Board, Relay Outputs
I/O Board
Channel R Voted Relay
Driver
Coil
I/O Board
V
Channel S
Relay Output
I/O Board
Channel T
Terminal Board, High Reliability Relay Outputs
I/O Board KR KS
Channel R Relay KR
Coil
Driver
KS KS KT Relay Output
I/O Board Relay
Coil
Channel S Driver
KT KT KR
Relay
I/O Board Coil
Driver
Channel T
Relay Output Circuits for Protection
For servo outputs as shown in the following figure, the three independent current
signals drive a three-coil servo actuator, which adds them by magnetic flux
summation. Failure of a servo driver is sensed and a deactivating relay contact is
opened.
I/O Boards
Servo Driver Output
Channel R Terminal Coils
D/A Board On Servo
Valve
Servo Driver
Channel S
D/A
Servo Driver
Channel T
D/A
Hydraulic
Servo
Valve
TMR Circuit to Combine Three Analog Currents into a Single Output
Summarized
The following figure shows 4-20 mA signals combined through a 2/3 current sharing
circuit that allows the three signals to be voted to one. This unique circuit ensures
that the total output current is the voted value of the three currents. Failure of a 4-20
mA output is sensed, and a deactivating relay contact is opened.
I/O Boards
4-20 mA Driver Current
Channel R Feedback
D/A
Output
4-20 mA Driver
Load
Channel S
D/A
4-20 mA Driver
Channel T
D/A Output
Terminal
Board
TMR Circuits for Voted 4-20 mA Outputs
Input Processing
All inputs are available to all three controllers but there are several ways that the
input data is handled. For those input signals that exist in only one I/O module, the
value is used by all three controllers as common input without SIFT-voting as shown
in the following figure. Signals that appear in all three I/O channels may be
application-voted to create a single input value. The triple inputs either may come
from three independent sensors or may be created from a single sensor by hardware
fanning at the terminal board.
A single input can be brought to the three controllers without any voting as shown in
the following figure. This arrangement is used for non-critical, generic I/O, such as
monitoring 4-20 mA inputs, contacts, thermocouples, and RTDs.
I/O Rack Control Rack

Field Wiring Termin. Bd. I/O Board VCMI IONet VCMI Controller
R,S, R,S,T
Direct Signal or T Exchange No Control System
Sensor
Input Condition Vote Database
Alarm Limit
SC
A R
R,S, or T
Single Input to Three Controllers, Not Voted
Summarized
One sensor can be fanned to three I/O boards for medium-integrity applications as
shown in the following figure. This configuration is used for sensors with medium-
to-high reliability. Three such circuits are needed for three sensors. Typical inputs
are 4-20 mA inputs, contacts, thermocouples, and RTDs.

R,S,or T R,S,T
Sensors Fanned Signal Prevote Exchange Voter Control
Input Condition System Database
SC R Voted (A)
A
R,S, or T Voter
SC S Voted (A)
R,S, or T Voter
SC T Voted (A)
R,S, or T Voter
One Sensor with Fanned Input & 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, shown in the following
figure, is used for special applications only.

R,S,or T R,S,T
Sensors Common Signal No Median Control System
Input Condition Vote Select Database
Alarm Limit Block
A Median (A,B,C)
SC MSB
A B A
R,S, or T R B
C
C
SC A Median (A,B,C)
B B MSB A
R,S, or T C S B
C
A Median (A,B,C)
SC MSB
C B A
R,S, or T C T B
C
Three Independent Sensors with Common Input, Not Voted
Summarized
The following figure shows three sensors, each one fanned and then SIFT-voted.
This arrangement provides a high-reliability system for current and contact inputs,
and temperature sensors.
I/O Rack Controller Rack
Field WiringTermin. Bd.I/O Board VCMI IONet VCMI Controller
R,S,or T R,S,T
Sensors Fanned Signal Prevote Exchange Voter Control System
Input Condition Database
Alarm Limit
SC R Voted "A"
A Control
R, S, or T Voter Voted "B" Block
Voted "C"
B SC S Voted "A"
Control
Same R, S, or T Voter Voted "B"
Block
Voted "C"
SC T Voted "A"
C Control
Same R, S, or T Voter Voted "B"
Block
Voted "C"
Three Sensors, Each One Fanned and Voted, for Medium to High Reliability Applications
Speed inputs to high-reliability applications are brought in as dedicated inputs and

then SIFT-voted. The following figure shows the configuration. Inputs such as speed
control and overspeed are not fanned so there is a complete separation of inputs with
no hardware cross-coupling that could propagate a failure. RTDs, thermocouples,
contact inputs, and 4-20 mA signals can also be configured this way.
R,S,or T R,S,T
Sensors Dedicated Signal Prevote Exchange Voter Control System
Input Condition Database
Alarm Limit
SC R Voted (A,B,C)
A
R,S, or T Voter
B SC S Voted (A,B,C)
R,S, or T Voter
SC T Voted (A,B,C)
C
R,S, or T Voter
Three Sensors with Dedicated Inputs, Software Voted for High Reliability Applications
State Exchange
Voting all of the calculated values in the TMR system is unnecessary and not
practical. The actual requirement is to vote the state of the controller database
between calculation frames. Calculated values such as timers, counters, and
integrators are dependent on the value from the previous calculation frame. Logic
signals such as bi-stable relays, momentary logic with seal-in, cross-linked relay
circuits, and feedbacks have a memory retention characteristic. A small section of the
Summarized
database values is voted each frame.

Median Value Analog Voting
The analog signals are converted to floating point format by the I/O interface boards.
The voting operation occurs in each of the three controller modules (R, S, and T).
Each module receives a copy of the data from the other two channels. For each voted
data point, the module 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. The following figure provides examples.
The disagreement detector (see the section, Disagreement Detector) checks the
signal deviations and sets a diagnostic if they exceed a preconfigured limit, thereby
identifying failed input sensors or channels.
Median Value Voting Examples
Sensor Median Sensor Median Sensor Median

Sensor Inputs Input Selected Input Selected Input Selected
Value Value Value Value Value Value
Sensor
981 910 1020
1
Sensor 985 981 985 978 985 985

2
Sensor 978 978 978

3
Configured TMR No TMR TMR Diagnostic TMR Diagnostic

Deviation = 30 Diagnostic on Input 1 on Input 1
Median Value Voting Examples with Normal and Bad Inputs
Two Out of Three Logic Voter

Each of the controllers has three copies of the data as described above for the analog
voter. The logical values are stored in the controller database in a format that
requires a byte per logical value. Voting is a simple logic process, which inputs the
three values to find the two values that agree.
The logical data has an auxiliary function called forcing, which allows the operator
to force the logical state to be either true or false and have it remain in that state until
unforced. The logical data is packed in the input tables and the state exchange tables
to reduce the bandwidth requirements. The input cycle involves receive, vote,
unpack, and transfer to the controller database. The transfer to the database must
leave the forced values as they are.
Disagreement Detector
A disagreement detector is provided to continuously scan the pre-vote input data sets
and produce an alarm bit if a disagreement is detected between the three values in a
voted data set. The comparisons are made between the voted value and each of the
three pre-vote values. The delta for each value is compared with a user
programmable limit value. The limit can be set to avoid nuisance alarms but indicate
that one of the pre-vote values has moved out of normal range. Each controller is
required to compare only its pre-vote value with the voted value, for example, R
compares only the R pre-vote value with the voted value.
Summarized
Failure of one of the three voted input circuits has no effect on the controlled process
since the fault is masked by SIFT. Without a disagreement detector, a failure could
go unnoticed until occurrence of a second failure.
Forced Variables
The controller has a feature called Forced Variables. This allows the maintenance
technician using toolbox 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 reboot 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.
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.
Command Action
Commands sent to the TMR control require special processing to ensure that the
three voting controllers perform the requested action at the same time. Typically, the
commanding device is a computer connected to the UDH that sends messages over a
single network so there is no opportunity to vote the commands in each controller.
Commands may be sent from one of several redundant computers at the operator
position(s).
When any TMR controller receives a command message, it synchronizes the

corresponding response of all three controllers by retransmitting the command to its
companions across the IONet and queuing it for action at the start of the next frame.
By default, the HMIs send all commands to the UDH communicator.
Rate of Response
The control system can run selected control programs at the rate of 100 times per
second (10 ms frame rate) for simplex systems and 50 times per second (20 ms frame
rate) for TMR systems.
Summarized
Failure Handling
The general operating principle on failures is that corrective or default action takes
place in both directions away from the fault. When a fault occurs in the control
hierarchy extending from the terminal mounts through I/O boards, backplanes,
networks, and main CPUs, there is a reaction at the I/O processor. There is also a
reaction at the main controller, if still operating. When faults are detected, health bits
are reset in a hierarchical fashion. If a signal goes bad, the health bit is set false at the
control module level. If a board goes bad, all signals associated with that board,
whether input or output, have the health bits set false. A similar situation exists for
the I/O rack. In addition, there are pre-configured default failure values defined for
all input and output signals so that normal application code may cope with failures
without excessive healthy bit referencing. Healthy bits in TMR systems are voted if
the corresponding signal is TMR.
Loss of Control Module in Simplex System - If a control module fails in a

simplex system, the output boards go to the configured default output state after a
timeout. The loss of the controller board propagates down through the IONet so that
the output board knows what to do. This is accomplished by shutting down the
IONet.
Loss of Control Module in TMR System - If a control module fails in a TMR

system, the TMR outputs and simplex outputs on that channel timeout to the
configured default output state. TMR control continues using the other two control
modules.
Loss of I/O VCMI in TMR System - If the VCMI in an interface module in a

TMR system fails, the outputs timeout to the configured default output state. The
inputs are set to the configured default state so that resultant outputs, such as UDH,
can be set correctly. Inputs and output healthy bits are reset. A failure of the VCMI
in Rack 0 is viewed as equivalent to a failure of the control module itself.
Loss of I/O VCMI in Simplex System - If the VCMI in an interface module in a

simplex system fails, the outputs and inputs are handled the same as a TMR system.
Loss of I/O Board in Simplex System - If an I/O board in a simplex system

fails, hardware on the outputs from the I/O boards set the outputs to a low power
default value given typical applications. Input boards have the input values set to the
pre-configured default value in the master VCMI board.
Loss of Simplex I/O Board in TMR System - If the failed simplex I/O board is
in a TMR system, the inputs and outputs are handled as described herein if they were
in a simplex system.
Loss of TMR I/O Board in TMR System - If a TMR I/O board fails in a TMR
system, inputs and outputs are handled. TMR, SIFT, and hardware output voting
keep the process running.
Loss of IONet in Simplex System - If the IONet fails in a simplex system, the
output boards in the I/O racks timeout and set the pre-configured default output
values. The master VCMI board defaults the inputs so that UDH outputs can be
correctly set.
Loss of IONet in TMR System - If the IONet fails in a simplex system, outputs
follow the same sequence as for a Loss of Control Module in simplex. Inputs follow
the same sequence as for Loss of I/O VCMI in TMR.
Summarized
Turbine Protection
Turbine overspeed protection is available in three levels, control, primary, and
emergency. 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 VTUR I/O board bring in a shaft speed signal to each
controller where they are median selected. If the controller determines a trip
condition, the controller sends the trip signal to the TRPG terminal board through the
VTUR I/O board. The three VTUR 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 shows the primary and emergency levels of protection.
Software
Voting
High Speed Shaft R TTUR Controller R TRPG

& Terminal
Terminal VTUR
Board
Board
High Speed Shaft S
Controller S Primary
& Hardware Protection
VTUR Voting
High Speed Shaft T (Relays)
Controller T
&
VTUR
Magnetic
Speed
Pickups
Trip
(3 used)
Solenoids
(Up to three)
High Speed Shaft R8 TPRO

VPRO TREG
Terminal R8 Terminal
Board Board
High Speed Shaft S8
VPRO
Hardware Emergency
S8
Voting Protection
High Speed Shaft T8
(Relays)
VPRO
T8
Magnetic
Speed Trip Signal
Pickups to Servo
(3 used) Terminal
Board
TSVO
Primary and Emergency Overspeed Protection
Summarized
Emergency overspeed protection is provided by the independent triple redundant
VPRO protection system. This uses three shaft speed signals from magnetic pickups,
one for each protection module. These are brought into TPRO, a terminal board
dedicated to the protection system. Either the controllers or the protection system can
independently trip the turbine. Each VPRO 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 VPRO
modules completely independent. The only link between VPRO 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, TSVO. Plug J1 on TREG is wired to plug JD1 on
TSVO, and if this is energized, relay K1 disconnects the servo output current and
applies a bias to force the control valve closed.
Reliability and Availability

System reliability and availability can be calculated using the component failure
rates. These numbers determine whether to use simplex circuits or TMR circuits.
TMR systems have the advantage of online repair discussed in the section, Online
Repair for TMR Systems.
Online Repair for TMR Systems

The high availability of the TMR system is a result of being able to do repair online.
It is possible to shut down single modules for repair and leave the voting trio in full
voting mode operation, which effectively masks the absence of the signals from the
powered down module. However, there are some restrictions and special cases that
require extra attention.
Many signals are reduced to a single customer wire at the terminal boards so removal
of the terminal board requires that the wires be disconnected momentarily. Each type
of terminal board must be evaluated for the application and the signal type involved.
Voltages in excess of 50 V are present in some customer wiring. Terminal boards
that have only signals from one controller channel may be replaced at any time if the
faulty signals are being masked by the voter. For other terminal boards such as the
relay outputs, the individual relays may be replaced without disconnecting the
terminal board.
For those singular signals driven from only one I/O board, there is no redundancy or
masking. These are typically used for non-critical functions such as pump drives,
where loss of the control output simply causes the pump to run continuously.
Application designers must avoid using such singular signals in critical circuits. The
TMR system is designed such that any of the three controllers may send outputs to
the singular signals, keeping the function operational even if the normal sending
controller fails.
Note Before performing an online repair, power down only the module (rack) that
has the fault. Failure to observe this rule may cause an unexpected shutdown of the
process (each module has its own power disconnect or switch). The modules are
labeled such that the diagnostic messages identify the faulty module.
Summarized
Repair the faulty modules as soon as possible. Although the TMR system will
survive certain multiple faults without a forced outage, a hidden fault problem may
exist after the first unrepaired failure occurs. Multiple faults within the same module
cause no concern for online repair since all faults will be masked by the other voters.
If a second unrelated fault occurs in the same module set, either of the faulty
powered-down modules introduces a dual fault in the same three-signal set. This may
cause a process shutdown.
Reliability
Reliability is represented by the Mean Time Between Forced Outage (MTBFO) of
the control system. The MTBFO is a function of which boards are being used to
control and protect the turbine. The complete system MTBFO depends on the size of
the system, number of simplex boards, and the amount of sensor triplication.
In a simplex system, failure of the controller or I/O communication may cause a

forced outage. Failure of a critical I/O module also causes a forced outage. However,
there are non-critical I/O modules that can fail and be replaced without a shutdown.
The MTBFO is calculated using published failure rates for components.
Availability is the percentage of time the system is operating, taking into account the
time to repair a failure. Availability is calculated as follows:
MTBFO x 100%
-----------------------
MTBFO + MTTR
where:
MTTR is the Mean Time To Repair the system failure causing the forced outage.
With a TMR system, there can be failures without a forced outage because the
system can be repaired while it continues to run. The MTBFO calculation is complex
since it is calculating the probability of a second (critical) failure in another channel
during the time the first failure is being repaired. The time to repair is an important
input to the calculation.
The availability of a well-designed TMR system with timely online repair is

effectively 100%. Possible forced outages can still occur if a second failure of a
critical circuit occurs before the repair is completed. Other possible forced outages
can occur if the repairman erroneously powers down the wrong module.
Note To avoid possible forced outages from powering down the wrong module,
check the diagnostics to identify the modules that contain the failure.
System reliability has been determined by calculating the Failures In Time (FIT)
9
(failures per 10 hours) based on the Bellcore TR-332 Reliability Prediction
Procedure for Electronic Equipment. The Mean Time Between Failures (MTBF) can
be calculated from the FIT.
Summarized
Third-Party Connectivity
The Mark VI can be linked to the plant DCS in one of three ways:
• Modbus link from the HMI Server RS-232C port to the DCS
• A high-speed 10 Mbaud Ethernet link using the Modbus over TCP/IP protocol
• A high-speed 10 Mbaud Ethernet link using the TCP/IP protocol with an
application layer called GEDS Standard Messages (GSM)
The Mark VI can be operated from the plant control room.
GSM supports turbine control commands, Mark VI data and alarms, the alarm
silence function, logical events, and contact input sequence of events records with 1
ms resolution. The following figure shows the three options. Modbus is widely used
to link to the DCS, but Ethernet GSM has the advantage of speed, distance, and
functionality.
To DCS To DCS To DCS

Serial Modbus Ethernet Modbus Ethernet GSM
UCVx
Controller
x
PLANT DATA HIGHWAY
HMI Server Node

L
A
N
To Plant Data
Highway (PDH)
Ethernet Ethernet
UCVE
x
Ethernet
UNIT DATA HIGHWAY
Optional Communication Links to Third-Party Distributed Control System
Summarized
Notes
Mark VI Turbine Control System Guide
56 of 1016
CHAPTER 3
Chapter 3 Networks
Introduction
This chapter defines the various networks in the control system that communicate
with the operator interfaces, servers, controllers, and I/O. This chapter also provides
information on fiber-optic cables, including components and guidelines.
Network Overview
The Mark VI 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
and controllers, which provide real-time control of the turbine and its associated
equipment, through the operator interface systems, and up to facility-wide
monitoring or DCS. Each layer uses standard components and protocols to simplify
integration between different platforms and improve overall reliability and
maintenance. The layers are designated as the Enterprise, Supervisory, Control, and
I/O.
Note Ethernet is used for all Mark VI data highways and the I/O network.
Summarized
I of 1016 Chapter 3 Networks • 3-1
Network Layers
To Optional Customer Network Enterprise Layer
Router
HMI HMI HMI Field
Viewer Viewer Viewer Support
Supervisory Layer
PLANT DATA H IGHWAY
PLANT DATA H IGHWAY
HMI Servers
Control Layer
U NIT D ATA H IGHWAY
U NIT DATA H IGHWAY
Gas Turbine Steam Turbine Generator

Control TMR Control Protection BOP Exciter
Mark VI Mark VI Gen. 90-70 PLC EXCITER
Protect
Mark VI
Mark VI
Genius
IONet IONet
Bus
I/O Boards I/O Boards I/O Boards
Mark VI Control as Part of Integrated Control System
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 generally
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).
Summarized
3-2 • Chapter 3 Networks 58 of 1016
The Control layer provides continuous operation of the process equipment. The
controllers on this layer are highly coordinated to support continuous operation
without 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.
Printer
Printer
Type 1 Redundancy Non-critical nodes

such as printers can be connected without
using additional communication devices.
Network Switch B
Network Switch A
Type 2 Redundancy Nodes that are only

available in Simplex configuration
Redundant can be connected with a redundant
Switch switch. The switch automatically senses a
failed network component and fails-over to
Network Switch B a secondary link.
Network Switch A
Controller Controller
Network Switch B
Network Switch A Type 3 Redundancy Nodes such as

dual or TMR controllers are tightly
Dual
coupled so that each node can send the
same information. By connecting each
controller to alternate networks, data is still
<R> <S> <T> available if a controller or network fails.
Network Switch B
Network Switch A
TMR
Type 4 Redundancy This type provides

redundant controllers and redundant network
links for reliability. This is useful if
the active controller network interface cannot
Network Switch B sense a failed network condition.
Network Switch A
Summarized Redundant Networks for Different Applications

Data Highways
The PDH is the plant level supervisory network. The PDH connects the HMI server
with remote viewers, printers, historians, and external interfaces. The PDH has no
direct connection to the Mark VI controllers, which communicate over the unit data
highway (UDH). Using the Ethernet with the TCP/IP protocol over the PDH
provides an open system for third-party interfaces. The following figure shows the
equipment connections to the PDH.
GT #1 PEECC GT #2 PEECC GT #3 PEECC

220VAC
UPS ENET 0/1 ENET 0/0 CONSOLE AUX
SW1 SW5 SW9

PDH
PDH
PDH
UD H
UD H
UD H
ADH
ADH
ADH
TRUNK
TRUNK
TRUNK
CROSSOVER UTP
CROSSOVER UTP
CROSSOVER UTP
220VAC 220VAC 220VAC
UPS UPS UPS
SW2 SW6 SW10
PDH
PDH
PDH
UDH
UDH
UDH
ADH
ADH
ADH
TRUNK
TRUNK
TRUNK
21
A B A B A A B A B A B A B
NIC1 NIC2 NIC1 NIC1 NIC2 NIC1 NIC2
M M M M M
M
GT1_SVR uOSM GT2_SVR GT3_SVR

PC Desk SEE NOTE 6 PC Desk PC Desk
18in. Desktop LCD(dual) PEECC Rack - uOSM 18in. Desktop LCD(dual) 18in. Desktop LCD(dual)
Mouse Mouse Mouse
UPS BY GE
220VAC 220VAC 220VAC 220VAC

UPS UPS UPS
Customer Control Room

SW14
SW16
SW13
SW15
220VAC
220VAC
9 10 11 12 13 14 15 16 17 18 19 20 9 10 11 12 13 14 15 16 17 18 19 20
UPS
UPS
PDH UDH ADH TRUNK PDH UDH ADH T RUNK
PDH UDH PDH UDH
GSM 1 GSM 2
GSM 2
GSM 3 GSM 3
4
GSM 1
A B A B A B A B A B A B
NIC1 NIC2 NIC1 NIC2 NIC1 NIC2
M M M M M M
CRM1_SVR CRM2_SVR CRM3_SVR

18in. Desktop LCD(dual) 18in. Desktop LCD(dual) 18in. Desktop LCD(dual)
Mouse Mouse Mouse

UPS UPS UPS
Typical Plant Data Highway Layout

PDH Network Features
Feature Description
Type of Network Ethernet CSMA/CD in a single or redundant star configuration
Speed 100 Mb/s, Full duplex
Media and Distance Ethernet 100BaseTX for switch to controller/device connections. The cable is 22 to 26 AWG
with unshielded twisted pair, category 5e EIA/TIA 568 A/B. Distance is up to 100 meters.
Ethernet 100BaseFX, with fiber-optic cable, for distances up to 2 km (1.24 miles)*.
Number of Nodes Up to 1024 nodes supported
Protocols Ethernet-compatible protocol, typically TCP/IP-based. Use GE Standard Messaging (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
Summarized
3-4 • Chapter 3 Networks
Various third-party interfaces are available; GSM and Modbus are the most common.
60 of 1016
Note *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.

The UDH is an Ethernet-based network that provides direct or broadcast peer-to-peer
communications between controllers and an operator/maintenance interface. It uses
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 shows redundant UDH networks with connections to the
controllers and HMI servers.
GT #1 PEECC GT #1 - A192 GT #2 PEECC GT #2 - A192 GT #3 PEECC GT #3 - A192

Mark VI LCI Mark VI LCI Mark VI LCI
EX2100 EX2100 EX2100
T S R SW3 TRANSCEIVER T S R SW7 TRANSCEIVER T S R SW11 TRANSCEIVER
SW1 M1 M2 A B SW5 M1 M2 A B SW9 M1 M2 A B
PDH
PDH
PDH
PDH
PDH
PDH
UD H
UD H
UD H
UPS UPS UPS
UDH
UDH
UDH
ADH
ADH
ADH
ADH
ADH
ADH
TRU NK
TRU NK
TRU NK
TRUNK
TRUNK
TRUNK
CROSSOVER UTP
CROSSOVER UTP
CROSSOVER UTP
220VAC 220VAC 220VAC 220VAC 220VAC 220VAC
UPS UPS UPS UPS UPS UPS
SW4 SW8 SW12

SW2 SW6 SW10
PDH
PDH
PDH
PDH
PDH
PDH
U DH
U DH
U DH
U DH
UDH
UDH
ADH
ADH
ADH
AD H
ADH
ADH
TRUNK
TRUNK
TRUNK
TRUNK
TRU NK
TRU NK
M M M M M M
GT1_SVR GT2_SVR GT3_SVR

PC Desk PC Desk PC Desk
Mouse Mouse Mouse

UPS UPS UPS
Customer Control Room

SW14
SW16
SW13
SW15
220VAC
220VAC
9 10 11 12 13 14 15 16 17 18 19 20 9 10 11 12 13 14 15 16 17 18 19 20
UPS
UPS
PDH UD H ADH TR UNK PDH U DH AD H TRUNK
PDH UD H PDH UD H
M M M
M M M
UNIT DATA HIGHWAY (UDH)
CRM1_SVR CRM2_SVR CRM3_SVR
Mouse Mouse Mouse

UPS UPS UPS
Typical Unit Data Highway Layout

UDH Network Features
Feature Description
Type of Network Ethernet, full duplex, in a single or redundant star configuration
Media and Distance Ethernet 100BaseTX 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 meters. Ethernet
100BaseFX with fiber-optic cable optional for distances up to 2 km (1.24 miles).
Number of Nodes At least 25 nodes, given a 25 Hz data rate. For other configurations, contact the factory.
Type of Nodes Controllers, PLCs, operator interfaces, and engineering workstations
Supported
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.
Summarized
Data Highway Ethernet Switches
The UDH and PDH networks use Fast Ethernet switches. The system modules are
cabled into the switches creating a star-type network architecture. Two switches used
with an interconnecting cable provide redundancy.
Redundant switches provide redundant, duplex communication links to controllers

and HMIs. Primary and secondary designate the two redundant Ethernet links. If the
primary link fails, the converter automatically switches the traffic on the main link
over to the secondary link without interruption to network operation. At 10 Mb/s,
using the minimum data packet size, the maximum data loss during fail-over
transition is 2-3 packets.
Note Switches are configured by GE for the control system. Therefore, pre-
configured switches should be purchased from GE. Each switch is configured to
accept UDH and PDH.
GE Part # 323A4747NZP31(A, B, or C)
Configuration A B C
PDH 1-8 Single VLAN can be used for UDH or PDH 1-18,23-26
UDH 9-16 None
ADH 17-19 19-21
Uplinks 20-26 22 to Router
Configuration 323A4747NZP31A is the standard configuration with

323A4747NZP31B being used for legacy systems with separate UDH and PDH
networks. Part 323A4747NZP31C is obsolete and was used in special instances to
provide connectivity between the PDH and the onsite monitor (OSM) system.
GE Part # 323A4747NZP37(A or B)
Configuration A B
PDH 1-3 Single VLAN can be used for UDH or PDH
UDH 5-7
ADH None
Uplinks 4,8,9-16
Virtual LAN (VLAN) technology is used in the UDH and PDH infrastructure to
provide separate and redundant network infrastructure using the same hardware. The
multi-VLAN configuration (Configuration A) provides connectivity to both PDH
and UDH networks. Supplying multiple switches at each location provides
redundancy. The switch fabric provides separation of the data. Each uplink between
switches carries VLAN data encapsulated per IEEE 802.1q. The UDH VLAN data is
given priority over the other VLAN by increasing its 802.1p priority.
Summarized
Selecting IP Addresses for UDH and PDH
Use the following table to select IP addresses on the UDH and PDH. The standard IP
address is 192.168.ABC.XYZ.
Ethernet IP Address Rules
Network A BC X Y Z
Type Type Network
Number Controller/Device Number Unit Number Type of Device
UDH 1 01-99 1 = gas turbine controllers 1 = Unit 1 1 = R0
2 = steam turbine controllers 2 = Unit 2 2 = S0
•
• 3 = T0
9 = Unit 9 4 = HRSG A
5 = HRSG B
6 = EX2000 or EX2100 A
7 = EX2000 or EX2100 B
8 = EX2000 or EX2100 C
9 = Not assigned
0 = Static Starter
0 = All other 02 - 15 = Servers
devices on the 16 - 25 = Workstations
UDH
26 - 37 = Other stations (Viewers)
38 = Turbine Historian
39 = OSM
40 - 99 = Aux Controllers, such as
ISCs
PDH 2 01 – 54 2 to 199 are reserved for customer supplied items
200 to 254 are reserved for GE supplied items such as viewers and printers
The following are examples of IP addresses:
192.168.104.133 would be UDH number 4, gas turbine unit number 3, T0 core.
192.168.102.215 would be UDH number 2, steam turbine unit number 1, HRSG B.
192.168.201.201 could be a CIMPLICITY Viewer supplied by GE, residing on

PDH#1.
192.168.205.10 could be a customer-supplied printer residing on PDH#5.
Note Each item on the network such as a controller, server, or viewer must have an
IP address. The above addresses are recommended, but if this is a custom
configuration, the requisition takes precedence.
IONet
IONet is an Ethernet 10Base2 network used to communicate data between the VCMI
communication board in the control module, the I/O boards, and the three
independent sections of the Protection Module . In large systems, it is used to
communicate with an expansion VME board rack containing additional I/O boards.
These racks are called interface modules since they contain exclusively I/O boards
and a VCMI. IONet also communicates data between controllers in TMR systems.
Summarized
Note Remote I/O can be located up to 185 m (607 ft) from the controller.

Another application is to use the interface module as a remote I/O interface located at
the turbine or generator. The following figure shows a TMR configuration using
remote I/O and a protection module.
R0 S0 T0 R8 S8 T8
TMR System V
V U V U V U V V
with Remote P
C C C C C C P P
I/O Racks M R
M V M V V R R
I X I X I X O O O
IONet - R
IONet - S
IONet - T
R1 S1 T1 UCVX is Controller,
V V V VCMI is Bus Master,
VPRO is Protection
C I/O C I/O C I/O Module,
M Boards M Boards M Boards I/O are VME boards.
I I I (Terminal Boards not
IONet Supports
Multiple Remote shown)
I/O Racks
IONet Communications with Controllers, I/O, and Protection Modules

IONet Features
IONet Feature Description
Type of Network Ethernet using extension of ADL protocol
Speed 10 Mb/s data rate
Media and Ethernet 10Base2, RG-58 coax cable is standard
Distance Distance to 185 m (607 ft)
Ethernet 10BaseFL with fiber-optic cable and converters
Distance is 2 km (1.24 miles)
Number of Nodes 16 nodes
Protocol Extension of ADL protocol designed to avoid message collisions; Collision Sense (CSMA)
functionality is still maintained
Message Size Maximum packet size 1500 bytes
Message Integrity 32-bit CRC appended to each Ethernet packet
IONet - Communications Interface

Communication between the control module (control rack) and interface module (I/O
rack) is handled by the VCMI in each rack. In the control module, the VCMI
operates as the IONet master, while in the interface module it operates as an IONet
slave. The VCMI establishes the network ID, and displays the network ID, channel
ID, and status on its front cabinet LEDs.
The VCMI serves as the master frame counter for all nodes on the IONet. Frames are
sequentially numbered and all nodes on IONet run in the same frame. This ensures
that selected data is being transmitted and operated on correctly.
Summarized
I/O Data Collection
I/O Data Collection, Simplex Systems - When used in an interface module, the
VCMI acts as the VME bus master. It collects input data from the I/O boards and
transmits it to the control module through IONet. When it receives output data from
the control module, it distributes it to the I/O boards.
The VCMI in slot 1 of the control module operates as the IONet master. As packets
of input data are received from various racks on the IONet, the VCMI collects them
and transfers the data through the VME bus to the I/O table in the controller. After
application code completion, the VCMI transfers output values from the controller
I/O table to the VCMI where the data is then broadcast to all the I/O racks.
I/O Data Collection and Voting, TMR Systems - For a small TMR system, all
the I/O may be in one module (triplicated). In this case, the VCMI transfers the input
values from each of the I/O boards through the VME bus to an internal buffer. After
the individual board transfers are complete, the entire block of data is transferred to
the pre-vote table, and also sent as an input packet on the IONet. As the packet is
being sent, corresponding packets from the other two control modules are being
received through the other IONet ports. Each of these packets is then transferred to
the pre-vote table.
After all packets are in the pre-vote table, the voting takes place. Analog data
(floating point) goes through a median selector, while logical data (bit values) goes
through a two-out-of-three majority voter. The results are placed in the voted table.
A selected portion of the controller variables (the states such as counter/timer values
and sequence steps) must be transferred by the master VCMI boards to the other
master VCMI boards to be included in the vote process. At completion of the voting,
the voted table is transferred through the VME bus to the state table memory in the
controller.
For a larger TMR system with remote I/O racks, the procedure is very similar except
that packets of input values come into the master VCMI over IONet. After all the
input data is accumulated in the internal buffer, it is placed in the pre-vote table and
also sent to the other control modules over IONet. After all the packets and states are
in the pre-vote table, they are voted, and the results are transferred to the controller.
Output Data Packet - All the output data from a control module VCMI is placed
in packets. These packets are then broadcast on the IONet and received by all
connected interface and control modules. Each interface module VCMI extracts the
required information and distributes to its associated I/O boards.
Ethernet Global Data (EGD)

EGD allows you to share information between controller components in a networked
environment. 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.
Summarized
The exchange contains a configuration signature, which shows 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:
• 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 Supervisory data is transmitted periodically at either 480 or 960 ms. Control data is transmitted at
Communication 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 bytes. 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 VI 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.
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.
Summarized
R
EGD
Redundant
Path for UDH
UNIT DATA HIGHWAY

EGD
S I/O NET
T I/O NET
R I/O NET
S
EGD
T
EGD
Unit Data Highway EGD TMR Configuration
In a DUAL 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 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.
Modbus Communications
The Mark VI control platform can be a Modbus Slave on either the COM2 RS-232C
serial connection or over Ethernet. In the TMR configuration, commands are
replicated to multiple controllers so only one physical Modbus link is required. The
same functions supported over the serial ports are supported over Ethernet. All
Ethernet Modbus messages are received on Ethernet port 502.
Note The Modbus support is available in either the simplex or TMR configurations.
Messages are transmitted and received using the Modbus RTU transmission mode
where data is transmitted in 8-bit bytes. The other Modbus transmission mode where
characters are transmitted in ASCII is not supported. The supported Modbus point
data types are bits, shorts, longs, and floats. These points can be scaled and placed
into compatible Mark VI signal types.
Summarized
There are four Modbus register page types used:
• Input coils
• Output coils
• Input registers
• Holding registers
Since the Mark VI has high-priority control code operating at a fixed frame rate, it is
necessary to limit the amount of CPU resources that can be taken by the Modbus
interface. To limit the operation time, a limit on the number of commands per second
received by the Mark VI is enforced. The Mark VI control code also can disable all
Modbus commands by setting an internal logical signal.
There are two diagnostic utilities that can be used to diagnose problems with the
Modbus communications on a Mark VI. The first utility prints out the accumulated
Modbus errors from a network and the second prints out a log of the most recent
Modbus messages. This data can be viewed using the toolbox.
Note For additional information on Mark VI Modbus communications, refer to the

sections Ethernet Modbus Slave and Serial Modbus Slave and to document, GEI-
100535, Modbus Communications.
Ethernet Modbus Slave

Modbus is widely used in control systems to establish communication between
distributed control systems, PLCs, and HMIs. The Mark VI controller 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 third party Modbus master computers to read and
write signals that exist in the controller, using a subset of the Modbus function codes.
The Mark VI controller will respond to Ethernet Modbus commands received from
any of the Ethernet ports supported by its hardware configuration.
Ethernet Modbus may be configured as an independent interface or may share a

register map with a serial Modbus interface.
UNIT DATA HIGHWAY
Ethernet Ethernet
Modbus Modbus
Mark VI 90-70 PLC
ENET1
ENET1
ENET2
UCVx
VC MI
CPU
I/ O
I/ O
I/ O
ENET2
Simplex
RS-232C
Summarized
Serial Modbus
68 of 1016
Ethernet Modbus
Ethernet Modbus Features
Feature Description
Communication Type Multidrop Ethernet CSMA/CD, employing TCP/IP with Modbus Application Protocol
(MBAP) layered on top. Slave protocol only
Speed 10 Mb/s data rate
Media and Distance Using 10Base2 RG-58 coax, the maximum distance is 185 m (607 ft).
Using 10BaseT shielded twisted pair, with media access converter, the maximum
distance is 100 m (328 ft)
Using 10BaseFL fiber-optics, with media access converter, a distance of several
kilometers is possible
Only the coax cable can be multidropped; the other cable types use a hub forming a
Star network.
Message Integrity Ethernet supports a 32-bit CRC appended to each Ethernet packet.
Redundancy Responds to Modbus commands from any Ethernet interface supported by the
controller hardware
Supports register map sharing with serial Modbus
Function Codes
01 Read Coil Read the current status of a group of 1 to 2000 Boolean signals
02 Read Input Read the current status of a group of 1 to 2000 Boolean signals
03 Read Registers Read the current binary value in 1 to 125 holding registers
04 Read Input Read the current binary values in 1 to125 analog signal registers
Registers
05 Force Coil Force a single Boolean signal to a state of ON or OFF
06 Preset Register Set a specific binary value into holding registers
07 Read Exception Read the first 8 logic coils (coils 1-8) - short message length permits rapid reading
Status
15 Force Coils Force a series of 1 to 800 consecutive Boolean signals to a specific state
16 Preset Registers Set binary values into a series of 1 to 100 consecutive holding registers
Serial Modbus Slave

Serial Modbus is used to communicate between the Mark VI and the plant DCS. This
is shown as the Enterprise layer in the introduction to this chapter. The serial
Modbus communication link allows an operator at a remote location to make an
operator command by sending a logical command or an analog setpoint to the Mark
VI. 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 predetermined ramp rate.
Note The Mark VI controller also supports serial Modbus slave as a standard
interface.
The HMI Server supports serial Modbus as a standard interface. The DCS sends a
request for status information to the HMI, or the message can be a command to the
turbine control. The HMI is always a slave responding to requests from the serial
Modbus master. There can only be one master.
Summarized
Serial Modbus Features
Serial Modbus Feature Description
Type of communication Master/slave arrangement with the slave controller following the master; full duplex,
asynchronous communication
Speed 19,200 baud is standard; 9,600 baud is optional
Media and distance Using an RS-232C cable without a modem, the distance is 15.24 m (50 ft); using an RS-
485 converter it is 1.93 km (1.2 miles).
Mode ASCII Mode - Each 8-bit byte in the message is sent as two ASCII characters, the
hexadecimal representation of the byte. (Not available from the HMI server.)
Remote Terminal Unit (RTU) Mode - Each 8-bit byte in the message is sent with no
translation, which packs the data more efficiently than the ASCII mode, providing about
twice the throughput at the same baud rate.
Redundancy Supports register map sharing with Ethernet Modbus.
Message security An optional parity check is done on each byte and a CRC16 check sum is appended to the
message in the RTU mode; in the ASCII mode, a longitudinal redundancy check (LRC) is
appended to the message instead of the CRC.
Note This section discusses serial Modbus communication in general terms. Refer
to GEH-6410, Innovation Series Controller System Manual and HMI manuals for
additional information. Refer to GEH-6126, HMI Application Guide and GFK-1180,
®
CIMPLICITY HMI for Windows NT and Windows 95 User's Manual. For details on
how to configure the graphic screens refer to GFK-1396, CIMPLICITY HMI for
Windows NT and Windows 95 CimEdit Operation Manual.
Modbus Configuration
Systems are configured as single point-to-point RS-232C communication devices. A
GE device on Serial Modbus is a slave supporting binary Remote Terminal Unit
(RTU) full-duplex messages with CRC. Both dedicated and broadcast messages are
supported.
A dedicated message is a message addressed to a specific slave device with a

corresponding response from that slave. A broadcast message is addressed to all
slaves without a corresponding return response.
The binary RTU message mode uses an 8-bit binary character data for messages.
RTU mode defines how information is packed into the message fields by the sender
and decoded by the receiver. Each RTU message is transmitted in a continuous
stream with a 2-byte CRC checksum and contains a slave address. A slave station’s
address is a fixed unique value in the range of 1 to 255.
The Serial Modbus communications system supports 9600 and 19,200 baud, none,
even, or odd parity, and 7 or 8 data bits. Both the master and slave devices must be
configured with the same baud rate, parity, and data bit count.
Modbus Function Codes
Function
Codes Title Message Description
01 01 Read Holding Coils Read the current status of a group of 1 to 2000 Boolean signals
02 02 Read Input Coils Read the current status of a group of 1 to 2000 Boolean signals
03 03 Read Holding Registers Read the current binary values in 1 to 125 analog signal registers
04 04 Read Input Registers Read the current binary values in 1 to125 analog signal registers
05 05 Force Single Holding Coil Force (or write) a single Boolean signal to a state of ON or OFF
Summarized
06 06 Preset Single Holding Preset (or write) a specific binary value into a holding register
Register

07 07 Read Exception Status Read the first 8 logic coils (coils 1-8) - short message length permits
rapid reading of these values
08 08 Loopback Test Loopback diagnostic to test communication system
15 15 Force Multiple Coils Force a series of 1 to 800 consecutive Boolean signals to a specific
state
16 16 Preset Multiple Holding Set binary values into a series of 1 to 100 consecutive analog signals
Registers
Hardware Configuration
A Data Terminal Equipment Device (DTD) transmits serial data on pin 3 (TD) of a
9-pin RS-232C cable. A Data Communication Device (DCE) is identified as a device
that transmits serial data on pin 2 (RD) of a 9-pin RS-232C cable. Refer to the
following table.
Using this definition, the GE slave Serial Modbus device is DTD because it transmits
serial data on pin 3 (TD) of the 9-pin RS-232C cable. If the master serial Modbus
device is also a DTD, connecting the master and slave devices together requires an
RS-232C null modem cable.
The RS-232C standard specifies 25 signal lines: 20 lines for routine operation, two
lines for modem testing, and three remaining lines unassigned. Nine of the signal
pins are used in a nominal RS-232C communication system. Cable references in this
document will refer to the 9-pin cable definition found in the following table.
Terms describing the various signals used in sending or receiving data are expressed
from the point of view of the DTE. For example the signal, transmit data (TD),
represents the transmission of data coming from the DTD going to the DCE.
Each RS-232C signal uses a single wire. The standard specifies the conventions used
to send sequential data as a sequence of voltage changes signifying the state of each
signal. Depending on the signal group, a negative voltage (less than -3 V) represents
either a binary 1 data bit, a signal mark, or a control off condition, while a positive
voltage (greater that +3 V) represents either a binary zero data bit, a signal space, or
a control on condition. Because of voltage limitations, an RS-232C cable may not be
longer than 15.2 m (50 ft).
Nine of the twenty-five RS-232C pins are used in a common asynchronous

application. All nine pins are necessary in a system configured for hardware
handshaking. The Modbus system does not use hardware handshaking; therefore it
requires just three wires, receive data (RD), transmit data (TD), and signal ground
(GND) to transmit and receive data.
The nine RS-232C signals used in the asynchronous communication system can be
broken down into four groups: data, control, timing, ground.
RS-232C Connector Pinout Definition
DTE DTE Signal Function
DB 9 DB 25 Description Output Input Type
1 8 Data Carrier Detect X Control Signal comes from the other RS-232C
(DCD) device telling the DTE device that a circuit
has been established
2 3 Receive Data (RD) X Data Receiving serial data
3 2 Transmit Data (TD) X Data Transmitting serial data
4 20 Data Terminal Ready X Control DTE places positive voltage on this pin when
(DTR) powered up
Summarized
5 7 Signal Ground (GND) Ground Must be connected

6 6 Data Set Ready (DSR) X Control Signal from other RS-232C device telling the
DTE that the other RS-232C device is
powered up
7 4 Request To Send X Control DTE has data to send and places this pin
(RTS) high to request permission to transmit
8 5 Clear To Send (CTS) X Control DTE looks for positive voltage on this pin for
permission to transmit data
9 22 Ring Indicator (RI) X Control A modem signal indicating a ringing signal
on the telephone line
Data Signal wires are used to send and receive serial data. Pin 2 (RD) and pin 3
(TD) are used for transmitting data signals. A positive voltage (> +3 V) on either of
these two pins signifies a logic 0 data bit or space data signal. A negative voltage (< -
3 V) on either of these two pins signifies a logic 1 data bit or mark signal.
Control Signals coordinate and control the flow of data over the RS-232C cable.
Pins 1 (DCD), 4 (DTR), 6 (DSR), 7 (RTS), and 8 (CTS) are used for control signals.
A positive voltage (> +3 V) indicates a control on signal, while a negative voltage (<
-3 V) signifies a control off signal. When a device is configured for hardware
handshaking, these signals are used to control the communications.
Timing Signals are not used in an asynchronous 9-wire cable. These signals,
commonly called clock signals, are used in synchronous communication systems to
synchronize the data rate between transmitting and receiving devices. The logic
signal definitions used for timing are identical to those used for control signals.
Signal Ground on both ends of an RS-232C cable must be connected. Frame

ground is sometimes used in 25-pin RS-232C cables as a protective ground.
Serial Port Parameters

An RS-232C serial port is driven by a computer chip called a universal asynchronous
receiver/transmitter (UART). The UART sends an 8-bit byte of data out of a serial
port preceded with a start bit, the 8 data bits, an optional parity bit, and one or two
stop bits. The device on the other end of the serial cable must be configured the same
as the sender to understand the received data. The software configurable setup
parameters for a serial port are baud rate, parity, stop, and data bit counts.
Transmission baud rate signifies the bit transmission speed measured in bits per
second. Parity adds an extra bit that provides a mechanism to detect corrupted serial
data characters. Stop bits are used to pad a serial data character to a specific number
of bits. If the receiver expects 11 bits for each character, the sum of the start bit, data
bits, parity bit, and the specified stop bits should equal 11. The stop bits are used to
adjust the total to the desired bit count.
UARTs support three serial data transmission modes: simplex (one way only), full
duplex (bi-directional simultaneously), and half duplex (non-simultaneous bi-
directional). GE’s Modbus slave device supports only full duplex data transmission.
Device number is the physical RS-232C communication port.
Baud rate is the serial data transmission rate of the Modbus device measured in bits
per second. The GE Modbus slave device supports 9,600 and 19,200 baud (default).
Stop bits are used to pad the number of bits that are transmitted for each byte of
serial data. The GE Modbus slave device supports 1 or 2 stop bits. The default is 1
stop bit.
Parity provides a mechanism to error check individual serial 8-bit data bytes. The
Summarized
GE Modbus slave device supports none, even, and odd parity. The default is none.
72 of 1016
Code (byte size) is the number of data bits in each serial character. The GE
Modbus slave device supports 7 and 8-bit data bytes. The default byte size is 8 bits.
Ethernet GSM
Some applications require transmitting alarm and event information to the DCS. This
information includes high-resolution local time tags in the controller for alarms (25
Hz), system events (25 Hz), and sequence of events (SOE) for contact inputs (1 ms).
Traditional SOEs have required multiple contacts for each trip contact with one
contact wired to the turbine control to initiate a trip and the other contact to a
separate SOE instrumentation rack for monitoring. The Mark VI uses dedicated
processors in each contact input board to time stamp all contact inputs with a 1 ms
time stamp, thus eliminating the initial cost and long term maintenance of a separate
SOE system.
Note The HMI server has the turbine data to support GSM messages.
An Ethernet link is available using TCP/IP to transmit data with the local time tags to
the plant level control. The link supports all the alarms, events, and SOEs in the
Mark VI cabinet. GE supplies an application layer protocol called GSM (GEDS
Standard Messages), which supports four classes of application level messages. The
HMI Server is the source of the Ethernet GSM communication.
HMI View Node
PLANT DISTRIBUTED CONTROL SYSTEM
(DCS)
Ethernet Ethernet
GSM Modbus
PLANT DATA HIGHWAY
PLANT DATA HIGHWAY
HMI Server Node HMI Server Node
Modbus Communication
From UDH From UDH

Communication to DCS from HMI using Modbus or Ethernet Options
Summarized
Administration Messages are sent from the HMI to the DCS with a Support Unit
message, which describes 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 occurs or clears, a system event occurs or clears, or a contact input
SOE closes or opens. Each logic point is transmitted 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 5,000 data points in the Mark VI 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 are sent from the DCS to the HMI including
turbine control commands and alarm queue commands. Turbine control commands
include momentary logical commands such as raise/lower, start/stop, and analog
setpoint target commands. Alarm queue commands consist of silence (plant alarm
horn) and reset commands as well as alarm dump requests that cause the entire alarm
queue to be transmitted from the Mark VI to the DCS.
PROFIBUS Communications
PROFIBUS is used in wide variety of industrial applications. It is defined in
PROFIBUS Standard EN 50170 and in other ancillary guideline specifications.
PROFIBUS devices are distinguished as masters or slaves. Masters control the bus
and initiate data communication. They decide bus access by a token passing
protocol. Slaves, not having bus access rights, only respond to messages received
from masters. Slaves are peripherals such as I/O devices, transducers, valves, and
such devices. PROFIBUS is an open fieldbus communication standard.
Note PROFIBUS functionality is available in simplex, non-TMR Mark VIs only.
At the physical layer, PROFIBUS supports three transmission mediums: RS-485 for
universal applications; IEC 1158-2 for process automation; and optical fibers for
special noise immunity and distance requirements. The Mark VI PROFIBUS
controller provides opto-isolated RS-485 interfaces routed to 9-pin D-sub
connectors. Termination resistors are not included in the interface and must therefore
be provided by external connectors. Various bus speeds ranging from 9.6 kbit/s to 12
Mbit/s are supported, although maximum bus lengths decrease as bus speeds
increase.
To meet an extensive range of industrial requirements, PROFIBUS consists of three

variations: PROFIBUS-DP, PROFIBUS-FMS, and PROFIBUS-PA. Optimized for
speed and efficiency, PROFIBUS-DP is utilized in approximately 90% of
PROFIBUS slave applications. The Mark VI PROFIBUS implementation provides
PROFIBUS-DP master functionality. PROFIBUS-DP masters are divided into Class
1 and Class 2 types. Class 1 masters cyclically exchange information with slaves in
defined message cycles, and Class 2 masters provide configuration, monitoring, and
maintenance functionality.
Note The Mark VI operates as a PROFIBUS-DP Class 1 master exchanging

information (generally I/O data) with slave devices each frame.
Summarized
Mark VI UCVE controller versions are available providing one to three PROFIBUS-
DP masters. Each may operate as the single bus master or may have several masters
on the same bus. Without repeaters, up to 32 stations (masters and slaves) may be
configured per bus segment. With repeaters, up to 126 stations may exist on a bus.
Note More information on PROFIBUS can be obtained at www.profibus.com.
PROFIBUS Features
PROFIBUS Feature Description
Type of PROFIBUS-DP Class 1 master/slave arrangement with slaves responding to masters once
communication per frame; a standardized application based on the ISO/OSI model layers 1 and 2
Network topology Linear bus, terminated at both ends with stubs possible
Speed 9.6 kbit/s, 19.2 kbit/s, 93.75 kbit/s, 187.5 kbit/s, 500 kbit/s, 1.5 Mbit/s, 12 Mbit/s
Media Shielded twisted pair cable
Number of stations Up to 32 stations per line segment; extendable to 126 stations with up to 4 repeaters
Connector 9-pin D-sub connector
Number of masters From 1-3 masters per UCVE
PROFIBUS Bus Length
Maximum Bus
kb/s Length in Meters
9.6 1200
19.2 1200
93.75 1200
187.5 1000
500 400
1500 200
12000 100
Configuration
The properties of all PROFIBUS master and slave devices are defined in electronic
device data sheets called GSD files (for example, SOFTB203.GSD). PROFIBUS can
be configured with configuration tools such as Softing AG’s PROFI-KON-DP.
These tools enable the configuration of PROFIBUS networks that comprise devices
from different suppliers, based on information imported from corresponding GSD
files.
Note GSD files define the properties of all PROFIBUS devices.
The third-party tool is used rather than the toolbox to identify the devices making up
PROFIBUS networks as well as specifying bus parameters and device options (also
called parameters). The toolbox downloads the PROFIBUS configurations to Mark
VI permanent storage along with the normal application code files.
Note Although the Softing AG’s PROFI-KON-DP tool is provided as the

PROFIBUS configuration tool, any tool with the binary configuration file produced
in the Softing format can be used.
For additional information on Mark VI PROFIBUS communications, refer to

document, GEI-100536, PROFIBUS Communications.
Summarized
I/O and Diagnostics
PROFIBUS I/O transfer with slave devices is driven at the Mark VI application level
by a set of standard block library blocks. Pairs of blocks read and write analog,
Boolean, and byte-oriented data types. The analog blocks read two, four, or eight
bytes, depending on associated signal data types, and handle the proper byte
swapping. The Boolean blocks automatically pack and unpack bit-packed I/O data.
The byte-oriented blocks access PROFIBUS I/O as single bytes without byte
swapping or bit packing. To facilitate reading and writing unsigned short integer-
oriented PROFIBUS I/O (needed since unsigned short signals are not available), a
pair of analog-to-word/word-to-analog blocks work in tandem with the PROFIBUS
analog I/O blocks as needed.
Data transfers initiated by multiple blocks operating during a frame are fully
coherent since data exchange with slave devices takes place at the end of each frame.
PROFIBUS defines three types of diagnostic messages generated by slave devices:
• Station-related diagnostics provide general station status.

• Module-related diagnostics indicate certain modules having diagnostics pending.
• Channel-related diagnostics specify fault causes at the channel (point) level.
Note PROFIBUS diagnostics can be monitored by the toolbox and the Mark VI
application.
Presence of any of these diagnostics can be monitored by the toolbox as well as in

Mark VI applications by a PROFIBUS diagnostic block included in the standard
block library.
Fiber-Optic Cables
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 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:
Summarized
• The cost, especially for short runs, may be more for a fiber-optic link.
76 of 1016
• 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.
Components
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.
Multimode 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.
Fiber-optic Cable
Multimode 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 microns 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 microns in diameter. 62.5/125 optical cable is the most
common type of cable and should be used.
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.
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.
Summarized
• 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.
Fiber-Optic Converter
Fiber-optic connections are normally terminated at the 100BaseFX fiber port of the
Ethernet switch. Occasionally, the Mark VI communication system may require an
Ethernet media converter to convert selected UDH and PDH electrical signals to
fiber-optic signals. The typical media converter makes a two-way conversion of one
or more Ethernet 100BaseTX signals to Ethernet 100Base FX signals.
100Base FX 100BaseTX
Port Port
Dimensions: Power: Data:

TX RX
Pwr
Width: 3.0 (76 mm) 120 V ac, 100 Mbps,
Height: 1.0 (25 mm) 60 Hz fiber optic
Depth: 4.75 (119 mm)
Fiber UTP/STP
Media Converter, Ethernet Electric to Ethernet Fiber-optic
Connectors
The 100Base FX fiber-optic cables for indoor use in Mark VI control have SC type
connectors. The connector, shown 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 shown, or they can be separate.
Locating
Key
.
Fiber
.
Solid Glass
Center
Snap-in connnectors
SC Connector for Fiber-optic Cables
Summarized
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.
System Considerations
The following considerations should be noted when designing a fiber-optic network.
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.
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.
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.
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
Summarized Part Numbers (from OCC)

Each of these cables are SMF 8.3/125um 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
®
Siecor Corporation
PO Box 489
Hickory, NC 28603-0489
Phone: (800)743-2673
Fiber-optic Connectors:
®
3M - Connectors and Installation kit
Thomas & Betts - Connectors and Assembly polishing kit
Amphenol – Connectors and Termination kit
Single-mode Fiber-optic Cabling

Single-mode fiber-optic (SMF) cable is approved for use in the Mark VI 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)
cable limit of 2000 m (2187.2 yd) to 15000 m (16404.00 yd)
The following figure shows the differences between the two cable types.
Dispersion
125um
62.5um
Input Output
Pulse Pulse
Light Transmission in Multi-mode Fiber-optic Cable Cross section

125um
9um
Input Output
Pulse Pulse
Light Transmission in Single-mode Fiber-optic Cable Cross section
Multi-mode and Single-mode Fiber-optic Cable Transmissions
Summarized
The figure shows a typical 62.5/125 µm MMF segment. Light (typically from a
LED) enters through an aperture at the left, 62.5 µm in diameter. This aperture is
many times the dimension of the typical 1500 µm wavelength used for transmission.
This difference between the aperture and the wavelengths allows waves to enter at
multiple angles. Since the cladding material has a different index of refraction than
the core, these waves will be reflected due to the large angle of incidence (Snells
Law). Because of different angles, there are many paths the light can make through
the fiber with each taking a different time to arrive at the detector. This 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.
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 because the
signal attenuation per foot is less. The main disadvantage of SMF cables is the cost
of installation.
IONet Components (Single-Mode Fiber)

For Mark VI Control IO-Net Topologies, the following rules apply for deploying
SMF Systems.
1 Single-Mode Fiber-optic is validated for use on the Mark VI Control IONet

using the N-Tron 508FXE2-SC-15 switch
2 The same general guideline as MMF of no more than (5) switches should be
placed in series should be maintained, (more were tested).
The topology should be kept as flat and balanced as possible (star topology).
The N-Tron 508FXE2-SC-15 switch is the ONLY switch validated and approved for
this application. Use of any other switch in this application can result in poor
operation and/or damage to the associated equipment. The N-Tron 508FXE2-SC-15
can be identified from the following label:
Side View of N-Tron 508FXE2-SC-15 Discontinuities
Summarized
Time Synchronization
The time synchronization option synchronizes all turbine controls, generator
controls, and HMIs on the UDH to a Global Time Source (GTS). 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, either the BC620AT or BC627AT, is placed in

the HMI computer. This board acquires time from the GTS 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 through Network Time
Protocol (NTP). The HMI Server provides time to time slaves either by broadcasting
time, or by responding to NTP time queries, or by both methods. Refer to RFC 1305
Network Time Protocol (Version 3) dated March 1992 for details.
Redundant time synchronization is provided by supplying a time/frequency

processor board in another HMI Server as a backup. 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 global rather than local. This is done
because global time steadily increases at a constant rate while corrections are
allowed to local time. Historical data is stored with global time to minimize
discontinuities.
Redundant Time Sources

If either the GTS or time master becomes inoperative, the backup is to switch the
BC620AT or BC627AT to flywheel mode with a drift of ±2 ms/hour. In most cases,
this allows sufficient time to repair the GTS 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 GTS, which time master has the best quality signal, and which master is
listed first in the configuration file.
Selection of Time Sources

The BC620AT and BC627AT boards support the use of several different time
sources; however, the time synchronization software does not support all sources
supported by the BC620AT board. A list of time sources supported by both the
BC620AT 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
Summarized
– TTL/CMOS compatible voltage levels
82 of 1016
• 1 PPS (one pulse per second) using the External 1 PPS 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 or
BC627AT board
– Flywheel mode as the sole time source for the plant
Summarized
Notes
84 of 1016
CHAPTER 4
Chapter 4 Codes, Standards, and

Environment
Introduction
This chapter describes the codes, 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.
Safety Standards
EN 61010-1 Safety Requirements for Electrical Equipment for Measurement, Control, and
Laboratory Use, Part 1: General Requirements
CAN/CSA 22.2 No. 1010.1-92 Safety Requirements for Electrical Equipment for Measurement, Control, and
Laboratory Use, Part 1: General Requirements
ANSI/ISA 82.02.01 1999 Safety Standard for Electrical and Electronic Test, Measuring, Controlling, and
Related Equipment – General Requirements
IEC 60529 Intrusion Protection Codes/NEMA 1/IP 20
Electrical
Printed Circuit Board Assemblies
UL 796 Printed Circuit Boards
ANSI IPC guidelines
ANSI IPC/EIA guidelines
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.
EN 61000-6-4: 2001 Generic Emissions Industrial Environment

EN 61000-6-2: 2001 Generic Immunity Industrial Environment
IEC 61000-4-2:1995 Electrostatic Discharge Susceptibility
IEC 61000-4-3:2006 Radiated RF Immunity
Summarized
IEC 61000-4-4:2005 Electrical Fast Transient Susceptibility

I of 1016
Chapter 4 Codes, Standards, and Environment • 4-1
IEC 61000-4-5:2006 Surge Immunity
IEC 61000-4-6:1996 Conducted RF Immunity
IEC 61000-4-11:2004 Voltage Variation, Dips and Interruptions
Authorized Representative and Responsible Person:
Eurolink (Europe) Ltd.

Avalon House
Marcham Road
Abingdon
Oxfordshire OX14 1UD UK
Low Voltage Directive 2006/95/EC

EN 61010-1 Safety Requirements for Electrical Equipment for Measurement,
Control, and Laboratory Use, Part 1: General Requirements
Supply Voltage
Line Variations
Ac Supplies – Operating line variations of ±10%
IEEE STD 141-1993 defines the Equipment Terminal Voltage – Utilization voltage.
The above meets IEC 60204-1 1999, and exceeds IEEE STD 141-1993, and ANSI
C84.1-1989.
Dc Supplies – Operating line variations of -30%, +20% or 145 V dc. This meets
IEC 60204-1 1999.
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 1999 and IEEE STD 141-1993.
Harmonic Distortion
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 – 30th
harmonic
This meets IEC 60204-1 1999.
Current: The system specification is not per individual equipment
Less than 15% of maximum demand load current for harmonics less than 11
Summarized 86
4-2 • Chapter 4 Codes, Standards, and Environment of 1016
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.
Frequency Variations
Frequency variation of ±5% when operating from ac supplies (20 Hz/sec slew rate)
This exceeds IEC 60204-1 1999.
Surge
Withstand 2 kV common mode, 1 kV differential mode
This meets IEC 61000-4-5 (ENV50142), and ANSI C62.41 (combination wave).
Clearances
NEMA Tables 7-1 and 7-2 from NEMA ICS1-2000
This meets IEC 61010-1:1993/A2: 1995, CSA C22.2 #14, and UL 508C.
Power Loss
100 % Loss of supply - minimum 10 ms for normal operation of power products
100 % Loss of supply - minimum 500 ms before control products require reset (only
applicable to ac powered systems with DACAs; not applicable to dc-only powered
Mark VIs).
This exceeds IEC 61000-4-11.
Environment
Storage
If the system is not installed immediately, 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.
Summarized
– Maintain the following environment in the storage enclosure:

I of 1016
– Recommended ambient storage temperature limits from -40 to 80°C (-
40 to 176 °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
– No temperature variations that cause moisture condensation
Moisture on certain internal parts can cause electrical

failure.
Condensation occurs with temperature drops of 15°C (27 °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.
Operating
The Mark VI control components cabinet is suited to most industrial environments.
To ensure proper performance and normal operational life, the environment should
be maintained as follows:
• Temperature at bottom of module (acceptable):

Control Module with running fans 0 to 60°C (32 to 140 °F)
I/O Module 0 to 60°C (32 to 140 °F)
• Enclosures should be designed to maintain this temperature range.

• Relative humidity: 5 to 95%, non-condensing.
Note Higher ambient temperature decreases the life expectancy of any electronic
component.
Environments that include excessive amounts of any of the following elements

reduce panel performance and life:
• Dust, dirt, or foreign matter

• Vibration or shock
• Moisture or vapors
• Rapid temperature changes
• Caustic fumes
• Power line fluctuations
Summarized 88
• Electromagnetic interference 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
The preferred location for the Mark VI control system cabinet would be in an
environmentally controlled room or in the control room itself. The cabinet should be
mounted where the 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. Also, air passing through the conduit must be within the acceptable
temperature range as listed previously.
Elevation
Equipment elevation is related to the equivalent ambient air pressure.
• Normal Operation - 0 to1000 m (3286.8 ft) (101.3 kPa - 89.8 kPa)

• Extended Operation - 1000 to 3050 m (3286.8 ft to 10,006.5 ft) (89.8 kPa - 69.7
kPa)
• Shipping - 4600 m (15,091.8 ft) maximum (57.2 kPa)
Note A guideline for system behavior as a function of altitude is that for altitudes
above 1000 m (3286.8 ft), the maximum ambient rating of the equipment decreases
linearly to a rating of 5°C (41°F) at 3050 m (10,006.5 ft).
The extended operation and shipping specifications exceed EN50178.
Contaminants
Gas
The control equipment withstands the following concentrations of corrosive gases at

50% relative humidity and 40°C (104 °F):
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
The above meets EN50178 Section A.6.1.4 Table A.2 (m).
Summarized
I of 1016
Vibration
Seismic
Universal Building Code (UBC) - Seismic Code section 2312 Zone 4 (Optional)
Operating / Installed at Site
Vibration of 1.0 G Horizontal, 0.5 G Vertical at 15 to 120 Hz
See Seismic UBC for frequencies lower than 15 Hz.
Packaging
The standard Mark VI cabinets meet NEMA 1 requirements (similar to the IP-20
cabinet).
Optional cabinets for special applications meet NEMA 12 (IP-54), NEMA 4 (IP-65),
and NEMA 4X (IP-68) requirements. Redundant heat exchangers or air conditioners,
when required, can be supplied for the above optional cabinets.
UL Class 1 Division 2 Listed Boards

Certain boards used in the Mark VI are UL listed (E207685) for Class 1 Division 2,
Groups A, B, C, and D, Hazardous Locations, Temperature Class T4 using UL-1604.
Division 2 is described by NFPA 70 NEC 1999 Article 500 (NFPA - National Fire
Protection Association, NEC - National Electrical Code).
The Mark VI boards/board combinations that are listed may be found under file
number E207685 at the UL website and currently include:
• IS200VCMIH1B, H2B
• IS200DTCCH1A, IS200VTCCH1C
• IS200DRTDH1A, IS200VRTDH1C
• IS200DTAIH1A, IS200VAICH1C
• IS200DTAOH1A, IS200VAOCH1B
• IS200DTCIH1A, IS200VCRCH1B
• IS200DRLYH1B
• IS200DTURH1A, IS200VTURH1B
• IS200DTRTH1A
• IS200DSVOH2B, IS200VSVOH1B
• IS200DVIBH1B, IS200VVIBH1C
• IS200DSCBH1A, IS200VSCAH2A
• IS215UCVEH2A, M01A, M03A, M04A, M05A
• IS215UCVDH2A
• IS2020LVPSG1A
Summarized 90
CHAPTER 6
Chapter 6 Tools and System

Interface
Introduction
This chapter summarizes the tools used for configuring, loading, and operating the
Mark VI system. These include the Control System Toolbox (toolbox),
CIMPLICITY HMI operator interface, and the Turbine Historian.
Toolbox
®
The toolbox is Windows -based software for configuring and maintaining the Mark
VI control system. The software usually runs on an engineering workstation or a
CIMPLICITY HMI located on the PDH. For details, refer to GEH-6403, Control
System Toolbox for a Mark VI Controller.
IONet communicates with all the control and interface racks. This network topology
is configured using the toolbox. Similarly, the toolbox configures all the I/O boards
in the racks and the I/O points in the boards. the following figure displays the
toolbox screen used to select the racks.
The Outline View on the left side of the screen is used to select the racks required for
the system. This view displays all the racks inserted under Mark VI I/O. In the
example, three TMR Rack 0s are included under the heading Rack 0 Channel R/S/T
(TMR).
Summarized
I of 1016 Chapter 6 Tools and System Interface • 6-1
Click on the TMR rack in the Outline View (Rack 0 The Summary View displays a
in this example) to view all the channels at the graphic of each rack and all the
same time in the Summary View. boards they contain.
Configuring the Equipment Racks
Configuring the Application

The turbine control application is configured in the toolbox using graphically
connected control blocks, which display in the Summary View. These blocks consist
of basic analog and discrete functions and a library of special turbine control blocks.
The Standard Block library contains over 60 different control blocks designed for
discrete and continuous control applications. Blocks provide a simple graphical way
for the engineer to configure the control system. The turbine block library contains
more than 150 additional blocks relating to turbine control applications.
Summarized
6-2 • Chapter 6 Tools and System Interface 92 of 1016
The control system is configured in the toolbox work area, displayed in the following
figure The Outline View on the left side of the screen displays the control device.
The Summary View on the right side of the screen displays the graphical
configuration of the selected item. Block inputs and outputs are connected with
signals to form the control configuration. These connections are created by dragging
and dropping a signal from a block output to another block input. The connected
blocks form macros, and at a higher level, the blocks and macros form tasks covering
major sections of the complete control.
Connecting Control Blocks in the Work Area
CIMPLICITY HMI
The CIMPLICITY HMI is the main operator interface to the Mark VI turbine control
system. HMI is a computer with a Windows operating system and CIMPLICITY
graphics display system, communicating with the controllers over Ethernet.
For details refer to GEH-6126, HMI Application Guide. Also refer to GFK-1180,
CIMPLICITY HMI for Windows NT and Windows 95 User's Manual. For details on
how to configure the graphic screens refer to GFK-1396 CIMPLICITY HMI for
Windows NT and Windows 95 CimEdit Operation Manual.
Basic Description
The Mark VI HMI consists of three distinct elements:
HMI 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 provides
device communication for both internal and external data interchanges.
System 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. The
database is used for system configuration, but not required for running the system.
Summarized
HMI viewer provides the visual functions, and is the client of the server. It contains
the operator interface software, which allows the operator or maintenance personnel
to view screen graphics, data values, alarms, and trends, as well as issue commands,
edit control coefficient values, and obtain system logs and reports.
Depending on the size of the system, these three elements can be combined into a
single computer, or distributed in multiple units. The modular nature of the HMI
allows units to be expanded incrementally as system needs change. A typical Viewer
screen using graphics and real-time turbine data is displayed in the following figure.
In the graphic display, special displays can be obtained using the buttons in the
column on the right side. Also note the setpoint button for numeric entry and the
raise/lower arrows for opening and closing valves.
Alarm Detail
display selection
Shaft Vibration
display selection
Setpoint Entry
selection
Alarm Summary
window
Interactive Operator Display for Steam Turbine & Generator
Product Features
The HMI contains a number of product features important for power plant control:
• Dynamic graphics
• Alarm displays
• Process variable trending
• Point control display for changing setpoints
• Database logger
• HMI access security
• Data Distribution Equipment (DDE) application interface
Summarized
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 user graphic
screen displays. Editing and animation tools, with the familiar Windows
environment, provide an intuitive, easy to use interface. Features include:
• Standard shape library

• Object Linking and Embedding (OLE)
• Movement and rotation animation
• Filled object capabilities, and interior and border animation
CimView is the HMI run-time portion, displaying the process information in
graphical formats. In CimView, the operator can view the system screens, and
screens from other applications, using OLE automation, run scripts, and get
descriptions of object actions. Screens have a 1-second refresh rate, and a typical
graphical display takes 1second 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.
Trending, based on ActiveX technology, gives user’s data analysis capabilities.

Trending uses data collected by the HMI or data from other third-party software
packages or interfaces. Data comparisons between current and past variable data can
be made for identification of process problems. Trending includes multiple trending
charts per graphic screen with unlimited pens per chart, and the operator can resize
or move trend windows to convenient locations on the display.
The point control cabinet provides a listing of points in the system with real-
time values and alarm status. Operators can view and change local and remote set
points using the up/down arrows or by direct numeric entry. Alarms can be enabled
and disabled, and alarm limits modified by authorized personnel.
The basic control engine allows users to define control actions in response to
system events. A single event can invoke multiple actions, or one action can be
invoked by many events. The program editor uses a Visual Basic for Applications
compliant programming language.
Optional features include the Web Gateway that allows operators to access HMI data
from anywhere in the world over the Internet. Third party interfaces allow the HMI
to exchange data with distributed control systems, programmable logic controllers,
I/O devices, and other computers.
Computer Operator Interface (COI)

The COI consists of a set of product and application specific operator displays
running on a small cabinet computer (10.4 or 12.1 inch touch screen) hosting the
embedded Windows operating system. This operating system uses only the
components of the operating system required for a specific application. This results
in all the power and development advantages of a Windows operating system.
Development, installation or modification of requisition content requires the GE
Control System Toolbox (toolbox). For details, refer to GEH-6403, Control System
Toolbox for a Mark VI Controller.
Summarized
The COI can be installed in many different configurations, depending on the product
line and specific requisition requirements. For example, it can be installed in the
cabinet door for Mark VI applications or in a control room desk for Excitation
Control System applications. The only cabling requirements are for power and for
the Ethernet connection to the UDH. Network communication is through the
integrated auto-sensing 10/100BaseT Ethernet connection. Expansion possibilities
for the computer are limited, although it does support connection of external devices
through FDD, IDE, and USB connections.
The COI can be directly connected to the Mark VI or Excitation Control System, or
it can be connected through an EGD Ethernet switch. A redundant topology is
available when the controller is ordered with a second Ethernet port.
The networking of the COI to the Mark VI is requisitioned or customer-defined.
Interface Features
Numeric data displays are driven by EGD pages transmitted by the controller. The
refresh rate depends both on the rate at which the controller transmits the pages, and
the rate at which the COI refreshes the fields. Both are set at configuration time in
the toolbox.
The COI uses a touch screen, and no keyboard or mouse is provided. The color of
pushbuttons are feedbacks and represent state conditions. To change the state or
condition, press the button. The color of the button changes if the command is
accepted and the change implemented by the controller.
Numeric inputs on the COI touch screen are made by touching a numeric field that
supports input. A numeric keypad then displays and the desired number can be
entered.
An Alarm Window is provided and an alarm is selected by touching it. Then Ack,
Silence, Lock, or Unlock the alarm by pressing the corresponding button. Multiple
alarms can be selected by dragging through the alarm list. Pressing the button then
applies to all selected alarms.
Note For complete information, refer to GEI-100434, Computer Operator Interface

(COI) for Mark VI or EX2100 Systems.
Turbine Historian
The Turbine Historian is a data archival system based on client-server technology.
This provides data collection, storage, and display of power island and auxiliary
process data. Depending on the requirements, the product can be configured for just
turbine-related data, or for broader applications that include balance of plant process
data.
The Turbine Historian combines high-resolution digital event data from the turbine
controller with process analog data creating a sophisticated tool for investigating
cause-effect relationships. It provides a menu of pre-defined database query forms
for typical analysis relating to the turbine operations. Flexible tools enable the
operator to quickly generate custom trends and reports from the archived process
data.
Summarized
System Configuration
The Turbine Historian provides historical data archiving and retrieval functions.
When required, the system architecture provides time synchronization to ensure time
coherent data.
The Turbine Historian accesses turbine controller data through the UDH as shown in
the figure below. Additional Turbine Historian data acquisition is performed through
Modbus and/or Ethernet-based interfaces. Data from third-party devices such as
Bently Nevada monitors, or non-GE PLCs is usually obtained through Modbus,
while Ethernet is the preferred communication channel for GE/Fanuc PLC products.
The HMI and other operator interface devices communicate to the Turbine Historian
through the PDH. Network technology provided by the Windows operating system
allows interaction from network computers, including query and view capabilities,
using the Turbine Historian Client Tool Set. The interface options include the ability
to export data into spreadsheet applications.
Plant Data Highway
HMI Server # 1 HMI Server # 2 HMI Viewer Historian

DAT
Tape
Unit Data Highway
Data Transmission to the Historian and HMI
System Capability
The Turbine Historian provides an online historical database for collecting and
storing data from the control system. Packages of 1,000, 5,000, or 10,000 point tags
may be configured and collected from as many as eight turbine controls.
A typical turbine control application uses less than 1,000 points of time-tagged
analog and discrete data per unit. The length of time that the data is stored on disk,
before offline archiving is required, depends upon collection rate, dead-band
configuration, process rate of change, and the disk size.
Data Flow
The Turbine Historian has three main functions: data collection, storage, and
retrieval. Data collection is over the UDH and Modbus. Data is stored in the
Exception database for SOE, events, and alarms, and in the archives for analog
Summarized
values. Retrieval is through a web browser or standard trend screens.

I/O I/O I/O
Control Third Party

System
PLC Devices
Ethernet Ethernet Modbus
Process
Turbine Control
Data Archives
Exception
Dictionary (Analog
Database Values)
(SOE)
Server Side
Client Side
Trend DataLink
Web Browser
Generation
Alarm & Event Report Process Data Excel for

Cross Plot (Trends) Reports &
Event Scanner Analysis
Turbine Historian Functions and Data Flow
Turbine Historian Tools

A selection of tools, screens, and reports are available to ensure that the operator can
make efficient use of the collected data as follows:
• Alarm and Event Report is a tabular display of the alarms, events, and SOE
for all Mark VI units connected to the Turbine Historian. This report presents
the following information on a point’s status; time of pickup (or dropout), unit
name, status, processor drop number, and descriptive text. This is a valuable tool
to aid in the analysis of the system, especially after an upset.
• Historical Cross Plot references the chronological data of two signal points,
plotted one against another, for example temperature against revolutions per
minute (RPM). This function permits visual contrasting and correlation of
operational data.
• Event Scanner function uses logic point information (start, trip, shutdown, or
user-defined) stored in the historical database to search and identify specific
situations in the unit control.
• Event/Trigger Query Results shows the user’s inputs and a tabular display
of resulting event triggers. The data in the Time column represents the time tag
of the specified Event Trigger.
• Process Data (Trends) is the graphical interface for the Turbine Historian
and can trend any analog or digital point. 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. The
Turbine Historian can be set up to mimic strip chart recorders, analyze the
performance of particular parameters over time, or help troubleshoot root causes
of a turbine upset. The trend display, shown in the following figure, is an
example of a turbine startup.
Summarized
Typical Multi-Pen Process Trend Display
Data Collection Details
Mark VI control uses two methods to collect data. The first process uses EGD pages
defined in the system database (SDB). The Turbine Historian uses this collection
method for periodic storage of control data. It also receives exception messages from
the Mark VI controller for alarm and event state changes. When a state change
occurs, it is sent to the Turbine Historian. Contact inputs or SOE changes are
scanned, sent to the Turbine Historian, and stored in the Exception database with the
alarms and event state changes. These points are time-tagged by the Mark VI
controller.
Time synchronization and time coherency are extremely important when the operator
or maintenance technician is trying to analyze and determine the root cause of a
problem. To provide this, the data is time-tagged at the controller that offers system
time-sync functions as an option to ensure that total integrated system data remain
time-coherent.
Data points configured for collection in the archives are sampled once per second
from EGD. Analog data that exceeds an exception dead-band and digital data that
changes state is sent to the archives. The Turbine Historian uses the swinging door
compression method that filters on the slope of the value to determine when to save a
value. This allows the Turbine Historian to keep orders of magnitude and more data
online than in conventional scanned systems.
The web browser interface provides access to the Alarm and Event Report, the
Cross-Plot, the Event Scanner, and several Turbine Historian status displays.
Configurable trend displays are the graphical interface to the history stored in the
archives. They provide historical and real time trending of process data.
®
The PI DataLink (optional) is used to extract data from the archives into
Summarized
spreadsheets, such as Excel for report generation and analysis.

Notes
100 of 1016
CHAPTER 7
Chapter 7 Maintenance and

Diagnostics
Introduction
This chapter discusses board maintenance and component replacement, alarm
handling, and troubleshooting in the Mark VI system. The configuration of process
alarms and events is described, and also the creation and handling of diagnostic
alarms caused by control system equipment failures.
Maintenance
This equipment contains a potential hazard of electric
shock or burn. Only personnel who are adequately trained
and thoroughly familiar with the equipment and the
instructions should install, operate, or maintain this
equipment.
Note For replacement of modules and boards for nuclear applications refer to GEI-
100657, Mark VI Maintenance Procedures for Replacing Circuit Boards on Nuclear
Lineups.
Modules and Boards

Note Return the failed board to GE for repair. Do not attempt to repair it on site.
The Mark VI system should be inspected every 30,000 hours (3.4 years) to ensure
the components are functioning properly. This inspection should include, but not be
limited to, terminal boards, VME boards, and cables. After long service in a very
dirty environment, the terminal boards and VME boards should be cleaned. Remove
the dirt and dust from the boards using a grounded, natural bristle drapery brush. A
grounded, natural bristle paintbrush could also be used. The board can then be
washed in water with a mild dishwashing detergent. Rinse the board in deionized
water. The board should then be rinsed in alcohol to remove any remaining traces of
the water. Allow the board to air dry.
DO NOT use compressed air to clean the boards. The

compressed air may contain moisture that could combine
with dirt and dust and damage the boards. If the
compressed air pressure is too strong, components could
be blown off the boards or delicate solder runs could be
damaged.
Summarized
I of 1016 Chapter 7 Maintenance and Diagnostics • 7-1
DO NOT use solvent-based cleaners to terminal boards,
modules or cables. These agents could damage the boards
and the insulation used on the cables.
To clean cables, disconnect them from terminal boards and modules. A damp, lint
free, cotton cloth works best.
Component Replacement
equipment.
Replacing a Controller
¾ To replace and reload the UCVx
1 If a controller has failed, powered down the rack and disconnect all cables from
the controller panel.
2 Loosen the top and bottom screws on the controller board.
3 Use the upper and lower ejector tabs to disengage the controller from the
backplane.
4 Remove the controller and replace it with a spare controller.
5 Use the upper and lower ejector tabs to install the new controller.
6 Tighten the top and bottom screws to secure the controller to the VME rack.
7 Pull the VCMI out of the rack so far enough to disconnect it from backplane.
8 Connect the serial loader cable between the computer and COM1 of the
controller.
a If the controller is a UCVB or UCVD, use the serial loader to download the
flash file system to the controller
b If the controller is a UCVE or later, use the compact flash programmer to
download the flash file system. (The programmer is included in the service
kit)
9 Use the serial loader to configure the controller with its TCP/IP address.
10 Reconnect the Ethernet cable to the controller and power up the rack.
11 Use the toolbox to download runtime to the controller.
12 Use the toolbox to download application code, to permanent storage only, in the
controller.
13 Power down the rack.
14 Re-insert the VCMI into the backplane.
15 Power up the rack.
Summarized
7-2 • Chapter 7 Maintenance and Diagnostics 102 of 1016
Replacing a VCMI
¾ To replace and reload the VCMI
1 If a VCMI or VPRO has failed, the rack should be powered down, and the
IONet connector unplugged from the board front, leaving the network still
running through the T-fitting.
2 Loosen the top and bottom screws on the VCMI or VPRO board.
3 Use the upper and lower ejector tabs to disengage the controller from the
backplane
4 Remove the VCMI and replace it with a spare VCMI.
5 Use the upper and lower ejector tabs to install the new VCMI or VPRO board.
6 Tighten the top and bottom screws to secure the new VCMI or VPRO to the
VME rack.
7 Power up the VME rack.
8 From the toolbox Outline View, under item Mark VI I/O, locate the failed rack.
Locate the VCMI, which is usually under the simplex rack, and right-click the
VCMI.
9 From the shortcut menu, click Download. The topology downloads into the
new board.
10 Cycle power to the rack to establish communication with the controller.
Replacing an I/O Board in an Interface Module

¾ To replace an I/O Board
1 Power down the interface VME rack.

2 Loosen the top and bottom screws on the I/O board.
3 Use the upper and lower ejector tabs to disengage the controller form the
backplane.
4 Replace the board with a spare board of the same type, first checking that the
jumper positions match the slot number (the same as the old board).
5 Use the upper and lower ejector tabs to install the new I/O board.
6 Tighten the top and bottom screws to secure the new I/O board to the VME rack.
8 From the toolbox Outline View, under item Mark VI I/O, locate the failed rack.
Find the slot number of the failed board and right-click the board.
9 From the shortcut menu, click Download. The board configuration downloads.
Note Newer I/O boards do not have Berg jumpers.
Summarized
Replacing a Terminal Board
The terminal boards do not contain software requiring reload, but some have power
supplied to them.

shock or burn. Power is provided by the Mark VI control
cabinet to various input and output devices. External
sources of power may be present in the Mark VI cabinet
that are NOT switched on or of by the control power
circuit breaker(s). Before handling or connecting any
conductors to the equipment, use proper safety
precautions to ensure all power is turned off. To minimize
risk of personal injury, damage to the control equipment,
or damage to the controlled process, it is recommended
that all power to a terminal board be removed before
replacement of the terminal board. Most terminal boards
are supplied from all three power supplies of a TMR
system as well as multiple external sources and therefore
may require shutdown of the turbine before replacement
is made.
¾ To replace a terminal board
1 Disconnect any power cables coming into the terminal board, and unplug all the
I/O cables (J-plugs).
2 Loosen the two screws on the wiring terminal blocks and remove the blocks. Tie
off to the side, if necessary, leaving the field wiring attached.
3 Remove the failed terminal board by removing the mounting screws.
4 Replace it with a spare board, checking that any jumpers are set correctly (the
same as the old board).
5 Securely tighten the terminal board mounting screws.
6 Screw the terminal blocks back in place and plug in the J-plugs and the power
cables.
Summarized
Cable Replacement
The I/O cables are supported in plastic brackets behind the back base and the power
cables (125 V dc) in cable cleats behind the mounting panels. Since these brackets
are not continuous, it is not recommended that the replacement cable be pulled
through behind the back bases. It is recommended the new cables be run across the
top or bottom of the back base and down the side of the I/O wiring trough to the
module power supply.
¾ To replace an I/O cable or power cable
1 Power down the interface module and disconnect the failed cable from the
module. Leave the cable in place. Do not remove the failed cable from the
enclosure.
2 Disconnect the failed cable from the terminal board.
3 Connect the replacement cable to the terminal board, and lay the new cable in
the field-wiring trough at the side of the I/O terminal boards. Use space at the
top and bottom of the cabinet to run the cable across the cabinet to the interface
module.
4 Connect the cable to the interface module and power up the module. Secure the
cable in place with tie wraps.
Note Additional required cables for system expansion are installed in the same
way.
Alarms Overview
Three types of alarms are generated by the Mark VI system, as follows:
Process alarms are caused by machinery and process problems and alert the
operator by means of messages on the HMI screen. The alarms are created in the
controller using alarm bits generated in the I/O boards or in sequencing. The user
configures the desired analog alarm settings in sequencing using the toolbox. As well
as generating operator alarms, the alarm bits in the controller can be used as
interlocks in the application program.
Hold list alarms are similar to process alarms with the additional feature that the
scanner drives a specified signal True whenever any hold list signal is in the alarm
state (hold present). This signal is used to disable automatic turbine startup logic at
various stages in the sequencing. Operators may override a hold list signal so that the
sequencing can proceed even if the hold condition has not cleared.
Diagnostic alarms are caused by Mark VI equipment problems and use settings
factory-programmed in the boards. Diagnostic alarms identify the failed module to
help the service engineer quickly repair the system. For details of the failure, the
operator can request a display on the toolbox screen.
Summarized
Alarm Diagnostic
HMI HMI Toolbox
Display Display
UDH
R Process and S T Diagnostic

Hold List Alarms
Controller Controller Controller
Alarms
Diagnostic
I/O I/O I/O
Alarm Bits
Alarm Types Generated by Mark VI
Process Alarms
Process Alarms are generated by the transition of Boolean signals configured by the
toolbox with the alarm attribute. The signals are driven by sequencing or tied to input
points to map values directly from I/O boards. Process alarm signals are scanned
each frame after the sequencing is run. In TMR systems process signals are voted
and the resulting composite signal is present in each controller.
A useful application for process alarms is the annunciation of system limit-checking.

Limit-checking takes place in the I/O boards at the frame rate, and the resulting
Boolean status information is transferred to the controller and mapped to process
alarm signals.
Two system limits are available for each process input, including thermocouple,
RTD, current, voltage, and pulse rate inputs. System limit 1 can be the high or low
alarm setting, and system limit 2 can be a second high or low alarm setting. These
limits are configured from the toolbox in engineering units.
There are several choices when configuring system limits. Limits can be configured
as enabled or disabled, latched or unlatched, and greater than or less than the preset
value. System out of limits can be reset with the RESET_SYS signal.
Process (and Hold) Alarm Data Flow

Process and Hold alarms are time stamped and stored in a local queue in the
controller. Changes representing alarms are time stamped and sent to the alarm
queue. Reports containing alarm information are assembled and sent over the UDH
to the CIMPLICITY HMIs. Here the alarms are again queued and prepared for
operator display by the alarm viewer.
Operator commands from the HMI, such as alarm Ack, Reset, Lock, and Unlock, are
sent back over the UDH to the alarm queue where they change the status of the
appropriate alarms. An alarm entry is removed from the controller queue when its
state has returned to normal and it has been acknowledged by an operator. Refer to
the following figure.
Hold alarms are managed in the same fashion but are stored on a separate queue.
Additionally, hold alarms cannot be locked but may be overridden.
Summarized Note The operator or the controller can take action based on process alarms.

Mark VI Controller UDH Mark VI HMI
Input Signal 1
. . Alarm
Report
Alarm
Receiver
Alarm
Viewer
Alarm
. . Scanner
. . Alarm
Command
Alarm Queue
Input Signal n Operator Commands
Alarm
Queue - Ack
Alarm Logic including - Reset
variable Time - Lock
- Unlock
Alarm ID - Override for hold lists
Generating Process Alarms
To configure the alarm scanner on the controller, refer to GEH-6403 Control System
Toolbox for Mark VI Controller. To configure the controller to send alarms to all
HMIs, use the UDH broadcast address in the alarm IP address area.
Diagnostic Alarms
The controller and I/O boards all generate diagnostic alarms, including the VCMI,
which generates diagnostics for the power subsystem. Alarm bits are created in the
I/O board by hardware limit-checking. Raw input-checking takes place at the frame
rate, and resulting alarms are queued.
• Each type of I/O board has hardware limit-checking based on preset (non-
configurable) high and low levels set near the ends of the operating range. If this
limit is exceeded, a logic signal is set and various types of input are removed
from the scan.
• In TMR systems, a limit alarm associated with TMR Diff Limt is created if any
of the three inputs differ from the voted value by more than a preset amount.
This limit value is configured by the user and creates a voting alarm indicating a
problem exists with a specific input.
• If any one of the diagnostic alarms is set, it creates a board composite diagnostic
alarm, L3DIAG_xxxx, where xxxx is the board name. This signal can be used to
trigger a process alarm. Each board has three L3DIAG_ signals,
L3DIAG_xxxx1, 2, and 3. Simplex boards use only L3DIAG_xxxx1. TMR
boards use all three with the first assigned to the board in R, the second assigned
to the same board in S, and the third assigned to the same board in T.
• The diagnostic signals can be individually latched, and then reset with the
RESET_DIA signal, typically in the form of a message from the HMI.
• Generally diagnostic alarms require two consecutive occurrences before being
set True (process alarms only require one occurrence).
In addition to inputs, each board has its own diagnostics. The VCMI and I/O boards
have a processor stall timer that generates a signal SYSFAIL. This signal lights the
red LED on the front cabinet. The watchdog timers are set as follows:
• VCMI communication board 150 ms
Summarized
• I/O boards 150 ms

If an I/O board times out, the outputs go to a fail-safe condition which is zero (or
open contacts) and the input data is put in the default condition, which is zero.
The three LEDs at the top of the front cabinet provide status information. The normal
RUN condition is a flashing green and FAIL is a solid red. The third LED is
normally off but shows a steady orange if a diagnostic alarm condition exists in the
board.
The controller has extensive self-diagnostics. These are available directly at the
toolbox. In addition, UCVB and UCVD runtime diagnostics, which may occur
during a program download, are displayed on LEDs on the controller front cabinet.
Each terminal board has its own ID device, which is interrogated by the I/O board.
The board ID is coded into a read-only chip containing the terminal board serial
number, board type, revision number, and the J type connector location.
Voter Disagreement Diagnostics

Each I/O board produces diagnostic alarms when it is configured as TMR and any of
its inputs disagree with the voted value of that input by more than a pre-configured
amount. This feature allows the user to find and fix potential problems that would
otherwise be masked by the redundancy of the control system. The user can view
these diagnostics the same way one views any other diagnostic alarms. The VCMI
triggers these diagnostic alarms when an individual input disagrees with the voted
value for a number of consecutive frames. The diagnostic clears when the
disagreement clears for a preset number of frames.
The user configures voter disagreement diagnostics for each signal. Boolean signals
are all enabled or disabled by setting the DiagVoteEnab signal to enable under the
configuration section for each input. Analog signals are configured using the
TMR_DiffLimit signal under configuration for each point. This difference limit is
defined in one of two ways. It is implemented as a fixed engineering unit value for
certain inputs and as a percent of configured span for other signals. For example, if a
point is configured as a 4-20 mA input scaled as 0-40 engineering unit, its
TMR_DiffLimit is defined as a percent of (40-0). The type of limit checking used is
spelled out in the dialog box for the TMR_DiffLimit signal for each card type. These
signal are summarized in the following table.
Type of TMR Limit-Checking
I/O Processor Type of I/O Delta Method
Board
VAIC % of Configured Span
VGEN Analogs % of Configured Span
PT, CT Engineering Units
VPRO Pulse rates Engineering Units
Thermocouples Engineering Units
Analogs % of Configured Span
PT, CT Engineering Units
VPYR mA % of Configured Span
Gap Engineering Units
VRTD -------- Engineering Units
VSVO Pulse rates Engineering Units
POS Engineering Units
mA % of Configured Span
Summarized
VTCC -------- Engineering Units

VTURH1/H2 Pulse rates Engineering Units
PT Engineering Units
Flame Engineering Units
Shaft monitor Engineering Units
VVIB Vibration signals Engineering Units
For TMR input configuration, refer to GEH-6403 Control System Toolbox for a
Mark VI Controller. All unused signals will have the voter disagreement checking
disabled to prevent nuisance diagnostics.
Totalizers
Totalizers are timers and counters that store critical data such as number of trips,
number of starts, and number of fired hours. The Mark VI control provides a special
block, Totalizer, which maintains up to 64 values in a protected section of non-
volatile RAM (NVRAM).
The Totalizer block should be placed in a protected macro to prevent the logic
driving its counters from being modified. Users with sufficient privilege may set and
clear Totalizer counter values from the toolbox dialogue box. An unprivileged user
cannot modify the data. The standard block library help file provides more details on
using the Totalizer block.
Troubleshooting
To start troubleshooting, be certain the racks have correct power supply voltages;
these can be checked at the test points on the left side on the VME rack.
Refer to Help files as required. From the toolbox, click Help for files on Runtime
Errors and the Block Library. Also, from the Start button, navigate to the Mark VI
controller to see help files on Runtime, I/O networks, Serial Loader, Standard Block
Library, and Turbine Block Library.

equipment.
First level troubleshooting uses the LEDs on the front of the I/O and VCMI boards.
If more information on the board problems and I/O problems is required, use the
toolbox diagnostic alarm display for details.
I/O Board LEDs

Green - Normal Operation
During normal operation, all the Run LEDs on the board front panels flash green. All
boards in all racks should flash green.
Orange - System Diagnostic in Queue
An orange Status LED lit on one board indicates there is an I/O or system diagnostic
Summarized in queue in that board. This is not an I/O board failure, but may be a sensor problem.

¾ To view the diagnostic message
1 From the toolbox Outline View, select Online using the Go on/offline button.
2 Locate the rack in the Summary View and right-click the board. A shortcut
menu displays.
3 From the shortcut menu, select View Diagnostic Alarms. The Diagnostic
Alarms table displays. The following data is displayed in tabular form:
– Time - The time when the diagnostic was generated
– Fault Code - The fault code number
– Status - A 1 indicates an active alarm, and a 0 indicates a cleared, but
not reset (acknowledged), alarm
– Description - A short message describing the diagnostic
This diagnostic screen is a snapshot, but not real time. For new data, select the
Update command.
To display all of the real time I/O values in the Summary View, left-click the board
on the screen. The I/O values will display. All the real time I/O values display in the
Summary View. At the top of the list is the L3DIAG board alarm, followed by the
board point system limit values, and with the I/O (sensor) values at the bottom. From
these alarms and I/O values, determine whether the problem is in the terminal board
or in the sensor.
For example, if all the I/O points in a board are bad, the board has failed, a cable is
loose, or the board has not been configured. If only a few I/O points are bad, the I/O
values are bad, or part of the terminal board is burned up.
Red - Board Not Operating
If a board has a red Fail LED lit, it indicates the board is not operating. Check if it is
loose in its slot. If so, switch off the rack power supply, push the board in, using the
top and bottom injector/ejector tabs. Check to see if the top and bottom mounting
screws are loose and tighten, if necessary. Turn the power on again.
If the red light still comes on, power down the rack, remove the board and check the
firmware flash memory chip. If the board has a socketed flash memory chip, this
chip can be plugged in the wrong way, which damages it. The following figure
shows a typical I/O board with the chip location. The chamfer on the chip should line
up with the chamfer on the receptacle, as shown. If no flash chip is installed, replace
the board with a new one. Newer boards have a soldered flash chip so no adjustment
is possible.
Summarized
I/O Board
I/O Board Generic

Circuitry
Flash
Memory
Flash
Chip
Memory
Socket
I/O Board Specific

Circuitry
I/O Board with Flash Memory Chip
Earlier I/O board versions had a reset button on the front. If your board has this,
check to see if this button is stuck in. If so replace the board with a new one.
It is possible the failure is in the rack slot and not in the board. This can be
determined by board swapping, assuming the turbine is shut down. Remove the same
good board from the same slot in an adjacent TMR rack, and move the bad board to
this good slot. Be sure to power down the racks each time. If the problem follows the
board, replace the board. If it does not, there may be a problem with the VME
backplane. Inspect the board slot for damage; if no damage is visible, the original
board may not have been seated properly. Check the board for proper seating.
If a whole rack of I/O boards show red LEDs, it is probably caused by a

communication failure between the slave VCMI and the I/O boards in the rack. This
can result from a controller or VCMI failure or an IONet cable break. The failure
could also be caused by a rack power supply problem. Either the master or slave
VCMI could be at fault, so check the Fail LEDs to see where the problem is.
If several but not all I/O boards in a rack show red, this is probably caused by a rack
power supply problem.
Controller Failures
If the controller fails, check the VCMI and controller diagnostic queues for failure
information. Power down the controller rack and reboot by bringing power back (do
not use the Reset button). If the controller stays failed after reboot, replace it with a
spare.
If a controller fails to start, this usually indicates a runtime error that is typically a
boot-up or download problem. The runtime error number is usually displayed after
an attempted online download. The controller Runtime Errors Help screen on the
toolbox displays all the runtime errors together with suggested actions.
Summarized
If the controller or its VCMI fails, then the IONet on this channel stops sending or
receiving data. This drives the outputs on the failed channel to their fail-safe state.
The failure does not affect the other two IONet channels, which keep running.
Power Distribution Module Failure

The PDM is a very reliable module with no active components. However, it does
contain fuses and circuit switches, and may have an occasional cabling or connector
problem. Most of the outputs have lights indicating voltage across their supply
circuit. Open the PDM front door to see the lights, switches, and fuses.
PDM diagnostic information is collected by the VCMI, including the 125 V dc bus
voltage and the status of the fuses feeding relay output boards. These can be viewed
on the toolbox by right-clicking the VCMI board, and then selecting View
Diagnostic Alarms.
Online Download
The Mark VI control system is designed to perform some types of control
configuration downloads to an operating system, referred to as online downloads,
which are made to a control while it is actually controlling the system. Online
downloads are made without restarting control processors or board racks. Because
downloads to an operating system can cause process actions that may take the system
to a state that the control considers a trip condition, these downloads should only be
made after the current state of the system has been carefully reviewed for process
changes that could occur during the download.
Since these downloads could reveal a condition that compromises the TMR ability of
the control, it is recommended that they be made only to systems that are proven to
be TMR-capable by successfully passing a TMR test. Refer to the section, TMR Test
Procedure.
Note It is recommended that you read this entire section prior to planning an online
download.
Preliminary Checks for Online Download

¾ Perform the following preliminary checks before starting the online
download
1 Ensure all the turbine auxiliaries are in appropriate control states.

2 Secure systems as necessary and review control logic for auxiliary systems
carefully before initiating a download, as process disturbances can occur during
the process.
3 Select an operationally robust system operating point and allow sufficient time
for the system to reach a stable operating condition before starting the download.
If the download could change the system performance, select a system state that
will be minimally affected by the change.
4 Check every controller, VCMI, and VPRO for active diagnostic alarms. Active
diagnostic alarms may indicate that the TMR capability of the control is
compromised, and can increase the chances the system could trip. Clear all
active alarms.
Summarized
5 If, however, the download is made with active diagnostic alarm conditions,
record and examine each diagnostic alarm for potential failure modes when the
controllers are activated with the new code. The root cause of each process
alarm must be understood to know if the download process occurred correctly.
6 The new code or constants must be compatible with keeping the turbine running,
such as with TMR and the application. Instances where simplex trips were added
through new code have occurred, and the installation of this code resulted in
trips. Other instances have introduced changes in operating states that could not
be reached without first encountering a trip condition, such as valve out-of-
position.
7 Check site records for past successful TMR checks on the system. These TMR
checks should be performed after each code installation to verify that the
application code still maintains TMR capability.
Control State
From the Control System Toolbox (toolbox) open the system's configuration file
(m6b). Connect to the control, and verify that the file is equal and online
(controlling). For all racks in a TMR system, check that the UCVx (controller) I/O
state = 6A hex (106 decimal) and that the control state is CA hex as follows:
This indicates that the R controller is the designated Double-click on the

processor. The designated processor letter will always control box to display
display with a green background on the Status bar. the Controller State
Selecting any other processor will display a letter with dialog
a yellow background. This example illustrates a
controller that is equal and in-control.
Summarized
For older systems that lack the feature to display this data from the toolbox, this
information is found by using telnet to connect directly to the controllers in turn by
their IP address, and using the monitor ma command to verify the IOC = CA and
STATE = 6A:
# monitor ma
ID = <R> IOC = CA SRTP_OK = 0 UDH COMM = 1 STATE = 6A CLK = EXT

TMR DC = <R>
Note Online downloads can be used to resolve minor revision differences, such as
those that occur in tuning. To resolve a major revision, you must restart the
controller after a download to permanent storage. A file that is equal, but will not go
online (into the control state), can only be resolved by restarting the controller.
Before the online download is performed, all control constants that are not the same
in the currently running control as in the configuration (.m6b) file must be identified
and confirmed since when the download is performed, all constants changes that
were made to the configuration file are initiated into the control.
For TMR systems, resolve all the issues related to TMR operation and make sure all
the controllers are online before performing the download. View the diagnostic
alarms and make sure no mismatch diagnostic alarms are present. Inconsistent
diagnostic alarms can indicate hardware or application software issues that could
compromise TMR operation. Use the following procedures to view, record, and
compare values. Resolve all issues before proceeding with the download.
¾ To review and record control constants
1 While online to the controller, from the toolbox, select the File menu and
Open. Select the master configuration file (.m6b).
2 From the View menu, select Control Constants. The Control Constant
List View displays. Review and record any constants that are different
(disregard differences in any library modules).
3 Select the File menu and Export to .csv to produce a record of the constants.
Each difference must be recorded and understood before the download.
Differences may reflect things such as experimental changes to operating
conditions.
¾ To view and record the logic forcing
From the toolbox, select View menu and Force Lists. The Forced Lists window
displays. Forced signals must be recorded and understood before the download.
Summarized
Record the decision and value for each to be used after the download.

¾ To compare the configuration
From the toolbox, under Hardware and I/O Definitions, right-click Mark VI I/O and
select Compare Configuration. Solve any differences before proceeding, since
they represent changes made to boards that were not saved in the configuration file.
If necessary to record the differences produce and print a differences report.
Make any necessary corrections to the configuration file.
¾ To check for active diagnostic alarms on Mark VI I/O boards
From the toolbox, expand the items Hardware and I/O Definitions and Mark VI I/O.
Right-click each board and select View Diagnostic Alarms, and record any active
diagnostic alarms.
It may be necessary to first clear inactive diagnostic alarms to reach the state where
the diagnostic board point is zero. Resolve or understand all active diagnostic alarms
before proceeding with the download.
Note A yellow LED on an I/O board or a VCMI board indicates that a

diagnostic alarm (not necessarily active) is present. However, the lack of an
LED may simply indicate a failed LED.
Download Checklist
Unit ML Number Unit ML Number Unit ML Number
Item Name Item Status for Unit Item Status for Unit Item Status for Unit
Pre-Update
Checklist
1 Code Suitability
2 Diagnostics
3 Previous TMR Checks
4.1 MkVI
Control State
Control Constants
Alarm Drops
Logic Forcing
I/O Configuration
Active Diagnostics
TMR Mismatch Diagnostics
Download
Checklist
5 Mark VI Validate/Build/Download
Downloads Application, Symbols,
Compressed .m6b
5.1 Application Save .m6b
Summarized
TMR Test Procedure
The following procedure should be used to test the TMR capability of the turbine
control system. This test places the system in a simplex mode while the controller
restarts, which increases the possibility for the system to trip.
¾ To prepare the system for TMR testing
Note Prior to conducting any type of TMR test, overall system design,
including especially all simplex I/O and simplex outputs to external control
systems, must be reviewed to make sure that the fundamental system design is
TMR-capable. This review must include a thorough examination of all simplex
control sequencing code and I/O.
1 Review all standing and intermittent process alarms on the turbine control panel.
Resolve all alarms related to TMR devices and critical control functions. If any
alarms remain uncleared, make a print out to document the status of the alarm
queue prior to the test.
2 Review all I/O board standing and intermittent diagnostic alarms on the turbine
control panel. Resolve all alarms related to TMR devices and critical control
functions.
3 Ensure that the trip logs are properly configured and obtaining the proper data.
4 Create a high resolution data trend that includes the following:
TMR analog transducers
Each speed pickup
LVDT inputs
Exhaust thermocouple values
Gas valve position commands
IBH valve position commands
Liquid fuel bypass valve commands (if applicable)
IGV position commands
servo current signals
Digital status and trip signals
¾ To test the R, S, and T controllers
Note The designated controller should be tested last, since it will be the
controller that is supplying data for the Trend Recorder. If the designated
controller is R, then the testing order should be T, S, R. Or, if S is the
designated controller, then test R, T, and the S controller last. This
procedure assumes R is the designated controller.
1 With the unit at steady-state and either Full Speed No Load or Spinning Reserve
(or other appropriate operating point as determined by the operations), from the
toolbox View menu select Trend Recorder and begin recording the
designated controller. The requirement is to always record data from a controller
that is not going to be shutdown.
Note The user when connecting online determines the controller that the Trend
Recorder collects data from.
2 Power down the T controller and make sure the system maintains its current
Summarized
operational state.

Note If there is a TMR issue a shutdown may be issued.
3 Power up the T controller, and using the toolbox monitor T until it returns to the
controlling state (IO State = 0x6A, Control State 0xCA). Wait at least five
minutes for the unit to stabilize before continuing.
4 Stop the Trend Recorder and save the trend file using an appropriate file name
including date, time, and ID of the controller that was powered down. Record the
file name.
5 Start a new trend file on the R controller (designated).
6 Power down the S controller, and make sure the system maintains its current
operational state.
1 Power up the S controller, and using the toolbox monitor S until it returns to the
2 Stop the Trend Recorder and save the trend file. Record the file name.
3 Start a new trend file on the S controller, since it will become the designated
controller when the R controller is powered down.
4 Power down the R controller and make sure the system maintains its current
operational state.
5 Power up the R controller, and using the toolbox, monitor R until it returns to the
6 Stop the Trend Recorder and save the trend file. Record the file name.
¾ To test the turbine protection module (VPRO)
1 Determine the control state of the protection module. The three protection
modules are identified using either of two names - X, Y, and Z, or
synonymously VPROR, VPROS, and VPROT respectively. Use the toolbox to
view the health of the appropriate L3DIAG_VPROx to determine when the
VPRO has come back to controlling state after it is powered up.
In this example, the X VPRO has not reached it's control state as evidenced by
the unhealthy L3DIAG_VPROR signal while both Y and Z are in their control
state.
Summarized
2 Start a new trend file using the designated controller.
3 Power down the X VPRO, observe that the unit continues to operate, even
though L3DIAG_VPROR is unhealthy. Note if there is a TMR issue a shutdown
may also be issued.
4 Power up the X VPRO. Using the health of L3DIAG_VPROR, monitor the X
controller until it returns to the controlling state: Once this occurs, wait an
additional five minutes before continuing.
5 Stop the trend file and save it. Start a new trend file.
6 Power down the Y VPRO and observe that the unit continues to operate, even
though L3DIAG_VPROS is unhealthy. Note if there is a TMR issue a shutdown
may also be issued.
7 Power up the Y VPRO. Using the health of L3DIAG_VPROS, monitor the Y
VPRO until it returns to the controlling state. Once this occurs, wait an
8 Stop the trend file and save it. Start a new trend file.
9 Power down the Z VPRO, observe that the unit continues to operate, even
though L3DIAG_VPROT is unhealthy. Note if there is a TMR issue a shutdown
may also be issued.
10 Power up the Z VPRO. Using the health of L3DIAG_VPROT, monitor the Z
controller until it returns to the controlling state. Once this occurs, wait an
11 Stop the trend file and save it.
Summarized
In Case of Trip
If a trip occurs when a control is powered down in this test, BEFORE the control is
restarted save the trip log, the individual controller capture blocks, the alarm, and the
event files (.D03). The data in the individual controller capture blocks will be lost
when the controller is re-started. The capture block data from the two controllers that
were powered at the time of the trip must be uploaded and saved as trend files. Using
the Trend Recorder, go online with both controllers, one at time, upload the block
collected data and save it.
The trip log is usually stored in the local HMI directory,

E:\Historian_Data\Gn_TripLog. Each trip is stored in an individual file in a date-
stamped subdirectory. From toolbox, open the appropriate trip log (.dca file) to
verify the correct trip event.
On a standard customer HMI, there is a shortcut icon for Internet Explorer on the
desktop labeled Alarm And Event Logger, which opens the TCI Homepage for the
HMI. Select the Alarm and Event Report link and fill in the appropriate request for
all of the alarm and event information surrounding the trip. Save this report to a file.
Review the trip log and events to determine the cause of the trip. The combination of
two alarms may indicate the root cause. For example, LVDT mismatch or loss of
LVDT combined with the power down of a controller may cause a gas control valve
not following trip and alarm. This type of root cause should be resolved on site by
fixing the faulty TMR device and documenting the root cause and resolution as part
of the trip report.
Another potential root cause could be I/O used in control code as critical inputs has
been terminated in the control as simplex points. If this is uncovered a PAC case
should be written and sent to the controls requisition engineer. Attachments for this
PAC case should be the current .m6b file and the four sets of files - trend files, trip
log, event file, and the diagnostic alarm file.
If the trip RCA indicates that the trip was caused by a controller fault, capture all
diagnostic alarms from each VCMI and the I/O boards into a file. Contact your GE
support representative and provide the four sets of files - trend files, trip log, alarm
and event files, and the diagnostic alarm file. The report should describe at what
point in the TMR testing the trip occurred and include a description of the specific
sequence of events leading to the trip.
Summarized
Notes
120 of 1016
CHAPTER 8
Chapter 8 Applications
Introduction
This chapter describes some of the applications of the Mark VI hardware and
software, including the servo regulators, overspeed protection logic, generator
synchronization, and ground fault detection.
Generator Synchronization
This section describes the Mark VI Generator Synchronization system. This system
is suitable for synchronizing generator breakers where the control can adjust
speed/frequency. It is not designed for transmission line breaker synchronizing
where there may be fixed phase relationships. Its purpose is to momentarily energize
the breaker close coil, at the optimum time and with the correct amount of time
anticipation, so as to close the breaker contact at top center on the synchroscope. Top
center is often known as top dead center. Closure will be within one degree of top
center. It is a requirement that a normally closed breaker auxiliary contact be used to
interrupt the closing coil current.
5760-0969-E399-21EC
The synchronizing system consists of three basic functions, each with an output
relay, with all three relays connected in series. All three functions have to be true
(relay picked up) simultaneously before the system applies power to the breaker
close coil. Normally there will be additional external permissive contacts in series
with the Mark VI system, but it is required that they be permissive only, and that the
precise timing of the breaker closure be controlled by the Mark VI system. The three
functions are:
• Relay K25P, a synchronize permissive; turbine sequence status

• Relay K25A, a synchronize check; checks that the slip and phase are within a
window (rectangle shape); this window is configurable
• Relay K25, an auto synchronize; optimizes for top dead center
The K25A relay should close before the K25 so that the synchronous check function
will interfere with the auto synchronous optimizing. If this sequence is not executed,
a diagnostic alarm will be posted, a lockout signal will be set true in signal space,
and the application code may prevent any further attempts to synchronize until a
reset is issued and the correct coordination is set up.
Hardware
The synchronizing system interfaces to the breaker close coil through the TTUR
terminal board as in the following figure. Three Mark VI relays must be picked up,
plus external permissive contacts must be true, before a breaker can close.
The K25P relay is directly driven from the controller application code. In a TMR
system, it is driven from R, S, and T controllers, using 2/3 logic voting. In a simplex
Summarized
system, it may be configured, by jumper, to be driven from the R controller only.

I of 1016 Chapter 8 Applications • 8-1
5 Force the following signals to the TRUE state:
– VTUR, Sync_Perm, then K25P should pick up
– VTUR, Sync_Perm_AS, then K25 should pulse when the voltages are in
phase
– VPRO, SynCK_Perm, then K25A should pulse when the voltages are in
phase
6 Verify that the TTUR breaker close interface circuit, screws 3 to 7, is being made
(contacts closed) when the voltages are in phase.
7 Run a trend chart on the following signals:
VPRO: GenFreqDiff, GenPhaseDiff, L25A_Command, K25A_Fdbk
VTUR: GenFreqDiff, GenPhaseDiff, L25_Command, CB_K25_PU,
CB_K25A_PU
8 Use an oscilloscope, voltmeter, synchroscope, or a light to verify that the relays
are pulsing at approximately the correct time.
9 Examine the trend chart and verify that the correlation between the phase and the
close commands is correct.
10 Increase the slip frequency to 0.5 Hz and verify that K25 and K25A stop pulsing
and are open.
11 Return the slip frequency to 0.1 to 0.2 Hz, and verify that K25 and K25A are
pulsing. Reduce the generator voltage to 40 V ac and verify that K25 and K25A
stop pulsing and are open.
Overspeed Protection Logic

The figures in this section define the protection algorithms coded in the VPRO
firmware. VTUR contains similar algorithms. A configurable parameter from the
toolbox is illustrated with the abbreviation CFG(xx), where xx indicates the
configuration location. Some parameters/variables are followed with an SS
indicating they are outputs from Signal Space (meaning they are driven from the
CSDBase); other variables are followed with IO indicating that they are hardware I/O
points.
Summarized
OnlineOS1Tst, SS OnLineOS1
Online
OverSpeed Test
OnlineOS1X, SS
OnlineOS1X, SS
A
L97EOST_ONLZ
TDPU
1.5 sec
B
OnlineOS1x, SS L97EOST_ONLZ L97EOST_RE

Reset
pulse
L86MR, SS L86MRX
L97EOST_RE
OnLineOS1X, SS
L97EOST_ONLZ
1.5 sec
L97EOST_RE, Reset Pulse
VPRO Protection Logic - Online Overspeed Test
Summarized
8-12 • Chapter 8 Applications 123 of 1016
OS1_Setpoint , SS
RPM A |A|
A
A-B A OS1_SP_CfgEr
OS_Setpoint, CFG A>B
B 1 RPM System Alarm, if the two
RPM B
(J5, PulseRate1) setpoint don't agree!!
MIN
OS_Stpt_PR1 OS_Setpoint_PR1
A A
zero
MULT A A+B
0.04
B MIN B
OS_Tst_Delta, CFG x
B
(J5, PulseRate1) RPM
OfflineOS1tst, SS
OnlineOS1
PulseRate1, IO
A
OS1
A>=B
OS_Setpoint_PR1
B
OS1_Trip
OS1
Overspeed
Trip
OS1_Trip L86MR, SS
Frame Rate
PulseRate1, IO
A -0 A
|A-B| A
Z
Speed1_Diff
Speed1, SS B A>B
-1 B (A & B & C)
OS_Diff, CFG (RPM)
Z
B
-2
C
Z
SpeedDifEn, Card CFG
Speed1_Diff SpeedDifTrip
Enable
Speed
Difference Trip
SpeedDifTrip L86MR, SS
Speed1_Diff
TDPU
60 Sec
VPRO Protection Logic - Overspeed Trip, HP
Summarized
PR_Zero Hyst
1
0
0 RPM
CFG
PulseRate1, IO
A
PR1_Zero
AB
Min_Speed, CFG (J5,
PulseRate1)
B
(Pulse Rates in Hz)

A
A>B
75 Hz AND
B
PR1_Accel
S
(Der) A
AB
Acc_Setpoint, CFG (J5,PulseRate1)

B
Dec1_Trip
PR1_DEC
Dec1_Trip L86MR,SS
Acc_Trip, CFG (J5, PulseRate1)
Acc1_Trip
PR1_ACC PR1_MIN Enable
Acc1_TrEnab
Acc1_Trip L86MR,SS
*Note: Where 100% is define as the OS Setpoint
VPRO Protection Logic - Overspeed Trip, HP (continued)
Summarized
OS1_SP_CfgEr PR1_Zero L5CFG1_Trip
HP
Config Trip
L5CFG1_Trip L86MR,SS
PR1_Max_Rst
PR_Max_Rst
PR1_Zero_Old PR1_Zero
PR1_Zero
0.00
PR1_Max_Rst PR1_Max
Max
PulseRate1
PR1_Zero PR1_Zero_Old
VPRO Protection Logic - Overspeed Trip, HP (continued)
Summarized
OS2_Setpoint , SS
A |A|
RPM A
A-B A OS2_SP_CfgEr
(J5, PulseRate2) RPM B
setpoints don't agree
A
Min
B
OS_Setpoint_PR2
OS_Stpt_PR2
A A
zero
0.04 Mult A A+B
B Min B
OS_Tst_Delta
B
CFG(J5, PulseRate2) RPM
OfflineOS2test, SS
OnlineOS2test, SS
PulseRate2, IO
A
OS2
A>=B
OS_Setpoint_PR2
B
OS2_Trip
OS2
Overspeed
Trip
OS2_Trip L86MR,SS
VPRO Protection Logic - Overspeed LP
Summarized
PulseRate2, IO
A
PR2_Zero
AB
Min_Speed, CFG (J5,
PulseRate2)
B
(Pulse Rates in Hz)

A
PR2_Dec
A>B
75 Hz AND
B
PR2_Accel
S
(Der) A
AB

B
Dec2_Trip
PR2_DEC
Dec2_Trip L86MR,SS
Acc2_Trip
Acc2_TrEnab
Acc2_Trip L86MR,SS
VPRO Protection Logic - Overspeed LP (continued)
Summarized
L5CFG2_Trip
OS2_SP_CfgEr PR2_Zero LP
Config Trip
PR_Max_Rst PR2_Max_Rst
PR2_Zero
0.00
PR2_Max_Rst Max PR2_Max
PulseRate2
PR1_MIN PR2_Zero LockRotorByp LPShaftLocked
LPShaftLocked L86MR, SS
VPRO Protection Logic - Overspeed LP (continued)
Summarized
OS3_Setpoint , SS
A
RPM |A| A
A-B A OS3_SP_CfgEr
(J5, PulseRate3) RPM B
setpoints don't agree
A
Min
B
OS_Stpt_PR3
OS_Setpoint_PR3
A A
zero
0.04 Mult A A+B
B Min B
OS_Tst_Delta
B
CFG(J5, PulseRate3) RPM
OfflineOS3tst, SS
OnlineOS3tst, SS
PulseRate3, IO
A
OS3
A>=B
OS_Setpoint_PR3
B
OS3_Trip
OS3
Overspeed
Trip
OS3_Trip L86MRX
VPRO Protection Logic - Overspeed IP
Summarized
PulseRate3, IO
A
PR3_Zero
AB
Min_Speed, CFG (J5, PulseRate3)
B
(Pulse Rates in Hz)

A
PR3_Dec
A>B
75 Hz AND
B
PR3_Accel
S
(Der) A
AB

B
Dec3_Trip
PR3_DEC
Dec3_Trip L86MR,SS
Acc3_Trip
Acc3_TrEnab
Acc3_Trip L86MR,SS
Summarized
VPRO Protection Logic - Overspeed IP (continued)

OS3_SP_CfgEr PR3_Zero L5CFG3_Trip
IP
Config Trip
PR_Max_Rst PR3_Max_Rst
PR3_Zero
0.00
PR3_Max_Rst PR3_Max
Max
PulseRate3
VPRO Protection Logic - Overspeed IP (continued)
Summarized
Notes:
,CFG == VPRO config data
,SS == from signal space
(SS) == to signal space
TC1 (SS)
TC2 (SS) TC_MED(SS)

MED
TC3 (SS)
Zero
OTSPBias(SS)
MAX
OTBias,SS
L3SS_Comm
OTBias_RampP,CFG
OTBias_RampN,CFG
MED A
OTBias_Dflt,CFG A+B
A
B
A-B
B
-1
Z
TC_MED
A
Overtemp_Trip,CFG L26T
A A>=B
A-B B
OTSPBias
B OTSetpoint(SS)
OT_Trip_Enable,CFG
OT_Trip (SS)
L26T
OT_Trip L86MR,S
S
VPRO Protection Logic - Over-Temperature
Summarized
RPM_94%
RatedRPM_TA, RPM_103.5%
Calc Trip
CFG (VPRO, Config)
Anticipate RPM_106%
Speed RPM_116%
references RPM_1%
RPM_116%
A TA_StptLoss,SS
OS1_TATrpSp,SS RPM A<B Alarm
B OR L30TA
A
A<B
RPM_103.5% B
TA_Spd_SP
RPM_106%
RPM_1%/sec
Rate
TA_Spd_SP TA_Spd_SPX, RPM
Ramp A
Trp_Anticptr
RPM_94% Reset A<B
(Out=In)
B
TrpAntcptTst Hyst
RPM_1%
PulseRate1, IO, RPM
TA_Trip,SS Trip Anticipator

SteamTurbOnly Trp_Anticptr Trip
L12TA_TP
VPRO Protection Logic - Trip Anticipation
Summarized
PR1_Zero, SS
Speed1, SS
A A == 100; Stale_Speed = 1
A == 1; CNTR = CNTR + 1 CNTR Stale_Speed
A == B A A
-1 A == 0; CNTR = 0 A == 0; Stale_Speed = 0
Z B
Ratchet Counter Ratchet Toggle
Frame Rate
StaleSpdEn, Card CFG
Enable StaleSpdTrip
Stale_Speed
StaleSpdTrip L86MR, SS
Stale_Speed
TDPU
60 Sec
Stale Speed Trip
ContWdog, SS
A
A == 1; CNTR = CNTR + 1 5 CNTR = 5; Heart_Beat_Loss = 0
CNTR Heart_Beat_Loss
A != B A
-1 A == 0; CNTR = CNTR - 1 0 CNTR = 0; Heart_Beat_Loss = 1
Z B
Up - Down Counter Saturation Limit
Toggle
Frame Rate
ContWdogEn, Card CFG
Enable ContWdogTrip
Heart_Beat_Loss
ContWdogTrip L86MR, SS
Heart_Beat_Loss
TDPU
60 Sec
Control Watchdog Trip
Summarized
L5Cont_Trip
L5Cont1_Trip
Contact
Trip
L5Cont2_Trip
L5Cont3_Trip
L5Cont4_Trip
L5Cont5_Trip
L5Cont6_Trip
L5Cont7_Trip
Turbine_Type, CFG (VPRO Crd_Cfg)

SteamTurb Only Configured
LargeSteam Steam Turbine
only, not
MediumSteam including Stag
SmallSteam
OS1_Trip
SpeedDifTrip
StaleSpdTrip
ComposTrip1A
Dec1_Trip
Composite
L5CFG1_Trip Trip 1A
L5Cont_Trip
Acc1_Trip
Cross_Trip, SS
ContWdogTrip
OT_Trip SteamTurbOnly
LM_2Shaft LM_3Shaft HPZeroSpdByp,SS PR1__Zero
L3Z
LMTripZEnabl,
CFG(VPRO)
VPRO Protection Logic - Trip Logic
Summarized
OS1_Trip ComposTrip1A
SpeedDifTrip
StaleSpdTrip
Dec1_Trip
L5CFG1_Trip
L5Cont_Trip
Acc1_Trip
Cross_Trip, SS
ContWdogTrip
OT_Trip SteamTurbOnly
HPZeroSpdByp,
LM_2Shaft LM_3Shaft SS PR1__Zero
L3Z
LMTripZEnabl,CFG(VPRO)
Summarized
OS2_Trip GT_2Shaft ComposTrip1B Composite
Trip 1B
Dec2_Trip
LM_2Shaft
L5CFG2_Trip
LM_3Shaft
Acc2_Trip
LPShaftLocked
OS3_Trip LM_3Shaft
Dec3_Trip
L5CFG3_Trip
Acc3_Trip
ComposTrip1 Composite
ComposTrip1A
Trip 1
ComposTrip1B
Turbine_Type, CFG (VPRO)

ComposTrip2
ComposTrip1 Stag_GT_1Sh Composite
Trip 2
Stag_GT_1Sh
OS1_Trip
Dec1_Trip
L5CFG1_Trip
L5Cont_Trip
Acc1_Trip
Cross_Trip, SS
VPRO Protection Logic - Trip Logic (continued)
Summarized
RelayOutput, CFG( J3,K1_Fdbk)
used ETR1
TA_Trip TestETR1 ComposTrip1 L5ESTOP1 Trip Relay,
ETR1_Enab
x x Energize
to Run
TRES,TREL*
KE1*
ETR1 SOL1_Vfdbk KE1_Enab Economizing
TDPU Relay,
used Energize to
TA_Trp_Enabl1 Econ,
CFG(VPRO_CRD,CFG) KE1, J3
RelayOutput, CFG( J3,KE1_Vfdbk)
2 sec
used
L5ESTOP1 ETR2
TA_Trip TestETR2 ComposTrip1 Trip Relay,
ETR2_Enab Energize
x x
to Run
TRES,TREL*
KE2*
TDPU Relay,
Energize to
used
TA_Trp_Enabl2 Econ,
RelayOutput, CFG(J3,KE2_Vfdbk)
2 sec

L97EOST_ONLZ Large Steam
used
ETR3
TA_Trip ComposTrip1 TestETR3 ETR3_Enab L5ESTOP1 Trip Relay,
x x Energize
to Run
TRES,TREL*
KE3* Economizing
ETR3 SOL3_Vfdbk KE3_Enab
TDPU Relay,
Energize to
used Econ,
TA_Trp_Enabl3
2 sec Note: * Functions, L5ESTOP1 & KEx

are not included in the TRES, TREL
TB applications. They are included
only in the TREG applications.
VPRO Protection Logic - ETR 1, 2, and 3
Summarized
used ETR4
TA_Trip TestETR4 ComposTrip1 L5ESTOP2 Trip Relay,
ETR4_Enab
x x Energize
to Run
TRES,TREL*
KE4*
TDPU Relay,
used Energize to
TA_Trp_Enabl4 Econ,
RelayOutput, CFG( J4,KE4_Vfdbk)
2 sec
used ETR5
ComposTrip1 L5ESTOP2 Trip Relay,
ETR5_Enab Energize
x x
to Run
TRES,TREL*
KE5*
TDPU Relay,
Energize to
used
Econ,
KE2, J4
2 sec
used
ComposTrip2 ETR6
ETR6_Enab L5ESTOP2 Trip Relay,
x x Energize
to Run
TRES,TREL*
KE6* Economizing
ETR6 SOL6_Vfdbk KE6_Enab
TDPU Relay,
Energize to
used Econ,
KE3, J4
2 sec Note: * Functions, L5ESTOP2 and

are not included in the TRES, TREL
TB applications. They are included
only in the TREG applications.
VPRO Protection Logic - ETR 4, 5, and 6
Summarized
CFG(J3, K25K_Fdbk)
SynchCheck(Used, Unused)
VoltageDiff
SystemFreq(50,60)
TurbRPM
ReferFreq
FreqDiff
PhaseDiff
GenVoltage
BusVoltage
SynCk_Perm, SS GenFreq, SS
Synch Check Function
SynCk_ByPass, SS BusFreq, SS
GenVolts, SS
Slip
BusVolts, SS
GenFreqDiff, SS
DriveFreq Phase GenPhaseDiff, SS
GenVoltsDiff, SS
GenPT_KVolts, IO Synch
Window
BusPT_KVolts, IO L25A_Cmd, IO
K4CL
ComposTrip1 K4CL_Enab OnlineOS1Tst Servo Clamp
Relay, Energize
Used to Clamp, K4CL
RelayOutput,
CFG (J3,K4CL_Fdbk)
K25A
L25A_Cmd K25A_Enab Synch Check Relay
Energize to Close
Used Breaker, K25A
on TTUR via TREG
SynchCheck,
CFG (J3,K25A_Fdbk)
VPRO Protection Logic - Servo Clamp
Summarized
Inputs Inputs
TPRO, J5 TPRO, J6 GenPT_KVolts
PulseRate1 Gen Volts
Speeds, PR BusPT_KVolts
PulseRate2 Bus Volts
TC1*
PulseRate3 Thermocouples
TC2*
TREG, J3 KESTOP1_Fdbk TC3*
ESTOP1
Contact1 ColdJunction
Trip Interlocks
Contact2 Analog AnalogIn1
Inputs
Contact3 AnalogIn2
Contact4 AnalogIn3
Contact5
Contact6
Contact7
Outputs:
Sol1_Vfdbk
Voltage to TREG, J3
solenoid, Sol2_Vfdbk ETR1
feedback Relays KX1, KY1, KZ1
Sol3_Vfdbk ETR2
Relays KX2, KY2, KZ2
K1_Fdbk* ETR3
Trip Relay Relays KX3, KY3, KZ3
feedback K2_Fdbk* KE1
Relay KE1
K3_Fdbk* KE2
Relay KE2
KE1_Fdbk KE3
Econ Relay Relay KE3
feedback KE2_Fdbk K4CL
Relay K4CL
KE3_Fdbk K25A
Relay K25A
Clamp Relay K4CL_Fdbk
feedback TREG, J4
K25A_Fdbk ETR4
Synch Check Relays KX1, KY1, KZ1
Relay feedback ETR5
TREG, J4 ETR6
KESTOP2_Fdbk KE4
ESTOP2 Relay KE4
Sol4_Vfdbk KE5
Relay KE5
Voltage to KE6
solenoid, Sol5_Vfdbk Relay KE6
feedback Sol6_Vfdbk
K4_Fdbk*
Trip Relay
feedback K5_Fdbk
K6_Fdbk
*Note: Each signal appears three
KE4_Fdbk times in the CSDB; declared Simplex.
Econ Relay
feedback KE5_Fdbk
KE6_Fdbk
VPRO Protection Logic - Hardware I/O Definition
Summarized
Signal Space
Inputs TPRO,J5
Signal Space
PulseRate1
Speeds, RPM
PulseRate2 Inputs
PulseRate3
Outputs:
PR1_Zero
SynCk_Perm
PR2_Zero Zero Synch
Speed SynCk_ByPass
TREG, J3 PR3_Zero Check
KESTOP1_Fdbk
ESTOP1
Cross_Trip
Contact1
Contacts
Contact2 OS1_SP_CfgErr Overspeed OnLineOS1Tst
Contact3 Config
OS2_SP_CfgErr Test OnLineOS1X
Alarm
Contact4 OS3_SP_CfgErr OnLineOS2Tst
Contact5 OnLineOS3Tst
Contact6 ComposTrip1 Composite OffLineOS1Tst
Contact7 ComposTrip2 Trips OffLineOS2Tst
ComposTrip3 OffLineOS3Tst
Sol1_Vfdbk Voltage to TrpAntcptTst
L5CFG1_Trip
Sol2_Vfdbk solenoid, Config Trip
L5CFG2_Trip LockRotorByp
Sol3_Vfdbk feedback Trip Bypass
L5CFG3_Trip HPZeroSpdByp
* K1_Fdbk OS1_Trip
Diagn
PTR1
* K2_Fdbk Trip Relay
feedback
OS2_Trip Overspd checking PTR2
* K3_Fdbk OS3_Trip Trips PTR3
PTR4
KE1_Fdbk Econ Relay Dec1_Trip PTR5
KE2_Fdbk feedback Dec2_Trip Dec PTR6
KE3_Fdbk Dec3_Trip Trips
Acc1_Trip Overspeed OS1_Setpoint
Clamp Relay
K4CL_Fdbk feedback Acc2_Trip Accel Setpoints OS2_Setpoint
K25A_Fdbk Synch Check Acc3_Trip Trips OS3_Setpoint
Relay feedback LPShaftLock LP Shaft Locked Trip
KESTOP2_Fdbk TREG, J4 OS1_TATrpSP
ESTOP2 TA Setpoint
TA_Trip
Sol4_Vfdbk Trip
Voltage to TA_StptLoss OTBias
Sol5_Vfdbk Antic
solenoid,
Sol6_Vfdbk feedback OT_Trip Ovrtemp TestETR1
K4_Fdbk Trip Relay
TestETR2
Trip Relay Test
K5_Fdbk L5ESTOP1 TestETR3
feedback ESTOPs
K6_Fdbk L5ESTOP2 TestETR4
* KE4_Fdbk
L5Cont1_Trip Trip1_Inhbt
* KE5_Fdbk Econ Relay
feedback L5Cont2_Trip
Contact
Trip2_Inhbt
* KE6_Fdbk
L5Cont3_Trip
Trips
Trip3_Inhbt
TPRO,J6 L5Cont4_Trip Trip4_Inhbt
GenPT_KVolts
Gen Volts L5Cont5_Trip Trip5_Inhbt
BusPT_KVolts
Bus Volts L5Cont6_Trip Trip6_Inhbt
TC1 L5Cont7_Trip Trip7_Inhbt
*
* TC2 Thermocouples,
these TC's will
* TC3
appear 3 times
mA1_Trip
Misc
ColdJunction mA2_Trip
in the CSDB (SMX) Trips
mA3_Trip IO Net ContWdog
Control
AnalogIn1
Analog Watch dog
AnalogIn2 Inputs L25A_Cmd
AnalogIn3 Synch
GenFreq
Check Cold
BusFreq
Junct'n CJBackup
GenVolts Backup
BusVolts
VCMI (Mstr) L86MR
GenFreqDiff Reset
GenPhaseDiff
Max speed
GenVoltsDiff PR_Max_Rst
Reset
PR1_Accel Accel
PR2_Accel
Gen Center DriveFreq
PR3_Accel
Freq
PR1_Max
Max Speed Speed1
PR2_Max Controller
since the
PR3_Max Speed
last Zero
Summarized
8-32 • Chapter 8 Applications
VPRO Protection Logic - Signal Space
143 of 1016
Inputs Signal Space
Cont1_TrEnab Configuration
Cont2_TrEnab Status
Cont3_TrEnab
Cont4_TrEnab
Cont5_TrEnab
Cont6_TrEnab
Cont7_TrEnab
Acc1_TrEnab
Acc2_TrEnab
Acc3_TrEnab
OT_TrEnab
GT_1Shaft
GT_2Shaft
LM_2Shaft
LM_3Shaft
LargeSteam
MediumSteam
SmallSteam
Stag_GT_1Sh
Stag_GT_2Sh
ETR1_Enab
ETR2_Enab
ETR3_Enab
ETR4_Enab
ETR5_Enab
ETR6_Enab
KE1_Enab
KE2_Enab
KE3_Enab
KE4_Enab
KE5_Enab
KE6_Enab
K4CL_Enab
K25A_Enab
Inhbt1_Fdbk
Inhbt2_Fdbk
Inhbt3_Fdbk
Inhbt4_Fdbk
Inhbt5_Fdbk
Inhbt6_Fdbk
Inhbt7_Fdbk
L3SS_Comm
Trip1_EnCon
Trip2_EnCon
Trip3_EnCon
Trip4_EnCon
Trip5_EnCon
Trip6_EnCon
Trip7_EnCon
Summarized
VPRO Protection Logic - Signal Space (continued)

Intercept Valve Trigger (IVT)
The peak speed following rejection of 10% or greater rated load cannot be
maintained within limits on some units by the normal speed and servo control action.
Approximately 70% of turbine power is generated in the reheat and low-pressure
turbine sections (the boiler re-heater volume represents a significant acceleration
energy source). Fast closing of the IVs can therefore quickly reduce turbine power
and peak overspeed. The action fulfills the first basic function of normal overspeed
control, limiting peak speed. The IVT signal is produced in the controller by the IVT
algorithm and associated sequencing, see the previous figure, EVA Valve Actuation
Logic.
Early Valve Actuation (EVA)

The EVA function may be implemented on sites where instability, such as loss of
synchronization, presents a problem. EVA closes the IVs for approximately one
second upon sensing a fault that is not a load rejection. This action reduces the
available mechanical power, thereby inhibiting the loss of synchronization that can
occur as a result of increased machine angle (unbalance between mechanical and
electrical power). If the fault persists, the generator loses synchronization and the
turbine is tripped by the overspeed control or out-of-step relaying.
The EVA is enabled in the toolbox by selecting Enable for the EVA_Enab
parameter. The conditions for EVA action are as follows:
• The difference between mechanical power (reheat pressure) and electrical power
(megawatts) exceeds the configured EVA unbalance threshold (EVA_Unbal)
input value.
• Electrical power (megawatts) decreases at a rate equivalent to (or greater than)
one of three rates configured for EVA megawatt rate threshold (EVA_Rate).
This value is adjustable according to three settings: HIgh, MEdium, and LOw.
These settings correspond to 50, 35, and 20 ms rates respectively.
Note The megawatt signal is derived from voltage and current signals provided
by customer-supplied transformers located on the generator side of the circuit
breaker.
The EVA_Unbal value represents the largest fault a particular generator can sustain
without losing synchronization. Although the standard setting for this constant is
70%, it may be adjusted up or down 0 to 2 per unit from the toolbox. All EVA events
are annunciated.
Fast Overspeed Trip in VTUR

In special cases where a faster overspeed trip system is required, the VTUR Fast
Overspeed Trip algorithms may be enabled. The system employs a speed
measurement algorithm using a calculation for a predetermined tooth wheel. Two
overspeed algorithms are available in VTUR as follows:
• PR_Single. This uses two redundant VTUR boards by splitting up the two
redundant PR transducers, one to each board.
• PR_Max. This uses one VTUR board connected to the two redundant PR
transducers. PR_Max allows broken shaft and deceleration protection without
the risk of a nuisance trip if one transducer is lost.
Summarized
The fast trips are linked to the output trip relays with an OR-gate as shown in the
following figures. VTUR computes the overspeed trip, not the controller, so the trip
is very fast. The time from the overspeed input to the completed relay dropout is 30
msec or less.
Input Signal Space

VTUR, Firmware
Config. Inputs
Scaling
Input, PR1 param. RPM PulseRate1
PR1Type, d RPM/sec Accel1
PR1Scale 2
PulseRate2 dt
------ Four Pulse Rate Circuits ------- RPM PulseRate2
PulseRate3 Accel1 RPM/sec Accel2
Accel2 RPM PulseRate3
RPM/sec Accel4
Fast Overspeed Protection
FastTripType PR_Single
PulseRate1 A
PR1Setpoint A>B S FastOS1Trip
PR1TrEnable B
R
PR1TrPerm
PulseRate2 A
A>B S
PR2Setpoint B FastOS2Trip
PR2TrEnable R
PR2TrPerm
PulseRate3 A
PR3TrEnable B
R
PR3TrPerm
PulseRate4 A
A>B S FastOS4Trip
PR4Setpoint B
PR4TrEnable R
PR4TrPerm
InForChanA Accel1
Accel2 Input AccelA
Accel3 cct. A S
Accel4 select A>B AccATrip
AccASetpoint
B R
AccelAEnab
AccelAPerm
InForChanB Accel1
Accel2 Input AccelB
Accel3 cct. A S AccBTrip
Accel4 select A>B
AccBSetpoint B R
AccelBEnab Fast Trip
AccelBPerm Path
ResetSys, VCMI, Mstr False = Run
OR
PTR1 Primary Trip Relay, normal Path, True= Run True = Run Output, J4,PTR1
AND
PTR1_Output
PTR2 Primary Trip Relay, normal Path, True= Run AND True = Run Output, J4,PTR2
PTR2_Output
PTR3 True = Run Output, J4,PTR3
PTR3_Output -------------Total of six circuits ----- Output, J4A,PTR4
PTR4 True = Run
PTR4_Output Output, J4A,PTR5
PTR5 True = Run
PTR5_Output True = Run Output, J4A,PTR6
PTR6
PTR6 Output
Summarized
Fast Overspeed Algorithm, PR-Single

Signal Space
Input Config. VTUR, Firmware
Scaling inputs
Input, PR1 param. PulseRate1 RPM PulseRate1
PR1Type, RPM/sec Accel1
2 d
PR1Scale
dt RPM PulseRate2
PulseRate2
Accel1 ------ Four Pulse Rate Circuits ------- RPM/sec Accel2
PulseRate3 Accel2 RPM PulseRate3
Accel3 RPM/sec Accel3
RPM/sec Accel4
FastTripType PR_Max Fast Overspeed Protection
DecelPerm
DecelEnab
DecelStpt
InForChanA
InForChanB
Accel1 Input AccelA
Neg A
Accel2 cct. S
Accel3 AccelB AB
B PR1/2Max
PulseRate1 A
MAX A>B S
PulseRate2 FastOS1Trip
FastOS1Stpt B
FastOS1Enab R
FastOS1Perm
PR3/4Max
PulseRate3 A
MAX A>B S FastOS2Trip
PulseRate4
FastOS2Stpt B
FastOS2Enab R
FastOS2Perm
N/C FastOS3Trip
PR1/2Max N/C FastOS4Trip
A
|A-B| A
PR3/4Max A>B S
DiffSetpoint B FastDiffTrip
B
DiffEnab R
DiffPerm
Fast Trip
ResetSys, VCMI, Mstr Path
OR
False = Run
True = Run Output, J4,PTR1

PTR1 Primary Trip Relay, normal Path, True= Run AND
PTR1_Output
PTR2_Output
PTR3_Output -------------Total of six circuits --------- True = Run Output, J4A,PTR4
PTR4
PTR5 True = Run Output, J4A,PTR5
PTR5_Output
PTR6_Output
Fast Overspeed Algorithm, PR-Max
Summarized
Compressor Stall Detection
Gas turbine compressor stall detection is included with the VAIC firmware and is
executed at a rate of 200 Hz. There is a choice of two stall algorithms and both use
the first four analog inputs, scanned at 200 Hz. One algorithm is for small LM gas
turbines and uses two pressure transducers. The other algorithm is for heavy-duty gas
turbines and uses three pressure transducers, refer to the following figures.
Real-time inputs are separated from the configured parameters for clarity. The
parameter CompStalType selects the type of algorithm required, either two
transducers or three. PS3 is the compressor discharge pressure, and a drop in this
pressure (PS3 drop) is an indication of a possible compressor stall. In addition to the
drop in pressure, the algorithm calculates the rate of change of discharge pressure,
dPS3dt, and compares these values with configured stall parameters (KPS3
constants). Refer to the following figures.
The compressor stall trip is initiated by VAIC, and the signal is sent to the controller
where it is used to initiate a shutdown. The shutdown signal can be used to set all the
fuel shut-off valves (FSOV) through the VCRC and TRLY or DRLY board.
Summarized
Input VAIC, 200 Hz scan rate *Note: where x, y, represent any two Signal Space
Config of the input circuits 1 thru 4. Inputs
Input, cctx* param.
AnalogInx*
Scaling
Low_Input, Low_Value,
High_Input, High Value 4
Sys Lim Chk #1
SysLim1Enabl, Enabl SysLimit1_x*
4
SysLim1Latch, Latch
SysLim1Type, >=
SysLimit1, xxxx
ResetSys, VCMI, Mstr Sys Lim Chk #2
4 SysLimit2_x*
SysLim2Enabl, Enabl AnalogIny*
SysLim2Latch, Latch
SysLimit1_y*
SysLim2Type, <=
SysLimit2, xxxx SysLimit2_y*
Validation & Stall Detection

CompStalType two_xducer PS3B_Fail
OR PS3A_Fail OR
Input Circuit Selection PS3A PS3B
InputForPS3A eg. AnalogIn2
InputForPS3B PS3A_Fail
eg. AnalogIn4 PS3_Fail
PS3B_Fail AND
PS3A A
|A-B| A
PS3B DeltaFault
B A>B
PressDelta B
PS3Sel Selection Definition
If PS3B_Fail & not PS3A_Fail
SelMode Max then PS3Sel = PS3A;
ElseIf PS3A_Fail & not PS3B_Fail
PS3A then PS3Sel = PS3B;
ElseIf DeltaFault
then PS3Sel = Max (PS3A, PS3B)
PS3B ElseIf SelMode = Avg PS3Sel PressSel
then PS3Sel = Avg (PS3A, PS3B)
PS3A_Fail ElseIf SelMode = Max
then PS3Sel = Max (PS3A, PS3B) d DPS3DTSel
__
Else
PS3B_Fail then PS3SEL = old value of PS3SEL dt PressRateSel
-DPS3DTSel
-1 X
TimeDelay
-DPS3DTSel TD
KPS3_Drop_Mx PS3_Fail
KPS3_Drop_Mn
KPS3_Drop_I A Mid A AND
KPS3_Drop_S A+B A>B
X B B
z-1
stall_timeout
PS3i
PS3Sel X stall_set
KPS3_Delta_S AND S
A
delta_ref CompStall
KPS3_Delta_I A+B MIN Latch
B A R
stall_delta
KPS3_Delta_Mx delta AB AND PS3i_Hold
A
KPS3_Drop_L
B PS3Sel BA-B stall_permissive
CompStalPerm
MasterReset, VCMI, Mstr
Small (LM) Gas Turbine Compressor Stall Detection Algorithm
Summarized
Input VAIC, 200 Hz scan rate *Note: where x, y, z, represent any
Signal Space
Config. three of the input circuits 1 thru 4. inputs
param. Scaling
Input, cctx* AnalogInx*
Low_Input, Low_Value,
High_Input, High Value 4 Sys Lim Chk #1
SysLim1Enabl, Enabl SysLimit1_x*
4
SysLim1Latch, Latch
SysLim1Type, >=
SysLimit1, xxxx
ResetSys, VCMI, Mstr
Sys Lim Chk #2
4 SysLimit2_x*
SysLim2Enabl, Enabl
AnalogIny*
SysLim2Latch, Latch SysLimit1_y*
SysLim2Type, <=
SysLimit2_y*
SysLimit2, xxxx
AnalogInz*
SysLimit1_z*
SysLimit2_z*
Stall Detection
CompStalType
three_xducer
not used DeltaFault

Input Circuit Selection
InputForPS3A
eg. AnalogIn1
InputForPS3B
eg. AnalogIn2
InputForPS3C
eg. AnalogIn4
PS3C
PS3B MID PS3Sel, or CPD PressSel
PressDelta not used PS3A SEL
d DPS3DTSel
__
SelMode not used dt PressRateSel
-DPS3DTSel
-1 X
TimeDelay
TD
KPS3_Drop_Mx -DPS3DTSel
KPS3_Drop_Mn
KPS3_Drop_I MID A
A
KPS3_Drop_S A+B A>B
X B B
z-1
stall_timeout
PS3i
PS3Sel X stall_set
KPS3_Delta_S S
A AND CompStall
A+B delta_ref Latch
KPS3_Delta_I MIN stall_
B A
KPS3_Delta_Mx delta R
delta AB PS3i_Hold A
B AND A-B
PS3Sel stall_permissive
B
CompStalPerm
MasterReset, VCMI, Mstr
Heavy Duty Gas Turbine Compressor Stall Detection Algorithm
Summarized
200
0
B. Delta PS3 drop (PS3 initial - PS3 actual) , DPS3, psid

180 25
0 0
Rate of Change of Pressure- dPS3dt, psia/sec

D
A. KPS3_Drop_S
B. KPS3_Drop_I
C. KPS3_Drop_Mn
140 D. KPS3_Drop_Mx 20
0 0
120 A
0
100 15
0 0
80
0
60 10
0 0
G
40 E
0
20 5
C
0 0
E. KPS3_Delta_S
B
0 F. KPS3_Delta_I
F G. KPS3_Delta_Mx
-200 0
0 100 200 300 400 500 600 700
Initial Compressor Discharge Pressure PS3
Configurable Compressor Stall Detection Parameters
The variables used by the stall detection algorithm are defined as follows:
PS3 Compressor discharge pressure
PS3I Initial PS3
KPS3_Drop_S Slope of line for PS3I versus dPS3dt
KPS3_Drop_I Intercept of line for PS3I versus dPS3dt
KPS3_Drop_Mn Minimum value for PS3I versus dPS3dt
KPS3_Drop_Mx Maximum value for PS3I versus dPS3dt
KPS3_Delta_S Slope of line for PS3I versus Delta PS3 drop
KPS3_Delta_I Intercept of line for PS3I versus Delta PS3 drop
KPS3_Delta_Mx Maximum value for PS3I versus Delta PS3 drop
Summarized
Ground Fault Detection Sensitivity
Ground fault detection on the floating 125 V dc power bus is based upon monitoring
the voltage between the bus and the ground. The bus voltages with respect to ground
are normally balanced (in magnitude), that is the positive bus to ground is equal to
the negative bus to ground. The bus is forced to the balanced condition by the
bridging resistors, Rb, as shown in the following figure. Bus leakage (or ground
fault) from one side will cause the bus voltages with respect to ground to be
unbalanced. Ground fault detection is performed by the VCMI using signals from the
PDM. Refer to Volume II of this System Guide.
P125 Vdc
Rb Rf Vout,Pos
Monitor1
Jumper Grd Fault
Grd Vout,Neg
Rb Monitor2
N125 Vdc
Electrical Circuit Model
Rb/2
Vbus/2 Vout,
Rf Bus Volts
wrt Ground
Ground Fault on Floating 125 V dc Power Bus
There is a relationship between the bridge resistors, the fault resistance, the bus
voltage, and the bus to ground voltage (Vout) as follows:
Vout = Vbus*Rf / [2*(Rf + Rb/2)]
Therefore the threshold sensitivity to ground fault resistance is as follows:
Rf = Vout*Rb / (Vbus – 2*Vout).
The ground fault threshold voltage is typically set at 30 V, that is Vout = 30 V. The
bridging resistors are 82 K each. Therefore, from the formula above, the sensitivity
of the control panel to ground faults, assuming it is on one side only, is as shown in
the following figure.
Note On Mark V, the bridging resistors are 33 K each so different Vout values
result.
Summarized
Sensitivity to Ground Faults
Vbus - Bus Vout - Measured Bus to Rb (Kohms) - bridge
voltage ground voltage (threshold) resistors (balancing) Rf (Kohms) -fault Control System
resistor
105 30 82 55 Mark VI
125 30 82 38 Mark VI
140 30 82 31 Mark VI
105 19 82 23 Mark VI
125 19 82 18 Mark VI
140 19 82 15 Mark VI
105 10 82 10 Mark VI
125 10 82 8 Mark VI
140 10 82 7 Mark VI
105 30 33 22 Mark V
125 30 33 15 Mark V
140 30 33 12 Mark V
The results for the case of 125 V dc bus voltage with various fault resistor values is
40.0
30.0 Fault Resistance (Rf) Vs Threshold
Fault, Rf
Voltage (Vout) at 125 V dc on

20.0
Mark VI
10.0
0.0
0 10 20 30
Voltage, Vout
Threshold Voltage as Function of Fault Resistance
Analysis of Results
On Mark VI, when the voltage threshold is configured to 30 V and the voltage bus is
125 V dc, the fault threshold is 38 Ω. When the voltage threshold is configured to 17
V and the voltage bus is 125 V dc, the fault threshold is 15 Ω.
The sensitivity of the ground fault detection is configurable. Balanced bus leakage
decreases the sensitivity of the detector.
Summarized
Notes
154 of 1016
Glossary of Terms
application code
Software that controls the machines or processes, specific to the application.
ARCNet
Attached Resource Computer Network. A LAN communications protocol developed
by Datapoint Corporation.The physical (coax and chip) and datalink (token ring and
board interface) layer of a 2.5 MHz communication network which serves as the
basis for DLAN+.
ASCII
American Standard for Code for Information Interchange (ASCII). An 8-bit code
used for data.
Asynchronous Device Language (ADL)

An application layer protocol used for I/O communication on IONet.
attributes
Information, such as location, visibility, and type of data that sets something apart
from others. In signals, an attribute can be a field within a record.
Balance of Plant (BOP)

Plant equipment other than the turbine that needs to be controlled.
Basic Input/Output System (BIOS)

Performs the controller boot-up, which includes hardware self-tests and the file
system loader. The BIOS is stored in EEPROM and is not loaded from the toolbox.
baud
A unit of data transmission. Baud rate is the number of bits per second transmitted.
Bently Nevada
A manufacturer of shaft vibration monitoring equipment.
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).
Summarized
I of 1016 Glossary of Terms • G-1
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.
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.
COM port
Serial controller communication ports (two). COM1 is reserved for diagnostic
information and the Serial Loader. COM2 is used for I/O communication.
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.
Current Transformer (CT)

Measures current in an ac power cable.
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.
Summarized
G-2 • Glossary of Terms 156 of 1016
dead band
A range of values in which the incoming signal can be altered without changing the
output response.
device
A configurable component of a process control system.
DIN-rail
European standard mounting rail for electronic modules.
Distributed Control System (DCS)

Control system, usually applied to control of boilers and other process equipment.
DLAN+
®
GE Energy LAN protocol, using an ARCNET controller chip with modified
ARCNET drivers. A communication link between exciters, drives, and controllers,
featuring a maximum of 255 drops with transmissions at 2.5 MBPS.
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, Digital, and Intel .
Ethernet Global Data (EGD)

Control network and protocol for the controller. Devices share data through EGD
exchanges (pages).
excitation control system

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.
fault code
A message from the controller to the HMI indicating a controller warning or failure.
Finder
A subsystem of the toolbox for searching and determining the usage of a particular
item in a configuration.
firmware
The set of executable software that is stored in memory chips that hold their content
without electrical power, such as EEPROM.
Summarized
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.
Graphic Window
A subsystem of the toolbox for viewing and setting the value of live signals.
health
A term that defines whether a signal is functioning as expected.
Heartbeat
A signal emitted at regular intervals by software to demonstrate that it is still active.
hexadecimal (hex)
Base 16 numbering system using the digits 0-9 and letters A-F to represent the
decimal numbers 0-15. Two hex digits represent 1 byte.
I/O
Input/output interfaces that allow the flow of data into and out of a device.
I/O drivers
Interface the controller with input/output devices, such as sensors, solenoid valves,
and drives, using a choice of communication networks.
I/O mapping
Method for moving I/O points from one network type to another without needing an
interposing application task.
Summarized
initialize
To set values (addresses, counters, registers, and such) to a beginning value prior to
the rest of processing.
Innovation Series Controller

A process and logic controller used for several types of GE industrial control
systems.
instance
Update an item with a new definition.
IONet
The Mark VI 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.
macro
A group of instruction blocks (and other macros) used to perform part of an
application program. Macros can be saved and reused.
Mark VI Turbine Controller

A controller hosted in one or more racks that perform turbine-specific speed control,
logic, and sequencing.
median
The middle value of three values; the median selector picks the value most likely to
be closest to correct.
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.
non-volatile
The memory specially designed to store information even when the power is off.
Summarized
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.
pcode
A binary set of records created by the toolbox, which contain the controller
application configuration code for a device. Pcode is stored in RAM and Flash
memory.
PDM
Power Distribution, Modular consists of core components and branch components
that make up the power distribution system for the Mark VI Controller. The PDM
can be customized for specific applications.
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.

Ethernet communication network between the HMI Servers and the HMI Viewers
and workstations
Potential Transformer (PT)

Measures voltage in a power cable.
Power Load Unbalance (PLU)

Detects a load rejection condition which can cause overspeed.
product code (runtime)

Software stored in the controller’s Flash memory that converts application code
(pcode) to executable code.
PROFIBUS
An open fieldbus communication standard defined in international standard EN 50
170 and is supported in simplex Mark VI systems.
Programmable Logic Controller (PLC)

Designed for discrete (logic) control of machinery. It also computes math (analog)
function and performs regulatory control.
Summarized
Proximitor
Bently Nevada's proximity probes used for sensing shaft vibration.
QNX
A real time operating system used in the controller.
realtime
Immediate response, referring to process control and embedded control systems that
must respond instantly to changing conditions.
reboot
To restart the controller or toolbox.
Redundant Power Supply Module (RPSM)

IS2020RPSM Redundant Power Supply Module for VME racks that mounts on the
side of the control rack instead of the power supply. The two power supplies that
feed the RPSM are mounted remotely.
register page
A form of shared memory that is updated over a network. Register pages can be
created and instanced in the controller and posted to the SDB.
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.
resources
Also known as groups. Resources are systems (devices, machines, or work stations
where work is performed) or areas where several tasks are carried out. Resource
configuration plays an important role in the CIMPLICITY system by routing alarms
to specific users and filtering the data users receive.
runtime
See product code.
runtime errors
Controller problems indicated on the front cabinet by coded flashing LEDS, and also
in the Log View of the toolbox.
sampling rate
The rate at which process signal samples are obtained, measured in samples/second.
Sequence of Events (SOE)

A high-speed record of contact transitions taken during a plant upset to allow
detailed analysis of the event.
Summarized
Serial Loader
Connects the controller to the toolbox computer using the RS-232C COM ports. The
Serial Loader initializes the controller flash file system and sets its TCP/IP address to
allow it to communicate with the toolbox over the Ethernet.
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 VI 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 Mark VI control also uses output hardware voting.
stall detection
Detection of stall condition in a gas turbine compressor.
static starter
This runs the generator as a motor to bring a gas turbine up to starting speed.
Status_S
GE proprietary communications protocol that provides a way of commanding and
presenting the necessary control, configuration, and feedback data for a device. The
protocol over DLAN+ is Status_S. It can send directed, group, or broadcast
messages.
Status_S pages
Devices share data through Status_S pages. They make the addresses of the points on
the pages known to other devices through the system database.
symbols
Created by the toolbox and stored in the controller, the symbol table contains signal
names and descriptions for diagnostic messages.
task
A group of blocks and macros scheduled for execution by the user.
Summarized
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.
time slice
Division of the total module scheduling period. There are eight slices per single
execution period. These slices provide a means for scheduling modules and tasks to
begin execution at different times.
trend
A time-based plot to show the history of values, similar to a recorder, available in the
Turbine Historian and the toolbox.
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.

Connects the Mark VI controllers, static starter control system, excitation control
system, PLCs, and other GE provided equipment to the HMI Servers.
validate
Makes certain that toolbox items or devices do not contain errors, and verifies that
the configuration is ready to be built into pcode.
Windows NT
Advanced 32-bit operating system from Microsoft for 386-based computers and
above.
word
A unit of information composed of characters, bits, or bytes, that is treated as an
entity and can be stored in one location. Also, a measurement of memory length,
usually 4, 8, or 16-bits long.
Summarized
Index
GE installation • 2
A related • 2
acronyms and abbreviations • 3 download
alarms offline • 44
diagnostic • 9 online • 44, 15
overview • 6 topology and application code • 42
process • 7
E
ANSI • 1
application code • 21, 4 early planning • 1
early valve actuation • 39
B electrical • 1, 16
boards elevation • 6
I/O • 12 environment • 4
terminal • 14 equipment receiving and handling • 3
UL Class 1 Division 2 Listed • 7 Ethernet
VCMI communication • 10 GSM • 19
installing • 32
C Modbus Slave • 14
Ethernet Global Data (EGD) • 11
cable
separation and routing • 2, 22 F
specifications • 28
CIMPLICITY • 3, 5 failure
code download • 42 handling • 33
command action • 32 power distribution module • 11
communications • 10, 12, 20 fault detection
components ground • 48
system • 1 features
Computer Operator Interface (COI) • 8 control and protection • 20
configuration interface • 4
hardware • 17 product • 5
Modbus • 12, 16 terminal block • 32
system • 9 fiber optic cables • 23, 24
connecting the system • 32 firmware • 12
contaminants • 4, 6
G
control
and protection • 20 generator protection • 5
cabinet • 1 grounding
controller equipment • 14, 15
designated • 24 guidelines
cable routing • 22
D cableway spacing • 22
Data Highway
H
Ethernet Switches • 7
Plant • 4, 5 hardware verification procedure • 12
Unit • 2, 6 Historian • 9
diagnostic alarms • 9 Historian tools • 9
disagreement detector • 31 how to get help • 3
documents Human-Machine Interface (HMI) • 3, 18
Summarized
I of 1016 Index • I-1
a controller • 2
I a terminal board • 2
I/O a VCMI • 2
boards • 12 an I/O board • 2
cabinet • 1
S
installation
support • 1 sequence of events (SOE) • 3, 19, 9
interface serial • 15
features • 4 serial port parameters • 18
modules • 1 startup checks • 38
IONet • 11, 10 state exchange • 29
IP address • 8 storage • 4
synchronization
L generator • 1
levels of redundancy • 19 simulation • 12
link to Distributed Control System (DCS) • 4 time • 30
low voltage directive • 2 system
building grounding • 16
M components • 1
excitation control • 5
median value analog voting • 30
Modbus • 12, 16 T
Modbus slave
Ethernet • 14 third-party connectivity • 37
serial • 15 TMR
module architecture • 21
control • 6 operation • 23
interface • 8 test procedure • 18
Turbine protection • 17 Toolbox • 2
MTBFO • 36 totalizers • 11
Turbine
N Historian • 9
Historian tools • 9
NEMA • 5, 1
protection • 34
O U
online repair • 35
UDH communicator • 24, 32
overview
alarms • 6 V
network • 1
vibration • 7, 9
P voting • 30
power load unbalance • 35 W
power requirements • 10
process alarms • 7 weights and dimensions • 5
processing wire sizes • 28
input • 27
output • 25
protection • 34
Q
QNX • 18
R
replacing
Summarized
I-2 • Index 165 of 1016
g GE Energy
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Summarized
1 540 387 7000
www.geenergy.com
166 of 1016
GE Energy
Mark* VI Control
System Guide, Volume II
GEH-6421M
Reduced manual for MAINTENANCE training
in Gas Turbine Mechanical Drive application
g


Revised: 080314
Issued : 040120

ARCNET is registered trademark of Datapoint Corporation.
AutoCAD is a registered trademark of Autodesk, Inc.
Belden is a registered trademark of Belden Electronic Wire and Cable of Cooper.
Celeron is a trademark of Intel Corporation.
CIMPLICITY is a registered trademark of GE Fanuc Automation North America, Inc.
Flamarrest is a trademark of Akzo Nobel N.V.
IEEE is a registered trademark of Institute of Electrical and Electronics Engineers.
Intel and Pentium are registered trademarks of Intel Corporation.
Kevlar is a registered trademark of E. I. du Pont de Nemours Company.
Keyphasor is a registered trademark of Bently Nevada Corporation.
Modbus is a registered trademark of Schneider Automation.
NEC is a registered trademark of the National Fire Protection Association.
PI DataLink is a registered trademark of OSI Software Inc.
POSIX is a registered trademark of the Institute of Electrical and Electronic Engineers (IEEE).
Proximitor and Velomitor are registered trademarks of Bently Nevada.
QNX is a registered trademark of QNX Software Systems, Ltd. (QSSL).
Siecor is registered trademark of Corning Cable Systems Brands, Inc.
Tefzel is a registered trademark of E I du Pont de Nemours Company.
ThinWire is a trademark of Xerox Corporation.
Vibro-meter is a registered trademark of Vibro-Meter, Inc.
3M is a trademark of 3M Company.
168 of 1016


equipment.

169 of 1016

personnel.


170 of 1016
Contents
I/O Overview 5
Relay Board Summary ................................................................................................................................. 8
Trip Terminal Board Summary .................................................................................................................... 9
Simplex DIN-Rail Mounted Terminal Board Summary............................................................................... 9
UCV Controller 13
Controller Overview................................................................................................................................... 13
UCVG Controller ....................................................................................................................................... 15
UCVF Controller........................................................................................................................................ 18
UCVE Controllers ...................................................................................................................................... 20
UCVD Controller ....................................................................................................................................... 27
UCVB Controller ....................................................................................................................................... 29
Alarms ........................................................................................................................................................ 31
UCV Board UCVD Controller Runtime Errors.......................................................................................... 32
VAIC Analog Input/Output 35

VAIC Analog Input/Output........................................................................................................................ 35
TBAI Analog Input/Output ........................................................................................................................ 48
DTAI Simplex Analog Input/Output.......................................................................................................... 54
VAMA Acoustic Monitoring 59

VAMA Acoustic Monitoring ..................................................................................................................... 59
DDPT Simplex Dynamic Pressure Transducer Input................................................................................. 73
VAMB Acoustic Monitoring Input 79

VAMB Acoustic Monitoring...................................................................................................................... 79
VAOC Analog Output 97

VAOC Analog Output................................................................................................................................ 97
TBAO Analog Output .............................................................................................................................. 103
DTAO Simplex Analog Output................................................................................................................ 107
VCCC/VCRC Discrete Input/Output 111

VCCC/VCRC Discrete Input/Output ....................................................................................................... 111
TBCI Contact Input with Group Isolation................................................................................................ 118
TICI Contact Input with Point Isolation ................................................................................................... 123
DTCI Simplex Contact Input with Group Isolation ................................................................................. 127
TRLYH1B Relay Output with Coil Sensing ............................................................................................ 131
TRLYH1C Relay Output with Contact Sensing....................................................................................... 136
TRLYH1D Relay Output with Servo Integrity Sensing........................................................................... 141
TRLYH1E Solid-State Relay Output ....................................................................................................... 147
TRLYH1F Relay Output with TMR Contact Voting ............................................................................... 153
DRLY Simplex Relay Output .................................................................................................................. 160
171
GEH-6421M Mark VI Turbine Control System Guide of 1016
Volume II Contents • I
VCMI Bus Master Controller 165
VCMI Bus Master Controller ................................................................................................................... 165
VGEN Generator Monitor and Trip 175

VGEN Generator Monitor and Trip ......................................................................................................... 175
TGEN Generator Monitor ........................................................................................................................ 183
TRLYH1B Relay Output with Coil Sensing ............................................................................................ 187
TRLYH1F Relay Output with TMR Contact Voting ............................................................................... 193
VPRO Turbine Protection Board 201

VPRO Emergency Turbine Protection ..................................................................................................... 201
TPRO Emergency Protection ................................................................................................................... 219
TREG Turbine Emergency Trip ............................................................................................................... 226
TRES Turbine Emergency Trip................................................................................................................ 233
TREL Turbine Emergency Trip ............................................................................................................... 239
VPYR Pyrometer Board 245

VPYR Pyrometer Input ............................................................................................................................ 245
TPYR Pyrometer Input............................................................................................................................. 261
VRTD RTD Input 265

VRTD RTD Input..................................................................................................................................... 265
TRTD RTD Input ..................................................................................................................................... 273
DRTD Simplex RTD Input ...................................................................................................................... 279
VSVA Servo Control 285

VSVA Servo Control................................................................................................................................ 285
VSCA Serial Communication Input/Output 317

VSCA Serial Communication Input/Output............................................................................................. 317
DSCB Simplex Serial Communication Input/Output............................................................................... 326
DPWA Transducer Power Distribution .................................................................................................... 329
VSVO Servo Control 333

VSVO Servo Control................................................................................................................................ 333
TSVO Servo Input/Output........................................................................................................................ 369
DSVO Simplex Servo Input/Output ......................................................................................................... 377
VTCC Thermocouple Input 385

VTCC Thermocouple Input...................................................................................................................... 385
TBTC Thermocouple Input ...................................................................................................................... 395
DTTC Simplex Thermocouple Input........................................................................................................ 399
VTUR Turbine Specific Primary Trip 403

VTUR Primary Turbine Protection .......................................................................................................... 403
TTURH1B Primary Turbine Protection Input .......................................................................................... 419
TRPG Turbine Primary Trip..................................................................................................................... 426
II • Contents 172 of 1016 Mark VI Turbine Control System Guide Volume II

GEH-6421M
TRPL Turbine Primary Trip..................................................................................................................... 431
TRPS Turbine Primary Trip ..................................................................................................................... 434
TTSA Trip Servo Interface....................................................................................................................... 438
DTUR Simplex Pulse Rate Input ............................................................................................................. 441
DTRT Simplex Primary Trip Relay Interface .......................................................................................... 444
DRLY Simplex Relay Output .................................................................................................................. 447
VVIB Vibration Monitor Board 451

VVIB Vibration Monitor.......................................................................................................................... 451
TVIB Vibration Input............................................................................................................................... 472
DVIB Simplex Vibration Input ................................................................................................................ 477
TTPW Power Conditioning Board 483

TTPW Power Conditioning...................................................................................................................... 483
VME Rack Power Supply 491

VME Rack Power Supply ........................................................................................................................ 491
VME Redundant Power Supply 507

Redundant Power Supply ......................................................................................................................... 507
Power Distribution Modules 517

PDM Power Distribution Modules........................................................................................................... 517
PPDA Power Distribution System Feedback ........................................................................................... 527
DS2020DACAG2 ac-dc Power Conversion............................................................................................. 531
Replacement/Warranty 537
Pack/Board Replacement ......................................................................................................................... 537
Renewal/Warranty.................................................................................................................................... 540
Glossary of Terms 541
173
Volume II Contents • III
I/O Overview
The following table lists all the I/O processor boards, the number of I/O per
processor that they support, and their associated standard terminal boards. Some
standard terminal boards have simplex and TMR versions (in addition to simplex
DIN-rail mounted ones). Refer to the section, simplex DIN-rail mounted terminal
board summary for simplex DIN-rail mounted terminal board information.
I/O Processor Boards and Standard Terminal Boards
I/O Processor Number of I/O Associated Terminal

Board I/O Signal Type per Processor Boards
VAIC Analog inputs, 0-1 mA, 4-20 mA, voltage 20 TBAI
Analog outputs, 4-20 mA, 0-200 mA 4 TBAI
VAOC Analog outputs, 4-20 mA 16 TBAO
VCCC Contact inputs 48 TBCI, TICI
Solenoid outputs 12 TRLY
Dry contact relay outputs 12 TRLY
VCRC Contact inputs 48 TBCI
Solenoid outputs 12 TRLY
Dry contact relays outputs 12 TRLY
VGEN Analog inputs, 4-20 mA 4 TGEN
Potential transformers, gen (1) bus (1) 2 TGEN
Current transformers on generator 3 TGEN
Relay outputs (optional) 12 TRLY
VPRO Pulse rate inputs 3 TPRO
Potential transformers, gen (1), bus (1) 2 TPRO
Thermocouple inputs 3 TPRO
Analog inputs, 4-20 mA 3 TPRO
Trip solenoid drivers 3 TREG (through J3)
Trip interlock inputs 7 TREG (through J3)
Emergency-stop input (hardwired) 1 TREG (through J3)
Economizing relays 3 TREG (through J3)
Trip solenoid drivers 3 TREG (2nd board through J4)
Emergency-stop input (hardwired) 1 TREG (2nd board through J4)
Economizing relays 3 TREG (2nd board through J4)
VPYR Pyrometer temperature inputs (4/probe) 2 TPYR
® 2 TPYR
Keyphasor shaft position inputs
VRTD Resistance temperature device (RTD) 16 TRTD
VSCA Serial I/O communications 6 DSCB
VSVO Servo outputs to hydraulic servo valve 4 TSVO
LVDT inputs from valve position 12 TSVO
LVDT excitation outputs 8 TSVO
Pulse rate inputs for flow monitoring 2 TSVO
Pulse rate probe excitation 2 TSVO
VTCC Thermocouple inputs 24 TBTC
VAMA Acoustic monitoring (Simplex only) 2 DDPT
174
Volume II I/O Overview • 5
I/O Processor Number of I/O Associated Terminal
Board I/O Signal Type per Processor Boards
VAMB Acoustic monitoring (Simplex only) 18 TAMB
VTURH1B Pulse rate magnetic speed pickups 4 TTUR
Potential transformers, generator and bus 2 TTUR
Shaft current and voltage monitor 2 TTUR
Breaker Interface 1 TTUR
Flame detectors (Geiger-Mueller) 8 TRPG (through J4)
Trip solenoid drivers for ETDs 3 TRPG (through J4)
VTURH2B Same as above, plus 3 trip solenoid drivers TRPG (2nd board through
J4A)
VVIB ® 16 TVIB
Shaft Proximitor /seismic probes
(Vib/Displ/Accel)
Shaft proximity probes (displacement) 8 TVIB
Shaft proximity reference (Keyphasor) 2 TVIB
Terminal Board Terminal Block Features

Many of the terminal boards in the Mark VI use a 24-position pluggable barrier
terminal block (179C9123BB). These terminal blocks have the following features:
• Made from a polyester resin material with 130°C (266 °F) rating
• Terminal rating is 300 V, 10 A, UL class C general industry, 0.375 in creepage,
0.250 in strike
• UL and CSA code approved
• Screws finished in zinc clear chromate and contacts in tin
• Each block screw is number labeled 1 through 24 or 25 through 48 in white
• Recommended screw tightening torque is 8 in lbs
Terminal Board Disconnect Switch (TBSW)

The Mark VI Terminal Board Disconnect Switch (TBSW) provides an individual
disconnect switch for each of the 48 customer I/O points on Mark VI terminal boards
in the following figure. This facilitates such procedures as continuity checking,
isolation for test, and others. Two TBSW assemblies are required for each terminal
board, one numbered 1-24, the other numbered 25-48 (GE part numbers
336A4940CHG1 and 336A4940CHG2 respectively). The TBSW fits and connects
into the terminal boards’ 24-point pluggable barrier terminal block receptacles.
The TBSW is designed for continuous 5 A rms current at 300 V rms and complies
with EN61010-1 clearance specifications. The NEMA power/voltage class rating (A,
E, F, G) for the TBSW is dependant on the terminal board the TBSW is mounted
upon see the following table.
Top View Front View Side View
TBSW Mounted to Terminal Block
6 • I/O Overview 175 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
The TBSW is not to be used for live circuit interruption. The
circuit must be de-energized before the circuit is either closed
or opened by the TBSW.
TBSW/Terminal Board Applications Summary
In the following table lists the TBSW/terminal board applications for the Mark VI.
An OK indicated in the TBSW applications column indicates an approved
application of the TBSW for terminal board specifications for voltage and current.
Those board points that require limiting the terminal boards application are indicated
with a note number (corresponding notes follow the table).
TBSW/Terminal Board Applications
TBSW Applications
Board Type CSA NEMA
TBTC Thermocouples OK OK
TRTD RTDs OK OK
TBAI Analog inputs OK OK
TBAO Analog outputs OK OK
TBCI Contact inputs OK OK
TICI Contact inputs Note 1 Note 2
TRLY Contact outputs Note 1 Note 2
TSVO Servo I/O OK OK
TTUR Turbine I/O OK OK
TRPG Flame I/O Note 3 Note 3
TREG OK OK
TRPL OK OK
TREL OK OK
TRPS OK OK
TRES OK OK
TPRO OK OK
TVIB OK OK
TGEN OK OK
TPYR OK OK
Table Notes:
1. The inputs on the TICI and TRLY boards are high voltage isolated inputs. The
TBSW is classified by CSA for use up to 300 V rms. Circuits applied to the TICI or
TRLY terminal board with the TBSW installed must be externally limited to 300 V
rms. Care must also be taken to assure that no adjacent circuits, that when both are
operating, do not exceed 300 V rms between them.
2. NEMA ratings are given according to the power and voltage limiting abilities of
the circuit. The TICI and TRLY terminal boards carry no components that are
designed to limit voltage or current. For this reason, the TBSW application
limitations for these two terminal boards will depend on the customer’s ability to
install voltage and current limiting devices on the TBSW circuits according to
NEMA guidelines. The following chart indicates the NEMA class and the voltage it
must be limited too before it can be applied to the TBSW. Voltages are for circuit
voltage, and circuit to adjacent circuit voltage.
176
Class Voltage Description
A 50 V All circuits which cannot be otherwise classified. Use this
peak rating when no external current and voltage limiting devices
are present.
E 225 V Known and controlled transient voltages without sufficient
peak current limiting impedance.
F 300 V Known and controlled voltages with short-circuit power 10
rms kVA or less.
G 300 V Known and controlled voltages with short-circuit power
rms 500VA or less.
3. The TRPG flame detectors require a 335 V dc circuit. The TBSW is classified by
CSA and NEMA for use up to 300 V rms. Circuits applied to the TRPG terminal
board flame detectors with the TBSW installed must be must be limited to 300 V
rms, disallowing the use of the TBSW when the flame detectors are operational.
Relay Board Summary

Mark VI Relay Board Features
TRLYH1E
DRLYH1A TRLYH1C TRLYH2E TRLYH1F
Feature DRLYH1B TRLYH1B TRLYH2C TRLYH1D TRLYH3E TRLYH2F
Fused solenoid 0 6 6 6 0 12 (with WPDF)
driver relays
# Dry circuit 12 5 5 0 12 12 (without WPDF)
relays
Relay Type Mechanica Mechanica Mechanical Mechanica Solid-State Mechanical
l l Form C l Form A H1F = Form A
Form C Form C Form C H2F = Form B
Control Simplex Simplex Simplex Simplex Simplex TMR Only
and TMR and TMR and TMR and TMR
# Ignition 0 1 1 0 0 0
transformer
outputs
Relay No MOV MOV and R- MOV No No
suppression C
Solenoid relay No Relay coil Relay NO Solenoid No Relay coil current /12
sensing current/6 contact resistance (WPDF)
type/quantity voltage/6 /6
Other relay No Relay coil Relay NO N/A Relay NO Relay coil current /12
sensing current/6 contact contact voltage/ (no WPDF)
type/quantity voltage/6 12
Solenoid fuse N/A 6 6 6 N/A 12 (WPDF)
sense
Operating 120/240 120/240 H1=120/ 240 No H3= 120/240 120
voltage V ac H2=No
Operating 28/125 24/125 H1=125 24/ 110/ H2=28 28/125
voltage V dc H2=24 125 H3=125
Internal No No No Yes No No
switching power
supply
Daughterboards None None 18 None None WPDF
Terminal type Euro-box Barrier Barrier Barrier Barrier Barrier
GEH-6421M
Trip Terminal Board Summary
Mark VI Trip Terminal Board Features
Output Input
Output Contacts, Contacts, Input
Contacts, 24 V dc, Dry, Contacts, Economy
125 V dc, 1 3 Amp ESTOP 125 V dc Dry, 24 V dc Resistor
Board TMR Simplex
Amp
TRPGH1A* Yes No Yes No No No No No
TRPGH1B Yes No Yes Yes No No No No
TRPGH2A* No Yes Yes No No No No No
TRPGH2B No Yes Yes Yes No No No No
TREGH1A* Yes No Yes No Yes Yes No Yes
TREGH1B Yes No Yes Yes Yes Yes No Yes
TREGH2B Yes No Yes Yes Yes No Yes Yes
TRPLH1A Yes No Yes Yes Yes No No No
TRELH1A Yes No Yes Yes No Yes No No
TRELH2A Yes No Yes Yes No No Yes No
TRPSH1A Yes Yes Yes Yes Yes No No No
TRESH1A Yes Yes Yes Yes No Yes No No
TRESH2A Yes Yes Yes Yes No No Yes No
*These boards will become obsolete.
Simplex DIN-Rail Mounted Terminal Board Summary

Speed control systems for small turbines require a simplified system architecture.
Simplex control is used to reduce cost and save space. Compact DIN-rail mounted
terminal boards are available instead of the larger T-type terminal boards used on
TMR systems. IONet is not used since the D-type terminal boards cable directly into
the control chassis to interface with the I/O boards.
In the VME rack, a VCMI board provides two-way communication between the
controller and the I/O processor boards. The controller Ethernet port is used to
communicate with other system components, such as an operator interface or PLC.
Additional PLC I/O can be tied into the system using the controller Genius port. A
typical system is illustrated in the following figure. The system is powered by 24 V
dc, and uses a low voltage version of the standard VME rack power supply.
The board designations and functions along with the corresponding I/O processor
boards are listed in the following table. In all cases, the signal conditioning on the
DIN-type terminal boards is the same as on the T-type boards, and the I/O
specifications described apply. However, the number of inputs and outputs, and the
grounding provisions differ, and the boards do not support TMR. Permanently
mounted high-density Euro-Block terminal blocks are used to save space. The blocks
have terminals accepting wire sizes up to one #12 wire, or two #14 wires. The typical
wire size used is #18 AWG.
178
Fan
x x x x x x x x
To sequencer
& operator Ethernet
interface V U V V V V V V V V V S Power
C C T T T A A S S R C P Supply
M V U U C I I V V T R A
Serial Modbus COM2 I B R R C C C O O D C R
communication E
x x x x x x x x x x x x x
24 V dc
power
1 2 3 4 5 6 7 8 9 10 11 12 13
DTCI
DTCI Contact
DTUR Contact Inputs
Turbine DTRT Inputs
Control Transit
-ion Bd. DTUR
Turbine
Control DRLY DRLY
DRLY Relay Relay
Relay Outputs Outputs
Output
DRTD
DRTD RTD
RTD Inputs
DTTC DTTC Inputs
Thermo DTAI DTAI
Thermo Analog
-couples -couples Analog
Inputs Inputs
DSVO
DSVO Servo
Servo Outputs
Outputs
DTAI
Analog DTAI
Inputs Analog
Inputs
DSVO DSVO
Servo Servo
Outputs Outputs
Small Simplex System Rack, Boards, and Cabling
GEH-6421M
Simplex DIN-Rail Mounted Terminal Boards
DIN Euro Size Number

Terminal board of Points Description of I/O I/O Processor Board
DTTC 12 Thermocouple temperature inputs with one cold junction VTCC
reference
DRTD 8 RTD temperature inputs VRTD
DTAI 10 Analog current or voltage inputs with on-board 24 V dc VAIC
2 power supply
Analog current outputs, with choice of 20 mA or 200 mA
DTAO 8 Analog current outputs, 0-20 mA VAOC
DTCI 24 Contact Inputs with external 24 V dc excitation VCRC (or VCCC)
DRLY 12 Form-C relay outputs, dry contacts, customer powered VCRC (or VCCC)
DTRT -------- Transition board between VTUR and DRLY for solenoid VTUR
trip functions
DTUR 4 Magnetic (passive) pulse rate pickups for speed and fuel VTUR
flow measurement
DSVO 2 Servo valve outputs with choice of coil currents from 10 VSVO
mA to 120 mA
6 LVDT valve position sensors with on-board excitation
2 Active pulse rate probes for flow measurement, with 24 V

dc excitation provided
DVIB 8 Shaft Proximitor/seismic probes (Vib/Displ/Accel) VVIB
4 Shaft proximity probes (displacement)
1 Shaft proximity reference (Keyphasor)
Grounding
During panel design, provisions for grounding the terminal board and wiring shields
must be made. These connections should be as short as possible. A metal grounding
strip can be firmly mounted to the panel on the right hand side of the terminal board.
Shields and the SCOM connection can be conveniently made to this strip. Note that
only the thermocouple board has screws for the shield wires.
The VME rack is grounded to the mounting panel by the metal-to-metal contact
under the mounting screws. No wiring to the ground terminal is required. For more
grounding information, refer to Volume I, Chapter 5.
180
UCV Controller
Controller Overview
The Mark* VI UCV_ controller is a 6U high, single or double slot, single board
computer (SBC) that operates the turbine application code. The controller mounts in
a VME rack called the control module and communicates with the turbine I/O boards
®
through the VME bus. The controller operating system is QNX , a real time,
multitasking OS designed for high-speed, high-reliability industrial applications.
Three communication ports provide links to operator and engineering interfaces as
follows:
• Ethernet connections to the UDH for communication with HMIs, and other
control equipment
• RS-232C connection for setup using the COM1 port
• RS-232C connection for communication with distributed control systems (DCS)
®
using the COM2 port (such as Modbus slave)
Operation
The controller is loaded with software specific to its application to steam, gas, and
land-marine aeroderivative (LM), or balance of plant (BOP) products. It can execute
up to 100,000 rungs or blocks per second, assuming a typical collection of average
size blocks. An external clock interrupt permits the controller to synchronize to the
clock on the VCMI communication board to within ±100 microseconds.
External data is transferred to and from the control system database (CSDB) in the
controller over the VME bus by the VCMI communication board. In a simplex
system, the data consists of the process inputs and outputs from the I/O boards. In a
TMR system, the data consists of the voted inputs from the input boards, singular
inputs from simplex boards, computed outputs to be voted by the output hardware,
and the internal state values that must be exchanged between the controllers.
Note Application software can be modified online without requiring a restart.
Controller Versions
Five controller versions are in use:
• The single-slot UCVE is the current generation controller used in most new
systems.
• The double-slot UCVF is the high-end current generation controller used in only
the systems that require it.
• The single-slot UCVG features performance between the UCVE and the UCVF
and may be used as a direct replacement for any previous controller version
without necessitating a backplane upgrade.
Note The double-slot UCVB and UCVD are no longer shipped with new
systems, but are still in use in older systems.
181
Volume II UCV Controller • 13
The UCVE and UCVF may also be used to replace earlier revision controllers, but
require a backplane upgrade. If replacing a UCVB, an Ethernet cabling upgrade from
10Base2 to 10Base-T is also required.
Diagnostics
If a failure occurs in the Mark VI controller while it is running application code, the
rotating status LEDs (if supported) on the front panel stop and an internal fault code
is generated.
If a failure occurs in the Mark VI controller, a diagnostic alarm is generated that can
be read from the toolbox. In the UCVB and UCVD, these diagnostics are also
encoded by flashing LEDs on the front panel. The error numbers and descriptions are
available on the toolbox help screen. Additional information can also be obtained
from the controller COM1 serial port. For further information, refer to GEH-6421,
Vol. I Mark VI System Guide, Chapter 7, Troubleshooting and Diagnostics.
Installation
A control module contains (at a minimum) the controller and a VCMI. Three rack
types can be used: the GE Fanuc integrator’s rack shown in the following figure and
two sizes of Mark VI racks shown in the section, VCMI - Bus Master Controller.
The GE Fanuc rack is shorter and is used for stand-alone modules with remote I/O
only. The Mark VI racks are longer and can be used for local or remote I/O.
Whichever rack is used, a cooling fan is mounted either above or below the
controller. The stand-alone control module implemented with a GE Fanuc
integrator’s rack also requires a VDSK board to supply fan power and provide the
rack identification through an ID plug.
VCMIH2 Communication Board with Controller Interface Board

Three IONet Ports (VCMIH1 with One UCVX VDSK
IONet is for Simplex systems)
VME Rack
POWER
SUPPLY
Power Supply
x x x x
Cooling Fan Fan 24 Vdc

behind Panel Power
Typical Controller Mounted in Rack with Communication Board
14 • UCV Controller 182 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
UCVG Controller
® ™
The UCVG is a single-slot board using an Intel Ultra Low Voltage Celeron 650
MHz processor with 128 MB of flash memory and 128 MB of SDRAM. Two
10BaseT/100BaseTX (RJ-45 connector) Ethernet ports provide connectivity. The
first Ethernet port allows connectivity to the UDH for configuration and peer-to-peer
communication.
The second Ethernet port is for use on a separate IP logical subnet and can be used
for Modbus or private Ethernet Global Data (EGD) network. This Ethernet port is
configured through the toolbox. The controller validates its toolbox configuration
against the existing hardware each time the rack is powered up.
Note A separate subnet address allows the controller to uniquely identify an

Ethernet port. IP subnet addresses are obtained from the Ethernet network
administrator (for example, 192.168.1.0, 192.168.2.0).
Mark VI Controller UCVGH1
Reset Switch
(allows the system to be
RS
reset from the front panel) T
S
V
Monitor port for GE use G
A
Keyboard/mouse port
COM1 RS-232C port for M
[ / for GE use
initial controller setup K
2 1
COM2 RS-232C port for
serial communication C Ethernet Status LEDs
O
M
2:1
Active (Blinking = Active)
ETHERNET 1 (Solid = Inactive)
Primary Ethernet port for L
Link (Yellow = 10BaseT)
A
Unit Data Highway (UDH) N (Green = 100BaseTX)
communication (toolbox) 1
L
A
(Solid = Inactive)
ETHERNET 2 N Link (Yellow = 10BaseT)
2
Secondary Ethernet port for (Green = 100BaseTX)
expansion I/O communication USB
Two individual USB connectors
S
Status LEDs
Status LEDs
B: Booting. BIOS boot in progress. (red)
I: IDE activity is occurring. (yellow)
P
M
P: Power is present. (green)
C R: Board reset. (red)
UCVG
H1
x
UCVG Controller
183
Note The factory setting of the battery is in the disabled position. To enable the
battery, set SW10 to the closed position as shown in the following drawing.
(SW10
shown in (Do not change
closed 2-3 setting)
position)
AS Shipped
Setting
UCVG Controller Side View
GEH-6421M
UCVG Controller Specifications
Item Specification
Microprocessor Intel Ultra Low Voltage Celeron 650 MHz
Memory 128 MB SDRAM
128 MB Compact Flash Module
256 KB Advanced Transfer Cache
Operating System QNX
Programming Control block language with analog and discrete blocks; Boolean logic represented in relay
ladder diagram format. Supported data types include:
Boolean
16-bit signed integer
32-bit floating point
64-bit long floating point
Primary Ethernet Twisted pair 10BaseT/100BaseTX, RJ-45 connector:
Interface (Ethernet 1) TCP/IP protocol used for communication between controller and toolbox
®
EGD protocol for communication with CIMPLICITY HMI, and Series 90-70 programmable
logic controllers (PLCs)
Ethernet Modbus protocol supported for communication between controller and third-party
DCS
Secondary Ethernet Twisted pair 10BaseT/100BaseTX, RJ-45 connector:
Interface (Ethernet 2) EGD protocol
DCS
COM Ports Two micro-miniature 9-pin D connectors:
COM1 Reserved for diagnostics, 9600 baud, 8 data bits, no parity, 1 stop bit
®
COM2 Used for serial Modbus communication, 9600 or 19200 baud
Power Requirements +5 V dc, 4 A typical, 5.4 A maximum
UCVGH1 +12 V dc, less than 1 mA typical
- 12 V dc, less than 1 mA typical
Expansion site ®
PMC expansion site available, IEEE 1386.1 5V PCI
Environment Operating temperature: 0ºC to 70ºC (32 ºF to 158 ºF)
Storage temperature: -40ºC to 80ºC (-40 ºF to 176 ºF)
Note The UCVG controller contains a Type 1 Lithium battery. Replace only with
equivalent battery type, rated 3.3 V, 200 mA.
185
UCVF Controller
®
The UCVF is a double-slot board using an 850 MHz Intel Pentium III processor
with 16 or 128 MB of flash memory and 32 MB of DRAM. Two
10BaseT/100BaseTX (RJ-45 connector) Ethernet ports provide connectivity. The
first Ethernet port allows connectivity to the UDH for configuration and peer-to-peer
communication.
The second Ethernet port is for use on a separate IP logical subnet. This Ethernet
port is configured through the toolbox. The controller validates its toolbox
configuration against the existing hardware each time the rack is powered up.
Note A separate subnet address allows the controller to uniquely identify an

Ethernet port. IP subnet addresses are obtained from the Ethernet network
administrator (for example, 192.168.1.0, 192.168.2.0).
Mark VI Controller UCVFH2
x x
Ethernet Status LEDs
ETHERNET 1 (Solid = Inactive)
Primary Ethernet port for Unit L Link (Yellow = 10BaseT)
Data Highway (UDH) A
(Green = 100BaseTX)
N
communication (toolbox) 1 Active (Blinking = Active)
L (Solid = Inactive)
A
ETHERNET 2 N Link (Yellow = 10BaseT)
Secondary Ethernet port for 2 (Green = 100BaseTX)
STATUS
expansion I/O communication
C
O
Status LEDs
COM1 RS-232C port for M VMEbus SYSFAIL
initial controller setup 1:2
Flash Activity
COM2 RS-232C port for U Power Status
serial communication S CPU Throttle Indicator
B
RST
M
Keyboard/mouse port /
K
for GE use
S
V
Monitor port for GE use G
A
Note: To connect the

M
E batteries that enable
Z NVRAM and CMOS, set
Z
A jumper E8 to pins 7-8 ("IN")
N and jumper E10 to ("IN").
I
N
E
UCVF
H2
x x
UCVF Controller
GEH-6421M
UCVF Controller Specifications
Item Specification
Microprocessor Intel Pentium III 850 MHz
Memory 32 MB DRAM
16 or 128 MB Compact Flash Module
256 KB Advanced Transfer Cache
Battery-backed SRAM - 8K allocated as NVRAM for controller functions
Programming Control block language with analog and discrete blocks; Boolean logic represented in
relay ladder diagram format. Supported data types include:
Boolean
Primary Ethernet Interface Twisted pair 10BaseT/100BaseTX, RJ-45 connector:
(Ethernet 1) TCP/IP protocol used for communication between controller and toolbox
EGD protocol for communication with CIMPLICITY HMI, and Series 90-70 PLCs
Ethernet Modbus protocol supported for communication between controller and third-
party DCS
party DCS
Power Requirements +5 V dc, 6 A typical, 7 A maximum
UCVFH2 +12 V dc, 200 mA typical, 400 mA maximum
-12 V dc, 2.5 mA typical
187
UCVE Controllers
The UCVE is available in multiple forms: UCVEH2 and UCVEM01 to
UCVMEM05. The UCVEH2 is the standard Mark VI controller. It is a single-slot
board using a 300 MHz Intel Celeron processor with 16 or 128 MB of flash memory
and 32 MB of DRAM. A single 10BaseT/100BaseTX (RJ-45) Ethernet port provides
connectivity to the UDH.
The UCVEM_ _ modules have all the features of the UCVEH2 with the addition of
supporting additional Ethernet ports and Profibus. Some UCVEM_ _ modules
support secondary 10BaseT/100BaseTX Ethernet ports for use on a separate IP
logical subnet. The secondary Ethernet port is configured through the toolbox. The
controller validates its toolbox configuration against the existing hardware each time
the rack is powered up. A separate subnet address allows the controller to uniquely
identify an Ethernet port.
Mark VI Controller UCVEH2
Status LEDs
STATUS
Monitor port for GE use VME bus SYSFAIL

Flash Activity
S
V Power Status
G
A
Keyboard/mouse port
for GE use
M
/
K
initial controller setup C
O
M
COM2 RS-232C port for 1:2 Ethernet Status LEDs
serial communication
L
A Active (Blinking = Active)
N (Solid = Inactive)
ETHERNET 1 RST
Ethernet port for UDH Link (Yellow = 10BaseT)
P
communication C (Green = 100BaseTX)
M Note: To connect the
I
P
batteries that enable
NVRAM and CMOS, set
jumper E8 to pins 7-8 ("IN")
M and jumper E10 to ("IN").
E
Z
Z
A
N
I
N
E
UCVE
H2
x
UCVE Controller
GEH-6421M
UCVE Controller Specifications
Item Specification
Microprocessor Intel Celeron 300 MHz
Memory 32 MB DRAM
16 or 128 MB Compact Flash Module
128 KB L2 cache
Battery-backed SRAM - 8K allocated as NVRAM for controller functions
Programming Control block language with analog and discrete blocks; Boolean logic represented in
relay ladder diagram format. Supported data types include:
Boolean
Primary Ethernet Twisted pair 10BaseT/100BaseTX, RJ-45 connector:
Interface (Ethernet 1) TCP/IP protocol used for communication between controller and toolbox
EGD protocol for communication with CIMPLICITY HMI and Series 90-70 PLCs
party DCS
Power Requirements +5 V dc, 6 A typical, 8 A maximum
UCVEH2 +12 V dc, 180 mA typical, 250 mA maximum
-12 V dc, 180 mA typical, 250 mA maximum
UCVEM01 Controller Specifications

Item Specification
Ethernet Modbus protocol supported for communication between controller and third
party DCS
Power Requirements +5 V dc, 6.2 A typical, 8.2 A maximum
+12 V dc, 180 mA typical, 250 mA maximum
189
Note For specifications common to all UCVE modules, refer to UCVEH2
Controller Specifications.
Mark VI Controller UCVEM01
Status LEDs
STATUS
VME bus SYSFAIL

Monitor port for GE use
Flash Activity
S
V Power Status
G
A
Keyboard/mouse port
for GE use
M
/
K Ethernet Status LEDs
O
1:2 (Solid = Inactive)
Link (Yellow = 10BaseT)
L (Green = 100BaseTX)
A
ETHERNET 1 N
Primary Ethernet port for RST
Speed (Off = 10BaseT)
UDH communication SPEED LINK/
(On = 100BaseTX)
(toolbox) ACT
P
C
Link/Active
ETHERNET 2 M
I
Secondary Ethernet port for P
M
E
Note: UCVEMxx modules Z
are shipped with the Z
A
batteries enabled. N
I
N
E
UCVE
M01
x
UCVEM01 Front Panel

Item Specification
Interfaces (Ethernet 2-4) EGD protocol
Ethernet Modbus protocol supported for communication between controller and
third-party DCS
GEH-6421M
Status LEDs
STATUS
Monitor port for GE use VME bus SYSFAIL

Flash Activity
S
V Power Status
G
for GE use
M
/
K
O
1:2
L
ETHERNET 1 A (Solid = Inactive)
N
Primary Ethernet port for UDH
communication (toolbox)
RST Link (Yellow = 10BaseT)
P
(Green = 100BaseTX)
C
M
I
P
Secondary Ethernet ports for Note: UCVEMxx modules
expansion I/O communication: PMC
are shipped with the
0
M batteries enabled.
ETHERNET 2 E
0
Z
1
Z
1
Not used A
N
2
I
2
ETHERNET 3 N
3
E
3
ETHERNET 4
610
UCVE
M02
x
UCVEM02 Front Panel

Item Specification
PROFIBUS Interface (PROFIBUS 1-2) PROFIBUS DP master class 1
191
x x
Status LEDs
STATUS Left: Power Status
Middle: Flash Activity
Monitor port for GE use Right: VME bus SYSFAIL
PCI MEZZANINE CARD 0

S
V
G
PROFIBUS 1
for GE use
M PROFIBUS Serial Interface
/ Transmit Active LED
K
O
1:2

PROFIBUS 2
L PROFIBUS Serial Interface
ETHERNET 1 A
N Transmit Active LED
communication (toolbox) RST
P
C
Top: Active M
I
(Blinking = Active) P Note: UCVEMxx modules
(Solild = Inactive) are shipped with the
Bottom: Link batteries enabled.

M
(Yellow = 10BaseT) E
(Green = 100BaseTX) Z
Z
A
N
I
N
E
UCVE
M03
x x
UCVEM03 Front Panel

Item Specification
PROFIBUS Interface PROFIBUS DP master class 1
(PROFIBUS 1-3)
GEH-6421M
x x
Status LEDs
STATUS Left: Power Status
Monitor port for GE use Middle: Flash Activity
Right: VMEbus SYSFAIL

S
Keyboard/mouse port V
for GE use G
A
PROFIBUS 1
M PROFIBUS Serial Interface
/ Transmit Active LED
COM1 RS-232C port for K

O
1:2

L PROFIBUS 2
ETHERNET 1 A
PROFIBUS Serial Interface
N
Primary Ethernet port for UDH Transmit Active LED
communication (toolbox) RST
P
Ethernet Status LEDs C
Top: Active
M
(Blinking = Active) I
(Solild = Inactive) P
Bottom: Link
(Yellow = 10BaseT) PROFIBUS 3

M
(Green = 100BaseTX) E
Z Transmit Active LED
Z
A
N
Note: UCVEMxx modules I
are shipped with the N
E
batteries enabled.
UCVE
M04
x x
UCVEM04 Front Panel

Item Specification
party DCS
PROFIBUS Interface PROFIBUS DP master class 1
(PROFIBUS 1)
193
Status LEDs
STATUS
VMEbus SYSFAIL
Monitor port for GE use Flash Activity
S
V Power Status
G
A
Keyboard/mouse port
for GE use M
/
K
COM1 RS-232C port for Ethernet Status LEDs
C
initial controller setup O
M
COM2 RS-232C port for 1:2 Active (Blinking = Active)
serial communication (Solid = Inactive)
L Link (Yellow = 10BaseT)
ETHERNET 1 A
N
(Green = 100BaseTX)
RST
communication (toolbox) Speed (Off = 10BaseT)
(On = 100BaseTX)
SPEED LINK/
ACT
P
C
ETHERNET 2 M Link / Active

I
Secondary Ethernet port for P
PROFIBUS 1
M
E
Z Transmit Active LED
Note: UCVEMxx modules Z
A
are shipped with the N
batteries enabled. I
N
E
UCVE
M05
x
UCVEM05 Front Panel
GEH-6421M
UCVD Controller
The UCVD is a double-slot board using a 300 MHz AMD K6 processor with 8 MB
of flash memory and 16 MB of DRAM. A single 10BaseT (RJ-45 connector)
Ethernet port provides connectivity to the UDH.
The UCVD contains a double column of eight status LEDs. These LEDs are
sequentially turned on in a rotating pattern when the controller is operating normally.
When an error condition occurs, the LEDs display a flashing error code that
identifies the problem. For more information, refer to GEH-6410, Innovation Series
Controller System Manual.
Mark VI Controller UCVDH1, H2
x x
ETHERNET
Ethernet port for UDH
communication
ACTIVE H L
SLOT1
Controller and communication BMAS Status LEDs showing Runtime Error Codes
ENET
status LEDs SYS resulting from startup, configuration, or
BSLV
RESET
download problems
FLSH
GENA
Monitor port for GE Use
MONITOR
Only
Hard disk connector for GE use

HARD DISK

initial controller setup
COM2
COM1

serial communications
LPT1
ISBus drive LAN (Not Used)

Special ports for GE Use,
KEYBOARD
printer, keyboard, and

mouse
GENIUS
MOUSE
Receptacle for Genius cable plug
UCVD
H2
x x
UCVD Controller Front Panel
195
UCVD Controller Specification
Item Specification
Microprocessor AMD-K6 300 MHz
Memory 16 MB DRAM
8 MB Flash Memory in UCVD
256 KB of level 2 cache
Operating QNX
System
LEDs LEDs on the faceplate provide status information as follows:
ACTIVE Processor is active
SLOT 1 Controller configured as slot 1 controller in VME rack
BMAS VME master access is occurring
ENET Ethernet activity
BSLV VME slave access is occurring
STATUS Display rotating LED pattern when OK
Display flashing error code when faulted
FLSH Writing to Flash memory
GENX Genius I/O is active
Boolean
Ethernet Twisted pair 10BaseT, RJ-45 connector
Interface TCP/IP protocol used for communication between controller and toolbox
Serial Request Transfer Protocol (SRTP) interface between controller and HMI
DCS
Power +5 V dc, 6 A
Requirements +12 V dc, 200 mA
-12 V dc, 200 mA
GEH-6421M
UCVB Controller
The UCVB is a double-slot board using a 133 MHz Intel Pentium processor with 4
MB of flash memory and 16 MB of DRAM. A single 10Base2 (BNC connector)
Ethernet port provides connectivity to the UDH.
The UCVB contains a double column of eight status LEDs. These LEDs are
sequentially turned on in a rotating pattern when the controller is operating normally.
When an error condition occurs, the LEDs display a flashing error code that
identifies the problem. For more information, refer to GEH-6410, Innovation Series
Controller System Manual.
Mark VI Controller UCVBG1
x x
DLAN DROP
1 0
8
Ethernet port for UDH DLAN network drop number
communication ETHERNET configuration dip switches (Not Used)
1
ACTIVE H L
SLOT1
Controller and communication BMAS Status LEDs showing Runtime Error Codes
ENET
status LEDs SYS resulting from startup, configuration, or
BSLV
RESET
download problems
FLSH
GENA
Monitor port for GE Use
MONITOR
Only
HARD DISK
COM1 RS-232C port for Hard disk connector for GE use

initial controller setup
COM2
COM1

serial communications
LPT1
DLAN network connection (Not Used)

DLAN
Special ports for GE use,

KEYBOARD
printer, keyboard, and

mouse GENIUS
MOUSE
Receptacle for Genius cable plug
UCVB
G1
x x
UCVB Controller Front Panel
197
UCVB Controller Specification
Item Specification
Microprocessor Intel Pentium 133 MHz
Memory 16 MB DRAM
4 MB Flash Memory in UCVB
256 KB of level 2 cache
LEDs LEDs on the faceplate provide status information as follows:
ACTIVE Processor is active
SLOT 1 Controller configured as slot 1 controller in VME rack
BMAS VME master access is occurring
ENET Ethernet activity
BSLV VME slave access is occurring
STATUS Display rotating LED pattern when OK
Display flashing error code when faulted
FLSH Writing to Flash memory
GENX Genius I/O is active
Boolean
Ethernet Interface ™
Thinwire 10Base2, BNC connector:
TCP/IP protocol used for communication between controller and toolbox
SRTP interface between controller and HMI
DCS
DLAN+ Interface ®
Interface to DLAN+, a high speed multidrop network based on ARCNET , using a token
passing, peer to peer protocol
Power +5 V dc, 5.64 A
Requirements +12 V dc, 900 mA
-12 V dc, 200 mA
GEH-6421M
Alarms
Fault Fault Description Possible Cause
31 I/O Compatibility Code Mismatch Outdated configuration in the VCMI
32 Diagnostic Queue Overflow Too many diagnostics are occurring simultaneously
33 Foreground Process Outdated runtime version
34 Background Process Outdated runtime version
37 Idle Process Outdated runtime version
38 Ambient Air Overt temperature Warning. The The rack fan has failed or the filters are clogged.
rack is beginning to overheat.
39 CPU Over temperature Fault. The controller The rack fan has failed or the filters are clogged.
CPU has overheated and may fail at any time.
40 Genius I/O Driver Process Outdated runtime version
41 Register I/O Process Outdated runtime version
42 Modbus Driver Process Outdated runtime version
43 Ser Process Outdated runtime version
44 Rcvr Process Outdated runtime version
45 Trans Process Outdated runtime version
46 Mapper Process Outdated runtime version
47 SRTP Process Outdated runtime version
48 Heartbeat Process Outdated runtime version
49 Alarm Process Outdated runtime version
50 Queue Manager Process Outdated runtime version
51 EGD Driver Process Outdated runtime version
52 ADL Dispatcher Process Outdated runtime version
53 ADL Queue Process Outdated runtime version
54 DPM Manager Process Outdated runtime version
68 Genius IOCHRDY Hangup Outdated runtime version
70 Genius Lock Retry Outdated runtime version
71 Genius Outdated runtime version
72 Application Code Online Load Failure Application code error
74 Application Code Startup Load Failure Application code error
75 Application Code Expansion Failure Application code error
76 ADL/BMS Communication Failure with the VCMI The VCMI firmware version is too old to work with this
controller runtime version.
77 NTP Process Outdated runtime version
78 Outdated Controller Topology Download application code and reboot
79 Outdated VCMI Topology Download configuration to VCMI and reboot
80 No VCMI Topology Old VCMI firmware doesn’t support controller/VCMI
topology checking. Upgrade VCMI firmware.
81 Platform Process Outdated runtime version
82 Hardware Configuration Error The controller hardware doesn’t match the configuration
specified by the toolbox. Use the toolbox to view the errors
in the controller trace buffer (for example: View General
Dump the trace buffer).
83 Register I/O Write/Command Limit Exceeded Verify that the total command rate of all Modbus interfaces
does not exceed the maximum.
84 State Exchange Voter Packet Mismatch Verify that all three controllers are executing the same
application code.
85 Maximum Number of Boolean State Variables The application code is using too many Boolean variables.
Exceeded Move some functions to other controllers.
199
86 Too Many EGD Producers Configured for Fault The controller can redirect data over the IONET from a
Tolerant Support maximum of 16 EGD producers. Data from subsequent
producers will be lost in the event of an Ethernet failure.
87 Too Many EGD Points Configured for Fault The controller can redirect a maximum of 1400 bytes of
Tolerant Support data over the IONET. Subsequent EGD points will be lost in
the event of an Ethernet failure.
88 Producing Fault Tolerant EGD Data The controller is redirecting data from the Ethernet to
another controller over the IONET.
89 Requesting Fault Tolerant EGD Data The controller is requesting that Ethernet data be redirected
to it over the IONET from another controller.
90 Process Alarm Queue Is Full Subsequent process alarms will be lost unless the current
alarms are acknowledged and cleared by the operator.
91 Hold List Queue Is Full Subsequent hold alarms will be lost unless the current
alarms are acknowledged and cleared by the operator.
92 Data Initialization Failure Verify that all controllers are executing the same application
code. If no VCMI is used (simulation mode), verify that the
clock source is set to internal. If a VCMI is used, verify that
the clock source is set to external.
93 Pcode mismatch between TMR controllers Download the same application code to all three controllers
94 Unable to start up Dynamic Data Recorder Outdated runtime version - download runtime and restart.
95 Dynamic Data Recorder Configuration Fault Revalidate the application code and then select the Update
Dynamic Data Recorder button from the toolbox toolbar
96 Dynamic Data Recorder Process Outdated runtime version - download runtime and restart
UCV Board UCVD Controller Runtime Errors

In addition to generating diagnostic alarms, the UCVB and the UCVD controller
boards display status information on front panel LEDs. The Status LED group on
these controllers contains eight segments in a two vertical column layout as shown in
the following figure. These LEDs display controller errors if a problem occurs. The
right-most column makes up the lower hexadecimal digit and the left-most column
makes up the upper digit (the least significant bits on the bottom). Numerical
conversions are provided with the fault code definitions.
Note For all controllers, refer to the stats line in the toolbox.
Controller front panel For example, flashing F

in this pattern:
ACTIVE H L
SLOT1 S
BMAS
ENET T
A F
SYS
BSLV T
U F
S
F
FLSH
GENA
is error 0x43, decimal 67
Flashing Controller Status LEDs Indicate Error Codes
GEH-6421M
If the controller detects certain system errors (typically during boot-up or download),
it displays flashing and non-flashing codes on these green status LEDs. These codes
correspond to runtime errors listed in the toolbox help file. The following table
describes the types of errors displayed by the LEDs.
Controller Runtime Errors
Controller Condition Status LED Display

Controller successfully completes its Displays a walking ones pattern consisting of a single lighted green LED
boot-up sequence and begins to rotating through the bank of LEDs.
execute application code
Error occurs during the BIOS phase Non-flashing error code is displayed
of the boot-up sequence
Error occurs during the application Flashing error codes are displayed until the error has been corrected and
code load either the application code is downloaded again, or the controller is
rebooted.
Error occurs while the controller is May freeze with only a single LED lighted. No useful information can be
running interpreted from the LED position. Fault codes are generated internally.
201
Notes
202 of 1016
VAIC Analog Input/Output
VAIC Analog Input/Output

Functional Description
The Analog Input/Output (VAIC) board accepts 20 analog inputs and controls 4
analog outputs. Each terminal board accepts 10 inputs and 2 outputs. Cables connect
the terminal board to the VME rack where the VAIC processor board is located.
VAIC converts the inputs to digital values and transfers them over the VME
backplane to the VCMI board, and then to the controller. For outputs, the VAIC
converts digital values to analog currents and drives these through the terminal board
into the customer circuit.
VAIC supports both simplex and triple modular redundant (TMR) applications.
When used in a TMR configuration, input signals on the terminal board are fanned
out to three VME board racks R, S, and T, each containing a VAIC. Output signals
are driven with a proprietary circuit that creates the desired current using all three
VAICs. In the event of a hardware failure, the bad VAIC is removed from the output
and the remaining two boards continue to produce the correct current. When used in
a simplex configuration, the terminal board provides input signals to a single VAIC,
which provides all of the current for outputs.
Compatibility
There are two generations of the VAIC board with corresponding terminal boards.
The original VAIC includes all versions prior to and including VAICH1C.
VAICH1B is included in this generation. When driving 20 mA outputs these boards
support up to 500 Ω load resistance at the end of 1000 ft of #18 wire. This generation
of board requires terminal board TBAIH1B or earlier for proper operation. They also
work properly with all revisions of DTAI terminal boards.
The newest VAICH1D and any subsequent releases are designed to support higher
load resistance for 20 mA outputs drive voltage: up to 18 V is available at the
terminal board screw terminals. This permits operation into loads of 800 Ω with
1000 ft of #18 wire with margin. This generation of the board requires TBAIH1C or
later, or any revision of STAI.
203
Volume II VAIC Analog Input/Output • 35
VME Rack R x
VAIC Board RUN

FAIL
STAT
TBAI Terminal Board TBAI Terminal Board
VME bus to VCMI

x JT1 x JT1
x x x x
x x x x
x x x x
x x x x
x x x x
x x x x
x x x x
x x x x Cable to VME
x x x
x
x x JS1 To x x JS1 Rack T
x x x
x
x x Rack x x
x T x
x x
x x x x
x x x x
x x
x To x
x Cable to VME VAIC
x x
x
JR1 x
x JR1
x
x
Rack x
x Rack S
x
x x
x x
x
S x x
x
x x J3
x x x x
x x x x
x x x x
x x x x
x x
J4
VAIC, Analog Input Terminal Boards, and Cabling (TMR System)
Installation
To install the V-type board
1 Power down the VME processor rack

2 Slide in the board and push the top and bottom levers in with your hands to seat
its edge connectors
3 Tighten the captive screws at the top and bottom of the front panel
Note Cable connections to the terminal boards are made at the J3 and J4
connectors on the lower portion of the VME rack. These are latching type
connectors to secure the cables. Power up the VME rack and check the
diagnostic lights at the top of the front panel. For details, refer to the section on
diagnostics in this document.
36 • VAIC Analog Input/Output 204 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Operation
The VAIC board accepts 20 analog inputs, controls 4 analog outputs, and contains
signal conditioning, an analog MUX, A/D converter, and D/A converter. The type of
analog input, either voltage, 4-20 mA, or ±1 mA, is selected by jumpers on the
terminal board. Two of the four analog output circuits are 4-20 mA and the other two
can be configured for 4-20 mA or 0-200 mA. Inputs and outputs have noise
suppression circuitry to protect against surge and high frequency noise.
The following table displays the analog I/O capacity of VAIC, using two TBAI
terminal boards.
Quantity Analog Input Types Quantity Analog Output Types

16 ±10 V dc, or ±5 V dc, or 4-20 mA 2 0-20 mA or 0-200 mA
4 4-20 mA, or ± 1 mA 2 0-20 mA
Analog Input Terminal Board <R> Module

TBAI
8 circuits per Controller
terminal board Application Software
Typical transmitter, Noise
Mark VI powered Suppr-
ession
+24 V dc P28V
Current Limit
+/-5,10 Vdc J#A Analog Input

Vdc
T N Board VAIC
4-20 ma S 20 ma
Return 250 ohms A/D D/A

J#B
Open Return
PCOM Connectors
2 circuits per at
terminal board bottom of
VME rack
P28V
+24 V dc Current Limit Excitation
1 ma J#A JR1 J3/4
+/-1 ma N
S 20 ma
4-20 ma 250
ohm 5k ohms
Return
J#B
Return
Open
Current
Two output circuits Regulator/
Jump select on one Power Supply
circuit only; #2 Circuit 200 ma
is 4-20 ma only
JO
Signal 20 ma
N
S
Return
ID
SCOM
VAIC and Analog Input Terminal Board, Simplex System
205
In a TMR system, analog inputs fan out to the three control racks from JR1, JS1, and
JT1. The 24 V dc power to the transducers comes from all three VME racks and is
diode OR selected on the terminal board. Each analog current output is fed by
currents from all three VAICs. The actual output current is measured with a series
resistor, which feeds a voltage back to each VAIC. The resulting output is the voted
middle value (median) of the three currents. The following figure shows VAIC in a
TMR arrangement.
Terminal Board TBAI <R> Module
8 circuits per Controller

Typical transmitter, termination board Application Software
Noise
Mark VI powered
Suppr-
P28V<T>
ession P28VR P28V<S>
+24 V dc Current Limit
J#A Analog Input

+/-5,10 Vdc Vdc
T N Board VAIC
4-20 ma S 20 ma
Return 250 ohms A/D D/A

J#B
Open Return
PCOM
Connectors
at
2 circuits per bottom of
termination board VME rack
P28VR
+24 Vdc Current Limit
Excitation
+/-1 ma 1 ma J#A JR1 J3/J4
N Filter 2 Pole
4-20 ma S 20 ma
250
ohm 5k ohms
Return
J#B
Open Return
PCOM S ID Current
T Regulator/
Two output circuits JO Power Supply
#2 circuit is 4-20 200 ma
mA only
Signal 20 ma
N S JS1
S T
Return
SCOM
ID
JT1 To rack<S>
To rack<T>
ID
VAIC and Analog Input Terminal Board, TMR System
Note With the noise suppression and filtering, the input ac common mode rejection
(CMR) is 60 dB, and the dc CMR is 80 dB.
GEH-6421M
Transmitters/transducers can be powered by the 24 V dc source in the control
system, or can be powered independently. Diagnostics monitor each output and a
suicide relay disconnects the corresponding output if a fault cannot be cleared by a
command from the processor. Hardware filters on the terminal board suppress high
frequency noise. Additional software filters on VAIC provide configurable low pass
filtering.
Compressor Stall Detection
VAIC firmware includes gas turbine compressor stall detection, executed at 200 Hz.
Two stall algorithms can be selected. Both use the first four analog inputs, scanned at
200 Hz. One algorithm is for small LM gas turbines and uses two pressure
transducers (refer to the figure, Small (LM) Gas Turbine Compressor Stall Detection
Algorithm). The other algorithm is for heavy-duty gas turbines and uses three
pressure transducers (refer to the figure, Heavy Duty Gas Turbine Compressor Stall
Detection Algorithm).
Real-time inputs are separated from the configured parameters for clarity. The
parameter CompStalType selects the type of algorithm required, either two
transducers or three. PS3 is the compressor discharge pressure. A drop in this
pressure (PS3 drop) indicates possible compressor stall. The algorithm also
calculates the rate of change of discharge pressure, dPS3dt, and compares these
values with configured stall parameters (KPS3 constants).
The compressor stall trip is initiated by VAIC, which sends the signal to the
controller where it is used to initiate a shutdown. The shutdown signal can be used to
set all the fuel shut-off valves (FSOV) through any relay output.
207
Specifications
Item Specification
Number of channels 24 channels per VAIC board (20 AI, 4 AO) with two terminal boards
Input span 4-20 mA, ±1 mA, ±5 V dc, ±10 V dc
Input Impedance 250 Ω at 4-20 mA
5,000 Ω at 1 mA
500,00 Ω at voltage input
Input converter resolution 16-bit A/D converter with 14-bit resolution
Scan time Normal scan 10 ms (100 Hz)
Inputs 1 through 4 available for scan at 200 Hz
Measurement accuracy Better than 0.1% full scale
Noise suppression on inputs The first 10 circuits (J3) have a hardware filter with single pole down break at 500 rad/sec
The second 10 circuits (J4) have a hardware filter with a two pole down break at 72 and
500 rad/sec
A software filter, using a two pole low pass filter, is configurable for 0, .75, 1.5 Hz, 3 Hz, 6
Hz, 12 Hz
Common mode rejection Ac CMR 60 dB @ 60 Hz, with up to ±5 V common mode voltage
Dc CMR 80 dB with -5 to +7 peak volt common mode voltage
Common mode voltage range ±5 V (±2 V CMR for the ±10 V inputs)
Output converter 12-bit D/A converter with 0.5% accuracy
Output load 500 Ω for 4-20 mA output – board revisions prior to and including VAICH1C (requires
TBAIH1B or DTAI)
800 Ω for 4-20 mA output, board revisions VAICH1D and later (requires TBAIH1C or
STAI)
50 Ω for 200 mA output
Power consumption Less than 31 MW
Compressor stall detection Detection and relay operation within 30 ms
Fault detection Analog input out of limits
Monitor D/A outputs, output currents, and total current
Monitor suicide relay and 20/200 mA scaling relays
Compare input signals with the voted value and check difference against the TMR limit
Failed I/O chip
Physical
Temperature 0 to 60°C (32 to 140 °F)
Size 26.04 cm high x 1.99 cm wide x 18.73 cm deep (10.26 in x 0.782 in x 7.375 in )
208
Diagnostics
Three LEDs at the top of the VAIC front panel provide status information. The
normal RUN condition is a flashing green, and FAIL is a solid red. The third LED
displays STATUS and is normally off, but displays a steady orange if a diagnostic
alarm condition exists in the board. Diagnostic checks include the following:
• Each analog input has hardware limit checking based on preset (non-
limit is exceeded a logic signal is set and the input is no longer scanned. If any
one of the input’s hardware limits is set, it creates a composite diagnostic alarm,
L3DIAG_VAIC, which refers to the entire board. Details of the individual
diagnostics are available from the toolbox. The diagnostic signals can be
individually latched, and then reset with the RESET_DIA signal.
• Each input has system limit checking based on configurable high and low levels.
These limits can be used to generate alarms, and can be configured for
enable/disable, and as latching/non-latching. RESET_SYS resets the out of
limits.
• In TMR systems, if one signal varies from the voted value (median value) by
more than a predetermined limit, that signal is identified and a fault is created.
This can provide early indication of a problem developing in one channel.
• Monitor D/A outputs, output currents, total current, suicide relays and 20/200
mA scaling relays; these are checked for reasonability and can create a fault.
• TBAI has its own ID device that is interrogated by VAIC. The board ID is coded
into a read-only chip containing the terminal board serial number, board type,
revision number, and the JR, JS, JT connector location. When the chip is read by
the I/O processor and a mismatch is encountered, a hardware incompatibility
fault is created.
GEH-6421M
Configuration
Parameter Description Choices
Configuration
System limits Enable or disable system limits Enable, disable
Output voting Select type of output voting Simplex, simplex TMR
Min_ MA_Input Select minimum current for healthy 4-20 mA input 0 to 21 mA
Max_ MA_Input Select maximum current for healthy 4-20 mA input 0 to 21 mA
CompStalType Select compressor stall algorithm (# of transducers) 0, 2, or 3
InputForPS3A Select analog input circuit for PS3A Analog in 1, 2, 3, or 4
InputForPS3B Select analog input circuit for PS3B Analog in 1, 2, 3, or 4
InputForPS3C Select analog input circuit for PS3C Analog in 1, 2, 3, or 4
SelMode Select mode for excessive difference pressure Maximum, average
PressDelta Excessive difference pressure threshold 5 to 500
TimeDelay Time delay on stall detection, in milliseconds 10 to 40
KPS3_Drop_Min Minimum pressure rate 10 to 2000
KPS3_Drop_I Pressure rate intercept 10 to 100
KPS3_Drop_S Pressure rate slope 0.05 to 10
KPS3_Delta_S Pressure delta slope 0.05 to 10
KPS3_Delta_I Pressure delta intercept 10 to 100
KPS3_Delta_Mx Pressure delta maximum 10 to 100
KPS3_Drop_L Threshold pressure rate 10 to 2000
KPS3_Drop_Mx Max pressure rate 10 to 2000
J3:IS200TBAIH1A Terminal board connected to VAIC through J3 Connected, not connected
AnalogIn1 First of 10 analog inputs - board point Point edit (input FLOAT)
Input type Current or voltage input type Unused, 4-20 mA, ± 5 V, ± 10 V
Low_Input Value of current at the low end of scale -10 to +20
Low_Value Value of input in engineering units at low end of scale -3.4082e + 038 to 3.4028e + 038
High_Input Value of current at the high end of scale -10 to +20
High_Value Value of input in engineering units at high end of scale -3.4082e + 038 to 3.4028e + 038
Input _Filter Bandwidth of input signal filter Unused, 0.75, 1.5 Hz, 3 Hz, 6 Hz, 12 Hz
TMR_Diff_Limit Difference limit for voted inputs in % of high-low values 0 to 100
Sys_Lim_1_Enable Input fault check Enable, disable
Sys_Lim_1_Latch Input fault latch Latch, unlatch
Sys_Lim_1_Type Input fault type Greater than or equal
Less than or equal
Sys_Lim_1 Input limit in engineering units -3.4082e + 038 to 3.4028e + 038
Sys_Lim_2_Enable Input fault check Enable, disable
Less than or equal
Sys_Lim_2 Input limit in engineering units -3.4082e + 038 to 3.4028e + 038
AnalogOut1 First of two analog outputs - board point Point edit (output FLOAT)
Output_MA Type of output current Unused, 0-20 mA, 0-200 mA
Low_MA Output mA at low value 0 to 200 mA
Low_Value Output in engineering units at low mA -3.4082e + 038 to 3.4028e + 038
High_MA Output mA at high value 0 to 200 mA
High_Value Output value in engineering units at high mA -3.4082e + 038 to 3.4028e + 038
210
TMR Suicide Suicide for faulty output current, TMR only Enable, disable
Diff Limit Current difference for suicide, TMR only 0 to 200 mA
D/A Err Limit Difference between D/A reference and output, in % for 0 to 100 %
suicide, TMR only
J4:IS200TBAIH1A Terminal board connected to VAIC via J4 Connected, not connected
AnalogIn11 First of 10 analog inputs - board point Point edit (input FLOAT)
AnalogOut3 First of two analog outputs - board point Point edit (output FLOAT)
Board Points (Signals) Description - Point Edit (Enter Signal Connection) Direction Type
L3DIAG_VAIC1 Board diagnostic Input BIT
SysLimit1_1 System limit 1 Input BIT

: : Input BIT
: : Input BIT
OutSuicide1 Status of suicide relay for output 1 Input BIT
: : Input BIT
DeltaFault Excessive difference pressure Input BIT
CompStall Compressor stall Input BIT

: : Input FLOAT
Out4MA Feedback, total output current, mA Input FLOAT
CompPressSel Selected compressor press, by stall Algor. Input FLOAT
PressRate Sel Selected compressor press rate, by stall Algor. Input FLOAT
CompStallPerm Compressor stall permissive Output BIT
GEH-6421M
Alarms
2 Flash memory CRC failure Board firmware programming error (board will not go
online)
3 CRC failure override is active Board firmware programming error (board is allowed
to go online)
16 System limit checking is disabled System checking was disabled by configuration
17 Board ID failure Failed ID chip on the VME I/O board
18 J3 ID failure Failed ID chip on connector J3, or cable problem
24 Firmware/hardware incompatibility. The firmware Invalid terminal board connected to VME I/O board-
on this board cannot handle the terminal board it is check the connectors and call the factory
connected to
30 ConfigCompatCode mismatch. Firmware: [ ] ; Tre: A tre file has been installed that is incompatible with
[ ] The configuration compatibility code that the the firmware on the I/O board. Either the tre file or
firmware is expecting is different than what is in firmware must change. Contact the factory
the tre file for this board
31 IOCompatCode mismatch. Firmware: [ ]; Tre: [ ] A tre file has been installed that is incompatible with
The I/O compatibility code that the firmware is the firmware on the I/O board. Either the tre file or
expecting is different than what is in the tre file for firmware must change. Contact the factory
this board
32-65 Analog input [ ] unhealthy Excitation to transducer, bad transducer, open or
short-circuit
66-69 Output [ ] individual current too high relative to Board failure
total current. An individual current is N mA more
than half the total current, where N is the
configurable TMR_Diff Limit
70-73 Output [ ] total current varies from reference Board failure or open circuit
current. Total current is N mA different than the
reference current, where N is the configurable
TMR_Diff Limit
74-77 Output [ ] reference current error. Board failure (D/A converter)
The difference between the output reference and
the input feedback of the output reference is
greater than the configured DA_Err Limit
measured in percent
78-81 Output [ ] individual current unhealthy. Simplex Board failure
mode only alarm if current out of bounds
82-85 Output [ ] suicide relay non-functional. The Board failure (relay or driver)
shutdown relay is not responding to commands
86-89 Output [ ] 20/200 mA selection non-functional. Configured output type does not match the jumper
feedback from the relay indicates incorrect 20/200 selection, or VAIC board failure (relay)
mA relay selection (not berg jumper selection)
90-93 Output [ ] 20/20 mA suicide active. One output of Board failure
the three has suicided, the other two boards have
picked up current
94 J3 terminal board and configuration incompatible
95 J4 terminal board and configuration incompatible
128-223 Logic Signal [ ] voting mismatch. The identified A problem with the input. This could be the device,
signal from this board disagrees with the voted the wire to the terminal board, the terminal board, or
value the cable
224-249 Input Signal # voting mismatch, Local [ ], Voted [ ]. A problem with the input. This could be the device,
The specified input signal varies from the voted the wire to the terminal board, the terminal board, or
value of the signal by more than the TMR Diff Limit the cable
212
TBAI Analog Input/Output
The Analog Input/Output (TBAI) terminal board supports 10 analog inputs and 2
outputs. The 10 analog inputs accommodate two-wire, three-wire, four-wire, or
externally powered transmitters. The analog outputs can be set up for 0-20 mA or 0-
200 mA current. Inputs and outputs have noise suppression circuitry to protect
against surge and high frequency noise.
TBAI has three DC-37 pin connectors provided on TBAI for connection to the I/O
processors. Simplex applications are supported using a single connector (JR1). TMR
applications are supported using all three connectors.
In TMR applications, the input signals are fanned to the three connectors for the R,
S, and T controls. TMR outputs combine the current of the three connected output
drivers and determine the total current with a measuring shunt. TBAI then presents
the total current signal to the I/O processors for regulation to the commanded
setpoint.
Mark VI Systems
In the Mark* VI system, TBAI works with VAIC processor and supports simplex
and TMR applications. One or two TBAIs can be connected to the VAIC. In TMR
systems, TBAI is cabled to three VAIC boards.
Mark VIe Systems
In the Mark VIe system, TBAI works with the PAIC I/O pack and supports simplex
and TMR applications. In TMR systems, three PAICs plug directly into the TBAI.
GEH-6421M
x
x
x 1
JT1
x 2
x 4
x 3
x 6
x 5
x 8
x 7
x 10
x 9
x 12
x 11
x 14
x 13 J ports conections:
x 16
x 15
x 18
x 17 Plug in PAIC I/O Pack
10 Analog Inputs x 20
x 19 JS1 for Mark VIe system
2 Analog Outputs x 22
x 21
x 24
x 23
x
or
x Cables to VAIC boards

x 26
x 25 for Mark VI system;
x 28
x 27
30
x 29
x
x 31
The number and location
x 32 JR1 depends on the level of
x 34
x 33
x 35 redundancy required.
x 36
x 38
x 37
x 40
x 39
x 42
x 41
x 44
x 43
x 46
x 45
x 48
x 47
x
x
Shield bar Barrier type terminal

blocks can be unplugged
from board for maintenance
TBAI Input Terminal board
Installation
Connect the input and output wires directly to two I/O terminal blocks mounted on
the terminal board. Each block is held down with two screws and has 24 terminals
accepting up to #12 AWG wires. A shield terminal attachment point is located
adjacent to each terminal block.
TBAI can accommodate the following analog I/O types:
• Analog input, two-wire transmitter

• Analog input, three-wire transmitter
• Analog input, four-wire transmitter
• Analog input, externally powered transmitter
• Analog input, voltage ±5 V, ±10 V dc
• Analog output, 0-20 mA
• Analog output, 0-200 mA
214
The following diagram shows the wiring connections, jumper positions, and cable
connections for TBAI.
Board Jumpers
Analog Input Terminal Board TBAI JT1
Circuit Jumpers
20mA/V dc Open/Ret
x
x 1 Input 1 (24V) Input 1 J1A J1B
Input 1 (20ma) x 2
x 3 Input 1 ( Vdc)
Input 1 (Ret) x 4
Input 2 (20ma) x 6
Input 2 (Ret)
x 7 Input 2 ( Vdc)
x 8
Input 3 (20ma) x 10
x 11 Input 3 ( Vdc)
Input 3 (Ret) x 12
Input 4 (20ma) x 14
x 15 Input 4 ( Vdc)
Input 4 (Ret) x 16
x 17 Input 5 (24V) Input 5 J5A J5B JS1 J ports connections:
Input 5 (20ma) x 18
x 19 Input 5 ( Vdc)
Input 5 (Ret) x 20
Input 6 (20ma) x 22 Plug in PAIC I/O Pack
x 23 Input 6 ( Vdc) for Mark VIe
Input 6 (Ret) x 24
x or
Cable(s) to VAIC
board(s) for Mark VI;
x
Input 7 (20ma) x 26 The number and location
Input 7 (Ret)
x 27 Input 7 ( Vdc)
x 28 depends on the level of
Input 8 (20ma)
x 31 Input 8 ( Vdc) 20mA/1 mA Open/Ret
Input 8 (Ret) x 32 JR1
Input 9 (20ma)
x 34
Input 9 (Ret)
x 35 Input 9 (1ma)
x 36
Input 10 (20ma)
x 38
x 39 Input 10 (1ma)
Input 10 (Ret) x 40
PCOM
x 41 PCOM
x 42
x 43 PCOM 20mA/200mA
PCOM x 44
x 45 Output 1 ( Sig) Output 1 J0
Output 1 (Ret) x 46
Output 2 (Ret)
x 47 Output 2 ( Sig) Output 2 No Jumper (0-20mA)
x 48
x
Two-wire +24 V dc Three-wire +24 V dc

transmitter transmitter wiring
wiring 4-20mA Voltage input VDC J#A 4-20 mA Voltage input VDC J#A
T
4-20 ma 20 ma 4-20 ma 20 ma
T
Return Return
Open J#B Open J#B
PCOM
Externally powered +24 V dc Four-wire +24 V dc

transmitter wiring transmitter wiring
J#A
4-20 mA Voltage input VDC J#A 5 V dc Voltage input VDC
4-20 ma 20 ma T 4-20 ma 20 ma
+ +
Power
T Return Signal Return
Supply - -
Open J#B Max. common Open J#B
mode voltage Misc return PCOM
is 7.0 V dc to PCOM
PCOM
TBAI Terminal Board Wiring
Operation
TBAI provides a 24 V dc power source for all the transducers. The inputs can be
configured as current or voltage inputs using jumpers (J#A and J#B). One of the two
analog output circuits is 4-20 mA and the other can be configured as 4-20 mA or 0-
200 mA. The following table displays the analog I/O capacity of TBAI.
GEH-6421M
Quantity Analog Input Types Quantity Analog Output Types
8 ±10 V dc, or ±5 V dc, or 4-20 mA 1 0-20 mA or 0-200 mA
2 4-20 mA, or ±1 mA 1 0-20 mA
Note With the noise suppression and filtering, the input ac CMR is 60 dB, and the
dc CMR is 80 dB.
Each 24 V dc power output is rated to deliver 21 mA continuously and is protected

against operation into a short circuit. Transmitters/transducers can be powered by the
24 V dc source in the control system, or can be independently powered. Jumper JO
selects the type of current output. Diagnostics monitor each output and a suicide
relay in the I/O controller disconnects the corresponding output if a fault cannot be
cleared by a command from the processor.
Terminal Board TBAI
8 circuits per I/O CONTROLLER

terminal board
Application Software
SYSTEM Noise
POWERED Suppr-
ession
+24 V dc P28V
Current Limit
+/-5,10 Vdc Vdc J#A

T N
4-20 ma S 20 ma
250 ohms
Return
J#B
Open Return R
PROCESSOR
PCOM
2 circuits per
termination board
A/D D/A
P28V
+24 V dc Current Limit Excitation
1 ma J#A JR1
+/-1 ma N
S 20 ma
4-20 ma 250
ohm 5k ohms
Return
J#B
Return
Open
Current
Regulator/
Two output circuits
Jump select on one Power Supply
circuit only; #2 Circuit 200 ma
is 4-20 ma only
JO
Signal 20 ma
N
S
Return
ID
SCOM
Simplex Analog Inputs and Outputs
216
In a TMR system, analog inputs fan out to the three I/O controllers (VAIC or PAIC).
The 24 V dc power to the transducers comes from all three controllers and is diode
shared on TBAI. Each analog current output is fed by currents from all three
controllers. The actual output current is measured with a series resistor, which feeds
a voltage back to each I/O controller. The resulting output is the voted middle value
(median) of the three currents. The following figure shows TBAI in a TMR system.
I/O CONTROLLER
Terminal Board TBAI
8 circuits per Application Software
Terminal board
SYSTEM Noise
POWERED Suppr-
P28V<T>
ession P28VR P28V<S>
+24 V dc Current Limit
+/-5,10 Vdc Vdc J#A

T N
4-20 ma S 20 ma
250 ohms
Return
J#B
Open Return
R
PCOM PROCESSOR
2 circuits per
terminal board A/D D/A
P28VR
+24 Vdc Current Limit Excitation
1 ma J#A JR1
+/-1 ma N
4-20 ma S 20 ma
250
ohm 5k ohms
Return
J#B
Open Return
PCOM S ID Current
T Regulator/
Two output circuits, JO Power Supply
#2 circuit is 4-20 200 ma
mA only
Signal 20 ma
N S JS1
S T
Return
To S PROCESSOR
SCOM
ID
JT1
To T PROCESSOR
ID
Analog Inputs and Outputs, TMR
GEH-6421M
Specifications
Item Specification
Number of channels 12 channels (10 AI, 2 AO)
Input span, transmitters 1-5 V dc from 4-20 mA current input
Outputs 24 V outputs provide 21 mA each connection
Maximum lead resistance 15 Ω maximum two-way cable resistance, cable length up to 300 m (984 ft)
Output load 500 Ω for 4-20 mA output, TBAIH1B with VAICH1C
800 Ω for 4-20 mA output, TBAIH1C with VAICH1D
800 Ω for 4-20 mA output, TBAIH1C with PAIC
50 Ω for 200 mA
Physical
Fault detection Monitor total output current
Check connector ID chip for hardware incompatibility
Temperature -30 to 65ºC (-22 to +149 ºF)
Size 10.16 cm wide x 33.02 cm high ( 4.0 in x 13 in)
Diagnostics
Diagnostic tests are made on the terminal board as follows:
• The board provides the voltage drop across a series resistor to indicate the output
current. The I/O processor creates a diagnostic alarm (fault) if any one of the
two outputs goes unhealthy.
• Each cable connector on the terminal board has its own ID device that is
interrogated by the I/O controller. The ID device is a read-only chip coded with
the terminal board serial number, board type, revision number, and the JR, JS,
JT connector location. When this chip is read by the I/O controller and a
mismatch is encountered, a hardware incompatibility fault is created.
Configuration
The terminal board is configured by jumpers. For the location of these jumpers, refer
to the installation diagram. The jumper choices are as follows:
• Jumpers J1A through J8A select either current input or voltage input.
• Jumpers J1B through J8B select whether the return is connected to common or
is left open.
• Jumpers J9A and J10A select either 1 mA or 20 mA input current.
• Jumpers J9B and J10B select whether the return is connected to common or is
left open.
• Jumper J0 sets output 1 to either 20 mA or 200 mA.
218
Notes
219 of 1016
VAOC Analog Output
VAOC Analog Output
The Analog Output (VAOC) board controls 16 analog, 20 mA outputs. Outputs are
wired to analog output terminal board(s) (TBAO or DTAO). Cables with molded
plugs connect the terminal board to the VME rack where the VAOC processor board
is located. VAOC receives digital values from the controller over the VME
backplane from the VCMI, converts these to analog output currents, and sends them
to the terminal board. The actual output current is measured on the terminal board
and fed back to VAOC where it is controlled.
In triple modular redundant (TMR) applications, control signals are fanned to the
same terminal board from three VME board racks R, S, and T, as shown in the
following figure. Six cables are required to support all 16 outputs. Each final current
output is the median selection of the three currents in the three VAOCs. This median
select circuit is in each VAOC.
VME Rack R x
VAOC Board
RUN
FAIL
STAT
TBAO Terminal Board
x JT1 JT2 VME bus to VCMI

x x
x x
x x
x x
x x
x x
x x
x x Cables to VME
x x
x x JS1 JS2 Rack T
x x
x x
x
x
x x
x x
x x
x
Cables to VME
x
x JR1 JR2 Rack S VAOC
x
x x x
x x
x x
x x
x x J3
x x
x x
x
J4
VAOC Board, TBAO Terminal Board, and Cabling
220
Volume II VAOC Analog Output • 97
Compatibility
There are two generations of the VAOC board with corresponding terminal boards.
The original VAOC includes all versions prior to and including VAOCH1B. When
driving 20 mA outputs, these boards support up to a 500 Ω load resistance at the end
of 1000 ft (304.8 m) of #18 wire. This generation requires terminal board TBAOH1B
or earlier for proper operation, or any revision of DTAI.
The newest VAOC board, VAOCH1C, and any subsequent releases, support higher
load resistance on the first eight output circuits. For 20 mA outputs, a drive voltage
up to 18 V is available at the terminal board screw terminals. This permits operation
with a 800 Ω load resistance with 1000 ft (304.8 m) of #18 wire with margin. The
second set of eight output circuits retains the 500 Ω rating of the original VAOC.
VAOCH1C requires TBAOH1C or later.
Installation
1 Power down the VME I/O processor rack

its edge connectors
4 Power up the VME rack and check the diagnostic lights at the top of the front
panel
connectors to secure the cables.
98 • VAOC Analog Output 221 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Operation
VAOC supports 16 analog 0-20 mA outputs. The VAOC contains the D/A converter
and driver that generates the controlled currents, as shown in the following figure.
The output current is measured by the voltage drop across a resistor on the terminal
board. Terminal board outputs have noise suppression circuitry to protect against
surge and high frequency noise. The following figure shows VAOC circuitry in a
simplex arrangement.
<R> Module
Analog Output Board VAOC TBAO Terminal Board Maximum load
Noise 4-20 mA, 500
Suicide
D/A Current suppr- ohms
100 Relay J3 JR1
Regulator/ ohms
ession 01
Signal
From Power Driver 50 ohms
NS Circuit #1
controller 02 Return
Sensing
Current 03 Signal
04 Return Circuit #2
Sensing 05 Signal
Output Current
07 Signal
First group of 8 analog 0-20 mA outputs Group 1 09 Signal
ID 11 Signal
13 Signal
15 Signal
Suicide
D/A Current 16 Return Circuit #8
100 Relay J4 JR2
Regulator/ ohms 17 Signal
From Power Driver 50 ohms NS 18 Return Circuit #9
controller 19 Signal
Current Sensing
21 Signal
22 Circuit #11
Output Current Sensing
Return
23 Signal
25 Signal
Second group of 8 analog 0-20 mA outputs Group 2 26 Circuit #13
Return
27 Signal
ID 28 Circuit #14
Return
29 Signal
31 Signal
Connectors at bottom 32 Return Circuit #16

of VME rack
Analog Output Current Circuits, Simplex System
In a TMR system, each analog current output is fed by the sum of the currents from
the three VAOCs. The total output current is measured with a series resistor that
feeds a voltage back to each VAOC. The resulting output is the voted middle value
(median) of the three currents. If one output fails, the other two pick up the current to
the correct value. In the event of a circuit malfunction that cannot be cleared by a
command from the processor, the circuit is disconnected by opening the shutdown
relay contacts. This isolation function is only operational when configured for TMR
operation.
222
Specifications
Item Specification
Number of channels 16 current output channels, single ended (one side connected to common)
Analog outputs 0-20 mA, with up to 500 Ω burden
Response better than 50 rad/sec
D/A converter resolution/accuracy 12 bit resolution with 0.5% accuracy
Frame rate 100 Hz on all 16 outputs
Fault detection Output current out of limits
Outer total (TMR) current
D/A converter output
Suicide relay operation
Failed ID chip
Diagnostics
Three LEDs at the top of the I/O board front panel provide status information. The
shows STATUS and is normally off but displays a steady orange if a diagnostic
alarm condition exists in the board. The diagnostics include the following:
• Each output is monitored by diagnostics. Voltage drops across the local and
outer loop current sense resistors, the D/A outputs, and at the shutdown relay
contacts are sampled and digitized.
• Standard diagnostic information is available on the outputs, including high and
low limit checks, and high and low system limit checks (configurable). If any
one of the outputs goes unhealthy a composite diagnostic alarm, L3DIAG_xxxx,
occurs. Details of the individual diagnostics are available from the toolbox. The
diagnostic signals can be individually latched, and then reset with the
RESET_DIA signal if they go healthy.
interrogated by the I/O processor. The ID device is a read-only chip coded with
and JT connector location. When the ID chip is read by the I/O processor and a
GEH-6421M
Configuration
Note The following information is extracted from the toolbox and represents a
sample of the configuration information for this board. Refer to the actual
configuration file within the toolbox for specific information.

VAOC Configuration
Output Voting Select type of output voting Simplex, Simplex TMR
J3:IS200TBAOH1A Terminal board connected to VAOC through J3 Connected, not connected
AnalogOut1 Analog output 1 board point (first set of 8 analog outputs) Point edit (output FLOAT)
Output_MA Type of output current Unused, 0-20 mA
Low_MA Output mA at low value 0 to 20 mA
Low_Value Output in engineering units at low mA -3.4028e + 038 to 3.4028e + 038
High_MA Output mA at high value 0 to 20 mA
High_Value Output value in engineering units at high mA -3.4028e + 038 to 3.4028e + 038
TMR_ Suicide Enable suicide for faulty output current, TMR only Enable, disable
TMR_Diff Limit Current difference in mA for suicide, TMR only 0 to 20 mA
D/A_Err Limit Difference between D/A reference and output, in % for 0 to 100 %
suicide, TMR only
J4:IS200TBAOH1A Terminal board connected to VAOC though J4 Connected, not connected
AnalogOut9 Analog output 9 - board point (second set of 8 analog Point edit (output FLOAT)
outputs)
Board Points Signals Description - Point Edit (Enter Signal Connection) Direction Type
L3DIAG_VAOC1 Board diagnostic Input BIT
L3DIAG_VAOC2 Board diagnostic Input BIT
L3DIAG_VAOC3 Status of suicide relay for output 1 Input BIT
OutSuicide1 Input BIT
: : Input BIT
Out1MA Measure total output current in mA Input Float
: : Input Float
Out16MA Measure total output current in mA Input Float
224
Alarms
online)
3 CRC failure override is active Board firmware programming error (board is allowed to
go online)
24 Firmware/hardware Incompatibility Invalid terminal board connected to VME I/O board
30 ConfigCompatCode mismatch; Firmware: [ ]; Tre: A tre file has been installed that is incompatible with the
[ ]The configuration compatibility code that the firmware on the I/O board. Either the tre file or firmware
firmware is expecting is different than what is in the must change. Contact the factory
tre file for this board
31 IOCompatCode mismatch; Firmware: [ ]; Tre: [ ]The A tre file has been installed that is incompatible with the
I/O compatibility code that the firmware is expecting firmware on the I/O board. Either the tre file or firmware
is different than what is in the tre file for this board must change. Contact the factory
82-97 Output [ ] Total current too high relative to total Board failure
current. An individual current is N mA more than
half the total current, where N is the configurable
TMR_Diff Limit
98-113 Output [ ] Total current varies from reference Board failure or open circuit
current. Total current is N mA different than the
reference current, where N is the configurable
TMR_Diff Limit
114-129 Output [ ] Reference Current Error. The difference Board failure (D/A converter)
between the output reference and the input
feedback of the output reference is greater than the
configured DA_Err Limit measured in percent
130-145 Output [ ] Individual Current Unhealthy. Simplex Board failure
mode alarm indicating current is too high or too low
146-161 Output [ ] Suicide Relay Non-Functional. The Board failure (relay or driver)
suicide relay is not responding to commands
162-177 Output [ ] Suicide Active. One output of three has Board failure
suicided, the other two boards have picked up the
current
GEH-6421M
TBAO Analog Output
The Analog Output (TBAO) terminal board supports 16 analog outputs with a
current range of 0-20 mA. Current outputs are generated by the I/O processor, which
can be local (Mark* VIe control) or remote (Mark VI control). The outputs have
noise suppression circuitry to protect against surge and high-frequency noise. TBAO
has two barrier-type terminal blocks for customer wiring and six D-type cable
connectors.
Mark VI Systems
In Mark VI systems, TBAO works with VAOC processor and supports simplex and
TMR applications. Cables with molded plugs connect TBAO to the VME rack where
the VAOC board is located. In TMR systems, TBAO is cabled to three VOAC
boards.
Mark VIe Systems
In Mark VIe systems, TBAO works with the PAOC I/O pack and supports simplex
applications only. The I/O packs plug into the D-type connectors and communicate
over Ethernet with the controller.
Refer to GEI-100577 Mark VIe Analog Input for board compatibility.
x DC-37 pin connectors

x
x 2 x 1 JT1 JT2 with latching fasteners
4 x 3
Eight Analog x
x 5
x 6
Outputs x 8 x 7
x 10 x 9
x 12 x 11
x 14 x 13 J ports conections:
x 16
x 15
x 18 x 17 Plug in PAOC I/O Pack(s)
x 20 x 19 JS1 JS2 for Mark VIe system
x 22 x 21
x 24 x 23 or
x
Cables to VAOC I/O boards
x for Mark VI;
x 26 x 25
28 x 27
Eight Analog x
x 29 The number and location depends
Outputs x 30
x 32
x 31 on the level of redundancy required.
x 33 JR1 JR2
x 34
x 36 x 35
x 38 x 37
x 40
x 39
x 42
x 41
x 44 x 43
x 46 x 45
x 48 x 47
x
x
Barrier Type Terminal

Shield
Blocks can be unplugged
Bar
TBAO Analog Output Terminal Board
226
Installation
Attach TBAO to a vertical mounting plate. Connect the wires for the 16 analog
outputs directly to the two I/O terminal blocks mounted on the left of the board. Each
point can accept two 3.0 mm (#12AWG) wires with 300 V insulation per point using
spade or ring type lugs. Each block is held down with two screws and has 24
terminals. A shield terminal strip attached to chassis ground is located immediately
to the left of each terminal block. Make cable connections to TBAO follows:
• In Mark VI systems, connect cables with molded plugs to the D-type connectors
on the TBAO and to the VME rack where the VAOC processor is located. Use
two cables for simplex or six cables for TMR.
• In Mark VIe systems, plug the PAOC I/O packs directly into selected D-type
connectors. Special side mounting brackets support the packs.
The following figure shows details of TBAO wiring and cabling.
For Mark VIe

Analog Output Termination Board TBAO control, use I/O
JT1 JT2 Packs
x For Mark VI
Output 1 (Return) x
x 1 Output 1 (Signal) control, use
2
x 3 Output 2 (Signal) cables as
Output 2 (Return) x 4
Output 3 (Return) x x 5 Output 3 (Signal) follows:
6
x 7 Output 4 (Signal)
Output 4 (Return) x 8 To J4
Output 5 (Return) x
10 on I/O
Output 6 (Return) x 12 rack T
Output 8 (Return) x x 15 Output 8 (Signal)
16
x 17 Output 9 (Signal) JS1 JS2 To J3
Output 10(Return) x x 19 Output 10(Signal) on I/O
20
x 21 Output 11(Signal) rack T
Output 11(Return) x 22
Output 12(Return) x
x 23 Output 12(Signal)
24
x
x To J4
x 25 Output 13 (Signal) on I/O
Output 13(Return) x 26
Output 14(Return) x
x 27 Output 14 (Signal) rack S
28
Output 15(Return) x
30
Output 16(Return) x
x 31 Output 16 (Signal) To J3
32 JR1 JR2
x 33 on I/O
x 34
x 35 rack S
x 36
x 37
x 38
x 39
x 40
x 41
x 42
x 43
x 44
x 45 To J4
x 46
x 47 on I/O
x 48
x
rack R
To J3
on I/O
rack R
I/O Terminal block with barrier terminals
Terminal blocks can be unplugged from
terminal board for maintenance
Up to two #12 AWG wires per point with 300
volt insulation
TBAO Terminal Board Wiring
GEH-6421M
Operation
TBAO supports 16 analog control outputs. Driven devices should not exceed a
resistance of 500 Ω (900 Ω if using I/O packs) and can be located up to 300 m (984
ft) from the turbine control cabinet. The VAOC or PAOC contains the D/A converter
and drivers that generate the controlled currents. The output current is measured by
the voltage drop across a resistor on the terminal board.
Filters reduce high-frequency noise and suppress surge on each output near the point
of signal exit. The following figure shows TBAO in a simplex system.
TBAO Terminal Board

Noise
JR1 suppression
Current output 50 ohms 01 Signal
NS Circuit #1
02 Return
03 Signal
Current feedback 05 Signal
06 Circuit #3
Current feedback Return
07 Signal
return
09 Signal
Group 1
(8)
ID 11 Signal
To I/O
13 Signal
Processors
15 Signal
JR2 16 Return Circuit #8

50 ohms 17 Signal
NS 18 Return Circuit #9
19 Signal
21 Signal
23 Signal
25 Signal
Group 2
(8)
27 Signal
ID 28 Circuit #14
Return
29 Signal
31 Signal
Analog Outputs, Simplex
228
In a TMR system, each analog current output is fed by the sum of the currents from
the three I/O processors, as shown in the drawing below. The total output current is
measured with a series resistor that feeds a voltage back to each I/O processor. The
resulting output is the voted middle value (median) of the three currents.
TBAO Terminal Board

Noise
JR1 Suppression
Current output 50 ohms
01 Signal
NS Circuit #1
02 Return
03 Signal
Current feedback
05 Signal
Current feedback 06 Return Circuit #3
Return 07 Signal
ID 09
JS1 Group 1 Signal
(8) 10 Return Circuit #5

11 Signal
ID 13 Signal
To I/O processors JT1 15 Signal
ID
JR2 17 Signal
19 Signal
21 Signal
ID
JS2 23 Signal
Group 2 25 Signal
(8) 26 Circuit #13
Return
ID 27 Signal
To I/O processors 28 Circuit #14
JT2 Return
29 Signal
31 Signal
ID 32 Return Circuit #16
Analog Output, TMR
GEH-6421M
Specifications
Item Specification
Number of channels 16 current output channels, single-ended (one side connected to common)
Analog output current 0-20 mA
Customer load Up to 500 Ω burden with VOACH1B and TBAOH1B and 900 Ω burden (18 V compliance) with
resistance PAOC and TBAOH1C
Physical
Size 10.16 cm wide x 33.02 cm high (4.0 in x 13.0 in)
Temperature -30 to +65ºC (-22 to +149 ºF)
Diagnostics
Diagnostic tests are made on the terminal board as follows:
• The board provides the voltage drop across a series resistor to indicate the output
current. The I/O processor creates a diagnostic alarm (fault) if any one of the
two outputs goes unhealthy.
interrogated by the I/O controller. The ID device is a read-only chip coded with
JT connector location. When this chip is read by the I/O controller and a
Configuration
There are no jumpers or hardware settings on the board.
DTAO Simplex Analog Output

The Simplex Analog Output (DTAO) terminal board is a compact analog output
terminal board designed for DIN-rail mounting. DTAO has eight analog outputs
driven by the VAOC I/O board over a single cable. This board is designed for
simplex-only applications and only works with the VAOC. A single cable with 37-
pin D-type connector connects DTAO to the VAOC rack. This cable is identical to
those used on the larger TBAO terminal board. Two DTAO boards can be connected
to the VAOC for a total of 16 analog outputs.
Note The DTAO board does not work with the PAOC I/O pack.
The on-board circuits and noise suppression are the same as those on TBAO. High-
density Euro-block type terminal blocks are permanently mounted to the board, with
two screw connections for the ground connection (SCOM). An on-board ID chip
identifies the board to the VAOC for system diagnostic purposes.
230
VCCC/VCRC Discrete Input/Output
VCCC/VCRC Discrete Input/Output

Note VCRC is a single slot version of VCCC with the same functionality, but
contact input cables plug into the front of the board.
The Discrete Input/Output (VCCC) board with its associated daughterboard accepts
48 discrete inputs and controls 24 relay outputs from four terminal boards. VCCC is
a double width module and mounts in the VME I/O rack. This rack has two sets of
J3/J4 plugs for cables to the TBCI and TRLY terminal boards. VCRC is a narrower,
single slot board and can be used instead of the VCCC.
VCCC Board VCRC Board

x x
RUN RUN
FAIL FAIL
STAT STAT
VME bus to VCMI VME bus to VCMI
J33
J44
To Contact Input
boards (2)
VCCC VCRC
x x
Connectors on J3 J3 Connectors on J3
VME rack VME rack
J4 J4 J4
To Relay Output
boards (2) To Relay Output
boards (2)
To Contact Input
boards (2)
VCCC and VCRC Boards and Cable Connections
231
Volume II VCCC/VCRC Discrete Input/Output • 111
VCRC Option
The VCRC board has the same functionality as the VCCC board but takes up only
one VME slot because no daughter board is required. Two front panel connectors,
J33 and J44, accept the contact inputs from the TBCI terminal boards. Relay outputs
on TRLY use the J3 and J4 ports on the VME rack, the same as for VCCC. If
locating cables on the front panel is undesirable, VCCC can be used instead.
Note VCRC does not support the TICI contact voltage sensing board.
Installation

its edge connectors
panel
Cable connections to the terminal boards are made at the J3 and J4 connectors (right
hand set) on the lower portion of the VME rack. These are latching type connectors
to secure the cables. Cable connections to the TRLY terminal boards are made to the
left hand set of J3 and J4 connectors.
Note With the VCRC, both TBCI cables connect to J33 and J44 on the front panel,
not to connectors under the rack.
Operation
VCCC passes the input voltages through optical isolators and samples the signals at
the frame rate for control functions, and at 1 ms for sequence of events (SOE)
reporting. VCCC transfers the signals over the VME backplane to the VCMI, which
sends them to the controller. The contact input processing is shown in the figure,
VCCC and I/O Terminal Boards, Simplex System.
Contact Inputs
The first 24 dry contact inputs are wired to a contact input terminal board. A second
terminal board is required for inputs 25 - 48. Dc power is provided for the contacts.
Cables with molded plugs connect the terminal board to the VME rack where the
VCCC processor board is located.
High speed scanning and recording at 1 ms rate is available for inputs monitoring
important turbine variables. The SOE recorder reports all contact openings and
closures with a time resolution of 1 ms. Contact chatter and pulse widths down to 6
ms are reported.
The dry-contact inputs are powered from a floating 125 V dc (100 - 145 V dc)
supply (TBCIH1) or from a floating 24 V dc (18.5 – 32 V dc) supply (TBCIH2).
Filters reduce high frequency noise and suppress surge on each input near the point
of signal exit. Noise and contact bounce is filtered with a 4 ms filter. Ac voltage
rejection (50/60 Hz) is 60 V rms with 125 V dc excitation.
112 • VCCC/VCRC Discrete Input/Output 232 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
For triple modular redundant (TMR) applications, contact input voltages are fanned
out to three VME board racks R, S, and T through plugs JR1, JS1, and JT1. The
signals are processed by the three VCCCs and the results voted by the VCMI board
in each controller rack.
Relay Outputs
TRLYH1B holds 12 plug-in magnetic relays. The first six relay circuits can be
jumpers configured for either dry, Form-C contact outputs, or to drive external
solenoids. A standard 125 V dc or 115 V ac source, or an optional 24 V dc source,
with individual jumper selectable fuses and on-board suppression can be provided
for field solenoid power. The next five relays (7-11) are un-powered isolated Form-C
contacts. Output 12 is an isolated Form-C contact, used for special applications such
as ignition transformers.
Cables carry relay control signals and monitor feedback voltages between VCCC and
TRLY. Relay drivers, fuses, and jumpers are mounted on the relay board. Several
types of relay boards can be driven, including TRLY, DRLY, and SRLY.
The relay outputs have failsafe features so that when a cable is unplugged, the inputs
vote to de-energize the corresponding relays. Similarly, if communication with the
associated VME board is lost, the relays de-energize.
233
Terminal Board TBCI <R> Rack
Contact Input /Relay Output Board VCCC

JE1
(+) Floating
(-)
125 V dc Gate
or JE2 Total of 48 circuits:
24 V dc (+) Gate
(-) P5
JR1 J3A
Noise Gate
Suppr-
(+) ession
Gate
N
(-) S Ref.
Gate
Field Contact ID
(+)
N Gate
(-) S J4A Optical isolation
BCOM
Field Contact Gate
(+)
24 contact inputs
per board Total of 24 circuits:
Contact inputs from second
TBCI terminal board
Relay Terminal Board TRLY
NC
25
K# Powered Relay
or Dry J3
Com JA1 command
Contacts signals
26
NO
27 K# K# J4
JR1
P28V
K# Coil Relay
Driver
JS1
RD
To second relay terminal board
Monitor JT1
Connect JR1, JS1, and JT1
to 3 VCCCs in TMR system,
12 relay outputs per board and leave JA1 open
VCCC and I/O Terminal Boards, Simplex System
GEH-6421M
Specifications
Item Specification
Number of channels 48 dry contact voltage input channels (24 per terminal board)
24 relay output channels (12 relays per terminal board)
Input contact excitation H1 – nominal 125 V dc, floating, ranging from 100 to 145 V dc
voltage H2 – nominal 24 V dc, floating, ranging from 18.5 to 32 V dc
Input isolation Optical isolation to 1500 V on all inputs
Input filter Hardware filter, 4 ms
Ac voltage rejection 60 V rms @ 50/60 Hz at 125 V dc excitation
Input frame rate System dependent scan rate for control purposes
1,000 Hz scan rate for SOE monitoring
Rated voltage on relays a: Nominal 125 V dc or 24 V dc
b: Nominal 120 V ac or 240 V ac
Max relay load current a: 0.6 A for 125 V dc operation
b: 3.0 A for 24 V dc operation
c: 3.0 A for 120/240 V ac, 50/60 Hz operation
Max response time on 25 ms
Max response time off 25 ms
Relay contact material Silver cad-oxide
Relay contact life Electrical operations: 100,000
Mechanical operations: 10,000,000
Fault detection Loss of contact input excitation voltage
Non-responding contact input in test mode
Loss of user solenoid power (blown fuse)
Coil current disagreement with command
Relay contact voltage monitoring indicates problem
Unplugged cable or loss of communication with I/O board; relays de-energize if
communication with associated I/O board is lost
Failed ID chip
Physical
Size - VCRC 26.04 cm high x 1.99 cm wide x 18.73 cm deep (10.25 in x 0.782 in x 7.375 in)
- VCCC 26.04 cm high x 3.98 cm wide x 18.73 cm deep (10.25 in x 1.564 in x 7.375 in)
Temperature 0 to 60ºC (32 to 140 ºF)
235
Diagnostics
Three LEDs at the top of the I/O board front panel provide status information. The
shows STATUS and is normally off but displays a steady orange if a diagnostic
alarm condition exists in the board. The diagnostics include the following:
• Each output is monitored by diagnostics. Voltage drops across the local and
outer loop current sense resistors, the D/A outputs, and at the shutdown relay
contacts are sampled and digitized.
• Standard diagnostic information is available on the outputs, including high and
low limit checks, and high and low system limit checks (configurable). If any
one of the outputs goes unhealthy a composite diagnostic alarm, L3DIAG_xxxx,
occurs. Details of the individual diagnostics are available from the toolbox. The
RESET_DIA signal if they go healthy.
and JT connector location. When the ID chip is read by the I/O processor and a
Configuration

Configuration
System Limits Enable all system limit checking Enable, disable
J3:IC200TRLYH1B Terminal board 1 connected to VCCC through J3 Connected, not connected
Relay01 First relay output (from first set of 12 relays) Point edit (Output BIT)
- card point
Relay Output Select relay output Used, unused
FuseDiag Enable fuse diagnostic Enable, disable
Relay01Fdbk Relay 01 contact voltage (first set of 12 relays) Point edit (Input BIT)
- card point
ContactInput Configurable Item:slot# Used, unused
SignalInvert Inversion makes signal true if contact is open Normal, invert
SignalFilter Contact Input filter in msec 0, 10, 20, 50
J4:IC200TRLYH1B Terminal board 2 connected to VCCC through J4 Connected, not connected
Relay01 Relay output 1 (second set of 12 relays) Point edit (Output BIT)
- card point
Relay01Fdbk Relay 1 contact voltage (second set of 12 relays) Point edit (Input BIT)
- card point
J3A:IS200TBCIH1A Terminal board connected to VCCC from J3 Connected, not connected
Contact01 First contact of 24 on first terminal board - board point Point edit (input BIT)
Contact input Select contact input Used, unused
Signal invert Inversion makes signal true if contact open Normal, invert
Sequence of events Select input for sequence of events scanning Enable, disable
Signal filter Contact input filter in milliseconds 0, 10, 20, 50
J4A:IS200TBCIH1A Terminal board connected to VCCC from J4 Connected, not connected
GEH-6421M
Contact01 First contact of 24 on second terminal board Point edit (input BIT)
- board point
Board point Signals Description-Enter Signal Connection Name Direction Type
L3DIAG_VCCC1 Board diagnostic Input BIT
Alarms
1 SOE Overrun. Sequence of events data overrun Communication problem on IONet
online)
3 CRC failure override is active Board firmware programming error (board is allowed to
go online)
16 System limit checking is disabled. System limit System checking was disabled by configuration
checking has been disabled
22 J33/J3A ID failure Failed ID chip on connector J33 or J3A, or cable problem
23 J44/J4A ID failure Failed ID chip on connector J44 or J4A, or cable problem
24 Firmware/hardware incompatibility. The firmware on Invalid terminal board connected to VME I/O board.
this board cannot handle the terminal board it is Check the connections and call the factory.
connected to
30 ConfigCompatCode mismatch; Firmware: [ ] ; Tre: [ A tre file has been installed that is incompatible with the
] The configuration compatibility code that the firmware on the I/O board. Either the tre file or firmware
firmware is expecting is different than what is in the must change. Contact the factory.
tre file for this board
31 IOCompatCode mismatch; Firmware: [ ]; Tre: [ ] The A tre file has been installed that is incompatible with the
I/O compatibility code that the firmware is expecting firmware on the I/O board. Either the tre file or firmware
is different than what is in the tre file for this board must change. Contact the factory.
33-56/ TBCI J33/J3A/J44/J4A contact input [ ] not Normally a VCCC problem, or the battery reference
65-88 responding to Test Mode. A single contact or group voltage is missing to the TBCI terminal board, or a bad
of contacts could not be forced high or low during cable.
VCCC self-check
129-140/ TRLY J3/J4 relay output coil [ ] does not match The relay terminal board may not exist, or there may be a
145-156 requested state. A relay coil monitor shows that problem with this relay, or, if TMR, one VCCC may have
current is flowing or not flowing in the relay coil, so been out-voted by the other two VCCC boards.
the relay is not responding to VCCC commands
161-172/ TRLY J3/J4 relay driver [ ] does not match The relay terminal board may not exist and the relay is
177-188 requested state. The relay is not responding to still configured as used, or there may be a problem with
VCCC commands this relay driver.
97-102/ TRLY J3/J4 fuse [ ] blown. The fuse monitor The relay terminal board may not exist, or the jumpers
113-118 requires the jumpers to be set and to drive a load, are not set and there is no load, or the fuse is blown.
or it will not respond correctly
240/241 TBCI J3/J4 excitation voltage not valid, TBCI The contact input terminal board may not exist, or the
J33/J3A/J44/J4A contact inputs not valid. The contact excitation may not be on, or be unplugged, or the
VCCC monitors the excitation on all TBCI and DTCI excitation may be below the 125 V level.
boards, and the contact input requires this voltage
to operate properly
256-415 Logic signal voting mismatch. The identified signal A problem with the input. This could be the device, the
from this board disagrees with the voted value wire to the terminal board, the terminal board, or the
cable.
237
TBCI Contact Input with Group Isolation
The Contact Input with Group Isolation (TBCI) terminal board accepts 24 dry
contact inputs wired to two barrier-type terminal blocks. Dc power is wired to TBCI
for contact excitation. The contact inputs have noise suppression circuitry to protect
against surge and high-frequency noise.
Mark VI Systems
In the Mark* VI system, TBCI works with VTCC/VCRC and supports simplex and
TMR applications. Cables with molded plugs connect TBCI to VME rack where the
VCCC or VCRC processor board is located. Both board versions TBCIH_B and
TBCIH_C work correctly with Mark VI and are functionally identical.
Mark VIe Systems
In the Mark VIe system, the TBCI works with the PDIA I/O pack and supports
simplex, dual, and TMR applications. One, two, or three PDIAs can be plugged
directly into the TBCI. Mark VIe requires the C version of this board for correct
mechanical alignment of connector JT1 with I/O pack mechanical support.
Board Versions
Three versions of TBCI are available as follows:
Terminal Contact
Board Inputs Excitation Voltage
TBCIH1C 24 Nominal 125 V dc, floating, ranging from 100 to 145 V dc
GEH-6421M
x
x
JT1 DC-37 pin
x 2
x 1
x 3 connectors with
x 4
x 5 latching fasteners
x 6
12 Contact x 7 JE1 JE2
x 8
Inputs x 10
x 9
x 12
x 11
x 14
x 13
x 16
x 15 J - Port Connections:
x 17 Plug in PDIA I/O Pack(s)
x 18
x 19 JS1 for Mark VIe system
x 20
x 21
x 22
x 23
x 24 or
x
Cables to VCCC/VCRC
x boards for Mark VI;
x 26
x 25
x 28
x 27 The number and location
12 Contact x 30
x 32
Inputs x 33 JR1
x 34
x 36
x 35
x 37
x 38
x 39
x 40
x 41
x 42
x 43
x 44
x 45
x 46
x 47
x 48
x
x
Barrier Type Terminal

Shield Blocks can be unplugged
Bar from board for maintenance
TBCI Contact Input Terminal Board
Installation
Wiring
Connect the wires for the 24 dry contact inputs directly to two I/O terminal blocks on
the terminal board. These blocks are held down with two screws and can be
unplugged from the board for maintenance. Each block has 24 terminals accepting
up to #12 AWG wires. A shield terminal strip attached to chassis ground is located
immediately to the left of each terminal block.
Power Connection
Connect TBCI to the contact excitation voltage source using plugs JE1 and JE2, as
shown in following figure.
Cabling Connections
In a simplex system, connect TBCI to the I/O processor using connector JR1. In a
TMR system, connect TBCI to the I/O processors using connectors JR1, JS1, and
JT1. Cables or I/O packs are plugged in depending on the type of Mark VI or Mark
VIe system, and the level of redundancy.
239
Note For a Mark VIe system, the I/O packs plug into TBCI and attach to side-
mounting brackets. One or two Ethernet cables plug into the pack. Firmware may
need to be downloaded. Refer to GEH-6700, ToolboxST for Mark VIe Control.
Contact Input Terminal Board TBCI 1 1

JT1
x
3 3
x 1 Input 1 (Positive) JE1 JE2
Input 1 (Return) x 2
x 3 Input 2 (Positive)
Input 2 (Return) x 4 Contact Excitation
Input 3 (Return) x 6 Source, 125 Vdc
Input 4 (Return)
x 8
Input 5 (Return)
x 10
J - Port Connections:
Input 9 (Return)
x 18 JS1 Plug in PDIA I/O Pack(s)
Input 10(Return) x 20 for Mark VIe system
Input 11(Return) x 22
Input 12(Return) x 23 Input 12 (Positive) or
x 24
x
Cables to VCCC/VCRC
boards for Mark VI;
x
x 25 Input 13 (Positive) The number and location
x 27 Input 14 (Positive) depends on the level of
x 29 Input 15 (Positive) redundancy required.
Input 16 (Return) x 32 JR1
Input 20 (Return)
x 40
x 43 Input 22 (Positive) Inputs 22, 23, 24
Input 23 (Return) x 46 are 10 mA, all
Input 24 (Return) x 48 others are 2.5 mA
x
Terminal Blocks can be unplugged Up to two #12 AWG wires per

from terminal board for maintenance point with 300 volt insulation
TBCIH1C Terminal Board Wiring and Cabling
GEH-6421M
Operation
Filters reduce high-frequency noise and suppress surge on each input near the point
of signal entry. The dry contact inputs on H1 are powered from a floating 125 V dc
(100-145 V dc) supply from the turbine control. The 125 V dc bus is current limited
in the power distribution module prior to feeding each contact input. H2 and H3
versions use lower voltages as shown in the specification table.
The discrete input voltage signals pass to the I/O processor, which sends them
through optical isolators providing group isolation and transfers the signals to the
system controller. The reference voltage in the isolation circuits sets a transition
threshold that is equal to 50% of the applied floating power supply voltage. The
tracking is clamped to go no less than 13% of the nominal rated supply voltage to
force all contacts to indicate open when voltage dips below this level.
Terminal Board TBCIH1C
JE1 I/O Processor

(+) Floating
(-)
Gate
JE2
From 125 V dc (+) Gate
Power Source (-)
Total of 48 circuits
P5
JR1 Gate
Noise
Suppr-
(+) ession Gate
N
(-) S Ref.
ID Gate
Field Contact
(+) BCOM
N JS1 Gate
(-) S Optical Isolation
Field Contact
Gate
(+)
N
(-) S ID
BCOM
Field Contact
JT1
(+)
N
(-) S To I/O Processor
Field Contact
(+) ID
N
(-) S BCOM
Field Contact
(+)
N
(-) S
24 Contact Inputs per Terminal Board.
Field Contact
BCOM Each contact input terminates on one
point and is fanned to <R>, <S>, and <T>
Contact Input Circuits
A pair of terminal points is provided for each input, with one point (screw) providing
the positive dc source and the second point providing the return (input) to the board.
The current loading is 2.5 mA per point for the first 21 inputs on each terminal
board. The last three have a 10 mA load to support interface with remote solid-state
output electronics. Contact input circuitry is designed for NEMA Class G creepage
and clearance.
241
Specifications
Item Specification
Number of channels 24 contact voltage input channels
Excitation voltage H1: Nominal 125 V dc, floating, ranging from 100 to 145 V dc
H2: Nominal 24 V dc, floating, ranging from 18.5 to 32 V dc
H3: Nominal 48 V dc, floating, ranging from 32 to 64 V dc
Input current H1: For 125 V dc applications:
First 21 circuits draw 2.5 mA (50 kΩ)
Last three circuits draw 10 mA (12.5 kΩ)
H2: For 24 V dc applications:
First 21 circuits draw 2.5 mA (10 kΩ)
Last three circuits draw 9.9 mA (2.42 kΩ)
H3: For 48 V dc applications:
First 21 circuits draw 2.5 mA
Last three circuits draw 10 mA
Input filter Hardware filter, 4 ms
Power consumption 20.6 W on the terminal board
Temperature rating 0 to 60ºC (32 to 140 ºF)
Fault detection Loss of contact input excitation voltage
Non-responding contact input in test mode
Unplugged cable
Physical
Size 33.02 cm high x 10.16 cm wide (13.0 in. x 4.0 in)
Temperature Operating: -30 to 65ºC (-22 to 149 ºF)
Diagnostics
Diagnostic tests to components on the terminal boards are as follows:
• The excitation voltage is monitored. If the excitation drops to below 40% of the
nominal voltage, a diagnostic alarm is set and latched by the I/O pack/board.
• As a test, all inputs associated with this terminal board are forced to the open
contact (fail safe) state. Any input that fails the diagnostic test is forced to the
failsafe state and a fault is created.
• If the input from this board does not match the TMR voted value from all three
boards, a fault is created.
• Each terminal board connector has its own ID device that is interrogated by the
I/O pack/board. The connector ID is coded into a read-only chip containing the
board serial number, board type, revision number, and the JR1/JS1/JT1
connector location. When the chip is read by the controller and a mismatch is
encountered, a hardware incompatibility fault is created.
Configuration
GEH-6421M
TRLYH1B Relay Output with Coil Sensing
The Relay Output with coil sensing (TRLYH1B) terminal board holds 12 plug-in
magnetic relays. The first six relay circuits configured by jumpers for either dry,
Form-C contact outputs, or to drive external solenoids. A standard 125 V dc or
115/230 V ac source, or an optional 24 V dc source with individual jumper selectable
fuses and on-board suppression, can be provided for field solenoid power. The next
five relays (7-11) are unpowered isolated Form-C contacts. Output 12 is an isolated
Form-C contact, used for special applications such as ignition transformers.
Mark VI Systems
In Mark* VI systems, TRLY is controlled by the VCCC, VCRC, or VGEN board

and supports simplex and TMR applications. Cables with molded plugs connect the
terminal board to the VME rack where the I/O boards are mounted. Connector JA1 is
used on simplex systems, and connectors JR1, JS1, and JT1 are used for TMR
systems.
Mark VIe Systems
In the Mark VIe system, the TRLY works with the PDOA I/O pack and supports
simplex and TMR applications. PDOA plugs into the DC-37 pin connectors on the
terminal board. Connector JA1 is used on simplex systems, and connectors JR1, JS1,
and JT1 are used for TMR systems.
Solenoid
power
TB3 X
x JT1
x 2
x 1
JF1JF2
x 4
x 3
x 6
x 5
x 8
x 7
x 10
x 9
x 12
x 11
x 14
x 13
x 15 Fuses J - Port Connections:
x 16
x 18
x 17
20
x 19 JS1
x
x 21 Plug inPDOA I/O Pack(s)
12 Relay Outputs x 22 for Mark VIe system
x 24
x 23
x
or
x
x 26
x 25 Output Cables to VCCC/VCRC or VGEN
28
x 27 boards for Mark VI system
x
x 29
Relays
x 30
32
x 31 The number and location
x
x 33 JA1 JR1 depends on the level of
x 34
x 36
x 38
x 37
x 40
x 39
x 42
x 41
x 44
x 43
x 46
x 45
x 48
x 47
x x
Shield Barrier type terminal Solenoid

bar blocks can be unplugged power
TRLYH1B Relay Output Terminal Board
243
Installation
Connect the wires for the 12 relay outputs directly to two I/O terminal blocks on the
terminal board as shown in the figure, TRLYH1B Terminal Board Wiring. Each
block is held down with two screws and has 24 terminals accepting up to #12 AWG
wires. A shield terminal strip attached to chassis ground is located on to the left side
of each terminal block.
Connect the solenoid power for outputs 1-6 to JF1. JF2 can be used to daisy chain
power to other TRLYs. Alternatively, power can be wired directly to TB3 when
JF1/JF2 are not used. Connect power for the special solenoid, Output 12, to
connector JG1.
Jumpers JP1-JP6 are removed in the factory and shipped in a plastic bag. Re-install
the appropriate jumper if power to a field solenoid is required. Conduct individual
loop energization checks as per standard practices and install the jumpers as
required. For isolated contact applications, remove the fuses to ensure that
suppression leakage is removed from the power bus.
Note These jumpers are also for isolation of the monitor circuit when used on
isolated contact applications.
Alternate customer power wiring N125/24 V dc Power

Terminal 1 - Pos source
Terminal 2 - Neg P125/24 V dc
TB3 JF1 JF2

Relay Output Terminal Board x x x x 1 1
TRLYH1B
3 3
x
x 1 Output 01 (NC) - Relays +
Output 01 (COM) x 2
x 3 Output 01 (NO) FU1 Out 01 FU7 JP1
Output 01 (SOL) x 4
x 5 Output 02 (NC) -
Output 02 (COM) x 6 +
Output 02 (SOL)
x 7 Output 02 (NO)
x 8 FU2 Out 02 FU8 To
x 9 Output 03 (NC) JP2
Powered, Output 03 (COM) x 10 connectors
Output 03 (SOL)
x 11 Output 03 (NO) - +
fused x 12 JA1, JR1,
Output 04 (COM) 14
x 13 Output 04 (NC) FU3 Out 03 FU9 JP3
solenoids x
JS1, JT1
Output 04 (SOL) 16
x 15 Output 04 (NO) - +
form-C x
Output 05 (COM) x 17 Output 05 (NC) FU4 Out 04
x 18 FU10 JP4
Output 05 (SOL) x 19 Output 05 (NO)
x 20 - +
Output 06 (COM) x 21 Output 06 (NC)
x 22
Output 06 (SOL) x 24
x - +
FU6 Out 06 FU12 JP6
Fuses Fuses Jumper
Neg,return Pos, High choices:
x
power (JPx)
x 26 or dry
x 27 Output 07 (NO)
x 28 contact (dry)
Dry Output 08 (COM) x 30
x 29 Output 08 (NC)
contacts x 31 Output 08 (NO) To connectors JA1, JR1, JS1, JT1
x 32
form-C Output 09 (COM) x 33 Output 09 (NC)
x 34
x 36
x 35 Output 09 (NO)
Output 10 (COM) x 37 Output 10 (NC) Power to special circuit 12
x 38
x 40
x 39 Output 10 (NO)
x 41 Output 11 (NC) JG1 1 Customer power
Output 11 (COM) x 42
Special x 43 Output 11 (NO) 2
x 44
circuit, Output 12 (COM) x 45 Output 12 (NC)
x 46 3 Customer return
form-C, Output 12 (SOL)
x 47 Output 12 (NO)
x 48
ign. xfmr. x 4
JF1, JF2, and JG1 are power plugs
TRLYH1B Terminal Board Wiring
GEH-6421M
Operation
Relay drivers, fuses, and jumpers are mounted on the TRLYH1B. For simplex
operation, D-type connectors carry control signals and monitor feedback voltages
between the I/O processors and TRLY through JA1.
Relays are driven at the frame rate and have a 3.0 A rating. The rated contact-to-
contact voltage is 500 V ac for one minute. The rated coil to contact voltage is 1,500
V ac for one minute. The typical time to operate is 10 ms. Relays 1-6 have a 250 V
metal oxide varistor (MOV) for transient suppression between normally open (NO)
and the power return terminals. The relay outputs have a failsafe feature that vote to
de-energize the corresponding relay when a cable is unplugged or communication
with the associated I/O processor is lost.
Output 01
Relay Terminal Board - TRLYH1B
NC 1
Alternate Dry K1
TB3
Power, 20 A FU7 Com 2
1 P125/24 V dc
24 V dc or
125 V dc or 2 JP1
115 V ac or 3 NO 3
230 V ac 4 +
K1 K1 Field
FU1 Solenoid
JF1 1 N125/24 Vdc Sol 4 -
Normal Power
Source,pluggable 3
3.15 Amp "6" of the above circuits
(7 Amp) slow-blow
JF2 Output 07
1
Power NC
3 Monitor
Daisy-Chain >14 Vdc 25
K7
>60 Vac
JA1 Com Dry
26
Contact,
Monitor Select
Form-C
NO
K7 K7 27
R
"5" of these circuits
I/O
Processor JR1
P28V
Relay Coil K#
Driver
Relay ID
Output JS1 RD
Output 12
Monitor
>14 Vdc NC
ID >60 Vac
K12 45
JT1
"12" of the above circuits
Com Special
46 Circuit
NO
ID 47
K12 K12
Available for JG1
GT Ignition Transformers 1 Sol
(6 Amp at 115 Vac
3 "1" of these circuits 48
3 Amp at 230 Vac)
TRLYH1B Circuits, Simplex System
245
For TMR applications, relay control signals are fanned into TRLY from the three I/O
processors R, S, and T through plugs JR1, JS1, and JT1. These signals are voted and
the result controls the corresponding relay driver. Power for the relay coils comes
from all three I/O processors and is diode-shared. The following figure shows a
TRLYH1B in a TMR system.
Relay Terminal Board - TRLYH1B Output 01

NC 1
Alternate Dry K1
TB3
power, 20 A 1 P125/24 V dc FU7 Com 2
24 V dc or
2 JP1
125 V dc or
3 NO 3
115 V ac or
230 V ac 4 +
K1 K1 Field
FU1 solenoid
JF1 1 N125/24 V dc Sol 4 -
Normal power
source,pluggable 3.15 Amp 6 of the above circuits
3
(7 Amp) slow-blow
JF2 Output 07
Power 1
NC
daisy-chain 3 Monitor
>14 V dc K7 25
>60 V ac
JA1 Com Dry
26 contact,
Monitor Select
form-C
R NO
I/O K7 K7 27
Processor 5 of these circuits
Relay JR1
P28V
Control
Relay
Coil K#
Driver
ID
RD
JS1
To S I/O Processor Output 12

Monitor
>14 V dc NC
ID >60 V ac
K12 45
JT1
12 of the above circuits
Com Special
To T I/O Processor 46 circuit
NO
ID 47
K12 K12
Available for JG1
GT ignition transformers 1 Sol
(6 Amp at 115 V ac 3 1 of these circuits 48
3 Amp at 230 V ac)
TRLYH1B Circuits, TMR System
GEH-6421M
Specifications
Item Specifications
Number of relay channels 12: 6 relays with optional solenoid driver voltages
on one TRLY board 5 relays with dry contacts only
1 relay with 7 A rating
b: Nominal 115/230 V ac
Max load current a: 0.6 A for 125 V dc operation
Max response time on 25 ms typical
Max response time off 25 ms typical
Maximum inrush current 10 A
Contact material Silver cad-oxide
Contact life Electrical operations: 100,000
Fault detection Loss of relay solenoid excitation current
Coil current disagreement with command
communication with associated I/O board is lost.
Physical
Temperature -30 to + 65ºC (-22 to +149 ºF)
Diagnostics
• The output of each relay (coil current) is monitored and checked against the
command at the frame rate. If there is no agreement for two consecutive checks,
an alarm is latched.
• The solenoid excitation voltage is monitored downstream of the fuses and an
alarm is latched if it falls below 12 V dc.
• If any one of the outputs goes unhealthy a composite diagnostics alarm,
L3DIAG_xxxx occurs.
• When an ID chip is read by the I/O processor and a mismatch is encountered, a
hardware incompatibility fault is created.
• Each terminal board connector has it own ID device that is interrogated by the
connector location. When the chip is read by the I/O processor and mismatch is
• Relay contact voltage is monitored.
• Details of the individual diagnostics are available in the configuration
application. The diagnostic signals can be individually latched, and then reset
with the RESET_DIA signal if they go healthy.
247
Configuration
Board adjustments are made as follows:
• Jumpers JP1 through JP12. If contact voltage sensing is required, insert jumpers
for selected relays.
• Fuses FU1 through FU12. If power is required for relays 1-6, two fuses should
be placed in each power circuit supplying those relays. For example, FU1 and
FU7 supply relay output 1. Refer to terminal board wiring diagram for more
information.
TRLYH1C Relay Output with Contact Sensing

The Relay Output with contact sensing (TRLYH1C) terminal board holds 12 plug-in
magnetic relays. The first six relay circuits are Form-C contact outputs to drive
external solenoids. A standard 125 V dc or 115 V ac source with fuses and on-board
suppression is provided for field solenoid power. TRLYH2C holds 12 plug-in
magnetic relays. The first six relay circuits are Form-C contact outputs to drive
external solenoids. A standard 24 V dc source with fuses and on-board suppression is
provided for field solenoid power.
The next five relays (7-11) are unpowered, isolated Form-C contacts. Output 12 is an
isolated Form-C contact with non-fused power supply, used for ignition
transformers. For example, 12 NO contacts have jumpers to apply or remove the
feedback voltage sensing.
TRLYH1C and H2C are the same as the standard TRLYH1B board except for the
following:
• Six jumpers for converting the solenoid outputs to dry contact type are removed.
These jumpers were associated with the fuse monitoring.
• Input relay coil monitoring is removed from the 12 relays.
• Relay contact voltage monitoring is added to the 12 relays. Individual
monitoring circuits have voltage suppression and can be isolated by removing
their associated jumper.
• High-frequency snubbers are installed across the NO and SOL terminals on the
six solenoid driver circuits and on the special circuit, output 12.
Mark VI Systems
In the Mark* VI system, the TRLY is controlled by the VCCC or VCRC board and
supports simplex and TMR applications. Cables with molded plugs connect the
systems.
GEH-6421M
Mark VIe Systems
In the Mark VIe system, TRLY works with the PDOA I/O pack and supports
Solenoid
power
TB3 X
x JT1
x 2
x 1
JF1JF2
x 4
x 3
x 6
x 5
x 8
x 7
x 10
x 9
x 12
x 11
x 14
x 13
x 15 Fuses J - Port Connections:
x 16
x 18
x 17
20
x 19 JS1
x
x 21 Plug in PDOA I/O Pack(s)
12 Relay Outputs x 22 for Mark VIe system
x 24
x 23
x
Output or
x Relays
x 26
x 25 Cables to VCCC/VCRC
28
x 27 boards for Mark VIe system
x
x 29
Jumpers
x 30
32
x 31
x
x 33 JA1 JR1 The number and location
x 36
x 35
x 38
x 40
x 39
x 42
x 41
x 44
x 43
x 46
x 45
x 48
x 47
x x
Shield Barrier type terminal Solenoid

bar blocks can be unplugged power
TRLYH1C Relay Output Terminal Board With Voltage Sensing
Installation
Connect the wires for the 12 relay outputs directly to two I/O terminal blocks on the
terminal board as shown in the figure, TRLYH1C Terminal Board Wiring. Each
wires. A shield terminal strip attached to chassis ground is located immediately to
the left of each terminal block.
Connect the solenoid power for outputs 1-6 to JF1 normally. JF2 can be used to
daisy-chain power to other TRLYs. Alternatively, power can be wired directly to
TB3 when JF1/JF2 are not used. Connect power for the special solenoid, Output 12,
to connector JG1.
249
Jumpers JP1-12 remove the voltage monitoring from selected outputs.
Alternative Customer Power N125/24 Vdc Power

Power Wiring Return Source
P125/24 Vdc
TB3 JF1 JF2

Relay Output Terminal Board x x x x 1 1
TRLYH1C (Contact Voltage Sensing)
4 3 2 1
3 3
x
x 1 Output 01 (NC) - +
Output 01 (COM) x 2
Output 01 (SOL) x 4
x 7 Output 02 (NO)
Output 02 (SOL) x 8 FU2 Out 02 FU8 JP2
x 9 Output 03 (NC)
Powered, - +
x 11 Output 03 (NO)
Fused
Output 04 (COM) 14
x 13 Output 04 (NC) FU3 Out 03 FU9 JP3
Solenoids x
Output 04 (SOL) 16
x 15 Output 04 (NO) - +
Form-C x
Voltage
Output 05 (COM) x 17 Output 05 (NC) FU4 Out 04 FU10
x 18 JP4 Sensing
x 20 - + Boards
x 22
x - +
FU6 Out 06 FU12 JP6
Fuses Fuses
Neg,Return Pos,High
x
Output 07 (NC) JP7 Cable
x 26 Connectors
x 27 Output 07 (NO)
x 28 JA1, JR1,
Dry Output 08 (COM) x 29 Output 08 (NC) JP8
x 30 JS1, JT1
Contacts x 31 Output 08 (NO) Relays
x 32
Form-C Output 09 (COM) x 33 Output 09 (NC)
x 34 JP9
x 36
x 35 Output 09 (NO)
x 38
x 39 Output 10 (NO) JP10
x 40
x 41 Output 11 (NC)
Special x 43 Output 11 (NO) JP11
x 44
Circuit, Output 12 (COM) x 45 Output 12 (NC)
x 46
Form-C, Output 12 (SOL)
x 47 Output 12 (NO) JP12
x 48
Ign. Xfmr. x
JG1 1 3
Customer Customer
Power Return
Power to Circuit 12
TRLYH1C Terminal Board Wiring
Operation
Relay drivers, fuses, and jumpers are mounted on the TRLYH1C. Relays 1-6 have a
250 V MOV for transient suppression between the NO and power return terminals.
Relays are driven at the frame rate and have a 3.0 A rating. The rated contact-to-
contact voltage is 500 V ac for one minute. The rated coil to contact voltage is 1,500
V ac for one minute. The typical time to operate is 10 ms. The relay outputs have a
failsafe feature that votes to de-energize the corresponding relay when a cable is
unplugged or communication with the associated I/O board is lost.
GEH-6421M
For simplex operation, a cable carries control signals and monitor feedback voltages
between the I/O board and TRLY through JA1. For TMR applications, relay control
signals are fanned into TRLY from the three I/O boards R, S, and T through plugs
JR1, JS1, and JT1. These signals are voted and the result controls the corresponding
relay driver. The 28 V power for the relay coils comes in from all three I/O boards
and is diode-shared. The following figure shows a TRLYH1C in a TMR system.
Relay Terminal Board - TRLYH1C Output 01

with Contact Voltage Sensing
NC 1
Alternate K1
TB3
Power, 20 A FU7 Com 2
1 P125/24 V dc
24 V dc or
2
125 V dc or
115 V ac or 3 NO 3
240 V ac 4 6 of these +
K1 K1 Field
circuits Snub
FU1 4
Solenoid
JF1 1 N125/24 Vdc -
Normal Power Sol
Source, pluggable 3.15 Amp
3 slow-blow JP1
(7 Amp)
JF2 Output 07
1
Power NC
3 Monitor
Daisy-Chain >14 Vdc 25
K7
>60 Vac
JA1 Com Dry
26
Contact
Monitor Select
Form-C
NO
R
K7 K7 27
I/O
Processor JP7
JR1
P28V
K#
5 of these circuits
Coil
Relay Relay
Driver
Control ID
JS1 RD
To S I/O Processor JP12 Output 12

Monitor
Voltage NC
ID
K12 45
JT1
12 of the above circuits
Com Special
To T I/O Processor
46 Circuit
NO
ID 47
K12 K12
Available for JG1 Snub
GT Ignition 1
Transformers 3
1 of these circuits Sol 48
(6 A at 120 V ac
3 A at 240 V ac)
TRLYH1C Circuits
251
Specifications
Item Specifications
Number of relay channels on one 12: Six relays with solenoid driver voltages
TRLY board Five relays with dry contacts only
One relay with 7 A rating
b: Nominal 120 V ac or 240 V ac
Max load current a: 0.6 A for 125 V dc operation
Max response time on 25 ms typical
H1C contact feedback threshold 70-145 V dc, nominal 125 V dc, threshold 45 to 65 V dc
90-132 V rms, nominal 115 V rms, 47-63 Hz, threshold 45 to 72 V ac
190-264 V rms, nominal 230 V rms, 47-63 Hz, threshold 45 to 72 V ac
H2C contact feedback threshold 16-32 V dc, nominal 24 V dc, threshold 10 to 16 V dc
Contact material Silver cad-oxide
Fault detection Loss of relay excitation current
NO contact voltage disagreement with command
communication with associated I/O board is lost
Physical
Temperature -30 to + 65ºC (-22 to 149 ºF)
Diagnostics
L3DIAG_xxxx occurs.
GEH-6421M
Configuration
Board adjustments are made as follows:
• Jumpers JP1 through JP12. If contact voltage sensing is required, insert jumpers
for selected relays.
• Fuses FU1 through FU12. If power is required for relays 1-6, two fuses should
be placed in each power circuit supplying those relays. For example, FU1 and
FU7 supply relay output 1. Refer to terminal board wiring diagram for more
information.
TRLYH1D Relay Output with Servo Integrity Sensing

The Relay Output with Solenoid Integrity Sensing (TRLYH1D) terminal board holds
six plug-in magnetic relays. The six relay circuits are Form-C contact outputs,
powered and fused to drive external solenoids. A standard 24 V dc or 125 V dc
source can be used. The board provides special feedback on each relay circuit to
detect a bad external solenoid. Sensing is applied between the NO output terminal
and the SOL output terminal.
TRLYH1D is similar to the standard TRLYH1B board except for the following:
• There are only six relays.
• The board is designed for 24/125 V dc applications only.
• Relay circuits have a NO contact in the return side as well as the source side.
• The relays cannot be configured for dry contact use.
• Input relay coil monitoring is removed.
• The terminal board provides monitoring of field solenoid integrity.
• There is no special-use relay for driving an ignition transformer.
Mark VI Systems
In the Mark* VI systems, the TRLY is controlled by the VCCC or VCRC board and
supports simplex and TMR applications. Cables with molded plugs connect the
systems.
Mark VIe Systems
In the Mark VIe systems, the TRLY works with the PDOA I/O pack and supports
253
Power,
Normal power source daisy chain
24/125 V dc (14 A) Alternate power
source (14 A)
Barrier type JF1 JF2 X
terminal x TB3 JT1
2
x 1
blocks can be x
x 3
unplugged x 4
x 6
x 5
from board for x 7
x 8
maintenance x 10
x 9
x 12
x 11
x 14
x 13
x 16
x 18
x 17
20
x 19 JS1
x
x 21 Plug in PDOA I/O Pack(s)
x 22 for Mark VIe system
6 Relay Outputs x 24
x 23
x
or
TB1
Fuses
Output Cables to VCCC/VCRC
Relays boards for Mark VI;
JA1 JR1 The number and location

depends on the level of
redundancy required.
Shield
bar x
TRLYH1D Relay Output Terminal Board
Installation
Connect the wires for the six relay outputs directly to the TB1 terminal block on the
terminal board as shown in the figure, TRLYH1D Terminal Board Wiring. The
wires. A shield terminal strip, attached to chassis ground, is located immediately to
the left of the terminal block.
GEH-6421M
Connect the solenoid power for outputs 1-6 to JF1. JF2 can be used to daisy-chain
power to other TRLYs. Alternatively, power can be wired directly to TB3 when
JF1/JF2 are not used.
N125/110/24 V dc Alternate customer

+ +
Power source power source
- -
JF1 JF2 TB3
Relay Output Terminal Board 1 1 x x x x
TRLYH1D
4 3 2 1 JT1
3 3
x
x 1 Output 01 (NC) - Relays +
Output 01 (COM) x 2
x 3 Output 01 (NO) FU1 Out 01 FU7
Output 01 (SOL) x 4
Output 02 (SOL)
x 7 Output 02 (NO)
x 8
x 9 Output 03 (NC) FU2 Out 02 FU8
x 11 Output 03 (NO) - + J - Port Connections:
x 13 Output 04 (NC) FU3 Out 03 FU9
x 15 Output 04 (NO) - + JS1 Plug in PDOA I/O Pack(s)
Output 05 (COM) x 17 Output 05 (NC) FU4 Out 04
x 18 FU10 for Mark VIe system
x 20 - +
x 22
FU5 Out 05 FU11 or
x 23 Output 06 (NO)
x - + Cables to VCCC/VCRC
FU6 Out 06 FU12 boards for Mark VI;
Fuses Fuses
Neg,return Pos, High The number and location
depends on the level of
Wiring to JA1 JR1 redundancy required.
six external
solenoids
TRLYH1D Terminal Board Wiring
255
Operation
The six relays have a MOV and clamp diode for transient suppression between the
NO and power return terminals. The relay outputs have a failsafe feature that votes to
de-energize the corresponding relay when a cable is unplugged or communication
with the associated I/O board is lost.
TRLYH1D monitors each solenoid between the NO and SOL output terminals.
When the relay is de-energized, the circuit applies a bias of less than 8% nominal
voltage to determine if the load impedance is within an allowable band. If the
impedance is too low or high for consecutive scans, an alarm feedback is generated.
The contacts must be open for at least 1.3 seconds to get a valid reading.
110 or 125 V dc Solenoid Voltage
Announce
Yes Unknown No Unknown Yes
Solenoid Failure?
(R_NOM = 644 Ω)
Solenoid Resistance 80 Ω 153 Ω 2.2 kΩ 2.2 kΩ
24 V dc Solenoid Voltage
Announce
Yes Unknown No Unknown Yes
Solenoid Failure?
(R_NOM = 29 Ω)
Solenoid Resistance 5Ω 11 Ω 148 Ω 153 Ω
TRLYH1D Solenoid Fault Announcement
GEH-6421M
For simplex operation, cables carry control signals and solenoid monitoring feedback
voltages between the I/O board and TRLY through JA1. For TMR applications, relay
control signals are fanned into TRLY from the three I/O processor boards R, S, and
T through plugs JR1, JS1, and JT1. These signals are voted and the result controls
the corresponding relay driver. Power for the relay coils comes in from all three I/O
boards and is diode-shared. The following figure shows TRLYH1D in a TMR
system.
Relay Terminal Board - TRLYH1D

Output 01
NC 1
Alternate power
TB3 K1
source (14 A) FU7
1 P125/24 V dc Com 2
2
3 NO 3
Normal power 4 +
source, pluggable K1 Field
FU1 4 solenoid
24 V dc or JF1 1 N125/24 V dc -
110 V dc or 3.15 Amp Sol
K1
125 V dc 3
slow-blow
(14 Amp) TB1
JF2
1
Power Monitor Solenoid
daisy-chain 3
>14 Vdc Integrity
>60 Vac Monitor 6 of the
JA1
Fuse Fdback above
R Monitor Select
I/O circuits
Processor
24 kHz from
Power Supply
Relay
Control JR1
P28V
Coil K#
Relay
Driver
ID
RD
JS1
To S I/O Processor 6 of the above circuits
ID
JT1
To T I/O Processor
ID
TRLYH1D Circuits, TMR System
257
Specifications
Item Specification
Number of relay channels Six relays with special customer solenoid monitoring
Rated voltage on relays Nominal 125 V dc or 24 V dc
Relay contact rating for 24 V dc Current rating 10 A, resistive
voltage Current rating 2 A, L/R = 7 ms, without suppression
Relay contact rating for 125 V dc Current rating 0.5 A, resistive
voltage Current rating 0.2 A, L/R = 7 ms, without suppression
Current rating 0.65 A, L/R = 150 ms, with suppression (MOV) across the load
Maximum response time on 25 ms typical
Maximum response time off 25 ms typical
Board size 17.8 cm by 33.0 cm (7 in by 13 in)
Fault detection Loss of solenoid voltage supply (fuse monitor)
Solenoid resistance measured to detect open and short circuits
Unplugged cable or loss of communication with I/O board (relays de-energize if
communication with associated I/O board is lost)
Physical
Temperature -30 to +65ºC (-22 to +149 ºF)
Diagnostics
L3DIAG_xxxx occurs.
Configuration
GEH-6421M
VCMI Bus Master Controller
VCMI Bus Master Controller
The VME Bus Master Controller (VCMI) board is the communication interface
between the controller and the I/O boards, and the communication interface to the
system control network, known as IONet. VCMI is also the VME bus master in the
control and I/O racks, and manages the IDs for all the boards in the rack and their
associated terminal boards. The two versions of the VCMI are shown in the
following figure:
VCMI H1 VCMI H2
x x
VCMI is OK
RUN Error or Power up Failure RUN

FAIL FAIL
STATUS STATUS
Pushbutton RESET
RESET
S S
E E
R R
I VME bus to I/O I VME bus to I/O
A A
boards and controller L
boards and controller
L
M
BE 8O
D
TX 4
U
RX 2L
CD 1E
M I
BE 8 O O IONet3 port
N
4 D
IONet node E 10Base2
2 U
L T
1 3
E
TX R
RX S
R Channel ID CD T
S I
T O IONet2 port
N
E 10Base2
Transmitting Packets T
TX Receiving Packets 2
RX Collisions on IONet TX
CD RX
CD
I I
O O
N N
E IONet port E IONet1 port
T T
1 10Base2 2 10Base2
x x
Communication Communication
board - 1 IONet board - 3 IONets
VCMI Boards, Single, and Triple Network Versions
259
Volume II VCMI Bus Master Controller • 165
Multiple I/O racks can be connected to the IONet, each rack with its own VCMI
board. The following figure shows three simplex system configurations with local
and remote I/O using the VCMI.
V U Simplex system with

C C I/O local I/O
M V Boards
I X
UCVX is controller
VCMI is bus master
I/O are VME boards
R0 R1 R2
V U V V
C C I/O C C I/O Simplex system with
I/O
M V Boards M Boards M Boards local & remote I/O
I X I I
IONet
Simplex System Configurations with Local and Remote I/O
166 • VCMI Bus Master Controller 260 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
The following figure shows two sizes of triple modular redundant (TMR) systems.
The first example is a small system where all the I/O is mounted in the VME control
rack so no remote I/O racks are required. Each channel (R, S, T) has its own IONet,
and the VCMI has three IONet ports.
The second example is a larger system with remote I/O racks. Each IONet supports
multiple I/O racks, but only one rack is shown here. All I/O channels (R, S, T) are
identical in terms of I/O boards and points.
R0 S0 T0 TMR system with

V U V U V U local I/O
C C I/O C C I/O C C I/O
M V Boards M V Boards M V Boards UCVX is controller
I X I X I X
VCMI is bus master
I/O are VME
IONet - R Termination boards
IONet - S not shown
IONet - T
R0 S0 T0 TMR system with

V U V U V U remote I/O,
C C C C C C Termination boards
M V M V M V not shown
I X I X I X
IONet - R
IONet - S
IONet - T
R1 S1 T1
V V V
C C C I/O IONet supports
I/O I/O
M Boards M Boards M Boards multiple remote
I I I I/O racks
TMR System Configurations with Local and Remote I/O
261
The VCMI card receives analog and digital feedback of power status through the
J301 backplane connector. J301 connections are as follows:
Backplane VCMI Hardware VCMI Software

J301 Pin Signal VCMI Signal Description Signal Space Signal Space Description
1 P28AA +28 V Power out
2 PCOM Power common
5 SG201C28 AIN4P Analog input 4 + Spare 02 Analog spare 02
6 SG201C27 AIN4N Analog input 4 - Spare 01 Analog spare 01
7 SG201C26 AIN3P Analog input 3 +
8 SG201C25 AIN3N Analog input 3 -
9 SG201C24 DINRET Digital input
Power common
10 SG201C23 DINPWROUT Digital input
Power output
11 SG201C22 DIN12 Digital input 12 Logic_In_12 Spare 05
16 SG201C17 DIN7 Digital input 7 Logic_In_7 Fuse 29, J17 Fault
17 PCOM Power common
18 P28AA +28 V Power out
19 SIGCOM02 SCOM-DCOM
JP2 Select
20 N28 -28 V Power out
21 PCOM Power common
26 SG201A26 AIN2P Analog input 2 + N125_Grd N125 with respect to ground
27 SG201A25 AIN2N Analog input 2 -
28 SG201A24 AIN1P Analog input 1 + P125_Grd P125 with respect to ground
29 SG201A23 AIN1N Analog input 1 -
30 SG201A22 DIN6 Digital input 6 Logic_In_6 Fuse 32, J20 Fault
31 SG201A21 DIN5 Digital input 5 Logic_In_5 Fuse 31, J19 Fault
32 SG201A20 DIN4 Digital input 4 Logic_In_4 Miscellaneous contact
33 SG201A19 DIN3 Digital input 3 Logic_In_3 AC2 source fault
34 SG201A18 DIN2 Digital input 2 Logic_In_2 AC1 source fault
35 SG201A17 DIN1 Digital input 1 Logic_In_1 Battery bus fault
36 SIGCOM01 SCOM-DCOM
JP1 Select
37 CBL301ID CBL301ID ID Cable signal
GEH-6421M
Specifications
Item Specification
Board Type 6U high VME board, 0.787 inch wide
Processor Texas Instruments TMS320C32 32-bit digital signal processor
Memory Dual-port memory, 32 Kbytes in 32-bit transfer configuration
SRAM, 256k x 32
Flash memory, 512k x 8-VCMIH_B; 4096K x 8-VCMIH_C
Communication H1 version: One IONet 10Base2 Ethernet port, BNC connector, 10 Mbits/sec
H2 version: Three IONet 10Base2 Ethernet ports, BNC connectors, 10 Mbits/sec
VME bus block transfers
1 RS-232C Serial port, D-style plug connector, 9600 (only)
Frame Rate 10 ms (100 Hz) for simplex
40 ms (25 Hz) for TMR
20 ms, 80 ms application dependent
Diagnostics
The internal +5 V, ±12 V, ±15 V, and ±28 V power supply buses are monitored and
alarmed. The alarm settings are configurable and usually set at 3.5%, except for the
28 V supplies, which are set at 5.5%.
Diagnostic signals from the power distribution module (PDM), connected through
J301, are also monitored. These include ground fault and over/under voltage on the
P125 V bus, two differential ±5V dc analog inputs, P28A and PCOM for external
monitor circuits, and digital inputs.
Configuration
VCMI Toolbox Configuration (Part 1 of 2)

Configuration
System Limits Enable or disable all system limits Enable, disable
PS_Limit1 ± Power supply limits for P5, P15, N15 in % 0 to 10

PS_Limit2 ± Power supply limits for P12, N12, P28, N28 in 0 to 10
percent
PwrBusLimits Enable or disable power bus diagnostics Enable, disable
125 vBusHlim High limit for 125 V dc bus in volts 0 to 150
125 vBusLlim Low limit for 125 V dc bus in volts 0 to 150
125 vBusGlim Low volts to ground limit for 125 V dc bus 0 to 150
(diagnostic)
J3 Power Monitor PDM monitor Connected, not connected
Logic_In_1 First of 12 logical inputs – board point signal Point edit (input BIT)
Logic_In Configurable item Used, unused
P125_Grd P125 with respect to ground – board point signal Point Edit (Input FLOAT)
Input Type Type of analog input Used, unused
Low_Input Input volts at low value -10 to +10
Low_Value Input value in engineering units at low MA -3.4082e+038 to 3.4028e+038
263
High_Input Input volts at high value -10 to +10
High_Value Input value in engineering units at high MA -3.4082e+038 to 3.4028e+038
Input _Filter Bandwidth of input signal filter in Hz Unused, 0.75 Hz, 1.5 Hz, 3 Hz,
TMR_DiffLimit Difference limit for voted TMR inputs in % of high- 0 to 10
low values
Sys_Lim_1_Enabl Enable system limit 1 fault check Enable, disable
Less than or equal
Sys_Lim_1 Input limit in engineering units -3.4082e+038 to 3.4028e+038
Sys_Lim_2 Same as above for Sys Lim 1 Same as for Sys_Lim_1
N125_Gnd Same as for P125_Grd – board point signal Same as for P125_Grd
Spare 01 Similar to P125_Grd – board point signal Similar to P125_Grd
Spare 02 Similar to P125_Grd – board point signal Similar to P125_Grd
VCMI Toolbox Configuration (Part 2 of 2)

Board Point Signal Description - Point Edit (Enter Signal Connection) Direction Type
L3Diag_VCMI1 Board diagnostic Input BIT
SysLimit1-1 P125_Grd (Input exceeds limit) Input BIT
SysLimit1-2 N125_Grd (Input exceeds limit) Input BIT
SysLimit1-3 Spare 01 (Input exceeds limit) Input BIT
SysLimit1_125 P125 bus out of limits (Input exceeds limit) Input BIT
SysLimit2-1 P125_Grd (Input exceeds limit) Input BIT
SysLimit2-2 N125_Grd (Input exceeds limit) Input BIT
SysLimit2_125 P125 bus out of limits (Input exceeds limit) Input BIT
P125Bus Calc 125 V dc bus voltage (P125Grd - N125Grd) Input FLOAT
ResetSYS System limit reset (Special VCMI output to I/O bds) Output BIT
ResetDIA Diagnostic reset (Special VCMI output to I/O bds) Output BIT
ResetSuicide Suicide reset (Special VCMI output to I/O bds) Output BIT
MasterReset Master reset L86MR (Special VCMI out to I/O bds) Output BIT
Logic_In_1 Battery bus fault Input BIT
Logic_In_2 AC1 source fault Input BIT
Logic_In_3 AC2 source fault Input BIT
Logic_In_4 Misc contact Input BIT
Logic_In_5 Fuse 31, J19 fault Input BIT
Logic_In_8 Spare 01 Input BIT
P125_Grd P125 with respect to ground, P3 – 28 to 29 Input FLOAT
GEH-6421M
N125_Grd N125 with respect to ground, negative number, P3 – 26 to 27 Input FLOAT
Spare01 Analog spare 01, P3 – 07 to 08 Input FLOAT
Spare02 Analog spare 02, P3 – 05 to 06 Input FLOAT
Alarms
1 SOE Overrun. Sequence of Events data overrun Communication problem on IONet
2 Flash Memory CRC Failure Board firmware programming error (board will not go
online)
3 CRC Failure Override is Active Board firmware programming error (board is allowed to
go online)
4 Watchdog circuitry is not armed Board firmware programming error (board is allowed to
go online)
16 System Limit Checking is Disabled System checking was disabled by configuration
17 Board ID Failure Failed ID chip on the VME I/O board
18 J3 ID Failure Failed ID chip on connector J3, or cable problem
22 J3A ID Failure Failed ID chip on connector J3A, or cable problem
24 Firmware/Hardware Incompatibility Invalid terminal board connected to VME I/O board
25 Board inputs disagree with the voted value A problem with the input. This could be the device, the
wire to the terminal board, the terminal board, or the
cable.
30 ConfigCompatCode mismatch; Firmware: #, Tre: # A tre file has been installed that is incompatible with
The configuration compatibility code that the firmware the firmware on the I/O board. Either the tre file or
is expecting is different than what is in the tre file for firmware must change. Contact the factory.
this board
31 IOCompatCode mismatch; Firmware: #; Tre: # A tre file has been installed that is incompatible with
The I/O compatibility code that the firmware is the firmware on the I/O board. Either the tre file or
expecting is different than what is in the tre file for this firmware must change. Contact the factory.
board
32 P5=###.## Volts is Outside of Limits. The P5 power A VME rack backplane wiring problem and/or power
supply is out of the specified operating limits supply problem
33 P15=###.## Volts is Outside of Limits. The P15 power If "Remote Control", disable diagnostic and ignore;
supply is out of the specified operating limits otherwise probably a back plane wiring or VME power
supply problem.
34 N15=###.## Volts is Outside of Limits. The N15 power If "Remote Control", disable diagnostic and ignore;
supply is out of the specified operating limits otherwise probably a VME backplane wiring and/or
35 P12=###.## Volts is Outside of Limits. The P12 power If "Remote I/O", disable diagnostic and ignore;
36 N12=###.## Volts is Outside of Limits. The N12 power If "Remote I/O", disable diagnostic and ignore;
37 P28A=###.## Volts is Outside of Limits. The P28A If "Remote Control", disable diagnostic and ignore;
power supply is out of the specified operating limits otherwise probably a VME backplane wiring and/or
38 P28B=###.## Volts is Outside of Limits. The P28B If "Remote Control", disable diagnostic and ignore;
power supply is out of the specified operating limits otherwise probably a VME backplane wiring and/or
265
39 P28C=###.## Volts is Outside of Limits. The P28C If "Remote Control" disable diagnostic. Disable
power supply is out of the specified operating limits diagnostic if not used; otherwise probably a backplane
wiring and/or power supply problem.
40 P28D=###.## Volts is Outside of Limits. The P28D If "Remote Control" disable diagnostic. Disable
41 P28E=###.## Volts is Outside of Limits. The P28E If "Remote Control" disable diagnostic. Disable
42 N28=###.## Volts is Outside of Limits. The N28 power If "Remote Control" disable diagnostic. Disable
supply is out of the specified operating limits diagnostic if not used; otherwise probably a backplane
43 125 Volt Bus=###.## Volts is Outside of Limits. The A source voltage or cabling problem; disable 125 V
125-Volt bus voltage is out of the specified operating monitoring if not applicable.
limits
44 125 Volt Bus Ground =###.## Volts is Outside of Leakage or a fault to ground causing an unbalance on
Limits. The 125-Volt bus voltage ground is out of the the 125 V bus; disable 125 V monitoring if not
specified operating limits applicable.
45 IONet-1 Communications Failure. Loss of Loose cable, rack power, or VCMI problem
communication on IONet1
48 VME Bus Error Detected (Total of ### Errors). The The sum of errors 60 through 66 - Contact the factory.
VCMI has detected errors on the VME bus
49 Using Default Input Data, Rack R.#. The VCMI is not IONet communications failure - Check the VCMI and/or
getting data from the specified rack IONet cables.
50 Using Default Input Data, Rack S.#. The VCMI is not IONet communications failure - Check the VCMI and/or
51 Using Default Input Data, Rack T.#. The VCMI is not IONet communications failure - Check the VCMI and/or
52 Missed Time Match Interrupt (## uSec). The VCMI has Possible VCMI hardware failure
detected a missed interrupt
53 VCMI Scheduler Task Overrun. The VCMI did not Possibly too many I/O
complete running all its code before the end of the
frame
54 Auto Slot ID Failure (Perm. VME Interrupt). The VCMI I/O board or backplane problem
cannot perform its AUTOSLOT ID function
55 Card ID/Auto Slot ID Mismatch. The VCMI cannot read Board ID chip failed
the identity of a card that it has found in the rack
56 Topology File/Board ID Mismatch. The VCMI has ID chip mismatch - Check your configuration
detected a mismatch between the configuration file and
what it actually detects in the rack
57 Controller Sequencing Overrun Too much application code used in controller. Reduce
the code size.
58 Controller PCODE Version Mismatch between R,S,and Error during controller download - revalidate, build, and
T. R, S, and T have different software versions download all 3 controllers.
59 IONet Communications Failure. Loss of Loose cable, rack power, or VCMI problem (VCMI
communications on the slave VCMI IONet slave only)
60- VME Error Bit # (Total ## Errors). The VCMI has VME backplane errors - Contact factory.
66 detected errors on the VME bus
67 Controller Board is Offline. The VCMI cannot Controller failed or is powered down.
communicate with the controller
68- I/O Board in Slot # is Offline. The VCMI cannot I/O board is failed or removed. You must replace the
87 communicate with the specified board board, or reconfigure the system and redownload to
the VCMI, and reboot.
GEH-6421M
88 U17 Sectors 0-5 are not write protected Sectors not write protected in manufacturing. Contact
the factory.
89 SRAM resources exceeded. Topology/config too large The size of the configured system is too large for the
VCMI. You must reduce the size of the system.
90 U54 Flashsectors #-## not write protected Sectors not write protected in manufacturing. Contact
the factory
267
Notes
268 of 1016
VPRO Turbine Protection Board
VPRO Emergency Turbine Protection

The Emergency Turbine Protection (VPRO) board and associated terminal boards
(TPRO and TREG) provide an independent emergency overspeed protection system.
The protection system consists of triple redundant VPRO boards in a module
separate from the turbine control system, controlling the trip solenoids through
TREG. The figures shows the cabling to VPRO from the TPRO and TREG terminal
boards.
Note VPRO also has an Ethernet connection for IONet communications with the
control modules.
The VPRO board in the Protection Module provides the emergency trip
function. Up to three trip solenoids can be connected between the TREG and TRPG
terminal boards. TREG provides the positive side of the 125 V dc to the solenoids
and TRPG provides the negative side. Either board can trip the turbine. VPRO
provides emergency overspeed protection and the emergency stop functions. It
controls the 12 relays on TREG, nine of which form three groups of three to vote
inputs controlling the three trip solenoids.
The original VPROH1A has been superseded by the functionally equivalent

VPROH1B. VPROH1A and VPROH1B supports a second TREG board driven from
VPRO connector J4. VPROH2B is a lower power version of VPRO that omits
support for the second TREG board. Applications using a second TREG board
connected to J4 must use VPROH1A or VPROH1B, not VPROH2B.
269
Volume II VPRO Turbine Protection Board • 201
TPRO Terminal Board VPRO- R8
Ethernet
x IONet x x x
x
x 1 JZ1
x 2
x 4 x 3 I RUN
x 5 O FAIL
x 6 N STAT
x 8 x 7 E 8 X
x 10 x 9 T 4 Y
x 12 x 11 T 2 Z
x 14 x 13 R 1
x 15 C
x 16 JZ5
x 18 x 17 S
x 20 x 19 JY1 E
x 22 x 21 Cables to VPRO-T8 R J6
x 24 x 23
x J P5
COM
5
JY5 P28A
x P28B
x 26 x 25 E
x 28 x 27 T
x 30 x 29 H
x 32 x 31 R
x 33 JX1 Cables to VPRO-S8 J J
x 34 P
x 36 x 35 JX5 3 4 P
A
38 x 37
x R O
x 40 x 39 A
x 41 W
x 42 F N L
x 44 x 43 E
x 45 VPRO
x 46 Cables to VPRO-R8 R
x 48
x 47 x x x
x
x
To TREG
Shield 37-pin "D" shell
Bar type connectors To Second TREG
with latching (optional)
BarrierType Terminal fasteners
VPRO Board, TPRO Terminal Board, and Cabling
202 • VPRO Turbine Protection Board 270 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
The figure shows how the VTUR and VPRO processor boards share in the turbine
protection scheme. Either one can independently trip the turbine using the relays on
TRPG or TREG.
VTUR Special speed cable

JR5 TTUR
JS5
JT5
J5
Two
JR1
xfrs
JS1
Optional 3 Relays
JT1
daughter- Gen Synch
board
335 V dc from <Q>
J3 J4 J5
JR1
TRPG
JS1
J3
JT1
To second
TRPG board 9 Relays
J4 J4 (optional) (3 x 3 PTR's)
J1
J2
125 VDC
Cable Trip Solenoids,

three circuits
J2 J1
TREG Trip signal to
JX1
TSVO TB's
JY1
VPRO
JZ1
J3
To second 12 Relays
J4 TREG Board
(9 ETR's,
(optional)
J5 3 econ. relays)
JH1
J6
P125 V dc from <PDM>
NEMA class F
Special speed cable

JX5 TPRO
JY5
J7
JZ5
JX1 2 transformers
JY1
125 VDC JZ1
Turbine Control and Protection Boards
271
Installation

its edge connectors
panel
Note Cable connections to the terminal boards are made at the J3, J4, J5, and J6
connectors on VPRO front panel. These are latching type connectors to secure
the cables. Connector J7 is for 125 V dc power. For details refer to the section
on diagnostics in this document.
It may be necessary to update the VPRO firmware to the latest level. For
instructions, refer to GEH-6403 Control System Toolbox for a Mark VI Turbine
Controller.
Operation
The main purpose of the protection module is emergency overspeed (EOS)
protection for the turbine, using three VPRO boards. In addition, VPRO has backup
synchronization check protection, three analog current inputs, and nine thermocouple
inputs, primarily intended for exhaust over-temperature protection on gas turbines.
The protection module is always triple redundant with three completely separate and
independent VPRO boards named R8, S8, and T8 (originally named X, Y, and Z).
Any one of these boards can be powered down and replaced while the turbine is
running without jeopardizing the protection system. Each board contains its own I/O
interface, processor, power supply, and Ethernet communications (IONet) to the
controller. The communications allow initiation of test commands from the
controller to the protection module and the monitoring of EOS system diagnostics in
the controller and on the operator interface. Communications are resident on the
VPRO board. The VPRO board has a VME interface that allows programming and
testing in a VME rack. However, the backplane is neutralized when plugged into the
protection module to eliminate any continuity between the three independent
sections.
Speed Control and Overspeed Protection
Speed control and overspeed protection is implemented with six passive, magnetic
speed pickups. The first three are monitored by the controllers, which use the median
signal for speed control and primary overspeed protection. The second three are
separately connected to the R8, S8, and T8 VPROs in the protection module.
Provision is made for nine passive magnetic speed pickups or active pulse rate
transducers (TTL type) on the TPRO terminal board with three being monitored by
each of the R8, S8, and T8 VPROs. Separate overspeed trip settings are programmed
into the application software for the primary and emergency overspeed trip limits,
and a second emergency overspeed trip limit must be programmed into the I/O
configurator to confirm the emergency overspeed (EOS) trip point.
GEH-6421M
The speed is calculated by counting passing teeth on the wheel and measuring the
time involved. Another protection feature is: after the turbine reaches a
predetermined steady-state speed, the rate of change of speed is continuously
calculated and compared with 100%/sec and transmitted to the controller to trip the
unit if it is detected. This steady-state speed limit is a tuning constant located in the
controller’s application software. Another speed threshold which is monitored by the
EOS system, is 10% speed. This is transmitted to the controller to verify that there is
no gross disagreement between the first set of three speed pickups being monitored
by the controller (for speed control and the primary overspeed protection) and the
second set of three speed pickups being monitored by the EOS system.
Speed Difference Detection
There should never be a reason why the speed calculated by PPRO is significantly
different from the speed calculated by the main control. Speed difference detection
looks at the difference in magnitude between pulse rate 1 from both PPRO and the
main control. If the difference is greater than the set threshold for three successive
samples, a SpeedDifTrip is latched. If the main control recovers for 60 seconds, the
trip is removed. This allows the main control to recover with subsequent re-arming
of the backup protection.
Interface To Trip Solenoids
The trip system combines the Primary Trip Interface from the controller with the
EOS Trip Interface from the protection module. Three separate, triple redundant trip
solenoids (also called Electrical Trip Devices - ETDs) are used to interface with the
hydraulics. The ETDs are connected between the TRPG and TREG terminal boards.
A separately fused 125 V dc feeder is provided from the turbine control for each
solenoid, which is energized in the run mode and de-energized in the trip mode.
Backup Synch Check Protection
Backup synch check protection is provided in the Protection Module. The generator
and bus voltages are supplied from two, single phase, potential transformers (PTs)
secondary output supplying a nominal 115 V rms. The maximum cable length
between the PTs and the turbine control is 100 meters of 18 AWG twisted, shielded
wire. Each PT is magnetically isolated with a 1,500 V rms rated barrier and a circuit
load less than 3 VA. The synch algorithms are based on phase lock loop techniques.
Phase error between the generator and bus voltages is less than +/-1 degree at
nominal voltage and 50/60 Hz. A frequency range of 45 to 66 Hz is supported with
the measured frequency within 0.05% of the input frequency. The algorithm is
illustrated under TTUR, generator synchronizing.
Each PT input is internally connected in parallel to the R8, S8, and T8 VPROs. The
triple redundant phase slip windows result in a voted logical output on the TREG
terminal board, which drives the K25A relay. This relay’s contacts are connected in
series with the synch permissive relay (K25P) and the auto synch relay (K25) to
insure that no false command is issued to close the generator breaker. Similarly,
contacts from the K25A contact are connected in series with the contacts from
remote, manual synchronizing equipment to insure no false commands.
Thermocouple and Analog Inputs
Thermocouple and analog inputs are available in the VPRO, primarily for gas turbine
applications. Nine thermocouple inputs are monitored with three connected to each
VPRO. These are generally used for backup exhaust over-temperature protection.
Also, one ±5, 10 V dc, 4-20 mA (selectable) input, and two 4-20 mA inputs can be
connected to the TPRO terminal board, which feeds the inputs in parallel to the three
VPROs.
273
Power Supply
Each VPRO board has its own on-board power supply. This generates 5 V dc and 28
V dc using 125 V dc supplied from the cabinet PDM. The entire protection module
therefore has three power supplies for high reliability
TREG is entirely controlled by VPRO, and the only connections to the control
modules are the J2 power cable and the trip solenoids. In simplex systems a third
cable carries a trip signal from J1 to the TSVO terminal board, providing a servo
valve clamp function upon turbine trip.
Control of Trip Solenoids
Note The solenoid circuit has a metal oxide varistor (MOV) for current suppression
and a 10 Ω, 70 W economizing resistor.
Both TRPG and TREG control the trip solenoids so that either one can remove
power and actuate the hydraulics to close the steam or fuel valves. The three trip
solenoids are supplied with 125 V dc through plug J2, and draw up to 1 A with a 0.1
second L/R time constant. The nine trip relay coils on TREG are supplied with 28 V
dc from VPRO boards in R8, S8, and T8.
A separately fused 125 V dc feeder is provided for the solenoids, which energize in
the run mode and de-energize in the trip mode. Diagnostics monitor each 125 V dc
feeder from the power distribution module at its point of entry on the terminal board
to verify the fuse integrity and the cable connection.
Solenoid Trip Tests
Application software in the controller is used to initiate tests of the trip solenoids.
Online tests allow each of the trip solenoids to be manually tripped one at a time
either through the PTR relays from the controller or through the ETR relays from the
protection module. A contact from each solenoid circuit is wired back as a contact
input to give a positive indication that the solenoid has tripped. Primary and
emergency offline overspeed tests are provided too for verification of actual trips due
to software simulated trip overspeed conditions.
GEH-6421M
Terminal Board TPRO VPRO R8 VPRO S8 VPRO T8
1 Noise Suppression
JX1
Protection Protection Protection
Gen. Volts
120 V ac NS
2
from PT
Noise Suppression
3 ID
Bus Volts
120 V ac JY1 J6 J6 J6
NS
from PT 4
To TTUR 1
Thermocouple Inputs CJ
13
TC1RH NS
14 Three TC ccts to R8 ID
TC1RL NS 1 Overspeed Overspeed Overspeed
19 CJ
TC1SH NS JZ1 Em Stop Em Stop Em Stop
20 Three TC ccts to S8 Sync Sync Sync
TC1SL NS 1 Check Check Check
25 CJ
TC1TH NS Overtemp Overtemp Overtemp
26 Three TC ccts to T8
TC1TL NS ID
P28VV
5
P28V,R8
P24V1 Current P28V,S8
Limiter P28V,T8 J5 J5 J5
7
V dc VDC
6 JPA1
20mA1 20 ma
250 ohms To R8,S8,T8
8 J3
mAret J3 J3
One of the above ccts
Open Ret
JPB1
9 Current P28VV
P24V2 J4 J4 J4
Limiter
10
20 mA2
250
ohms To R8,S8,T8
Two of the above ccts
JX5
#1 MX1H 31 To TREG and
Filter
Emergency Clamp Trip Solenoids
Magnetic NS
MX1H 32 AC
Speed Coupling
Pickup 3 Circuits
ID
#2 MY1H 37 Filter
Emergency Clamp JY5
Magnetic NS
MY1L 38 AC
Speed Coupling
Pickup 3 Circuits
ID
#3 MZ1H 43 Filter
Emergency Clamp JZ5
Magnetic NS
MZ1L 44 AC
Speed Coupling
Pickup 3 Circuits ID
TMR VPROs and TPRO Terminal Board
275
Specifications
Item Specification
Number of Inputs 3 Passive speed pickups
1 Generator and 1 Bus Voltage
3 Thermocouples1 4-20 mA current or voltage
2 4-20 mA current
7 Trip interlocks
2 Emergency Stop
Number of Outputs 6 Trip Solenoids
6 Economizer relays
1 Breaker relay command, K25A on TTUR
1 Servo clamp relay contact, to TSVO boards
Power Supply Voltage Input supply 125 V dc (70-145 V dc)
Output 5 V dc and 28 V dc
Frame Rate Up to 100 Hz
MPU Characteristics Output resistance 200 Ω with inductance of 85 mH.Output generates 150 V p-p into 60 K
Ω at the TPRO terminal block, with insufficient energy for a spark. The maximum short
circuit current is approximately 100 mA.
The system applies up to 400 Ω normal mode load to the input signal to reduce the
voltage at the terminals.
MPU Cable Sensors can be up to 300 m (984 ft) from the cabinet, assuming that shielded pair cable
is used, with typical 70 nF single ended or 35 nF differential capacitance, and 15 Ω
resistance.
MPU Pulse Rate Range 2 Hz to 20 kHz
MPU Pulse Rate Accuracy 0.05% of reading; resolution is 15 bits at 100 Hz Noise of the acceleration measurement
is less than ±50 Hz/sec for a 10,000 Hz signal being read at 10 ms.
MPU Input Circuit Sensitivity Minimum signal is 27 mV pk at 2 Hz
Minimum signal is 450 mV pk at 14 kHz
Generator and Bus Voltage Two Single-Phase Potential Transformers, 115 V rms secondary voltage accuracy is
Sensors 0.5% of rated Volts rms
Frequency Accuracy 0.05%
Phase Difference Measurement better than 1 degree.
Allowable voltage range for synchronizing is 75 to 130 V rms. Each input has a load of
less than 3 VA.
Thermocouple Inputs Same specifications as for VTCC board
Analog Inputs 2 current inputs, 4-20 mA
1 current input, with selection of 4-20 mA, or ±5 V dc, or ±10 V dc.
Same specifications as for VAIC board
GEH-6421M
Diagnostics
Three LEDs at the top of the VPRO front panel provide status information. The
normal RUN condition is a flashing green, FAIL is a solid red. The third LED is
STATUS and is normally off but shows a steady orange if a diagnostic alarm
condition exists in the board. VPRO makes diagnostic checks and creates faults as
follows:
• Trip relay driver and contact feedbacks

• Solenoid voltage and solenoid voltage source
• Economizer relay driver and contact feedbacks
• K25A relay driver and coil
• Servo clamp relay driver and contact feedback
• High and low limits on all analog inputs
• If any one of the above signals goes unhealthy, a composite diagnostic alarm
L3DIAG_VPROR, or S, or T occurs. The diagnostic signals can be individually
latched and then reset with the RESET_DIA signal if they go healthy.
Terminal board connectors on TPRO and TREG have their own ID device that is
interrogated by the I/O board. The ID device is a read-only chip coded with the
terminal board serial number, board type, revision number, and plug location. When
the chip is read by VPRO and a mismatch is encountered, a hardware incompatibility
fault is created.
Configuration
Configuration
Turbine_Type Define the type of turbine from selection of ten types Two gas turbine, two LM, two
large steam, one medium
steam, one small steam, two
stag GT
LMTripZEnable On LM machine, when no PR on Z, enable vote for trip Enable, disable
OT_Trip_Enbl Enable overtemperature trip Enable, disable
OvrTemp_Trip Iso-thermal overtemperature trip setting for exhaust thermocouples -60 to 2,000
in degree F
TA_Trip_Enab1 Steam, enable trip anticipation on ETR1 Enable, disable
(same for four ETRs)
ContWdogEn Enable trip on loss of control outputs to VPRO Enable. disable
SpeedDifEn Enable trip on speed difference between controller & VPRO Enable. disable
StaleSpdEn Enable trip on speed from controller freezing Enable, disable
DiagSolPwrA For TREL/TRES, sol power, BusA, diagnostic Enable, disable
(same for three solenoids)
RatedRPM_TA Steam, rated RPM, used for trip anticipation calc 0 to 20,000
AccelCalType Select acceleration calculation type Slow, medium, fast
Auto Reset Automatic restoring of thermocouples removed from scan Enable, disable
OTBias_RampP Overtemperature bias ramp positive
OTBias_RampN Overtemperature bias ramp negative
Min_MA_Input Minimum MA for healthy 4/20 ma Input 0 to 21
Max_MA_Input Maximum MA for healthy 4/20 ma Input 0 to 21
OTBias_Dflt Overtemperature bias
277
OS_Diff Absolute speed difference, in percent, for trip threshold (if 0 to 10
SpeedDifEn enabled)
5J6:IS200TPRO
PulseRate1 First of three speed inputs - card point point edit (input FLOAT)
PRType Selects gearing (resolution) Unused, PR<6,000 Hz,
PR>6,000 Hz
PRScale Pulses per revolution (output RPM) 0 to 1,000
OS_Setpoint Overspeed trip setpoint in RPM 0 to 20,000
OS_Tst_Delta Offline overspeed test setpoint delta in RPM -2,000 to 2,000
Zero_Speed Zero speed for this shaft in RPM 0 to 20,000
Min_Speed Minimum speed for this shaft in RPM 0 to 20,000
Accel_Trip Enable acceleration trip Enable, disable
Acc_Setpoint Accelerate trip setpoint in RPM/second 0 to 20,000
TMR_DiffLimt Difference limit for voted pulse rate inputs in engineering units 0 to 20,000
BusPT_KVolts Kilo-Volts RMS, bus potential transformer - card point Point edit (input FLOAT)
PT_Input PT input in kilovolts rms for PT_Output 0 to 1,000
PT_Output PT output in volts rms for PT_Input typically 115 60 to 150
TMR_DiffLimt Difference limit for voted PT inputs in percent 0 to 100
GenPT_KVolts Kilo-Volts RMS, generator PT, configuration similar to Bus PT- Point edit (input FLOAT)
card point
TC1R Thermocouple 1, for R module (first of R, S, and T) - card point Point edit (input FLOAT)
ThermCplType Select thermocouple type or mV input Unused, mV, T, K, J, E
Low Pass Filter Enable 2 Hz low pass filter Enable, disable

TC2R Thermocouple 2, for R module (first of R, S, and T) config as Point edit (Input FLOAT)
above - card point
TC3R Thermocouple 3, for R module (first of R, S, and T) config as Point edit (Input FLOAT)
above - card point
Cold Junction Cold junction for thermocouples 1-3 Point edit (Input FLOAT)
TMR_DiffLimt Difference limit for voted TMR cold junction inputs in Deg F -60 to 2,000
AnalogIn1 First of three analog inputs - card point Point Edit (Input FLOAT)
Input Type Type of analog input Unused, 4-20 mA, ±10 V
Low_Input Input mA at low value -10 to 20
Low_Value Input value in engineering units at low value -3.402e +38 to 3.402e +38
High_Input Input mA at high value -10 to 20
High_Value Input value in engineering units at high mA -3.402e +38 to 3.402e +38
InputFilter Filter bandwidth in Hz Unused, 12 Hz, 6 Hz, 3Hz,
1.5 Hz, 0.75 Hz
Trip_Enable Enable trip for this mA input Enable, Disable
DiagHighEnab Enable high input limit diag Enable, Disable
DiagLowEnab Enable low input limit diag Enable, disable
TripSetpoint Trip setpoint in engineering units -3.402e +38 to 3.402e +38
TripTimeDelay Time delay before tripping turbine after signal exceeds setpoint in 0 to 10
seconds
TMR_DiffLimt Difference limit for voted TMR inputs in per cent of (High_Value- 0 to 100
Low_Value)
J3:IS200TREG First TREG board Connected, not connected
KESTOP1_Fdbk1 Emergency Stop ESTOP1, inverse sense, K4 relay, True=Run - Point edit (input BIT)
card point
DiagVoteEnab Enable voting disagreement diagnostic Enable, disable
Contact1 Trip interlock 1 (first of 7) - card point Point edit (Input BIT)
GEH-6421M
ContactInput Trip interlock 1 used Used, unused
SeqOfEvents Record contact transitions in sequence of events Enable, disable
DiagVoteEnab Enable voting disagreement diagnostic Enable. disable
TrpTimeDelay Time delay before tripping turbine after contact opens (sec) 0 to 10
TripMode Trip mode Direct, conditional, disable
K1_Fdbk Trip relay 1 feedback (first of 3) - card point Point edit (Input BIT)
RelayOutput Relay feedback used Used, unused
DiagSolEnab Enable solenoid voltage diagnostic Enable, disable
KE1_Fdbk Economizer relay for trip solenoid feedbk (first of 3) - card point Point edit (Input BIT)
RelayOutput Economizer relay feedback used Used, unused
K4CL_Fdbk Drive control valve servos closed, use only for steam turbine Point edit (Input BIT)
simplex - card Point
Relay Output Servo valve clamp used Used, unused
K25A_Fdbk Synchronizing check relay on TTUR - card point Point edit (Input BIT)
SynchCheck Synch check relay K25A used Used, unused
SystemFreq System frequency in Hz 50 or 60
ReferFreq Select generator frequency reference for PLL, standard PR input PR Std or Sg space
or from signal space
TurbRPM Rated load turbine RPM 0 to 20,000
VoltageDiff Maximum voltage difference in kV rms for synchronizing 0 to1,000
FreqDiff Maximum frequency difference in Hz for synchronizing 0 to 0.5
PhaseDiff Maximum phase difference in degrees for synchronizing 0 to 30
GenVoltage Minimum generator voltage in kV rms for synchronizing 1 to 1,000
BusVoltage Minimum bus voltage in kV rms for synchronizing 1 to 1,000
J4A:IS200TREG Second TREG board Connected, not con.
KESTOP2_Fdbk Emergency stop ESTOP2, inverse sense, K4 relay, True= run - Point edit (Input BIT)
card point
K4_Fdbk Trip relay 4 feedback (first of 4,5,6) - card point Point edit (Input BIT)
KE4_Fdbk Economizing relay for trip solenoid 4 (first of 4,5,6) - card point Point edit (Input BIT)
Card Points(Signals) Description–Point Edit (Enter Signal Connection) Direction Type

L3DIAG-VPROR Card Diagnostic Input BIT
L3DIAG-VPROS Card Diagnostic Input BIT
L3DIAG-VPROT Card Diagnostic Input BIT
PR1_Zero L14HP_ZE Input BIT
PR2_Zero L14IP_ZE Input BIT
PR3_Zero L14LP_ZE Input BIT
K1_FdbkNVR Non voted L4ETR1_FB, Trip Relay 1 Feedback R Input BIT
K1_FdbkNVS Non voted L4ETS1_FB, Trip Relay 1 Feedback S Input BIT
K1_FdbkNVT Non voted L4ETT1_FB, Trip Relay 1 Feedback T Input BIT
: : :
K6_FdbkNVR Non voted L4ETR6_FB, Trip Relay 6 Feedback R Input BIT
K6_FdbkNVS Non voted L4ETS6_FB, Trip Relay 6 Feedback S Input BIT
K6_FdbkNVT Non voted L4ETT6_FB, Trip Relay 6 Feedback T Input BIT
279
OS1_Trip L12HP_TP Input BIT
OS2_Trip L12IP_TP Input BIT
OS3_Trip L12LP_TP Input BIT
Dec1_Trip L12HP_DEC Input BIT
Dec2_Trip L12IP_DEC Input BIT
Dec3_Trip L12LP_DEC Input BIT
Acc1_Trip L12HP_ACC Input BIT
Acc2_Trip L12IP_ACC Input BIT
Acc3_Trip L12LP_ACC Input BIT
TA_Trip Trip Anticipate Trip L12TA_TP Input BIT
TA_StpLoss L30TA Input BIT
OT_Trip L26TRP Input BIT
MA1_Trip L3MA_TRP1 Input BIT
SOL1_Vfdbk When TREG used, Trip Solenoid 1 Voltage detected status Input BIT
: : Input BIT
SOL6_Vfdbk When TREG used, Trip Solenoid 6 Voltage detected status Input BIT
L25A_Cmd L25A Breaker Close Pulse Input BIT
The following Input BITs marked config are set by Configuration

Cont1_TrEnab Config_Contact 1 Trip Enabled Input BIT
: : Input BIT
Cont7_TrEnab Config -contact 7 trip enabled Input BIT
Acc1_TrEnab Config- accel 1 trip enabled Input BIT
OT_TrEnab Config – overtemp trip enabled Input BIT
GT_1Shaft Config – gas turb, 1 shaft enabled Input BIT
GT_2Shaft Config – gas turb, 2 shaft enabled Input BIT
LM_2Shaft Config – LM turb, 2 shaft enabled Input BIT
LM_3Shaft Config – LM turb, 3 shaft enabled Input BIT
LargeSteam Config – Large steam 1, enabled Input BIT
MediumSteam Config – medium steam, enabled Input BIT
SmallSteam Config – small steam, enabled Input BIT
STag_GT_1S Config - stag 1 shaft, enabled Input BIT
STag_GT_2S Config - stag 2 shaft, enabled Input BIT
ETR1_Enab Config - ETR1 relay enabled Input BIT
: : :
ETR6_Enab Config - ETR6 relay enabled Input BIT
KE1_Enab Config - economizing relay 1 enabled Input BIT
K4CL_Enab Config - servo clamp relay enabled Input BIT
K25A_Enab Config - sync check relay enabled Input BIT
GEH-6421M
L5CFG1_Trip HP config Trip Input BIT
L5CFG2_Trip IP config Trip Input BIT
L5CFG3_Trip LP config Trip Input BIT
OS1_SP_CfgEr HP overspeed setpoint config mismatch error Input BIT
OS2_SP_CfgEr IP overspeed setpoint config mismatch error Input BIT
OS3_SP_CfgEr LP overspeed setpoint config mismatch error Input BIT
ComposTrip1 Composite trip 1 Input BIT
L5ESTOP1 ESTOP1 trip, TREG, J3 Input BIT
L5ESTOP2 ESTOP2 trip, TREG, J4 Input BIT
L5Cont1_Trip Contact1 trip Input BIT
: : Input BIT
L5Cont7_Trip Contact7 trip Input BIT
LPShaftLock LP shaft locked Input BIT
Inhbt1_Fdbk Trip inhibit signal feedback for contact 1 Input BIT
: : :
Inhbt7_Fdbk Trip inhibit signal feedback for contact 7 Input BIT
L3SS_Comm Valid communications with VCMI status Input BIT
Trip1_EnCon Contact1 trip enabled conditional Input BIT
: : Input BIT
Trip7_EnCon Contact7 trip enabled conditional Input BIT
BusFreq Bus frequency SFL 2 Hz Input FLOAT
GenFreq Gen frequency SF 2 Hz Input FLOAT
GenVoltsDiff Gen - bus kV difference rms: gen low is negative Input FLOAT
GenFreqDiff Gen - bus slip Hz: gen slow is negative Input FLOAT
GenPhaseDiff Gen - bus phase difference degrees: gen lag is negative Input FLOAT
PR1_Accel HP accel in RPM/SEC Input FLOAT
PR2_Accel IP accel in RPM/SEC Input FLOAT
PR3_Accel LP accel in RPM/SEC Input FLOAT
PR1_Max HP max speed since last zero speed in RPM (see Vol 1 Chap 8 Input FLOAT
overspeed protection)
PR2_Max IP max speed since last zero speed in RPM Input FLOAT
PR3_Max LP max speed since last zero speed in RPM Input FLOAT
OTSPBias Overtemperature setpoint bias Input FLOAT
OTSetpoint Overtemperature setpoint Input FLOAT
SynCk_Perm L25A_PERM – sync check permissive Output BIT
SynCk_ByPass L25A_BYPASS – sync check bypass Output BIT
Cross_Trip L4Z_XTRP – control cross trip Output BIT
OnLineOS1Tst L97HP_TST1 – on line HP overspeed test Output BIT
OnLineOS2Tst L97LP_TST1 – on line HP overspeed test Output BIT
OnLineOS3Tst L97IP_TST1 – on line LP overspeed test Output BIT
OffLineOS1Tst L97HP_TST2 – offline HP overspeed test Output BIT
OffLineOS2Tst L97LP_TST2 – offline IP overspeed test Output BIT
OffLineOS3Tst L97IP_TST2 – offline LP overspeed test Output BIT
TrpAntcptTst L97A_TST – trip anticipate test Output BIT
LokdRotorByp L97LR_BYP – locked rotor bypass Output BIT
HPZeroSpdByp L97ZSC_BYP – HP zero speed check bypass Output BIT
281
TestETR1 L97ETR1 – ETR1 test, true denergizes relay Output BIT
: : :
TestETR4 L97ETR4 – ETR4 Test, true denergizes relay Output BIT
PTR1 L20PTR1 – primary trip relay CMD for diagnostic only Output BIT
: : :
PTR6 L20PTR6 – primary trip relay CMD for diagnostic only Output BIT
PR_Max_Rst Max speed reset (see Vol 1 Chap 8 overspeed protection) Output BIT
OnLineOS1X L43EOST_ONL – online HP overspeed test with auto reset Output BIT
Trip1 Inhbt Contact1 trip inhibit Output BIT
: : :
Trip7 Inhbt Contact7 trip inhibit Output BIT
CJBackup Estimated TC cold junction temperature in Deg F Output FLOAT
OS1_Setpoint HP overspeed setpoint in RPM Output FLOAT
OS2_Setpoint IP overspeed setpoint in RPM Output FLOAT
OS3_Setpoint LP overspeed setpoint in RPM Output FLOAT
OS1_TATrpSp PR1 overspeed trip setpoint in RPM for trip anticipate Fn Output FLOAT
OTBias Overtemperature bias signal Output FLOAT
DriveFreq Drive (Gen) Freq (Hz), used for non standard drive config. Output FLOAT
Speed1 Shaft speed 1 in RPM Output FLOAT
ContWdog Controller watchdog counter Output LONG INT
Alarms
2 Flash memory CRC failure Board firmware programming error (board will not go online)
3 CRC failure override is active Board firmware programming error (board is allowed to go
online)
4-15 Reserved for future use
16 System limit checking is disabled System checking was disabled by configuration.
22 J3A ID failure Failed ID chip on connector J3A, or cable problem
23 J4A ID failure Failed ID chip on connector J4A, or cable problem
24 Firmware/Hardware incompatibility Invalid terminal board connected to VME I/O board
30 ConfigCompatCode mismatch; firmware: #; Tre: # The A tre file has been installed that is incompatible with the
configuration compatibility code that the firmware is firmware on the I/O board. Either the tre file or firmware must
expecting is different than what is in the tre file for this change. Contact the factory.
board
31 IOCompatCode mismatch; firmware: #; Tre: # The I/O A tre file has been installed that is incompatible with the
compatibility code that the firmware is expecting is firmware on the I/O board. Either the tre file or firmware must
different than what is in the tre file for this board change. Contact the factory.
32-38 Contact input # not responding to test mode trip Contact input circuit failure on VPRO or TREG/TREL/TRES
interlock number # is not reliable board.
39-40 Contact excitation voltage test failure contact excitation Loss of P125 voltage caused by disconnection of JH1 to
voltage has failed, trip interlock monitoring voltage is TREG/TREL/TRES, or disconnect of JX1, JY1, JZ1 on
lost TREG/TREL/TRES to J3 on VPRO.
GEH-6421M
41-43 Thermocouple ## raw counts high. The ## A condition such as stray voltage or noise caused the input to
thermocouple input to the analog to digital converter exceed +63 mV.
exceeded the converter limits and will be removed from
scan
44-46 Thermocouple ## raw counts low. The ## The board detected a thermocouple open and applied a bias
thermocouple input to the analog to digital converter to the circuit driving it to a large negative number, or the TC is
exceeded the converter limits and will be removed from not connected, or a condition such as stray voltage or noise
scan caused the input to exceed -63 mV.
47 Cold junction raw counts high. Cold junction device The cold junction device on the terminal board has failed.
input to the A/D converter has exceeded the limits of
the converter. Normally two cold junction inputs are
averaged; if one is detected as bad then the other is
used. If both cold junctions fail, a predetermined value
is used
48 Cold junction raw counts low. Cold junction device The cold junction device on the terminal board has failed.
input to the A/D converter has exceeded the limits of
the converter
49 Calibration reference # raw counts high. Calibration The precision reference voltage on the board has failed.
reference # input to the A/D converter exceeded the
converter limits. If Cal. Ref. 1, all even numbered TC
inputs will be wrong; if Cal. Ref. 2, all odd numbered
TC inputs will be wrong
50 Calibration reference raw counts low. Calibration The precision reference voltage on the board has failed.
reference input to the A/D converter exceeded the
converter limits
51 Null reference raw counts high. The null (zero) The null reference voltage signal on the board has failed.
reference input to the A/D converter has exceeded the
converter limits
52 Null reference raw counts low. The null (zero) The null reference voltage signal on the board has failed.
reference input to the A/D converter has exceeded the
converter limits
53-55 Thermocouple ## linearization table high. The thermo- The thermocouple has been configured as the wrong type, or
couple input has exceeded the range of the a stray voltage has biased the TC outside of its normal range,
linearization (lookup) table for this type. The or the cold junction compensation is wrong.
temperature will be set to the table's maximum value
56-58 Thermocouple ## linearization table low. The thermo - The thermocouple has been configured as the wrong type, or
couple input has exceeded the range of the a stray voltage has biased the TC outside of its normal range,
linearization (lookup) table for this type. The or the cold junction compensation is wrong.
temperature will be set to the table's minimum value
59-61 Analog Input # unhealthy. The number # analog input The input has exceeded 4-20 mA range, or for input #1 if
to the A/D converter has exceeded the converter limits jumpered for ±10 V, it has exceeded ±10 V range, or the 250
Ω burden resistor on TPRO has failed.
63 P15=####.## volts is outside of limits. The P15 power Analog ±15 V power supply on VPRO board has failed.
supply is out of the specified +12.75 to +17.25 V
operating limits
64 N15=####.## volts is outside of Limits. The N15 Analog ±15 V power supply on VPRO board has failed.
power supply is out of the specified –17.25 to –12.75 V
operating limits
67 P28A=####.## Volts is Outside of Limits. The P28A The P28A power supply on VPWR board has failed, otherwise
power supply is out of the specified 23.8 to 31.0 V there may be a bad connection at J9, the VPWR to VPRO
operating limits interconnect.
68 P28B=####.## Volts is Outside of Limits. The P28B The P28B power supply on VPWR board has failed, otherwise
power supply is out of the specified 23.8 to 31.0 V there may be a bad connection at J9, the VPWR to VPRO
operating limits interconnect.
69-82 Relay driver feedback does not match the requested The relay driver or relay driver feedback monitor on the
state. The state of the command to the relay does not TREG/TREL/TRES terminal board has failed, or the cabling
match the state of the relay driver feedback signal; the between VPRO and TREG/TREL/TRES is incorrect.
relay cannot be reliably driven until corrected
283
69-71 Trip Relay (ETR) Driver # Mismatch requested State. See 69-82 above
Terminal Board 1
72-74 Econ Relay Driver # Mismatch Requested State. See 69-82 above
Terminal Board 1
75 Servo Clamp Relay Driver Mismatch (K4CL) See 69-82 above
Requested State.
76 K25A Relay (Synch Check) Driver Mismatch See 69-82 above
Requested State.
77-79 Trip Relay (ETR) Driver # Mismatch requested State. See 69-82 above
Terminal Board 2
80-82 Econ Relay Driver # Mismatch Requested State. See 69-82 above
Terminal Board 2
83-96 Relay contact feedback does not match the requested The relay contact or relay contact feedback monitor on the
state. The state of the command to the relay does not TREG/TREL/TRES terminal board has failed, or the cabling
match the state of the relay contact feedback signal; between VPRO and TREG/TREL/TRES is incorrect.
the relay cannot be reliably driven until corrected
83-85 Trip Relay (ETR) Contact # Mismatch requested State. See 83-96 above
Terminal Board 1
86-88 Econ Relay Contact # Mismatch Requested State. See 83-96 above
Terminal Board 1
89 Servo Clamp Relay Driver Mismatch (K4CL) See 83-96 above
Requested State. Terminal Board 1
90 K25A Relay (Synch Check) Contact The K25A relay contact feedback on the TREG/TREL/TRES
MismatchRequested State. Terminal Board 1 board has failed, or the K25A relay on TTUR has failed, or the
cabling between VPRO and TTUR is incorrect. The state of
the command to the K25A relay does not match the state of
the K25A relay contact feedback signal; cannot reliably drive
the K25A relay until the problem is corrected. The signal path
is from VPRO to TREG/TREL/TRES to TRPG/TRPL/TRPS to
VTUR to TTUR.
91-93 Trip Relay (ETR) Contact # Mismatch Requested See 83-96 above
State. Terminal Board 2
94-96 Econ Relay Contact # Mismatch Requested State. See 83-96 above
Terminal Board 2
97 TREG/TREL/TRES J3 Solenoid Power Source is The power detection monitor on the TREG1/TREL1/TRES1
Missing. The P125 V dc source for driving the trip board has failed, or there is a loss of P125 V dc through the
solenoids is not detected; cannot reliably drive the trip J2 connector from TRPG/TRPL/TRPS board, or the cabling
solenoids between VPRO and TREG1/TREL1/TRES1 or between
TREG1/TREL1/TRES1 and TRPG/TRPL/TRPS is incorrect.
98 TREG/TREL/TRES J4 Solenoid Power Source is The power detection monitor on the TREG2/TREL2/TRES2
Missing. The P125 V dc source for driving the trip board has failed, or there is a loss of P125 V dc through the
solenoids is not detected; cannot reliably drive the trip J2 connector from TRPG/TRPL/TRPS board, or the cabling
solenoids K4-K6 between VPRO and TREG2/TREL2/TRES2 or between
TREG2/TREL2/TRES2 and TRPG/TRPS/TRPL is incorrect.
Also trip relays K4-K6 may be configured when there is no
TREG2/TREL2/TRES2 board.
99-104 TREG/TREL/TRES Solenoid Voltage # Mismatch The trip solenoid # voltage monitor on TREG/TREL/TRES has
Requested State. The state of the trip solenoid # does failed or ETR # driver failed, or PTR # driver failed. There may
not match the command logic of the voted ETR # on be a loss of 125 V dc through the J2 connector from
TREG/TREL/TRES, and the voted primary trip relay TRPG/TRPL/TRPS, which has a separate diagnostic. See
(PTR) # on TRPG/TRPL/TRPS, the ETR cannot be (105-107)
reliably driven until corrected
105 TREL/TRES, J3, Solenoid Power, Bus A, Absent. The Loss of power bus A through J2 connector from TRPL/TRPS
voltage source for driving the solenoids is not detected
on Bus A; cannot reliably drive these solenoids
106 TREL/TRES, J3, Solenoid Power, Bus B, Absent. The Loss of power bus B through J2 connector from TRPL/TRPS
on Bus B; cannot reliably drive these solenoids
GEH-6421M
107 TREL/TRES, J3, Solenoid Power, Bus C, Absent. The Loss of Power Bus C through J2 connector from TRPL/TRPS
on Bus C; cannot reliably drive these solenoids
108 Control Watchdog Trip Protection Verify that the ContWdog is set up correctly in the toolbox and
This alarm can only occur if Configuration -> that the source of the signal is changing the value at least
ContWdogEn has been enabled. once a frame.
An alarm indicates that the signal space point ->

ContWdog has not changed for 5 consecutive frames. Check Ethernet cable and connections.
The alarm will reset itself if changes are seen for 60
seconds.
109 Speed Difference Trip Protection Verify that the Speed1 signal is set up correctly in the toolbox
This alarm can only occur if Configuration -> and that the source of the signal reflects the VTUR pulse rate
SpeedDifEnable has been enabled. speed.
An alarm indicates that the difference between the Check Ethernet cable and connections.
output signal Internal Points -> Speed1 and the first
VPRO pulse rate speed is larger than the percentage
Configuration -> OS_DIFF for more than 3 consecutive
frames. The alarm will reset itself if the difference is
within limits for 60 seconds.
110 Stale speed trip protection. Verify that the Speed1 signal is set up correctly in the toolbox
This alarm can only occur if Configuration -> and that the source of the signal reflects the VTUR pulse rate
StaleSpdEn has been enabled. An alarm indicates that speed input.
the signal Internal Points -> Speed1 has not changed
for 5 consecutive frames. The alarm will reset itself if Check Ethernet cable and connections.
the speed dithers for 60 seconds.
128-319 Logic Signal # Voting mismatch. The identified signal A problem with the input. This could be the device, the wire to
from this board disagrees with the voted value the terminal board, the terminal board, or the cable.
320-339 Input Signal # Voting mismatch, Local #, Voted #. The A problem with the input. This could be the device, the wire to
specified input signal varies from the voted value of the the terminal board, the terminal board, or the cable.
signal by more than the TMR Diff Limit
285
TPRO Emergency Protection
The Emergency Protection (TPRO) terminal board provides the VPRO with speed
signals, temperature signals, generator voltage, and bus voltage as part of an
independent emergency overspeed and synchronization protection system. The
protection system consists of triple redundant VPRO boards in a module separate
from the turbine control system, controlling the trip solenoids through TREx (TREG,
or TREL, or TRES). TPRO supplies inputs to all three VPRO boards. The following
figure shows the cabling to VPRO from the TPRO and TREx terminal boards.
The VPRO board provides the emergency trip function. Up to three trip solenoids
can be connected between the TREx and TRPx (TRPG, or TRPL, or TRPS) terminal
boards. TREx provides the positive side of the 125 V dc to the solenoids and TRPx
provides the negative side. Either board can trip the turbine. VPRO provides
emergency overspeed protection and the emergency stop functions. It controls the 12
relays on TREG, nine of which form three groups of three to vote inputs controlling
the three trip solenoids. A second TREG board may be driven from VPRO through
J4.
Note TPRO does not work with the Mark* VIe I/O packs.
286
The following figure shows how the VTUR and VPRO boards share in a gas turbine
protection scheme. Both detect turbine overspeed, and either one can independently
trip the turbine using the relays on TRPG or TREG.
TPRO Terminal Board VPRO- R8

Ethernet
x IONet x x x
x
x 1 JZ1
x 2
x 4 x 3 I RUN
x 5 O FAIL
x 6 N STAT
x 8 x 7 E 8 X
x 10 x 9 T 4 Y
x 12 x 11 T 2 Z
x 14 x 13 R 1
x 15 C
x 16 JZ5
x 18 x 17 S
x 20 x 19 JY1 E
x 22 x 21 Cables to VPRO-T8 R J6
x 24 x 23
x J P5
COM
5
JY5 P28A
x P28B
x 26 x 25 E
x 28 x 27 T
x 30 x 29 H
x 32 x 31 R
x 33 JX1 Cables to VPRO-S8 J J
x 34 P
x 36 x 35 JX5 3 4 P
A
38 x 37
x R O
x 40 x 39 A
x 41 W
x 42 F N L
x 44 x 43 E
x 45 VPRO
x 46 Cables to VPRO-R8 R
x 48
x 47 x x x
x
x
To TREG
Shield 37-pin "D" shell
Bar type connectors To Second TREG
with latching (optional)
BarrierType Terminal fasteners
TPRO Terminal Board, VPRO Board, and Cabling
GEH-6421M
VTUR Special speed cable
JR5 TTUR
JS5
JT5
J5
Two
JR1
xfrs
JS1
Optional 3 Relays
JT1
daughter- Gen Synch
board
335 V dc from <Q>
J3 J4 J5
JR1
TRPG
JS1
J3
JT1
To second
TRPG board 9 Relays
J4 J4 (optional) (3 x 3 PTR's)
J1
J2
125 VDC
Cable Trip Solenoids,

three circuits
J2 J1
TREG Trip signal to
JX1
TSVO TB's
JY1
VPRO
JZ1
J3
To second 12 Relays
J4 TREG Board
(9 ETR's,
(optional)
J5 3 econ. relays)
JH1
J6
P125 V dc from <PDM>
NEMA class F
Special speed cable

JX5 TPRO
JY5
J7
JZ5
JX1 2 transformers
JY1
125 VDC JZ1
Turbine Control and Protection Boards, Gas Turbine Control Example
288
Installation
The generator and bus potential transformers, analog inputs, and thermocouples are
wired to the first terminal block on TPRO. The magnetic speed pickups are wired to
the second block. Jumpers JP1A and JP1B are set to give either a 4-20 mA or voltage
input on the first of the three analog inputs.
The wiring connections are shown in the following figure. Two cables go to each of
the three VPRO boards.
Turbine Protection
JZ1
Terminal Board TPRO ma VOLTS
x JP1A
x 1 Gen (H) Gen
Gen (L) x 2
Bus (L) x 4
x 3 Bus (H) Volts OPEN RETURN
x 5 P24V1
20mA1 x 6
mAret x 8
x 7 VDC
Analog JP1B
x 9 P24V2
20mA2 x 10 Inputs
20mA3 x 12
x 11 P24V3
TC1R (L) x 14
x 13 TC1R (H)
15 To VPRO-T8
TC2R (L) 16
x TC2R (H)
x JZ5 JY1 J6
x 17 TC3R (H)
TC3R (L) x 18
x 19 TC1S (H)
TC1S (L) x 20
TC2S (L) x 22
x 21 TC2S (H) Thermocouple
24
x 23 TC3S (H) Inputs
TC3S (L) x
x
To J5
JY5
x
x 25 TC1T (H)
TC1T (L) x 26
x 27 TC2T (H)
TC2T (L) x 28
TC3T (L) x 30
x 29 TC3T (H) To VPRO-S8
JX1
MX1 (L) x 32
x 31 MX1 (H) J6
MX2 (L) x 34
x 33 MX2 (H)
To J5
MX3 (L) x 36
x 35 MX3 (H) Magnetic
x 37 MY1 (H) Speed JX5
MY1 (L) x 38
MY2 (L) x 40
x 39 MY2 (H) Pickups
x 41 MY3 (H) (MPU)
MY3 (L) x 42
MZ1 (L) x 44
x 43 MZ1 (H)
MZ2 (L) x 46
x 45 MZ2 (H)
x 47 MZ3 (H)
MZ3 (L) x 48
x
To J5
To VPRO-R8
Up to two #12 AWG wires per Terminal Blocks can be J6
point with 300 volt insulation unplugged from terminal board
for maintenance
TPRO Wiring and Cabling
GEH-6421M
Operation
The main purpose of the TPRO is to supply speed signals to VPRO for the
emergency overspeed (EOS) protection for the turbine. In addition, TPRO supplies
generator signals for backup synchronization check protection, three analog current
inputs, and nine thermocouple inputs, primarily for exhaust over-temperature
protection on gas turbines. VPRO provides 28 V dc to TPRO to power the three
analog input transmitters.
Speed Control and Overspeed Protection
Speed control and overspeed protection is implemented with six passive, magnetic
speed pickups. The first three are monitored by the controller, which uses the median
signal for speed control and the primary overspeed protection. The second three are
separately connected to the three VPROs in the protection module. Provision is made
for nine passive magnetic speed pickups or active pulse rate transducers (TTL type)
on the TPRO terminal board, with three being monitored by each of the three
VPROs.
Backup Synch Check Protection
TPRO provides inputs to the protection module for backup synchronization check.
The generator and bus voltages are supplied from two, single phase, potential
transformers (PTs) secondary output supplying a nominal 115 V rms. The maximum
cable length between the PTs and the turbine control is 100 meters of 18 AWG
twisted, shielded wire. Each PT is magnetically isolated with a 1,500 V rms rated
barrier and a circuit load less than 3 VA.
Each PT input is internally connected in parallel through TPRO to the three VPROs
in the protection module. The triple redundant phase slip windows result in a voted
logical output on the TREG terminal board, which drives the K25A relay. This
relay’s contacts are connected in series with the synch permissive relay (K25P) and
the auto synch relay (K25) to insure that no false command is issued to close the
generator breaker. Similarly, contacts from the K25A contact are connected in series
with the contacts from remote, manual synchronizing equipment to insure no false
commands.
Thermocouple and Analog Inputs
TPRO provides thermocouple and analog inputs to the protection module, primarily
for gas turbine applications. Nine thermocouple inputs are monitored with three
connected to each VPRO. These are generally used for backup exhaust over-
temperature protection. Also, one ±5, 10 V dc, 4-20 mA input, and two 4-20 mA
inputs can be connected to the TPRO terminal board, which feeds the inputs in
parallel to the three VPROs.
290
Terminal Board TPRO VPRO R8 VPRO S8 VPRO T8
1 Noise Suppression
JX1
Protection Protection Protection
Gen. Volts
120 V ac NS
2
from PT
Noise Suppression
3 ID
Bus Volts
120 Vac JY1 J6 J6 J6
NS
from PT 4
To TTUR 1
Thermocouple Inputs CJ
13
TC1RH NS
14 Three TC ccts to R8 ID
TC1RL NS 1 Overspeed Overspeed Overspeed
19 CJ
TC1SH NS JZ1 Em Stop Em Stop Em Stop
20 Three TC ccts to S8 Sync Sync Sync
TC1SL NS 1 Check Check Check
25 CJ
TC1TH NS Overtemp Overtemp Overtemp
26 Three TC ccts to T8
TC1TL NS ID
P28VV
5
P28V,R8
P24V1 Current P28V,S8
Limiter P28V,T8 J5 J5 J5
7
V dc VDC
6 JPA1
20mA1 20 ma
250 ohms To R8,S8,T8
8 J3
mAret J3 J3
One of the above ccts
Open Ret
JPB1
9 Current P28VV
P24V2 J4 J4 J4
Limiter
10
20 mA2
250
ohms To R8,S8,T8
Two of the above ccts
JX5
#1 MX1H 31 To TREG and
Filter
Emergency Clamp Trip Solenoids
Magnetic NS
MX1H 32 AC
Speed Coupling
Pickup 3 Circuits
ID
#2 MY1H 37 Filter
Emergency Clamp JY5
Magnetic NS
MY1L 38 AC
Speed Coupling
Pickup 3 Circuits
ID
#3 MZ1H 43 Filter
Emergency Clamp JZ5
Magnetic NS
MZ1L 44 AC
Speed Coupling
Pickup 3 Circuits ID
TPRO Terminal Board and TMR VPROs
GEH-6421M
Specifications
Item Specification
Number of Inputs 9 Passive proximity probes for speed pickups
1 Generator and 1 Bus Voltage
9 Thermocouples
1 4-20 mA current or voltage
2 4-20 mA current
Power Supply Voltage Input supply 28 V dc for the analog sensors
Magnetic Pickup (MPU) Output resistance 200 ohms with inductance of 85 mH.
Characteristics Output generates 150 V p-p into 60 K ohms at the TPRO terminal block, with insufficient
energy for a spark. The maximum short circuit current is approximately 100 mA.
The system applies up to 400 ohm normal mode load to the input signal to reduce the voltage
at the terminals.
MPU Cable Sensors can be up to 300 m (984 ft) from the cabinet, assuming that shielded pair cable is
used, with typical 70 nF single ended or 35 nF differential capacitance, and 15 ohms
resistance.
MPU Pulse Rate Range 2 Hz to 20 kHz
MPU Input Circuit Minimum signal is 27 mV pk at 2 Hz
Sensitivity Minimum signal is 450 mV pk at 14 kHz
Generator and Bus Two Single-Phase Potential Transformers, 115 V rms secondary.
Voltage Sensors Voltage accuracy is 0.5% of rated Volts rms.
Frequency Accuracy 0.05%.
Phase Difference Measurement better than 1 degree.
Allowable voltage range for synchronizing is 75 to 130 V rms.
Each input has a load of less than 3 VA.
Thermocouple Inputs Same specifications as for VTCC board
Analog Inputs 2 current inputs, 4-20 mA
1 current input with selection of 4-20 mA, or ±5 V dc, or ±10 V dc.
Same specifications as for VAIC board.
Size 17.8 cm Wide x 33.02 cm High (7.0 in x 13 in)
Diagnostics
VPRO makes diagnostic checks on TPRO and its cables and input signals as follows:
• If high or low limits on analog inputs are exceeded a fault is created.

L3DIAG_VPROR (or S, or T) occurs. The diagnostic signals can be
individually latched and then reset with the RESET_DIA signal if they go
healthy.
Terminal board connectors on TPRO have their own ID device that is interrogated by
the I/O board. The ID device is a read-only chip coded with the terminal board serial
number, board type, revision number, and plug location. When the chip is read by
VPRO and a mismatch is encountered, a hardware incompatibility fault is created.
292
Configuration
Configuration of the terminal board is by means of jumpers. For location of these
jumpers refer to the Installation diagram. The jumper choices are as follows:
• Jumper JPA1 selects either current input or voltage input

• Jumper JPB1 selects whether the return is connected to common or is left open
All other configuration is for VPRO and is done from the toolbox.
TREG Turbine Emergency Trip

The Gas Turbine Emergency Trip (TREG) terminal board provides power to three
emergency trip solenoids and is controlled by the I/O controller. Up to three trip
solenoids can be connected between the TREG and TRPG terminal boards. TREG
provides the positive side of the dc power to the solenoids and TRPG provides the
negative side. The I/O controller provides emergency overspeed protection,
emergency stop functions, and controls the 12 relays on TREG, nine of which form
three groups of three to vote inputs controlling the three trip solenoids.
There are a number of board types as follows:
• The H1A version is not used for new production and is replaced by H1B.
• H1B is the primary version for 125 V dc applications. Control power from the
JX1, JY1, and JZ1 connectors are diode combined to create redundant power on
the board for status feedback circuits and powering the economizing relays.
Power separation is maintained for the trip relay circuits.
• H2B is used for 24 V dc applications. All other features are the same as H1B.
• H3B is a special version of H1B for use in systems with redundant TREG
boards. Feedback circuit and economizing relay power is provided only by the
JX1 connector.
JY1 connector.
JZ1 connector.
In redundant TREG applications, it is typical to find one H3B and one H4B board
used together. It is important that system repairs be done with the correct board type
to maintain the control power separation designed into these systems.
Mark VI Systems
In Mark* VI systems, the VPRO works with the TREG terminal board. Cables with
molded plugs connect TREG to the VPRO module.
Mark VIe Systems
In Mark VIe systems, TREG is controlled by the PPRO pack on SPRO. The PPRO
I/O packs plug into the D-type connectors on SPRO. Cables with molded plugs
connect TREG to the SPRO board.
GEH-6421M
TREG Terminal Board
P125 Vdc
To TRPG
JH1 J1
x
x
x 2
x 1 J2
x 4
x 3 JZ1 To TSVO
x 6
x 5 termination
8
x 7
x
x 9 boards (SMX)
x 10
x 12
x 11
x 14
x 13
x 16
x 15
x 18
x 17 Cable to
x 20
x 19 JY1 Protection
x 22 x 21 VPRO
x 23 Module
x 24
x
x
x 26
x 25
x 28
x 27
x 30
x 29
x 32
x 31
x 33 JX1 Cable to
x 34 x 35
x 36
x 37 VPRO
x 38
x 40
x 39
x 42
x 41
x 44
x 43
x 46
x 45
x 48
x 47 Cable to
x
x
VPRO
Shield bar To second TREG

Barrier type terminal 37-pin D shell type
(optional)
blocks can be connectors with latching
unplugged from board fasteners
for maintenance
TREG Turbine Emergency Trip Terminal Board, and Protection Module I/O Controller
294
Installation
The three trip solenoids, economizing resistors, and the emergency stop are wired
directly to the first I/O terminal block. Up to seven trip interlocks can be wired to the
second terminal block. The wiring connections are shown in the following figure.
Note TREGH2B is a 24 V dc version of the terminal board.
Power 125V dc To TRPG, 12 wires To TSVO

boards on
SMX systems
Turbine Emergency Trip
J2 J1
Terminal Board TREG JH1
JZ1
x
x 1 SOL 1 or 4
PWR_N1 x 2
x 3 RES 1A
RES 1B x 4
6
x 5 SOL 2 or 5
PWR_N2 x
RES 2B x 8
x 7 RES 2A
x 9 SOL 3 or 6
PWR_N3 x 10
12
x 11 RES 3A
RES 3B x
14
x 13 E-TRP (H)
E-TRP (H) x
x 15
E-TRP (L) x 16 JUMPER
x 17
x 18
x 19 JY1 VPRO
x 20
x 21
x 22
x 23
x 24
x
x
x 25
x 26
x 27
x 28
PWR_P2 (for probe)
x 29
x 30 JX1 VPRO
x 32
x 31 PWR_P1 (for probe)
x 33
x 34
x 35 Contact TRP1 (H)
Contact TRP1 (L) x 36
x VPRO
Up to two #12 AWG wires per Terminal blocks can be unplugged

point with 300 volt insulation from terminal board for maintenance
TREG Terminal Board Wiring
Operation
TREG is entirely controlled by the VPRO protection module, and the only
connections to the control modules are the J2 power cable and through the trip
solenoids. In simplex systems a third cable carries a trip signal from J1 to the TSVO
terminal board, providing a servo valve clamp function upon turbine trip.
GEH-6421M
Control of Trip Solenoids
Both TRPG and TREG control the trip solenoids so that either one can remove
power and actuate the hydraulics to close the steam or fuel valves. The nine trip relay
coils on TREG are supplied with 28 V dc from the I/O controller. The trip solenoids
are supplied with 125 V dc through plug J2, and draw up to 1 A with a 0.1 second
L/R time constant.
Note The solenoid circuit has a metal oxide varistor (MOV) for current suppression
and a 10 Ω, 70 W economizing resistor.
A separately fused 125 V dc feeder is provided from the turbine control for the
solenoids, which energize in the run mode and de-energize in the trip mode.
Diagnostics monitor each 125 V dc feeder from the power distribution module at its
point of entry on the terminal board to verify the fuse integrity and the cable
connection.
Two series contacts from each emergency trip relay (ETR1, 2, 3) are connected to
the positive 125 V dc feeder for each solenoid, and two series contacts from each
primary trip relay (PTR1,2,3 in TRPG) are connected to the negative 125 V dc
feeder for each solenoid. An economizing relay (KE1, 2, 3) is supplied for each
solenoid with a normally closed contact in parallel with the current limiting resistor.
These relays are used to reduce the current load after the solenoids are energized.
The ETR and KE relay coils are powered from a 28 V dc source from the I/O
controller. Each I/O controller in each of the R8, S8, and T8 sections supplies an
independent 28 V dc source.
The 28 V dc bus is current limited and used for power to an external manual
emergency trip contact, shown as E-STOP. Three master trip relays (K4X, K4Y,
K4Z) disconnect the 28 V dc bus from the ETR, and KE relay coils if a manual
emergency trip occurs. Any trip that originates in either the protection module (such
as EOS) or the TREG (such as a manual trip) will cause each of the three protection
module sections to transmit a trip command over the IONet to the control module,
and may be used to identify the source of the trip.
In addition, the K4CL servo clamp relay will energize and send a contact feedback
directly from the TREG terminal board to the TSVO servo terminal board. TSVO
disconnects the servo current source from the terminal block and applies a bias to
drive the control valve closed. This is only used on simplex applications to protect
against the servo amplifier failing high.
Note The primary and emergency overspeed systems will trip the hydraulic trip
solenoids independent of this circuit.
296
Trip
Terminal Terminal Board TREG 
solenoid JX1
Board TRPG VPRO
1 or 4 KE1 KX1 KY1 KX1 RD
02 - + 01 section R8
KX2 J3
KY1 KZ1 RD
J2 J2 ID
Mon KX3 RD
04 KZ1 KX1
Optional
P28X1 Mon
economizing 03
resistor, K4X KX1,2,3
Trip solenoid 28 V dc
100 ohm,
2 or 5 KE2 KX2 KY2 
70W 04 - + 05 JY1
VPRO
KY1 RD
KY2 KZ2 section S8
J2 J2 J3
Mon
KY2 RD
KZ2 KX2 ID
08 KY3 RD
07
Trip P28Y1 Mon
solenoid K4Y KY1,2,3
28 V dc
3 or 6 KE3 KX3 KY3
06 - + 09
JZ1 
KY3 KZ3 KZ1 VPRO
J2 J2 RD section T8
Mon
KZ2 J3
KZ3 KX3 RD
12 ID
11 KZ3 RD
PWR_N1 02 P28Z1
for test
Mon
06
Sol pwr monitor K4Z KZ1,2,3
10 JX1 28 V dc
Mon JY1
J2 J2 JZ1
- N125V
+ P125V KE1,2,3 JX1
P28VV 2 JY1
30 RD
PWR_P1 JX1 3 JZ1
31 PWR_P2 JY1 Mon
for test probe JZ1 KE1,2,3
Three economizing relay circuits
Trip interlock
K4CL JX1 P125X seven circuits
To TSVO P28VV 2 To Exc 35 TRP1H
boards on J1
RD JY1 NS
3 JX1
SMX systems K4CL JZ1 36 TRP1L
K4CL JY1 TRP NS
Servo clamp JZ1
Mon 13
N125X
To relay 14 ETRPH
K25A on J2 P28VV CL
J2 16
TTUR JX1 K4X ETRPL
2 JY1 E-Stop
RD 15
3 JZ1 K4Y JUMPR
JH1 Mon
P125X K4Z 17 JUMPR
JX1
N125X
JY1 18 Second E-STOP
BCOM when applicable
JZ1
TREG Board, Trip Interlocks, and Trip Solenoids
Solenoid Trip Tests
Application software in the controller is used to initiate tests of the trip solenoids.
Online tests allow each of the trip solenoids to be manually tripped one at a time,
either through the PTR relays from the controller, or through the ETR relays from
the protection module. A contact from each solenoid circuit is wired back as a
contact input to give a positive indication that the solenoid has tripped. Primary and
emergency offline overspeed tests are provided too for verification of actual trips due
to software simulated trip overspeed conditions.
GEH-6421M
Specifications
Item Specification
Number of trip solenoids Three solenoids per TREG (total of six per I/O controller)
Trip solenoid rating H1 - 125 V dc standard with 1 A draw
H2 - 24 V dc is alternate with 1 A draw
Trip solenoid circuits Circuits rated for NEMA class E creepage and clearance
Circuits can clear a 15 A fuse with all circuits fully loaded
Solenoid inductance Solenoid maximum L/R time constant is 0.1 second
Suppression MOV across the solenoid
Relay outputs Three economizer relay outputs, two second delay to energize
Driver to breaker relay K25A on TTUR
Servo clamp relay on TSVO
Solenoid control relay Contacts are rated to interrupt inductive solenoid loads at 125 V dc, 1 A
contacts Bus voltage can vary from 70 to 145 V dc
Trip inputs Seven trip interlocks to the I/O controller protection module, 125/24 V dc
One emergency stop hard wired trip interlock, 24 V dc
Trip interlock excitation H1 - Nominal 125 V dc, floating, ranging from 100 to 145 V dc
H2 - Nominal 24 V dc, floating, ranging from 18.5 to 32 V dc
Trip interlock current H1 for 125 V dc applications:
Circuits draw 2.5 mA (50 Ω)
H2 for 24 V dc applications:
Circuits draw 2.5 mA (10 Ω)
Trip interlock isolation Optical isolation to 1500 V on all inputs
Trip interlock filter Hardware filter, 4 ms
Trip interlock ac voltage 60 V rms @ 50/60 Hz at 125 V dc excitation
rejection
Size 17.8 cm wide x 33.02 cm, high (7.0 in x 13.0 in)
Diagnostics
The I/O controller runs diagnostics on the TREG board and connected devices. The
diagnostics cover the trip relay driver and contact feedbacks, solenoid voltage,
economizer relay driver and contact feedbacks, K25A relay driver and coil, servo
clamp relay driver and contact feedback, and the solenoid voltage source. If any of
these do not agree with the desired value then a fault is created.
TREG connectors JX1, JY1, and JZ1 have their own ID device that is interrogated
by I/O controller. The ID device is a read-only chip coded with the terminal board
serial number, board type, revision number, and the plug location. When the chip is
read by the I/O board and a mismatch is encountered, a hardware incompatibility
fault is created.
Configuration
There are no switches on the terminal board.
Note A jumper must be placed across terminals 15 and 17 if the second emergency
stop input is not required.
298
VRTD RTD Input
VRTD RTD Input
The Resistance Temperature Device (RTD) Input (VRTD) board accepts 16, three-
wire RTD inputs. These inputs are wired to a RTD terminal board (TRTD or
DRTD). Cables with molded fitting connect the terminal board to the VME rack
where the VRTD processor board is located.
VRTD excites the RTDs and the resulting signals return to the VRTD. VRTD
converts the inputs to digital temperature values and transfers them over the VME
backplane to the VCMI, and then to the controller.
TRTD Terminal Board VRTD VME Board
x
x
x 2
x 1 TRTD capacity for RUN
x 4
x 3 FAIL
8 RTD x 5 16 RTD inputs STAT
x 6
inputs x 8
x 7
x 10
x 9
x 12
x 11
x 14
x 13 VME bus to VCMI
x 16
x 15
x 18
x 17
x 20
x 19 JA1 37-pin "D" shell
x 22
x 21
x 23 type connectors
x 24 with latching
x
fasteners
x
x 26
x 25
x 28
x 27
8 RTD x 30
x 29
inputs x 32
x 31
x 33 JB1
x 34
x 36
x 35
x 38
x 37 Cables to VME
x 40
x 39 I/O rack
VRTD
x 42
x 41 x
x 44
x 43
x 46
x 45 Connectors on J3
x 48
x 47 VME I/O rack
x
x
Shield
bar
J4
Barrier type terminal

from board for
maintenance
RTD Input Terminal Board, I/O Board, and Cabling
299
Volume II VRTD RTD Input • 265
Installation

its edge connectors
Operation
VRTD supplies a 10 mA dc multiplexed (not continuous) excitation current to each
RTD through the terminal board. The resulting signal returns to VRTD. The VCO
type A/D converter uses voltage to frequency converters and sampling counters. The
converter samples each signal and the excitation current four times per second for
normal mode scanning and 25 times per second for fast mode scanning, using a time
sample interval related to the power system frequency. Software in the digital signal
processor performs the linearization for the selection of 15 RTD types.
RTD open and short circuits are detected by out of range values. An RTD that is
determined to be outside the hardware limits is removed from the scanned inputs to
prevent adverse effects on other input channels. Repaired channels are reinstated
automatically in 20 seconds or can be manually reinstated.
In triple modular redundant (TMR) configuration, TRTDH1B provides redundant

RTD inputs by fanning the inputs to three VRTD boards in the R, S, and T racks. All
RTD signals have high frequency decoupling to ground at signal entry. RTD
multiplexing is coordinated by redundant pacemakers so that the loss of a single
cable or VRTD does not cause the loss of any RTD signals in the control database.
VRTD boards in R, S, and T read RTDs simultaneously. The RTDs read by each
VRTD differ by two RTDs, such that when R reads RTD3, S reads RTD5, and T
reads RTD7, and so on. This ensures that the same RTD is not excited by two
VRTDs simultaneously and hence produce bad readings.
266 • VRTD RTD Input 300 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
<R> or <S> or <T> I/O rack
Termination RTD Input Board VRTD

Board TRTD
Noise
J3 Excit.
suppression JA1
Excitation
RTD
Signal NS
I/O Core
Return Processor
TMS320C32
Grounded or
ungrounded (8) RTDs Connectors
ID at
bottom of A/D Processor VMEbus
VME Bus
VME rack
Noise
JB1 J4 Excit.
suppression
Excitation
RTD
Signal NS
Return VCO type A/D
Grounded or converter
(8) RTDs
ungrounded
ID
RTD Inputs and Signal Processing, Simplex System
301
Signals
TerminalBoard TRTDH1B PM= Pacemaker
Tx = VRTD transmit
Rx = VRTD receive
Noise
JRA
suppression ID
Excitation
RTD PM, Tx
Signal NS PM, Rx, S
Return JSA
ID
Grounded or
ungrounded PM, Tx
(8) RTDs to JRA, JSA, JTA
PM, Rx, R
JTA
ID
PM, Tx
PM, Rx, R
Noise JRB
suppression ID
Excitation
RTD PM, Tx
Signal NS PM, Rx, T
Return JSB
ID
Grounded or
ungrounded (8) RTDs to JRB, JSB, JTB PM, Tx
PM, Rx, T
JTB
ID
PM, Tx
PM, Rx, S
RTD Inputs and Connections to three VRTD Processors in TMR System
Specifications
Item Specification
Number of channels 16 channels per VRTD board
RTD types 10, 100, and 200 Ω platinum
10 Ω copper
120 Ω nickel
Span 0.3532 to 4.054 V
A/D converter resolution 14-bit resolution
Scan Time Normal scan 250 ms (4 Hz)
Fast scan 40 ms (25 Hz)
Power consumption Less than 12 W
Measurement accuracy See Tables
GEH-6421M
Item Specification
Common mode rejection Ac common mode rejection 60 dB @ 50/60 Hz
Dc common mode rejection 80 dB
Common mode voltage range ±5 V
Normal mode rejection Rejection of up to 250 mV rms is 60 dB @ 50/60 Hz system frequency for normal scan
Maximum lead resistance 15 Ω maximum two way cable resistance
Fault detection High/low (hardware) limit check
High/low (software) system limit check
Failed ID chip
RTD Accuracy
RTD Type Group Gain Accuracy at 400 ºF
120 Ω nickel 120 Ω nickel 2 ºF
200 Ω platinum Normal_ 1.0 2 ºF
100 Ω platinum -51 to 240ºC (- 60 ºF to 400 ºF) Gain_ 2.0 2 ºF
10 Ω copper 10 Ω Cu_10 10 ºF
RTD Types and Ranges
RTD inputs are supported over a full-scale input range of 0.3532 to 4.054 V. The
following table shows the types of RTD used and the temperature ranges.
RTD Type Name/Standard Range °C Range °F

10 Ω copper MINCO_CA GE 10 Ω Copper -51 to +260 -60 to +500
100 Ω platinum SAMA 100 -51 to +593 -60 to +1100
100 Ω platinum DIN 43760 -51 to +700 -60 to +1292
IEC-751
MINCO_PD
MINCO_PE
PT100_DIN
100 Ω platinum MINCO_PA -51 to +700 -60 to +1292
IPTS-68
PT100_PURE
100 Ω platinum MINCO_PB -51 to +700 -60 to +1292
Rosemount 104
PT100_USIND
120 Ω nickel MINCO_NA -51 to +249 -60 to +480
N 120
200 Ω platinum PT 200 -51 to +204 -60 to +400
303
Diagnostics
Three LEDs at the top of the VRTD front panel provide status information. The
normal RUN condition is a flashing green and FAIL is a solid red. The third LED is
normally off, but shows a steady orange if a diagnostic alarm condition exists in the
board. Diagnostic checks include the following:
• Each RTD type has hardware limit checking based on preset (non-configurable)
high and low levels set near the ends of the operating range. If this limit is
exceeded, a logic signal is set and the input is no longer scanned. If any one of
the input’s hardware limits is set, it creates a composite diagnostic alarm,
L3DIAG_VRTD, referring to the entire board. Details of the individual
• Each RTD input has system limit checking based on configurable high and low
levels. These limits can be used to generate alarms, and can be configured for
enable/disable, and as latching/non-latching. RESET_SYS resets the out of limit
signals. In TMR systems, limit logic signals are voted and the resulting
composite diagnostic is present in each controller.
• The resistance of each RTD is checked and compared with the correct value, and
if high or low, a fault is created.
• Each connector has its own ID device, which is interrogated by the I/O
processor board. The terminal board ID is coded into a read-only chip containing
the terminal board serial number, board type, revision number, and the
connector location. If a mismatch is encountered, a hardware incompatibility
fault is created.
Configuration
Module Parameter Description Choices

Configuration
System limits Enable or disable all system limit Enable, disable
checking
Auto reset Enable or disable restoring of RTDs Enable, disable
removed from scan
Group A rate Sampling rate and system 4 Hz, 50 Hz filter
frequency filter for first group of 8 4 Hz, 60 Hz filter
inputs
25 Hz
Group A gain Gain 2.0 is for higher accuracy if Normal_1.0
ohms <190, first group of 8 inputs Gain_2.0
10 ohm Cu_10.0
Group B rate Sampling rate and system 4 Hz, 50 Hz filter
frequency filter for second group of 4 Hz, 60 Hz filter
8 inputs
25 Hz
Group B gain Gain 2.0 is for higher accuracy if Normal_1.0
ohms <190, second group of 8 Gain_2.0
inputs
10 ohm Cu_10.0
J3J4:IS200TRTDH1C Terminal board Connected, not connected
RTD1 First of 16 RTDs - Board point Point edit (input FLOAT)
signal
GEH-6421M
Module Parameter Description Choices
RTDRTD type RTDs linearizations supported by Unused
VRTD;VRTD select RTDRTD or CU10 MINCO_CA
Ohms Input (unused inputs are
removed from scanning) PT100_DIN MINCO_PD
PT100_PURE MINCO_PA
PT100_USIND MINCO_PB
N120 MINCO_NA
MINCO_PIA PT100_SAMA
PT200 MINCO_PK
Ohms
SysLim1 Enable Enables or disables a temperature Enable, disable
limit for each RTD,RTD can be used
to create an alarm
SysLim1 Latch Determines whether the limit Latch, unlatch
condition will latch or unlatch for
each RTD;RTD reset used to
unlatch.
SysLim1 Type Limit occurs when the temperature Greater than or equal
is greater than or equal (>=), or less Less than or equal
than or equal to (<=) a preset value.
System Limit 1 Enter the desired value of the limit -60 to 1,300
temperature, Deg F or Ohms
SysLim2 Enable Enables or disables a temperature Enable, disable
limit which can be used to create an
alarm
SysLim2 Latch Determines whether the limit Latch, unlatch
condition will latch or unlatch; reset
used to unlatch.
SysLim2 Type Limit occurs when the temperature Greater than or equal
is greater than or equal (>=), or less Less than or equal
than or equal to (<=) a preset value.
System Limit 2 Enter the desired value of the limit -60 to 1,300
temperature, Deg F or Ohms
TMR Diff Limt Limit condition occurs if 3 -60 to 1,300
temperatures in R,S,T differ by
more than a preset value; this
creates a voting alarm condition.
Board Point Signals Description-Point Edit (Enter Signal Connection) Direction Type
L3DIAG_VRTD1 Board diagnostic Input BIT
SysLim1RTD1 System limit 1 Input BIT
: : Input BIT
: : Input BIT
305
Alarms
2 Flash Memory CRC Failure Board firmware programming error (board will not go online)
3 CRC failure override is Active Board firmware programming error (board is allowed to go online)
16 System Limit Checking is Disabled System checking was disabled by configuration.
30 ConfigCompatCode mismatch; Firmware: A tre file has been installed that is incompatible with the firmware on
[ ]; Tre: [ ]. The configuration compatibility the I/O board. Either the tre file or firmware must change. Contact
code that the firmware is expecting is the factory.
different than what is in the tre file for this
board
31 IOCompatCode mismatch; Firmware: [ ] ; A tre file has been installed that is incompatible with the firmware on
Tre: [ ] The I/O compatibility code that the the I/O board. Either the tre file or firmware must change. Contact
firmware is expecting is different than what the factory.
is in the tre file for this board
32- 47 RTD [ ] high voltage reading, Counts are An RTD wiring/cabling open, or an open on the VRTD board, or a
Y VRTD hardware problem (such as multiplexer), or the RTD device
has failed.
48- 63 RTD [ ] low voltage reading, Counts are Y An RTD wiring/cabling short, or a short on the VRTD board, or a
VRTD hardware problem (such as multiplexer), or the RTD device
has failed.
64- 79 RTD [ ] high current reading, Counts are Y The current source on the VRTD is bad, or the measurement device
has failed.
80- 95 RTD [ ] low current reading, Counts are Y An RTD wiring/cabling open, or an open on the VRTD board, or a
VRTD hardware problem (such as multiplexer), or the RTD device
has failed.
96- 111 RTD [ ] Resistance calc high, it is Y The wrong type of RTD has been configured or selected by default,
Ohms. RTD [ ] has a higher value than the or there are high resistance values created by faults 32 or 35, or
table and the value is Y both 32 and 35.
112- RTD [ ] Resistance calc low, it is Y Ohms. The wrong type of RTD has been configured or selected by default,
127 TRD [ ] has a lower value than the table or there are low resistance values created by faults 33 or 34, or
and the value is Y both 33 and 34.
128- Voltage Circuits for RTDs, or Current Internal VRTD problems such as a damaged reference voltage
151 Circuits for RTDs have Reference raw circuit, or a bad current reference source, or the voltage/current null
counts high or low, or Null raw counts high multiplexer is damaged.
or low
152 Failed one Clock Validity Test, scanner still VME board, terminal board, or cable could be defective.
running. In TMR mode, the firmware tests
whether the three TMR boards are
synchronized and will stop scanning inputs
under certain conditions
153 Failed one Phase Validity Test, scanner VME board, terminal board, or cable could be defective.
still running. In TMR mode, the firmware
tests whether the three TMR boards are
GEH-6421M
154 Failed both Clock Validity Tests, scanner VME board, terminal board, or cable could be defective.
shutdown. In TMR mode, the firmware
tests whether the three TMR boards are
155 Terminal Board connection(s) wrong. Check cable connections.
Cables crossed between <R>, <S>, and
<T>
156 25 Hz Scan not Allowed in TMR Mode, Configuration error. Choose scan of 4 Hz_50 Hz Fltr or 4 Hz_60 Hz
please reconfigure Fltr.
160- Logic Signal [ ] Voting mismatch. The A problem with the input. This could be the device, the wire to the
255 identified signal from this board disagrees terminal board, the terminal board, or the cable.
with the voted value.
256- Input Signal [ ] Voting mismatch, Local [ ], A problem with the input. This could be the device, the wire to the
271 Voted [ ]. The specified input signal varies terminal board, the terminal board, or the cable.
from the voted value of the signal by more
than the TMR Diff Limit
TRTD RTD Input

The RTD Input (TRTD) terminal board accepts 16, three-wire RTD inputs. These
inputs are wired to two barrier type terminal blocks. The inputs have noise
suppression circuitry to protect against surge and high frequency noise. TRTD
communicates with one or more I/O processors, which convert the inputs to digital
temperature values and transfer them to the controller.
There are four versions of TRTD as follows:
• TRTDH1B is a TMR version that fans out the signals to three VRTD boards
using six DC-type connectors.
• TRTDH1C is a simplex board with two DC-type connectors for VRTD.
• TRTDH1D is a simplex board with two DC-type connectors for PRTD, normal
scan.
• TRTDH2D is a simplex board with two DC-type connectors for PRTD, fast
scan.
Mark VI Systems
In the Mark* VI system, TRTDH1B and TRTDH1C works with the VRTD
processor and supports simplex and TMR applications. One TRTDH1C connects to
the VRTD with two cables. In TMR systems, TRTDH1B connects to three VRTD
processors with six cables.
Mark VIe Systems
In the Mark VIe system, TRTDH1D and TRTDH2D works with the PRTD I/O pack
and support simplex applications only. Two PRTD packs plug into the TRTD for a
total of 16 inputs.
307
TRTDH1C, H1D, H2D Terminal Board TRTDH1B Terminal Board
TRTD capacity for
+ 16 RTD inputs +
2 1 1
3 2
4 4 3
Eight RTD 6 5 DC-37 pin 5 JTA JTB
7 Connectors Eight RTD 6
Inputs 8 8 7
10 9 With latching Inputs 9
11 10
12 fasteners 12 11
14 13 13
15 14
16 16 15
18 17 17
19 18
20 JA1 20 19
22 21 21
23 22 JSA JSB
24 24 23
J Ports:
26 25 Plug in PRTD I/O Pack(s) 25

27 26
28 for Mark VIe 28 27
Eight RTD 30 29 29
31 or Eight RTD 30
Inputs 32 JB1 Cable(s) to VRTD 32 31
33 Inputs 33
34 35 34 JRA JRB
36 board(s) for Mark VI; 35
37 36 37
38 39 38
40 the number and location 40 39
42 41 41
43 depends on the level of 42
44 44 43
45 redundancy required . 45
46 47 46
48 47
48
+ +
Shield Barrier Type terminal

Bar Blocks can be unplugged
from board formaintenance
RTD Input Terminal Boards
Installation
Connect the wires for the 16 RTDs directly to the two terminal blocks on the
terminal board. Each block is held down with two screws and has 24 terminals
accepting up to #12 AWG wires. A shield terminal strip attached to chassis ground is
located immediately to the left of each terminal block.
For CE mark applications, double-shielded wire must be used.

All shields must be terminated at the shield terminal strip. Do
not terminate shields located at the end device.
GEH-6421M
In a TMR Mark VI system, TRTDH1B provides redundant RTD inputs by fanning
the inputs to three VRTD boards in the R, S, and T racks. The inputs meet the same
environmental, resolution, suppression, and function requirements and codes as the
TRTDH1C terminal board; however, the fast scan is not available.
RTD Terminal Board TRTDH1C
Screw Connections Screw Connections

x
x 1 Input 1 (Exc)
Input 1 (Sig) x 2
x 3 Input 1 (Ret)
Input 2 (Exc) x 4
Input 2 (Ret)
x 5 Input 2 (Sig)
x 6
x 7 Input 3 (Exc)
Input 3 (Sig) x 8
x 9 Input 3 (Ret)
Input 4 (Exc) x 10
Input 4 (Ret)
x 11 Input 4 (Sig)
x 12
Input 5 (Sig)
x 13 Input 5 (Exc)
x 14
Input 6 (Exc) x 15 Input 5 (Ret) JA1
x 16
x 17 Input 6 (Sig)
Input 6 (Ret) x 18
x 19 Input 7 (Exc)
Input 7 (Sig) x 20
x 21 Input 7 (Ret) First 8 RTDs
Input 8 (Exc) x 22 J-Port Connections:
x 23 Input 8 (Sig) to JA1
Input 8 (Ret) x 24
x Plug in PRTD I/O Pack(s) for
Mark VIe
x
or
x 25 Input 9 (Exc)
Input 9 (Sig) x 26
x 27 Input 9 (Ret)
Input 10 (Exc) x 28 Cable to VRTD I/O board(s) for
Input 10 (Ret)
x 29 Input 10 (Sig)
x 30 Mark VI;
x 31 Input 11 (Exc)
Input 11 (Sig) x 32 JB1
Input 12 (Exc)
x 33 Input 11 (Ret) The number and location
x 34
x 35 Input 12 (Sig) depends on the number of
Input 12 (Ret) x 36
Input 13 (Sig)
x 37 Input 13 (Exc) inputs required.
x 38 Second 8
x 39 Input 13 (Ret)
Input 14 (Exc) x 40 RTDs to JB1
Input 14 (Ret)
x 41 Input 14 (Sig)
x 42
Input 15 (Sig) x 43 Input 15 (Exc)
x 44
Input 16 (Exc)
x 45 Input 15 (Ret)
x 46
x 47 Input 16 (Sig)
Input 16 (Ret) x 48
x
A Excxx
Application Note:
- Optional Ground: connnect the B wire to ground;
RTD
- RTD Group wiring, that is sharing the B wire;
B Sigxx
tie the B wires together at the RTDs,
C
Retxx tie the Sigxx signals together at the TRTD terminal
b board, and interconnect with one wire.
TRTDH1C RTD Terminal Board Wiring
309
Operation
TRTD supplies a 10 mA dc multiplexed (not continuous) excitation current to each
RTD, which can be grounded or ungrounded. The 16 RTDs can be located up to 300
m (984 ft) from the turbine control cabinet with a maximum two-way cable
resistance of 15 Ω.
The A/D converter in the I/O processor samples each signal and the excitation
current four times per second for normal mode scanning and 25 times per second for
fast mode scanning, using a time sample interval related to the power system
frequency. Software performs the linearization for the selection of 15 RTD types.
RTD open and short circuits are detected by out-of-range values. An RTD that is
determined to be outside the hardware limits is removed from the scanned inputs to
prevent adverse effects on other input channels. Repaired channels are reinstated
automatically in 20 seconds or can be manually reinstated.
All RTD signals have high-frequency decoupling to ground at signal entry. RTD
multiplexing in the I/O processor is coordinated by redundant pacemakers so that the
loss of a single cable or I/O processor does not cause the loss of any RTD signals in
the control database.
TRTDH1C RTD I/O Processor Board

Terminal Board
I/O Processor is either
remote (Mark VI) or
Noise Excitation
suppression JA1 local (Mark VIe)
Excitation
RTD To
Signal NS controller
Return A/D
Processor VMEbus
Conv
Grounded or
ungrounded ID
(8) RTDs
Noise
Suppression JB1
Excitation
RTD
Signal NS JB1 cables to I/O processor
VRTD for Mark VI systems
Return or
Grounded or connects to PRTD I/O pack
ungrounded for Mark VIe systems
(8) RTDs ID
TRTD (Simplex) Inputs and Signal Processing
GEH-6421M
Signals
TerminalBoard TRTDH1B PM= Pacemaker
Tx = VRTD transmit
Rx = VRTD receive
Noise
JRA
suppression ID
Excitation
RTD PM, Tx
Signal NS PM, Rx, S
Return JSA
ID
Grounded or
ungrounded PM, Tx
(8) RTDs to JRA, JSA, JTA
PM, Rx, R
JTA
ID
PM, Tx
PM, Rx, R
Noise JRB
suppression ID
Excitation
RTD PM, Tx
Signal NS PM, Rx, T
Return JSB
ID
Grounded or
ungrounded (8) RTDs to JRB, JSB, JTB PM, Tx
PM, Rx, T
JTB
ID
PM, Tx
PM, Rx, S
TRTDH1 TMR-Capable RTD Terminal Board
Specifications
Item Specification
Number of channels Eight channels per terminal board
RTD types 10, 100, and 200 Ω platinum
10 Ω copper
120 Ω nickel
Span 0.3532 to 4.054 V
Maximum lead resistance 15 Ω maximum two-way cable resistance
High/low (software) system limit check
Failed ID chip
311
RTD Accuracy
RTD Type Group Gain Accuracy at 400 ºF
120 Ω nickel 120 Ω nickel 2 ºF
100 Ω platinum -51 to 240ºC (- 60 ºF to 400 ºF) Gain_ 2.0 2 ºF
10 Ω copper 10 Ω Cu_10 10 ºF
RTD Types and Ranges
RTD inputs are supported over a full-scale input range of 0.3532 to 4.054 V. The
following table shows the types of RTD used and the temperature ranges.
RTD Type Name/Standard Range °C Range °F

10 Ω copper MINCO_CA GE 10 Ω Copper -51 to +260 -60 to +500
100 Ω platinum SAMA 100 -51 to +593 -60 to +1100
100 Ω platinum DIN 43760 -51 to +700 -60 to +1292
IEC-751
MINCO_PD
MINCO_PE
PT100_DIN
100 Ω platinum MINCO_PA -51 to +700 -60 to +1292
IPTS-68
PT100_PURE
100 Ω platinum MINCO_PB -51 to +700 -60 to +1292
Rosemount 104
PT100_USIND
120 Ω nickel MINCO_NA -51 to +249 -60 to +480
N 120
200 Ω platinum PT 200 -51 to +204 -60 to +400
GEH-6421M
Diagnostics
Diagnostic checks include the following:
• Each RTD type has hardware limit checking based on preset (non-configurable)
high and low levels set near the ends of the operating range. If this limit is
exceeded, a logic signal is set and the input is no longer scanned. If any one of
the input’s hardware limits is set, it creates a composite diagnostic alarm,
L3DIAG_xxxx, referring to the entire board. Details of the individual
• Each RTD input has system limit checking based on configurable high and low
levels. These limits can be used to generate alarms, and can be configured for
enable/disable, and as latching/non-latching. RESET_SYS resets the out of limit
signals. In TMR systems, limit logic signals are voted and the resulting
composite diagnostic is present in each controller.
• The resistance of each RTD is checked and compared with the correct value, and
if high or low, a fault is created.
• Each connector has its own ID device, which is interrogated by the I/O
processor board. The terminal board ID is coded into a read-only chip containing
the terminal board serial number, board type, revision number, and the
connector location. If a mismatch is encountered, a hardware incompatibility
fault is created.
Configuration
DRTD Simplex RTD Input

The Simplex RTD Input (DRTD) terminal board is a compact RTD terminal board
designed for DIN-rail mounting. The board has eight RTD inputs and connects to the
VRTD processor board with a single cable. This cable is identical to those used on
the larger TRTD terminal board. The terminal boards can be stacked vertically on the
DIN-rail to conserve cabinet space. Two DRTD boards can be connected to VRTD
for a total of 16 temperature inputs. Only a simplex version of the board is available.
Note The DRTD board does not work with the PRTD I/O pack.
Installation
Note There is no shield terminal strip with this design.
Mount the plastic holder on the DIN-rail and slide the DRTD board into place.
Connect the wires for the eight RTDs directly to the terminal block. The Euro-Block
type terminal block has 36 terminals and is permanently mounted on the terminal
board. Typically #18 AWG wires (shielded twisted triplet) are used. Terminals 25
through 34 are spares. Two screws, 35 and 36, are provided for the SCOM (ground)
connection, which should be as short a distance as possible.
Note SCOM must be connected to ground.
313
Notes
314 of 1016
VSCA Serial Communication
Input/Output
VSCA Serial Communication Input/Output

The Serial Communication Input/Output (VSCA) board provides I/O interfaces for
external devices using RS-232C, RS-422, and RS-485 serial communications.
Currently the IS200VSCAH2A version is available. The DSCB terminal board
connects to the external devices, which include intelligent pressure sensors such as
® ®
smart Honeywell pressure transducers and Kollmorgen electric drives.
VSCA connects to the DSCB terminal board(s) through the J6 and J7 front panel
connectors. These are parallel connected using 37-pin D shell connectors with group
shielded twisted pair wiring. For RS-422 and RS-485, DSCB can interface with
external devices at distances up to 1000 ft, at baud rates up to 375 kbps. For RS-
232C, the distance is only 50 ft or 2500 pF of cable capacitance (including the cable
from VSCA to the DSCB). It supports short haul modems for longer distances.
Installation
1 Power down the VME I/O processor rack.

its edge connectors.
3 Tighten the captive screws at the top and bottom of the front panel.
connectors on the front panel. These are latching type connectors to secure the
cables. Power up the VME rack and check the diagnostic lights at the top of the
front panel; for details refer to the section on diagnostics in this document.
It may be necessary to update the VSCA firmware to the latest level. For
instructions, refer to GEH-6403 Control System Toolbox for the Mark VI Turbine
Controller.
315
Volume II VSCA Serial Communication Input/Output • 317
Operation
Note VSCA/DSCB is a data terminal device (DTE).
The VSCA is a single slot board with six serial communication ports. Each port can
be independently configurable as an RS-232C, RS-485, or RS-422 interface, using a
three-position group jumper (berg array). Both RS-232C and R-S422 support full
duplex. The line drivers on VSCA include appropriate termination resistors with
configurable jumpers to accommodate multi-drop line networks. RS-422 and RS-485
outputs have tri-state capability. I/O goes to a high impedance condition when
powered down. They do not cause significant disturbance when powered down/up
(less than 10 ms) on a party line. The open wire condition on a receiver is biased to a
high state.s
• RS-232C supports: RXD, TXD, DTR/RTS, GND, CTS (five wire)

• RS-422 supports: TX+, TX-, RX+, RX-, GND
• RS-485 supports: TX/RX+, TX/RX-, GND
Data Flow from VSCA to Controller
The data flow from VSCA to the UCV_ controller is of two types: fixed I/O and
®
Modbus I/O. Fixed I/O is associated with the smart pressure transducers and the
Kollmorgen electric drive data. This data processes completely, every frame, as with
conventional I/O. The required frame rate is 100 Hz. These signals are mapped into
signal space, using the .tre file, and have individual health bits, use system limit
checking, and have offset/gain scaling.
Note Two consecutive time outs are required before a signal is declared unhealthy.
Diagnostic messages are used to annunciate all communication problems.
Modbus I/O is associated with the Modbus ports. Because of the quantity of these
signals, they are not completely processed every frame. Instead they are packetized
and transferred to the UCV_ processor over the IONet through a special service. This
accommodates up to 2400 bytes at 4 Hz, or 9600 bytes at 1 Hz, or combinations
thereof. This I/O is known as second class I/O, where coherency is at the signal level
only, not at the device or board level. Health bits are assigned at the device level, the
UCV_ expands (fully populate) for all signals, and system limit checking is not
performed.
Ports 1 and 2 only (as an option) support the Honeywell pressure configuration. It
reads inputs from the Honeywell smart pressure transducers, type LG-1237. This
service is available on ports 1 and 2 as an option (pressure transducers or Modbus, or
drives). The pressure transducer protocol uses the XDSAG#AC interface board and
RS-422. Each port can service up to six transducers. The service is 375 kbaud,
asynchronous, and with nine data bits (11 bits including start and stop). It includes
the following failsafe features:
• Communication miss counters, one per device, and associated diagnostics

• After four consecutive misses it forces the input pressure to 1.0 psi, and posts a
diagnostic. After four consecutive hits (good values) it removes the forcing and
the diagnostic.
Three ports (any three, but no more than three) support the Kollmorgen electric
drive. It communicates with a Kollmorgen electric fast drive FD170/8R2-004 at a
19200 baud rate, point-to-point, using RS-422.
318 • VSCA Serial Communication Input/Output 316 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Modbus service
The current Modbus design supports the master mode. However the design does not
prevent the future enhancement of Modbus slave mode of operation. It is
configurable at the port level as follows:
• Used, not used

• Baud Rate RS-232C: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600
• Baud Rate RS-485/422: 19200, 38400, 57600, 115000
• Parity: none, odd, even
• Data bits: seven, eight
• Stop bits: one, two
• Station addresses
• Multi-drop, up to eight devices per port; maximum of 18 devices per board
• RTU
• Time out (seconds) per device
The Modbus service is configurable at the signal level as follows:
• Signal type
• Register number
• Read/write
• Transfer rate, 0.5, 1, 2, or 4 Hz
• Scaling, offset, and gain
The service supports function codes 1-7, 15, and 16. It also supports double 16-bit
registers for floating point numbers and 32-bit counters. It periodically tries 20
attempts to reestablish communications with a dead station. The VSCA and toolbox
support type casting and scaling of all I/O signals to/from engineering units, for both
fixed I/O and Modbus I/O.
Physical interfaces
Special connections are required for RS-485 applications with VSCA/DSCB located
somewhere in the middle of the transmission path. Because of the potential length of
the connection between VSCA and DSCB, there may be substantial stub length to
the connection that will affect signal quality. For this reason, VSCA supports the
connection of two DSCB boards wired in parallel. This permits RS-485 signals to
come in one DSCB, pass through VSCA with the RS-485 transceiver, and go out the
opposite DSCB. This ensures that the stub-length of the RS-485 path is minimized.
Note The above arrangement is not required when the VSCA/DSCB is located at
one end of the RS-485 wiring.
317
The following figure shows the physical interface to the electric drives. For the
Honeywell transducer interface using DSCB and DPWA, refer to the section, DSCB
Serial Input/Output.
Twisted shielded pair

AWG#18 min, up to
1000 ft, ground shields at
Mark VI end only
Mark VI Control J2
8+ Electric Drive
9 - Rx FD170/8F2-004
4+
6 - Tx
5 Grd
V D J4
S S 3
C C 6 Enable
A B 7 P24 V
8 enable
31 Crit fault
32 relay Chassis
J1 J4 23 18 20 22
4 5 1 2 3 6 30 27 17 19 21 28
+
T 125 V dc power
R -
Ph PhPhGrd
V L Ref Sin Cos
A B C
C Y Drive enable relay
C
T L4FMVn_ENAX
C Enable = Close
B
C
I Contact input
L5FMVn_CFZ 1 2 3 5 46 7 8 FE A BDCG
Fault = Open Motor Grd Ther Resolver
Motor
frame
Shield
(int)
exc 1
exc 2 Actuator/Valve
sec2 3 L
V
sec2 4 D
sec1 5 T
sec1 6
V T
S S Monitoring signals
V V
O O
VSCA Interface to Electric Servo Drive using DSCB Board
GEH-6421M
Specifications
Item Specification
Number of Serial Ports 6 per VSCA board
Devices Port Pressure Transducer Electric Drive* Modbus Comm.
1 Y Y Y
2 Y Y Y
3 - Y Y
4 - Y Y
5 - Y Y
6 - Y Y
Type RS-422 (375 KB) RS-422 (19.2 KB) RS-232 (57.6 KB) RS-422 (115 KB)
RS-485 (115 KB)
Boards DSCB, DPWA DSCB DSCB
Choices (jumper select)
RS-232C 50 ft Baud Rates up to 57.6 kbps. Full duplex
RS-422 1000 ft Baud Rates up to 375 kbps
RS-485 1000 ft Baud Rates up to 375 kbps Full duplex
Ports 1 and 2 Honeywell pressure transducers, 6 transducers per port using XDSA board
Ports 1 through 6 Modbus operation or Kollmorgen electric fast drive FD170/8R2-004. * Note
Size 26.04 cm high x 1.99 cm wide x 18.73 cm deep (10.25 in. x 0.78 x 7.375 in.)
Note Any three ports, but no more than three, can support the electric drive.
Diagnostics
Three LEDs at the top of the VSCA front panel provide status information. The
shows a steady orange if a diagnostic alarm condition exists in the board. Diagnostic
checks include the following:
• Each port checks communications and if there is no response, or bad data, or the
communication port is non functional, a diagnostic fault is set. This creates a
composite diagnostic alarm, L3DIAG_VSCA, referring to the entire board. The
RESET_DIA signal.
• Each terminal board has its own ID device, which is interrogated by the I/O
board. The board ID is coded into a read-only chip containing the terminal board
serial number, board type, revision number, and the JA1 connector. When the
chip is read by the I/O board and a mismatch is encountered, a hardware
incompatibility fault is created.
Details of diagnostic faults generated by the electric actuator are a separate category
and are listed in the Alarms section of this document.
319
Configuration
VSCA is configured with board jumpers and with the toolbox. Jumpers JP1 through
JP6 are block jumpers, used to select the port electrical characteristic, RS-232C, RS-
422, or RS-485. Each jumper has three positions marked 232, 422, and 485.
Jumpers JP7 through JP12 are block jumpers, used to select the correct termination
configuration for all the transmission lines (Tx). Each jumper has three positions
marked TRM, THR, and PRK where:
• TRM means with terminating resistor.

• THR means no terminating resistor, pass through to J7.
• PRK means no terminating resistor, or park position
Jumpers JP13 through JP18 are block jumpers, and are used to select the correct
termination configuration for all the receive lines (Rx). Each jumper has three
positions marked, TRM, THR, and PRK, where the meanings are the same as above.
A two-position jumper, JPU1, selects between Honeywell pressure transducer and

Modbus operation for ports 1 and 2. The default position for JPU1 is X2, which
enables the serial clock for operation with Honeywell transducers. Position X1
selects the clock needed for Modbus operation. JPU1 is located at the bottom of the
board towards the backplane connector (away from the other jumpers).
VSCA Board Jumper Positions
Network Port 232/422/485 Tx

Number Communication TRM/THR/PRK Rx TRM/THR/PRK
Port 1 JP1 JP7 JP13
Port 2 JP2 JP8 JP14
Port 3 JP3 JP9 JP15
Port 4 JP4 JP10 JP16

VSCA_Crd_Cfg
Pressure_ Port1_Cfg
PortNum Toolbox Parameter, Applicable port, Port 1 only
PortType Type of VSCA port
Priority Priority None, Odd, Even
PhyConnect Type of physical connection RS-232, RS-422, RS-485
TermType Type of Termination None, Terminated, Pass through
BitsPerChar Bits per character 7 Bits, 8 Bits, 9 Bits
Parity Normal parity None, Odd, Even
StopBits Normal Parity 1 StopBit, 2 StopBit
Baud Baud rate
DevAddr1 Device Address for transducer
(first of six devices)
TimeOut Time out in msec 10 … 60000
Pressure_ Port2_Cfg (Similar configuration, for six devices)
PressureXdr_Pnt_Cfg
GEH-6421M
RawMin Scaling Factor Raw Limit -3.4E+038, +3.4E+038
RawMax Scaling Factor Raw Limit -3.4E+038, +3.4E+038
EngMin Scaling Factor eng limit -3.4E+038, +3.4E+038
EngMax Scaling Factor eng limit -3.4E+038, +3.4E+038
Lim1Enable Enable Limit 1 check Disable, Enable
Lim1_Latch Latch error limit 1 NotLatch, Latch
Lim1Comp Latch error compare <=, >=
(Similar for Lim2)
Limit1 Limit 1
Limit2 Limit 2
ElectDrive_Port_Cfg
PortNum Toolbox Parameter, Applicable port, Port 1 thru 6
Priority Priority None, Odd, Even
Baud Baud rate
ATA Drive parameter, Ampl Temp Alarm
PCP Drive parameter, Position Loop Comp
PDP Drive parameter, Position Loop Comp
PIN Drive parameter, Position Integral Gain
PPN Drive parameter, Position Loop Proportional Gain
RES_p1 Drive parameter, Resolver excit amplitude
RES_p2 Drive parameter, Resolver excit freq
RMS_p1 Drive parameter, Resolver excit freq
RMS_p2 Drive parameter, Resolver excit freq
RTL_p1 Drive parameter, Time limit
RTL_p2 Drive parameter, Time limit
TOF Drive parameter, Torque Offset
TimeOut Time Out in msec 10 … 60000
ElectDriveRefCfg
RawMin Scaling Factor Raw Limit -3.4E+038, +3.4E+038
RawMax Scaling Factor Raw Limit -3.4E+038, +3.4E+038
EngMin Scaling Factor eng limit -3.4E+038, +3.4E+038
EngMax Scaling Factor eng limit -3.4E+038, +3.4E+038
ElectDrivePosCfg (Similar to PressureXdr_Pnt_Cfg)
ElectDriveVelCfg (Similar to ElectDriveRefCfg)
ElectDriveTorCfg (Similar to ElectDriveVelCfg)
Modbus_Port_Cfg
PortNum Toolbox Parameter, which port, Port 1 thru 6
Priority Priority 0…7
321
Baud Baud rate 300, 600, 800, 1200, 2400, 9600,
115000, 192000, 384000, 57600,
375000.
StationCount Toolbox Parameter, Number of stations
Modbus_Station_Cfg
StationAddr What is station address 1 … 255
PageCount Toolbox Parameter, Number of Pages
TimeOut Time Out in msec 10 … 60000
FuncCode15 The connected station supports Modbus command Enable, Disable
FC15 Force Mult Coils.
FuncCode16 The connected station supports Modbus command Enable, Disable
FC16 Write Mult Registers.
DataSwap Float Data Format, swap words, ie Most Significant LswFirst, MswFirst
first
MaxBools Maximum Number of Booleans per request -32768 … +32767
MaxReg Maximum Number of Registers per request -32768 … +32767
DeviceDelay Transmit Delay Time in msec for non Modbus 0 … 60000
compliant slaves
Modbus_Page_Cfg
PageType What is the page type – HC, HR, OC, CC …
PointCount Toolbox Parameter, Number of points
Modbus_Bit_Cfg
Address Address of remote Register/Discrete 1 … 9999
BitNumber Bit-Packed register bit number –1 = Not Used 0 or –1
RemDataType Data-type of remote register/discrete UNS16, PAC16, SIGN16
UpdateRate The rate at which inputs are updated – Never means ½, 1, 2, 4 Hz
spare
RawMin Scaling factor raw minimum -3.4E+038, +3.4E+038
RawMax Scaling factor raw maximum -3.4E+038, +3.4E+038
EngMin Scaling factor engineering minimum -3.4E+038, +3.4E+038
EngMax Scaling factor engineering maximum -3.4E+038, +3.4E+038
Modbus_Long_Cfg (Similar to Modbus_Bit_Cfg)
Modbus_Float_Cfg
Address Address of remote Register/Discrete
BitNumber Bit-Packed register bit number –0 = LSB -1 or 0
(Similar to Modbus_Bit_Cfg)
PointDefs
Pressure Transducer Port 1 and 2 Point Definitions.
Electric Drive Port Point Definitions (see drive Faults
in the Alarm section).
GEH-6421M
Alarms
VSCA I/O Board Diagnostic Alarms

2 Flash ,memory CRCCRC failure Board firmware programming error (board will not go online)
3 CRCCRC failure override is active Board firmware programming error (board is allowed to go online)
30 ConfigCompatCode mismatch; Firmware: A tre file has been installed that is incompatible with the firmware on
[] the I/O board. Either the tre file or firmware must change. Contact the
factory
31 IOCompatCode mismatch; Firmware: [ ] A tre file has been installed that is incompatible with the firmware on
the I/O board. Either the tre file or firmware must change. Contact the
factory.
32 Port [ ] Device/Station [ ] No Response Message sent but no response received. Hardware or software
configuration error.
33 Port [ ] Device/Station [ ] Bad Data Message sent but bad data received. Software configuration error
34 Configure problem, Port [ ] , No communications taking place. Hardware or software configuration
Communications nonfunctional error
35 Electric drive, Port [ ], save command non
functional
36 Card ID failure
37 P6 ID failure
Electric Actuator Diagnostic Alarms
Fault (Point Definition) Note

L5FMV_CF Drive critical fault
L3FMV_RST Drive reset fault feedback
L5FMV_LRC Drive LRC fault
L5FMV_BOV Fault, Bus overvoltage (> 240 V)
L5FMV_BUV Fault, Bus undervoltage (< 90 V)
L30FMV_LVA Alarm, Low Volts (< 100 V)
L5FMV_WDT Fault, Watch Dog Timer
L5FMV_OVC Fault, Bridge Over-Current
L5FMV_POR Fault, Power On Reset
L5FMV_ATF Fault, Ampl. Temperature
L5FMV_MTF Fault, Motor Temperature
L30FMV_RMS Alarm, Alarm, RMS Over-current
L5FMV_PCF Fault, Position Control
L5FMV_RTL Fault, Commun. Time Limit.
L5FMV_CSL Fault, Check Sum Limit.
L5FMV_CVL Fault, Control Volts Limit
L5FMV_PF Fault, Processor Failure
L5FMV_RF Fault, Resolver Limit
323
DSCB Simplex Serial Communication Input/Output
The Simplex Serial Communication Input/Output (DSCB) terminal board is a
compact interface terminal board, designed for DIN-rail mounting. DSCB connects
to theVSCA board with a 37-wire cable. VSCA provides communication interfaces
with external devices, using RS-232C, RS-422, and RS-485 serial communications.
DSCB is wired to the external devices, which include intelligent pressure sensors
® ®
such as the smart Honeywell Pressure Transducers and Kollmorgen Electric
Drives used for valve actuation.
Wiring to devices uses shielded twisted pair. DSCB communication signals have on-
board noise suppression. An on-board ID chip identifies the board to VSCA for
system diagnostic purposes.
Note DSCB does not work with the PSCA I/O pack.
Installation
Mount the plastic holder on the DIN-rail and slide the DSCB board into place.
Connect the wires for the external devices to the Euro-Block type terminal block as
shown in the following figure. Four terminals are provided for the SCOM (ground)
connection, which should be as short as possible. Connect DSCB to VSCA using the
37 pin JA1 connector.
Note Jumpers J1 - J6 direct SIGRET directly to SCOM or through a capacitor to

SCOM. The shield must be grounded at one end or the other, but not both. If the
shield is grounded at the device end, the jumpers should be set to include the
capacitor in the circuit. If the shield is not grounded at the device end, the jumpers
should be set to go directly to SCOM.
GEH-6421M
DSCB DIN-rail mounted
terminal board
Twisted shielded pair,
JA1 s AWG#18, to external
To/from VSCA, J6 s devices.
37 wire cable, SCOM Configurable to RS232,
with twisted pair, Cap RS422, or RS485.
group shielding J1 SIGRET
Six channels, screw
SCOM
definitions below
s
s
Six channels
SCOM GRD
DSCB Terminal Assignments
RS422 TX+ TX- RX+ RX- NC SIGRET JPx SCOM

RS485 NC NC Tx/RX+ Tx/RX- NC SIGRET JPx SCOM
RS232 CTS DTR/RTS RX NC TX SIGRET JPx SCOM
Chan 1 1 2 3 4 5 6 JP1 7
Chan 2 8 9 10 11 12 13 JP2 14
Chan 3 15 16 17 18 19 20 JP3 21
Chan 4 22 23 24 25 26 27 JP4 28
Chan 5 29 30 31 32 33 34 JP5 35
Chan 6 36 37 38 39 40 41 JP6 42
43,44,45,46
Comments: The RS422/RS485 transmit and receive pairs must use
a twisted pair in the VSCA to DSCB
DSCB Wiring, Cabling, and Jumper Positions
325
Operation
The three XDSA boards are intermediate distribution boards for the RS-422 multi-
drop signals. The pressure transducers plug into ports P1, P2, P3, and P4 on these
boards. The following figure shows DSCB using two of the six VSCA channels,
Ports 1 and 2, to interface with 12 Honeywell pressure transducers.
Mark VI control Fuel skid

From VSCA
board front, XDSAG1ACC
P1
Outer valve
J6 1 Power
Adr= 0 Press Xdr
GP1OA
2 LG-1237
Chan A, RS422
DSCB +
3 Chan A
1 4 P2
JA1 Tx 2 5 Press Xdr
Outer valve
Adr= 1
Port #1
6
LG-1237
GP2OA
+ 7
Rx 34 8
P3 Outer valve
Chan B, RS422 Adr= 2 Press Xdr
9 Power
LG-1237 GP1OB
8 + 10
Tx 9 11 Chan B
Port #2 12 P4 Outer valve
+ 13 Adr= 3 Press Xdr
Rx 10
11
14
LG-1237
GP2OB
15
16 Stab-on
nearest gnd
XDSAG1ACC
P1 Pilot valve
Adr= 4 Press Xdr
1 Power
LG-1237
GP1PA
2
3 Chan A
4 P2 Pilot valve
5 Press Xdr
Adr= 5
6
LG-1237
GP2PA
7
8
43
44 P3 Pilot valve
45 Adr= 6 Press Xdr
46 9 Power
LG-1237
GP1PB
10
SCOM 11 Chan B
Gnd 12
13
P4 Pilot valve
Adr= 7 Press Xdr
14
LG-1237
GP2PB
15
16 Stab-on
nearest gnd
XDSAG1ACC
XDSA Jumper Settings P1 Inner valve
Adr= 8 Press Xdr
1 Power
LG-1237
GP1IA
Termination: Tx Only, JP1, JP2: 2
3 Chan A
Set to "IN" if end of line; 4 P2 Inner valve
5 Press Xdr
Set to "OUT" if not end of line. 6 Adr= 9
GP2IA
7 LG-1237
Address: 8
Jumper Outer Pilot Inner
P3 Inner valve
Adr=10 Press Xdr
JP3 0 1 0 Chan A 9 Power
LG-1237
GP1IB
10
JP4 0 0 1 Chan A 11 Chan B
12
13
P4 Inner valve
Adr=11 Press Xdr
14 GP2IB
JP5 0 1 0 Chan B 15 LG-1237
16 Stab-on
JP6 0 0 1 Chan B
nearest gnd
DSCB Connections to XDSA and Pressure Transducers
GEH-6421M
Specifications
Item Specification
Number of Channels Six
Choices (jumper select on VSCA)
RS-232C 50 feet Baud Rates up to 57.6 kbps Full duplex
RS-422 1000 feet Baud Rates up to 375 kbps
RS-485 1000 feet Baud Rates up to 375 kbps Full duplex
Connector for VSCA cable 37-pin D shell connector
Size, with support plate 8.6 cm Wide X 16.2 cm High (3.4 in x 6.37 in)
Diagnostics
The DSCB terminal board has its own ID device, which is interrogated by VSCA.
The board ID is coded into a read-only chip containing the terminal board serial
number, board type, revision number, and the JA1 connector. When the chip is read
by VSCA and a mismatch is encountered, a hardware incompatibility fault is created.
Communication and device problems are detected by the VSCA and reported to the
toolbox.
Configuration
Each of the six channels has a jumper to connect the cable shield to ground through a
capacitor. These are used when the shield is grounded at the device end. The jumper
positions are shown in the Installation section. All other configuration is done on the
VSCA board and in the toolbox.
DPWA Transducer Power Distribution

The Transducer Power Distribution (DPWA) terminal board is a DIN-rail mounted
power distribution board. It accepts input voltage of 28 V dc ±5%, provided through
®
a two-pin Mate-N-Lok connector. Connectors are provided for two independent
power sources to allow the use of redundant supplies. The input can accept power
from a floating isolated voltage source. The input to DPWA includes two 1 kΩ
resistors from positive and negative input power to SCOM. These center a floating
power source on SCOM. Attenuated input voltage is provided for external
monitoring. Output power of 12 V dc ±5% is connected to external devices through a
Euro- type terminal block, using screw terminals and AWG#18 twisted-pair wiring.
DPWA provides three output terminal pairs with a total output rated at 0 to 1.2 A.
The outputs are compatible with the XDSAG#AC interface board. Outputs are short
circuit-protected and self-recovering.
Note DPWA provides excitation power to LG-1237 Honeywell pressure

transducers.
327
Installation
Mount the DPWA assembly on a standard DIN-rail. Connect input power to
connector P1. If multiple DPWA boards are used, use connector P2 as a pass-through
connection point for the power to additional boards. If a redundant power input is
provided, connect power to connector P3 and use connector P4 as the pass-through
to additional boards.
Connect the wires for the three output power circuits on screw terminal pairs 9-10,
11-12, and 13-14.
Note The DPWA terminal board includes two screw terminals, 15 and 16, for
SCOM (ground) that must be connected to a good shield ground.
DPWA Power Distribution Terminal Board P12 9

s P12V1
10
P28V dc P12R1
P28V dc to P12Vdc,
1 P1 P12 V dc 1.2 Amp P12 11
s P12V2
2 Isolation 12
P12R2
P2
P12 13
s P12V3
Return 14
s P12R3
15
SCOM
P3 16
SCOM
100k
P4
20 k
1
1k 1k PSRet
SCOM 2
Bus SCOM
centering
bridge 100 k 100 k
SCOM
20 k 20 k
3
SCOM PS28VA
4 SCOM
5
PS28VB
6
SCOM
DPWA Board Block Diagram
GEH-6421M
Operation
DPWA has an on-board power converter that changes the 28 V dc to 12 V dc for the
transducers. A redundant 28 V dc supply can be added if needed. The following
figure shows the DPWA power distribution system feeding power to 12 LG-1237
pressure transducers.
Controller Fuel skid
Power for channel A XDSA P1

Outer valve
+ Adr= 0 Press Xdr
1 GP1OA
DPWA 12 Vdc +/-5%
2
Power LG-1237
1.2 Amp 3 Chan A
P1 P12 9 + 4
1 + 28 V P2
Return 10 5 Outer valve
2 to Adr= 1 Press Xdr
6 GP2OA
28 Vdc +/- 5% 12 V P12 LG-1237
11 + 7
Return 8
Isol 12
P2
1 P12 13 +
2 Return P3
14 Outer valve
+ Adr= 2 Press Xdr
Grd1 9 Power GP1OB
15 LG-1237
Redundant Grd2 10
power supply
16 11 Chan B
when required P3 12 P4
13 Outer valve
Adr= 3 Press Xdr
14 LG-1237 GP2OB
15
Return 100K Stab-on
1 16
20K
SCOM 2
P4
P28_J1 100K nearest gnd
3
SCOM 20K
4
P28_J2 100K 5
SCOM 20K 6 XDSA P1
Pilot valve
+ Adr= 4 Press Xdr
1 LG-1237 GP1PA
Power
2
3 Chan A
4 P2
5 Pilot valve
Adr= 5 Press Xdr
6 LG-1237 GP2PA
7
8
P3
Pilot valve
Adr= 6 Press Xdr
Power for channel B + 9 Power LG-1237
GP1PB
10
DPWA 12 V dc +/-5% 11 Chan B
12 P4
1.2 Amp Pilot valve
P1 13 Adr= 7 Press Xdr
P12 9 + GP2PB
28 V 14 LG-1237
to Return 10 15
12 V 16 Stab-on
P12 11 +
Return 12
Isol
P2 nearest gnd
P12 13 +
Return 14
Grd1 15
XDSA P1
Grd2 16 Inner valve
+ Adr= 8 Press Xdr
P3 1 Power LG-1237 GP1IA
2
3 Chan A
4 P2
5 Inner valve
Adr= 9 Press Xdr
Return 100K 6 LG-1237 GP2IA
P4 1 VDCx 7
SCOM 20K 2 Retx 8
P28_J1 100K 3 VDCx
SCOM 20K 4 Retx P3
Inner valve
P28_J2 100K + Adr= 10 Press Xdr
5 VDCx 9 Power GP1IB
20K LG-1237
SCOM 6 Retx 10
11 Chan B
12 P4
13 Inner valve
Adr=11 Press Xdr
Power supply 14 GP2IB
LG-1237
monitoring 15
voltage 16 Stab-on
inputs
nearest gnd
DPWA Power Distribution to XDSA and Smart Pressure Transducers
329
Specifications
Item Specification
Number of Channels Three power output terminal pairs
Input voltage 28 V dc ±5%, provisions for redundant source
Input current Limited by protection to no more than 1.6 A steady state
Output voltage 12 V dc ±5%, maximum total current of 1.2 A, short circuit protected, and self-recovering
Monitor voltages Attenuated by 6:1 ratio
Diagnostics
DPWA features three voltage outputs to permit monitoring of the board input power.
The voltage monitor outputs are all attenuated by a 6:1 ratio to permit reading the 28
V dc using an input voltage with 5 V dc full scale input. Terminal 1 (PSRet) is the
attenuated voltage present on the power input return line. Terminal 3 (PS28VA) is
the attenuated voltage present on the P1 positive power input line. Terminal 5
(PS28VB) is the attenuated voltage present on the P3 positive power input line.
Terminals 2, 4, and 6 provide a return SCOM path for the attenuator signals. In
redundant systems, monitoring PS28VA and PS28VB permits the detection of a
failed or missing redundant input. In systems with floating 28 V power, with the
input centered on SCOM, the positive and return voltages should be approximately
the same magnitude as a negative voltage on the return. If a ground fault is present in
the input power, it may be detected by positive or return attenuated voltage
approaching SCOM while the other signal doubles.
Configuration
GEH-6421M
VSVO Servo Control
VSVO Servo Control
The Servo Control (VSVO) board controls four electro-hydraulic servo valves that
actuate the steam/fuel valves. These four channels are usually divided between two
servo terminal boards (TSVO or DSVO). Valve position is measured with linear
variable differential transformers (LVDT). The loop control algorithm is run in the
VSVO.
Three cables connect to VSVO on J5 plug on the front panel and the J3/J4
connectors on the VME rack. TSVO provides simplex signals through the JR1
connector, and fans out TMR signals to the JR1, JS1, and JT1 connectors. Plugs JD1
or JD2 are for external trips from the protection module.
TSVO Terminal Board External VSVO Processor Board

trip
x
x x
x 1 JT1
x 2 x 3 37-pin "D" shell RUN
x 4 type connectors FAIL
x 6 x 5 JD1 STAT
x 8 x 7 with latching
x 10 x 9 JD2 fasteners
x 12 x 11
LVDT inputs x 13
Pulse rate inputs x 16 x 15
x 18 x 17
LVDT excitation x 19 Cables to VME
x 20 JT5 JS1
Servo coil outputs x 22 x 21 rack T
x 24 x 23
x
x
x 26 x 25 JS5
x 28 x 27 Cables to VME
x 30 x 29 rack S
x 32 x 31 J5
x 34 x 33 JR1
x 36 x 35
x 38 x 37 JR5
x 40 x 39 VSVO
x 42 x 41 x
x 44 x 43
46 x 45
x
x 47 J3
x 48
x
x
Shield Connectors on
bar VME rack R J4
Barrier type terminal Cables to VME

blocks can be unplugged rack R
From second TSVO
Servo/LVDT Terminal Board, VSVO Processor Board, and Cabling
331
Volume II VSVO Servo Control • 333
Installation

its edge connectors
Operation
VSVO provides four channels consisting of bi-directional servo current outputs,
LVDT position feedback, LVDT excitation, and pulse rate flows inputs. The TSVO
provides excitation for, and accepts inputs from , up to six LVDT valve position
inputs. There is a choice of one, two three, or four LVDTs for each servo control
loop. Three inputs are available for gas turbine flow measuring applications. These
signals come through TSVO and go directly to the VSVO board front at J5.
Each servo output is equipped with an individual suicide relay under firmware
control that shorts the VSVO output signal to signal common when de-energized,
and recovers to nominal limits after a manual reset command is issued. Diagnostics
monitor the output status of each servo voltage, current, and suicide relay.
334 • VSVO Servo Control 332 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Simplex Systems
VSVO circuits for a simplex system are shown in the following figures.
Capacity <R> Control Module

6 LVDT/R inputs on each of 2
boards, and total of 2 active/passive Controller
magnetic pickups. Application Software
Termination
Board TSVOH1B
(Input portion) Servo Board
VSVO
JR1 J3
LVDT LVDT1H 1 Digital
3.2k Hz, SCOM
A/D Regulator servo
7 V rms regulator
excitation P28VR
A/D converter
2
source LVDT1L D/A D/A converter
6 Ckts. P28V Servo driver P28V J3

or LVDR Voltage
Limit
Current
Suicide
P24V1 41 limit Relay
P24VR1 42 Configurable
Gain To Servo
Pulse rate 39
P1TTL Outputs
inputs 43( JR5 J5 3.2KHz
active probes PR P1H Pulse Excitation To TSVO
2 - 20 k Hz TTL P1L 44 Rate
To
Connector second
(PR only available 45 CL
P24V2 on front of TSVO
on 1 of 2 TSVOs)
46 VSVO
P24VR2
Pulse rate 40 board
P2TTL
inputs, P2H 47(
magnetic PR
MPU P2L 48
pickups
2 - 20 k Hz Noise suppr.
LVDT and Pulse Rate Inputs, Simplex
Each servo output channel can drive one or two-coil servos in simplex applications,
or two or three-coil servos in TMR applications. The two-coil TMR applications are
for 200# oil gear systems where each of two control modules drive one coil each and
the third module interfaces with the servo. Servo cable lengths up to 300 meters (984
feet) are supported with a maximum two-way cable resistance of 15 ohms. Because
there are many types of servo coils, a variety of bi-directional current sources are
selectable by configuring jumpers.
Another trip override relay, K1, is provided on each terminal board and is driven
from the Protection Module. If an emergency overspeed condition is detected in
the Protection Module, the K1 relay energizes and disconnects the VSVO servo
output from the terminal block and applies a bias to drive the control valve closed.
This is only used on simplex applications to protect against the servo amplifier
failing high, and is functional only with respect to the servo coils driven from <R>.
Note The primary and emergency overspeed systems can trip the hydraulic
solenoids independent of this circuit.
333
<R>
Controller Terminal Board

TSVOH1B (continued)
Servo Board
Coil current range
VSVO
10,20,40,80,120 ma
A/D converter
Digital
P28VR JD1
A/D Regulator servo 1 Trip input from
K1 module (J1)
regulator 2
From
LVDT D/A D/A converter P28VR JD2
JP1 1
TSVO 120B
120 2
Servo driver J3 JR1 80
Servo coil from<R>
Voltage 40 25 SR1H
Limit 20
10 31 SRS1H
N
Suicide 1k 22 ohms
S
P28V Relay 2 Ckts. ohm 89 ohms
26 1k ohm
Configurable SR1L
Gain SCOM
17 ER1H
J5 3.2KHz,
3.2KHz
Pulse Excitation
N 7V rms
S 18 excitation
Rate ER1L
2 Ckts. SCOM source

Connector on Noise for LVDTs
front of VSVO To suppr-
second ession
TSVO
Servo Coil and LVDT Outputs, Simplex (continued) LVDT Outputs, Simplex
TMR Systems
In TMR applications, the LVDT signals on TSVO fan out to three racks through
JR1, JS1, and JT1. Three connectors also bring power into TSVO where the three
voltages are diode high-selected and current limited to supply 24 V dc to the pulse
rate active probes. VSVO circuits for a TMR system are shown in the following
figures.
Note Only two pulse rate probes on one TSVO are used.
GEH-6421M
<R>
<S>
<T>
Controller
Terminal
Board TSVOH1B Servo Board
(Input Portion) VSVO
LVDT JR1 J3 A/D converter Digital

LVDT1H 1
3.2k Hz, A/D Regulator servo
7 V rms regulator
P28VR
excitation
2
JS1 J3
source LVDT1L P28V D/A D/A converter
SCOM Same for <S>
6 Ckts. P28VS
Servo driver To servo
Voltage
JT1 J3 Limit outputs
on TSVO
Same for <T>
P28VT
Diode Voltage
Select
P24V1 41 CL P28V Connector on Configurable
front of VSVO Gain
P24VR1 42 card in <R>
JR5 J5 To TSVO
Pulse rate P1TTL 39 3.2KHz
Pulse excitation
inputs
active probes
43( Rate
P1H
2 - 20 kHz PR
44 JS5 J5 in <S>
TTL P1L

P24V2
on 1 of 2 TSVOs) 46 JT5 J5 in <T>
P24VR2
P2TTL
40
Pulse rate
P2H 47 (
inputs, PR
magnetic MPU P2L 48
pickups
Noise
2 - 20 kHz
suppression
LVDT and Pulse Rate Inputs,TMR
335
For TMR systems, each servo channel has connections to three output coils with a
range of current ratings up to 120 mA selected by jumper.
<R>
<S>
<T>
Controller
Terminal Board
TSVOH1B (continued)
Servo Board
VSVO Servo current range
Digital 10,20,40,80,120 ma
A/D converter servo
JD1 Trip input from
regulator
A/D Regulator P28VR 1
2
 not used for
From Suicide TMR
TSVO P28VR JD2
D/A relay JP1
LVDT 120B
1
120 2
Servo coil from <R>
25 S1RH
Voltage 40
Limit 20
10 31
N
22 ohms
2 Ckts. S
89 ohms
26 S1RL 1k ohm
Configurable
Gain
17 ER1H 3.2KHz,
J5 3.2KHz 7V rms
Pulse excitation 2 Ckts S
N
18 excitation
Rate ER1L
source
Connector on J3 JS1 JP2 For LVDTs
front of VSVO 120B
120 Servo coil from <S>
card 80 27 S1SH
40
20
10 N
S
2 Ckts. 28 S1SL
21 ESH 3.2KHz,
1 Ckt. N 7V rms
S 22 ESL excitation
J3 JT1 source
JP3
120B
120
80
Servo coil from <T>
29 S1TH
40
20
10
N
S
2 Ckts. 30 S1TL
23 ETH 3.2KHz,
N 7V rms
1 Ckt. S 24 ETL excitation
source
Noise suppression
For LVDTs
Servo Coil Outputs and LVDT Excitation, TMR
GEH-6421M
The following table defines the standard resistance of servo coils, and their
associated internal resistance, selectable with the terminal board jumpers shown in
the figure above. In addition to these standard servo coils, non-standard coils can be
driven by using a non-standard jumper setting. For example, an 80 mA, 125 Ω coil
can be driven by using a jumper setting 120B.
Servo Coil Ratings
Coil Nominal Coil Resistance Internal

Type Current (Ohms) Resistance (Ohms) Application
1 ±10 mA 1,000 180 Simplex and TMR
2 ±20 mA 125 442 Simplex
3 ±40 mA 62 195 Simplex
4 ±40 mA 89 195 TMR
5 ±80 mA 22 115 TMR
6 ±120 mA (A) 40 46 Simplex
7 ±120 mA (B) 75 10 TMR
Note The total resistance is equivalent to the standard setting.
The control valve position is sensed with either a four-wire LVDT or a three-wire
linear variable differential reluctance (LVDR). Redundancy implementations for the
feedback devices is determined by the application software to allow the maximum
flexibility. LVDT/Rs can be mounted up to 300 meters (984 feet) from the turbine
control with a maximum two-way cable resistance of 15 Ω.
Each terminal has two LVDT/R excitation sources for simplex applications and four
for TMR applications. Excitation voltage is 7 V rms and the frequency is 3.2 kHz
with a total harmonic distortion of less than 1% when loaded.
Note The excitation source is isolated from signal common (floating) and is capable
of operation at common mode voltages up to 35 V dc, or 35 V rms, 50/60 Hz.
A typical LVDT/R has an output of 0.7 V rms at the zero stroke position of the valve
stem, and an output of 3.5 V rms at the designed maximum stoke position (these are
reversed in some applications). The LVDT/R input is converted to dc and
conditioned with a low pass filter. Diagnostics perform a high/low (hardware) limit
check on the input signal and a high/low system (software) limit check.
Two pulse rate inputs connect to a single J5 connector on the front of VSVO. This
dedicated connection minimizes noise sensitivity on the pulse rate inputs. Both
passive magnetic pickups and active pulse rate transducers (TTL type) are supported
by the inputs and are interchangeable without configuration. Pulse rate inputs can be
located up to 300 meters (984) from the turbine control cabinet, assuming a shielded-
pair cable is used with typically 70 nF single ended or 35 nF differential capacitance
and 15 Ω resistance.
Note The maximum short circuit current is approximately 100 mA with a maximum
power output of 1 W.
A frequency range of 2 to 30 kHz can be monitored at a normal sampling rate of

either 10 or 20 ms. Magnetic pickups typically have an output resistance of 200 Ω
and an inductance of 85 mH excluding cable characteristics. The transducer is a high
impedance source, generating energy levels insufficient to cause a spark.
337
Digital Servo Regulators
The Digital Servo Regulators n = 1-4 in the following figure divides the servo
regulators into the software and hardware portions of the control loop. The user can
choose the LVDT and pulse rate inputs as the servo feedback. The LVDT input is a
3.2 kHz sinusoidal signal with a magnitude proportional to the position of the
electro-mechanical valve that is controlled by the servo output. The pulse rate input
is TTL-type signal or a periodic signal that triggers a comparator input. The
comparator output transitions are counted by an FPGA on VSVO and converted to a
flow rate. For LVDT feedbacks, LVDT1 – 12 are scaled and conditioned in the
Position Feedback function of the Digital regulator and can also be independently
conditioned by a separated Monitoring function. The asterisk after a block name
indicates a more detailed drawing exists to better define the block function. All
signal space I/O for the VSVO is identified as either si for system input (the
controller reads the signal space variable from the servo) or so for system output (the
controller writes the signal space variable to the servo card). Italic text is defined as a
configuration parameter that can be changed in the toolbox to redefine the operation
of the VSVO. Internal variables, for example Variable_Name, are not visible to the
user through the toolbox.
GEH-6421M
Digital Servo Regulators n = 1 - 4
SystemLimits
PRType Dither_Freq I/O Configuration
RegNumber EnableCurSui
PRScale
MonitorType RegType DitherAmpl EnablFdbkSui
SuicideForcen (VSVO Servo firmware)

CalibEnabn Regn_Error
(so) (si)
(so)
RegnSuicide
Digital Reg. (RegType)* (si)
Regn_Ref MasterReset
(so) + (so) Servo Suicide Rn_SuicideNV
100%
Control* (si)
G mA_cmdn
Regn_Fdbk Servo
(si) - -100% L3DIAG_VSVO
Open/Short
SuicideReset (si)
FlowRate1 Monitor*
(so)
Pulse (si) Dither Control
Position SuicDrv
Rate FlowRate2 Calibration +
Fdbk +
Calc. (si) Function K_comp %
Function ServoOutnNV
IMFBKn function -----
(I range) cnt (si)
50% Duty Cyl
ServoOutputn
Monitor* (si)
ServoOutnNV
volts / cnt -1
(si)
GEH-6421M Mark VI Turbine Control System Guide

ServoOutIn
Monx (si)
339
(si) x=1- 12
Execution Rate = 200 Hz
(VSVO Hardware)
Volume
FPGA Registe
II
r
of 1016
PulsRate1H/L
Pulse Rate
SUIMON Servo Current Regulator n
Support Logic
PulsRate2H/L I/O SUICDRVH
AE1H/L K1
BE1H/L ACOM T
P28 o
LVDT1-12 10
AE2H/L SERVOxH
Servo n D/A DACIREF Op BUF
BE2H/L D/A Amp
Controller +/- 4.0V FS ohm
T
f LV1H/L M
ACOM S
r A/D U Diff
LV2H/L cntrl X V
o IMFBK +/- 2.0V @full scale Amp SERVOxL O
m LV3H/L A/D Controller & Register
A/ Servo1
Interface to PSVO Programmable
LV4H/L D Gain /4 ACOM
T M Microprocessor Gain
Reg
S U cntrl
LV5H/L
V X
O LV6H/L Logic
I/O
LV7H/L Param_Name - Servo config parameter (Toolbox view)
Signal_Name - signal from A/D in (no Toolbox view)
LV8H/L Variable_Name - internal vars to Servo (no Toolbox view)
* - indicates a detailed drawing with title per block name.
LV9H/L
Input_Name - Input to controller from Servo
LV10H/L (si) (Toolbox view)
Output_Name - Output from controller to Servo
LV11H/L (so) (Toolbox view)
VSVO Servo Control • 341

LV12H/L
Servo Suicide Control
The Servo Suicide Control function compares the absolute value of the filtered servo
current error against the configuration parameter value, Sui_Margin. This function
determines if the hardware servo current regulator has lost control of the current. If
the current feedback is not following the current command, a diagnostic is generated
and the servo current output is suicided (disabled and put in a safe state).
GEH-6421M
Servo Suicide Control
SuicideForce
Master_Reset (so)
(so) EnablCurSuic(cfg)
1
0
0
LowPass > Reg_Type(cfg) =
Y Time 4_LV_LM
Filter ABS Sui_Margin S
Delay
Tc = .5 sec (cfg) Latch OR
R
Suicide_Reset N
(so) No Time Delay
+ - Master_Reset
(so)
Master_Reset 1
mA_cmdx IMFBx (so)
<= 1) Clear Servo I Diag.
where where Suicide_Reset
Sui_Margin
x = 1- 4 x = 1- 4 Y (so)
(cfg) 2) Servo State = OK
Servo State =
N Suicide_Reset Failed
(so) 1
Cur_Sui_En(cfg) 1) Set Servo I Diag. EnablCurSuic(cfg)

2) Servo State = Failed
341
suicide
1) Servo State = OK
Volume II
Limit_Check_Servo_Output_Current
1) Set Servo Current Range
of 1016
Suicide_Reset
(so) 2) FPGA out = no suicide
Master_Reset OR
CalibEnabn (so) 3) Servo State = OK
n=1- 4 (so) 1) Set Servo Current Range = 120 mA
4) Servo Reg Health = OK
2) FPGA out = suicide
NOT
3) Servo State = Failed
4) Servo Reg Health = Not OK
1) Set Servo Current Range
2) FPGA out = no suicide
3) Servo State = OK
Param_Name(cfg) - Servo config parameter (Toolbox view) 4) Clear I/O Diagnostic

Variable_Name - internal vars to Servo (no Toolbox view) 5) Servo Reg Health = OK
1) Set Servo Current Rng = 120 mA
(si) (Toolbox view)
2) FPGA out = suicide
(so) (Toolbox view) 3) Servo State = Failed
4) Set I/O Offline Diagnostic

DPM_State_Online

(Servo is OnLine) 5) Servo Reg Health = OK
Open/Short Detect Function
The servo output open circuit detection function checks for open or broken wires
between the terminal screws of the terminal board and the servo coil. If the servo
driver voltage is high and no current is flowing, the diagnostic alarm,
Msg_Servo_Open, is issued.
Diagnostic Alarm
(Msg_Servo_Short)
|ServoOutVn| <= Diag = True
|ServoOutnNV * ohms * delta_mA_pct + 0.2| Servo State /= Failed
Diagnostic Alarm
(Msg_Servo_Short)
Diag = False
Presently, disabled in PSVO
Diagnostic Alarm
(Msg_Servo_Open)
Diag = True
|ServoOutVn| > 5 V ServoOutnNV < 10 %
Diagnostic Alarm
(Msg_Servo_Open)
Diag = False
Open_Short_Detect is called by the Servo routine every 5ms.
Open Short Detect Function
GEH-6421M
1 PulseRate /2 PulseRateMax
The Digital Servo Regulator is configured as a flow-rate regulator. A pulse signal
with a frequency proportional to the flow-rate of the liquid fuel is the feedback for
the 1 PulseRate version of the flow-rate regulator. With the dual input, the larger
pulse rate frequency is selected as the feedback for the flow rate regulator. System
Limit functions monitor each pulse rate input and are enabled through the
configuration parameter, SysLimxEnabl. It can latch the signal space limit flags
SysLimxPR1 and/or SysLimxPR2.
343
Digital Servo Regulator RegType = 1_PulseRate
PR_Scale (EU * sec / pulse) SysLim1Enabl I/O Configuration

SysLim2Type Reg_Gain RegType
SysLim2Enabl SysLim1Type
PRateInput1 SysLimit2 SysLimit1 RegNullBias
SysLim2Latch SysLim1Latch
Sys2 Lmt En
Regn_error
>= Lmt
<= Value
SysLim2PR1 n=1- 4 (si)
0
(si)
input
Latch Option
346 • VSVO Servo Control

Param_Name - Servo config parameter (Toolbox view) Regn_Ref
Signal_Name - signal from A/D in (no Toolbox view) n=1- 4(so)
Variable_Name - internal vars to Servo (no Toolbox view)
Sys1 Lmt En
Input_Name - Input to controller from Servo >= Lmt + +
(si) (Toolbox view) <= Value
0 +
SysLim1PR1
Output_Name - Output from controller to Servo input
Servo_mA_ref(%)
(si) -
(so) (Toolbox view) Latch Option +
Regn_fdbk
0 M
(si) n=1- 4
U FlowRate1
fs1 = (# pulses/sec) /
X Regn_NullCor
(# pulses/entry)
n=1- 4 (so)
fs1 Pulse Rate 1 Calc.
344
# of fs2 = 100hz
Pulses # of Entries to # of Pulses /
List Use List Entry
Flow Spd LM HiSpd Flow Spd LM HiSpd
PLE0
PLE1 Eng. Units
GEH-6421M
1 4 3 2 Gear5 24 24 24 32
PLE2 Hysteresis
PLE3
from 1 4 4 2 Gear4 8 12 12 16
FPGA .
PR1 . 1 4 6 2 Gear3 4 6 8 8
Pulse . 1 2 2 1 Gear2 2 3 8 4
Ctr PLE127 1 1 1 1 Gear1 1 2 8 2
PLE(x) - PLE(x - # of Speed (rpm)
# of entries to use) pulses Flow (pulses/sec) 362 724 1448 2896
--------------------------------------- pulses / sec Spd (pulses/sec) 724 1448 2896 5793
Tics
TLE(x) - TLE(x - # of tic
List LM (pulses/sec) 724 1448 2600 5400
entries to use)
TLE0 HSpd(pulses/sec) 724 1448 2896 5793
TLE1
TLE2 6.25 e +06 tics
TLE3 ------
Accel1
from . sec PR_Scale
PLE(x) - PLE(x - 24) PLE(x) - PLE(x - 12) (si)
FPGA . pulses/sec/sec
Timer . TLE(x) - TLE(x - 24) TLE(x) - TLE(x - 12)
TLE12 (TLE(x) - TLE(x - 24)) / 2
7
PR_Scale
PR_Type
I/O Configuration
of 1016 Mark VI Turbine Control System Guide Volume II

Digital Servo Regulator RegType = 2_PlsRateMAX
PRateInput2 SysLim2Enabl SysLim1Enabl I/O Configuration

Reg_Gain RegType
PR_Scale SysLim2Type SysLim1Type
(EU * sec / SysLimit2 SysLimit1 RegNullBias
pulses) PRateInput1 SysLim2Latch SysLim1Latch
Sys2 Lmt En Sys2 Lmt En
>= Lmt >= Lmt Param_Name - Servo config parameter(Toolbox view)

<= Value <= Value
SysLim2PR1 Signal_Name - signal from A/D in (no Toolbox view)
0 0
SysLim2PR2 (si) Regn_error Variable_Name - internal variables(no Toolbox view)
from input (si) input
n=1- 4 (si) * - IDs a detailed drawing with title per block name.
FPGA Accel2 Latch Option Latch Option
PR2 (si)
Regn_Ref (si) (Toolbox view)
Pulse
Sys1 Lmt En Sys1 Lmt En n=1- 4(so) Output_Name - Output from controller to Servo
Ctr (so) (Toolbox view)
Pulse >= Lmt >= Lmt
Rate 2 <= Value <= Value
0 0
SysLim1PR2 SysLim1PR1
Calc. input input (si) + +
from (si)
Latch Option Latch Option +
FPGA Servo_mA_ref(%)
Timer PR2 0 M -
Regn_fdbk +
M U FlowRate1
0 Maximum (si) n=1- 4
U X
Select
X

FlowRate2 Regn_NullCor
PR1 n=1- 4 (so)
345
fs1 Pulse Rate 1 Calc.
Volume
Pulse
II
fs2 = 100hz
Count PR1 # of Entries to # of Pulses /
Use List Entry
of 1016
List fs1 = (# pulses/sec) / Flow Spd LM HiSpd Flow Spd LM HiSpd
PLE0
(# pulses/entry)
PLE1 1 4 3 2 24 24 24 32
Gear5
PLE2 Hysteresis
PLE3
from PR_Scale 1 4 4 2 8 12 12 16
. Gear4
FPGA
PR1 . 1 4 6 2 Gear3 4 6 8 8
Pulse . 1 2 2 1 Gear2 2 3 8 4
Ctr PLE127 1 1 1 1 Gear1 1 2 8 2
PLE(x) - PLE(x - # of Speed (rpm)
# of entries to use) pulses Flow (pulses/sec) 362 724 1448 2896
-------------------------------------- pulses / sec Spd (pulses/sec) 724 1448 2896 5793
Tics
TLE(x) - TLE(x - # of tic
List LM (pulses/sec) 724 1448 2600 5400
entries to use)
TLE0 HSpd(pulses/sec) 724 1448 2896 5793
TLE1
TLE2 6.25 e +06 tics
TLE3 ------
Accel1
from . sec PR_Scale
PLE(x) - PLE(x - 24) PLE(x) - PLE(x - 12) (si)
FPGA . pulses/sec/sec
Timer . TLE(x) - TLE(x - 24) TLE(x) - TLE(x - 12)
TLE12 (TLE(x) - TLE(x - 24)) / 2
7
PR_Scale

PR_Type I/O Configuration
1 LVposition, 2 LVposMIN, 2LVposMAX,
3LVposMID
The following LVDT feedback configurations are provided for the servo value
position loop:
• 1_LVposition – one LVDT signal is used as the position feedback.

• 2_LVposMIN – the minimum of two LVDT signals is selected as the position
feedback.
• 2_LVposMAX – the maximum of two LVDT signals is selected as the position
feedback.
• 3_LVposMID – the median of three LVDT signals is selected as position
feedback.
The LVDT feedback signals are bounded and scaled using the Calibration function.
The Calibration function uses the following configuration parameters: position at the
minimum end stop in engineering units (EU), MinPOSvalue, and the position at the
maximum end stop in EU, MaxPOSvalue. In the calibration mode the LVDT sensors
are forced into the minimum and maximum positions. The feedback voltages,
MnLVDTx_Vrms and MxLVDTx_Vrm,s are recorded for each of the LVDT
feedbacks used. From these values, the internal constants Reg_Sensor_Hdwr_Hi,
Reg_Sensor_Hdwr_Lo, Reg_Sensor_Offset, Reg_Sensor_Gain, and
Reg_Sensor_End_Stop_Min are calculated. These internal constants are used by the
Regulator Calculation Position function.
The Regulator Calculation Position function performs an input boundary check that
makes sure the input signal is between the values, Reg_Sensor_Hdwr_Hi and
Reg_Sensor_Hdwr_Lo. If the feedback input is out of range a diagnostic alarm is
generated. The scaling from volts_rms to position feedback in EU is calculated next.
A limit check is then performed on the selected feedback.
GEH-6421M
Digital Servo Regulator RegType = 1_LVposition
I/O Configuration
Reg_Gain
LVDT1input
RegType RegNullBias
TMR_DiffLimt
Regn_Ref CalibEnabn
n=1- 4 (so) Regn_error n=1- 4 (so)
(si) n=1- 4
+ +
LVDT1 +
LVDT2 X Servo_mA_ref(%)
LVDT3
LVDT4 - +
LVDT5 M

LVDT6 Reg Calc. Limit
U Position(%) Regn_NullCor
LVDT7 Position* Check*
X n=1- 4 (so)
347
LVDT8 Regn_fdbk
LVDT9 (si) n=1- 4
LVDT10
Volume
LVDT11
II
LVDT12
of 1016
Calibrate
Function* MnLVDT1_Vrms(cfg),
Reg_Sensor_Hdwr_Hi
MxLVDT1_Vrms(cfg)
Reg_Sensor_Hdwr_Lo
RegCalMode
Reg_Sensor_Offset
(si)
Reg_Sensor_Gain
CalibEnabn
Reg_Sensor_End_Stop_Min
(so) n=1- 4
Param_Name(cfg) - Servo config parameter (Toolbox view)

Input_Name - Input to controller from Servo (Toolbox MaxPosValue LVDT_Margin
(si) view)
Output_Name - Output from controller to Servo MinPosValue

(so) (Toolbox view) I/O Configuration
Digital Servo Regulator RegType = 2_LVposMIN
I/O Configuration
LVDT1input
Reg_Gain
LVDT2input
RegType RegNullBias
TMR_DiffLimt
LVDT1
LVDT2
Regn_error
LVDT3
Status_B (si) n=1- 4
LVDT4
LVDT5 M Status_A
LVDT6 Reg Calc.

U Regn_Ref CalibEnabn
LVDT7 Position*
X n=1- 4 (so) n=1- 4 (so)
LVDT8
PositionA(%)
LVDT9
LVDT10 StatA StatB
LVDT11 A + +
LVDT12 +
B
X Servo_mA_ref(%)
LVDT1
- +
M PositionB(%)
Reg Calc.
U Limit Regn_NullCor
Position* MIN M
X Check* n=1- 4 (so)
Regn_fdbk
(si) n=1- 4
348
LVDT12
Minimum Select
GEH-6421M
Calibrate MnLVDT1_Vrms(cfg),
Function* MxLVDT1_Vrms(cfg)
Reg_Sensor_Hdwr_Hi
Reg_Sensor_Hdwr_Lo
MnLVDT2_Vrms(cfg),
MxLVDT2_Vrms(cfg)
Reg_Sensor_Offset
RegCalMode
Reg_Sensor_Gain
(si)
Reg_Sensor_End_Stop_Min CalibEnabn
(so) n=1- 4

(si) view)

Digital Servo Regulator RegType = 2_LVposMAX
LVDT1input I/O Configuration
Reg_Gain
LVDT2input
RegType RegNullBias
TMR_DiffLimt
LVDT1
LVDT2
LVDT3
Status_B
LVDT4
LVDT5 M Status_A
LVDT6 Reg Calc.
U CalibEnabn
LVDT7 Position* Regn_error
X Regn_Ref n=1- 4 (so)
LVDT8 PositionA(%) n=1- 4 (si)
LVDT9 n=1- 4 (so)
LVDT10 StatA StatB
LVDT11 A + +
LVDT12 +
B X Servo_mA_ref(%)
LVDT1
- +
PositionB(%)
M Reg Calc. Limit

MAX M Regn_NullCor
U Position* Check*
n=1- 4 (so)
349
X Regn_fdbk
(si) n=1- 4
LVDT12
Volume
Maximum Select
II
of 1016
Calibrate MnLVDT1_Vrms(cfg),
Function* MxLVDT1_Vrms(cfg)
Reg_Sensor_Hdwr_Hi
MnLVDT2_Vrms(cfg),
Reg_Sensor_Hdwr_Lo
MxLVDT2_Vrms(cfg)
Reg_Sensor_Offset
RegCalMode
Reg_Sensor_Gain
(si)
CalibEnabn
(so) n=1- 4

(si) view)

Digital Servo Regulator RegType = 3_LVposMID
LVDT1input I/O Configuration

RegNullBias
LVDT2input
RegType Reg_Gain
LVDT3input TMR_DiffLimt
LVDT1
LVDT2
LVDT3
LVDT4
LVDT5 M
LVDT6 Reg Calc. Regn_Ref
U CalibEnabn
LVDT7 Position*

X n=1- 4 (so) Regn_error n=1- 4 (so)
LVDT8
(si) n=1- 4
LVDT9
LVDT10
LVDT11 + +
PositionA(%)
LVDT12 +
X Servo_mA_ref(%)
LVDT1
- +
M Reg Calc. Median Limit

U PositionB(%) Regn_NullCor
Position* Select Check*
X Regn_fdbk n=1- 4 (so)
(si) n=1- 4
LVDT12
350
PositionC(%)
LVDT1
GEH-6421M
M
Reg Calc.
U MnLVDT1_Vrms(cfg),
Position*
X MxLVDT1_Vrms(cfg)
Calibrate
LVDT12 Function* MnLVDT2_Vrms(cfg),
Reg_Sensor_Hdwr_Hi
MxLVDT2_Vrms(cfg)
Reg_Sensor_Hdwr_Lo
MnLVDT3_Vrms(cfg),
MxLVDT3_Vrms(cfg)
Reg_Sensor_Offset
RegCalMode
Reg_Sensor_Gain
(si)
CalibEnabn
(so) n=1- 4

(si) view)

Reg_Calc_Position
Reg_Sensor_Hdwr_Lo[x] <= LVDT[x].volt_rms <= Reg_Sensor_hdwr_Hi[x]

Reg_Sensor_Offset[x] Reg_Sensor_End_Stop_Min[x]
Is a LVDT selected? Reg_Sensor_Fail_Ctr < Failed_2 Reg_Sensor_Gain[x]
- +
LVDTx + +
X Reg_Sensor[x].Pos (%)
where x = 1 - 12
+ Reg_Sensor[x].Pos(%)
Reg_Sensor is used for RegTypes:
_Hdwr_Hi[x] 1_LVposition
2_LVposMIN
X 1) Reg_Sensor.state = OK 2_LVposMAX
2) Reg_Sensor_Fail_Ctr = 0 3_LVposMID
3) Clear Diagnostic Alarm
1.1

Reg_Sensor[x].volts_rms
351
Reg_Sensor[x].volts_rms
Volume
is used for RegTypes:
II
4_LVLM
of 1016
1) Reg_Sensor.state = Fail
2) Set Diagnostic Alarm
1) Increment Reg_Sensor_Fail_Ctr
2) Don't update Reg_Sensor_Pos
Reg_Sensor_Hdwr_Lo[x] = MnLVDT_Vrms(cfg) - (MxLVDT_Vrms(cfg) - MnLVDT_Vrms(cfg)) * LVDT_Margin(cfg) / 100 before calibration.
Reg_Sensor_Hdwr_Hi[x] = MxLVDT_Vrms(cfg) + (MxLVDT_Vrms(cfg) - MnLVDT_Vrms(cfg)) * LVDT_Margin(cfg) / 100 before calibration.


Limit Check Function
Fdbk_lo_limit < Regn_fdbk < Fdbk_hi_limit

(si) GoodFdbk = True
RegType(cfg) /=
Fdbk_lo_limit < Fdbk_hi_limit 4LV_LM
Regn_PosAFlt =False
(si)
Fdbk_hi_limit < Regn_fdbk < Fdbk_lo_limit
(si)
Regn_PosBFlt =False
(si)
Master_Reset
GoodFdbk = True (so)
1) Clear Diag. Alarm "Msg Sel Pos"
2) Regn_fdbk health bit "OK"
3) Fbk_Fail_ctr = 0
Suicide_Reset
(so)
Increment Fbk_Fail_ctr
Fbk_Fail_Ctr < Threshold
1) Regn_fdbk health bit "Not OK"

2) Fdbk_state = Failed
EnableFdbkSuic = True 1) Set Diag. Alarm "Msg Sel Pos"

(so)
Fdbk_lo_limit = MinPOSvalue(cfg) - Fdbk_suicide_margin
Fdbk_hi_limit = MaxPOSvalue(cfg) + Fdbk_suicide_margin

(si) (Toolbox view)
(so) (Toolbox view)
GEH-6421M
4 LV_LM
The 4_LV_LM Digital Servo regulator uses four LVDT inputs to calculate the single
position feedback required for the servo position loop. The Regulator Calculation
Position performs the boundary check for the LVDT input signals. The scaling from
volts_rms to position in EU is not calculated, but the volts_rms value for each of the
LVDT feedbacks is calculated. The ratio of (A – B) / (A + B) is performed on the
LVDT input pairs and scaling is calculated using the input from the Calibration
function.
The internal variables, Reg_2LV[A].pos, PosA and Reg_2LV[B].pos, PosB are

checked against the configuration parameter limits, MinPOSvalue and MaxPOSvalue
in the Position A & B Diagnostic function. Results from PosA, PosB, and the
diagnostic Booleans feed the Position Feedback Selection function. Refer to the
Position Feedback Selection block diagram to understand the details of the function.
Other differences in the LM servo regulator are the following:
• Gain Modifier function

• Lead/Lag filter on the position error
• Configurable servo position error output clamp
353
Digital Servo Regulator RegType = 4_LV_LM
RegType I/O Configuration
CurSlope2 LagTau
MaxPosValue LeadTau
LVDT1input CurBreak
LVDT2input RegNullBias CurClpPs
MinPosValue CurSlope1
LVDT3input TMR_DiffLimt
Reg_Gain CurClpNg
LVDT4input
Reg_Sensor_Hdwr_Hi[x]
Reg_Sensor_Hdwr_Lo[x]
Reg_2LV[0].pos.gain
LVDT1
Reg_2LV[0].pos.offset
M Reg_Sensor[B]. CalibEnabn
Reg Calc.
U volts_rms n=1- 4 (so)
Position*

X (refer to details) A + B /= 0 Regn_Ref
MiscFdbknA
n=1- 4 (si) n=1- 4 (so)
LVDT12 -
A-B +
-------- X
A +B Reg_2LV[A].pos Regn_error
LVDT1 + +
(si) n=1- 4 + 1 + s * LeadTau Servo_
Regn_ mA_
0 X
M Pos AFlt 1 + s * LagTau ref%)
Reg Calc. n=1- 4 (si) - +
U
Position* Reg_Sensor[B].volts_rms Regn_fdbk Gain Modifier Lead/Lag Filter Clamp
X PosA
Reg_2LV[A]. (si) n=1- 4
Diag.* Regn_NullCor
Reg_2LV[0].sum_failed pos.failed
LVDT12 Sum NOT USED
Reg_2LV[0].sum_lim_hi (si) n=1- 4
Check* Limit
Reg_2LV[0].sum_lim_lo PosDiffEnabn Regn_GainMod
Check*
n=1- 4 (si) (si) n=1- 4
354
Reg_2LV[1].sum_lim_hi
Sum Pos.
Reg_2LV[1].sum_lim_lo
LVDT1 Check* Reg_2LV[B]. Fdbk Reg_2LV[0].sum_lim_hi, Reg_2LV[0].sum_lim_lo
Reg_2LV[1].sum_failed PosB pos.failed Sel
Diag.* Reg_2LV[1].sum_lim_hi, Reg_2LV[1].sum_lim_lo
M Reg_Sensor[C].volts_rms Func*
Reg Calc. Reg_2LV[0].pos.failed_lim
U
GEH-6421M
Position* Regn_
X 0 Reg_2LV[0].pos.offset
Pos BFlt Regn_PosDif1(si) n=1- 4
n=1- 4 (si) Reg_2LV[0].pos.gain
LVDT12 Regn_PosDif2(si) n=1- 4
C-D Reg_2LV[B].pos Reg_2LV[1].pos.failed_lim
-------- X
+ Reg_2LV[1].pos.offset
LVDT1 C+D Calibrate
- Reg_2LV[1].pos.gain
Function*
C + D /= 0 Reg_Sensor_Hdwr_Lo[x], Reg_Sensor_Hdwr_Hi[x]
M
Reg Calc. Reg_2LV[1].pos.offset
U Reg_Sensor_Gain[x], Reg_Sensor_Offset[x]
Position
X (refer to details)
Reg_Sensor[D].volts_rms
MnLVDT1_Vrms(cfg), MxLVDT1_Vrms(cfg)
LVDT12 MiscFdbknB
Reg_2LV[1].pos.gain
n=1- 4 (si) MnLVDT3_Vrms(cfg), MxLVDT3_Vrms(cfg)
Reg_Sensor_Hdwr_Lo[x]
Reg_Sensor_Hdwr_Hi[x]
RegCalMode
Param_Name - Servo config parameter (Toolbox view) (si)
CalibEnabn
PosSelect PosDiffCmp1 LVDT_Margin n=1- 4 (so)
* - indicates a detailed drawing with title per block name. MinPosValue
PosDefltEnab PosDiffTime1
Input_Name - Input to controller from Servo LVDTVsumMarg
SelectMinMax PosDiffCmp2
(si) (Toolbox view) MaxPosValue I/O Configuration
DefltValue PosDiffTime2
(so) (Toolbox view)

Position A & B Diagnostic Function
PosA Diag Function
MinPosValue(cfg) <= Reg_2LV[A].pos <= If Reg_2LV[A].pos.failed_limit = 1 for MiscFdbk1A

MaxPosValue(cfg) then MiscFdbk1A (si)
(si) Health bit = OK
else MiscFdbk1A
LATCH
Reg_2LV[A].pos.failed_limit (si) Health bit = Not OK
1
S
If Reg_2LV[A].pos.failed_limit = 1 for MiscFdbk2A
then MiscFdbk2A (si)
R
0 else MiscFdbk2A
(si) Health bit = Not OK
Master_Reset
(so)
OR Reg_2LV[A].pos.failed
Reg_2LV[0].sum_failed
PosB Diag Function

Reg_2LV[1].sum_failed
OR Reg_2LV[B].pos.failed
MinPosValue(cfg) <= Reg_2LV[B].pos <=

MaxPosValue(cfg)
If Reg_2LV[A].pos.failed_limit = 1 for MiscFdbk1B
then MiscFdbk1B (si)
1 else MiscFdbk1B
LATCH
S
0 Reg_2LV[B].pos.failed_limit If Reg_2LV[A].pos.failed_limit = 1 forMiscFdbk2B
then MiscFdbk2B (si)
R
else MiscFdbk2B

Input_Name - Input to controller from Servo (Toolbox
(si) view)
(so) (Toolbox view)
355
Position Feedback Selection Function
| Reg_2LV[A].pos - Reg_2LV[B].pos | > | Reg_2LV[A].pos - Reg_2LV[B].pos | >
PosDiffCmp2 (cfg) for PosDiffTime2 (cfg) PosDiffCmp1 (cfg) for PosDiffTime1 (cfg) PosSelect(cfg) = 1
Reg_2LV[A] Reg_2LV[B] PosDefltEnab(cfg) PosSelect(cfg) = 0 PosSelect(cfg) = 2
.pos.failed .pos.failed PosDiffEnab
Reg_2LV[A]
(so) SelectMinMax(cfg)
.pos
MIN Select
Reg_2LV[B]
.pos

MAX Select
(A+B)/2
356
GEH-6421M
DefltValue
(cfg)
Regn_fdbk
(si)
where n=1 or 2
Regn_PosDif1(si)
Set
0
False
Set
False
1
After Time
Delay1, set
True After Time
Delay2, set
True
Param_Name(cfg) - Servo config parameter (Toolbox view) PosDiffTime1(cfg)
Variable_Name - internal vars to Servo (no Toolbox view) Regn_PosDif2(si)
Input_Name - Input to controller from Servo (Toolbox PosDiffTime2(cfg)
(si) view)
(so) (Toolbox view)

Sum Check Calc
+ Y
Reg_Sensor[A].volts_rms >= Reg_2LV[0]. sum_lim_hi
OR Reg_2LV[0].sum_failed = True
+
N
Reg_Sensor[B].volts_rms
Y
<= Reg_2LV[0]. sum_lim_lo
Reg_2LV[0].sum_failed =
N AND
False
+ Y
Reg_Sensor[C].volts_rms >= Reg_2LV[1]. sum_lim_hi
OR Reg_2LV[1].sum_failed = True
+
N
Reg_Sensor[D].volts_rms
Y
<= Reg_2LV[1]. sum_lim_lo
Reg_2LV[1].sum_failed =
N AND
False
Monitors - 1 LVposition, 2 LVposMIN, 2LVposMAX,

3LVposMID
The following Monitor configurations are available:
• 1_LVposition – one LVDT signal is used as the position feedback.

• 2_LVposMIN – the minimum of two LVDT signals is selected as the position
feedback.
• 2_LVposMAX – the maximum of two LVDT signals is selected as the position
feedback.
• 3_LVposMID – the median of three LVDT signals is selected as the position
feedback.
357
Monitor MonitorType = 1_LVposition
MinPosValue MonitorType I/O Configuration
LVDT1input
MaxPosValue
MnLVDT1_Vrms
MxLVDT1_Vrms LVDT_Margin TMR_DiffLimt

Offset1 = MinPosValue -
((MaxPosValue - MinPosValue) /
(MxLVDT1_Vrms - MnLVDT1_Vrms)) *
LVDT1 MnLVDT1_Vrms
LVDT2 Gain1 = (MaxPosValue - MinPosValue) /
LVDT3 (MxLVDT1_Vrms - MnLVDT1_Vrms)
LVDT4
LVDT5 Gain1 Offset1
+
358
LVDT6 M +
Monx
U X x=1- 12 (si)
LVDT7 X
LVDT8 If LVDTx > MxLVDT1_Vrms + LVDT_Margin *
(MxLVDT1_Vrms - MnLVDT1_Vrms)
GEH-6421M
LVDT9 then 1) Assign Monx unhealthy
LVDT10 x=1- 12 (si)
2) If Out_of_Limits 3 passes
LVDT11
then Set Diagnostic Alarm
LVDT12 else if LVDTx < -MnLVDT1_Vrms + LVDT_Margin *
then 1) Assign Monx unhealthy
x=1- 12 (si)
2) If Out_of_Limits 3 passes Param_Name - Servo config parameter (Toolbox view)
then Set Diagnostic Alarm Signal_Name - signal from A/D in (no Toolbox view)
else 1) Assign Monx healthy Variable_Name - internal vars to Servo (no Toolbox view)
2) Reset Out_of_limits counter. Input_Name - Input to controller from Servo (Toolbox
(si) view)
Note: x = 1 - 12

Monitor MonitorType = 2_LVposMIN or 2_LVposMAX
LVDT1input
MaxPosValue
LVDT2input MnLVDT1_Vrms MnLVDT2_Vrms
MxLVDT1_Vrms MxLVDT2_Vrms TMR_DiffLimt LVDT_Margin
If LVDTx > MxLVDTz_Vrms + LVDT_Margin *

Offset1 = MinPosValue - (MxLVDTz_Vrms - MnLVDTz_Vrms)
((MaxPosValue - MinPosValue) / then 1) Assign Monx unhealthy
x=1- 12 (si)
MnLVDT1_Vrms 2) If Out_of_Limits 3 passes
LVDT1
LVDT2 Gain1 = (MaxPosValue - MinPosValue) / else if LVDTx < -MnLVDTz_Vrms + LVDT_Margin *
LVDT3 (MxLVDT1_Vrms - MnLVDT1_Vrms) (MxLVDTz_Vrms - MnLVDTz_Vrms)
LVDT4 x=1- 12 (si)

LVDT5 Gain1 Offset1 2) If Out_of_Limits 3 passes
+
359
LVDT6 M +
U X else 1) Assign Monx healthy
LVDT7 X 2) Reset Out_of_limits counter.
Volume II
LVDT8 Offset2 = MinPosValue -
((MaxPosValue - MinPosValue) / Note: z = 1 - 2 and x = 1 - 12
LVDT9
of 1016
LVDT10 MnLVDT2_Vrms
LVDT11
Gain2 = (MaxPosValue - MinPosValue) /
LVDT12 (MxLVDT2_Vrms - MnLVDT2_Vrms)
LVDT1
Gain2 Offset2 Maximum Select
+
M + if MonitorType = 2_LVposMAX
Monx
U X or x=1- 12 (si)
X Minimum Select
if MonitorType = 2_LVposMIN
LVDT12
Param_Name - Servo config parameter (Toolbox view)

(si) view)

Monitor MonitorType = 3_LVposMID
LVDT1input
MaxPosValue
LVDT2input MnLVDT1_Vrms MnLVDT2_Vrms MnLVDT3_Vrms
MxLVDT1_Vrms MxLVDT2_Vrms MxLVDT3_Vrms TMR_DiffLimt LVDT_Margin
LVDT3input
If LVDTx > MxLVDTz_Vrms + LVDT_Margin *

Offset1 = MinPosValue - (MxLVDTz_Vrms - MnLVDTz_Vrms)
((MaxPosValue - MinPosValue) / then 1) Assign Monx unhealthy
x=1- 12 (si)
MnLVDT1_Vrms 2) If Out_of_Limits 3 passes

LVDT1
LVDT2 Gain1 = (MaxPosValue - MinPosValue) / else if LVDTx < -MnLVDTz_Vrms + LVDT_Margin *
LVDT3 (MxLVDT1_Vrms - MnLVDT1_Vrms) (MxLVDTz_Vrms - MnLVDTz_Vrms)
LVDT4 x=1- 12 (si)
LVDT5 Gain1 Offset1 2) If Out_of_Limits 3 passes
+
M + then Set Diagnostic Alarm
LVDT6
U X else 1) Assign Monx healthy
LVDT7 X 2) Reset Out_of_limits counter.
LVDT8 Offset2 = MinPosValue -
((MaxPosValue - MinPosValue) / Note: z = 1 - 3 and x = 1 - 12
LVDT9
LVDT10 MnLVDT2_Vrms
360
LVDT11
LVDT12
LVDT1
Gain2 Offset2
GEH-6421M
+
M +
Median Monx
U X x=1- 12 (si)
Select
X
Offset3 = MinPosValue -
LVDT12 ((MaxPosValue - MinPosValue) /
MnLVDT3_Vrms

LVDT1
Gain3 Offset3
M +
+
U X
X
LVDT12 Param_Name - Servo config parameter (Toolbox view)

(si) view)

Specifications
Item Specification
Number of inputs (per TSVO) 6 LVDT windings
2 pulse rate signals (total of 2 per VSVO)
External trip signal
Number of outputs (per TSVO) 2 servo valves (total of 4 per VSVO board)
4 excitation sources for LVDTs
2 excitation sources for pulse rate transducers
Internal sample rate 200 Hz
Power supply voltage Nominal 24 V dc
LVDT accuracy 1% with 14-bit resolution
LVDT input filter Low pass filter with 3 down breaks at 50 rad/sec ±15%
LVDT common mode rejection CMR is 1 V, 60 dB at 50/60 Hz
LVDT excitation output Frequency of 3.2 ± 0.2 kHz
Voltage of 7.00 ± 0.14 V rms
Pulse rate accuracy 0.05% of reading with 16-bit resolution at 50 Hz frame rate
Noise of acceleration measurement is less than ± 50 Hz/sec for a 10,000 Hz signal
being read at 10 ms
Pulse rate input Minimum signal for proper measurement at 2 Hz is 70 mVpk, and at 12 kHz is 827
mVpk.
Magnetic PR pickup signal Generates 150 V p-p into 60 kΩ
Active PR Pickup Signal Generates 5 to 27 V p-p into 60 kΩ
Servo valve output accuracy 2% with 12-bit resolution
Dither amplitude and frequency adjustable
Fault detection Suicide servo outputs initiated by:
Servo current out of limits or not responding
Regulator feedback signal out of limits
361
Diagnostics
Three LEDs at the top of the VSVO front panel show status information. The normal
RUN condition is a flashing green, and FAIL is solid red. The third LED is STATUS
and is normally off but displays a steady orange if an alarm condition exists on the
board. Diagnostic checks include the following:
• The output servo current is out of limits or not responding, which creates a fault.
• The regulator feedback (LVDT) signal is out of limits. A fault is created and if
the associated regulator has two sensors, the bad sensor is removed from the
feedback calculation and the good sensor is used.
• The servo has suicided. This creates a fault.
• The A/D converter calibration voltage is out of limits and a default value is
being used.
• The LVDT excitation voltage is out of range. A fault is created
• The input signal varies from the voted value by more than the TMR differential
limit. This causes a fault to be created indicating a problem with this sensor
input.
• If any one of the above signals go unhealthy a composite diagnostic alarm,
L#DIAG_VSVO, occurs. Details of the individual diagnostics are available from
the toolbox. The diagnostic signals can be individually latched, and reset with
the RESET_DIA signal if they go healthy.
• Connectors JR1, JS1, JT1 on the terminal board have their own ID device that is
interrogated by the I/O board. The ID device is a read-only chip coded with the
terminal board serial number, board type, revision number, and the plug
location. When the chip is read by VSVO and a mismatch is encountered, a
Configuration
Configuration
System Limits Select system limits Enable, disable
Regulator 1 LVDT/R calibration Online LVDT calibration, yes/no
RegType Algorithm used in the regulator Unused 1_PulseRate
2_PlsRateMAX 1_LVposition
2_LVposMIN 2_LVposMAX
3_LVposMID 2_LvpilotCyl
4_LVp/cylMAX 4_LV_LM no_fbk
RegGain Position loop gain in (%current/%position) -200 to 200
RegNullBias Null bias in % current, balances servo spring force -100 to 100
DitherAmpl Dither in % current (minimizes hysteresis) Dither amp: 0 to 10
MinPOSvalue Position at Min End Stop in engineering units. -15 to 150
MaxPOSvalue Position at Max End Stop in engineering units. -15 to 150
MnLVDT1_Vrms LVDT1_Vrms at Min End Stop (Normally set by the 0 to 7.1
Calibration function)
MxLVDT1_Vrms LVDT1_Vrms at Max End Stop (Normally set by the 0 to 7.1
:
MnLVDT4_Vrms LVDT4_Vrms at Min End Stop (Normally set by the 0 to 7.1
MxLVDT4_Vrms LVDT4_Vrms at Max End Stop (Normally set by the 0 to 7.1
GEH-6421M
LVDT_Margin Used in the calibration function to calculate the 0 to 7.1
internal variables, Reg_Sensor_Hdwr_Lo and
Reg_Sensor_Hdwr_Hi for LVDT sensor check.
TMR_DiffLimt Difference limit off voted pulse inputs (EU) 0 to 12000
Monitor 1
Monitor type Monitor algorithm Unused 1_LVposition
2_LVposMIN 2_LVposMAX
3_LVposMID
MinPOSvalue Position at Min End Stop in engineering units. -15 to 150
MaxPOSvalue Position at Max End Stop in engineering units. -15 to 150
MnLVDT1_Vrms LVDT1_Vrms at Min End Stop (not set by the 0 to 7.1
MxLVDT1_Vrms LVDT1_Vrms at Max End Stop (not set by the 0 to 7.1
:
MnLVDT4_Vrms LVDT4_Vrms at Min End Stop (not set by the 0 to 7.1
MxLVDT4_Vrms LVDT4_Vrms at Max End Stop (not set by the 0 to 7.1
LVDT_Margin Used in the calibration function to calculate the 0 to 7.1
internal variables, Reg_Sensor_Hdwr_Lo and
Reg_Sensor_Hdwr_Hi for LVDT sensor check
done by the Monitor function.
TMR_DiffLimt Difference limit off voted pulse inputs (EU) 0 to 12000
J3:IS200TSVOH1A Terminal board 1 connected to VSVO through J3 Connected, not connected

Servo Output1 Measured output current in percent – Board point Point edit (input FLOAT)
Reg Number Identify regulator number Unused, Reg1, Reg2, Reg3, Reg4
Servo_MA_Out Select current output for coil windings 10, 20, 40, 80, 120 mA
EnableCurSuic Select Suicide function based on current Enable, disable
Curr_Suicide Percent current error to initiate suicide 0 to 100% (output current error)
EnablFbkSuic Select Suicide function based on position feedback Enable, disable
Fdbk_Suicide Percent position error to initiate suicide 0 to 100% (actuator position error)
Servo Output2 Measured output current in percent - Board point Point edit (input FLOAT)
J4:IS200TSVOH1A Terminal Board 2 connected to VSVO via J4 Connected, not connected
Servo Output3 Servo current output wired to valve - Board point Point edit (input FLOAT)
Servo Output4 Servo current output wired to valve - Board point Point edit (input FLOAT)
J5:IS00TSVOH1A Pulse Rate inputs cabled to J5 connector Connected, not connected
FlowRate1 Pulse rate input selected - Board point Point edit (input FLOAT)
PRType Select speed or flow type signal Unused, Speed, Flow, Speed_High,
Speed_LM
PRScale Convert Hz to engineering units 0 to 1,000
SysLim1Enabl Select system limit Enable, disable
SysLim1Latch Select whether alarm will latch Latch, not latch
SysLim1Type Select type of alarm initiation >= or <=
SysLimit Select alarm level in GPM or RPM 0 to 12,000
SystemLim2 Same as above Same as above
TMR_DiffLimt Difference limit off voted pulse inputs (EU) 0 to 12,000
FlowRate2 Pulse rate input selected - Board point (as above) Point edit (input FLOAT)
363
L3DIAG_VSVOR Board diagnostic Input BIT
L3DIAG_VSVOS Board diagnostic Input BIT
L3DIAG_VSVOT Board diagnostic Input BIT
R1_SuicideNVR Regulator 1 Suicide relay status, non-voted for VSVO-R Input BIT
R1_SuicideNVS Regulator 1 Suicide relay status, non-voted for VSVO-S Input BIT
R1_SuicideNVT Regulator 1 Suicide relay status, non-voted for VSVO-T Input BIT
SysLim1PR1 System Limit 1 indication for Pulse Rate 1 Input BIT
Reg1Suicide Regulator 1 suicide relay status Input BIT
: : Input BIT
Reg4Suicide Regulator 4 suicide relay status Input BIT
Reg1_PosAFlt Reg1, LM machine only, position A failure Input BIT
: : Input BIT
Reg4_PosAFlt Reg4, LM machine only, position A failure Input BIT
Reg1_PosBFlt Reg1, LM machine only, position B failure Input BIT
: : Input BIT
Reg4_PosBFlt Reg4, LM machine only, position B failure Input BIT
Reg1_PosDif1 Reg1, LM machine only, position difference failure Input BIT
: : Input BIT
: : Input BIT
RegCalMode Regulator under calibration Input BIT
Reg1_Fdbk Regulator 1 feedback Input FLOAT
: : Input FLOAT
Reg4_Fdbk Regulator 4 feedback Input FLOAT
MiscFdbk1a Reg1, PosA when 4_LV_LM or Pilot when 2_LvpilotCy or Input FLOAT
4_LVp/cylMax
MiscFdbk1b Reg1, PosB when 4_LV_LM or otherwise not used. Input FLOAT
4_LVp/cylMax
4_LVp/cylMax
4_LVp/cylMax
GEH-6421M
Reg1_Error Regulator 1 position or flow rate error Input FLOAT
: : Input FLOAT
Reg4_Error Regulator 4 position or flow rate error Input FLOAT
Accel1 GPM/sec based on Pulse Rate 1 Input FLOAT
Accel2 GPM/sec based on Pulse Rate 2 Input FLOAT
Mon1 Position feedback based on Monitor 1 Input FLOAT
: : Input FLOAT
Mon12 Position feedback based on Monitor 12 Input FLOAT
ServoOut1NVR Servo Current Output 1, non-voted for VSVO-R Input FLOAT
ServoOut1NVS Servo Current Output 1, non-voted for VSVO-S Input FLOAT
ServoOut1NVT Servo Current Output 1, non-voted for VSVO-T Input FLOAT
CalibEnab1 Enable calibration Reg 1 Output BIT
: : Output BIT
CalibEnab4 Enable calibration Reg 4 Output BIT
SuicideForce1 Force suicide on Reg 1 Output BIT
: : Output BIT
SuicideForce4 Force suicide on Reg 4 Output BIT
PossDiffEnab1 Position difference enable reg 1, LM only Output BIT
: : Output BIT
PossDiffEnab4 Position difference enable reg 4, LM only Output BIT
Reg1_Ref Reg 1 position reference Output FLOAT
: : Output FLOAT
Reg4_Ref Reg 4 position reference Output FLOAT
Reg1-GainMod Reg 1 gain modifier (don’t use) Output FLOAT
: : Output FLOAT
Reg4-GainMod Reg 4 gain modifier (don’t use) Output FLOAT
Reg1_NullCor Reg 1 null bias correction Output FLOAT
: : Output FLOAT
Reg4_NullCor Reg 4 null bias correction Output FLOAT
Internal Variables Internal variables to service the auto-calibration display, not configurable
365
Alarms
2 Flash Memory CRC Failure Board firmware programming error (board will
not go online)
3 CRC failure override is Active Board firmware programming error (board is
allowed to go online)
16 System Limit Checking is Disabled System checking was disabled by
configuration.
18 J3 ID Failure Failed ID chip on connector J3, or cable
problem
problem
problem
problem
22 J3A ID Failure Failed ID chip on connector J3A, or cable
problem
problem
24 Firmware/Hardware Incompatibility Invalid terminal board connected to VME I/O
board
30 ConfigCompatCode mismatch; Firmware: #; Tre: # The A tre file has been installed that is incompatible
configuration compatibility code that the firmware is with the firmware on the I/O board. Either the
expecting is different than what is in the tre file for this tre file or firmware must change. Contact the
board factory.
31 IOCompatCode mismatch; Firmware: #; Tre: # The A tre file has been installed that is incompatible
I/O compatibility code that the firmware is expecting is with the firmware on the I/O board. Either the
different than what is in the tre file for this board tre file or firmware must change. Contact the
factory.
33-44 LVDT # RMS Voltage Out of Limits. Minimum and The LVDT may need recalibration.
maximum LVDT limits are configured
45 Calibration Mode Enabled The VSVO was put into calibration mode.
46 VSVO Board Not Online, Servos Suicided. The servo is The controller (R, S, T) or IONet is down, or
suicided because the VSVO is not on-line there is a configuration problem with the
system preventing the VCMI from bringing the
board on line.
47-51 Servo Current # Disagrees with Reference, Suicided. A cable/wiring open circuit, or board problem.
The servo current error (reference - feedback) is greater
than the configured current suicide margin
52-56 Servo Current # Short Circuit. This is not currently used NA
57-61 Servo Current # Open Circuit. The servo voltage is greater A cable/wiring open circuit, or board problem.
than 5V and the measured current is less than 10%
62-66 Servo Position # Feedback Out of Range, Suicided. LVDT or board problem
Regulator number # position feedback is out of range,
causing the servo to suicide
67-71 Configuration Message Error for Regulator Number #. The LVDT minimum and maximum voltages
There is a problem with the VSVO configuration and the are equal or reversed, or an invalid LVDT,
servo will not operate properly regulator, or servo number is specified.
72 Onboard Calibration Voltage Range Fault. The A/D A problem with the Field Programmable Gate
calibration voltages read from the FPGA are out of limits, Array (FPGA) on the board
and the VSVO will use default values instead
73-75 LVDT Excitation # Voltage out of range There is a problem with the LVDT excitation
source on the VSVO board.
GEH-6421M
77 Servo output assignment mismatch. Regulator types 8 & 9 Fix the regulator configurations.
use two servo outputs each. They have to be consecutive
pairs, and they have to be configured as the same range
128- Logic Signal # Voting mismatch. The identified signal from A problem with the input. This could be the
191 this board disagrees with the voted value device, the wire to the terminal board, the
terminal board, or the cable.
224- Input Signal # Voting mismatch, Local #, Voted #. The A problem with the input. This could be the
259 specified input signal varies from the voted value of the device, the wire to the terminal board, the
signal by more than the TMR Diff Limit terminal board, or the cable.
TSVO Servo Input/Output

The Servo Input/Output (TSVO) terminal board interfaces with two electro-hydraulic
servo valves that actuate the steam/fuel valves. Valve position is measured with
LVDTs. Two cables connect to VSVO using the J5 plug on the front of VSVO and
the J3 or J4 connector on the VME rack. TSVO provides simplex signals through the
JR1 connector, and fans out TMR signals to the JR1, JS1, and JT1 connectors. Plugs
JD1 or JD2 are for an external trip from the protection module.
TSVO Terminal Board External VSVO Processor Board

trip
x
x x
x 1 JT1
x 2 x 3 37-pin "D" shell RUN
x 4 type connectors FAIL
x 6 x 5 JD1 STAT
x 8 x 7 with latching
x 10 x 9 JD2 fasteners
x 12 x 11
LVDT inputs x 13
Pulse rate inputs x 16 x 15
x 18 x 17
LVDT excitation x 19 Cables to VME
x 20 JT5 JS1
Servo coil outputs x 22 x 21 rack T
x 24 x 23
x
x
x 26 x 25 JS5
x 30 x 29 rack S
x 32 x 31 J5
x 34 x 33 JR1
x 36 x 35
x 38 x 37 JR5
x 40 x 39 VSVO
x 42 x 41 x
x 44 x 43
46 x 45
x
x 47 J3
x 48
x
x
Shield Connectors on
bar VME rack R J4
Barrier type terminal Cables to VME

blocks can be unplugged rack R
From second TSVO
TSVO Servo Terminal Board and VSVO Processor Board
367
Installation
Connect the wires for the sensors and servo valves directly to two I/O terminal
blocks on the terminal board, as displayed in the figure Servo Terminal Board
Wiring. Each block is held down with two screws and has 24 terminals accepting up
to #12 AWG wiring. A shield termination strip attached to chassis ground is located
immediately to the left of each terminal block. Connect the wires for the external trip
into JD1 or JD2. Cable the J5 connectors to the front of VSVO boards in racks <R>,
<S>, and <T>. Cable the J1 connectors to the VME rack below VSVO in <R>, <S>,
and <T>.
Each servo output can have three coils in TMR configuration. Each coil current is
jumper selected using JP1-6.
Servo/LVDT Terminal Board TSVOH1B

1 External Trip from 
2 GND
x
x 1 LVDT 01 (H)
LVDT 01 (L) x 2 JD1 1 External Trip
x 3 LVDT 02 (H)
LVDT 02 (L) x 4
x 5 LVDT 03 (H) 2 GND
LVDT 03 (L) x 6
LVDT 04 (L) x 8
x 7 LVDT 04 (H)
x 9 LVDT 05 (H) JD2
LVDT 05 (L) x 10
LVDT 06 (L) x 12
x 11 LVDT 06 (H)
x 13
x 14
x 15
x 16 To connectors
Exc R1 (L) x 17 Exc R1 (H)
x 18 JR5, JS5, JT5,
Exc R2 (L) x 19 Exc R2 (H)
x 20 JR1, JS1, JT1
Exc S (L) x 21 Exc S (H)
x 22
Exc T (L) x 24
x 23 Exc T (H)
x JP1 Servo Coil 01 R
JP2 Servo Coil 01 S

x
Servo 01 R (L) x 25 Servo 01 R (H) JP3 Servo Coil 01 T

x 26
Servo 01 S (L) x 27 Servo 01 S (H)
x 28
Servo 01 T(L) x 30
x 29 Servo 01 T (H)
x 31 Servo 01 SMX (H) JP4 Servo Coil 02 R
Servo 02SMX(H) x 32
Servo 02 R (L) x 34
x 33 Servo 02 R (H)
Servo 02 S (L) x 36
x 35 Servo 02 S (H) JP5 Servo Coil 02 S
x 37 Servo 02 T (H)
Servo 02 T (L) x 38
Pulse 02 (TTL)
x 39 Pulse 01 (TTL)
x 40 JP6 Servo Coil 02 T
Pulse 01 (24R) x 42
x 41 Pulse 01 (24V)
x 43 Pulse 01 (H)
Pulse 01 (L) x 44
x 45 Pulse 02 (24V) Jumper Choices:
Pulse 02 (24R) x 46
Pulse 02 (L)
x 47 Pulse 02 (H) 120B +/-120 ma (75 ohm coil)
x 48
x 120A +/-120 ma (40 ohm coil)
80 +/- 80 ma
40 +/- 40 ma
20 +/- 20 ma
10 +/- 10 ma

point with 300 V insulation from terminal board for maintenance
Servo Terminal Board Wiring
GEH-6421M
Operation
VSVO provides four channels consisting of bi-directional servo current outputs,
LVDT position feedback, LVDT excitation, and pulse rate flows inputs. The TSVO
provides excitation for, and accepts inputs from, up to six LVDT valve position
inputs. There is a choice of one, two, three, or four LVDTs for each servo control
loop. If three inputs are used they are available for gas turbine flow measuring
applications. These signals come through TSVO and go directly to the VSVO board
front at J5.
Each servo output is equipped with an individual suicide relay under firmware
control that shorts the VSVO output signal to signal common when de-energized,
and recovers to nominal limits after a manual reset command is issued. Diagnostics
monitor the output status of each servo voltage, current, and suicide relay.
Capacity <R> Control Module

6 LVDT/R inputs on each of 2
boards, and total of 2 active/passive Controller
magnetic pickups. Application Software
Termination
Board TSVOH1B
(Input portion) Servo Board
VSVO
JR1 J3
LVDT LVDT1H 1 Digital
3.2k Hz, SCOM A/D Regulator servo
7 V rms regulator
excitation A/D converter
2 P28VR
source LVDT1L D/A D/A converter
6 Ckts. P28V Servo driver P28V J3

Voltage
or LVDR Limit
Current
Suicide
P24V1 41 limit Relay
P24VR1 42 Configurable
Gain To Servo
Pulse rate P1TTL 39 Outputs
inputs 43( JR5 J5 3.2KHz
active probes PR P1H Pulse Excitation To TSVO
2 - 20 k Hz TTL P1L 44 Rate
To
Connector second
(PR only available 45 CL on front of TSVO
on 1 of 2 TSVOs) P24V2
46 VSVO
P24VR2
Pulse rate 40 board
P2TTL
inputs, P2H 47(
magnetic PR
MPU P2L 48
pickups
2 - 20 k Hz Noise suppr.
LVDT and Pulse Rate Inputs, Simplex (Part 1 of 2)
369
Each servo output channel can drive one or two-coil servos in simplex applications,
or two or three-coil servos in TMR applications. The two-coil TMR applications are
for 200# oil gear systems where each of two control modules drive one coil each,
and the third control module has no servo coil interface. Servo cable lengths up to
300 meters (984 feet) are supported with a maximum two-way cable resistance of 15
Ω. Because there are many types of servo coils, a variety of bi-directional current
sources are selectable by configuring jumpers.
Another trip override relay K1 is provided on each terminal board and is driven from
the Protection Module. If an emergency overspeed condition is detected in the
Protection Module, the K1 relay energizes and disconnects the VSVO servo output
from the terminal block and applies a bias to drive the control valve closed. This is
only used on simplex applications to protect against the servo amplifier failing high,
and is functional only with respect to the servo coils driven from <R>.
<R>
Controller Terminal Board

TSVOH1B (continued)
Servo Board
Coil current range
VSVO
10,20,40,80,120 ma
A/D converter
Digital
P28VR JD1
A/D Regulator servo 1 Trip input from
K1 module (J1)
regulator 2
From
LVDT D/A D/A converter P28VR JD2
JP1 1
TSVO 120B
120 2
Servo coil from<R>
Voltage 40 25 S1RH
Limit 20
10 31 S1SH
N
Suicide 1k 22 ohms
S
P28V Relay 2 Ckts. ohm 89 ohms
26 1k ohm
Configurable S1RL
Gain SCOM
17 ER1H
J5 3.2KHz,
3.2KHz
Pulse N 7V rms
Excitation
S 18 excitation
Rate ER1L
2 Ckts. SCOM source

Connector on Noise for LVDTs
front of VSVO To suppr-
second ession
TSVO
Servo Coil and LVDT Outputs, Simplex (Part 2 of2)
GEH-6421M
In TMR applications, the LVDT signals on TSVO fan out to three racks through
JR1, JS1, and JT1. Three connectors also bring power into TSVO where the three
voltages are diode high-selected and current limited to supply 24 V dc to the pulse
rate active probes.
<R>
<S>
<T>
Controller
Terminal
Board TSVOH1B Servo Board
(Input Portion) VSVO
LVDT JR1 J3 A/D converter Digital

LVDT1H 1
3.2k Hz, A/D Regulator servo
7 V rms regulator
P28VR
excitation
2
JS1 J3
source LVDT1L P28V D/A D/A converter
SCOM Same for <S>
6 Ckts. P28VS
Servo driver To servo
Voltage
JT1 J3 Limit outputs
on TSVO
Same for <T>
P28VT
Diode Voltage
Select
P24V1 41 CL P28V Connector on Configurable
front of VSVO Gain
P24VR1 42 card in <R>
JR5 J5 To TSVO
Pulse rate P1TTL 39 3.2KHz
inputs Pulse excitation
active probes
43( Rate
P1H
2 - 20 kHz
PR
44 JS5 J5 in <S>
TTL P1L

P24V2
on 1 of 2 TSVOs) 46 JT5 J5 in <T>
P24VR2
P2TTL
40
Pulse rate
P2H 47 (
inputs, PR
magnetic MPU P2L 48
pickups
Noise
2 - 20 kHz
suppression
LVDT and Pulse Rate Inputs, TMR (Part 1 of 2)
371
For TMR systems, each servo channel has connections to three output coils with a
range of current ratings up to 120 mA, selected by jumper.
<R>
<S>
<T>
Controller
Terminal Board
TSVOH1B (continued)
Servo Board
VSVO Servo current range
Digital 10,20,40,80,120 ma
A/D converter servo
JD1 Trip input from
regulator
A/D Regulator P28VR 1
2
 not used for
From Suicide TMR
TSVO P28VR JD2
D/A relay JP1
LVDT 120B
1
120 2
Servo coil from <R>
25 S1RH
Voltage 40
Limit 20
10 31
N
22 ohms
2 Ckts. S
89 ohms
26 S1RL 1k ohm
Configurable
Gain
17 ER1H 3.2KHz,
J5 3.2KHz 7V rms
Pulse excitation 2 Ckts S
N
18 excitation
Rate ER1L
source
Connector on J3 JS1 JP2 For LVDTs
front of VSVO 120B
120 Servo coil from <S>
card 80 27 S1SH
40
20
10 N
S
2 Ckts. 28 S1SL
21 ESH 3.2KHz,
1 Ckt. N 7V rms
S 22 ESL excitation
J3 JT1 source
JP3
120B
120
80
Servo coil from <T>
29 S1TH
40
20
10
N
S
2 Ckts. 30 S1TL
23 ETH 3.2KHz,
N 7V rms
1 Ckt. S 24 ETL excitation
source
Noise suppression
For LVDTs
Servo Coil Outputs and LVDT Excitation, TMR System (Part 2 of 2)
GEH-6421M
The following table defines the standard servo coil resistance and their associated
internal resistance, selectable with the terminal board jumpers shown in the figure
above. In addition to these standard servo coils, it is possible to drive non-standard
coils by using a non-standard jumper setting. For example, an 80 mA, 125 Ω coil
could be driven by using a jumper setting 120B.
Servo Coil Ratings
Jumpe Nominal Coil Resistance Internal

r Label Current (Ohms) Resistance (Ohms) Application
10 ±10 mA 1,000 180 Simplex and TMR
20 ±20 mA 125 442 Simplex
40 ±40 mA 62 195 Simplex
40 ±40 mA 89 195 TMR
80 ±80 mA 22 115 TMR
120A ±120 mA (A) 40 46 Simplex
120B ±120 mA (B) 75 10 TMR
The control valve position is sensed with either a four-wire LVDT or a three-wire
LVDR. Redundancy implementations for the feedback devices are determined by the
application software to allow the maximum flexibility. LVDT/Rs can be mounted up
to 300 meters (984 feet) from the turbine control with a maximum two-way cable
resistance of 15 Ω.
Each terminal board has two LVDT/R excitation sources for simplex applications
and four for TMR applications. Excitation voltage is 7 V rms and the frequency is
3.2 kHz with a total harmonic distortion of less than 1% when loaded.
Note The excitation source is isolated from signal common (floating) and is capable
of operation at common mode voltages up to 35 V dc, or 35 V rms, 50/60 Hz.
A typical LVDT/R has an output of 0.7 V rms at the zero stroke position of the valve
stem, and an output of 3.5 V rms at the designed maximum stoke position (these are
reversed in some applications). The LVDT/R input is converted to dc and
conditioned with a low pass filter. Diagnostics perform a high/low (hardware) limit
check on the input signal and a high/low system (software) limit check.
Two pulse rate inputs connect to a single J5 connector on the front of VSVO. This
dedicated connection minimizes noise sensitivity on the pulse rate inputs.
Both passive magnetic pickups and active pulse rate transducers (TTL type) are
supported by the inputs and are interchangeable without configuration. Pulse rate
inputs can be located up to 300 meters (984) from the turbine control cabinet; this
assumes shielded-pair cable is used with typically 70 nF single ended or 35 nF
differential capacitance and 15 ohms resistance.
A frequency range of 2 to 30 kHz can be monitored at a normal sampling rate of

either 10 or 20 ms. Magnetic pickups typically have an output resistance of 200 Ω
and an inductance of 85 mH excluding cable characteristics. The transducer is a high
impedance source, generating energy levels insufficient to cause a spark.
Note The maximum short circuit current is approximately 100 mA with a

maximum power output of 1 W.
373
Specifications
Item Specification
Number of inputs 6 LVDT windings
2 pulse rate signals (total of 2 per VSVO)
External trip signal
Number of outputs 2 servo valves (total of 4 per VSVO board)
4 excitation sources for LVDTs
2 excitation sources for pulse rate transducers
Power supply voltage Nominal 24 V dc
LVDT excitation output Frequency of 3.2 ±0.2 kHz
Voltage of 7.00 ±0.14 V rms
Pulse rate input Minimum signal for proper measurement at 2 Hz is 33 mVpk, and at 12 kHz is 827 mVpk.
Magnetic PR pickup signal Generates 150 V p-p into 60 kΩ
Active PR Pickup Signal Generates 5 to 27 V p-p into 60 kΩ
Fault detection Servo current out of limits or not responding
Regulator feedback signal out of limits
Failed ID chip
Size 17.8 cm high x 33.02 cm wide (7 in. x 13 in.)
Technology Surface mount
Diagnostics
VSVO performs diagnostic checks on the terminal board, including the following:
• If the output servo current is out of limits or not responding, a fault is created.
• If the regulator feedback (LVDT) signal is out of limits, a fault is created and if
the associated regulator has two sensors, the bad sensor is removed from the
feedback calculation and the good sensor is used.
• If any one of the above signals go unhealthy a composite diagnostic alarm,
L#DIAG_VSVO occurs. Details of the individual diagnostics are available from
the toolbox. The diagnostic signals can be individually latched, and reset with
the terminal board serial number, board type, revision number, and the J
connector location. When this chip is read by the I/O processor and a mismatch
is encountered, a hardware incompatibility fault is created.
Configuration
For a simplex system, jumper JP1 configures the coil current of Servo 1, and jumper
JP4 configures the coil current of Servo 2. Refer to the table Servo Coil Ratings for
more information.
In a TMR system, each servo output can have three coils.Jumpers JP 1 – 3 configure
the coil currentfor Servo 1, and Jumpers JP 4 – 6 configure the coil current for Servo
2. All other configuration is done from the toolbox.
GEH-6421M
VTCC Thermocouple Input
VTCC Thermocouple Input
The Thermocouple Input (VTCC) board accepts 24 thermocouple inputs. These
inputs are wired to the TBTC or DTTC terminal boards. Cables with molded plugs
connect the terminal board to the VME rack where the VTCC thermocouple
processor board is located. The TBTC can provide both simplex (TBTCH1C) or
triple module redundant (TMR) control (TBTCHIB). Two groups of the VTCC
provide different temperature ranges optimized for gas turbine control applications
(VTCCH1) and general-purpose applications (VTCCH2). The same terminal boards
are used with both groups of the VTCC card.
VTCCH1 supports E, J, K, S, and T types of thermocouples and mV inputs. The mV

span is -8mV to +45mV.
VTCCH2 supports E, J, K, S, T as well as B, N, and R types of standard

thermocouples and mV inputs. The mV span for VTCCH2 is -20mV to +95mV.
Note Input data is transferred over the VME backplane from VTCC to the VCMI
and then to the controller.
375
Volume II VTCC Thermocouple Input • 385
TBTC Terminal Board VTCC VME Board
x
x
x 2
x 1 TBTC, capacity for RUN
x 3 FAIL
x 4 24 thermocouple inputs STAT
TC x 6
x 5
inputs x 8
x 7
x 10
x 9
x 11 VME Bus to VCMI
x 12
x 14
x 13 communication board
x 16
x 15
x 18
x 17
x 19 37-pin "D" shell
x 20 JA1
x 21 type connectors
x 22
x 23 with latching
x 24
x
fasteners
x
x 26
x 25
x 28
x 27
TC x 30
x 29
32
x 31
inputs x
x 33 JB1
x 34
x 36
x 35
x 38
x 37 Cables to VME
x 40
x 39 rack
VTCC
x 42
x 41 x
x 44
x 43
x 46
x 45 Connectors on J3
x 48
x 47 VME rack
x
x
Shield bar
ground
J4
Barrier type terminal

from board for
maintenance
Thermocouple Input Terminal Board, I/O Board, and Cabling
Installation

its edge connectors
386 • VTCC Thermocouple Input 376 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Operation
Type E, J, K, S, and T thermocouples can be used with VTCCH1, and they can be
grounded or ungrounded. Type E, J, K, S, T, B, N and R thermocouples can be used
with VTCCH2, and they can be grounded or ungrounded. They can be located up to
300 m (984 ft) from the turbine control cabinet with a maximum two-way cable
resistance of 450 Ω. High frequency noise suppression and two cold junction (CJ)
reference devices are mounted on the terminal board.
Linearization for individual thermocouple types is performed in software by VTCC.

A thermocouple that is determined to be out of the hardware limits is removed from
the scanned inputs to prevent adverse affects on other input channels.
Cold Junctions
If both CJ devices are within the configurable limits, then the average of the two is
used for CJ compensation. If only one CJ device is within the configurable limits,
then that CJ is used for compensation. If neither CJ device is within the configurable
limits, then a default value is used. The thermocouple inputs and cold junction inputs
are automatically calibrated using the filtered calibration reference and zero voltages.
Note VTCC boards manufactured after software version VTCC-100100C and

higher have additional thermocouple and cold junction features. The newly designed
boards permit the use of S-type thermocouples, in addition to all previous types.
They also provide for a remote CJ compensation feature for thermocouple inputs.
This allows the user to select whether CJ compensation is done based on a
temperature reading at a remote location or at the terminal board as explained above.
The calculations are the same as previous VTCC boards, only the source of the CJ
reading changes.
Two CJ references are used per VTCC, one each for connectors J3 and J4. Each
reference can be selected as either remote (from VME bus) or local (from associated
terminal board, T-type or D-type). All references are then treated as sensor inputs
(for example, averaged, limits configured). The two references can be mixed, one
local and one remote. CJ signals go into signal space and are available for
monitoring. Normally the average of the two is used. Acceptable limits are
configured, and if a CJ goes outside the limit, a logic signal is set. A 1 °F error in the
CJ compensation causes a 1 °F error in the thermocouple reading.
Hard coded limits are set at 32 to 158 °F, and if a CJ goes outside this range, it is
regarded as bad. Most CJ failures are open or short circuit. If one CJ fails, the good
one is used. If both CJs fail, the backup value is used. This backup value can be
derived from CJ readings on other terminal boards, or can be the configured default
value.
377
<R> or <S> or <T> Rack
Terminal Board TBTC
Thermocouple Input Board VTCC
Local
cold junction Excitation
JA1 J3
reference
Remote cold
junction
Thermocouple references
High
Noise
Low Suppression
Grounded or (12) thermocouples Connectors at

ungrounded ID I/O Core
bottom of
VME rack A/D Processor
Local TMS320C32
cold junction Excit. VMEbus
JB1 J4
reference
Thermocouple
High
Noise
Low Suppression
(12) thermocouples
ID
Simplex Thermocouple Inputs to VTCC Processor Board
GEH-6421M
Terminal Board TBTCH1B <R> Rack
Thermocouple Input Board VTCC

JRA J3
Local ID Excitation.
CJ reference
Thermocouple High
Low NS
Remote CJ
Grounded or Noise JSA references
ungrounded suppression ID
To
<S>
(12) thermocouples Rack
JTA A/D Processor

ID
To VMEbus
<T>
Rack
I/O Core
Processor
TMS320C32
JRB J4 Excit.
Local ID
Cold Junction
Reference
Thermocouple High
Low NS
Grounded or JSB
ungrounded ID
(12) thermocouples Analog-Digital
To Converter
<S>
Rack
JTB
ID
To
<T>
Rack
TMR Thermocouple Inputs to VTCC Processor Boards
Thermocouple inputs are supported over a full-scale input range of -8.0 mV to +45.0
mV. The following table shows typical input voltages for different thermocouple
types versus the minimum and maximum temperature range. The CJ temperature is
assumed to range from +32 to +158 °F.
Thermocouple E J K S T
Low range, °F / °C −60 /−51 −60 / −51 −60 / −51 0 / −17.78 −60 / −51
mV at low range with reference at 158 °F (70°C) −7.174 −6.132 −4.779 −0.524 −4.764
High range, °F / °C 1100 / 593 1400 / 798 2000 / 1093 3200 / 1760 750 / 399
mV at high range with reference at 32 °F (0°C) 44.547 42.922 44.856 18.612 20.801
379
VTCCH1 Thermocouple Range
Thermocouple inputs are supported over a full-scale input range of -8.0 mV to +45.0
mV. The following table shows typical input voltages for different thermocouple
types versus the minimum and maximum temperature range. The CJ temperature is
assumed to range from 0 to 70°C (+32 to +158 °F).
Thermocouple Type E J K S T
VTCCH1
Low range, °F -60 -60 -60 0 -60
°C -51 -51 -51 -17.78 -51
mV at low range with -7.174 -6.132 -4.779 -0.524 -4.764
reference at 70°C (158 °F)
High range, °F 1100 1400 2000 3200 750

°C 593 760 1093 1760 399
mV at high range with 44.547 42.922 44.856 18.612 20.801
VTCCH2 Thermocouple Range
Thermocouple inputs support a full-scale input range of -20.0 mV to + 95.0 mV. The
following table shows typical input voltages for different thermocouple types versus
the minimum and maximum temperature range. The CJ temperature is assumed to
range from 0 to 70°C (+32 to +158 °F).
Thermocouple Type E J K S T
VTCCH2
Low range, °F -60 -60 -60 0 -60
°C -51 -51 -51 -17.78 -51
mV at low range with -7.174 -6.132 -4.779 -0.524 -4.764
High range, °F 1832 2192 2372 3200 752

°C 1000 1200 1300 1760 400
mV at high range with 76.373 69.553 52.41 18.612 20.869
Thermocouple Type B N R
VTCCH2
Low range, °F 32 -60 0
°C 0 -51 -17.78
mV at low range with -0.0114 -3.195 -0.512
High range, °F 3272 2282 3092

°C 1800 1250 1700
mV at high range with 13.593 45.694 20.220
GEH-6421M
Specifications
Item Specifications
Number of channels 24 channels per terminal board and I/O board
Thermocouple types E, J, K, S, T thermocouples, and mV inputs for VTCCH1
E, J, K, S, T, B, N, R thermocouples, and mV inputs for VTCCH2
Span -8 mV to +45 mV for VTCCH1
-20 mV to +95 mV for VTCCH2
A/D converter Sampling type 16-bit A/D converter with better than 14-bit resolution
CJ compensation Reference junction temperature measured at two locations on each terminal board (option
for remote CJs).
TMR board has six CJ references.
Cold junction temperature Cold junction accuracy 1.1ºC (2 ºF)
accuracy
Conformity error Maximum software error 0.14ºC (0.25 ºF)
Measurement accuracy VTCCH1 = 53 µV (excluding cold junction reading).
Example: For type K, at 1000 ºF, including cold junction contribution,
RSS error= 3 ºF
VTCCH1 = 115 µV (excluding cold junction reading).
Example: For type K, at 1000 ºF, including cold junction contribution,
RSS error= 6 ºF
Common mode rejection Ac common mode rejection 110 dB @ 50/60 Hz, for balanced impedance input
Common mode voltage ±5 V
Normal mode rejection Rejection of 250 mV rms is 80 dB @ 50/60 Hz
Scan time All inputs are sampled at 120 times per second for 60 Hz operation; for 50 Hz operation it is
100 times per second
High/low system (software) limit check
Monitor readings from all TCs, CJs, calibration voltages, and calibration zero readings
381
Diagnostics
Three LEDs at the top of the front panel provide status information. The normal run
condition is a flashing green, and fail is a solid red. The third LED shows a steady
orange if a diagnostic alarm condition exists in the board. Diagnostic checks include
the following:
• Each thermocouple type has hardware limit checking based on preset (non-
limit is exceeded a logic signal is set and the input is no longer scanned. If any
one of the 24 inputs hardware limits is set it creates a composite diagnostic
alarm, L3DIAG_VTCC, referring to the entire board. The diagnostic signals can
be individually latched, and then reset with the RESET_DIA signal.
• Each thermocouple input has system limit checking based on configurable high
and low levels. These limits can be used to generate alarms, and can be
configured for enable/disable, and as latching/non-latching. RESET_SYS resets
the out of limit signals.
• In TMR systems, if one signal varies from the voted value (median value) by
more than a predetermined limit, that signal is identified and a fault is created.
This can provide early indication of a problem developing in one channel.
• Each terminal board and I/O board has its own ID device, which is interrogated
by the I/O board. The board ID is coded into a read-only chip containing the
terminal board serial number, board type, revision number, and the JA1/JB1
connector location. When the chip is read by the I/O processor and a mismatch
is encountered, a hardware incompatibility fault is created. Details of diagnostic
faults are in the Alarms section of this document.
Configuration

Configuration
SysFreq System frequency (used for noise rejection) 50 or 60 Hz
SystemLimits Enables or disables all system limit checking Enable, disable
Auto Reset Automatic Restoring of Thermocouples removed from scan Enable, disable
J3J4:I200TBTCH1A Terminal board Connected, Not Connected
ThermCpl1 First of 24 thermocouples - board point signal Point edit (input FLOAT)
ThermoCpl Type Thermocouples supported by VTCC; unused inputs are Unused, mV, S, T, K, J, E
removed from scanning, mV inputs are primarily for
maintenance.
When configured for mV input, the signal span is –8 mV to
+45 mV. The input is not compensated for CJ and is a
straight reading of the terminal board mV input. In order to
detect open wires, each input is biased using plus and
minus 0.25 V through 10 Ω resistors. This should be taken
into account if high impedance mV signals are to be read.
LowPassFiltr Enable 2 Hz low pass filter Enable, disable
SysLim1 Enabl Enables or disables a temperature limit which can be used Enable, disable
to create an alarm.
SysLim1 Latch Determines whether the limit condition will latch or unlatch; Latch, unlatch
reset used to unlatch.
SysLim1 Type Limit occurs when the temperature is greater than or equal Greater than or equal, less
(>=), or less than or equal to (<=) a preset value. than or equal
GEH-6421M
SysLimit 1 Enter the desired value. Engineering units
SysLim2 Enabled Enables or disables a temperature limit which can be used Enable, disable
to create an alarm.
SysLim2 Latch Determines whether the limit condition will latch or unlatch; Latch, unlatch
reset used to unlatch.
SysLim2 Type Limit occurs when the temperature is greater than or equal Greater than or equal, less
(>=), or less than or equal to (<=) a preset value. than or equal
SysLimit 2 Enter the desired value. Engineering units
TMR Diff Limt Limit condition occurs if 3 temperatures in R, S, T differ by -60 to 2,000
more than a preset value (deg F); this creates a voting
alarm condition.
ColdJunc1 First CJ reference - Board point signal (similar As above (input FLOAT)
configuration as for thermocouples but no low pass filter or
CJ type choices of local or remote).
ColdJunc2 Second CJ reference – Board point signal (similar As above (input FLOAT)
configuration as for thermocouples but no low pass filter or
CJ type choices of local or remote).
Board Points
(Signals) Description-Point Edit (Enter Signal Connection Name) Direction Type
L3DIAG_VTCC1 Board diagnostic Input BIT
SysLim1TC1 System limit 1 for thermocouple Input BIT
: : Input BIT
SysLim1CJ1 System limit 1 for CJ Input BIT
SysLim1JC2 System limit 1 for CJ Input BIT
: : Input BIT
CJ Backup CJ backup Output FLOAT
CJ Remote 1 CJ remote 1 Output FLOAT
CJ Remote 2 CJ remote 2 Output FLOAT
ThermCpl1 Thermocouple reading Input FLOAT
: : Input FLOAT
ThermCpl24 Thermocouple reading Input FLOAT
ColdJunc1 CJ for thermocouples (TC) 1-12 Input FLOAT
ColdJunc2 CJ for TCs 13-24 Input FLOAT
383
Alarms
2 Flash Memory CRC Failure Board firmware programming error (board will
not go online)
19 J4 ID Failure. Failed ID chip on connector J4, or cable problem
problem
problem
board
30 ConfigCompatCode mismatch; Firmware: [ ] ; Tre: [ ] The A tre file has been installed that is incompatible
configuration compatibility code that the firmware is with the firmware on the I/O board. Either the tre
expecting is different than what is in the tre file for this board file or firmware must change. Contact the
factory.
31 IOCompatCode mismatch; Firmware: [ ]; Tre:[ ] The I/O A tre file has been installed that is incompatible
compatibility code that the firmware is expecting is different with the firmware on the I/O board. Either the tre
than what is in the tre file for this board file or firmware must change. Contact the
factory.
32-55 Thermocouple [ ] Raw Counts High. The [ ] thermocouple A condition such as stray voltage or noise
input to the analog to digital converter exceeded the caused the input to exceed +63 millivolts.
converter limits and will be removed from scan
56-79 Thermocouple [ ] Raw Counts Low. The [ ] thermocouple The board has detected a thermocouple open
input to the analog to digital converter exceeded the and has applied a bias to the circuit driving it to
converter limits and will be removed from scan a large negative number, or the TC is not
connected, or a condition such as stray voltage
or noise caused the input to exceed -63
millivolts.
80,81 Cold Junction [ ] Raw Counts High. CJ device number [ ] The CJ device on the terminal board has failed.
input to the A/D converter has exceeded the limits of the
converter. Normally two CJ inputs are averaged; if one is
detected as bad then the other is used. If both CJs fail, a
predetermined value is used
82,83 Cold Junction [ ] Raw Counts Low. CJ device number [ ] The CJ device on the terminal board has failed.
input to the A/D converter has exceeded the limits of the
converter. Normally two CJ inputs are averaged; if one is
detected as bad then the other is used. If both CJs fail, a
predetermined value is used
84,85 Calibration Reference [ ] Raw Counts High. Calibration The precision reference voltage on the board
Reference [ ] input to the A/D converter exceeded the has failed.
converter limits. If Cal. Ref. 1, all even numbered TC inputs
will be wrong; if Cal. Ref. 2, all odd numbered TC inputs will
be wrong
86,87 Calibration Reference [ ] Raw Counts Low. Calibration The precision reference voltage on the board
Reference [ ] input to the A/D converter exceeded the has failed.
converter limits. If Cal. Ref. 1, all even numbered TC inputs
will be wrong; if Cal. Ref. 2, all odd numbered TC inputs will
be wrong
88,89 Null Reference [ ] Raw Counts High The null reference voltage signal on the board
has failed.
GEH-6421M
90,91 Null Reference [ ] Raw Counts Low. The null (zero) The null reference voltage signal on the board
reference number [ ] input to the A/D converter has has failed.
exceeded the converter limits. If null ref. 1, all even
numbered TC inputs will be wrong; if null ref. 2, all odd
numbered TC inputs will be wrong
92-115 Thermocouple [ ] Linearization Table High. The thermo- The thermocouple has been configured as the
couple input has exceeded the range of the linearization wrong type, or a stray voltage has biased the TC
(lookup) table for this type. The temperature will be set to the outside of its normal range, or the CJ
table's maximum value compensation is wrong.
116- 139 Thermocouple [ ] Linearization Table Low. The thermo - The thermocouple has been configured as the
couple input has exceeded the range of the linearization wrong type, or a stray voltage has biased the TC
(lookup) table for this type. The temperature will be set to the outside of its normal range, or the CJ
table's minimum value compensation is wrong.
160- 255 Logic Signal [ ] Voting mismatch A problem with the input. This could be the
device, the wire to the terminal board, the
terminal board, or the cable.
256- 281 Input Signal [ ] Voting mismatch, Local [ ], Voted [ ]. The A problem with the input. This could be the
specified input signal varies from the voted value of the device, the wire to the terminal board, the
signal by more than the TMR Diff Limit terminal board, or the cable.
TBTC Thermocouple Input

The Thermocouple Input (TBTC) terminal board accepts 24-type E, J, K, S, or T
thermocouple inputs. It accepts additional B, N and R types of thermocouple inputs
only when used with PTCCH2 in Mark VIe. These inputs are wired to two barrier-
type blocks on the terminal board. TBTC communicates with the I/O processor
through DC-type connectors. Two types of the TBTC are available, as follows:
• TBTCH1C for simplex applications has two DC-type connectors.

• TBTCH1B for TMR applications has six DC-type connectors.
Mark VI Systems
In the Mark VI system, TBTC works with the VTCC processor and supports simplex
and TMR applications. One TBTCH1C connects to the VTCC with two cables. In
TMR systems, TBTCH1B connects to three VTCC boards with six cables.
Mark VIe Systems
In the Mark VIe system, TBTC works with the PTCC I/O pack and supports
simplex, dual, and TMR applications. In simplex systems, two PTCC packs plug into
the TBTCH1C for a total of 24 inputs. With the TBTCH1B, one, two, or three PTCC
packs can be connected, supporting a variety of system configurations.
• Simplex pack – 12 inputs

• Simplex packs – 24 inputs
• TMR packs – 12 inputs
385
The Thermocouple Input (TBTC) terminal board accepts 24-type E, J, K, S, or T
thermocouple inputs for PTCCH1 pack and 24-type E, J, K, S,T,B,N or R
thermocouple inputs for PTCCH2 pack.
TBTCH1C Terminal Board TBTCH1B Terminal Board

Simplex TMR
x x
x TBTCH1C, x TBTCH1B,
x 1 x 1 JTA JTB
x 2 capacity for x 2 capacity for
x 4
x 3 x 4
x 3
x 5 24 thermocouple x 5 24 thermocouple
12 TC x 6 x 6
x 7 inputs x 7 inputs (with Packs
Inputs x 8 x 8
x 9 x 9 only 12 inputs)
x 10 x 10
x 12
x 11 x 12
x 11
x 14
x 13 x 14
x 13
x 16
x 15 x 16
x 15
x 18
x 17 J ports: x 18
x 17
x 19 JA1 x 19
x 20 x 20 JSA JSB
x 22
x 21 Plug in PTCC I/O Pack(s) x 22
x 21
x 24
x 23 for Mark VIe system x 24
x 23
x x
or
x x
x 26
x 25 Cables to VTCC boards x 26
x 25
x 28
x 27 for Mark VI system; x 28
x 27
12 TC x 30
x 29 x 30
x 29
32
x 31 32
x 31
Inputs x JB1 x JRA JRB
x 34
x 33 For TBTCH1B the number x 34
x 33
x 36
x 35 and location of PTCC I/O x 36
x 35
x 37 points depends on the level x 37
x 38 x 38
x 39 of redundancy required. x 39
x 40 x 40
x 42
x 41 x 42
x 41
x 44
x 43 x 44
x 43
x 45 x 45
x 46 x 46
x 48
x 47 x 48
x 47
x x
x x
Shield Bar BarrierType Terminal Shield Bar BarrierType Terminal

Ground Blocks can be unplugged Ground Blocks can be unplugged
from board for from board for
maintenance maintenance
Thermocouple Terminal Board, I/O Processor, and Cabling
Installation
Connect the thermocouple wires directly to the two I/O terminal blocks. These
removable blocks are mounted on the terminal board and held down with two
screws. Each block has 24 terminals accepting up to #12 AWG wires. A shield
terminal strip attached to chassis ground is located on the left side of each terminal
block.
In Mark VI systems, cable the TBTC J-type connectors to the I/O processors in the
VME rack.
In Mark VIe systems, plug the I/O packs directly into the TBTC J-type connectors.
The number of cables or I/O packs depends on the level of redundancy required.
GEH-6421M
Operation
The 24 thermocouple inputs can be grounded or ungrounded. They can be located up
to 300 m (984 ft) from the turbine control panel with a maximum two-way cable
resistance of 450 Ω. TBTC features high-frequency noise suppression and two CJ
reference devices, as shown in following figure. The I/O processor performs the
analog-to-digital conversion and the linearization for individual thermocouple types.
In Mark VI simplex systems using TBTCH1C, one VTCC is used. In Mark VIe
simplex systems, two PTCC packs plug into TBTC, obtaining 24 thermocouple
inputs.
Terminal Board TBTCH1C

Thermocouple I/O Processor
I/O Processor is either

Cold Junction JA1 Excitation
remote (Mark VI) or local
Reference
(Mark VIe)
Thermocouple
High
Noise
Low Suppression
A/D
Processor
Conv
Grounded or (12) thermocouples
ungrounded ID
Cold Junction JB1

Reference
JB1 cables to I/O controller

Thermocouple
High
Noise
Low Suppression
(12) thermocouples
ID
Thermocouple Inputs and I/O Processor, Simplex
387
For TMR systems using TBTCH1B, the thermocouple signals fan out to three J-
connectors. The Mark VI system accommodates 24 inputs and the Mark VIe system
accommodates 12 inputs.
The TBTC terminal board supports all thermocouple spans documented for the
associated thermocouple I/O processor.
Termination Board TBTCH1B Thermocouple I/O Processor

<R>
JRB Excitation.
ID I/O Processor is either
Cold Junc. remote (Mark VI) or
Refer. local (Mark VIe)
Thermocouple High
Low NS
Grounded or Noise JSB

ungrounded Suppression ID
A/D Processor
(12) thermocouples Conv.
JTB
ID
JRA
ID
Cold Junc.
Refer.
Thermocouple High
Low NS
Grounded or JSA
ungrounded ID
(12) thermocouples
Other selected J-ports cable to I/O
Processor VTCC for Mark VI systems,
or
connect PTCC I/O Packs for Mark VIe,
JTA for <S> and <T>.
ID
Thermocouple Inputs and I/O Processor, TMR systems
Cold Junctions
The CJ signals go into signal space and are available for monitoring. Normally the
average of the two is used. Acceptable limits are configured, and if a CJ goes outside
the limit, a logic signal is set. A 1 °F error in the CJ compensation will cause a 1 °F
error in the thermocouple reading.
Hard-coded limits are set at -40 to 85°C (-40 to +185 ºF), and if a CJ goes outside
this, it is regarded as bad. Most CJ failures are open or short circuit. If the CJ is
declared bad, the backup value is used. This backup value can be derived from CJ
readings on other terminal boards, or can be the configured default value (refer to
signals in the section, Configuration).
GEH-6421M
Specifications
Item Specification
Number of channels 24 channels per terminal board
Thermocouple types E, J, K, S, T thermocouples, and mV inputs if TBTC is connected to PTCCH1 or
VTCCH1
E, J, K, S, T, B, N ,R thermocouples, and mV inputs if TBTC is connected to PTCCH2
or VTCCH2
Span -8 mV to +45 mV if TBTC is connected to PTCCH1 or VTCCH1
-20 mV to +95 mV if TBTC is connected to PTCCH2 or VTCCH2
Cold junction compensation Reference junction temperature measured at two locations on each H1C terminal board
TMR H1B board has six CJ references. Only three available with Mark VIe I/O packs.
Cold junction temperature CJ accuracy 1.1ºC (2 ºF)
accuracy
Monitor readings from all TCs, CJs, calibration voltages, and calibration zero readings.
Diagnostics
• Each thermocouple type has hardware-limit checking based on preset (non-

limit is exceeded, a logic signal is set and the input is no longer scanned. If any
one of the inputs hardware limits is set, it creates a composite diagnostic alarm.
• Each terminal board connector has its own ID device that is interrogated by the
I/O board. The board ID is coded into a read-only chip containing the terminal
board serial number, board type, revision number, and the J connector location.
If a mismatch is encountered, a hardware incompatibility fault is created.
• When operating with the I/O processor a very small current is injected into each
thermocouple path. This is done to detect open circuits and is of a polarity to
create a low temperature reading should a thermocouple open.
DTTC Simplex Thermocouple Input

The Simplex Thermocouple Input (DTTC) terminal board is a compact terminal
board designed for DIN-rail mounting. The board has 12 thermocouple inputs and
connects to the VTCC thermocouple processor board with a single 37-pin cable. This
cable is identical to the one used on the larger TBTC terminal board. The on-board
signal conditioning and CJ reference are identical to those on the TBTC board.
Note An on-board ID chip identifies the board to the VTCC for system diagnostic
purposes.
Two DTTC boards can be connected to the VTCC for a total of 24 inputs. High-
density Euro-Block type terminal blocks are permanently mounted to the board with
two screw connections for the ground connection (SCOM). Every third screw
connection is for the shield. Only the simplex version of the board is available. The
terminal boards can be stacked vertically on the DIN-rail to conserve cabinet space.
Note The DTTC board does not work with the PTCC I/O pack.
389
Notes
390 of 1016
VTUR Turbine Specific Primary Trip
VTUR Primary Turbine Protection

The Primary Turbine Protection (VTUR) board, has the following functions:
• Measures the turbine speed with four passive pulse rate devices and passes the
signal to the controller, which generates the primary overspeed trip
• Provides automatic generator synchronizing and closes the main breaker
• Monitors induced shaft voltage and current
®
• Monitors eight Geiger-Mueller flame detectors on gas turbine applications.
The detectors connect to TRPG and use 335 V dc, 0.5 mA from an external
supply.
• Controls three primary overspeed trip relays on the TRPx terminal board. The
controller generates the trip signal, which is sent to VTUR and then to TRPx to
trip the emergency solenoids. The turbine overspeed trip can come from VTUR
or VPRO. TRPx contains nine magnetic relays to interface with three trip
solenoids, known as the electrical trip devices (ETD). Nine relays are used in
TMR systems, three in simplex systems.
Board Versions
There are two board versions as follows:
• VTURH1 drives three trip solenoids using one TRPx board and accepts eight
flame detectors
• VTURH2 is a two-slot version that drives six trip solenoids using two TRPx
boards, but only accepts eight flame detectors
391
Volume II VTUR Turbine Specific Primary Trip • 403
TTURH1B Terminal Board VTUR VME Board
Breakers
x
Generator volts x 37-pin "D" shell
x
Bus volts x 1 JT1 type connectors
x 2 RUN
Shaft volts x 4 x 3 with latching FAIL
x 6
x 5 fasteners STAT
Shaft current x 7
x 8
x 10
x 9
x 12 x 11
x 14 x 13
x 16
x 15
x 20
x 19 JT5 JS1 rack T
x 22
x 21
24 x 23
x VME bus to VCMI
x
x
Magnetic x 25 JS5
x 26
speed x 28 x 27 Cables to VME
30 x 29 rack S J
pickups (12) x
x 31
x 32 JR1 5
x 34 x 33
x 36
x 35
x 38
x 37 JR5
x 40
x 39 VTUR
x 42
x 41 x
x 44
x 43
46
x 45
x
x 47 J3
x 48
x
TB3 x
Wiring to
Shield bar TTL speed Connectors on
pickups VME rack R J4
Cables to VME
Barrier type terminal rack R
Cable to TRPG
VTUR Turbine Control Board, Terminal Boards, and Cabling
Installation

its edge connectors
Note Cable connections to the terminal boards are made at the J3 connector on
the lower portion of the VME rack. These are latching type connectors to secure
the cables. Cable connection to the J5 connector on TTUR is made from J5 on
the front panel. The cable to TRPG connects at J4. Power up the VME rack and
check the diagnostic lights at the top of the front panel, for details refer to the
section on diagnostics in this document.
404 • VTUR Turbine Specific Primary Trip 392 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Operation
In simplex applications, up to four pulse rate signals can be used to measure turbine
speed. Generator and bus voltages are brought into VTUR for automatic
synchronizing in conjunction with the turbine controller and excitation system.
TTUR has permissive generator synchronizing relays and controls the main breaker
relay coil 52G. Shaft voltage is picked up with brushes and monitored along with the
current to the machine case.
Note VTUR contains the pulse rate to digital circuits. VTUR alarms high voltages
and tests the integrity and continuity of the circuitry.
The following figures show the VTUR simplex and TMR turbine speed inputs and
generator synchronizing circuits.
TTURH1B Terminal Board <R> Control Generator Breaker 52G

(input portion) Rack feedback
a
JR1 J3 Turbine
Gen. GENH
17 suppression 02 01
Board Terminal Board TTURH1B
volts
VTUR (continued)
120 V ac NS
from PT GENL 18 28Vdc
Pulse
Rate J3 JR1 TMR JP1
SMX
MUX K25P
Bus BUSH 19 ID A/D RD Synch. Perm.
volts
120 Vac NS Ac&Dc Mon
20 Shaft
from PT BUSL TMR
test SMX
JP2
To K25
TPRO Trip RD Auto Synch
solenoids
SVH
21 Mon
Flame
175V NS sensors K25A
SVL 22 Synch. check
from VPRO
Shaft J5
23 Mon
SCH J4
14V NS
SCL 24
J8 08 06,7 05 04 03
Connectors
5 (TB3)
Machine case TTL1_R
JR5 at bottom of
VME rack B M A
)
MPU1RH 41 K A U
#1 Primary Filter
Magnetic NS Clamp Trip R N T
MPU1RL 42 AC
signals O
Speed PU Coupling H
6 (TB3) to
TTL2_R
TRPG P125Gen
)
MPU2RH 43 Filter
#2 Primary
Clamp Note 1: TTL option only
Magnetic
44 NS AC ID
Speed PU MPU2RL
Coupling
available on first two
Speed pickups. 52G
45 Note 2: An external normally
#3 Primary Filter b
Clamp
Magnetic NS AC closed auxiliary breaker
46
Speed PU Coupling
contact must be provided in
Breaker coil
47 the breaker close coil circuit
#4 Primary Filter
Magnetic Clamp as indicated.
48 NS AC N125Gen
Speed PU Coupling Note 3: Signal to K25A
comes from TREG/VPRO
through TRPG & VTUR.
VTUR Turbine Speed Inputs and Generator Synchronizing on TTUR, Simplex
393
52G
a
<T> Generator Breaker
<S> Feedback
Terminal Board TTURH1B <R>
(input portion) Turbine Terminal Board TTURH1B 02 01
B52GH
B52GL
Board (continued)
Noise JR1 J3 VTUR
GENH 17 Suppression
J3 JR1
Gen. Volts 28Vdc
NS f( )
120 Vac
GENL 18 JP1
from PT Pulse TMR
Rate/ SMX
Digital K25P
2 RD Synch.
BUSH 19 MUX
JS1 3 Permissve
Bus Volts J3 JS1
A/D
120 Vac NS JP2 TMR
BUSL 20
from PT AC&DC SMX
shaft K25
To 2
test RD Auto Synch.
TPRO 3
Trip J3 JT1
SVH 21 solenoids
JT1
175V NS Flame K25A
SVL 22
sensors Synch. check
from VPRO
J4
Shaft J5
23
SCH Mon
14V Connectors
NS at bottom of
SCL 24
VME rack
5 (TB3) J8 08 07 06 05 04 03
Machine Case TTL1R JR5
)
MPU1RH 41
#1 Primary
BKRH
MAN
Filter
AUTO
Magnetic
Clamp Trip
NS AC
Speed PU MPU1RL 42 Coupling
Signals to
4 Circuits* TRPG
3 (TB3) P125Gen
TTL1S JS5 Note 1: TTL option only
)
MPU1SH 33 available on first two circuits.

#2 Primary Filter
of each group of 4 pickups*. 52G
Clamp
Magnetic NS AC
b
Speed PU MPU1SL 34 Coupling
Note 2: An external normally
4 Circuits*
1 (TB3)
closed auxiliary breaker
Bkr Coil
TTL1T JT5 contact must be provided in
To Rack S
)
MPU1TH 25 the Breaker close coil circuit

#3 Primary Filter
as indicated.
Clamp
Magnetic NS AC N125Gen
26
Speed PU MPU1TL Coupling
Note 3: Signal to K25A
4 Circuits* comes from TREG/VPRO
To Rack T
VTUR Turbine Speed Inputs and Generator Synchronizing, TMR
Speed Pickups
Note The median speed signal is used for speed control and for the primary
overspeed trip signal.
VTUR interfaces with four passive, magnetic speed inputs with a frequency range of
2 to 20,000 Hz. Using passive pickups on a sixty- tooth wheel, circuit sensitivity
allows detection of 2-RPM turning gear speed to determine if the turbine is stopped
(zero speed). If automatic turning gear engagement is provided in the turbine control,
this signal initiates turning gear operation.
GEH-6421M
The primary overspeed trip calculations are performed in the controller using
algorithms similar to (but not the same as) those in the VPRO protection board. The
fast trip option used on gas turbines runs in VTUR.
Primary Trip Solenoid Interface
The normal primary overspeed trip is calculated in the controller and passed to the
VTUR and then to the chosen primary trip terminal board. TRPx contains relays to
interface with the ETDs. TRPx typically works in conjunction with an emergency
trip board (TREx) to form the primary and emergency sides of the interface to the
ETDs. VTUR supports up to three ETDs driven from each TRPx/TREx combination.
VTUR supports the following trip boards:
• TRPG is targeted at gas turbine applications and works in conjunction with the
TREG board for emergency trip.
• TRPS is used for small and medium size steam turbine systems and works in
conjunction with the TRES board for emergency trip.
• TRPL is intended for large steam turbine systems and works in conjunction with
the TREL board for emergency trip.
Note Additional trip boards are being developed for other specific applications.
To support trip board operation, VTUR provides discrete inputs used to monitor
signals such as trip relay position, synchronizing relay coil drive, and ETD power
status.
Fast Overspeed Trip
In special cases where a faster overspeed trip system is required, the VTUR Fast
Overspeed Trip algorithms can be enabled. The system employs a speed
measurement algorithm using a calculation for a predetermined tooth wheel. Two
overspeed algorithms are available as follows:
• PR_Single uses two redundant VTURs by splitting up the two redundant PR

transducers, one to each board. PR_Single provides redundancy and is the
preferred algorithm for LM gas turbines.
• PR_Max uses one VTUR connected to the two redundant PR transducers.
PR_Max allows broken shaft and deceleration protection without the risk of a
nuisance trip if one transducer is lost.
The fast trips are linked to the output trip relays with an OR-gate. VTUR computes
the overspeed trip instead of the controller, so the trip is very fast. The time from the
overspeed input to the completed relay dropout is 30 ms or less.
395
Input Signal Space
Firmware
Config. Inputs
param. Scaling
Input, PR1 RPM PulseRate1
PR1Type, d RPM/sec Accel1
PR1Scale 2
PulseRate2 dt
------ Four Pulse Rate Circuits ------- RPM PulseRate2
RPM/sec Accel4
Fast Overspeed Protection
FastTripType PR_Single
PulseRate1 A
PR1TrEnable B
R
PR1TrPerm
PulseRate2 A
A>B S
PR2Setpoint B FastOS2Trip
PR2TrEnable R
PR2TrPerm
PulseRate3 A
PR3TrEnable B
R
PR3TrPerm
PulseRate4 A
A>B S FastOS4Trip
PR4Setpoint B
PR4TrEnable R
PR4TrPerm
InForChanA Accel1
Accel2 Input AccelA
Accel3 cct. A S
Accel4 select A>B AccATrip
AccASetpoint
B R
AccelAEnab
AccelAPerm
InForChanB Accel1
Accel2 Input AccelB
Accel3 cct. A S AccBTrip
Accel4 select A>B
AccBSetpoint B R
AccelBEnab Fast Trip
AccelBPerm Path
ResetSys, VCMI, Mstr False = Run
OR
PTR1 Primary Trip Relay, normal Path, True= Run True = Run Output, J4,PTR1
AND
PTR1_Output
PTR2 Primary Trip Relay, normal Path, True= Run AND True = Run Output, J4,PTR2
PTR2_Output
PTR3_Output -------------Total of six circuits -----
PTR4_Output Output, J4A,PTR5
PTR5 True = Run
PTR5_Output True = Run Output, J4A,PTR6
PTR6
PTR6_Output
Fast Overspeed Algorithm, PR-Single
GEH-6421M
Input Config. Signal Space
Firmware
param. Scaling inputs
Input, PR1 PulseRate1 RPM PulseRate1
PR1Type, RPM/sec Accel1
2 d
PR1Scale
dt RPM PulseRate2
PulseRate2
Accel1 Accel2
------ Four Pulse Rate Circuits -------RPM/sec
Accel3 RPM/sec Accel3
RPM/sec Accel4
FastTripType PR_Max Fast Overspeed Protection
DecelPerm
DecelEnab
DecelStpt
InForChanA
InForChanB
Accel1 Input AccelA
Neg A
Accel2 cct. S
Accel3 AB
PulseRate4 AccelB PulseRateB B
PR1/2Max
PulseRate1 A
PulseRate2 MAX A>B S FastOS1Trip
FastOS1Stpt B
FastOS1Enab R
FastOS1Perm
PR3/4Max
PulseRate3 A
PulseRate4 MAX A>B S FastOS2Trip
FastOS2Stpt B
FastOS2Enab R
FastOS2Perm
N/C FastOS3Trip
PR1/2Max N/C FastOS4Trip
A
|A-B| A
PR3/4Max A>B S
DiffSetpoint B FastDiffTrip
B
DiffEnab R
DiffPerm
Fast Trip
ResetSys, VCMI, Mstr Path
OR
False = Run

PTR1_Output
PTR2_Output
PTR3_Output -------------Total of six circuits --------- True = Run Output, J4A,PTR4
PTR4
PTR5_Output
PTR6_Output
Fast Overspeed Algorithm, PR-Max
397
Shaft Voltage and Current Monitor
Bearings can be damaged by the flow of electrical current from the shaft to the case.
This current can occur for several reasons:
• A static voltage can be caused by droplets of water being thrown off the last
stage buckets in a steam turbine. This voltage builds up until a discharge occurs
through the bearing oil film.
• An ac ripple on the dc generator field can produce an ac voltage on the shaft
with respect to ground through the capacitance of the field winding and
insulation. Note that both of these sources are weak, so high impedance
instrumentation is used to measure these voltages with respect to ground.
• A voltage can be generated between the ends of the generator shaft due to
dissymmetries in the generator magnetic circuits. If the insulated bearings on the
generator shaft breakdown, the current flows from one end of the shaft through
the bearings and frame to the other end. Brushes can be used to discharge
damaging voltage buildup, and a shunt should be used to monitor the current
flow.
The turbine control continuously monitors the shaft to ground voltage and current,
and alarms excessive levels. There is an ac test mode and a dc test mode. The ac test
applies an ac voltage to test the integrity of the measuring circuit. The dc test checks
the continuity of the external circuit, including the brushes, turbine shaft, and the
interconnecting wire.
Note The dc test is driven from the R controller only. If the R controller is down,
this test cannot be run successfully.
Flame Detectors
When used with TRPG, VTUR monitors signals from eight Geiger-Mueller flame
detectors. With no flame present, the detector charges up to the supply voltage. The
presence of the flame causes the detector to charge to a level and then discharge
through TRPG. As the flame intensity increases the discharge frequency increases.
When the detector discharges, VTUR and TRPG convert the discharged energy into
a voltage pulse. The pulse rate varies from 0 to 1,000 pulses/sec. These voltage
pulses are fanned out to all three modules. Voltage pulses above 2.5 V generate a
logic high, and the pulse rate over a 40 ms time period is measured in a counter.
Automatic Synchronizing
All synchronizing connections are located on the TTUR terminal board. The
generator and bus voltages are provided by two, single phase, potential transformers
(PTs) with a fused secondary output supplying a nominal 115 V rms. Measurement
accuracy between the zero crossing for the bus and generator voltage circuits is 1
degree.
Turbine speed is matched against the bus frequency. The generator and bus voltages
are matched by adjusting the generator field excitation voltage from commands sent
between the turbine controller and the EX2000 over the Unit Data Highway (UDH).
A command is given to close the breaker when all permissions are satisfied. The
breaker is predicted to close within the calculated phase/slip window. Feedback of
the actual breaker closing time is provided by a 52G/a contact from the generator
breaker (not an auxiliary relay) to update the database. An internal K25A sync check
relay is provided on the TTUR; the independent backup phase/slip calculation for
this relay is performed in the protection module. Diagnostics monitor the relay
coil and contact closures to determine if the relay properly energizes or de-energizes
upon command.
GEH-6421M
Sync Display Description
Sync Permissive Gen voltage: OK/not OK
Bus voltage: OK/not OK
Gen frequency: OK/not OK
Bus frequency: OK/not OK
Difference volts: OK/not OK
Difference frequ:OK/not OK
Phase: K25, OK/not OK
K25A, OK/not OK
Limit Constants Upper and lower limits for the above permissive
Breaker Performance Diagnostics: Slow check relay
Sync relay lockup
Breaker #1 close time out of limits
Breaker #2 close time out of limits
Relay K25P trouble
Breaker closing voltage (125 V dc) missing
Control Pushbuttons Sync monitor: ON, OFF
Speed adjust: RAISE, LOWER
Voltage adjust:RAISE, LOWER
Specifications
Item Specification
Number of inputs 4 passive speed pickups
1 shaft voltage and 1 current measurement
1 generator and 1 bus voltage
Generator breaker status
8 flame detectors from first TRPG
Number of outputs Synch permissive and Auto synch relays.
Primary trip solenoid interface, 3 outputs to TRPx
Additional 3 trip outputs from second TRPx using VTURH2
MPU pulse rate range 2 Hz to 20 kHz
MPU pulse rate accuracy 0.05% of reading
MPU input circuit sensitivity 27 mV pk (detects 2 rpm speed)
Shaft voltage monitor Signal is frequency of ±5 V dc (0 – 1 MHz) pulses from 0 to 2,000 Hz
Shaft voltage wiring Up to 300 m (984 ft), with maximum two-way cable resistance of 15 Ω
Shaft voltage dc test Applies a 5 V dc source to test integrity of the external turbine circuit and measures dc
current flow. Circuit computes a differential resistance between 0 and 150 Ω within ±5 Ω
and compares against shunt limit and brush limit. Readings above 50 Ω indicate a fault.
Return signal is filtered to provide 40 dB of noise attenuation at 60 Hz.
Shaft voltage ac test Applies a test voltage of 1 kHz to the input of the VTUR shaft voltage circuit (R module
only). Shaft voltage monitor circuit on R, S, and T displays an offset of 1000 Hz from normal
reading.
Shaft current input Measures shaft current in amps ac (shunt voltage up to 0.1 V pp)
Generator and bus voltage Two single phase potential transformers, with secondary output supplying a nominal 115 V
sensors rms
Each input has less than 3 VA of loading
Allowable voltage range for synch is 75 to 130 V rms
Each PT input is magnetically isolated with a 1,500 V rms barrier
Cable length can be up to 1,000 ft. of 18 AWG wiring
399
Item Specification
Synchronizing Frequency accuracy 0.05% over 45 to 66 Hz range
measurements Zero crossing of the inputs is monitored on the rising slope
Phase difference measurement is better than ±1 degree
Contact voltage sensing 20 V dc indicates high and 6 V dc indicates low
Each circuit is optically isolated and filtered for 4 ms
Trip solenoids 6 per VTURH2 (3 per TRPx terminal board)
3 per VTURH1
Flame detectors 8 per VTUR
Diagnostics
Three LEDs at the top of the VTUR front panel provide status information. The
normal RUN condition is a flashing green, FAIL is a solid red. The third LED is
STATUS and is normally off but shows a steady orange if a diagnostic alarm
condition exists in the board. VTUR makes diagnostic checks including:
• If feedback from the solenoid relay drivers differs with the control signal a fault
is created
• If feedback from the relay contacts differs with the control signal a fault is
created
• Loss of solenoid power creates a fault
• High and low flame detector voltage creates a fault
• Slow synch check relay, slow auto synch relay, and locked up K25 relay; all of
these condition creates a fault
L3DIAG_VTUR occurs. The diagnostic signals can be individually latched and
then reset with the RESET_DIA signal if they go healthy
• Terminal board connectors JR1, JS1, JT1, JR5, JS5, JT5 have their own ID
device that is interrogated by the I/O board. The ID device is a read-only chip
coded with the terminal board serial number, board type, revision number, and
plug location. When the chip is read by VTUR and a mismatch is encountered, a
hardware incompatibility fault is created
Configuration

Configuration
VTUR system limits Select system limits Enable, disable
SMredundancy Select Simplex or TMR system Simplex or TMR
AccelCalType Select acceleration calculation type Slow, medium, fast
FastTripType Select Fast Trip algorithm Unused, PR_Single, PR_Max
J3J5:IS200TTURH1A TTUR connected to VTUR through J3 and J5 Connected, not connected
PulseRate1 Pulse rate input 1 - board point Point edit (input FLOAT)
PRType Select Speed or Flow type input Unused, speed, flow, Speed_LM
PRScale Select pulses per revolution 0 to 1,000
SysLim1Enable Select system limit 1 Enable, disable
GEH-6421M
SysLimit1 Select alarm level in GPM or RPM 0 to 20,000
SysLim2Enable Select system limit 2 (as above) Enable, disable
TMRDiffLimit Difference limit for voted PR inputs EU 0 to 20,000
ShVoltMon Shaft voltage monitor - board point Point edit (input FLOAT)
SysLim1Enable Select System Limit 1 Enable, disable
SysLimit1 Select alarm level in frequency 0 to 100
SysLim2Enable Select system limit 2 (as above) Enable, disable
ShCurrMon Shaft current monitor - board point Point edit (input FLOAT)
ShuntOhms Shunt resistance 0 to 100
Shunt limit Shunt maximum ohms 0 to 100
Brush limit Shaft brush maximum ohms 0 to 100
SysLimit1 Select alarm level in amps 0 to 100
GenPT_KVolts Generator potential transformer - board point Point edit (input FLOAT)
PT_Input PT input in kVrms for PT output 0 to 1,000
PT_Output PT output in Vrms, nominal 115 V rms 0 to 150
SysLim1 Select alarm level in kVrms 0 to 1,000
SysLim2 Select alarm level in kVrms 0 to 1,000
BusPT_Kvolts Bus potential transformer - board point Point edit (input FLOAT)
Ckt_Bkr Circuit breaker - board point Point edit (input BIT)
System Frequency Select frequency in Hz 50 or 60
CB1CloseTime Breaker 1 closing time, ms 0 to 1,000
CB1 AdaptLimit Breaker 1 self adaptive limit, ms 0 to 1,000
CB1 AdaptEnabl Select breaker 1 self adaptive limit Enable, disable
CB1FreqDiff Breaker 1 special window frequency 0 to 10
difference, Hz
CB1PhaseDiff Breaker 1 special window phase difference, 0 to 30
degrees
CB2CloseTime Breaker 2 closing time, ms (as above) 0 to 1,000
J4:IS200TRPGH1A TRPG terminal board, 8 flame detectors Connected, not connected
Description - Point Edit

Board Points Signals (Enter Signal Connection) Direction Type
L3DIAG_VTUR1 Board diagnostic Input BIT
ShShntTst_OK Shaft voltage monitor shunt test OK Input BIT
ShBrshTst_OK Shaft voltage brush test OK Input BIT
CB_Volts_OK L3BKR_VLT circuit breaker coil voltage available Input BIT
CB_K25P_PU L3BKR_PERM sync permissive relay picked up Input BIT
CB_K25_PU L3KBR_GES auto sync relay picked up Input BIT
CB_K25A_PU L3KBR_GEX sync check relay picked up Input BIT
401
Description - Point Edit
Board Points Signals (Enter Signal Connection) Direction Type
Gen_Sync_LO Generator sync trouble (lockout) Input BIT
L25_Command -------- Input BIT
Kq1_Status -------- Input BIT
: : Input BIT
Kq6_Status -------- Input BIT
FD1_Flame -------- Input BIT
: : Input BIT
FD16_Flame -------- Input BIT
SysLim1PR1 -------- Input BIT
: : Input BIT
SysLim1PR4 -------- Input BIT
SysLim1SHV Ac shaft voltage frequency high L30TSVH Input BIT
SysLim1SHC Ac shaft current high L30TSCH Input BIT
SysLim1GEN -------- Input BIT
SysLim1BUS -------- Input BIT
SysLim2PR1 (same set as for Limit1 above) Input BIT
GenFreq Hz frequency Input FLOAT
BusFreq Hz frequency Input FLOAT
GenVoltsDiff KiloVolts rms-Gen Low is negative Input FLOAT
Gen Freq Diff Slip Hz-Gen Slow is negative Input FLOAT
Gen Phase Diff Phase Degrees-Gen Lag is negative Input FLOAT
CB1CloseTime Breaker #1 close time in milliseconds Input FLOAT
CB2CloseTime Breaker #2 close time in milliseconds Input FLOAT
Accel1 RPM/SEC Input FLOAT
: : Input FLOAT
Accel4 RPM/SEC Input FLOAT
FlmDetPwr1 335 V dc Input FLOAT
ShTestAC L97SHAFT_AC SVM_AC_TEST Output BIT
ShTestDC L97SHAFT_DC SVM_DC_TEST Output BIT
FD1_Level 1 = high detection counts level Output BIT
: : Output BIT
FD16_Level 1 = high detection counts level Output BIT
Sync_Perm_AS L83AS - auto sync permissive Output BIT
Sync_Perm L25P - sequencing sync permissive Output BIT
Sync_Monitor L83S_MTR - monitor mode Output BIT
Sync_Bypass1 L25_BYP-1 = auto aync bypass Output BIT
Sync_Bypass0 L25_BYPZ-0 = auto sync permissive Output BIT
CB2_Selected L43SAUT2 - 2nd breaker selected Output BIT
AS_Win_Sel L43AS_WIN - special window selected Output BIT
Sync_Reset L86MR_SYNC - sync trouble reset Output BIT
Kq1 L20PTR1 - primary trip relay Output BIT
: : Output BIT
Kq6 L20PTR6 - primary trip relay Output BIT
GEH-6421M
Alarms
2 Flash Memory CRC Failure Board firmware programming error (board will not go online)
3 CRC failure override is Active Board firmware programming error (board is allowed to go
online)
16 System Limit Checking is Disabled System checking was disabled by configuration
30 ConfigCompatCode mismatch; Firmware: [ ]; A tre file has been installed that is incompatible with the
Tre:[ ] The configuration compatibility code firmware on the I/O board. Either the tre file or firmware must
that the firmware is expecting is different than change. Contact the factory.
what is in the tre file for this board
31 IOCompatCode mismatch; Firmware: [ ]; Tre:[ A tre file has been installed that is incompatible with the
] The I/O compatibility code that the firmware firmware on the I/O board. Either the tre file or firmware must
is expecting is different than what is in the tre change. Contact the factory.
file for this board
32-37 Solenoid [ ] Relay Driver Feedback Incorrect. The solenoid relay driver on the TRPG/L/S board has failed, or
Solenoid (1-6) relay driver feedback is the cabling between VTUR and TRPG/L/S is incorrect.
incorrect as compared to the command;
VTUR cannot drive the relay correctly until the
hardware failure is corrected
38-43 Solenoid [ ] Contact Feedback Incorrect. The solenoid relay driver or the solenoid relay on the
Solenoid (1-6) relay contact feedback is TRPG/L/S board has failed, or the cabling between VTUR and
incorrect as compared to the command; TRPG/L/S is incorrect.
VTUR cannot drive the relay correctly until the
hardware failure is corrected
44-45 TRPG [ ] Solenoid Power Absent. P125/24 V Power may not be coming into TRPG/L/S on the J1 connector,
dc power is not present on TRPG terminal or the monitoring circuit on TRPG/L/S is bad, or the cabling
board; VTUR cannot energize trip solenoids 1 between TRPG/L/S and VTUR is at fault.
through 3, or 4 through 6 until power is
present
46,48 TRPG [ ] Flame Detector Volts Low at Y Volts. Power comes into TRPG through J3, J4, and J5. If the voltage
TRPG 1 or 2 flame detect voltage is low; the is less than 314.9 V dc, this should be investigated. If the
ability to detect flame by detectors 1 through voltage is above this value, the monitoring circuitry on TRPG or
8, or 9 through 16 is questionable the cabling between TRPG and VTUR is suspect.
47,49 TRPG [ ] Flame Detector Volts High at Y This power comes into TRPG through J3, J4, and J5. If the
Volts. TRPG 1 or 2 flame detect voltage is voltage is greater than 355.1 V dc, this should be investigated.
high; the ability to detect flame by detectors 1 If the voltage is below this value, the monitoring circuitry on
through 8, or 9 through 16 is questionable TRPG or the cabling between TRPG and VTUR is suspect.
because the excitation voltage is too high and
the devices may be damaged
50 L3BKRGXS – Synch Check Relay is Slow. The synch check relay I3BKRGXS, known as K25A, on
The auto synchronization algorithm has TTUR is suspect; also the cabling between VTUR and TTUR
detected that during synchronization with no may be at fault.
dead bus closure (synch bypass was false)
the auto synch relay I3BKRGES closed before
synch relay I3BKRGEX closed
403
51 L3BKRGES – Auto Synch Relay is Slow. The The Auto synch relay I3BKRGES also known as K25, on
auto synchronization algorithm has detected TTUR is suspect; also the cabling between VTUR and TTUR
that the auto synch relay I3BKRGES had not may be at fault.
closed by two cycle times after the command
I25 was given
52-53 Breaker [ ] Slower than Adjustment Limit The breaker is experiencing a problem, or the operator should
Allows. Breaker 1 or 2 close time was consider changing the configuration (both nominal close time
measured to be slower than the auto synch and self-adaptive limit in ms can be configured).
algorithms adaptive close time adjustment
limit allows
54 Synchronization Trouble - K25 Relay Locked K25 on TTUR is most likely stuck closed, or the contacts are
Up. The auto synchronization algorithm has welded.
determined that the auto synch relay
I3BKRGES, also known as K25, is locked up.
Auto synch will not be possible until the relay
is replaced
55 Card and Configuration File Incompatibility. Install the correct TRE file from the factory
You are attempting to install a VTUR board
that is not compatible with the VTUR TRE file
you have installed
56 Terminal Board on J5X and Config File Check your configuration.
Incompatibility. VTUR detects that the terminal
board that is connected to it through J5 is
different than the board that is configured
57 Terminal Board on J3 and Config File Check your configuration.
58 Terminal Board on J4 and Config File Check your configuration.
59 Terminal Board on J4A and Config File Check your configuration.
board that is connected to it through J4A is
60 Terminal Board TTUR and card The TTUR or VTUR must be changed to a compatible
VTUR Incompatibility. VTUR detects that the combination.
TTUR connected to it is an incompatible
hardware revision
61 TRPL or TRPS Solenoid Power Bus "A" Cabling problem or solenoid power source
Absent
62 TRPL or TRPS Solenoid Power Bus "B" Cabling problem or solenoid power source
Absent
63 TRPL or TRPS Solenoid Power Bus "C" Cabling problem or solenoid power source
Absent
64-66 TRPL/S J4 Solenoid [ ] Voltage mismatch. PTR or ETR relays, or defective feedback circuitry
The voltage feedback disagrees with the PTR
or ETR feedback
128- 223 Logic Signal [ ] Voting mismatch. The A problem with the input. This could be the device, the wire to
identified signal from this board disagrees with the terminal board, the terminal board, or the cable.
the voted value
224- 251 Input Signal [ ] Voting mismatch, Local [ ], A problem with the input. This could be the device, the wire to
Voted the terminal board, the terminal board, or the cable.
[ ]. The specified input signal varies from the
voted value of the signal by more than the
TMR Diff Limit
GEH-6421M
TTURH1B Primary Turbine Protection Input
The Primary Turbine Protection Input (TTURH1B) terminal board works with
VTUR and has the following inputs and outputs:
• Twelve passive pulse rate devices sensing a toothed wheel to measure the
turbine speed
• Generator voltage and bus voltage signals from potential transformers
• 125 V dc output to the main breaker coil for automatic generator synchronizing
• Inputs from the shaft voltage and current sensors to measure induced shaft
voltage and current
TTUR has three relays, K25, K25P, and K25A, that all have to close to provide 125
V dc power to close the main breaker, 52G. The speed signal cable to VTUR uses
the JR5 connector, and the other signals use the JR1 connector. For TMR systems,
signals fan out to the JR5, JS5, JT5, JR1, JS1, and JT1 connectors.
Mark VI Systems
In the Mark* VI system, the TTUR works with the VTUR processor and supports
simplex and TMR applications. In TMR systems, TTURH1B connects to three
VTUR boards.
Note TTURH1B does not support I/O packs, see Mark VIe below.
Mark VIe Systems
For the Mark VIe system, a new design board, the TTURH1C, is used.
Note This document does not describe TTURH1C. For details, refer to GEI-100575
PTUR Turbine Specific Primary Trip.
405
TTURH1B Terminal Board VTUR VME Board
Breakers
x
Generator volts x 37-pin "D" shell
x
Bus volts x 1 JT1 type connectors
x 2 RUN
Shaft volts x 4
x 3 with latching FAIL
x 6
x 5 fasteners STAT
Shaft current x 7
x 8
x 10
x 9
x 12
x 11
x 14
x 13
x 16
x 15
x 18
x 17 Cables to VME
x 20
x 19 JT5 JS1 rack T
x 22
x 21
24
x 23
x VME bus to VCMI
x
x
Magnetic x 25 JS5
x 26
speed x 28
x 27 Cables to VME
30
x 29 rack S J
pickups (12) x
x 31
x 32 JR1 5
x 34
x 33
x 36
x 35
x 38
x 37 JR5
x 40
x 39 VTUR
x 42
x 41 x
x 44
x 43
46
x 45
x
x 47 J3
x 48
x
TB3 x
Wiring to
Shield bar TTL speed Connectors on
pickups VME rack R J4
Cables to VME
Barrier type terminal rack R
Cable to TRPG
TTUR Turbine Terminal Board, Processor Board, and Cabling
Installation
Connect the wires for the magnetic pick ups, shaft pick ups, potential transformers,
and breaker relays to the two I/O terminal blocks TB1 and TB2, as shown in the
figure, TTUR Terminal Board Wiring. Each block is held down with two screws and
has 24 terminals accepting up to #12 AWG wires. A shield termination strip attached
to chassis ground is located immediately to the left of each terminal block.
Use jumpers JP1 and JP2 to select either SMX or TMR for relay drivers K25 and
K25P. If used, connect the wires for optional TTL active speed pick ups to TB3;
these require an external power supply.
GEH-6421M
Simplex systems use cable connectors JR5 and JR1. TMR systems use all six cable
connectors.
Turbine Terminal Board TTURH1B

JP1 JP2
K1
TB1
x
TMR SMX TMR SMX
x 1 52G (H)
52G (L) x 2
x 3 P125GEN
AUTO x 4 K3
BKRH x 6
x 5 MAN
N125GEN x 8
x 7 BKRH
x 9
x 10
x 11
x 12 K2
x 13
x 14
x 15
x 16
x 17 Gen (H)
Gen (L) x 18
Bus (L)
x 19 Bus (H)
x 20
ShaftV (L) x 22
x 21 ShaftV (H)
x 23 ShaftC (H)
ShaftC (L) x 24
x
To connectors JR5,
JS5, JT5, JR1, JS1, JT1
TB2
TB3 Screw Connections
x
x 25 MPU 1T (H) TTL1T 01
MPU 1T (L) x 26
x 27 MPU 2T (H) TTL2T 02
MPU 2T (L) x 28
MPU 3T (L) x 30
x 29 MPU 3T (H)
MPU 4T (L) x 32
x 31 MPU 4T (H)
x 33 MPU 1S (H) TTL1S 03
MPU 1S (L) x 34
x 35 MPU 2S (H) TTL2S 04
MPU 2S (L) x 36
MPU 3S (L) x 38
x 37 MPU 3S (H)
x 39 MPU 4S (H) 01
MPU 4S (L) x 40
MPU 1R (L) x 42
x 41 MPU 1R (H) TTL1R 05
x 43 MPU 2R (H) TTL2R 06 J8 x
MPU 2R (L) x 44
MPU 3R (L) x 46
x 45 MPU 3R (H)
x 47 MPU 4R (H)
MPU 4R (L) x 48
x
TB3
TTUR Terminal Board Wiring
407
Operation
In simplex applications, up to four pulse rate signals can be used to measure turbine
speed. Generator and bus voltages are brought into TTUR for automatic
synchronizing in conjunction with VTUR, the turbine controller, and excitation
system. TTUR has permissive generator synchronizing relays and controls the main
breaker relay coil, 52G.
TTURH1B Terminal Board <R> Control Generator Breaker 52G

(input portion) Rack feedback
a
JR1 J3 Turbine
Gen. GENH
17 suppression 02 01
Board Terminal Board TTURH1B
volts
VTUR (continued)
120 V ac NS
from PT GENL 18 28Vdc
Pulse
Rate J3 JR1 TMR JP1
SMX
MUX K25P
Bus BUSH 19 ID A/D RD Synch. Perm.
volts
120 Vac NS Ac&Dc Mon
20 Shaft
from PT BUSL TMR
test SMX
JP2
To K25
TPRO Trip RD Auto Synch
solenoids
SVH 21 Mon
Flame
175V NS sensors K25A
SVL 22 Synch. check
from VPRO
Shaft J5
23 Mon
SCH J4
14V NS
SCL 24
J8 08 06,7 05 04 03
Connectors
5 (TB3)
Machine case TTL1_R
JR5 at bottom of
VME rack B M A
)
MPU1RH 41 K A U
#1 Primary Filter
Magnetic NS Clamp Trip R N T
MPU1RL 42 AC
signals O
Speed PU Coupling H
6 (TB3) to
TTL2_R
TRPG P125Gen
)
MPU2RH 43 Filter
#2 Primary
Clamp Note 1: TTL option only
Magnetic
44 NS AC ID
Speed PU MPU2RL
Coupling
available on first two
Speed pickups. 52G
45 Note 2: An external normally
#3 Primary Filter b
Clamp
Magnetic
46 NS AC closed auxiliary breaker
Speed PU Coupling
contact must be provided in
Breaker coil
47 the breaker close coil circuit
#4 Primary Filter
Magnetic Clamp as indicated.
48 NS AC N125Gen
Speed PU Coupling Note 3: Signal to K25A
comes from TREG/VPRO
TTUR Control I/O and VTUR Board, Simplex
GEH-6421M
In TMR applications all inputs fan to the three control racks. Control signals coming
into TTUR from R, S, and T are voted before they actuate permissive relays K25 and
K25P. Relay K25A is controlled by the VPRO and TREG boards.
Note All three relays have two normally open contacts in series with the breaker
close coil.
52G
a
<T> Generator Breaker
<S> Feedback
Terminal Board TTURH1B <R>
(input portion) Turbine Terminal Board TTURH1B 02 01
B52GH
B52GL
Board (continued)
Noise JR1 J3 VTUR
17 Suppression
GENH
J3 JR1
Gen. Volts 28Vdc
NS f( )
120 Vac
18 JP1
from PT GENL Pulse TMR
Rate/ SMX
Digital K25P
2 RD Synch.
BUSH 19 MUX
JS1 3 Permissve
Bus Volts J3 JS1
A/D
120 Vac NS JP2 TMR
BUSL 20
from PT AC&DC SMX
shaft K25
To 2
test RD Auto Synch.
TPRO 3
Trip J3 JT1
SVH 21 solenoids
JT1
175V NS Flame K25A
SVL 22
sensors Synch. check
from VPRO
J4
Shaft J5
SCH 23 Mon
14V Connectors
NS at bottom of
SCL 24
VME rack
5 (TB3) J8 08 07 06 05 04 03
Machine Case TTL1R JR5
)
MPU1RH 41
#1 Primary BKRH
MAN
Filter
AUTO
Magnetic Clamp Trip
NS AC
Speed PU MPU1RL 42 Coupling
Signals to
4 Circuits* TRPG
3 (TB3) P125Gen
TTL1S JS5 Note 1: TTL option only
)
MPU1SH 33 available on first two circuits.

#2 Primary Filter
of each group of 4 pickups*. 52G
Clamp
Magnetic NS AC
b
Speed PU MPU1SL 34 Coupling Note 2: An external normally
4 Circuits*
1 (TB3)
closed auxiliary breaker
Bkr Coil
TTL1T JT5 contact must be provided in
25
To Rack S
)
MPU1TH the Breaker close coil circuit

#3 Primary Filter
as indicated.
Clamp
Magnetic NS AC N125Gen
26
Speed PU MPU1TL Coupling
Note 3: Signal to K25A
4 Circuits* comes from TREG/VPRO
To Rack T
TTUR Control I/O and VTUR Board, TMR
409
Specifications
Item Specification
Number of inputs 12 passive speed pickups.
1 shaft voltage and 1 shaft current measurement.
1 generator and 1 bus voltage.
Generator breaker status contact.
Signal to K25A relay.
Number of outputs Generator breaker coil, 5 A at 125 V dc
Power supply voltage Nominal 125 V dc to breaker coil
MPU pulse rate range 2 Hz to 20 kHz
MPU pulse rate accuracy 0.05% of reading
MPU input circuit sensitivity 27 mV pk (detects 2 rpm speed)
Shaft voltage monitor Signal is frequency of ± 5 V dc (0 – 1 MHz) pulses from 0 to 2,000 Hz
Shaft voltage wiring Up to 300 m (984 ft), with maximum two-way cable resistance of 15 Ω
Shaft voltage dc test Applies a 5 V dc source to test integrity of the external turbine circuit and measures dc
current flow.
Shaft voltage ac test Applies a test voltage of 1 kHz to the input of the VTUR shaft voltage circuit (R module
only).
Shaft current input Measures shaft current in amps ac (shunt voltage up to 0.1 V pp)
Generator and bus voltage Two single phase potential transformers, with secondary output supplying a nominal 115 V
sensors rms
Each input has less than 3 VA of loading
Allowable voltage range for synch is 75 to 130 V rms
Each PT input is magnetically isolated with a 1,500 V rms barrier
Cable length can be up to 1,000 ft. of 18 AWG wiring
Generator breaker circuits External circuits should have a voltage range within 20 to 140 V dc. The external circuit
(synchronizing) must include a NC breaker auxiliary contact to interrupt the current
Circuits are rated for NEMA class E creepage and clearance
250 V dc applications require interposing relays
Contact voltage sensing 20 V dc indicates high and 6 V dc indicates low
Each circuit is optically isolated and filtered for 4 ms
Technology Surface mount
Temperature Operating: -30 to 65ºC (-22 to 149 ºF)
GEH-6421M
Diagnostics
VTUR makes diagnostic tests on the terminal board and connections as follows:
• Feedback from the solenoid relay drivers; if they do not agree with the control
signal a fault is created.
• Feedback from the relay contacts; if they do not agree with the control signal a
fault is created.
• Loss of solenoid power, which creates a fault.
• Slow synch check relay, slow auto synch relay, and locked up K25 relay; all of
these create a fault.
L3DIAG_VTUR occurs. The diagnostic signals can be individually latched and
then reset with the RESET_DIA signal if they go healthy.
• Terminal board connectors JR1, JS1, JT1, JR5, JS5, JT5 have their own ID
device that is interrogated by the I/O board. The ID device is a read-only chip
coded with the terminal board serial number, board type, revision number, and
plug location. When the chip is read by VTUR and a mismatch is encountered, a
Configuration
Jumpers JP1 and JP2 select either simplex or TMR for relay drivers K25 and K25P.
There are no switches on the board.
411
TRPG Turbine Primary Trip
The Gas Turbine Primary Trip (TRPG) terminal board is controlled by the Primary
Turbine Protection controller (VTUR or PTUR). TRPG contains nine magnetic
relays in three voting circuits to interface with three trip solenoids (ETDs). The
TRPG works in conjunction with the TREG to form the primary and emergency
sides of the interface to the ETDs. TRPG also accommodates inputs from eight
®
Geiger-Mueller flame detectors for gas turbine applications. There are two board
types as follows:
• The H1A and H1B version for TMR applications has three voting relays per trip
solenoid.
• The H2A and H2B version for simplex applications has one relay per trip
solenoid.
Mark VI System
In the Mark* VI system, the TRPG works with the VTUR board and supports
simplex and TMR applications. Cables with molded plugs connect TRPG to the
VME rack where the VTUR board is located.
Mark VIe System
In the Mark VIe system, the TRPG is controlled by the PTUR packs on TTURH1C
and supports simplex and TMR applications. The I/O packs plug into the D-type
connectors on TTURH1C, which is cabled to TRPG.
Version Difference
Output contact, Output contact, 28 V Power
Board TMR Simplex 125 V dc, 1 A 24 V dc, 3 A use
TRPGH1A* Yes No Yes No Normal
TRPGH2A* No Yes Yes No Normal
TRPGH1B Yes No Yes Yes Normal
TRPGH2B No Yes Yes Yes Normal
TRPGH3B Yes No Yes Yes Special
* H1A and H2A are not used for new applications. TRPGH3B features special
handling of 28 V control power and is otherwise identical to a TRPGH1B. Consult
factory for additional details.
GEH-6421M
ETD power
x DC-37 pin type

x
x 1 JT1 connectors
x 2 J1
x 4
x 3 with latching
Trip solenoids x 5
Power monitoring x 6 fasteners
x 8
x 7
x 10
x 9
x 12
x 11
x 14
x 13
x 16
x 15
x 18
x 17
x 20
x 19 JS1 J - Port Connections:
x 22
x 21
x 24
x 23
Cables to TTURH1C
x
for Mark VIe system
x or
x 26
x 25
28
x 27
x Cables to VTURboards
x 30
x 29
Flame sensor x 31 for Mark VI system
x 32
signals (8) x 33 JR1
x 34
x 36
x 35
x 38
x 37
x 40
x 39
x 42
x 41 J2
x 44
x 43
x 45 J4
x 46 J5
x 48
x 47
x
J3
x
Shield bar
335 V from rack

power supplies
Cable to
R, S, T
TREG
TRPG Terminal Board and Cabling
413
Installation
Connect the wires for the three trip solenoids directly to the first I/O terminal block.
Connect the wires for the flame detectors (if used) to the second terminal block.
Connect the power for the flame detectors to the J3, J4, and J5 plug.
Connect the 125 V dc power for the trip solenoids to the J1 plug. Transfer power to
the TREG board using the J2 plug.
Turbine Primary Trip Terminal Board TRPG

125 V dc
J1
JT1
x
x 1 125 Vdc (P)
Trip Solenoid 1 or 4 x 2
x 3 125 Vdc (P)
Trip Solenoid 2 or 5 x 4
6
x 5 125 Vdc (P)
Trip Solenoid 3 or 6 x
x 7
x 8
125 Vdc (N) x 10
x 9 125 Vdc (N)
x 12
x 14
x 13 JS1
x 16
x 15 Cables to TTURH1C
x 18
x 17 for Mark VIe system
x 19
x 20
x 21 or
x 22
x 23
x 24
Cables to control rack VTUR boards
x
for Mark VI system
JR1
x
x 25
x 26
x 27
x 28
x 30
x 29 J2
x 31
x 32
Flame 1 (L) x 33 Flame 1 (H)
x 34
Flame 2 (L) x 36
x 35 Flame 2 (H) Cable to TREG
x 37 Flame 3 (H)
Flame 3 (L) x 38
x 39 Flame 4 (H)
Flame 4 (L) x 40 335 V dc
Flame 5 (L) x 42
x 41 Flame 5 (H) J4
Flame 6 (L)
x 43 Flame 6 (H)
x 44 335 V dc
x 45 Flame 7 (H) J5
Flame 7 (L) x 46
x 47 Flame 8 (H) 335 V dc
Flame 8 (L) x 48 J3
x

point with 300 V insulation from terminal board for maintenance
TRPG Terminal Board Wiring
GEH-6421M
Operation
The I/O pack/board provides the primary trip function by controlling the relays on
TRPG, which trip the main protection solenoids. In TMR applications, the three
inputs are voted in hardware using a relay ladder logic two-out-of-three voting
circuit. The I/O pack/board monitors the current flow in its relay driver control line
to determine its energize or de-energize vote/status of the relay coil contact status.
Supply voltages are monitored for diagnostic purposes. A normally closed contact
from each relay on TRPG is monitored by the diagnostics to determine its proper
operation.
PDM 125 V dc + - Monitoring outputs

Terminal Board TRPG J1 01 03 05 09 10
H1A (TMR), H2A (Simplex) P125 Terminal
Trip Board TREG
JR1 N125 Solenoid
From R "PTR 1/4"
RD KR1 KR1 KS1 1 or 4 KE1
02 - + 01
RD KR2 KS1 KT1

ID J2 J2
RD KR3 Mon
KT1 KR1 04
28 Vdc
Optional 03
Mon economizing Trip
"PTR 2/5" resistor Solenoid
KR1,2,3
KR2 KS2 04 2 or 5 05 KE2
- +
These relays in TMR systems
From S JS1 KS2 KT2 J2 J2
RD KS1
Mon
KT2 KR2 08
RD KS2
ID 07
RD KS3
Trip
28 Vdc "PTR 3/6" Solenoid
KR3 KS3 3 or 6 KE3
Mon 06 - + 09
KS1,2,3 KS3 KT3 J2 J2

JT1 Mon
From T
RD KT1 KT3 KR3 12
11
RD KT2
ID To JR1, 02
RD KT3 JS1, JT1 06
Solenoid
28 Vdc Power Monitor 10
Mon J2 J2
N125 Vdc -
KT1,2,3 +
8 signals to 3 monitor
JR1 ,JS1,JT1 signals to J3
JR1,JS1,JT1 Voltage Supply
and Monitor 335 V dc from R
FLAME1H 33 NS 335 V dc Voltage Supply
J4
34 and Monitor 335 V dc from S
NS J5
FLAME1L Voltage Supply
Supply 8 and Monitor 335 V dc from T
Eight flame detectors
detector circuits
TRPG and Connections to Controller and Trip Solenoids
415
Note A metal oxide varister (MOV) and a current limiting resistor are used in each
ETD circuit
The primary overspeed trip comes from the controller and is passed to the I/O
pack/board, and then to TRPG. TRPG works in conjunction with the TREG board,
which is controlled by the emergency overspeed system. This TRPG/TREG
combination can drive three ETDs.
Flame Detectors
®
The primary protection system monitors signals from eight Geiger-Mueller flame
detectors. With no flame present, the detector charges up to the supply voltage. The
presence of flame causes the detector to charge to a level and then discharge through
TRPG. As the flame intensity increases, the discharge frequency increases. When the
detector discharges, the I/O pack/board and TRPG convert the discharged energy
into a voltage pulse. The pulse rate varies from 0 to 1,000 pulses/sec. These voltage
pulses are fanned out to all three modules. Voltage pulses above 2.5 volts generate a
logic high, and the pulse rate over a 40 ms time period is measured in a counter.
Specifications
Item Specification
Trip solenoids 3 solenoids per TRPG
Solenoid rated voltage/current 125 V dc standard with up to 1 A draw
24 V dc is alternate with up to 1 A draw (H1B, H2B, H3B)
Solenoid response time L/R time constant is 0.1 sec
Current suppression MOV on TREG
Current economizer Terminals for optional 10 Ω, 70 W economizing resistor on TREG
Control relay coil voltage supply Relays are supplied with 28 V dc from JR1, JS1, and JT1
Flame detectors 8 detectors per TRPG
Flame detector supply voltage/current 335 V dc with 0.5 mA per detector
Diagnostics
The I/O board runs the TRPG diagnostics. These include feedback from the trip
solenoid relay driver and contact, solenoid power bus, and the flame detector
excitation voltage too low or too high. A diagnostic alarm is created if any one of the
signals go unhealthy (beyond limits). Connectors JR1, JS1, and JT1 on the terminal
board have their own ID device, which is interrogated by the I/O board, and if a
mismatch is encountered, a hardware incompatibility fault is created. The ID device
is a read-only chip coded with the terminal board serial number, board type, revision
number, and the plug location.
Configuration
GEH-6421M
VVIB Vibration Monitor Board
VVIB Vibration Monitor
The Vibration Monitor (VVIB) board processes vibration probe signals from the
TVIB or DVIB terminal board. Up to 14 probes connect directly to the terminal
board. Two TVIB can be cabled to the VVIB processor board. VVIB digitizes the
various vibration signals, and sends them over the VME bus to the controller. The
Mark* VI system uses Bently Nevada* probes for shaft vibration monitoring. The
following vibration probes are compatible:
• Proximity
• Velocity
• Acceleration
• Seismic
• Phase
Note If desired, a Bently Nevada 3500 monitoring system can be connected to

the terminal board.
Vibration probes are normally used for four protective functions in turbine
applications as follows:
Vibration: Proximity probes monitor the peak-to-peak radial displacement of the

shaft (the shaft motion in the journal bearing) in two radial directions. This system
®
uses non-contacting probes and Proximitors , and detects alarms, trips, and faults.
Rotor Axial Position: A probe is mounted in a bracket assembly off the thrust
bearing casing to observe the motion of the thrust collar on the turbine rotor. This
system uses non-contacting probes and Proximitors, and detects thrust bearing wear
alarms, trips, and faults.
Differential Expansion: This application uses non-contacting probe(s) and

Proximitor(s) and detects alarms, trips, and faults for excessive expansion
differential between the rotor and the turbine casing.
Rotor Eccentricity: A probe is mounted adjacent to the shaft to continuously

sense the surface and update the turbine control. The calculation of eccentricity is
made once per revolution while the turbine is on turning gear. Alarm and fault
indications are provided.
There are two types of TVIB terminal boards, H1A and H2A. The H2A type board
has BNC connectors allowing portable vibration data gathering equipment to be
plugged in for predictive maintenance purposes. Both types have connectors so that
Bently Nevada vibration monitoring equipment can be permanently cabled to the
terminal board to measure and analyze turbine vibration.
417
Volume II VVIB Vibration Monitor Board • 451
TVIB Terminal Board VVIB VME Board
x
x
x 37-pin "D" shell
x 1 ...JA1
... JT1 type connectors
x 2 ...
. RUN
x 4 x 3 ... with latching FAIL
...
6 x 5 . STAT
x
x 7
...
... fasteners
Vibration x 8 .
...
x 10
x 9 ...
signals x 11
.
...
x 12 . JB1
...
x 14 x 13 ...
...
x 16 x 15 .
x 17
...
...
.
Cable to
x 18
x 20
x 19 ...
...
. JS1 rack T
x 22 x 21
24 x 23 JC1
x VME bus to VCMI
x
x
x 26 x 25
x 28
x 27 Cable to
x 29 JD1 rack S
Vibration x 30
x 32
x 31
signals x 33 JR1
x 34 P2 P1
x 36 x 35
x 38 x 37
x 40 x 39 P6 P5 P4 P3 VVIB
x 42 x 41 x
x 44
x 43
x 46 x 45 P10 P9 P8 P7 Connectors on J3
x 48
x 47
14 13 12 P11 VME rack R
x
x
Shield bar
Cables with inner and outer shields: Connect
inner shield to shield bar and leave the outer J4
Cable to VME
shield which is connected to the sensor case
rack R
open.
Plugs for Portable Bently-
Nevada data gathering & Cable from second TVIB
monitoring equipment
Cables to fixed Bently-
Nevada 3500 Vibration
Monitoring System
Vibration Processor Board, Terminal Board, and Cabling
Installation

its edge connectors
452 • VVIB Vibration Monitor Board 418 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Operation
®
The terminal board supports Proximitor, Seismic, Accelerometer, and Velomitor
probes of the type supplied by Bently Nevada. Power for the vibration probes comes
from the VVIB boards, in either simplex or TMR mode. The probe signals return to
VVIB where they are A/D converted and sent over the VME bus to the controller.
<R>
<S>
<T>
Vibration Board
Terminal Board TVIBH2A VVIB
JR1 J3
N28V 28 V dc
To
N28VR controller
<S>
<T> Amp A/D
Current
Limit ID Sampling
1 N24V1
S CL type A/D
P V 2 PR01H converter
S JS1 J3 (16 bit)
R s V 3mA
S N28V
O JP1A P,A
3 PR01L Same as
X S
Vib. or pos. PCOM <S>
Eight of the
prox. (P), or
above ccts. ID
seismic (S), P,V,A
or accel (A), TMR
or velomiter N28V
JT1
Applications
S J3
(V) N28V
CL JP1B
Negative Same as
25 N24V9 Volt Ref <T>
S
P 26 PR09H ID
R S
JA1
O 27 PR09L D
S
X B2
Four of the 5
above ccts. Buffer
Position Amplifiers
prox PCOM JB1 J4
D
B2
N28V 5
Buffer P1-P8 JC1 J4

CL Amplifiers D
B2
37 N24V13 5
S
P 38 PR13H
R S
O 39 PR13L P9-P12
S BNC JD1
X J4
Buffer Connectors D
Reference or Amplifiers B9
PCOM
keyphasor
prox. One of the above ccts for Mark VI
(Two of the above ccts for B/N
P13-P14
Four cables to Bently
Nevada 3500 system
VVIB Processor, Vibration Probes, and Bently Nevada Interface, TMR system
419
VVIB supplies -28 V dc to the terminal board for Proximitor power. In TMR
systems, a diode high-select circuit selects the highest -28 V dc bus for redundancy.
Regulators provide individual excitation sources, -23 to -26 V dc, short circuit
protected.
Probe inputs are sampled at high speeds up to 4600 samples per second over discrete
time periods. The maximum and minimum values are accumulated, the difference is
taken (max-min) for vibration, and the results are filtered. The resulting peak-to-peak
voltage is scaled to yield engineering units (EU) (peak-to-peak) displacement for
Proximitors inputs, EU (pk) for velocity inputs from accelerometers, integrated
outputs, seismics, and Velomitors.
Vibration Monitoring Firmware
The Vibration Monitoring on the VVIB in partitioned in the following manner:
Channels 1 – 3:
Channels 1 through 3 can be used for position information from Proximitors,

wideband vibration information from Proximitors, accelerometers with integrated
outputs, Velomitors, and Seismics. 1X and 2X information can be derived from
®
Proximitors viewing axial vibration information when a Keyphasor probe is used.
Tracking filters are normally used in LM applications with accelerometers.
Gapx_Vibx Vibration Filtering section runs the low-pass filter for the gap
calculation, the wideband vibration filter, and the maximum / minimum detect for
the peak-to-peak calculation at a 4.6 kHz rate and 2.3 kHz rate if input channels 14
through 21 are configured as vibration channels. The Gap Scaling and Limit Check
runs at the frame rate. This function converts the gap value from volts to the desired
EU. The system limit check provides two detection limits and Boolean outputs for
the status. The Vpp, Filter and Limit Check block runs every 160 ms. The peak-to-
peak calculation is based on the Vfmax and Vfmin values of the Gapx_Vibx
Wideband Vibration Filtering section. The wideband peak-to-peak signal is filtered
and then scaled to EU.
Note Vibx is expressed in EU (pk) for the configuration parameter, VibTypes:

accelerometers with integrated outputs, seismics, and Velomitors. Vibx is expressed
in EU(pk – pk) for Proximitors.
The re-scaled wideband signal is the input for the limit check function. The limit
check provides the Booleans, SysLim1VIBx, and SysLim2VIBx for the limit check
status.
Three tracking filters are provided to calculate the peak vibration for the LM
applications when accelerometers are used. The tracking filters provide the vibration
that occurs at the rotor speeds defined by the System outputs, LM_RPM_A,
LM_RPM_B, and/or LM_RPM_C. LMVib1A is the vibration detected on channel 1
based on the rotor speed, LM_RPM_A. LMVib1B is the vibration detected on
channel 1 based on rotor speed, LM_RPM_B. LMVib1C is based on LM_RPM_C.
The 1X and 2X filters provide the peak-to-peak vibration vector relative to the
Keyphasor input from channel 13. VIB1X1 is the peak-to-peak magnitude of the
vibration from channel 1 relative to the rpm based on the Keyphasor input.
Vib1xPH1 is the phase angle in degrees of the vibration vector from channel 1
relative to the Keyphasor input. VIB2X1 is the peak-to-peak magnitude of the
vibration from channel 1 relative to twice the Keyphasor rpm. Vib2xPH1 is the
phase angle in degrees of the 2X vibration vector from channel 1.
GEH-6421M
Channels 4 – 8:
Channels 4 through 8 can be used for position information from Proximitors,

wideband vibration information from Proximitors, Velomitors, and Seismics. 1X and
2X information can be derived from Proximitors viewing axial vibration information
when a Keyphasor probe is used. Channels 4 through 8 are identical to channels 1
through 3 with the exception of the Tracking filters. Channels 4-8 do not include the
Tracking filters.
Terminal
Board Pts
ScaleOff
PRO01/14H Diff Amp,
Vgap GAP1/14_VIB1/9
MUX & A/D
PRO01/14L SysLimit2 *
VIB_Scale SysLim2GAP1/14
Limit Chk
A/D GAIN & SysLim1GAP1/14
SysLimit1 *
OFFSET Gap Scaling & Limit Check
COMP. (Exec Rate = Frame Rate = 25, 50 or 100 hz)
VOLTS LOW PASS * Additional SysLimit Config. Parm.

----------- FILTER SysLim1Enable (En or Dis)
COUNT (8 Hz) SysLim1Latch (Latch or Not Latch)
SysLim1Type (>= or <=)
ScaleOff
Vib1/9
V_wb VIBScale SysLimit2 *
SysLim2VIB1/9
Limit Chk
Mag. (db) LP Filter
SysLim1VIB1/9
0 (1-pole) SysLimit1 *
-3
Vib_PP_Fltr (Hz)
Vmax
Wideband Vibration Filtering
and Vfmax
Peak Detection +
Vfpp
- CLAMP
Vfmin
FilterType
Fltrhpcutoff Fltrhpattn
Fltrlpcutoff Fltrlpattn Vmin
Filtering Vpp, Filter & Limit Check

(Exec. Rate = 4.6khz for <= 8 chs. & 2.3khz for > 8 chs.) (Exec Rate = 6.25 hz)
Gap1_Vib1(TVIB1) & Gap14_Vib9(TVIB2) Vibration Calculations
PRO02/15H GAP2/15_VIB2/10
SysLim2GAP2/15
PRO02/15L SysLim1GAP2/15
Vib2/10
SysLim2VIB2/10
SysLim1VIB2/10
PRO08/21H GAP8/21_VIB8/16
SysLim2GAP8/21
Vib8/16
SysLim2VIB8/16
SysLim1VIB8/16
Signal
Space
(Sys Inputs)
421
Channels 9 – 12:
Channels 9 – 12 are used for position information only. The Gapx_Pos_Filtering

runs at 4.6 kHz rate and 2.3 kHz rate if input channels 14 through 21 are configured
as vibration channels. This section provides an 8 Hz low pass filter for the gap
calculation. Gapx_Pos Scaling and Limit Check runs every frame. This function
rescales the gap value from volts to EU based on the configuration. The System
Limit Check can be used set a Boolean at minimum and/or maximum limit values
configured by the user.
Channnel 13:
Channel 13 supports position feedback and Keyphasor feedback. The Key_Phasor

Filtering is executed 4.6 kHz rate and 2.3 kHz rate if input channels 14 through 21
are configured as vibration channels. The Filtering function performs a median select
filter for the gap signal.
A hardware comparator circuit with a software controlled hysteresis limit is used to

detect the leading edge of the slot or pedestal gap transition. The Keyphasor timing
pulse is fed into an FPGA with counters that determine the time between Keyphasor
pulses and the firmware uses this information to calculate the rotor speed in rpm. At
very low speeds the hardware Keyphasor comparator is not usable and the runtime
application code determines speed by counting pulses detected through the system
input, GAP13_KPH1.
The Gap13 KP Scaling and Limit Check runs every frame. The gap scaling and
System Limit Check performs the same way it does for channels 1 through 12.
GEH-6421M
Terminal Signal
Board Pts Space
ScaleOff (Sys Inputs)
PRO09/22H Diff Amp,
Vgap GAP9/22_POS1/5
MUX & A/D
PRO09/23L SysLimit2 *
Scale SysLim2GAP9/22
Limit Chk
SysLimit1 *
OFFSET
COMP. LOW PASS * Additional SysLimit Config. Parm.
FILTER SysLimxEnable (En or Dis)
(8 Hz) SysLimxLatch (Latch or Not Latch)
VOLTS SysLimxType (>= or <=)
-----------
COUNT
Gap9 Position Filtering Gap9 Position Scaling & Limit Check
( Rate = 4.6khz for <= 8 vib chs. or 2.3khz for > 8 chs.) (Exec Rate = Frame Rate = 25, 50 or 100 hz)
Gap9_Pos1(TVIB1) and Gap22_Pos5(TVIB2) Gap Calculations
PRO10/23H GAP10/23_POS2/6
Gap10_Pos2(TVIB1) & Gap23_Pos6(TVIB2) Gap Calculations SysLim2GAP10/23
PRO12/25H GAP12/25_POS4/8
Gap12_Pos4(TVIB1) & Gap25_Pos8(TVIB2) Gap Calculations SysLim2GAP12/25
Gap13/26 Filtering ScaleOff

PRO13H Diff Amp, ( Rate = 4.6khz for <= 8 vib chs.
MUX & A/D or 2.3khz for > 8 chs.) Vgap GAP13/26_KPH1/2
PRO13L SysLimit2 *
Scale SysLim2GAP13/26
Limit Chk
SysLimit1 *
OFFSET
COMP.
MEDIAN
* Additional SysLimit Config. Parm.
SELECT SysLimxEnable (En or Dis)
VOLTS SysLimxLatch (Latch or Not Latch)
-1 -1
----------- SysLimxType (>= or <=)
Z Z
COUNT
Key Phasor Support
KPH_Thrshld
KPH_Type
Comparator Speed
Timer RPM_KPH1/2
/ Interrupt Calculation Gap13/26 Scaling & Limit Check
(Exec Rate = Frame Rate = 25, 50 or 100 hz)
Gap13_KP1(TVIB1) & Gap26_KP2(TVIB2) Calculations
423
The Wideband_Vibration Filtering function is executed at 4.6 kHz rate and 2.3 kHz
rate if input channels 14 through 21 are configured as vibration channels. The
vibration input for this function comes from the FPGA that controls the A/D and
multipler circuit. The gap or position filter is a 2-pole low pass filter with a cutoff
frequency set at 8 Hz. The output of the gap filter is expressed in volts and provides
the input the Gap Scaling and Limit Check function.
The wideband vibration information can be shaped or conditioned based on the

configuration parameter, FilterType. FilterTypes equal to Low-pass, Band-pass or
High-pass are used for the Seismic and Velomitor sensor types. FilterType = None is
used by all the other sensor types. The Low-Pass filter can be configured for 2, 4, 6
or 8 pole attenuation behavior through the parameter, Filtrlpattn. The 3 db cutoff
frequency, Filtrlocutoff is also adjustable. The High-pass filter can also be
configured for 2, 4, 6 and 8 pole to sharpen the attenuation characteristics of the filter
through the parameter, Filtrhpattn. The cutoff frequency, Filtrhpcutoff is adjustable
in configuration.
The wideband filtered vibration output, Vfout goes through a minimum/maximum

peak detect function. The capture window for the minimum/maximum detect is 160
milliseconds wide for Keyphasor based speeds greater than 12 rpm. The objective is
to capture at least 2 cycles of vibration information to get an accurate peak-to-peak
calculation.
The wideband unfiltered vibration output, goes through a second

minimum/maximum peak detect function. The outputs, Vmax and Vmin, are used to
clamp the filtered vibration output peak-to-peaks.
GEH-6421M
and Peak Detection
Exec. Rate = 4600 / 2300 Hz
Note 1: Text in BLUE are PVIB configuration parameters.
Mag. (db) Low Pass Filter Note 2: This filter type is only used for Seismics and VelomitorsTM.
V_wb
0 (2,4,6 or 8-pole)
-3 Note 3: This filter type is used for all other sensor types.
Filtrlpcutoff Freq. (Hz)
Filtrlpattn = 8 6 4 2
High Pass Filter Mag. (db) Low Pass Filter

Mag. (db) Vfmax
(2,4,6 or 8-pole) 0 (2,4,6 or 8-pole) FilterType MAX

(cnts)
0 -3
-3 Lowpass(Note2)
425
Bandpass(Note2) Vfout
Volume
MIN Vfmin
(cnts)
II
Highpass(Note2) (cnts)
Filtrlpcutoff Freq. (Hz) Pk-Pk Scan Time
Freq. (Hz)
of 1016
Filtrlpattn = 8 6 4 2 160 ms
none(Note3)
Filtrhpcutoff
Filtrhpattn = 2 4 6 8
High Pass Filter

Mag. (db)
(2,4,6 or 8-pole)
0
-3
MAX
Freq. (Hz)
Filtrhpcutoff
Filtrhpattn = 2 4 6 8
MIN Vmin
(cnts)
Pk-Pk Scan Time
160 ms
VVIB Vibration Monitor Board • 459

Vmax
(cnts)
Vpp Filter and Limit Check
The Vpp, Filter and Limit Check operates on channels 1 through 8 for TVIB1 and
channels 14 through 21 for TVIB2. The execution rate for the function is 6.25 Hz.
The Vpp, Filter, and Limit Check inputs are the following:
• Vfmax – filtered maximum peak vibration

• Vfmin – filtered minimum peak vibration
• Vmin – unfiltered min peak vibration
• Vmax – unfiltered max peak vibration
The system inputs or Vpp, Filter, and Limit Check outputs are:
VIBx - the wideband vibration in EU where the units for EU are in peak for the
configuration parameter, VibType = Seismic, Velomitor or Accelerometer and the
EU units are peak-to-peak for VibType = Proximitor
SysLim1VIBx – the System Limit #1 Boolean (Boolean is True if VIBx is in the

limit 1)
SysLim2VIBx – the System Limit #2 Boolean (Boolean is True if VIBx is in the

limit 2)
The system output used is the System Limit Reset Boolean. If Reset is True, a
latched System Limit Boolean is cleared.
The filtered peak-to-peak wideband vibration signal, Vfpp = Vfmax – Vfmin. Vfpp
is then clamped based on the unfiltered peak-to-peak wideband value. The clamp
prevents outputs from the Infinite Impulse Response (IIR-based) filter designs used
for the high-pass and low-pass filters to exceed the original input values. The
clamped wideband vibration signal, Vpp passes through a single-pole low-pass filter
with an adjustable cutoff frequency, VIB_PP_Fltr.
The Vpp, Filter, and Limit Check scaling block converts the clamped and filtered
wideband peak-to-peak vibration from volts to EU or Volts peak (Vp) depending on
the configuration parameter VibType.
• VibType – determines the A/D conversion value, AD_CONV in units of volts /

counts and the default value for the sensor offset and the final EU units being
expressed in peak or peak-to-peak.
• VIBScale – gain factor expressed in volts peak / EU (peak) irregardless to the
VibType setting.
• ScaleOffset – offset value in EU (peak).
The Vpp, Filter and Limit Check provides two System Limit blocks. The following
configuration parameters control the behavior of the System Limit block:
• SysLimxEnabl – the System Limit (x=1 or 2) Enable is set True to select the use
of the block.
• SysLimxType – the System Limit (x=1 or 2) Type selects whether the limit
check does a “>=” check or a “<=” check.
• SysLimitx – System Limit (x=1 or 2) is the limit value used in the “>=” or “<=”
check.
• SysLimxLatch – System Limit (x=1 or 2) Latch determines whether the Boolean
status flag is latched or unlatched. If the Boolean status flag is latched the flag
will remain True even if the limit value is no longer exceeded.
GEH-6421M
The system input or System Limit Boolean status flag is SysLimxVIBy where x is
the System Limit block number (1 or 2) and y is the VVIB channel input number (1
– 8 for TVIB1 and 14 – 21 for TVIB2).
Gap Scaling and Limit Check
The Gap Scaling and Limit Check operates on channels 1 through 8 for TVIB1 and
channels 14 through 21 for TVIB2. The execution rate for the function is 25, 50, or
100 Hz. The rate of execution is based on the frame rate selected for IONet. The
system inputs or Gap Scaling and Limit Check outputs are:
Gapx_VIBx – the position or gap value in EU for Proximitors and bias voltage in
Vdc for accelerometers with integrated outputs, seismics, and Velomitors
SysLim1GAPx – the System Limit #1 Boolean; (Boolean is True if GAPx_VIBx is

in the limit 1)
SysLim2GAPx – the System Limit #2 Boolean. (Boolean is True if GAP_VIBx is in

the limit 2)
The Gap Scaling and Limit Check scaling block converts the 8 Hz filtered output gap
signal from volts to EU or Volts peak (Vp) depending on the configuration
parameter VibType. The scaling is determined by the following configuration
parameters:
• VIB_Scale – gain factor expressed in volts peak / EU (peak) irregardless to the

VibType setting.
• ScaleOffset – offset value in EU (peak)
The Gap Scaling and Limit Check provides two System Limit blocks. The following
configuration parameters control the behavior of the System Limit block:
of the block.
check.
The system input or System Limit Boolean status flag is SysLimxGAPy where x is
427
Gapx_POSy Gap Calculations
The Gapx_POSy Gap Calculations is comprised of the Gapx Position Filtering and
the Gapx_Pos Scaling and Limit Check where x is the VVIB channel number 9
through 12 for TVIB1 and 22 through 25 for TVIB2 and y is the position number 1 –
4 for TVIB1 and 5 – 8 for TVIB2. The Gapx_POSy Gap Calculation’s outputs are:
Gapx_POSy – the position or gap value in EU for Proximitors
SysLim1GAPx – the System Limit #1 Boolean (Boolean is True if GAPx_POSy is in

the limit 1)
SysLim2GAPx – the System Limit #2 Boolean (Boolean is True if GAP_POSy is in

the limit 2)
The Gapx_Position Filtering is executed at 4.6 kHz rate and 2.3 kHz rate if input
channels 14 through 21 are configured as vibration channels. The position input for
this function comes from an FPGA that controls the multiplexed A/Ds. The A/D
value is compensated for A/D gain and offset errors and converted to volts. A
median select filter is then applied.
The Gapx_Position Scaling and Limit Check scaling block converts the filtered gap
signal from volts to EU or Volts peak (Vp) depending on the configuration
parameter VibType. The configuration parameters are:
• Scale – gain factor expressed in volts peak / EU (peak)

The Gapx_Position Scaling and Limit Check provides two System Limit blocks. The
following configuration parameters control the behavior of the System Limit block:
of the block.
check.
The system input or System Limit Boolean status flag is SysLimxGAPy where x is
GEH-6421M
Gap13/26_KPH1/2 Calculations
The Gap13/26_KPH12 Calculations is comprised of the Gap13/26 Filtering and the

Gap13/26_KP Scaling and Limit Check. The Gap13/26_KPH1/2 Calculation system
inputs are:
GAP13_KPH1 – the position or gap value in EU for the Keyphasor Proximitor for
TVIB1
GAP26_KPH2 – the position or gap value in EU for the Keyphasor Proximitor for
TVIB2
SysLim1GAP13 – the System Limit #1 Boolean for TVIB1 (Boolean is True if

GAP13_KPH1 is in the limit 1)



The Gap13_KPH1 system outputs are:
SysLimReset – the System Limit Reset Boolean (If Reset is True, a latched System
Limit Boolean is cleared)
LM_RPMx – rotor shaft speed in rpm from different stages of the turbine (x = A, B
or C)
The Gap 13/26 Filtering is executed at 4.6 kHz rate and 2.3 kHz rate if input
channels 14 through 21 are configured as vibration channels. The input for this
function comes from a multiplexed A/D controlled by an FPGA. The Gap 13/26
Filtering uses the median select function to calculate the filtered gap. The median
select filter uses the present value (n), the previous (n-1), and the value 2 samples
back (n-2) to perform a median select on. The output is expressed in volts and passes
to the Gap13/26 Scaling and Limit Check.
The Gap13/26 Scaling and Limit Check scaling block converts the filtered gap signal
from volts to EU. The Gap13/26 runs at the frame rate of either 25, 50 or 100 Hz.
The gap conversion is based on the following configuration parameters:

The Gap13/26 Scaling & Limit Check provides two System Limit blocks. The
following configuration parameters control the behavior of the System Limit block:
of the block.
check.
429
The system input or System Limit Boolean status flag is SysLimxGAP13 for TVIB1
and SysLimxGAP26 for TVIB2 where x is the System Limit block number (1 or 2).
1X and 2X Calculations based on Keyphasor Input
The 1X and 2X Calculations based on a Keyphasor input provides a peak-to-peak

vibration component (magnitude and phase) at both the Keyphasor frequency and
twice the frequency. The calculations are comprised of two sections:
• Modulator and Filter

• Magnitude and Phase Calculation
The system inputs from the 1X & 2X calculations are:
• Vib1Xy – the peak-to-peak magnitude of the vibration phasor that is rotating at

the Keyphasor frequency
• Vib1xPHy – the phase angle between the Keyphasor input and the ViB1Xy
vibration phasor
• Vib2Xy – the peak-to-peak magnitude of the vibration phasor that is rotating at
the twice the Keyphasor frequency
• Vib1xPHy – the phase angle between the Keyphasor input and the Vib2Xy
vibration phasor, and where y is the VVIB channel number, 1 through 8 for
TVIB1 and 14 through 21 for TVIB2
The Modulator and Filter for both the 1X and 2X calculations are executed at 4.6
kHz rate and 2.3 kHz rate if input channels 14 through 21 are configured as vibration
channels. The 1X modulator has two inputs: delta_1/delta_2 and the vibration
channel input. The delta_1/ delta_2 is the point in the key_phasor cycle where the
vibration channel input was sampled. The range for delta_1/delta_2 is from 0 to 1.
Delta_1/delta_2 is converted to radians and is the index into a cosine and sine lookup
table. The result from the cosine and sine lookup table is modulated with the
vibration channel input. The modulated signal is filtered through a 4-pole low pass
filter with a cutoff frequency of 0.25 Hz. The filter output provides the dc value of
the de-modulated components: the real and imaginary phasors of the vibration
component that is rotating at 1X speed.
The Vibration 1X function uses the real and imaginary vibration components based
on the Keyphasor frequency as the inputs to the RMS calculator. The square root of
the sum of the squares of the real and imaginary vibration components times the
scaling block results in the peak-to-peak magnitude of the 1X vibration phasor,
Vib1Xy rotating at the Keyphasor frequency. The phase, Vib1xPHy, is the arccosine
of the absolute value of Fpi / (VMK ).
The Vibration 2X function is the same calculation except the input delta_1/delta_2 is
multiplied by 4 * PI instead of 2 * PI. The results are a peak-to-peak magnitude of
the 2X vibration phasor, Vib2Xy, rotating at twice the Keyphasor frequency and a
phase of Vib2xPHy.
The scaling block converts the VMK * 4 signal to EU. The scaling is based the
following configuration parameters:

GEH-6421M
Terminal
Board Pts
Ch 1/14 Signal Cond. & A / D Input Block
PRO01/14H Diff Amp, A/D GAIN VOLTS

MUX & & OFFSET -----------
PRO01/14L A/D COMP. COUNT
Signal
Vibration 1X for Ch 1/14
Space
LOW PASS (Sys Inputs)
Fs = 100 Hz
COS X FILTER X
(.25 Hz, 4P)
delta_1 ips
------------- 2 * PI + SQRT 4 ------ Vib1X1/9
delta_2 volt
LOW PASS 57.29578 Vib1xPH1/9
VMK
SINE X FILTER X
(.25 Hz, 4P)
D
Fs = 4.6khz for <= 8 chs. or -1
Fpi N ABS
2.3khz for > 8 vib ch. COS
DIVIDE
Vibration 2X for Ch 1
LOW PASS
Fs = 100 Hz
COS X FILTER X
(.25 Hz, 4P)
ips
4 * PI + SQRT 4 ------ Vib2X1/9
volt
LOW PASS 57.29578 Vib2xPH1/9
VMK
SINE X FILTER X
(.25 Hz, 4P)
D
Fs = 4.6khz for <= 8 chs. or -1
Fpi N ABS
2.3khz for > 8 vib ch. COS
DIVIDE
where delta_1 Time from KeyPhasor to A/D Read

---------- = --------------------------------------------------- + ( Channel # - 1 ) * A/D Conv. Time
Terminal delta_2 KeyPhasor Period
Board Pts
PRO02/15H Vib1X2/10
Ch 2/15 Signal Cond. &
Vibration 1X for Ch2/15
A / D Input Block
PRO02/15L Vib1xPH2/10
Vib2X2/10
Vib2xPH2/10
PRO08/21H Vib1X8/16
Ch 8/21 Signal Cond. &
Vibration 1X for Ch8/21
A / D Input Block
PRO08/21L Vib1xPH8/16
Vib2X8/16
Vib2xPH8/16
431
Tracking Filters based on LM_RPM_A/B and C
The Tracking Filters based on LM_RPM_A/B and C provide the peak vibration
component (magnitude only) at the frequencies: LM_RPM_A, LM_RPM_B, and
LM_RPM_C. The Tracking filters require both Modulation & filter stage executing
at 4.6 kHz rate and 2.3 kHz rate if input channels 14 through 21 are configured as
vibration channels and the Magnitude calculation.
The system inputs from the Tracking filters are:
• LMVibxA – the peak magnitude of the vibration component rotating at

LM_RPM_A speed
• LMVibxB – the peak magnitude of the vibration component rotating at
LM_RPM_B speed
• LMVibxC – the peak magnitude of the vibration component rotating at
LM_RPM_C speed
• SysLim1ACCx – the System Limit Boolean status of Limit1 where x = 1
through 9
• SysLim2ACCx – the System Limit Boolean status of Limit2 where x = 1
through 9
The Modulator and Low-pass filter for the LMVibxA, LMVibxB, and LMVibxC
tracking filters are executed at 4.6 kHz rate. The low-pass filter is identical for all
tracking filters. The filter is a 5-pole low-pass filter with a cutoff frequency equal to
2.5 Hz. The LMVibxA filter inputs are the modulated signals cos(2pi/60Fs *
LM_RPM_A) * Vibration Input and sin(2pi/60Fs * LM_RPM_A) * Vibration Input.
The filtered output of the modulated vibration input with the sine is the de-modulated
imaginary component of the channel vibration based on the rotor shaft speed,
LM_RPM_A and the filtered output of the modulated vibration input with the cosine
is the de-modulated real component of the channel vibration based on the rotor shaft
speed, LM_RPM_A.
The LMVibxB and LMVibxC tracking filters perform the same task as the
LMVibxA filter, except the de-modulated real and imaginary components of the
vibration input are based on the rotor speeds: LM_RPM_B and LM_RPM_C.
The scaling block converts the VMx where x = A, B, or C magnitude to EU. The
scaling is based on the following configuration parameters:

The Tracking Filter provides two System Limit blocks. The following configuration
parameters control the behavior of the System Limit block:
of the block.
check.
GEH-6421M
Terminal
Board Pts Ch 1 Signal Cond. & A / D Input Block
PRO01H Diff Amp, A/D GAIN VOLTS

MUX & & OFFSET -----------
PRO01L A/D COMP. COUNT
Signal
Space
Ch 1Tracking Filter for LM_RPM_A (Sys Inputs)
Fs = 4.6khz for <= 8 chs. or
Signal 2.3khz for > 8 vib ch. LOW PASS ips
Space COS X FILTER X 2 ------ LMVib1A
(Sys Outputs) (2.5 Hz, 5P) volt
2 * PI
LM_RPM_A ---------- X + SQRT
60 * Fs SysLimit2 * SysLim2ACC1
LOW PASS
n SINE X FILTER X Limit Chk
(2.5 Hz, 5P) SysLimit1 * SysLim1ACC1
( 1 to Fs / (LM_RPM_A/60) ) SysLimxEnable (En or Dis)
SysLimxLatch (Latch or Not Latch) Fs = 100 Hz
SysLimxType (>= or <=)
Ch 1 Tracking Filter for LM_RPM_B

2.3khz for > 8 vib ch. LOW PASS ips
COS X FILTER X 2 ------ LMVib1B
(2.5 Hz, 5P) volt
2 * PI
LM_RPM_B ---------- X + SQRT
SysLimit2 * SysLim2ACC2
60 * Fs
LOW PASS Limit Chk
n
SINE X FILTER X SysLimit1 * SysLim1ACC2
(2.5 Hz, 5P) * Additional SysLimit Config. Parm.
SysLimxEnable (En or Dis)
( 1 to Fs / (LM_RPM_B/60) ) SysLimxLatch (Latch or Not Latch)
SysLimxType (>= or <=) Fs = 100 Hz
Ch 1 Tracking Filter for LM_RPM_C

2.3khz for > 8 vib ch. LOW PASS ips
COS X FILTER X 2 ------ LMVib1C
(2.5 Hz, 5P) volt
2 * PI
LM_RPM_C ---------- X + SQRT
SysLimit2 * SysLim2ACC3
60 * Fs
LOW PASS Limit Chk
SINE X FILTER X SysLimit1 * SysLim1ACC3
n (2.5 Hz, 5P)
SysLimxEnable (En or Dis)
( 1 to Fs / (LM_RPM_C/60) ) SysLimxLatch (Latch or Not Latch) Fs = 100 Hz
SysLimxType (>= or <=)
LMVib2A
Ch 2 Tracking Filter for LM_RPM_A SysLim2ACC4
SysLim1ACC4
LMVib2B
Terminal
Ch 2 Tracking Filter for LM_RPM_B SysLim2ACC5
Board Pts
SysLim1ACC5
PRO02H LMVib2C
Ch 2 Signal Cond. &
Ch 2 Tracking Filter for LM_RPM_C SysLim2ACC6
A / D Input Block
PRO02L SysLim1ACC6
LMVib3A
Ch 3 Tracking Filter for LM_RPM_A SysLim2ACC7
SysLim1ACC7
LMVib3B
Ch 3 Tracking Filter for LM_RPM_B SysLim2ACC8
SysLim1ACC8
PRO03H LMVib3C
Ch 3 Signal Cond. &
Ch 3 Tracking Filter for LM_RPM_C SysLim2ACC9
A / D Input Block
PRO03L SysLim1ACC9
433
Specifications
Item Specification
Number of Channels TVIB: 13 probes: 8 vibration, 4 position, 1 Keyphasor
VVIB: 26 probes with two TVIB boards
Vibration Measurement Range Accuracy Frequency
Proximity Displacement 0 to 4.5 V pp ±0 .030 V pp 5 to 200 Hz
Displacement 0 to 4.5 V pp ±0 .150 V pp 200 to 500 Hz
Seismic Velocity 0 to 2.25 V p Max [2% reading, ±0.008 Vp] 5 to 200 Hz
Velocity 0 to 2.25 V p Max [5% reading, ±0.008 Vp] 200 to 500 Hz
Velomitor Velocity 0 to 2.25 V p Max [2% reading, ±0.008 Vp] 5 to 200 Hz
Velocity 0 to 2.25 V p Max [5% reading, ±0.008 Vp] 200 to 500 Hz
Accelerometer Velocity (track filter) 0 to 2.25 V p ±0.015 Vp 10 to 233 Hz
Position Position -.5 to -20 V dc ±0.2 V dc Air gap (average)
Phase Degrees 0 to 360 degrees ±2 degrees Up to 14,000 rpm
(1X vibration component with respect to key slot)
Probe power -24 V dc from the -28 V dc bus; each probe supply is current limited
12 mA load per transducer
Probe signal sampling 16-bit A/D converter with 14-bit resolution on the VVIB
Sampling rate is 4,600 samples per second in fast scan mode (4,000 to 17,500 rpm)
Sampling rate is 2,586 samples per second for nine or more probes (less than 4,000 rpm)
All inputs are simultaneously sampled in time windows of 160 ms
Rated RPM If greater than 4,000 rpm, can use eight vibration channels, (others can be prox/position)
If less than 4,000 rpm, can use 16 vibration channels, and other probes
Buffered outputs Amplitude accuracy is 0.1% for signal to Bently Nevada 3500 vibration analysis system
Diagnostics
Diagnostics perform a high/low (hardware) limit check on the input signal and a
high/low system (software) limit check. The software limit check is adjustable in the
field.
A probe fault, alarm, or trip condition occurs if either of an X or Y probe pair

exceeds its limits. In addition, the application software prevents a vibration trip (the
ac component) if a probe fault is detected based on the dc component.
Position inputs for thrust wear protection, differential expansion, and eccentricity are
monitored similar to the vibration inputs except only the dc component is used for a
position indication. A 16-bit sampling type A/D converter is used with 14-bit
resolution and overall circuit accuracy of 1% of full scale.
Vibration Monitoring and Analysis
Note The Mark VI system provides vibration protection and displays the basic
vibration parameters.
GEH-6421M
Each input is actively isolated and the signals made available through four plugs for
direct cabling to a Bently Nevada 3500 monitor. This configuration provides the
maximum reliability by having a direct interface from the Proximitors to the turbine
control for trip protection and still retaining the real-time data access to the Bently
Nevada system for static and dynamic vibration monitoring.
Note The Mark VI system displays the total vibration, the 1X vibration component,
and the 1X vibration phase angle, but it is not intended as a vibration analysis
system.
Fourteen BNC connectors on TVIB provide buffered signals available to portable

data gathering equipment for predictive maintenance purposes. Buffered outputs
have unity gain, 10 kΩ internal impedance, and can drive loads up to 1500 Ω
configuration.
Configuration
Configuration
System limits Enable system limits Enable, disable
Vib_PP_Fltr First order filter time constant (sec) 0.01 to 2
LMVib1A Vib, 1X component, for LM_RPM_A, input #1 - board Point edit (input FLOAT)
point
SysLim1Enable Enable system limit 1 fault check Enable, disable
SysLim1Latch Latch system limit 1 fault Latch, not latch
SysLim1Type system limit 1 check type >= or <=
SysLimit1 System Limit 1 - Vibration in mils (Prox) or Inch/sec -100 to +100
(seismic, accel)
SysLim2Enable Enable system limit 2 (same configuration as above) Enable, disable
TMR_DiffLimt Difference limit for voted TMR inputs in volts or mils -100 to +100
LMVib1B Vib, 1X component, for LM_RPM_B, #1 - board point Point edit (input FLOAT)
LMVib1C Vib, 1X component, for LM_RPM_C, #1 - board point Point edit (input FLOAT)
LMVib2A Vib, 1X component, for LM_RPM_A, #2 - board point Point edit (input FLOAT)
LMVib3A Vib, 1X component, for LM_RPM_A, #3 - board point Point edit (input FLOAT)
J3:IS200TVIBH1A Vibration terminal board, first of two Connected, not connected
GAP1_VIB1 Average air gap (for Prox) or dc volts (for others) - board Point edit (input FLOAT)
point
VIB_Type Type of vibration probe Unused, PosProx, VibProx, VibProx-
KPH1, VibProx-KPH2, VibLMAccel,
VibVelomitor, KeyPhasor
VIB_Scale Volts/mil or volts/ips 0 to 2
ScaleOff Scale offset for prox position only, in mils 0 to 90
SysLim1Enable Enable system limit 1 Enable, disable
SysLim1Latch Latch the alarm Latch, not latch
SysLim1Type System limit 1 check type >= or <=
SysLimit1 System limit 1 – GAP in negative volts (for vel) or positive -100 to +100
mils (prox)
SysLim2Enabl Enable system limit 2 (same configuration as above) Enable, disable
TMR_DiffLimt Difference limit for voted TMR inputs in volts or mils -100 to +100
435
Vib1 Vibration, displacement (pk-pk) or velocity (pk) - board Point edit (input FLOAT)
point
SysLim1Enable System limits configured as above Enable, disable
GAP2_VIB2 Second vibration probe of 8 - board point Point edit (input FLOAT)
point
GAP9_POS1 First position probe of 4 - board point Point edit (input FLOAT)
GAP13_KPH1 KeyPhasor probe air gap - board point Point edit (input FLOAT)
J4:IS200TVIBH1A Second vibration terminal board Connected, not connected
GAP14_VIB9 First Vibration Probe of 8 - board point Point edit (input FLOAT)
point
GAP22_POS5 First position probe of 4 - board point Point edit (input FLOAT)
GAP26_KPH2 KeyPhasor probe air gap - board point Point edit (input FLOAT)
L3DIAG_VVIB1 Board diagnostic Input BIT
SysLim1GAP1 Gap signal limit Input BIT
: : Input BIT
: : Input BIT
SysLim1VIB1 Vibration signal limit Input BIT
: : Input BIT
SysLim1ACC1 Acceleration signal limit Input BIT
: : Input BIT
: : Input BIT
: : Input BIT
RPM_KPH1 Speed RPM, of KP #1 Input FLOAT
RPM_KPH2 Speed RPM, of KP #2 Input FLOAT
Vib1X1 Vibration, 1X component only, displacement Input FLOAT
: : Input FLOAT
Vib1X16 Vibration, 1X component only, displacement Input FLOAT
Vib1XPH1 Angle of 1X component to KP Input FLOAT
: : Input FLOAT
Vib1XPH16 Angle of 1X component to KP Input FLOAT
LM_RPM_A -------- Output FLOAT
LM_RPM_B -------- Output FLOAT
LM_RPM_C -------- Output FLOAT
GEH-6421M
Alarms
2 Flash Memory CRC Failure Board firmware programming error (board will not
go online)
board.
30 ConfigCompatCode mismatch; Firmware: #; Tre: # A tre file has been installed that is incompatible
The configuration compatibility code that the firmware with the firmware on the I/O board. Either the tre
is expecting is different than what is in the tre file for file or firmware must change. Contact the factory.
this board
31 IOCompatCode mismatch; Firmware: #; Tre: # A tre file has been installed that is incompatible
The I/O compatibility code that the firmware is with the firmware on the I/O board. Either the tre
expecting is different than what is in the tre file for this file or firmware must change. Contact the factory.
board
32 VVIB A/D Converter 1 Calibration Outside of Spec. The hardware failed (if so replace the board) or
VVIB monitors the Calibration Levels on the 2 A/D. If there is a voltage supply problem
any one of the calibration voltages is not within 1% of
its expected value, this alarm is set
33 VVIB A/D Converter 2 Calibration Outside of Spec. The hardware failed (if so replace the board) or
VVIB monitors the Calibration Levels on the 2 A/D. If there is a voltage supply problem
any one of the calibration voltages is not within 1% of
its expected value, this alarm is set
34 TVIB J3 Analog Input (channel #) Out of Limits Possible open circuit, customer cable short or
sensor failure
35 TVIB J4 Analog Input (channel #) Out of Limits Possible open circuit, customer cable short or
sensor failure
65-77/ TVIB/DVIB J3/J4 Analog Input # out of limits. VVIB The TVIB/DVIB board(s) may not exist but the
81-93 monitors the Signal Levels from the 2 A/D. If any one sensor is specified as used, or the sensor may be
of the voltages is above the max value, this diagnostic bad, or the wire fell off, or the device is miswired.
is set
128- Logic Signal # Voting mismatch. The identified signal A problem with the input. This could be the device,
287 from this board disagrees with the voted value the wire to the terminal board, the terminal board,
or the cable.
288- Input Signal # Voting mismatch, Local #, Voted #. The A problem with the input. This could be the device,
404 specified input signal varies from the voted value of the wire to the terminal board, the terminal board,
the signal by more than the TMR Diff Limit or the cable.
437
TVIB Vibration Input
The Vibration Input (TVIB) terminal board accepts up to 14 vibration probes, two of
which can be cabled directly to the VVIB board. VVIB processes and digitizes the
displacement and velocity signals, which are then sent over the VME bus to the
controller. The Mark* VI system uses Bently Nevada probes for shaft vibration
monitoring. The following vibration probes are compatible with TVIB:
• Proximity
• Velocity
• Acceleration
• Seismic
• Phase
There are two types of TVIB terminal boards, H1A and H2A. The H2A type board
has BNC connectors allowing portable vibration data gathering equipment to be
plugged in for predictive maintenance purposes. Both types have connectors so that
Bently Nevada vibration monitoring equipment can be permanently cabled to the
terminal board to measure and analyze turbine vibration.
In the Mark VI system TVIB works with the VVIB processor and supports simplex
and TMR applications. Two TVIBs connect to VVIB with two cables. In TMR
systems, TVIB connects to three VVIB processors with three cables.
Note TVIBH does not support Mark VIe I/O packs.
GEH-6421M
TVIB Terminal Board VVIB VME Board
x
x
x 37-pin "D" shell
x 2
x 1 ...JA1
...
...
JT1 type connectors
. RUN
x 4
x 3 ... with latching FAIL
...
6
x 5 . STAT
x
x 7
...
... fasteners
Vibration x 8 .
...
x 10 x 9 ...
.
signals x 11 ...
x 12 . JB1
...
x 14 x 13 ...
...
x 16 x 15 .
x 17
...
...
.
Cable to
x 18
x 20 x 19 ...
...
. JS1 rack T
x 22 x 21
24 x 23 JC1
x VME bus to VCMI
x
x
x 26 x 25
x 28 x 27 Cable to
x 29 JD1 rack S
Vibration x 30
x 32 x 31
signals x 33 JR1
x 34 P2 P1
x 36 x 35
x 38 x 37
x 40 x 39 P6 P5 P4 P3 VVIB
x 42 x 41 x
x 44
x 43
x 46 x 45 P10 P9 P8 P7 Connectors on J3
x 48
x 47
14 13 12 P11 VME rack R
x
x
Shield bar
Plugs for Portable Bently- J4

Cable to VME
Nevada data gathering &
rack R
monitoring equipment
Cables to fixed Bently- Cable from second TVIB

Nevada 3500 Vibration
Monitoring System
Vibration Terminal Board, Processor Board, and Cabling
Installation
Connect the wires for the 14 vibration probes to the two terminal blocks, three wires
per probe. In simplex systems, connect the TVIB1 JR1 connector to VVIB J3 on the
VME rack and the TVIB JR1 connector to VVIB J4. In TMR systems, connect the
VVIB JR1, JS1, and JT1 connectors to the R, S, and T VVIBs. Use jumpers JP1
through JP8 to select the probe type for the first eight probes. Optionally, connect
TVIB to a Bently Nevada system using connectors JA1, JB1, JC1, and JD1.
Note Permanent cable connections to BNCs P1 through P14 are not made.
439
S P,V,A
Vibration Terminal JPxB B/N buffer: Jumper
Board TVIBH2A JPxA sensor input: V P,A positions
S
JP1B Probe
x JP1A selection
x 1 N24V01 JP2B jumpers
PR01 (H) x 2
N24V02 x 4
x 3 PR01 (L) JP2A
x 5 PR02 (H) JP3B
PR02 (L) x 6
x 7 N24V03 JP3A
PR03 (H) x 8 JP4B
N24V04 x 10
x 9 PR03 (L)
x 11 PR04 (H) Vibration JP4A
PR04 (L) x 12 JP5B
x 13 N24V05 probes
PR05 (H) x 14 JP5A
x 15 PR05 (L) JP6B
N24V06 x 16
PR06 (L) x 18
x 17 PR06 (H) JP6A
PR07 (H)
x 19 N24V07 JP7B
x 20
N24V08
x 21 PR07 (L) JP7A
x 22
x 23 PR08 (H) JP8B
PR08 (L) x 24
JP8A
x
Connectors JR1, JS1, JT1, to VME racks
Connectors JA1,JB1, JC1, JD1 to optional

x Bentley Nevada 3500 system
PR09 (H) x 26
x 25 N24V09
N24V10 x 28
x 27 PR09 (L) BNC
x 29 PR10 (H) Position connectors
PR10 (L) x 30
x 31 N24V11 probes P2 P1 for portable
PR11 (H) x 32
x 33 PR11 (L) data
N24V12 x 34
x 35 PR12 (H) gathering
PR12 (L) x 36
PR13 (H) x 38
x 37 N24V13 P6 P5 P4 P3 equipment
N24V14 x 40
x 39 PR13 (L)
PR14 (L) x 42
x 41 PR14 (H)
x 43 P10 P9 P8 P7
x 44 P1 is PR01
x 45 Reference P2 is PR02
x 46
x 47 probe and so on.
x 48 P14 P13 P12 P11
x Bently Nevada P14 is for
probe Bently Nevada
Connector Pin Assignments Px, BNC
Jumper JPXA:
Ckt Sensor Conn Comm Sign Shld Connector
P1 S = Seismic
01 Vib 1 JA1 2 3 4
V = Velomitor
02 Vib 2 JA1 6 7 8 P2
P3 P = Proximitor
03 Vib 3 JA1 10 11 12
P4 A = Accelerometer
04 Vib 4 JA1 24 23 22
05 Vib 5 JB1 2 3 4 P5 Jumper JPXB:
06 Vib 6 JB1 6 7 8 P6 S = Seismic
07 Vib 7 JB1 10 11 12 P7 V = Velomitor
08 Vib 8 JB1 24 23 22 P8 P = Proximitor
09 Pos 1 JC1 2 3 4 P9 A = Accelerometer
10 Pos 2 JC1 6 7 8 P10
11 Pos 3 JC1 10 11 12 P11
12 Pos 4 JC1 24 23 22 P12
13 Ref probeJD1 3 1 2 P13
14 B/N only JD1 9 5 4 P14
Terminal Board TVIB Wiring
Operation
® ®
TVIB supports Proximitor , Seismic, Accelerometer, and Velomitor probes
supplied by Bently Nevada. Power for the vibration probes comes from the VVIB
boards in simplex or TMR mode. The probe signals return to VVIB where they are
A/D converted and sent over the VME bus to the controller. Vibration, eccentricity,
and axial position alarms and trip logic are generated in the controller.
GEH-6421M
A -28 V dc source is supplied to the terminal board from the VME board for
Proximitor power. In TMR systems, a diode high-select circuit selects the highest -
28 V dc bus for redundancy. Regulators provide individual excitation sources, -23 to
-26 V dc, that are short circuit protected. VVIB samples the probe inputs at high
speed over discrete time periods.
<R>
<S>
<T>
Vibration Board
Terminal Board TVIBH2A VVIB
JR1 J3
N28V 28 V dc
To
N28VR controller
<S>
<T> Amp A/D
Current
Limit ID Sampling
1 N24V1
S CL type A/D
P V 2 PR01H converter
S JS1 J3 (16 bit)
R s V 3mA
S N28V
O JP1A P,A
3 PR01L Same as
X S
Vib. or pos. PCOM <S>
Eight of the
prox. (P), or
above ccts. ID
seismic (S), P,V,A
or accel (A), TMR
or velomiter N28V
JT1
Applications
S J3
(V) N28V
CL JP1B
Negative Same as
25 N24V9 Volt Ref <T>
S
P 26 PR09H ID
R S
JA1
O 27 PR09L D
S
X B2
Four of the 5
above ccts. Buffer
Position Amplifiers
prox PCOM JB1 J4
D
B2
N28V 5
Buffer P1-P8 JC1 J4

CL Amplifiers D
B2
37 N24V13 5
S
P 38 PR13H
R S
O 39 PR13L P9-P12
S BNC JD1
X J4
Buffer Connectors D
Reference or Amplifiers B9
PCOM
keyphasor
prox. One of the above ccts for Mark VI
(Two of the above ccts for B/N
P13-P14
Four cables to Bently
Nevada 3500 system
TVIB Board, Vibration Probes, and Bently Nevada Interface
441
Specifications
Item Specification
Number of Channels 13 probes: 8 vibration, 4 position, 1 Keyphasor
Probe Type Measurement Range Accuracy
Proximity Displacement 0 to 4.5 V pp ±0 .030 V pp
5 to 200 Hz
Displacement 0 to 4.5 V pp ±0 .150 V pp
200 to 500 Hz
Seismic Velocity 0 to 2.25 V p Max [2% reading, ±0.008 Vp]
5 to 200 Hz
Velocity 0 to 2.25 V p Max [5% reading, ±0.008 Vp]
200 to 500 Hz
Velomitor Velocity 0 to 2.25 V p Max [2% reading, ±0.008 Vp]
5 to 200 Hz
Velocity 0 to 2.25 V p Max [5% reading, ±0.008 Vp]
200 to 500 Hz
Accelerometer Velocity (track filter) 0 to 2.25 V p ±0 .015 Vp
10 to 233 Hz
Position Position -.5 to -20 V dc ±0.2 V dc
Air gap (average)
Phase Degrees
0 to 360 degrees ±2
degrees
Up to 14,000 rpm
(1X vibration
component with respect
to key slot)
Probe power -24 V dc from the -28 V dc bus; each probe supply is current limited
12 mA load per transducer
Rated RPM If greater than 4,000 rpm, can use eight vibration channels, (others can be prox/position)
If less than 4,000 rpm, can use 16 vibration channels, and other probes
Buffered outputs Amplitude accuracy is 0.1% for signal to Bently Nevada* 3500 vibration analysis system
GEH-6421M
Diagnostics
Diagnostic tests are performed on the terminal board components by VVIB as
follows:
• Diagnostics perform a high/low (hardware) limit check on the probe input

signals and a high/low system (software) limit check. These limits create faults.
• A probe fault, alarm, or trip condition will occur if either of an X or Y probe pair
exceeds its limits.
• Position inputs for thrust wear protection, differential expansion, and
eccentricity are monitored similar to the vibration inputs except only the dc
component is used for a position indication. If a maximum limit is exceeded a
fault is created.
Fourteen BNC connectors on TVIB provide buffered signals available to portable
data gathering equipment for predictive maintenance purposes. Buffered outputs
have unity gain, 10 Ω internal impedance, and can drive loads up to 1500 Ω.
Configuration
Jumpers JP1A through JP8A select the type of the first eight probes as follows:
• S = Seismic
• V = Velocity
• P = Proximity
• A = Accelerometer
Refer to the Installation section for more information.
DVIB Simplex Vibration Input

The Simplex Vibration Input (DVIB) terminal board is a compact vibration terminal
board for DIN-rail mounting. It is designed to meet UL 1604 specification for
operation in a 65°C Class 1, Division 2 environment. DVIB accepts 13 vibration
probes, including 8 vibration inputs, 4 position inputs, and 1 Keyphasor input. It
connects to the VVIB processor board with a 37-pin cable identical to those used on
the larger TVIB terminal board. VVIB accommodates two DVIB boards.
Note Only a simplex version is available.
443
Notes
444 of 1016
TTPW Power Conditioning Board
TTPW Power Conditioning

The Power Conditioning (TTPWH1A) terminal board power conditioning board
provides branch circuit protection and distribution between one or more Mark* VI
rack mounted +28 V dc power supplies and discrete wiring to peripheral devices.
The H1A has three 2-pin inputs for +28 V dc from the Mark VI power supply. It
provides diode OR selection between the three inputs to power the +28 V dc outputs.
Outputs are rated 22 – 30 V dc, 0 – 0.25 A individually and capable of parallel
operation. There is high frequency isolation between the inputs and the outputs and
the voltage drop is less than +4 V dc when delivering rated current.
<R>
Power
VME rack supply
PL2
PS28C PL3
"Isolation" PS28C
<S>
Power TB2
T Nine 0.25 A
VME rack supply P1
T outputs
PL2
P2 P
PL3 W
PS28C P3
PS28C T
"Isolation"
TB1 B
Discret A
<T> ewiring I
Power
Monitoring
VME rack supply
PL2
PL3
PS28C
PS28C
"Isolation"
TTPWH1A Application Diagram
445
Volume II TTPW Power Conditioning Board • 483
Large steam turbines use 24 V dc electrical trip solenoid valves (ETSV). Power for
these valves is provided to the TRPL and TREL trip boards by a power transition
board TTPW. Wiring from the rack power supplies, through TTPW, to the trip board
is shown in the figure.
<R>
Power Single ETSV Applications:
VME rack supply
PL2
PS28C PL3
"Isolation" PS28C
<S>
Power
VME rack supply P1 T JA1 PwrA JP1 T
PL2 T R
P2 P P
PL3 W
PS28C P3 L ETSV
PS28C T
"Isolation"
B
Discret A
<T> wiring I T
Power R
Monitoring
VME rack supply E
PL2 L
PL3
PS28C
PS28C
"Isolation"
Double ETSV Applications:

<R>
Power P1 T JA1 PwrA
VME rack supply
T
PL2 P
PL3 W
PS28C
"Isolation" PS28C T
B
A T
<S> I JP1 R
Power Monitoring P
JP2
VME rack supply L ETSV1 ETSV2
PL2 P2 T JA1 PwrB
T
PL3 P
PS28C T
"Isolation" PS28C W R
T E
<T> B L
A
Power I
VME rack supply Monitoring
PL2
PS28C PL3
"Isolation" PS28C
TTPWG1B Wiring to the ETSV
484 • TTPW Power Conditioning Board 446 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Installation
TTPWG1B
Three 28 V dc supplies are wired from I/O racks R, S, and T to plugs P1, P2, and P3.
The primary 28 V dc output comes from plug JA1 and is wired to the trip board
TRPL. The power monitoring signals are wired to the top terminal block (TB1) and
go to an analog input board. The secondary voltage outputs are wired to the lower
terminal block (TB2) as shown in the following figure.
Power Conditioning Board TTPWG1B
28 V power from
racks R, S, T
x
x 1 P1 1 P28R
x 2
x 3 PCOM (Sig) (R)
PCOM (Gnd) x 4 2 PCOM
x 5
x 6
P28R (Gnd) x 8
x 7 P28R (Sig) P2
x 9 1 P28S
x 10 (S)
x 11 P28S (Sig) Monitoring 2 PCOM
P28S (Gnd) x 12
x 13 signals to
x 14
x 15 P28T (Sig) TBAI board P3
P28T (Gnd) x 16 1 P28T
x 17 (T)
x 18 PCOM
x 19 P28V (Sig) 2
P28V (Gnd) x 20
x 21
x 22
x 23
x 24
x 28 V power to
TRPL trip board
x
x 25 P28V1 (Pos) JA1 1 P28V
P28V1 (Neg) x 26
x 27 P28V2 (Pos) (P28V)
P28V2 (Neg) x 28 2 PCOM
x 29
x 30
P28V3 (Neg) x 32
x 31 P28V3 (Pos)
P28V4 (Pos) Power
x 33
P28V4 (Neg) x 34 outputs
P28V5 (Neg) x 36
x 35 P28V5 (Pos)
P28V6 (Neg) x 38
x 37 P28V6 (Pos)
x 39
x 40
x 41
x 42
x 43
x 44
x 45
x 46
x 47
x 48
x
TTPWG1B Board with Wiring and Cabling
447
TTPWH1A
Three 28 V dc supplies are wired from I/O racks R, S, and T to plugs P1, P2, and P3.
The power monitoring signals are wired to the top terminal block (TB1) and go to an
analog input board. The secondary voltage outputs are wired to the lower terminal
block (TB2) as shown in the following figure.
Power Conditioning Board TTPWH1A
28 V power from
racks R, S, T
x
x 1 P1 1 P28R
x 2
x 3 PCOM (Sig) (R)
PCOM (Gnd) x 4 2 PCOM
x 5
x 6
P28R (Gnd) x 8
x 7 P28R (Sig) P2
x 9 1 P28S
x 10 (S)
x 11 P28S (Sig) Monitoring 2 PCOM
P28S (Gnd) x 12
x 13 signals to
x 14
x 15 P28T (Sig) TBAI board P3
P28T (Gnd) x 16 1 P28T
x 17 (T)
x 18 PCOM
x 19 P28V (Sig) 2
P28V (Gnd) x 20
x 21
x 22
x 23
x 24
x
P28V1 (Neg) x 26
x 25 P28V1 (Pos)
x 27 P28V2 (Pos)
P28V2 (Neg) x 28
P28V3 (Neg) x 29 P28V3 (Pos)
x 30
P28V4 (Neg) x 32
x 31 P28V4 (Pos)
x 33 P28V5 (Pos) Power
P28V5 (Neg) x 34
x 35 P28V6 (Pos) outputs
P28V6 (Neg) x 36
P28V7 (Neg) x 38
x 37 P28V7 (Pos)
P28V8 (Neg)
x 39 P28V8 (Pos)
x 40
x 41 P28V9 (Pos)
P28V9 (Neg) x 42
x 43
x 44
x 45
x 46
x 47
x 48
x
TTPWH1A Wiring and Cabling Diagram
GEH-6421M
Operation
TTPWG1B
The turbine ETSV is a 24 V dc device with a 24 watt, 20-22 ohm coil. Power is
supplied from the three I/O rack supplies to TTPWG1B, where the three 28 V
supplies are diode ORed to produce a single 28 V dc output. The primary output is 0
- 2 A (total), 22 - 30 V dc, and there are four secondary outputs of 0.25 A each.
P1 P2 P3
TTPWG1B 2 1 2 1 2 1
Power Supply Monitoring

PCOM
(screw compatible to TBAI)
100k PCOM
Sig 3
PCOM 4 10k
Gnd P28R
P28S
SCOM
100k P28T
Sig 7
P28R 8
Gnd 10k
SCOM 100k
Sig 11
P28S Gnd 12 10k
100k
15 SCOM P28V
Sig
P28T Gnd 16 10k
SCOM 100k
Sig 19
P28V Gnd 20 10k Bus voltage
centering bridge
SCOM 1k 1k
Peripheral Power Outputs

22 - 30 V dc, 2.0 A total SCOM
(+) 25 P28V
P28V1 (-) 26
2.0 A
27 SCOM
(total) P28V2 (+) 28
(-)
1
To TRPL
2
JA1
(+) 31
P28V3 32
(-)
33
0.25 A P28V4 (+) 34
(-)
outputs
(each) (+) 35
P28V5 (-) 36
(+) 37
P28V6 38
(-)
PCOM PCOM
TTPWG1B Board Diagram
449
TTPWH1A
The TTPWH1A power conditioning board provides branch circuit protection and
distribution between one or more Mark VI rack mounted +28 V dc power supplies
and discrete wiring to peripheral devices. The H1A has three 2-pin inputs for +28 V
dc from the Mark VI power supply. It provides diode or selection between the three
inputs to power the +28 V dc outputs. Outputs are rated 22 – 30 V dc, 0 – 0.25 A
individually and capable of parallel operation. There is high frequency isolation
between the inputs and the outputs and the voltage drop is less than +4 V dc when
delivering rated current.
Typical applications power the H1A from the P28C output of the VME rack power
supply. When this is done, the isolation jumper on the rack is placed in the isolated
position removing all connections between the P28C output and the rack. The
TTPWH1A then provides a resistive bridge to ground to center the power circuit
with respect to ground. Voltage feedback monitoring signals are provided using
0.1% resistors allowing monitoring of three input voltages, output voltage, and
voltage between PCOM and SCOM.
Note The TTPWH1A internal signal paths are shown in the figure. Nine current
limited 0.25 A outputs are provided and may be paralleled for higher current
applications.
GEH-6421M
The +28 V dc power source should have an isolated common (return), especially if
the load is external to the cabinet and is grounded. The rack power supplies are wired
through TTPWH1A to the trip board.
P1 P2 P3
2 1 2 1 2 1
TTPWH1A
Power Supply PCOM
Monitoring
3 100k PCOM
PCOM 4 10k
P28R
P28S
SCOM P28T
7 100k
P28R 8
10k
11 SCOM 100k
P28S 12 10k
100k
15 SCOM
P28T 16 10k
19 100k Bus voltage

P28V 20 10k
centering
bridge
SCOM 1k 1k
SCOM
Peripheral
power 25
P28V
26
SCOM
27
22 - 30 V dc 28
0.25 A each
29
30
31
32
33
34
35
36
37
38
39
40
41
42 PCOM
TTPWH1A Board Diagram
Specifications
TTPWH1A Specification
Item Description
Inputs Three 28 V dc inputs from the VME rack power supplies
Outputs Nine current limited outputs of 0.25 A, 22 – 30 V dc, 28 V dc nom.
Monitoring Three 28 V dc inputs
Output 28 V dc power
PCOM voltage
Accuracy Resistors in measuring circuits are 0.1%
451
TTPWG1B Specification
Item Description
Inputs Three 28 V dc inputs from the VME rack power supplies
Outputs Three outputs with total of 2.0 A, 22 – 30 V dc, 28 V dc nom. (to TRPL board)
Four current limited outputs of 0.25 A, 22 – 30 V dc, 28 V dc nom
Monitoring Three 28 V dc inputs
Output 28 V dc power
PCOM voltage
Accuracy Resistors in measuring circuits are 0.1%
Diagnostics
The five monitored voltages are wired to an analog input terminal board, TBAI. The
I/O processor board, VAIC, creates a fault if an input signal goes out of configured
limits, either high or low.
Configuration
There are no switches or jumpers on the power conditioning boards. On the VME
rack power supply, place the P28C isolation jumper in the isolated position.
Alarms
The alarms associated with this board depend on system use of the feedback signals.
GEH-6421M
VME Rack Power Supply
VME Rack Power Supply

The Mark* VI VME rack power supply mounts on the side of the VME control and
interface racks. It supplies +5, ±12, ±15, and ±28 V dc to the VME backplane, and
an optional 335 V dc output for powering flame detectors connected to TRPG.
Two supply input voltage selections are available. There is a 125 V dc input supply
that is powered from a Power Distribution Module (PDM) and a low voltage version
for 24 V dc operation.
Note A different power supply is used on the stand-alone control rack which only
powers the Mark VI controller, VDSK, and VCMI.
453
Volume II VME Rack Power Supply • 491
PSA PSB
POWER
SUPPLY
PULL TO TOGGLE
1 (ON)
SWITCH
0 (OFF)
GREEN LED NORMAL
RED LED FAULT
YELLOW LED AVAILABLE
REV. NO.
GE CAT. NO.
S/N
A82 SP B82 SP C82 SP 533 SP o 521 SP

IS2020LVPSG1
and
IS2020RKPSG1
T AT SSP 82 SP 533 SP o 521 SP

IS2020LVPSG2 -4
and
IS2020RKPSG2-3
VME Rack Power Supply types G1 and G2, Front, Side, and Bottom Views
492 • VME Rack Power Supply 454 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
IS2020RKPSG1 & IS2020LVPSG1
P335VDC 3 2 1 To safety Ground
125/24VDC Input
Control
+
IS2020RKPSG1 On/Off 400 W Output Ret
Power
125V Input Power Supplies
yl ppu S
Suppression switch
Red Fault
PS28C
PS125
+ 3
V521 mor F
P125 2 Suppression
Yellow Avail 2
N125 1 OV Protect 1
+
3 Green Normal
NC PS28A
V533 P
W86. 1
4 UV Detect RKPSG1 335V + 3
ci goL
2
t eR
1
yl ppu S
P24 3 125 or 24V OV Faults
N24 2 Power PS28B
V42 mor F
Enable
1 + 3
2
PS24 1
l ort no C el ban E
P5.0V P12V N12V P15V N15V N28V P28V (A) P28V (B) P28V (C) P28V (D) P28V (E)
75 W x 2 50 W 25 W 50 W 50 W 25 W 50 W 50 W 50 W 50 W 50 W
+ s s Ret + Ret - Ret + Ret - Ret - Ret + Ret + Ret + Ret + Ret + Ret
Suppression Suppression Suppression Suppression Suppression Suppression Suppression Suppression Suppression Suppression
OV Protect OV Protect OV Protect OV Protect OV Protect OV Protect OV Protect OV Protect OV Protect OV Protect
t upnI V42
Suppression
OV Protect
1 GSPVL0202 SI

PSB PSA
24,28,32,20 18,22,26,30 16 14 12 10 8 6 32 30 28 26 24 22 20 18 16 14 12 10 8 6
455
Volume II
of 1016
IS2020RKPSG2 & G3 PSSTAT 1 2 3 4 P335VDC 3 2 1
125V Input Control To safety Ground
+
Power On/Off Ret
yl ppu S
Suppression switch
PS125 Red Fault
following table defines these variations.

V521 mor F
P125 2 Suppression
Yellow Avail
N125 1
1 T AT S
2 T AT S
DN GDI
OV Protect
DI GI S DI
+
3 Green Normal
NC
RKPSG2 & LVPSG4
V533 P
W86. 1
4 UV Detect
335V Option
ci goL
t eR
IS2020RKPSG2- 3 & IS2020RKPSG2- 3
yl ppu S
P24 3
125/24VDC Input
N24 2
V42 mor F
125 or 24V Enable/Status 300/400 W Output RKPSG2 & LVPSG2
1 Power Power Supplies 400W Option
Block Diagram of RKPS and LVPS versions of VME Power Supply

PS24
l ort no C el ban E
P5.0V P12V N12V P15V N15V N28V P28V (A) P28V (B) P28V (C) P28V (D)
150 W 25 W 10 W 100 W 100 W 50 W 100 W 100 W 100 W 100 W
+ s s Ret + Ret - Ret + Ret - Ret - Ret + Ret + Ret + Ret + Ret
IS2020LVPSG2,
G3 & G4 Suppression Suppression Suppression Suppression Suppression Suppression Suppression Suppression
24V Input OV Protect OV Protect OV Protect OV Protect OV Protect Suppression OV Protect OV Protect OV Protect
OV Protect
PS28
Suppression
3
OV Protect 2
variations provide different power supply input and output requirements. The
1
PSB PSA
There are currently seven major variations of the VME rack power supply. These
24,28,32 20 18 22,26,30 16 14 12 10 8 6 32 30 28 26 24 22 20 18 16 14 12 10 8 6
VME Rack Power Supply • 493

VME Rack Power Supply Option Definitions
IS2020 Part Input Output +28V PSA +28V Remote Support Redundant
Number Voltage Rating Outputs Outputs PS335 Output Status ID Output Operation
LVPSG1 24 V dc 400W Qty. 5 Qty. 3 No No No
RKPSG1 125 V dc 400W Qty. 5 Qty. 3 Yes No No
RKPSG2* 125 V dc 400W Qty. 5 Qty. 1 Yes Yes Yes
RKPSG3* 125 V dc 400W Qty. 5 Qty. 1 No Yes Yes
LVPSG2* 24 V dc 400W Qty. 5 Qty. 1 No Yes Yes
LVPSG3* 24 V dc 300W Qty. 3 None No Yes Yes
LVPSG4* 24 V dc 300W Qty. 3 None Yes Yes Yes
* Newer design power supplies
With the exception of the number of remote 28 V outputs, the RKPSG2 and
LVPSG2 are designed to be direct replacements for the RKPSG1 and LVPSG1
respectively. These two supplies have been replaced with the newer designs (marked
with asterisk in the table above).
Installation
The power supply is mounted to the right-hand side of the VME rack on a sheet
metal bracket. The dc input, 28 V dc output, and 335 V dc output connections are at
the bottom. The newer design also has a status connector on the bottom. Two
connectors, PSA and PSB, at the top of the assembly mate with a cable harness
carrying power to the VME rack.
Each of the five 28 V dc power modules supplies a section of the VME rack. These
sections are labeled A, B, C, D, E, and F. The P28C output or PS28 at the bottom of
the power supply can be used to power an external peripheral device. To do this the
jumper plug shown on the bracket to the left of the rack must be moved from the
Normal position to the Isolated position below.
The fan is only used when the controller is mounted in the rack. It is powered from
the top connector on the same bracket, located on the left side of the rack.
GEH-6421M
To prevent electric shock, turn off power to the RPSM to be
replaced, then test to verify that no power exists on the module
before touching it or any connected circuits.
To prevent equipment damage, do not remove, insert, or

adjust any connections while power is applied to the
equipment.
Power cables to
VME chassis
5 slots - A 4 slots - B 4 slots - C 4 slots - D 4 slots - E
Fan
+24 V x x x x x x x x x x x x x x x x x x x PSA
to fan, used PSB
with controller Power
Supply
Plug position
P28 normal
Plug position
P28 isolated
VME chassis,
21 slots for I/O
and control, or x x x x x x x x x x x x x x x x x x x x x
for just I/O
J301
Power supply
Testpoints
GND
Rack Ethernet
ID plug 125
V dc
input
from
P28C power to external PDM
peripheral device (move
Cable from
plug from normal to 335 V dc
PDM monitor
isolated position)
Power Supply, VME Chassis, and Cabling to External Devices
457
To remove the power supply
1 Loosen the PSA/PSB bracket captive fastener at the top front of the module.
2 Separate the PSA/PSB bracket assembly from the RPSM.
3 Disconnect the bottom connectors.
4 Loosen the two front sheet metal bracket captive fasteners.
5 Pull the sheet metal bracket/power module assembly forward, disconnect the
four rear side connectors and then slide the assembly off of the control rack.
6 Remove the four mounting screws that hold the RPSM to the bracket and
remove it.
Note Reinstall the screws and bracket on the control rack if a replacement
module is not going to be installed.
To install the power supply
1 Locate the supply mounting sheet metal bracket and four mounting screws.
2 Position the module on the bracket with the front of the module at the captive
fasteners, then install the four mounting screws and tighten.
3 Slide the module bracket assembly on to the control rack, connect the four rear
side connectors and then push the assembly in to tighten the two front captive
fasteners.
4 Slide the PSA/PSB assembly rear tab into the slot on the bracket located at the
top rear of the RPSM.
5 Push the connector assemble into the mating connectors on the top of the RPSM.
6 Tighten the PSA/PSB bracket captive fastener.
7 Connect the power supply bottom connectors.
GEH-6421M
PIN32 5V
23
PIN30 5V RET
03
PIN28 5V
82
PIN26 5V RET
62
PIN24 5V 42
PIN22 5V RET 22
PSB
PIN20 5V 02
PIN18 5V RET 81
PIN16 +12V 61
PIN14 RET 41
PIN12 -12V 21
PIN10 RET 01
PIN8 +15V 8
PIN6 RET 6
PIN4 N/C 4
PIN2 N/C
PIN32 -15V 23
PIN30 RET 03
PIN28 -28V 82
PIN26 RET 62
PIN24 28VA 42
PIN22 RET 22
PIN20 28VB
PSA
02
PIN18 RET 81
PIN16 28VC 61
PIN14 RET 41
PIN12 28VD 21
PIN10 RET 01
PIN8 28VE 8
PIN6 RET 6
PIN4 N/C 4
PIN2 N/C
Power Supply, Top Connectors
459
IS2020LVPSG1 IS2020LVPSG2 - 4
and and
IS2020RKPSG1 IS2020RKPSG2 - 3
PS24
GND
RETURN
CIRCUIT
PS125 or PS24
PS125 or PS24
+24VDC
NO.1
PS125
RETURN
+125VDC
N/C
CIRCUIT
GND
NO.1
PS335
PS335
PS335
RETURN
GND
+335VDC
CIRCUIT
NO.1
PS28C
PS28 &
PS28
PS28A-C
RETURN
GND
+28VDC
CIRCUIT
NO.1
PS28B
STAT2
IDGND
NO.4
NO.2
PSSTAT
PSSTAT
PS28A
STAT1
IDSIG
NO.3
NO.1
WITH STAR WASHER

1/4 X 20 STUD
AND TWO (2)

JAM NUTS
Power Supply, Bottom Connectors
GEH-6421M
Operation
The VME Rack power supply has only one user control, the power switch, and three
status LED indicators. The power switch provides front-panel control of the power
supply output voltages and when toggled serves as a fault reset. The yellow, red and
green LEDs indicate the status of the input power, fault presence, and normal
operation.
Note Newer supply designs also have a status output that mimics the status of the
green LED and an ID output that uniquely identifies the supply back to the system.
Power Switch
The front panel power switch is a locking type that must be pulled out to change
position. This switch is a low voltage control to enable or disable the output voltages.
If the red LED is ON indicating a fault condition the power switch can be toggled
OFF and then back ON again to clear the fault. The fault will only be cleared if the
condition that caused it no longer exists.
Yellow LED
When the power switch is OFF the yellow LED will indicate the status of the input
power. If this LED is ON there is power present on the supply input connector. For
the newer design, the yellow LED will only turn ON if the input voltage is above the
input under-voltage fault threshold.
Red LED
This LED will only be ON if there is input power, the power switch is ON, and a
fault has been detected.
Green LED/Status Output
If there is input power, the power switch is ON, and there are no detectable faults,
the Green LED will be ON. The newer designs also have a status output that mimics
the status of this LED. The status output is a NO solid-state relay contact that will be
CLOSED when the green LED is ON.
Fault Conditions
There are three classes of power supply faults:
• Those that transiently shutdown an output

• Those that require some reset action to clear
• Permanent failures that require the replacement of the supply.
This section describes the first two fault classes and assumes the cause of the fault is
external. For a detailed fault diagnostics, refer to the section, Diagnostics and
Troubleshooting.
Note When the external condition causing the current limit condition is corrected,
the output voltage will return to normal.
461
If an overcurrent condition exists on an output, the voltage on that output will fold
back as required to maintain the constant current limit output. For every output other
than the 5 V supply, this condition is not detectable at the supply and the green LED
will remain ON. Detection of a low output voltage due to excessive output current
has to be detected at the system level through the power supply voltage monitoring.
The newer design also has an over temperature monitor of the output modules and a
current limit detector on the optional 335V supply. These additional fault detectors
may cause the red LED to come on when an output is in current limit but the red
LED will also go out when the output voltage returns to normal.
The 5 V current limit is a special case due to the 5 V under-voltage detector. If the
current limit causes the 5 V output voltage to fold back below the UV threshold, all
of the other outputs will be disabled until the 5 V output voltage returns to a voltage
above the UV threshold.
All of the other faults will shut down one or all of the outputs until the external cause
of the fault condition is removed and the supply is reset. A reset can be initiated
through the front panel power switch or by removing and reapplying input power to
the supply. Output over-voltage faults on the newer design require the removal of
input power for a minimum of one minute to reset the fault once the source of the
fault has been removed. Below is a power supply fault summary.
• Input under-voltage (Latched)

• Input over-voltage (Newer Design Only)
• P5 output under-voltage
• Output over-voltage (Latched)
• Over temperature (Newer Design Only)
GEH-6421M
The following figure shows the power supply connections to the VME rack and the
distribution of the power supply outputs.
* PS28 or PS28C Configuration:
Note: The power supply PS28 or PS28C may be

isolated from the I/O rack for external use. One plug,
two positions Normal (PL2), Isolation (PS3), for
selection; Plug is located on left side of rack (from the
front). P28A and P28B are for internal cabinet use only,
Input power
notto go outside of the cabinet.

Power Supply
PS335 PS28A PS28B *PS28 or
PS125 or *PS28C
PS24 Remote
28V
IS2020RKPSG1 - 3 or IS2020LVPSG1 - 4
To safety ground
PSB PSA
24,28,32,20 18,22,26,30 16 14 12 10 8 6 32 30 28 26 24 22 20 18 16 14 12 10 8 6
P28D
P28C
P28A
P28B
P28E
N15
N28
Ret
Ret
Ret
Ret
Ret
Ret
Ret
N12
P12
P15
P5
P5
P5
P5
Ret
Ret
Ret
Ret
Ret
Ret
Ret
VME Rack
P5 P5
P28A DCOM DCOM
1
Fan P12 P12
2
Power N12 N12
PL1 PCOM
s
1 P15 P15
*PS28C 2
"Normal" 3 s
ACOM ACOM
4 PL2
21 Slot Only
s
1 N15 N15
*PS28C 2
s
"Isolation" 3
4
PL3
PL2
Test Pts
P15 N15
PL3
ACOM P28AA
P28BB
P28CC s s s s s s
P28DD
P28A P28B P28C P28D P28E
P28EE
PCOM
N28
DCOM s s s s s s
SCOM PCOM PCOM
N28 N28
SCOM SCOM
J5
Ether IO
Slots 1 thru 5 Slots 6 thru 9 Slots 10 thru 13 Slots 14 thru 17 Slots 18 thru 21
SCOM
I/O 21 slot rack only
The symbol, s represents a "pi" suppression filter: Note: SCOM must be connected to ground via therack
scom mounting hardware, metal to metal conductivity, to the
mounting base and hence to ground.
VME I/O Rack Power Supply and Cables
463
Specifications
Item Description
Input voltage
125 V input 70 V to 145 V dc floating supply Up to 10 V pp ripple
24 V input 18.5 V to 32 V dc floating supply Up to 2 V pp ripple
Input under-voltage Under-voltage protection provided to prevent supply operation when the input voltage is
below the minimum operating level.
Input over-voltage* Over-voltage protection provided to prevent supply operation when the input voltage is
above the maximum operating level.
Isolation True isolation from input to output, 1500 V
Output voltages Output Voltage Voltage Regulation Capacity Typical Over
Voltage
For the RKPSG1 and P5 +5 V dc Less than ± 3% 150 W 120% ± 5%
LVPSG1 supplies P15 +15 V dcLess than ± 3% 50 W 120% ± 5%
N15 -15 V dc Less than ± 3% 50 W 120% ± 5%
P12 +12 V dcLess than ± 3% 50 W 120% ± 5%
N12 -12 V dc Less than ± 3% 25 W 120% ± 5%
P28 +28 V dcLess than ± 5% 50 W 120% ± 5%
N28 -28 V dc Less than ± 5% 25 W 120% ± 5%
P335 +335 V dc Less than ± 5% 1.68 W 110% to 120%
For the RKPSG2 -3 P5 +5 V dc Less than ± 3% 150 W 130% ± 5%
and LVPSG2 - 4 P15 +15.35 V dc Less than ± 3% 100 W 120% ± 5%
supplies*
N15 -15.35 V dc Less than ± 3% 100 W 120% ± 5%
Note: P5 on these
supplies has remote P12 +12.3 V dc Less than ± 3% 25 W 120% ± 5%
voltage sensing. N12 -12.3 V dc Less than ± 3% 10 W 120% ± 5%
P28 +28 V dcLess than ± 5% 100 W 120% ± 5%
N28 -28 V dc Less than ± 5% 50 W 120% ± 5%
P335 +335 V dc Less than ± 5% 1.68 W 110% to 120%
Power sequencing The 5 V dc supply comes up first, then all the others
Total Output Maximum of 400 W
Total output LVPSG3 Maximum of 300 W
& 4 only*
Short circuit Short circuit protection on all power supplies, with self-recovery.
Note: A 5 V short circuit on the new design will cause a latched fault.
Temperature Ambient air convection cooling 0 to 60ºC
Indicating lights Green: Normal Status is OK
Red: Fault Power is applied, but one or more outputs off due to a fault.
Yellow: Available Power is applied, but switch is OFF
Status output* NO SSR contact .5 A @ 55 V dc - Closed when the green indicating light is on
ID tag output* Dallas DS2502 output. 2502 data = Week and year tested, unit number, part number
and revision
*Only pertain to the newer design power supplies
GEH-6421M
Diagnostics
Incoming and outgoing voltages and currents are monitored for control and
protection purposes. If the red LED is ON, this is not a direct indication that the
power supply has failed and has to be replaced. The LED ON could indicate that
something is wrong in the system and the fault LED is latched on. The following is
a description of the power supply parameters that are monitored and the conditions
that can cause faults.
Input Under-voltage (below the minimum operating voltage)
The input voltage has to be above the under-voltage threshold or operation of the
supply will be inhibited. For the newer design this is indicated by no LEDs ON. The
red LED will come ON and remain on until the input voltage is above the under-
voltage threshold and the power switch is toggled. If an under-voltage fault occurs
during normal operation, the outputs will be disabled and the red LED will come ON
and remain ON until the input voltage is above the under-voltage threshold and the
power switch is toggled.
Note If the supply power switch is turned on in this condition there will be no output
voltages.
Input Over-voltage (newer design above maximum operating voltage)
If the supply power switch is turned on in this condition there, will be no output
voltages and the red LED will come ON and remain on until the input voltage is
below the over-voltage threshold and the power switch is toggled. If an over-voltage
fault occurs during normal operation, the outputs will be disabled and the red LED
will come ON and remain ON until the input voltage is below the over voltage
threshold and the power switch is toggled.
Note The input voltage has to be below the over-voltage threshold or operation of
the supply will be inhibited and the yellow LED will be ON.
5 V Output Under-voltage (typically below 4.7 V)
The P5 output voltage has to be above the under-voltage threshold or operation of

the supply will be inhibited, all supply outputs will be turned off, and the red LED
will be ON. If an under-voltage fault occurs during normal operation, the outputs
will be disabled and the red LED will come ON and remain ON until the output
voltage is above the under-voltage threshold.
5 V Output Over-voltage (typically above 6 V)
The P5 output voltage has to be below the over-voltage threshold or operation of the
supply will be inhibited. All supply outputs will be latched OFF and the red LED
will be ON until the power switch is toggled. For the newer design, this fault must be
reset by removing input power to the supply (wait for one minute and re-apply input
power).
Output Over-voltage other than P5 (typically above 120%)
The output voltage has to be below the over-voltage threshold or operation of the
supply output that is above the threshold will be inhibited (latched OFF) until the
power switch is toggled. The red LED will be ON during this fault. For the newer
design, this fault must be reset by removing input power to the supply (wait for one
minute and re-apply input power).
465
Output Over-temperature (newer design typically above 100 degrees C)
The modules that supply the output voltage have to be operated below the over-
temperature threshold. A specific supply output module operated above the threshold
will be inhibited until the temperature is lowered below the threshold. The red LED
will be ON during this fault. An over-temperature of the 5 V module will cause a 5
V under-voltage fault.
Troubleshooting
The supply has no field serviceable components. If a supply is found to be defective

it must be replaced. The power supply cover should not be removed in the field.
There are only two indications of a problem on the power supply itself. A problem is
indicated when there are no LEDs ON or the red LED is ON. Both conditions will be
annunciated on the newer designs through the status output.
No LEDs ON is a good indication of an input voltage problem or a defective supply.

If the red LED is ON, the cause could be any of the fault conditions listed above or a
defective supply. Below is a list of troubleshooting hints.
Note Over-voltage faults on the newer design must be reset by removing input
power to the supply, waiting for one minute, and re-applying input power.
No LEDs ON
Verify that the input connector and voltage to the supply are correct. If they are, then
replace the supply. Use caution when powering on the replacement supply because
the failure could have been caused by a problem in the system.
Red LED ON and system up
This condition indicates that the 5 V power is OK. Use the system diagnostics and or
testpoints on the left bottom of the control rack or at the supply connectors to find
the faulted outputs. Try and clear the fault with the input power or switch reset. If the
green LED comes ON, the fault was a transient one and may come back. If the red
LED is still ON, remove the connector supplying the faulted output and reset the
supply. If the red LED is still ON, then a defective supply is the most probable cause.
If the green LED comes ON, then the problem is most likely in the system.
Red LED ON and system down
This condition indicates that the 5 V power is not OK. In this case, all of the supply
outputs should be off. Try and reset the fault with the input power. If the green LED
comes on the fault was a transient one and may come back. If the red LED is still
ON, remove the PSA/PSB output connector at the top of the supply and reset the
supply. If the red LED is still ON, then a defective supply is the most probable cause.
If the green LED comes ON, then the problem is most likely in the system.
Green LED ON and system up but one or more of the voltages out of
specification
This condition indicates that the 5 V power is OK. Each supply output has a current
limit and short circuit protection. This condition could be caused by a short or failed
component in the system. Remove the connector supplying the failed output voltage.
If the voltage returns to normal this is an indication of a system problem. If the
voltage does not return to normal then the most probable cause is a defective supply.
GEH-6421M
Thermal over-temperature faults (new design only)
Even in the worst case ambient conditions, a thermal fault should not occur if the
outputs are not overloaded. A sustained current limit on a supply output will be the
most likely cause of a thermal fault.
Configuration
The P28C output or PS28 at the bottom of the power supply can be used to power an
external peripheral device. To do this the jumper plug on the bracket to the left of the
rack must be moved from the Normal position to the Isolated position below.
Alarms
32 P5=###.## Volts is Outside of Limits. The P5 A VME rack backplane wiring problem and/or power supply
power supply is out of the specified operating problem
limits
33 P15=###.## Volts is Outside of Limits. The If "Remote Control", disable diagnostic and ignore; otherwise
P15 power supply is out of the specified probably a back plane wiring or VME power supply problem
operating limits
34 N15=###.## Volts is Outside of Limits. The If "Remote Control", disable diagnostic and ignore; otherwise
N15 power supply is out of the specified probably a VME backplane wiring and/or power supply problem
operating limits
35 P12=###.## Volts is Outside of Limits. The If "Remote I/O", disable diagnostic and ignore; otherwise
P12 power supply is out of the specified probably a VME backplane wiring and/or power supply problem
operating limits
36 N12=###.## Volts is Outside of Limits. The If "Remote I/O", disable diagnostic and ignore; otherwise
N12 power supply is out of the specified probably a VME backplane wiring and/or power supply problem
operating limits
37 P28A=###.## Volts is Outside of Limits. The If "Remote Control", disable diagnostic and ignore; otherwise
P28A power supply is out of the specified probably a VME backplane wiring and/or power supply problem
operating limits
38 P28B=###.## Volts is Outside of Limits. The If "Remote Control", disable diagnostic and ignore; otherwise
P28B power supply is out of the specified probably a VME backplane wiring and/or power supply problem
operating limits
39 P28C=###.## Volts is Outside of Limits. The If "Remote Control" disable diagnostic. Disable diagnostic if not
P28C power supply is out of the specified used; otherwise probably a backplane wiring and/or power supply
operating limits problem
40 P28D=###.## Volts is Outside of Limits. The If "Remote Control" disable diagnostic. Disable diagnostic if not
P28D power supply is out of the specified used; otherwise probably a backplane wiring and/or power supply
41 P28E=###.## Volts is Outside of Limits. The If "Remote Control" disable diagnostic. Disable diagnostic if not
P28E power supply is out of the specified used; otherwise probably a backplane wiring and/or power supply
42 N28=###.## Volts is Outside of Limits. The If "Remote Control" disable diagnostic. Disable diagnostic if not
N28 power supply is out of the specified used; otherwise probably a backplane wiring and/or power supply
467
Notes
468 of 1016
VME Redundant Power Supply
Redundant Power Supply

The redundant power supply module (RPSM) parallels two independent power
supplies to provide ten output voltages with improved reliability. ORing diodes are
used to OR the outputs of one supply with the outputs from the second redundant
supply. Nine of the paralleling circuits have an additional current limit function. All
output circuits have an LED status indicator.
The following figure shows the power and signal flow for two paralleled power
supplies that provide power to a Mark* VI control rack. To provide redundancy, the
outputs of each supply are passed into the RPSM, ORed and the redundant voltages
are passed out the RPSM outputs. The RPSM module mounts on the side of the
control rack in place of the power supply. The two power supplies that feed the
RPSM are remotely mounted.
PSSTAT
Power Supply PSA
1
PSB
1PSSTAT
1PSA
PSA
1PSB
PSB MarkVI rack

RPSM
connections
2PSA
2PSB PSSTAT
PS28
PSA
2PSSTAT
Power Supply PSB
2
PSSTAT
Power Supply and RPSM Signal Flow
469
Volume II VME Redundant Power Supply • 507
Installation
Top View
PSA PSB
Captive
fastener
Mounting Mounting 3 1
1PSB
screw screw
15 13
3 1
2PSB
IS2020RPSM
15 13
Status
LEDs
3 1
1PSA
15 13
3 1
1PSSTAT PSSTAT 15 2PSA 13
2PSSTAT PS28
Mounting
screw Slide Mounting
mounting screw
Captive plate
fastener
Side View
Control
rack
RPSM Module and VME Chassis
The RPSM module is mounted to the right hand side of the VME rack on a sheet
metal bracket. The status and 28 V dc output connections are at the bottom. Two
connectors, PSA and PSB, at the top of the assembly connect with a cable harness
carrying power to the VME rack. The four 15-pin connect-N-Lock connectors at the
back side of the module are the primary power feeds from the remotely mounted
power supplies.
508 • VME Redundant Power Supply 470 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
To prevent electric shock, turn off power to the RPSM to be
replaced, then test to verify that no power exists on the module
before touching it or any connected circuits.
To prevent equipment damage, do not remove, insert, or

adjust any connections while power is applied to the
equipment.
The RPSM module is mounted to the right hand side of the VME rack on a sheet
metal bracket. The status and 28 V dc output connections are at the bottom. Two
connectors, PSA and PSB, at the top of the assembly connect with a cable harness
carrying power to the VME rack. The four 15-pin connect-N-Lock connectors at the
back side of the module are the primary power feeds from the remotely mounted
power supplies.
To remove the RPSM

1 Loosen the PSA/PSB bracket captive fastener at the top front of the module.
2 Separate the PSA/PSB bracket assembly from the RPSM.
3 Disconnect the bottom connectors.
4 Loosen the two front sheet metal bracket captive fasteners.
5 Pull the sheet metal bracket/power module assembly forward, disconnect the
four rear side connectors and then slide the assembly off of the control rack.
6 Remove the four mounting screws that hold the RPSM to the bracket and
remove it.
Note Reinstall the screws and bracket on the control rack if a replacement
module is not going to be installed.
To reinstall the RPSM

1 Locate the supply mounting sheet metal bracket and four mounting screws.
2 Position the module on the bracket with the front of the module at the captive
fasteners, then install the four mounting screws and tighten.
3 Slide the module bracket assembly on to the control rack, connect the four rear
side connectors and then push the assembly in to tighten the two front captive
fasteners.
4 Slide the PSA/PSB assembly rear tab into the slot on the bracket located at the
top rear of the RPSM.
5 Push the connector assemble into the mating connectors on the top of the RPSM.
6 Tighten the PSA/PSB bracket captive fastener.
7 Connect the power supply bottom connectors.
471
PIN32 5V
23
PIN30 5V RET
03
PIN28 5V
82
PIN26 5V RET
62
PIN24 5V 42
PIN22 5V RET 22
PSB
PIN20 5V 02
PIN18 5V RET 81
PIN16 +12V 61
PIN14 RET 41
PIN12 -12V 21
PIN10 RET 01
PIN8 +15V 8
PIN6 RET 6
PIN4 N/C 4
PIN2 N/C
PIN32 -15V 23
PIN30 RET 03
PIN28 -28V 82
PIN26 RET 62
PIN24 28VA 42
PIN22 RET 22
PIN20 28VB
PSA
02
PIN18 RET 81
PIN16 28VC 61
PIN14 RET 41
PIN12 28VD 21
PIN10 RET 01
PIN8 28VE 8
PIN6 RET 6
PIN4 N/C 4
PIN2 N/C
RPSM Top Connectors
GEH-6421M
1 & 2PSB
Pin
13 15 1 P5V1/2
2 P5V1/2
1PSB
3 P5V1/2
4 P5RTN
5 P5RTN
6 P5RTN
1 3
7 NC
8 P5SENP
9 P5SENN
13 15 10 P15V1/2
11 N12
2PSB 12 P12V1/2
13 P15RTN
14 N12RTN1/2
1 3 15 P12RTN
1 & 2PSA
Pin
3 1
1 P28AB1/2
1PSA
2 N28
3 N15
4 AB28RTN
5 N28RTN1/2
15 13 6 N15RTN1/2
7 NC
8 P28AB1/2
3 1 9 AB28RTN
10 P28E1/2
2PSA
11 P28D1/2
12 P28C1/2
13 E28RTN
15 13 14 D28RTN
15 C28RTN
RPSM Back Side Connectors
473
PS28
Pin
1 P28E
2 CHASS
1
3 E28RTN
PS28
3
PSSTAT
Pin
1 IDSIG
4 IDGND
2 1STAT1
1
4
5 1STAT2
PSSTAT
3 2STAT1
6 2STAT2
3
6
2PSSTAT
Pin
1 IDSIG
2 IDGND
2PSSTAT
3 2STAT1
3
1
4 2STAT2
3 4
1 2
1PSSTAT
1PSSTAT
Pin
1 IDSIG
4
2
2 IDGND
3 1STAT1
4 1STAT2
RPSM Bottom Connectors
GEH-6421M
Operation
1
1PSSTAT 2
3
RPSA
4
ID 1
4
2 PSSTAT
1 5
2 3
2PSSTAT 3 6
4
1PSA 1 4 8 9 12 15 11 14 10 13
2PSA 1 4 8 9 12 15 11 14 10 13
P28V (B) ECB

ECB ECB ECB
3
P28V (A) P28V (C) P28V (D) P28V (E) 2 PS28
100 W 100 W 100 W 100 W 1
+ Ret + Ret + Ret + Ret
PSA 24 22 20 18 16 14 12 10 8 6
1PSA 1PSB
5 2 6 3 10 13 14 11 12 15 1, 2, 3 8 9 4, 5, 6
2PSB
2PSA 5 2 6 3 10 13 14 11 12 15 1, 2, 3 8 9 4, 5, 6
+s -s
ECB ECB ECB ECB ECB

P5V
N28V N15V P15V N12V P12V 150 W
50 W 100 W 100 W 10 W 25 W
Ret – Ret – + Ret Ret – + Ret + Ret
PSA 26 28 30 32 8 6 10 12 16 14 20,24,28,32 18,22,26,30
PSB
RPSM Block Diagram
475
Output Voltage ORing
The ten outputs of two supplies are ORed together using low forward drop Schottky
diodes. If an output of one of the supplies fails, the corresponding output on the other
supply will pick up the full load through the diode. It is not intended that the two
supplies equally share the load current, but if a short occurs on a RPSM output, it is
possible to supply twice the normal short circuit current to the load. To prevent this,
all of the outputs of the ORing diodes, with the exception of the 5 V, have an
additional current limit circuit.
Note These circuits will hold the short circuit current to an acceptable level.
Refer to the Specifications section for expected RPSM output voltages accounting
for the voltage losses introduced by passing the supply outputs through the ORing
circuits. Due to the wiring impedance between the supply outputs and the RPSM,
the supplies will tend to share the load. The sharing will reduce the diode and
conductor losses so the expected losses for normal operations will be less than with
one supply faulted.
Current Limit ECB
Nine of the outputs have electronic circuit breakers (ECBs) to limit the short circuit
current. These circuit breakers are of the auto-reset type. Once the supplied output
current exceeds the over-current threshold the output will be turned OFF and the
reset timer started. Once the reset timer has expired the output will be turned back
ON. If the over-current condition still exists, the output will be turned OFF and the
reset timer started again. This cycle will continue until the short is removed. The
output will then return to normal operation.
Note No current limiting is provided on the RPSM module for the 5 V output.
RPSM Electronic Circuit Breaker Limits
Parameter Min. Typical Max. Units

Reset Time 500 msec
±12 OC Threshold 2.78 3.3 3.89 Amps
±15 OC Threshold 8.30 10 11.70 Amps
±28 OC Threshold 4.15 5 5.85 Amps
Indicator LEDs
All the RPSM supply outputs have green status LEDs to indicate that power is being
supplied to the load. The LEDs are located on the front panel of the module. For
normal operations these LEDs will be ON solid. If the RPSM is not supplying the
correct power to the load, one or more of these LEDs are OFF or flashing.
Note A flashing LED indicates that the output ECB is tripped
GEH-6421M
LED Definitions
LED Description
P5 P5 output voltage indicator
N12 N12 output voltage indicator
P28AB P28A/B output voltage indicator
P28C P28C output voltage indicator
P28D P28D output voltage indicator
P28E P28E output voltage indicator
Specification
Item Description
Output Voltage Conditions Minimum Typical Maximum Units
+5 V 20 - 30 A 4.90 5.05 5.20 V dc
±12 V 0.1 - 1.6 A 11.64 12.0 12.72 V dc
±15 V 0.1 - 5.3 A 14.55 15.0 15.97 V dc
±28 V 0.2 - 3.2 A 26.6 28.0 29.4 V dc
Outputs P28V (A), P28V (B), P28V (C), P28V (D), P28V (E), all with 100 W capability
PS28 External 28 V output, from P28 (E)
N28V 50 W
N15V 100 W
P15V 100 W
N12V 10 W
P12V 25 W
P5V 150 W
477
Diagnostics
Below is a list of fault indications and the possible causes.
All RPSM green LEDs OFF - This is an indication of a problem back at the
power supplies and not an RPSM failure.
One or more RPSM green LEDs OFF (but not all) - An RPSM LED OFF
condition is an indication that there is no output voltage due to a short in the control
rack or an RPSM failure.
5 V output problems - The 5 V output is unique from all of the other outputs.
This RPSM output does not have current limit protection and has remote voltage
sensing from the power supplies to the RPSM module. With a 5 V transient short or
problem in the system, the most likely failure mode will be a 5 V output over-voltage
fault back at the power supplies. Under high currents the losses will become high
enough to cause the voltage at the power supplies to exceed the over-voltage
threshold. Refer to the 5 V paragraph in GEI-100567 VME Power Supply for
details. Any time the RPSM P5 green LED is on, the RPSM 5 V output voltage is
above 4.55 V.
Redundant power supply replacement - As long as one of the power supplies

is fully operational, the RPSM green LEDs will be ON and the correct power will be
supplied to the system. When one of the power supplies fails, replacement can be
postponed until it is convenient to do so. Before replacing the supply, refer to the
troubleshooting guidelines outlined in GEI-100567 VME Power Supply to rule out a
transient fault that can be reset such as an input power under-voltage. If the supply is
found to be defective, follow removal and installation procedure outlined in the
Power Supply section.
Parallel Status/ID
Each status connector from the power supplies has a status and ID signal. The ID
signals from the two supplies are wired together along with the ID signal from the
RPSM and passed out through the PSSTAT connector. The ID signal output is a
single wire LAN line with three DALLAS 2502 ID ICs connected on it. The NO
SSR contact status signals from the both supplies are passed through the RPSM and
out the PSSTAT connector.
Power Supply 1 and 2 Status SSR NO Contacts
Parameter Conditions Min. Max. Units

V dc rating 55 V dc
V ac rating 55 V peak
Current rating 500 mA
ON resistance 1.0 Ohm
Isolation 1500 V dc
There are no field serviceable components in the RPSM module. If one or more of
the green front panel LEDs are OFF, this is not a direct indication that the RPSM
module has failed and has to be replaced. An LED OFF could indicate that
something is wrong in the system and the fault is not due to the RPSM module.
Configuration
GEH-6421M
Power Distribution Modules
PDM Power Distribution Modules

The Power Distribution Modules (PDM) provides 125 V dc and 115 V ac (or 230 V
ac) to the Mark* VI system for all racks and terminal boards. There is a second
version of the PDM for the control cabinet in those systems using remote I/O
cabinets.
Diagnostics to
VCMI through J301
in <R> rack
Power cables to
interface modules
125 V dc, 115/230 V ac
DIN-rail
termination
Output power board
connectors
Power Distribution Module

(for interface modules)
TB2 TB1
Power
TB3 Input filters
terminals Filtered dc
and ac power
to PDM
JTX1 AC/DC
115 V Converter
Cable to
Cable to PDM JZ2
transformer or JZ3
inside ac/dc JTX2
JZ
converter 230 V
TB1
Customer's power TB2

cables, 125 V dc
One or two converters and 115/230 V ac
Power Distribution Module, Ac to Dc Converter, and Diagnostic Cabling
479
Volume II Power Distribution Modules • 517
Installation
The cabling, wiring connections, and fuse locations for the PDM in the interface
cabinet are shown in the figure.
PDM Cable Destination
JPD Diagnostic term. brd.

JZ2 Ac/dc convert #1
JZ3 Ac/dc convert #2
JZ1 Cable to door resis.
J1R <R> power supply

J2R <R> power supply
J1S <S> power supply
J2S <S> power supply
J1T <T> power supply
J2T <T> power supply
J1C Spare
J1D Spare
J7X <X> power supply

J7Y <Y> power supply
J7Z <Z> power supply
J7A TRPG#1
J7W TREG
J8A TRLY
J8B TRLY
JZ1 J8C TRLY
J8D TRLY
J12A TBCI
Ground reference J12B TBCI
jumper BJS J12C TBCI
J15 Miscellaneous
J16 Miscellaneous
J17 TRLY
J18 TRLY
J19 TRLY
J20 TRLY
Note : When connecting ac power

to the power distribution (TB1),verify 125 V dc supply
that JTX connector on both ac
source selectors (see Ac/dc 120 V ac supply
converter) are plugged into JTX1 for
115 V ac, or JTX2 for 230 V ac. Auxiliary 120
V ac supply
Interface Cabinet PDM Circuit Board
518 • Power Distribution Modules 480 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Fuses in Interface and Control Cabinet PDM
Values of the fuses for the PDM interface cabinet are shown in the following table.
Interface Cabinet PDM Fuse Ratings
Current Voltage
PDM Fuse* J Connector Rating Rating Vendor Catalog No.
No.
FU1-FU6 J1R, S, T 15 A 125 V ®
Bussmann GMA-15A
FU7-FU10 J1C, D 5A 125 V Bussmann GMA-5A
FU13-FU20 J8A, B, C, D 15 A 125 V Bussmann GMA-15A
FU21-FU26** J12A, B, C 1.5 A 125 V Bussmann GMC-1.5A
FU27-FU28*** J15, 16 3.2 A 250 V Bussmann MDL-3.2A
FU29 J17 15 A 250 V Bussmann ABC-15A
FU30 J18 5A 250 V Bussmann ABC-5A
FU31-FU32 J19, 20 15 A 250 V Bussmann ABC-15A
FU34-FU39 J7X, Y, Z 5A 125 V Bussmann GMA-5A
*All fuses are ferrule type 5 mm x 20 mm, except for FU27-FU32 which are 0.25" x 1.25 ".
**The short circuit rating for FU21-FU26 is 100 A
***The short circuit rating for FU27-FU28 is 70 A
The PDM in the control cabinet (IS2020CCPD) does not supply power to any
terminal boards except the TRLY boards. Values for the fuses in the control cabinet
PDM are similar to those in the I/O cabinet PDM, except the rating for fuses FU1-
FU6 is 5 A instead of 15 A.
Operation
The customer's 125 V dc and 115/230 V ac power is brought into the PDM through
power filters. The ac power is cabled out to one or two ac/dc converters which
produce 125 V dc. This dc voltage is then cabled back into the PDM and diode
coupled to the main dc power, forming a redundant power source. This power is
distributed to the VME racks and terminal boards.
Either 115 V ac or 230 V ac can be handled by the ac/dc converters. The transformer
cable must be plugged into either JTX1 for 115 V ac, or JTX2 for 230 V ac
operation.
Diagnostic information is collected in the PDM and wired out to a DIN rail mounted
terminal board. A cable then runs to the VCMI in rack <R> through J301.
Ac feeders, J17-20, are fused and cabled out to the relay terminal boards. 125 V dc
feeders are fused and cabled to the interface (I/O) cabinets, protection modules,
TRPG, TREG, and TRLY. To ensure a noise free supply to the boards, the PDM is
supplied through a control power filter (CPF), which suppresses EMI noise. The CPF
rack holds either two or three Corcom 30 A filter modules as shown in the following
figure.
Power to the contact inputs first passes through resistors R3 and R4, through TB2,
before being fused and cabled to the TBCI boards. Contact inputs operate with 125 V
dc excitation.
481
Control Cabinet PDM
Power requirements for the control cabinet are less than for the interface cabinet. The
PDM has the same layout but different fuse ratings, since only the control racks and
relay output boards require power. For additional noise filtering for the controllers,
Corcom power filters are included with the PDM.
125 V dc Ac 1 Ac 2
+ P125 - N125 115/230 V ac 115/230 V ac
TB2 5 6 3 4 1 2
DCF1 ACF1 ACF2 Power filter board

TB1 5 6 3 4 1 2
TB1 1 2 3 4 5 6 7 8 9 10 11 12
Chassis Chassis
DS2020PDMAG6 DS200TCPD
FU29 Ac feeders
DCLO AC1N
DCHI AC1H AC2H AC2N J17
FU30
JZ4 J18
FU31
For bus P125V JZ5 J19
monitoring FU32 125 V dc
BJS J20 to TREG,
TB3 ACSHI JH1,
P125 VR JZ2 DACA#1
1 Contact
P125S
2 332k inputs
(+1.82V)
JZ3 DACA#2 +
3
10k -
Chassis 4
5 TB3
10k 12 11 10
6
Dc feeders
N125 S 7
SW1
FU1/FU2 J1R
(-1.82V) 8 332k
[J2R
9
[J1S
J2S J1T
N125 VR
FU9/FU10 SW5 [
J1C J2T R1 R2
J1D 22 22
FU13/FU14
J8A ohm ohm
J8B 70 70
JZ1 W W
1
FU19/FU20 J8C
10 J8D
TB2 Door
9 FU34/FU35 SW6
1 2 3 4 6
J7X
FU38/FU39 SW8 J7Y
P125 VR 4 J7Z
N125 VR 7
11 J7A
12
R3 R4 1 J7W P125 V
FU21/FU22 2 N125 V
22 22 Door
J12A
ohm ohm
FU25/FU26 J12B
70 W 70 W 3 J12C
2 + P125 V 3 J15
2
R5, 50 ohm,* 70 W FU28 1
FU27
3.2 3.2 A
A 1
J16
2
R6, 50 ohm,* 70 W 3
Diagnostic info
JPD
*Note: Field configurable
Distribution Module for I/O Cabinet
GEH-6421M
Ac1 Ac2 To safety
125 V dc ground
115/230 115/230
V ac V ac
+P125 - N125 AC1H AC1N AC2H AC2N IS2020CCPD
TB1 1 2 3 4 5 6
Chassis
MOV suppression
In+ Gnd In- In+ Gnd In- In+ Gnd In-
DCF1 ACF1 ACF2
120/250 V, 30 Amp 120/250 V, 30 Amp 120/250 V, 30 Amp Power filters
Out+ Out- Out+ Out- Out+ Out-
DS200TCPD Ac feeders to
AC1H AC1N TRLY boards
DCHI DCLO AC2H AC2N FU29
J17
FU30
P125V JZ4 J18
JZ5 FU31
J19
BJS FU32
J20
DACA#1
ACSHI
DACA#2
JZ2 JZ3
FU1/FU2 SW1 J1R

Dc feeders to
FU3/FU4 SW2 J1S
controller racks
FU5/FU6 SW3 J1T <R0>,<S0>,<T0>
DIN-rail transition terminal board
+ 28 Analog In 1 37- pin
P125 V TB2 P125S (+1.82V)
29 P125_Grd connector
1
332k
2 + 27 Analog In 2
3 26 N125_Grd
10k N125 S
4
(-1.82V) + 7 Analog In 3 Cable to VCMI
5
10k 8 Spare 01 via VDSK on
6 Chassis
+ 5 Analog In 4 One to one front of <R0>
7
8 332k control rack.
6 Spare 02 compatability
9 between screw
N125 V 10 P5V (TB) and 37-pin
connector
9 DCOM numbers.
Diagnostic information JPD 35 DIN1, Logic_In_1
P5V 7 34 DIN2, Logic_In_2
DCOM 8
33 DIN3, Logic_In_3
BAT 1
AC1 2 32 DIN4, Logic_In_4
AC2 3
31 DIN5, Logic_In_5
Spare 4
J19 Fuse31 5 30 DIN6, Logic_In_6
J20 Fuse32 6 16 DIN7, Logic_In_7
J17 Fuse29 9
PDM for Controller Cabinet
483
Ground Fault Detection Sensitivity
Note Ground fault detection is performed by the VCMI using signals from the
PDM.
Ground fault detection on the floating 125 V dc power bus is based upon monitoring
the voltage between the bus and the ground. The bus voltages with respect to ground
are normally balanced (in magnitude), that is the positive bus to ground is equal to
the negative bus to ground. The bus is forced to the balanced condition by the
bridging resistors, Rb (refer to the figure). Bus leakage (or ground fault) from one
side will cause the bus voltages with respect to ground to be unbalanced.
Power Distribution Module
P125 Vdc
Rb Rf Vout,Pos
Monitor1
Jumper Grd Fault
Grd Vout,Neg
Rb Monitor2
N125 Vdc
Electrical Circuit Model
Rb/2
Vbus/2 Vout,
Rf Bus Volts
wrt Ground
Ground Fault on Floating 125 Vdc Power Bus
There is a relationship between the bridge resistors, the fault resistance, the bus
voltage, and the bus to ground voltage (Vout) as follows:
Vout = Vbus*Rf / [2*(Rf + Rb/2)]
Therefore the threshold sensitivity to ground fault resistance is as follows:
Rf = Vout*Rb / (Vbus – 2*Vout).
The ground fault threshold voltage is typically set at 30 V, that is Vout = 30 V. The
bridging resistors are 82 K each. Therefore, from the formula above, the sensitivity
of the control panel to ground faults, assuming it is on one side only, is as shown in
the following table.
Note On Mark V systems, the bridging resistors are 33 K each so different Vout
values result.
GEH-6421M
Sensitivity to Ground Faults
Vbus - Bus Vout - Measured Bus to Rb (Kohms) - bridge Rf (Kohms) -fault

voltage ground voltage (threshold) resistors (balancing) resistor Control System
105 30 82 55 Mark VI
125 30 82 38 Mark VI
140 30 82 31 Mark VI
105 19 82 23 Mark VI
125 19 82 18 Mark VI
140 19 82 15 Mark VI
105 10 82 10 Mark VI
125 10 82 8 Mark VI
140 10 82 7 Mark VI
105 30 33 22 Mark V
125 30 33 15 Mark V
140 30 33 12 Mark V
The results for the case of 125 V dc bus voltage with various fault resistor values is
40.0
30.0 Fault Resistance (Rf) Vs Threshold
Fault, Rf
Voltage (Vout) at 125 V dc on

20.0
Mark VI
10.0
0.0
0 10 20 30
Voltage, Vout
Threshold Voltage as Function of Fault Resistance
Results
On Mark VI, when the voltage threshold is configured to 30 V and the voltage bus is
125 V dc, the fault threshold is 38 Ω. When the voltage threshold is configured to 17
V and the voltage bus is 125 V dc, the fault threshold is 15 Ω.
The sensitivity of the ground fault detection is configurable. Balanced bus leakage
decreases the sensitivity of the detector.
485
Specifications
Item Specification
Number of input sources One 125 Volt battery
One or two 115/230 V ac sources
Control Power filters Dc: One Corcom 30 A filter modules - 120/250 V, 30 A
Ac: One or two Corcom 30 A filter modules - 120/250 V, 30 A
AC to DC converters One or two DACA converters – 115 or 230 V ac
Redundancy The two or three dc sources are diode coupled to form a redundant power source for the I/O
racks
Outputs Two TMR I/O racks, six total
Three VPRO protection modules
One TRPG and one TREG board
Four AC feeders to TRLY boards
Four DC feeders to TRLY boards
Three TBCI boards
Two spare, two miscellaneous outputs
GEH-6421M
Diagnostics
As shown in the following figure, the 125 V dc is reduced by a resistance divider
network to signal level for monitoring. Other items monitored include the battery
voltage, two ac sources, and fuses in the feeders to the relay output boards. In the
interface cabinet this diagnostic data is monitored by the VCMI. In the control
cabinet it is cabled to the VDSK board and then to the VCMI.
DS2020PDMAGx Din Rail Transition

Termination Board
TB3
P125 VR
1 37-pin
332k P125S (+1.82V) connector
2
+ 28 Analog In 1
3
10k 29 P125_Grd
4 Chassis
5 27 Analog In 2
10k
6 + 26 N125_Grd
7 37-wire cable
N125 S (-1.82V)
N125 VR 8 332k +7 Analog In 3
9 8 Spare01
One to one
+5 Analog In 4 Connect to VCMI
compatability
6 Spare02 between via J301, in <Rx>
screw (TB) I/O rack
and 37-pin
10 P5V connector
numbers
9 DCOM
JPD
35 DIN1, Logic_In_1
P5V 34 DIN2, Logic_In_2
7
DCOM
8 33 DIN3, Logic_In_3
BAT
AC1
2
AC2 31 DIN5, Logic_In_5
3
Spare
J19 Fuse31
5
J20 Fuse32 16 DIN7, Logic_In_7
6
J17 Fuse29
9
PDM Diagnostic Monitoring
487
Configuration
Switches
The PDM for the I/O cabinets has a number of jumpers and switches as follows.
Refer to the circuit diagrams for location and function.
Switch Indicator Output Cable Destination

SW1 Yes J1R, J2R <R> Power Supply, 125 V dc
SW2 Yes J1S, J2S <S> Power Supply, 125 V dc
SW3 Yes J1T, J2T <T> Power Supply, 125 V dc
SW4 Yes J1C Spare 125 V dc supply
SW5 Yes J1D Spare 125 V dc supply
SW6 Yes J7X <X> (or R8) Power, 125 V dc supply
SW7 Yes J7Y <Y> (or S8) Power, 125 V dc supply
SW8 Yes J7Z <Z> (or T8) Power, 125 V dc supply
Jumpers
Jumpers are located on TB1, and TB2. Resistors are located on TB3 to reduce the
125 V dc to 1.82 V dc for monitoring the bus.
Ground Reference Jumper
Jumper BJS is supplied for isolation of ground reference on systems with an external
ground reference. The ground reference bridge across the 125 V dc power has two
resistances, one on each side, and BJS connects the center to ground.
Note When more than one PDM is supplied from a common 125 V dc source,
remove all the BJS connections except one.
PDM variables including the ac and dc sources, P125 and N125 voltages, and the
status of fuses 31, 32, and 33, are monitored by the VCMI in <R> rack. Refer to the
VCMI toolbox configuration in GEI-100551, VCMI Bus Master Controller.
Alarms
43 125 Volt Bus = [ ] Volts is Outside of Limits. The 125 A source voltage or cabling problem; disable 125 V
Volt bus voltage is out of the specified operating limits. monitoring if not applicable.
44 125 Volt Bus Ground = [ ] Volts is Outside of Limits. Leakage or a fault to ground causing an unbalance on the
The 125 Volt bus voltage ground is out of the 125 V bus; disable 125 V monitoring if not applicable.
specified operating limits.
GEH-6421M
PPDA Power Distribution System Feedback
The Power Distribution System Feedback (PPDA) pack accepts inputs from up to six
different power distribution boards. It conditions the board feedback signals and
provides a dual redundant Ethernet interface to the controllers. PPDA feedback is
structured to be plug and play uses electronic IDs to determine the power distribution
boards wired into it. This information is then used to populate the IONet output
providing correct feedback from connected boards.
Compatibility
The PPDA I/O pack is hosted by the JPDS or JPDM 28 V dc Control Power boards
on the Mark* VIe Modular Power Distribution (PDM) system. It is compatible with
the feedback signals created by JPDB, JPDE, and JPDF.
Installation
The PPDA I/O pack mounts on either a JPDS or JPDM 28 V dc control power
terminal board.
To install the PPDA pack
1 Securely mount the desired terminal board.

2 Directly plug one PPDA I/O pack for simplex or three PPDA I/O packs for
TMR into the terminal board connectors.
3 Mechanically secure the packs using the threaded studs adjacent to the Ethernet
ports. The studs slide into a mounting bracket specific to the terminal board
type. The bracket location should be adjusted such that there is no right-angle
force applied to the DC-62 pin connector between the pack and the terminal
board. The adjustment should only be required once in the life of the product.
4 Plug in one or two Ethernet cables depending on the system configuration. The
pack will operate over either port. If dual connections are used, the standard
practice is to connect ENET1 to the network associated with the R controller.
5 Apply power to the pack by plugging in the connector on the side of the pack. It
is not necessary to insert this connector with the power removed from the cable
as the I/O pack has inherent soft-start capability that controls current inrush on
power application.
6 Configure the I/O pack as necessary.
7 Connect ribbon cables from connector J2 on JPDS or JPDM to daisy chain other
core boards feeding information to PPDA.
Note Additional PDM feedback signals may be brought into the PPDA I/O pack
through the P2 connector on the host board. The P1 connector is never used on a
board that hosts the PPDA I/O pack, PPDA must always be at the end of the
feedback cable daisy chain.
489
Diagnostics
The PPDA performs the following self-diagnostic tests:
• A power-up self-test including checks of RAM, flash memory, Ethernet ports,

and most of the processor board hardware
• Continuous monitoring of the internal power supplies for correct operation
• A check of the electronic ID information from the terminal board, acquisition
card, and processor card confirming the hardware set matches, followed by a
check confirming the application code loaded from flash memory is correct for
the hardware set
• The analog input hardware includes precision reference voltages in each scan.
Measured values are compared against expected values and are used to confirm
health of the A/D converter circuits.
• Details of the individual diagnostics are available from the ToolboxST*
application. The diagnostic signals are individually latched, and then reset with
Configuration
Variable Description Direction Type
L3DIAG_PPDA_R I/O Diagnostic Indication Input BOOL
L3DIAG_PPDA_S I/O Diagnostic Indication Input BOOL
L3DIAG_PPDA_T I/O Diagnostic Indication Input BOOL
LINK_OK_PPDA_R I/O Link Okay Indication Input BOOL
LINK_OK_PPDA_S I/O Link Okay Indication Input BOOL
LINK_OK_PPDA_T I/O Link Okay Indication Input BOOL
ATTN_PPDA_R I/O Attention Indication Input BOOL
ATTN_PPDA_S I/O Attention Indication Input BOOL
ATTN_PPDA_T I/O Attention Indication Input BOOL
PS18V_PPDA_R I/O 18 V Power Supply Indication Input BOOL
PS18V_PPDA_S I/O 18 V Power Supply Indication Input BOOL
PS18V_PPDA_T I/O 18 V Power Supply Indication Input BOOL
PS28V_PPDA_R I/O 28 V Power Supply Indication Input BOOL
PS28V_PPDA_S I/O 28 V Power Supply Indication Input BOOL
PS28V_PPDA_T I/O 28 V Power Supply Indication Input BOOL
IOPackTmpr_R I/O pack Temperature (deg F) AnalogInput REAL
IOPackTmpr_S I/O pack Temperature (deg F) AnalogInput REAL
IOPackTmpr_T I/O pack Temperature (deg F) AnalogInput REAL
Pbus_R_LED Pbus R is in Regulation Input BOOL
Pbus_S_LED Pbus S is in Regulation Input BOOL
Pbus_T_LED Pbus T is in Regulation Input BOOL
Src_R_LED All R Pbus Sources OK Input BOOL
Src_S_LED All S Pbus Sources OK Input BOOL
Src_T_LED All T Pbus Sources OK Input BOOL
Aux_LED Aux 28 outputs OK Input BOOL
Batt_125V_LED 125 V battery volts OK Input BOOL
Batt_125G_LED 125 V battery floating Input BOOL
JPDD_125D_LED 125 V JPDD feeds OK Input BOOL
Pbus_125P_LED 125 V Pbus feeds OK Input BOOL
GEH-6421M
Variable Description Direction Type
Batt_24V_LED 24 V battery volts OK Input BOOL
Batt_24G_LED 24 V battery floating Input BOOL
JPDD_24D_LED 24 V JPDD feeds OK Input BOOL
Pbus_24P_LED 24 V Pbus feeds OK Input BOOL
AC_Input1_LED Ac input 1 OK Input BOOL
AC_Input2_LED Ac input 2 OK Input BOOL
AC_JPDA_LED Ac JPDA feeds OK Input BOOL
AC_Pbus_LED Ac Pbus feeds OK Input BOOL
JPDR_LED JPDR Src Select OK Input BOOL
Accelerometer_X Vibration input, X-coordinate AnalogInput REAL
Accelerometer_Y Vibration input, Y-coordinate AnalogInput REAL
App_1_LED Application driven Output BOOL
Fault_LED Fault Led - Application driven) Output BOOL
Parameter Description Selections

InFiltEnb1 Enable inputs filtering for terminal board #1 Disable, Enable
InFiltEnb2 Enable inputs filtering for terminal board #2 Disable, Enable
InFiltEnb3 Disable, Enable
491
DS2020DACAG2 ac-dc Power Conversion
The DS2020DACAG2 is a drop in replacement for the DS2020DACAG1. It is
backward compatible in systems that used the previous version and it should be used
as a replacement part for the previous model. The DACA converts 115/230 V ac
input power into 125 V dc output power, and the output power rating is
approximately 1000 W.
A DACA is used when the primary power source for a control system is 125 V dc
with or without a battery. In addition to power conversion, DACA provides
additional local energy storage to extend the ride-through time whenever the Mark
VIe Control has a complete loss of control power.
The DS2020DACAG2 model has a higher power rating than the previous module.
Also, this new model can be paralleled for greater output current, whereas paralleling
was not recommended for the previous model. The DS2020DACAG2 is
recommended for all new panel designs.
Installation
The DACA module has four mounting holes in its base. Ac power input and dc
output is through a single 12-position connector JZ that is wired into connector JZ2
or JZ3 of the PDM. Selection of 115 V ac or 230 V ac input is made by plugging the
DACA internal cable into connector JTX1 for 115 V or JTX2 for 230 V.
Ensure the proper voltage is selected before power is applied to

the equipment.
JTX1 DACA
115 V Converter
Cable to
transformer JTX2
230 V JZ Cable to
inside DACA PDM JZ2
converter Or JZ3
DACA Module Wiring
492
DACA Filter Capacitor Wear Out
The electrolytic capacitors in the DACA module wear out over time due to the
ambient temperature of the environment where they are used. The following table
shows the calculated life expectancy and recommended replacement schedule for the
DACA modules.
DACA Replacement Schedule
Calculated Life Expectancy of Recommended

DACA Capacitor Replacement Schedule*
At 20°C (68 °F) ambient 100 years
*Due to wear out of Electrolytic Capacitor
To replace a DACA power conversion module
1 Remove power from the DACA module. Allow 1 minute for the output voltage
to discharge.
2 Remove the power input/output cable (JZ) on the right side of the module top.
3 Remove the four bolts securing the DACA module to the floor of the cabinet.
4 Remove the DACA module.
5 Make note of which receptacle the capacitor power plug is in. This is on the left
side of the module top. JTX1 is for 115 V ac and JTX2 is for 230 V ac.
6 Ensure the capacitor power plug is in the same position as the one removed.
JTX1 is for 115 V ac and JTX2 is for 230 V ac.
7 Place the new DACA module in the same position as the one removed.
8 Secure the DACA module to the cabinet floor with the four bolts removed from
the previous module.
9 Install the power input/output plug (JZ) on the right side of the module top.
10 Restore power to the DACA module.
DACA Power Conversion Modules
GEH-6421M
Hole size for 1 / 4"
TAPTITE (4PL)
Drill Plan
Note: Keep out area is 8.65 in. x 13.9 in.
DACA Mounting Pattern
Operation
DACA receives ac power through the cable harness that is plugged into connector
JZ. DACA uses a full wave bridge rectifier and an output filter capacitor. If needed,
the user must provide an input filter to attenuate harmonic currents injected into the
incoming line.
Single DACA Module, Maximum Output Current is 9.5 A dc
Input to DACA Input Current Output Voltage Output Voltage

V ac RMS at Max Load Load = 1 A dc Load = 9.5 A dc
115 V ac 11 A 119 V dc 107 V dc
230 V ac 6A
The DACAG2 can be paralleled for greater output current. In parallel operation,
current sharing between the two DACAs is critical. Uneven current sharing can
cause one of the DACAs to operate beyond its output current rating.
Two DACA Modules with Outputs Paralleled, Maximum Output Current is 16.5 A dc*
Input to DACA Input Current Output Voltage Output Voltage

V ac RMS at Max Load Load = 1 A dc Load = 15 A dc
115 V ac 20 A 120 V dc 110 V dc
230 V ac 11 A
* The two paralleled DACAs must be connected to one ac voltage source for
even output current sharing.
For proper implementation of parallel DACAs, the following must be observed:
• The DACAs must be connected to the same ac source to ensure equal input
voltages to the DACAs.
• The maximum output current per DACA is derated for parallel operation. This
derating accounts for variance in DACA open circuit voltages and variance in
DACA output impedances. The following curve should be used. The maximum
recommended total panel current is 16.5 A dc.
494
Probability of overloading one DACA when two
DACAs are paralled; Plotted at various panel loads
exceeding 9.5 A dc rating

Probability of one DACA
Total panel Load, A dc
Specifications
Item Specification
Input Voltage 105-132 V ac or 210-265 V ac, 47 to 63 Hz
Output Voltage 90 to 145 V dc with a load of 1 to 9.5 A
Over the full range of input voltage
Output Current Rating 9.5 A dc, -30 to 45°C (-22 to 113 °F)
Linearly derate to 7.5 A dc at 60°C (140 °F)
Output Ripple Voltage 4 V p-p
Discharge Rate Nominal input of 115 or 230 V ac, no load, discharge to less than 50 V dc within 1 minute of
removal of input power.
Hold Up (time for output V in (V ac) 105 115 132
to discharge to 70 V dc Initial Load (A dc) 9.5 9.5 9.5
with constant power load)
Pout (W) 882 974 1131
Hold Up Time (ms) 19.5 29.5 48.8
Temperature -30 to 60°C (-22 to +140 °F) free convection
Humidity 5 to 95%, non-condensing
UL 508C Safety Standard Industrial Control Equipment
CSA 22.2 No. 14 Industrial Control Equipment
EN 61010 Section 14.7.2 – Overload Tests
EN 61010 Section 14.7.1 – Short Circuit Test
EN 61000-4-2 Electrostatic Discharge Susceptibility
EN 61000-4-3 Radiated RF Immunity
EN 61000-4-4 Electrical Fast Transient Susceptibility
EN 61000 –4-5 Surge Immunity
EN61000-4-6 Conducted RF Immunity
EN 50082-2:1994 Generic Immunity Industrial Environment
ENV 55011:1991 - ISM equipment emissions
IEC 529 Intrusion Protection Codes/NEMA 1/IP 20
GEH-6421M
Notes
496 of 1016
CHAPTER 8
Replacement/Warranty
Pack/Board Replacement
Handling Precautions
To prevent component damage caused by static electricity, treat
all boards with static sensitive handling techniques. Wear a
wrist grounding strap when handling boards or components,
but only after boards or components have been removed from
potentially energized equipment and are at a normally
grounded workstation.
This equipment contains a potential hazard of electric shock,
burn, or death. Ensure that all Lockout/Tag Out procedures are
followed prior to replacing terminal boards. Only personnel
who are adequately trained and thoroughly familiar with the
equipment and the instructions should install, operate, or
maintain this equipment.
Printed wiring boards may contain static-sensitive components. Therefore, GE ships

all replacement boards in anti-static bags.
Use the following guidelines when handling boards:
• Store boards in anti-static bags or boxes.

• Use a grounding strap when handling boards or board components (per previous
Caution criteria).
Replacement Procedures
System troubleshooting should be at the circuit board level. The failed pack/board
should be removed and replaced with a spare.
Note The failed pack/board should be returned to GE for repair. Do not attempt to
repair it on site.
To prevent electric shock, turn off power to the turbine control,

then test to verify that no power exists in the board before
touching it or any connected circuits.
To prevent equipment damage, do not remove, insert, or adjust

board connections while power is applied to the equipment.
497
Volume II Replacement/Warranty • 537
Replacing V-type Boards
To replace the board
1 Power down the rack and remove the failed board.

2 Replace the board with a spare board of the same type, and move the Ethernet
ID plug from the old VPRO board to the replacement.
4 From the toolbox Outline View, under item Mark VI I/O, locate the failed
protection rack.From the shortcut menu, click Download. The board firmware
and configuration downloads.
Replacing T-type Boards

1 Lockout and/or tagout the field equipment and isolate the power source.
2 Check the voltage on each terminal and ensure no voltage is present.
3 Unplug the I/O cable (J-Plugs).
4 If applicable, unplug JF1, JF2 and JG1.
5 If applicable, remove TB3 power cables.
6 Loosen the two screws on the wiring terminal blocks and remove the blocks,
leaving the field wiring attached.
7 Remove the terminal board and replace it with a spare board, check that all
jumpers are set correctly (the same as in the old board).
8 Screw the terminal blocks back in place and plug in the J-plugs and connect
cable to TB3 as before
Replacing D-type Boards

1 Lockout and/or tag out the field equipment and isolate the power source.
2 Unplug the I/O cable (J-plugs).
3 Disconnect all field wire and thermocouples along with shield wire.
4 Remove the terminal board and install the new board.
5 Reconnect all field wire and thermocouples as before.
6 Plug the I/O cable (J-plug) back.
538 • Replacement/Warranty 498 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
Replacing J-type Boards
1 Lockout and/or tag out the field equipment and isolate the power source.
2 Check the voltage on each terminal to ensure no voltage is present.
3 Verify the label and unplug all connectors.
4 Loosen the two screws on each of the terminal blocks and remove the top
portion leaving all field wiring in place. If necessary, tie the block to the side out
of the way.
5 Remove the mounting screws and the terminal board.
6 Install a new terminal board. Check that all jumpers, if applicable, are in the
same position as the ones on the old board.
7 Tighten it securely to the cabinet.
8 Replace the top portion of the terminal blocks and secure it with the screws on
each end. Ensure all field wiring is secure.
9 Plug in all wiring connectors.
Replacing S-type Boards

1 Lockout and/or tagout the field equipment and isolate the power source.
2 Check the voltage on each terminal to ensure there is no voltage present.
3 Unplug the I/O cable (J-plugs)
4 If applicable, unplug JF1, JF2, and JG1.
5 If applicable, remove the TB3 power cables.
6 A S-type terminal board uses a Euro-style box terminal block. Gently pry the
segment of the terminal block, containing the field wiring, away from the part
attached to the terminal board, leaving the wiring in place. If necessary, tie the
block to the side out of the way.
7 Remove the mounting screws and terminal board.
8 Install a new terminal board. Check to ensure all jumpers, if applicable, are in
the same position as the ones on the old board.
9 Tighten it securely to the cabinet.
10 Slide the segments containing field wiring into the terminal block. Ensure the
numbers on the segment with the field wires match the numbers on the terminal
block. Press together firmly. Ensure all field wiring is secure.
499
Volume II Replacement/Warranty • 539
Renewal/Warranty
How to Order a Board
When ordering a replacement board for a GE product, you need to know:
• How to accurately identify the part

• If the part is under warranty
• How to place the order
Board Identification
A printed wiring board is identified by an alphanumeric part (catalog) number

located near its edge. The following figure explains the structure of the part number.
The board’s functional acronym, shown below, is normally based on the board
description, or name.
IS 200 xxxx G# A A A
Artwork revision
Functional revision 1
Hardware form 2
Hardware form
Functional acronym
Assembly level 3
Manufacturer (DS & IS for GE in Salem, VA)

1
Backward compatible
2
Not backward compatible
3200 = a base-level board
215 = a higher level assembly or added components

220 = pack specific assembly
230 = a higher level module
Board Part Number Conventions
Placing the Order
Renewals/spares (or those not under warranty) should be ordered by contacting the
nearest GE Sales or Service Office, or an authorized GE Sales Representative. Be
sure to include:
• Complete part number and description

• Serial number
• Material List (ML) number
Note All digits are important when ordering or replacing any board. The
factory may substitute later versions of replacement boards based on availability
and design enhancements. However, GE Energy ensures backward compatibility
of replacement boards.
540 • Replacement/Warranty 500 of 1016 Mark VI Turbine Control System Guide Volume II
GEH-6421M
g GE Energy
1501 Roanoke Blvd.
1 540 387 7000

www.geenergy.com
501 of 1016
GE Energy
Control System Toolbox

For a Mark VI Turbine Controller
GEH-6403L Reduced manual for Maintenance training
g

CompactFlash is a registered trademark of SanDisk Corporation.

IBM is a registered trademark of International Business Machines Corporation.
Intel is a registered trademark of Intel Corporation.
Pentium is a registered trademark of Intel Corporation.
Series 90 is a trademark of GE Fanuc Automation North America, Inc.
503 of 1016


equipment.

504 of 1016

personnel.


505 of 1016
Contents
Chapter 1 Overview 1-1
Introduction ............................................................................................................................1-1
Before Beginning....................................................................................................................1-2
How To Use This Manual ........................................................................................1-2
Conventions..............................................................................................................1-3
Chapter 2 Using the Toolbox 2-1
Introduction ............................................................................................................................2-1
Computer Requirements .........................................................................................................2-2
Installation ..............................................................................................................................2-2
Upgrade from Previous Releases ............................................................................................2-3
Maintain Multiple Releases of Toolbox ...................................................................2-3
Migrate Files to Release 9 ........................................................................................2-4
Use Controller Files..................................................................................................2-4
Start the Toolbox ....................................................................................................................2-5
Work Area ................................................................................................................2-5
Access Online Help ................................................................................................................2-7
Privilege/Password .................................................................................................................2-8
Privilege Level Functions.........................................................................................2-8
Change Password ...................................................................................................2-10
Toolbox Options ...................................................................................................................2-12
General ...................................................................................................................2-13
Startup ....................................................................................................................2-14
Database .................................................................................................................2-15
Libraries .................................................................................................................2-16
Print ........................................................................................................................2-17
Controller ...............................................................................................................2-18
Block Diagram .......................................................................................................2-19
Accuwave Power Conversion.................................................................................2-20
AVDV Series Drive................................................................................................2-21
Toshiba GE System Drive ......................................................................................2-22
EX2100...................................................................................................................2-23
Static Starter Drive .................................................................................................2-24
OC2000 ..................................................................................................................2-25
AcDcEx2000 ..........................................................................................................2-26
Trend Recorder.......................................................................................................2-27
Innovation Series Drive..........................................................................................2-28
Connect the Toolbox.............................................................................................................2-29
Innovation Series/Mark VI Controller....................................................................2-29
OC2000 ..................................................................................................................2-29
AcDcEx2000 ..........................................................................................................2-30
Innovation Series Drive..........................................................................................2-31
AccuWave Power Conversion Device....................................................................2-32
Toshiba GE System Drive ......................................................................................2-33
Remote Connection ................................................................................................2-34
Chapter 3 Basic Configuration 3-1
Introduction ............................................................................................................................3-1
Create a Controller..................................................................................................................3-2
General Tab ..............................................................................................................3-3
GEH-6403L Toolbox for a Mark VI Turbine Controller Contents • i
506 of 1016
Memory Tab ............................................................................................................ 3-4
NTP Tab .................................................................................................................. 3-5
Note Tab .................................................................................................................. 3-6
Alarm Scanner Tab.................................................................................................. 3-7
Triple Modular Redundancy (TMR) Tab ................................................................ 3-9
Hold List Scanner Tab............................................................................................3-10
Customer InformationTab ......................................................................................3-11
Ethernet Setup Tab .................................................................................................3-12
Working with Files and Menus.............................................................................................3-13
Import Standard Files .............................................................................................3-15
Save Files................................................................................................................3-16
Revision Tracking...................................................................................................3-16
Open and Close Files..............................................................................................3-17
Export Configuration Files .....................................................................................3-17
Work with Project Files..........................................................................................3-19
Locked Items ..........................................................................................................3-21
Batch Operations ....................................................................................................3-24
Menu Commands....................................................................................................3-25
I/O Checkout.........................................................................................................................3-33
I/O Checkout Status................................................................................................3-35
Filtering ..................................................................................................................3-36
Blockware Concepts .............................................................................................................3-37
Blocks and Block Pins............................................................................................3-38
Macros, Macro Definitions, and Macro Pins ..........................................................3-38
Tasks and Scheduling .............................................................................................3-39
Modules, Module Definitions, and Module Pins ....................................................3-43
Functions ................................................................................................................3-44
Libraries..................................................................................................................3-44
Configuration ........................................................................................................................3-45
Create/Delete Blockware ........................................................................................3-45
Functions and Software Libraries ...........................................................................3-46
Type Definitions .....................................................................................................3-48
Scale Definitions.....................................................................................................3-51
Signal Definitions ...................................................................................................3-53
Table Definitions ....................................................................................................3-58
Import Files ............................................................................................................3-59
Edit Table Definition ..............................................................................................3-60
Module Definitions and Modules ...........................................................................3-63
Module Pins............................................................................................................3-67
Macro Definitions...................................................................................................3-71
Macro Pins..............................................................................................................3-73
Tasks.......................................................................................................................3-75
Blocks and Macros .................................................................................................3-78
Block Flow Diagram ..............................................................................................3-85
Instance Module and Macro ...................................................................................3-86
Alarm Tab...............................................................................................................3-87
Limits Tab ..............................................................................................................3-88
Device Menu Commands......................................................................................................3-91
Database Commands ..............................................................................................3-91
Validate ..................................................................................................................3-92
Build Pcode and Symbols.......................................................................................3-92
Software Setup......................................................................................................................3-94
Controller Setup......................................................................................................3-94
Serial Loader ..........................................................................................................3-95
Initialize Flash ........................................................................................................3-96
Compact Flash Setup ..............................................................................................3-97
ii • Contents GEH-6403L Toolbox for a Mark VI Turbine Controller
507 of 1016
Configure TCP/IP...................................................................................................3-98
Product Code (Runtime) Software .........................................................................3-99
Application Code..................................................................................................3-100
Software Modifications.......................................................................................................3-101
Modify Application Code.....................................................................................3-101
Upload Mark VI File ............................................................................................3-105
Upgrade Product Code (Runtime) Software.........................................................3-105
Use Totalizers.......................................................................................................3-108
Restore Application Code.....................................................................................3-109
Replicate Device...................................................................................................3-110
Monitor ...............................................................................................................................3-111
Going Online/Offline............................................................................................3-111
Watch Windows ...................................................................................................3-114
Monitor Controller State.......................................................................................3-117
Control Constant and Tuning Variable View .....................................................................3-118
Work Area ............................................................................................................3-118
File Compare View.............................................................................................................3-122
Application Documentation................................................................................................3-125
Print Options.........................................................................................................3-125
Print Preview ........................................................................................................3-130
Block Diagram .....................................................................................................3-131
Reports .................................................................................................................3-133
Application Diagnostics......................................................................................................3-140
Types of Application Diagnostics ........................................................................3-140
Generating Application Diagnostics.....................................................................3-142
Control Blocks that Generate Diagnostics............................................................3-144
Runtime Data Flow ..............................................................................................3-146
Diagnostic Data ....................................................................................................3-146
Dynamic Data Recorder (DDR) .........................................................................................3-148
Create and Delete DDR ........................................................................................3-148
Configure DDR ....................................................................................................3-149
Status Signals .......................................................................................................3-150
Import and Export DDR .......................................................................................3-151
Add Signals ..........................................................................................................3-152
Update DDR .........................................................................................................3-152
Chapter 4 Finder 4-1
Introduction ............................................................................................................................4-1
Using the Finder .....................................................................................................................4-2
Finder .......................................................................................................................4-2
Target Finds..............................................................................................................4-3
Chapter 5 Batch Operations 5-1
Introduction ............................................................................................................................5-1
Batch Operations File .............................................................................................................5-2
Batch Window..........................................................................................................5-3
Configure a Batch Operation....................................................................................5-4
Run a Batch Operations File.....................................................................................5-5
System Make Wizard ...............................................................................................5-5
Open and Save Batch Operations File ......................................................................5-6
Import and Export Batch Operations File.................................................................5-6
Chapter 6 File Checkin/Checkout 6-1
Introduction ............................................................................................................................6-1
Initialization............................................................................................................................6-1
508 of 1016
Chapter 7 Configuring System Information 7-1
Introduction............................................................................................................................ 7-1
Working with System Information Files................................................................................ 7-2
Concepts ................................................................................................................................ 7-2
Scale Definitions...................................................................................................... 7-2
Type Definitions ...................................................................................................... 7-2
Measurement System............................................................................................... 7-3
System Overview..................................................................................................... 7-3
Configuration ......................................................................................................................... 7-3
Create/Modify System Information ......................................................................... 7-3
Insert/Modify Scale Definitions .............................................................................. 7-5
Resource Type Definitions ...................................................................................... 7-6
Enumerations........................................................................................................... 7-7
Alarm Classes .......................................................................................................... 7-8
System Overview..................................................................................................... 7-9
Put Data into Database ...........................................................................................7-11
Chapter 8 Graphics Window 8-1
Introduction............................................................................................................................ 8-1
Graphics Window Objects ..................................................................................................... 8-2
Create Graphics Window......................................................................................... 8-3
Menu Bar ................................................................................................................. 8-3
Drag-and-Drop Data ................................................................................................ 8-8
Properties Toolbar ................................................................................................... 8-9
View Signal Summary ........................................................................................................... 8-9
Settings .................................................................................................................................8-10
Frame Size and Options..........................................................................................8-10
Pen Color and Pen Width .......................................................................................8-10
Brush Color and Use Brush ....................................................................................8-11
Text Font ................................................................................................................8-11
Select Controls........................................................................................................8-12
Draw Commands ..................................................................................................................8-14
Insert Object ...........................................................................................................8-16
Insert Picture...........................................................................................................8-16
Animate Objects ...................................................................................................................8-17
Value and Enable Return ........................................................................................8-18
Numeric Animation ................................................................................................8-21
Bar Graph ...............................................................................................................8-22
Trend ......................................................................................................................8-23
Text.........................................................................................................................8-24
Color.......................................................................................................................8-25
Property ..................................................................................................................8-26
Input Fields ...........................................................................................................................8-27
Numeric ..................................................................................................................8-27
Setpoint...................................................................................................................8-28
Initial Value ............................................................................................................8-28
Text.........................................................................................................................8-29
Toggle Command ...................................................................................................8-29
Event Input .............................................................................................................8-30
Hyperlinks ..............................................................................................................8-31
Using Graphics Window Objects..........................................................................................8-32
Signal Substitution..................................................................................................8-37
Forced Signals ........................................................................................................8-38
String Substitutions.................................................................................................8-39
Graphics Windows for the Control Operator Interface (COI) ................................8-40
509 of 1016
Chapter 9 Hardware and I/O 9-1
Introduction ............................................................................................................................9-1
I/O and Network Interface ......................................................................................................9-2
I/O Points..................................................................................................................9-2
Insert I/O and Network Interfaces ............................................................................9-3
Mark VI I/O ............................................................................................................................9-5
Racks ........................................................................................................................9-6
Simplex Rack in Outline and Summary View..........................................................9-9
TMR Rack in Outline and Summary View ............................................................9-10
I/O Boards ..............................................................................................................9-11
Configure Boards in Outline View.........................................................................9-13
Upgrade Boards......................................................................................................9-16
Compare I/O Board Commands .............................................................................9-16
Download Firmware...............................................................................................9-19
Compare Board Revisions......................................................................................9-20
Upload Configuration to File..................................................................................9-22
Compare Configuration to File...............................................................................9-22
VSVO Servo Board ................................................................................................9-23
VSCA Serial Interface Board .................................................................................9-27
Sequence of Events ................................................................................................9-31
EGD Interface.......................................................................................................................9-32
Edit EGD ................................................................................................................9-32
EGD Exchanges .....................................................................................................9-33
EGD Points.............................................................................................................9-36
Genius Networks ..................................................................................................................9-39
Genius Network Configuration ..............................................................................9-40
Genius Network View ............................................................................................9-41
Configure Genius LAN Board................................................................................9-43
Genius Blocks.........................................................................................................9-45
Field Control Station ..............................................................................................9-48
Field Control Module .............................................................................................9-51
Genius Block and Field Control Module Points.....................................................9-54
Third Party Operator Interfaces..............................................................................9-54
Monitor Genius.......................................................................................................9-55
Main Board ...........................................................................................................................9-60
Non-volatile Random-Access Memory ..................................................................9-60
NOVRAM Points ...................................................................................................9-63
Register Network ..................................................................................................................9-64
Ethernet SRTP........................................................................................................9-65
Serial/Ethernet Modbus ..........................................................................................9-68
Allen-Bradley Data Highway™ Plus (DH+)..........................................................9-70
Custom Register Network ......................................................................................9-72
Modify Page Settings .............................................................................................9-74
Modify Point Settings.............................................................................................9-75
Chapter 10 Configuring the Network Interface 10-1
Introduction ..........................................................................................................................10-1
Concepts ...............................................................................................................................10-2
Configuration........................................................................................................................10-3
Create Network Interface .......................................................................................10-3
Work with Network Interface Files ........................................................................10-5
Define Network Connection...................................................................................10-6
Insert/Define Signals ..............................................................................................10-8
Map Signals to a Network ......................................................................................10-8
Specify Signals Used by the Network Interface .....................................................10-9
510 of 1016
Put Into Database/Get From Database..................................................................10-11
Profibus Interface .................................................................................................10-13
Chapter 11 Signals and the Database 11-1
Introduction...........................................................................................................................11-1
Signal Concepts ....................................................................................................................11-2
Drive Signals ..........................................................................................................11-2
Controller Signals ...................................................................................................11-2
Scale Definitions.....................................................................................................11-8
Signal Selector........................................................................................................11-9
SDB.....................................................................................................................................11-12
Put Into and Get From Database...........................................................................11-12
Chapter 12 Turbine Historian Configuration 12-1
Introduction...........................................................................................................................12-1
Working with Files and Menus.............................................................................................12-2
Menu Commands....................................................................................................12-2
Configuration ........................................................................................................................12-4
Create Configuration ..............................................................................................12-4
Templates..............................................................................................................................12-6
Collections..............................................................................................................12-8
Signals ..................................................................................................................12-10
Troubleshooting ..................................................................................................................12-15
Chapter 13 Setup for Turbine HMI Configuration 13-1
Introduction...........................................................................................................................13-1
Concepts ...............................................................................................................................13-2
Working With Files and Menus ............................................................................................13-3
Export as .prj and .tre files......................................................................................13-3
Device Menu Commands .......................................................................................13-4
Configuration ........................................................................................................................13-6
Modify HMI Configuration Properties ...................................................................13-7
Define a Network Connection ................................................................................13-8
Insert EGD Exchanges............................................................................................13-9
Signals ..................................................................................................................13-11
Chapter 14 Configuring the COI 14-1
Introduction...........................................................................................................................14-1
Concepts ...............................................................................................................................14-2
Working With Files and Menus ............................................................................................14-3
Configuration ........................................................................................................................14-6
Modify COI Configuration Properties....................................................................14-7
Define Network Connection ...................................................................................14-8
Insert/Define EGD Exchanges................................................................................14-9
Graphics Window Files ........................................................................................14-10
Glossary of Terms G-1
Index I-1
511 of 1016
Chapter 1 Overview
Introduction
This manual describes GE Control System Solutions products and the Control
System Toolbox, which is micro-processor-based software used to configure and
maintain control equipment. The toolbox is a Windows®-based application, which
runs on a Pentium® 166 or higher, personal computer (pc). Major products
configured with the toolbox include:
• Mark VI Turbine Controllers
• Innovation Series™ drives
• Innovation Series controllers
• Operator Console 2000 (OC2000)
• AC/DC2000 Digital Adjustable Speed Drive and EX2000 Digital Exciter
(AcDcEx2000)
• EX2100 Excitation Control
• Toshiba System drives
• LS2100 Static Starter Control
Primary functions of the toolbox include:
The toolbox software configures • Graphic-based editor for configuring application code
various control equipment.
Therefore, each product package • Block, macro, and module library support
can consist of the toolbox, • Live data block flow diagrams
product files for the controller or
drive, Trend Recorder, Data • Online code change
Historian, and product files for • Online Help files
the System Database (SDB). To
order the toolbox software and • I/O configuration and monitoring
specific product support files, • Signal management and signal trending
refer to the Product Catalog,
GEP-9145. • Multi-user file management
• Report generation
• Batch operation mode
• Target firmware upgrades
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 1 Overview • 1-1
512 of 1016
Before Beginning
Windows-based screen This manual describes the features of the toolbox and presents step-by-step
borders may vary in procedures for using the applications. It presumes that the user has already installed
appearance. Windows and possesses at least a medium-level knowledge of Windows. Hardware
requirements and instructions for installing the products are provided in Chapter 2.
How To Use This Manual

This manual provides the user with information on installing the toolbox and other
products used to configure control equipment. It also describes other features
provided in the toolbox software. This manual is organized as follows:
Chapter 1 Overview. This chapter defines available products and features of the
toolbox, as well as the contents of this manual and conventions used.
Chapter 2 Using the Toolbox. This chapter provides basic installation and startup
procedures for using the toolbox to configure a product.
Chapter 3 Basic Configuration. This chapter describes how to use the toolbox to
configure a controller.
Chapter 4 Finder. This chapter defines the features of the Finder, which searches
the device in the toolbox for items such as text and signals.
Chapter 5 Batch Operations. This chapter describes the Batch Operations mode.
This mode allows you to perform various operations on any number of different file
types at one time.
Chapter 6 File Checkin/Checkout. This chapter describes the Checkin/ Checkout
utility, which allows users to share files contained in a master file.
Chapter 7 System Information. This chapter describes the System Information
device which configures information global to a project, making it available to other
interfaces.
Chapter 8 Graphics Window. This chapter describes the Graphic Window, which
creates custom graphics interfaces for customer and process requirements.
Chapter 9 Hardware and I/O. This chapter describes the controller networks and
I/O used in the toolbox.
Chapter 10 Configuring the Network Interface. This chapter provides
instructions for using the toolbox to configure a Network Interface.
Chapter 11 Signals and the Database. This chapter defines signals and their
sources. It also defines the topological information in the database.
Chapter 12 Turbine Historian Configuration. This chapter describes the toolbox
interface for configuration and use of the Turbine Historian.
Chapter 13 Configuring the HMI Device. This chapter describes the HMI device
and its importation of data from the SDB.
Chapter 14 Configuring the Control Operator Interface (COI). This chapter
describes the Control Operator Interface and its importation of data from the SDB.
Glossary The Glossary provides definitions of terms and toolbox concepts.
Refer to the Table of Contents for the organization of these chapters.
1-2 • Chapter 1 Overview GEH-6403L Toolbox for a Mark VI Turbine Controller
513 of 1016
Conventions
The following conventional terms, text formats, and symbols are used throughout
this documentation for the toolbox.
Convention Meaning
Bold Indicates that the word is being defined.

Arial Indicates the file name or file path used.
Arial Bold Indicates the menu, the actual command or option selected from a menu, a
button, or title of a dialog box.
Italic Indicates new terms, margin notes, and the titles of figures, chapters, and other
books in the toolbox package.
UPPERCASE Indicates a directory, file name, or block name. Lowercase letters can be used
when typing names in a dialog box or at the command prompt, unless otherwise
indicated for a specific application or utility.
Monospace Represents examples of screen text or words and characters that are typed in a
text box or at the command prompt.
¾ Indicates a procedure.
Indicates a procedure with only one step.
• Indicates a list of related information, not procedural steps.
The following list presents some basic guidelines for working with menus:
When a menu is displayed, press the up/down arrow keys to highlight a command
name. Then press Enter to select the menu command. The menu can also be selected
by clicking with a cursor-positioning device (CPD), such as a mouse.
When a command ends in an ellipsis (…), the application displays a dialog box that
asks the user to supply more information.
If a command turns a feature on and off, a checkmark (9) is displayed by the
command name when the feature is on.
When a command ends with an arrow ( ), the menu cascades to display more
command names.
If a command name is grayed out, it indicates that the command does not apply to
the current situation or there is another selection or action before selecting the
command.
Related Documents
GE provides system instruction documents for the different components of each
product. For questions or additional documentation, contact the nearest GE sales
office or authorized GE sales representative.
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 1 Overview • 1-3
514 of 1016
Notes
515 of 1016
Chapter 2 Using the Toolbox
Introduction
Setting options should be This chapter provides basic instructions for using the toolbox. It defines the toolbox
determined before starting a menu commands, including the Options menu, which has a Settings dialog tab for
configuration. each product. Methods of communication and toolbox connections are also
available.
Section Page
Computer Requirements...........................................................................................2-2
Installation ................................................................................................................2-2
Upgrade from Previous Releases..............................................................................2-3
Start the Toolbox ......................................................................................................2-5
Access Online Help ..................................................................................................2-7
Privilege/Password ...................................................................................................2-7
Toolbox Options.....................................................................................................2-12
Connect the Toolbox ..............................................................................................2-29
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 2 Using the Toolbox • 2-1
516 of 1016
Start the Toolbox
The toolbox is started from the Windows NT or 95 Workstation.
To start the toolbox
1. Click Windows Start button, Programs, GE Control System
To create a device, refer to Solutions, and Control System Toolbox.
Chapter 3, the section Create
a Controller. 2. Click the toolbox icon. The toolbox Work Area displays. It is blank until a
device is created or opened.
Work Area
If more than controller is A controller’s runtime action is configured using the toolbox. From the File menu,
open in the Work Area, each begin a New configuration or Open a previously saved configuration file. The
device will have a screen with toolbox Work Area is the main screen and contains the following:
an Outline View and
Work Area commands can be accessed through the menu bar or the toolbar,
Summary View.
depending on the selected product file.
Outline View displays the configuration in a hierarchy, with the drive/controller
name as the first item and other configuration items listed in levels below it.
Summary View displays information based on the item highlighted in the Outline
View. For example, in a controller configuration, the item taskname displays a block
diagram. In a drive configuration, the item Diagram displays drive block diagrams
(which can be configured from this view). The Tracking command controls what
The Tracking button displays in the Summary View. When Tracking is on, it tracks or displays the item
toggles the command on and selected (highlighted) in the Outline View. When Tracking is off, it freezes the
off. Summary View of the last selected item.
Detached Summary View is a separate window from the Work Area window and
Click to display the displays a copy of the Summary View. Option settings for the Detached
Detached Summary View. Summary View are separate from the Summary View (see the section, Toolbox
Options). This window can be sized, configured, and edited.
Note The following screen represents a basic toolbox Work Area format. Menu
commands, toolbar buttons, and Outline View items will vary with the product
installed.
517 of 1016
Titlebar
Toolbar
Outline
View
Bookmark
Note
Summary
View
Log
View
Status Privilege Level

bar TMR Processor Connection
Edit Status
Connection/Revision
Idle Time
Double-click to edit the Note can be created when most items are inserted into the drive/controller. Select an
note. item, then select Edit and Insert First. If the item dialog box has a Note text box
and a note is entered, the Note icon displays beside the item in the Outline View
(as shown). Highlight an item containing a Note icon. The note displays in the
Summary View and on the Status Bar at the bottom of the Work Area.
Bookmark items display this Bookmark enables you to mark major items in the Outline View and then return
icon . to them easily using the Bookmarks command in the Edit menu. The Toggle
Bookmark command turns the icon on and off. The Goto Next Bookmark
command jumps to the next item marked with the .
Find the cause of an error by Log View displays configuration data for the highlighted item. This data compiles
double-clicking the error. during toolbox functions, such as file imports, validations, builds, or errors.
It can be toggled on and off Status Bar displays information across the bottom of the screen. When online, the
from the View menu. left side displays a description of various toolbox commands or notes entered. To
display a menu command description, click the menu command and move the
pointer over the command. The right side displays the following information for the
selected controller.
2-6 • Chapter 2 Using the Toolbox GEH-6403L Toolbox for a Mark VI Turbine Controller
518 of 1016
Status Field Displays Background
Privilege Level Privilege Level: 0 -
Privilege Level: 1 -
TMR Processor R Proc -
Connection S Proc -
T Proc -
Edit - white
READ yellow
Connection/Revision Offline gray
Equal green
Minor Diff yellow
Major Diff red
Idle time Idle white
Access Online Help

To obtain Help for the dialog Specific Help dialog boxes are available by pressing the F1 function key, when a
dialog box is displayed. Help can also be accessed using the following methods:
box on the screen, press F1 .
To obtain Help on . . . Do this . . .

Menu commands Highlight the command and press F1
Dialog boxes Press F1 when the dialog box displays on the screen
Block information Click the desired block with the right mouse button and select Item Help
Help contents Click the Help menu and select Contents
Help Click the Help menu and select Using Help
Specific word(s) Click the Help menu, select Contents, and click the tab Find, then enter the word(s)
to search
519 of 1016
Privilege/Password
Refer to the next section to The privilege/password system assigns different levels of access to the devices.
change the password. Passwords can be established for the different privilege levels, so that each user can
access a device at the level necessary for the job that person is assigned.
To set a privilege level
From the Options menu, select Privilege. The Select Privilege Level
dialog box displays (refer to the next section, Privilege Level Functions).
Privilege Level Functions

A password can be assigned to each of the toolbox privilege levels. (Each successive
level allows all the functions of the previous level.)
520 of 1016
Level Functions
0: Read Only View code
Use the Finder
Monitor live data
Trend (including saving trend definitions in .trn files and saving
collected data)
Change View attributes under Options\Settings
Print blockware code and reports
Change the password for level 0
1: Change Controller Online All functions allowed in Level 0, including change password
Signal Values levels in Levels 0 and 1
Force signals in a controller
Change the value of variables
2: Change Controller Code, All functions allowed in Level 0 and Level 1
Use all Macros
Make code changes
Download
Import/Export
Put in database and Get from database
Validate, build, save, backup, and pack signals
Change the password for Levels 0, 1, and 2
3: View all Macros View structure of macros
4: Change all Macros Delete macros
Modify macros
521 of 1016
Change Password
To change the password
From the Options menu, select Passwords. The Changing Password
dialog box displays.
Select the privilege

leve to change.
Click OK.
The Changing
password for level
dialog box displays
(refer to next
section).
Enter the old

password.
Enter the new

password.
Re-enter the new

password for
verification.
Note If a password for a lower level is to be changed, the higher level overrides the
need for the old password and the Temporary Password button does not display.
When a password is created, it is associated with the binary file currently opened. To
remove a password for a particular level, type the old password, but do not enter
anything for the new password.
If a macro has access level 2, a user at privilege level 2 or above can use the macro
in code, but cannot see the blocks or pins that make up the macro, except for any
pins that the macro writer decided to make visible. These pins are displayed in the
Summary View of the block diagram, not in the Outline View. If a Visio diagram
or Help file is associated with the macro, they also can be seen.
If a macro has access level 3, a user at privilege level 2 or above can view the blocks
and pins that make up the macro. They can also select the code and copy it to their
own macro and modify.
If a macro has access level 4, a user at privilege level 2 or above can change or delete
the code.
If the old password is not known, a temporary password can be requested.
522 of 1016
To request a temporary password
1. From the Changing Password dialog box, click the Request button. The
Temporary Password Request dialog box displays.
Click OK.
The
Password_ID
text displays.
2. Follow the appropriate instructions from the Password_ID text.
523 of 1016
Toolbox Options
Option settings are saved in The toolbox working environment can be defined for each application. This section
the user’s Windows registry describes each tab that can be set to customize the toolbox device, database, block
when the toolbox is closed. diagrams, and such. These tabs are located in the Options menu under Settings.
To customize the toolbox settings
1. From the Options menu, select Settings. The Settings dialog box displays.
Click a tab to bring it to the front and select options.
2. Click OK to apply the changes and close the dialog box. Click Cancel to exit
and not change any settings.
524 of 1016
General
The General tab applies to all devices.
Select a font for the Online View. Select a font Expert Mode allows
The default font is System Bold. for the Finder. extra data to be seen
Use compact export format

compresses the .tre files
produced by exporting. Less
hard disk space is used, and
it is easier to read and edit.
Save Bookmarks in files

saves bookmarks
between closing and
reopening files.
Auto-Save files every [ ]

minutes automatically saves
the files at the set increment.
The default is 15 minutes.
Compress files when Backup files before save

saving saves and stores creates a backup copy of
files in a compressed files before saving new
format to save disk space. information. This includes
.ucb, .dcb, .icb, and .ocb.
525 of 1016
Startup
The Startup tab allows you to specify whether you want a file to automatically load
at startup.
Select one of the following

file options:
None dictates that no file

is automatically loaded on
toolbox startup.
Load last file loads the

files that were in use when
the toolbox was exited.
Select file allows you to

select the file that loads
when the toolbox starts.
Click Browse... to locate
the file.
526 of 1016
Database
The Database tab defines the database and any required network information. It
applies to all devices as listed.
Select the SDB

database (SDB
is the system
database used
on a Windows
computer).
Note: USDB is
not used by
Static Starter
Control.
Enter the name

of the host to the
database. The
server name is
not case-
sensitive. If a
name server is
not available,
the IP address
must be used.
Enter the location of the SDB sub-directory on the server where the data
files are stored. The name must include the drive letter and at least one
sub-directory. The SDB cannot be located at the root of a drive. For a
USDB, the name is specified in the GEBHOST environment variable on
the LynxOS computer, for example, ustst_usdb.
527 of 1016
Libraries
The Libraries tab defines the block and module libraries that are automatically
imported when a new controller (or OC2000) is created.
Note Existing controller libraries are referenced in the .prj file and override these
default libraries.
Select the product

library to define.
Default libraries
are listed. Use the
command buttons
to enter and edit
the library list.
Up and Down
rearranges the
list order.
Change inserts
the edited library
back into the list.
Add inserts the
new library from
the text box.
Remove deletes
the selected library
from the list.
Browse… allows you

to search the directory
structure and select
an existing directory.
528 of 1016
Print
The Print tab allows you to set print options for the current device. It applies to
controllers and drives as listed.
The Block Diagram Where Used Scope applies
only to controllers. Specify the scope of the signal
cross-referencing in the active block diagram.
Select the font for

the text displayed
immediately over
the blocks in the
diagram. The
default font is
Courier New.
Select the font for the

Signal Definitions and
Where Used Lists at
the end of each block
subsection. The default
font is Courier New.
Select the font for the

text at the top of each
new section and block
subsection. The
default font is Arial.
Select the font for all text
not listed above, including
block names and pins. The
font side directly affects the
number of blocks that
display on a page diagram.
The default font is Arial
Narrow.
Select this check box to

use old-style printing.
529 of 1016
Controller
The Controller tab allows you to select the following options.

allow Boolean Engine
(BENG) blocks to be
edited using a Relay
Ladder Diagram (RLD).
If this box is not checked,
modify the block using
the Edit Block
Connections dialog box.
Select to enable
revision tracking, which
allows you to enter
information about a
change to a document
(file) when it is saved.
Select to display file

checkout status.
Refer to the Checkin-
Checkout utility.
530 of 1016
Block Diagram
The Block Diagram tab allows you to specify how the block diagram displays in the
Summary View and Detached Summary View.

allow Boolean Engine
(BENG) blocks to be
edited using a Relay
Ladder Diagram (RLD).
If this box is not checked,
modify the block using
the Edit Block
Connections dialog box.
Select to enable
revision tracking, which
allows you to enter
information about a
change to a document
(file) when it is saved.
Select to display file

checkout status.
Refer to the Checkin-
Checkout utility.
531 of 1016
Trend Recorder
The Trend Recorder tab allows you to select the following options.
Select any of the following

options.
Horizontal Grid Lines

displays the horizontal grid
lines when in replay mode.
Vertical Grid Lines
displays the vertical grid
lines when in replay mode.
Right Vertical Axis
displays the vertical axis
on the right side.
Dual Vertical Axis
displays the outer Y-axis.
Check to automatically
configure the recorder with
predefined signals.
Note: This option only works
with Innovation Series Drives
and when performing Mark VI
I/O board calibrations.
Check to zoom in the Trend

Recorder, using the mouse to
drag-and-drop a rectangle on
the screen.
Check for a Yes/No confirmation
prompt to display before the zoom
takes place.
Select the default pen width, Check to display Enter the amount of memory Click Default Colors to
in pixels, used to draw the the amount of the Easy-Drive reserves for change the colors used
signal traces. reserved memory storing traces. The default to draw the traces.
that was used. value of 2 MB allows four Click Columns to
signals to be captured at 32- select the headings to
ms intervals for about 14 be displayed in the
minutes before the oldest data Lower Signal View.
is overwritten.
532 of 1016
Connect the Toolbox
The toolbox operates over Ethernet through a controller gateway and over a DLAN+
for an OC2000 and AcDcEx2000 or over ISBus to an Innovation Series drive.
Optionally, it can operate over a serial cable to a drive. The toolbox must
communicate with a device to configure or monitor it. There are two methods of
communication available:
See Windows Help Topics: TCP/IP is used to inter-network dissimilar systems. To use TCP/IP, the proper
Windows Setup Help for network software must be installed and configured in Windows NT or Windows 95.
installing and configuring If the toolbox uses TCP/IP to communicate with an OC2000 or drive, a controller is
TCP/IP. required to act as a gateway.
Direct Serial is available only with drives. The toolbox communicates directly with
the drive using the pc serial port. No special network software is required.
Innovation Series/Mark VI Controller

The toolbox can be directly connected to a controller using Ethernet.
Control System Innovation Series Controller

Toolbox
Ethernet
Windows PC
Toolbox connected directly to a controller
OC2000
The OC2000 communicates using DLAN+. The toolbox can communicate with the
OC2000 only when a controller acts as a TCP/IP to the DLAN+ gateway.
Control System OC2000

Innovation Series Controller
Toolbox
TCP\IP DLAN+
Windows PC
Toolbox connection to an OC2000
533 of 1016
Remote Connection
For more information, refer to Windows can make TCP/IP connections remotely, such as connecting the toolbox to
the Windows documentation on a remote device, using modems.
Remote Access Service and
Dial-up Networking.
Modem/Ethernet
TCP/IP Gateway
Control System
Toolbox TCP/IP
Modem Modem
Ethernet
Windows PC Innovation Series Controller
DLAN+
OC2000 DC2000 AC2000 EX2000
Remote Toolbox Connection to DLAN+ Gateway
Control System
Toolbox TCP/IP Modem/Ethernet
Modem Modem
TCP/IP Gateway
Ethernet
Windows PC Innovation Series Controller +
- AC
Innovation Series
MCL ACL
ISBus
+ +
- AC - AC
Innovation Innovation
Series Series
Remote Toolbox Connection to ISBus Gateway
534 of 1016
Notes
535 of 1016
Chapter 3 Basic Configuration
Introduction
This chapter provides instructions for using the toolbox to configure and monitor a
Mark VI Turbine controller. It also has information on using other features of the
toolbox specific to the controller.
Section Page
Introduction ..............................................................................................................3-1
Create a Controller ...................................................................................................3-2
Working with Files and Menus ..............................................................................3-14
I/O Checkout ..........................................................................................................3-37
Blockware Concepts...............................................................................................3-41
Configuration..........................................................................................................3-49
Software Setup .....................................................................................................3-100
Software Modifications ........................................................................................3-107
Monitor.................................................................................................................3-117
Control Constant and Tuning Variable View .......................................................3-124
File Compare View...............................................................................................3-128
Application Documentation..................................................................................3-131
Application Diagnostics .......................................................................................3-148
Dynamic Data Recorder (DDR) ...........................................................................3-156
Note If you are not able to perform an operation described in this chapter, check
your privilege level (refer to the section, Privilege Level Functions).
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 3 Basic Configuration • 3-1
536 of 1016
Working with Files and Menus
A Mark VI controller is configured using different types of files. The configuration
files generate output files that can be downloaded to the controller.
Configuration files include:
Tree files (.tre) are text files that transport controller software and hardware
configurations to different versions of the toolbox.
Binary working files (.m6b) contain an exact copy of the configuration used by the
toolbox. Users generally work from .m6b files.
Note Each .m6b file should be kept in a separate folder.
Project files (.prj) are text files that keep track of the order of .tre files and hold
some controller configuration information.
Batch build files (.bld) can execute various toolbox operations on a list of different
configuration files.
Output files include:
Pcode files (.pcd) are application files and describe the configuration for the
controller. These files can be downloaded to the controller.
Symbol files (.sym) describe the signals used by diagnostics to the controller. These
files can be downloaded to the controller.
Signal reports (.sig), cross-reference reports (.xrf), Pcode reports (.pcr), and
block diagram printout files (.prn) can be generated, viewed, and printed.
Back up all files often to avoid losing data.
3-14 • Chapter 3 Basic Configuration GEH-6403L Toolbox for a Mark VI Turbine Controller
537 of 1016
The following diagram shows the relationship between these files and the toolbox.
Programmer Workstation
mkvi_io.tre
sblib.tre
turblib.tre *.m6b file
hardware,
Save
library, and Export
function .tre files
Documentation
Import Open
Print
Open
*.prj file Export
(.tre) Get from
database Windows NT
or
The .prj files (Open/Export) Windows 95 Build
*.pcd & *.sym
list all .tre files that should be running toolbox files
imported for this controller.
Put into Download
database
Note The default installation directory

SDB or Controller
is C:\Program Files\GE Control System
USDB
Solutions\ToolBox.
538 of 1016
Save Files
Saving a controller file writes the entire contents of the configuration to a .m6b file.
The content of the file and everything associated with that configuration is preserved.
The prior .m6b is renamed to Backup of xxx.m6b.
To save a file
Or click 1. From the File menu, select Save. The Save As dialog box displays.
2. Enter the file name (change the file type, if desired) and click Save.
Once a configuration is saved, the Save button can save the new file without asking
for a file name. The Save button also indicates when a change is made to the
configuration by highlighting (turning red) and becoming enabled.
Note The Save button highlight feature indicates that the configuration has changed
and that a failure in the computer or toolbox will result in a loss of those changes.
Revision Tracking
Saving controller files starts the revision tracking system in the toolbox. Revision
tracking helps in troubleshooting configurations, as well as providing traceability and
ownership of files changes. The Revision Entry dialog box displays just prior to
the file being saved to disk.
Date/Time
stamp of
this revision.
The user name

of the currently
logged in
WIN98/NT/2000
account.
Enter a
description of
this revision.
Since a revision is required for each Save operation, selecting the Cancel button
also cancels the Save operation.
Revision tracking is enabled by default. To disable revision tracking, change the
toolbox options. Refer to Chapter 2, Toolbox Options.
539 of 1016
Open and Close Files
Opening a .m6b file reads a previously saved controller configuration into the
toolbox.
To open a file
Or click 1. From the File menu, select Open. The Open dialog box displays.
2. Select the file name and click Open.
Check the Release Notes located Note If another version of the toolbox is used to open a .m6b that was saved with a
in the toolbox Help menu under different version, a Warning displays. Either install the toolbox version that the .m6b
About Toolbox. was saved in (listed in the Warning box) or consult the toolbox Release Notes to see
if they are compatible.
To close a file
From the File menu, select Close.
Closing a controller file removes the configuration from the toolbox. If the
configuration has not been saved, a dialog box displays and asks if the configuration
should be saved.
Export Configuration Files

This option is normally not required, but is provided when
upgrading between versions of the Mark VI controller runtimes
older than V05.09.00C. The Export command can also be used if
there are problems with a newer version of the toolbox that
changes the configuration file (.m6b) format that is not backward-
compatible, or if there are problems with a runtime upgrade.
Normally, newer versions of the toolbox load configuration files created by older
versions. However, if a problem occurs because of a major change in functionality,
the toolbox may not be able to load the configuration file. In this case, it is necessary
to first export the configuration file with the old version of the toolbox to a project
file, and then open the project file with the new version.
Note The .tre files can be exported selectively, or for the entire controller.
The Upgrade command is also used to upgrade a configuration (.m6b) from one
runtime version to the next. But if the upgrade needs to take place between runtimes
that are less than V05.09.00C, the upgrade command cannot be used. In this case, an
Export All command is performed. The new Mark VI controller runtime is installed,
and the project file that uses the new runtime files is opened, completing the
upgrade.
The manual Export command may also be necessary if there are automatic upgrade
problems due to major changes in the runtime features. The Export command allows
for a manual upgrade, which corrects problems with the automatic upgrade.
Note The first time you export, make sure that each item is configured to be saved in
the desired directory.
540 of 1016
Batch Operations
Many operations in a controller configuration can be started for more than one
controller using batch operations. The file name and the operation for each file can
be saved in a batch build file (.bld).
To create a batch build file
1. From the File menu, select New. The New dialog box displays.
2. Click the Utilities tab, select Batch Build File, then click OK. The Batch
operations dialog box displays.
The controller performs the following batch operations:
• Put Signals puts the controller’s signal data into the database.
• Get Signals obtains another controller’s signal information from the database.
• Validate Device verifies that the configuration is ready to build Pcode.
• Export Device writes the .tre and .prj files for a configuration.
• Build Device creates a Pcode file.
• Save Device writes configuration to an .m6b file.
• Offline Download downloads the Pcode file to the controller and restarts it.
• Flash Download downloads the Pcode file to flash memory.
• Build Symbols creates a symbol file.
• Put Symbols writes the controller’s symbol information to the database.
• Download Symbols downloads the symbol file to flash memory.
541 of 1016
Menu Commands
The toolbox work area contains the following Menu bar:
File Menu
The File menu provides the following commands:
New creates a new controller/file.

Or click .
Open displays an existing controller/file.
Or click .
Close exits an existing controller/file.
Or click . Save/Save As preserves an opened controller/file to a specified name.
Import retrieves a file from the specified source. Or, from the menu, select Imports
Or click .
a second language report.csv file.
Export sends file(s) to a specified .tre file.
Compare compares the functions of the currently open file with those of another,
user-specified file.
Upgrade allows you to upgrade the Mark VI configuration file from one version of
the runtime to a newer version.
542 of 1016
Print Setup allows you to select a printer and printer connection.
Or click . Print provides a paper (hard) copy of a specified file or page.
Print to MetaFile prints the block diagram to a set of Enhanced Metafiles (*.emf)
instead of sending it to the printer. These metafiles can be viewed using various
graphical software programs, or imported into text processing programs such as
Microsoft Word.
Print Preview displays the page as it would be printed.
Send To opens email and provides a copy of the currently opened file to send (you
must have Windows messaging, such as Exchange).
File 1, 2, 3... lists and opens a previous opened file.
Exit closes the toolbox.
Edit Menu
The Edit menu allows you to modify the controller:
Modify edits the item highlighted in the Outline View.
Or click . Delete removes the item highlighted in the Outline View.
Cut removes the highlighted item and places it on the clipboard.

Or click .
Copy duplicates the highlighted item and places it on the clipboard.
Or click .
Paste places the highlighted item from the clipboard into the current file.
Or click .
Insert First inserts the first new item under the item highlighted in the hierarchy of
the Outline View.
Insert Next inserts the next new item at the same level as the item highlighted in
the hierarchy of the Outline View.
Instance updates a single item or select All to update the entire controller/file.
Renumber changes the numbers of the highlighted blocks.
543 of 1016
Bookmark items display this Bookmarks enable you to mark major items in the Outline View and then return to
icon . them using the menu commands or clicking the bookmark icon.
Override Modules unlink all software modules from their library templates.
544 of 1016
View Menu
The View menu allows you to view areas within the controller with the commands
listed.
Click to toggle Tracking Tip For faster navigation in the Outline View, turn Tracking off. Only turn
on and off.
Tracking on to view an item in the Summary View.
545 of 1016
A check mark ( ) displays by Toolbar displays or hides the Toolbar.
the command name when the
Status Bar displays or hides the Status bar.
feature is on.
Tracking toggles the tracking feature of the Summary View on and off.
Or click .
Close Outline reduces the hierarchy items listed in the Outline View to just the
controller level.
Detached Summary creates a separate window of the Summary View.
Or click .
Zoom In enlarges the view of the block diagram area.
Or click .
Zoom Out reduces the view of the block diagram area.
Or click .
Go Back and Go Forward allows you to return to earlier selections in the
Or click . Outline View.
Finder starts the Finder window to search text and signal usage.
Watch Windows creates a customized, quick-reference list of signals and their
online values.
SDB Browser is a separate window, which can help you find items (such as signal
usage from the different types of controllers), display the topology of a system,
perform a filtered signal search on the SDB, and more (refer to GEI-100271).
Force Lists displays forced signals and I/O points that can be edited.
Reports creates a report of the Alarm List, Hold List, Event List, Scale List, Signal
List, Signal Cross Reference, Multiple Written Signal List, EGD Network,
Simulation Data, Control Options, I/O Report, I/O Point List, Unused I/O Report,
Revision Log Report, Enumerated Data Types, Control Spec Reports (IO Config and
Signal Config), Block Pin Report, or Tuning Variables.
Note Refer to Chapter 3, Application Documentation, Reports for detailed

information on the reports the toolbox can generate.
Trend Recorder monitors and graphs signal values from a controller (refer to
GEH-6408).
Control Constants displays a separate window to view control constants, which
can be viewed and compared as a group, exported to .csv files for manipulation
outside of the toolbox, and merged back into the configuration.
I/O Checkout creates a report of all I/O with columns to indicate if the I/O point
has been checked (it’s status), when it was checked, and a freeform note for each
point.
Configuration Statistics opens the Device Metrics window to display memory
usage.
Controller Status Commands are hardcoded QNX commands. They display
under one of the following menus: General, File System, Network, or
Process.
Controller Load Profiler allows you to quickly and easily interrogate the
controller to determine what application tasks are scheduled to run and which, if any,
are delayed.
Controller State creates a report on the current state of the controller.
546 of 1016
Device Menu
The Device menu allows you to manage the controller with the commands listed.
Validate makes certain that selected items or functions do not contain errors and
Or click . confirms that a configuration is ready to build Pcode.
Build compiles the configuration and generates the Pcode.
Or click .
Pack signals reassigns address tokens when signals become fragmented.
Download sends files to the current controller.
Or click .
Application Code sends the values of all the parameters from the loaded
controller configuration files to the current controller.
Product Code (Runtime) sends the Mark VI firmware configuration to the
current controller.
Compact Flash allows Compact Flash to be reprogrammed.
View/Set Time allows time in controller to be set to pc time.
View/Set Totalizers displays the totalizer information.
Restore from Perm Storage overwrites the application code stored in the
controller’s RAM with the code stored in the controller’s FLASH.
Upload retrieves Mark VI files from any controller.
Online/offline toggles to initiate communication to the controller.
Or click .
Put Symbols Into Database places diagnostic symbol information into the
database.
Put Into Database places controller information into the database.
Get From Database reads information from the database and places it in the
current configuration.
Create Undefined Signals produces a definition for signals not defined.
Note For additional information on the Put Into Database, Get From
Database, Validate, Upload, Build, and Download commands, refer to the
section, Device Menu Commands.
547 of 1016
Options Menu
The Options menu allows you to manage general options for toolbox operation.
For more information on the

Option menu, refer to
Chapter 2, Using the
Toolbox.
Settings allows you to assign general toolbox options.

Privilege sets the privilege level for a session.
Passwords sets the password for a privilege level.
Logout User clears the user ID and sets the privilege level to zero. It locks all
libraries or functions in all open documents in the temporarily unlocked state (refer
to the section, Locked Items).
Re-Lock Function or Software Library locks the item and enables the
password.
548 of 1016
Window Menu
The Window menu allows you to manage screen views..
Cascade arranges the windows in an overlapped style.

Tile Horizontal arranges the windows in horizontally non-overlapped tiles.
Tile Vertical arranges the windows in vertically non-overlapped tiles.
Arrange Icons arranges the icons of closed windows.
Close All closes all open windows.
Window 1, 2, ... allows you to view currently open files.
549 of 1016
Help Menu
The Help menu offers the following Help files.
Contents displays the Help files for the toolbox.

Using Help displays general instructions on how to use Help.
Standard Blocks displays a block library used across all industries.
Industry Blocks displays a block library used in specific industries, such as
metals, paper, and material handling.
Runtime Errors defines errors that display in the Log View.
Item Help displays Help information about the item highlighted in the Outline
View.
Release Notes provides product changes in the toolbox.
Send Problem Report allows you to submit a system change request for the
toolbox.
Goto Toolbox Web Site takes you to the toolbox home page.
About Toolbox displays the version number and platform for this application.
550 of 1016
I/O Checkout
This view allows you to customize the optimal setup by providing live data during
the I/O checkout phase of turbine installation. It allows you to select the columns
desired for the report. Once the report is generated, click the column header to sort
the data in each column.
To view an I/O checkout report
From the View menu, select I/O Checkout.
The Select Columns dialog box displays to allow you to select the desired
information for the report.
Click the
checkbox to
select a column.
Click the box
again to uncheck.
Click OK. The I/O

Checkout view
displays.
551 of 1016
Click to zoom in (increase) or
Click to define the zoom out (decrease) the text size
Checkout status (refer to in the checkout view. If the
the status box below). To currently selected font is at its When online, live data displays in green. Points that
Checkout any item, the maximum or minimum, the font do not correspond to data from the Mark VI will be Click on a column
privilege level must be at must be changed to a different font displayed as N/A. To change or force the live data, header to sort that
least 2 in the Options menu right click on the row and choose Change Live Data. column alphabetically
Click
Filter to
determine
items to
display in
columns.
Refer to
section
Filtering
Click to
add or
remove a
column.
The status bar displays three items.

Percentage of filtered points that are in the Verified State.
Percentage of all points that in the Verified State.
Number of points that are currently being displayed.
552 of 1016
Blockware Concepts
For more information on how The controller software is made up of blocks that perform control logic. The
to configure each item, refer software is referred to as blockware. These blocks correspond to a function block
to the section, Configuring that exists in the product code (runtime). The block definitions are imported as .tre
Controller Blockware. files within the block libraries.
These blocks are used to make up macros. Blocks and macros make up tasks. One or
more tasks can go into a module and any number of modules make up a function.
This hierarchy shows how the different levels of controller blockware display in the
Outline View below.
There are two levels of blockware that can be reused and instanced any number of
times:
• Macro(s) contain a standard collection of blocks.
• Module(s) are a more complex collection of tasks that have a defined
scheduling relationship.
For more information, see In the toolbox, block, macro and module parameters are called pins (from their
Chapter 11, Signals and the likeness to the pins of an integrated-circuit chip). All pins have a name unique to
Database. their block, macro, or module. Pins are connected by signals, which are the basic
unit for variable information. Signals are created with signal definitions, module
pins, and macro pins or block pins.
553 of 1016
Blocks and Block Pins
Standard library block names Blocks are the most basic programming element. They can perform functions such
are preceded with an underscore as math, solve an RLD, and perform a filter. They can also solve a Boolean equation.
( _ ), such as _CLAMP, to (These blocks can be compared to C-language functions, Pascal procedures or
differentiate them from macros FORTRAN subroutines.) The product code blockware supports a function for each
and blocks in the Industry block block that displays in the standard or Industry block libraries. For more information
library. about the individual blocks and how they work, see the toolbox’s Block Library
Help.
When a block is inserted into a task, a number and colon is added before the name to
make the use of the block unique, such as 20:MENG. This number is used to refer to
For connecting information,
pins of the block from other blocks in the same task or macro, such as 20:OUT.
refer to the section, Connect a
Pin. Block pins contain signals when the block is inserted. Block pins can be connected
to one another or to other pins and signals using these signals.
Macros, Macro Definitions, and Macro Pins

A macro is a collection of blocks and other macros that contains well-defined inputs
and outputs. You can create a macro by constructing a macro definition. If the macro
definition changes, add a version number.
Once the macro is defined, insert the macro into a task or another macro. The
inserted macro’s internal blocks and connections cannot be changed. Macros can be
inserted in up to three levels as follows:
Macro pins have unique names; once inserted, they can be referenced just like block
pins. Macro pins are also signals that can be connected to the pins of the constituent
blocks and macros. Once inserted, these macro pins act as the parameters of the
macro whose behavior is specified based on how they are used in the code inside the
macros. The macro can have one macro pin designated as an enable pin. The enable
pin is a logical or Boolean signal that activates a macro.
Macros are shown in the following Outline View. The item, Macro Definitions, is
located in both Function and in the Macro and Module Library. The library provides
a main location for standard modules and macros. Function provides a location for
modules and macros used in a particular function.
554 of 1016
If a macro is defined local to a function, it cannot be used outside that function.
Therefore, if the macro is used in more than one function, it should be defined in a
macro library. Also, if the same macro is used in more than one controller on a given
job or used on more than one job, it should also be in a library.
The libraries only contain code definitions, not code already instanced to run in the
controller. By defining the macro in a library, the library can be directly imported
into the second controller without having to separate instanced code. This makes the
maintenance of that macro easier, should it ever need to be changed.
For information on If a macro definition is changed, the inserted versions of the macro can be updated
instancing, refer to the by instancing the macro. Instancing a macro replaces all the blocks and macros, and
section, Instancing Module their connections inside the macro, but keeps the connections to the macro pins of
and Macro Pins. the macro instance. Macros can only be instanced individually, if they are in a Task
(top level).
Tasks and Scheduling

For more information, refer Tasks divide a module into items that require different scheduling parameters. Each
to GEH-6410, Innovation task has a period multiplier. The task period multiplier determines the rate of task
Series Controller System execution by a binary multiple of the module base scheduling period. This can be 1,
Manual. 2, 4, or 8 times the module period or event driven. A task can be scheduled to run
based on 5 ms, 40 ms, or 320 ms module period.
Tip A task cannot be scheduled to run any faster than the Frame Period specified
in the General tab of the Controller Properties dialog box (refer to the section,
Creating a Controller, General Tab).
See the Task Scan Scheduling To equalize CPU loading, each task has a skew offset that shifts its scheduling
Periods Table for a list of position relative to other tasks without changing its execution frequency. The
possible combinations of skew possible values for skew offset vary between 0 and 7 as a function of the period
and period multiplier and the multiplier.
effect of each on task
scheduling. Note Care should be taken when data is shared between modules at two different
time bases. This shared data can change at any time within the slower module, when
the faster module pre-empts it.
555 of 1016
Tasks are scheduled to run based on the order that they display in the Outline View.
In the following example, TaskA comes before TaskB and TaskB comes before
TaskC. If all three tasks are scheduled with the same module period, period
multiplier, and skew offset, TaskA always runs before TaskB and TaskB always runs
before TaskC.
For example, the scheduler runs tasks that are scheduled to run in a 40 ms time slice.
If there is extra CPU time before the next 40 ms time slice, it will run any 320 ms
based code currently scheduled to run.
Task Scan Scheduling Periods Table

Within a time slice, the tasks are In the following table, each time slice is either 5 ms, 40 ms, or 320 ms long, based
scheduled based on the order on the scheduling period selected for that module in the Edit Module dialog box. If a
they display in the Outline View. controller has several modules with the same scheduling period, all the tasks within
all these modules end up together in the same scheduling table. In the table, X
represents when a task will run based on the period multiplier and skew offset
selected for it.
556 of 1016
Task Scan Periods at 5, 40, & 320 ms Module Base
Task Task Skew Offset+Module Scan Period Slice 1 Slice 2 Slice 3 Slice 4 Slice 5 Slice 6 Slice 7 Slice 8
PeriodMult Skew
0* 0
1 0 5, 40 or 320 X X X X X X X X
ms
2 0 10, 80, or X X X X
640 ms
2 1 10, 80, or X X X X
640 ms
4 0 20, 160, or X X
1280 ms
4 1 20, 160, or X X
1280 ms
4 2 20, 160, or X X
1280 ms
4 3 20, 160, or X X
1280 ms
8 0 40, 320, or X
2560 ms
8 1 40, 320, or X
2560 ms
8 2 40, 320, or X
2560 ms
8 3 40, 320, or X
2560 ms
8 4 40, 320, or X
2560 ms
8 5 40, 320, or X
2560 ms
8 6 40, 320, or X
2560 ms
8 7 40, 320, or X
2560 ms
* A task with a 0 period multiplier is only scheduled if an Event is executed.
557 of 1016
Task Execution
Tasks can be enabled and disabled from the blockware by connecting the task enable
to a signal and modifying the online value. Disabling a task prevents it from
executing, regardless of its schedule or any Events put into the database. To prevent
execution of the blocks in that task and the inputs and outputs used in that task from
being transferred, Task enable can be forced to False, using the toolbox.
Tasks are configured to execute periodically. All the external inputs referenced by a
task are automatically transferred from the I/O table to the signal table, just before
the task execution. This signal is frozen for the duration of the execution, as long as
it is not shared by a task in a module with a shorter scheduling period.
Tasks in modules with a 40 ms scheduling period have a higher priority than tasks in
modules with a 320 ms scheduling period. If a 320 ms base task is running when it is
time for a 40 ms base task to run, the 320 ms base task is interrupted for the 40 ms
base task to run. However, within the same module-scheduling period, one task
cannot interrupt another even if it is currently scheduled to run.
For example, taskA is scheduled to run every 640 ms and taskB is scheduled to run
every 2560 ms. If taskB is currently running when it is time for taskA to run, taskA
can not interrupt taskB. However, all control blocks are written to use absolute time.
This means that a timer block in taskA would know and adjust appropriately if more
than 640 ms had passed since it last ran. It would not assume that 640 ms had passed
just because taskA was scheduled to run at that rate.
For more information, see the All the external outputs referenced by the task are transferred from the signal table to
section Simulation System. the I/O table at the end of the task execution. Forcing or simulation can override the
I/O transfers. Even if a task is exited early, its outputs are still written.
Modules can also have a skew. A module skew is added to the task skew offset for
all tasks in the module. It is normally used for processes such as the following. A
module definition is written to control one stand of a finishing mill. The module is
then instanced six times, once for each stand in the finish mill. Each stand’s module
instance has a different skew offset, so that all the code will not be scheduled to run
at the same time.
Module pin signals can be internal signals, I/O signals, or network signals. Module
pins have an Event option, independent of the signal attached to the pin, which
affects how blockware is scheduled.
Frames
A Mark VI frame is the period in which the controller reads inputs, computes a
control algorithm, and produces outputs at the terminal boards. To insure proper
operation, all tasks must run to completion within this window and still reserve
enough time to perform the I/O.
Input Task Output and Input Task Output and

collection execution distribution collection execution distribution
and voting and voting
Frame 1 Frame 2
40 ms
Example of 40 ms Frame
558 of 1016
Modules, Module Definitions, and Module Pins
Modules allow you to reuse blockware on a higher level than macros. All blockware
downloaded can be found in the Outline View, Function level, in the item Modules.
Note There is not a Modules item in the Macro and Module Libraries level.
However, Modules Definitions can be defined there.
There are several types of modules:

• Instanced modules are defined in the item Module Definition under Functions
or Macro and Module Libraries, then instanced in the item Modules under
Function. Like macros, these modules are updated by changing the definition
and then instancing that particular module (once instanced, the tasks cannot be
changed).
• Inline modules are defined in the item Module under Functions. They are not
meant to be reused.
• Override modules are a combination of the instanced and inline modules. They
are created by instancing a module definition and then overriding it from the
Module Edit dialog box. Overriding a module allows you to start with a
standard module definition and then be able to modify it as an inline module.
The pins of a module work similar to macro pins. Module pins are primarily intended
as parameters to the module. However, a local pin can be used to share data between
tasks in the macro.
Module pins can be connected to external signals through the Module pin
definition dialog box. The connections owned by the module pin are kept intact
when a module is instanced. In this way, a module can be updated with a new
module definition and not lose these connections.
All modules have a region name. The complete signal name for a signal associated
with module pins is the module’s region and pin name. For example, the instanced
module CM\std1\speed and module pin name, AutoMode produce the signal name
CM\std1\speed\AutoMode. In the module, the block and macro pins can reference the
module pins by using the module pin name only.
The period and skew of a The period and skew of a module can be overridden in an instanced module, without
module are discussed in the actually overriding the entire module definition. This permits users to maintain the
section, Tasks and Scheduling. inter-relation of modules in the same scheduling chart, while incorporating changes
made to a module definition.
To determine if a Module Module Definitions include a revision field. If the definition of the module changes,
Definition should be under the update the revision. When a module definition is instanced, the instance shows
item Module Library or which revision it was instanced from. This helps determine if a module has been
Function, refer to the section, re-instanced after a change was made to the module definition.
Macro Definition.
559 of 1016
Functions
Functions are also associated Functions are at the highest level in the hierarchy and used primarily to group
with a .tre file in that each inter-related modules. All the data types scale factors, signals, module definitions,
function is exported as a macro definitions and instances for a given function can be independently associated
separate .tre file. with a function, which allows you to move a function from one controller to another.
Libraries
The controller has three types of libraries:
• Block libraries provide a description of the runtime blocks.
• Hardware Module libraries describe the different types of I/O that can be wired
into a controller. It is described in the file, mkvi_io.tre.
• Macro and Module libraries provide a central location for standard macros and
modules.
For Macro and Module libraries, the .tre files have the same basic format as
Functions .tre files, except for the file descriptor at the beginning. Also, there is no
Modules item, only Macro and Module Definitions. Macro and module libraries can
be imported again, as needed.
For more information, refer For Block libraries, the .tre file must be imported and the runtime standard or
to the section, Monitoring. industry software must be downloaded to the controller. A mismatch of .tre file
libraries and the corresponding runtime software cause the controller to stop
executing when the controller is downloaded. To import a new block library, it is
necessary to export the entire configuration, then import it with the new library .tre
files located where the old files used to be.
560 of 1016
Configuration
A controller configuration is constructed by using the toolbox or by importing .tre
files containing blockware. To build the configuration using the toolbox:
• Create a controller
• Import the necessary libraries
• Insert blockware and hardware
For more information, refer Blocks correspond to a function block that exists in the runtime. These blocks are
to the section, Blockware used to make up macros. Blocks and macros make up tasks. A task(s) can be inserted
Concepts. into a module and any number of modules makes up a function. All of these items
are inserted into a configuration the same way.
Create/Delete Blockware
To create blockware into a configuration
1. From the Outline View, click a blockware item to highlight it.
Once an item exists, another item 2. From the Edit menu, select Insert First. Or, click the right-mouse button and
can be inserted by following the select Insert First. Depending on the item being configured, a dialog box
same steps, but select Insert displays to name and define the item.
Next.
Note If a command name is grayed, it indicates that the command does not apply to
the current situation or that you need to make a selection or complete another action
before selecting the command.
To delete a block(s) from a configuration

1. From the Outline View, click the desired item to highlight it.
Or click 2. From the Edit menu, select Delete. Or, press the Delete key.
561 of 1016
Functions and Software Libraries
A function or software library acts as a grouping mechanism for inter-related scales,
type, signal, macro and module definitions. Only functions have modules, which
contain the software downloaded to the controller. Each function or software library
can be exported to a .tre file with the default name, funcname.tre.
To insert a function into a configuration
Once a function exists, 1. From the Outline View, select Functions.
another function can be
2. From the Edit menu, select Insert First. Or, click the right-mouse button and
inserted by following the
select Insert First. The Function Name dialog box displays.
same steps, but select Insert
Next.
Enter a name with up

to eight characters
and click OK.
This item is inserted
into the Outline View
(shown below).
562 of 1016
To edit a function
1. From the Outline View, highlight the function.
2. From the Edit menu, select Modify. Or, right-click and select Modify from the
shortcut menu. The Edit Funtion dialog box displays.
Displays the default access level of Revision allows you to keep track
this function. of changes to the function
Use - This function will be used in definition. The form of the
code, but you will not be able to view revision must be V##.##.##A,
or change it where ## is at least two decimal
View - view this functions contents, digits and the final A can be any
but not change it. alphabetic character. If the
Change - you have total access to format is entered incorrect, the
this function. toolbox replaces the revision
string with V??.??.???.
The function name displays.

Displays the name of the .tre
file assocated with this
function. This field can be
modified during the export
process.
Enter the location of the help
file assocated with this item.
Item help is selected using
the right-mouse shortcut
menu.
prevent the file from being
exported during an Export
All command.

enable password protection.
Refer to the section, Locked
Items.
This button displays the
Change Password dialog box,
allowing you to set or change
the password to lock this item
when password protection is
enabled.
Enter a note to
describe the
function.
Note The “Access Protection” is independent of the “Password Protection” scheme.

Access Protection uses the Privilege level settings, and works in the same manner as
Macro Protection. See Chapter 2: Privilege/Password for more information.
Note As noted before, the above information for ‘Functions’ also apply to Software
Libraries.
563 of 1016
Type Definitions
Type definitions are enumerated data types, which can be used by pin or signal
definitions. An advantage of using type definitions is that the pin of a block, macro,
or module can be limited in scope to particular values or a range of values. Also, you
can select another controller name, instead of using the controller drop number.
To insert type definitions into a configuration
1. From the Outline View, click Type Definitions to highlight it.
Or click the right-mouse button 2. From the Edit menu, select Insert First. The Type definition dialog box
and select Insert First. displays to define the data type.
Note Once a type definition exists, another can be inserted by following the same
steps, but selecting Insert Next. The item can also be deleted.
The Type Definition dialog box is also used to edit existing type definitions.
To edit a type definition
1. From the Outline View, click the type definition name to highlight it.
Or double-click the type 2. From the Edit menu, select Modify. The Type definition dialog box displays
definition name. (refer to the next section, Define Type Definition).
564 of 1016
Define Type Definition
Define the type definition below.
Enter a name of up to 12
characters.
Enter a description of up
to 50 characters.
Select the basic data type that
this type definition is based on
(refer to the list below). Type
definitions are always based on
another data type.
Select the data entry restriction.

If Range, assign a minimum
and maximum range definition.
If Enumeration, define the
Value name and value.
To add an enumeration, enter a
name and value, then click
Add.
To modify, select the
enumeration, make changes,
and click Add.
To remove, select the
enumeration and click
Remove.
Basic Data Types

Bool - 8-bit Boolean (0 to 1)
Int - 16-bit signed integer (-32, 768..32,767)
Lint - 32-bit signed integer (-2,147, 483,648...2,147,483,647)
Float - 32-bit IEEE floating point (-3.4 + 38 to 3.4E + + 38)
Lfloat - 64-bit IEEE floating point (-1.8E + 380 to 1.8E + 308)
Collection Data Types
Analog includes all basic data types, except Boolean
Simple includes all basic data types
String is zero-terminated ASCII string (1 to 255 characters)
(Strings must be an array whose length equals the maximum
number of characters + 1 for the terminating zero.
565 of 1016
Predefined Type Definitions
Type definitions are used extensively with database settings. Some type definitions
obtain information specific to a particular process by getting it from the database.
To locate predefined type definitions
Or click 1. From the File menu, select Import.

2. From the Import dialog box, import the file Sysdata.tre.
3. From the Outline View, click the symbols next to the item System Data
and again next to Type Definitions to display the predefined type definitions
from the database.
566 of 1016
Scale Definitions
Scale definitions can be associated with signals. They are used primarily to scale raw
I/O into engineering units used internally by the blockware. For the controller, scales
can be created in the toolbox and put into the database.
On many large processes, scales are defined in the System Information device. If a
scale needs to be edited, System Information eliminates having to know which
binary working files to open.
To insert a scale definition into a configuration
1. From the Outline View, select Scale definitions.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Scale definition dialog box
button and select Insert First. displays.
This dialog box is also used to edit existing scale definitions.
To edit a scale definition
1. From the Outline View, select the scale definition name.
Or double-click the scale 2. From the Edit menu, select Modify. The Scale definition dialog box
definition. displays.
Note Both scale and type definitions can be defined locally to a signal or pin and
display as -Custom- in the Signal Definition or Module Pin dialog list boxes.
These local definitions do not have names and do not display in the list boxes for
other signals. Also, they cannot be put into the database because they do not have a
name.
Enter the Minimum and Maximum

values of each system and Raw to
provide the conversion infromation.
Measurement System names

(in this case US and METRIC)
are defined in the System
Interface properties dialog,
under “Measurement Systems”.
Refer to Chapter 7, Create/
Modify System Information,
System Device dialog box.
Enter the Unit names for each

system (five-character limit).
Select the Precision from the
list boxes.
Enter a description of the

scale definition (50-
character limit)
567 of 1016
Signal Definitions
Signal definitions are used to define signals associated with a Function or Macro and
Module Library.
To insert signal definitions into a configuration
1. From the Outline View, expand Functions or Macro and Module Libraries.
Click
Signal
Definitions
2. From the Edit menu, select Insert First. The Edit Signal Definition dialog
box displays. This dialog box is used to define the signal definition (refer to the
next section, Define Signal Definition).
To edit a signal definition
1. From the Outline View, click the signal definition name to highlight it.
Or double-click the signal 2. From the Edit menu, select Modify. Edit the signal from the Edit Signal
definition name. Definition dialog box.
For more information, refer to Signal definitions also display when you update the database. When you put signal
Chapter 11, Signals and the information into the database, three items, which hold lists of signals, are inserted
Database. under System Data (in the Outline View):
568 of 1016
Define Signal Definition
Define the signal definition below.
Enter the name of the signal with at least one and up to three regions followed by a signal
name. Separate the region(s) and name with a backslash, such as reg1/ signal_name. The
Region can be six characters, maximum; the signal name can be 12 characters maximum.
Enter a descriptive Note below the name with up to 50 characters.
The signal description can be

in a second language. It is not
necessary to have a description
in both description fields. See
the section Create a Controller,
General Tab to edit a description
in both languages.
Type lists all the type

definitions and simple
types for this device.
From the dropdown list
select Custom to create
a locally defined data
type. Click Edit… to add
the specific information
for that locally defined
data type.
Enter a scale definition
for this device. From the
dropdown list, select
Custom to create a
locally defined scale.
Click Edit... to view
predefined scales.
FALSE is the default, if

this is not a Control
Constant. Select TRUE
for signal definitions and
module pins that can be
viewed as a group and Connection allows you to Enter the length of the signal, Select these options to make the
exported to a .csv file. connect signal definitions to if it is an Array and the initial module pin a Hold, Event, I/O, or
Select READ to restrict other signals. Enter the name of Value for. the elements. If the Network. If the pin is connected
online changes to this the signal in the text box or click Array size is greater than to a Status_S signal and used in
.
module pin. Browse… When one signal is one, a list box of the initial a task, that task is scheduled
connected to another, they share values for the array elements when the value of the signal
the same place in memory. displays above Value. changes, as well as the normally
scheduled execution times.
If a signal has the Network check box selected, then this signal is added to an EGD
Exchange under two circumstances: (See Chapter 9, EGD Interface, EGD
Exchanges, Internal Exchange Settings.)
From the Outline View, right-click an EGD Exchange and select Add Network
Signals. This adds all signals flagged as network signals (but not already connected)
to the Exchange.
Define an Exchange to Receive Network Signals, and then use the command Put to
database.
569 of 1016
Note If a Function, or Library module is protected as ‘View only’, then a user at
privilege level 2 or above can modify some of the signal attributes. The available
attributes are listed in the “Edit Module Pin” section dealing with the ‘Pin Override’
feature.
Note The second language description is used for Turbine systems that use the
language translation feature of the Turbine Control Interface (TCI). Both
descriptions are stored in the SDB with the Put Into Database command. The TCI
Phrase Translation file is also updated. TCI uses this file to translate from language 1
to language 2 respectively.
570 of 1016
Tuning Variables
A tuning variable is a special signal with high and low limits, which is used as a
constant. Initial values and run time changes are bound by the high and low limits.
Only float, lfloat, int, and lint

signals can be a tuning
variable.
The high and low limits apply to setting Select this option to name this signal a
the initial value of a signal and also when tuning variable. If the Tuning Variable
making online changes to the value of a checkbox is not checked, then the high
signal in a controller. and low limits for initial value will not be
displayed.
Note You must be at privilege level 4 to make a signal a tuning variable and set the
initial value limits.
For tuning variables that are defined to be arrays, high and low limits can be defined
for each element in the array. In the example below, the second element has a low
limit of 90 and a high limit of 200 (with an initial value of 100). The first or third
elements can have totally different high and low limits and a different initial value.
571 of 1016
The summary screen for the tuning variable ‘test\tune1’ shows (see below) the
different initial values and the tuning high limit for each element in the array.
572 of 1016
Alarm Tab
The Alarm tab is illustrated below.
Check to make the

Alarm a signal (only
available with a
Boolean signal).
The Alarm Class

dropdown lists all
available alarm
classes. You must
first use the
command, Get from
Database. PRC is
the default.
To select an alarm in
CIMPLICITY, enter
the full path or the
file name (256-
character limit) in
CIMPLICITY Screen
or click Browse... .
573 of 1016
Limits Tab
Note The Limits tab is only available for turbine projects (including Mark VI,
EX2100, Static Starter, and ISC in a turbine device). For ISC devices, refer to the
section, General Tab.)
Setpoint Limits are used in CIMPLICITY to limit

the maximum and minimum values that can be
set for that signal in a CIMPLICITY screen.
Display Limits are

defined in the Scale
definition as the
Native System
maximum and
minimum. You can
override the Scale
definition display
limits by enabling the
Signal display limits
and entering new
limits in the Signal.
Click to select and

set the Deadband
value.
Note All values entered are in the signal’s

Measurement System.
574 of 1016
Table Definitions
A lookup table is a reference Many complex mechanical issues can be modeled using lookup tables. The
table that maps an index or controller implements these tables using table definitions. A table definition is
key to a value to be looked up presented like a signal definition in that it is named in the same way and is used in
and returned. It is often used instruction blocks. However, table definitions have other characteristics as required
as an alternative to lengthy by the Control Specifications from GE Aircraft Engines for LM Turbine
runtime calculations. Applications for the Mark VI, and can be used by the Innovation Series Controller.
A table definition consists of a name, note, identification string, revision string,
engineering units, data array dimensions, adjust flag, minimum and maximum Z
values, and data. The data consists of one or two independent arrays (X and Y) and a
dependent array (Z).
Tables with a single independent array are sometimes called univariate tables and
consist of X and Z linear arrays of the same length. Univariate table block pins have
a data-type of UniTable_F. Tables with two independent arrays are sometimes called
bivariate tables and consist of X and Y linear arrays and a Z two-dimensional array.
Bivariate table block pins have a data-type of BiTable_F. Bivariate table definitions
display in the Summary View as follows:
The leftmost column

contains the X (down) array
values.
The top row contains the Y

array values.
The remainder of the cells

are Z array values.
The Z values are arranged
such that the intersection of
the X and Y values give the
corresponding Z value.
575 of 1016
Table definitions
are part of the
item Functions.
They can only be

inserted into the
configuration by
importing a table
definition .tre file.
This .tre file is
usually included in
the configuration.
Import Files
To import files
1. From the Outline View, select Table Definitions, then right-click the table
definition name.
2. From the pop-up menu, select Import Table Tree File.
Table definitions can export contents to a comma-separated variable (.csv) file.

These files can then be merged back into the controller configuration.
576 of 1016
To export or merge a table definition .CSV file
1. From the Outline View, use the right-mouse button to select the name of the
Table Definition to be exported.
2. From the pop-up menu, select either Export Table .CSV File or Merge
Table .CSV File.
3. Select or enter the .csv file name. The default file name displays, based on the
table’s name of the form region_region_region_signalname.csv.
Edit Table Definition

Once a table definition exists, it can be edited. The Table Definition Edit dialog
box consists of a Properties tab and an Initial Values tab. If the controller is online,
an additional Live Data tab displays in front of the Properties tab. The tab displays
live values that can be modified and downloaded.
To edit a table definition
1. From the Outline View, select the table definition name.
Or click the right-mouse 2. From the Edit menu, select Modify. The Table Definition Edit dialog box
button and select Modify. displays (Refer to the next two sections, Properties Tab and Initial Values Tab).
Properties Tab
Define table properties below.
The name of the table displays

automatically and cannot be edited.
It is also used on block pins to which
this table definition is connected.
This is the name of the tree file that

this table definition came from, if it
was not part of a function .tre file.
This field is also modified as a result
of exporting the table definition to a
separate .tre file.
Enter a description of the table

definition.
Enter a free form text identifier.
Enter a free form text revision

number or date.
Enter a free form text describing the

engineering units of the X, Y and Z
data values.
Enter the minimum and maximum for the Z data values. These
Click OK to save
values are used by the toolbox to limit the values that can be
the changes.
entered into the live or initial values. The values are used by
the controller runtime software to limit the output of blocks that
use these Z values.
577 of 1016
Initial Values Tab
The Initial Values tab contains all the initial values for the table definition. The cells
are arranged in a table format (as in the Summary View). Edit the values as follows:
Click on the cell to edit in

the table.
To navigate through the

table, click on a cell and
press <Tab> to go right,
<Shift><Tab> to move
left . Press the up and
down arrow keys to move
up and down in the cells.
578 of 1016
Live Data Tab
The Live Data tab is illustrated below.
Click on the cell to edit.

To navigate through the
table, click on a cell and
press <Tab> to go right,
<Shift><Tab> to move left.
Press the up and down
arrow keys to move up and
down in the cells.
Click to save the values to

the configuration.
Click to update the Live

values grid with the current
value in the controller.
Click OK to save changes

to the configuration. Save
to Initial Value must be
clicked also.
Click Cancel to undo
changes made to
properties and values.
Download and Save to
Initial Values are not
canceled.
Click to download the modified values to the controller.
579 of 1016
Module Definitions and Modules
Module Definitions and Modules are items in the hierarchy that can be used to divide
blockware; they can also be used to reuse blockware.
Instanced and over-ride

modules are defined under
Module Definitions.
Inline modules are defined

under Modules.
Insert Module Definitions and Modules

When a Module is inserted, the type must be specified as defined or inline. Defined
types are existing Module Definitions and inline modules are determined later.
Module definitions are reusable and have a revision number to keep track of changes
to the modules.
Both configuration items are inserted by using the same procedure. When both are
inserted, they contain another level item called Pins (refer to the section, Module
Pins). At this level, you can insert all of the Tasks for the Module Definition or
Module (refer to the section, Tasks).
To insert a module definition or module into a configuration
1. From the Outline View, select Module Definitions (found under the item
Functions or Macro and Module Libraries) or Modules (found under the item
Functions).
Or click the right-mouse 2. From the Edit menu, select Insert First. The Module Definition Name or
button and select Insert First. New Module dialog box displays (refer to the sections Name Module
Definition or Name Module).
580 of 1016
Name Module Definition
Define the module name below.
Enter a name for the item you are

inserting. Click OK.
The name displays under the item

you are inserting in the Outline View.
Name Module
The New Module dialog box is illustrated below.
Select an existing
module definition.
Enter a note for
the module.
Check Inline to
insert an empty
inline module and
Enter a name with up define it later.
to three regions
separated by
backslashes. (The
pins, inserted un the
item Pins, use this
same region as a full
name.)
581 of 1016
Edit Module Definitions and Modules
Once a module is inserted, it can be edited. The same dialog box is used for a module
definition or module.
To edit a module definition or module
1. From the Outline View, select the name of the module or module definition.
2. From the Edit menu, select Modify. The Edit Module or Edit Module
Or double-click the name with Definition dialog box displays. The appropriate fileds for the particular module
the right-mouse button. type are enabled (refer to the next section, Edit Module Definition or Module
Dialog Box).
Select a module (such as HMI_1) and turn on

Tracking. The Summary View contains the
name and scheduling of the selected module
and a scrolling list of the tasks in the module.
When the toolbox is online

and communicating to the
controller, the text in the task
list turns green and the
online Heartbeat and Enable
Value display in the column.
582 of 1016
Edit Module Definition or Module Dialog Box
The Edit Module dialog box is illustrated below.
Check to change an instanced module to an over -ride module. An instanced

module has a colon ( : ) between the region names, such as reg \reg:module.
The over-ride module has an at symbol @, such as reg\reg@module. The
Over-ride checkbox can toggle to change an edited module definition back
to the original. Remove the X and perform an instance. Any custom changes Definition Revision records
made to the module when it was overridden are deleted. the revision of this module's
definition which resides in the
Module and Macro Library.
Module Revision
tracks changes to this
module. The form of
the revision must be
V##.##.##A, where ## is at least
two decimal digits and the final A
can be any alphabetic character.
If the format entered is incorrect,
the toolbox replaces the revision
string with V??.??.???.
Click this button to uncheck the Pin
Override enable checkbox on all
pins under this module. Overridden
pin data is lost unless the module
itself is over-ridden. See the Edit
Module Pin section for details on
the Pin Override feature.
Select the module scheduling
base period. The associated
over-ride check box is only
enabled for instanced modules.
Check this box to make the fields
behave like the connection of a
module pin (the information of
the module instance is not
replaced when it is re-instanced).
Select the module scheduling
base skew. The associated Over-
ride check box is enabled only
when the module is instanced.
Enter a name for the Graphic Enter a name for the Help file
Window or Windows metafile associated with this module.
, module. Enter a description
associated with this Select the module definition or of the module.
This is accessed by selecting instance in the outlineand then
a module in the Outline click Item Help from the right-
View, then selecting the click pop-up menu to display the
Detached Summary View. Help file entered here.
583 of 1016
Module Pins
Module pins are parameters for a module. They are inserted under the item Pins.
(Pins are automatically created when the item Module is inserted.)
To insert a pin into a Module
1. From the Outline View, under the item Modules or Module Definitions, click
beside a module to display the item Pins.
2. Select Pins.
Or click the right-mouse 3. From the Edit menu, select Insert First. The Module Pin Name dialog box
The Module Pin Name dialog box is illustrated below.
Enter a name for the item you are inserting.

The name must begin with an alphabetic
character and contain a maximum of 12
characters. Click OK.
The name displays under the item you are

inserting in the Outline View.
584 of 1016
Edit Module Pin
To modify a module pin
1. From the Outline View, select the module pin.
Or double-click the name with 2. From the Edit menu, select Modify. The Edit Module Pin dialog box
the right-mouse button. displays.
Note For instanced pins, only the field, Connection is active.
Refer to the section, Module This dialog box is used to edit both the Module and Macro Pins. Inserting and editing
Definitions and Modules. module pins is limited to module definitions, inline modules, and override modules.
Module pins are referenced in the module’s blockware using only the pin name. By
maintaining the use of this name exclusively, the modules can be re-used. This same
method is used to make macro definitions re-usable.
This check box is enabled for pins that are in an‘instanced’
module. When checked, certain attributes of the instanced pin
can be modified. The modifications will be retained even after
re-instancing the module.
Enter a name with up to 12

characters (must begin
with an alphabet character).
Module pin names do not
include regions. The
regions for signals
associated with module
pins have the same region
as the module. The text
box below the name allows
you to enter up to 50
characters to describe the
pin.
FALSE is the default value.

Select TRUE for signal
definitions and module pins
that can be viewed as a
group and exported to a
.csv file. Select READ to
restrict online changes to
this module pin (although it
is still viewed as a normal
control constant).
Select this box to

mark the pin as a
DLAN+ event.
Enter the connection Select these options to make the module pin a Hold, Event point. If the pin
path for the pin. is connected to a signal and used in a task, then that task is scheduled to
run when the value of the signal changes, as well as at the scheduled run
times. The pin can also be checked to show that it is an I/O, Network
(EGD), Tuning Variable, or Virtual HMI Point.
585 of 1016
Override Enable check box
The Override Enable check box is enabled for pins that are in an instanced module.
When selected, certain attributes of the instanced pin can be modified. The
modifications will be retained even after re-instancing the module. The Override
Enable check box is enabled, and retains its state, even if the module is overridden
(at the module level). The attributes that can be modified are listed below:
Module pin tab
• Override Enabled and checked
• Pin Note (description)
• Scale
• DLAN+ Event checkbox
• Hold, Event check box (Boolean only)
• I/O, Network, Virtual HMI point check box
• Value
• Connection
Alarm tab (Booleans only):
• Alarm check box
• Alarm class (when alarm checkbox is checked)
• CIMPLICITY screen (when alarm checkbox is checked)
Limits tab (non Booleans only):
• Display Limits enable and values
• Set point Limits enables and values
• Dead band enable and values
The following attributes are not enabled
• Name
• Type
• Array Size
• Tuning Variable
• Control Constant
If the Override enable checkbox is unchecked, then the pin attributes will revert to
the values from the library definition. An Undo Pin Override button is available in
the module edit dialog to remove the pin override for all pins under the module.
Note If a function, or library module is protected as View only, then a user at

privilege level 2 or above can modify the same pin attributes that are available with
the Pin Override feature. This is also true of Signal definitions. It is NOT true for
Macro pins or module pins under a Library.
586 of 1016
Alarm Tab
Check to make the

available with a
Boolean signal).
The Alarm Class

dropdown lists all
available alarm
classes. You must
first use the
command, Get from
Database. PRC is
the default.
CIMPLICITY, enter
file name (256-
character limit) in
CIMPLICITY Screen
587 of 1016
Limits Tab
The Limits tab is shown below.
Display Limitsare
defined in the scale
definition as the
Native System
maximum and
minimum. You can
override the scale
definition display
signal display limits
and entering new
limits in the signal.
Click to select and

set the Deadband
value.
Note All values entered are in the signal's native Measurement System.
588 of 1016
Macro Definitions
Macros provide a way to re-use blockware on a lower level than modules. Macros
are only instanced and never inline or override. Therefore, all macros must be
inserted under the item Macro Definitions to be used in blockware.
To insert a macro
1. From the Outline View, select Macro Definitions.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Macro Definitions Name
button and select Insert First. dialog box displays.


589 of 1016
Edit Macro Definition
To edit a macro definition
1. From the Outline View, select the macro definition name.
2. From the Edit menu, select Modify. The Edit Macro Definition dialog box
displays.
Revision allows you to keep track of changes to the macro definition. The
form of the revision must be V##.##.##A, where ## is at least two decimal
digits and the final A can be any alphabetic character. If the format is
entered incorrect, the toolbox replaces the revision string with V??.??.???.
Edit the name that was created
in the MacroDef Name dialog
box. It must not have more than
12 characters.
Enter the name of the pin that
enables the macro or select
from a list of defined pins in the
drop-down list box.
Enter the name of the Windows

Metafile associated with this
macro. This is accessed by
selecting a macro in the Outline
View and then selecting the
Detached Summary View.
Enter a name for the help file

associated with this macro or
click Browse to search.
Selecting the macro definition
or instance in the Outline
View and then clicking Item
Help in the right-click pop-up Displays the default access level of this macro.
menu displays the same help Use - you can use this macro in code, but not view or change it
file entered here. View - you can use this macro as well as view its contents
Change - you have total access to this macro
590 of 1016
Macro Pins
Macro pins are the parameters for a macro. They are inserted under the item Pins.
(Pins are automatically created when the item Macro is inserted.)
To insert a pin into a Macro
1. From the Outline View, under the item Macro Definitions, click
beside a module to display the item Pins.
2. Select Pins.
Or click the right-mouse 3. From the Edit menu, select Insert First. The Macro Pin Name dialog box
The Macro Pin Name dialog box is illustrated below.


591 of 1016
Edit Macro Pin
To edit a macro pin
Or double-click the name with 1. From the Outline View, select the macro pin.
the right-mouse button.
2. From the Edit menu, select Modify. The Edit Macro Pin dialog box displays.
Note For instanced pins, only the Connection field is active.
Change the name created in the Macro Pin Name dialog box. It
can be up to seven characters long and must begin with an
alphabetic character. Macro pins are not named with regions
included. The text box below the name allows you to enter up to
50 characters to describe the pin.
Note: Sometimes this text box is used by HMI to describe
diagnostic messages.
Select from a list of data types,
made up from all of the type
definitions and basic types for this
controller. To create a locally
defined data type, select Custom
from the drop-down list. Then click
Edit... to add the specific
information for that locally defined
data type.
Select how the pin is used in the

macro: Input, Output, Local (not
intended to be used outside of this
module), Const, and State (read
and write). Usage is not verified
during validation. Usage also
indicates if the pin displays on the
left or right of the macro block. An
Input or Const display on the left of
the macro block; Local, Output, or
State display on the right.
Visibility specifies the conditions

under which the pins are viewed on
block diagrams. Always (pin is
always displayed), Never (pin is
never displayed), Used (pin is Array size and Value define the arry length Enter the name of the signal that
displayed when connected to of the signal (if it is an array) and the initial the pin will be connected to, or
anything), or Wired (pin is value for the elements. If the array length click Browse... to select from
displayed only if connected to is greater than one, a list box of the initial the Signal Selector dialog box.
another signal. This option is not values for the array elements displays
always applicable (see the Option above the Value list box. To edit this box,
menu, Block Diagram.) click on a value in the box, then enter a
value in the Value list box or select from
the drop-down list.
For more information, refer Note For Used and Wired pins, if just a macro instance is selected in the Outline
to the section, Macros, Macro View with tracking on, the Summary View displays all pins regardless of their
Definitions, and Macro Pins. visibility status.
592 of 1016
Tasks
Refer to the section, Tasks Tasks are both the basic scheduling unit and a blockware grouping mechanism in the
and Scheduling. controller. Tasks are inserted into modules and can be modified.
To insert a task into a Module
1. From the Outline View, under the item Modules or Module Definitions,
select a module name.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Task Name dialog box
The Task Name dialog box is illustrated below.


593 of 1016
Edit Task
To edit a task
1. From the Outline View, select the task name.
Or double-click the right-mouse 2. From the Edit menu, select Modify. The Edit Task dialog box displays.
button.
Enter a unique name of up to

12 characters.
Enter the task description.
Change the execution time

slice that this task executes.
This can distribute the
execution of different tasks,
so that overruns do not
occur. The possible values in
the drop-down box depend
on the value selected as the
Period Mult.
Period Mult determines how
often a task runs. The period
multiplier times the module's
period equals the period that
this task executes. This is
Event 1,2,4, or 8. (Event
generates a multiplier of zero Enable option buttons allow selection of a value for the task enable.
and the task only runs if an
Event occurs.) Always makes the enable True.
Never makes the enable False.
Pin enables the drop-down list box to select the names of this
module's pins.
Signal changes the drop-downlist box to display the signal.
Selector dialog box selects a signal.
Tip When either Pin or Signal is selected in the Enable options, a module pin or
signal name can also be typed in.
594 of 1016
Enable or Disable Task
Do not enable/disable application code tasks unless you have a

complete understanding of the consequences.
The following screen displays tasks in the Outline View. With Tracking on, it shows
how the tasks can be displayed in the Summary View.
Module, HMI_1
Tasks, SigGen and

geni
Click on the Module
Click on the Task name, such as
name (SigGen) to HMI_1 to display
display its position in Task information in
the block diagram the Summary View.
(Summary View)
To enable or disable a task
Or click 1. If not already online, go online. From the Device menu, select Online.
2. The Go Online dialog box displays.
3. From the Outline View, double-click the task name. The Send Value dialog
displays.
Enter the Value to

enable or disable
the task.
Select this box to

prevent blockware
from overwriting
the Value.
Toggle Value inverts the current

value and sends it to the controller
without closing the dialog box.
595 of 1016
Blocks and Macros
Blocks are the basic programming construct for blockware. Macros can group blocks
so that they look like a single block. Once a macro is defined, blocks and macros are
connected similarly to make tasks or other macros. The following sections describe
how block and macros can be connected to create functional controller software.
Insert and Delete
The hierarchy for block and macros can be seen in the Outline View shown below.
Macro
Task
Block
Macro
A macro in the item Macro Definitions displays as mac2. When the macro is
inserted in a task or another macro, it displays as a block because the name is
preceded with a block number and a colon (40:mac2). The pins display directly
under the macro name in its instanced form, instead of under the item Pins under the
macro name. Also, the item Blocks displays on the same level but below the
instanced macro items. Only one block or macro can be inserted at a time.
To insert a block or macro into a task
1. From the Outline View, select a task name.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Select Block Type dialog box
3. From the list, Category, select a block category, then select a block from the
block library. (The center text block displays either the Library or the Function
This process does not apply to name.) Or, from the list Macros, select a macro.
modules that are instanced.
4. Click OK or double-click the block/macro. The item is inserted under Task
name.
To delete a block or macro from a configuration
1. From the Outline View, select the desired item.
Or click 2. From the Edit menu, select Delete. Or, press the Delete key.
Note Blocks or macros that cannot be deleted (those that belong to either a macro or
an instanced module) disable the delete commands when they are selected in the
Outline View.
596 of 1016
Select Block Type
The Select Block Type dialog box is illustrated below.
Macros list box is selected in the same way as

the Block categories.
This number identifies the block

within the task or module, which
it is being inserted into. The
number can be modified as long
as it is greater than the previous
block and less than 89999.
This list displays the standard or

industry block library, which are
grouped into similar functions.
Select one or more categories
and the list box on the right
changes to display all the blocks
in that category(s).
The All button displays all the
blocks. The None button displays
none of the blocks.
The blocks that display in this list

box can be inserted into the task.
Select the block and click OK or
double-click the name of the
desired block.
Note is a read-only field, which displays a description of the block or
macro selected. Scroll it by clicking the box so that the cursor
displays in the note text, then use the Page Up/Page Down or arrow keys.
Rubber Blocks
When a block in inserted, all the block pins are included. The exceptions are blocks
with a variable number of pins, known as rubber blocks, which insert only the first
set of pins. The block pins that are active only when they display are called rubber
pins. These blocks are handled differently because their functions can act on a
number of sets of pins, depending on how many pins are present. By showing only
the active pins, the diagrams are less cluttered and both the toolbox and runtime
require less memory.
An example of a rubber block with rubber pins is the _BENG block, which is a relay
ladder diagram (RLD). The RLD can have from one to 16 different signals used in
the ladder. The block is a rubber block because it can stretch from using only one
input to using up to 16 inputs.
597 of 1016
Connect Pin
For more information, refer To connect the pins of a block or macro, use the Connect Block Pin dialog box or
to the section, RLD Editor. the Edit Block/Macro Connections dialog box. Boolean engine blocks can also
be connected using the RLD editor, which is the default for Boolean engine blocks.
To connect/edit a pin
1. From the Outline View, select a block or macro. The block diagram displays in
the Summary View.
2. From the Summary View, double-click the desired pin. The Connect Block
Pin dialog box displays.
From displays the selected block number and pin

the Type, and the Usage of the pin being
Enter the value this block or

instanced macro pin will be
connected to.
The following command

select the pin connection. (The
Pin buttons all display thePin Select
dialog box, described below.)
Signal displays the Signal

Selector dialog box to select a fully
qualified signal.
Module Pin is only enabled when editing
a task in a Module or Module
The name is a pin name only, so the
signal name uses the module region
its region.
Macro Pin is only enabled when editing
a macro definition. It lists macro pins, which can be connected to this
Block Pin is always enabled. This command provides a list of all
possible block pins that are on the same level of blockware (either in
same task or macro definition). The names display as block
colon, pin name (100:IN).
Inv places a tilde (~) in front of the pin. A ~ placed before any
inverts the signal for the connection being made. This command is
enabled for Boolean pins.
Create Pin allows you to create a macro or module pin that is not in
Pin Select list. It invokes the Edit Module Pin Definition dialog box with
name and type preset to the values matching the current pin
connected. Clicking OK in Edit Module Pin Definition creates a module
if the block/macro pin is in a Task or creates a macro pin if the
macro pin is in a Macro
The drop down list provides enumerated data types (including
variables). Inserting an enumeration in the To text box gives the pin
initial value. Initial values can also be connected to block and macro
by entering a valid numerical value for pins with a simple numerical
type or type definitions based on a numerical data
598 of 1016
Edit Block Connections
The Edit Block and Edit Macro Connections dialog box allow you to edit and
connect block and instanced macro pins for the entire block or macro. The dialog
box accepts inputs on a pin-by-pin basis. This means that once you enter the
connection text and either press Enter or select another pin, the text is applied to the
pin.
To edit all pins in a block or macro
1. From the Outline View, select the block or macro pin. The block diagram
displays in the Summary View.
2. From the Summary View, double-click the desired pin. The Edit Block
Connections (or Macro Connections) dialog box displays.
This is a list of all the pins of the block
being edited. Click on the pin to be This is the instance name Enter a description for every
connected/edited. The Pin name of the block or macro. instance of the block.
displays in the read only box below the
pin names.
This text box allows you to enter the

pin to connect. The command buttons
can also be used to select the pin.
Or, when a single pin is selected for
connecting, it displays in the text box
below the Connection list box. Based
on the pin type, specific help is then
displayed beneath the text box. For
example, for the equation (EQUAT)
pin on a Math block, the help lists all
the mathematical operations that can
be performed, such as +, -, *, / ABS,
or SQR. Also, the drop-down list in the
bottom right-hand corner displays the
required data type for that pin, such
as Float or Boolean.
Signal displays the Signal Selector

dialog box to select a fully qualified
signal.
Module Pin is only enabled when
editing a task in a Module or Module
Definition. The name is a pin name
only, so the full signal name uses the
module region as its region.
Macro Pin is only enabled when editing a macro Block Pin is always enabled. This command
definition. It lists macro pins, which can be provides a list of all the possible block pins that are
connected to this pin. on the same level of blockware (either in the same
Create Pin allows you to create a macro or task or macro definition). The names display as
module pin that is not in the Pin Select list. It block number, colon, pin name (100:IN).
invokes the Edit Module Pin Definition dialog Inv places a tilde (~) in front of the pin. A ~ placed
box with the name and type preset to the values before any signal, inverts the signal for the
matching the current pin being connected. connection being made. This command is only
Clicking OK in Edit Module Pin Definition creates enabled for Boolean pins.
a module pin if the block/macro pin is in a Task
or creates a macro pin if the block/macro pin is in
a Macro Definition.
599 of 1016
Relay Ladder Diagram
From the Options menu, select Boolean engine blocks can be connected differently than other blocks and macros.
Settings and click the option, Use These blocks perform logical operations on inputs to set the output to some value.
RLD editor. The operation is determined by a Boolean equation, which uses symbolic pin names
as operants. The Relay Ladder Diagram (RLD) editor transforms the Boolean
equation into a relay ladder diagram, where symbolic relay contacts are arranged so
that power flows to the symbolic output coil on the right from the power bus on the
left when the relay contacts in between make a complete connection.
Arranging the contacts on the drawing area using the mouse creates Boolean
equations. Select a drawing mode and place the elements on the grid by clicking the
mouse in that square. Contacts connected horizontally are logically ANDed and
those line connected vertically are logically ORed. The names of signals or pins are
connected with contacts in either select mode or one of the contact modes by double-
clicking the contact or coil that receives a name.
RLD Editor
To connect a block using the RLD editor
1. From the Summary View, select a Boolean block (titled BENG or BENG_D).
Or double-click the block 2. From the Edit menu, select Modify. The RLD editor displays.
name.
600 of 1016
RLD Editor Toolbar Commands
Click… To…
Start the edit mode, where contacts can be moved, copied, and deleted.
Select a square, place the cursor over a grid square and click the left mouse button.
Connect a contact to a signal or pin, double-click a contact. The Connect Contact dialog box
displays.
Move a contact, click the contact and drag-and-drop to the desired grid square.
Copy a contact, press and hold the Ctrl key, click the contact, and drag and drop to the desired
grid square.
Delete a contact or line segment, click a grid square and press Delete.
Start the drop mode, where a normally open contact can be dropped onto the grid square.
Connect a contact to a signal or pin, double-click a contact. The Connect Contact dialog box
displays.
Start the drop mode where a normally closed contact can be dropped onto the grid square.
Connect contacts, where as the cursor moves through the grid area, a green tracer segment
indicates where a line segment can be added. A red tracer segment indicates where a line
segment or a contact can be deleted (contacts cannot be moved or copied in this mode).
Validate and compress the RLD. Errors are identified with row and column numbers in the grid
square(s).
Insert a row at the currently selected grid square.
Insert a column at the currently selected grid square.
Select a pin and edit the note and connect any non-RLD related pins. This button displays the
Edit Block Connections dialog box.
Tip The drop-down list RLD Size provides different font sizes that enlarge or
reduce the RLD editor Work Area. If the Work Area is larger than the RLD window,
scroll bars display to access and view the entire workspace.
Renumber and Rename, using Window Methods

To maximize productivity, the Starting at the bottom of the controller hierarchy, blocks and macro instances can be
toolbox uses many standard cut-and-pasted whenever it is possible to insert one or the other. The number
Windows methods, such as associated with each block or macro is automatically applied by the toolbox. The
cut-and-paste or drag-and- default increment (Step by:) is 10 for blocks or macros pasted at the end of a task.
drop. However, when a block or macro is pasted between two existing blocks or macros, it
is assigned a number halfway between the numbers of the two existing blocks or
macros. Blocks in a task or macro definition can also be renumbered in groups.
601 of 1016
Block Flow Diagram
The block flow diagram displays the links that connect blocks and macros in a task, a
macro definition, and the block level of a macro instance. The diagram is viewed in
the Summary View (and also in the Detached Summary View, a stand-alone version
shown below). Block connections and editing can be performed from both views.
The block diagram has several viewing options.
Refer to the section Using the To select block flow diagram viewing options
Toolbox.
From the Options menu, select Settings, then select the Block Diagram
tab. These settings determine how the blocks display in the Summary View.
Edit the display or connect blocks from this view as follows:
To… From the Block Flow Diagram…

Display the RLD editor Double-click the Boolean engine block name.
Display the Edit Block Connection dialog box Double-click the block or macro name.
Display the Connect Block Pin dialog box for that pin Double-click the pin of a block.
Highlight the connection of a pin to another pin Click the pin itself or the area adjacent to the pin name reserved
for the pin connection.
Connect a module pin already connected to a block pin Click the module pin, drag-and-drop it on the pin to connect it to.
Modify a live value With the controller online, double-click the green value next to
the pin.
Tip Instead of using the Connect Block Pin dialog box, click a pin inside the
block work area. Drag-and-drop the pin onto the pin of another block.
602 of 1016
Alarm Tab
Check to make the

available with a
Boolean signal).
The Alarm Class

dropdown lists all
available alarm
classes. You must
first use the
command, Get from
Database. PRC is
the default.
CIMPLICITY, enter
file name (256-
character limit) in
CIMPLICITY Screen
603 of 1016
Limits Tab
The Limits tab is shown below.
Display Limitsare
defined in the scale
definition as the
Native System
maximum and
minimum. You can
override the scale
definition display
signal display limits
and entering new
limits in the signal.
Click to select and

set the Deadband
value.
Note All values entered are in the signal's native Measurement System.
604 of 1016
Device Menu Commands
This section describes the following Device menu commands:
• Put Into Database and Get From Database let controllers share signals with
other controllers on the network.
• Validate confirms that a configuration is ready to build Pcode.
• Build creates a Pcode, a symbol table file, and a compressed Mark VI file for
the configuration.
• Download sends configuration components to the controller.
Database Commands
For more information, refer to Put Into Database writes signal and topology information to the database. Get
Chapter 11, Signals and the From Database reads other controller’s information from the database and
Database. includes it in the controller configuration. Both commands can be performed as Full
or Incremental. The toolbox must also put diagnostic symbol information into the
database for other controllers in the system.
To Put Into Database or Get From Database
If this command is not 1. From the Device menu, select either Put Into Database or Get From
available, verify the database Database.
and server name entered in
2. Select Full to include all information or Incremental for specific information.
the Database options dialog
box (refer to the section, The Put Into Database and Get From Database commands allow controllers to
Using the Toolbox). share signals with other controllers and drives on the network. For example, a RUN
signal from a controller can be used to tell an AcDcEx2000 to run. The controller
creates and puts the signal into the system database. The AcDcEx2000 gets the
signal information from the database for that signal. When the controller issues the
RUN command, the AcDcEx2000 sees the signal on its page and takes the
appropriate action. The following table defines what information can be changed in
either the controller or the database by these commands.
Innovations Series Controller Database Interface
Information Get from Database Put into database Put Topology into Put Symbols
without Topology Database into
(USDB only) Database
DLAN+ Signals yes yes yes N/A
Ethernet Signals no N/A yes N/A
Signal Symbols no no no yes
Device Name no no yes N/A
Device Number yes no yes (assigns if = 0) N/A
Network Name yes no yes N/A

Network Number yes no yes (assigns if = 0) N/A
Scales yes yes yes N/A

System data type yes no no N/A
definitions
605 of 1016
Validate
Validate confirms that a configuration is ready to build Pcode. Validation status
displays in the Outline View by the color of the text. Valid items are in black text
and invalid items are in red text. When an item is invalid, the item that owns the
invalid item is also in red text. This status expands up each level, so that the
drive/controller (name) item of an invalid configuration is always red.
In the controller, validating checks connection compatibility, data types, equations,
hardware, and such, which must be correct to build and download a controller.
To validate an item
1. From the Outline View, select an item(s).
Or click 2. From the Device menu, select Validate.
3. Select either All to validate the entire drive/controller or Selected to validate
the highlighted item and all items in the levels below.
If an error(s) is found, it displays in the Log View located below the Outline View.
Double-click an error to go to the item in the configuration that was not validated.
Build Pcode and Symbols

When a controller item is valid, a Pcode file (.pcd) and symbol table file (.sym) can
be built (created). Both are built by the toolbox and can be downloaded to the
controller to change the configuration.
A symbol table is required to place signal information in block diagnostic messages
for the OC2000 and MM2000. This table consists of a list of the signal names with
the address token and a description. This is the same information that goes into the
database when putting diagnostic information into the database, excluding block
notes for the diagnostic detail.
To build Pcode for a controller
Or click From the Device menu, select Build. The Build options dialog box displays.
Build application control

code writes the .pcd file.
Enter a file name in the
text box or click Browse...
to select a .pcd file already
created.
Build application diagnostic

symbol table writes the .sym
file. Enter a file name in the
text box or click Browse... to
select a sym already created.
Select this option to put the

symbols into a database.
Note When errors occur during a build, the error messages display in the Log View.
606 of 1016
Software Setup
The following sections describe how to set up the software portion of the controller
for the first time.
Downloading is when a component of a configuration is sent to the component's
controller.
Flash is a non-volatile memory technology that contains the real-time operating
system, the file system, and the TCP/IP software. These are installed with the Serial
Loader, so the remaining runtime and configuration can be downloaded more
efficiently over Ethernet.
The controller is shipped with Basic I/O system (BIOS) performs the boot-up, including hardware self-tests, and
the BIOS, the real-time the Serial Loader.
operating system, and the
Product code (runtime) software converts Application code (Pcode) configurations
runtime software installed.
to executable code (software) and schedules them.
However, to insure that the
latest software is loaded, Application code (Pcode) (.pcd) file, created by the toolbox, contains the controller
perform the controller setup, configuration.
described in the next section.
Symbols table file (.sym), created by the toolbox, contains signal names and
descriptions for diagnostic messages. The information is read into RAM as needed,
making updating the file in permanent storage sufficient.
Ethernet or UDH Cable
Toolbox &
Serial Loader
Software
COM1 Mark VI Controller
RS-232C Serial Loader Cable
Controller Setup
The following steps define how to set up the controller for the first time. It is
assumed that the toolbox and controller are already installed in the pc.
Note CompactFlash™ setup is available only for those systems having a platform of
UCVE or greater.
To set up the controller

1. Load the flash and configure TCP/IP with the Serial Loader over a serial cable
(see the section, Loading the Flash File System).
A soft reboot from the toolbox 2. Cycle power on the controller to activate the new IP settings.
is not sufficient. 3. From the toolbox, load the product code (runtime).
4. Load the application code (Pcode) and symbol files to permanent storage only.
5. Cycle power on the controller again.
Note The remaining sections define each of these steps.
607 of 1016
Serial Loader
The RS-232C cable can be The Serial Loader initializes the controller flash file system and sets its TCP/IP
ordered through your local address to allow it to communicate with the toolbox over Ethernet. It requires an
GE authorized distributor, as RS-232C serial cable. The cable specifications are as follows:
part number 336A3582P1
Controller PC
Pin Pin
Adapter Cable DCD 1 1 DCD
to Controller DSR 6 6 DSR
RD 2 2 RD
COM1 Port
RTS 7 7 RTS
TD 3 3 TD
CTS 8 8 CTS
DTR 4 4 DTR
RI 9 9 RI
GND 5 5 GND
9-Pin Plug 9-Pin 9-Pin 9-Pin Plug

Subminiature D Subminiature D
Receptacle Receptacle
A short adapter cable is required to plug into the controller COM1 Micro-D size
connector. This cable can be ordered as part number 336A4929G1. The Serial
Loader can load the Flash File System and configure the TCP/IP software in the
controller.
To connect the Loader serial cable
1. Connect the end of the cable to COM1 (9-pin connector) on the controller.
2. Connect the end of the serial cable labeled UC2000 connector to the converter
cable.
3. Connect the end of the serial cable labeled pc COM Port to one of the pc COM
ports.
608 of 1016
Initialize Flash
The Flash File System is loaded during system installation, using the Serial Loader .
To start the Serial Loader
1. From the Start menu, select Programs, GE Control Systems Solutions,
Mark VI Controller, and Serial Loader. The Serial Loader dialog box
displays.
2. Enter the correct setting as defined in the following Serial Loader dialog box.
3. Click Start Command(s).
TCP/IP Settings include Computer Name, IP Address, Subnet Mask, and
Router IP. (Obtain this information from your network administrator.) Click
this button to display the dialog box to enter this network data (see the
section, Configuring TCP/IP ).
Select Mark VI from the

drop-down list .
Click to define the PC COM

port. Make sure this port
matches the hardware
cable port (usually COM2
or COM3).
Click Load Flash File

System .
Click Display Summary

Information to display
information in this status
window.
Click
to start the selected
commands.
When the load completes, the following message box displays.
Note The button, Source Directory, points to the location of the BIOS, CMOS, and
flash binary files. It is enabled when CPU Type is either Custom or Mark V LM. The
controller directory is automatically set to platform (C:\Program Files\GE Control
System Solution\MarkVI_Controller\platform)
609 of 1016
Compact Flash Setup
To write the Compact Flash
From the Device menu, select Download, Compact Flash.
Select the
processor.
Note If the Compact Flash hardware is not found, the following error message
displays. Check the hardware installation and the Compact Flash disk placement.
Select Refresh
to update the
Flash Device
information.
The IP Name, IP
Address, Subnet
Mask and
Default Gateway
are read from
System Information
information and
cannot be
modified from
this dialog box.
Select Write to
write the compact
flash to the device.
Select Cancel to
exit without altering
the compact flash.
610 of 1016
Configure TCP/IP
Obtain the Computer Name, IP Address, Subnet Mask, Broadcast Mask, and Router
Click in the IP from your network administrator. Enter this data into the proper fields below:
Serial Loader dialog box.
Enter the Internet Protocol (IP) host
name. For Ethernet networks with a
global name server, the host name
can be used interchangeably with
the IP Address when
communicating to a controller.
IP Address is used to identify a

node on a network and specify
routing information on an Internet.
Enter the 32-bit value used by the

IP software to extract the network
ID and host ID from the IP
address. To be valid, the mask
must contain a "1" for all of the
network bits of the IP address
class (shown above).
This field is calculated

automatically.
Enter the 32-bit value used Click to load or save
by the IP software to route these settings (.ssf file)
external network messages. to the local PC.
Tip All IP addresses and masks are represented in dotted decimal notation,
within each of the four bytes of the address, separated with periods, such as
3.29.22.27. To determine the correct IP addresses and masks, see your network
administrator.
To change only the TCP/IP from its initial setting

1. Modify the TCP/IP Settings dialog box.
2. In the Serial Loader dialog box, check Configure TCP/IP and
Display summary Information.
3. Click Start Command(s).
4. After the command completes, reboot the controller for the change to take
effect.
611 of 1016
Product Code (Runtime) Software
Product code is loaded over Ethernet by the toolbox.
To load the product code (runtime)
1. From the toolbox, create a new Mark VI controller, or load an existing file.
2. From the Device menu, select Download, then select Product Code
(Runtime). The Download File dialog box displays.
Note Some controller versions may display two files, Runtime.dnl and Select.dnl.
Select .dnl should always be selected unless instructed otherwise by personnel.
3. Select Select.dnl and click Open. All possible files that can be downloaded
display in the following dialog box.
Click to uncheck
any file not used
by the controller
(to conserve
memory). The
toolbox deletes
the entire
directory , then
downloads only
the checked files.
If you are not sure

which files to
select, click Scan
hardware for
suggestions. All
files associated
with I/O in the
configuration will
be checked.
612 of 1016
Application Code
After validating and building application code, download it.
To download application code
Or click 1. From the Device menu, select Download, then select Application Code....
The Download Application Code dialog box displays. The default screen
displays with all options checked.
2. Reboot the controller using the power switch.
613 of 1016
Software Modifications
The following sections describe how to modify the application code in the controller
and how to upgrade the product code software to a newer version.
Modify Application Code

The controller executes the application code from RAM. Each time the controller is
rebooted, the application code is copied from permanent storage in the flash into the
RAM. This allows you to try out new application code by downloading it into RAM
and then to restore the original configuration by rebooting. Or alternately, the new
code may be made the default by writing it to permanent storage.
Some application code changes, including editing, inserting, or deleting blockware
may be downloaded to RAM without stopping the control process. This is known as
an online download.
Some application code changes, including modifications to I/O, scales, or variable
addresses may only be downloaded to RAM by stopping and restarting the control
process. This is known as an offline download.
Still other application code changes, including modifications to system memory sizes
cannot be downloaded to RAM but must be downloaded to permanent storage only
and the controller rebooted. Any change that may be implemented with an online or
an offline download may also be performed this way. Refer to the section,
Major/Minor Differences.
Pcode is written when the To change the application code in the controller
menu command, Build
1. From the toolbox, modify the application code.
application control code, is
selected. This file contains all
the application software for 2. Select Validate and Build.
the controller. 3. From the Device menu, select Download, then select Download
Application Code.
4. Select the desired download option from the Download application code
dialog box.
614 of 1016
Check Download to memory to replace the current running configuration with the
new application code. Then, select from Memory Download Mode
Online - Init all constants to replace the running configuration without stopping
Downloads to
for a fast download. Since all constants are initialized the process increases.
RAM
Online - Init only new constants to replace the running configuration without
stopping for a fast bumpless download.
Check to download the new

application code (.pcd file) to
flash memory to be used when
the controller is rebooted. This
does not change the current
running configuration.
Downloads to Enter the correct .pcd file name
Flash Browse...
Check to download the .sym

file to permanent storage. This
changes the active symbol
table in the controller.
Enter the correct .sym file
name or click Browse...
Check to download the
compressed Mark VI file to
permanent storage. This file
serves as disaster recovery if
the PC-based file gets
corrupted.
Note When all options are selected, the symbol table is downloaded first. Then the
application code is downloaded to memory. If the download to memory succeeds,
the code is downloaded to permanent storage. If it fails, the download to permanent
storage is cancelled.
615 of 1016
Major/Minor Differences
The toolbox detects differences between the application code loaded into it and that
loaded into the controller by comparing the revision dates. The revision in the
toolbox and the controller is stored as two date and time values. These values are
cleared in the toolbox when a major or minor change occurs and set when the
configuration is built (Pcode). When the toolbox is online with a controller, the
major/minor revision of the downloaded configuration in the controller is compared
with the current configuration in the toolbox.
Major and Minor

revision
differences are
indicated in the
Summary View.
The connection/revision status is displayed here.
The controller application files consists of Pcode files and diagnostic symbol table
files. Pcode can be downloaded to either the active RAM to replace the running
configuration, or to permanent storage. Permanent storage is flash memory for the
controller for use the next time the controller boots.
Pcode can be downloaded to the controller RAM in either an online mode, where the
configuration is switched over quickly, or offline where the controller is completely
stopped and then restarted. It is usually beneficial to use the online download, but the
amount of configuration change could make this impossible.
A major difference means that the major revision in the toolbox is different from the
major revision in the controller. A minor difference means that the minor revisions
differ, but the major revisions are the same. Equal means that both major and minor
revisions are the same. These differences display in the Status Bar.
616 of 1016
A bumpless download does It is not always possible to download online when a change is made to the
not disrupt the control as a configuration that prevents the download from being bumpless, such as numerous
result of the download. changes to signals in regard to their address tokens, or changes to scales or I/O. In
the toolbox, a major change is one that does not allow an online download. These
include changes caused by additions of hardware modules, or packing signals.
Packing involves reclaiming unused tokens (this does not include connecting signals
to points). Minor changes are any other changes to the configuration including
editing, inserting, or deleting blockware.
The status of changes to the configuration can be seen from the Summary View, as
shown below. The first example shows a configuration just built, the second has
minor changes, and the third major changes.
617 of 1016
Upload Mark VI File
The following steps allow you to retrieve a permanently stored Mark VI file (.m6b).
To upload a Mark VI file
From the Device menu, select Upload.
When the file is uploaded, a new window is created with the name <device
name>_dl.m6b.
Enter the IP Address or

the Host Name of the
target controller.
Select the type of
controller. The default is
the currently open device
type, if present.
Upgrade Product Code (Runtime) Software

The following steps define how to install a new version of the product code software
in a previously configured controller. It is assumed that the toolbox and a previous
version of the product code are already installed in the pc, and that an application
code file (.m6b or .ucb) exists.
To upgrade the product code
1. From the toolbox, select the File menu, then Open. Select the existing
application code file (.m6b).
2. From the File menu, select Export, then select All. From the Export All
options dialog box, select an option to export the application code into its tree
files (.tre) and a project file (.prj).
3. Install the new controller product code from the product CD.
618 of 1016
4. From the Device menu, select Download, then select Product code
(Runtime).
5. Select Select.dnl and click Open. All possible files that can be downloaded
display in the following dialog box.
619 of 1016
6. Click to uncheck any file not used by the controller (in order to conserve
flash space). The toolbox deletes the entire directory and then downloads only
the checked items. If you are not sure which files to check, select Scan
hardware for suggestions. Files that are associated with I/O in the
configuration will be checked.
7. When you are finished with your selections, click OK. The following message
displays.
8. Click No. Do not reboot.

9. From the File menu, select Close.
10. From the File menu, select Open and open the project file. This imports the
component files (.tre) back into the toolbox by opening the project file (.prj).
Note This will create a new Work Area to merge the application code (.tre files)
with the new product code.
11. Click Validate and Build to create a new Pcode file (.pcd) from the
application code.
12. From the File menu, select Save.
13. From the Device menu, select Download, and then select Application
Code.... The Download Application Code dialog box displays.
14. Check Download to permanent storage and Download symbols.
620 of 1016
15. Click OK.
16. Wait until the red FLSH LED on the controller has turned off.
17. Reboot the controller using the power switch.
Use Totalizers
Totalizers are timers and counters that store data such as number of trips, number of
starts, number of fired hours and such. They are currently used in Mark VI or
EX2100 application code. The outputs of the timers and counters are then stored in
NOVRAM.
Note A special password is required to modify Totalizer values. To obtain a

password from the GE OnSite Center, click the Save button on the dialog box below
for instructions. No password is required to view the current value of the Totalizers.
To view or modify the totalizers value

From the Device menu, select Download, and View/Set Totalizers. The
Totalizers dialog box displays.
Enter the
password in
Password
field.
Click Modify to
change the value
of the highlighted
item.
621 of 1016
To request a totalizer password
1. From the Device menu, select Download, View/Set Totalizers. The
Totalizers dialog box displays an Identifier.
2. Click Save to save the identifier to the hard drive. The Totalizer_ID text
displays the procedure to follow to receive a Totalizer password. The password
sent is valid for 24 hours only.
Restore Application Code

The application code running in the controller's memory may be different from that
in permanent storage. If the code in memory becomes unstable, this command loads
into the controller's memory the uncorrupted code in permanent storage. All changes
to the code in memory will be lost.
Note Restoring from permanent storage cannot revert application code if the major
revisions between permanent storage and memory are not equal.
To restore application code from permanent storage

From the Device menu, select Download, then Restore from Perm
Storage.
622 of 1016
Monitor
Once a controller is configured and downloaded, the live signal values can be
viewed. This section defines how to go online to monitor these values and certain
Summary Views when the controller is being monitored. These views are displayed
when the Tracking button is on and an item is selected in the Outline View.
Going Online/Offline
To see the live data from the Summary Views, it is necessary to be online
(communicating to a running controller).
To go online
Or click . From the Device menu, select Online. Online blockware information can be
monitored from the status bar and the Summary View.
Status Bar
When online is started, it is indicated on the status bar in the lower-right corner of
the Device Window, shown below. The difference status and idle time of the
controller replaces the word Offline when the controller and toolbox are
communicating. The status bar also displays the enable value and heartbeat of any
tasks or blocks of tasks in the block flow diagram (Summary View), when the
diagram is active.
623 of 1016
Module View
For information on how to The Summary View for a module item displays the task list with the module
configure and view a module’s scheduling information. When monitoring live data, the task list also shows the
graphics window, refer to the enable value and heartbeat, as shown below. When the toolbox is offline, the
section, Graphics Window. heartbeat and enable value are replaced with a hyphen. The Detached Summary
View for a module item with graphic window file is called a Graphics Window.
Task, Macro, and Block View

For more information, refer The Summary View (right side) for tasks, macro definitions, macros, blocks, and the
to the section, Block Flow block items of a macro instance is called the block flow diagram. When a block or
Diagram. macro instance is highlighted in the Outline View and Tracking is on, the Summary
View displays that single item. When the controller is online, the block flow diagram
displays live data values (in green) next to the block or macro pin.
To modify the live data values
From the Summary View, double-click the values. One of the following dialog
boxes displays.
Boolean Value
Use the dialog box below to modify a Boolean value.
Use this dialog box to

change or force the live value
of a Boolean signal. Forcing
the value keeps the
blockware from writing over
the forced value, whereas an
unforced value can be over-
written in blockware.
624 of 1016
Numerical Value
The numerical value is modified with the dialog box below.
Use this dialog box to enter a
value to be sent to the controller.
These values cannot be forced,
so values that are written in
instruction blocks do not change
to the value being sent.
Current is the live value of the

signal. Enter the Next value and
click Send.
Delta is the value to be added or

subtracted from the current value.
Click here and increment Click here and decrement
Token is the logical address of the Current value by the the Current value by the
the signal. Delta amount and send it Delta amount and send it
to the controller. to the controller.
Array Value
The dialog box below is used to modify the array value.
Click on the
element to
change.
Click Modify.
The Boolean or
Numeric Send
Value dialog
displays with
this element.
625 of 1016
Watch Windows
The Watch Windows function creates a quick reference list containing names,
values, units, and description of the online values of signals. Each controller
document can contain multiple, uniquely named watch windows. These are saved,
then exported to or imported from the controller's project file.
To select a Watch Window
From the toolbar, click View, then select Watch Windows. The Select
Watch Window dialog box displays.
All Watch Window

names are listed here.
To create a Watch Window

1. Click the New button. The New Watch Window dialog box displays.
2. Type a unique name. Click OK to view Watch Windows.
Note It is possible to minimize any watch window by clicking the minimize symbol
in the upper right hand part of the dialog.
626 of 1016
Selects the appropriate
signal in the configuration
file.
Starts the trender and

inserts the signal
If you are online, this will

pop up the change live
value dialog
This will be signal

definition as a comma
delimited line into the
operating system paste
buffer
You can add comments to any
signal in a watch window.
These comments are saved with
the watch window, not the
signal.
To insert a signal
1. From the Outline View, right-click on a signal to display a shortcut menu.
2. Select Insert Signal to open the toolbox Signal Selector dialog box.
3. Select a signal and click OK.
To delete a signal
From the Outline View, right-click on the signal, then select Delete Signal.
Or, select the signal and press the Delete button.
Note Signals can also be dragged-and-dropped into Watch Window from other
Watch Windows or the Outline View. Dragging an I/O point into a Watch Window
will display the point's attached signal, not the point.
Controller Status Commands

The Controller Status Commands are a set of diagnostic functions that the toolbox
can run on the controller. They allow you to view the status of many control system
functions. If you contact GE for technical support for your controller, you may be
asked to run some of these commands. The results of a command displays in a text
window, which can be saved as a file.
627 of 1016
Controller Load Profiler System
To configure Controller Load To configure the Controller Load Profiler
Profiler, you must have
From the Outline View, double-click the controller name.
Standard Block Library
(SBLIB) revision 7 Note You must validate, build, and download for the controller changes to take
(V07.xx.xx) or greater effect.
installed.
Select this box

to enable
Controller Load
Profiler for the
device.
Once the Controller Load Profiler is enabled, select it from the View menu. The
Profiling Controller Load window displays the following information.
The data in this report can be Scheduling Chart Number identifies the three charts in the controller, one for
sorted by clicking on the each base period of module configuration and task schedules. Each scheduling chart
column header and printed to can have multiple modules defined.
a CSV file with the print
Overrun Counter advances if the time to start a task exceeds the time allotted (the
command (CTRL+P).
chart base period).
Chart base period is the maximum period of time allotted for the execution of
application tasks within each time slice in a chart.
Last Run Time is the time needed to run all the tasks in a slice.
Bar Graph is the percentage of the slice used by the tasks. The graph displays in
red when more than 90% of the run time is used.
Last, Minimum, and Maximum Frame Time (in milliseconds) columns
allow the user to reset the minimum and maximum frame times by selecting the first
line in the list and selecting Reset under the Device menu.
628 of 1016
Monitor Controller State
The toolbox status bar displays information about the controller state. The status bar
feature called Control State allows the status to be viewed from a remote site.
This displays the current

device state as Unknown.
The four states (in increasing priority) that can be viewed are:
• Control - controller is running (green background)
• Boot - controller is starting up (yellow background)
• UNKN - controller state is unknown; more investigation is required (yellow
background)
• Fail - controller has failed (red background)
For Simplex systems, the state displays for that one controller. For TMR systems, the
highest priority state of the set of controllers displays. For example, if both the <R>
and <S> controllers are in the Control state and <T> is in the Fail state, Fail
displays. For more detailed controller state information, display the Controller
State dialog box.
To display the Controller State dialog box
From the status bar, double-click the controller state. Or, from the View Menu,
select Controller State.
The value of the IO The value of the Control
State of the controller. State of the controller.
An asterisk (*)
determines the
designated
controller.
The current
controller
state
Explanation
of current
controller
state
629 of 1016
Control Constant and Tuning Variable View
A flag indicates the existence Control Constant is a signal with an initial value that is read and never written.
or status of a particular Control constants are specific constants that a user might want to consider separate
condition. from other constants because of their importance to key control algorithms. Users
can flag signal and module definition pins that have this property. Once flagged,
constants can be viewed and compared as a group, exported to .csv files for
manipulation outside of the toolbox, and merged back into the configuration.
Tuning Variable is a signal with upper and lower limits, which define the bounds
of the initial value and when making runtime changes. Tuning variables are specific
signals that are considered separate from other signals and constants because of their
importance to key control algorithms. Only users at privilege level 4 can flag signals
and module definition pins to have this property, and to set the upper and lower
limits. A user at privilege level 2 and above can change the initial value or runtime
value of a tuning variable, but not outside the range defined by the upper and lower
limits. Once flagged, tuning variables can be viewed and compared as a group,
exported to .csv files for manipulation outside of the toolbox, and merged back into
the configuration.
Work Area
To use the Control Constant View
1. Create or open a binary working file (.m6b).
2. From the View menu, select Control Constants. A separate window
displays, called the Control Constant View.
To use the Tuning Variable View
1. Create or open a binary working file (.m6b).
2. From the View menu, select Reports and then Tuning Variables. A separate
window displays, called the Tuning Variable View.
The following sections describe the menu commands and work area specific to
Control Constant and Tuning Variable View.
File Menu
The File menu is illustrated below.
Close exits the Control Constant View.

Save/Save As preserves on open file. Save As prompts you for a new file name.
Merge in .CSV reads the saved and modified .csv file and overwrites the initial
value of the signals in the configuration with the new value specified.
630 of 1016
Export to .CSV writes the signal information to a .csv file. The form of the file
name is DEVICEControlConst.csv, where DEVICE is the actual controller name.
The signal information includes the name, value, scale, type, and a note.
Print provides a paper copy of the Control Constant View.
Print Preview displays the page as it would be printed.
Print Setup allows you to select a printer and print connection.
Edit Menu
The Edit menu is illustrated below.
Modify allows you to edit the selected signal.

Find allows you to search the Control Constant View for text in the signal names.
Device Menu
The Device menu is illustrated below.
Online toggles the controller online/offline to view live data values and enables the
Save Values command.
Save Values obtains the displayed live values and puts them in the controller
configuration. Make these changes permanent by going to the controller window and
saving the binary file.
Modes of Operation
The Control Constant and Tuning Variable Views have two modes of operation,
online and offline. The Control Constant offline view displays the Signal Name,
Initial Value, Type, Scale, and Note for all signals that are control constants.
The Tuning Variable offline view displays the Signal Name, Initial Value, Type,
Scale, Upper and Lower limit, Note, and Path for all signals that are Tuning
Variables.
631 of 1016
To edit a view
Double-click a signal name. The Edit Module Pin or Signal Edit dialog box
displays.
In the online mode, the live Value displays (second column). Signal Names that have
differences between the live Value and Initial Value are marked with a red
not-equals symbol (≠).
To modify the live value
Double-click a signal name. The Send value dialog box displays.
Send Value
Use the dialog box below to modify the send value.
Use this dialog box to enter a

value to be sent to the controller.
These values cannot be forced, so
values that are written in
instruction blocks do not change to
the value being sent.
Current is the live value of the

signal. Enter the Next value and
click Send (or click Send & Close
to exit the dialog box).
Delta is the value to be added or

subtracted from the current value. Click to either Increment or Click here to send the value entered
Decrement the Current in the Next box to the controller. This
Token is the logical address of the value by the Delta amount is the default setting, so typing a
signal. and send it to the controller. value and pressing Enter also sends
the value and closes the dialog box.
632 of 1016
The following dialog displays for Tuning Variable View.
Tune High Limit – The Next value cannot be greater then the high limit.
Tune Low Limit – The Next value cannot be less then the low limit.
If the signal is not a tuning variable, then the high and low limits fields do not show
up in this dialog.
Note In both views, the live values can be saved to the configuration online from
the Device menu.
633 of 1016
File Compare View
The File menu contains a Compare command, which compares one configuration
file with another.
Compare All compares an entire file configuration with another selected .m6b file.
Compare Selected compares a selected item of two .m6b files.
Compare Block Configuration compares the application code of each file. It
performs a back-chain from each output signal that compares the inputs, the block
types, and connections that create the signal. Block numbers and code locations in
the Outline View are ignored.
Compare Signals compares each output signal defined in the application code.
Each signal is tested for initial value, data type, and such.
634 of 1016
To compare files
1. From the File menu, select Compare, then the desired comparison type. If
more than one .m6b file is open, the Compare dialog box displays.
Select to
compare with
an open file.
Select which
open file to
compare.
Select whether
to compare a
currently open
file or open a
new one, then
click OK. The
Translate
Regions dialog
box displays.
This column displays regions of This column contains the

the Reference file for comparison. same columns for the test file.
Select the regions

to compare.
Click here to change

the name of the
regions to compare.
2. Configure any region relationships, as necessary, and click OK.
635 of 1016
The items compare and display as follows:
Select a location to search for items Detailed description of
that are different in the .m6b files. the difference error.
The two
files being
compared.
The items that are different.
Note The menu commands for this screen are the same as basic toolbox menu
commands. Refer to the section, Menu Commands.
636 of 1016
Application Documentation
All reports and diagrams Application documentation consists of printable tables, reports, and block diagrams
contain extensive cross- that help you understand and maintain the system. Most Outline View items can be
referencing. printed individually or as part of a larger document that thoroughly describes the
controller configuration. Block diagrams provide information about controller
blockware and reports contain information about signals and Pcode.
The full application document contains numerous optional sections:
• Device Summary lists the main settings for the Mark VI controller, including IP
addresses, platform types, and customer information.
• Document Reading Aid explains the conventions and symbols used in the
document.
• Revision Log is a list of changes made to the controller configuration that
includes the modification date and user name.
• Table of Contents provides page numbers for each section heading.
• Functions includes the block diagrams of all controller functions.
• Macro Definitions includes the block diagrams for all non-protected controller
macros.
• Reports include summaries of alarms, I/O, and such.
• Signal Cross Reference provides a list of all named signals in the configuration
with type, units, description, and references to signal locations.
Print Options
The item selected in the Outline View determines what gets printed. If you wish to
print the entire controller configuration, select the controller name. If you wish to
print only a single module, function, or task, select that item.
To print application documentation
1. From the Outline View, click the desired item to highlight it.
2. From the File menu, select Print Preview to view the document online or
Print to create a hard copy. The Print Options dialog box displays.
The Print Options dialog box contains four tabs: Options, Margins, Fonts, and
Profiles.
637 of 1016
Options Tab
The Options tab lets you select the report type.
Select the reports

to be printed.
The Page Numbering options control page number assignment.

• Linear page numbers go sequentially from one. The page number on the
printout corresponds to the actual printed page.
• Hierarchical by Module, Task page numbers are divided into three parts:
section, sub-section, and page. The section number starts with one and
increments for every function and module. The sub-section number is
incremented for every task within a section. The page number starts with one for
the first page of a task and counts linearly.
• Hierarchical by Function, Module, Task is similar to Hierarchical by Module,
Task except that there are four parts to a page number.
• Hierarchical with section names uses text strings for sections instead of
numbers.
Note Cross-references to hierarchical page numbers are often abbreviated within a

section. For example, a reference from the first page to the second page of a task
would only show the page number, not the section and sub-section.
638 of 1016
The block diagrams options control printing of block diagrams.
• Text Size controls the font size, which determines the diagram scaling.
• Show Block Drawings determines whether to include the internal drawings for
complex library blocks. Although these drawings help with understanding the
code, they occupy much space.
• Wires can cross page edge selects wire-routing behavior in multi-page
diagrams. This option enables or disables the printing of wires that cross page
boundaries in multi-page diagrams.
• Show live data values enable a signal's live value to be printed if you are online
in the toolbox.
Note Because large blocks cannot always fit on a single page if you select a text size
too large for your paper, always preview before printing.
Margins Tab
The Margins tab lets you select either single- or double-sided printing and margin
settings.
Select the check box

for either single-sided
or double-sided
printing.
Note When printing double-sided, the back-page margins are mirror image of the
front-page margins.
639 of 1016
Font Tab
The font tab provides font sizing options.
Select the
desired font.
Note Selecting fonts that are too large can result in text printing outside the margins.
640 of 1016
Profiles Tab
The Profiles tab allows you to save your print settings for future use.
If you selected Print Preview from the File menu, the layout calculates and
displays, using the current printer setup. If you selected Print, the standard Print
Note In very large controllers, the print layout calculations can take several minutes.
641 of 1016
Print Preview
To preview application documentation
1. From the File menu, select Print Preview to see how the application
documentation will look when printed and to proof for mistakes.
2. Click the Print Preview button to close the print preview. Click Print to open
the Print dialog box.
642 of 1016
Block Diagram
For more information, refer The block diagram can be captured and viewed (Summary View or the Detached
to the section, Block Flow Summary View) or printed to a hard copy (paper) form. The diagram displays the
Diagram. item (task, macro, or macro definition) currently highlighted in the Outline View.
To view a block flow diagram
1. From the Outline View, click the desired item (in the hierarchy list) to
highlight it.
Or click to view the 2. View the diagram from the Summary View or select Detached Summary
Detached Summary View. View from the Edit menu.
Or, from the File menu, select Print Preview to view the diagram online or select
Or click to print a hard Print to create a hard copy.
copy.
Page breaks divide the report The Block Flow diagram uses the Comment block to force page breaks. The diagram
information into orderly pages are numbered in a row/column format. (This format makes it easy to assemble
pages. the report on a wallboard.) The size and characteristic of the blocks can be edited in
the Block Diagram tab.
To edit the Block Diagram
1. From the Options menu, select Settings. The Settings dialog box displays.
2. Click the tab Block Diagram (defined in the following section).
643 of 1016
Block Diagram Tab
The Block Diagram tab is illustrated below.
Display the blocks in a list with no

connections or connected to each
other or the Summary View and
Detached Summary View .
Check to show all List block

diagram pins. This command
disregards the text box Visibility,
if it is checked in the Edit Macro
Pin Definition dialog box. Font
size changes the font size of all
text on the block diagram.
Check the following options for

interconnected block diagrams:
Show all pins displays all
block pins. This command
disregards the text box
Visibility, if checked in the
Edit Macro Pin Definition
dialog box.
Reorder pins rearranges the
pins to minimize crossing the
connections on the diagram.
Show input or Show output
connections displays the
connection names and values.
Font size changes the font Change the Summary View tracking feature to display various levels
size of all text on the block of the hierarchy, when they are selected in the Outline View. Select
diagram. the item to display on the lowest level. The default is Task/Macro.
644 of 1016
Reports
Reports provide controller information in a printed form. Reports display in a
separate window and can be viewed, saved, and printed. The following report types
can be generated for the controller:
• Alarm List
• Hold List
• Event List
• Scale List
• Signal List
• Signal Cross-Reference
• Multiple Written Signal List
• EGD Network
• Simulation Data
• Control Options
• I/O Report
• I/O Module Report
• I/O Point List
• Unused I/O Report
• Revision log Report
• Enumerated Data Types
• Control Spec Reports
− IO Config
− Signal Config
• Block Pin Report
• Tuning Variables
• 2nd Language Report
• Orphan Signal Report
To generate a report
From the View menu, select Reports. Select the desired report. The report
displays as a separate window.
When viewing a report, a text find feature is available to search for specific text in
the report. From the View menu, select Find. The Report Find dialog box displays
to enter text and search the report (defined in the following section).
Report Find
The Report Find dialog box is illustrated below.
645 of 1016
Enter the text you want to find
from the report. The found text
is highlighted in the report..
Enter new text or click Cancel.
Only Boolean signals can be

selected for the Alarm List, Alarm, Hold, Event Lists
Hold list, and Event List The Alarm List report creates a spreadsheet displaying all the signals marked as
reports. These reports can be alarms. This report lists the signal name, description, and the alarm (drop) id for
used to create the alarm.dat, each signal. Signals are marked as alarms on the Edit Signal Definition or Edit
bold.dat, and event.dat files Module Pin dialog box.
used by the HMI to display
the alarm lists. The Hold List report produces a spreadsheet displaying all the signals marked as
Automatic Turbine Startup (ATS) hold signals. Signals are marked as Holds on the
Edit Signal Definition or Edit Module Pin dialog box. This report, which lists
the signal name, description, and the hold id for each signal, looks exactly like the
Alarm List report.
The Event List reports all the signals marked as Event signals. Signals are marked
as events on the Edit Signal Definition or Edit Module Pin dialog box. This
report, which lists the signal name, description, and the Event id for each signal,
looks exactly like the Alarm List report.
Scale List
The Scale List report provides a list of all scales that are used in the controller
configuration. The list includes both locally defined scales and global scales (Scales
under ‘System Data, External Scale Definitions’ which are brought into the
configuration when a ‘Get from database’ is performed).
Signal List
The Signal List report provides a list of all the signals in the controller. For every
signal, the report lists the signal name, the data type, and the token number. Signals
listed in the controller configuration, but not used by any blocks have a blank token.
Signal Cross-Reference
The Signal Cross-Reference report provides a list of all locations in the blockware
where named signals are used. Named signals are signals defined by you, usually
either in a signal definition or as module pins. Automatic signals are generated by the
toolbox. They connect block pins, when neither pin is connected to a named signal.
The first part of the signal cross-reference is an index of the items in the controller.
In the cross-reference, an item is considered down to the level of an item that
contains blocks, which could be a task, a macro, or a macro definition. The code
corresponding to one of these items shows the level of the item.
An example of the index is as follows:
Index of sections for controller uc2k-9
01 Functions
02 tmr_test
646 of 1016
02:01 ........\MacroDefs
02:01:01 ........\.........\my_macro
02:02 ........\Pump
02:02:01 ........\....\PumpTask
02:03 ........\Entry\Pump1@Pump
02:03:01 ........\................\PTask
The second part of the signal cross-reference is the actual cross-reference list. Each
location, where the signal is referenced, is listed for every signal. Each reference
consists of a section code for the task macro or macrodef, the block number, and a
flag (*) to show whether the signal is being written on the block. Examples from a
cross-reference report are as follows:
Entry\Pump1\PumpEngine------------:
Signal Entry\Pump1\PumpEngine is not used anywhere in the blockware.

Entry\Pump1\sinout----------------: 02:03:01:0020*
Signal Entry\Pump1\sinout is written to on block 20 of task Ptask, in module

Entry\Pump1@Pump, in function tmr_test.
Entry\Pump1\Start-----------:02:03:01:0030 02:03:01:0030*
The signal Entry\Pump1\Start displays on two pins (one read, one write) on block
30 of the same task.
Multiple Written Signal List

This report provides a list of all signals that are written to by more then one block or
pin. Each row for a signal includes the path to indicate where the point is written to.
There are many times where it is advantageous to write to a signal from multiple
locations, but if it is done accidentally, the consequences can be such that the code
will not operate as intended. This report will show those errors.
EGD Network
The EGD Network report provides a list of all signals and IO that is connected to
the EGD network. It includes which EGD exchange it is connected to, the direction
of the point, data type, update rate, and other selectable data.
647 of 1016
I/O Report
Once the I/O report option is selected, the IO Report Select Columns dialog box
displays.
Select the columns desired for the report. Once the report is generated, click the
column header to sort the data by column.
The following table describes the columns.
648 of 1016
Columns in the I/O Report
Column Name Description

Entry Counts the number of items in the report. Sort by this column to place the data in its
original order.
Device ID of device attached to the screw
Cable Number ID of the cable attached to the screw
Wire Number ID of the wire attached to the screw
Interposing TB ID of the terminal board junction, if any, between the Mark VI and the actual I/O
Sense Used for relay and solenoid circuits only. Sense of relay connected
TB Screw Number of the screw on the terminal board
TB Name Name of the terminal board
TB Location Panel location of the terminal board
Screw Name Name of the screw on the terminal board
Point Name Name of the point that the screw services
Card Jumpers List of jumpers on the VME card and the position to which they should be set
VME Card Name of the VME card
VME Jack Name of the jack on the VME card to which this terminal board connects. Formatted to
match cable labels. Rack number followed by channel designator (Q means R, S, and
T) followed by jack designator as shown on the screen print. Rack designators are
postfixed by the slot number on the screen print.
Signal name Name of the signal attached to the point
Used Whether the point is used by the CSP
Description Note attached to the point. If the point has no note, the note from the signal is attached
Engr Low The Low_Value configuration item of the point, when presen
Engr High The High_Value configuration item of the point, when present
Engr Units Units associated with the scale associated with the signal
Raw Low The Low_Input configuration item of the point, when present
Raw High The High_Input configuration item of the point, when present
Raw Units The units associated with the InputType configuration item of the point, when present
Mask The units associated with the SignalInvert configuration item of the point, when present
649 of 1016
Importing an I/O Report from a .csv file
Save the .M6B file before importing.
The Mark VI supports automated import of some or all of an I/O report. This is used
whenever there are multiple sources of the report data.
Do not import columns you To Import an I/O Report
do not want to change.
Highlight the Mark VI I/O in the Outline View.
1. Under the File menu, select Import.
2. Select CSV as the type of the import file.
3. Select the file to be imported.
4. Select the columns to be displayed in the report.
Note If toolbox cannot import the data, it will alert you to the discrepancy. The
number at the beginning of the error message corresponds to the line number in the
.csv file.
I/O Point list

The I/O point list report provides a list of all IO points. The points are referenced
from the device, rack, slot, board type, point name, and terminal board position.
Unused I/O
This provides a filtered version of the I/O report, specific to the points that do not
have any signal attached to them. If the I/O point has a signal name it will determine
if that point’s signal is being used in the application code.
Revision Log Report

This report displays the revision log of the selected document. Columns include:
• Date/time stamp
• Username
• Computer name
• Description
650 of 1016
Enumerated Data Types Report
To create an Enumerated Data Types Report
From the View menu, select Reports, then Enumerated Data Types. The
Enumerated Data Types Options dialog box displays.
Select to include
all enumerated
data types in the
document.
Select to include
only data types
defined in Module
and Macro
Libraries.
Select to include
the signal name
currently
assigned to the
data type.
Control Spec Reports/IO Config

The I/O Config report provides a list of all IO points and their configuration. The
columns to include are configurable. There is a row for each configuration item for
an IO point. The configuration name and value are included.
Control Spec Reports/Signal Config

The Signal Config report provides a list of all Signals and their configuration. The
columns to include are configurable. If a signal is an array, there is a row for each
element. Some of the configuration items included are Scale, units, control constant,
used by code, used by IO, ED, alarm, event, hold, Display and setpoint limits, dead
band, alarm class, and Cimplicity Screen.
Block Pin Report

The Block Pin report provides a list of all block pins, by
Function/Module/Task/Block/Pin name, and includes its connection if any. Block
number and block comments are also included.
Tuning Variable Report

The Tuning Variable report provides a list of all signals and pins that are defined to
be Tuning Constants. See the section on “Control Constants and Tuning Variable
view” for more details.
2nd Language Report

The 2nd Language report provides a list of all signals along with both language
descriptions. The report includes fields that can be used for sorting and filtering.
These fields include: alarm (yes or no), event (yes or no), SOE (yes or no),
hold (yes or no), network (yes or no), and the path. This report can be exported
to a CSV file. The CSV file can then be edited to supply translated descriptions for
signals that require a translation. The CSV file can then be imported back into the
MarkVI configuration, along with the 2nd language descriptions. The import is
performed from the menu item, File/Import/2nd Language.
651 of 1016
Orphan Signal Report
The Orphan Signal report provides a list of all signals and pins not driven by
software, I/O, or from a network. Control constants and tuning variables are not
included in this list.
652 of 1016
Application Diagnostics
This section describes the application diagnostics feature of the controller.
Application diagnostics inform the operator and/or maintenance engineer why an
action cannot be started, or why it stopped. Application diagnostics are generated
from the same code running the process, so that you no longer need to maintain
separate code. Diagnostics can be viewed through HMI programs (Diagnose and
DLAN View).
Types of Application Diagnostics

There are four types of application diagnostics:
The four-character • Triggered (TRGD)
abbreviation for the diagnostic
type can be used to filter the • Broken run (RUND)
diagnostics that display on the • Feedback (FDBK)
problem history screen.
• Sequence (SEQD)
Triggered (TRGD)
There are three types of triggered diagnostics:
• Start diagnostics are generated when an operator or piece of logic tries to
initiate an action not permitted. The start diagnostic indicates why the action
cannot be started. It lists either the permissives not satisfied and/or what is
calling for the action to be stopped.
• Off diagnostics, which are the reverse of the start diagnostics, are generated if
something is requested to be turned off and off permissives are not met.
Normally with off permissives, the equipment is not being turned off, but is
being toggled to a second state (for example, a dual position solenoid.) The off
permissives are specified when there are permissives for going into the second
state.
• Requested diagnostics are normally used when a process is going to be started
up after a downturn. When diagnostics are requested, no action is initiated.
Therefore, the operator can actually request the status to correct problems before
it is time to start the process. Diagnostics requested over the diagnostic network
only display the logic with permissives not met (the operator does not have to
filter through I’m OK messages).
Control code can be configured to generate diagnostics when operator or
maintenance personnel request them.
Note When diagnostics are requested specifically from an HMI screen over
Ethernet, a response is always sent back exclusively to the requesting screen. This
assures the operator that all permissives are satisfied.
653 of 1016
Broken Run (RUND)
A run permissive is a permissive Broken run diagnostics are generated when an action stops because it loses a run
required for a piece of permissive. The diagnostic tells what permissive(s) changed state, causing the action
equipment to run or for an to stop, and what permissives are required to start the action again.
action to continue.
Frequently, equipment or actions have two different sets of permissives:
Start permissives only need to be met when an action is initiated.
Run permissives need to be met for the action to be initiated and for the action to
continue.
Feedback (FDBK)
There are two types of feedback diagnostics:
• When an action is both permitted and requested to start, but there is no feedback
after the expected amount of time. For example, a solenoid is energized to move
a piece of equipment. It is expected to pick up a limit switch when the piece of
equipment is in position. If the limit switch does not pick up in the expected
period of time, a feedback diagnostic is generated.
• When this control code successfully turned something on and then later lost its
feedback. For example, a piece of equipment is moved into position so that it
picked up a limit switch. Later at some point, perhaps due to softening in the
hydraulic system, that piece of equipment moves off the limit switch. Since it
was not moved off by an operator or by control code, a feedback diagnostic
would be generated indicating that the equipment was no longer in the proper
position.
Sequence (SEQD)
Sequence diagnostics are generated from the code performing a sequence. There are
two types of sequence diagnostics as follows:
A merge time-out occurs when a sequence has parallel paths that merge back
together. When the sequence is defined, it is expected that the parallel actions will
complete within some pre-defined time from each other. If one of the actions has
completed, and the other action(s) has not, a merge time-out sequence diagnostic is
generated. At this point, the operator should determine if there is a triggered,
feedback, or broken run diagnostic from the piece of code that actually initiated the
control action.
This is a programming A handshaking fault is when one step of the sequence was trying to hand off
diagnostic that an operator in control of the sequence to the next step and a fault is detected. (This is normally
the field should never see. caused by the handshaking signal being written to someplace else in the code when it
should not be.)
654 of 1016
Generating Application Diagnostics
When a diagnostic is generated, it can contain more permissive signals than those
connected to the block that detected the problem. The back-chaining feature traces
back through any other rungs that feed into the signals on the block. In the following
example, the permissive engine at rung number 80 (80:_PENG) controls moving a
drive in the forward direction. The run permissive pin on the block is RPRM. The
output coil of the RLD at rung 60 is wired into the run permissive. Also, one of the
inputs to the RLD in rung 60 is the output coil of the RLD at rung 23. If the drive is
running forward and loses a run permissive, the broken run diagnostic will not only
check all of the contacts in rung 60, but also all the contacts in rung 23. If the signal
Drive\Std1\RDYRUN in rung 23 drops out, causing the drive to stop running
forward, then the broken run diagnostic reports the signal that caused the drive to
stop.
Refer to the next section, Blocks contain several pins that control when diagnostics get generated, and how far
Control Blocks that Generate back the diagnostics program in controller will trace through code to find
Diagnostics. permissives not met. These pins are described below. Next to each pin description is
the actual spelling of that pin name as it appears on the block, such as reqdiag.
Request Pin (reqdiag)

The request diagnostics pin does not initiate any actions, but allows the operator to
check a block to see if permissives have been met. It only generates a diagnostic
message if a permissive is not met. This is a rising edge detect pin (the permissives
are only checked when the signal transitions from a low to a high).
655 of 1016
Disable Pin (ddiag)
The disable diagnostics pin controls whether or not this block generates a diagnostic
message when a problem is detected. The pin can be tied to a signal so that the block
dynamically adjusts when it generates a diagnostic. For example, some mill
equipment is in auto mode. The block that controls the equipment when it is in
manual mode could be configured to not generate diagnostics when the equipment is
in auto mode. To do this, attach the auto_mode signal to the ddiag pin on the manual
control code block.
Disable Back-Chaining Pin (ddiagbc)

The disable diagnostics back-chaining pin controls how far back through the code
permissives not met can be traced. In the following example, rung 220 puts the entry
section in run mode when requested, as long as all permissives are met. If passline 1
equipment is used, passline 1 permissives must be met. If passline 2 equipment is
used, passline 2 permissives must be met. Therefore, if passline 2 is used, the
detailed permissives for passline 1 are not important. On rung 160, E_PL2 is on the
ddiagbc pin. Therefore, when rung 220 generates a diagnostic, if passline 2 is
selected, and passline 1 permissives are not met, the only passline 1 signal the
operator sees is PL1\perms\ok.
For example, the operator would not see the details of unhealthy drives in passline 1
(from rung 140). All the detailed permissives for passline 2 not met are shown.
656 of 1016
Feedback Time Pin (fbtime)
The feedback time pin contains a number, which is the amount of time (ms) the
control block waits between when it asked to take an action until it expects to get
feedback that the action is complete. For example, a solenoid is energized to move a
piece of equipment. It is expected to pick up a limit switch when the piece of
equipment is in position. If the limit switch does not pick up in the specified period
of time, a feedback diagnostic is generated. A time less than zero is equivalent to no
time limit and keeps the control code from ever generating a feedback time
diagnostic.
Merge Time Pin (mrtime)

The merge time pin contains a number, which is the amount of time (ms) the
sequence merge block waits at the completion of a parallel merge. If there are
multiple paths of a sequence, they all merge together with a merge block. This merge
block knows which sequence steps merge together. It keeps track of the time from
when the first sequence step merges until the last sequence step merge is complete. If
this amount of time is longer than the specified merge time, a merge time sequence
diagnostic is generated. A time less than zero is equivalent to no time limit and keeps
the control code from ever generating a merge time diagnostic.
Disable Feedback Fault Pin (dfbflt)

The disable feedback fault pin keeps the control code from generating a diagnostic
when this control code successfully turns something on and then later loses its
feedback. This pin might be used when automatic control code moves equipment
into a specified position. Because the equipment is in position, the feedback is high.
If the operator switches into manual control and subsequently moves the equipment
out of position, use the dfbflt pin to not generate a diagnostic.
Control Blocks that Generate Diagnostics

There are two control blocks that either directly generate diagnostics or supply
information used in the diagnostics generated. They are BENG_D and BENG.
These blocks that directly generate diagnostics have two pins in common:
dispgrp (display group) pin is a three-character abbreviation for the function the
application code is performing. For example, the display group for automatic width
control might be AWC. The display group is used by HMI to determine which
diagnostics are displayed at which stations based on the functions the operator at that
station needs to monitor.
For some control blocks, the status pin uniquely identifies the block of code that produced the diagnostic. (The
status pin has state information same status signal should never be attached to more than one control block.) The
used in performing logic. 50-character signal description for the status signal is the one-line description the
operator sees to describe the diagnostic condition.
657 of 1016
BENG_D
The BENG_D (Boolean engine with diagnostics) is a basic RLD, which performs
the logic specified by the contacts in the rung and sets the output coil accordingly.
This block can generate diagnostics in two different circumstances:
• If the output coil drops out, it generates a RUND (lists which signal(s) caused
the output coil to drop out). It also back-chains to check for signals in any RLDs
that feed into this block.
• If the signal on the request diagnostic pin goes True and the output coil is not
picked up, it generates a TRGD (lists the missing signals in order for the coil to
pick up).
Tip Normally a pushbutton (or other change in a logic state) is combined with
permissives to pick up the output coil. The output coil initiates an action in the mill.
To generate a diagnostic when the action is not permitted, wire the pushbutton to the
reqdiag pin, and also put it into a seal-in circuit in the RLD logic. The output coil
will seal-in around the pushbutton, if the action was initially permitted. In this
configuration, a diagnostic is only generated when the action is not permitted.
The BENG_D block has a disable diagnostics pin. This pin can be used to control if
a diagnostic message is generated or not, in the two circumstances described above.
This block also has a disable diagnostics back-chaining pin. This pin controls if the
diagnostic is traced back through the block to find the root signals or just report the
output coil.
The BENG_D block also keeps a time stamp whenever it’s signals change state. This
time stamp is used when a RUND is detected. The time stamps are checked to
determine which signals changed state immediately before the broken run condition
occurred.
BENG
The BENG (Boolean engine) is a basic RLD that performs the logic specified by the
contacts in the rung and sets the output coil accordingly. This block also has a
disable diagnostics back-chaining pin, which controls whether this block will allow a
diagnostic to trace back through it to find the root signals, or just report the output
coil. The BENG block keeps a time stamp whenever its signals change state. This
time stamp is used when a broken run diagnostic is detected. The time stamps are
checked to determine which signals changed state immediately before the broken run
condition occurred.
658 of 1016
Runtime Data Flow
The following section describes how diagnostics are routed to the HMI.
The HMI must be online when A control block generates a diagnostic. The controller diagnostic code captures the
the message is sent out to state of all inputs to that block, storing the states in a diagnostic message. The value
capture and store the in the dispgrp pin of the block is also stored. The diagnostic message is sent out
application diagnostic. over the diagnostic network and then read by the HMI.
The OC2000 keeps the latest diagnostics and faults, based on the value in the
dispgrp pin. The OC2000 reads the diagnostic message and, if it was configured to
care about this dispgrp value, stores the message in a list.
The diagnostic item in the OC2000 list only identifies the problem of the control
action. However, additional information to find out exactly what permissives caused
the problem can be requested and sent back to the controller over the diagnostic
network.
The larger computer-based HMI systems maintain a long list of all diagnostic and
fault messages sent over the DLAN+ or Ethernet. Again, the diagnostic item in this
HMI list just identifies what control action had a problem. When the operator wants
additional information, the HMI sends this request with the original information back
to the controller. However, in this case, the message is sent back over Ethernet. All
further pieces of information for the operator about this diagnostic are sent over
Ethernet.
Diagnostic Data
In addition to the actual code configuration, diagnostic data is stored in the symbol
table (.sym file) and the SDB.
Symbol Table
The Build and Download Diagnostic data is stored in the application diagnostic symbol table and downloaded
commands are explained in the to the controller. The Build command in the toolbox allows you to build the symbol
section, Building Pcode and table at the same time the configuration code is being built. Similarly, the
Symbols. Download application code dialog box allows you to download the diagnostic
symbol table immediately after the code is downloaded.
The symbol table contains two main pieces of data:
• Major revision when code was built
• Token numbers (addresses), and associated signal names and signal descriptions
Note When a diagnostic condition is detected, the identified permissives are

referenced by these addresses. The symbol table provides the correlation between the
address and signal name.
The diagnostics function in the controller only uses data from the symbol table when
the major revision of the code that the symbol table was built against matches the
code currently running in the controller. The symbol table and code must match for
the signal addresses in the symbol table to be correct.
Tip If a diagnostic, such as: token # 7074 can't resolve name, displays on the
HMI or OC2000, from the toolbox, rebuild the diagnostic symbol table from a .ucb
that matches what's running in the controller and then download the new diagnostic
symbol table. Also, perform searches using the Finder/Text/Address tab.
659 of 1016
Therefore, every time a major revision of the code occurs, the symbol table must
rebuild and download. When a new symbol table is downloaded, controllers do not
need to be stopped.
Tip The toolbox allows you to continually build and download the symbol table.
To automatically build, from the Device menu, select Build and the Build symbol
table option. To automatically download, from the Device menu, select Download/
Application Code and the Download symbols option.
To view the major and minor revision

If the toolbox is connected to the
controller, it also shows the 1. From Outline View, click to turn on Tracking.
major and minor revision of the 2. Click the controller name. The major and minor revision of the code currently
code in the controller. running displays in the Summary View.
Any major revision of the code Major revision of the code changes include:
requires you to rebuild and
• Status_S pages changes (even through getting information from the database)
download the diagnostic symbols
table. • Genius changes (besides just attaching a different signal to an existing I/O
point)
• Point is added to NOVRAM
• Network is added or deleted
• Signals were packed
Note When extra signals are added that might be in a diagnostic, you must rebuild
and download the diagnostic symbols table, even if the code did not change the
major revision.
Put Diagnostic Symbols into the SDB

When diagnostic symbols are put into the SDB, the data is obtained from the .m6b
currently open in the toolbox (not from the symbol table). The main symbol data
includes signal names and signal descriptions token numbers. Symbols should be put
into the SDB with every build.
660 of 1016
Dynamic Data Recorder (DDR)
The DDR feature collects data when specified trigger events occur. The advantage
of using DDRs over capture blocks is that DDRs can be reconfigured without having
to download application code to the controller. This enables changes to be made to
the DDRs without disrupting the controller during runtime. Up to 12 DDRs can be
configured for the controller.
Note DDRs can only be used by Mark VI Runtime V04.00.00C or newer. Also, due
to memory constraints, controller boards that precede the UCVE cannot use DDRs.
Create and Delete DDR

To insert a DDR
1. From the Outline View, click on the Dynamic Data Recorders item to
highlight it.
2. From the Edit menu, select Insert First.
Or, click the right-mouse button and select Insert First.
3. Once a DDR exists, insert another by following the same steps, but selecting
Insert Next.
To delete a DDR
1. From the Outline View, select the DDR to remove.
2. From the Edit menu, select Delete.
Or, click the Delete key.
661 of 1016
Configure DDR
To configure a DDR
1. From the Outline View, highlight the DDR to configure.
2. From the Edit menu, select Modify. Or, click the right-mouse button and select
Modify. The Dynamic Data Recorder dialog box displays.
Enter the Name of the Enter the name of the Status
DDR (use standard Signal (integer signal) used to
file name characters). store the DDR status.
Enter a string Description (up to 50

characters) of the DDR.
Enable Signal is used to manually

enable the DDR.
Check Auto Enable to automatically

re-enable the DDR after 60 seconds.
Period Multiplier specifies the
intervals for data collection.
Total Samples specifies the number of

DDR samples to record when the
trigger condition occurs. This includes
Pre-trigger Samples.
Condition is the comparison

condition that helps qualify when the
trigger occurs (refer to the options
below).
Type defines the way the trigger is
detected. Selecting edge means that the
DDR must observe the trigger signal in
the false condition at least once prior to
observing in the true condition.
Enter the signal to apply the trigger condition, type Compare Value is the
and compare value that determine if a trigger has threshold value against which
occurred. the trigger signal is compared.
Trigger Signal Condition options

eq equal to compare value
ge greater than or equal to compare value
le less than or equal to compare value
lt less than compare value
ne not equal to compare value
Note If the trigger signal is a Boolean type, eg and ne are the only available
conditions.
662 of 1016
Status Signals
Status signals, which indicate the status of the associated DDR, are used by the Data
Historian to determine when to upload the data. Status signals are always integers.
All 12 status signals must be assigned and placed on an EGD page for validation to
be successful, even if no DDRs are used. This is done because the status signals are
set up with the application code download. Adding the status signals initially
eliminates downloading application code when adding a new DDR.
To add Status Signals
1. In the Outline View, click on Dynamic Data Recorder to highlight it.
2. From the Edit menu, select Modify. Or, click the right-mouse button and select
Modify. The Dynamic Data Recorder Status Signals dialog box displays.
Source File indicates

which .tre file the DDR
setup information has
been exported to.
3. Click Browse… to assign a signal. The Signal Selector dialog box displays.
4. Select the signal to be used as the status signal. Click OK.
663 of 1016
Import and Export DDR
To import a DDR from a .tre file
1. From the File menu, select Import. Or, select the Import button . The
Import File dialog box displays.
2. From the Import File dialog box, select the .tre file that corresponds to the
DDR you wish to import. Click OK.
Note If the .tre file being imported contains the formatting flags %d or %n, then %d
will be replaced by the device name, and %n will be replaced by the Mark VI
devices Design Memo (DM) number. This is a GE Power Systems project number
whose value can be accessed by editing the device item and going to the Customer
Information tab.
To export a DDR to a .tre file

1. From the Outline View, highlight the DDR to be exported.
2. From the File menu, select Export, then Selected Item. Or, click the right-
mouse button and select Export Selected Item.
3. When the Export dialog box displays, click Save.
Note An Export All includes all the DDRs in a single .tre file.
664 of 1016
Add Signals
Signals can be added to a DDR. When a trigger occurs, these signals are collected by
the buffer and subsequently uploaded by the Data Historian and/or Trend Recorder.
Each signal is sampled for the total number of samples configured. This means that if
the DDR is set up to record 100,000 samples with three signals assigned, 300,000
items will be acquired. Up to 96 signals can be assigned to each DDR.
Note There is a 12-MB size limit on the memory that can be allocated to the DDRs.
If this memory allocation is exceeded, an error is reported during validation.
To add a signal
1. In the Outline View, highlight the DDR that you wish to add a signal to.
select Insert First.
The Dynamic Data Recorder Signal dialog box displays.
Enter the signal name

or click Browse... to
search for and select
a signal.
3. Click OK to insert the signal.
Update DDR
DDRs are updated separately from the application code download.
To update a DDR
1. In the Outline View, select Dynamic Data Recorders, then click the
Validate button .
2. From the Device menu, select Download, then Update Dynamic Data
Recorder. Or, click the Update Dynamic Data Recorder button .
665 of 1016
Chapter 4 Finder
Introduction
This chapter defines the features of the Finder. The Finder is a separate window in
the toolbox, which contains several useful find tools. It can help you find items, such
as text, overrides, differences, and signal/variable usage from the different types of
devices.
Note The SDB Browser is another window that finds items, such as signal usage,
system topology, signals on the SDB, and more (refer to GEI-100506).
Section Page
Using the Finder .......................................................................................................4-2
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 4 Finder • 4-1
666 of 1016
Using the Finder
¾ To use the Finder
1. From the View menu, select Finder. The Finder window displays (see the next
Or click .
section, Finder Window).
2. Select a target from the drop-down Target List. (All loaded targets are listed.
The default target is the current device.)
3. Select a tab according to the type of search desired.
4. Enter each field of the tab (described in the next section).
5. Click . Once the search completes, the Output View and Status bar
display the results.
Tip ª By default, the Finder closes when the Find button is clicked on or when you
click any part of the screen outside the Finder Window. Click to keep the Finder
open.
Finder
Title Bar
To resize the window:
Toolbar
Target List 1. Click the window to
Tabs highlight it.
2. Point the mouse
arrow on any side of
the window until the
double arrow displays.
3. Click the arrow and
drag the window to the
desired size.
Output
View
Status bar
4-2 • Chapter 4 Finder GEH-6403L Toolbox for a Mark VI Turbine Controller
667 of 1016
The Finder target determines the device and area of the search. When the Finder is
activated, it automatically selects the current device as the target and displays it in
the Title bar. A target performs various finds:
Target Can find
SDB Signals
OC2000 Text
AcDcEx2000 Text, variable usage, override, difference
Innovation Series drive Text
Innovation Series and Mark VI controller and System Information Text, signal usage
EX2100 Text, signal usage
Located below the Title bar is the toolbar.
Click… To…
Hold the Finder Window open. If this pushpin displays, the Window closes when the area outside the
Finder Window is clicked. Click the pushpin to keep the Finder on top of the Device Window, even when
you click outside the Finder Window.
Close the Finder Window. This pushpin displays when the pushpin above is clicked. The Finder Window
remains opens when the pushpin is in this position (even when working in another window).
Goto an item in the Outline View. Highlight an item in the Output View, then click this button to find it in
the Outline View. Double-click an item to edit it.
Hide the tabs and make the Finder window display only the Output View.
Target Finds
The Finder contains tabs that display according to the device selected in the drop-
down box, Target List and the tab selected (type of find). The following sections
describe each tab.
Refer to the SDB Browser in The Text/Address tab allows you to search for all text and address usage. It is
GEI-100271. available on all targets, except the SDB. The Signals/Variable Usage tab allows you
to search for signals/variables in a controller, AcDcEx2000, or System Information.
Signals apply to a controller
The Override tab and Differences tab display only when the target is an
or System Information target.
AcDcEx2000 device.
Variables apply to an ¾ To perform a find
AcDcEx2000.
1. From the Outline View, click an item to search.
2. From the toolbar, click . The Finder displays to begin your search. Select
the desired tab as described in the following sections.
668 of 1016
Text/Address
Enter the text to find.
The drop-down box allows

you to access previous
finds.
Click here to include all

note message boxes in
the find.
Click Find to start the find.
All text found displays in

the Output View.
Method allows you to qualify the find by selecting one of the following from the drop-down
box:
Anywhere In matches items that contain the find text anywhere within their text.
Begins with matches items whose text begins with the find text.
Exact matches items who text is exactly as the find text.
Using wildcards (*,?) allows the characters (* and ?) to specify multiple and single match-
anything characters.
Address is for the ACDCEX2000 and matches items who address is the same as the find
text. This method is also useful for finding controller signal names related to token numbers,
such as diagnostic that have an out of date symbol file.
4-4 • Chapter 4 Finder GEH-6403L Toolbox for a Mark VI Turbine Controller
669 of 1016
Signal/Variable Usage
Select the target

from the drop-down
list.
The Track Highlighted

Item box is checked by
default. This indicates
that the currently
highlighted item in the
Outline View is the
signal variable to find.
The signal/variable items

that are found display in
the Output View.
Note When a different item is selected in the Outline View, the Find is performed
again. Click the option Track Highlighted Item to uncheck it and prevent the find
from executing each time the Outline View item changes.
670 of 1016
Notes
671 of 1016
Chapter 5 Batch Operations
Introduction
This chapter describes the Batch Operation mode. This mode performs a variety of
functions, such as Validate and Build, on any number of files of different device
types. This is especially useful when recreating the system database or when the
process contains multiple devices.
Section Page
Batch Operations File ...............................................................................................5-2
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 5 Batch Operations • 5-1
672 of 1016
Batch Operations File
File name(s) must be added to a new batch operation or names can be edited in an
existing .bld file.
To create a batch operations file
From the File menu, select New. The New dialog box displays.
Or click
Click the tab, Utilities.
Select Batch
Operations
File.
Click OK.
The Batch
Window
displays.
Toolbox Command Line Options
The toolbox can be run from the command line and perform a number of specific
operations. The command line operation allows for performing actions with
automation. A listing of the command line operations is shown below. Command
line options can be sepecified with a dash (-S) or with a forward slash (/S). All
descriptions and examples are shown with the forward slash.
5-2 • Chapter 5 Batch Operations GEH-6403L Toolbox for a Mark VI Turbine Controller
673 of 1016
The various command line options in the toolbox are as follows:
Command Line Definition Usage Example
/S Disable the Splash Screen when Toolbox/S
starting toolbox
/U Sets the User ID. The command
should be followed by a user
name (3 Chars)
/R Performs batch operations Toolbox /R <file Toolbox /R C:\Site\Master\Batch1.bld
name> (.bld - batch operations file)
/SupressUI Hides the toolbox window
/ControlSpecCsv Generates IO Config Report.csv Toolbox/ControlSpecCsv Toolbox /ControlSpecCsv
and CSP Signal Report.csv files <file name> C:\MkVI1.m6b (should be .m6b file.)
/IoReportCsv Generates IO Report.csv file Toolbox /IoReportCsv Toolbox /IoReportCsv C:\MkVI1.m6b

<file name> (This file should be .m6b file.)
/ControlSpecCsvV9 Same as /ControlSpecCsv. but
the report file is generated in
Version 9 format
/IoReportCsvV9 Same as /IoReportCsv. but the
report file is generated in Version
9 format.
/ImportOrderingDrawing Imports Ordering Drawings Toolbox <Device file Toolbox C:\Mkvi1.m6b
name> ImportOrdering /ImportOrderingDrawing
Drawing <Drawing file C:\Drawing.tsv (Ordering drawing file
name>
should be .tsv or .csv file.)
/ImportControlConstants Imports a Control Constant file to Toolbox ImportControl Toolbox /ImportControlConstants
an .m6b file. Constants <Device file C:\Mkvi1.m6b
name> <Control Constant C:\ControlConstants.csv
file name>
Toolbox Toolbox –ImportControlConstants
/ImportControlConstan C:\ControlConstants.csv
ts <file name>
/ExportOSMReports Generates the following .csv files Toolbox Toolbox /ExportOSMReports
- Signal List Report.csv /ExportOSMReports C:\MkVI1.m6b (The file should be a
<file path> .m6b file.)
- Alarm List Report.csv
- Event List Report.csv
- Scale List Report.csv
- Enumerated Data Types
Report.csv
- EGD Network Report.csv
- Control Constants Report.csv
- IO Point List Report.csv
- SOE Report.csv
/BatchCsv Executes a Batch CSV file Toolbox /BatchCsv Toolbox /BatchCsv C:\Batch1.csv
<file name> (The file should be a .csv file.)
/Q Runs batch file in quiet mode. Toolbox /BatchCsv Toolbox /R C:\Batch1.bld /Q
Use with /R and /BatchCsv <file name> /Q Toolbox /BatchCsv C:\Batch1.csv /Q
commands
/Version Writes the version of the /Version <Device file /Version C:\Site\MkVI1.m6b
particular device file to an output path> <Output file C:\Site\version.txt
file. path> The input file should be a device file.
The output file contains the version
number of toolbox that last wrote to it.
Number is in the form: V11.02.03C
674 of 1016
Batch Window
File Names is the list of files upon which the commands are
performed. The files are opened in the order shown in the list.
Use the edit buttons to modify current positions. Add Files(s)...inserts
the names of files in
the file names list.
Remove deletes the

highlighted name(s)
from the file names list.
Copy makes an
additional copy of the
highlighted files in the
file names list..
Move Up moves the

highlighted files up the
file names list.
Move Downmoves
the highlighted files
down the file names
list.
If an error occurs:
Stop stops the batch

operation.
Continue continues the

batch operation at the
Add inserts the commands highlighted Remove removes the next command.
the Available Commandslist into the highlighted from the Available
Selected Commandslist. Commands list. Next File continues the
batch operation at the
The window at the bottom of the screen next file.
provides status information, including errors.
675 of 1016
Configure a Batch Operation
To add to the File Name list
From the Batch operations dialog box, click Add…. The Add File dialog
box displays.
Select the file(s)

to be added to the
File Names list.
For more information, refer Tip If you are using the Checkin/Checkout utility, make sure all files added to the
to Chapter 6, File File Names list are checked out, in Exclusive (read/write) mode. Otherwise,
Checkin/Checkout. operations may not work and not be found until the Error Log file is examined.
To configure a batch operation

1. From the Batch operations dialog box, edit any File Name(s) with the
command buttons (Move Up, Move Down, and Change).
2. Select all commands to be performed on each file.
3. Select an Error option.
4. Click Save to save the Batch Operation to a .bld file.
5. Click Start to run the Batch Operation.
676 of 1016
Run a Batch Operations File
Run a Batch Operations file in one of three ways:
1. Click Start in the Batch Window.
2. Select a command prompt.
3. Open a .bat file.
To run the toolbox from the command prompt, type toolbox and the name of the .bld
file. If the directory of either the toolbox or the .bld file is not in the path, the
directory names must be included in the command line.
Two command line options are available:
• The -r indicates that the batch should run immediately and not wait until the
Start button is pressed.
• The -u_ _ _ (three-character user ID) is used to enter a user ID so that the Enter -
User ID dialog box will not display before each file is opened.
Running a batch file from the command prompt works the same as the toolbox
interactive mode. The toolbox opens, runs, and completes the Error log. The Error
log (.log) can be viewed from a text editor.
A batch operation can also be initiated from the command line using a .csv file
which had been exported from a batch build (.bld) file. The batch operation can also
be run in quiet mode using the –Q option (as shown below). In quiet mode, the
toolbox will run minimized, and no message boxes will pop up. All operation
information will be written to the log file. The log file will be created at the same
location in which the command line is run. The command line information is shown
below:
–BatchCsv or /BatchCsv - Runs a Batch .csv file.

Usage: Toolbox –BatchCsv <file name> or Toolbox /BatchCsv <file
name>
Example: Toolbox /BatchCsv C:\Batch1.csv (should be a .csv file).
–Q or /Q - Runs a Batch file in quiet mode.
Usage: Toolbox –BatchCsv <file name> –Q or Toolbox /BatchCsv
<file name> /Q
This option can be used with both /R and /BatchCsv commands.
Example: Toolbox /R C:\Batch1.bld /Q

Toolbox /BatchCsv C:\Batch1.csv /Q
677 of 1016
System Make Wizard
The System Make wizard populates the Batch File with the necessary files and
commands to prepare all project files for download.
To run the System Make Wizard
1. From the Edit menu, select System Make Wizard.
2. Specify the root directory of the project configuration files.
3. Click OK.
The wizard scans all folders beneath the root folder and adds all relevant files to the
file names list. The wizard also selects all necessary commands for those files.
Note Check the file list after running the wizard to make sure that there are no
unnecessary files included in the list.
678 of 1016
Batch Error Log File
During a Batch Operation, a log window displays the status messages produced
during the operation. This log is written to a file with the same name as the .bld file
and the extension .log. Any errors that occurred during the operation are also
displayed here.
Open and Save Batch Operations File

To save a .bld file
Press the Save button on the Batch Operations dialog box. From the Save
dialog box that displays, enter a file name.
To open an existing .bld file
From the File menu, select Open. From the Open dialog box that displays,
select the desired file name and directory.
Import and Export Batch Operations File

Batch Operations files may be modified using text editors, then imported or exported
by means of Command Separated Variable (.csv) files.
To export a .csv file
From the File menu, select Export to CSV. From the Save dialog box that
displays, select the desired file name and folder.
To import a .csv file
From the File menu, select Import from CSV. From the Open dialog box that
displays, select the desired file name and folder.
679 of 1016
Chapter 6 File Checkin/Checkout
Introduction
This chapter describes the Checkin/Checkout utility, which allows you to share files
contained in a master location. The files in the Master Directory are checked out into
the specified Local Directory in either Share read (read-only) or Exclusive
(read/write) mode.
Initialization
Note This utility does not prevent the File Manager from overwriting the files in the
Master or Local Directory.
¾ To initialize the Master Directory

1. From the File Manager, select a directory to maintain the Master files.
2. Copy all desired files into this Master directory.
3. From the Program Manager, double-click the Checkin/Checkout icon. The
Checkin/Checkout Utility dialog box is displayed.
4. Select the Master Directory and Local Directory.
When the utility is run for the first time, a lock (.lck) file and text (.txt) file are
created in the specified Master Directory. The user.lck file keeps the current lock
state of all files processed by this utility. The userlock.txt keeps track of all the files
in the Lock File Data screen.
The Checkin/Checkout dialog box contains two directories to manage shared files.
The fields and commands are as follows:
Local Directory and Master Directory display a list of files and the current lock
status of each file, based on the List of Files Type list box. Browse… allows the
user to select a drive and directory for both the Master and Local Directory.
List of Files Type provides a choice of filenames to display, based on the filename
extensions in parentheses. The default extension is All Files (*.*).
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 6 File Checkin/Checkout • 6-1
680 of 1016
Click Checkout to copy the highlighted file(s) Details displays the current Lock File
in the Master Directory list to the Local Data (File, Lockstate, Computer: User,
Directory list. Directory access must be Date/Time) of all files that are processed
Shared read file(s) are
granted. by this utility.
copied to the Local
Directory as read only files.
These file(s) are displayed
with an R after the file
name. The file(s) can be
copied, even if locked by
another user. Any attempt
to write to the file causes a
Permission denied error
message.
Exclusive files(s) are
copied to the Local
Directory as read/write
files. This denies anyone
else access to check the
file out in Exclusive mode.
Click to copy the highlighted

file(s) in the Local Directory
to the Master Directory.
Directory access must be
granted.
Note: The highlighted file
must be in Exclusive mode
or it must not exist in the
Master Directory. The file is
set to read only (R) in the
Master and Local
directories after copying. Select the type of file(s) to Access forces the lock of the selected Master Directory to
Other users can now check display in the Master Directory you. Use this only if no other users are using this utility and
out this file. list. the lock is granted to another user. This will happen if the box
is turned off or the task is terminated while running the utility.
Unlock removes the lock on the currently highlighted file(s) in
the Master Directory. This removes the file(s) from being
controlled by the utility. Unlock makes the master copy and
the local copy of the file accessible.
Note The Unlock command is unconditional (the file is not copied or changed in
any way). The user is responsible for managing the file. The read attribute is left
enabled on the master file.
6-2 • Chapter 6 File Checkin/Checkout GEH-6403L Toolbox for a Mark VI Turbine Controller
681 of 1016
Chapter 7 Configuring System
Information
Introduction
This chapter provides instructions for using the toolbox to configure System
Information. System Information is used to configure information global to a project.
This information includes data such as scale factors, CIMPLICITY® Human-
Machine Interface (HMI) resource names, enumerations, and alarm classes.
Once the configuration for System Information is defined, the data is put into the
System Database (SDB) for access by other drives, controllers, and interfaces.
Section Page
Working with System Information Files ..................................................................7-2

Concepts ...................................................................................................................7-2
Configuration............................................................................................................7-3
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 7 Configuring System Information • 7-1
682 of 1016
Working with System Information Files
System Information is configured using two types of files:
Binary working files (.syb) contain an exact copy of the configuration used by the
toolbox. Users generally work from .syb files.
Project files (.prj) are text files containing property and system configuration
information. The files transport the System Information to different versions of the
toolbox.
Concepts
There is no hardware item for System Information (such as the drive or controller) in
the toolbox. System Information is used primarily to configure and manage
information global to a project. This information includes Scale Definitions, and
resource names (Type Definitions).
Scale Definitions
The ownership of scale Scale definitions are scale factors associated with signals. They are used to
definitions, those of System
Information as well as of • Scale raw I/O into engineering units used internally by the blockware in a
controller or CIMPLICITY HMI system.
other devices, is maintained
in the database. • Provide unit, precision, and limit information for a signal.
Alarm Classes
An alarm class, which defines the attributes for a classification of alarms, is created
for each group of related alarms that share a common priority and color scheme.
Type Definitions
Resource Names
System Information defines Resource names are stored within a special Type Definition named Resource. Any
and puts resource names into signal put into the database can be associated with one resource name (just like a
the database. This makes the signal can be associated with a scale definition). This resource name groups signals
resource names available to used by the CIMPLICITY HMI system. When some systems import signals into
other devices that can then CIMPLICITY, the resource name is used to determine which signals get imported.
assign them to appropriate (For example, you can import all the signals that have a resource name of Entry.)
signals. The resource name can also be used as a filter for displaying alarm/event data on a
CIMPLICITY HMI.
Enumerations
Enumerations are defined as type definitions. Properly defined enumerations are
stored in the SDB when a System Information Put Into Database command is
performed. To qualify as an enumeration, the Type Definition must be Enumeration
with a Base Datatype of Int. If a second language has been defined, then for each
enumerated field, there are text boxes for both languages. The enumerations is the
SDB are imported into the CIMPLICITY system when the HMI Device performs a
7-2 • Chapter 7 Configuring System Information GEH-6403L Toolbox for a Mark VI Turbine Controller
683 of 1016
build. One language enumeration description over the other is imported into
CIMPLICITY depending on which language is selected in the HMI Device.
Measurement System
The names are entered in the The Measurement System defines the names of the two measurement systems. The
System Device Name dialog names are used for dual scales when creating a scale definition. Measurement
box. Refer to the section, System 1 should be the primary measurement system used in the project. The default
Configuration. name for System 1 is US, and the default name for System 2 is Metric.
System Overview
The system overview provides the ability to access various configuration files and
other executables through an animated drawing interface. Requisition engineering
provides the overview drawing in a metafile format to be used by the Toolbox.
Configuration
Create/Modify System Information

To create System Information
Or click 1. From the File menu, select New. The New dialog box displays.
2. From the System Configuration tab, select System Information and click
OK. The System Information window is created with a temporary name,
such as sys1. The Outline View contains these items:
To modify System Information name

1. From the Outline View, click the name to highlight it.
Or double-click the name. 2. From the Edit menu, select Modify. The System Device Name dialog box
displays.
684 of 1016
Enter the desired Measurement
System names (12 character limit) for Turbine System must be checked to
System 1 and for System 2. The apply Measurement Systems and the
names displayed are the defaults. Dual Language Definition.
Select the desired language

from the drop down boxes.
Language 2 is required for
turbine systems that use the
Language Translation feature of
Turbine Controls Interface (TCI).
This feature allows alarm
messages and events to be
displayed in either Language 1
or Language 2. These definitions
are also used by the HMI device
when importing signals into the
CIMPLICITY HMI system.
Note: Both the Measurement System configuration and the Dual Language
Definition are stored in the SDB when performing the command, Put into
Database for the System Information.
685 of 1016
Insert/Modify Scale Definitions
Scale definitions can be associated with signals. They are used primarily to scale raw
I/O into engineering units used internally by the blockware. For the controller, scales
can be created in the toolbox and then put into the database.
Tip On many large processes, scales are defined in System Information, allowing
all controllers to use the global scale. To modify a scale, you can immediately open
the system information file instead of searching all the controllers to find the scale.
To insert scale definitions

1. From the Outline View, select Scale Definitions.
Or use the shortcut keys, Shift Or, click the right-mouse button and select Insert First. The Scale definition
+ Insert. dialog box displays.
To modify scale definitions
1. From the Outline View, select the scale definition name.
Or double-click the scale 2. From the Edit menu, select Modify. The Scale definition dialog box
definition. displays.
Scale Names are defined in the Measurement System dialog box. If
multi-scales are desired, enter the primary scale name in the textbox
for System 1. Refer to the section, Measurement System.
Enter the Minimum

and Maximum values
of each system and
Raw to provide the
conversion informaton.
Enter a description of
the scale definition
(50-character limit).
Enter the Unit names for each system (five-character

limit). Select the Precision from the list boxes.
686 of 1016
Resource Type Definitions
Refer to Chapter 3, the Resources are defined as type definitions. The resource type definition allows the
section Type Definitions. CIMPLICITY HMI to group signals. System Information puts the resource name
into the SDB for other devices to get the resource names and associate them with
signals.
Resource is always of Basic Data type: String. When resource names are first
defined, it is not necessary to assign a value to the value name (refer to the resource
Type definition dialog box). This is done automatically when System Information
puts the data into the database. For example, the following list displays a set of
resources entered without a value.
After System Information puts its configuration into the SDB, values for each
resource name are assigned automatically by the database.
687 of 1016
Enumerations
Enumerations are defined as type definitions. Properly defined enumerations are
stored in the SDB when a System Information Put Into Database command is
performed. To qualify as an enumeration, the Type Definition must be Enumeration
with a Base Datatype of Int. For each enumerated field, the Note field must be filled
out with not more than 32 characters. The reason for this rule is that the Note field is
multilingual and is used as the enumerated text field in CIMPLICITY.
The following is an example of an enumeration.
The enumerations are placed in the database with the Put into Database
command, which makes them available for use as a datatype by signals.
The HMI configuration will import all enumerations in the SDB into the
CIMPLICITY system. Any signals on EGD that use one of the global enumerations
as a datatype will have the corresponding CIMPLICITY point associated with the
CIMPLICITY enumeration.
688 of 1016
Alarm Classes
To insert an alarm class
1. From the Outline View, select Alarm Classes.
select Insert First. The Edit Alarm Class dialog box displays.
Enter the alarm class

Name (five-character
limit).
Enter the alarm class

Priority (0 through 9,
with 0 being highest).
Enter a Description of
up to 50 characters, if
desired.
Select Foreground
and Background
colors for the Normal
State, the Alarm State,
and the Acknowledge
State.
689 of 1016
System Overview
The system overview is used to graphically access the configuration files and
programs used in a system. The hyperlinks on the drawing display the associated
binary configuration files.
690 of 1016
Configure System Overview Settings
To configure System Overview settings
1. From the Outline View, select the System Overview item. The Edit Overview
Settings dialog box displays.
Select the metafile

to be associated
with the System
Overview.
Click Add to
enter target
information into
the Edit
Overview Target
Settings dialog
box.
2. Click the Add button to display the Edit Overview Target Settings dialog
box.
The target
Name is the
name as it
appears on the
windows
metafile.
Two lines of
text can be
entered to
describe each
target.
Enter the
executable or
binary
configuration
file to be
associated with
the target.
The Summary View then displays the metafile with the target text. The command
associated with the target can be run by double-clicking the hyperlink in the metafile.
691 of 1016
Put Data into Database
To make configuration information available to other devices through the system
database, you must use the Put into Database command.
To put data into the database
From the Device menu, select Put Into Database. A warning message box
displays to confirm the operation.
692 of 1016
Notes
693 of 1016
Chapter 9 Hardware and I/O
Introduction
This chapter defines the controller networks and inputs and outputs (I/O) used in the
toolbox. It includes configuring a network interface, and signal and I/O connections
used in blockware.
Section Page
I/O and Network Interface........................................................................................9-2

Mark VI I/O..............................................................................................................9-5
EGD Interface.........................................................................................................9-34
Genius Networks ....................................................................................................9-42
Main Board.............................................................................................................9-63
Register Network....................................................................................................9-67
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 9 Hardware and I/O • 9-1
694 of 1016
I/O and Network Interface
A controller configuration can be divided into two sections, Blockware and I/O. I/O
items, also known as hardware modules, can be found/created in Outline View of
the toolbox under the item, Hardware and I/O Definitions. These items define the
I/O or network interfaces used by the controller and connect I/O with signals to be
used in blockware. Also, many items monitor the live data of specific I/O points and
their associated signals, so you can see the transfer from I/O to the signal or from the
signal to I/O. All controller hardware modules are composed of points. Sometimes,
between the points and network interface level there is a further division of points
into pages or blocks.
I/O Points
Points are the I/O for the controller and must be associated with signals to be
accessed in blockware. This point-signal association is very important to the
controller function.
I/O points also represent a buffer separate from the signals used by controller
blockware. This memory is modified directly by drivers that handle the various
controller interfaces as well as by blockware. Blockware reads and writes these I/O
points through I/O transfers. These transfer data from input points to their signals at
the execution of tasks that use those signals. Transfers of data from signals to their
associated output points occur at the end of the execution of tasks that use those
signals, as shown below. For any signal connected to an I/O point, the direction of
point determines whether it is considered an input or an output.
Note A point can never be both an input and an output.
Inputs written to
signal space before
a task runs
Network 1 Mark VI Turbine Network 2

I/O Points Controller Signals I/O Points
Outputs written
from signal space
after a task runs
A signal can be connected to more than one point. If one of the points is an input and
one is an output, the controller transfers the value of the point from the input to the
output through the signal. This I/O transfer occurs regardless of whether the signal is
used in a task. The runtime process that performs this function periodically in the
background (during idle time) is called the I/O mapper, since it maps inputs to
outputs.
9-2 • Chapter 9 Hardware and I/O GEH-6403L Toolbox for a Mark VI Turbine Controller
695 of 1016
To edit controller properties
1. From the Outline View, double-click the device name (top of Outline View).
The controller device Properties dialog box displays.
2. From the General tab, select the following options.
Name specifies this
controller when
communicating with
the SDB. It defaults
to mkvi1 the first
time a controller is
created. The name
is saved as a .prj.
Clock specifies
the source of the
clock as internal or
external. For Mark
VI controllers, set
the clock to
External (unless
the hardware is a
simulator).
Platform specifies
the hardware
platform on which
the configuration
operates. This field
is important for
proper control
execution records
and for selecting Select the Device No. is the system SDB
hardware and I/O. basic I/O and number. If set to 0, the next Select this check Select this check box Select the interval (ms) that
For more detailed compute rate available SDB number is box to to enable the the I/O mapper task runs.
information on for a Mark VI assigned to the device when indicate that Controller Load The I/O mapper task
selecting the system. data is entered into the you are Profiler for the transfers signals between
appropriate database. operating a device. different I/O points, if the
platform, refer to TMR system. signals are not used in
Chapter 9, blockware code.
Hardware and I/O.
696 of 1016
Configure Boards
A point can have configuration data, as shown in the summary view below for
‘ThermCpl3’.
Configuration is data that
applies to the complete
board.
Card Points contain I/O
points not directly associated
with a terminal board.
Signals can be attached to
Card Points, I/O points, but
not Internal Variables
Modify the board by clicking +

to expand it.
With the right mouse button,

click on an item name. Select
Modify from the pop-up
menu.
Refer to the following sections

for more information on each
board item.
The configurable items for the terminal board points can be modified at one common
window.
To modify a point’s configuration
1. From the toolbox, Outline View, expand the I/O board.
2. Expand the terminal board (J3J4:IS200TBTC).
3. Right-mouse click on the point to modify and select Modify from the shortcut
menu. The following dialog box displays.
697 of 1016
5. Click on the desired ‘Value’ cell to modify the configurable item. Depending on
the typeof configurable item, drop down items are displayed, or you can enter a
number.
6. Click OK button. The values are saved to the configurable items. When the
point is selected in the toolbox outline view, a list of the configurable items and
their values display in the summary view.
Both board points and points that are part of a terminal board can be connected to a
signal, using the upper part of the MarkVI Point Edit dialog box. A point that does
not have any configurable items uses a different dialog box as shown in the next
section.
Note Other configurable items include regulators, terminal boards and monitors.
698 of 1016
Configuration
Depending on what item is

selected under Configuration, a
dialog box displays to enable/
disable, select high/low limits,
select operation mode
such as TMR or Simplex.
(This dialog box is also used

when configuring points under the
item Card Points.)
699 of 1016
Card Points
A point can be configured and be modified by selecting the Edit menu, then
Modify. The software configuration dialog box displays.
The board, VTCC,

contains the items
Card Points and
terminal board with
points.
The points contain

Configuration,
which can be
modified.
Both of these items can be connected to a signal using the Point Edit dialog box.
To connect a signal to a point
1. Expand the configuration item and select a point.
2. From the Edit menu, select Modify. The Point Edit dialog box displays.
Enter the name of the signal to

connect or click Browse… to
search for an available signal.
Displays the Point Descriptors

dialog box where you enter
distinct information about this
point.
Edit the signal you entered as the

signal connection.
Note Other items in this dialog

box are fixed and cannot be
modified for a Mark VI I/O.
700 of 1016
Terminal Boards
Some properties of a terminal board can be modified.
To modify the properties of a terminal board
1. Click on the terminal board to select it
2. From the Edit menu, select Modify. The Terminal Board Properties dialog
box displays
The Connector
Name cannot be
changed.
The Connected
box must be
checked to
configure the
Terminal Board
and the
Hardware Form.
Select the
terminal board
and the hardware
form to be used.
701 of 1016
Upgrade Boards
You can upgrade existing boards and modify some of the board’s attributes.
To upgrade a board
1. From the Outline View, click the item Mark VI I/O to highlight it.
2. Select the Import button or from the File menu, select Import. The File Open
3. Select the file, Mark_IO.tre. Click Open.
4. Once all .tre files are imported, go back to the Outline View. Select the board
to upgrade. Right-mouse click and, from the shortcut menu, select Upgrade.
5. Select the hardware form factor and other attributes with dialog boxes described
in the preceding section, Select I/O board.
Note If a terminal board’s connection status changes, an offline change occurs and a
warning message displays for confirmation. Once inserted, terminal board properties,
hardware form factor, or compatibility codes can only be modified by upgrading the
board.
Compare I/O Board Commands

Use the following commands to compare an uploaded I/O board.
• Compare with configuration information
• Upload the board configuration to a binary file
• Compare a previously loaded binary file to the configuration
702 of 1016
Compare Configuration
To compare the board configuration with the current configuration
From the Outline View, right-mouse click on the board and select Compare
Configuration from the shortcut menu.
Any differences display in a window as follows:
Select the check box

next to the item to
read configuration
contents into the
current configuration.
Click to generate a
report of differences.
The following report displays.
Note Comparing a TMR board can result in three differences per board since a
comparison is done for all three boards and generally the same configuration is
downloaded to all three. To accept the board’s value into the current configuration
from the Differences dialog box, click the check box next to any one of the three
values, then click OK.
703 of 1016
Download Board Configuration
All the configuration items within a board can be downloaded for one board, a whole
rack, or all the racks.
When you select Mark VI I/O To download board configuration
or any of its associated items
1. Select the item to download.
under the Hardware and I/O
Definitions section, the menu 2. From the Config menu, select Download. Or, right-click the item to
bar will change to include the download and select Download from the shortcut menu.
Config menu.
704 of 1016
Download Firmware
To download Mark VI firmware
1. In the Outline View, select Mark VI I/O.
2. Click the right-mouse button and select Download from the following menu:
3. From the Download all Mark VI I/O dialog box, select Download Firmware.
Click OK.
4. The following warning displays. Click Yes to start downloading firmware to the
cards in all the project racks. Refer to the status messages at the bottom of the
toolbox window.
705 of 1016
Compare Board Revisions
To compare board revisions between device and toolbox
1. In the Outline View, select Mark VI I/O.
2. Click the right-mouse button and select Compare H/W Board Revisions
from the following menu:
3. If the device is not online, the following message box displays:
4. Click Yes to connect to the device and read board revisions. Click No to read
only Toolbox board revisions.
706 of 1016
The output is displayed in a window as follows:
A # icon indicates there is a difference between toolbox and device values. The
difference could be in any of the values – card name, hardware form, and
firmware revision.
707 of 1016
Upload Configuration to File
Upload a board configuration into a binary file to allow it to be accessed for
comparisons.
To upload a configuration into a binary file
1. From the Outline View, right-mouse click on the board to be compared.
2. Select Upload Config to File from the shortcut menu.
3. Select a file name for the binary file (a suggestion is provided, based on device,
name, channel, board, and slot.)
4. Click Save to save the file.
Compare Configuration to File

You must have access to a binary file to use this command.
To compare configurations
1. From the Outline View, right-mouse click on the board to be compared.
2. Select Compare Config to File from the drop-down menu.
3. Select the correct file, then click Open to complete the comparison.
Refer to the section, Compare Configuration, for the results of this compare.
708 of 1016
VSVO Servo Board
The VSVO board controls four electohyralic servo values (refer to the section Insert
I/O Board). In the toolbox configurable items include, Regulators and Monitors. Up
to four Regulators, which are automatically numbered consecutively, can be added to
a configuration.
To add a Regulator
1. From the toolbox under VSVO, expand the items and select Regulators.
Right-mouse click on
Regulators
Select Insert First from the

shortcut menu.
Regulator 1 is inserted.
2. Calibrate the Regulators as follows:

(LVDT/R Calibration Dialog Box).
Right-mouse click on the

Regulator 1.
Select Calibrate from the

shortcut menu.
The following Warning
displays.
Click Yes to continue with the calibration process.
If the controller is not online

the following dialog box displays.
Click Yes to go online to

calibrate the regulator.
The LVDT/R Calibration
dialog box displays (refer to
the next section).
Click No and the toolbox allows you to select to view Constant
(refer to the section, LVDT/R Calibration Dialog Box).
709 of 1016
LVDT/R Calibration Dialog Box
This command starts the Click View to display the
Note Each variable is Calibration Mode. predefined Position Gain and
monitored to see if the state Click On to enter Calibration Position Offset tuneup
was performed successfully. Mode or click Off to unselect constants stored in the board
the mode. (refer to the section, Calibration
Calibrate Sequence Constants Dialog Box).
commands
are as follows:
Click Min End Pos to stroke

the actuator to the minimum
end position.
Click Fix 1 to read the voltage

at the Min End Pos.
Click Max End Pos to stroke

the actuator to the maximum
end position.
Click Fix 2 to read the voltage

at the Max End Pos.
Click Calibrate to use the

calculated values.
Click Save to save calculated

board values .
The values are saved in the

toolbox and downloaded with a
new sequence number.
Dynamic Signals are During the verification process, you can send a manual
available while online and value to the board and inspect the movement of the
when this dialog box displays. actuator.
These signals are supplied
with voted live data through Verification commands are as follows:
the controller.
Click Off to turn off this mode.
Click Manual to enter a value in the text box.
Click Send Manual to send the entered value to the

board.
Click Verify Position to step the current and monitor the

position.
Click Verify Current to step the position and monitor the

current.
The Trend Recorder allows you to view the actuator

position or current feedback.
710 of 1016
Tip If the calibration permissive is not set, all command buttons are grayed out.
This permissive is driven by controller blockware. The output point is CalibEnabx
where x is the selected regulator. Find this point in the application code and
determine why the permissive is not set. Once this permissive is set, return to this
dialog box and select On again.
Once in Calibration Mode, all the command buttons are available. The toolbox
monitors the calibration permissive and the state bit as follows.
• If calibration permissive is lost, all buttons on the dialog box gray out, except for
the Constants View button and the Dynamic Signals list.
• If the calibrate state bit is lost, all buttons on the dialog box gray out, except for
the Calibration Mode On and Off, the Constants View button, and the
Dynamic Signals list.
In Simplex and TMR operations, you receive a message from any of the requested
commands that are not complete. For example, in a TMR operation, if the
Calibration Mode was requested for all three channels (R, S, and T) and only the R
and S channels are available, you are notified that the T channel would not go into
Calibration Mode.
Verification is found on the In Calibration Mode, you can step through the calibrate process by selecting each
Calibration dialog box, just button in the field, Calibrate Sequence. If the requested state is achieved by all
under the field Calibrate appropriate systems, the button stays depressed. If there is a problem, the command
Sequence. button releases, indicating that the requested state was not achieved. The Min End
Pos, Fix 1, Max End Pos, Fix 2, and Calibrate buttons are mutually exclusive
(only one state may be active at any one time).
Modify Regulator & Monitor

The configurable items Regulator and monitor can be modified at one common
window.
To modify a Regulator or Monitor
1. From the toolbox, expand the VSVO board.
2. Expand the Regulator or Monitor.
3. Right mouse click on the item to modify and select Modify from the shortcut
menu.
Note You must have a privilege level 4 to view the configurable items unless.
711 of 1016
4. The following screen displays.
5. Click on the desired cell to modify a configurable item. Depending on the type
of configurable item, shortcut menu displays to allow you to modify the value.
6. Click OK button. The values are saved to the configurable items. When the
Regulator or Monitor is selected in the toolbox outline view, a list of the
configurable items and their values display in the summary view.
712 of 1016
Trend Recorder
After the verification process, Position and Current signals are trended. The Position
signals are attached to Reg1_Fdbk, Reg2_Fdbk, Reg3_Fdbk and Reg4_Fdbk. The
Current signals are attached to ServoOutput1, ServoOutput2, ServoOutput3, and
ServoOutput4.
The Trend Recorder is started with the signals ready for trending. After a time delay,
Trending samples are taken
a message is sent to the board to begin the trend. The time scale, x-axis for the
at 32 ms.
command Verify Position, is 10 seconds. The time scale, x-axis for the command
Verify Current, is 30 seconds. The magnitude, y-axis, for Position is defined in
current Regulator mode in the Outline View as follows:
The minimum Position value

is MinPOSValue minus 10.
The maximum Position value

is MaxPOSValue plus 10.
VSCA Serial Interface Board

The VSCA board is different from other I/O boards in that it consists of six
configurable serial ports. The VSCA is never a TMR board. Each port can be
configured as a pressure transducer, electric valve drive, or Modbus master interface.
When a VSCA board in

inserted in the Outline
View, port items display
under the DSCB terminal
board item.
713 of 1016
To specify the interface for a particular port
From the Outline View, right-click the port name, then select Insert First
from the shortcut menu.
The following dialog displays.
Because of the unique The pressure transducer and electric drive interfaces have fixed interfaces once they
communications requirements are inserted for a port. The points and software configurations are modified using the
of the pressure transducer same dialog boxes as the fixed interface I/O boards described earlier in this chapter.
interface, it is only available
on ports 1 and 2.
Configurable Items
The Modbus master interface (Modbus Port) can have any number of stations, pages,
and points inserted.
To insert a station
From the Outline View, right-click the item Modbus Stations and select Insert
First from the shortcut menu. The item Station1 displays in the Outline View.
The pages and points of a station can be added by importing a special .csv file that
defines the points for that station. Importing a .csv file into a station with existing
points creates new points provided that the address software config does not conflict
with the address of an existing point on a particular page.
714 of 1016
The item, Station 1, displays
in the Outline View.
Four types of pages can be inserted

in each station. These correspond to
the four register types.
Insert a register page by

right-clicking on Modbus
Pages. Select Insert First.
The Select Insertable Hardware Module dialog box displays.
The page is inserted and displays in the Outline View.
715 of 1016
Right-mouse click
and select Insert
First.
The Modify Point Connection dialog box displays.
Enter the name of the

signal or click Browse…
to search for an
available signal.
Select the data type for

the scaled point in the
controller, either Bool,
LInt or Float.
Select the direction of
the point, either Read or
Write.
Note Omitting the signal connection displays a spare in the Outline View although
to avoid using Modbus bandwidth the UpdateRate software config should be set to
Never.
Shortcut Menu Commands

The following commands are available for VSCA configurable items.
Modbus points can be
sorted according to
address. The VSCA
firmware can then group
different points into the
same message to make
the link usage more
efficient.
Import points (.csv
file) to Station or
Modbus Pages.
Export the pages
and points of a
station.
716 of 1016
Sequence of Events
There are a number of Mark VI boards capable of using sequence of events. The
example below is a VCCC board with contact inputs, which have events defined.
If a contact input has an event defined and this input is enabled through its software
configuration, a message displays on the defined CIMPLICITY screen. An soe.dat
file is created with the Build command and placed on the user's hard drive. This file
has the associations between the sequence of event drop number for this point and its
signal name. It allows the event transition to display correctly on the associated HMI.
Tip Make sure that all devices are kept in separate folders. This soe.dat file will
always be generated, regardless of the device name. For example, if there is a
G1.m6b and a G2.m6b in the same folder, they will both generate the soe.dat file.
The last one to write out the file will be the last available sequence information. So
to get unique device sequence-of-event information, make sure that all devices are in
separate folders.
717 of 1016
EGD Interface
Addresses of the points on the Ethernet Global Data (EGD) is a control network, as well as a protocol for the Mark
exchanges are made known to VI controller. EGD uses Ethernet as the physical and data-link layer of the network.
other controllers through the It can send directed or broadcast messages. Devices share data through EGD
SDB. exchanges (pages).
Note Exchange is a CIMPLICITY term, which means the same as the term page in
the toolbox. Exchanges provide a way to share live signals (variables) over Ethernet.
To insert the EGD Interface network

1. From the Outline View, click Hardware and I/O Definitions.
2. From the File menu, select Insert First. The New I/O or Network Interface
3. Select EGD Interface and click OK. The network is inserted into the Outline
View as shown below.
Ethernet Global Data

(EGD) network
The network is assigned a default name (EGD1), number (0) and Producer ID. To
edit the settings, refer to the next section, Edit EGD.
Edit EGD
The dialog box displays a default name (EGD1), number (0) and Producer ID.

Interface to be edited. A
default name is generated
when the EGD is inserted.
The number is found in the

SDB. If set to zero, this is
assigned when it is put into
the database.
The default IP address is

1.1.1.1. A unique address
or name can be entered.
Double-click the device
name to refer to the IP
address in the Device
Properties dialog box.
Enter the .tre file to export.
Enter a note to describe Click OK. The network

the network. The note can displays un the Outline
be up to 50 characters. View under the
Hardware and I/O
Definitions item.
718 of 1016
EGD Exchanges
Exchanges (pages) provide a way to share live signals over EGD. These exchanges
are periodically broadcast by the owner using EGD shared RAM update messages,
known as feedback messages. The exchange broadcasts every 320 milliseconds by
default, but you can set the interval to any value not less than 10 milliseconds. An
exchange can be a maximum of 1400 bytes long and is addressed on byte
boundaries. Boolean points are packed eight to a byte, and the bit number that
describes which one ranges from zero to seven. A controller can own up to 16
exchanges, although the limit is five by convention.
Note Once the EGD network is inserted under Hardware and I/O Definitions in the
Outline View, the EGD exchanges must be inserted.
To insert an exchange
1. From the Outline View, click the EGD network name to highlight it.
Or click the right-mouse 2. From the Edit menu, select Insert First. The item Exch1 is inserted under the
button and select Insert First. item, EGD network. The default name of the exchange is Exch# (where # is the
number of exchanges owned by this controller).
Note Once an exchange exists, another item can be inserted by following the same
steps, but select Insert Next.
These exchanges are sometimes referred to as internal exchanges in the toolbox

controller. Exchanges owned by other controllers are called external exchanges.
Internal exchanges can be modified using the Internal Exchange Settings dialog
box.
To modify an internal exchange
1. Click a exchange to highlight it.
Or double-click the exchange. 2. From the Edit menu, select Modify. The Internal Exchange Settings
dialog box displays (refer to the next section, Internal Exchange Settings).
719 of 1016
Internal Exchange Settings
This data field is used
by ToolboxST™.
Enter a name ( up to five
characters).
Enter a number (1 to 255) or
enter zero for the device to be
posted to the SDB and
assigned the next available
number.
Enter the frame period for the
EGD exchange. Each Frame
Period is equivalent to 40
ms. The Exchange period
determines the time between
EGD feedback transmissions
on Ethernet. The default
Frame Period is 8 (320 ms)
Check this box so this
exchange to receive signals
that are flagged as network
signals when the command
Put to database is used.
Select the Broadcast or

Directed. Broadcast allows
signals to be sent on multiple
Ethernet (if available).
Directed specifies a
destination address for the
exchange.
% Allocated is the
percentage of exchange
memory that is allocated.
% Free is the percentage of
exchange memory remaining
CfigSig is the Configuration
Signature. It provides the
current version number of the
controller and notifies users
of modifications to the
exchange, which are Click to keep the Click to unlock all Click to reclaim all
monitored by other memory location of signals and allow the lost memory.
controllers in the system. The points with signals on memory location of
number is checked for the exchange. points that have
consistency between the signals to change.
exchange being broadcast by
the owner and the user’s
copy.
Only one internal exchange can be checked to Receive Network Signals. When one
exchange is checked, any previously selected exchange is automatically cleared.
When the command, Put to database is performed, any signals flagged to be
network signal (see Chapter 3, Configuration, Signal Definitions, Define Signal
Definition) are automatically connected to this EGD Exchange. This happens only
for signals that are not already connected. There is also a batch command to
Instance Network Signals, which does the same thing as the command, Put to
database.
720 of 1016
For another way to add network signals to an exchange, from the Outline View,
right-click an exchange and select Add Network Signals. This adds all signals
flagged as network signals (but not already connected) to the Exchange.
Whenever a point is deleted from an exchange (in the Outline View), that space is
not reclaimed. All controllers referencing that exchange must update from the
database. This loss of memory can be seen in the % Loss field of the Internal
Exchange Settings dialog box. To reclaim this lost space, compress the exchange.
The following Warning displays.
721 of 1016
External Exchanges
The External Exchange data displays in the Summary View (shown below). This
data includes the signal name, a list of the points on that exchange, data type, health,
and so on. When the controller is monitored online, the second column, Value,
displays the live data value for the point on that line.
Note External Exchanges cannot be modified. A message box displays stating that
you are not the owner.
EGD external exchanges have two built-in diagnostic mechanisms: exchange healthy
and link presence. The link presence for a controller is True whenever messages are
being received from that controller. When the exchange healthy for a controller is
True, feedback messages are being received from that controller. When the health of
a variable (signal) connected exclusively to an EGD point is used in blockware, the
exchange healthy is actually the value used.
When the controller gets information from the database, exchange zero is inserted
into the network and called LINK. This exchange holds a list of signals called link
presence bits, which are set whenever an EGD message is received from a controller.
If no messages arrive for a controller in 1.28 seconds, the value of the link presence
signal goes to zero. These signals can be used in blockware like any other signal. The
form of the name is NET\DEV\ExchangeNameHEALTHY where NET is the name of
the network, DEV is the name of the controller, and ExchangeName is the name of
the external exchange.
722 of 1016
EGD Points
A point can only be inserted EGD exchanges are made up of points, which are associated with controller signals.
into an internal exchange. Each point corresponds to a complete signal, regardless of the length or amount of
memory that the point occupies in the exchange. The name has the form
EGD.BYTE.BIT, where BYTE is the eight-bit byte offset into the exchange, and BIT
is the bit number, which ranges from zero–seven (seven is the most significant bit).
Note New EGD points added to an existing EGD exchange can be downloaded
online. If points are deleted from an exchange an offline download is required
To insert and modify a point

1. From the Outline View, click the EGD exchange to highlight it.
Or use the shortcut keys, Shift 2. From the Edit menu, select Insert First. The EGD Point Settings dialog
+ Insert box displays. It is used to insert and edit EGD points.
Enter the Name of the signal associated with this point. This
Select the Data Type from name must be provided to create a point. Click Browse... to
a drop-down list of data select the signal using the Signal Selector dialog box.
types supported by the
EGD. These data types
are different from the basic
controller data types and
are listed below.
Select Lock to set the
work offset and bit
number. (Also use the
Lock All Signals and
Unlock All Signals
command in the Internal
Exchange Settings
dialog box).
Address is assigned by
the toolbox to a point that
is Byte.BIT.
Enter Write for the

controller to produce
information or Read to
receive information.
CIMPLICITY Resource
allows you to mark this
particular signal to be
moved into the
CIMPLICITY database
using the SDB Exchange. The Health Address is Edit Signal displays the Signal Edit dialog
provided for signals that box. The button is only active when the point is
need health, such as being inserted.
DLAN+ and Genius.
Feedback Data Types

BOOL - 1-bit value DWORD - Long (32-bits) integer
WORD - 16-bit integer REAL - 32-bit floating point number
723 of 1016
Tip EGD points can be created in the Outline View by using drag-and-drop to
insert a signal definition in the exchange item. This point data type is compatible
with the data type of the signal being dropped. The direction is assumed to be a
feedback. Modify the point data type using the EGD Point Settings dialog box.
EGD Points in the Summary View

The Summary View displays a diagram of the point and its connection to a scale
and signal. Each connection can be edited from the Summary View.
To edit the point, signal, or scale
1. From the Outline View, click the point. A diagram of the point and its
connection to a scale and signal display in the Summary View.
2. From the Summary View, double-click the actual point, signal, or scale. The
appropriate Edit dialog box displays.
When the controller is being monitored online, the Summary View displays the
live data value for the point and the signal connected to the point, as shown in the
screen below. Normally these two values should be equal. If they are not, make sure
the task that uses that signal is enabled. At least one task using that signal must be
enabled for an I/O transfer to run and copy the point value into the signal value, or
vice versa.
To modify/force a point or signal value
Or click . 1. From the Device menu, select Online.

2. From the Outline View, click the point. A diagram of the point and its
connection to a scale and signal display in the Summary View.
3. From the Summary View, double-click the actual point value or signal value.
The appropriate Edit dialog box displays.
724 of 1016
725 of 1016
Main Board
Right-click the controller The item Main Board currently holds the non-volatile memory. Inserting the Main
name and select Modify. Board depends on the type of controller selected in the Properties dialog box, such
From the tab General, select as the SD200UCPB, SD215UCV_, or DS214ACL_.
Platform and the desired
controller.
To insert Main Board
1. From the Outline View, click Hardware and I/O Definitions.
Or click the right-mouse 2. From the Edit menu, select Insert First. The New I/O or Network
button and select Insert First. Interface dialog box displays.
3. Select Main Board and click OK.
Non-volatile Random-Access Memory

Non-volatile random-access memory (NOVRAM) is battery-backed memory that
holds its values even when the controller loses power. This is used in the controller
to save values that change over time and need to be maintained through a power loss.
Upon starting the controller, the initial values specified in Pcode are written to the
signal’s RAM locations, followed by the values held in NOVRAM. The NOVRAM
values are not transferred into the signals when the NOVRAM major revision
changes (meaning the location of existing signals in NOVRAM changes) or for
points that were just added. Once the controller is running, signals associated with
the NOVRAM points are written to the battery-backed memory at the end of the task
in which the signals are used. When NOVRAM is added to a controller for the first
time, it is necessary to download the Pcode to permanent storage and reboot the
controller since the controller needs to add resources that it can only do at startup.
In the controller, NOVRAM is modeled as I/O. This means that each NOVRAM
location corresponds to a point. The NOVRAM signals are written as part of I/O
transfers after the execution of the tasks where those signals are used.
726 of 1016
Insert/Modify NOVRAM
To insert NOVRAM in a Main Board module
1. From the Outline View, click Main Board.
Or use the shortcut keys, 2. From the Edit menu, select Insert First. Or, click the right-mouse button and
Shift + Insert. select Insert First. The New I/O or Network Interface dialog box displays.
3. Select Nonvolatile RAM (NOVRAM) and click OK.
The list of signals and their corresponding NOVRAM locations must be static for the
controller to restore values to the proper signals. Therefore, never move NOVRAM
points. The NOVRAM Edit dialog box displays statistics on memory space. It also
displays the option to sort the page order and the command to compress the memory
space, if required.
727 of 1016
To modify NOVRAM
Or double-click the item 1. In the Outline View, click NOVRAM.
NOVRAM.
2. From the Edit menu, select Modify. The NOVRAM Edit dialog box displays.
Statistics display data on memory space as follows:

Version is a number incremented by the toolbox whenever a change takes place, such as
1.0. The first number is the major number and the second is the minor number.
% Allocated displays the amount of memory used.
% Free displays the amount of NOVRAM that can still be used.
% Lost displays the amount of NOVRAM that was lost because of the deletion of the points
that are not reclaimed so that the mapping of points is deterministic.
Page Sort Order rearranges

the list of NOVRAM points in
the Outline and Summary
Views, so that it is sorted
alphabetically by the signal
name or the point name. This
does not affect the order of
points in the NOVRAM.
Compress Page recovers unused

memory in NOVRAM that
accumulates when points are
removed without compressing.
This command increases the
major version number.
Note Only compress the page if a large % space is lost and not enough % space is
free in which to add the required data.
Modifications to the NOVRAM are shown in the Version number, such as 1.0. The
major number (1) increases whenever the page is compressed. The minor number (0)
increases when a point is added or deleted. This version number is used by the
runtime to know when to initialize the signal from NOVRAM when the controller
starts up. If the major number changes, nothing is transferred to local memory when
the controller starts. If the minor number changes, only the points that have not
changed are transferred to local memory.
728 of 1016
NOVRAM Points
When NOVRAM points are inserted, the numeric value of the highest point number
is saved and used to assign the next point number/name. If a NOVRAM point is
deleted, the memory location of the point is not reclaimed until the Compress
Page command is executed.
To insert a NOVRAM point
Or use the shortcut keys, 1. From the Outline View, click NOVRAM.
Shift + Insert
Insert another item by select Insert First. The NOVRAM Point Edit dialog box displays.
selecting Insert Next.
Enter the point to edit.
Select Input or Output.
Data Type is the named

type of the I/O point.
Enter the name of the signal related to this View the signal note to make sure
point. Click Browse... to select a signal. this is the correct signal.
Sometimes a NOVRAM point is also mapped to another input point from a network.
When the controller starts up, the signal is restored to the value stored in NOVRAM.
In addition, the input point is given the same restored value, so that the first I/O
transfer from the point to the signal cannot give it meaningless values.
Signals that are forced in the controller are saved in NOVRAM and are not lost when
the controller is restarted. These force values are not restored if the major revision of
the application code changes because it is possible that the addresses of the signals
may have all changed. The NOVRAM is divided such that using all of the 512 points
available should not infringe on the memory available for forced points.
NOVRAM points can be added to the list of points using drag-and-drop. Drag the
signal onto the item NOVRAM in the Outline View. The point name and data types
are assigned automatically based on the signal that is dragged.
729 of 1016
Register Network
Register network interfaces allow the controller to communicate with other devices
that do not use EGD over Ethernet or Status_S over the DLAN+, such as the
CIMPLICITY Human Machine Interface (HMI) and others, which hold their internal
data in registers.
Data is modeled as a set of register spaces that are either words or bits. Each register
space is given a type name, such as %M (bits) or %R (words). A number identifies
Pages can be created and
registers within a space. The controller interfaces with devices using a form of
instanced in the controller
shared memory that is updated over a network. The shared memory is referred to as
and put into the SDB.
register pages. A register page corresponds to part or all of one register space. The
HMI reads or writes registers defined by the controller. The %M and %R spaces
provide the only general purpose register facilities for bits and 16-bit words,
respectively.
The toolbox generates the required mapping for controller signals into the register
pages. The toolbox can also generate appropriate text or binary files to configure
other controllers to match up with the register page(s) images in the controller. This
section describes the following register networks that provide an interface to Mark
VI controllers:
• Ethernet Service Request Transfer Protocol (SRTP)
• Serial/Ethernet Modbus™
• A-B Data Highway Plus (DH+)
• Ethernet Modbus (Legacy)
• Custom Register Network
730 of 1016
Serial/Ethernet Modbus
Serial/Ethernet Modbus interface provides communication between the Mark VI
controller and other non-GE controllers using the Serial RS-232C connection,
RS-485 is used for multiple
Ethernet or both. Communication with the remote controller is implemented using
controllers.
register pages. The register maps may be independent or shared (overlapping).
To insert a Serial Modbus
1. Click the item Hardware and I/O Definitions.
Or click the right-mouse 2. From the Edit menu, select Insert First. The New I/O or Network
button and select Insert First. Interface dialog box displays.
Note The Mark VI is always a Modbus slave unless it is using the VSCA.
Select Serial/Ethernet
Modbus and click OK.
731 of 1016
Serial Modbus Settings
Baud Rate, Parity, Data Bits , and Stop
Bits define the communication settings for
Enter the communication the network and must be set to match all
Mode for the network. The other controllers on the network (check this
default mode is Binary. dialog box on other controllers).
Identifies the Serial Modbus

network in the controller.
Enter up to five characters.
Enter the communication

Port used to talk to the
external controller (COM1 is
not available).
Enter the network address
of the controller. It must be
a unique number between 1
and 255.
Select the desired
physical Modbus
interface. Shared pages
can receive commands
from either the Serial or
Ethernet interfaces.
Input Enable Signal:

Inputs to this controller can
be enabled and disabled
programatically by
specifying a Boolean signal
here and manipulating it
with blockware. Enter a note to describe this This option is only available in
modbus interface. Expert Mode and at Privilege Level
4. It limits the number of
commands processed per second.
<name> Serial Modbus
Interface. Select Insert
First.
Pg1 is inserted.
To insert points, right-mouse

click on Pg1 and select
Insert First.
Note To modify pages and points, refer to the sections, Modify Page Settings and
Modify Point Settings at the end of this chapter.
732 of 1016
The named DH+ Interface is inserted.
Right-mouse click
A-B Data Highway
Plus Interface. Select Insert
First.
Pg1 is inserted.
To insert points, right-mouse

click on Pg1 and select
Insert First.
Note To modify the pages and points, refer to the sections Modify Page Settings and
Ethernet Modbus Settings
Enter the Network Name

using up to five characters.
The name must begin with
a letter of the alphabet.
Enter a Note to describe

the interface.
Click OK. The <name>

Ethernet Modbus Interface
is inserted.
Ethernet Modbus
Interface. Select Insert
First.
.
Pg1 is inserted.
To insert points, right-

mouse click Pg1 and
select Insert First.
.
Note To modify the pages and points, refer to the sections Modify Page Settings and
733 of 1016
Chapter 11 Signals and the Database
Introduction
This chapter defines signals and their sources. It also defines the topological
information in the database. The database is a collection of signals, scales, and other
topological information, which all devices in a system share for communication.
Devices place information into the database with the command Put Into Database
and obtain information with the command Get From Database. There are two
databases: System and Unified System.
System Database (SDB) is a Windows-based client/server database, which uses .dbf
files for storing data.
Unified System Database (USDB) is an Informix® SQL relational client/server
database, which runs on a LynxOs-based PC.
Section Page
Signal Concepts......................................................................................................11-2
SDB ......................................................................................................................11-12
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 11 Signals and the Database • 11-1
734 of 1016
Signal Concepts
Signals are the placeholders for memory locations in the toolbox’s different
platforms. Signals also connect both the pins in blockware and blockware to the
points in hardware. They are created by signal definitions and pins as part of
blockware. Every block, macro, or module that is inserted has a signal associated
with its pins.
For more information, refer Signals exist in the database only when they are mapped (connected) to a network
to the section, SDB. I/O point and the device configuration command, Put Into Database, is used.
When a signal is put into the database, it is made available to other devices to get.
Signals can be created by:
• Inserting a signal definition
• Sending the Get From Database command
• Inserting an item of blockware in a controller
Drive Signals
Signals in the AcDcEx2000 are owned by variables (VARs). The number and types
of signals depend on the type of AcDcEx2000 being configured. The signal tokens
are fixed, since the VARs are created when the device is created and exist as long as
the device exists.
Controller Signals
In the toolbox Outline View, controller signal definitions are inserted under the
item Signal Definitions (under the items Functions or Macro and Module Libraries).
Signal definitions are also placed under the item System Data, under the items
External Signal Definition and Undefined Signal Definition, using the command,
Get From Database. Also, in the item System Data, a list of LINK_OK signals are
placed under the item Network Signal Definitions.
11-2 • Chapter 11 Signals and the Database GEH-6403L Toolbox for a Mark VI Turbine Controller
735 of 1016
Signal definitions can be
inserted under the items
System Data, Macro and
Module Libraries,
Functions.
736 of 1016
Macro Pin vs. Module Pin
A Mark VI Controller signal is defined in a macro pin or module pin before
instancing. The following table provides guidelines on how and when to define a pin.
When to use a macro pin: Guidelines for Macro Definition Pin

For any signal that needs to be accessed outside this Name is limited to seven characters.
macro.
Can attach a 50-character note.
For signals that will help with debugging, especially if it will
When a macro is instanced, the macro’s pin names are
avoid having to look inside the macro.
combined with the instance number to automatically make
the signal name.
Use a module pin when: Guidelines for Module Definition Pin
Signal is used in more than one task. Name is limited to 12 characters.
Signal is a Status_S or I/O signal (do not use fully qualified Can attach a 50-character note.
signal name, such as R1/R2/R3/name).
Can attach a scale factor to the signal.
One or more tasks in the module need to be event-started
Inserting a module pin makes it obvious which signals are
on the rising edge of this signal.
inputs/outputs.
Signal is not used elsewhere, but needs a custom signal
The pins on blocks and macros in the module definition can
description. (A custom signal description is needed for any
be written to point to this module pin, no matter what region
signal that might end up as a permissive that could be
prefixes were specified when the module was instanced.
diagnosed, such as an input to a BENG or a BENG D
block).
Signal/Pin Connection
Signals are created by signal definitions or for pins as part of blockware. Every
block, macro, or module that is inserted has a signal associated with its pins. When a
signal is created:
• A block pin or instanced macro pin is automatically named based on the pin
name and block number. They are referenced from pins on other blocks using
# :pin_name (# is the block number: name of pin). There is no signal description
associated with this signal. This signal can only be used within the same level of
code. If the block is in a macro, it can only be used within that macro and if the
block is in a task, it can only be used within that task.
• A module instanced pin or inline module pin are global to the device. They can
be connected to a Status_S variable or an I/O point. The signal name is in the
form R1\R2\R3\module_pin_name, where R1\R2\R3 was specified when the
module was instanced.
• A signal definition is also global to the device. It can be connected to a Status_S
variable or an I/O point. The signal name is in the form R1\R2\R3\signal_name.
A scale factor can be attached to the signal.
737 of 1016
Pins are connected to other pins or signals to make blockware function in a
prescribed way. A connection is generally indicated in the Outline View by a name
in parentheses following the pin name, such as:
For more information, see Pin connections display in a hierarchy that can be seen in the Finder under the tab
Chapter 4, Finder. Signal/Variable Usage, as shown.
The hierarchy reflects the way pins and signals are connected. Each item in the list
references the item in the level above it. A signal hierarchy, excluding I/O points, is
represented in Pcode by a single address token. This means that only one initial value
or scale is used and the top level is the source of such information.
It is important to recognize the directional nature of connections to obtain the correct
data type. Pins with a collection data type, such as Analog or Simple, must reference
For a list of data types, refer
pins with non-collection data types. Referencing incorrectly causes a validation
to Chapter 2, Using the
error. Correct the error by reversing the direction of the connection or by creating a
Toolbox.
pin and referencing that pin.
738 of 1016
Attaching Signals to I/O
I/O points found under the Hardware and I/O Definitions item can be used in
blockware only when they are connected to signals. The Summary View below
displays an example of the connected signal and scale.
The I/O mapper task is a program that transfers inputs to outputs in the controller.
The toolbox creates I/O transfer Pcode records for any signal connected to both input
and output points. Similar records are also created for tasks that have signals with
I/O points connected to block pins.
More than one point can be connected to a signal. These multiple connections direct
the mapper task to move inputs to outputs using I/O transfers, although the signal is
not used in any task. To have more than one input point results in a validation error.
However, it is possible to connect multiple output points to this signal, along with a
single input point.
For more information, see the Scale factors are associated with signals and not points, so that all points connected
sections, Status_S Points and to a particular signal will all use the same scale factor. When the input transfer
Genius Block and Field occurs, the raw counts are converted to engineering units used by the blockware.
Control Module Points. When the output transfer occurs, the engineering units are converted to raw counts.
Note Because the I/O mapper is not synchronized with the scheduling frame, Mark
VI I/O should not be configured for transfer.
739 of 1016
Special Signal Properties
Properties of certain signals can be accessed in blockware and used as part of the
normal logic by preceding the name of the pin or signal, as follows:
• Precede the inverse of a Boolean signal with a tilde symbol ~.
• Precede the health of any signal connected to an I/O point, (Boolean value) with
the number symbol #.
A signal’s health status indicates whether the associated point is functioning as
intended. The value of the signal health varies depending on the points to which the
signal is connected. The following table shows what information goes into the value
of the health. The health of signals not connected to I/O points is TRUE. Generally,
signals connected to output points are always healthy.
Input I/O Type # Health is…

Genius No Genius point or block faults and block present and GENI_ON
Field I/O No point, module, or block faults and block present
Register I/O I/O semaphore, page, and heartbeat healthy for register I/O types depending on
required client functionality
Internal Status_S Input page healthy
External Status_S Input page healthy and signal health as filled out by the I/O mapper task if the
source device signal is connected to both an input and output
Signals connected to Genius points also have an extended health  with the
symbols ##. The extended health of a point is a 32-bit mapped value used to extract
more specific health information on a given I/O point. The meaning of the bits differ
according to the I/O type. The table below defines different I/O types.
I/O Type Byte 3 (MSB) Byte 2 Byte 1 Byte 0 (LSB)
GENIUS Bit0 = GENI_ON Bit0 = block present *Block fault code *Circuit fault
code
Field I/O Bit0 = GENI_ON Bit0 = block present *Block fault code *Circuit fault
code
Bits 4-7: module fault code,
reset same as Genius
Register I/O Not used Bit0 = I/O semaphore Bit0 = heartbeat Bit 0 = page
health = 1 health = 1 health = 1
NOVRAM Byte 2 error count Byte 1 error count Byte 0 error Bit 0 = point
count health = 1
* The meaning of the Genius Block and circuit fault codes can be obtained from the Genius I/O System and
Communications, User’s Manual, GEK-90486F-1.
740 of 1016
Scale Definitions
A scale can be attached to either a signal definition or module pin definition. Any
signal can be mapped to a network page owned by the device. When the command
Put Into Database is used, all the signals and any scales attached are put into the
SDB. The scale is now available to other devices using the command Get From
Database. These scale definitions display under the System Data/External Scale
Definitions items, as shown below:
741 of 1016
Signal Selector
The Signal Selector dialog box allows you to select a signal for various toolbox
functions.
¾ To select a signal
1. In the Outline View, select Functions, Signal Definition, then right-click the
signal name and select Modify. The Edit Signal definition dialog box
displays.
2. Click the Browse... button to display the Signal Selector dialog box shown
below.
Double-click on the
region to select
signals from.
A list of available
signals displays.
Double-click to
select the desired
signal.
A description of the
selected signal
displays here.
Select the type of signal to display Select either Local or Network

in the list above, such as All Types Items, when available. The default
or Boolean. is Local.
3. Click the SDB Browse button. The SDB Signal Browser dialog box displays.
742 of 1016
In the example above, a specific Network, a Device, and a Data Type are selected
from drop-down menus to display just those selected signals.
Another method of selecting a desired filter region is to click the Browse Region
button. The Select a Region dialog box displays.
743 of 1016
4. Click the Attributes button on the SDB Signal Browser
dialog box to define the columns displayed in the list box in the Select Signal
Fields to View dialog box.
The Add All, Add, Remove, and Remove All buttons move signals from the left
list box to the right.
744 of 1016
SDB
For more information, refer The SDB is a client/server Windows-based database that uses .dbf files for storing
to GEI-100506. data. Only the device that owns the topology and signal data can put that information
into the SDB. There is no separate import program.
Select the database from the Options menu, Settings option, and Database tab.
The SDB:
• Can be created from the toolbox as long as the SDB server is running.
• Is specified by a path-qualified sub-directory where the database is stored. The
SDB name must include a drive letter.
I/O points and internal signals that can be put into the database are stored in the
signal table.
Put Into and Get From Database

The command Put Into Database provides information for other devices in the
system. The command Get From Database allows the devices to obtain this
information. All devices put the same information into the database depending on the
configuration (except the System Device). The following data can be put into the
database:
• Device information (topology data), such as device name, type, and number.
• Network information (topology data), such as the networks connected to the
device, pages associated with each network connection, and drop numbers when
applicable.
• Signals owned by the device and mapped to pages owned by the device.
• Scales owned by the device, which are attached to signals that get put into the
database.
745 of 1016
Put Into Database
The Put Into Database command can be full or incremental. By selecting the Full
option, the old signals of a device are deleted from the database and replaced by the
signals that the device presently owns. This is also true for network connections and
pages owned by a device.
If you select the Incremental option, signals are added that have been created since
the last Put Into Database command. All previous signals are still in the database
(even if they were removed from the device configuration). Incremental is especially
useful for devices that have thousands of signals and it is necessary to add one or two
new signals with out taking the time to re-put everything.
When the command Put Into Database is used, certain fields that have a value of
0 are automatically assigned a new value by the database. The numbers that the
database assigns are used in the device configuration. This includes data such as:
• Device number (must start at 256 or database reassigns number)
• Drop number (DLAN+)
• Page number (DLAN+)
¾ To put information into the database
1. From the Device menu, select Put Into Database. Select Full to include all
information or Incremental for specific information.
The toolbox displays the message box shown below, indicating which server and
database will be used. If any of this information is incorrect, click No to cancel the
operation.
2. Click Yes to continue the command, Put Into Database. The Error Log
View displays the present state and status of the command.
746 of 1016
Get From Database
The get process also searches for undefined signals in the database. Then, the
database server returns signal attributes and the signals are assigned owners. The
owners are the external devices on the same network as the device performing the
get. The signal attributes returned by the database are used for building the device’s
Pcode. The command, Get From Database also allows the device to obtain the
actual value of the signal from the network interface during runtime.
There are two types of get: full and incremental.
• In the Full command, the list of External Signal Definitions under the item
System Data are ignored. After the command is completed, this list is rebuilt,
and the point list for external pages under the item I/O Display Definitions is
rebuilt.
• The Incremental command applies only to signals. When getting from the
database, the toolbox creates a list of signals used by the device, but not owned
by the device. Signals in the item External Signal Definition are not bound, but
the new bound signals are added to the item and to the external device’s pages.
A warning is issued in the An incremental get can be faster then a full get, especially if a device is using
Error Log View when an thousands of signals. However, the incremental will not receive any updates to
incremental get is performed. external signal data that existed before and may have changed.
¾ To get information from database
1. From the Device menu, select Get From Database. Select Full to include all
information or Incremental for specific information.
One of the following message boxes, displays:
2. Click OK to continue the command. Click Cancel to end process

The signals are displayed under the item External Signal Definitions.
747 of 1016
Tip ª During the command Get From Database, the toolbox creates a list of all
signals that are used and not owned by the device. It then attempts to find them in the
database. The signals that are found are placed under System Data/External Signal
Definitions. They are also shown as points in the device’s external page under
Hardware and I/O Definitions.
If signals are not found in the database, a message box displays to create Undefined
Signals Definitions. If undefined signals are created, they are displayed under the
item UnDefined Signal Definitions, as shown below.
Signal found in the database

and not owned by the device
are compiled here
Signal not found in the

database are compiled here
748 of 1016
Scale Results
When a scale is associated with a signal, the scale name and information are included
with the signal. Global scale definitions do not change as often as signal usage. So,
after getting topology and signals, a dialog box displays to Get Scales. Click No and
receive a warning that scales were not received and previously defined external
scales were not touched. Click Yes and the item Externally Defined Scales is
replaced with all the scales defined in the database.
Note Get scales returns all the scales in the SDB, including those owned by this
device. However, these scales are ignored by the device since it is the owner.
Global Enumerations
System Configuration can define Enumeration Type definitions, which are global.
When System Configuration performs a Put into Database command, these
enumerations are stored in the SDB. Any device that performs a Get from
Database command will get these global enumerations, along with signals, scales,
and other data. These global enumerations are stored as shown below.
These standard
type definitions
are used for
Status_S.
These five type

definitions are
global.
These global enumerations can be used as data types for signals. It is only necessary
to define the enumeration once to use it in any number of devices.
749 of 1016
Chapter 12 Turbine Historian
Configuration
Introduction
Once collected, the data can The Turbine Historian Configuration device is used to generate configuration files,
be accessed either by GE data configure the historical data collection, and implement the configuration for the
analysis applications or by Mark VI, PI-based, Turbine Historian.
PI-ProcessBook.
This device configures the Turbine Historian to collect the following signal data and
distribute over the Unit Data Highway (UDH).
• Mark VI, Ethernet Global Data (EGD)
• Alarm and Event
• Sequence Of Event (SOE)
• Hold
Section Page
Working with Files and Menus ..............................................................................12-2

Configuration..........................................................................................................12-4
Templates ...............................................................................................................12-6
Troubleshooting....................................................................................................12-15
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 12 Turbine Historian Configuration • 12-1
750 of 1016
Working with Files and Menus
The Turbine Historian is configured, using one of three types of configuration files:
For more information, refer • Turbine Historian binary (.thb) file is the binary file form of the configuration
to Turbine Historian System created through the Save command. The configuration can also be exported to a
Guide, GEH-6422. projected file.
• Project (.prj) file is a text file that holds configuration information.
• Tree files (.tre) are text files that contain configuration information.
Menu Commands
Turbine Historian Configuration menus, such as File, Edit, and View, are managed
just as other toolbox and Windows menu commands.
Device Menu
The Device menu contains the following commands:
Validate checks the configuration for errors.

Build is disabled under Build is used to produce the Turbine Historian configuration files and to configure
specific conditions. Refer to the PI database with the points defined in each collection.
the Troubleshooting section.
Put In Database verifies that the device properties are correct and inserts the
device into the database. Configuration and the defined network connections are
inserted into the SDB Device and Topology tables. This data is then used when the
Turbine Historian Configuration creates text files during the Build command.
Get From Database retrieves signal information from the database. Each time that
a signal or set of signals is added to a Collection, you must use this command.
Restart Services may not be Restart Services stops and then starts the HST and ICN Services. This enables
enabled under specific any changes to the configuration.
conditions. Refer to the
Troubleshooting section.
Note A Build requires that F:\config.dat be defined, PI services installed and

running, and the HST service installed.
12-2 • Chapter 12 Turbine Historian Configuration GEH-6403L Toolbox for a Mark VI Turbine Controller
751 of 1016
Build Command
The Build command:
• Produces the unit-specific files alarm.dat, event.dat, hold.dat, soe.dat, and
unit_egd.dat for the HST runtime system
• Produces the historian-specific unit files egd_push.u and piconfig.u
• Runs the utility program ddbuild2 to create the unit-specific files longname.dat
and unitdata.dat for the HST runtime system
• Runs the utility program hstdbs to create the system level egd_push.dat and
piconfig.dif files, and for non-Mark VI units, create the system level
pi_push.dat file
• Produces the file enetalm.dat file for the HST runtime alarm subsystem
• Produces the EGD icn.ini file
• Modifies the HOSTS file
• Runs the utility program piconfig to populate the PI database
The following files are generated by the Build for each Mark VI unit defined in
F:\config.dat.
• F:\UNITn\ALARM.dat
• F:\UNITn\EVENT.dat
• F:\UNITn\HOLD.dat
• F:\UNITn\LONGNAME.dat
• F:\UNITn\SOE.dat
• F:\UNITn\UNIT_EGD.dat
• F:\UNITn\UNITDATA.dat
• F:\UNITn\EGD_PUSH.u
• F:\UNITn\PICONFIG.u
The following list of files is generated by the Build for the Turbine Historian site
configuration.
• F:\EGD_PUSH.dat
• F:\PI_PUSH.dat (if non-Mark VI units are correctly defined)
• F:\PICONFIG.dif
• F:\ENETALM.dat
• %WINDIR%\ICN.ini (merge of SDB data with F:\ICN_EX.ini, if it exists)
• %WINDIR%\SYSTEM32\DRIVERS\ETC\HOSTS (intelligent merge of SDB
data and existing HOSTS file)
752 of 1016
Configuration
This section defines the four major items for configuring the Turbine Historian.
• Create
• Templates
• Collections
• Signals
Create Configuration
¾ To create a configuration
1. From the File menu, select New. The New dialog box displays.
2. Click the System Configuration tab.
Or click .
3. Select Turbine Historian Configuration and click OK.
The Outline View displays the following items:
The Turbine Historian

Configuration is given
the default name, th1.
¾ To modify the name

Or double-click the device 1. From the Outline View, click the device name to highlight it.
name.
2. From the Edit menu, select Modify. The Turbine Historian Device
Properties dialog box displays.
753 of 1016
The default Device Name is
th1. Enter the new name
here.
The Plant Data Highway

(PDH) name must match the
Historian's computer
found on the control panel
applet network' identification
tab. The IP address must
match the IP address
assigned to the Historian's
network interface board
connected to the PDH.
Network Name for the PDH
must be unique, since all
Turbine Historian Devices
and all HMI devices
connected to a PDH will
this name to identify that
PDH.
Enter the root location for

PI data archive
Select the Measurement Systemwhose The Unit Data Highway Computer Computer Click OK to
engineering units and conversion data Name(UDH)
must be unique. The UDH IP Addressmust apply changes.
used to store and display the data on match the IP address assigned to the
Turbine Historian. Refer toChapter 7, network interface board connected to the UDH.
Configuring System , to configure UDH Network Namemust match the EGD
multiple
I f tiscales. name that all Mark VIs will use to communicate with
Turbine Historian.
754 of 1016
Templates
A Turbine Historian template is a grouping of signals typically based on turbine
type/turbine size. Templates can be imported or created manually.
¾ To import a Template
1. From the Outline View, click Turbine Historian Templates.
2. From the File menu, select Import. The Import File dialog box displays.
3. Highlight the desired template tree file.
4. Click Open. The template file is imported.
¾ To manually create a Template
Or, click an existing template 1. From the Outline View, click Turbine Historian Templates.
to highlight It, then right-click
2. From the Edit menu, select Insert First. The Turbine Historian Template
and select Insert First.
Name dialog box displays.
Enter a unique
template name.
¾ To modify Template properties

Right-click the Template and 1. From the Outline View, under the item Turbine Historian Templates, highlight
select Modify. Or, double- the template.
click the Template.
2. From the Edit menu, select Modify. The Template Properties dialog box
displays.
755 of 1016
Enter the Name here.
Enter the folder name to

which the Template will
be exported. If left
blank, the template file
is stored in the folder
where the Turbine
Historian resides.
Enter a Note about

the template.
Click OK to apply
changes.
756 of 1016
Collections
A Turbine Historian collection is a group of signals from one unit (turbine
network/controller pair). Collections can be created by instancing templates or
adding points manually.
¾ To create a Collection
1. From the Outline View, click Turbine Historian Collections to highlight
it.
Or right-click an existing
collection and select Insert 2. From the Edit menu, select Insert First. The Turbine Historian Collection
First. Name dialog box displays.
3. Enter a unique name and click OK. This name should be the two-character unit
name assigned to the unit in F:\config.dat.
Enter a unique Collection

name here. The name
should be the two-
character unit name
assigned to the unit in
F:\config.dat.
¾ To instance or remove a Template

Or double-click the 1. From the Outline View, click the collection to highlight it.
collection.
2. From the Edit menu, select Modify. The Collection Properties dialog box
displays.
Or right-click the highlighted 3. Click a template in the Templates Available list to select it.
collection and select Modify. 4. Click Add to add it to the Templates In Collection list. The template now
Multiple templates can be moves from the Templates Available list.
added to a collection. 5. Click OK to add the template signals to the collection.
Note An instanced template must have its wildcard substitution variables, %0, %1,
… %9 and ^, defined. To define the wildcard substitution variables, select the
template in the Templates In Collection list, then select the substitution variable in
the Substitutions list, then enter the string value. Click Apply. The %C substitution
is always set to the Collection name and cannot be edited.
757 of 1016
Enter a unique collection
name. This name should be
the two-character unit name
assigned to the unit in
F:\CONFIG.DAT.
Enter the name of the folder

where the collection file
will be exported. If left
blank, the collection file is
stored in the folder where
the Turbine Historian Device
file is located.
This displays the list of
templates available to be
added to the collection.
Select a template and click
Add to add the template to
the collection. The
Templates in Collection
box displays a list of the
templates already added.
To remove a template,
highlight the template name
and click Remove.
Enter a note describing the

collection.
To see the substitution symbols for a particular template, highlight the Template name
in the Templates in Collection list. The symbols for that template display in the
Substitutions box. To enter a value for a substitution symbol, highlight the symbol in
the Substitutions list, enter the value, and click Apply.
Note To add a signal to a Collection, refer to the section, Signals.
758 of 1016
Signals
Signals can be added to a collection manually by selecting the desired signals from
the available network signals. When a signal is added, default information is put into
the signal’s fields. When the command Get From Database is performed, some
fields may be overwritten with data from the SDB. The Exception Deviation field
must be updated for each manually entered signal.
Field Name Description Signal Definition vs. SDB Definition

Signal Name EGD signal name Cannot be different from SDB
Description Signal Description Uses SDB
Exception Deviation Change in engineering units that Must enter, not in SDB
triggers writing the signal to the
historian subsystem
Data Collection Determines if point is saved in Default is ENABLED, not in SDB
history
Data Type For example, REAL, BOOL Uses SDB
Units Engineering Units Uses SDB, if this field is blank
Precision Number of decimal places to Uses whichever is greater between the
display signal and SDB definitions
Maximum Data Plot Maximum plot limit, for display Default is 100, not in SDB
purpose only
Minimum Data Plot Minimum plot limit, for display Default is 0, not in SDB
purpose only
Maximum Raw Counts Maximum input value used to Default is 100, not in SDB
convert data to different
engineering units
Minimum Raw Counts Minimum input value used to Default is 0, not in SDB
engineering units
Maximum Engineering Units Maximum target value used to Default is 100, not in SDB.
engineering units
Minimum Engineering Units Minimum target value used to Default is 0, not in SDB
engineering units
Maximum Quality Limit Maximum value, in engineering Default is “*”, not in SDB
units, over which the quality bit is
set when saved in the database
Minimum Quality Limit Minimum value, in engineering Default is “*”, not in SDB
units, over which the quality bit is
set when saved in the database
759 of 1016
Add Signals From the Outline View
¾ To add a signal to a collection
Or click an existing signal to 1. From the Outline View, click an existing template under Turbine Historian
highlight it and then right- Templates, or click an existing collection under Turbine Historian
click and select Insert First. Collections to highlight it.
2. From the Edit menu, select Insert First. The Turbine Historian Signal
Name dialog box displays.
Append a unique
signal name to %C.
For a collection
signal, append a
unique name to the
<collection name>
or click Browse. . .
to display the SBD
Signal Browser.
.
¾ To add signals using the SDB Signal Browser

When the SDB Signal From the Turbine Historian Signal Name dialog box, click Browse…. The
Browser is opened from this SDB Signal Browser dialog box displays.
dialog box, only single-signal
selection is allowed.
Select EGD
network.
Click Query to
display a list of
network signal
that are defined in
the SDB. A list of
signals displays
in the Available
Signals list.
760 of 1016
Highlight the
desired
signal(s) and
click Add. The
added signals
display in the
Selected
Signals list.
When finished
selecting, click
OK to apply the
changes.
Add Signals Using the SDB Browser

¾ To add signals using the SDB Browser
1. To start the SDB Browser, click the View menu and select SDB Browser.
The SDB Browser dialog box displays.
761 of 1016
2. Select the Signal tab and click Query. The Query Design dialog box
displays.
Fill in the
appropriate
Criteria and
click OK.
The query
searches the
SDB and
displays the
results in the
SDB Browser
dialog box.
3. Highlight the desired signal(s) and press Ctrl+C to copy the signal information
to the paste buffer.
4. From the Outline View, highlight the target template or collection, then press
Ctrl+V to paste the signals into the template or collection.
762 of 1016
Modify Signals
¾ To modify Signal properties
Or, right-click the Signal and 1. From the Outline View, highlight the signal.
select Modify. Or, double-
2. From the Edit menu, select Modify. The Edit Turbine Historian Signal
click the Signal.
Definition dialog box displays.
Enter the Signal Name or click

Browse... to display the SDB
Signal Browser where you can
select a signal.
As the Exception Deviation,

enter the minimum number of
scaled units a signal must
change prior to being written to
the Historian subsystem ( see
note below).
Enable or disable Data

Collection to save this signal to
the Historian subsystem.
Display Settings:
The engineering Units depend
on the Measurement System
selected in the Device
Properties and the
corresponding value in the Mark
VI signal scale. Refer to Chapter
7, Configuring System
Information, to configure scales.
Precision is the number of
decimal places defined by the
Mark VI signal scale.
Conversion Settings:
The Conversion Settings
values are used for converting
the controller data from its
native format to a new format in
the Turbine Historian. Values The Quality Limits values, The maximum and minimum Data
are determined by the Mark VI in engineering units, are Plotting limits are defined by the
signal scale conversion settings over or under which the maximum and minimum conversion
and the Measurement System questionable bit is set. settings of the scales unless the Mark
selected for this device. These are typically set to ^, VI signal plotting limits are enabled.
allowing all data to be saved Refer to Chapter 3, Basic
Enter a signal Note. without setting the Configuration, to enable and set
questionable bit. the signal plotting limits.
Note The Exception Deviation field will be disabled, and will use the Mark VI's
signal deadband, if it is enabled. Leave the field blank to use 0.5% of the scaled data
plotting limits.
763 of 1016
¾ To edit multiple signals
1. From the Outline View, highlight a signal, then press and hold the ---Ctrl or
Shift key to highlight multiple signals.
2. From the Edit menu, select Modify. The Edit Turbine Historian Signal
Definition dialog box displays with the Signal Name field disabled
3. Use the mouse to select or press the Tab key to move to the fields to modify.
4. Enter changes and click OK. The following dialog box displays.
5. Select Yes to update all fields.

Select No to return to the Edit Turbine Historian Signal Definition without
making any changes. All selected signals will match this configuration.
Troubleshooting
When troubleshooting or The commands Build and Restart Services are disabled.
reporting errors, refer to the
Verify that the following PI Services are running:
Error Number in the error
message. This number relates • Network Manager
specific information regarding
the nature of the encountered • Update Manager
problem. • Archive Subsystem
• Snapshot Subsystem
• Base Subsystem
Verify that the following files exist in the specified drives and directories:
• F:\config.dat
• G:\exec\hst.exe
The commands Put In Database and Get From Database are disabled.
Verify that the SDB is defined correctly (refer to the Options menu, Settings, and
Database tab).
764 of 1016
Notes
765 of 1016
Chapter 13 Setup for Turbine HMI
Configuration
Introduction
TCI is part of the Turbine This chapter provides instructions for using the toolbox to configure the Turbine
runtime system, which HMI. The Turbine HMI configuration is used to import data into CIMPLICITY HMI
integrates the Mark VI and to generate a number of text files used by the Turbine Control Interface (TCI)
controller, CIMPLICITY system. Most of the information for the Turbine HMI configuration is obtained from
HMI, and PI or Historian the System Database (SDB).
systems
Section Page
Concepts .................................................................................................................13-2
Working With Files and Menus..............................................................................13-3
Configuration..........................................................................................................13-6
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 13 Setup for Turbine HMI Configuration • 13-1
766 of 1016
Concepts
The HMI configuration requires some setup tasks for the Build command to load the
CIMPLICITY system with signals from the SDB, and to automatically produce the
text files required by the TCI. The HMI configuration:
• Creates and defines configuration properties
• Specifies the network connection
• Specifies the EGD exchanges it uses
• Puts data into the SDB
• Gets signal data from the SDB
• Validates and saves the configuration file
• Uses the Build command to automatically perform the following:
− Import signals and other data into the CIMPLICITY system
− Produce the EGD icn.ini file
− Produce the turbine Alarm.dat, Hold.dat, Event.data, Soe.dat, and
unit_EGD.dat text files for the TCI runtime system
− Produce the turbine Enet_alm.dat file for the TCI runtime alarm
subsystem
− Modify the HOSTS file, if required
− Modify the CIMPLICITY CimHost.txt file, if required
− Run the utility program ddbuild2 that produces intermediate files for the
TCI subsystem
13-2 • Chapter 13 Setup for Turbine HMI Configuration GEH-6403L Toolbox for a Mark VI Turbine Controller
767 of 1016
Working With Files and Menus
The HMI configuration uses three types of files:
• Binary working files (.hmb) contain an exact copy of the configuration used by
the toolbox. Users generally work from .hmb files.
• Tree files (.tre) are text files that contain configuration information.
• Project files (.prj) are text files that can group all .tre files in a configuration.
Export as .prj and .tre files

¾ To save the HMI Configuration to a .prj file
1. From the Outline View, highlight the interface name you want to export.
HMI Configuration menu 2. From the File menu, select Export (see menu below).
commands are managed just
3. Select All. The Export Project dialog box displays to confirm the name of the
as other toolbox and
.prj file.
Windows menus (refer to
Chapter 3). 4. Click OK to save the .prj file.
¾ To save part of an HMI Configuration to a .tre file

1. From the Outline View, highlight the item you want to export.
2. From the File menu, select Export (see menu above).
3. Select Selected. The Export dialog box displays to select the name for the .tre
file.
4. Specify a file name or use the default, then click OK to save the .tre file.
768 of 1016
Device Menu Commands
¾ To put HMI configuration data into the SDB
1. From the Device menu, select Put to Database.
2. When the message box displays, click Yes.
The HMI configuration and the defined network connections are inserted into the
SDB device and topology tables. This data is then used when the HMI configuration
creates text files during the Build command.
¾ To get signal data from the SDB
1. From the Device menu, select Get from Database.
2. Click Yes on the toolbox message box.
The Get From Database gets all signals defined in the SDB for exchanges defined
in the HMI configuration. The signals are placed in the .tre file under each exchange.
769 of 1016
¾ To validate and build the HMI Configuration
1. Select the HMI configuration name at the top level of the Outline View.
2. From the Device menu, select Validate. A Validation complete message
displays in the status window.
3. From the Device menu, select Build.
When the following message box displays, click Yes.
Signal Attributes
• Setpoint limits can be defined for a signal in the toolbox. Setpoint limits
are not attributes of a scale. Enter the limits in the Native Measurement
System for the signal (if the signal’s native measurement system is U.S. and
has units of inches, setpoint limits may be setpoint low limit = 1 inch and
setpoint high limit = 10 inches).
• Display limits are initialized by the scale associated with the signal. The
display limits are fixed by the minimum and maximum engineering values
for the selected native measurement system of the scale. If the scale’s
selected native measurement system is U.S. and has units of inches, and the
minimum value is one inch and the maximum value is 10 inches, the
display low limit will be one inch and display high limit will be 10 inches.
However, it is possible to define display limits for a signal, independent of
the scale. If this is done, the display limits for the signal overrides those for
the scale. Just as for the setpoint limits, the signals display limits are defined
in the signals selected native measurement system. If the signal's display
limits are defined, these will be used for importing a point's display limits.
If the signal’s display limits are not defined, the display limits from the
scale are used to define the CIMPLICITY point display limits.
• Alarm class. If a signal is defined with an Alarm attribute, you may
assign an Alarm Class to the signal (alarm classes are defined in the system
information file of the toolbox. Controllers have a list of defined alarm
classes available after performing a get from the SDB). The signal’s alarm
class is imported into the CIMPLICITY system as an attribute of the point.
• CIMPLICITY screen name. If a signal is defined with an Alarm attribute,
you may assign the name of a CIMPLICITY screen file as an attribute of
the signal. The signal’s CIMPLICITY screen is imported into the
CIMPLICITY system as an attribute of the point. When an alarm is
generated in CIMPLICTY from the signal, you may then easily access the
defined screen from the CIMPLICITY alarm screen.
• CIMPLICITY enumerations. CIMPLICITY enumerations show up in the
work inch under Points/Point Enumerations in the left-hand tree view. If an
SDB signal has an enumeration associated with it, the enumerations name is
included in the CIMPLICITY point attribute. The enumeration itself will
have been imported during the build before signals are imported.
770 of 1016
Configuration
This section provides instructions for using the toolbox to setup and configure the
HMI.
¾ To create a Turbine HMI configuration
1. From the File menu, select New. When the New window displays, click the
System Configuration tab.
2. Select Turbine HMI Configuration. Click OK.
The HMI Configuration window is created with a temporary name, such as hmi1.
The Outline View of the window displays the following items:
Configuration name
771 of 1016
Modify HMI Configuration Properties
¾ To modify HMI configuration properties
1. From the Outline View, click the interface name to highlight it.
2. From the Edit menu, select Modify. The HMI Configuration Properties
Enter a Network Name for the PDH
or select from the drop-down list.
Enter the Configuration

Name.
Enter the name and

address information for
the Plant Data Highway
(PDH).
Enter the name and

address for the Unit Data
Highway (UDH).
Enter the location and

name
. of the HMI
CIMPLICITY Project File.
Select either Language 1

or 2 to specify which
language will be used for
descriptions when
importing signals into the
CIMPLICITY HMI system.
The language names are
derived from the System
Information (see chapter
7), which puts the names
in the SDB.
772 of 1016
Define a Network Connection
¾ To define a network connection
Or right-click and select 1. From the Outline View, click the item Hardware and I/O Definitions.
Insert First.
3. The Enter or Select a Network dialog box displays.
4. Enter the network name or select a network from the drop-down list.
5. Click OK. The network item is inserted in the Outline View.
EGD
Network
Interface
773 of 1016
Edit EGD Network
¾ To modify a network connection
1. Click the network name to highlight it.
Or right-click the Network
2. From the Edit menu, select Modify. The Edit EGD Interface dialog box
name and select modify.
displays.
Network Name
Network Number is assigned

by the SDB when the command
Put in Database is performed.
Producer ID is usually the

name of the computer on the
UDH
Source is the name and

location of the exported .tre file.
If the network has not been
exported, this field will be blank.
Insert EGD Exchanges

Any number of EGD exchanges are inserted in the toolbox in the Outline View
under the EGD network. The exchanges should contain the signals needed by the
CIMPLICITY HMI system. Once the exchanges are inserted, use the command Get
from Database to make the signals for each defined exchange available for import
into the CIMPLICITY HMI.
¾ To insert one or more Exchanges into a configuration
1. From the Outline View, click the desired network.
Or click the right- mouse 2. From the Edit menu, select Insert First. The Select EGD Exchange(s)
button and select Insert First. dialog box displays.
774 of 1016
Once the Exchanges are 3. Either type the name of the exchange directly in the exchange text box, or click
inserted, signals can be one or more of the exchanges in the list. The format for the exchange is <device
inserted using the command name:exchange name>.
Get From Database.
4. Click OK. The Outline View displays all the selected exchanges.
After the Get from Database command is performed, the signals associated with
each exchange are inserted into the tree view, as shown below.
775 of 1016
Signals
All signals for each exchange defined in the HMI configuration are imported into the
CIMPLICITY point database when a build is performed. A number of automatic
actions take place during this step of the build.
• If the required devices and resources have not been defined in CIMPLICITY
yet, this step of the build creates them in the CIMPLICITY system. The defined
measurement systems (typically US and metric) are inserted or updated in the
CIMPLICITY system.
• If there is a scale associated with the SDB signal, a CIMPLICITY measurement
unit is created and identified by the SDB scale name. If dual scaling has been
defined, these are used to create the required measurement units and the
associations required for switching between measurement systems in the
CIMPLICITY system. If the signal is a float (or real) and the precision has been
defined, this data defines the CIMPLICITY precision. If it is not defined in the
SDB, a default precision of 2 is used.
• If there is an enumeration associated with the SDB signal, the enumeration name
is included as an attribute of the CIMPLICITY point.
• All signals imported into CIMPLICITY use the ICN DevCom and the
Unsolicited and On Change update mode.
• If the signal being imported has the scale enabled, the build defines the forward
and reverse scale equations for the equivalent CIMPLICITY point. A signals
scale is enabled or disabled by the device that owns the signal.
• CIMPLICITY can own signals on EGD. For these signals, CIMPLICITY writes
the values with the EGD exchanges being broadcast on the exchanges periodic
rate. The signals must be defined by a Network Interface device, in order to
accomplish this (which essentially represents the CIMPLICITY system). The
producer IP and the IP address for the Network Interface must match the IP of
the box on which the CIMPLICITY server is located, which is also the IP of the
HMI Device. The Network Interface is ‘Put’ to the SDB. When the HMI
Device is configured to use the exchanges from the Network interface and a
‘Get from database’ is performed, the signals will be configured as Read/Write.
This is the direction the signals will have when imported into CIMPLICITY,
giving it the ability to write the values.
Note Refer to the section, EGD Point Settings, for details on how to enable/disable
scaling for an EGD signal.
776 of 1016
Controller tab 2-18
Create a controller 3-45
Index Database
SDB and USDB 11-2
DLAN+ Interface
Status_S pages 3-147, 9-75
Draw commands 8-14
Dynamic Data Recorder (DDR) 3-148
Add Signals 3-152, 12-11, 12-12
Configure DDR 3-149
Status Signals 3-150
UpdateDDR 3-152
A
E
AcDcEx2000 tab 2-26
Alarm Scanner tab 3-7, 3-10 EGD Interface
Application Code Edit 13-9, 14-8
Download 3-100, 3-101, 3-107 Exchanges 9-32, 9-33, 9-35, 13-9, 13-10, 14-9
Modify 3-101 Insert 13-9
Application Diagnostics
Generating 3-142, 9-59 F
Application Documentation
Block diagram 3-125 Field Control module
Reports 3-28, 3-125, 3-133, 3-139 Conventional 9-52
Intelligent 9-53
Points 9-2, 9-14, 9-36, 9-37, 9-48, 9-54, 9-63, 11-6
B Finder window
Batch Operations Text/Address tab 3-146, 4-3
Error log 5-5 Forcelist commands 9-58
Block Diagram tab 2-19, 3-131, 3-132
Blocks G
Description 3-137, 3-138, 12-10
Flow diagram 3-131 Genius Block Detail View 9-47, 9-48
Rename 3-83, 3-84 Genius network
Renumber 3-26, 3-83, 3-84 Field Control Station 9-39, 9-44, 9-45, 9-48, 9-55, 9-
Rubber 3-79 56, 9-58
LAN board 9-43
View 9-41
C Get From Database command 3-91, 11-2
Checkin/Checkout utility 5-4, 6-1 Graphics window
Comment block 3-131 Create 8-3
Configuration files Draw commands 8-14
Export 3-17 Properties toolbar 8-9, 8-30
Control Constant View View Signal Summary 8-5, 8-9
access 3-118 Graphics Windows for the Control Operator Interface
Access 2-7, 2-34 (COI) 8-40
Controller Properties
Alarm Scanner 3-7, 3-10 H
General 2-13, 3-3, 3-39, 9-4
Memory 3-10 Hardware and I/O Definitions
Note 3-6 Description 3-137, 3-138, 12-10
NTP 3-5 Help
TMR 3-9 Menu 3-32
GEH-6403L Toolbox for a Mark VI Turbine Controller Index • I-1
777 of 1016
Hold List Scanner tab 3-10 Description 3-137, 3-138, 12-10
Points 3-137, 9-14, 9-30, 9-37, 9-47, 9-48, 9-54, 9-59,
I 9-63, 9-66, 9-69, 9-71, 9-72, 9-75, 13-11
NTP tab 3-5
I/O Mapper 3-3
I/O or Network Interface
O
Insert 9-3, 9-23
Mark VI 2-4, 2-29, 3-1, 3-3, 3-7, 3-8, 3-10, 3-12, 3- OC2000 tab 2-25
13, 3-29, 3-42, 3-57, 3-58, 3-91, 3-96, 3-99 Output files
I/O Points 8-38, 9-2, 9-59 Types 3-28, 3-139, 3-140, 9-6, 9-36
Inline module 3-43 Override module 3-43
Innovation Series Drive tab 2-20, 2-28
Instanced module 3-43 P
Passwords
L
Changing 2-10, 2-11
Libraries Pcode files (.pcd)
Description 3-137, 3-138, 12-10 Build 3-24, 3-29, 3-91, 3-92, 3-101, 3-107, 3-146, 3-
Libraries tab 2-16 147, 5-1, 9-31, 12-2, 12-3, 12-15
License Description 3-137, 3-138, 12-10
Agreement 2-2 Print tab 2-17
Privilege level
M Functions 2-8, 2-9, 3-1, 3-21, 3-43, 3-44, 3-46, 3-53,
3-63, 3-125, 3-134, 10-8, 10-9, 11-2
Macro and Module libraries Setting 2-1
Lock 6-1 Product code (runtime)
Macro Definition Load 3-28, 3-94, 3-116
Description 3-137, 3-138, 12-10 Upgrade 2-3, 3-105, 9-16
Edit 3-72, 3-74, 3-81 Profibus Interface 10-13, 10-14
Macro Pins Project files (.prj)
Description 3-137, 3-138, 12-10 Create and view 3-137, 3-138, 12-10
Macros
Description 3-137, 3-138, 12-10
R
Main Board
NOVRAM 3-108, 9-60, 9-61, 9-62, 9-63, 11-7 Register network
Memory tab 3-4 Custom Register Network 9-64, 9-72
Menus DH+ 9-64, 9-70, 9-71
Help 2-7, 2-10, 2-29, 3-8, 3-17, 3-32, 3-38, 8-3 Ethernet Modbus 9-64, 9-68, 9-71, 9-72
Module Definitions Ethernet SRTP 9-65, 9-67
Description 3-137, 3-138, 12-10 Serial Modbus 9-68, 9-69
Edit 3-65 Reports
Insert 3-63 Generate 3-142, 3-144, 9-58
Module Pins Signal Cross Reference 3-28, 3-125
Description 3-137, 3-138, 12-10 Signal list 3-133
Modules Simulation data 3-133
Description 3-137, 3-138, 12-10 Requirements 2-2
Resource name 7-2
N RLD editor
Commands 3-25, 3-28, 3-29, 3-83, 3-91, 3-115, 3-
Network Interface 124, 8-14, 9-16, 9-30, 12-2, 13-4, 14-3, 14-4
Create 10-3 Description 3-137, 3-138, 12-10
Dialect 10-7
Signals 3-24, 3-29, 3-37, 3-53, 3-91, 3-115, 3-122, 3-
S
133, 3-134, 3-152, 4-3, 8-38, 8-40, 9-25, 9-63
Note tab 3-6 Scale definitions
NOVRAM Description 3-137, 3-138, 12-10
I-2 • Index GEH-6403L Toolbox for a Mark VI Turbine Controller
778 of 1016
Serial Loader
Starting 3-83
Settings
AcDcEx2000 2-26
Controller 2-18
Database 2-15, 11-12, 12-15
EX2100 2-23
General 2-13, 3-3, 3-39, 9-4
Innovation Series Drive 2-20, 2-28
Libraries 2-16
OC2000 2-25
Print 2-17
Static Starter Drive 2-24
Tosvert Series Drive 2-22
Trend Recorder 2-27
Signals
Concepts 3-37, 3-45, 7-2, 10-2, 13-2, 14-2
Pin connection 11-5
Status_S pages 3-147, 9-75
String substitution 3-89
System information
Files 7-2
T
TCP/IP
Configure 3-98
TMR tab 3-9
W
Watch Windows 3-28, 3-114, 3-115
Select Watch Window 3-114
Work Area
Detached Summary View 2-5, 2-19, 3-85, 3-112, 3-
131, 8-39, 9-41, 9-47
GEH-6403L Toolbox for a Mark VI Turbine Controller Index • I-3
779 of 1016
g GE Energy
1501 Roanoke Blvd.
1 540 387 7000

www.geenergy.com
780 of 1016
*(+$9ROXPH,RI
)
6XSHUVHGHV*(+
*(,QGXVWULDO6\VWHPV
Reduced manual for Mark VI Maintenance training
)RU63(('7521,&7XUELQH&RQWURO
2SHUDWRU¶V*XLGH
781 of 1016

!

! DVLV !
"#

!$!

!
$
!
!
% ! !

&!
$
$ !
%

!

!
"
!
! '
&!
$

( ! "
&! !
%!

!

!$) !
%! !

&!!
$ $
(!
!
$
!
! *!
!
$ +
(!

,-,. "/

01,-23415
+ 6,7771.087771219297 :
6,-1297278(
:
; #+ 6,-12797448
:
8<6=
&!
! :
%!

! !

!
'

&! $%!
$!

$
!

(!

>! ( + ?34,40

!(8,:
%
@ ' + % >
%
.$
+ A

.B% ">

(AC((%D ! "; !! B (
"E#
#
A B A @ @ B% "A

A$! "!
! "(

(3/" "F( (
>%.FB( "

782 of 1016
6DIHW\6\PERO/HJHQG
,QGLFDWHVDSURFHGXUHFRQGLWLRQRUVWDWHPHQWWKDWLIQRW
VWULFWO\REVHUYHGFRXOGUHVXOWLQSHUVRQDOLQMXU\RUGHDWK
VWULFWO\REVHUYHGFRXOGUHVXOWLQGDPDJHWRRUGHVWUXFWLRQRI
HTXLSPHQW
,QGLFDWHVDSURFHGXUHFRQGLWLRQRUVWDWHPHQWWKDWVKRXOGEH
VWULFWO\IROORZHGLQRUGHUWRRSWLPL]HWKHVHDSSOLFDWLRQV
1RWH(

!
*(+$9ROXPH,2SHUDWRU¶V*XLGH 6DIHW\6\PERO/HJHQG••D
783 of 1016
7RSUHYHQWSHUVRQDOLQMXU\RUHTXLSPHQWGDPDJH
FDXVHGE\HTXLSPHQWPDOIXQFWLRQRQO\DGHTXDWHO\
WUDLQHGSHUVRQQHOVKRXOGPRGLI\DQ\
SURJUDPPDEOHPDFKLQH
7KHH[DPSOHDQGVHWXSVFUHHQVLQWKLVPDQXDOGR
QRWUHIOHFWWKHDFWXDODSSOLFDWLRQFRQILJXUDWLRQV%H
VXUHWRIROORZWKHFRUUHFWVHWXSSURFHGXUHVIRU
\RXUDSSOLFDWLRQ
E••6DIHW\6\PERO/HJHQG +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
784 of 1016
&RQWHQWV
Reader Comments
&KDSWHU2YHUYLHZ
( ! ,3,
?A(F ,3
! ; ! ,3
?A( ,32
>
,31
! ,34
F
; ! ,39

3; ! ,39
%
,39
.
>! ,37
? %>! ,35
%# ,35
? ?
,3,
&KDSWHU4XLFN6WDUW3URFHGXUHV
( ! 3,
?A(3

>
32
F) 31
F %
3-
> .!>
3-
%? 3-
%C0 3-
> >
34

C
34
?
C >
8 %!$
:34
&KDSWHU'LVSOD\2QO\3URJUDPV
( ! 23,
> .!>
23
;
! ! 23
> .!>
@ 232
> .!>
234

&!>
239
;
;! 239

0 % $!
> 237
%? 235
%? ;
235
%? 23,,
%? >
/#23,,
> ? .!
@ 23,
%? A "0( 23,2
*(+$9ROXPH,2SHUDWRU¶V*XLGH &RQWHQWV••L
785 of 1016
&RQWHQWV²&RQWLQXHG
%C0 23,1
%C;
23,1
%C0 >
/#23,1
0 .!
23,-
%C0 23,-
&KDSWHU&RQWURO&RPPDQG3URJUDPV

( ! 13,
> >
13
> >
13
@" ;
132
> >
@ 131
> > 134
% % 134
> >
139
>
A 139
@" % 13,,
F F 13,2
C! 13,2
! 13,2
A!

! 13,1

C
13,-

C
13,-
?
C 8
: 13,4
?
C 13,4
?
C 13,4
?
C .!
13,4
&KDSWHU&,03/,&,7<'LVSOD\V
( ! -3,
(AC((%D EF$) -3
A !
H>
-3
%
80
%
: -34

;
?A(-37
! -37
!.! -3,
!
;
-3,1
#
;

-32
!
(
;
-3-
#
-34
. $
>
-37
LL••&RQWHQWV +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
786 of 1016
&RQWHQWV²&RQWLQXHG
&KDSWHU&,03/,&,7<3URMHFW&RQILJXUDWLRQ
( ! 43,
@"$43
F ) 432

A 431
!431

43-

434
(
437
#

A 43,
>/# 43,
>/
43,

A$! > ( 43,,
FC
8F: 43,
$SSHQGL[$+0,)XQFWLRQ5HIHUHQFH
?A(;! %!$
3,
(AC((%D?A(! ;! 31
$SSHQGL[%$ODUP2YHUYLHZ
( ! /3,
?
C
8 %!$F
: /3

/3
8 ?
:
> ;
/3
>
/32
*ORVVDU\
,QGH[
*(+$9ROXPH,2SHUDWRU¶V*XLGH &RQWHQWV••LLL
787 of 1016
&KDSWHU2YHUYLHZ
,QWURGXFWLRQ
*(GRFXPHQW*(+$ %?! 3A ( 8?A(:>%.FB( !$
!3
9ROXPHGHVFULEHV+0,

3
3

PDLQWHQDQFHIHDWXUHV &! ( ! 3$ " ! A I@ B%I
LQWURGXFHGLQWKLVFKDSWHU
3 !%?A(

A "(0A "0A "0CA A "0( !$

%! ?A( ( !
!
$
?A( ! (AC((%DI?A(!
>%.FB(A "(0A "0A "0CA A "0( !$

. +RZWR8VH7KLV'RFXPHQW
% $ ?A(
!$
!
! ! !

!$ !
% H
+
6HFWLRQ 3DJH
?A(F ,3
! ; ! ,3
?A( ,32
>
,31
! ,34
F
; ! ,39

3; ! ,39
%
,39
.
>! ,37
? %>! ,35
%# ,35
? ?
,3,
*(+$9ROXPH,2SHUDWRU¶V*XLGH &KDSWHU2YHUYLHZ••
788 of 1016
+0,2YHUYLHZ
7KH&,03/,&,7<+0,LVD ?A(! 8
#: $ %!$
(
SURGXFWRI*()DQXF 8%(:(AC((%D/8T(A/: %!$

!
$XWRPDWLRQ >
?A(! ! (AC((%D?A(

! ! 8#:
%?A( $!

&! !
7KHWRROER[LV*(¶V:LQGRZV
EDVHGVRIWZDUHSDFNDJHXVHG 1RWH%%!$

! > %!$
IRUFRQWUROOHUFRQILJXUDWLRQDQG %

$#8
$#:> ? %. A "0(
GLDJQRVWLFV !$
!
$# !
! ?A(
!$
! +
• A !$ !

8#

! $ $ ":
• (!
!$8#

F! . 'C :
3URGXFW)HDWXUHV
%?A( !$! !

+
• >
•

• $

•

8 :
• ?A( !
••&KDSWHU2YHUYLHZ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
789 of 1016
+0,&RPSRQHQWV
% !$
?A(
!
8
;!,3,:+
*).SURYLGHVDGHWDLOHG • &,03/,&,7<+0,!

!$ !
GHVFULSWLRQRIWKH&,03/,&,7< $
! 8:.
,
SURGXFW¶VFDSDELOLWLHV (AC((%D ! !$

J +0,6HUYHU !$
$ >
?
> ? 8A "0(
:
! %

! $
#

J +0,9LHZHU !
!
(

!

!

!
$

• 7XUELQH&RQWURO,QWHUIDFH7&,!
8
,3! : !
!$! %(

!$

! +

J
3 ! !$
8A "(0
0:
J !$
! $
8A "(0 0:
J

!$
8A "
0(:
J A 8A "(0 0:
• 7&,0%8%('(AC((%D/!

&,0%RU&,0%ULGJH:
$ (A((%D %(
+
J $
(AC((%D

!$!
J ; 8A "(000CA:
8
: (AC((%D
• 6\VWHPGDWDEDVH8A "0(
: $

(

$

('F

$
> 8>:# %
$ ! ! $! &!!

> H
$$

$! !

! %!
! ?A(
! $
#

790 of 1016
&,03/,&,7< 7&,0% 7&,

)LJXUH'DWD)ORZ%HWZHHQ+0,&RPSRQHQWV
*UDSKLF'LVSOD\V
%?A(!
! (AC((%D

%

3
6FUHHQVDUHGHYHORSHGXVLQJ %?A(
!
SUHFRQILJXUHGJUDSKLFEXLOGLQJ

! ! >

EORFNVWKDWSURYLGH $

$)
FRPPRQDOLW\WRGLIIHUHQWSODQW !
"$ ?3

$!
DSSOLFDWLRQVWKDWXVHWKH+0,

,
?A(

! ! $

&! !

?A( " !
H

%

!
;!,3
!
0 !

3
!$
% 8: $
!

!

791 of 1016
& #" #$%
&!&
!
"
!
"

)LJXUH6DPSOH+0,'LVSOD\6KRZLQJ6WHDP7XUELQHDQG*HQHUDWRU'DWD
% "?A(!

3
!
H
!
+
*).SURYLGHVDGHWDLOHG • &LP(GLW $) 3 !
GHVFULSWLRQRIWKH&LP(GLWDQG

@
&LP9LHZDSSOLFDWLRQV ! ! ; !
!+
J
$
J F$) C" $8FC:
J A
J ;
$) $
$
• &LP9LHZ ?A(!3

8 ;!,3:(0

!FC !
! $) ,3

" ?A(
0
792 of 1016
• $ODUP9LHZHU
! !

$ $! $ $!
!
! $

$
! $)
0
• 7UHQGLQJ$ E
!
$

%!
$ ?A( 3

" > $ ! $

$ $
%
!!

!

H

• 7KHSRLQWFRQWUROSDQHO

3

!
!F

$ !
• 7KHEDVLFFRQWUROHQJLQH
!

"!

$
"$ % ! 0!
/

!
&RPPXQLFDWLRQV
5HIHUWR*(+9RO,, ;!,32 "!$ ?A( !
DQGLQGLYLGXDOFRQWUROOHU >%.FB( !$

GRFXPHQWVIRUPRUHGHWDLO
DERXWWKHQHWZRUNVDQG
SURWRFROXVHGIRU+0, ) ($&$
FRPPXQLFDWLRQ

()
()#*+ ()#*, & (

'
)-($&$
) #

.& #.
#
) )

' ' '

)/0 )/0 )/0
)LJXUH([DPSOHRID7XUELQH&RQWURO&RPPXQLFDWLRQV1HWZRUN
793 of 1016
; %'(! &! ! $!

8>: ?A((!

8A: A$!I
A

! !

3

+ 3
&!

! >&!
$
!
A$! ?A(
> !

!$
2SWLRQDO)HDWXUHV
'RFXPHQW*(+SURYLGHV %?A(! @ B%I3$ +LVWRULDQ!

LQIRUPDWLRQDERXWWKH
!

F(*(3/"I
+LVWRULDQ

3
! ?

'?A(0 %?A(! ? !
3$
> ? 8>?: !.32

%?A(
! WLPHV\QFKURQL]DWLRQ $
$
3 3

! @!
$

!$

! !

&!

:HE*DWHZD\
?A(

( %
?A( #

> $

('F !
$SSOLFDWLRQ6SHFLILF)HDWXUHV
@ ?A( 0DUN9RUWKH0DUN9,WXUELQH
FRQWUROOHUV !$

$

?A(%A "0( ! $
%
$#
8
$#:
@ ?A(!!,QWHJUDWHG&RQWURO6\VWHPV8(:!

%DODQFHRI3ODQW8/F:
('/F
$
?A(
7HFKQLFDO6SHFLILFDWLRQV
# ?A(
! * ! %?A( "

! ?A(

794 of 1016
5HODWHG'RFXPHQWDWLRQ
%
!
?A( >%.FB( !$

! ?A( +
³*(+´LVWKHGRFXPHQW +0,UHODWHGGRFXPHQWV
LGHQWLILFDWLRQQXPEHU
• ?34,40
!II+0,IRU63(('7521,&7XUELQH&RQWUROApplication
*XLGH
• (3,,4-*('66WDQGDUG0HVVDJH)RUPDW
• (3,956'%([FKDQJH8VHU¶V*XLGHIRU&RQWURO6\VWHP6ROXWLRQV
• (3,-6\VWHP'DWDEDVH8WLOLWLHVIRU&RQWURO6\VWHP6ROXWLRQV
• (3,-,2+0,7LPH6\QFKURQL]DWLRQIRU63(('7521,&7XUELQH&RQWURO
• (3,-,13RZHU%ORFN&RQWUROIRU63(('7521,&7XUELQH&RQWURO
3URGXFW'HVFULSWLRQ
• (3,-,-0LFURVRIW1HW0HHWLQJIRU63(('7521,&7XUELQH&RQWURO
,QVWDOODWLRQDQG6HWXS
• (3,-,4*(,QGXVWULDO6\VWHP6WDQGDUG0HVVDJHV*60
• (3,-2-0RGEXV&RPPXQLFDWLRQ,QWHUIDFHIRU63(('7521,&0DUN9,
7XUELQH&RQWUROOHUV
• ?3417XUELQH+LVWRULDQ6\VWHP*XLGH
• ;K3,,7&,03/,&,7<%DVH6\VWHP8VHU
V0DQXDO
• ;K3,,7,&,03/,&,7<+0,3ODQW(GLWLRQ%DVH6\VWHP'HYLFH
&RPPXQLFDWLRQV0DQXDO
• ;K3,254&,03/,&,7<+0,&LP(GLW2SHUDWLRQ0DQXDO
• ;K3,49-&,03/,&,7<+0,23&6HUYHU2SHUDWLRQ0DQXDO
0DUN9,FRQWUROOHUDQGUHODWHGGRFXPHQWV
• ?3412&RQWURO6\VWHP7RROER[IRU&RQILJXULQJD0DUN9,7XUELQH
&RQWUROOH
• ?3417&RQWURO6\VWHP7RROER[IRU&RQILJXULQJWKH7UHQG5HFRUGHU
• ?341,63(('7521,&0DUN9,6\VWHP*XLGH9ROXPHV,DQG,,
• L3917-63(('7521,&0DUN9,7XUELQH&RQWURO6RIWZDUH0DLQWHQDQFH
• (3,97'DWD+LVWRULDQ
0DUN9DQG9/0FRQWUROOHUDQGUHODWHGGRFXPHQWV
• ?3-59563(('7521,&0DUN97XUELQH&RQWURO8VHU¶V0DQXDO
• ?3-5763(('7521,&0DUN97XUELQH&RQWURO0DLQWHQDQFH0DQXDO
• ?34,5-63(('7521,&0DUN97XUELQH&RQWURO$SSOLFDWLRQ0DQXDO
2YHUYLHZ
• ?342-10DUN9/063(('7521,&7XUELQH&RQWURO,!8VHU¶V0DQXDO
795 of 1016
+RZWR8VH7KLV'RFXPHQW
%! ! !
$
A @
# >%.FB(
!$

)RUDQH[DFWRXWOLQHRIWKH %! H

GRFXPHQW¶VFRQWHQWDQG ! ! ?A(
RUJDQL]DWLRQUHIHUWRWKH7DEOH
&KDSWHU2YHUYLHZ ! ! !

RI&RQWHQWV
!
&KDSWHU4XLFN6WDUWXS !
?A(
&KDSWHU'LVSOD\2QO\$SSOLFDWLRQV$?A(

!

&KDSWHU&RQWURO&RPPDQG$SSOLFDWLRQV$?A(

!

&KDSWHU&,03/,&,7<'LVSOD\V?A(! !(AC((%D

! E$)

&KDSWHU&,03/,&,7<3URMHFW&RQILJXUDWLRQ
!
! (AC((%D)

! ?A(!

>%.FB(

! !
!$

! ?A(
7H[W&RQYHQWLRQV
%
$
!
! !
&RQYHQWLRQ 0HDQLQJ
Ø !

B!$
!
$
8#

$ H
!
!$ 8!$ : $

8#
DEF
/!
8•:
.
!$!
w !

/#8¨:
"

$ULDO%ROG @$ !

!
$#
# $#
Monospace . #
>F #

796 of 1016
+RZWR*HW+HOS
(
$ ! !

+
³´LQGLFDWHVWKHLQWHUQDWLRQDO (!

DFFHVVFRGHUHTXLUHGZKHQ

FDOOLQJIURPRXWVLGHWKH86$ ,-,. "/

01,-23415
+ 6,7771.087771219297 :
6,-1297278(
:
; #+ 6,-12797448
1RWH
&! !$ &!

!$
$
#
&!

797 of 1016
&KDSWHU4XLFN6WDUW3URFHGXUHV
,QWURGXFWLRQ

?A(3

! H

&! ! *
( !!

!

3!
% $ !!
! ?A(
>
?A( ! !
% H
+
6HFWLRQ 3DJH
?A(3

>
32
F) 31
F %
3-
> .!>
3-
%? 3-
%C0 3-
> >
34

C
34
?
C >
8 %!$
: 34
*(+$9ROXPH,2SHUDWRU¶V*XLGH &KDSWHU4XLFN6WDUW3URFHGXUHV••
798 of 1016
6WDUWLQJ8S+0,
Ø7RVWDUWXSWKH+0,DQGRSHQ\RXUDSSOLFDWLRQ
w ! "&WUO6$OW6'HOHWH

$
*).GHVFULEHV&LP9LHZ @ ! (AC((%D0 80 :

LQGHWDLO !
8;!3,:

(AC((%D
1RWH%?A(
! 0 81
:
$(AC((%D
(

! !
$$

!
$!
2
"
!!

2

"

!
"

#
!3$ $ %$!
!
"
.,4,
%
)LJXUH([DPSOHRI+0,6WDUWLQJ6FUHHQ
••&KDSWHU4XLFN6WDUW3URFHGXUHV +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
799 of 1016
$ODUP'LVSOD\V
2&;LVDQREMHFWOLQNLQJDQG $ODUP9LHZHU FE$) $ (AC((%D?A(
HPEHGGLQJ2/(FXVWRP ;!3,(
! !
FRQWURO
$ ! !
! ! $

! %( ! (AC((%D

%!$
%( 6LOHQFH/RFN 8QORFN
0
!8([WHQGHG$ODUP&RPPDQGV -:
'"" 3$$ $$ %$

3$ $

!
$!
"
)LJXUH([DPSOHRI$ODUP'LVSOD\6FUHHQ
800 of 1016
2SHQLQJ3URMHFWV
'RFXPHQW*).SURYLGHV %(AC((%D@"$
! ! H
GHWDLODERXWXVLQJ:RUNEHQFK ) . -#
!@"$
Ø7RRSHQDSURMHFW
, F @ ;
#

F %56"2
2 >!$
3
" %

%@"$
8;!32:
7%$5
7%$5 4 %"!
4"! 4#

4#""2 42""
$" #$
4#"2 42&8! &
( " "
. !$

#

"" % !
0 2
""

.
!
. !
$
%

!&$ 2 !
"
)LJXUH6DPSOH:RUNEHQFK'LVSOD\
••&KDSWHU4XLFN6WDUW3URFHGXUHV +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
801 of 1016
2WKHU7RROV
%

@ 3$ 3! ! ?A(

3

?
$ !
!! $ 2 1
!
For Mark VI, refer Toolbox manual GEH-6403
'\QDPLF5XQJ'LVSOD\
5HIHUWR&KDSWHUIRUPRUH %> .!>
! !
LQIRUPDWLRQ 0DUN9
(

! $
"

&! ! 8A "0(!
$#
! :
Ø7RRSHQWKH'\QDPLF5XQJ'LVSOD\
wF @ "
6WDUW7XUELQH&RQWURO0DLQWHQDQFH*URXS
8QLW7 '\QDPLF5XQJ'LVSOD\
7ULS+LVWRU\
5HIHUWR&KDSWHUIRUPRUH %%?

8
:

LQIRUPDWLRQ $ !
% H 3 3

Ø7RYLHZWKH7ULS+LVWRU\
, F @ "
8QLW7 7ULS+LVWRU\
; %?
$#8;!232:

!
6HOHFW8QLW

2
" 6HOHFW/RJ $!
$

1
" &ROOHFW$! &DQFHO$!
D!
@

!!

!

7ULS/RJ9LHZHU
5HIHUWR&KDSWHUIRUPRUH (%( ?A( !!A "0

LQIRUPDWLRQ !

ODVWWHQWULSV ?A(8%?A(

!
$!
:
Ø7RYLHZWKH0DUN97ULSORJ
, F @ "
8QLW7 7ULS/RJ9LHZHU
; %C0
$#

! 6HOHFW8QLW

$#
2 ; 6HOHFWD3UHYLRXV7ULS/RJ

$

1
" *R7R$!

8
:
802 of 1016
&KDSWHU'LVSOD\2QO\3URJUDPV
,QWURGXFWLRQ
%?A(
$
!

.
!

&KDSWHUGHVFULEHVFRQWURO %?A(*
3

! !$

FRPPDQGSURJUDPV D!

% $
3
(
+
6HFWLRQ 3DJH
> .!>
23
;
! ! 23
> .!>
@ 232
> .!>
234

&!>
239
;
;! 239

0 % $!
> 237
%? 235
%? ;
235
%? 23,,
%? >
/#23,,
> ? .!
@ 23,
%? A "0( 23,2
%C0 23,1
%C;
23,1
%C0 >
/# 23,1
0 .!
23,-
%C0 23,-
*(+$9ROXPH,2SHUDWRU¶V*XLGH &KDSWHU'LVSOD\2QO\3URJUDPV••
803 of 1016
'\QDPLF5XQJ'LVSOD\
0DUN9,XVHVWKHWRROER[IRU %> .!>
!

WKLVIXQFWLRQ A "0
(

! $
"
&!
! % !
+
• !
• .!C >
8.C>:!
!
H
• //

"!
!

!

!
• > >
8 1:

!
!
• ;!

!
!

! *
&! 8:
%
!

> .!>
+
• %(! $!
• A
! $
•

!
• $!
! *
)LOH6WUXFWXUH
7DEOH'\QDPLF5XQJ'LVSOD\)LOH'HVFULSWLRQ
)LOH1DPH 'HVFULSWLRQ
#';# . 7

$
<
%
1#
!$

1# '$
%
%$!!
<

606=)=70 >. '$ !%% %$

606))'). '$"!%% %$
6061) '$"%
%$
!"
6061# #<==7

%
%
!$ > .!>
!

!
%

!!
!
$
$ > .!>
(
! &!
!

%> .!>
QRW

!

(
>
.!>

!

••&KDSWHU'LVSOD\2QO\3URJUDPV +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
804 of 1016
7ULS+LVWRU\
0DUN9,XVHVWKH&RQWURO %%?

8
:

6\VWHP7RROER[IRUWKLV $ A "00CA!
% H
IXQFWLRQ 3 3
% !

! !$

D! ! !

87ULS+LVWRU\'LDORJ%R[$
:

> $ 8>/: $
%
841 #:

8()#';=# :

# A "0

! 8()#;:
7ULS+LVWRU\)LOH
%? !

3
#

%

!A B 8'DWD+LVWRU\5HVXOWV:LQGRZ:
%%?

$ %
? %
! ()#';=# 3
!
! (

!3 $
D! ! #

62(VDUHVHTXHQFHRIHYHQWV ;3 3 8%(A:

> %

# #$
!

%
! $
F

!$
(
! #

%
%C>

! ! 8()#;:
!

$! !

"%! ! 3
3( !
#!
! !
! H
;!232
()#';=#
!

!$ ! ()#;!
$
()#';=#

1RWH %?

!!

805 of 1016
+HDGHU3!%
$!
-"AB"
&!()#;
&

!
$%
"

"

'$+4
!
+:4

'+4
!
+4

.+:4
!
)LJXUH7ULS+LVWRU\5HVXOWV'LVSOD\HGLQ1RWHSDG
7ULS+LVWRU\RQWKH0DUN9,
5HIHUWR'DWD+LVWRULDQ %A "0(
! > ?

$#

GRFXPHQW*(,DQG %?
$

7UHQG5HFRUGHUGRFXPHQW
!

!$!
*(+IRUPRUH

$
> 8>:
$
1!%
LQIRUPDWLRQ
!$!
4
% ! %.
$#
@ !

!
3

! $
?3

!

F
$

806 of 1016
&KDSWHU&RQWURO&RPPDQG
3URJUDPV
,QWURGXFWLRQ
&KDSWHUGHVFULEHVGLVSOD\ %?A(*
8 :
!
$
RQO\SURJUDPV

% $ ?A(
(
+
6HFWLRQ 3DJH
> >
13
> >
13
@" ;
132
> >
@ 131
;!13,#
A!@ 131
> > 134
% % 134
> >
139
>
A 139
@" % 13,,
F F 13,2
C! 13,2
! 13,2
A!

! 13,1

C
13,-

C
13,-
?
C 8
: 13,4
?
C 13,4
?
C 13,4
?
C .!
13,4
*(+$9ROXPH,2SHUDWRU¶V*XLGH &KDSWHU&RQWURO&RPPDQG3URJUDPV••

807 of 1016
'HPDQG'LVSOD\
7KLVSURJUDPLVXVHGRQ0DUN > >
A I@ I3$
#$

,99DQG9/0FRQWUROOHUV
!

! (
)RU0DUN9,UHIHUWRWKH&RQ
!$
!+
WURO6\VWHP7RROER[GRFXPHQ
WDWLRQ • $

• $
!
! 8:
•
$

!
•
&!
!
•

! !

• $
! > >

8
:RUNLQJZLWK)LOHV :
2QO\TXDOLILHGSHUVRQQHONQRZOHGJHDEOHDERXWWXUELQHFRQ
WURODQGSURWHFWLRQVKRXOGFUHDWHDQGH[HFXWHFRPPDQGV
7KHFRPPDQGVFDQDIIHFWWKHFRQWUROVWDWHDQGDFWLRQRIWKH
XQLWFRQWURO
%> >
$ ! H ! @3
>F3$
86WDUWLQJ'HPDQG'LVSOD\:%

! ! !> >
A "(00 0CA

;A "0(
!
$#
6WDUWLQJ'HPDQG'LVSOD\
% ! > >
+
• >!$
3
" 8
$
" :
• F @ "
8QLW7 'HPDQG'LVSOD\
• >F '(0$1' (QWHU

• F @ "
6WDUW 5XQ '(0$1'(;(

$#
'(0$1''0LVORFDWHGLQ > >
!
!

9:+,3
WKH)?5817,0(GLUHFWRU\ ! !

! % " 3
+
)RUGHVFULSWLRQDQGRSHUDWLRQ • 0HQX
8!:

$
3
RIWKHVHSURJUDPZLQGRZVVHH
> >

WKH'HPDQG'LVSOD\:LQGRZV
VHFWLRQLQWKLVFKDSWHU • 'DWD !
! %

A!
••&KDSWHU&RQWURO&RPPDQG3URJUDPV +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,

808 of 1016
&KDSWHU&,03/,&,7<'LVSOD\V
,QWURGXFWLRQ
7KH&,03/,&,7<+0,SURGXFW %(AC((%D?A(

PXVWEHLQVWDOOHGEHIRUHWKHVH #

F
DSSOLFDWLRQVFDQEHXVHG
3 "
%
!$
?A(! (AC((%D

*).SURYLGHVDGHWDLOHG (AC((%D!

!$ ! $

GHVFULSWLRQRIWKH&,03/,&,7< ! 8:.
,(AC((%D
GLVSOD\IHDWXUHV ! !$

(AC((%D! FC E
!

(A/8(AC((%D/: $
(AC((%D

!$! A "08A "0(!>:%(A/

! +
• 0$5.9B53
!$!%(

(AC((%D A
• (;70*5

(AC((%D

A 8 4:
• /2&.287
"! ! !%(8([WHQGHG$ODUP
&RPPDQGV$
:
• 6,/(1&(
! !%(8([WHQGHG$ODUP
&RPPDQGV$
:
% !
+
6HFWLRQ 3DJH
(AC((%D EF$) -3

A !
H>
-3
%
80
%
: -34

;
?A( -37
! -37
!.! -3,
!
;
-3,1
#
;

-32
!
(
;
-3-
#
-34
. $
>
-37
*(+$9ROXPH,2SHUDWRU¶V*XLGH &KDSWHU&,03/,&,7<'LVSOD\V••
809 of 1016
&,03/,&,7<$FWLYH;2EMHFWV
0LFURVRIW&RUSRUDWLRQ E

$) !

GHYHORSHG$FWLYH;FRQWUROV ! E%

%
RULJLQDOO\WRVXSSRUWWKH $ !
$)
!
FUHDWLRQRI,QWHUQHWHQDEOHG !
!
$)
DSSOLFDWLRQV
;
?A(
! (AC((%D 3!
$
(!
8
0: E$) +A !
H>
%
% $$

0DUN99/0 0DQXDO6\QFKURQL]LQJ'LVSOD\
%$
8&!:

* ! %
! !$
* ! 3H!

2/(LV³2EMHFW/LQNLQJDQG ;A "0 0CA A !
F$) 8 FC$) :
(PEHGGLQJ´VHHWKH*ORVVDU\ (AC((%D?A(
!

IRUDPRUHGHWDLOHGGHILQLWLRQ H 8;!-3,:%$)

$! ;A "0 0CA
$) !

,4?H;A "0( ,?H
%A !
H>
! $! (AC((%D

%$ ! $) ! %(

%$) ! ! $ (AC((%D
?A(3URSHUWLHV
$# $) % $ $$

#$
"44

!
!%"
%
6FRSH
.H4,
=

44
%

%UHDNHU
='"!=

44
%
%XWWRQV

9 &

$!"!
< 44 %

!!

9DOXHV $ 44 %

3HUPLVVLYHV
)LJXUH0DQXDO6\QF2EMHFW8VHGLQ&,03/,&,7<+0,
1RWH@!! / "

/ "%$!
$#

$! +
• &RPPDQG $ "

• 'RQH#
$#
$ "

••&KDSWHU&,03/,&,7<'LVSOD\V +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
810 of 1016
0DUN99/0 7ULJJHUHG3ORW9DOYH7UDYHO
%%
! E$) 3
!$ % $ $

! %!$ $ " !!
!$
8!

:
C" A !
H>
%
! (AC((%D

8;!-3:D!! $) $

! %

$
(AC((%D?A(3URSHUWLHV
$#8;!-32:
!!!
"
&$
"$ 3"&!"

"
!

" %^
"
!% "
!%+
+,:
!
3

!

-"!
"
!

!
4
"%!

!
!
!

)LJXUH,QDFWLYH7ULJJHUHG3ORW6FUHHQ
811 of 1016
&RQILJXULQJ2EMHFW3URSHUWLHV
% # $!%

8;!
-32:
#"%","
$4 #

"
# "
!%

%
! "^!"
2 !
!
$!
"
++,:

# %!"4!&

9% $!

%

#% $"
"
% %!$
% &!$$" &

# %$"
# !" "
" !%$$
%
$
$
"%!
$!
%$! "
!
)LJXUH,QDFWLYH7ULJJHUHG3ORW6FUHHQ6KRZLQJ9HUVLRQ:LQGRZ
812 of 1016
$ODUP)LOWHULQJLQ+0,6HUYHUV
*).SURYLGHVDGHWDLOHG B

!(AC((%D(>
GHVFULSWLRQRIWKH&,03/,&,7<

0 8 FE
:D!

GLVSOD\IHDWXUHV

!$ !
!
$#
%
;
!

% $$ +
• 0 !.!%#
! !
$

%!$ # /F

•
! 8#
> C A!?:
%!

?A(!
+
, !!
!!
2 !

$OOSURFHGXUHVPXVWEHIROORZHGDQGFRPSOHWHGLQWKHRUGHU
SUHVHQWHG
,WLVJRRGSUDFWLFHWRFKHFNRIIHDFKSURFHGXUHZKHQ\RX
FRPSOHWHLW)RUWKLVSXUSRVHWKLVFKDSWHULQFOXGHVFKHFNER[HV
QH[WWRHDFKSURFHGXUHKHDGLQJ
1RWH%! &! ! ""

(AC((%D
! @"$
! .!
! !
>! ;K3,,7

&RQILJXULQJ8VHUV
! !
" (AC((%D?A()
(AC((%D?A(!
$! ! $!+

6HFXULW\±! $ 3DVVZRU( !
$
! (AC((%D?A() ! !
$ (>
5ROHVDQG3ULYLOHJHV±!

(AC((%D
?A()
%
!
! ( !
"
!!

9LHZRI5HVRXUFHV±!* $
!

!! !*
!*$ODUP
9LHZHU
¨$OOSURFHGXUHVLQWKLV Ø7RFRQILJXUH8VHUVIRUWKH&,03/,&,7<+0,SURMHFW
VHFWLRQZHUHFRPSOHWHG
, F ) (AC((%D@"$8 4
VXFFHVVIXOO\
:
( @"$

! !

8VHUV3
$

813 of 1016
7%"
!
"
)7) )'C
""
% !
#
$"
!
"
%
!
%
! 2
2 F 1HZ8VHU

$# !
23(5$725
'"$&

8VHU,'$ 2.
814 of 1016
1 F 8VHU3URSHUWLHV
$# !23(5$725
2SHUDWRU 8VHUQDPH
#
'"$&

8VHU1DPH
$ 2.
7KH5HVRXUFHVSURSHUWLHVOHW -
5HVRXUFHV $
!%, !%7

\RXGHILQHWKHUHVRXUFHVIRU
ZKLFKWKHXVHUFDQYLHZ
DODUPV #

"

!

'!!

3

%
$YDLODEOH $
$GG
1RWH.! $ $ * ;#

! 8VHU !

%!$%,8%,:
7 .! ,
815 of 1016
4 > 5ROH3URSHUWLHV !F.%F. $

#
"

816 of 1016
&RQILJXULQJ5HVRXUFHV
¨$OOSURFHGXUHVLQWKLV Ø7RFRQILJXUH5HVRXUFHVIRUWKH&,03/,&,7<+0,SURMHFW
VXFFHVVIXOO\ , ( @"$
! !

5HVRXUFHV3
!$

#
1HZ5HVRXUFH7

"2. !$

'"$&

5HVRXUFH,'$ 2.
817 of 1016
2 5HVRXUFH'HILQLWLRQ%, !$

'"'HVFULSWLRQ

"
8VHUV
!5HVRXUFH
'!!8VHUVIRUWKLV5HVRXUFH3
%
$YDLODEOH8VHUV 3$ $GG

"
8VHUV %$
5HVRXUFH
1 ! 2 !%, %7%,

%7 !$

818 of 1016
&RQILJXULQJ$ODUP)LOWHUV
¨$OOSURFHGXUHVLQWKLV Ø7RFRQILJXUH$ODUP)LOWHUVIRUWKH&,03/,&,7<+0,SURMHFW
VXFFHVVIXOO\ , ( @"$
! $GYDQFHG

$ODUP
&ODVVHV $

#
$ODUP&ODVV ',$* $

'"
#
'$2UGHU
$"%$

$% !$"

'$ &$2UGHU 3$$$
$"
# "
"" "

819 of 1016
2 !

!$

$&$

!
$ODUP&ODVV! ! !

" !

$&
", < $
820 of 1016
1 ( @"$
$

6FUHHQV$ODUPFLP
8
):

$ODUPFLP
+#
,#
821 of 1016
- .
"
(GLW
$ODUPV
F)UDPH&RQWDLQHU ! $

#
1RWH(AC((%D?A(! 8 :

$ !
% $
!

!%
$ $
"$!

822 of 1016
4 .
"
&,03/,&,7<$09&RQWURO2EMHFW
3URSHUWLHV ! $
%
&,03/,&,7<$09
&RQWURO3URSHUWLHV
$#
+#
,#
823 of 1016
9 ) $
"$GG3URMHFW $

# $
6HOHFW3URMHFW
!
!
"

2

!$%
!!!
.

3

$"2
&$$

# $"2%$!"4

!&

2.'$"2!

"
$
3URMHFWV
7 (3URMHFWV $!$

3
"
) $/$50B),/7(5%

3URMHFW6HWWLQJV
$# $
$ODUPVHWXS
$

$ODUP
VHWXS!
$"
3URMHFWV
!
'"
824 of 1016
3URMHFW!
6HWXS
!
# ""
$
3$
!!&
"2
5 F

0
"6HWXS $
%
$ODUP6HWXS
$#

825 of 1016
%HWVXUHWRLQFOXGHWKH³´ , 6HWXS
',$*B*7 $

V\PERODWWKHEHJLQQLQJRI
WKH6HWXSQDPH7KLVPDNHV
LWDFFHVVLEOHWRDOOXVHUV
:LWKRXWWKHV\PEROLWFDQEH
DFFHVVHGRQO\E\WKHXVHU
DFFRXQWWKDWFUHDWHGLW
'"6HWXS

'$0RGLI\6HWXS $

!
"

&
,,
&ODVVHV $
',$*
$#

2.
826 of 1016
,
5HVRXUFHV $%
7
$# 2. !
$ODUP6HWXSV
$# $

,2
"6DYH !
,1;
!8 , ,2: !
827 of 1016
([DPSOHVRI6FUHHQVIRU)LOWHUHG$ODUPV
!

! !
;!-31 !-34 #

)LJXUH6FUHHQIRU*DV7XUELQH7'LVSOD\LQJ$ODUP2QO\IRU7
1RWH%

$

828 of 1016
)LJXUH6FUHHQIRU*DV7XUELQH7'LVSOD\LQJ$ODUP2QO\IRU7
829 of 1016
)LJXUH6FUHHQIRU$OO'LVSOD\LQJ$ODUPVIRU$OO
&XUUHQWO\,PSOHPHQWHG)LOWHUV

$
!+
• P>(Q%,8%F%7:
• P.FQ%,8%F%7:
• PEQ%,8%F%7:PEKQ%,8%F%7:
• PCC
• PD%A
• P/F
830 of 1016
([WHQGHG$ODUP&RPPDQGV
7RGLVSOD\DODUPVDVWDQG ! %( ! (AC((%D
0
DORQH$ODUP9LHZHULV !$
%
! # 78C"
":
HPEHGGHGLQWRD&,03/,&,7< ! $! (AC((%D
0
VFUHHQ
6LOHQFH/RFN 8QORFN$! !!
! !!

$ $!
Ø7RHGLWFXVWRPDODUPIHDWXUHVIRUWKH6LOHQFH/RFNDQG8QORFN
EXWWRQV
, . 3
" $ "! $ODUP
!
$

&,03/,&,7<$09&RQWURO2EMHFW 3URSHUWLHV
%
A " %XWWRQV $

!$

# !
"
=""
"

#
$$ $! "
=
($ $ !&

%
!% # !%
$$ $! J
""

# !
" $
/RFN8QORFN
6LOHQFH

!%%
!
"
%
$

2 ( %XWWRQ&DSWLRQ $!
!$

831 of 1016

%
%
""
!

! $! +

5HTXLUHGGDWDDQGGDWDIRUPDW • /2&.287! #5
FDQEHYLHZHGIURPWKH'26
70 >0-'5]@]@]!!;!"@]%)@_!`
FRPPDQGOLQHE\W\SLQJ
6,/(1&(DQG/2&.287 70 > +a
a!a%!_!`
-970 >5 :a
a!a%!_!`
• 6,/(1&(! #+
#)79 a
_!`
832 of 1016
&KDSWHU&,03/,&,7<3URMHFW
&RQILJXUDWLRQ
,QWURGXFWLRQ
7KH&,03/,&,7<+0,SURGXFW % $! !(AC((%D) !
PXVWEHLQVWDOOHGEHIRUHWKHVH !$
?A(! %!

DSSOLFDWLRQVFDQEHXVHG !!
""
(AC((%D)
>! ;K3,,7
(AC((%D?A(!
$!
) +

3URMHFW1DPHJ 8#
695:
6XE'LUHFWRU\JA! $ "2
3DWKJ.56 "2
*HQHUDORSWLRQVJ/
#

3URWRFROVJA "06! 8 %(A/:
F $

%) $# ! (AC((%D@"$8
;!43:
% H
+
6HFWLRQ 3DJH
@"$43
F ) 432

A 431
!431

43-

434
(
437
#

A 43,
>/# 43,
>/
43,

A$! > ( 43,,
FC
8F: 43,
*(+$9ROXPH,2SHUDWRU¶V*XLGH &KDSWHU&,03/,&,7<3URMHFW&RQILJXUDWLRQ••
833 of 1016
8VLQJ:RUNEHQFK
'RFXPHQW*).SURYLGHV %(AC((%D?A(@"$
! !
GHWDLODERXWXVLQJ:RUNEHQFK H ) (
A @ #

! ! ! .
$ODUP)LOWHULQJLQ+0,6HUYHUV8 -:#
@"$

Ø7RRSHQ:RUNEHQFK
,
"6WDUW @ "$

3URJUDPV (AC((%D?A( @"$
2U
w
%
%56 "2
;!43, )LOH! 1HZ3URMHFW;!43
3URMHFW!
# ) 3URSHUWLHV
)LJXUH:RUNEHQFK0HQX )LJXUH:RUNEHQFK0HQX
6KRZLQJ6HOHFWLRQVIRU 6KRZLQJ6HOHFWLRQVIRU
6WDUWLQJD1HZ3URMHFW ([DPLQLQJ3URMHFW3URSHUWLHV
••&KDSWHU&,03/,&,7<3URMHFW&RQILJXUDWLRQ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9RO,
834 of 1016
2SHQLQJD3URMHFW
(AC((%D?A( ) $
$

Ø7RRSHQD&,03/,&,7<SURMHFWWKURXJKWKH:LQGRZV6WDUWPHQX
,
"6WDUW @ "$

3URJUDPV &,03/,&,7<+0, :RUNEHQFK
$
"(AC((%D@"$
2 ; :RUNEHQFK
2SHQ )LOH!
1
) !
Ø7RRSHQD&,03/,&,7<SURMHFWIURPWKH:LQGRZV)LOH([SORUHU
, F;
#

F %56"2
2 >!$
3
" %

Ø7RRSHQD&,03/,&,7<SURMHFWIURPWKH6WDUW0HQX
,
"6WDUW @ "$

'RFXPHQWV
2
" %

835 of 1016
6LJQDO0DQDJHU
7KHSURJUDPFDQEHIRXQGRQ (A "(00 0CA
A !
WKH+0,LQ (AC((%D
!$
%%(! $

*?(;(&?&6'%8WLO(;( !$! !
! *>
> $!
$ %(
;A "(0A "0 A "0CA

A !
!$

> $ 8>/: ! !
(AC((%D A
> $
!!3

#
%(
; A "0(
! ?A(
6HWXS
Ø7RHQDEOHDODUPVIRU&,03/,&,7<
, )

1HZ3URMHFW
$# $

&$
" !
#
!
#
#
""
(AC((%D) !! ! (AC((%D

!
% $

$
) . &,03/,&,7<%DVH6\VWHP8VHU¶V0DQXDO*).
) !
836 of 1016
@
A

(AC((%D
! (AC((%D !

;#

! %, !
!
(AC((%D (AC((%D!$
%,
0$5.9B53LV7&,0%IXQFWLRQ ;
A !
! !
WKDWFROOHFWVGDWDIURPD $ A.K0Q. ;#

%,
WXUELQHXVLQJ7&,DQGIRUZDUGV !
!
!
+
WKHLQIRUPDWLRQWRWKH
&,03/,&,7<3RLQW0DQDJHU • %,Q%(A ! *!
• %,Q>% ! *!
• %,Q0C(> /

! ?A(!

! !
6LJQDOV
&6'%LV&RQWURO6\VWHP
A
> > $ ! *
'DWDEDVH >/
$!

!

$! +
6LJQDO
DWWULEXWH 'HVFULSWLRQ
9 # J

!/&
'" )7) )'C""$
"!
$

"
"%$

-
-
.
#
%" 3 3!3"
($7 ($ %$
J

7&7 7& %$

0%%
0%%
$ #=&$$

!

9"
%!
" %$
J

# ! # !%

# 0"
"%!
%$

'" "%$

# J

D! !

%
@ C

! # !

H
!
837 of 1016
$ODUPV
7KH6LJQDO0DQDJHUFDQDOVR (AC((%D

EHXVHGWRFRQILJXUHDODUPVIRU !3 !%
A $! !
(;DQG(;H[FLWHUV
A "0A "0CA A "0( !$

( !
! (>+
$ODUPXVH $ODUP,'IRUFRQILJXUDWLRQ

% ]@1

% ]@1
( !
"
11 (07#
#<%
11 #0

11 9'
1Q
$!" "! $
11'$
)7) )'C
! "
4&$!%%
"
%$

@
A !

!

+
• (

! (AC((%D
!
• (

! #

!
• %

+
&ODVV 'HILQLWLRQ

)

(07 ( !

#0 #<%
9'
F,>

&
&RQILJXULQJ([FLWHU$ODUPV
#
!
.56F,:::'
% E#
!
$ E# %#

!
!

Ø7RFRQILJXUHDODUPVIRUFRQWUROOHUV
w
$ODUPV $FWLRQ!

A !

?
C O d
e
838 of 1016
Ø7RFRQILJXUHDODUPVIRU(;H[FLWHUV
,
(;$ODUPV $FWLRQ!

A !#
.56F,:::'

([FLWHU)DXOW&RGH
$#
A "

!$

A !
!

! !

# $#((AC((%D !

!

! !
(AC((%D

!
'"
3RLQW,'
# $

$%
&$

%$

" !$
'$
"
&$

!'$

$!
2 !
# !

! # ; !
$#
1 @

'RQH
839 of 1016
,PSRUWLQJ6LJQDOV
@
A

Ø7RDGGVLJQDOVWRWKH6LJQDO0DQDJHUOLVW
,
1HZ )LOH!

$#

!

>
>
'"&$& !!

%

!
%$#""!5
•

13&$$$
8
%$
•
b3&$$$
8
%$
#
% $

"$
&

%$
"!""
$$$%
# 8QLW%
%

&$" !3!!

#
840 of 1016
Ø7RLQGLYLGXDOO\LPSRUWVLJQDOVLQGLYLGXDOO\LQWR&,03/,&,7<
w (
A

Ø7RLPSRUWDOOVLJQDOVDWRQFHLQWR&,03/,&,7<
, (
A
6HOHFW$OO (GLW!

,PSRUW $FWLRQ!
%

$#
!
%

(AC((%D) 8;!434:
)LJXUH([DPSOHRI&,03/,&,7<3URMHFW6HOHFWLRQ'LDORJ%R[
D! !

(AC((%D $

Ø7RSRSXODWHWKH6LJQDO0DQDJHU¶VGLVSOD\HGOLVWRIVLJQDOVZLWKWKH
VLJQDOVUHIHUHQFHGLQDVHWRIVFUHHQV
,
0DWFK $FWLRQ!

A

!
> >

(AC((%D
$ ! !$!

841 of 1016
([WHUQDO$ODUP0DQDJHU
%#

A (AC((%D/
8(A/:( !
!$

(AC((%D
A

;A "(0 0(

$
;A "0

$

$
A "0(

!
$#

8 ?3412:
6'%([FKDQJH
% > $ 8>/:#
$
A "0(
(
!
(AC((%D
$
# A "0(>/
. (3,95 $! >/#
6'%8WLOLWLHV
7KH6'%8WLOLWLHVPXVWUXQRQ %>/

$
A "0(
%
WKH3&WKDWLVWKH&,03/,&,7< !
(AC((%D
$ #
6HUYHU A "0(>/%>/
! !!

(AC((%D?A() +
•
>/ !$
•
$

1
3 #
$ ! !
•
V
1
% 5S39
$

8C:
•
>/ (AC((%D?A()

. (3,- $! >/

842 of 1016
0RGEXV'DWD,QWHUIDFH
7KLVXWLOLW\LVXVHGZLWK0DUN %?A( A$!
8;!439:%
,9DQG9,FRQWUROOHUV &! ! 8 A$! : $ !
!
! $
&! @ ?A( !$
0RGEXVLVDQLQGXVWU\VWDQGDUG
!$
/ .32

FRPPXQLFDWLRQOLQNXVHGE\WKH

" !
+0,WRSURYLGHWKHFXUUHQW
YDOXHRIYDULDEOHVIURPWKH &LP0RG !
$(!
8
0:
+0,WRDQ\V\VWHPWKDW (AC((%D) ( ! ! $ (AC((%D
UHTXHVWVLWYLDWKH0RGEXVOLQN $ %(A$!
%
A$!

()#
)
' )
) ' ) )0 !
#
)7) )'C
#

c
7
)LJXUH'DWD)ORZIURP&RQWUROOHUVLQ0RGEXV6ODYH0RGH
&LP0RGB/

!
8 )0;7F
!
%( A$!
(AC((%D
8 )07#'%

(

. ! (3,-,9 $! !A
AQC
843 of 1016
2/(IRU3URFHVV&RQWUROV23&
23&ZDVGHYHORSHGE\WKH F ! $ ?A(
23&)RXQGDWLRQDQGHQGRUVHG ('F( $ A FC

E\0LFURVRIW
(AC((%DF&OLHQW (AC((%D!
F%F
!
(AC((%D

(AC((%D !+
•
!
F
•

• %
•
$ !(AC((%D

. ; !! ;K3,,7,F

F6HUYHUV
$
!
$ F
%(AC((%D?A(F6HUYHU
3$ !3 (AC((%D?A(
)
. ; !! ;K3,49-F
844 of 1016
6HFWLRQ 3DJH
?A(;! %!$
3,
(AC((%D?A(! ;! 31
+0,)XQFWLRQVIRU*(7XUELQH&RQWUROOHUV
*%!$
?A(! $ %(%(A/
%!$

! >%
$

!

$
>%.FB( !$
;!
!(AC((%D!

0DUN 0DUN 0DUN 0DUN

+0,)XQFWLRQ $SSOLFDWLRQ1RWHV
,9 9 9 /0 9,
'DWDDQG&RQWURO'LVSOD\V
!
" ü ü ü ü ' "$
%)
7. ü ü ü ' %%)

" ü ü ü ' %%)
4
" ü ü ü '#%)

" ü ü ü '#%)

" ü ü ü ' %%)

!2

" ü ü ü ' %%)

" ü ü ' %%)
'"(
ü ü ü "
%)
&,03/,&,7<$GGRQV
)7) )'C=! ü ü ü ü
# ü ü ü ü #=$%)
ü ü ü ü

"
" ü ü ü ü
#$8
" ü ü ü )" !&$ )7) )'C%)

ü ü
'! ü ü
*(+$9ROXPH,2SHUDWRU¶V*XLGH $SSHQGL[$+0,)XQFWLRQ5HIHUHQFH••$
845 of 1016
0DUN 0DUN 0DUN 0DUN
,9 9 9 /0 9,
8QLW&RPPXQLFDWLRQV
# ü ü
#. ü 9
)
# ü 9

)
' )!
d
ü ü 9
)
ü
8QLW&RPPXQLFDWLRQVFRQWLQXHG

ü ü ü ü

ü ü ü ' %%)

ü ü ü ü
#0
ü ü ü ü
( !7
ü ü
&$#'#
#=-
/$ ü
8QLW&RQILJXUDWLRQ7RROV
#<! ü ü ü ' %%)
#< " ü ü ü ' %%)
#< ü ü ü ' %%)
# ü ü ü ' %%)
' " ü ü
"" !& !
ü ü ü ' %%)
.&& ! ü ü ' %)
ü ü
!)!% ü ü ü '#%)
7
ü ü ü ü
.) ü
7= %'
ü
)/0 %' ü ü ü ' %%)
7LPH6\QFKURQL]LQJ
'
. ü ü ü ü 9'%)
($
)) ü ü ü ü 0"
# ü ü ü ü 0"
9' ü ü ü ü 0"
$••$SSHQGL[$+0,)XQFWLRQ5HIHUHQFH +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
846 of 1016
0DUN 0DUN 0DUN 0DUN
,9 9 9 /0 9,
2WKHU)XQFWLRQV
ü ü ü ü
(
ü ü ü ü
'"(
ü ü ü "=
e(
%)
9 ü ü ü ü ' %%)
($4
"! ü ü ü ' '!!%)

" ü ü ü
2SWLRQDO)XQFWLRQV
' )!
# ü ü ü ü
' )!

ü ü ü . !%
# ü ü ü ü
&= ü ü ü ü
% ü ü ü #"
:HE'LDJQRVWLF)XQFWLRQV
!
" ü ü ü
7.
" ü ü

" ü ü ü ü

" ü ü
()7.
ü ü ü ü
G(0- ü ü ü
'LDJQRVWLF3URJUDPV
! !. % ü ü ü ü
847 of 1016
&,03/,&,7<+0,6XSSRUWHG)XQFWLRQV
% !$
?A(! ! (AC((%D?A(%

$

!
'RQRWORDGXQVXSSRUWHG&,03/,&,7<IXQFWLRQVRQWKH+0,
IRU63(('7521,&7XUELQHFRQWUROOHUV
$OWKRXJKWKH&,03/,&,7<+0,IXQFWLRQOLVWHGEHORZZLOOUXQ
RQWKH+0,IRU63(('7521,&7XUELQHFRQWUROOHUVWKH\DUH
QRWQHFHVVDULO\VXSSRUWHGE\*(3RZHU6\VWHPVIRUXVHRQWKH
+0,3OHDVHFKHFNZLWKD*(3RZHU6\VWHPVUHSUHVHQWDWLYHIRU
DYDLODELOLW\
2SWLRQVQRWOLVWHGDVVXSSRUWHGLQWKHIROORZLQJWDEOHKDYHQRW
EHHQTXDOLILHG
(DUOLHVW
6XSSRUWHG &,03/,&,7<)XQFWLRQ 6XSSRUWHG $SSOLFDWLRQ1RWHV
9HUVLRQ
! !4

!
=
(
f,#g & ü )F & 2
f,#g =
ü
=
%""

"
7 0=
# G#

#

&$ &
$!

%()
(
8 "$
!
8
(
'!
)F 2%&!
()% 9 )&$. 9
f,#g ()!

ü
<
"
!

<!
f,#g !

ü
!
' /)
B:+#, 0
# 3%3'
"" HB:f^g4gf^^
B:+#, 0 #
# 3%3'
"" HB:f^g4gf^^
B:+#^ 0"
!
f,#g ü #! % "$4"
& G &
$••$SSHQGL[$+0,)XQFWLRQ5HIHUHQFH +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
848 of 1016
(DUOLHVW
6XSSRUWHG &,03/,&,7<)XQFWLRQ 6XSSRUWHG $SSOLFDWLRQ1RWHV
9HUVLRQ
f,#g =! ü &

)7) )'C

!
$

B:+#, '!
ü "4"!
%"

f,#g 4'!

ü )F 2%&!
"
4!"!"
" "!%"
f,#g #
h:d7 . '
ü &7 %
#!! "
!!
""
B:+#, #0 2
d ü
!!!""$!
"! 2
# 9&%
%#
#
#
&$
()!

"
'0" '

$$"!%
f,#g G & ü #! )7) )'C()!& "
G & #!

&
!!& &

f,#g FC
ü F 2%" " 4!
849 of 1016
,QWURGXFWLRQ
% !$

?A(

$#+?
C > 8;!/3,:

+0, +0, 7RROER[

"
"
-(
]@
c ]#@ ]'@

( !7

,2 ,2 ,2
=
)LJXUH%7KUHH7\SHVRI$ODUPV*HQHUDWHGE\WKH0DUN9,&RQWUROOHU
% #

!$

! ?A(( !
! ?A( ! !$ !
1RWH% #

A "0(

? !

A "(0A "0 A "0CA

# !

%
$# !
%
+
6HFWLRQ 3DJH
?
C
/3

/3
8 ?
:
> ;
/3
>
/32
*(+$9ROXPH,2SHUDWRU¶V*XLGH $SSHQGL[%$ODUP2YHUYLHZ••%
850 of 1016
+ROG/LVW$ODUPV6WHDP7XUELQH2QO\
5HIHUWRWKH+ROG/LVWVHFWLRQLQ ?
C

!
&KDSWHU
%! ?
C

8
:%
! $
! !$ !

! &!F

&!

3URFHVV$ODUPV

!$ $

$ ?A(%

!
$ ('F$ &!%!
!

&!!
$#

$ /

!$

$#8A "0(:
$! %
$$
&! $ !
!
('F
$

&!!(
%A.
!

!!

!
"
C " "
('F$ !

/
!

%

$
!
! !

.%>!
!
!
, $

$

%

!
$#!
%
!
C $!
$
$

!

! !
$ .%QD

3URFHVVDQG+ROG$ODUP'DWD)ORZ

7KHRSHUDWRURUWKHFRQWUROOHU ?

&!!
FDQWDNHDFWLRQEDVHGRQ

SURFHVVDODUPV &!!.
$
>?
(AC((%D?A(?
&!!

$
0
F ?A(!
"
. C"

" $ " >?
&!!% !

&!!
!
$ "
8
;!/3:
?

$! &!!

$
"$! $
%••$SSHQGL[%$ODUP2YHUYLHZ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
851 of 1016
0DUN9,&RQWUROOHU 8'+ 0DUN9,+0,
)" # +

"

&

#

4
!
)" # 0" !

4
7 ) ! 4

' 47
4-
) 40!%( !7

)LJXUH%*HQHUDWLQJ3URFHVV$ODUPV
'LDJQRVWLF$ODUPV
>
!$&! $
!
$ >

!

&!"
;

!
&!

$#8A "0(:
?A(

>

%
('F$

! 0A(
!$ %
#

3
$

$#8A "0(:
>
$
$#$
$

" !$!
!

('F$ $

$
$#
*(+$9ROXPH,2SHUDWRU¶V*XLGH $SSHQGL[%$ODUP2YHUYLHZ••%
852 of 1016
*ORVVDU\
$FWLYH;
E
$A !

!

@ E! " &! !!$!
$ $
(

! $!

E

!
A ( #
I " $
" $

"!
$FWLYH;FRQWURO

8$) :! E
$
E

$ !

#! $ $$

E

!
!
660!
/ L E
!
@

DODUP
&! "
$

$ODUP9LHZHU

(AC((%D8 FE
:

$09

0
DSSOLFDWLRQ

3 !

!

! !
!

$5&1(7
.!! B " CB!

$> .B%
8 # :

"8 " $ :
-A?H!
"
*(+$9ROXPH,2SHUDWRU¶V*XLGH *ORVVDU\••
853 of 1016
%DODQFHRI3ODQW%23

&! !$ $

ERDUG
$ ! $ !
!
%RROHDQ
>
# %!;

EUHDNHUFLUFXLWEUHDNHU
$
" $ "! !

!
"
$ "! ! $
! !
&!
% !$
*! 8:
&LP(GLW
$) 3
(AC((%D?A( !
! 0 (

&,03/,&,7<+0,
3$ ; !! ! $

"
&! &!
FLPSURM
%&!!$ (AC((%D?A() 8.56 "2:%
) ! @"$8%:
!$
&LP9LHZ

! (AC((%D?A(!

&!
# $)
( %
!
!

!

! ! @

FOLHQWVHUYHU
! ! "&!
! ;#
"
&! !
FRPPDQGOLQH
%
!
! $ ! $
% ! # 3$ ! A3>F

! 8(:! @
FRQILJXUH

$ "
$

)!$

••*ORVVDU\ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
854 of 1016
FRQWUROV\VWHP
&! !
)! ! !

&!A@
$
&!
!
&!A@ !&!

!$!
#
&RQWURO6\VWHP6ROXWLRQV
! >
;#

!
%
$#>/#
&RQWURO6\VWHP7RROER[
WRROER[
&5&

.! " ! !

"
FURVVSORW
>
$

E3D

H
&6'%

> $ ! !$

!

!

&6)

; " ! "
!
%@(BE $
! 2A?H
'!
% !$
*$ "!! 8:8

&!:
GDWDGLFWLRQDU\

$
$ %

!$ $!

$
$

!
3 ! H ; ?A(

$! ! 3

$
#
8$
:

8 '! !:% ! >
>
-9)''' $ ?A( ! 3

'&6
> $!
!

!
$

&!
GHDGEDQG
.
!
$
!
! ! %? ! $

!
855 of 1016
'HPDQG'LVSOD\
?A(!
!

!$
!
( ! !

!
GHYLFH
! $

'HYFRP

! $$
(AC((%D?A( A $
G\QDPLF
$! H
(*'

$
> "
!$
>
!># 8 :
(WKHUQHW
CB ,, $ ! !
"!
'
( !
'

( !%'( ('F
(72

$E#>
&! 8>: (

HYHQW
>
$ !

(;
#
( !

!

! !

IDXOWFRGH

?A(

!
ILUPZDUH
#! $

!

! .FA;

ILOWHU

IRUFLQJ

!

!

! $
" ('F

IUDPHUDWH
/ !

(

! 3! 3
! !

856 of 1016
*60
(!
A
3

>%

!

B

!
!
&! $ >&!
*OREDO7LPH6RXUFH*76
@
!
%8
%:! "

JUDSKLFDOXVHULQWHUIDFH*8,
$ ! ! $
(
! ! " ;

$
E#
# 3$ $

A A @ B(E
E@
KHDGHU
%# !
!

$

! !!

!
+LVWRULDQ

'3$

!#
( $3
!

!$

!3

+0,
?! 3A ( %?A( @ B%3$
!$
!#

&! %?A(!
(AC((%D ! ?
%

?
+56*
? . %!# ! !$

LFRQ

! 8

:

! @
" !
$

,&6
(
%($ !

$!

LQLWLDOL]H

!8 ! !: $
!

857 of 1016
,21HW
%A "0(('F ! "
/$1
C
"8! :
CB

$!

ORJLFDO
!'
! /

0DUN,9
>%.FB( !$
!,572%

!
! 8%A.:
!
3

0DUN9

3
>%.FB( !$
!,55,

$

# %A.
&! >F3$

! ! B%3$ (AC((%D?A(
0DUN9/0
>%.FB( !$
!,55-

! >C 8>C:

$
&! ! B%3$ (AC((%D?A(
0DUN9,
0A3$ >%.FB( !$

$

#
%A.
&! ! B%3$ (AC((%D?A(

%
$#
PHQX
8 :
!
$
0RGEXV

!

$!
A!
$ C !
QHWZRUN
!
" !

REMHFW
8 :
$!

!

%
! !

$
($) 3 #
$)

3 $ ! !

2&;
FC!
!
$ $
@ E8A *#

:$ " $
FE
858 of 1016
2/(
8!
:F$)
" $!
!
$A ( $
!
$)

"$

$$)

"

! FC$!
@
23&
FC
%F 3
$ !A *
FC'FA
%
F "
$
$
$ ! '

' $!'

SDQHO
% &!
$
!
SF
$$ SHUVRQDOFRPSXWHU
3'+
3ODQW'DWD+LJKZD\
SHUPLVVLYHV

3ODQW'DWD+LJKZD\3'+
! "
" ? ?A(?A(0
"
3/&
$

% 8

:

! 8
:! !

SORW
% $

!

SRLQW
/ ! $

SURGXFWFRGHUXQWLPH

*;

8: #! $

859 of 1016
UHDFWLYHFDSDELOLW\
% ) $ $

!! 0
!%
! $

!
!
UHERRW
.

!
UHOD\ODGGHUGLDJUDP5/'

!

!

UHVRXUFHV

" !.! 8 "
":
" ! .!
!

(AC((%D $!

!
!
UXQWLPH
SURGXFWFRGH
6HTXHQFHRI(YHQWV62(
3
! "!
!

A !$
!
! ,

VHUYHU

"
$

3$ " 0
VHWSRLQW
0
!
$
! !

!
VLJQDO
/ ! $

6LPSOH[
F &!

('F
!

62(
6HTXHQFHRI(YHQWV
6573
.&! %
!

! $ !$
?A(
860 of 1016
6WDJHOLQN
.B%3$ !
"!$

V\QFKURVFRSH
( ! H
WDJ
( !
7&($
>%F/ 8%:

*
T,O! 3 ! (
% %$ ! T,O
TEOTDO TUO%$

!

!
H % ! !
%8
,:$
(FB% T.,O*>%$ %%

%!$%/ 8>%%: %
!
!

7&,
%!$
( %3!
" ?A(
!$

7&3,3
!

3 "
(
B(E $! !

%

( ! ! !
3

WLPHWDJ
(

705
%
A!
.! % ! !

('F !
$

$
! !

WRROER[&RQWURO6\VWHP7RROER[
@ 3$ " ! ! A "0(

#
WUHQG
%3$

!
$

? ?A(
%
$#
WULJJHU
%
,,
&!
861 of 1016
8QLW'DWD+LJKZD\8'+
A "0(
C(EC

&! ?A( !
"
87&

%
3
XWLOLW\

"!!

!

H

# !
ZHEEURZVHU
! A ( #
B B

$ "
:LQGRZV17
23$ A 2743$
$
:RUNEHQFK
(AC((%D?A( ! ! H
(AC((%D) !

862 of 1016
,QGH[ %
/

,39-37-3-
$ 8SULQWHGZLULQJERDUGV:
/
43-/3
/F8%DODQFHRI3ODQW:
$ "8FLUFXLWEUHDNHU:
$
E$) ,35-3,-3-34313- &
A !
H>
-3-343,
,3-,37-3,9
,34313-
,3-232231-3,9
%
-3-34-393,
(AC((%D

323413,4
E$) ,35-3,-3-34313-

0 ,34323413,4-37-3431/3
?A(,32,3732-3,-3-34-37-3,-3,1-3,9
0 ,3-,343
43,J43243,43,3,313-/3
#
32-3,-34
)-3,443,43
C"3213,9-34-39/3
0 ,3-,34331
C"! -3,-34-39
! $ "-3-32

32-3,-34-39

3,3,

"32-34-39/3

23423,,23,-13,2J13,--39

-37
43943,,
!-3,1
! ,32,34,3743143,331

0 ,34323413,4-37-3431/3
,3923,243,43,,
A0-3,7-34
A$!,3943,,3J31
0 ,3-,343
! ,32,353113913,213,113,4-3,
#
32-3,-34
-32J-34-37-3,-3,143431J439
C"3213,9-34-39/3

-3,1
C"! -3,-34-39
> >
13,2

32-3,-34-39
!-3,

"32-34-39/3
!-37

,32,31,34323-23513,-13,4-3,-37

> $ 8>/:13,943143-
-3443143-43443,31/3

,32,34,3513,

323432/32

; 8;:3

C
3413,-

! ,37

0 ,34323413,4-37-3431/3

%
$#8
$#:,3,39,373-

-3,4-3
2323523,21343,/3,J/32
A0-3,7-34
%.,3,3723,232
43443,3/3,/32

#
32-3,-34
A "(0,3,,321313,213,--3743143,
C"3213,9-34-39/3
43,,3,3/3,
C"! -3,-34-39
A "0,3,J,32,39,373-3423235

32-3,-34-39
23,J23,-13-3-3443143443,3,J

"32-34-39/3
32/3,J/32
#

A 43,3,
A "0CA,3,,3723,23,123,-4314343,

,35-32
/3,

-3743
A "0(,3,J,32,39,373-2323523,2
?
C 3413,413,94343/3,/3
1313,4-343143443,3,J32/3,J/32
23,43,3/3,J/32

A0-3,7-34
E,35-3,-3-34313-
,3-232231-3,9
>/8&RQWURO6LJQDO'DWDEDVH:

,3,32,313,
;8&RQWURO6\VWHP)UHHZD\:
*(+$9ROXPH,2SHUDWRU¶V*XLGH ,QGH[••
863 of 1016
' *
> > ,32132J13413543143-435 A 8A:,3932
23523,,23,23,-
,3J,34-3,-373,3-
$ ,3-,37-3,9

> $ 8>/:13,943143- 0 ,3-,343
>/# ,3743, A8*(6WDQGDUG0HVVDJHV:
>/
43,3
>8'LVWULEXWHG&RQWURO6\VWHP: +
> >
342323223-23713J13,,
13,213,13,32 ?
13,,
!13,2 ? ,3,
;
;! 239 ? ,3,39,3723,232

13 ?A(8+XPDQ0DFKLQH,QWHUIDFH:
13-

43443,3/3,/32
/3,/3

?
C 3413,413,94343/3,/3
0 ,3-,343 ?! 3A ( 8?A(:
> >
342323223-23713J13,, !,3
13,213,13,32
!,39
A !
H-3-343,
3-
. $
-373,
132
&!239 !,37-3,5J-3,431
> $!
8>:,39 ,39
! ,37,3,13 !3
>F 8
:23423,,23,-13,2J
13,--3943943,, ,
> .!>
,3123J237
234 (,39
23123-235
.
( "
>8
$
> :23,23 !,35
,3923,243,,

$
> 8>:23,23 0
E434439
!
434439 A !
H>
-3-343,
# -37434439 A "(0,3,,321313,213,--3743143,43,,
#
32-3,-34 3,3/3,
C"3213,9-34-39/313,9 A "0,3,J,32,39,373-342323523,J
C"! -3,-34-39 23,-1313,4-3-3443143443,3,J32

32-3,-34-39 /3,J/32

"32-34-39/3 A "0CA,3,,3723,23,123,-4314343,
#

A 43,3, /3,
A "0(,3,J,32,39,373-2323523,213
13,4-343143443,3,J32/3,J/32
) A$!,3943,,33231
!
434439

! !2343 1

-37

,35-32 ",31
.!> -3,2 ,3923,243,43,,
.
-3,, A$!,3943,,33231
-3,
••,QGH[ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
864 of 1016
2 A "0,3,J,32,39,373-3423235
23,J23,-1313,4-3-3443143443,
$) 3,J32/3,J/32
E,35-3,-3-34313- A "0CA,3,,3723,23,123,-4314343,
FE32-37 /3,
FC,3-32-3,-343, A "0(,3,J,32,39,373-2323523,2
F,3743,31 1313,4-343143443,3,J32/3,J/32
FE32-37 !,3-,343
FC,3-32-3,-343,
FC
8F:,3743,31
F82/(IRU3URFHVV&RQWUROV: 7
%(87XUELQH&RQWURO,QWHUIDFH:
3 %'(,3931
23123-23523,13-

,34-3,4 %A.87ULSOH0RGXODU5HGXQGDQF\:
>?83ODQW'DWD+LJKZD\:
$#8&RQWURO6\VWHP7RROER[:
,31-31 ,34313-

> ? 8>?:,32 %.,3,3723,232
C83URJUDPPDEOH/RJLF&RQWUROOHU: %? 3-235J23,-3,32
,32,343423223723523,13213-134
13,1J13,9431J4394353-/3 E$) ,34313-
$ /32 %
-3-34-393,

23,43,3/3,J/32

-34

/3,/3 %? 3-235J23,-3,32
%A. /3 > ? .!
@ 23523,,23,23,-

132 >
/#23523,,
$
C
8C:43,3- >
3-
) ,3531-37-3,-3,1-3,543,J C3-23,123,-
43143543,43, A "0(23,2
! 23,,
)-3,443,43 235
@"$31-37-3,-3,1-3,443,J432 %
A!
.! 8%A.:/3
31432 %!$
( 8%(:,3,32323-23,1
13,4-3,-3-3443143-43,,3,J32
5
. $
>
-373, 8
&! ,3, >?88QLW'DWD+LJKZD\:
.!> -3,2 > ? 8>?:,32/3
!!-3, -3,
.
-3,, !!-37
!3-23232234J2373,
9
6

-34
>/# ,3743,
>/
43,3
! ,3-37-3, :
&! 8F:434 $3-
&!>
239 > ;! 32
13943,139 ,393-

A 431J4353, @"$31-37-3,-3,1-3,443,J432

437
F86HTXHQFHRI(YHQWV:
,39
>%.FB(

A "(0,3,,321313,213,--3743143,
43,,3,3/3,
*(+$9ROXPH,2SHUDWRU¶V*XLGH ,QGH[••
865 of 1016

*(,QGXVWULDO6\VWHPV
*HQHUDO(OHFWULF&RPSDQ\
5RDQRNH%OYG
ZZZ*(LQGXVWULDOFRP 6DOHP9$86$
866 of 1016
*(+$9ROXPH,I2RI

6XSHUVHGHV*(+

Reduced manual for Mark VI Maintenance training
)RU63(('7521,&7XUELQH&RQWURO
Application*XLGH
867 of 1016

!

! DVLV !
"#

!$!

!
$
!
!
% ! !

&!
$
$ !
%

!

!
"
!
! '
&!
$

( ! "
&! !
%!

!

!$) !
%! !

&!!
$ $
(!
!
$
!
! *!
!
$ +
(!

,-,. "/

01,-23415
+ 6,7771.087771219297 :
6,-1297278(
:
; #+ 6,-12797448
:
8<6=
&!
! :
%!

! !

!
'

&! $%!
$!

$
!

(!

>! ( + ?34,40

!(8,:
%
@ ' + % >
%
.$
+ A

.B% ">

(AC((%D ! "; !! B (
"E#
#
A B A @ @ B% "A

A$! "!
! "(

(3/" "F( (
>%.FB( "

868 of 1016
6DIHW\6\PERO/HJHQG
VWULFWO\REVHUYHGFRXOGUHVXOWLQSHUVRQDOLQMXU\RUGHDWK
VWULFWO\REVHUYHGFRXOGUHVXOWLQGDPDJHWRRUGHVWUXFWLRQRI
HTXLSPHQW
,QGLFDWHVDSURFHGXUHFRQGLWLRQRUVWDWHPHQWWKDWVKRXOGEH
VWULFWO\IROORZHGLQRUGHUWRRSWLPL]HWKHVHDSSOLFDWLRQV
1RWH(

!
*(+$9ROXPH,2SHUDWRU¶V*XLGH 6DIHW\6\PERO/HJHQG••D
869 of 1016
7RSUHYHQWSHUVRQDOLQMXU\RUHTXLSPHQWGDPDJH
FDXVHGE\HTXLSPHQWPDOIXQFWLRQRQO\DGHTXDWHO\
WUDLQHGSHUVRQQHOVKRXOGPRGLI\DQ\
SURJUDPPDEOHPDFKLQH
7KHH[DPSOHDQGVHWXSVFUHHQVLQWKLVPDQXDOGR
QRWUHIOHFWWKHDFWXDODSSOLFDWLRQFRQILJXUDWLRQV%H
VXUHWRIROORZWKHFRUUHFWVHWXSSURFHGXUHVIRU
\RXUDSSOLFDWLRQ
E••6DIHW\6\PERO/HJHQG +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,
870 of 1016
&RQWHQWV
5HDGHU&RPPHQWV
6DIHW\6\PERO/HJHQG
&KDSWHU2YHUYLHZ
( ! ,3,
?A(F ,3
! ; ! ,3
?A( ,32
>
,31
! ,34
F
; ! ,39

3; ! ,39
%
,39
.
>! ,37
? %>! ,35
%# ,35
? ?
,3,
&KDSWHU,QVWDOODWLRQ
( ! 3,
C ! 3
(
3
(AC((%D) 3
B% 3
! " 32
(AC((%D0 ! 32
B "! 32
%(0 31
(
31

%( 31
F " 3-
%(F 3-
(AC((%D) 3-

34
! 34
. 34
> ? ( 34
&KDSWHU0DLQWHQDQFH
( ! 23,
> ! ! ;
23
(AC((%D> 23
%(> 23
%(! 23-
%(! ;
23-
! ;
8;+HFB;(>%: 239
*(+$9RO$SSOLFDWLRQ*XLGH &RQWHQWV••
871 of 1016

;
8;+HB%CA>%: 23,
# ! ;
8E>%: 23,,
A$!! ;
8(FIF.%>%: 23,
%! ;
8%(ADB>%: 23,2
%J% ;
8%(AJFB>%: 23,-

23,4
B%! 23,9
%!$
A ( 23,7
>! ! 23
%(A$!A 23
%(A$!
23
(AC((%DA$!A 23,
>>I%%K> >! ! 23
A "(0 23
A "0 A "0CA 232
A "0( 232
AIB3
232
C 239
%C 239
> >
235
A 232
A 0 232,
!!8? >! %!$A9: 232

; ! ;! 232-

C 232-

? 2324
HST_SOE=NO 2324

? 2329
?>
231,
. 231,
.K. 231,
A 231-
%(A$! 231-
@$ 2314
@$3/ >
2319
%? 2317
%? A "08; 0: 2317
%? A "08B 0: 23-1
%? A "0( 23-5
> %
234
/ L! 234
F 234
&KDSWHU8WLOLWLHV
( ! 13,

>!,KCA>A, 132

>!3CA>A 132
.@?F 131
! 3
$ >
13-
A "0!
$ 13-
!$! 134
C! 137
> 137
!
$ >
>
/# 135
A "0(!
$ 135
.>I(> 13,
?M. 13,
••&RQWHQWV +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9RO
872 of 1016

>
13,,

13,
A "0(
13,

)! >
13,2
> ! >
13,-
;
% 13,-
> ! >
13,-
>A>.> ! 13
> >
! 13-
> >
!;
13-
/C;(CK
$
%;
134
C;>
139
;
! ! 139
C;>
137
A$!C ;
1324
A$!IC 1324
AAI 3A$!A 1327
AI 3A$!
1327
> >! 3>>I%% 1325
0F%K > >
131
.
%C
3CF.K 131

C>
/# 131
%
( A 3%(AB 1311
%JA "3%JIAM 131-
0(@ 1317
0(@
1317

0(@
1317
0(@IC(AK0 >
C 1315
0(@I>30 >
> 13-
0(@30 F> 13-,
0(@,30 F> 13-
0(@ 13-2
0(@30 > (( 13-4
0(@% 13-5
0(@>3
$
> 134
0(@030 ?30 %!$> 1341
0(@L30 A!
3?3%!$> 1344
@$3/ >
1347
@$>
1345
@CA>A3@$
>!
139
@B%K@$.B%! 139,
@.@?FK@$.@?F>
139
@%?BK@$! 1392
@FB%K@$
>
1391
@>AB>3@$> >
1394
C 1397
@/C3@$
$
>
1395
@?.%K@$?

N # . 137
?

! . 137
@?(%F.D3?

N . $> 1371
@C;F.3@$C;>
1374
@/.F4K@$ / A "0( 1379
A "0(%
$#/ . 135
@/.FE>3@$ / 1354
E> > / / . 1357
@.F3@$C 13,
@AI>23@$! O>2;
13,,
*(+$9RO$SSOLFDWLRQ*XLGH &RQWHQWV••
873 of 1016
&KDSWHU1HWZRUNLQJ
( ! -3,
A "(0 K
; -3
; -3
A "0 3
" -32
%. -32

" -31
;$3F $
-3,
. -3,,
-3,2
A "0(> ? K -3,1
> ? -3,-

> ? -3,-
A "0(B ".!
-3,4
B "&! -3,4

C" -3,7
&KDSWHU&RQWURO&RQILJXUDWLRQ
( ! 43,
A "0
43
?A( 3> 43

3! ;
434
>
3! ;
439

439
A "0(
437

437
.>I(> 437
>/(C>K>
/!
A "0 43,,
>/(C>,K>
/!
A "0CA 43,
>/(C>,K> ! /!
43,
>(/(C>,K(FI;> ;
/!
43,1
>/(C>,K.FA!$3> /!
43,1
>>CF%3> > C 43,-
>>%(C3> >
43,9
AM-AMKA "0A " 43,7
;A0(>3;!
A 0
(> 43,5
C>/.AKC P > $ A 43,
C>/?MKC P > $ " 43
>>0CK> > 0
432
C.AICK
C 432
FB%%K 431
FB%?MK " 43-
LFAC3&! 439
L>FA%K&!>! 432,
L>(%8&!: 4321
.(B%3
&! 431
%/CI8% $

: 4311
.FA 431-
;
>
4317
>;K>;
4317
*ORVVDU\
,QGH[
••&RQWHQWV +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9RO
874 of 1016
&KDSWHU2YHUYLHZ
,QWURGXFWLRQ
*(+9RO,LVDQ+0, %?! 3A ( 8?A(:>%.FB( !$
!3
RSHUDWRU¶VJXLGHIRUPDQ\

3
3

IHDWXUHVLQWURGXFHGLQWKLV &! ( ! 3$ " ! A Q@ B%Q
FKDSWHU
3 !%?A(

A "(0A "0A "0CA A "0( !$

%! ?A(
( !

!
$
?A( ! (AC((%DQ?A(
! >%.FB(A "(0A "0A "0CA A "0(
!$
. +RZWR8VH7KLV'RFXPHQW

% $ ?A(
!$

!
! ! !

6HFWLRQ 3DJH
?A(F ,3

! ; ! ,3
?A( ,32
>
,31
! ,34
F
; ! ,39

3; ! ,39
%
,39
.
>! ,37
? %>! ,35
%# ,35
? ?
,3,
*(+$9ROXPH,,$SSOLFDWLRQ*XLGH &KDSWHU2YHUYLHZ••
875 of 1016
+0,2YHUYLHZ
7KH&,03/,&,7<+0,LVD ?A(! $ %!$
( 8%(:(AC((%D
SURGXFWRI*()DQXF /8%(A/: %!$

! >

$XWRPDWLRQ ?A(! ! (AC((%D?A(

! !
%?A( $!

&! !
7KHWRROER[LV*(¶V:LQGRZV
EDVHGVRIWZDUHSDFNDJHXVHG 1RWH%%!$

! > %!$
IRUFRQWUROOHUFRQILJXUDWLRQDQG %

$#8
$#:> ? %. A "0(
GLDJQRVWLFV !$
!
$# !
%?A(!
!$
! +
• A !$ !

8#

! $ $ ":
• (!
!$8#

F! . 'C :
3URGXFW)HDWXUHV
%?A(
! !

+
• >
•

• $

•

8 :
• ?A( !
••&KDSWHU2YHUYLHZ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,,
876 of 1016
+0,&RPSRQHQWV
% !$
?A(
!
8
;!,3,:+
*).SURYLGHVDGHWDLOHG • &,03/,&,7<+0,!

!$ !
GHVFULSWLRQRIWKH&,03/,&,7< $
! ! 8:.
,
SURGXFW¶VFDSDELOLWLHV (AC((%D ! !$

K +0,6HUYHU !$
$ >
?
> ? 8A "0(
:
! %

! $
#

K +0,9LHZHU !
!
(

!

!

!
$

• 7XUELQH&RQWURO,QWHUIDFH7&,!
8
,3! : !
!$! %(

!$

! +

K
3 ! !$
8A "(0
0:
K !$
! $
8A "(0 0:
K

!$
8A "0(:
K A 8A "(0 0:
• 7&,0%8%('(AC((%D/!

&,0%RU&,0%ULGJH:
$ (A((%D %(
+
K $
(AC((%D

!$!
K ; 8A "(000CA:
8
: (AC((%D
• 6\VWHPGDWDEDVH8A "0(
: $

(

$

('F

$
> 8>:# %
$ ! ! $! &!!
> P
$$

$! !

! %!
! ?A(
! $
#

877 of 1016
&,03/,&,7< 7&,0% 7&,
3RLQW $ODUP
'DWDEDVH 4XHXH
$ODUP ([WHUQDO $ODUP

$ODUPV
3RLQW'DWD
0DQDJHU $ODUP 4XHXH

0DQDJHU
V
P
DU
'HYLFHV
$ O 'HYLFH

LQW &ROOHFWRU
3R
3RLQW 3RLQW'DWD 0DUN9 'DWD

0DQDJHU 53 'LFWLRQDU\
'HYFRP
(*'
'HYLFHV
)LJXUH'DWD)ORZ%HWZHHQ+0,&RPSRQHQWV
*UDSKLF'LVSOD\V
%?A(!
! (AC((%D

%

3
6FUHHQVDUHGHYHORSHGXVLQJ %?A(
!
SUHFRQILJXUHGJUDSKLFEXLOGLQJ

! ! >

EORFNVWKDWSURYLGH $

$)
FRPPRQDOLW\WRGLIIHUHQWSODQW !
"$ ?3

$!
DSSOLFDWLRQVWKDWXVHWKH+0,

,
?A(

! ! $

&! !

D!
?A( " ! P

%
!

;!,3
!
0 !

3
!$
% 8: $
! !

!

878 of 1016
$ODUP9LHZHU 6HWSRLQW(QWU\ $ODUP'HWDLO 6KDIW9LEUDWLRQ
ZLQGRZ VHOHFWLRQ GLVSOD\VHOHFWLRQ GLVSOD\VHOHFWLRQ
)LJXUH6DPSOH+0,'LVSOD\6KRZLQJ6WHDP7XUELQHDQG*HQHUDWRU'DWD
% "?A(! !

3
!
P
!
+
*).SURYLGHVDGHWDLOHG • &LP(GLW $) 3 !
GHVFULSWLRQRIWKH&LP(GLWDQG

@
&LP9LHZDSSOLFDWLRQV ! ! ; !
!+
K
$
K F$) C" $8FC:
K A
K ;
$) $
$
• &LP9LHZ ?A(!3

8 ;!,3:(0 !

!FC ! !
$) ,3

" ?A(0
879 of 1016
• $ODUP9LHZHU
! !

$ $! $ $!
!
! $

$
! $)
0
• 7UHQGLQJ$ E

$

%!
$ ?A( 3

" > $ ! $

$ $
%
!!

!
R! P

• 3RLQWFRQWUROSDQHO

3

!
!D!

$
!
• %DVLFFRQWUROHQJLQH
!

"!

$"
$ % ! 0!
/

!
&RPPXQLFDWLRQV
5HIHUWR*(+9RO,, ;!,32 "!$ ?A( !
DQGLQGLYLGXDOFRQWUROOHU >%.FB( !$

GRFXPHQWVIRUPRUHGHWDLO
DERXWWKHQHWZRUNVDQG 0DUN9,3ODQW'DWD+LJKZD\(WKHUQHW
SURWRFROXVHGIRU+0,
FRPPXQLFDWLRQ
'DWD 'DWD
+0,
+0,6HUYHU +0,6HUYHU 9LHZHU +LVWRULDQ
75
0DUN9,8QLW'DWD+LJKZD\(WKHUQHW
0DUN,9&RQWURO6\VWHP)UHHZD\&6)
0DUN96WDJHOLQN
0DUN9, 0DUN,9 0DUN9

7XUELQH 7XUELQH 7XUELQH
&RQWURO &RQWURO &RQWURO
,2 ,2 ,2
)LJXUH([DPSOHRID7XUELQH&RQWURO&RPPXQLFDWLRQV1HWZRUN
880 of 1016
; %'(! 3 &! ! $!

8>: ?A((!

8A: A$!Q
A

! !

3

+ 3
&!

! >&!
$
!
A$! ?A(
> !

! !$

2SWLRQDO)HDWXUHV
'RFXPHQW*(+SURYLGHV %?A(! @ B%Q3$ +LVWRULDQ!

LQIRUPDWLRQDERXWWKH
!

F(*(3/"Q
+LVWRULDQ

3
! ?

'?A(0 %?A(! ? !
3$
> ? 8>?: !.32

%?A(
! WLPHV\QFKURQL]DWLRQ $
$
3 3

! @!
$

!$

! !

&!

:HE*DWHZD\
! ?A(

( %3
?A( # >

$

('F !
$SSOLFDWLRQ6SHFLILF)HDWXUHV
@ ?A( 0DUN9RUWKH0DUN9,WXUELQH
FRQWUROOHUV !$

$

?A(%A "0( ! $
%
$#8
$#:
@ ?A(!!,QWHJUDWHG&RQWURO6\VWHPV8(:!

%DODQFHRI3ODQW8/F:
('/F
$
?A(
7HFKQLFDO6SHFLILFDWLRQV
# ?A(
! * ! %?A( "

! ?A(

881 of 1016
5HODWHG'RFXPHQWDWLRQ
%
!
?A( >%.FB( !$

! ?A( +
*(+LVWKHGRFXPHQW +0,UHODWHGGRFXPHQWV
LGHQWLILFDWLRQQXPEHU
• ?34,40
!(+0,IRU63(('7521,&7XUELQH&RQWURO2SHUDWRU¶V
*XLGH
• (3,,4-*('66WDQGDUG0HVVDJH)RUPDW
• (3,956'%([FKDQJH8VHU¶V*XLGHIRU&RQWURO6\VWHP6ROXWLRQV
• (3,-6\VWHP'DWDEDVH8WLOLWLHVIRU&RQWURO6\VWHP6ROXWLRQV
• (3,-,2+0,7LPH6\QFKURQL]DWLRQIRU63(('7521,&7XUELQH&RQWURO
• (3,-,13RZHU%ORFN&RQWUROIRU63(('7521,&7XUELQH&RQWURO
3URGXFW'HVFULSWLRQ
• (3,-,-0LFURVRIW1HW0HHWLQJIRU63(('7521,&7XUELQH&RQWURO
,QVWDOODWLRQDQG6HWXS
• (3,-,4*(,QGXVWULDO6\VWHP6WDQGDUG0HVVDJHV*60
• (3,-2-0RGEXV&RPPXQLFDWLRQ,QWHUIDFHIRU63(('7521,&0DUN9,
7XUELQH&RQWUROOHUV
• ?3417XUELQH+LVWRULDQ6\VWHP*XLGH
• ;M3,,7&,03/,&,7<%DVH6\VWHP8VHU
V0DQXDO
• ;M3,,7,&,03/,&,7<+0,3ODQW(GLWLRQ%DVH6\VWHP'HYLFH
&RPPXQLFDWLRQV0DQXDO
• ;M3,254&,03/,&,7<+0,&LP(GLW2SHUDWLRQ0DQXDO
• ;M3,49-&,03/,&,7<+0,23&6HUYHU2SHUDWLRQ0DQXDO
0DUN9,FRQWUROOHUDQGUHODWHGGRFXPHQWV
• ?3412&RQWURO6\VWHP7RROER[IRU&RQILJXULQJD0DUN9,7XUELQH
&RQWUROOH
• ?3417&RQWURO6\VWHP7RROER[IRU&RQILJXULQJWKH7UHQG5HFRUGHU
• ?341,63(('7521,&0DUN9,6\VWHP*XLGH9ROXPHV,DQG,,
• S3917-63(('7521,&0DUN9,7XUELQH&RQWURO6RIWZDUH0DLQWHQDQFH
• (3,97'DWD+LVWRULDQ
0DUN9DQG9/0FRQWUROOHUDQGUHODWHGGRFXPHQWV
• ?3-59563(('7521,&0DUN97XUELQH&RQWURO8VHU¶V0DQXDO
• ?3-5763(('7521,&0DUN97XUELQH&RQWURO0DLQWHQDQFH0DQXDO
• ?34,5-63(('7521,&0DUN97XUELQH&RQWURO$SSOLFDWLRQ0DQXDO
2YHUYLHZ
• ?342-10DUN9/0 63(('7521,&7XUELQH&RQWURO,!8VHU¶V0DQXDO
882 of 1016
+RZWR8VH7KLV'RFXPHQW
D!!
$
A @ #
>%.FB(
!$

)RUDQH[DFWRXWOLQHRIWKH %! P
!

GRFXPHQW¶VFRQWHQWDQG ! ! ?A(
RUJDQL]DWLRQUHIHUWRWKH7DEOH
&KDSWHU2YHUYLHZ% ! ! !
RI&RQWHQWV

&KDSWHU6WDUWXS% !
! "!

?A(
&KDSWHU0DLQWHQDQFH% !?A( !%(
! !

&KDSWHU8WLOLWLHV% $?A(!

&KDSWHU1HWZRUNLQJ% $ ! "
?A(
$!

7H[W&RQYHQWLRQV
%
$
!
! !
&RQYHQWLRQ 0HDQLQJ
Ø !

B!$
!
$
8#

$ P
!
!$ 8!$ : $

8#
DEF
/!
8•:
.
!$!
w !

/#8¨:
"

$ULDO%ROG @$ !

!
$# #
$#
Monospace . #
>F #

883 of 1016
+RZWR*HW+HOS
(
$ ! !

+
³´LQGLFDWHVWKHLQWHUQDWLRQDO (!

DFFHVVFRGHUHTXLUHGZKHQ

FDOOLQJIURPRXWVLGHWKH86$ ,-,. "/

01,-23415
+ 6,7771.087771219297 :
6,-1297278(
:
; #+ 6,-12797448
1RWH
&! !$ &!

!$
$
#
&!

884 of 1016
&KDSWHU,QVWDOODWLRQ
,QWURGXFWLRQ

?A(3

! P

&! ! *
( !!

!

3!
%
! "! ?A(

6HFWLRQ3DJH
C ! 3

(
3
(AC((%D) 3
B% 3
! " 32
(AC((%D0 ! 32
B "! 32
%(0 31
(
31

%( 31
F " 3-
%(F 3-
(AC((%D) 3-

34
! 34
. 34
> ? ( 34
*(+$9ROXPH,,$SSOLFDWLRQ*XLGH &KDSWHU,QVWDOODWLRQ••
885 of 1016
/RJLQDQG6WDUWXS
,QLWLDO3RZHU8S

?A(!

&,03/,&,7<3URMHFW
" (AC((%D) &LPSURM

&?6LWH?&LPSURM
178VHUQDPHVDQG3DVVZRUGV
Ø7RFKHFNWKH17XVHUQDPHVDQGSDVVZRUGV
, ; 6WDUW!
6HWWLQJV&RQWURO3DQHO1HWZRUN
F ,GHQWLILFDWLRQ $
" &RPSXWHU1DPH :RUNJURXS

2 " !
?A(!

?A(, ! ! !&! !
$
! ! 0.,8:0@.,8 :.A,F !
3!
! 0.,0. $
1 0 178VHUV $GPLQLVWUDWRURSHUPDLQWB%!
(AC((%D!! !
- @

$GPLQLVWUDWRU
3URJUDPV$GPLQLVWUDWLYHWRROV
8VHU0DQDJHU " B%!' +
!
?A(

?

F
••&KDSWHU,QVWDOODWLRQ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,,
886 of 1016
&RQILJXUDWLRQ&KHFNV
&,03/,&,7<9HUVLRQDQG6HWXS
" (AC((%D0) !

>" !
Ø7RFKHFN&,03/,&,7<3URMHFW&RQILJXUDWLRQ
, ;&RQILJXUDWLRQ&DELQHW
+HOS$ERXW&IJ&DE"
(AC((%D0
; !$ ) &RQILJXUDWLRQ&DELQHW
3URMHFW
3URMHFW6HWWLQJV
2 !(AC((%D?A(
) +

) B + #
0.,0@.,
!$> +A! $)8"!@ #
:
+ +H(%
F + B
1 "
(AC((%D

+
.M06!
A
5
>(
-
6WDUW3URJUDPV&,03/,&,7<+0,5HJLVWUDWLRQ"
(AC((%D.
4 " ! 8QLWB&RQWUROFLP "

1HWZRUN&RQILJXUDWLRQ
" "( $

Ø7RFKHFNWKHQHWZRUNFRQILJXUDWLRQ
,
6WDUW6HWWLQJV&RQWURO1HWZRUN3URWRFROV7&3,3
" ( ! >?8 >
? : >?8
> ? :!
$
'DWD+LJKZD\,3$GGUHVVHV%
,5,47/EDJ
2 " 6XEQHW0DVNR !
$------
1 " '16(QWU\
8
!:
- " $
$!+
3 ; 0/
$ + #
$

3 ; 0>
$ + ,/ % - $

4
6WDUW6HWWLQJV&RQWURO1HWZRUN$GDSWHUV
9 ; $GDSWHU7DE &203&,&RPER1,&
&%&RPER
887 of 1016
7 "
+H B%H 2HH H?
! !

( %
!
$$ &!

!
$ ! %

#
? ;
+
127.0.0.1 localhost
192.168.1.10 G1_EGD #MKVI <R> CONTROLLER
192.168.1.20 G2_EGD #MKVI <R> CONTROLLER
192.168.1.30 S1_EGD #MKVI <R> CONTROLLER
192.168.1.14 SS1_EGD #LCI
%! ,I> (
7&,9HUVLRQ
" %( 9HUVLRQGDW

+H H%(
6LWH,QVWDOODWLRQ
"
!

! ! !$
! ! 8
:
Ø7RFKHFNWKHRYHUDOOV\VWHPFRQILJXUDWLRQ
w ; &RQILJGDW
"
+
3 !$
3
3 !
3
%

&RQILJGDW
+
;
; UNIT UNIT PATH TO UNIT UNIT
; NUMBER NAME CONFIGURATION DATA TYPE
; ------ ---- ------------------ ----
UNIT_DATA
1 G1 F:\UNIT1 MARKVI
7&,6HWWLQJV
" %( !
% "
Ø7RFKHFNWKH7&,6HWWLQJV
,
6WDUW6HWWLQJV&RQWURO3DQHO7&,
; $XWRORJLQ $" (QDEOHG8 RSHU:
2 ; 6LWH $ +H H0.,'HIDXOW6FDOH" (QJOLVK
0HWULF

1 ; 7LPH6\QF $" 1RQH

- ; $UFQHW $" 1RW8VHG

888 of 1016
2SHUDWLRQ&KHFNV
7&,2SHUDWLRQ
" %(!

Ø7RFKHFNRSHUDWLRQRIWKH7&,
, .$ !
; &RPPDQG3URPSW
C:\ net start
2 C" %( +7&,7XUELQH&RQWURO,QWHUIDFHZDVVWDUWHG
VXFFHVVIXOO\
1
6WDUW6HWWLQJV&RQWURO3DQHO6HUYLFHV
- ; 6HUYLFHV
"%(
+
%( !
> > $

>

! !
(B !
B "%
!
>/ !
&,03/,&,7<3URMHFW
(AC((%D) !

! $
Ø7RVWDUWWKH&,03/,&,7<SURMHFW
, ; ;+H)
JHI
(AC((%D)
%&RQILJXUDWLRQ&DELQHW
;&RQILJXUDWLRQ&DELQHW
5XQ8%
:F$
(AC((%D !!

2 ; 'HVNWRS ! #! I

1
6WDUW3URJUDPV&,03/,&,7<+0,!
- ; +0,!
3RLQW&RQWURO3DQHO
4 ; 3RLQW&RQWURO3DQHO
)LOH 1HZ
9 ; (GLW!
$GG
7 ; !
$ %

! (AC((%D
!

889 of 1016
$ODUP3ULQWHU
"
!%
!!

# ( $ !
P
Ø7RDFFHVVWKHSULQWHUZL]DUG
w
6WDUW6HWWLQJV3ULQWHUV
% P

$XWRVWDUW
"! . ! R !
$ ! (AC((%D
(A0
% !(AC((%D

"
! (A0 (

(AC((%D
5HPRWH$FFHVV6HUYLFH
" . 8.:. $ !
!
$
Ø7RPDQXDOO\VWDUW5$6XVLQJ:LQGRZV
,
"6WDUW3URJUDPV$GPLQLVWUDWLYH7RROV&RPPRQ
5HPRWH$FFHVV$GPLQ
; 5HPRWH$FFHVV$GPLQ

"6HUYHU 6WDUW
5HPRWH$FFHVV6HUYHU.
Ø7RDXWRPDWLFDOO\VWDUW5$6
w (. $ ! !
$ !

.
'DWD+LJKZD\,3$GGUHVVHV
'HSHQGLQJRQWKHSURMHFWWKH . ! (
DFWXDO,3DGGUHVVHVPD\QRW !
( >? >?!?341,3
IROORZWKHVHJXLGHOLQHV 63(('7521,&0DUN9,7XUELQH&RQWURO6\VWHP*XLGH
% ( ,5,47$%&;<=
%
#
( +
!
$>?1 !$! !$2%
!
$>? !$! !$,?./
!
$ (AC((%D0 !
$>?T,
!
$ ! 3!
>?T-

!$ "------
1RWH "!
!

( ( ! ! &! "
890 of 1016
&KDSWHU0DLQWHQDQFH
,QWURGXFWLRQ
% ! ?A( !%!$
( 8%(:
! ! !

! !

6HFWLRQ3DJH
> ! ! ;

23
(AC((%D> 23
%(> 23
%(! 23-
%(! ;
23-
! ;
8;+HFB;(>%: 239

;
8;+HB%CA>%: 23,
# ! ;
8E>%: 23,,
A$!! ;
8(FIF.%>%: 23,
%! ;
8%(ADB>%: 23,1
%J% ;
8%(AJFB>%: 23,4

23,9
B%! 23,7
%!$
A ( 23,5
>! ! 23,
%(A$!A 23,
%(A$!
23,
(AC((%DA$!A 23
>>I%%K> >! ! 232
A "(0 232
A "0 A "0CA 231
A "0( 231
AIB3
231
C 237
%C 237
> >
232
A 232,
A 0 232
!!8? >! %!$A9: 2322

; ! ;! 2324

C 2324

? 2329
HST_SOE=NO 2329
*(+$9ROXPH,,$SSOLFDWLRQ*XLGH &KDSWHU0DLQWHQDQFH••
891 of 1016

? 2327
?>
231
. 231
.K. 231
A 2314
%(A$! 2314
@$ 2319
@$3/ >
2317
%? 2315
%? A "08; 0: 2315
%? A "08B 0: 23--
%? A "0( 234
> %
234,
/ L! 234,
F 234,
'LUHFWRU\6WUXFWXUHDQG)LOHV
&,03/,&,7<'LUHFWRULHV
%?A( ! R
(AC((%D %(3%(AC((%D

+
)RUDGHVFULSWLRQRI C:
&,03/,&,7<GLUHFWRULHVUHIHU
WR*).&,03/,&,7<
8VHU¶V0DQXDO CIMPLICITY
HMI
BSM_DATA
DATA
EXE
LOG
7&,'LUHFWRULHV
%%(! ! 3 3
SVHXGRRUVXEVWLWXWH
• ) 3 !!$
• *
!$

!
!$
%
3!%(! $

&%
&

%(
••&KDSWHU0DLQWHQDQFH +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,,
892 of 1016
C:
CIMPLICITY
G:
TCI
DATA
DATA
EXEC EXEC
LOG &LVSDUWLWLRQHGLQWR LOG
SVHXGRGULYHV*
SITE DQG)DVVKRZQ F:
RUNTIME RUNTIME
UNIT1
UNIT1
PROM
PROM
USER
UTILITY
USER
GULYHV) * !

&%! $
$%( !
!!%(&! $! ! !
%( !

'ULYH))LOHV
%

!GULYH)
3

FRQILJXUDWLRQ
+
• &21),*'$7 !
( !
! # ! !$

! 3 (

"
$! !
"# %( !

$
"
*(+9ROXPH,GHVFULEHV • 6<67(0''
(

WKH'HPDQG'LVSOD\SURJUDP XQLWGG
!$
(
"
%(!
'ULYH)6XEGLUHFWRULHV
• ?5817,0( !3>
A!
'(0$1'11'0
(

A "0! #
• ?86(5 !
!%( 3!
!
! !
(
! !

! ! $
$!
• ?81,7Q ! $
$ %( Q&!

! !$8! #! ! '!$ :;

"! > > ! ! 3
!

$" %

! !
8! V81,7'$7$'$7,26&$/('$7
$/$50'$7$1'&21676(7'$7
893 of 1016
• ?81,7Q?3520
.FA3

!
('F! >!
&!
&!

! %
!$3 ! /
/
"C$ 8//C:

.FA!

'ULYH*6XEGLUHFWRULHV
!$3 GULYH*
LQIRUPDWLRQ
+
• ?(;(&
#! $

' $ %(
$
!! 3!#!
• ?'$7$
&!$ 3(

$!$ 3

!

" !
!
3 GULYH)+ %
!

3
$!
• ?/2* ! ! ! $
$! !$
!

3!

894 of 1016
7&,&RQILJXUDWLRQ
%($!

!
! !

%(
+
• %
$!

! !
• !

• %%( ! ! ! ?A( !
!

•
A$!Q A 8A:
• %( ?A( !

?A(! %! (AC((%D$
! (AC((%D $

7&,&RQILJXUDWLRQ)LOHV
%!
%( !GULYH)%

)
! %( !

%

! !$
+
7DEOH&RQILJXUDWLRQ)LOHVE\&RQWUROOHU7\SH
)LOH1DPH ,QWHUQDO 0DUN,9 0DUN9 0DUN9/0 0DUN9,

&21),*'$7 $OO $OO $OO $OO $OO
FRPPXQLFDWLRQ FRPPXQLFDWLRQ FRPPXQLFDWLRQ FRPPXQLFDWLRQ FRPPXQLFDWLRQ
SURJUDPV SURJUDPV SURJUDPV SURJUDPV SURJUDPV
(1(7$/0'$7 1$ 1$ 1$ 1$ $OO
FRPPXQLFDWLRQ
SURJUDPV
(*'386+'$7 1$ 1$ 1$ 1$ $OO
FRPPXQLFDWLRQ
SURJUDPV
,2B32576'$7 $OO 0RGEXV3'' 1$ 1$ 1$
FRPPXQLFDWLRQ 6HULDO063
SURJUDPV RU063RYHU
56&
3,&21),*',) $OO $OO $OO $OO $OO
FRPPXQLFDWLRQ FRPPXQLFDWLRQ FRPPXQLFDWLRQ FRPPXQLFDWLRQ FRPPXQLFDWLRQ
SURJUDPV SURJUDPV SURJUDPV SURJUDPV SURJUDPV
7,0(6<1&'$7 2SWLRQDOILOH 2SWLRQDOILOH 2SWLRQDOILOH 2SWLRQDOILOH 2SWLRQDOILOH
7,0(=21('$7 2SWLRQDOILOH 2SWLRQDOILOH 2SWLRQDOILOH 2SWLRQDOILOH 2SWLRQDOILOH
,QWHUQDO±)RUVWRUDJHRIFRPSXWHGYDOXHVDQGGDWDIURPD'LVWULEXWHG&RQWURO6\VWHP'&6IRUH[DPSOH

±1RWUHODWHGWRWKHFRPPXQLFDWLRQPHWKRGXVHG
$OOFRPPXQLFDWLRQSURJUDPV±XVHGZLWKDOOIURQWHQGFRPPXQLFDWLRQSURJUDPVWKLVFRQWUROOHUVXSSRUWV
%

&!%( !)?&21),*'$7
)?7,0(=21('$7!$
!

&!

!
895 of 1016
)?&21),*'$7 !
%( %

%(
+
• %
!$
! !$ !$
8,:
• % ! ! !
!
• % !$
8A "(0A "0A "0CAA "0(:
• %
"
• %%( !
)?7,0(=21('$7! %

%@
B% " " ! $!
!$
%(

2SWLRQDO&RQILJXUDWLRQ)LOHV
F %(!

&!

! %

!+
• )?(*'B386+'$7%
!
! >

! A "0(
%

$ >
• )?,2B32576'$7%

! %(
" .32 %
!
!
$! 8$ ! U:
! %!
!A$!A A$!

• )?7,0(6<1&'$7%

! ?A( $

"(
! ?A( P
"
#
!$
!

"
• )?02'%B):''$7%

! A$!

! $! A$! !

%

!

!

$

8%
!
! A$!
" .32

":
• )?$7B67$57'$7%
! %(
( ! 3 $
%(
• )?$7B6723'$7%
!$%(
! (
! 3 $
$%(
896 of 1016
7&,)RQW/RDGLQJ
% $! %(! % !

%!% $
@ B%V

$
%

$! )RQWV

%

$! *?'$7$
!+
• /,1('5$:77)%%!%
!
$
!

$# 3
%!
! !
!$ > .!>

• *(/2)BBB77)%%!%
!
! !

&RQILJXUDWLRQ)LOH)?&21),*'$7
0DUN,90DUN90DUN9/0 %)?&21),*'$7
! ! .B%
DQG0DUN9,VXSSRUWWKLV A$!%
! A "0(! ;.3

XWLOLW\ 2
! A "(0! %?A( ,1
! &21),*'$7#
+
;
; F:\CONFIG.DAT - HMI CONFIGURATION FILE
;
; CONFIG.DAT - This file defines the overall configuration of the system.
; After making any changes, you will have to reboot the pc for the change
; to take effect.
;
;------------------------------------------------------------------------------
;
; This section defines the site name (16 char max)
;
SITENAME
Power Station
;
;------------------------------------------------------------------------------
;
; NETWORK TYPE - A definition of the networks this pc is on.
; Network Number...... Decimal number 1-n
; Network Type........ (STAGELINK, CSF, SERIAL)
; Device Driver....... Name of the network driver used
; MY LUN.............. This PC's assigned HEX MSP LUN (CSF, SERIAL only)
;
; NETWORK NETWORK DEVICE MY
; NUMBER TYPE DRIVER LUN
; ------- ------- -------- ----
NETWORK_TYPE
1 CSF AnetDev0 0A02
2 STAGELINK AnetDev1 ****
;------------------------------------------------------------------------------
;
; UNIT DATA - A definition of the units
; Unit Number......... Decimal number from 1-n
; Unit Name........... 1 or 2 character unit name
; Path to Config...... Directory path of unit configuration directory
; Unit Type........... (MARKIV, MARKV, MARKVLM, MARKVI, HMI
;
; UNIT UNIT PATH TO UNIT
; NUMBER NAME CONFIG DATA TYPE
; ------ ---- ----------- ----
897 of 1016
UNIT_DATA
;
1 T1 F:\UNIT01 MARKIV
2 T2 F:\UNIT02 MARKV
3 T3 F:\UNIT03 MARKVI
4 T4 F:\UNIT04 MARKVLM
5 T5 F:\UNIT05 HMI
;
;------------------------------------------------------------------------------
;
; NETWORK DATA - A list of the network nodes we need to talk to.
; Unit Number......... The unit number associated with this node
; Processor........... The identity of the processor at this node address
; Network Number...... The network this node is on
; Network Address..... The HEX address of the node on this network
; MSP LUN............. The node's assigned HEX MSP LUN (CSF, SERIAL only)
;
; UNIT NETWORK NET MSP
; NUMBER PROC NUMBER ADDR LUN
; ------ ---- ------- ---- ---
NETWORK_DATA
1 C 1 FE 0401
2 C 2 FC ***
4 R 2 F8 ***
;
;------------------------------------------------------------------------------
OPTIONS
;
;
%)?&21),*'$7
$! ! %, A "(0
! ;%B%@F.MI>% ; .(C
! ! CB!$! !

B%@F.MI%D ;

"B "!%CB ?A(!
B%@F.MI%D ; .(CA "(0!
• % A "0!
"
• %2 A "0( &! "
B%@F.MI>%
• %1 A "0CA!
"
• %- A$! ( ?A(
;
A8AA:! A "(0! "
! $! A "(0 B%@F.MI%D
)&21),*'$7

#

B%@F.MI%D ! ! A "0 A "(0
;
A8AA:A "(0+
; NETWORK TYPE - A definition of the networks this pc is on.

; Network Number...... Decimal number 1-n
; Network Type........ (STAGELINK, CSF, SERIAL)
; Device Driver....... Name of the network driver used
; MY LUN.............. This PC's assigned HEX MSP LUN (CSF, SERIAL only)
;
; ------- ------- -------- ----
NETWORK_TYPE
1 STAGELINK AnetDev0 ****
898 of 1016
2 CSF AnetDev1 0A02
3 SERIAL MSP_3 0B01 ;0B01 = top RS-232C port on unit
4 SERIAL MSP_4 0B02 ;0B02 = bottom RS-232C port on unit
5 SERIAL MSP_5 0B01 ;0B01 = top RS-232C port on unit
;------------------------------------------------------------------------------

" $
A "0!
! !

A "0 A "0CA! ; $

A "(0! ! !

!
;

"!
,2B32576'$7

&KDQJHVWRWKHFRQILJGDWILOHIRUWKH3&,$5&1(7ERDUG
% ! ! ?A(? FA ! (
.B%$ ! A "0
"%

.B%$ ! ; A "
(0
&21),*'$7
! (.B%$

"A "0! %&21),*'$7
!
B%@F.MI%D
" ! (.B%
$ %B%@F.MI%D !
(%BA
$ B(%I>%

B%@F.MI%D
(.B%$
+
; This section defines the network interfaces owned by TCI. If not

; present the system defaults to a single ISA ARCNET Card as network 1.
; Supported network types are STAGELINK and CSF. If a CSF is defined,
; the LUN must also be defined, typically as 0A01 - 0A08.
;
; ------- ------- -------- ----
NETWORK_TYPE
1 STAGELINK CCSI20020Dev1 ****
;
1RWH%CB
!
A "(0;!

B%@F.MI%D (.B%$

+
; This section defines the network interfaces owned by TCI. If not
; present the system defaults to a single ISA ARCNET Card as network 1.
; Supported network types are STAGELINK and CSF. If a CSF is defined,
; the LUN must also be defined, typically as 0A01 - 0A08.
;
; ------- ------- -------- ----
NETWORK_TYPE
;
1RWH% (.B%$ ! !&&6,'HY

"!
899 of 1016
(WKHUQHW$ODUP3URWRFRO)LOH)?(1(7$/0'$7
$/0DODUPSURWRFROLVXVHG )?(1(7$/0'$7
(
IRUGHOLYHULQJGLJLWDOH[FHSWLRQ !
%?A(&!

8#

PHVVDJHVLQFOXGLQJDODUPV A "0(:! CA

HYHQWVDQG6HTXHQFHRI(YHQWV
@
$
#
$
62(PHVVDJHV

! ( @ ?A(!
(1(7$/0'$7 ! %
# 8$
:
$

+0,FRQILJXUDWLRQILOH ( !
; !
)?&21),*'$7GHILQHVWKH
#
&! ( R%
A!
.! 8%A.:
XQLWV
&! @ CA. 8$/05&9(;(

# ( ! (
)?(1(7$/0'$7

! ! $/05&9(;(
( $ !
(1(7$/0'$7
! (> $ >/
!
6'%LVWKH6\VWHP'DWDEDVH ! %(>
!
!
! ! %
! ! $

$ ! %(> &!$ ! !
!
7\SLFDO)?(1(7$/0'$7ILOH ;
; ENETALM.DAT - This file is used by the Ethernet ALARM RECEIVER program
; to define how to interpret the data received.
;
; There should be one line per Ethernet Alarm Generator node that this
; computer is supposed to monitor. Simplex turbine controls have
; one node per unit, TMR turbine controls have three nodes per unit.
;
; UNIT:
; This is the Data Dictionary unit number for the turbine, and must
; agree with the unit number assignments in the F:\CONFIG.DAT file.
;
; PROC:
; This is the processor specification, ( R | S | T ).
;
; IP_ADDRESS:
; This is the IP address assigned to this Ethernet Alarm Generator.
;
; DEVICE: (optional, unused at the current time)
; This is the device number assigned to this node.
;
; Example:
;
;Unit Proc IP_Address Device
;---- ---- --------------- ------
; 1 R 192.168.1.1 46
; 2 R 192.168.1.4 47
; 2 S 192.168.1.5 47
; 2 T 192.168.1.6 47
;
;
;------------------------------------------------------------------------
;
;Unit Proc IP_Address Device
;---- ---- --------------- ------
1 R 192.168.1.10 49
1 S 192.168.1.11 49
1 T 192.168.1.12 49
900 of 1016
)LJXUH0DUN9([FLWHU)DXOW&RGH'LDORJ
0RGEXV&RQILJXUDWLRQ)LOH,2B32576'$7
0DUN,90DUN9DQG0DUN9, %A$!A 800RGEXVH[H: A$!

VXSSRUWWKLVXWLOLW\ 80RGEXVH[H: !

)?,2B32576'$7
$
! $ ! A$!
(>
F !

!> >!

A
8
A:A! A "(0
5HIHUWR*(,0RGEXV %!
((3$ #
$
IRU63(('7521,&7XUELQH # C 3 %!

&RQWURO $

$ " WX
%A$!
!
+
• %WAF>/IC0IF.%X ('F
$! A$!

"/

" ! FA,FA
#
$ %
"!
$$!

8 A$! !
":
• %WAF>/I(BAB%X ! $A$!

! !$ A$! %(A$!

!
(

8:!
A$!
"
• %WAF>/IC0I%(AF%X

! BM ! ! !
901 of 1016
%! P)?,2B32576'$7! #

)?,2B32576'$7
A$!
"%

*?'$7$?,2B32576'$7
%

,2B32576'$7

!

!
;-------------------------------------------------------------------------
;-------------------------------------------------------------------------
;
; <HMI> PORT DEFINITION FILE - F:\IO_PORTS.DAT
;
;
; This file defines the serial ports that exist on this pc
; and that are to be controlled by TCI services.
;
;-------------------------------------------------------------------------
;-------------------------------------------------------------------------
;
; This section defines MODBUS SLAVE port and hardware characteristics.
; This section can be duplicated up to 8 times (Ethernet plus serial ports).
;
[MODBUS_SLAVE_PORT]
;port com2
port none
baud 9600
parity 0 ;0-4 (none,odd,even,mark,space)
databits 8 ;5-8
stopbits 0 ;0-2 (1, 1.5, 2 stop bits) (1.5 stop bits currently unsupported)
xonxoff 0 ;0-1
port_it 40 ;Timeout interval between characters, msec. Default=40
port_tt 200 ;Timeout for total message, msec. Default=200
;-------------------------------------------------------------------------
;
; This section defines that the MODBUS can receive requests over the
; ethernet. There can only be one of these sections.
;
[MODBUS_SLAVE_PORT]
;port ethernet
port none
timeout 60 ; no activity disconnect time in minutes (0 = disable)
Max_Connections 10 ; Maximum number of socket connections allowed
;-------------------------------------------------------------------------
;
; This section defines MODBUS slave address and software characteristics
;
[MODBUS_ASSIGNMENT]
;
;format1: SLAVE nnn UNIT uu MODE keyword
;format2: SLAVE nnn CIMPLICITY project MODE keyword
; where: nnn is the SLAVE address (in decimal) to recognize when sent
; a message from a modbus master.
; uu is the two character unit name (defined in F:\CONFIG.DAT)
; project is the name of a CIMPLICITY project on this computer.
; keyword is either RS16, RU16, UN12, HW12, or NATIVE for Signed 16,
; Unsigned 16, Unsigned 12, Honeywell 12, and Native data
; respectively.
;
; SLAVE and MODE are required entries. UNIT or CIMPLICITY must also be
; on a valid line.
; A new line should appear for each definition. Normally this is one
; or two lines for typical data patterns. A maximum of 16
; definition lines may appear.
;
;SLAVE 1 UNIT <unit_name> MODE RS16
;SLAVE 2 CIMPLICITY <project_name> MODE RU16
;-------------------------------------------------------------------------
;
; This section defines MODBUS slave timeout and Nak characteristics
;
902 of 1016
[MODBUS_SLAVE_TIMEOUT]
modbus_timeout 4000 ;Time (milliseconds) before we give up and send nak
modbus_timeout_nak 6 ;Nak code used if unit timeout occurs.
;To use timeout, specify 4 or 6 only.
;To disable timeout, specify 0.
;-------------------------------------------------------------------------
7LPH6\QF&RQILJXUDWLRQ)LOH7,0(6<1&'$7
0DUN,90DUN90DUN9/0 %% ! $!
!
DQG0DUN9,VXSSRUWWKLV
" A "0 A "0CA
>
! $
XWLOLW\
"%A $
%
" !$
5HIHUWR*(,+0,7LPH
% !

)?7,0(6<1&'$7
6\QFKURQL]DWLRQ ' %"
)?7,0(6<1&'$7
$
+
----------------------------------------------------------
TIMESYNC [<controller> MODE <mode> [LEVEL_SHIFT] | LOWRES | SLAVE]
LOCAL_TIMESET [ENABLED | DISABLED]
I_TIME [LOCAL | UTC]
MARKV_TIME [LOCAL | UTC]
TIME_SOURCE [LOCAL | UTC]
TIME_LOAD [MANUAL | LOCAL |NETWORK]
----------------------------------------------------------
903 of 1016

*?'$7$?7,0(6<1&'$7

)?7,0(6<1&'$7 &!#

7,0(6<1&'$7
+
;------------------------------------------------------------
;
; TIMESYNC Parameters. 11-JUL-1995
; Last Update: 14-MAR-1997
;
; The line beginning with "TIMESYNC" indicates time acquisition hardware
; exists in the system. The syntax of this line is:
;
; TIMESYNC <controller> MODE <mode> [LEVEL_SHIFT]
;
; where <controller> is one of the following:
; BC620AT (from Bancomm, Division of Datum Inc.)
; PC-SG2 (from TrueTime Inc.)
; ISA-SYNCCLOCK16 (from JXI2 Inc.)
; TPRO-PC (from KSI, Division of Odetics Inc.)
;
;
; <mode> defines the external time reference and
; is one of the following:
; IRIG-A IRIG-A Timecode.
; IRIG-B IRIG-B Timecode.
; NASA-36 Nasa 36 bit timecode.
; 2137 2137 Timecode.
; 1PPS 1 pulse per second.
; 1PPM 1 pulse per minute.
; 1PPH 1 pulse per hour.
; FLYWHEEL Free Running Clock.
; "LEVEL_SHIFT" is specified if the timecode is DC Level Shifted
; rather than modulated.
;
; Different timeboards do not support all <mode> selections. The
; following table defines available combinations of timeboards and
; mode combinations:
;
; TimeBoard External Time References Supported
; --------- ----------------------------------
; BC620AT IRIG-A (Modulated and DC Level Shifted)
; IRIG-B (Modulated and DC Level Shifted)
; NASA-36 (Modulated and DC Level Shifted)
; 2137 (Modulated only)
; 1PPS, 1PPM, and 1PPH
; FLYWHEEL
;
; TPRO-PC IRIG-B (Modulated only)
; NASA-36 (Modulated only)
; 1PPS (Requires -m option on board)
; 1PPM and 1PPH
; FLYWHEEL
;
; PC-SG2 IRIG-A (Modulated and DC Level Shifted)
; IRIG-B (Modulated and DC Level Shifted)
; 1PPM and 1PPH
; FLYWHEEL
;
; ISA-SYNCCLOCK16 IRIG-A (Modulated only)
; IRIG-B (Modulated only)
; NASA-36 (Modulated only)
; 1PPS, 1PPM, and 1PPH
; FLYWHEEL
;
TIMESYNC BC620AT MODE IRIG-B
;
; "LOCAL_TIMESET [ENABLED | DISABLED]" is used to allow the operator interface
;time to be set to the same time as the Stagelink Time Master. Note the operat
or ;interface does not require a time/frequency board to be a time slave.
;
LOCAL_TIMESET ENABLED
;
; "I_TIME", "MARKV_TIME" and "TIME_SOURCE" identify what timebase is used
904 of 1016
; in the operator interface, the Turbine Control, and the Global Time Source. ;
Choices are UTC and LOCAL.
;
; NOTE: MARK V Plus panels always have UTC as their timebase. This is not
; changeable.
;
I_TIME LOCAL
MARKV_TIME LOCAL
TIME_SOURCE UTC
;
; "TIME_LOAD [MANUAL | LOCAL | NETWORK]" defines whether major time elements
; (year, day-of-year etc.) are derived from the PC automatically (i.e. LOCAL);
; or obtained from other Stagelink Time Masters (i.e. NETWORK),
; or whether TIMESYNC functions are disabled until major time is entered
; manually via TIMEUTIL (i.e. MANUAL).
;
TIME_LOAD LOCAL
;
; "TIMESET <node-address>" is used when Mark V panels with older versions
; of firmware exist on the stagelink that do not support the timesync
; protocol. In this case, this computer can act as a "repeating timeset"
; computer, transmitting time every hour. <node-address> is the Arcnet
; address in HEX and must be in the range 01-FF. There may be up to
; 32 "TIMESET <node-address>" lines specified in this datafile.
;
;-------------------------------------------------------------------
ҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞҞ
7LPH=RQH7UDQVLWLRQ)LOH7,0(=21('$7
0DUN,90DUN90DUN9/0 % $)?7,0(=21('$7 ! 7=B0$.((;(!

DQG0DUN9,VXSSRUWWKLV 7,0(=21('$7! %3$
XWLOLW\ $ % >
%

!$! %$
CFC
1RWH% $

%(AIJFBI(B;F.A%(FB ! !$@ B%
5HIHUWR*(,+0,7LPH 7,0(=21('$7 ! , !

6\QFKURQL]DWLRQ &!%
- $!%'CFC

"!%
! %3$

CFC3$
"!%

!

B
B3# 8 :
$!!8;
:
%%3$ !
"! %àC
%

# B%
&!

$!7=B0$.((;( !
"
7,0(=21('$78
$ :( !
3$

!
! ! ' ' %'
>
%(
! , ;#
7=B0$.( !,554
,55, !1
!
/ !
7=B0$.(! @ B% %J( !
$

P F
! 7=

$
!
!
!
'>
%
%J $ LBE'B(E P!
8S!

! :
1RWH%!
7,0(=21('$7
&!

!

!$

905 of 1016
&RQWURO3DQHO$SSOHW
0DUN9DQG0DUN9,VXSSRUW %%(

! )! !$ !$
WKLVXWLOLW\
A
!A "
!
$
$XWR/RJLQ
% $!
!!
! !

! $ ! !
%
!
$

VKLIWNH\ !$
" $ "!

'LVDEOHG(QDEOHG('LVDEOHG
!
!

!((QDEOHG
!
!

!
$

8VHUQDPH% ! ! !
$

'RPDLQ% ! !
$
( !!

!
3DVVZRUG% ! !
$

3DVVZRUG9HULI\% ! (

&!
7&,6LWH
% $ !
%(

6LWH'LUHFWRU\3%

%
;

'HIDXOW6FDOH3% !

!
( $

8#

A :
7LPH+DUGZDUH
% $ P ! %(
7LPH&DUG%
P !
7LPH&RGH% !8#
(.(3/:
7LPH%DVH% $ !8#
%:
7LPH6\QF6WDJHOLQN
% $ P %(
'LVDEOH7LPH6\QF% $
P !
7LPH&OLHQW6ODYH% ?A(
!
!
/RZ5HVROXWLRQ7LPH0DVWHU% ! $ !

"
+LJK5HVROXWLRQ7LPH0DVWHU7LPH&DUG% ! $
! 3
! $ %

$
3

! $
!$! !

$GYDQFHG6HWWLQJV%
% )!

" "

" !

! $
$
)!
906 of 1016
7LPH&DUG/RDGLQJ0DMRU7LPH(OHPHQW% C
8 !
:B "A !

$5&1(7
% $ .B%!
" .B%$
%)! $ ! $ .B%
"
1HWZRUN7\SH% .B% "!
%DVH,2$GGUHVV% (F .B%$
%DVH0HPRU\$GGUHVV% .B%$
,QWHUUXSW1XPEHU% ! !$ .B%$
$5&1(7/LQN$GGUHVV% .B%$
.B% "
$ "! !&!

$5&1(7&DUGV.B%$ $ !

173&RQILJXUDWLRQ
7KLVXWLOLW\LVVXSSRUWHGE\ %B%! ! ! B%
0DUN9, B%%B% B%

P A "0(
"B%!

! +
• A ! $ !!
• A !
!
. *(,+0,7LPH6\QFKURQL]DWLRQR
B% B%
!

B%! !

! !
907 of 1016
7XUELQH&RQWURO0DLQWHQDQFH,FRQV
%( 8,&21(;( !
" 6WDUW

! ) "&!$ ?A( ! !

D! ! P !
$

!! @ B%! !
*(+9ROXPHGHVFULEHV
WKHIROORZLQJ7&,SURJUDPV
• 'HPDQG'LVSOD\
• '\QDPLF5XQJ'LVSOD\
• 7ULS+LVWRU\
• 7ULS/RJ9LHZHU
)LJXUH7KH7XUELQH&RQWURO0DLQWHQDQFH6WDUW0HQX6HOHFWLRQV
% $!

+
*?(;(&?8,&21(;(
6WDUW0HQX7XUELQH&RQWURO0DLQWHQDQFH $%
$!
%!$
A $!

"
)LJXUH5HEXLOG6WDUW0HQX'LDORJ%R[
908 of 1016
%5HEXLOG6WDUW0HQX
$#
%
# $!
%

%!$
A
! !3
!

%( > !
! " ! P % !

#
% ! ! " % !

"
909 of 1016
'HYLFH&RPPXQLFDWLRQV&RQILJXUDWLRQ
7&,0RGEXV0DVWHU
0DUN,90DUN9DQG0DUN9, %?A( $! !

VXSSRUWWKLVXWLOLW\
% !!
38#

/
B
$ :
&RQILJXUDWLRQ
5HIHUWR*(,0RGEXVIRU %?A(A$! 8
:A$!
63(('7521,&7XUELQH&RQWURO ! .32
! (A$!
IRUGHWDLOV ?A( A$!
!
! A$!

% $

$
.32
" $ !3 ! !

" $ !
%A$!
! &! A$!

?A( ! !

!! #! !
$! ! ! 17

; A$!
! $

! ! %

8 :
%
A$!
$
.32
!
"
"
%.32
" " !

!
" ! &!
( ,53$ !8$ ': $!
"!

!
"

&! ! &!
$ !

7&,0RGEXV6ODYH
0DUN,90DUN90DUN9/0 A$!
!
"
$!

DQG0DUN9,VXSSRUWWKLV 8>:> $!
A "(0A "0A "0CA A "0(
FRQILJXUDWLRQ
> !A$!

;!232

!(AC((%D %(A$!
>A "0

%(A$!
A "(0 0(
!(AAF>
C
$!
>? ! %(A$!

; A "0(3$ 5Y39 $
C

8C: 5 ! ! !V

C %(A$!A !
910 of 1016
+0,6(59(5
0DUN9,
7&,
0DUN,9 7&, &,03/,&,7< &,002' 0RGEXV '&6
6ODYH
0DUN9DQG
0DUN9/0
)LJXUH'DWD)ORZIURP&RQWUROOHUVLQ0RGEXV6ODYH0RGH
% $

A$!

$
.32
" $ !3 !
!
"% $

A$!

$ $ !3 !
! %> !
,
#!

" $!
%(%!$
A$!

! $

" $ $!

P
%%(A$!
!

&!
%( !

#!,4
$!
%(B

!
$ !

&,03/,&,7<0RGEXV0DVWHU
0DUN9,VXSSRUWVWKLVXWLOLW\ C ! ! $ !$
!
(AC((%DA$!A %?A( $! A$!

C ? >;!231$

! ?A( C ? >

> C( C
!

$
+0,6(59(5
&,03/,&,7< 7&, +LVWRULDQRU

3/&
0RGEXV 0RGEXV '&6
2WKHU &,03/,&,7< &,002'
0DVWHU
6ODYH 0RGEXV
0DQXIDFWXUHU &RPPXQLFDWLRQV 0DVWHU
RWKHU0RGEXV
6ODYHGHYLFHV
LQFOXGH0HWHUV
DQG5HOD\V
)LJXUH'DWD)ORZIURPD1RQ*(3/&WRWKH+LVWRULDQ
(AC((%DA$! !

3C%$ C (AC((%D
&! $ %(%?
>? C

911 of 1016
7DEOH+0,+LVWRULDQ&6)$GGUHVVLQJ
+0, &6)$GGUHVV /81
) $
( $
' $
7DEOH+0,+LVWRULDQ6HULDO$GGUHVVLQJ
+0, &6)$GGUHVV /81

) '
( '
0DUN9DQG0DUN9/0
%%(

! !
"! (

.B% %( !

.B%$
". &RQWURO
3DQHO$SSOHW
0DUN9,
5HIHUWR*(+&RQWURO %>? "! ! $ ?A( A "0(
6\VWHP7RROER[IRUD0DUN9,
% " !!

$#;
7XUELQH&RQWUROOHU 1HWZRUN,QWHUIDFH 2XWOLQH9LHZ
"

0RGLI\ (GLW!
(0B$1$(PLVVLRQV$QDO\VLV
0DUN9/0VXSSRUWVWKLV %
AIB((
XWLOLW\ ?A(.32! "
! !
A "0CA
%
!/A8/ A
:

&RQILJXUDWLRQ)LOH)RUPDW
%)?,2B32576'$7

%
$!$
%

P
WHPBDQDBVHWXSX(

!

! ! !
(
! ! !
#! $R 3

912 of 1016
(3$/RJ
0DUN,90DUN90DUN9/0 %
!!
!
3 !$ ) !
DQG0DUN9,VXSSRUWWKLV #% !

XWLOLW\
!

7KH(3$/RJJHU
%
$!

% $

?A(! @
B% (3$3ULQWHU
)?&21),*'$7

F +
Options
EPA_LOG=Yes
%

$
R
$
!(AC((%D

$
A "0(A "0CA

A "0

% ! (3$3ULQWHU!
$
!

!
!
!

! ! !
!
$! CF(

! )% ! A "0

!
913 of 1016
(3$/2*:HW/RZ12[(3$/RJJHU
/:4,1FOHDU &!'&&
66
&DOFXODWH
DYHUDJHRIHDFK
LQSXWHYHU\
/LVWRILQSXWV PLQXWHEDVHGRQ
IURP RQFHSHUVHFRQG
(3$B%65& VDPSOLQJ
/:4/1
HQDEOH
0LQXWH )RXU0LQXWH$ODUP /:/;0,1

$YHUDJHV ,I:;&!:;-IRU
6WRUHGLQ IRXUFRQVHFXWLYH
WLPH
SRLQWFLUFXODUILOH PLQXWHDYHUDJHWKHQ
VHW/:/;0,1
FOHDU FOHDUGDWD
HQDEOH
+RXUO\$YHUDJH +RXUO\$ODUP /:/;+5

&DOFXODWHGDIWHU ,I:;&!:;-IRU
WLPH HDFKSRLQWV KRXUO\DYHUDJH
KDYHEHHQVWRUHG WKHQVHW
FOHDU /:/;+5
FOHDUGDWD
HQDEOH
)LJXUH(3$/2*0DUN9&RQWUROOHU3RUWLRQ
914 of 1016
(3$/2*:HW/RZ12[(3$/RJJHU
,!3URFHVVRU
&21),*'$7 2XWSXWWR
GLVSOD\
,I
KRXUO\DQG
(3$B/2* <(6 PLQXWH DYHUDJHV
FROOHFWGDWDIURP
&!DQGHQDEOH
RXWSXWV
2XWSXWWRSULQWHU
PLQXWH
DYHUDJH
$OOPLQXWH
KRXUO\DYHUDJH DYHUDJHVIURP
KRXUO\DYHUDJH
FDOFXODWLRQ
HQDEOH HQDEOH
/:/;+5
$1'
,2B32576'$7
2XWSXWWRSULQWHU
(QDEOHRXWSXWWR RQFHDQKRXU
SULQWHUDVVLJQHGWR
(3$35,17 KRXUO\DYHUDJH
YDULDEOH
HQDEOH
HQDEOH
)LJXUH(3$/2*WKH+0,,!3URFHVVRU3RUWLRQ
(3$'DWD'LVSOD\
%A "0

)?81,71?(3$B465&!
@ ! # 8! B :

$
%

(3$B465&!
+
; ----------------------------EPA_Q.SRC-------------------------
; Note that the TIME column header does not have to be defined in this file.
: The header is automatically created when the program is run.
;
; SIGNAL NAME
; -----------
DWATT
CTIM
TTXM
WXJ
WXC
FQG
FQL
CMHUM
;END OF FILE
915 of 1016

!
A "0 $

&! $ @ES8%C;C'@%.3%A.%(F: @E
8&!;C'@%.3%A.%(F:
$
!

( &! @ES @E$
IRXUWK ILIWK 8
:

%
! $ ! (3$B465&
F $ (3$B%65&

! $

Z[
0DUN9,(3$/RJ
%
A "0(

A "0@

!$
" A "0(

%

!
$
!

) ( ! !$
" !3
! !
% !
?A(

! ( ? !

3HUIRUPDQFH0RQLWRU
0DUN9,VXSSRUWVWKLVXWLOLW\ %(IILFLHQF\0DSä äY A ?A(

!

!$ !
! ! !

7KH3HUIRUPDQFH0RQLWRULV
!!

VXSSOLHGE\*((QWHU6RIWZDUH
!
&!
'DYLV&$3KRQH A Y !!

!
!$* $
! (
!

$ "
916 of 1016
$GGLWLRQDO)HDWXUHVDQG)XQFWLRQV
% $ !
!

3

$$

$ODUP3ULQWLQJDQG/RJJLQJ
%
C

% %(

?A(%
C ! !
&!

!F
C!

$#
8ORJJHUH[H: $!

!
!
1RWH> ! (AC((%D
!$
!
%(
C
%
C &!
$ !

%( ! +
• @ B% ! $ $ODUP3ULQWHU! A
%

% !

$

3 ! #
!
%

$# !
• %

! $!

$
! 5 ! ,1
,- 7-

$

$! $

%!
$! !
P
F
C

$ODUP3ULQWHU
$ /RJJHU
&RQWURO
$#
&,03/,&,7<$ODUP3ULQWLQJ
( !(AC((%D
C

(AC((%D
!
$!

!$
;!
!
$ !
Ø7RPRGLI\WKH:LQGRZV173ULQWHUSURSHUWLHVIRU&,03/,&,7<SULQWLQJ
,
6WDUW6HWWLQJV3ULQWHUV

; )LOH!
3URSHUWLHV
2
$
$
6FKHGXOLQJ
3ULQWGLUHFWO\WRWKHSULQWHU
1
2.
917 of 1016
$ODUP+LVWRU\
0DUN,90DUN90DUN9/0 %%(?

!$ $

?A(
DQG0DUN9,VXSSRUWWKLV @$3$ &! $!
XWLOLW\ %

@$$ ! B (
#

3ULQW %3ULQW @

R &!! ! "
F

?A(
!
%@$3$
"! !

!
!
(

!

! V

! %
! %DFN$! $
$ODUP&ROOHFWLRQ

! !%(,-% $

)?&21),*'$7

! F
+
ALARM_HISTORY=YES
%

)?&21),*'$7
! F +
HST_DIR=C:\HMIDATA
( !
+H?A(>%!A "!
+H?A(>%

F
$ !
%

)?&21),*'$7 !
! +
• % $

+
ST_ALM=NO
H
• % $

+
ST_EVT=NO\
H
• % $

F
+
ST_SOE=NO
H
ODUP+LVWRU\LVVLPLODUWRWKH
$ %

? ?A(
+LVWRULDQ+LVWRULFDO$ODUP
%
? !
" +

(YHQW5HSRUW
• % !
!
! $

$"
2 >

2
• %"!
,A/
+0,+RPHSDJH% !

%( $ 8WFLKWP:

+H !$H H%
! !A @$

!
Ø7RFRQILJXUHWKH+RPHSDJH
, ; +0,JROGGLVNWFLKWP F?LQHWSXE?ZZZURRW?GHIDXOWKWP
WFLKWP F?LQHWSXE?ZZZURRW?WFLKWP !@$
"WFLKWP !

.! $ V $ +''

%
.

D!!

! ! $!

$!
.

918 of 1016
+LJK6SHHG'DWD&ROOHFWLRQ
9,(:7
0(@%
!

3 !$ A "

0A "0CA
! !

$!.
1
7UHQG5HFRUGHU
0DUN9,VXSSRUWVWKLVXWLOLW\ ( A "0(
$
$

$#

2%

5HIHUWR*(+&RQWURO
> ?
$#
6\VWHP7RROER[IRU&RQILJXULQJ
A!

$
$ "! 3
D7UHQG5HFRUGHU

!

5HPRWH$FFHVV
.
$ ! . 8.:
! @$% !

5$6±5HPRWH$FFHVV6HUYHU
@!. !
! >

B " $
; ! ! ?A(
%
! . %'(
! B /(
! "
&RQILJXULQJ5HPRWH$FFHVV
%?A(&! $
?A(
!
3! / $!
3!
. 8.: $!@
B%
Ø7RFRQILJXUH5HPRWH$FFHVV5$6
,
"6WDUW 6HWWLQJV &RQWURO3DQHO
>!$

" 1HWZRUN&RQILJXUDWLRQ%1HWZRUN
$#

2
6HUYLFHV $
919 of 1016
6WDUWLQJWKH5HPRWH$FFHVV6HUYLFH
F .! $
Ø7RPDQXDOO\VWDUW5$6XVLQJ:LQGRZV
• ,
"6WDUW 3URJUDPV $GPLQLVWUDWLYH7RROV&RPPRQ
5HPRWH$FFHVV$GPLQ
•
"6HUYHU 6WDUW5HPRWH$FFHVV6HUYHU.
Ø7RPDQXDOO\VWDUW5$6IURPDFRPPDQGSURPSW
w ; &RPPDQG 3URPSW +
net start "remote access server"
(QWHU.
Ø7RVHWXS5$6WRVWDUWDIWHUHDFKUHERRW
,
"6WDUW 6HWWLQJV &RQWURO3DQHO 6HUYLFHV
; 6HUYLFHV !$

"5HPRWH$FFHVV6HUYHU
2 6WDUWXS7\SH $$XWRPDWLF
1
"2.
- .$ ! . $
*60
0DUN,90DUN90DUN9/0 A ! $ !$
DQG0DUN9,FRQWUROOHUV

>%
$
>
VXSSRUW*60

A

$ $#
JDWHZD\ >% ?A( !
!

%
!
A

#
5HIHUWR*(,*60IRU

!B
63(('7521,&7XUELQH !
!
&! $ >&!
&RQWUROIRUGHWDLOV
7&,0RGEXV
0DUN,90DUN90DUN9/0 %A$!Y %(
>
DQG0DUN9,VXSSRUW0RGEXV
@ %(

$0RGEXV6ODYHR %(

$0RGEXV0DVWHU $ $ $
A$!

! .32
! A$!
! .32
!

5HIHUWR*(,0RGEXV (A$!VODYH > &!

IRU63(('7521,&7XUELQH
) $ A$! &! A$!
"
&RQWUROIRUGHWDLOV
%>
!A$!

%
! $ !$! 8! %.%%F:

8!

:A$!

$ A$!
!$
*
920 of 1016
:HE6HUYHU
(

?A(!

! $3$
%?A(
&! $$ !
#! $

"
$
! $ ( @$
! $

Ø7RHQDEOHWKH:HEVHUYHU
, ; 'HVNWRS
" 6WDUW$!
; 6WDUW!
"6HWWLQJV &RQWURO3DQHO
2 ; &RQWURO3DQHO!
"6HUYLFHV
1
:RUOG:LGH:HE3XEOLVKLQJ6HUYLFH
- ; 6HUYLFHV
$#
" 6WDUW$! 3
!
4 $ ! ,QWHUQHW([SORUHU
9 ( " @
@@$!$
! $

6WDUWXS«$! 3
! 6HUYLFHV

$#
7
DXWRPDWLF 2.% $
! !
$
PDQXDO 2.
+0,+RPH3DJH
Ø7RFRQILJXUHWKH+0,GHIDXOWGLVSOD\+RPH3DJH
,
"6WDUW 3URJUDP 0LFURVRIW3HHU:HE6HUYLFHV
,QWHUQHW6HUYLFH0DQDJHU%( A

@
@@$ $$
:::
2
"3URSHUWLHV 6HUYLFH3URSHUWLHV«
1 %( A
! "

$#"( (QDEOH'HIDXOW'RFXPHQW
Default.htm "'LUHFWRU\%URZVLQJ$OORZHG
- %( A
!

c:\inetpub\wwwroot.
%!
?A(? $

+
c:\inetpub\wwwroot\GEDS.
4 ( ! $

+
c:\inetpub\wwwroot\default.htm.
9
" $ ?A(?

$

!
!
!$ ! *

" !

$ ?A(
Ø7RVXEVWLWXWHWKH*(VXSSOLHGSDJH
w ; &RPPDQG3URPSW +
copy c:\inetpub\wwwroot\geds\tci.htm c:\inetpub\wwwroot\default.htm
(QWHU%

921 of 1016
:HE%DVHG'LVSOD\V
@$K$

$
" %

+
0DUN,9DQG0DUN9VXSSRUW 'HPDQG'LVSOD\%

!

WKLVGLVSOD\ $
$ B C
$ C $$
)?:'(0$1''$7

0DUN,99DQG9, 3URFHVV$ODUPV%

!

0DUN9RQO\ 'LDJQRVWLF$ODUPV%

!

0DUN9RQO\ /RJLF)RUFLQJ%

! (

!

0DUN9RQO\ &RQWURO&RQVWDQWV%

!

!
+0,6WDUWXSORJ%

!

?A(
%URZVH%

$"

3RLQW%URZVHU%

!
$5&:+2%

.B
)73,QWHUIDFH
%;%(

?A(%

$
$
IWS3URRW 0 !

$! " IWS3URRW
922 of 1016
7ULS+LVWRU\
*(+9ROXPH,GHVFULEHV ( A "0
$ ?A((
WKH7ULS+LVWRU\SURJUDP A "0( $ ?A(
$#! > ?
%A "0 A "0CA%?

!%(,4 $ $
FA%

!
#
8#

!
?A(( $! :
7ULS+LVWRU\RQWKH0DUN9)LUVW9HUVLRQ
;%(,-
%?

#

;+H.B%(A D! !B

"%.(,%, # %.(%, # %, !

0DUN9DQG0DUN9/0 %! %?
! !$
VXSSRUWWKLVXWLOLW\ %
$

$ !
% P 3 3

%%?
! !

% !!

!

$
@

!!
!

> $ 8>/: $
%
841 #:

8+,67B%65&:

# A "0

! 8+,6B$*(:
)LOH7\SH
9LHZLQJ%%? !

3

#
%

!B $

$! )LOH6DYH$V! B
&RQILJXUDWLRQ%%?
! ! !
+,67B%65&(

$ %? (

!3 $
#

;3 3 8%(A:

> %

# #$
!

%
! $
&!

!$ (
!

#
$
% ! ! %C>
&!
! !
!
!

33 ! 8+,6B$*(: !
#!
!
! ! P
(

+,67B%65&
!

!$ ! +,6B$*(!

$
+,67B%65&

923 of 1016
% ! ! %C

!+
• 'LVDEOHG
$ $
8% !

!:
• 8QVXSSRUWHG%! A "0A "0CA
• 1R/LFHQVH%

• 3HQGLQJ%

$ $

• ,Q3URJUHVVA $#

• 7LPHRXW%
!

&! %

#

• 'HFRGLQJ
$
$

$
• 6DYLQJ% $ 0 $ "
• 'RQH
$
%

#
%

$

$
!
trpfil_trace%
$
$ !

$
%

!
+
Trip Log Collection Status Report
03-SEP-1999 11:03:56 TCI Development
UNIT Collection Unit Trip Buffer Filename

---- ------------ -------------------- ----------------------
T1 Done 01-SEP-1999 17:10:28 19990901_171028_T1_TRP
7ULS+LVWRU\RQWKH0DUN9,
0DUN9,VXSSRUWVWKLVXWLOLW\ A "0(!
$#
%?

!
F
5HIHUWR*(,&RQWURO %
$#
'DWD+LVWRULDQ

%
6\VWHP7RROER[IRU&RQILJXULQJ
$

D7UHQG5HFRUGHU !

!$!
>

$

1! !$!

4
% !
$#7UHQGHUA!

!
3
!
$
?3
!

F

$

;F

! %
%
"
9LHZ
(YHQW/LVW
924 of 1016
'LDJQRVWLF7RROV
%?A(
!$ !$

%DVLF*HQHULF4XHVWLRQV
%
$ &!

!$
! $!

! QRW !
'LGWKHFRQILJXUDWLRQVWRSIXQFWLRQLQJ"
<HV( ! "
!
"$
>

! !
!"

!
1R( ! ! " !

" !
! $

+DVDQ\WKLQJEHHQFKDQJHG"
<HV($
! $

1R(
"! !
$

!

$UHRWKHUFRPSXWHUVIXQFWLRQLQJFRUUHFWO\"
<HV( $

!

FM $

$ $

! V
! !
1R(

! $

$ $

!
" !
2YHUYLHZRI$SSURDFK
% !

! /
!
$
$
; !$
$
$
"
%
)
"
?A(+
• %
$ %(

>
> 8A "0( ! > > :
• >
%( (AC((%D $(A/
• (AC((%D
!
V
( $
$!! 3 33 3 F
!$ # $
$ ! !!

$ " !$ ! !
!

925 of 1016
7URXEOHVKRRWLQJ
% !$

! !

$
! ?A(A $!
!
$! +HE %
!
$
! %?
!
$!
(UURU/RJV
F "

$ ?A(F

! $
! ! %

!! $!

!

%?A(

+HCF %
!

$ !$
$
A

!
%
# %(

7&,/2*

%
! &!"

!$

$
%( %(CF
$! ! 7&,/2*% %(
$
7&,/2*

7&,/2* ! !$
$
&!

(! ! .B%8
" A "0A "0CA
; A "(0: .B%!>

@ B%
( .B%!
$
! !

.B% "!

" @ B%
.B%%

"6WDUW3URJUDPV$GPLQLVWUDWLYH7RROV
(YHQW9LHZHU% ! 6\VWHP
%

$
> > ! A "
0(C ! >

7UDFH*OREDO6HFWLRQV
A ! "

$
B

&!$! ! $! $
! $

$

$ ! $ $

F$!
"
$
$!
!

!

%

$
"
$

@ !
$

$

$
@
$
!

% !
"
$
!
!

%
$
%;
8*%/),/((;(:
$
"

%
$
; #3
$
%

$

(( # !

$
B ,

926 of 1016
%$ !/C;(C
+
GBL2FILE <global_section_name> <filename>
@+
• Z
$
I I [
$

! %
$
$ !

!

• Z
[

!
/
!!
'03# ! !

$
$! &!

! 7;7#
!$

"
$!B
@$ $
$
% @$

$
!
$
!

"
$

%!
$

!
@$$
$
")LOH
6DYH$V
Ø7RDFFHVVWKH:HE*OREDO6HFWLRQ)RUP
, ; @$$ :HE+0, !
.C+
/scripts/GEDS/wgblf.exe
%:HE*OREDO6HFWLRQ)RUP

$

!#
+
?A(A!+ +'',5,47,1

$
;+ +'',5,47,1' '>' $
#
3URGXFW&RGH9DOLGDWLRQDQG9HUVLRQ&KHFN
%?A(! $!
! !$
@
!
"
?A(! $
! $ $
$ ! !(

" ! !$

!
$!

5HIHUWR&KDSWHU8WLOLWLHVIRU %?A(!
! !
"

GHWDLOVRI&+(&.&5& !
"%"
" !
" $! @ !
$! .8
.! ":

! $! %?M.!
.

!
Ø7RUXQ&+(&.&5&
, ; &RPPDQG3URPSW +
CHECKCRC
(QWHU%!

+HCF
(

$!

?A(! $! $

927 of 1016
1RWH !$ ?A(! !
#

$! 8

!$
$! :
.
( $!

!
$ !
!
% $ $

$
!
$
$ !
PXVW! #
!

$

(

$
!

?A(! ! $!
*?'$7$?9(56,21'$7
%

! ." ."

! $!
&RPPXQLFDWLRQ/D\HU
%!
$
!
&! >
> >
$
%
""
> > >
$
!
!
8" >
$
>$

> >
:
5HIHUWR&KDSWHU8WLOLWLHVIRU %
0(@! > > !
GHWDLOVRI9,(: ( !

( V
!
!

! !

%
0(@>! >
$

! ( !

( V
!
!

! !

0(@ 0(@> !!

! "
$
$ ! ! (
$! 3!
! $
( $!
V
!
$ !$

!$
( $! > > >
$

! !
>
" !

0(@ 0(@> > > >

$
%
# >
# A 3 %

F $
0 $
$! !
"

• %
>!T, 8$/0'803(;(:%
>
# A
> C

%
$! $ " !
$
CA>A, $! <'^=&!

c^c
!!

928 of 1016
• %
>!T 8$/0'803(;(:%

!
&!!
%! ! $ $ $! !$CA>A
$! c'^c&!

% $!

?A( ! 8F

$! $

$ $
! 3 ! :
( ! ! ?
Z([ " FM(
!
" !
$ #

"( "
?A(( !
! 8
: $!
! ! # (
"" ! " !
"

!
> !

!
" !
&!"" "!
!
"

!
" !

$

3UHGHILQHG'DWD'XPS
%>> .32

!
> > (
! ?A( !
%
!

)?,2B32576'$7
% / ! !$
$ ! .32 (
!V
!
%>> " ! !$
$ !$! %>> !
83''B67$7(;(:
! .!
!$ ! $!

B
! !

"!
!
!$ "8A R

$!

:.! !
!

" !

! $
( $$! > >
!
!
$

%
! !
$$
! !
)?81,7Q?3''803'$7

%
!
$

! V81,7'$7$'$7
! V(1*/,6+6&$

!
! $
$
"! 8
: >
> A "! "
$

"!
$

" $
!(

$
!

! !
%> >!"

!
$
%
$
$

$
" SGGXPSBWUDFHQ!
$

929 of 1016
0RGEXV2YHU56&
%A$!.32 3# .32

!
> >
%
?A(
%
!

)?,2B32576'$7
/ ! !$
$ ! %

"
$!
(
!V !
# % 8,4$ !,4$ U:
"
!

" ! $

%A$! " ! !$
$ !$! %A$!A
! 800B67$7(;(:
! .!
!$ #

$
$!

.! !
!

" !
!
$# %A$!
! 80B67$7(;(:

! A$!

( $$! > >
!
!
A$! $

%
!
A$! ! $$

! ! )?81,7Q?00EXVQ!'$7
%

!
$
! V
81,7'$7$'$7
! V(1*/,6+6&$

! $
$
" 8
:
> > (
$
!

! !
%A$! "
#
!
$
%
$
$

$
" 00RGEXVBWUDFHQ!
$

0632YHU&6)
0DUN,9VXSSRUWVWKLVXWLOLW\ %A; # ;
%
; " "
)?&21),*'$7
/ >
# A
!
% $
; " .@?F!
!
.@?F "$!
"( !
$$!
.@?F

" $
" $
.@?F
!$! "( !$
$
" $
.! !
!
)
" 83 "
$
" "
"# :
930 of 1016
• % .B%$ ! !

('F ! &!
8(.L:%%(

! .B% !
$ $ ( $

$ !
!

.B% $
8 V .B%$
! :
B% CC"
.B%
( " $
&! !
# $

$
!%/ A
# $ ! "

$ %
$
"
$
$ EHDFRQBWUDFH
$
" 8$
: ?
!
" $
$

(*'2YHU(WKHUQHW
%>
$
$
# >
# .
"
! > #
!

%,&1,1,
># %,&1,1,

V@ > 8
+H@(BB%:(
># $#
>
$

%,&1,1,
$ ?A( !
%
,&1,1,
$ >

@ B% C( ?

?A( >(B(

! $
%!!
?A(> $

! %
$!
$ !

? ! $! ?A(
( $ ! $ ! $$
! (B ! 3,1*(B!

$
! !
!
" $
(!
FM" # ,&1,1,

80 ? :
F !
># !

! ?A(
%>
# A !$ $! "
! $
%
. 8$/05&9(;(:" "

>
# A %
$$
$
DOPUFYBHQHW(
( $!
!
CA>A, ( !
!$$ $
% )?(1(7$/0'$7

A "! ! !$ ! !$
)?&21),*'$7
! ! !$ A "0(
!$
8( ! ! #
:
931 of 1016
0RGEXV2YHU(WKHUQHW
%A$! 3#
"

!
> >
%
?A(
5HIHUWR*(,0RGEXV %
!

IRU63(('7521,&7XUELQH )?,2B32576'$7

&RQWUROIRU0RGEXVGHWDLOV A$!
(
! !
#
% 8,43$ !,43$ U:
"!

" ! $

%A$! " ! !$
$ !$! %A$!A
! 800B67$7(;(:
! .!
!$ #

$
$!

.! !
!

" !
!
$# %A$!
! 80B67$7(;(:

!

( $$! > >
!
!
A$! $

%
!
A$! ! $$

! ! )?81,7Q?00EXVQ!'$7
%

!
$
! V
81,7'$7$'$7
! V(1*/,6+6&$

$ $
$
"! 8
:
> > (
$
!

! !
%A$! "
#
!
$
%
$
$

$
" 00RGEXVBWUDFHQ!
$

932 of 1016
&KDSWHU8WLOLWLHV
,QWURGXFWLRQ
% !?A(!

!.@?F
>!

C;
0(@

@$3$

6HFWLRQ3DJH
( ! 13,

>!,KCA>A, 132

>!3CA>A 132
.@?F 131
F 131
! 3
$ >
13-
A "0!
$ 13-
!$! 134
C! 137
> 137
!
$ >
>
/# 135
A "0(!
$ 135
.>I(> 13,
?M. 13,

>
13,,

13,
A "0(
13,

)! >
13,2
> ! >
13,-
;
% 13,-
> ! >
13,-
>A>.> 3 3! 13
> 3>
3 3! 13-
> >
!;
13-
/C;(CK
$
%;
134
C;>
139
;
! ! 139
C;>
137
A$!C ;
1324
A$!IC 1324
AAI 3A$!A 1327
AI 3A$!
1327
> >! 3>>I%% 1325
*(+$9ROXPH,,$SSOLFDWLRQ*XLGH &KDSWHU8WLOLWLHV••
933 of 1016
0F%K > >
131

C>
/# 131
%
( A 3%(AB 1311
%JA "3%JIAM 131-
0(@ 1317
0(@
1317

0(@
1317
0(@IC(AK0 >
C 1315
F 1315
0(@I>30 >
> 13-,
F 13-,
0(@30 F> 13-
F 13-
0(@,30 F> 13-2
F 13-2
0(@ 13-1
F 13-1
0(@30 > (( 13-9
F 13-9
0(@% 134
F 134
0(@>3
$
> 1342
F 1342
0(@030 ?30 %!$> 134-
F 134-
0(@L30 A!
3?3%!$> 1349
F 1349
@$3/ >
1345
@$>
139
@CA>A3@$
>!
139
@B%K@$.B%! 1392
@.@?FK@$.@?F>
1391
@%?BK@$! 139-
@FB%K@$
>
1394
@>AB>3@$> >
1397
C 137
@/C3@$
$
>
137,
@?.%K@$?

N # . 137
?

! . 1371
@?(%F.D3?

N . $> 1374
@C;F.3@$C;>
1377
@/.F4K@$ / A "0( 1375
A "0(%
$#/ . 135
@/.FE>3@$ / 1357
@.F3@$C 13,
@AI>23@$! O>2;
13,2
••&KDSWHU8WLOLWLHV +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,,
934 of 1016
$ODUP'XPS±$/0'803
#

!CA>A, CA>A
DQG0DUN9,VXSSRUWWKLV %
F $
XWLOLW\
%
>!T, $/0'803(;(
>
# A > C

%
$!
$ "
$
CA>A, $!
'^&!

<^=

!!
%

+
G:\EXEC>almdump1 /?
ALMDUMP1 - Alarm Dump of exception messages.
This program will display the exception messages received from each unit as they
arrive. By default it will show the Process Alarm exceptions, but this can be
changed by supplying a command line parameter indicating the exception list to
display.
Commands can be sent back to the unit to silence, acknowledge, or reset alarms.
Enter “?” while running for a list of valid commands.
COMMAND FORMAT: ALMDUMP1 [list] [/EX] [/NODE=\Nodename]
[list] indicates the exception list to display, which can be:
PALARM or PROCESS......Displays the Process Alarm exceptions
DALARM or DIAG.........Displays the Diagnostic Alarm exceptions
HOLD...................Displays the Hold List exceptions (if used)
EVENT..................Displays the Event List exceptions
SOE....................Displays the Sequence of Events exceptions
/EX indicates to use the Extended interface to provide a formatted dump of the
data records.
/NODE=<nodename> can be used to obtain records from another computer.
$ODUP'XPS$/0'803
>!T $/0'803(;(

DQG0DUN9,VXSSRUWWKLV !
&!! %! ! $ $ $!
XWLOLW\ !$CA>A $! '^&!

% $!
?A(
!
935 of 1016
&$5'B,'
0DUN9DQG9/0VXSSRUWWKLV .>I(> C!
A "0A "0CA

XWLOLW\0DUN9,XVHVWKH .FA !( !!

WRROER[
*.FA&!! !!

!$

1RWH%.>I(> !&KDSWHU8QLW&RQILJXUDWLRQ
&+(&.&5&
%?A(! $!
! !$
@
!
"
?A(! $
! $ $
$ ! !(

" ! !$

!

$!

%?A(!
! !
"

!
"%"
" !
" $! @ !
$! .8
.! ":

! $! %?M.!
.

$!
Ø7RUXQ&+(&.&5&
w ; +?M.
(QWHU%!

*?/2*
(

$!

?A(! $! $

1RWH !$ ?A(! !
#

$! 8

!$
$! :
.
( $!

!
$ !

!
% $ $

$ !
$
$
!PXVW! #
!

$

(

$
!

?A(! ! $!
*?'$7$?9(56,21'$7
%

! ." ."
! $!
936 of 1016
&RQWURO&RQVWDQWV'LVSOD\
0DUN9DQG0DUN9/0 %?A(
>

!
VXSSRUWWKLVXWLOLW\0DUN

!

! *
,9XVHVWKHORFDORSHUDWRU
;
!
!

LQWHUIDFH )! >
)! $

0DUN9,XVHVWKHWRROER[ %
>
$

%

!
+
•
•
%! $ ! %

!

+
•
• 0
!
•
%
B )! $

%
! )! $
&! "

! 8. %: %&! "

!! ! #!
!/
!
&! " $

7DEOH0HQX6WUXFWXUH
0HQX 0HQX,WHP 'HVFULSWLRQ

)LOH 3ULQW 6HQGZKDWLVRQWKHGLVSOD\WRDSULQWHU
3ULQW6HWXS 6HOHFWWKHGHVLUHGSULQWHUDQGLWVVHWXS
([LW ([LWWKH&RQWURO&RQVWDQWVGLVSOD\
(GLW 6HOHFW8QLW 6HOHFWWKHXQLWFRQWUROOHUZLWKZKLFKWKH&RQWURO&RQVWDQWVGLVSOD\ZLOOFRPPXQLFDWH
)LQG3RLQW %ULQJVXSWKH)LQG3RLQWGLDORJER[)URPWKLV\RXFDQORFDWHDSRLQWLQWKHOLVW
6HW3RLQW 7KLVGLDORJER[VHWVWKHIRQWWKDWERWKWKHKHDGHUDQGWKHGDWDOLVWZLOOXVH
6HW'HIDXOW 7KLVVHWVWKHIRQWDQGFROXPQZLGWKVEDFNWRWKHV\VWHPGHIDXOW
9LHZ 7RRO%DU 7RJJOHVWKHWRROEDURQDQGRII
6WDWXV%DU 7RJJOHVWKHVWDWXVEDURQDQGRII
+HOS $ERXW&RQWURO 7KLV'LDORJER[VKRZVWKHUHYLVLRQOHYHORIWKH&RQWURO&RQVWDQWV'LVSOD\
&RQVWDQWV
%
>
$"
!
(
!
>

! (!

! !
! ;#
!
+
*?(;(&?&2167'6381,77
%

$

/ $ 1R9DOLG'DWD(

937 of 1016
&KDQJLQJD&RQWURO&RQVWDQW
F

!# $ )! >!$
3
"
$ )! F! " $ )!
(QWHU
)LJXUH±&RQWURO&RQVWDQWV'LVSOD\
0DUN9,&RQWURO&RQVWDQWV
A "0(!
$# "
%
$#

0 %

0
!(
0
!%
B

$

!

; ?3412&RQWURO6\VWHP7RROER[IRU
&RQILJXULQJD0DUN9,&RQWUROOHU
938 of 1016
&RQWURO&RQVWDQWV$GMXVW'LVSOD\
0DUN9DQG0DUN9/0 %?A(
)! >

! )!

!
VXSSRUWWKLVXWLOLW\
)! $
%

%

! $
!

(

!
!A

)! >
$ %
$P
8
!
$ :
0DUN9,XVHVWKHWRROER[ %
)! >
$"

(
$#

%
! +
32,1781,7!32,171$0(!
%! &!!
! #
+
*?(;(&?&2167$'-32,177&6.$76
%!

! #
+
*?(;(&?&2167$'-32,17&6.$76
+HDGHU7LPHWDJ
%
)! >

!+6LWH1DPH8QLW
1DPH &XUUHQW7LPH$ ! %

$
/ $
1R9DOLG'DWD(

)LJXUH±&RQWURO&RQVWDQWV$GMXVW'LVSOD\
939 of 1016
*%/),/(±*OREDO6HFWLRQ7R)LOH
$
%;
!
!
DQG0DUN9,VXSSRUWWKLV $ "! %( (
XWLOLW\ "
$
P $!!

A ! $ "! %(
"
$
%

$

! $

$:HEEDVHGYHUVLRQLVDOVR %
$
%;
8*%/),/((;(:
!

DYDLODEOHUHIHUWRWKH:HE
$
"
%
8WLOLWLHVVHFWLRQIRUPRUH
$
!!
(( # !

$
GHWDLOV
B %$
!/C;(C
+
GBL2FILE <global_section_name> <filename>
%QDPHV
+
• Z
$
I I [
$
%
$

$ !

!

• Z
[

!
!
'03
# !
$
!$!
&! 7;7# ! !$
3
"

$! ((

>
$
!!
&!
"

" %
$!
$ $

$

940 of 1016
/RJLF)RUFLQJ'LVSOD\
0DUN9DQG0DUN9/0 ; %C;>

VXSSRUWWKLVXWLOLW\
8,:
;
0DUN,9XVHVWKHORFDOFRQWURO #
! !$
$ "
SDQHOIRUIRUFLQJQRWWKH+0,
$

!
$
0DUN9,XVHVWKHWRROER[

!
C; $

2QO\TXDOLILHGSHUVRQQHONQRZOHGJHDEOHDERXWWXUELQH
FRQWURODQGSURWHFWLRQVKRXOGXVHWKH/RJLF)RUFLQJ
IXQFWLRQV,PSURSHUXVHPD\DGYHUVHO\DIIHFWWKHFRQWURO
DQGSURWHFWLYHIHDWXUHVRIWKHFRQWUROV\VWHP
%C;>

!

%

>

$
"C;>

;#

C;>

> ;C

C
;>
!
(

C
;>

$ #

;

!
! # %C;>

!

$GHOD\RFFXUVEHIRUHIRUFHG/RJLFVLJQDOVDSSHDURQWKH
/RJLF)RUFLQJ'LVSOD\VFUHHQ:KHQRSHQLQJDILOHZDLWD
IHZPRPHQWVIRUDOORIWKHIRUFHGVLJQDOVWRDSSHDUSULRUWR
WDNLQJDQ\DFWLRQ
)LOH6WUXFWXUH
%C;>

#! $

*?(;(&?/)25&((;(B

%C;>

#

7;7# B C;>

! C
;>

!

( $!!
!

%

! ;+H
$! ! ;+H.B%(A
C;>

!> >

$

!
C;>
$
!

> >
941 of 1016
)RUFLQJDQG8QIRUFLQJ/RJLF6LJQDOV0DUN9,
A "0(!
$#
?A(;
(3
412&RQWURO6\VWHP7RROER[IRU&RQILJXULQJD0DUN9,7XUELQH&RQWUROOHU%
$ !
+
Ø7RIRUFHDORJLFVLJQDO
, F
$# !
2QOLQH $
! ! 8
:
2 0 0DMRU 0LQRU5HYLVLRQV

!
$

1 $

/HYHO
- 0
&!
4 >!$

"

!%
$#

6WDUWLQJWKH/RJLF)RUFLQJ'LVSOD\
Ø7RVWDUWWKH/RJLF)RUFLQJ'LVSOD\
, ; "
/RJLF)RUFLQJ'LVSOD\
; &RPPDQG /)25&( (QWHU
6WDUW5XQ
/)25&(
"(QWHU
2 %/RJLF)RUFLQJ'LVSOD\

%C;>
! $

! ! %/)25&($

%! ! +
/UNIT:
/FILE:
%81,7+ ! > >

! &! ;#
+
F:\RUNTIME>LFORCE /UNIT:T1
! !$! $

!

! !

8QLW6HOHFWLRQ
$#
! !
!

!
%C;>

$

! ! ),/(%),/(+ ! C
;>

&! C;>

;
#
+
F:\RUNTIME>LFORCE /FILE:LFORCE2.TXT

+
F:\UNIT1>LFORCE /FILE:F:\RUNTIME\LFORCE2.TXT
% ! &!

!
$#

"
$
"C;>

942 of 1016
0RGEXV/LVW)LOH*HQHUDWRU
5HIHUWR*(,0RGEXV A$! $! ! $ !$

IRU63(('7521,&7XUELQH
A$! !
&RQWURO !
A (AC((%DQA$!A
% !A$!
! $ ?A(

$!
8>:
%%!$
( 8%(: ?A(
! >%.FB( !$

!

(AC((%D %(A$!

!
" ?A( >

!!

!$

%A$!
"
> !$

!$ !
! @ > ?A(
" 0RGEXV6ODYH
%?A(
!0RGEXV0DVWHU

! $

8C:;
#
?A( !

" /
B
!&! !$$ @ ?A(!A$!
A
! !
>
? (A$! %( A$!

% &! %( $ $
! A$!

&,03/,&,7<0RGEXV0DVWHU ! ! C

$

8/F:&!
!; !C
! !C
0RGEXVB/
@ %(8%!$
( : A$!
"
!$ +
0DUN9DQG0DUN9/0VXSSRUW ( ! %(> > A$!
!
WKLVXWLOLW\ AF>/>%
! !
AF>/IC!

$

0DUN,9DQG0DUN9,VXSSRUW ( !
$(AC((%D A$!
!
&,002'B/ (AAF>>%(AAF>IB>%
(AC((%D(%I.FF%
(AAF>IC!

$

943 of 1016
2SHUDWLRQ
02'%86B/
!
! ! !
( &!
$!
$

!

(! '^
!

#
+
F:\UNIT1>MODBUS_L /?
MODBUS_L: MODBUS LISTING PROGRAM
Command format: MODBUS_L [options] options:
ENGLISH, METRIC, CUSTOM, HARDWARE
These options control the scale code set used to supply the gain,
offset, and engineering units for each point.
RS16, RU16
These options control the formatting of the raw data, with the
appropriate changes to the gain and offset for each point.
QUIET
This option disables the printout to the terminal of messages
indicating that a point name was not found in the dictionary.
The messages, however, will be indicated in the MODBUS.LST file.
NOLONG
This option produces a MODBUS.LST file without longnames.
LONG
This option makes a MODBUS.LST with a nonlogic longname field of
66 characters. The nonlogic longname field default is 40 char.
/LOG
Redirect output sent to the screen into MODBUS_L.LOG.
F:\UNIT1>
AF>/IC!

A$! !$
!$

%
02'%86/67
%02'%86/67
!
! A A$!
"
)?81,7Q?02'%86/67

$
+
+HR0001 | SWREF_CMD | SIGN16 | 512 | 0 | MW |

+HR0002 | DRVAR_CMD | SIGN16 | 512 | 0 | MVAR |
+HR0003 | SC43LOAD | UNS16 | 65536 | 0 | STATE |
HR0004 | @SPARE | spare |
HR0005 | @SPARE | spare |
+HR0006 | L90PSEL_CMD | SIGN16 | 512 | 0 | MW | PRESELECTED LOAD ANALOG SETPOINT
+HR0009 | SC43 | UNS16 | 65536 | 0 | STATE | TURBINE CONTROL SELECTION
HR00010 | SS43 | UNS16 | 65536 | 0 | STATE | TURBINE COMMAND STATE SELECTION
HR0200.00| L52GX | PACKED | GENERATOR BREAKER CLOSURE
HR0200.01| L94X | PACKED | NORMAL SHUTDOWN
HR0200.02| L30D_SD | PACKED | NORMAL DISPLAY MESSAGE “SHUTDOWN STATUS”
HR0200.03| L30D_SU | PACKED | NORMAL DISPLAY MESSAGE “STARTUP STATUS”
+HC0001 | L1FAST_CPB | LOGIC | FAST LOAD START SIGNAL
+HC0002 | L1START_CPB | LOGIC | START SIGNAL
+HC0003 | L70R4R_CPB | LOGIC | SPEED SETPOINT RAISE COMMAND PUSHBUTTON
+HC0004 | L70R4L_CPB | LOGIC | SPEED SETPOINT LOWER COMMAND PUSHBUTTON
944 of 1016
00BVWDW0RGEXV0DVWHU6WDWLVWLFV
@%( A$!A #
A$!A !!
8AAI%%: $!
# !

%A$!A "!
$

!% 00BVWDWH[H

! A$!A

! .!AAI
! +
)?86(5!PPBVWDW
A$!A
! +
0RGEXV0DVWHU
17,-_! $A$!A
_! $ $A$!A
17,-_! !!

_! #

_! !
_! $!!

_! .
_! $
0RGEXV0DVWHU
17,-_! $A$!A
_! $ $A$!A
191-_! !!

_! #

1-_! !
_! $!!

_! .
-_! $
@!

A$!A !
)?,2B32576'$7

%! $ $ UHVHW 00BVWDW
5HVHW
0BVWDW0RGEXV6ODYH6WDWLVWLFV

AI
$
A$!
%
! $ ?A( #

>%

AAI

945 of 1016
3UHGHILQHG'DWD'XPS6WDWLVWLFV3''B67$7
0DUN,9VXSSRUWVWKLVXWLOLW\ @ A "(0! > >!
> >! !!
8>>I%%: $!
!( !

A "(0>> %

3''XPS'$7
+
Mark IV Predefined Data Dump statistical summary:

PDDump 1.
0 = Number of bytes we tossed while waiting for start of new message.
0 = Number of times we got a new message with a channel # above 8.
1 = Number of times we started a new message without finishing previous.
0 = Number of complete message received with a bad checksum.
0 = Number of messages stopped due to intercharacter timeout.
0 = Number of messages stopped due to buffer full.
217 = Number of good messages received.
0 = Number of good messages ignored due to mismatched message size.
217 = Number of good messages processed.
PDDump 2.
0 = Number of bytes we tossed while waiting for start of new message.
0 = Number of times we got a new message with a channel # above 8.
0 = Number of times we started a new message without finishing previous.
0 = Number of complete message received with a bad checksum.
0 = Number of messages stopped due to intercharacter timeout.
0 = Number of messages stoped due to buffer full.
220 = Number of good messages received.
0 = Number of good messages ignored due to mismatched message size.
220 = Number of good messages processed.
%#

$

$
!
!$ W>>AI%] !$ !
)?,2B32576'$7

946 of 1016
3927(±3UHYRWH'DWD'LVSOD\
0DUN9VXSSRUWVWKLVXWLOLW\ %?A( > >

('F
0DUN9,XVHV760RUWKH
!$

! !
WRROER[VHHODWHULQWKLV %
!!
!$

('F
FKDSWHU %

(

2SHUDWLRQ
% > >
$
%

!6LWH1DPH8QLW1DPH &XUUHQWWLPH$ !
%
#
!+3RLQW1DPH9RWHGYDOXH5YDOXH6YDOXH7
YDOXH 8QLWV%
$

"

%

! #
3.3

7DEOH0HQX6WUXFWXUH
%XWWRQ 0HQX,WHP 'HVFULSWLRQ

)LOH 3ULQW 6HQGZKDWLVRQWKHGLVSOD\WRDSULQWHU
3ULQW6HWXS 6HOHFWDQGVHWXSWKHGHVLUHGSULQWHU
([LW ([LWWKH3UHYRWHGLVSOD\
(GLW 6HOHFW8QLW 6HOHFWVWKHXQLWWKH3UHYRWH'LVSOD\ZLOOFRPPXQLFDWHZLWK
)LQG3RLQW %ULQJVXSWKH)LQG3RLQWGLDORJER[)URPWKLV\RXFDQORFDWHDSRLQWLQ
WKHOLVW
6HW)RQW 7KLVGLDORJER[VHWVWKHIRQWIRUERWKWKHKHDGHUDQGWKHGDWDOLVW
6HW'HIDXOW 7KLVVHWVWKHIRQWDQGFROXPQZLGWKVEDFNWRWKHV\VWHPGHIDXOW
9LHZ 7RRO%DU 7RJJOHVWKHWRROEDURQDQGRII
6WDWXV%DU 7RJJOHVWKHVWDWXVEDURQDQGRII
)UHH]H'DWD 7KLVIXQFWLRQVWRSVWKHXSGDWHRIWKHGDWDRQWKHVFUHHQ,IWKHOLVWLV
VFUROOHGWKHQHZHQWULHVZLOOQRWEHXSGDWHGXQWLOWKHGDWDLVXQIUR]HQ
+HOS $ERXW3UHYRWH 'LDORJER[WKDWVKRZVWKHUHYLVLRQOHYHORIWKH3UHYRWH'DWD'LVSOD\
&RPPDQG/LQH'HVFULSWLRQ
% > >
$"
! (

! >
! (
!
!
!
! ;#
+
*?(;(&?3927(81,77
+HDGHU7LPHWDJ
%? %

$

/ $ 1R9DOLG'DWD(

947 of 1016
.
%C
3CF.K
0DUN,90DUN90DUN9/0

!$
$ !

DQG0DUN9,VXSSRUWWKLV %$ODUP/RJJHU
!

XWLOLW\ ! ! D!!
!
$
!
%! $
+
•

• >

•
• F3&!
% ! !

!

)LJXUH7KH$ODUP/RJJHU&RQWURO'LDORJ%R[
8VLQJWKH$ODUP/RJJHU'LDORJ%R[
%$ODUP/RJJHU&RQWURO
$#
! !
C
A "

+
•
$
•
!
•
!

• ;
!$!

•
948 of 1016
6HOHFW,QIRUPDWLRQWREH3ULQWHG
%! $

>
F
&RQILJXUDWLRQRIWKHLQGLYLGXDO Y
Y "$#

C
SRLQWVLVQRWDIXQFWLRQRIWKH $
!
$ODUP/RJJHU&RQWURO
6HOHFW8QLW
$
! $ %!
$ $
! 6HOHFW8QLW$#

$
%
+
• $OO8QLWV%
$!

! !
!
• )OXVK%XWWRQ%;
!$!

)$

DOO! %;
!$! "
&! FM$! $
• 6DYH6HWWLQJV
C RQO\
!
"2.
$ODUP/RJJHU&RQWURO
$#
• )LOH7\SH%
C

"
( ! !

$

$
C

([HFXWLQJWKH$ODUP/RJJHU&RQWURO
%
C
$
!

! &!"
$
!
D! !
! P !
ORJJHUH[H 5XQ
$# 6WDUW!
!$

"
%
#
! 81,7 7
G:\EXEC\LOGGER.EXE /UNIT:T1
949 of 1016
7HUPLQDO,QWHUIDFH0RQLWRU7,01
0DUN9DQG0DUN9/0 A "0

%(AB8%
VXSSRUWWKLVXWLOLW\7KLVLVQRW ( A :!$

!$

LQWKH+0, $

! $
!

('F
$ ZL[Z[ ! .32
53 >

$

!
+
• /K/A8/ A :&
• K! /A
• >K>A8>!
A: !
• KA
• (3
('F$
• CKC !

)RU0DUN9,GLDJQRVWLFGDWD A A "0( !%A8%
A :

LVLQWKHWRROER[
3$ ('F

$ (
$# #
> ? ; ?341,63(('7521,&0DUN
9,7XUELQH&RQWURO
950 of 1016
:HE%DVHG'LVSOD\V
@$
$
?A( @$3$
%@$

$

! ?A(

"%

$
!

• :$/0'803@/
>!>
%

%(
&!!%!
&!!

>
?
C $

!
$

• :$1(7&@/.B%! >
%
! .B%
• :$5&:+2@/.B% !>
%

.B% $
?A(( !!
$!.B%
! $

• :$87+(1@/! % @/
!
*@/ (
!
$ ! ! ! $

&!
• :&2167@/
>
%

!
!
A "0A "0CA
• :'(0$1'@/> >
> > %
!
!
> > $ !
%

!
&!
• :*%/@/
$
>
%

$!
$

$
$

$

• :+$(537@/?

. %

!

! % ?A(?

• :+,6725<@/?

. $> %!

!

!

#

• :/)25&(@/C;>
%

!
A "0A "0CA

• :3%52@/ / A "0(%

$
A "0(

!$

! $ !
• :3%52;'@/ / > > %

$
> > $ !

! A "0 A "0CA
951 of 1016
• :352&(66@/C %

! ?A(
• :680B'@/! >2;
%!

#
(
$!

!

# '

$FFHVVLQJWKH:HE'LVSOD\V
Ø7RDFFHVVWKH:HEGLVSOD\VIURPWKH+0,
, ; 'HVNWRS
6WDUW3URJUDPV @$$ 8!!

( #
:
%@$$

2 (
! ? +
+''

1
"(QWHU%7&,,QIRUPDWLRQ@$?

(! ?A($! ! ?A($
" @$
$ !@$$ $ +
+''Z of your pc>
952 of 1016
)LJXUH7&,,QIRUPDWLRQ'LVSOD\
953 of 1016
:$/0'803:HE$ODUP'XPSGLVSOD\
! %(
&!!
>
?
C !
$
XWLOLW\
%@CA>A
%(
? *&XUUHQW3URFHVV$ODUPV &XUUHQW'LDJQRVWLF$ODUPV
$

&!! %(!$ ! @$
&XUUHQW'LDJQRVWLF$ODUPV

$
A "0

!
! ! !
% @CA>A@$
+
+''Z[' '>'@CA>AE?
%
$!
$!(
!

$

$
$!
&!!!
$
!
$ $ @$
$!
+
+''Z[' '>'@CA>AE^Z [6Z [6Z [U
)LJXUH:HE$ODUP'XPS'LVSOD\
954 of 1016
;#

$ !

!$ !
$
+
+''Z[' '>'@CA>AE^C.A6>.F
D! $
?FC>
%!$ A "0
A "0( $
@$!+

<A HREF=”/scripts/GEDS/walmdump.exe/HOLDS.TXT?HOLD”>Current Hold List</A>
%
!
+
PALARM - (default) Show the Process Alarm Queue
DALARM - Show the Diagnostic Alarm Queue
DIAG - Show the Diagnostic Alarm Queue
HOLD - Show the HOLD queue (if present)
TIME - (default) Show the records sorted by TIME

DROP - Show the records sorted by UNIT NUMBER and DROP NUMBER
:$1(7&±:HE$5&1(7&RXQWHUV
0DUN,90DUN9DQG0DUN9 %@$.B%! $!
/0VXSSRUWWKLVXWLOLW\ !!
&! $

$
%

! %(@$? %

!$
B%
8.B%! : 3

@$

%
@$
.C+
+''Z[' '>'@B%E?
% %(?
>$!

( +
<A HREF=”/scripts/geds/wanetc.exe”>ARCNET Driver Counters</A>

!
!% !

+
/D - show diag counters (default)
/P - show protocol info
/S - show state info
/R - reset diag counters

/I - diag counter information
% $$ &! &! "
.C
$

(!

!<6=;#

.B%
$
!
+
<A HREF=”/scripts/geds/wanetc.exe?/p”>ARCNET Driver Protocols</A>
955 of 1016
:$87+(1±:HE$XWKHQWLFDWLRQRI8VHU
! @$3$
$!

!
$

!(

!! !
$

! &!!

!
$
F @$" !

! $
"
@ !
@$
&!! !
! !
$#(
! !

&! F ! $ ! @$$
!

&! ! !
$
@$$
$! !
$ #
%@$ ! @%?B " !

! ( $ "! ! (!
! ! $ "
! !
B
&! !D! $

!
&! %
! ( !
$
$! ! !
!

!
956 of 1016
:*%/:HE*OREDO6HFWLRQ'LVSOD\
0DUN,90DUN90DUN9/0 %@$
$
! $
DQG0DUN9,VXSSRUWWKLV ! $ "! $!! %(
XWLOLW\ (
$
@$
$ @$$
A ! $ "! %(
"
$
%

$ R

! $
$!
%@$
$

$!

$

D!
"

%
! ! 5()5(6+5(/2$'$!
$
>
$
!!
&!
"

" %
$!
$ $

$

)LJXUH:HE*OREDO6HFWLRQ'LVSOD\
957 of 1016
:+$(537±:HE+LVWRULFDO$ODUP (YHQW([FHSWLRQ5HSRUW
0DUN,90DUN90DUN9/0 %?

# . !!

P ?A(# !
XWLOLW\
F $

"!!

"! % ! ?A( !
)LJXUH+LVWRULFDO$ODUPDQG(YHQW([FHSWLRQ5HSRUW
958 of 1016
% !!
+
• !

• >

• %
• . *
%. ! !

+
• % # 8
:
•
• !

+
3 , "! !
3 C
" !
"
• F !$

• >
+
3 CA

3 0%
3 F&!
• > #
$
( $
%
#
$ % ! &!
! %DFN$! $$
$
959 of 1016
+LVWRULFDO$ODUPDQG(YHQW6XPPDU\5HSRUW
?

! . !!

P
%
&!

!
(

&!
!!

! # ! ! "
!

)LJXUH+LVWRULFDO$ODUPDQG(YHQW6XPPDU\5HSRUW
960 of 1016
% !!
+
• !

• >

• %
• . *
• .
%

! !
>
!$
!$
F%! !

+
• B!$"! !$!
• !$
" !$!
"
•
•
• >!$
> # %! !

F+
• B!$"! !$!
•
• F
• > #
( $ #
$ % !
&!! %DFN$! $$
$
961 of 1016
:+,6725<+LVWRULFDO$ODUP (YHQW5HSRUWE\'D\
@ ?

$
%( 23

F ?A( %
! @$3$ ?

$ !

(

?A(!

%?

. $>
!
"

+
•

#
• !

*
•

3
%GD\$ !%

( !

!
%

<<<<00''B '
+
• DDDD !
• AA
• >>
• ***
+
3 CA_

3 0%_
3 F_&!
• >2
#
2
%

+H?A(>%%
$
$ ?%I>(._Z [ F
)?&21),*'$7
?

F
!
$ODUPB+LVWRU\ <HV
%?

. $> @$

%
$ $

%
$

! ?%AC $
! $!
!

$%

$!

/
! !

!

?A(
2

! $
$ $

" $

!

!
" 9LHZ

6XPPDUL]H
'RZQORDG

(!

!

" 'RZQORDG
"
6DYHWDUJHWDV6DYHOLQNDV
962 of 1016
%0
?

! P
?

. *!
%

! $
$

! %
%

8% !

# ! @$!:

(! @?(%F.D %(@/!

$!%
$

!

>

! >$!( !+
<LI>
<A HREF=”/scripts/GEDS/whistory.exe”>Alarm, Event, and SOE files (List mode)</A>
</LI>
<LI>
<A HREF=”/scripts/GEDS/whistory.exe?Table”>Alarm, Event, and SOE files (Table mode)</A>
</LI>
963 of 1016
:3%52±:HE3RLQW%URZVHUIRU0DUN9,
0DUN9,VXSSRUWVWKLVXWLOLW\ %A "0(> $ /
! $!

!>
! A "0(>
# D! ! P

Ø$FFHVVLQJWKH0DUN9,7RROER[3RLQW%URZVHUIRUP
, ; 'HVNWRS!$

" 7&,0HQX%7&,,QIRUPDWLRQ
$$

)LJXUH:HE3RLQW%URZVHU
;+0,,QIRUPDWLRQ
" 3RLQW%URZVHU'DWD'LFWLRQDU\ #
%0DUN9,7RROER[%URZVHU6HOHFW2SWLRQV
%
!
!

> %

;+HB(%D!!
!

A "0(%
$#
#

)?81,7?*0%
964 of 1016
)LJXUH0DUN9,%URZVHU)RUP
Ø7RYLHZWKH0DUN9,7RROER[5HSRUW
, ; 0DUN9,7RROER[6HOHFW2SWLRQV
!

%$ $

@

" 6XEPLW$! %&! A "0(
%
$#.

965 of 1016
%
$ A "0(%

$#/ K

F

6HOHFWLQJWKH3RLQWV
$ $

! *71

6HOHFWLQJWKH/LVW7\SH% !

(*' !
>#

># !$ A "0(
6LJQDO
!

$

A "0(

(*'([FKDQJH
! $! >
#
6HOHFWLQJWKH'LVSOD\7\SH% !
7H[W/" &69
$! ! !
$ 0 $

!

> $

6HOHFWLQJWKH)LOH/RFDWLRQ%A "0(%
$#
!

966 of 1016
0DUN9,7RROER[%URZVHU5HSRUWV
% +>
>#

C

(*'5HSRUW
%>

!

! !(> ># # !$ *
# # !$8! !:
> (
%
$#4

?A( !
# ;

%
$#4,1$
% *

)LJXUH(*'5HSRUW
967 of 1016
%0
!
> $

Ø7RORDGWKH(*'5HSRUW&69ILOHLQWRDVSUHDGVKHHW
• ; 0 (*'5HSRUW
! )LOH
• ; )LOH !
6DYH$V
FVY
#
• ;

%
#

0 +
...Site: HSTLAB1
...Unit: GT8
...List: EGD—Signals available over EGD
...Time: 16-MAR-2000 14:46:32
PointName,ProducerID,Xchg#,Offset,Rev,EGDType,EngUnit,Description
TH1,GT8_EGD,14,0,0.2,WORD,”N/A”,”GT8\OPSYS\TH1”
TH2,GT8_EGD,14,2,0.2,WORD,”N/A”,”GT8\OPSYS\TH2”
L1START_CPB,GT8_EGD,15,0.0,1.0,BOOL,”N/A”,”Master start signal”
L1FAST_CPB,GT8_EGD,15,0.1,1.0,BOOL,”N/A”,”Master fast load start signal”
L1STOP_CPB,GT8_EGD,15,0.2,1.0,BOOL,”N/A”,”Master Stop Signal”
L43CDOFF_CPB,GT8_EGD,15,0.3,1.0,BOOL,”N/A”,”Cooldown/Hydraulic Ratchet Off Command Pushbutton”
L43CDON_CPB,GT8_EGD,15,0.4,1.0,BOOL,”N/A”,”Cooldown/Hydraulic Ratchet On Command Pushbutton”
L83DT1_CMD,GT8_EGD,15,0.5,1.0,BOOL,”N/A”,”Diesel Test Enable State”
L70R4R_CPB,GT8_EGD,15,0.6,1.0,BOOL,”N/A”,”Speed Setpoint Raise Pushbutton”
L83SCI_CMD,GT8_EGD,15,0.7,1.0,BOOL,”N/A”,”Icoch/Droop Select Command”
L70R4L_CPB,GT8_EGD,15,1.0,1.0,BOOL,”N/A”,”Speed Setpoint Lower Pushbutton”
L83DRP_CMD,GT8_EGD,15,1.1,1.0,BOOL,”N/A”,”Droop Select Command”
L83WQON_CPB,GT8_EGD,15,1.2,1.0,BOOL,”N/A”,”NOx Injection on pushbutton”
L83WQOF_CPB,GT8_EGD,15,1.3,1.0,BOOL,”N/A”,”NOx Injection off pushbutton”
L43BWON_CPB,GT8_EGD,15,1.4,1.0,BOOL,”N/A”,”Operator Select Water Wash On Pushbutton”
L83WWOFF_CPB,GT8_EGD,15,1.5,1.0,BOOL,”N/A”,”Online Water Wash Off Pushbutton”
LGVENT_O_CPB,GT8_EGD,15,1.6,1.0,BOOL,”N/A”,”Gas Vent Valve Open Permissive Pushbutton”
LGVENT_C_CPB,GT8_EGD,15,1.7,1.0,BOOL,”N/A”,”Gas Vent Valve Close Permissive Pushbutton”
LGMAIN_O_CPB,GT8_EGD,15,2.0,1.0,BOOL,”N/A”,”Gas Main Valve Open Permissive Pushbutton”
LGMAIN_C_CPB,GT8_EGD,15,2.1,1.0,BOOL,”N/A”,”Gas Main Valve Close Permissive Pushbutton”
L83TVON_CPB,GT8_EGD,15,2.2,1.0,BOOL,”N/A”,”Simple Cycle Operation Select”
L83TVOFF_CPB,GT8_EGD,15,2.3,1.0,BOOL,”N/A”,”Simple Cycle Operation Select”
L83GVMAN_ON,GT8_EGD,15,2.4,1.0,BOOL,”N/A”,”IGV Manual Control On”
L83GVMAN_OFF,GT8_EGD,15,2.5,1.0,BOOL,”N/A”,”IGV Manual Control Off”
L86MR1_CPB,GT8_EGD,15,2.6,1.0,BOOL,”N/A”,”Master Reset”
L4DE1,GT8_EGD,15,2.7,1.0,BOOL,”N/A”,”Diesel Engine Starting/Running Indication”
L4DS,GT8_EGD,15,3.0,1.0,BOOL,”N/A”,”Master Control - Diesel Engine Starter”
L83WQ,GT8_EGD,15,3.1,1.0,BOOL,”N/A”,”NOx Control Selection Logic”
L43A,GT8_EGD,15,3.2,1.0,BOOL,”N/A”,”Auto Mode Selected”
L43C,GT8_EGD,15,3.3,1.0,BOOL,”N/A”,”Crank Mode Selected”
L43CA,GT8_EGD,15,3.4,1.0,BOOL,”N/A”,”Cable Remote Selected On”
L43F,GT8_EGD,15,3.5,1.0,BOOL,”N/A”,”Fire Mode Selected”
TNRI_CMD,GT8_EGD,16,0,0.2,REAL,”N/A”,”Isoch Speed Setpoint Command Variable”
SC43LOAD,GT8_EGD,16,4,0.2,DWORD,”N/A”,”Enumerated State: Load Reference Command.”
SC43F,GT8_EGD,16,8,0.2,DWORD,”N/A”,”Fuel selection enumerated command state”
CSRGVMAN_CMD,GT8_EGD,16,12,0.2,REAL,”N/A”,”IGV Setpoint Command Signal”
SC43GEN,GT8_EGD,16,16,0.2,DWORD,”N/A”,”Generator Control Selection”
L90PSEL_CMD,GT8_EGD,16,20,0.2,REAL,”N/A”,”Preselect Load Setpoint Command”
DRVAR_CMD,GT8_EGD,16,24,0.2,REAL,”N/A”,”VAR Control Manual Reference”
968 of 1016
6LJQDO5HSRUW
%

!

!
$ A "0( (

%
$#4
?A( !

#
;
%
$#4,1$
% *

)LJXUH6LJQDO5HSRUW
%0
!
> $

Ø7RORDGWKH6LJQDO5HSRUW&69ILOHLQWRDVSUHDGVKHHW
, ; 0 6LJQDO5HSRUW
! )LOH
; )LOH !
6DYH$V
FVY
#
2 ;

969 of 1016
%
#

0 +
...Site: HSTLAB1
...Unit: GT8
...List: Signal—Signals defined for this unit
...Time: 16-MAR-2000 14:49:11
Signal,DataType,EngUnit,Description
AATCD,Float,”N/A”,”Atomizing Air Temperature Degrees F”

ACC1_TRENAB,Bool,”N/A”,
ACC1_TRIP,Bool,”N/A”,
BUSFREQ,Float,”N/A”,
CMHUM2,Float,”N/A”,”Specific Humidity”
CMHUM3,Float,”N/A”,”Specific Humidity”
COMPOSTRIP1,Bool,”N/A”,
CONT1_TRENAB,Bool,”N/A”,
CPD1,Float,”N/A”,
CPD1_ARLIST,Float,”N/A”,”Array list for CPD rolling average
calculation.”
CPD_AVERAGE,Float,”N/A”,”Average CPD pressure for display.”
CTIM_1,Float,”N/A”,”Probe 1 compressor inlet temperature in degrees C.”
CTIM_1_F,Float,”N/A”,”Probe 1 inlet air temperature converted to F”
CTIM_2,Float,”N/A”,”Compressor inlet temperature”
CTIM_2_F,Float,”N/A”,”Probe 2 inlet air temperature converted to F.”
CTIM_3,Float,”N/A”,”Compressor inlet temperature”

CTIM_3_F,Float,”N/A”,”Probe 3 inlet air temperature converted to F.”
CTIM_DIF_ALM,Bool,”N/A”,”Inlet temperature max differential alarm.”
DEC1_TRIP,Bool,”N/A”,
DESIGNATE,Bool,”N/A”,
DRIVEFREQ,Float,”N/A”,
DTGGC10,Float,”N/A”,”Generator Temp - Cold Gas Coupling End”
DTGGC11,Float,”N/A”,”Generator Temp - Cold Gas Collector End”
DTGGH19,Float,”N/A”,”Generator Temp - Hot Air Collector End”
970 of 1016
(*'([FKDQJH5HSRUW
%>#

! # 8
:!$
!
$ #

#
8!
: # !8!:

#
)LJXUH(*'([FKDQJH5HSRUW
%0
!
> $

Ø7RORDGWKH(*'([FKDQJH5HSRUW&69ILOHLQWRDVSUHDGVKHHW
, ; 0 (*'([FKDQJH5HSRUW
! )LOH
; )LOH !
6DYH$V
FVY
#
2 ;

971 of 1016
%
#

0 +
...Site: HSTLAB1
...Unit: GT8
...List: EGD Exchange Information
...Time: 16-MAR-2000 14:49:38
Page,Length,Period,Source,Destination
14,4,320,GT8_EGD,BROADCAST
972 of 1016
:352&(66:HE3URFHVV/LVW
%@$C 8@.F:

! (
!
$!

% !!
$!
!
!
$ !

5HIHUWRWKHVHFWLRQRQ . !
! $ !
:$87+(1IRULQIRUPDWLRQRQ " @$ ! $ ! !
D!
DXWKHQWLFDWLRQ
! !

! ! ! @$$ >

! ! $
$

;#
3 ! $ $

/ !
! $!

!
%( % %(
!
'HEXJJLQJ,QIRUPDWLRQ +
<LI><A HREF=”scripts/GEDS/wprocess.exe”>Process List</A></LI>
%

@$C
+
)LJXUH:HE3URFHVV/LVW'LVSOD\
973 of 1016
:680B':HE6XPPDU\RI ')LOHV
0DUN,90DUN90DUN9/0 @ ?

$
%( 23
F ?A( %

XWLOLW\
$ @$3$ ?

. @$3
$ ?

. $> !
$

! !
%!
! !$ @$3$ ?

. $> $!

!
%
!!
'
3 !

$ '
$
P
(

?A(!

%GD\$ !%

(
!
!
%

<<<<00''B ' +
• DDDD !
• AA
• >>
• ***
+
3 CA_

3 0%_
3 F_&!
• >2
# 8
2:

+H?A(>%
%
?

F
! $ODUPB+LVWRU\
<HV
#
@AI>2 !(
%
$
!

!
% $! +(/3

%
$

+
• ?C3

• .%3( #
• A3( ! !
!
F
• >(.%F.D_Z [3%
'

(
! <= ! !

• Z
[
$
P
;#

A ,-,
! !

!

DODUPVW[W

!
$!+
WSUM_D03 DIRECTORY=. RPT 20010315_ALM.D03 >alarms.txt
974 of 1016
;#
! !$!

A ,-,

! !
!

VXPPDU\W[W

!

$!+
WSUM_D03 DIRECTORY=. SUM 20010315_ALM.D03 >summary.txt
%!

?

!
$! %

*
%

"
P

$
(

$
!
$

975 of 1016
&KDSWHU1HWZRUNLQJ
,QWURGXFWLRQ
% ! ! " ?A( A "
(0A "0A "0(
$!

%
;

" > ?
> ?

"

6HFWLRQ3DJH
A "(0 K
; -3
; -3
A "0 3
" -32
%. -32

" -31
;$3F $
-3,
. -3,,
-3,2
A "0(> ? K -3,1
> ? -3,-

> ? -3,-
A "0(B ".!
-3,4
B "&! -3,4

C" -3,7
*(+$9ROXPH,,$SSOLFDWLRQ*XLGH &KDSWHU1HWZRUNLQJ••
976 of 1016
0DUN9,'DWD+LJKZD\±(WKHUQHW
! $ ?A( A "0(
$
> ? 8>?:% ! "!
> ? /;!-3-$
%
$ $3 $

! !

$
!
! $ ?A( ?A(0 $

> ? 8>?:% ! "!

> /;!-3-%
$ $3 $

! !
$

!
7R2SWLRQDO&XVWRPHU1HWZRUN (QWHUSULVH/D\HU
5RXWHU
+0, +0, +0, )LHOG
9LHZHU 9LHZHU 9LHZHU 6XSSRUW
6XSHUYLVRU\/D\HU
3/$17 '$7$ %
3 /$17 '$7$ $ 5RXWHU
+0,6HUYHUV 260
+LVWRULDQ
&RQWURO/D\HU
8 1,7 '$7$+,*+:$< %
8 1,7 ' $7$+,*+:$< $
6LPSOH[ 0LVF
7058QLW 8QLW *HQHUDWRU 6WDWLF
([FLWHU
&RQWUROV &RQWUROV 3URWHFWLRQ &RQWUROV 6WDUWHU
0DUN9, 0DUN9, *HQ *()3/& (;&,7(5 /&,
0DUN9, 3URWHFW (;&,7(5
*()3/&
)XWXUH
0DUN9,
*HQLXV *HQLXV
,21HW ,21HW
%XV %XV
,2%RDUGV ,2%RDUGV ,2%RDUGV ,2%RDUGV
)LJXUH0DUN9,&RQWURODQG+0,6HUYHUVDQG9LHZHUV
••&KDSWHU1HWZRUNLQJ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,,
977 of 1016
8QLW'DWD+LJKZD\
%>? $ " $ 3 3
! $

?A(
.! $

$

%>?!
$
> 8>: 3$

!

$ >'( % $
-3-
" !
7DEOH8'+1HWZRUN)HDWXUHV
8'+)HDWXUH 'HVFULSWLRQ
7\SHRI1HWZRUN (WKHUQHW&60$&'XVLQJ(WKHUQHW*OREDO'DWD(*'SURWRFROLQVLQJOHRUUHGXQGDQWQHWZRUN
FRQILJXUDWLRQ
6SHHG 0ESVGDWDUDWHFDSDEOH
0HGLDDQG'LVWDQFH (WKHUQHW%DVH7;IRUVZLWFKWRGHYLFHFRQQHFWLRQV7KHFDEOHLVWR$:*XQVKLHOGHG
WZLVWHGSDLUFDWHJRU\(,$7,$$%'LVWDQFHLVXSWRPHWHUV
(WKHUQHW%DVH);ZLWKILEHURSWLFFDEOHRSWLRQDOIRUQHWZRUNEDFNERQHGLVWDQFHLVWZRNP
1XPEHURI1RGHV :LWKQRGHVV\VWHPSURYLGHVD+]GDWDUDWH)RURWKHUFRQILJXUDWLRQVFRQWDFWWKHIDFWRU\
3URWRFRO (*'SURWRFROEDVHGRQWKH8'3,3VWDQGDUG5)&
65736HULDO5HTXHVW7UDQVIHU3URWRFROSURWRFRO
0HVVDJH,QWHJULW\ ELW&5&DSSHQGHGWRHDFK(WKHUQHWSDFNHWSOXVLQWHJULW\FKHFNVEXLOWLQWR8'3DQG(*'
7LPH6\QFK 1HWZRUN7LPH3URWRFRO173
0HWKRGV
3ODQW'DWD+LJKZD\
%>?!
>? %>?
!
!$

&! >?% $
-34 " !
7DEOH3'+1HWZRUN)HDWXUHV
3'+)HDWXUH 'HVFULSWLRQ
7\SHRI1HWZRUN (WKHUQHW&60$&'LQDVLQJOHRUUHGXQGDQWVWDUFRQILJXUDWLRQ
6SHHG 0ESVGDWDUDWH
0HGLDDQG'LVWDQFH (WKHUQHW%DVH7;IRUVZLWFKWRGHYLFHFRQQHFWLRQV7KHFDEOHLVXQVKLHOGHGWZLVWHGSDLU
WKHGLVWDQFHLVXSWRP
(WKHUQHW%DVH);ZLWKILEHURSWLFFDEOHIRUQHWZRUNEDFNERQHWKHGLVWDQFHLVXSWRNP
1XPEHURI1RGHV 8SWRQRGHVVXSSRUWHG
3URWRFROV (WKHUQHWFRPSDWLEOHURXWDEOHSURWRFROW\SLFDOO\7&3,3EDVHG
0HVVDJH,QWHJULW\ ELW&\FOLF5HGXQGDQF\&RGH&5&DSSHQGHGWRHDFK(WKHUQHWSDFNHWSOXVDGGLWLRQDO
FKHFNVLQSURWRFROXVHG
([WHUQDO,QWHUIDFHV 9DULRXVWKLUGSDUW\LQWHUIDFHVDUHDYDLODEOH*60DQG0RGEXVDUHWKHPRVWFRPPRQ
978 of 1016
0DUN9,1HWZRUN5XOHV
.!
A "0(>? >? " % $
-39

A "0( !
7DEOH-391HWZRUN5XOHV
1HWZRUN5XOH 'HVFULSWLRQ
1XPEHURI+0,6HUYHUV 8SWRHLJKW+0,6HUYHUVSHU0DUN9,XQLWFRQWUROOHURQWKH8'+
/RFDO+0,VHUYHU 7KHORFDO+0,ZRXOGQRUPDOO\EHDVHUYHUWRLWVORFDOWXUELQHFRQWURO$VDPXOWLXQLW
RSWLRQWKH+0,VHUYHUPD\EHDVHUYHUWRVHYHQRWKHUXQLWVDOVR'DWDFROOHFWLRQLV
DFFRPSOLVKHGRYHUWKH8'+)RUPXOWLXQLWFRQILJXUDWLRQVFUHDWHDVLQJOHSURMHFWIRUDOO
HLJKWXQLWVDQGSURSHUO\FRS\WKHSURMHFWWRWKHRWKHU+0,VWREHFRQILJXUHGDVPXOWL
XQLWRQWKHVDPHQHWZRUN
&RQWURO5RRP+0, 7KHFRQWUROURRP+0,PD\EHDVHUYHUIRUXSWRHLJKW0DUN9,FRQWUROOHUV7KLVFDQEH
VHUYHU DFFRPSOLVKHGE\FUHDWLQJDVLQJOHSURMHFWIRUDOOHLJKWXQLWV
5HPRWH+0,9LHZHU 5HPRWH&,03/,&,7<YLHZHULVDYDLODEOHIRUUHPRWHPRQLWRULQJDQGFRQWURO&RQVXOWWKH
7XUELQH&RQWURO6\VWHPIDFWRU\IRULWVDYDLODELOLW\
+LVWRULDQ $VLQJOH+LVWRULDQFDQKDQGOHXSWRHLJKW0DUN9,FRQWUROOHUVRQWKH8'+
8QLW'DWD+LJKZD\ 2QO\*(GHYLFHV0DUN9,+0,6HUYHUV(QJLQHHULQJZRUNVWDWLRQV+LVWRULDQVDQG*(
3/&VDUHDOORZHGRQWKH8'+
3ODQW'DWD+LJKZD\ +0,YLHZHUV+0,VHUYHUV(QJLQHHULQJZRUNVWDWLRQV+LVWRULDQVSULQWHUVWKLUGSDUW\
3/&VDQGLQWHUIDFHVWRFXVWRPHUVFRUSRUDWH/$1VDUHDOORZHG
,QWHUIDFHOLQNV 7KH+0,VHUYHUFDQSURYLGH0RGEXV6HULDO0RGEXV7&3,3*60RU23&OLQNVWR
H[WHUQDOGHYLFHVVXFKDVD'&6V\VWHP
0DUN9,DOVRKDVFDSDELOLW\RI0RGEXVIURPWKHFRQWUROOHU
5HIHUHQFHV 0DUN9,6\VWHP*XLGH*(+
(WKHUQHW1HWZRUN(TXLSPHQW
; $ A "0(

!
8%: .S31- !
;
!

$3 $
!% $
&!

8A(: &! 8.;(:C
7KHILEHURSWLFFDEOHXVHV6& 3 3 $
$

W\SHFRQQHFWRUV !
$

;$3 $
$!
$
!
$!
$!
(
$!
$ !
%>? " $

% $
-3,
979 of 1016
.! " A "0( ;!-34%
$$ ! !
+
• FA F A !
!$
$

• @ @" ! !
• C
"

!

"
• . % ! A "0(

!

!

7DEOH3'+1HWZRUN+DUGZDUH
3'++DUGZDUH 'HVFULSWLRQ
7ZLVWHGSDLU 8QVKLHOGHG7ZLVWHG3DLU873FDEOHWR$:*SDLU&DWHJRU\(,$7,$$%RU
FDEOH EHWWHULQFOXGLQJ5-FRQQHFWRUV
0D[LPXPGLVWDQFHIRU873FDEOHLVPIW
$RQHWRRQH873FDEOHLVXVHGWRFRQQHFWDGHYLFH+0,RUSULQWHUWRDVZLWFK
$RQHWRRQH873FDEOHLVXVHGWRFRQQHFWDVZLWFKWRDURXWHU
$FURVVRYHU873FDEOHLVXVHGWRFRQQHFWDVZLWFKWRDVZLWFK
)LEHURSWLFFDEOH 2SWLFDOILEHUFDEOH(WKHUQHW%DVH);W\SHPLFURQGXDOZLQGRZJUDGHGLQGH[
SURILOHPXOWLPRGHJODVVRQJODVVFRQVWUXFWLRQWKHUPRSODVWLFMDFNHWLQFOXGLQJ6&W\SH
FRQQHFWRUV
0D[LPXPGLVWDQFHIRUILEHURSWLFFDEOHLVPIW
:KHQFRQQHFWLQJILEHURSWLFFDEOHXVLQJ6&W\SHFRQQHFWRUVWKHFRQQHFWLRQVKDYHWREH
FURVVHGWKDWLVWKHWUDQVPLWDWRQHHQGLVFRQQHFWHGWRWKHUHFHLYHDWWKHRWKHUHQGDQGYLFH
YHUVD
6ZLWFKHV )DVW(WKHUQHW6ZLWFKHV&LVFR&DWDO\VWRUHTXLYDOHQW
5RXWHUV 5RXWHUV&LVFRRUHTXLYDOHQW
5HGXQGDQW )DXOW7ROHUDQFHLVDFFRPSOLVKHGE\XVLQJUHGXQGDQWVZLWFKHVFRQILJXUHGLQDVLQJOHORJLFDO
6ZLWFKHV QHWZRUN
980 of 1016
6HULDO/LQN

A$!!
" $! ! $
!$
!
$!
8>:
A "(0A "0 A "0(
! A$!! %

"
:LWK0DUN9,(WKHUQHW
>

0RGEXVLVWKHSUHIHUUHG

C
!
0RGEXVFRPPXQLFDWLRQ ! &!

! !
!$

!
%?A(!
A$! (A$!

> &! ! ?A(
,IWKH'&6QHHGVDODUPVWKHQ
!$
%?A(
&! A$!
*60PHVVDJLQJLVUHTXLUHG

$
(A$! ?A(&!

! ! .%

$

! $ C >8 (3,-,90RGEXVIRU

63(('7521,&7XUELQH&RQWURO
%.32
?A(!
"% $

- 8,-:$! $# $!

,5$ !! ! % $
-35$ !
7DEOH6HULDO0RGEXV)HDWXUHV
)HDWXUH 'HVFULSWLRQ
&RPPXQLFDWLRQ 0DVWHUVODYHDUUDQJHPHQWZLWKWKHVODYHFRQWUROOHUIROORZLQJWKHPDVWHUIXOOGXSOH[DV\QFKURQRXV
7\SH FRPPXQLFDWLRQ
0HGLD 56&FDEOHZLWKRXWOLQHGULYHUVWKHGLVWDQFHLVIWPZLWKOLQHGULYHUVWKHGLVWDQFHLV
RYHUDPLOH
6SHHG 7\SLFDORQHVHFRQGGDWDXSGDWHEDXGLVVWDQGDUG
0HVVDJH7\SH 0DVWHU6ODYHSROOHGFRPPXQLFDWLRQV\VWHP
5HPRWH7HUPLQDO8QLW5780RGH(DFKELWE\WHLQWKHPHVVDJHLVVHQWZLWKQRWUDQVODWLRQ
ZKLFKSDFNVWKHGDWDPRUHHIILFLHQWO\WKDQWKH$6&,,PRGHSURYLGLQJDERXWWZLFHWKHWKURXJKSXWDW
WKHVDPHEDXGUDWH
$6&,,0RGH(DFKELWE\WHLQWKHPHVVDJHLVVHQWDVWZR$6&,,FKDUDFWHUV±WKHKH[DGHFLPDO
UHSUHVHQWDWLRQRIWKHE\WH1RWDYDLODEOHIURPWKH+0,6HUYHU
0HVVDJH,QWHJULW\ $QRSWLRQDOSDULW\FKHFNLVGRQHRQHDFKE\WHDQGD&5&FKHFNVXPLVDSSHQGHGWRWKHPHVVDJH
LQWKH578PRGH
981 of 1016
&KDSWHU&RQWURO&RQILJXUDWLRQ
,QWURGXFWLRQ
% $ ! A "(0A "0 A "0CA

?A(%A "0(
!!
%
$#
6HFWLRQ3DJH
( ! 43,
?A( 3> 43

3! ;
434
>
3! ;
439

439
A "0(
437

437
.>I(> 437
>/(C>K>
/!
A "0 43,,
>/(C>,K>
/!
A "0CA 43,
>/(C>,K> ! /!
43,2
>(/(C>,K(FI;> ;
/!
43,1
>/(C>,K.FA!$3> /!
43,1
>>CF%3> > C 43,-
>>%(C3> >
43,9
AM-AMKA "0A " 43,7
;A0(>3;!
A 0
(> 43,5
C>/.AKC P > $ A 43,
C>/?MKC P > $ " 43
>>0CK> > 0
432
C.AICK
C 432
FB%%K 431
FB%?MK " 43-
LFAC3&! 439
L>FA%K&!>! 432,
L>(%8&!: 4321
.(B%3
&! 431
%/CI8% $

: 4311
.FA 431-
;
>
4317
>;K3>;
4317
*(+$9ROXPH,,$SSOLFDWLRQ*XLGH &KDSWHU&RQWURO&RQILJXUDWLRQ••
982 of 1016
0DUN9,&RQWUROOHU
7KH+0,LVQRWXVHGWR %A "0(
!!

$#%
$#
FRQILJXUHWKH0DUN9, @ 3$ " ! !

!
A "0(
. ?3
412&RQWURO6\VWHP7RROER[IRU&RQILJXULQJD0DUN9,7XUELQH&RQWUROOHU
%
$#
! +

• 3$ !

•
$
" !

$ !
• C

• F

• F
?

• ('F$
!
•

• A!
3!

• .
• % !
%
$# ! ?A( "
8WLOLWLHV
A
!
A "(0A "0 A "0CA!

?A(A "0(!

$#
&$5'B,'
0DUN9DQG9/0VXSSRUWWKLV .>I(> C!
A "0A "0CA
XWLOLW\0DUN9,
.FA !( !!

XVHVWKHWRROER[
V.FA&!! !!

!$

1RWH% ! (
$ .FA
$
%DFNJURXQG
%A "0 A "0CA
!

$
$ .FA $ .
$ .FA &!%.FA

$
$ % !
$
!
! $ "

.FA$! ! .>I(>!

%
$
A "0
A "0CA
%A "0

$
.FA
.FA%

$ 8! %>: !$8! ,:
••&KDSWHU&RQWURO&RQILJXUDWLRQ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,,
983 of 1016
6(4&203/6HTXHQFLQJ
0DUN9DQG0DUN9/0 %
&!

VXSSRUWWKLVXWLOLW\
&! 8: !

0DUN9,XVHVWKHWRROER[ %&!

&!! 65&

0675B6(4&)*
!
%&!

@
2QO\TXDOLILHGSHUVRQQHONQRZOHGJHDEOHDERXWWXUELQHFRQWURO
DQGSURWHFWLRQVKRXOGXVHWKH6HTXHQFH&RPSLOHU,PSURSHU
XVHPD\DGYHUVHO\DIIHFWWKHFRQWURODQGSURWHFWLYHIHDWXUHVRI
WKHFRQWUROV\VWHP
)LOH6WUXFWXUH
5HIHUWRWKHQH[WVHFWLRQIRU %! ! &!
$3
8
: $
LQIRUPDWLRQRQWKH

%
$
&!
6(4$3
0675B6(4&)*ILOH A "0CA A "0 6(4B%$3 6(4B4$3%

#

0675B6(4/2* ! !

!
&!
!
!

$

$
$!
$
"35,0,7,9('() %,*%/2&.'()

((

$
"
$
!
!

81,7'$7$'$7
&!
!
"
! !

0675B6(4&)* 6(4$3
0DUN9/0
81,7'$7$'$7
6(4&203/(;(
3520?35,0,7,9('() 6(4B%$3
&RQWURO
6HTXHQFH 0DUN9
3520?%,*%/2&.'() &RPSLOHU
^6HJPHQW
^6HJPHQW 6(4B4$3
^6HJPHQWQDPH`65& 0DUN9
)LJXUH6HTXHQFH&RPSLOHU%ORFN'LDJUDP
([HFXWLQJWKH6HTXHQFH&RPSLOHU

&!
LFAC

!

%&!

0675B6(4/2* !
%! $
$! &!
" &!!
65&:% $3! !

!!
&!
#!
984 of 1016
;
; MSTR_SEQ.CFG for MKV LM
;
---------------------------------------------------------------------
-- Configuration file for sequencing compiler
---------------------------------------------------------------------
;#LIST
Major Minor
rev rev
#BBL_REVISION 1 1
---------------------------------------------------------------------
-- R, S, T Segments
---------------------------------------------------------------------
; Frame Rate Frame Time(period) Hz
; Scan Rate n = 1 = (base)10 = msec iteration interval 100
; Scan Rate n = 2 = 20 = msec iteration interval 50
; Scan Rate n = 4 = 40 = msec iteration interval 25
; Scan Rate n = 8 = 80 = msec iteration interval 12.5
;
; For Mark VLM the reference rate is 100 Hz, 10 msec
#<Q>_SEGMENTS
; Scan rate, n Offset within scan rate
#SEGMENT SEQ_10GE 1 0 ;GENIUS COMM ;CHECK
#SEGMENT SQ_BLK 1 0 ;
#SEGMENT SQ40_2 4 2 ;PD
#SEGMENT SQ40_1 4 1 ;PD
#SEGMENT SQ640 64 11 ;13
#SEGMENT SQ160_5T 16 5 ; DRAIN / PURGE ;VALVE
DEMAND AND FEEDBACK
#SEGMENT SQ160_3T 16 3 ; DRAIN / PURGE
#END
6(4'2&07±6HTXHQFLQJ'RFXPHQWRU
0DUN9DQG0DUN9/0 %
&!>!

VXSSRUWWKLVXWLOLW\ !
! %! #

0DUN9,XVHVWKHWRROER[
!$

"! $!
(
!
!
%
&!>! !
&!!
65&:
0675B6(4&)*
!
%&!
>!
@
)LOH6WUXFWXUH
%
!$ >! % &63351

%&63B;5()351
3! /

!
!
985 of 1016
% .FA !
!
! V.B% !
# %A. $
%
.FA
!
7KH)250$7SDUWLWLRQLVQRW
" ;F.A%>
;F.A%
LQFOXGHGLQWKH86(5SVHXGR
3 .FA

/ !

VHFWLRQ ! ;F.A% # $ "
;F.A% ! !
)ODVK'RZQORDGHU
0DUN9,VXSSRUWVWKLVXWLOLW\ %A "0(
!

$#%
$# $
! ?A( " (

$ ! ! !

&RPSDFW)ODVK! ;
>
;

?3412&RQWURO6\VWHP7RROER[IRU&RQILJXULQJD0DUN9,
&RQWUROOHU
8')±8VHU'HILQHG)LOH
0DUN9/0VXSSRUWVWKLV >;83>;
: A "0CA! !

XWLOLW\0DUN9XVHVWKH $ ! ?A( 3

((3520SURJUDPLQVWHDG A "0CA

0 !!
$3
!
A "0CA
%
! &!
% $

('F! %
! !
! ! $
?A(
"

(
>;

A "0CA
" ! V

$!
2SHUDWLRQ
>;
!

! >F
@ ! ! ! %! $ A "0
CA! &! " !

A "0CA! D!

"
!
$ Z.[
>; >;[
••&KDSWHU&RQWURO&RQILJXUDWLRQ +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROXPH,,
986 of 1016
*ORVVDU\
$FWLYH;
E
$A !

!

@ E! " &! !!$!
$ $
(

! $!

E

!
A ( #
Q " $
" $

"!
$FWLYH;FRQWURO

8$) :! E
$
E

$ !

#! $ $$

E

!
!
660!
/ S E
!
@

DODUP
&! "
$

$ODUP9LHZHU

(AC((%D8 FE
:

$09

0
DSSOLFDWLRQ

3 !

!

! !
!

$5&1(7
.!! B " CB!

$> .B%
8 # :

"8 " $ :
-A?P!
"
987 of 1016
%DODQFHRI3ODQW%23

&! !$ $

ERDUG
$ ! $ !
!
%RROHDQ
>
# %!;

EUHDNHUFLUFXLWEUHDNHU
$
" $ "! !

!
"
$ "! ! $
! !
&!
% !$
*! 8:
&LP(GLW
$) 3
(AC((%D?A( !
! 0 (

&,03/,&,7<+0,
3$ ; !! ! $

"
&! &!
FLPSURM
%&!!$ (AC((%D?A() 8)?&LPSURM:%
) ! @"$8JHI:
!$
&LP9LHZ

! (AC((%D?A(!

&!
# $)
( %
!
!

!

! ! @

FOLHQWVHUYHU
! ! "&!
! ;#
"
&! !
FRPPDQGOLQH
%
!
! $ ! $
% ! # 3$ ! A3>F

! 8(:! @
FRQILJXUH

$ "
$

)!$

988 of 1016
FRQWUROV\VWHP
&! !
)! ! !

&!A@
$
&!
!
&!A@ !&!

!$!
#
&RQWURO6\VWHP6ROXWLRQV
! >
;#

!
%
$#>/#
&RQWURO6\VWHP7RROER[
WRROER[
&5&

.! " ! !

"
FURVVSORW
>
$

E3D

P
&6'%

> $ ! !$

!

!

&6)

; " ! "
!
%@(BE $
! 2A?P
'!
% !$
*$ "!! 8:8

&!:
GDWDGLFWLRQDU\

$
$ %

!$ $!

$
$

!
3 ! P ; ?A(

$! ! 3

$
#
8$
:

8 '! !:% ! >
>
81,7'$7$'$7 $ ?A( ! 3

'&6
> $!
!

!
$

&!
GHDGEDQG
.
!
$
!
! ! %? ! $

!
989 of 1016
'HPDQG'LVSOD\
?A(!
!

!$
!
( ! !

!
GHYLFH
! $

'HYFRP

! $$
(AC((%D?A( A $
G\QDPLF
$! P
(*'

$
> "
!$
>
!># 8 :
(WKHUQHW
CB ,, $ ! !
"!
'
( !
'

( !%'( ('F
(72

$E#>
&! 8>: (

HYHQW
>
$ !

(;
#
( !

!

! !

IDXOWFRGH

?A(

!
ILUPZDUH
#! $

!

! .FA;

ILOWHU

IRUFLQJ

!

!

! $
" ('F

IUDPHUDWH
/ !

(

! 3! 3
! !

990 of 1016
*60
(!
A
3

>%

!

B

!
!
&! $ >&!
*OREDO7LPH6RXUFH*76
@
!
%8
%:! "

JUDSKLFDOXVHULQWHUIDFH*8,
$ ! ! $
(
! ! " ;

$
E#
# 3$ $

A A @ B(E
E@
KHDGHU
%# !
!

$

! !!

!
+LVWRULDQ

'3$

!#
( $3
!

!$

!3

+0,
?! 3A ( %?A( @ B%3$
!$
!#

&! %?A(!
(AC((%D ! ?
%

?
+56*
? . %!# ! !$

LFRQ

! 8

:

! @
" !
$

,&6
(
%($ !

$!

LQLWLDOL]H

!8 ! !: $
!

991 of 1016
,21HW
%A "0(('F ! "
/$1
C
"8! :
CB

$!

ORJLFDO
!'
! /

0DUN,9
>%.FB( !$
!,572%

!
! 8%A.:
!
3

0DUN9

3
>%.FB( !$
!,55,

$

# %A.
&! >F3$

! ! B%3$ (AC((%D?A(
0DUN9/0
>%.FB( !$
!,55-

! >C 8>C:

$
&! ! B%3$ (AC((%D?A(
0DUN9,
0A3$ >%.FB( !$

$

#
%A.
&! ! B%3$ (AC((%D?A(

%
$#
PHQX
8 :
!
$
0RGEXV

!

$!
A!
$ C !
QHWZRUN
!
" !

REMHFW
8 :
$!

!

%
! !

$
($) 3 #
$)

3 $ ! !

2&;
FC!
!
$ $
@ E8A *#

:$ " $
FE
992 of 1016
2/(
8!
:F$)
" $!
!
$A ( $
!
$)

"$

$$)

"

! FC$!
@
23&
FC
%F 3
$ !A *
FC'FA
%
F "
$
$
$ ! '

' $!'

SDQHO
% &!
$
!
SF
$$ SHUVRQDOFRPSXWHU
3'+
3ODQW'DWD+LJKZD\
SHUPLVVLYHV

3ODQW'DWD+LJKZD\3'+
! "
" ? ?A(?A(0
"
3/&
$

% 8

:

! 8
:! !

SORW
% $

!

SRLQW
/ ! $

SURGXFWFRGHUXQWLPH

*;

8: #! $

993 of 1016
UHDFWLYHFDSDELOLW\
% ) $ $

!! 0
!%
! $

!
!
UHERRW
.

!
UHOD\ODGGHUGLDJUDP5/'

!

!

UHVRXUFHV

" !.! 8 "
":
" ! .!
!

(AC((%D $!

!
!
UXQWLPH
SURGXFWFRGH
6HTXHQFHRI(YHQWV62(
3
! "!
!

A !$
!
! ,

VHUYHU

"
$

3$ " 0
VHWSRLQW
0
!
$
! !

!
VLJQDO
/ ! $

6LPSOH[
F &!

('F
!

62(
6HTXHQFHRI(YHQWV
6573
.&! %
!

! $ !$
?A(
994 of 1016
6WDJHOLQN
.B%3$ !
"!$

V\QFKURVFRSH
( ! P
WDJ
( !
7&($
>%F/ 8%:

*
Z,[! 3 ! (
% %$ ! Z,[
ZE[ZD[ ZJ[%$

!

!
P % ! !
%8
,:$
(FB% Z.,[*>%$ %%

%!$%/ 8>%%: %
!
!

7&,
%!$
( %3!
" ?A(
!$

7&3,3
!

3 "
(
B(E $! !

%

( ! ! !
3

WLPHWDJ
(

705
%
A!
.! % ! !

('F !
$

$
! !

WRROER[&RQWURO6\VWHP7RROER[
@ 3$ " ! ! A "0(

#
WUHQG
%3$

!
$

? ?A(
%
$#
WULJJHU
%
,,
&!
995 of 1016
8QLW'DWD+LJKZD\8'+
A "0(
C(EC

&! ?A( !
"
87&

%
3
XWLOLW\

"!!

!

P

# !
ZHEEURZVHU
! A ( #
B B

$ "
:LQGRZV17
23$ A 2743$
$
:RUNEHQFK
(AC((%D?A( ! ! P
(AC((%D) !

996 of 1016

"32-34-39
#

A 43,

,35-32

-3743
?
C 3413,413,943413,4
,QGH[ 13,9
23,43,
A0-3,7-34
,3-232231-3,9

,3,32,31
%
/

,39-37-3-
$ 8 $ :
/
43-
/F8/

:,39-37-3-
$ "8! $ ":-3-32
$
E$) ,35-3,-3-3 &
A !
P>
-3-36 ,3-,37-3,9
,36 ,3-232231-3,9
%
-3-34-39 (AC((%D

323413,4 E$) ,35-3,-3-34

0 ,34323413,4-37-34 ?A(,32,3732-3,-3-34-37-3,-3,1-3
13,4 ,943,4343243,43,
0 ,3-,343 )-3,443,43
#
32-3,-34 0 ,3-,343
C"3213,9-34-3913,9 ! $ "-3-32
C"! -3,-34-39
3,3,

32-3,-34-39
23423,,23,-13,213,113,--39

"32-34-39 43943,,13,213,113,-

-37 ! ,32,34,3743143,
!-3,1 ,3923,243,43,,

0 ,34323413,4-37-34 A$!,3943,,3
13,4 ! ,32,353113913,213,113,4-3,
A0-3,7-34 -32-31-3--34-37-3,-3,14343143-43
0 ,3-,343 443913913,213,113,4
#
32-3,-34

-3,1
C"3213,9-34-39,13,9 > >
13,2
C"! -3,-34-39 !-3,

32-3,-34-39 !-37

"32-34-39

> $ 8>/:13,943143-13,9

,32,31,34323-23513,-13,4-3,-37
,32,34,3513,
-3443143-43443,3113,-13,4
; 8;:

3234

! ,37

C
3413,-
%
$#,3,39,373-2323523

0 ,34323413,4-37-34 ,21343,
13,4
%
$#8
$#:,323,243,

-3,4-3
A0-3,7-34 %.,3,3723,232
43443,

#
32-3,-34 A "(0,3,,321313,213,--3743143,43
C"3213,9-34-3913,9 ,,1313,213,-
C"! -3,-34-39

32-3,-34-39
+0,$SSOLFDWLRQ*XLGH ,QGH[•1
997 of 1016
A "0,3,,3,32,39,373-342323523 !
434439
,23,223,123,-13-3-3443143443, # -37434439
13 #
32-3,-34
A "0CA,3,,3723,23,123,-431434 C"3213,9-34-39/313,9
C"! -3,-34-39
A "0(,3,,3,32,39,373-2323523,2
32-3,-34-39
1313,4-343143443,
"32-34-39/3
1313,4 #

A 43,

E,35-3,-3-34 )
>/8

> $ :13,943143-13
,9 !
434439

! !2343

,35-37-32

,35-32
'
.!> -3,2
> > ,3213213113-13413543143-43 .
-3,,
513213113-134135 -3,
23523,,23,23,-
$ *

> $ 8>/:13,943143-13,9
>/# ,3743, A 8A:,39
>/
43,
,3,32,31,3-,34-3,-37
>8> $!
:,39
> >
342323223-23713132131 ,3-,37-3,9
13-13413913713513,13,,13,213,13, 0 ,3-,343
321313213113-13413913713513,13 A8*(6WDQGDUG0HVVDJHV:,39
,,13,213,1
!13,2 +
;
;! 239
13 ?
13,,
13- ? ,3,

43443, ? ,3,39,3723,2

?A(8+XPDQ0DFKLQH,QWHUIDFH:,3,,3,32,3
0 ,3-,343 1,3-,34,39,37,353,33-3423,23
> >
342323223-23713132131 ,113,13,-13,4-3,-3-3743,4343143
13-13413913713513,13,,13,213,13, -43,43,,43,
321313213113-13413913713513,13 /3213,13,-13,4
,,13,213,1
A !
P-3-34
. $
-37 ?
C 3413,413,9436
&!239
> $!
8>:,39 ?! 3A ( 8?A(:,3,,3,32,31,3
! ,37,3,13 -,34,39,37,353,33-3423,23,1
>F 8
:23423,,23,-13,2 13,13,-13,4-3,-3-3743,4343143-43
13,113,--3943943,,13,213,113,- ,43,,43,
> .!>
,312323223123-234239 13,13,-13,4
237 !,3
234
!,39
23123-23513-
3-

132
!,37-3,5-3-3,431
( ,39
>8
$
> :23,2 !3
,3923,243,43,,

$
> 8>:23,2
E434439
2••Index +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROumeII
998 of 1016
, ) ,3531-37-3,-3,1-3,543,43432
43143543,43,
(,39 !
)-3,443,43
. @"$31-37-3,-3,1-3,443,43432
31432
"
!,35
5
0 . $
>
-3
&! ,3,
A !
P>
-3-34
.!> -3,2
A "(0,3,,321313,213,--3743143,43
!!-3,
,,3,3/3,1313,213,-
.
-3,,
A "0,3,,3,32,39,373-342323523,
!> .!>
3-23232234239
23,223,123,-1313,4-3-3443143443
237
,1313,4
A "0CA,3,,3723,23,123,-431434
6
A "0(,3,,3,32,39,373-2323523,213 >/# ,3743,
13,4-343143443, >/
43,
/321313,4 ! ,3-37-3,
A$!,3943,, &! 8F:434
&!>
239
1 13943,139

A 43143-434439437435
",31

437
,3923,243,43,,
F86HTXHQFHRI(YHQWV:434
A$!,3943,,
,39
>%.FB(

2 A "(0,3,,321313,213,--3743143,43
,,1313,213,-
$)
A "0,3,,3,32,39,373-342323523
E,35-3,-3-34
,23,223,123,-1313,4-3-34431434
FE32-37
43,1313,4
FC,3-32-3,-343,
A "0CA,3,,3723,23,123,-431434
F,3743,
FE32-37
A "0(,3,,3,32,39,373-2323523,2
FC,3-32-3,-343,
1313,4-343143443,
FC
8F:,3743,
1313,4
F82/(IRU3URFHVV&RQWUROV:,3743,
!,3-,343
3
7

,34-3,4
%(87XUELQH&RQWURO,QWHUIDFH:,3,32323-
>?83ODQW'DWD+LJKZD\:,32
23,113,4-3,-3-3443143-43,,
,31-31
13,4

> ? 8>?:,32
%'(,3931
C83URJUDPPDEOH/RJLF&RQWUROOHU:43,
23123-23523,13-
,32,343423223723523,13213-134
13,113,-13,413,943143-434439435

$#8&RQWURO6\VWHP7RROER[:,323,243,
13213-13413,113,-13,413,9
,34

23,43,
%.,3,3723,2
%? 3-23523,23,,23,23,223,123
,-

132

$
C
8C:43,
+0,$SSOLFDWLRQ*XLGH ,QGH[• 3
999 of 1016
E$) ,34
%
-3-34-393,

-34
%? 3-23523,23,,23,23,223,123
,-
> ? .!
@ 23523,,23,23,-
>
/#23523,,
>
3-
C3-23,123,-
C23,1
A "0(23,2
23,,
235
%!$
( 8%(:,3,32323-23
,113,4-3,-3-3443143-43,,
13,4
8
>?88QLW'DWD+LJKZD\:,32
> ? 8>?:,32
-3,
!!-37
9

-34
:
$3-
,393-
@"$31-37-3,-3,1-3,443,43432
4••Index +0,IRU63(('7521,&7XUELQH&RQWURO*(+$9ROume ii
1000 of 1016

*(,QGXVWULDO6\VWHPV
*HQHUDO(OHFWULF&RPSDQ\
5RDQRNH%OYG
ZZZ*(LQGXVWULDOFRP 6DOHP9$86$
1001 of 1016
GEI-100278B
g
GE Industrial Systems
Data Historian
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. If further information is desired or if particular problems arise
that are not covered sufficiently for the purchaser’s purpose, the matter should be
referred to GE Industrial Systems.
This document contains proprietary information of General Electric Company, USA
and is furnished to its customer solely to assist that customer in the installation,
testing, operation, and/or maintenance of the equipment described. This document
shall not be reproduced in whole or in part, nor shall its contents be disclosed to any
third party without the written approval of GE Industrial Systems.
Indicates a procedure, practice, condition, or statement that,

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

observed, could result in damage to or destruction of
equipment.
Note Indicates an essential or important procedure or statement.
Section Page
Functional Description.................................................................................................2
Working with Files and Menu Commands ..................................................................3
Menu Commands..................................................................................................3
Data Historian Concepts ..............................................................................................4
Configuration ...............................................................................................................4
Creating the Data Historian Configuration ...........................................................5
Collections ............................................................................................................7
Signals ................................................................................................................13
Dead Bands.........................................................................................................14
Troubleshooting..................................................................................................15
________
ARCNET is a registered trademark of GE Fanuc Automation North America, Inc.
CIMPLICITY® is a registered trademark of GE Fanuc Automation North America, Inc.
Ethernet™ is a trademark of Xerox Corporation.
Innovation Series is a trademark of General Electric Company, USA.
Windows® and Windows NT® are registered trademarks of Microsoft Corporation.
1002 of 1016
For assistance, contact: This document provides instructions for configuring the Data Historian using the GE
Control System Toolbox. The Data Historian records control signals from Innova-
tion Series™ drives and controllers and local area networks (LANs) connected to a
Post Sales Service
personal computer. Data is saved in a Data Collection and Analysis (.dca) file format
1501 Roanoke Blvd.
The program runs in the background as a service on the computer that is running the
Windows NT® or Windows 2000 operating system.
Phone: 1 800 533 5885
+ 1 540 378 3280 The Data Historian records the following values:
(International)
Fax: + 1 540 387 8606 (All) • Signals on a drive LAN (DLAN+) to which an Innovation Series con-
(“+” indicates the interna- troller is connected
tional access code required
when calling from outside the • Ethernet Global Data (EGD) signals on any Ethernet™ connected to
United States/Canada the computer on which the program is running
• Control Signal Freeway (CSF) signals if the Data Historian computer

has an ARCNET® board for CSF
• DLAN+ signals if the Data Historian computer has an ARCNET board

for DLAN+
• Service Request Transfer Protocol (SRTP) signals if the Data Historian

computer has the Programmable Logic Controller (PLC) Interface
• Innovation Series Controller Capture Buffers through EGD or DLAN+
• Innovation Series Drives Capture Buffers through EGD
Once collected in the .dca format, data can be accessed by the Trend Recorder or by
other GE data analysis applications.
1003 of 1016
Working with Files and Menu Commands
The Data Historian is configured using one of two types of configuration files:
• Data Historian binary (.reb) file is the binary form of the configuration created
through the File \ Save command. The configuration can also be exported to a
project file.
• Project (.prj) file is a text file that holds configuration information.
The configuration files generate the following output files, which can be downloaded
to the Data Historian service:
• Data Historian build (.rcd) file contains all of the configuration information and is created by the Device \ Build
command.
• DATAHISTORIAN.CFG is simply a copy of the .rcd file that is placed in the Data Historian’s output directory
during a download. This file is read by the Data Historian service when it is started or when a message is received
that the configuration has been downloaded.
Menu Commands
Data Historian menus, such as File, Edit, and View, are managed just as other tool-
box and Windows menu commands.
Device Menu
The Device menu contains the following commands:
Auto Configure is only avail- Auto Configure creates the signal list for the live collection of the Trip Log. The
able on the Trip Log. signals are resolved from the open controller file. If the controller file is not open in
the toolbox, then the signals are resolved from the controller directly. If both meth-
ods fail, the signal list will not be updated.
Get From Database retrieves signal information from the database. Use this
command after all signals have been added.
Validate checks the configuration for errors. The results are posted in the Log
View. Before you can validate a configuration, you must:
• Specify addressing parameters in the Addressing Parameters dialog box
(host computer and host IP address).
• Specify collection information in the Insert Collection dialog box.
GEI-100278B Data Historian • 3
1004 of 1016
• Add all signals and then perform a Get From Database.
Build creates the Data Historian build (.rcd) output file. The .rcd file is a binary file
that contains all of the configuration information.
Download sends the configuration file to the specified Data Historian. This com-
mand attempts to open a connection to the Data Historian service and send a copy of
the .rcd file to it. The Data Historian service creates the file
DATAHISTORIAN.CFG on the computer where it resides.
Data Historian Concepts

The Data Historian is configured in the toolbox as follows:
1. Create a Data Historian configuration. Select a Data Historian host. (Since there
may be different Data Historian services running on different NT Host systems,
specify the service by naming the Host NT box and, optionally, its IP address.)
2. Add collections. A collection is associated with only one network and/or con-
troller with access to the signals on that network.
3. Attach signals to the collection (found on the same network). Signals can be
chosen individually from the Signal Selector dialog box or from the Signal
Database (SDB) browser.
Any errors encountered while
issuing commands are posted in
the Log View. 4. From the Device menu, select the commands (or associated buttons) Auto
Configure (Trip Log only), Get from Database , Validate ,
Build , and Download .
5. The configuration (.reb file) can be exported, which produces a .prj file.
Configuration
This section defines the four major areas of interest when configuring the Data His-
torian as follows:
• Create configuration
• Collections
• Signals
• Dead bands
4 • Data Historian GEI-100278B
1005 of 1016
Creating the Data Historian Configuration
Ø To create a configuration
Or click
• From the File menu, select New. The New dialog box displays.
Click the System

Configuration tab.
Select Data Historian

Configuration and
click OK.
1006 of 1016
Modifying the Device Name
The Outline View on the left side of the window displays the following:
The Data Historian is given the
default name, dh1. You can modify
this device name and then enter the
Host Name and Host IP Address.
Ø To modify a Data Historian device name

1. From the Outline View, click on the device name to highlight it.
Or double-click on the device
name. 2. From the Edit menu, select Modify. The Data Historian Addressing Pa-
rameters dialog box displays.
In most cases, the Host Name
and Host IP Address are the
same name. 3. Enter the desired device name and the correct Host Name and Host IP Ad-
dress. Click OK.
Host Addressing Parameters
The Data Historian Device

Name defaults to dh1. Enter the
new name here.
Enter the name of the computer

in the Windows domain that runs
the Data Historian service.
Enter the name of the PC in the

TCP/IP domain. This can be a
text string associated with a
server name or four numbers
separated by dots, such as
255.255.255.255.
When finished entering information, click OK.
Then add a collection (refer to the section, Collections).
1007 of 1016
Collections
The Data Historian is configured by adding collections. A collection is a group of
signals found on the same network. Collections have a data management feature that
automatically deletes old files and also limits the amount of disk space the files can
use. The following type of collections can be added:
• Controller Live Data
• Controller Capture Buffer
• PC Live Data
• Drive Capture Buffer
• Trip Log
Insert Collection
Ø To insert a collection
1. From the Outline View, click on Collections.
Or click the right mouse button
and select Insert First. 2. From the Edit menu, select Insert First. The Insert Collection dialog box
displays.
Select one of the

following collection types.
Note For descriptions

of the collection types,
refer to the parapgraphs
that follow.
Click OK.
1008 of 1016
An extra load is placed on the
controller for each collection. Controller Live Data
Controller Live Data collects data directly from the controller. The controller
must be on a DLAN+ and running a DLAN+ software. The Data Historian computer
does not have to be on a DLAN+. Controller Live Data collection starts a process on
the controller.
Enter the maximum Enter the maximum time
size (in MB) for the (in hours) that the data will
directory holding the remain on the disk before
collected data. being automatically
deleted.

colection (also the
name of the Data
Historian subdirectory
for the data collected).
Enter the rate (ms)
that the data is
collected from the
data source.
Enter up to 50
characters describing
the collection.
Select the controller
name from which the
data is collected.
Select the name of the
DLAN+ from which the
signals are collected.
Click OK.
1009 of 1016
Controller Capture Buffer
Controller Capture Buffer uploads a capture buffer when the status changes from
capturing to capture complete. The only signals in this collection are the status
signals from the capture buffers. Each capture buffer upload is written to a separate
file in the same collection directory. The status signal can be either on the DLAN+
or EGD network.
Enter the maximum size (in MB) for the directory holding the collected data.
Enter the maximum time (in hours) that the data will remain
on the disk before being automatically deleted.
Enter the name of the collection
(also is the
name of the Data Historian
subdirectory for the data that the
Data Historian collects).
Enter the rate (ms) that the data

is collected from the data
source.
Enter up to 50 characters
describing the collection (this
description will be the title for the
CSV file).
Select the controller name from
where the data is
being collected.

network from where the signals
are collected.
When finished, click OK.
Select this option to print the .csv file to the default Select this option to write data to a
printer. This option is only available when "Create .csv file in addition to the .dca file.
CSV File" option is selected.
1010 of 1016
PC Live Data
PC Live Data collects data from DLAN+, CSF, SRTP, or EGD networks. This col-
lection takes the data from network memory maps located on the Data Historian
computer. This collection requires that the following hardware, software, and con-
figuration have been installed and are running on the Data Historian computer:
• DLAN+ collection requires an ARCNET card and driver.
• CSF collection requires an ARCNET card and CSF driver (available from GE-
Toshiba Automation Systems).
• SRTP collection requires the PLC interface software, which uses the Host
Communication Toolkit from GE Fanuc. To use this feature, you must have a
GE Fanuc License (available from GE-Toshiba Automation Systems).
• EGD collection requirements differ depending on whether or not the Data Histo-
rian is running on the CIMPLICITY® Server computer.
− If the Data Historian is running on the CIMPLICTY Server computer, then

this requires that the signals are imported into the CIMPLICITY project and
the EGD Devcom and service are installed.
The network interface can be − If the Data Historian is running on a standard computer, then this requires
created and configured by us- that a network interface is created and configured and the EGD initializa-
ing the toolbox on the Data tion file (ICNSDB.INI) exports for this computer. The standard computer
Historian computer. must be on the control network Ethernet. The EGD Service must also be in-
stalled and running.
Note Any changes to the exchanges received by this computer requires re-exporting
the EGD initialization file (ICNSDB.INI) file and restarting the EGD Service.
1011 of 1016
Enter the maximum time (in hours) that the data will
remain on the disk before being automatically deleted.
collection (also is the
subdirectory for the data that
the Data Historian collects).
Enter the rate (ms) that the
data is collected from the
data source.
describing the collection.

network from where the
Select the source of the

timestamp used in the
data files.
Drive Capture Buffer

Drive Capture Buffer uploads a capture buffer when the signal changes. The col-
lection's only signal, Capture Complete, must be on the EGD network.
Enter the maximum time (in hours) that the data will
remain on the disk before being automatically deleted.
collection (also is the
subdirectory for the data that
the Data Historian collects).
Enter the rate (ms) that the
data is collected from the
data source.
Select the drive name from

where the data is
being collected.
EGD network from where
the signals are collected.
1012 of 1016
Trip Log
This collection also contains Trip Log is a combination of live data collected at a rate of one second and multiple
alarms and events generated capture buffers collected at a high-speed rate. The signals defined by the user for the
through the Turbine Control collection are the status signals from the capture buffers. The signals are resolved
Interface (TCI) system. A menu from the controller file, if it is open in the toolbox, or from the controller directly.
button is provided to automati- Both the capture buffer status signals and the collected signals must be on the EGD
cally generate the signal list for network.
the live data. The live data con-
sists of the signals defined in
the capture buffers.
. The Trip Log creates two collections: one PC Live collection and one Trip collec-
tion. When a trip occurs (the capture buffer status transitions to capture complete),
this collection reads from the PC Live Collection 24 hours of previously collected
data alarms and events prior to the capture buffer and writes it to the trip file. Then
data from the capture buffers is written to the same file creating a single comprehen-
sive file for the trip. The last 30 trips are saved.
Enter the name of the unit. The Collection Name will be the <Unit Name>_TRIPLOG. Enter the name of the site.
(The Collection Name is
also the name of the Data
Historian subdirectory for
the data that the Data
Historian collects).
Select the controller name

that contains the capture
buffer.
Select the name of the EGD

network from where the
Enter name of TCI computer

(default is the Data Historian
PC name). This PC creates
the alarms and events.
1013 of 1016
Signals
Once the collection is created, signals can be added. Select the desired signals from
the collection’s network signals.
Ø To add signals to the collection
1. From the Outline View, click on the collection name.
To add the next signal, click on

the signal you just inserted and
select Insert Next.
Or, click the right mouse button and select Insert First. The Signal Selector
Note The signal must be on the network chosen for collection or the get command
from the database will fail.
Signal Selector
Locate the
desired signal
from the
Regions list.
Click on the
signal to add it
to the Signal
Name list.
Click OK and
the signal
displays under
the collection
name in the
Outline View.
Tip Ä The SDB Browser can be used to add multiple signals. The query used for
the find should include the network chosen in each Insert Collection dialog box.
Using the list of signals returned from the query, you can perform a multiple select,
and then drag-and-drop from the Browser to the collection.
A completed device configuration displays in the Outline View as follows:
1014 of 1016
Dead Bands
Every signal has a parameter called a dead band. The dead band establishes a range
that the signal can vary before a new signal value is recorded. This function prevents
quantities of insignificant data from being collected. For example, a variable can
vary between 0 − 12 V, but sit at or drift near zero.
Also, if only changes of 0.1 V or more is desired, a dead band range of 0.1 can be set
to prevent a file of meaningless drift values from being created. A dead band of zero
indicates that all value changes, no matter how small, are recorded.
Set Dead Band

Ø To set the dead band for a signal
• From the Outline View, double-click on the signal name. The Modify Signal
Change the
signal name or
click Browse to
locate and select
the name.
Enter the
required dead
band and
click OK.
1015 of 1016
When troubleshooting or re- Troubleshooting
porting errors, refer to the Error
Number in the error message. Not receiving data or data is all zeros while running a Live PC collection on the
This number relates specific DLAN or CSF network.
information regarding the nature • The Data Historian computer needs an ARCNET Card installed.
of the encountered problem
• The ARCNET Card requires an ARCNET driver (DLAN) or CSF driver
(CSF) loaded and configured.
• Verify that drivers are working properly and receiving data.Are configured
on the DLAN of the target Controller.
Not receiving any data or data is invalid while running a PC Live collection on the
EGD network.
• Verify the signal is on the target EGD.
• Verify the exchange is being sent to the Data Historian computer.
• Verify the Data Historian computer is on the control network Ethernet with the
other controllers. The EGD does not route exchanges.
• Verify the installation, configuration and running status of the EGD service.
• Verify healthy exchange received by the Data Historian computer. (Use Pro-
gram Files\GE Control System Solutions\ICN_Service\EGDStatus.exe to verify
the status of the EGD exchanges on the computer.)
• A Capture Buffer Collection running from the controller or the drive is not re-
ceiving any data when the capture buffer triggers.
• Verify a running status signal from the controller capture buffer on EGD or
DLAN.
• Verify compatible firmware for capture buffer uploads. Only the Innovation Se-
ries Drives have the capture buffer upload feature.
• Verify that the Data Historian is seeing the status transition by creating a PC
Live collection of status signals.
g
Issue date: 2000-11-15 General Electric Company
GEI-100278B
 2000 by General Electric Company, USA.
1501 Roanoke Blvd. Data Historian • 15
All rights reserved.
1016 of 1016

Sonatrach Mark - VI Maintenance VOL - I PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Sonatrach Mark - VI Maintenance VOL - I PDF

Încărcat de

Drepturi de autor:

Formate disponibile

GE

Oil & Gas

1. INTRODUCTION TO SPEEDTRONIC MARK VI

2. SPEEDTRONIC MARK VI HARDWARE DESCRIPTION

3. GENERAL SOFTWARE DESCRIPTION

4. TOOLBOX SOFTWARE CONFIGURATION

7. OPERATING PROCEDURES AND INVESTIGATION

 LVDT Calibration (AUTOCAL)

9. QUESTION AND ANSWER

Course Duration: 5 Days

SPEEDTRONIC MARK* VI - Maintenance

Customized for: SONATRACH (ALGERIA)

Customer Training Job: 0622457

Customer : SONATRACH (ALGERIA)

Should further information be desired or should particular problems arise that

Reviewed Verified Validate

Customized for: SONATRACH (ALGERIA)

Customized for: SONATRACH (ALGERIA)

If further assistance or technical information is desired, contact the nearest GE Sales or

© 2004 - 2007 General Electric Company, USA. All rights reserved.

* Trademark of General Electric Company

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

Note Indicates an essential or important procedure, condition, or statement.

Isolation of test equipment from the equipment under test

To minimize hazard of electrical shock or burn, approved

To prevent personal injury or equipment damage caused by

Chapter 1 Overview 1-1

Chapter 2 System Architecture 2-1

GEH-6421L Mark VI Control System Guide Volume15

Chapter 3 Networks 3-1

Chapter 4 Codes, Standards, and Environment 4-1

Chapter 5 Installation and Configuration 5-1

Chapter 6 Tools and System Interface 6-1

Chapter 7 Maintenance and Diagnostics 7-1

GEH-6421L Mark VI Control System Guide Volume17

Chapter 8 Applications 8-1

Glossary of Terms G-1

• Speed control during turbine startup

Mark VI I/O Board Rack

Ethernet Data Highway

(48) Contact Inputs. 1 ms SOE

(2) 3-Phase Gen/Line Voltage, (1) 3-Phase Gen. Current

• GEH-6403 Control System Toolbox for a Mark VI Controller (for details of

Acronyms and Abbreviations

Summarized NFPA National Fire Protection Association

GEH-6421L Mark VI Control System Guide Volume21

Chapter 2 System Architecture

To Optional Customer Network Enterprise Layer

Gas Turbine Steam Turbine Generator

Typical Mark VI Integrated Control System

Control Operator Interface (COI)

An Alarm Window is provided and an alarm is selected by touching it. Then

Link to Distributed Control System (DCS)

Plant Data Highway (PDH)

The exciter is supplied in NEMA 1 freestanding floor-mounted indoor type metal

Static Starter Control System

The control cabinet contains an Innovation Series controller in a Versa Module

The static starter cabinet is a ventilated NEMA 1 free-standing enclosure made of

Controller UCVx Fan I/O Processor

VCMI Communication Board with Controller Interface Board

Cooling Fan Fan 24 Vdc