Has anyone had any success with the HP T/R2200 G2? I have used the T/R2200 with nut a few times before and it works great, but the G2 doesn't want to talk to me. I have tried bcmxcp from 2.0.4, 2.2.2, and svn, as well as the usb drivers. Maybe the G2 isn't a rebadged powerware unit? Thanks James
> > Has anyone had any success with the HP T/R2200 G2? I have used the > T/R2200 with nut a few times before and it works great, but the G2 > doesn't want to talk to me. > > I have tried bcmxcp from 2.0.4, 2.2.2, and svn, as well as the usb > drivers. Maybe the G2 isn't a rebadged powerware unit? >One more thing... if it helps, the usb info is: Bus 003 Device 003: ID 03f0:1f0a Hewlett-Packard James
On Sep 10, 2008, at 8:29 AM, James Harper wrote:> > >> -----Original Message----- >> From: Charles Lepple [mailto:clepple at gmail.com] >> Sent: Wednesday, 10 September 2008 22:11 >> To: James Harper >> Cc: nut-upsuser at lists.alioth.debian.org >> Subject: Re: [Nut-upsuser] HP T/R2200 G2 >> >> On Wed, Sep 10, 2008 at 6:18 AM, James Harper >> <james.harper at bendigoit.com.au> wrote: >>>> >>>> Has anyone had any success with the HP T/R2200 G2? I have used the >>>> T/R2200 with nut a few times before and it works great, but the G2 >>>> doesn't want to talk to me. >>>> >>>> I have tried bcmxcp from 2.0.4, 2.2.2, and svn, as well as the usb >>>> drivers. Maybe the G2 isn't a rebadged powerware unit? >> >> What errors are you getting with the USB drivers? (Permissions are a >> little more complicated with USB peripherals.) > > 'Can't open POWERWARE USB device, retrying ...' with the bcmxcp_usb > driver. > > I'm running the drivers directly for testing, and specifying '-u root' > to make sure that permissions aren't an issue. An strace shows no > access > denied type errors. > >>> One more thing... if it helps, the usb info is: >>> >>> Bus 003 Device 003: ID 03f0:1f0a Hewlett-Packard >> >> What does 'lsusb -vvv -d 03f0:1f0a' return? >> > > Attached. > > The source code definitely makes no reference to that vendorid or > productid that I can see. > > I did try the '-x explore' with the usbhid-ups driver (2.2.2 version), > debug output of that is attached if that helps.The output looks like it could be relatively easily supported by usbhid-ups. I'm forwarding it to the -dev list. (For reference, the debug output compresses easily.) -- Charles Lepple clepple at gmail
[moved to nut-upsdev] On Sep 10, 2008, at 8:29 AM, James Harper wrote:> > >> -----Original Message----- >> From: Charles Lepple [mailto:clepple at gmail.com] >> Sent: Wednesday, 10 September 2008 22:11 >> To: James Harper >> Cc: nut-upsuser at lists.alioth.debian.org >> Subject: Re: [Nut-upsuser] HP T/R2200 G2 >> >> On Wed, Sep 10, 2008 at 6:18 AM, James Harper >> <james.harper at bendigoit.com.au> wrote: >>>> >>>> Has anyone had any success with the HP T/R2200 G2? I have used the >>>> T/R2200 with nut a few times before and it works great, but the G2 >>>> doesn't want to talk to me. >>>> >>>> I have tried bcmxcp from 2.0.4, 2.2.2, and svn, as well as the usb >>>> drivers. Maybe the G2 isn't a rebadged powerware unit? >> >> What errors are you getting with the USB drivers? (Permissions are a >> little more complicated with USB peripherals.) > > 'Can't open POWERWARE USB device, retrying ...' with the bcmxcp_usb > driver. > > I'm running the drivers directly for testing, and specifying '-u root' > to make sure that permissions aren't an issue. An strace shows no > access > denied type errors. > >>> One more thing... if it helps, the usb info is: >>> >>> Bus 003 Device 003: ID 03f0:1f0a Hewlett-Packard >> >> What does 'lsusb -vvv -d 03f0:1f0a' return? >> > > Attached. > > The source code definitely makes no reference to that vendorid or > productid that I can see. > > I did try the '-x explore' with the usbhid-ups driver (2.2.2 version), > debug output of that is attached if that helps. > > Thanks > > James<r2200g2.txt><r2200g2-explore.txt>Here they are, compressed. I think that it should be relatively easy to support this model, since it appears to follow the HID Power Device Class spec. (The devil is in the details, such as what the UPS actually reports as the battery runs down.) Arnaud, Arjen - any thoughts? -- Charles Lepple clepple at gmail -------------- next part -------------- A non-text attachment was scrubbed... Name: r2200g2.txt.gz Type: application/x-gzip Size: 3568 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20080910/a09eaf57/attachment.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: r2200g2-explore.txt.gz Type: application/x-gzip Size: 5252 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20080910/a09eaf57/attachment-0001.bin
Citeren "Arjen de Korte" <nut+devel at de-korte.org>:> OK, it's in the trunk now. It would be nice if James could check if it > works and if he's able to change the nominal output voltage through > 'upsrw'. I took the liberty to assume this would work in a similar > manner as my MGE Evolution (I have quite a bit of information on that > one now).In retrospect you were absolutely right with your observation that this looks like a Tripplite device. Looking at the similarities (manuals, pictures) there is little doubt that this is a re-branded Tripplite SMART2200RMXL2U. Therefor we should probably support this device through the 'tripplite-hid' subdriver. I'll remove the 'hp-hid' subdriver and apply the (slightly modified) patch you proposed to the trunk. Best regards, Arjen -- Please keep list traffic on the list