search for: _battery_charge

Changed the driver as you suggest ... # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) USB communication driver 0.32 Using protocol: Q1 0.02 Can't autodetect number of battery packs [-1/13.50] Battery runtime will not be calculated (runtimecal not set) ... looks like it's connected to something, although maybe

...w in ups.conf(5), but don?t enter runtimecal, it will guesstimate the state of charge by looking at the battery voltage alone. This is not reliable under load..." Does your UPS report load? If so, there is the "runtimecal" option. http://www.networkupstools.org/docs/man/blazer.html#_battery_charge -- Charles Lepple clepple at gmail

...always set their own values for 'battery.voltage.{high,low}' and fine-tune calculations. Plus, we can always add a note here or there and recommend using certain values to have a slightly less inaccurate estimate for a given device. See: - https://networkupstools.org/docs/man/nutdrv_qx.html#_battery_charge - the various 'default.battery.*' and 'override.battery.*' items, 'runtimecal', 'chargetime' and 'idleload', here: https://networkupstools.org/docs/man/nutdrv_qx.html#_extra_arguments If you still can't find acceptable values, and you have any idea on ho...

...d (runtimecal not set) > > ... looks like it's connected to something, although maybe the driver is not quite right? That looks reasonable. Not all UPSes provide enough information to calculate runtime, but you can improve it slightly: http://networkupstools.org/docs/man/nutdrv_qx.html#_battery_charge What does "upsc easton" say? (make sure that upsd is running)

...but don?t enter runtimecal, it will guesstimate the state of charge by looking at the battery voltage alone. This is not reliable under load..." > > Does your UPS report load? If so, there is the "runtimecal" option. > > http://www.networkupstools.org/docs/man/blazer.html#_battery_charge > Yes, and it is set-up correctly. The time displayed is not far away from reality -- tested during a thunderstorm :-) > We should probably look into ways to make it easier to build custom .deb files for Ubuntu. Making a .deb can be automated; adding a ppa is possible and easy (if one wo...

On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote: > > Hi, > > thanks for the reply. > > On 2014-05-29 05:21, Charles Lepple wrote: >>> Now my questions: >>> 1. should the blazer_ser's high voltage be the voltage during charging >>> or right after I've unplugged it from the mains? >> sounds like during charging (or more

Dear Daniele, i understand perfectly, i'd like to explain you why we choosed to clone the blazer_usb driver: some of our devices uses Voltronic Q1 protocol and we tried the Krauler Subdriver (it was the one with the right "commands", Q1, F, etc.), but the issues were 2: - first: the Krauler Subdriver expects a different number of bytes in answer because in debug i see "Short

Hi, thanks for the reply. On 2014-05-29 05:21, Charles Lepple wrote: >> Now my questions: >> 1. should the blazer_ser's high voltage be the voltage during charging >> or right after I've unplugged it from the mains? > sounds like during charging (or more accurately, during float charging at the end of the cycle): > >

...always set their own values for 'battery.voltage.{high,low}' and fine-tune calculations. Plus, we can always add a note here or there and recommend using certain values to have a slightly less inaccurate estimate for a given device. See: - https://networkupstools.org/docs/man/nutdrv_qx.html#_battery_charge - the various 'default.battery.*' and 'override.battery.*' items, 'runtimecal', 'chargetime' and 'idleload', here: https://networkupstools.org/docs/man/nutdrv_qx.html#_extra_arguments If you still can't find acceptable values, and you have any idea on ho...