Tutorial to connect OC-MCP/EFIS with OGS1.20 and FS2004

[Georg Schneider]

:DHello to all Cockpitbuilders around the world!:D

Now is the time to do something for the community from my site!

Many people here in the forum have helped me understanding
sioc a bit more!

So i decided to write a hopefully helpfull tutorial to connect the

Opencockpits Modules (MCP/2x EFIS) with the great freeware
Glass Cockpit software "OGS 1.20" from "Cockpitware.com"
and FS2004.

The last week i had a big struggle with this and "kiek(Nick)" and
Norbert helped me a heck out of it:-D:mrgreen:8);)

The tutorial describes everything you need and how to setup everything!
In the .zip file which you can download in the tutorial downloadsection.


i encluded the tutorial in .doc(word97/2003 format)
my ogs.ini file as reference and my sioc.ini file as reference.
And the sioc script to run OC-MCP/2xEFIS) with OGS1.20

I`ve rewritten the original efis script provided in the OGS1.20 download
to match the Captain/FO EFIS you can buy at Opencockpits shop.
I´ve merged the FS2004AP script provided in the sioc download
with my rewritten efis script.

Everything is tested in my cockpit with the original OC-MCP/2xEFIS
from Opencockpits.
All functions work so far OGS1.20 is cabable to.

I´ve made some compromisses to functionality but this is described in
the tutorial.

The provided script is fully plug`n play with the OC-modules!
You only have to adjust ogs.ini/sioc.ini and you are ready to run:-D

I`ve checked everything a view times and if you find any mistakes
please contact me.

To get running the OC-MCP and OC-captain/FO EFIS is needed.
Also OGS1.20 from http://cockpitware.com
and SIOC 3.50 with update 3.52b from http://www.opencockpits.de

For those guys who have problems to get network connection with
IOCP-server/client please read the tutorial and i hope things
work out well;)

I hope my work can help someone(especially the beginners) as much
i get helped here in the forum!

Greetings and happy flying

George

The provided downloadlink will be actice till file is accepted in the download section!
Then it will be removed here due limited download traffice.

[Trevor Hale]

Thanks George. If you would like, please upload that file into the Download Library. That way you don't use up all your bandwidth.

Trev

[Bob Reed]

George.. Thank you VERY much! Yes we need to get this in the download area....

[Georg Schneider]

:DHi Bob and Trev !

Thanks for the quick reply !

Please give me your reply to my tutorial and some advice to make
it even better in next version;)

Hope it helps many people!
Will upload it in the download section!

Greetings George

[Bob Reed]

:DHi Bob and Trev !

Thanks for the quick reply !

Please give me your reply to my tutorial and some advice to make
it even better in next version;)

Hope it helps many people!
Will upload it in the download section!

Greetings George

I will have a look at it tonight or tomorrow morning and let you know IF there is anything I feel needs to be changed.. I have a feeling it will be just fine.

[barkay]

Georg,

First of all thanks for the tutorial and the very neatly designed ssi file. As far as I understand when I looked at your file you used a variable called CPTflags. Whenever a state changes you have also used a lot of SETBIT and CHANGEBIT commands. However I did not see any connection from this program to tell the SIM to change the ND range and/or mode as CPTFlags only changes the bit state of the variable and do not tell enything to the simulator. At least this is as far as I went. I know I am missing something here. Is this a special variable used by lets say OGS sending a command to the simulator?

When I use the IOCP log I see that the bit states are changing but the SIM does not do anything.

I will appreciate if you can clarify this.

Best Regards,

P.S. If what I am thinking is true and you used macros can you pls send the fsuipc.ini file so I can understand how u named them and compare with your code?

Barkay

[Georg Schneider]

Hi Barkay !

First of all thanks for your compliment;)
It took me some weeks to get the glue by myself with SIOC and OGS120.

So dont worry if something is unclear when you first start with SIOC and OGS.
I was reading OGS manual about 100 times to understand it.

OGS uses the IOCP client driver (IOCP variables) the OGS variables
are programmed into IOCP and must be below variable 1195.

The description of the used variables is at the end of OGS120 manual.

At the beginning of the SIOC script you define a base Var from where
your sioc script starts.
Also this base var must be defined in OGS.ini.

When you read the ogs manual you will see that every function has
its own numbers like
BIT NUMBER 3 for the 40NM position set on range selector

In the SIOC script 40NM switch is switched on with setbit=3
and switched off with clearbit=3

The CPTFLAGS and FOFLAGS are used to differ the captain and FO side.

When you look at the beginning of the SIOC script you see the inizialisation of the FLAGS.

CAPTAINFLAGS = base var(500+0) >>>>> 500

FOFLAGS = base var(500+1)>>>>>>>>>>501

You also need to look deeper in SIOC and IOCP manuals because
everything to descripe here in the forum will take me some weeks typing;)

The IOCP protokoll is similar to the FSUIPC protokoll from GENIUS
"PETER DAWSON":cool:.

SO !!! OGS120 talks to the FLIGHTSIM over the IOCP protokoll.

And the thing with macros with fsuipc is that i do not use em because
its right now not usefull for me.

I use now no more PMDG where you need the macros to achieve full
functionality.
I switched over as BETA TESTER to FLIGHTDECKSOFTWARE
which is similar to Projekt Magenta.
But a lot easyer to get everything running.

In my 737-800 pit now 5 PC`s are running for testing everything.
But the new Flightdecksoftware from Bart Devriendt is capable to run
Captain side and EICAS,MCP,CDU from one PC and FOside with IOCARDS
from OPENCOCKPITS and SIOC from second PC.

To run everything smoothly you normaly need a good FS9/FSX PC and one
good PC (CoreDUO 2,2GHZ and 2gig Ram and Geforce 8500-8600 with 512MB RAM)
And the third PC for the FOside you only need an Celeron with 1,6GHZ and
1GB Ram.

If you want to do yourself a favour leave the PMDG behind and start with
a good flightdecksoftware.

PMDG is great for only desctop computing but not for a real cockpit sim.

I hope i helped you a bit with some explanations!?

And read the manuals more and more times and try to get into SIOC
programming yourself and start with little testscripts for only one switch or so to see how all works.

And feel free to ask again you`re welcome !:D

With kind regards

George from Germany