Problem with PFC b737 Yoke

[Peter Dowson]

the problem now is that if i go into FSUIPC and say assign PTT to button 1 the view snaps back to up...

You have something very wrong if merely assigning one control results in another activating. Enable Button and Event logging in FSUIPC and see what the log shows when you do that. I suspect there are still assignments you've not found. The CH-encoding of buttons on yokes, which I think is emulated in the PFC yoke, uses combinations of 4 button signals (the max in an old-fashioned game port device) to produce 15 different button signals, plus an "off". I suspect this is where it's all going wrong -- if they still do that, which of course they may not.

I really have no information so I cannot tell what is going on. I'm only trying to help because I have had dealings with PFC devices -- but not the USB ones except their recent consoles.

If you purchased this recently and you aren't getting support for something which doesn't work, why aren't you creating hades (this forum won't let me use h e l l ! At least not all joined up!) with your supplier, rather than allowing them the complacency of saying "it works here"? I'd demand better suport or your money back!

Pete

[Peter Nielsen]

Tks Pete for the hints,

i enabled logging and this is a part of the log.. there is a constant command for PAN UP from button 32???

789360 [Buttons] 52=R1,32,C65734,0
789360 Repeating flag set: bRef=0, Joy=1, Btn=32 (RepeatDelayCtr=11)
789360 FS Control Sent: Ctrl=65734, Param=0
789360 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP
789422 [Buttons] 52=R1,32,C65734,0
789422 Repeating flag set: bRef=0, Joy=1, Btn=32 (RepeatDelayCtr=11)
789422 FS Control Sent: Ctrl=65734, Param=0
789422 [Buttons] 52=R1,32,C65734,0
789422 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP
789469 [Buttons] 52=R1,32,C65734,0
789469 Repeating flag set: bRef=0, Joy=1, Btn=32 (RepeatDelayCtr=11)
789469 FS Control Sent: Ctrl=65734, Param=0
789469 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP
789516 [Buttons] 52=R1,32,C65734,0
789516 Repeating flag set: bRef=0, Joy=1, Btn=32 (RepeatDelayCtr=11)
789516 FS Control Sent: Ctrl=65734, Param=0
789516 [Buttons] 52=R1,32,C65734,0
789516 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP
789563 [Buttons] 52=R1,32,C65734,0
789563 Repeating flag set: bRef=0, Joy=1, Btn=32 (RepeatDelayCtr=11)
789563 FS Control Sent: Ctrl=65734, Param=0
789563 [Buttons] 52=R1,32,C65734,0
789563 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP
789625 [Buttons] 52=R1,32,C65734,0
789625 Repeating flag set: bRef=0, Joy=1, Btn=32 (RepeatDelayCtr=11)
789625 FS Control Sent: Ctrl=65734, Param=0
789625 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP
789625 [Buttons] 52=R1,32,C65734,0
789672 [Buttons] 52=R1,32,C65734,0

[Peter Dowson]

i enabled logging and this is a part of the log.. there is a constant command for PAN UP from button 32???

Okay. Button 32 is the forward press of a Hat -- FSUIPC numbers the 8 possible positions of a Hat from 32 to 39, clockwise.

789360 [Buttons] 52=R1,32,C65734,0

And that clearly identifies the line in your FSUIPC INI file which assigns button 32, i.e the line reading

52=R1,32,C65734,0

in the [Buttons] section. You said you'd got rid of all FSUIPC button assignments, but evidently not the very one which was troubling you! How did you miss it?

If you aren't sure what you are doing with FSUIPC it would be best to delete your INI file so nothing is set and everything returns to defaults!

Regards
Pete

[Peter Nielsen]

Tks Pete

I deleted this entry

52=R1,32,C65734,0

And all now works PERFECT!!

I am extremely grateful for your hints and replies as this did solve the issue.. Having used CH for the better part of 10 years and also FSUIPC i never ever had this kind of issue and it was driving me nuts..

Only draw back now is that as i went in and killed all my USB drivers i gotta start all over again, as now my Flight Illusion set up is complainig about not existing ports, the TQ on Phidgets has decided it does not like me either and the Rudder has decided it has become a permanent brake.

A well, wonders of Windows!

Pete, Aron Tks gents!

PS.. forgot to say.. the PFC Yoke is wonderful.. very very good.

[Peter Nielsen]

bad dream...
as of last night the aieleron input is as dead as a dodo..

Elevator works fine, calibration does not help, has anyone else had this breaking down on them?
Peter

[mounty]

I had this problem with my PFC yoke some years ago and they told me it was a dysfunctional potentiometer. Didn't do anything with it, sold the unit as was to someone.

Rob

[OmniAtlas]

Had a similar problem with the trim on my PFC Beech Yoke. Regardless of what I programed in FSUIPC, trimming down would cause the plane to go down (and not up), and trimming up would cause the plane to go up (and not down).

Ended up having to delete the aircraft settings in FSUIPC and reprogramming everything again (it was previously assigned with a saitek yoke).

[Peter Dowson]

Had a similar problem with the trim on my PFC Beech Yoke. Regardless of what I programed in FSUIPC, trimming down would cause the plane to go down (and not up), and trimming up would cause the plane to go up (and not down).

A simple reversal would have fixed that. Both FS and FSUIPC have reverse options. You don't normally need them for trim, but maybe yu had one set in one of the places.

Pete

[OmniAtlas]

I tried the reverse option, didn't work but resetting FSUIPC did the trick.

Theres something funny with the PFC yoke buttons; when I enter bios, my key selection (cursors) go crazy -- its like I'm holding down the down-cursor key. I can only enter my bios submenus if I disconnect the yoke first.

[Peter Dowson]

I tried the reverse option, didn't work but resetting FSUIPC did the trick.

Sounds like you had conflicting assignments.

Theres something funny with the PFC yoke buttons; when I enter bios, my key selection (cursors) go crazy -- its like I'm holding down the down-cursor key. I can only enter my bios submenus if I disconnect the yoke first.

You have a button assignment with "repeat" enabled" for a button or switch which is either stuck "on" or "pressed", or a button which does not actually exist but for which Windows is signalling "pressed". The former is more likely.

Pete