similar to: Welcoming a new NUT Team member

[was: svn commit r915 - in trunk: . drivers] Hi Kjell, sorry, I'm still much late in emptying my mail stack... 2007/5/25, Kjell Claesson <kjell.claesson at epost.tidanet.se>: > Den Friday 25 May 2007 08.52.20 skrev Arnaud Quette: > > > > I would be interested in some more info: > > - lshal -u <your device's UDI> > > the UDI can be obtained for ex.

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

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 fellows, I would like to welcome a new member in the Development Team: Jonathan Dion, who is a trainee engineer from the ENSIMAG school, and who will work on the Configuration sub project. He will soon post a draft specification (off list link) to start discussing that subject. This sub project has long been postponed, and I'm sure Jonathan will produce good work on this, allowing us to

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

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

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:

Citeren Kjell Claesson <keyson-guest op alioth.debian.org>: > Author: keyson-guest > Date: Mon Mar 23 17:37:37 2009 > New Revision: 1817 > > Log: > data/driver.list, add Eaton Powerware 9130 compatibility with bcmxcp > and usbhid-ups. 1) Is this really true? I would have expected that this device would be supported through bcmxcp (serial) and bcmxcp_usb (USB), like

tisdagen den 2 juli 2013 20.24.47 skrev Alf H?gemark: > Hi > Hi Alf, > I have the following UPS : > ups.mfr: Eaton > ups.model: POWERWARE UPS 500i > ups.power.nominal: 500 > > It is using the bcmxcp_usb driver. > > I started the driver with debug options, and noticed the following for > the meter map : > > 0.475625 0027 0000 51

On Jul 2, 2013, at 5:16 PM, Kjell Claesson wrote: >> I hope other people can also test this. >> >> Regards >> Alf Hogemark > > Due to some crashes on the disks and lack of time I don't have the git on the > pc now. But maybe some other can commit this. I'd like to ask people to specifically try the bcmxcp branch on GitHub - it includes some changes

Hi, So far I've gleaned heaps of useful info from the list and got mostly running with NUT. There was a thread by Paul Battaglia and Kjell Claesson about the R3000 which has helped me get so far, but now with the patched driver I still have this on startup: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS driver 0.11

On 6/29/2013 at 6:16 PM Kjell Claesson wrote: |l??rdagen den 29 juni 2013 11.28.14 skrev Mike.: |8<------------------snip--------------------- |Hi Mike, |> |> Thanks for the quick reply. |> |> I checked the log file (which, admittedly, I should have done before I |> posted about the problem :) ). |> |> Here's the command and the corresponding log message: |>

Hi Alexander, > I've UPS named PowerMan RealSmart 1000, it is not listed in > compatibility list. I found that it works with "fentonups" driver and > have ups.model "Unknown S163-1000". Ithink "1000" is from capacity - > I've seen in Internet someone have RealSmart 800 identified "S163-800". > Also PowerMan have

l?rdagen den 29 juni 2013 15.22.44 skrev Mike.: 8<-------------snip----------------- Sorry for the delay. > Here is the console output of bcmxcp with -DDD specified: > > > [snip] > 13.721204 Auto delay on: 2 > > 13.721243 send_command: (4 bytes) => ab 01 35 1f > 13.821127 send_command: (4 bytes) => ab 01 33 21 > 13.920982

Hi Denny. Nice, i have entered the HP R5500 XR to the drivers.list in the Testing and Development tree. Some info for you when you setup the nut. The shutdown_delay of the driver is internal to the ups. It calculate the time it can run after low-battery with the load. So when it comes to OB LB it starts the shutdown_delay and power off after it runs out. This is the normal way, as you would

Dear NUT users and developers, A bit later than usual, here is the traditional end of the year mail to sum up the past year, think about the future and make some announcements. Those of you who have followed closely the project already know: 2008 has been a harder year than ever. And the UPS world has somehow finished a full revamp cycle, started 2 years ago! * A new sponsor: Last year,

Hi, Got this mail. It looks like he has a ups with revision before K, and need another startup. The 'PW_SET_REQ_ONLY_MODE' is not implemented, so to make it work we have to follow the protocol and send a 'PW_ID_BLOCK_REQ'. This in comsetup of bcmxcp_ser.c Also the standard id block ends with 'Statistics Map', so we have to Skip after reading the length of the 'Size

Hi. Have back-ported the bcmxcp and bcmxcp_usb driver from Development. I hope it's done right. Tested a clean cvs fetch after commit and it build and install ok. Regards Kjell

Dears, I finally resolve my problem, I just make symbolic link: [test at box var/run/]# ln -s -T /var/state/ups/ nut Now I finally got services online: # /sbin/service ups start Starting UPS driver controller: [ OK ] Starting upsd: [ OK ] Starting UPS monitor (master): [ OK ] BUT, on upsc I