similar to: (no subject)

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, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

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

Hello everybody, After succeeded in "tuning" nut-2.0.0's hidups and 2.0.3's newhidups on customized Linux kernels, we are now facing a new challenge : trying to install nut-2.0.5 on a RedHat ES4 which is based on a 2.6.9 kernel. I picked up the 2.0.5 source package and follow the INSTALL doc until step 6. So far so good. RH ES4 is managed by udev, therefore I presume we

(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 everybody, I installed and configured Nut 2.4.3 on Debian Squeeze, using package. It monitors an MGE Pulsar 1500 UPS in standalone mode. Here are parts of upsmon.conf : SHUTDOWNCMD "/bin/bash /root/extinction.sh >> /var/log/ups/ups.log 2>>&1" NOTIFYCMD "/bin/bash /usr/sbin/alerte.sh" [...] NOTIFYFLAG ONBATT SYSLOG+EXEC At startup, driver, upsd and upsmon

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

Hi I have Pulsar 1000 (MGE) and mge-shut 2.0.5-3. By default mge-shut don;t reboot ups after upsmoc -c fsd, only permanent powerdown. After I add ondelay=30 in config, all nice, ups restarted after 10 sec. But according man mge-shut ondelay measured in tens of seconds and by default equal 3. -- Olleg Samoylov

Hello, I forgot nut since more than a year because a lot of job with other application My server nut failed since severals months We had 3 electric failure so I must install a new server nut I work with ubuntu 10.04.4 (64bits) / I installed nut 2.4.3 with deposits I have a MGE Pulsar evolution 2200 connected on usb last week when I began my tests all was ok (communication etc etc ..)

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

I suspect that the battery is failing on my Pulsar Evolution 500 (it is several years old now) but I can't seem to get a valid battery voltage from the UPS. The following tests were done using NUT 2.2.1, but I first noticed this with the trunk, and reproduced it with the current branches/Testing as well. The only two values I have seen for battery.voltage are 120.0 and 119.0, e.g.: $ upsc

Hello, I encounter a problem using the UPS MGE Evolution 850 VA USB with Debian Etch and the nut package available for this version. I got this error: ==syslog== Can't connect to UPS [MGE850VA] (usbhid-ups-auto): No such file or directory upsd[2767]: Startup successful upsmon[2769]: Startup successful upsd[2767]: Connection from 127.0.0.1 upsd[2767]: Client MGE at 127.0.0.1 logged

Hello, I've installed Nut (2.0.5) on RedHat a week ago, and upsmon seems to generate false alarms every hour: ... Jun 8 06:10:56 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on line power Jun 8 06:35:46 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on battery Jun 8 06:35:51 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on line power

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, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk

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

Dear Sirs, I have an old but very well-working UPS MGE Pulsar ESV8+ Rack. I'd like to use it to power FreeBSD 9.0-Rel server. Of fortunately I have problem with recommended driver - mge-utalk, nut 2.6.4 (installed from FreeBSD Ports). I get messages: Could not get multiplier table: using raw readings. and updateinfo: Cannot update system status I saw similar thread on mailing list with no

I'm experiencing a rather serious issue with the usbhid-ups driver on two different Linux systems. The symptoms on both systems are the same: After anything from a few hours to a day or two, upsd is no longer able to communicate with the UPS. upsd initially starts complaining about "data from UPS <such-and-such> is stale - check driver", then upsmon reports a loss of

Hello, looking for replacements for some older Powerware equipment I found the MGE Pulsar Extreme 1000C and I'm currently testing one with nut-2.0.3 on a self-brewn i386-linux. Upto now everything seems to work fine - except I can't get the power outlets switching on again after mains returns. As this works with Personal Solution-Pac 2 on W2k I thought that there might be a way to