Home » Blog » PowerBlock » PowerBlock: A Power Switch for the Raspberry Pi

PowerBlock: A Power Switch for the Raspberry Pi

PowerBlock Top View

The PowerBlock is an add-on board for the Raspberry Pi (version 1, 2, and 3) models A+ and B+. It provides a microcontroller-based power-switch functionality.

This article describes the PowerBlock itself, as well as how to connect a power switch and how to install the driver.

While this is the original article about the PowerBlock you can find an updated version about the PowerBlock here.


The PowerBlock provides a power switch functionality. Why might this be of interest for you? The Raspberry Pi comes without a power switch. As soon as you plug the micro USB cable into the RPi, it turns on. If you want to shutdown the Raspberry Pi, you need to call a shutdown command to to bring the system into a state in which you can safely remove the USB cable again. If you just pull out the micro USB cable your file system might become corrupted and you might possibly loose data.

Here, the PowerBlock comes into play. It is stacked onto the GPIO header of the Raspberry Pi and provides a micro USB connector itself, a connector for a toggle switch to control the power supply of the Raspberry Pi, and a connector for an LED to indicate whether the Raspberry Pi is off, booting, running, or shutting down. The power supply is controlled by a tiny microcontroller on the PowerBlock PCB that monitors the button state as well as the state of the Raspberry Pi and switches a MOSFET accordingly. This means that there is no need anymore to plug and unplug the USB cable from the Raspberry if you want to completely and safely turn it off.

Dimensions and Interfaces


The dimensions of the PowerBlock PCB are chosen such that it exactly matches the two mounting holes on the opposite of the USB sockets of the Raspberry Pi models A+ and B+. The PowerBlock PCB comes with the same round corners as the Raspberry itself and give it a neat look. Regarding the GPIO usage the PowerBlock is attached to the first 2×6 pins of the Raspberry Pi GPIO header.

Hardware Interfaces

Here are a top and bottom view of the PowerBlock PCB:

The hardware interfaces of the PowerBlock are described in the following:

  • 2×6 pin female header as connector to the Raspberry Pi
    The PowerBlock PCB is attached to the Raspberry with a 2×6 pin female header. This header makes use of pins 1 to 12 of the J8 header. This header is used for connecting the voltage and ground pins as well as the I2C pins between the RPi and the PowerBlock. The PCB is kept as small as possible so that you can easily access all other pins that are not used by the PowerBlock.

  • Micro USB Connector for the power supply
    The PowerBlock has the same USB Micro connector as the Raspberry Pi. That means you can simply use your existing USB Micro cable for powering the RPi.

  • Pin Outs for 5V Supply Voltage and Ground
    If you do not want to use the USB connector, GND and the 5V supply voltage can also be accessed via two pins so that you could use batteries or whatever you like to power the RPi.

  • Optional DC Barrel Jack Adapter
    The PowerBlock is also prepared for connecting a DC barrel jack adapter. The hole dimensions for the barrel jack adapter are chosen such that most of DC barrel jack adapters should fit. Here is a picture that shows the PowerBlock with the optional DC barrel jack:

  • Pin Out for a Toggle Switch
    To control the power state of the Raspberry Pi the PowerBlock provides an interface for attaching a toggle switch. The on-board microcontroller monitors the state of that switch as well as the one of the Raspberry.

  • Pin Out for Status LED
    The current power state of the Raspberry Pi can be indicated with a 5V status LED that can be attached to the two pins that are provided by the PowerBlock. These states can be “off”, “booting”, “on”, and “shutdown”. The different state are indicated with easy-to-distinguish static and pulsing patterns.

  • Optional USB A Connector as power out
    If you want to provide a switched 5V voltage to another device, you can solder a USB A connector to the PowerBlock – it is prepared for that as well. Here is a picture that shows the PowerBlock with both the optional DC barrel jack as well as the USB A connector:

  • In-Service Programmer (ISP) pin-out for ATtiny
    The Power Switch logic is realized with the help of an Atmel ATtiny85 microcontroller. If you want to you have the possibility to access the microcontroller with the ISP header. In this way you could reprogram the microcontroller with whatever functionality you like.

Assembly of the PowerBlock

Assembly of the PowerBlock? Not needed – it comes fully assembled. You only need to connect a power switch and, optionally, an LED. This is described in more detail in the following.

Attaching a Power Switch

To turn the Raspberry Pi on and off with the PowerBlock you need to attach a toggle switch to the two button pins on the PowerBlock. Technically speaking, the microcontroller on the PowerBlock looks, if the two pins of the switch are connected or not. If they are connected, a GPIO pin of the microcontroller on the PowerBlock is pulled to GND and interpreted accordingly.

  • It is important that you use a toggle switch and not a momentary button with the PowerBlock. Otherwise the Raspberry Pi will be turned off again right after booting.
  • If you do not want to use the power switch functionality you can disable this in the configuration file /etc/PowerBlockconfig.cfg by setting “powerswitch”: false.
  • The power switch circuitry of the PowerBlock leads to a tiny voltage drop and we made the experience that a good quality power supply and a good quality USB cable are mandatory for a working setup. If unsure, we can recommend the official Raspberry Pi Power Supply.

Attaching a Status LED

The PowerBlock has pin outs for an optional status LED that indicates the power state of the Raspberry Pi. You can directly attach an LED to the pins that are marked with “LED”. You need to pay attention to the polarity of the LED: The LED pins are marked with “+” and “-” for that.

The LED will blink in four different patterns that depend on the power state of the Raspberry Pi:

  1. Off: The LED is simply off.
  2. Booting: The LED slowly fades in and out.
  3. On: The LED constantly stays on.
  4. Shutting down: The LED fades in and out twice as fast as during boot up.

Software Setup and Configuration

The power switch functionality of the PowerBlock is controlled with the GPIO pins 17 and 18 of the Raspberry Pi:

  • Pin 17 can be used to indicate the power state of the Raspberry Pi. This pin is read by the PowerBlock”s microcontroller to control the on-board power switch.
  • Pin 18 can be read by the Raspberry Pi to get status of the button that is attached to the PowerBlock.

The PowerBlockService is an open-source driver for the PowerBlock. It provides a service for interacting with the power button signals as well as for mapping attached game controllers to corresponding game pad devices on the Raspberry Pi. The installation only takes a few steps and is done from command line. In the following, this is described in more detail.

Command-Line Installation

The command-line installation consists of these steps:

  1. Installing required packages
  2. Fetching the latest version of the PowerBlock driver and service from the public repository.
  3. Compiling the driver binary.
  4. Installing the driver binary.
  5. Installing the service.

To be able to successfully build the driver you need to have certain APT packages installed:

sudo apt-get update
sudo apt-get upgrade -y
sudo apt-get install -y git cmake g++-4.9 doxygen

The following commmands for the command line do the above steps:

git clone git://github.com/petrockblog/PowerBlock.git
cd PowerBlock
mkdir build && cd build
cmake ..
sudo make install
sudo make installservice

You might need to reboot your Raspberry in order to have all needed services running.

The above installation procedure is also shown in this video. Please note that, other than in the video, you need to install g++-4.9 as described above:

Video Demonstration

The following video shows the PowerBlock in action:


What if you want to put your Raspberry Pi together with the PowerBlock into a case? If the RPi together with the PowerBlock fit into your case depends on the lind of power jack and the case you use. Overall, the PowertBlock adds about 6 mm in height to the Raspberry Pi 2 Model B. If you are interested, a user has published his design files for a 3D printable case that fits a PowerBlock at Thingiverse.


The PowerBlock is an extension board for the Raspberry Pi (TM). The key feature of the PowerBlock is a power switch functionality to safely turn on and off the power to the Raspberry Pi with a toggle switch. A connector for a status LED that indicates the power status of the Raspberry Pi can optionally be connected to the PowerBlock.

If you are interested in getting the PowerBlock, you can find it in our shop.

Check Also

PowerBlock RPi 4 compatible

Our Boards Compatibility with the Raspberry Pi 4

The Raspberry Pi 4 was recently released. This post is about our boards and their …


  1. Hi, having issues installing:

    pi@media:~ $ sudo apt-get update
    Hit http://archive.raspberrypi.org jessie InRelease
    Hit http://mirrordirector.raspbian.org jessie InRelease
    Get:1 https://dev2day.de jessie InRelease [301 B]
    Ign https://dev2day.de jessie InRelease
    Get:2 https://dev2day.de jessie Release.gpg [303 B]
    Ign https://dev2day.de jessie Release.gpg
    Get:3 https://dev2day.de jessie Release [299 B]
    Ign https://dev2day.de jessie Release
    Get:4 https://dev2day.de jessie/main armhf Packages [322 B]
    Hit http://archive.raspberrypi.org jessie/main armhf Packages
    Get:5 https://dev2day.de jessie/main Translation-en_GB [323 B]
    Hit http://archive.raspberrypi.org jessie/ui armhf Packages
    Get:6 https://dev2day.de jessie/main Translation-en [320 B]
    Get:7 https://dev2day.de jessie/main armhf Packages [322 B]
    Get:8 https://dev2day.de jessie/main Translation-en_GB [323 B]
    Get:9 https://dev2day.de jessie/main Translation-en [320 B]
    Get:10 https://dev2day.de jessie/main armhf Packages [322 B]
    Get:11 https://dev2day.de jessie/main Translation-en_GB [323 B]
    Get:12 https://dev2day.de jessie/main Translation-en [320 B]
    Get:13 https://dev2day.de jessie/main armhf Packages [322 B]
    Get:14 https://dev2day.de jessie/main Translation-en_GB [323 B]
    Get:15 https://dev2day.de jessie/main Translation-en [320 B]
    Get:16 https://dev2day.de jessie/main armhf Packages [322 B]
    Err https://dev2day.de jessie/main armhf Packages
    Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
    Get:17 https://dev2day.de jessie/main Translation-en_GB [323 B]
    Ign https://dev2day.de jessie/main Translation-en_GB
    Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
    Get:18 https://dev2day.de jessie/main Translation-en [320 B]
    Ign https://dev2day.de jessie/main Translation-en
    Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
    Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
    Ign http://archive.raspberrypi.org jessie/main Translation-en_GB
    Ign http://archive.raspberrypi.org jessie/main Translation-en
    Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB
    Ign http://archive.raspberrypi.org jessie/ui Translation-en
    Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_GB
    Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
    Ign http://mirrordirector.raspbian.org jessie/main Translation-en_GB
    Ign http://mirrordirector.raspbian.org jessie/main Translation-en
    Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_GB
    Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
    Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_GB
    Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
    W: Failed to fetch https://dev2day.de/pms/dists/jessie/main/binary-armhf/Packages HttpError404

    E: Some index files failed to download. They have been ignored, or old ones used instead.
    pi@media:~ $ sudo apt-get upgrade -y
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    Calculating upgrade… The following packages were automatically installed and are no longer required:
    pix-icons pix-plym-splash pixel-wallpaper plexmediaserver-installer
    Use ‘apt-get autoremove’ to remove them.
    The following packages have been kept back:
    ghostscript libfreerdp-cache1.1 libfreerdp-client1.1 libfreerdp-core1.1 libfreerdp-gdi1.1 libgs9 libgs9-common python-openssl python3-openssl
    0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
    pi@media:~ $ sudo apt-get install -y git cmake g++-4.9 doxygen
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    doxygen is already the newest version.
    g++-4.9 is already the newest version.
    git is already the newest version.
    cmake is already the newest version.
    The following packages were automatically installed and are no longer required:
    pix-icons pix-plym-splash pixel-wallpaper plexmediaserver-installer
    Use ‘apt-get autoremove’ to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
    pi@media:~ $ git clone git://github.com/petrockblog/PowerBlock.git
    Cloning into ‘PowerBlock’…
    remote: Enumerating objects: 49, done.
    remote: Counting objects: 100% (49/49), done.
    remote: Compressing objects: 100% (38/38), done.
    remote: Total 853 (delta 19), reused 29 (delta 11), pack-reused 804
    Receiving objects: 100% (853/853), 2.51 MiB | 1.36 MiB/s, done.
    Resolving deltas: 100% (287/287), done.
    Checking connectivity… done.
    pi@media:~ $ cd PowerBlock
    pi@media:~/PowerBlock $ mkdir build && cd build
    pi@media:~/PowerBlock/build $ cmake ..
    — The C compiler identification is GNU 4.9.2
    — The CXX compiler identification is GNU 4.9.2
    — Check for working C compiler: /usr/bin/cc
    — Check for working C compiler: /usr/bin/cc — works
    — Detecting C compiler ABI info
    — Detecting C compiler ABI info – done
    — Detecting C compile features
    — Detecting C compile features – done
    — Check for working CXX compiler: /usr/bin/c++
    — Check for working CXX compiler: /usr/bin/c++ — works
    — Detecting CXX compiler ABI info
    — Detecting CXX compiler ABI info – done
    — Detecting CXX compile features
    — Detecting CXX compile features – done
    — JsonCpp Version: 1.7.7
    — Found PythonInterp: /usr/bin/python2 (found suitable version “2.7.9”, minimum required is “2.6”)
    — Found Doxygen: /usr/bin/doxygen (found version “1.8.8”)
    — Configuring done
    — Generating done
    — Build files have been written to: /home/pi/PowerBlock/build
    pi@media:~/PowerBlock/build $ make
    Scanning dependencies of target jsoncpp_lib_static
    [ 5%] Building CXX object src/lib/jsoncpp/src/lib_json/CMakeFiles/jsoncpp_lib_static.dir/json_reader.cpp.o
    [ 11%] Building CXX object src/lib/jsoncpp/src/lib_json/CMakeFiles/jsoncpp_lib_static.dir/json_value.cpp.o
    /home/pi/PowerBlock/src/lib/jsoncpp/src/lib_json/json_value.cpp: In constructor ‘Json::Value::Value(Json::ValueType)’:
    /home/pi/PowerBlock/src/lib/jsoncpp/src/lib_json/json_value.cpp:346:27: warning: declaration of ‘empty’ shadows a member of ‘this’ [-Wshadow]
    static char const empty[] = “”;
    [ 17%] Building CXX object src/lib/jsoncpp/src/lib_json/CMakeFiles/jsoncpp_lib_static.dir/json_writer.cpp.o
    [ 23%] Linking CXX static library libjsoncpp.a
    [ 23%] Built target jsoncpp_lib_static
    Scanning dependencies of target powerblock-app
    [ 29%] Building CXX object src/powerblock/CMakeFiles/powerblock-app.dir/PowerBlock.cpp.o
    /home/pi/PowerBlock/src/powerblock/PowerBlock.cpp:24:22: fatal error: plog/Log.h: No such file or directory
    compilation terminated.
    src/powerblock/CMakeFiles/powerblock-app.dir/build.make:62: recipe for target ‘src/powerblock/CMakeFiles/powerblock-app.dir/PowerBlock.cpp.o’ failed
    make[2]: *** [src/powerblock/CMakeFiles/powerblock-app.dir/PowerBlock.cpp.o] Error 1
    CMakeFiles/Makefile2:514: recipe for target ‘src/powerblock/CMakeFiles/powerblock-app.dir/all’ failed
    make[1]: *** [src/powerblock/CMakeFiles/powerblock-app.dir/all] Error 2
    Makefile:127: recipe for target ‘all’ failed
    make: *** [all] Error 2

    Any help would be appreciated.

  2. I did finally manage to get this to build on my wheezy based pi, but it was a super pain to do because wheezy only goes to g++-4.8 I spent a long time fighting with it.

    I used the laryx answer from this: https://stackoverflow.com/questions/25147363/how-to-install-g-4-9-on-debian-wheezy-armel

    to get the parts from a jessie build and then manually did the cmake setup with -DCMAKE_C_COMPILER= and -DCMAKE_CXX_COMPILER= definitions on the cmake command line pointing to the new 4.9 stuff. Just exporting CC and CXX in the env didn’t work for me.

    Hopefully this will help other’s trying to get PowerBlock working on a wheezy pi.

  3. You mention customization of the program running on the ATMEL chip by connecting through the ISP header. Is the default program contained on the ATTINY chip located on your github? I can’t seem to find it.

  4. Matthew Olsen

    I’ve just received the power block and am building a custom case for my setup. Since the power block takes up the necessary GPIO pins for running a small fan, is there an alternative way to power a small cooling fan?

    • The PowerBlock has 5V output pins (+, -). These pins are also switched by the PowerBlock. As long as the fan does not draw too much current, those pins could be used. The maximum current the PowerBlock can handle is 3.7 A – including the current consumption of the Raspberry! If you need more power you could use the output pins to switch, e.g., a relay. Hope that helps!

  5. Hi! So is the git software used to execute the shutdown command? Is it possible to execute a python script once shutdown is initiated? I’d like to turn power on off for an arduino when the pi shuts off?

  6. Erkan Moustafa

    Hi All,

    i installed the PowerBlock and everything seemed to go well.
    i switched on the Pi and the LED flashed while booting into Retropie.
    Retropie loaded up but the LED continued to flash I pressed the switch to powerdonw but nothing happened the LED just continued to flash.
    Any ideas on how I can resolve this?


  7. Hello everybody, a friend and I are working on a Raspberry pi3 model B in a Megadrive 2 case. We bought a Powerblock to be able to use the original powerswitch button and the original LED. When trying to install all the PowerBlock stuff, we ran into errors such as :
    pi@retropie:~ $ git clone git://github.com/petrockblog/PowerBlock.git
    fatal: destination path ‘PowerBlock’ already exists and is not an empty directory.
    pi@retropie:~ $ cd PowerBlock
    pi@retropie:~/PowerBlock $ mkdir build && cd build
    mkdir: cannot create directory ‘build’: File exists
    pi@retropie:~/PowerBlock $ cmake ..
    CMake Error: The source directory “/home/pi” does not appear to contain CMakeLists.txt.
    Specify –help for usage, or press the help button on the CMake GUI.
    pi@retropie:~/PowerBlock $ make
    make: *** No targets specified and no makefile found. Stop.
    pi@retropie:~/PowerBlock $ make ..
    make: Nothing to be done for ‘..’.
    We still get the cmakelists error after installing the drivers again. Any idea on how to solve this ?
    Oh, and the LED keeps on blinking when the Raspberry is on.

  8. I just received my PowerBlock, wired it up, installed the driver and it’s working except that it never actually cuts power to the Raspberry Pi and stays blinking after shutdown. What am I doing wrong?

  9. how to make this work on openelec/libreelec?

  10. I keep getting a error: -bash: syntax error near unexpected token `;&’

    I’ve tried following the video as well, but just using “make” after cd PowerBlock doesn’t seem to be working either.


  11. during the driver install, I get this:

    pi@raspberrypi:~/PowerBlock/build $ cmake ..
    bash: cmake: command not found

    Am I typing this wrong?

  12. Joseph Ferris

    Would I still need to wire a resistor up for an LED, or does R3 on the board handle that for me already?

    Thank you, in advance!

  13. iain hancock

    Hi, hope ok to post a query here. I have a raspberry pi 3, latest official retropie, plus a powerblock. I have a switch wired in I beleive is latching (Maplin: http://www.maplin.co.uk/p/illuminated-red-push-to-make-switch-n07ar ) and the power connected to the powerblock.

    i’ve found a couple references to a similar issue where if I use the switch to power off, the machine shutsdown neatly then instantly powers back up again even tho the switch is now “open”.

    the machine will not cold boot when the switch is open!

    I did have trouble installing the driver. the instructions here, fail:

    the ones here are materially different and seem to work:

    But I now have this reboot issue.

    have I just wired the switch up to the wrong pins, or have the wrong type of switch! I’m not using the LED side of the switch, just the 2 pins to the 2 pins on the switch.

    thank you for your help, it seems an ideal solution but user error? 🙂


    • You can check, if the PowerBlock works properly by connecting the switch pins directly with each other (without any button in between). If they are connected the PowerBlock should turn on the RPi. As soon as the are disconnected a shutdown signal should be triggered.

      • iain hancock

        hi, ok I tried that and it works perfectly. then I switched my weak little brain on and … I described this completely insanely wrongly.

        The actual situation is this:

        Now I have the powerswitch driver installed, the switch works as expected.

        BUT if i now shut down the pi from the emulationstation quit menu option, the pi shuts down and starts up again on its own. it didnt do this before i installed the driver.

        thats the issue. sorry for confusing matters with a bogus report.

      • That is because the PowerBlock/ControlBlock only looks at the status of the attached switch. You should use the switch only to switch of the RPi.

      • iain hancock


        coming back to this if you dont mind. so with the powerblock driver installed, i can – these are as my current experience –

        1. I can only switch the pi off by using the power switch attached to the pi3, Yes?

        2. from command line on the pi, ‘sudo shutdown now’ – the pi will shut down and stay off. Yes?

        3. but choosing the ‘shutdown’ option from emulation station/under retropie will not work. the device will reboot because the power switch is closed. yes?

        is there a workaround for case 3?

        thank you! iain 🙂

      • hi, did you get answers to this?

      • iain hancock

        no reply.

        I’m still hoping the powerswitch and driver does not stop me turning off the system from ES. It seems odd to kill that functionality. Thats why I think i have something set up badly, that cant be right. why would it break or change that?

        i can still ssh into the pi, sudo shutdown now, that works, but the powrswitch seems to have stopped the ES menu option from working.

      • Sorry for this late reply.

        There is no workaround for case 3 – the hardware switch overrules the software in this case.

  14. Hello,
    Can you tell me which pins are really used by the powerblock ? I would like to know if some of them are free to use them with an other software.
    I also see a “5V + – IN” inscription on the board, may I use this for the power supply instead of the micro usb port ?
    Thank you !

  15. Jason Pereira

    Hi there,
    I wanted to add an extra switch to the powerblock so that I could invoke an umount script to un mount the usb drive where my roms are stored. Can I use pins 11/12? it seems from the pi3 GPIO header pins 11/12 are GPIO17 & GPIO18, so by reading those pins I should be able to detect a button press(connect to ground). Are my assumptions correct?


  16. Hey there.

    I got a PowerBlock for my project where I’m installing the Raspberry Pi in an old Sega Genesis Model 2 shell. I plugged the power supply (made for use with Raspberry Pi 3) into the micro USB port on the PowerBlock itself, and I am using the original toggle power button from the Sega Genesis motherboard. I’m pretty sure the power button and the LED is properly connected, but when I press the power button, absolutely nothing happens. So do I need to configure the software first before this device will physically work, or should I already have been able to turn it on even without the software installed?


    • Nevermind, I figured it out! Turns out I had the switch connected wrong (the power switch in the Sega Genesis model 2 has 5 pinouts, I apparently was using the wrong combination). Works really awesome! Thanks! 😀

      • I have a PI, also have an Ouya with a 1 terabyte all games, not bad, Run Kodi on both too.
        Which Reminds me of when I was a test patient for Viagra but Left because everyone was pretty Hard-On me.
        Seems I can’t keep a job, I worked at a sperm bank but was let go due to Carpal Tunnel 🙁

      • Lol! xDD But yeah, you should see this console I’m putting together. It’s still a work in progress, but it’s pretty sweet! ^^

      • Keep me posted I like making my own retro consoles, got thousands on mine.

      • Will do! ^^ Here’s a video of what I have so far in action: https://www.youtube.com/watch?v=9wTxhPr2Z88

      • Thats super cool man!

      • Thanks! 😀

      • Έλληνας

        1 terabyte of games on Ouya? XD Is that like 100 Angry Birds clones + a few Farmville clones or what? Is this the entire Android Play Market on an SD card or something? And is any of that actually enjoyable to play?

  17. Software I’d like to run requires GPIO 4. Can I pass through pin 4 and GND on the PowerBlock?

  18. here’s a bit of a dumb question, but since I’m new to all of this, I don’t really know the answer myself. I bought this board for my Raspberry, and I’ve bought these female pins (https://www.aliexpress.com/item/10PCS-2-54mm-40-Pin-Stright-Female-Single-Row-Pin-Header-Strip-PCB-Connector/32597304567.html?spm=2114.13010608.0.0.TmYjXn) but I don’t know which wires I should be using to connect the pins to these rocker switches (http://www.dx.com/p/on-off-pressing-button-power-control-switches-black-white-5-pcs-270035#.WICHx31SHDM)

    because there are so many different kinds of wires I have no idea which ones I should be using.

  19. Steven Mercurio

    Are the drivers compatable with Fedora 25? I have one SD card loaded with every NOOBs OS to try them out and learn them and another I am loading with Fedora 25.

  20. Devon Dunnington

    I was able to power it on with a push on push off button. I didn’t have to change any of your script or programs at all.

  21. Hi, I am interested in getting the powerblock as I will be installing it into a cabinet with the pi. I’m not too familiar with with electrical components but I’m trying to find out how the LED wires and the toggle switch wires are connected to the pins? It looks like most pictures online show some sort of black connectors which I can find on multiple sites but what size are those pins so that i can find the right size connector? I’m not referring to the GPIO pins but instead to the pins that the LED and toggle switch connect to. I’m trying to gather and purchase all the pieces at once so I don’t have it in front of me to measure. Thanks for making the power situation easier!

  22. Hi I have the powerblock installed and working but what I am trying to do without success is get the Rasoberry Pi to autimatically run a script so that I do not need to have a mouse or keyboard attached.

    Please can anyone help ?

  23. Like to the store is broken

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

We use Cookies and similar technology to collect and analyse information about the users of this website. We use this information to enhance the content, advertising and other services available on the site. Please click ‘Accept cookies’ to consent to the use of this technology by petrockblock. You can manage your preferences at any time by visiting our Cookies Policy page.