similar to: why did self test warn?

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%

On 2019-02-16 12:41 p.m., Stuart D. Gathman wrote: > On Sat, 16 Feb 2019, James wrote: > >> These changed: >> battery.runtime: >> ups.load: >> >> Is the battery dead again? >> Do I need a new UPS? > > Compare the upsc output with the screen/led display on the UPS.  If they > are in agreement, then there is no problem with NUT.  Your issue is

I switched my desktop with my raspberry pi because I thought my desktop ups had a larger capacity. Now the ups.load of each is not what it was (it should be). The battery.runtime is better for my desktop (it's supposed to be worse) and my raspberry pi is worse (I hoped for hours better). What am I seeing? I switched them for longer raspberry pi time and the APC battery is getting old. :-)

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

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

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

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

On Sat, 16 Feb 2019, James wrote: > These changed: > battery.runtime: > ups.load: > > Is the battery dead again? > Do I need a new UPS? Compare the upsc output with the screen/led display on the UPS. If they are in agreement, then there is no problem with NUT. Your issue is with the UPS or the battery. Aftermarket batteries can be .. substandard. We bought one in 2018 that

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:

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:

I would like to solicit some feedback re: the battery.runtime.lowconfiguration settings through NUT. I was able to set the value using the 'upsrw' command but when I did a 'upsc' the configuration seems incorrect. Please see below for details. Thank you OS name and version: ?? ?Description:??? Debian GNU/Linux 12 (bookworm) ?? ?Release:??????? 12 ?? ?Codename:?????? bookworm

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

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,

I'm going to guess that since your test runtime of 305 is very close to the low limit of 300, that's the warning. Not yet a fail, but very, very close. On October 31, 2020 11:41:39 AM CDT, Rick Dicaire <kritek at gmail.com> wrote: >Hi folks, new to list... >nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD. > >After performing upscmd cp1350 at localhost

On Saturday 31 October 2020 20:13:48 Rick Dicaire wrote: > On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > > I'm going to guess that since your test runtime of 305 is very close > > to the low limit of 300, that's the warning. Not yet a fail, but > > very, very close. > > I tried setting > override.battery.runtime.low = 60

On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > I'm going to guess that since your test runtime of 305 is very close to > the low limit of 300, that's the warning. Not yet a fail, but very, very > close. > I tried setting override.battery.runtime.low = 60 in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only

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

On 6/4/2017 4:46 PM, Charles Lepple wrote: [snip] >> 4) when I went down to 95 volts, the "AVR" kicked in to boost the >> voltage without going to battery. This was indicated by a "click" from >> the UPS and an indication on the UPS display. > > In non-explore mode, does the driver report the AVR status? (No need to set things back up if you have

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

On Sat, 16 Feb 2019, James wrote: > Now it says: > battery.runtime: 1170 > The display on the UPS fluctuates between 16-19 minutes. > > ups.load says 30 constantly and The display on the UPS says 30% so I think > that is correct. battery.runtime is in seconds, so that agrees with the UPS display as well. > How you find out your battery was manufactured in 2012? APC