There are several commercial and non-commercial options available to control LED displays. These range from small portable displays running on a dedicated microcontroller to large commercial ones that are controlled by custom applications running on a dedicated computer and multiple controllers. WLED is a non-comercial (open source) program and is the probably the best available for portable displays as it supports a wide variety of animations/colour palettes and can be controlled by your cell phone over WiFi. In order to make your own WLED displays, you will need a laptop/desktop and:Continue Reading →
WLED is a relatively new platform for communicating with and animating LED’s without requiring a PC to drive them. As a FastLED afficionado, I’ve been developing my own code to communicate with several displays. The summer of 2019 was spent implementing an MQTT infrastructure that would support my FastLED sketches and after MUCH trial and error, I got it to work as shown here:
As a result of the challenges I faced, this effort took several months and I still didn’t accomplish my goal at the end.Continue Reading →
To be able to control multiple lanterns at the same time in order to create a coordinated display.
The MQTT client library I use for Arduinos (pubsubclient) is ‘blocking’ in that if your connectivity to the server is not reliable, then the display sometimes stutters and possibly stops. I’ve tried some non-blocking workarounds, but it’s not 100% reliable.
In addition, although I can control these lanterns in a lab environment, the message often doesn’t make it through to one of the 10 Arduinos I’m testing with and has to be resent. Therefore, a command for them to simultaneously reboot works maybe 1 in 5 attempts across those 10 lanterns.
As a result, I think that while controlling lanterns via wifi and MQTT is pretty good, controlling them for coordinated displays is not that reliable.
This is the IoT MQTT Panel Pro layout I use for my FastLED based ‘mesh’ sketch. I’ve also got a physical control panel consisting of:
- 2 rotary encoders
- 2 potentiometers
- 4 pushbuttons
I’ve been working on an interactive art project as a favour for a friend of mine that would allow you to push buttons, use rotary encoders, potentiometers and so on in order to control an animated light fixture elsewhere in the room.
These controls would allow you to change:
- Display mode
- Toggle direction
- Toggle glitter
- and so on. . .
To do so, I’m using an ESP8266 enabled FastLED based lantern combined with an ESP32 based control panel. They’re both MQTT enabled, and I’ll be using an Android phone as the wifi hotspot and MQTT broker.
Here’s an email I sent about my progress in wiring and initial coding for the control panel:
I finished wiring up all the pins this morning and . . .
ABSOLUTELY NOTHING WORKED. Wouldn’t even upload to the ESP32. Got out the voltmeter and started measuring:
- LED was wired backwards (causing it to not upload), so I removed it temporarily.
- Some pins didn’t support internal pullup so I had to do some research and re-wiring.
- Didn’t set internal pullup correctly in the code. Found and fixed.
- Got digital pins working with basic digitalRead().
- Found an ESP32 button library, so I don’t have to worry about de-bouncing.
- Got that working with multiple buttons.
- Had to rename the analog ports and got the potentiometers working. Values were backwards, but math fixed that.
- Had previously successfully tested a rotary encoder library, so I added the code.
- One rotary encoder wasn’t working. Swapped wires, was the same encoder. Pins were OK.
- Had a rotary encoder soldering issue (solder blob). Fixed that and got both working as well.
- Soldered on a new WS2812 LED. Installed FastLED and got that working once I found a compatible pin.
- Got some ESP32 network code. It compiled.
- Got my old MQTT networking code. It compiled as well.
- Have smushed together my wifi/MQTT code with FastLED and the various inputs.
- Amazingly, it all still compiled.
Next step will be to start adding MQTT publishing functionality to each of those inputs.
So far so good. This shit takes time to do though. As <other friend> well knows, it can take a LOT of time.
In summary, things typically don’t go as expected, so it can boil down to troubleshooting techniques. Divide and conquer.
Update: The next day, I had the buttons and potentiometer working just peachy. Only problem is, that my mode selector was meant for buttons and I was trying to use a rotary encoder for that. Now have to change code for both the control panel as well as the lantern to accept the values provided by the rotary encoder. Have also got the LED on the control panel to show Red when there’s no network connectivity, Orange when it’s connected, and finally Green when both wifi and MQTT are connected.
As mentioned in my ‘Getting Started’ post, I create separate ‘devices’ for my different Arduino sketches, such as mqtt-LED, mqtt-fire2012xy, mqtt-mesh, and so on. In addition, I may have more than 1 of each type of lantern displaying at the same time. To do so, I will serialize each lantern (it’s in the code) and using a combo box widget, I can then select one or ALL of each device type and publish that to the broker, which will then get picked up by the subscribing device. I’ll then use another widget to send hue, brightness to other information to the selected devices.
In order to support these multiple device types (aka sketches), I’ll add a device prefix to the topic.
For a fire2012 lantern, the published topic can look like this:
Our first example was outlined in “Getting Started withi ESP8266 and MQTT“. This first example uses a sketch called mqtt-LED-synchronous.ino to blink the internal LED. It waits for the wifi initialization, followed by the MQTT initialization to complete before the continuous loop can run.
The second example is called mqtt-LED and appears similar to the first examples, however while the networking and MQTT code are initializing, the loop is running. In addition, if we temporarily lose MQTT connectivity, the sketch will continue MQTT transmission/reception once communications are re-established.
The third example is called mqtt-JSON and adds JSON data exchange to the previous example, allowing for more detailed information to be exchanged between the control panel and the subscribing device.
mqtt-fire is our first example using the FastLED display library. Controls in this example are a combo box, which is used to select from one or more fire enabled lanterns, while the remaining slider controls support brightness, hue, speed, cooling and sparking.
Being able to control an Arduino remotely really ups our automation game. In the beginning, it was buttons and potentiometers and from there, we graduated to Infra Red remote control.
With the widespread availability of IoT (Internet of Things) functionality, we now have Internet connectivity to our Arduino compatible microcontrollers. One method is to setup our Arduino as a web server, and Jason Coon’s ESP8266 webserver is a prime example.
Another option is a messaging protocol called MQTT (Message Queuing Telemetry Transport) which provides a lightweight method of controlling IoT devices, and in this case an ESP8266 based microcontroller.
This tutorial goes through the steps of setting up an Android phone and an ESP8266 based WeMOS D1 Mini with MQTT controls to turn the internal LED of the ESP8266 on and off.Continue Reading →
/* My FastLED Tips, Tricks and Traps
By: Andrew Tuline
Date: July, 2015
These notes are best viewed with an IDE such as Sublime Text. This is NOT a functional program, but a series of notes about using FastLED.
Continue Reading →
This is a compendium, so far of the lantern festivals in Vancouver. Others will be added as I attend them.
Continue Reading →