similar to: Resetting replace battery status on Pulsar 1500

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

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

On May 26, 2014, at 4:05 AM, "Daniel O'Connor" <doconnor at gsoft.com.au> wrote: > I've looked in upsc, upsrw and upscmd but none seem to have a suitable option. Is there a "battery.test" command, or similar?

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

On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote: >> What would log it? > > The driver. OK. >> I could try running the driver with debugging and see if that shows anything of interest. > > That should help. Unfortunately for non-debug operation, it appears that most of the usbhid-ups instcmd messages are buried at debug level 3 or 5. That

On May 27, 2014, at 9:59 PM, Daniel O'Connor wrote: > > On 28 May 2014, at 10:54, Charles Lepple <clepple at gmail.com> wrote: >> On May 26, 2014, at 8:21 PM, Daniel O'Connor wrote: >> >>> However if I do either of the tests upscmd just reports 'OK' and nothing happens. >> >> Anything in syslog? > > Not that I can see :( >

On May 28, 2014, at 8:59 PM, Daniel O'Connor wrote: > On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote: >>> What would log it? >> >> The driver. > > OK. > >>> I could try running the driver with debugging and see if that shows anything of interest. >> >> That should help. Unfortunately for non-debug

On 28 May 2014, at 10:54, Charles Lepple <clepple at gmail.com> wrote: > On May 26, 2014, at 8:21 PM, Daniel O'Connor wrote: > >> However if I do either of the tests upscmd just reports 'OK' and nothing happens. > > Anything in syslog? Not that I can see :( What would log it? I could try running the driver with debugging and see if that shows anything of

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

On 26 May 2014, at 23:26, Charles Lepple <clepple at gmail.com> wrote: > On May 26, 2014, at 4:05 AM, "Daniel O'Connor" <doconnor at gsoft.com.au> wrote: > >> I've looked in upsc, upsrw and upscmd but none seem to have a suitable option. > > Is there a "battery.test" command, or similar? There are these commands.. test.battery.start.deep

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

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

On May 26, 2014, at 8:21 PM, Daniel O'Connor wrote: > However if I do either of the tests upscmd just reports 'OK' and nothing happens. Anything in syslog? These commands should result in a self-test similar to the periodic one (the Evolution 500 does it every two weeks), but the "OK" from upscmd doesn't actually wait for the command to be executed. -- Charles

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