So I went the cheap route and got a Xin Mo keyboard encoder for another build project. I now have this issue where the buttons are working, but they are finicky. Pressing a direction once will do multiple presses, and holding a direction will have the effect of pressing and letting go (the character moves in the direction, then stops, then moves again, etc.) I have seen that there were some kernel build fixes, but I thought that was compiled with the latest beta so I am not sure if rebuilding the kernel will fix this. I really wanted to ask if I get a iPac or Minipac, will that just fix the problem? I am assuming this issue is with the Xin Mo encoder, and not how piplay handles a keyboard encoder, correct? I appreciate any help you guys can give me on this.
@Rydon - it can be a couple of issues. The first that comes to mind is what type of switches do your joystick and buttons use? momentary, leaf, snap? You may be having debounce issues, which is when the contacts either bounce off of each other (creating a double connection) or the contacts come close enough to make a connection but then move apart before making their real connection.
While I don't have any experience with leaf type, I've been told that you can manually adjust them to compensate for debounce.
Thanks for the info guys. I will try the kernel nel and see how that does. If that does not resolve it, I will check the switches, as they are old (from previous cabinets/left over CPs). I'll report back with my findings.
ian57: I am getting an error message when trying to extract the tar file.
gzip: stdin: not in gzip format tar: Child returned status 1 tar: Exiting with failure status due to previous errors
I have tried renaming the file, using tar -xzf, sudo at the beginning, etc. I still get the error. Could there be an issue with your kernel on your end? My linux is pretty limited so I apologize if I missed an easy fix.
Hi all, kinda resurrecting this. I have two boards each connected via USB to the Pi for 2 controllers. It appears as though the Pi is processing it as a single controller. any suggestions to split them out?
This is a stop-gap fix as long term I'm going to try and use I2C to connect the controllers and use the rest of the I/O to control LEDs.