ESP8266 Developer Zone

Re: "Non-atomic" +CIPSEND bug

2017-12-25T14:37:28+08:00

Hi, yes, the TCP connection could be ended by the server or the client, you can capture the TCP packets (by omnipeek or wireshark) to check the reason of disconnection.

Statistics: Posted by Her Mary — Mon Dec 25, 2017 2:37 pm

Re: "Non-atomic" +CIPSEND bug

2017-12-22T16:48:08+08:00

Her Majesty wrote:
Message "CLOSE" means the connection is closed, you should stop sending data.
Detect message "CONNECTED" to start a new transmission.

hi，majesty；
you say ,"CLOSE" means the connection is closed,but i want know why the connection closed ?
i know some reasons,such as ;
1 the tcp server could close connection;
2 mcu could send AT cmd to esp8266 ,close connection;
Is there any other reason ?

Statistics: Posted by 朝花夕拾 — Fri Dec 22, 2017 4:48 pm

Re: "Non-atomic" +CIPSEND bug

2017-03-24T14:19:54+08:00

Message "CLOSE" means the connection is closed, you should stop sending data.
Detect message "CONNECTED" to start a new transmission.

Statistics: Posted by Her Mary — Fri Mar 24, 2017 2:19 pm

"Non-atomic" +CIPSEND bug

2016-10-27T20:54:18+08:00

I have a problem with reopen socket until data transfer performed.

For example:

Send to ESP: AT+CIPSEND=1,xxx\r\n
Receive from ESP: OK\r\n
Receive from ESP: >
Send to ESP: ...some...data... (first portion of data)
Receive from ESP: 1,CLOSED\r\n (remote client close connection when data transfered to internal buffer of ESP)
Send to ESP: ...some...data... (next portion of data)
Receive from ESP: 1,CONNECTED\r\n (remote client open new connection when data transfered)
Send to ESP ...some...data... (last portion of data, all data sended)
Receive from ESP: OK\r\n
Receive from ESP: SEND OK\r\n
...

In this case all data for the old connection sent in new connection.

What can I do with this?

Thank you.

Statistics: Posted by Rst7 — Thu Oct 27, 2016 8:54 pm