On Sat, Oct 4, 2008 at 8:44 AM, Arnaud Quette <[EMAIL PROTECTED]> wrote: > 2008/10/4 Raphael Geissert <[EMAIL PROTECTED]>: >> Package: nut >> Version: 2.2.2-8 >> Severity: wishlist >> Tags: patch [...] >> * the battery charge information, at least as displayed by knutclient 0.9.4, >> is either 0% or 100%, the latter only being displayed when the UPS is fully >> charged. >> * the runtime info is only updated after a test.battery.start.<quick/deep>, >> there's no calibrate.<start/stop> for it. > > I don't know much about TL devices, and I've not dug the ml, but > Charles might have an answer to that.
I don't know much about the Tripp Lite devices covered by the usbhid-ups driver, but the usual debug suggestions apply. You can run the driver with -DDD on the command line, and look for messages related to battery charge. Going out on a limb here, maybe it's something that we have to explicitly poll (versus waiting for it to be reported on the interrupt pipe), for the times when it is below 100%. In any case, it's probably a good idea to first verify that knutclient agrees with upsc. -- - Charles Lepple -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
