After update to v0.6 ESP8266 relay node problem

6 years 8 months ago #190 by cdj
After an hard reset :

AT+CIPSTART="TCP","192.168.0.10",37602"


OK
Linked
Request Node id
write: command: 3, type: 0, len: 0, sender: -1, crc:160
Send cmd:AT+CIPSEND=9

AT+CIPSEND=9

> Sending len:9
hÿÿ
SEND OK

OK
Unlink

And add node fail in timeout...

Please Log in or Create an account to join the conversation.

6 years 8 months ago - 6 years 8 months ago #191 by cdj
And now after changing my modified arduino serial buffer and switch to arduino uno normal it gives me :

SEND OK

+IPD,9:hOK
Receive: command: 3, type: 3, len: 0, sender: 0, crc: 120(394)
Command
PING response

and loop in this way....AND FINALLY NODE ADDED !!!
Thanks and sorry

Please Log in or Create an account to join the conversation.

6 years 8 months ago - 6 years 8 months ago #295 by iotfan
Similar problem here...

I´m using a Raspberry pi with EasyIoT Server image v0.6.
That works perfect with LAN and NRF24L01+ connected.
One MySensor node is successfully connected to the Raspberry pi.
Now i´m working on a connection between a ESP8266 and the Raspberry pi, without success.
I have configured SSID and credentials for my WLAN and the IP Address of the Raspberry (IoT) Server in Esp8266EasyIoTConfig.h. The Driver on the Raspberry pi is enabled and server port is 37602 on both sides.
I use the newest original sketches from your github site on an Arduino Duemilanove. In this case the temp/humidity node sketch.
Unfortunatelly the Arduino serial console says always something like

EasyIoTEsp init
nodeid:-1
hwReset
E_START
E_CWMODE
Send cmd:AT+CWMODE=1

Response timeout
E_CWMODE
Send cmd:AT+CWMODE=1

and jumps in a loop.
On server side the "Add node" function also timed out.
Pinging the node fails.

When i connect the ESP8622 with serial interface to a terminal program, every AT- command works well. I can also ping the ESP8622.

Where is my failure ?
Please help!

Please Log in or Create an account to join the conversation.

6 years 8 months ago #301 by cdj
Remember to Connect arduino gnd with esp gnd.... and try to reboot esp with a terminal opened... try to set correct arduino type in ide
The following user(s) said Thank You: iotfan

Please Log in or Create an account to join the conversation.

6 years 8 months ago #307 by EasyIoT

iotfan wrote: Similar problem here...

I´m using a Raspberry pi with EasyIoT Server image v0.6.
That works perfect with LAN and NRF24L01+ connected.
One MySensor node is successfully connected to the Raspberry pi.
Now i´m working on a connection between a ESP8266 and the Raspberry pi, without success.
I have configured SSID and credentials for my WLAN and the IP Address of the Raspberry (IoT) Server in Esp8266EasyIoTConfig.h. The Driver on the Raspberry pi is enabled and server port is 37602 on both sides.
I use the newest original sketches from your github site on an Arduino Duemilanove. In this case the temp/humidity node sketch.
Unfortunatelly the Arduino serial console says always something like

EasyIoTEsp init
nodeid:-1
hwReset
E_START
E_CWMODE
Send cmd:AT+CWMODE=1

Response timeout
E_CWMODE
Send cmd:AT+CWMODE=1

and jumps in a loop.
On server side the "Add node" function also timed out.
Pinging the node fails.

When i connect the ESP8622 with serial interface to a terminal program, every AT- command works well. I can also ping the ESP8622.

Where is my failure ?
Please help!


Timeout means that Arduino doesn't receive response to AT command from ESP. Is HW connection ESP-Arduino ok? Write simple test program (without ESP library) on Arduino and send AT command and see if you get response.
The following user(s) said Thank You: cdj, iotfan

Please Log in or Create an account to join the conversation.

6 years 8 months ago #329 by iotfan
Hi guys,

everything works fine now, i had an cabling issue (RX, TX from ESP8266 crossed to Arduino TX,RX) and not to D10, D11...
My failure, sorry for that- shame on me.

Thank you for your support and your great job here!

Please Log in or Create an account to join the conversation.

Time to create page: 0.250 seconds