<![CDATA[Unexpected Vbus readings for M5StickC-Plus]]>I came across a mystery (well, at least a mystery to me) while porting some code to the M5Unified API. In trying to see if the USB power was unplugged, I came across the undocumented M5.Power.getVBUSVoltage() method. In following the source code all they way down, I can see that it's reading the VBus voltage from the AXP192 and then scaling it to return a value in millivolts.

I expected to be able to compare that result against 0 to decide if the USB cable was plugged in. When it is plugged in, I get readings a little above 5000 mV. However, when the cable is unplugged, I get readings around 830 mV. That's with the internal battery nearly fully charged. I don't know if the unplugged reading changes with the internal battery charge or with the M5StickC-Plus workload or whatever.

As a workaround, I'm comparing against 2000 mV instead of 0 mV to decide if the device is unplugged.

Where do those 830 mV come from?

]]>https://community.m5stack.com/topic/7640/unexpected-vbus-readings-for-m5stickc-plusRSS for NodeWed, 29 Apr 2026 04:12:59 GMTWed, 25 Jun 2025 18:56:19 GMT60<![CDATA[Reply to Unexpected Vbus readings for M5StickC-Plus on Thu, 03 Jul 2025 01:09:52 GMT]]>@ajb2k3 Thanks for the reply. Maybe I'm misunderstanding what the Vbus is supposed to be. I thought it was the power coming in from the USB port. Even if there is a trickle of stuff draining the battery, there shouldn't be any input from USB. I suppose something is just leaking over somehow.

]]>https://community.m5stack.com/post/29372https://community.m5stack.com/post/29372Thu, 03 Jul 2025 01:09:52 GMT<![CDATA[Reply to Unexpected Vbus readings for M5StickC-Plus on Fri, 27 Jun 2025 04:27:25 GMT]]>@wjcarpenter Standby voltage. the stick doesn't truly power off and there is always a small voltage present in the stick which is why the battery always runs out.
The voltage increasing with a cable plugged in is normal and thank you for pointing out this function.

]]>https://community.m5stack.com/post/29344https://community.m5stack.com/post/29344Fri, 27 Jun 2025 04:27:25 GMT<![CDATA[Reply to Unexpected Vbus readings for M5StickC-Plus on Wed, 25 Jun 2025 19:02:43 GMT]]>Perhaps I should mention what I was doing before porting to the M5Unified API. I was using the M5.Axp API to read the input power status register and decoding it. That told me directly what I wanted to know, but it doesn't seem to be available in the current iteration of the M5Unified API.

]]>https://community.m5stack.com/post/29334https://community.m5stack.com/post/29334Wed, 25 Jun 2025 19:02:43 GMT