similar to: Data string for 2 instant commands to Powerware 9110

My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as Powerware 5119, according to Karl Schmidt (http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html) also Deltec PowerRite Pro II, and according to http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was

My UPS is an Exide NetUPS SE PRC1500i (1500 VA), also known as Powerware 5119, according to Karl Schmidt (http://lists.alioth.debian.org/pipermail/nut-upsuser/2005-July/000026.html) also Deltec PowerRite Pro II, and according to http://www.usedups.de/compaq_ups.html also Compaq R3000h. I am not sure if the information in http://www.bps.hu/powerware/model_en.html is to be interpreted as that it was

I've got a Powerware 5119 RM UPS. driver.list says to use "genericups upstype=20", however I know this UPS supports the UPS Code II protocol, so I wanted to use the upscode2 driver. It took some hacking but finally it works. I'm using NUT 2.4.1 and upscode2 driver version 0.87 (however the latest r2350 version of upscode2.c isn't significantly different, so I think all

Hi, just wanted to confirm that Fiskars UPS 9000 series (aka Powerware Plus 500 series) with optional UPS Information Unit works fine with upscode2 driver. Tested on Fiskars 9200 (20kVA/400V/3ph). Regards, -- Sebastian Zagrodzki Dzia? Sieciowy ICM, Uniwersytet Warszawski s.zagrodzki at net.icm.edu.pl (+48-22) 5520527, 8268009, fax. 8284195 http://www.net.icm.edu.pl/

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

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

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, Am 13.02.2012 um 18:58 schrieb Arnaud Quette: > 2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: >> Hi, > > Hi Thomas, > >> I want the driver report the battery status from ABM charging controllers >> -patch attached- : > > For now, I've tracked your patch here: >

I am using the upscode2 driver with an old powerware ups. The driver seems slow to start and to spite the message of giving up it does work. Any thoughts on why it is having trouble synchronizing? ---------8<--------- Starting upscode2: Network UPS Tools - UPScode II UPS driver 0.84 (2.0.3) Copyright (C) 2001-2002 H&#9618;vard Lygre, Copyright (C) 2004 Niels Baggesen Warning: This is

THANKYOUTHANKYOUTHANKYOUTHANKYOU!!!!!! There was a smaller patch posted to the list for lines -1389,9 +1390,10 a couple years ago, it helped some - BUT - it was still buggy. I have a Compaq R3000, I will get this patch integrated pronto and test Note that since the UPS relies on the voltage from the battery pack to determine state of charge, it is quite useful to add in the battery pack

Hi All, I put my Compaq R3000 UPS on NUT. Every once in a while the battery alarm light turns on, on the front of the UPS. Maybe once every couple of days or so. When that happens I get the following output in /var/log/messages: Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: .20 MOUL1 Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: 0119.20 MOIL1 Sep 22

On 11/8/2014 6:54 AM, thomas schorpp wrote: > Dear Ted, > > Am 07.11.2014 um 17:47 schrieb Ted Mittelstaedt: >> On 11/3/2014 9:25 PM, thomas schorpp wrote: >>> Hi Ted, >>> >>> Am 04.11.2014 um 04:12 schrieb Ted Mittelstaedt: >>>> >>> >>>> Note that since the UPS relies on the voltage from the battery pack to

Hi All, I have what is probably a 12 year old (or older) Compaq R3000 UPS plugged into a FreeBSD 8 system running NUT version 2.6.5 This UPS contains a total of 16 batteries in 2 banks of 8, each battery is 6 volts and the bank produces 50 volts. The UPS monitors battery voltage and the battery charger in the UPS works like this. For about 2 days it will apply a charge/float/topping

Hallo, I own a NETUPS 450 (Model on the sticker: PRM 450i; upsstats reports "UPS 450 VA FW -0024") which perfectly works with the upscode2 driver. Maybe you want to add it to your list, even if the model is >10 years old. I suppose this is true for the whole series. According manual the come in the 450VA, 700VA, 1000VA and 1500VA strengths. They have been sold under different

Hi I have PW 5115 500 UPS which has both RS232 and USB connectors. bcmxcp driver works fine with serial connection but bcmxcp_usb does not with USB one. After some USB sniffing on windows box I've found that PW5115 communicates in other way than supposed in driver. Applying attached patch makes driver to work properly. System: FreeBSD 6.2 but ugen driver needs patching in order to respect

2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>: > Hi, Hi Thomas, > I want the driver report the battery status from ABM charging controllers > -patch attached- : thanks for your patch. since it introduces a new variable (battery.status.abm), I prefer to step back and think to something useful more widely. thus, I'm thinking about a generic

----- Doorgestuurd bericht van dkbrig at gmail.com ----- Datum: Thu, 29 Jan 2009 11:16:06 -0600 Van: Danny <dkbrig at gmail.com> Onderwerp: upscode2.c Aan: adkorte-guest at alioth.debian.org Hi, I apologize if you are not the correct person, but I was wanting to submit a bug report for the upscode2.c driver but could not find a way to do that from the NUT website.

Here are some Powerware compatibility info I got by a colleague, and authorized to publish. @Kjell: can you take over checking our driver.list and other info source to see if there's a gap? thanks, Arnaud ________________________________________________________________________ Old info from ca. 2002, but still mostly valid except that some 5125s got a

On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > Worse, however, is if there's a power failure right near the end > of the 2-days-off cycle. That happened to me last week - it was a > short duration 15 second loss - and the upscode2 driver decided it needed to issue a forced shutdown. > > Very likely this was because upscode2 had decided the batteries > were

On 2/20/2014 6:55 AM, Charles Lepple wrote: > On Feb 19, 2014, at 12:50 PM, Ted Mittelstaedt wrote: > >> Worse, however, is if there's a power failure right near the end of >> the 2-days-off cycle. That happened to me last week - it was a >> short duration 15 second loss - and the upscode2 driver decided it >> needed to issue a forced shutdown. >> >>