I have a non-plug-and-play IOcards flightdeck. I have been using it with iFLY with success and now would like to change to PMDG 737NGX. I found this document "Offset Mapping for PMDG 737NGX" but the offsets are read-only which means I can't have my iocards switches to control the PMDG panel. How do I get both read and write access?

 

BR,

Magnus

You need to use the SDK Control codes with FSUIPC to send values back to the NGX.

That link returns to this topis for me.

 

Does the SDK (software development kit?) requires Windows programming skills?

Is there a tutorial for making the required work?

 

I found MCP + EFIS already available as LUA's for SIOC.ini.

WIll the SDK when compiled end up in another LUA then?

 

Sorry, I really don't get the big picture of this....

You need to know how to program in C++ to use the SDK, yes.

I found these control codes in your blog. It works to control switches with the Saitek joystick, but not from my IOcards. How do I make the FSUIPC react to my IOcards?

Whoops, pasted the the link wrong. Shoud've been http://www.blueskies737.com/737ngx-control-codes/

 

With Opencockpits IOCards and SIOC you can have it trigger a virtual joystick button in FSUIPC with code like this:

 

Var 1 Link IOCARD_SW device 1 Input 55 Type I
{
&FO_JoyStick64 = CHANGEBIT 0 v1 // toggle button 0 of joystick 64 - STBY Mode
}
Var 2 name FO_JoyStick64 Link FSUIPC_OUT Offset $3340 Length 4

You are a god! 

Thank you, it works perfect!!

It worked with the first 23 switches. How do I continue? I am at $3364 now...

I tried to change joystick fro FO_JoyStick to C_JoyStick, but it does not recognise the C_JoyStick

You should be able to get 32 buttons on 9 virtual joysticks.  

 

The number after "changebit" is the button # and the offset is the Joystick number.

Now I get it! Next thing, "Length 4" makes other switches to also activate at the same time. "Length 1" solves this, but then only 8 sw per Joystick of course.... :-(

Hmmm...

 

When you adda  new 'VAR X' line and change the "0" to 1,2, etc...  are you also changing the v1 to match the var # it's inside?

Thanks again. It helped. Flaps won't move.I use the offset 76773 for retrecting it fully. But it does not move. FSUIPC picks it up (shows the 76773). In FSUIPC I entered value 0 for setting it and 1 for resetting it. Is that correct?

After restarting or reset the  FSX. FSUIPC not read any data? FSUIPC need reset too?

If you are working with Oencockpits IO-Cards and SIOC, you don't need FSUIPC for this.

Roar Kristensen made a driver for this, which can be found here: www.flightsim4fun.com/download.

 

For Plug-and-Play-modules he delivers even complete scripts, and two documents with all necessary events and offsets to make your own SIOC-scripts for non Plug-and-play instruments.