similar to: Eaton PowerWare 9120 3000i

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]

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

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 On 02/12/2014 06:46 PM, Greg Vickers wrote: > Hi all, > > I've hooked up an Eaton Powerware 5110 to Ubuntu 13.10 server, and > configured nut

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 just acquired a new UPS and have been trying to get it to work with NUT. It's an Eaton/Powerware 9120 700i with both USB and RS-232 interfaces. I first tried the USB interface (using bcmxcp_usb) and found that the UPS worked fine for a few minutes but then NUT lost communication and didn't get it back. In addition the UPS itself seemed to lock up at one point such that the

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

Has anyone gotten the newhidups driver to work w/ the Powerware 9120 series? Here's what I get for debug info (It's the Phoenixtec device): $ sudo lsusb Bus 002 Device 002: ID 0846:1040 NetGear, Inc. Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 06da:0002 Phoenixtec Power Co., Ltd Bus 001 Device 001: ID 0000:0000 $sudo /lib/nut/newhidups -DDDDD auto Network UPS Tools: New

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

Hi On http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_5110 you can see what is reported. The unreleased part refers to v2.7.1, which is now released. Alf Greg Vickers <daehenoc at iinet.net.au>: >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

Hi, I want to test the events off my UPS. I define In upsmon.conf: RUN_AS_USER root NOTIFYCMD /sbin/upssched NOTIFYMSG ONLINE "UPS %s on line power" NOTIFYMSG ONBATT "UPS %s on battery" NOTIFYMSG LOWBATT "UPS %s battery is low" # NOTIFYMSG FSD "UPS %s: forced shutdown in progress" NOTIFYMSG COMMOK "Communications with UPS %s established"

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

A couple of different issues with the reporting script. First the password masking is not working as intended: I have three different passwords in my ups.users file and only the last one is masked. Here's the first part of the resulting report where I've replaced the unmasked passwords with <PASSWORD-n>. NUT configuration 2019-07-14 16:58:15 UTC ###########

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'm running a single "nut-server" that monitors seven ups units. In upsmon.conf: MONITOR ups-1 0 <User> <Pw> master MONITOR ups-2 0 <User> <Pw> master MONITOR ups-3 0 <User> <Pw> master MONITOR ups-4 0 <User> <Pw> master MONITOR ups-5 1 <User> <Pw> master MONITOR ups-6 1 <User> <Pw> master MONITOR

> What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines when to shut down. > > Also, if you don't want to wait for both UPSes to drain to the low battery state, you can set up a pair of dummy-ups drivers. I'm

There's supposedly another way with a custom upsmon.conf: NOTIFYMSG type message upsmon comes with a set of stock messages for various events. You can change them if you like. NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "Someone pulled the plug on %s" Note that %s is replaced with the identifier of the UPS in question. The message must be one

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was

Was /etc/nut/upssched-cmd automatically installed? I don't have it on my raspberry pi. :-( On 2019-04-03 1:54 p.m., Mike wrote: > I figured this out and it is working now.  This fix seems strange to me > and is possibly a bug.  I'm sharing in case it might help others. > > I had to uncomment all of the NOTIFYFLAG statements whether I was > changing them or not.