I built a wireless totem keyboard using XIAO nRF52840, however, I am not sure if the lipo battery is being charged. I connected it with an Anker power bank that can tell how fast it’s charging, and it reads 0. I checked the LED and it turns on when the keyboard is on and being plugged in, but nothing otherwise. The keyboard works wirelessly so the battery should be working. Does anyone have an idea what is wrong with it?
Could it be that the lipo battery is nearly fully charged so it doesn’t charge?
Hi,
Here is some related information about charging XIAO nRF52840:
- Select charging current as 50mA or 100mA
- Considerations when using charging function
- Behavior of the red light when powered on
Hope this can help you.
1 Like
So the red charging indicator LED being on means battery is being charged. If not charging or battery is full, the red light will go off. I guess the Anker power bank shows “0” because the charging current is less than its display threshold. Usually this kind of power bank is for high power devices like tens or 100+ Watts mobile phones and computers. You can try with a dedicated Ampere meter to test the charging current.
1 Like
Hi there,
I would agree, I have a small power pak the shuts down when connected after a few seconds because the Xiao isn’t a big enough load… LOL funny if I connect a low battery to Xiao and then power it with the Power pak it works… Up until the battery is fully charged, then again it shuts off as if not connected. If i manually switch the bank ON it works for a few seconds then powers down (only using the RGB blink sketch) btw.
“The Xiao is too Efficient for some power banks” 
just sipping the juice.
YMMV
HTH
GL 
PJ 
2 Likes
yes… i will charge or run 2 devices on the battery bank that has 2 or 3 USB ports to keep it “awake”
2 Likes
Also, some power banks have a special mode for tiny current devices like earbuds. Check the user manual and you might find the descriptions, like double click the button or something to enter this mode.
1 Like
I did that but it still didn’t work
Good that it wasn’t only me encountering this problem