You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Gordon
So you're saying that the requests are actually being seen by the Espruino board and handled, just not being replied to over the network?
Roughly how many requests per second are you sending when this becomes a problem?
Could you run
E.getErrorFlags()when it happens to see if Espruino's input buffer has ever got full and dropped characters? It should return[]if all is well.You could also try
wifi.at.debug()to start dumping the communications to the ESP8266, to see if it's a problem with Espruino not sending the responses, or if it's the ESP8266 itself getting swamped.My guess is it might be the ESP8266 itself though - in that case I'm not really sure what to suggest... I guess if you see some error message from the ESP8266 after doing
at.debugthen we could handle that and use it to do something - I'm not sure what would be appropriate though.Is it possible that the computer sending the requests has just left a bunch of connections open? In that case the ESP8266 would have to wait until they timed out before it was able to open more.