similar to: "Communications lost" temporarily at every startup

Greetings Arnaud and others, I've been using NUT with Gentoo Linux for a couple of years now. I recently installed SUSE Linux 10.0 and I'm having difficulty getting it to recognize my UPS (MGE Ellipse). I tried the MGE-PSP package, but the GUI crashes immediately on startup. I decided to get just NUT running correctly before worrying about that. I uninstalled MGE-PSP and am left wtih

2006/1/13, Paul Mogren <fkamogee@yahoo.com>: > > This thread is FYI. I don't need any help here. > no, but some details for those who will read it, maybe ;-) I have SUSE 10.0 and an MGE Ellipse. I installed the NUT package from MGE. > > 1) The generated ups.conf pointed to a bad location: > /dev//dev/input/event0 > who generated that ? it seems like an old hiddev

Hello. So as my english is not so good, i'll try to write my story in bash commands :o) miwa@zork3$ uname -mrs FreeBSD 5.5-STABLE i386 miwa@zork3$ su root@zork3# cd /usr/ports/sysutils/nat root@zork3# make && make install root@zork3# cd ../nut-usb root@zork3# make && make install root@zork3# cd /usr/local/etc/nut root@zork3# cat ups.conf user=root [MGE-Ellipse]

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, I have installed in suse 9.3 and ellipse premium 500 usb a psp 3.0 with yast2 and versions: nut-2.0.2-4 mgeups-psp-3.0.0-3 the first time that I launch psp it seems to contact the UPS and you can make changes to the parameters and all seems ok. If you make a reboot the psp hangs up and if you try /etc/init.d/ups it fails: Starting service NUT: -> Starting UPS driver: Network UPS Tools -

Hi, I have an MGE Ellipse UPS connected to a FreeBSD 7.0 system and it works OK to begin with but after an hour or so it dies, eg.. Starts out OK.. debug level is '2' upsdrv_initups... Checking device (0463/FFFF) (/dev/usb2//dev/ugen0) - VendorID: 0463 - ProductID: ffff - Manufacturer: MGE UPS SYSTEMS - Product: ELLIPSE - Serial Number: 000000000 - Bus: /dev/usb2 Trying to match device

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"

Hi, I'm running into an issue while using FreeBSD 5.4, NUT from ports (2.0.3), serial on /dev/cuaa1, Ellipse 1200 USBS. The ups.conf is : [ellipse] driver=mge-utalk port=/dev/cuaa1 desc="Telecom Closet Ellipse" When I go to start it I get : Network UPS Tools - UPS driver controller 2.0.3 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.87 (2.0.3)

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, i use nut with mge comet ex 7 rt (mge-shut driver). Is ist possible, that upsmon loses states? I obtain onbatt and online messages every time, but sometimes there are no lowbatt and/or shutdown messages. regrads, miroslav -- SHALTEV.ORG @ http://www.shaltev.de

Hello, I installed NUT and configured it for 2 MGE UPS's connected via USB. Debian etch NUT package: # dpkg -l nut*|grep ^ii ii nut 2.0.4-3 The core system of the nut - Network UPS Tools ii nut-usb 2.0.4-4 USB Drivers subsystem for the nut - Network UP Separately, with only one UPS defined in ups.conf, each one works fine (I specified specific serial numbers for either, with

Hi all, I have a MGE Ellipse 600 UPS connected to com1 on a PC running FreeBSD 4.11 with nut-2.0.2_1 installed. I have everything working and operational. BUT. on rare occasions I reboot my machine and when it comes up I get the following error: Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - MGE UPS SYSTEMS/SHUT driver 0.64 (2.0.2) No communication with UPS Driver failed to

Hello, I'm using NUT to manage a MGE Ellipse ASR UPS, with the newhidups driver. It works fine, except that after a few hours, I get a few errors from the kernel and the driver dies. Here's the output from the syslog: Apr 26 02:00:41 ezquiel kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Apr 26 02:00:43 ezquiel last message repeated 2 times

On opensuse 10.3, i installed nut and configured my ups.conf like i did it on opensuse 10.2 by putting (10.3 , nut 2.2.0): [MGEpc675] driver = usbhid-ups port = auto desc = "MGEpc675" instead of (10.2 , nut 2.0.4) : [MGEpc675] driver = newhidups port = auto desc = "MGEpc675" But it doesn't work. It appears that upsdrvctl

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

Hi everybody, If we let the feature running, it appears that the driver gets unbound after a while ( variable from quarter of hour to 6 hours ) and cannot reconnect. This behavior appear with both MGE Ellipse ASR and non-ASR models with connection to an UHCI and OHCI controllers. The USB core is from 2.4.28 kernel. We use nut-2.0.3. Start, powerfail and recovery detections, UPS shutdown work

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

My UPS is a Eaton Ellipse 1000S (But its identified as MGE Ellipse 0463:ffff). I have been using the usb interface with the usbhid-ups driver, but I found that sometimes (too much times) the driver doesn't respond and NUT doesn't receive changes nor notifications from the UPS. The kernel lose the connections with USB device, in the kernel logs appears: Dec 30 11:24:12 rei kernel:

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

Hi, i had purchase a MGE-Ellipse 500 and i'm trying to use the DB9 F / RJ45 cable send by MGE with UPS. Which driver i'm suppose to use: mge-utalk or mge-shut ? When i try mge-utalk i've got this message: # upsdrvctl start Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - MGE UPS SYSTEMS/U-Talk driver 0.80.3 (2.0.0) Startup timer elapsed, continuing... and there is