similar to: NUT 2.0.3 ups.conf serial comms to an MGE Ellipse

guys, A bit off topic here, but since this issue already has a history here: serial connection to the SCD, the never ending story ... - the intel D945GSEJT mainboard (ICH7) has two serial ports with onboard connectors which require a ribon cable to the external DB9 connectors in the case. I tested 5 cables, but none works. whereas I'm not sure if it is a cable problem. this is what dmesg

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

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

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

[fwded to the list] Hi Fran?ois, > I didn't post this on the list as it seems a little bit more MGE > stuff than nut. Anyway feel free to post it if you consider it's > relevant. > > This is the trace you were asking for. The Ellipse 800 correctly shut > down in this test : > > This was running on a i386 recent hardware, the cpu load is under 5%, > 360MB out of

Hello happy nuters, Some complementary words about making nut 2.02 successfully run on FreeBSD with MGE Ellipse. With the usefull information Arnaud sent, it's rather obvious that the erratic response of the ups to the shutdown script is linked to its difficulty to handle large traffic on the serial line. These are the final tweak I made to have this configuration satisfyingly

I am in the process of migrating from running CentOS 4.8 (32-bit) to CentOS 5.4 (64-bit) on my AMD Sempron(tm) Processor LE-1300 system (it is running CentOS 4.8 32-bit because the disk images are from a previous PIII system), and things are 'interesting' WRT how the Lava Computer mfg Inc Quattro-PCI card is being handled. lspci (on CentOS 4.8 32-bit) yields: 01:0a.0 Serial controller:

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

I've recently bought an MGE 650 that has both cables : USB and Serial. Since it's used on a server, I'd prefer not to load usb drivers just for nut. The problem is, either with newhidups or with mge-shut, the driver instantanly report that the communication with my MGE is lost, and shotly after that my ups is unavailable. It never show up again, and nut constantly says that the

Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500. I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2, nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!) lsusb shows: Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS /etc/ups/ups.conf says: [myups] driver = usbhid-ups port = auto desc = "Local UPS"

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 have recently purchased MGE ellipse 1200 UPS for my home system. Obviously, the choice of this particular brand was mainly dictated by MGE's long-standing support for Linux and NUT project. The fact that the box was clearly the prettiest looking one on the block did help also ;-). I have had NUT tools installed and configured in no time, as I did it numerous times before -- kudos

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, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags)

Hi people. I'm trying to config a: MGE ELISE PREMIUM 1200 NT 02 Serial Nr. 92HE04008 With its serial cable into /dev/ttyS0. I had configured ups.conf, with no luck. Here is my ups.conf: [upscura] driver = mge-shut port = /dev/ttyS0 desc = "UPS" The permissions into /dev/ttyS?: crw------- 1 nut nut 4, 64 mar 8 18:43 /dev/ttyS0 crw------- 1 nut nut 4, 65 mar 8 18:42

Hi all, First of all thanks for the great work on nut ! (despite it's not fully functional yet overhere). Everything seemed to go fine until the final test : shutdown the UPS ! The system is running FreeBSD 5.3, the UPS is MGE Ellipse 800 USBS both linked with the MGE serial cable. The system is a remote server, only running some file services and large disks. The porting,

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