similar to: Powerware 9125 working w/ SNMP

Thanks to the great help here, I now have a UPS spitting out something resembling a report descriptor. So since I seem destined to have to create a new USB HID subdriver, I figured I'd get started on the path. I followed all of the directions on the web....I used the script to generate the usbhid subdriver, feeding it the output of the usbhid-ups driver from reading my UPS. All that worked

Hello! It looks like bcmxcp driver doesn't fit my device: UPS Model ? ? ? ? ? ? ? ? ? ?PW9125 UPS Firmware Version ? ?FP: 1.10 INV: 1.10 VA Rating ? ? ? ? ? ? ? ? ? ? ?3000 VA Web/SNMP card is present. Minicom connection to /dev/ttyS0 gives nice banner and control menu, but they prevent nut driver from working correctly (I guess). UPS should be switched into "Pass-Through" mode

Hello! It looks like bcmxcp driver doesn't fit my device: UPS Model ? ? ? ? ? ? ? ? ? ?PW9125 UPS Firmware Version ? ?FP: 1.10 INV: 1.10 VA Rating ? ? ? ? ? ? ? ? ? ? ?3000 VA Web/SNMP card is present. Minicom connection to /dev/ttyS0 gives nice banner and control menu, but they prevent nut driver from working correctly (I guess). UPS should be switched into "Pass-Through" mode

Den 14-03-2014 21:29, Rob Groner skrev: > It works pretty good after that. However, if I'm going to tailor > my hid2nut table, it would really help if there was some master list > of all the paths (input.voltage, battery.temperature, etc) NUT supports, > instead of having to dig through different driver files to see what's available. Is there some list? How about

I'm trying to set up nut with a MGE UPS equiupped with a network management card, but encountered a problem. UPS: MGE Pulsar M 3000 Network Management card (installed in the UPS): 66102 (2006 edition) Operating system: FreeBSD Nut port version: 2.0.5 Nut driver: snmp-ups According to MGE in Norway this card is supported by nut, but only the old version of the card (66244) is listed on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Has anyone gotten it working at all with Linux :) I picked one up for thiry bucks and would love to monitor it! Liz - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD/5fEIACpLcG4dhwRAmeCAJ9+8FGXqKoOlZdkw/KFXb9n0PEemwCdHaoD NVnv7JjmBAjNsExK6WzAdnA= =pcPX - -----END PGP

2006/4/4, Niels Baggesen <nba@users.sourceforge.net>: > On Tue, Apr 04, 2006 at 10:57:51PM +0200, Nick Rosier wrote: > > Again, with an unstripped version of newhidups. But it doesn't seem to > > give more information; no core dump either. Anything else I can try? > > Strace it and hope the file doesn't fill up my disk :-) > > It is probably better to try

Hi developers, the current setup when doing a make (even a make -s) is very noisy, and makes it very easy to miss warnings from gcc. I would like to add a --slient option to libtool. How do the rest of you feel about that? /Niels -- Niels Baggesen - @home - ?rhus - Denmark - nba@users.sourceforge.net The purpose of computing is insight, not numbers --- R W Hamming

I've recently moved from installing NUT from source to installing NUT from the FreeBSD package (FreeBSD 9.1). One would think that I might have learned not to change anything, but I made the change. And here is my tale of woe..... My first question is: is it possible to simulate a "UPS is on battery" state? Some background: UPS comm port is connected to and monitored by

With automake, we collectively need to check to see if 'make distcheck' still works after adding or removing files. Basically, nothing will make its way into the NUT distribution tarball unless it is somehow mentioned in one of the Makefile.am files. See the packaging/RedHat directory for an example. Niels, thank you for spotting the extra nut.spec file in SVN; however, it needs to be

Great, thanks! Two questions: * what is a domain literal? Is this something like 192.168.0.1? In this case, the '[]' are probably unnecessary. * are you sure you want to use fprintf(stderr, ...) in a library? This doesn't seem like a good idea to me. Wouldn't it be more consistent to extend upscli_errlist[] ? -- Peter Arjen de Korte wrote: > > Author:

I've got persistent trouble getting nut to work, though I think I've done everything by the book (the Debian specific readme included). I've tracked it down to upsd not working as it should: it just won't keep going. :( I.e. checking the process list (or using its reload command) shows that there just isn't a upsd process, at all. Starting upsd with a few -D's for

I'm access nut online via localhost. But I have the following problems. When I click on Statistics I get cannot open /etc/hosts.conf. When I click on settings I get: Error: Can't open upsset.conf to verify security settings. Refusing to start until this is fixed. I have .htaccess in cgi-bin with the following: <Files upsset.cgi> deny from all allow from 127.0.0.1 </Files>

Hi, just through setting up nut-2.0.2 I ran into a shutdown problem. As I have already spend some time on it and don't know any further, I like to ask for advice. Situation: Powerware 9125 serially connected using /dev/cua0 nut compiled and installed fine system shall - broadcast a message and shut down if ups on battery for 30+ s - wait 120 s - broadcast another message - give system 120

On Sep 19, 2014, at 4:03 PM, Nello Lucchesi <nello at octobergroup.com> wrote: > I'm looking for a driver for and old uninterruptible power supply (UPS), Eaton Powerware 9125 2500U. I want to use it with my FreeNAS server. > > I looked a the list and didn't see a driver for it: > > http://www.networkupstools.org/stable-hcl.html?manufacturer=Eaton > > I see a

I'm looking for a driver for and old uninterruptible power supply (UPS), Eaton Powerware 9125 2500U. I want to use it with my FreeNAS server. I looked a the list and didn't see a driver for it: http://www.networkupstools.org/stable-hcl.html?manufacturer=Eaton I see a driver for the 9130; any idea whether it will work with a 9125? Any other ideas for connecting the 9125 to a FreeNAS

> Author: nba-guest > Date: Mon Apr 24 20:45:39 2006 > New Revision: 414 > > Modified: > trunk/CHANGES > trunk/drivers/cpsups.c > Log: > Fix C++ style declarations between statements > > Modified: trunk/CHANGES Niels, What is the reason for 'fixing' this? Constructions like these are used in many locations throughout the sources (not only in the

Hi - I have 5 Linux servers connected to 1 SmartUPS 2200 VA. The software from APC for Linux requires a Windows machine be present on the network as a server in order to manage the Linux machines. This is a show stopper for us since we don't have access to any Windows machines. My first impression of NUT is it can shutdown the machine connected to the UPS via the serial cable but it

I'm currently testing the bcmxcp driver for NUT, and it causes me some trouble. And when scanning the archives it seems like the 3110 USB problem reported recently. The bcmxcp daemon stops running, and the logs shows the following: Oct 6 14:22:32 host.dom.tld bcmxcp[82628]: Communications with UPS lost: Receive error (data): got -1 bytes instead of 28!!! Oct 6 14:22:33 host.dom.tld

Bugs item #20455, was opened at 2008-05-30 16:54 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=20455&group_id=85 Category: None Group: Code Status: Open Resolution: None Priority: 3 Submitted By: Nobody (None) Assigned to: Nobody (None) Summary: win32-open3: crashes after 170 popen3 operations Initial Comment: OS: XP w/SP2 C:\Documents and