The ControlBlock also finds on the model b. However, one difference between B and B+ is that B needs a bit more power than B+. Depending on your power supply this might lead to instabilities with the power switching component on the ControlBlock, because the MOSFET on it adds a small voltage drop.
Hope that helps?
I have just released a post about the virtual COM port of the GamepadBlock. I hope that answers your questions! You can find it at https://blog.petrockblock.com/2017/11/11/using-virtual-com-port-gamepadblock/
@ortsac hate to hijack this, do you have pictures of your completed project? You may have built exactly what I need to build myself for the misses. I am looking to also emplace a Pi3 into an authentic NES console, for use just for NES and SNES emulation. I would like to bounce some ideas of you if possible as well as get some feedback/guidance of any issues you may have ran across.
Yes, and while it wasn't the wiring, it was a fault in the board which was preventing a pin's signal being received.
I was able to replicate the issue on another Pi by removing the connection for either the Latch or Clock wires, so I suggest checking those first.
The new GamepadBlock supports switching between the various controller modes via a virtual COM port.
For the ControlBlock a Bash script could be written that changes the controlblockservice.cfg file and reloads the ControlBlock service. I have not had time to work on that yet, though.
@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.
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.
I`m sure meanwhile you solved the Problem.
Do you remember what has been the reason for the controlblock showing all Buttons are constantly "ON"?
I am trying to set up a new Arcade Station with RPi3+Controlblock V1.6 + 2 x Sanwa Joysticks & Buttons and I have the same Problem right now.