search for: maxcurr

Displaying 3 results from an estimated 3 matches for "maxcurr".

Did you mean: maxcorr
2014 Nov 03
0
RFC: new variable battery.status (was: [PATCH] upscode2: Report ABM Status)
...id) { 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-voltages provided by UPS are - * applicable to battery charge, but they usually aren't */ + * applicable to battery charge, but they usually aren't, cause high is a UPS internal and/or battery + * ABSOLUTE MAXIMUM RATING, not reported as...
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
...-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-voltages provided by UPS are > - * applicable to battery charge, but they usually aren't */ > + * applicable to battery charge, but they usually aren't, cause high is > a UPS internal and/or battery > + * ABSOLUTE MAXIMUM RAT...