similar to: Powerware Prestige 1000VA

Hello, does NUT support Powerware Prestige EXT 1000VA / PowerWorks A30 models in smart mode? I don't see them mentioned in the compatibility list (only Powerware 3115 and 5119 are there, listed as supported only by the "genericups" driver). Is the protocol known to be compatible with any other, supported UPS types? Thanks, Marek

Hi, I've got a Powerware Prestige 9 1kVA UPS that seems to not be working with nut. It's not in the current "supported hardware" list, but the old bcmxcp page lists it as being a UPS that speaks that protocol. I have the following in my ups.conf [powerware] driver = bcmxcp port = /dev/ttyS0 desc = "Powerware Prestige 9 EXT" baud_rate = 2400 And when I start the

(I saw this flipping through the archives for something else.) Marek, did the bcmxcp driver work for you or is your UPS too old? John

Looking for Powerware Prestige 9 Series 6000VA. If you know where I can buy one please respond. thanks!

---------- Forwarded message ---------- From: Tim Dawson <tadawson at tpcsvc.com> Date: Thu, Feb 13, 2014 at 12:07 AM Subject: Re: [Nut-upsuser] Powerware (Eaton) Prestige 9 UPS To: Charles Lepple <clepple at gmail.com> Charles - As a quick followup, the Prestige (both FW 2.13 and 3.09 - 2.x is pre-Eaton, 3.x post) reply to the topology block query thus: 3.064046

I noted some correspondence from several years back about supporting this device with bcmxcp, and the problems therein. Since I have one of these UPS units, still going strong, and the Eaton LanSafe stuff has finally caused me enough grief to abandon it, I figured I'd take a look at this. The issue is not that bad - the bcmxcp driver query of the topology block (2 bytes!) is returning

Hi there. At the moment I'm trying to get my HP T1500 XR (Powerware 5125) UPS to work with NUT. NUT registers that the UPS is on battery/online, but I just cant get the program to shut down the computer I'm using the original cable (thus I didn't enter anything in the ups.conf file) If I remove the cable and run the daemon/program the computer will shutdown after x minutes defined in

During the last month, I've been integrating a Powerware 5115 into an embedded system by writing a custom NUT daemon. This work has gone quite well and NUT has been very helpful, but it sure would be nice to have some additional instcmds for the 5115. The bcmxcp driver comments mention "manuals for the BCM/XCP". I'm wondering if I could get a copy of those so that I might

Hi. I'm looking for a way to configure an Eaton Powerware 5125 under Debian Squeeze (amd64) with USB port. Can someone help me? Find attached bellow my settings: # cat /etc/nut/ups.conf ... [ups01] driver = bcmxcp_usb port = /dev/bus/usb/002/003 desc = "Powerware 5125" # ls -la /dev/bus/usb/002/003 crw-rw-r-- 1 root nut 189, 130 Nov 21 11:45 /dev/bus/usb/002/003 #

Someone might want to add this to the docs - cable list and compatibility list - took me way to long to find. I was trying to find information on my UPS and came up with the following names for the same UPS series. Powerware 5119 Exide name was NetUPS SE Deltec name was PowerRite Pro II (1000VA-3000VA) What I have: The Exide NETUPS SE model PRC2400a p/n 05144038-3904 OUTPUT 2400VA 1600 WATTS

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

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

Ok, I installed the ups, and installed nut, and /proc/bus/usb/devices says this T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=06da ProdID=0002 Rev= 0.01 S: Manufacturer=POWERWARE S: Product=Powerware UPS C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 20mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00

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

I'm currently testing the bcmxcp driver for NUT, and it causes me some trouble. And when scanning the archives it seems like the 3110 USB problem reported recently. The bcmxcp daemon stops running, and the logs shows the following: Oct 6 14:22:32 host.dom.tld bcmxcp[82628]: Communications with UPS lost: Receive error (data): got -1 bytes instead of 28!!! Oct 6 14:22:33 host.dom.tld

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

I ordered some Powerware 3105 devices for Linux workstations. These devices only have an USB interface. I understood too late that support for Powerware devices is only available for the serial interface. Since the protocols over serial and USB seem to be identical, it was not too difficult to modify the bcmxcp driver to support USB. The new and changed files can be found here:

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

Hi all. As the subject has come up. Powerware ups may contain several cpu's and different firmware versions. Five of them is always ordered in a specific way. 1 control panel 2 inverter 3 rectifier 4 net interface card 5 display control So if a ups have a inverter cpu but not a control panel it sets the firmware revision to 00.00 to the control panel cpu, and get the version for the