On 2015-07-20 04:04, Charles Lepple wrote:
Michal,
I ran across this Debian bug today:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707223
It's a bit of a corner case, and it's for NUT 2.6.4 (apcsmart driver v3.04),
but I was wondering if it was still applicable for the latest code?
It might be, I don't recall changing much in context of those commands -
and the code never relied on registers.
"nut reports 100% battery charge after unplugging the battery on a Smart-UPS
2200 RM (SUA2200RMI2U) using apcsmart.
Powerchute correctly reports the missing battery. The front panel displays 0%
charge and change battery is flashing.
The Smart Protocol commands B (Battery voltage) and f (Battery level) report
false values of 55.35V and 100%.
The missing battery might be indicated by register values:
Register0: 00
Register1: 20
Register2: 00
Register1 indicates: Command sent to stop bypass with no battery connected -
UPS still in bypass
All register values are 00 on an identical UPS with a connected battery."
I'll try looking into it.
_______________________________________________
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
