tomahawk66

Hi everyone, Great information in this thread! I am also considering replacing the worn-out spiking trim pots on my Saitek throttle quadrant. However I wonder if someone could please clarify a couple of things for me. (1) When I inspect the rotation angle of the lever, it is about 85 degrees, about 80 degrees of rotation in the potentiometer range and about 5 degrees in the detent (switch) range. However, in post #7, Sokol1_br writes of a resistive trail of 30 deg to 50 deg. Which is it? (2) The pot when inserted in the Saitek quad behaves as if it has a switch in the detent at the lower extreme. How is this achieved practically? Is it done via the firmware flashed to the controller? Note that the potentiometer itself does not have a switch at either extreme. Thank you! Chakko.

Hi overpro and Maximvs, Just a reminder that if Maximvs is using your 1HID*256 buttons version, then, as we discussed in posts #142 and #144 and #153: (i) Pointy's joystick test will not work (ii) SV Mapper will work, but only for the first 128 buttons......the remaining show spurious returns (iii) FSUIPC + LUA is successfully able to handle all 256 buttons Regards, Chakko.

Hi again, overpro, I cannot thank you enough for the time and trouble you have taken to create the alternative 256-button*1HID version of your firmware. Fantastic contribution to our hobby! :v: It occurred to me that in situations where one is attaching more than one such Arduino HID-joystick to the (FSX/FSUIPC) PC, it would help to identify each Arduino with a unique serial number, so that each could be associated definitely with a separate cockpit device. This has been a useful feature of Bodnar and Pokeys cards that I have also been using. As I understand it, each Arduino programmed with your firmware will have the serial number 'C2', and this has the potential to cause confusion when more than one is attached. Is there any simple way of 'stamping' unique serial numbers on each device? Or, would you consider creating some sort of plugin where this number could be inserted/changed by the end-user? Thank you anyway for everything that you have done!:thumbup: Chakko.

Hi overpro, This is to confirm that FSUIPC-LUA correctly recognizes all 256 encoder button/button presses as unique 'virtual joystick' button presses in FSX, and so these actions are uniquely assignable there. Thank you for your outstanding contribution!:thumbup: Chakko.

Hi overpro, Thanks for this ..... I will test the pins under FSUIPC-LUA (this will involve writing some lua plugins) and get back to you in a few days. In the meantime, I ran Pete Dowson's HID device scanner (HID Scanner.exe) and the log shows an Arduino with 256 buttons: ********* HidScanner, Version 2.00 by Pete Dowson ********* Device at "\\?\hid#vid_03eb&pid_2043&mi_00#8&392dae83&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=03EB, Product=2043 (Version 0.3) Manufacturer= Arduino Product= 001 Serial Number= C2 Usage Page: 1 Input Report Byte Length: 49 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: 8 Number of InputData Indices: 264 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 -> 256 at indices 8 -> 263 Value Dial at index 0, range 0 -> 65535, using 16 bits Value Sldr at index 1, range 0 -> 65535, using 16 bits Value R/RZ at index 2, range 0 -> 65535, using 16 bits Value V/RY at index 3, range 0 -> 65535, using 16 bits Value U/RX at index 4, range 0 -> 65535, using 16 bits Value Z at index 5, range 0 -> 65535, using 16 bits Value Y at index 6, range 0 -> 65535, using 16 bits Value X at index 7, range 0 -> 65535, using 16 bits ************************************************************************** So everything actually looks good, so far. :thumbup: Chakko.

Hi overpro, Thank you so much for this .... quite fantastic! :thumbup: I loaded the new hex file (needed to short the pins before Flip could open the USB port) ..... and yes, pointy's joystick test does not work ..... but, SV Mapper duly showed a single C.V.P Joystick with 256 buttons. ....... However, from the image, you will notice that many buttons from 225 to 255 seem to be permanently on, even with nothing connected to the Mega pins. On testing the pins with encoders and switches connected, I found normal responses from Mega pins (22, 38+39) = encoder buttons [1+2] all the way to pins (29, 53) = button [128]. But there was no response to Mega pins [30, 38] onwards. So it seems that the present firmware/code will recognise a joystick with 256 buttons but will not respond to button presses beyond # 128 (or beyond Mega pins (29,53)). Thank you for your attention, and with Warm Regards!:) Chakko.

Sir, I look forward to your 1HID*256buttons version as and when you have the time for this. Thank you again for your wonderful work!:thumbup: Warm Regards....

@RightStuff, I had the same question, so after some experimentation, was able to draw up the following scheme and 'formulae': Mega2560 R3, digital pin 22 ~ 37 connected to row 1 ~ row 16 digital pin 38~53 connected to column 1 ~ column 16 (please note I use 1 ~ 16 rather than 0 ~ 15) Scheme: rows (1 to 16) x cols (1 to 16) = 256 points cvp1 = first cvp joystick in svp mapper / pointy joystick test cvp2 = second cvp joystick in svp mapper / pointy joystick test ENCODER: row used for common connection, column used for diode connection BUTTON: row used for straight (= non-diode) connection, column used for diode connection rows (1 to 4) x cols (1+2 to 15+16) reserved for encoder_buttons [1+2 to 63+64] rows (5 to 16) x cols (1 to 16) reserved for button [65 to 256], or, button [65 to 128, 1 to 128] _____________________________________________________ row 1 col 1+2: cvp1.encoder_buttons 1+2 row 1 col 3+4: cvp1.encoder_buttons 3+4 . . row 1 col 15+16: cvp1.encoder_buttons 15+16 row 2 col 1+2: cvp1.encoder_buttons 17+18 . . row 4 col 15+16; cvp1.encoder_buttons 63+64 formula is cvp1.encoder_buttons [16*(row-1) + col] ----------------------------------------------------- row 5 col 1: cvp1.button 65 row 5 col 2: cvp1.button 66 . . row 5 col 16: cvp1.button 80 row 6 col 1: cvp1.button 81 row 6 col 2: cvp1.button 82 . . row 8 col 16: cvp1.button 128 formula is cvp1.button [16*(row-1) + col] ----------------------------------------------------- row 9 col 1: cvp2.button 1 row 9 col 2: cvp2.button 2 . . row 9 col 16: cvp2.button 16 row 10 col 1: cvp2.button 17 row 10 col 2: cvp2.button 18 . . row 16 col 16: cvp2.button 128 formula is cvp2.button [16*(row-9) + col] _____________________________________________________ Chakko Kovoor 9 Oct 2015 Yes, so all encoder pins are on cvp1.[1 to 64]

Hi Overpro, Thank you ever so much for your fantastic contribution. I have successfully tested your code with encoders and switches in FSX, and everything works as intended. Now, if one uses FSUIPC LUA one can actually access upto 256 inputs per HID controller. This would be a better solution for FSX-FSUIPC (rather than the present 128 x 2) as then there would be no possibility of the software wrongly identifying the joystick involved (as might happen now with 2 joysticks labelled cvp joystick). So my question is whether there is a simple way of modifying your code to achieve this? As I am not an expert programmer, would you or anyone else be willing to do this and offer this as an alternative? Thank you once again!

Hi dubalucu, In reply to your post # 127: Initially I thought you might have gone out of range on the Windows Game Controller window (which will show buttons for each CVP Joystick but only upto # 32). But when I connected your particular combination of pin #31 and pin # 39, I got a light on the second CVP Joystick, button # 18. This was visible in both Windows Game Controller and SVP Mapper. Of course, I am using diodes, but I think you should be okay without it if you're testing just a single pair of pins (single button). Please correct me if I am wrong. CK.