ryanf

Thanks Pete for all the support. I can also confirm that the rudder and aileron trim on the Cirrus II console can be enabled through the Trims/Steering Page in your PFC module. thanks, Ryan.

Hi Pete, Actually unplugging would be very easy to do. Regarding removing the module manually - will I loose all my settings? Great! I must have been mislead by the following statement in the user guide: "Also please note that the Rudder Trim knob on the consoles (but not in the cockpit) is a hardware trimming device and only applies to rudders actually connected through the console, not those connected to a Game Port or USB input." So is this incorrect? In any case, I should have checked! Thanks, Ryan.

Hi Pete, just to follow up: That's because I don't want to use the PFC console **every** time I use FSX - so having to un-install/re-install the module every other day would be over-kill in my opinion. I think I might not have explained myself correctly here. What I was trying to say was that based on the behaviour I see in X-Plane, the rudder and aileron trim controls are **not** hard-wired into the aileron and rudder controls but are available to be read separately in software over the interface. So, if this is the case, can your PFC module support this? I will look further into the documentation as you suggest also. Sorry - my answer was vague alright. I am using PFC module version 4.34 for FSX. thanks again, Ryan.

Hi Peter, thanks for the quick reply. Regarding point 1 - if I just leave the console controls centred etc then will that not keep overriding control inputs from other sources? Also, the switches such as ignition, alternator etc. on the console will over-ride settings from other sources. So there is no overall disable option on the PFC module? Regarding point 2 - I'll try programming it using FSUIPC - thanks. Regarding point 3 - the question was not about X-Plane - I was just using it as an example of how the positions of the aileron and rudder trim on the console are available in software so my question was, can this be supported also in your PFC module? I am using the latest version of the PFC module. thanks, Ryan.

Hi Peter, I have a few questions regarding the PFC module for my Cirrus II console running on windows XP and FSX. 1. Is there a way to disable the console if I want to use FSX without it? 2. The Anti-Ice switch on my console does not seem to control the anti-ice systems on the Real Air Simulations B60. Can you advise on what I should do next to investigate it? Should I contact the RAS people first? MAybe find out if there is an offset available? 3. When I run X-Plane with my Cirrus II, I am able to use the aileron and trim (potentiometer) switches i.e. they are visible in software - I am able to view and calibrate their settings from within X-Plane. I think I had previously read in the PFC module documentation that they were purely hardware switches i.e. attenuating/amplifying the signal from the console yoke (and PFC rudder - if attached - which I don't) controls. If this is not the case, can they be supported by the PFC module? thanks, Ryan.

Hi Pete, I don't really know why both programs need to be assigned their own IP address but that is what their manual instructs. I didn't fully understand initially your point about using the localhost IP address - but if I understand correctly now - you mean that if I assign FSXpand (the server part) with the actual IP interface address and then assign the localhost IP address to FSClient (the client part), then it should work..? That would make sense alright. No need to configure a second IP address on the ethernet adapter. In any case, I can follow up with the FSXpand support guys. thanks for your help, Ryan.

Thanks Peter. I add the second IP address on the same interface by clicking the advanced button on the TCP/IP config dialog. This allows me to type in more IP addresses and subnet masks. Apparently, this must be done to allow FSXpand and FSClient to run on the same machine - in which case, they are using FSUIPC (via WideFS) to talk to FSX which is on another machine. Each program must be assigned its own IP address and will not start unless it has them. Thus the localhost IP address is not enough. I have configured Wideclient to use TCP and it addresses the FSX server PC via the hostname. regards, Ryan.

Hi Peter, recently I have been testing FSXpand and in order to run the server and client programs on the same (non FS) computer, I have to add a second IP address on the PC where it runs. However, if I have the second IP address added, Wideclient cannot connect to FSX but when I remove the second IP address again, Wideclient can start. Then, after successfully starting Wideclient, I can add the second IP address again and get FSXpand working. Does Wideclient have a problem with a second IP address on a client machine? thanks, Ryan.

Thanks Pete. The issue here is that I recently installed X-Plane also and the PC I am using in X-plane for the outside view - where I would have to run FS, does not have the PFC hardware connected to it at the moment. I thought there might be a possibility of your driver working with WideFS. thanks, Ryan.

Hi Peter, is there any possibility to connect PFC hardware to a PC which is not running FS but connected to one via the network and running wideclient? thanks, Ryan

Hi Pete, well I did the following: 1. Removed the rudder axis assignments in FS - I thought FS would just ignore it since the FS joysticks were disabled...not the case though...should have read the FSUIPC documentation more carefully! 2. Removed all wind 3. Checked the outside view of the aircraft and saw no rudder deflection. With this testing, everything was working fine - no steering off-course and no brake messages. Then I added wind again and still it worked fine. So I think it was a problem that FS was still processing the brake axes. It's working fine now! Thanks for your help! cheers, Ryan.

Hi Pete, It pulls to the right - I am using a cessna 152 model so the propwash & torque should cause it to pull to the left. I'll double check that. Nice! Why didn't I think of that.....? Will check it thanks! thanks, Ryan.

Hi Pete, thanks for the **very** quick reply! The rudder axis outputs are not zero the whole time - just when I steer straight with the pedals i.e. don't push either pedal. I'll check the FSUIPC & FS (FS9 but not sure exact version) versions and the CH driver and then get back to you. Many thanks, Ryan.

Hi, I am new to this forum - hi to everyone! I am having a problem with my CH Pro rudder pedals and FSUIPC. I recently started using a PFC Cirrus II console but I am using it with my CH PRo rudder pedals. I decided to use FSUIPC exclusively for the rudder axes processing so I disabled joystick support in FS9 and assigned and calibrated the rudder axes in FSUIPC. I saw two problems; firstly, when rolling on the runway, the plane keeps pulling to one side and I have to use a lot of rudder pedal deflection to keep it straight. Yet when I check the FSUIPC axis calibration page, the rudder output is zero and the brake outputs are also zero. I also tested the rudder pedals using the CH PRo software and they seem perfectly calibrated there also. When flying, I don't seem to be out of balance according to the slip indicator so I was unsure if it was a small rudder deflection or a brake problem. However, the brake message does not appear on the FS window. Even if I take my feet off the pedals entirely, I still get the plane pulling to one side. secondly, the brake axes on the rudder seemed very sensitive so I assigned a larger null zone through FSUIPC and what sometimes seems to happen is if I press very lightly on either brake, I get the brake message appearing for less than a second on the FS window before disappearing. I also checked in the FSUIPC calibration window and sure enough, if I do the same thing, the out value momentarily shows a non-zero value before immediately resetting itself back to zero where it should be (since I am still within the null zone). I used to have the rudders axes assigned through FS and did not have this problem before. Any ideas? thanks, Ryan.