similar to: Support for CyberPower CP1350AVRLCD

I bought a new CyberPower CP850AVRLCD ups, connected it to a usb port and I'm trying to use it with hal. I installed [root at phoenix ~]# rpm -q nut nut-client nut-2.2.0-6.1.fc8 nut-client-2.2.0-6.1.fc8 lsusb sees it: [root at phoenix docs]# lsusb Bus 001 Device 001: ID 0000:0000 Bus 005 Device 002: ID 0c45:1050 Microdia Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000

I was getting: "Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: Operation not permitted" so I manually installed the udev rules the source (I installed the Gentoo ebuild). I am now getting: # upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using

Hi Patrick, 2010/11/15 Patrick O'Malley > I've confirmed that the CyberPower CP1350AVRLCD works with nut using > the USB port and the usbhid-ups driver. It is not on your list. > Thanks! > have you checked all variables, and most of all that shutdown works as expected? ie http://new.networkupstools.org/user-manual.html#Testing_shutdowns please also send us an upsc output.

On Tuesday 21 January 2020 19:52:01 Charles Lepple wrote: > sudo lsusb -v -d 0764:0501 copious output, containing this: idVendor 0x0764 Cyber Power System, Inc. idProduct 0x0501 CP1500 AVR UPS bcdDevice 0.01 iManufacturer 3 CPS iProduct 1 CP625HGa I take it that this is evidence they don't follow the spec to the letter.

I've been running the Debian packaged 2.4.3 for a while, working find. When 2.6.0-1 just pushed through to debian, things have stopped working :( I checked what had been the usual suspects in past problems, namely permissions problems in /dev/bus/usb, but all seems in order: $ lsusb ... Bus 009 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS $ ls -l /dev/bus/usb/009/002

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm in the process of upgrading my solution to spread the load over two ups'es. Both are Cyberpower, where one is the classic "Intelligent" 1500LCD, the other a "Value" 2200E Both connect via UPS, and both work using the ups-hid driver. So far so good. The idea is to connect both of them via USB to the same FreeBSD 8

Hi, Have anybody tried Cyberpower Value 600E (USB) under FreeBSD? usbhid-ups from nut 2.4.1 does not recognize (find) the device on my machine. [root at substance /usr/local/libexec/nut]# uname -a FreeBSD substance.dyndns.org 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root at walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [root at substance

Hi. I have this this on a Odroid-u2 backing it up. Have the USB from the CyberPower SX650G plug in the Odroid-u2 and when I do a lsusb it looks like this: Bus 001 Device 008: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS The User's Manual list SE450G and SX650G. So I guess they would take the same driver. CyberPower web page has a driver but it's for i386 not ARM like

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've searched the listserv archive, to no avail, so I hope I'm not duplicating a previous problem. I am anxious to get this working, so I'm open to uninstalling what I have and starting over. One note which may not be meaningful is that this UPS pre-dates the Raspberry Pi I've got connected to it, and I used to use it with the CyberPower software, which requires logging in with a

All, I have built and installed nut from git on Archlinux. It uses the usbhid driver. Beginning a couple of years ago, nut begin failing to run on Archlinux without 'tweaking' or 'fudging' the install. There are two primary problems: (1) upsdrvctl cannot be launched normally i.e. (/usr/sbin/upsdrvctl start) without failing to connect: Dec 14 02:24:39 phoinix systemd[1]:

Hello, I've had this same model CyberPower connected to a linux server and a freebsd server. [root at sensor003 menon]# lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus

On Tuesday 14 January 2020 00:03:09 Gene Heskett wrote: > On Monday 13 January 2020 22:42:46 Charles Lepple wrote: > > On Jan 13, 2020, at 10:17 PM, Gene Heskett wrote: > > >>> (I was looking at the hid-subdrivers.txt file in the latest NUT > > >>> tree, which has the command line amended to not generate that > > >>> "too many non-option

All, I have a Cyberpower UPS that I have been working with for about a year. I have used NUT in the past with good results, but as of late have been seeing issues with nut talking to the UPS. I will start with the information on the server that is running NUT, and has the UPS connected VIA an RS232 cable. O/S : Fedora 9 Kernal (uname -a): Linux haruhi 2.6.26.5-45.fc9.x86_64 #1 SMP Sat

All, I have a Cyberpower UPS that I have been working with for about a year. I have used NUT in the past with good results, but as of late have been seeing issues with nut talking to the UPS. I will start with the information on the server that is running NUT, and has the UPS connected VIA an RS232 cable. O/S : Fedora 9 Kernal (uname -a): Linux haruhi 2.6.26.5-45.fc9.x86_64 #1 SMP Sat

Arjen, I just installed openSuSE 11.1. I though it would be simple to setup the same CyberPower CP1000AVRLCD on the same machine that we worked through the 20+ voltage issue with, but usbhis-ups driver is failing for some reason. I have gotten the output I remember you needing from the last issue for you. What do you think the problem might be? Here is the information: First the logs from the

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

Hey guys, :) recently, I installed Cyberpower PR2200ELCDRT2U, however, I have not managed to get this UPS working with FreeNAS 11, yet. According to compatibility list, PR2200 should work fine, when using powerpanel driver: http://networkupstools.org/ddl/Cyber_Power_Systems/ http://networkupstools.org/ddl/Cyber_Power_Systems/PR2200.html However, when trying to establish a connection between

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:

I have a CyberPower 1500AVR LCD connected by USB to an up-to-date Debian Testing box running nut 2.4.3. /etc/nut/ups.conf contains the following information: [myups] driver = usbhid-ups port = auto When I run upsdrvctl start I receive the following output: Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication