similar to: trying to use powerware 3110 USB with NUT

I ordered some Powerware 3105 devices for Linux workstations. These devices only have an USB interface. I understood too late that support for Powerware devices is only available for the serial interface. Since the protocols over serial and USB seem to be identical, it was not too difficult to modify the bcmxcp driver to support USB. The new and changed files can be found here:

Hi Arnaud, Any luck with the latest subversion trunk? From: Greg Sent: Wednesday, May 13, 2009 10:34 PM To: Greg ; Arnaud Quette Cc: Kjell Claesson ; nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Arnaud, Some more testing on Ubuntu 9.04. Here is the output of bcmxcp_usb and lsusb ============================================ root at

I decided to try this to see if it worked better since Powerware decided to build in some oddball USB protocol instead of using a HID UPS profile, but it doesn't seem to work. The USB/serial dongle is recognized by Linux and added as /dev/ttyUSB0, owned by group "dialout", so I had to add the nut user to the dialout group. In the compatibility list, the proper driver for the

Hi, I recently downgraded my kernel to 2.4 series (2.4.32-rc2). Now I can't get nut running. It was fine with 2.6.14. It say's: --------------------- # ./bcmxcp_usb -uroot AUTO Network UPS Tools - BCMXCP UPS driver 0.10 (2.1.0) Can't reset POWERWARE USB endpoint Unable to find POWERWARE UPS device on USB bus ... --------------------- I've straced it in nut_usb.c

Hello, ppl! I try configure NUT for communicate with my Powerware 5115 UPS. As root I run '/lib/nut/bcmxcp_usb -DDDD -u root -a ups', but driver can't connect to my UPS. Some output: Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) debug level is '4' usb_set_debug: Setting debugging level to 3 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 001

Hi. Have back-ported the bcmxcp and bcmxcp_usb driver from Development. I hope it's done right. Tested a clean cvs fetch after commit and it build and install ok. Regards Kjell

Kjell Claesson wrote: > Then i have a problem. My computer is down due to a > faulty mainboard, Youch. I hate it when that heppens. Hope it wasn't because you got a power spike ;-) Let me or Georg know if you want us to run any debug code. Feels like a bcmxcp_usb driver bug to me since the bcmcxp serial driver works fine and all my other USB devices work fine (wifi adapter, memory

On 5/23/07, Kjell Claesson <keyson-guest at alioth.debian.org> wrote: > Author: keyson-guest > Date: Wed May 23 21:12:51 2007 > New Revision: 915 > > Log: > - Enabled requested Alarm function in bcmxcp.c > > Modified: > trunk/ChangeLog > trunk/drivers/bcmxcp.c Looks like this breaks when HAL is enabled. At the end of:

Hello... I have a PowerWare 9120 attached via USB to my Debian system. My ups.conf looks like this: [ups1] driver = bcmxcp_usb port = auto desc = "PowerWare 9120" When testing the driver with "upsdrvctl -u root start" I get: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS

Are there driver to this device it works? I trie with 9130 and 9140 driver but didn't work. Thanks Ignacio Fridemberg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20121025/af016ac1/attachment.html>

Citeren Kjell Claesson <keyson-guest op alioth.debian.org>: > Author: keyson-guest > Date: Mon Mar 23 17:37:37 2009 > New Revision: 1817 > > Log: > data/driver.list, add Eaton Powerware 9130 compatibility with bcmxcp > and usbhid-ups. 1) Is this really true? I would have expected that this device would be supported through bcmxcp (serial) and bcmxcp_usb (USB), like

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

Hi I have the following UPS : ups.mfr: Eaton ups.model: POWERWARE UPS 500i ups.power.nominal: 500 It is using the bcmxcp_usb driver. I started the driver with debug options, and noticed the following for the meter map : 0.475625 0027 0000 51 output.frequency 0.475634 0028 0004 51 input.frequency 0.475641 0033 0008 51 battery.voltage

Hello: I have a UPS model MXE II MAXIM brand online, 3500VA 2100W. Connects to the PC by a USB 2.0 port. I wanted to use nut, but this brand is not on the list of nut drivers. lsusb returns: ... Bus 003 Device 003: ID 06DA: 0201 Phoenixtec Power Co., Ltd ... I did not find this manufacturer in the driver list. Anyone know if you can have compatibility with other make and model of UPS. With

Following the instructions a following site I can not get nut to work with my UPS. http://bernaerts.dyndns.org/linux/75-debian/335-debian-wheezy-install-monitor-eaton-ups Hope that you can find out what is wrong by the provided info in the email Best Regards, Magnus Karlsson # lsusb -s 001:005 -v Bus 001 Device 005: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Device Descriptor: bLength

Adam: Thanks for putting up this page. But something is wrong. In particular, our Powerware 9135 is a three phase UPS system with THREE 480 volt outputs. So the displayed voltage is not correct -- in fact there should really be THREE voltages displayed, all around 480v. Nut developers: I am copying the NUT mailing list to see if anyone can suggest how to fix this. NUT developers, see the

Hi I set up my ups with driver snmp-ups, and it get recognized as a AEC T2003. In the nut-cgi upstats page input/output/load are displayed corectly, but the Status field is marked as "Not supported". Is "Status" important to initiate shutdown in case of low battery ? Will my server shut down correctly ? thanks Massimo I include "upsc snmp@localhost" output:

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

Hi, Made a test build of the Testing branch. The problem is that upsmon and upsc is not respecting the revision change of libupsclient.so. It is now libupsclient.so.1, but i get this. /usr/sbin/upsmon: error while loading shared libraries: libupsclient.so.0: cannot open shared object file: No such file or directory and: upsc: error while loading shared libraries: libupsclient.so.0: cannot

Hi, I have an HP R5500XR and a Compaq R3000XR that I would like to use with nut. I searched the compatibility lists and the mail list archives but couldn't find anything. They both have 9 pin serial ports. Can anyone give me any information about them, and if they are supported by nut? Thanks, Denny Fox