similar to: Is "eaton 5115 UPS" compatible with NUT

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

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

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

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

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

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

Hello, I 'm trying to set up an Eaton PW5110 using nut-2.4.1 in OpenBSD, my ups.conf follows : [myups] driver = bcmxcp_usb port = auto desc = "Eaton PW 5110 (1500VA)" My first attempt to run upsdrvctl ended up complaining about unimplemented usb_clear_halt() in libusb. I patched libusb-0.1.12 with the following patch :

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

Hi, just wanted to provide a upsc dump for an Eaton/Powerware 5115 rack mount unit. This was on a CentOS 7.3 machine with following packages installed: nut-client-2.7.2-3.el7.x86_64 nut-2.7.2-3.el7.x86_64 nut-cgi-2.7.2-3.el7.x86_64 $ upsc eaton5115 ambient.temperature: 43 ambient.temperature.high: 75 battery.charge: 100 battery.runtime: 24171 battery.voltage: 40.96 device.mfr: Eaton

> 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

On 16/02/14 00:38, Charles Lepple wrote: > 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 loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. > Tim: spot on. > > Greg, > > If you want, you can capture the -DDDD output

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

I like to think of myself as reasonably intelligent when it comes to systems (MS in Comp Sci, albeit a few hundred moons ago), but I seem to be missing something when it comes to installing NUT on a 64 bit windows XP system. I downloaded and attempted it install but the installer said I needed to install libusb manually. So I went and grabbed that, unpacked the ZIP file and ran the

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

On Dec 17, 2013, at 12:45 PM, Bruce Bowler wrote: > upsdrvctl stop and start don't complain... > > ------------ > C:\Program Files (x86)\NUT\bin>upsdrvctl stop > Network UPS Tools - UPS driver controller 2.6.5-3723:3731M > > C:\Program Files (x86)\NUT\bin>upsdrvctl start > Network UPS Tools - UPS driver controller 2.6.5-3723:3731M > > C:\Program Files

I've got some strange problem with NUT on my 5115 on Debian Etch: ---snip--- $ sudo ./bcmxcp_usb -DDDDDDD -a 5115 Network UPS Tools - BCMXCP UPS driver 0.13 (2.3.0-1181) Warning: This is an experimental driver. Some features may not function correctly. debug level is '7' Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus Things to try: -

I am seeing some problems when using the Powerware 5115 UPS when connected to the Patsburg USB controller and would like to know if anyone has a solution. The symptom is that PING messages sent to the bcmxcp_usb driver take as long as 25 seconds to complete. The configuration is a Romley patform (a.k.a., Sandy Bridge + Patsburg) running Debian 6 with 2.6.39 kernel with NUT 2.6.4 in which the

Good evening, I tried getting this to work a couple years back but didn't have enough time to do all the debugging that was needed (apologies to the devs who tried to help at that time). It's working much better now, but I'm still not able to get an answer from upsc. Can anyone help me work out why I'm getting the error when querying with upsc: Error: Data stale My