similar to: Powerware 9120 / bcmxcp losing communication

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

hello everyone, I've been testing the NUT solution as opposed to the undocumented LanSafe application to control my Eaton UPS. I am on a Slackware 13.37 system with a 2.6.37.6 kernel. NUT version is 2.4.3 . I installed the tarball by compiling it directly on my system (as a slackbuild package). The UPS is an Eaton Powerware 9155, but I don't know how to obtain the manufacturing date. The

Hello... I have a PowerWare 9120 attached via USB to my Debian system. My ups.conf looks like this: [ups1] driver = bcmxcp_usb port = auto desc = "PowerWare 9120" When testing the driver with "upsdrvctl -u root start" I get: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS

On 19/09/13 01:30, Kris Jordan wrote: > Luke-Jr wrote, On 9/18/2013 1:02 PM: >> I wanted to suggest some rating for functionality. I got the UPS >> available >> that seemed to have the best possible rating from NUT's list (Eaton >> Powerware >> UPS 1500), and found out it doesn't support telling me battery level or >> runtime! :/ > > I'm

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

Hi All, I'm a system administrator of a large data center, and I've recently replaced the machine that acted as the nut master for our cluster/cloud. The machine that was interfacing with our Powerware 9135 450KVA 3 phase UPS, not to confused with Eaton's Powerware 9135, and was a Fedora Core 4 box running nut version 2.0.3-4 connected by a serial cable. We are using these versions

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

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

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

I decided to try this to see if it worked better since Powerware decided to build in some oddball USB protocol instead of using a HID UPS profile, but it doesn't seem to work. The USB/serial dongle is recognized by Linux and added as /dev/ttyUSB0, owned by group "dialout", so I had to add the nut user to the dialout group. In the compatibility list, the proper driver for the

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, I've got a Powerware Prestige 9 1kVA UPS that seems to not be working with nut. It's not in the current "supported hardware" list, but the old bcmxcp page lists it as being a UPS that speaks that protocol. I have the following in my ups.conf [powerware] driver = bcmxcp port = /dev/ttyS0 desc = "Powerware Prestige 9 EXT" baud_rate = 2400 And when I start the

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

Luke-Jr wrote, On 9/18/2013 1:02 PM: > I wanted to suggest some rating for functionality. I got the UPS available > that seemed to have the best possible rating from NUT's list (Eaton Powerware > UPS 1500), and found out it doesn't support telling me battery level or > runtime! :/ I'm avoiding Eaton/Powerware because the lack of usbhid support, the bcmxcp driver

I wanted to suggest some rating for functionality. I got the UPS available that seemed to have the best possible rating from NUT's list (Eaton Powerware UPS 1500), and found out it doesn't support telling me battery level or runtime! :/ Luke

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

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