Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi Pete!

I have some problems with the pfc.dll v1.90 (I use the Precision Flight Controls Throttle quadrant) and two add-ons: SSW Airbus 310 and Ready for Pushback 747-200.

The problem for these 2 add-ons is the same: the autothrottle system on the autopilot (for the SSW310) and the FFRATS (on the 747RFP) don't work! I do some tests but the only way to solve the problem is to remove the pfc.dll from FS9 and use the default F1/F4 key for the throttle. I think there's some incompatibility with the pfc.dll and these add-ons. I think it's strange that both add-ons have the problem. Can you help me? Or is there someone else who have this problem?

Thanks!

Regards,

Max

Posted

The problem for these 2 add-ons is the same: the autothrottle system on the autopilot (for the SSW310) and the FFRATS (on the 747RFP) don't work! I do some tests but the only way to solve the problem is to remove the pfc.dll from FS9 and use the default F1/F4 key for the throttle. I think there's some incompatibility with the pfc.dll and these add-ons.

I've really no idea whatsoever what is going on. Can you be a little more explicit about what the problem is? Then maybe I could hazard some guesses.

When the FS A/P is enabled, the throttle inputs should have no effect. If the panels are configured to assume changes on the throttle inputs should disengage the A/T, then it sounds like you have some jitter on your throttle quadrant. Try calibrating with parking spaces at max and min throttle (and park them when using A/T), and also enable the digital filtering.

Note that, with PFC.DLL, if there's no change detected on the throttle levers, no messages for throttle changes are sent to FS.

Regards,

Pete

Posted

Hi Pete and thanks for reply.

Well now I post my problem on the 747RFP forum.

Anyway I try to explain "better" with my poor English :(

The 747RFP has a system called FFRATS which controls the take off power (also power in climb and crz mode) setting the maximum epr value. When you set this system and you are ready to take off you should advance the hardware throttle levers to maximum (as written in the manual) and when epr value reaches 1.1 (I don't remember exactly the value) the FFRATS system is activated and it limits the maximum power to the EPR value set on the FFRATS panel.

If I try to move the levers to full power as written in the manual I have my engines at max power thrust. It seems that the ffrats doesn't work. When I in flight the "traditional" a/t works and it maintains the speed selected.

Now if I remove the pfc.dll and I use the default keyboard assignments (F1-F4) the FFRATS works great! :unsure:

This happen also if i set the levers to idle (and I have not any disalignment or false input from them)

The same problem happens when I use the Airbus A310 SSW!

On this add-on all the autothrottle system doesn't work but when I remove the pfc.dll (and so disable the console) all work :roll:

This happen ONLY with these two add-ons...

All others work without any problem and my PFC Console is good!

I'd like to know if someone else has this problem.... :oops:

PS: I have a friend of mine which use the same add-on which use the MS Force FeedBack throttle and CH Cloche with the throttle lever and all work.

Many thanks to all!

Best regards,

Max

Posted

The same problem happens when I use the Airbus A310 SSW!

On this add-on all the autothrottle system doesn't work but when I remove the pfc.dll (and so disable the console) all work :roll:

Please read and join in on the thread entitled "FSUIPC & PSS Airbus".

Regards,

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.