-->
Page 1 of 2

tcp client with At cmd not working

PostPosted: Thu May 18, 2017 8:14 am
by Sushant Naik
I am trying to setup tcp client in Station mode, whenever i try to connect i get following in ESplorer terminal
AT+CIFSR
+CIFSR:STAIP,"192.168.1.101"
+CIFSR:STAMAC,"18:fe:34:16:c2:c3"

OK
AT+CIPMUX=1
AT+CIPSTART=0,"TCP","192.168.1.100",80
busy p...

OK
AT+CIPMUX=1
AT+CIPSTART=0,"TCP","192.168.1.100",80
busy p...

OK
AT+CIPSEND=0,7
sushant
busy p...
link is not


I have been using AI-v0.9.5.0 AT Firmware.bin, and not downloaded any custom code.
what does busy p... stand for ? how to resolve it ? why does ESPlorer does have "Send Data" in tcp server Section ?

Re: tcp client with At cmd not working

PostPosted: Sat May 20, 2017 4:34 pm
by atexit8

Re: tcp client with At cmd not working

PostPosted: Sun May 21, 2017 12:39 am
by Sushant Naik
atexit8 wrote:I found https://alselectro.wordpress.com/2015/05/13/wifi-module-esp8266-2-tcp-client-server-mode/ works for me


He demonstrated how to use ESP in server mode, i have done that. Issue is am not able to use ESP in tcp client mode.

Re: tcp client with At cmd not working

PostPosted: Sun May 21, 2017 5:51 pm
by QuickFix
What is the current mode of your ESP?

Possible mode values:
  1. Station mode (client)
  2. AP mode (host)
  3. AP + Station mode (host and client)

Query:
Code: Select allAT+CWMODE?

Set:
Code: Select allAT+CWMODE=<required mode>


To use an ESP8266 as a client, it must be set to either 1 (client only) or 3 (client and AP/host).