similar to: [Fwd: Centos/RHEL with MGE UPS Protection Centers (usb)]

comments online, > > The problem with this howto is that the shutdown process will NOT > work as expected. (This is why I ccd you, J.J.Garcia). (See below) > > Thanks a lot Antoine for the feedback, my fault for not checking a full shutdown with newhidups as i used to do with the serial-line models! i was hopping that the new second unit i bought (usb one) work fine as the old

OPENSOURCE wrote: > > I hope this answer your questions, and I hope you're ready to wait a bit > more. > Sure, NP for me, thanks for the feedback Arnaud. I have to admit that past days im having the syslog with a lil more activity from the new usb attached unit (ellipse ASR 1000 VA) Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2-pre2) Detected an UPS: MGE UPS

Hi I try since a week to run my MGE Protection Center under Suse Linux 9.3. At the MGE site i found an HowTo. I have installed NUT an create the=20 configs but at boot the newhidups driver say=B4s "no USB/HID UPS found".=20= Anyone an Idea? Johannes Schatz=

Hi, There is many (20 per day on average) messages like: kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -110 usbhid-ups[6768]: HIDGetDataValue: Connection timed out What can be done do correct that problem? best regards, Franck my configuration: debian etch nut 2.2.1 (recompiled source from testing to use latest version before posting here) updated

Hi, I recently bought a MGE protection center 500. I am running a gentoo, and I am currently trying to enable the ups handling by the os, with no success. First, I compiled and installe nut 2.0.2 (with usb support) and psp 3.0. I made ebuild for them that I will submit soon to bugs.gentoo.org. The ups is connected via usb, and lsusb confirms that the device is detected (cf end of the mail for

Dear users, This mail is to announce the beta availability of the mge-xml driver in NUT's trunk. This (overdue) driver allows to support MGE* (UPS Systems and Office Protection Systems) Network Management Cards. This development is sponsored by MGE Office Protection Systems, which is also the NUT sponsor, web hoster and (new) benefactor in general. This driver offers similar services to the

Hi All, I have an mge pulsar esv 14+ rackmount UPS connected via straight through serial cable to a USB to serial adaptor (My motherboard does not have a native RS232 port). I am running Ubuntu Server 9.04 x64, and nut 2.4.1-2ubuntu4 installed via APT. I am getting the error: Poll UPS [ups1 at localhost] failed - Driver not connected My conf files: (ups.conf) [ups1] driver=mge-utalk

Hello My server with another UPS (MGE Pulsar Evolution2200 USB) is OK. All scripts work Is it possible to work with a UPS MGE CometExtrem 6 on serial port Which driver can I use ? I tried with mge-shut ou mge-utalk without any success when I start driver with upsdrvctl with mge-utalk I have (after a long time) Can't connect to UPS [MGE_cometEX] (mge-utalk-MGE_cometEX): No such

Hi, Perhaps as you know it Schneider Electric acquired APC, which involves the combination of APC and MGE. http://www.apc-mge.com MGE is an important contributor for NUT with for example Arnaud Quette, it's does not that the MGE strategy for the free software is stopped by Schneider Electric or APC. It is the good moment to make pressure on Schneider Electric, MGE and APC to support the

Dear Sirs, I have an old but very well-working UPS MGE Pulsar ESV8+ Rack. I'd like to use it to power FreeBSD 9.0-Rel server. Of fortunately I have problem with recommended driver - mge-utalk, nut 2.6.4 (installed from FreeBSD Ports). I get messages: Could not get multiplier table: using raw readings. and updateinfo: Cannot update system status I saw similar thread on mailing list with no

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,

Hello, I'm using an MGE Evolution 1500 with a Debian Sarge 2.4.27 smp server. NUT is using the mge-utalk driver. [ups1500] driver = mge-utalk port = /dev/ttyS0 Seens I did a test.battery.start, my UPS goes off (beep!) once per week (same day, same hour). I guess there should be a very easy explanation for this, unfortunatly, I haven't found it yet. I've tried to upgrade

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

Hello, I'll be back with my MGE Evolution 2200 connected with RS232 I upgrade nut 2.0.1 in nut 2.2 + psp as you ask me PSP autodetect my UPS and autoconfigure NUT. not really diffcult ! So I didn't change anything but I always have in my syslog these event Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale Nov 13 11:09:27 mezenc upsmon[3865]: Poll

Dear NUT user, You are right concerning the autonomy calculation on Ellipse 650 UPS ("Low End" small Off Line UPS) => the estimation is not really accurate (and also a little bit pessimistic) => this is a known limitation that was documented on the previous NUT mailing list (before Alioth.org) MGE will stop soon the production of these models and will sell Protection Center and

Hi I have Pulsar 1000 (MGE) and mge-shut 2.0.5-3. By default mge-shut don;t reboot ups after upsmoc -c fsd, only permanent powerdown. After I add ondelay=30 in config, all nice, ups restarted after 10 sec. But according man mge-shut ondelay measured in tens of seconds and by default equal 3. -- Olleg Samoylov

[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, I find the following feature with MGE Pulsar evolution 2200: [root@hat ups]# /usr/sbin/upsd Network UPS Tools upsd 2.0.2 Connected to UPS [hat_PC_ups]: mge-utalk-ttyS0 Synchronizing........ giving up [root@hat ups]# upsc hat_PC_ups@localhost Error: Data stale Is there a way to make the sync part longer? After 5-10 seconds, however, things work fine: [root@hat ups]# upsc

Hello nuters, FreeBSD, Ellipse USBS 800, serial line, nut 2.02 everything works fine. But I'm only able to get an automatic shutdown when reaching the built-in 30% level. I the "lowbatt parameter" is set to anything, it's simply ignored. This is a problem as I want to shutdown around 90% to avoid the battery to drain out when multiple shutdowns occur. Any idea ?