Closed bialabs closed 5 years ago
according to this log, everything is OK with the library and the sketch. esp8266 has problems to connect to that site or to Internet. so it is a problem with the network.
or the esp8266 has restricted 'visibility' to AP and/or is underpowered so it has problems to transmit
or there is some RF interference
"busy p..." is "busy processing". this is a response of the AT firmware to the ?
'ping' from the library. the AT firmware responds so the library waits until next timeout.
the AT firmware responds with error messages. one is "SEND FAIL", one is "DNS Fail".
I run your sketch without problems.
using an external antenna attached to the esp seems that works better! I think is a RF interference problem because my esp is near the router thank you for your advices
in which conditions the library responds with: To much garbage on RX ?
after that error client.connect stops working. How to avoid that?
in which conditions the library responds with: To much garbage on RX ?
after that error client.connect stops working. How to avoid that?
after 25 ignored lines waiting to match the expected response. usually there are ignored lines with some notifications from the AT firmware and at reset there are around 22 boot log lines. I implemented this to detect wrong connection for example with unconnected RX pin or without ground connected between Arduino and esp8266.
can you show the log?
i'll explain better my case i am using your library in a project where i send the content of multiple files (many) from sd to server. Each file i make a client.connect and a get request. The strange part is that i have this error always after 255 client.connect. In the log i get:
(until this connection, all was working good with no problems)
esp> AT+CIPSTART=4,"TCP","www.myserver.com",80 ...sent
esp> ?
esp> busy p... ...ignored
..(repeated 25 times)..
esp> ?
esp> busy p...esp ERROR: To much garbage on RX
for now i have found a dirty hack, when it happens i reinitialize the esp with:
Serial3.begin(9600);
WiFi.init(Serial3);
WiFi.begin(ssid, pass);
it looks like a bug in AT firmware. if you want to try to wait longer, you can set longer timeout on Serial3 with Serial3.setTimeout(2000);
(default is 1000 milliseconds)
setTimeout do not fix the issue with the at firmware
for now when it happens i reinitialize Wifi. In this situation the esp seems disconnected, i get IP Address 0.0.0.0 and 0 dBm signal
i am testing this library (1.0.1 and Espressif's AT firmware 1.7.1) with the following sketch:
i have two problems
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> DNS Fail ...ignored
esp> ERROR ...error esp ERROR: expected OK got ERROR Connection failed
esp> AT+CIPSTART=4,"TCP","www.mysite.com",80 ...sent esp> 4,CONNECT ...ignored esp> OK ...matched Connecting... esp INFO: send data on link 4 esp> AT+CIPSEND=4,64 ...sent esp> OK ...ignored
esp> > ...matched esp> Recv 64 bytes ...matched esp> ? esp> busy s... ...ignored
esp> ? esp> busy s... ...ignored
esp> ? esp> busy s... ...ignored
esp> ? esp> busy s... ...ignored
esp> ? esp> busy s... ...ignored
esp> ? esp> busy s... ...ignored
esp> ? esp> busy s... ...ignored
esp> 4,CLOSED ...processed esp INFO: closed linkId 4 esp> SEND FAIL ...matched esp ERROR: failed to send data esp INFO: send data on link 4 esp ERROR: link is not connected.
esp INFO: close link 4 esp WARN: link is not active esp INFO: free linkId 4 esp INFO: start TCP to www.mysite.com:80 on link 4 esp> AT+CIPSTART=4,"TCP","www.mysite.com",80 ...sent esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> ? esp> busy p... ...ignored
esp> 4,CONNECT ...ignored esp> OK ...matched Connecting...