similar to: MGE UPS Comet EX RT 7 not setting LB

Hi everyone, We just got an MGE Comet EX 11 RT with extra battery (all 250kg of it..) and I have talked to it with NUT. One thing I see is the frequency.. input.frequency: 500 output.frequency: 500 It appears to be in tenths of a Hz vs Hz as I see on a Pulsar Extreme. I'm using NUT 2.0.3 on FreeBSD 6.1 Thanks. -- Daniel O'Connor software and network engineer for Genesis Software -

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

My $0.02: LB is baked in to nut behavior. So if a UPS doesn't report LB, then it makes sense to synthesize it. Synthetic LB is the cleanest fix at the earlier processing point. One could have a config that is basically synthetic-lowbatt-percent that generates LB if (as Jim says) on battery, not calibrating, and batt% <= that. One could have a similar config

Hi Sabine and Christoph, I've just committed a few changes to mge-utalk (r2749). can you please try a snapshot and report back the results: http://new.networkupstools.org/download.html#Snapshots cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

Makes sense, and a PR is a way to solicit feedback :) I'd document this for ups.conf (man page and examples), including a note that for devices which do provide a healthy LB these values may be set to 0 safely. Wondering if non-zero defaults should be there anyway. @Community, WDYT? Also, this critical-state check should be done only when the UPS is on battery (and perhaps not calibrating),

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

First of all, please forgive me is this question has already been covered in these mailing lists; the "Search mailing list" link is dead, and I've only read the most recent monthly archives. I often have a situation where, for one of many possible reasons, the UPS always thinks that its battery is critical. And I'm even fine with a situation when it's an emergency

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

Hi, We have been testing an MGE Pulsar M 3000 and found that the lowbatt doesn't appear to do much. You can see it in the output of upsc but battery.charge.low is still the default. Setting battery.charge.low with upsrw does seem to 'stick' though so I we can use that. Mostly I'm wondering what the driver param is for :) -- Daniel O'Connor software and network engineer

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

The UPS is connected to the following environment: OS: Debian GNU/Linux 9.6 (stretch) NUT version: 2.7.4-5 Device output from lsusb: 0463:ffff MGE UPS Systems UPS Model name: MGE EllipseMAX 1500 URLs: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-MAX-eol.aspx?cx=97&GUID=7BB6CD53-9F6D-4D62-B326-1099F137BF8D http://powerquality.eaton.com/68558.aspx?cx=97 The problem

On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines

On December 2, 2018 7:29:38 PM GMT+02:00, raul <raulvior.bcn at gmail.com> wrote: >I have restored original configuration and enabled the ignorelb flag. I > >didn't point out in the original e-mail that after every poweroff the >battery percentage is reported at 40% instead of 100% and charges >slowly again to 100%. Maybe the UPS sends a LB event and shuts down

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

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

Hi everybody, Sorry for the eternity it took to solve the UTalk problems, but I've been busy on so many fronts... I've updated the CVS Testing tree, which will soon become 2.0.3 stable release, with mge-utalk 0.87. This release fixes the UTalk problems you have recently faced. If possible, please test it and report back if it work or not with your unit. To do so: 1) Retrieve the source

Linux-2.4.28 libusb-0.1.8 nut-2.6.5 [+most recent drivers from GIT] - from tarball EATON 3S700DIN [mfr.date 09/28/14] ---------------------------------- ISSUES: I) Too many kernel logs: --- In /var/log/kernel.log usbdevfs: usb_submit_urb returned -28 In /var/log/daemon.log: usbhid-ups[744]: libusb_get_interrupt: No error usbhid-ups[744]: libusb_get_interrupt: error submitting URB: No space left

Hello, I'm experiencing a strange early shutdown behavior with the following system: * */OS/*: Slackware Linux 14.2 x86_64 * */NUT/*: 2.7.4 (from my own package <https://sotirov-bg.net/slackpack/pack.cgi?id=4083>) * */UPS/*: MGE Ellipse PRO 1600 <powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-PRO.aspx> (bought in September 2017) */Problem

Arnaud, > first, even if your battery is full, and your ups is online, there is a > small amount of power drawn. So having always is CHRG status is normal. > In fact, these complementary status are more interesting for higher end > UPSs. > > second, these status need not to be handled like LB, as each one clears the > other. While LB had no pending event (!LB) before... >

On Jan 11, 2015, at 11:48 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: >> The file drivers/usbhid-ups.c is looking for any of the following conditions to declare LB: >> >> ? STATUS(LOWBATT) >> ? STATUS(TIMELIMITEXP) >> ? STATUS(SHUTDOWNIMM) >> >> The mapping to HID Path names will depend on the model, but STATUS(LOWBATT) can come