selkan

Hi Pete, I am probably going to have to get back on a couple of items, but this might help you. I am using FSX; when starting engines using switches 1 and 2 only, they spool up engines, but upon reaching 20% N1, they die on me, and the process is repeated and repeated until I stop it by putting switch in the down position and back to center. I am using the latest PFC.Dll dated 22/01/09, I am pretty sure this must be version 4.34 I am using FSUIPC Version 4.421 I used to run FS9, and had no problems (with appropriate drivers) With regard to my A/T button, I do need to check I have it properly enabled in my PFC Main screen. It does however work 100% of the time using the FSUIPC interface, and 0% using PFC Drivers only. I should mention however that it does not come back to the 'on' position reflecting the actual switch position, so in the event of a go-around, I have to mannually flick it off and on again. I am not sure how to attach an PFC INI file to a post like this, can you tell me how, or an e-mail address I can send to (I know how to do that!) Just one other point which might help. Prior to my re-install of Vista, etc etc, I was getting a problem sometimes with switch number 4 when shutting down engines. Sometimes it would work, sometimes not. It did however always work after a few 'goes' at it.

Hi Peter, I wonder if you may be able to offer advice. I short time ago, I started having problems with my Engine Switches on my PFC Jetliner Console. I normally use switches 1 and 2 for starting engines (737-800) and switches 3 and 4 for fuel input/cutoff. Switches 1 and 2 still worked, but 3 and 4 stopped working. This coincided with a few other problems in my main Server P.C., and coupled with wanting a new faster harddrive, I decided to do a complete re-install; Vista 32 Ultimate, and FSX. I have nearly completed this major works, but my Engine Switches 3 and 4 are still not working. They show that they are working within the PFC Test Page. Also, when I try and use Switches 1 and 2 only to start engines, and auto latch at 20% N1, this is also not working. I have a registered copy of latest FSUIPC and WideServer for my network etc. I have sent this information to PFC, but so far they don't know what might be wrong. In the past, I have always had a problem with my A/T Press Button Switches on Throttle Handles (to turnoff off A/T on my MCP Hardware), but was able to set this via the FSUIPC Interface (buttons & Switches). I have looked under the 'headings' here (include PM), but can't find anything to help with fuel/engine switches. I was hoping you might be able to offer advice on how I might be able to set Switches 3 and 4 within FSUIPC, before it is concluded that something has actually gone wrong with the Console. Thanks, Steven

Hi Pete, seems to have done the trick. I went to FSUIPC Menu, and found the battery life was set to '1', so I have put it to '0'. I have had a couple of flights since, and all worked fine. I think what had happened was that I introduced four of my own wave files into FDC for the push back sequence. This added about 4-5 minutes to the push back sequence, i.e. with no engines running to take over matters. The Batteries had always been set to '1', but by chance I had always started engines before Batteries packed up!! Anyway, many thanks again; I don't think I would ever had thought of this one causing the problem! Regards, Steven

Hi Pete, will have a look at Magic Battery. I do not have PMSystems in use, so no APU is actually running in FSX -I believe? The shut down normally happens during push back. I use FDC Check lists etc, so it is normally around the twenty minute time mark. Thanks for advice again. Regards, Steven

Hi Pete, further to my troubles with my MCP, I actually have another problem which I can't solve. This started about three weeks ago, but I decided not to mention it while you were thinking about my MCP. Basically, I have PFC Jetliner Console. I connect to FSX (at my Gate), and then switch on my Console and MCP (same switch). After about twenty minutes my Comms - Avionics, switch off, and at the same moment my GC screens and FMC screen go blank. FSX is still running, and my Yoke, connected through Console is still working. If I turn off Avionics switch on Console and back on, then all screens come alive again and are connected to FSX, but Avionics will not restart. I have tried using a Key within FSUIPC to reset PFC drivers, but this does not work. Looking at the PFCFSX (Version 4.30) Log it says: User_requested comms restart! (which of course I havn't) If of any help, the information in log says FSX Version 10.0.61472.0 (SimConnect 10.0.61259.0) I am lost on this one; it normally happens about 8 out of 10 flights. Today I justy switched things on and didn't touch anything, and again after about twenty minutes all clicked off. Is there any advice you can offer? Thanks, Steven

Hi Pete, sorry for the delay. We have now completed up-dates, but afraid to say it has made no difference to the problem. I am not sure if this information will help you at all but:- when I am cruising along at say 35000' using VNAV and LNAV my speed window is blanked out and PFD is reading .79 - all as it should. If I press V/S, the PFD as you know jumps to a much higher value than .79, and accordingly I twiddle Speed Knob and get it back to read .79 If I now go back to using VNAV, the .79 in PFD has now been remembered, and when I come to make my descent all works O.K. I don't know if this helps, but clearly the information is being stored, and retained! Regards, Steven

Hi Pete, just to let you know I am unable to do up-dates to PMGC this weekend. I have a friend (ex P.C. World Manager) who is very good with P.C.'s who helps me with such matters, who has been unwell this weekend. I will contact you again just as soon as up-dates have been made. Regards, Steven

Hi Pete, O.K. if I leave speed window on MCP at .79 then my A/T will strive for the PFD display. As you can imagine, if this reads .97, this sends engines pretty wild! My PMGC (PFD) are now three years old, and I will up-date this weekend. I also notice you mention I am one CDU update behind, so I will do that as well. Many thanks, Steven

Hi Pete, I will endevour to answer:- My MCP Hardware is connected to a Com. Port (1) on main Server P.C. and in turn to PM MCP Software. My Jetliner Console is connect to separate Com. Port (2) again on Server P.C. and operates from PFCFSX.Dll 4.30 for FSX. I need to explain exactly what I mean by 'roll back' - When crusing at say 35,000ft using VNAV and LNAV I am cruising at .79 mach, as indicated on Pilots PDF (IAS around 250) Speed window on MCP blanked out. I am now given instruction to descend to say 29,000ft - If I am going to use V/S to descend I will tune in 29,000ft into my altitude window on MCP and then press V/S; at this moment my speed window opens and reads .79 correctly, but my PFC jumps from anything between .82 and .97. In order to make my PDF read .79 I need to turn my speed knob on MCP to .78 or .80 and then back to .79. I can then wind a descent value into my V/S window for the descent rate that I want. All the above is the same using LV CHG i.e. PDF will read .82 - .97 and again I will adjust speed and back to .79 to correct. I am using the following Versions:- MCP 422 CDU 392 PMGC 418 - this could be the problem, as I must update FSUIPC 4.20 WideFS 6.75 PFCFSX 4.30 I hope I have managed to make matters clear? Many thanks, Steven

Hi Pete, I agree this is probably a PM problem, but as I seem to have not made myself clear, I will try and answer your questions. I use PFC MCP Hardware. I use PM MCP Software Running on Server with FSX, FSUIPC etc etc. I have PFC Jet Console and use your PFCFSX program running on Server. Yes - when descending my Target speed reads .82 - .94 mach on PM GC. This is the same when using either LVL CHG or V/S. I use the Speed Knob on MCP Hardware to roll the mach number back to .79 Hope this at least tells you what is happening? Regards, Steven

Hi Pete, not sure if you can help? I have PFC MCP, Jet Console, FMC etc using ProjectMagenta Software. I have given this problem to ProjectMagenta, but no luck so far, so wonder if it might be a FSUIPC/WideServer/Client problem? I run FSX on one main Server P.C.(Vista Ultimate 64) and four client P.C.'s (Windows 2000) for Pilot, Co-Pilot Instrumentation (Boeing Glass Cockpit), FMC and Engine Instrumentation over a network. My problem is:- I fly the FSX default 737-800. When cruising my Mach speed reads .79. When told to descend by ATC and press V/S, my speed window opens and reads .79 correctly, but the mach speed on my Pilots instrumentation can read anything from mach .82 to .94!, so I have to quickly roll it back to .79 to avoid speed increasing dramatically. I already have FiddleMachForPM=Yes in my FSUIPC ini, and this corrects the problem when switching between mach and IAS. Hope you might be able to offer advice? Thanks Steven