similar to: [HCL] Powerware PW5125 with driver bcmxcp

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)

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

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

I've patched bcmxcp.c such that it can power cycle the outlet load segments independently on a Powerware PW5125 UPS. I presume that it will work for any XCP protocol UPS with 2 load segments. Should these instant commands be called outlet.1.shutdown.return outlet.2.shutdown.return ? Where do the descriptions displayed by upscmd -l come from? Presently it shows outlet.1.shutdown.return -

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

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

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

Hi, I'd like to inform You that this UPS communicates well via the serial port. I haven't tested USB, and no shutdown testing so far, however, I hope it will run well. HP R5000 upsc output: ambient.temperature: 27.4 ambient.temperature.high: 45 battery.charge: 99.0 battery.runtime: 536 battery.voltage: 236.3 device.mfr: Eaton device.model: HP R5000 5000i device.serial: 3C81520083

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

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

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 Fri, Sep 11, 2020, at 4:05 PM, Bartosz wrote: > Dear All, > > Could you please recommend me a UPS with 100% support of the ondelay parameter and NUT compatibility? > > 850 or 1000 VA > > I have the EATON 5E850iUSBDIN UPS and it does not support this parameter so I would like to buy another UPS that for sure will support it. > > Thank you, > Bart Can you tell

Jim Klimov <jimklimov+nut at gmail.com> > > I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

Jim Klimov <jimklimov+nut at gmail.com> > > I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

I have a brand new Eaton 5E UPS purchased in Australia. Details: Eaton 5E Model: 5E650iUSB-AU Date: best I can find is the shipping date to supplier on box label - May 2014 OS: Ubuntu 14.04 Server edition Nut 2.7.1 Installed via apt-get install nut I have two problems I would like to fix. First the beeper is annoying and loud and I worry it will wake everyone up at night. I read that you can

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

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> > > Got an update for APC Modbus users: a new PR is waiting for real-life testing for settable variables and instant commands support. > > https://github.com/networkupstools/nut/pull/2184 > > As before, a custom build of libmodbus may be needed for USB support (detailed in the earlier PR), but Serial and