similar to: Driver not found for Powerware 5110

2009/8/28 Thomas Zulliger <Thomas.Zulliger at quiksilver.com.au> > Hi Arnaud > Hi Thomas, > I'm experiencing exactly the same problem > > DNS-323 fun_plug Fonz > nut 2.4.1-1.tgz > powerware 3105 > using BCMXCP_usb > > /mnt/HD_a2/packages # lsusb > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 002: ID 0592:0002 Powerware Corp. > Bus 001

Hi, I'm trying to get a Powerware 3105 UPS working on SuSE 10.0. I have compiled nut from the current Subversion repository. This UPS uses the bcmxcp_usb driver. I cannot get the driver to find the ups on the USB bus. The error message I get is:- -------------- bcmxcp_usb -u nut -DDDDD -a pw3105 -------------------- Network UPS Tools - BCMXCP UPS driver 0.10 (2.1.0) debug level is

Hi everyone, First of all a big thank you for the NUT package, I've been using it for years and couldn't get by without it! I have two Powerware UPS's here, a 9120/1500va and a 5110/700va. The 9120 has used a hacked bcmxcp driver (serial) from the 2.0.2 nut version for about a year now (which I'll explain more about in a seperate email to the dev list), and the 5110 which I just

Hi I'm having a problem with the bcmxcp_usb driver FSD command: everything seems to work apart from: upsmon -c fsd Environment: Ubuntu 7.04, nut 2.0.5-1, nut-usb 2.0.5-1, Powerware 3105 UPS. upsd appears to send the FSD command to the UPS, upsmon then runs my NOTIFYCMD (which halts my PC) but the UPS just doesn't turn off. Here are the /var/log/daemon.log entries: Jul 24 23:13:16

Hi I have PW 5115 500 UPS which has both RS232 and USB connectors. bcmxcp driver works fine with serial connection but bcmxcp_usb does not with USB one. After some USB sniffing on windows box I've found that PW5115 communicates in other way than supposed in driver. Applying attached patch makes driver to work properly. System: FreeBSD 6.2 but ugen driver needs patching in order to respect

On 13/02/14 12:16, Charles Lepple wrote: > On Feb 12, 2014, at 7:50 PM, Tim Dawson wrote: > >> Run the driver with -DDDDD and see what variables it picks up. I have noted that with the Prestige 9 in bcmxcp, some variables are not consistent within models, and had to do some gentle remapping to get things to work correctly. I ran the new driver (see below) and with -DDDD it throws out

On Feb 12, 2014, at 7:50 PM, Tim Dawson wrote: > Run the driver with -DDDDD and see what variables it picks up. I have noted that with the Prestige 9 in bcmxcp, some variables are not consistent within models, and had to do some gentle remapping to get things to work correctly. Tim, is this the issue you mentioned on 2014-02-02 with blocks 0x9 and 0x13? I'll reply to that email. > On

Hi all, I've hooked up an Eaton Powerware 5110 to Ubuntu 13.10 server, and configured nut appropriately. The cgi scripts are working fine, but on upsstats.cgi, the Batter, UPS Temp and Battery Runtime fields are all blank - and there are no entries for these values in the 'All data' tree. I've checked the man page for bcmxcp_usb

Hi all, I've got a Powerware 5110 UPS that I'm trying to set up with nut in Ubuntu. I've installed nut and configured the first two files: $ cat /etc/nut/nut.conf MODE=standalone $ cat /etc/nut/ups.conf [pw5110] driver = bcmxcp_usb port = auto # port = /dev/bus/usb/002/002 When I try to test this configuration with the following command: $ sudo upsdrvctl start pw5110 Network UPS

Hi, I am wanting to use NUT to connect to an Eaton Powerware 5110 UPS using USB to connect. - I am using NUT 2.0.2 - I have compiled it with USB support - I can see that the UPS is registered as connecting in /var/log/messages eg usb 3-1: USB disconnect, address 3 usb 3-2: new low speed USB device using uhci_hcd and address 4 But I don't know how to progress from here.

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

This is just to let the list know that I have had success getting my FC3 system talking to my USB PW3105. I used nut 2.0.3 and recompiled from source so as to get the bcmxcp_usb driver. After that it was just a matter of following the (very good) INSTALL instructions provided in the tarball. Although I haven't got the hotplug scripts working yet (the samples provided are not a good fit on a

Hi Does there exist any work on getting the powerware driver to work with USB devices under freebsd? I have tryed with the usb enabled newhidups driver for freebsd but it does not seem to work. $ newhidups -a newhid -DD Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2) debug level is '2' found 0 (-1) No USB/HID UPS found //erlis -------------- next part -------------- An HTML

Hi, I have set up a RaspberryPi computer to do monitoring of two UPSs. One is an MGE evolution 800, one is an Eaton Powerware 5110. The MGE was being monitored by another Linux (Ubuntu 12.04) computer, and I just copied and pasted in the relevant nut config and it works just fine with nut. I've tried to set up the Powerware 5110 with nut, and the bcmxcp_usb driver can't communicate

Hi, OS: FreeBSD 9.0-RELEASE NUT version: nut-2.6.5_1 (installed from ports) UPS: Eaton powerware 5110 Can you help me with this device, please? [root at mail /usr/local/etc/nut]# /usr/local/libexec/nut/usbhid-ups -DDDD -a eaton Network UPS Tools - Generic HID driver 0.37 (2.6.5) USB communication driver 0.31 0.000000 debug level is '4' 0.001239 upsdrv_initups... 0.001958

The driver will poll the UPS for what variables it supports when it starts, and then go into a polling loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. You can get the comm spec for XCP from the nut site if you want to delve deeper. I'd give more specifics, but am out of town and only working from memory at the moment . . . - Tim On

Hi, I'm having trouble with nut running on feisty. I have a powerware 5110 connected using USB i did an "sudo lsusb -a" before and after i plugged in the powerware usb cable and did a diff on the results of the two which was: -- 322c322 < Port 2: 0000.0100 power --- > Port 2: 0001.0301 C_CONNECT lowspeed power connect -- current ups.conf is: -- [pw5110] driver =

> On February 14, 2014 11:22:22 PM CST, Greg Vickers <daehenoc at iinet.net.au> wrote: >> I ran the new driver (see below) and with -DDDD it throws out tons of >> never ending information, what am I looking for? :) > On Feb 15, 2014, at 2:57 AM, Tim Dawson wrote: > The driver will poll the UPS for what variables it supports when it starts, and then go into a polling

Nut for Windows 2.6.3-3 + Eaton/PW 5110 (103004256-5591). I had to manually install libusb driver and I'm using bcmxcp_usb. upsd.exe is reporting to me "Out of memory". It will run, but once anything connects to the daemon, it dies with that message. I don't have much experience with NUT yet so I'm not sure what the next course of action is. I do have NUT for Windows

Dear Nutters, I am trying to get NUT as supplied with SuSE 10.1 working and I think I have a USB problem, possibly due to some missing startup scripts concerning permissions. The machine sees the USB device as per /var/log/messages: Jun 5 16:28:27 silver-server kernel: usb 2-1: new low speed USB device using uhci_hcd and address 7 Jun 5 16:28:27 silver-server kernel: usb 2-1: new device