logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

What could be the causes of the ESP32 burning up when connected to the expansion board?

prem111 1704 15
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Reply | New topic
  • #1 18559944
    prem111
    Level 4  
    Hello, I probably burnt the esp32 wroom devkit module. Now when I switch it on the LEDs don't light up and it gets very hot until it steams. I may have made a mistake. I will describe how I connected it. The module was plugged into an expansion board designed for nodemcu - maybe this was the problem ? I attach how this expansion board looks like. I powered this from a 12v liion pack - this nodemcu expansion board supports 6-24v input.

    What could be the causes of the ESP32 burning up when connected to the expansion board? .
  • ADVERTISEMENT
  • #2 18560293
    khoam
    Level 42  
    prem111 wrote:
    The module was plugged into an expansion board intended for the nodemcu - perhaps this is where the problem was ?
    .
    This NodeMCU Base is designed for modules with ESP8266, which have slightly different meaning of some pins. When the ESP32 DevKit is inserted into the NodeMCU Base, some ESP32 pins are shorted to ground and power. This does not yet mean that the ESP32 DevKit itself is faulty. Just check it without this NodeMCU Base.
  • ADVERTISEMENT
  • #3 18560308
    prem111
    Level 4  
    Yes i checked without it, i connect the microusb alone and it doesn't fire up either, it just automatically heats up. I'll add that 2 months it was running on this nodemcu base with no problem, just today while plugging in power it went out and heated up right away.

    The most important question for me is what happened, is it a matter of this nodemcu base or could it have contributed to this, but after all, it worked for some time without a problem. It never overheated etc.

    PS. do you know of any expansion boards for esp32 available here in Poland ?
  • ADVERTISEMENT
  • #4 18560341
    khoam
    Level 42  
    prem111 wrote:
    I'll add that 2 months it was running on this nodemc base with no problems, just today while plugging in power it went out and overheated right away.
    .
    This is possible. As long as you did not drive these "critical" pins as outputs, nothing bad happened. Below for comparison the "pinology" of the ESP8266 and ESP32 modules.

    What could be the causes of the ESP32 burning up when connected to the expansion board? What could be the causes of the ESP32 burning up when connected to the expansion board? .
  • #5 18560366
    prem111
    Level 4  
    What do you mean when you write you did not drive the critical pins as outputs ? I didn't connect anything new I simply connected the package to the DC socket on this nodemc base as usual.
  • #6 18560372
    khoam
    Level 42  
    prem111 wrote:
    What do you mean by writing you did not drive the critical pins as outputs ?
    .
    That is, until the program that loaded the ESP32 did so while it was running.
  • #7 18560412
    prem111
    Level 4  
    Nothing new is likely to have happened here either, there is micropython and a few scripts, but nothing new has been added for a few days.
  • #8 18560712
    khoam
    Level 42  
    prem111 wrote:
    do you know of any expansion boards for esp32 available here in Poland ?
    .
    I have not come across NodeMCU Base solutions for ESP32 DevKit. Also, newer versions of ESP32 DevKit have more leads than 30.
  • #9 18560719
    prem111
    Level 4  
    I found one:

    keyestudio ESP32 IO Shield

    Unfortunately not available in Poland.
  • ADVERTISEMENT
  • #10 18560732
    khoam
    Level 42  
    And probably more expensive than the ESP32 DevKit itself :) For what purpose do you need such a "base board"?
  • #11 18560743
    prem111
    Level 4  
    I need to put the esp in an enclosure, so it would be convenient to sit it on "something" and plug the RF receiver (in my case xbee) under the uart. besides, I don't want to use contact boards because they are inconvenient for me.
  • #12 18560772
    khoam
    Level 42  
    And the module itself with ESP32 can only be powered by USB?
  • #13 18560794
    prem111
    Level 4  
    This may be the case.
  • #14 18560803
    khoam
    Level 42  
    You might consider buying a mini D1 ESP32 module with two-row combs. You should have no problem "attaching" the RF module.
    What could be the causes of the ESP32 burning up when connected to the expansion board? .
    Available in Poland.
  • #15 18560818
    prem111
    Level 4  
    Thanks for the hint and for the replies in this thread greetings :)
  • #16 18617037
    Anonymous
    Level 1  
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around the overheating and potential failure of an ESP32 Wroom DevKit module when connected to a NodeMCU expansion board. The user initially reported that the module was functioning well for two months but suddenly began to overheat and fail upon powering it with a 12V Li-ion pack. Responses indicate that the NodeMCU Base is designed for ESP8266 modules, which have different pin configurations, potentially causing short circuits when the ESP32 is used. Suggestions include testing the ESP32 without the expansion board and considering alternative expansion boards specifically designed for the ESP32, such as the keyestudio ESP32 IO Shield, although availability in Poland is limited. The conversation also touches on the need for a suitable base for housing the ESP32 and connecting peripherals like RF receivers.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT