client disconnect cause wdt reset

doughboy
Posts: 63
Joined: Thu Mar 05, 2015 1:54 am

client disconnect cause wdt reset

Postby doughboy » Thu Mar 05, 2015 1:08 pm

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

ESP_Faye
Posts: 1638
Joined: Mon Oct 27, 2014 11:08 am

Re: client disconnect cause wdt reset

Postby ESP_Faye » Fri Mar 06, 2015 3:59 pm

Hi,

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

doughboy
Posts: 63
Joined: Thu Mar 05, 2015 1:54 am

Re: client disconnect cause wdt reset

Postby doughboy » Sat Mar 07, 2015 4:47 am

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.

ESP_Faye
Posts: 1638
Joined: Mon Oct 27, 2014 11:08 am

Re: client disconnect cause wdt reset

Postby ESP_Faye » Tue Mar 17, 2015 11:02 am

Hi,

Sorry for the inconvenience..

Please have a try with the attachment.
Attachments
test_at_150317.zip
(168.85 KiB) Downloaded 369 times

doughboy
Posts: 63
Joined: Thu Mar 05, 2015 1:54 am

Re: client disconnect cause wdt reset

Postby doughboy » Tue Mar 17, 2015 1:07 pm

I now just get
0,CONNECT FAIL

no more wdt reset.

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

jayc75
Posts: 23
Joined: Sun Feb 15, 2015 6:44 pm

Re: client disconnect cause wdt reset

Postby jayc75 » Thu Mar 19, 2015 4:55 pm

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: Select all

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,

ESP_Faye
Posts: 1638
Joined: Mon Oct 27, 2014 11:08 am

Re: client disconnect cause wdt reset

Postby ESP_Faye » Thu Mar 19, 2015 8:27 pm

Hi,

Sorry that I can‘t replicate your problem..

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

jayc75
Posts: 23
Joined: Sun Feb 15, 2015 6:44 pm

Re: client disconnect cause wdt reset

Postby jayc75 » Fri Mar 20, 2015 2:25 am

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!
Attachments
stresstest.PNG
stresstest.PNG (81.34 KiB) Viewed 4147 times

doughboy
Posts: 63
Joined: Thu Mar 05, 2015 1:54 am

Re: client disconnect cause wdt reset

Postby doughboy » Fri Mar 20, 2015 4:13 am

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.

jayc75
Posts: 23
Joined: Sun Feb 15, 2015 6:44 pm

Re: client disconnect cause wdt reset

Postby jayc75 » Fri Mar 20, 2015 6:32 am

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...

Who is online

Users browsing this forum: No registered users and 1 guest