ESP8266 Community Forum

- Mon Aug 03, 2015 1:03 pm #24909 Hi!

I have two ESP8266-ESP01 and both are showing the following problem. One is used as temperature sensor and the other one is running the sample web server sketch.

After powering up the ESP connects to the WiFi network and every minute a new temperature is posted to ThingSpeak. But after a few minutes the ESP stops working. Temperature values are no longer posted and the red LED starts to flicker very fast. The LED on my power supply also flickers and the ESP gets very hot.

The same with the one that is running the web server. Suddenly the server is not responding any longer and the red LED flickers. If I reset the ESP it is working again for some minutes.

The both ESPs are powered up by different circuits. The first one is powered up by a YwRobot bread board power supply adapter (http://www.petervis.com/Raspberry_PI/Breadboard_Power_Supply/YwRobot_Breadboard_Power_Supply.html) connected to 9V/1A power supply and the other one by an AMS1117 circuit (self designed), connected to a 5V/1,5A USB charger.

If I constandly ping the boards I always get something like this:

Code: Select all Answer from 192.168.1.200: Bytes=32 Zeit=3ms TTL=255
Answer from 192.168.1.200: Bytes=32 Zeit=3ms TTL=255
Answer from 192.168.1.200: Bytes=32 Zeit=4ms TTL=255
Answer from 192.168.1.2: Target host unreachable.
Answer from 192.168.1.2: Target host unreachable.
Answer from 192.168.1.200: Bytes=32 Zeit=3ms TTL=255
Answer from 192.168.1.200: Bytes=32 Zeit=13ms TTL=255
Answer from 192.168.1.200: Bytes=32 Zeit=24ms TTL=255
Answer from 192.168.1.200: Bytes=32 Zeit=14ms TTL=255
Answer from 192.168.1.200: Bytes=32 Zeit=2ms TTL=255
Answer from 192.168.1.200: Bytes=32 Zeit=152ms TTL=255
Answer from 192.168.1.2: Target host unreachable.
Answer from 192.168.1.2: Target host unreachable.
Answer from 192.168.1.2: Target host unreachable.
Answer from 192.168.1.2: Target host unreachable.
Answer from 192.168.1.2: Target host unreachable.
Answer from 192.168.1.200: Bytes=32 Zeit=80ms TTL=255
Answer from 192.168.1.200: Bytes=32 Zeit=15ms TTL=255

And if I connect the boards to my programmer every few seconds I get messages like this one:

Code: Select allwdt reset
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
~ld

ets Jan  8 2013,rst cause:4, boot mode:(3,7)


And sometimes this:

Code: Select allConnecting to TriTraTrullala

Exception (0):
epc1=0x4020fcc3 epc2=0x00000000 epc3=0x00000000 excvaddr=0x3ffeb890 depc=0x00000000

ctx: sys
sp: 3fffa198 end: 3fffffb0 offset: 01a0

>>>stack>>>
3fffa338:  40102183 00000002 00000000 00000001 
3fffa348:  fbf8ffff 04000002 3feffe00 00000100 
[...]


O.O

- Mon Aug 03, 2015 3:47 pm #24928 I've run my ESP-01 test board with a self built AMS1117 3.3v reg for almost 8 months, without any problems. I've had an ESP-01 running for a week or more, nonstop, without it failing.

The red LED on the ESP-01 is simply across the 3.3v power with a resistor. From your description of the behaviour, especially the fact that the 'upstream' power supply LED is also flickering... you likely have a problem with power somewhere. Maybe not both systems, but if one power system damages the ESP-01 and you move them around... maybe both ESPs are now damaged.

Take voltage measurements, hang an oscilloscope across the power in, and try to observe what's happening when the ESPs start failing.

- Tue Aug 04, 2015 2:05 am #24968

...Take voltage measurements, hang an oscilloscope across the power in, and try to observe what's happening when the ESPs start failing.

I have no oscilloscope.
But I'll try to measure the voltage/current with my multimeter.
But it's odd that it works for a few minutes (meanwhile the ESP is getting hotter and hotter, I guess) and then the ESP reaches this unstable condition.

- Tue Aug 04, 2015 2:39 pm #25026 FYI... I am using this power circuit.... https://pl.vc/n7el