OCP4NGX_255 ,script OCpngx_v3.4.ssi

[betampona]

Hello, I just switching to OCPNGX_255 and V3.4.ssi script.
Everything is operational, the dial with the electrical values, the lights of the valve It Works.
I congratulate you for the work.

As you advance on Overhead, I can not find the input in the program for the following events.
2605 oh_cvr_erase
2606 oh_cvr_test
2602 oh_bleed_trip_reset_button
2597 oh_bleed_ovht_test_button
2661 tat_test
2689 navdsp_fmc_sel
2628 oh_elec_galley
2633 oh_elec_maint_swicht

Waiting for an answer.
Greetings.
Dominique.

[mvr1918]

Hi,

Thanks for letting me know about these missing buttons.


I will make them available in the next update of the script.

I also need to ironed out some small bugs in the OVH script( not very important bugs, but there are some Leds that do not bahve correctly in all
the 15 different electrical states of he Power system.


Ones I have corrected them I will update.

Please report any other findings

Thanks,
Roar

[betampona]

Hello, I was a bit too quick on the proper functioning of OCP4NGX.
Before I had a program that I modified from time to time OCP4NGX.exe stopped. I re-booted and all OCP4NGX.exe off again normally.
Now I use the script v3.4, I just make a flight and .exe Ocp4ngx is stopped during the flight. When I wanted to revive OCP4NGX.exe. The IRS were arrested and it is impossible for me to put them on the road in the FMC during the flight.
The IRS should not be cut with the Var 2800 (via the battery switch)

Dominique
traduction google.

[betampona]

Hello,
Can I have an example to the script OCP4NGX_V3.4 .ssi. For the "Var 2800"
now I have this:

Var 0000, Value 0
{
&LT_TIMER = 0
&SD_DELAY = 0
&MCP_R_DELAY = 0
&BlankOrLit = -999999
&OnOrOff = 0
&Blank = 1
&Lit = 0
&LightsSel = 1 // 1 = Default no test
&ZERO_MCP = 0 // GET RID OF DIRT!
&ovh_state = 0
CALL &CloseAnnuns
&COM1_Power_ON = 0
&NAV1_Power_ON = 0
&COM2_Power_ON = 0
&NAV2_Power_ON = 0
&ADF_Power_ON = 0
&ATC_Power_ON = 0
&CDU1_POWER_ON = 0
&CDU2_POWER_ON = 0
&MCP_POWER_ON = 0
&MIP_POWER_ON = 0
&ENG1_Servo = 512
&ENG2_Servo = 512
}

Var 2800, name ovh_state, static

Var 0465, name State_delay

Dominique

[mvr1918]

Hi,

You could either change

&ovh_state = 0

to

&ovh_state = 1

or

Var 2800, name ovh_state, static value 1

re: IRS

you can always delete the IRS handling in the OVH script part

I put it in as I do not have the AFT OVH in my cockpit..

[Lukasz]

Hello I buy this Friday program, I not have p & p from opencockpit, just master card and expansion.
I install it as described in your file
I run SIOC code file is the
I want to display my mcp LED homemade "vs" when I click on in the cockpit with me right will be displayed nothing
I change the output device and at you idx = 15 out= 32 me idx = 1 output = 11 but nothing is happening, when
I run IOCP console I have all the variable but nothing changes in the log when I move in the aircraft cockpit on screen, is what it is possible that SIOC does not communicate with the server oc4ngx?

Sorry for my English
Lukasz

[mvr1918]

Hi,

If I understand you correct, you have an Expansion/MASTER card only. Please verify.

Try the following:

1. Edit the MCP IDX15 line in OC4BA.ini
to MCP_My IDX33

Now you should have a working sioc.ini configured correctly for your hardware

2. Run SIOC.exe and click Edit_Script, export to text, save as OCP4NGX_V1.2m.txt

3. Edit the OCP4NGX_v1.2m.txt so that all Device 15 lines are reading Device 33

4. In the same file, find the line Var 2800 name ovh_state and edit it to Var2800 name ovh_state value 1

5. You must now also edit the output of "vs" in the script to match your hardware
6. Save

7. Start SIOC.exe again and click Edit_Script and open the newly edited OCP4NGX_v1.2m.txt and recompile and save as OCP4NGX_v1.2m.ssi

8. Run OC4BAConfig , select OCP4NGX_1.2m.ssi and link the detected EXP/MASTER to MCP_My

9. Now try to start a B737 flight

[Lukasz]

Hi,

If I understand you correct, you have an Expansion/MASTER card only. Please verify.

Try the following:

1. Edit the MCP IDX15 line in OC4BA.ini
to MCP_My IDX33

Now you should have a working sioc.ini configured correctly for your hardware

2. Run SIOC.exe and click Edit_Script, export to text, save as OCP4NGX_V1.2m.txt

3. Edit the OCP4NGX_v1.2m.txt so that all Device 15 lines are reading Device 33

4. In the same file, find the line Var 2800 name ovh_state and edit it to Var2800 name ovh_state value 1

5. You must now also edit the output of "vs" in the script to match your hardware
6. Save

7. Start SIOC.exe again and click Edit_Script and open the newly edited OCP4NGX_v1.2m.txt and recompile and save as OCP4NGX_v1.2m.ssi

8. Run OC4BAConfig , select OCP4NGX_1.2m.ssi and link the detected EXP/MASTER to MCP_My

9. Now try to start a B737 flight

Good Morning
I followed your advice, everything works 100% Thank you

What I did was I took the OCP4NGX_v3.1.ssi Export text file and saved OCP4NGX_v3.1_m.ssi (is that it's nothing that I took the version 3.1?)

For the future for my switch I must do the same?
If I bought a p & p opencockpit Module "flaps eg"
it will work?

Once last thing how to find an APU ON switch in the 3.1 file?

Thank you for your quick reaction and above all thanks to you that it works.
Lukasz

[mvr1918]

Hi,

3.4 is the latest script version , not 3.1.
If you are using the 3.4 script file as a base for your hardware, you also need to use the OCP4NGX_255.exe as this one has
support for all PMDG SDK events and variables compared to the OCP4NGX_248.exe( default OCP4NGX.exe after installation)
that has only support for the standard events and variable syou find in the P&P modules. Read MUST READ about how to rename OCP4NGX.exe and changing versions.

You should also edit the Var2800 name ovh_state line so it read Var2800 name ovh_state value 1 in the 3.4 script


All P&P module should work, but they must all be configured once via OC4BAConfig.

To find APU ON you search for "APU_ST" in the 3.4m txt file