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@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 <wo...@nobugconsulting.ro>: > On 06/12/2017 12:56 PM, Andrea de Lutti wrote: > > > >> > I have also successfully tested the battery... >> > >> > upscmd -uadmin -pups Elit@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 >
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
