Displaying 8 results from an estimated 8 matches for "schorpp".
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 usefu...
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:
> https://alioth.debian.org/tracker/index.php?func...
2014 Nov 04
2
RFC: new variable battery.status
...%VAR battery.charge% " \
+ "%VAR battery.voltage% %VAR output.current% " \
"%VAR input.voltage% %VAR ups.load% [%VAR ups.status%] " \
"%VAR ups.temperature% %VAR input.frequency%"
Ted
On 11/3/2014 3:25 PM, thomas schorpp wrote:
> 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
>>> controlle...
2014 Nov 04
0
RFC: new variable battery.status
...logger using the upsclient(3) library.
30s are far to long to catch short but maybe damaging line power incidents, so I would second that.
3. Maybe You shouldn't top post nor (re)word wrap mails to devlists, thank You.
PL ?
>
> Ted
y
tom
>
>
> On 11/3/2014 3:25 PM, thomas schorpp wrote:
>> 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...
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:
>&g...
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
>>> vol...
2014 Nov 08
1
RFC: new variable battery.status
On 11/8/2014 6:54 AM, thomas schorpp wrote:
> 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 UP...
2011 Sep 28
0
[BUG] nut 2.4.3+: UPS EP-1K: Firmware fault: USB-Interface crashes with nut.org monitoring if driver polling time <15 sec
@fsp
Please forward to development, manufacturing and quality management department:
Model EP1000(PPF6000/100), 431107300095, 4711140480534, Art-Nr. 8296861, 70539, 14Z00000, 35-0200116-01G
@nut-users
http://www.networkupstools.org/ 2.4.3 debian stable, 2.6.2 upstream, linux 2.6.38-debian-bpo
# /usr/local/src/nut-2.6.2/drivers/blazer_usb -u root -DDDDD -a ups
Network UPS Tools - Megatec/Q1