search for: claesson

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

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 Ubuntu9:/lib/nut# ./bcmxcp_usb -a PowerWare -u root Network...

OK Eric, Den Tuesday 22 May 2007 08.56.08 skrev Eric S. Raymond: > Kjell Claesson <kjell.claesson at epost.tidanet.se>: > > Or install the udev rules and replug the ups. > > Did that. Manual startup of the driver now works without -u root, > indicating (I think) that the udev rools are doing their job. This > 8<-----------------------Snip------------...

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

Hi I set up my ups with driver snmp-ups, and it get recognized as a AEC T2003. In the nut-cgi upstats page input/output/load are displayed corectly, but the Status field is marked as "Not supported". Is "Status" important to initiate shutdown in case of low battery ? Will my server shut down correctly ? thanks Massimo I include "upsc snmp@localhost" output:

Hi, Made a test build of the Testing branch. The problem is that upsmon and upsc is not respecting the revision change of libupsclient.so. It is now libupsclient.so.1, but i get this. /usr/sbin/upsmon: error while loading shared libraries: libupsclient.so.0: cannot open shared object file: No such file or directory and: upsc: error while loading shared libraries: libupsclient.so.0: cannot

Hi, Need to get an answer to the following. I find the naming to be little redundant regarding the 'input.transfer.boost.low - hige'. The same goes for input.transfer.trim.low - high. As I find it, there is only one point where the boost or buck (trim) kicks in. Let's say that the nominal voltage is 230 volt, then we have a input.transfer.boost point on say 220 volt. If the

What rigs do you folks use to listen to your music? I have a P-III 500 with Altec Lansing speakers in the dining room and a P-II 350 with Labtec speakers in the Guestroom/office. Sorry, I can't remember what model the Lansings are off the top of my head. The Labtec speakers are fairly cheap. I have a PCI ensonique sound card in the P-III system. I not sure what kind of sound card is in the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Has anyone used nut with a XPCC UPS, in particular one of the XVRT units? Their supplied monitoring tool "works", but I'd really prefer to use nut if possible. I've systematically gone through each of the drivers in /lib/nut and none seem to talk with the unit properly. I'll be talking with a XPCC support person tomorrow, though

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

All, I have a Cyberpower UPS that I have been working with for about a year. I have used NUT in the past with good results, but as of late have been seeing issues with nut talking to the UPS. I will start with the information on the server that is running NUT, and has the UPS connected VIA an RS232 cable. O/S : Fedora 9 Kernal (uname -a): Linux haruhi 2.6.26.5-45.fc9.x86_64 #1 SMP Sat

All, I have a Cyberpower UPS that I have been working with for about a year. I have used NUT in the past with good results, but as of late have been seeing issues with nut talking to the UPS. I will start with the information on the server that is running NUT, and has the UPS connected VIA an RS232 cable. O/S : Fedora 9 Kernal (uname -a): Linux haruhi 2.6.26.5-45.fc9.x86_64 #1 SMP Sat

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 (2.0.5) Communications with UPS lost: Error executing comma...

tisdagen den 16 december 2014 15.36.29 skrev Frantz de Germain: > Hello, Hi Frantz, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. > I've got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of > this message)" > > I've been looking for "pollonly" in

Hello all, I have obtained a Compaq T700 H UPS sans-cable. My research indicates it would've come with a HP #201092-001 cable, and from previous posts on this list, it speaks upscode2, possibly being a rebadged Eaton unit. Any suggestions for cable pinouts I can try? Regards, Mathew McBride

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

Hi all, Have a strange behaviour that I don't know how to debug. This is when I use the Eaton PW5125 ups. I have it connected And running in standby. Starting up the drivers (pw3105 and pw5125) and they run. Start up the upsd and can read info from both of them. The 3105 is supplying the computer and the 5125 have a dummy load. The 5125 is showing that it is off line. Now when I hit the on

Hi all, Arjen can you enlighten me about the function of the blazer upsdrv_shutdown function. I think they are in the wrong order. Regards Kjell

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

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