Sign in to follow this  
psolk

Mid-Flight First impressions

Recommended Posts

First off,Congratulations on the code release and thank you for all the effort.Here are my first impressions as I take her from KEWR-EGCC. 1. FDE- HUGE improvement, wow!!! It really is like a diferent a/c and truly has that heavy feel to her. Taxi, Takeoff and climb felt like I was flying something BIG. Acceleration and takeoff showed no signs of pushing/pulling off runway. Straight down the centerline2. FMC ETA is fixed Step-climb also appears fixed Nav/Rad shows correct runway. Init/Ref switches to correct arrival runway and parks after departureDid a hold shortly after departure with no issues3. LNAV/VNAV seems much more stable, no more rapid changes4. TCAS Ghost issues resolved in offline mode5. Did we get new sounds? She sounds throatier.. Could just be me6. Hitting flaps up and then flaps 5 again no longer cancels VNAV information7. Changes to FMC do not cancel VNAV information8. Stats still dissapear when you hit EXEC in FMC.9. modelling issues were not resolved (who cares, she flies :) )10. Overall I am pleased thus far. That is all I can think of off the top of my head and I am sure I will have more to report after descent approach and touchdown. Thanks again to the team,-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

OK, I need to change # 7. I just had a step from 35 to 390 ordered by the FMC. Dialed 390 on the MCP and pressed it and sure enough VNAV disconnected and Econ speed is now blank. I am now going to have to go in and move the CF06L waypoint up in the FMC deleting other waypoints in order to get it back.So # 7 does not appear to be fixed at all, at least for me,-PaulEDIT: OK this is really weird, I was able to get it back without changing my legs at all. It looks like the FMC is ordering a step the plane can not handle. MCP speed is .830 and when I execute to 390 as ordered by the FMC I lose my VNAV and Econ SPD. If I dial the MCP back down to 350 and select it again, VNAV comes back and econ speed us repopulated in magenta. I just tried a step to 370 instead and VNAV held fine.So it almost looks like the FMC is commanding a step to 390 but then telling me it can't do it when I execute it and disengaging VNAV and losing its econ spd settings in the process...Any ideas, is this a r/w idiosynchrocy (spelling) or a PSS issue?Thanks in advance.-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

I had this problem as well. I had to climb manually to get VNAV to take over again. I was trying to get to 370 from 350. FMC CRZ page said optimum was FL387.

Share this post


Link to post
Share on other sites

Hey Bob, I edited my post, check it out. I figured out how to re-engage VNAV when this happens,The beauty of being on a 6 hour hop from KEWR-EGCC :) Lots of time to experiment,-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

It's good that you can recover. I think you should get a 'UNABLE CRZ ALT' (or something like that) message if the FMC can't go to the requested altitude.

Share this post


Link to post
Share on other sites

I was able to step to 370 so it was almost like the FMC was telling me it was ok to do a 2k foot step even though it was set for ICAO and displaying a 4k foot climb. Weird... Agreed on the unable crz alt, I don't think this should be happening.-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

Woo-Hoo, welcome to Manchester Ladies and Gentleman we hoped you enjoyed your flight. Other than the VNAV issue mid-flight everything else was perfect. I did find a workaround above as well.TBH, I don't think any other plane does a better job of correcting pilot error on overshoot than the PSS T7. I have noticed a number of times on short approaches where I have overshot the intercept flying in hdg mode prior to LOC capture. PSS will lock on prior to overshootting, follow the overshoot and then bring itself back and correct perfectly. For me anyway in a lot of other a/c if you overshoot you are done and they are not going to come back and catch on their own without help...Also, you can load up another flight plan after arriving just fine, Just change the DEP airport or select a new FP. The boxes do not clear automatically but you can still load another FP just fine. Only issue the the Autopilot Disconnect message but I saw Normans response on that earlier and hopefully someone can come up with a workaround.So my only complaint thus far was the VNAV issue mentioned above, hopefully someone from PSS can comment on that otherwise like I said, simply peachy :)See you back in KEWR,Thanks again, look forward to your feedback,-Paul

Share this post


Link to post
Share on other sites

This seems to be the proper thread to add positive experiences with the T7 v1.1 patch. I have to add my two thumbs up on the update. I agree the FDE's improvements are amazing. The CDU is now working 100% for me. I never had any problems beyond the above mentioned. In my book this software is now complete and very enjoyable. Thanks PSS! I know it's been tense for a while but you have delivered. Congrats!Whadzen

Share this post


Link to post
Share on other sites

>Thanks PSS! I know it's>been tense for a while but you have delivered. Congrats!Thank you kindly Sir!

Share this post


Link to post
Share on other sites

What abou the VNAV/Step Climb issue mentioned above Norman, any comment? Congrats again,-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

Hello Paul,Whilst Norman and I have not seen this "issue", I have sent a request to the beta team to see if we can reproduce it, in an attempt to find a fix.regards,

Share this post


Link to post
Share on other sites

Thanks Steven, I think the bigger thing here is that if others do not realize the fix for this people are going to think the CDU is broken... For me I am good now that I know how to work around it.Maybe a sticky with V1.1 known issues and workarounds...1. VNAV disconnects when Step Climb is initiated. Fix: Re-enter the same value for crz alt you are already at. If your step was 4000 ft. Try a step of 2000ft instead. The step will then recalculate and VNAV will re-engage.2. A/P is not "fully" disconnected upon touchdownFix: Ensure "Z" key has not been pressed engaging default A/P3. Avionics issues/weird electronic behaviorFix: Ensure your default flight is default Cessna, Engines running, electronics on. Tip. You do not have to actually load this flight. The parameters are read from the create a flight screen. You can still just select the T7 and departure airport without LOADING the Cessna first. It just has to be saved as your default flight.4. Holes in VC texturesFix: Don't look thereand so on and so on...-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

>4. Holes in VC textures>Fix: Don't look therePaul,Thanks for putting one HUGE smile on my face! :D

Share this post


Link to post
Share on other sites

Paul,A question:Maybe I didn't see this in the posts; I've read through it and haven't seen this, but then again, I am medicated :-laugh1 :On the progress page, what were the values for min opt and max alt?If the max alt was less than 390 (say 387), then VNAV will not command the climb. This is one possible explanation for why it would step only to 370. I know this sounds like a really dumb question, but I didn't see it. I probably missed this, but if you could restate that or refer me back to the post #, I'd appreciate that. I'll fly a test trip tomorrow when my head is clear...had the C scope thing today...a snakey experience.Thanks for understanding my plight...Dave Lambbaw716

Share this post


Link to post
Share on other sites

Dave, welcome to the medication club first of all. It is Vicodin for me, recovering from spinal surgery. C-scope, I assume you are reffering to a camera where the sun don't shine? I just had one done to look for internal bleeding from top and bottom. Not fun, I wish you the best.Now for your questionI had step to 390 NOW in the CDUOPT Alt was only 376 and Max was 404It looks like the CDU logic was to not command 370 because I was already beyond that for an OPT ALT but would not climb to 390 because OPT wasn't there yet.Feel better,-PaulEDIT: Just confirmed it. Initial crz alt was 340. Step size was set to ICAO. As soon as Opt Alt hit 361 CDU commanded step to 380. Max Alt was 397 and again VNAV disconnected when I tried to initiate the climb. Entered 360 on the MCP and initiated that instead and all was happy again.Liquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

PaulCan you do a quick experiment and change ICAO to 2000, see if that makes a difference.Adam

Share this post


Link to post
Share on other sites

>Dave, welcome to the medication club first of all. It is>Vicodin for me, recovering from spinal surgery. C-scope, I>assume you are reffering to a camera where the sun don't>shine? I just had one done to look for internal bleeding from>top and bottom. Not fun, I wish you the best.--------------------------------------------------Thanks Paul and confirm your point for same reason. Outcome good. BTW, I have five blown discs (four in the C spine, one at L5/S1).Rx of choice Avinza (long acting MS) great stuff...long acting and no fog unlike the regular stuff. OK..now to the issue at hand: I think you hit the issue on the head. I was reading the 777 manual (the real one) under "climb constraints", and the books says the following:"Step ClimbFuel and ETA predictions assume the airplane climbs at each predicted step climb point as airplane weight decreases. FMC predicted step climb increments are based on the step size shown on the CRZ page. If a step size of zero is entered, the FMC assumes a constant altitude cruise. Flight crew entry of a planned step altitude on the CRZ or RTE LEGS page overrides the FMC step climb predictions before that point. Entry of a planned step altitude on the RTE LEGS pages overrides a "step to" entry made on the CRZ page.Predicted step altitudes are shown on the RTE LEGS page. The distance and ETA to the next step point (predicted or flight crew entered) are shown on the CRZ and PROGRESS pages. They are also shown on the ND map display with a green circle and S/C label".Of course, this explanation is clear as mud. :-rollerFrom what I gleen from your post below, you were making your altitude changes in the MCP based on the predicted OPT ALT. So, if I interpret the above correctly, if you were making a change in altitude based on the CRZ page, and the RTE LEGS page had a different altitude set for that waypoint leg, the RTE LEGS page would take priority over anything you change using the CRZ page.So my question is this: In your example, your step size was ICAO. As soon as OPT ALT 361 CDU commanded step to FL380, you initiated the climb, but the VNAV wouldn't accept it. What was the RTE LEGS alt at that position? If it was, say FL360, if I read the manual correctly, VNAV would not have commanded the climb to FL380. To do that you would have to use FLCH or IAS/MACH + VS.If your RTE LEGS altitude was FL380 at the point you initiated the climb, then there might be an argument for the possibility of a fault in the programming of the ICAO step climb profile on the CRZ page.Does this make any sense?It sounds like the proper procedure to change altitude when the RTE LEGS page is different than the OPT CRZ altitude is to change the altitude on the RTE LEGS page, then change it on the MCP, then hit VNAV. If you can confirm that information for me, then I think I will have this straight in my head...I think this is a procedural thing with the FMS (I am not a pilot, I would have to consult my brother in law who is a 747-400 F/O with about 10000PIC hours...he can give me the straight skinny...he knows both the PEGASUS and SMITH CDUs sideways). I admit to having a reasonable handle on the glass, but I am not an expert. I have the FMC Guide for the 777 as well as two 777 Operating Manuals and CBT training CDs...I suppose I could find the lesson for operating it and go through it myself to be sure.It doesn't sound to me to be a PSS FMS fault...Do you concur?ThanksDave LambB767 Captain British Airways Virtualbaw716------------------------------------------------------>Now for your question>I had step to 390 NOW in the CDU>OPT Alt was only 376 and Max was 404>It looks like the CDU logic was to not command 370 because I>was already beyond that for an OPT ALT but would not climb to>390 because OPT wasn't there yet.>Feel better,>-Paul>>EDIT: Just confirmed it. Initial crz alt was 340. Step size>was set to ICAO. As soon as Opt Alt hit 361 CDU commanded>step to 380. Max Alt was 397 and again VNAV disconnected when>I tried to initiate the climb. Entered 360 on the MCP and>initiated that instead and all was happy again.>>Liquid Cooled>AMD 4000 San Diego>2 Gigs Kingston Corsair XMS CL2>Dual 7800 GTX >24 inch widescreen dual 19 inch LCD>Raid-0>psolksig.jpg

Share this post


Link to post
Share on other sites

Just a little issue...ICAO doesn not allow for the use of even FL's above FL300, regardless of what OPT/MAX indicate.There seems to be a bigger issue at play here, but, that would be something to start with.

Share this post


Link to post
Share on other sites

>Just a little issue...>>ICAO doesn not allow for the use of even FL's above FL300,>regardless of what OPT/MAX indicate.>>There seems to be a bigger issue at play here, but, that would>be something to start with.Ah, the game's afoot:I am looking at Bill Bulfer's FMC Guide for Big Boeings (incl PEGASUS on 777). STEP SIZE ICAO default value is 2000ft increments below FL290 and 4000ft increments above. A different STEP SIZE is allowed by entering the STEP SIZE in feet from 0 to 9000 in 1000ft increments. If NO step climbs will be made, it is "important" to enter zero so that the performance calculations will compute accurate fuel predictions.So, Brian, your statement above regarding STEP SIZE does not appear to be entirely correct. You can enter an even number flight level as your planned altitude based on the predictions on the PERF INIT page; however, the STEP SIZE at ICAO only references the increments of climb above FL290, not that you can't fly it. The default is ICAO; however, the value can be changed based on the particular conditions.What we need to try is flying with an even flight level as the programmed final altitude and program the STEP SIZE on the PERF INIT page with a) ICAO and see if the legs pages reflect the appropriate step sizes at the optimum points and :( with a value < or > an ICAO value, say 2000ft increments above FL300 and see if the FMS will recalculate the step climb profile accordingly.The question really comes down to a) if this particular aspect of the FMC is modelled in the 777 and :( if it is, what values other than the default ICAO can be entered either on the PERF INIT page or the CRZ page. We should test this to see if the step values can be manipulated in this form.Just as an aside, there is the zero step climb technique to consider. If no step climbs will be made, zero must be entered as stated above. This will blank TO STEP CLIMB header and field at 1R of CRZ and 4R of PROG 1/2. The step size zero technique eliminates all down path step climbs. Otherwise, performance calculations will assume the computed optimum steps will be made, possibly resulting in non-conservative predictions of fuel at destination. In cases where substantial headwinds exist at higher altitudes, FMC can show a savings by staying at a lower altitude.For example, you are planning a flight EWR-SFO and there are substantial headwinds at most levels along the most direct route (say FL340 and higher). If you don't enter ZERO in the STEP SIZE, the FMC will calculate fuel burn based on the "optimum altitude", which, if the proper average wind component for the route is not entered correctly can produce an incorrect fuel burn prediction. This is the purpose of the ability to override the ICAO in the STEP SIZE line of the PERF INIT page. You can change different values to achieve different fuel predictions based on various altitudes and wind conditions. In the case above, it might be more fuel efficient to do a straight climb to FL320 and stay there (on medium haul flights this is possible); in which case the STEP SIZE needs to be set to zero so it will calculate the correct fuel burn based on the altitude and winds you enter into the FMC. Note: Any entry made in STEP SIZE before the flight on the PERF INIT page propogates to the CRZ page.IMPORTANT NOTE: If you elect to change STEP SIZE during the flight, it can be done only on the CRZ page and not the PERF INIT page. Reference: Page 80 of FMC Guide for Big Boeings.Suggestion to pilots: Attempt to manipulate the STEP SIZE in the preflight setup and see what changes result on the LEGS pages and the CRZ page. You may find that you have different values for MIN/OPT/MAX altitudes predicated on a manual override of the default ICAO setting on the PERF INIT page.To PSS: Were these particular aspects of the FMC modeled in this release of the 777? Just curious, because if not, it might explain why some people are having some of these step climb issues. If not modelled, this would be an excellent add on, since it would give the ability to actually manipulate the fuel calculation on the ground based on the parameters fed into the FMC (especially winds and step climb variations) as well as provide improved fuel economy values for MIN/OPT/MAX altitudes under specific wind conditions.Also, side question for PSS, were pilot defined waypoints (pilot constructed) modeled in the FMC? Specifically:-Place-Bearing-Distance-Place-Bearing/Place-Bearing-Along Track Waypoint-Interval Lat or Long-Airway intersectionIf not, could you indicate which ones were not, so that we can build a work around for some of these pilot defined waypoints other than specific lat/log positions? If this information is in the user manual, then so indicate and I can look up the information and do the tests to see what can be manipulated, then I can report it back on the forum. In addition, if these are not included, these would be terrific improvements to have in the FMC and programming should not be terribly difficult (again ref. FMC Guide page 19-22).Final question-Conditional waypoints (waypoints not created by pilots) such as in SIDS/STARS...I presume these can be modeled based on how the specific SID/STAR is built and then loaded into the SID/STAR file. If this is not the case, can you also please advise and then possibly consider for future release?Many thanks,Dave LambCaptain, British Airways VirtualSenior Captain, United Airlines Virtual Cat IV

Share this post


Link to post
Share on other sites

WOW,Dave,First off, glad to hear everything went well. I had 11 hours of surgery in September from the stomach and the back to have a titanium cage put in my back. I feel your pain. Agai, glad it worked out for you.I can not even begin to thank you. I was hoping for exactly this, people with more knowledge to come along and clear this up (or confuse me even more, I am not sure yet)If you look at my first post I actually asked if this was a PSS thing or a real world idiosynchracy. It is amazing how much we assume is a bug when in reality it works the same way on the real thing and not being a r/w pilot we have no clue. Based on your first post, If I command a step to 390 but my legs page still says 370 then I will only be able to climb under VNAV to 370 despite my PROG page saying CLIMB NOW.That makes a great deal of sense but the question would be does the r/w counterpart behave the same way as the sim or does it generate an unable crz alt message. Again, all I can do is assume but I would be very surprised if the r/w units just dropped the VNAV command altogether. You never know though..Similarly, I will try another long haul this afternoon. I took a long weekend in order to have ample testing time for my new T7 :)This time I will set the step to 2000 instead of ICAO and see how it handles it. Again, thank you so much for all of this information, I am doing my best to suck it up. Knowing the workaround to re-engage VNAV makes this more of an annoyance than an issue and if it proves to be r/w behaviour then kudos to PSS...Thanks again Dave, trying 2k feet step today Andy,-Paul Liquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

Just an FYI, all pilots I have spoken to say that during step climbs they do not use VNAV because it gives you the max allowable engine thrust, which is not comfortable for the pax. They just use a v/s of about 500ft/min.

Share this post


Link to post
Share on other sites

-Davidoff, you are 100% correct. If you watch the ITVV videos, they specifically mention that. The issue though is whether or not you will be able to re-engage VNAV at the Alt you climb to. If your initial CRZ AlT was 350 and step is set to ICAO then when the CDU says STEP NOW on the PROG page, if you go to VNAV it says step to 390. In reality your OPT ALT is 371 but because Step is ICAO and your OPT ALT is above 370 CDU tells you to step to 390. Because 390 is higher than the value in the legs page, VNAV will not accept it, you lose VNAV altogether, your econ spd on the PROG page and you have to fly the rest of the route via the MCP minus VNAV.So the question is not whether or not to use it for the climb but if VNAV is operating correctly and will be able to re-engage once the climb is complete.It does look like there (might) be an issue with the logic of the PSS CDU but we do have a workaround and some of those with a lot more knowledge than myself are researching this a bit as well.Thanks Davidoff, good point,-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

Just sterted my first flight witn V1.1 and inadvertantly selected Flap 1 at 5000 ft - well into a VNAV climb. On my system "Act Econ Climb" changed to "Act Econ Desc" and the aircraft entered a gradual descent at 1500 fpm - MDC alt was still set at 36000, the FD indicated a climb and LNAV continued as normal. Although I could continue the climb using VSFPA, I found that I could do nothing to restore the VNAV climb - I tried disconnecting and reconnecting the AP, changing the cruise level etc etc.I then saw your item #6 above and had a look at the take off and initial climb. I found that, if I selected flap up and then back to 5 at the time I changed from 15 flap to 5 flap - during the "Act Lim Spd Clb" phase, the VNAV profile remained ok; but if I did the same slightly later between the 5 and 1 flap speeds - during the "Act 250kt Clb" phase, VNAV changed to "Act Lim Spd Des" and the aircraft changed to the same 1500 fpm descent. Again, no way, I could revert to VNAV climb.To date I have not found out how to clear the FMC when an error like this occurs - very grateful if anyone has any ideas.John RooumBTW re your #8 - I have seen several in flight cockpit photos and this appears to be SOP once a route is "executed" in the CDU.

Share this post


Link to post
Share on other sites

Hi John,I am enroute from KEWR-LLBG right now. ~10 hours to go LOL but I will try to replicate what you are saying ASAP. It might be tomorrow morning. Then Iwill figure out if we can get a workaround. Hopefully someone from the PSS team can look at it as well.As for my #8 I will watch the CP ITVV 777 video and see if it happens to show it... Maybe it is an operator option or like you said, just SOP.Thanks John,-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites

Hi Adam, doing KEWR-LLBG right now and like you asked I set my step to 2000 during my pre-flight. Indeed, this time the legs page clearly depicts the steps as you scroll through. I see 330 (Initial crz) then 350 370 and 390 as I scroll through my 18 pages of legs :)I think that is the ticket. It is a much more realistic procedure I would imagine to climb at 2000 foot intervals opposed to 4000 foot intervals. I still wonder if this is realistic CDU behavior but perhaps Dave and his resources are better qualified to answer that. Anyone got a r/w T7 pilot handy :)-PaulLiquid CooledAMD 4000 San Diego2 Gigs Kingston Corsair XMS CL2Dual 7800 GTX 24 inch widescreen dual 19 inch LCDRaid-0psolksig.jpg

Share this post


Link to post
Share on other sites
Sign in to follow this