LINDA - Errors with Devices - PLEASE READ

[ScotFlieger 280]

Several users have reported various errors with devices not connecting to LINDA.  Some of these errors are related to newer USB devices such as touch screens and the wireless mice/keyboards.  To help you to get LINDA working, it is useful to know what device is causing the problem.

 

Please follow the following guidelines when reporting the error:

 

1.  Unplug the USB for all your devices (joysticks, throttles, touch screen), reboot your system and open LINDA.

 

2.  Plug in each device one-at-a-time and ensure that LINDA shows the device on the Summary and Setup Joysticks pages and that buttons are highlighted on the Joysticks page.

 

3.  If an error message is displayed, either as a pop up dialog or on the LINDA Console, note or take a screen shot of the full error message.

 

4.  Find and note the Vendor and Product IDs (VID and PID) as described below.

 

5.  Report your problem on the Support forum quoting the LINDA version you are using.

 

I will do my best answer your problem.

 

 

PID & VID

 

The PID and VID can be viewed by opening the Device Manager and looking under Human Interface Devices. Find the device that is not being recognised by LINDA and open the properties (double click or right click and select properties). Then under Details, select Hardware Ids from the Property dropdown.  The Vendor and Product IDs (VID/PID) appear in the first and second line as a 4 character hexadecimal number.

 

The VID and PID are used by LINDA to work out the type of device and whether it should be included in the list of devices.

 

 

 

UPDATE

 

Further investigation and testing by affected users has identified that the ‘Device cannot be opened’ errors are being generated by the third-party library routines used by LINDA to interface with HID devices. Even updating to the latest version of the library has not resolved the problem with certain devices.  There is nothing more I can do a this time with the LINDA code until the library is updated.  The only way forward I can suggest is for affected users to isolate the USB device that is stopping the others working and leave it disconnected.  Not a satisfactory situation I know. 

Edited December 22, 2014 by ScotFlieger
Update on source of issue