similar to: Differences between USB and serial on an MGE Pulsar Evolution 3000

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

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 have a FreeBSD 9.2 system with NUT 2.6.5 (installed via the ports tree) with an MGE Pulsar 1500 connected. A while ago it complained it needed the battery replaced and it was finally replaced last week, however I can't find out how to reset the flag in NUT. I've looked in upsc, upsrw and upscmd but none seem to have a suitable option. The UPS is connected via RS232 and upsc output

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

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, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():

We have several systems in remote locations and I have found that the ones in the US are having issues.. We are an Australian company and can't source a 110V UPS locally so we arrange to have one bought for the site when it's installed. It seems that in the US we are getting "Pulsar EX 1500" UPSs but locally we buy "Pulsar 1500". NUT seems to work find with the

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hello, we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server using a serial cable. Installed and configured properly are RPM versions of nut-2.0.3-0.1.fc5 nut-client-2.0.3-0.1.fc5 nut-cgi-2.0.3-0.1.fc5 which all work (mostly) fine. The server is connected to outlet.0 and properly shuts down when it's loosing power after around 20 minutes. It also boots up whenever the ups

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

On Fri, Sep 11, 2020, at 4:05 PM, Bartosz wrote: > Dear All, > > Could you please recommend me a UPS with 100% support of the ondelay parameter and NUT compatibility? > > 850 or 1000 VA > > I have the EATON 5E850iUSBDIN UPS and it does not support this parameter so I would like to buy another UPS that for sure will support it. > > Thank you, > Bart Can you tell

Hello Niels, thanks a lot for this compatibility submission. This is part of the remaining things at Eaton. I've added an entry to the new Hardware Compatibility List: http://new.networkupstools.org/stable-hcl.html BTW, have you tested a shutdown with this unit? Otherwise, you should! thanks again, Arnaud Quette Le samedi 02 octobre 2010 ? 12:42 +0200, Niels Kristian Jensen a ?crit :

Hi, FINALLY got my UPS working, YEA!!!! But now it brings up even more issues.. (BOOO!!) 1) I'm thinking this is a UPS issue, but when I pull the plug on my UPS, it goes from 100 to 30 in just a short amount of time (Minutes). This causes the machine to shut down. But once it gets to 0, its beeped its little heart out for a few more HOURS providing power to the non-system items perfectly.

On Fri, Sep 25, 2020 at 11:47:42PM +0300, Manuel Wolfshant wrote: > On 9/25/20 1:36 PM, Lionel Élie Mamane wrote: >> On Thu, Sep 24, 2020 at 06:51:23PM +0300, Manuel Wolfshant wrote: >>> On 9/21/20 9:47 PM, Lionel Élie Mamane wrote: >>> We have a HP R/T 3000 G4 UPS; according to the data returned by >>> the usbhid-ups driver, it seems to be a "badge

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]

OS version: FreeBSD 8.4-RELEASE-p19 NUT version: nut-2.7.2_6 NUT installation method: from freebsd pkg system Device info: EATON 9SX 5000i, manufacturing date: 05.09.2014 ups.firmware: 9SX5Ki When i try to see battery charge, in output it have not such variable, and i can't control my server and other clients connected to them. Any options cannot power of server. How to see current battery

Hi, This might be a simple thing to fix, but I can?t figure it out. We replaced the battery for the first time in our Eaton 5PX a couple of weeks ago, but we haven?t been able to clear the ?ups.alarm: replace battery!? status. Details of our installation are: OS: Debian 6 NUT version: 2.7.4 Installation method: from source tarball UPS device: Eaton 5PX2000IRT, 240V, 1800W, 2000VA, bought in