On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> 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 proper calculation. With the V_interval[] settings, you can >> tweak the new state-of-charge calculation to match what you see 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.charge value when it is recharging. I'm not so sure if it makes sense to make them reconfigurable while the driver is running-- the driver doesn't take very long to restart, and if they were made available through upsrw, they wouldn't be saved back to ups.conf anyway. I could be persuaded, though. -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
