PFC Throttle Console and Quadrant set up

[grm1]

Hi Pete,

I am a registered user of FSUIPC. I have version 4.9.6.3 installed in PD3V3.4.18.19475. I have used PFC yokes for a number of years without issue, first the Vmax yoke and now the Cirrus yoke. They are magnificent so I recently purchased their throttle console and the six lever turbo prop quadrant with the go around button. I am looking for instructions to get the rudder trim on the console and the reverse function on the quadrant to work. when I asked PFC for instructions this was the reply I received.

 "Greg,

 

Hello! Sorry about the problem you have experienced with the set up. Our console is only full compatible with X-Plane 9 as we have a specific driver for it. Though you can make it work with FSX using FSUIPC, unfortunately we do not have instructions for this and will have to refer you to the Peter Dowson.

 

The forum for FSUIPC is http://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/.

 

Sincerely,

 

Ivan Bernardo

Technical Support"

 

After spending close to a $1,000 I expected much better support from PFC. 

 

Will you assist me with instructions on how to set up the rudder trim and reverse function? I was able to get the landing gear lever to function properly using FSUIPC but I do not have a clue as to the rudder trim and reverse. The prop and condition levers work fine.

 

Thanks,

 

Greg

 

[Pete Dowson]

25 minutes ago, grm1 said:

I am a registered user of FSUIPC. I have version 4.9.6.3 installed in PD3V3.4.18.19475.

Please update to 4.964 now.

26 minutes ago, grm1 said:

Will you assist me with instructions on how to set up the rudder trim and reverse function? 

Why not try assigning them in the axis assignments? The FSUIPC User Guide might help!

Pete

 

[grm1]

Pete,

I have read the users guide and have tried assigning them in the axis assignments. For the rudder trim, I can see different values being entered when I rotate the knob. I click ok to accept and save but it does not change the rudder trim setting in the aircraft. I am using the Flight 1 B200 King Air as the loaded aircraft. I get no values shown when I try to create a reverse axis. When I try to calibrate the reverse or rudder trim in the calibration section I get 0 for every value set. I have tried the "send direct to FSUIPC" option. I know this is not your fault or responsibility, but this way harder than it needs to be. Any suggestion as to the proper proceedure would be greatly appreciated. 

Greg

 

 

 

[Pete Dowson]

50 minutes ago, grm1 said:

For the rudder trim, I can see different values being entered when I rotate the knob. I click ok to accept and save but it does not change the rudder trim setting in the aircraft. I am using the Flight 1 B200 King Air as the loaded aircraft.

Always test with a default aircraft. Many add-ons do their own thing.

51 minutes ago, grm1 said:

I get no values shown when I try to create a reverse axis.

If there's no input from the device then FSUIPC can't do anything with it. What is this "reverse axis" in any case?. Where do you have that on the device? My PFC throttle quadrant just has the 6 levers. Are you using two of those? All the levers on mine were the same, just 6 axes you could assign to anything. I fly 737 so I have two throttles, two reversers, a speedbrake and a flaps assigned on mine (not in that order). It's controlled through my PFCFSX.DLL driver.

From the fact that you've not mentioned PFCFSX I assume your device is some new USB connecting device which doesn't need my PFCFSX.DLL driver. Is that right? I know PFC were moving away from the old serial port based system to standard USB joystick control. Otherwise, if you are using PFCFSX, then it is just a matter of selecting the correct configuration in its own menu, and calibrating there.

If it is a standard Windows-recognised Game Controller with 7 axes and the flaps INC/DEC lever, then I assume FS can see all of the levers and the switches?Can you see them all in Windows Game Controllers? Do they operate correctly there?

I can help with FSUIPC and PFCFSX, but not with generic joystick devices I've never seen. I do software support (my my software), not hardware.

So maybe you should explain in a lot more detail what you have, what you have tried, and what you are doing.

Unfortunately I'm now away till Monday, so there will be a delay before any more replies.

Pete

 

[grm1]

Pete,

Here is the PFC picture of the throttle quadrant I am try to set up. PD3V3 does see all the lever axis and will calibrate them.

There are stops built into the housing for the six levers, similar to a real turbo prop. This quadrant does mirror that found in a B200 King Air. I have set the throttle axis to go from idle to max power above the detent,  leaving the travel  below the detent to activate the reverse function. I have tried calibrating the full length of the throttle range, but the aircraft do not go into the reverse in the aircraft, it just increases the total distance of throttle adjustment. The prop levers will put the props into feather, when moved below the detent. The condition levers will cut off the fuel and shut down the engines when moved past the detent. I expected that there would actually be a button I could set to perform the "decrease throttle quickly" function such as the default F2 key press. There is not. I have been trying to use the FSUIPC reverse axis function for the unused portion of the throttle lever travel. I have also tried assigning a key press button macro at the end to the throttle travel without success. This would be the best outcome as I also fly the PMDG 737 a lot and I have seen your comment in another post that the PMDG aircraft will not recognize a reverse axis. Is assigning a key press macro possible at the end of the axis? 

As to the rudder trim axis, it is a rotary knob on the console itself. I have had FSUIPC recognize this as an axis, however it had no effect on the King Air's rudder trim. As you suggested, I will test this with a default aircraft. However, I only fly advanced add-on aircraft. Is it possible to use this rudder trim axis control to be set up to send the flight simulator key stroke instructions for rudder trim left and rudder trim right?

I think what is frustrating me the most is that PFC is telling me it is possible to make it work with FSUIPC but not how. As part of my due diligence, prior to purchasing this quadrant, I saw a you tube video of the this quadrant and console working perfectly with the Majestic Q400 in PD3V3. 

I hope you enjoy your weekend away and look forward to your reply.

 

Thank you for your help,

 

Greg

 

 

 

 

[grm1]

Pete,

Thank you for your suggestion to test the rudder trim in a default aircraft. It works fine in the default Mooney. I then tested it in the A2A P-51 and Milviz P-38L as these were the aircraft I really wanted to use it with. The rudder trim works fine in both aircraft. I can assign the reverse function to the go around button but would prefer to get the throttle axis working the reverse.

Thanks for FSUIPC and your help.

Greg

 

[grm1]

Pete

I have resolved the issue. When I first got the console and throttle quadrant, I set up and calibrated the six levers using PD3V3 axis assignment and calibration. The throttle worked very well with the exception of the reverse function. After many hours of trying various methods, I deleted the PD3V3 settings and assigned the axis and calibration using FSUIPC. This worked perfectly including the reverse range on the throttle levers. Now the TO/GA button is available as I had been using that to generate reverse thrust. I am going to try to map the mouse click to the auto throttle engage click in the PMDG 737.

Thanks for your help and patience,

Greg

[grm1]

I now have a new issue with the PFC console and quadrant. I am sure I have caused it with my fumbling around. Neither PD3V3 or FSUIPC will recognized a new button being pushed for assignment. The old assignments I had mapped in PD3V3 still work. I have axis assigned and calibrated with FSUIPC. The original button assignments are in PD3V3. How do I start over from stratch. I have tried deleting FSUIPC, un plugging the console and rebooting the computer. If I delete the button assignments in PD3V3 will FSUIPC them be able to see them for assignment? 

FSUIPC CFG

 

[General]
Console=No
UpdatedByVersion=4964
History=TZR739N9WVKKQWSRAUN8L
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
NewDeleteVehiclesForAES=No
AutoScanDevices=Yes
AssignJoystickIDs=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
OOMcheck=Yes
OOMcheckInterval=10
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=19
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.4.18.19475
SimConnectUsed=3.4.0.0

[Traffic Limiter]
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50

[JoyNames]
AutoAssignLetters=No
0=PFC Throttle Quadrant Console
0.GUID={21966330-F9F0-11E6-8001-444553540000}
1=CH PRO PEDALS USB
1.GUID={E16F79B0-DDB0-11E5-8004-444553540000}
2=PFC Cirrus Yoke
2.GUID={E16D08B0-DDB0-11E5-8003-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10
0=17X,1,D,0,9,0,0    -{ DIRECT: Throttle1 }-
1=17Y,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
2=17Z,256,D,0,17,0,0    -{ DIRECT: PropPitch1 }-
3=17R,256,D,18,0,0,0    -{ DIRECT: PropPitch2 }-
4=17U,256,D,0,13,0,0    -{ DIRECT: Mixture1 }-
5=17V,256,D,14,0,0,0    -{ DIRECT: Mixture2 }-

[LuaFiles]
1=Aerosoft_F14AB

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=H0,0,K71,8     -{Key press: G}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=F:\Prepar3D\Sound\
Device1=Primary Sound Driver
Device2=Speakers (2- High Definition Audio Device)
Device3=Digital Audio (S/PDIF) (2- High Definition Audio Device)
Device4=S27B550-C (NVIDIA High Definition Audio)
Device5=Digital Audio (S/PDIF) (2- High Definition Audio Device)

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=Yes
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Throttle1=-16384,-3483,512,16383
Throttle2=-16384,-3483,512,16383
Mixture1=-16384,2451,2451,16383
Mixture2=-16384,1161,1161,16383
PropPitch1=-16384,-1677,512,16383
PropPitch2=-16384,-903,512,16383
Rudder=-16380,-512,512,16380

[Profile.X]
1=Eaglesoft Citation X 2.0 N713FL 750

[JoystickCalibration.X]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Throttle1=-16384,-3483,512,16383
Throttle2=-16384,-3483,512,16383
Mixture1=-16384,2451,2451,16383
Mixture2=-16384,1161,1161,16383
PropPitch1=-16384,-1677,512,16383
PropPitch2=-16384,-903,512,16383

HID Scanner

 Device at "\\?\hid#vid_045e&pid_0095&col01#8&2832de4c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=045E, Product=0095 (Version 4.36)
  Manufacturer= 
  Product= 
  Serial Number= 
  Device is a mouse
  Usage Page: 1
  Input Report Byte Length: 6
  Output Report Byte Length: 0
  Feature Report Byte Length: 2
  Number of Link Collection Nodes: 3
  Number of Input Button Caps: 1
  Number of InputValue Caps: 4
  Number of InputData Indices: 9
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 1
  Number of Feature Data Indices: 1
  Buttons range 1 -> 5 at indices 0 -> 4
  Value Y at index 5, range -127 -> 127, using 8 bits
  Value X at index 6, range -127 -> 127, using 8 bits
  Value Wh at index 7, range -127 -> 127, using 8 bits
  Value Wh at index 8, range -127 -> 127, using 8 bits
  **************************************************************************
  
  Device at "\\?\hid#vid_045e&pid_0095&col02#8&2832de4c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=045E, Product=0095 (Version 4.36)
  Manufacturer= 
  Product= 
  Serial Number= 
  Usage Page: C
  Input Report Byte Length: 0
  Output Report Byte Length: 0
  Feature Report Byte Length: 2
  Number of Link Collection Nodes: 1
  Number of Input Button Caps: 0
  Number of InputValue Caps: 0
  Number of InputData Indices: 0
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 1
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 1
  **************************************************************************
  
  Device at "\\?\hid#vid_045e&pid_0095&col03#8&2832de4c&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=045E, Product=0095 (Version 4.36)
  Manufacturer= 
  Product= 
  Serial Number= 
  Usage Page: C
  Input Report Byte Length: 2
  Output Report Byte Length: 0
  Feature Report Byte Length: 2
  Number of Link Collection Nodes: 2
  Number of Input Button Caps: 0
  Number of InputValue Caps: 1
  Number of InputData Indices: 1
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 2
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 2
  Value Wh at index 0, range -127 -> 127, using 8 bits
  **************************************************************************
  
  Device at "\\?\hid#vid_0689&pid_d011#9&1319a53f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=0689, Product=D011 (Version 2.0)
  Manufacturer= Precision Flight Controls, Inc.
  Product= PFC Throttle Quadrant Console
  Serial Number= 
  Usage Page: 1
  Input Report Byte Length: 21
  Output Report Byte Length: 11
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 4
  Number of Input Button Caps: 1
  Number of InputValue Caps: 27
  Number of InputData Indices: 35
  Number of Output Button Caps: 0
  Number of Output Value Caps: 10
  Number of Output Data Indices: 10
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  Buttons range 1 -> 8 at indices 7 -> 14
  Value Dial at index 0, range 0 -> 1023, using 16 bits
  Value Sldr at index 1, range 0 -> 1023, using 16 bits
  Value R/RZ at index 2, range 0 -> 1023, using 16 bits
  Value V/RY at index 3, range 0 -> 1023, using 16 bits
  Value U/RX at index 4, range 0 -> 1023, using 16 bits
  Value Z at index 5, range 0 -> 1023, using 16 bits
  Value X at index 6, range 0 -> 1023, using 16 bits
  Value 0x17 at index 15, range 0 -> 255, using 8 bits
  Value 0x16 at index 16, range 0 -> 255, using 8 bits
  Value 0x15 at index 17, range 0 -> 255, using 8 bits
  Value 0x14 at index 18, range 0 -> 255, using 8 bits
  Value 0x13 at index 19, range 0 -> 255, using 8 bits
  Value 0x12 at index 20, range 0 -> 255, using 8 bits
  Value 0x11 at index 21, range 0 -> 255, using 8 bits
  Value 0x10 at index 22, range 0 -> 255, using 8 bits
  Value 0x0F at index 23, range 0 -> 255, using 8 bits
  Value 0x0E at index 24, range 0 -> 255, using 8 bits
  Value 0x0D at index 25, range 0 -> 255, using 8 bits
  Value 0x0C at index 26, range 0 -> 255, using 8 bits
  Value 0x0B at index 27, range 0 -> 255, using 8 bits
  Value 0x0A at index 28, range 0 -> 255, using 8 bits
  Value 0x09 at index 29, range 0 -> 255, using 8 bits
  Value 0x08 at index 30, range 0 -> 255, using 8 bits
  Value 0x07 at index 31, range 0 -> 255, using 8 bits
  Value 0x06 at index 32, range 0 -> 255, using 8 bits
  Value 0x05 at index 33, range 0 -> 255, using 8 bits
  Value 0x04 at index 34, range 0 -> 255, using 8 bits
  **************************************************************************

 
  Device at "\\?\hid#vid_0689&pid_d014#9&d8a55c6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=0689, Product=D014 (Version 2.0)
  Manufacturer= Precision Flight Controls, Inc.
  Product= PFC Cirrus Yoke
  Serial Number= 
  Usage Page: 1
  Input Report Byte Length: 21
  Output Report Byte Length: 11
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 4
  Number of Input Button Caps: 1
  Number of InputValue Caps: 4
  Number of InputData Indices: 20
  Number of Output Button Caps: 0
  Number of Output Value Caps: 1
  Number of Output Data Indices: 1
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  Buttons range 1 -> 16 at indices 3 -> 18
  Value Z at index 0, range 0 -> 2047, using 16 bits
  Value Y at index 1, range 0 -> 2047, using 16 bits
  Value X at index 2, range 0 -> 2047, using 16 bits
  Value 0x00 at index 19, range 0 -> 255, using 8 bits
  **************************************************************************
  
  Device at "\\?\hid#vid_068e&pid_00f2#9&9f14c97&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=068E, Product=00F2 (Version 0.0)
  Manufacturer= CH PRODUCTS
  Product= CH PRO PEDALS USB 
  Serial Number= 
  Usage Page: 1
  Input Report Byte Length: 4
  Output Report Byte Length: 0
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 2
  Number of Input Button Caps: 0
  Number of InputValue Caps: 3
  Number of InputData Indices: 3
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  Value Z at index 0, range 0 -> 255, using 8 bits
  Value Y at index 1, range 0 -> 255, using 8 bits
  Value X at index 2, range 0 -> 255, using 8 bits
  **************************************************************************
 

HID scanner report

 

 

 

[Pete Dowson]

9 hours ago, grm1 said:

I now have a new issue with the PFC console and quadrant. I am sure I have caused it with my fumbling around. Neither PD3V3 or FSUIPC will recognized a new button being pushed for assignment. The old assignments I had mapped in PD3V3 still work. I have axis assigned and calibrated with FSUIPC. The original button assignments are in PD3V3.

It is as very bad idea indeed to have controllers enabled in P3D and assigned in FSUIPC. Choose one or the other! Assign axes in P3D not in FSUIPC if that's where you want buttons assigned. Otherwise DISABLE controllers altogether in P3D and use FSUIPC exclusively.

Currently you have no buttons assigned in FSUIPC at all, so I can't help you with why they may not function.

BTW, whilst your PFC devices look exactly the same as mine they are completely different. Yours are standard joystick devices, which must be supported by PFC or their retailers. They were wrong referring you to me! I've never had any such devices to test with and they do not use any driver software I provided specifically for PFC devices.

Pete

 

[grm1]

Pete,

I want to thank you for all your help. The problem with the button assignments is that windows sees the device but I can not get any of the axis or buttons to show up in the game controller test mode. I have a call into PFC support.

Greg

 

 

[grm1]

Pete,

I finally have it all solved. The issue of windows not seeing the buttons or levers was caused by the device being seen as a USB device and not a joy stick. I caused this when I deleted a PFC calibration utility. I re-downloaded the utility and changed the status of the device back to joy stick. A search of the AVSIM forum, revealed this nomenclature issue as a potential cause. Windows now saw the buttons and levers as FSUIPC and PD3V3. I currently have all the axis and buttons assigned through PD3V3. The six levers are calibrated with FSUIPC. The rudder trim is assigned as an axis through FSUIPC. It all works as expected.

I have called PFC support and left another message informing them the issue was resolved and they did not need to call. I am going to post a message on AVSIM so that others may be spared my experience. It is still very high quality equipment.

Thanks again for your understanding and support,

 

Greg

7 hours ago, Pete Dowson said:

It is as very bad idea indeed to have controllers enabled in P3D and assigned in FSUIPC. Choose one or the other! Assign axes in P3D not in FSUIPC if that's where you want buttons assigned. Otherwise DISABLE controllers altogether in P3D and use FSUIPC exclusively.

Currently you have no buttons assigned in FSUIPC at all, so I can't help you with why they may not function.

BTW, whilst your PFC devices look exactly the same as mine they are completely different. Yours are standard joystick devices, which must be supported by PFC or their retailers. They were wrong referring you to me! I've never had any such devices to test with and they do not use any driver software I provided specifically for PFC devices.

Pete