similar to: Fwd: Re: MGE NMC and NutShutdownModule (and other stuff)

Hi all, some time ago I bought at discount price a NMC for managing a few computers using the programmable outlets features available on my MGE Evolution, unuseful otherwise (ATM). However, expecially for my server machine, I don't like very much the NSM client provided by MGE/Eaton and I'd rather use only NUT from my distribution. So, looking at the netxml-ups driver, I started adding

Hi, I'm a MGE Evolution 650 owner and, after putting in place a basic configuration for controlling my UPS, I'm going to tune a little bit better NUT for my needs. First of all let me describe my little (SOHO) scenario: I have the ISP modem/switch (providing VoIP too, so it's important to keep it running as much as possible), a small low power home server and a much hungrier PC.

I am running NUT 2.2.0 compiled from the FreeBSD ports tree. [inchoate 14:50] ~ >upsc ups1 at localhost battery.charge: 59 battery.charge.low: 20 battery.charge.restart: 0 battery.runtime: 6350 battery.type: PbAc battery.voltage: 43.0 driver.name: usbhid-ups driver.parameter.offdelay: 120 driver.parameter.ondelay: 13 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version:

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

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

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

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

I was looking at how other drivers deal with outlet collections, and I noticed some differences between newhidups in 2.0.4 (from Debian's 2.0.4-2.3) and the SVN trunk (rev 723) on an Evolution. Full diff is below, but here are the highlights: * MGE HID 0.9 vs 1.0 * outlet.#.switch seems to have moved to the commands outlet.#.load.{on,off} Then I found this in the ChangeLog: * fix

Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Author: adkorte-guest > Date: Wed Nov 11 10:44:46 2009 > New Revision: 2102 > > Log: > Properties changed > > Modified: [...] > trunk/drivers/netxml-ups.c Oops, this accidentally slipped in as well. This update changed the behavior of the netxml-ups driver to allow a NSM-client only mode. In

Hello ! I've just a problem with upsd/upsmon 2.0.4, please have a look at the upsc command: -------------------- battery.charge: 59 battery.charge.low: 5 battery.runtime: 1312 battery.voltage: 24.0 driver.name: newhidups driver.parameter.port: auto driver.version: 2.0.4 driver.version.data: MGE HID 0.9 driver.version.internal: 0.28 input.frequency: 0.0 input.transfer.boost.low: 184.0

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 ?

Hi, I've been using NUT for many years to look after the UPS on my home servers. Originally I was using a Compaq R3000 but that was replaced with an MGE Pulsar Evolution 3000 about a couple of years ago because the Compaq one was just too noisy! I'm just setting up a replacement server and would like to connect it using a serial cable as I've found that the USB connection

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

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

Dear folks, According to mge-mib.c (NUT 2.6.2) LB condition is gained from variable .1.3.6.1.4.1.705.1.5.14.0 (i.e. upsmgBatteryLowBattery.0). The test device of me does not set this variable to yes(1) even if runtime drops below the preconfigured limit. I complained about this at Schneider Electric. They replied that low battery status is indicated by .1.3.6.1.4.1.705.1.5.14.0

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 =

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,

Hello, At my workplace I have exact UPS config as stated in the subject (APC MGE Galaxy 5500 + AP9635CH). I have it set up to work with snmp-ups NUT driver. Despite many readings from *upsc* command I am not receiving "On Line Status" (ups.status OL) nor "On Battery Status" (ups.status OB) and therefore I can't get my systems to shutdown during a power outage event.

One good intro to this is https://github.com/networkupstools/nut/blob/master/docs/snmp-subdrivers.txt although it focuses on adding new subdrivers - but more or less the same workflow applies to extending existing ones. Sometimes it helps to generate a new one for a currently-partially-supported device, and then compare with existing subdriver (using meld or similar GUI helps a lot) to port the

I've got an update on this case Using tkmib I discovered that my UPS (NMC per say) sends its state by OID 1.3.6.1.4.1.318.1.1.1.11.1.1.0 .iso.org.dod.internet.private.enterprises.apc.products.hardware.ups.upsState.upsBasicState.upsBasicStateOutputState.0 = 0001010000000000001000000000000000000000000000000000000000000000 (mib used for this snmpget was powernet441.mib) (I got a description about