Displaying 7 results from an estimated 7 matches for "batt_volt_nom".
Did you mean:
batt_volt_low
2014 Aug 11
1
Cyberpower Value1200E might not need 0.667 battery scaling
...0601), NULL },
> @@ -59,12 +66,48 @@ static usb_device_id_t cps_usb_device_table[] = {
> { -1, -1, NULL }
> };
>
> +/*! Adjusts @a battery_scale if voltage is well above nominal.
> + */
> +static void cps_adjust_battery_scale(double batt_volt)
> +{
> + const char *batt_volt_nom_str;
> + double batt_volt_nom;
> +
> + if(battery_scale_checked) {
> + return;
> + }
> +
> + batt_volt_nom_str = dstate_getinfo("battery.voltage.nominal");
> + if(!batt_volt_nom_str) {
> + upsdebugx(2, "%s: 'battery.voltage.nominal' not available...
2014 Aug 09
0
Cyberpower Value1200E might not need 0.667 battery scaling
On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote:
> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote:
>
>> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote:
>>
>>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage
2014 Aug 08
2
Cyberpower Value1200E might not need 0.667 battery scaling
On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote:
> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote:
>
>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id:
2014 Nov 03
0
RFC: new variable battery.status (was: [PATCH] upscode2: Report ABM Status)
...ot;, NULL, NULL },
{ "test.failure.start", NULL, NULL },
{ "test.failure.stop", NULL, NULL },
{ "test.battery.start", "UPBT", "1" },
@@ -1363,6 +1363,7 @@
static float batt_charge_pct(void)
{
float chg=-1;
+ float batt_volt_rs = (batt_volt_nom * 26/24); /* ABM specs Vrs at 108.333 % Vnom */
/* This is only a rough estimate of charge status while charging.
* When on battery something like Peukert's equation should be used */
@@ -1389,9 +1390,10 @@
chg *= (100/maxcurr);
}
/* Old method, assumes battery high/low-volt...
2014 Feb 19
3
Logic problem in NUT with upscode2 driver
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
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 04
2
RFC: new variable battery.status
...gt; { "test.failure.start", NULL, NULL },
> { "test.failure.stop", NULL, NULL },
> { "test.battery.start", "UPBT", "1" },
> @@ -1363,6 +1363,7 @@
> static float batt_charge_pct(void)
> {
> float chg=-1;
> + float batt_volt_rs = (batt_volt_nom * 26/24); /* ABM specs Vrs at
> 108.333 % Vnom */
>
> /* This is only a rough estimate of charge status while charging.
> * When on battery something like Peukert's equation should be used */
> @@ -1389,9 +1390,10 @@
> chg *= (100/maxcurr);
> }
> /* Old method, assumes b...