100% found this document useful (1 vote)
555 views338 pages

GEH-6729H Vol2

Uploaded by

Jorge Contreras
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
555 views338 pages

GEH-6729H Vol2

Uploaded by

Jorge Contreras
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 338

GE Energy GEH-6729H

Mark* Ve Control, Volume II


Application Guide
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.

© 2007 – 2010 General Electric Company, USA. All rights reserved.


Revised: 2010-11-03
Issued: 2007-05-18

* 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.
Salem, VA 24153–6492 USA

........................................................................................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

Note Indicates an essential or important procedure, condition, or statement.

Tip Ä Provides essential information that is not normally defined in regular use but
from an experienced user.

A margin note is used to


emphasize a specific statement
or provide a reference.
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.

To minimize hazard of electrical shock or burn, approved


Warning 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
PIOA I/O Interface Module .................................................................................................... 1-1
IONet and ARCNET® Interface (PIOA) ...........................................................................................1-1
PIOA Specific Alarms ....................................................................................................................1-29
Common Module Alarms...............................................................................................................1-66
JPDV Terminal Board ....................................................................................................................1-67
PMVE Mark Ve Control I/O Module ....................................................................................... 2-1
Mark VIe Control I/O Communication (PMVE) ................................................................................2-1
PMVE Specific Alarms ..................................................................................................................2-14
Common Module Alarms...............................................................................................................2-38
MVRA I/O Interface Board.............................................................................................................2-39
MVRB I/O Interface Board.............................................................................................................2-78
MVRC I/O Interface Board ............................................................................................................2-94
MVRF I/O Interface Board...........................................................................................................2-104
HSLA Interface ............................................................................................................................2-131
Common Module Content...................................................................................................... 3-1
Auto-Reconfiguration.......................................................................................................................3-1
Hardware Jumpers ..........................................................................................................................3-2
Common Module Alarms.................................................................................................................3-4
Signal Flow Diagrams ............................................................................................................ 4-1
Reference........................................................................................................................................4-1
Signal Flow Diagrams ...................................................................................................................4-10
Power Distribution Diagrams ............................................................................................... 5-1
Overview .........................................................................................................................................5-1
Power Distribution Core <PD> Diagrams........................................................................................5-3
Replacement and Ordering.................................................................................................... 6-1
Replacement ...................................................................................................................................6-1
Ordering a Board.............................................................................................................................6-4

GEH-6729H Contents 1
Notes

2 Contents Mark* Ve Control, Volume II


PIOA I/O Interface Module

IONet and ARCNET® Interface (PIOA)


Functional Description
The IONet ARCNET (PIOA) I/O pack provides an interface between the newer Mark* Ve
control Ethernet IONet and the existing Mark V control RS-485 IONet or the excitation
control ARCNET. The PIOA provides an interfaces to the I/O boards TCDA and TCEA.
The I/O pack mounts to the JPDV terminal board through a 37-pin connector. The LAN
connections (IONet and ARCNET) 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. There is a separate IONet
PIOA for each core (R, S, T, and C), if the system is TMR. Excitation control ARCNET
adds a single PIOA to <C> core for simplex applications or a single PIOA to <R> and
<C> cores for redundant applications.

Infrared port not used

Two PIOA Packs on a JPDV Board in a Mark Ve Core

GEH-6729H PIOA I/O Interface Module Application Guide 1-1


Installation
The PIOA I/O pack only mounts to the JPDV terminal board. JPDV has two DC-37
pin connectors labeled JA1 and JB1. If the interface is an ARCNET interface to the
excitation control, the PIOA mounts to the JA1 connector. If the interface is an RS-485
IONet interface to the Mark V TCDA and TCEA I/O boards, the PIOA mounts to the
JB1 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 correct terminal board connector (JA1 or JB1).
Plug the pack into JA1 for an ARCNET excitation control interface. Plug the pack
into JB1 for a RS-485 IONet interface.
3. Mechanically secure the packs using the threaded studs adjacent to the Ethernet ports.
The studs slide into a mounting bracket specific to the terminal board type. The
bracket location should be adjusted such that there is no right-angle force applied to
the DC-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 pack
will operate over either port. If dual connections are used, the standard practice is to
connect ENET1 to the network associated with the R controller.
5. Apply power to the pack by plugging in the connector on the side of the pack. It is
not necessary to insert this connector with the power removed from the cable as
the I/O pack has inherent soft-start capability that controls current inrush on power
application.
6. Configure the I/O pack as necessary.

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 ToolboxST Download
Attention Wizard again.

1-2 Mark* Ve Control, Volume II


Operation

Processor
The processor board is common to the Ethernet I/O packs. 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, including sequencing and monitoring

The processor board connects to an acquisition board specific to the I/O pack or 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 pack or 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 pack 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 pack or 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.

Auto-Reconfiguration
Refer to the Auto-Reconfiguration section in the Common Module Content chapter.

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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-3


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 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 the RS-485 IONet signals
• 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

Input/Output Signals
The I/O interface acquisition board (BIOA) has a UART to interface the processor to the
RS-485 IONet, 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.

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.

1-4 Mark* Ve Control, Volume II


RS-485 IONet
Ø To add a PIOA module for RS-485 IONet 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-5


1-6 Mark* Ve Control, Volume II
For a typical TMR system, there are two TCDA boards and one TCEA board per core
(total of three). For a typical Simplex system, there are one TCDA board and three TCEA
boards attached to the RS-485 IONet. Physical Position refers only to the order of terminal
boards in this list. The actual order of the terminal boards is fixed within the PIOA.

GEH-6729H PIOA I/O Interface Module Application Guide 1-7


Ø To configure the RS-485 IONet
1. From the Component Editor Tree View, select the desired PIOA.
2. Click the Parameters tab in the Summary View.

1-8 Mark* Ve Control, Volume II


Certain protection parameters must match their corresponding protection jumper
configurations on TCEA. These parameters are System, HPOverspeedTripFreq, and
LPOverspeedTripFreq. To calculate the overspeed jumper configuration, divide the
decimal value by 16 and convert the result into a binary value where each bit represents
the state of a jumper. For the System Configuration parameter, the parameter values
are 1Simplex, 2-LM, and 3-TMR.

Binary Bit Values 512 256 128 64 32 16 8 4 2 1


HP Overspeed Trip Jumpers: J21 J20 J19 J18 J17 J16 J15 J14 J13 J12
Positions for 3960 RPM: 0 0 1 1 1 1 1 1 1 0
System Configuration Jumper Positions: J29 J28
Positions for TMR: 1 1
LP Overspeed Trip Jumpers: J27 J26 J25 J24 J23 J22 J11 J10 J9 J8
Positions for 0 RPM: 0 0 0 0 0 0 0 0 0 0

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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-9


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

1-10 Mark* Ve Control, Volume II


GEH-6729H PIOA I/O Interface Module Application Guide 1-11
Ø 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.

Specifications
Item Specification
Number of channels One RS-485 IONet channel 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 IONet filtering and termination is on the JPDV terminal board.
Frame rate RS-485 IONet has a 32 Hz frame rate.
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 (DLAN+ or RS-485 IONet)
Temperature -30 to 65 ºC (-22 to 149 ºF)

1-12 Mark* Ve Control, Volume II


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 (DLAN+ or RS-485 IONet).

Communication LEDs
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 IONet data bytes are being received by PIOA.
• Tx flashes when RS-485 IONet data bytes are being transmitted by PIOA.

GEH-6729H PIOA I/O Interface Module Application Guide 1-13


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 pack is transmitting or
receiving data over the port
Red / Green ATTN Shows I/O pack status

I/O Pack Status

LED Flashing Pattern Description Software Version


Red LED out There are no detectable problems with the I/O pack. All
ATTN
LED solid on A critical fault is present that prevents the I/O pack from operating. 3.04 or earlier
There could be hardware failures on the processor or acquisition
boards, or there is not any application code loaded.
4 Hz 50% An alarm condition is present in the I/O pack. These alarms include
wrong processor / terminal board combination, terminal board is
missing, or errors in loading the application code.
1.5 Hz 50% The I/O pack is not online.
0.5 Hz 50% This is used during factory testing to draw attention to the I/O pack.
Red Solid Booting - prior to reading Dallas ID 3.05 or later
ATTN
4 Hz 50% Diagnostic present
2 Hz 50% Awaiting an IP address
1 Hz 50% No Firmware to load (Program mode)
0.5 Hz 50% Application not loaded
Green Solid BIOS (at power on), but if it remains in this state, the I/O pack is
ATTN not functioning properly and should be replaced.
2 Hz 50% Awaiting Auto-Reconfiguration release
1 Hz 50% In WAIT or STANDBY mode
Two 4 Hz flashes Application online
every 4 sec

1-14 Mark* Ve Control, Volume II


Configuration
Parameter Description Choices
NetworkType The network protocol used IONet-485, ARCNET
TCDA1PromRev TCDA1 EPROM revision ** F1ACE, F1ACM, F1ACN,
F1BCE, F1BCM, F1BCN
TCDA2PromRev TCDA2 EPROM revision ** F1ACE, F1ACM, F1ACN,
F1BCE, F1BCM, F1BCN
TCDA3PromRev TCDA3 EPROM revision ** F1ACE, F1ACM, F1ACN,
F1BCE, F1BCM, F1BCN
TCEA1PromRev TCEA1 EPROM revision ** F1ACK, F1ACM, F1BEC
TCEA2PromRev TCEA2 EPROM revision ** F1ACK, F1ACM, F1BEC
TCEA3PromRev TCEA3 EPROM revision ** F1ACK, F1ACM, F1BEC
** The prom set revisions listed under the Choices column have been validated with the Mark Ve control system, and are
supported by the configuration tools. Other prom revisions exist, but should be replaced with one of the validated/supported
prom sets.
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 Mark Ve control synchronizing function adjusts the
defined Breaker Close Times by comparing the time the
breaker closure signal was sent from the Mark Ve control 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

GEH-6729H PIOA I/O Interface Module Application Guide 1-15


Parameter Description Choices
close time becomes eight cycles, the Mark Ve control
adjusts the five to an eight, taking three closures to make
this change. If the time required becomes nine cycles, the
Mark Ve control 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 Mark Ve
control 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.

1-16 Mark* Ve Control, Volume II


Parameter Description Choices
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 Mark Ve 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

If there is a mismatch between these values and the jumpers on the TCEA board, the
Mark Ve control system may not go into Controlling state.

Attention
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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-17


Parameter Description Choices
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 IONet-RS485 network 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 EX2000 has only one master TRUE, FALSE
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

1-18 Mark* Ve Control, Volume II


Parameter Description Choices
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 Mark V binary FreqLow, Percent, Degrees
fix point notation to Mark Ve 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

GEH-6729H PIOA I/O Interface Module Application Guide 1-19


TCDA Jumper Configuration
Core Location Revision
<QDn> 1,2,3 Rev. TCDAG#A,
TCDAG#B, or TCDAH#B
<CD> 1
<DD> 1,3

Jumper Position Default Position Application Notes


J1 Off On = factory test Board test enable
OFF for proper operation
J2 In = Terminated Out = not terminated IONet termination resistor
J3
J6 0 Binary weighted IONet Address
J5 0 value This configuration varies for:
J4 0 <QDn>,<CD>,<DD>
1 1
See next table
1 2
1 4
J7 1 = enable 0 = disable Enable stall timer
Enable = normal operation
J8 In = operate Out = test mode Test enable
In = normal operation
JP9 B = 16 A = 11.7 IONet frequency (applies only to
TCDAH#B):
B for all DS200TCDAF1B prom sets,
and F1A prom sets with rev CI and
above; A for DS200TCDAF1A prom
sets up to and including rev CE

TCDA Binary Summation Board Addressing - J4, J5, J6

CORE Location Address J4 J5 J6


<QD1> 1 0 0 0 0
<QD2> 2 1 0 0 1
<CD> 1 0 0 0 0
<DD> 1 0 0 0 0
<DD> 3 1 0 0 1

1-20 Mark* Ve Control, Volume II


TCEA Jumper Configuration

Option One

Core Location Revision


<P> 1 <X> Rev. TCEAG#A
3 <Y>
5 <Z>

Jumper Default Position Position Binary Value Application Notes


J1 0 1 = test Test Function: 1 = Enable
J2 0 1 = term IONet termination resistors
J3 0 = resistors not connected

J4 Refer to Note 1 table 1 IONet address


J5 2 This configuration varies for X,Y,Z
J6 4
J8 Application-specific 1 Base frequency, low-pressure shaft
J9 2 Refer to Note 2 table
J10 4
J11 8
J12 Application-specific 1 Base frequency, high-pressure shaft
J13 2 Refer to Note 3 table
J14 4
J15 8
J16 Application-specific 1 High-pressure shaft trip frequency
J17 2 Refer to Note 5 below
J18 4
J19 8
J20 16
J21 32
J22 Application-specific 1 Low-pressure shaft trip frequency
J23 2 Refer to Note 5 below
J24 4
J25 8
J26 16
J27 32
J28 Application-specific 1 Type of control application
J29 2 Refer to Note 4 table
J30 1 = enable 0 = stall disable Stall function: must be in position 1.
J31 In Out Factory test. Install for proper field
operation.

GEH-6729H PIOA I/O Interface Module Application Guide 1-21


Note 1

TCEA - X,Y,Z board definition determined according to binary summation


Board Address J4 J5 J6
X 4 1 0 0
Y 5 1 0 1
Z 6 1 1 0

Note 2

TCEA - Base frequency of the speed sensors for the low-pressure shaft of a dual shaft machine. Select table
frequency, which is the closest to: {rated RPM * #teeth /60 sec/min}.
Frequency J11 J10 J9 J8
2880 *** 0 1 1 0
3300 0 0 0 1
4150 *** 0 1 0 1
4670 0 0 1 0
4980 0 0 1 1
6500 0 1 0 0
Not Used ** 0 0 0 0
** Not Used is the default setting for single shaft machines.
*** Available with TCEAFIACJ or later proms

Note 3

TCEA - Base frequency of the speed sensors for a single shaft machine or the high-pressure shaft of a dual shaft
machine. Select table frequency, which is the closest to: {rated RPM * #teeth/60 sec/min}.
Frequency J15 J14 J13 J12
3000 0 0 0 1
3600 0 0 1 0
3980 ** 1 0 0 1
4800 0 0 1 1
4860 0 1 0 0
5100 0 1 0 1
7100 0 1 1 0
7491 0 1 1 1
7833 1 0 0 0
Not Used 0 0 0 0
** Available with TCEAFIACK or later PROMS.

1-22 Mark* Ve Control, Volume II


Note 4

TCEA - Type of Control Application


Type of Application J29 J28
LM2500 or LM 5000 0 1
Simplex 1 0
All other 1 1

Note 5: TCEA– High-pressure and low-pressure shaft trip frequency is the pulses per
second from the speed sensors (magnetic pickups) that result in an emergency overspeed
trip.

Trip Frequency = Trip RPM * #teeth/60 sec/min = Base Frequency * {100 + Binary
Sum/4}/100

or, solving for Binary Sum,


Binary Sum = {(Trip Frequency/Base Frequency) -1} * 400

Where Binary Sum is the decimal equivalent of the binary weighted values.

For example:

Gas Turbine
. Rated RPM = 5100, Emergency Overspeed set to 112%, 60 teeth on pickup wheel.

Base Frequency = 5100 * 60/60 = 5100

Set J15 = 0, J14 = 1, J13 = 0, J12 = 1.

Binary Sum = {(5712/5100) - 1} * 400 = {1.12 - 1} * 400 = 48; in binary, 48 = 110000.

Set J21 = 1, J20 = 1, J19 = 0, J18 = 0, J17 = 0, J16 = 0.

SteamTurbine
. Rated RPM = 3600, Emergency Overspeed set to 110%, 160 teeth on pickup wheel.

Base Frequency = 3600 * 160/60 = 9600. Set J15 = 1, J14 = 0, J13 = 0, J12 = 0.

Binary Sum = {(3690/3600) - 1} * 400 = 40; in binary, 40 = 101000.

Set J21 = 1, J20 = 0, J19 = 1, J18 = 0, J17 = 0, J16 = 0.

GEH-6729H PIOA I/O Interface Module Application Guide 1-23


Option Two

Core Location Revision


<P> 1 <X> Rev. TCEAG#B
3 <Y>
5 <Z>

Jumper Position Binary Value Application Notes


0 1 = test Test Function: 1 = Enable
J1
J2 0 1 = termination RS-485 IONet termination
J3 resistors resistors; 0 = resistors not
connected
J4 Refer to Note 1 table for TCEAG#A 1 RS-485 IONet address; this
J5 2 configuration varies for X, Y, and
J6 4 Z locations
J8 Application-specific 1 Low-pressure shaft trip frequency
J9 2 Refer to Note 6, next page
J10 4
J11 8

J22 16
J23 32
J24 64
J25 128
J26 256
J27 512
J12 Application-specific 1 High-pressure shaft trip frequency
J13 2 Refer to Note 6
J14 4
J15 8

J16 16
J17 32
J18 64
J19 128
J20 256
J21 512
J28 Application-specific 1 Type of control application
J29 2 Refer to Note 4 for TCEAG#A
J30 1 = enable 0 = stall disable Stall function: must be in position
1
J31 In Out Factory test. Install for proper
field operation.

1-24 Mark* Ve Control, Volume II


Note 6: TCEA– High-pressure and low-pressure shaft trip frequency is the pulses per
second from the speed sensors (magnetic pickups) that result in an emergency overspeed
trip. For the G#B vintage of the TCEA, the exact frequency is set in the Mark VIe
Parameters tab of a configured module. The binary value of the jumpers MUST be equal
to the selected trip frequency divided by 16.

Binary Value = (Trip Frequency/16)

Where Binary Value is the hexadecimal equivalent of the binary weighted values.

The following tables show the structure for the HP and LP settings:

HP Decimal Hex J21 J20 J19 J18 J17 J16 J15 J14 J13 J12
Trip value value (512) (256) (128) (64) (32) (16) (8) (4) (2) (1)
(Hz)
16383 1023 3FF 1 1 1 1 1 1 1 1 1 1 Max
16 1 001 0 0 0 0 0 0 0 0 0 1 Min
0 0 000 0 0 0 0 0 0 0 0 0 0 Shaft
not
used

LP Decimal Hex J27 J26 J25 J24 J23 J22 J11 J10 J9 J8
Trip value value (512) (256) (128) (64) (32) (16) (8) (4) (2) (1)
(Hz)
16383 1023 3FF 1 1 1 1 1 1 1 1 1 1 Max
16 1 001 0 0 0 0 0 0 0 0 0 1 Min
0 0 000 0 0 0 0 0 0 0 0 0 0 Shaft
not
used

Example:

HP shaft overspeed trip frequency set to 3960 (110% of 3600)

3960/16 = 247.5 ===> round DOWN (always) to 247 decimal = 0F7 Hex

0 F 7
J21 J20 J19 J18 J17 J16 J15 J14 J13 J12
0 0 1 1 1 1 0 1 1 1

GEH-6729H PIOA I/O Interface Module Application Guide 1-25


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 dv 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


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

Jumper Isolates Position Application Notes


BJ1 47–56 In = Connect +125 Out = Disconnect Remove for testing only. Isolates the 125
V dv Interrogation +125 V dc V dc positive bus from the output wiring
BJ2 57–66
voltage to contact Interrogation to help troubleshoot ground faults on the
BJ3 67–76 inputs voltage from 125 V dc system. Refer to Appendix C,
BJ4 77–86 contact inputs page 3–14.

BJ5 87–96

1-26 Mark* Ve Control, Volume II


DTBC Jumper Configuration
Core Location Revision
<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 Refer to Appendix C, page 3–15
11
12
13
14
15
16
17
18

GEH-6729H PIOA I/O Interface Module Application Guide 1-27


DTBD Jumper Configuration
Core Location Revision
<QDn>
9
<CD> Rev. DTBDQ#A
optional

Jumpers Position Application Notes


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
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 Refer to Appendix C page 3–16
11
12
13
14
15
16

PTBA Jumper Configuration

Core Location Revision


<P> 6 Rev. PTBAQ#A

Jumper Position Application Notes


BJ1 In = Enabled Out = Disabled Local audible alarm enable
ALM Remove to silence alarm
Refer to Figure C-68.

1-28 Mark* Ve Control, Volume II


PIOA Specific Alarms
33
Description Complete loss of communication with IONet-485.

Possible Cause

• Bad/Disconnected RS485 cable; Digital and Protections cores powered down

Solution

• Replace/reconnect RS485 cable; power up the cores

34
Description Complete loss of communication with ARCNET.

Possible Cause

• Bad/Disconnected ARCNET cable; no ARCNET devices on the network

Solution

• Replace/reconnect 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 RS485 cable; TCDA powered down; hardware failure

Solution

• Replace/reconnect RS485 cable; power up the cores; replace TCDA if necessary

GEH-6729H PIOA I/O Interface Module Application Guide 1-29


53 - 55
Description Lost communication with TCEA[ ].

Possible Cause

• Bad/disconnected RS485 cable; TCEA powered down; hardware failure

Solution

• Replace/reconnect RS485 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

1-30 Mark* Ve Control, Volume II


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

• Unused diagnostic alarm

Solution

• Reset Diagnostic alarms

GEH-6729H PIOA I/O Interface Module Application Guide 1-31


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.

1-32 Mark* Ve Control, Volume II


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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-33


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 card only as a last resort.

1-34 Mark* Ve Control, Volume II


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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-35


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.

1-36 Mark* Ve Control, Volume II


2884-2886
Description TCEA[ ] is unused.

Possible Cause

• Unused diagnostic alarm

Solution

• Reset Diagnostic alarms

2887-2889
Description TCEA[ ] Memory changed

Possible Cause

• Unused diagnostic alarm

Solution

• Reset Diagnostic alarms

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

• Replace the TCEA board.

GEH-6729H PIOA I/O Interface Module Application Guide 1-37


2896-2898
Description TCEA[ ] HP base speed config trouble

Possible Cause

• Discrepancy between the IO configuration and the jumper settings associated with the HP base speed definition.

Solution

• Check the IO config against the jumper settings.

2899-2901
Description TCEA[ ] LP base speed config trouble

Possible Cause

• Discrepancy between the IO configuration and the jumper settings associated with the LP base speed definition.

Solution

• Check the IO config against the jumper settings.

2902-2904
Description TCEA[ ] HP over speed config trouble

Possible Cause

• Discrepancy between the IO configuration and the jumper settings associated with the HP over speed definition.

Solution

• Check the IO config against the jumper settings.

2905-2907
Description TCEA[ ] LP over speed config trouble

Possible Cause

• Discrepancy between the IO configuration and the jumper settings associated with the LP over speed definition.

Solution

• Check the IO config against the jumper settings.

1-38 Mark* Ve Control, Volume II


2908-2910
Description TCEA[ ] System config trouble

Possible Cause

• Discrepancy between the IO configuration and the jumper settings associated with the System config definition.

Solution

• Check the IO config against the jumper settings.

2911-2913
Description TCEA[ ] Trip board config trouble

Possible Cause

• Discrepancy between the IO configuration and the actual hardware;


i.e. the trip board TCT_
• The trip board must be as follows:
• Gas Turbine = TCTG;
Med Steam Turbine = TCTS;
Large Steam Turbine = TCTL;
Extended Large Steam= TCTE;
• It could also be bad connectivity in cable JL, TCEA;

Solution

• Check the IO config 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"; if cabling is OK, replace TCEA; if alarm still indicates trouble replace the trip
board TCT_.

GEH-6729H PIOA I/O Interface Module Application Guide 1-39


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

• Check the cabling on TCEA "JL"; if cabling is OK, replace TCEA; if alarm still indicates trouble replace the trip
board TCT_.

2920-2922
Description TCEA[ ] Digital output, 0ETR2

Possible Cause

• The relay driver circuitry associated with relay ETR2 is bad. The relationship is:

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


STM,TCTS
ETR2 [X] K8 K10 K10 K10
ETR2 [Y] K7 K4 K11 K4
ETR2 [Z] K9 K12 K12 K12

Solution

• Check the cabling on TCEA "JL"; if cabling is OK, replace TCEA; if alarm still indicates trouble replace the trip
board TCT_.

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

• Check the cabling on TCEA "JL"; if cabling is OK, replace TCEA; if alarm still indicates trouble replace the trip
board TCT_.

1-40 Mark* Ve Control, Volume II


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

• Check the cabling on TCEA "JL"; if cabling is OK, replace TCEA; if alarm still indicates trouble replace the trip
board TCT_.

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

• Check the cabling on TCEA "JL"; if cabling is OK, replace TCEA; if alarm still indicates trouble replace the trip
board TCT_.

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

• Check the cabling on TCEA "JL"; if cabling is OK, replace TCEA; if alarm still indicates trouble replace the trip
board TCT_.

GEH-6729H PIOA I/O Interface Module Application Guide 1-41


2935-2937
Description TCEA[ ] TMR check trouble, ETR1

Possible Cause

• The 3 ETR1 relays are not in agreement, i.e. 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.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


STM,TCTS
ETR1 [X] K5 K11 K4 K11
ETR1 [Y] K4 K5 K5 K5
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 3 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 3 ETR2 relays are not in agreement, i.e. 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.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

1-42 Mark* Ve Control, Volume II


2941-2943
Description TCEA[ ] TMR check trouble, PTR1

Possible Cause

• The 3 PTR1 relays are not in agreement, i.e. 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.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

2944-2946
Description TCEA[ ] TMR check trouble, PTR2

Possible Cause

• The 3 PTR2 relays are not in agreement, i.e. one is bad.

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.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-43


2947-2949
Description TCEA[ ] TMR check trouble, PTR3

Possible Cause

• The 3 PTR3 relays are not in agreement, i.e. one is bad.

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

• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [R] JL-15; [S]
JL-16; [T] JL-17. If still a problem replace the appropriate MVRA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

2950-2952
Description TCEA[ ] TMR check trouble, PTR4

Possible Cause

• The 3 PTR4/ETR3 relays are not in agreement, i.e. 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

• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [R] JL-18; [S]
JL-19; [T] JL-20. If still a problem replace the appropriate MVRA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

1-44 Mark* Ve Control, Volume II


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.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


STM,TCTS
ETR1 [X] K5 K11 K4 K11
ETR1 [Y] K4 K5 K5 K5
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 3 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.

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.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


STM,TCTS
ETR1 [X] K8 K10 K10 K10
ETR1 [Y] K7 K4 K11 K4
ETR1 [Z] K9 K12 K12 K14

• 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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-45


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

1-46 Mark* Ve Control, Volume II


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.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-47


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

• 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 RD3 failure diagnostic or a
PTR2 TMR check trouble diagnostic should be indicated. Verify that the PTR1 relay is not loose.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


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

• 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 RD3 failure diagnostic or a
PTR2 TMR check trouble diagnostic should be indicated. Verify that the PTR1 relay is not loose.

Gas,TCTG MED LG STM,TCTL LG STM,TCTE


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.
• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [X] JL-15; [Y]
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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

1-48 Mark* Ve Control, Volume II


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

• 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 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;
• If replacing the trip board does not fix the problem, replace TCEA and/or check cable "JL" continuity [X] JL-15; [Y]
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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-49


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

2980-2982
Description TCEA[ ] Loopback, solenoid, ETD1/SOL1/MTSV

Possible Cause

• This diagnostic is checking a composite function, i.e. 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,
i.e. cable JL, TCT_, TCEA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

1-50 Mark* Ve Control, Volume II


2983-2985
Description TCEA[ ] Loopback, solenoid, ETD2/SOL2/ETSV

Possible Cause

• This diagnostic is checking a composite function, i.e. 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.

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, i.e. cable JL, TCT_, TCEA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-51


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, i.e. 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, i.e. cable JL, TCT_, TCEA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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)
• 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:


• 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, i.e. cable JL, TCT_, or TCEA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

1-52 Mark* Ve Control, Volume II


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

SOL4 – Gas Turb, TCTG – solenoid #4


eqn is SOL4 = (ETR2 and PTR4)

MLO – Large Steam, TCTL – mech Lockout valve


eqn is MLO = relay MLO
• 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:


• 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, i.e. cable JL, TCT_, or TCEA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

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, i.e. cable JL, TCT_, or TCEA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-53


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, i.e. cable JL, TCT_, or TCEA.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

2998-3000
Description Unused diagnostic alarm

Possible Cause

• Unused diagnostic alarm

Solution

• Reset Diagnostic alarms

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?

1-54 Mark* Ve Control, Volume II


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_.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

• Proper identification of the failed card may require removal of 2of the 3 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
eqn: [(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 gen breaker does not have an excessive closure
time and that the configured bkr 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
eqn: [(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 gen breaker does not have an excessive closure
time and that the configured bkr 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-55


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

3017-3019
Description TCEA[ ] 52GX 125 V dc voltage missing

Possible Cause

• The gen 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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

1-56 Mark* Ve Control, Volume II


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

3023-3025
Description TCEA[ ] Relay trouble, K4-2

Possible Cause

• Protection relay k4-2, on the TCT_ trip board, is out of step with the majority.
• Med/Large Steam, TCTS/TCTL: k4- 2 = k21
Gas Turb, TCTG: k4-2 = k23

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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-57


3026-3028
Description TCEA[ ] Relay trouble, K4-3

Possible Cause

• Protection relay k4-3, on the TCT_ trip board, is out of step with the majority.
• Med/Large Steam, TCTS/TCTL: k4- 3 = k22
Gas Turb, TCTG: k4-3 = k24

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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

3029-3031
Description TCEA[ ] Relay trouble, K4-4

Possible Cause

• Protection relay k4-4, on the TCT_ trip board, is out of step with the majority.
• Med/Large Steam, TCTS/TCTL: k4- 4 = k23
Gas Turb, TCTG: k4-4 = k25

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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

1-58 Mark* Ve Control, Volume II


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

• 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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

GEH-6729H PIOA I/O Interface Module Application Guide 1-59


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.

Note Since the feedback signal for monitoring this condition is connected to all 3 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.

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
Description TCEA[ ] Power supply out of limits, P15

Possible Cause

• The TCEA P15V is out of limits.

Solution

• Replace the TCEA board.

3050-3052
Description TCEA[ ] Power supply out of limits, N15

Possible Cause

• The TCEA N15V is out of limits.

Solution

• Replace the TCEA board.

1-60 Mark* Ve Control, Volume II


3053-3055
Description TCEA[ ] Power supply out of limits, P24

Possible Cause

• The TCEA P24V is out of limits.

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 aux 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
Description TCEA[ ] Power supply out of limits, P335

Possible Cause

• The TCEA P335 is out of limits.

Solution

• Replace TCEA.

GEH-6729H PIOA I/O Interface Module Application Guide 1-61


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.

1-62 Mark* Ve Control, Volume II


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

• Med Steam only, failed an emergency online overspeed system test.

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

• Med Steam only, failed an emergency online overspeed system test.

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

• Med Steam only, failed an emergency online overspeed system test.

Solution

• Replace TCEA card, then MVRA card and then JD cables. Ensure IONet communications to TCEA are functioning.

GEH-6729H PIOA I/O Interface Module Application Guide 1-63


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-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
Description QD2 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.

3305-3400
Description QD3 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.

3409-3440
Description TMR P Core/Simplex R TCEA BooleanInputs "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.

1-64 Mark* Ve Control, Volume II


3457-3488
Description Simplex S TCEA BooleanInputs "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.

3505-3536
Description Simplex T TCEA BooleanInputs "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.

3561-3565
Description TMR P Core/Simplex R TCEA Analog "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",

Possible Cause

• A problem with a status input. This could be the device, the wire to the terminal board, or the terminal board.

3566-3573
Description TMR P Core/Simplex R TCEA FlameDetector "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",

Possible Cause

• A problem with a status input. This could be the device, the wire to the terminal board, or the terminal board.

3574-3578
Description Simplex S TCEA Analog "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",

Possible Cause

• A problem with a status input. This could be the device, the wire to the terminal board, or the terminal board.

3579-3586
Description Simplex S TCEA FlameDetector "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",

Possible Cause

• A problem with a status input. This could be the device, the wire to the terminal board, or the terminal board.

GEH-6729H PIOA I/O Interface Module Application Guide 1-65


3587-3591
Description Simplex T TCEA Analog "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",

Possible Cause

• A problem with a status input. This could be the device, the wire to the terminal board, or the terminal board.

3592-3599
Description Simplex T TCEA FlameDetector "Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]",

Possible Cause

• A problem with a status input. This could be the device, the wire to the terminal board, or the terminal board.

Common Module Alarms


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

1-66 Mark* Ve Control, Volume II


JPDV Terminal Board
Functional Description
JPDV is the power distribution board for the MVRA and MVRF, up to two controllers, an
Ethernet switch and up to two PIOA packs. The board is the interface for the PIOA pack
to the DLAN+ to the excitation control and the RS-485 IONet to TCDAs and TCEAs.

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 packs, if present.
5. Connect the RS-485 IONet LAN cable.
6. Connect the DLAN+ (ARCNET) coax cable the BNC connector.
7. Connect the Power In Cable, from the power supply.

Refer to figure, JPDV Power Distribution Board in the previous section.

GEH-6729H PIOA I/O Interface Module Application Guide 1-67


Operation
The JPDV board contains the DLAN+ filtering and passes the signal to BIOA through
the DC-37 pin connector. The board contains the RS-485 IONet termination and pull-up
and pull-down resistance, and passes the signal to the BIOA through the DC-37 pin
connector. The JPDV routes power to the PIOA packs, the controllers, the MVRA and
MVRF and the Ethernet switch.

Specifications
Item Specification
Number of channels One DLAN+(ARCNET) channel
One RS-485 IONet channel
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.

1-68 Mark* Ve Control, Volume II


PMVE Mark Ve Control I/O Module

Mark VIe Control I/O Communication (PMVE)


Functional Description
The Mark* Ve control PMVE (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, and MVRF 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 control
processor board that is loaded with specific software and combined with one of the Mark
Ve 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
application. 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.

Installation
The PMVE mounts to the Mark Ve control location 1 plate.

Mark Ve Control Location1 Device Layout

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-1


Ø 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 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 system, and then start the ToolboxST*
Attention Download Wizard again.

Operation
Control software can be The PMVE is loaded with configuration parameters specific to its application. The
modified online without being IEEE® 1588 protocol is used through the IONets to synchronize the clock for the PMVE
restarted. 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 ms.

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 attemped, the Enter Password
dialog box displays. All protected functions performed during the remainder of the
ToolboxST session do not require re-entering the password.

2-2 Mark* Ve Control, Volume II


Adding a 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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-3


2-4 Mark* Ve Control, Volume II
GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-5
Adding the MVRx Board
Ø To add the MVRx board
1. From the Component Editor, click the Hardware tab.

2. The Configure Sub-Assembly dialog box displays.

2-6 Mark* Ve Control, Volume II


3. Make desired changes to the configuration, then click OK.

Note To add additional boards, select another Port item and follow the same procedure.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-7


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.

UCSA Setup
Ø To configure the PMVE's UCSA Processor

2-8 Mark* Ve Control, Volume II


1. From the Hardware tab Tree View, right-click the PMVE module and select
Setup. The I/O Pack Setup Wizard displays.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-9


2. When the Welcome wizard displays, click Next.

2-10 Mark* Ve Control, Volume II


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
The recalibration of a MVRA or MVRF servo is required when a new terminal board is
used on a system. The controller saves the barcode of the terminal board and 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. Liquid Fuel
regulators do not have to be recalibrated (where applicable).

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-11


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
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 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.

2-12 Mark* Ve Control, Volume II


UCSA LEDs
• Power displays solid green when the internal 5 V supply is up and regulating. The
PMVE 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 PMVE is online and running application code.
• Flash flashes amber when any flash device is being accessed. DC is not used in
the PMVE application.
• Diag displays solid red when the PMVE 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 PMVE 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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-13


PMVE Specific Alarms
The following alarms are specific to the PMVE I/O pack.

5400–5400,
8400–8400
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.

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 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 MVRF or terminal board failure if other thermocouples are
working correctly.
• Check the thermocouple for open circuit.
• Verify that the incoming mV signal does not exceed -63 mV.
• Verify that the thermocouple type matches the configuration.

2-14 Mark* Ve Control, Volume II


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.

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 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 the thermocouple for an open circuit.
• Verify that the incoming mV signal does not exceed -63 mV.
• Verify that the thermocouple type matches the configuration.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-15


5401-5430,
8401-8430
Description Vibration Input Sensor [ ] unhealthy ([ ])

Possible Cause

• Incorrect configuration for sensor type


• Open circuit
• Faulty transducer

Solution

• Verify that the sensor configuration matches the connected sensor type.
• Check field wiring, including shields.
• Replace the sensor.

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.

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.

2-16 Mark* Ve Control, Volume II


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 the field wiring and connections to the indicated analog input channel.
• Check the field device for failure.
• Check the ground select jumper for the input.
• Verify that the inputs are in operable range (-10 V to 10 V).

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).

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-17


5421-5435,
8421-8435
Description Analog 4-20 mA Input [ ] unhealthy ([ ] mA)

Possible Cause

• Excitation to transducer wrong or missing


• Faulty transducer
• Analog input current input beyond the specified range
• Open or short-circuit on input

Solution

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

5421-5435,
8421-8435
Description Analog 4-20 mA Input [ ] unhealthy ([ ] mA)

Possible Cause

• Excitation to transducer wrong or missing


• Faulty transducer
• Analog input current input beyond specified range
• Open or short-circuit on input

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-5439,
8436-8439
Description LVDT Excitation [ ] Failed

Possible Cause Faulty cable between terminal and acquisition card

Solution Inspect cable and replace, if needed.

2-18 Mark* Ve Control, Volume II


5436-5447,
8436-8447
Description Vibration Input for Seismic (Velocity) Sensor [ ] unhealthy ([ ])

Possible Cause

• Faulty transducer
• 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.

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

• Excitation to transducer wrong or missing


• Faulty transducer
• Analog input current input beyond the specified range.
• Open or short-circuit on input

Solution

• Check field wiring and connections to 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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-19


5448-5455,
8448-8455
Description LVDT [ ] Position Out of Limit ([ ] Vrms)

Possible Cause

• Excitation voltage to LVDT incorrect


• Faulty transducer
• Open or short-circuit on LVDT
• LVDT input out of range
• LVDT not calibrated

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.
• Check the LVDT sensor.
• Calibrate the servo regulator with the proper LVDT.
• Verify the configuration limits, MinVrms and MaxVrms.
• Verify that PosMargin is set to the proper value.

5448-5465,
8448-8465
Description LVDT [ ] Position Out of Limit ([ ] Vrms)

Possible Cause

• Excitation voltage to LVDT incorrect


• Faulty transducer
• 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.

2-20 Mark* Ve Control, Volume II


5450-5465,
8450-8465
Description LVDT [ ] Position Out of Limit ([ ] Vrms)

Possible Cause

• Excitation voltage to LVDT is incorrect


• Faulty transducer
• 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 MVRB 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.

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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-21


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.

2-22 Mark* Ve Control, Volume II


5464-5467,
8464-8467
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 the regulator inputs are connected to used sensor inputs in the configuration.

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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-23


5468-5471,
8468-8471
Description Servo [ ] Output Suicide Active

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
• Regulator feedback out of range
• Servo current feedback differs from servo current command

Solution

• Check and correct the configuration parameters relating to the list of possible causes.
• 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.

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.

2-24 Mark* Ve Control, Volume II


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%.

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

• Check field wiring, including shields. Problem is usually not a MVRA or terminal 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.

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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-25


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.

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.
• Replace the acquisition card.

2-26 Mark* Ve Control, Volume II


5484-5490,
8484-8490
Description Pack internal reference voltage [ ] out of limits ([ ])

Possible Cause Calibration reference voltage more than ±5% from expected value

• Power supply issue


• Internal hardware failure

Solution

• Check the power supply voltages.


• Replace the acquisition card.

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.

5491-5497,
8491-8497
Description Pack internal null voltage[ ] out of limits ([ ])

Possible Cause Null voltage more than ±5% from expected value

• Power supply issue


• Internal hardware failure

Solution

• Check the power supply voltages.


• Replace the acquisition card.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-27


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

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
• Regulator feedback out of range
• Servo current feedback differs from servo current command

Solution

• Check and correct the configuration parameters relating to the list of possible causes.
• 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.

5498-5501,
8498-8501
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 range of the output.


• Confirm the correct power supply voltage.
• Check the field wiring and device. Problem is usually not a MVRF or terminal board failure if other analog outputs are
working correctly.
• Replace the acquisition card.

2-28 Mark* Ve Control, Volume II


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.

5504-5509,
8504-8509
Description Output [ ] Total 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

Solution

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


• Confirm the correct power supply voltage.
• Check the field wiring and device.
• Replace the acquisition card.

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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-29


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

Possible Cause Review any additional diagnostics for possible causes.

• TMR_SuicLimit set too low


• Field wiring problem
• Command beyond range of output
• Software suicide requested
• Terminal board failure

Solution

• Check the field wiring and status of the 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.
• Verify that the software suicide request is not activated.

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.

2-30 Mark* Ve Control, Volume II


5525-5531,
8525-8531
Description Pack internal reference voltage [ ] out of limits ([ ])

Possible Cause Calibration reference voltage is more than ±5% from the expected value.

• Power supply issue


• Internal hardware failure

Solution

• Check the power supply voltages.


• Replace the acquisition card.

5526-5536,
8526-8536
Description Pack internal reference voltage [ ] out of limits

Possible Cause Calibration reference voltage more than ±5% from expected value

• Power supply issue


• Internal hardware failure

Solution

• Check the power supply voltages.


• Replace the acquisition card.

5528-5533,
8528-8533
Description Output [ ] Suicide relay non-functional

Possible Cause Analog output suicide relay command does not match feedback

• Relay failure on acquisition card


• Hardware failure

Solution If a hardware failure, 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

• Check the power supply voltages.


• Replace the acquisition card.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-31


5532-5538,
8532-8538
Description Pack internal null voltage[ ] out of limits ([ ])

Possible Cause Null voltage is more than ±5% from the expected value.

• Power supply issue


• Internal hardware failure

Solution

• Check the power supply voltages.


• Replace the acquisition card.

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.

5534-,
8534-8539
Description Output [ ] DAC Cmd Volts Disagrees with DAC feedback by 5%

Possible Cause Output command voltage disagrees with DAC feedback

Solution Replace the acquisition card.

5537-5547,
8537-8547
Description Pack internal null voltage[ ] out of limits

Possible Cause Null voltage more than ±5% from expected value

• Power supply issue


• Internal hardware failure

Solution

• Check the power supply voltages.


• Replace the acquisition card.

2-32 Mark* Ve Control, Volume II


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.

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 the correct power supply voltage.
• Check the field wiring and device. Problem is usually not a MVRB or terminal board failure if other analog outputs are
working correctly.
• Replace the acquisition card.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-33


5541-5542,
8541-8542
Description Output [ ] Total current feedback unhealthy ([ ] mA)

Possible Cause

• Commanded output beyond the range of output


• Field wiring problem
• Field device problem
• Open loop or too much resistance in loop

Solution

• Verify that the commanded output is within the range of the output.
• Confirm correct power supply voltage.
• Check field wiring and device.
• Replace acquisition card.

5541-5542,
8541-8542
Description Output [ ] Total 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

Solution

• Verify that the commanded output is within the range of the output.
• Confirm the correct power supply voltage.
• Check the field wiring and device.
• Replace acquisition card.

2-34 Mark* Ve Control, Volume II


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

Possible Cause

• Field wiring problem


• Connected device problems interfering with current
• Software suicide requested
• Hardware failure

Solution

• Cerify that sensor feedback is within limits.


• Verify that the software suicide request is not activated.

5545-5546,
8545-8546
Description Output [ ] 20/200 mA suicide active

Possible Cause Review any additional diagnostics for possible causes.

• TMR_SuicLimit set too low


• Field wiring problem
• Command is beyond output range
• Software suicide requested
• Terminal board failure

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.
• Verify that the software suicide request is not activated.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-35


5545-5546,
8545-8546
Description Output [ ] 20/200 mA suicide active

Possible Cause Review any additional diagnostics for possible causes.

• TMR_SuicLimit set too low


• Field wiring problem
• Command beyond range of output
• Software suicide requested
• Terminal board failure

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.
• Verify that the software suicide request is not activated.

5547-5548,
8547-8548
Description Output [ ] Suicide relay non-functional

Possible Cause Analog output suicide relay command does not match feedback.

• Relay failure on acquisition card


• Hardware failure

Solution If hardware failure, replace the acquisition card.

5549-5550,
8549-8550
Description Output [ ] Suicide relay non-functional

Possible Cause The analog output suicide relay command does not match the feedback.

• Relay failure on the acquisition card


• Hardware failure

Solution If hardware failure, replace the acquisition card.

2-36 Mark* Ve Control, Volume II


5549-5550,
8549-8550
Description Output [ ] Suicide relay non-functional

Possible Cause Analog output suicide relay command does not match feedback.

• Relay failure on acquisition card


• Hardware failure

Solution If hardware failure, replace 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

Solution Replace the acquisition card.

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.


• Replace the acquisition card.

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.
• Internal hardware failure

Solution

• Verify that the 200 mA jumpers are set correctly.


• Replace the acquisition card.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-37


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 each input type:

• 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.

5800-5831,
8800-8831,
5887-5910,
8887-8910,
5933, 5942,
8933, 8942
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.

5802-5807,
8802-8807
Description Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]

Possible Cause Voter disagreement detected between R and T I/O packs

Solution Adjust the LVDT_TMR_DiffLim on the Parameters tab.

Common Module Alarms


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

2-38 Mark* Ve Control, Volume II


MVRA I/O Interface Board
Functional Description
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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-39


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


1. Verify that power is removed from the core.
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, Adding the MVRx Board.

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 Mark V and Mark Ve 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 a TBD(name) power supply

All analog and digital I/O signals are read and written at the 5 ms rate by the PMVE(s).

2-40 Mark* Ve Control, Volume II


Regulator Diagrams

Position Regulator

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-41


Speed Ratio Regulator

2-42 Mark* Ve Control, Volume II


Speed Ratio PI control

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-43


Liquid Fuel Regulator

2-44 Mark* Ve Control, Volume II


Liquid Fuel with Position Feedback

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-45


Liquid Fuel PI Control

2-46 Mark* Ve Control, Volume II


Compressor Stall Algorithm

Compressor Stall Algorithm

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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-47


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.

2-48 Mark* Ve Control, Volume II


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
The recalibration of a MVRA or MVRF servo is required when a new terminal board is
used on a system. The controller saves the barcode of the terminal board and 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. Liquid Fuel
regulators do not have to be recalibrated (where applicable).

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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-49


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
&gt;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.

2-50 Mark* Ve Control, Volume II


Parameter Description Selections
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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-51


MVRA I/O Parameter Groups – Analog Inputs

Parameter Description Selections


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
enabled, a diagnostic is generated.
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.

2-52 Mark* Ve Control, Volume II


MVRA I/O Parameter Groups – Analog Outputs

Parameter Description Selections


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

Parameter Description Selections


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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-53


MVRA_IO Parameter Groups_LVDTs

Parameter Description Selections


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)
The absolute value in V rms read by the LVDT when the valve
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 V or Mark Ve. Excit_fromS, Excit_fromT
ExcitMonCal Excitation monitor calculated value in Vrms. Not available in 1 to 10 V (FLOAT)
Mark V or Mark Ve.

MVRA_IO Parameter Groups_Monitors

Parameter Description Selections


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

2-54 Mark* Ve Control, Volume II


MVRA_IO Parameter Groups_PT

Parameter Description Selections


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

Parameter Description Selections


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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-55


MVRA_IO Parameter Groups_Regulators

Parameter Description Selections


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.

2-56 Mark* Ve Control, Volume II


Parameter Description Selections
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
PositionInput2 Position input 2 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
PositionInput3 Position input 3 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 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,
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
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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-57


Parameter Description Selections
FlowInput2 Flow rate input 2 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
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
generated. The servo is suicided, if the EnabPressureFbkSuic
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
generated. The servo is suicided, if the EnabFlowFbkSuic 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
generating a suicide based on a transient condition.
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.

2-58 Mark* Ve Control, Volume II


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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-59


MVRA_IO Parameter Groups_Thermocouples

Parameter Description Selection


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

Parameter Description Selection


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


Core Location Revision
<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

2-60 Mark* Ve Control, Volume II


MVRA Specific Alarms

5400-5400,
8400-8400
Description Unallowed VarIOCompatCode Change: Old - [ ] New - [ ]

Possible Cause

• The configuration file located in flash storage does not match the firmware

Solution

• Compress the variables and rebuild the I/O pack. Download both the firmware and the application code

5401-5415,
8401-8415
Description Thermocouple [ ] Unhealthy ([ ])

Possible Cause

• Defective sensor reading or loose wire.

Solution

• Problem is usually not a MVRA or terminal board failure if other thermocouples are working correctly. The solution
may be one of the following:
− The board has detected a thermocouple open and applied a bias to the circuit, driving it to a large negative number,
or the TC is not connected, or a condition such as stray voltage or noise caused the input to exceed -63 mV.
− The thermocouple has been configured as the wrong type, or a stray voltage has biased the TC outside of its normal
range, or the cold junction compensation is wrong, or the thermocouple wiring is open.

5416-5416,
8416-8416
Description Cold Junction Unhealthy, Using Backup

Possible Cause

• Defective sensor reading on the terminal board. Defective reference voltage on MVRA

Solution

• 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).

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-61


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

Possible Cause

• Loose wire connection or defective sensor

Solution

• Problem is usually not a MVRA or terminal board failure if other analog inputs are working correctly. Check field wiring
including shields. Check ground select jumper for the 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

• Loose wire connection or defective sensor

Solution

• Problem is usually not a MVRA or terminal board failure if other analog inputs are working correctly. Check field
wiring including shields. Check ground select jumper for the input. Verify that inputs are in operable range (3.0-21.5
mA) Verify parameter settings for Min_MA_Input and Max_MA_Input.

5436-5447,
8436-8447
Description Vibration Input for Seismic (Velocity) Sensor [ ] unhealthy ([ ])

Possible Cause

• Dc reading is out of range

Solution

• Verify connection. Replace sensor.

5448-5465,
8448-8465
Description LVDT [ ] Position Out of Limit ([ ] Vrms)

Possible Cause

• Loose wire connection or defective sensor

Solution

• Problem is usually not a MVRA or terminal board failure if other LVDT inputs are working correctly. Check field
wiring including shields and LVDT Excitation. Calibrate servo regulator with the proper LVDT. Verify the MinVrms
and MaxVrms limits.

2-62 Mark* Ve Control, Volume II


5466-5469,
8466-8469
Description Monitor [ ] Invalid Servo Configuration

Possible Cause

• The monitor type does not match the regulator type

Solution

• Verify that the monitor and regulator configurations are identical to the ToolboxST application

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

Solution

• Calibrate one regulator at a time

5471-5471,
8471-8471
Description Calibration: Selected LVDT Max / Min Pos Limit Out of Range

Possible Cause

• The calibration min/max value exceeds the acceptable limits

Solution

• Check the regulator configuration for parameter 'PositionInput#1' for the particular Servo. Check the 'MaxPosValue' &
MinPosValue' for LVDT# Selected input in 'PositionInput#1'. The MaxPosValue for LVDT Input should be between
50% and 150%. The MinPosValue for LVDT Input should be between -50% and 50%.

5472-5482,
8472-8482
Description FlowRate [ ] Input unhealthy

Possible Cause

• Pulse rate input exceeds the maximum limit.

Solution

• Reduce pulse rate to within specifications.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-63


5485-5492,
8485-8492
Description Servo [ ] Disabled, Configuration error Fault No:[ ]

Possible Cause

• The regulator type is not defined by this firmware version

Solution

• Verify that the firmware version supports this regulator type.

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

Possible Cause

• Invalid/Incorrect Configuration: The following can cause this error


− 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

• Regulator feedback out of range


• Servo current feedback differs from servo current output

Solution

• Check and correct the configuration parameters for selected type of regulator. Check inputs are connected to used
sensor inputs in configuration.

5501-5508,
8501-8508
Description Servo [ ] Position Feedback out of range ([ ] %)

Possible Cause

• Sensor feedback out of range, software suicide requested

Solution

• Verify that sensor feedback is within limits

2-64 Mark* Ve Control, Volume II


5509-5516,
8509-8516
Description Servo [ ] Pressure Feedback out of range ([ ])

Possible Cause

• Sensor feedback out of range, software suicide requested

Solution

• Verify that sensor feedback is within limits.

5517-5524,
8517-8524
Description Servo [ ] Flow Feedback out of range ([ ])

Possible Cause

• Sensor feedback out of range, software suicide requested.

Solution

• Verify that sensor feedback is within limits

5525-5531,
8525-8531
Description Ref [ ] Reference Voltage out of limits ([ ])

Possible Cause

• A/D reference voltage is out of acceptable range.

Solution

• Replace the acquisition board or check power supply voltages.

5532-5538,
8532-8538
Description Null [ ] Null Voltage out of limits ([ ])

Possible Cause

• The null voltage not the correct specification.

Solution

• Replace the acquisition board or check power supply voltages.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-65


5534-5539,
8534-8539
Description Output [] Dac Cmd Volt Disagrees with Dac Feedback

Possible Cause

• The output command voltage disagrees with the D ac Feedback.

Solution

• Replace acquisition board.

5539-5540,
8539-8540
Description Output [ ] Individual current unhealthy ([ ] mA)

Possible Cause

• The individual current is outside the expected range

Solution

• Check the terminal output device for proper connections/operation. Replace acquisition board

5541-5542,
8541-8542
Description Output [ ] Total current unhealthy ([ ] mA)

Possible Cause

• The commanded current reference does not match the feedback within the specified time limit.

Solution

• Verify that the commanded output is not changing too fast.

5543-5544,
8543-8544
Description Output [ ] 20 mA suicide active

Possible Cause

• Simplex suicide activated. Sensor feedback out of range, software suicide requested.

Solution

• Check sensor feedback to see if it is within limits. Verify that the software suicide request is not activated.

2-66 Mark* Ve Control, Volume II


5545-5546,
8545-8546
Description Output [ ] 20 mA suicide active

Possible Cause

• TMR suicide activated Sensor feedback out of range, software suicide requested.

Solution

• Check sensor feedback to see if it is within limits. Verify that the software suicide request is not activated.

5547-5548,
8547-8548
Description Output [ ] Suicide relay non-functional

Possible Cause

• Simplex: Command relay state does not match feedback

Solution

• Replace acquisition board

5549-5550,
8549-8550
Description Output [ ] Suicide relay non-functional

Possible Cause

• TMR: Commanded relay state does not match feedback

Solution

• Replace acquisition board

5553,
8553
Description Output [ ] 200 mA Jumper Setting Invalid, Overcurrent Detected

Possible Cause

• Excessive current has been detected on analog output and the output has been suicided.

Solution

• Excessive current may be due to an incorrect setting of the 200 mA jumpers. Verify that these jumpers are set correctly.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-67


5800-5831,
8800-8831,
5887-5910,
8887-8910,
5933, 5942,
8933, 8942
Description Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]

Possible Cause

• Voter disagreement detected between R, S, and T controller

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 AnalogInputxx, adjust the TMR_DiffLimit.
− If input variable is PulseInputxx, adjust the TMR_DiffLimit.
− If input variable is ServoOutputxx, adjust the TMR_DiffLimit on the Regulators tab.
− If input signal is LVDTxx, adjust the LVDT_TMR_DiffLimit on the Parameters tab.

TBQA Thermocouples Input Board

Functional Description
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.
Refer to GEH-6729, Mark Ve Application Guide, Volume II, Appendix C for diagrams and
connection information.

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

2-68 Mark* Ve Control, Volume II


QTBA Terminal Board

Functional Description
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/Mark Ve cabinets. The QTBA routes the raw analog input and output through ribbon
cables to the Mark V or Mark Ve 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. Refer to GEH-6729 Mark Ve Application Guide, Volume II, Appendix C
for diagrams and connection information.

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
Core Location Revision
<R>
<S> 6 Rev. QTBAG#A
<T>

Jumper Default Position Position Application Notes


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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-69


TBQB Terminal Board

Functional Description
The TBQB provides for a phoenix block screw connection between specific external
customer field devices and the Mark V/Mark Ve cabinets. The TBQB routes the raw
analog input and output through ribbon cables to the Mark V or Mark Ve 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
The I/O processor performs the analog-to-digital conversion and the linearization of
analog signals. Refer to GEH-6729 Mark Ve Application Guide, Volume II, Appendix C
for diagrams and connection information.

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
Core Location Revision
<R>
7 Rev. TBQBQ#A

2-70 Mark* Ve Control, Volume II


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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-71


TBQC Terminal Board

Functional Description
The TBQC provides for input and output phoenix block screw connections between
specific external customer field devices and the Mark V/Mark Ve panels. The TBQC routes
the raw analog input and output through ribbon cables to the Mark V or Mark Ve 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. Refer to GEH-6729 Mark Ve Application Guide, Volume II, Appendix C for
diagrams and connection information.

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)

2-72 Mark* Ve Control, Volume II


TBQF Terminal Board

Functional Description
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/Mark Ve cabinets. The TBQF routes the raw
steam applications. analog input and output through ribbon cables to the Mark V or Mark Ve 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
The I/O processor performs the analog-to-digital conversion and the linearization of
analog signals. Refer to GEH-6729 Mark Ve Application Guide, Volume II, Appendix C
for diagrams and connection information.

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)

BJ16 Analog Output jumper

BJ17 Analog Output jumper

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-73


TCQC Terminal Board

TCQC Jumper Configuration


Core Location Revision
<R> 4 Rev. TCQCG#B
<S>
<T>

Jumper Default Position Position Application Notes


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 on Mark Ve
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 on Mark Ve
Place jumper in default position
BJ22 Enabled Disabled Oscillator enable
Enable = normal operation

2-74 Mark* Ve Control, Volume II


Jumper Default Position Position Application Notes
BJ23 Out = termination In = termination Not used on Mark Ve
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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-75


TCQC Interfacing Board Servo Output Jumpers

2-76 Mark* Ve Control, Volume II


GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-77
MVRB I/O Interface Board
Functional Description
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:

• Analog outputs LVDTs


• Accelerometers
• Proximeters
• Keyphasors

Additional Functionality:

• Vibration protection algorithms


• 1/2 x, 1x and 2x magnitude and phase

2-78 Mark* Ve Control, Volume II


Installation
Ø To install the MVRB
1. Verify that power is removed from the core.
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 MVRB from its static bag and reverse this procedure.
6. Once the MVRB 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, Adding the MVRx Board.

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 Mark VIe turbine
protection in the Mark Ve control system.

Protection capability in the application blockware allows the blockware to monitor the
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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-79


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:

2-80 Mark* Ve Control, Volume II


JP5 — JP6:

MVRB On-Board Analog Output Jumper Settings

JP8 — JP9:

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-81


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.

Number of Inputs Type Terminal Board


2 Analog outputs TBQD
3 Vibration inputs or accel inputs TBQD
15 Vibration inputs TBQD
10 Proximeter input TBQD
2 Keyphasor proximeter input TBQD

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)

2-82 Mark* Ve Control, Volume II


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
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

MVRB Board Parameters

Parameter Description Selections


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,
The AVSelection is used to read internal variables that are not AOut2IndivCurFdbk,
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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-83


MVRB I/O Parameter Groups

MVRB I/O Parameter Groups – Analog Outputs


Parameter Description Selections
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)
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 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.
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.
HoldLastVal holds the analog output at the last value in
engineering units received before the MVRA went offline.
Output_Value allows the end 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 the analog output to when the
MVRA goes offline.

2-84 Mark* Ve Control, Volume II


MVRB I/O Parameter Groups – LVDT Inputs
Parameter Description Selections
Enable Enable the LVDT Disable, Enable
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)
The absolute value in V rms read by the LVDT when the valve
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


Parameter Description Selections
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


Parameter Description Selections
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)
VdcLowLimit 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.
VdcHighLimit V dc high health limit -2.5 to 18.0 V (FLOAT)
If the vibration axial voltage is greater than this high limit, the
sensor is unhealthy.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-85


MVRB I/O Parameter Groups – Vibration Sensors 4 through 18
Parameter Description Selections
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)
VdcLowLimit 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.
VdcHighLimit V dc high health limit -2.5 to 18.0 V dc (FLOAT)
If the proximeters voltage is greater than this high limit, the
sensor is unhealthy.

MVRB I/O Parameter Groups – Proximeter Sensors 19 through 28


Parameter Description Selections
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)
VdcLowLimit V dc low health limit -2.5 to 18.0 V (FLOAT)
If the proximeters voltage is less than this low limit, the sensor
is unhealthy.
VdcHighLimit V dc high health limit -2.5 to 18.0 V (FLOAT)
If the proximeters voltage is greater than this high limit, the
sensor is unhealthy.

MVRB I/O Parameter Groups – Keyphasor Proximeter Sensors


Parameter Description Selections
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)
VdcLowLimit V dc low health limit -2.5 to 18.0 V (FLOAT)
If the proximeters voltage is less than this low limit, the
keyphasor sensor is unhealthy.
VdcHighLimit V dc high health limit -2.5 to 18.0 V (FLOAT)
If the proximeters voltage is greater than this high limit, the
keyphasor sensor is unhealthy.

2-86 Mark* Ve Control, Volume II


MVRB I/O Internal Variables Groups

MVRB I/O Input Variable Groups – Analog Output Feedback


Parameter Description Selections
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


Parameter Description Selections
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


Parameter Description Selections
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

Parameter Description Selections


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
frequency and a magnitude is calculated.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-87


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

Parameter Description Selections


LPShaftFreq LP shaft frequency in RPM (populated by the application) RPM (FLOAT)
The accelerometer output is frequency locked to the LP shaft
frequency and a magnitude is calculated.

MVRB I/O Input Variable Groups – Vibration 1x 2x Feedbacks


Parameter Description Selections
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


Parameter Description Selections
ProxVdcxx 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.

2-88 Mark* Ve Control, Volume II


MVRB Jumper Configuration
Core Location Revision
<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
JP3 Machines (Aircraft engine set to same.
derivative)
JP4

JP5

JP6
J14 Disable Enable Card test enable
Disable = Normal operation
J15 Out = disable Oscillator Enable
In = enable Enable = Normal operation

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-89


MVRB Specific Alarms

5401-5430,
8401-8430
Description Vibration Input Sensor [ ] unhealthy ([ ])

Possible Cause

• dc reading is out of range

Solution

• Verify connection. Replace sensor.

5450-5465,
8450-8465
Description LVDT [ ] Position Out of Limit ([ ] Vrms)

Possible Cause

• Loose wire connection or defective sensor

Solution

• Problem is usually not a MVRB or terminal board failure if other LVDT inputs are working correctly. Check field
wiring including shields and LVDT excitation.
• Calibrate servo regulator with the proper LVDT.
• Verify the configuration limits, MinVrms and MaxVrms.

5525-5531,
8525-8531
Description Ref [ ] Reference Voltage out of limits

Possible Cause

• A/D reference voltage is out of acceptable range.

Solution

• Replace the acquisition board or check the power supply voltages.

5532-5538,
8532-8538
Description Null [ ] Null voltage out of limits

Possible Cause

• The null voltage is out of specification.

Solution

• Replace the acquisition board or check the power supply voltages.

2-90 Mark* Ve Control, Volume II


5547-5548,
8547-8548
Description Output [ ] Suicide relay non-functional

Possible Cause

• Simplex: Command relay state does not match feedback

Solution

• Replace the acquisition board.

5549-5550,
8549-8550
Description Output [ ] Suicide relay non-functional

Possible Cause

• TMR: Commanded relay state does not match feedback

Solution

• Replace the acquisition board.

5551-5556,
8551-8556
Description Output [ ] Dac Cmd Volts Disagrees with Dac fbk by 5%

Possible Cause

• The output command voltage disagrees with the D ac feedback.

Solution

• Replace the acquisition board.

5553, 8553
Description Output [ ] 200 mA Jumper Setting Invalid, Overcurrent Detected

Possible Cause

• Excessive current has been detected on analog output and the output has been suicided.

Solution

• Excessive current is probably due to an incorrect setting of the 200 mA jumpers. Verify that these jumpers are set
correctly.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-91


5802-5807,
8802-8807
Description Input Signal []Voting Mismatch, Local=[ ], Voted=[ ]

Possible Cause

• Voter disagreement detected between R, S, and T controller

Solution

• Adjust the LVDT_TMR_DiffLimit Parameter

TBQD Terminal Board

Functional Description
The TBQD provides for phoenix block screw connection between specific external
customer field devices and the Mark V and Mark Ve cabinets. It routes the raw analog
input and output through ribbon cables to the Mark V or Mark Ve to condition, process,
and control the signal. The TBQD board has no active electronics, just protective circuits
and jumpers. Each screw has a defined input or output function. The TBQD allows
connection to customer proximeters, LDVTs, and analog output devices.

Operation
The I/O processor performs the analog-to-digital conversion and the linearization of
analog signals. Refer to GEH-6729 Mark Ve Application Guide, Volume II, Appendix C
for diagrams and connection information.

Specifications

Item Specifications
Number of inputs 6 LVDT inputs
18 vibration inputs
8 proximeter inputs
2 keyphasor proximeters
Number of outputs 2 – 4 to 20 mA outputs

QTBA Analog Output Jumper Settings

2-92 Mark* Ve Control, Volume II


Configuration

Core Location Revision


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

Jumper Default Position Application Notes


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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-93


MVRC I/O Interface Board
Functional Description
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

2-94 Mark* Ve Control, Volume II


Installation
Ø To install the MVRC
1. Verify that power is removed from the core.
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 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.
7. Use the ToolboxST application to configure the MVRx as needed. Refer to the
section, Adding the MVRx Board.

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.

Number of Inputs Type Terminal Board


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
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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-95


Configuration

MVRC Board Parameters

Parameter Description Selections


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


Parameter Description Selections
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) *
[( 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
enabled, a diagnostic is generated.

2-96 Mark* Ve Control, Volume II


MVRC_IO Parameter Groups_Analog Outputs
Parameter Description Selections
Output_MA Output mA selection Unused, 0-20 mA
Low_MA Output mA at low value 0 to 20 mA (FLOAT)
Low_Value Output value in engineering units at low mA E.U. (FLOAT)
High_MA Output mA at high value 0 to 20 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)]
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.
HoldLastVal holds the analog output at the last value in
engineering units received before the MVRC 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 the analog output to, when the
MVRC goes offline.

MVRC_IO Parameter Groups_Cold Junctions


Parameter Description Selections
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


Parameter Description Selections
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
by using a table lookup specific to that device.
RTDUnit Select RTD unit degrees C or F Deg_F, Deg_C

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-97


MVRC_IO Parameter Groups_Shunt C
Parameter Description Selections
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


Parameter Description Selections
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


Parameter Description Selections
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 degrees C or F Deg_F, Deg_C

2-98 Mark* Ve Control, Volume II


MVRC Specific Alarms

5400-5400,
8400-8400
Description Unallowed VarIOCompatCode Change: Old - [ ]; New - [ ]

Possible Cause

• The configuration file located in flash storage does not match the firmware

Solution

• Compress the variables and rebuild the I/O pack. Download both the firmware and the application code

5401-5442,
8401-8442
Description Thermocouple [ ] Unhealthy

Possible Cause

• Defective sensor reading or loose wire.

Solution

• Problem is usually not a MVRC or terminal board failure if other thermocouples are working correctly. The solution
may be one of the following:
− The board has detected a thermocouple open and has applied a bias to the circuit driving it to a large negative
number, or the TC is not connected, or a condition such as stray voltage or noise caused the input to exceed -63 mV.
− The thermocouple has been configured as the wrong type, or a stray voltage has biased the TC outside of its normal
range, or the cold junction compensation is wrong, or the thermocouple wiring is open.

5443-5445,
8443-8445
Description Cold Junction [ ] Unhealthy, Using Backup

Possible Cause

• Defective sensor reading on the terminal board. Defective reference voltage on MVRC

Solution

• The local cold junction signal from the terminal board is out of range. The normal range is -30 to 65°C (-22 - 145 °F).

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-99


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

Possible Cause

• Loose wire connection or defective sensor

Solution

• Verify connection. Verify that the voltage range is within specification limits. Replace sensor.

5482-5525,
8482-8525
Description RTD [ ] Unhealthy

Possible Cause

• Loose wire connection or defective sensor

Solution

• Verify connection. Verify that the voltage range is within specification limits.

5526-5536,
8526-8536
Description Ref [ ] Reference voltage out of limits

Possible Cause

• A/D reference voltage out of acceptable range

Solution

• Replace the acquisition board or check the power supply voltages.

5537-5547,
8537-8547
Description Null [ ] Null voltage out of limits

Possible Cause

• Null voltage not correct specification

Solution

• Replace the acquisition board or check the power supply voltages.

2-100 Mark* Ve Control, Volume II


TBCA Thermocouples Input Board

Functional Description
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. Refer to GEH-6729 Mark Ve Application Guide, Volume II,
Appendix C for diagrams and connection information.

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.

TBQA Thermocouples Input Board


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

TBCB Terminal Board

Functional Description
The TBCB provides for phoenix block screw connection between specific external
customer field devices and the Mark V and Mark Ve cabinets. It routes the raw analog
input and output through ribbon cables to the Mark V or Mark Ve 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
The I/O processor performs the analog-to-digital conversion and the linearization of
analog signals. Refer to GEH-6729 Mark Ve Application Guide, Volume II, Appendix C
for diagrams and connection information.

Specifications

Item Specifications
Number of inputs 14 RTDs
8 - 0 to 1 mA or 4 to 20 mA
14 – 4 to 20 mA

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-101


Configuration
Core Location Revision
<C>
7
Rev. TBCBQ#A
optional

Jumper Position Application Notes


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

2-102 Mark* Ve Control, Volume II


TCPD Terminal Board

TCPD Jumper Configuration


Core Location Revision
<PD> 1 Rev. TCPDG#B

Jumper Position Application Notes


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

Functional Description
The CTBA provides for phoenix block screw connection between specific external
customer field devices and the Mark V and Mark Ve cabinets. It routes the raw analog
input and output through ribbon cables to the Mark V or Mark Ve to condition, process,
and control the signal. 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
The I/O processor performs the analog-to-digital conversion and the linearization of
analog signals. Refer to GEH-6729 Mark Ve Application Guide, Volume II, Appendix C
for diagrams and connection information.

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
Core Location Revision
<C> 6 Rev. CTBAG#A

Jumper Position Application Notes


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)

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-103


MVRF I/O Interface Board
Functional Description
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

2-104 Mark* Ve Control, Volume II


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.
2. Carefully remove all ribbon cables and power cables from the board connectors.

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
4. Remove the old board and place it in a static bag.
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.
7. Use the ToolboxST application to configure the MVRx as needed. Refer to the
section, Adding the MVRx Board.

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
The recalibration of a MVRA or MVRF servo is required when a new terminal board is
used on a system. The controller saves the barcode of the terminal board and 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. Liquid Fuel
regulators do not have to be recalibrated (where applicable).

Specifications
The MVRF has the same hardware functionality as the TCQF. Original TCQF ribbon
cables plug directly into the MVRF to simplify replacement.

Number of Inputs Type Terminal Board


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).

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-105


Diagnostics
The MVRF has its own ID device, which is interrogated by the PMVE. The MVRF 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

MVRF Board Parameters

Parameter Description Selections


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,
The AVSelection is used to read internal variables that are not AOut2IndivCurFdbk,
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.

2-106 Mark* Ve Control, Volume II


MVRF I/O Parameter Groups

MVRF_IO Parameter Groups_Analog Inputs


Parameter Description Selections
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) *
[( mA input - Low_Input) / (High_Input - Low_Input)]
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


Parameter Description Selections
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.
Low_MA Output mA at low value 0 to 20 mA (FLOAT)
Low_Value Output value in engineering units at low mA E.U. (FLOAT)
High_MA Output mA at high value 0 to 20 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 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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-107


MVRF_IO Parameter Groups_Analog Outputs
Parameter Description Selections
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.
HoldLastVal holds the analog output at the last value in
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


Parameter Description Selections
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


Parameter Description Selections
Enable Enable the LVDT Disable, Enable
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.

2-108 Mark* Ve Control, Volume II


MVRF_IO Parameter Groups_Monitors
Parameter Description Selections
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


Parameter Description Selections
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
generated. This notifies the user of a possible fault of that
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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-109


MVRF_IO Parameter Groups_Regulators

Parameter Description Selections


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
generated. This notifies the user of a possible fault of that
servo output.

2-110 Mark* Ve Control, Volume II


Parameter Description Selections
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
PositionInput2 Position input 2 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
PositionInput3 Position input 3 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 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,
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
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

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-111


Parameter Description Selections
FlowInput2 Flow rate input 2 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
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
generated. The servo is suicided, if the EnabPressureFbkSuic
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
generated. The servo is suicided, if the EnabFlowFbkSuic 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
generating a suicide based on a transient condition.
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.

2-112 Mark* Ve Control, Volume II


Simple Regulator with Gain and Feedback Control

MVRF_IO Parameter Groups_Thermocouples

Parameter Description Selection


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 in unit degrees C or F Deg_F, Deg_C

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-113


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)

2-114 Mark* Ve Control, Volume II


Servo Regulator Diagrams

Position Regulator

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-115


Speed Ratio Regulator

2-116 Mark* Ve Control, Volume II


Speed Ratio PI Control

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-117


Liquid Fuel Regulator

2-118 Mark* Ve Control, Volume II


Liquid Fuel with Position Feedback

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-119


Liquid Fuel PI Control

2-120 Mark* Ve Control, Volume II


MVRF Specific Alarms

5400, 8400
Description Unallowed VarIOCompatCode Change: Old - [ ]; New - [ ]

Possible Cause

• The configuration file located in flash storage does not match the firmware

Solution

• Compress the variables and rebuild the I/O pack. Download both the firmware and the application code

5401-5415,
8401-8415
Description Thermocouple [ ] Unhealthy ([ ])

Possible Cause

• Defective sensor reading or loose wire.

Solution

• Problem is usually not a MVRF or terminal board failure if other thermocouples are working correctly. The solution
may be one of the following:
− The board has detected a thermocouple open and has applied a bias to the circuit driving it to a large negative
number, or the TC is not connected, or a condition such as stray voltage or noise caused the input to exceed 63 mV.
− The thermocouple has been configured as the wrong type, or a stray voltage has biased the TC outside of its normal
range, or the cold junction compensation is wrong, or the thermocouple wiring is open.

5416-5416,
8416-8416
Description Cold Junction Unhealthy, Using Backup

Possible Cause

• Defective sensor reading on the terminal board. Defective reference voltage on MVRF.

Solution

• The local cold junction signal from the terminal board is out of range. The normal range is -30 to 65°C (-22 - 145 °F).

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-121


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

Possible Cause

• Loose wire connection or defective sensor

Solution

• Problem is usually not a MVRF or terminal board failure if other Analog Inputs are working correctly. Check field
wiring including shields.
• Check ground select jumper for the 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

• Loose wire connection or defective sensor

Solution

• Problem is usually not a MVRF or terminal board failure if other Analog Inputs are working correctly. Check field
wiring including shields.
• Check ground select jumper for the input. Verify that the inputs are in operable range (3.0-21.5 mA).
• Verify parameter settings for Min_MA_Input and Max_MA_Input.

5436-5439,
8436-8439
Description LVDT Excitation [ ] Failed

Possible Cause

• Defective cable between terminal and acquisition board

Solution

• Inspect cable and replace if needed.

2-122 Mark* Ve Control, Volume II


5440-5447,
8440-8447
Description LVDT [ ] Servo Excitation Ratio Out of Range ([ ])

Possible Cause

• Defective cable between terminal and acquisition board

Solution

• Inspect cable and replace if needed.

5448-5455,
8448-8455
Description LVDT [ ] Position Out of Limit ([ ] Vrms)

Possible Cause

• Loose wire connection or defective sensor

Solution

• Problem is usually not a MVRF or terminal board failure if other LVDT inputs are working correctly. Check field
wiring including shields and LVDT Excitation.
• Calibrate servo regulator with the proper LVDT.
• Verify the configuration limits, MinVrms and MaxVrms.

5456-5457,
8456-8457
Description Monitor [ ] Invalid Servo Configuration

Possible Cause

• The monitor type does not match the regulator type

Solution

• Verify that the monitor and regulator are configured as in the ToolboxST application.

5458-5458,
8458-8458
Description More than One Servo Requested for Calibration

Possible Cause

• More than one ToolboxST interface is trying to calibrate the regulator

Solution

• Only calibrate one regulator at a time

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-123


5459-5459,
8459-8459
Description Calibration, Selected LVDT Max / Min Pos Limit Out of Range

Possible Cause

• The calibration Min/Max value exceeds the acceptable limits

Solution

• Check the regulator configuration for Parameter 'PositionInput#1' for the particular servo.
• Check the 'MaxPosValue' & MinPosValue' for LVDT# Selected input in 'PositionInput#1'.
• The MaxPosValue for LVDT input should be between 50% and 150%.
• The MinPosValue for LVDT input should be between -50% and 50%.

5460-5463,
8460-8463
Description FlowRate [ ] Input unhealthy ([ ])

Possible Cause

• Pulse rate input exceeds the maximum limit.

Solution

• Reduce pulse rate to within the specification.

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

Possible Cause

• The regulator type is not defined by this firmware version

Solution

• Verify that the firmware version supports this regulator type.

2-124 Mark* Ve Control, Volume II


5468-5471,
8468-8471
Description Servo [ ] Output Suicide Active

Possible Cause

• Invalid/incorrect configuration :
− Either of the following may cause this error
− 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

• Regulator feedback out of range


• Servo current feedback differs from servo current output

Solution

• Verify the correct configuration parameters for selected type of regulator.


• Verify thatinputs are connected to used sensor inputs in configuration.

5472-5475,
8472-8475
Description Servo [ ] Position Feedback out of range ([ ] %)

Possible Cause

• Possible causes are sensor feedback out of range, software suicide requested.

Solution

• Verify that sensor feedback is within limits.

5476-5479,
8476-8479
Description Servo [ ] Pressure Feedback out of range ([ ])

Possible Cause

• Possible causes are sensor feedback out of range, software suicide requested.

Solution

• Verify that sensor feedback is within limits.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-125


5480-5483,
8480-8483
Description Servo [ ] Flow Feedback out of range ([ ])

Possible Cause

• Possible causes are sensor feedback out of range, software suicide requested.

Solution

• Verify that sensor feedback is within limits.

5484-5490,
8484-8490
Description Ref [ ] Reference Voltage out of limits ([ ])

Possible Cause

• A/D reference voltage is out of acceptable range.

Solution

• Replace the acquisition card or check the power supply voltages.

5491-5497,
8491-8497
Description Null [ ] Null Voltage out of limits ([ ])

Possible Cause

• The null voltage is out of spec.

Solution

• Replace the acquisition card or check the power supply voltages.

5498-5501,
8498-8501
Description Output [ ] Individual current unhealthy ([ ] mA)

Possible Cause

• The individual current is outside the expected range

Solution

• Check the terminal output device for proper connections/operation. Replace acquisition card.

2-126 Mark* Ve Control, Volume II


5504-5509,
8504-8509
Description Output [ ] Total current unhealthy ([ ] mA)

Possible Cause

• The commanded current reference does not match the feedback within the specified time limit.

Solution

• Verify that the commanded output is not changing too fast.

5510-5515,
8510-8515
Description Output [ ] 20 mA suicide active

Possible Cause

• Simplex suicide activated.


• Possible causes are sensor feedback out of range, software suicide requested.

Solution

• Verify that sensor feedback is within limits.


• Verify that the software suicide request is not activated.

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

Possible Cause

• TMR suicide activated.


• Possible causes are sensor feedback out of range, software suicide requested.

Solution

• Verify that sensor feedback is within limits.


• Verify that the software suicide request is not activated.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-127


5522-5527,
8522-8527
Description Output [ ] Suicide relay non-functional

Possible Cause

• Simplex: Command relay state does not match feedback

Solution

• Replace the acquisition card.

5528-5533,
8528-8533
Description Output [ ] Suicide relay non-functional

Possible Cause

• TMR: Commanded relay state does not match feedback

Solution

• Replace the acquisition card.

5534-5539,
8534-8539
Description Output [ ] Dac Cmd Volts Disagrees with Dac fbk by 5%

Possible Cause

• The output command voltage disagrees with the Dac Feedback.

Solution

• Replace the acquisition card.

5551-5552,
8551-8552
Description Output [ ] Dac Cmd Volts Disagrees with Dac fbk by 5%

Possible Cause

• The output command voltage disagrees with the Dac Feedback.

Solution

• Replace the acquisition card.

2-128 Mark* Ve Control, Volume II


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 controller

Solution

• Adjust the specified parameter below for the each input type:
− If input variable is AnalogInputxx, adjust the TMR_DiffLimit.
− If input variable is PulseInputxx, adjust the TMR_DiffLimit.
− If input variable is ServoOutputxx, adjust the TMR_DiffLimit on the Regulators tab.
− If input signal is LVDTxx, adjust the LVDT_TMR_DiffLimit on the Parameters tab.

TBQA Thermocouples Input Board


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

Functional Description
The TBQG provides for phoenix block screw connection between specific external
customer field devices and the Mark V and Mark Ve cabinets. It routes the raw analog
input and output through ribbon cables to the Mark V or Mark Ve to condition, process,
and control the signal. 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
The I/O processor performs the analog-to-digital conversion and the linearization of
analog signals. Refer to GEH-6729 Mark Ve Application Guide, Volume II, Appendix C
for diagrams and connection information.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-129


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 Mark Ve 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
Core Location Revision
<S>
7
Rev. TBQGQ#A
optional

Jumper Default Position Application Notes


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

2-130 Mark* Ve Control, Volume II


HSLA Interface
Functional Description
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.

GEH-6729H PMVE Mark Ve Control I/O Module Application Guide 2-131


Installation
The HSLA and MVRx are combined during factory assembly. The HSLA by itself is not
available as a replacement part for the Mark Ve control system.

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

2-132 Mark* Ve Control, Volume II


Common Module Content
The following information is common to Mark Ve distributed I/O modules:

• Auto-Reconfiguration
• Hardware Jumpers
• Common Module Alarms

Auto-Reconfiguration
The Auto-Reconfiguration feature allows I/O packs to be replaced without the operator
having to manually reconfigure them. If the Auto-Reconfiguration feature is enabled,
when the controller detects an I/O pack booting with a different configuration, a
reconfiguration file is automatically downloaded from the controller to the I/O pack. This
reconfiguration includes the bootload, baseload, firmware, and parameters. Each I/O
pack 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 finished. Other downloads to the I/O pack cannot
software suite version 3.06 or be initiated while it is being Auto-Reconfigured. If an I/O pack is already running,
later. 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 pack or
module if necessary. The Auto-reconfiguration of terminal boards and controllers is not
supported. If a terminal board is replaced, the I/O pack must be manually reconfigured
with the new terminal board barcode identifier.

Refer to GEH-6700, ToolboxST When power is applied, the I/O pack boots up and, if enabled, the Auto-Reconfiguration
User Guide for Mark VIe process starts. It generates a signal to the controller to indicate it needs an IP address and
Control for more information. configuration. The controller queries the I/O pack to identify existing files to determine
if a reconfiguration is needed. The controller then starts to download the IP address and
reconfiguration files. The controller signals the I/O pack when the download is complete.
The I/O pack reboots, performs a self-diagnostic test, and goes online.

Note When replacing an I/O pack 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-6729H Common Module Content Application Guide 3-1


Hardware Jumpers
Hardware jumpers are used to configure Mark* Ve hardware (printed circuit boards and
terminal boards) 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 damage to the system or personnel.
Warning
The following hardware jumper configuration examples show printed circuit board
silkscreens and jumper positions.

3-2 Mark* Ve Control, Volume II


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.

GEH-6729H Common Module Content Application Guide 3-3


Common Module Alarms
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/maintenance a firmware programming error occurred. The I/O pack or module did not go online
with the controller.
• During normal operation the hardware failed.

Solution

• During commissioning/maintenance rebuild the system, then download the application and the configuration to the
I/O pack or module.
• During normal operation replace the I/O pack or module.

3
Description CRC failure override is active

Possible Cause

• During commissioning/maintenance a firmware programming error occurred. The I/O pack or module did not go online
with the controller.
• During normal operation the hardware failed.

Solution

• During commissioning/maintenance rebuild the system, then download the application and the configuration to the
I/O pack or module.
• During normal operation replace the I/O pack or module.

3-4 Mark* Ve Control, Volume II


4
Description I/O pack or module in stand alone mode

Possible Cause

• During commissioning/maintenance the I/O pack or module configuration is invalid.


• During normal operation the hardware failed.

Solution

• During commissioning/maintenance rebuild the system, then download the application and the configuration to the
I/O pack or module.
• During normal operation replace the I/O pack or module.

5
Description I/O pack or module in remote I/O mode

Possible Cause

• During commissioning/maintenance the I/O pack or module configuration is invalid.


• During normal operation the hardware failed.

Solution

• During commissioning/maintenance rebuild the system, then download the application and the configuration to the
I/O pack or module.
• During normal operation replace the I/O pack or module.

6
Description Special User Mode active. Now: [ ]

Possible Cause

• During commissioning/maintenance the I/O pack or module configuration is invalid.


• During normal operation the hardware failed.

Solution

• During commissioning/maintenance rebuild system, then download the application and the configuration to the I/O
pack or module.
• During normal operation replace the I/O pack or module.

GEH-6729H Common Module Content Application Guide 3-5


7
Description The I/O pack or module has gone to the Offline state

Possible Cause

• During commissioning/maintenance the Ethernet cable is disconnected or connected to the wrong port
• During normal operation the controller is offline or restarted
• Faulty Ethernet switch/cable

Solution Verify that the controller is not offline. If other I/O pack or module are not reporting a problem, there may be
an IONet cable or switch problem.

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.

3-6 Mark* Ve Control, Volume II


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.
• Manually restart the I/O pack or module.

22
Description Diagnostic status signal (...L3DIAG and/or ...ATTN) is [ ]; therefore, diagnostic status for this I/O pack
or module maybe 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.

GEH-6729H Common Module Content Application Guide 3-7


24
Description Cannot retrieve I/O pack or module 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.
• Manually restart 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.

3-8 Mark* Ve Control, Volume II


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.

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 Input voltage has dropped below 26.5 V. I/O pack or module input power is required to be within the
range 28 V ±5%.
In most cases, the normal pack operation continue 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.

GEH-6729H Common Module Content Application Guide 3-9


258
Description Temperature [ ] degF is out of range ([ ] to [ ] degF)

Possible Cause Temperature went outside -20 to 85°C (-4 to 185 °F)

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

• During commissioning/maintenance the I/O pack or module does not have the correct configuration file stored in its flash
file system.
• During commissioning/maintenance there is a hardware problem.
• During normal operation there is a hardware failure.

Solution

• During commissioning/maintenance confirm the correct installation of the ToolboxST application.


• During commissioning/maintenance rebuild the system and download the application and the configuration to the
I/O pack or module.
• During normal operation replace the I/O pack or module.

3-10 Mark* Ve Control, Volume II


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
• During normal operation there is a hardware failure

Solution

• During commissioning/maintenance rebuild the system and download the application and the configuration to the
I/O pack or module.
• During normal operation replace the I/O pack or module.

265
Description Configuration file load error - invalid I/O header size

Possible Cause

• During commissioning/maintenance build error


• During commissioning/maintenance the controller EGD revision code is not supported
• During commissioning/maintenance incompatible version of the I/O pack or module firmware is downloaded
• During normal operation there is a hardware failure

Solution

• During commissioning/maintenance confirm the correct installation of the ToolboxST application.


• During commissioning/maintenance verify that each I/O pack or module is upgraded to the latest version by right-clicking
each pack or module and selecting Upgrade.
• During commissioning/maintenance rebuild the application and download the firmware and the application code to
the affected I/O pack or module.
• During normal operation replace the I/O pack or module.

GEH-6729H Common Module Content Application Guide 3-11


266
Description Configuration file load error - invalid file length

Possible Cause

• During commissioning/maintenance the configuration file in the I/O pack or module does not have the correct size to
match the application code that is loaded.
• During normal operation hardware failure

Solution

• During commissioning/maintenance 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.
• During normal operation replace the I/O pack or module.

267
Description Firmware Load Error

Possible Cause

• During commissioning/maintenance incompatible version of firmware downloaded


• During normal operation there is a hardware failure.

Solution

• During commissioning/maintenance confirm the correct installation of the ToolboxST application.


• During commissioning/maintenance ensure 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.
• During commissioning/maintenance rebuild the application and download the firmware and the application code to
the affected I/O pack or module.
• During normal operation replace the I/O pack or module.

3-12 Mark* Ve Control, Volume II


268
Description Firmware Load Error - Incompatible FPGA Revision: Found [ ] Need [ ]

Possible Cause

• During commissioning/maintenance incompatible version of firmware downloaded


• During normal operation there is a hardware failure.

Solution

• During commissioning/maintenance confirm the correct installation of the ToolboxST application.


• During normal operation 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.
• During normal operation rebuild the application and download the firmware and the application code to the affected
I/O pack or module.
• During normal operation replace the I/O pack or module.

271
Description Internal communication error - Exchange [ ] Export failed

Possible Cause Internal runtime error

Solution

• Restart the I/O pack or module. If the problem persists, replace the I/O pack or module.

279
Description Could not determine platform type from hardware

Possible Cause

• During commissioning/maintenance there is an incorrect firmware version or hardware malfunction (firmware could
not recognize host hardware type).
• During normal operation there is a hardware failure.

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 processor module.

GEH-6729H Common Module Content Application Guide 3-13


280
Description Platform hardware does not match configuration

Possible Cause

• During commissioning/maintenance the platform type identified in the application configuration does not match actual
hardware
• During normal operation there is a hardware failure

Solution

• Fix the platform type in the ToolboxST application (General tab, General Properties, Platform).
• Rebuild and download the application.
• If the problem persists, replace the processor module.

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 processor 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.

3-14 Mark* Ve Control, Volume II


283
Description Firmware execution error - Internal process crashed

Possible Cause Runtime or hardware malfunction (runtime process failed)

Solution

• Reload firmware and application and restart.


• 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 base load.

284
Description Unexpected reboot occurred - firmware fault

Possible Cause Runtime or hardware malfunction (runtime process failed)

Solution

• Reload firmware and application and restart. 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.
• If this does not work, replace processor module.
• I/O pack or module: Re-download the base load.

285
Description Unexpected reboot occurred - hardware fault

Possible Cause

• Runtime or hardware malfunction


• Runtime process stalled

Solution

• Reload firmware and application and restart.


• If the problem persists, replace the processor module.

GEH-6729H Common Module Content Application Guide 3-15


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)

Solution

• Verify that the controller is online.


• Confirm that the correct terminal board ID is present in the ToolboxST configuration.
• Check IONet (switches, cables).

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

• During commissioning/maintenance invalid application configuration


• During normal operation 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.

3-16 Mark* Ve Control, Volume II


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

• During commissioning/maintenance the I/O pack or module application process is not providing system signal inputs to
EGD every frame.

Solution

• During commissioning/maintenance rebuild and download the firmware and the application.
• During commissioning/maintenance verify that the idle time is adequate for the I/O pack or module and that the frame
rate does not exceed defined limits.
• During commissioning/maintenance if the problem persists, replace the I/O pack or module .

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.

GEH-6729H Common Module Content Application Guide 3-17


341
Description Firmware/IO Configuration Incompatibility

Possible Cause I/O pack or module configuration files are incompatible with the firmware (files do not contain
necessary revision)

Solution

• Confirm the correct installation of the ToolboxST software.


• 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.

342
Description Firmware/Configuration Incompatible

Possible Cause I/O pack or module configuration files are incompatible with the firmware (files do not contain
necessary revision)

Solution

• Confirm the correct installation of the ToolboxST software.


• 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.

366
Description Initialization failure - IO firmware

Possible Cause I/O pack or module did not initialize correctly

Solution

• Restart the I/O pack or module.


• Re-download the firmware.
• Replace the I/O pack or module.

367
Description Internal communications error - HSSL Comm link down

Possible Cause Internal runtime error

Solution

• Check High Speed Serial Link (HSSL) cables.


• If problem the persists, replace the I/O pack or module.

3-18 Mark* Ve Control, Volume II


368
Description Configuration file load error - invalid header size

Possible Cause

• During commissioning/maintenance build error


• During commissioning/maintenance controller EGD revision code is not supported
• During commissioning/maintenance incompatible version of the I/O pack or module firmware downloaded
• During normal operation there is a hardware failure

Solution

• During commissioning/maintenance confirm the correct installation of the ToolboxST application.


• During commissioning/maintenance 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.
• During commissioning/maintenance rebuild the application and download the firmware and the application code to
the affected I/O pack or module.
• During normal operation replace the I/O pack or module.

369
Description Internal communication error - Exchange [ ] Export failed

Possible Cause Internal runtime error

Solution

• Restart the I/O pack or module. If the problem persists, replace the I/O pack or module.

371
Description IONet-EGD signal inputs are not being updated

Possible Cause

• During commissioning/maintenance I/O pack or module application process is not providing system signal inputs to
EGD every frame.

Solution

• During commissioning/maintenance rebuild and download the firmware and the application.
• During commissioning/maintenance verify that the idle time is adequate for the I/O pack or module, and that the frame
rate does not exceed defined limits.
• During commissioning/maintenance if the problem persists, replace the I/O pack or module.

GEH-6729H Common Module Content Application Guide 3-19


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 processor 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

• During commissioning/maintenance confirm the correct installation of the ToolboxST application.


• During commissioning/maintenance 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.
• During commissioning/maintenance rebuild the application and download the firmware and the application code to
the affected I/O pack or module.
• During normal operation replace the I/O pack or module.

445
Description Incorrect or Missing Acquisition Board on HSSL link 1

Possible Cause The acquisition card on High Speed Serial Link 1 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.
• Verify that the ToolboxST configuration for the appropriate HSSL connector matches the hardware.

446
Description Incorrect or Missing Acquisition Board on HSSL link 2

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.
• Verify that the ToolboxST configuration for the appropriate HSSL connector matches the hardware.

3-20 Mark* Ve Control, Volume II


447
Description Incorrect or Missing Acquisition Board om HSSL link 3

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.
• Verify that the ToolboxST configuration for the appropriate HSSL connector matches the hardware.

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
the ToolboxST application

449
Description Acquisition Board barcode mismatch on HSSL link 2

Possible Cause The barcode on the acquisition card connected to High Speed Serial Link 2 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
the ToolboxST application

450
Description Acquisition Board barcode mismatch on HSSL link 3

Possible Cause The barcode on the acquisition card connected to High Speed Serial Link 3 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
the ToolboxST application

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.

GEH-6729H Common Module Content Application Guide 3-21


452
Description Communication Lost on HSSL Link 2

Possible Cause The UCSA can no longer communicate with the acquisition card on High Speed Serial Link 2

Solution Verify that the Ethernet cable is connected and that the acquisition card is healthy.

453
Description Communication Lost on HSSL Link 3

Possible Cause The UCSA can no longer communicate with the acquisition card on High Speed Serial Link 3

Solution Verify that the Ethernet cable is connected and that the acquisition card is healthy.

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

499
Description I/O pack is connected to an unknown board

Possible Cause The terminal 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 newer version of the terminal board is 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 the 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 module.

3-22 Mark* Ve Control, Volume II


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.
• Replace the I/O pack or module.
• 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.

GEH-6729H Common Module Content Application Guide 3-23


1008-1010,
1264-1266
Description Outputs unhealthy on IONet [ ] - Major Signature Mismatch

Possible Cause Application/configuration does not match in I/O pack or module and controller

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.
• If the problem persists, replace affected I/O pack or module, then replace the controller.

1008-1010,
1264-1266
Description Outputs unhealthy on IONet [ ] - Minor Signature Mismatch

Possible Cause Application/configuration does not match in I/O pack or module and controller

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 the 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 [ ] - Timestamp Mismatch

Possible Cause Application/configuration does not match in I/O pack or module and controller

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 the controllers.
• If the problem persists, replace affected I/O pack or module, then replace the controller.

3-24 Mark* Ve Control, Volume II


Signal Flow Diagrams

Reference
Abbreviations
A/D Analog to Digital Converter
CL Current Limit
CTR Counter

D/A Digital to Analog Converter


FPGA Field Programmable Gate Array
MP Micro Processor
MUX Multiplexer, switches multiple inputs to one output
RD Relay Driver
USART Universal Synchronous/Asynchronous Receiver/Transmitter
VCO Voltage Controlled Oscillator

(VCO and CTR combined are the same as an A/D Converter)

Ethernet Cable Color Codes


Cat5e Ethernet Cable Color Code
Red Cables connecting to the <R> Ethernet switch
Black Cables connecting to the <S> Ethernet switch
Blue Cables connecting to the <T> Ethernet switch
Yellow High-speed serial link one
Purple High-speed serial link two
Green High-speed serial link three
Orange Crossover/point-to-point

System Block Diagrams


System block diagrams begin on the following page. These diagrams support a typical
Mark Ve control. Unit-specific modifications may be required to support various
applications.

GEH-6729H Signal Flow Diagrams Application Guide 4-1


4-2 Mark* Ve Control, Volume II
GEH-6729H Signal Flow Diagrams Application Guide 4-3
4-4 Mark* Ve Control, Volume II
GEH-6729H Signal Flow Diagrams Application Guide 4-5
Ethernet Routing Tables
Ethernet cable core-to-core routing for both single and redundant ARCNET is provided
below.

Ethernet Cable Core-to-Core Routing – Single ARCNET

From To
Core Device Port Core Device Port
<R> SW 5 <C> UCSA1 ENET1
<R> SW 6 <S> UCSA2 R/SL1
<R> SW 7 <T> UCSA2 R/SL1
<S> SW 4 <C> PIOA – JA1 ENET1
<S>; SW 5 <C> PIOA – JB1 ENET1
<S> SW 6 <R> UCSA2 S/SL2
<S> SW 7 >T> UCSA2 S/SL2
<T> SW 4 <C> PIOA – JB1 ENET2
<T> SW 5 <C> UCSA1 ENET2
<T> SW 6 <S> UCSA2 T/SL3
<T> SW 7 <R> UCSA2 T/SL3
<R> SW 4 <C> PIOA – JA1 ENET2

Notes 1) UCSA1 is the PMVE (pack control).


2) UCSA2 is the controller
3) All ports are labeled on device front.

Example:

From Point:

• <R> is the R core


• SW is the Ethernet switch located in the R core
• 5 is the port number on the switch

To Point:

• <C> is the C core


• UCSA1 is the PMVE UCSA in <C> core
• ENET1 is the first Ethernet port on the UCSA

Location 1 Device Layout

4-6 Mark* Ve Control, Volume II


Ethernet Cable Core-to-Core Routing – Redundant ARCNET

From To
Core Device Port Core Device Port
<R> SW 5 <C> UCSA1 ENET1
<R> SW 6 <S> UCSA2 R/SL1
<R> SW 7 <T> UCSA2 R/SL1
<S> SW 4 <C> PIOA – JA1 ENET1
<S> SW 5 <C> PIOA – JB1 ENET1
<S> SW 6 <R> UCSA2 S/SL2
<S> SW 7 <T> UCSA2 S/SL2
<T> SW 4 <C> PIOA – JB1 ENET2
<T> SW 5 <C> UCSA1 ENET2
<T> SW 6 <S> UCSA2 T/SL3
<T> SW 7 <R> UCSA2 T/SL3

Notes 1) UCSA1 is the PMVE (pack control).


2) UCSA2 is the controller
3) All ports are labeled on device front.

Example:

From Point:

• <R> is the R core


• SW is the Ethernet switch located in the R core
• 5 is the port number on the switch

To Point:

• <C> is the C core


• UCSA1 is the PMVE UCSA in <C> core
• ENET1 is the first Ethernet port on the UCSA

Location 1 Device Layout

GEH-6729H Signal Flow Diagrams Application Guide 4-7


Milliamps Input Tables
Core, Card, and Generic Signal Name from Signal Termination Points JBB or JHH Pin Hardware
Location Left Column of IO.ASG File Numbers Jumper
<C> C_C_MAI01 POS NEG EXC BJC
37 38 39 1 2 1
Core C_C_MAI02 41 42 40 3 4 2
CTBA C_C_MAI03 43 44 45 5 6 3

card C_C_MAI04 47 48 46 7 8 4

location C_C_MAI05 49 50 51 9 10 5
C_C_MAI06C_ 53 54 52 11 12 6
<C> 6
C_C_MAI07 55 56 57 13 14 7
C_C_MAI08 59 60 58 15 16 8
C_C_MAI09 61 62 63 17 18 9
C_C_MAI10 65 66 64 19 20 10
C_MAI11 67 68 69 21 22 11
C_C_MAI12 71 72 70 23 24 12
C_C_MAI13 73 74 75 25 26 13
C_C_MAI14 77 78 76 27 28 14
<C> C_C_MAI15 1 2 3 1 2 1
Core C_C_MAI16 5 6 4 3 4 2
TBCB C_C_MAI17 7 8 9 5 6 3
card C_C_MAI18 11 12 10 7 8 4
location C_C_MAI19 13 14 15 9 10 5
<C> C_C_MAI20 17 18 16 11 12 6
7optional C_C_MAI21 19 20 21 13 14 7
card C_C_MAI22 23 24 22 15 16 8
C_C_MAI23 25 26 27 17 18 9
C_C_MAI24 29 30 28 19 20 10
C_C_MAI25 31 32 33 21 22 11
C_C_MAI26 35 36 34 23 24 12
C_C_MAI27 37 38 39 25 26 13
C_C_MAI28 41 42 40 27 28 14

4-8 Mark* Ve Control, Volume II


Core, Card, and Generic Signal Name Signal Termination Points JHHP in Hardware
Location from Left Column of Numbers Jumpers
IO.ASG File
POS NEG EXC BJC BJL
<C> C_C_MAI29 43 44 45 29 30 15 23
Core C_C_MAI30 47 48 46 31 32 16 24
TBCB C_C_MAI31 49 50 51 33 34 17 25
C_C_MAI32 53 54 52 35 36 18 26
location C_C_MAI33 55 56 57 37 38 19 27
<C> 7 C_C_MAI34 59 60 58 39 40 20 28
optional C_C_MAI35 61 62 63 41 42 21 29
card C_C_MAI36 65 66 64 43 44 22 30

Core, card, and Generic Signal Name Signal termination Points JB Pin Numbers Hardware
Location from Left Column of Jumpers
IO.ASG file
POS NEG EXC BJC
<Q> Q_R_MAI01 35 36 37 1 2 1
Core Q_R_MAI02 39 40 38 3 4 2
Q_R_MAI03 41 42 43 5 6 3
TBQC Q_R_MAI04 45 46 44 7 8 4
or Q_R_MAI05 47 48 49 9 10 5
TBQF Q_R_MAI06 51 52 50 11 12 6
card Q_R_MAI07 53 54 55 13 14 7
Q_R_MAI08 57 58 56 15 16 8

location Q_R_MAI09 59 60 61 17 18 9
<R> 9 Q_R_MAI10 63 64 62 19 20 10
Q_R_MAI11 65 66 67 21 22 11
Q_R_MAI12 69 70 67 23 24 12
Q_R_MAI13 71 72 73 25 26 13
Q_R_MAI14 75 76 74 27 28 13
Q_R_MAI15 77 78 79 29 30 15

GEH-6729H Signal Flow Diagrams Application Guide 4-9


Signal Flow Diagrams

mA Connection Examples and Notes


(see Tables on previous pages for connection points and hardware jumpers.)

4-10 Mark* Ve Control, Volume II


<QDn> Core — Ignition Transformers on DTBD Terminal Boards

GEH-6729H Signal Flow Diagrams Application Guide 4-11


<QDn> or >CD> Core — Digital Inputs on DTBA Terminal Board

4-12 Mark* Ve Control, Volume II


<QDn> or <CDn> Core — Digital Inputs on DTBB Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-13


<QDn> or <CD> Core — Relay Outputs on DTBC Terminal Board

4-14 Mark* Ve Control, Volume II


<QDn> or <CD> Core — Relay Outputs on DTBD Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-15


<C> Core — UCSA PMVE (Pack Control) and High-speed Serial Link

4-16 Mark* Ve Control, Volume II


<C> Core — RS-232 Communications on UCSA PMVE

GEH-6729H Signal Flow Diagrams Application Guide 4-17


<C> Core - 4-20 mA Inputs on CTBA Terminal Board

4-18 Mark* Ve Control, Volume II


<C> Core - 4-20 mA Inputs on TBCB Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-19


<C> Core — 0–1 and 4–20 mA Inputs on TBCB Terminal Board

4-20 Mark* Ve Control, Volume II


<C> Core — Thermocouple Inputs on TBQA Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-21


<C> Core — Thermocouple Inputs on TBQA Terminal Board — Continued

4-22 Mark* Ve Control, Volume II


<C> Core — Thermocouple Inputs on TBQA Terminal Board — Continued

GEH-6729H Signal Flow Diagrams Application Guide 4-23


<C> Core — RTD Inputs on TBCA Terminal Board

4-24 Mark* Ve Control, Volume II


<C> Core — RTD Inputs on TBCA Terminal Board — Continued

GEH-6729H Signal Flow Diagrams Application Guide 4-25


<C> Core — RTD Inputs on TBCB Terminal Board

4-26 Mark* Ve Control, Volume II


<C> Core — 4–20 mA Outputs on CTBA Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-27


<C> Core — Shaft Voltage Monitoring on CTBA Terminal Board

4-28 Mark* Ve Control, Volume II


<C> Core — Power Supply Monitoring MVRC

GEH-6729H Signal Flow Diagrams Application Guide 4-29


<C> Core — Unused Connections on CTBA Terminal Board

4-30 Mark* Ve Control, Volume II


<C> Core — ARCNET Communications on PIOA — Single ARCNET

GEH-6729H Signal Flow Diagrams Application Guide 4-31


<C> Core — ARCNET Communications on PIOA — Redundant ARCNET

4-32 Mark* Ve Control, Volume II


<C> Core — IONet Communications on PIOA

GEH-6729H Signal Flow Diagrams Application Guide 4-33


<Q> Core — UCSA Controller

4-34 Mark* Ve Control, Volume II


<Q> Core — UCSA PVME (Pack Control) and High-speed Serial Link

GEH-6729H Signal Flow Diagrams Application Guide 4-35


<Q> Core — RS-232 Communications on UCSA Controller

4-36 Mark* Ve Control, Volume II


<Q> Core — RS-232 Communications on UCSA PMVE

GEH-6729H Signal Flow Diagrams Application Guide 4-37


<Q> Core — 4–20 mA Inputs on TBQF Terminal Board

4-38 Mark* Ve Control, Volume II


<Q> Core - 4-20 mA Inputs on TBQC Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-39


<Q> Core — 4–20 mA Inputs on TBQC Terminal Board Using MVRF

4-40 Mark* Ve Control, Volume II


<Q> Core — LVDT Excitation and Feedback Signal on QTBA/TBQC

GEH-6729H Signal Flow Diagrams Application Guide 4-41


<Q> Core — LVDT Excitation and Feedback Signal on QTBA/TBQC

4-42 Mark* Ve Control, Volume II


<Q> Core — LVDT Excitation and Feedback Signal on QTBA/TBQF G#A

GEH-6729H Signal Flow Diagrams Application Guide 4-43


<Q> Core — LVDT Excitation and Feedback Signal on QTBA/TBQF G#B

4-44 Mark* Ve Control, Volume II


<Q> Core — LVDT Excitation and Feedback Signal on QTBA/TBQC Using MVRF

GEH-6729H Signal Flow Diagrams Application Guide 4-45


<Q> Core — Thermocouple Inputs on TBQA Terminal Board Using MVRA

4-46 Mark* Ve Control, Volume II


<Q> Core — Thermocouple Inputs on TBQA Terminal Board Using MVRF

GEH-6729H Signal Flow Diagrams Application Guide 4-47


<Q> Core — Vibration Inputs on TBQB Terminal Board

4-48 Mark* Ve Control, Volume II


<Q> Core — MegaWatt Transducer Inputs on QTBA Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-49


<Q> Core — Pulse Rate Inputs on QTBA Terminal Board

4-50 Mark* Ve Control, Volume II


<Q> Core — Pulse Rate Inputs on QTBA and TBQB Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-51


<Q> Core — Pulse Rate Inputs on TBQG Terminal Board Using MVRF

4-52 Mark* Ve Control, Volume II


<Q> Core — Analog Current and Voltage Inputs on TBQB Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-53


<Q> Core — Analog Current and Voltage Inputs on TBQG Terminal Board Using MVRF

4-54 Mark* Ve Control, Volume II


<Q> Core - Compressor Discharge Pressure Inputs on TBQB

GEH-6729H Signal Flow Diagrams Application Guide 4-55


<Q> Core - 3-Coil Servo Outputs on QTBA Terminal Board for TCQC

4-56 Mark* Ve Control, Volume II


<Q> Core - 3-Coil Servo Outputs on QTBA Terminal Board for TCQC

GEH-6729H Signal Flow Diagrams Application Guide 4-57


<Q> Core - 3-Coil Servo Outputs on TBQG Terminal Board Using MVRF

4-58 Mark* Ve Control, Volume II


<Q> Core - 4-20 mA Outputs on TBQC Terminal Board Using MVRA

GEH-6729H Signal Flow Diagrams Application Guide 4-59


<Q> Core - 4-20/200 mA Outputs on TBQF Terminal Board Using MVRA

4-60 Mark* Ve Control, Volume II


<Q> Core - 4-20 mA Outputs on TBQC Terminal Board Using MVRF

GEH-6729H Signal Flow Diagrams Application Guide 4-61


<Q> Core - 4-20 mA Outputs on TBQG Terminal Board Using MVRF

4-62 Mark* Ve Control, Volume II


<Q> Core - Connections on QTBA Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-63


<Q> Core — Unused Connections on TCQC Board

4-64 Mark* Ve Control, Volume II


<Q> Core - Power Supply Monitoring

GEH-6729H Signal Flow Diagrams Application Guide 4-65


<Q> Core – ARCNET Communications on PIOA – Redundant ARCNET

4-66 Mark* Ve Control, Volume II


<Q> Core – IONet Communications on PIOA

GEH-6729H Signal Flow Diagrams Application Guide 4-67


<P> Core - Emergency Trip Pushbutton Connections on PTBA

4-68 Mark* Ve Control, Volume II


<P> Core - Circuit Breaker (52G) Close Circuit

GEH-6729H Signal Flow Diagrams Application Guide 4-69


<P> Core - Emergency Trip Circuit - Medium Steam Turbine

4-70 Mark* Ve Control, Volume II


<P> Core - Emergency Trip Circuit - Gas Turbine

GEH-6729H Signal Flow Diagrams Application Guide 4-71


<P> Core - Emergency Trip Circuit - Large Steam Turbine

4-72 Mark* Ve Control, Volume II


<P> Core - Emergency Trip Extended Circuit - Large/Medium Steam Turbine

GEH-6729H Signal Flow Diagrams Application Guide 4-73


<P> Core - Emergency Overspeed Magnetic Pickups on PTBA

4-74 Mark* Ve Control, Volume II


<P> Core - Flame Intensity Inputs on PTBA Terminal Board

GEH-6729H Signal Flow Diagrams Application Guide 4-75


<P> Core - Bus Generator PT Inputs on PTBA Terminal Board

4-76 Mark* Ve Control, Volume II


<P> Core - Alarm Horn Circuit and Sync Check

GEH-6729H Signal Flow Diagrams Application Guide 4-77


Mark Ve Synchronization

4-78 Mark* Ve Control, Volume II


<P> Core - Generator Voltage and Current Signal Interface

GEH-6729H Signal Flow Diagrams Application Guide 4-79


Notes

4-80 Mark* Ve Control, Volume II


Power Distribution Diagrams

Overview
The customer's 125 V dc and 115/230 V ac power is brought into the PDM through power
filters. The ac power is cabled out to one or two ac/dc converters, which produce 125 V
dc. This dc voltage is then cabled back into the PDM and diode-coupled to the main dc
power, forming a redundant power source. This power is distributed to the Mark Ve
cores and terminal boards.

Either 115 V ac or 230 V ac can be handled by the ac/dc converters. The transformer cable
must be plugged into either JTX1 for 115 V ac, or JTX2 for 230 V ac operation.

The ac feeders, J17-20, are fused and cabled out to terminal boards. The 125 V dc feeders
are fused and cabled to the protection module, <P>, DTBA, DTBC, and TCTG. To ensure
a noise free supply to the boards, the PDM is supplied through a control power filter
(CPF), which suppresses EMI noise. The CPF rack holds either two or three Corcom 30 A
filter modules as shown in the following figure.

The JZ4 and JZ5 plugs are the auxiliary ac source connection point for applications
that require an isolated input for an uninterruptable power source connection(s) and/or
switched back up power source. The hot side can be isolated with external circuitry
connected to these plugs, however, the neutral cannot.

Care must be used when connecting auxiliary ac sources


into the JZ4 and JZ5 plugs. The neutral of the auxiliary
ac input (JZ4 and JZ5 plugs) is connected to the neutral
of the critical ac input (TB1, points 7, 8, 11, and 12).
Caution
The 27 boxes (for ANSI standard designation number) are undervoltage devices that send
a logic signal to the <C> core (refer to Figure 20, Power Supply Monitoring on MVRC) if
the input voltage, either ac or dc, is no longer present. These signals can be incorporated
into sequencing to be used as alarms. The ac undervoltage boxes incorporate a LED
to give a visual indication of fuse status; in the dc circuits, the LED is still provided,
but in a separate circuit.

GEH-6729H Power Distribution Diagrams Application Guide 5-1


An example of the undervoltage detectors is as follows:

If the green LED is off or the red LED is on, the fuse is open.

Switches are provided on newer revisions of the <PD> core. These should be used when it
is necessary to remove power from only one core or board at a time.

The following pages provide diagrams of the Power Distribution Core <PD>. For
simplification, not every component is shown.

5-2 Mark* Ve Control, Volume II


Power Distribution Core <PD> Diagrams
The cabling, wiring connections, and fuse locations for the PDM in the interface cabinet
are shown below.

PDM Cabling, Wiring, and Fuse Locations

GEH-6729H Power Distribution Diagrams Application Guide 5-3


Switches in <PD> Core
The PDM for the I/O cabinet contains the following jumpers and switches. Refer to the
circuit diagrams for location and function.

Switch Indicator Output Cable Destination


SW1 Yes J1R, J2R <R> Power Supply, 125 V dc
SW2 Yes J1S, J2S <S> Power Supply, 125 V dc
SW3 Yes J1T, J2T <T> Power Supply, 125 V dc
SW4 Yes J1C <C> Power Supply, 125 V dc
SW5 Yes J1D <D> Power Supply, 125 V dc
SW6 Yes J7X <P> TCEA Loc 1, 125 V dc supply
SW7 Yes J7Y <P>; TCEA Loc 3, 125 V dc supply
SW8 Yes J7Z <P> TCEA Loc 5, 125 V dc supply

Ground Reference Jumper


Jumper BJS is supplied for isolation of ground reference on systems with an external
ground reference. The ground reference bridge across the 125 V dc power has two
resistances, one on each side, and BJS connects the center to ground.

Note When more than one PDM is supplied from a common 125 V dc source, remove
all the BJS connections except one.

Fuses in <PD> Core


The DS200TCPDG4B fuse values are shown in the following table.

PDM Fuse* No. J Connector Current Rating VoltageRating Vendor Catalog No.
FU1-FU6 J1R, S, T 5A 125 V Bussmann® GMC-5A
FU7-FU10 J1C, D 5A 125 V Bussmann GMC-5A
FU13-FU20 J8A, B, C, D 15 A 125 V Bussmann GMA-15A
FU21-FU26** J12A, B, C 1.5 A 250 V Bussmann GMC-1.5A
FU27-FU28*** J15, 16 3.2 A 250 V Little Fuse 31303.2
FU29 J17 15 A 250 V Bussmann ABC-15A
FU30 J18 5A 250 V Bussmann AGC-5A
FU31-FU32 J19, 20 15 A 250 V Bussmann ABC-15A
FU34-FU39 J7X, Y, Z 5A 125 V Bussmann GMA-5A

*All fuses are ferrule type 5 mm x 20 mm, except for FU27-FU32, which are 0.25"
x 1.25 ".

**The short circuit rating for FU21-FU26 is 100 A

***The short circuit rating for FU27-FU28 is 70 A

5-4 Mark* Ve Control, Volume II


<PD> Core - Incoming Ac and Dc Circuits

GEH-6729H Power Distribution Diagrams Application Guide 5-5


Distribution Charts

<PD> Core - Dc Power Distribution

* In Chart 1, Circuits 6-9 are similar to circuits 1-5 with the exception of no switches

5-6 Mark* Ve Control, Volume II


<PD> Core - Ac Power Distribution

GEH-6729H Power Distribution Diagrams Application Guide 5-7


Dc Distribution, Chart 1

Circuit CRn FP FN Amps SW CR Positive Negative CORE


JW JX JY JZ
1 1 FU1 FU2 5 1 1 J1R-1 J2R-1 J1R-2 J2R-2 R
2 2 FU3 FU4 5 2 2 J1S-1 J2S-1 J1S-2 J2S-2 S
3 3 FU5 FU6 5 3 3 J1T-1 J2T-1 J1T-2 J2T-2 T
4 4 FU7 FU8 5 4 4 J1C-1 N/A J1C-2 N/A C
5 5 FU9 FU10 5 5 5 J1D-1 N/A J1D-2 N/A D
6 8 FU13 FU14 15 N/A 8 J8A-1 N/A J8A-2 N/A QD1
7 9 FU15 FU16 15 N/A 9 J8B-1 N/A J8B-2 N/A CD
8 10 FU17 FU18 15 N/A 10 J8C-1 N/A J8C-2 N/A *
9 11 FU19 FU20 15 N/A 11 J8D-1 N/A J8D-2 N/A *

*These connections can go to either the <CD> or <QD2> core depending on the Mark
Ve application. See the Mark Ve case wiring diagram for actual connections for the
specific job.

Dc Distribution, Chart 2

Circuit DCnP FP FN Amps CR Positive Negative CORE


DCnNn
JY JZ
1 12 FU21 FU22 1.5 12 J12A-1 J12A-2 QD1
2 13 FU23 FU24 1.5 13 J12B-1 J12B-2 CD1
3 14 FU25 FU26 1.5 14 J12C-1 J12C-2 QD2

Ac Distribution, Chart 3

Circuit AcnH FHI Amps CR HOT Neutral CORE


ACnLOn
JY JZ
1 1 FU29 15 15 J17–1 J17-1 AUX
2 2 FU30 5 16 J18-1 J18-2 *TCTL
3 3 FU31 15 17 J19-1 J19-2 QD1
4 4 FU32 15 18 J20-1 J20-1 QD1

*Second circuit used only on large steam applications

In gas turbine applications, ac3H and ac4H are used for the ignition transformers. The ac
distribution voltage depends on the application.

5-8 Mark* Ve Control, Volume II


Special Use Contact Outputs and Related Components
Two contact output circuits contain unique components for special applications. Contact
output 16 and 17 are designed for gas turbine solenoid circuits; contact output 16 for
compressor bleed valve solenoid, and contact output 17 for liquid fuel forwarding stop
valve solenoid. Figure D-4 shows contact output 16 (Q_QD1_CO16) and Figure D-5
shows contact output 17 (Q_QD1_CO17).

Contact Output 16 Circuit

GEH-6729H Power Distribution Diagrams Application Guide 5-9


Contact Output 17 Circuit

5-10 Mark* Ve Control, Volume II


Contact output 18 (Q_QD1_CO18) is designed for the high pressure liquid fuel pump
clutch solenoid in gas turbine applications. If this solenoid requires reduced voltage,
remove the jumper from JZ2 to JZ3. Figure D-6 shows the components of this circuit.

Contact Output 18 Circuit

GEH-6729H Power Distribution Diagrams Application Guide 5-11


Ground Fault Detection Sensitivity
Ground fault detection is Ground fault detection on the floating 125 V dc power bus is based upon monitoring
performed by the PMVE using the voltage between the bus and the ground. The bus voltages with respect to ground
signals from the <PD>. are normally balanced (in magnitude), that is the positive bus to ground is equal to the
negative bus to ground. The bus is forced to the balanced condition by the bridging
resistors, Rb, refer to the figure. Bus leakage (or ground fault) from one side causes the
bus voltages with respect to ground to be unbalanced.

Ground Fault on Floating 125 V dc Power Bus

There is a relationship between the bridge resistors, the fault resistance, the bus voltage,
and the bus to ground voltage (Vout) as follows:

Vout = Vbus*Rf / [2*(Rf + Rb/2)]

Therefore, the threshold sensitivity to ground fault resistance is as follows:

Rf = Vout*Rb / (Vbus – 2*Vout).

The ground fault threshold voltage is typically set at 30 V (Vout = 30 V). The bridging
resistors are 33 K each. Therefore, from the formula above, the sensitivity of the control
panel to ground faults, assuming it is on one side only, is as shown in the following table.

Sensitivity to Ground Faults

Vbus - Bus voltage Vout - Measured Bus Rb (Kohms) - bridge Rf (Kohms) -fault Control System
to ground voltage resistors (balancing) resistor
(threshold)
105 30 33 22 Mark Ve
125 30 33 15 Mark Ve
140 30 33 12 Mark Ve

5-12 Mark* Ve Control, Volume II


Core Power Supply and Distribution

<Q> and <QD> Core – Power Supply I

GEH-6729H Power Distribution Diagrams Application Guide 5-13


<Q> and <QD> Core – Power Supply II

5-14 Mark* Ve Control, Volume II


<C>, <D>, <CD>, and <DD> Core - Power Supply I

GEH-6729H Power Distribution Diagrams Application Guide 5-15


<C>, <D>, <CD>, and <DD> Core - Power Supply II

5-16 Mark* Ve Control, Volume II


<Q>, <C>, and <D> Core — Power Distribution JPDV

GEH-6729H Power Distribution Diagrams Application Guide 5-17


Notes

5-18 Mark* Ve Control, Volume II


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-6729H Replacement and Ordering Application Guide 6-1


Replacing I/O Packs
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


1. Lockout and/or tagout the field equipment and isolate the power source.
2. Disconnect the power plug located in the connector on the side of the I/O pack.
3. Unplug the Ethernet cables and mark the positions of the removed cables.
4. Loosen the two mounting nuts on the I/O pack threaded shafts.
5. Unplug the I/O pack.
6. Verify that the replacement I/O pack is compatible with one being replaced by
comparing the model numbers on their faceplates. The model number begins with an
IS220P prefix. Most times the numbers will match, but sometimes newer revisions
are used to replace older I/O packs.
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.

If the Auto-Reconfiguration feature is enabled and the


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

Replacing the PMVE


Ø To replace the PMVE

♦ Refer to the following sections for installation and replacement procedures:

• PMVE I/O Communication, 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

6-2 Mark* Ve Control, Volume II


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

GEH-6729H Replacement and Ordering Application Guide 6-3


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

6-4 Mark* Ve Control, Volume II


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

GEH-6729H Replacement and Ordering Application Guide 6-5


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.

6-6 Mark* Ve Control, Volume II


GE Energy
1501 Roanoke Blvd.
Salem, VA 24153–6492 USA

1 540 387 7000


www.geenergy.com

You might also like