Displaying 20 results from an estimated 1000 matches similar to: "Logic problem in NUT with upscode2 driver"
2012 Feb 13
3
RFC: new variable battery.status (was: [PATCH] upscode2: Report ABM Status)
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
2014 Nov 03
0
RFC: new variable battery.status (was: [PATCH] upscode2: Report ABM Status)
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:
>
2014 Nov 04
2
RFC: new variable battery.status
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
2014 Feb 20
1
Logic problem in NUT with upscode2 driver
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.
>>
>>
2014 Feb 20
0
Logic problem in NUT with upscode2 driver
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
2009 Jan 29
1
Fwd: upscode2.c
----- 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.
2010 Mar 03
1
using upscode2 driver with Powerware 5119 RM
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
2014 Nov 07
5
RFC: new variable battery.status
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
>> determine state of charge, it is quite useful to add in the battery pack
>> voltage to the logs as such:
>>
>> --- upslog.c.orig 2012-07-31 10:38:58.000000000
2023 Jul 05
1
failed after upgrade - upscode2: Missing UPCL after UPCL
On 7/5/23 03:17AM, Jim Klimov wrote:
> Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since),
> did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build
> your own in one of many ways possible :\
I think I'm not following you - with debug 3 -->> it
2013 Sep 22
1
Question on weird output from a Compaq R3000
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
2023 Jul 05
1
failed after upgrade - upscode2: Missing UPCL after UPCL
Ah, I thought you missed in my earlier reply the part about a bug with
debug printouts in 2.8.0 (fixed on master since), did not comment on that
when you replied with quoting... So, for now options are to bump debugging
to 3+ or to build your own in one of many ways possible :\
On Wed, Jul 5, 2023, 06:23 Karl Schmidt <karl at lrak.net> wrote:
> On 7/4/23 10:01PM, Jim Klimov wrote:
>
2023 Jul 05
1
failed after upgrade - upscode2: Missing UPCL after UPCL
Normally yes - enable and start the target and the particular services
relevant to your setup.
For the binary you have from packaging (if not rebuilt as suggested
earlier), set debug_min=3 in ups.conf section for upscode2, to currently
trade driver viability for some storage traffic with more logs :\
Sorry about that,
Jim
On Wed, Jul 5, 2023, 02:29 Karl Schmidt <karl at lrak.net> wrote:
2017 Mar 01
2
error en el cambio de formato desde factor a numerico USANDO LAPPLY
?Hola,
Es más fácil que todo eso...
Es que en tu fichero de entrada, la segunda fila son las unidades de las
variables que tienes en la primera fila, pero "R" al leerlas las considera
como un string que altera la clase de toda la columna cuando ésta es
numérica.
Simplemente eliminando esa segunda fila, las columnas acaban teniendo la
clase que deben..
2023 Jul 05
1
failed after upgrade - upscode2: Missing UPCL after UPCL
On 7/4/23 10:01PM, Jim Klimov wrote:
> Normally yes - enable and start the target and the particular services relevant to your setup.
>
> For the binary you have from packaging (if not rebuilt as suggested earlier), set debug_min=3 in ups.conf section for
> upscode2, to currently trade driver viability for some storage traffic with more logs :\
>
> Sorry about?that,
> Jim
2010 Mar 02
3
Back to apcupsd
Ok, so another apc UPS 3000 complained about bad batteries, and I changed
them out from the same order that I'd gotten in a couple of months ago.
The APC SmartUPS 3000 started connecting and disconnecting the USB
connection. I brought down and up the service, no joy.
Finally, after googling, I found a *completely* undocumented way to start
apcupsd, that a few years ago someone was told to
2020 Nov 01
1
ups.test.result meaning
>
>
> > battery.voltage: 16.0
> At that voltage, 5 of the 12 cells are shorted
> > output.voltage: 138.0
> too high by about 15 volts
>
> Wow! That battery is beyond toasted, shoulda been replaced months ago.
> And the output voltage is a bit much if its truthfull.
>
Thanks for the response Gene!
I've ordered a replacement unit.
I'm not sure about the
2014 Nov 04
0
RFC: new variable battery.status
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
> determine state of charge, it is quite useful to add in the battery pack
> voltage to the logs as such:
>
> --- upslog.c.orig 2012-07-31 10:38:58.000000000 -0700
> +++ upslog.c 2014-02-20 09:23:14.000000000 -0800
> @@ -50,6 +50,7
2014 Nov 08
0
RFC: new variable battery.status
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
>>> determine state of charge, it is quite useful to add in the battery pack
>>>
2008 Dec 23
2
Exide NetUPS SE (aka Powerware 5119 etc)
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
2008 Dec 23
2
Exide NetUPS SE (aka Powerware 5119 etc)
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