search for: battery_min

...lly charged, so that's better than > >> nothing. > > > > Yes, the V_interval[] being exposed is a very good idea and does seem > > the only sensible workaround. > > As of the latest push (rev 0d1e017), the tripplite_usb driver > (v0.22) now reads the battery_min and battery_max variables from > ups.conf at startup. Great, many thanks. I have pulled tripplite_usb.c only (with the rest as provided by Gentoo, meaning version 2.7.1) but the result ends up reading incorrect values: 0.050452 Setting 'battery_min' to 1e+01 0.050472 Se...

...e via >> upsc when the battery is fully charged, so that's better than >> nothing. > > Yes, the V_interval[] being exposed is a very good idea and does seem > the only sensible workaround. As of the latest push (rev 0d1e017), the tripplite_usb driver (v0.22) now reads the battery_min and battery_max variables from ups.conf at startup. Testing on my OMNIVS1000, the voltage difference between OB and OL is significant, so aside from having two sets of min/max ranges, I'd say calibrate it on the discharge side of the slope, and don't put too much stock in the battery.charg...

...hat's better than >>>> nothing. >>> >>> Yes, the V_interval[] being exposed is a very good idea and does seem >>> the only sensible workaround. >> >> As of the latest push (rev 0d1e017), the tripplite_usb driver >> (v0.22) now reads the battery_min and battery_max variables from >> ups.conf at startup. > > Great, many thanks. I have pulled tripplite_usb.c only (with the rest > as provided by Gentoo, meaning version 2.7.1) but the result ends up > reading incorrect values: > > 0.050452 Setting 'battery_min&...

Hello, At 09:24 -0400 on 2014-5-23 Charles Lepple wrote: > > See attached. Still doesn't have the writable V_interval values, > but I probably won't have time to test that until later. Thank you for the patch. > Don't worry about the battery physical properties for now - the > problem there is that we don't have enough information from the UPS > to do a