so i upgraded to staging, with SDK 1.3, replaced the nointurrupts with the savedPS, and it is looking pretty good. adding the bail out using _getItrrCount(), returning an error code from show(), and then using that to resend the pixels works really well, it works for my ADAlights too.. I thought i'd measure how often it was failing.. using 100 LEDs, it was failing 1-6 every 10 seconds or so, but not very much... use ping -f and you can see the effect on failed sends...

@forkineye I've just tried out the microajax, and progmem methods you have for your web pages. I like it. Do you get a couple of second pause between each request when u load a page? for each of the page..1-2 sec.. microajax.js... 1-2 sec... style.css...1-2 sec...values...

occasionally i seem to get a crash as well... the stack dump pointed to 40101da4 <pvPortMalloc>:

i want to move my dynamic content over to ajax which is why I'm interested

the web stuff needs some work. any other traffic causes serious lag in the interface. the biggest issue is multiple requests. i'm going to redo it in the future so it doesn't ahve to load the css each time

@forkineye I modified a program to use your UART driver ESPixelUART.cpp. The program drives an 8x8 array at 30 fps. No problem so far with crashes. 20 minutes of "sudo ping -A <IP addr>" does not crash it. Using git commit aafacdc (Aug 16) to build the program so this is very close to the latest. I should have another 8x8 next week so can try 128 LEDs at once.

@sticilface I use the Huzzah board preset with CPU freq 160 MHz. No way to change the Flash freq and I am not sure what the default is.@forkineye Trying different patterns. No problems. The program implements the Open Pixel Control protocol(same as Fadecandy) so I am running various Fadecandy demos. The program does not implement the fc advanced dithering and interpolation. It just receives pixel values via TCP then pushes the pixels to the LEDs.

i actually got it to work up to 300, fell over at 400 though... thats fine.. i managed with the new SDK to run 400 using my other method! but 200 is plenty..using the latest staging, the web server is printing out every request, despite DEBUG not being defined, in the web server... i can't seem to find where the output is coming from though!