ESP8266 Developer Zone

Re: client disconnect cause wdt reset

2015-03-23T01:35:22+08:00

can you share a bit of code so I can see what you did please... what exactly did you handle?

Statistics: Posted by jayc75 — Mon Mar 23, 2015 1:35 am

Re: client disconnect cause wdt reset

2015-03-22T23:43:45+08:00

ok, after modifying my code to take into account AT command response may contain response not related to the command, my program is now able to handle multiple connections without a problem.

Statistics: Posted by doughboy — Sun Mar 22, 2015 11:43 pm

Re: client disconnect cause wdt reset

2015-03-22T06:27:35+08:00

I think AT firmware can be improved to not send CONNECT/DISCONNECT and IPD messages if an AT command is pending response.

This will fix this issue once and for all.

Statistics: Posted by doughboy — Sun Mar 22, 2015 6:27 am

Re: client disconnect cause wdt reset

2015-03-22T06:25:19+08:00

After adding lots of debug prints,
I think the main problem is, connection and IPD events messages are getting returned in between AT commands and responses.

For example, if I sent AT+CIPSTATUS

I expect to receive
STATUS:3
+CIPSTATUS:0,"TCP","192.168.1.16",56204,1

OK

but instead I get
+IPD,0,316:GET /test HTTP/1.1
Host: 192.168.1.11
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Cache-Control: max-age=0

STATUS:3
+CIPSTATUS:0,"TCP","192.168.1.16",56205,1

OK

Since I keep reading until I find the string "STATUS", then the entire IPD section is lost.

This is exactly why I think the AT format is more suitable for human interaction, and not for programmability.

Its like you call a function and you get your reply, but together with some other information not related to the function.

Statistics: Posted by doughboy — Sun Mar 22, 2015 6:25 am

Re: client disconnect cause wdt reset

2015-03-21T19:29:41+08:00

I agree, if I send request too fast like using 1ms between each request the module goes nuts and the AT stops working all together... it no longer responds to AT and all I get is one line...

I will create a video demo using the known tools. i'm using V1.0 as well.

Cheers

Statistics: Posted by jayc75 — Sat Mar 21, 2015 7:29 pm

Re: client disconnect cause wdt reset

2015-03-21T15:04:33+08:00

I am still convinced simultaneous connection is not working due to the messages getting all mixed up. I am using latest 1.0 firmware.

for example, if i just do a CIPSEND command, and then sent the data. when I read from serial, I should be expecting SEND OK, but connection string can occur.
Also I have experienced only 1,CONNECT is received, and the +IPD is completely lost.

I have wasted so may days trying to figure how to get this to work.

I really think it will be easier if the source code is available. I can probably find the problem in a few hours.

Statistics: Posted by doughboy — Sat Mar 21, 2015 3:04 pm

Re: client disconnect cause wdt reset

2015-03-20T23:49:37+08:00

I debugged this some more and I think in my case, the hang is due to the second connection is coming in after a CIPSEND

> 1,CONNECT

notice that is comes right after the CIPSEND command, so it is missing the \r\n before the 1,CONNECT, but is just appended to the > (> and space after).
Since my code peeks one character after \n to see if it is a '+' or '0' - '4', it is now unable to detect the 1,CONNECT event.
I think it should be \r\n1,CONNECT always.

Thanks.

Statistics: Posted by doughboy — Fri Mar 20, 2015 11:49 pm

Re: client disconnect cause wdt reset

2015-03-20T20:10:52+08:00

one more thing I've noticed is ESP8266 never servers the request number 10, 100, 1000..
so basically when I get to request 10 and I send a reply from my microcontroller it never reaches the client and always return busy... the same thing happens to request 100 and 1000 all return busy no matter what...

can you please check .

I also noticed an issue in the doc see the attached file below:

thank you.

Statistics: Posted by jayc75 — Fri Mar 20, 2015 8:10 pm

Re: client disconnect cause wdt reset

2015-03-20T17:14:13+08:00

Hi,
Thank you for running the test and looking into this.

the only way you will get to reproduce the bug is when you run MULTIPLE instances of StressTestNetwork.exe at the same time, and you must send a reply from your ESP8266 server to see the issue happening... because it hangs when it tries to process requests and replies...

btw the test firmware is much more stable so whatever your doing is helping keep up the good work

one more request: can you please add support for Multicast to this AT test so I can test it see this post: viewtopic.php?f=16&t=234&p=1098#p1098

Thanks
Cheers,

Statistics: Posted by jayc75 — Fri Mar 20, 2015 5:14 pm

Re: client disconnect cause wdt reset

2015-03-20T10:34:03+08:00

Hi,

Sorry that I still can't replicate your problem, my test log as the picture.

Could you have a try with my test bin file ? if you still have this problem, please offer more information about your test steps or UART1 output logs .

test_at_150317.zip

Statistics: Posted by ESP_Faye — Fri Mar 20, 2015 10:34 am

Re: client disconnect cause wdt reset

2015-03-20T06:32:18+08:00

During my tests I didn't set CIPSTO .... so it freezes! and no longer response to AT commands.

when I tried setting CIPSTO=10 it helped and it does continue to send on the first Channel ID but not the other channels. I also noticed how it chocks every time it gets a second Simultaneous request while using the timeout CIPSTO=10.

I hope this gets fixed soon...

Statistics: Posted by jayc75 — Fri Mar 20, 2015 6:32 am

Re: client disconnect cause wdt reset

2015-03-20T04:13:25+08:00

I noticed a hang on multiple connection even before this fix.

with the latest AT firmware, the first connection is still able to send a response, but second connection is not.
if I specify a CIPSTO, then the server continues to work after the timeout period has elapsed.

Statistics: Posted by doughboy — Fri Mar 20, 2015 4:13 am

Re: client disconnect cause wdt reset

2015-03-20T02:25:00+08:00

Sure,
the same test and program i shared in this topic:

viewtopic.php?f=16&t=243

or you can download the program i use directly from this link:

download/file.php?id=231

Basically start your ESP8266 and start the Server at Port 80, then start the StressTestNetworkWinForm.exe and change the IP Address to your ESP8266, keep everything else as is and hit Start, keep it running and you will notice how it will freeze at some point.

Next to test the Multiple channel issue start another instance of the StressTestNetworkWinForm.exe and hit start while both running and watch how the ESP8266 will freeze when it reaches multiple Channeld ID.

i hope this helps.

btw: if you want the source code of StressTestNetworkWinForm.exe please let me know and i'll be happy to share it, it is built using C# and Visual Studio.

If you have any questions please let me know!

Statistics: Posted by jayc75 — Fri Mar 20, 2015 2:25 am

Re: client disconnect cause wdt reset

2015-03-19T20:27:59+08:00

Hi，

Sorry that I can‘t replicate your problem..

Could you provide more information like your test steps, UART1 output log ?

Statistics: Posted by ESP_Faye — Thu Mar 19, 2015 8:27 pm

Re: client disconnect cause wdt reset

2015-03-19T16:55:35+08:00

HI this new test firmware doesn't reset when a connection fails but it still suffers from handling MULTPLE Connections (Multiple Channels), it starts serving requests ok and then freezes and wouldb't serve anymore requests when two or more request come in a the same time !!!! at least in the old firmware the module would reset and continues to work now it just sits there !!!! please fix before releasing it this into the beta...

output is below....

Code:

0,CONNECT

+IPD,0,29:GET /Hello World HTTP/1.0

AT+CIPSEND=0,235
1,CONNECT

+IPD,1,29:GET /Hello World HTTP/1.0

+IPD,1,29:GET /Hello World HTTP/1.0

AT+CIPSEND=1,235

3,CONNECT

+IPD,3,29:GET /Hello World HTTP/1.0


AT+CIPSEND=3,235

4,CONNECT

+IPD,4,29:GET /Hello World HTTP/1.0

AT+CIPSEND=4,235

any idea ???????

thanks,

Statistics: Posted by jayc75 — Thu Mar 19, 2015 4:55 pm

Re: client disconnect cause wdt reset

2015-03-17T13:07:39+08:00

I now just get
0,CONNECT FAIL

no more wdt reset.

thanks.
when will the sdk with this fix be released?

Statistics: Posted by doughboy — Tue Mar 17, 2015 1:07 pm

Re: client disconnect cause wdt reset

2015-03-17T11:02:54+08:00

Hi,

Sorry for the inconvenience..

Please have a try with the attachment.

test_at_150317.zip

Statistics: Posted by ESP_Faye — Tue Mar 17, 2015 11:02 am

Re: client disconnect cause wdt reset

2015-03-07T04:47:57+08:00

when client disconnects, the esp module should just return on uart the message n,CLOSED where n is the socket id number.

Thank you for fixing.

Statistics: Posted by doughboy — Sat Mar 07, 2015 4:47 am

Re: client disconnect cause wdt reset

2015-03-06T15:59:20+08:00

Hi,

Thanks for your bug reporting, we will fix it ASAP.

Statistics: Posted by ESP_Faye — Fri Mar 06, 2015 3:59 pm

client disconnect cause wdt reset

2015-03-05T13:08:51+08:00

I am using firmware from esp_iot_sdk_v0.9.6_b1
in server mode, if I use curl to connect to server, then I do CTRL-C on curl, the server will wdt reset and program stops running.
I think server must not hang if client disconnects. Actually since the client initiated the connection, the client rightfully should be able to disconnect without causing any problem on the server.

+IPD,0,80:GET /test HTTP/1.1
User-Agent: curl/7.33.0
Host: 192.168.1.11
Accept: */*

0,CONNECT FAIL

ets Jan 8 2013,rst cause:4, boot mode:(1,1)

wdt reset

Statistics: Posted by doughboy — Thu Mar 05, 2015 1:08 pm