search for: chargetim

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

...230 output.voltage: 230.7 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 15 ups.status: OL ups.temperature: 41.5 ups.type: online Now I would elaborate the config and make use of the runtime guestimation. I added the following lines: runtimecal = 2000,100,5000,50 chargetime = 86400 default.battery.voltage.high = 109.6 default.battery.voltage.low = 84.4 default.battery.capacity = 40 I didn't do any measuerements yet and these data are based solely on the datasheet of my batteries and common sense. Now I get battery.capacity: 40 battery.charge: 0 battery.runtime:...

...*upsc output* * *battery.charge: 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 inpu...

Device manufacturer: JAWAN tech Name:JW-UPSLC02 [upsc output] battery.charge: 100 battery.voltage: 13.60 battery.voltage.high: 13 battery.voltage.low: 10.4 battery.voltage.nominal: 12.0 device.mfr: device.model: device.type: ups driver.name: blazer_usb driver.parameter.chargetime: 43200 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.vendorid: 0665 driver.version: 2.7.2 driver.version.internal: 0.11 input.current.nominal: 6.0 input.frequency: 60.0 input.frequency.nominal: 60 input.voltage: 118.0 input.voltage.f...

...vendorid = "0665" productid = "5161" [upsc output] battery.charge: 100 battery.voltage: 13.60 battery.voltage.high: 13 battery.voltage.low: 10.4 battery.voltage.nominal: 12.0 device.mfr: device.model: device.type: ups driver.name: blazer_usb driver.parameter.chargetime: 43200 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.vendorid: 0665 driver.version: 2.7.2 driver.version.internal: 0.11 input.current.nominal: 6.0 input.frequency: 60.0 input.frequency.nominal: 60 input.voltage: 118.0 inpu...

...te here or there and recommend 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...

...gatec/Q1 protocol USB driver 0.10 (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.voltag...

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

..."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 Information Command (I) 1...

...e, 2.6.2 upstream, linux 2.6.38-debian-bpo # /usr/local/src/nut-2.6.2/drivers/blazer_usb -u root -DDDDD -a ups Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.2) 0.000000 send_to_all: SETINFO driver.parameter.port "auto" 0.000080 send_to_all: SETINFO driver.parameter.chargetime "8" 0.000104 send_to_all: SETINFO driver.parameter.runtimecal "1200,100,3200,50" 0.000381 debug level is '5' 0.081525 Checking device (0D8C/0006) (005/002) ... 0.179808 Trying to match device 0.179822 Device does not match - skipping 0.179845...

...te here or there and recommend 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...