Professional Documents
Culture Documents
Gas Turbine Control
Gas Turbine Control
While it's not likely that a single control processor or a single protective processor will try to trip the turbine, it is
possible and does very rarely occur (and is accompanied by Diagnostic Alarms, and in some cases, a Process Alarm or
two). But, this is all done in "hardware" using traces on the TRPG and TREG cards and contacts of the PTR and ETR
relays. So, this is how a software-generated/detected trip will eventually cause a turbine trip (by removing either or
both of the 125 VDC sides of the power supply to the fuel stop solenoid). Again, the PTRs are on the TRPG and the
ETRs are on the TREG. It's this combination of software and hardware that makes the Speedtronic so reliable (because
this is used in one way or another in all the digital Speedtronic turbine control systems, from Mark IV through the
Mark VIe).
It's also important to note that the emergency overspeed protection in the <P> core (performed by each of the VPROs)
is also a speed rate-of-change protection. So, if the speed increases really fast, or if it decreases really fast, then the
overspeed detection will be actuated and the ETR for that VPRO will trip. I said "... the ETR for that VPRO will
trip...." because there are three independent speed pickups, one to each of the VPROs, so that if one speed pickup fails
when the turbine is running then the VPRO that speed pickup is connected to will de-energize it's ETR relay. Speed
pick-ups don't usually all fail at the same time, but when they do fail they usually fail intermittently at first, which can
drive the VPRO it's connected to crazy--generating a lot of nuisance alarms (Process- and Diagnostic). But, that's
better than tripping the turbine, and it is an indication that the speed pickup is failing or has failed. And, at least one of
the Process Alarms that will be annunciated will be an "overspeed" alarm--because either the speed feedback is
intermittently changing very quickly, or it has dropped precipitously to zero, and either of those conditions will actuate
the overspeed detection logic because of a sudden change in the rate of speed increase and/or decrease.
Next reply will cover how the E-Stop P/Bs "control" the ETRs. But, if you want to anticipate the discussion, have a
look at the drawings in the System Guide manual.
Finally, I'm no "wizard" or super-intelligent person. I had the good fortune to spend a lot of years waiting for
construction personnel to finish installing turbines (including the wiring and field devices) and used that time to study
the drawings and manuals. I was also fortunate enough to have had the ability to contact knowledgeable individuals
who could "fill in the gaps" for me early in my career, and used that to form my "thinking" and deduction skills.
There's still a LOT I have to learn, and aLOT I haven't seen, but using the philosophies I've come to learn and
understand it's usually not too difficult to understand why or how some things are done the way they are even if they
seem to be very convoluted. As we've learned, some things are actually very simple though they appear to be very
complicated.
There are MANY ways to enhance and improve the reliability and availability of control systems--not just this way.
But, I've come to know that the methods employed by GE (even though they are NOT well-documented, if they are
documented at all) are among the simplest and most robust in the power generation industry--again, even if at first
glance they seem very complicated. It just takes a willingness (and the time!) to dig into the available documentation
and manuals and follow signals through the circuits and logic. That's one of the really good things about GE
Speedtronic turbine control systems--they are usually much better documented than most other comparable systems.
By that I mean that there most of the algorithms and "blocks" used have very simple diagrams which can be used to
understand the flow of signals through them. Most of the other control systems I encounter just use empty rectangles
with some inputs and outputs (and the inputs and outputs can be on either side, top or bottom of the empty rectangle)
to represent functions or algorithms. One has to find a manual to understand what happens inside the empty rectangle,
and that's not always easy to do because many of the descriptions don't include and "logic" diagrams, just words.
I appreciate your kind words, but, they are unwarranted except to the extent that I spent a good many nights and
weekends in hotel rooms all around the world studying and marking-up drawings and redrawing diagrams (all unpaid)
in order to improve my understanding. Because of the kind and helpful people I encountered early in my career as a
Field Engineer I try to help as many people as I can to help develop and improve their understanding--because had I
not had the extremely good fortune to have worked with those people I would have left this field very quickly, because
of the poor training I received early on and the dearth of documentation available. So, really I'm just repaying a debt of
gratitude for the knowledge and guidance I received early on. So, now more thanks are required. I do appreciate
positive--as well as negative feedback (when accompanied by an explanation of what could have been done better!)--
but let's just keep the kind words to feedback, positive and/or negative.
Also, if you have other questions or functions you want to understand please open a thread and we can try to help
explain them.
Next reply will cover how the E-Stop P/Bs "control" the ETRs. But, if you want to anticipate the discussion, have a
look at the drawings in the System Guide manual.
CSA, i am learning to read hardware drawings. I think if E-stop PB is pushed down, then the power of ETR will lost.
thus fuel solenoid is cut off electricity, and the GT trips.
I am not sure whether it is right but i tired!
CSA, i think i am fortune to find this forum, and encounter you, and your reply helps me a lot. Without your help, i am
not sure where i am. The GT control seems so difficult to learn for me at very beginning.
I think there is a long way to go, but i am willing to continue.
Thanks a lot!
Best regards!
Neo
2)
3) Seven (7) discrete trip inputs to TRPG which open to trip; remember these cannot be inverted, and they cannot be
forced in Toolbox/ToolboxST.
So, the TRP legs of each of the seven inputs go to the VPRO--not to <Q>, and somehow, in the firmware of the VPRO
the state of the input is monitored and used as a "permissive" for the Relay Driver outputs from <X>, <Y> and <Z>
to the ETR coil circuits (over the same cables, JX1, JY1 and JZ1).
CSA,i am not clear about the relationship between L4 and 7 discrete trip inputs. Are these 7 discrete inputs one part of
L4T logic or they are independent of L4T? Are these 7 discrete trip inputs only monitored in <P> core? Or can we see
thers logic signals via toolbox?
Can you take one example of these 7 trip inputs? I am wondering what kind of discrete inputs should be connected to
TREG terminal board.
I checked on my site,and think l86tgt1 may be one of the 7 trip inputs,and it is one part of L4T logic.
3)
So, what appears to be happening is that the trip "interlocks" are being used as permissives (normally closed
contacts) for the Relay Driver outputs from <X>,<Y> and <Z> VPROs to the ETR circuits on the TRPG.
You said they are normally closed contacts. Does that mean if the trip input is logic 0,then the turbine trips?
Hope i am clear this time.
Best regards!
Neo
By CSA on 4 November, 2014 - 8:48 am
1 out of 1 members thought this post was helpful...
Neo,
1) Yes; there are ways to trip the turbine via the Control Oil or Trip Oil system. Units with a mechanical overspeed
bolt will trip via the Control- or Trip Oil systems, and some units have a manual "Trip" button or lever in the
Accessory Compartment that will also trip the turbine via the Control or Trip Oil System.
2) I don't have access to a Mark VI System Guide at the present time or I would refer to the VPRO/TREG section to
try to give a more concise answer. GE does some "unusual" and inconsistent things from time to time, and I believe
this is one of those consistently inconsistent things--using the TREG discrete inputs in the L4T rung(s). These seven
discrete trip inputs were essentially added to the TREG for SIMPLEX tripping purposes, and it was my understanding
that they were not typically used for TMR applications. They were meant to be used to trip via the ETRs in the event
that communication between <R> and <P> was lost--in effect, a back-up or redundant trip method. Usually, a second
contact of the low-low L.O. pressure switch, for example, was wired to the TREG and used to trip the turbine in the
event that <R> didn't recognize a change of state of it's low-low L.O. pressure trip discrete input.
Because there is no application code which is visible using Toolbox in <P> I believe that some individuals add the
TREG discrete trip inputs to an L4T rung so that there is more "visibility" if one of them should actually trip the
turbine.
I also believe that there are timed over-rides for some of these TREG discrete trip inputs because they might not be
closed when a START is initiated and so a time delay is required to allow the signal to close and a START to progress.
I have done this test many years ago (perhaps philosophy or firmware has changed--but I tend to think not): I would
jumper all of the TREG discrete trip inputs which were enabled on a particular Mark VI (usually one of the "skeleton"
Mark VI SIMPLEX panels) and then force L4_XTP to a logic "0" to pick up the ETR relays. I would also force
L20FG1X, for example, to pick up the PTRs to energize 20FG-1. Then I would open each of the TREG discrete input
circuits one at a time and observe that the ETRs would drop out and 20FG-1 would drop out--and I did not observe
that the PTRs would drop out (because these TREG discrete inputs were NOT used in any L4T rung). This would
prove (to me) that any of the seven TREG discrete trip inputs would indeed deactuate the ETR relays, resulting in a de-
energization of the fuel trip solenoid.
Again, there is no "visible" application code in <P> to observe how this works; it's just coded in firmware. I believe in
an older version of the Mark VI System Guide it was documented in the firmware description of the VPRO/TREG
cards, but I don't have access to that as this writing.
I don't believe it's necessary to use any of the TREG discrete trip inputs in any L4T rung to actually trip the turbine--I
think it was done by some individuals because they thought it should be done. I believe that if any of the seven TREG
discrete trip inputs open when the turbine is running that it will drop out the ETR relays before the change of state is
transmitted to <Q> and processed by the application code to de-energize the PTR for the fuel trip solenoid. So, it just
seems redundant (not necessarily wrong, but not necessary) to use the TREG discrete trip inputs in any application
code L4T rung.
That's about the best explanation I can provide at this time.
3) As we discovered during the L4 journey, yes; the inputs must be closed during normal operation and when they
open the turbine will be tripped. I don't recall the signal names but a couple of them were "inverted" (the signal name
was a logic "1" when the unit was to be running, and a logic "0" when the unit was to be tripped--which is opposite of
GE-design heavy duty gas turbine control philosophy). I think it was L86TGT1 or something like that in the L4 rung.
And didn't we discover that one of them was "inverted" in application code??? Kind of ... unnecessary.
Again, we are dealing with engineering performed by the GE Belfort bunch, and they are pretty lax with standards
enforcement, just doing what they think should be done on your application--so some of this is just to be expected.
Finally--it was my understanding that the TREG discrete trip inputs were NOT to be used on TMR applications,
because of the nature of TMR controls. So, in my personal opinion using any TREG discrete trip input on a TMR
application is in unnecessary, and if one does use one or more then the signal names should match
Hope this helps!