thr3ads.net - Nut upsuser - [Nut-upsuser] ABB UPS Powervalue 11RTG2 : blazer_usb: works /nutdrv

If this information is useful, please help other people find it:
Share via:

Yogesh Bhanu

2022-Jul-01 09:09 UTC

[Nut-upsuser] ABB UPS Powervalue 11RTG2 : blazer_usb: works /nutdrv_qx: iffy

Hi,

I just installed an ABB UPS Powervalue 11RT G2 1KVA. I'm using NUT version
2.8.0 on a RPI3 running ArchLinux.
# config
--snip--
[abb1kva]
    driver = "nutdrv_qx"
    port = "auto"
    vendorid = "0665"
    productid = "5161"
    bus = "001"
    desc = "ABB PowerValue G2 1KVA"
    runtimecal = 240,100,360,75,1200,50,1380,25
--snip--

I get the following output :

--snip--
[root at threepi01 nut]# upsdrvctl -u nut   -DDD start
Network UPS Tools - UPS driver controller 2.8.0
   0.000000 [D2]
If you're not a NUT core developer, chances are that you're told to
enable
debugging
to see why a driver isn't working for you. We're sorry for the
confusion,
but this is
the 'upsdrvctl' wrapper, not the driver you're interested in.

Below you'll find one or more lines starting with 'exec:' followed
by an
absolute
path to the driver binary and some command line option. This is what the
driver
starts and you need to copy and paste that line and append the debug flags
to that
line (less the 'exec:' prefix).

Alternately, provide an additional '-d' (lower-case) parameter to
'upsdrvctl' to
pass its current debug level to the launched driver.

   0.000602 [D1] Starting UPS: abb1kva
   0.000774 [D2] 3 remaining attempts
   0.000820 [D2] exec:  /usr/lib/nut/nutdrv_qx -a abb1kva -u nut
Network UPS Tools - Generic Q* USB/Serial driver 0.32 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Protocol [PI05] is not supported by this driver
Protocol [PI05] is not supported by this driver
Protocol [PI05] is not supported by this driver
Protocol [PI05] is not supported by this driver
Protocol [PI05] is not supported by this driver
Protocol [PI05] is not supported by this driver
Using protocol: Megatec 0.06
No values for battery high/low voltages
Using 'guesstimation' (low: 20.800000, high: 26.000000)!
No charge time specified, using built in default [43200 seconds]
No idle load specified, using built in default [10.0 %]

[root at threepi01 nut]# upsc abb1kva
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.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.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: 2.8.0
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: 236.3
input.voltage.fault: 236.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: 20
ups.productid: 5161
ups.status: OL
ups.temperature: 20.1
ups.type: online
ups.vendorid: 0665
--snip--




But with the blazer_usb.
# config:

--snip--
[abb1kva]
    driver = "blazer_usb"
    port = "auto"
    vendorid = "0665"
    productid = "5161"
    bus = "001"
    desc = "ABB PowerValue G2 1KVA"
    runtimecal = 240,100,360,75,1200,50,1380,25
--snip--

I get the following output:

--snip--
[root at threepi01 nut]# upsdrvctl -u nut   -DDD start
Network UPS Tools - UPS driver controller 2.8.0
   0.000000 [D2]
If you're not a NUT core developer, chances are that you're told to
enable
debugging
to see why a driver isn't working for you. We're sorry for the
confusion,
but this is
the 'upsdrvctl' wrapper, not the driver you're interested in.

Below you'll find one or more lines starting with 'exec:' followed
by an
absolute
path to the driver binary and some command line option. This is what the
driver
starts and you need to copy and paste that line and append the debug flags
to that
line (less the 'exec:' prefix).

Alternately, provide an additional '-d' (lower-case) parameter to
'upsdrvctl' to
pass its current debug level to the launched driver.

   0.000573 [D1] Starting UPS: abb1kva
   0.000621 [D2] 3 remaining attempts
   0.000655 [D2] exec:  /usr/lib/nut/blazer_usb -a abb1kva -u nut
Network UPS Tools - Megatec/Q1 protocol USB driver 0.14 (2.8.0)
Please note that this driver is deprecated and will not receive
new development. If it works for managing your devices - fine,
but if you are running it to try setting up a new device, please
consider the newer nutdrv_qx instead, which should handle all 'Qx'
protocol variants for NUT. (Please also report if your device works
with this driver, but nutdrv_qx would not actually support it with
any subdriver!)

Supported UPS detected with megatec protocol
Vendor information read in 1 tries
No values provided for battery high/low voltages in ups.conf

Using 'guestimation' (low: 20.800000, high: 26.000000)!
No charge time specified, using built in default [43200 seconds]
No idle load specified, using built in default [10.0 %]

[root at threepi01 nut]# upsc abb1kva
battery.charge: 93
battery.runtime: 2237
battery.voltage: 27.24
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.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: 2.8.0
driver.version.internal: 0.14
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.current.nominal: 4.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 237.7
input.voltage.fault: 237.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: 18
ups.mfr:
ups.model: WPHVR1K0
ups.productid: 5161
ups.status: OL
ups.temperature: 20.1
ups.type: online
ups.vendorid: 0665
--snip--
Q: How can I get the new driver to display the correct outputs for ?
--snip--
battery.charge: 0
battery.voltage: 2.28
--snip--

Q: is it possible to fix the battery Voltage values as the reported voltage
"battery.voltage: 27.24":
is correct ( confirmed on the panel)

battery.voltage.high: 26.00
battery.voltage.low: 20.80

Q:  Do I have to upload a DDL to get the following output sorted.

From:
--snip--
ups.mfr:
ups.model: WPHVR1K0
--snip--

To:
--snip--
ups.mfr: ABB
ups.model:  Powervalue 11RT G2 1kva
--snip--

Q. What does "input.voltage.fault" mean ?

Thanks in advance,

Yogesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220701/3f995894/attachment.htm>

Yogesh Bhanu

2022-Aug-11 04:33 UTC

head link

[Nut-upsuser] ABB UPS Powervalue 11RTG2 : blazer_usb: works /nutdrv_qx: iffy

Hi,

an update w.r.t NUT support for " ABB UPS Powervalue 11RT G2".

I can confirm it works with the configuration listed below when using the
driver "nutdrv_qx".
With the caveat that "battery.voltage" is under reported.
Sometimes it helps to RTFM.
--snip--
*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.
--snip--

+ Working Config:
--snip--
[abb1kva]
    driver = "nutdrv_qx"
    port = "auto"
    vendorid = "0665"
    productid = "5161"
    bus = "001"
    desc = "ABB PowerValue G2 1KVA"
    # runtimecal from ABB UPS documentation
    runtimecal = 240,100,360,75,1200,50,1380,25
    override.battery.packs = 12
--snip--

+ Output:
--snip--
[root at threepi01 ~]# upsc abb1kva
battery.charge: 100
battery.packs: 12
battery.runtime: 2400
battery.voltage: 2.28 <== under reported
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.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.synchronous: auto
driver.parameter.vendorid: 0665
driver.version: 2.8.0
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: 237.9
input.voltage.fault: 238.1
input.voltage.nominal: 240
output.voltage: 237.9
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: 20.7
ups.type: online
ups.vendorid: 0665
--snip--

Q. Is it possible to fix the battery.voltage output ?

Q. What is the proper way to get the model and vendor recognized ?

Kind Regards,

Yogesh

On Fri, Jul 1, 2022 at 11:09 AM Yogesh Bhanu <yogesh.bhanu at gmail.com>
wrote:
> Hi,
>
> I just installed an ABB UPS Powervalue 11RT G2 1KVA. I'm using NUT
version
> 2.8.0 on a RPI3 running ArchLinux.
> # config
> --snip--
> [abb1kva]
>     driver = "nutdrv_qx"
>     port = "auto"
>     vendorid = "0665"
>     productid = "5161"
>     bus = "001"
>     desc = "ABB PowerValue G2 1KVA"
>     runtimecal = 240,100,360,75,1200,50,1380,25
> --snip--
>
> I get the following output :
>
> --snip--
> [root at threepi01 nut]# upsdrvctl -u nut   -DDD start
> Network UPS Tools - UPS driver controller 2.8.0
>    0.000000 [D2]
> If you're not a NUT core developer, chances are that you're told to
enable
> debugging
> to see why a driver isn't working for you. We're sorry for the
confusion,
> but this is
> the 'upsdrvctl' wrapper, not the driver you're interested in.
>
> Below you'll find one or more lines starting with 'exec:'
followed by an
> absolute
> path to the driver binary and some command line option. This is what the
> driver
> starts and you need to copy and paste that line and append the debug flags
> to that
> line (less the 'exec:' prefix).
>
> Alternately, provide an additional '-d' (lower-case) parameter to
> 'upsdrvctl' to
> pass its current debug level to the launched driver.
>
>    0.000602 [D1] Starting UPS: abb1kva
>    0.000774 [D2] 3 remaining attempts
>    0.000820 [D2] exec:  /usr/lib/nut/nutdrv_qx -a abb1kva -u nut
> Network UPS Tools - Generic Q* USB/Serial driver 0.32 (2.8.0)
> USB communication driver (libusb 1.0) 0.43
> Protocol [PI05] is not supported by this driver
> Protocol [PI05] is not supported by this driver
> Protocol [PI05] is not supported by this driver
> Protocol [PI05] is not supported by this driver
> Protocol [PI05] is not supported by this driver
> Protocol [PI05] is not supported by this driver
> Using protocol: Megatec 0.06
> No values for battery high/low voltages
> Using 'guesstimation' (low: 20.800000, high: 26.000000)!
> No charge time specified, using built in default [43200 seconds]
> No idle load specified, using built in default [10.0 %]
>
> [root at threepi01 nut]# upsc abb1kva
> 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.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.synchronous: auto
> driver.parameter.vendorid: 0665
> driver.version: 2.8.0
> 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: 236.3
> input.voltage.fault: 236.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: 20
> ups.productid: 5161
> ups.status: OL
> ups.temperature: 20.1
> ups.type: online
> ups.vendorid: 0665
> --snip--
>
>
>
>
> But with the blazer_usb.
> # config:
>
> --snip--
> [abb1kva]
>     driver = "blazer_usb"
>     port = "auto"
>     vendorid = "0665"
>     productid = "5161"
>     bus = "001"
>     desc = "ABB PowerValue G2 1KVA"
>     runtimecal = 240,100,360,75,1200,50,1380,25
> --snip--
>
> I get the following output:
>
> --snip--
> [root at threepi01 nut]# upsdrvctl -u nut   -DDD start
> Network UPS Tools - UPS driver controller 2.8.0
>    0.000000 [D2]
> If you're not a NUT core developer, chances are that you're told to
enable
> debugging
> to see why a driver isn't working for you. We're sorry for the
confusion,
> but this is
> the 'upsdrvctl' wrapper, not the driver you're interested in.
>
> Below you'll find one or more lines starting with 'exec:'
followed by an
> absolute
> path to the driver binary and some command line option. This is what the
> driver
> starts and you need to copy and paste that line and append the debug flags
> to that
> line (less the 'exec:' prefix).
>
> Alternately, provide an additional '-d' (lower-case) parameter to
> 'upsdrvctl' to
> pass its current debug level to the launched driver.
>
>    0.000573 [D1] Starting UPS: abb1kva
>    0.000621 [D2] 3 remaining attempts
>    0.000655 [D2] exec:  /usr/lib/nut/blazer_usb -a abb1kva -u nut
> Network UPS Tools - Megatec/Q1 protocol USB driver 0.14 (2.8.0)
> Please note that this driver is deprecated and will not receive
> new development. If it works for managing your devices - fine,
> but if you are running it to try setting up a new device, please
> consider the newer nutdrv_qx instead, which should handle all 'Qx'
> protocol variants for NUT. (Please also report if your device works
> with this driver, but nutdrv_qx would not actually support it with
> any subdriver!)
>
> Supported UPS detected with megatec protocol
> Vendor information read in 1 tries
> No values provided for battery high/low voltages in ups.conf
>
> Using 'guestimation' (low: 20.800000, high: 26.000000)!
> No charge time specified, using built in default [43200 seconds]
> No idle load specified, using built in default [10.0 %]
>
> [root at threepi01 nut]# upsc abb1kva
> battery.charge: 93
> battery.runtime: 2237
> battery.voltage: 27.24
> 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.synchronous: auto
> driver.parameter.vendorid: 0665
> driver.version: 2.8.0
> driver.version.internal: 0.14
> driver.version.usb: libusb-1.0.26 (API: 0x1000109)
> input.current.nominal: 4.0
> input.frequency: 50.0
> input.frequency.nominal: 50
> input.voltage: 237.7
> input.voltage.fault: 237.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: 18
> ups.mfr:
> ups.model: WPHVR1K0
> ups.productid: 5161
> ups.status: OL
> ups.temperature: 20.1
> ups.type: online
> ups.vendorid: 0665
> --snip--
> Q: How can I get the new driver to display the correct outputs for ?
> --snip--
> battery.charge: 0
> battery.voltage: 2.28
> --snip--
>
> Q: is it possible to fix the battery Voltage values as the reported
> voltage "battery.voltage: 27.24":
> is correct ( confirmed on the panel)
>
> battery.voltage.high: 26.00
> battery.voltage.low: 20.80
>
> Q:  Do I have to upload a DDL to get the following output sorted.
>
> From:
> --snip--
> ups.mfr:
> ups.model: WPHVR1K0
> --snip--
>
> To:
> --snip--
> ups.mfr: ABB
> ups.model:  Powervalue 11RT G2 1kva
> --snip--
>
> Q. What does "input.voltage.fault" mean ?
>
> Thanks in advance,
>
> Yogesh
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220811/b0cc47c4/attachment-0001.htm>

Nut upsuser - Jul 2022 - ABB UPS Powervalue 11RTG2 : blazer_usb: works /nutdrv_qx: iffy

[Nut-upsuser] ABB UPS Powervalue 11RTG2 : blazer_usb: works /nutdrv_qx: iffy

[Nut-upsuser] ABB UPS Powervalue 11RTG2 : blazer_usb: works /nutdrv_qx: iffy