- Mon Jun 27, 2016 3:22 am
#49854
We use 2016 May 11 AT non-SDK firmware.
We try to use th following AT command
AT
ATE0
AT+CWMODE_CUR=1
AT+CWJAP_CUR="ZYXELO","84149929"
AT+CIPSTART="TCP","192.168.91.2",5001
AT+CIPMODE=1
AT+CIPSEND
...
then we try to random send data to server, and get echo data from server.
(Half-duplex). Each time, we send the data less than 1460 bytes.
Our server is very simple linux socket code, just like
n = recv(socket, buffer, BUFFER_SIZE);
sendbytes =send(socket, buffer, n);
In most case, the esp8266 module can get correct echo packet and report it to MCU.
But sometimes, error happen:
the server echo correct data , however, the esp8266 returns shorter packet,
and sometimes the return packet has corrupt data.
Does anyone see this kind error?
It seems that data loss between ESP8266 to MCU...
We try to use th following AT command
AT
ATE0
AT+CWMODE_CUR=1
AT+CWJAP_CUR="ZYXELO","84149929"
AT+CIPSTART="TCP","192.168.91.2",5001
AT+CIPMODE=1
AT+CIPSEND
...
then we try to random send data to server, and get echo data from server.
(Half-duplex). Each time, we send the data less than 1460 bytes.
Our server is very simple linux socket code, just like
n = recv(socket, buffer, BUFFER_SIZE);
sendbytes =send(socket, buffer, n);
In most case, the esp8266 module can get correct echo packet and report it to MCU.
But sometimes, error happen:
the server echo correct data , however, the esp8266 returns shorter packet,
and sometimes the return packet has corrupt data.
Does anyone see this kind error?
It seems that data loss between ESP8266 to MCU...
