GEH-6729H Vol2
GEH-6729H Vol2
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.
Your Job Function / How You Use This Publication Publication No. Address
Publication Issue/Revision
Date
General Rating
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?)
Place
stamp
_______________________
here
_______________________
_______________________
GE Energy
Documentation Design, Rm. 297
1501 Roanoke Blvd.
Salem, VA 24153–6492 USA
Warning
Tip Ä Provides essential information that is not normally defined in regular use but
from an experienced user.
GEH-6729H Contents 1
Notes
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.
Processor
The processor board is common to the Ethernet I/O packs. It contains the following:
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.
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.
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.
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.
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)
• 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.
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.
Option One
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.
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
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.
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.
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.
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:
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
BJ5 87–96
Possible Cause
Solution
34
Description Complete loss of communication with ARCNET.
Possible Cause
Solution
35
Description Invalid Frame Rate: [ ]ms. Only [ ]ms Rate is supported
Possible Cause
Solution
50 - 52
Description Lost communication with TCDA[ ].
Possible Cause
Solution
Possible Cause
Solution
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
59 - 61
Description EPROM mismatch: TCDA[ ] reports MajorRev: [ ]MinorRev: [ ]
Possible Cause
• The configured EPROM revisions do not match the EPROMs installed on TCDA
Solution
62 - 64
Description EPROM mismatch: TCEA[ ] reports MajorRev: [ ] MinorRev: [ ]
Possible Cause
• The configured EPROM revisions do not match the EPROMs installed on TCEA
Solution
Possible Cause
Solution
68 - 70
Description Configuration failed for TCEA[]: Invalid message.
Possible Cause
Solution
2400 - 2402
Description TCDA[ ] is unused.
Possible Cause
Solution
2403-2405
Description TCDA[ ] Memory changed.
Possible Cause
Solution
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.
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.
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)
• (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.
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.
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.
Possible Cause
Solution
2887-2889
Description TCEA[ ] Memory changed
Possible Cause
Solution
2890-2892
Description TCEA[ ] HP reading, hardware trouble
Possible Cause
• The High Pressure shaft speed is calculated utilizing two different types of hardware. This diagnostic means the difference
in the two readings exceeds its allowable limit.
Solution
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
Possible Cause
• Discrepancy between the IO configuration and the jumper settings associated with the HP base speed definition.
Solution
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
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
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
Possible Cause
• Discrepancy between the IO configuration and the jumper settings associated with the System config definition.
Solution
2911-2913
Description TCEA[ ] Trip board config trouble
Possible Cause
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
Solution
• Check the cabling on TCEA "JL"; if cabling is OK, replace TCEA; if alarm still indicates trouble replace the trip
board TCT_.
Possible Cause
• The relay driver circuitry associated with relay ETR1 is bad. The relationship is:
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:
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_.
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_.
Possible Cause
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.
• 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
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.
• 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.
Possible Cause
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.
• 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
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.
• 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.
Possible Cause
Solution
• If no PTR3 relay driver RD4 failure diagnostic is indicated, then suspect the trip board TCT_; determine which PTR3
relay is bad by looking for a corresponding vote exchange diagnostic message; verify that the PTR3 relay is not loose.
• 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
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.
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.
• 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.
• 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.
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.
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.
• 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.
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.
• 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.
• 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.
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.
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)
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.
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)
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.
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:
Solution
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.
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
Solution
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.
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
Solution
3002-3004
Description TCEA[ ] Slow synch check 25X relay
Possible Cause
• The synch check relay, L25X (sometimes designated L25A), is not picked up when the synch relay L25 picks up. This is
wrong, the synch check relay should always pickup and be out of the way when the synch relay picks up.
• The synch relay hardware identifications are:
• L25 – synch relay, k3
L25X – synch check relay, k2
L25P – synch relay, k1
Solution
• If L25X is not picking up, Check the "CSP" sequencing: verify that the L25X_PERM coil is being driven with correct
logic. L25X_PERM must be true before L25X will pick up. It is also required that the turbine speed be simulated if not
doing an actual startup. If L25X is picking up slow (as opposed to not picking up), then check the system parameters:
what is the configured phase for L25X? What is the breaker close time? What is the slip when the breaker is being
closed? Are these set correctly?
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.
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
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.
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.
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.
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
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.
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
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
Solution
3050-3052
Description TCEA[ ] Power supply out of limits, N15
Possible Cause
Solution
Possible Cause
Solution
• This is the relay coil supply; it is diode selected on the trip board TCT_; The loss one P24V supply should not cause a
problem.
3056-3058
Description TCEA[ ] Power supply trouble, P24AS/N24AS
Possible Cause
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
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
Solution
• Replace TCEA.
Possible Cause
Solution
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
Solution
3095-3097
Description TCEA[ ] Diagnostic task trouble
Possible Cause
Solution
• Replace TCEA.
Possible Cause
Solution
• Replace TCEA card, then JL cables. Ensure IONet communications to TCEA are functioning.
3101-3103
Description TCEA[ ] Emerg online OS test fail, ETR2
Possible Cause
Solution
• Replace TCEA card then JL cables. Ensure IONet communications to TCEA are functioning.
3104-3106
Description TCEA[ ] Prim online OS test fail, PTR1
Possible Cause
Solution
• Replace TCEA card, then MVRA card and then JD cables. Ensure IONet communications to TCEA are functioning.
3107-3109
Description TCEA[ ] Prim online OS test fail, PTR2
Possible Cause
Solution
• Replace TCEA card, then MVRA card and then JD cables. Ensure IONet communications to TCEA are functioning.
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.
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.
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.
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.
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.
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:
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.
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.
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.
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.
Note To add additional boards, select another Port item and follow the same procedure.
• 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
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).
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.
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:
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.
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
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.
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.
Possible Cause
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.
Possible Cause
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
Solution
Possible Cause
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
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 transducer
• Open circuit
• Incorrect configuration for sensor resistance (ohms)
Solution
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
Solution
Possible Cause
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
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.
Possible Cause
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
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.
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
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.
Possible Cause
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.
Possible Cause
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
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.
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
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 ([ ] %)
Solution
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 ([ ])
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
Solution
Possible Cause Calibration reference voltage more than ±5% from expected value
Solution
5485-5492,
8485-8492
Description Servo [ ] Disabled, Configuration error Fault No:[ ]
Possible Cause
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
Solution
Possible Cause
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
Solution
Solution
5504-5509,
8504-8509
Description Output [ ] Total current feedback unhealthy ([ ] mA)
Possible Cause
Solution
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.
Solution
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
Possible Cause Calibration reference voltage is more than ±5% from the expected value.
Solution
5526-5536,
8526-8536
Description Pack internal reference voltage [ ] out of limits
Possible Cause Calibration reference voltage more than ±5% from expected value
Solution
5528-5533,
8528-8533
Description Output [ ] Suicide relay non-functional
Possible Cause Analog output suicide relay command does not match feedback
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
Possible Cause Null voltage is more than ±5% from the expected value.
Solution
5534-5539,
8534-8539
Description Output [ ] DAC Cmd Volts Disagrees with DAC feedback
5534-,
8534-8539
Description Output [ ] DAC Cmd Volts Disagrees with DAC feedback by 5%
5537-5547,
8537-8547
Description Pack internal null voltage[ ] out of limits
Possible Cause Null voltage more than ±5% from expected value
Solution
Possible Cause
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
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.
Possible Cause
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
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.
Possible Cause
Solution
5545-5546,
8545-8546
Description Output [ ] 20/200 mA suicide active
Solution
Solution
5547-5548,
8547-8548
Description Output [ ] Suicide relay non-functional
Possible Cause Analog output suicide relay command does not match feedback.
5549-5550,
8549-8550
Description Output [ ] Suicide relay non-functional
Possible Cause The analog output suicide relay command does not match the feedback.
Possible Cause Analog output suicide relay command does not match feedback.
5551-5556,
8551-8556
Description Output [ ] DAC Cmd Volts Disagrees with DAC feedback by 5%
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
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
Solution Adjust the specified parameter below for each input type:
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:
5802-5807,
8802-8807
Description Input Signal [ ] Voting Mismatch, Local=[ ], Voted=[ ]
The MVRA is a functional replacement for the Mark V TCQA and IOMA boards.
• Thermocouples (Simplex)
• Servos and LVDTs
• Pulse Rates
• Proximeters
• Analog Inputs
• Analog Outputs
• PTR Relays
• Bus and Gen Voltage
• CPD and Megawatt
• 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.
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).
Position Regulator
Items in bold are I/O pack configuration parameters. Variables with (ssi) or (sso) are
assignable.
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:
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.
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.
The system for calculating rotation depends on parameters sensing rotation of a toothed
speed wheel, then correcting by the following equation:
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.
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.
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
MVRA On-board Analog Output Jumper Settings for JP1 and JP2
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
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).
Possible Cause
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
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
Solution
5448-5465,
8448-8465
Description LVDT [ ] Position Out of Limit ([ ] Vrms)
Possible Cause
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.
Possible Cause
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
Solution
5471-5471,
8471-8471
Description Calibration: Selected LVDT Max / Min Pos Limit Out of Range
Possible Cause
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
Solution
Possible Cause
Solution
5493-5500,
8493-8500
Description Servo [ ] Output Suicide Active
Possible Cause
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
Solution
Possible Cause
Solution
5517-5524,
8517-8524
Description Servo [ ] Flow Feedback out of range ([ ])
Possible Cause
Solution
5525-5531,
8525-8531
Description Ref [ ] Reference Voltage out of limits ([ ])
Possible Cause
Solution
5532-5538,
8532-8538
Description Null [ ] Null Voltage out of limits ([ ])
Possible Cause
Solution
Possible Cause
Solution
5539-5540,
8539-8540
Description Output [ ] Individual current unhealthy ([ ] mA)
Possible Cause
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
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.
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
Solution
5549-5550,
8549-8550
Description Output [ ] Suicide relay non-functional
Possible Cause
Solution
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.
Possible Cause
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.
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
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>
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
Configuration
Core Location Revision
<R>
7 Rev. TBQBQ#A
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
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
Regulators 2 - 4
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
Additional Functionality:
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.
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.
No single event should trip the turbine, and should be qualified and filtered in application
code as appropriate and necessary.
JP1 — JP2:
JP3 — JP4:
JP8 — JP9:
Specifications
The MVRB has the same hardware functionality as the TCQB. Original TCQB ribbon
cables plug directly into the MVRB to simplify replacement.
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)
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
JP5
JP6
J14 Disable Enable Card test enable
Disable = Normal operation
J15 Out = disable Oscillator Enable
In = enable Enable = Normal operation
5401-5430,
8401-8430
Description Vibration Input Sensor [ ] unhealthy ([ ])
Possible Cause
Solution
5450-5465,
8450-8465
Description LVDT [ ] Position Out of Limit ([ ] Vrms)
Possible Cause
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
Solution
5532-5538,
8532-8538
Description Null [ ] Null voltage out of limits
Possible Cause
Solution
Possible Cause
Solution
5549-5550,
8549-8550
Description Output [ ] Suicide relay non-functional
Possible Cause
Solution
5551-5556,
8551-8556
Description Output [ ] Dac Cmd Volts Disagrees with Dac fbk by 5%
Possible Cause
Solution
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.
Possible Cause
Solution
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
The MVRC is a functional replacement for the Mark V TCCA and TCCB boards.
• Thermocouples
• RTD inputs
• Analog inputs
• Analog outputs
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.
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.
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
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).
Possible Cause
Solution
• Verify connection. Verify that the voltage range is within specification limits. Replace sensor.
5482-5525,
8482-8525
Description RTD [ ] Unhealthy
Possible Cause
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
Solution
5537-5547,
8537-8547
Description Null [ ] Null voltage out of limits
Possible Cause
Solution
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.
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
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
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
• Thermocouples (simplex)
• Servos and LVDTs
• Pulse rates
• Proximeters
• Analog inputs
• Analog outputs
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.
All analog and digital I/O signals are read and written at the 5 ms rate by the PMVE(s).
Configuration
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.
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.
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.
The system for calculating rotation depends on parameters sensing the rotation of a
toothed speed wheel, then correcting by the following equation:
Position Regulator
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
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).
Possible Cause
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
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
Solution
Possible Cause
Solution
5448-5455,
8448-8455
Description LVDT [ ] Position Out of Limit ([ ] Vrms)
Possible Cause
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
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
Solution
Possible Cause
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
Solution
5464-5467,
8464-8467
Description Servo [ ] Disabled, Configuration error Fault No:[ ]
Possible Cause
Solution
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
Solution
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
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
Possible Cause
• Possible causes are sensor feedback out of range, software suicide requested.
Solution
5484-5490,
8484-8490
Description Ref [ ] Reference Voltage out of limits ([ ])
Possible Cause
Solution
5491-5497,
8491-8497
Description Null [ ] Null Voltage out of limits ([ ])
Possible Cause
Solution
5498-5501,
8498-8501
Description Output [ ] Individual current unhealthy ([ ] mA)
Possible Cause
Solution
• Check the terminal output device for proper connections/operation. Replace acquisition card.
Possible Cause
• The commanded current reference does not match the feedback within the specified time limit.
Solution
5510-5515,
8510-8515
Description Output [ ] 20 mA suicide active
Possible Cause
Solution
5516-5522,
8516-8522
Description Output [ ] 20 mA suicide active
Possible Cause
Solution
Possible Cause
Solution
5528-5533,
8528-8533
Description Output [ ] Suicide relay non-functional
Possible Cause
Solution
5534-5539,
8534-8539
Description Output [ ] Dac Cmd Volts Disagrees with Dac fbk by 5%
Possible Cause
Solution
5551-5552,
8551-8552
Description Output [ ] Dac Cmd Volts Disagrees with Dac fbk by 5%
Possible Cause
Solution
Possible Cause
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.
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.
Item Specifications
Number of inputs 4 pulse inputs
4 - 4 to 20 mA inputs
Number of outputs 4 servo outputs
4 analog outputs
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.
Configuration
Core Location Revision
<S>
7
Rev. TBQGQ#A
optional
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.
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
• 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.
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.
• 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.
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.
Possible Cause
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
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
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.
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
20
Description I/O communication failure between [ ] and controller.
Possible Cause
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.
Possible Cause
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
23
Description [ ] controller state is not OK...(i.e. Major Difference).
Possible Cause
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
Solution
Possible Cause I/O pack or module configuration files are incompatible with the firmware. Files have wrong revision.
Solution
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.
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
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
Solution
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
Solution
Possible Cause
Solution
271
Description Internal communication error - Exchange [ ] Export failed
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.
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
Solution
284
Description Unexpected reboot occurred - firmware fault
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
Solution
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
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
Solution
Possible Cause
Solution
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
Possible Cause I/O pack or module configuration files are incompatible with the firmware (files do not contain
necessary revision)
Solution
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
366
Description Initialization failure - IO firmware
Solution
367
Description Internal communications error - HSSL Comm link down
Solution
Possible Cause
Solution
369
Description Internal communication error - Exchange [ ] Export failed
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.
Possible Cause Hardware memory failure (process data that should not change after the controller goes online was
modified)
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
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.
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.
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
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.
Possible Cause
Solution
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.
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.
Reference
Abbreviations
A/D Analog to Digital Converter
CL Current Limit
CTR Counter
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
Example:
From Point:
To Point:
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
Example:
From Point:
To Point:
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
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
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.
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.
Note When more than one PDM is supplied from a common 125 V dc source, remove
all the BJS connections except one.
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 ".
* In Chart 1, Circuits 6-9 are similar to circuits 1-5 with the exception of no switches
*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
Ac Distribution, Chart 3
In gas turbine applications, ac3H and ac4H are used for the ignition transformers. The ac
distribution voltage depends on the application.
There is a relationship between the bridge resistors, the fault resistance, the bus voltage,
and the bus to ground voltage (Vout) as follows:
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.
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
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).
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.
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.
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.