flatdog Posted September 19, 2011 Report Share Posted September 19, 2011 Has anyone tried using one of these: http://www.flightsimparts.eu/Shop_Electronics_Pokeys55.html with FSUIPC. It is seen by Windows as a 'virtual joystick' and is listed with a GUID (and assigned a letter) in my FSUIPC.INI file. Switches attached to the card are recognised in ProSim and Windows game controller setup but I cannot get any response to a button click (or keypress)in the FSUIPC interface. Buttons connected to a BU0386X card are detected perfectly by FSUIPC. Thank you. Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 19, 2011 Report Share Posted September 19, 2011 Has anyone tried using one of these: http://www.flightsim...s_Pokeys55.html with FSUIPC. It is seen by Windows as a 'virtual joystick' and is listed with a GUID (and assigned a letter) in my FSUIPC.INI file. Switches attached to the card are recognised in ProSim and Windows game controller setup but I cannot get any response to a button click (or keypress)in the FSUIPC interface. Buttons connected to a BU0386X card are detected perfectly by FSUIPC. Does FS itself see them? If so, as what button numbers? FSUIPC3 uses the basic windows joystick API (like FS98 and FS2000 used to), and it may just be that the device isn't compatible with that. FSUIPC4 uses the same methods as FSX. There's a utility program called "HidScanner" available in the Download Links subforum (in the "Latest Lua" thread). If you run that it will show details about all the HID joystick devices on your system. find that card and show me the extract from the Log it produces. If you are using FS9 or before, and the device isn't compatible with the basic joystick interface, then the only way to access the buttons in FSUIPC would be via a Lua plug-in using the Hid functions in the COM library. Regards Pete Link to comment Share on other sites More sharing options...
flatdog Posted September 19, 2011 Author Report Share Posted September 19, 2011 I am using FSX and FSUIPC 4.728 I have attached the HID Scanner log below. I should correct what I said earlier. I have a simple throttle connected to one of the analogue inputs on the card which can be calibrated in FSUIPC and works in FSX. I have a couple of inputs set using the POKeys software to emulate F6 & F5 which are seen as a keypress by FSUIPC and work in FSX. I have a switch connected to the card to operate the parking brake which is seen by ProSim 737, operates the parking brake on the default 737-800 when ProSim is running but is not seen as a button press by either the windows game controller setup or FSUIPC. It does not operate the parking brake in FSX if ProSim is not running. I should say that I have just started experimenting with this card as it is relatively inexpensive and seems to have a lot of features. I cannot claim to understand 100% exactly what it is doing but I notice that in the log file one of the two entries for the card describes it as a 'virtual keyboard'. Thank you. ********* HidScanner, Version 2.00 by Pete Dowson ********* Device at "\\?\hid#vid_044f&pid_b108#8&368b84a9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=044F, Product=B108 (Version 1.0) Manufacturer= Thrustmaster Product= T.Flight Hotas X Serial Number= Usage Page: 1 Input Report Byte Length: 23 Output Report Byte Length: 3 Feature Report Byte Length: 13 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 18 Number of InputData Indices: 30 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 1 Number of Feature Button Caps: 0 Number of Feature Value Caps: 3 Number of Feature Data Indices: 3 Buttons range 1 -> 12 at indices 0 -> 11 Value POV at index 12, range 0 -> 7, using 4 bits Value X at index 13, range 0 -> 1023, using 10 bits Value Y at index 14, range 0 -> 1023, using 10 bits Value Sldr at index 15, range 0 -> 255, using 8 bits Value R/RZ at index 16, range 0 -> 255, using 8 bits Value Z at index 17, range 0 -> 255, using 8 bits Value 0x2B at index 18, range 0 -> 255, using 8 bits Value 0x2A at index 19, range 0 -> 255, using 8 bits Value 0x29 at index 20, range 0 -> 255, using 8 bits Value 0x28 at index 21, range 0 -> 255, using 8 bits Value 0x27 at index 22, range 0 -> 255, using 8 bits Value 0x26 at index 23, range 0 -> 255, using 8 bits Value 0x25 at index 24, range 0 -> 255, using 8 bits Value 0x24 at index 25, range 0 -> 255, using 8 bits Value 0x23 at index 26, range 0 -> 255, using 8 bits Value 0x22 at index 27, range 0 -> 255, using 8 bits Value 0x21 at index 28, range 0 -> 255, using 8 bits Value 0x20 at index 29, range 0 -> 255, using 8 bits ************************************************************************** Device at "\\?\hid#vid_045e&pid_00f9&mi_00#a&32dd356b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=045E, Product=00F9 (Version 0.3) Manufacturer= Microsft Product= Microsoft Wireless Desktop Receiver 3.1 Serial Number= Microsoft Wireless Desktop Receiver 3.1 Device is a keyboard Usage Page: 1 Input Report Byte Length: 9 Output Report Byte Length: 2 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 154 Number of Output Button Caps: 2 Number of Output Value Caps: 0 Number of Output Data Indices: 4 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_045e&pid_00f9&mi_01&col01#a&1fad192d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=045E, Product=00F9 (Version 0.3) Manufacturer= Microsft Product= Microsoft Wireless Desktop Receiver 3.1 Serial Number= Microsoft Wireless Desktop Receiver 3.1 Usage Page: C Input Report Byte Length: 4 Output Report Byte Length: 0 Feature Report Byte Length: 2 Number of Link Collection Nodes: 2 Number of Input Button Caps: 3 Number of InputValue Caps: 4 Number of InputData Indices: 7 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 1 Number of Feature Value Caps: 2 Number of Feature Data Indices: 3 Value Wh at index 0, range -127 -> 127, using 8 bits Value 0x01 at index 1, range 0 -> 3, using 2 bits Value 0x03 at index 4, range 0 -> 3, using 2 bits Value 0x0D at index 6, range 0 -> 65535, using 16 bits ************************************************************************** Device at "\\?\hid#vid_045e&pid_00f9&mi_01&col02#a&1fad192d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=045E, Product=00F9 (Version 0.3) Manufacturer= Microsft Product= Microsoft Wireless Desktop Receiver 3.1 Serial Number= Microsoft Wireless Desktop Receiver 3.1 Device is a mouse Usage Page: 1 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 2 Number of Link Collection Nodes: 5 Number of Input Button Caps: 1 Number of InputValue Caps: 4 Number of InputData Indices: 9 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 2 Number of Feature Data Indices: 2 Buttons range 1 -> 5 at indices 0 -> 4 Value Y at index 5, range -127 -> 127, using 8 bits Value X at index 6, range -127 -> 127, using 8 bits Value Wh at index 7, range -127 -> 127, using 8 bits Value Wh at index 8, range -127 -> 127, using 8 bits ************************************************************************** Device at "\\?\hid#vid_045e&pid_00f9&mi_01&col03#a&1fad192d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=045E, Product=00F9 (Version 0.3) Manufacturer= Microsft Product= Microsoft Wireless Desktop Receiver 3.1 Serial Number= Microsoft Wireless Desktop Receiver 3.1 Usage Page: C Input Report Byte Length: 8 Output Report Byte Length: 0 Feature Report Byte Length: 2 Number of Link Collection Nodes: 4 Number of Input Button Caps: 8 Number of InputValue Caps: 9 Number of InputData Indices: 1549 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 2 Number of Feature Data Indices: 2 Value 0x0E at index 1280, range 0 -> 255, using 8 bits Value 0x05 at index 1283, range 0 -> 31, using 5 bits Value 0x02 at index 1539, range 1 -> 255, using 8 bits Value Wh at index 1540, range -127 -> 127, using 8 bits Value Wh at index 1541, range -127 -> 127, using 8 bits Value 0x02 at index 1542, range 0 -> 255, using 8 bits Value 0x01 at index 1543, range 0 -> 3, using 2 bits Value 0x03 at index 1546, range 0 -> 3, using 2 bits Value 0x0D at index 1548, range 0 -> 65535, using 16 bits ************************************************************************** Device at "\\?\hid#vid_045e&pid_00f9&mi_01&col04#a&1fad192d&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=045E, Product=00F9 (Version 0.3) Manufacturer= Microsft Product= Microsoft Wireless Desktop Receiver 3.1 Serial Number= Microsoft Wireless Desktop Receiver 3.1 Usage Page: 1 Input Report Byte Length: 2 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 1 Number of InputValue Caps: 0 Number of InputData Indices: 256 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_06c2&pid_004c#9&1205cc9c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=06C2, Product=004C (Version 1.0) Manufacturer= Phidgets Inc. Product= PhidgetLED Serial Number= 114517 Usage Page: FFA0 Input Report Byte Length: 42 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: 1 Number of Output Button Caps: 0 Number of Output Value Caps: 1 Number of Output Data Indices: 1 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Value 0x02 at index 0, range 0 -> 1, using 8 bits ************************************************************************** Device at "\\?\hid#vid_1dc3&pid_1001&mi_00#a&11f44069&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Virtual Joystick Serial Number= 1.12090 Usage Page: 1 Input Report Byte Length: 17 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 2 Number of Input Button Caps: 1 Number of InputValue Caps: 6 Number of InputData Indices: 38 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 Buttons range 1 -> 32 at indices 6 -> 37 Value U/RX at index 0, range 0 -> 1023, using 16 bits Value V/RY at index 1, range 0 -> 1023, using 16 bits Value Z at index 2, range 0 -> 1023, using 16 bits Value Y at index 3, range 0 -> 1023, using 16 bits Value X at index 4, range 0 -> 1023, using 16 bits Value Thr at index 5, range 0 -> 1023, using 16 bits ************************************************************************** Device at "\\?\hid#vid_1dc3&pid_1001&mi_01#a&29b7ccae&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Communication Interface Serial Number= 1.12090 Usage Page: FF00 Input Report Byte Length: 65 Output Report Byte Length: 65 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: 1 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 ************************************************************************** Device at "\\?\hid#vid_1dc3&pid_1001&mi_02#a&5e08eec&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Virtual keyboard Serial Number= 1.12090 Device is a keyboard Usage Page: 1 Input Report Byte Length: 35 Output Report Byte Length: 0 Feature Report Byte Length: 0 Number of Link Collection Nodes: 1 Number of Input Button Caps: 2 Number of InputValue Caps: 0 Number of InputData Indices: 110 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 0 Number of Feature Data Indices: 0 ************************************************************************** Device at "\\?\hid#vid_1dd2&pid_1001#8&276e438c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DD2, Product=1001 (Version 1.35) Manufacturer= Leo Bodnar Product= BU0836X Interface Serial Number= B07471 Usage Page: 1 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 1 Number of InputData Indices: 33 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 0 -> 31 Value POV at index 32, range 0 -> 7, using 4 bits ************************************************************************** Device at "\\?\hid#vid_1dd2&pid_1001#8&3288478d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DD2, Product=1001 (Version 1.33) Manufacturer= Leo Bodnar Product= BU0836X Interface Serial Number= B07138 Usage Page: 1 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 1 Number of InputData Indices: 33 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 0 -> 31 Value POV at index 32, range 0 -> 7, using 4 bits ************************************************************************** Device at "\\?\hid#vid_1dd2&pid_1001#9&11bc8276&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DD2, Product=1001 (Version 1.35) Manufacturer= Leo Bodnar Product= BU0836X Interface Serial Number= B20384 Usage Page: 1 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 1 Number of InputData Indices: 33 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 0 -> 31 Value POV at index 32, range 0 -> 7, using 4 bits ************************************************************************** Device at "\\?\hid#vid_1dd2&pid_1001#9&3427402a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=1DD2, Product=1001 (Version 1.35) Manufacturer= Leo Bodnar Product= BU0836X Interface Serial Number= B18398 Usage Page: 1 Input Report Byte Length: 6 Output Report Byte Length: 0 Feature Report Byte Length: 18 Number of Link Collection Nodes: 3 Number of Input Button Caps: 1 Number of InputValue Caps: 1 Number of InputData Indices: 33 Number of Output Button Caps: 0 Number of Output Value Caps: 0 Number of Output Data Indices: 0 Number of Feature Button Caps: 0 Number of Feature Value Caps: 1 Number of Feature Data Indices: 1 Buttons range 1 -> 32 at indices 0 -> 31 Value POV at index 32, range 0 -> 7, using 4 bits ************************************************************************** Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 19, 2011 Report Share Posted September 19, 2011 I notice that in the log file one of the two entries for the card describes it as a 'virtual keyboard'. If it is sending keypresses then, yes, it's more a keyboard than a joystick, or maybe it can be both or either. I did Google it and found a description which includes: Standard USB joystick simulation (6 axis, 32 buttons with triggering support). Now if that is true then all of thsoe 6 axes and 32 buttons should be detected in FSUIPC4 (and FSX for that matter). If they are not then it is likely that you need to do some configuring using the software supplied with the card. After all, it does say: All the I/O are controlled by the provided software which allows either to use the graphical user interface or advanced console type interface. The settings can be stored on the device, so no special software is needed on target system. I see you included the whole of the HidScanner log, which wasn't needed. But there are actually three entries for the PoLabs device: Manufacturer= PoLabs Product= Virtual Joystick which certainly does have 32 buttons and the usual 6 axes: Buttons range 1 -> 32 at indices 6 -> 37 Value U/RX at index 0, range 0 -> 1023, using 16 bits Value V/RY at index 1, range 0 -> 1023, using 16 bits Value Z at index 2, range 0 -> 1023, using 16 bits Value Y at index 3, range 0 -> 1023, using 16 bits Value X at index 4, range 0 -> 1023, using 16 bits Value Thr at index 5, range 0 -> 1023, using 16 bits the other two devices it presents are: Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Communication Interface which is presumably its programming interface, used by its own software only, and Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Virtual keyboard Your "virtual keyboard". One point that does come to mind is that FSUIPC only handles the first 16 joystick devices, those assigned an ID by windows of 0 to 15. This is the "joystick number" it uses. I'm wondering now, with all those devices you have connected, whether Windows is actually assigning an ID in the range FSUIPC can handle. Please check the FSUIPC4.INI file. You'll find a section in there entitled "[Joynames]". See if the device is listed there. if so you should be good to go. If not then its either some configuring at the card which is needed, or you'd need to resort to a Lua plug-in. The latter could certainly handle the "virtual joystick" device. Regards Pete Link to comment Share on other sites More sharing options...
flatdog Posted September 19, 2011 Author Report Share Posted September 19, 2011 OK - sorted. As you suggested it was a configuration issue. It is necessary not only to configure the port on the card as a digital input but then to also map the port to a joystick button using the peripherals / joystick menu. I have attached an image in case it is of use to anyone else. Thank you for pointing me in the right direction. Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 19, 2011 Report Share Posted September 19, 2011 OK - sorted. As you suggested it was a configuration issue. It is necessary not only to configure the port on the card as a digital input but then to also map the port to a joystick button using the peripherals / joystick menu. I have attached an image in case it is of use to anyone else. Thank you for pointing me in the right direction. Glad you resolved it. If it is likely to help others, do you think you could re-post your helpful pix in the User Contributions subforum, please? Thanks, Pete Link to comment Share on other sites More sharing options...
tlhflfsx Posted September 21, 2011 Report Share Posted September 21, 2011 I have been using a PoKeys55T for a few of months. I found that even though the PoKeys device will only map 32 buttons in the joystick configuration. (The 32 buttons is a windows limitation for joystick units) I was able to have all 55 buttons used by FSX as follows. First I mapped the 32 buttons possible in the PoKeys joystick configuration. (Six of the buttons are the -/+ output from three encoders). These 32 buttons are configured in FSUIPC in the "Buttons + Switches" tab Next I mapped the remaining buttons on the PoKeys to emulate keyboard outputs that I know FSX does not use ( example: <control> <shift> <A>). These buttons are than configured in FSUIPC in the "Key Presses" tab. In addition to using the PoKeys55T for input to FSX I also use the PoKeys55T device to turn on / off various LED's from lua events scripts. Hope this information is helpful. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now