- Mon Aug 01, 2016 3:46 am
#51878
Sorry, thought I'd already replied to this but must have messed it up!
Mmiscool - that would be brilliant, amazes me how fast responses are here, far better than any request system I've encountered elsewhere. And I've been doing IT stuff for a very long time.
Forlotto - I agree about ping being a really useful tool in a lot of circumstances! I'm sorry I didn't really explain what prompted the initial post - an espbasic user had posted on the forum about performance issues and it made me think. The issue is when the esp is acting more-or-less automomously, and we only have access to stuff at the esp8266basic interface driven by the program.
It seemed to me possible (without knowing how esp8266basic or the user's code worked) that one possible cause was the esp trying to write to a non-existant connection. If say your esp is operating as a thermostat, you might want to prioritise turning heat off over updating thingspeak, but also extend your logging so you could apply the data later. Imagine using your dimmer to keep light levels in a room constant, where some of the light came from a window. If you can't update the dimmer output because you're waiting for some logging action to timeout, and as a result it all gets too bright, result unhappy....
I worked on something similar for a friend's immersion heater that if the control loop took more than a millisecond to execute it was too long.
Where IP networks are involved, the vast potential variance makes it harder to do things to a timetable. As you say, many ways to get round it...all good fun!