search for: runtimecal

...onsulting.ro> wrote: > > On 5/15/20 12:13 PM, Yogesh Bhanu wrote: > > [...] > > # Is it possible to calculate /estimate how much time is left when on > > battery ? > > > When the UPS does not report that, you can ask nut to provide an > estimate by using the runtimecal directive. For instance I have in > ups.conf on a system where I use an Inform low-end UPS: > > runtimecal = 120,100,480,50 > default.battery.voltage.low = 21.2 > default.battery.voltage.high = 27.7 > > > > ______________________________________...

...ll calibration. > > My answer was based on the documentation, but you could make a case for the on-battery voltage. A little more explanation under the "Battery Charge" heading: "If you specify both battery.voltage.high and battery.voltage.low 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...

...ectly? > 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>

...when disconnecting the battery), but the charging voltage, which has nothing to do with the actual charge. > A little more explanation under the "Battery Charge" heading: > > "If you specify both battery.voltage.high and battery.voltage.low 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 > Yes,...

Hi Mauel, No dice. The config does not show up config: --8<-- [tripp] driver = usbhid-ups port = auto vendorid = 09ae productid = 2009 bus = 001 desc = "Tripp Lite SMX1000LCD" runtimecal = 660,100,180,50 -->8-- output: --8<-- upsc tripp Init SSL without certificate database battery.charge: 100 battery.runtime: 736 battery.type: PbAc battery.voltage: 13.5 battery.voltage.nominal: 12.0 device.mfr: Tripp Lite device.model: TRIPP LITE UPS device.serial: FW-2473 A device.type: u...

Hi, This is a newbie post so please bear with me. After loosing my router to a random Subminute outage. I looked around for a fanless UPS and bought Tripp Lite SMX1000LCD The above constellation works. But I have some questions about outputs. Please see attache nut report for the config. upsc output: --8<-- fourpi01:~# upsc tripp Init SSL without certificate database battery.charge: 100

> > > 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 > >

...r 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 the driver is not quite right? On 2016-10-20 18:39, Charles Lepple wrote: >> but no /dev/ttyUSB0 >> >> How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 > > They are created aut...

Hi everyone, I installed latest version of Nut on Debian Wheezy 64bit. This is a virtual server hosted by VMware ESXi. It's a Nagios monitoring server. I configured one Sweex UPS in ups.conf and everything is working. ups.conf: [sweex1] driver = blazer_usb port = auto runtimecal = 1100,100,2200,50 Now I want to connect two more identical UPSes to the same server, total of 3 UPSes. I see from nut documentation that for driver blazer_usb I can specify a Bus parameter. root at nagios:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 00...

> On Oct 31, 2016, at 10:15 PM, Michael Evans <mjevans1983 at gmail.com> wrote: > > Are there any other tests I can perform or ways that I can help gather data to get the longer tests supported? > The "test.battery.start" command takes a parameter in seconds (defaults to 600): https://github.com/networkupstools/nut/blob/v2.7.4/drivers/nutdrv_qx_blazer-common.c#L286

...ol 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)! Battery runtime will not be calculated (runtimecal not set) Thank you lots, Andrea -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170607/334afbbd/attachment-0001.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 informatio...

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 t...

...ol 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)! Battery runtime will not be calculated (runtimecal not set) but root at artu:~# upsc Elit at artu Error: Connection failure: Connection refused Starting the driver with debug level 5 seems happier, but continue to cycle root at artu:~# /lib/nut/blazer_usb -a Elit -u nut -DDDDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) 0...

...etwork UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)Supported UPS detected with megatec protocolVendor information unavailableNo values provided for battery high/low voltages in ups.conf Using 'guestimation' (low: 10.400000, high: 13.000000)!Battery runtime will not be calculated (runtimecal not set)[CODE] I recall, from past experience with this UPS, that the nominal voltage is around 13.1 . ?I have?no idea what the low voltage should be, but 10.4 is probably okay. So, would I add the following?in the ups.conf? [CODE]default.battery.voltage.high = 13.5default.battery.voltage.low = 10....

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 hel 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 informatio...

On 5/15/20 12:13 PM, Yogesh Bhanu wrote: > [...] > # Is it possible to calculate /estimate how much time is left when on > battery ? When the UPS does not report that, you can ask nut to provide an estimate by using the runtimecal directive. For instance I have in ups.conf on a system where I use an Inform low-end UPS:         runtimecal = 120,100,480,50         default.battery.voltage.low = 21.2         default.battery.voltage.high = 27.7

...; wrote: >> On 5/15/20 12:13 PM, Yogesh Bhanu wrote: >>> [...] >>> # Is it possible to calculate /estimate how much time is left when on >>> battery ? >> >> When the UPS does not report that, you can ask nut to provide an >> estimate by using the runtimecal directive. For instance I have in >> ups.conf on a system where I use an Inform low-end UPS: >> >> runtimecal = 120,100,480,50 >> default.battery.voltage.low = 21.2 >> default.battery.voltage.high = 27.7 >> >> >> >>...

...e a nice result whith blazer_ser driver! respect! # ./nut start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.4.1) Supported UPS detected with megatec protocol Vendor information read in 1 tries Battery runtime will not be calculated (runtimecal not set) <================= !!! Starting nut. Network UPS Tools upsd 2.4.1 listening on 172.16.0.220 port 3493 listening on 127.0.0.1 port 3493 Connected to UPS [Powercom]: blazer_ser-Powercom backup# upsc Powercom at localhost battery.voltage: 28.80 <========= !!! it is a normal? what u th...

...drv* it tells me the following: * * Starting UPS drivers ...* *Network UPS Tools - UPS driver controller 2.6.0* *Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0)* *Supported UPS detected with megatec protocol* *Vendor information unavailable* *Battery runtime will not be calculated (runtimecal not set)* So the information that is VERY IMPORTANT to properly poweroff the computer is not given. The battery charge, the time remained can't be calculated. Will it be supported in the future versions of the driver? -- B/R, Alexander Eremenko. -------------- next part -------------- An HT...