You are reading a single comment by @Gordon and its replies. Click here to read the full conversation.
  • You probably want to call at.debug(); before CIPSTART, just so you can see what's being sent back a bit sooner.

    It looks to me like the CIPSEND command itself is working, but the connection has already been closed by the server - hence the CLOSED message?

    While the AT command module doesn't have an easy way to respond to just >, I don't think you have to worry. It basically always sends > so you can pretty much ignore having to wait for it and just keep sending data.

About

Avatar for Gordon @Gordon started