To Next Page

To Previous Page

Telit LE910 V2 Series AT Commands

80446ST10707A Rev. 0– 2015-11-03

Mod. 0808 2011-07 Rev.2

<cause> - socket disconnection cause:

0 – not available(socket has not yet been closed)

1.- remote host TCP connection close due to FIN/END: normal remote

disconnection decided by the remote application

2 -.remote host TCP connection close due to RST, all others cases in

which the socket is aborted without indication from peer (for instance

because peer doesn't send ack after maximum number of

retransmissions/peer is no more alive).

All these cases include all the "FATAL" errors after recv or send on the

TCP socket(named as different from EWOULDBLOCK)

3.- socket inactivity timeout

4.- network deactivation(PDP context deactivation

from network)

Note: any time socket is re-opened, last disconnection

cause is reset. Command report 0(not available).

Note: user closure cause(#SH) is not considered and

if a user closure is performed after remote disconnection,

remote disconnection cause remains saved and is not

overwritten.

Note: if more consecutive closure causes are received,

the original disconnection cause is saved.

(For instance: if a TCP FIN is received from remote

and later a TCP RST because we continue to send data,

FIN cause is saved and not overwritten)

Note: also in case of <closureType>(#SD) set to 255, if the socket has

not yet been closed by user after the escape sequence,

#SLASTCLOSURE indicates remote disconnection cause if it has been

received.

Note: in case of UDP, cause 2 indicates abnormal(local)

disconnection. Cause 3 and 4 are still possible.

(Cause 1 is obviously never possible)

Note: in case of command mode connection and remote closure with

subsequent inactivity timeout closure without

retrieval of all available data(#SRECV or SRING mode 2),

it is indicated cause 1 for both possible FIN and RST from remote.

Telit Wireless Solutions LE910 User Manual

Questions and Answers: