Nut upsdev - Jan 2016 - [HCL] NHS Laser Senoidal 5000VA supported by gamatronic

Below the answers:
> This is the same as https://github.com/networkupstools/nut/issues/254 ,
right?
Yes, this UPS is the same.
> Does battery.runtime only get updated when on battery power, or is this
with a different load?
> battery.runtime.low: 59940
> battery.temperature: 00
Yes, this time time is updated on battery power, This is a dynamic counter that
changes with a different load.
> Is this fixed at 0, or is there a temperature option?
In this case, this UPS doesn't have a temperature sensor, therefore this
value is equal zero.
> battery.voltage: 163.4
> device.mfr: NHS Sistemas de Energia
> device.model: Laser Senoidal 5000VA
> device.type: ups
> driver.name: gamatronic
> driver.parameter.pollinterval: 20
> driver.parameter.port: /dev/ttyACM2
> driver.version: 2.6.3
> driver.version.internal: 0.02
> input.frequency: 59.9
> input.transfer.high: 144
> input.transfer.low: 096
> input.voltage: 127.6
> input.voltage.nominal: 120
> output.current: 0.0
> output.frequency: 60.0
> output.voltage: 119.1
> ups.firmware: LSPWM(15).55
> ups.id: ny7bd8723tbecabc
> ups.load: 000
> ups.mfr: NHS Sistemas de Energia
> ups.model: Laser Senoidal 5000VA
> ups.power.nominal: 05000
> ups.status: OL
> 
> 
> 
> Below the "upsc" command when the UPS is on battery without input
(input bad):
> 
> 
> battery.charge: 100
> battery.current: 0.0
> battery.date: 12292015
> battery.runtime: 00076
> battery.runtime.low: 59940
> This seems rather high. This variable is supposed to represent the runtime
[in seconds] below which the UPS will signal "LB", but this capture
only shows "OB".
> battery.temperature: 00
> battery.voltage: 155.9
> device.mfr: NHS Sistemas de Energia
> device.model: Laser Senoidal 5000VA
> device.type: ups
> driver.name: gamatronic
> driver.parameter.pollinterval: 20
> driver.parameter.port: /dev/ttyACM2
> driver.version: 2.6.3
> driver.version.internal: 0.02
> input.frequency: 0.0
> input.transfer.high: 144
> input.transfer.low: 096
> input.voltage: 0.0
> input.voltage.nominal: 120
> output.current: 0.0
> output.frequency: 60.0
> output.voltage: 119.7
> ups.alarm: Input Bad 
> ups.firmware: LSPWM(15).55
> ups.id: ny7bd8723tbecabc
> ups.load: 000
> ups.mfr: NHS Sistemas de Energia
> ups.model: Laser Senoidal 5000VA
> ups.power.nominal: 05000
> ups.status: ALARM OB
This value is high because we don't have a load in the output of the UPS,
therefore, with this load the time until the UPS achieve the low battery status
is 59940 seconds.

Best Regards.
----------------------------------------------------------- 
Thiago Wiezbicki 
NHS Sistemas de Energia 
Av. Juscelino Kubitschek de Oliveira, 5270 
Cidade Industrial - Curitiba - PR 
Fone/Fax: +55 41 2141-9262 
http://www.nhs.com.br

On Jan 8, 2016, at 7:09 AM, Thiago Wiezbicki - NHS <thiago.wiezbicki at
nhs.com.br> wrote:
> 
>>> battery.runtime: 00076
>>> battery.runtime.low: 59940
>> 
>> This seems rather high. This variable is supposed to represent the
runtime [in seconds] below which the UPS will signal "LB", but this
capture only shows "OB".
> 
> This value is high because we don't have a load in the output of the
UPS, therefore, with this load the time until the UPS achieve the low battery
status is 59940 seconds.
I admit that the documentation is not clear that battery.runtime.low should be a
configuration value, rather than a counter.

However, I am still confused as to why the runtime.low number is larger than
runtime (which would be the time until the battery is completely empty, versus
just low).

Since this might be hard to work around with the current driver, we can put a
note in the DDL, but at this point I don't know what the note should say.

-- 
Charles Lepple
clepple at gmail

I wasn't clear. 

battery.runtime.low is not a counter, but a value estimated in seconds that is
decreasing conforming the battery is discharging. It's mean: How much time
(in seconds) will be necessary until the battery achieve the depleted status (
http://www.networkupstools.org/protocols/sec.html#Estimated_Minutes ) . If the
UPS don't have a load, this value will be higher than the value when the UPS
have 100% of load.

The battery.run.low is not related with battery.runtime this is important
explain. Battery.runtime will count in seconds
(http://www.networkupstools.org/protocols/sec.html#Seconds_on_Battery) how much
time the UPS is in the Battery status and doesn't depend of load or other
parameter as battery.run.low depends.

battery.run.low is a dynamic timer, initially without a load in UPS it will be a
high seconds estimator. It will change dynamically conforms I can increase the
UPS load or not. It's a value calculated from the UPS to notice the User how
much time he have until the UPs battery achieve the depleted status.

The battery.run.low can be higher than battery.runtime, do you agree?


----------------------------------------------------------- 
Thiago Wiezbicki 
NHS Sistemas de Energia 
Av. Juscelino Kubitschek de Oliveira, 5270 
Cidade Industrial - Curitiba - PR 
Fone/Fax: +55 41 2141-9262 
http://www.nhs.com.br

----- Mensagem original -----
De: "Charles Lepple" <clepple at gmail.com>
Para: "Thiago Wiezbicki - NHS" <thiago.wiezbicki at nhs.com.br>
Cc: "nut-upsdev" <nut-upsdev at lists.alioth.debian.org>
Enviadas: S?bado, 9 de janeiro de 2016 19:41:09
Assunto: Re: [Nut-upsdev] [HCL] NHS Laser Senoidal 5000VA supported by
gamatronic

On Jan 8, 2016, at 7:09 AM, Thiago Wiezbicki - NHS <thiago.wiezbicki at
nhs.com.br> wrote:
> 
>>> battery.runtime: 00076
>>> battery.runtime.low: 59940
>> 
>> This seems rather high. This variable is supposed to represent the
runtime [in seconds] below which the UPS will signal "LB", but this
capture only shows "OB".
> 
> This value is high because we don't have a load in the output of the
UPS, therefore, with this load the time until the UPS achieve the low battery
status is 59940 seconds.
I admit that the documentation is not clear that battery.runtime.low should be a
configuration value, rather than a counter.

However, I am still confused as to why the runtime.low number is larger than
runtime (which would be the time until the battery is completely empty, versus
just low).

Since this might be hard to work around with the current driver, we can put a
note in the DDL, but at this point I don't know what the note should say.

-- 
Charles Lepple
clepple at gmail