similar to: Battery Volts shown as 20+ on Cyber Power UPS CP1000AVRLCD [ DATA ]

Nut Developers, I have unsuccessfully tried to solve a problem with the voltage value on my Cyber Power UPS CP1000AVRLCD. Something is wrong with the battery voltage calculation. It always reads around 20 volts with that's nuts (pardon the pun). Right now: battery.voltage : 20.3 You can take a look for yourself at http://www.3111skyline.com/nutindex.html Is there a parameter I can check

On 2/20/2014 6:55 AM, Charles Lepple wrote: > On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > >> Worse, however, is if there's a power failure right near the end of >> the 2-days-off cycle. That happened to me last week - it was a >> short duration 15 second loss - and the upscode2 driver decided it >> needed to issue a forced shutdown. >> >>

Arjen, I just installed openSuSE 11.1. I though it would be simple to setup the same CyberPower CP1000AVRLCD on the same machine that we worked through the 20+ voltage issue with, but usbhis-ups driver is failing for some reason. I have gotten the output I remember you needing from the last issue for you. What do you think the problem might be? Here is the information: First the logs from the

Hi, Trying to rotate the ups.log on a FreeBSD 7.0 system and its not being nice about it. I tried the "quick and dirty" way by doing : mv /var/log/ups.log ${DATEDDIRECTORY}/ups.log kill -1 `cat /var/db/nut/upslog.pid` I get : Sep 17 10:57:20 valhalla upslog[81972]: could not reopen logfile /var/log/ups.log: Permission denied So I stop upslog, remove the file, and start it

oops, this wasn't supposed to make it into the trunk yet. I can revert it until further testing, but has anyone else tried running with this patch? http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-April/003821.html On Mon, May 4, 2009 at 10:05 PM, Charles Lepple <clepple-guest at alioth.debian.org> wrote: > Author: clepple-guest > Date: Tue May 5 02:05:09 2009 > New

Dear Ted, Am 07.11.2014 um 17:47 schrieb Ted Mittelstaedt: > On 11/3/2014 9:25 PM, thomas schorpp wrote: >> Hi Ted, >> >> Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >>> >> >>> Note that since the UPS relies on the voltage from the battery pack to >>> determine state of charge, it is quite useful to add in the battery pack >>>

Hi Ted, Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: > > Note that since the UPS relies on the voltage from the battery pack to > determine state of charge, it is quite useful to add in the battery pack > voltage to the logs as such: > > --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700 > +++ upslog.c 2014-02-20 09:23:14.000000000 -0800 > @@ -50,6 +50,7

On 11/3/2014 9:25 PM, thomas schorpp wrote: > Hi Ted, > > Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >> > >> Note that since the UPS relies on the voltage from the battery pack to >> determine state of charge, it is quite useful to add in the battery pack >> voltage to the logs as such: >> >> --- upslog.c.orig 2012-07-31 10:38:58.000000000

Hi Thanks for a very nice piece of software. I have a tiny suggestion for upslog.c. It adds a signal handler for the USR1 signal, which simply triggers it to abort the current sleep and log the requested now. I find it useful because my upssched-cmd can then killall -USR1 upslog to ensure that there is an entry in the log for brief power dropouts which would otherwise be unrecorded (because

Hi, One of my APC devices reports: "unacceptable utility voltage rate of change". I believe it has something to do with input voltage fluctuating too fast maybe even beneath or over the input voltage thresholds. Should I worry about this? should I measure input voltage? (I suppose I'd need more than multimeter readings. Maybe an oscilloscope or a multimeter that can record

I finally got around to writing myself a NUT UPS monitoring tool. NUT's UPS monitoring CGI tools provide a detailed instantaneous view of the UPS's state at any moment, but provide no history. The attached tool, upswatch, uses Kiss Gabor's UPS::Nut module and Tobi Oetiker's rrdtool to provide a graphical history of the major UPS operating parameters via a web browser.

On Feb 4, 2014, at 9:05 AM, Chris Duffy wrote: > ugen1.3: <USB UPS PPC> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON [...] > idVendor = 0x06da > idProduct = 0x0005 This VID:PID combination should be handled by blazer_usb. In NUT 2.7.1 and later, this would be covered by nutdrv_qx as well. > I am running all the ups programs as root, i.e. "ps -aux" shows:

I see this in syslog: Aug 12 03:57:22 orion upsd[18274]: Data for UPS [a102-apc-10] is stale - check driver (one for each UPS). Then I see a bunch of messages like this: Aug 12 03:58:02 orion upsd[18274]: write() failed for ::1: Broken pipe Aug 12 03:58:02 orion snmpd[2872]: Connection from UDP: [127.0.0.1]:50940 And then it returns to normal like this: Aug 12 03:58:04 orion upsd[18274]: UPS

I upgraded from V2.2 to V2.4. I use the "upslog" command to log the values of my belkin ups (belkinunv via serial port). It would occasionally start to record garbage, but it would always go back to normal in V2.2 if I restarted. In V2.4 it would not record the values, and the process would fail after the next interval had passed. I had set if for 300 seconds. I walked through the

2005/12/15, Alexander V. Inyukhin <shurick@sectorb.msk.ru>: > > Package: nut > Version: 2.0.2-2 > Severity: wishlist > > Hello. Hi Alexander, I think it is a good idea to log ups variables to rrd > database instead of log file. So, I create standalone > rrd logger dervied from upslog nut client. > Of course, this could be easily implemented using > upsc or

I have taken out the batteries and measured them with a multimeter. They put out 13V (they are rated 12V 9Ah). Putting them back again and disconnecting the UPS from the mains it is kept on, powering all the connected devices. The shutdowns only occur when the UPS is being monitored. Are you sure it's a battery problem? Do UPS perform further tests when they are being polled for data?

Hi Andy, On Dec 8, 2014, at 7:07 PM, Andy Juniper <ajuniper at freeuk.com> wrote: > It adds a signal handler for the USR1 signal, which simply triggers it to abort the current sleep and log the requested now. I will admit that I'm not an expert on how signals interrupt system calls on all systems, but for what it's worth, the code looks good to me. Is it correct to assume that

Charles, We run everything as "root" :) However, we are using NUT 2.6.5. Are we missing something by running 2.6.5 rather then 2.7.1? If so, I can build/install 2.7.1. Thx chris Would On 2/4/14, 9:05 PM, Charles Lepple wrote: > On Feb 4, 2014, at 9:05 AM, Chris Duffy wrote: > >> ugen1.3: <USB UPS PPC> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON > [...]

On Sun, Nov 16, 2008 at 11:08 AM, Arnaud Quette <aquette.dev at gmail.com> wrote: >>> The remainder, until the -pre stage, will be: >>> - the Powerman support (through the powerman driver) for more PDUs >>> - the possible RRD integration into upslog >> >> It would be nice to have native RRD support in upslog, but we may also >> want to point

THANKYOUTHANKYOUTHANKYOUTHANKYOU!!!!!! There was a smaller patch posted to the list for lines -1389,9 +1390,10 a couple years ago, it helped some - BUT - it was still buggy. I have a Compaq R3000, I will get this patch integrated pronto and test Note that since the UPS relies on the voltage from the battery pack to determine state of charge, it is quite useful to add in the battery pack