It basically supports everything in FastLED - all the led chipsets, all the library, etc… It doesn’t have hardware SPI support (yet) but there is bit banging support that’s more than enough for pushing APA102’s right now.
It also doesn’t yet have parallel output support, the jury is still out as to whether or not that will end up working or working well.
No limitation - though there appears to be some things around a handful of pins that you need to be careful about how you use (some of the pins want to be high or low when the chip starts up to determine what mode it starts up in - I still haven’t figured out all the details about what would/wouldn’t work with leds specifically - there are probably other folks out there who have).
I only just started playing with the ESP8266 this afternoon, so I’m still learning my way around it.
@Waldy_Wiz : It new code is checked in to the regular ‘master’ branch on github, but it’s not yet tagged in a numbered release. So check out or download the latest from github at this point; we’ll be tagging it in a numbered release, probably “3.1.2” in the near future.
Everyone please let us know what you find in using this! It’s a totally new platform, and there’s going to be a lot to learn. As always, we’re looking to the FastLED community to share ideas, tips, bug reports, and useful bits of code!
@Mark_Kriegsman I’m using Arduino 1.6.7 (WIN 10) updated under preferences the boards manager URL, loaded Demo Reel, selected under board Generic EPS8266 or Huzzah and get compiler error: http://pastebin.com/dGgGfjnv
Two findings: error occurs when a function is called, eg. Fire2012();
although it is declared with void Fire2012().
Next error under
random16_add_entropy( random());
exit status 1
no matching function for call to ‘random()’
I will try an older Arduino version and report whether the problems are still there.
Update: Arduino 1.6.4 is working without those error messages !
Thanks - I’ll try to reproduce those here. Looks like there’s something possibly wrong with their version of the special ‘preprocessor’ that Arduino (normally) applies to your files before compiling them. The ESP version may be behind.
Please let us know which sketches work for you and which ones give problems – and thank you VERY much for the pastebin compiler output and for your report!
Workaround: If you move the ‘loop’ function down to the bottom of the source file it compiles fine.
Alternatively, you can explicitly forward-declare the Fire2012 function, as you’d have to do in normal C/C++ environments (not Arduino, which tries to do this automatically for you… and fails sometimes!).
You could put this one line right before the loop function:
void Fire2012();
That fixes their compilation problem in this case, too. But if they have this problem everywhere, we’re going to have to forward-declare everything everywhere until they fix it.
[Side note: This is why ‘new’ platforms are always a pain… it just takes time for them to get ALL the bugs out… and in the meantime it make it harder for library developers to figure out which bugs are ours and which are theirs, and which are the offspring of the union.]
Do anyone knows a clear procedure on how to use the esp , as wifi to serial interface , in order to make a " transparent" connection to the teensy . So in summary I would like to get rid of the USB cable and update my LEDs projects on teensy via wifi , and also use the wireless comunication channel to talk with the user interface .
There is a project here , but is not clear how to configure the arduino ide to make the trick.
@Gustavo_K , it’s a USB enumeration problem. You want the host machine to believe the teensy is actually plugged into it. A friend pointed me to Silex. I’m using their wireless solution. It’s not cheap, nor is is small, but it works beautifully.
Thanks for the responses ,
It should be able to do it without any additional hardware just the teensy and the esp 8266 , it is the esp software side and the teensy+ide configuration what is not clear to make a wireless replacement of the USB wire.
It seams it is much easier with Bluetooth …l
@Gustavo_K : interesting topic! Would you start a new post with your question and let’s see what people come up with? (I think it’s getting buried down here.)