override.battery.packs doesn't work to adjust reported battery voltage

baerenwaldfreund commented 2 years ago

I spent a lot of time reactivating my old UPS: Online Xanto S700 (build before 2012). But now it almost works. But I still have a small error.

The parameter 'override.battery.packs' doesn't work. Incorrect battery voltage is still reported.

Here the output:

:; upsc ups@localhost

Init SSL without certificate database
battery.charge: 100
battery.packs: 12
battery.runtime: 2400
battery.voltage: 2.27
battery.voltage.high: 26.00
battery.voltage.low: 22.00
battery.voltage.nominal: 24.00
device.mfr: Online-UPS
device.model: Xanto S700
device.type: ups
driver.name: nutdrv_qx
driver.parameter.chargetime: 43200
driver.parameter.idleload: 10
driver.parameter.pollfreq: 5
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/ttyUSB0
driver.parameter.protocol: q1
driver.parameter.runtimecal: 240,100,720,50
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: Q1 0.07
driver.version.internal: 0.28
input.frequency: 50.0
input.voltage: 243.8
input.voltage.fault: 243.8
output.voltage: 230.0
ups.beeper.status: disabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 0
ups.mfr: Online-UPS
ups.model: Xanto S700
ups.status: OL
ups.temperature: 25.0
ups.type: online

The batterie voltage is 2.27V. So I hoped the parameter 'override.battery.packs=12' will help. But it doesn't work. The reported voltage is still 2.27V.

Here is my ups.conf:

[ups]
        driver = nutdrv_qx
        port = "/dev/ttyUSB0"
        desc = "Online Xanto S700"
        protocol = q1
        override.battery.packs = 12
        default.battery.voltage.nominal = 24.00
        default.battery.voltage.low = 22.00
        default.battery.voltage.high = 26.00
        runtimecal = 240,100,720,50
        chargetime = 43200
        idleload = 10
        pollfreq = 5
        default.ups.mfr = "Online-UPS"
        default.ups.model = "Xanto S700"

What can I do to ensure that the correct voltage is displayed?

jimklimov commented 2 years ago

I am not sure how that value's override would impact voltage. I believe it is for tracking the hardware composition of (larger) UPSes - how many independent batteries it has, if some can be diagnosed and replaced separately: https://github.com/networkupstools/nut/blob/master/docs/nut-names.txt#L450

Beside that, the issue title is misleading: according to the data screenshot in your post, battery.packs: 12 is in fact applied :)

jimklimov commented 2 years ago

Also, just in case: are you able to measure the actual battery voltage with an electric meter?

Is the battery as old as the UPS or did you replace it - their lifetime is in a few years' range at best, so a 10 years old battery is probably dead and the voltage reading may be in fact correct ;)

baerenwaldfreund commented 2 years ago

thx for your reply.

The two batteries are new. I replaced the batteries a few weeks ago. The voltage should be 2x12V=24V (nominal voltage). I measured the open circuit voltage at 27,2V.

The original software of my UPS shows the right voltage: 27,24V. So the problem is in the nut-software.

Here the description of this parameter:

 override.battery.packs = value

    Some devices report a part of the total battery voltage.

    For instance, if battery.voltage.nominal is 24 V, but it reports a battery.voltage
of around 2 V, the number of battery.packs to correct this reading would be 12.
The driver will attempt to detect this automatically, but if this fails somehow,
you may want to override this value.

per https://networkupstools.org/docs/man/nutdrv_qx.html

So it should work. But it doesn't work :-(

I found another thread about this: https://github.com/networkupstools/nut/issues/1039

But I can't find a solution.

Any ideas?

EmersonHeiderich commented 2 years ago

I also have the same issue reported by the user. My NUT is returning Battery.voltage 225.00 and when viewing the UPS panel or measuring through a voltmeter, I get 216 Volts. I performed tests with blazer_ser and nutdrv_qx but got the same results.

Has anyone found a solution?

NOTE: Nobreate TS Shara TS SYAL 10 KVa connected via serial to USB converter.

ups@ups:~$ upsc tsshara01 Init SSL without certificate database battery.charge: 100 battery.voltage: 225.00 battery.voltage.high: 221 battery.voltage.low: 166.40 battery.voltage.nominal: 192.0 device.mfr: device.model: 11-06K device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyUSB0 driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.internal: 1.57 input.current.nominal: 47.0 input.frequency: 59.9 input.frequency.nominal: 60 input.voltage: 122.5 input.voltage.fault: 32.9 input.voltage.nominal: 127 output.voltage: 126.9 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: 11.001.011 ups.load: 36 ups.mfr: ups.model: 11-06K ups.status: OL ups.temperature: 25.0 ups.type: online

anphsw commented 2 years ago

Facing same problem with Powerman Online 1000 Plus (USB connection): (battery.packs are changed, but voltage still around 2V)

[ 1194.166542] usb 1-8: new low-speed USB device number 3 using xhci_hcd [ 1194.182429] usb 1-8: New USB device found, idVendor=0001, idProduct=0000 [ 1194.182434] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1194.182460] usb 1-8: Product: MEC0003 [ 1194.182463] usb 1-8: Manufacturer: MEC [ 1194.183546] usb 1-8: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 1194.728180] generic-usb 0003:0001:0000.0001: hiddev0,hidraw0: USB HID v1.00 Device [MEC MEC0003] on usb-0000:00:14.0-8/input0

$upsc ups0@localhost battery.charge: 100 battery.packs: 12 battery.voltage: 2.25 battery.voltage.high: 26.00 battery.voltage.low: 20.80 battery.voltage.nominal: 24 device.type: ups driver.name: nutdrv_qx driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: Megatec 0.06 driver.version.internal: 0.28 input.current.nominal: 4.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 235.4 input.voltage.fault: 120.0 input.voltage.nominal: 220 output.voltage: 235.3 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: V009B002D= ups.load: 31 ups.productid: 0000 ups.status: OL BYPASS ups.temperature: 27.0 ups.type: online ups.vendorid: 0001

anphsw commented 2 years ago

Tried blazer_usb with with same override.battery.packs value - it shows actual voltage, so maybe bug in nutdrv_qx only. $upsc ups0@localhost battery.charge: 100 battery.packs: 12 battery.voltage: 27.0 battery.voltage.high: 26.0 battery.voltage.low: 20.8 battery.voltage.nominal: 24.0 device.mfr: device.model: device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.internal: 0.12 input.current.nominal: 4.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 235.8 input.voltage.fault: 120.0 input.voltage.nominal: 220 output.voltage: 235.7 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: V009B002D= ups.load: 31 ups.mfr: ups.model: ups.productid: 0000 ups.status: OL BYPASS ups.temperature: 27.0 ups.type: online ups.vendorid: 0001

jimklimov commented 2 years ago

Just in case - might also be a bug in 2.7.4 release that was long ago. With 2.8.0 finally published this year, are you in position to check if it (or current git head) fares better?

mateuszdrab commented 2 years ago

I think there is a bug in nutdrv_qx, switched from blazer_usb and lost battery charge info additionally

y0g33 commented 2 years ago

FWIW, I can confirm with latest git head the bug in nutdrv_qx persists. Tested on ABB Powervalue with usb

Network UPS Tools - Generic Q* USB/Serial driver 0.32 (2.8.0-5-g9cb8de681)
USB communication driver (libusb 1.0) 0.43
battery.charge: 0
battery.voltage: 2.28
battery.voltage.high: 26.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: 2.8.0-5-g9cb8de681
driver.version.data: Megatec 0.06
driver.version.internal: 0.32
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 238.9
input.voltage.fault: 238.4
input.voltage.nominal: 240
output.voltage: 238.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 17
ups.productid: 5161
ups.status: OL BYPASS
ups.temperature: 24.9
ups.type: online
ups.vendorid: 0665

jimklimov commented 2 years ago

Just to clarify: https://github.com/networkupstools/nut/commit/9cb8de681 is not "latest git head" but the April release of NUT v2.8.0. Some bugs were fixed since then, though I don't remember anyone addressing this one.

One thing that comes to mind regards the change from libusb-0.1 to 1.0 - might be some issue in that lib or use of it?.. Can you build and test in-place (install not required) current NUT against libusb-0.1.x to rule that out?

jimklimov commented 2 years ago

Also by IDs in the last post, I think the subdriver should be cypress?

y0g33 commented 2 years ago

Found the error, was using old build config rules. After fixing the config, still no dice :-(.

battery.charge: 100
battery.voltage: 2.28
battery.voltage.high: 26.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: 2.8.0-497-g532bada82
driver.version.data: Megatec 0.06
driver.version.internal: 0.32
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 240.8
input.voltage.fault: 240.6
input.voltage.nominal: 240
output.voltage: 240.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 19
ups.productid: 5161
ups.status: OL BYPASS
ups.temperature: 23.0
ups.type: online
ups.vendorid: 0665

As requested here is an output when compiled with libusb-0.1.

battery.charge: 100
battery.voltage: 2.28
battery.voltage.high: 26.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: 2.8.0-497-g532bada82
driver.version.data: Megatec 0.06
driver.version.internal: 0.32
driver.version.usb: libusb-0.1 (or compat)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 238.8
input.voltage.fault: 239.6
input.voltage.nominal: 240
output.voltage: 238.8
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 18
ups.productid: 5161
ups.status: OL BYPASS
ups.temperature: 22.9
ups.type: online
ups.vendorid: 0665

jimklimov commented 2 years ago

Scribbling some notes here, to juggle for "differential diagnostics, people!" :)

blazer_ser returns IMHO strange results - battery (pack) yielding 216V? (or 225V for that matter... wondering if there is some rounding error with the maths and int-float conversions involved)
- To me, the hundreds of Volts are suspicious on batteries, if that is not a rack-sized stack of UPS with expansion cabinets... but if the original software, or panel, or Voltmeter confirm that... so be it
- "216 vs 225" needs a closer look at maths done in code. Note that part of NUT release v2.8.0 there was a large effort to fix compilation warnings, including revision of numeric type conversion and casting. It would be helpful to check if current codebase also mis-reports that reading, or fixed it "inadvertently" (and only delve further if not fixed). Notably, some casting from floating-point to integer types in the middle of calculations chain could cause effective rounding, and errors of that could aggregate in overall result.
blazer_usb seems to work as people expect it to, at least for NUT v2.7.4 codebase
nutdrv_qx seems to NOT work as people expect it to, regardless of NUT v2.7.4 of v2.8.0+ codebase and libusb0/1 backend, so at least not a regression of v2.8.0
some of the nutdrv_qx reports did not include a battery.packs reading so I suppose those reporters did not set the override parameter

Also:

the "override" and "default" parameters are not reflected in the "driver.*" collection complicating the investigation

I think there is a bug in nutdrv_qx, switched from blazer_usb and lost battery charge info additionally

They are different drivers with shared heritage, possibly not all mapping tables are in sync. And/or different subdriver or protocol settings were used - not enough detail in this message.

UPDATE: Per code analysis added below, these two issues may be related - seems charge is only calculated in some conditions if not reported by device directly. Although I think the intent was to provide it always - either natively from device reports, or guesstimated.

Noting similar code paths that deal with battery packs variables in blazer and nutdrv_qx drivers:

qx_initbattery() tries to guess battery.packs if not specified by config (or not learned from explicit data walk):
- https://github.com/networkupstools/nut/blob/4e3d0ecceac4cc6ad7d61df8f1676ecf6c7e4035/drivers/nutdrv_qx.c#L320-L359
- The bug might be here, in if (!dstate_getinfo("battery.charge") || !dstate_getinfo("battery.runtime")) { lots of init } clause at the start of the function -- at least for the original post, both dstate values are available so the driver never sets batt.packs it seems (and battery.voltage.high/low/nom for that matter):
  - https://github.com/networkupstools/nut/blob/4e3d0ecceac4cc6ad7d61df8f1676ecf6c7e4035/drivers/nutdrv_qx.c#L278-L283
- Looking at that if clause, it seems that by original design (very original - from initial commit https://github.com/networkupstools/nut/commit/dee3620a1876e4c760628787f9ad1ec3ba2e3ba2 of the driver a decade ago), if the device initially reports its charge and runtime on its own, we do not guesstimate them from voltages and amounts of batteries; arguably per that intention these should not have been reported at all.
- Maybe it makes sense to restructure this bit to do actually set values we have read from device or override config regardless of whether we have practical use for them. @clepple @aquette @zykh - WDYT?
- Notably blazer_initbattery() is not so shielded from the start: https://github.com/networkupstools/nut/blob/4e3d0ecceac4cc6ad7d61df8f1676ecf6c7e4035/drivers/blazer.c#L602-L610
Equivalent bit of logic in blazer to set up batt.packs (apparently from battery.voltage.nominal) is:
- https://github.com/networkupstools/nut/blob/4e3d0ecceac4cc6ad7d61df8f1676ecf6c7e4035/drivers/blazer.c#L133-L167
qx_ups_walk() part which deals with battery.voltage (and estimates battery.charge) is enabled by runtimecal option for some more complicated time-sliding logic to consider battery.packs, otherwise falls back to qx_battery() for linear approximation if the option is not set:
- https://github.com/networkupstools/nut/blob/4e3d0ecceac4cc6ad7d61df8f1676ecf6c7e4035/drivers/nutdrv_qx.c#L3739-L3823
blazer_battery() and qx_battery():
- https://github.com/networkupstools/nut/blob/4e3d0ecceac4cc6ad7d61df8f1676ecf6c7e4035/drivers/blazer.c#L89-L114
- https://github.com/networkupstools/nut/blob/4e3d0ecceac4cc6ad7d61df8f1676ecf6c7e4035/drivers/nutdrv_qx.c#L225-L255

jimklimov commented 2 years ago

Can you try building and running the driver from https://github.com/jimklimov/nut/tree/issue-1279 (source of PR #1652) to check if it behaves better? So far just making educated guesses...

y0g33 commented 2 years ago

I get compile time errors when I try to build issue-1279. This does not happen with the master-branch

Build system is RPI3 running ArchLinux.

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../include -isystem /usr/local/include -g -O2 -Wno-reserved-identifier -Wno-unknown-warning-option -std=gnu99 -Wno-system-headers -Wall -Wextra -Wsign-compare -pedantic -Wno-error -MT strptime.lo -MD -MP -MF .deps/strptime.Tpo -c strptime.c  -fPIC -DPIC -o .libs/strptime.o
strptime.c:59:25: error: expected ';' before 'uint64_t'
   59 | typedef unsigned __int64 uint64_t;
      |                         ^~~~~~~~~
      |                         ;
strptime.c:59:1: warning: useless type name in empty declaration
   59 | typedef unsigned __int64 uint64_t;
      | ^~~~~~~
strptime.c: In function 'strptime':
strptime.c:389:25: warning: implicit declaration of function '_tzset'; did you mean 'tzset'? [-Wimplicit-function-declaration]
  389 |                         _tzset();
      |                         ^~~~~~
      |                         tzset
At top level:
cc1: note: unrecognized command-line option '-Wno-unknown-warning-option' may have been intended to silence earlier diagnostics
cc1: note: unrecognized command-line option '-Wno-reserved-identifier' may have been intended to silence earlier diagnostics
make[1]: *** [Makefile:603: strptime.lo] Error 1
make[1]: Leaving directory '/home/alarm/scratch/nut/nut/common'
make: *** [Makefile:507: all] Error 2

jimklimov commented 2 years ago

That's odd... errors per se seem familiar from recent discussion on more building stacks for Windows. This file is a fallback for platforms that lack strptime() in their libc, lifted from BSD and not much chiseled since it happened to work well for the one platform and toolkit it was then intended for practically.

The primary problem here is that it got built at all. The function should just be in standard Linux/glibc. And it should be similar in current master that got built well...

If you have that workspace still around, can you check in config.log - search for strptime and see what it could complain about when checking for build environment's capabilities? Any compiler error (space rays hitting RAM, low disk space, antivirus, etc.) that end up in a failed check cause an autotools decision that the method is not available.

So is it something random, due to build machine constraints, or something NUT recipes and other code can address?

Do the two codebases you tried differ in configure.ac or m4/* files? Maybe some existing fix was not backported from master to issue branches?..

jimklimov commented 2 years ago

Also wondering if something important for the test happens reproducibly e.g. due to 32-bit ARM (right?)

y0g33 commented 2 years ago

It is a 64 bit system

output snippet from config.log

 $ ./configure --enable-NIT

## --------- ##
## Platform. ##
## --------- ##

uname -m = aarch64
uname -r = 5.15.61-4-rpi-ARCH
uname -s = Linux
uname -v = #1 SMP PREEMPT Thu Sep 1 13:34:10 MDT 2022

To the untrained eye only thing that stands out is when configure exits.

target_vendor='unknown'
udevdir=''
configure: caught signal 2
configure: exit 1

jimklimov commented 2 years ago

The signal 2 would be Ctrl+C... Did the configure script complete? It should end with a printout of major features and CFLAGS, with a 0 exit-code.

jimklimov commented 2 years ago

Also, did you ./autogen.sh it after changing branches?

y0g33 commented 2 years ago

My bad. I did run "./autogen.sh".

These are the steps I undertook to build.

git clone --branch issue-1279  https://github.com/jimklimov/nut.git

cd nut

./autogen.sh

./configure

make

This time I have outputs from config.log to work with.

configure:13072: $? = 0
configure:13085: result: yes
configure:13103: checking for strptime(s1,s2,tm)
configure:13177: gcc -o conftest -isystem /usr/local/include -g -O2 -Wno-reserved-identifier -Wno-unknown-warning-option -std=gnu99   conftest.c  >&5
conftest.c: In function 'main':
conftest.c:141:11: error: storage size of 'tm' isn't known
  141 | struct tm tm;
      |           ^~
conftest.c:143:11: warning: implicit declaration of function 'strptime' [-Wimplicit-function-declaration]
  143 | char *p = strptime(date, "%m/%d/%Y", &tm);
      |           ^~~~~~~~
At top level:
cc1: note: unrecognized command-line option '-Wno-unknown-warning-option' may have been intended to silence earlier diagnostics
cc1: note: unrecognized command-line option '-Wno-reserved-identifier' may have been intended to silence earlier diagnostics
configure:13177: $? = 1
configure: program exited with status 1
configure: failed program was:
| /* confdefs.h */

jimklimov commented 2 years ago

Can you please grep -R strptime /usr/{,*/}include/ to check if it is there?

Possibly the test in configure.ac slacks off and only tests with one of include <time.h> or include <sys/time.h>?.. (on most systems nowadays both exist and picking one suffices) In that case it should get encumbered with #if HAVE_TIME_H etc. like in include/timehead.h I guess.

y0g33 commented 2 years ago

Here is the requested output:

grep -R strptime /usr/{,*/}include/
/usr/include/isc/tm.h:isc_tm_strptime(const char *buf, const char *fmt, struct tm *tm);
/usr/include/time.h:extern char *strptime (const char *__restrict __s,
/usr/include/time.h:extern char *strptime_l (const char *__restrict __s,
/usr/include/c++/12.1.0/bits/locale_facets_nonio.tcc:  // Expand a strptime format string and parse it.  E.g., do_get_date() may
/usr/include/c++/12.1.0/bits/locale_facets_nonio.h:       *  specified for strftime(3)/strptime(3).  The actual parsing

jimklimov commented 2 years ago

Probably looking after the lines

configure: failed program was:
| /* confdefs.h */

you'd see a wall of text with generated tested source, including the macros about TIME headers the script found so far. But looking at the test code now, it should at least #include <time.h> as the fallback.

So then it seems like some systems thing why it does not serve the definitions. On my Debian Linux under hand, time.h includes bits/types/struct_tm.h (for target-dependent definitions) and only declares strptime if __USE_XOPEN is defined, which gets set in features.h if _GNU_SOURCE is defined among other ways to get it.

Your build does include -std=gnu99 so I'd expect that to be implicitly requested, but try running ./configure CFLAGS='-D_GNU_SOURCE=1' explicitly, to see if that rectifies things?

jimklimov commented 2 years ago

Cheers @y0g33 : I've got an Arch Linux container running now, and reproduced your issue. Hopefully the shuffle from #1659 above would fix it for you (did for me, and ./ci_build.sh passed except for integration tests with Python). New gcc-12 and clang-14 offered some new warnings FWIW (but that is a separate matter for another day)...

Until that gets tested and merged, you can try to git pull --all ; git cherry-pick ffc2023 in your workspace, and rerun the build (including autogen).

UPDATE: That PR was merged, so issue-1279 branch was updated to include current NUT master plus the proposed fix.

y0g33 commented 2 years ago

Thanks @jimklimov : Now the build did complete. Still no dice with override battery packs 😞.

battery.charge: 100
battery.packs: 12
battery.voltage: 2.28
battery.voltage.high: 26.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.override.battery.packs: 12
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-805-g65ed37042
driver.version.data: Megatec 0.06
driver.version.internal: 0.32
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 239.7
input.voltage.fault: 239.5
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 17
ups.productid: 5161
ups.status: OL
ups.temperature: 23.2
ups.type: online
ups.vendorid: 0665

jimklimov commented 2 years ago

Thanks for the report. At least, the part about reporting driver.parameter.override.* worked, and the parameter did set battery.packs.

Curiously, all previous reports stated ups.status: OL BYPASS but the latest one is ups.status: OL - do you know if that is a physically valid change (some maintenance works on the device at that time? anything in its own log if there is one?) or a change in the driver behavior (there were some CPS-related fixes since NUT v2.8.0 release, though ones I think of were IIRC for USB HID models).

As for battery.voltage not being further adjusted, I'm a bit of at a crossroads.

On one hand, this currently functions as designed: With the code analysis above in mind (as well as differences in some of these regards between nutdrv_qx and blazer* drivers), it seems that previous authors deemed this bit of info only useful as one of the factors in fallback estimation of battery charge and remaining battery.runtime (notably not seen produced in your case). At least, it also seems that for existing code having one of those values is reason to not bother about fixing up battery.voltage (I'd expect both of them to be required-served to avoid fallbacks, but oh well for the moment). Your device does serve at least a battery.charge: 100 hence fallback (or parts of it peppered around the codebase) is avoided, and so the "useless" adjustment from reported voltage of a single average(?) battery pack in your device's case to the summary voltage of all packs together as "the battery" (value in 24V range in your case) is also not done as it does not impact the charge/runtime fallback calculation which is not done because served.

On another hand, curious people like you do want a known reasonable voltage for "battery" overall. I wonder if it is reasonable to either introduce a new configuration option to be explicit about the requested adjustment, or to imply it by presence of the override.battery.packs setting, or "guess" by checking if the current battery.voltage is in the correct ballpark (between low/high if known, possibly via another override) or otherwise if the current battery.voltage times battery.packs is in that ballpark -- and if yes, adjust. I suppose an explicit option would be prudent to clearly either multiply or not - as the battery might discharge and get out of the ballpark during an outage, causing weird "adjusted" readings as the numbers for decision cross the border.

I do not know offhand if there are devices, at least those with Megatec Q* protocols, which natively report complete battery voltage or all report that of one cell/pack.

Yet another matter is the lack of battery.runtime reading in your case (and also some other reports above), which does not seem to be "guesstimated" instead either. This fallback might only be triggered by runtimecal driver option however, which is missing in your config.

jimklimov commented 2 years ago

Can you start the driver with higher debug level? In case of current NUT codebase (e.g. with the PR build you have) it may be as easy as specifying debug_min = 2 among driver options and restarting the driver (comment it away later).

I wonder if either there on driver's stderr (or in driver systemd unit journal, etc.) or in system log at INFO level, you'd see messages from https://github.com/networkupstools/nut/blob/bce0bff55f89fce06da3330e7ced07e4d906f28e/drivers/nutdrv_qx.c#L399 and below. Overall, if the driver initialization does recognize lack of battery.runtime served by device in your case, so whether it would prepare the fallback handling at all (and how - successfully or not for different components it looks at)?

My current guess is that it might have tried even initially, with "standard" driver, but failed to guess battery.packs because 2.28 * 12 = 27.36 which is outside the 20.80 .. 26.00 range your device reports... or driver guesses as a fork around 24.0 if only the nominal voltage is known from device (it logs "No values for battery high/low voltages" and "Using 'guesstimation' (low: %f, high: %f)!" then). Maybe yours does not have 12 packs, etc? Possibly disconnecting the battery assembly and checking with a voltmeter (or just looking at its printed label spec, indentations on casing, etc.) could be usefully informative. Are there two assemblies of 12V each?

y0g33 commented 2 years ago

Please find my answers to your queries.

Curiously, all previous reports stated ups.status: OL BYPASS but the latest one is ups.status: OL - do you know if that > is a physically valid change (some maintenance works on the device at that time? anything in its own log if there is one?) or a change in the driver behavior (there were some CPS-related fixes since NUT v2.8.0 release, though ones I think of were IIRC for USB HID models).

As the UPS is new. I was running some tests, The changes you see are intended change.

OL BYPASS -- was the Eco mode tests. OL -- It is running in production.

battery.voltage

Please note the low and high voltage values reported are guess estimated I have checked it at the Panel (random times) -- It does report 27.[2-6]0 as floating voltage Multimeter tests will follow soon.

battery.charge: 0

It could be that I provided output minus battery pack option from my initial testing

Battery

UPS uses 2x 12V (6 Cells per Unit) https://www.csb-battery.com.tw/english/01_product/02_detail.php?fid=17&pid=113

Spec sheet reported Floating Voltage matches with what I see at the panel

Runtimecal / battery.runtime

I have the values for Battery runtime. Please see the output below. I have observed it takes upto a minute (anecdotal) before I can see battery runtime

battery.charge: 100
battery.packs: 12
battery.runtime: 2400
battery.voltage: 2.26
battery.voltage.high: 26.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.override.battery.packs: 12
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-805-g65ed37042
driver.version.data: Megatec 0.06
driver.version.internal: 0.32
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 241.8
input.voltage.fault: 242.1
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 18
ups.productid: 5161
ups.status: OL
ups.temperature: 31.0
ups.type: online
ups.vendorid: 0665

jimklimov commented 2 years ago

Thanks for the confirmations and details! Especially that battery.runtime does eventually appear (it possibly takes a "full walk" of the device, or several?, for the driver to notice it does not have a native reading so it calculates one).

"Down and down went Alice into the rabbit hole..." - I can't actually find dstate_setinfo.*"battery.voltage" matches in QX-related drivers, neither nutdrv_qx nor blazer_usb. Some other (unrelated) drivers do have explicit assignments for the reading. A few nutdrv_qx subdrivers however have processing hooks, namely:

drivers/nutdrv_qx_ablerex.c:    { "battery.voltage",            0,      NULL,   "Q1\r", "",     47,     '(',    "",    28,                                                                                        31,      "%.2f", 0,      NULL,   NULL,   ablerex_battery },

=> lots of complicated if-then decisions

drivers/nutdrv_qx_masterguard.c:        { "battery.voltage",            0,      NULL,   "Q3\r", "",     71,     '(',   "",                                                                                        31,      35,     "%.1f", 0,                      NULL,   NULL,   masterguard_battvolt },

=> snprintf(value, valuelen, "%.2f", masterguard_my_numcells * s);

drivers/nutdrv_qx_voltronic-qs-hex.c:   { "battery.voltage",            0,      NULL,   "QS\r", "",     47,     '#',   "",                                                                                        32,      36,     "%.2f", 0,      NULL,   voltronic_qs_hex_preprocess_qs_answer,  voltronic_qs_hex_battery_voltage },

=> snprintf(value, valuelen, item->dfl, (val1 * val2) / 510.0);
=> but that one may be further complicated as a non-plaintext protocol dialect

Again, it seems like by default the packs count (times device-reported single pack voltage) was supposed to impact charge/runtime guesses but not to feed back into battery.voltage itself. Maybe a separate name for one of those is needed, to be clear...

jimklimov commented 2 years ago

Cheers, I've updated that PR with a "theoretical fix", introducing a battery_voltage_reports_one_pack driver option (a flag). If set, it should cause the reported battery.voltage to get multiplied while not impacting the "guesstimations", hopefully (e.g. avoiding both multiplying twice and not multiplying at all). Testing needed :)

y0g33 commented 2 years ago

"battery.charge" is zero , ergo "battery.runtime" is zero and the value for "battery.voltage.high" has also changed.

battery.charge: 0
battery.runtime: 0
battery.voltage: 2.28
battery.voltage.high: 30.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.bus: 001
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-840-gf26c1edae
driver.version.data: Megatec 0.07
driver.version.internal: 0.33
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 235.3
input.voltage.fault: 235.1
input.voltage.nominal: 240
output.voltage: 239.8
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 21
ups.productid: 5161
ups.status: OL
ups.temperature: 22.1
ups.type: online
ups.vendorid: 0665

jimklimov commented 2 years ago

Thanks!

The change for battery.voltage.high was expected (up from a factor of 130/120 to 150/120 over the nominal, to match that battery spec sheet with 15V desulphurization cycle voltage).

Loss of battery.charge and battery.runtime was not expected; did they appear after time (e.g. after a minute like for earlier reports)?

Did you remove/comment-away the override.battery.packs? Do the driver initialization logs indicate it tried to detect the value (though without charge/runtime, it might not do that...), or did 1.25 * batt.volt.nom (vs. 1.2*...) range expansion not suffice to decide that 12 is the suitable amount?

Finally, these driver.parameters.* do not indicate that you added the new flag battery_voltage_reports_one_pack to test, so I can't see if it (along with a decent battery.packs count) would adjust the reported battery.voltage to around 24V (27.36V in your case).

y0g33 commented 2 years ago

Only half of it made thru, I wanted to provide both the options.

With all options set including "battery_voltage_reports_one_pack". I was not sure if passing following assignment makes sense for "battery_voltage_reports_one_pack".

[abb1kva]
    battery_voltage_reports_one_pack =  "1"
    driver = "nutdrv_qx"
    port = "auto"
    vendorid = "0665"
    productid = "5161"
    bus = "001"
    subdriver = "cypress" 
    runtimecal = "240,100,360,75,1200,50,1380,25"
    override.battery.packs = "12"

Please find the output below:

battery.charge: 0
battery.packs: 12
battery.runtime: 0
battery.voltage: 2.27
battery.voltage.high: 30.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.battery_voltage_reports_one_pack: 1
driver.parameter.bus: 001
driver.parameter.override.battery.packs: 12
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-840-gf26c1edae
driver.version.data: Megatec 0.07
driver.version.internal: 0.33
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 236.5
input.voltage.fault: 236.6
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 15
ups.productid: 5161
ups.status: OL
ups.temperature: 20.9
ups.type: online
ups.vendorid: 0665

Loss of battery.charge and battery.runtime was not expected; did they appear after time (e.g. after a minute like for earlier reports)?

Yes "battery.runtime" shows up after a minute, but "battery.charge" comes up on first pass as "0".

jimklimov commented 2 years ago

Thanks, so it did not help battery.voltage multiply for some reason... (will look for typos then)

As for battery.charge - can you please double-check that running an older driver iteration reports it well again? (To rule out that the device changed behavior along the way, and confirm that some recent change the code did mis-fire)

Thanks in advance.

jimklimov commented 2 years ago

Okay, so at least found one typo why battery_voltage_reports_one_pack option did not get considered :\

But git diff 65ed37042..f26c1edae does not seem to show anything that would impact handling of battery.charge explicitly.

Wondering now if the added qx_multiply_battvolt mapping for battery.voltage misfired somehow (I guess Q1\r query returns a string with many readings; could the new method overwrite the original partially, to inject the new battery.voltage instead of "whatever should happen properly"?..)

y0g33 commented 2 years ago

FWIW, the old driver works w.r.t " battery.charge".

battery.charge: 100
battery.packs: 12
battery.voltage: 2.28
battery.voltage.high: 27.0
battery.voltage.low: 23.6
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.bus: 001
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: 2.8.0-497-g532bada82
driver.version.data: Megatec 0.06
driver.version.internal: 0.32
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 235.4
input.voltage.fault: 235.4
input.voltage.nominal: 240
output.voltage: 239.8
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 17
ups.productid: 5161
ups.status: OL
ups.temperature: 22.4
ups.type: online
ups.vendorid: 0665

Please let me know when can I do git pull and run a build again

jimklimov commented 2 years ago

Thanks for confirmation about the old driver. As for updated iteration - you can try that PR branch https://github.com/jimklimov/nut/tree/issue-1279 as it is now (96723b7 currently), thanks.

y0g33 commented 2 years ago

It seems we have hit another bug:

battery.charge: 0
battery.packs: 12
battery.runtime: 7
battery.voltage: 27.36
battery.voltage.high: 30.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.battery_voltage_reports_one_pack: 1
driver.parameter.bus: 001
driver.parameter.override.battery.packs: 12
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-843-g96723b74c
driver.version.data: Megatec 0.07
driver.version.internal: 0.33
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 239.7
input.voltage.fault: 239.7
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 17
ups.productid: 5161
ups.status: OL
ups.temperature: 21.5
ups.type: online
ups.vendorid: 0665

jimklimov commented 2 years ago

So... good news is that battery.voltage: 27.36 now appears as originally desired.

Bad news is battery.charge is reported, but as zero. Perhaps it was not reported by the device after all, but estimated by code? Or worse, reported by device BUT overwritten with code's estimations (which should not have fired then)? And then being somehow assumed to be 0 (and not -1 which is treated as unknown) it is not reevaluated? :\

I see qx_battery() can zero it out if negative (so something like (2.26 - 20.80) might end up wrong in such manner). Currently on the road - can you please instrument your copy of the function with upsdebugx() to print out interesting variables (e.g. does it consider the single-cell or full battery voltage in these maths?) and run the driver with sufficient debug level? And also log the qx_initbattery(void) if it sees a reasonable battery.charge (present, not zero)?

Runtime estimation is arcane magic of its own (and I think it only accepts two pairs of numbers, not 4 as in your screenshots - not sure OTOH if the extra values are ignored or confuse sscanf()); currently with "something" clobbering the charge evaluaton/query, I'm reluctant to look into it right now.

y0g33 commented 2 years ago

If it helps here is the output with debug level set to 5.


Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.000000        [D1] debug level is '5'
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.006239        [D1] Saving PID 113105 into /run/nut/nutdrv_qx-abb1kva.pid
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.006390        [D5] send_to_all: SETINFO device.type "ups"
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.006418        [D1] upsdrv_initups...
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021336        [D2] Checking device 1 of 5 (0665/5161)
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021489        [D2] - VendorID: 0665
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021512        [D2] - ProductID: 5161
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021531        [D2] - Manufacturer: unknown
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021557        [D2] - Product: unknown
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021575        [D2] - Serial Number: unknown
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021594        [D2] - Bus: 001
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021613        [D2] - Device: unknown
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021631        [D2] - Device release number: 0002
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021649        [D2] Trying to match device
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021673        [D3] match_function_regex: matching a device...
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021867        [D2] Device matches
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021890        [D2] Reading first configuration descriptor
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.021924        [D3] libusb_kernel_driver_active() returned 0
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.022041        [D2] Claimed interface 0 successfully
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.022069        [D3] nut_usb_set_altinterface: skipped libusb_set_interface_alt_setting(udev, 0, 0)
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.022105        [D5] send_to_all: SETINFO ups.vendorid "0665"
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.022131        [D5] send_to_all: SETINFO ups.productid "5161"
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.024146        [D3] send: QGS
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.088984        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 31 20 35
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.121971        [D5] read [  8]: (8 bytes) => 30 2e 30 20 32 33 39 2e
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.162963        [D5] read [ 16]: (8 bytes) => 38 20 35 30 2e 30 20 30
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.195965        [D5] read [ 24]: (8 bytes) => 30 30 2e 38 20 30 31 36
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.236944        [D5] read [ 32]: (8 bytes) => 20 33 37 32 2e 33 20 33
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.277945        [D5] read [ 40]: (8 bytes) => 38 38 2e 33 20 30 32 37
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.326947        [D5] read [ 48]: (8 bytes) => 2e 32 20 2d 2d 2d 2e 2d
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.359942        [D5] read [ 56]: (8 bytes) => 20 30 32 38 2e 38 20 31
Sep 23 03:43:49 threepi01 nut-driver@abb1kva[113105]:    0.392941        [D5] read [ 64]: (8 bytes) => 30 30 30 30 30 30 30 30
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.417948        [D5] read [ 72]: (8 bytes) => 30 30 31 0d 00 00 00 00
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.418012        [D3] read: (243.1 50.0 239.8 50.0 000.8 016 372.3 388.3 027.2 ---.- 028.8 100000000001
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.418115        [D5] send_to_all: SETINFO input.voltage "243.1"
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.420181        [D3] send: QPI
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.468942        [D5] read [  0]: (8 bytes) => 28 50 49 30 35 0d 00 00
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.468995        [D3] read: (PI05
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.469089        Protocol [PI05] is not supported by this driver
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.469128        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: PI05]
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.469172        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.472549        [D3] send: QGS
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.528951        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 31 20 35
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.569942        [D5] read [  8]: (8 bytes) => 30 2e 30 20 32 33 39 2e
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.602940        [D5] read [ 16]: (8 bytes) => 37 20 35 30 2e 30 20 30
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.643940        [D5] read [ 24]: (8 bytes) => 30 30 2e 37 20 30 31 38
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.676937        [D5] read [ 32]: (8 bytes) => 20 33 37 30 2e 31 20 33
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.717947        [D5] read [ 40]: (8 bytes) => 38 36 2e 34 20 30 32 37
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.750941        [D5] read [ 48]: (8 bytes) => 2e 32 20 2d 2d 2d 2e 2d
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.807945        [D5] read [ 56]: (8 bytes) => 20 30 32 38 2e 38 20 31
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.840932        [D5] read [ 64]: (8 bytes) => 30 30 30 30 30 30 30 30
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.857943        [D5] read [ 72]: (8 bytes) => 30 30 31 0d 00 00 00 00
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.857999        [D3] read: (243.1 50.0 239.7 50.0 000.7 018 370.1 386.4 027.2 ---.- 028.8 100000000001
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.858086        [D5] send_to_all: SETINFO input.voltage "243.1"
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.861426        [D3] send: QPI
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.909950        [D5] read [  0]: (8 bytes) => 28 50 49 30 35 0d 00 00
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.910014        [D3] read: (PI05
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.910057        Protocol [PI05] is not supported by this driver
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.910094        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: PI05]
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.910137        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.912175        [D3] send: QGS
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    0.976953        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 31 20 35
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.009945        [D5] read [  8]: (8 bytes) => 30 2e 30 20 32 33 39 2e
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.050968        [D5] read [ 16]: (8 bytes) => 37 20 35 30 2e 30 20 30
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.091942        [D5] read [ 24]: (8 bytes) => 30 30 2e 36 20 30 31 36
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.124935        [D5] read [ 32]: (8 bytes) => 20 33 37 31 2e 31 20 33
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.165945        [D5] read [ 40]: (8 bytes) => 38 35 2e 34 20 30 32 37
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.198936        [D5] read [ 48]: (8 bytes) => 2e 32 20 2d 2d 2d 2e 2d
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.231934        [D5] read [ 56]: (8 bytes) => 20 30 32 38 2e 38 20 31
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.272939        [D5] read [ 64]: (8 bytes) => 30 30 30 30 30 30 30 30
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.289950        [D5] read [ 72]: (8 bytes) => 30 30 31 0d 00 00 00 00
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.290011        [D3] read: (243.1 50.0 239.7 50.0 000.6 016 371.1 385.4 027.2 ---.- 028.8 100000000001
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.290100        [D5] send_to_all: SETINFO input.voltage "243.1"
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.292172        [D3] send: QPI
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.340936        [D5] read [  0]: (8 bytes) => 28 50 49 30 35 0d 00 00
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.340989        [D3] read: (PI05
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.341075        Protocol [PI05] is not supported by this driver
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.341116        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: PI05]
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.341168        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.343180        [D3] send: M
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.391940        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.391995        [D3] read: (NAK
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.392038        [D2] voltronic_qs_protocol: invalid protocol [(NAK]
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.392075        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: (NAK]
Sep 23 03:43:50 threepi01 nut-driver@abb1kva[113105]:    1.395425        [D3] send: M
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.435950        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.436009        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.436052        [D2] voltronic_qs_protocol: invalid protocol [(NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.436089        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: (NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.438173        [D3] send: M
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.486938        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.486993        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.487037        [D2] voltronic_qs_protocol: invalid protocol [(NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.487077        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: (NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.490426        [D3] send: M
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.538984        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.539064        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.539112        [D2] voltronic_qs_hex_protocol: invalid protocol [(NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.539149        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: (NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.541189        [D3] send: M
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.589940        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.589995        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.590049        [D2] voltronic_qs_hex_protocol: invalid protocol [(NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.590087        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: (NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.593432        [D3] send: M
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.641942        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.642003        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.642049        [D2] voltronic_qs_hex_protocol: invalid protocol [(NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.642086        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: (NAK]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.644172        [D3] send: QS
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.700941        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.700997        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.701079        [D2] qx_process_answer: short reply (input.voltage)
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.704418        [D3] send: QS
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.776944        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.777042        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.777086        [D2] qx_process_answer: short reply (input.voltage)
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.780430        [D3] send: QS
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.836941        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.837034        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.837199        [D2] qx_process_answer: short reply (input.voltage)
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.839308        [D3] send: D
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.887946        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.888004        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.888044        [D2] qx_process_answer: short reply (input.voltage)
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.891416        [D3] send: D
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.939955        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.940020        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.940061        [D2] qx_process_answer: short reply (input.voltage)
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.942175        [D3] send: D
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.990977        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.991051        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.991091        [D2] qx_process_answer: short reply (input.voltage)
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    1.993193        [D3] send: Q1
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.049943        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 33 20 32
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.082968        [D5] read [  8]: (8 bytes) => 34 33 2e 32 20 32 33 39
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.123945        [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 34 20 35
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.164934        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.205944        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.230935        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.230995        [D3] read: (243.3 243.2 239.7 014 50.0 2.26 28.8 00000001
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.231081        [D5] send_to_all: SETINFO input.voltage "243.3"
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.233184        [D3] send: ID
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.289946        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.289999        [D3] read: (NAK
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.290040        [D4] bestups_preprocess_id_answer: wrong length [device.model: 8]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.290079        [D4] qx_process: failed to preprocess answer [device.model]
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.290123        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.292173        [D3] send: Q1
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.348940        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 33 20 32
Sep 23 03:43:51 threepi01 nut-driver@abb1kva[113105]:    2.381944        [D5] read [  8]: (8 bytes) => 34 33 2e 31 20 32 33 39
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.430938        [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 37 20 35
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.463929        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.504943        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.529944        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.530003        [D3] read: (243.3 243.1 239.7 017 50.0 2.26 28.8 00000001
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.530086        [D5] send_to_all: SETINFO input.voltage "243.3"
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.532170        [D3] send: ID
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.588942        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.589047        [D3] read: (NAK
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.589091        [D4] bestups_preprocess_id_answer: wrong length [device.model: 8]
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.589128        [D4] qx_process: failed to preprocess answer [device.model]
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.589175        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.592545        [D3] send: Q1
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.648958        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 33 20 32
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.681951        [D5] read [  8]: (8 bytes) => 34 33 2e 30 20 32 33 39
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.722932        [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 35 20 35
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.763931        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.820986        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.853942        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.854002        [D3] read: (243.3 243.0 239.7 015 50.0 2.26 28.8 00000001
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.854090        [D5] send_to_all: SETINFO input.voltage "243.3"
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.856178        [D3] send: ID
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.912937        [D5] read [  0]: (8 bytes) => 28 4e 41 4b 0d 00 00 00
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.912994        [D3] read: (NAK
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.913074        [D4] bestups_preprocess_id_answer: wrong length [device.model: 8]
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.913113        [D4] qx_process: failed to preprocess answer [device.model]
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.913166        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.915183        [D3] send: Q1
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    2.987953        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 33 20 32
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.020938        [D5] read [  8]: (8 bytes) => 34 33 2e 35 20 32 33 39
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.061933        [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 38 20 35
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.102961        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.143941        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.176948        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.177064        [D3] read: (243.3 243.5 239.7 018 50.0 2.26 28.8 00000001
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.177152        [D5] send_to_all: SETINFO input.voltage "243.3"
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.179175        [D3] send: QPI
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.227947        [D5] read [  0]: (8 bytes) => 28 50 49 30 35 0d 00 00
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.228008        [D3] read: (PI05
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.228062        Protocol [PI05] is not supported by this driver
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.228101        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: PI05]
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.228145        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.230177        [D3] send: Q1
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.294949        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 32 20 32
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.335936        [D5] read [  8]: (8 bytes) => 34 33 2e 31 20 32 33 39
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.376935        [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 39 20 35
Sep 23 03:43:52 threepi01 nut-driver@abb1kva[113105]:    3.409941        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.450936        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.483932        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.483989        [D3] read: (243.2 243.1 239.7 019 50.0 2.26 28.8 00000001
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.484072        [D5] send_to_all: SETINFO input.voltage "243.2"
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.487423        [D3] send: QPI
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.535957        [D5] read [  0]: (8 bytes) => 28 50 49 30 35 0d 00 00
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.536021        [D3] read: (PI05
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.536065        Protocol [PI05] is not supported by this driver
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.536102        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: PI05]
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.536146        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.538183        [D3] send: Q1
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.594946        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 32 20 32
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.635943        [D5] read [  8]: (8 bytes) => 34 32 2e 38 20 32 33 39
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.676953        [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 36 20 35
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.709931        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.742934        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.775930        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.775989        [D3] read: (243.2 242.8 239.8 016 50.0 2.26 28.8 00000001
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.776083        [D5] send_to_all: SETINFO input.voltage "243.2"
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.778174        [D3] send: QPI
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.826947        [D5] read [  0]: (8 bytes) => 28 50 49 30 35 0d 00 00
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.827007        [D3] read: (PI05
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.827060        Protocol [PI05] is not supported by this driver
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.827098        [D4] ups_infoval_set: failed to preprocess value [ups.firmware.aux: PI05]
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.827144        [D5] send_to_all: DELINFO input.voltage
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.829240        [D3] send: Q1
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.885959        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 32 20 32
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.926943        [D5] read [  8]: (8 bytes) => 34 32 2e 39 20 32 33 39
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    3.959942        [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 39 20 35
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.008945        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.041935        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.074937        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.074993        [D3] read: (243.2 242.9 239.8 019 50.0 2.26 28.8 00000001
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.075075        [D5] send_to_all: SETINFO input.voltage "243.2"
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.077203        [D3] send: I
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.125964        [D5] read [  0]: (8 bytes) => 23 20 20 20 20 20 20 20
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.166939        [D5] read [  8]: (8 bytes) => 20 20 20 20 20 20 20 20
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.199944        [D5] read [ 16]: (8 bytes) => 20 57 50 48 56 52 31 4b
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.240952        [D5] read [ 24]: (8 bytes) => 30 20 20 20 30 32 37 32
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.273940        [D5] read [ 32]: (8 bytes) => 34 2e 30 38 20 20 0d 00
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.273999        [D3] read: #                WPHVR1K0   02724.08
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.274068        [D5] send_to_all: SETINFO ups.firmware "02724.08"
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.274106        Using protocol: Megatec 0.07
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.274176        [D5] send_to_all: SETINFO driver.version "Windows-v2.8.0-alpha3-843-g96723b74c"
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.274225        [D5] send_to_all: SETINFO driver.version.internal "0.33"
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.274273        [D5] send_to_all: SETINFO driver.name "nutdrv_qx"
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.274309        [D1] upsdrv_initinfo...
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.274354        [D5] send_to_all: SETINFO driver.version.data "Megatec 0.07"
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.276437        [D3] send: Q1
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.348950        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 31 20 32
Sep 23 03:43:53 threepi01 nut-driver@abb1kva[113105]:    4.381934        [D5] read [  8]: (8 bytes) => 34 32 2e 37 20 32 33 39
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.438932        [D5] read [ 16]: (8 bytes) => 2e 37 20 30 32 30 20 35
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.471929        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.512980        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.545983        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.546072        [D3] read: (243.1 242.7 239.7 020 50.0 2.26 28.8 00000001
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.546183        [D5] send_to_all: SETINFO input.voltage.fault "242.7"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.546259        [D5] send_to_all: SETINFO output.voltage "239.7"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.546323        [D5] send_to_all: SETINFO ups.load "20"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.546386        [D5] send_to_all: SETINFO input.frequency "50.0"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.546444        [D5] send_to_all: SETINFO battery.voltage "2.26"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.546908        [D5] send_to_all: SETINFO ups.temperature "28.8"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.546970        [D5] update_status: OL
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.547044        [D5] update_status: !LB
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.547114        [D5] send_to_all: SETINFO ups.type "online"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.547159        [D5] update_status: !CAL
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.547204        [D5] update_status: !FSD
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.547264        [D5] send_to_all: SETINFO ups.beeper.status "enabled"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.549713        [D3] send: F
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.599002        [D5] read [  0]: (8 bytes) => 23 32 34 30 2e 30 20 30
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.639990        [D5] read [  8]: (8 bytes) => 30 34 20 30 32 34 2e 30
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.664981        [D5] read [ 16]: (8 bytes) => 20 35 30 2e 30 0d 00 00
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.665114        [D3] read: #240.0 004 024.0 50.0
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.665221        [D5] send_to_all: SETINFO input.voltage.nominal "240"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.665293        [D5] send_to_all: SETINFO input.current.nominal "4.0"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.665364        [D5] send_to_all: SETINFO battery.voltage.nominal "24.0"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.665425        [D5] send_to_all: SETINFO input.frequency.nominal "50"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.667603        [D3] send: I
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.717032        [D5] read [  0]: (8 bytes) => 23 20 20 20 20 20 20 20
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.757997        [D5] read [  8]: (8 bytes) => 20 20 20 20 20 20 20 20
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.798992        [D5] read [ 16]: (8 bytes) => 20 57 50 48 56 52 31 4b
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.840006        [D5] read [ 24]: (8 bytes) => 30 20 20 20 30 32 37 32
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.872981        [D5] read [ 32]: (8 bytes) => 34 2e 30 38 20 20 0d 00
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873104        [D3] read: #                WPHVR1K0   02724.08
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873160        [D1] ups_infoval_set: non significant value [device.mfr]
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873233        [D5] send_to_all: SETINFO device.model "WPHVR1K0"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873284        [D5] send_to_all: ADDCMD beeper.toggle
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873328        [D5] send_to_all: ADDCMD load.off
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873370        [D5] send_to_all: ADDCMD load.on
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873421        [D5] send_to_all: ADDCMD shutdown.return
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873465        [D5] send_to_all: ADDCMD shutdown.stayoff
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873507        [D5] send_to_all: ADDCMD shutdown.stop
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873574        [D5] send_to_all: ADDCMD test.battery.start
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873620        [D5] send_to_all: ADDCMD test.battery.start.deep
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873660        [D5] send_to_all: ADDCMD test.battery.start.quick
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873702        [D5] send_to_all: ADDCMD test.battery.stop
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873747        [D5] send_to_all: SETINFO ups.delay.start "180"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873789        [D5] send_to_all: SETFLAGS ups.delay.start RW
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873835        [D5] send_to_all: ADDRANGE ups.delay.start 0 599940
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873876        [D5] send_to_all: SETFLAGS ups.delay.start RW NUMBER
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873937        [D5] send_to_all: SETINFO ups.delay.shutdown "30"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.873986        [D5] send_to_all: SETFLAGS ups.delay.shutdown RW
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874028        [D5] send_to_all: ADDRANGE ups.delay.shutdown 12 600
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874071        [D5] send_to_all: SETFLAGS ups.delay.shutdown RW NUMBER
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874116        No values for battery high/low voltages
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874170        [D5] send_to_all: SETINFO battery.voltage.low "20.80"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874218        [D5] send_to_all: SETINFO battery.voltage.high "30.00"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874260        Using 'guesstimation' (low: 20.800000, high: 30.000000)!
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874321        [D5] send_to_all: SETINFO battery.charge "0"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874447        [D2] qx_initbattery: battery runtime exponent: 1.409
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874493        [D2] qx_initbattery: battery runtime nominal: 240.0
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874533        [D2] qx_initbattery: battery runtime estimate: 0.0
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874565        No charge time specified, using built in default [43200 seconds]
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874613        No idle load specified, using built in default [10.0 %]
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874673        [D5] send_to_all: SETINFO driver.parameter.pollfreq "30"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874710        [D1] upsdrv_updateinfo...
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.874747        [D1] Quick update...
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.876945        [D3] send: Q1
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.933969        [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 31 20 32
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    4.974989        [D5] read [  8]: (8 bytes) => 34 33 2e 32 20 32 33 39
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.007945        [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 39 20 35
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.048939        [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.089949        [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.122976        [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123060        [D3] read: (243.1 243.2 239.7 019 50.0 2.26 28.8 00000001
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123113        [D5] update_status: OL
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123161        [D5] update_status: !LB
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123212        [D5] update_status: !CAL
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123256        [D5] update_status: !FSD
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123321        [D5] send_to_all: SETINFO ups.status "OL"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123361        [D5] send_to_all: DATAOK
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123747        [D2] dstate_init: sock /var/lib/nut/nutdrv_qx-abb1kva open on fd 9
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123809        [D5] send_to_all: SETINFO driver.parameter.pollinterval "2"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113105]:    5.123858        [D5] send_to_all: SETINFO driver.parameter.synchronous "auto"
Sep 23 03:43:54 threepi01 nut-driver@abb1kva[113077]: Network UPS Tools - UPS driver controller Windows-v2.8.0-alpha3-843-g96723b74c
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: Startup successful
Sep 23 03:43:54 threepi01 systemd[1]: Started Network UPS Tools - device driver for NUT device 'abb1kva'.
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D1] Saving PID 113107 into /run/nut/nutdrv_qx-abb1kva.pid
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 30 20 32
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 32 20 32 33 39
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 37 20 30 32 30 20 35
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D3] read: (243.0 243.2 239.7 020 50.0 2.26 28.8 00000001
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:43:54 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: sock_connect: enabling asynchronous mode (auto)
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D3] new connection on fd 10
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO battery.charge "0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO battery.charge "0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO battery.packs "12"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO battery.packs "12"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETFLAGS battery.packs
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETFLAGS battery.packs
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO battery.voltage "2.26"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO battery.voltage "2.26"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO battery.voltage.high "30.00"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO battery.voltage.high "30.00"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO battery.voltage.low "20.80"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO battery.voltage.low "20.80"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO battery.voltage.nominal "24.0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO battery.voltage.nominal "24.0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO device.model "WPHVR1K0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO device.model "WPHVR1K0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO device.type "ups"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO device.type "ups"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.name "nutdrv_qx"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.name "nutdrv_qx"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.battery_voltage_reports_one_pack "1"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.battery_voltage_reports_one_pack "1"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.bus "001"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.bus "001"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.override.battery.packs "12"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.override.battery.packs "12"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.pollfreq "30"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.pollfreq "30"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.pollinterval "2"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.pollinterval "2"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.port "auto"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.port "auto"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.productid "5161"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.productid "5161"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.runtimecal "240,100,360,75,1200,50,1380,25"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.runtimecal "240,100,360,75,1200,50,1380,25"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.subdriver "cypress"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.subdriver "cypress"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.synchronous "auto"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.synchronous "auto"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.parameter.vendorid "0665"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.parameter.vendorid "0665"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.version "Windows-v2.8.0-alpha3-843-g96723b74c"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.version "Windows-v2.8.0-alpha3-843-g96723b74c"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.version.data "Megatec 0.07"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.version.data "Megatec 0.07"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.version.internal "0.33"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.version.internal "0.33"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO driver.version.usb "libusb-1.0.26 (API: 0x1000109)"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO driver.version.usb "libusb-1.0.26 (API: 0x1000109)"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO input.current.nominal "4.0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO input.current.nominal "4.0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO input.frequency "50.0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO input.frequency "50.0"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO input.frequency.nominal "50"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO input.frequency.nominal "50"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO input.voltage "243.2"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO input.voltage "243.2"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO input.voltage.fault "242.7"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO input.voltage.fault "242.7"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO input.voltage.nominal "240"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO input.voltage.nominal "240"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO output.voltage "239.7"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO output.voltage "239.7"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.beeper.status "enabled"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.beeper.status "enabled"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.delay.shutdown "30"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.delay.shutdown "30"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDRANGE ups.delay.shutdown 12 600
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDRANGE ups.delay.shutdown 12 600
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETFLAGS ups.delay.shutdown RW NUMBER
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETFLAGS ups.delay.shutdown RW NUMBER
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.delay.start "180"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.delay.start "180"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDRANGE ups.delay.start 0 599940
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDRANGE ups.delay.start 0 599940
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETFLAGS ups.delay.start RW NUMBER
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETFLAGS ups.delay.start RW NUMBER
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.firmware "02724.08"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.firmware "02724.08"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.load "20"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.load "20"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.productid "5161"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.productid "5161"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.status "OL"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.status "OL"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.temperature "28.8"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.temperature "28.8"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.type "online"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.type "online"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending SETINFO ups.vendorid "0665"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: SETINFO ups.vendorid "0665"
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD beeper.toggle
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD beeper.toggle
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD load.off
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD load.off
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD load.on
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD load.on
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD shutdown.return
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD shutdown.return
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD shutdown.stayoff
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD shutdown.stayoff
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD shutdown.stop
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD shutdown.stop
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD test.battery.start
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD test.battery.start
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD test.battery.start.deep
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD test.battery.start.deep
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD test.battery.start.quick
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD test.battery.start.quick
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending ADDCMD test.battery.stop
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: ADDCMD test.battery.stop
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending DATAOK
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: DATAOK
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending DUMPDONE
Sep 23 03:43:55 threepi01 nutdrv_qx[113107]: [D5] send_to_one: DUMPDONE
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 30 20 32
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 38 20 32 33 39
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 39 20 35
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D3] read: (243.0 242.8 239.8 019 50.0 2.26 28.8 00000001
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:43:56 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 39 20 32
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 30 20 32 33 39
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 37 20 35
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 35 20 30 30
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D3] read: (242.9 243.0 239.8 017 50.0 2.26 28.5 00000001
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:43:58 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 33 20 32
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 35 20 32 33 39
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 39 20 35
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D3] read: (243.3 243.5 239.7 019 50.0 2.26 28.8 00000001
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:00 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 33 20 32
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 36 20 32 33 39
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 37 20 35
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D3] read: (243.3 243.6 239.7 017 50.0 2.26 28.8 00000001
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:02 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:03 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending PONG
Sep 23 03:44:03 threepi01 nutdrv_qx[113107]: [D5] send_to_one: PONG
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 36 20 32
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 34 20 32 33 39
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 38 20 35
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D3] read: (242.6 242.4 239.7 018 50.0 2.26 28.8 00000001
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:04 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 32 20 32
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 37 20 32 33 39
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 36 20 35
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D3] read: (243.2 242.7 239.7 016 50.0 2.26 28.8 00000001
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:06 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:08 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:08 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:08 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:08 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 37 20 32
Sep 23 03:44:08 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 39 20 32 33 39
Sep 23 03:44:08 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 39 20 35
Sep 23 03:44:08 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:08 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:09 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:09 threepi01 nutdrv_qx[113107]: [D3] read: (242.7 242.9 239.8 019 50.0 2.26 28.8 00000001
Sep 23 03:44:09 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:09 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:09 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:09 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:09 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending PONG
Sep 23 03:44:09 threepi01 nutdrv_qx[113107]: [D5] send_to_one: PONG
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 39 20 32
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 36 20 32 33 39
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 38 20 35
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D3] read: (242.9 242.6 239.8 018 50.0 2.26 28.8 00000001
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:10 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 30 20 32
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 37 20 32 33 39
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 32 20 35
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D3] read: (243.0 242.7 239.8 012 50.0 2.26 28.8 00000001
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:12 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 33 20 32
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 35 20 32 33 39
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 38 20 35
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D3] read: (243.3 243.5 239.8 018 50.0 2.26 28.8 00000001
Sep 23 03:44:14 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:15 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:15 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:15 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:15 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending PONG
Sep 23 03:44:15 threepi01 nutdrv_qx[113107]: [D5] send_to_one: PONG
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 32 20 32
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 38 20 32 33 39
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 37 20 35
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D3] read: (243.2 242.8 239.8 017 50.0 2.26 28.8 00000001
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:16 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 36 20 32
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 30 20 32 33 39
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 37 20 35
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D3] read: (242.6 242.0 239.8 017 50.0 2.26 28.8 00000001
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:18 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:20 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:20 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:20 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:20 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 33 20 32
Sep 23 03:44:20 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 33 20 32 33 39
Sep 23 03:44:20 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 38 20 35
Sep 23 03:44:20 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:20 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:21 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:21 threepi01 nutdrv_qx[113107]: [D3] read: (242.3 242.3 239.8 018 50.0 2.26 28.8 00000001
Sep 23 03:44:21 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:21 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:21 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:21 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:21 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending PONG
Sep 23 03:44:21 threepi01 nutdrv_qx[113107]: [D5] send_to_one: PONG
Sep 23 03:44:22 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:22 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:22 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:22 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 32 20 32
Sep 23 03:44:22 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 37 20 32 33 39
Sep 23 03:44:22 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 37 20 35
Sep 23 03:44:22 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:22 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:23 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:23 threepi01 nutdrv_qx[113107]: [D3] read: (243.2 242.7 239.8 017 50.0 2.26 28.8 00000001
Sep 23 03:44:23 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:23 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:23 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:23 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:24 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:24 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:24 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:24 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 31 20 32
Sep 23 03:44:24 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 34 20 32 33 39
Sep 23 03:44:24 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 38 20 35
Sep 23 03:44:24 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:24 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:25 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:25 threepi01 nutdrv_qx[113107]: [D3] read: (243.1 243.4 239.7 018 50.0 2.26 28.8 00000001
Sep 23 03:44:25 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:25 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:25 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:25 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:26 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:26 threepi01 nutdrv_qx[113107]: [D1] Full update...
Sep 23 03:44:26 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:26 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 31 20 32
Sep 23 03:44:26 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 32 20 32 33 39
Sep 23 03:44:26 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 37 20 35
Sep 23 03:44:26 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D3] read: (243.1 243.2 239.7 017 50.0 2.26 28.8 00000001
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] send_to_all: SETINFO input.voltage "243.1"
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] send_to_all: SETINFO input.voltage.fault "243.2"
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] send_to_all: SETINFO ups.load "17"
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] send_to_all: SETINFO battery.voltage "27.12"
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:27 threepi01 nutdrv_qx[113107]: [D5] send_to_all: SETINFO battery.runtime "2"
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 39 20 32
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 35 20 32 33 39
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 38 20 35
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D3] read: (242.9 242.5 239.8 018 50.0 2.26 28.8 00000001
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:28 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 38 20 32
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 37 20 32 33 39
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 36 20 35
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D3] read: (242.8 242.7 239.8 016 50.0 2.26 28.8 00000001
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:30 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:32 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:32 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:32 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:32 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 32 20 32
Sep 23 03:44:32 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 32 20 32 33 39
Sep 23 03:44:32 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 37 20 35
Sep 23 03:44:32 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:32 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:33 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:33 threepi01 nutdrv_qx[113107]: [D3] read: (243.2 243.2 239.8 017 50.0 2.26 28.8 00000001
Sep 23 03:44:33 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:33 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:33 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:33 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:33 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending PONG
Sep 23 03:44:33 threepi01 nutdrv_qx[113107]: [D5] send_to_one: PONG
Sep 23 03:44:34 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:34 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:34 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:34 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 32 2e 37 20 32
Sep 23 03:44:34 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 39 20 32 33 39
Sep 23 03:44:34 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 37 20 30 31 38 20 35
Sep 23 03:44:34 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:34 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:35 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:35 threepi01 nutdrv_qx[113107]: [D3] read: (242.7 242.9 239.7 018 50.0 2.26 28.8 00000001
Sep 23 03:44:35 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:35 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:35 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:35 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:36 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:36 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:36 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:36 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 30 20 32
Sep 23 03:44:36 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 32 2e 36 20 32 33 39
Sep 23 03:44:36 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 35 20 35
Sep 23 03:44:36 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:36 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:37 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:37 threepi01 nutdrv_qx[113107]: [D3] read: (243.0 242.6 239.8 015 50.0 2.26 28.8 00000001
Sep 23 03:44:37 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:37 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:37 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:37 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:38 threepi01 nutdrv_qx[113107]: [D1] upsdrv_updateinfo...
Sep 23 03:44:38 threepi01 nutdrv_qx[113107]: [D1] Quick update...
Sep 23 03:44:38 threepi01 nutdrv_qx[113107]: [D3] send: Q1
Sep 23 03:44:38 threepi01 nutdrv_qx[113107]: [D5] read [  0]: (8 bytes) => 28 32 34 33 2e 32 20 32
Sep 23 03:44:38 threepi01 nutdrv_qx[113107]: [D5] read [  8]: (8 bytes) => 34 33 2e 32 20 32 33 39
Sep 23 03:44:38 threepi01 nutdrv_qx[113107]: [D5] read [ 16]: (8 bytes) => 2e 38 20 30 31 39 20 35
Sep 23 03:44:38 threepi01 nutdrv_qx[113107]: [D5] read [ 24]: (8 bytes) => 30 2e 30 20 32 2e 32 36
Sep 23 03:44:38 threepi01 nutdrv_qx[113107]: [D5] read [ 32]: (8 bytes) => 20 32 38 2e 38 20 30 30
Sep 23 03:44:39 threepi01 nutdrv_qx[113107]: [D5] read [ 40]: (8 bytes) => 30 30 30 30 30 31 0d 00
Sep 23 03:44:39 threepi01 nutdrv_qx[113107]: [D3] read: (243.2 243.2 239.8 019 50.0 2.26 28.8 00000001
Sep 23 03:44:39 threepi01 nutdrv_qx[113107]: [D5] update_status: OL
Sep 23 03:44:39 threepi01 nutdrv_qx[113107]: [D5] update_status: !LB
Sep 23 03:44:39 threepi01 nutdrv_qx[113107]: [D5] update_status: !CAL
Sep 23 03:44:39 threepi01 nutdrv_qx[113107]: [D5] update_status: !FSD
Sep 23 03:44:39 threepi01 nutdrv_qx[113107]: [D2] send_to_one: sending PONG
Sep 23 03:44:39 threepi01 nutdrv_qx[113107]: [D5] send_to_one: PONG

For reference sake. I 'm providing output with driver blazer_usb I have commented out following options.

#    battery_voltage_reports_one_pack = 1
#    override.battery.packs = 12

upsc abb1kva
battery.charge: 87
battery.runtime: 2090
battery.voltage: 27.12
battery.voltage.high: 26.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.mfr:
device.model: WPHVR1K0
device.type: ups
driver.name: blazer_usb
driver.parameter.bus: 001
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-843-g96723b74c
driver.version.internal: 0.15
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 243.2
input.voltage.fault: 243.1
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 16
ups.mfr:
ups.model: WPHVR1K0
ups.productid: 5161
ups.status: OL
ups.temperature: 29.4
ups.type: online
ups.vendorid: 0665

y0g33 commented 2 years ago

For posterity the first output with driver "nutdrv_qx" with following command is :

systemctl start nut-driver@abb1kva.service  && watch "upsc abb1kva"

battery.charge: 0
battery.packs: 12
battery.voltage: 2.26
battery.voltage.high: 30.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.battery_voltage_reports_one_pack: 1
driver.parameter.bus: 001
driver.parameter.override.battery.packs: 12
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-843-g96723b74c
driver.version.data: Megatec 0.07
driver.version.internal: 0.33
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 239.6
input.voltage.fault: 239.6
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 18
ups.productid: 5161
ups.status: OL
ups.temperature: 29.4
ups.type: online
ups.vendorid: 0665

After 22 seconds:

battery.charge: 0
battery.packs: 12
battery.runtime: 2
battery.voltage: 27.12
battery.voltage.high: 30.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.battery_voltage_reports_one_pack: 1
driver.parameter.bus: 001
driver.parameter.override.battery.packs: 12
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-843-g96723b74c
driver.version.data: Megatec 0.07
driver.version.internal: 0.33
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 239.1
input.voltage.fault: 239.1
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 15
ups.productid: 5161
ups.status: OL
ups.temperature: 29.4
ups.type: online
ups.vendorid: 0665

jimklimov commented 2 years ago

Thanks, lots of magic numbers to mull over! If only I knew these protocols :)

At least, this seems to confirm that neither battery.charge nor battery.runtime are "natively" reported by the device, so whatever numbers appear they are calculated by driver. Strange how battery.voltage only gets multiplied after some time, not from first reading - but this may be why battery charge evaluation ends up zero: (2.26 - 30) in a formula is negative, so rounded to 0. Ideas (explorative hacks) welcome :) Probably to get closer to a 100% charge reported normally, you'd have to set the batt.volt.high to 27.2 or so (e.g. via overrides) if that matches your batteries and device measurements. Maybe makes sense to tune back down the defaults I changed in the PR (to match 13.5-14.0V common charging voltage per 12V battery, not 15V for extreme maintenance ops).

read: (243.1 50.0 239.8 50.0 000.8 016 372.3 388.3 027.2 ---.- 028.8 100000000001

Just guessing, I think "027.2" might be the battery assembly voltage. Wondering what the 372 and 388 are - could be runtimes?.. Hopefully someone gets hold of "PI05" protocol dialect spec to actually support it :\

y0g33 commented 2 years ago

Just a though, why don't we delay the setting of battery.charge after battery.voltage is set . From what you infer, It is being set early on.

Just guessing, I think "027.2" might be the battery assembly voltage. Wondering what the 372 and 388 are - could be runtimes?.. Hopefully someone gets hold of "PI05" protocol dialect spec to actually support it :\

I have no idea where that comes from. I have seen that. I have gone thru the documentation of UPS. I cannot find any reference to this. The panel is kludgy but I will cycle thru it and see if something comes up.

Have a great weekend.

jimklimov commented 2 years ago

Just a thought, why don't we delay the setting of battery.charge after battery.voltage is set . From what you infer, It is being set early on.

Well, I posted references to code I think is complicit (and changes to some of it in the PR)...

From my reading, it would delay those calculations if battery.voltage were not available - but it is (2.27), just for some reason not adjusted yet. Maybe it reads options (override pack count) later in init?..

jimklimov commented 2 years ago

Updated the PR with a twist on that recent idea - to adjust battery.voltage dstate (and batt.volt.act variable) just after we learn that there are several battery packs and voltage reported speaks about only one of them. Such knowledge would be inferred from user settings for the driver, at least for the "only one" part.

y0g33 commented 2 years ago

Wow, it Works !!!. Battery voltage is showing with the right value and so does the calculated "battery charge".

battery.charge: 69
battery.packs: 12
battery.voltage: 27.12
battery.voltage.high: 30.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.battery_voltage_reports_one_pack: 1
driver.parameter.bus: 001
driver.parameter.override.battery.packs: 12
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-844-g31882eb9e
driver.version.data: Megatec 0.07
driver.version.internal: 0.33
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 49.9
input.frequency.nominal: 50
input.voltage: 238.5
input.voltage.fault: 238.5
input.voltage.nominal: 240
output.voltage: 239.8
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 19
ups.productid: 5161
ups.status: OL
ups.temperature: 24.7
ups.type: online
ups.vendorid: 0665

After 22 sec


battery.charge: 69
battery.packs: 12
battery.runtime: 1649
battery.voltage: 27.12
battery.voltage.high: 30.00
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.battery_voltage_reports_one_pack: 1
driver.parameter.bus: 001
driver.parameter.override.battery.packs: 12
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,360,75,1200,50,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-844-g31882eb9e
driver.version.data: Megatec 0.07
driver.version.internal: 0.33
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 238.8
input.voltage.fault: 239.1
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 17
ups.productid: 5161
ups.status: OL
ups.temperature: 24.7
ups.type: online
ups.vendorid: 0665

jimklimov commented 2 years ago

Great! Can you please also check that if you set override.battery.voltage.high to 27.12 (or maybe softer default.battery.voltage.high - so if the driver on some device would yield such value, it would be honoured instead) - if any such setting would place your healthy battery.charge closer to 100%? If that does help, I'd add a message to driver initialization like "XX.XX was defaulted, but if current YY.YY represents the charged battery - set this driver option".

jimklimov commented 2 years ago

I'm also still not sure (after reading code) that runtimecal has any use for numbers beyond first two pairs. Docs seem to imply that it is needed to specify two runtimes at different percent loads as far apart as you can measure (e.g. 240s at 100% and 1380s at 25% in your setting), and based on battery.charge it would do a linear approximation (or since #1027 a more realistic nonlinear one, given enough data/options).

y0g33 commented 2 years ago

Looks like we hit another bug. The value for battery.charge is calculated against default.voltage.high i.e. 30V and the override value never gets picked up. I have modified runtimecal as per your suggestion.

config:

[abb1kva]
    driver = "nutdrv_qx"
    port = "auto"
    vendorid = "0665"
    productid = "5161"
    bus = "001"
    desc = "ABB PowerValue G2 1KVA"
    subdriver=cypress
    runtimecal = 240,100,1380,25
    battery_voltage_reports_one_pack = 1
    override.battery.voltage.high = 27.0
    override.battery.packs = 12

output:

battery.charge: 70
battery.packs: 12
battery.runtime: 1680
battery.voltage: 27.24
battery.voltage.high: 27.0
battery.voltage.low: 20.80
battery.voltage.nominal: 24.0
device.model: WPHVR1K0
device.type: ups
driver.name: nutdrv_qx
driver.parameter.battery_voltage_reports_one_pack: 1
driver.parameter.bus: 001
driver.parameter.override.battery.packs: 12
driver.parameter.override.battery.voltage.high: 27.0
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: 5161
driver.parameter.runtimecal: 240,100,1380,25
driver.parameter.subdriver: cypress
driver.parameter.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: Windows-v2.8.0-alpha3-844-g31882eb9e
driver.version.data: Megatec 0.07
driver.version.internal: 0.33
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 49.9
input.frequency.nominal: 50
input.voltage: 237.4
input.voltage.fault: 237.6
input.voltage.nominal: 240
output.voltage: 239.7
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: 02724.08
ups.load: 16
ups.productid: 5161
ups.status: OL
ups.temperature: 24.5
ups.type: online
ups.vendorid: 0665

networkupstools / nut

override.battery.packs doesn't work to adjust reported battery voltage #1279