i own a CyberPower OR2200LCDRM2U and was wondering if any nut drivers support this ups. none i have tried have worked although usbhid-ups did tell me that the productid=0601 was not supported yet. i see in the compatability list on the nut website that the PR2200 is supported with the powerpanel driver but the OR2200 is not listed. i am interested in what i am doing wrong or if this is a support issue. i will gladly post any requested data. thank you for your consideration in this matter. _________________________________________________________________ Express your personality in color! Preview and select themes for Hotmail?. http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=PID23391::T:WLMTAGL:ON:WL:en-US:WM_HYGN_express:082009 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090809/ebf2837c/attachment.htm>
On Aug 9, 2009, at 12:01 PM, James Erickson wrote:> i own a CyberPower OR2200LCDRM2U and was wondering if any nut > drivers support this ups. none i have tried have worked although > usbhid-ups did tell me that the productid=0601 was not supported > yet. i see in the compatability list on the nut website that the > PR2200 is supported with the powerpanel driver but the OR2200 is not > listed. i am interested in what i am doing wrong or if this is a > support issue. i will gladly post any requested data. thank you for > your consideration in this matter.Some useful bits of information: * Your Linux (?) distribution and kernel version * The version of NUT which you tried Also, please send the output of 'lsusb -vvv -d :0601' to a file, and attach that to your reply. Thanks!
> From: James Erickson > Date: August 9, 2009 6:17:51 PM EDT > To: Charles Lepple > Subject: Re: [Nut-upsuser] CyberPower OR2200 > > On Sun, Aug 09, 2009 at 03:46:26PM -0400, Charles Lepple wrote: >> On Aug 9, 2009, at 12:01 PM, James Erickson wrote: >> >>> i own a CyberPower OR2200LCDRM2U and was wondering if any nut >>> drivers support this ups. none i have tried have worked although >>> usbhid-ups did tell me that the productid=0601 was not supported >>> yet. i see in the compatability list on the nut website that the >>> PR2200 is supported with the powerpanel driver but the OR2200 is not >>> listed. i am interested in what i am doing wrong or if this is a >>> support issue. i will gladly post any requested data. thank you for >>> your consideration in this matter. >> >> Some useful bits of information: >> >> * Your Linux (?) distribution and kernel version >> * The version of NUT which you tried >> >> Also, please send the output of 'lsusb -vvv -d :0601' to a file, and >> attach that to your reply. >> >> Thanks! > > > Linux Distribution: Gentoo > Kernel Version: Linux-2.6.30-gentoo-r4 > NUT Version: NUT 2.4.1-r1 > > Please find output of "lsusb -vvv -d :0601" attached. > > Thank you very much.-------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: lsusb.txt URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090809/1cf11e99/attachment-0001.txt> -------------- next part -------------- The HID descriptor is only 31 bytes long, which is probably too short to contain the information needed by the usbhid-ups driver. There is a possibility that this UPS is using some sort of USB-to- serial adapter internally. Do you have any details about what software is intended to be used to monitor this UPS?
On Aug 10, 2009, at 2:50 PM, James Erickson wrote:> The OR2200LCDRM2U is a native USB device and does not utilize any > adapters like our older UPS designs do. The USB port design in its > most > basic form should be the same as the 685AVR, 800AVR, and AE550 that > are > listed as compatible with the NUT usbhid-ups driver. If you need any > additional information I would be happy to try to obtain it from our > software/firmware group. If you can let me know precisely what he > needs > I will see if I can obtain it.I am not as familiar with the usbhid-ups driver, but you may have to add "productid=0601" and "-u root" to the driver command line for testing. Let us know how that works, and we will either update the driver, or try some other debug options.
On Aug 10, 2009, at 9:40 PM, James Erickson wrote:> On Mon, Aug 10, 2009 at 07:35:51PM -0400, Charles Lepple wrote: >> On Aug 10, 2009, at 2:50 PM, James Erickson wrote: >> >>> The OR2200LCDRM2U is a native USB device and does not utilize any >>> adapters like our older UPS designs do. The USB port design in its >>> most >>> basic form should be the same as the 685AVR, 800AVR, and AE550 that >>> are >>> listed as compatible with the NUT usbhid-ups driver. If you need any >>> additional information I would be happy to try to obtain it from our >>> software/firmware group. If you can let me know precisely what he >>> needs >>> I will see if I can obtain it. >> >> I am not as familiar with the usbhid-ups driver, but you may have to >> add "productid=0601" and "-u root" to the driver command line for >> testing. >> >> Let us know how that works, and we will either update the driver, or >> try some other debug options. > > attempted command line as follows: > > odysseus ~ # upsdrvctl -DDDDD -u root startSorry I didn't explain this better. Passing a bunch of "-D" flags to upsdrvctl increases the debug level of upsdrvctl, not the driver.> Network UPS Tools - UPS driver controller 2.4.1 > Starting UPS: cyberpower > exec: /lib/nut/usbhid-ups -a cyberpower -u rootThis is where I was being lazy - I didn't check what system you were using, so I didn't have the path handy. Please run "/lib/nut/usbhid-ups -a cyberpower -u root -x productid=0601", and if we need additional detail, we'll add a few more "-D"s to the line. (The debug output can get unmanageable quickly.)> Network UPS Tools - Generic HID driver 0.34 (2.4.1) > USB communication driver 0.31 > This CyberPower device (0764:0601) is not (or perhaps not yet) > supported > by usbhid-ups. Please make sure you have an up-to-date version of NUT. > If > this does not fix the problem, try running the driver with the > '-x productid=0601' option. Please report your results to the NUT > user's > mailing list <nut-upsuser at lists.alioth.debian.org>. > > No matching HID UPS found > Driver failed to start (exit status=1) > odysseus ~ # > > > my /etc/nut/ups.conf reads as follows: > > MONITOR cyberpower at odysseus 1 upsmonuser 090660 master > > [cyberpower] > driver=usbhid-ups > -x productid=0601 > port=auto > > is this a sane configuration?Almost - in ups.conf you don't need the -x flag, just key=value pairs: [cyberpower] driver=usbhid-ups productid=0601 port=auto
[please keep this thread on-list - that way other people can reference it later.] On Aug 10, 2009, at 10:24 PM, James Erickson wrote:>> Please run "/lib/nut/usbhid-ups -a cyberpower -u root -x >> productid=0601", and if we need additional detail, we'll add a few >> more "-D"s to the line. (The debug output can get unmanageable >> quickly.) > > odysseus ~ # /lib/nut/usbhid-ups -a cyberpower -u root -x > productid=0601 > Network UPS Tools - Generic HID driver 0.34 (2.4.1) > USB communication driver 0.31 > Using subdriver: CyberPower HID 0.2 > > just let me know if you need more data.Looks like you can start upsd, and see what it says when you connect with 'upsc'.
>Does the battery voltage match the front panel? The specs on thewebsite say >4x 12V batteries, but that could be in a 2x2 arrangement to give 24V. there is no voltage information on the front panel so i am not sure whats going on there.>Was upsc actually showing two copies of these values, or was that just >cut-n-paste? No worries if it was the latter, but I'm curious to seeif we >are parsing the HID descriptor incorrectly. cut and paste error.sorry about that. _________________________________________________________________ Windows Live?: Keep your life in sync. http://windowslive.com/explore?ocid=PID23384::T:WLMTAGL:ON:WL:en-US:NF_BR_sync:082009 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090811/3f99d5e9/attachment.htm>