Unwanted pitch up 6000 ft/min

[JWS]

My only thought is that perhaps AutoV/S ini setting is off in the simulator - but I still have to cross check that. I made a note to observe the V/S selection in the last sim session and I saw no errors. It was operating exactly like it should (never saw 6000ft/min!!). I also have a vague memory that errors like this can be down to either the panel.cfg file or the aircraft.cfg file settings.
I will keep an eye out for this though, and also check the ini settings re the auto setting.

Regards
Jonathan Richardson

Jonathan,

I will check auto V/S ini setting (which should be "on"??). As far as I can tell it's the combo CPFlight and MP MCP that gives the problem. CPFlight stand alone or PM MCP stand alone do seem to function properly (engaging V/S gives 0000 in the window, then set + or - using thumbwheel).

Tell me what specific information you need from my settings etc. and I will mail them to your Project Magenta mail address. Thanks for the efforts so far.

Regards,

JWS

[JonathanRichardson]

>I will check auto V/S ini setting (which should be "on"??). As far as I can tell it's the combo CPFlight and MP MCP that gives the problem. CPFlight stand alone or PM MCP stand alone do seem to function properly (engaging V/S gives 0000 in the window, then set + or - using thumbwheel).

Hi

We use that combination with latest firmware. I have a very slight feeling from memory that the Auto V/S is off, but I have not checked - I'm working in other areas right now, but if I fire up the 737 today I will check it. I presume you have checked both alternatives already, so it is unlikely to be this setting (I presume).

Regards
Jonathan Richardson

[NicD]

I have the same combination and have had better results with the Auto-V/S turned off.

[JWS]

I'll double check both settings once again.

JWS

[JWS]

Tried AutoV/S 'on' and 'off' but with the same result. Engaging V/S means +6000 ft in the window, no matter what you do (re-installed latest firmware).

However, I noticed that for a very brief moment a negative value seems to appear in the window before 6000 becomes visible. It's a flash, too short to see what the actual value is, but I managed to see the minus sign before it turns to +6000.
I wonder if PM settings like speed intervention and altitude intervention are responsible. E.g. speed intervention doesn't function properly on the CPFlight in my case. During VNAV (speed window empty) pressing the CPFlight MCP SPD button longer than a second or so should result in an open SPD window (so you can adjust the speed) while maintaining the VNAV mode. In my case VNAV always closes and SPD mode is engaged.

So I'll check this out, maybe tonight.

I tested with default aircraft (737 & 747). Results are the same, PM alone works fine (including SPD Int), CPFlight MCP alone also, the combination of the two doesn't.

Regards,

JWS

[JWS]

Problem solved thanks to CPFlight & PM.

JWS

[marco]

Hello JWS,

You say : problem solved. May we have some more informations ?
Thx in advance.

Marco

[JWS]

Marco,

I've made on the request of CPFlight some serial log files during test flights engaging V/S etc. These files have been studied by Paolo and Jonathan to see what was happening between the MP MCP software and the CPFlight hardware. Paolo discovered some anomalies (what exactly I don't know) and made some alterations to the firmware and now the CPF "rocks the planet" again. There some minor other issues yet but I'm in the process of making new log files and will hand them over to CPF. And this is really the way to do it because the guys at PM and CPF can make sense out of them files.

Grtz.

JWS

[marco]

Hello JWS,

Thx for your informations.

Bedank.

Marco