On 10/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I have in my possession a PowerWalker VI 1400, the big brother to the > NUT-supported VI 1000. It seems to work fairly well with the > megatec-driver, however there is one bigger problem and that is the > incorrect detection of battery.charge. This causes the UPS send the OB > LB flag at - according to NUT - 43% of battery.charge, however the > real charge at this point is closer to ~25%. A powerloss is inevitable > when there is - again, according to NUT - 17% left in the > battery.charge. I haven't tried the dev-tree but since megatec.c in > the dev-tree is identical to the megatec.c in nut-2.2.1-pre1 I assume > the problem is still around.
>From NUT 2.2.0 onwards, the megatec driver supports an option named "battvolts" in ups.conf, in which one specified the battery.voltage reported by the UPS when discharged (just before it turns itself off, not when it triggers a low battery event), and the voltage when the UPS is full. For example... battvolts = 20:26.2 ...would mean "battery.voltage: 20" when almost completely discharged and "battery.voltage: 26.2" when fully charged. The value you are obtaining for "battery.charge" is just a best effort value based on data obtained from other models. If that value is incorrect, the only way to set it straight is to use the "battvolts" option. -- Carlos Rodrigues _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
