AT command does not respond after high-frequency communication （firmware ：ESP32-C3-MINI-1-AT-V3.2.0.0 ）

[matlam1989]

mcu send(Message cycle from 50ms to 100ms) :

15:58:53.087 AT+CIPRECVDATA=0,64
AT+CIPSEND=0,27
~hg%娴Q***駏���*CSU�*謁
15:58:54.156 ?
15:58:55.159 ?
15:58:56.162 ?
15:58:57.171 AT+CIPRECVDATA=0,64
15:58:58.175 ?
15:58:59.178 ?
15:59:00.181 ?
15:59:01.185 AT+CIPRECVLEN?
15:59:02.188 ?

Esp32c3 respond ：

OK

>
Recv 27 bytes
15:58:53.164 
+IPD,0,27
16:00:05.900 0,CLOSED

SEND FAIL

The Esp32c3 module does not respond to AT commands for 3 minutes continuously，finally “SEND FAIL” and Communication restored to normal.

more log:

mcu send

16:31:13.663 AT+CIPRECVDATA=0,108
AT+CIPSEND=0,27
~hg%娴Q******耥���*CSU�*��
16:31:13.687 AT+CIPRECVDATA=0,64
16:31:13.782 AT+CIPSEND=0,27
~hg%娴Q******耦���*CSU�*kf
AT+CIPRECVLEN?
16:31:13.866 AT+CIPSEND=0,27
~hg%娴Q******耧���*CSU�*LJ
16:31:13.968 AT+CIPSEND=0,27
~hg%娴Q******耩���*CSU�*�5
16:31:14.045 AT+CIPRECVDATA=0,108
16:31:14.073 AT+CIPSEND=0,27
~hg%娴Q******耨���*CSU�*��
16:31:14.174 AT+CIPSEND=0,27
~hg%娴Q*****耱���*CSU�*宮
16:31:14.291 AT+CIPRECVDATA=0,64
AT+CIPSEND=0,27
~hg%娴Q******耋���*CSU�*獳
AT+CIPRECVLEN?
16:31:14.377 AT+CIPSEND=0,27
~hg%娴Q******耵���*CSU�*^�
16:31:15.455 ?
16:31:16.458 ?
16:31:17.461 ?
16:31:18.471 AT+CIPRECVDATA=0,64
16:31:19.474 ?
16:31:20.477 ?
16:31:21.480 ?
16:31:22.484 AT+CIPRECVLEN?
16:31:23.487 ?
16:31:24.490 ?
16:31:25.493 ?
16:31:26.497 AT+CIPSEND=0,27
16:31:27.500 ?
16:31:28.503 ?
16:31:29.506 ?
16:31:30.515 AT+CIPRECVLEN?
16:31:31.518 ?
16:31:32.521 ?
16:31:33.524 ?
16:31:34.528 AT+CIPSEND=0,27
16:31:35.531 ?
16:31:36.533 ?
16:31:37.537 ?
16:31:38.545 AT+CIPRECVLEN?
16:31:39.549 ?
16:31:40.552 ?
16:31:41.555 ?
16:31:42.558 AT+CIPSEND=0,27
16:31:43.562 ?
16:31:44.564 ?
16:31:45.568 ?
16:31:46.576 AT+CIPRECVLEN?
16:31:47.580 ?
16:31:48.582 ?
16:31:49.586 ?
16:31:50.590 AT+CIPSEND=0,27
16:31:51.593 ?
16:31:52.595 ?
16:31:53.598 ?
16:31:54.607 AT+RST
16:31:55.609 ?
16:31:56.612 ?
16:31:57.615 ?
16:31:58.619 AT+RST
16:31:59.621 ?
16:32:00.624 ?
16:32:01.627 ?
16:32:02.631 AT+RST
16:32:03.634 ?
16:32:04.637 ?
16:32:05.639 ?
16:32:06.648 AT+RST
16:32:07.650 ?
16:32:08.655 ?
16:32:09.656 ?
16:32:10.660 AT+RST
16:32:11.662 ?
16:32:12.665 ?
16:32:13.669 ?
16:32:14.672 AT+RST
16:32:15.675 ?
16:32:16.678 ?
16:32:17.681 ?
16:32:18.689 AT+RST
16:32:19.693 ?
16:32:20.696 ?
16:32:21.699 ?
16:32:22.702 AT+RST
16:32:23.705 ?
16:32:24.708 ?
16:32:25.711 ?
16:32:26.714 AT+RST
16:32:27.717 ?
16:32:28.720 ?
16:32:29.723 ?
16:32:30.731 AT+RST
16:32:31.734 ?
16:32:32.737 ?
16:32:33.740 ?
16:32:34.743 AT+RST
16:32:35.746 ?
16:32:36.749 ?
16:32:37.752 ?
16:32:38.755 AT+RST
16:32:39.758 ?
16:32:40.761 ?
16:32:41.764 ?
16:32:42.772 AT+RST
16:32:43.775 ?
16:32:44.778 ?
16:32:45.781 ?
16:32:46.784 AT+RST
16:32:47.787 ?
16:32:48.790 ?
16:32:49.793 ?
16:32:50.796 AT+RST
16:32:51.799 ?
16:32:52.901 ?
16:32:54.127 ?
16:32:55.526 ?
16:32:56.529 ?
16:32:57.532 ?
16:32:59.516 ?
AT+RST
16:33:00.548 ?
16:33:00.669 ATE0
16:33:00.733 AT+CIPMUX=1
AT+CIPRECVMODE=1
AT+SYSSTORE=0
AT+CWMODE?
AT+CWSTATE?
AT+CIPAP="192.168.4.1","192.168.4.1","255.255.255.0"
AT+CIPAP?
AT+CWSAP="Mintranetix","q1234567890",3,4,1,0
16:33:01.738 ?
16:33:02.060 AT+CWSAP?
AT+CIPAP="192.168.4.1","192.168.4.1","255.255.255.0"
AT+CIPAP?
16:33:03.102 ?
AT+CIPAP="192.168.4.1","192.168.4.1","255.255.255.0"
AT+CIPAP?
AT+CWSAP="Mintranetix","q1234567890",3,4,1,0

>
Recv 27 bytes
16:31:13.063 
SEND OK
16:31:13.161 
OK

>
Recv 27 bytes

SEND OK
16:31:13.223 
+IPD,0,54
16:31:13.279 +CIPRECVDATA:54,~************�>���*IVU**咜
~************�?���*IVU**⒅
OK

OK

>
Recv 27 bytes

SEND OK
+CIPRECVLEN:0,0,0,0,0

OK
16:31:13.361 
OK

>
Recv 27 bytes

SEND OK
16:31:13.471 
OK

>
Recv 27 bytes

SEND OK
16:31:13.567 
OK

>
Recv 27 bytes

SEND OK
16:31:13.667 
+IPD,0,108
+CIPRECVDATA:108,~************餈���*IVU**釺
~************餉���*IVU**舩
~************養���*IVU**�
~************餋���*IVU**� 
OK

OK

>
Recv 27 bytes
16:31:13.699 
SEND OK

+IPD,0,27
+CIPRECVDATA:27,~************餌���*IVU**€�
OK
16:31:13.795 
OK

>
Recv 27 bytes

SEND OK
+CIPRECVLEN:0,0,0,0,0

OK
16:31:13.875 
OK

>
Recv 27 bytes

SEND OK
16:31:13.987 
OK

>
Recv 27 bytes

SEND OK
16:31:14.051 
+IPD,0,108
+CIPRECVDATA:108,~************餎���*IVU**Y�
~************餏���*IVU**0�
~************餑���*IVU**��
~************餒���*IVU**�=
OK

OK

>
Recv 27 bytes

SEND OK
16:31:14.174 
OK

>
Recv 27 bytes

SEND OK
16:31:14.296 
+IPD,0,54
+CIPRECVDATA:54,~************餓���*IVU**��
~************餔���*IVU**卐
OK

OK

>
Recv 27 bytes

SEND OK
+CIPRECVLEN:0,0,0,0,0

OK
16:31:14.392 
OK

>
Recv 27 bytes
16:31:14.456 
+IPD,0,54
16:32:51.911 +STA_DISCONNECTED:"68:67:25:e7:5d:4c"
16:32:53.095 +STA_CONNECTED:"68:67:25:e7:5d:4c"
+DIST_STA_IP:"68:67:25:e7:5d:4c","192.168.4.2"
16:32:53.127 +STA_DISCONNECTED:"68:67:25:e7:5d:4c"
16:32:54.535 +STA_CONNECTED:"68:67:25:e7:5d:4c"
+DIST_STA_IP:"68:67:25:e7:5d:4c","192.168.4.2"
16:32:58.455 0,CLOSED

SEND FAIL
16:32:58.503 0,CONNECT

+IPD,0,27
16:32:59.543 
ERROR

OK
+STA_DISCONNECTED:"68:67:25:e7:5d:4c"
16:33:00.711 
ready
ATE0

OK

OK

OK

OK
+CWMODE:2

OK
+CWSTATE:0,""

OK
16:33:00.742 
OK
+CIPAP:ip:"192.168.4.1"
+CIPAP:gateway:"192.168.4.1"
+CIPAP:netmask:"255.255.255.0"

OK

[ustccw]

@matlam1989 From the information you provided, it is possible that the transmitted TCP data did not receive a TCP ACK from the remote host, causing the TCP window to fill up and thus blocking the AT command port.
In this situation, you can use the AT+CIPTCPOPT command to configure a send timeout to close the TCP connection prematurely.
As for why the transmitted TCP data did not receive a TCP ACK from the remote host, further analysis would require providing TCP packet captures.

[matlam1989]

thank you