similar to: HCL HP R5000 supported by bcmxcp

On 2/21/2017 8:34 AM, Charles Lepple wrote: > On Feb 20, 2017, at 11:19 AM, Mike <the.lists at mgm51.com> wrote: >> >> This UPS is already listed in the compatibility list. But I wanted to >> add the instant commands supported by upscmd: >> > ... >> and note that a delayed shutoff command is not available. >> >> (NUT 2.7.4 on OpenBSD 6.0)

This UPS is already listed in the compatibility list. But I wanted to add the instant commands supported by upscmd: ============================ Instant commands supported on UPS [PW5125]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper load.on - Turn on the load immediately outlet.1.load.off - Turn off the load on

On Feb 20, 2017, at 11:19 AM, Mike <the.lists at mgm51.com> wrote: > > This UPS is already listed in the compatibility list. But I wanted to > add the instant commands supported by upscmd: > ... > and note that a delayed shutoff command is not available. > > (NUT 2.7.4 on OpenBSD 6.0) > > imo, it would be useful if this info were submitted along with the

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

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:

Greetings, I have been using the bcmxcp_usb driver heavily over the last two years as part of a very successful product, first from NUT 2.4.1 and now from NUT 2.6.0. Now I have a need to do setvar of the outlet.n.delay.start variables, so recently I modified bcmxcp.c to do that. I've tested it and it works well for my purposes. My plans are to begin shipping that modified driver as part

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

List: I have an Eaton (Powerware) Model 5115 and am using the bcmxcp_usb driver on a OpenBSD 4.9 system. The upsdrvctl start appears to work and I get a message in my daemon log stating that it successfully started. I can successfully start the upsd daemon. I get a successful start messaage from the upsmon program, but it soon complains of 'stale' data. It looks like the driver

On 01/27/2016 03:26 AM, Maciej W. Rozycki wrote: > On Fri, 15 Jan 2016, Leonid Yegoshin wrote: > >>> So you need to build a different kernel for some types of MIPS systems? >>> Or do you do boot-time rewriting, like a number of other arches do? >> I don't know. I would like to have responses. Ralf asked Maciej about old >> systems and that came nowhere. Even

On 01/27/2016 03:26 AM, Maciej W. Rozycki wrote: > On Fri, 15 Jan 2016, Leonid Yegoshin wrote: > >>> So you need to build a different kernel for some types of MIPS systems? >>> Or do you do boot-time rewriting, like a number of other arches do? >> I don't know. I would like to have responses. Ralf asked Maciej about old >> systems and that came nowhere. Even

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

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

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, 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 Just to let you know that I have updated the pull request 33, adding these as well : bcmxcp: Add mapping for input.quality to meters bcmxcp: Output more info hardware capabilities in debug mode bcmxcp: Add support for reading topology map and setting ups.description Alf