Stop breadboarding and soldering – start making immediately! Adafruit’s Circuit Playground is jam-packed with LEDs, sensors, buttons, alligator clip pads and more. Build projects with Circuit Playground in a few minutes with the drag-and-drop MakeCode programming site, learn computer science using the CS Discoveries class on code.org, jump into CircuitPython to learn Python and hardware together, or even use Arduino IDE. Circuit Playground Express is the newest and best Circuit Playground board, with support for MakeCode, CircuitPython, and Arduino. It has a powerful processor, 10 NeoPixels, mini speaker, InfraRed receive and transmit, two buttons, a switch, 14 alligator clip pads, and lots of sensors: capacitive touch, IR proximity, temperature, light, motion and sound. A whole wide world of electronics and coding is waiting for you, and it fits in the palm of your hand.
Python for Microcontrollers — sysfs is dead! long live libgpiod! libgpiod for linux & Python running hardware @circuitpython @micropython @ThePSF #Python @Adafruit #Adafruit
Get the only spam-free daily newsletter about wearables, running a "maker business", electronic tips and more! Subscribe at AdafruitDaily.com !
Useful info! Is it possible to customise their function, or populate the empty pads on the Model A and use them for something else?
@Kieran The short answer is no, with the possible exception of the ACT LED, which could probably be customized with some low-level driver changes.
The longer answer is that the power LED is directly connected to the power supply rail (schematic page 4, E2), and the FDX, 100 and LNK LEDs are directly connected to the USB/Ethernet chip which will control them using hardware (schematic page 3, G6). The ACT LED goes to a GPIO pin on the SoC, which means its purpose is set by software (schematic page 2, B5).
Cheers Sam, I’d come to a similar conclusion, GPIO 16 (Act LED) doesn’t seem to be modifiable from within the OS sadly. Ah well, just a thought!