Displaying 20 results from an estimated 1000 matches similar to: "Powerware 5125 works ?"
2013 Feb 21
1
NUT with Powerware 5125.
Hi,
Does anyone know how to make NUT works with Powerware 5125?
I already tried serial communication (genericups and bcmxcp) and USB
(usbhid-ups and bcmxcp_usb), but without success.
I'm using the latest version of NUT (2.6.5) under Debian amd64.
Can anyone help me?
Thanks.
Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2005 Nov 11
2
Powerware 9125 - bcmxcp - shutdown problem
Hi,
just through setting up nut-2.0.2 I ran into a shutdown problem. As I have
already spend some time on it and don't know any further, I like to ask for
advice.
Situation:
Powerware 9125 serially connected using /dev/cua0
nut compiled and installed fine
system shall
- broadcast a message and shut down if ups on battery for 30+ s
- wait 120 s
- broadcast another message
- give system 120
2007 Nov 30
1
powerware 5125 and bcmxcp driver
I'm trying to get a Powerware 5125 UPS running using the bcmxcp driver,
but I get the following errors:
video2:~# /sbin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.0.4
Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4)
Communications with UPS lost: Error executing command
Communications with UPS lost: Error executing command
Communications with UPS lost: Error executing
2006 Oct 16
1
bcmxcp_usb offers no runtime or serial # with a Powerware 5110/700va
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
2007 Feb 03
2
Powerware 5110
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
2017 Feb 20
2
[HCL] Powerware PW5125 with driver bcmxcp
This UPS is already listed in the compatibility list. But I wanted to
add the instant commands supported by upscmd:
============================
Instant commands supported on UPS [PW5125]:
beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily mute the UPS beeper
load.on - Turn on the load immediately
outlet.1.load.off - Turn off the load on
2007 Jul 25
3
Nut fsd command ignored: bcmxcp_usb driver, Powerware 5105 UPS
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
2012 Nov 21
2
Powerware 5125 (USB) under Debian Squeeze.
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
#
2006 May 09
3
Eaton Powerware 5110 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.
2013 Sep 19
0
UPS compatibility list
Luke-Jr wrote, On 9/18/2013 1:02 PM:
> I wanted to suggest some rating for functionality. I got the UPS available
> that seemed to have the best possible rating from NUT's list (Eaton Powerware
> UPS 1500), and found out it doesn't support telling me battery level or
> runtime! :/
I'm avoiding Eaton/Powerware because the lack of usbhid support, the
bcmxcp driver
2013 Aug 08
0
HP R1500 G3 problems
=?ISO-8859-1?Q?Alf_H=F8gemark?= <alf at i100.no> writes:
> I am working on improving the bcmxcp driver, to add more data reported
> from the driver, and also add support for sending more commands to the ups.
> The code changes are currently not part of any release, but they are in
> github, and some more are on the way.
> Would you be able to do some testing on your HP R3000
2013 Jul 02
2
bcmxcp: Patch for adding ups.load and battery.voltage.low
Hi
I have the following UPS :
ups.mfr: Eaton
ups.model: POWERWARE UPS 500i
ups.power.nominal: 500
It is using the bcmxcp_usb driver.
I started the driver with debug options, and noticed the following for
the meter map :
0.475625 0027 0000 51 output.frequency
0.475634 0028 0004 51 input.frequency
0.475641 0033 0008 51 battery.voltage
2008 Dec 23
2
Exide NetUPS SE (aka Powerware 5119 etc)
My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as
Powerware 5119, according to Karl Schmidt
(http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html)
also Deltec PowerRite Pro II, and according to
http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not
sure if the information in http://www.bps.hu/powerware/model_en.html
is to be interpreted as that it was
2008 Dec 23
2
Exide NetUPS SE (aka Powerware 5119 etc)
My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as
Powerware 5119, according to Karl Schmidt
(http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html)
also Deltec PowerRite Pro II, and according to
http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not
sure if the information in http://www.bps.hu/powerware/model_en.html
is to be interpreted as that it was
2013 Sep 18
5
UPS compatibility list
I wanted to suggest some rating for functionality. I got the UPS available
that seemed to have the best possible rating from NUT's list (Eaton Powerware
UPS 1500), and found out it doesn't support telling me battery level or
runtime! :/
Luke
2008 Sep 19
1
Powerware9120 not shutting down the UPS
Hi all
I'm busy testing the Powerware9120 and am stuck at the powering down of
the UPS.
I'm running the latest Debian Lenny and here is my versions
Network UPS Tools - UPS driver controller 2.2.2
Network UPS Tools - BCMXCP UPS driver 0.14 (2.2.2)
ups.conf
[pw]
driver = bcmxcp_usb
port = auto
shutdown_delay = 60
I get all the correct info from the UPS and NUT works great and
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
2014 Feb 26
3
Powerware Prestige 9 Series
Looking for Powerware Prestige 9 Series 6000VA. If you know where I can
buy one please respond. thanks!
2009 Sep 21
4
Powerware 5115 USB Issue
Hi,
I'm trying to get a Powerware 5115 to communicate with the NUT via USB under Debian Linux and need help.
Here is the output that I see.
co-nh5:/tmp/mnt/projects/pwusb/nut-2.4.1# /usr/local/ups/bin/upsdrvctl -u root start
Network UPS Tools - UPS driver controller 2.4.1
Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1)
USB communication subdriver 0.17
Communications with UPS lost:
2005 Oct 09
3
bcmxcp - Powerware 9125
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