similar to: Long shutdown time - customise runtime for bcmxcp

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

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

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

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)

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

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

Hello All, Sorry for the long post, I'm just trying to give as much info as I have about the problem(s) ... Recently I've tried to port NUT to the hardware router Asus WL-500g Deluxe (http://wiki.openwrt.org/OpenWrtDocs/Hardware/Asus/WL500GD), that runs OpenWRT Linux distribution (http://www.openwrt.org) based on Linux 2.4.30 kernel, in order to support my Powerware 5110 UPS (through USB

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

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 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 I try since a week to run my MGE Protection Center under Suse Linux 9.3. At the MGE site i found an HowTo. I have installed NUT an create the=20 configs but at boot the newhidups driver say=B4s "no USB/HID UPS found".=20= Anyone an Idea? Johannes Schatz=

Hi. FYI. Have tested the bcmxcp driver from cvs development tag. And it work as expected on the 5115 with the serial interface. So to Wolfgang, no bug introduced in the serial module when you split'ed the driver. If i get some time to spare, i have a look on the serial module to make it wake up the ups. The 9125 is type pnp so it need to be waken up. Then there are some cleanup to be done

Hi everyone, First of all a big thank you for the NUT package, I've been using it for years and couldn't get by without it! I have two Powerware UPS's here, a 9120/1500va and a 5110/700va. The 9120 has used a hacked bcmxcp driver (serial) from the 2.0.2 nut version for about a year now (which I'll explain more about in a seperate email to the dev list), and the 5110 which I just

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 List, My FC2 Wine installation crashes (without any message displayed) on every application which shows the std. file selection dialog (eg File - Open) as soon as I change the directory in the dialog or click "OK" or "Cancel". This even happens with the stock "notepad" that comes with Wine. "Winefile" however can browse the file systems correctly,

THE GOOD: NUT is able to communicate with my Powerware 5115A over USB using the bcmxcp_usb driver: ambient.temperature: 38 battery.charge: 99 battery.runtime: 9000 battery.voltage: 27.07 driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.2.1 driver.version.internal: 0.13 input.frequency: 50.34 input.voltage: 235 output.current: 0.0

A question about the tc binary and diff file that are included in htb3.6-020525.tgz. I can''t seem to patch tc in the source tree, and that has made me hesitate to alternatively substitute the native /usr/sbin/tc for the binary supplied with the patch materials. I''m running kernel 2.4.19-r9, and when I run xingu:/usr/src/linux #patch -p1 --dry-run < ../htb3.6.tc.diff the

Hi I'm hoping someone can help. I'm running fc5 with nut 2.0.3. I just recently acquired 2 Gamatronic SmartCompact ups for my Linux boxes. As you can see from the info below, everything looks ok. When I unplug the ups from the wall, after a while, the computer shutdowns very rudely. That it is just turns off. No scrolling down of processes shutting down It does not seem shutdown

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]