2008/10/4 Arjen de Korte <[EMAIL PROTECTED]>: > Citeren Charles Lepple <[EMAIL PROTECTED]>: > >> 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%. > > The usbhid-ups driver polls for practically all variables. The polling > frequency is determined by a flag that is passed in the HID2NUT lookup > table: > > (default) - every 'pollfreq' seconds (default: 30) > HU_FLAG_QUICK_POLL - every 'pollinterval' seconds (default: 2) > HU_FLAG_SEMI_STATIC - when something has been written to the UPS > HU_FLAG_STATIC - only at startup > > In the current 'tripplite-hid' subdriver, the 'battery.charge' has no > special flags assigned, so it will be polled every 'pollfreq' seconds. > Depending on the accuracy of the charge calculation and the load that is > applied, it is quite possible that there is basically nothing reported > between 100% and 0%.
iirc, we've already seen this before, but I don't recall the details, and don't have enough time to dig... the question is: does the windows software report some real battery charge? @Raphael: it's another question for you ;-) Arnaud -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ Free Software Developer - http://arnaud.quette.free.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
