Glad to hear that!

I have updated the instant scripts such that the libc6 and libc6-dev packages are also automatically installed.

Glad to hear that!

@BuZz Thanks a lot Jools! :-)

Worked for me too! Thanks!

For future note: I removed the dependency to WiringPi now. Please see also https://retropie.org.uk/forum/topic/23328/powerblock-driver-quick-installation-fails/5.

It is fixed now. Please see https://retropie.org.uk/forum/topic/23328/powerblock-driver-quick-installation-fails/5.

@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).

Good to hear all is working well!

I still need to buy a Pi 4 so it will take some time for testing it out..

Thanks for the support!

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 have the same problem, not know how to solve, also my start button becomes X (for example) any tip? Thanks

Sounds as if something is going very wrong. Can you post a picture of your hardware setup here?

Hello, we found that the Linux/Raspbian service ModemManager interferes with the GamepadBlock. We released a possible fix for that:

https://blog.petrockblock.com/gamepadblock/#linux

Hope that helps!

Glad to hear that you made it work!

Hello Florian,

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!

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.

Glad to hear that!