Something I've been struggling with since I installed the T7 is that my Engine #1 does not complete it's stabilization during the startup procedure.   At first I thought it was the throttle settings withing FSUIPC, so I followed everyone's recommendations to bypass FSUPIC and let FSX manage the throttle.   I did that.  No change.

 

THEN... I was watching FROOGLE PETE's video "PMDG 777 - FULLY LOADED, KJFK to KDEN Part 1".    Lo and behold... I see that his Engine 1 gets stuck temporarily in the exact same spot as mine... he even makes a comment about it when it finally "jumps" to its completed state of stabilization.

 

See his video at exactly 28:13 when it jumps.    The issue for me is... mine NEVER jumps to where it needs to be (EVER!).    And... when I move the throttle all the cockpit controls move (throttles, center display shows power being requested) but Engine one provides no thrust.  Engine 2 is fine.

 

This link will take you to exactly 28-minutes where Froogle has already initiated Engine 1 start and he is waiting for this stabilization.

 

http://www.youtube.com/watch?v=fMrW4O4WXYY&t=28m0s

 

Why is mine NOT completing ?   It is stuck at 21.8 N1 and 391 EGT.

 

Any help would be immensely appreciated.

Ok,

 

I dont know who this Froogle guy is, but forget about him.

(ok that is a bit harsh,...eehm...lets just say I see how can he be a big help....but not everything he does is by the book...ok)

 

For one, he is starting the engines without even looking at the secondary engine page!

How are you supposed to recognize what is wrong during an engine start if you dont look at ALL you engine parameters???

 

One of the things you have to MANUALLY abort an engine start for is lack of oil pressure rise.

This is one of the few things not monitored by the Eng Autostart system....so if you dont monitor it either....nobody is!

 

Without oil press you can ruin that exspensive engine quickly!

 

 

Also his engine is stabilized at 27:55.

(he just does not know it)

The starter has cut out and EGT has dropped at that time.

It makes sence for him to wait for that jump so that both engine EGT match but the fact is...that is not normal.

(also in real life with differently aged (and even configured sometimes) Engines indication can differ quite a bit between left and right)

 

That sudden rapid EGT increase at 28:13 is a sim error (snag).

The real airplane does not do that and it is not the indication of the engine being stabilized.

(so you are in fact waiting for a sim snag to happen!)

 

My engines start as they are supposed to, without the sudden jump!

 

 

 

Now, lets start to make sure you are doing everything right.

 

Make sure the Autostart feature is on (switch on overhead panel).

APU running!

Engine starter switch - on

Fuel Control Switch - Run (right away, no need to wait for anything as autostart takes care of correct sequencing of fuel/ignition/etc)

 

 

First N2 should start rotating

then N1 should follow

oil press is normally already rising now

Then around 33% N2 fuel flow (FF)should show (0.5 - 0.9)

Next is EGT rise.

(this is where you Check oil press increasing, but for this excersise it doesnt matter as we just want the engine to start.)

 

So:

N2

N1

FF

EGT

 

then keep going back and forth between N1 and N2 and EGT (N1, N2, EGT...N1,N2,EGT....N1,N2,EGT...etc) to see if RPMs keep increasing but not redline and that EGT goes up (but not redline) and then drops again.

 

My EGT (I just tried at Vienna with TAT17) rises up to 555C and then after starter cutout drops to 455C.

Done, finished!

The engine is stablisized when EGT has dropped.

 

If you keep monitoring the EGT then you will see it slowly rising (as I am typing this mine has increased to 464C) but no sudden jump should occur.

And if it does then that is a sim snag, or freeze, or stutter, or whatever.

 

 

Let me know how you get on now.

Thanks for help. Now the engine's running very good, but sometimes I had problem with it. And again very thanks.

Do you have PACKs on? I normally leave PACKs off for startup, try doing that and see if it helps.

Do you have PACKs on? I normally leave PACKs off for startup, try doing that and see if it helps.

Not that is matters much in a simulation, butwhy do you leave packs off?

 

The normal is procedure is for everything to be On/Auto on the overhead....thats what makes the 777 so nice and easy.

 

 

The normal is procedure is for everything to be On/Auto on the overhead....thats what makes the 777 so nice and easy.

 

More buttons to pushy-push after start up. Gets a bit too boring otherwise

haha, ok :-)

I have seen this "jump" too and I've done a video to illustrate:
APU on, hydraulics on, packs auto, all correclty configured for an engine start.

Watch in HD please.

 

http://youtu.be/kLRdNMfoWsA

 

Don't know if it's a bug or normal, but it is there.  :Thinking:

It happens with any engine start sequence, on both engines, packs auto or off.

I have seen this "jump" too and I've done a video to illustrate:

APU on, hydraulics on, packs auto, all correclty configured for an engine start.

Watch in HD please.

 

 

 

Don't know if it's a bug or normal, but it is there.  :Thinking:

It happens with any engine start sequence, on both engines, packs auto or off.

Yes, I see.

 

But what I also see is that your FF is not at idle FF.

At idle you should have max 0.9 and you have 2.2!

 

Either close you thrust lever all the way, or press F1 or recalibrate.

 

I dont know if that is what screwing things up, but it could be!

Yes, I see.

 

But what I also see is that your FF is not at idle FF.

At idle you should have max 0.9 and you have 2.2!

 

Either close you thrust lever all the way, or press F1 or recalibrate.

 

I dont know if that is what screwing things up, but it could be!

Thanks for point this out but I've tested with no hardware connected, no FSUIPC, only keyboard and FS default assignments, with the same result. It's a minor thing I can live with, but just to join the OP cause.  :lol:

Regarding fuel flow, I agree but AFAIK it's an FS limitation. I could be wrong though.

 

Edit: Fuel flow, it's in Pounds. 1000kgs = 2204lbs

So I think it's correct.

Hi All,

 

This engine start behaviour was reported a couple of months ago in this forum by me and some other simmers just after the relesae of the PMDG T7.At that time beeing a small thing it went unnoticed by the devs.

My starts on both engines are exactly the same.  In reality such an EGT jump is simply not possible.

 

Cheers,

Onduty, do you have a hardware throttle? 

Maybe we can narrow this down to users who don't have hardware throttles, because I haven't seen this reported elsewhere yet. 

Sidenote: Onduty, you gotta sign your names on the forums buddy, the mods will delete your post otherwise.

Thanks for point this out but I've tested with no hardware connected, no FSUIPC, only keyboard and FS default assignments, with the same result. It's a minor thing I can live with, but just to join the OP cause.  :lol:

Regarding fuel flow, I agree but AFAIK it's an FS limitation. I could be wrong though.

 

Edit: Fuel flow, it's in Pounds. 1000kgs = 2204lbs

So I think it's correct.

Ah ok....didnt realizes that. Makes sence.

 

Well then I dont know what's up with that jump.

 

Try changing to KG....who knows!

Packs in 777 are switched off automatically during engine start, then back on shortly after engine start is completed.

 

Mike

I can confirm that i too have been experiencing this since release