[Nut-upsuser] Nut and PowerWare 5115

Tue Apr 28 12:16:57 UTC 2009

Hi Arnaud and Kjell,

Sorry for the slow reply.

From: Arnaud Quette 
Sent: Friday, April 24, 2009 7:59 PM
To: Greg 
Cc: Kjell Claesson ; nut-upsuser at lists.alioth.debian.org 
Subject: Re: [Nut-upsuser] Nut and PowerWare 5115

Greg,

2009/4/23 Greg <greg_roll at hotmail.com>

  Hi Arnaud and Kjell,

  Please find answers below.

  I also re-compiled 2.4.1 myself on Ubuntu and still got the same issues/errors.

ok, I think I've got it: how did you tried this one: recompiling the deb package or the source.
there is a udev change in 2.4.1 that is targeted to Jaunty.
udev rules were previously in /etc/udev/rules.d, and is now is /lib/udev/rules.d

this means that the privileges won't be set correctly if you use such a package on pre jaunty.
if you went from source, well I'm not sure.

I compiled from source but running on Ubuntu 8.10

I just did a clean compile of 2.4.1 on Ubuntu 8.10 from source and after running ./configure make and make install. upsdrvctl is not available.
It exists in /usr/local/ups/bin but I cannot run it. Very weird. So I would say my issues with the previous timeouts was due to installing the DEB package and it not completely being removed.

  If you have anything you would like run or if there is any other debugging I am happy to compile/run it.

yep, I'm interested in a simple 'lsusb'
then, validates the privileges for both 2.2.2 and 2.4.1 with the data from lsubs (Bus and Dev)
by doing an "ls -l /dev/bus/usb/XXX/YYY" (and/or /proc/bus... equivalent).

Here is the output of lsusb and ls on Ubuntu 8.10 running nut 2.2.2
=========================================================
Bus 002 Device 002: ID 0c45:63fa Microdia 

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 005: ID 0e0f:0002 

Bus 001 Device 004: ID 06da:0002 Phoenixtec Power Co., Ltd UPS

Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

crw-rw-r-- 1 root nut 189, 3 2009-04-28 21:14 /dev/bus/usb/001/004

===================================================

I can't get an output of 2.4.1 as it wont compile now on Ubuntu 8.10.

Here is the output of lsusb and ls on my QNAP running nut
=========================================================
Bus 001 Device 005: ID 06da:0002 Phoenixtec Power Co., Ltd.
Bus 001 Device 004: ID 04a9:10a5 Canon Inc.
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc.
Bus 001 Device 001: ID 0000:0000 Virtual Hub

After plugging in device
-rw-r--r--    1 admin    administ       52 Apr 28 22:11 /proc/bus/usb/001/005

I think changed the permissions to...
-rw-rw-r--    1 admin    administ       52 Apr 28 22:11 /proc/bus/usb/001/005
=========================================================

After changing the permissions on my QNAP above I still get the same output
=========================================================
Network UPS Tools - UPS driver controller 2.4.1
Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1)
USB communication subdriver 0.17
usb_set_debug: Setting debugging level to 3 (on)
usb_os_init: Found USB VFS at /proc/bus/usb
usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 005 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
Communications with UPS lost: Receive error (data): got 32 bytes instead of 116!!!

USB error: error sending control message: Connection timed out
Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31!

USB error: error sending control message: Broken pipe
Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31!

USB error: error sending control message: Broken pipe
Communications with UPS lost: Receive error (Request command): COMMAND: 31

RECONNECT USB DEVICE

usb_os_find_busses: Found 001
usb_os_find_busses: Skipping non bus directory devices
usb_os_find_devices: Found 005 on 001
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
USB error: could not set config 1: Broken pipe
Can't set POWERWARE USB configuration
Unable to find POWERWARE UPS device on USB bus

Things to try:

 - Connect UPS device to USB bus

 - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf).
   See upsdrvctl(8) and ups.conf(5).

Fatal error: unusable configuration
CLOSING

Driver failed to start (exit status=1)

=================================================================

my guess is that it's a permission issue.
and you can validate it by running the driver as root (ie bcmxcp_usb -u root ...)

Unfortunately there is no change.

I guess we can rule out ubuntu 8.10 and nut 2.41 being an issue as that looks like some other issue not related to this.

So my 5115 works on 2.2.2 on ubuntu but I can't even get nut 2.2.2 to work on my QNAP. (even after changing permissions on the USB device)

Once again thanks for your help!

  Is there anything else you can think of that I can try to get nut 2.2.2 working on my QNAP??

  From: Arnaud Quette 
  Sent: Wednesday, April 22, 2009 9:31 PM
  To: Greg ; Kjell Claesson 
  Cc: nut-upsuser at lists.alioth.debian.org 
  Subject: Re: [Nut-upsuser] Nut and PowerWare 5115

  Greg,

  I forgot to add that I'm interested in an upsc output of the working version (ubuntu 8.10 with 2.2.2...)

  Here you go
  =============================

  root at ubuntuvmp:~# upsc PowerWare at localhost
  ambient.temperature: 42
  battery.charge: 100
  battery.runtime: 2334
  battery.voltage: 13.47
  driver.name: bcmxcp_usb
  driver.parameter.pollinterval: 2
  driver.parameter.port: auto
  driver.version: 2.2.2
  driver.version.internal: 0.14
  input.frequency: 50.34
  input.voltage: 249
  output.current:  0.0
  output.frequency: 50.34
  output.phases: 1
  output.voltage: 249
  output.voltage.nominal: 240
  ups.firmware: Cont:01.00 Inve:10.04
  ups.load:  10.2
  ups.model: 51150500A           500VA
  ups.power.nominal: 500
  ups.serial: UY196A0229
  ups.status: OL

  =============================

everything is ok there.
I still fail to see anything that can result in the 2.4.1 issue you have.

  thanks (and sorry for top posting)
  Arnaud

  2009/4/22 Arnaud Quette <aquette.dev at gmail.com>

    Greg, Kjell,

    2009/4/21 Kjell Claesson <kjell.claesson at epost.tidanet.se> 

      tisdag 21 april 2009 14:43:28 skrev  Greg:
      > Hi Kjell,
      >
      Hi Greg,

      > Sorry for the late reply been doing a lot of testing.

      No problem.

      > I got the package from
      > http://ipkg.nslu2-linux.org/feeds/optware/cs05q3armel/cross/stable/nut_2.4.
      >1-1_arm.ipk It pretty much pre-compiled which are then extracted to the
      > device on installation.

      OK.

      >
      > I tested nut and the 5115 under Ubuntu 8.10. Ubuntu comes with nut 2.2.2 by
      > default which works fine. I installed 2.4.1 which does not work either.
      >

      This is not so good. Then we may have a bug introduced to the nut_usb.
      I cc this mail to Arnaud.
      Arnaud can you run some tests on the PW5115 with NUT 2.4.1 ?
      We may have broken something from version 2.2.2.

      But it may be the package also but I think Arnaud is working on that to.

    well, the packages (and ipk are iirc kinda simplified debs) are quite straighforward.
    the "nut" package (for example on Ubuntu) includes the core and the serial/usb drivers, with the udev file and so on. the hal support is in another packages that is conflicting with the "nut" one (in order to avoid runtime conflict between the classic and hal drivers).

      The error:

      > USB error: could not set config 1: Device or resource busy
      > Can't set POWERWARE USB configuration
      > Unable to find POWERWARE UPS device on USB bus

      Is indicating that something is already running.
      Did you check that the debug run was the only thing running at the moment.

    yup, 2nded.
    Greg: can you try again this test please.

    Yes it was the only thing running. I even restarted a few times and tried a few more times.

      > So I compiled and installed 2.2.2 on my QNAP device and it still doesn't
      > work.
      > 2.2.2 was compiled on my QNAP without HAL support just USB support.

      Yes, and I see that you get the same error as you get on 2.4.1 on the QNAP.

      The problem is that I don't have any 5115 to test this on. So I hope that
      Arnaud can test this. My PW3105 is running fine on usb on 2.4.1.

    I've just made some test on PW5115 500i (500VA), nut 2.4.1(-2 ; packaged) on an Ubuntu 8.10. Everything was fine. same goes for 2.2.2 (from source this time)
    the firmwares are:
    - USB: 01.00
    - Main:10.04

    This is the only 5115 I have underhand, but what is puzzling me is the exact model name:
    - mine (with 2.2.2) displays "Model = PW5115 500i         500VA"
    - while Greg's displays        "Model = 51150500A           500VA"

    a subtle difference! though the 2 firmwares (USB and main) are identical.
    iirc, this value (the name) can be changed. Have you done so Greg?

    I was unaware about changing the name of the UPS. I have not done this.

    I'm still learning PW, and will have to check with the PW people there.
    more info soon

    cheers,
    Arnaud
    -- 
    Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
    Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
    Debian Developer - http://www.debian.org
    Free Software Developer - http://arnaud.quette.free.fr/ 

Arnaud
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090428/b265b657/attachment-0001.htm>