search for: kenwood0622

It would appear that there is nothing that can be done to correct the output voltage reading. Is there anyone in this group that would have a suggestion on alternative software for remote monitoring of a UPS installed on a distant server?

On Apr 4, 2014, at 8:56 AM, Bill S <kenwood0622 at gmail.com> wrote: > It would appear that there is nothing that can be done to correct the > output voltage reading. Nothing easy, but the AC output voltage is reported by the UPS. It requires more than just a five-minute fix, though. The DC battery voltage is the one that seems to b...

On Fri, Apr 4, 2014 at 9:49 AM, Charles Lepple <clepple at gmail.com> wrote: > On Apr 4, 2014, at 8:56 AM, Bill S <kenwood0622 at gmail.com> wrote: > >> It would appear that there is nothing that can be done to correct the >> output voltage reading. > > Nothing easy, but the AC output voltage is reported by the UPS. It requires more than just a five-minute fix, though. > > The DC battery volta...

First I have to apologize for what I think will be the start of a new thread when I send this, but I did not receive a copy of my original posting that I can reply to and I do not see a way of adding to the thread without that copy. If I am wrong, please advise how I should have posted and it won't happen again. I suspect there has been no response to my posting of March 24, 2014 because

I just noticed what I think is another incorrectly reported value. I found that on the second screen of upsstats.cgi, the one with bar graphs, that the reported battery voltage is 16.0V even though the battery charge is at 100% and the UPS is on AC power. I would have thought it should be more than 25V.

Since there is apparently no immediate solution to upsstats.cgi not reading the output voltage correctly, I have moved on to trying to use upsset.cgi. To recap the UPS is a CyberPower CyberPower CP1500PFCLCD UPS running on a headless server running Slackware 14.1 with the 3.10.7 kernel. The version of NUT is 2.71 and I am using usbhid-ups for communication with the UPS The problem is that when

I have attached two .gz files of the driver output with the -DDDD option. One is for when the unit is on the line AC and the the other is when it is on battery so that there are at least two points of reference. In earlier tests, I did note that when the unit was placed on battery that the upsstats.cgi screen reported that the input voltage from 119V to 120V and did not go to zero as I expected

On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: <<Snip>> > > I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V:

I recently purchased a CyberPower CP1500PFCLCD UPS as a replacement UPS for a headless server running Slackware 14.1 with the 3.10.7 kernel. I then downloaded the NUT 2.7.1 tarball on the server and following the directions installed the software. The installation went well and the UPS will shutdown the server using the forced down test and then it powers back up as it should. The