similar to: Scheduling a 2.2.1 release

Hi Kjell, a few notes: - you should bump the DRV_VERSION upon every change - you should track the drivers TODO list in a comment header (such as "implement smart load segment detection" completed with your info, ...). That would help to bootstrap new contributors. - you can also use the alioth trackers (features request, or task) to give some external visibility on what remains to be

Hi Michael, I've forwarded your patch to Kjell, who's maintaining the bcmxcp driver, and to the nut development list. Kjell and others have more knowledges of the xcp protocol and will be able to analyze your patch. 2008/1/4, michalwd1979 <michalwd1979 at o2.pl>: > Hello Arnaud, > I am sending You a small patch to bcmxcp.c and bcmxcp.h files from nut-2.2.0. I written this

Fellows, the -pre branch for 2.2.2 is opened. If you have something to backport for trunk or fix in Testing, it's time to do so. If you are unsure, don't hesitate to ask me or on this list. I'd like to see 2.2.2 going out soon (~2 weeks max) Arnaud -- Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com Network UPS Tools (NUT) Project Leader -

Hi Matthijs, > Arnaud. >After some trial and error, i found out that the HP R3000 XR ups's we have >can be used with Network Ups Tools. >This using the bcmxcp driver. > >Note that in the code of this driver (line 1420) , the Baudrate is fixed to >9600 baud. >to connect to a serial HP R3000 XR ups one needs to change this to 19200 >baud. > >ideally, this should

Hi Georg, > one question with regard to a Powerware 5115 UPS connected to a Debian 3.1 > Sarge box via USB: I downloaded and compiled nut 2.0.2 but I am unable to > configure the USB subsystem so that upsdrvctl recognizes the UPS. > > My /usr/local/ups/etc/ups.conf contains: > > [bla] > driver = bcmxcp > port = /dev/usbdev2.2 > desc = "bla bla

Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog

Network UPS Tools version 2.0.5 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.0/nut-2.0.5.tar.gz - News: http://www.networkupstools.org/source/2.0/new-2.0.5.txt - ChangeLog: http://www.networkupstools.org/source/2.0/ChangeLog

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

tags 439986 upstream thanks Hi Florian, 2007/8/29, Florian Forster <octo at verplant.org>: > Package: nut-dev > Version: 2.2.0-1 > Severity: minor > > After upgrading from version 2.0.something to version 2.2.0-1 the type > `UPSCONN' had been renamed to `UPSCONN_t'. This is a problem for > software that is supposed to work with different versions of this >

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

Are there driver to this device it works? I trie with 9130 and 9140 driver but didn't work. Thanks Ignacio Fridemberg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20121025/af016ac1/attachment.html>

Hello: I have a UPS model MXE II MAXIM brand online, 3500VA 2100W. Connects to the PC by a USB 2.0 port. I wanted to use nut, but this brand is not on the list of nut drivers. lsusb returns: ... Bus 003 Device 003: ID 06DA: 0201 Phoenixtec Power Co., Ltd ... I did not find this manufacturer in the driver list. Anyone know if you can have compatibility with other make and model of UPS. With

Adam: Thanks for putting up this page. But something is wrong. In particular, our Powerware 9135 is a three phase UPS system with THREE 480 volt outputs. So the displayed voltage is not correct -- in fact there should really be THREE voltages displayed, all around 480v. Nut developers: I am copying the NUT mailing list to see if anyone can suggest how to fix this. NUT developers, see the

Fellows, time has come for a new NUT release: I'm planning on 2.6.1 next week (max Friday 27), and I'm currently processing remaining patches. If you have some more on your side, please send in. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer -

Hi, I have an HP R5500XR and a Compaq R3000XR that I would like to use with nut. I searched the compatibility lists and the mail list archives but couldn't find anything. They both have 9 pin serial ports. Can anyone give me any information about them, and if they are supported by nut? Thanks, Denny Fox

Network UPS Tools version 2.2.1-pre1 has been released. http://www.networkupstools.org/ Note that a transition is underway for both the NUT domain name and the webserver. So you might face few minor problems... USB UPS owners are also warmly welcome to test the shutdown function of their device. Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.1-pre1.tar.gz

Attached is a patch to hopefully improve the wording of some of the man pages. I will commit this in the next few days, but I wanted to give the driver authors a chance to comment. One thing that I feel is important is cross-referencing between the man pages. On the off-chance that someone does RTFM, it would be good if we make sure that a user doesn't have to read too far in order to find

I have setup nut-2.4.1 with the bcmxcp driver for my HP R3000 XR unit and although it appears to work, I receive the following sorts of errors in syslog: Aug 27 10:33:05 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (data): got 0 bytes instead of 64!!! Aug 27 10:33:15 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (data): got 0 bytes instead of 64!!! Aug 27

I'll be back one more time perhaps I found the reason of these errors Nov 13 11:09:22 mezenc upsmon[3865]: Poll UPS [mgeups at localhost] failed - Data stale it happens when daemon upsd et upsmon are started after the boot obviously, there isn't any errors when upsd and upsmon are started at boot following later ... -----Message d'origine----- De : goudard sabine Envoy? : mardi

I decided to try this to see if it worked better since Powerware decided to build in some oddball USB protocol instead of using a HID UPS profile, but it doesn't seem to work. The USB/serial dongle is recognized by Linux and added as /dev/ttyUSB0, owned by group "dialout", so I had to add the nut user to the dialout group. In the compatibility list, the proper driver for the