ESP8266 Community Forum

- Fri Nov 28, 2014 2:32 pm #3474 Hi,

+CIPDISCONNECT is when browser (or any client) closes connection. You should call CIPCLOSE after getting CIPDISCONNECT from ESP - at least I think that order should be.
But at this moment, there is a bug in releasing connection-contex resources and this causes to wdt_reset, check few post ealier, I had written about this too. When I call CIPCLOSE=connection-contex-id and after that, client connect again and send data to ESP next thing that happens is wdt_reset ...

- Tue Dec 02, 2014 3:55 pm #3853 Hello,

I finished compilling atproto command set into spreadsheet (Excel/Calc) , I published it on google drive:
https://drive.google.com/folderview?id=0BySjzBz--msUT3M3TngtR2stN1U&usp=sharing
If you have comments...

- Wed Dec 03, 2014 12:21 pm #3935 Hello saper_2.
I reviewed the description and think it is convenient and useful manual. Thank you very much for your effort.
I have a question - do you have some information about removing bug with occupy/release of the contexts described in previous posts.

- Wed Dec 03, 2014 12:22 pm #3936 Hello saper_2.
I reviewed the description and think it is convenient and useful manual. Thank you very much for your effort.
I have a question - do you have some information about removing bug with occupy/release of the contexts described in previous posts.