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
Copy file name to clipboardExpand all lines: docs/Power_capabilities.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ that can be accessed on the I2C bus at address 0x75. Access is possible via M5.
22
22
-**Can communication with the IP5306 power controller be tested and confirmed?** Yes, with `canControl()`
23
23
-**Where does the IP5306 power controller get its own power?** Only from either the battery or the USB port. The 5V connection on the M5Stack
24
24
Core/Basic/Gray controller is not a power *source* for the IP5306 chip and is considered downstream from the chip (i.e. the *output*). If the M5Stack controller
25
-
is being powered through the 5V pin (for example, through a base or some other accessory), this power is not an *input* to the IP5306 chip,
25
+
is being powered through the 5V connection other than the USB port (for example, through a base or some other accessory), this power is not an *input* to the IP5306 chip,
26
26
and will not charge the battery. The IP5306 will shut down under this condition to minimize battery drain, unless configured not to.
27
27
When the chip is shut down, it will not respond to I2C communication
0 commit comments