Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dealing with AT+CIPSTART errors #10

Open
dbrgn opened this issue Oct 24, 2022 · 1 comment
Open

Dealing with AT+CIPSTART errors #10

dbrgn opened this issue Oct 24, 2022 · 1 comment
Labels
question Further information is requested

Comments

@dbrgn
Copy link
Contributor

dbrgn commented Oct 24, 2022

Connecting and sending data works initially:

AT+CIPSEND=1,172

OK
>
PUT /sensors/people_now_present/ HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Content-Length: 7
Host: status.crdmp.ch
User-Agent: Nixie counter

value=1

Recv 172 bytes

SEND OK
+IPD,1,518

...but after some delay the connection is closed.

1,CLOSED
WIFI GOT IP

If I try to send data from this point on, this always fails with the excellent error message "ERROR":

AT+CIPSTART=1,"TCP","94.230.210.85",80

ERROR
1,CLOSED
AT+CIPSTART=1,"TCP","94.230.210.85",80

ERROR
1,CLOSED

Any idea what the problem could be?

(Serial communication captured with a logic analyzer.)

@marius-meissner
Copy link
Member

marius-meissner commented Oct 24, 2022

Sounds like a tricky problem. Maybe a bug within ESP-AT? Which firmware version are you using?

I assume you are calling receive() from time to time? Just to make sure that the remote buffer of ESP-AT does not fill up.

Would it be possible to see what is happening at the remote webserver (TCP handshake, etc.)?

@marius-meissner marius-meissner added the question Further information is requested label Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants