Jump to content
The simFlight Network Forums

FSUIPC can't see my CH Pro Throttle.

Recommended Posts

All of these can see my CH Prothrottle:


CH Control manager can see the ProThrottle, and it can be calibrated there.

FSX can see the ProThrottle, it is on the list of controllers in the FSX menu, and FSX can assign to it's buttons and axis.

Windows 7 sees the Prothrottle installed.

But FSUIPC in FSX cannot see the ProThrottle.

(FSUIPC can see all the other 5 controllers:

2 CH Quads

1 CH pedals

1 TM Warthog throttle

1 TM Warthog stick

But FSUIPC cannot see the Prothrottle.

(I move the handle and push buttons  on Prothrottle and nothing happens in FSUIPC Options and Settings).

I have unplugged and replugged in the Prothrottle and also shut down and rebooted the PC Computer (Windows7). Which did not help.

0=Joystick - HOTAS Warthog
2=CH Pro Pedals USB
1=Throttle - HOTAS Warthog
5=CH Throttle Quadrant USB
3=CH Throttle Quadrant USB

0=0X,232,D,1,0,0,0    -{ DIRECT: Aileron }-
1=0Y,234,D,2,0,0,0    -{ DIRECT: Elevator }-
2=1Z,256,D,4,0,0,0    -{ DIRECT: Throttle }-
3=1S,256,D,21,0,0,0    -{ DIRECT: ElevatorTrim }-
4=2X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
5=2Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
6=2Z,512,D,3,0,0,0    -{ DIRECT: Rudder }-








Link to comment
Share on other sites

Well, I got it sorted. Reading 'Sticky' Church's hints on joysticks, he said that even if Windows can see all the controllers, and the controllers work in sims and programs, nevertheless Windows will change somethings about (I think Sticky called it) the controllers' ID's every time Windows reboots for about 5 reboots after connecting new joysticks. Apparently FSUIPC needs this to stabilized. Windows will stabilize it's handling/labeling of the controllers after the controllers are first connected, but Windows needs several reboot to do this (so said CH Products programmer Bob Sticky Church).

So even though I had rebooted once after first plugging in the Pro Throttle, I went ahead and rebooted Windows (7) again and again several times using Windows 'Shut Down', not using Windows 'Restart' (again as recommended by Mr. Church). Thus forcing Windows to read all the hardware again on these reboots.

Finally after about 4 reboots FSUIPC was seeing all the controllers and everything now is fine.


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.