similar to: Deltec PRA1500 UPS and FC4

I have a Raspberry PI that I have connected to a Deltec UPS via serial (upscode2 driver). I had an older version of Rasbian running. The nut configuration worked fine but I had mail issues I couldn't resolve when gmail changed how it handled MTAs. Plus it was running an old version of Deb that is no longer supported. It was broken enough I could not upgrade to a never version so I started from

Here is the output root at nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]' 4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? 00:00:31 avahi-daemon: running [nutpi.local] 1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? 00:03:41 /lib/nut/upscode2 -a deltec-PRA1500 1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? 00:00:28 /lib/nut/upsd 1

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

Someone might want to add this to the docs - cable list and compatibility list - took me way to long to find. I was trying to find information on my UPS and came up with the following names for the same UPS series. Powerware 5119 Exide name was NetUPS SE Deltec name was PowerRite Pro II (1000VA-3000VA) What I have: The Exide NETUPS SE model PRC2400a p/n 05144038-3904 OUTPUT 2400VA 1600 WATTS

Here are my permissions and user info. Let me know if there is anything else I should check pi at nutpi:~ $ ls -alt /etc/nut total 56 drwxr-xr-x 87 root root 4096 Jan 26 15:22 .. drwxr-xr-x 2 root nut 4096 Jan 26 13:53 . -rw-r----- 1 root nut 4719 Jan 26 13:15 upssched.conf -rw-r----- 1 root nut 15347 Jan 26 11:25 upsmon.conf -rw-r----- 1 root nut 1543 Jan 26 10:02 nut.conf -rw-r-----

One last update. I needed to log out and in to get the group add of my user nutmon to be recognized. My permissions are now root:nut on upssched.conf and it works. On Tue, Jan 28, 2020 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or unsubscribe

The time and upssched-cmd are now working. Here are the issues I had: 1) Did not define NOTIFYCMD in upsmon.conf Added NOTIFYCMD /sbin/upssched 2) Added +EXEC to NOTIFYMSG rules I am using 3) Change ownership of upssched.conf to my nut user nutmom. I had added nutmon to the group nut but it didn't work. Thanks again for all your guidance On Tue, Jan 28, 2020 at 7:00 AM

If you look closer at: > pi at nutpi:~ $ sudo ls -alt /home/nutmon > total 32 > -rw------- 1 nutmon nutmon 172 Jan 26 12:32 .bash_history > drwxrwx--- 2 nutmon nutmon 4096 Jan 26 12:32 upssched there is a d in the first position of the upssched permissions showing this is a directory. This is the directory location for PIPEFN and LOCKFN as defined in

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

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

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

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

Roger, here is my output of ps -elf |grep upssched root at nutpi:~# ps -elf |grep upssched 0 S root 1242 1191 0 80 0 - 1834 pipe_w 05:23 pts/0 00:00:00 grep upssched No timer, just the grep of upssched.. On Mon, Jan 27, 2020 at 4:27 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to >

I only pasted a subset of my upsmon.conf. NOTIFYCMD is in my upsmon.conf AFA nutmon user. I was trying different things I had the directory as nutmon nut but changed it to nutmon nutmon to see if that worked. It didn't make a difference. Sorry about the digest this. I needed to hit a line in gmail web client to see the subject line. Know I know. Thanks for the heads up.. [root at donner

I tried to find a search button for the mailing list but could not. So rtfm me with the link please. If not.. I have an old Deltec PowerRite Pro 2 UPS which has a 9 pin serial cable. By trial and error Im pretty sure I found LB = DCD, but can not get the combination for OB / OL. No matter what I do I get the results below. driver.name: genericups driver.parameter.CP: CTS driver.parameter.LB:

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

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

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

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