Home » Blog » ControlBlock » ControlBlock: Power Switch, Game Controllers, and I/O for the Raspberry Pi

ControlBlock: Power Switch, Game Controllers, and I/O for the Raspberry Pi



First: What is a simple solution for turning the Raspberry Pi on and off with a power switch in a smarter way than cutting the power supply and risk data loss?

Second: What is a simple way for connecting arbitrary arcade controllers to the RPi? In the following we present the ControlBlock, a Raspberry Pi (TM) Add-On that solves both problems.


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

Arcade ControllersThere exist individual solutions for both use cases: You can get power switch solutions for the Raspberry Pi as well as input accessories that can be connected to the RPi via USB. However, I wanted to have a more compact and neatly integrated solution – something that provides a whole bunch of general purpose input and output pins together with a reliable and intuitive power switch solution.




p>The ControlBlock 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 as well as two General Purpose Input/Output (GPIO) Expanders with overall 32 pins so that you are able to connect quite anything you like to it.

Besides the hardware itself, a driver software is presented here, that allows for an easy installation and configuration of the ControlBlock functionalities, especially the connection of game controllers. Currently, the driver supports these game pad types:

  • Arcade Controllers
    Connect any controllers that are based on microswitches and the driver will map these either to two distinct game pads or to keyboard presses with MAME layout, which can be seen as the de facto standard in this field.
  • SNES Controllers
    The driver also supports the polling scheme of Super Nintendo Entertainment (SNES) controllers. Currently, the driver supports up to two SNES controllers that can be attached to the ControlBlock.
  • NES Controllers
    Since Nintendo Entertainment System (NES) controllers and SNES controllers are so similar in their hardware, the driver also supports up to two NES controllers.

The sources of the driver are publicly available at Github and can be further enhanced to support additional controllers in the future.

In the following, details are given for the individual features that are mentioned above. Functionalities, dimensions, and hardware interfaces are described first. Then, the assembly is described in more details. After that, the configuration and a demonstration video is presented. A conclusion is given at the end of this article.

Functionalities>The ControlBlock provides two main functionalities that can be used independently from each other:

  1. Power Switch
    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 RPi, 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.
    The ControlBlock provides a connector for a toggle switch to control the power supply of the RPi. Furthermore, it provides a connector for an LED to indicate whether the RPi is off, booting, running, or shutting down. The power supply is controlled by a tiny microcontroller that monitors the button state as well as the state of the RPi and switches a MOSFET accordingly. This means that there is no need anymore to plug and unplug the USB cable from the RPi if you want to completely turn your RPi off.

  2. General Purpose Input/Output and Game Controllers
    The 2×40 pins header of the Raspberry Pi already comes with a bunch of GPIO pins that can be used for all kinds of things to control and sense. However, these pins go directly into the main controller of the RPi and there is no further circuitry protection. Also, if you want to attach a set of arcade controllers, this task can become quite troublesome. The ControlBlock comes with two GPIO expanders MCP23017: Overall, you have 32 additional GPIO pins that can be controlled via the I2C interface of the RPi. The GPIOs can be accessed with terminal blocks that also provide cable protection. And if you accidentally create a short circuit you do not have to fear to fry your whole Raspberry with that then.

Also, if you want to connect your RPi to any kind of game controllers, you have to decide which GPIO pins to use and you must adapt your driver software such that exactly these pins are controlled. The ControlBlock makes the task of connecting game controllers to the Raspberry Pi very easy: The ControlBlock PCB is clearly marked with pin outs for players 1 and 2 and the provides driver software for the ControlBlock can easily be configured for different controller types.


Dimensions and Interfaces


The dimensions of the ControlBlock PCB are chosen such that it exactly matches the mounting holes of the Raspberry Pi models A+ and B+. The ControlBlock PCB comes with the same round corners as the Raspberry itself. Of course, these round corners provide no further functionalities, but give the whole setup a neat look. Regarding the GPIO usage the ControlBlock is attached to the first 2×6 pins of the Raspberry Pi GPIO header.

The ControlBlock does not fit the Raspberry Pi models A and B. The reasons for this are the composite out connector and the missing mounting holes of the Raspberry Pi models A and B.


Hardware Interfaces

ere is a top-view of the ControlBlock PCB:
Top-view of the ControlBlock

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

  • 2×6 pin female header as connector to the Raspberry Pi
    The ControlBlock 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 ControlBlock. The PCB is prepared for breaking out all other pins of that header so that you can easily access all other pins that are not used by the ControlBlock.

  • Micro or B-Type: USB Connectors for the power supply
    The first version of the ControlBlock had a USB mini connector. Because so many people asked for it the ControlBlock got a USB Micro connector now. That means you can simply use your existing USB Micro cable. The USB Micro connector comes by default with the ControlBlock. If you would like to use a bigger USB connector, you can optionally solder a USB-B socket to the ControlBlock! This should give you the flexibility that you need for your project.

  • Pin Outs for 5V Supply Voltage and Ground
    If you do not want to use 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.

  • Pin Out for a Toggle Switch
    To control the power state of the Raspberry Pi the ControlBlock 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 can be indicated with a 5V status LED that can be attached to the two pins that are provided by the ControlBlock. These states can be “off”, “booting”, “on”, and “shutdown”. The different state are indicated with easy-to-distinguish static and pulsing patterns.

  • 2×16 GPIO pins
    Overall, the two GPIO expanders provide 32 GPIO pins for arbitrary usage. With revision 2.X of the Raspberry Pi, these pins can be accessed via the SPI interface of the Raspberry Pi. With revision 1.X of the ConterolBlock, these pins can be accessed via the I2C interface with the I2C addresses 0x20 and 0x27.
    Alternatively, to manually access the pins you can use the provided ControlBlock driver software to easily connect and poll various game controllers. For this, the top silkscreen of the ControlBlock PCB is marked with pin outs for players 1 and 2.

  • 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.

  • GPIO pins used by the ControlBlock
    The ControlBlock revision 2.X uses these GPIO pins of the 40-pin header of the Raspberry Pi: 3.3V (pin 1), 5V (pin 2), GPIO 17 (pin 11), GPIO 18 (pin 12), MOSI (pin 19), MISO (pin 21), SCLK (pin 23), CE0 (pin 24).


Assembly of the ControlBlock

e ControlBlock consists of SMD as well as of THT components. The THT components consist of these parts:

  • 1x 2-pin female terminal block
  • 2x 2-pin male header
  • 1x 2×6-pin female connector
  • 4x 8-pin female terminal block

These parts are shown in the following image:

The assembly of the THT components is done in a few steps, which are described in detail in the following:

  1. Solder the 2-pin female terminal block on the top side (i.e., the side with the white marking print) of the ControlBlock. Take care for the correct orientation of the terminal block!

2. Solder the two 2-pin male headers for the button and the status LED. Note that you might to adapt this step according to the button and/or the LED that you want to use with the ControlBlock.

3. Solder the 2×6 female pin header on the bottom side of the ControlBlock (i.e., the side without the white marking print)

4. Solder the first 8-pin terminal block on the top side of the ControlBlock. Take care for the correct orientation of the terminal block! First, solder a single pin and check the resulting alignment of the terminal block. If the terminal block is placed well, continue with the other seven pins.

5. Solder the other three 8-pin terminal blocks in the same way as you did with the first 8-pin terminal block.

The fully assembled ControlBlock should look like this:



Attaching a Power Button

the Raspberry Pi on and off with the ControlBlock you need to attach a toggle switch to the two button pins on the ControlBlock. Technically speaking, the microcontroller on the ControlBlock looks, if the two button pins are connected or not. If they are connected, a GPIO pin of the microcontroller on the ControlBlock is pulled to GND and interpreted accordingly.
  • It is important that you use a toggle switch and not a momentary button with the ControlBlock. 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/controlblockconfig.cfg by setting “powerswitch”: false.
  • The power switch circuitry of the ControlBlock 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

olBlock 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.

How to at

How to attach Arcade Buttons, Joysticks, Gamepads

s from the arcade buttons, joysticks, as well as from the (S)NES gamepads are connected to the ControlBlock via the screw terminal blocks. You need a slotted screwdriver with a maximum width of 2.5 mm for that. Detailed instructions for the individual controller types are given further below.


Software Setup and Configuration

ports of the ControlBlock can be accessed via the I2C interface of the Raspberry Pi. The addresses of the two GPIO expanders are 0x20 and 0x27.

The power switch functionality of the ControlBlock 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 ControlBlock”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 ControlBlock.

The ControlBlockService is an open-source driver for the ControlBlock. 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 can either be done completely from command line or half-automatically with the help of the RetroPie-Setup Script. In the following, these two methods are described in more detail.


Command-Line Installation

efore you start with the installation of the ControlBlock driver, make sure that the SPI-interface (in case of ControlBlock rev. 2.X) or the I2C-interface (in case of ControlBlock rev. 1.X) is enabled. You can do this via the tool raspi-config in the “Advanced Options” menu. Enable the interface and let the kernel module be loaded by default. Reboot your system to let the changes take effect.

The command-line installation consists of these steps:

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

Here is a step-by-step guide:

  1. Eventually: Download and copy the RetroPie SD card image version 3.5 to the sd card
  2. Do not connect any other (USB) controller to the Raspberry for now to avoid any unnecessary interference
  3. Connect the power supply and the switch with the ControlBlock and switch on the Raspberry
  4. When EmulationStation has loaded and shows the controller configuration, press F4 to get to the command prompt.
  5. Alternatively: Connect to the Raspberry Pi via SSH to get to the command prompt
  6. Run „sudo raspi-config“, select „Advanced Options“, select „SPI“ and enable the SPI interface and the SPI kernel module on boot by default by selecting „Yes“ in the following two screens.
  7. Exit raspi-config by selecting finish and select „reboot“ when asked for it.
  8. Again, press F4 in EmulationStation to get to the command prompt or connect to your RPi via ssh
  9. Update the apt package cache: sudo apt-get update
  10. Install any APT updates: sudo apt-get upgrade -y
  11. Reboot (IMPORTANT, otherwise we might get a modprobe error) via “sudo reboot”
  12. Install necessary packages: sudo apt-get install -y cmake g++-4.9 doxygen
  13. Clone the ControlBlock driver repository: git clone --recursive https://github.com/petrockblog/ControlBlockService2.git If you have revision 1.X of the ControlBlock use the command git clone https://github.com/petrockblog/ControlBlockService.git
  14. Change into the driver folder: “cd ControlBlockService2” (or “cd ControlBlockService” for rev. 1.X)
  15. Build Makefile: mkdir build && cd build && cmake ..
  16. Compile the driver: make
  17. Install the driver: sudo make install
  18. Install the service so that the driver is loaded on boot: sudo make installservice


  • You can now configure the ControlBlock service by editing its configuration file via „sudo nano /etc/controlblockconfig.cfg“.
  • After changing the configuration, you can reload the service via „sudo service controlblockservice restart”
  • You can test your attached controller(s) with the tool jstest, e.g., with „jstest /dev/input/js0“ (Exit with Ctrl-C)

This video demonstrates the above steps:

Using Arcade Controllers with the Contr

Using Arcade Controllers with the ControlBlock

indicators that describe a default pin out for arcade controllers: You can connect two joysticks and 12 buttons for each of the two players:


The ControlBlock service can be configured in two different ways when using arcade controls:

As one option it can be configured such that it provides two game pad devices in the system, one for each player. To do so, the configuration in the file /etc/controlblockconfig.cfg must set “gamepadtype” to “arcade”:

    "gamepadtype" : "arcade"

As another option the ControlBlock service can be configured such that it provides a virtual keyboard with the de-facto MAME standard. To do so, the configuration in the file /etc/controlblockconfig.cfg must set “gamepadtype” to “mame”:

    "gamepadtype" : "mame"

The button mapping is shown in the following diagram:


Using (S)NES Controllers with the ControlBlockUsing (S)NES Controllers with the ControlBlock

d SNES controllers. Here is a diagram that describes the pin out for using NES and SNES controllers with the ControlBlock:


Here is a pin out diagram for NES and SNES connectors:

If you want to use a SNES case, here is a diagram that shows the pin out of the original SNES controller front:

SNES Controller Front Pin Out
SNES Controller Front Pin Out

In order to poll NES and SNES controllers the configuration in the file /etc/controlblockconfig.cfg must set “gamepadtype” to “snes”:

    "gamepadtype" : "snes"

You can also connect a latching reset button to Player-2, Input B. If the button is pressed a virtual ESC-key press will be triggered.

Only one Gamepad

If you want to connect only

Only one Gamepad

lBlock you can set the element onlyOneGamepad to true: It enables only one gamepad in the system (e.g., if only Player-1 buttons are wired to the ControlBlock in your setup, this prevents a ghost gamepad from being selected as default player 2 in retroarch)

4-Player Extension

The driver can handle up t

4-Player Extension

eans that you can stack two ControlBlock on top of each other to have inputs for four players. To do so make sure that you set different addresses for each of the ControlBlocks. You can set the address of each ControlBlock by setting the two solder jumpers of each ControlBlock accordingly. The values of the solder jumpers have to be set in the configuration file with the elements SJ1 and SJ2. Also, you have to enable the second ControlBlock by setting the element enabled for the second ControlBlock to true.

Power Switch Functionality

To enable or disab

Power Switch Functionality

ou can set the element powerswitchOn to true or false:

  • true: Activates the handling of the power switch signals of the ControlBlock.
  • false: Deactivates the handling of the power switch signals of the ControlBlock.

Video Demonstrations

Power Switch


Power Switch

tionsower switch functionality of the ControlBlock:

Arcade Controllers

The the following demonstra

Arcade Controllers

trollers for two players that are mounted on a simple wooden console. The bottom of it looks as following:

Bottom view of the wooden demo arcade controllers console.

This video shows the controllers in action:

SNES Controllers

This video shows the ControlB

SNES Controllers

s attached to it:


The ControlBlock is an extension bo


ry Pi (TM). The two key features of the ControlBlock are

  • a power switch functionality and
  • general purpose input/output (GPIO) pins ready to use, e.g., for connecting arcade or SNES controllers.

The power switch functionality allows to turn on and off the power to the Raspberry Pi with a toggle switch. Therefore, a toggle switch can also be connected to the ControlBlock. There is also a connector for a status LED that indicates the power status of the Raspberry Pi.

The GPIO pins can be accessed from the Raspberry Pi via the I2C interface. The ControlBlock makes it very easy to connect arcade controllers for up to two players. The open-source driver for the ControlBlock can be configured for various controller types. It supports, e.g., arcade controllers that are mapped to game pad devices, as well as a mapping to a MAME keyboard configuration. The ControlBlock also supports, e.g., the polling of SNES and NES controllers so that it also provides the functionality of the RetroPie GPIO Adapter.

If you are interested in getting the ControlBlock for your project, it can be ordered at the shop.

Check Also

Raspberry Pi 3 Model B+ (TM)

All gadgets fully compatible with Raspberry Pi 3 Model B+

Hi everyone! This is a short post about the compatibility of our boards with the …


  1. I built my raspberry with the ControlBlock in my SNES and connected the power switch. but i made the software setup with the switch turned off now the system boots the otherway arround (when i turn the switch to off it boots). can i restore it in the config? thx for your help

  2. I just ordered this for a Raspberry pi 3 b. Will it fit? I see no detail the dimensions. Is there a 3 b+ available?

    Also has anyone found a case with a fan this will fit into?

  3. I just ordered this for a Raspberry pi 3 b. Will it fit? I see no detail the dimensions. Is there a 3 b+ available?

    Also has anyone found a case with a fan this will fit into?

  4. If i have my RPI 3 and i add the control block to it, is it possible to add heat sink and a mini fan or is that not even something considerd? Im new to this. Would that be too much? Also where can i get the same toggle switch?

  5. Hi. I’m planning to build my own “RPi in a SNES case” project and want to buy a ControlBlock for this as it seems to make it a lot easier. As far as I understand it, I can use the original power switch and the original LED with the ControlBlock, right? But what about the SNES reset button? There are many tutorials out there that describe how to build a soft reset circuit but they all use GPIO pins that would be blocked by the ControlBlock, mainly Pins 1, 6 and 7. 1 and 6 are no problem, but Pin 7 seems to be unique. Any idea how I could make the reset button work?
    P.S.: I have a RPi 1 Model B+.

    • I just saw photos of the latest revision and it seems that it allows access to pins 1 to 12. Ist that correct? So I could still use those to connect the SNES reset button and perform a soft reset, right?

      • Hi Thomas, yes – you can use the original SNES power switch and LED. All GPIO pins are accessible also with the ControlBlock attached, so that you should not have any problem with further custom circuit!

  6. I am loving the PowerBlock for use with my RetroPi and was considering picking up an amplifier to use with an 8-Ohm speaker. This should work well since the amplifier requires access to one of the 5V and ground pins and the Powerblock has access to that next to the led and switch pins. I’ve soldered pins there and used them to run a fan thus far. I wanted to hook up SNES ports so have ordered my ControlBlock. It replaces the PowerBlock of course but doesnt seem to give you access to run something to the 5V pin. Will I be able to use this amplifier with the ControlBlock? (https://www.adafruit.com/product/3006)

  7. I have this device and a MiniPac USB device. Which is better to use with a RPi3?

  8. Hi. I built my arcade with this great gadget. Now, I installed Kodi on retropie and I would like use arcade joystick and buttons for control. I tried with Joymap version 0.3, but don’t recognized arcade controls events. Somebody has a sugerence?

    Thanks and luck with your proyects.

  9. I can’t on fresh installed retropie 3.7 with control block rev 1.6.
    I followed all the steps without errors or mistakes, juste deactivated powerswitch functionality in controlblockservice.cfg.

    Am i missing something ?
    Player 1 & Player 2 VCC is for 5V right ?
    Maybe an error on my wiring …

  10. Hi!
    Thans for this excellent addon! 😀
    I have one question, I am using a Super Famicom controller board and SFC pads.
    I’ve soldered the stuff like the image above, but I can’t make the pads work. The switch and LED work as they should tho. Does this have something to do with regional lock on pads? I remember that NTSC pads aren’t compatible with PAL consoles. Any help would be great, as I can’t find a solution. 🙁

  11. Is it possible to stack these to extend the number of controllers to 4? I’m looking to build a 4-player arcade cabinet.

  12. I was wondering whether any of the interrupt lines from the MCP23017s were linked up to any Pi GPIO?

    • The current revision does not have any interrupt lines from the MCP23017s connected to the Pi-GPIOs.
      that is an interesting idea for the next revision, which is planned to be produced within the next two to three months. Would you have a preference regarding the connections?

      • I don’t think so, I suppose any spare GPIO would do (unless another commenter has any better recommendations). I believe that INTA and INTB can be setup to be OR’d together, so you could hook up just 1 interrupt if you wanted to save GPIOs, but it then again it might be nice to have both interrupts available.
        It would mean it would be possible to have the controls interrupt driven, rather than polling the chips, perhaps using the MCP23008 driver (I believe it’s included in Raspbian) which supports MCP23017 and MCP23S17. Though according to http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt the driver only supports interrupts for I2C chips atm, so maybe it wouldn’t be ideal for MCP23S17 at the moment.

  13. I have the control block. Do you sell the SNES adapter board as well? I cannot locate replacement SNES connectors (for cheap that is) from my usual source (eBay).

  14. I See “Coin” Pin, How to Use It ?

  15. Daniel Bulanowski

    Curious to know if anyone could help me figure out how to do the power switch thing with a 3 pronged rocker switch instead?

  16. Brian Austin

    Anyone having issues with “install error #2”? It is looking to update a file during “sudo make installservice”, but the target file is not there. Directory tree enabled in Retropie and all APT updates completed. Also, where can I install this via the semi-automated script mentioned above? Thanks for any help.

    • Certain things changed with the Raspbian version “Jessie” in comparison to “Wheezy”. I have pushed the needed updates for the ControlBlockService2, which fix these issues!

      • Brian Austin

        Thank you! I reformatted and started from scratch. I got a different reason for error#2 this time. Also, if it helps diagnose, my switch also does not work. I posted a pic for reference. I feel like I am missing something simple…

      • I found that one important change did not make it into the yesterday’s updates of the ControlBlockService2. That is fixed now, sorry!

      • Brian Austin

        It works! I think I have an error in my wiring, but that is for me to work on. An awesome addition to the Pi, for sure. Danke.

  17. How down the ControlBlock work with other USB controllers and the hot-swapping ability you have programmed intro RetroPie? I would like to build a 2-player arcade box where I could use only the arcade sticks and buttons except when I feel inclined to plug in retro style usb game pads. I want the arcade sticks/buttons to be player 1&2 unless I add USB gamepads, then I want them to become player 1&2. Will this functionality work with the ControlBlock?

    • The ControlBlock service installs one or two (depending on the configuration) controllers in the system, which appear, e.g., in /dev/inputs/. Usually, they are players 1 and 2. Additional controllers just appear as other controllers in that folder. How the emulators react on these variety of controllers must be configured in the emulator configuration, I guess.

  18. Grant Anderson

    What joysticks and buttons did you use?

  19. Michael Dorsey

    I have my raspberrypi power supply hooked up to my TV via USB. Once I hit the power button on my remote raspberrypi boots up and vice versa wwhen I turn my TV off. It’s a simple solutions to the switch problem.

  20. I installed everything. But how do you map the arcade buttons to the keyboard buttons. It’s been done before but not by me so I know it’s possible. I need the steps after installation.
    Please help!!!
    I use the Slice of PI/O board if you wanna know.
    Thanks in advance!

    • So, you have the ControlBlock and the Slice of PI/O board? I do not understand your setup, I think.
      If you have the ControlBlock installed, you can set the gamepad type to “mame” so that joystick and button events are mapped to the standard MAME key presses.

      • The setup is that the Slice of PI/O board is hooked up to the Pi via GPIO. The arcade buttons are -obviously- hooked up to the board. I don’t have the ControlBlock if I didn’t make that clear before (sorry). There is some activity as when Emulationstation goes dark due to inactivity, and I press any of the buttons or move the joystick, it goes out of the dimness.
        I hope that is sufficient information.
        Thanks in advance!

      • All right, I see. Sorry, but I do not know how to do that easily. I am sure there are other customers of that board that have similar things in mind and discuss this in the forum of the distributor or so.
        The ControlBlock comes with a dedicated ControlBlock service that does this button-key mapping …

      • Can’t really find any help online. But thanks for your help anyway.
        It can be done with this setup. My friend did it before. But because I’m starting again with a fresh SD-Card, I don’t know how to set up the arcade controls.

  21. I can’t get MAME4ALL to work in RetroPie 3.0 with the “gamepadtype” : “arcade” option. I need to have 2 players with joystick and buttons. The controls work in the menu but not when I get into the games. I have tried to use TAB and change settings for input but the games can’t find the controls. Any help ?

    • Jimmy Blaschke


      Have you resolved your issue with the second set of arcade controls not working? I just recently installed the controlblock and finally can play most games, but with only one sit of controllers. Two people can play, but with only one set. I am not sure where to make any changes. I don’t want to make any changes to retroarch config file cause that may take me back several steps.

      Have you had any luck?

  22. Fredrik Svensson

    What have I done wrong when installing ControlBlock drivers and the pie just go halt when rebooting?

    • Sounds as if you need to attach a power switch or you need to disable the power switch in /etc/controlblockconfig.cfg.
      Also, you need to connect the micro USB ONLY to the ControlBlock, if you want to use a power switch. Hope that helps!?

  23. Will this control block also provide power to LED arcade buttons? If not, does anyone know how to power LED arcade buttons power with some type of USB connection?

  24. Joe Scott Volpe

    Hi there,
    I’d like to buy your Control Block.
    I’m just looking for some advice first.
    I’m building a 4 player arcade cabinet. I will have 4 joysticks(16 inputs) and 29 buttons for a total of 45 inputs.

    Will the control block allow me to connect 45 button inputs for my 4 player arcade setup?

    Thanks so much in advance!

  25. Hallo Florian, sorry mein englisch ist nicht gerade gut, daher in deutsch… Muss ich am Micro USB Connector Strom anschließen? Auch 5V, 2A wie der Rasp? Brauch ich also 2 Netzteile wenn ich den Controlblock benutzen möchte?

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.