Sorry. I do it without needing to think. Open LINDA and click on Editor (set Developer Mode in LINDA Setup if required). Click on Open and select common.lua from file menu.

The line numbers are displayed down the side. Alternatively, enter CMDRST in the Search box and press F3. This will find the line. Click at the being of the line containing CMDRST and type '--'. The line will turn orange (commented out).

Then close LINDA and restart LINDA and your Flt Sim.

 

O.k....thanks i will come back to you very soon.

 

Hi all,

I have exact the same problem as Ben mentioned in the beginning of this post. I bought a brand new VRinsight Boeing 2 MCP. I tried everything in this post but the MCP is not responding when Linda is used. With the VRI software it works. When I use Linda the VRI software is closed in the taskmanager. I would like to use Linda because it makes programming the MCP much easier. What I did:
- updated the FTDI driver to version 2.12.28.0 (speed set to 115200)
- FSUIPC version is 5.15 (in the fsuipc.ini is only COM3 present
- I tried different powered USB ports (energy saving is turned off)
- I use the latest Linda version
- Linda says everything is ok (3 times)
- I use windows 10 pro x64 version Build 10.0.17763 Version 1809

Has anyone a suggestion what to do? Thanks in advance.

Kind Regards, Hans
 

 

Hi Hans

I do not have any good news for your. I can not explain why some users (several with new panels) are having problems. I am using the latest version of Win10 as new and I am not seeing any problems. If I could reproduce the fault I would be half way to finding the cause.

Please try this test build of LINDA 3.0.11 and use FSUIPC5 5.15h with the extra VRIDisableCMDRST=Yes in the [General] section. This build comments out the CMDRST statement in common.lua.

Email me your fsuipc5.log file.

 

 

Edited February 3, 20197 yr by ScotFlieger

Hi Scot thanks for your quick response. When I unzip the test build it gives that it is corrupt. Can you check this? Thanks.

 

 

Edited February 3, 20197 yr by Hans_11

6 minutes ago, Hans_11 said:

Hi Scot thanks for your quick response. When I unzip the test build it gives that it is corrupt. Can you check this? Thanks.

The download link is valid and unzips for me on my Mac but not on Windows. I hate Windows.

Edited February 3, 20197 yr by ScotFlieger

Try again.

Hi Scot I did all three. The difference now is that I see SPD HDG ALT V/S and the COM radio on my Combo 2. I didn't see them earlier when using Linda. When I change these in the cockpit I see them changing on my combo panel. When I turn the knobs or push for example the NAV button on my combo they don't work. I will sent you my fsuipc log file before and after. Thanks again.

Greets, Hans

Edited February 3, 20197 yr by Hans_11

Hi Hans

That is good news. At least the Combo panel is not disconnecting with the workarounds (ie. no CMDRST reset or LIGHTS on).

Which aircraft are you using? For the buttons and knobs to work you need the correct functions assigned. Not all aircraft have the required config-mcpX.default defined.

To email me the logs use linda @ awginfosys.net (without the spaces).

Scot, I used the Maul M7 260C (standard P3D V4.4). When I use the PMDG 737-800 NGX SPD, HDG, ALT and V/S are not changing on the combo when changed in the cockpit. The only radio I see on my combo is COM1. When I change it in the cockit I see that on my combo. No response when using the combo.

I sent you a private message with my old and new fsuipc log files in text.

 

See my reply to your message.

I suspect your config-mcp2.lua file is corrupt. Open directory /modules/LINDA-cfg/aircrafts/pmdg 737 and check that there are 3 config-mcpX.default files present. If so delete the config-mcpX.lua files and restart LINDA and P3D. This should create working copies of the appropriate configuration files. 

Andrew thanks again. I'll try it tomorrow evening.

 

20 hours ago, Bentree_ said:

O.k....thanks i will come back to you very soon.

Hi Ben

Thank you for these logs. They are very revealing and show that FSUIPC is correctly connecting to the panel and this is enabling LINDA to communicate. Switching the LAMP button and the panel going to "sleep" (stops responding) proves that the power spike is the source of your problems. For future operations, turn on the panel lights before you start P3D if you require them.

 

With the workaround FSUIPC 5.15h installed, I am also experiencing the non-operation of the knobs and buttons on the MCP Combo panel. Now I have been able to reproduce this problem I can now start investigating the cause. Please standby.

 

 

Update: Although the test FSUIPC build 5.15h allows problematic panels to connect, it stops FSUIPC and therefore LINDA receiving inputs from the panel buttons and knobs. Investigation continues.

In meantime, this test build of LINDA 3.0.11 v3 corrects error with default aircraft configurations.

 

Edited February 4, 20197 yr by ScotFlieger
Link fixed

Hi Andrew,

It is very good news that we seem to approach some solutions. Thanks for your endless efforts.

It would be great if we where able to get the MCP Combo to work with the Leonardo MD82, this was the reason for me to purchase the MCP Combo in the first place. (i do not fly the default aircraft, but good to hear the combo is working for those).

The workaround for the LAMP button is totally no problem.

Anxiously standing by for more news....

Regards,

Ben