Jump to content
The simFlight Network Forums

no throttle response pokeys card and FSUIPC


Recommended Posts

I have a strange problem with my throttle levers. They are direct connected to a poti and with a pokeys card. FSUIPC is controling the inputs. There is no conflicting assignment in FS9! The problem is that I have to select FSUIPC after every start of FS9 and scan the axis for the throttles again otherwise they are not recognized by FS9. The assignment in FSUIPC is still there but I just have to scan the axis again and than FS9 is recignizing the throttles? Other controls like speedbrake connected in the same way are working without the mentioned procedure.

Link to comment
Share on other sites

I have a strange problem with my throttle levers. They are direct connected to a poti and with a pokeys card. FSUIPC is controling the inputs. There is no conflicting assignment in FS9! The problem is that I have to select FSUIPC after every start of FS9 and scan the axis for the throttles again otherwise they are not recognized by FS9. The assignment in FSUIPC is still there but I just have to scan the axis again and than FS9 is recignizing the throttles? Other controls like speedbrake connected in the same way are working without the mentioned procedure.

Sounds like they are asleep. Are you sure you actually need to scan them? Normally just entering the options and exiting again will do the trick.

Check your USB power management in Windows Device Manager. It defaults to "on" which makes Windows remove the power when the device isn't used for a while. If they are asleep when fS + FSUIPC is starting up, then the devices won't be seen.

Regards

Pete

Link to comment
Share on other sites

Thank you Pete for the fast response but I'm aware of this problem and funny thing is that the poti for the speed brake is on the same card and is not sleeping it is responding without rescanning in FSUIPC? Should I delete the ini file? But I have a lot connected it is a lot of work.... :(

Link to comment
Share on other sites

Thank you Pete for the fast response but I'm aware of this problem and funny thing is that the poti for the speed brake is on the same card and is not sleeping it is responding without rescanning in FSUIPC? Should I delete the ini file? But I have a lot connected it is a lot of work.... :(

Don't see what good deleting the INI file will do. If one axis is readable on a device, they all are readable as it is one call into Windows to read all axes, POVs and buttons, all at once. There's no way to separate them. And FSUIPC does the same thing when you enter the Options as it does when it is started, exactly the same.

I assume you are using an up-to-date supported version of FSUIPC, by the way? 3.999z.

Pete

Link to comment
Share on other sites

Hallo Pete I'm using version 3.999 and I found out:

when I'm using 'send to FS as normal axis' the throttles are recognized immediately but I want to use 'send direct to FSUIPC' but than the throttles are only recognized when I scan them again in FSUIPC???

More ideas it is working now but not the way I want it?

Link to comment
Share on other sites

when I'm using 'send to FS as normal axis' the throttles are recognized immediately but I want to use 'send direct to FSUIPC' but than the throttles are only recognized when I scan them again in FSUIPC???

Recognised where? In the axis assignments? In calibration? In FS? In a specific aircraft, or all?

At the assignments stage therer is obviously not difference.

In the calibration tab, axes sent DIRECT to calibration have to be recognised there -- it is more likely that those sent as normal controls to Fs could get intercepted by another add-on.

If you mean in FS itself, then do you mean all aircraft, or only specific ones? And when do the axes appear to disconnect? How long does it take?

I remember you said your speedbrake, connected in the same way (and assigned in the same way) was okay. But in FSUIPC all axes are treated alike, so are you sure it isn't more related to the aircraft you are using?

Regards

Pete

Link to comment
Share on other sites

sorry I wasn't precise enough. Recognized means I'm starting FS9 and the throttles are moving as soon as I push them forward. Not recognized means I start FS9 and I have to enter FSUIPC and use the scan function on axis ass. and then they are working.

I always use the same aircraft 737 default.

Link to comment
Share on other sites

sorry I wasn't precise enough. Recognized means I'm starting FS9 and the throttles are moving as soon as I push them forward. Not recognized means I start FS9 and I have to enter FSUIPC and use the scan function on axis ass. and then they are working.

I always use the same aircraft 737 default.

Hmmm. When you say "I have to enter FSUIPC and use the scan function on axis ass", what does it show? Do you have to scan all of them? Have you tried merely opening the options and closing them again. This makes FSUIPC repeat the initial scan, just the same as it does when it first loads up.

Once they work, do they continue working for the entire session?

If yes to both of those questions, then it sounds like for some reason your Pokeys things are not really ready when FS is first started, so they appear disconnected in the initial scan. I really cannot understand why -- maybe Pokeys support could advise? I've really not heard of any such behaviour before. FSUIPC just uses standard Windows facilities for these things, nothing special or different.

Regards

Pete

Link to comment
Share on other sites

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.