search for: 119v

...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 it would. I also noted that the output voltage remained at 136V. I do have a old General Radio variac kicking around with no line cord or sockets that I can cobble something together with if these files do not provide enough data. On Wed, Mar 26, 2014...

...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 it would. Hmm, I wonder if it just wasn't polling fast enough? From the AC file: 0.263461 Report[get]: (3 bytes) => 0f 77 00 0.263469 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 119 On battery...

On Mar 23, 2014, at 11:12 PM, Bill S wrote: > The output of the driver is below. The incorrect voltage of 136 is > shown at 0.265256. It should match input voltage of 119 as shown at > 0.265219 but it doesn't. The voltages displayed on the UPS LCD panel > information however are equal and match the input voltage provided by > the driver. There might be other incorrect

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