PFC MCP

[selkan]

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

[Pete Dowson]

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.

But no MCP? You mention all the things not relevant, but not the thing you are asking about? Where is the PM MCP program and are you using PM MCP to drive the PFC MCP directly, or are you using my PFCFSX program? How am I supposed to advise without any relevant information?

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

You should set the target altitude first surely. Then normally LVL CHG, but V/S if you wish.

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.

What do you mean by "pilot's instrumentation"? Do you mean the PFD from the PM GC program? The target or the actual? The target should always follow the setting on the MCP. PM's software is responsible for that.

And if the MCP already reads .79, how do you "roll it back" to .79. It doesn't make any sense.

BTW, for my software it is always vital to quote version numbers. This query sounds almost 100% about PM software (so this is really the wrong place), but PM component version numbers are just as important too.

There are PM Forums at http://www.mycockpit.org/forums/forumdi27981&f=99 .

Regards

Pete

[selkan]

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

[Pete Dowson]

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.

And are both the PFC MCP and PFC Jet Console daisy chained to the same COM/USB port and driven by my PFCFSX, or is the PFC MCP connected direct to the PM MCP and only the Jet Console connected to PFCFSX.DLL?

You see it makes a considerable difference as to which piece of software is actually responsible! In my setup the MCP is controlled by PM's MCP software, so I've really not had a great deal of exposure of my own MCP handling in PFCFSX. It was tested very thoroughly in the FS9 version, PFC.DLL.

And in any case, version numbers of all the software components being used are still vital. You seem to have forgotten to mention them again.

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

And I still don't understand that -- how do you "roll back" the value of .79 you said was displayed on the speed window on the MCP to .79? That still makes as little sense as last time you stated it and I asked the same question.

Hope this at least tells you what is happening?

No, sorry, you seem to have missed pretty much all of my questions.

If you could please consider answering the questions maybe I could set up a similar arrangement here and see what is happening. But without knowing about how you have things connected, what version numbers of FSUIPC, PFCFSX, MCP, GC and CDU programs you are using, and how you actually manage to roll back a value of .79 to .79, I can't do anything at all. Sorry.

Regards

Pete

[selkan]

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

[Pete Dowson]

My MCP Hardware is connected to a Com. Port (1) on main Server P.C. and in turn to PM MCP Software.

Okay. Good. It isn't anything to do with my software then! ;-)

I need to explain exactly what I mean by 'roll back'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.

Assuming for "PFC" you mean the "PFD" screen, that does certainly sound like a bug in either the PM MCP or GC software. I must admit to never having seen such. But I'll try it -- tomorrow now.

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.

Ah, so by "roll back" you mean "twiddle the knob to force the GC to correct itself".

And if you left the MCP showing .79 and the PFD showing something different, which speed is the A/T system striving for, the MCP-displayed value or the PFD displayed one? Obviously if it's the PFD displayed one then, since it is the MCP program which is controlling the throttle, it points to a bug in that one, or possibly a mismatch of versions.

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

Okay. I have the same except CDU 393 (an intermediate build said to "fix a major bug" according to the main update page), and PFD 452. You are right, your PFD version is 34 builds out of date -- probably years! I don't think PM support users with such disparate levels. There are bound to be changes which make those conflict with each other!

Regards

Pete

[selkan]

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

[Pete Dowson]

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.

Ok. Let me know afterwards. I can set up a test here too, though it would really only be to confirm an error report to PM.

The new CDU is in the "intermediate versions" list, not the main list, but the latter does say, in small print, that it fixes a "major bug".

Regards

Pete

[selkan]

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

[selkan]

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

[Pete Dowson]

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 ...

It can't really help me at all because it must be a function of the PM software. I really am not part of PM and have no idea of the software internals. You need to post your PM support problems to PM support. Possibly also ask on the PM forums -- there's a lot of helpful people there.

I won't get the chance to actually try it to see if I get the same until next weekend, but a friend of mine and I had several flights over the weekend without seeing any problems. This is with the MCP in the PFC 737 cockpit.

Regards

Pete

[selkan]

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

[Pete Dowson]

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.

Sounds like your battery is running down. Have you got the engine(s) running and generator/alternator switched on? Or else got the APU running (if you are using PMsystems).

If you don't want the battery to run down and haven't got the facilities to get power in time, look at using the "magic battery" facilities in FSUIPC (Miscellaneous page).

Most of the things you ask here are PM related and you should be dealing with PM support. The MCP question was another one in point. I did say I'd see if I could corroborate it, but I've run out of time now till late March. Sorry.

Pete

[selkan]

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

[Pete Dowson]

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.

Depends on the aircraft -- the battery use varies, and of course it also depends how much stuff you've got switched on. There's an APU in FSX (wasn't in FS9) but I don't know if it works [-- you'd have to switch it on though, even it it is in the model you use. I use the pmSystems one. Some of the better add-on aircraft have one.

Alternatively leave most things turned off till you are ready to start an engine and its generator.

Pete

[selkan]

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