ME310G1/ME910G1/ML865G1 AT Commands Reference Guide
80617ST10991A Rev.4 Page 393 of 545 2020-04-15
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)
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.
In case of UDP, cause 2 indicates abnormal (local) disconnection. Cause 3 and 4 are still
possible.
(Cause 1 is obviously never possible)
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.
AT#SLASTCLOSURE=?
Test command reports the supported range for parameter <connId>
To Next Page
Loading...
Need help?
General
