ESP8266 Developer Zone

Re: missing send callback

2015-12-04T11:30:13+08:00

Hi,

If the network environment is not well, the TCP packet will fail to send, then it will retry several times to send the TCP packets. You got no callback means it is still retrying.
You can use "espconn_set_opt" and "espconn_set_keepalive" to enable the TCP keep alive function. It will keep detecting whether the TCP connection broke or not.

Code:

uint32_t keeplive; 

espconn_set_opt(pesp_conn, ESPCONN_KEEPALIVE); // enable TCP keep alive

//set keepalive: 75s = 60 + 5*3 
keeplive = 60; 
espconn_set_keepalive(pesp_conn, ESPCONN_KEEPIDLE, &keeplive); 
keeplive = 5; 
espconn_set_keepalive(pesp_conn, ESPCONN_KEEPINTVL, &keeplive); 
keeplive = 3; //try times 
espconn_set_keepalive(pesp_conn, ESPCONN_KEEPCNT, &keeplive);

It means that ESP8266 will check whether the TCP connection broke or not every 60s, and if the first detection gets no response, it will retry the detection 3 times with 5s interval.

espconn_regist_time: when ESP8266 runs as TCP server, it will disconnect to the TCP client that does not actively (does not communicate with ESP8266 till timeout which is 9~10 seconds by default). If you set it to be 0, ESP8266 will never disconnect to the TCP client which is not actively. We do not suggest that.

Statistics: Posted by ESP_Faye — Fri Dec 04, 2015 11:30 am

Re: missing send callback

2015-12-03T22:50:59+08:00

Thanks for your fast answer.
With ESPCONN_MAXNUM was only for testing. My problem, that the program never gets a callback, neither a disconnect callback.

I've found
espconn_regist_time
What exactly does this function set? Should I set it to 0?
I send every 1 second a frame, is this not enough?

Which debugging is possible?
I send now a Keep-Alive paket from the Smartphone every second. It looks better, but why?

Statistics: Posted by Bummibaer — Thu Dec 03, 2015 10:50 pm

Re: missing send callback

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

Hi,

If the network environment is not well, the TCP packet will fail to send, then it will retry several times to send the TCP packets.

ESP8266 can hold 8 TCP packets (or 2920 bytes) waiting for sending (or retry sending) at most. "ESPCONN_MAXNUM" means that this limitation is met, you have already got 8 TCP packets waiting for sending.

So you need to wait till the previous packets sent successfully, or use espconn_set_keepalive to shorter the time of detecting whether the TCP connection broke.

Statistics: Posted by ESP_Faye — Thu Dec 03, 2015 10:20 am

missing send callback

2015-12-02T21:48:10+08:00

Hi,
I want to send 23 bytes every second to an android device.
My Server Init :

Code:

  serverConn.type = ESPCONN_TCP;
  serverConn.state = ESPCONN_NONE;
  serverTcp.local_port = port;
  serverConn.proto.tcp = &serverTcp;

   rc = espconn_set_opt (conn, ESPCONN_KEEPALIVE  | ESPCONN_COPY | ESPCONN_NODELAY); // enable write buffer
  rc = espconn_regist_write_finish (conn, user_tcp_write_finish); // register write finish callback
   rc = espconn_regist_sentcb (conn, serverSentCb);

The Sequence of tx is:

Code:

send_buf(...)
   if ( ready_tosend) {
       espconn_send(...)
       ready_tosend = false;
   }
}
user_tcp_write_finish() {
}
serverSentCb() {
   ready_tosend = true;
}

The problem after ~10 sends, I don't get any serverSentCb() , it's stuck.
If I send again anyway, I get ESPCONN_MAXNUM, and it's also stays.

Is there a way to debug this?

Please help

I'm using esp_iot_sdk_v1.5.0_15_11_27

Statistics: Posted by Bummibaer — Wed Dec 02, 2015 9:48 pm