ESP8266 Community Forum

- Sun Feb 05, 2017 10:00 pm #62121 hey Mike,
Sorry to bug you just wondered if you have had a chance to look at this?
Do you have any thoughts on whether this issue can be resolved?

I know you are probably busy just haven't heard anything.
Thanks in advance
dwight

- Sun Feb 05, 2017 11:56 pm #62124 It is confirmed this is a problem.

https://learn.adafruit.com/neopixels-an ... s/overview

It has to do with the precise timing of the neopixels and not being able to write to the servos at the same time.

Serial terminal in the chrome browser see https://serialTerminal.com

http://esp8266basic.com
A BASIC interpreter for your ESP

Working now on Autodrop3d. A 3d printer with automatic part ejection system. https://autodrop3d.com

- Mon Feb 06, 2017 9:47 pm #62199 Hi Mike,

Thanks for shedding some light on this.

So just one follow up Q.

Do you know why a NEO statement kills the IO(SERVO) output for a full 25 - 30 seconds??

Whereas a NEO statement only suspends a IO(PWO) output for a very short duration just while the NEO data is being sent, then the PWO comes right back but the SERVO output stays off for a LONG time then comes back on its own.

This would not be such an issue if the SERVO came right back after the NEO data was sent.

thanks again
dwight

- Fri Feb 24, 2017 12:29 pm #62977 hi Mike,

Sorry to belabor this issue... but do you know if it is going to be possible to at least make the delay/interruption in the SERVO output only last while the NEO data is being sent??

As it is now for some reason the SERVO output stays off for a LONG time (>20 seconds) even when there is no NEO data being sent.

It would be nice if it at least behaved like the PWO output where it is only interrupted during actual NEO data then it comes right back.

Thanks for any light you can shed as to why the SERVO output stays off for a LONG time.

regards
dwight