similar to: MGE Pulsar Ellipse 800 offearly or box shutdown late

> If you set lowbatt=70 then the behaviour you are seeing is normal. Don't > set lowbatt and you'll get the default manufacturer settings which is > LOWBATTERY at 30% charge level. > > Philippe Thanks for quick response! I realized this and forget this setting! For now I think that my box does not recognize signal about low battery - I'm only started to read SHUT

upsmon.conf using NOTIFCMD and NOTIFYFLG is working well, it is calling my script "notify" on requested events (ONBATTERY,LOWBATTERY and ONLINE). Command #upsmon -c fsd -u monmaster myups at localhost gracefully shutdown my box and after several seconds switch off the ups's load. Two problems: - notify script is called and executed as user "nut" (as it used to be

Thanks for suggetions and keep me indumb about making of Debian packages:D I will try this package "nut_2.2.0-2_i386.deb" One little questionm, shoud I use newmge-shut driver? - my ups is quite old - more then 3 years, connected through serial cable. >> PS: Arjen de Korte suspected something was wrong around my "heater" load, >> for now I have used two 150W lamps

Hi, recently I observed that during a power outage, my NUT setup doesn't shutdown properly. Indeed it never reaches the LowBattery state to notify and initiate shutdown on clients. Reviewing my setup and logs I think I'm facing multiple problems and I'm unable to point to real root cause. First, let me focus on my scenario and current setup: In normal status (ONLINE, fully charged)

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

Hi, Our research group is planning to buy an MGE Pulsar Evolution 3000 to protect our operational computers against power failures with an SNMP network management card. We would like to connect the UPS only through its network card (and not via USB or serial cable to another computer) and install the NUT software (client+server) on each machine to catch the shutdown SNMP signal from the UPS

I'm now doubting if I've made this statement or not, so here it is: newmge-shut is *not* ready for production usage! I've lately found some bugs during the MGE PSP 3.0.4/3.0.5/3.0.6 updates. So for the moment, prefer to keep using mge-shut. 2007/10/25, R?zsa G?bor <mailer.tovis at freemail.hu>: > newmge-shut ??? > Shutdown, switch of ups does not work. Using command >

Hello, My MGE Pulsar Evolution 800 had some hardware troubles (it may be the batteries according to the manual). The fault was not detected so the power was cut to the load and nothing appears in the log files. Arnaud: do you know if the UPS have some way to report this kind of troubles to the PC so that NUT can handle it with a shutdown sequence ? Philippe

Hi, My UPS is MGE Pulsar Ellipse Premium 1200VA, connected on USB port, usbhid-ups driver. Using simply KNotify about UPS connection states I noticed that sometimes unpredictably a notification appears that the USB connection to the UPS is lost and a few seconds later another notification appears that the connection is restored. And this repeats to infinity. The only way to get out of it is to

Hi all, I am trying to communicate to this Eaton Ellipse (see above) using nut from a Debian Squeeze system on Armel architecture. But have not succeeded so far. Version: Linux b3 2.6.39.4-11 #1 Tue Apr 3 21:45:12 FET 2012 armv5tel GNU/Linux Nut version is 2.4.3-1.1squeeze2 this information if from dpkg. NUT installation method:from debian package for armel. The problem is I cannot

On Jun 20, 2013, at 10:35 AM, Louis Chaillet wrote: > With respect clarification of the documentation (and reference to your question Charles). The documentation does suggest that you can shutdown the ups by the upsdrvclt shutdown [ups] command. Specifically in "http://www.networkupstools.org/docs/man/upsdrvctl.html" in the section commands under warning. In the "Network UPS

Hi Charles, thank you for your answer. This was indeed the core of the problem. I have amended the configuration files. It means now the communication works as required. Alas I now have another problem. Just for the record here is the configuration after the changes. The configuration is as follows. #nut.conf MODE=standalone #ups.conf [eaton] driver = usbhid-ups port = auto

Hello, I'm trying to communicate with a MGE Pulsar STS 16 using nut under Linux, but I've had no luck so far. I haven't saw it supported in the doc, so if there's anything I can try... Thanks, Arnaud. -- Perso: http://launay.org/blog/ H?bergement: http://www.nocworld.com/

(Sorry, I accidentally discarded the wrong message in the moderation queue - please subscribe to the list to avoid this in the future.) > From: <onyx at netfusion.fr> > Subject: [HCL] MGE Pulsar Evolution 1100 - not recognized by USB driver > Date: December 22, 2011 12:15:16 AM EST > To: <nut-upsuser at lists.alioth.debian.org> > > > Hi everybody, > > It

Hi all, Have been using Nut on Linux for over ten years now and find it brilliant. Thanks. Just upgraded to 2.4.2 and have the 5 or 6 models of UPS's that we use (apcsmart, megatec, mge-shut, surgemax, digitus) all working including the MGE Pulsar Evolution 1100 on a USB connection using the usbhid-ups driver. Running on SLES9. Old but we still have a few servers out there running

We have several systems in remote locations and I have found that the ones in the US are having issues.. We are an Australian company and can't source a 110V UPS locally so we arrange to have one bought for the site when it's installed. It seems that in the US we are getting "Pulsar EX 1500" UPSs but locally we buy "Pulsar 1500". NUT seems to work find with the

I have an MGE Pulsar Evolution 1100 connected to a Debian box, with nut-2.0.1 (the standard "sarge" packages). I have it connected through USB, and I'm using newhidups. However, about once a day the driver looses contact with the UPS and I have to restart NUT to get it to drop the "data stale" nonsense (it happens more often than this, but most times it recovers without

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 9/28/06, Ingo Schaefer <ingo@ingo-schaefer.de> wrote: > Hallo, > > I installed nut 2.0.4 on a Solaris 8 and tried two things: > > First I wanted the ups to connect via usb, but I could not compile the > usb drivers. Make usb told me: no target named usb found Do you have libusb installed? (I was not aware that there was a port of libusb for versions of Solaris before

Hello all, I wonder if the improvements to a driver called "newmge-shut" which have been mentioned in October 06 got it to the 2.0.5 release? I tried my setup again with this release and still get this "communication lost -> established -> lost -> established" cycle. USB was not working because of the Solaris 8 installation. Regards, Ingo -------------- next part