[Nut-upsdev] Using USB CyberPower CPL550SL / AE550,

[Greg Grotsky]

Guys,
  How can I get my system to boot up and load the driver correctly?  I
rebooted it when I got home this evening and the UPS device moved to this
spot: /dev/bus/usb/002/002 which wouldn't be a big deal, except the
permissions changed back to root:plugdev.  When I load upsdrvctl it can't
connect because of the permissions.

Anyway, how can I go about finding the correct ups usb device in /dev and
changing the permissions of it during boot (before upsdrvctl gets issued)??

Any suggestions?

On 2/7/07, Peter Selinger <selinger at mathstat.dal.ca> wrote:
>
> Hi Greg,
>
> the battery runtime is computed by the device firmware. 80 minutes
> sounds like a lot, but there's no guarantee that it's accurate.
>
> -- Peter
>
> Greg Grotsky wrote:
> >
> > Thanks Peter, Charles Lepple repsonded this morning and I got it all
> sorted
> > out. I believe it's working now, I can execute "upsc myups" and it spits
> out
> > all sorts of cool info. I have a question though: Does "battery.runtime"
> get
> > calculated based on the current load or is it just something that the
> > manufacturer sets in the firmware for the model? I ask because the value
> I
> > currently have for battery.runtime is 4800 and from what I read that is
> in
> > seconds. I'm basically running just a computer (no monitor) from the
> ports
> > on this thing, does 80 minutes of runtime sound right?
> >
> > Thanks,
> > -Greg
> >
> >
> > On 2/7/07, Peter Selinger <selinger at mathstat.dal.ca> wrote:
> > >
> > > From the file INSTALL:
> > >
> > >    The setup for USB ports is slightly more complicated. Device files
> > >    for USB devices, such as /proc/bus/usb/002/001, are usually
> > >    created "on the fly" when a device is plugged in, and disappear
> > >    when the device is disconnected.  Moreover, the names of these
> > >    device files can change randomly. To set up the correct
> > >    permissions for the USB device, you may need to set up (operating
> > >    system dependent) hotplugging scripts.  Sample scripts and
> > >    information are provided in the scripts/hotplug and
> > >    scripts/udev directories. (If you want to try if a driver
> > >    works without setting up hotplugging, you can add the "-u root"
> > >    option to upsd, upsmon, and drivers; this should allow you to
> > >    follow the below instructions. However, don't forget to set up the
> > >    correct permissions later!).
> > >
> > > -- Peter
> > >
> > > Greg Grotsky wrote:
> > > >
> > > > So I just bought one of these fabulous CyberPower UPS devices from
> > > BestBuy
> > > > hoping I could control it with my machine.  Luckily, I found
> NUT!  I've
> > > got
> > > > the SVN sources and compiled and installed them but I haven't been
> able
> > > to
> > > > get it to recognize the usb AE550.
> > > >
> > > > When I plug the usb cable in I see this in syslog:
> > > > Feb  6 22:36:56 mythbox kernel: usb 1-1: new low speed USB device
> using
> > > > ohci_hcd and address 4
> > > > Feb  6 22:36:56 mythbox kernel: usb 1-1: configuration #1 chosen
> from 1
> > > > choice
> > > > Feb  6 22:36:56 mythbox kernel: hiddev96: USB HID v1.10 Device [CPS
> UPS
> > > > AE550] on usb-0000:00:02.0-1
> > > >
> > > > I run lsusb and I see this:
> > > > $ lsusb
> > > > Bus 003 Device 001: ID 0000:0000
> > > > Bus 001 Device 004: ID 0764:0501 Cyber Power System, Inc.
> > > > Bus 001 Device 001: ID 0000:0000
> > > > Bus 002 Device 002: ID 15c2:ffda SoundGraph Inc.
> > > > Bus 002 Device 001: ID 0000:0000
> > > >
> > > > My /usr/local/ups/etc/ups.conf file contains
> > > > [CyberPower]
> > > >  driver = usbhid-ups
> > > >  port = auto
> > > > # vendor = "Cyber Power Systems"
> > > > # product = "AE550"
> > > > # vendorid = 0764
> > > > # productid = 0501
> > > >  desc = "MythBox"
> > > >
> > > > When I run upsdrvctl start I get this:
> > > > $ ./upsdrvctl start
> > > > Network UPS Tools - UPS driver controller 2.1.0
> > > > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (
> 2.1.0
> > > )
> > > >
> > > > No matching HID UPS found
> > > > Driver failed to start (exit status=1)
> > > >
> > > >
> > > > I have tried everything in attempt to get this recognized.  As you
> can
> > > see
> > > > in my conf file I tried supplying the values I recieved in lsusb and
> the
> > > > vendor and product names.  I've tried doing that at the command line
> as
> > > well
> > > > running usbhid-ups -x vendor=CyberPower.  I've also tried supplying
> > > > usbhid-ups with the device name /dev/usb/hiddev0 or
> /dev/usbdev1.4_ep00
> > > or
> > > > /dev/usbdev1.4_ep81 (not sure what these are but I think they all
> > > represent
> > > > the ups).  I've created a user for the software to use and set the
> > > > permissions correctly.  What am I missing??
> > > >
> > > > BTW: I'm running 64bit version of Debian.  I didn't have any
> problems
> > > with
> > > > the compile or install.
> > > >
> > > > Thanks,
> > > > -Greg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070207/178964bc/attachment.htm