similar to: UPS - CYBERPOWER CPS DX600E supported by usbhid-ups

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

> 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

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'

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

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

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

[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

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

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

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

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

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

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:

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

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:

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

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

CyberPower Systems PR6000LCDRTXL5U http://www.cyberpowersystems.com/products/ups-systems/smart-app-ups/pp-series/PR6000LCDRTXL5U.html I had to create the following udev rule (on RHEL6): ATTR{idVendor}=="0764", ATTR{idProduct}=="0601", MODE="664", GROUP="dialout" Shutdown testing successful. UPS comes back online after turning off. # upsc battery.charge:

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 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