similar to: [HCL] Eaton 5S1500LCD supported by usbhid-ups

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

Hello, we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server using a serial cable. Installed and configured properly are RPM versions of nut-2.0.3-0.1.fc5 nut-client-2.0.3-0.1.fc5 nut-cgi-2.0.3-0.1.fc5 which all work (mostly) fine. The server is connected to outlet.0 and properly shuts down when it's loosing power after around 20 minutes. It also boots up whenever the ups

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,

I was looking at how other drivers deal with outlet collections, and I noticed some differences between newhidups in 2.0.4 (from Debian's 2.0.4-2.3) and the SVN trunk (rev 723) on an Evolution. Full diff is below, but here are the highlights: * MGE HID 0.9 vs 1.0 * outlet.#.switch seems to have moved to the commands outlet.#.load.{on,off} Then I found this in the ChangeLog: * fix

Hi, FINALLY got my UPS working, YEA!!!! But now it brings up even more issues.. (BOOO!!) 1) I'm thinking this is a UPS issue, but when I pull the plug on my UPS, it goes from 100 to 30 in just a short amount of time (Minutes). This causes the machine to shut down. But once it gets to 0, its beeped its little heart out for a few more HOURS providing power to the non-system items perfectly.

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:

>> last night we had what looked like a power spike and 3 machines plugged >> into 2 Eaton UPS went down instantly. I heard the click the UPS makes when >> it shuts the load on the ports and then shuts itself down (ie same thing if >> I simulate with upsmon -fsd). The machines instantly came back, there was no >> actual downtime, and the machine next to them which is

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

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

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"

Hi Dag 2010/2/28 Dag Atle Nettum <dagatle at innit.no> > Hello > > > > I understand you are the project leader of Nut. > > > > In my company we have a Eaton 9135 6000 UPS, we are running NUT 2.4.1 > (Debian squeeze) > > > > The ups is connected with a USB cable but it reports a temperature of 300 > degredes. > > > > Can I send you

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

Hi, I'm a MGE Evolution 650 owner and, after putting in place a basic configuration for controlling my UPS, I'm going to tune a little bit better NUT for my needs. First of all let me describe my little (SOHO) scenario: I have the ISP modem/switch (providing VoIP too, so it's important to keep it running as much as possible), a small low power home server and a much hungrier PC.

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.

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

On Jun 4, 2014, at 6:38 PM, Shen Chuan wrote: > $ sudo upsrw -s battery.charge.low=70 -u * -p * ups > OK Not sure this does what you originally asked, though. Does upsc show any settings related to sensitivity? -- Charles Lepple clepple at gmail

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