PFChid64 Addon doesn't open in P3Dv4

[Gerd]

Hello Pete or John,

with the new FSUIPC6 I couldn't get a GUI surface of PFChid64 USB-Trottle control.
When I click on PFChid64 Addon within the sim (picture 1) I receive the same information message as with FSUIPC5 (picture 2).
The FSUIPC6.log file shows a correct loading of the .dll file.
But the PFChid64.log reports missing PFC.mcro files. Why are they missing?
And there are other errors 6 reported -
Could you find out a way to let it work correctly?
The installation proceeded with the Add-on.xml method (see picture 3).

Regards
Gerd

 

[Gerd]

... I had only 20kB total size for attachments in my first post above. Otherwise I got an error message. 20kB only? Is that correct?

For this postI have only 468B max total size, so that I can't drag anything here. What's going wrong now?

Regards

Gerd

[Gerd]

o. k. delete Tab and call back: 4.99 MB! Why not immedately -

 

FSUIPC6.log PFChid64.log

[John Dowson]

26 minutes ago, Gerd said:

with the new FSUIPC6 I couldn't get a GUI surface of PFChid64 USB-Trottle control.

Sorry, what does this mean?

27 minutes ago, Gerd said:

But the PFChid64.log reports missing PFC.mcro files. Why are they missing?

You can ignore that message. You can add a PFC.mcro file to override the default controls/events that are assigned to PFC devices - see the provided documentation for details.

31 minutes ago, Gerd said:

When I click on PFChid64 Addon within the sim (picture 1) I receive the same information message as with FSUIPC5 (picture 2).

Of course - you are using the same PFChid64.dll...there is no difference in the handling of PFC devices in FSUIPC5 and FSUIPC6.

Your PFChid64.log file does show these errors:
 

Quote

        0: Error 6 [00000006] returned on HidD_GetAttributes:  (\\?\hid#irdevicev2&col06#2&2818a073&0&0005#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd)
...
        0: Error 6 [00000006] returned on HidD_GetAttributes:  (\\?\hid#irdevicev2&col07#2&2818a073&0&0006#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd)
        0: Error 6 [00000006] returned on HidD_GetAttributes:  (\\?\hid#vid_046d&pid_c317&mi_00#7&7dc58f9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd)
        0: Error 6 [00000006] returned on HidD_GetAttributes:  (\\?\hid#irdevicev2&col05#2&2818a073&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd)
        0: Error 6 [00000006] returned on HidD_GetAttributes:  (\\?\hid#irdevicev2&col08#2&2818a073&0&0007#{4d1e55b2-f16f-11cf-88cb-001111000030})

which is probably your issue. Not sure what can be causing those - I will take a look, but tomorrow now. In the mean-time, please reboot and try again...
Does it still work with FSUIPC5?

John

[John Dowson]

Those errors are nothing to worry about - your PFC Throttle is detected and should be ok to use - what exactly is your issue?

Note that the PFChid64.dll was also updated at the end of January so you should update this. The update was for PFC avionics stacks when using MSFS, so should not really affect you, but always a good idea to use the latest version if needing support.

John

[Gerd]

With the current PFChid64.dll V5.143 the throttle levers don't work either.

Sorry, if I couldn't express my issue clearly enough, but with GUI (Graphical User Interface) I expected something similar as for the PFCcom unit used to choose the desired lever units and do the calibration, not only an information window.

issue: The buttons work, but the levers have no effect on the aircraft.
To ask in one sentence: How can I control and calibrate them?

Gerd

[Gerd]

Remark:
with buttons I mean the flaps- and gearswitch and rudder rotaryknob.
The rotaryknob only moves the blue triangle in the G1000 MFD RUDDER TRIM, but I can't notice anything in moving either the rudder or the pedals. Is that intended?

[John Dowson]

11 hours ago, Gerd said:

but with GUI (Graphical User Interface) I expected something similar as for the PFCcom unit used to choose the desired lever units and do the calibration, not only an information window.

There is no GUI with the PFC hid driver - please see the documentation included with the driver (PFChidDLL User Guide.pdf).

11 hours ago, Gerd said:

the levers have no effect on the aircraft.
To ask in one sentence: How can I control and calibrate them?

I can't notice anything in moving either the rudder or the pedals. Is that intended?

I am not sure how axes are handled with the driver - check to se if you can see them in FSUIPC's axes assignment tab, and if so, assign and calibrate there.
According to the log you originally posted, a PFC throttle quadrant was acquired so that should be assignable, but no PFC rudder - only CH Pro pedals.

[Gerd]

On 2/9/2023 at 10:01 AM, John Dowson said:

There is no GUI with the PFC hid driver - please see the documentation included with the driver (PFChidDLL User Guide.pdf).

Well thanks! I discoved it in the note "There is a menu entry in FS for PFChid (in the Modules or Add-ons menu), but this is merely to confirm that the driver is correctly loaded, and to provide Version information."

[Gerd]

On 2/9/2023 at 10:01 AM, John Dowson said:

I am not sure how axes are handled with the driver - check to se if you can see them in FSUIPC's axes assignment tab, and if so, assign and calibrate there.

Well, in the Options Control menue nothing is moving, when I try to calibrate a lever ...

[Gerd]

... but in the FSUIPC's axes assignment tab the In- and Out-field data are moving, when I move lever 1,
but only lever 1. The other 5 don't trigger anything.

[Gerd]

Let me try to read and play a bit. I find something to read in FSUIPC User Guide.pdf page 35.
Or have you something else to recommend?

 

[John Dowson]

You have to assign in FSUIPC, not P3D, if using the FSUIPC PFC drivers.

6 minutes ago, Gerd said:

The other 5 don't trigger anything.

Did you click Rescan before moving another axes? Once one axes detected, you have to click the Rescan button to detect another. If the same axes keeps showing, you can also click the Ignore Axes button to ignore that for the rest of the session (i.e. while the Axes assignment dialog box is still open).

[Gerd]

o. k. thanks John, that worked.

I could create two Profiles and Axes in FSUIPC6_20230216.ini, one "Single Enging HP", the other one called "Jet Two-engine".
The type of action I assigned to “Send direct to FSUIPC calibration”.
The funcionality switches correctly between both Profiles when aircraft are changed.
But the "Jet Two-engine" Profile will still have to be modified  for
- 390 Premier IA to get the Cut-Off area of the throttles activated
- Hawker 850XP to get the DUMP area of the spoilers to be activated; further more they are in reverse function, which has to be changed as well.

But I think, I'm on the right way -

FSUIPC6_20230216.ini

[John Dowson]

10 hours ago, Gerd said:

But the "Jet Two-engine" Profile will still have to be modified  for
- 390 Premier IA to get the Cut-Off area of the throttles activated
- Hawker 850XP to get the DUMP area of the spoilers to be activated; further more they are in reverse function, which has to be changed as well.

Or maybe create a new profile for each of those, based upon your "Jet Two-engine" profile, as needed. 

You can reverse your spoilers in the spoiler calibration section, on page 6 of the calibration tab. For the DUMP area, you can use the right-hand side of the axes assignment tab, to send the appropriate control(s) when entering and/or leaving the DUMP area.

 

[Gerd]

On 2/16/2023 at 11:14 AM, John Dowson said:

Or maybe create a new profile for each of those, based upon your "Jet Two-engine" profile, as needed. 

Well, I followed your proposal to be more flexible in programming (see .ini-File).

FSUIPC6_20230223_2.ini

[Gerd]

On 2/16/2023 at 11:14 AM, John Dowson said:

You can reverse your spoilers in the spoiler calibration section, on page 6 of the calibration tab.

That was successful as well, thanks!

[Gerd]

On 2/16/2023 at 11:14 AM, John Dowson said:

For the DUMP area, you can use the right-hand side of the axes assignment tab, to send the appropriate control(s) when entering and/or leaving the DUMP area.

For the 390 Premier IA I could create a 390_Spoiler_Dump.mcro and assigned it to a joystick button, which works (see picture FSUIPC Spoiler Button Control 3.PNG)
Compared with the spoiler switch it activates all 4 levers and moves them faster than the switch spoiler, which activates only the two outer levers.
To do the same with only the switch spoiler I renamed the command to "L:ASD_390_LEVER_SPOILER=Toggle", but it didn't work, because I doesn't seem to be the correct one for that switch (see picture 390 Switch spoiler.PNG).
Do you have any idea, where I can find that name?

[Gerd]

On 2/16/2023 at 11:14 AM, John Dowson said:

For the DUMP area, you can use the right-hand side of the axes assignment tab, to send the appropriate control(s) when entering and/or leaving the DUMP area.

Unfortunately the axes assignment, to move it by the throttle lever, as you recommended, was not successful (see picture FSUIPC Spoiler Button Control 2b.PNG).
Nothing changes. Do you have any idea what has to be changed?

[John Dowson]

10 hours ago, Gerd said:

Do you have any idea, where I can find that name?

To determine how to operate a switch, do the following:
   - first, see if there is a standard event/control that you can use. To do this, activate logging for Events (non-axis controls) and open the logging console window. Then flip the switch in the UI and see if any event is logged - if so, you can use that.
  - if there is no standard event/control,. list the lvars and see if anything looks appropriate. Then flip the switch and list the lvars again to see if the lvar you have identified changes value. If so, you can use that.

I can't really help you any further as I don't have the 390 Premier IA.

10 hours ago, Gerd said:

Unfortunately the axes assignment, to move it by the throttle lever, as you recommended, was not successful (see picture FSUIPC Spoiler Button Control 2b.PNG).
Nothing changes. Do you have any idea what has to be changed?

Well, if that assignment doesn't work when assigned to a switch, it won't work when sent when using an axis range. Note also that the range for the action you assigned is 0-0, You should really set a wider range for this (using the From and To buttons).

Also please note that these questions have nothing to do with the title of this topic - 'PFChid64 Addon doesn't open in P3Dv4'. Please don't continually use the same topic for different issues. Create a new appropriately titled topic (also with the aircraft you are using)  - you may then get assistance from others who own this aircraft.

John

[Gerd]

On 2/23/2023 at 12:02 PM, John Dowson said:

To determine how to operate a switch, do the following:
   - first, see if there is a standard event/control that you can use. To do this, activate logging for Events (non-axis controls) and open the logging console window. Then flip the switch in the UI and see if any event is logged - if so, you can use that.

Thanks for your response and your advice to open a new thread.
The logging told me the event "SPOILERS ON" and "SPOILERS OFF", which seem to be standard ones, but I wasn't successful to assign them to buttons.
I found the Making a FSUIPC Macro (Tutorial) on avsim, which uses exacly that spoiler theme.
Thus I'll follow there and continue posting there, when I'm not successful or will come back with a new thread.

Gerd

[John Dowson]

6 minutes ago, Gerd said:

Thanks for your response and your advice to open a new thread.

Which you didn't follow...no new thread!

7 minutes ago, Gerd said:

The logging told me the event "SPOILERS ON" and "SPOILERS OFF", which seem to be standard ones, but I wasn't successful to assign them to buttons.

Presume you mean they didn't work...

8 minutes ago, Gerd said:

I found the Making a FSUIPC Macro (Tutorial) on avsim, which uses exacly that spoiler theme.

Ok. But it seems you already have a macro for this, so just assign that to a button or key to test if its working.

11 minutes ago, Gerd said:

Thus I'll follow there and continue posting there, when I'm not successful or will come back with a new thread.

Ok.

John