I am using the AT#SSENDEXT command to send data to a TCP socket, and AT#SRECV to receive data from the socket. The problem is, that i sometimes losing the data from the socket, when it closes.
Is there some way to avoid losing the data when the socket closes?
I have hidden the port and ip addess in this example
How do you close the socket, and how do you know/observe data loss?
Normal
0
21
false
false
false
DA
X-NONE
X-NONE
MicrosoftInternetExplorer4
If I don´t
get the data out within about one second get a NO CARRIER and then the socket
closes. Else i close it with an AT#SH=1. I would like to let the socket stay
open until I close it.
The socket closes because the server application finishes the connections I suppose, check there what is happening. If both parties take no closing action then the socket should stay opened indefinitely, theoretically.
We use cookies to enhance your browsing experience and help us improve our websites. To improve our website, we carefully select third parties that use cookies to allow us to serve specific content and achieve the purposes set out in our cookie policy. For more information on how to make adjustments through your browser to the cookies being used on your device, please click Find Out More link. By closing this banner or continuing to browse our website, you agree to our use of such cookies. FIND OUT MORE
I am using the AT#SSENDEXT command to send data to a TCP socket, and AT#SRECV to receive data from the socket. The problem is, that i sometimes losing the data from the socket, when it closes.
Is there some way to avoid losing the data when the socket closes?
The setup is:
I have hidden the port and ip addess in this example
How do you close the socket, and how do you know/observe data loss?
Normal
0
21
false
false
false
DA
X-NONE
X-NONE
MicrosoftInternetExplorer4
If I don´t
get the data out within about one second get a NO CARRIER and then the socket
closes. Else i close it with an AT#SH=1. I would like to let the socket stay
open until I close it.
The socket closes because the server application finishes the connections I suppose, check there what is happening. If both parties take no closing action then the socket should stay opened indefinitely, theoretically.