Hi, it's me again. I haven't yet tested my UPS with full load, but I have tried to insert some values in ups.conf, I have kept the example on the blazer_usb driver help page: runtimecal = 240,100,720,50 When I try to start the driver, I receive root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Supported UPS detected with megatec protocol Rating information unavailable Vendor information unavailable No values provided for battery high/low voltages in ups.conf Using 'guestimation' (low: -0.866667, high: -1.083333)! Initial battery charge undetermined Driver failed to start (exit status=1) What should I do? Thanks again, Andrea 2017-06-12 12:34 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>:> On 06/12/2017 12:56 PM, Andrea de Lutti wrote: > > > >> > I have also successfully tested the battery... >> > >> > upscmd -uadmin -pups Elit at artu test.battery.start.quick >> >> I would also recommend testing the shutdown procedure and making sure >> that everything works as expected on power failures. >> Please, let us know the results of these tests, so that we can add a >> more informed report about your device to our library >> (http://networkupstools.org/ddl/). >> > > ?Nice, I would like to test it, but if I don't have battery runtime value > and / or battery charge, how may I test it correctly? > I have seen also some strange values for battery.voltage.high and > battery.voltage.low....are they correct? > > run with a test load ( at least twice, for 50% and 100% load for > instance ) and write down the periods between full charge and shutdown. > Then you can use runtimecal in ups.conf to obtain guestimations during > normal usage >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170616/de0aa8a6/attachment.html>
On Jun 16, 2017, at 2:20 AM, Andrea de Lutti <adelutti at gmail.com> wrote:> Using 'guestimation' (low: -0.866667, high: -1.083333)! > Initial battery charge undetermined > Driver failed to start (exit status=1)The "low" and "high" voltages should correspond to the battery voltage when it is discharged (LB) and charged, respectively. For a 12V (nominal) battery, they should not be less than zero :-) There is a check for whether the nominal battery voltage is 1, but it should be looking for -1. (This has been fixed in nutdrv_qx, but was not backported to blazer*) As Manuel suggested, you can use the "defaults.battery.voltage.low" and "defaults.battery.voltage.high" options in ups.conf - there is a bit of a chicken-and-egg problem here, but you can still put in approximate values (say, 10.4 and 13.0) in order to run the calibration, and then adjust them to the actual reported values.
Thanks mates,
as suggested I have added
runtimecal = 240,100,720,50
default.battery.voltage.low = 10.4
default.battery.voltage.high = 13.8 (the actual charging voltage)
In ups.conf
I have also added the startup procedure in rc.local file, everything is
fine...
I have only to make a deep test.
Is there a way to add a NOTIFYMSG value for the battery test?
Thank you lots
Andrea
2017-06-16 14:50 GMT+02:00 Charles Lepple <clepple at gmail.com>:
> On Jun 16, 2017, at 2:20 AM, Andrea de Lutti <adelutti at gmail.com>
wrote:
> > Using 'guestimation' (low: -0.866667, high: -1.083333)!
> > Initial battery charge undetermined
> > Driver failed to start (exit status=1)
>
> The "low" and "high" voltages should correspond to the
battery voltage
> when it is discharged (LB) and charged, respectively. For a 12V (nominal)
> battery, they should not be less than zero :-)
>
> There is a check for whether the nominal battery voltage is 1, but it
> should be looking for -1. (This has been fixed in nutdrv_qx, but was not
> backported to blazer*)
>
> As Manuel suggested, you can use the
"defaults.battery.voltage.low" and
> "defaults.battery.voltage.high" options in ups.conf - there is a
bit of a
> chicken-and-egg problem here, but you can still put in approximate values
> (say, 10.4 and 13.0) in order to run the calibration, and then adjust them
> to the actual reported values.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170616/54d32e75/attachment.html>