Question on 737 overhead

[biggstuff]

Thx for your response.
I believe the back-end software has been changed to only recognize the new script and not the old one.
That maybe the problem OCP4NGX_v4.5 script version.

One other question if anyone knows

Var 1056, name g_FT, static, Value 0

Does the value of 0 needs to be changed with a servo position value? I did not change it on the other servos that works perfectly.

[PH-JRJ]

I think it should work and will edit my script within a few weeks and test it.
Roar told me the difference between OC4BAv5 and Oi4FS servo scripts: Some small fixes and more accurate gauge outputs are the main changes.

My values are also on 0

Best regards

Remco

[biggstuff]

Thx for your feedback. I'm going to wait for your test to see how it performs before I attempt it.
I am still learning scripting, so I am not that confident lol
Just share your findings whenever you are complete.
Thx again!!

[PH-JRJ]

I’ll keep you posted !

[biggstuff]

So I did an experiment just a few hours ago as I had this idea.
I decided to use the actual FT values just like the VSI uses and incorporate the negative values

Var 1056, name g_FT, static, Value 0
{
L0 = &g_FT
L2 = L0
C0 = L0 >= -50
C1 = L0 <= -45
IF C0 AND C1
{
&g_FT_low_val = -50
&g_FT_high_val = -45
&FT_high_val = 210
&FT_low_val = 262

etc
Here was my outcome.
Servo position when I start SIOC was at -50 for FT
I loaded PMDG 737 coldndark. Servo position moved to zero (0). However virtual cockpit was still at -50.
Then I put ground power and Virtual cockpit moved to still at 0 and OVH servo FT moved to +10.
Put APU power and virtual cockpit now moved to +10
So It did not match from the beginning but did match after APU powerup.
Just thought I share this, just incase it helps with further diagonosis.

I have other issues with other servos but I hope we can understand one by one.
Duct Press not matching.
VSI does wild swings when taxing and aircraft hits bumps or goes up and down slightly. Other than that it works well in climb and descent.
CT is now completely off track and not matching.

Deleted my other post to track things here so I copied and pasted the post here so I can remember
Need some help from those that have the OVH servos working.
I have manged to get all the other gauge servos somewhat matching the virtual cockpit fo the PMDG 737 however I am struggling to get these last two to play ball.
FT- Fuel temperature in the cockpit would not move at all. I have checked the Var numbers and output on the servos card to make sure it is correct, however when I initiate power and flight it will still stay at zero on the OVH but virtual cockpit would move. I have also calibrated it.

PL/PR - Duct pressure gauge. This moves with the virtual cockpit but despite all the calibration with the right servo numbers the OVH needles are completel out of sync with the virtual cockpit of both needles. I get full displacement of the OVH needle while virtual cockpit is say only a quater movement. Totally out of sync. Again I have collected the servo numbers and updated the script with those numbers and expected them to match closely just like all the othe ones I have done.
Also need to mention I have OC servo plus card so I only use one card for the FWD OVH not two per the older set ups.
With the little I know about the script mods and everything I have done so far I sincerely believe this problem is coming from the back end software and not the script. All servos should be equal and if I set the values they should perform similar. Which is not the case here.
What could I check next?

[PH-JRJ]

Hi Bigstuff,

Apology for the very late response ....
I have changed the FT part and used script code of an old version and the Gauge is working correct now!

I suggest to make a copy of your current script file first and remove this part:

Var 0140, name SERVO_FT, Link USB_SERVOS, Device 37, Output 1, PosL 10, PosC 511, PosR 1000, Type 1

Var 8010, name FT_val

Var 8011, name g_FT_calc

Var 8012, name FT_calc

Var 8013, name g_FT_val

Var 8014, name g_FT_low_val

Var 8015, name g_FT_high_val

Var 8016, name FT_high_val

Var 8017, name FT_low_val

Var 1056, name g_FT, static, Value 0
{
L0 = &g_FT
L2 = L0
C0 = L0 >= 0
C1 = L0 <= 100
IF C0 AND C1
{
&g_FT_low_val = 0
&g_FT_high_val = 100
&FT_high_val = 0
&FT_low_val = 224
}
C0 = L0 >= 100
C1 = L0 <= 200
IF C0 AND C1
{
&g_FT_low_val = 100
&g_FT_high_val = 200
&FT_high_val = 224
&FT_low_val = 291
}
C0 = L0 >= 200
C1 = L0 <= 300
IF C0 AND C1
{
&g_FT_low_val = 200
&g_FT_high_val = 300
&FT_high_val = 291
&FT_low_val = 366
}
C0 = L0 >= 300
C1 = L0 <= 400
IF C0 AND C1
{
&g_FT_low_val = 300
&g_FT_high_val = 400
&FT_high_val = 366
&FT_low_val = 445
}
C0 = L0 >= 400
C1 = L0 <= 500
IF C0 AND C1
{
&g_FT_low_val = 400
&g_FT_high_val = 500
&FT_high_val = 445
&FT_low_val = 521
}
C0 = L0 >= 500
C1 = L0 <= 600
IF C0 AND C1
{
&g_FT_low_val = 500
&g_FT_high_val = 600
&FT_high_val = 521
&FT_low_val = 584
}
C0 = L0 >= 600
C1 = L0 <= 700
IF C0 AND C1
{
&g_FT_low_val = 600
&g_FT_high_val = 700
&FT_high_val = 584
&FT_low_val = 636
}
C0 = L0 >= 700
C1 = L0 <= 800
IF C0 AND C1
{
&g_FT_low_val = 700
&g_FT_high_val = 800
&FT_high_val = 636
&FT_low_val = 681
}
C0 = L0 >= 800
C1 = L0 <= 900
IF C0 AND C1
{
&g_FT_low_val = 800
&g_FT_high_val = 900
&FT_high_val = 681
&FT_low_val = 757
}
C0 = L0 >= 900
C1 = L0 <= 1000
IF C0 AND C1
{
&g_FT_low_val = 900
&g_FT_high_val = 1000
&FT_high_val = 757
&FT_low_val = 809
}
&FT_calc = &FT_low_val - &FT_high_val
&g_FT_calc = &g_FT_high_val - &g_FT_low_val
&g_FT_val = L0 - &g_FT_low_val
&FT_val = &FT_calc * &g_FT_val
&FT_val = &FT_val / &g_FT_calc
L1 = &FT_high_val + &FT_val
&SERVO_FT = L1
}


And insert this part:
Var 0227, name SERVO_FuelTemp, Link USB_SERVOS, Device 37, Output 1, PosL 192, PosC 511, PosR 1023, Type 1

Var 1056, name TXRX_FuelTemp, static, Link SUBRUTINE
{
IF &EL_STATE = 15
{
L0 = 606 // sets needle to 0
L1 = &TXRX_FuelTemp * 6
L0 = L0 + L1
&SERVO_FuelTemp = L0
}
ELSE
{
&SERVO_FuelTemp = 660
}
}

Make sure you change the L0 value with your needle to 0 value. mine is 606.
Save your txt file and compile it to see if there are no errors and save as ssi file.

Best regards

Remco