You're getting confused with the NGX. Also the 737 cabin altitude warning can be reset, unlike the takeoff config warning.

Ah, my mistake. I thought the thread was about the NGX. And yes, it can via the altitude horn cutout button on the overhead panel.Regards

 

The TOCW horn is one and the same as the cabin pressure warning. Yes, it does go off below 12,000ft. 10,000 to be exact!! If it goes off on the ground it's take off configuration. In the air at or above 10,000ft it's cabin pressure.

You got me there! was working off hazy memory on that one. The masks auto deploy at 14,000 in the real bird and am not sure where the 12,000 came from. At any rate the original thread is about an issue with the T7 and I thought it was about the NGX, again, oops. Regards

 

 

Ah, my mistake. I thought the thread was about the NGX. And yes, it can via the altitude horn cutout button on the overhead panel.Regards

No worries. I've done exactly the same myself before now.

 

 

No worries. I've done exactly the same myself before now.

So did I in the first moment... I was wondering if the OP accidentally posted an NGX behaviour in the 777X forum.

No "EICAS message" and no warning lights but (config) warning sound would speak for that.

Will be interesting to hear about the outcome...

It has to be the out of trim warning. On a second leg of a flight I have had this warning even when the trim was set, I had to trim up a bit then back down to the assigned setting. It was a light airplane so trim was 3.75 or so

It has to be the out of trim warning. On a second leg of a flight I have had this warning even when the trim was set, I had to trim up a bit then back down to the assigned setting. It was a light airplane so trim was 3.75 or so

That occurs on ground, not in flight. Anyway the OP has already identified its related to the autopilot.

It has to be the out of trim warning.

But IIRC the T7 T/O config trim warning gives: alert sound + EICAS red message "CONFIG STABILIZER"+ red light "WARNING" (glare shield) if trim is set at a value out of the (variable) greenband range. So it is quite "distinguishable"... :huh:

 

 

 

Do you engage the AP prior to takeoff?

 

That also confused me.  Probably the OP is mixing up A/P and A/T.

A bit mysterious but I think the answer to this will be very easy in the end... B)

That also confused me. Probably the OP is mixing up A/P and A/T.

A bit mysterious but I think the answer to this will be very easy in the end... B)

Illogical Captain. The A/T does not cause a warning like this, the AP does. Also the warning was cancelled by the AP disconnect switch, therefore it was the AP warning.

 

The OP hasn't been back recently. Maybe the problem is solved and we'll never know what happened to cause it. It's possible the AP never was engaged but the aural alert became latched on due to a software glitch (a bad FSX load for example). Or maybe it was engaged inadvertently before takeoff.

Also the warning was cancelled by the AP disconnect switch, therefore it was the AP warning.

 

As long as the op clicked twice  depending on how he has set up his fmc on this part

I was engaging the AP prior to takeoff, just as I did with the 737 NGX.  When I stopped doing that, I no longer get the warning light or horn.

You don't engage the AP on the ground in the NGX either

You don't engage the AP on the ground, period! Only during pre-flight test.

 

 

I was engaging the AP prior to takeoff, just as I did with the 737 NGX. When I stopped doing that, I no longer get the warning light or horn.

Thanks for clearing that up! B)

As long as the op clicked twice depending on how he has set up his fmc on this part

The two presses are first to disengage the A/P and second to cancel the disengage warning. If the A/P disengages for some other reason (as here due to the control inputs during takeoff) only one press is required to cancel the warning.

Presuming we are talking about the Red Warning light in the Master Warning/Caution button directly in front on the glareshield ... There really isn't much in a 777 that generates a warning/caution light and/or sound (buzzer, horn, bell, etc) without an EICAS message.

 

Therefore I'm wondering if it's a coding problem? My suggestion would be pausing the simulation just after takeoff and having a really good look around the panel for a secondary indication. Especially the overhead panel and the Flap/Gear/Terrain indicators.

 

I made this diagram up a while ago for a training presentation, it gives you an idea of what starts and stops when on a takeoff in respect of the inhibits.

 

http://www.infinidim.org/?p=2994

No, it wasn't tail strikes.  I had been activating my A/P before taking off.  That was the cause of the warnings.