J.C.

Oh ok, In other words, the "heading" mode of the autopilot is normally used for flying the arc? Thanks, just wanted to make sure I wasn't missing anything. Regards, Jermaine Clarke Nassau, Bahamas

Hello, I purchased the Ejet from simmarket a few weeks ago (order # 1282761). Very nice aircraft, and flies very well across the board. However, I do have an issue that I need some assistance with. The ejet is not following the DME arc procedure as programmed in the FMS. I've done a few flights in the Caribbean (where DME arcs are typically a part of the SID/STAR procedures) and in all instances, I've had to follow the arc manually in "heading" mode since LNAV won't follow the procedure, even though the FMS is set up correctly. I'm using the ejet version 2, FS9.1, and windows 7 64-bit. I've checked and doubled checked the manual to make sure I'm not missing anything, Can someone please assist with this issue. Thanks and best regards. Jermaine Clarke Nassau, Bahamas

It worked! Thanks Pete, you're a genius Regards, Jermaine Clarke Nassau, Bahamas

Ok, thanks Jermaine Clarke Nassau, Bahamas

Hello Pete, I've recently purchased the feelthere ERJ series aircraft, and for the most part, it works pretty well with my PFC equipment (Cirrus Beech Yoke and turboprop throttle quandrant). However, I'm noticing that the reverse thrust is not working with the ERJ (the only way I can activate the reverse thrust is by constantly pressing F2). I've posted on the feelthere forums, but have yet to get a reply. Can you provide some assistance with resolving this issue please. I'm using FS9.1 and version 2 of the feelthere ERJ (Windows 7 64 bit is my OS). Jermaine Clarke Nassau, Bahamas

Hi Pete, No, my previous system was Windows Xp professional (32 bit). Interesting, I'll try your suggestion (such a pity ,though, since I really love Windows 7 so far :)) Thanks, J.C.

Good day and Happy New Year!, I recently acquired a new system (Alienware Aurora_R2, equipped with Intel i5 CPU 760@2.8Ghz, 6 GB Ram, Windows 7 64 Bit). I re-installed FS9, along with all FSUIPC (version 3.98), and PFC dll (version 2.307). I'm using the Cirrus Beech yoke, throttle quandrant (King Air throttles), and yoke assembly, connected to the PC via a serial to USB converter(with the appropriate drivers installed). I had the same set-up installed on my previous PC with no issues. However, I'm experiencing intermittent issues whereby the controls and quandrant would suddenly stop responding to my inputs, and move on their own. (the movements are erratic, and can be seen externally(control surfaces) and inside the cockpit when the throttle quadrant window is opened). As I said earlier, this only happens every so often, and, since it happened this morning, I decided to record the PFC and FSUIPC log. Additionally, I disconnected the throttle quandrant to see if it would make a difference, but, it still happened.(Note: Before this latest event, I reinstalled FSUIPC and PFC dlls to see if that would make a difference also). As the log files are pretty big, can you tell me which info from the logs would be helpful in assisting you with determining the cause. Your assistance would be greatly appreciated. Thanks in advance. J.C.

Thanks Pete! I'll proceed as instructed, hopefully all goes well :) Thanks again J.C.

Good morning, I recently installed FSX on my system (after years of faithful service from FS9). Now comes the challenge, re-installing my PFC drivers and FSUIPC. I have updated FSX to SP2( including downloading the SDK updates as well). I installed the latest PFC and FSUIPC(unregistered) dlls in the FSX modules folders. However,when I rebooted FSX, hoping to see the familiar modules tab as in FS9 (pressing the Alt key), no luck. After further research, it appears that i need the simconnect DLL (I found it in the SDK updates), and, as per the instructions, I installed it in the same root file that contains the FSX.cfg file. However, I'm still not seeing the "add-on" tab that apparently contains the FSUIPC and PFC modules to allow setting up the PFC equipment for use in FSX. Can you provide some further assistance please (FSX is gonna take some getting used to obviously, even for this seasoned simmer). Thanks in advance. (BTW, I'm using windows7). J.C. (MYNN)

Hi Pete, It seems like the serial port was the cause of my problems all along :) I purchased a serial to USB adapter, and, viola, no more issues. Thanks much for all your assistance. Regards Jermaine Clarke Nassau Bahamas

Hi Pete, I'm using Windows Xp Professional edition (service pack 3 installed). Yes, I'm using onboard sound, but, as I alluded to in my post, I tested with the sound off and it still produces the same results( with engines started). I have just assigned a hot key in FSUIPC for restarting the PFC driver, and, when I've lost response, pressing my hotkey(A on the keyboard), immediately restores control response. I tested this for a few minutes and it works pretty good (however, this is not a feasible long term solution as I would be doing this continuously during flight, which would add to the rigours and fatigue of a typical IFR flight in a C172, lol). Is there any way of cutting down the default auto-restart time of the PFC driver? Maybe that might be a permanent work-around to my dilemna. Thanks again Jermaine Clarke

Hi Pete, Just to provide a quick update as to where I'm at with this issue. As per your suggestion, I contacted the folks over at PFC to see what sort of assistance they might be able to provide. After a few back and forth e-mails with their tech folks, they suggested that I mail them the throttle quandrant console in order for them to inspect the unit. Since this won't be practical for me right now (I'm using the controls to assist me with an upcoming IPC in late December), I decided to do some more checks in hopes of ruling out the controls as the source of the problem. Here is what I have discovered after further testing: 1. I usually begin flights with the default C172 in a power off mode (everything shutdown, as in cold start). In this mode, the controls work fine (throttle inputs, and control inputs), with no intermittent loss of response. I did this for a few minutes, and everything seems to be ok. 2. I turned the sound "off" (pressing Q), and started the engines. With the engines started, the intermittent loss of response from the controls begins. Pressing Q to turn the sound on produces the same results (intermittent loss of response). 3. I alternated back and forth with engines off/engines off for a few minutes in each condition, and the results were as before. 4. I tried with different default aircraft, along with the flight 1 C172 (the aircraft i normally fly), and the results were the same. So it appears that the problem only manifests itself with the engines on. I'm at a total loss to explain why this would only happen with the engines on. Before I bite the bullet and do a complete re-install, is there anything else that you might suggest that I can try to resolve this issue? Any suggestions would be greatly appreciated. Thanks Jermaine Clarke

Hi Pete, I'm using the original COM connections that PFC shipped (my stuff is around 7 years old). Maybe I need to look at switching over to the USB adapters then? I'll recheck the connections when i return home. Thanks again Jermaine Clarke

Good day Pete, I'm using the PFC Beech Yoke and Throttle Quandrant combo(Turbo Prop Quandrant installed). Here's my problem. Every so often, my controls become "lifeless", i.e they don't respond to inputs. This lasts for a few seconds, and then control is restored. I checked the PFC log file in my modules folder, and the above message pops up a few times in the log file (auto-restart due to lack of incoming data). The most recent log file is as follows: ********* PFC DLL, Version 2.307 by Pete Dowson ********* 218360: Refesh initialisation to synchronize switches 731578: Auto-Restart due to lack of incoming data 750703: Auto-Restart due to lack of incoming data 869531: Auto-Restart due to lack of incoming data 1015672: Auto-Restart due to lack of incoming data ********* PFC Log file closed ********* Any assistance in solving this issue will be greatly appreciated. Thanks Jermaine Clarke

Thanks, Pete. J.C.