search for: battery_capacity

...strok way failed because some vars had spaces. (e.g. model "Liebert NX") 2) new multipliers for: frequency, nominal power. I get correct readings now, before I had 500 Hz, and 200VA and now it's ok for me. Test with your models. 3) added battery temperature 4) removed battery.charge. BATTERY_CAPACITY != charge, BATTERY_CAPACITY means how much the battery has lost its original energy capacity from aging. -S sample outout: ambient.temperature: 25.0 battery.current: 0.00 battery.runtime: 11940 battery.temperature: 20.1 battery.voltage: 540.5 battery.voltage.nominal: 0.0 device.mfr: Liebert devic...

Hi guys, I found the troblue and fix it! I attached the patch. The trouble was in the command reply buffer use. You compute the value that value = reply[6]*256+reply[5] <- it's wrong The right solution: value = reply[5] * 256 + reply[6]; And other bug, battery.runtime compute, you divide this value 60 <- it's wrong right value: divide 1.0 I continue the work on this

...bian Developer - http://people.debian.org/~aquette/<http://people.debian.org/%7Eaquette/> Free Software Developer - http://arnaud.quette.free.fr/ sample output: > > BATTERY_TIME_REMAIN: 52.0 > BATTERY_VOLTAGE: 263.0 > BATTERY_VOLTAGE_NOMINAL: 275.0 > BATTERY_CURRENT: 0.0 > BATTERY_CAPACITY: 100.0 > BYPASS_VOLTAGE: 231.0 > MAX_LOAD: 10000.0 > LOAD_WATTS: 1033.0 > LOAD_VA: 1245.0 > LOAD_PERCENT: 14.0 > INPUT_FREQUENCY: 49.9 > OUTPUT_FREQUENCY: 49.9 > BYPASS_FREQUENCY: 49.9 > INVERTER_TEMP: 0.0 > BATTERY_TEMP: 0.0 > PFC_TEMP: 0.0 > AMBIENT_TEMP: 25.9...

2009/10/15 Farkas Levente <lfarkas at lfarkas.org> > hi, > i read your thread at: > > http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-January/003772.html > > http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-January/003775.html > we've got exactly the same problem that we need a nut driver for liebert > ups. is there any progress in this field?