search for: on_batteri

Displaying 5 results from an estimated 5 matches for "on_batteri".

Did you mean: on_battery
2006 May 17
1
upsmon/upssched shutdown problem
Hi, we're trying to do something that's perhaps unorthodox, but seemingly should work; but not for me. We've got a Powerware 9315, that we are serially attaching one machine to. We have several classes of systems that we want to have shut down at different times. I've been doing my config testing by attaching the master machine to a Powerware 9120, and yanking the power
2009 Jan 26
1
ups emerson liebert GTX2 ESP-II serial protocol demo
2009/1/22 Spiros Ioannou <sivann at gmail.com> > Cher Arnaud, > Hi Spiros, > I send you a demo that reads info from an Emerson Liebert > GXT2-10000T230 through the RS-232 port. This uses the "ESP-II (ESP 2) > Protocol". > Current supported data includes: measurements (voltage, temperature, > etc) , ID strings (serial number, etc), status flags (inverter on,
2013 Jun 19
0
[HCL] StarPower PCF-800va supported by richcomm_usb
Greets... ..just bought a cheap UPS today, works in debian 7.0 wrt nut 2.6.4 using richcomm_usb driver... ....output of upsc..... //// root at debian7:~# upsc starpower at localhost device.mfr: Richcomm dry-contact to USB solution device.model: UPS USB MON V1.4 device.serial: unknown device.type: ups driver.name: richcomm_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto
2009 Oct 18
3
liebert GTX2 ESP-II serial support
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?
2010 Apr 02
7
Liebert GXT2 NUT driver
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