@petrockblog Well, right now it is only my assumption that the power supply in combination with the powerstrip and other power supplies causes the problem. If you are interested in further investigations, I can send back the problematic PowerBlocks, or I could do a few simple measurements.
Being a beta tester would be fine, I am used to work with hardware/software in development status. However, it depends on the timeframe as I have have an eye on an alternative solution. But if we talk about one, two, three months, I would be glad in acting as beta tester.
@petrockblog It appears that I can get the service running by commenting out the line "[ -x "$DAEMON" ] || exit 0" and then starting the service. This also allows the service to run on boot.
So, why does this line need to be commented out? I'm confused why this would work for everyone else and not my setup (even though I started from a completely fresh RetroPi 4.5).
@superpie3k Thanks for your responses. I was away on vacation and only just got back to this. I had the same experience as above. "Had to install wiringpi manually, and to execute steps from https://github.com/petrockblog/PowerBlock manually. Seems to be a version mismatch with library wiringpi." But I got it working now.
So, I have mounted the PowerBlock and I have tested it for some days. It works almost as expected, spordically it shows unexpected behaviour. I will create a separate thread explaining my observations.
Anyway, thanks for supplying me with a replacement device.
I just wanted to share that I have managed to swap the cooked component for a new one, and it’s fixed the powerblock back to working order.
Thanks for your help. Managed to desolder the old one with some flux, desolder wick and some patience. Getting the new one in was easier than expected.
Glad to hear that you are making progress!
It should always be possible to use the ControlBlock together with any USB controller. You would just need to run the input configuration for each device on EmulationStation. All controller types should be recognised and working afterwards.
Regarding your question about the need for an additional keyboard: What you would need to do is to configure the emulators such that you have full control with your arcade / gamepad controls only. That should be possible.
Hope that helps!
I know this is over a year old, but I am curious how you came to diagnose your issue as a board defect. Was it a defect in the Pi board or the SNES board?
I'm having the same issue straight out of the box, never have gotten it to work. The controller was tested working before disassembly. I created a new thread on this but not much insight yet...
So far I did not explicitly test the GamepadBlock with a Neogeo controller. Can you post a link to the controller that you have?
Looking at the pin out at http://old.pinouts.ru/Game/NeoGeoJoystick_pinout.shtml the integration of Neogeo support should be quite easy.
That looks like it would do the trick, but it also looks like a daunting endeavor. I'd have to modify the design to work in my case with a full size NES case. All those mini jump wires between contacts is going to suck for me too. Plus I have no idea what those other parts (diode, resistor, capacitor, etc) are used for. I wish I knew more about electronic circuits. That's why I liked the Mausberry circuit so much, plug in, put the wires where they need to go, and you're done (after getting the script obviously). The PowerBlock was useful too because you just attach it to the GPIO pins. I still think doing something like the Mausberry would work best, but I'm not sure if they can support the amps. Waiting for them to reply.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.