#Need help/guide identifying poor battery life (sweep bling no rgb, nice!nano v2)

1 messages · Page 1 of 1 (latest)

crisp axle
#

Hi there!

I bought a built Ferris Sweep bling with 110mah lipo and 2 nice!nano v2 and the battery seems to last only a day.

Before i start messing with the hardware (where i m not that confortable, that is why i bought it built in the first place), can it be a config error or anything like that?

The first thing I checked was that deep sleep mode was in fact deep sleeping as the board disappeared from the bluetooth device list.  
Tried flashing reset firmware, checked for swollen battery.  Currently trying to get a clearer portrait getting battery percentage kinda regularly with notes about usage

Here is my config: https://github.com/JulBell/zmk-config-ferris-sweep/tree/8973a2426e4738339fa6bfc57fc0eacfd9796ffa

PS: I might take a bit to answer and/or check/tests answers due to workload, sry about that

crisp axle
#

If anyone can help me/tell me what is missing in my post to get some help. Or guide me to steps to troubleshoot ... I’m kinda lost here

#

some data I tried to gather

#

Trying to do the same today without the ZMK studio snippet on the build... but numbers seems to follow the same

#

Need help/guide identifying poor battery life (sweep bling no rgb, nice!nano v2)

eternal light
#

No idea if your battery is from a reputable source either. I have run into someone in this discord who was told their battery was 110mAh...but when they posted a picture, said battery was physically too small to have that capacity.
You haven't indicated where this keyboard was purchased.

crisp axle
#

Thanks for your answer!
I bought it from a builder i know. He used it before without issue but stopped to build his own few months ago, the keyboard might have slept a bit...
it s built with real nice!nano v2, not clones.
checked batteries to see any sign of swelling,

#

nothing on both

#

as everything seems fine under eye inspection, I wondered if i did mess something in my config/build that can induce that drain on both sides (and even weirdly the drain is more pronounced on the right side)

#

i ordered a multimeter, but it’ll take a week or so to be there.

#

so I’m open to suggestion till its there

eternal light
#

You've ruled out most of the obvious culprits. I wonder if your batteries are on their last legs...

crisp axle
#

That’s the last test … the orignal builder is sending me a new battery I should receive it before the multimeter so I think I’m gonna need to do some soldering to test it.

crisp axle
#

So, I received my multimeter and i was able to check for power consumption of the nano itself: 10mA on boot and then 6.6mA on what i think was deep sleep.... really high...
could it be the CONFIG_ZMK_SPLIT_BLE_CENTRAL_BATTERY_LEVEL_PROXY=y andCONFIG_ZMK_SPLIT_BLE_CENTRAL_BATTERY_LEVEL_FETCHING=y on my config that causes such high power consumption ?

crisp axle
#

Anyone has tried/have the knowledge of such a thing ?

rigid oyster
#

is that on both sides?

I've done a bit of testing a three months ago on some n!n clones that initially were good and at some point they started to drain about 0.7mA idle no deep sleep. Way lower than yours but still much higher than a fresh set I tested at 0.3mA.

How are you charging the batteries? For me I think using a PD USB charger is damaging something it since using the fresh n!n clones and only connecting to a dumb usba charger has been fine since then.

crisp axle
#

both sides are draining but only mesured the right side as it was the one that drains faster weirdly (cause for what I understood left side should use more power than peripheral ). I’ve read that clones can have an higher resistance that can cause more power consumption but mine are not clones...
Also read that at some point on main there was an default option in the build that was enabled and caused high power drain, but seems to be fixed. I even checked on build logs to fin any ref to that option, and seems to be gone (smth ending with _HV)

I charged them with usb from laptop while using, and from screen usb hub.

molten finch
#

Would not account for all the power drain you're seeing, but make sure you press the reset button once after flashing new firmware. I recently discovered there's a bug somewhere in the bootloader where it uses 0.3-0.5 mA constantly after flashing new firmware.

crisp axle
#

Hum… interesting…definitely in the things to check… thanks !
Do you know if there is an open issue or something like that to eventually add info and follow resolution status ?

molten finch
rigid oyster
crisp axle
#

LiPo + ────> Multimeter RED (A / mA / µA input)
Multimeter BLACK (COM) ────> Nice!nano VCC / BAT +
LiPo − ─────────────────────> Nice!nano GND

rigid oyster
#

Yeah not much more I can think of with the config you shared, Joel's discovered bug and confirming how it was measured. Maybe get a clone n!n, flash your config, measure the consumption and see if the issue happens again over time.

crisp axle
#

Yup… do you have any reco for one specific ?

rigid oyster
crisp axle
#

Thanks, gonna have a look at it asap... with christmas time, shipping time will be hellish tho ...

crisp axle
#

Ordered 2 tenstar red… w8&see when they arrive

#

I guess I’ll keep them on if they work properly

rigid oyster
#

hope that will be the fix for the drain issue

crisp axle
#

I hope it won’t … so that it’s something less expensive than the original nano that is faulty

rigid oyster
#

but don't you want to figure out what's causing the drain? if the clones are fine then we know the genuine n!n is faulty or there's a tiny bridge some where on there causing that drain

crisp axle
#

Yes ! What i meant was that if it fixes the drain that points to a faulty genuine n!n, and that is not ideal because that is more expensive than finding an fixing a little bridge somewhere on the solder 🙂

rigid escarp
crisp axle
#

Update : the clone fixed the issue ... I contacted the seller, and he claims that the keyboard was working fine etc etc (basically telling i’m lying ...)

rigid oyster
#

ugh

crisp axle
#

At least it means ZMK is working properly 🙂