FSUIPC - PFC Cirrus II Serial Yoke not working in FSX

[jeffk]

My PFC Cirrus II Yoke is not responding in FSX. With FSUIPC 4.853 installed, the device is recognized over COM1 within FSX. Throttles and switches respond correctly, but the yoke reports a solid '64' in the configuration screen. Throw the hidden switch under throttle panel and the numbers jump to '17' and flicker to '23'.

Some details of the configuration:

Precision Flight Controls Cirrus II Serial Flight Console (w/hidden switch under throttle panel)

Windows 7 64-bit (fresh install)

FSX with Acceleration Pack

Lava PCIe Serial Card - 64 bit driver / tested with known working serial cable

FSUIPC 4.853

pfcfsx.dll

Opening up com1 via putty, I'm able to ascii scroll by as I throw switches and push buttons. The yoke also seems to send data (was trying to ensure it wasn't a hardware failure).

Additional efforts:

I've also tried the ELITEFS serial driver without success (same issue with yoke not working).

My original goal was to get this device working with ASA IP Trainer. ASA provided me with CirrusBATD.dll and it was also unsuccessful.

I'm very encouraged that Pete has gone to the trouble to author and maintain FSUIPC. I'm looking forward to being a registered user and practicing for my IFR rating.

Thank you for your assistance.

[Pete Dowson]

My PFC Cirrus II Yoke is not responding in FSX. With FSUIPC 4.853 installed, the device is recognized over COM1 within FSX.

Er, FSUIPC4 does not support PFC serial devices, and I have no idea how FSX is reading it on COM1 as FS doesn't have any serial port facilities.

PFC serial devices are supported by my PFC modules -- PFC.DLL for FS9 and before and PFCFSX for FSX and later.

Throttles and switches respond correctly, but the yoke reports a solid '64' in the configuration screen. Throw the hidden switch under throttle panel and the numbers jump to '17' and flicker to '23'.

I've no idea where you are looking to see these numbers, sorry. What s the "hidden" switch supposed to be doing?

Some details of the configuration:

....

pfcfsx.dll

Ah, NOW you mention PFCFSX. So are you enabling the yoke and calibrating in PFCFSX as instructed? Have you referred to the user instructions at all? Why are you only referring to FSUIPC, which doesn't include PFC serial support except via the PFC drivers?

The PFC DLLs have test modes for checking the switches as well. I suggest you refer to the user guide. If you want more help, be sure to mention the version number of PFCFSX too. You might want to check that it is up to date -- see Download Links subforum.

Have you considered PFC support, as really it is their business?

Regards

Pete

[jeffk]

Hi Pete, Thanks for your prompt response.

I loaded FSUIPC4 to create a modules folder for fsx in which to place PFCFSX.dll as per the user instructions. I have read the complete user instructions before posting as I didn't wish to be one of 'those people'.

"For FSX, you must install FSUIPC4 first if you‘ve not already done so. The FSUIPC4 installer will create a Modules folder, and it is onto that folder you then must copy the PFCFSX.DLL."

This is the version of pfcdll I downloaded from http://www.schiratti.com/dowson.html

PFC DLL 2.40

includes

4.40 for FSX

My understanding of the hidden switch under the throttle quadrant is to change protocols from Elite to PFC. I don't have the historical knowledge to comment further on Elite vs PFC.

The numbers I'm referring to are from the pfcdll calibration screen.

When the switch is in the Elite mode, the input values for the aileron and elevator jitter between 0, 17 and 23.

When the switch is in PFC mode, the input values for the aileron and elevator stay locked at 64 (I'm assuming this is a 0 to 127 scale and they're reporting they're in the middle).

I have unchecked boxes other than the two I'm trying to isolate and only have aileron and elevator selected.

I'm happy to pay PFC for support. I've phoned and emailed them without a response. I'll try again.

Thank for writing comprehensive documentation. I was pleased to see 49 pages of detailed explanation when the industry standard is terse by comparison.

Jeff

[Pete Dowson]

I loaded FSUIPC4 to create a modules folder for fsx in which to place PFCFSX.dll as per the user instructions. I have read the complete user instructions before posting ...

Ah, okay. Good. In fact FSUIPC is not there just to create the folder, it is actually the interface into FS used by all my other modules, so it is needed. With PFCFSX.DLL also installed and configured it can actually also be used for FS axis assignment and calibration, and for switch assignments too. But generally it is best to do this in the PFC module itself.

My understanding of the hidden switch under the throttle quadrant is to change protocols from Elite to PFC. I don't have the historical knowledge to comment further on Elite vs PFC.

Ah, yes. I remember that the older versions were "dual protocol".

The numbers I'm referring to are from the pfcdll calibration screen.

Okay. That's the information I needed.

When the switch is in the Elite mode, the input values for the aileron and elevator jitter between 0, 17 and 23.

I'm surprised there are any numbers. The Elite protocol is rather different and PFCFSX doesn't understand it. You are probably seeing rubbish interpretations of stuff arriving, that is all.

When the switch is in PFC mode, the input values for the aileron and elevator stay locked at 64 (I'm assuming this is a 0 to 127 scale and they're reporting they're in the middle).

Yes, 64 would be pretty central, though not many actual units would be so accurately set. It sounds like something is wrong with the wiring or the pots themselves. Have you checked the "Test" tab in the PFC driver -- it should recognise and decode the rockers and buttons on the yoke.

Check also that the port speed is correct. I don't know if the default for PFCFSX was always applicable to all models. There will be a line to configure that in the PFCFSX.INI file. Normally 9600 I think, but also try 4800 and 19200.

When you say "Opening up com1 via putty,...", is that some sort of Port monitor? If so, can it display hex values as well as ASCII (there's no ASCII in either the PFC or Elite protocols). If so, show me what you get on COM1 for the axes.

PFCFSX's test mode will give you the hex values as well as the decode. There s also a wealth of logging functions in PFCFSX.DLL which can help us understand what is going on. See the options bottom left on the "Test" tab.

I'm happy to pay PFC for support. I've phoned and emailed them without a response. I'll try again.

Hmm. There used to be a Support Forum, but I can't see any sign of it now. Contact with their Tech Support is difficult -- even for a PFC developer like me. My emails get answered, eventually, but it can take a week or two. They aren't a large company despite their extensive range of quality (and expensive!) products, and the limited number of staff are always busy and often off-site doing installation work and so on. However, you should always be able to get through on the 'phone to someone, even if they can't help directly. At least they could put you on a list.

Good luck,

Pete

[jeffk]

Success. I did receive a response from PFC and their suggestion worked.

Risking public embarrasment, I will share their feedback so as to help future users.

"When you tested the unit with ASA and FSX did you have your battery master on? If not make sure that it is on, on the earlier version of our systems the battery master needs to be in the on position for the elevator and aileron to work properly. "

I moved the system to a quiet room and can now hear the hobbs meter ticking over when the battery master switch is on. My earily testing had the switch on, but I had software configuration issues. I didn't feel overly clever when I read PFC's note and realized I had overlooked this issue (now that my software install was correctly sorted). As expected, the protocal switch has to be in the PFC (to the right) position.

Pete, thank you for your trouble shooting assistance. I am now a registered owner of a FSUIPC license.