RE: nRF9160 TCP connect errno -116

DavidKaplan — Mon, 21 Jun 2021 07:05:08 GMT

Shalom!

This morning we found my problem. I was checking the errno after calling the blocking_connect() function even when the err returned from connect() was zero therefore I was closing the socket. Now the modem seems to re-connect to our TCP server.

Thank you very much

David

//-----------------------------------------------------------------------------
// connect_to_cloud
//  Description
//    Tries to connect to the Cloud
//  Parameters
//  Returns
//   ami_socket_connect_result
//-----------------------------------------------------------------------------
static int connect_to_cloud(void)
{
  atomic_set(&disconnect_requested, 0);

  struct sockaddr    local_addr;
  int                err;
  char               sIPPort[24];

  sprintf(sIPPort,"%u.%u.%u.%u:%u",
      cur_server.server_ip.bytes[MSB_HI_BYTE],
      cur_server.server_ip.bytes[MSB_LO_BYTE],
      cur_server.server_ip.bytes[LSB_HI_BYTE],
      cur_server.server_ip.bytes[LSB_LO_BYTE],
      cur_server.server_port.word
   );
  //---------------------------------------------------------------------------
  // Parse the IP:Port string
  //---------------------------------------------------------------------------
  if (!net_ipaddr_parse((const char *)sIPPort,strlen(sIPPort),&local_addr)){
    d_printf(LINE_INFO,kDbg_Error|kDbg_General,"ServerIP:PortParsingErr");
    return AMI_SOCKET_CONNECT_RES_ERR_NOT_INITD;
  }
  //---------------------------------------------------------------------------
  // Close socket if opened
  //---------------------------------------------------------------------------
  if (app_socket_fd>=0){
    close(app_socket_fd);
  }
  //---------------------------------------------------------------------------
  // Create a TCP socket
  //---------------------------------------------------------------------------
  app_socket_fd = socket(AF_INET,SOCK_STREAM,IPPROTO_TCP);
  d_printf(LINE_INFO,kDbg_Info|kDbg_General,"SocketFD:%d",app_socket_fd);
  //---------------------------------------------------------------------------
  // Set socket timeout
  //---------------------------------------------------------------------------
  err = socket_timeout_set(app_socket_fd,SOCK_STREAM);
  if (err) {
    d_printf(LINE_INFO,kDbg_Info|kDbg_General,"SetSockTimeoutErr:%d", errno);
    return err;
  }
  //---------------------------------------------------------------------------
  // Connect
  //---------------------------------------------------------------------------
  err = blocking_connect(app_socket_fd, (struct sockaddr *)&local_addr,sizeof(struct sockaddr_in));
  if (errno && err<0){
    err = errno;
    d_printf(LINE_INFO,kDbg_Info|kDbg_General,"ConnectionErr:%d %s",errno,sIPPort);
  }else
    d_printf(LINE_INFO,kDbg_Info|kDbg_General,"Connected:%s",sIPPort);
  return err;
} // connect_to_cloud

RE: nRF9160 TCP connect errno -116

Hakon — Fri, 18 Jun 2021 11:54:48 GMT

Hello,

have you checked the server side for any issues? Have you made sure that the connection isn't being rejected by the server?

RE: nRF9160 TCP connect errno -116

DavidKaplan — Thu, 17 Jun 2021 04:46:24 GMT

Shalom!

I had another bug opened and I posted this morning's testing there by mistake so please see that thread with debug information.

I am very sorry about the mixup, David

https://devzone.nordicsemi.com/f/nordic-q-a/76060/lte-m-always-connected/314587#314587

RE: nRF9160 TCP connect errno -116

DavidKaplan — Wed, 16 Jun 2021 12:40:55 GMT

Shalom!

I am now testing my re-connection algorithm in case that our TCP server is restarted or the network does down and etc.

The same thing happens when I try to reconnect to the same IP.

It must be something that I forgot to do.

6-16 15:36 16/06/2021 12:36:48 | 16/06/2021 15:37:06[ami_socket.c: 342] SocketFD:1
6-16 15:36 16/06/2021 12:36:48 | 16/06/2021 15:37:06[ami_socket.c: 286] SocketTimeout:30s
6-16 15:36 16/06/2021 12:36:48 | 16/06/2021 15:37:06[ami_main.c: 359] RRC mode:Connected
6-16 15:36 16/06/2021 12:36:48 | 16/06/2021 15:37:06[ami_socket.c: 357] ConnectionErr:116 192.117.103.217:8808

Thanks David