similar to: MGE Pulsar Extreme communication problems

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

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 the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():

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

Hi all, I just changed my old MGE ellipse for a evolution 850 (now eaton). I can connect using mge-shut (newmge-shut doesn't work). But I have a few issues. I lloked around on NUT web-site and googled with no luck. Using debian lenny on 2.6.18 kernel (due to some ISDN driver that doesn't work with earlier kernels) 1) the most annoying is that I cannot shutdown the UPS. here is a trace :

Hello Panagiotis 2015-04-01 16:28 GMT+02:00 Panagiotis Kritikakos < panagiotis.kritikakos at nikitec.gr>: > Hello all, > > OS name: FreeNAS 9.3 > NUT version: 2.7.2 > NUT installed method: Bundled with FreenNAS 9.3 > Device: EATON 5SC 1000 (http://powerquality.eaton. > com/Products-services/Backup-Power-UPS/5SC.aspx?cx=5& >

Hello Arno, Thanks for the quick reply. FreeNAS is FreeBSD-based. Yes, I could test a patch. As I have mentioned, this behavior is not seen at every single reboot but after most reboots. Also, some times, the connectivity can be lost without even rebooting. That is not very often can have happened a few times. Best regards, Panagiotis On 2/4/2015 5:44 ??, Arnaud Quette wrote: > Hello

Hello all, OS name: FreeNAS 9.3 NUT version: 2.7.2 NUT installed method: Bundled with FreenNAS 9.3 Device: EATON 5SC 1000 (http://powerquality.eaton.com/Products-services/Backup-Power-UPS/5SC.aspx?cx=5&wtredirect=www.eaton.com/5SC&GUID=B81251A4-F34E-4373-94B3-B4FB3D0CBCA8) Problem description: This was originally reported as bug to FreeNAS

Hello Panagiotis 2015-04-03 14:28 GMT+02:00 Panagiotis Kritikakos < panagiotis.kritikakos at nikitec.gr>: > Hello Arno, > > Question: have you also tested oldmge-shut? >> Otherwise, that might be interesting to do so and send back the results >> of these tests... >> > Yes, I've tried this as well with worse results unfortunately. This driver > seems to

I have trouble in getting communication work with MGE Ellipse 500. I bought it second hand and I don't have the cable for it. How do I know if it's the Serial or USB model? The serial number of the unit is: 769B16015. I suspect it is the serial version as the label next to the RJ11 stands "com port", but I can't be 100% sure. MGE Ellipse serial cable pinout can be found

Hi Panagiotis 2015-04-06 9:13 GMT+02:00 Panagiotis Kritikakos < panagiotis.kritikakos at nikitec.gr>: > Hello Arno, > > Can apply the patch directly or should I recompile nut? > not sure to fully understand your comment, but... this is a source code patch, so you indeed have to apply it to the NUT source code (from within the source tree, "patch -p1 <

Hello Arno, FreeNAS doesn't come with a compiler and I had to compile with the patch on FreebBSD-9.3 and then copy the produced mge-shut. Unfortunately it didn't work out. For every try I was getting "Connection Refused" and when I tried /usr/local/libexec/nut/mge-shut -D -a <ups_name> I was always getting 'No matching HID UPS found'. I returned back to the

Hello Arno, Can apply the patch directly or should I recompile nut? Best regards, Panagiotis On 3/4/2015 5:06 ??, Arnaud Quette wrote: > Hello Panagiotis > > 2015-04-03 14:28 GMT+02:00 Panagiotis Kritikakos > <panagiotis.kritikakos at nikitec.gr > <mailto:panagiotis.kritikakos at nikitec.gr>>: > > Hello Arno, > > Question: have you also

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 have a FreeBSD 9.2 system with NUT 2.6.5 (installed via the ports tree) with an MGE Pulsar 1500 connected. A while ago it complained it needed the battery replaced and it was finally replaced last week, however I can't find out how to reset the flag in NUT. I've looked in upsc, upsrw and upscmd but none seem to have a suitable option. The UPS is connected via RS232 and upsc output

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 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 Arno, > Question: have you also tested oldmge-shut? > Otherwise, that might be interesting to do so and send back the > results of these tests... Yes, I've tried this as well with worse results unfortunately. This driver seems to be even more unstable. When it gets able to set communication with the UPS (which is not always the case), it usually lost it again after a while.

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

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