GEH-6800 - Vol - II 2 PDF

GE Energy GEH-6800_Vol_II
Mark* VIe Control

Migration from Mark V Control, Volume II
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.
© 2011 General Electric Company, USA. All rights reserved.

Issued: 2011-05-30
* Trademark of General Electric Company

ARCNET is a registered trademark of Datapoint Corporation.
Bussmann is a registered trademark of Cooper Bussmann, Incorporated
CompactFlash is a registered trademark of SanDisk Corporation.
IEEE is a registred trademark of Institute of Electrical and Electronics Engineers.
Neutrino and QNX are registered trademarks of QNX Software Systems, LTD.
To:
Readers Comments GE Energy
Documentation Design, Rm. 297
1501 Roanoke Blvd.
Salem, VA 24153–6492 USA
Fax: 1–540–387–8651
(GE Internal DC *278–8651)
We welcome comments and suggestions to make this publication more useful.

Your Name Today’s Date If needed, how can we contact
you?
Your Company’s Name and Address Job Site Fax No ........................................
Phone No ...................................
GE Requisition No. E-mail .........................................
Your Job Function / How You Use This Publication Publication No. Address
Publication Issue/Revision
Date
General Rating
Excellent Good Fair Poor Additional Comments
Contents ...............................................
Organization ...............................................
Technical Accuracy ...............................................
Clarity ...............................................
Completeness ...............................................
Drawings / Figures ...............................................
Tables ...............................................
Referencing ...............................................
Readability ...............................................
Specific Suggestions (Corrections, information that could be expanded on, and such.)
Page No. Comments
............................................................................................. ..................................................................................................
............................................................................................. ..................................................................................................
............................................................................................. ..................................................................................................
............................................................................................. ..................................................................................................
.............................................................................................. ..................................................................................................
.............................................................................................. ..................................................................................................
Other Comments (What you like, what could be added, how to improve, and such) .....................................................................
.....................................................................................................................................................................................................
.....................................................................................................................................................................................................
......................................................................................................................................................................................................
......................................................................................................................................................................................................
......................................................................................................................................................................................................
......................................................................................................................................................................................................
Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?)
Superior Comparable Inferior Do not know Comments .............................................

Detach and fax or mail.
....................................................................Fold here and close with staple or tape....................................................................
Place
stamp
_______________________
here
_______________________
_______________________
GE Energy
Documentation Design, Rm. 297
1501 Roanoke Blvd.
........................................................................................Fold here first........................................................................................

Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not strictly

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

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

strictly followed in order to optimize these applications.
Attention
To prevent personal injury or damage to equipment, follow all
GE safety procedures, LOTO, and site safety procedures as
indicated by EHS.
Warning
This equipment contains a potential hazard of electric shock,

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

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

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

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

followed and only properly certified equipment is used as a
critical component of a safety system. Never assume that the
HMI or the operator will close a safety critical control loop.
Warning
Contents
Mark VIe Control Migration from Mark V Control, Volume II ................................................. 1
Contents ................................................................................................................................................... 1
PIOA ARCNET® Interface Module ......................................................................................... 1-1
ARCNET Interface (PIOA) ........................................................................................................................ 1-1
PIOA Specific Alarms ............................................................................................................................. 1-17
Common Module Alarms......................................................................................................................... 1-53
JPDV Terminal Board ............................................................................................................................. 1-54
PMVE Control I/O Module ...................................................................................................... 2-1
Control Input/Output (PMVE) .................................................................................................................... 2-1
MVRA I/O Interface Board ...................................................................................................................... 2-13
MVRA Specific Alarms........................................................................................................................... 2-45
MVRB I/O Interface Board ...................................................................................................................... 2-56
MVRB Specific Alarms........................................................................................................................... 2-69
MVRC I/O Interface Board ...................................................................................................................... 2-75
MVRC Specific Alarms........................................................................................................................... 2-83
MVRF I/O Interface Board ...................................................................................................................... 2-86
MVRF Specific Alarms ......................................................................................................................... 2-105
Common Module Alarms....................................................................................................................... 2-114
MVRP Power Board ............................................................................................................................. 2-115
HSLA Interface ................................................................................................................................... 2-127
PMVD Digital I/O Module........................................................................................................ 3-1
Digital Input/Output (PMVD)..................................................................................................................... 3-1
PMVD Specific Alarms ........................................................................................................................... 3-18
PMVP Turbine Protection I/O Module ................................................................................... 4-1
Turbine Protection (PMVD) ....................................................................................................................... 4-1
PMVP Specific Alarms............................................................................................................................ 4-32
Protection Boards from Mark V Control ..................................................................................................... 4-60
Common Module Content...................................................................................................... 5-1
Auto-Reconfiguration................................................................................................................................ 5-1
Processor Board ....................................................................................................................................... 5-2
Processor LEDs ....................................................................................................................................... 5-3
Hardware Jumpers.................................................................................................................................... 5-4
Common Module Alarms........................................................................................................................... 5-6
Replacement and Ordering.................................................................................................... 6-1
Replacement ........................................................................................................................................... 6-1
Ordering a Board...................................................................................................................................... 6-8
GEH-6800_Vol_II Contents 1
Notes
2 Contents Mark VIe Control Migration from Mark V Control

PIOA ARCNET® Interface Module
ARCNET Interface (PIOA)

Functional Description
The ARCNET I/O pack (PIOA) provides an interface for the excitation control. The
I/O pack mounts to the JPDV terminal board through a 37-pin connector. The LAN
connections are made to the JPDV.
System input to the I/O pack is through dual RJ-45 Ethernet connectors and a 3-pin
power input. Visual diagnostics are provided through indicator LEDs. Excitation control
ARCNET uses a single PIOA in the <C> core for simplex applications or a single PIOA
to <R> and <C> cores for redundant applications.
Infrared Port Not Used
PIOA I/O pack Mounted on JPDV Terminal Board and PMVE
GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-1

Installation
The PIOA I/O pack only mounts to the JPDV terminal board. JPDV has two DC-37 pin
connectors. For an ARCNET interface to the excitation control, the PIOA mounts to
the JA1 connector.
Ø To install the PIOA I/O pack

1. Securely mount the JPDV terminal board to the front core board holder.
2. Plug the PIOA I/O pack into the JA1 terminal board connector for an ARCNET
excitation control interface.
3. Mechanically secure the I/O pack 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-37 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 PIOA
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 PIOA by plugging in the connector on the side of the I/O 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.
If the configuration being downloaded contains I/O packs with

different module IDs than the configuration currently running,
the download may install incorrect firmware to some I/O packs.
If this occurs, make sure the controller is running the new
configuration, restart the entire system, and then start the
Attention ToolboxST Download Wizard again.
1-2 Mark VIe Control Migration from Mark V Control

ARCNET
Ø To add a PIOA module for ARCNET support
1. From the Component Editor, click the Hardware tab.
2. From the Tree View, right-click the Distributed I/O item and select Add Module.
The Add Module Wizard dialog box displays.

This page is not used for the ARCNET configuration. Click Next.

Ø To configure the ARCNET interface for the exciter
1. From the Component Editor Tree View, select the desired PIOA.
2. Click the Parameters tab in the Summary View.

Operation
Refer to the following sections in the chapter, Common Module Content:
• Auto-Reconfiguration
• Processor Board
• Processor LEDs
Input/Output Signals
The I/O interface acquisition board (BIOA) has a UART to interface the processor to the
RS-485 (no longer used), an ARCNET controller chip to interface the processor to the
excitation control DLAN+ LAN, and a programmed complex programmable logic device
(CPLD) to provide the glue logic for the hardware interfaces. The serial communication
LEDs (ARx, ATx, Rx, Tx) are on the BIOA board, but driven by the processor.
ID Line
The processor board and acquisition board within the I/O pack contain electronic ID parts
that are read during power initialization. A similar part located with each terminal board
DC-37 pin connector allows the processor to confirm correct matching of I/O pack to
terminal board and report board revision status to the system level control.
Power Management
The I/O pack includes power management in the 28 V input circuit. The management
function provides soft start to control current inrush during power application. After
applying power, the circuit provides a fast current limit function to prevent an I/O pack or
terminal board failure from propagating back onto the 28 V power system. When power
is present and working properly, the green PWR indicator will light. If the current limit
function operates, the indicator will be out until the problem is cleared.
Connectors
The I/O pack contains the following connectors:
• DC-37 pin connector on the underside of the I/O pack connects directly to the JPDV
terminal board. The connector contains the ID signal, DLAN+ (ARCNET) signals,
and RS-485 signals (no longer used).
• RJ-45 Ethernet connector, ENET1 on the side of the PIOA is the primary system
interface
• Second RJ-45 Ethernet connector, ENET2 on the side of the PIOA is the redundant
or secondary system interface
• 3-pin power connector on the side of the PIOA is for 28 V dc power for both the I/O
pack and terminal board

Password Protection
If a password(s) was set in the General tab Property Editor for the ToolboxST component,
the following function requires a password.
Modify Data Modify Design
Add Module ✓ ✓
Note The first time you attempt a password-protected function, the Enter Password
dialog box displays. All protected functions performed during the remainder of the
ToolboxST session do not require re-entering the password.
Specifications
Item Specification
Number of channels One RS-485 channel (no longer used), and one DLAN+ channel.
Input Filter and isolation LAN wires connect to the JPDV board.
DLAN+ filtering is on the JPDV board. The DLAN+ is a transformer isolated LAN with termination
resistance on the primary side of the transformer. The transformer and termination resistance is
located on the BIOA board.
RS-485 filtering and termination (no longer used) is on the JPDV terminal board.
Frame rate RS-485 has a 32 Hz frame rate (no longer used).
DLAN+ is a change detect LAN. Command messages are sent to the excitation control master
when command data is changed by the controller.
Fault detection Loss of communications
Temperature -30 to 65 ºC (-22 to 149 ºF)
Diagnostics
The I/O pack performs the following self-diagnostic tests:
• A power-up self-test that includes 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 board,
and processor board to confirm that the hardware set matches, followed by a check
that the application code loaded from flash memory is correct for the hardware set
• Monitoring for loss of communications

Status LEDs
Refer to the Processor LEDs section in the Common Module Content chapter.
The PIOA uses the following four additional LEDs for serial communication status:
• ARx flashes on and off when ARCNET messages are being received by PIOA.
• ATx flashes on and off when ARCNET messages are being transmitted by PIOA.
• Rx flashes when RS-485 data bytes are being received by PIOA (no longer used).
• Tx flashes when RS-485 data bytes are being transmitted by PIOA (no longer used).

Configuration
Parameter Description Choices
NetworkType The network protocol used IONet-485, ARCNET
TCDA1PromRev TCDA1 EPROM revision ** F1ACE, F1ACM, F1ACN,
F1BCE, F1BCM, F1BCN
F1BCE, F1BCM, F1BCN
F1BCE, F1BCM, F1BCN
TCEA1PromRev TCEA1 EPROM revision ** F1ACK, F1ACM, F1BEC
** No longer used when TCDA has been replaced with PMVD
Protection
GenBkr1CloseTime The anticipated time required to close the breaker, in cycles 0 — 255 cycles
The number of cycles required between the time the
breaker closure is initiated from the Mark Ve controller
to the time the breaker actually closes. The constant
is specified in cycles so it is independent of the
turbine/generator set frequency. The constant is necessary
for breaker closure to occur at approximately zero phase
difference between the generator and the system bus for a
zero current flow through the breaker at closure time. The
Turbine vendor specifies the value since the constant is
dependent on breaker type.
GenBkr2CloseTime The anticipated time required to close the breaker, in cycles 0 — 255 cycles
The number of cycles required between the time the
breaker closure is initiated from the Mark Ve control to the
time the breaker actually closes. The constant is specified
in cycles so it is independent of the turbine/generator set
frequency. The constant is necessary for breaker closure
to occur at approximately zero phase difference between
the generator and the system bus for a zero current flow
through the breaker at closure time. The Turbine vendor
specifies the value since the constant is dependent on
breaker type.
GenBkrAdaptLimit If adaptive close time enabled, the maximum amount of 0 — 255 cycles
compensation allowed by the control
The controller synchronizing function adjusts the defined
Breaker Close Times by comparing the time the breaker
closure signal was sent from the controller to the time the
breaker actually closed, as the actual time may change
with the age of the breaker. The Breaker Adjust Limit
constant specifies the limit the control is allowed to adjust
the Breaker Close Time constants. The adjustments are
made in increments of one. For the values above, the
initial close time is set at five cycles. If the actual required
close time becomes eight cycles, the controller adjusts the
five to an eight, taking three closures to make this change.

If the time required becomes nine cycles, the controller
does not make another adjustment, but leaves it at eight
and generates a diagnostic alarm.
GenBkrAdaptEnable Adaptive close time enabled TRUE, FALSE
Breaker self-adaptive correction enables the controller to
use the adaptive breaker closure time function.
GenBkr1DiagEnable Log diagnostic if GenBkr1CloseTime parameter does not TRUE, FALSE
meet specification
GenBkr2DiagEnable Log diagnostic if GenBkr2CloseTime parameter does not TRUE, FALSE
meet specification
GenVoltDiagEnable Log diagnostic if 125 V dc has problem TRUE, FALSE
This parameter (Gen Panel 125 V dc Diagnostic Enable)
controls the activity of a diagnostic alarm generated upon
the loss of availability of generator breaker close voltage.
This is typically not enabled for mechanical or compressor
drive applications.
TripSystem Type of Trip Board used EXT, FPT, GAS, MED,
LARGE
Type Application Trip Board
MED Medium and TCTS
Fitchburg steam
turbines
GAS All gas turbines TCTG
LARGE Large steam turbines TCTL
EXT Large steam turbines TCTE
System Type of control system used LM, SIMPLEX, TMR
HPBaseSpdIndex*** For TCEAG#A, HP Base/Full Load Frequency 3000, 3600, 3980, 4800,
HP Base Speed Index parameter specifies the HP shaft 4860, 5100, 7100, 7491,
design speed. The rotor design speed is fixed and is 7833
independent of operating speed. This constant must match
the hardware jumper settings or a diagnostic alarm will
be generated.
LPBaseSpdIndex*** For TCEAG#A, LP Base/Full Load Frequency NotUsed, 2880, 3300, 4150,
LP base_speed index specifies the LP shaft design speed. 4670, 4980, 6500
The LP shaft design speed is fixed and is independent of
the operating speed. Therefore, 100% operating speed
may or may not correspond to 100% design speed. This
constant must match the hardware jumper settings or a
diagnostic alarm will be generated.
HPOverSpdIndex*** For TCEAG#A, the binary representation of the desired HP 0 – 255 cnts
trip frequency
HP overspeed index is the rated design speed percentage
that the rotor is allowed to reach before an overspeed
condition generates an alarm. This constant must match
the hardware jumper settings or a diagnostic alarm will be
generated. Each count represents 0.25 percent.
*** No longer used when TCEA has been replaced with PMVP

LPOverSpdIndex*** For TCEAG#A, the binary representation of the desired LP 0 – 255 cnts
trip frequency
LP overspeed_index is the design speed percentage the
rotor reachs before an overspeed condition generates an
alarm. This constant must match the hardware jumper
settings or a diagnostic alarm will be generated. Each
count represents 0.25 percent.
TripAnticationEnable*** Trip Anticipation Enable TRUE, FALSE
This function monitors the turbine's acceleration. The
acceleration can be so high that the turbine reaches and
exceeds the overspeed point in an extremely short time.
By the time the controller issues the trip and the valves
react accordingly, the turbine may already have been
damaged. When this high acceleration rate is detected
and this function is enabled, the controller control issues
a trip instead of waiting for the overspeed detection. Trip
anticipate is used exclusively on large steam turbines.
LPAccelCheckEnable*** For TCEAG#B, enable for LP acceleration check TRUE, FALSE
HPBreakAwaySpdRatio*** For TCEAG#B, this is the percent of HP speed at which 0 – 128%
the LP shaft speed should be greater than zero. This only
applies to two-shaft turbines.
LPBreakAwaySpdRatio*** For TCEAG#B, signal not used in TCEA code 0 – 128%
HPOverspeedTripFreq*** For TCEAG#B, the HP Overspeed Trip Frequency, in 0 – 16363 Hz
pulses per second
This is the HP input frequency for overspeed trip setting.
Enter the pulse frequency for the emergency overspeed
trip setpoint. For example, if the emergency overspeed
setting was 110% of rated speed, then the value should be
set to 3600 times 110%, or 3960 pulses/second.
LPOverspeedTripFreq*** For TCEAG#B, the LP Overspeed Trip Frequency, in 0 – 16363 Hz
pulses per second
This is the LP input frequency for overspeed trip setting.
Enter the pulse frequency for the emergency overspeed
trip setpoint. For example, if the emergency overspeed
setting was 110% of rated speed, then the value should be
set to 3600 times 110%, or 3960 pulses/second.
HPFullLoadFreq*** For TCEAG#B, the HP Base/Full Load Frequency, in 0 — 16363
pulses per second
This is the HP input frequency for 100 percent rated speed.
Enter the pulse frequency from the magnetic pickups for
100% rated speed. For example, if 100% rated speed is
1800 rpm and the pickup wheel has 120 teeth, the correct
value is: 1800 RPM x 120 pulses/revolution /
60 seconds/minute = 3600 pulses/second

LPFullLoadFreq*** For TCEAG#B, the LP Base/Full Load Frequency, in 0 – 16363 Hz
pulses per second
This is the LP input frequency for 100 percent rated speed.
Enter the pulse frequency from the magnetic pickups for
100% rated speed. For example, if 100% rated speed is
1800 rpm and the pickup wheel has 120 teeth, the correct
value is: 1800 RPM x 120 pulses/revolution /
60 seconds/minute = 3600 pulses/second
NumLPInterruptsBtwnCheck*** This is the number of LP speed interrupts between 1 – 15 cnts
acceleration checks. Each interrupt represents eight teeth
passing (for TCEAG#B F1BE# PromRevs).
NumInterruptsForSpdCalc*** Number of LP speed interrupts for speed calculation(for 1 – 15 cnts
TCEAG#B F1BE# PromRevs)
MinLPProtFreq*** Minimum LP speed (in Hz) to enable protection(for 1 – 32767 Hz
TCEAG#B F1BE# PromRevs)
LPAccelLimit*** LP acceleration limit (in Hz/sec)(for TCEAG#B F1BE# 1 – 32767 Hz / sec
PromRevs)
DropNumber The ARCNET address of the PIOA, expressed in 0x31 - 0xFE
Hexadecimal format
GenerateEvents Generate Sequence of Events (SOE) records for changes Enable, Disable
in excitation logic input signals received through the
ARCNET interface with the exciter
BaudRate The baud rate of the RS–485 network (no longer used) 1000 KB, 750 KB
CoreType This is the type of digital I/O core used. The DD digital I/O DD, OTHER
core has 192 contact inputs (0 outputs). All other digital I/O
cores have 96 contact inputs and 60 relay outputs.
InDCore Determines if the module resides in the D core (TRUE), or TRUE, FALSE
in the C, R, S, or T cores (FALSE)
SimplexEX Determines if the attached excitation control has only one TRUE, FALSE
master core
Contact Inputs
ContactInput Condition of input (diagnostic alarms are only enabled Unused, Used
when the contact input is used)
SignalInvert Inversion makes signal true if contact is open Normal, Invert
SeqOfEvents Record contact transitions in sequence of events Enable, Disable
DiagVoteEnab Enable voting disagreement diagnostic Enable, Disable

Relay Outputs
RelayOutput Condition of relay (diagnostic alarms are only Unused, Used
enabled when the contact input is used)
Boolean Inputs
Input Condition of input Unused, Used
DiagVoteEnab Enable voting disagreement diagnostic Enable, Disable
Analog Inputs/Output
Usage Condition of signal Unused, Used
Scale This is the type of scaling to perform on input None, Logical, Counts, Frequency,
value. It affects conversion from the old Mark FreqLow, Percent, Degrees
V control binary fix point notation to the newer
floating point (based upon input or output type).
TMR_DiffLimit Diag Limit for TMR input vote difference, in percent 0 - 200
Flame Detectors
FlameDet Condition of input Unused, Used
This enables use of flame detectors on gas turbine
systems.
FlameLimitLo Flame Threshold Limit Low 0 – 255 pulses
This is the first of two flame threshold limits for
each detector. Threshold is based on the number
of pulses generated by the flame detectors in
1/16th of a second. A value of 2 in this field
is equivalent to a 32 Hz signal from the flame
detectors. Normal operation produces a 300 Hz
signal or about 18 pulses in 1/16th of a second. A
Lower detection setting equals higher sensitivity.
FlameLimitHi Flame Threshold Limit High 0 - 255 pulses
This is the second of two flame threshold limits
for each detector. Selection of the low or high
threshold limit is based on the status of Boolean
signals L28FD_PRI_HI (for flame inputs 1 through
4) and L28FD_SEC_HI (for flame inputs 5 through
8). Threshold is based on the number of pulses
generated by the flame detectors in 1/16th of a
second. A value of 2 in this field is equivalent to
a 32 Hz signal from the flame detectors. Normal
operation produces a 300 Hz signal, or about 18
pulses in 1/16th of a second.
Scale Type of scaling to perform on input value Counts
TMR_DiffLimt Diag Limit for TMR input vote difference, in hertz 0 – 160 Hz
Boolean Outputs
Output Condition of Output Unused, Used
GenerateEvents FALSE

DTBA Jumper Configuration
Core Location Revision

<QDn>
6
<CD> Rev. DTBAG#A
<DD> 6, 8
Jumper Isolates Position Application Notes

BJ1 1–9 In = Connect +125 Out = Remove for testing only. Isolates the 125
V dc Interrogation Disconnect V dc positive bus from the output wiring
BJ2 10–18
voltage to contact +125 V dc to help troubleshoot ground faults on the
inputs Interrogation 125 V dc system.
BJ3 19–27 voltage from
contact inputs
BJ4 28–36
BJ5 37–46
DTBB Jumper Configuration

<QDn>
7
<CD> Rev. DTBBG#A
<DD> 7,9

BJ1 47–56 In = Connect Out = Disconnect Remove for testing only. Isolates the
contact contact positive interrogation voltage bus from
BJ2 57–66
interrogation interrogation the external wiring to help troubleshoot
BJ3 67–76 voltage from J8 voltage from J8 ground faults on the interrogation voltage
BJ4 77–86 to the individual to the individual bus system.
contact input contact input
BJ5 87–96
circuit excitation circuit excitation
terminal board terminal board
points. points.

DTBC Jumper Configuration
<QDn>
<CD> 8 Rev. DTBCG#A
Jumpers Position Application Notes

Pn and Mn
1 Both In = Mark Ve control Both Out = Dry contact Always Install Jumpers in Pairs
2 supplies power to output output Install corresponding (Pn and Mn) jumpers for
3 solenoid driver output
4 Solenoid driver output For example, insert P8 and M8 for solenoid
5 circuit 8
6 Voltage depends on Remove corresponding (Pn and Mn)
7 application jumpers for dry contact outputs
8 For example, remove P10 and M10 for dry
9 contact circuit 10
10
11
12
13
14
15
16
17
18

DTBD Jumper Configuration
<QDn>
9
<CD> Rev. DTBDG#A
optional

Pn and Mn
1 Both In = Mark Ve Both Out = Dry contact output Always Install Jumpers in Pairs
2 control supplies power Install corresponding (Pn and Mn) jumpers for
3 to output solenoid driver output.
5 circuit 38
10
11
12
13
14
15
16

PIOA Specific Alarms
Note Alarms that reference RS-485, the TCEA, and the TCDA are shown for legacy
compatibility purposes only. These alarms are not applicable when using the new
PMVD and PMVP modules.
33
Description Complete loss of communication with IONet-485.
Possible Cause
• Bad/Disconnected RS-485 cable; Digital and Protections cores powered down
Solution
• Replace/reconnect RS-485 cable; power up the cores
34
Description Complete loss of communication with ARCNET.
Possible Cause
• No ARCNET devices on the network

• Disconnected or bad ARCNET cable
Solution
• Reconnect or replace the ARCNET cable.
35
Description Invalid Frame Rate: [ ]ms. Only [ ]ms Rate is supported
Possible Cause
• The PIOA only supports a 40 ms controller frame rate.
Solution
• Set the controller frame rate to 40 ms
50 - 52
Description Lost communication with TCDA [ ].
Possible Cause
• Bad/disconnected RS-485 cable; TCDA powered down; hardware failure
Solution
• Replace/reconnect RS-485 cable; power up the cores; replace TCDA if necessary

53 - 55
Description Lost communication with TCEA [ ].
Possible Cause
• Bad/disconnected RS-485 cable; TCEA powered down; hardware failure
Solution
• Replace/reconnect RS-485 cable; power up the cores; replace TCEA if necessary
56 - 58
Description Software/HW Jumper Configuration mismatch on TCEA [ ].
Possible Cause
• Configurations for HPOverspeedTrip, LPOverspeedTrip, or System don't match the jumper configurations on TCEA
Solution
• Verify the I/O configuration against the jumper settings
Note A reboot of the PIOA is required to clear this diagnostic alarm.
59 - 61
Description EPROM mismatch: TCDA [ ] reports MajorRev: [ ]MinorRev: [ ]
Possible Cause
• The configured EPROM revisions do not match the EPROMs installed on TCDA
Solution
• Verify the I/O configuration against the EPROM revision
62 - 64
Description EPROM mismatch: TCEA [ ] reports MajorRev: [ ] MinorRev: [ ]
Possible Cause
• The configured EPROM revisions do not match the EPROMs installed on TCEA
Solution
• Verify the I/O configuration against the EPROM revision

65 - 67
Description Configuration failed for TCDA [ ]: Invalid message.
Possible Cause
• TCDA Memory error
Solution
• Cycle power on TCDA
68 - 70
Description Configuration failed for TCEA [ ]: Invalid message.
Possible Cause
• TCEA Memory Error; EPROM revision mismatch
Solution
• Cycle power on TCEA; Verify I/O configuration with EPROM revision
2400 - 2402
Description TCDA [ ] is unused.
Possible Cause
• Unused diagnostic alarm
Solution
• Reset Diagnostic alarms
2403-2405
Description TCDA [ ] Memory changed.
Possible Cause
Solution

2406-2408
Description TCDA [ ] Plug JO1 is disconnected.
Possible Cause
• The indicated cable (JO1 or JO2) on the TCDA card in the QD (or CD) core is either damaged or disconnected.
• This diagnostic is not likely to be caused by a component failure on the TCDA card, and it is extremely unlikely to
be caused by a component failure on the TCRA card.
• However, this diagnostic can also be generated if fuse FU1 is blown on the TCPS card in the core to which the TCDA
is attached. Fuse FU1 protects the P24 voltage output, which drives not only the TCDA's relays on the TCRA cards,
but also serves as the interrogation voltage in determining if JO1 and JO2 are connected correctly between the TCDA
and its TCRAs. If fuse FU1 is blown, the TCDA will generate both of the following diagnostics, even if all cables are
connected properly:
• TCDA Plug JO1 is disconnected; TCDA Plug JO2 is disconnected
• On applications of TCDAG#A, and applications of TCDAG#B prior to revision G#BE_, loss of fuse FU1 will cause an
additional diagnostic alarm to occur:
• TCDA BATREF signal failure (plug JQ)
Solution
• Inspect the indicated cable for damage, and re-attach or replace it as necessary.
• If all cables appear to be connected properly, check to see if fuse FU1 is blown on the TCPS card that drives the TCDA.
• Replace the TCDA and/or TCRA cards only as a last resort.
• Be warned that plugging in or unplugging cable JO1 or JO2 with power applied may cause the TCDA card to reset due to
transient voltage spikes on the power bus. It would be best to remove power from the TCDA before moving these cables.

2409-2411
Description TCDA [ ] Plug JO2 is disconnected.
Possible Cause
• The indicated cable (JO1 or JO2) on the TCDA card in the QD (or CD) core is either damaged or disconnected.
• This diagnostic is not likely to be caused by a component failure on the TCDA card, and it is extremely unlikely to
be caused by a component failure on the TCRA card.
• However, this diagnostic can also be generated if fuse FU1 is blown on the TCPS card in the core to which the TCDA
is attached. Fuse FU1 protects the P24 voltage output, which drives not only the TCDA's relays on the TCRA cards,
but also serves as the interrogation voltage in determining if JO1 and JO2 are connected correctly between the TCDA
and its TCRAs. If fuse FU1 is blown, the TCDA will generate both of the following diagnostics, even if all cables are
connected properly:
• TCDA Plug JO1 is disconnected; TCDA Plug JO2 is disconnected
• On applications of TCDAG#A, and applications of TCDAG#B prior to revision G#BE_, loss of fuse FU1 will cause an
additional diagnostic alarm to occur:
• TCDA BATREF signal failure (plug JQ)
Solution
• Inspect the indicated cable for damage, and re-attach or replace it as necessary.
• If all cables appear to be connected properly, check to see if fuse FU1 is blown on the TCPS card that drives the TCDA.
• Replace the TCDA and/or TCRA cards only as a last resort.
• Be warned that plugging in or unplugging cable JO1 or JO2 with power applied may cause the TCDA card to reset due to
transient voltage spikes on the power bus. It would be best to remove power from the TCDA before moving these cables.

2412-2414
Description TCDA [ ] BATREF signal failure (plug JQ).
Possible Cause
• The BATREF signal on the TCDA card in the QD (or CD or DD) CORE is absent.
• Possible reasons for a BATREF signal failure are as follows:
• (1) The fuse for plug J12A, J12B, or J12C is blown in the [PD] core.
• (2) The cable running from the [PD] core (plug J12A, J12B, or J12C) to the DTBA contact input terminal board (plug
J12) is either damaged or disconnected.
• (3) The cable running from the DTBA contact input terminal board (plug JQR, JQS, or JQT) to the TCDA card (plug JQ)
is either damaged or disconnected.
• (4A) Fuse FU4 is blown on the TCPS card in the core to which the TCDA is attached (applications with
DS200TCDAG#BE_ and later, including all DS200TCDAH1B cards). Fuse FU4 protects the circuits for P15A/N15a and
P15B/N15B voltage outputs. The P15B/N15B voltages are used on the TCDA to generate 24 V dc, which is used to drive
one of the relays (KR, KS, or KT) on the DTBA contact input terminal board. When dropped out, these relays remove the
125 volt reference signal from the TCDA which is used in generating the BATREF signal.
Note P15B is on JP-3, N15B is on JP-2, BCOM is on JP-1. P24B is on JQ-1 (measure with respect to JQ- 50, N1 5B)
• (4B) Fuse FU1 is blown on the TCPS card in the core to which the TCDA is attached (applications with
DS200TCDAG#BD_ and earlier, including all DS200TCDAG#A cards) on the TCPS card in the core to which the TCDA
is attached. The FU1 fuse protects the circuits for P24 voltage output, which is used to drive one of the relays (KR, KS, or
KT) on the DTBA contact input terminal board. When dropped out, these relays remove the 125 volt reference signal
from the TCDA which is used in generating the BATREF signal. If fuse FU1 is blown, the TCDA will generate all three
of the following diagnostics, even if all cables are connected properly:
• TCDA Plug JO1 is disconnected; TCDA Plug JO2 is disconnected; TCDA BATREF signal failure (plug JQ)
Note P24V is on JP-7, DCOM is on JP-6
• (5) (Unlikely) A component has failed in either the BATREF generation or detection circuit on the TCDA.
• The TCDA can detect if power from the PDM is reaching the DTBA (plug J12), but it cannot tell if power is also
reaching the DTBB (plug JY) from the DTBA (plug JY). Thus, if there is a problem with cable JY, then the TCDA
will be unable to tell that half of its inputs do not work.
Solution
• Trace through the circuit path described above from the [PD] core to the TCDA. Replace fuses or reattach/replace
cables as necessary. Be sure to check fuse FU1 on the TCPS if the TCDA is generating all three diagnostic alarms
as described above.
• Replace the TCDA board only as a last resort.

2416-2703
Description TCDA [ ] Contact input [ ] failure.
Possible Cause
• A component has failed within the indicated input signal processing circuit (#[nn]) on the TCDA card in the QD (or CD
or DD) core.
• This fault condition can be detected as soon as the component failure occurs, regardless of the state of the contact input
on the terminal board (DTBA/B).
• (1) This fault only applies to component failures on the TCDA. Hardware faults along cables JQ or JR, or on the terminal
boards themselves cannot normally be detected.
• (2) A BATREF failure, although causing all TCDA inputs to fail, is detected separately and will not produce these
alarm messages.
• (3) Noisy contact inputs (with superimposed AC, for example) may also cause these diagnostic alarms to occur. Older
TCDA cards are more susceptible to noise than the newer surface-mount TCDA design.
Solution
• Replace the affected TCDA card. However, if noise on the TCDA contact inputs is the problem, find a way to filter the
noise so that it is not introduced into the DTBA/DTBB terminal boards.

2704-2883
Description TCDA [ ] Relay output [ ] failure.
Possible Cause
• The indicated relay circuit (#[nn]) on the TCDA card in the QD (or CD) module does not appear to be functioning properly.
• This fault is detected by monitoring the current drawn through cable JO1 or JO2 from a TCRA card. There are several
possible failures that can lead to this diagnostic alarm:
• (1) There is a component failure on the TCDA card, so that the TCDA either cannot properly operate the relay, or
cannot properly detect the state of the relay.
• (2) Cable JO1 or JO2 is not properly connected. This fault is usually indicated by the additional presence of diagnostic
alarm "Plug JO[n] is disconnected"
• (3) Cable JO1 or JO2 is damaged.
• (4) (Unlikely) There is a component failure on the TCRA card.
• Because the relay drivers are actually located on the TCRA card, the TCDA is not normally capable of detecting a failure
in either the relay driver or the relay itself. (Relay coil burned out, for example.)
Solution
• The first thing to check is cables JO1 and JO2. JO1 carries signals for relays 1 through 30; JO2 carries those for relays 31
through 60. Make sure these cables are securely plugged in at both ends (one end on the TCDA, one end on the TCRA),
and that the cables appear to be undamaged. Also check to make sure that the cables are plugged into the correct sockets,
since there are several options depending on whether the card is used in simplex or TMR mode. The appropriate cable
(JO1 or JO2) may even need to be replaced.
Note Be warned that plugging in or unplugging cable JO1 or JO2 with power applied may cause the TCDA card to reset
due to transient voltage spikes on the power bus. It would be best to remove power from the TCDA before moving these
cables. If replacing the appropriate cable still does not fix the problem, then the fault is almost certainly with the TCDA
card. Replacing the TCDA should then fix this problem.
• Replace the TCRA board only as a last resort.

2884-2886
Description TCEA [ ] is unused.
Possible Cause
Solution
2887-2889
Description TCEA [ ] Memory changed
Possible Cause
Solution
2890-2892
Description TCEA [ ] HP reading, hardware trouble
Possible Cause
• The High Pressure shaft speed is calculated utilizing two different types of hardware. This diagnostic means the difference
in the two readings exceeds its allowable limit.
Solution
• Replace the TCEA board.
2893-2895
Description TCEA [ ] LP reading, hardware trouble
Possible Cause
• The Low Pressure shaft speed is calculated utilizing two different types of hardware. This diagnostic means the difference
in the two readings exceeds its allowable limit
Solution

2896-2898
Description TCEA [ ] HP base speed config trouble
Possible Cause
• Discrepancy between the I/O configuration and the jumper settings associated with the HP base speed definition.
Solution
• Check the I/O configuration against the jumper settings.
2899-2901
Description TCEA [ ] LP base speed config trouble
Possible Cause
• Discrepancy between the I/O configuration and the jumper settings associated with the LP base speed definition.
Solution
2902-2904
Description TCEA [ ] HP over speed config trouble
Possible Cause
• Discrepancy between the I/O configuration and the jumper settings associated with the HP over speed definition.
Solution
2905-2907
Description TCEA [ ] LP over speed config trouble
Possible Cause
• Discrepancy between the I/O configuration and the jumper settings associated with the LP over speed definition.
Solution

2908-2910
Description TCEA [ ] System config trouble
Possible Cause
• Discrepancy between the I/O configuration and the jumper settings associated with the System configuration definition.
Solution
2911-2913
Description TCEA [ ] Trip board config trouble
Possible Cause
• Discrepancy between the I/O configuration and the actual hardware (for example, the trip board TCTx)
The trip board must be as follows:
Gas Turbine = TCTG
Med Steam Turbine = TCTS
Large Steam Turbine = TCTL
Extended Large Steam= TCTE
• Bad connectivity in cable JL, TCEA
Solution
• Check the I/O configuration against the hardware (trip board) in [P] slot 4. Also check cable on connector JL.
2914-2916
Description TCEA [ ] Digital output, 025DRV
Possible Cause
• The relay driver circuitry associated with relay 25 (K3) is bad.
Solution
• Check the cabling on TCEA JL connector.

• If the cabling is okay, replace the TCEA.
• If the alarm still indicates trouble, replace the trip board TCTx.

2917-2919
Description TCEA [ ] Digital output, 0ETR1
Possible Cause
• The relay driver circuitry associated with relay ETR1 is bad. The relationship is:
Gas,TCTG MED LG STM,TCTL LG STM,TCTE
STM,TCTSL
ETR1 [X] K5 K11 K4 K11
ETR1 [Y] K4 K5 K5 K5
ETR1 [Z] K6 K13 K6 K13
Solution

2920-2922
Description TCEA [ ] Digital output, 0ETR2
Possible Cause
• The relay driver circuitry associated with relay ETR2 is bad. The relationship is:
STM,TCTS
ETR2 [X] K8 K10 K10 K10
ETR2 [Y] K7 K4 K11 K4
ETR2 [Z] K9 K12 K12 K12
Solution

2923-2925
Description TCEA [ ] Digital output, 0DRV0 (clamp)
Possible Cause
• The relay driver circuitry associated with circuit 0DRV0, the servo clamping function, is bad.
Solution


2926-2928
Description TCEA [ ] Digital output, 0DRV1 (KE1,ELO)
Possible Cause
• The relay driver circuitry associated with circuit 0DRV1, is bad. On Large Steam, this is the ELO, k19 (electrical
lockout); on Medium Steam, this is the KE1, k19 (emergency trip bypass test 1); on Gas turbines, this circuit is not used.
Solution

2929-2931
Description TCEA [ ] Digital output, 0DRV2 (KE2)
Possible Cause
• The relay driver circuitry associated with circuit 0DRV2, is bad. On Large Steam, this circuit is not used; on Medium
Steam, this is the KE2, k18 (emergency trip bypass test 2); on Gas turbine, this circuit is not used.
Solution

2932-2934
Description TCEA [ ] Digital output, 0ALARM
Possible Cause
• The Alarm (horn) on the TCEB board, connected via the PTBA jumper "AL_EN" and the trip board, TCT_, will have lost
at least one of its 3 inputs and may not function (2/3 voting may override the problem).
Solution


2935-2937
Description TCEA [ ] TMR check trouble, ETR1
Possible Cause
• The three ETR1 relays are not in agreement (for example, one is bad).
Solution
• If no ETR1 relay driver diagnostic alarm is indicated, then suspect the trip board TCT_; determine which ETR1 is bad by
looking for a corresponding vote exchange diagnostic message; verify that the ETR1 relay is not loose.

STM,TCTS
ETR1 [X] K5 K11 K4 K11
ETR1 [Z] K6 K13 K6 K13
• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [X[ JL-4;
[Y] JL-3; [Z] JL-5.
Note Since the feedback signal for monitoring this condition is connected to all three TCEA boards via the same conductor
in all "JL" cables, an input circuit failure (short to common) on any of the TCEA boards could cause an error in the feedback
status read by all TCEA boards. Therefore, if the actions above do not correct the diagnostic condition, the other TCEA
boards should be replaced, and/or the other "JL" cables should be checked, and replaced if necessary.
2938-2940
Description TCEA [ ] TMR check trouble, ETR2
Possible Cause
• The three ETR2 relays are not in agreement (for example, one is bad).
Solution
• If no ETR2 relay driver diagnostic alarm is indicated, then suspect the trip board TCT_; determine which ETR2 is bad by
looking for a corresponding vote exchange diagnostic message; verify that the ETR2 relay is not loose.

STM,TCTS
ETR2 [X] K8 K10 K10 K10
ETR2[Y] K7 K4 K11 K4
ETR2 [Z] K9 K12 K12 K12
• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [X] JL-7;
[Y] JL-6; [Z] JL-8.

2941-2943
Description TCEA [ ] TMR check trouble, PTR1
Possible Cause
• The three PTR1 relays are not in agreement (for example, one is bad).
Solution
• If no PTR1 relay driver RD2 failure diagnostic is indicated, then suspect the trip board TCT_; determine which PTR1 is
bad by looking for a corresponding vote exchange diagnostic message; verify that the PTR1 relay is not loose.

STM,TCTS
PTR1 [X] K13 K7 K7 K7
PTR1 [Y] K14 K8 K8 K8
PTR1 [Z] K15 K9 K9 K9
• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [R] JL-9; [S] JL-10;
[T] JL-11. If problem persists, replace the appropriate MVRA.
2944-2946
Possible Cause
Solution
• If no PTR2 relay driver RD3 failure diagnostic is indicated, then suspect the trip board TCT_; determine which PTR2 is
bad by looking for a corresponding vote exchange diagnostic message; verify that the PTR2 relay is not loose.

STM,TCTS
PTR2 [X] K19 K15 K15 K15
PTR2 [Y] K20 K16 K16 K16
PTR2 [Z] K21 K17 K17 K17
• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [R] JL-12; [S]
JL-13; [T] JL-14. If problem persists, replace the appropriate MVRA.

2947-2949
Possible Cause
Solution
• If no PTR3 relay driver RD4 failure diagnostic is indicated, then suspect the trip board TCT_; determine which PTR3
relay is bad by looking for a corresponding vote exchange diagnostic message; verify that the PTR3 relay is not loose.
Gas,TCTG Steam, TCTE

PTR3 [R] K10 K19
PTR3 [S] K11 K20
PTR3 [T] K12 K21
JL-16; [T] JL-17. If still a problem replace the appropriate MVRA.
2950-2952
Possible Cause
• The three PTR4/ETR3 relays are not in agreement (for example, one is bad).
Solution
• If no PTR4 relay driver RD5 failure diagnostic is indicated, then suspect the trip board TCT_; determine which
PTR4/ETR3 relay is bad by looking for a corresponding vote exchange diagnostic message; verify that the PTR4/ETR3
relay is not loose.
Gas,TCTG TCTE
PTR4 [R] K16 ETR3 K14
PTR4 [S] K17 ETR3 K6
PTR4 [T] K18 ETR3 K18
JL-19; [T] JL-20. If still a problem replace the appropriate MVRA.

2953-2955
Description TCEA [ ] Loopback, relay, ETR1
Possible Cause
• The feedback of an ETR1 contact disagrees with the required or intended state of this particular relay; the [Z] (TCE3)
board only checks the ETR1 relay driven by itself. Likewise for [X] and [Y].
Solution
• If no 0ETR1 digital output diagnostic is indicated, then suspect the trip board TCT_; verify that the ETR1 relay is not loose.

STM,TCTS
ETR1 [X] K5 K11 K4 K11
ETR1 [Z] K6 K13 K6 K13
[Y] JL-3; [Z] JL-5.
2956-2958
Description TCEA [ ] Loopback, relay, ETR2
Possible Cause
• The feedback of an ETR2 contact disagrees with the required or intended state of this particular relay; the [Z] (TCE3)
board only checks the ETR2 relay driven by itself. Likewise for [X] and [Y].
Solution
• If no 0ETR2 digital output diagnostic is indicated, then suspect the trip board TCT_; verify that the ETR2 relay is not loose.

STM,TCTS
ETR1 [X] K8 K10 K10 K10
ETR1 [Y] K7 K4 K11 K4
ETR1 [Z] K9 K12 K12 K14
[Y] JL-6; [Z] JL-8.

2959-2961
Description TCEA [ ] Loopback, relay, DRV1
Possible Cause
• The feedback of a relay contact disagrees with the required or intended state of this particular relay; on medium steam
(TCTS) this is the KE1 (emergency trip bypass); on Large steam (TCTL), this is the ELO (electrical lockout); it is not
used on the Gas Turbine (TCTG). There is only one relay in this circuit; the voting is done at the logic level, as opposed
to the relay contact level.
Solution
• If no 0DRV1 digital output diagnostic is indicated, then suspect the trip board TCT_; verify that the relay is not loose:
KE1 is k19; ELO is k19. If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL"
continuity JL-15.
2962-2964
Description TCEA [ ] Loopback, relay, DRV2
Possible Cause
• The feedback of a relay contact disagrees with the required or intended state of this particular relay; on medium steam
(TCTS) this is the KE2 (emergency trip bypass); it is not used on Large Steam (TCTL) or Gas Turbine (TCTG). There is
only one relay in this circuit; the voting is done at the logic level, as opposed to the relay contact level.
Solution
• If no 0DRV2 digital output diagnostic is indicated, then suspect the trip board TCT_; verify that the relay is not loose:
KE2 is k18; If replacing the trip board does not fix the problem, replace TCEA and/or check cable JL continuity JL-16.

2965-2967
Description TCEA [ ] Loopback, relay, PTR1
Possible Cause
• The feedback of a PTR1 contact disagrees with the required or intended state of this particular relay; the [Z] (TCE3) board
only checks the PTR1 relay driven by [T] MVRA; Likewise there is a partnership between [X] and [R], [Y] and [S].
Solution
• If all three TCEx boards are reporting this problem, suspect the application code; the relay is driven from the MVRA and
checked by the TCEA; the application code must write the required relay status to an appropriate coil to inform the TCEA
of what MVRA is doing. If it is on one TCEA board only, then either a PTR1 relay driver RD2 failure diagnostic or a
PTR1 TMR check trouble diagnostic should be indicated. Verify that the PTR1 relay is not loose.

STM,TCTS
PTR1 [R] K13 K7 K7 K7
PTR1 [S] K14 K8 K8 K8
PTR1 [T] K15 K9 K9 K9
• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [X] JL-9; [Y] JL-10;
[Z] JL-11. If still a problem replace the appropriate MVRA.

2968-2970
Description TCEA [ ] Loopback, relay, PTR2
Possible Cause
• The feedback of a PTR2 contact disagrees with the required or intended state of this particular relay; the [Z] (TCE3) board
only checks the PTR2 relay driven by [T] MVRA; Likewise there is a partnership between [X] and [R], [Y] and [S].
Solution

STM,TCTS
PTR1 [R] K19 K15 K15 K15
PTR1 [S] K20 K16 K16 K16
PTR1 [T] K21 K17 K17 K17

STM,TCTS
PTR2 [R] K19 K15 K15 K15
PTR2 [S] K20 K16 K16 K16
PTR2 [T] K21 K17 K17 K17
• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [X] JL-12; [Y]
JL-13; [Z] JL-14. If still a problem replace the appropriate MVRA.
JL-16; [Z] JL-17 for Gas Turb, or JL-15 for the Med Steam, or JL-16 for Large Steam. If still a problem replace the
appropriate MVRA.

2971-2973
Description TCEA [ ] Loopback, relay, KP- 1/PTR3/MLO
Possible Cause
• The feedback of a KP-1/PTR3/MLO relay contact disagrees with the required or intended state of this particular relay;
KP-1 (k6) is used on Med Steam; PTR3 (k10, k11, k12) are used on Gas Turbine; MLO (k13) is used on Large Steam; and
PTR3 (k19, k20, k21) are used on Extended Large Steam. On Gas Turbine and Extend Large Steam, the [Z] (TCE3)
board only checks the PTR3 relay driven by [T] MVRA; likewise there is a partnership between [X] and [R], [Y] and [S].
Solution
of what the MVRA is doing. If it is on one TCEA board only, then either a PTR3 relay driver RD4 failure diagnostic or a
PTR3 TMR check trouble diagnostic should be indicated. Verify that the appropriate relay is not loose;
JL-16; [Z] JL-17 for Gas Turb, or JL-15 for the Med Steam, or JL-16 for Large Steam. If still a problem replace the
appropriate MVRA.
2974-2976
Description TCEA [ ] Loopback, relay, KP- 2/PTR4/ORST
Possible Cause
• The feedback of a KP- 2/PTR4/ORST relay contact disagrees with the required or intended state of this particular relay;
KP-2 (k14) is used on Med Steam/ PTR3 (k16, k17, k18) are used on Gas Turb/MLO (k14) is used on Large Steam.
On gas turb, the [Z] (TCE3) board only checks the PTR4 relay driven by [T] MVRA; Likewise there is a partnership
between [X] and [R], [Y] and [S].
Solution
• If all three TCEx boards are reporting this problem, suspect the application code; the relay is driven from MVRA and
checked by TCEA; the application code must write the relay status to an appropriate coil to inform TCEA what MVRA
is doing. If it is on one TCEA board only and if diag 1357 is not showing up then suspect the trip board TCT_; make
sure the relay is not loose; If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL"
continuity [X] JL-18; [Y] JL-19; [Z] JL 20 for Gas Turb, or JL-16 for the Med Steam, or JL-17 for Large Steam; If still
a problem replace the appropriate MVRA.

2977-2979
Description TCEA [ ] Loopback, solenoid, OTS
Possible Cause
• Applicable to Large Steam only; The OTS (k18) relay contact disagrees with the required or intended position of this
particular relay
Solution
• If all three TCEx boards are reporting this problem, suspect the application code; the relay is driven from MVRA and
checked by TCEA; the application code must write the relay status to an appropriate coil to inform TCEA what MVRA
is doing. If it is on one TCEA board only and if diag 1358 is not showing up then suspect the trip board TCT_; make
sure the relay is not loose; If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL"
continuity JL-18; If still a problem replace the appropriate MVRA.
2980-2982
Description TCEA [ ] Loopback, solenoid, ETD1/SOL1/MTSV
Possible Cause
• This diagnostic is checking a composite function (for example, one made up of more than one relay). If other diagnostics
associated with these relays show up, they should be resolved first. This diagnostic will be true when the feedback signal,
indicating actual voltage applied to the trip solenoid coil, disagrees with the required or intended value for this solenoid:
• ETD1 – Med Steam, TCTS – elect trip device
– eqn is ETD1= (ETR1 OR KE1)
AND (PTR1 OR KP1)
SOL1 – Gas Turb, TCTG – solenoid #1

– eqn is SOL1= (ETR1 and PTR1)
MTSV – Large Steam, TCTL – mech Trip sol valve.

– eqn is MTSV= ((not ETR1) or (not PTR1) or L5E)
ETD1 – Extended Large Steam, TCTE – elect trip device

– eqn is ETD1= (ETR1 and PTR1)
• This check point is downstream of the TMR hardware, after the hardware has necked down to a single circuit.
Solution
• If all three TCEx boards are reporting this problem, suspect the trip board TCT_, the power cable J7W, or wiring problems
on the output screws of PTBA; if only one processor board reports the problem, suspect the detection circuitry (for
example, cable JL, TCT_, TCEA).

2983-2985
Description TCEA [ ] Loopback, solenoid, ETD2/SOL2/ETSV
Possible Cause
• This diagnostic is checking a composite function (for example, one made up of more than one relay). If other diagnostics
associated with these relays show up, they should be resolved first. This diagnostic will be true when the feedback signal,
indicating actual voltage applied to the trip solenoid coil, disagrees with the required or intended value for this solenoid:
• ETD2 – Med Steam, TCTS – elect trip device
– eqn is ETD2= (ETR2 OR KE2) AND (PTR2 OR KP2)

– eqn is SOL2= (ETR2 and PTR2)
ETSV – Large Steam, TCTL – elect Trip sol valve.

– eqn is ETSV= (ETR2 and PTR2)
ETD2 – Extended Large Steam, TCTE – elect trip device

– eqn is ETD2= (ETR2 and PTR2)
Solution
• Trip board TCT_, the power cable J7W, or wiring problems on the output screws of PTBA; if only one processor board
reports the problem, suspect the detection circuitry (for example, cable JL, TCT_, TCEA).

2986-2988
Description TCEA [ ] Loopback, solenoid, SOL3/ELO
Possible Cause
• 32 • PIOA I/O Interface Module GEI-100617B Mark Ve Alarm ID Alarm Description Possible Cause Solution AND
(PTR1 OR KP1) SOL1 – Gas Turb, TCTG – solenoid #1 – eqn is SOL1= (ETR1 and PTR1) MTSV – Large Steam, TCTL
– mech Trip sol valve. – eqn is MTSV= ((not ETR1) or (not PTR1) or L5E) ETD1 – Extended Large Steam, TCTE – elect
trip device – eqn is ETD1= (ETR1 and PTR1) This check point is downstream of the TMR hardware, after the hardware
has necked down to a single circuit. any of the TCEA boards could cause an error in the feedback status read by all TCEA
boards. Therefore, if the actions above do not correct the diagnostic condition, the other TCEA boards should be replaced,
and/or the other "JL" cables should be checked, and replaced if necessary. 2983-2985 TCEA[ ] Loopback, solenoid,
ETD2/SOL2/ETSV This diagnostic is checking a composite function (for example, one made up of more than one relay).
If other diagnostics associated with these relays show up, they should be resolved first. This diagnostic will be true when
the feedback signal, indicating actual voltage applied to the trip solenoid coil, disagrees with the required or intended
value for this solenoid: ETD2 – Med Steam, TCTS – elect trip device – eqn is ETD2= (ETR2 OR KE2) AND (PTR2 OR
KP2) SOL2 – Gas Turb, TCTG – solenoid #2 – eqn is SOL2= (ETR2 and PTR2) ETSV – Large Steam, TCTL – elect Trip
sol valve. – eqn is ETSV= (ETR2 and PTR2) ETD2 – Extended Large Steam, TCTE – elect trip device – eqn is ETD2=
(ETR2 and PTR2) This check point is downstream of the TMR hardware, after the hardware has necked down to a single
circuit. trip board TCT_, the power cable J7W, or wiring problems on the output screws of PTBA; if only one processor
board reports the problem, suspect the detection circuitry (for example, cable JL, TCT_, TCEA).
Note Since the feedback signal for monitoring this condition is connected to all three TCEA boards via the same
conductor in all "JL" cables, an input circuit failure (short to common) on any of the TCEA boards could cause an error
in the feedback status read by all TCEA boards. Therefore, if the actions above do not correct the diagnostic condition,
the other TCEA boards should be replaced, and/or the other "JL" cables should be checked, and replaced if necessary.
2986-2988 TCEA[ ] Loopback, solenoid, SOL3/ELO solenoid:
• N/A – for Med STEAM ETSV – Extended Large Steam, TCTE

– eqn is ETSV=(ETR3 and PTR3)
Solution
• If all three TCEx boards are reporting this problem, suspect:

• Gas Turb: the trip board TCTG, the power cable J7W, or wiring problems on the output screws of PTBA;
• Large Stm: the trip board TCTL, the power cable J18 (AC power), or wiring problems on the output screws of PTBA;
• If only one processor board reports the problem, suspect the detection circuitry (for example, cable JL, TCT_, or TCEA).

2989-2991
Description TCEA [ ] Loopback, solenoid, SOL4/MLO
Possible Cause
• This diagnostic is checking a composite function for Gas Turb, nothing for Med Steam, and a single Relay for Large
Steam. If other diagnostics associated with these relays show up, they should be resolved first. This diagnostic will be
true when The feedback signal, indicating actual voltage applied to the solenoid coil, disagrees with the required or
intended value for this solenoid:
• N/A – for Med STEAM

eqn is SOL4 = (ETR2 and PTR4)
MLO – Large Steam, TCTL – mech Lockout valve

eqn is MLO = relay MLO
Solution
• If all three TCEx boards are reporting this problem, suspect:

• Gas Turb: The trip board TCT_, the power cable J7W, or wiring problems on the output screws of PTBA;
• LargeStm: The trip board TCT_, the power cable J18 (AC power), or wiring problems on the output screws of PTBA;
• If only one processor board reports the problem, suspect the detection circuitry (for example, cable JL, TCT_, or TCEA).
2992-2994
Description TCEA [ ] Loopback, solenoid, 0RST
Possible Cause
• This diagnostic is for Large Steam only. If other diagnostics associated with this function show up, they should be
resolved first. This diagnostic will be true when The feedback signal, indicating actual voltage applied to the solenoid coil,
disagrees with the required or intended value for this solenoid. This check point is downstream of the TMR hardware,
after the hardware has necked down to a single circuit.
Solution
• If all three TCEx boards are reporting this problem, suspect: the trip board TCT_, the power cable J18 (AC power), or
wiring problems on the output screws of PTBA; if only one processor board reports the problem, suspect the detection
circuitry (for example, cable JL, TCT_, or TCEA).

2995-2997
Description TCEA [ ] Loopback, solenoid, OTS
Possible Cause
• This diagnostic is for Large Steam only. If other diagnostics associated with this function show up, they should be
resolved first. This diagnostic will be true when The feedback signal, indicating actual voltage applied to the solenoid coil,
disagrees with the required or intended value for this solenoid. This check point is downstream of the TMR hardware,
after the hardware has necked down to a single circuit.
Solution
• If all three TCEx boards are reporting this problem, suspect the trip board TCT_, the power cable J18 (ac power), or
wiring problems on the output screws of PTBA; if only one processor board reports the problem, suspect the detection
circuitry, (for example, cable JL, TCT_, or TCEA).
2998-3000
Description Unused diagnostic alarm
Possible Cause
Solution
3002-3004
Description TCEA [ ] Slow synch check 25X relay
Possible Cause
• The synch check relay, L25X (sometimes designated L25A), is not picked up when the synch relay L25 picks up. This is
wrong, the synch check relay should always pickup and be out of the way when the synch relay picks up.
• The synch relay hardware identifications are:
• L25 – synch relay, k3
L25X – synch check relay, k2
L25P – synch relay, k1
Solution
• If L25X is not picking up, Check the "CSP" sequencing: verify that the L25X_PERM coil is being driven with correct
logic. L25X_PERM must be true before L25X will pick up. It is also required that the turbine speed be simulated if not
doing an actual startup. If L25X is picking up slow (as opposed to not picking up), then check the system parameters:
what is the configured phase for L25X? What is the breaker close time? What is the slip when the breaker is being
closed? Are these set correctly?

3005-3007
Description TCEA [ ] Synch lockup, 25 relay failure
Possible Cause
• The synch check relay, L25 is picked up when it is not supposed to be.
• The synch relay hardware identifications are:
• L25 – synch relay, k3
L25X – synch check relay, k2
L25P – synch relay, k1
Solution
• If reported by all three processors, suspect the trip board TCT_. Otherwise, suspect the detection circuit and check
cable JL, TCEA, and TCT_.
• Proper identification of the failed card may require removal of two of the three JL cables and verification of operation of
the remaining circuit, rotating through the cards until all failures are identified.
3008-3010
Description TCEA [ ] Breaker 1 close time out of limits
Possible Cause
• The measured time for breaker #1 to close on the last synch operation was outside of the limits as defined by the following
equation: [(Config Bkr close time) - (Config limit)] < [measured bkr close time] < [(Config Bkr close time)+(Config
limit)].
Solution
• If reported by all three processors, suspect the generator breaker contact (required interconnection) to the PTBA
termination board, or cabling JM. If this is not the problem, verify that the generator breaker does not have an excessive
closure time and that the configured breaker close time is correct; if still a problem, consider opening up the allowable
configured limit, maybe it is too tight. If only reported by one processor, suspect TCEA or cabling JL.

3011-3013
Description TCEA [ ] Breaker 2 close time out of limits
Possible Cause
• The measured time for breaker #2 to close on the last synch operation was outside of the limits as defined by the following
equation: [(Config Bkr close time) - (Config limit)] < [measured bkr close time] < [(Config Bkr close time)+(Config
limit)].
Solution
• If reported by all three processors, suspect the generator breaker contact (required interconnection) to the PTBA
termination board, or cabling JM. If this is not the problem, verify that the generator breaker does not have an excessive
closure time and that the configured breaker close time is correct; if still a problem, consider opening up the allowable
configured limit, maybe it is too tight. If only reported by one processor, suspect TCEA or cabling JL.
3014-3016
Description TCEA [ ] 25P trouble
Possible Cause
• This is a loop back test on relay L25P, k1 on TCT_; it means the feedback of P (synch permissive relay) contact disagrees
with the required or intended position of this particular relay; the (TCE3) board only checks the P relay; it is driven by
MVRA, [RST], the relay is on TCT_ and the voting is done at the logic level.
Solution
• If reported by all three processors, and diag 1353 is not showing, suspect the application code; the relay is driven from
MVRA and checked by TCEA; the application code must write the relay status to an appropriate coil (L25PX) to inform
TCEA what MVRA is doing; also, since there is only one relay, suspect trip board TCT_; Make sure the k1 relay is not
loose. If still a problem suspect MVRA's. If it is on one TCEA board only then suspect the TCEA board or the cable JL.
3017-3019
Description TCEA [ ] 52GX 125 V dc voltage missing
Possible Cause
• The generator panel 125 V dc is not present on the PTBA board.
Solution
• Check for 125 V dc on PTBA, screws 35 to 41; if that is correct suspect trip board TCT_, cable JN.

3020-3022
Description TCEA [ ] Relay trouble, K4-1
Possible Cause
• Protection relay k4-1, on the TCT_ trip board, is out of step with the majority.
• Med/Large Steam, TCTS/TCTL: k4- 1 = k20
Gas Turb, TCTG: k4-1 = k22
Solution
• Check for a loose or missing relay. Replace relay if necessary. If still a problem, replace the trip board TCT_, check
cabling JL, and replace TCEA.
3023-3025
Possible Cause
Solution

3026-3028
Possible Cause
Solution
3029-3031
Possible Cause
Solution

3032-3034
Description TCEA [ ] 4 relay disagreement
Possible Cause
• Protection relays k4-1, 2, 3, 4 are not all in the same state (on the TCT_ trip board).
• Med/Large Steam, TCTS/TCTL: k4- 1=k20, k4_2=k21
k4-3=k22, k4-4=k23
Gas Turb, TCTG: k4-1=k22,
k4_2=k23
k4-3=k24, k4-4=k25
Solution
3035-3037
Description TCEA [ ] Voltage missing, 0diag32, 125 V dc
Possible Cause
• The 125 V dc voltage is not present on the TCT_ board.
Solution
• Check cable J7W on TCT_. If still a problem, suspect trip board TCT_, cable JL, TCEA.
3038-3040
Description TCEA [ ] Voltage missing, 0diag33, 24VR
Possible Cause
• The 24VR voltage is not present (or out of limits) on the TCT_ board
Solution
• Check all three JL cables. If still a problem, suspect trip board TCT_, cable JL, TCEA.

3041-3043
Description TCEA [ ] Voltage missing, 0diag34, 115 V ac
Possible Cause
• The 115 V ac voltage is not present (or out of limits) on the TCT_ board. This is applicable to Large Steam only.
Solution
• Check J18 cable. If still a problem, suspect trip board TCT_, cable JL, or TCEA.
3044-3046
Description TCEA [ ] Power supply out of limits, P5
Possible Cause
• The TCEA P5V is out of limits.
Solution
• Replace the TCEA board (or adjust the P5V via R29 on TCEA).
3047-3049
Possible Cause
Solution
3050-3052
Description TCEA [ ] Power supply out of limits, N15
Possible Cause
• The TCEA N15V is out of limits.
Solution

3053-3055
Possible Cause
Solution
• This is the relay coil supply; it is diode selected on the trip board TCT_; The loss one P24V supply should not cause a
problem.
3056-3058
Description TCEA [ ] Power supply trouble, P24AS/N24AS
Possible Cause
• The TCEA P24A is out of limits.
Solution
• Check TCEA Fuse FU4; measure voltage across it, if not zero then replace it. If still a problem, check for a wiring
problem external (PTBA screws 65 and 66). If still a problem, replace TCEA.
3059-3061
Description TCEA [ ] Ground fault on P24AS/N24AS Bus
Possible Cause
• The TCEA auxiliary supply, P24A, has a ground fault.
Solution
• Check for a ground fault on the external wiring (PTBA screws 65 and 66). If still a problem replace TCEA.
Note On Gas turbine applications with a GE/Reuter-Stokes flame detector interface module, interchanging the isolated P24
with the control power wired to the interface module will result in this condition. Correct wiring such that the isolated P24
supplies the power for the transducers and the control power for direct interface with the control panel are kept separate.
3062-3064
Possible Cause
• The TCEA P335 is out of limits.
Solution
• Replace TCEA.

3065-3067
Description TCEA [ ] Power supply out of limits, DCOM
Possible Cause
• The TCEA DCOM is out of limits.
Solution
• Verify that the DCOM, stab connection, is connected to each TCEA.
3068-3091
Description TCEA [ ] Flame detector [ ] out of limits
Possible Cause
• Signal input(s) at TCEA connector JK-1(#1)...JK-8(#8) appear to be greater than 2Hertz while at (or near) ZERO speed.
Solution
• Replace Flame detector. If still a problem, check external wiring; replace TCEA.
3092-3094
Description TCEA [ ] IONet address trouble
Possible Cause
• IONet address out of range.
Solution
• Check jumpers; if still a problem, replace TCEA.
3095-3097
Description TCEA [ ] Diagnostic task trouble
Possible Cause
• A/D converter hung up.
Solution
• Replace TCEA.
3098-3100
Description TCEA [ ] Emerg online OS test fail, ETR1
Possible Cause
• Med Steam only, failed an emergency online overspeed system test.
Solution
• Replace TCEA card, then JL cables. Ensure IONet communications to TCEA are functioning.

3101-3103
Description TCEA [ ] Emerg online OS test fail, ETR2
Possible Cause
Solution
• Replace TCEA card then JL cables. Ensure IONet communications to TCEA are functioning.
3104-3106
Description TCEA [ ] Prim online OS test fail, PTR1
Possible Cause
Solution
• Replace TCEA card, then MVRA card and then JD cables. Ensure IONet communications to TCEA are functioning.
3107-3109
Description TCEA [ ] Prim online OS test fail, PTR2
Possible Cause
Solution
• Replace TCEA card, then MVRA card and then JD cables. Ensure IONet communications to TCEA are functioning.
3110-3112
Description TCDA [ ] Relays dropped due to IONet-485 failure.
Possible Cause
• The TCDA did not hear the digital output packet on the IONet in a timely fashion. This can be caused by a complete
loss of IONet communications (e.g. IONet cable disconnected, IONet master rebooted), or because the IONet master
simply did not send the output packet. Note that with a complete IONet failure, the TCDA will not be able to report
this condition until communications are re-established.
Solution
• If this alarms occurs, but not because of any action on your part (resetting cores, for example) then check for bad or
intermittent cabling on the IONet. Also check for proper IONet termination. As a last resort, you could try replacing
the TCDA and/or IOMA/STCA, but this is not likely to solve the problem. If all else fails, call your local GE service
representative.

3113–3536
3113-3208
Description QD1 Core ContactInputs "Logic Signal [ ] Voting Mismatch",
Possible Cause
• A problem with a status input. This could be the device, the wire to the terminal board, or the terminal board.
3209-3304
Possible Cause
3305-3400
Possible Cause
3409-3440
Description TMR P Core/Simplex R TCEA BooleanInputs "Logic Signal [ ] Voting Mismatch",
Possible Cause
3457-3488
Description Simplex S TCEA BooleanInputs "Logic Signal [ ] Voting Mismatch",
Possible Cause
3505-3536
Description Simplex T TCEA BooleanInputs "Logic Signal [ ] Voting Mismatch",
Possible Cause
3561-3599
3561–3565
Description TMR P Core/Simplex R TCEA Analog "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",
Possible Cause

3566–3573
Description TMR P Core/Simplex R TCEA FlameDetector "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",
Possible Cause
3574–3578
Description Simplex S TCEA Analog "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",
Possible Cause
3579-3586
Description Simplex S TCEA FlameDetector "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",
Possible Cause
3587-3591
Description Simplex T TCEA Analog "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",
Possible Cause
3592-3599
Description Simplex T TCEA FlameDetector "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",
Possible Cause
Common Module Alarms

Refer to the Common Module Alarms section in the Common Module Content chapter.

JPDV Terminal Board
JPDV is the power distribution board for the MVRA and MVRF, up to two controllers, an
Ethernet switch and up to two PIOA I/O packs. The board is the interface for the PIOA
to the DLAN+ to the excitation control.
JPDV Power Distribution Board
Installation
Ø To install cabling (signals and power)
1. Connect the power cables going to MVRA and MVRF, if present.
2. Connect the power cables to the Ethernet switch, if present.
3. Connect the power cables to the controllers, if present.
4. Connect the power cables to the PIOA, if present.
5. Connect the DLAN+ (ARCNET) coax cable the BNC connector.
6. Connect the Power In Cable, from the power supply.

Operation
The JPDV board contains the DLAN+ filtering and passes the signal to BIOA through the
DC-37 pin connector. The JPDV routes power to the PIOA, the controllers, the MVRA
and MVRF, and the Ethernet switch.
Specifications
Item Specification
Number of channels One DLAN+(ARCNET) channel
One RS-485 channel (no longer used)
Power 28 V from the power supply
Temperature rating 0 to 60°C (32 to 140 °F)
Diagnostics
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
There are no jumpers or hardware settings on the board.

Notes

PMVE Control I/O Module
Control Input/Output (PMVE)

The PMVE module (based on the UCSA processor board) communicates and controls
one or more I/O agents across the high-speed serial link (HSSL). The PMVE supports
the MVRA, MVRB, MVRF, and MVRP boards in TMR and simplex configuration,
as well as the MVRC board in simplex configuration. Configuration parameters from
the ToolboxST* application are used for customization. The UCSA is a stand-alone
processor board that is loaded with specific software and combined with one of the
MVRx analog I/O boards to become the PMVE module.
The PMVE is controlled by the Mark VIe controller through the IONet. The controller
contains the application code blockware that can be customized for a particular turbine.
The PMVE operating system (OS) is QNX® Neutrino®, a real-time, multitasking OS
designed for high-speed, high-reliability industrial applications. Six communication
ports provide links to I/O, operator, and engineering interfaces as follows:
• RS-232C connection for setup using the COM1 port
• Ethernet connection for the IONet (two ports)
• High Speed Serial Links (HSSL) (three ports)
Note The HSSL are private special-purpose Ethernet ports that support only the I/O
agents and the PMVE.
GEH-6800_Vol_II PMVE Control I/O Module System Guide 2-1

Installation
The PMVE mounts to the location 1 plate.
Ø To install the PMVE

1. Verify that power is removed from the core.
Note Record the termination point of each Cat5e Ethernet cable before removing
them from the PMVE.
2. Remove the Cat5e Ethernet cables from the front of the PMVE.
3. Remove the power cable connected at the top of the PMVE. Observe the position of
the ferrite filter located on the power cable.
4. Loosen (do not remove) the two mounting nuts located at the top and bottom of
the PMVE. To remove the PMVE, slide it to position the upper nut in the hole in
the PMVE mounting foot and lift off.
5. Mount the new PMVE by reversing step 4. Torque the two nuts to 20 - 25 in-lbs.
6. Plug in all Cat5e Ethernet cables that were removed in step 2. Verify that the cables
are returned to the original position.
7. Plug in the power connector, then return the ferrite filter to its original position.
8. Apply power to the core.
9. Use the ToolboxST application to download and configure the module as needed.
If the configuration being downloaded contains I/O

packs/modules with different IDs than the configuration
currently running, the download may install incorrect firmware
to some I/O packs/modules. If this occurs, make sure the
controller is running the new configuration, restart the entire
Attention system, and then start the ToolboxST* Download Wizard again.

Configuring the PMVE Module
Ø To add a PMVE control I/O module
1. From the ToolboxST application, Mark VIe controller Component Editor, click
the Hardware tab.
2. From the Tree View, right-click the Distributed I/O item and select Add Module.
The Add Module Wizard dialog box displays.

Ø To configure the MVRx
1. Make desired changes to the configuration, then click OK.
Note To add additional boards, select another Port item and follow the same procedure.

Ø To setup the PMVE
The PMVE’s UCSA must be configured with a TCP/IP address prior to connecting to
the IONet Ethernet.
1. Install and configure a serial connection to the COM port on the UCSA. An RJ-45 to
DB9 adapter is required along with an Ethernet cable for the serial connection. The
adapter part number is 342A4944P1. The following figure shows the pin definition of
the UCSx RJ-45 to the COM port adapter.
2. From the Tree View, right-click the PMVE and select Setup.

3. When the Welcome wizard displays, click Next.

Operation
PMVE software can be modified The PMVE is loaded with configuration parameters specific to its application. The IEEE®
online without being restarted. 1588 protocol is used through the IONets to synchronize the clock for the PMVE and
controller to within ±100 microseconds. External data is transferred to and from the
control system database in the controller over the IONets. The PMVE propagates the
synchronization time to each of its I/O agents. Data is transferred to the I/O agents across
the HSSL every five microseconds.
UCSA Processor
The UCSA processor board (IS200UCSAH1A) is part of the PMVE module and provides
the following:
• High-speed processor with random access memory (RAM) and flash memory
• Two fully-independent 10/100 Ethernet ports with connectors Enet1 and Enet2 for
connecting to the main Mark VIe controllers' IONet ports
• Three fully-independent high-speed serial link ports with connectors R/SL1, S/SL2,
T/SL3
• One universal asynchronous receiver-transmitter (UART) type serial port with RJ-45
Connector
• Hardware watchdog timer and reset circuit
• Status-indication LEDs
• Electronic ID
• CompactFlash® support
The processor application code contains the logic to allow a UCSA to operate on one or
two IONet inputs. When using two IONet inputs, both network paths are active at all
times. A failure of either network does not disturb I/O pack operation and is indicated
through the working network connection. This arrangement is more tolerant of faults than
a classic hot-backup system in which the second port is only used after a primary port
failure is detected. The Ethernet ports on the UCSA auto-negotiate between 10 and 100
mbps speed, and between half-duplex and full-duplex operation.
Auto-Reconfiguration
Refer to the Auto-Reconfiguration section in the Common Module Content chapter.
When replacing a PAMC or PMVE, the Auto-Reconfiguration process will not function
properly unless the existing CompactFlash® card from the UCSA being replaced is
removed and installed into the new UCSA. If a new or blank CompactFlash card is used,
perform the manual setup procedure found in GEH-6700 ToolboxST User Guide for
Mark VIe Control.

Recalibration
A liquid fuel regulator with no The recalibration of a PSVO, PSVP, or PCAA servo is required when a new terminal
LVDTs would not have to be board is used on a system. The controller saves the barcode of the terminal board and
recalibrated. compares it against the current terminal board during reconfiguration load time. Any time
a recalibration is saved, it updates the barcode name to the current board.
Password Protection
If a password(s) was set in the General tab Property Editor for the ToolboxST component,
the following function requires a password.
Modify Data Modify Design

Add Module
Note The first time a password-protected function is attempted, the Enter Password
dialog box displays. All protected functions performed during the remainder of the
ToolboxST session do not require re-entering the password.
Specifications
Item Specification
Microprocessor Freescale Power pc (Power QUICC II PRO 667 MHz).
Memory 256 MB DDR SDRAM through one SODIMM Flash-backed SRAM - 8 K allocated as
NVRAM for controller functions Compact flash size is dependent on the application.
Operating System QNX Neutrino
IONet Ethernet Interface (2) Twisted pair 10BaseT/100BaseTX, RJ-45 connectors:
IONet interface to communicate with the Mark VIe controller
HSSL Interface Twisted pair 10BaseT/100BaseTX, RJ-45 connectors:
(3 ports) Proprietary Serial protocol over an Ethernet physical layer
COM ports One accessible through RJ-45 connector on front panel
For cabling, use a standard 4-pair UTP cable (for example, Ethernet cable) joined with a
null modem connector (GE part #342A4944P1)
Power Requirements 32 V dc to 18 V dc (12.5 W typical preliminary)
Environmental Operating: 0 to 65°C (32 to 149 °F)
Storage: -40 to 85°C (-40 to 185 °F)
Relative humidity: 5% to 95%, no-condensing
Weight 2 lbs
Temperature 0 to 60°C (32 to 140 °F)

Diagnostics
The I/O module performs the following self-diagnostic tests:
• A power-up self test that includes checks of RAM, flash memory, Ethernet ports, and
and processor board ID to confirm that the hardware set matches, followed by a check
that the application code loaded from flash memory is correct for the hardware set.
• Each input has sensor limit checking, open circuit detection, dc bias autonulling, and
excessive dc bias detection. Alarms are generated for these diagnostics.
Details of the individual diagnostics are available in the ToolboxST application. I/O block
SYS_OUTPUTS, input RSTDIAG can be used to direct all I/O modules to clear from the
alarm queue all diagnostics in the normal healthy state.

UCSA LEDs
• Power displays solid green when the internal 5 V supply is up and regulating. The
PAMC converts the incoming 28 V dc to 5 V dc. All other internal supplies are
derived from the 5 V.
• Online displays solid green when the PAMC is online and running application code.
• Flash flashes amber when any flash device is being accessed. DC is not used in
the PAMC application.
• Diag displays solid red when the PAMC has a diagnostic available. The diagnostic
can be viewed and cleared using the ToolboxST application.
• Link displays solid green if the Ethernet hardware interface on the PAMC has
established a link with an Ethernet port.
• Act indicates packet traffic on an Ethernet interface. If traffic is low, this LED may
flash but in most systems, it is on solid.
• On displays solid green when the USB is active.
• Boot displays solid red or flashing red during the boot process.
The boot LED is lit continuously during the boot process unless an error is detected. If
an error is detected, the LED flashes at a 1 Hz frequency. While flashing, the LED is on
for 500 ms and off for 500 ms. The number of flashes indicates the failed state. After the
flashing section, the LED turns off for three seconds. These are flashing codes:
1. Failed Serial Presence Detect (SPD) EEPROM

2. Failed to initialize DRAM or DRAM tests failed
3. Failed NOR flash file system check
4. Failed to load FPGA or PCI failed
5. CompactFlash device not found
6. Failed to start IDE driver
7. CompactFlash image not valid
If the CompactFlash image is valid but the runtime firmware has not been loaded, the
boot LED flashes continuously at a 1 Hz rate. Once the firmware is loaded, the boot
LED turns off.
Configuration
Refer to the MVRA, MVRB, MVRC, and MVRF sections for specific configuration
information.

MVRA I/O Interface Board
The MVRA is an I/O board on the PMVE using the high-speed serial link (HSSL). The
PMVE contains specialized code for the MVRA that communicates and controls the
MVRA analog and digital I/O. Configuration parameters customize MRVA operation.
The MVRA is a functional replacement for the Mark V TCQA and IOMA boards.
MVRA analog and digital I/O is as follows:
• Thermocouples (Simplex)
• Servos and LVDTs
• Pulse Rates
• Proximeters
• Analog Inputs
• Analog Outputs
• PTR Relays
• Bus and Gen Voltage
• CPD and Megawatt

Additional functions include:
• Compressor Stall
• Bus and Generator Sync
• Check Permissive
• Improved Speed and Acceleration Calculation
• Enhanced Speed Algorithm (Speed Wheel and Gear Tooth Compensation)
Installation
The MVRA mounts behind the PMVE in the rack in position 1.
Ø To install the MVRA

2. Carefully remove all ribbon cables and power cables from the board connectors.
Note The red or blue stripes are always on the left.
3. Holding the board in place, press up the three top and three bottom tabs.
4. Remove the old board and place it in a static bag.
5. Remove the new MVRA from its static bag and reverse this procedure.
6. Once the MVRA is in place, connect the HSSL link cable from the PMVE.
7. Use the ToolboxST application to configure the MVRx as needed. Refer to the
section, Configuring the PMVE Module.
Operation
Note Control software can be modified online without being restarted.
The PMVE contains configuration parameters specific to the MVRA. External data is
transferred to and from the control system database in the controller over the IONets. The
PMVE propagates the control and data to each of its I/O boards. Data is transferred to the
MVRA across the HSSL every five milliseconds.
Through internal ribbon cables, other interface boards supply additional input and output
as follows:
• Bus/Gen PT
• Sync frequency and phase
• Relay control
• Megawatt and CPD input
• Power supply monitoring
• Power to this board is supplied by an MVRP power supply
All analog and digital I/O signals are read and written at the 5 ms rate by the PMVE(s).

Regulator Diagrams
Position Regulator

Speed Ratio Regulator

Speed Ratio PI control

Liquid Fuel Regulator

Liquid Fuel with Position Feedback

Liquid Fuel PI Control

Compressor Stall Algorithm
Compressor Stall Algorithm
Items in bold are I/O pack configuration parameters. Variables with (ssi) or (sso) are
assignable.

Sync Check
The MVRA functions much like the TCQA, and includes sync check functionality. The
MVRA writes the control limits and enables the sync check logic in the FPGA. The FPGA
controls the relay enable permissive when all conditions are satisfied.
The MVRA uses a time-based algorithm, which improves speed and acceleration.
This algorithm collects the number of tooth pulses and 25Mhz tics that occurred between
those pulses within a specified time interval. The equation is as follows:
Pulse Input(E.U.) = Freq(hz) * (60.0(sec/min) / TeethPerRev) * PRScale(E.U)
The MVRA uses an enhanced speed algorithm (ESA) for speed wheels and gear tooth
pulse rate sensors.
Variability on the gear tooth wheel spacing causes variability in the speed measurement
and acceleration. The ESA measures and corrects this spacing. However, it does not
introduce latencies or correct for electronic or sensor abnormalities. If the ESA cannot
correct for the speed anomalies, it defaults to the evenly spaced algorithm. The ESA
should not be used for critical overspeed functions. The only requirement for this mapping
to occur is to enable the ESA, and set the teeth per revolution to the correct value. This can
be used for any pulse device that has multiple tooth or pulses generated per revolution, but
it must be an integer number. With a multi-gear box, the ESA is only required to know the
number of gear teeth on the sense gear. The scaling can accommodate the gearing ratios.
Note The ESA should not be used for pulse generators, or devices that generate
precision pulse rates. If the ESA tries to correct for a variation that does not exist, noise
or jitter in the speed or acceleration signal results.
Calculating Tooth Correction Factors
The correction factor is the percentage that the tooth represents of the whole (one
revolution). For example, each of four teeth in a wheel represents 25% of the whole.

Removing variation from the speed is determined by individual tooth corrections
according to the equation: where k = teeth in a revolution
The system for calculating rotation depends on parameters sensing rotation of a toothed
speed wheel, then correcting by the following equation:
Pulse Input(E.U.) = Freq(hz) * (60.0(sec/min) / TeethPerRev) * PRScale(E.U.)
Recalibration
Specifications
The MVRA has the same hardware functionality as the TCQA and IOMA.
Original TCQA ribbon cables plug directly into the MVRA to simplify replacement.
Number of Inputs Type Terminal Board

15 Thermocouples (Simplex) TBQA
8 Servos QTBA
4 Pulse inputs (TTL) QTBA/TBQB
4 Analog inputs 10 V TBQB
15 Analog inputs 4-20 mA TBQB
2 Analog outputs TBQC/TBQF
12 Vibration inputs TBQB
16 LVDT TBQF
7 Pulse Inputs (Magnetic) QTBA

Diagnostics
The MVRA board has its own ID device, which is interrogated by the PMVE. The board
ID is coded into a read-only chip containing the board serial number, board type, and
revision number. This ID is checked as part of the power-up diagnostics.
Configuration
MVRA Board Parameters
Parameter Description Selections

Min_MA_Input Minimum mA for healthy 4/20 mA input. The MVRA generates 0 to 22.5 mA (FLOAT)
an unhealthy status for any of the 4-20 mA inputs that are
less than this value.
Max_MA_Input Maximum mA for healthy 4/20 mA input. The MVRA 0 to 22.5 mA (FLOAT)
generates an unhealthy status for any of the 4-20 mA inputs
greater than this value.
LVDT_TMR_DiffLim TMR input vote difference in percentage of range. The RST 0 to 200 % (FLOAT)
controllers calculate the median value of the three TMR LVDT
values. If any of the TMR LVDTs are greater than or less than
this difference from the median value in percent, a diagnostic
is generated on the errant MVRA.
AccelCalcInMs Calc Accel using x ms (5 ms granularity) of samples. 5 to 160 ms (FLOAT)
Acceleration is the change in speed over a time delta. This
parameter specifies that time delta in ms. The longer the time
delta, the smoother the acceleration.
TBQxRevAATermBoard TBQx is a Revision AA terminal board. The TBQx Revisions No, Yes
>AA have a resistor in the feedback circuit. This generates
a gain error that must be corrected.
AVSelection TMR internal selection variables. Unused, AOut1IndivCurFdbk,
The AVSelection is used to read internal variables that are not AOut2IndivCurFdbk,
placed in signal space. SoftwareSpare
Currently to monitor the individual current feedback of the
TMR current summed analog output to determine proper
operation.
This is not a TMR-voted value, but a individual value from
each I/O pack.
Used for initial check out and for field diagnostic issues.
SyncCheckEnab Generator bus sync check enable Enables the hardware sync Disable, Enable
check function in the FPGA. The FPGA controls the sync
check permissive relay.
BusFreq Bus frequency (50 Hz or 60 Hz). The Sets the Sync check 60 Hz, 50 Hz
PLL operational frequency range in the FPGA. The FPGA
controls the sync check permissive relay.
GenMinKVolts Generator PT primary minimum sync in engineering units (kV 0 to 1000 kV or % (FLOAT)
or percent). The lowest generator kV or percentage value at
which the FPGA sync check permissive relay is enabled
BusMinKVolts Bus PT primary minimum sync in engineering units (kv or 0 to 1000 kV or % (FLOAT)
percent). The lowest Bus kV or percentage value at which the
FPGA sync check permissive relay is enabled

PhaseLimit Maximum sync phase limit. The maximum phase difference 0 to 360 Deg (FLOAT)
allowed between the bus and the generator. If the phase
difference is greater, the FPGA sync check permissive relay
is not enabled.
FreqLimit Maximum sync frequency limit. The maximum frequency 0 to 5 Hz (FLOAT)
difference between the bus and the generator allowed. If
the frequency difference is greater, the FPGA sync check
permissive relay is not enabled.
BusGenAmplitudeDiffLimit Bus gen amplitude difference Limit in Eng Units (kV or 0 to 1000 kV or % (FLOAT)
percent). The maximum kV or percentage amplitude
difference allowed between the bus and the generator. If
the amplitude difference is greater, the FPGA sync check
permissive relay is not enabled.
CompStallEnab Compressor stall enable. Enables the compressor stall Disable, Enable
algorithm on the MVRA. This uses the CPD VCO input. Use
parameters below to control the algorithm to detect the stall
on the compressor guide vanes.
TimeDelay Time delay on stall detection (ms). Time from detection 10 to 40 ms (FLOAT)
of a possible stall event and enunciating the event to the
blockware. This prevents a false detection from tripping the
turbine.
KPS3DropL Threshold pressure rate 10 to 2000 (FLOAT)
CPD low pressure limit
KPS3DropSlope Pressure rate slope 0.05 to 10 (FLOAT)
CPD drop rate limit slope
KPS3DropInter Pressure rate intercept -250 to 100 (FLOAT)
CPD Drop rate limit intercept
Pressure Rate Drop Reference = PS3i * KPS3DropSlope + KPS3DropIntercept
KPS3DropMn Minimum drop pressure rate 10 to 2000 (FLOAT)
CPD pressure rate drop reference low clamp limit.
KPS3DropMax Maximum drop pressure rate 10 to 2000 (FLOAT)
CDP pressure rate drop reference upper clamp limit.
KPS3DeltaSlope Pressure delta slope 0.05 to 10 (FLOAT)
CPD pressure delta limit slope
KPS3DeltaInter Pressure delta intercept -250 to 100 (FLOAT)
CPD pressure delta limit intercept
Pressure Delta Stall Reference = PS3i * KPS3DeltaSlope + KPS3DeltaIntercept
KPS3DeltaMax Pressure delta maximum -250 to 100 (FLOAT)
CPD maximum delta for delta stall reference

MVRA I/O Parameter Groups – Analog Inputs

InputType Type of analog input Unused, 4-20 mA
Low_Input Input mA (or V) at low value -10 to 20 mA or V (FLOAT)

Low_Value Input Value in engineering units at low mA (or V) E.U. (FLOAT)
High_Input Input mA (or V) at high value -10 to 20 mA or V (FLOAT)
High_Value Input value in engineering units at \hHigh mA (or V) E.U. (FLOAT)
Analog Input( E.U.) = Low_Value + (High_Value - Low_Value)*
[( mA input - Low_Input) / (High_Input - Low_Input)]
DiagHighEnab Enable high input limit diagnostic. If the 4-20 mA analog input Disable, Enable
exceeds the parameter Max_MA_Input and DiagHighEnab is
enabled, a diagnostic is generated.
DiagLowEnab Enable low input limit diagnostic. If the 4-20 mA analog input Disable, Enable
exceeds the parameter Min_MA_Input and DiagLowEnab is
TMR_DiffLimit Diag Limit,TMR input vote difference, in PerCent of 0 to 200 % (FLOAT)
(High_Value - Low Value). The RST controllers calculate the
median value of the three TMR analog inputs. If any of the
TMR analog inputs are greater than or less than this difference
from the median value in percentage, a diagnostic is generated
on the errant MVRA.

MVRA I/O Parameter Groups – Analog Outputs

Output_MA Output mA selection Unused, 0-20 mA,
0-200 mA
Suicide_Enab Enable suicide for faulty output current if in a TMR current Disable, Enable
sharing configuration. This enable is only used when a TMR
hardware current or d ac feedback fault occurs.
Low_MA Output mA at low value 0 to 200 mA (FLOAT)
Low_Value Output value in engineering units at low mA E.U. (FLOAT)
High_MA Output mA at high value 0 to 200 mA (FLOAT)
High_Value Output value in engineering units at high mA E.U. (FLOAT)
milliAmp Output = Low_MA + (High_MA - Low_MA)*
[(Analog Output(E.U.) - Low_Value) / (High_Value - Low_Value)]
TMR_SuicLimt Suicide threshold, for TMR operation. Load-sharing margin in 0 to 200 % (FLOAT)
mA. If any of the three individual analog outputs exceeds 50%
of the mA output plus this margin, the mA output is allowed
to suicide.
D/A_ErrLimit Suicide Threshold, for TMR operation. Defective D/A reference 0 to 200 % (FLOAT)
versus commanded output feedback, in percentage. If the
hardware command output and the commanded D/A difference
exceeds this limit for more than three frames, the mA output
performs a suicide.
OutputState State of the analog output when offline . Sets the mA output to PwrDownMode, HoldLastVal,
a known value when the MVRA is offline. Output_Value
PwrDownMode set analog output to 0.0 in engineering units.
HoldLastVal holds the analog output at the last value in
engineering units received before the MVRA went offline.
Output_Value allows the user to specified the offline value in
engineering units.
Output_Value Pre-determined value for the outputs. This specifies the E.U. (FLOAT)
engineering unit value to set analog output to, when the MVRA
goes offline.
MVRA I/O Parameter Groups – Cold Junctions

ColdJuncType Select CJ Type. This selection allows control software to Remote, Local
substitute the current terminal board’s cold junction value in
degrees with another value from application space in degrees.
ColdJuncUnit Select TC display unit in degrees C or F Deg_F, Deg_C

MVRA_IO Parameter Groups_LVDTs

Enable Enable the LVDT Disable, Enable
MinVrms LVDT V rms at Min End Stop (Normally set by auto-calibrate). 0 to 7.1 Volts (FLOAT)
The absolute value in V rms read by the LVDT when the valve
is at the minimum end position.
MaxVrms LVDT V rms at Max End Stop (Normally set by auto-calibrate). 0 to 7.1 V (FLOAT)
is at the maximum end position.
MinPosValue Position at Min End Stop in engineering units. The position in -15 to 150 % (FLOAT)
percentage to be returned by the LVDT when the valve is at
the minimum end position.
MaxPosValue Position at maximum end stop in engineering units The position -15 to 150 % (FLOAT)
in percent to be returned by the LVDT when the valve is at the
maximum end position.
LVDT Input Position = MinPosValue + (MaxPosValue - MinPosValue)*
[( Lvdt Vrms Input - MinVrms) / (MaxVrms - MinVrms)]
PositionMargin Allowable range exceed error of position in percentage. If the 1 to 10 % (FLOAT)
position exceeds the MaxPosValue or MinPosValue by this
percentage, an unhealthy status and a diagnostic is generated.
ExcitSelect Excitation monitor selection. Unused, Excit_fromR,
Not available in Mark VIe control Mark V migration. Excit_fromS, Excit_fromT
ExcitMonCal Excitation monitor calculated value in Vrms. Not available in 1 to 10 V (FLOAT)
Mark VIe control Mark V migration.
MVRA_IO Parameter Groups_Monitors

RegType Monitor regulator type selection. Allows monitoring of the Unused, Position, SpeedRatio,
regulator’s control feedback in percentage. The monitor type LiquidFuel, LiquidFuel_wPosition
must match the regulator type.
ServoNum Servo number used Servo01, Servo02, Servo03,
Select the servo feedback to be monitored. Servo04, Servo05, Servo06,
Based upon the selected monitor RegType, only one of the Servo07, Servo08
MonVxx parameters is visable or selectable.
MonVarPos Monitor variable selection for position regulator. Select one of Unused, Position1, Position2,
these to be monitored in percentage. Position3, ServoCurrentRef
MonVarLiqFuel Monitor variable selection for liquid fuel regulator. Select one Unused, Flow1, Flow2,
of these to be monitored in percentage. ServoCurrentRef
MonVarSpdRat Monitor variable selection for speed ratio regulator. Select one Unused, Pressure1, Pressure2,
of these to be monitored in percentage. Position, OuterRegErr,
OuterLoopErr, Position2,
Position1, ServoCurrentRef
MonVarLiqFuelPos Monitor variable selection for liquid fuel with position regulator. Unused, Position, OuterRegErr,
Select one of these to be monitored in percentage. OuterLoopErr, Position2,
Position1, Flow1, Flow2,
ServoCurrentRef

MVRA_IO Parameter Groups_PT

PT_Input PT primary in engineering units (kv or percent) for PT_Output. 0 to 1000 kV or % (FLOAT)
PT_Output PT output in V RMS for PT_Input - typically 115 0 to 1000 kV or % (FLOAT)
TMR_DiffLimt Diag limit, TMR input vote difference, in engineering units. The 0 to 1000 kV or % (FLOAT)
RST controllers calculate the median value of the three TMR
PT values. If any of the TMR PT inputs are greater than or less
than the difference from the median value in percentage, a
diagnostic is generated.
MVRA_IO Parameter Groups_Pulse Rates

PR_Enable Enables pulse rate input Disable, Enable
PRScale Pulses per second scaled to engineering units. 0 to 1000 ( FLOAT)
EnhSpdAlgEnab Enhanced speed algorithm enable Disable, Enable
Used for speed wheel or any multi-tooth per revolution
speed-sensed device. This algorithm corrects for machined
tooth spacing differences. Do not use for protection or on
frequency generators.
TeethPerRev Teeth per revolution. Number of teeth or gear of vanes that 1 to 195 Teeth/Rev (INT)
pass in one revolution. This must be a integer value.
Example:
Teeth/Rev = 4
Pulse Input(E.U.) = Pulses/Sec * ( 60.0(sec/min) / TeethPerRev) *

PRScale
If PRScale = 1, then Pulse Input is in RPM
TMR_DiffLimit Diag klimit, TMR input vote Difference, in engineering units. 0 to 20000 difference (FLOAT)
The controller calculates the median value of the three pulse
rate input values. If any of the three PR inputs is greater than
or less than this difference, a diagnostic is generated and the
user is notified.

MVRA_IO Parameter Groups_Regulators

RegType Servo regulator algorithm type Unused, Position, SpeedRatio,
LiquidFuel, LiquidFuel_wPosition
RegGain Position loop gain in (% Current/Eng Unit). This adjusts the -200 to 200 (FLOAT)
regulator loop gain response. The higher this value, the faster
the servo valve responds. This rate is limited by the valve
slew rate.
RegNullBias Position loop Null Bias in %Current – Balances Servo Spring -100 to 100 (FLOAT)
Force. This force closes or opens the valve if the power is lost.
This parameter compensates to this force.
EnabCurSuic Current Suicide Enable Disable, Enable
If the Current Feedback Suicide is enabled and the following
are True, the servo performs a suicide.
a) The difference between the commanded current and the
individual current feedback exceeds the Curr_Suicide limit.
b) for a period greater than ½ second period.
EnabPosFbkSuic Position feedback suicide enable Disable, Enable
If the Position Feedback Suicide is enabled and the following
are True, the servo performs a suicide.
a) the position feedback exceeds the position limits of either:
MinPosValue - Fdbk_Suicide
MaxPosValue + Fdbk_Suicide
b) for a period of PosFailDelay in milliseconds.
EnabPressureFbkSuic Pressure feedback Suicide Enable Disable, Enable
If the Pressure Feedback Suicide is enabled and the following
is True, the servo performs a suicide.
a) the pressure feedback exceeds the pressure limits of either:
PresFbkLowLim
PresFbkHighLim
b) for a period of PressureFailDelay in ms
EnabFlowFbkSuic Flow feedback suicide enable Disable, Enable
If the flow feedback suicide is enabled and all the below is
True, the servo performs a suicide.
a) the flow feedback exceeds the flow limits of either:
FlowFbkLowLim
FlowFbkHighLim
b) for a period of FlowFailDelay in ms
Curr_Suicide Short servo output if current error exceeds this amount in 0 to 100 % (FLOAT)
percentage
Fdbk_Suicide Short servo output if position feedback error exceeds this 0 to 10 % (FLOAT)
amount in percentage
TMR_DiffLimit Diag limit, TMR input vote Difference, servo current in -15 to 150% (FLOAT)
engineering units
The controller calculates the median value of the three servo
currents values. If any of the three servo currents are greater
than or less than this difference in percent, a diagnostic is
generated. This notifies the user of a possible fault of that
servo output.

DitherAmpl Dither in % current. Amplitude of the dither moves a valve from 0 to 10 % (FLOAT)
a fixed position and back again. This dithering is to reduce
breakaway torque if the valve sits in a fixed position for an
extended time.
DitherFreq Dither rate in Hertz. Rate at which dithering moves a valve Unused, 8_33 Hz, 12_5 Hz, 16_67
from a fixed position and back again. This dithering is to Hz, 25 Hz, 50 Hz, 100 Hz
reduce breakaway torque if the valve sits in a fixed position
for an extended time.
PositionInput1 Position input 1 selection LVDT01, LVDT02, LVDT03,
Selected LVDT converted from VRMS to a position by using LVDT04, LVDT05, LVDT06,
the LVDT configuration. This selection is valid for the following LVDT07, LVDT08, LVDT09,
regulator types: LVDT11, LVDT10, LVDT13,
Position, Speed Ratio, LVDT12, LVDT15, LVDT14,
LiquidFuel_wPosition. LVDT16, Unused
the LVDT configuration. This selection is valid for the Position LVDT07, LVDT08, LVDT09,
regulator type LVDT11, LVDT10, LVDT13,
LVDT12, LVDT15, LVDT14,
LVDT16, Unused
PressureInput1 Pressure input 1 selection Unused, AnalogInput1,
Selected pressure input converted from mA to a position by AnalogInput2
the analog input configuration. This selection is valid for the
Speed Ratio regulator type
PressureInput2 Pressure Input 2 Selection Unused, AnalogInput1,
FlowInput1 Flow rate input 1 selection Unused, PulseRateTTL4,
Selected pulse input converted from a flow rate to a position PulseRateMPU7,
using the pulse rate configuration. This selection is valid for PulseRateMPU6,
following regulator types: PulseRateMPU5,
LiquidFuel PulseRateMPU4,
LiquidFuel_wPosition PulseRateMPU3,
PulseRateMPU2,
PulseRateMPU1, PulseRateTTL3,
PulseRateTTL2, PulseRateTTL1

PulseRateMPU2,
K_OuterReg Outer Regulator Gain -200 to 200 (FLOAT)
K_Conv_OuterReg Outer Regulator K_Conv -200 to 200 (FLOAT)
Tau_OuterReg Tau for Outer Regulator 0 to 10 (FLOAT)
LowLim_OuterReg Outer regulator low limit -200 to 200 (FLOAT)
Outer regulator low limit clamp
HiLim_OuterReg Outer regulator high limit -200 to 200 (FLOAT)
Outer regulator high limit clamp
PresFbkLowLim Pressure feedback low limit -150 to 5000 (FLOAT)
If pressure feedback is lower than this limit, a diagnostic is
generated. The servo is suicided, if the EnabPressureFbkSuic
is enabled
PresFbkHiLim Pressure feedback high limit -150 to 5000 (FLOAT)
If pressure feedback is higher than this limit a diagnostic is
is enabled
FlowFbkLowLim Flow feedback low limit -150 to 5000 (FLOAT)
If Flow feedback is lower than this limit, a diagnostic is
generated. The servo is suicided, if the EnabFlowFbkSuic is
enabled
FlowFbkHiLim Flow feedback high limit -150 to 5000 (FLOAT)
If flow feedback is higher than this limit, a diagnostic is
enabled
PosFailDelay Time delay (msec) before position feedback suicide is 0 to 10000 ms (FLOAT)
generated on a fault. This time delay keeps the firmware from
generating a suicide based on a transient condition.
PressFailDelay Time delay (msec) before pressure feedback suicide is 0 to 10000 ms (FLOAT)
generated on a fault This time delay keeps the firmware from
FlowFailDelay Time delay (msec) before flow feedback suicide is generated 0 to 10000 ms (FLOAT)
on a fault. This time delay keeps the firmware from generating
a suicide based on a transient condition.

Simple Regulator with Gain and Feedback Control
MVRA_IO Parameter Groups_Relays
Parameter Description Selection

Enable Enable Relay Unused, Used
This function enables the use of the PTR relays. These relays
are used in conjunction with the protection trip relays. The
application blockware controls these relays.

MVRA_IO Parameter Groups_Thermocouples

ThermCplType Select TC type or mV input. Unused, mV, T, K, J, E, S
This parameter specifies the type of thermocouple device that
is wired to the screws. The selected thermocouple device
outputs raw millivolts. This value is converted to a temperature
by using a table lookup specific to that device.
ThermCplUnit Select TC display unit in degrees C or F Deg_F, Deg_C
MVRA_IO Parameter Groups_Vibration

SensorEnab Vibration sensor enabled Disable, Enable
Vib_Gain Vibration Gain-Vpk/Vipspk 0.01 to 1000 Vpk/Vipspk (FLOAT)
Vibration Input(ipspk) = Vibration V Peak / Vib_Gain(Vipspk)
SensorRes Sensor resistance ohms 100 to 2000 ohms (FLOAT)
This resistance is used to calculate a specific minimum voltage
working range. If the sensor exceeds this limit, it is declared
faulted. Generates diagnostic and unhealthy.
MVRA Jumper Configuration

<R> 2 Rev. MVRAH#A
<S>
<T>
Jumper Default Position Position Application Notes

JP1 20 mA max 200 mA max Circuit #1 current range*
JP2 Circuit #2 current range*
MVRA On-board Analog Output Jumper Settings for JP1 and JP2

TBQA Thermocouples Input Board
The Simplex Thermocouple Input (TBQA) terminal board accepts 45-type E, J, K, S,
or T thermocouple inputs, as well as three cold junctions. These simplex inputs are
sent through ribbon cables to one of three MVRA boards. Each MVRA processes 15
thermocouples and one cold junction.
Operation
The 45 thermocouple inputs can be grounded or ungrounded. The I/O processor performs
the analog-to-digital conversion and the linearization for individual thermocouple types.
Specifications
Item Specifications
Number of channels 45 channels per terminal board
Thermocouple types E, J, K, S, T thermocouples, and mV inputs
Span -63 mV to +63 mV
Cold junction Reference junction temperature measured on the TBQA
compensation
Fault detection High/low (hardware) limit check
Monitor readings from all TCs, CJs, calibration voltages, and
calibration zero readings

QTBA Terminal Board
The QTBA, which contains simple protective circuits and jumpers, provides for phoenix
block screw connection between specific external customer field devices and the Mark V
control cabinets. The QTBA routes the raw analog input and output through ribbon cables
to the PMVE that conditions, processes, and control the signal. Each QTBA screw has a
defined input or output function. The QTBA allows connection to speed and fuel flow
divider pickup signals, servo valve outputs, water injection flow meter inputs, megawatt
transducer inputs, as well as supplying excitation current for LVDTs.
Operation
The I/O processor performs the analog-to-digital conversion and the linearization of
analog signals.
Specifications
Item Specifications
Number of inputs 6 magnetic pulse rate inputs 1 Megawatt transducer input
Number of outputs 8 servo value outputs
6 Excitation sources for LVDTs
Configuration
<R>
<S> 6 Rev. QTBAG#A
<T>

J1 20 mA 1 mA
0-1 mA on 4-20 mA input signal select
Special MW transducer input*. Refer to Appendix
C, page 3–50.

TBQB Terminal Board
The TBQB provides for a phoenix block screw connection between specific external
customer field devices and the Mark V control cabinets. The TBQB routes the raw analog
input and output through ribbon cables to the PMVE that conditions, processes, and
controls the signal. The TBQB contains no active electronics, only protective circuits.
Each TBQB screw has a defined input or output function. The TBQB allows connection
to compressor discharge pressure devices, magnetic pickups, 0-10 V inputs, and vibration
inputs.
Operation
analog signals.
Specifications
Number of Inputs Type

1 magnetic pulse rate
1 compressor discharge
4 10 V inputs
15 4 to 20 mA inputs
12 vibration inputs
Configuration
<R>
7 Rev. TBQBQ#A

Jumper Position Application Notes
BJ1 All In = Fan one input to all three All Out = one input to each Pressure Input #1 transducer
processors processor configuration*
BJ2
BJ3
BJ4
BJ5 In = mA input, 250 ohm burden Out = voltage input, no burden Pressure Transducer Input #1
resistor installed; one for each resistor Current or voltage input burden
BJ6
input to <R>,<S>, and <T> If BJ1 - BJ5 are in, BJ6 and BJ7 resistor (250 ohm) configuration
BJ7 MUST be out CPD inputs*
BJ8 <R> input, In = current Out = voltage input, no burden ±4-20 mA or ±10 V dc burden
resistor resistor (250 ohm) configuration
BJ9 <S> input, In = current
BJ10 <T> input, In = current
BJ11 <R> input, In = current Out = Voltage input, no burden ±4-20 mA or ±10 V dc burden
resistor resistor (250 ohm) configuration
BJ12 <S>, input, In = current
BJ13 <T> input, In = current
BJ14 In = current input to all three Out = Voltage input, no burden ±4-20 mA or ±10 V dc burden
processors resistor resistor (250 ohm) configuration
Refer to Appendix C,, pages 3–54
BJ15 In = current input to all three Out = Voltage input, no burden ±4-20 mA or ±10 V dc burden
processors resistor resistor (250 ohm) configuration
Refer to Appendix C,, pages 3–56

TBQC Terminal Board
The TBQC provides for input and output phoenix block screw connections between
specific external customer field devices and the Mark V control panels. The TBQC routes
the raw analog input and output through ribbon cables to the PMVE that conditions,
processes, and controls the signal. The TBQC board has no active electronics, only
protective circuits and jumpers. Each TBQC screw has a defined input or output function.
The TBQC allows connection to 4-20 mA inputs, LVDTs, and 4-20 mA outputs.
Operation
The I/O processor performs analog-to-digital conversion and the linearization of analog
signals.
Specifications
Item Specifications
Number of inputs 16 LVDT inputs
16- 4 to 20 mA inputs
Number of outputs 2 analog outputs
TBQC On-board Analog Input Jumper Settings
BJ01 through BJ015 negative to DCOM (jumpered)
BJ16 Analog Output jumper
BJ17 Analog Output (1, 2) 20 mA or jumper 2 and 3 (200 mA)

TBQF Terminal Board
The TBQF terminal board is The TBQF provides for a phoenix block screw connection between specific external
optional for large and medium customer field devices and the Mark V control cabinets. The TBQF routes the raw analog
steam applications. input and output through ribbon cables to the PMVE to condition, process, and control the
signal. The TBQF board has no active electronics, only protective circuits and jumpers.
Each screw has a defined input or output function. The TBQF allows connection to 4-20
mA inputs, LVDTs, and 4-20 mA outputs.
Operation
analog signals.
Specifications
Item Specifications
Number of inputs 16 LVDT inputs
16- 4 to 20 mA inputs
Number of outputs 2 analog outputs
TBQF On-Board Analog Input Jumper Settings
BJ01 through BJ015 Negative to DCOM (jumpered)

TCQC Terminal Board
TCQC Jumper Configuration

<R> 4 Rev. TCQCG#B
<S>
<T>

BJ1 Regulator #1 These jumpers are used to select the output
BJ2 current range, 10 mA to 240 mA
BJ25
BJ26
BJ27
BJ3 Refer to Regulators 2- 4 table below. Regulator #2
BJ4
BJ28
BJ29
BJ30
BJ5 Regulator #3
BJ6
BJ31
BJ32
BJ33
BJ7 Regulator #4
BJ8
BJ34
BJ35
BJ36
BJ9 Refer to Regulators 5- 8 table below. Regulator #5 These hardware jumpers are used to select
BJ10 the output current range, 10 mA to 40 mA
BJ11 Regulator #6
BJ12
BJ13 Regulator #7
BJ14
BJ15 Regulator #8
BJ16
Connect
BJ17 DCOM not Not used in Mark VIe control Mark V migration.
connected Place jumper in default position
BJ18 In = No additional Out = Current Out for intrinsically safe installations; further limits P15 and N15
limit supply supply to
BJ20 Current limit voltage Proximity transducers (LM installations)
BJ21 1-2 = Enabled 2-3 = Disabled Not used in Mark VIe control Mark V migration.
Place jumper in default position
BJ22 Enabled Disabled Oscillator enable
Enable = normal operation

BJ23 Out = termination In = termination Not used in Mark VIe control Mark V migration.
resistor out resistor in Place jumper in default position
BJ24
JP38 1-2 = 0.195Vp 2-3 = 0.3868 Vp FF2 Mag pickup hysteresis level
JP39 1-2 = 0.195Vp 2-3 = 0.3868 Vp FF1 Mag pickup hysteresis level
Regulators 2 - 4
BJ1,3,5,7 BJ2,4,6,8 BJ25,28,31,34 BJ26,29,32,35 BJ27,30,33,36

Nominal Servo
Output Coil 10 10X 20 40 80 DEF Y Z DEF A DEF B DEF C
(mA) (Ohms)
10 1000 X X X X X
(Gas
Simplex)
10 1000 X X X X X
(Other)
20 125 X X X X X
40 62.5 X X X X X
80 22 X X X X X
120 40 X X X X X
240 37.5 X X X X X
Regulators 5 - 8
BJ9,11,13,15 BJ10,12,14,16
Nominal Servo Coil
Output (Ohms) 10 10X 20 40 10 20 40
(mA)
10 1000 X X
(Gas
Simplex)
10 (Other) 1000 X X
20 125 X X
40 62.5 X X

TCQC Interfacing Board Servo Output Jumpers

MVRA Specific Alarms
5400–5400,
8400–8400
Note This alarm has been depreciated and is only shown for legacy compatibility.
Description Unallowed VarlOCompatode Change: Old — [ ] New — [ ]
Possible Cause The configuration file located in flash storage does not match the
firmware
Solution
• Compress the variable and rebuild the I/O pack.

• Download both the firmware and the application code.
5416-5416,
8416-8416
Description Cold Junction Unhealthy, Using Backup
Possible Cause The local cold junction signal from the terminal board is out of
range. The normal range is -30 to 65°C (-22 to 145 °F).
Solution If hardware is in the normal temperature range, there is a possible hardware

failure of the cold junction sensor on the terminal board. Replace the terminal board.
5470-5470,
8470-8470
Description More than One Servo Requested for Calibration
Possible Cause
• More than one ToolboxST interface is trying to calibrate the regulator.

• Only one servo can be calibrated at a given time, but multiple calibration requests
are being made.
Solution Check variables in the Variables Tab to confirm that only one CalibEnab#
for only one servo is set to True at a given time.

5471-5471,
8471-8471
Description Calibration: Selected LVDT Max / Min Pos Limit Out of Range
Possible Cause Used to ensure that all selected LVDTs are scaled to the same units.
• MaxPosValue or MinPosValue for selected LVDT configured in the regulator

configuration is out of range (for example, ±50%) encountered during calibration.
Solution
• Check the regulator configuration for parameter PositionInput#1 for the particular
servo.
• Check the MaxPosValue and MinPosValue for LVDT# selected input in
PositionInput#1.
• The MaxPosValue for LVDT input should be between 50% to 150%.
• The MinPosValue for LVDT input should be between -50% to 50%.
5401-5415,
8401-8415
Description Thermocouple [ ] unhealthy ([ ])
Possible Cause
• Thermocouple mV input on terminal board exceeded the thermocouple range or

hardware limit. Refer to help documentation for specified thermocouple ranges.
• Thermocouple configured as wrong type.
• Board detected a thermocouple open, applied bias to circuit, driving it to a large
negative number, or TC not connected, or a condition such as stray voltage or noise
caused input to exceed -63 mV.
• Stray voltage or noise caused input to exceed -63 mV.
Solution
• Check field wiring, including shields. Problem is usually not a MVRA or terminal
board failure if other thermocouples are working correctly.
• Check thermocouple for open circuit.
• Measure incoming mV signal to verify that it does not exceed -63 mV.
• Verify that the thermocouple type matches the configuration.

5417-5420,
8417-8420
Description Analog ±10 V Input [ ] unhealthy ([ ] V)
Possible Cause
• Excitation to transducer wrong or missing

• Faulty transducer
• Analog input voltage input beyond specified range
• Open or short-circuit on input
Solution
• Check field wiring and connections to indicated analog input channel.

• Check field device for failure.
• Check ground select jumper for input.
• Verify that inputs are in operable range (-10 V to 10 V).
5421-5435,
8421-8435
Description Analog 4-20 mA Input [ ] unhealthy ([ ] mA)
Possible Cause

• Analog input current input beyond specified range
Solution
• Check field wiring and connections to the indicated analog input channel.
• Check the field device for failure.
• Check the ground select jumper for input.
• Verify that the inputs are in operable range ( 3.0-21.5 mA).
• Verify the parameter settings for Min_MA_Input and Max_MA_Input.

5436-5447,
8436-8447
Description Vibration Input for Seismic (Velocity) Sensor [ ] unhealthy ([ ])
Possible Cause
• Open circuit
• Incorrect configuration for sensor resistance (ohms)
Solution
• Check field wiring, including shields.

• Verify that the sensor resistance matches the configured sensor resistance.
• Replace the sensor.
5448-5465,
8448-8465
Description LVDT [ ] Position Out of Limit ([ ] Vrms)
Possible Cause
• Excitation voltage to LVDT incorrect

• Open or short-circuit on LVDT
• LVDT input out of range.
• LVDT not calibrated
Solution
• Check field wiring, including shields and LVDT excitation. Problem is usually not a
MVRA or terminal board failure if other LVDT inputs are working correctly.
• Check the LVDT sensor.
• Calibrate the servo regulator with the proper LVDT.
• Verify the configuration limits, MinVrms and MaxVrms.
• Verify that the LVDT excitation terminal board connections match the configured
excitation source specified in ExcitSelect.
• Verify that PosMargin is set to the proper value.

5466-5469,
8466-8469
Description Monitor [ ] Invalid Servo Configuration
Possible Cause Invalid configuration for selected servo and regulator type
Solution
• Verify that the monitor regulator type matches the regulator type of the selected servo.
• Rebuild and download configuration.
5472-5482,
8472-8482
Description PulseRate [ ] Input unhealthy
Possible Cause
• Pulse rate input exceeds maximum limit

• Broken wire on flow rate input
• Faulty sensor
Solution
board failure if other flow rate inputs are working correctly.
• For magnetic pickup sensor, check gap.
• For TTL sensor, check power to sensor and gap.
• Replace the hardware.
5485-5492,
8485-8492
Description Servo [ ] Disabled, Configuration error Fault No:[ ]
Possible Cause
• Servo position input connected to unused LVDT

• Incorrect position input configuration
• Servo flow input connected to unused PR
• Incorrect flow input configuration
• Servo pressure input connected to unused analog Input
• Incorrect pressure input configuration
Solution
• Check and correct the configuration parameters relating to the list of possible causes.
• Check that regulator inputs are connected to used sensor inputs in configuration.

5493-5500,
8493-8500
Description Servo [ ] Output Suicide Active
Possible Cause

• Servo pressure input connected to unused analog Input
• Regulator feedback out of range
• Servo current feedback differs from servo current command
Solution
• Verify that inputs are connected to used sensor inputs in the configuration.
• LVDT feedback issue: Check position sensor connections.
• Check position sensor mechanical integrity to the valve.
• Check for wiring of servo output loop for open or short circuit.
• Check for short or open servo coil.
5501-5508,
8501-8508
Description Servo [ ] Position Feedback out of range ([ ] %)
Possible Cause LVDT position feedback outside specified range
Solution
• Check the LVDT configuration settings.

• Calibrate the affected regulator.
• Check the field wiring.
• Check for a shorted/open position sensor coil.
• Check the position sensor mechanical integrity.

5509-5516,
8509-8516
Description Servo [ ] Pressure Feedback out of range ([ ])
Possible Cause Pressure feedback used in servo regulator outside specified range
Solution Check the source of the pressure signal including the sensor, field wiring,
and configuration.
5517-5524,
8517-8524
Description Servo [ ] Flow Feedback out of range ([ ])
Possible Cause Flow feedback used in a servo regulator outside specified range
Solution
• If active pulse rate flow sensor, check power to device, field wiring, sensor, and
configuration.
• If magnetic pulse rate flow sensor, check device, field wiring, and input configuration.
• Check the gap between the sensor and the flow wheel.
5525-5531,
8525-8531
Description Pack internal reference voltage [ ] out of limits ([ ])
Possible Cause Calibration reference voltage more than ±5% from expected value,
indicating hardware failure
Solution
• Check the power supply voltages.

• Replace the acquisition card.
5532-5538,
8532-8538
Description Pack internal null voltage[ ] out of limits ([ ])
Possible Cause Null voltage more than ±5% from expected value, indicating
hardware failure
Solution


5534-5539,
8534-8539
Description Output [ ] DAC Cmd Volts Disagrees with DAC feedback
Possible Cause Output command voltage disagrees with DAC Feedback
Solution Replace the acquisition card.
5539-5540,
8539-8540
Description Output [ ] Individual current feedback unhealthy ([ ] mA)
Possible Cause
• Commanded output beyond range of output

• Field wiring problem
• Field device problem
• Open loop or too much resistance in loop
• Acquisition card failure
• Terminal board failure
Solution
• Verify that the commanded output is within the range of the output.
• Confirm correct power supply voltage.
• Check field wiring and device. Problem is usually not a MVRA or terminal board
failure if other analog outputs are working correctly.
• Replace acquisition card.
5541-5542,
8541-8542
Description Output [ ] Total current feedback unhealthy ([ ] mA)
Possible Cause
• Commanded output beyond the range of output

Solution
• Confirm correct power supply voltage.
• Check field wiring and device.

5543-5544,
8543-8544
Description Output [ ] 20/200 mA suicide active
Possible Cause

• Connected device problems interfering with current
• Software suicide requested
• Hardware failure
Solution
• Verify that sensor feedback is within limits.

• Verify that the software suicide request is not activated.
5545-5546,
8545-8546
Possible Cause Review any additional diagnostics for possible causes.
• TMR_SuicLimit set too low

• Command is beyond output range
Solution
• Check the field wiring and status of connected device.

• Verify that the value of TMR_SuicLimit is set correctly.
• Verify the field wiring connections.
• Verify that the commanded output is within output range.

5547-5548,
8547-8548
Description Output [ ] Suicide relay non-functional
Possible Cause The analog output suicide relay command does not match feedback.
• Relay failure on acquisition card

Solution If hardware failure, replace the acquisition card.
5549-5550,
8549-8550
Possible Cause The analog output suicide relay command does not match the
feedback.
• Relay failure on the acquisition card

MVRA, MVRB, MVRF: 32

Description Logic Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]
Possible Cause N/A
Solution N/A

MVRA: 5800-5831, 8800-8831
5851-5862, 8851-8862
5887-5910, 8887-8910
5923, 5932, 8923, 8932
MVRB: 5802-5807, 8802-8807
MVRF: 5800-5828, 8800-8828
5851-5862, 8851-8862
Description Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]
Possible Cause Voter disagreement detected between R,S and T I/O packs
Solution Adjust the specified parameter below for the each input type:
• If input variable is MegaWattVco or CpdVco, adjust the TMR_DiffLimit.

• If input variable is AnalogInput[ ], adjust the TMR_DiffLimit.
• If input variable is PulseInput[ ], adjust the TMR_DiffLimit.
• If input variable is ServoOutput[ ], adjust the TMR_DiffLimit on the Regulators tab.
• If input signal is LVDT[ ], adjust the LVDT_TMR_DiffLim on the Parameters tab.
• If application is Mark Ve, check connectivity of 19PL cable.
5553, 8553
Description Output [ ] 200 mA Jumper Setting Invalid, Overcurrent Detected
Possible Cause
• Excessive current detected on analog output and output has been suicided. Excessive
current is probably due to an incorrect setting of the 200 mA jumpers.
• Internal hardware failure
Solution
• Verify that the 200 mA jumpers are set correctly.


MVRB I/O Interface Board
The MVRB is an I/O board on the PMVE using the high-speed serial link (HSSL). The
PMVE contains specialized code for the MVRB that communicates and controls the
MVRB analog and digital I/O. Configuration parameters customize MVRB operation.
The MVRB is a functional replacement for the Mark V TCQB board.
MVRB analog and digital I/O is as follows:
• LM Prox Vibration Inputs

• Prox Vibration Inputs
• Prox Position Key Phasor
• LVDT/LVDR
• 4-20ma or 200ma Output
Additional Functionality:
• Vibration protection algorithms

• 1/2x, 1x and 2x shaft displacement and phase

Installation
Ø To install the MVRB
5. Remove the new MVRB from its static bag and reverse this procedure.
6. Once the MVRB is in place, connect the HSSL link cable from the PMVE.
Operation
Control software can be The PMVE contains configuration parameters specific to the MVRB. External data is
modified online without being transferred to and from the control system database in the controller over the IONets. The
restarted. PMVE propagates the control and data to each of its I/O boards.
Data is transferred to the MVRB across the HSSL every five milliseconds. All analog
and digital I/O signals are read and written at the 5 ms rate by the PMVE. The MVRB
functions much like the TCQB, and includes the 1/2x, 1x and 2x shaft displacement and
phase monitoring.
Protection capability in the application blockware allows the blockware to monitor the
wobble of the shaft relative to a keyphasor and also shaft vibration and balance of the shaft
relative to a keyphasor. The 1/2x is typically used to detect bearing oil leaks or any ½
rotational frequency event. The 1x is used for shaft balancing, or detecting any rotational
frequency event. The magnitude is the force of the unbalance, and the phase is where the
imbalance relative to the keyphasor occurs.
The 2x was proposed for 9H machines to detect blade cracking. This is only used at a
steady state speed. If the blockware detected an x% degree phase shift at this steady speed,
an alarm was annunciated. The 2x magnitude should be used as a qualifier. Since this
feature was not verified, a change in the load may cause this shift.
The function is accomplished by the follow method:

When the keyphasor sees a notch or the post (0 degrees), the FPGA collects 256 data
samples from the selected proximeter at the sample rate of 16x the shaft speed.
This data is then transferred back to the PMVE processor and processed through a Fast
Fourier Transform (FFT). Since the data was collected by the FPGA at 16x shaft rate, the
FFT contains bin centered 1/2x, 1x and 2x magnitude and phase information.
This information can now be attached to protection blocks in application code.
No single event should trip the turbine, and should be qualified and filtered in application
code as appropriate and necessary.
JP1 — JP2:
JP3 — JP4:

JP5 — JP6:
MVRB On-Board Analog Output Jumper Settings
JP8 — JP9:

JP10 — JP11:
Specifications
The MVRB has the same hardware functionality as the TCQB. Original TCQB ribbon
cables plug directly into the MVRB to simplify replacement.
Transducer Designator Quantity Function Terminal Board

Input
Prox 1-18 PR1 - PR18 18 Displacement (qty=15 when PX1 - PX3 are TBQD
PX1- PX3 3 accel input) TBQD
18 PR1 - PR3 can be jumpered for TBQD
18 accelerometer input TBQD
Vibration ac (qty=15 when PX1 - PX3 are
accel input)
Vibration peak (qty=15 when PX1 - PX3
are accel input)
Prox 19-30 PR19 - PR30 12 Displacement TBQD
3 Prox 29 and 30 inputs can be used for key TBQD
phasor input
LVDT 17-22 LV17 - LV22 6 Displacement TBQD
Signal Output Designator Quantity Function Terminal Board

Curr Out 3-4 CUR3OUT - 2 4mA - 20ma or 4mA - 200mA output, TBQD
CUR4OUT jumper configurable

Environment
Temperature 0 - 60 ºC
Humidity 5% - 95% non-condensing
Shock and Vibration 1.0 G horizontal, 0.5 G vertical at 15 to 120 Hz
Physical Characteristics
Size 11.00 inch x 8.40 inch (same size and mounting holes as TCQB)
Technology SMT and through-hole, multi-layer
Agency UL, CSA, and CE
Requirements
Diagnostics
The MVRB board has its own ID device, which is interrogated by the PMVE. The board

Configuration
MVRB Board Parameters

TBQxRevAATermBoard TBQx is a Revision AA terminal board. No, Yes
The TBQx revisions >AA have a resistor in the feedback
circuit. This generates a gain error that must be corrected.
AVSelection TMR internal selection variables. Unused, AOut1IndivCurFdbk,
brought out to signal space. This is used for initial check out SoftwareSpare
and diagnostic issues.
LVDT_TMR_DiffLim LVDT TMR input vote difference in % of range 0 to 200 % (FLOAT)
The RST controllers calculate the median value of the three
TMR LVDT values. If any of the TMR LVDTs are greater
than or less than this difference from the median value in
percentage, a diagnostic is generated.
MVRB I/O Parameter Groups
MVRB I/O Parameter Groups – Analog Outputs

Output_MA Output mA selection Unused, 0-20 mA, 0-200 mA
Suicide_Enab Enable suicide for faulty output current if in a TMR current Disable, Enable
sharing configuration
Low_MA Output mA at low value Disable, Enable 0 to 200 mA
(FLOAT)
milliAmp Output = Low_MA + (High_MA - Low_MA) *
TMR_SuicLimt Suicide threshold, for TMR operation. Load sharing margin in 0 to 200 mA (FLOAT)
mA. If any of the three individual analog outputs exceeds 50%
of the mA output plus this margin, the mA output is allowed
to suicide.
D/A_ErrLimit Suicide threshold, for TMR operation. Defective D/A reference 0 to 200 % (FLOAT)
versus commanded output feedback in percentage. If the
hardware command output and the commanded D/A difference
exceeds this limit for more than 3 frames, the mA output
performs a suicide.

MVRB I/O Parameter Groups – Analog Outputs
OutputState State of the analog output when offline. Sets the mA output to PwrDownMode, HoldLastVal,
a known milliamp value when the MVRA is offline. Output_Value
PwrDownMode sets analog output to 0.0 in engineering units.
engineering units received before the MVRA went offline.
Output_Value allows the end user to specified the offline value
in engineering units.
engineering unit value to set the analog output to when the
MVRA goes offline.
MVRB I/O Parameter Groups – LVDT Inputs

MinVrms LVDT V RMS at Min End Stop (Normally set by auto-calibrate) 0 to 7.1 V (FLOAT)
The absolute V in volts rms read by the LVDT when the valve
is at the minimum end position.
MaxVrms LVDT V RMS at Max End Stop (Normally set by auto-calibrate) 0 to 7.1 V (FLOAT)
is at the maximum end position.
MinPosValue Position at Min End Stop in engineering units -15 to 150 % or EU (FLOAT)
The position in percentage to be returned by the LVDT when
the valve is at the minimum end position.
MaxPosValue Position at Max End Stop in engineering units -15 to 150 % or EU (FLOAT)
The position in percentage to be returned by the LVDT when
the valve is at the maximum end position.
MVRB I/O Parameter Groups – Accelerometers

Gain Accelerometer gain in V peak / inches per second peak 0.0 to 1000.0 Vpk/Vipspk (FLOAT)
Offset Accelerometer offset in inches per second 0.0 to 100.0 ips (FLOAT)
Accelerometer (ips) = Accelerometer in V peak / Gain (Vpk/ipspk) + Offset (ips)
MVRB I/O Parameter Groups – Vibration Sensors 1 through 3

InputType Vibration Input Type Unused, Proximeter,
The first three proximeter inputs can be used for accelerometers Accelerometer
or proximeters.
1x2xSelection Keyphasor selector Unused, Keyphasor1, Keyphasor2
Assign a keyphasor to this proximeter to calculate a phase and
magnitude of the 1x and 2x shaft Vibration.
VibGain Vibration gain in V peak / mil 0.0 to 1000.0 Vpk/mil (FLOAT)
Vibration (mils) = Vibration in V peak / Gain (Vpk/mil)

V dc LowLimit V dc low health limit -2.5 to 18.0 V (FLOAT)
If the vibration axial voltage is less than this low limit, the
sensor is unhealthy.
V dc HighLimit V dc high health limit -2.5 to 18.0 V (FLOAT)
If the vibration axial voltage is greater than this high limit, the

InputType Vibration input type Unused, Proximeter
1x2xSelection Keyphasor selector Unused, Keyphasor1, Keyphasor2
Assign a keyphasor to this vibration proximeter to calculate a
phase and magnitude of the 1x and 2x shaft vibration.
VibGain Vibration gain in V peaks / mil 0.0 to 1000.0 Vpk/mil (FLOAT)
Vibration (mils) = Vibration in Volts peak / Gain (Vpk/mil)
V dc LowLimit V dc low health limit -2.5 to 18.0 V dc (FLOAT)
If the proximeters voltage is less than this low limit, the sensor
is unhealthy.
V dc HighLimit V dc high health limit -2.5 to 18.0 V dc (FLOAT)
If the proximeters voltage is greater than this high limit, the
MVRB I/O Parameter Groups – Proximeter Sensors 19 through 28

SensorEnab Proximeter enabled Disable, Enabled
ProxGain Proximeter gain in V / mil 0.0 to 1000.0 V/mil (FLOAT)
ProxOffset Proximeter offset in mil -2048.0 to 2048.0 mils (FLOAT)
Proximeter Axial (mils) = Proximeter Volts / ProxGain (V / mil) + ProxOffset(mils)
If the proximeters voltage is less than this low limit, the sensor
is unhealthy.
MVRB I/O Parameter Groups – Keyphasor Proximeter Sensors

SensorEnab Proximeter enabled Disable, Enabled
ProxGain Proximeter gain in V / mil 0.0 to 1000.0 V/mil (FLOAT)
ProxOffset Proximeter offset in mils -2048.0 to 2048.0 mils (FLOAT)
Proximeter Axial (mils) = Proximeter V / ProxGain (Volts / mil) + ProxOffset(mils)

MVRB I/O Parameter Groups – Keyphasor Proximeter Sensors
If the proximeters voltage is less than this low limit, the
keyphasor sensor is unhealthy.
keyphasor sensor is unhealthy.
MVRB I/O Internal Variables Groups
MVRB I/O Input Variable Groups – Analog Output Feedback

AOut1SuicFdbk Analog output 1 suicide relay feedback Suicided = True (BOOLEAN)
The suicide state of the analog output
AOut2SuicFdbk Analog output 2 suicide relay feedback Suicided = True (BOOLEAN)
The suicide state of the analog output
AnalogOutFdbk1 Analog output 1 feedback in engineering units % or E.U. (FLOAT)
This feedback should match analog output commanded value
in percentage.
AnalogOutFdbk2 Analog output 2 feedback in engineering units % or E.U. (FLOAT)
This feedback should match analog output commanded value
in percentage.
MVRB I/O Output Variable Groups – Analog Output Control

Suicide01_R/S/T Analog output 1 suicide control (non-latched) (BOOLEAN)
The suicide in the R/S/T analog output
Suicide02_R/S/T Analog output 2 suicide control (non-latched) (BOOLEAN)
The suicide in the R/S/T analog output
MVRB I/O Input Variable Groups – Accelerometer Feedbacks

AccelMagxHP LM accelerometer magnitude (ips) at HP Shaft Freq Ips (FLOAT)
This accelerometer output is frequency locked to the HP shaft
frequency. Feedback value is the HP magnitude (ips) of the
result.
AccelMagxIP LM accelerometer magnitude (ips) at IP Shaft Freq Ips (FLOAT)
This accelerometer output is frequency locked to the IP shaft
frequency. Feedback value is the IP magnitude (ips) of the
result.
AccelMagxLP LM accelerometer magnitude (ips) at LP Shaft Freq Ips (FLOAT)
. This accelerometer output is frequency locked to the LP shaft
frequency. Feedback value of the LP magnitude (ips) of the
result.

MVRB I/O Output Variable Groups – Accelerometer Shaft Frequency in RPM

HPShaftFreq HP shaft frequency in RPM (populated by the application) RPM (FLOAT)
The accelerometer output is frequency locked to the HP shaft
frequency and a magnitude is calculated.
IPShaftFreq IP shaft frequency in RPM (populated by the application) RPM (FLOAT)
The accelerometer output is frequency locked to the IP shaft
LPShaftFreq LP shaft frequency in RPM (populated by the application) RPM (FLOAT)
The accelerometer output is frequency locked to the LP shaft
MVRB I/O Input Variable Groups – Vibration 1x 2x Feedbacks

VibxxMagHalfx Vibration Prox Magnitude at 1/2x (mils) mils (FLOAT)
The vibration proximeter output is frequency locked to the shaft
through the keyphasor. 1/2x Feedback calculated is magnitude
in mils.
VibxxMag1x Vibration Prox Magnitude at 1x (mils) mils (FLOAT)
The vibration proximeter output is frequency locked to the
shaft through the keyphasor. 1x Feedback calculated is the
magnitude in mil and phase.
VibxxPhase1x Vibration prox phase at 1x (degrees) mils (FLOAT)
Phase in degrees relative to the keyphasor
VibxxMag2x Vibration prox magnitude at 2x (mils) The vibration proximeter mils (FLOAT)
output is frequency locked to the shaft through the keyphasor.
2x Feedback calculated is the magnitude in mil and phase.
VibxxPhase2x Vibration prox phase at 2x (degrees) mils (FLOAT)
Phase in degrees relative to the keyphasor
MVRB I/O Input Variable Groups – V dc Proximeters 1 through 18 Feedback

Prox V dc xx Proximeter V dc V (FLOAT)
This variable returns the dc offset of the vibration proximeter.
This is normally used for a sensor health, but could be used
when appropriately scaled in blockware as a course axial
position.

MVRB Jumper Configuration
<R>
<S>
Rev. MVRBH#A
<T>
Jumper Default Position Application Notes

JP8 S = Simplex R = Redundant 20\200 mA output circuit #1 Mode
select*
JP9 20 mA Max 200 mA Max 20\200 mA circuit #1 current range*
JP10 S = Simplex R = Redundant 20\200 mA output circuit #2 Mode
select*
JP11 20 mA Max 200 mA Max 20\200 mA circuit #2 current range*
JP1 Default Proximity Transducer Accelerometer is Accelerometer or proximity
commonly used as a transducer select
JP2 vibration input on LM Hardware jumpers 1-6 should all be
Machines (Aircraft engine set to same.
JP3
derivative)
JP4
JP5
JP6

TBQD Terminal Board
The TBQD provides for phoenix block screw connection between specific external
customer field devices and the Mark V control cabinets. It routes the raw analog input
and output through ribbon cables to the PMVE to condition, process, and control the
signal. The TBQD board has no active electronics, just passive conditioning circuits and
jumpers. Each screw has a defined input or output function. The TBQD allows connection
to customer transducers and I/O.
Operation
analog signals.
Specifications
Item Specifications
Number of inputs Up to 30 proximeter inputs
3 accelerometer inputs
2 key phasor inputs
6 LVTD inputs.
Number of outputs 2 - 4 to 20 mA or 4 to 200 mA outputs
TBQD Analog Output Jumper

Settings
Configuration

<R> for Simplex 7 Rev. TBQDQ#A
optional
<S> for TMR

BJ1 20 mA Max 200 mA Max 20 / 200 mA Actuator Output Current Range
BJ2

MVRB Specific Alarms
5401-5430,
8401-8430
Description Vibration Input Sensor [ ] unhealthy ([ ])
Possible Cause
• Incorrect configuration for sensor type

• Open circuit
Solution
• Verify that the sensor configuration matches the connected sensor type.
• Check field wiring, including shields.
• Replace the sensor.
5450-5465,
8450-8465
Possible Cause
• Excitation voltage to LVDT is incorrect

• LVDT input out of range
Solution
• Check field wiring, including shields and LVDT excitation. Problem is usually not a
MVRB or terminal board failure if other LVDT inputs are working correctly.

5525-5531,
8525-8531
Possible Cause Calibration reference voltage is more than ±5% from the expected
value.
• Power supply issue

Solution

5532-5538,
8532-8538
Possible Cause Null voltage is more than ±5% from the expected value.

Solution


5539-5540,
8539-8540
Possible Cause
• Commanded output beyond range of output.

Solution
• Confirm the correct power supply voltage.
• Check the field wiring and device. Problem is usually not a MVRB or terminal board
5541-5542,
8541-8542
Possible Cause

Solution
• Check the field wiring and device.

5543-5544,
8543-8544
Possible Cause

Solution
• Verify that sensor feedback is within limits.

5545-5546,
8545-8546

• Command beyond range of output
Solution
• Check the field wiring and status of connected device.

5547-5548,
8547-8548
Possible Cause The analog output suicide relay command does not match feedback.


5549-5550,
8549-8550
Possible Cause Analog output suicide relay command does not match the feedback.
• Relay failure on the acquisition card

5551-5556,
8551-8556
Description Output [ ] DAC Cmd Volts Disagrees with DAC feedback by 5%
Possible Cause Output command voltage disagrees with DAC feedback
32
Possible Cause N/A
Solution N/A
5802-5807, 8802-8807


5553, 8553
Description Output [ ] 200 mA Jumper Setting Invalid, Overcurrent Detected
Possible Cause
• Excessive current detected on analog output; output suicided. Excessive current

probably due to an incorrect setting of the 200 mA jumpers.
Solution
• Verify that the 200 mA jumpers are set correctly.


MVRC I/O Interface Board
The MVRC is an I/O board on the PMVE using the high-speed serial link (HSSL). The
PMVE contains specialized code for the MVRC that communicates and controls the
MVRC analog and digital I/O signals. Configuration parameters customize MVRC
operation.
The MVRC is a functional replacement for the Mark V TCCA and TCCB boards.
MVRC analog and digital I/O is as follows:
• Thermocouples
• RTD inputs
• Analog inputs
• Analog outputs
Installation
Ø To install the MVRC

4. Remove the old board and place in a static bag.
5. Remove the new MVRC from the static bag and reverse this procedure.
6. Once the MVRC is in place, connect the HSSL link cable from the PMVE.
Operation
Application software can be The PMVE contains configuration parameters specific to the MVRC. External data is
modified online without being transferred to and from the control system database in the controller over the IONets. The
restarted. PMVE propagates the control and data to each of its I/O boards. Data is transferred to the
MVRC across the HSSL every five milliseconds.
Specifications
The MVRC has the same hardware functionality as the TCCA and TCCB I/O boards.
Original TCCA and TCCB ribbon cables plug directly into the MVRC to simplify
replacement.

42 Thermocouples TBQA
36 Analog inputs CTBA / TBCB
16 Analog outputs CTBA
44 RTD inputs TBCA / TBCB
All analog and digital I/O signals are read and written at the 5ms rate by the PMVE.
Diagnostics
The MVRC has its own ID device, which is interrogated by the PMVE. The MVRC board

Configuration
MVRC Board Parameters

SystemFreq System frequency (Hz) 60 Hz, 50 Hz
Used in determining the PLL operational frequency for Bus
and Gen Lock.
Min_MA_Input Minimum mA for healthy 4/20 mA input. The MVRA generates 0 to 22.5 mA (FLOAT)
a unhealthy status for any of the 4-20 mA inputs that are less
than this value.
Max_MA_Input Maximum mA for healthy 4/20 mA input. The MVRA generates 0 to 22.5 mA (FLOAT)
a unhealthy status for any of the 4-20 mA inputs that are
greater than this value.
Min_MA_Input Minimum mA for healthy 0/1 mA input. The MVRA generates a -0.5 to 1.5 mA (FLOAT)
unhealthy status for any of the 1 mA inputs that are less than
this value.
Max_MA_Input Maximum mA for healthy 0/1 mA input. The MVRA generates -0.5 to 1.5 mA (FLOAT)
a unhealthy status for any of the 1 mA inputs that are greater
than this value.
BusVoltage Bus kV at 115 Vrms PT out 0 to 1000 KV or % (FLOAT)
Use to scale Bus PT 115 V RMS sensor input to Bus kV
GenVoltage Generator kV at 115 Vrms PT out 0 to 1000 KV or % (FLOAT)
Used to scale generators 115 volts RMS sensor input to
generator kV
GenCurrent Generator current (Amps) at 5 Amps CT out. 0 to 50000 (FLOAT)
Used to scale Generators 5 Amp CT sensor input to generator
current.
PhaseShift Voltage phase shift (deg) -60 to 60 deg (FLOAT)
MVRC I/O Parameter Groups
MVRC_IO Parameter Groups_Analog Inputs

InputType Type of Analog Input Unused, 4-20 mA
Low_Input Input mA (or V) at low value -10 to 20 mA (FLOAT)
Low_Value Input Value in engineering units at Low mA (or V) E.U. (FLOAT)
High_Input Input mA (or V) at high value -10 to 20 mA (FLOAT)
High_Value Input value in engineering units at High mA (or V) E.U. (FLOAT)
Analog Input( E.U.) = Low_Value + (High_Value - Low_Value) *
DiagHighEnab Enable high input limit diagnostic. If the 4-20 mA analog input Disable, Enable
exceeds the parameter Max_MA_Input and DiagHighEnab is
DiagLowEnab Enable Low Input Limit Diagnostic. If the 4-20 mA analog input Disable, Enable
exceeds the parameter Min_MA_Input and DiagLowEnab is

MVRC_IO Parameter Groups_Analog Outputs
Output_MA Output mA selection Unused, 0-20 mA
OutputState State of the analog output when off-line. Sets the mA output to PwrDownMode, HoldLastVal,
a known mA value when the MVRC is offline. Output_Value
PwrDownMode set analog output to 0.0 in engineering units.
engineering units received before the MVRC went offline.
Output_Value allows the user to specified the offline value in
engineering units.
engineering unit value to set the analog output to, when the
MVRC goes offline.
MVRC_IO Parameter Groups_Cold Junctions

ColdJuncType Select CJ type. This selection allows application software Remote, Local
substitute the current terminal board’s cold junction value in
degrees with another value from application space in degrees.
ColdJuncUnit Select TC display unit in degrees C or F Deg_F, Deg_C
MVRC_IO Parameter Groups_RTD

RTDType Select RTD type or ohms input N120, PT200, PT100_SAMA,
This parameter specifies the type of RTD device that is wired to PT100_USIND, Ohms, CU10,
the screws. The selected RTD device outputs raw V base upon PT100_PURE, Unused,
the current injected. This value is converted to a temperature Ohms_10, PT100_DIN
RTDUnit Select RTD unit degrees C or F Deg_F, Deg_C

MVRC_IO Parameter Groups_Shunt C
ShuntOhms Shunt ohms 0 to 100 ohms (FLOAT)
ShuntLimit Shunt max test ohms 0 to 100 ohms (FLOAT)
BrushLimit Shaft (Brush) max ohms 0 to 100 ohms (FLOAT)
SysLim1Enabl Enable system limit 1 fault check Disable, Enable
SysLim1Latch Latch system limit 1 fault NotLatch, Latch
SysLim1Type System limit 1 check type ( >= or <= ) <=, >=
SysLimit1 Current amps 0 to 100 (FLOAT)
SysLim2Enabl Enable system limit 2 fault check Disable, Enable
SysLim2Latch Latch system limit 2 fault NotLatch, Latch
SysLim2Type System limit 2 check type ( >= or <= ) <=, >=
SysLimit2 Current amps 0 to 100 amps (FLOAT)
TMR_DiffLimt Diag limit, TMR input vote difference, in engineering units 0 to 100 E.U. (FLOAT)
MVRC_IO Parameter Groups_Shunt V

Frequency HZ Voltage pulses/Sec (Hz) 0 to 100 Hz (FLOAT)
TMR_DiffLimt Diag limit, TMR input vote difference, in engineering units 0 to 100 difference in Hz (FLOAT)
MVRC_IO Parameter Groups_Thermocouples

ThermCplType Select TC type or mV input Unused, mV, T, K, J, E, S
ThermCplUnit Select TC display unit degrees C or F Deg_F, Deg_C

TBCA Thermocouples Input Board
The Simplex RTD Input (TBCA) terminal board supplies 30 RTD with precision current
source, then reads and returns the RTD signals.
Operation
The I/O processor performs the analog-to-digital conversion and the linearization for
individual RTD types.
Specifications
Item Specifications
Number of channels 30 RTD channels per terminal board
RTD types N120, PT200, PT100_SAMA, PT100_USIND, CU10, PT100_PURE, Ohms_10,
PT100_DIN.

Note Refer to the TBQA Thermocouples Input Board section in the MVRA I/O
Interface Board section.
TBCB Terminal Board
The TBCB provides for phoenix block screw connection between specific external
customer field devices and the Mark V control cabinets. It routes the raw analog input and
output through ribbon cables to the PMVE to condition, process, and control the signal.
The TBCB board has no active electronics, just protective circuits and jumpers. Each
screw has a defined input or output function. The TBCB allows connection to customer
RTDs and analog output devices.
Operation
analog signals.
Specifications
Item Specifications
Number of inputs 14 RTDs
8 - 0 to 1 mA or 4 to 20 mA
14 – 4 to 20 mA

Configuration
<C>
7
Rev. TBCBQ#A
optional

BJ1 to BJ22 are for input circuits 1 to In = connects NEG Out = mA input is If the hardware jumper is installed, the
22, respectively of mA current not referenced to NEG terminal of the respective mA input
inputs to DCOM DCOM is connected to DCOM
Jumper Input Circuit Position Application Notes
BJ23 15 In = 4-20 mA input Out = 0-1 mA input Hardware jumpers 23-30 modify the
current range characteristics of circuits
BJ24 16
15-22 (BJ 15-22)
BJ25 17
BJ26 18
BJ27 19
BJ28 20
BJ29 21
BJ30 22

TCPD Terminal Board
TCPD Jumper Configuration

<PD> 1 Rev. TCPDG#B

BJS In = provide ground Out = 125 V dc system Ground reference jumper
reference for 125 V dc already has ground Remove for systems with external ground
reference point reference on 125 V dc system
For circuit drawing, refer to Appendix page 4–5.
CTBA Terminal Board
The CTBA provides for phoenix block screw connection between specific external
The CTBA has no active electronics, just protective circuits and jumpers. Each screw has
a defined input or output function. The CTBA allows connection to customer shaft current
and voltage monitoring, as well as 4-20 mA analog input and output devices.
Operation
analog signals.
Specifications
Item Specifications
Number of inputs 14 - 4 to 20 mA inputs
1 shaft voltage monitoring
1 current monitoring
Number of outputs 16- 4 to 20 mA outputs
Configuration
<C> 6 Rev. CTBAG#A

BJ1 In = connects NEG of Out = mA inputs is not If the hardware jumper is installed, the NEG
to BJ14 mA current inputs to referenced to DCOM. terminal of the respective mA input is connected
DCOM to DCOM.
BJ15 Default connected DCOM not connected DCOM connection for RS232 Monitor Port (TIMN)

MVRC Specific Alarms
5401-5442,
8401-8442
Description Thermocouple [ ] Unhealthy
Possible Cause
• Thermocouple mV input on terminal board exceeded the thermocouple range or

hardware limit. Refer to help documentation for specified thermocouple ranges.
• Thermocouple configured as wrong type
• Board detected a thermocouple open and applied bias to circuit, driving it to a large
negative number, or TC not connected, or condition such as stray voltage or noise
Solution
• Check the thermocouple for an open circuit.
• Verify that the incoming mV signal does not exceed -63 mV.
5443-5445,
8443-8445
Description Cold Junction [ ] Unhealthy, Using Backup
Possible Cause Local cold junction signal from terminal board is out of range
(normal range is -30 to 65°C or -22 to 145 °F).
Solution If the hardware is in the normal temperature range, there is a possible

hardware failure of the cold junction sensor on the terminal board. Replace terminal board.

5446-5481,
8446-8581
Description Analog Input [ ] unhealthy
Possible Cause

• Analog input current input beyond the specified range.
Solution
• Check field wiring and connections to indicated analog input channel.

• Check the ground select jumper for input.
• Verify that the inputs are in operable range (3.0-21.5 mA).
5482-5525,
8482-8525
Description RTD [ ] Unhealthy
Possible Cause
• RTD wiring/cabling open or high impedance

• Open on the connections to the terminal board
• RTD device failed
• Internal hardware problem
Solution
• Check the field wiring for open circuit or high impedance.

• Verify the proper connections to the terminal board.
• Check the RTD for proper operation.

5526-5536,
8526-8536
Description Pack internal reference voltage [ ] out of limits
Possible Cause Calibration reference voltage more than ±5% from expected value

Solution

5537-5547,
8537-8547
Description Pack internal null voltage[ ] out of limits
Possible Cause Null voltage more than ±5% from expected value

Solution


MVRF I/O Interface Board
The MVRF is an I/O board on the PMVE using the high-speed serial link (HSSL). The
PMVE contains specialized code for the MVRF that communicates and controls the
MVRF analog and digital I/O. Configuration parameters customize MVRF operation. The
MVRF is a functional replacement for the Mark V TCQB board.
MVRF analog and digital I/O is as follows.
• Thermocouples (simplex)
• Servos and LVDTs
• Pulse rates
• Proximeters
• Analog inputs
• Analog outputs

Installation
The MVRF mounts in the rack behind the PMVE in position one.
Ø To install the MVRF

1. Verify that power has been removed from the core.
Note The red or blue stripes on the cables are always on the left.
3. Holding the board in place. press up the three top and three bottom tabs
5. Remove the new MVRF from its static bag, and reverse this procedure.
6. Once the MVRF is in place, connect the HSSL link cable from the PMVE.
Operation
The PMVE contains configuration parameters specific to the MVRF. External data is
transferred to and from the control system database in the controller over the IONets. The
PMVE propagates the control and data to each of its I/O boards. Data is transferred to the
MVRF across the HSSL every five milliseconds.
Recalibration
Specifications
The MVRF has the same hardware functionality as the TCQF. Original TCQF ribbon
cables plug directly into the MVRF to simplify replacement.

13 Thermocouples TBQA
4 Servos TBQG
4 Analog inputs 10 V TBQC
15 Analog inputs 4-20 mA TBQC
6 Analog outputs TBQG
8 LVDT TBQC
4 Pulse inputs (magnetic) TBQC
All analog and digital I/O signals are read and written at the 5 ms rate by the PMVE(s).

Diagnostics
The MVRF has its own ID device, which is interrogated by the PMVE. The MVRF board
Configuration
MVRF Board Parameters

Min_MA_Input This is the minimum mA for healthy 4/20 mA input. The MVRF 0 to 22.5 mA (FLOAT)
generates an unhealthy status for any of the 4-20 mA inputs
that are less than this value.
Max_MA_Input This is the maximum mA for healthy 4/20 mA input. The 0 to 22.5 mA (FLOAT)
MVRF generates an unhealthy status for any of the 4-20 mA
inputs that are greater than this value.
LVDT_TMR_DiffLim This is the TMR input vote difference in % of range. The R, S, 0 to 200 % (FLOAT)
and T controllers calculate the median value of the three TMR
LVDT values. If any of the TMR LVDTs are greater than or
less than this difference from the median value in percentage,
a diagnostic is generated.
AccelCalcInMs This is the Calc Accel using x ms (5 ms granularity) of 5 to 160 ms (FLOAT)
samples. Acceleration is the change in speed over a time
delta. This parameter specifies that time delta in milliseconds.
The longer the time delta, the smoother the acceleration.
TBQCRevAATermBoard TBQC is a revision AA terminal board. The TBQC revisions > No, Yes
AA have a resistor in the feedback circuit. This generates a
gain error that must be corrected.
TBQGRevAATermBoard TBQG is a revision AA terminal board. The TBQG revisions > No, Yes
AA have a resistor in the feedback circuit. This generates a
gain error that must be corrected.
AVSelection These are the TMR internal selection variables. Unused, AOut1IndivCurFdbk,
brought out to signal space. AOut3IndivCurFdbk,
This is used to monitor the individual current feedback of AOut4IndivCurFdbk,
the TMR current summed analog output to determine proper AOut5IndivCurFdbk,
operation. AOut6IndivCurFdbk,
This is not a TMR voted value, but an individual value from SoftwareSpare
each I/O pack.
This is used for initial check out and for field diagnostic issues.

MVRF I/O Parameter Groups
MVRF_IO Parameter Groups_Analog Inputs

InputType Type of analog input Unused, 4-20 mA
Low_Input Input mA (or V) at low value -10 to 20 mA or V (FLOAT)
Low_Value Input value in engineering units at low mA (or V) E.U. (FLOAT)
High_Input Input mA (or V) at high value -10 to 20 mA or V (FLOAT)
High_Value Input value in engineering units at high mA (or V) E.U. (FLOAT)
Analog Input( E.U.) = Low_Value + (High_Value - Low_Value) *
DiagHighEnab This enables the high input limit diagnostic. If the 4-20 mA Disable, Enable
analog input exceeds the parameter Max_MA_Input, and
DiagHighEnab is enabled, a diagnostic alarm is generated.
DiagLowEnab This enables the low input limit Diagnostic. Disable, Enable
If the 4-20 mA analog input exceeds the parameter
Min_MA_Input, and DiagLowEnab is enabled, a diagnostic
alarm is generated.
TMR_DiffLimit This is the Diag Limit,TMR input vote difference, in percent 0 to 200 % (FLOAT)
of (High_Value – Low_Value). The RST controllers calculate
the median value of the three TMR analog inputs values. If
any of the TMR analog inputs are greater than or less than
this difference from the median value in percent, a diagnostic
alarm is generated.
MVRF_IO Parameter Groups_Analog Outputs

Output_MA Output mA selection Unused, 0-20 mA
Suicide_Enab This enables suicide for faulty output current if in a TMR current Disable, Enable
sharing configuration.
TMR_SuicLimt This is the suicide threshold for TMR operation with load 0 to 200 mA (FLOAT)
sharing margin in mA. If any of the three individual analog
outputs exceeds 50% of the mA output plus this margin, the
mA output is allowed to suicide.
D/A_ErrLimit This is the suicide threshold, for TMR operation with 0 to 200 % (FLOAT)
defective D/A reference versus commanded output feedback
in percentage. If the hardware command output and the
commanded D/A difference exceed this limit for more than
three frames, the mA output performs a suicide.

MVRF_IO Parameter Groups_Analog Outputs
OutputState This is the state of the analog output when offline. It sets the PwrDownMode, HoldLastVal,
mA output to a known milliamp value when the MVRF is offline. Output_Value
PwrDownMode sets analog output to 0.0 in engineering units.
engineering units received before the MVRF went offline.
Output_Value allows the user to specify the offline value in
engineering units.
Output_Value This is the pre-determined value for the outputs. This specifies E.U. (FLOAT)
the engineering unit value to set for analog output when the
MVRF goes offline.
MVRF_IO Parameter Groups_Cold Junctions

ColdJuncType This selects CJ type. It allows control software to substitute the Remote, Local
current terminal board’s cold junction value in degrees with
another value from application space in degrees.
ColdJuncUnit Select TC display unit in ºC or ºF Deg_F, Deg_C
MVRF_IO Parameter Groups_LVDTs

MinVrms This is the LVDT V rms at min end stop (normally set by 0 to 7.1 V (FLOAT)
auto-calibrate). It is the absolute value in V rms read by the
LVDT when the valve is at the minimum end position.
MaxVrms This is the LVDT V rms at Max End Stop (normally set by 0 to 7.1 V (FLOAT)
auto-calibrate). It is the absolute value in V rms read by the
LVDT when the valve is at the maximum end position.
MinPosValue This is the position at Min End Stop in engineering units. It is -15 to 150 % (FLOAT)
the position in percent to be returned by the LVDT when the
valve is at the minimum end position.
MaxPosValue This is the position at Max End Stop in engineering units. It is -15 to 150 % (FLOAT)
the position in percent to be returned by the LVDT when the
valve is at the maximum end position.
LVDT Input Position = MinPosValue + (MaxPosValue - MinPosValue) *
[( Lvdt Vrms Input - MinVrms) / (MaxVrms - MinVrms)]
PositionMargin This is the allowable range exceed error of position in %. If the 1 to 10 % (FLOAT)
position exceeds the MaxPosValue or MinPosValue by this
percent, it generates an unhealthy status and a diagnostic
alarm.

MVRF_IO Parameter Groups_Monitors
RegType This is the monitor regulator type selection. It allows monitoring
of the regulator’s control feedback in percent. The monitor type
must match the regulator type.
ServoNum This is the servo number used. Servo01, Servo02, Servo03,
Select the servo’s feedback to be monitored based on the Servo04, Servo05, Servo06,
selected monitor’s RegType, but only one of the below MonVxx Servo07, Servo08
parameters is visible or selectable.
MonVarPos This is the monitor variable selection for position regulator. Unused, Position1, Position2,
Select one of these to be monitored in percent. Position3, ServoCurrentRef
MonVarLiqFuel The monitor variable selection for liquid fuel regulator allows Unused, Flow1, Flow2,
one of these to be monitored in percent. ServoCurrentRef
MonVarSpdRat The monitor variable selection for speed ratio regulator allows Unused, Pressure1, Pressure2,
one of these to be monitored in percent. Position, OuterRegErr,
OuterLoopErr, Position2,
Position1, ServoCurrentRef
MVRF_IO Parameter Groups_Pulse Rates

PR_Enable Enables pulse rate (PR) input Disable, Enable
PRScale Pulses per second scaled to engineering units 0 to 1000 (FLOAT)
TMR_DiffLimit This is the Diag Limit, TMR input vote difference in engineering 0 to 20000 difference (FLOAT)
units. The controller calculates the median value of the three
pulse-rate input values. If any of the three are greater than
or less than this difference in percent, a diagnostic alarm is
PR input.
TeethPerRev This is the teeth per revolution. It is the number of teeth or 1 to 195 Teeth/Rev (INT)
gear of vanes that pass in one revolution. This must be an
integer value.
Example:
Teeth/Rev = 4
EnhSpdAlgEnab Enhanced speed algorithm enable is used for speed wheel Disable, Enable
or any multi-tooth per revolution speed sensed device. This
algorithm corrects for machined tooth spacing differences. Do
not use for protection or on a frequency generators.

MVRF_IO Parameter Groups_Regulators

RegType Servo regulator algorithm type Unused, Position, SpeedRatio,
LiquidFuel, LiquidFuel_wPosition
RegGain This is the position loop gain in % of (current / engineering -200 to 200 (FLOAT)
unit). This adjusts the regulator loop gain response. The higher
this value, the faster the servo valve responds. This rate is
limited by the valves slew rate.
RegNullBias This is the position loop null bias in % of current minus balances -100 to 100 (FLOAT)
servo spring force. This force closes or opens the valve if the
power is lost. This parameter compensates to this force.
EnabCurSuic This is the current suicide enable. If the current feedback Disable, Enable
suicide is enabled and all of the following is true, the servo
performs a suicide:
a) The difference between the commanded current and the
individual current feedback exceeds the Curr_Suicide limit.
b) It exceeds the limit for a period greater than .5 second
EnabPosFbkSuic If the position feedback suicide is enabled and all the following Disable, Enable
is true, the servo performs a suicide:
a) the Position feedback exceeds the position limits of either:
• MinPosValue - Fdbk_Suicide
• MaxPosValue + Fdbk_Suicide
b)• It exceeds the limit for a period of PosFailDelay in
milliseconds.
EnabPressureFbkSuic If the pressure feedback suicide is enabled and all the following Disable, Enable
is True, the servo performs a suicide.
a) the pressure feedback exceeds the pressure limits of either:
PresFbkLowLim
PresFbkHighLim
b) It exceeds the limit for a period of PressureFailDelay in
milliseconds.
EnabFlowFbkSuic If the flow feedback suicide is enabled and all the following is Disable, Enable
True, the servo performs a suicide:
a) the flow feedback exceeds the flow limits of either:
FlowFbkLowLim
FlowFbkHighLim
b) It exceeds the limit for a period of FlowFailDelay in ms.
Curr_Suicide Short servo output if current error exceeds this amount in 0 to 100 % (FLOAT)
percentage
Fdbk_Suicide Short servo output if position feedback error exceeds this 0 to 10 % (FLOAT)
amount in percentage
TMR_DiffLimit This is the Diag limit, TMR input vote difference, servo current -15 to 150% (FLOAT)
in engineering units.
The controller calculates the median value of the three servo
currents values. If any of the three servo currents are greater
than or less than this difference in percent, a diagnostic is
servo output.

DitherAmpl Dither in % current. Amplitude of the dither moves a valve from 0 to 10 % (FLOAT)
a fixed position and back again. This dithering is to reduce
breakaway torque if the valve sits in a fixed position for an
extended time.
DitherFreq Dither rate in Hertz. Rate at which dithering moves a valve Unused, 8_33 Hz, 12_5 Hz, 16_67
from a fixed position and back again. This dithering is to Hz, 25 Hz, 50 Hz, 100 Hz
reduce breakaway torque if the valve sits in a fixed position
for an extended time.
the LVDT configuration. This selection is valid for the Position LVDT07, LVDT08, LVDT09,
regulator type LVDT11, LVDT10, LVDT13,
LVDT12, LVDT15, LVDT14,
LVDT16, Unused
PressureInput1 Pressure input 1 selection Unused, AnalogInput1,
PressureInput2 Pressure Input 2 Selection Unused, AnalogInput1,
PulseRateMPU2,

PulseRateMPU2,
K_OuterReg Outer Regulator Gain -200 to 200 (FLOAT)
K_Conv_OuterReg Outer Regulator K_Conv -200 to 200 (FLOAT)
Tau_OuterReg Tau for Outer Regulator 0 to 10 (FLOAT)
LowLim_OuterReg Outer regulator low limit -200 to 200 (FLOAT)
Outer regulator low limit clamp
HiLim_OuterReg Outer regulator high limit -200 to 200 (FLOAT)
Outer regulator high limit clamp
PresFbkLowLim Pressure feedback low limit -150 to 5000 (FLOAT)
If pressure feedback is lower than this limit, a diagnostic is
is enabled
PresFbkHiLim Pressure feedback high limit -150 to 5000 (FLOAT)
If pressure feedback is higher than this limit a diagnostic is
is enabled
FlowFbkLowLim Flow feedback low limit -150 to 5000 (FLOAT)
If Flow feedback is lower than this limit, a diagnostic is
enabled
FlowFbkHiLim Flow feedback high limit -150 to 5000 (FLOAT)
If flow feedback is higher than this limit, a diagnostic is
enabled
PosFailDelay Time delay (msec) before position feedback suicide is 0 to 10000 ms (FLOAT)
PressFailDelay Time delay (msec) before pressure feedback suicide is 0 to 10000 ms (FLOAT)
FlowFailDelay Time delay (msec) before flow feedback suicide is generated 0 to 10000 ms (FLOAT)
on a fault. This time delay keeps the firmware from generating
a suicide based on a transient condition.

Simple Regulator with Gain and Feedback Control
MVRF_IO Parameter Groups_Thermocouples

ThermCplType Select TC type or mV input Unused, mV, T, K, J, E, S
ThermCplUnit Select TC display in unit degrees C or F Deg_F, Deg_C

Enhance Speed Algorithm (ESA)
Variability on the gear tooth wheel spacing causes variability in the speed measurement
and acceleration. The ESA measures and corrects this spacing. However, it does not
introduce latencies or correct for electronic or sensor abnormalities. If the ESA cannot
correct for the speed anomalies, it defaults to the evenly spaced algorithm. The ESA
should not be used for critical overspeed functions. The only requirement for this mapping
to occur is to enable the ESA and then set the teeth per revolution to the correct value.
Note This can be used for any pulse device that has multiple tooth or pulses generated
per revolution, but it must be an integer number. ESA should not be used for pulse
generators, or devices that generate a precision pulse rates.
With a multi-gear box, the ESA is only required to have the number of gear teeth on the
sense gear. The scaling can accommodate the gearing ratios. If the ESA tries to correct for
a variation that does not exist, noise or jitter in the speed or acceleration signal results.
Calculating Tooth Correction Factors
The correction factor is the percentage that the tooth represents of the whole (one
revolution). For example, each of four teeth in a wheel represents 25% of the whole.
Removing variation from the speed is determined by individual tooth corrections

according to the following equation (where k = teeth in a revolution).
The system for calculating rotation depends on parameters sensing the rotation of a
toothed speed wheel, then correcting by the following equation:
Pulse Input(E.U.) = Freq(hz) * ( 60.0(sec/min) / TeethPerRev) * PRScale(E.U)

Servo Regulator Diagrams
Position Regulator

Speed Ratio Regulator

Speed Ratio PI Control

Liquid Fuel Regulator

Liquid Fuel with Position Feedback

Liquid Fuel PI Control

Note Refer to the TBQA Thermocouples Input Board section in the MVRA I/O
Interface Board section.
TBQC Terminal Board

Note Refer to the TBQC Terminal Board section in the MVRA I/O Interface Board
section.
TBQG Terminal Board
The TBQG provides for phoenix block screw connection between specific external
The TBQG has no active electronics, but contains simple protective circuits and jumpers.
Each TBQG screw has a defined input or output function. The TBQG allows connection
to customer LVDTs, 4-20 mA inputs and outputs, speed and fuel flow divider pickup
signals, servo valve outputs, and water injection flow meter inputs.
Operation
analog signals.

Specifications
Item Specifications
Number of inputs 4 pulse inputs
4 - 4 to 20 mA inputs
Number of outputs 4 servo outputs
4 analog outputs
TBQG Analog Input Jumpers
JP1 1-2 ±10 V 2-3 4-20 mA

JP2 1-2 ±10 V 2-3 4-20 mA
JP3 1-2 ±10 V 2-3 4-20 mA
JP4 1-2 ±10 V 2-3 4-20 mA
The MVRF functions much like the TCQA, and uses a time-based algorithm to improve
speed and acceleration.
The PMVE algorithm collects the number of tooth pulses and 25 Mhz tics that occurred
between those pulses within a specified time interval.
Pulse Input(E.U.) = Freq(hz) * (60.0(sec/min) / TeethPerRev) * PRScale(E.U)
Configuration
<S>
7
Rev. TBQGQ#A
optional

JP1 Default 24–20 mA or ±10 V dc burden resistor (250 ohm)
2–3 = current input configuration
1–2 = voltage input Input #1
JP2 1–2 2–3 Input #2
JP3 1–2 2–3 Input #3
JP4 1–2 2–3 Input #4

MVRF Specific Alarms
5401-5415,
8401-8415
Description Thermocouple [ ] unhealthy ([ ])
Possible Cause
• Thermocouple mV input on terminal board exceeded thermocouple range or hardware

limit. Refer to help documentation for specified thermocouple ranges.
• Thermocouple configured as wrong type
• Board detected a thermocouple open and applied bias to circuit, driving it to a large
negative number, or TC not connected, or a condition such as stray voltage or noise
Solution
• Check field wiring, including shields. Problem is usually not a MVRF or terminal
• Check the thermocouple for open circuit.
• Verify that the incoming mV signal does not exceed -63 mV.
5416-5416,
8416-8416
Description Cold Junction Unhealthy, Using Backup
Possible Cause Local cold junction signal from terminal board is out of range
(normal range is -30 to 65°C or -22 to 145 °F).
Solution If the hardware is in the normal temperature range, there is a possible

hardware failure of the cold junction sensor on the terminal board. Replace terminal board.

5417-5420,
8417-8420
Description Analog ±10 V Input [ ] unhealthy ([ ] V)
Possible Cause

• Analog input voltage input beyond specified range
Solution
• Check the field wiring and connections to the indicated analog input channel.
• Check the ground select jumper for the input.
• Verify that the inputs are in operable range (-10 V to 10 V).
5421-5435,
8421-8435
Description Analog 4-20 mA Input [ ] unhealthy ([ ] mA)
Possible Cause

• Analog input current input beyond the specified range
Solution
• Check the field wiring and connections to indicated analog input channel.
• Check the ground select jumper for the input.
• Verify that the inputs are in operable range ( 3.0 to 21.5 mA)
5436-5439,
8436-8439
Description LVDT Excitation [ ] Failed
Possible Cause Faulty cable between terminal and acquisition card
Solution Inspect cable and replace, if needed.

5448-5455,
8448-8455
Possible Cause
• Excitation voltage to LVDT incorrect

• LVDT input out of range
Solution
• Check the field wiring, including shields and LVDT excitation. Problem is usually
not a MVRF or terminal board failure if other LVDT inputs are working correctly.
• Verify that PosMargin is set to the proper value.
5456-5457,
8456-8457
Description Monitor [ ] Invalid Servo Configuration
Possible Cause Invalid configuration for selected servo and regulator type
Solution
• Verify that the monitor regulator type matches the regulator type of the selected servo.
• Rebuild and download configuration.
5458-5458,
8458-8458
Description More than One Servo Requested for Calibration
Possible Cause
• More than one ToolboxST interface trying to calibrate the regulator

• Only one servo can be calibrated at a given time, but multiple calibration requests
are being made.
Solution Check the variables in the Variables tab to verify that only one CalibEnab#
for only one servo is set to True at a given time.

5459-5459,
8459-8459
Description Calibration, Selected LVDT Max / Min Pos Limit Out of Range
Possible Cause Used to ensure that all selected LVDTs are scaled to the same units.
• MaxPosValue or MinPosValue for selected LVDT configured in regulator

configuration is out of range (±50%), encountered during calibration.
Solution
• Check the regulator configuration for the parameter PositionInput#1 for the
particular servo.
• Check the MaxPosValue and MinPosValue for the LVDT# selected input in
PositionInput#1.
• The MaxPosValue for LVDT Input should be between 50% to 150%.
• The MinPosValue for LVDT Input should be between -50% to 50%.
5460-5463,
8460-8463
Description PulseInput [ ] unhealthy ([ ])
Possible Cause
• Pulse rate input exceeds maximum limit

• Broken wire on flow rate input
• Faulty sensor
Solution
• Check field wiring, including shields. Problem is usually not a MVRF or terminal
board failure if other flow rate inputs are working correctly.
• Check gap on magnetic pickup sensor.
• Replace the hardware.

5464-5467,
8464-8467
Description Servo [ ] Disabled, Configuration error Fault No:[ ]
Possible Cause

• Servo pressure input connected to unused analog input
Solution
• Check that the regulator inputs are connected to used sensor inputs in the
configuration.
5468-5471,
8468-8471
Description Servo [ ] Output Suicide Active
Possible Cause

• Servo pressure input connected to unused analog input
• Regulator feedback out of range
• Servo current feedback differs from servo current command
Solution
• Check inputs are connected to used sensor inputs in the configuration.
• LVDT Fdbk issue: Check position sensor connections.
• Check position sensor mechanical integrity to the valve.
• Check for wiring of servo output loop for open or short circuit.
• Check for short or open servo coil.

5472-5475,
8472-8475
Description Servo [ ] Position Feedback out of range ([ ] %)
Possible Cause LVDT position feedback outside of specified range
Solution
• Check the LVDT configuration settings.

• Calibrate the affected regulator.
• Check the field wiring.
• Check for a shorted/open position sensor coil.
• Check the position sensor mechanical integrity.
5476-5479,
8476-8479
Description Servo [ ] Pressure Feedback out of range ([ ])
Possible Cause Pressure feedback in a servo regulator outside specified range
Solution Check the source of the pressure signal including the sensor, field wiring,
and configuration.
5480-5483,
8480-8483
Description Servo [ ] Flow Feedback out of range ([ ])
Possible Cause Flow feedback in servo regulator outside specified range
Solution
• If active pulse rate flow sensor, check power to the device, field wiring, sensor, and
configuration.
• If magnetic pulse rate flow sensor, check device, field wiring, and input configuration.
• Check the gap between the sensor and the flow wheel.
5484-5490,
8484-8490
Possible Cause Calibration reference voltage more than ±5% from expected value

Solution


5491-5497,
8491-8497
Possible Cause Null voltage more than ±5% from expected value

Solution

5498-5501,
8498-8501
Possible Cause

Solution
• Verify that the commanded output is within range of the output.

• Check the field wiring and device. Problem is usually not a MVRF or terminal board

5504-5509,
8504-8509
Possible Cause

Solution
• Verify that the commanded output is within range of the output.

• Check the field wiring and device.
5510-5515, 8510-8515
Description Output [ ] 20 mA suicide active
Possible Cause

Solution
• Verify that the sensor feedback is within limits.


5516-5522,
8516-8522
Description Output [ ] 20 mA suicide active

• Command beyond range of output
Solution
• Check the field wiring and status of the connected device.

5522-5527, 8522-8527
Possible Cause Analog output suicide relay command does not match feedback

Solution If a hardware failure, replace the acquisition card.
5528-5533,
8528-8533
Possible Cause Analog output suicide relay command does not match feedback

Solution If a hardware failure, replace the acquisition card.

5534-5539,
8534-8539
Description Output [ ] DAC Cmd Volts Disagrees with DAC feedback by 5%
Possible Cause Output command voltage disagrees with DAC feedback
32
Possible Cause N/A
Solution N/A
5800-5828, 8800-8828
5851-5862, 8851-8862



MVRP Power Board
The MVRP power board provides power distribution for the existing Mark V control
hardware and the upgraded Mark VIe control hardware with communication to the PMVE.
The MVRP is a 28 V dc/dc converter with multiple outputs. The connectors and pin
outputs are fully compatible with the existing control hardware. The MVRP provides the
following outputs:
• +5 V dc
• ±15 V dc
• ±15 V dc (A)
• ±15 V dc (B)
• +28 V dc
• +28 V dc (1)
• +28 V dc (2)
The maximum input power is 150 W, maximum output power is 137 W, and the full Load
efficiency is 91%. Soft start is available for the input, and current limiting is available for
all outputs except ±15. The ±15 V dc (B) outputs provide a symmetrical current latch for
both the positive and negative halves during overloads.
The MVRP has two main power sections: a 40 W switcher that operates at 116 KHz and a
smaller 3 W switcher that operates at 300 KHz. Three of the bipolar outputs provide 1500
V isolation. The MVRP measures 208.9 mm x 57.0 mm (8.224 in x 2.244 in) and weighs
0.18 Kg (0.4 lb). Diagnostics provide feedback to the PMVE.

MVRP Layout

MVRP Block Diagram

Installation
The MVRP is installed in the power supply assembly, GE P/N 259B2451EZG01. The
connectors, pin outputs, loads, and diagnostic outputs are defined by this power supply
assembly, which is a retrofit for the existing Mark V control cores. The MVRP input power
comes from a 150 W, 125 V to 28 V dc/dc converter, GE P/N 342A4922P28V150DHNC.
The following instructions are used to reassemble the R, S, and T cores. The power supply
module is the first item to be installed in the core.
Ø To reassemble cores S, R, and T

1. Before placing the power supply (catalog number 259B2451EZG01) in the core,
plug cable 2PL (part number 336A4940FL G01), supplied with core material, into
connector 2PL, located on the MVRP board. The red wire in the 2PL cable must
align with Pin 1 on the board.
Note If there is not enough cable length to allow the connections, connect the cables
after the power supply is seated.
2. Locate connectors JP1 and JP2 on the MVRP board and the NYOGEL 10cc syringe
found in the field service kit.
3. Lubricate JP1 and JP2 by inserting the male pin into the syringe tip opening. There
should be sufficient lubricant in the tip to allow the coating of two pins before the
syringe plunger needs to be depressed slightly. If lubricant is exposed on the outside
of the tip, remove excess by wiping with a clean cloth. Verify that the lubricant does
not extrude out and touch adjoining pins.
Note Lubrication is needed to prevent tin-to-tin fretting corrosion. Refer to TB04931

and GEI–100304 Lubricating Tin/Lead Electrical Connectors Used on Printed Wiring
Boards for further information.

Note To avoid damage, do not push on the heat sinks when installing the power
supply. Refer to the next photo.

4. At location 5, position the power supply at a 30-degree angle in the plastic frame. The
bottom of the power supply must make contact with the three plastic tabs located at
the bottom of the frame.
5. Align the three bottom frame posts with the power supply postholes. While holding
the bottom power supply frame plate in place and maintaining posthole alignment,
gently lower the power supply module until it makes contact with the three upper
tabs. Apply pressure, and allow the supply to rest on upper tabs.
6. While continuing to hold the bottom power supply frame plate, seat the bottom of
the power supply by pushing tab 1, then tab 2 and tab 3. Repeat walking across the
tabs until the power supply is properly seated into the frame. This usually takes
three or four cycles. Use gentle to moderate pressure on the power supply frame to
seat the module easily.
7. Repeat step 4 to seat the top of the power supply module. Verify that it is fully
seated before continuing.
8. Connect cables JP1, JP2, JC, and X1 into the MVRP power board.

9. Connect power cable J1 to the short pigtail connector J1-125VDC located on the lower
right of the power supply. J1 is an existing cable from the disassembly procedure.
The longer pigtail cable with connector JPDV-J28 is connected later in this procedure.
10. Attach the power supply ground wires (green/yellow) from the PS1 connector P1-Gnd
and PS2 connector P1-Gnd to the enclosure (PE) ground bus located in the bottom
right corner of the enclosure. Verify that cables JP1, JP2, 2PL, X1, P1-Gnd (PS1),
and P1-Gnd (PS2) are connected to the power supply.
R, S, T, and C Core Power Supply Ground Wire Paths to PE Ground

Operation
Input Filter
The input filter consists of a transient suppressor and common mode filter. The filter
powers three sections of the MVRP:
• The solid state circuit breaker that current limits the 28 V loads powered by the MVRP
• The dc/dc converter module that provides isolated ±15 V dc power, reference to
common ICOMA
• The push-pull power supply that generates:
− +5 V dc
− Isolated ±15 V dc power, reference to common BCOM
− ±15 V dc power, reference to common PCOM
Circuit Breaker
An LT1641-2 hot swap controller IC and support circuitry comprise the solid state circuit
breaker. The circuit breaker provides
• Fold back current limiting

• Automatic retry
• Soft start
• Under voltage lockout
The breaker has an under voltage lockout of 14.5 V. The current limit is 4.7 A. The rated
load is 4 A, shared among three outputs: P28, P28-1 and P28-2. The Calex® dc/dc provides
three watts of isolated ±15 V dc power, tight voltage regulation, and current limiting.
The heart of the push-pull power supply is the UCC28089 push-pull controller IC. The
controller features:
• Under voltage lockout with hysteresis

• Soft start and automatic over-current/retry
• Primary side under-voltage protection (UVLO)
• Turn-on/off UVLO with 10.5 V / 8.0 V thresholds
• Push-pull oscillator with dead time
• Dual alternating push-pull output
• Duty cycle limited to less than 50%
The power Mosfets are avalanche rated to handle the high voltage transients at turn on.
The top output winding powers a Schottky full wave rectifier with capacitive filter. This
provides 6.5 V minimum to an LM1086 low drop out regulator set for a 5 V dc output,
referenced to PCOM. A filter capacitor on the 5 V dc output provides additional ripple
reduction and some hold up capacity. The LM1086 has built in current limiting.

The middle winding powers a full wave rectifier with capacitive filter to provide ±15 V dc
unregulated power, referenced to PCOM. A capacitive filters output filter and provides
some hold up capacity. Standard fast rectifiers (non Schottky) provide a fixed voltage drop
to reduce the output voltage. Pre load resistors lower the no load output voltage. No
current limiting is provided on this output.
The bottom winding powers a full wave rectifier with capacitive filter to provide ±15
V dc unregulated and isolated power, referenced to BCOM. A capacitive filters output
filter and provides some hold up capacity. Standard fast rectifiers (non Schottky) provide
a fixed voltage drop to reduce the output voltage. Pre load resistors lower the no load
output voltage. An overload on any output (P15B to N15B, P15B to BCOM, N15B to
BCOM) will latch off both outputs. The latch activates when P15B or N15B sag to ±11 V.
The MVRP input power must be cycled to reset the latch. Static overload protection is
provided by a 0.5 A polyfuse that, when activated, drops the output voltage and sets the
latch. The on state impedance of the polyfuse helps to drop voltage to trigger the latch
during transient overloads, such as short circuits. The transformer impedance will also sag
the output voltage during overloads, and thereby assisting to activate the latch.

Specifications
Input voltage range 27.4 28.6 V dc
Input current at 28 V dc 0.225 A at No load 4.75 A at 121.7 W out
Power output, max, Po_max 137 Watts
Power input, max at Po_max 150 Watts
V in and output loading Vin = 28.6 V Vin = 27.4 V
all outputs no load all outputs fully loaded
V dc V dc at A dc
P5 (1.5 A max) 5.01 5.01 at 1.160
P15 (0.75 A max) 15.95 14.93 at 0.537
N15 (0.75 A max) -15.78 -14.93 at -0.537
P15B (0.33 A max) 16.15 14.72 at 0.282
N15B (0.33 A max) -15.99 -14.76 at -0.229
P15 A (0.1 A max) 15 15.00 at 0.1 A
N15A (0.1 A max) -15 -15.00 at 0.1 A
P28-1 at JP1 (2.0A max) 27.58 26.91 at 1.682
P28-2 at JP2 (2.0 A max) 27.56 26.92 at 1.749
P28 at 2PL Sum of P28-1, P28-2 and P28 must not exceed 4 A
Voltage isolation
P15A, ACOM, and N15A to all I/O 1500 V ac
P15B, BCOM, and N15B to all I/O 1500 V ac
Input characteristics
Input current 5.4 A, max.
Efficiency 91.6% at 121.7 W output
Switching frequency 116.1 KHz
Input current ripple at 28 V dc with all outputs at full load 330 mA
Under voltage lockout range for P28, P28-1, P28-2 Input 28 V dc = 13.6 V to 14.5 V
Under voltage lockout range for push pull regulator Input 28 V dc = 9.5 V to 11.5 V
Input inrush current with all outputs at full load (graph) 12.8 A pk;
Output characteristics
Start up time at 28 V dc with all outputs at full load P5 Stable: 14 mS; all outputs stable: 22 mS
Output over voltage protection None
Output short circuit characteristics ( dc )
P5 Short circuit current limit 2.0 A
P,N15 Short circuit char. No limiting
P,N15B Short circuit char Poly fuse, 0.5 A. Both outputs are latched off when P15B or N15B
overloads.
P28 Short circuit foldback activation 4.7 A. This is the summed current from P28-1, P28-2, and P28.
P15A, N15A Short circuit curr limit 0.21 A

Output characteristics
Output short circuit characteristics (transient)
P5 Output short circuit transient
P,N15A Output short circuit transient
P,N15B Output short transient
P28 Output short transient (P28, P28-1 or P28-2)
Output ripple
Typical output ripple w/ all outputs at full load, P5 5 mv p-p
Typical output ripple w/ all outputs at full load, P,N15B 10 mv p-p
Typical output ripple w/ all outputs at full load, P,N15 25 mv p-p
Physical characteristics
Board ID chip None
Size 8.225 x 2.250
Weight 0.40 lbs.
Temperature 0°C to 50°C (32 °F to 122 °F) Operational, -50°C to +100°C (-58 °F
to 212 °F) Storage
Humidity 5 to 95% non-condensing
Reliability 1905 failures per billion hours
Safety standards, North America CSA 22.2 No. 1010 Safety requirements for electrical equipment
for measurement, control and laboratory use.
Safety standards, Europe EN 61010-1 safety requirements for electrical equipment for
measurement, control and laboratory use.

Diagnostics
All diagnostic outputs are referenced to PCOM. Scaled analog feedback is provided for
all supplies referenced to PCOM (non-isolated). Simple attenuators scale the voltages
for the diagnostic outputs. The block diagram gives the scaling. The isolated power
supplies “A” and “B” are level sensed and discrete go/no go indications are passed through
optocouplers for ohmic isolation. The block diagram gives the threshold levels.
LED DS1 provides indication of input power.
Analog Feedback
P15S (JC-7): P15 Fbk 0.1667 V_fbk / V_actual
N15S (JC-8): N15 Fbk 0.1667 V_fbk / V_actual ( fbk is positive)
P28S (JC-9): P28 Fbk 0.1667 V_fbk / V_actual ( fbk is positive)
P125BS (JC-15): P125B Fbk 0.0667 V_fbk / V_actual
N125BS (JC-16): N125B Fbk 0.0667 V_fbk / V_actual (fbk is positive)
Discrete feedback Open collector, 40 V max., 2 mA max.
P15AS (JC-11): P15A Fbk, digital P15A > 12.7 → Low
N15AS (JC-12): N15A Fbk, digital N15A < -12.7 → Low
P15BS (JC-13): P15A Fbk, digital P15B > 13.6 → Low
N15BS (JC-14): N15A Fbk, digital N15B < -13.6 → Low
Configuration
The MVRP hardware is non-configurable.
Alarms
The diagnostic outputs are monitored by the MVRA. Alarms are annunciated in the
ToolboxST application and WorkstationST Alarm Viewer.

HSLA Interface
The HSLA is a single or dual port High Speed Serial Link (HSSL) interface for host
application boards (MVRA, B, C, F). The HSLA provides the following features:
• Up to two HSSL interfaces configured as:

− RJ-45 copper CAT3e (right-angle)
− Fiber-optic (fast fiber connections)
• Field programmable gate array (FPGA) for the application program
− Onboard programmable flash available to load the application program
− Protected boot flash to enable initial HSSL communications
• Generic 3.3 V I/O interface with the host application board
− Either input or output
J1 and J2 (55 points)
JL (36 or 51 points)
− Input only
J1 and J2 (0 points)
JL (10 points)
• 3.3 V dc at 1.0 A power supply available to be used by the host application board
Interface to the application board is through the FPGA. Each I/O point is designed to be
general purpose with a few specialized function I/O pins.

Installation
The HSLA and MVRx are combined during factory assembly. The HSLA by itself is not
available as a replacement part for the PMVE module.
Diagnostics
• DS1 is a yellow TX/RX. This LED is only on when data is being transmitted or
received from the HSLA port J3 to the host PMVE.
• DS2 is a green link LED. This LED is on when a valid cable connection is detected
between the HSLA port J3 and the PMVE.
• DS3 is a yellow TX/RX. This LED is only on when data is being transmitted or
received from the HSLA port J4 to the host PMVE.
• DS4 is a green link LED. This LED is on when a valid cable connection is detected
between the HSLA port J4 and the PMVE.
• DS5 is a red attention LED. This is used by the application code for special functions,
such as LED is on during application flash programming.
• DS6 is a green power-applied LED. This LED is on whenever power greater than
5 V dc is applied.
HSLA LEDs

PMVD Digital I/O Module
Digital Input/Output (PMVD)

The PMVD I/O module provides an interface between the Ethernet IONet and the existing
Mark V control contact inputs and relay outputs. The module consists of the MVRD digital
I/O board, processor board, iButton, and the associated firmware. The iButton contains
the unique ID used by the ToolboxST application to initialize the PMVD firmware.
The MVRD board is the same The PMVD connects with the TCRA relay boards, and terminal boards DTBA, DTBB,
shape and size as the Mark DTBC, and DTBD. The PMVD further improves on Mark V control diagnostics by
V control TCDA board it is providing break detection for the ribbon cable and contact input wiring. This break
intended to replace. detection feature is only enabled on systems that have upgraded the existing Mark V
control DS200DTBA and DS200DTBB terminal boards with the newer IS200DTBA and
IS200DTBB terminal boards. A wetting voltage greater than 90 V is also required.
PMVD Module Includes MVRD, Processor Board, and iButton
GEH-6800_Vol_II PMVD Digital I/O Module System Guide 3-1

Compatibility
Three PMVD combinations are required to replace a TMR TCDA on the QD1 and QD2
cores of the Mark V control system. One PMVD combination each is required to replace
a TCDA on the CD core, and simplex QD1 and QD2 cores. Two PMVD combinations
are required to replace the TCDA boards in a DD core, which has contact inputs without
contact outputs and does not use the DTBC and DTBD terminal boards.

Installation
Ø To install the PMVDs as an upgrade from the TCDAs
The PMVD is installed as 1. Verify the terminal boards (DTBA, DTBB, DTBC, and DTBD)(DTBA, DTBB,
an upgrade to the existing DTBC, and DTBD) are securely mounted to the front core board holder.
Mark V control TCDA. For
2. Locate the iButton holder below the processor board on the PMVD assembly and
complete upgrade installation
note the label information for the iButton code. This will be used to initialize the
instructions (including the
ToolboxST* application after the hardware is installed.
removal of TCDAs), refer to
the installation guides for this 3. Connect the PMVDs where the TCDAs were previously located (one PMVD module
platform. replaces one TCDA board). Refer to the section, Compatibility.
4. Depending on the system configuration, plug one or two Ethernet cables into the
processor board's RJ-45 connectors. The PMVD 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. Connect the ribbon cables from the terminal boards (JR, JQ) and relay boards (JO1,
JO2).
Note The cable connectors are keyed. They are installed in the same orientation as
they existed with the former Mark V control TCDA.
6. Connect the JP connector on the side of the PMVD to apply power.
Note It is not necessary to insert this connector with the power removed from the
cable because the PMVD has inherent soft-start capability that controls current inrush.
7. Use the ToolboxST application to configure the PMVD as necessary. Refer to

GEH-6700, ToolboxST User Guide for Mark VIe* Control, Chapter 6 Mark VIe
Component Editor, the section, Hardware Tab.
If the configuration being downloaded contains I/O

packs/modules with different IDs than the configuration
currently running, the download may install incorrect firmware
to some I/O packs/modules. If this occurs, make sure the
controller is running the new configuration, restart the entire
Attention system, and then start the ToolboxST Download Wizard again.
Operation
• Processor Board
• Processor LEDs
MVRD
The MVRD is an I/O board containing the features and functionality of the Mark V
control TCDA board. The MVRD provide 96 contact inputs and 60 digital outputs. It
is designed to be completely compatible with existing Mark V control power supplies,
the TCRA board, and terminal boards DTBA, B, C, and D. The MVRD communicates
directly to the <Q> cores through IONet as part of the PMVD I/O module.

Contact Inputs and Relay Outputs
The PMVD within the digital cores (QD1, QD2, CD, and DD) consists of a set of contact
inputs and relay outputs under control of the IONet. Depending on the core type, there
can be one (simplex) or three (TMR) application boards, two or four terminal boards, and
two relay boards (if contact outputs are part of the core).
PMVD Simplex (CD) Core Block Diagram

PMVD TMR (QD1, QD2) Core Block Diagram

Each of the 96 contact inputs is passed from the DTBA and DTBB terminal boards
through ribbon cables to the MVRD application board. Other ribbon cables in turn pass
relay commands from MVRD board to the two TCRA boards within the core. The 60 sets
of relay contacts from the TCRA boards are connected by high current ribbon cables.
Contact isolation between the battery supply and the internal logic supply is provided by:
• Inputs with digital-isolators between the contact input comparators and the logic
• Outputs with relay coil to contact isolation
The circuitry is designed to The PMVD does not support a mixture of wetting supply voltages on contact inputs and/or
operate with battery supplies outputs within the same core. If a system has both 24 and 125 V dc signals, separate cores
of 24 to 125 V dc (nominal), are needed to support each voltage system separately. In addition, some features may be
where all inputs are referenced disabled based on supply voltage (for example open wire detection is not supported on
to the same supply. systems with less than about 90 V).
Contact Input Failure Compensation

The PMVD uses contact inputs wired to the MVRD digital input board. Inputs may be set
to unhealthy for any of the following reasons:
• The contact input fails its force high hardware test.

• The contact input fails its force low hardware test.
• An open ribbon is detected, in which a ribbon cable such as JR or JQ has failed
or was unplugged.
• An open wire is detected, in which a contact input field wire has failed or has become
open circuited.
• A network communications failure or other hardware failure has occurred.
Each contact input must be In situations where a contact input state goes unhealthy, the associated contact input
specifically designed for the state will go to False, but it is important that the application designer consider the fail
system where it is being applied safe implications of such an unhealthy signal. If necessary, the VAR_HEALTH block
to provide a safe and controlled can be used as shown below to stop a process or equipment and bring the system to
system. safe, controlled state. The following figure is an example of controller application code
for a situation where it is necessary to use a True value instead of a False value (when
a contact input goes unhealthy).

Error Checking
The operation of the PMVD is frame based, with accesses to the contact inputs and
relay outputs performed every millisecond in support of the Sequence of Event (SOE)
processing. The SOE function provides tables of sequences seen on the contact inputs
and relay commands, with time tagging on each of up to four transitions – first, second,
third, and most recent since the last SOE table read. Once read, the SOE table is cleared to
allow a new accumulation of sequence data.
Contact input ribbon cable and external contact wiring checks with added resistors can
only occur when the supply voltage is at 90 volts or higher. The PMVD will not perform
open wire detection on systems operating at 24 or 28 volts. The resistors are added
individually to each switch contact that is to be enabled for open wire detection, as set up
in the ToolboxST application. Resistors are GE part number 64G3514-S133F for a 133
Kilo-ohm 0.5 watt 1% 100 ppm/ °C resistor with axial leads. This resistor can operate
within a range of -65 to 165 °C (-85 to 329 °F), with higher temperatures (such as on
exhausts) requiring a different resistor type.
Open wire detection also relies on the resistance of the wiring to and from the contact,
with up to 20 kilo-ohms on each direction allowed. Higher series resistances will result
in a CLOSED contact not being properly detected and reporting an incorrect OPEN
condition. This series resistance also includes any extra resistance such as on a solid-state
or a non-precious metallic contact. Practically speaking, the 20 kilo-ohm values allows
for very long distances, with up to 237 km for a run using 24 AWG wire. Example wire
gauges and resistances are:
• 12 AWG at 5.2 ohms/km

• 28 AWG at 213 ohms/km
• 40 AWG at 3441 ohms/km
Lengths of wiring are also subject to correct installation – where all contact input wiring
should be fed through metallic conduit for correct shielding. Failure to observe this will
degrade the PMVD’s internal protection against false readings in the event of nearby
EMI/EMC transmissions.
The supply fed to the contacts on inputs must be the same supply voltage as that fed to
the DTBA at connector J12. Sharing of a supply across multiple contacts is allowed, for
example several contacts with single supply wire out and several contact wires back
in the same wire bundle. Jumpers on the DTBA that isolate the supply fed to terminal
board connections (example – contact 1 has the supply at TB1-2 and return from contact
into TB1-1) must be installed to allow for the separate feeds to the contacts from the
terminal strip.
The ribbon cables to the TCRA boards are also tested for operation with checks both at
the current loading of the overall board power consumption as well as individual control
signal sensing of the coil driver load. If an individual signal wire in the ribbon cable opens,
preventing relay control, then the lack of driver input current provides a diagnostic. If the
relay is left open (driver off) then a ribbon break cannot be detected due to the correct lack
of driver current. The PMVD diagnostic alarms use this logic to avoid false alarms.

The ribbon cables to the DTBA and DTBB are verified using sensing logic to detect any
broken ribbon cable signal conductors, and the external contacts may also be optionally
checked for open wiring with the user installing resistors across each contact being
checked. The ribbon cables to the TCRA boards are also tested for operation with checks
both at the current loading of the overall board power consumption as well as individual
control signal loading.
DTBA/B sensing is required for determining if the terminal boards support cable and
wire break detection. This is accomplished by sensing the current drawn on the DTBA
board by a relay, then passing this to the A/D for a comparison check. For this to occur
the IS200DTBA must not be installed with a DS200DTBB or the DS200DTBA must not
be installed with an IS200DTBB.
Power Management
The PMVD includes power management in the 28 V input circuit. The management
function provides soft start to control current inrush during power application. After
applying power, the circuit provides a fast current limit function to prevent an I/O module
failure from propagating back onto the 28 V power system. When power is present
and working properly, the green PWR indicator will light. If the current limit function
operates, the indicator will be out until the problem is cleared.
Connectors
The PMVD contains the following connectors:
• 50-pin connector JQ for the ribbon cable to the DTBA for inputs 1 to 46
• 50-pin connector JR for the ribbon cable to the DTBB for inputs 47 to 96
• 34-pin connector JO1 for the ribbon cable to the TCRA relay board in slot 4 for
outputs 1-30
• 34-pin connector JO2 for the ribbon cable to the TCRA relay board in slot 5 for
outputs 31 to 60
• RJ-45 Ethernet connector, ENET1 on the side of the pack is the primary system
interface
• Second RJ-45 Ethernet connector, ENET2 on the side of the pack is the redundant
or secondary system interface
• 3-pin power connector on the side of the pack is for 28 V dc power for the pack
and terminal board

Specifications
Item Specification
Number of channels 96 contact inputs referenced to the battery supply

60 relay contact outputs
Power consumption 4.7 Watts worst case (cold), typically 4.4 Watts loading on MVRP supplies
Size Each MVRD is 8.5 in (215.9 mm) x 11.0 in (279.4 mm), mounting within slots 1, 2, and 3 for the
Mark V control QD frame
Technology Surface-mount
Operating Temperature -30 to 65ºC (-22 to 149 ºF)

Diagnostics
The PMVD performs the following self-diagnostic tests:
that the application code loaded from flash memory is correct for the hardware set
• Monitoring for loss of communications.
Alarms are generated for the relay outputs in two ways:
• If the driver is enabled (relay turned on as in the PDIO) with the current sensing
transistor not turned on (indicating a broken connection to the TCRA), but if the core
is input only, this alarm is disabled by the ToolboxST application
• Current sensing on the supply voltage to the TCRA generates the alarm if the current
drops below 10 mA (the minimum guaranteed load for the TCRA internal circuitry in
the case where all coils are not powered).
Additional alarms are generated when detected based on:
• Verifying the reference was correctly set on the dual D/A convertors each driving half
of the comparators, where the sensed value should be within 0.25% of the setting, and
the difference is based on avoiding noise-induced alarms while verifying performance
relative to the circuitry tolerances
• Verifying the A/D operation, where the input is forced to 0 V for null test and 2.5 V
reference for a second check, if the sensed values are not within 0.1% of the setting,
an alarm is set (based on the test values being preset by 0.1% resistor divider into
a 12 bit accurate A/D)
Test points are provided on the MVRD for the following features:
• TP1 and TP2 are for forcing a reset to the hardware when shorted together
• TP3 does not exist (legacy from the TCDA)
• TP4 is an analog output, presently not used but available for engineering tests, capable
of driving a high impedance such as an oscilloscope.
Hardware self-test functions within the MVRD include:
• Feedback of test bits from the contact output shift register to the contact output status
multiplexing register, allowing for known bit patterns to be checked validating that
the shared shift register clock, load, and reset logic is functional.
• Analog voltage sensing of the DAC settings, allowing both for error checking as
well as correction for any non-linearity.

Processor LEDs
Color Label Description

Green PWR Shows the presence of control power
Green LINK Provided for each Ethernet port to indicate if a valid Ethernet connection is present
Yellow TxRx Provided for each Ethernet port to indicate when the I/O module is transmitting
or receiving data over the port
Red/Green ATTN Shows I/O module status
ATTN LED Flash Codes
LED Flashing Pattern Description
Red ATTN LED out There are no detectable problems

Solid Booting - prior to reading board ID
4 Hz 50% Diagnostic alarm active
2 Hz 50% Awaiting an IP address
1 Hz 50% No firmware to load (Program mode)
0.5 Hz 50% Application code not loaded to the I/O module
Green ATTN Solid BIOS (at power on), but if it remains in this state, the I/O module is
not functioning properly and should be replaced
2 Hz 50% Awaiting Auto-Reconfiguration release
1 Hz 50% I/O module in WAIT or STANDBY
Two 4 Hz flashes every 4 seconds Application online
MVRD LEDs
Ten LEDs are provided on the MVRD board to indicate status. These are labeled DS10
through DS1. When DS10 through DS1 are interpreted as a binary number, with DS10
the most significant bit and DS1 the least significant bit, the resulting number can be
converted to hexadecimal for easy status lookup using the following tables:
During bootup/initialization:
LED Pattern Description

(hexadecimal)
0FF Initial value (reset)
0FE Initialized Digital Input Scan
0FC Initialized Frame and SOE handler
0F8 Initialized QC mode
0F0 Voter Disagreement Detection initialized
0E0 ADL resource manager initialized

During normal operation:
DS10 Is set to indicate the health of the IONet communication with the controller.
If LINKOK is true, this LED will be lit.
DS9-DS1 Refer to the LED in the following table:
LED Pattern (hexadecimal) Description

000 Passed hardware initialization, during normal operation with no diagnostic errors. A
NO ERROR message will flash.
010 Contact input #01 failure, including force high, force low, open wire.
011 Contact input #02 failure, including force high, force low, open wire.
06F Contact input #96 failure, including force high, force low, open wire.
070 Relay output #01 failure; output state feedback does not match coil state.
071 Relay output #02 failure; output state feedback does not match coil state.
0AB Relay output #60 failure; output state feedback does not match coil state.
0B0 Plug J01 is disconnected from MVRD board to TCRA.
0B1 Plug J02 is disconnected from MVRD board to TCRA.
0B2 BATREF signal failure. Check plug for JQ on MVRD or plug J12 on DTBA.
0B3 Relays dropped due to IONET failure
0B8 MVRD, cable JR has open wires.
0B9 MVRD, cable JQ has open wires.

100 Wire fault sensed at contact input #01, must have external resistors added at switch.
101 Wire fault sensed at contact input #02, must have external resistors added at switch.
15F Wire fault sensed at contact input #96, must have external resistors added at switch.

Configuration
Note The following information is extracted from the ToolboxST application and
represents a sample of the configuration information for this board. Refer to the actual
configuration file within the ToolboxST application for specific information.
Parameter Description Choices Notes

Redundancy
I/O pack Redundancy Simplex, TMR Simplex, TMR
Physical Position
1 DTBA G1A, H1A, H2A Contact Inputs 1-46
2 DTBB G1A, H1A, H2A Contact Inputs 47-96
3 DTBC G1A, G2A Contact Outputs 1-30
4 DTBD G1A, G2A Contact Outputs 31-60
Variables Description Direction Type

L3DIAG_PMVD_x I/O diagnostic indication, Input BIT
where x=R, S, or T
LINK_OK_PMVD_x I/O link okay indication, Input BIT
where x=R, S, or T
ATTN_PMVD_x I/O Attention indication, Input BIT
where x=R, S, or T
PS18V_PMVD_x I/O 18 volt indication, where Input FLOAT
x=R, S, or T
PS28V_PMVD_x I/O 28 volt indication, where Input FLOAT
x=R, S, or T
IOPackTmvr_x I/O temperature indication, Input FLOAT
deg.F., where x=R, S, or T

Parameter Description Choices Notes
PMVD Inputs 1-46 First item listed is
default
Input This contact input is used Unused, Used
SignalInvert Inversion makes Signal True if Normal, Invert
Contact is Open
SeqOfEvents Record Contact transitions in Disable, Enable
Sequence of Events
DiagVoteEnab Enable Voting Disagreement Enable, Disable
Diagnostic
OpenWireDetection External Wire Detection Disable, Enable This option is not
present for DTBAG1A
SignalFilter Contact Input Filter in ms Zero, Ten, Twenty, Fifty, Hundred
PMVD Inputs 47-96 First item listed is

default
Input This contact input is used Unused, Used
SignalInvert Inversion makes signal true if Normal, Invert
contact is open
SeqOfEvents Record Contact transitions in Disable, Enable
Sequence of Events
DiagVoteEnab Enable Voting Disagreement Enable, Disable
Diagnostic
OpenWireDetection External Wire Detection Disable, Enable This option is not
present for DTBBG1A
SignalFilter Contact Input Filter in msec Zero, Ten, Twenty, Fifty, Hundred
Relay Feedbacks
Input This relay output is used Unused, Used
SignalInvert Inversion of Relay signal Normal, Invert
SeqOfEvents Record Relay command transitions Disable, Enable
in Sequence of Events
Output_State State of the outputs when off-line PwrDownMode, HoldLastValue,
Output_Value
Output_Value Pre-determined value for the off, on Displays only if needed.
outputs See Output_State

SOE Assignment
0 Relay Output #1
1 Relay Output #2
59 Relay Output #60

60 Relay Output Feedback #1

120 Contact Input #1
DTBA Jumper Configuration

<QDn>
6
<CD> Rev. DTBAG#A
<DD> 6, 8

BJ1 1–9 In = Connect +125 Out = Remove for testing only. Isolates the 125
V dc Interrogation Disconnect V dc positive bus from the output wiring
BJ2 10–18
voltage to contact +125 V dc to help troubleshoot ground faults on the
inputs Interrogation 125 V dc system.
BJ3 19–27 voltage from
contact inputs
BJ4 28–36
BJ5 37–46
DTBB Jumper Configuration

<QDn>
7
<CD> Rev. DTBBG#A
<DD> 7,9

BJ1 47–56 In = Connect Out = Disconnect Remove for testing only. Isolates the
contact contact positive interrogation voltage bus from
BJ2 57–66
interrogation interrogation the external wiring to help troubleshoot
BJ3 67–76 voltage from J8 voltage from J8 ground faults on the interrogation voltage
BJ4 77–86 to the individual to the individual bus system.
contact input contact input
BJ5 87–96
circuit excitation circuit excitation
terminal board terminal board
points. points.
DTBC Jumper Configuration

<QDn>
<CD> 8 Rev. DTBCG#A

Pn and Mn
1 Both In = Mark Ve control Both Out = Dry contact Always Install Jumpers in Pairs
2 supplies power to output output Install corresponding (Pn and Mn) jumpers for
3 solenoid driver output
5 circuit 8
10
11
12
13
14
15
16
17
18

DTBD Jumper Configuration
<QDn>
9
<CD> Rev. DTBDG#A
optional

Pn and Mn
1 Both In = Mark Ve Both Out = Dry contact output Always Install Jumpers in Pairs
2 control supplies power Install corresponding (Pn and Mn) jumpers for
3 to output solenoid driver output.
5 circuit 38
10
11
12
13
14
15
16

PMVD Specific Alarms
The following alarms are specific to the PMVD.
2400 - 2495
Description Contact input [ ] not responding, hardware failure
Possible Cause The input hardware internal to the PMVD has experienced a failure.
Solution Replace the PMVD.
2500 - 2595
Description Contact input [ ] wire break on wiring to external switch
Possible Cause An error in the wiring to the contact input has been detected.
Solution Check the terminal board connections and wire continuity.
2600 - 2695
Description Logic Signal [ ] Voting Mismatch
Possible Cause In a TMR application, the values for the specified signal do not agree between the R, S, and T PMVDs.
Solution
• From the ToolboxST application, verify that the R, S, and T PMVD signal values are equal.
• Check the PMVD power and networking.
• Verify that the PMVD is mounted securely to the terminal board.
• Replace the PMVD.
2700 - 2759
Description Relay coil [ ] failure, relay feedback does not match
Possible Cause Relay feedback does not match commanded state
Solution
• Clear the voter disagreements (for TMR).

• Check the PMVD connector alignment and seating.
• Check the PMVD configuration.
• Replace the terminal board.

2838
Description Hardware compatibility - Dallas ID failure
Possible Cause The Dallas ID read has failed, so verification of board type has not been successful.
2839
Description Hardware failure - contact reference circuit
Possible Cause The reference digital to analog conversion circuit that is used for the evaluation of contact inputs has
failed to yield a valid result. Contact input open/close detection may be incorrect.
2840
Description Relay board cable not installed, connector J01
Possible Cause The cable from the MVRD board to the TCRA board is not installed or functioning correctly.
Solution Replace or reseat the cable that connects the MVRD board through the J01 connector to the TCRA board.
2841
Description Relay board cable not installed, connector J02
Possible Cause The cable from the MVRD board to the TCRA board is not installed or functioning correctly.
Solution Replace or reseat the cable that connects the MVRD board through the J02 connector to the TCRA board.
2842
Description Contact Input DTBA board cable not installed, connector JQ
Possible Cause The cable from the MVRD board to the DTBA board is not installed and functioning.
Solution
• Replace or reseat the cable that connects the MVRD board through the JQ connector to the DTBA board.
• Ensure the berg jumpers on the DTBA board are installed.
2843
Description Contact Input DTBB board cable not installed, connector JR
Possible Cause The cable from the MVRD board to the DTBB board is not installed and functioning.
Solution
• Replace or reseat the cable that connects the MVRD board through the JR connector to the DTBB board.
• Ensure the berg jumpers on the DTBB board are installed.

2844
Description Unhealthy wetting voltage
Possible Cause
• Board wetting voltage is misconfigured.

• Incorrect wetting voltage has been applied.
Solution
• Verify that the board wetting voltage range is properly configured.

• Check the board wetting voltage and connections.
2845
Description Wetting voltage insufficient
Possible Cause
• Board wetting voltage is too low to support contact input open wire detection
• Board wetting voltage is too low to support contact input open ribbon detection
Solution
• Use a wetting voltage greater than 90 volts, or

• Disable contact input open wire detection for all inputs.
2846
Description Auxiliary terminal board DTBA Configuration and Hardware mismatch
Possible Cause As configured in the ToolboxST application, the specified auxiliary terminal board DTBA does not match
the installed auxiliary terminal boards connected to the MVRD through the JQ connector.
Solution
• From the ToolboxST application, Hardware tab, double-click the PMVD and verify that the HW Form for auxiliary
terminal boards DTBA and DTBB match the terminal boards that are actually installed in the core.
• Upgrade both the DTBA and DTBB auxiliary terminal boards to the newer H versions.
2847
Description Auxiliary terminal board DTBA/DTBB hardware form mismatch
Possible Cause As configured in the ToolboxST application, the specified auxiliary terminal boards DTBA and DTBB
must both have the same hardware form letter. Either both must be of type G or both must be of type H.
Solution
• From the ToolboxST application, Hardware tab, double-click the PMVD and ensure that the HW Form for auxiliary
terminal boards DTBA and DTBB match.
• Upgrade both the DTBA and the DTBB auxiliary terminal boards to the newer H versions.

2848
Description Hardware failure - DAC feedback mismatch
Possible Cause
• The analog to digital feedback used to monitor the digital to analog conversion circuit has received feedback that is
out of the expected range.
• The reference values may not be generating correctly.
• Contact input open/close detection may be incorrect.
Solution
2849
Description MVRD Power supply unhealthy
Possible Cause A feedback signal in the FPGA of the MVRD has detected a power supply unhealthy. This may
be the P15v, N15v, or P5v supply.
Solution
• Verify that the power supply connector to the MVRD from the MVRP power supply is connected properly.
• Replace the IS200MVRP power supply.


Notes

PMVP Turbine Protection I/O Module
Turbine Protection (PMVD)

The PMVP provides an interface between the IONet and the existing Mark V control
protection I/O signals. It consists of a processor board attached to a MVRE acquisition
board and an iButton identification device. Each PMVP also has its own independent
power supply.
The PMVP connects to the expansion board (TCEB) and the appropriate trip board
(TCTE, TCTG, TCTL, or TCTS) for the desired application. These boards are in turn
connected to the PTBA terminal board. The PMVP provides a visual diagnostic interface
through indicator LEDs on the MVRE.
The PMVP is the functional replacement of the Mark V control TCEA board. Three
PMVP I/O modules replace the three Mark V control TCEA boards in the core of the
Mark VIe control, Mark V migration. Even in Simplex applications, the core requires
three PMVP I/O modules for proper emergency protection of the unit.
GEH-6800_Vol_II PMVP Turbine Protection I/O Module System Guide 4-1

Installation
While performing the upgrade Ø To install the PMVPs as an upgrade to the TCEAs
from three TMR TCEAs to
1. Locate and lock out/tag out the field equipment, and isolate the power source.
the TMR PMVP modules, the
turbine will be shut down. 2. Open the P core front door and pull the two tabs at lower right and left to unlock the
plastic frames holding the boards within.
3. Lift up and tilt out the first plastic tray to expose the TCEB board.
4. If the board has a row of four transformers (square parts) at the interior (as shown in
the following figure), replace the board with the latest revision board (where the four
transformers are in a 2 x 2 array at the bottom of the board).
Early Revision TCEB Requiring Replacement to Avoid Transformer Interference
Note This is due to possible interference between the early revision’s upper
transformers and the heatsink on the MVRE board, where the large majority of TCEB
boards have no interference.
a. Disconnect and tag cables JV, JPU, JPV, JPW, JMP, JKX, JKY, JKZ, JVA, JWX,
JWY, and JWZ.
b. Remove the Rev A TCEB board from the plastic frame, releasing the plastic tabs
along the top and bottom of the board frame.
c. Install the Rev B TCEB board, with the JKX, JKY, and JKZ ribbon connectors
located close to the plastic tray pivots.
d. Reconnect the cables to the new TCEB board, keeping the same orientations and
cable paths as before.

Newer Revision DS200TCEBG1B
Cable Connections within P Core

5. For each of the front board slots, perform the following steps to replace the original
X, Y, and Z DS200TCEA protection.
a. Disconnect and tag the J7 (battery power from PDM), JK (ribbon to TCEB), JW
(335V to TCEB), JL (ribbon to trip board), and X3 (earth ground) cables.
b. Disconnect and remove the JX1 and/or JX2 cables (original RS-485 network that
is upgraded to the new Ethernet-based IONet) from the TCEA.
c. Remove the TCEA board from the plastic frame, releasing the plastic tabs along
the top and bottom of the board frame.
Original TCEA Boards Being Replaced

d.
Do not attempt to handle, remove, or secure the iButton

with the board held vertically, as the clip internal spring
will likely propel the part. If the part falls and is lost, a
replacement (GE p/n 64G2262-001A) will be needed. In
addition, the metal case on the iButton could fall into
the lower cores. If this occurs, the core would require
Caution disassembly to locate the part because it could cause the
shorting of other electronics.
On a table or other flat horizontal surface, open the packaging for the
replacement MVRE board. Locate the removable iButton ID beside the processor
daughterboard.
e. Verify that the iButton is securely held within its mounting clip (there are two
tabs at “9:00” and “3:00”).
f. Record the iButton code.
g. Install the PMVP into the plastic frame, oriented with the processor daughter
board towards the upper left side of the core.
h. Reconnect the J7, JK, JL, and X3 cables.

i. Install the following new Ethernet cables:
i. Location 1 PMVP Ethernet 1 to R switch 11 uses a red 6 foot long RJ-45
CAT 5 cable, GE p/n 336A4976ATP009
ii. Location 3 PMVP Ethernet 1 to S switch 11 uses a black 6 foot long RJ-45
iii. Location 5 PMVP Ethernet 1 to T switch 11 uses a blue 4 foot long RJ45
j. Connect the Ethernet cable onto the upper processor daughterboard’s RJ-45
connector, as shown in the following figure. Allow the cable to flow to the left
wall and down to the bottom of the slot. Spiral wrap recommended around the
cables where they exit the cores to protect against chaffing. Leave enough slack
in the cable loop to allow the movement of the frames.
Front Slot with Upgrade PMVP

6. Repeat all of step five to replace the remaining TCEA in Location 3 (<Y>) and the
TCEA in Location 5 (<Z>) with PMVPs. The new protection hardware requires a
total of three PMVP modules (X, Y, and Z).
7. Use the ToolboxST* application to download and configure the new PMVP modules.

If the configuration being downloaded contains I/O modules
with different module IDs than the configuration currently
running, the download may install incorrect firmware to some
I/O modules. If this occurs, make sure the controller is running
the new configuration, restart the entire system, and then start
Attention the ToolboxST Download Wizard again.
Operation
Processor
• Processor Board
• Processor LEDs
P Core Components
The upgraded protection core uses three PMVP I/O modules (for TMR operation) for
sensing inputs through the PTBA terminal board in combination with a trip board (TCTE,
TCTG, TCTL, or TCTS). An expansion board TCEB provided isolation transformers and
signal matching circuits.
Each PMVP contains a processor board attached to a MVRE acquisition board and a
MVIP identification device (iButton). The processor board’s field programmable gate
array (FPGA) provides the digital interfaces to the MVRE logic. The MVRE also contains
an independent power supply (BSVP), which allows the processor core to operate from
the battery feed.
The PMVP power supply provides operating voltages for the MVRE and associated trip
boards, including:
• 24 V for relay coils

• 335 V flame detector supply
• isolated 24 V for relay contacts
• local 5 V for logic analog supplies (±15 V)

MVRE Acquisition Logic
The primary trip relays (PTR1 The MVRE is a single replacement board containing the features and functionality of the
and PTR2) are controlled by Mark V control TCEA board. The MVRE provides two magnetic pickup circuits for
the MVRA. speed detection, two ac line input circuits for generator/bus frequency determination, eight
flame detection circuits, independent power supply monitoring circuits, relay outputs, and
feedback inputs. It is designed to be completely compatible with existing Mark V control
power supplies, the TCEB and TCTx boards, and PTBA terminal boards. The MVRE
communicates directly to the <Q> core through the IONet as part of the PMVP I/O module.
Emergency Trip Protective Functions

The PMVP performs the following protective functions in a mix of hardware,
programmable logic, and firmware:
• Firmware Overspeed and Overdeceleration Detection

• Additional Trip Protection
• Main Control Watchdog
• Stale Speed Detection
• Steam Turbine Trip Anticipation
• Overspeed Test Logic, Steam Turbine
• Hardware Overspeed Detection
The following sections of this document contain diagrams and descriptions that build
upon each other to present a flow into the PMVP’s Emergency Trip Relay (ETR) Logic.
Configuration parameters from within ToolboxST application, I/O point values, and
hardware sensor data are shown as functional block logic in most cases and as relay ladder
logic in others cases. The changes in presentation help to simplify some of the more
complex algorithms while providing an accurate description of the protective features
of the PMVP.
Firmware Overspeed and Overdeceleration Detection

Programmable counters are used to measure the pulses from the magnetic pickups sensing
gear teeth on two turbine shafts (high pressure and low pressure). The ToolboxST
application is used to set up the operating modes of this protection.
Firmware Overspeed Detection functions include:
• Fault on overspeed threshold match failure between configuration and signal space
values when speed is zero.
• Provide a mechanism to zero the threshold for online overspeed test.
• Provide a mechanism to modify the threshold for offline overspeed test, bounded to
limit increases to the threshold to 104%.
• Compare the threshold to the calculated speed and latch overspeed.

Additional Trip Protection
HP Zero Speed For Gas turbine applications, the PMVP offers a Zero Speed trip for
the HP shaft. The trip setpoint is 1% of the configured Base Speed setpoint with a 0.2%
hysteresis to clear.
LP Shaft Breakaway Locked For Gas turbine applications, the PMVP offers a shaft
locked trip for the LP Shaft. The trip condition will be set when the HP shaft speed is
above the configured minimum speed while the LP shaft speed is still at zero.
LP Over-acceleration Trip The PMVP offers an over-acceleration trip for the

LP shaft. Shaft speed is calculated at 2 distinct instances then used to calculate the
acceleration of the shaft. The trip condition is set if the speeds are above minimum
configured speed and the acceleration is above a configured setpoint.
Main Control Cross Trip The PMVP offers a cross trip feature which is an output I/O
signal from the Main Control that can initiate an ETR trip signal should the application
require it.

Main Control Watchdog
The classic control watchdog function will continue to be used. In this approach a value is
passed from the main control to the PMVP each data frame. If the PMVP stops receiving
the value from the main control a counter is incremented and after five data frames leads
to a trip. If the main control recovers for 60 seconds, the trip is removed. This allows for
the recovery of the main control with subsequent re-arming of the backup protection.

Stale Speed Detection
The PMVP firmware If the PMVP HP Speed is determined to be zero speed, the protection is turned off. If
implements the same above zero speed, the PMVP reads the value of speed from the main control Speed1. If
speed-based main control the current speed exactly matches the speed from the last data frame then a counter is
watchdog function that has incremented. If the counter reaches a threshold then a stale speed trip is declared and
been added to the PPRO. latched. If speeds are different the counter is cleared. This protection is based on the
knowledge that a live speed signal always “dithers” or moves some small amount. The
only way you will see consecutive signals with the same value for a period of time is if
the speed calculation or worse is not functioning in the main control. If the main control
recovers for 60 seconds the trip is removed- this allows for the recovery of the main
control with subsequent re-arming of the backup protection.

Steam Turbine Trip Anticipation
In large steam applications, a trip anticipator (TA) function is available. The overspeed
trip setpoint is reduced as the load is increased, which will reduce the turbine speed
overshoot in case of full load rejection. The PMVP determines the TA speed setpoint and
the median value is sent to the Mark VIe controller. This setpoint is confirmed to be within
a valid range, limited to high and low preset values and becomes the TA reference.
If the TA setpoint is out of range, a diagnostic alarm is generated and a fixed value of
106% is used for the TA reference. If the HP shaft scaled speed feedback signal exceeds
the TA reference, a trip is initiated. A test circuit tracks the TA speed setpoint and when
test is selected, the processor inhibits a trip then reduces the setpoint at a rate of 1% per
second until a TA trip is activated.

Overspeed Test Logic, Steam Turbine
The PMVP provides an online test feature for the overspeed logic of a steam turbine.
The logic adjusts the overspeed trip setpoints to simulate a trip condition and open the
appropriate trip relays. In the following figure, there is a second signal that initiates an
online overspeed test for HP Speed. The signal OnlineHP_Tst has the additional attribute
that it creates a 1.5 second reset pulse when it is removed.

Hardware Overspeed Detection
In addition to the Firmware Overspeed Detection algorithm, the PMVP implements an
independent hardware-based algorithm within programmable logic. This algorithm
provides an extra layer of protection in the event the firmware malfunctions.
Hardware overspeed trip functions include:
H/W OVERSPEED Setpoint • Load the independent hardware overspeed set point only when the PMVP re-boots or
is only set in the hardware at has power cycled
PMVP power on. Changes to
• Generate an alarm when the hardware configuration set point is greater than a 1
the value require a reboot or
Hertz difference from the value passed through signal space from the application
power cycle of the PMVP.
configuration
• Generate an alarm and signal space Boolean when the set point in configuration fails
to match the value stored in the hardware
• Implement speed calculation and the trip logic entirely inside programmable logic
• Overspeed response time will be < 20 ms at trip speed
Note There is no separate enable /disable signal for this Overspeed protection. The
disable signal is created by setting a high overspeed point value. The calculated speed
will never reach the value needed to trigger HWOS_TRIP.
The actual hardware implementation depends on two configuration items:
HWOS_Setpoint specifies the overspeed trip level in RPM

PRScale determines the number of speed sensor pulses per revolution used to convert
pulse rate into RPM for both hardware and firmware overspeed value

Emergency Trip Relay (ETR) Logic
The PMVP implements the ETR logic within programmable logic array of the hardware.
This approach delivers a very reliable, robust and deterministic means of tripping the
machine. The firmware aggregates its composite trip conditions and sends the result to the
programmable logic. The logic then aggregates the hard-wired trips, the HWOS, and the
FW composite trips into the main HW Trip used to control the ETRs.
This separation of trip control minimizes the impact of the slower processes within the
firmware and prevents a firmware malfunction from defeating the protection control.
Hardwired trips (L4_FB) will be connected to the PTBA terminal board in the 
protection core. These hardwired trips will de-energize the 24 V dc supply from all the
ETR and PTR relays. The PMVP will also generate a trip condition.
Composite Trips

Trip Relay Logic

Application-specific Relay Logic
The remaining relays on the Trip Boards are also controlled within programmable logic.
However, their operation changes depending upon which trip board is installed. Refer
to GEH-6800 Volume I, Mark VIe Control Migration from Mark V Control, Chapter 3
Application Specific Functions for more information.
Application-specific Example

Firmware Watchdog
Hardware in the PMVP monitors operation of the local firmware and provides a watchdog
trip function in the event of a firmware malfunction. The operation of this watchdog does
not show up in the normal sequencing figures. The PMVP hardware is designed to be in a
fail-safe or trip mode if it is not properly configured and operating. This means that with
power off, while starting up, when in a hardware reset, or otherwise not online, the pack
will vote to trip. If the pack watchdog acts, it will reset the hardware thereby generating a
vote to trip. The processor board used inside the I/O pack has hardware features that allow
it to differentiate between a reset caused by the watchdog hardware and a reset caused by
cycling of power. This information is available from the pack after it re-starts. In the event
that a pack votes to trip due to a reset, it is then possible to determine if a watchdog reset
or a cycling of control power caused the event.
Synchronization
The P core has two potential transformer inputs that are converted to pulses by zero
crossing circuits and measured with two counter/timer channels. Speed from the magnetic
sensors and voltage is then compared with a dual rate algorithm to match the turbine
generator shaft speed to the grid frequency. A slow rate is used for small differences in
speed (to avoid overshoot) while the fast rate allows a quicker match in speed.
The P core firmware uses the speed readings within a control sequence program to
perform the following steps:
• Confirm permissives with under and over voltage and frequency limits on both
the generator and the grid, as well as voltage differences between the grid and the
generator
• Monitor a contact on the power circuit breaker (ANSI designation 52G) to measure
the time taken to close the breaker, with a self-adaptive adjustment used to anticipate
the closure time
• Confirm RST permission through command sequence or contact 25P, RST permission
by sync check 25X, and automatic sync signal from the P core firmware
• External permissions including auto sync selection, field breaker state, lack of sync
inhibits, turbine startup complete, and unit at approximate sync speed

Generator Sync Check

Generator Auto Sync

Flame Detection
Gas turbines use flame detectors to monitor the combustion chamber, where the detectors
detect the UV radiation within the flame. The normal output from the energized detector
is a pulsing voltage related to the intensity of the flame. The P core senses the flame
detectors by monitoring the frequency of pulses resulting from a threshold circuit.
Configuration of the detectors involves the pulse thresholds (relative to a 62.5 millisecond
window). Results of the detection are passed to the RST cores through the IONet.
Diagnostics from this circuit/firmware include a check to determine if the LP shaft is at
zero speed and the flame detection is above 2 Hz (LED patterns 250-257 hex for the 8
channels) and voltage checks on the 335 V supply to the flame detectors (LED pattern
24E hex).
Eight flame detectors connect to the PMVP are powered by TMR fed P335V from the
MVRE through the TCEB. The signals are sensed for fluctuations (sparking) with counters
within the MVRE’s FPGA. The following figure shows the signal flow within the core in
the original Mark V implementation (MVRE replaces the TCEA).
Flame Detector Circuit Flow
The MVRE uses separate diodes to perform the function of a high-speed clamp, limiting
the signal between 0 and 5 V. The eight separate flame detector inputs are diode clamped
and then digitized to provide a pulse train to the counters within the processor board's
FPGA.

Shaft and Grid Sensing
The turbine system has six sensors, with two each passed to one of the three MVREs
within the core. The two magnetic pickups to each MVRE are sensed for shaft speed, with
the sensor signals ac coupled, magnified, and clipped to drive counters within the MVRE’s
FPGA. The PBTA terminal board provides MOV protection, with the signals passed
directly through the TCEB to the MVRE.
Analog Sensing for Internal Voltage Diagnostics

Absolute voltage values may The internal power supply is monitored for correct output voltages and ground reference.
alter with design evolution to The following eight channels are used for sensing:
lower power parts.
1. Sensing the local logic supply (0 to 3.6 V range with 3.3 V typical)
2. Sensing the analog positive supply (0 to 16.5 V with 15 V typical)
3. Sensing the analog negative supply (0 to -16.5 V with -15 V typical, requires an
additional op amp for inversion)
4. Sensing the isolated 24 V supply positive rail (resistor centered to common, buffered
with 0 to 24 V range, typically 12 V with no external ground faults)
5. Sensing the isolated 24 V supply negative rail (resistor centered to common, inverted
with 0 to -24 V range, typically 12 V with no external ground faults)
6. Sensing the local 24 V supply (0 to 30 V with 24 V typical)
7. Sensing the flame detector output voltage (0 to 360 V with 335 V typical)
8. Sensing the 28 V supply to the daughterboard (0 to 33 V with 28 V typical)
Mag Sensor and Ac Inputs

The magnetic sensors inputs have varying frequency and voltage level signals from the
gear tooth sensors. Input voltages are ranging from a low of 0.03 volts to a maximum of
200 Vpp for a frequency range of 2 to 10000 Hz. The pulses are counted by logic within
the FPGA on the MVRE. The following figure displays how the inputs from the sensors
flow through the PTBA, through the TCEB, and to the MVRE, with a parallel connection
to the TCQC board within the RST cores.

Emergency Overspeed Pickup Wiring in the P Core

Power Supply
The PMVP has several power supplies for internal use, driven from the 125 V battery feed
for the trip board resources at a peak load of 73 Watts. The following table lists the loads
within the core as well as the anticipated dc/dc efficiencies (minimum) and supply loads.
MVRE Supply Volts (Absol.) Load (Amps) dc/dc Eff. Power in Watts 125 feeds Trip P28 feeds
Circuitry MVRE Circuitry
P15 15 0.05 80% 0.94 0.00 0.94
N15 15 0.05 80% 0.94 0.00 0.94
P335 335 0.005 43% 3.90 0.00 3.90
P24A 24 1.2 80% 36.00 36.00 0.00
P24 24 1 80% 30.00 30.00 0.00
P5 5 1 80% 6.25 6.25 0.00
bppb 28 0.25 100% 7.00 0.00 7.00
Power Consumption for Concept 85.02 72.25 12.77
The P28 supply passes through a common mode filter (equivalent to that on the processor
board) for supply protection to surge and EMI/EMC. The internal dc/dc uses a 2 W
half-bridge driver to a small (2 W) transformer, in turn generating the P15 and N15 used
by the analog circuitry. The P335 supply uses an isolated region to keep noise from
entering the circuit board planes. A second dc/dc half bridge driver (rated at a 75 W load)
runs off of the 125 V battery, and generates the following through a transformer:
P24A and N24A are resistor • The trip board’s P24V at 1A with respect to PCOM (Relay Coil Supply)
centered with respect to DCOM
• A floating P24A at 1.2 A with respect to N24A (Trip Contact Loads)
and monitored for ground
faults. • P5 at 1A with respect to DCOM (Trip Driver Logic)
Three independent power supplies provide local power to the three MVREs as well as
power to the trip and expansion boards using triple modular redundancy. In this way, a
supply failure only affects one MVRE with the other two MVREs continuing to provide
protection. The following supply voltages are isolated from the incoming battery source
of 125 V nominal (80 to 145 V):
• Local logic supply is 3.3 V from either the processor board local regulated output (up
to 300 mA drawn) or as a separate output from the MVRE supply
• The external logic supply for 5 V ±5% at 1 A for the TCTx trip board is through JL-49.
The actual load is estimated at under 100 mA based on known trip board circuitry.
• Local analog supply with ±15 V at 50 mA for the comparators and other analog
components on the MVRE
• Local relay supply with 24 V at 1 A for the TCTx relay coils
The resistor network on • The external isolated contact supply for the TCTx outputs is - 21 to 30 volts
diagnostics is used to center differential at up to 1.2 amps continuous, 1.5 amps surge. Current limiting (or
w/r DCOM and to detect trip or foldback in the event of a shorted output) is provided. This supply is through JL-44,
cabling ground faults. JL-50.
• External high voltage P335 with isolation is 303 to 350 V dc at 3 mA load, zener
clamped, with an active current limit of 7 mA.

Specifications
Item Description
Supply 125 V dc for PMVP, 125 V for TCTx
Processing Rate 1 ms interrupt
Magnetic Pickups Two circuits into counters, evaluated every 2-3 ms
Relay Drivers 7 drivers with sensing of drive current
Generator Volt, Phase Magnitude alarm, timing sensing on 1 ms
Bus Volt, Phase Magnitude alarm, timing sense on 1 ms
Breaker Close n/a
Shaft Voltages n/a
Flame Detection Every 40 ms
Temperature -30 to 65°C (-22 to 149 °F)
Technology Surface mount
Diagnostics
The PMVP performs the following self-diagnostic tests:
• L3BKR_GXS – the Sync Check Relay is Slow
• L3BKR_GES – the Auto Sync Relay is Slow
• Breaker #1 Slower than Adjustment Limit Allows
• Breaker #2 Slower than Adjustment Limit Allows
• Synchronization Trouble
that the application code loaded from flash memory is correct for the hardware set.
• Diagnostic information includes status of the solenoid relay driver, contact, high
and low flame detector voltage, and the sync relays. If any one of the signals goes
unhealthy a composite diagnostic alarm occurs.
The diagnostic signals can be individually latched, and then reset with the RESET_DIA
signal after they go healthy. Details of the individual diagnostics are available from the
ToolboxST application.
There are several groups of signals sensed for trip diagnostics and settings:
• 7 of relay driver sensing, with the feedback signals set if the driver is enabled
• 40 of trip diagnostics, board ID, and magnitude alarms for the generator and bus
ac inputs

The input circuitry for logic signals has additional signals routed through the multiplexors,
such that an internal test signal can be sensed. This allows a background test to operate,
forcing a known logic signal to occur every scan to detect if the multiplexing logic has
any control signals stuck high or low. The inputs are scanned every millisecond, with the
data placed into holding buffers for the processor to read.
The MVRE’s FPGA provides drivers for serial to parallel shift registers, used to generate
internal self-test signals as well as LED controls. The self-test signals are passed to the
input multiplexers, allowing known signals to be sensed at each group of inputs as a
verification of the scanning hardware.

Configuration
Note The following information is extracted from the ToolboxST application and
represents a sample of the configuration information for this board. Refer to the actual
configuration file within the ToolboxST application for specific information.
Parameters Description Choices

TripAnticipate For Steam Turbines, enables the Trip Anticipation Algorithm Disable, Enable
SimplexMainControl Enables Simplex algorithms when connected to Simplex Disable, Enable
Main Control
ContWDogEn Enables Trip on loss of outputs from Main Control Outputs Disable, Enable
StaleSpdEn Enables Trip on Frozen Speed from Main Control Disable, Enable
HP Pulse Rate
PulseRate Enables HP Pulse Rate monitor Unused, Used
BaseSpeed 100% rated speed setpoint in Hertz 0 - 12000
OS_SetPoint Firmware Overspeed Trip setpoint in Hertz 0 - 12000
HWOS_SetPoint Hardware Overspeed Trip setpoint in Hertz 0 - 12000
PR_Scale Pulses per revolution used for RPM-Hertz conversions 0 - 1000
TMR_DiffLimit TMR Voting difference in Percent 0 - 100
LP Pulse Rate
PulseRate Enables LP Pulse Rate monitor Unused, Used
BaseSpeed 100% rated speed setpoint in Hertz 0 - 12000
OS_SetPoint Firmware Overspeed Trip setpoint in Hertz 0 - 12000
HWOS_SetPoint Hardware Overspeed Trip setpoint in Hertz 0 - 12000
PR_Scale Pulses per revolution used for RPM-Hertz conversions 0 - 1000
AccelTripEnable Enables Acceleration Trip algorithm Disable, Enable
AccelTripSetpoint Acceleration Trip Setpoint in Hz/sec 0 - 32767
AccelTripBeginSetpoint Starting Speed setpoint for calculating acceleration in Hz 0 - 12000
HP BreakAway Ratio HP Speed setpoint at which to check for LP shaft turning 0 - 100
in Percent
NumLPIntsBtwnCheck Teeth Groups between acceleration computations - 1 Group 0 - 15
= 8 teeth
NumIntsForSpdCalc Teeth Groups to average acceleration speed across - 1 0 - 15
Group = 8 teeth

Gen-Breaker
SystemFreq The System Frequency in Hertz 60Hz, 50Hz
Brkr1SelfAdapt Enables adaptive close time calculations Disable, Enable
Brkr1DiagEnable Enables diagnostic alarm if associated Breaker Close Time Disable, Enable
does not meet spec
Brkr1VoltDiagEnable Enables diagnostic alarm if 125 V dc has problem Disable, Enable
Brkr1CloseTime The anticipated time required to close the Breaker, in Cycles 0 - 255
Brkr1AdaptLimit The maximum amount of adaptive close time compensation 0 - 255
allowed
Brkr1DiagVoteEnab Enables Voting Disagreement Diagnostic detection Enable, Disable
Brkr2SelfAdapt Enables adaptive close time calculations Disable, Enable
Brkr2DiagEnable Enables diagnostic alarm if associated Breaker Close Time Disable, Enable
does not meet spec
Brkr2VoltDiagEnable Enables diagnostic alarm if 125 V dc has problem Disable, Enable
Brkr2CloseTime The anticipated time required to close the Breaker, in Cycles 0 - 255
Brkr2AdaptLimit The maximum amount of adaptive close time compensation 0 - 255
allowed
Brkr2DiagVoteEnab Enables Voting Disagreement Diagnostic detection Enable, Disable
Gen-Bus
Usage Condition of Input Unused, Used
Flame
FlameDet Enables Flame Detection monitor Unused, Used
FlameLimitLo Flame Threshold LimitLo (LOW detection counts means HIGH 0 - 255
sensitivity)
FlameLimitHi Flame Threshold LimitHI (HI detection counts means LOW 0 - 255
sensitivity)
TMR_DiffLimt TMR Input Vote Difference, in Hertz 0 - 160
Relay Feedbacks
Input Condition of Input Unused, Used

SignalInvert Enables Signal Inversion, Invert makes Signal True if Contact Normal, Invert
is Open
SeqOfEvents Enables SOE, SOE records transitions as Sequence of Events Disable, Enable
in 1ms resolution
DiagVoteEnab Enables Voting Disagreement Diagnostic detection Enable, Disable

ESTOP
Input Condition of Input Unused, Used
SignalInvert Enables Signal Inversion, Invert makes Normal, Invert
Signal True if Contact is Open
DiagVoteEnab Enables Voting Disagreement Enable, Disable
Diagnostic detection
Relays
RelayOutput Condition of Output Unused, Used

PMVP Specific Alarms
The following alarms are specific to the PMVP module.
32
Description HP Overspeed firmware setpoint configuration error
Possible Cause There is a HP firmware overspeed limit mismatch between the I/O signal space limit and the configuration
setpoint. The current configuration file downloaded from the ToolboxST application has a different overspeed limit than the
I/O signal HP OS_Setpoint.
Solution From the Component Editor, Hardware tab, PMVP, Speed tab, match the output signal designated in
HP_OSSetpoint to with the configuration value of OS_Setpoint (found in the HP Pulse Rate tab).
33
Description HP Overspeed hardware setpoint configuration error
Possible Cause There is a HP hardware overspeed limit mismatch between the I/O signal space limit and the configuration
setpoint. The current configuration file downloaded from the ToolboxST application has a different overspeed limit than
the I/O signal HP_HWOS_Setpt.
HP_HWOS_Setpt with the configuration value of HWOS_SetPoint (found in the HP Pulse Rate tab).
34
Description HP Overspeed hardware setpoint changed after power on
Possible Cause This alarm always occurs when HP Pulse Rate HWOS_Setpoint or PR_Scale is changed and downloaded
to the PMVP after the module has been powered.
Solution Confirm that the limit change is correct, then restart the PMVP to re-initialize the hardware overspeed limit.
35
Description LP Overspeed firmware setpoint configuration error
Possible Cause There is an LP firmware overspeed limit mismatch between the I/O signal space limit and the
configuration setpoint. The current configuration file downloaded from the ToolboxST application has a different overspeed
limit than the I/O signal LP OS_Setpoint.
LP_OSSetpoint with the configuration value of OS_Setpoint (found in the LP Pulse Rate tab).

36
Description LP Overspeed hardware setpoint configuration error
Possible Cause There is a LP hardware overspeed limit mismatch between the I/O signal space limit and the configuration
setpoint. The current configuration file downloaded from the ToolboxST application has a different overspeed limit than
the I/O signal LP_HWOS_Setpoint.
LP_HWOS_Setpt with the configuration value of HWOS_Setpoint (found in the LP Pulse Rate tab).
37
Description LP Overspeed hardware setpoint changed after power on
Possible Cause This alarm always occurs when HP Pulse Rate HWOS_Setpoint or PR_Scale is changed and downloaded
to the PMVP after the module has been powered
Solution Confirm that the limit change is correct, then restart the PMVP to re-initialize the hardware overspeed limit.
38
Description Control Watchdog Protection Activated
Possible Cause This alarm only occurs if the parameter ContWdogEn has been enabled, and it indicates that the ContWdog
variable has not changed for five consecutive frames. The alarm clears if the variable continues to change for 60 seconds.
Solution Verify that the ContWdog is set up correctly in the ToolboxST application, and that the source of the signal
is changing the value at least once a frame.
39
Description Stale Speed Protection Activated
Possible Cause This alarm can only occur if the parameter StaleSpdEn has been enabled, and it indicates that the
MainCtrl_HP_Spd variable has not changed for 100 consecutive frames. The alarm clears if the speed dithers for 60 seconds.
Solution Verify that the MainCtrl_HP_Spd signal is set up correctly in the ToolboxST application, and that the source of
the signal reflects the primary (PMVE, MVRA) pulse rate speed.

50
Description Invalid trip board system configuration, Configured=[ ] Attached=[ ]
Possible Cause
• There is a discrepancy between the I/O configuration and the actual hardware trip board TCTx. The trip board must
be as follows:
Gas Turbine = TCTG (4)
Medium steam turbine = TCTS (2)
Large steam turbine = TCTL (6)
Extended large steam = TCTE (3)
• There may also be poor connectivity in cable JL.
Solution
• Check the I/O configuration against the hardware (trip board) in [P] slot 4.
• Check the cable on connector JL.
51
Description Digital output, 025DRV
Possible Cause The relay driver circuitry associated with relay 25 (K3) is faulty.
Solution
• Check the cabling on the MVRE JL.

• If there are no problems with the cabling, replace the MVRE.
52
Description Digital output, 0ETR1
Possible Cause The relay driver circuitry associated with relay ETR1 is faulty. The relationship is:
Relay Gas, TCTG MED STM, TCTS LG STM, TCTL LG STM, TCTE
ETR1 [X] K5 K11 K4 K11

ETR1 [Z] K6 K13 K6 K13
Solution


53
Description Digital output, 0ETR2
Possible Cause The relay driver circuitry associated with relay ETR2 is faulty. The relationship is:
Relay Gas, MED STM, TCTS LG STM, TCTL LG STM, TCTE

TCTG
ETR2 [X] K8 K10 K10 K10
ETR2 [Y K7 K4 K11 K4
ETR2 [Z]] K9 K12 K12 K12
Solution

54
Description Digital output, 0DRV0 (clamp)
Possible Cause The relay driver circuitry associated with the servo clamping function of the circuit 0DRV0 is faulty.
Solution

• If there is no problem with the cabling, replace the MVRE.
55
Description Digital output, 0DRV1 (KE1,ELO)
Possible Cause The relay driver circuitry associated with circuit 0DRV1 is faulty.
• On large steam turbines, this is the ELO, K19 (electrical lockout).

• On medium steam turbines, this is the KE1, K19 (emergency trip bypass test 1).
• On gas turbines, this circuit is not used.
Solution


56
Description Digital output, 0DRV2 (KE2)
Possible Cause The relay driver circuitry associated with circuit 0DRV2 is faulty.
• On large steam turbines, this circuit is not used.

• On medium steam turbines, this is the KE2, K18 (emergency trip bypass test 2).
• On gas turbines, this circuit is not used.
Solution

57
Description Digital output, 0ALARM
Possible Cause The alarm (horn) on the TCEB board, connected through the PTBA jumper AL_E and the trip board
TCTx, has lost at least one of its three inputs and may not function (2/3 voting may override the problem).
Solution

58
Description TMR check trouble, ETR1
Possible Cause
• The feedbacks of the three ETR1 relays do not agree.

• If an ETR1 relay driver diagnostic alarm is not also indicated, there may be a problem with the trip board TCTx.
Solution
• If present, determine which ETR1 is faulty by looking at the corresponding vote exchange diagnostic message.
• Use the following table to verify that the corresponding ETR1 relay is not loose.
ETR1 [X] K5 K11 K4 K11
ETR1 [Z] K6 K13 K6 K13
• Check the cabling on the MVRE [X] JL-4, [Y] JL-3, [Z] JL-5.
• Replace the TCTx trip board.

59
Description TMR check trouble, ETR2
Possible Cause
• The feedbacks of the three ETR2 relays do not agree

• If an ETR2 relay driver diagnostic alarm is not also indicated, there may be a problem with the trip board TCTx.
Solution
• If present, determine which ETR2 is faulty by looking at the corresponding vote exchange diagnostic message.
• Use the following table to verify that the corresponding ETR2 relay is not loose.

TCTG
ETR2 [X] K8 K10 K10 K10
ETR2 [Y K7 K4 K11 K4
ETR2 [Z] K9 K12 K12 K12
• Check the cabling on the MVRE [X] JL-7; [Y] JL-6; [Z] JL-8.
60
Description TMR check trouble, PTR1
Possible Cause The three PTR1 relays do not agree, therefore, one is faulty.
• The feedbacks of the three PTR1 relays do not agree.

• If a PTR1 relay driver RD2 failure diagnostic is not also indicated, there may be a problem with the trip board TCTx.
Solution
• If present, determine which PTR1 is faulty by looking at the corresponding vote exchange diagnostic message.
• Use the following table to verify that the PTR1 relay is not loose.
relay Gas, TCTG MED STM, TCTS LG STM, TCTL LG STM, TCTE
PTR1 [X] K13 K7 K7 K7
PTR1 [Y] K14 K8 K8 K8
PTR1 [Z] K15 K9 K9 K9
• Check the cabling on the MVRE [R] JL-9, [S] JL-10, [T] JL-11.

• If the problem persists, replace the appropriate TCQA.

61
Possible Cause

Solution

TCTG
PTR2 [X] K19 K15 K15 K15
PTR2 [Y] K20 K16 K16 K16
PTR2 [Z] K21 K17 K17 K17

62
Possible Cause

Solution
Relay Gas, TCTG Steam, TCTE

PTR3 [R] K10 K19
PTR3 [S] K11 K20
PTR3 [T] K12 K21


63
Description TMR check trouble, PTR4 or ETR3
Possible Cause
• The three PTR4 or ETR3 relays do not agree.

• If a PTR4/ETR3 relay driver RD5 failure diagnostic is not also indicated, there may be a problem with the trip board TCTx.
Solution
• If present, determine which PTR4/ETR3 is faulty by looking at the corresponding vote exchange diagnostic message.
• Use the following table to verify that the PTR4/ETR3 relay is not loose.
Gas, TCTG Steam, TCTE

PTR4 [R] K16 ETR3 [R] K14
PTR4 [S] K17 ETR3 [S] K6
PTR4 [T] K18 ETR3 [T] K18

64
Description Loopback, relay, ETR1
Possible Cause
• The feedback of a ETR1 contact disagrees with the required or intended state of this particular relay.
Note The [Z] (MVRE) board only checks the ETR1 relay driven by itself. The same is true for the [X] and [Y] MVREs.
• If a 0ETR1 digital output diagnostic is not also indicated, there may be a problem with the trip board TCTx.
Solution
• Use the following table to verify that the ETR1 relay is not loose.
Relay Gas, TCTG MED STM, LG STM, TCTL LG STM, TCTE

TCTS
ETR1 [X] K5 K11 K4 K11
ETR1 [Z] K6 K13 K6 K13

65
Description Loopback, relay, ETR2
Possible Cause
• The feedback of a ETR2 contact disagrees with the required or intended state of this particular relay.
Note The [Z] (MVRE) board only checks the ETR2 relay driven by itself. The same is true for the [X] and [Y] MVREs.
• If a 0ETR2 digital output diagnostic is not also indicated, there may be a problem with the trip board TCTx.
Solution
• Use the following table to verify that the ETR2 relay is not loose.
Relay Gas, TCTG MED STM, LG STM, TCTL LG STM, TCTE

TCTS
ETR2 [X] K8 K10 K10 K10
ETR2 [Y] K7 K4 K11 K4
ETR2 [Z] K9 K12 K12 K14
66
Description Loopback, relay, DRV1
Possible Cause
• The feedback of a relay contact disagrees with the required or intended state of this particular relay.
− On medium steam turbines (TCTS), this is the KE1 (emergency trip bypass)
− On large steam turbines (TCTL), this is the ELO (electrical lockout).
− It is not used on the gas Turbines (TCTG).
Note There is only one relay in this circuit, the voting is done at the logic level, as opposed to the relay contact level.
• If a 0DRV1 digital output diagnostic is not also indicated, there may be a problem with the trip board TCTx.
Solution
• Verify that the K19 relay is not loose.

• Check the MVRE JL-15 cable continuity.
• Replace the MVRE.

67
Description Loopback, relay, DRV2
Possible Cause
• The feedback of a relay contact disagrees with the required or intended state of this particular relay.
− On medium steam turbines (TCTS), this is the KE2 (emergency trip bypass).
− It is not used on large steam (TCTL) or gas turbines (TCTG).
Note There is only one relay in this circuit; the voting is done at the logic level, as opposed to the relay contact level.
• If a 0DRV2 digital output diagnostic is not also indicated, there may be a problem with the trip board TCTx.
Solution

• Check the MVRE JL-16 cable continuity.
68
Description Loopback, relay, PTR1
Possible Cause ;
• The feedback of a PTR1 contact disagrees with the required or intended state of this particular relay.
Note The MVRE [Z] board only checks the PTR1 relay driven by [T] TCQA. There is a similar partnership between [X]
and [R] MVREs, and [Y] and [S] TCQAs .
• Either a PTR1 relay driver RD2 failure diagnostic or a PTR1 TMR check trouble diagnostic should be indicated. If
not, there may be a problem with the TCTx trip board.
Solution
PTR1 [R] K13 K7 K7 K7
PTR1 [S] K14 K8 K8 K8
PTR1 [T] K15 K9 K9 K9

• If a problem still exists, replace the appropriate TCQA.

69
Description Loopback, relay, PTR2
Possible Cause
• The feedback of a PTR2 contact disagrees with the required or intended state of this particular relay.
Note The MVRE [Z] board only checks the PTR2 relay driven by [T] TCQA. There is a similar partnership between [X]
and [R] MVREs, and [Y] and [S] TCQAs .
• Either a PTR2 relay driver RD3 failure diagnostic or a PTR2 TMR check trouble diagnostic should be indicated. If
Solution
PTR2 [R] K19 K15 K15 K15
PTR2 [S] K20 K16 K16 K16
PTR2 [T] K21 K17 K17 K17


70
Description Loopback, relay, KP-1/PTR3/MLO
Possible Cause
• The feedback of a KP-1/PTR3/MLO relay contact disagrees with the required or intended state of this particular relay.
− KP-1 (k6) is used on medium steam turbines.
− PTR3(k10, k11, k12) are used on gas turbines.
− MLO (k13) is used on large steam turbines.
− PTR3 (k19, k20, k21) are used on Extended Large Steam.
Note On gas and extended large steam turbines, the [Z] MVRE board only checks the PTR3 relay driven by [T] TCQA.
There is a similar partnership between [X] and [Y] MVREs, and [R] and [S] TCQAs.
• Either a PTR3 relay driver RD4 failure diagnostic, or a PTR3 TMR check trouble diagnostic should be indicated. If
Solution
• Verify that the appropriate relay is not loose.


71
Description Loopback, relay, KP-2/PTR4/ORST
Possible Cause
• The feedback of a KP-2/PTR4/ORST relay contact disagrees with the required or intended state of this particular relay.
− KP-2 (k14) is used on medium steam turbines.
− PTR3(k16, k17, k18) are used on gas turbines.
− MLO (k14) is used on large steam turbines.
Note On gas turbines, the [Z] MVRE board only checks the PTR4 relay driven by [T] TCQA. There is a similar
partnership between [X] and [Y] MVREs, and the [R] and [S] TCQAs.
• if a Logic Signal [ ] Voting Mismatch alarm is not also displaying, there may be a problem with the trip board TCTx.
Solution
• Verify that the applicable relay is not loose.

• Check the cabling on the MVRE [X] JL-18, [Y] JL-19, [Z] JL-20 for gas turbines, or JL-16 for medium steam, or JL-17
for large steam turbines.
• Replace the MVRE

• If a problem still exits, replace the appropriate TCQA.

72
Description Loopback, Relay, OTS
Possible Cause
• This is applicable to large steam turbines only. The OTS (k18) relay contact disagrees with the required or intended
position of this particular relay.
• If a Voting Mismatch alarm is not also displaying, there may be a problem with the trip board TCTx.
Solution

• Check the cabling on the MVRE JL-18.

73
Description Loopback, solenoid, ETD1/SOL1/MTSV
Possible Cause This diagnostic is checking a composite function (one made up of more than one relay).
• If other diagnostics associated with these relays display, they should be resolved first.
• This diagnostic is True when the feedback signal, indicating actual voltage applied to the trip solenoid coil, disagrees with
the required or intended value for this solenoid as shown in the following table.
ETD1 Med Steam, TCTS – elect trip device

eqn is ETD1=(ETR1 OR KE1) AND (PTR1 OR KP1)
SOL1 Gas Turb, TCTG – solenoid #1
eqn is SOL1=(ETR1 and PTR1)
MTSV Large Steam, TCTL – mech Trip sol valve.
eqn is MTSV=((not ETR1) or (not PTR1)or L5E)
ETD1 Extended Large Steam, TCTE – elect trip device
eqn is ETD1=(ETR1 and PTR1)
Note This checkpoint is downstream of the TMR hardware, after the hardware has necked down to a single circuit.
• If all three MVRE boards are reporting this, there may be a problem with one of the following items:
− Trip board TCTx
− Power cable J7W
− Wiring on the output screws of the PTBA
• If only one processor board reports this, there may be a problem with the detection circuitry (for example, the cable
JL, TCTx, or the MVRE).
Solution
• If present, resolve other diagnostic alarms associated with this relay.

• Check power cables and terminal board screws.

74
Description Loopback, solenoid, ETD2/SOL2/ETSV
Possible Cause This diagnostic is checking a composite function (one made up of more than one relay).
• This diagnostic is True when the feedback signal, indicating actual voltage applied to the trip solenoid coil, disagrees with
the required or intended value for this solenoid as shown in the following table.
ETD2 Med Steam, TCTS – elect trip device

eqn is ETD2=(ETR2 OR KE2) AND (PTR2 OR KP2)
ETSV Large Steam, TCTL – elect Trip sol valve
eqn is ETSV=(ETR2 and PTR2)
ETD2 Extended Large Steam, TCTE – elect trip device
eqn is ETD2=(ETR2 and PTR2)
• If all three MVRE boards are reporting this, there may be a problem with one of the following items:
− Trip board TCTx
− Power cable J7W
− Wiring on the output screws of the PTBA
• If only one processor board reports this, there may be a problem with the detection circuitry (for example, the cable JL,
trip board TCTx, or the MVRE).
Solution


75
Description Loopback, solenoid, SOL3/ELO
Possible Cause This diagnostic is checking a composite function for gas turbines, nothing for medium steam, and a
single relay for large steam.
• This diagnostic is True when the feedback signal, indicating actual voltage applied to the solenoid coil, disagrees with the
required or intended value for this solenoid as shown in the following table.

ELO Large Steam, TCTL – elect Lockout valve
eqn is ELO = relay ELO

ETSV Extended Large Steam, TCTE
eqn is ETSV=(ETR3 and PTR3)
• If all three MVRE boards are reporting this alarm, there may be a problem with one of the following items.
− Gas turbine: the trip board TCTG, the power cable J7W, or wiring problems on the PTBA output screws
− Large steam: the trip board TCTL, the power cable J18 (ac power), or wiring problems on the PTBA output screws
• If only one processor board reports the problem, the problem may be with the detection circuitry (for example, JL
cable, trip board TCTx, or MVRE).
Solution


76
Description Loopback, solenoid, SOL4/MLO
Possible Cause This diagnostic is checking a composite function for gas turbines, nothing for medium steam, and a
single relay for large steam.
required or intended value for this solenoid as shown in the following table.

eqn is SOL4 = (ETR2 and PTR4)
MLO Large Steam, TCTL – mech Lockout valve
eqn is MLO = relay MLO
• If all three MVRE boards are reporting this alarm, there may be a problem with one of the following items.
− Gas turbines: the trip board TCTx, the power cable J7W, or wiring problems on the PTBA output screws.
− Large steam: the trip board TCTx, the power cable J18 (AC power), or wiring problems on the PTBA output screws.
• If only one processor board reports this, the problem may be with the detection circuitry (for example, JL cable, trip
board TCTx, or MVRE).
Solution


77
Description Loopback, solenoid, ORST
Possible Cause This diagnostic is for large steam turbines only.
• If other diagnostics associated with this function display, they should be resolved first.
required or intended value for this solenoid. This checkpoint is downstream of the TMR hardware, after the hardware has
necked down to a single circuit.
• If all three MVRE boards are reporting this, there may be a problem with the trip board TCTx, the power cable J18 (ac
power), or wiring problems on the output PTBA screws.
Solution

78
Description Loopback, solenoid, OTS
Possible Cause This diagnostic is for large steam turbines only.
• If other diagnostics associated with this function display, they should be resolved first.
required or intended value for this solenoid. This checkpoint is downstream of the TMR hardware, after the hardware has
necked down to a single circuit.
• If all three MVRE boards are reporting this, there may be a problem with the trip board TCTx, the power cable J18 (ac
power), or wiring problems on the output PTBA screws.
Solution


79
Description Slow synch 25 relay
Possible Cause This is an unused diagnostic alarm.
Solution Reset all diagnostic alarms.
80
Description Slow synch check 25X relay
Possible Cause
• The synch check relay, L25X (sometimes designated L25A), is not activated when the synch relay L25 activates. This
synch check relay should always be activated and be out of the way when the synch relay activates.
• The synch relay hardware identifications are as follows:
− L25 – synch relay, k3
− L25X – synch check relay, k2
− L25P – synch relay, k1
Solution
• If L25X is not activating, check the CSP sequencing.

• Verify that the L25X_PERM coil is being driven with correct logic. L25X_PERM must be set to True before L25X
activates. It is also required that the turbine speed be simulated if not doing an actual startup.
• If L25X is activating slowly (as opposed to not activating), check the following system parameters.
− Configured phase for L25X
− Breaker close time
− Slip when the breaker is being closed
81
Description Synch lockup, 25 relay failure
Possible Cause
• The synch check relay L25 is activated when it is supposed to be inactive.

− L25 – synch relay, k3
− L25X – synch check relay, k2
− L25P – synch relay, k1
• If reported by all three processors, there may be a problem with the trip board TCTx.
• Problem with the detection circuit (JL cable, MVRE, or trip board TCTx)
Solution


82
Description Breaker 1 close time out of limits
Possible Cause
• The measured time for breaker #1 to close on the last synch operation was outside the limits as defined by the following
eqn.
[(Config Bkr close time) - (Config limit)] < [measured bkr close time] < [(Config Bkr close time)+(Config limit)].
• If reported by all three processors, there may be a problem with the generator breaker contact (required interconnection)
to the PTBA termination board, or cabling JM.
• If only reported by one processor, it may be the MVRE or cabling JL.
Solution
• Verify that the generator breaker does not have an excessive closure time.
• Extend the allowable configured limit; it may be too tight.
• Check the generator breaker contact and cabling JM.
83
Description Breaker 2 close time out of limits
Possible Cause
• The measured time for breaker #2 to close on the last synch operation was outside the limits as defined by the following
eqn.
[(Config Bkr close time) - (Config limit)] < [measured bkr close time] < [(Config Bkr close time)+(Config limit)].
• If reported by all three processors, there may be a problem with the generator breaker contact (required interconnection)
to the PTBA termination board, or cabling JM.
• If only reported by one processor, it may be the MVRE or cabling JL.
Solution
• Verify that the generator breaker does not have an excessive closure time.
• Extend the allowable configured limit, it may be too tight.
• Check the generator breaker contact and cabling JM.

84
Description 25P trouble
Possible Cause This is a loopback test on relay L25P, k1 on TCTx.
• The feedback of P (synch permissive relay) contact disagrees with the required or intended position of this particular relay.
Note The MVRE board only checks the P relay. It is driven by TCQA, the relay is on TCTx, and the voting is done at
the logic level.
• Hardware problems with TCTx, K1 relay, TCQA, or MVRE
Solution

• Check the MVRE JL cable.
• Replace the trip board TCTx.

• If a problem still exists, replace the TCQA board.
85
Description 52GX 125 V dc voltage missing
Possible Cause The generator panel 125 V dc is not present on the PTBA board.
Solution
• Check for 125 V dc on the PTBA, screws 35 to 41.

• Check trip board TCTx, cable JN.
• Check the MVRE JL cable.
• Replace the trip board TCTx.
86
Description Relay trouble, K4-1
Possible Cause Protection relay K4-1, on the TCTx trip board, is out of step with the majority.
Med/Large Steam TCTS/TCTL K4-1 = K20
Gas Turb TCTG K4-1 = K22
Solution
• Check for a loose or missing relay. Replace the relay, if necessary.

• Check the MVRE JL cabling.
• If a problem still exists, replace the trip board TCTx.

87
Possible Cause Protection relay K4-2 on the TCTx trip board is out of step with the majority.
Gas Turbine TCTG K4-2 = K23
Solution

88
Solution


89
Solution

90
Description 4 relay disagreement
Possible Cause
• Protection relays K4-1,2,3,4 are not all in the same state (on the TCTx trip board).
Med/Large TCTS/TCTL K4-1= K20, K4-2 = K21 K4-3 = K22 K4-4 = K23
Steam
Gas TCTG K4-1 = K22 K4-2 = K23 K4-3 = K24 K4-4 = K25
Turbine
Solution


91
Description Voltage missing, 0diag32, 125 V dc
Possible Cause The 125 V dc voltage is not present on the TCTx board.
Solution
• Check the cable J7W on TCTx.

92
Description Voltage missing, 0diag33, 24VR
Possible Cause The 24VR voltage is not present (or out of limits) on the TCTx board.
Solution
• Check all three JL cables.

93
Description Voltage missing, 0diag34, 115 V ac
Possible Cause The 115 V ac voltage is not present (or out of limits) on the TCTx board. This is applicable to large
steam turbines only.
Solution
• Check the J18 cable.


94
Description Power supply out of limits, P5
Possible Cause The MVRE P5 V is out of limits.
Solution
• Adjust the P5 V through the R29 on the MVRE.

• Replace the MVRE board.
95
Solution Replace the MVRE board.
96
Description Power supply out of limits, N15
Possible Cause The MVRE N15 V is out of limits.
Solution Replace the MVRE board.
97
Note This is the relay coil supply. It is diode-selected on the trip board TCTx. The loss of only one P24 V supply will
not shut down the turbine.
Solution
• Check for loss of supply or loose wire.

• Replace the power supply.
• If the problem still exists, replace the MVRE.
98
Description Power supply trouble, P24AS/N24AS
Possible Cause The MVRE P24A is out of limits.
Solution
• Check the MVRE Fuse FU4. Measure the voltage across it, if the voltage is not zero, replace the fuse.
• If the problem still exists, check for an external wiring problem (PTBA screws 65 and 66).
• If the problem still exists, replace the MVRE.

99
Description Ground fault on P24AS/N24AS Bus
Possible Cause The MVRE aux supply, P24A, has a ground fault.
Solution
• Check for a ground fault on the external wiring (PTBA screws 65 and 66).
• If a problem still exists, replace the MVRE.
Note On gas turbine applications with a GE/Reuter-Stokes flame detector interface module, interchanging the isolated P24
with the control power wired to the interface module results in this condition. Correct wiring such that the isolated P24
supplies the power for the transducers, and the control power for direct interface with the control panel, are kept separate.
100
Possible Cause The MVRE P335 is out of limits.
Solution Replace the MVRE.
101
Description Power supply out of limits, DCOM
Possible Cause The MVRE Dcom is out of limits.
Solution Verify that the DCOM stab connection is connected to each MVRE.
102-109
Description Flame detector [ ] out of limits
Possible Cause Signal input(s) at the MVRE connector JK-1(#1) through JK-8(#8) appear to be greater than 2 Hz while
at (or near) ZERO speed.
Solution
• Check the external wiring.

• Replace the flame detector.

110
Description Emerg online OS test fail, ETR1
Possible Cause For medium steam turbines only, an emergency online overspeed system test failed.
Solution
• Replace the MVRE, then replace the JL cables

• Verify that the IONet communications to the MVRE are functioning.
111
Description Emerg online OS test fail, ETR2
Solution

• Replace the MVRE and/or the JL cables.
• Ensure IONet communications to the MVRE are functioning.
112
Description Prim online OS test fail, PTR1
Solution
• Replace the MVRE and the TCQA, then replace the JD cables.
• Ensure IONet communications to MVRE are functioning.
113
Description Prim online OS test fail, PTR2
Solution
• Replace the MVRE and the TCQA, then replace the JD cables.
• Ensure IONet communications to MVRE are functioning.

1050-1178
Description Logic Signal [ ] Voting Mismatch
Possible Cause There is a problem with a status input between the R, S, and T MVREs, either the device, the wire
to the terminal board, or the terminal board.
Solution
• Verify that the R, S, and T MVRE configurations are equal to the ToolboxST configuration.
• Check the PMVP power and networking.
• Check the PMVP mounting on the terminal board.
• Verify the operation of the device generating the specified signal.
• Verify the terminal board wiring and connections.
1179-1204
Possible Cause There is a problem with a status input between the R, S, and T MVREs, either the device, the wire
to the terminal board, or the terminal board.
Solution
• Verify that the R, S, and T MVRE configurations are equal to the ToolboxST configuration.
• Check the PMVP power and networking.
• Check the PMVP mounting on the terminal board.
• Verify the operation of the device generating the specified signal.
• Verify the terminal board wiring and connections.


Protection Boards from Mark V Control
Trip Boards
Refer to GEH-6800 Volume I, The following trip boards (connected by JL) are specific to a type of turbine, primarily in
Mark VIe Control Migration the solenoid types and quantities as well as the diagnostics passed back to the MVRE:
from Mark V Control, Chapter 3
Application Specific Functions. • TCTE has drivers for three solenoids, each controlled by TMR relay contacts for ETR
(from the MVRE) and PTR (from the R, S, T cores) relays. Two of the solenoids
(ETD1, ETD2) have current switches to drive either 240 or 120 ohm coils, and the
third driver is for a 24 V coil (ETSV).
• TCTL has drivers for a 125 V solenoid coil controlled by a parallel OR of TMR
contacts for ETR1 or ORD2, and a 24 V solenoid coil controlled by TMR contacts for
ETR2 and ORD3
• TCTS has drivers for two solenoid coils (ETD1, ETD2) with current switches to
drive either 240 or 120 V coils. A TMR of ETR1 or DRV1 and a TMR of ORD2 or
ORD4 controls ETD1’s driver. A TMR of ETR2 or DRV2 and a TMR of ORD3 or
ORD5 controls ETD2’s driver.
• TCTG with drivers for four solenoids (A, B, C, D) are all 125 V coils. Solenoid A is
controlled by TMR of ETR1 and TMR of PTR1, solenoid B by TMR of ETR2 and
TMR of PTR2, solenoid C by TMR of PTR3, and solenoid D by TMR of PTR4.

JL Connections for Trip to PMVP
TCTE TCTG TCTL TCTS
JL-1 P24 P24 Input Power

JL-2 COM COM for P24 supply
JL-3 ODIAG0 = ETR1 ETR1-Y K5 Sense ETR1-Y K4 Sense ETR1-Y K5 Sense K5 Sense
Y Sense
JL-4 ODIAG1 = ETR1 ETR1-X K11 Sense ETR1-X K5 Sense ETR1-X K4 Sense K11 Sense
X Sense
JL-5 ODIAG2 = ETR1 ETR1-Z K13 Sense ETR1-Z K6 Sense ETR1-Z K6 Sense K13 Sense
Z Sense
JL-6 ODIAG3 = ETR2 ETR2-Y K4 Sense ETR2-Y K7 Sense ETR2-Y K11 Sense K4 Sense
Y Sense
JL-7 ODIAG4 = ETR2 ETR2-X K10 Sense ETR2-X K8 Sense ETR2-X K10 Sense K10 Sense
X Sense
JL-8 ODIAG5 = ETR2 ETR2-Z K12 Sense ETR2-Z K9 Sense ETR2-Z K12 Sense K12 Sense
Z Sense
JL-9 ODIAG6 = PTR1 PTR1-R K7 Sense PTR1-R K13 Sense PTR1-R K7 Sense K7 Sense
R Sense
JL-10 ODIAG7 = PTR1 PTR1-S K8 Sense PTR1-S K14 Sense PTR1-S K8 Sense K8 Sense
S Sense
JL-11 ODIAG8 = PTR1 PTR1-T K9 Sense PTR1-T K15 Sense PTR1-T K9 Sense K9 Sense
T Sense
JL-12 ODIAG9 = PTR2 PTR2-R K15 Sense PTR2-R K19 Sense PTR2-R K15 Sense K15 Sense
R Sense
JL-13 ODIAG10 = PTR2 PTR2-S K16 Sense PTR2-S K20 Sense PTR2-S K16 Sense K16 Sense
S Sense
JL-14 ODIAG11 = PTR2 PTR2-T K17 Sense PTR2-T K21 Sense PTR2-T K17 Sense K17 Sense
T Sense
JL-15 ODIAG12 = PTR3 PTR3-R K25 Sense PTR3-R K10 Sense K19 Sense K6 Sense
R Sense
JL-16 ODIAG13 = PTR3 PTR3-S K26 Sense PTR3-S K11 Sense K13 Sense K14 Sense
S Sense
JL-17 ODIAG14 = PTR3 PTR3-T K27 Sense PTR3-T K12 Sense K14 Sense K19 Sense
T Sense
JL-18 ODIAG15 ETR3-R K6 Sense PTR3-R K16 Sense K18 Sense K18 Sense
JL-19 ODIAG16 ETR3-S K14 Sense PTR3-S K15 Sense MLO - K13 Sense n/c
JL-20 ODIAG17 ETR3-T K18 Sense PTR3-T K16 Sense OTS - K18 Sense n/c
JL-21 ODIAG18 = K1 P125BUF - K1 Sense PBUF - K1 Sense PBUF - K1 Sense K1 Sense
Sensing
JL-22 ODIAG19 K20 Sense K22 Sense K20 Sense K20 Sense

TCTE TCTG TCTL TCTS
JL-26 ODIAG23 Solenoid SOLENOID A ETD1 SOLENOID A Sense MTSV Solenoid ETD1 Solenoid
A Sense Sense Sense
JL-27 ODIAG24 Solenoid SOL3 ETSV Sense SOLENOID B Sense ELO K19 Sense n/c
B
JL-28 ODIAG25 Solenoid SOLENOID C ETD2 SOLENOID C Sense ETSV Solenoid ETD2 Solenoid
C Sense Sense Sense
JL-29 ODIAG26 Solenoid n/c SOLENOID D Sense ORST K14 Sense n/c
D
JL-30 ODIAG27 = Sync K1-K2-K3 to 25 CNTRL Sense - Sync Check Output Sensing
Check
JL-31 ODIAG28 = K3 P125CTRL through K3 Sense
Check
JL-32 ODIAG29 = P125GVX Sense
P125CTRL Sense
JL-33 ODIAG30 = 52G/AUX Sense
52G/AUX Sense
JL-34 ODIAG31 = SENSE5E Sensing
SENSE5E Sense
JL-35 ODIAG32 = P125BUF Sensing PBUF Sensing P125BUF Sensing P125BUF Sensing
P125BUF Sense
JL-36 ODIAG33 = P24VR P24VR Sense
Sense
JL-37 OD25DRV O25DRV K3 Driver Input
JL-38 OETR2 K4 Y K10 X K12 K7 (Y), K8 (X), K9 ETR2 K11 Y K10 K4 (Y), K10 (X),
Z Driver (Z) Driver X K12 Z K12 (Z) Driver
JL-39 OETR1 K5 Y K11 X K13 K4 (Y), K5 (X), K6 ETR1 K5 Y K4 X K6 Z K5 (Y), K11 (X), K13
Z Driver (Z) Driver (Z) Driver
JL-40 ODRV0 OEOSTRP Driver
JL-41 ODRV1 n/c n/c ODRV1 TMR to K19 K19 Driver
JL-42 ODRV2 n/c n/c n/c K18 Driver
JL-43 ODIAG34 n/c n/c H115V AC Sense n/c
JL-44 P24A Isolated P24I to TMR to JT-1
JL-45 ID0 P5V Common Common Common
JL-46 ID1 P5V Common P5V P5V
JL-47 ID2 Common P5V P5V Common
JL-48 OALARM OALARM Driver
JL-49 P5 P5 Supply
JL-50 Return for P24A N24I return from JT-2

JD Connections for Trip to MVRx with PMVE
TCTE TCTG TCTL TCTS

JD-1 ORD0 Driver ORD0 driver (TMR) to K2
JD-2 ORD1 Driver ORD1 driver (TMR) to K2
JD-3 ORD2 Driver n/c ORD2 driver to K14 ORD2 driver to K7 for ORD2 driver to K7 for
for R, K14 for S, R, K8 for S, K9 for T R, K8 for S, K9 for T
K15 for T
JD-4 ORD3 Driver for ORD3 driver to K15 ORD3 driver to K19 ORD3 driver to K15 ORD3 driver to K15
PTR2 for R, K16 for S, K17 for R, K20 for S, for R, K16 for S, for R, K16 for S,
for PTR2 coils K21 for T K17 for T K17 for T
JD-5 ORD4 Driver for ORD4 driver to K25 ORD4 driver to K10 ORD4 TMR to K13 ORD4 driver to
PTR3 for R, K26 for S, for R, K11 for S, K6 (TMR)
K27 for T K12 for T
JD-6 ORD5 Driver n/c ORD5 driver to K16 ORD5 TMR to K14 ORD5 driver to
for R, K17 for S, K14 (TMR)
K18 for T
JD-7 ORD6 Driver n/c n/c ORD5 TMR to K18 n/c
JD-8 n/c n/c n/c n/c
JD-13 OEOSTRP Output
JD-14 LINE in
JD-15 LGCOM return
JD-16 GENR in GENR in GENR in GENR in

JM Connections for Trip to PBTA Outputs
TCTE TCTG TCTL TCTS

JM-1 Solenoid A SOLARES to ETD n/c SOL1X to MTSC SOLARES to ETD
coil coil
JM-2 Solenoid C SOLCRES n/c ORST AC Return SOLCRES
JM-3 Sync Check Out 25CNTRL /K1, K2, K3 to P125)
JM-4 Solenoid A SOLABPOS SOLAPOS SOL1Y to MTSV SOLABPOS to ETD1
(125V)
JM-5 Solenoid A SOLANEG SOLANEG SOL1L to MTSV SOLANEG from
(125V) ETD1
JM-6 Contact 52 25G/AUX
JM-7 Solenoid C/D SOLCDPOS SOLCDPOS H115V AC Power SOLCPOS
JM-8 Solenoid C SOLCNEG SOLCNEG ELO AC Return SOLCNEG
JM-9 Solenoid B SOL3H SOLBPOS SOL3H to ETSV n/c
(24V)
JM-10 Solenoid B SOL3L SOLBNEG SOL3L to ETSV n/c
(24V)
JM-11 Manual Sync MAN Output (K1, K3 to P125)
JM-12 Solenoid D n/c SOLDNEG MLO AC Return n/c

JN Connections for Trip to PBTA Inputs and Power
TCTE TCTG TCTL TCTS

JN-1 Supply to Trip Switch POS5E (tie to POS5E (tie to POS5E (tie to POS5E (tie to
N125BVX to drive N125BUF to drive N125BUF to drive N125BUF to drive
K20, K21) K22, K23) K20, K21) K20, K21)
JN-2 Return from Trip SENSE5E input to trip board
Switch with Sensing
JN-3 Return from External TRPSENSE input to trip board
Trip Switch without
Diagnostic Sense
JN-4 GEN Panel 125V P125CTRL supply
Feed
JN-5 GEN Panel 125V P125VGX sensing
Feed
JN-6 GEN Panel 125V N125GX return
Return
JN-7 Line Signal LINE in
JN-8 AC Common LGCOM return
JN-9 GEN Signal GENR in
JN-10 Solenoid 6 OTS for n/c n/c OTC AC return n/c
Large Steam
JT Connections for Trip to PBTA Inputs and Power
TCTE TCTG TCTL TCTS

JT-1 24VI Supply Isolated 24V supply Isolated 24V supply Isolated 24V supply Isolated 24V supply
JT-2 24VI Return Isolated 24V return Isolated 24V return Isolated 24V return Isolated 24V return
J7W-1 VPOS Supply P125VX supply to PVX supply to TCTG P125VX supply to P125VX supply to
TCTE TCTL TCTS
J7W-2 VNEG Return N125VX return from NVX return from N125VX return N125VX return
TCTE TCTG from TCTL from TCTS
J18-1 AC Hot n/a n/a H115 AC Hot n/a
J18-2 AC Neutral n/a n/a L115 AC Neutral n/a

PTBA Terminal Board
Refer to GEH-6800 Volume I, This PTBA is the terminal board in the protection core of the existing Mark V control
Mark VIe Control Migration system. The PTBA allows customer site wiring into the protection core, which also
from Mark V Control, Chapter contains a trip board, a TCEB signal interface board, and three PMVP protection modules
10 Signal Flow and Power operating in TMR. The PTBA provides the following signal connections:
Distribution Diagrams.
• Flame detectors with up to 335 V dc at the terminals are passed from the PTBA
through the TCEB to three PMVPs.
• Trip logic is passed from the PTBA to the trip board (TCTG, TCTL, TCTE, or
TCTS, depending on the type of turbine), including the generator panel contacts, trip
contacts, and solenoid outputs for trip valves at the turbine.
• Power system sensing for generator and bus (grid) currents (5 Amps), and line
voltages (120 V ac) are passed to the TCEB’s internal transformers, and then on to
the PMVPs, and to connectors for the original Mark V control power load unbalance
(PLU) unit.
• Speed pickups for HP (3) and LP (3) turbine shafts are passed from the PTBA through
the TCEB to PMVPs. These inputs are optional depending on the turbine type, with
any unused inputs shorted to avoid noise pickup.
The PTBA connects to the other core boards with ribbon cables at the following
outputs:
• JU to the TCEB, carrying the magnetic speed pickup, flame detector input signals
• JVA and JVB to the TCEB, carrying the current limited 335 V dc signals for flame
detectors
• JV to the TCEB, carrying the generator and line currents and voltages
• JM and JN to the trip boards, carrying the contact and solenoid signals
• JJR, JJS, and JJT are for the LM2500 system only, carrying the magnetic speed
pickup signals to <R>, <S>, and <T> cores
The PTBA cannot be replaced under power without a turbine trip occurring. For any
replacements, the turbine system must be fully shut down with lock out tag out.
High voltages exist on the terminals for the PTBA for the
flame detectors and line voltages. The current transformer
inputs to the PTBA can generate high voltages if the wiring is
disconnected either at the terminal strip or by removing the
Warning ribbon cables.
To prevent injury from shock and turbine trip, only work on

this wiring with the system shut down. Current transformers
must have their output terminals shorted at the CT location
prior to wire changes.
Warning

Common Module Content
The following information is common to the distributed I/O modules:
• Processor LEDs
• Hardware Jumpers
• Common Module Alarms
Auto-Reconfiguration
The Auto-Reconfiguration feature allows I/O modules to be replaced without operator
configuration. If the Auto-Reconfiguration feature is enabled, when the controller
detects an I/O module booting with a different configuration, a reconfiguration file is
automatically downloaded from the controller to the I/O module. This reconfiguration
includes the bootload, baseload, firmware, and parameters. Each I/O module is updated
with the current configuration that matches the configuration used by the controller, unless
it already contains the latest version.
Auto-Reconfiguration is While an Auto-Reconfiguration is in progress, the controller will not allow a reboot until
available with the ControlST* after the Auto-Reconfiguration has completed. Other downloads to the I/O module cannot
software suite version 4.0 or be initiated while it is being Auto-Reconfigured. If an I/O pack is already running,
higher. Auto-Reconfiguration only performs diagnostics.
Auto-Reconfiguration is enabled or disabled in the ToolboxST application through the

Component Editor. This allows the operator to manually reconfigure each I/O module if
necessary. If a terminal board is replaced, the I/O pack must be manually reconfigured.
Refer to GEH-6700, ToolboxST When power is applied, the I/O module boots up and, if enabled, the Auto-Reconfiguration
User Guide for Mark VIe process starts. It generates a signal to the Mark VIe controller to indicate it needs an IP
Control, Chapter 6 Mark VIe address and configuration. The Mark VIe controller queries the I/O module, identifies
Component Editor, the section existing files to determine if a reconfiguration is needed, downloads the IP address and
Auto-Reconfiguration. reconfiguration files, then signals the I/O module when the download is complete. The I/O
module reboots, performs a self-diagnostic test, and goes online.
Note When replacing an I/O module with one that already has the proper baseload
and firmware, the Auto-Reconfiguration process takes a relatively short time (less
than a minute). When the baseload and/or firmware needs to be reloaded, the
Auto-Reconfiguration process may take a few minutes to complete.
GEH-6800_Vol_II Common Module Content System Guide 5-1

Processor Board
The BPPx processor board is used with most Ethernet-based I/O modules. It contains
the following:
• High-speed processor with RAM and flash memory

• Two fully independent 10/100 Ethernet ports with connectors
• Hardware watchdog timer and reset circuit
• Internal temperature sensor
• Status-indication LEDs
• Electronic ID and the ability to read IDs on other boards
• Input power connector with soft start/current limiter
• Local power supplies
The processor board connects to an acquisition board specific to the I/O module function.
Upon application of input power, the soft-start circuit ramps up the voltage available on
the processor board. The local power supplies are sequenced on, and the processor reset
is removed. The processor completes self-test routines and then loads application code
specific to the I/O module type from flash memory. The application code reads board
ID information to ensure the correct matching of application code, acquisition board,
and terminal board. With a good match, the processor attempts to establish Ethernet
communications, starting with request of a network address. The address request uses
the industry standard dynamic host configuration protocol (DHCP) and the unique
identification read from the terminal board. After Ethernet initialization, the processor
programs the on-board logic, runs the application, and enables the acquisition board
to begin operation.
The processor application code contains all the logic necessary to allow the I/O module to
operate from one or two Ethernet inputs. When operated from two Ethernet inputs, both
network paths are active all the time. A failure of either network will not result in any
disturbance to the I/O module operation, and the failure will be indicated through the
working network connection. This arrangement is more tolerant of faults than a classic
hot-backup system where the second port is only used after a primary port failure is
detected. The Ethernet ports on the processor auto-negotiate between 10 and 100 Mbps
speed, and between half-duplex and full-duplex operation.
Note The PMVE module contains a UCSA processor.

Processor LEDs
Color Label Description
Green PWR Shows the presence of control power
Green LINK Provided for each Ethernet port to indicate if a valid Ethernet connection is present
Yellow TxRx Provided for each Ethernet port to indicate when the I/O module is transmitting
or receiving data over the port
Red/Green ATTN Shows I/O module status
ATTN LED Flash Codes
LED Flashing Pattern Description
Red ATTN LED out There are no detectable problems

Solid Booting - prior to reading board ID
4 Hz 50% Diagnostic alarm active
2 Hz 50% Awaiting an IP address
1 Hz 50% No firmware to load (Program mode)
0.5 Hz 50% Application code not loaded to the I/O module
Green ATTN Solid BIOS (at power on), but if it remains in this state, the I/O module is
not functioning properly and should be replaced
2 Hz 50% Awaiting Auto-Reconfiguration release
1 Hz 50% I/O module in WAIT or STANDBY
Two 4 Hz flashes every 4 seconds Application online
Note The PMVE module contains a UCSA processor with different LEDs.

Hardware Jumpers
Jumpers are used to configure control system hardware to meet specific application
requirements. A hardware jumper consists of a pin, or series of pins mounted
perpendicularly to a printed circuit board, and a plastic and metal jumper that can be
manually inserted over pairs of pins. When the jumper is placed over two pins, a
connection is made and the function associated with those pins is enabled. When not in
use, a jumper may be stored in proximity to a specific pin arrangement by placing the
jumper over only one pin. This does not create a circuit connection, but is available
if a change is necessary.
Hardware jumpers perform a wide variety of functions.

These devices regulate operations such as card frequency,
memory storage, overspeed trip settings, and system grounding.
Improper application of hardware jumpers can cause significant
Warning damage to the system or personnel.
The following hardware jumper configuration examples show printed circuit board
silkscreens and jumper positions.

These jumper configuration tables are divided into five sections:
• The first table indexes the core(s) where the board is found such as <R>, <S>, <T>,
the location(s) of the board within theses core(s) (identical cards can occupy multiple
locations within multiple cores, and a board revision number (Rev.)
• The Jumper column gives the number of the jumper being identified.
• The Position column defines the position(s) in which to place a jumper for a
specific pin configuration. This category is subdivided into separate listings when
an individual pin configuration has multiple functions.
• The Application Notes describes the functions of the various pin configurations. The
following table is an example.
Note Refer to the specific distributed I/O module chapter, Configuration section for
the jumper configuration tables for each board.

The following alarms are common to all distributed I/O modules, but not all of these
alarms are applicable for every module.
0
Description Diagnostic Alarm Reset
Possible Cause
Solution
2
Description Flash memory CRC failure
Possible Cause
During commissioning or maintenance:
• A firmware programming error occurred. The I/O pack or module did not go online with the controller.
• The hardware failed.
Solution
• Rebuild the system, then download the application and the configuration to the I/O pack or module.
• Replace the I/O pack or module.

3
Description CRC failure override is active
Possible Cause
• A firmware programming error occurred. The I/O pack or module did not go online with the controller.
Solution
4
Description I/O pack in stand alone mode
Possible Cause
• The I/O pack or module configuration is invalid.

Solution

5
Description I/O pack in remote I/O mode
Possible Cause

Solution
6
Description Special User Mode active. Now: [ ]
Possible Cause

Solution
• Rebuild system, then download the application and the configuration to the I/O pack or module.

7
Description The I/O pack has gone to the Offline state
Possible Cause
• Ethernet cable disconnected or connected to wrong port

• Controller is offline or restarted.

• Faulty Ethernet switch/cable
Solution
• Check the Ethernet cable.

• Verify that the controller is not offline.

• Replace the Ethernet switch/cable.
16
Description System limit checking is disabled
Possible Cause System checking disabled by configuration
Solution System checking was disabled by the configuration.
20
Description I/O communication failure between [ ] and controller
Possible Cause
• I/O pack or module did not complete Start

• I/O pack or module configuration files missing
• I/O pack or module restarted
• I/O pack or module configured for dual networks, but only one network is connected
• Network issue
Solution
• If the Control/Status communication is working correctly, any additional diagnostics should indicate the cause of the
problem.
• Build and download parameters to the I/O pack or module.
• Download firmware and parameters to the I/O pack or module.
• Verify that the Ethernet cables and network switch are operating correctly.
• Manually restart the I/O pack or module.

21
Description Control/Status communication failure between [ ] and controller
Possible Cause
• Asynchronous Drive Language (ADL) communication unhealthy

• Terminal board barcode is typed incorrectly in the ToolboxST configuration
• Wrong terminal board is configured in the ToolboxST application
• I/O pack or module is plugged into the wrong Jack on the terminal board, or the wrong jack number is configured in
the ToolboxST application
• I/O pack or module is configured in the ToolboxST application, but the configuration is not downloaded to the controller
• I/O pack or module is in program mode
Solution
• Verify that the I/O pack or module configuration (Type, HW Form, Bar Code, position) matches the actual hardware.
• Build and download the configuration to the controller, wait for communication status to change, then scan and download
to the I/O pack or module.
22
Description Diagnostic status signal (...L3DIAG and/or ...ATTN) is [ ]; therefore, diagnostic status for this I/O pack
may be inaccurate, unknown, or indeterminate
Possible Cause
• I/O pack or module status signal quality is in warning state

• Signal quality is unhealthy, forced, or being simulated
• Status information is inaccurate
Solution Check signal health, remove the force, or simulated condition.
23
Description [ ] controller state is not OK...(i.e. Major Difference)
Possible Cause Major difference in controller application/configuration code
Solution Rebuild the system and download.

24
Description Cannot retrieve I/O pack information. [ ]
Possible Cause
• Cannot get the requested information from I/O pack or module.

• Communication program failure
• I/O pack or module unable to retrieve the IP address
• Terminal board barcode is typed incorrectly in the ToolboxST configuration
• Wrong terminal board is configured in the ToolboxST application
• I/O pack or module is plugged into the wrong Jack on the terminal board, or the wrong jack number in the ToolboxST
configuration
• I/O pack or module is configured in the ToolboxST application, but the configuration is not downloaded to the controller
• I/O pack or module is in program mode
Solution
• Verify that the I/O pack or module configuration (Type, HW Form, Bar Code, position) matches the actual hardware.
• Build and download the configuration to the controller, wait for communication status to change, then scan and download
to the I/O pack or module.
• Check the network cables for proper connection.
• Verify that the switch is functioning correctly.
25
Description Control/Status communication Error: [ ]
Possible Cause
• Cannot get diagnostic information from I/O pack or module

• I/O pack or module is not able to load firmware
Solution
• Verify the I/O pack or module configuration.

• Rebuild the application and download the firmware and the application to the I/O pack or module.
• Check the network cables for proper connection.
• Verify that the switch is functioning correctly.

30
Description Firmware/Configuration Incompatibility Error;Firmware: [ ] Config: [ ]
Possible Cause I/O pack or module configuration files are incompatible with the firmware. Files have wrong revision.
Solution
• Confirm the correct installation of the ToolboxST application.

• Verify that each I/O pack or module is upgraded to the latest version by right-clicking each I/O pack or module and
selecting Upgrade.
• Rebuild the application and download the firmware and the application code to the affected I/O pack or module.
31
Description Firmware/IO Configuration Incompatibile;Firmware: [ ] IO Config: [ ]
This alarm has been depreciated and is only shown for legacy compatibility.
Possible Cause
• I/O pack or module configuration files are incompatible with the firmware.
• The files have the wrong revision.
Solution

• Verify that each I/O pack or module is upgraded to the latest version by right-clicking each I/O module and selecting
Upgrade.
• Rebuild the application, and download the firmware and application code to the affected I/O pack or module.
256
Description [ ]V Pwr supply voltage is low
Possible Cause
• Input voltage dropped below 18 V. I/O pack or module input power required to be within range 28 V ±5%. I/O pack or
module operation will be compromised or may stop completely.
Solution
• If PPDA is available to monitor control cabinet power, check the I/O pack or module for active alarms.
• Check the I/O pack or module power within the control cabinet; begin with power supplies and work toward the affected
I/O pack or module.

257
Description [ ]V Pwr supply voltage is low
Possible Cause
• For BPPB-based I/O packs, input voltage has dropped below 26.5 V. Input voltage is required to be within the range
28 V ±5%.
• For BPPC-based I/O packs, input voltage has dropped below 24 V. Input voltage is required to be within the range
24 V ±10%.
Note In most cases, normal pack operation continues below this voltage, but field devices that require 24 V from the
terminal board may begin to experience reduced voltage operation with undetermined results.
Solution
• If PPDA is available to monitor control cabinet power check the I/O pack or module for active alarms.
• Check I/O pack or module power within the control cabinet; begin with power supplies and working toward the affected
I/O pack or module.
258
Description Temperature [ ] °F is out of range ([ ] to [ ] °F)
Possible Cause
• Temperature went outside -35 to 85°C (-31 to 185 °F) limits for most I/O modules.
• Temperature went outside -35 to 66°C (-31 to 151 °F) limits for PCNO or PPRF.
Solution Verify the environmental controls for the cabinet containing the I/O pack or module. The I/O pack or module
will continue to operate correctly beyond these temperature limits, but long-term operation at elevated temperatures may
reduce equipment life.
259
Description Application Runtime Error - [ ] Frame overruns occurred
Possible Cause Overloaded controller or controller sequencer malfunction (one or more frame overruns occurred)
Solution
• Increase the frame idle time by reducing the application or increasing the EGD period.
• Increase the frame idle time by using a faster processor board (UCCC).
• Increase the frame idle time by replacing the processor module.

261
Description Unable to read configuration file from flash
Possible Cause
• The I/O pack or module does not have the correct configuration file stored in its flash file system.
• There is a hardware problem.

• There is a hardware failure.
Solution

• Rebuild the system and download the application and the configuration to the I/O pack or module.
262
Description Bad configuration file detected
Possible Cause
During commission/maintenance:
• The configuration file in the I/O pack or module is not compatible with loaded application code
• There is a hardware failure
Solution
• Rebuild the system and download the application and the configuration to the I/O pack or module.

263
Description Invalid configuration file
Possible Cause
• The downloaded configuration file is for a different type of I/O module.

Solution
• Rebuild the control system and download the application and configuration to the I/O module.
• Replace the I/O pack.
264
Description Firmware/Configuration Incompatibility Error
Possible Cause
• I/O pack or module configuration files are incompatible with the firmware.
• The files have the wrong revision.
Solution

• Verify that each I/O pack or module is upgraded to the latest version by right-clicking each I/O pack and selecting Upgrade.

265
Description Configuration file load error - invalid I/O header size
Possible Cause
• Build error
• Controller EGD revision code is not supported
• Incompatible version of the I/O pack or module firmware was downloaded
Solution

• Rebuild the application, and download the firmware and application code to the affected I/O module.
266
Description Configuration file load error - invalid file length
Possible Cause
• The configuration file in the I/O pack or module does not have the correct size to match the application code that is loaded.
Solution
• Confirm the correct installation of the ToolboxST application. Rebuild the application and download the firmware and
the application code to the affected I/O pack or module.

267
Description Firmware Load Error
Possible Cause
• Incompatible version of firmware downloaded

Solution

• Ensure that each I/O pack or module is upgraded to the latest version. From the ToolboxST application, right-click each
I/O pack or module and selecting Upgrade.
268
Description Firmware Load Error - Incompatible FPGA Revision: Found [ ] Need [ ]
Possible Cause
• Incompatible version of firmware downloaded

Solution

selecting Upgrade.

269
Description EGD communication Initialization Failure
Possible Cause Internal runtime error
Solution
• Restart the I/O pack or module.

• Upgrade the I/O pack or module firmware and application code.
• If the problem persists, replace the I/O pack or module.
271
Description Internal communication error - Exchange [ ] Export failed
Possible Cause
• I/O pack or module does not have correct configuration file stored in flash file system
• Internal runtime error
• Internal runtime error
Solution
• From the ToolboxST application, confirm the correct configuration of the I/O pack or module.
• Rebuild the system, and download the application and configuration to the I/O pack or module.

• If problem persists, replace the I/O pack or module.
279
Description Could not determine platform type from hardware
Possible Cause
• There is an incorrect firmware version or hardware malfunction (firmware could not recognize host hardware type).
Solution
• Verify that all connectors are aligned properly and fully seated.
• Check the firmware version for compatibility with platform. If it is correct, replace the I/O pack or module.

280
Description Platform hardware does not match configuration
Possible Cause
• The platform type identified in the application configuration does not match actual hardware
• There is a hardware failure
Solution
• Fix the platform type in the ToolboxST application (General tab, General Properties, Platform).
• Rebuild and download the application.
281
Description Firmware Load Error - FPGA not programmed due to platform errors
Possible Cause File downloaded to configure the Field Programmable Gate Array (FPGA) not successfully applied
Solution
• Verify that all connectors are aligned properly and fully seated.
• Check the firmware version for compatibility with platform. If it is correct, replace the I/O pack or module.
282
Description Firmware Load Error - application independent processes failed to initialize
Possible Cause Runtime malfunction. An application-independent firmware process could not be started successfully.
Solution
• Reload firmware and application and restart.

• Controller: If the failure persists, remove the Compact Flash module and reprogram the boot loader using the ToolboxST
configuration. Download using the Device | Download | Controller setup | Format Flash selection. After reinstalling the
flash module and restarting, reload the firmware and application.
• Replace the module.
• I/O pack or module: Re-download the base load.

283
Description Firmware execution error - Internal process crashed
Possible Cause Runtime or hardware malfunction (runtime process failed)
Solution

• Controller: If failure persists, remove the Compact Flash module and reprogram the boot loader using ToolboxST.
Download using the Device | Download | Controller setup | Format Flash pick, then, after reinstalling the flash module and
restarting, reload firmware and application.
• If this does not work, replace processor module.
• I/O pack or module: Re-download the baseload and the firmware.
284
Description Unexpected reboot occurred - firmware fault
Possible Cause Runtime or hardware malfunction (runtime process failed)
Solution
• Reload the firmware and application, and restart the controller and/or I/O module.
• Controller: If failure persists, remove the Compact Flash module and reprogram the boot loader using the ToolboxST
application. Download using the Device | Download | Controller setup | Format Flash selection. After reinstalling the
flash module and restarting, reload firmware and application.
• I/O pack or module: Re-download the baseload and the firmware.
• If this does not work, replace the I/O module or controller.
285
Description Unexpected reboot occurred - hardware fault
Possible Cause
• Runtime or hardware malfunction

• Runtime process stalled
Solution

• If the problem persists, replace the processor module.

293
Description Waiting on IP addr Ionet [ ] before continuing
Possible Cause I/O pack or module waiting to obtain network address from the controller using DHCP
• Network problem
• Controller problem
• I/O pack or module not configured correctly, or incorrect ID (barcode)
• I/O pack or module is configured with 2 network addresses in the ToolboxST application, but only has one network
physically connected.
Solution
• Verify that the controller is online.

• Confirm that the correct terminal board ID is present in the ToolboxST configuration.
• Check IONet (switches, cables).
• From the ToolboxST application, verify that the I/O pack or module network configuration matches the physical network
configuration.
295
Description IOPACK - The FPGA is not generating an I/O interrupt
Possible Cause There is a FPGA inside the I/O pack or module that controls I/O or module hardware. The logic in the
FPGA generates an interrupt to the processor requesting that the I/O or module be serviced. That interrupt is not occurring
as expected.
Solution Rebuild system and download to the I/O pack or module. If the problem persists, replace the pack.
300
Description Application Code Load Failure
Possible Cause
• Invalid application configuration

• There is a firmware or hardware malfunction
Solution
• Rebuild and download the application to all processors.

• Reload the firmware and application.
• If the problem persists, replace processor module.

301
Description Configuration Load Failure
Possible Cause
• I/O pack or module I/O configuration files missing

• I/O pack or module reseated on the terminal board (clears configuration from I/O pack or module)
Solution
• Rebuild and download the application to all the processors.

• Reload the firmware and application.
• If the problem persists, replace processor module.
338
Description Pack Firmware Error - Inputs are not being updated
Possible Cause
• The I/O pack or module application process is not providing system signal inputs to EGD every frame.
Solution
• Rebuild and download the firmware and the application.

• Verify that the idle time is adequate for the I/O pack or module and that the frame rate does not exceed defined limits.
339
Description Outputs are not being received
Possible Cause
• I/O pack or module not receiving outputs from the controller after previously receiving outputs
• Controller is restarting or has restarted
• Failed Ethernet connection between the I/O pack or module and controller
• Internal firmware failure
Solution
• Check for disconnected IONet cables or malfunctioning network switches.

• Verify that the controller is online and operating correctly.
• Rebuild and download the firmware and configuration to the I/O pack or module.

340
Description Memory Verification failed - Data structures
Possible Cause Hardware memory failure (data that should not change after I/O pack or module has gone online
has been modified)
Solution
• Rebuild and download the application to all affected I/O packs or modules.
• Reload the firmware and application code.
• If problem persists, replace the I/O pack or module.
341
Description Firmware or I/O Configuration Incompatibility
Possible Cause I/O pack or module configuration files incompatible with firmware (files do not contain necessary revision)
Solution
• Confirm the correct installation of the ToolboxST software.

selecting Upgrade.
342
Description Firmware or Configuration Incompatible
Possible Cause I/O pack or module configuration files incompatible with firmware (files do not contain necessary revision)
Solution

343
Description Memory Verification failed - Firmware Libraries
Possible Cause Hardware memory failure (data that should not change after the I/O pack or module has gone online
was modified)
Solution
• Rebuild and download the application to all affected I/O packs or modules.

351
Description Internal Firmware error - Thread [ ] timing overrun
Possible Cause An application task scheduled with a scan rate either occurred twice as fast or twice as slow as the
expected rate.
Solution
• Check the idle time on the I/O pack or module, and verify that the frame rate is correct.
366
Description Initialization failure - IO firmware
Possible Cause I/O pack or module did not initialize correctly
Solution

• Download the firmware and application code.
367
Description Internal communications error - HSSL Comm link down
Solution
• Check the High Speed Serial Link (HSSL) cables.

• Download the firmware and application code.

368
Description Configuration file load error - invalid header size
Possible Cause
• Build error
• Controller EGD revision code not supported
• Incompatible version of I/O pack or module firmware was downloaded
Solution

• Rebuild the application, and download the firmware and application code to the affected I/O pack or module
369
Description Internal communication error - Exchange [ ] Export failed
Solution

370
Description Internal EGD communication error - Exchange [ ] Import failed
Solution


371
Description IONet-EGD signal inputs are not being updated
Possible Cause
• The I/O pack or module application process is not providing system signal inputs to EGD every frame.
Solution
• Rebuild and download the firmware and application code.

• Verify that the idle time is adequate for the I/O pack or module, and that the frame rate does not exceed defined limits.
372
Description Memory Validation failed - Data structures
Possible Cause Hardware memory failure (process data that should not change after the controller goes online was
modified)
Solution Replace the I/O pack or module.
373
Description Firmware/IO Configuration Incompatible
Possible Cause I/O pack or module configuration files are incompatible with the firmware (files do not contain
necessary revision)
Solution

selecting Upgrade.

445
Description Incorrect or Missing Acquisition Board on HSSL link 1
Possible Cause The acquisition board on High Speed Serial Link 1 is not connected or does not agree with the
ToolboxST configuration.
Solution
• Verify that the correct acquisition board is connected to the specified HSSL connector on the UCSA.
• Verify that the ToolboxST configuration for the appropriate HSSL connector matches the hardware.
446
Possible Cause The acquisition card on High Speed Serial Link 2 is not connected or does not agree with the ToolboxST
configuration.
Solution
• Verify that the correct acquisition card is connected to the specified HSSL connector on the UCSA.
447
Possible Cause The acquisition card on High Speed Serial Link 3 is not connected or does not agree with the ToolboxST
configuration.
Solution
• Verify that the correct acquisition card is connected to the specified HSSL connector on the UCSA.
448
Description Acquisition Board barcode mismatch on HSSL link 1
Possible Cause The barcode on the acquisition card connected to High Speed Serial Link 1 does not agree with those
provided in the ToolboxST application
Solution Verify that the correct acquisition card is connected to the link and that the correct barcode has been entered in

449
450
451
Description Communication Lost on HSSL Link 1
Possible Cause The UCSA can no longer communicate with the acquisition card on High Speed Serial Link 1
Solution Verify that the Ethernet cable is connected and that the acquisition card is healthy.
452
453
485
Description Configuration mismatch with Auto-Reconfiguration server
Possible Cause Some or all of the I/O pack or module configuration files do not match those on the Auto-Reconfiguration
server
Solution Perform a scan and download using the ToolboxST application

490
Description Software watchdog has been disabled
Possible Cause
• A runtime malfunction has disabled the software watchdog protective function.

• An invalid version of firmware has been downloaded.
Solution
• Reload the base load, firmware, and application code to the I/O pack or module, and restart.
• If failure persists, remove the flash memory from the Mark VIe controller and reprogram the boot loader using the
ToolboxST application. Download using the Device | Download | Controller setup | Format Flash selection. After
reinstalling the flash memory and restarting, reload the firmware and application code.
• If the problem persists, replace the I/O pack or module or the Mark VIe controller.
491
Description Hardware watchdog has been disabled
Possible Cause
• A runtime malfunction has disabled the hardware watchdog protective function.

• A hardware failure has disabled the hardware watchdog protective function.
Solution
• Reload the firmware and restart the I/O pack or module.

• If the problem persists, replace the I/O pack or module or the Mark VIe controller.
499
Description I/O pack is connected to an unknown board
Possible Cause
• The terminal board or auxiliary terminal board connected to the I/O pack or module is not recognized by this version
of firmware.
• This can occur if a new terminal board has been connected but the I/O pack is configured with firmware that does not
support the new hardware.
Solution
• Upgrade the ControlST software suite to a version that supports the new hardware.
• Download latest firmware and parameters to the I/O pack or module.

500
Description I/O pack is connected to the wrong terminal board
Possible Cause The I/O pack or module is connected to a recognized terminal board that is not supported.
Solution
• For a list of supported terminal board and I/O pack combinations, consult the following product documents: GEH-6721
Vol II, GEH-6800 Vol II, GEI-100733, GEI-100731, GEI-100686, and GEI-100734. From the Start Menu, select All
Programs, GE ControlST, Documentation.
• Verify that the I/O pack is connected to a terminal board that is supported.
• Replace the I/O pack or terminal board to create a supported combination.
• Use the ToolboxST application to reconfigure the I/O module.
1008-1010,
1264-1266
Description Outputs unhealthy on IONet [ ] - Message Timeout
Possible Cause
• Controller is rebooting or has rebooted

• Application/configuration does not match in I/O pack or module and controller.
• Failed Ethernet connection between the I/O pack or module and the controller.
Solution
• Reset all diagnostic alarms.

• Rebuild and download the application to all the processors, including I/O packs or modules.
• Reload the firmware and the application.
• Verify that the Ethernet cable on the I/O pack or module matches the ToolboxST configuration.
• Check for a faulty Ethernet cable from the I/O pack or module to the network switch and/or from the switch to the
controller. Replace cable(s) if necessary.
• Faulty network switch; place the I/O pack or module's Ethernet cable into an empty port. If the problem persists, replace
the network switch.

1008-1010,
1264-1266
Description Outputs unhealthy on IONet [ ] - Message Length not valid
Possible Cause Application/configuration does not match in I/O pack or module and controller
Solution
• Rebuild and download the application/parameters to all controllers and I/O packs or modules.
• Reload the firmware and parameters to the affected I/O pack or module.
• Reload the firmware and the application to all controllers.
• If the problem persists, replace affected I/O pack or module, then replace the controller.
1008-1010,
1264-1266
Description Outputs unhealthy on IONet [ ] - Major Signature Mismatch
Solution
• Rebuild and download the application/parameters to all the controllers and I/O packs or modules.
• Reload the firmware and the parameters to the affected I/O pack or module.
• Reload the firmware and the application to all controllers.
1008-1010,
1264-1266
Description Outputs unhealthy on IONet [ ] - Minor Signature Mismatch
Solution
• Reload the firmware and the application to all the controllers.

1008-1010,
1264-1266
Description Outputs unhealthy on IONet [ ] - Timestamp Mismatch
Solution
• Reload the firmware and the application to all the controllers.

Replacement and Ordering
Replacement
Printed wiring boards may contain static-sensitive components. Therefore, GE ships all
replacement boards in anti-static bags. When handling boards or board components,
make sure to store them in anti-static bags or boxes and use a grounding strap (per the
following Caution criteria).
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
Caution workstation.
To prevent personal injury or damage to equipment, follow all

GE safety procedures, LOTO, and site safety procedures as
indicated by EHS.
Warning
This equipment contains a potential hazard of electric shock,

burn, or death. Only personnel who are adequately trained and
thoroughly familiar with the equipment and the instructions
should install, operate, or maintain this equipment.
Warning
Replacement Procedures
The failed board should be System troubleshooting should be at the circuit board level. The failed I/O pack or board
returned to GE for repair. Do should be removed and replaced with a spare.
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.
Warning
To prevent equipment damage, do not remove, insert, or adjust

board connections while power is applied to the equipment.
Caution
GEH-6800_Vol_II Replacement and Ordering System Guide 6-1

Replacing the PIOA
Replacement of the terminal board or full IS230 module requires full re-configuration of
the changed component using the ToolboxST application. For this reason, it is generally
preferable to replace only the I/O pack unless the terminal board is known to be the point
of failure.
Ø To replace an I/O pack
Refer to the I/O pack 1. Verify that the replacement I/O pack is compatible with one being replaced by
Compatibility section for a comparing the model numbers on their faceplates. The model number begins with an
list of hardware versions. IS220P prefix. Most times the numbers will match, but sometimes newer revisions
are used to replace older I/O packs.
2. Lockout and/or tagout the field equipment and isolate the power source.
3. Remove the power to the I/O pack. For the PSVP, turn SW1 on the SSVP to the
P28OFF position. For other I/O packs, remove the power plug located in the
connector on the side of the I/O pack.
4. Unplug the Ethernet cables and mark the positions of the removed cables.
5. Loosen the two mounting nuts on the I/O pack threaded shafts.
6. Unplug the I/O pack.
7. Plug in the replacement I/O pack. Make sure it is fully inserted into the slots on the
mounting base, then properly tighten the mounting nuts.
8. Plug the Ethernet and power cables back into the I/O pack and re-energize the
equipment.

Replacing the PMVE
Ø To replace the PMVE
• PMVE Ethernet Interface, Installation

• MVRA I/O Interface Board, Installation
• MVRB I/O Interface Board, Installation
• MVRC I/O Interface Board, Installation
• MVRF I/O Interface Board, Installation
Ø To Replace an existing MVRP with a new MVRP

1. LOTO
2. Remove power.
3. Remove cables.
4. Remove the five mounting screws.
5. Remove the old MVRP board.
6. Insert the new MVRP board.
7. Use the X1 S-tab and PB1 power bug to tie the MVRP to chassis or to tie together
the PCOM of adjacent boards.
8. Use the five mounting screws to attach the MVRP to standoffs in the power supply
module.
Note Mounting details are provided in GE Drawing 259B2451EZG01.
9. Power on the MVRP by connecting the 28 V dc input to J28.

Replacing the PMVD
Ø To replace an existing PMVD with a new PMVD
1. Verify that the replacement PMVD is compatible with one being replaced by
comparing the model numbers. The model number begins with an IS220P prefix.
3. Remove the power plug located in the connector on the side of the old PMVD.
4. Unplug the Ethernet cables and record the positions of the removed cables.
5. Unclip the tabs at the top of the board and remove the board from the plastic frame.
Do not attempt to handle, remove, or secure the iButton with

the board held vertically, as the clip internal spring will likely
propel the part. If the part falls and is lost, a replacement (GE
p/n 64G2262-001A) will be needed. In addition, the metal case
on the iButton could fall into the lower cores. If this occurs,
Caution the core would require disassembly to locate the part because it
could cause the shorting of other electronics.
6. Remove the iButton (round cell) from the old board.

7. Replace the iButton on the new board with the one taken from the old board.
8. Connect the new PMVD. Make sure it is fully inserted into the slots on the mounting
base.
9. Connect the Ethernet and power cables back into the PMVD and re-energize the
equipment.
If the Auto-Reconfiguration feature is enabled and the Mark

VIe controller detects the I/O module running with a different
configuration, a reconfiguration file is automatically downloaded
from the controller to the I/O module. Refer to the section,
Attention Auto-Reconfiguration.

Replacing a PMVP
When replacing a single PMVP, Ø To replace an existing PMVP with a new PMVP
the remaining two PMVPs and
1. Locate and lock out/tag out the specific power feed to board being replaced.
the turbine will remain online,
provided there are no other 2. Open the P core front door and pull the two tabs at lower right and left to unlock the
fault conditions present. plastic frames holding the boards within.
Front Slot with PTBA Terminal Board and PMVP Module

3. Disconnect and tag the J7 (battery power from PDM), JK (ribbon to TCEB), JW
(335V to TCEB), JL (ribbon to trip board), and X3 (earth ground) cables.
4. Disconnect and tag the Ethernet cable to the processor daughterboard.
5. Remove the old PMVP assembly from the plastic frame, releasing the plastic tabs
along the top and bottom of the board frame.
6.
Do not attempt to handle, remove, or secure the iButton with

the board held vertically, as the clip internal spring will likely
propel the part. If the part falls and is lost, a replacement
(GE p/n 64G2262-001A) will be needed. In addition, the
metal case on the iButton could fall into the lower cores. If
Caution this occurs, the core would require disassembly to locate the
part because it could cause the shorting of other electronics.
On a table or other flat horizontal surface, open the packaging for the new PMVP.
Remove the iButton ID located next to the processor board and put it aside as a spare.
7. Remove the iButton from the old PMVP and insert it into the new PMVP.
8. Verify that the iButton is securely held within its mounting clip (there are two tabs
at “9:00” and “3:00”).

9. Record the iButton code.
10. Install the PMVP into the plastic frame, oriented with the processor daughterboard
towards the upper left.
11. Reconnect the J7, JK, JL, and X3 cables.
12. Connect the Ethernet cable to the upper processor daughterboard’s RJ-45 connector.
Allow the cable to flow to the left wall and down to the bottom of the slot. Spiral wrap
recommended around the cables where they exit the cores to protect against chaffing.
Leave enough slack in the cable loop to allow the movement of the frames.
13. Startup the control system.
Refer to GEH-6700, ToolboxST 14. If the iButton was not used from the existing PMVP or if Auto-Reconfiguration is not
User Guide for Mark VIe enabled, use the ToolboxST application to reconfigure the PMVP module as needed.
Control, Chapter 7 Work Online Run the download scan wizard to initiate the required download.
With a Mark VIe Component.
the section Download Wizard. If the Auto-Reconfiguration feature is enabled and the Mark
VIe controller detects the I/O module running with a different
configuration, a reconfiguration file is automatically downloaded
from the controller to the I/O module. Refer to the section,
Attention Auto-Reconfiguration.
Replacing J-type Boards
Ø To replace the board

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 T-type Boards
Ø To replace the board
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.

Ordering 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 board’s functional acronym, displayed below, is normally based on
the board description, or name.
Board Part Number Conventions

Note I/O packs follow the same board part number convention except Functional
revision is listed after rev. on the label, and they do not have an Artwork revision.
I/O Pack Part Number Convention

Note The modules follow the same board part number convention except Functional
revision is listed after rev. on the label, and they do not have an Artwork revision.
Placing the Order

Renewals/spares (or those When ordering, be sure to include the following items:
not under warranty) should
be ordered by contacting the • Complete part number and description
nearest GE Sales or Service • Serial number
Office, or an authorized GE
Sales Representative. • Material List (ML) number
Note All digits are important when ordering or replacing any board. The factory
may substitute newer board versions based on availability and design enhancements,
however, GE Energy ensures backward compatibility of replacement boards.

GE Energy
1501 Roanoke Blvd.
1 540 387 7000

www.geenergy.com

GEH-6800 - Vol - II 2 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GEH-6800 - Vol - II 2 PDF

Uploaded by

Copyright:

Available Formats

GE Energy GEH-6800_Vol_II

Mark* VIe Control

© 2011 General Electric Company, USA. All rights reserved.

* Trademark of General Electric Company

We welcome comments and suggestions to make this publication more useful.

Excellent Good Fair Poor Additional Comments

Superior Comparable Inferior Do not know Comments .............................................

........................................................................................Fold here first........................................................................................

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

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

Indicates a procedure, condition, or statement that should be

This equipment contains a potential hazard of electric shock,

Isolation of test equipment from the equipment under test

Warning To minimize hazard of electrical shock or burn, approved

To prevent personal injury or equipment damage caused by

Always ensure that applicable standards and regulations are

2 Contents Mark VIe Control Migration from Mark V Control

ARCNET Interface (PIOA)

Infrared Port Not Used

PIOA I/O pack Mounted on JPDV Terminal Board and PMVE

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-1

Ø To install the PIOA I/O pack

If the configuration being downloaded contains I/O packs with

1-2 Mark VIe Control Migration from Mark V Control

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-3

1-4 Mark VIe Control Migration from Mark V Control

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-5

1-6 Mark VIe Control Migration from Mark V Control

Modify Data Modify Design

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-7

1-8 Mark VIe Control Migration from Mark V Control

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-9

1-10 Mark VIe Control Migration from Mark V Control

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-11

1-12 Mark VIe Control Migration from Mark V Control

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-13

Core Location Revision

Jumper Isolates Position Application Notes

DTBB Jumper Configuration

Jumper Isolates Position Application Notes

1-14 Mark VIe Control Migration from Mark V Control

Jumpers Position Application Notes

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-15

Jumpers Position Application Notes

1-16 Mark VIe Control Migration from Mark V Control

• Bad/Disconnected RS-485 cable; Digital and Protections cores powered down

• Replace/reconnect RS-485 cable; power up the cores

• No ARCNET devices on the network

• Reconnect or replace the ARCNET cable.

• The PIOA only supports a 40 ms controller frame rate.

• Set the controller frame rate to 40 ms

• Bad/disconnected RS-485 cable; TCDA powered down; hardware failure

• Replace/reconnect RS-485 cable; power up the cores; replace TCDA if necessary

GEH-6800_Vol_II PIOA ARCNET® Interface Module System Guide 1-17

• Bad/disconnected RS-485 cable; TCEA powered down; hardware failure

• Replace/reconnect RS-485 cable; power up the cores; replace TCEA if necessary

• Verify the I/O configuration against the jumper settings

Note A reboot of the PIOA is required to clear this diagnostic alarm.

• Verify the I/O configuration against the EPROM revision

• Verify the I/O configuration against the EPROM revision

1-18 Mark VIe Control Migration from Mark V Control

• TCDA Memory error

• Cycle power on TCDA