Eugenio Remus

Looks like I fixed it. I edited the "bugged" fsuipc.ini and came out with a "straighter" version of it. And the aircraft made one normal flight. Tomorrow I will rehearse. I enclose both .ini (in a zip) so that your supreme knowledge after comparing them will likely determine what wrong setting was "blocking" the climb, for me and other people to know and to stay away from ... Thanks for your kindness and your dedication and your support. Eu FSUIPC7.zip

I am aware that FSUIPC can reset all the settings to the default values; I guess this doesn't erase any user assignment ... does it ? And if doesn't, and the assignments stays in place ... what if the culprit is among the assignments, that are not erased ? The reset to defaults operation would be of no use. Am I correct ? Eu

John, I got news. I have been on a PMDG support forum where a guy last December started a S.O.S. thread and described a situation quite identical to mine, including the "STAB OUT OF TRIM" alert. In the end he simply removed his FSUIPC.ini and went flying with a regenerated FSUIPC.ini and he said the a/c was behaving okay. He wasn't able - that way - to tell what parameter, control, offset or else had gone wrong. I have no problems with making the same experiment, but ... shall I then reprogram all the hardware assignments (axes and buttons) from scratch ?!?!

No this cannot happen like you described it ! The first log will show the reduced climb rate and the elevator trim getting down from T/O value to below 1 ... when the 737 has leveled off, and it can't climb anymore, so I am basically stuck ... it's then when I need to exit FSUIPC, and as soon as I do it (well let's say it takes a few seconds) the a/c goes back to regular climb rate (in fpm) and the elevator trim gets back to higher values, maybe not around 5, which is a common average given normal fuel and payload, but at least around 4. That you can see by comparing the logs, because that's also what I witness. What is set, or reset, by restarting FSUIPC ... that I don't know. What do you want me to monitor for the next tries ? Unfortunately, having NO assignments whatsoever for the elevator trim and even NOTHING for the flaps has given me success.

Mind you, when I re-start FSUIPC the a/c flies under autopilot (LNAV and VINAV) so I needn't touch any control. As a matter of fact, I switch on the A/P short after passing 1,000 ft AGL, as per good common practices. Everything that happens - the handicaped climb that sees the a/c leveling off and the elevator trim descending from the T/O value to below 1 - happens under autopilot and autothrottle. You saw changes in the spoiler settings because I actioned the lever from DOWN to UP going thru the other positions, just to make sure that I was to take off with the spoiler down ... As for the elevator trim, I may be in need to adjust it after takeoff if I want to engage the A/P, because if you set the PMDG parameter "realistic A/P engagment" the A/C must be properly trimmed, and this means you must not apply significant actions on the yoke (on the elevator, especially), if you want to engage the A/P Hope this helps, and of course I will go on testing. I think I should also totally clear any hardware assignment to the spoiler: after all, I don't need it for take-off ... do I ? So if I can take-off and climb "normally" then we know that it's the way I am controlling the spoiler axis that gets in my way. This can be done without any particular offset logging ... so it's worth trying, and maybe it will be the very first test I take.

I might have moved on purpose the spoiler lever to make sure I left it in the "UP" range. Okay I modified the PMDG .ini as requested and here you go with another couple logs, after I upgraded to the last FSUIPC version published. Events, Axes and Offsets (the four you asked for) were requested. You will probably see the elevator trim value to descend from the takeoff setting (higher than 5) to almost below 1. Then I switched FSUIPC off and could see the elevator trim getting back to a setting that's convenient for a climb, in fact the a/c that had almost leveled up started to climb again and reached the commanded speed of 250 kias. I heard the noise and could also see the elevator trim wheels spinning to reflect that change of value. I also moved the spoiler lever up (to the flight detent position) and back down, to make sure it wasn't interfering with the climb. In theory, it looked raised and stwowed ... in practice, I don't know ... Maybe you can find what's the disturbing - yet temporary factor. Needless to say, when I re-launched FSUIPC, this didn't prevent the normal climb to continue. Looking forward to hear from you. FSUIPC7_log (2).zip FSUIPC7_prev (2).zip

Okay, here are the FSUIPC7_logs.zipnew logs as per your instructions.

And what I can tell you after a few more flights, is that I mustn't switch FSUIPC back on too fast, or the problem will persist. The aircraft needs a firm grip on the "free" climb before FSUIPC can be run again harmlessly. Hope it makes sense according to your findings ...

Here you go sir, I hope I did my homework well ... Curious and anxious to know about what you'll discover ! Best regards Eu FSUIPC7_log (1).zip FSUIPC7_prev.zip

yes, I kept the button controls on the axis range, since those positions will satisfy most needs during flight. Unfortunately that seems to get in my way again. With the spoiler controlled via buttons preset along an "unused" axis, I still have my climb choked. It is enough for me to close FSUIPC as soon as I see the darn "STAB OUT OF TRIM" light blinking, and to re-launch it a few seconds after, and then it's all right ... it's definetely weird. What should I now include in the log ?

It's a sophisticated way, but I am not that kind of tech guy. I pasted the line you wrote into the myevents.txt file, then I removed the ordinary axis assignment, and opted for the "Send to FS as a preset" option for such axis (and I could select my brand new preset ....), also removed the previous axis calibration as per your suggestion. But that setting could not move the spoiler lever at all ... So I went for something less refined, but that could be enough for my needs and - above all - to overcome the climb/accelerate issues ,,, so I set the spoiler axis as "unused" and programmed five button ranges for the PMDG presets "DOWN, ARMED, 50 %, FLIGHT DETENT, UP" and so I could finally see the lever moving along its full range of motion, along with the physical joystick lever. I will tell you if this will work and keep me away from trouble. I will leave it to other (and more tech-proficient) simmers to implement your suggestion, but thanks anyways.

And this is exactly my case (e.g. the landing gear lever, with the DOWN, OFF and UP positions), but thanks for the confirmation. One other thing I noticed about the spoiler axis calibration: I moved the lever full range back and forth, to set the bottom and top values. But when I operate it (in flight), I can see it traveling only between the "UP" and the "FLIGHT DETENT" position ... although there is still a portion to go ...

I think I found it. I allowed the a/c to fly level without asking for any climb, but it couldn't speed up anyway. So I started to investigate the spoiler axis and it wasn't properly calibrated. After calibration it would allow the a/c to speed up normally and even to climb. So I will do more testing but I think we're on the right track. Will let you know, Thanks anyways Eu

FYI, on a second trial, I did monitor the elevator trim value as soon as the climb got stuck and the STAB OUT OF TRIM light started to blink: it had been kept very close to zero ... 0,2, 0.5, 0.8, but as soon as I closed FSUIPC (and the light went off) the value started to increase, well beyond 1, and it soon reached 4 and above. Also, I don't have any joystick axis assigned to the elevator trim.

Well John you wouldn't believe your eyes. As soon as I turned FSUIPC off, the a/c resumed a normal climb, she got from 190 to 250 kias and reached 3500 fpm as a rate of climb. But the first thing which happened: the "STAB OUT OF TRIM" yellow blinking light stopped blinking and went quiet. So what does FSUIPC do to the stabilizer axis in order to "kidnap" him from the autopilot ? Thanks for your kind attention. Eu p.s. when you have a chance, bring my best regards to your dad. He might remember one Italian fellow simmer who got in touch with him quite a few years ago to fine tune the tiller-to-rudder transition during the takeoff roll ....

Well, someone who was in my situation asked that on the PMDG forums, and he was told to turn FSUIPC off, and bring the a/c to normal behavior, so it looks like a ping-pong game. Although it's weird, there has to be something getting in the way ... I will go back to the PMDG forums and see if there are any news. And I will see if quitting FSUIPC in that scenario "unleashes" the aircraft. Will report back. Thanks for now.

My situation is depictable almost exactly like it was described at the beginning of this topic: despite flaps being fully retracted (and spoilers obviously down), with sufficient climb power, the aircraft is incapable to climb and keeps its altitude despite autothrottle ON and in VNAV SPD mode, which ought to entitle a 250 kias climb or even more above 10.000 ft. See below what happened today. Before testing, I updated FSUIPC to 7.4.2 and recalibrated the throttles without reverse zone. (Will re-enclose FSUIPC.ini if needed). I brought the a/c to a runway, properly configured for takeoff, and began logging with "Buttons & Switches" and "Events" until it showed incapable to normally increase its initial climb. See the FSUIPC.log enclosed. My operations after I began testing were pretty normal: - pressed TO/GA - raised gear after lift off - selected CMD A to engage the A/P above 1.000 ft - started to raise flaps after 3,000 ft. agl were reached - put ldg gear lever and a/brake to OFF What I noticed was then that despite an 88.4 % N1 of CLB power, with flaps already commanded up (and the spd brk stowed), the a/c couldn't speed up to more than 196 KIAS and substantially stopped climbing and leveled off, with just a slight bit of vertical speed. Therefore I ended the test and zipped the files and here I am ... Thanks for the diagnosis. Best regards, Eugenio. FSUIPC7_log.zip

Hi, I need to bring this topic back to attention, since I started in the very same situation which brought the original user to post it ... and it is also clear to me that - should I erase my modified FSUIPC.ini - the 737 PMDG would work back to its normal climbing skills with a "virgin" fsuipc.ini ... But I can't obviously be happy with such a "dismantling" solution, because this means I can no longer use my many many assignments. Then I need your help to ascertain the specific cause of the malfunction, so that I can fix my FSUIPC.ini and go back to full operations with the 737 PMDG. Thanks for the attention, and since I already expect that a closer analisys of such file is needed, I am enclosing it right now. Best regards, Eugenio Remus FSUIPC7.zip