search for: 136v

...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 at 9:22 AM, Charles Lepple <clepple at gmail.com> wrote: > On Mar 23, 2014, at 11:12 PM, Bill S wrot...

...UPS.Input.Voltage, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 119 On battery: 0.082947 Report[get]: (3 bytes) => 0f 00 00 0.082957 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 16, Value: 0 > I also noted that the output voltage remained at 136V. This value (136) is suspiciously a Logical Minimum that was set elsewhere in the HID Report Descriptor. AC: 0.263726 Report[get]: (3 bytes) => 12 77 00 0.263735 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: 136 Note that 0x77 == 119 decimal. Bat...

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