Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Problems with retarding throttles ! Please help !

Featured Replies

Hi everybody,I've posted a message on this some time ago but never had any echoes of it.When flying 767PIC, in flight, when I retard the throttles to idle, the left engine won't go to idle. What happens is that as I retard the throttles, approaching the 35% N1, suddenly the left engine spools up to 60% ! Then I continue to retard the throttles to idle, but the left engine stays at 60% while the right engine sets in idle. Imagine the problems I have on landing ! The aircraft takes half of the runway to actually land ! Once on the ground, there I can go ti idle with both engines....However, using the autopilot, on an autoland, the engines go to idle with no problem !Does anybody else have / had this problem or similar ? I'm using CH Yoke + Pro Pedals, WinXP, FS2002, 767PIC+posky merge patched to 1.1 etc. All drivers to the most recent versions. FSUIPC as well with axis configured etc. This ONLY HAPPENS with 767PIC ! All other aircraft work perfectly : A320 PSS, DF7374, etc.Any suggestions on how to solve the problem ?Many thanks for your replies that can help me love flying the 767PIC again since it's such an awesome piece of software... !Andr

Andr

Thanks for the suggestion Stephan, however that's not it. Actually, If I show up the pedestal during the throttle retard, both throttles are linked, but when reaching 35% N1 suddenly the left engine throttle jumps up - sort of like an FS2002 internal overriding of the joystick ! Pretty strange and still not solvedAnybody else had this ???Andr

If just discovered that if I disable EEC on both engines the problem is gone. So I suspect an internal 767 PIC panel problem here ?Well, this is still anoying to have to remember to switch off the EEC before landing... anybody else has suggestions for a permanent fix ?Thanks,Andr

Hi,Reinstall FS2k2 patch.Tero

PPL(A)

Hi,I've tried to reinstall 767 PIC and the Fs2002 patch, with no success.I've tried to delete the 767W.ini but it doesn't work either..; :-(Thanks however !Andr

>If just discovered that if I disable EEC on both engines the >problem is gone. So I suspect an internal 767 PIC panel >problem here?I doubt it is an internal PIC panel problem, per se. A lot of other folks use this panel and even with very similar hardware. No one else has made comments on this so it is unlikely (not impossible) that the problem is related to any bugs in PIC. The most likely problem is specific to your system, either software or hardware. Something is not right with how your system is interacting with PIC. As it is very complex and utilizes a lot of custom code, it may just be that PIC is showing some minor problems with your system that other aircraft are not able to detect.If reinstalling PIC doesn't help (make sure to completely uninstall it prior), there must be something else sending erroneous info to the throttles. I would suspect your yoke or any drivers associated with it. However, I would suggest you go through a trouble-shooting routine and you'll be able to track down the problem.

Hi Ken and thanks for your reply.However, since the problem only arises within 767 PIC, and only when the panel takes control of the throttles via the EEC, and since this happens only with 767 PIC, and since the throttle of my Yoke never shows any problems in the joystick config panel (the axis travels are fully normal) and in FSUIPC all is calibrated and normal.So I don't see how it could be the joystick or the software since there are no drivers for this Yoke, it's USB.I don't know were to start searching for another problem in my system ; I mean all drivers are the latest....don't get it at all.Maybe I'll try to re-install a second FS2002 with only 767 PIC + FS2K2 patch on it, without merging with Posky...we shall see.Ok, CU !Andr

Andr

I once had a problem of not being able to cut throttles completely to idle - therefore thrust reversers would not deploy after landing. I recalibrated the throttle over and over with no help. So finally I reserved fairly generous amount of lower calibration zone for the idle. This way I must have sacrificed close to 13% of the total throttle range. But now everything works prefectly - no problem with idle and thrust reversers.Not sure whether this is similar to your problem but it is a good indication that PIC's software is sound (btw, I do use EEC of course) and the issue was the noise from the throttle/USB. Michael J.

Michael J.

  • 3 months later...

I seem to have similar problem which I am presently searching. To troubleshoot I began a slow Idle decent from FL330 autothrottle and auto pilot off. FL300 and mach 6.1 Throttle 1 and 2 alternaltely jump up to 60% and down again over and over as to not alow the engines to settle below 50% or so. I pitched to nose over and increased speed to mach 6.3 and the problem went away. At Fl 280 its at mach 6.0, Fl 230 its mach 5.9 etc...The problem also goes away if I turn off both EEC's or if I deselect "set" in the multiple throttle option of fsuipc. I've tried plenty of null area in both fsuipc and msfs with no change. Joy 1 is a logitec wingman for ail and elv only, joy 2 is custom using ch vpp driver for throttle 1, 2, rudder and spoiler. The speed thing makes this problem interesting. Any clues anyone? I will continue my search as I reconfigure my joystics to 2 wingmans in the future and update this thread if needed. Thanks. Oh and yes I've de instlled and reinstalled msfs pic and put newest fsuipc first in the diretory.

WOW!!!!......Mach 6.0!!!Thats an impressive airframe & engine configuration you have on that 767.;)-=MB=-

Big oops, you all know I meant 0.60 etc...Thanks for pointing that out.phil

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.