[Nut-upsuser] CyberPower OR2200

Charles Lepple clepple at gmail.com
Tue Aug 11 01:50:39 UTC 2009

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 start

Sorry 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 root

This 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:


More information about the Nut-upsuser mailing list