similar to: Cannot connect to a Eaton Ellipse Pulsar ASR/6000VA usbs [solved] but new problem surfaces.

On Jun 20, 2013, at 10:35 AM, Louis Chaillet wrote: > With respect clarification of the documentation (and reference to your question Charles). The documentation does suggest that you can shutdown the ups by the upsdrvclt shutdown [ups] command. Specifically in "http://www.networkupstools.org/docs/man/upsdrvctl.html" in the section commands under warning. In the "Network UPS

Hi all, I am trying to communicate to this Eaton Ellipse (see above) using nut from a Debian Squeeze system on Armel architecture. But have not succeeded so far. Version: Linux b3 2.6.39.4-11 #1 Tue Apr 3 21:45:12 FET 2012 armv5tel GNU/Linux Nut version is 2.4.3-1.1squeeze2 this information if from dpkg. NUT installation method:from debian package for armel. The problem is I cannot

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

Hello guys, I have to manage an Eaton Ellipse ASR 750 VA UPS under a FreeBSD 8.2 server. I used nut from ports collection but I'm unable to detect the UPS by USB cable. Here is the output of 'usbconfig -u 4 -a 2 dump_device_desc' : ugen4.2: <ELLIPSE EATON> at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110

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

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 all Arnaud, Some newly purchased Ellipse ASR-model UPS find their way to my office for a first evaluation test. It concerns the Ellipse 1500 and Ellipse 1000 models. As you know we are still working with hidups. Peripheral recognition, start of NUT, mains short interruptions management, all that work fine... as expected ;-) But changes occured on the delayed shutdown procedure after the

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

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

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

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

> 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

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

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, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

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

Hi I'm having a problem with the bcmxcp_usb driver FSD command: everything seems to work apart from: upsmon -c fsd Environment: Ubuntu 7.04, nut 2.0.5-1, nut-usb 2.0.5-1, Powerware 3105 UPS. upsd appears to send the FSD command to the UPS, upsmon then runs my NOTIFYCMD (which halts my PC) but the UPS just doesn't turn off. Here are the /var/log/daemon.log entries: Jul 24 23:13:16

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)