October 17, 200322 yr James, You were 100% correct about the ARC moving with the advance of the THROTTLES like it is in PIC. The only thing that should lack behind slightly is the N1. Sorry, I jumped the gun here thinking too much in the actual N1 insted of reading what you really said. So yes there IS a issue with this here on the 737. Please forgive my aburptness in responding to you the way I did. Sometimes comparisons are indeed relevent and I should watch my emotions in this regard to read between the lines. [h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-5/196432/winglets_lg.jpg Randy J Smith
October 17, 200322 yr Author No promises James, but they are looking at this right now ;)[h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-5/196432/winglets_lg.jpg Randy J Smith
October 18, 200322 yr Hey gents:Could you briefly summarize the issue? I searched for the original post on this subject, but I can't find it.Thanks,James W.
October 18, 200322 yr Author THe issue is that the predicted ARC should move in sync with your throttles and not lag behind, the actual N1 should lag behind slightly but not the arc... The original post had some personal attacks so it was removed...[h4]Best Wishes,Randy J. Smithhttp://img.villagephotos.com/p/2003-5/196432/winglets_lg.jpg Randy J Smith
October 18, 200322 yr "THe issue is that the predicted ARC should move in sync with your throttles and not lag behind, the actual N1 should lag behind slightly but not the arc..."I assume, by "predicted ARC", you mean the marker for "commanded" thrust, Randy? The arc itself is the difference between the commanded N1 (thrust lever position) and the actual N1. The marker doesn't have any sort of predictive feature... not like, say, the airspeed trend vector.You can slam the throttles forward really quickly and the command mark will follow the throttles _almost_ immediately. There may be a very slight delay due to electric signals moving down wires, graphics processing, etc. However, the large delay in the current version of PMDG makes it very difficult to manually set the thrust for takeoff.Depending on how fast the thrust levers are moved forward, the length of the arc between the commanded N1 and actual N1 can vary substantially. The engine has to accelerate to the commanded N1 value, but the EEC won't allow it to accelerate too quickly.... otherwise the engine might stall.Slam dunk (acceleration) tests are sometimes done on engine ground test runs. I don't think we push the levers all the way forward however... that would be too risky. Cheers.Ian. P.S. BTW, I thought this topic was discussed and agreed upon weeks ago (by the "experts")? ;-)
October 18, 200322 yr Great!! I was hoping that this was the issue. I've often wondered if the tick mark should be moving with the throttles (like PIC).Glad to hear that it actually should be, and that it's being addressed.James
October 21, 200322 yr Commercial Member Gents-it was fixed TODAY. ;-)Cheers, Lefteris Kalamaras - Founder www.flightsimlabs.com
October 21, 200322 yr Much appreciated :-)You make it sound so easy, Lefteris.... but I'm sure it wasn't ;-)Thanks.Cheers.Ian.
October 22, 200322 yr Good news, that's another little niggling problem gone.You're right Ian, we spoke about the lagging N1 predictors on a thread called "Thrust Reduction Height" back on 23rd August!
Create an account or sign in to comment