Extremely interesting. $3? More info needed, were to buy, etc...
In response to the networking question. As long as you are using unicast, the 802.11 access point (wireless router etc) or a network switch (a true hub is impossible to purchase these days) will send only properly addressed unicast packets (and broadcast / multicast packets) to a device. I would NEVER recommend the use of multicast unless you have multiple controllers that need to output exactly the same information. Even then it is better to send the same data to multiple destinations using unicast packets. It is better to waste a bit of a universe and assign the data for a different controller to a new universe than it is to use multicast and flood the entire network when only a few devices need any particular piece of data.
With that said, I would take 10 or 20 of these. They are the right size to put at the base of a pair of arches or even have one per element in the yard (this year I get to have a large yard). This would significantly cut down on the wires in the yard. FYI: I run a separate 802.11AC network with 1.2Gb capacity for my lighting show (a router and firewall separate my show network from my home network). I have a couple of Raspberry PIs that I sprinkle around. This device would be even better. Do these devices support WPA2 and how would it be configured?
ESP-01 / EPS8266 - WS2811 / WS2812 NEO Pixel controller
#Martin, I am completely with you on the Unicast / Multicast, unless you have lot of devices using the same universe, Unicast is much better for this application.
Yes it supports WPA2, I am using it.
SSID and Password appears to be persistent and stored in flash, Somewhere else than other than the core program memory.
The device is a ESP-01 - ESP8266. I have just ordered 10x off ebay to do some more testing.
By default, it works like a modem and uses AT commands. I was going to use it with a Arduino Nano V3, but the Nano does not really add any value. - Too little memory.
So I have used the ESP SDK, and what fun it is!!! Trying to find good and correct information, in english is hard going.
I opted to use windows to do the compiling, not only is it a pain to setup, lots of things!, seem much harder to get working.
So I am going to try it on linux.
It's not just this IC manufacturer, but why do companies design great uC for public use, then restrict access to device information with NDA's - Legal Morons!. In my experience, the competition are the first people to have copies of secret documents, without NDA's.
The programming reference, its distracting, Every page is watermarked "Confidencial" yet the document is Publicly accessible on there website. Sorry - Ranting!!
By using unicast, only 3 pieces of information need configuring in the device. SSID, Password and Pixel Colour order.
The device obtains it IP Address using DHCP, if you what to control the IP Address of each module, most routers allow IP assignment by MAC, if not, turn off the DHCP in the Router and running your own DHCP on the PC.
I have only tested this with 800kHz pixels. But it should be easy to change it to 400kHz
I guess the pixel colour order could be changed in Vixen filters, but i could not make it work / figure it out.
Pixel length is defined in the Universe frame.
Currently there are some timing issues !!! I am trying to iron these out.
I have also been working on a configuration GUI / Webpage. So you do not need to hard code and compile them.
With regards to Data through-put, if we stick with unicast and do not overload the receiver with to many pixels, its really down to the Wifi Router, link speed, the limitations of 802.11g. These days, the ISM band is a busy place!!
It is important to use radio channels with very few other users and preferably those with weak neighbors.
if the spectrum is busy, the packet lost will be greater and cause packet to be re-sent, this will slow the packets down, packets then backup and the frame rate will drop. If the spectrum is very busy, you will drop UDP frames completely.
Assuming you dedicate a WiFi Router to the cause and you can get a link speed of 54Mbits/s. The maximum data rate is going to be around 5180 E.1-31 universes / second ish.., @ 20Hz = 259 universes. With 510 Channels = 170 Pixels per universe. = 259 * 170 = 44030 Pixels @ 20Hz. - Of course, this is the maximum, I would budget for no more than 50% of this.
i.
Has more progress been made on this? I have been playing with the ESP8266 and I have one setup running NodeMCU and lua scripts to send temperature data to thingspeak. I would like to use these to make a Santa hat my kids can wear that is synced to the music. Last year I got into redirecting pixel data from Vixen to a webpage so viewers could change the lights from their car. This seems like the next step. Let me know if I can help you in testing.
Ceer123 wrote:Has more progress been made on this? I have been playing with the ESP8266 and I have one setup running NodeMCU and lua scripts to send temperature data to thingspeak. I would like to use these to make a Santa hat my kids can wear that is synced to the music. Last year I got into redirecting pixel data from Vixen to a webpage so viewers could change the lights from their car. This seems like the next step. Let me know if I can help you in testing.
I have something that is a work in progress using an esp-01 and the nodemcu firmware. I'm in the process of testing 2 outputs of 150 pixels in xlights. So far, it's working ok but occasionally the module will "lock up", requiring a reboot of the esp-01. I'll keep you posted as the testing progresses.
