Displaying 20 results from an estimated 900 matches similar to: "Powerware Prestige 9 Series"
2014 Mar 01
3
Git - do I have the right repository?
On Feb 28, 2014, at 7:49 PM, Tim Dawson wrote:
> I just noted that I got my outputs reversed in my posting - the git version is the .26, with 2.7.1 being .28, which still seems odd . . .
The "-3857M" suffix on the "0.26 (2.6.5-3857M)" version was generated from SVN. Is it possible that the driver is left over from another package?
--
Charles Lepple
clepple at gmail
2014 Feb 02
2
Powerware (Eaton) Prestige 9 UPS
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
2014 Feb 13
2
Eaton Powerware 5110 - some stats not reported
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
2015 Sep 22
2
UPS/NUT with openSUSE 13.1
For fun, if you want to see where the system thinks it is linking a
library from, you can use "ldconfig -p" and it will give you a path to
all known libraries that it can find. If you have one loaded, and it
can't find it (odd directory, etc.) you can always amend
"LD_LIBRARY_PATH" the same way as PKG_CONFIG_PATH I mentioned earlier .
. . . PKG . . . is for the build
2015 Sep 22
2
UPS/NUT with openSUSE 13.1
Rob -
Just stepping in from the sidelines . . . with a few tidbits.
Nut uses pkgconfig to find and identify stuff as part of it's build . .
. So, depending on where your libusb install went, if it wasn't in the
default "PKG_CONFIG_PATH" setting, it won't be found. Much like other
shell variables, you can adjust that setting to find anything you like .
. .
IE
2014 Feb 13
0
Fwd: Powerware (Eaton) Prestige 9 UPS
---------- 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
2014 Feb 28
2
Git - do I have the right repository?
On Feb 28, 2014, at 1:05 PM, Tim Dawson wrote:
> Git:
>
> Network UPS Tools - BCMXCP UPS driver 0.28 (2.7.1)
> RS-232 communication subdriver 0.20
>
>
> 2.7.1:
>
> Network UPS Tools - BCMXCP UPS driver 0.26 (2.6.5-3857M)
> RS-232 communication subdriver 0.20
>
>
> I'm not so much noting the "2.6.5" in the dev, but the 0.28 vs 0.26 bcmxcp
2006 Sep 19
2
help w/ Powerware Prestige 9
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
2007 May 19
1
Powerware Prestige 1000VA
Hi all,
I've more-or-less got NUT 2.0.4 working with my Powerware Prestige
1000VA UPS (serial), but unfortunately NUT is flagging LOW_BATTERY
continuously, which is a tad embarrassing when power fails ;-)
The numbers from upsc blah at localhost seem reasonable:
ambient.temperature: 24.5
battery.charge: 99
battery.runtime: 3999
battery.voltage: 69.2
driver.name: bcmxcp
2005 Sep 20
1
Powerware Prestige EXT 1000VA / PowerWorks A30 support?
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
2014 Feb 13
0
Eaton Powerware 5110 - some stats not reported
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
2014 Feb 13
2
Eaton Powerware 5110 - some stats not reported
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
2014 Feb 15
0
Eaton Powerware 5110 - some stats not reported
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
2006 May 29
0
Powerware Prestige EXT 1000VA / PowerWorks A30 support?
(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
2015 Sep 21
3
UPS/NUT with openSUSE 13.1
On Sep 21, 2015, at 9:39 AM, Rob Groner <rgroner at RTD.com> wrote:
>
> I didn't think to look for a log (attached), but now looking in it, I don't see anything more than I already thought I knew. It's as cryptic as configure itself.
>
> It does reference the line in the configure where the test for USB failed, but I'd already been looking in there. I
2014 Feb 28
0
Git - do I have the right repository?
Question: I just uploaded the git development repository, and upon
building it, I note that on the bcmxcp driver, it would appear that the
git tree is actually older than what is in the 2.7.1 release:
Git:
Network UPS Tools - BCMXCP UPS driver 0.28 (2.7.1)
RS-232 communication subdriver 0.20
2.7.1:
Network UPS Tools - BCMXCP UPS driver 0.26 (2.6.5-3857M)
RS-232 communication subdriver 0.20
2014 Mar 06
5
Developing the UPS side of the UPS-NUT equation (via usbhid)
My company is developing a new UPS, with smarts provided by a PIC32 Microchip micro-controller. The controller comes with a demo for a USBHID-UPS, and after some tweaking, I was able to get NUT to recognize it and start showing some reasonable values.
To make this UPS as easy to use as possible for the end-user who chooses Linux, I figured I would just completely implement the official USB HID
2014 Feb 16
0
Eaton Powerware 5110 - some stats not reported
On Feb 15, 2014, at 6:46 PM, Greg Vickers wrote:
> Thanks! I've attached the file to this email (bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like it's looping by that time. I'm not sure what to look for, does grepping for 'Yes' show the variables that the driver can pull off this UPS?
The boolean variables seem to be indicated by "Yes". I
2002 Dec 13
2
Stumped at "Network Neighbourhood", Samba server is visible, but it's path can't be found ...
Hi all,
I can see the RH7.3 linux box I've configured with the latest
Redhat RPM samba package in the Windows 2000 network
neighbourhood, but when I double click the W2000 computer
icon I get the message
"\\Linuxbox is not accessible,
The network path was not found."
The network is a small switched lan, sadly with only one unix
box (RH7.3) and a mixture of Windows2000 and 98
2014 Feb 16
1
Eaton Powerware 5110 - some stats not reported
The meter map is basically a bitmap that indicates what variables are output (and in what format) by the UPS. You will likely see a variable, 'not mapped' or nothing. The variables and 'not mapped' items are output by the UPS in the measurement block, and the map tells nut how to read it. 'Unmapped' means that there is a variable there that nut is ignoring, and the xcp