similar to: communication problems with eaton 9130 over usb

Hi, I have successfully configured Nut to work with EATON PS 650: system detects low battery, initiates shutdown, waits for UPS to switch power off. However, when power is restored, UPS immediately powers on all power plugs independently from ups.timer.start setting. upsc reports "ups.timer.start" variable availability which is set to 0. upsrw reports "ups.delay.start"

Here is a Compatibility Report for the Eaton Ellipse ECO 1600 UPS. Roger battery.charge: 100 battery.charge.low: 20 battery.runtime: 1575 battery.type: PbAc device.mfr: EATON device.model: Ellipse ECO 1600 device.serial: 000000000 device.type: ups driver.name: usbhid-ups driver.parameter.lowbatt: 37 driver.parameter.offdelay: 30 driver.parameter.ondelay: 40 driver.parameter.pollfreq: 30

Hello Niels, thanks a lot for this compatibility submission. This is part of the remaining things at Eaton. I've added an entry to the new Hardware Compatibility List: http://new.networkupstools.org/stable-hcl.html BTW, have you tested a shutdown with this unit? Otherwise, you should! thanks again, Arnaud Quette Le samedi 02 octobre 2010 ? 12:42 +0200, Niels Kristian Jensen a ?crit :

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

Hello Charles, I've attached a dump below. There were no long entries on any of the hosts, neither the one running standalone, nor the master/slave combo, which is not too surprising, it was really fast: I saw the light flickering in the room, almost like flash, and all those 3 systems went down. I first heard the "click" of the ports being disabled, heard the systems shut down, and

Hey Charles, Latest update. Looks like in ups.conf I setup default.input.transfer.low = 84. After I took that line out, restart upsdrvctl, upsmon, and upsd, the command of sudo upsrw -s input.transfer.low=70 -u * -p * ups return OK. Still need to verify if it works by using voltage regulator and will keep you updated. Thank you for your help Regards Shen On Thu, Jun 5, 2014 at 8:54 AM,

Hey Charles, Looks like after take out default.input.transfer.low, upsrw script *DOES* work, the only thing for Eaton 3S 500 is that it is only accept certain voltage values for input.transfer.low, 84v and 96v are two of them. Otherwise the value never gets picked up. Thank you for all your help Shen On Thu, Jun 5, 2014 at 12:07 PM, Shen Chuan <shen at minutekey.com> wrote: > Hey

OS version: FreeBSD 8.4-RELEASE-p19 NUT version: nut-2.7.2_6 NUT installation method: from freebsd pkg system Device info: EATON 9SX 5000i, manufacturing date: 05.09.2014 ups.firmware: 9SX5Ki When i try to see battery charge, in output it have not such variable, and i can't control my server and other clients connected to them. Any options cannot power of server. How to see current battery

Hello Charles, Thank you so much for your help. Just run upsc and it is possible that input.transfer.low is the one because we used power regulator to bring down the power around 84v and then the ups sent the power loss message to PC. Do you think some others may take effect for the low voltage? Just have the upsc result attached. Then I retried input.transfer.low, default.input.transfer.low,

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 wanted to provide a upsc dump for an Eaton/Powerware 5115 rack mount unit. This was on a CentOS 7.3 machine with following packages installed: nut-client-2.7.2-3.el7.x86_64 nut-2.7.2-3.el7.x86_64 nut-cgi-2.7.2-3.el7.x86_64 $ upsc eaton5115 ambient.temperature: 43 ambient.temperature.high: 75 battery.charge: 100 battery.runtime: 24171 battery.voltage: 40.96 device.mfr: Eaton

On 12/25/2013 12:16 AM, Kris Jordan wrote: > Angel Tsankov wrote, On 12/24/2013 1:22 AM: [...] >> I can see that my UPS (MGE Protection Center 675) has a parameter >> ups.timer.start (currently holding the strange value of -10). Any idea >> if this could help and how this parameter can be changed? > > in upsrw? In upsc only. Here's the complete output:

On Sep 19, 2014, at 4:03 PM, Nello Lucchesi <nello at octobergroup.com> wrote: > I'm looking for a driver for and old uninterruptible power supply (UPS), Eaton Powerware 9125 2500U. I want to use it with my FreeNAS server. > > I looked a the list and didn't see a driver for it: > > http://www.networkupstools.org/stable-hcl.html?manufacturer=Eaton > > I see a

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

I'm looking for a driver for and old uninterruptible power supply (UPS), Eaton Powerware 9125 2500U. I want to use it with my FreeNAS server. I looked a the list and didn't see a driver for it: http://www.networkupstools.org/stable-hcl.html?manufacturer=Eaton I see a driver for the 9130; any idea whether it will work with a 9125? Any other ideas for connecting the 9125 to a FreeNAS

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

Hi! After some problems doing the automatic shutdown of the UPS on Debian, I have found this Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293401 Now I fixed it calling always ups-monitor from the halt script despite being halt'ed' or powered off (and relying on the POWERDOWNFLAG be set). Which is the correct aproach or best solution to workarround this bug? And now my

On Fri, Sep 25, 2020 at 11:47:42PM +0300, Manuel Wolfshant wrote: > On 9/25/20 1:36 PM, Lionel Élie Mamane wrote: >> On Thu, Sep 24, 2020 at 06:51:23PM +0300, Manuel Wolfshant wrote: >>> On 9/21/20 9:47 PM, Lionel Élie Mamane wrote: >>> We have a HP R/T 3000 G4 UPS; according to the data returned by >>> the usbhid-ups driver, it seems to be a "badge

On 19/09/13 01:30, Kris Jordan wrote: > 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