UDP from ESP8266 to MegunoLink Pro
Posted: Fri Feb 05, 2016 4:53 am
I'm in the midst of developing a temperature monitor on the ESP8266 (ESP-12E) and using UDP to send data to a TimePlot on MegunoLink. The ESP8266 is a fussy chip and I have three that don't work any more. The one that I'm working with now is an ESP-12E with a breadboard adapter. I have a Dallas DS18B20 (with 3 meter cable and breadboard pins) talking to the ESP8266. Every 10 secs it sends a UDP packet to the Megunolink Pro. So far, I'm just reading the received packets with the MegunoLink Monitor panel. The IP address and UDP port of the ESP8266 are fixed (192.168.1.228:2880) so that i can send a start packet to the ESP82 from the MegunoLink.
The ESP8266 initiates with a "!Start" message from the MegunoLink Monitor panel. I will replace the Monitor with a button on the Interface panel after I get the ESP8266 program stable. I has been a few days of experimenting to get this far. I also send a "!Stop" message from the MegunoLink Monitor when I want to stop the packets from the ESP8266.
I'll post a further update if the MegunoLink and the ESP8266 remain stable over night. Up until about 2 hours ago, I could only maintain stable communication for a half hour or so. Lots of crashes on the ESP8266, including a "panic" message streaming out of the ESP into the serial monitor on the Arduino IDE.
If the two are still communicating in the morning, I'll begin a TimePlot and an Interface panel with Start and Stop buttons. One interesting unresolved question is "why do I have to send two start messages before two way communication begins". The start messages need to be about 2 secs apart.
If you are interested, post something.
Jim
The ESP8266 initiates with a "!Start" message from the MegunoLink Monitor panel. I will replace the Monitor with a button on the Interface panel after I get the ESP8266 program stable. I has been a few days of experimenting to get this far. I also send a "!Stop" message from the MegunoLink Monitor when I want to stop the packets from the ESP8266.
I'll post a further update if the MegunoLink and the ESP8266 remain stable over night. Up until about 2 hours ago, I could only maintain stable communication for a half hour or so. Lots of crashes on the ESP8266, including a "panic" message streaming out of the ESP into the serial monitor on the Arduino IDE.
If the two are still communicating in the morning, I'll begin a TimePlot and an Interface panel with Start and Stop buttons. One interesting unresolved question is "why do I have to send two start messages before two way communication begins". The start messages need to be about 2 secs apart.
If you are interested, post something.
Jim