similar to: Powerware 5110 UPS with nut in Ubuntu

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

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

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

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

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

Luke-Jr wrote, On 9/18/2013 1:02 PM: > I wanted to suggest some rating for functionality. I got the UPS available > that seemed to have the best possible rating from NUT's list (Eaton Powerware > UPS 1500), and found out it doesn't support telling me battery level or > runtime! :/ I'm avoiding Eaton/Powerware because the lack of usbhid support, the bcmxcp driver

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

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

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

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

I wanted to suggest some rating for functionality. I got the UPS available that seemed to have the best possible rating from NUT's list (Eaton Powerware UPS 1500), and found out it doesn't support telling me battery level or runtime! :/ Luke

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, Been searching like crazy to find an answer to this. I have even read some of the source code but cannot figure this one out. I have installed nut 2.4.1 on my QNAP 409 Pro. (command: ipkg install nut) I have configured the ups.conf, upsd.conf and upsd.users. When i run "upsdrvctl start" I get the following error messages and output.

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

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