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

Citeren Marco Chiappero <marco op absence.it>: > I managed to get twice connected at the same time from the same > machine to a single UPS using different hostnames, so it's > definitely not an IP based check (at least here with 66102 / EC). Never mind. The alarm messages are not bound to a specific outlet, but are sent to all NSM clients that are connected. Which means

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.

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

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

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.

So what would it take me to edit NUT's code for my case to work? My Network Management Card sends its output state using unfortunately only (I guess so) this OID: 1.3.6.1.4.1.318.1.1.1.11.1.1.0 Weirdly the standard way of obtaining Battery Status (drivers/apc-mib.c) 1.3.6.1.4.1.318.1.1.1.2.1.1.0 gives me good results. Unfortunately power status OID's value type differs (my: 64 digits

Well thanks, The solution for my problem was kinda easy (still need some testing though): found out my ups status is a string, so then I changed the way snmp-ups.c gets the status. Had to change *nut_snmp_get_int *to *nut_snmp_get_str *at around line 3470, then grab fourth char out, use *strtol *function to then send it to *su_status_set *function. I created my copy of *apc-mib.c *with my OID at

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

Hello, this is a request for assistance that I submitted earlier, this time with the dataset. My mistake for taking up bandwidth. I've also rephrased the question to address an additional concern. I'm working on a windows XP machine with R 2.8.1 1). I'd like a barchart (or other lattice type display) HSI ~ of the three factors (Region, Scenario and HydroState). However

Dear Arjen, Arnaud et al, I've just organized an MGE UPS with Ref. 66074 SNMP/Web Transverse Card for testing purposes. Months ago I found a quite simple bug in the UPS-MIB implementation of this card and Schneider Electric guys seemed not to have intention and/or knowledge to fix it. Now local representative sent me an MGE "Pulsar Extreme 2000 VA" model in order to find an

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

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

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

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

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:

Hello. ?I am hoping someone will be willing to help me understand something about hazard plots created with muhaz(...). ?I have some background in statistics (minor in grad school), but I haven't been able to figure one thing about hazard plots. ?I am using hazard plots to track customer cancellations. ?I figure I can treat a cancellation as a "death", and if someone is still a

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 ?

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