> > > root at artu:~# upsc Elit at artu > > Init SSL without certificate database > > battery.voltage: 13.90 > > battery.voltage.high: -1.08 > > battery.voltage.low: -0.87 > > device.type: ups > > driver.name: blazer_usb > > driver.parameter.pollinterval: 2 > > driver.parameter.port: auto > > driver.version: 2.7.2 > > driver.version.internal: 0.11 > > input.frequency: 50.0 > > input.voltage: 228.7 > > input.voltage.fault: 140.0 > > output.voltage: 226.5 > > ups.beeper.status: enabled > > ups.delay.shutdown: 30 > > ups.delay.start: 180 > > ups.load: 16 > > ups.productid: 0000 > > ups.status: OL > > ups.temperature: 30.0 > > ups.type: offline / line interactive > > ups.vendorid: ffff > > Glad it works. >?Yep! :)?> > > > 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? TY Andrea? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170612/592db249/attachment.html>
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/ <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/20170612/d8dda286/attachment.html>
Thanks a lot, I will do it and keep you informed. Best regards 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/20170612/a5e339dd/attachment.html>
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>