similar to: variables between manufacturers

On 2018-12-16 8:04 a.m., Charles Lepple wrote: > On Dec 15, 2018, at 10:32 PM, James <bjlockie at lockie.ca> wrote: >> >> My UPS has an LCD that says the battery is 100% and the estimated run time is 12min. >> The uspc has similar results. >> The problem is when line power is lost the UPS batter goes to 0% very quickly (seconds). >> >> It charged to 85%

The battery was replaced in December and the output from upsc was: $ upsc desktop_ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1020 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP850AVRLCD device.type: ups driver.name: usbhid-ups

I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? Does any make better batteries that don't go down faster when they get old? battery.charge: 100 battery.charge.low: 10

Cyberpower CPS850avrlcd https://www.cyberpowersystems.com/product/ups/cp850avrlcd/ shutdown sequence: UNTESTED upsc output: _____  sudo upsc cp-ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1230 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS

CyberPower OR700LCDRM1U (http://www.cyberpowersystems.com/products/ups-systems/smart-app-ups/rackmount-lcd/OR700LCDRM1U.html) upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 6000 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 14.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS OR700

My UPS has an LCD that says the battery is 100% and the estimated run time is 12min. The uspc has similar results. The problem is when line power is lost the UPS batter goes to 0% very quickly (seconds). It charged to 85% when power was restored. 86-100% is slower. I did: $ upscmd desktop_ups test.battery.start.deep Username (admin): Password: OK Now the ups.test.result says there is a

Hi! I just installed a new CP1000PFCLCD (Cyber Power PFC Sinewave UPS) and everything appears to be working correctly, except that I have an oddly high output voltage reading from nut. All of the other values seem consistent with what the front-panel LCD says except for this one. Is this something that needs a correction factor, or perhaps the value the driver is reading has been remapped? BTW,

UPS - CYBERPOWER CPS DX600E upsc usb at localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1650 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 4.8 battery.voltage.nominal: 12 device.mfr: CPS device.model: DX600E device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Hello all, I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here:

Hello I have an issue with an CyberPower DX600E, it doesn't switch up when the power is back; after it has been unloaded; is it because of one of those variables ? regards Franck #upsc myups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1380 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 4.7

I have the same issue of incorrect output voltage being reported by usbhid-ups, as run on NAS4Free (FreeBSD). UPS is as shown below. There is a thread on this list from 2014 that has these same issues, apparently never addressed by any of the later usbhid-ups releases. I?m using 2.7.3. The value I am especially concerned with is the output voltage; if ANY thing should be right on the report, it?s

I just got NUT 2.0.1 running on my Debian system at home.? I have a new CPS UPS connected via USB.? Everything is working fine, except the UPS is showing a value of 120% charged.? Any idea what causes this?? Here's the upsc output for my UPS: battery.charge: 120 battery.charge.low: 10 battery.charge.warning: 20 battery.runtime: 1320 battery.runtime.low: 300 battery.type: PbAcid

Just wanted to report that I have successfully got a Dynex DX-800U UPS functioning with the newhidups driver. This UPS appears to be made by CyberPower Systems and I believe is the same as the CPS 800AVR. --------- # upsc dynex@localhost battery.charge: 66 battery.charge.low: 10 battery.charge.warning: 20 battery.runtime: 399 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 19.7

Hi folks, new to list... nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD. After performing upscmd cp1350 at localhost test.battery.start.quick the result was "Done and warning". I searched through syslog but could find no additional information. What is the warning? Battery charge was 100% before test was performed. Here's the full output from upsc after test:

On Monday 26 October 2020 09:01:31 Charles Lepple wrote: > On Oct 25, 2020, at 11:52 AM, Robert Stocker <kneadtoknow at gmail.com> wrote: > > Init SSL without certificate database > > battery.charge: 100 > > battery.charge.low: 10 > > battery.charge.warning: 20 > > battery.mfr.date: CPS > > battery.runtime: 15690 > > battery.runtime.low: 300

Hello, I am having a heck of a time with false low battery alarms right now.  It has been going on for the last couple of months.  I originally started getting them with a UPS that was 1-2 years old so I thought it was time to change it out and buy a new one.  I'm still getting the false alarms with the brand new one.  The status is "OL LB" which is strange to me. I have a

I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id: 0764:0501, UPS.PowerSummary.Voltage reports 26.6 for the 24V batteries so when the 0.667 battery scale is applied that goes down to 17.7V. upsc output: battery.charge: 100

[updated] OpenBSD 6.1/amd64 NUT 2.7.4p0 (from OpenBSD package) Results of upsc: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2902 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 26.9 battery.voltage.nominal: 24 device.mfr: CPS device.model: CP1500AVRLCDa device.serial: CTHGN200xxxx device.type: ups driver.name:

This was very helpful for me, thank you! On Sat, Oct 24, 2020 at 9:06 AM Charles Lepple <clepple at gmail.com> wrote: > The easiest way to tell if upsd is working is to run "upsc -l" on the same > system, which will list the NUT UPS names, and then run e.g. "upsc mge" > (replacing "mge" with the name returned by "upsc -l") > Here was the

> Subject: [Nut-upsuser] CyberPower DX600E won't switch up after power > is back > Message-ID: <3c530815d1ea602efdfec0d67eb1e0b1 at secretfatty.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hello > I have an issue with an CyberPower DX600E, > it doesn't switch up when the power is back; after it has been > unloaded; > is it because