similar to: add'on : MGE Ellipse 800 USBS & FreeBSD

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

[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

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,

I have an Ellipse USBS connected via serial cable to a CentOS 3 box. Do I need to turn off the UPS as the final stage of shutdown, or will the UPS power itself off, before the battery reaches a level to low to safely recharge from? I notice there is the option for the UPS to turn itself off (and on again) unattended if power is restored during shutdown, but there doesn't seem to be an option

Hi there, I've replaced yesterday my old UPS with a brand new "Eaton Ellipse MAX 600 USBS". I've choosed the Eaton (previously MGE) both because I've always been extremely satisfied with MGE UPSes of all kinds at work, and because of the involvement of MGE (with Arnaud) in nut development, which made me quite sure that I would have no trouble with an Eaton (MGE) UPS and

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 >

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

upsmon.conf using NOTIFCMD and NOTIFYFLG is working well, it is calling my script "notify" on requested events (ONBATTERY,LOWBATTERY and ONLINE). Command #upsmon -c fsd -u monmaster myups at localhost gracefully shutdown my box and after several seconds switch off the ups's load. Two problems: - notify script is called and executed as user "nut" (as it used to be

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

Thanks for suggetions and keep me indumb about making of Debian packages:D I will try this package "nut_2.2.0-2_i386.deb" One little questionm, shoud I use newmge-shut driver? - my ups is quite old - more then 3 years, connected through serial cable. >> PS: Arjen de Korte suspected something was wrong around my "heater" load, >> for now I have used two 150W lamps

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

Hello, I've installed & configured NUT 2.0.4 connected over a serial port to an MGE USBS 750. When the UPS enters the 'critical' state (ie, battery load below the defined battery.charge.low AND power input off), the UPS just shutdown itself instead of notifying NUT. When I say the UPS just shutdown, I mean it autonomously shut down itself within one second after reaching the

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

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

Hello everybody, Our supoprt team is facing a problem which froze the CPU. They suspect that this happens after an automatic battery test, which lets the battery goes down to 30% and then stop the test. At this level of charge, our kernel also triggers a shutdown (CPU and UPS). I saw (in the doc found here : tools.*mge*ops.net/download/intl/products/*ellipse*-asr/28-umeasr_08.pdf) that this

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,

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"