similar to: Question outlet.n.status

I am running NUT 2.2.0 compiled from the FreeBSD ports tree. [inchoate 14:50] ~ >upsc ups1 at localhost battery.charge: 59 battery.charge.low: 20 battery.charge.restart: 0 battery.runtime: 6350 battery.type: PbAc battery.voltage: 43.0 driver.name: usbhid-ups driver.parameter.offdelay: 120 driver.parameter.ondelay: 13 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version:

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

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

I ran into a portability issue with drivers/bcmxcp.c in nut-2.4.1 on my UnixWare 7.1.4 machine. The error I get is ..... UX:acomp: ERROR: "/opt/src/utils/nut-2.4.1/drivers/bcmxcp.c", line 835: integral constant expression expected ..... Looking at the code we see ..... int init_outlet(unsigned char len) { unsigned char answer[len]; ..... Although gcc can handle it, it's not

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

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

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: > > # upsrw -u au -p ap -s outlet.1.delay.shutdown=12

Hi, I've been getting emails from upsmon saying: Subject: UPS PW5125 at localhost notification: ONBATT UPS PW5125 at localhost on battery But then the machines on the UPS stay on for hours; we haven't got that kind of runtime, more like 10-20 minutes. After a few occurrences, it now happened at a time where I could log in to see in real time what is happening and: $ upsc PW5125 |

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 >

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

I've patched bcmxcp.c such that it can power cycle the outlet load segments independently on a Powerware PW5125 UPS. I presume that it will work for any XCP protocol UPS with 2 load segments. Should these instant commands be called outlet.1.shutdown.return outlet.2.shutdown.return ? Where do the descriptions displayed by upscmd -l come from? Presently it shows outlet.1.shutdown.return -

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

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

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

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

I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD

To all, I attempted to configure the UPS tools for the Tripp-Lite SmartOnline 1500VA 2U rackmount UPS. I followed the instructions from the 'upsdrvctl start' output and posted the diagnostic information below. Is my UPS using an unknown product ID as reported? From the mailing list archive, I have found another posting for the same UPS with device model '09AE/4003', whereas

So my Macbook''s battery sucks... and I''m thinking of grabbing a new one, I''m curious how the availability of power outlets have been at RailsConfs. For those who have gone before, was it hard to find an outlet to plug into? Are they mindful of this? I hope so. Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ You received this message because