precision flight controls cirrus ii console tpm FSUIPC 5 - Precision Flight Control Cirrus II console missing files figured out for the throttle body

[richzep]

Pete,

I have updated the latest FSUIPC 5.103 and PFCHID 1.49 / PFChid64 and found everything worked great except the throttle body for my TPM ( Throttle, Prop, Mix ) controls on my PFC cirrus II console USB. They simply did not work at all. My computer sees the throttle body just not FSUIPC 5. After digging all the files and verifying them with P3D v3 version file which worked, I figured out the problem and wanted to share with you and other members. The AXES part of the install was missing in the FSUIPC.ini file in P3D v4 modules folder. You can see it below, you might want to update the FSUIPC 5.103 / PFCHID 1.49 / PFChid64 to include the axes part of the controls. I simply just copied the Axes portion from my P3D v3 modules FSUIPC v4 to the FSUIPC 5 for P3D v4 and now works great.

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

 

Richard

 

Edited July 16, 2017 by richzep

[Pete Dowson]

3 hours ago, richzep said:

The AXES part of the install was missing in the FSUIPC.ini file in P3D v4 modules folder. You can see it below, you might want to update the FSUIPC 5.103 / PFCHID 1.49 / PFChid64 to include the axes part of the controls. I simply just copied the Axes portion from my P3D v3 modules FSUIPC v4 to the FSUIPC 5 for P3D v4 and now works great.

The Axes entries in the INI file are added by you, by going to FSUIPC's Axis assignments tab and assigning as you want. The throttle quadrant assignments are flexible, according to PFC device, and assigned according to the aircraft you are flying.

You must have done that in the past sometime with FSUIPC4 and PFCHid.DLL. Please see this part of the PFCHid user guide:

Quote

 

Setting PFChid options
There are very few options in PFChid. The driver is intended to be used as supplied, with no changes or configuration needed by the user in the module itself.
 

If the device you are using PFChid for includes a PFC throttle quadrant, the one with up to 6 levers and usually with different optional arrangements, then you will need a Registered version of FSUIPC in order to assign these levers to their desired functions and calibrate them for FS use. The best way in FSUIPC is to use its "Profiles" feature, setting up one profile for each configuration you may want. Then different aircraft can be assigned to different profiles, and FSUIPC will automatically take care of the re-assignments of levers as different aircraft are loaded.

 

 

[richzep]

Pete,

thanks for the reply, but FSUIPC 5 did not see the throttle at all in the AXIS tab, so I was forced to copy the file so it can recognize it. In previous versions of FSUIPC I never had to do that it always recognized the throttle body. Just thought it was odd.

Richard

[Thomas Richter]

Hi,

just to confirm I did run a test, no mcro file in use. Only the Cirus II connected as it is with latest FSUIPC5.103j and the PFCHid64.dll (5.01). Make sure you have all latest versions installed/ updated to current versions.

Throttle unit is seen as Controller 17 with axes:

THR_L = X

THR_R = Y

PROP_L = Z

PROP_R = R

MIX_L = U

MIX_R = V

Values are all from -16384 to +16383, so all OK.

Tested with FSUIPC5.103j and PFSCHid5.01

 

  Manufacturer= Precision Flight Controls, Inc.

  Product= PFC Cirrus II Pro

  Vendor=0689, Product=C200

  Serial Number= PFC Cirrus II Pro

       16: ... Ok, added as device #1

     3125: Using macros from "F:\FS\Prepar3D v4\Modules\PFC.mcro" selected

Thomas

[Pete Dowson]

14 hours ago, richzep said:

thanks for the reply, but FSUIPC 5 did not see the throttle at all in the AXIS tab, so I was forced to copy the file so it can recognize it.

I see my colleague Thomas has tested this now, and found it to be okay, and working as it should.

Thanks Thomas!

Pete