You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, as part of my developments to get Watchy low power (and solar). sqfmi/Watchy#118
I found out that there were inconsistent power usages in the display module.
Just "touching" the connector would lead to differences in power usage from 130uA-600uA.
Also different displays seem to behave differently (V1-V2, color, ...). Agains same range 130uA-600uA.
I ended up finding that the RES# pin was the culprit, just touching that one would change the results.
RES# of the display is supposed to be left connected to HIGH.
If it is not left in that state the Dsiplay hardware will not fully enter deep sleep.
I checked that with ANY display and any watchy (I have 2), leaving this pin to 3V3 sets the power usage to 125uA.
The problem is, it can't be done on SW, since the RES pin is connected to a normal GPIO and not to a RTC GPIO.
GPIOs are left high impedance in deep sleep and therefore not driven to any value.
Solutions:
Pullup resistor of 100k-1M (I measured no current flowing in the pin at all <1uA).
Connect RES to RTC pin and leave the PIN as output + HIGH state.
The text was updated successfully, but these errors were encountered:
Hi, as part of my developments to get Watchy low power (and solar). sqfmi/Watchy#118
I found out that there were inconsistent power usages in the display module.
Just "touching" the connector would lead to differences in power usage from 130uA-600uA.
Also different displays seem to behave differently (V1-V2, color, ...). Agains same range 130uA-600uA.
I ended up finding that the RES# pin was the culprit, just touching that one would change the results.
RES# of the display is supposed to be left connected to HIGH.
If it is not left in that state the Dsiplay hardware will not fully enter deep sleep.
I checked that with ANY display and any watchy (I have 2), leaving this pin to 3V3 sets the power usage to 125uA.
The problem is, it can't be done on SW, since the RES pin is connected to a normal GPIO and not to a RTC GPIO.
GPIOs are left high impedance in deep sleep and therefore not driven to any value.
Solutions:
The text was updated successfully, but these errors were encountered: