Data Sheet
!
5. TCP/IP-Related AT Commands
5.2.9. AT+CIPBUFSTATUS—Checks the Status of the TCP-Send-Buffer
5.2.10. AT+CIPCHECKSEQ—Checks If a Specific Segment Was Successfully Sent
Set
Command
1. Single connection: (+CIPMUX=0)
AT+CIPBUFSTATUS
2. Multiple connections: (+CIPMUX=1)
AT+CIPBUFSTATUS=<linkID>
Response
<nextsegmentID>,<segmentIDsent>,<segmentIDsuccessfullysent>,<remainbuffer
size>,<queuenumber>
OK
Parameters
• <nextsegmentID>: the next segment ID obtained by AT+CIPSENDBUF;
• <segmentIDsent>: the ID of the TCP segment last sent;
• Only when <nextsegmentID> - <segmentIDsent> = 1, can AT+CIPBUFRESET be called to reset the
counting.
• <segmentIDsuccessfullysent>: the ID of the last successfully sent TCP segment;
• <remainbuffersize>: the remaining size of the TCP-send-buffer;
• <queuenumber>: available TCP queue number; it’s not reliable and should be used as a reference only.
Notes
This command can not be used for SSL connection.
Example
For example, in single connection, the command AT+CIPBUFSTATUS returns:
20,15,10,200,7
Description:
• 20: means that the latest segment ID is 19; so when calling AT+CIPSENDBUF the next time, the
segment ID returned is 20;
• 15: means that the TCP segment with the ID 15 is the last segment sent, but the segment may not
be successfully sent;
• 10: means that the TCP segment with the ID 10 was sent successfully;
• 200: means that the remaining size of the TCP-send-buffer is 200 bytes;
• 7: the available TCP queue number; it is not reliable and should be used as a reference only; when
the queue number is 0, no TCP data can be sent.
Set
Command
1. Single connection: (+CIPMUX=0)
AT+CIPCHECKSEQ=<segmentID>
2. multiple connections: (+CIPMUX=1)
AT+CIPCHECKSEQ=<linkID>,<segmentID>
Response
[<linkID>,]<segmentID>,<status>
OK
Espressif
! /!48 58
2017.05