Oi4FS support

[Splitpin]

Thanks again for your reply and exhaustive research, that sounds great. I think I understand the programming, just didn't know where to start - it's been a long time for an aging brain.
Another question - on my equally aging v2 MCP, I think I remember that while the Heading knob seems to have a click in/out - that it's not functionable - do you know ? I had an idea to make that click grab the current heading if I could.

[mvr1918]

If MCPv2 has the HDG button together with the HDG SEL they should work as follows:

An HDG button push sync the heading to the actual airplane heading
An HDG SEL sets the heading to what is shown in the HDG display and set AP in HDG mode

here are the buttons numbers, you can check in SIOC's SIOC Monitor if your HDG button is working

Var 0213, name D_CrsR, static, Link IOCARD_DISPLAY, Device 15, Digit 19, Numbers 3
Var 2070, name sFD_L, static, Link IOCARD_SW, Device 15, Input 16
Var 2071, name sAT_ARM, static, Link IOCARD_SW, Device 15, Input 33
Var 2072, name sDISENGAGE, static, Link IOCARD_SW, Device 15, Input 15
Var 2073, name sFD_R, static, Link IOCARD_SW, Device 15, Input 14

Var 2050, name bN1, static, Link IOCARD_SW, Device 15, Input 32, Type I
Var 2051, name bSPEED, static, Link IOCARD_SW, Device 15, Input 31, Type I
Var 2052, name bSPD_INTV, static, Link IOCARD_SW, Device 15, Input 37, Type I
Var 2053, name bCO, static, Link IOCARD_SW, Device 15, Input 13, Type I

Var 2054, name bVNAV, static, Link IOCARD_SW, Device 15, Input 30, Type I
Var 2055, name bLVL_CHG, static, Link IOCARD_SW, Device 15, Input 29, Type I
// this is fix to enable FLC as no Simconnect Event exist
{
&FO_JoyStick64 = CHANGEBIT 0 v2055 // toggle bit 0 of joystick 64
}
Var 2056, name bHDG, static, Link IOCARD_SW, Device 15, Input 34, Type I
Var 2057, name bHDG_SEL, static, Link IOCARD_SW, Device 15, Input 28, Type I
Var 2028, name sBANKING_SEL, static
Var 2059, name bLNAV, static, Link IOCARD_SW, Device 15, Input 27, Type I
Var 2060, name bVOR_LOC, static, Link IOCARD_SW, Device 15, Input 20, Type I
Var 2061, name bAPP, static, Link IOCARD_SW, Device 15, Input 24, Type I
Var 2062, name bALT_HLD, static, Link IOCARD_SW, Device 15, Input 23, Type I
Var 2063, name bALT_INTV, static, Link IOCARD_SW, Device 15, Input 36, Type I
Var 2064, name bVS, static, Link IOCARD_SW, Device 15, Input 22, Type I
Var 2065, name bCMD_A, static, Link IOCARD_SW, Device 15, Input 21, Type I
Var 2066, name bCSW_A, static, Link IOCARD_SW, Device 15, Input 20, Type I
Var 2067, name bCMD_B, static, Link IOCARD_SW, Device 15, Input 19, Type I
Var 2068, name bCWS_B, static, Link IOCARD_SW, Device 15, Input 18, Type I

I can make a modified script for MCPv2 user, but needs to get more info about the 3rd VS digit behavior

- start SIOC and go to IOCPConsole and Connect
-write a new number to 3rd digit (var 210 in IOCPConsole) Does it react to this?
-write a new number to 4th digit and then to 3rd digit(Var 211 and Var 210) any changes?

[Splitpin]

In response to the testing of..

[ - start SIOC and go to IOCPConsole and Connect
-write a new number to 3rd digit (var 210 in IOCPConsole) Does it react to this?
-write a new number to 4th digit and then to 3rd digit(Var 211 and Var 210) any changes? }

Started SIOC -> IOCPConsole and connected
write a new number using Var Number box and Value box writing to 210 no response at all (but it does remember the last value sent see below)
write a new number - writing to 211 yes it responds in hardware, 4th and 3rd digits are refreshed last value sent to 210 shows correctly. Setting 210 = 4 then setting 211 = 2 displays 2400

write a number to the 4th digit (shows) then write a new number to the 3rd digit - does not show any change

In use in sim using the VS wheel, the VS display responds with every 1000 change, continuing to dial the wheel through the hundreds shows no change until you get to the next thousand which shows as expected. This works in both + and - directions and at passing 0

Hope this helps

[mvr1918]

A new updated Oi4FS script has been emailed to you for testing.

[Splitpin]

Hi Roar

Partial success, from 0 to 1000 shows no change, but from 1000 it works perfectly 1100, 1200, 1300 etc.
Going backwards (down) from say 1500 shows 1500, 1400, 1300, 1200, 1100, 1000, 900 but stops showing change there.

Thanks
John

[mvr1918]

Open Edit Script in SIOC and change the value -999999 to -999998
and click OK and retest.

That should do it.

[Splitpin]

Hi Roar

I think you've nailed it. A quick test and it seems to be working as desired.
'think' because it had to be a quick test, I'll give it a more thorough workout tomorrow but it does seem to be working now with the &D_VS4 change = 999998

Thanks
John

[Splitpin]

Hi Roar

Yes confirmed, V/S of the v2 MCP is working perfectly now.
Even in the rough weather over the highlands of PNG where it had a busy workout I couldn't fault it.
Thanks very much for your efforts.

John

[mvr1918]

OK, fine.

The new updated Oi4FS script for MSFS default airplanes that solves the MCPv2 VS display issue will be included in the next Oi4FS package update( after an updated MSFS SDK SimConnect is released).

If any MCPv2 customers want this driver update before the next updated Oi4FS is released, send an email to roarkrsp@gmail.com

[joeair]

Hello,
is it possible to integrate the multiradio from oc into a script for oi4fs?
Oc has also no script for sioc and uses its own app for this.
It would be fine that would also be included in the oi4fs.

Thanks for answer, Joachim