similar to: [nut-commits] svn commit r1019 - in trunk: . drivers

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

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

Also works if you want to shutdown one segment/outlet early in the power failure. It should stay off until utility power returns and then apply the configured delay - although I haven't tested this aspect. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: bcmxcp.c.diff Url:

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

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

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

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 -

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

1 - its on load blinking battery LEDs and not giving proper back up time . APC sua1000i nut-upsdev-request@lists.alioth.debian.org wrote: Send Nut-upsdev mailing list submissions to nut-upsdev@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev or, via email, send a message with subject or body

Hi Arnaud, Hi Scott, Hi list, Here is a patch to support the Zinto D from ONLINE USV-Systeme AG. I already sent a version to Russell Kroll (2006-04-09), without no response and I cannot find support for Zinto in svn until now. I found a discussion on this list about the Xanto from ONLINE, but the Zinto seems to use different commands. The commands are quite similar to those for Opti-UPS, so I

On Jun 29, 2013, at 9:45 AM, Mike. wrote: > On 6/29/2013 at 9:14 AM Mike. wrote: > > |NUT 2.6.5 on FreeBSD 9.1 > | > | > |Why isn't the variable outlet.1.delay.shutdown set with the following > |command? > | > | > | > |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" > |outlet.1.delay.shutdown: -1 > | > |# upsrw -u au -p ap -s

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 |

On 6/29/2013 at 9:59 AM Charles Lepple wrote: |On Jun 29, 2013, at 9:45 AM, Mike. wrote: | |> On 6/29/2013 at 9:14 AM Mike. wrote: |> |> |NUT 2.6.5 on FreeBSD 9.1 |> | |> | |> |Why isn't the variable outlet.1.delay.shutdown set with the following |> |command? |> | |> | |> | |> |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" |>

Hi! We have two MGE Evolution 1100 here, and I want to make use of the powershare outlets to force a particular boot sequence on the machines powered by them. However I'm not sure how to set those variables upon NUT starting, without having to change the init scripts to call "upsrw". Is there some place where I can set them, where they can be read automatically on startup? One of

Hi, I have several Linux machines at home and I'm considering buying a UPS for them. I see that many models are supported by NUT (great!) but since I'm new to the UPS world I have some questions about UPS features and NUT support of them I couldn't find an answer for: 1/ are there UPS models who report/meter power usage through USB? per UPS socket or globally? 2/ are there UPS models

Hi, Have a question regarding 'outlet.n.status'. In the new-names.txt it say on/off. The problem is that I get more than just on/off. I can get: 1 = On/Closed, 2 = Off/Open, 3 = On with Pending Off, 4 = Off with Pending On, 5 = Unknown, 6= Reserved/Unknown, 7= Failed and Closed, 8=Failed and Open. I only get a int but it is mapped to this meaning. I search the list if I asked this

This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it

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,