Skip to content

Commit 5a9f504

Browse files
authored
Update Power_capabilities.md
1 parent ffa2564 commit 5a9f504

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/Power_capabilities.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ that can be accessed on the I2C bus at address 0x75. Access is possible via M5.
2222
- **Can communication with the IP5306 power controller be tested and confirmed?** Yes, with `canControl()`
2323
- **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
2424
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,
2626
and will not charge the battery. The IP5306 will shut down under this condition to minimize battery drain, unless configured not to.
2727
When the chip is shut down, it will not respond to I2C communication
2828
(for example, `getBatteryLevel()` will return -1)

0 commit comments

Comments
 (0)