Quote:
This is a bit of a personal choice. I use the TOGA buttons on the Throttles, then after having raised the landing gear, I turn the Autopilot ON, and then, depending on the SID, I will engage LNAV (or HDG SEL if VECTORS is listed as the next waypoint) and VNAV.

Quote:
On the CDU, open the RAD/NAV Page. In the scratchpad, enter the Frequency/Heading of the ILS in this format -> XXX.XX/XXX (111.10/335), then press LSK4L. IF the frequency/heading is already there, press LSK4L TWICE! The first press copies it to the scratchpad, the second press pastes it back. There will be an M after it, which tells you that it has been done manually, so make sure it is the correct FREQ/HDG.

My test flight I just completed worked fine. 

The only issue I had was the autoland was a bit firm.  Is there anything else that needs to be set for autoland?   It did go to idle thrust and did a small flare, but the AP stayed on after touchdown.

Should that have disengaged automatically, or do I need to do that manually after touchdown?

This is remarkable plane, it is going to take some time to get everything as smooth as I want it.

Thanks Mark.

I see that speed is everything with landing this baby.  A few knots too many on a manual landing and you're halfway down the runway at touchdown!

I flew this plane most of the day yesterday.  It is great when ity all goes smoothly, but I have some weird things that happen. 

According to Jon M's tutorial, when I put 250 into the speed window on the MCP,  the VNAV logic in the CDU is supposed to honor that restriction until I get to 10000feet.  On my first few flights, this seemed to work, but the last few, it can't seem to manage it.  More like 270.  Maybe it is running out of elevator authority.

The CDU also changes all my speeds in the Legs page to 315 after takeoff.  I was flying from Chicago to St Louis at fl280, and several of the legs were displayed as ".80/280" in the Legs page after CDU programming was complete.   But they all changed speed to 315 by themselves.   So then when I get to altitude, I have to do your left-click on the speed knob trick to get a cruise speed of .80.

Also, somehow now my marker beacon audio is sounding on takeoff.  Where are the controls for the audio for marker beacons? 

If I want to do FLCH mode to climb instead of VNAV, will the thrust settings for climb still change from Takeoff to Climb automatically?  Or do I have to do that manually?

Thanks again for all your help, Mark.   These CS planes are great (I have 727,737, and now this 777) but there is no way I could have got them working without you and the other great people on these forums who spend a lot of time helping us to get the most out of them. 

I see that speed is everything with landing this baby.  A few knots too many on a manual landing and you're halfway down the runway at touchdown!
I look at it this way. When looking at the 777 from the left or right side in Locked Spot view, make sure that the nose wheel is above the main landing gear (nose up attitude). That way the landing will be softer. as I said before, it does flare, but it is not very much. Sometimes, it doesn't flare at all! And the landing is going to be pretty heavy. This might be what you are seeing.

I flew this plane most of the day yesterday.  It is great when ity all goes smoothly, but I have some weird things that happen.
Mine flies very well most of the time - about 90% or better.

According to Jon M's tutorial, when I put 250 into the speed window on the MCP,  the VNAV logic in the CDU is supposed to honor that restriction until I get to 10000feet.  On my first few flights, this seemed to work, but the last few, it can't seem to manage it.  More like 270.  Maybe it is running out of elevator authority.
The VNAV should honour the speed you enter in the Speed Indicator. I assume that you are clicking in the centre of the IAS/MACH Selector so that VNAV is still active, but you are controlling the speed.

The CDU also changes all my speeds in the Legs page to 315 after takeoff.  I was flying from Chicago to St Louis at fl280, and several of the legs were displayed as ".80/280" in the Legs page after CDU programming was complete.   But they all changed speed to 315 by themselves.   So then when I get to altitude, I have to do your left-click on the speed knob trick to get a cruise speed of .80.
Strange. I haven't seen that myself. I can't think why it would change them. Next time that happens, check the VNAV CRZ page (page 2/3), and see what is entered in there for the speed. If it show 315, change it to 280 and the wspeed on the waypoints should change to match it.

Also, somehow now my marker beacon audio is sounding on takeoff.  Where are the controls for the audio for marker beacons?  
I can only assume that you are overflying some marker beacons after taking off, so they are triggering the sound. I have had this happen in other aircraft before (which possibly includes the Cs7770, I just ignore it.

If I want to do FLCH mode to climb instead of VNAV, will the thrust settings for climb still change from Takeoff to Climb automatically?  Or do I have to do that manually?
As far as I know, it will change on it's own. I rarely use FLCH, mostly VNAV, but that because it works fine for me almost all the time, as I said above. I gave the 777 a good run of tests out of Heathrow (EGLL) where a lot of time is spent holding altitude due to Altitude Constraints in the SID's (i.e. 6000 feet in the SID DVR6K), and even though I had entered the Cruise Altitude in the Altitude Indicator, it stopped at, and held, 6000 feet until it passed the waypoint that allowed it to continue the climb. So VNAV is working really well for me.

Ugh.  There must be something I'm missing that is making this 250 k speed restriction not work.  

I am using the TOGA switches on the throttle to get going.  I have the speed window set up to 250.  I have the AT armed.  I have the ALT set to fl 280.  Heading window has the heading dialed up.  F/D is on, with only VNAV activated.  

TOGA, rotate at VR, gear up at positive climb rate. Hold speed to about 180 k with pitch manually.  Engage AP,  retract flaps, watch plane accelerate to about 270k at VS of over 5000ftm.  Even after climb mode activates, "TOGA" is still on the screen above the main flight instruments.  

What is truly messed up is that even after 10,000 feet, where the restriction should go away, the speed stays at 270 at 4000+ fpm climb.  Why would it do that?  It ought to lower the nose and accelerate to the 315 that is in the Legs page at 10,000, yes????


Is there something I am supposed to do to tell the thing we are not taking off anymore and that it should be thinking climb speeds?

EDIT ######I might have got it#############

Instead of using the throttle TOAG button, I used the continuous thust button on the glareshield right below the AT arm switches.  This time it did what I wanted it to do.  

I also changes my cost factor to 500 from 100, and it seems to have stopped altering my legs page after takeoff.

What does everyone else use for cost factor?


****EDIT #2 ******************!!!!!
It only switches from TOGA mode to VNAV Speed hold mode if LNAV is also selected!! 

AHA!!  I knew I was missing something.  If I only have VNAV selected, it never gets out of TOGA mode. 

That's a major bug, I think.   You shoukd be able to use heading mode to hold the runway heading until ATC turns you.  But if you use heading mode for lateral guidance and have VNAV selected for vertical guidance, it fails to follow the 250 k speed restriction.  As soon as I hit LNAV, the VNAV starts working properly!