PFC Cirrus II USB is not working properly on MSFS2020 or 2024.

[mac8892fs]

*** Moved to FSUIPC7 support sub-forum ***

Hi

I used FSUIPC all the time back in the FSX days. I think it has very good functions.
I think that made my SIM experience the best I had at that time.
I stopped using flight simulators for 10 years, but I started flight SIM again with MSFS. I kept the PFC device all the time.

However, I'm currently having a problem.

MSFS is quite different from the SIM I know, such as the fact that it is operated through Steam. Also, I feel that the knowledge to operate it properly is outdated if I only have old memories.

Specifically, it includes the following:
Yesterday, I tried to use PFC Cirrus II USB with MSFS 2020 and 2024, but it didn't work.I read on other forums that PFC Cirrus II USB works properly. It was for MSFS2020.At this time, I couldn't find any information on PFC Cirrus II USB on MSFS2024. Maybe no one has tried it with MSFS2024.

But in my case, it doesn't work well with either MSFS2020 or 2024.
This is true whether I use FSUIPC7 or the default settings of MSFS.

These MSFS are the Steam versions.
Also, in the FSUIPC7 log and ini file, there are places where "Product = PFC Cirrus II" is written, so it seems to be recognized.

It is also recognized in MSFS Devicesetting, but when I try to assign ASSIGN, nothing happens.
I tried various things but couldn't solve the problem, so I decided to post on the forum to get your help.

PFCDLL is located in the FSUIPC7 folder, at "C:\FSUIPC7\PFCDLL".

Furthermore, operation tests using PFCTestGUI work without any problems.

For now, I can use the SIM by using the CH Products York and a game controller borrowed from my son, but the PFC device is necessary for me.

I have uploaded the FSUIPC7 "Log" file.
If necessary, I will also upload the "ini" file.

FSUIPC7_prev s.logFetching info...

Edited May 6 by John Dowson
Moved to FSUIPC7 support forum

[John Dowson]

I have moved your post to the FSUIPC7 support sub-forum, Please use this forum for all questions/issues with FSUIPC7 and MSFS2020/MSFS2024.

  On 5/6/2025 at 2:48 PM, mac8892fs said:

PFCDLL is located in the FSUIPC7 folder, at "C:\FSUIPC7\PFCDLL".

Expand  

For newer PFC HID devices, you do not need any additional software. You should be able to assign directly  using FSUIPC's assignment panels.

However, I think the PFC Cirrus II Pro is a non-Joystick type of HID device.  If so you'd need to install the PFChid64.dll. You will not see the PFC menu in the Add-ons menu until FSUIPC7 is connected to MSFS and you may even need an aircraft loaded and ready-to-fly.

The log file you attached shows that MSFS wasn't even running.

See this thread/comment and later: 

 

[mac8892fs]

Hi John.
Thank you for your kindness.
I'll read the thread you provided and try again tomorrow night after work!

Yes, you're right, the log file I sent earlier was not starting MSFS. I should have sent the correct one, but the symptoms were the same, so I sent this one.

I read your explanation and learned how to solve the problem.
I realized that the file I was using was for the serial port.

I'll let you know again when it works.

[mac8892fs]

Thank you for yesterday!
I tried it today.

In conclusion, the ailerons are working.
The flaps are working.
The light system is mostly fine.
The battery master and alternator have a problem with ASSIGN, but they are working. The avionics master is assigned to the right of the alternator.
The parking brake is working properly.

The problem is the trim. The trim works, but if you press it a little, it suddenly changes a lot. One push of it makes 10 units, and if you press it for a long time, it suddenly reaches the maximum.

I tried adjusting it with sets and curves, but it didn't work.
I also couldn't assign the throttle or mixture.

I read all the threads you linked to.

My model seems to be an old USB type, so I think I should use a combination of FSUIPC7 and PFChid64.dll.

There is only server in the add-ons, and PFC is not displayed.
I found PFChid64.log, so I checked it, but it showed many errors like Macros not found: "C:\FSUIPC7\PFC.mcro".
Is there somewhere I can download this from?
I will also upload the log of this test.

Note that the Ch product is also running at the same time during operation testing.
I plan to remove this when actually using it. However, at the moment the throttle isn't working, so I am running this as well.

These are my experiences on MSFS2024. I have not tried 2020.

FSUIPC7_prev 0507.logFetching info...

[John Dowson]

  On 5/7/2025 at 2:43 PM, mac8892fs said:

My model seems to be an old USB type, so I think I should use a combination of FSUIPC7 and PFChid64.dll.

Expand  

Nothing was working before you installed that (was it?), so you mustbe using the old USB-type model and so that is needed.

  On 5/7/2025 at 2:43 PM, mac8892fs said:

There is only server in the add-ons, and PFC is not displayed.

Expand  

That is not really an issue, as the menu entry would only display the PFC driver version number anyway. Not sure why that is no longer added though. This menu entry used to go on the P3D/FSX add-ons menu, and it may not have been updated to go to the FSUIPC7 add-ons menu.

  On 5/7/2025 at 2:43 PM, mac8892fs said:

I found PFChid64.log, so I checked it, but it showed many errors like Macros not found: "C:\FSUIPC7\PFC.mcro".

Expand  

That is not really an error - you add this file to override the default assignments.

  On 5/7/2025 at 2:43 PM, mac8892fs said:

The problem is the trim. The trim works, but if you press it a little, it suddenly changes a lot. One push of it makes 10 units, and if you press it for a long time, it suddenly reaches the maximum.

I tried adjusting it with sets and curves, but it didn't work.
I also couldn't assign the throttle or mixture.

Expand  

You need to read the documentation that comes with the driver -  the PFChidDLL User Guide and take a look at the PFCmacroIndex csv file
If things are not working correctly with the default assignments, you can create macros (in the PFC.mcro file) to override the default assignments. You can use logging in FSUIPC7 as well as in the PFC driver (as well as the PFCmacroIndex file) to determine what macro can be used for each switch (and maybe axis, but I am not sure).

Many aircraft in MSFS2020/MSFS2024 do not respond to the standard FS controls which will be the ones used by the default assignments. They can use things like lvars, hvars, input events or custom controls instead of the default FS controls, and can be specific to the aircraft being used. For these, you will need to determine how they work and override them by providing a macro entry.

For the trim, you can use FSUIPC/PFC logging to see what is being sent, and can also override the default assignments with your own macro.

You can also maybe see if there are any other PFC users with the same console in the FSUIPC7 sub-forum and maybe ask them (either via a message or tag them in an existing post).

Your log file does show a few issues:
    1. There were a few reconnection attempts (and one looks forced for some reason). You should tune the start-up parameters (or let FSUIPC auto-tune these). See the Advanced User guide and/or the FAQ entry (in the FAQ section of these forums) on this
    2. The WebSocketServer is being started - disable this unless you are using it.
    3. You have not installed the FSUIPC WASM module. This is not a problem, but you need this if you want to use lvars, hvars, or presets (which are useful for pretty much all aircraft),
        Install this unless you really have no need/intention of using these.

Sorry, but other than that I can't really help any further with PFC products. I don't have any and have never used them myself. The driver is pretty old now (way before my time!) and is provided as-is and is not really supported any more (by me!). You can also try PFC support.

Good luck!

John

[mac8892fs]

Hi John.

Thank you so much for your kindness.

You have provided so much information and it has been very helpful.

I would like to use your information to dig a little deeper and learn more about each of these topics.

[mac8892fs]

Hi John.

First, I'd like to thank you.

I've successfully assigned the throttle, props, and mixture.So, at a minimum, I can fly using PFC.

I still feel like the macro assignments aren't working properly.

There are several types:
1. Like trim issues, the assignments are correct, but there are problems with operation.
2. FSUIPC7 doesn't respond when I operate the switches.
This is all about the buttons and switches.
The switches and buttons that are working now seem to have been assigned automatically, and they are working without any problems.

They are the lights, magneto, parking brake, etc.
Also, there are some parts where the ASSIGN of some switches is inconsistent.

But this is just a report.

I'm going to dig deeper to find a solution tomorrow.

 

[John Dowson]

  On 5/9/2025 at 5:07 PM, mac8892fs said:

1. Like trim issues, the assignments are correct, but there are problems with operation.

Expand  

As I said, you need to use logging to see what is being sent, and also operate in the VC to see what should be sent, then update the assignment accordingly.

  On 5/9/2025 at 5:07 PM, mac8892fs said:

2. FSUIPC7 doesn't respond when I operate the switches.

Expand  

Not sure what this means....You won't see the buttons/switches in the assignment panel - I don't think it works like that for your device. The switches trigger a macro. There are default macros for most switches/buttons, but these may not work for many aircraft in MSFS2020/MSFS2024. That is why you can override the default macro and provide your own. This is all described in the PFChid User guide documentation - did you read that?

  On 5/9/2025 at 5:07 PM, mac8892fs said:

The switches and buttons that are working now seem to have been assigned automatically, and they are working without any problems.

Expand  

Yes - they will be using the default/inbuilt macros.

Please read the documentation provided with the PFChid64 driver dll.

[mac8892fs]

Hi John.

Thanks. I've almost solved the trim problem.

By editing the TrimRange value in the manual, it is no longer as sensitive as before.

Specifically, I set [Config]TrimRange=16 in PFChid64.ini.

Even at 16, it is still a little sensitive, but any value below this is automatically set to 16. Is there a way to make it a little smaller?

I haven't tried the PFC macro yet. I'm reading the manual over and over again to understand it better.

I really appreciate your support.

[John Dowson]

  On 5/11/2025 at 8:38 AM, mac8892fs said:

I've almost solved the trim problem.

By editing the TrimRange value in the manual, it is no longer as sensitive as before.

Specifically, I set [Config]TrimRange=16 in PFChid64.ini.

Even at 16, it is still a little sensitive, but any value below this is automatically set to 16. Is there a way to make it a little smaller?

Expand  

No there won't be. But I am surprised that is solving your issue, as the documentation states:

  Quote

A smaller value here will give faster adjustment when turning the wheel (or using an electric trim switch which operates by turning the wheel). A larger value will make it less sensitive and require more turns for the same trim adjustment.

Expand  

So you should need a larger value to make it less sensitive, not a smaller value.
If the trim wheel is using a macro, you could provide your own to override the default behavior, as for any other buttons/switches that don't work, or need to be made aircraft specific in their assignments.

  On 5/11/2025 at 8:38 AM, mac8892fs said:

I haven't tried the PFC macro yet. I'm reading the manual over and over again to understand it better.

Expand  

You also need to read up on how macros work in the FSUIPC7 Advanced User guide (page 36). You can log the macro name used for each button/switch by setting LogMacroNames=Yes in the [Debug] section of your PFChid.ini file. You can then create a macro with the logged name in the PFC.mcro file and this will then override the default behavior of the button/switch that uses that macro name.

John
 

[mac8892fs]

  On 5/11/2025 at 9:51 AM, John Dowson said:

No there won't be. But I am surprised that is solving your issue, as the documentation states:

So you should need a larger value to make it less sensitive, not a smaller value.
If the trim wheel is using a macro, you could provide your own to override the default behavior, as for any other buttons/switches that don't work, or need to be made aircraft specific in their assignments.

You also need to read up on how macros work in the FSUIPC7 Advanced User guide (page 36). You can log the macro name used for each button/switch by setting LogMacroNames=Yes in the [Debug] section of your PFChid.ini file. You can then create a macro with the logged name in the PFC.mcro file and this will then override the default behavior of the button/switch that uses that macro name.

John
 

Expand  

Hi John. I tried to change the settings as described above, but the elevator trim switch on the PFC yoke was not this way.

It seems that this is the case in FSUIPC7 250515.ini: ElevatorTrim=1024/-16383,1024/16383.

I change the settings but I don't see any change.

What would be the correct way to edit this value to slow down the elevator trim?

I also use Go-Flight Devices, and they all work fine.

I am once again reminded of the wonderful functions of FSUIPC.

I really want to say thank you.

The method you showed me above works fine with the elevator trim assigned to Go-Flight.

FSUIPC7 250515.iniFetching info... FSUIPC7 250515.logFetching info... PFChid64 250515.iniFetching info... PFChid64 250515.logFetching info...

[mac8892fs]

Just to add, all the switches except for the elevator trim now work properly.

I would say my problem is already 90% solved.

Thank you so much.

I'm really grateful.

[John Dowson]

I can't tell anything by looking at your files as I have no idea when you tried to operate the trim/ When you operate the elevator trim, what macro name do you see logged in the PFChid64.log file? What controls do you see logged in the FSUIPC6.log file? Note that you need to activate logging for Events (non-axis controls), which it looks like you haven't done. Also, open the logging console and you will be able to see what is logged when you activate the trim.
 

  On 5/16/2025 at 1:00 AM, mac8892fs said:

It seems that this is the case in FSUIPC7 250515.ini: ElevatorTrim=1024/-16383,1024/16383.

I change the settings but I don't see any change.

Expand  

That is the calibration used when the elevator trim is assigned to an axis in FSUIPC and is probably not used. Those values look very strange anyway (and the format is wrong) so I would remove that. You would normally calibrate the elevator trim on page 6 of the calibration screens and not modify the ini entry directly. But this only applies to the elevator trim axis.
Does your device have a trim wheel or buttons/a rocker? If a wheel, does this use buttons or is it an axis? 

[mac8892fs]

Hi John.

Thank you. Yes, as you said, it is automatically assigned to the 6th position. Therefore, it is assigned to the axis and is working correctly.
I also reset this 6th value to the standard value.

By the way, changing this value did not change the operation speed.

The value fluctuates by 128.
This is logged by 128, so the operation seems to be correct.
However, the speed is fast. I felt that it was beyond the range of FSUIPC adjustment.

This may be due to the fast physical speed of the PCF elevator trim (yoke) switch itself.

If so, I may need to change this switch itself to something else.

Thank you for everything.

 

Below are the values.

AXIS: Cntrl= 65706 (0x000100aa), Param= 5819 (0x000016bb) ELEVATOR_TRIM_SET

Throttle1=-16380,-256,256,16380/32

[John Dowson]

  On 5/18/2025 at 4:12 AM, mac8892fs said:

Thank you. Yes, as you said, it is automatically assigned to the 6th position. Therefore, it is assigned to the axis and is working correctly.
I also reset this 6th value to the standard value.

Expand  

Ok, so you can see the values change in the elevator trim calibration panel? That is interesting, but I wonder what, if any, macro it is using. I would expect it to use PitchTrim, but I can only see PitchTrimMust logged, and only once. I am not sure what that macro should be doing (if provided), so I don't really understand how itis controlling the pitch/elevator trim.
Maybe setting LogIPCwrites to Yes in the PFC ini would help.

  On 5/18/2025 at 4:12 AM, mac8892fs said:

The value fluctuates by 128.
This is logged by 128, so the operation seems to be correct.
However, the speed is fast. I felt that it was beyond the range of FSUIPC adjustment.

Expand  

128 would be the delta adjustment, i.e. it won't move for smaller adjustments. Changing this won't affect the speed of the trim adjustments, just the steps/deltas (i.e. the size of the increment/decrement.

  On 5/18/2025 at 4:12 AM, mac8892fs said:

Below are the values.

AXIS: Cntrl= 65706 (0x000100aa), Param= 5819 (0x000016bb) ELEVATOR_TRIM_SET

Throttle1=-16380,-256,256,16380/32

Expand  

But that is the throttle calibration. not the elevator trim calibration.

If the elevator trim is being calibrated, one way of slowing down the trim movement is to extend the upper range. So, if this is my elevator trim calibration:
    ElevatorTrim=-16383,0,0,16254/16
I would extend the upper range by increasing the upper threshold, e.g
    ElevatorTrim=-16383,0,0,20254/16

(or extend in both directions, and maybe add a null-zone for zero trim, i.e.
    ElevatorTrim=-20383,-512,512,20254/16

)
However, the problem with doing this is that you would lose the full range, and it won't be possible to get to full trim (as you axis would need to send a value of 20254 to do this in the example above).
 

Does the TrimRange setting have much affect? I see this is now set very high (1023), whereas before you had it set very low (16).

[mac8892fs]

Thank you for your reply.

I am not using macros at the moment.

The path to the macro file and the macro file exist, but nothing has been set.

I will write a report on this problem below.

For now, I have chosen a different solution.

I have a Leo Bodnar Electronics BU0836X. I used this board in the past, but I remembered it, so I dug it out in the warehouse.

When I connected this interface to the current system, it was displayed in the Device section of MSFS2024, and I was able to confirm that it could be used.

So, I wired it from the trim switch of the PFC yoke and connected it to it.

I used a connector between them, so I can easily return it to its original state at any time.

I used solder and a glue gun to get it done. I think it worked well.

As a result, I was able to operate the trim without any problems in normal use.

Other than the trim, the PFC system can be used without any problems thanks to the FSUIPC, so I am very grateful for this product.

For the time being, I will operate it using the method using the BU0836X of Leo Bodnar Electronics, but I would like to try the method you proposed when I have time.