similar to: Setvar in bcmxcp

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

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

Hi Here is a very minor patch for the bcmxcp.c driver, mainly fixing the function name used in debug statement, and at the same time fix indentation. Regards Alf Hogemark From 86c7940d0ea11b5b38a7f4518095ee2428d658c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alf=20H=C3=B8gemark?= <alf at i100.no> Date: Mon, 1 Jul 2013 21:11:40 +0200 Subject: [PATCH] bcmxcp: Fix method name outputted in

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

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

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

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

Hello! It looks like bcmxcp driver doesn't fit my device: UPS Model ? ? ? ? ? ? ? ? ? ?PW9125 UPS Firmware Version ? ?FP: 1.10 INV: 1.10 VA Rating ? ? ? ? ? ? ? ? ? ? ?3000 VA Web/SNMP card is present. Minicom connection to /dev/ttyS0 gives nice banner and control menu, but they prevent nut driver from working correctly (I guess). UPS should be switched into "Pass-Through" mode

Hello! It looks like bcmxcp driver doesn't fit my device: UPS Model ? ? ? ? ? ? ? ? ? ?PW9125 UPS Firmware Version ? ?FP: 1.10 INV: 1.10 VA Rating ? ? ? ? ? ? ? ? ? ? ?3000 VA Web/SNMP card is present. Minicom connection to /dev/ttyS0 gives nice banner and control menu, but they prevent nut driver from working correctly (I guess). UPS should be switched into "Pass-Through" mode

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

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

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

Hi all, I just acquired a new UPS and have been trying to get it to work with NUT. It's an Eaton/Powerware 9120 700i with both USB and RS-232 interfaces. I first tried the USB interface (using bcmxcp_usb) and found that the UPS worked fine for a few minutes but then NUT lost communication and didn't get it back. In addition the UPS itself seemed to lock up at one point such that the

Hi I have now done some work to clean up the bcmxcp driver somewhat, and then addede support for a number of more ups variables, so if you have hardware supporting it, you should get more output from "upsc" command, for example. I do not have hardware to test this, so I hope someone do have hardware and are willing to test. The changes should be ok, it is just add new mappings 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: