Cabin Climb Gauge

[NobbyC_B738]

Roar,
thanks for input and proposal for script mod. This should work.
I agree it must be a PMDG bug, because I can see these Var 1536 severe value fluctuations on IOCPConsole, although I haven't installed a cabin climb gauge and although I have disabled that section in script. Usually PMDG should suppress these spikes. Suppressing them in driver should be the second option.

Var 1819 is exactly what I was searching for as a condition. Many thanks for this. I couldn't find in the script but found now in your documentation of output variables.

In the meantime I will install cabin climb gage provisionally and try script mod hopefully within the next days. I will share results.

2 Questions:
1) in original vers 7.0 script I found a little mistake in Var 1536 section (not responsible for jittery gauge behavior)

var 1536.jpg (72.47 KiB) Viewed 65745 times

can you please confirm that the minus signs are missing at this place (red marking) and should be added. In other places the signs are correct.

2) The &SERVO_VSI value to set the needle to 0 (in your ELSE-condition) is not "0" or a value close to "0", but somewhere in the middle of the servo setting range (CPos, usually between 400 and 600, depending on gauge gear adjustment) because for cabin climb gauge "0" is in the middle of the scale, not at the lower end, like for most of the other gauges. Can you please confirm?

[mvr1918]

Agree that the value to set the needle to 0 is not 0, but 528 or something close depending of the specific servo arm built.
Yes, the values should be minus.

[NobbyC_B738]

Update:

- cabin climb gauge installed
- script modified acc. to Roar's proposal
- made 2 complete flights inc. pushback, taxiing and landing
- cabin climb gauge works perfectly fine in the air and in any situation on ground (no jittery gauge behavior on ground!)

if someone is interested in the corresponding script modification, please let me know and I will share here

[mvr1918]

Thanks, Norbert, for your help in ironing out this issue.

[biggstuff]

I attempted to modify the script and try it. But I keep getting an error message when compiling.
I made so many changes to the use of } and { and still wont compile.
N, I am script challenged so please share your script mod.

Phase 2
ERROR! - Unknow function
Line: 2986 IF Var 1819 > 1000
==> Var

[NobbyC_B738]

Hi,

Var 1819 was not used in the original scrip, for this reason I have specified it in the line between Var 0172 and Var 1536

cabin climb mod1.jpg (94.46 KiB) Viewed 65709 times

Please don't forget to add the two minus signs

At the end of Var 1536 I have put this (green box):

cabin climb mod2.jpg (114.75 KiB) Viewed 65709 times

I have used >500 feet for condition height what works fine. I think you can try lower heights as well.
"520" (&SERVO_VSI) is my value for needle at "0". Your value may be different.

Good luck

[biggstuff]

Hello, I think the definition of the function was what I was missing and hence the error that was displayed.
I will define the function and add the line.

Also a long time ago I added the - (minus) sign when I was trying to diagnose the wild swings of the VSI guage. So that part was fixed a while agon
Thx again and I will post feedback.

UPDATE
I made the changes per the suggested script. Kept my radio alt limit at >250 and it worked beautifully. No more jitters and right above 250 VSI started to report in sync with the VC guage.
Thx for fixing this issue. Beautifully done!!

[James Curry]

Gents,

Sorry I'm back late to this thread but I must say a big thank you to you all for your contributions.

The work around to stop the jittering seems to work absolutely fine after having put the new coding in to my current script.

Massive work by you all for thinking outside the box..
James.