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.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
You probably want to call
at.debug();
beforeCIPSTART
, 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 theCLOSED
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.