SIOC Pre compiler

[fordgt40]

Peter

Thanks for your kind offer of help, it is appreciated. I think that there are different expectations and understandings of what Chris is trying to do. I have persevered with SIOC and have a reasonable understanding, however, still welcome what Chris is trying to do as it would make my life easier.

There is no magical solution that will enable all to instantly programme SIOC, but anything that eases the syntax, colour code expressions and can easily highlight all instances of variables can only help some and more importantly encourage others to take the plunge. The way forward is to expand the usage of SIOC.

Regards

David

[kiek]

Hi guys,

I'd like to give an example of how simple SIOC scripts can be ...
Especially if you build for the Level-D 767 and you run my free lekseecon.exe program in the background, it is merely just a number of 'one liners'.

Suppose I want to connect three push buttons as MCP CMD L, MCP CMD C and MCP CMD R switch.

For each switch you only have to define one (!) line of SIOC code, like this:

Var 275 Link IOCARD_SW Input 5 Type P // CMD L
Var 276 Link IOCARD_SW Input 6 Type P // CMD C
Var 277 Link IOCARD_SW Input 7 Type P // CMD R

SIOC variable numbers 275, 276 and 277 are predefined by my lekseecon tool and are implicitly linked by lekseecon at run time to the Level-D.
These variable are the control variables for the switches in the Level-D panel. If the variable is 1 the switch will be ON, if it is 0 the switch will be OFF.

You only have to understand what the Variable attributes mean:
* Link IOCARD_SW means that the variable is linked to an IOCard switch;
* Input 5 means that the switch is connected to Input 5 of a Mastercard;
* Type P means that the switch is a push button, each time you push the button the Variable connected to it changes from 0 -> 1 or
from 1 -> 0.

The var numbers 275, 276 and 277 are only used in these lines, they will not appear anywhere else in the script so no need here for tools to find these places.

regards,

Nico

[pdpo]

Hi Niko,

be carefull with the examples form your LEKSECON, they are only valid if working with your program and with the LEVEL_D. The logic which needs to be put into SIOC and interact with FS is taken care of by your superb application. Therefor your sioc script has become merely a definition part to tell which inputs, which outputs, which displays.
If all addon planes (like PSS, like PMDG,..) would have such extensive SDK as the level-D there would be no more need for SIOC, just an application for each like your leksecon and cockpitbuilding would become a breeze.... lets hope the future turns in that direction

Greetz Peter

[weyes]

Yes, I agree with Peter.

If eveyrbody with every airplane could use lekseecon then tehre would be no need to think of a improved SIOC.

[kiek]

Hi,

it was a teaser... one can always switch to the 767...

For other airplanes using FSUIPC offsets it is just a tiny little bit more complex, you need two var definitions (instead of 1).

A first variable to make the FSUIPC offset available, and a second variable that relays the values from the switch to the FSUIPC var:

Var 1 name CMDL Link FSUIPC_OUT Offset $8b0A Length 2
Var 2 name CMDSwitch Link IOCARD_SW Input 5 Type P // CMD L
{
&CMDL = &CMDSwitch
}

And again, these two var declarations can be placed together in your SIOC script. These variable numbers or variable names will not be used anywhere else, no need for tools to highlight that.


But I'm always available to answer questions, here or in the Opencockpits fora,

Nico

[MortenHa]

Well, I said it was a brilliant idea, althought I'll never use it myself
I was of course thinking about those of you who do not know the nuts & bolts of programming.

I thought it might help...

I also warned Chris on how big this project could become if he went full throttle with this. It would take a considerable amount of time to make it user-friendly on a novice level (assuming nothing about Chris's programming skills, any project with such parameters is time consuming).

But look on the bright side!
The use of editors suitable for writing code has been discussed, as well as the well of information available among fellow builders.

So if there's a code problem, post it here!

There's help to be found

Cheers!

Morten

[fordgt40]

Nico

I wonder from how many sources the routine to light up the master caution and fire warning lights might be called?

Just a little teaser

Regards

David

[ian@737ng.co.uk]

Var 1 name CMDL Link FSUIPC_OUT Offset $8b0A Length 2
Var 2 name CMDSwitch Link IOCARD_SW Input 5 Type P // CMD L
{
&CMDL = &CMDSwitch
}

see, i told you it was like learning to write chinese !
just another teaser (no i mean it) ))

ciao ... ian

[kiek]

Var 1 name CMDL Link FSUIPC_OUT Offset $8b0A Length 2
Var 2 name CMDSwitch Link IOCARD_SW Input 5 Type P // CMD L
{
&CMDL = &CMDSwitch
}
see, i told you it was like learning to write chinese !
just another teaser (no i mean it) ))

LOL, writing chinese is a lot more difficult in my opinion...

However, if you do not understand these 5 lines, you made a wise decision to forget about SIOC.

nico

[kiek]

I wonder from how many sources the routine to light up the master caution and fire warning lights might be called?

Just a little teaser

David,
In my Level-D, the master caution light is controlled at only one place, just like the Gear indicator light in this annotated example:
http://www.lekseecon.nl/images/lekse...nno_output.htm



Regards,
Nico