Nut upsuser - Jun 2017 - Help with Elite 800VA usb UPS

>
> hmm, apparently the UPS doesn't close the replies to our queries with
> the expected CR and we (I) did not consider that case in nutdrv_qx --
> noted:
> https://github.com/networkupstools/nut/issues/441
>
> But blazer_usb, being less strict on the terminating CR of Q1 replies,
> should work with your device.
>
> > root at artu:~# upsc Elit at artu
> > Init SSL without certificate database
> > Error: Driver not connected
>
> aehm, was the blazer_usb driver running?
>
?This was tested with ?

?nutdrv_qx....

rroot at artu:~# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.2
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
Can't chdir to /var/run/nut: No such file or directory
Driver failed to start (exit status=1)

?but with blazer_usb seems better....

?root at artu:~# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.2
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
Supported UPS detected with megatec protocol
Rating information unavailable
Vendor information unavailable
No values provided for battery high/low voltages in ups.conf

Using 'guestimation' (low: -0.866667, high: -1.083333)!
Battery runtime will not be calculated (runtimecal not set)

but

root at artu:~# upsc Elit at artu
Error: Connection failure: Connection refused

Starting the driver with debug level 5 seems happier, but continue to cycle

root at artu:~# /lib/nut/blazer_usb -a Elit -u nut -DDDDD
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
   0.000000     debug level is '5'
   0.415024     Checking device (1D6B/0001) (006/001)
   0.478033     - VendorID: 1d6b
   0.478074     - ProductID: 0001
   0.478081     - Manufacturer: unknown
   0.478089     - Product: unknown
   0.478096     - Serial Number: unknown
   0.478103     - Bus: 006
   0.478109     Trying to match device
   0.478120     Device does not match - skipping
   0.478193     Checking device (1D6B/0001) (005/001)
   0.541928     - VendorID: 1d6b
   0.542215     - ProductID: 0001
   0.542370     - Manufacturer: unknown
   0.542525     - Product: unknown
   0.542673     - Serial Number: unknown
   0.542818     - Bus: 005
   0.542959     Trying to match device
   0.543981     Device does not match - skipping
   0.544060     Checking device (FFFF/0000) (004/004)
   0.560313     - VendorID: ffff
   0.560574     - ProductID: 0000
   0.560700     - Manufacturer:
   0.560833     - Product: 010937
   0.560958     - Serial Number:
   0.561081     - Bus: 004
   0.561205     Trying to match device
   0.561332     Device matches
   0.793308     send_to_all: SETINFO ups.vendorid "ffff"
   0.793568     send_to_all: SETINFO ups.productid "0000"
   0.793711     send_to_all: SETINFO device.type "ups"
   0.793897     send_to_all: SETINFO driver.version "2.7.2"
   0.794035     send_to_all: SETINFO driver.version.internal "0.11"
   0.794164     send_to_all: SETINFO driver.name "blazer_usb"
   0.794289     Trying megatec protocol...
   0.794402     send: Q1
   1.027417     received 46 (40)
   1.027475     read: (221.8 140.0 220.6 015 50.0 13.8 30.0 00001001
   1.027758     send_to_all: SETINFO input.voltage "221.8"
   1.027796     send_to_all: SETINFO input.voltage.fault "140.0"
   1.027839     send_to_all: SETINFO output.voltage "220.6"
   1.027903     send_to_all: SETINFO ups.load "15"
   1.027944     send_to_all: SETINFO input.frequency "50.0"
   1.027970     send_to_all: SETINFO battery.voltage "13.80"
   1.027990     send_to_all: SETINFO ups.temperature "30.0"
   1.028011     send_to_all: SETINFO ups.beeper.status "enabled"
   1.028031     send_to_all: SETINFO ups.type "offline / line
interactive"
   1.028049     send_to_all: SETINFO ups.status "OL"
   1.028058     Status read in 1 tries
   1.028067     Supported UPS detected with megatec protocol
   1.028077     send: F
   1.150426     received 21 (35)
   1.150482     read: #220.0 000 012.0 50.0
   1.150492     blazer_rating: short reply
   1.150510     Rating read 1 failed
   1.150520     send: F
   1.273356     received 21 (35)
   1.273397     read: #220.0 000 012.0 50.0
   1.273402     blazer_rating: short reply
   1.273407     Rating read 2 failed
   1.273418     send: F
   1.396336     received 21 (35)
   1.396380     read: #220.0 000 012.0 50.0
   1.396386     blazer_rating: short reply
   1.396392     Rating read 3 failed
   1.396403     Rating information unavailable
   1.396411     send: I
   1.591274     received 38 (35)
   1.591622     read: #                           TR00094S
   1.591816     blazer_vendor: short reply
   1.591925     Vendor information read 1 failed
   1.591938     send: I
   1.785267     received 38 (35)
   1.785641     read: #                           TR00094S
   1.785879     blazer_vendor: short reply
   1.786077     Vendor information read 2 failed
   1.786275     send: I
   1.980336     received 38 (35)
   1.980814     read: #                           TR00094S
   1.981136     blazer_vendor: short reply
   1.981417     Vendor information read 3 failed
   1.981633     Vendor information unavailable
   1.981900     No values provided for battery high/low voltages in ups.conf

   1.982186     send_to_all: SETINFO battery.voltage.low "-0.87"
   1.982418     send_to_all: SETINFO battery.voltage.high "-1.08"
   1.982649     Using 'guestimation' (low: -0.866667, high: -1.083333)!
   1.982878     Battery runtime will not be calculated (runtimecal not set)
   1.983106     send_to_all: SETINFO ups.delay.start "180"
   1.983331     send_to_all: SETINFO ups.delay.shutdown "30"
   1.983551     send_to_all: ADDCMD beeper.toggle
   1.983770     send_to_all: ADDCMD load.off
   1.983986     send_to_all: ADDCMD load.on
   1.984207     send_to_all: ADDCMD shutdown.return
   1.984508     send_to_all: ADDCMD shutdown.stayoff
   1.984750     send_to_all: ADDCMD shutdown.stop
   1.984862     send_to_all: ADDCMD test.battery.start
   1.984905     send_to_all: ADDCMD test.battery.start.deep
   1.985040     send_to_all: ADDCMD test.battery.start.quick
   1.985082     send_to_all: ADDCMD test.battery.stop
   1.985121     send: Q1
   2.217282     received 46 (40)
   2.217319     read: (221.8 140.0 220.6 015 50.0 13.8 30.0 00001001
   2.217362     send_to_all: DATAOK
   2.217474     dstate_init: sock /var/run/nut/blazer_usb-Elit open on fd 5
   2.217490     send_to_all: SETINFO driver.parameter.pollinterval "2"
   2.217497     send: Q1
   2.451299     received 46 (40)
   2.451338     read: (223.6 140.0 220.6 016 50.0 13.8 30.0 00001001
   2.451360     send_to_all: SETINFO input.voltage "223.6"
   2.451383     send_to_all: SETINFO ups.load "16"
   4.217877     send: Q1
   4.451260     received 46 (40)
   4.451564     read: (223.6 140.0 222.6 015 49.9 13.8 30.0 00001001
   4.451641     send_to_all: SETINFO output.voltage "222.6"
   4.451691     send_to_all: SETINFO ups.load "15"
   4.451737     send_to_all: SETINFO input.frequency "49.9"
   6.219742     send: Q1
   6.453145     received 46 (40)
   6.453182     read: (223.6 140.0 220.6 015 50.0 13.8 30.0 00001001
   6.453209     send_to_all: SETINFO output.voltage "220.6"
   6.453260     send_to_all: SETINFO input.frequency "50.0"
   8.220697     send: Q1
   8.453059     received 46 (40)
   8.453104     read: (223.6 140.0 220.6 015 49.9 13.8 30.0 00001001
   8.453143     send_to_all: SETINFO input.frequency "49.9"
  10.221828     send: Q1
  10.454997     received 46 (40)
  10.455043     read: (221.8 140.0 220.6 015 50.0 13.9 30.0 00001001
  10.455067     send_to_all: SETINFO input.voltage "221.8"
  10.455131     send_to_all: SETINFO input.frequency "50.0"
  10.455163     send_to_all: SETINFO battery.voltage "13.90"
  12.223764     send: Q1
  12.456907     received 46 (40)
  12.457129     read: (223.6 140.0 222.6 015 50.0 13.8 30.0 00001001
  12.457173     send_to_all: SETINFO input.voltage "223.6"
  12.457206     send_to_all: SETINFO output.voltage "222.6"
  12.457243     send_to_all: SETINFO battery.voltage "13.80"
  14.224891     send: Q1
  14.456862     received 46 (40)
  14.456918     read: (221.8 140.0 220.6 015 50.0 13.9 30.0 00001001
  14.456994     send_to_all: SETINFO input.voltage "221.8"
  14.457050     send_to_all: SETINFO output.voltage "220.6"
  14.457110     send_to_all: SETINFO battery.voltage "13.90"
  16.226737     send: Q1
  16.459791     received 46 (40)
  16.459847     read: (221.8 140.0 220.6 015 49.9 13.9 30.0 00001001
  16.459902     send_to_all: SETINFO input.frequency "49.9"
  18.228598     send: Q1
  18.461662     received 46 (40)
  18.461702     read: (223.6 140.0 220.6 015 49.9 13.8 30.0 00001001
  18.461723     send_to_all: SETINFO input.voltage "223.6"
  18.461850     send_to_all: SETINFO battery.voltage "13.80"
  20.230537     send: Q1
  20.463680     received 46 (40)
  20.463735     read: (221.8 140.0 220.6 015 49.9 13.9 30.0 00001001
  20.463770     send_to_all: SETINFO input.voltage "221.8"
  20.463870     send_to_all: SETINFO battery.voltage "13.90"
  22.232394     send: Q1
  22.464495     received 46 (40)
  22.464530     read: (227.0 140.0 226.5 015 50.0 13.9 30.0 00001001
  22.464547     send_to_all: SETINFO input.voltage "227.0"
  22.464564     send_to_all: SETINFO output.voltage "226.5"
  22.464574     send_to_all: SETINFO input.frequency "50.0"
  24.232629     send: Q1
  24.466477     received 46 (40)
  24.466536     read: (221.8 140.0 220.6 015 49.9 13.9 30.0 00001001
  24.466572     send_to_all: SETINFO input.voltage "221.8"
  24.466653     send_to_all: SETINFO output.voltage "220.6"
  24.466707     send_to_all: SETINFO input.frequency "49.9"
  26.234547     send: Q1
  26.467332     received 46 (40)
  26.467541     read: (221.8 140.0 220.6 015 50.0 13.8 30.0 00001001
  26.467588     send_to_all: SETINFO input.frequency "50.0"
  26.467615     send_to_all: SETINFO battery.voltage "13.80"
  28.236383     send: Q1
  28.469320     received 46 (40)
  28.469377     read: (223.6 140.0 220.6 015 50.0 13.8 30.0 00001001
  28.469420     send_to_all: SETINFO input.voltage "223.6"
  30.238212     send: Q1
  30.471209     received 46 (40)
  30.471245     read: (221.8 140.0 220.6 015 49.9 13.9 30.0 00001001
  30.471262     send_to_all: SETINFO input.voltage "221.8"
  30.471278     send_to_all: SETINFO input.frequency "49.9"
  30.471301     send_to_all: SETINFO battery.voltage "13.90"
  32.240077     send: Q1
  32.473109     received 46 (40)
  32.473145     read: (221.8 140.0 220.6 015 50.0 13.9 30.0 00001001
  32.473172     send_to_all: SETINFO input.frequency "50.0"
  34.241808     send: Q1
  34.475070     received 46 (40)
  34.475115     read: (220.1 140.0 218.6 014 49.9 13.9 30.0 00001001
  34.475139     send_to_all: SETINFO input.voltage "220.1"
  34.475191     send_to_all: SETINFO output.voltage "218.6"
  34.475223     send_to_all: SETINFO ups.load "14"
  34.475254     send_to_all: SETINFO input.frequency "49.9"
  36.243749     send: Q1
  36.476959     received 46 (40)
  36.477283     read: (221.8 140.0 220.6 014 50.0 13.8 30.0 00001001
  36.477358     send_to_all: SETINFO input.voltage "221.8"
  36.477419     send_to_all: SETINFO output.voltage "220.6"
  36.477482     send_to_all: SETINFO input.frequency "50.0"
  36.477542     send_to_all: SETINFO battery.voltage "13.80"
  38.245683     send: Q1
  38.478868     received 46 (40)
  38.478954     read: (221.8 140.0 220.6 015 50.0 13.8 30.0 00001001
  38.478997     send_to_all: SETINFO ups.load "15"
  40.247557     send: Q1
  40.479832     received 46 (40)
  40.479891     read: (221.8 140.0 220.6 015 49.9 13.8 30.0 00001001
  40.479955     send_to_all: SETINFO input.frequency "49.9"
  42.249436     send: Q1
  42.482780     received 46 (40)
  42.482838     read: (220.1 140.0 218.6 015 50.0 13.8 30.0 00001001
  42.482873     send_to_all: SETINFO input.voltage "220.1"
  42.482905     send_to_all: SETINFO output.voltage "218.6"
  42.482934     send_to_all: SETINFO input.frequency "50.0"

Thank you again,
A.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170610/b5bad75a/attachment-0001.html>

> Starting the driver with debug level 5 seems happier, but continue to cycle
It is meant to 'cycle', it's working correctly.
When you run the driver normally (i.e. not in debug mode), you don't
see all that output (plus, after having established a connection with
the device, the driver goes into the background), but it's doing
exactly the same thing.
> nutdrv_qx....
>
> rroot at artu:~# upsdrvctl start
> Network UPS Tools - UPS driver controller 2.7.2
> Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
> Can't chdir to /var/run/nut: No such file or directory
> Driver failed to start (exit status=1)
>
> but with blazer_usb seems better....
>
> root at artu:~# upsdrvctl start
> Network UPS Tools - UPS driver controller 2.7.2
> Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
> Supported UPS detected with megatec protocol
> Rating information unavailable
> Vendor information unavailable
> No values provided for battery high/low voltages in ups.conf
>
> Using 'guestimation' (low: -0.866667, high: -1.083333)!
> Battery runtime will not be calculated (runtimecal not set)
>
> but
>
> root at artu:~# upsc Elit at artu
> Error: Connection failure: Connection refused
Also, remember that, if you launch upsd and then you change the
content of ups.conf (for example, changing the driver of your UPS from
'nutdrv_qx' to 'blazer_usb'), you need to reload its
configuration
(upsd -c reload) or restart it (mandatory, if it's running in debug
mode).

So, let's try this:
1. stop all NUT-related services,
2. make sure to have the right things in your ups.conf (i.e. your UPS
configured for driver 'blazer_usb'),
3. launch upsd,
4. launch the driver,
5. now check the values with upsc: what happens?

So....seems so better...

Each time I rebbot, I miss the /var/run/nut folder...

root at artu:~# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.2
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
Can't chdir to /var/run/nut: No such file or directory
Driver failed to start (exit status=1)

root at artu:~# upsd
Network UPS Tools upsd 2.7.2
fopen /var/run/nut/upsd.pid: No such file or directory
listening on 192.168.1.1 port 3493
listening on 127.0.0.1 port 3493
Can't chdir to /var/run/nut: No such file or directory

Once manually created ad giving permission to nut group, I can start the
driver and the daemon:

root at artu:~# upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.2
Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
Supported UPS detected with megatec protocol
Rating information unavailable
Vendor information unavailable
No values provided for battery high/low voltages in ups.conf

Using 'guestimation' (low: -0.866667, high: -1

root at artu:~# upsd -c reload
Network UPS Tools upsd 2.7.2
.083333)!
Battery runtime will not be calculated (runtimecal not set)


root at artu:~# upsc Elit at artu
Init SSL without certificate database
battery.voltage: 13.90
battery.voltage.high: -1.08
battery.voltage.low: -0.87
device.type: ups
driver.name: blazer_usb
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.7.2
driver.version.internal: 0.11
input.frequency: 50.0
input.voltage: 228.7
input.voltage.fault: 140.0
output.voltage: 226.5
ups.beeper.status: enabled
ups.delay.shutdown: 30
ups.delay.start: 180
ups.load: 16
ups.productid: 0000
ups.status: OL
ups.temperature: 30.0
ups.type: offline / line interactive
ups.vendorid: ffff

What's the right procedure for loading driver/daemon at boot?
I have read a lot about /var/run/nut missing, but haven't find any
solution....

I have also successfully tested the battery...

 upscmd -uadmin -pups Elit at artu test.battery.start.quick

Thank you lots,
Andrea


2017-06-11 5:31 GMT+02:00 Daniele Pezzini <hyouko at gmail.com>:
> > Starting the driver with debug level 5 seems happier, but continue to
> cycle
>
> It is meant to 'cycle', it's working correctly.
> When you run the driver normally (i.e. not in debug mode), you don't
> see all that output (plus, after having established a connection with
> the device, the driver goes into the background), but it's doing
> exactly the same thing.
>
> > nutdrv_qx....
> >
> > rroot at artu:~# upsdrvctl start
> > Network UPS Tools - UPS driver controller 2.7.2
> > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
> > Can't chdir to /var/run/nut: No such file or directory
> > Driver failed to start (exit status=1)
> >
> > but with blazer_usb seems better....
> >
> > root at artu:~# upsdrvctl start
> > Network UPS Tools - UPS driver controller 2.7.2
> > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
> > Supported UPS detected with megatec protocol
> > Rating information unavailable
> > Vendor information unavailable
> > No values provided for battery high/low voltages in ups.conf
> >
> > Using 'guestimation' (low: -0.866667, high: -1.083333)!
> > Battery runtime will not be calculated (runtimecal not set)
> >
> > but
> >
> > root at artu:~# upsc Elit at artu
> > Error: Connection failure: Connection refused
>
> Also, remember that, if you launch upsd and then you change the
> content of ups.conf (for example, changing the driver of your UPS from
> 'nutdrv_qx' to 'blazer_usb'), you need to reload its
configuration
> (upsd -c reload) or restart it (mandatory, if it's running in debug
> mode).
>
> So, let's try this:
> 1. stop all NUT-related services,
> 2. make sure to have the right things in your ups.conf (i.e. your UPS
> configured for driver 'blazer_usb'),
> 3. launch upsd,
> 4. launch the driver,
> 5. now check the values with upsc: what happens?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170611/4b755dbb/attachment.html>