EX2100e Excitation System Troubleshooting

GEH-6788H
EX2100e Excitation Control

Diagnostic Alarms for Regulator Systems
Troubleshooting Guide
Dec 2017
For maintenance information, refer to the following document:

GEH-6784, EX2100e Excitation Control Regulator Systems Maintenance Guide
GE Internal
These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible
contingency to be met during installation, operation, and maintenance. The information is supplied for informational
purposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications,
and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflected
herein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or to
the document itself at any time. This document is intended for trained personnel familiar with the GE products referenced
herein.
GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this
document does not provide any license whatsoever to any of these patents.
GE Internal – This document is proprietary. It contains information that belongs to the General Electric Company 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 or the information it contains shall not be reproduced in whole or in part or disclosed to
any third party without the express written consent of GE.
GE provides the following document and the information included therein as is and without warranty of any kind,
expressed or implied, including but not limited to any implied statutory warranty of merchantability or fitness for
particular purpose.
For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE Sales
Representative.
Revised: Dec 2017

Issued: Nov 2011
© 2011 – 2017 General Electric Company.

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

Please send comments or suggestions to controls.doc@ge.com
GE Internal
Document Updates
Revision Update Description
Acronyms and Abbreviations Added UCSC
Related Documents Added GEH-6721_Vol_II

H
Overview Added an Attention to state that any reference to
UCSB infers UCSB or UCSC
Added alarm 546 for factory test mode
Common Controller Diagnostic Alarms 546
G Added alarm 547 for default device password
and 547
change
Acronyms and Abbreviations

CT Current transformer
EDFF EX2100e DC Fanned Feedback Board
EDSL Exciter Regulator Dual Selector
EGD Ethernet Global Data
ERAX EX2100e Regulator Auxiliary I/O
ESYS EX2100e System Interface Board for Customer I/O
EXAM Exciter Attenuator Module
HMI Human-machine Interface
HSLA High-speed Serial Link Interface for Host Applications
HVI High Voltage Interface
M1 Primary controller
M2 Backup controller
OEL Offline Overexcitation Limit
PCM Power conversion module
PCT Power current transformer
PPT Power potential transformer
PT Power transformer
SVS Shaft voltage suppressor
UCSB Universal Controller Stand-alone Version B
UCSC Universal Controller Stand-alone Version C
UEL Underexcitation limit
GEH-6788H Troubleshooting Guide 3

GE Internal
Related Documents
Doc # Title
GEH-6676 EX2100 and EX2100e Excitation Control Power System Stabilizer User Guide
GEH-6700 ToolboxST User Guide for Mark Controls Platform
GEH-6721_Vol_II Mark VIe and Mark VIeS Control Systems Volume II: General-purpose Applications System Guide
GEH-6781 EX2100e Excitation Control User Guide
GEH-6783 EX2100e Excitation Control for Regulator Systems Installation and Startup Guide
GEH-6784 EX2100e Excitation Control for Regulator Systems Maintenance Guide
GEH-6788 EX2100e Excitation Control Diagnostic Alarms for Regulator Systems Troubleshooting Guide
GEI-100256 Receiving, Handling and Storage of GE Drive and Excitation Control Equipment
GEI-100509 EX2100 and EX2100e Excitation Control Exciter Attenuation Module (EXAM) Instruction Guide
GEI-100525 Excitation Control Exciter Regulator Static Converter (ERSC and ERSD) Instruction Guide
Excitation Control Exciter Regulator Third-party Ground Detector Terminal Board (ERGT) Instruction
GEI-100531
Guide
GEI-100770 EX2100e Excitation Control DC Fanned Feedback (EDFF) Board Instruction Guide
GEI-100771 EX2100e Excitation Control Regulator Auxiliary I/O (ERAX) Board Instruction Guide
GEI-100772 EX2100e Excitation Control System I/O Interface (ESYS) Module Instruction Guide
GEI-100773 EX2100e Excitation Control Dual Regulator Selector (EDSL and ERSN) Board Instruction Guide
GEI-100775 EX2100e Excitation Control CT Expansion (ECTX) Board Instruction Guide
GEI-100782 High-speed Serial Link Interface (HSLA) Board Instruction Guide
GEI-100784 EX2100e Excitation Control for 35 A and 120 A Regulator Systems Application Guide
EX2100e Excitation and LS2100e Static Starter Control Systems Touchscreen Local Operator
GEI-100787
Interface Instruction Guide
GEI-100796 Excitation Control Exciter Regulator Bridge Interface (ERBI) Instruction Guide
GEI-100810 Industrial Ethernet Switch (ESWx) Instruction Guide
4 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

GE Internal
Safety Symbol Legend
Indicates a procedure or condition that, if not strictly observed, could result in

personal injury or death.
Warning
Indicates a procedure or condition that, if not strictly observed, could result in damage
to or destruction of equipment.
Caution
Indicates a procedure or condition that should be strictly followed to improve these

applications.
Attention
GEH-6788H Troubleshooting Guide 5

GE Internal
Control System Warnings
To prevent personal injury or damage to equipment, follow all equipment safety

procedures, Lockout Tagout (LOTO), and site safety procedures as indicated by
Employee Health and Safety (EHS) guidelines.
Warning
This equipment contains a potential hazard of electric shock, burn, or death. Only
personnel who are adequately trained and thoroughly familiar with the equipment
and the instructions should install, operate, or maintain this equipment.
Warning
Isolation of test equipment from the equipment under test presents potential electrical
hazards. If the test equipment cannot be grounded to the equipment under test, the
test equipment’s case must be shielded to prevent contact by personnel.
To minimize hazard of electrical shock or burn, approved grounding practices and

Warning procedures must be strictly followed.
To prevent personal injury or equipment damage caused by equipment malfunction,

only adequately trained personnel should modify any programmable machine.
Warning
Always ensure that applicable standards and regulations are followed and only
properly certified equipment is used as a critical component of a safety system. Never
assume that the Human-machine Interface (HMI) or the operator will close a safety
critical control loop.
Warning

GE Internal
1 Overview
This document addresses two forms of troubleshooting for the EX2100e Excitation Control:
• General Troubleshooting describes general issues that may be found during operation, but does not provide specific
alarm numbers.
• Specific Alarm Troubleshooting describes specific alarm messages as they are displayed on the ToolboxST* application.
With power applied, this equipment contains a potential hazard of electric shock or
burn. Only adequately trained persons who are thoroughly familiar with the
equipment and the instructions should maintain this equipment.
Warning
To prevent electric shock while servicing the equipment, personnel must understand
and follow all safety requirements for working around dangerous voltages. Make sure
that all power sources to the equipment are turned off, then ground and discharge the
equipment before performing any adjustments, servicing, or other acts requiring
Warning physical contact with the electrical components or wiring.
Any reference in this document to the UCSB controller infers the applicable form of
the Universal Stand-alone Controller (UCSB or UCSC) in the user’s system. For more
information, refer to the Mark VIe and Mark VIeS Control Systems Volume II:
General-purpose Applications System Guide (GEH-6721_Vol_II), the chapter
Attention Controllers and Unmanaged Switches.
Overview GEH-6788H Troubleshooting Guide 7

GE Internal
1.1 Safety Precautions
This equipment contains a potential hazard of electric shock or burn. Only personnel
who are adequately trained and thoroughly familiar with the equipment and the
instructions should install, operate, or maintain this equipment, or have access to the
location where it is installed.
Warning
To prevent electric shock or burn while servicing the equipment, personnel must
understand and follow all safety requirements for working around dangerous voltages.
Obey local site lockout/tagout (LOTO) procedures, wear appropriate personal
protective equipment (PPE), and follow GE instructions when performing any
adjustments, services, or other tasks requiring physical proximity or contact with the
Warning circuit boards, electrical components, or wiring of the exciter.
Due to the large amount of energy passing through the exciter power converter, failure
to properly reinstall shields or to completely latch doors and covers compromises these
safeguards and places personnel at higher risk when within the environs of the exciter.
Understand and follow the safety procedures and warning labels.
Shock and burn hazard boundaries for the Excitation Control Equipment are
dependent upon the specific site application conditions, including Power Potential
Transformer (PPT) voltage, the mega volt-ampere (MVA) and impedance ratings, and
fault overcurrent clearing time of the power sources feeding the exciter. It is the
Warning responsibility of the customer to perform an arc flash analysis of the system,
understand the hazard boundaries that exist, and employ adequate safeguards to
protect personnel who may be in the proximity of the exciter, whether working on it or
not. These safeguards include restricted access for unqualified personnel, prohibition
of unsafe online maintenance practices, and use of appropriate LOTO procedures and
PPE for qualified personnel who must access the exciter.
To prevent personal injury or death, personnel must be aware of arc flash hazards,
and must maintain safe distances at all times as determined by released energy
calculations. The extent of arc flash hazards is not known until the site-specific
installation is evaluated; therefore GE recommends that an arc flash assessment be
Warning conducted for each installation.
The following table illustrates the Arc Flash Protection Boundary (AFPB) and Hazard Risk Category Number (HRC#) based
on assumed installation conditions that might exist in a typical exciter application. These calculations are based on equations
published in NFPA™-70E, Electrical Safety in the Workplace (2012). These numbers are illustrative only, and must not be
interpreted as applicable to any customer site installation. It is the responsibility of the customer to perform an arc flash
analysis of his installation and implement appropriate safeguards as mentioned above. Consider modifications to the
installation to reduce the hazard levels during periods when maintenance personnel must be present to perform online repair
procedures. These modifications might include the use of reduced energy let-through (RELT) circuit breakers, arc flash
detection technology, or faster fault clearing time settings used during maintenance periods.
Note This content provides general and example electrical safety information. For TSR system applicable information, refer
to the section Digital Front-end, Kits, and Separated Controls Cabinet Applications.

GE Internal
Note When the control cabinet is attached to the power converter lineup, the control cabinet may be within the hazard
boundaries of the power converter. Appropriate PPE levels to access the control cabinet may therefore be higher than might
be expected based solely on hazards within the control cabinet itself.
Upstream Fault
Exciter Source MVA AFPB HRC #
Clearing Time
0.1 sec 2480 mm (98 in) 4
100 mm Multi-bridge 15
0.3 sec 4300 mm (169 in) Extreme Hazard
100 mm Warm Backup 0.1 sec 1570 mm (62 in) 3
6
(WBU) 0.3 sec 2720 mm (107 in) Extreme Hazard
0.1 sec 1160 mm (45 in) 2
77 mm 3.25
0.3 sec 2000 mm (79 in) 3
0.1 sec 810 mm (32 in) 1
53 mm 1.6
0.3 sec 1400 mm (55 in) 3
0.1 sec 480 mm (19 in) 1
42 mm 0.45
0.3 sec 830 mm (33 in) 1
0.3 sec 340 mm (13 in) 0
120 A Regulator 0.075
2.0 sec 1240 mm (49 in) 3
35 A Regulator 0.01 0.3 sec 120 mm (5 in) 0

GE Internal
Grounding Balls
Some models of the EX2100e excitation control may be equipped with grounding balls for temporary grounding of power
busses during maintenance, in accordance with site safety and LOTO procedures.
Grounding Balls Specifications

Grounding Ball Part Grounding Ball Grounding Ball Rating
Model
Number Diameter (per IEC-61230)
EX2100e 100 mm 151X1227RG02PC01 30 mm (1.2 in) 60 kA (250 ms)
EX2100e 77 mm and smaller 151X1227RG01PC01 25 mm (1.0 in) 35 kA (250 ms)
LS2100e 8.5 MVA and 14 MVA 151X1227RG01PC01 25 mm (1.0 in) 35 kA (250 ms)
To safely use the grounding balls within this equipment, site personnel must be properly qualified and aware of site specific
installation parameters as follows:
• Before using the grounding balls, verify the available short circuit current and clearing time of the overcurrent protective
equipment does not exceed their rating. These parameters are site specific, and not necessarily determined by equipment
within GE scope of supply.
• Use grounding clamps and cables that are compatible with the grounding balls and properly rated for the site parameters.
• Comply with site safety procedures and relevant standards such as those provided in the following list.
Refer to relevant standards, including:
• IEC 61230, Portable Equipment for Earthing or Earthing and Short-Circuiting

• ASTM F855, Temporary Protective Grounds to Be Used on De-energized Electric Power Lines and Equipment
• IEEE 1246, Guide for Temporary Protective Grounding Systems Used in Substations

GE Internal
Arc Flash Events
Evaluation of the root cause of arc flash failures in exciters, static starters, and similar power conversion equipment shows
that many arc flash events can be prevented with diligent installation and maintenance procedures.
Causes and Preventive Practices for Arc Flash Events

Causes Best Preventive Practices
□ Torque all power connections.
□ Apply torque marks.
Loose power bus, bolts, and harnesses (contributed
□ Periodically inspect that marks are aligned.
to more than 25% of the events evaluated)
□ Verify that all connectors are snug.
□ Verify that all connectors are free of mechanical stress.
□ Verify that all tools and parts are removed after installation and
maintenance.
Foreign objects such as tools, animals, loose parts, □ Retrieve and remove dropped fasteners and any chips or shavings
or moisture left in or ingested into the equipment from installation.
(caused approximately 25% of the events □ Do not store spare parts within the cabinets.
evaluated) □ Replace all shields and barriers after maintenance work.
□ Cover openings to keep out water, contaminants, and animals.
□ Keep cabinet doors securely closed.
□ Follow installation procedures carefully.
Other poor installation practice, such as cable □ Inspect cables for protection, support, and separation.
protection and energized part separation distances □ Inspect components and assemblies for adequate mounting and
voltage clearances.
Poor maintenance practice, such as keeping
openings sealed and air filters clean □ Follow maintenance guidelines appropriate for site conditions.
Catastrophic component failures, sometimes due to □ Monitor and mitigate external conditions that can lead to
premature failures.
external causes such as inadequate cooling,
□ Be careful not to damage new or reused parts during installation
excessive vibration, damage to insulating mica
procedures.
sheets or sleeves, transient overvoltage, or
□ Do not reuse questionable parts.
application beyond ratings
□ Know the equipment ratings and do not exceed them.

GE Internal
1.1.1 Digital Front-end, Kits, and Separated Controls Cabinet Applications
Some EX2100e excitation control installations may include a control cabinet that is separated from the power converter
lineup. Examples include EX2100e DFE applications and some combined EX2100e LCI Exciter Compartment (LEC)
installations, which locate the controls in a separate room of the LEC from the power converters, to isolate personnel in the
controls area from the arc flash hazards of the power converter. While such an arrangement greatly reduces the risks of shock,
burn, and injury from arc blast pressures, personnel should understand that hazardous voltage and energy levels are present in
the vicinity, and are exposed when the control cabinet door is opened.
Personnel should perform the following safety practices:
• Wear appropriate PPE for the equipment. For a separated EX2100e control cabinet, this is typically PPE-0.
• Field installation of harnesses for separated control cabinets or field mounted kits can introduce hazards and failure
modes if proper procedures are not followed. Failures at wire and cable connections are one of the leading causes of
electrical equipment misoperation, including unnecessary trips and failure of protective functions such as the 86 lockout
circuit to operate when needed. Watch out for:
− Open circuits or loose connections
− Short circuits
− Inadvertent contact and energizing cables with unintended voltages
− Insulation damage from installation or abrasion over time
− Conductor damage such as kinks, stretching, and stray strands at terminations
− Voltages present on harnesses during maintenance due to remote equipment not locked out. Establishing an
electrically safe state for work on the controls in some situations may also require lock-out to be performed on the
power converter, and vice versa.
− Poor terminations and stress on connectors. If harnesses are supplied pre-terminated, ensure the terminations and
connectors are not damaged during harness installation.
− Poor routing and protection of harnesses. Where harnesses pass through building or cabinet walls, provide adequate
protection against damage and sealing to prevent propagation of contaminants during normal operation and arc blast
gases during fault events. Refer to the applicable Installation and Startup manual, the section Cable Damage
Prevention for the equipment.
− Failure to separate harnesses by voltage and electromagnetic compatibility (EMC) levels. For the equipment, refer to
applicable Installation and Startup manual, the section General Cable Specification and Routing Guidelines.
• Be sure protective and functional grounding is provided for the detached equipment, per instructions provided in the
system elementary diagram. A minimum #2 AWG grounding wire must be provided from the detached control equipment
to the building system ground point. The power conversion cabinets must also be bonded to this point. For grounding
details, refer to the equipment elementary diagram.
• Look for hazards such as those in the above subsections during inspections following installation and maintenance.

GE Internal
Additional Safety Reminders
• Always know the voltage approach and arc flash boundaries for the equipment you work on or are exposed to, and wear
appropriate PPE.
• PPE always includes hearing protection. Arc flash events generate high sound levels and blast pressure waves that can
cause permanent hearing damage.
• While PPE may provide protection from shocks and burns, it does not provide protection from injuries such as falling or
being thrown by an arc blast pressure wave. For example, for a typical 77 mm EX2100e control installation with 300 ms
clearing time, the arc blast pressure at 0.9 m (3 ft) from the arc could be 640 kg/m2 (130 lbs/ft2). To avoid such injuries,
always de-energize and apply lockout for all maintenance activities in areas where arc flash hazards exist.
• Equipment may be energized from multiple sources, including unintended or inadvertent sources. Never assume any
conductor is safe to touch.
• Electromechanical devices such as relays and contactors are not suitable lockout devices, since they can be re-energized
electrically.
• When equipment is installed in rooms with small volumes, consider adding room pressure relief vents that open during
arc blast events to reduce the blast pressure. The exhaust from these vents must be directed away from personnel and
other equipment.
• Consider installing ground fault protection on control power supplies to the equipment, to provide additional safety for
site personnel.
• Always be alert to safety. Shock, burns, and other injuries may happen in an unanticipated instant, but can cause a
lifetime of impact.

GE Internal
Notes

GE Internal
2 General Troubleshooting
This section describes some general problems that may occur during operation of the EX2100e control but do not have an
associated alarm number. Refer to the following sections for general troubleshooting assistance:
• Control Troubleshooting provides possible solutions for problems that may occur during operation, such as the following:
− Touchscreen problems
− Board/module, power supplies, and fan failures
− Serial link functionality, erratic operation, and stability issues
− Noise and nuisance faults, wiring, and power supply failures
− Temperature alarms, events, and faults
• Control Cabinet Troubleshooting provides some possible solutions for problems that may occur in the control cabinet,
including the following:
− Diagnostic LED indications on boards/modules and/or Universal Controller Stand-alone board (UCSB)
− Communication issues
− Power supply issues
• Auxiliary Module Troubleshooting provides some possible solutions for problems that may occur with the auxiliary,
including the following:
− Breakers not closed
− Feedback and bridge voltage/current issues
− Exciter overload trips
− Harmonic noise
− AC line filter resistor problems
• Power Conversion Module Troubleshooting provides some possible solutions for problems that may occur in the PCM,
such as:
− 41A breaker trips
− High temperature alarms
− Fan failures
• Runtime Warnings describes errors that may occur during the download and expansion of the application code.
General Troubleshooting GEH-6788H Troubleshooting Guide 15

GE Internal
2.1 Control Troubleshooting
Problem Solution
□ Verify that the plugs are inserted correctly.
□ Check the power supplies.
Touchscreen display is off □ Refer to EX2100e Excitation and LS2100e Static Starter Control Systems Touchscreen
Local Operator Interface Instruction Guide (GEI-100787), the section Diagnostics and
Troubleshooting.
□ Replace the touchscreen.
□ Verify that the plugs are inserted correctly.
□ Refer to EX2100e Excitation and LS2100e Static Starter Control Systems Touchscreen
Local Operator Interface Instruction Guide (GEI-100787), the section Diagnostics and
Touchscreen ineffective, no
Troubleshooting.
errors displayed
□ Check the operation of the UCSB controller.
□ Re-download the application code to the UCSB controller.
□ Check the operation of the UCSB controller.
Parameter changes not
□ Re-download the parameters to the UCSB controller.
taking effect
□ Replace the UCSB controller.
□ Verify that the function is available and enabled.
Diagnostics do not perform □ Check the operation of the UCSB controller.
□ Replace the UCSB controller or touchscreen.
AC or DC input breakers □ Check the line filter or battery filters.

opening □ Check for a ground or short in the ac or dc input circuit (observe applicable warnings and
cautions).
□ Verify that the fuses are the correct size.
Power supply fuses blowing □ Check for any shorted or overloaded power supplies.
□ Check LEDs on the power supplies for proper voltage indications.
Metal oxide varistor (MOV)
□ Check the magnitude and waveforms of the ac and dc inputs for transients.
failures
□ Check all connections at all terminal boards.
□ Check the power supply.
Repetitive board failures □ Verify that all voltages (incoming ac and dc) are correct.
□ Check for damage caused by airborne chemical contamination or foreign objects.
□ Check for moisture.
□ Check fan power supply voltages.
□ Check if ambient often exceeds 40°C (104 °F).
Fan failures
□ Check for debris or blockages in air flow.
□ Verify that the recommended replacement schedule is followed.
□ Verify that the correct serial link cable is being used.
Serial link does not function □ Check the serial link connections at the terminal board.
properly □ Check the exciter's baud rate compared to the serial link device ( if the baud rate is changed,
shut down and immediately restart the control system).

GE Internal
Problem Solution
□ Check the power supplies for magnitude and ripple.
□ Check the connections on all cables and boards/modules.
□ Tighten all connections on terminal boards and all power connections.
Erratic operation
□ Verify that the hardware jumper settings are correct per the custom software.
□ Verify that all parameters are using the software test data sheet or custom software.
□ Check for noisy ground connections.
□ Check the settings of all parameters.
□ Check the inputs from generator feedback (power transformer and current transformer
inputs).
Stability problems □ Check the main generator field feedback for Saturable Current Transformers/Power
Potential Transformer (SCT/PPT) or rotating dc applications.
□ If the problem persists, contact the nearest GE sales or service office, or an authorized GE
sales representative.
□ Verify that the dc supply voltages are not used externally.
Noise/random nuisance
□ Check for suppression on all relays, breakers, and starters.
faults
□ Check all power supplies.
□ Check the wire sizes on the ac and dc power connections.
□ Verify that the control wires (28 V dc, 115 V ac) do not run in the same conduit or run parallel
closer than 101.6 mm (4 in) to the power wires, which may cause noise pickup.
□ Verify that all signal wires are shield-twisted pair, and that shields are grounded at the
exciter-end only.
Wiring issues □ Verify that signal wires are not grounded at more than one end or other than at the
exciter-end only.
□ Verify that the signal wires do not run in the same conduit, parallel, or closer than 101.6 mm
(4 in) to the power wires.
□ Verify that there is only one system ground.
□ Verify that the ground bus is large enough to prevent voltage drops or noise pickup.
□ Check for a high bridge temperature or faulty temperature sensor.
Bridge temperature high □ Check temperature alarm settings.
□ Check fans and air filters.
□ Check the wiring to PTs, PT fuses, and PT cabinet and verify that the connectors are seated
properly.
□ Check the settings for the PT fail detect level and scaling.
Power transformer (PT)
failure detected □ From the optional touchscreen, press RESET to clear and return to AUTO mode.
□ If the alarm does not clear, check PT inputs at the ESYS.
Refer to EX2100e Control System I/O Interface (ESYS) Module Instruction Guide
(GEI-100772).
□ If the V/Hz is ACTIVE, reset the alarm using the operator station or control panel.
□ If the V/Hz is ACTIVE, lower the excitation or raise the generator frequency until clear, then
V/Hz event reset the alarm.
□ Check the settings for the V/Hz regulator and calculation of generator voltage feedbacks.
□ Check PT inputs and scaling.
□ If the OEL LIMIT is ACTIVE, reset the alarm using the operator station or control panel.
□ If the OEL LIMIT is ACTIVE, lower the excitation until clear, then reset the alarm.
Overexcitation limit
□ Check the settings for the OEL regulators, and calculation of field current feedbacks.
(OEL) event
□ Verify correct shunt rating.
□ Investigate the field for shorted turns.

GE Internal
Problem Solution
□ If the UEL LIMIT is ACTIVE, reset the alarm using the operator station or control panel.
Underexcitation limit □ If the UEL LIMIT is ACTIVE, raise the excitation until clear, then reset the alarm.
(UEL) event □ Check the settings of UEL limits.
□ Check EX2100e control calculations of watts and volt-ampere reactives (VARs) versus other
plant instrumentation.
□ Check the Ethernet cables to the remote control operator interface (COI).
Link presence loss fault □ If communication to the COI is lost, use the optional touchscreen to operate the EX2100e
control.
□ Check for alarms in inactive control.
Control/bridge transfers □ Check for alarms in C control.
(redundant systems only) □ Check the settings of protective functions in C control.
C control is not included in dual Regulator systems.
□ Clear the alarm using the Reset Faults command.
□ If the alarm does not reset, review the ToolboxST application diagram, FGD_In , for the fault
location and calculated resistance. Consult station operation standing instructions for
operation with field ground. If the problem persists, contact the nearest GE sales or service
office, or an authorized GE sales representative.
Ground detector faults □ For Brushless Regulator applications, check the external third-party ground detector and the
connections at the Exciter Regulator Third-party Ground Detector Terminal (ERGT) board.
□ For field ground detector (FGD) oscillator problems, review the diagram, FGD_Seq , and
perform a FGD test. If this clears the condition, reset faults and continue operation. If not,
replace the EX2100e Auxiliary Interface (ERAX) board, Exciter Attenuation Module (EXAM),
or cable.

GE Internal
2.2 Control Cabinet Troubleshooting
Problem Description Solution
UCSB controller is not responding □ Check the power supply.
Lost communication to the board/module,
and it is impossible to communicate to □ Check the board/module.
Board LEDs are not lit □ Check the IP address of the UCSB
the board from the touchscreen.
controller.
UCSB controller is not When the computer is connected to the □ Check integrity of the ENET cable and
communicating with computer and controller, it is not possible to view or Ethernet Hub.
touchscreen modify parameters. □ Check the IP address settings.
□ Check the High Voltage Interface (HVI)
module.
ToolboxST application does not □ Check the fiber-optic connection to the
display feedback values for current When using a Trender, there are no EAUX or Exciter Regulator Auxiliary I/O
and volts when communicating to feedback values from the exciter. (ERAX) board.
the exciter □ Check the UCSB controller and/or
High-speed Serial Link Interface for Host
Applications (HSLA) board.
No power supply to the M1 or M2 None of the LEDs on the M1 or M2 □ Check the 125/28 V dc power supplies
controllers controller are lit. and replace if necessary.
□ Check the IP address of the
touchscreen.
No communication between the Controller is not responding to the
□ Replace the cable from the touchscreen
touchscreen and controller commands from the touchscreen.
to the Ethernet switch.

GE Internal
2.3 Auxiliary Module Troubleshooting
□ Breaker coil is broken. Replace the coil.
Flashing module not closing when FF breakers do not close or no CLOSE □ Using a meter, troubleshoot the close
command path from the control.
commanded to close command from the control.
□ Connect the battery power, if not
connected.
□ Use the ToolboxST application to detect
There are no correct values for the feedback the issue.
No feedback of bridge voltage □ Check the HVI boards and replace if
VARs in the Trender from lack of feedback
and current necessary.
from the bridge.
□ Replace the fiber-optic cables from the
HVI boards to the ERAX
□ Using an oscilloscope, monitor the
Exciter trips on dc overcurrent at The exciter trips when the load increases exciter output voltage for instability or
overshoots.
higher loads above 50%.
□ Connect the battery power, if not
connected.
A high level of harmonic noise was detected □ Using a scope, check the ac input
High level of harmonic by other users. voltage waveform.
disturbances at the ac incoming There is no indication that the ac line filter is □ Check the ac line filter fuses.
line actively working in the circuit (no heat □ Check the ac line filter resistors and
generated by the resistors). capacitors (if supplied).
□ Using a meter, check the integrity of the
When exciter under load, there is intensive line filter capacitors.
AC line filter resistor problem
heat generated by the ac line filter unit. □ Check if the capacitor is shorted and
replace if necessary.

GE Internal
2.4 Power Conversion Module Troubleshooting
41 ac or dc trips indicate open.
There may be a problem with the EAUX or
□ Adjust auxiliary contacts.
Breaker 41 not picking up coils Exciter High-speed Contactor Drive
(ERAX). □ Check the EAUX and/or ERAX boards.
Mechanical problems with the device.
□ Check the thermistor input.
□ Check the fans and fan rotation.
High bridge temperature The bridge is overheating. □ Verify that the cooling air input is not
blocked.
□ Check for high ambient air
temperature.
□ Check the fan power source and
connections.
Fan failures The fans are not operating. □ Check the seating of the fan module.
□ Check for high ambient air
temperature.
2.5 Runtime Warnings

Runtime warnings may occur during the download and expansion of the application code. Unlike errors, warnings do not halt
the expansion process. However, warnings are not displayed on the front panel LEDs; they are displayed at the serial port
(COM1) and in the ToolboxST application status window.

GE Internal
Notes

GE Internal
3 Specific Alarm Troubleshooting
The EX2100e control includes self-test diagnostics to aid in troubleshooting. The local operator interface, the optional
touchscreen, displays local operation status and diagnostic alarms. Diagnostic alarms indicate an abnormal condition
generated by the inner loop control or operating system. An alarm message and number are displayed, and possible causes
and solutions to aid in troubleshooting resolution are provided in the help file and the section, Specific Alarms. Some alarms
are not serious enough to automatically shut down or trip the excitation control. If the condition resolves itself, some alarms
will be automatically cleared. Other alarms, if not corrected within a certain time frame, will trip the control system. Alarms
can be reset from the ToolboxST application and the optional touchscreen. For further details, refer to EX2100e Excitation
and LS2100e Static Starter Control Systems Touchscreen Local Operator Interface Instruction Guide (GEI-100787).
Note The excitation control can broadcast codes through an Ethernet Global Data (EGD) link.
Alarm icon:
Green = No event
Yellow = Alarm present
Red = Trip present
Main Touchscreen
Specific Alarm Troubleshooting GEH-6788H Troubleshooting Guide 23

GE Internal
When the exciter annunciates an alarm, an icon is displayed on the main touchscreen and the code on the Alarm History
Buffer screen enables the operator to review the alarm description and reset the alarm. The text and color of the icon changes
from green (no event) to yellow (alarm) or red (trip). In a trip event, the exciter shuts down and the control should not be
restarted until the condition has been corrected. The controller’s red diagnostic LED is lit solid or flashes depending on the
type of alarm. Alarms are identified by number and descriptions, which are displayed using the touchscreen or the ToolboxST
application. For more information, refer to ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapters
related to EX2100e controls.
Alarm History Buffer Screen

GE Internal
3.1 EX2100e Control Regulator System Specific Alarms
The following alarms are specific to the EX2100e Control Regulator system.
2400
Description Fault Reset
Possible Cause No fault.
Solution No action; this is as designed for the control system.
2401
Description AtoD Gain(s) Flt
Possible Cause One of the ESYS analog channels failed during a calibration test.
Solution Check the ESYS and replace if other reasons for the failure are not found.
2402
Description Bridge Heat Sensor
Possible Cause The bridge temperature sensor for the bridge is faulty and gives an open indication due to:
• Faulty thermistor to the ERAX

• Faulty ERAX
• Faulty bridge temperature sensor
• Open wiring or poor connection
• Temperature reading is lower than P.RTDOpenCelsi
Solution
• Check the thermistor to the ERAX and replace the ERAX if necessary.
• Check the ERAX and replace if necessary.
• Check the bridge temperature sensor.
• Check wiring and connections.
• Check the temperature reading.
2403
Description Bridge Warm Alarm
Possible Cause Temperature feedback exceeded the alarm level as set by P.WarmCelsius due to:
• Problem with the converter air flow

• High ambient temperature
Solution
• Check the converter air flow.

• Check the ambient temperature and adjust as needed.
• Check the thermistor to the ERAX and replace if necessary.

GE Internal
2404
Description Extra Alarm
Possible Cause This extra alarm input is driven by a pointer and is specific to the application.
Solution Review the application.
2405
Description High Field Current
Possible Cause Field current has exceeded P.FldCurHiSet(Adc) for P.FldCurHiSec (sec). An unusual call for high field
current to meet power system demands has occurred due to:
• Parameters set incorrectly

• Faulty current feedback to the ERAX
Solution
• Check the parameter settings and adjust as needed.

• Check the current feedback to the ERAX.
2406
Description AlrmFldInvT
Possible Cause The field overcurrent inverse time device caused a alarm due toin correct operation or system conditions.
Solution Check for incorrect operation or system conditions that could have caused excessive field current for an extended
duration.
2407
Description FldMode: Current Reg
Possible Cause Field current regulation has been active after the delayed run time due to:
• OEL is online or offline

• High field current event
Solution
• If offline, check for a mistuned offline OEL pickup level V.OffLiOEPU.

• If online, verify that the parameter settings are property coordinated with the power system requirements.

GE Internal
2408
Description Field temp alarm
Possible Cause Field temperature (based on resistance calculation) exceeded P.HiFieldTemp due to:
• Field cooling problem

• Incorrect settings
• Bad generator voltage or current feedbacks
Solution
• Check the cooling system.

• Check the settings.
• Check the generator voltage and current feedbacks (EDFF).
2409
Description AlrmPTUV
Possible Cause A PT failure or undervoltage has occurred due to:
• PT fuses are blown

• PT switches are open
• Missing PT feedback (wiring)
• Voltage phase-to-phase unbalance
• ESYS failure
Solution
• Check PT fuses.
• Check PT switches and close if they are open.
• Check PT feedback (wiring).
• Check voltage phase to phase balance.
• Check the ESYS and replace if necessary.
2410
Description Alrm VHz Limit
Possible Cause The VHz limiter has became active while in auto mode due to:
• Undervoltage has occurred

• Generator ran down in speed prior to an exciter stop command
Solution
• Check for an undervoltage.

• Check the application configuration.

GE Internal
2411
Description AlrmVPTs_Rev
Possible Cause The main PT input frequency is reversed due to:
• Reversed phase sequence

• Problem with the PT wiring to switches
• Problem with wiring to the ESYS (TB2 44, 46, 48)
• P.GenRevSeqAdr is not in control
• ESYS failure
Solution
• Check the PT wiring to switches.

• Check the wiring to the ESYS (TB2 44,46,48).
• Verify that the parameter P.GenRevSeqAdr is in control.
2412
Description VPTs Failed (DualPT)
Possible Cause The main set of PTs have failed in dual PT mode due to:
• Lower voltage than the extra set

• Problem with wiring to the ESYS (TB2 44, 46, 48)
• ESYS failure
Solution
• Check the voltage reaching the ESYS screws (44, 46, 48).
• Check the wiring to the ESYS.
2413
Description AlrmXPTs_Rev
Possible Cause The extra PT input frequency was sensed reversed due to:
• Reversed phase sequence

• Problem with wiring to the ESYS
• P.GenRevSeqAdr is not in control
• ESYS failure
Solution

• Check the wiring to the ESYS (TB2 43, 45, 47).
• Confirm the use of P.GenRevSeqAdr is in control.

GE Internal
2414
Description VXTs Failed (DualPT)
Possible Cause The extra set of PTs have failed in dual PT mode due to:
• Lower voltage than the extra set

• Problem with wiring to the ESYS
• ESYS failure
Solution
• Check the voltage reaching the ESYS screws (43, 45, 47).
• Check the wiring to the ESYS.
2415
Description Aux52G Diag Flt
Possible Cause
• 52 device input does not match the other controller

• P.AuxForce52 mismatch between M1 and M2
• ESYS failure
Solution
• Check the 52 device input.

• Check P.AuxForce52 settings between M1 and M2.
2416
Description Aux86 Diag Flt
Possible Cause
• Lockout device (86) input does not match the other controller
• P.AuxForce86 mismatch between M1 and M2
• Wiring issue from the ERAX of one controller to another
• ERAX failure
Solution
• Check the 86 device input.

• Check P.AuxForce86 settings between M1 and M2.
• Check the wiring from the ERAX of one controller to the other controller.

GE Internal
2417
Description Capture sum ptr err
Possible Cause The capture summation only works with floats. It is not correct for any type other than floats.
Solution Review the data type used for summation.
2418
Description Cmd K3 Diag Flt
Possible Cause The state of the K3 driver command and the feedback from the relay driver on the ERAX disagree due
to:
• Problem with K3 coil

• Problem with K3 coil to ERAX-J7 harness
• ERAX failure
Solution
• Check the K3 coil.

• Check the K3 coil to ERAX-J7 harness.
2419
Description Cmd 41 Diag Flt
Possible Cause The state of the 41 driver command and the feedback from the relay driver on the ERAX disagree due to
failure of the ERAX.
Solution Check the ERAX and replace if necessary.
2420
Description DC Overcurrent Trip
Possible Cause Measured current has exceeded P.DC_FaultOC due to:
• External short circuit or low impedance on bridge output

• Incorrect shunt size for load
• Bad wiring
• Badly tuned regulator current regulator
• Rotating diode failure forced regulator current high
Solution
• Check for an external short circuit or low impedance on the bridge output.
• Verify the shunt size is correct for the load.
• Check and replace bad wiring.
• Retune regulator current regulator.
• Check for a rotating diode failure.

GE Internal
2421
Description DC Link Voltage Low
Possible Cause The measured DC link voltage is low by comparison to P.DCLinkLev due to:
• Source voltages to the regulator is low

• Possible missing phase if 3-phase input is required
• K3 did not close and the charging resistor is not bypassed
• ERAX dc link voltage sensing is bad
• PCM failure
Solution
• Check the source voltages to the regulator.

• Check for a missing phase if 3-phase input is required.
• Repair the problem in K3 circuit and replace the module.
• Check the ERAX and replace the board/module if necessary.
• Check the PCM and replace if necessary.
2422
Description Dyn Dis Cmd Fbk
Possible Cause
• Difference between the dynamic discharge command and duty

• Problem with the PCM.
• ERAX and/or power bridge control to an IGBT device has failed
Solution
• Check the DD command and duty and make adjustments as needed.

• Check for problems with the PCM and replace if necessary.
• Check the ERAX and/or the power bridge control to an IGBT device and replace if needed.
2423
Description Dyn Discharge Watts
Possible Cause The power dissipation limit of the dynamic discharge (DD) resistor has been exceeded due to:
• Possible short off the IGBT controlling DD

• Regulator current regulator is unstable
Solution
• Check for a short off the IGBT controlling DD

• Check the regulator current regulator stability.

GE Internal
2424
Description ACL/Inner Loop Heart Beat Alarm
Possible Cause There is no heart beat from the block area to the inner loop due to a missing application block or false
execution.
Solution Add the inverter block using application heart beat signals.
2425
Description ACL/Inner Loop Watchdog Alarm
Possible Cause There is a timing issue between the inner loop and block area.
Solution No action is required if this appears during startup, otherwise perform the following:
• Check for low idle time and reduce excessive blockware loading, if possible.
• Check for unusual system events that can cause excessive processor burden.
2426
Description ERAX Board Identifier
Possible Cause ERAX board identifier is incorrect.
Note This alarm should not occur without a board failure or an HSSL programming problem.
Solution
• Shut down and restart the control.

• Check the HSLA on the ERAX and replace if necessary.

GE Internal
2427
Description ERAX Power Supply Failure
Possible Cause
• Out-of-range power supply

• Pending power supply failure
Note ERAX PSOK monitors ±50 V input for the FGD power amplifier and 85G, ±8 V for the FGD and thermistor analog
signals, and 5V for the gate drive interfaces and other logic. The signal helps ensure that relays and gate drives fail to a benign
state.
A failure of one of these supplies will generate another alarm, such as out-of-range FGD or other feedback signals. Presence
of a PSOK alarm without other alarms may signal an out-of-range power supply and perhaps a pending failure.
Solution
• Check 28 V to the board at the J1 connector on the front of the PCM.

• Disconnect the FGD cable J2 on the front of the PCM. If the alarm clears, check for other problems, such as an EXAM
issue or field ground.
• Check for high surface contamination on the board and follow cleaning procedures.
• Check for excessive cabinet temperature and improve the thermal environment if not within specifications.
• Verify that the PSOK LED on the HSLA is lit. If P28 is good at ERAX-J1, but the HSLA PSOK is not lit, replace the
HSLA.
• If alarms clear when the controller is not running, check if K41 and K5T coils are excessively hot (drawing more than
rated current).
2428
Description ESYS Board Identifer
Possible Cause The ESYS board identifier is incorrect.
Note This should not occur without a board failure or HSSL programming problem.
Solution Check the ESYS and replace if necessary.
2429
Description ESYS Instance
Possible Cause The ESYS instance jumper is incorrect.
Solution Verify that JP3 is INS1.

GE Internal
2430
Description ESYS Power Supply Failure
Possible Cause
• Non-functional contact inputs

• Pending power supply failure
Note The ESYS power suppply monitor includes 55 V dc contact-in wetting voltage, 5 V dc logic supply, and a reset from
the HSLA, and helps ensure the DACs and relays fail to a benign state.
Presence of this alarm may explain other issues such as non-functional contact inputs, or a pending power supply failure.
Solution
• Check 28 V at the JS# connector for the offending section (M1, M2).
• Check for high surface contamination on the board and follow cleaning procedures.
• Check for excessive cabinet temperature and improve the thermal environment if not within specifications.
• Verify that the PSOK LED on the HSLA is lit. If P28 is good at ESYS-JS#, but the HSLA PSOK is not lit, replace the
HSLA.
• Check the open circuit voltage at the TB2 high side contact inputs (odd numbered terminals 27 - 39) and verify it is 50-55
V. Check for excessive loading on these contact inputs.
• Check the ESYS relays for possible coil shorts drawing excess current, including the following:
− Relay LEDs are lit
− No relays are excessively hot
− If the relay is removed, the PSGOOD alarm is clear
− Status feedback alarms are not occurring
2431
Description ESYS External Power Supply #1
Possible Cause
• P.ESYS_PS1_En is incorrect
• Problem with the cabling from the ESYS to the 28 V power supplies
• Problem with the wiring and overcurrent protection to the 28 V power supplies
• Problem with the incoming supply voltages
• PSOK LEDs on the supplies are not lit
• Failed 28 V output from the supplies
• ESYS failure
Solution
• Verify that P.ESYS_PS1_En is correct.

• Check the cabling from ESYS to the 28 V power supplies.
• Check the wiring and overcurrent protection to the 28 V power supplies.
• Check the incoming supply voltages.
• Verify that the PSOK LEDs on the supplies are lit.
• Check the 28 V output from the supplies and replace failed units.
• If the power supply is OK, check the ESYS and replace if necessary.

GE Internal
2432
Possible Cause
• ESYS failure
Solution

2433
Possible Cause
• ESYS failure
Solution


GE Internal
2434
Possible Cause
• ESYS failure
Solution

2435
Description ESYS Section (M1,M2) Incorrect
Possible Cause The cables from the ESYS sections to the corresponding master are incorrect.
Solution
• Check the wring and make corrections as needed.

• If the wiring is OK, check the HSLA and replace if necessary.
2436
Description Customer Analog 1
Possible Cause Customer analog input #1 to the ESYS does not match the other controller due to:
• Incorrect HSLA setting to the ESYS

• HSLA failure
• ESYS failure
Solution
• Check the HSLA setting to the ESYS.

• Check the HSLA and replace if necessary.

GE Internal
2437
Description Customer Analog 2
Possible Cause Customer analog input #2 to ESYS does not match the other controller due to:
• Incorrect HSLA setting to the ESYS

• HSLA failure
• ESYS failure
Solution
• Check the HSLA setting to the ESYS.

2438
Description Gen AC Gnd Flt Alm
Possible Cause
• Resistance is below the limit set by P.FGD_Ralarm and there is a ac ground

• Detector health unhealthy
• Generator ac ground
• Problem with the EXAM jumper settings
• ERAX internal failure
Solution
• Check the generator for an ac ground.

• Run a ground detector test to verify detector health.
• Check the parameters settings in the control and make adjustments as needed.
• Check the EXAM jumper settings.

GE Internal
2439
Description Grd Detector Cable
Possible Cause The cable to the EXAM of the field ground detector is open due to:

• Generator dc ground
• EXAM failure
Solution
• Check the generator for a dc ground.

• Check the able seating and replace the cable if necessary.
• Check the EXAM and replace the necessary.
2440
Description Gen DC Gnd Flt Alm
Possible Cause

Solution


GE Internal
2441
Description Gen Betw'n Bus Grd
Possible Cause
• Problem between the negative and positive bus

Solution
• Using V.GGDLocation, verify that 0 = negative bus and 1 = positive bus.

2442
Description Gen Gnd Flt Alm
Possible Cause

Solution


GE Internal
2443
Description Gen Gnd Flt Trip
Possible Cause
• Resistance is below the limit set by P.FGD_Rtrip and there is a ac ground

• Generator ground
Solution
• Check the generator for a ground.

2444
Description Gen Neg Bus Ground
Possible Cause
• Negative bus ground

Solution
• Check the generator for a negative bus ground.

2445
Description FGD Osc Neg V Low
Possible Cause The negative oscillator voltage is below acceptable limits.
2446
Description FGD Osc Pos V Low
Possible Cause The positive oscillator voltage is below acceptable limits.

GE Internal
2447
Description Gen Pos Bus Ground
Possible Cause
• Positive bus ground

• Incorrect parameter settings
Solution
• Check the generator for a positive bus ground.

2448
Description FGD Test Failed
Possible Cause The field ground detector oscillator and SVS test has failed due to:
• Incorrect settings, such as EXAM jumper settings

• Problem with the SVS
• Problem with the wiring from the EXAM
Solution
• Check all settings are correct, such as EXAM jumpers.

• Check the SVS.
• Check all wiring from the EXAM.
2449
Description 41M Fail to Open
Possible Cause
• Problem with the auxiliary feedback connection from the 41M device, causing the auxiliary contact to close
• Mechanical failure of the 41M device
• Incorrect software settings
Solution
• Check the auxiliary feedback connection from the 41 device.

• Check the 41 device for failure and replace if necessary.
• Check the software settings and make corrections as needed.

GE Internal
2450
Description 41M Fail to Close
Possible Cause
• Problem with the auxiliary feedback connection from the 41M device, causing the auxiliary contact to open
• Mechanical failure of the 41M device
• Incorrect software configuration of the 41M auxiliary and command
Solution
• Check the auxiliary feedback connection from the 41M device.

• Check the 41M device for failure and replace if necessary.
• Check the software configuration of the 41M auxiliary and command.
2451
Description Current Check Failed
Possible Cause During start/stop state 1, the field current was in excess of 5% AFNL (should be near zero, based on
modelled current in a brushless system) due to:
• Brushless system:
− Badly offset regulator current feedback
− Modeled field current and regulator current have in compatible settings
− Problem with the shunt wiring
− Bad ERAX circuitry
• DC Rotating system:
− Badly offset generator field current
− Problem with the fiber-optic cable from the EDFF to the ERAX
− Problem with the shunt wiring
− EDFF failure
− ERAX failure
Solution
• Brushless system:
− Run the offset removal test.
− Check the settings in the application software.
− Check shunt wiring.
− Check and Check the ERAX circuity and replace if necessary.
• DC Rotating system:
− Run the offset removal test.
− Check the fiber-optic cable connections from the EDFF to the ERAX.
− Check shunt wiring.
− Check the EDFF and replace if necessary.
− Check the ERAX and replace if necessary.

GE Internal
2452
Description Failure to Build
Possible Cause During a start, the field current was unable to build current to exceed P.IfldBuild in the allowed test time
P.BuildSec due to:
Note Multiple system errors, including improper configuration, internal or external failures, could be responsible.
General system:
• Power sources are not present

• Missing converter and/or incorrect wiring
• No output voltage
Brushless system:
• Problem with the shunt wiring.

• Modeled field current and regulator current have incompatible settings
• Bad ERAX circuitry
DC Rotating system:
• Problem with the shunt wiring.

• EDFF failure
• Problem with the ERAX circuitry
Solution
General system:
• Verify that the power sources are present.

• Verify that the converter and wiring are present and correct.
• Verify that the software settings are correct per past successful starts.
• Verify that the regulator can output voltage and monitor signals.
Brushless system:
• Check the shunt wiring and fix any wiring problems.

• Check the software and verify that the modeled field current and regulator current have incompatible settings.
• Check the ERAX circuity and replace if necessary.
DC Rotating system:
• Check the shunt wiring and fix any wiring problems.

• Check the EDFF and replace if necessary.
• Check the ERAX circuity and replace if necessary.
2453
Description Start Stop Logic
Possible Cause There is a system software error.
Solution Contact the nearest GE sales or service office, or an authorized GE sales representative.

GE Internal
2454
Description 41M Opened While Run
Possible Cause During the Running state, the 41M device auxiliary contact was sensed open due to:
• Problem with the auxiliary feedback connection from the 41M device
• Mechanical failure of the 41M
• External device has commanded the 41M to open
Solution
• Check the auxiliary feedback connection from the 41M device.

• Check the 41M device and replace if necessary.
• Check if an external device has commanded the 41M to open.
• Check the software settings and make adjustments as needed.
2455
Description AbortStop Trip
Possible Cause Other failures caused a shutdown through an abnormal sequence, including a stop given prior to reaching
the Running state.
Solution Clear all present diagnostics.
2456
Description Problem FieldCurrent
Possible Cause Field current measurement disagrees with the other controller due to:
• Problem with the shunt connections

• Problem with the connections to the EDFF
• Problem with the fiber-optic connections from the EDFF to the ERAX
• EDFF failure
• ERAX failure
Solution
• Check the shunt connections.

• Check connections to the EDFF.
• Check fiber-optic connections from the EDFF to the ERAX.

GE Internal
2457
Description Problem FieldVoltage
Possible Cause Field voltage measurement disagrees with the other controller due to:
• Problem with the shunt connections

• Problem with the connections to the EDFF
• Incorrect EDFF voltage jumper settings
• Problem with the fiber-optic connections from the EDFF to the ERAX
• EDFF failure
• ERAX failure
Solution
• Confirm that generator field voltage is zero by external measurement.

• Check the shunt connections.
• Check connections to the EDFF.
• Check the EDFF voltage jumper settings.
• Check fiber-optic connections from the EDFF to the ERAX.
2458
Description Problem Gating
Possible Cause The master gating control is suspected to have failed (based on modeling regulator voltage as firing
command times dc link voltage) due to:
• Problem with wiring and connections in the power circuit

• Problem with the power devices
• Problem with the dc link voltage measurement
• ERAX failure
Solution
• Check the wiring and connections in the power circuit.

• Check the power devices and replace if necessary.
• Check the dc link voltage measurement.
2459
Description Problem Hi Current
Possible Cause
• Generator high level current measurement disagrees with the other controller
• High negative sequence or dc component was present
Solution
• From the ToolboxST application, review the signals and make adjustments as needed.

GE Internal
2460
Description Problem Gen Current
Solution

GE Internal
2461
Description Problem with Regulator Current
Possible Cause Regulator current measurement disagrees with the other controller.
Solution
• Check shunt wiring and connectors.

2462
Description Problem with Regulator Voltage
Possible Cause Regulator voltage measurement disagrees with the other controller.
Solution
• Check module wiring.

2463
Description Problem Gen Voltage
Solution
2464
Description Problem ExtraVoltage
Possible Cause
• Extra generator or line voltage disagrees with the other controller

Solution
• From the ToolboxST application, review the signals.


GE Internal
2465
Description GP In 1 Diag Flt
Possible Cause
• General purpose ESYS input #1 did match the other controller

• Force parameter each controller is different
• Problem with the HSLA to the ESYS connection seating
• Problem with the HSLA
• Problem with the ESYS
Solution
• From the ToolboxST application, review signals and determine which master section is in error and compare them to the
actual hardware input state.
• Check the force parameter for each controller.
• Check the HSLA to the ESYS connection seating.
2466
Possible Cause

Solution

GE Internal
2467
Possible Cause

Solution
2468
Possible Cause

Solution

GE Internal
2469
Possible Cause

Solution
2470
Possible Cause

Solution

GE Internal
2471
Possible Cause

Solution
2472
Description GP Out 1 Diag Flt
Possible Cause The state of GP relay #1 on ESYS does not match the commanded state due to:
• Relay #1 is bad
• ESYS relay drive is bad
Solution
• Check if V.GpOut1_Rfb does not match V.GP_Output_1. If not, replace the relay.
• Check if V.GpOut1_Dfb does not match V.GP_Output_1. If not, check the ESYS and replace if necessary.
2473
• Relay #2 is bad
Solution

GE Internal
2474
• Relay #3 is bad
Solution
2475
• Relay #4 is bad
Solution
2476
Description Hw DC OverCurrent
Possible Cause A hardware detected overcurrent through the ERAX, which is the result of regulator current exceeding
2.5 times the regulator shunt value due to:
• External short circuit

• High capacitance loading on output
• Incorrect shunt size
• Problem with the shunt wiring
• Failed ERAX
Solution
• Check for an external short circuit and replace any bad circuitry.
• Check the high capacitance loading on output.
• Check the shunt size and replace with the correct size if necessary.
• Check the shunt wiring and fix any wiring issues.

GE Internal
2477
Description HW IGBT DD Fault
Possible Cause
• De-saturation
• Failed driver
Solution
• Check for an external short circuit.

• Replace the power device in the module.
2478
Description HW IGBT U Fault
Possible Cause
• De-saturation
• Failed driver
Solution

2479
Description HW IGBT V Fault
Possible Cause
• De-saturation
• Failed driver
Solution


GE Internal
2480
Description Peer Not Heard
Possible Cause
• Problem with the connection between the UCSx controllers

• Incorrect software configuration
• Faulty controller
Solution
• Check the connection between the UCSA/UCSB controllers

• Check the software configuration and make corrections as needed.
• Check the controller and replace if faulty.
2481
Description RDFD Alarm 1
Possible Cause Rotating Diode Failure detected based on harmonic level 1
Solution

• Check the harmonic detection threshold and frequency.
2482
Description RDFD Alarm 2
Possible Cause Rotating diode failure on harmonic level 2
Solution

2483
Description RDFD Trip 1
Solution


GE Internal
2484
Description RDFD Trip 2
Solution

2485
Description Start Dynamic Discharge Test Failure
Possible Cause
• Command versus feedback duty measurement mismatch

• Failure of the power device
• Failure of the ERAX
• Problem with the PCM
Solution
• Check the power conversion components, including the discharge resistor.

• Check the power device.
• Replace the PCM.
2486
Description Status 41 Bad
Possible Cause
• Problem with the wiring from the 41 device and the ERAX
• ERAX failure
Solution
• Check the wiring from the 41 device and the ERAX.

2487
Description ACL Not Ready
Note This alarm may occur during the startup sequence but should clear following a touchscreen reset.
Possible Cause
• Application is not properly configured (incorrect software download)

• Process failure
Solution Re-download and properly configure the software.

GE Internal
2488
Description Bridge Hot Trip
Possible Cause Temperature feedback from the power converter has exceeded the trip level as set by P.Hot_Celsius due
to:
• Problem with the converter air flow

• High ambient temperature
Solution
• Check the converter air flow.

• Check the ambient temperature.
• Check the thermistor to the ERAX and replace if necessary.
2489
Description Bridge Trip
Possible Cause A trip occurred in the bridge through the ERAX feedback signal due to:
• Hardware overcurrent
• Gate drive faults
Solution
• Check for a hardware overcurrent.

• Check for other diagnostic messages, such as Leg V, Leg U, Dynamic Discharge, and clear them.
2490
Description Trip from ERAX
Possible Cause The controller has lost communications from its ERAX board in the power conversion module due to:
• Incorrect software settings if consistently a fault

• Problem with the wiring from the UCSB to the HSLA on the ERAX
• Problem with the LEDs on the HSLA
Note This trip may appear at startup or during unexpected power supply events.
Solution
• Check the software settings and make adjustments as necessary.

• Check the wiring from the UCSB controller to the HSLA on the ERAX and make corrections as needed.
• Check the LEDs on the HSLA.

GE Internal
2491
Description Trip from ESYS
Possible Cause The controller has lost communications from its ESYS due to:
• Incorrect software settings if consistently a fault

• Problem with the wiring from the UCSB to the HSLA on the ESYS
• Problem with the LEDs on the ESYS or HSLA
Note This trip may appear at startup or during unexpected power supply events.
Solution
• Check the software settings and make adjustments as necessary.

• Check the wiring from the UCSB controller to the HSLA on the ESYS and make corrections as needed.
• Check the LEDs on the ESYS and/or HSLA.
2492
Description Trip External FGD
Possible Cause The application generated a trip from the external ground detector.
Solution Review the application for specific use.
2493
Description ACL GP Trip
Possible Cause The application generated a trip (general purpose).
2494
Description Trip via Lockout(86)
Possible Cause
• 86 lockout relay operated

• High transient noise on 86 wiring to ERAX from lockout relay
• Open wiring to 86 input to ERAX
• ERAX 86 input failure
Solution
• Check the generator protection relay initiating the 86 lockout relay and troubleshoot accordingly.
• Check for open wiring to the 86 input to the ERAX and the lockout relays.

GE Internal
2495
Description TripLOE1 (40 inner)
Possible Cause The impedance based 40 (LOE inner) device #1 caused a trip due to:
• Failure of the regulator or exciter to produce current

• Force trip from customer lockout (86 input)
• Improper software settings or system coordination
• Failure of ESYS sensing
Solution
• Check the regulator and exciter current for output.

• Check the customer lockout (86 input).
• Check the software settings and system coordination.
• Check the ESYS sensing and replace if necessary.
2496
Description TripLOE2 (40 outer)
Possible Cause The impedance based 40 (LOE outer) device #2 caused a trip due to:
• Failure of the regulator or exciter to produce current

• Force trip from customer lockout (86 input)
• Improper software settings or system coordination
Solution
• Check the exciter current for output.

• Check the customer lockout (86 input).
• Check the software settings and system coordination.
2497
Description NotRunning 52Closed
Note A lockout (86) trip is an expected indication of this alarm.
Possible Cause
• Closed 52G
• High noise level on 52G wiring
Solution
• Check the 52G contact input to the ESYS.

• Check the 52G wiring noise level.

GE Internal
2498
Description Trip OEL
Possible Cause The online (52G closed) field overcurrent inverse time device caused a trip due to:
• Software parameter settings prevented overexcitation limiters to hold current below the trip level
• OEL trip function is not coordinated with limiters
• Failure of the current regulator due to untuned settings
Solution
• Check for software parameter settings that prevented overexcitation limiters to hold current below the trip level.
• Coordinate the OEL trip function with limiters.
• Check the settings and tune as necessary.
2499
Description Trip Offline OEL
Possible Cause The off-line (52G open) field overcurrent inverse time device caused a trip from failure to regulate
terminal voltage or field current due to:
• Software parameter settings prevented overexcitation limiters to hold current below the trip level
• OEL trip function is not coordinated with limiters
• Failure of the current regulator due to untuned settings
Solution
• Check for software parameter settings that prevented overexcitation limiters to hold current below the trip level.
• Coordinate the OEL trip function with limiters.
• Check the settings and tune as necessary.
2500
Description Running at 0 speed
Possible Cause The exciter was in the Running state with 52G open and was not commanded to stop prior to generator
speed run down.
Solution Correct the external stop command.

GE Internal
2501
Description Trip Voltage High
Possible Cause Straight time high voltage device 59T caused a trip due to:
• AVR not regulating voltage due incorrect software configuration

• Faulty power converter control due to component failure
• System event raised voltage
Solution
• Check the software configuration and correct if necessary.

• Check the converter control components for failure.
• Check for a system event and raised voltage.
2502
Description TripVHz1
Possible Cause Straight time V/Hz 24T device #1 caused a trip due to:

Solution

2503
Description Trip VHz 2
Possible Cause Inverse time V/Hz 24T device #2 caused a trip due to:

Solution


GE Internal
2504
Description Trip Out 1 Diag Flt
Possible Cause The state of the trip #1 driver relay on the ESYS does not match the command due to:
• Incorrect seating of the HSLA on the ESYS

• HSLA failure
• ESYS failure
Solution
• Check for proper seating of the HSLA on the ESYS and make adjustments as needed.
2505
Description Trip Out 2 Diag Flt
Possible Cause The state of the trip #2 driver relay on ESYS does not match the command due to:
• Incorrect seating of the HSLA on the ESYS

• HSLA failure
• ESYS failure
Solution
• Check for proper seating of the HSLA on the ESYS and make adjustments as needed.

GE Internal
2506
Description Task 1 Exec Overrun
Possible Cause Task 1 (fastest) execution task exceeded the time available for completion.
Solution No action; this alarm is for reporting purposes only.
2507
Description Task 2 exec overrun
Possible Cause Task 2 (1 msec) execution task exceeded the time available for completion.
2508
Description Task 3 exec overrun
Possible Cause Task 3 (slowest) execution task exceeded the time available for completion.

GE Internal
2509
Description Exceed Max Zero Adj
Possible Cause An excessive offset has been detected during a push-button dc offset removal test (regulator and
generator field voltage and currents) due to:
• Regulator voltage:
− Regulator voltage incorrect external measurement
− Problem with the module wiring
− ERAX failure
• Generator and Exciter field voltage:

− Generator field voltage is zero
− Incorrect EDFF voltage jumper settings
− Problem with the connections to the EDFF
− Problem with the fiber-optic connections from the EDFF to the ERAX
− EDFF failure
− ERAX failure
• Generator and exciter field current:
− Problem with the generator shunt connections
− Problem with the connections to the EDFF
− Problem with the fiber-optic connections from the EDFF to the ERAX
− EDFF failure
− ERAX failure
Solution
• Regulator voltage:
− Confirm that regulator voltage is zero by external measurement
− Check the module wiring and make corrections as needed.
• Generator and exciter field voltage:

− Confirm that generator field voltage is zero using an external measurement.
− Check the EDFF voltage jumper settings and make adjustments as necessary.
− Check the connections to the EDFF.
− Check the fiber-optic connections from the EDFF to the ERAX.
• Generator and exciter field current:

− Check the generator shunt connections.
− Check the connections to the EDFF.
− Check the fiber-optic connections from the EDFF to the ERAX.

GE Internal
2510
Description Transfer LOE3
Possible Cause
• Loss of excitation from LOE device #3

• Incorrect protection versus limiter behavior
Solution
• Check for system failures that may have allowed for lack of regulation.
• Check for incorrect protection versus limiter behavior, such as the UEL.
2511
Description Transfer LOE4
• Loss of excitation from LOE device #4

Solution
2512
Description Transfer OEL
Possible Cause The backup master has detected an over excitation event and requested a master transfer due to:
• Overexcitation event
Solution
2513
Description Transfer VHz3 (str)
Possible Cause The C controller has made a master transfer request high V/Hz condition using its straight time V/Hz
device #3 due to incorrect protection versus limiter behavior such a incorrect V/Hz limit setting.
Solution
• Correct any incorrect V/Hz limit settings.

GE Internal
2514
Description Transfer VHz4
Possible Cause The C controller has made a master transfer request to a high V/Hz condition using its inverse time V/Hz
device #4. due to incorrect protection versus limiter behavior.
Solution
• Correct any incorrect V/Hz limit settings.
2515
Description ACL GP Alarm
Possible Cause The application generated an alarm trip (general purpose).
2516
Description Reverse Field Current
Possible Cause Generator shunt wiring reversed.
Note This trip may occur during some cross compound unit conditions when both the EX2100e control and other excitation
units are in parallel.
Solution Check if the generator shunt wiring is reversed.
2517
Description Problem on Low DC Link
Possible Cause Low dc link voltage caused a transfer to the backup controller due to:
• Problem with the supply power to the power converters

• Supply ac and dc breakers not closed
• Incorrect ERAX measured DC link voltage
• Incorrect software setting for incoming voltage level(s)
• PCM failure
Solution
• Check the supply power to the power converters.

• Verify that the ac and dc breakers (if present) are closed.
• If the ac and dc breakers breaker(s) are closed and power sources are present, check the ERAX measured dc link voltage.
Refer to V.DCLinkVolts.
• Verify that the software settings are at appropriate levels for the incoming voltage level(s).

GE Internal
2518
Description Trip on Low DC Link
Possible Cause The dc link voltage is below the parameter setting of DCLinkTrpLev due to:

• Supply ac and dc breakers not closed
• Incorrect ERAX measured DC link voltage
• Incorrect software setting for incoming voltage level(s)
• Problem with the dc link charging resistors (RCC)
• PCM failure
Solution
• Check the supply power to the power converters.

• Verify that the ac and dc breakers (if present) are closed.
• If the ac and dc breakers breaker(s) are closed and power sources are present, check the ERAX measured dc link voltage.
Refer to V.DCLinkVolts.
• Verify that the software settings are at appropriate levels for the incoming voltage level(s).
• Check the dc link RCC.
2519
Description CT Failure A phase
Possible Cause The AB and AC CT pairs show a high standard deviation on the current waveforms due to:
• Failure in the phase A CT

• Problem with the AB and AC CT, wiring, or switch
• ESYS failure
Solution
• Using the ToolboxST application tools, check phase A CT for failure.

• Inspect the AB and AC CT, wiring, or switch.

GE Internal
2520
Description CT Failure B phase
Possible Cause The AB and BC CT pairs show a high standard deviation on the current waveforms due to:
• Failure in the phase B CT

• Problem with the AB and BC CT, wiring, or switch
• Incorrect configuration of the ECTX on the ESYS module
• ESYS and/or ECTX failure
Solution
• Using the ToolboxST application tools, check phase B CT for failure.

• Inspect the AB and BC CT, wiring, or switch.
• Check the settings of the ECTX.
• If the problem persists, replace the ESYS and/or ECTX.
• Check the ESYS and the ECTX, and replace if necessary.
2521
Description CT Failure C phase
Possible Cause The BC and AC CT pairs show a high standard deviation on the current waveforms due to:
• Failure in the phase C CT

• Problem with the BC and AC CT, wiring, or switch
• ESYS failure
Solution
• Using the ToolboxST application tools, check phase C CT for failure.

• Inspect the BC and AC CT, wiring, or switch.
2522
Description CT Failure X phase
Possible Cause A single CT pair, or all three, show a high standard deviation due to:
• Failure in one or more of the CT pairs

• Problem with the CT wiring
• ESYS failure
Solution
• Using the ToolboxST application tools, check all phases of the CT for failure.
• Check for an unusual CT wiring error, such as an ESYS/EXCT input wired to the same phase.

GE Internal
2523
Description High DC Link Voltage
Possible Cause The dc link voltage has exceeded the setpoint due to:

• Misoperation of the dynamic discharge circuit
Solution
• Check both ac and dc sources to the power conversion units

• Check the dynamic discharge circuit
2524
Description ERAX HSLA Temperature Trip
Possible Cause The temperature of the HSLA on ERAX has exceeded the temperature trip setpoint.
Solution Using the ToolboxST application, perform the following:
• Check the temperature of the HSLA and the value of P.ERAXHotC.

• Check for excessively high ambient around the HSLA on the ERAX.
• Check the cooling fans and replace if necessary.
2525
Description ERAX HSLA Temperature Alarm
Possible Cause The temperature of the HSLA on ERAX has exceeded the temperature alarm setpoint.
• Check the temperature of the HSLA and the value of P.ERAXWarmC.

• Check for excessively high ambient around the HSLA on the ERAX.
• Check the cooling fans and replace if necessary.
2526
Description ERAX Group Trip
Possible Cause The ERAX group does not match the requirements.
Note This trip is not active in Simulator mode.
• Check the attribute, BridgeType, and verify that the ERAX board group is correct:
− 35 A requires ERAXH1
− 120 A requires ERAXH2
• Check P.ERAXGroup for any overrides.
• If the board group is incorrect, replace the ERAX.

GE Internal
2527
Description ERAX HSLA Temperature Diagnostic
Possible Cause The temperature of the HSLA on the ERAX is below the diagnostic setpoint.
• Check the temperature of the HSLA and the value of P.ERAXDiagC .

• Replace HSLA on the ERAX.
2528
Description Transfer Command Diagnostic
Note This diagnostic is produced by the backup controller and passed to the master as a Transfer Command alarm.
Possible Cause A command to transfer masters was attempted by the backup controller but the transfer did not occur
due to:
• Problem with the wire harness from EDSL (J5T) to K5T coil
• Problem with the wire harnesses from EDSL (J11M1, J11M2) to each PCM and the ERAX
• EDSL failure
• ERAX failure
Solution
• Check the wire harness from the EDSL (J5T) to the K5T coil as follows:
− If the K5 coil cannot energize, M1 will remain as master.
− Verify that the K5T coil resistance is less than 100 Ω.
− If the coil resistance is high, replace the K5T coil.
• Check the wire harnesses from the EDSL (J11M1, J11M2) to each PCM and to the ERAX located inside the PCM.
• Check the EDSL and replace if necessary.
• Check the ERAX (the backup master is the one that commands a transfer) and replace if necessary.

GE Internal
2529
Description Transfer Command Alarm
Note This alarm is produced by the active master as a result of receiving a Transfer Command diagnostic from the backup
controller.
Possible Cause A command to transfer masters was attempted by the backup controller but the transfer did not occur
due to:
• EDSL failure
• ERAX failure
Solution
2530
Description Transfer Without Command
Possible Cause A master transfer occurred without a command being issued due to:
• EDSL failure
• ERAX failure
Solution
2531
Description Peer Controller is Not OK
Possible Cause A controller was informed by the other controller that it is not OK. due to a trip or a problem.
Solution Using the ToolboxST application, investigate the peer controller for alarms to determine what is causing the
condition.

GE Internal
2532
Description K3 Fail to Close on Start
Possible Cause During the start sequence, K3 failed to close due to:
• Problem with the K3 coil

• Problem with the K3 coil to ERAX J-7 harness
• ERAX failure
Solution
• Check K3 coil.
• Check the K3 coil to ERAX-J7 harness.

GE Internal
Notes

GE Internal
4 Common Alarms
4.1 Controller Diagnostic Alarms
These diagnostic alarms are common among Mark Controls Platforms. However, some alarms are not applicable to all
controller platforms.
0
Description Diagnostic Alarm Reset
20
Description ToolboxST application detects unhealthy link or loss of communication between [ ] and controller.
Possible Cause
• I/O pack configuration files missing

• I/O pack restarted or did not complete startup
• I/O pack configured for dual networks, but only one network is connected
• Network issue preventing connection to ToolboxST application
• Power failure to the I/O pack
• Terminal board Bar Code entered incorrectly in ToolboxST configuration
• Wrong terminal board is configured in ToolboxST application
• I/O pack or module plugged into wrong jack on terminal board, or wrong jack number in ToolboxST configuration
• I/O pack configured in ToolboxST application, but configuration not downloaded to the controller
• I/O pack in program mode
Solution
• Verify that the Ethernet cables and network switch are operating correctly.
• Verify that the I/O pack configuration (such as Type, HW Form, Bar Code, position) matches the actual hardware.
• Manually restart the I/O pack or module.
• If ToolboxST 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.
• Build and download the configuration to the controller, wait for I/O pack communication status to change, then scan and
download to the I/O pack.
Note This alarm is not reported to the WorkstationST Alarm Viewer. This alarm is generated by the ToolboxST application,
not by the firmware.
Common Alarms GEH-6788H Troubleshooting Guide 73

GE Internal
21
Note This alarm is obsolete.
Description Control/Status communication failure between [ ] and controller
Possible Cause
• Asynchronous Drive Language (ADL) communication unhealthy

• Terminal board barcode typed incorrectly in the ToolboxST configuration
• Wrong terminal board is configured in the ToolboxST application
• I/O pack or module is configured in the ToolboxST application, but configuration is not downloaded to the controller
• I/O pack or module in program mode
Solution
• Verify that the I/O pack or module configuration (such as Type, HW Form, Bar Code, position) matches the actual
hardware.
• Perform a build and download the configuration to the controller, wait for pack communication status to change, then
scan and download to the I/O pack or module.
22
Description ToolboxST application detects a diagnostic status signal (...L3DIAG, ATTN, and/or LINK_OK...) is [ ];
therefore, the status signal is inaccurate, unknown, or indeterminate
Possible Cause
• I/O status signal quality in warning state

• Signal quality unhealthy, forced, or being simulated
• Status information inaccurate
Solution
• Check status signal health.

• Remove the force or simulated condition applied to the status signal.

GE Internal
23
Description ToolboxST application detects a major difference in [ ] controller application code
Possible Cause
• Compressing variables, EGD pages, distributed I/O, or NVRAM

• Changing frame or background period
• Changing controller or network redundancy
• Changing controller platform or NTP client mode
• Changing controller host name or IP address
• Changing IONet IP address
• Adding/removing first/last linking device (PFFA), respectively
• Removing a WCBM module
• Changing from multicast to broadcast (or vice-versa) I/O communication
• Adding the first Shared I/O module or connecting the first Controller to Controller I/O variable
• Removing the last Modbus Slave point
• Disabling controller web pages
• Disabling Wind Compress Data Log
• Disabling Wind Farm Management System
Solution Rebuild the controller and download.

GE Internal
24
Description ToolboxST application cannot retrieve diagnostics information from I/O pack [ ]
Possible Cause
• Cannot get requested information from I/O pack or module

• Communication program failure
• I/O pack or module unable to retrieve IP address
• Terminal board Bar Code entered incorrectly in ToolboxST configuration
• Wrong terminal board configured in ToolboxST application
• I/O pack or module configured in ToolboxST application, but configuration not downloaded to controller
• I/O pack or module in program mode
• I/O pack or module not able to load firmware
• Power failure to the I/O pack or module
Solution
• Verify that the I/O pack configuration (such as Type, HW Form, Bar Code, position) matches the actual hardware.
• Build and download the configuration to the controller, wait for pack communication status to change, then scan and
download to the I/O pack or module.
• Check network cables for proper connection.
• Verify that the switch is functioning correctly.

GE Internal
25
Note This alarm is obsolete.
Description Control/Status communication Error: [ ]
Possible Cause
• Cannot get diagnostic information from I/O pack or module

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

• Rebuild the application and download the firmware and application to the I/O pack or module.
• Check network cables for proper connection.
• Verify that the switch is functioning correctly.
259
Description Application Runtime Error - [ ] Frame overruns occurred
Possible Cause Overloaded processor sequencer malfunction (one or more frame overruns occurred)
Solution
For a controller, perform the following to increase the frame idle time:
• Reduce the application or increase the EGD period.

• Upgrade the controller to one with a faster processor.
• Replace the controller.
For an I/O module, perform the following:
• From the ToolboxST application, rebuild the system, then download the application and configuration to the I/O module.
• Replace the I/O module.

GE Internal
260
Description Application Runtime Error - [ ] Frame skips occurred
Possible Cause There is an overloaded processor or a processor malfunction. Frame number skips were detected. The
frame number should incrementally increase during Controlling state.
Solution
For a controller, do the following:
• Reduce the application or increase the EGD period to reduce the processor load.
• Upgrade the controller to one with a faster processor.
For an I/O module, do the following:
• From the ToolboxST application, rebuild the system, then download the application and configuration to the I/O module.
• Replace the I/O module.
279
Description Could not determine platform type from hardware
Possible Cause
• During commissioning/maintenance: Incorrect firmware version or hardware malfunction (firmware could not recognize
host hardware type)
• During normal operation: Hardware failure
Solution
• Verify that all connectors are aligned properly and fully seated.
• Check the firmware version for compatibility with platform. If correct, replace the controller.

GE Internal
280
Description Platform hardware does not match configuration
Possible Cause
• During commissioning/maintenance: Platform type identified in the application configuration does not match actual
hardware
• During normal operation: Hardware failure
Solution
• Fix the platform type in the ToolboxST application. From the General tab, select General Properties and Platform.
• Rebuild and download the application.
• If problem persists, replace the controller.
282
Description Firmware Load Error - application independent processes failed to initialize
Possible Cause Runtime malfunction. An application-independent firmware process could not be started successfully.
Solution
• Reload firmware and application and restart.

• If controller is a UCSA, try formatting and reloading the flash memory.
• If I/O pack has diagnostic: try to re-download the base load.
• Replace the controller or I/O module.
283
Description Firmware error - Internal process crashed
Possible Cause Runtime or hardware malfunction (runtime process failed).
Solution
• Reload firmware and application and restart.

• If controller is a UCSA, try formatting and reloading the flash memory.
• If this does not work, replace the controller.

GE Internal
292
Description Application Error - application overrunning the frame
Possible Cause Application cannot start within frame.
Solution Check application loading and reduce the amount of application code or frequency of execution. Build
application and download to all controllers.
294
Description Controller CPU overtemperature, Temp [ ] °C, Threshold [ ] °C
Possible Cause
• Excessive ambient temperature

• Hardware malfunction
• Fan loss
Solution
• Check the fan (if applicable), the ambient temperature, and for the presence of dust.
300
Description Application Code Load Failure
Possible Cause
During commissioning/maintenance:
• Invalid application configuration

During normal operation:
• Firmware or hardware malfunction
Solution
• Rebuild and download the application to all controllers.

• Reload firmware and application.

GE Internal
320
Description Process Alarm Buffers Full - controller can miss alarm transitions
Possible Cause
• Multiple alarm variables changing state too quickly to transmit all transitions
• Excessive alarms in queue (Plant-wide system failures)
Solution
During commissioning/maintenance:
• Reduce the number of alarms that can change state at the same time (filter alarm variables in the application code).
• Eliminate the conditions causing excessive process alarms.
321
Description Internal Runtime error - Process Alarms not being scanned
Possible Cause Runtime malfunction: alarms not being scanned. Controller may restart on software watchdog timeout
due to processor overload.
Solution
• Reload firmware and application, and restart.

322
Description Configuration Load error - Too many consumed EGD variables for Fault Tolerant EGD
Possible Cause Number of relevant, consumed UDH EGD variables exceeds fault tolerant EGD limitation of 1400 bytes
of data.
Normal UDH EGD operation not affected; however, in the event of UDH EGD failure, some consumed variables may not be
transmitted to redundant controllers over the IONet (if applicable).
Solution During commissioning/maintenance:
• Reduce the amount of relevant, consumed UDH EGD data by removing the appropriate number of variables from EGD
pages.
323
Description EGD Error - Fault Tolerant EGD activated
Possible Cause EGD exchange timeout occurred on requesting controller. Redundant processor (if applicable) is unable
to receive UDH EGD inputs and requested that EGD data be transferred over the IONet.
Solution
• Verify that all controllers on the UDH network are receiving all expected EGD exchanges.
• Verify that all relevant devices are powered on and producing data on the network.

GE Internal
324
Description EGD Error - Fault Tolerant EGD data requested
Possible Cause An EGD exchange timeout occurred on the requesting controller. Redundant processor (if applicable)
unable to receive UDH EGD inputs and has requested that EGD data be transferred over the IONet.
Solution
• Check UDH network and verify that all redundant controllers are receiving all expected EGD exchanges.
• Verify that all relevant devices are powered on and producing data on the network.
326
Description Communication lost from R processor
Possible Cause
• IONet or hardware malfunction

• S or T processor in redundant system lost communication with R processor
• Missing cable from the controller to the Unit Data Highway (UDH) network switch
Solution
• Go online with the R processor. Verify that the processor is in the Controlling state. If not communicating or in
Controlling state, restart the processor.
• Check for disconnected IONet cables or malfunctioning switches.
• Check for a defective Ethernet cable to network switch.
• Check for a defective network switch:
− Place the Ethernet cable into empty port.
− If the problem persists, replace the network switch.

GE Internal
327
Description Communication lost from S processor
Possible Cause

• R or T processor in redundant system lost communication with S processor
Solution
• Go online with the S processor. Verify that the processor is in the Controlling state. If not communicating or in
• Check for a defective Ethernet cable to network switch.
• Check for a defective network switch:
328
Description Communication lost from T processor
Possible Cause

• R or S processor in redundant system lost communication with T processor
Solution
• Go online with the T processor. Verify that the processor is in the Controlling state. If not communicating or in
• Check for a bad Ethernet cable to network switch.
• Check for a bad network switch:

GE Internal
329
Description Startup sequence failed - Data initialization timeout R processor
Possible Cause Controller unable to complete startup data initialization
• IONet malfunction
• Controllers have different application revisions
• One or more controllers powered down
• Controller overloaded by external command messages
Solution
• Check for disconnected IONet cables or malfunctioning network switches.

• Verify that all controllers are powered on.
• Disable all other command senders (for example, Modbus masters) until controller is online.
330
Description Startup sequence failed - Data initialization timeout S processor
Possible Cause Controller is unable to complete startup data initialization.
• One or more controllers are powered down
• Controller is overloaded by external command messages.
Solution

• Rebuild and download application.
• Ensure all controllers are powered up.

GE Internal
331
Description Startup sequence failed - Data initialization timeout T processor
Possible Cause Controller is unable to complete startup data initialization.
• One or more controllers are powered down
• Controller is overloaded by external command messages
Solution

• Rebuild and download application.
• Ensure all controllers are powered up.
332
Description Overtemperature - Controller rebooted and throttled
Possible Cause
• Excessive ambient temperature

• Fan loss
Solution
• Check ambient temperature.

• Check for dust buildup on the cabinet filters, controller, and power supply.
• Check fans.
334
Description Application Error – [ ] Frame Skips Detected
Possible Cause
• Hardware or IONet malfunction

• Frame number skips detected. Frame number should monotonically increase until rollover; alarm occurs following a
single frame number skips in successive frames.
Solution
• Check IONet (switches, cables).


GE Internal
335
Description Memory Verification Failed – Firmware Processes
Possible Cause A modification has occurred in the code segment for one of the processes. This indicates that a hardware
memory failure has occurred.
Solution Replace the controller.
336
Description Controller is Unlocked
Possible Cause
• Leaving Data Init control state and not locked

• The controller is unlocked through the ToolboxST application.
Solution From ToolboxST application, lock the controllers before running safety functions.
337
Description Output exchange disagreement detected
Possible Cause IONet malfunction or hardware problem. For at least one output, a difference was detected between the
controller outputs. This alarm remains active until the controllers agree on all outputs. A difference for non-Boolean data
generally indicates a deviation of more than 10% from the median value or no IONet EGD configuration is present. For
median values near zero, the variation exceeds integer 2 or real value 0.2.
Solution
• For the Mark VIe runtime, use the ToolboxST disagreement display (View | Disagreements) to determine which variables
are in disagreement.
• In the application, avoid use of global variable 'ControllerID' and avoid the use of sequencing block 'USB_HB'.
• Check IONet (switches, cables); rebuild and download application to all processors. If the problem persists, replace the
processor module.
347
Description Running Application does not match the Branded Application
Possible Cause Application not branded or different from branded version.
Note The purpose of branding is to label a verified safety application, and to ensure that it is running.
Solution
• Reload the branded application to the controller and I/O packs.

• Use the ToolboxST application to brand the currently running application.

GE Internal
348
Description Intermittent Communications on IONet1 – Packet Loss Exceeded [ ]%
Possible Cause
• Power cycled on I/O producer (controller or I/O module)

• Faulty Ethernet cable from I/O pack to IONet switch and/or from IONet switch to controller.
• Faulty IONet switch
• I/O message corruption
• Communication errors occurred on more than 5% of data transmissions on IONet1
Solution
• Check for evidence of I/O pack restart (diagnostic alarms, error logs).
• Replace Ethernet cable(s).
• Replace the I/O pack.
• Move the I/O pack’s Ethernet cable into an empty IONet switch port. If problem persists, replace the IONet switch.
349
Possible Cause

Solution
350
Possible Cause

Solution

GE Internal
352
Description Memory Validation Failed – Blockware Data Structures
Possible Cause A hardware memory failure because application process data was modified (data should not change after
controller goes online)
353
Description Memory Validation Failed – Configuration Shared Memory
Possible Cause A hardware memory failure because system process data was modified (data should not change after
controller goes online)
354
Description Memory Validation Failed – IONet Data Structures
Possible Cause There is a hardware memory failure because IONet process data was modified (data should not change
after the controller goes online)
355
Description State Exchange Voter disagreement detected
Possible Cause
• State Exchange disagreement found

• Application sequencing error
• IONet malfunction or hardware problem
Solution
• Use the ToolboxST disagreement display (View | Disagreements) to determine which variables are in disagreement.
• In the application, avoid use of global variable 'ControllerID' and avoid the use of 'USB_HB' block.
• Check IONet (switches, cables). If problem persists, replace the processor module.
356
Description NANs detected in CALC or NAN_BREAKER block
Possible Cause
• NaN (Invalid floating point number) received from I/O interface

• Hardware problem
Solution
• Check for external devices that may be sending NaNs to the controller.
• If conditions persists, replace the controller.

GE Internal
357
Description Internal Runtime error - Sequencer out-of-order or overrun detected
Possible Cause There is a possible hardware malfunction. Sequencer critical clients were scheduled out of order or were
overrun. This alarm occurs following three successive frames of sequencer critical client out-of-order detections. After five,
the controller is put into the FAILURE control state.
358
Description Internal Runtime error - Sequencer client execution underrun
Possible Cause Possible hardware malfunction. Sequencer critical client underrun detected. Alarm occurs after a
sequencer critical client has been run slower than its nominal rate three times in a row; after five, controller put in FAILURE
control state.
Solution
• Ignore this alarm if it occurs during a restart of the controller.

• If the alarm occurs during normal operation, then replace the controller.
359
Description Internal Runtime error - Sequencer client execution overrun
Possible Cause Possible hardware malfunction. Sequencer critical client overrun detected. Alarm occurs after a
sequencer critical client has been run faster than its nominal rate three times in a row; after five, controller put in FAILURE
control state.
Solution
• Ignore alarm if it occurs during a restart of the controller.

• Replace the controller, if the alarm occurs during normal operation.
360
Description Internal Runtime error - Sequencer frame period out-of-bounds (±15%)
Possible Cause Possible hardware malfunction. Frame period greater than ±15% of nominal. Alarm occurs following
frame period out-of-bounds condition occurring three frames in a row; after five, controller put in FAILURE control state.
Solution


GE Internal
361
Description Internal Runtime error - Sequencer frame state timeout out-of-bounds (±15%)
Possible Cause Possible hardware malfunction. Sequencer frame state timeout greater than ±15% of nominal. Alarm
occurs following a sequencer frame state timeout being out-of-bounds three frames in row; after five, controller put in
FAILURE control state.
Solution

362
Description Internal Runtime error - Sequencer frame number skip detected
Possible Cause Possible hardware or IONet malfunction. Frame number skips detected. Frame number should
monotonically increase until rollover; alarm occurs following three skips in a row, after five, controller put in FAILURE
control state.
Solution
• Ignore this alarm if it occurs during a restart of the controller.

• Check for hardware or network switch malfunction.

• Check for loose or defective network cables.
363
Description Memory Validation failed - Sequencer data structures
Possible Cause Hardware memory failure. Sequencer process data was modified (data should not change after the
controller is online).
364
Description Too many state voter disagreements detected
Possible Cause
• State exchange voter disagreement overflow. System exceeded the limit of 128 simultaneous disagreements at once.
• Application error
• Hardware problem or IONet malfunction
Solution
• Use the ToolboxST disagreement display (View | Disagreements) to determine which variables are in disagreement.
• In the application, avoid use of global variable 'ControllerID' and avoid the use of 'USB_HB' block.
• Check IONet (switches, cables).

GE Internal
374
Description Invalid Calibration Settings
Possible Cause
• Calibration file not detected

• Calibration file corrupted
• Calibration constants invalid
• Hardware Failure
Solution Replace the module.
375
Description Controller has entered Quality Control (QC) Mode
Possible Cause The device has received a command to enter factory QC mode.
Solution Reboot the device.
462
Description Hardware Reconfigured: Reboot by removing and reapplying power
Possible Cause Flash memory file system corruption.
Solution
• After reapplying power, Rebuild and download baseload, firmware and application.
• If the problem persists, replace the controller.
463
Description Internal runtime error - Could not create the Command and Event Log (CEL) file
Possible Cause Internal runtime error. Could not create the CEL file.
Solution
• Rebuild and download baseload, firmware, and application to the controller.

• If the problem persists, replace the controller.
464
Description Ethernet Interface [ ] disabled due to excessive traffic
Possible Cause Network interface has been disabled to protect itself from excessive activity on the network.
Solution
• Check for network loops.

• Monitor network activity and remove excessive traffic.

GE Internal
465
Possible Cause Network interface has been disabled to protect itself from excessive activity on the network
Solution

466
Possible Cause Network interface has been disabled to protect itself from excessive activity on the network
Solution

467
Solution

468
Solution


GE Internal
469
Description UDH EGD fault detected by the R processor
Possible Cause
• UDH EGD producer is powered down

• Producer is unhealthy
• Ethernet connection(s) failure
Solution
• Ensure all EGD producers are powered on and healthy.

• Check for a defective Ethernet cable from producer to network switch. Replace the cable(s).
• Check for a defective network switch by placing the producer's Ethernet cable into an empty port. If the problem persists,
replace the network switch.
• Replace the processor module.
470
Description UDH EGD fault detected by the S processor
Possible Cause

Solution
• Ensure all EGD producers are powered up and healthy.

• Replace the producer processor module.
471
Description UDH EGD fault detected by the T processor
Possible Cause

Solution


GE Internal
486
Description Auto-Reconfiguration server installation is incomplete
Possible Cause
• A download from the ToolboxST application to an I/O pack and/or the Auto-Reconfiguration server has failed
• Not all of the I/O packs were selected for download
Solution Perform a scan and download using the ToolboxST application.
487
Description Auto-Reconfiguration server failed scanning or downloading an I/O pack
Possible Cause At least one I/O pack is in an unexpected state that the Auto-Reconfiguration server is unable to handle
Solution
• Cycle power on the I/O pack.

• Perform a scan and download using the ToolboxST application.
488
Description EGD Error - Could not configure consumed exchanges from one or more Producers
Possible Cause
• Producer EGD Page(s) configured incorrectly

• Producer(s) powered down
• Network connectivity intermittent or severed
• Internal Firmware failure
Solution
• Rectify configuration error. Compress all pages and download application to Producer.
• Ensure each Producer is powered on and in the Controlling state.
• Refer to the Network Troubleshooting guide for possible solutions.
• Replace the Consumer and/or Producer hardware.

GE Internal
489
Description EGD Error - One or more consumed exchanges contain unbound variables
Possible Cause
• An EGD variable has been removed from a Producer's EGD configuration

• An EGD variable has been added to a different Producer's EGD Page from its original EGD Page
Solution
• Add the offending variable to the Producer's EGD configuration, compress the Page and download the application to the
Producer.
• Remove the reference to the offending variable from the Consumer's application code; build and download application to
the Consumer.
• Compress the EGD Page in the Producer where the variable has been added; build and download the application to the
Producer.
490
Description Software watchdog has been disabled
Possible Cause
• A runtime malfunction has disabled the software watchdog protective function

• An invalid version of firmware has been downloaded
Solution
• Reload base load, firmware, and application and restart.

• If using a UCSA, reformat the flash and reload the firmware.
• I/O pack or module: re-download the base load.
• If this does not work, replace the controller or I/O module.
491
Description Hardware watchdog has been disabled
Possible Cause
• A runtime malfunction has disabled the hardware watchdog protective function

• A hardware failure has disabled the hardware watchdog protective function
Solution
• Reload firmware and restart.

• If problem persists, replace hardware.

GE Internal
493
Description CDH EGD fault detected by the R processor
Possible Cause
• CDH EGD producer is powered down

Solution

494
Description CDH EGD fault detected by the S processor
Possible Cause

Solution


GE Internal
495
Description CDH EGD fault detected by the T processor
Possible Cause

Solution

496
Description Failed to incorporate the user-configured frame state timeouts
Possible Cause
• Invalid user-configured frame state timeout values

• Failed to parse the user-configured frame state timeouts file
Solution
• Timeout values configured by the user must satisfy the condition

Frame Rate > Output Timeout > App Timeout > Input Timeout > 0.
• Rebuild the application and force an offline download of the application to the controller.
497-498
Description Fan loss detected for controller fan [ ]
Possible Cause
• Fan power not applied
Solution
• Check the fan.

• Verify that the power connector is properly inserted.
• Replace the fan.

GE Internal
501
Description Total memory consumption has exceeded [ ] percent
Possible Cause Memory usage is driven from three functions:
• The online download procedure temporarily stores the previous and new application configuration in memory.
• The footprint of the application configuration/code has been enlarged.
• Memory usage can grow over time if there is a memory leak.
Solution
• The alarm should return to normal state after download is complete.

• Reduce the content of the application configuration/code.
• To address a memory leak, reboot the device to reinitialize baseline memory use. Monitor for reoccurrence and contact
your GE representative.
502
Description Syspage inconsistency detected
Possible Cause Memory corruption
Solution Restart the controller to re-initialize QNX syspage.
503
Description Communications timeout with Remote System Log Server
Possible Cause
• Remote Syslog server not in network

• Remote Syslog server down
• Incorrect Remote Syslog server IP address in system configuration
• Network issue (cables/switch) connecting controller to Remote Syslog server
Solution
• Verify that the Remote Syslog server is in operation.

• Verify that the correct Remote Syslog server IP address in the system configuration.
• Check the network connections.

GE Internal
504
Description Unauthorized executable was detected and terminated
Possible Cause When in Secure mode, the controller only permits authorized executables. An unauthorized executable
has been detected and dismissed.
Solution
• Inspect the syslog/error log messages

• Rebuild and download the baseload, firmware, and application to the controller.
• Re-install the ControlST application, then rebuild and download the baseload, firmware, and application to the controller.
505
Description R network shared I/O module inputs unhealthy
Possible Cause
• I/O module restarting or restarted

• I/O module application/configuration missing
• Application/configuration does not match in I/O module and controller
• Failed Ethernet connection between I/O module and controller
• Ethernet cable inserted into wrong connector on I/O module
Note When using the Shared IONet feature, this alarm is generated if there is a problem with receiving inputs from any
shared I/O module on the R IONet. Refer to Mark Controllers Shared IONet User Guide (GEH-6812).
Solution
• Rebuild and download application/parameters to all controllers and I/O modules.

• Reload firmware and parameters to the affected I/O module.
• Reload firmware and application to all controllers.
• If the problem persists, replace the affected I/O module, then replace the controller.

GE Internal
506
Description S network shared I/O module inputs unhealthy
Possible Cause

shared I/O module on the S IONet. Refer to Mark Controllers Shared IONet User Guide (GEH-6812).
Solution

507
Description T network shared I/O module inputs unhealthy
Possible Cause

shared I/O module on the T IONet. Refer to Mark Controllers Shared IONet User Guide (GEH-6812).
Solution

GE Internal
508
Description Application mismatch between redundant controllers
Possible Cause
• One processor installed new application code while the other processor(s) did not
• Processor was replaced and application code was built with a different version of the ToolboxST application
Solution
• Rebuild and download the application code to all controllers.

• Verify that the Application Code checkbox is selected in the download wizard for all controllers prior to downloading.
509
Description Controller certificate has been revoked
Possible Cause
• Controller certificate is in the Certificate Revocation List (CRL)

• Certificate Authority (CA) Administrator revoked the certificate
Solution
• Transition the controller from Secure to Open state then back to Secure to generate a new certificate and private key.
• Contact the Certificate Authority (CA) Administrator.
510
Description Controller certificate will expire within 30 days
Possible Cause Controller certificate will expire within 30 days
Solution

GE Internal
511
Description Controller certificate will expire within seven days
Possible Cause Controller certificate will expire within seven days
Solution
512
Description Controller certificate will expire in one day
Possible Cause Controller certificate will expire in one day
Solution
513
Description Controller certificate has expired; controller is no longer in Secure state
Possible Cause
• Controller is not in Secure state

• Controller certificate has expired
Solution
• Place the controller in the Secure state.

GE Internal
514-537
Description Controller To Controller (C2C) Inputs Unhealthy on IONet [ ] from ControlSet [ ]
Possible Cause
• Failed Ethernet connection between controllers

• Ethernet cable is inserted into the wrong connector on the IONet switch
• Controller to Controller (C2C) packet production is restarting or not occurring
• Application or configuration is missing in the controller or does not match in both controllers
Note A control set is a controller in a shared IONet group. There are 24 Controller to Controller (C2C) diagnostic alarms
assigned for eight control sets. Each control set contains three diagnostics for its IONets.
Solution
• Check for Ethernet connectivity between the controllers.

• Rebuild and download the application to all controllers.
• Reload the firmware and application to all controllers.
• If the problem persists, replace the affected switch and Ethernet cables, then replace the controller.
538
Description Certificate Authority (CA) certificate will expire within 30 days
Possible Cause CA certificate will expire within 30 days
Solution Contact the CA Administrator.
539
Description Certificate Authority (CA) certificate will expire within seven days
Possible Cause CA certificate will expire within seven days
540
Description Certificate Authority (CA) certificate will expire within one day
Possible Cause CA certificate will expire within one day

GE Internal
541
Description Certificate Authority (CA) certificate has expired; controller is no longer in Secure state
Possible Cause CA certificate has expired
542
Description Certificate Revocation List (CRL) has expired
Possible Cause CRL has expired
Solution
1. Contact the CA Administrator and request/confirm the renewal of the CRL.
2. After the CRL is renewed, from the Mark VIe Device menu select View | Diagnostics | Controller Advanced Diagnostics.
3. Expand the Commands tree, expand the Diagnostics tree, and double-click Get CRL for controller from CA
Server.
4. Confirm the reply, CRL received successfully, which indicates that the Mark VIe to CA Server connection is healthy.
5. Close the Advanced Diagnostics Commands window.
543
Description Total memory consumption has exceeded [ ] percent
Possible Cause
• Memory leak
• Application code is too large
Solution
• Decrease memory usage.

• Restart the controller.
544
Description Communications error with Certificate Authority Server
Possible Cause
• Certificate Authority (CA) server not in network or not in operation (server is down)
• Incorrect CA server IP address in system configuration
• Network issue (cables/switch) connecting controller to CA server
Solution
• Verify that the CA server is in operation.

• Verify that the CA server IP address is correct in the system configuration.
• Check the network connections.
GE Internal
545
Description Active PFFA diagnostics detected
Possible Cause At least one configured PFFA module contains an active diagnostic. Since each controller within a
control set monitors the diagnostic conditions of PFFA modules and connected Fieldbus devices, PFFA diagnostics may differ
between the individual controllers.
Solution
• If there are active PFFA diagnostics in the WorkstationST Alarm Viewer, correct those issues.
• If there are no active PFFA diagnostics in the Alarm Viewer, go online specifically to the controller with this 545
diagnostic using the ToolboxST application. From the Component Editor Hardware tab, select the PFFA with active
diagnostics, and correct the identified issues.
546
Description This component is or has been in factory test mode.
Possible Cause The controller or I/O pack has received the command to enter factory test mode.
Solution Reboot the I/O pack or controller.
547
Description Default user password detected
Possible Cause The controller password is the default value.
Solution From the ToolboxST application, set the password.
Note It is the user’s responsibility to change the default password to a unique password. If you do not know the default
password, contact the nearest GE Sales or Service Office, or an authorized GE Sales Representative.
To change the controller password, refer to the ToolboxST User Guide for Mark Controls Platform (GEH-6703), the section
Controller Password Change.

GE Internal
1000-2024
Description Inputs unhealthy on IO Module [ ], R pack IONet [ ] - Message Timeout
Possible Cause
• I/O pack restarting or restarted

• I/O pack application/configuration is missing
• Application/configuration does not match in the I/O pack and controller
• Failed Ethernet connection between I/O pack and controller
• Ethernet cable inserted into wrong connector on I/O pack
Solution
• Reset all diagnostic alarms.

• Rebuild and download application to all controllers and I/O packs.
• Verify that Ethernet cable on I/O pack matches the ToolboxST configuration.
• Check for faulty Ethernet cable from pack to network switch and/or from switch to controller. Replace cable(s) if
necessary.
• Defective network switch, place I/O pack's Ethernet cable into empty port. If problem persists, replace network switch.
GE Internal
1000-2024
Description Inputs unhealthy on IO Module [ ], S pack IONet [ ] - Message Timeout
Possible Cause

Solution

• Check for faulty Ethernet cable from I/O pack to network switch and/or from switch to controller. Replace cable(s) if
necessary.
1000-2024
Description Inputs unhealthy on IO Module [ ], T pack IONet [ ] - Message Timeout
Possible Cause
• Pack restarting or restarted

Solution

necessary.

GE Internal
1000-2024
Description Inputs unhealthy on IO Module [ ], IONet [ ] - Message Timeout
Possible Cause

Solution

necessary.
1000-2024
Description Inputs unhealthy on IO Module [ ], R pack IONet [ ] - Message Length not valid
Possible Cause Application/configuration does not match in the I/O pack and controller.
Solution
• Rebuild and download application/parameters to all controllers and I/O packs.

• Reload firmware and parameters to the affected I/O pack.
• If problem persists, replace affected I/O pack, then replace controller.
1000-2024
Description Inputs unhealthy on IO Module [ ], S pack IONet [ ] - Message Length not valid
Solution

GE Internal
1000-2024
Description Inputs unhealthy on IO Module [ ], T pack IONet [ ] - Message Length not valid
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ], IONet [ ] - Message Length not valid
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ], R Pack IONet [ ] - Major Signature Mismatch
Solution


GE Internal
1000-2024
Description Inputs unhealthy on IO Module [ ], S Pack IONet [ ] - Major Signature Mismatch
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ], T Pack IONet [ ] - Major Signature Mismatch
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ] IONet [ ] - Major Signature Mismatch
Solution

GE Internal
1000-2024
Description Inputs unhealthy on IO Module [ ], R Pack IONet [ ] - Minor Signature Mismatch
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ], S Pack IONet [ ] - Minor Signature Mismatch
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ], T Pack IONet [ ] - Minor Signature Mismatch
Solution


GE Internal
1000-2024
Description Inputs unhealthy on IO Module [ ] IONet [ ] - Minor Signature Mismatch
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ], R Pack IONet [ ] - Timestamp Mismatch
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ], S Pack IONet [ ] - Timestamp Mismatch
Solution

GE Internal
1000-2024
Description Inputs unhealthy on IO Module [ ], T Pack IONet [ ] - Timestamp Mismatch
Solution

• If problem persists, Immediate Attention Required: Fieldbus I/O Module [ ] Not Detected on IoNet [ ]ts, replace affected
I/O pack, then replace controller.
1000-2024
Description Inputs unhealthy on IO Module [ ] IONet [ ] - Timestamp Mismatch
Solution

1000-2024
Description Inputs unhealthy on IO Module [ ] IONet [ ] - Message Timeout
Solution


GE Internal
1000-2024
Description Immediate Attention Required: Fieldbus I/O Module [ ] Not Detected on IoNet [ ]
Possible Cause Note: If this diagnostic is active, the module needs to be replaced immediately. If it is simplex, the
devices under this PFFA have lost communication. If it is redundant and not replaced, and a controller on the remaining
module's IONet goes down, then control is lost for all devices under the PFFA modules.
• PFFA module did not complete Start

• PFFA module configuration files missing
• PFFA module restarted
• PFFA module configured for Hot Backup, but only one network is connected
• Serial connection between PFFA modules is broken
• Network issue
Solution
• If the Control/Status communication is working correctly, any additional diagnostics should indicate the cause of the
problem.
• Build and download parameters to the PFFA module and controller.
• Verify Serial cable is attached correctly.
• Verify that the Ethernet cables and network switch are operating correctly.
• Manually restart the PFFA module.
GE Internal
Glossary of Terms
Application code Software that controls the machine or process, specific to the application.
Automatic Voltage Regulator (AVR) AVR is controller software that maintains the generator terminal voltage through
the Field Voltage Regulator.
Auxiliary source A source of 3-phase ac power for the exciter, but not from the generator being controlled.
Board Printed circuit board
Bus Upper bar for power transfer, also an electrical path for transmitting and receiving data.
Configure To select specific options, either by setting the location of hardware jumpers or loading software parameters
into memory.
CT Current transformer, used to measure current in an ac power cable.
DACA Ac-to-dc converter for power supply, produces 125 V dc.
De-excitation The de-excitation circuit produces a conduction path through a discharge resistor or inductor to dissipate the
field current after a unit trip.
Device A configurable component of a control system.
Dual Redundancy An operation that uses two sets of control, I/O, and power channels in a redundant configuration for
higher reliability.
EDIS Exciter Power Distribution Module distributes 125 V dc to the power supplies.
EGD Ethernet Global Data, a control network and protocol for the controller. Devices share data through EGD exchanges
(pages).
Ethernet LAN with a 10/100 Mbit collision avoidance/collision detection system used to link one or more computers
together. Basis for TCP/IP and I/O services layers that conform to the IEEE 802.3 standard.
EX2100e Exciter GE static exciter; regulates the generator field current to control the generator output voltage.
Field flashing The supply of initial exciter current during startup, usually from station batteries.
Field ground detector The field ground detector is an active circuit that detects a ground in either the ac or dc sections of
the exciter and field wiring.
Firmware The set of executable software that is stored in memory chips that hold their content without electrical power,
such as EEPROM or Flash.
Gating Controlling the conduction of the power IGBTs or SCRs with an input pulse train (or a voltage).
HMI Human-machine Interface, usually a computer running Windows and CIMPLICITY HMI software.
I/O Input/output interfaces that allow the flow of data into and out of a device.
IP address The address assigned to a device on an Ethernet communication network.
Line filter Filter networks across the 3-phase input lines to the exciter to minimize the voltage spikes that result from the
abrupt decay of current during SCR commutations.
Power Conversion Module (PCM) The PCM or Bridge consists of six thyristors connected in a 3-phase bridge, with
associated protection and control devices, to generate the dc field voltage.
GEH-6788H Glossary of Terms 115

GE Internal
Power Current Transformer (PCT) A PCT can be attached to the generator line to provide a portion of the 3-phase
power for the exciter, part of a compound source.
Power Distribution Module (EDIS) The PDM distributes 125 V dc to the power supplies for the controllers and I/O
termination boards.
Permanent Magnet Generator (PMG) source An application in which the exciter receives ac power for the field from
a PMG mounted on the shaft of the generator. The PMG output frequency is typically 420 Hz or higher.
Power Potential Transformer (PPT) A PPT is attached to the generator terminals or an auxiliary bus to provide 3-phase
power for the exciter; referred to as a potential source.
Power System Stabilizer (PSS) PSS software produces a damping torque on the generator to reduce generator
oscillations.
Product code (runtime) Software stored in the controller's memory that converts application code (pcode) to executable
code.
PRV resistors These resistors reduce stress on the SCRs by balancing voltages on the SCRs during pole slip events.
PT Potential Transformer, used for measuring voltage in a power cable.
Redundant A system containing of duplicated components (boards or modules), which can transfer functionality from a
failed component to one of the duplicate components without loss of the entire system's functionality.
RTD Resistance Temperature Device, used for measuring temperature.
Runtime errors Controller problems indicated on the front panel by coded flashing LEDs, and also in the Log View of the
ToolboxST application.
Signal The basic unit for variable information in the controller.
Simplex System with only one set of control and I/O modules. Contrast with redundant control systems.
TCP/IP Communications protocols developed to inter-network dissimilar systems. It is a de facto UNIX standard, but is
supported on almost all systems. TCP controls data transfer and IP provides the routing for functions.
TMR Triple Modular Redundancy. An operation that uses three sets of control and I/O (channels M1, M2, and C) and votes
the results.
ToolboxST application A Windows-based software package used to configure the EX2100e and Mark VIe turbine
controller.
Touchscreen Diagnostic Display Interface also referred as keypad provides exciter status icons and displays fault
information. It can also be used to run the exciter, reset the exciter, display data, and provide other control functions.
116 EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

GE Internal
Unit Data Highway (UDH) Connects the EX2100e, Mark VIe turbine controllers, LS2100e, PLCs, and other GE provided
equipment to the HMI servers; runs at 10/100 Mbaud and supports peer-to-peer communications.
Warm backup (WBU) Two bridges are connected to the field but only one is actively producing power. The other bridge
does not receive gating pulses until it is required to take over from the active bridge.
GEH-6788H Glossary of Terms 117

GE Internal
Notes
118 EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

GE Internal
GE Internal

EX2100e Excitation System Troubleshooting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EX2100e Excitation System Troubleshooting

Uploaded by

Copyright:

Available Formats

GEH-6788H

EX2100e Excitation Control

For maintenance information, refer to the following document:

Revised: Dec 2017

© 2011 – 2017 General Electric Company.

We would appreciate your feedback about our documentation.

Related Documents Added GEH-6721_Vol_II

Acronyms and Abbreviations

GEH-6788H Troubleshooting Guide 3

4 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

Indicates a procedure or condition that, if not strictly observed, could result in

Indicates a procedure or condition that should be strictly followed to improve these

GEH-6788H Troubleshooting Guide 5

To prevent personal injury or damage to equipment, follow all equipment safety

To minimize hazard of electrical shock or burn, approved grounding practices and

To prevent personal injury or equipment damage caused by equipment malfunction,

6 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

Overview GEH-6788H Troubleshooting Guide 7

8 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

Overview GEH-6788H Troubleshooting Guide 9

Grounding Balls Specifications

• IEC 61230, Portable Equipment for Earthing or Earthing and Short-Circuiting

10 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

Causes and Preventive Practices for Arc Flash Events

Overview GEH-6788H Troubleshooting Guide 11

12 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

Overview GEH-6788H Troubleshooting Guide 13

14 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

General Troubleshooting GEH-6788H Troubleshooting Guide 15

AC or DC input breakers □ Check the line filter or battery filters.

16 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

General Troubleshooting GEH-6788H Troubleshooting Guide 17

18 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

General Troubleshooting GEH-6788H Troubleshooting Guide 19

20 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

2.5 Runtime Warnings

General Troubleshooting GEH-6788H Troubleshooting Guide 21

22 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

Specific Alarm Troubleshooting GEH-6788H Troubleshooting Guide 23

Alarm History Buffer Screen

24 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

Possible Cause No fault.

Solution No action; this is as designed for the control system.

• Faulty thermistor to the ERAX

• Problem with the converter air flow

• Check the converter air flow.

Specific Alarm Troubleshooting GEH-6788H Troubleshooting Guide 25

Solution Review the application.

• Parameters set incorrectly

• Check the parameter settings and adjust as needed.

• OEL is online or offline

• If offline, check for a mistuned offline OEL pickup level V.OffLiOEPU.

26 GEH-6788H EX2100e Excitation Control Diagnostic Alarms for Regulator Systems

• Field cooling problem

• Check the cooling system.

Possible Cause A PT failure or undervoltage has occurred due to:

• PT fuses are blown

• Undervoltage has occurred

• Check for an undervoltage.

Specific Alarm Troubleshooting GEH-6788H Troubleshooting Guide 27

Possible Cause The main PT input frequency is reversed due to:

• Reversed phase sequence

• Check the PT wiring to switches.