similar to: bcmxcp patch

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

UPS: HP R3000 XR with HP UPS Management Module What I Want: I just want the UPS to shut down the client called "tor" before the UPS power drains out, I'd prefer to use a direct serial cable instead of network, in case the network doesn't work. I'll manage the UPS trough the ethernet using the built-in HTTP webinterface in the HP UPS Management Module. I've created a

Hi, just through setting up nut-2.0.2 I ran into a shutdown problem. As I have already spend some time on it and don't know any further, I like to ask for advice. Situation: Powerware 9125 serially connected using /dev/cua0 nut compiled and installed fine system shall - broadcast a message and shut down if ups on battery for 30+ s - wait 120 s - broadcast another message - give system 120

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, 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 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 output.frequency 0.475634 0028 0004 51 input.frequency 0.475641 0033 0008 51 battery.voltage

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

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

I'm trying to get a Powerware 5125 UPS running using the bcmxcp driver, but I get the following errors: video2:~# /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing

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

I'm currently testing the bcmxcp driver for NUT, and it causes me some trouble. And when scanning the archives it seems like the 3110 USB problem reported recently. The bcmxcp daemon stops running, and the logs shows the following: Oct 6 14:22:32 host.dom.tld bcmxcp[82628]: Communications with UPS lost: Receive error (data): got -1 bytes instead of 28!!! Oct 6 14:22:33 host.dom.tld

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

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 All, I'm trying to communication with the HP r3000 XR UP using the latest stable build and I'm getting the following errors. Can anyone enlighten me with the errors below and what other course of action I can take. Thanks in advance. Paul. [root@WRRFtpServer etc]# /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS

Hi Inspired by the changes by Prachi Gandhi to use the command map from the UPS in the bcmxcp driver, I think the map should be used, if available, to control all commands the driver adds using "dstate_addcmd". The following patch is an attempt at doing so. The patch is against the bcmxcp branch. Since my UPS also supports : #define PW_UPS_ON (unsigned char)0x89 /* UPS on

Hi, I can't find a nice way to solve a problem. So if you have some ideas I would be greatfull. This is the problem. I can ask a bcmxcp ups what commands it support, if the firmware is after revision AE. I was thinking about to use this in the driver. For example ' a ups that don't support battery_test would not have this command enabled.' The hex responce look like this from

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

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 -

Greetings, I've just installed nut-2.4.1 on a Solaris 10 x86 machine to monitor a HP R3000XR UPS. SunOS babylon4 5.10 Generic_138889-08 i86pc i386 i86pc Solaris First of all, I encountered a single problem during the build. After configuring, drivers/Makefile ends up containing the following line: LIBNETSNMP_LDFLAGS = -R../lib -L/usr/sfw/lib -lnetsnmp -lgen [...] This is clearly