similar to: CyberPower DX600E won't switch up after power is back

> 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

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

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

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

Hi everybody, I recently bought a UPS Cyber Power DX600E ad I'm trying to manage it through Nut under FreeBSD. Unfortunately, usbhid-ups returns an error when I do: [root at berkelium /usr/local/etc/nut]# /usr/local/libexec/nut/usbhid-ups -u root -DD -a onduleur Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31 debug level is '2'

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:

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

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

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

[shutdown sequence] I have tested and verified the shutdown sequence works. [manufacturor] https://www.cyberpowersystems.com/product/ups/ec350g/ mbeisser at nas:~$ upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1575 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 9.3

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

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

CyberPower Value 1500ELCD-RU root at ubuntu:/home/oper# upsc myups at localhost battery.charge: 87 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 5220 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 16.5 battery.voltage.nominal: 24 device.mfr: CPS device.model: Value1500E device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq:

All, I just had a power failure that caused me a little drama. This spurred me into trying to get NUT up on my cyberpower 1500 again. For about 6 months I tried to get it to work with the new power panel drive with no luck. Today I removed all the old files for NUT and installed the newest version I could find (2.4.3) and it works perfectly now with my UPS. Hopefully now I

28 ??????? 2016??. 4:18:06 CEST, Raymond Day <raymondday at hotmail.com> ?????: >I forgot how I ask this. But I just found out. It's a list here: > >http://lists.alioth.debian.org/pipermail/nut-upsdev/2016-October/007229.html > >Thanks again. Seems like it's working real good. > >Is there a way to test if it will turn off my server when the battery >power

On Sun, 27 Oct 2019, EP wrote: > I can't imagine that's the way cyberpower wants their unit to work. With this > behavior the unit does exactly the opposite of what it is built for. It > doesn't protect your equipment. It will destroy it because the server which > was just shutted down cleanly will boot again on a battery-powererd ups. What > a crap. > > But I

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 Battery Backup with Surge Protection, model LE825G Appears to function properly with the driver listed on the HCL for the Cyber Power Systems ups 2 685AVR USB (usbhid-ups). Tested with shutdown mode "UPS Goes On Battery" with a 5 second timer and the system successfully shutdown as expected. upsc output: upsc ups battery.charge: 100 battery.charge.low: 10

Wow thanks for all your help. I unplug the power to the UPS and did the command "upsc serverups" to see if the "battery.charge: 100" would go down. I watched some videos so it's hard drive would spin up to use more power. After about a hour it did go down to "battery.charge: 90" So it is working. Not sure if it will turn off at 20% of battery that's what