logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

ESP32 WROVER-IB - causes of overheating and USB damage

prem111 1356 8
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
Reply | New topic
  • #1 18794507
    prem111
    Level 5  
    Hello, this is the second time I have had this problem. Are the esp32 (I have a wroover-ib) failing ? The second board has been burnt within a few months. I am powering from 12v via UBEC lowering the voltage to 5.22v (from ubec output -> micro usb). I don't know what exactly is failing/burning but the symptom was that the usb input on the wroover devkit board got hot. At the moment the LED is on but the esp is not responding, it is not possible to connect to the console via uart etc....
  • ADVERTISEMENT
  • #3 18795546
    prem111
    Level 5  
    Yes, ESP32_DevKitc_V4 plugged into ESP32-LCDKit_V1.1

    The LCDKit was plugged into the microusb from the 5.2v UBEC ( as power and ground ) and the devkit itself was also plugged into the microusb from the raspberry pi (to read logs from the esp).
  • ADVERTISEMENT
  • #4 18795556
    Anonymous
    Level 1  
  • #5 18795574
    prem111
    Level 5  
    Yes, I am enclosing a photo. ESP32 WROVER-IB - causes of overheating and USB damage .
  • ADVERTISEMENT
  • #6 18795606
    Anonymous
    Level 1  
  • #7 18795632
    prem111
    Level 5  
    Ok, that would explain a lot about the possible cause. Thanks !
  • ADVERTISEMENT
  • #8 18795646
    Anonymous
    Level 1  
  • #9 18795682
    prem111
    Level 5  
    Great idea ! This is exactly what I will do. Thank you again !
Reply | New topic
Report a violation of the law

Topic summary

The discussion revolves around the overheating and potential damage of the ESP32 WROVER-IB module, specifically in the context of using it with the ESP32-DevKitC and ESP32-LCDKit. The user reports that their second board has burned out after a few months, with symptoms including a hot USB input and unresponsiveness. It is suggested that powering the ESP32-DevKitC from two different +5V sources (the ESP32-LCDKit and a Raspberry Pi) may lead to damage. A solution proposed includes creating a special USB cable that cuts off the VBUS power line to prevent further issues while still allowing for log downloads.
Summary generated by the language model.
Today's popular
ADVERTISEMENT