similar to: bcmxcp_usb offers no runtime or serial # with a Powerware 5110/700va

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 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.

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

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 got a Powerware 5110 UPS which has a usb interface on it. I have downloaded and compiled nut-2.0.3-pre2 with the usb drivers enabled on RedHat Enterprise V3 however I have been unable to get nut to connect to the UPS. I have tried executing the driver directly (using bcmxcp_usb -DD -u root /proc/bus/usb/002/002) as well as using upsdrvctl with the port set to auto (am I correct in

Hi, I have an UPS Powerware 5110 ( usb connection ), on Linux OS is Debian 4.0 The /etc/ups.conf file setting is: [myups] driver = bcmxcp_usb port = auto desc = "UPS Powerware 5110 1500 VA" When the daemon starts it displays the following message: "Starting Network UPS Tools: (upsdrvctl failed)." Looking at /var/log/syslog I found the following line

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 =

I tried switching to the USB version of bcmxcp_usb and get this error when I try starting up upsdrvctl or bcmxcp_usb like so: /etc/nut/bcmxcp_usb -DDDD -a powerware -u nut I used this for ups.conf: [powerware] driver = bcmxcp_usb port = auto With the serial/usb dongle, I used this successfully: [powerware] driver = bcmxcp port = /dev/ttyUSB0 What devices does

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

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 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 Greg, Thomas and the list, I've not forgotten you nor your issue. It just took some time to gather a "faulty" unit and a bit of time to reproduce your issue. The good news is that I've commited a fix to the NUT development branch (aka Subversion), in the release r2015. The bad news is that your test and feedback is welcome ;-) For more info on getting and compiling the

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

Greetings, The way that bcmxcp_usb reacts to and recovers from a USB cable unplug-plug appears to have changed significantly between 2.4.1 and 2.6.0. While I can see some improvements, bcmxcp_usb 2.6.0 does not appear to handle a USB cable unplug-plug correctly. Does anyone know if this has been fixed in subsequent releases? Here are the details. When the USB cable between my server and my

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

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, 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