search for: powershares

Hi! We have two MGE Evolution 1100 here, and I want to make use of the powershare outlets to force a particular boot sequence on the machines powered by them. However I'm not sure how to set those variables upon NUT starting, without having to change the init scripts to call "upsrw". Is there some place where I can set them, where they can be read automatically on startup? One of

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

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

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

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

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

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

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

Hello ! I've just a problem with upsd/upsmon 2.0.4, please have a look at the upsc command: -------------------- battery.charge: 59 battery.charge.low: 5 battery.runtime: 1312 battery.voltage: 24.0 driver.name: newhidups driver.parameter.port: auto driver.version: 2.0.4 driver.version.data: MGE HID 0.9 driver.version.internal: 0.28 input.frequency: 0.0 input.transfer.boost.low: 184.0

...EXCHANGE IN COM 4 OPTIONSXPRESS HLDGS INC COM 5 SUPERIOR WELL SVCS INC COM 6 HCP INC COM 7 SENIOR HSG PPTYS TR SH BEN INT 8 NATIONWIDE HEALTH PPTYS INC COM 9 DUKE REALTY CORP COM NEW 10 HEALTH CARE REIT INC COM 11 POWERSHARES QQQ TRUST UNIT SER 1 12 FLEXTRONICS INTL LTD ORD 13 VENTAS INC COM However with 60 cases the names above are not fitting neatly into plot. Can someone advice on plot Parameters to fix the size of dendrogram and see the full names on X axis? Thanks. Neil -------...

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

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 =

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:

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

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: