A little over a month ago I acquired a CyberPower CP825AVR-G ups. I found the usb was reporting the same vendor id (0x0501) as a device requiring battery voltage scaling. However the CyberPower does not require the voltage scaling, and was thus showing the wrong voltage. I grabbed the software and removed the battery scaling from the file drivers/cps-hid.c(line 54) to make it work for me. Looks like the same usb device must have been used on another product, so either the product id will have to also be checked, or maybe add another config item to specify battery voltage scaling. -- Cliff Wright <cliff at snipe444.org>
On Dec 21, 2011, at 8:40 PM, Cliff Wright wrote:> A little over a month ago I acquired a CyberPower CP825AVR-G > ups. I found the usb was reporting the same vendor id (0x0501)(side note: 0x0501 is the product ID - the CyberPower vendor ID is defined earlier in the file as 0x0764)> as a device requiring battery voltage scaling. However the > CyberPower does not require the voltage scaling, and was thus > showing the wrong voltage. I grabbed the software and removed > the battery scaling from the file drivers/cps-hid.c(line 54) to > make it work for me. Looks like the same usb device must have > been used on another product, so either the product id will > have to also be checked, or maybe add another config item > to specify battery voltage scaling.Thanks for the heads-up. If you are using Linux, what does lsusb report? Perhaps there is something else in the USB device descriptor that can be used to automatically detect whether the voltage needs to be scaled. -- Charles Lepple
Long ago, Nostradamus foresaw that on 12/21/2011 09:08 PM, Charles Lepple would write:> On Dec 21, 2011, at 8:40 PM, Cliff Wright wrote: > >> A little over a month ago I acquired a CyberPower CP825AVR-G >> ups. I found the usb was reporting the same vendor id (0x0501) > (side note: 0x0501 is the product ID - the CyberPower vendor ID is defined earlier in the file as 0x0764) > >> as a device requiring battery voltage scaling. However the >> CyberPower does not require the voltage scaling, and was thus >> showing the wrong voltage. I grabbed the software and removed >> the battery scaling from the file drivers/cps-hid.c(line 54) to >> make it work for me. Looks like the same usb device must have >> been used on another product, so either the product id will >> have to also be checked, or maybe add another config item >> to specify battery voltage scaling. > Thanks for the heads-up. > > If you are using Linux, what does lsusb report? Perhaps there is something else in the USB device descriptor that can be used to automatically detect whether the voltage needs to be scaled.I have a CyberPower CP1500AVR which also reports 0x0764 0x0501 in lsusb. The iProduct field is "CP 1500C". Maybe the 825 has something different there that could be used.
On Wed, 21 Dec 2011 21:47:37 -0500 Stuart D Gathman <stuart at bmsi.com> wrote:> I have a CyberPower CP1500AVR which also reports 0x0764 0x0501 in > lsusb. The iProduct field is "CP 1500C". Maybe the 825 has something differentlsusb shows CP1500 AVR UPS. But maybe it is the Dynex DX-800U string that needs to be looked for if it is the only one needing scaling. Does the CP1500AVR need scaling? -- Cliff Wright <cliff at snipe444.org>
On Dec 21, 2011, at 10:31 PM, Cliff Wright wrote:> On Wed, 21 Dec 2011 21:47:37 -0500 > Stuart D Gathman <stuart at bmsi.com> wrote: > > >> I have a CyberPower CP1500AVR which also reports 0x0764 0x0501 in >> lsusb. The iProduct field is "CP 1500C". Maybe the 825 has something different > > lsusb shows CP1500 AVR UPS. But maybe it is the Dynex DX-800U string > that needs to be looked for if it is the only one needing scaling. > Does the CP1500AVR need scaling?Actually, can you both post the output of "sudo lsusb -vvv -d 0764:0501"? A text attachment will make it easier to diff them.
On Wed, 21 Dec 2011 22:45:02 -0500 Charles Lepple <clepple at gmail.com> wrote:> Actually, can you both post the output of "sudo lsusb -vvv -d 0764:0501"? A text attachment will make it easier to diff them.I see that the iProduct string is CP825AVR-G (iManufacturer CPS) Bus 001 Device 017: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0764 Cyber Power System, Inc. idProduct 0x0501 CP1500 AVR UPS bcdDevice 0.01 iManufacturer 3 CPS iProduct 1 CP825AVR-G iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 33 US bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 373 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x0001 Self Powered -- Cliff Wright <cliff at snipe444.org>
Long ago, Nostradamus foresaw that on 12/21/2011 10:45 PM, Charles Lepple would write:> lsusb -vvv -d 0764:0501-------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: lsusb.txt URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20111222/74fbab0f/attachment.txt>