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!

Hi @shukuyen ,

Sorry, I didn't make a tutorial but it was all pretty straightforward in the end.
I gutted an old Nes and dumped everything in :)

Parts used:

Rpi3 + microsd Raphnet dual nes to usb Petrockblock's controlblock and nylon posts Wiring

The hardware part was the easiest part tbh.
If you get it all wiredup i can make an image of my sd. That way you shouldnt have to configure anything :)

From: https://blog.petrockblock.com/powerblock-raspberry-pi-power-switch/

bd36f6ce-eb6a-4a71-bfa3-60e918fde773-image.png

Do you maybe have the micro-USB connector attached to the Raspberry Pi or the PowerBlock? It needs to be attached to the PowerBlock. Could you send me a photo of your hardware setup?

Can you tell me which version of RetroPie and which version of the Raspberry Pi you are using? I could try to reproduce the issue at my site.

Sorry or this late reply. Could you please contact me via email and send me your order number? I will make sure that you get a replacement!

Thanks for getting back to me, and thanks for making fantastic little bits of hardware, I hope it works out with the 3A+

I ordered the B model in the end, I figured that I might regret not having those extra USB ports down the line, and the larger footprint means I'll be forced into making a tidier build :)

@mitu said in Modify Power Button Behaviour to 'Hold for three seconds'??:

You can increase the bouncetime from 2sec to something larger.

Even as it is now, just a single quick push will shut the software down - i dont have to hold the button at all.

Perhaps I need to use a different script that relies on the button being held.

@cybermonkey01 most of the free to download games that can run on the pi are already in our ‘ports’ package manager.

Did you update the firmware to the latest version?

Glad to hear that!

Hi, did you get my email reply?

Thanks for the hint! I have updated the README. The install script (install.sh) already had that package. I was not aware of these differences.

Glad that it is working for your now!

What's the switch' part number? Where did you get it from? Maybe a little research can show how the switch LED is connected internally.
When you mentioned LED, is that the LED connected to the Contolblock or the LED on the switch?

If you power the RPi using the microUSB of the RPi itself you will loose the power switch and reset functions on the Powerblock. When the Powerblock is used as designed using its microUSB connector, power to the RPi is controlled by the Powerblock and routed to the Power and Ground pins of the GPIO connector. When the RPi is booted up the driver and control service of the Powerblock will initialy interrogate the status of the Powerblock board and intitiate the boot up process. If the microUSB on the RPi is used to as power source, all of this is bypassed and the RPi will power up as if the Powerblock does not exist.

The only way to use microUSB on th RPi together with the Powerblock is to isolate the RPi's micrUSB connections from the RPi itself (cut the traces from the RPi) and rewire them to the Powerblock's microUSB connector. Doing so is a mute, waste of time, potentially damaging to the RPi exercise.

All right.

I took a look into the sources of the ControlBlock driver. The same issue that caused the slow shutdown for the PowerBlock also existed there. I have fixed that now.

I got everything working flawlessly with a different power supply: 5.2V, 3A. :)