similar to: NUT with Powerware 5125.

Hi, I've been getting emails from upsmon saying: Subject: UPS PW5125 at localhost notification: ONBATT UPS PW5125 at localhost on battery But then the machines on the UPS stay on for hours; we haven't got that kind of runtime, more like 10-20 minutes. After a few occurrences, it now happened at a time where I could log in to see in real time what is happening and: $ upsc PW5125 |

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

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

NUT 2.6.5 on FreeBSD 9.1 Why isn't the variable outlet.1.delay.shutdown set with the following command? # upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" outlet.1.delay.shutdown: -1 # upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost Enter new value for outlet.1.delay.shutdown: 10 OK # upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"

On Jun 29, 2013, at 9:45 AM, Mike. wrote: > On 6/29/2013 at 9:14 AM Mike. wrote: > > |NUT 2.6.5 on FreeBSD 9.1 > | > | > |Why isn't the variable outlet.1.delay.shutdown set with the following > |command? > | > | > | > |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" > |outlet.1.delay.shutdown: -1 > | > |# upsrw -u au -p ap -s

On 6/29/2013 at 9:14 AM Mike. wrote: |NUT 2.6.5 on FreeBSD 9.1 | | |Why isn't the variable outlet.1.delay.shutdown set with the following |command? | | | |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" |outlet.1.delay.shutdown: -1 | |# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost |Enter new value for outlet.1.delay.shutdown: 10 |OK | |# upsc PW5125

Hi all, Have a strange behaviour that I don't know how to debug. This is when I use the Eaton PW5125 ups. I have it connected And running in standby. Starting up the drivers (pw3105 and pw5125) and they run. Start up the upsd and can read info from both of them. The 3105 is supplying the computer and the 5125 have a dummy load. The 5125 is showing that it is off line. Now when I hit the on

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

Hello, I have a Powerware 5125 UPS and I don't know which driver I should use. In the compatibility list for the stable branch I see 2 sections for this model: 5119, 5125 - genericups upstype=15 PW5125 - bcmxcp Why are there 2 and which should I use? Thank you.

l?rdagen den 29 juni 2013 15.22.44 skrev Mike.: 8<-------------snip----------------- Sorry for the delay. > Here is the console output of bcmxcp with -DDD specified: > > > [snip] > 13.721204 Auto delay on: 2 > > 13.721243 send_command: (4 bytes) => ab 01 35 1f > 13.821127 send_command: (4 bytes) => ab 01 33 21 > 13.920982

l?rdagen den 29 juni 2013 11.28.14 skrev Mike.: 8<------------------snip--------------------- Hi Mike, > > Thanks for the quick reply. > > I checked the log file (which, admittedly, I should have done before I > posted about the problem :) ). > > Here's the command and the corresponding log message: > > # upsrw -u au -p ap -s outlet.1.delay.shutdown=12

On 6/29/2013 at 9:59 AM Charles Lepple wrote: |On Jun 29, 2013, at 9:45 AM, Mike. wrote: | |> On 6/29/2013 at 9:14 AM Mike. wrote: |> |> |NUT 2.6.5 on FreeBSD 9.1 |> | |> | |> |Why isn't the variable outlet.1.delay.shutdown set with the following |> |command? |> | |> | |> | |> |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" |>

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 #

On 6/29/2013 at 6:16 PM Kjell Claesson wrote: |l??rdagen den 29 juni 2013 11.28.14 skrev Mike.: |8<------------------snip--------------------- |Hi Mike, |> |> Thanks for the quick reply. |> |> I checked the log file (which, admittedly, I should have done before I |> posted about the problem :) ). |> |> Here's the command and the corresponding log message: |>

On Feb 20, 2017, at 11:19 AM, Mike <the.lists at mgm51.com> wrote: > > This UPS is already listed in the compatibility list. But I wanted to > add the instant commands supported by upscmd: > ... > and note that a delayed shutoff command is not available. > > (NUT 2.7.4 on OpenBSD 6.0) > > imo, it would be useful if this info were submitted along with the

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

On 2/21/2017 8:34 AM, Charles Lepple wrote: > On Feb 20, 2017, at 11:19 AM, Mike <the.lists at mgm51.com> wrote: >> >> This UPS is already listed in the compatibility list. But I wanted to >> add the instant commands supported by upscmd: >> > ... >> and note that a delayed shutoff command is not available. >> >> (NUT 2.7.4 on OpenBSD 6.0)

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

I made a mistake setting my shell and have set the root users shell to /bin/bash instead of /bin/sh. I am curiuos if anyone knows how to fix this. The machines is FreeBSD 4.8-RELEASE-p4 and does not have sudo only su.

I have setup nut-2.4.1 with the bcmxcp driver for my HP R3000 XR unit and although it appears to work, I receive the following sorts of errors in syslog: Aug 27 10:33:05 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (data): got 0 bytes instead of 64!!! Aug 27 10:33:15 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (data): got 0 bytes instead of 64!!! Aug 27