Re: OC MCP Displays go off after light test
Posted: Fri Aug 18, 2017 9:03 pm
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
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