similar to: MGE Pulsar Evolution 1100 - USB - error sending control message

(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

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

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

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/

I'm running nut 2.0.1 with an MGE pulsar evolution 3000 with the mge-utalk (serial) driver on NetBSD 3.1 . I had a very strange occurance in my basement datacenter this early AM. the following was logged by upslog: 20080219 023452 100.0 123.0 049.0 [OL CHRG] NA 60.00 20080219 023522 100.0 122.8 049.0 [OL CHRG] NA 60.00 20080219 023552 098.0 123.0 049.0 [OL DISCHRG] NA 60.00 20080219 023622

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

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

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

hello, I tested all config with my ups and psp all seems to be OK now, I had change ups name and user name in ups.conf, upsd.users, upsmon.conf etc etc ... but I have quickly these events in my syslog without doing anyting what can I do ? Nov 15 11:09:22 mezenc upsmon[3865]: Poll UPS [pm2200 at localhost] failed - Data stale thanks a lot for your help Sabine GOUDARD Ecole Nationale

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:

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

Hi, Apologies if this is a known problem. I have just joined the list and haven't done an exhaustive search of the archives. Also I am no UPS expert, so please excuse me if some of my terminology is poor. I use an MGE Pulsar Extreme 700C connected via RS232 to the linux server it powers. I have recently upgraded to a new linux distribution. Both new and old use 2.6 kernels, although

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

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

> 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

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