M5Paper EPD power consumption
felmue last edited by felmue
today I did a charging experiment with a fully depleted M5Paper battery. After about 2 hours the charger IC switched from charging to standby (according to the two LEDs I've soldered to the corresponding charger IC outputs).
I used a multimeter (connected directly to the battery) to measure the battery voltage. The voltage from the internal ADC, read via
M5.getBatteryVoltage(), was about 5% higher than the voltage read by the multimeter for voltages below 4.2V. Above that the two values were pretty close. The reason for that is the voltage divider (3k / 11k) which when fed with 4.2V produces about 3.3V to the ADC input which is about the maximum a GPIO can take.
The highest voltage I've seen on the multimeter was 4.31V before the charging stopped. After which the voltage dropped back to 4.25V. I think that means the charger IC actually is setup for a 4.35V battery, but for some reason doesn't go all the way up to 4.35V.
Update: a possible reason is explained in the datasheet (Google translated):
_______________Charge termination voltage setting The default full termination voltage V FLOAT set inside the chip is approximately 4.35V, but due to the large charging current, the internal resistance of the battery and the line Loss will cause the actual full-charge termination voltage to be lower than this value, resulting in battery failure The law is full enough. SLM6635 by an external resistor RPV to increase V FLOAT of Voltage, used to compensate various losses, or to satisfy different applications Special requirements for voltage.The compensation voltage can be calculated by the following formula:
Delta V = I bat (Standby mode) * RPV
If there is no need to compensate the V FLOAT voltage, it is recommended that RPV be set to 1kΩ.
I did play around more with power down states and I managed to get a light sleep mode with fast wakeup from touch at around ~9mA.
I tried to get the touch into sleep mode by applying the steps outlined in the GT911 programming guide but I don't see any reduction in power consumption.
The steps are:
- switch ESP32 interrupt GPIO from input to output and set it low
- issue command 0x05 to address 0x8040
is there anything else that needs to be done? I'd appreciate your insight on that.
Thank you very much in advance.
mikeluan last edited by
months on a battery charge"
registered a new account for replying this.. not currently a M5Paper owner but will buy one soon!
I happened to be involved in a ESP + 8951 epaper project months ago, the target is months on battery charge (3xAAA battery).
Main env is done using arduino, and scriptable via Lua. UI is rendered on server, send down to the device during idle & stitched with Lua (it's a calendar kind of device).
repo is @ https://github.com/luan007/em_playbook
hope some code / impl provides some reference ..
I just discovered that the voltage divider used to feed the battery voltage into the ADC uses different values from what's listed in the M5Paper schematic.
- M5Paper schematics: 3 kOhm and 11 kOhm -> factor: 0.78571428571
- found in my M5Paper: 10 kOhm and 10 kOhm -> factor: 0.5
With the actual values the modified SCALE factor (0.785.. -> 0.5) found in the library also makes more sense. It compensates the voltage divider.
BTW: when you feed 4.2 V into the original 3 kOhm / 11 kOhm voltage divider you get exactly 3.3 V. So I guess initially M5Paper was designed / planned to use a 4.2 V battery.
I think I found the reason for why the touch IC (GT911) did not react when I tried to put it into sleep mode. The procedure asks for the ESP32 GPIO used for the touch interrupt to change to an output and then be driven low by the ESP32. Unfortunately GPIO36 is used for the touch interrupt and that is one of the few GPIOs which can only be used as input. So without hardware modification I don't see a way to put the touch IC into sleep mode. Or am I missing something?
fonix232 last edited by
@felmue that definitely sounds like a massive design issue - I wonder, maybe that's why the M5EPD library doesn't have any touchscreen power-off calls?
There was also a post on the M5Stack twitter recently, showing a blurred out image of upcoming devices, with a device eerily similar to the M5Paper taking up a large chunk of the photo: https://twitter.com/M5Stack/status/1357559621389479940/photo/1
I wonder if the design team realised these small issues and made a new board that is more fit for general usage purposes. It happened with the M5Cores (the Basic model had no PSRAM and the first units only had 4MB storage, which later got expanded to 16MB, then the Grey kit came with an MPU, then the Fire kit also included a microphone and PSRAM, among other changes), though the speed is much faster - I think there was almost a year between the Basic and Grey M5Cores, whereas the M5Paper was only recently released.
It does feel like a slap in the face for us who already bought multiple M5Paper units though - we've received a device that has a handful of obvious faulty design choices, and now we have to buy the new, updated model to get functionality that should've been working in the first iteration. Don't get me wrong, I'm happy for the updated design, I just hope there will be some discount for those who've already got units on their hands.
Joonas last edited by
You mention that you got the touch wakeup working. Could you share how you managed to do this?
I have searched and tried everything. I have had no luck with the touch wakeup. Currently my Homekit panel runs for about 5 hours without any sleep setup. This is just too low. I only need to use it couple of times a day and most of the time it should be on sleep.
felmue last edited by felmue
I went ahead and modified my M5Paper so it can put the touch IC (GT911) into sleep mode. By doing so the current (measured at the battery) drops about 7.6 mA.
With WiFi off, EDP power off, ESP32 in deep sleep and touch in sleep mode the overall current is about 1.6 mA.
Note: since putting touch into sleep mode requires touch INT to be driven low by ESP32, touching the screen can no longer be used to wake up M5Paper.
bricox last edited by bricox
Indeed GPIO36 is only input.
So I looked for another GPIO used only as input to reverse the 2 GPIO on the pcb.
I found the GPIO27 which tells ESP32 that the IT8951 is ready for a SPI dialogue
#define M5EPD_BUSY_PIN 27 (M5EPD.h)
EPD.begin(M5EPD_SCK_PIN, M5EPD_MOSI_PIN, M5EPD_MISO_PIN, M5EPD_CS_PIN, M5EPD_BUSY_PIN); (M5EPD.cpp)
m5epd_err_t M5EPD_Driver::begin(int8_t sck, int8_t mosi, int8_t miso, int8_t cs, int8_t busy, int8_t rst)
_pin_busy = busy;
On my pcb, the resistance R87 is absent (unwelded)
All you have to do is reverse the 5 and 16 tabs on the ESP32.
I scraped the varnish and then scanned the pcb.
You have to cut the 2 tracks between the 2 pins of the esp32 and the 2 vias.
then solder 2 thin wires.
very elegant solution. Thank you for sharing.
I opted to leave GPIO36 as is and connected GPIO19 (from port C) in parallel which I can then set to output if I want to use touch sleep mode. (Yes, I loose port C, but it made the soldering a bit easier. Only one additional wire from a pin on port C to the unpopulated R87 pad.)
I did a summary of the 3 ports A, B and C
You made a good choice using GPIO19.
Indeed, welding work is simplified.
Do you share your source code?
Do you share your source code?
Sure, you can find my touch sleep mode test sketch here.
It's a extended version of the TOUCH example which uses the left/up button to set touch into normal mode and right/down button to set into sleep mode.
To fully understand the GT911 controller, download these 2 pdf
Several developments are desirable :
- read position under interrupt and not in polling mode [GT911::update()]
- Exploit more all modes
- Check if the "green mode" (3.3mA) automatically change after 1 second of inactivity
- Generate a sound when you touch it
List of 21 other GT911 drivers :
including one in cpp:
fonix232 last edited by
@bricox based on the documentation, it should be possible to set the touch panel in a gesture recognising mode - would be nice to be able to offload that from the ESP32, alongside the interrupt-instead-of-poll change. This would certainly improve battery life.
@bricox - thank you for the links. I appreciate it. I already had the programming guide, but not the datasheet.
@fonix232 - so far I have not tried the gesture mode.
I am curious about what you guys are going to find regarding other modes.
I have others links for the GT911 driver in cpp
With interrupt : https://github.com/nik-sharky/arduino-goodix/blob/master/Goodix.cpp
No interrupt but handles 5 fingers : https://github.com/caiannello/ER-TFTM0784-1/blob/master/src/touch.cpp
We’ll have to adapt these source codes.
Sorry, i'm not a specialist for interrupts of Arduino framework....I am more familiar with the HAL framework of the STM32.
Thank you for these sustained sharing
a little bit of electronics (because no present in official doc) :
The PFL with C1, C2, C3, C4 R1 and C5:
Remark : pin 7&8 are "shield"
Find 1 output, to put low the INT signal of GT911, have another way possible ....
In the ESP pdf, I found this :
For reuse these pins, an article : https://www.instructables.com/ESP8266-Using-GPIO0-GPIO2-as-inputs/
I think that, in the M5paper, we can use GPIO0 as output.
What you think about ?
in M5Paper GPIO0 (together with ESP32_EN) already is connected to the boot / download mechanism which is controlled by CP_RTS and CP_DTR from the USB chip. ESP32_EN is also connected to the touch reset line which together with the touch INT line determine which I2C address the touch IC is going to use.
If you also connect GPIO0 to the touch INT line, GPIO0 and ESP32_EN will not only determine the ESP32 boot mode but also the touch IC I2C address depending on what CP_RTS and CP_DTR are doing.
On the other hand controlling GPIO0 from code to put the touch IC into sleep mode might have a negative effect on the automatic boot / download mechanism.
I personally would leave GPIO0 alone, but in general it is correct that GPIO0 can be used as output if needed.