similar to: [HCL] CyberPower OR700 supported by usbhid-ups

Hi all. I'm trying to get a CyberPower OR700LCDRM1U UPS working with NUT (via USB). I assumed this would be compatible since the OR2200LCDRM2U is. Clearly I'm wrong or missing something vital. I'm on FreeBSD, using the version of NUT from the ports tree (2.6.1). FWIW, I tried compiling from source with similar results. Here's my UPS in ups.conf: [ssups] driver=usbhid-ups

I'm trying to debug a problem with SIP trunks from a provider, but I'm looking for more detail then what "debug" is showing me in the console. (I'm running the Asterisk 1.6.0.10 w/ Trixbox) I'm rejecting incoming calls with a 401 Forbidden, but debug isn't saying why...bad secret, bad domain, bad user, etc. Is there a place I can see the reason? Thanks! --Brian

I'm playing with a new CentOS 8 with a cyperpower OR500 (a smaller sibling to the OR700) plugged in via USB. GNOME sees the UPS... but NUT does not (even if I shut down gnome). > [root at delp ups]# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.4 > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > No matching HID UPS found

[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

Cyber Power Systems CP1000PFCLCD = upsc output = attached = Shutdown results = I experienced a genuine power outage shortly after setup. The 1 master system and the 1 slave system both shutdown successfully. The master shutdown before the slave (*not* a bug report; I may not have this configured correctly yet). The UPS was not powered off by the master. I don't know if the UPS

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 Mar 27, 2020, at 11:51 PM, Ben Kamen <ben at benkamen.net> wrote: > > I'm playing with a new CentOS 8 with a cyperpower OR500 (a smaller sibling to the OR700) plugged in via USB. > > GNOME sees the UPS... but NUT does not (even if I shut down gnome). > >> [root at delp ups]# upsdrvctl start >> Network UPS Tools - UPS driver controller 2.7.4 >>

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

Cyber Power Systems CP600LCD https://www.cyberpowersystems.com/product/ups/cp600lcd/ upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2220 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP600 device.type: ups driver.name: usbhid-ups

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

Cyber Power Systems AVRG750U https://www.cyberpowersystems.com/product/ups/avrg750u/ upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 15360 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: AVRG750U device.serial: <REDACTED> device.type: ups

Attached is the first 32 seconds of the driver output after applying the patch which fixes the battery scaling problem for this UPS. Matthew Stapleton Email: matthew4196 at gmail.com On 10/08/14 01:27, Charles Lepple wrote: > On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com>

I didn't want to sign up for the nut-devs list or create a git account just to provide this information, so I hope posting this info here is OK... I just bought a Cyber Power Systems EC750G UPS for use as a spare. Here are some info for it: ========================= upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime:

On Nov 1, 2014, at 9:28 PM, hyouko at gmail.com wrote: > Provided that the subdriver works, I'd like to see, if possible, the logs of: > - driver startup > - a command that succeeds > - a command that fails > - q1 when online and all's ok > - q1 on battery > - setting pins_shutdown_mode Attached is a log of most of these conditions. Looks like reading the status for

Hi, Am I hitting some limit in match? Consider the following example: > tst<-seq(100,125,by=.2)%in%seq(0,800,by=.1) > sum(tst) [1] 76 > seq(100,125,by=.2) [1] 100.0 100.2 100.4 100.6 100.8 101.0 101.2 101.4 101.6 101.8 102.0 102.2 [13] 102.4 102.6 102.8 103.0 103.2 103.4 103.6 103.8 104.0 104.2 104.4 104.6 [25] 104.8 105.0 105.2 105.4 105.6 105.8 106.0 106.2 106.4 106.6 106.8

Hi, Am I hitting some limit in match? Consider the following example: > tst<-seq(100,125,by=.2)%in%seq(0,800,by=.1) > sum(tst) [1] 76 > seq(100,125,by=.2) [1] 100.0 100.2 100.4 100.6 100.8 101.0 101.2 101.4 101.6 101.8 102.0 102.2 [13] 102.4 102.6 102.8 103.0 103.2 103.4 103.6 103.8 104.0 104.2 104.4 104.6 [25] 104.8 105.0 105.2 105.4 105.6 105.8 106.0 106.2 106.4 106.6 106.8

Hi I have a called fil consisting of the following strings. > fil [1] " 102.2 639" " 104.2 224" " 105.1 1159" " 107.1 1148" " 108.1 1376" [6] " 109.2 1092" " 111.2 1238" " 112.2 349" " 113.1 1204" " 114.1 537" [11] " 115.0 303" " 116.1 490"

On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: >> >>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage

On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: > >> 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:

> Sure enough, it turned off after about 30 seconds (t=228). I unplugged it for about five seconds, and it came back on three minutes after I plugged it back in. However, the bypass bit inversion might be responsible for this: > > 228.304623 send: 'Q1' > 228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010' > 228.515494 ups_infoval_set: non