search for: idleload

...100 battery.runtime: 1000 <-- not reported by UPS (guesstimate) battery.voltage: 13.60 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.type: ups driver.flag.novendor: enabled driver.name: blazer_usb driver.parameter.chargetime: 43200 driver.parameter.idleload: 30 driver.parameter.pollinterval: 5 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.runtimecal: 300,100,900,50 <-- guessed from device rating driver.parameter.vendorid: 0665 driver.version: 2.6.4 driver.version.internal: 0.08 input.current.nominal: 3.0 input.frequ...

Hi Artronic art 1000 bl is supported partially by blazer_ser: battery.voltage: 13.40battery.voltage.nominal: 12.0 beeper.status: enabled device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.6.3 driver.version.internal: 1.51 input.current.nominal: 4.0 input.frequency: 50.1 input.frequency.nominal: 50 input.voltage: 232.9

On Feb 10, 2015, at 5:24 PM, Miroslav Todorov <miro0218 at yahoo.com> wrote: > Hi Artronic art 1000 bl is supported partially by blazer_ser: > When you say "partially supported", what is not supported? Are any of the values incorrect? -- Charles Lepple clepple at gmail

...mmend 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 how to improve our calculations, we're open to contributions. > - third: we have products with VID and PID: FFFF 0000, this is a problem...

...2.7.1) I have this settings: upsc ups91500 at localhost battery.charge: 100 battery.runtime: 12000 battery.voltage: 27.50 battery.voltage.high: 27.3 battery.voltage.low: 18.0 device.type: ups driver.flag.novendor: enabled driver.name: blazer_usb driver.parameter.chargetime: 43400 driver.parameter.idleload: 5 driver.parameter.offdelay: 600 driver.parameter.ondelay: 5 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/usb/hiddev0 driver.parameter.runtimecal: 600,100,900,50 driver.version: 2.7.1 driver.version.internal: 0.10 input.frequency: 50.0 input.voltage: 230.4 input.voltage.fault: 140....

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

...quot; vendor = "MEC" bus = "004" default.battery.voltage.high = 27.50 default.battery.voltage.low = 20.90 offdelay = 60 ondelay = 60 desc = "Fideltronik Viper 1200 UPS" runtimecal = 60,100,900,21 idleload = 10 chargetime = 28800 --------------------------------------------------- "lsusb -s 004:0002 -v": http://bpa.ksu.pl/pub/lsusb.txt (28kB) "nutdrv_qx -a Viper1200 -DDDD" output (init): http://bpa.ksu.pl/pub/nutdrv_qx_start.txt (7kB) Supported command: UPS Infor...

...mmend 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 how to improve our calculations, we're open to contributions. > - third: we have products with VID and PID: FFFF 0000, this is a problem...