Page 2 of 2

Re: OC MCP Displays go off after light test

Posted: Fri Aug 18, 2017 9:03 pm
by mvr1918
The whole CDU script logic now has disappeared from the script and is now handled
directly in the driver code.

This means that you have to make some online modification from your actual hardware to the default hardware input to the Var 1999.

Try ( not tested, just from top off my head)

Var 0622, name CDU1_My, Link USB_KEYS, Device 13 // FMC/CDU1_CAPT
{
if &CDU1_My = 39 // menu button on your HW
{
&CDU1 = 71 // menu button on default HW
}
.... etc...

Var 1999, name CDU1, static
--------

The index 71 points to 2156 in the array

I use in the driver


0000,2129,2175,2132,2176,2183,2162,2114,2135,2182,
2181,2180,2179,2178,2123,2122,2121,2177,2174,2166,
2165,2161,2120,2119,2118,2160,2157,2155,2147,2146,
2117,2116,2115,0000,0000,0000,0000,0000,0000,0000,
0000,0000,0000,0000,0000,0000,0000,0000,0000,2145,
2143,2141,2140,2138,2159,2163,2148,2136,2131,2127,
2125,2124,2139,2158,2149,0000,2137,2164,2142,2133,
2154,2156,2150,0000,2172,2134,2130,2128,2173,2144,
2151,0000,2171,2170,2169,2168,2167,2153,2152

Re: OC MCP Displays go off after light test

Posted: Sat Aug 19, 2017 5:28 pm
by seedosip
Hi Roar,
Thanks for reply, thats what I though when I have seen a new script, all the logic is in the driver.

I have tried just one button, Menu and it does work! Have to re-program the rest of the script. I can forward you the completed script in case someone else would need it, just the numbering would have to be change like in the old script.

I bet it has to be simple, but I cannot figure out how 2156 is button 71 in case of CDU Menu button...?
Could you please give me a hint on how to count? In case of Perf Init (2144) would that be button 1? 79?

Thanks a lot for your help.

Kind regards,
Sergej

Re: OC MCP Displays go off after light test

Posted: Sat Aug 19, 2017 5:46 pm
by mvr1918
0000,2129,2175,2132,2176,2183,2162,2114,2135,2182,
2181,2180,2179,2178,2123,2122,2121,2177,2174,2166,
2165,2161,2120,2119,2118,2160,2157,2155,2147,2146,
2117,2116,2115,0000,0000,0000,0000,0000,0000,0000,
0000,0000,0000,0000,0000,0000,0000,0000,0000,2145,
2143,2141,2140,2138,2159,2163,2148,2136,2131,2127,
2125,2124,2139,2158,2149,0000,2137,2164,2142,2133,
2154,2156,2150,0000,2172,2134,2130,2128,2173,2144,
2151,0000,2171,2170,2169,2168,2167,2153,2152

are

0,1,2,3,4,5,6,7,8,9
10,11.....
etc.

so 2144 would be 79

Re: OC MCP Displays go off after light test

Posted: Sun Aug 20, 2017 10:29 am
by seedosip
Indeed was very simple :) Somehow I was starting the count from 1 and not from 0.

All buttons work fine but during testing I have found one issue: I cannot press the same button twice, another button has to be pressed. For example entering ICAO LEBB is not possible, I can enter LEB and any other letter but not last B.
Same thing happens with numbers, for ZFW 55.2 cannot be entered 54, 2 or 56.2 no problem. Somehow same digit/letter cannot be repeated. I have tried with space and del, but does not work either.
Something to do with driver?


Kind regards,
Sergej

Re: OC MCP Displays go off after light test

Posted: Sun Aug 20, 2017 11:39 am
by mvr1918
A bug in script. Will be correted in the next beta build.

In the meantime, just add
{
&CDU1 = 0
}

after the Var 1999


{
&CDU2 = 0
}

after the Var 1998

AS SIOC do not act before a change of Var value has happen, it must be reset.