OCP4NGX with all PMDG 737NGX Variables and Events enabled in SIOC

Hi,

After some months away from flightsim due to other activites I have now updated OCP4NGX for OpenCocpits users.

A new and updated OCP4NGX can be downloaded from flightsim4fun.com - rk software

What is new

1. The main program is now called OC4BA (OpenCockpits for Boeing Airplanes).
2. The version of OC4BA is v.1.0
3. OC4BA consists of the OCP4B7X7 Manager and the OCP4NGX sub programs
4. In addition there are several Sioc txt and ssi files for different configurations
a. All Sioc txt and ssi files are now in v1.08
5. All PMDG NGX’s Variables and Events are now available through a new improved and faster OCP4NGX.
6. In order for users to use any or all of these new vars and events in their cockpits, new Sioc scripts have to be written.
7. If you make a new Sioc script for other parts of the NGX cockpit, please share with other users. Send me your script and I will upload it to flightsim4fun.com - rk software
8. You can make new scripts and merge them with existing scripts for MCP, EFIS, CDU by naming all new scripts in config.sioc.ini before compilation. See also http://www.lekseecon...configsioc.htmlon how to compile single and multiple scripts.
9. The link between Sioc variables and PMDG NGX Vars and Events are documented in Var LIST for info.txt and Events LIST for info.txt in your airplane folder ( Click NGX in the OCP4NGX Manager window)

rgs

Thank you! can't wait to get home to try it, I have been using you previous program since I started with my cockpit project and works great!
Thanks for your hard work!!!


Andy

IMPORTANT NOTICE for users of OCP4NGX who had the "missing MSVCP110.dll" message.


Please re-download the OCP4NGX from www.flightsim4fun as the file first uploaded had a multi-threading library linking failure that caused some or all of you
to get the "missing MSVCP110.dll" message when installing.


Sorry for the problems.




rgs,

Quote:

---

Originally Posted by Roarkr

Hi,

After some months away from flightsim due to other activites I have now updated OCP4NGX for OpenCocpits users.

A new and updated OCP4NGX can be downloaded from flightsim4fun.com - rk software

What is new

1. The main program is now called OC4BA (OpenCockpits for Boeing Airplanes).
2. The version of OC4BA is v.1.0
3. OC4BA consists of the OCP4B7X7 Manager and the OCP4NGX sub programs
4. In addition there are several Sioc txt and ssi files for different configurations
a. All Sioc txt and ssi files are now in v1.08
5. All PMDG NGX’s Variables and Events are now available through a new improved and faster OCP4NGX.
6. In order for users to use any or all of these new vars and events in their cockpits, new Sioc scripts have to be written.
7. If you make a new Sioc script for other parts of the NGX cockpit, please share with other users. Send me your script and I will upload it to flightsim4fun.com - rk software
8. You can make new scripts and merge them with existing scripts for MCP, EFIS, CDU by naming all new scripts in config.sioc.ini before compilation. See also http://www.lekseecon...configsioc.htmlon how to compile single and multiple scripts.
9. The link between Sioc variables and PMDG NGX Vars and Events are documented in Var LIST for info.txt and Events LIST for info.txt in your airplane folder ( Click NGX in the OCP4NGX Manager window)

rgs

---

ok so i tried it and here it goes:

MODULES that I have EFIS-737, MCP 737NG v2, FMC B-737 V3


the only problem i found is using new software my FMC does not work.

i dont want to blabber endlessly i am not sure if others will have this problem or maybe what info do you need to find out why is this problem.

I use OLD version software use following file to compile *.ssi file to use in confi_sioc.ini

PHP Code:

---


.\PMDG737NGX\OCP4NGX_EFIS_PP v1.05.txt
.\PMDG737NGX\OCP4NGX_MCP_PP v1.05.txt
.\PMDG737NGX\OCP4NGX_CDU_PP v1.05.txt     //this file is orignally named OCP4NGX_CDU v1.05.txt i just renamed it to change config_sioc.ini faster 


---

I use NEW version software use following file to compile *.ssi file to use in confi_sioc.ini

PHP Code:

---


.\PMDG737NGX\OCP4NGX_EFIS_PP v1.08.txt
.\PMDG737NGX\OCP4NGX_MCP_PP v1.08.txt
.\PMDG737NGX\OCP4NGX_CDU_PP v1.08.txt 


---

so when i use OLD software version everything works fine like it used to

in NEW version the FMC/CDU does not respond everything else is fine
improvement i see quick test is that all displays on MCP are alive when its MANAGER is run and SIOC as in the old version i had to actually turn knob for COURSE or IAS or whatever for numbers to come alive (not a big deal just a mention)

So anyways if there is some info you may need from me to see why FMC doesn't work I will be happy to let you know.


PS: well how i use 2 versions at once.. may it cause problem.. maybe...? let me know if you think so i didnt want to remove the old one since it work so GOOD !!! :D if you suppose this could cause trouble then maybe i should remove both and try to install only NEW one.. idk squat about C++ just funny that the old one works fine with all 3 modules EFIS MCP and FMC and it is only FMC that does not work with NEW software.. btw they are all PP modules

here is my install tree

c:\iocards\sioc\ this is where actual sioc.exe is with other sioc.ini etc..
c:\iocards\sioc\rk software\ this is where the OLD manager is and where i save the *.ssi file to use
c:\iocards\sioc\OC4BA\ this is where the NEW manager is and also here goes *.ssi file I want to use

Andy

OK just for kicks and to do it "BY THE BOOK" i uninstalled both version rebooted PC make sure all the old directories are GONE and installed ONLY NEW VERSION nothing else !

FMC still does not work with NEW version

Then i installed the OLD version FMC works fine..

Andy

Hi,

A new updated OCP4NGX with date stamp 15.02.2013 is now ready for download at flightsim4fun.com - rk software

All reported issues

"missing dll file"
"FMC V3 panel not working"

have now been corrected

rgs

Quote:

---

Originally Posted by AndyCYXU

OK just for kicks and to do it "BY THE BOOK" i uninstalled both version rebooted PC make sure all the old directories are GONE and installed ONLY NEW VERSION nothing else !

FMC still does not work with NEW version

Then i installed the OLD version FMC works fine..

Andy

---

Everything is working now!:D

If i find anything i will sure let you know

Thanks again Great program.
Andy

HI, this is a bunch of switches and buttons found on mip
I compiled it and tested with EFIC, MPC and CDU 1.08 PlugandPlay files works well together
feel free to use it I found it big help using it with OCP4NGX software no longer need to assign the custom parameters in FSUIPC
This is for PMDG737NGX

I play around with it and add more stuff like outputs etc..
GEAR LEVER does not work with PMDG's info they say to use some mouse thingy but idk...

Code:

---

//INPUTS ONLY

//MIP BUTTONS AND SWITCHES
//FOR USE WITH OPEN COCKPITS MASTER CARD and PMDG737NGX
//BUNCH OF BUTTONS AND SWITCHES FOR USE WITH Roar Kristensen OCP4NGX SOFTWARE
//BENEFIT OVER FSUIPC YOU DONT HAVE TO SET UP ALL THE EVENTS MANUALLY IN FSUIPC
//1 YOU NEED TO CHANGE DEVICE NUMBER TO MATCH YOU DEVICE IN THIS SET UP DEVICE 4 IS MY MASTER CARD CONNECTED TO USBEXPENSION CARD EASY TO DO USING NOTEPAD PLUS PLUS
//2 YOU NEED TO CHANGE INPUT NUMBER TO CORRESPOND WITH YOUR INPUT NUMBER FOR THE GIVEN SWITCH OR BUTTON


//--------------------------------------MAIN PANEL DU SELECTOR-------------------------------------------
Var 2372 Static, name CPT_MAIN_DU
Var 1 name CPT_OUTBD_PFD Link IOCARD_SW device 4 Input 3 Type I
{
v2372 = 0
}
Var 2 name CPT_NORM Link IOCARD_SW device 4 Input 8 Type I
{
v2372 = 1
}
Var 3 name CPT_ENG_PRI Link IOCARD_SW device 4 Input 1 Type I
{
v2372 = 2
}
Var 4 name CPT_PFD Link IOCARD_SW device 4 Input 7 Type I
{
v2372 = 3
}
Var 5 name CPT_MFD Link IOCARD_SW device 4 Input 0 Type I
{
v2372 = 4
}
//-----------------------------------------------LOWER DU SELECTOR-----------------------------------
Var 2371 Static, name CPT_LOWER_DU
Var 6 name CPT_ENG_LDU Link IOCARD_SW device 4 Input 6 Type I
{
v2371 = 0
}
Var 7 name CPT_NORM_LDU Link IOCARD_SW device 4 Input 5 Type I
{
v2371 = 1
}
Var 8 name CPT_ND_LDU Link IOCARD_SW device 4 Input 4 Type I
{
v2371 = 2
}


//----------------------------------------------AUTO BRAKE SELECTOR--------------------------------------
Var 2557 Static, name AUTOBRAKE_SEL
Var 9 name AUTOBRAKE_RTO Link IOCARD_SW device 4 Input 12 Type I
{
v2557 = 0
}
Var 10 name AUTOBRAKE_OFF Link IOCARD_SW device 4 Input 9 Type I
{
v2557 = 1
}
Var 11 name AUTOBRAKE_1 Link IOCARD_SW device 4 Input 10 Type I
{
v2557 = 2
}
Var 12 name AUTOBRAKE_2 Link IOCARD_SW device 4 Input 17 Type I
{
v2557 = 3
}
Var 13 name AUTOBRAKE_3 Link IOCARD_SW device 4 Input 13 Type I
{
v2557 = 4
}
Var 14 name AUTOBRAKE_MAX Link IOCARD_SW device 4 Input 14 Type I
{
v2557 = 5
}


//----------------------------------------ENG AND SYS BUTTONS-----------------------------------------
//WHEN USED AS Type P WORK BETTER BUT BUTTON GETS STUCK ON VIRTUAL COCKPIT
//MINOR

var 2560 static    name ENG_BUTTON Link IOCARD_SW device 4 Input 11 Type P
var 2561 static    name SYS_BUTTON Link IOCARD_SW device 4 Input 15 Type P


//-------------------------------------------------AP AT FMC RESET BUTTONS---------------------------------
//WORKS BETTER SET TO Type I AS WHEN Type P IS USED BUTTON GETS STUCK ON VIRTUAL COCKPIT
var 2366 static    name CPT_AP_RESET Link IOCARD_SW device 4 Input 21 Type I
var 2367 static    name CPT_AT_RESET Link IOCARD_SW device 4 Input 25 Type I
var 2370 static    name CPT_FMC_RESET Link IOCARD_SW device 4 Input 24 Type I



//-------------------------------------------------LIGHTS TEST DIM------------------------------------------
//DOES NOT ACTUALLY LIGHT UP INDICATORS ON HOME COCKPIT BUT DOES IN SIM NOT SURE WHY
//TEST LIGHT DIM 69978
//SEPARATE CODE IN LIGHTS DOCUMENT THAT DOES LIGHT UP HOMECOCKPIT INDICATORS

var 2373 static    name CPT_LIGHTS
Var 15 name LIGHTS_TEST Link IOCARD_SW device 4 Input 26 Type I
{
IF &LIGHTS_TEST = 1
{
v2373 = 0
}
ELSE
{
v2373 = 1
}
}
//var 2374 static name CPT_LIGHTS_2
Var 16 name LIGHTS_DIM Link IOCARD_SW device 4 Input 18 Type I
{
if &LIGHTS_DIM = 1
{
v2373 = 2
}
ELSE
{
v2373 = 1
}
}

//-------------------------------------------------DISENGAGE TEST SWITCH------------------------------------------
// DISENGAGE 69974
// PARAMETERS 0=1 1=OFF 2=2

var 2369 static    name CPT_DISENGAGE
Var 17 name CPT_UP_TEST Link IOCARD_SW device 4 Input 22 Type I
{
IF &CPT_UP_TEST = 1
{
v2369 = 0
}
ELSE
{
v2369 = 1
}
}

Var 18 name CPT_DOWN_TEST Link IOCARD_SW device 4 Input 19 Type I
{
IF &CPT_DOWN_TEST = 1
{
v2369 = 2
}
ELSE
{
v2369 = 1
}
}

//-------------------------------------------------FUEL FLOW SELECTOR------------------------------------------
// FULE FLOW SWITCH 70100
// PARAMETERS 0=RESET 1=RATE 2=USED

var 2558 static    name FUEL_FLOW
Var 19 name FUEL_RESET Link IOCARD_SW device 4 Input 23 Type I
{
IF &FUEL_RESET = 1
{
v2558 = 0
}
ELSE
{
v2558 = 1
}
}

Var 20 name FUEL_USED Link IOCARD_SW device 4 Input 20 Type I
{
IF &FUEL_USED = 1
{
v2558 = 2
}
ELSE
{
v2558 = 1
}
}



//-------------------------------------------------LANDING GEAR LEVER------------------------------------------
// DOES NOT ACTUALLY WORK PMDGS FAUL SO I COMMENTED IT
//var 2447 static    name GEAR
//Var 21 name GEAR_UP Link IOCARD_SW device 4 Input 29 Type I
//{
//IF &GEAR_UP = 1
//{
//v2447 = 0
//}
//ELSE
//{
//v2447 = 1
//}
//}

//Var 22 name GEAR_DOWN Link IOCARD_SW device 4 Input 28 Type I
//{
//IF &GEAR_DOWN = 1
//{
//v2447 = 2
//}
//ELSE
//{
//v2447 = 1
//}
//}

//-------------------------------------------------LANDING GEAR LEVER------------------------------------------
// SET UP THRU FSUIPC AS KEY PRESS WITH GEAR DOWN BUTTON28 SET AS G THEN GEAR UP BUTTON29 SET AS G AND WHEN RELEASED SET AS SHIFT PLUS G
// TO MOVE TO GEAR OFF POSITION

Var 27 Link IOCARD_SW device 4 Input 29 Type I
{
&FO_JoyStick64 = CHANGEBIT 22 v27 // GEAR UP
}

Var 28 Link IOCARD_SW device 4 Input 28 Type I
{
&FO_JoyStick64 = CHANGEBIT 23 v28 // GEAR DOWN
}

Var 29 name FO_JoyStick64 Link FSUIPC_OUT Offset $3340 Length 4

---

hope you guys find it useful and maybe even improve it

Andy

Here is a slightly modified script for Navigation Radio Plug and Play module from opencockpits
Only thing one needs to change is Device # to match your device as declared in sioc.ini
This is only for NavRadio i do not have COM radio I could not test it so i removed it to keep it clean and tested working well with all other scripts
you should not need to change nothing else but DEVICE #
then compile it together with other scripts you have into one *.ssi file

Code:

---

////////////////////////////////////////////////////////////////////
//// *******        File: OCP4NGX_NAV1-COM1 v1.08    **********************
/////                Roar Kristensen    February 11 2013
/////    OpenCockpits NAV1 & COM1 Sioc script to be used with OCP4NGX
///// ****************************************************************************

/// This script uses the following STATIC SIOC variable numbers in order to interface OCP4NGX and PMDG B737 SDK
/// !!! A STATIC SIOC Variable in this script MUST NOT BE CHANGED in order for OCP4NGX to work correctly!!!!


//  -----------------EDITED FROM ORIGINAL FOR NAV PLUG AND PLAY MODULE ONLY FROM OPEN COCKPITS----------------
//  -------------YOU ONLY NEED TO EDIT DEVICE NUMBER IN THIS SCRIPT IF YOU OWN OPENCOCKPITS NAVIGATION RADIO------
//  -------------PLUG AND PLAY MODULE TO MATCH YOUR DEVICE NUMBER AS DECLARED IN SIOC INI FILE---------------
//    Line 34: Var 4901 Static name AC_NAV1_BCD
//    Line 48: Var 4902 Static name ST_NAV1_BCD
//    Line 76: Var 6448 Static name NAV1_TFR Link IOCARD_SW Device 2 Input 6  Type P // Active/Standby swap button
//    Line 85: Var 5641 Static name NAV1_WH_INC value 0
//    Line 86: Var 5640 Static name NAV1_WH_DEC value 0
//    Line 87: Var 5643 Static name NAV1_FR_INC value 0
//    Line 88: Var 5642 Static name NAV1_FR_DEC value 0


//  -----------------NOT USED IN THIS SCRIPT THIS SCRIPT IS NAV RADIO ONLY---------------
//    Line 135: Var 4905 Static name AC_COM1_BCD
//    Line 148: Var 4906 Static name ST_COM1_BCD
//    Line 175: Var 6372 Static name COM1_TFR Link IOCARD_SW Device 0 Input 87  Type P // Active/Standby swap button
//    Line 179: Var 5637 Static name COM1_WH_INC value 0
//    Line 180: Var 5636 Static name COM1_WH_DEC value 0
//    Line 181: Var 5639 Static name COM1_FR_INC value 0
//    Line 182: Var 5638 Static name COM1_FR_DEC value 0

/// The SIOC variable naming and numbering are sync'd to PMDG SDK in this way:
/// PMDG VARS(that is output from aircraft) are within SIOC Vars 1000-1990
/// PMDG EVENTS( that is input to aircraft) are within SIOC Vars 2000-2990
/// FSX VARS(that is output from aircraft) use the OFFSET numbering less the 1 most significant number
/// FSX EVENTS( that is input to aircraft) use the OFFSET numbering less the 1 most significant number


// NAV1 part of script
//**********************************
//
Var 1 name AC_NAV1Low
Var 2 name AC_NAV1High
Var 3 name AC_NAV1

Var 4901 Static name AC_NAV1_BCD
{
  L0 = FROMBCD &AC_NAV1_BCD
  &AC_NAV1 = L0
  &AC_NAV1High = DIV L0 100
  &AC_NAV1Low = MOD L0 100
  CALL &OutAC_NAV1              // display new freq value to ACTIVE
}

Var 4 name ST_NAV1Low
Var 5 name ST_NAV1High
Var 6 name ST_NAV1

Var 4902 Static name ST_NAV1_BCD
{
  L0 = FROMBCD &ST_NAV1_BCD
  &ST_NAV1 = L0
  &ST_NAV1High = DIV L0 100
  &ST_NAV1Low = MOD L0 100
  CALL &OutST_NAV1              // display new freq value to STANDBY
}

Var 7 name OutAC_NAV1 Link SUBRUTINE 
{
  &D_AC_NAV1 = &AC_NAV1 + 10000    // to display + '1'
  &O_AC_NAV1DP = 1 
}

Var 8 name OutST_NAV1 Link SUBRUTINE 
{
  &D_ST_NAV1 = &ST_NAV1 + 10000    // to display + '1'
  &O_ST_NAV1DP = 1 
}

Var 9 name D_AC_NAV1 Link IOCARD_DISPLAY Device 2 Digit 0 Numbers 5
Var 10 name O_AC_NAV1DP Link IOCARD_OUT Device 2 Output 20 // Decimal Point   
Var 11 name D_ST_NAV1 Link IOCARD_DISPLAY Device 2 Digit 5 Numbers 5 
Var 12 name O_ST_NAV1DP Link IOCARD_OUT Device 2 Output 21 // Decimal Point

Var 6448 Static name NAV1_TFR Link IOCARD_SW Device 2 Input 6  Type P // Active/Standby swap button

Var 13 name NAV1_TEST Link IOCARD_SW Device 2 Input 2 // NAV1 TEST button doesnt do nothing lol


Var 5641 Static name NAV1_WH_INC value 0
Var 5640 Static name NAV1_WH_DEC value 0
Var 5643 Static name NAV1_FR_INC value 0
Var 5642 Static name NAV1_FR_DEC value 0

Var 15 name temp1 value 0
Var 16 name temp2 value 0

Var 17 name ROT_NAV1_ST Link IOCARD_ENCODER Device 2 Input 0 Aceleration 1 Type 2
{
&temp1 = &temp2
L0 = &ROT_NAV1_ST
&temp2 = ROTATE 0 100 L0
  IF &temp1 > &temp2
  {
    &NAV1_WH_INC = CHANGEBITN 0 &NAV1_WH_INC     
  }
  ELSE
    {
      &NAV1_WH_DEC = CHANGEBITN 0 &NAV1_WH_DEC
    }
}



Var 14 name ROT_NAV1_ST1 Link IOCARD_ENCODER Device 2 Input 4 Aceleration 1 Type 2
{
&temp1 = &temp2
L0 = &ROT_NAV1_ST
&temp2 = ROTATE 0 100 L0
  IF &temp1 > &temp2
  {
    &NAV1_FR_DEC = CHANGEBITN 0 &NAV1_FR_DEC
}
  ELSE
  {
  &NAV1_FR_INC = CHANGEBITN 0 &NAV1_FR_INC
  }
}

//END OF SCRIPT

---

Thanks for the software Roar... oh i said that already... :oops:

Andy

Hi Andy,

Just wanted to tell that I have now ordered the P&P OVH V3 from OpenCockpits. It will be fully usable with my OCP4NGX and soon to be ready sioc script.

An update of the MCP script to be used with the NEW MCP V3 from OpenCockpits will also soon be ready.


rgs,

does anyone have this version pls email to me new 1.2 does not work for me... and I can't find the install files I think I lost it deleted by mistake, thanks

andycyxu at Gmail.com

Hi Roar
I have Mastercard, Display, USB.. but I haven't any plug&play Opencokcpit modules.
I built it by myself.
My question : can I use OCP4NGX and using only my scripts and panels (Autobrake, COM,etc) to access PMDG ?
For instance : I have no way works the autobrake on PMDG and the ENG adn SYS buttons as well but through your software I can do that.
Could you confirm please ?
Thanks in advance
Mauricio

Quote:

---

Originally Posted by graziani

Hi Roar
I have Mastercard, Display, USB.. but I haven't any plug&play Opencokcpit modules.
I built it by myself.
My question : can I use OCP4NGX and using only my scripts and panels (Autobrake, COM,etc) to access PMDG ?
For instance : I have no way works the autobrake on PMDG and the ENG adn SYS buttons as well but through your software I can do that.
Could you confirm please ?
Thanks in advance
Mauricio

---

Hi,

Yes, you can use OC4BA v2 with own built OC hardware to get access to PDMG functions.

/Roar