similar to: 2.2.2 -pre backports open

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

[I'm switching my dev address to @gmail.com instead of @mgeups... please, update your bookmark] Peter Selinger wrote: > > Arnaud Quette wrote: > > > > Here is the status of PSE (Peter Selinger) NUT patches > > for newhidups (hidparser, apc support, ...). > > > > - nut-cvs-patch-REOPEN-2005-08-24: > > approved and applied on Development tree > >

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with

Kjell Claesson wrote: > Then i have a problem. My computer is down due to a > faulty mainboard, Youch. I hate it when that heppens. Hope it wasn't because you got a power spike ;-) Let me or Georg know if you want us to run any debug code. Feels like a bcmxcp_usb driver bug to me since the bcmcxp serial driver works fine and all my other USB devices work fine (wifi adapter, memory

Hi. I'm from Russia. I try to use NUT with PowerWalker vi 400 se (usb). I use FreeBSD 7.0 (amd64) and megatec_usb driver. Settingup the NUT with FreeBSD installation procedure (Thierry Thomas, from FreeBSD). PowerWalker connect to the computer by usb cable on port usb0 (uhib0). NUT don't starting, and talk to me that supporting device not found. Please, help me. Thank's! With best

Ok, I installed the ups, and installed nut, and /proc/bus/usb/devices says this T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=06da ProdID=0002 Rev= 0.01 S: Manufacturer=POWERWARE S: Product=Powerware UPS C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 20mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a little patch for the drivers.list The "Cyber Power Systems Intelligent Series CP1500EAVRLCD" ups http://eu.cyberpowersystems.com/products/ups_systems/intelligent/cp1500eavrlcd.htm Got one here running (see: https://nut.stillbilde.net/cgi-bin/nut/upsstats.cgi?host=CyberPower at upsmonitor) Works flawlessly. Patch as follows:

On Mon, May 12, 2008 at 7:58 AM, Charles Lepple <clepple at gmail.com> wrote: > One thing I just noticed with the recent backport of packaging/debian > from branches/Testing is that we will probably want to keep separate > versions of packaging/debian for internal testing versus official > releases. Right now, "debuild -us -uc" from the trunk (rev 1490) >

Hi fellows, I'm really pleased to announce that a first stage of NUT and HAL [1] integration has been reached: NUT drivers (in fact, only newhidups, tripplite_usb and bcmxcp_usb for the moment) can feed HAL data. It's a "quick and dirty" hack, as a proof of concept, and there is still lots of things to be done, both on NUT and HAL sides. But it's a good base, and very

2009/5/3 Thomas Juerges > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Arnaud, > Hi Thomas, > I just checked the 2.4.1 version of nut and found that you forgot to add > my old UPS model (APC Smart-UPS 900). I guess it is because you were > busy at the time when I sent you the patch. So here it goes again. :) > uh, right sorry. I was pretty sure I applied

Hello together, attached is a small compile fix for nut 2.2.2, again it's my friend "struct timeval" which was undefined without the #include statement. Cheers, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: nut-fix-compile.patch Type: text/x-diff Size: 318 bytes Desc: not available Url :

Network UPS Tools version 2.2.2-pre2 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.2-pre2.tar.gz - News: http://www.networkupstools.org/source/2.2/testing/new-2.2.2-pre2.txt - ChangeLog: http://www.networkupstools.org/source/2.2/testing/ChangeLog Arnaud and the NUT team -- Linux / Unix Expert R&D -

Network UPS Tools version 2.2.2-pre1 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.2-pre1.tar.gz - News: http://www.networkupstools.org/source/2.2/testing/new-2.2.2-pre1.txt - ChangeLog: http://www.networkupstools.org/source/2.2/testing/ChangeLog Arnaud and the NUT team -- Linux / Unix Expert R&D -

On 5/23/07, Kjell Claesson <keyson-guest at alioth.debian.org> wrote: > Author: keyson-guest > Date: Wed May 23 21:12:51 2007 > New Revision: 915 > > Log: > - Enabled requested Alarm function in bcmxcp.c > > Modified: > trunk/ChangeLog > trunk/drivers/bcmxcp.c Looks like this breaks when HAL is enabled. At the end of:

Hi again, The PGP sig for 2.2.2 is missing from http://eu1.networkupstools.org/source/2.2/ (so the corresponding link from the download page is broken). Also, for the record, I'm trying to compile 2.2.2 from sources and so far, on my Ubuntu Hardy system : - If I don't use during configure "--without-snmp", compilation crashes talking about some undefined things. - If I use

I tried switching to the USB version of bcmxcp_usb and get this error when I try starting up upsdrvctl or bcmxcp_usb like so: /etc/nut/bcmxcp_usb -DDDD -a powerware -u nut I used this for ups.conf: [powerware] driver = bcmxcp_usb port = auto With the serial/usb dongle, I used this successfully: [powerware] driver = bcmxcp port = /dev/ttyUSB0 What devices does

I ordered some Powerware 3105 devices for Linux workstations. These devices only have an USB interface. I understood too late that support for Powerware devices is only available for the serial interface. Since the protocols over serial and USB seem to be identical, it was not too difficult to modify the bcmxcp driver to support USB. The new and changed files can be found here:

Hi Arnaud, Any luck with the latest subversion trunk? From: Greg Sent: Wednesday, May 13, 2009 10:34 PM To: Greg ; Arnaud Quette Cc: Kjell Claesson ; nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] Nut and PowerWare 5115 Hi Arnaud, Some more testing on Ubuntu 9.04. Here is the output of bcmxcp_usb and lsusb ============================================ root at

On Wed, Oct 1, 2008 at 7:30 AM, Roman Serbski <mefystofel at gmail.com> wrote: >> Definitely seems like a permissions problem. >> >> It's been a while since I messed with USB on FreeBSD. What do the >> permissions look like on /dev/ugen*? What modifications did you make >> to /etc/devfs.rules? > > Thanks a lot Charles! I think I managed to get NUT

* I committed into CVS the gendb patch that I sent to the mailing list on September 12. Arnaud, I hope you approve of this patch; it is more reliable than the previous method in tracking the correct dependencies. * This, together with some other minor recent changes on the Development branch, is between the "before_PSE_3" and "after_PSE_3" tags. Arnaud: if you