Displaying 5 results from an estimated 5 matches for "pssclabs".
Did you mean:
psclass
2016 May 16
1
Low Battery event not occurring
...#39;m attaching a tar.gz of my ups directory. Can you take a glance and see if I have something misconfigured perhaps?
Please let me know.
Thanks.
--
Kamran Khan
PSSC Labs
HPC Software / Technical Engineer
________________________________________
From: Nut-upsuser <nut-upsuser-bounces+kamran=pssclabs.com at lists.alioth.debian.org> on behalf of Kamran Khan <kamran at pssclabs.com>
Sent: Monday, May 16, 2016 9:58:44 AM
To: Charles Lepple
Cc: nut-upsuser at lists.alioth.debian.org
Subject: Re: [Nut-upsuser] Low Battery event not occurring
Hi Charles,
Thanks for the response!
I don'...
2016 May 13
0
Low Battery event not occurring
...tus
OL CHRG
====================================================================
It won't provide a "LB" status.
Thanks again for the help.
--
Kamran Khan
PSSC Labs
HPC Software / Technical Engineer
________________________________
From: Nut-upsuser <nut-upsuser-bounces+kamran=pssclabs.com at lists.alioth.debian.org> on behalf of Kamran Khan <kamran at pssclabs.com>
Sent: Friday, May 13, 2016 3:30:00 PM
To: nut-upsuser at lists.alioth.debian.org
Subject: [Nut-upsuser] Low Battery event not occurring
Hi Everyone,
New to the list. Thanks in advance for any assistance...
2016 May 13
3
Low Battery event not occurring
Hi Everyone,
New to the list. Thanks in advance for any assistance you are able to provide.
I have a TrippLite SMART2200RM2UN UPS. I have installed and configured NUT as instructed on the website, and am able to monitor the status of the UPS without much problem. The only problem I am seeing is that I cannot get the machine to actually send a Low Battery ( LB ) signal.
When I run
2016 May 14
2
Low Battery event not occurring
>
> battery.charge: 3
> battery.charge.low: 10
> battery.charge.warning: 30
> battery.runtime: 93
> battery.temperature: 32.9
> battery.type: PbAC
> battery.voltage: 46.4
> battery.voltage.nominal: 48.0
Is it possible that battery.charge is really 30% rather than 3%?
The 3016 protocol models have issues with scaling on some of the voltages and frequencies. You can see
2016 May 16
0
Low Battery event not occurring
Hi Charles,
Thanks for the response!
I don't believe the battery.charge is actually 30%. I watched the "battery.charge" go down from "100" to "3", so I can only assume this field to be "%". Here is what it currently looks like after charging over the weekend:
====================================================
[root at localhost ~]# upsc myups at