Issue with board rebooting (WLED)
Posted May 24, 2022, 9:33 PM UTC
309
Does your code use any timers or counters?
2
I can’t really tell from the photo but it doesn’t look to follow the wiring guide from the get started guide. Without the resistor and the capacitor you will have issues. If it is correct and you are still having issues try replacing the esp8266. https://kno.wled.ge/basics/getting-started/
2
Did you try another NodeMCU (or a WeMos)? Could be a freak fault in the board.
2
First of all you don't need to use 2*2 wire of this diameter the maximum current drawn is 1-2A And where is connected your ground wire? You don't need the yellow/green on the esp
1
The earth cable it just the colour of the cable, it’s being used as a data line. The thickness of the cable is due to it being external and running through planter exposed to water and soil
2
Oh okay sorry
1
I’m hoping someone can help me because I’m out of ideas and googling on what to do! I have this ESP8266 setup to run some outdoor LED strips with WLED, and after having some connectivity issues (which was kindly sorted out by the people in this sub Reddit), I’m now having issues with the board rebooting at random intervals. I have added a 1000uF capacitor across the input supply to the ESP and moved the power input to the LEDs directly out of the PSU. The PSU is set to exactly 5V and everything runs fine for a random amount of time (anything from minutes to hours) and then the board reboots as WLED goes back to the default setting. I’m completely out of ideas on why this is happening now and could really do with some help please!
You're going to need to hook up the micro USB port and monitor it to see why it's resetting. I've run WLED before and had no issues, but there's too many variables to know what you have going on there.
If you can set the baud rate the baud rate to 74880 you'll see the debug messages and the boot message. https://kno.wled.ge/interfaces/serial/ If it's an exception causing the reset, then you'll need to install the ESP Exception Decoder to figure out what's going awry, https://github.com/me-no-dev/EspExceptionDecoder That only works with the USB serial monitor connected, of course. Copy EVERYTHING between the two CUT points in the output and drop that into the Exception Decoder, and that'll give us a clue where it's blowing up. Raw stack traces won't do anyone any good, but that decoded output WILL help. You're the only one that can do the decode, as it requires the ELF file that's generated when you compile WLED.
Ok that’s brilliant thanks! I will try this tomorrow and hopefully catch a reboot at some point! Hopefully it’s not hours!!