Hallo Thomas!
Wenn mich nicht alles täuscht habe ich die Ursache für das Nichteinhalten der Speed bei A/T connect gefunden, beachte mal den ersten Absatz und vergleiche ihn doch mal mit Deiner PFC-Einstellung. Ich habe den Haken entfernt und der 1. Flug klappte,hoffentlich bleibt es dabei:
Zitat LevelD-Forum
Make sure that the "Suppress possible interference from GamePort throttle assignments" option on the main tab of the PFC driver page is ***NOT*** checked. That option was put there specifically for PIC767 in FS2000/2002, because the method by which the PIC (and presumably LDS as well) panel's A/T controls the power is via the same mechanism as the regular joystick input. Selecting that option kills the A/T inputs to FS.
Second, I've found that if I firewall the throttle either full up or full idle, the A/T is less prone to jumping around. It appears that any time the PFC throttle input value changes, the throttle input to FS is set to the PFC throttle value until the LDS A/T resets it to where the A/T wants it. The net result is seeing the throttle target bouncing back and forth and jerky rapid changes in the power setting. If you leave some headroom in your throttle calibration, so that the last 1/2 inch or so of travel does not change the throttle input value, then it will prevent the PFC throttle values from drifting and causing these spurious power excursions.
I believe that something still needs to be done to disable the PFC throttle input while the LDS autothrottle is active. When the power is advanced for takeoff, it ratchets its way up, giving the definite appearance that the A/T and the PFC control are fighting each other. That could be accomplished by either programming the appropriate FSUIPC calls into the panel to disconnect the PFC axes during A/T operation, or by PFC, FSUIPC, or a utility program if a means is provided to ascertain if the LDS A/T is engaged.
Regards
Bob Scott
ATP IMEL Gulfstream II-III-IV-V L-300
Zitat Ende
Gruss
Rolf
|