Hi, > Citeren Jon Bendtsen <jbendt...@laerdal.dk>: > > I have a R3000XR, and i use bcmxcp using a seriel port out, since i > > can not find a USB port on the UPS. > > > > I do have a USB2serial on the host. > > > > I still experience that NUT upsstats.cgi says the UPS battery is at > > 97%, and some days later at 100%. It happens regularly. > > The bcmxcp driver reports directly what the UPS is telling us. If the > algorithm used for battery charge calculation is voltage based (not > entirely unlikely), small variations in the battery voltage may make > it jump between two fixed values all the time. I have a very strong > opinion about 'correcting' such behavior, since it can also be an > indication of imminent battery failure.
Totally agree with Arjen. When on line it is more of a voltage reading. And set the cell voltage to about 2.26 when on 100%. But it is not a direct voltage reading. It depends on where it land, when it change to floating. For example: If I do a battery test, it drop to about 80% before end. Then it start charging. But the % don't follow the voltage. I have 24 volt nominal so it is on 95% from about 26.5 to 27.3. Then when it goes to floating it drop to about 27.07 and say 99%. If it drop much when floating you get a low % reading, and as Arjen say it may indicate a bad cell. ( I know as I experienced that). BUT when it change to battery, the meter indicate remaining runtime in %. So start fixing this would make more damage than help. This is calculated during battery test. So if you have strange or large run-time numbers, do a battery test. (see page 115 of XCP Rev C.doc) /Kjell _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser