- Home
- Product Categories
- micro:bit
- SparkFun controller:bit - micro:bit Carrier Board (Qwiic)
SparkFun controller:bit - micro:bit Carrier Board (Qwiic)
The SparkFun controller:bit is a fun-filled "carrier" board for the micro:bit that, when combined with the micro:bit, provides you with a fully functional controller system. Designed in a similar form factor to the classic Nintendo controller, the controller:bit is equipped with a four-direction "D-pad" on the left side of the board and two action buttons on the right side of the board. The two push buttons on the micro:bit in the center function as start and select to complete the NES controller form factor.
The controller:bit connects to the micro:bit via an edge connector in the center of the board, making setup easy. This creates a handy way to swap out micro:bits for programming, while still providing reliable connections to all of the different pins on the micro:bit. We have also included several poke home connectors on the back of the board that correspond to each button on the controller:bit, allowing you to use external parts to control your game, robot, or anything your heart desires!
If you are thinking, "Hey, this looks an awful lot like the SparkFun gamer:bit." You're correct! This is the latest revision of the gamer:bit with some updated components and a Qwiic connector! We found that this board could not be contained by the "gamer" name as we used it to control everything from robots to weather stations!
Note: The SparkFun controller:bit does NOT include a micro:bit board. The micro:bit will need to be purchased separately.
The micro:bit is a pocket-sized computer that lets you get creative with digital technology. Between the micro:bit and our shield-like bit boards you can do almost anything while coding, customizing and controlling your micro:bit from almost anywhere! You can use your micro:bit for all sorts of unique creations, from robots to musical instruments and more. At half the size of a credit card, this versatile board has vast potential!
- Edge connector for ease of use with the micro:bit
- Full direction “D-pad”
- Two action buttons
- NES controller style
- Poke home connectors for external inputs (i.e., arcade joystick and buttons)
- Qwiic Connector
SparkFun controller:bit - micro:bit Carrier Board (Qwiic) Product Help and Resources
Wireless Remote Control with micro:bit
January 21, 2019
In this tutorial, we will utilize the MakeCode radio blocks to have the one micro:bit transmit a signal to a receiving micro:bit on the same channel. Eventually, we will control a micro:bot wirelessly using parts from the arcade:kit!
micro:arcade Kit Experiment Guide
July 21, 2017
We love games! We love writing games, building games and yes, even building game consoles. So we want to introduce to you the micro:arcade kit for the micro:bit!
Getting Started with the micro:bit
September 2, 2021
The BBC micro:bit is a compact, powerful programming tool that requires no software installation. Read on to learn how to use it YOUR way!
Comments
Looking for answers to technical questions?
We welcome your comments and suggestions below. However, if you are looking for solutions to technical questions please see our Technical Assistance page.
Customer Reviews
No reviews yet.
I have a remote control program using 2 microbits with the controller bit and the Sphero RVR. This works fine with microbit V1. but gives an error with the microbit V2.
I already contacted Sphero about this issue and this was their response:
Here's what I found: here is what we are able to verify: the Sphero RVR SDK extension works with the micro:bit V2 (Which we knew). We tested this out by running only a program using RVR commands on a V2 micro:bit connected to a RVR. No error message came up mentioning V1 or V2 errors ( or any errors at all). We took the program that was sent to us and tried to load it to a V1 and a V2 micro:bit. The V1 micro:bit worked fine as expected. The V2 error was exactly what the customer was seeing. Knowing #1 and #2 above, we did some more isolating of the issue. In looking at the RVR program file the customer sent us, we noticed that the gamer:bit extension is present but the program isn’t using the 2 blocks that are available. We reproduced the program file by copy and pasting the JS and starting a new program (without the gamer:bit extension installed in the program) and the program worked without issue. Based on this, we came to the realization that the gamer:bit extension (which says it is in Beta still) is likely the culprit of the error. Any time the gamer:bit extension is loaded into the program, we got the error you are seeing.
I would greatly appreciate a solution to this problem!
Thank you in advance!