ESP32 S3 vs ESP32 WROOM Power Consumption Issue
Posted: Tue Apr 25, 2023 2:56 am
Hi,
We noticed that our PCB design using the latest ESP32 S3 module draws significantly more current than our older PCB that used the ESP32 WROOM module. The datasheet claims that the ESP32 S3 module draws significantly less current than its predecessors but from using a bench top power supply and seeing the current draws using identical sketches between old and new PCB's, our old PCB's draw an average of 55mA running without anything going on besides advertising itself to nearby peripherals while the same firmware running on our new PCB's draw an average of 110mA. When connected through BLE, the old PCB and the new PCB would send IMU data, which would spike the current consumption to 85mA and 125mA on both old and new PCB's, respectively. Note that we're not testing deep sleep here, but we're testing the active states on the PCB's.
As another test, we monitored the TinyS3 dev kit, ESP32 S3 Dev-Kit-C1, and ESP32 Node MCU dev kit to see if maybe our PCB's were flawed in design. We found that our ESP32 Node MCU Dev Kit with the WROOM module drew the same amount of current on average as our old PCB's with the ESP32 WROOM and saw the same results when comparing either TinyS3 dev kit or ESP32 S3 Dev-Kit-C1 with our new PCB's with the new ESP32 S3 module. Do any of you know what could be the underlying issue with why our latest PCB's containing the ESP32 S3 module are drawing significantly more current (and sucking the battery life of our PCB's when connected via LiPo)?
References
ESP32-S3 Datasheet: https://www.espressif.com/sites/default ... eet_en.pdf
ESP32 WROOM Datasheet: https://www.espressif.com/sites/default ... eet_en.pdf
We noticed that our PCB design using the latest ESP32 S3 module draws significantly more current than our older PCB that used the ESP32 WROOM module. The datasheet claims that the ESP32 S3 module draws significantly less current than its predecessors but from using a bench top power supply and seeing the current draws using identical sketches between old and new PCB's, our old PCB's draw an average of 55mA running without anything going on besides advertising itself to nearby peripherals while the same firmware running on our new PCB's draw an average of 110mA. When connected through BLE, the old PCB and the new PCB would send IMU data, which would spike the current consumption to 85mA and 125mA on both old and new PCB's, respectively. Note that we're not testing deep sleep here, but we're testing the active states on the PCB's.
As another test, we monitored the TinyS3 dev kit, ESP32 S3 Dev-Kit-C1, and ESP32 Node MCU dev kit to see if maybe our PCB's were flawed in design. We found that our ESP32 Node MCU Dev Kit with the WROOM module drew the same amount of current on average as our old PCB's with the ESP32 WROOM and saw the same results when comparing either TinyS3 dev kit or ESP32 S3 Dev-Kit-C1 with our new PCB's with the new ESP32 S3 module. Do any of you know what could be the underlying issue with why our latest PCB's containing the ESP32 S3 module are drawing significantly more current (and sucking the battery life of our PCB's when connected via LiPo)?
References
ESP32-S3 Datasheet: https://www.espressif.com/sites/default ... eet_en.pdf
ESP32 WROOM Datasheet: https://www.espressif.com/sites/default ... eet_en.pdf