@paulkosm I think this is just the nature of the powerblock. The problem would be that the latching switch would still be latched in the on position (which is why you get a restart) and there's no way to automatically unlatch it. It might be more annoying to have to unlatch then latch again to turn the system on after a soft shutdown.

Personally I just use the powerblock switch to shutdown every time and never use the menu shutdown option now.

One idea to try out could be to try and disconnect the fan. If the behaviour is different and, in the best case, everything is working properly, then the fan might draw too much current.

Ok. Thanks for the answer !
Wasn't sure if you needed that driver for any on/off switch hooked up to the pins.

The same official micro-USB adapter that works in the jack, just out through an extender so that it can be powered in a custom case. The placement of the jack isn't ideal, I'm just moving it out.

Hello, I am very sorry if that email got lost somehow. Please contact me again at contact (at) petrockblock (dot) com!

@petrockblog I think you can best answer on this ;)

I saw your switch built in a NESPi case - it should fit perfectly in.
But what will happen in the following scenarios:

I use a momentary switch and press the button to powerdown (I think it's clear what will happen) I use a momentary switch, do a shutdown via software (Quit >> Shutdown system)

The Mausberry switch fails in this case, because it will miss the physical button press and therefore needs a GPIO signal sended to the Mausberry circuit (Take a look here).

If you don't do this modification the Raspberry will shutdown as usual but the Mausberry switch is still active and does not respond to any button switch. So you have to cut main power or reset the circuit to make it work again.

There was a problem with missing includes that slipped through with the recent minor update.

I have just pushed the fix. Everything should work now, sorry!

Revision 1.1 of the PowerBlock (introduced last year) provides break out pins for all needed signals. There is a brief blog post about it at https://blog.petrockblock.com/2016/05/20/new-revision-of-the-powerblock-increased-flexibility/. Maybe that gives some more insights.

After the installation of the PowerBlock and the ControlBlock drivers you need to enable the driver in a second step. I realise that this is not intuitive so that I created a patch for the RetroPie Setup. In the future, the drivers will be enabled with the installation.

@lostless thanks!

Took a slightly different approach and called the multi-switch shutdown script from etc/powerblockswitchoff.sh So that I’d keep the main driver intact.

Thanks again! This was something so simple that I overlooked. Totally missed that the script could issue the necessary ES shutdown without tying it to a physical switch.

I never got any response from @petrockblog on this....so I'm asking again, are there diagrams that we can look at? Also, how about a Parts List? Some of us are having deficient power when the ControlBlock is used. I know that a transistor (Q1) switch supplies power to the PI using the GPIO pins. The question is, what is the max current that Q1 supplies the RPi with? Is it 2.5A or much less? Is this a constant current or fluctuating current? Without a diagram and parts list we are constantly guessing where our issues come from.

@golaat Glad to be of help. Let us know how your project is going.

Glad that things are working for you now :-)

@Radioman673 So that we can all learn from your experience, what is exactly wrong with the install at "petrockblog"? I followed it to the letter and I had no issue with it...

There was indeed a problem with the HTML handling. I have corrected it.