Maker Toolkit / Circuit Playground Troubleshooting Guide

Hey all, I’m excited to see how many folks are getting rolling with the Maker Toolkit. I’ve put together a shortish troubleshooting guides that walks through the most common issues I’ve seen here. If there are things missing from this doc that you’ve run into, please let me know so I can add them.


Can the circuit playground be used as a standalone unit when students finish their projects?

Last year I had my CSP students use Unit 6 as a standalone unit. They really enjoyed the circuit playgrounds. Unit 5 Building Apps gives them the ability to jump right into Unit 6 CSD.

I meant, can you unplug the circuit playground from the computer, add a battery and run the code.

Hi Astra,

The board has to be plugged into the computer to work. The code is on the computer, not the board.




My students participated back in the Code Interactive Hackathon held in Dec, 2017 and they posted their project on DEVPOST here is the link:
The project is about an idea for a wearable ring that will connect to your phone when you have an emergency and you can not reach your phone. The group would like to use the Circuit Playground or Microbit to demonstrate how you press the ring to send a signal to your phone via bluetooth. They are working on designing the App Interface. I wonder if there is a way to demonstrate the idea in action.
The group is planning to submit the project to EMOTI-CON showcase.

Thanks a lot


It kind of depends on how important actually demoing the bluetooth component of it is versus demoing the interaction between hardware and an app. If the bluetooth element is more important, then you would probably want to go with the micro:bit and MakeCode. If the interaction between hardware and app is more imporant, then I’d go with the Circuit Playground and App Lab, explaining that the USB cable is playing the role that bluetooth would in a later iteration.


I guess I will stick with the circuit playground and App Lab since my students are designing Apps on App Lap.

Thank you Josh for your prompt response, and hope to see see in Atlanta.

I was wondering about this as well. Why would the circuit playground have an attachment for a battery if it has to be plugged in to work?
does this mean it does not actually have memory of its own? Which then means that it’s not technically a “computer?”
It sure would be nice to be able to unplug it especially since we’re trying to show this as an example of IoT.