Hardware set-up is ... CPFlight USB MCP with EFIS, connected to MIP737 interface connected to a daisy chain with Nav1 & 2, ADF, Comm1 and ADF attached. CPFlight hardware test application used to confirm all buttons and switches work on MCP and MIP737 other modules.

When running FS9.1? and selecting the FSLabs driver version 1.02 the MCP rotaries work correctly. AT switch? and light works and dialled in speed selection controls engine speed with correct annunciation. FD switch operates and illuminates correctly. EFIS seems to operate correctly. However,

1. No MCP illuminated buttons light on selection (although it appears at least the speed?button seems to be working given the AT behaviour).

2. Selection of CMD A button displays the CWSR CMD and CWSP annunciations.

3. PFD annunciations appear to be erratic (but this may be due to uncertainty of selection with no illuminated button to confirm selection)

4. AP does not seem to engage.

5. FD annunciation often seems to be in opposition to the switch selection.

Sixpack works correctly and? some MIP LEDs appear to work correctly. However,

1. AFDS AP, AT and FMC lights do not seem to illuminate except on test.

2. Speedbrake do not arm, speedbrake armed and stab out of trim illuminate all the time.

3. Autobrake LED does not momentarily illuminate when operation of autobrake switch to off.

Any help or suggestions most welcome

Just in case others may have similar problems in the future. I determined the source of the problem with my particular set-up. I use a cut down version of the panel displaying this on a separate monitor to the outside visuals. The problem turned out to be that?certain gauges have to be loaded with the panel for?the FSLabs driver to fully function.

I was missing these gauges from the panel.cfg .....

'testpanel'

'Autobrakes'

'Autobrakes disarm'

Once these were loaded (albeit reduced in size and discreetly hidden by the MIP framework) with the gauges that I needed (MCP and ND), everything seems to function correctly.

Andy-

thanks for posting the solution here! I admit I was a bit stumped, because your issue was singular to your report... it's clearly advised that anyone seeking solutions to such problems should have the unaltered 737 product installed before reporting here... (or at least, checked first that a reinstall of their product doesn't fix the problem).