similar to: Hardware compatability report: Eaton Ellipse ECO 1600

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

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

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"

Hello! We have two upses: MGE Pulsar M 3000 and MGE Pulsar EXtreme 3200C. They connect to server by USB. EXtreme works good with usbhid-ups (nut 2.2.1) and newhidups (nut 2.0.5). But Pulsar M doesn't want to work with usbhid-ups. - my ups.conf: [extreme] driver = usbhid-ups port = auto product = "EXtreme" [pulsar] driver = usbhid-ups port =

Hi! Info OS: TinyCore Linux 4.5.6 NUT version: 2.6.4 NUT innstallation method: source tarball Device name: Eaton Ellipse ups eco 1600 usb din (EL1600USBDIN) /usr/local/ups/etc/ups.conf file: [eaton] driver = usbhid-ups port = auto When I run: root at Dalen:/usr/local/ups/bin/upsdrvctl start eaton I get this error message: Network UPS Tools - UPS driver controller 2.6.4

Hi, This might be a simple thing to fix, but I can?t figure it out. We replaced the battery for the first time in our Eaton 5PX a couple of weeks ago, but we haven?t been able to clear the ?ups.alarm: replace battery!? status. Details of our installation are: OS: Debian 6 NUT version: 2.7.4 Installation method: from source tarball UPS device: Eaton 5PX2000IRT, 240V, 1800W, 2000VA, bought in

Hi, I have recently purchased MGE ellipse 1200 UPS for my home system. Obviously, the choice of this particular brand was mainly dictated by MGE's long-standing support for Linux and NUT project. The fact that the box was clearly the prettiest looking one on the block did help also ;-). I have had NUT tools installed and configured in no time, as I did it numerous times before -- kudos

Hello all, I've got an MGE Pulsar Ellipse Premium 800 powering a couple of FreeBSD systems. Driver used is mge-shut, I don't know what the new mge-shut driver offers, but I follow the "if it works, don't fix it" dogma here. :) I also had a nut server installed on the master, with the /usr/local/etc/rc.d/nut script slightly modified to include a couple of upsrw commands

Charles, It starts out good, then goes into a Connection timed out loop. If I can provide any information to fix a driver I'll do my best. Here's the output: # /usr/local/ups/bin/usbhid-ups -DD -a eaton Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 0.000000 debug level is '2' 0.002550 upsdrv_initups... 0.288229 Checking device

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

Hi! I am not really experienced with UPS devices or UPS control software like NUT but i am enthusiastic and trying to use Eaton-9130 (it has one extra EBM too) as rationally as possible with NUT. I believe in general things are under control and behave, although i have some glitches and i would like to ask for help. I am using Debian v. 7 amd64 and from its packages nut-server and nut-client, v.

I am running NUT 2.2.0 compiled from the FreeBSD ports tree. [inchoate 14:50] ~ >upsc ups1 at localhost battery.charge: 59 battery.charge.low: 20 battery.charge.restart: 0 battery.runtime: 6350 battery.type: PbAc battery.voltage: 43.0 driver.name: usbhid-ups driver.parameter.offdelay: 120 driver.parameter.ondelay: 13 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version:

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

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,

Hi, I've been using NUT for many years to look after the UPS on my home servers. Originally I was using a Compaq R3000 but that was replaced with an MGE Pulsar Evolution 3000 about a couple of years ago because the Compaq one was just too noisy! I'm just setting up a replacement server and would like to connect it using a serial cable as I've found that the USB connection

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 :

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,

Device manufacturer and name: *Eaton 5E 1100i USB* *upsc eaton5e* Init SSL without certificate database eaton5e root at eger:/home/siposg# upsc eaton5e Init SSL without certificate database battery.charge: 100 battery.runtime: 3160 battery.type: PbAc device.mfr: EATON device.model: 5E 1100i device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2