Report bugs and issues for the PMDG 737 for MSFS here

[wesleysiqueira]

I updated my script the problem that i mentioned stopped, but now CDU is not working anymore.

Can someone help me?

[idj4]

Change the following lines:

Var 1377, name aCDU1_EXEC, static, Link IOCARD_OUT, Device 31, Output 41
Var 1381, name aCDU1_FAIL, static, Link IOCARD_OUT, Device 31, Output 43
Var 1385, name aCDU1_OFST, static, Link IOCARD_OUT, Device 31, Output 45

To This:

Var 1377, name aCDU1_EXEC, static, Link IOCARD_OUT, Device 13, Output 2
Var 1381, name aCDU1_FAIL, static, Link IOCARD_OUT, Device 13, Output 4
Var 1385, name aCDU1_OFST, static, Link IOCARD_OUT, Device 13, Output 0

Regards
Ian

[wesleysiqueira]

Change the following lines:

Var 1377, name aCDU1_EXEC, static, Link IOCARD_OUT, Device 31, Output 41
Var 1381, name aCDU1_FAIL, static, Link IOCARD_OUT, Device 31, Output 43
Var 1385, name aCDU1_OFST, static, Link IOCARD_OUT, Device 31, Output 45

To This:

Var 1377, name aCDU1_EXEC, static, Link IOCARD_OUT, Device 13, Output 2
Var 1381, name aCDU1_FAIL, static, Link IOCARD_OUT, Device 13, Output 4
Var 1385, name aCDU1_OFST, static, Link IOCARD_OUT, Device 13, Output 0

Regards
Ian

Thank you! I will try, but those LEDs are connected to my mip expansion board. That's why I'm using on device 31.

[idj4]

Ok, sorry I thought you have an Opencockpits built CDU.

Is it a home built CDU? Can you give more details about it please?

Regards.

[wesleysiqueira]

Ok, sorry I thought you have an Opencockpits built CDU.

Is it a home built CDU? Can you give more details about it please?

Regards.

Yes it is a home built one, using a USBKeys card. Was working before, but after i commented all FO, variables from scrtipt. CDU is not working anymore.

[idj4]

Try it with the variables re-enabled. Using a script for a dual seat won’t cause any problems to a single seat, it covers both. This is why the script from Opencockpits is for dual seat.

Any script variables for the FO side won’t be executed if the hardware isn’t there to do so. These variables are, in effect, dead. I have a single seat too, so I don’t have a right side CDU or GPWS switch, but it doesn’t cause any issues.

Regards

[biggstuff]

If a module is added, i.e. the MIP ( Master 31,4,2,xx) in the PMDG B737.ini( airplane configuration file) and only have the
Boeing 737 MIP 2/3 structure (one seat) you need to disable the FO switches in the script. without doing this, there will be issues as the driver will not read the correct setting of a switch.

This must also be done for other modules that are in the pMDG B737.ini, if the modules are not fully equipped with all switches.

Adding // in front of the script codes that handle the non-existing switches will disable these switches.
First decompile the ssi script to a txt before adding the //. Then compile the modified script.

Roar

I've disabled the FO DU switches in the script. This has now eliminated the CPT's DU switches turning to the left when a LIGHTS TEST is executed. However, they still turn to the left when Oi4FS driver is launched. Also the GPWS aural sounds still activate when a LIGHTS TEST is executed.

I've noticed the SOURCE knob (DISPLAYS) on the software FWD-OH doesn't return to the AUTO position once it's been moved from it. It will only select ALL ON 1 or ALL ON 2 even when the hardware knob is on AUTO.

Regards.

Hi all
I just also found out that my SOURCE selector knob on the virtual OVH does not return to AUTO when moved away from it. I can bring the OVH switch to AUTO but the virtual switch would stay ALL ON 1 or ALL ON 2.
Was there any solution to this?

I found this section of the script and was wondering if it is correct

Var 2688, name NAVDSP_D_S_S, static

Var 0042, name sSOURCE_1, Link IOCARD_SW, Device 30, Input 36
{
IF &sSOURCE_1 = 1
{
&NAVDSP_D_S_S = 0
}
}

Var 0043, name sSOURCE_AUTO, Link IOCARD_SW, Device 30, Input 37
{
IF &sSOURCE_AUTO = 1
{
&NAVDSP_D_S_S = 1
}
}

Var 0044, name sSOURCE_2, Link IOCARD_SW, Device 30, Input 38
{
IF &sSOURCE_2 = 1
{
&NAVDSP_D_S_S = 2
}
}

[mvr1918]

Go to IOCPConsole in SIOC and test and verify that the knob gives correct output.

First test
Var 2688 NAVDSP_D_S_S

Give it a 0,1,2 to verify that the virutal cockpit knob reacts correctly.

Then test if the hardware knob works OK by monitoring the variables states and that it sets the correct value to the 2688 Var

[biggstuff]

Go to IOCPConsole in SIOC and test and verify that the knob gives correct output.

First test
Var 2688 NAVDSP_D_S_S

Give it a 0,1,2 to verify that the virutal cockpit knob reacts correctly.

Then test if the hardware knob works OK by monitoring the variables states and that it sets the correct value to the 2688 Var

Thx for the quick response.
I did the check as you suggested.
First I sent the values 0,1,2 to VAR 2688 and in all 3 instances it the virtual OVH knob responded correctly.
0- ALL ON 1
1 - AUTO
2 - ALL ON 2
Then I did the second check by moving the OC OVH to observe the values being received by VAR 2688
Moved to ALL ON 1 - Value 0
Moved to AUTO - Nothing received by VAR 2688 (No change - stays on the previous value)
Moved to ALL ON 2 - Value 2

Hope this helps you help us
Thx

[mvr1918]

The script works OK with an Opencockpit Overhead built module as it uses a rotary switch.
If it is not working for some of you, it could be

1. No connection between the rotary switch output pin and Input 37 of the MASTER card used(so its state never goes to 1 when switch it set to AUTO)
2. User built Overhead module that is not using a rotary switch but a ON-OFF-ON switch type.

To make the function work correctly when using a ON-OFF-ON switch type you can try to change the script to :

Var 2688, name NAVDSP_D_S_S, static, Value 1

Var 0042, name sSOURCE_1, Link IOCARD_SW, Device 30, Input 36
{
IF &sSOURCE_1 = 1
{
&NAVDSP_D_S_S = CHANGEBITN 0 ,&NAVDSP_D_S_S
}
ELSE
{
&NAVDSP_D_S_S = CHANGEBITN 0 ,&NAVDSP_D_S_S
}
}

Var 0043, name sSOURCE_2, Link IOCARD_SW, Device 30, Input 38
{
IF &sSOURCE_2 = 1
{
&NAVDSP_D_S_S = 2
}
ELSE
{
&NAVDSP_D_S_S = 1
}
}