similar to: New UPS supported in 2.0.4

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

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

Using the HOWTO in http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ I installed nut on an Ubuntu Edgy LAMP Server with an Eaton Powerware 5110 attached to it via usb. But nut fails to start properly (see the error message "Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon" below). It then complains about communication with the UPS being lost ("UPS

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

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

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

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

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

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

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

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

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

Has anyone had any success with the HP T/R2200 G2? I have used the T/R2200 with nut a few times before and it works great, but the G2 doesn't want to talk to me. I have tried bcmxcp from 2.0.4, 2.2.2, and svn, as well as the usb drivers. Maybe the G2 isn't a rebadged powerware unit? Thanks James

Has anyone had any success with the HP T/R2200 G2? I have used the T/R2200 with nut a few times before and it works great, but the G2 doesn't want to talk to me. I have tried bcmxcp from 2.0.4, 2.2.2, and svn, as well as the usb drivers. Maybe the G2 isn't a rebadged powerware unit? Thanks James

> 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