TorstenP

Today I tested your new exe file - unfortunately it dosen't work. But... I'm a little embarrassed, but the original application DOES run with both USB devices. It may be that I had included a few errors in the Lua code (sorry, but I can no longer trace it - I changed the code again and again). Here is the FSUIPC7.JoyScan.csv file no your request: Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk? ,,, HIDscanning completed ,,, REGscanning completed ,,, User settings imported ,,, Values matched and decided Your new program also wrote the same csv file. And, it gave an error on com.openhid(0x0, 0x11, 0, 0) 8687 LUA.3: Crash C0000005 at 7FFC143F6CBC: "D:\FSUIPC7\A320Rmp.lua" So the code change seems to be unsuccessful. However, the same line works with v7.2.13 and I cand send and receive data from the A320 RMP. The only remaining problem is that the device starts sending it status messages (with 20 Hz) right after the Lua script sends an message. And, it seems to not stop after FSUIPC is closed. At the next start of FSUIPC, the device is opened successfully, but sending a message fails. Restarting the device before the next FSUIPC start helps to establish a working connection again. I need to investigate that further. Many thanks again! Torsten

Hi John, both have really 0000 as vendor ID: Here is the output of HidScanner for USBkeys: Device at "\\?\hid#vid_0000&pid_0002#6&11466537&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0000, Product=0002 (Version 0.0) Manufacturer= Opencockpits Product= IOCardKEYS V2 Serial Number= IOCardKEYS V2 Usage Page: FF00 Input Report Byte Length: 9 Output Report Byte Length: 9 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 0 Number of InputValue Caps: 1 Number of InputData Indices: 8 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 8 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x01 at index 0, range 0 -> 255, using 8 bits Value 0x02 at index 0, range 0 -> 255, using 8 bits Value 0x03 at index 0, range 0 -> 255, using 8 bits Value 0x04 at index 0, range 0 -> 255, using 8 bits Value 0x05 at index 0, range 0 -> 255, using 8 bits Value 0x06 at index 0, range 0 -> 255, using 8 bits Value 0x07 at index 0, range 0 -> 255, using 8 bits Value 0x08 at index 0, range 0 -> 255, using 8 bits ************************************************************************** and here from the RMP module: Device at "\\?\hid#vid_0000&pid_0011#6&1566ae5b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0000, Product=0011 (Version 0.0) Manufacturer= Product= Serial Number= Usage Page: FFA0 Input Report Byte Length: 9 Output Report Byte Length: 9 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 0 Number of InputValue Caps: 2 Number of InputData Indices: 2 Number of Output Button Caps: 0 Number of Output Value Caps: 2 Number of Output Data Indices: 2 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x04 at index 0, range -128 -> 127, using 8 bits Value 0x03 at index 1, range -128 -> 127, using 8 bits ************************************************************************** Your idea with a "special" version sound good to me, mayn thanks for your support! Torsten

Hi, I have two USB cards from OpenCockpits (https://www.opencockpits.com), both have a vendor ID of 0000. Fortunately, the firmware of the UBSKeys card has strings for vendor and product, so opening it with com.openhid() works. The second card is installed in an Airbus A320 RMP and has no strings for the two IDs. Opening with com.openhid() does not work, although my tests in C and Lua with the hidapi library recognized and opened the device. Is it possible that FSUIPC does not accept a zero as vendor ID? If so, can this be corrected please? Best regards, Torsten