Closed d3th3n closed 4 years ago
Thanks for your suggestion. But I don't think you quite understand the code at this point. This is event-driven code, like a state-machine. In standby mode, after
setCpuFrequencyMhz(10);
gpio_wakeup_enable((gpio_num_t)AXP202_INT, GPIO_INTR_LOW_LEVEL);
gpio_wakeup_enable ((gpio_num_t)BMA423_INT1, GPIO_INTR_HIGH_LEVEL);
esp_sleep_enable_gpio_wakeup();
is executed, the CPU goes into sleep mode and no further code is executed. Here the watch consumes about 2mA in standby. I think that is ok. Only an Interrupt from bma or pmu wakes up the CPU. The only point where I see a suggestion is that every time I turn on the watch, the wifi is turned on.
The 300mAh are caused by my own measurements and is only an information. The charge controller never charges more than 300mAh into the battery (see battery setup) and is limited by the final charge voltage of 4.2V.
I agree with you but (without a measuring device) I can see a real difference in consumption. in principle, operation should "go into pause" but the battery barely lasts 6 hours but with the modification ... it really lasts longer (test to come)
Best regards Le 30 juil. 2020 à 20:10 +0200, Dirk Broßwick notifications@github.com, a écrit :
Thanks for your suggestion. But I don't think you quite understand the code at this point. This is event-driven code, like a state-machine. In standby mode, after setCpuFrequencyMhz(10); gpio_wakeup_enable((gpio_num_t)AXP202_INT, GPIO_INTR_LOW_LEVEL); gpio_wakeup_enable ((gpio_num_t)BMA423_INT1, GPIO_INTR_HIGH_LEVEL); esp_sleep_enable_gpio_wakeup(); is executed, the CPU goes into sleep mode and no further code is executed. Here the watch consumes about 2mA in standby. I think that is ok. Only an Interrupt from bma or pmu wakes up the CPU. The only point where I see a suggestion is that every time I turn on the watch, the wifi is turned on. The 300mAh are caused by my own measurements and is only an information. The charge controller never charges more than 300mAh into the battery (see battery setup) and is limited by the final charge voltage of 4.2V. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Oh... I'm a little surprised. With "normal" use, my battery lasts about two days. Without use it takes about 3 days until the battery is empty, that includes waking up every hour with wifi for 15 seconds.
this remains true during the night (when I do not use the watch) the discharge of the battery is very low ... on the other hand, during the day the drainage of the battery is very important (hence the modification) but, can -be, that the problem is elsewhere (in one of the two "short-circuited" functions?). All this to tell you that I appreciate your project
Best regards Le 30 juil. 2020 à 20:30 +0200, Dirk Broßwick notifications@github.com, a écrit :
Oh... I'm a little surprised. With "normal" use, my battery lasts about two days. Without use it takes about 3 days until the battery is empty, that includes waking up every hour with wifi for 15 seconds. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I found several solutions to make the watch much less energy consuming: on powermgm.cpp change the function as is :
void powermgm_loop(TTGOClass *ttgo) {
}
we really have a real gain on energy consumption ... One more thing ... in the TTGO T-Watch 2020 the battery is 380mA ... not 300mA