similar to: bcmxcp: Now supports more ups variables, help needed on testing on hardware

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

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 I had to close pull request 33, due to misspelling of commit messages. Charles helped me to fix it, and I have made a new pull request. The new pull request is : https://github.com/networkupstools/nut/pull/35 Regards Alf

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

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

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

On 08/07/2013 02:02 PM, Bendtsen, Jon wrote: > On 07/08/2013, at 13.40, Jan Phillip Greimann <jg at softjury.de> wrote: > >> Hi there, >> >> OS: (L)ubuntu 12.04 precise LTS >> Nut: 2.6.3-1ubuntu1.1 >> Installation Method: Package (apt-get install nut) >> Hardware: HP R1500 G3 INT > > FYI: > I have a different UPS, a HP R3000 XR and I monitor

=?ISO-8859-1?Q?Alf_H=F8gemark?= <alf at i100.no> writes: > I am working on improving the bcmxcp driver, to add more data reported > from the driver, and also add support for sending more commands to the ups. > The code changes are currently not part of any release, but they are in > github, and some more are on the way. > Would you be able to do some testing on your HP R3000

On 08/08/2013, at 18.58, Alf H?gemark <alf at i100.no> wrote: > On 08/07/2013 02:02 PM, Bendtsen, Jon wrote: >> On 07/08/2013, at 13.40, Jan Phillip Greimann <jg at softjury.de> wrote: >> >>> Hi there, >>> >>> OS: (L)ubuntu 12.04 precise LTS >>> Nut: 2.6.3-1ubuntu1.1 >>> Installation Method: Package (apt-get install nut)

I noted some correspondence from several years back about supporting this device with bcmxcp, and the problems therein. Since I have one of these UPS units, still going strong, and the Eaton LanSafe stuff has finally caused me enough grief to abandon it, I figured I'd take a look at this. The issue is not that bad - the bcmxcp driver query of the topology block (2 bytes!) is returning

2013/11/18 Vladimir Nesterenko <nesterenko.vy at gmail.com> > > > ---------- Forwarded message ---------- > From: Vladimir Nesterenko <nesterenko.vy at gmail.com> > Date: 2013/11/13 > Subject: Request for advice about NUTdrivers/bcmxcp > To: Arnaud Quette <ArnaudQuette at eaton.com> > > > Hello. > I am using this driver on openSUSE 12.3 with

Hi I am considering adding support in the bcmxcp driver for the following commands available in bcmxcp specification : #define PW_UPS_ON .. /* UPS on command. length 1-2 */ #define PW_UPS_ON_TIME .. /* Scheduled UPS on in n minutes. length 3-4 */ #define PW_UPS_ON_AT_TIME .. /* Schedule UPS on at specified date and time. length 7-8 */ #define

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

On Sep 19, 2013, at 12:11 PM, Paul O'Rorke wrote: > So where does this leave things regards Eaton and shut down? Has anyone managed graceful shut down from an Eaton unit with either of the ushhid or bcmxcp drivers? Generally speaking, the UPS will signal when it reaches a low battery state, regardless of whether the UPS publishes runtime statistics, battery percentages, or any other

The driver will poll the UPS for what variables it supports when it starts, and then go into a polling loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. You can get the comm spec for XCP from the nut site if you want to delve deeper. I'd give more specifics, but am out of town and only working from memory at the moment . . . - Tim On

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

2014-02-16 8:31 GMT+01:00 <alf at i100.no>: > Hi > Hi Alf, > One idea I've had for some time, but unfortunately not had time to > implement, is to add a general SNMP agent, which will work with all UPSes > supported by nut. > The idea is to have the SNMP agent use the "nut API" to fetch values from > the UPS. > So the SNMP agent will be similar to

The model should also work with the bcmxcp driver, but maybe that only works with serial, not usb. http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_9130 Alf Sent from my Cat? phone. Valeri Linchevski <lincher at ya.ru>:

The meter map is basically a bitmap that indicates what variables are output (and in what format) by the UPS. You will likely see a variable, 'not mapped' or nothing. The variables and 'not mapped' items are output by the UPS in the measurement block, and the map tells nut how to read it. 'Unmapped' means that there is a variable there that nut is ignoring, and the xcp