This library lets you control the addressable RGB LED strips from Pololu Robotics & Electronics.
This is a library for the mbed that allows you to control these addressable RGB LED products from Pololu:
- Addressable RGB 30-LED Strip, 5V, 1m (SK6812)
- Addressable RGB 60-LED Strip, 5V, 2m (SK6812)
- Addressable RGB 150-LED Strip, 5V, 5m (SK6812)
- Addressable RGB 60-LED Strip, 5V, 1m (SK6812)
- Addressable RGB 120-LED Strip, 5V, 2m (SK6812)
- Addressable High-Density RGB 72-LED Strip, 5V, 0.5m (SK6812)
- Addressable RGB 30-LED Strip, 5V, 1m (WS2812B)
- Addressable RGB 60-LED Strip, 5V, 2m (WS2812B)
- Addressable RGB 150-LED Strip, 5V, 5m (WS2812B)
- Addressable RGB 60-LED Strip, 5V, 1m (WS2812B)
- Addressable RGB 120-LED Strip, 5V, 2m (WS2812B)
- Addressable High-Density RGB 72-LED Strip, 5V, 0.5m (WS2812B)
- Addressable Through-Hole 5mm RGB LED with Diffused Lens, WS2811 Driver
- Addressable Through-Hole 8mm RGB LED with Diffused Lens, WS2811 Driver
- Adafruit 16 WS2812 LED NeoPixel Ring
- Adafruit 24 WS2812 LED NeoPixel Ring
- Adafruit 15 WS2812 LED NeoPixel 1/4-Ring
- Adafruit 5×8 WS2812 LED NeoPixel Shield for Arduino
- Addressable RGB 30-LED Strip, 5V, 1m (High-Speed TM1804)
- Addressable RGB 60-LED Strip, 5V, 2m (High-Speed TM1804)
- Addressable RGB 150-LED Strip, 5V, 5m (High-Speed TM1804)
This library is optimized for the SK6812 and WS2812B, so it transmits colors in green-red-blue order.
If you have a WS2811 LED or a high-speed TM1804 LED strip, please note that its red and green channels are swapped relative to the WS2812B, so you will need to swap those channels in your code. You might prefer to use the version of the library from October 2013, which does not require you to swap red and green in your code.
If you need to control the older, low-speed LED strips (items #2540, #2541, and #2542), you will need to use the version of this library from March 2013.
This library allows complete control over the color of an arbitrary number of LED strips with an arbitrary number of LEDs. Each LED can be individually controlled, and LED strips can be chained together.
This library should also work with any other LED strip based on the SK6812, WS281x, or TM1804.
This library has been tested on the mbed NXP LPC1768 (Cortex-M3 at 96 MHz), the mbed NXP LPC11U24 (Cortex-M0 at 48 MHz), and the NUCLEO-F303K8 (Cortex-M4 at 72 MHz). It will probably work on many other boards without modification.
This library does not work on chips families such as the STM32F4 where there is a single register for setting and clearing the value of an output pin. The library checks for the GPIO_IP_WITHOUT_BRR preprocessor macro and triggers a compile-time error if that macro is set.
Here are two example programs that show how to use the library:
This is an example program for the PololuLedStrip library. It generates a simple moving rainbow pattern.
This is an example program for the PololuLedStrip library. It generates a simple moving gradient pattern.
As a first step, you should compile and upload one of these to the mbed. When the program runs, the mbed should output color data on pin p8 dozens of times per second. The expected signal is documented on the Pololu website. The example programs only send colors for 60 LEDs, but they can easily be changed to send more for a longer strip.
The addressable RGB LED strips can be purchased on Pololu's website using the links above.
The LED strip’s data input connector has two pins that should be connected to the Arduino. The LED strip’s ground will need to be connected to one of the mbed’s GND pins, and the LED strip’s signal input line will be need to be connected to one of the Arduino’s I/O lines. Our example programs assume the signal line is connected to p8. These connections can be made using two Male-Female Premium Jumper Wires, with the female ends plugging into the LED strip and the male ends plugged into a breadboard that houses the mbed.
You will also need to connect a suitable power supply to the LED strip using one of the power connectors. The power supply must be at the right voltage and provide enough current to meet the LED strip's requirements.
If everything works properly, you will see a moving pattern of colors on the LED strip.
This library takes about 1.3 ms to update 30 LEDs (1 meter). The LED strips use a high speed one-wire protocol with relatively strict timing requirements, so this library disables interrupts to ensure reliable color transmission. Unfortunately, disabling the interrupts could cause problems in other libraries that uses interrupts.
This library provides an
interruptFriendly option that can let it coexist with interrupt-based libraries. When this option is enabled, the library will temporarily enable interrupts after each color is sent, about every 45 microseconds. If you can keep all of your interrupts short enough, then this option should allow this library to work in conjunction with your interrupt-based libraries. However, if you have an interrupt enabled that takes too long, then this interrupt will sometimes cause an extra long low pulse to emitted, which will be interpreted by the LED strip as a reset command. This can cause visible flickering in the LED strip. To turn on the
interruptFriendly option, add this line to the beginning of your
PololuLedStrip::interruptFriendly = true;
Chaining LED Strips together
No special code is required to chain LED strips together. An X-meter LED strip chained to a Y-meter LED strip can be controlled in exactly the same way as a single (X+Y)-meter LED strip.
Revisions of PololuLedStrip.h
|19:46d7ab0ba3e7||2013-10-09||Changed the timing so that this library only supports the high-speed strips now.||File Diff Annotate|
|18:34ba573573df||2013-03-01||A link in the docs didn't work, so I removed it.||File Diff Annotate|
|7:9a088f042ee0||2013-03-01||Things are still working well.||File Diff Annotate|
|1:102307d9b701||2013-02-27||Initial commit.;||File Diff Annotate|
|0:06475317f283||2013-02-27||Still working;||File Diff Annotate|