2.1 fixed the color issue for me. Thank you
Thanks to some private conversations with Shelby, my problem is SOLVED :biggrin:
I just wanted to follow up here in case anybody else runs into similar issue. My problem turned out to be a flaky jumper between USB adapter and ESPixelstick. All is working now. :thup:
sporadic wrote:It looks like it's in programming mode, but failing out as it begins. Did you try another ESP-01 module as well? It could be the ESP-01 module, USB cable, or serial adapter. If you're having issues with the other modules, can you post a pic of your programming setup?
sporadic wrote:I'm including the .efu files in the firmware release zip. You just upload them via the admin page and that's it. There are two in the 2.0 release package, one for pixel mode and one for serial mode. Feel free to switch them around and take it for a test drive 🙂
I think I may be confusing Flashing a new firmware version and configuring the board. When you talk about 'uploading' a new .efu file, I'm assuming you do this to upgrade the firmware over a USB connection to your computer. Then you can update the config OTA. Do I have this correct or is there some way to update the firmware OTA? If you can, where/how do you upload an .EFU file? How does the stick find it on your pc?
michaelc wrote:I think I may be confusing Flashing a new firmware version and configuring the board. When you talk about 'uploading' a new .efu file, I'm assuming you do this to upgrade the firmware over a USB connection to your computer. Then you can update the config OTA. Do I have this correct or is there some way to update the firmware OTA? If you can, where/how do you upload an .EFU file? How does the stick find it on your pc?
The .EFU files are for flashing via the web interface, but you have to be on the 2.0 firmware to do it. Once 2.0 is loaded (via serial connection using either the flash tool or Arduino), you can then update or switch firmware by uploading the .EFU file via the admin page.
Shelby, I know you were working on the GECE problem and had tested the newest firmware on a set of GECE's, but is it fixed and what exactly was happening to cause the timeout error? I want to make sure I go in to this season hopeful I won't have to reset strings that have gone to sleep. Why doesn't the same thing happen with a set of ws2811's?
scootchu wrote:Shelby, I know you were working on the GECE problem and had tested the newest firmware on a set of GECE's, but is it fixed and what exactly was happening to cause the timeout error? I want to make sure I go in to this season hopeful I won't have to reset strings that have gone to sleep. Why doesn't the same thing happen with a set of ws2811's?
The GECE protocol has to be bit-banged and is VERY slow, whereas I do some tricks with the UART to offload generation of the ws2811 signal. Bit-banging the protocol required interrupts to be disabled, but you only have so long before the wifi stack has to be serviced and things go sideways (watchdog reset). The issue last year was that there was an update to the Arduino core (more particularly, to the ESP8266 SDK included) that caused the resets to trigger while the GECE packet was being sent. Everything was working fine when I was developing and testing, however by the time the kits had shipped and people were using them in their shows, the Arduino core had updated. Depending on when you flashed yours, you could or could not have experienced the issue. I don't use GECE's in my show, so I never noticed anything. I was able to later verify the issue on the 60 pixel GECE matrix. The updated code changes the way the GECE packet is generated and I've tested it for over 48hrs with no reset issues.
Thanks for that answer. I know for one I am thankful for all that you do and amazed at how you do it. I have all me new modules built and I will re-flash all my modules from last year with the latest firmware.
Just thought I'd share.
pixelpuppy wrote:Thanks to some private conversations with Shelby, my problem is SOLVED :biggrin:
I just wanted to follow up here in case anybody else runs into similar issue. My problem turned out to be a flaky jumper between USB adapter and ESPixelstick. All is working now. :thup:
I only had the time to build my 3 a couple days ago. I tried flashing each of them using Shelby's flash tool last night and ran into the same kind of problems pixelpuppy reported
Here is a description of my flashing connection (don't laugh too hard, I used what I had available): 6ft Sargent USB to 9-pin D-Sub cable (FTDI inside) -> 5ft Cisco blue console cable (9-pin D-Sub to male RJ-45 -> female RJ-45 breakout board to screw terminals -> screw terminals connected to old computer floppy drive power connector plugged onto the board. Pile of wire in a heap with multiple connections at high baud rate. Hmmm, I guess I can understand why I'm not getting comms.
I have a Prop Plug but no jumpers (once again, don't laugh too hard). I ordered the KEDSUM CP2102 Module as much for the header cables as anything. It arrives tomorrow. It will simplify my connection significantly. I'll try again then.
Thank you for fixing GECE.
Okay. I've got 9 ESPixelSticks and 4 RENEsp boards programmed. I'm realizing that the crappy old router I'm using is a bit flaky so I'd like to get some suggestions on routers. I have this router outside my house currently in an enclosure but I'm willing to consider an outdoor router. What is a good, stable but not break the bank router to use. This will be the workhorse for my entire show.
Thanks.


