OvrcAHst wrote:
Since there's no in-hilt recharge and if there's no immediate intention to have one installed and integrated to the existing setup, has anyone tested what the discharge rate (in real-time) is with saber on and what the discharge rate is when saber is off?
Yes, I just did that. I only tested for 10 minutes though, because it's hard to hold leads onto a battery for a long time.
Standby power was 200-240mA and never got any lower in the first 10 minutes after turning the blade off. This suggests it should go through an entire charge in under a day (17 hours), but in my experience it actually lasts a few days so I assume it must drop down to something closer to 50mA or 100mA after a while.
This was the power consumption graph of the first two minutes:
On the left was when I connected the battery, slipped, connected it again, and waited a few seconds for power to settle. Then I turned on the blade (12W+ green, 4.06V Samsung 20R cell, pulse pattern 3, sound on). I only left it on a short time before turning it off, where it reached a peak draw of about 1570mA (~6.3W). Then it dropped down to 200mA in idle mode, and never got any lower. After 10 minutes the cell was at 4.03V.
I didn't set things up well for high-power testing, so the peak draw would likely be higher during normal use. This test does
not indicate that the 12W+ LED isn't running hot enough. It mostly just shows that the idle power is way too high.
Standby power should be less than 1mA, ideally less than 0.1mA. My ASP saber is running orders of magnitude hotter than that, at least until I get a kill/charge port installed.
Oh, and if the blade-on readings are anywhere near accurate, the expected runtime with the blade on looks like about 2.5 hours. Maybe more since it's direct-drive so current will drop with voltage. But at full 12W+ power with no blade flicker, runtime should be only about an hour.
Edit: Re-uploaded graph, forgot to turn off lowpass filter first time.