similar to: Random but persistent USB disconnect/reconnect with MGE Pulsar Ellipse Premium

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

I'm struggling to configuring nut for MGE Pulsar Ellipse 800 (at least Ellipse 800) for two boxes - home firewall and file server. I'm using Debian 4.0 Etch, every one of them. I'm built (after some dangerouse experiments) a testing configuration, where boxes are plugged to line, server playing as a master, firewall as a slave, and UPS connected to an electric heater about 300 Wats (no

> 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

Hi everyone, This is not directly NUT related, but i don't know where else I can still ask this. I have been using a pretty decent 2nd hand MGE ellipse premium 1200VA for a while now at home. http://www.mgeups.com/download/doc_intl/ small/premium/389uk.pdf It's been working very well for me on linux, but my linux server has recently passed away and now I only have Macs left.

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 have an MGE Ellipse Premium 1200 that I connected to my server using its USB cable. Nut seems to be working fine. I've done a power down test and it worked and came back up when the UPS had power again. I'm using the newhidups driver and the USB cable. The problem I'm having is that if I boot with the cable connected newhidups says it can't find the UPS. If I unplug and plug in

My new MGE Ellipse Premium 1200 is now working fine. I've tested pulling the plug and the computer shuts down properly and comes back up when I replug. The only strange behaviour is that when I put the power back on the battery shows as being at 86%. If it was at 86% it should have lasted longer. Is there any calibration step I can do? The only commands the ups seems to support are: $ upscmd

I am running Ubuntu 6.06 connected via serial port to an MGE Pulsar Ellipse 800VA. Have just installed NUT 2.0.3, and have problems with connectivity. This UPS was workign via serial connectivity to a BSD system only a few days ago. I have followed the instructions at http://opensource.mgeups.com/install/debian.htm The details... jason@ubuntu:~$ ls -la /dev/ttyS? crw-rw-rw- 1 root dialout 4,

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

Hello, I have Ellipse ASR 1500 UPS and now I'm trying to monutor it with NUT from FreeBSD. It seems that there are some problems with this UPS: =================================== ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 > usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), NEC(0x0000), rev 1.00 port 1 powered port 2

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

(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

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

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

Beautiful! The shutdown succeeded. Thank you very much. However there was no any notification on desktop at all. Only in journalctl. Here it is: Oct 27 23:38:11 i7 upsmon[2224]: UPS myups at localhost on battery Oct 27 23:38:11 i7 upssched[2244]: Timer daemon started Oct 27 23:38:11 i7 upssched[2244]: New timer: two-minute-warning-timer (5 seconds) Oct 27 23:38:11 i7 upssched[2244]: New timer:

On Wed, 28 Oct 2015, George Anchev wrote: > Beautiful! The shutdown succeeded. Did you see a line in the journal similar to this ? Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]: nut-delayed-ups-shudown.service calling upsdrvctl to shut down UPS unit > However there was no any notification on desktop at I'm guessing you use KDE and this

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/

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

Hi! I have a MGE Pulsar ES 8+ UPS. Here is the response of some commands: - Si --> 3000 44 0 - Si 1 --> Pulsar ES8+ 0 - Ai --> 5 0 It's not recognized very well by the current (from CVS) mge-utalk driver: [root@srv01 ~]# /home/rog/src/nut/drivers/mge-utalk -i 20 -DDD -u root /dev/ttyS0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.86 (2.1.0) debug level is '3'