LINDA - Fault Diagnosis Procedure - PLEASE READ

LINDA Problem and Fault Diagnosis - Guidance

LINDA users reporting problems or faults with LINDA would greatly assist in the diagnosis of their problem by providing the following information:

1. LINDA application version (go to LINDA Settings/About).

2. LINDA aircraft module name and version (in LINDA header).

3. FSX, Prepar3D (P3D) or MSFS version.

4. Aircraft supplier, model and version.

5. What were you trying to do (ie. connecting, programming functions, operating panel, etc).

6. A detailed description of what the problem is. Comments like “It doesn’t work” are not very helpful.

7. When requested or when red errors reported or when requested please do the following:

With LINDA 3.1.x and later

• Select Maintenance page.
• Click on Turn ON Fault Diagnosis Mode button.

With previous versions

• Go to LINDA Setup page.
• Tick Developer Mode, GUI and LUA boxes.
• Select VERBOSE from the download menu.
• Open Console.
• IMPORTANT. You may need to remove a block on logging in FSUIPCx.ini. You need to open it in the editor and search for the line LogOptionProtect and change it to NO. You will need to restart FSX/P3D after doing this.

Then

• Restart your Flt Sim and LINDA.
• Ensure that SYNC TO SIM is selected (aircraft outlined in orange).
• Run Flt Sim to reproduce error.
• Close down everything.
• Email FSUIPCx.LOG and LINDA2.LOG files (in /modules/ folder) together with the config-hid.lua or config-mcpX.lua for the aircraft you are using to LINDA @ awginfosys (dot) net (remove spaces).

NOTE: If you are sending .LUA files it would speed my analysis if you renamed the file to add a new .TXT extension.

With this information I will try to offer help to get users flying with LINDA.

Edited June 27, 20223 yr by ScotFlieger
Updated procedure for .txt extension