Jump to content
The simFlight Network Forums

cannot integrate my flight yoke with PFC - button 8 is sensed as button 7...


Recommended Posts

Hi Everyone:

 

I just got a new Precision Flight Controls (PFC) 737 Flight Yoke with accompanying rudder pedals and throttle console.  I am having a terrible time trying to get the equipment to talk correctly to FSUIPC.

 

Most important, when trying to program the button on the back right of the column yoke, whenever I press the back button, FSUIPC automatically senses it as "Button 7", but the PFC utilities that I received from PFC keep indicating that the very same button is called "Button 8".  Consequently, no matter what I try to assign to this button will not work.  PFC does not seem to know what is wrong, and I am totally confused at this point.  Anyone have any ideas?  They told me that I am supposed to configure this as a joystick, and not a USB device ion their calibration settings. Also, I am not sure if I am supposed to disable or enable the controls and devices in FSX or not.  Lastly, I do not know if it is better to assign this in FSUIPC as a straight FSX input or if I should be using the"Direct to FSUIPC" option.  Any help anyone can give me would be greatly appreciated.

 

Thank you!

 

Chris Catalano

Link to comment
Share on other sites

I just got a new Precision Flight Controls (PFC) 737 Flight Yoke with accompanying rudder pedals and throttle console.  I am having a terrible time trying to get the equipment to talk correctly to FSUIPC.

 

If it is all standard USB joystick-style connection, then it is a matter of Windows seeing it properly, not FSUIPC, because to FSUIPC it will just be another Windows joystick.

 

Does FS see them all?

 

Most important, when trying to program the button on the back right of the column yoke, whenever I press the back button, FSUIPC automatically senses it as "Button 7", but the PFC utilities that I received from PFC keep indicating that the very same button is called "Button 8".

 

That's just a matter of numbering conventions. FSUIPC has always numbered buttons from 0, same as Windows does internally. Other programs simply add 1 to the button number as they assume folks won't understand numbering starting from 0. 

 

Why do you think it is so "important"? The buttons could be called Ginger, Fred, Alice, and so on, as long as when you assign them they stay consistent. I don't understand your angst.

 

 Consequently, no matter what I try to assign to this button will not work.

 

Sorry, that does not follow. Program button 7 and your "button 8" will do what you ask. There's no "consequently" about it!

 

PFC does not seem to know what is wrong, and I am totally confused at this point.  Anyone have any ideas?  They told me that I am supposed to configure this as a joystick, and not a USB device ion their calibration settings.

 

Modern joysticks ARE all USB devices, so that makes no sense.

 

Also, I am not sure if I am supposed to disable or enable the controls and devices in FSX or not.

 

 

You can assign wherever you like, but don't mix. Either everything in FS, or everything in FSUIPC. It doesn't matter unless you want different assignments for different aircraft, which FSUIPC can handle automatically and FS can't handle at all.

 

If you assign in FSUIPC, disable controllers completely in FS.

 

Lastly, I do not know if it is better to assign this in FSUIPC as a straight FSX input or if I should be using the"Direct to FSUIPC" option.

 

That depends on what you are using it on, what addon aircraft. Some add-ons do not like the "direct" method. Otherwise, that is more efficient, that's all. There are some options only available "direct".

 

 Any help anyone can give me would be greatly appreciated.

 

Do please peruse the documentation installed in your FSUIPC Documents subfolder!

 

Pete

 

Link to comment
Share on other sites

Hi Pete:

 

Thanks for the response.  Believe it or not, I actually read the entire user guide cover to cover, but that was about a year ago.  So I am actually guilty of not remembering the details of some of it.  The fact is that my computer got a virus, and I had to do a complete reinstall of Windows 7, and as such, starting over so to speak with FSUIPC has given me some trouble.  In fact, I actually got quite good at using FSUIPC a year ago, to the point where (you'll be proud of me) I even programmed throttle cut ranges on my throttle handles and also the reversers.  So I was really getting good at using FSUIPC a year ago.  So now when I am trying to remember some of the subtleties, I am a bit overwhelmed. Sorry. Last night I did manage to  reprogram an entire new profile for the PFC equipment I am using.  I have chosen to disable the FSX controls completely, and to send all the inputs direct to FSUIPC.  That seems to be working best for me. All of this is for use with the PMDG 737 NGX, the only plane I ever fly.  While I am getting some weird results with getting the reversers to activate when I land (they don't spool up unless if I first quickly raise and lower the throttles through my throttle cut zone), I am having a lot of success reprogramming FSUIPC.  (BTW, I wonder if there are known issues with the PMDG 737 NGX and FSUIPC, or perhaps Precision Flight Controls equipment?  Have you heard of any that you know of?)

 

With regard to the "Button 07" and "Button 08" designations... here is the thing... I am certain I know how to program any and all buttons.  The fact is, I can program each and every one of the buttons on my PFC column yoke, and I have.  But for some unknown reason, the one button  on the back right (whatever it is designated as) will not program any command.  I have key commands associated with all the other buttons on the yoke and they are working correctly.  It is only that one button on the back right of my column yoke that is not allowing anything to be programmed to it.  No matter what I try to assign to it, it will not work, whereas it always used to before my Windows 7 reinstall.  Am I to presume there is something wrong with the button itself from a hardware standpoint?  However, I doubt this because when I test the buttons in the PFC calibration/hardware tools, it shows that it is responding (although it calls it "button 8 and not button 7).  I know the button therefore seems to be functioning, so I presumed it must have something to do with the numeric designation (but now after reading your reply, I see that this seems irrelevant, so thank you for explaining that).  So I just cannot figure out why I can program all the other buttons easily and successfully, but not this one button.  I don't know if there is something conflicting with it either in FSUIPC or elsewhere, so I am very frustrated at this point.  I mean, if I can program all the other buttons, what's one more button?  It should be just as easy as all the others.  Plus, I used to have this particular button functioning before my reinstall.  Is there something that you can think of that I may be simply missing?

 

(BTW, for some reason, the PFC hardware configuration tools let the user select each of the three devices I have as either a Joystick, or as a "PFC USB" input device.  Selecting the latter seems to open up other details in a drop down menu that I can further configure, such as: the switch layout style [boeing, SAAB, or Beech/Mooney/Cessna, etc], whether it is for one or two pilots with a pilot and copilot setup, disabling the possible throttle commands for the yoke, and other items such as that.  Although you correctly pointed out that today's joysticks are all USB, I have a feeling that PFC has this choice present so you can further configure their equipment, although I am not absolutely certain of this)

 

Anyway, if you can think of anything that I have overlooked with the programming of that one button on my column yoke, I would appreciate any suggestions.  Sorry if I have forgotten some of the finer details of your excellent program.  I was really getting quite good at using it a year ago.  Thankfully, much of it has started to come back to me.

 

Thanks again,

 

Chris Catalano

Link to comment
Share on other sites

All of this is for use with the PMDG 737 NGX, the only plane I ever fly.  While I am getting some weird results with getting the reversers to activate when I land (they don't spool up unless if I first quickly raise and lower the throttles through my throttle cut zone), I am having a lot of success reprogramming FSUIPC.  (BTW, I wonder if there are known issues with the PMDG 737 NGX and FSUIPC, or perhaps Precision Flight Controls equipment?  Have you heard of any that you know of?)

 

I don't know what PFC equipment you have -- all mine is either serial port driven using my own PFCFSX.DLL driver or USB but needing my PFCHID.DLL driver. I suspect the stuff you have is pure USB Joystick type hardware, which needs no special drivers and is recognised by Windows as joysticks in any case.

 

I don't use any PMDG aircraft, but I think most users fund they need to assign throttles to the normal FS controls, even in FSUIPC, and NOT calibrate in FSUIPC either. I think they may even program reverse on a button assigned to "throttle decrement" controls. But don't take my word for it. Ask around.

 

With regard to the "Button 07" and "Button 08" designations... here is the thing... I am certain I know how to program any and all buttons.  The fact is, I can program each and every one of the buttons on my PFC column yoke, and I have.  But for some unknown reason, the one button  on the back right (whatever it is designated as) will not program any command.  I have key commands associated with all the other buttons on the yoke and they are working correctly.  It is only that one button on the back right of my column yoke that is not allowing anything to be programmed to it.  No matter what I try to assign to it, it will not work, whereas it always used to before my Windows 7 reinstall.  Am I to presume there is something wrong with the button itself from a hardware standpoint?  However, I doubt this because when I test the buttons in the PFC calibration/hardware tools, it shows that it is responding (although it calls it "button 8 and not button 7).  I know the button therefore seems to be functioning, so I presumed it must have something to do with the numeric designation (but now after reading your reply, I see that this seems irrelevant, so thank you for explaining that).  So I just cannot figure out why I can program all the other buttons easily and successfully, but not this one button.  I don't know if there is something conflicting with it either in FSUIPC or elsewhere, so I am very frustrated at this point.  I mean, if I can program all the other buttons, what's one more button?  It should be just as easy as all the others.  Plus, I used to have this particular button functioning before my reinstall.  Is there something that you can think of that I may be simply missing?

 

What are all of the other buttons numbered 0-6 or whatever? Are there missing numbers?  You are really not providing any technical information I can use. When you assign this non-working button, what is entered for it in the INI file? When you've programmed it and go back to look in the assignments, has it mysteriously lost its assignment?

 

Sorry, but I cannot see your PC from here and you are not providing anything I can help with.

 

(BTW, for some reason, the PFC hardware configuration tools let the user select each of the three devices I have as either a Joystick, or as a "PFC USB" input device.  Selecting the latter seems to open up other details in a drop down menu that I can further configure, such as: the switch layout style [boeing, SAAB, or Beech/Mooney/Cessna, etc], whether it is for one or two pilots with a pilot and copilot setup, disabling the possible throttle commands for the yoke, and other items such as that.  Although you correctly pointed out that today's joysticks are all USB, I have a feeling that PFC has this choice present so you can further configure their equipment, although I am not absolutely certain of this)

 

Again, sorry, but I've never heard of a "PFC hardware configuration tool" and have no idea what on Earth it may be doing. I'm afraid you are most certainly dependent upon PFC support for that side of things.   i worked closely with PFC years ago (my cockpit was built by PFC), and produced the drivers for all their kit a while back, but I've no idea what they've been doing recently. I thought their current stuff was either standard Joystick USB, or, special USB (with displays as well as inputs, like their consoles and radio stacks), which would use my PFCHID driver.

 

Pete

 

Link to comment
Share on other sites

Well you are never going to believe this... since I knew I was CERTAIN I knew how to program the buttons correctly, and since I had done this in the past, I decided to try something for a test.  Since I had created several profiles in the past, I decided to load a different profile I created last year and assign it to the particular livery of the PMDG 737-800 I was working with, and guess what?!  That infamous "button 07" works perfectly!!!  In fact, I have it working in every other former profile I created during the past year!  So I guess there was just some sort of glitch with this particular profile that is corrupt, or has become corrupt, because the button seems to work fine in every other profile I have.  When I load the newest profile once again, the button ceases working. While I cannot explain this, I am happy nonetheless that this button is indeed configurable.  Is that crazy or what?

 

Thanks for all the advice.

 

Chris

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.