thr3ads.net - Nut upsuser - [Nut-upsuser] Zigor Ebro 650 compatibility - revisited (on Windows, at least) [Sep 2013]

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

Martyn Hill

2013-Sep-16 21:49 UTC

[Nut-upsuser] Zigor Ebro 650 compatibility - revisited (on Windows, at least)

Hi Arnaud and NUT team

You may recall some time ago, I and a few others posted questions about 
the above referenced (cheap and cheerful) USB-based UPS - specifically 
regarding FreeBSD USB support in NUT. The original posting was entitled 
"Zigor Ebro 650 compatibility".

I've since tried the latest Windows port of NUT with my WinXP laptop 
connected to the Zigor Ebro and finally gotten somewhere!

NUT and Blazer version: Network UPS Tools - Megatec/Q1 protocol USB 
driver 0.09 (2.6.5-3780M)

This at least proves that my previously moody Zigor device _can_ 
communicate nicely with NUT - and one step closer to getting it to work 
in FreeBSD (with its fancy USB stack...) - which is my ultimate aim.

I attach the output from running the blazer_usb.exe command in debug 
mode, with a very similar ups.conf that I had been using on FreeBSD, thus:

[zigor_ebro_blazer]
     driver = blazer_usb
     port = auto
     desc = "Zigor Ebro 650 USB UPS"
     subdriver = krauler
     protocol = megatec
     langid_fix = 0x409
     vendorid = 0001
     productid = 0000
     bus = bus-0            # This was different for FreeBSD, naturally.

Aside from the occasional "blazer_status: short reply ... Communications 
with UPS lost: status read failed!" messages (from which it appears to 
recover perfectly well), plus the odd corrupted reply from the device - 
e.g. "read: #Ff.0 2.0 12.00 50.0... blazer_rating: non numerical 
value [Ff.0]", the output seems quite promising!

Any ideas where I go from here - firstly to iron-out those buggy 
responses from the device and secondly (and where we left it 
previously), how to get FreeBSD to 'talk' libusb-0.1 or else allow 
FreeBSD (8.2) and NUT to work with this USB device?

Thanks in advance for any guidance in troubleshooting this (possibly not 
very common) configuration.
Martyn
London.

-- 
"There are 10 types of people in this world. Those who understand binary
and those who don't."

-------------- next part --------------
Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 (2.6.5-3780M)

   0.000000	send_to_all: SETINFO driver.parameter.port "auto"
   0.000000	send_to_all: SETINFO driver.parameter.subdriver "krauler"
   0.000000	send_to_all: SETINFO driver.parameter.protocol "megatec"
   0.000000	send_to_all: SETINFO driver.parameter.langid_fix "0x409"
   0.000000	send_to_all: SETINFO driver.parameter.vendorid "0001"
   0.000000	send_to_all: SETINFO driver.parameter.productid "0000"
   0.000000	send_to_all: SETINFO driver.parameter.bus "bus-0"
   0.000000	debug level is '6'
   0.000000	language ID workaround enabled (using '0x409')
   0.000000	Checking device (0001/0000) (bus-0/\\.\libusb0-0001--0x0001-0x0000)
   0.015625	- VendorID: 0001
   0.015625	- ProductID: 0000
   0.015625	- Manufacturer: unknown
   0.015625	- Product: unknown
   0.015625	- Serial Number: unknown
   0.015625	- Bus: bus-0
   0.015625	Trying to match device
   0.015625	Device matches
   0.031250	send_to_all: SETINFO ups.vendorid "0001"
   0.031250	send_to_all: SETINFO ups.productid "0000"
   0.031250	send_to_all: SETINFO device.type "ups"
   0.031250	send_to_all: SETINFO driver.version "2.6.5-3780M"
   0.031250	send_to_all: SETINFO driver.version.internal "0.09"
   0.031250	send_to_all: SETINFO driver.name "blazer_usb"
   0.031250	Trying megatec protocol...
   0.031250	send: Q1
   0.312500	received 96 (96)
   0.312500	read: (231.0 165.0 231.0 024 50.0 13.6 00.0 00001000
   0.312500	send_to_all: SETINFO input.voltage "231.0"
   0.312500	send_to_all: SETINFO input.voltage.fault "165.0"
   0.312500	send_to_all: SETINFO output.voltage "231.0"
   0.312500	send_to_all: SETINFO ups.load "24"
   0.312500	send_to_all: SETINFO input.frequency "50.0"
   0.312500	send_to_all: SETINFO battery.voltage "13.60"
   0.312500	send_to_all: SETINFO ups.temperature "0.0"
   0.312500	send_to_all: SETINFO ups.beeper.status "disabled"
   0.312500	send_to_all: SETINFO ups.type "offline / line interactive"
   0.312500	send_to_all: SETINFO ups.status "OL"
   0.312500	Status read in 1 tries
   0.312500	Supported UPS detected with megatec protocol
   0.312500	send: F
   0.421875	received 46 (46)
   0.421875	read: #Ff.0 2.0 12.00 50.0
   0.421875	blazer_rating: non numerical value [Ff.0]
   0.421875	send_to_all: SETINFO input.current.nominal "2.0"
   0.421875	send_to_all: SETINFO battery.voltage.nominal "12.0"
   0.421875	send_to_all: SETINFO input.frequency.nominal "50"
   0.421875	Ratings read in 1 tries
   0.421875	send: I
   0.625000	received 80 (80)
   0.625000	read: #ZIGOR           EBRO 650   VER 1.1   
   0.625000	send_to_all: SETINFO ups.mfr "ZIGOR"
   0.625000	send_to_all: SETINFO ups.model "EBRO 650"
   0.625000	send_to_all: SETINFO ups.firmware "VER 1.1"
   0.625000	Vendor information read in 1 tries
   0.625000	No values provided for battery high/low voltages in ups.conf

   0.625000	send_to_all: SETINFO battery.voltage.low "10.40"
   0.625000	send_to_all: SETINFO battery.voltage.high "13.00"
   0.625000	Using 'guestimation' (low: 10.400000, high: 13.000000)!
   0.625000	Battery runtime will not be calculated (runtimecal not set)
   0.625000	send_to_all: SETINFO ups.delay.start "180"
   0.625000	send_to_all: SETINFO ups.delay.shutdown "30"
   0.625000	send_to_all: ADDCMD beeper.toggle
   0.625000	send_to_all: ADDCMD load.off
   0.625000	send_to_all: ADDCMD load.on
   0.625000	send_to_all: ADDCMD shutdown.return
   0.625000	send_to_all: ADDCMD shutdown.stayoff
   0.625000	send_to_all: ADDCMD shutdown.stop
   0.625000	send_to_all: ADDCMD test.battery.start
   0.625000	send_to_all: ADDCMD test.battery.start.deep
   0.625000	send_to_all: ADDCMD test.battery.start.quick
   0.625000	send_to_all: ADDCMD test.battery.stop
   0.625000	send: Q1
   0.906250	received 96 (96)
   0.906250	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
   0.906250	send_to_all: SETINFO input.voltage "233.0"
   0.906250	send_to_all: SETINFO output.voltage "233.0"
   0.906250	send_to_all: SETINFO battery.charge "100"
   0.906250	send_to_all: DATAOK
   0.906250	dstate_init: sock \\.\pipe\blazer_usb-zigor_ebro_blazer open on fd
1960
   0.906250	send_to_all: SETINFO driver.parameter.pollinterval "2"
   0.906250	send_to_all: SETINFO device.mfr "ZIGOR"
   0.906250	send_to_all: SETINFO device.model "EBRO 650"
   0.906250	send: Q1
   1.187500	received 96 (96)
   1.187500	read: (233.0 165.0 233.0 024 50.2 13.6 00.0 00001000
   1.187500	send_to_all: SETINFO input.frequency "50.2"
   2.906250	send: Q1
   3.187500	received 96 (96)
   3.187500	read: (234.0 165.0 234.0 023 50.0 13.6 00.0 00001000
   3.187500	send_to_all: SETINFO input.voltage "234.0"
   3.187500	send_to_all: SETINFO output.voltage "234.0"
   3.187500	send_to_all: SETINFO ups.load "23"
   3.187500	send_to_all: SETINFO input.frequency "50.0"
   4.906250	send: Q1
   5.187500	received 96 (96)
   5.187500	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
   5.187500	send_to_all: SETINFO input.voltage "233.0"
   5.187500	send_to_all: SETINFO output.voltage "233.0"
   5.187500	send_to_all: SETINFO ups.load "24"
   6.906250	send: Q1
   7.187500	received 96 (96)
   7.187500	read: (234.0 165.0 234.0 024 50.2 13.6 00.0 00001000
   7.187500	send_to_all: SETINFO input.voltage "234.0"
   7.187500	send_to_all: SETINFO output.voltage "234.0"
   7.187500	send_to_all: SETINFO input.frequency "50.2"
   8.906250	send: Q1
   9.187500	received 96 (96)
   9.187500	read: (234.0 165.0 234.0 024 50.0 13.6 00.0 00001000
   9.187500	send_to_all: SETINFO input.frequency "50.0"
  10.906250	send: Q1
  11.187500	received 96 (96)
  11.187500	read: (231.0 165.0 231.0 024 50.0 13.6 00.0 00001000
  11.187500	send_to_all: SETINFO input.voltage "231.0"
  11.187500	send_to_all: SETINFO output.voltage "231.0"
  12.906250	send: Q1
  13.203125	received 96 (96)
  13.203125	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
  13.203125	send_to_all: SETINFO input.voltage "233.0"
  13.203125	send_to_all: SETINFO output.voltage "233.0"
  14.906250	send: Q1
  15.156250	received 96 (96)
  15.156250	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
  16.906250	send: Q1
  17.156250	received 96 (96)
  17.156250	read: (231.0 165.0 231.0 024 50.2 13.6 00.0 00001000
  17.156250	send_to_all: SETINFO input.voltage "231.0"
  17.156250	send_to_all: SETINFO output.voltage "231.0"
  17.156250	send_to_all: SETINFO input.frequency "50.2"
  18.906250	send: Q1
  19.156250	received 96 (96)
  19.156250	read: (236.0 165.0 236.0 024 50.0 13.6 00.0 00001000
  19.156250	send_to_all: SETINFO input.voltage "236.0"
  19.156250	send_to_all: SETINFO output.voltage "236.0"
  19.156250	send_to_all: SETINFO input.frequency "50.0"
  20.906250	send: Q1
  21.156250	received 96 (96)
  21.156250	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
  21.156250	send_to_all: SETINFO input.voltage "233.0"
  21.156250	send_to_all: SETINFO output.voltage "233.0"
  22.906250	send: Q1
  23.156250	received 96 (96)
  23.156250	read: (234.0 165.0 234.0 031 50.0 13.6 00.0 00001000
  23.156250	send_to_all: SETINFO input.voltage "234.0"
  23.156250	send_to_all: SETINFO output.voltage "234.0"
  23.156250	send_to_all: SETINFO ups.load "31"
  24.906250	send: Q1
  25.156250	received 96 (96)
  25.156250	read: (234.0 165.0 234.0 024 50.2 13.6 00.0 00001000
  25.156250	send_to_all: SETINFO ups.load "24"
  25.156250	send_to_all: SETINFO input.frequency "50.2"
  26.906250	send: Q1
  27.171875	received 96 (96)
  27.171875	read: (231.0 165.0 231.0 023 50.2 13.6 00.0 00001000
  27.171875	send_to_all: SETINFO input.voltage "231.0"
  27.171875	send_to_all: SETINFO output.voltage "231.0"
  27.171875	send_to_all: SETINFO ups.load "23"
  28.906250	send: Q1
  29.171875	received 96 (96)
  29.171875	read: (234.0 165.0 234.0 024 50.0 13.6 00.0 00001000
  29.171875	send_to_all: SETINFO input.voltage "234.0"
  29.171875	send_to_all: SETINFO output.voltage "234.0"
  29.171875	send_to_all: SETINFO ups.load "24"
  29.171875	send_to_all: SETINFO input.frequency "50.0"
  30.906250	send: Q1
  31.171875	received 96 (96)
  31.171875	read: (231.0 165.0 231.0 024 50.0 13.6 00.0 00001000
  31.171875	send_to_all: SETINFO input.voltage "231.0"
  31.171875	send_to_all: SETINFO output.voltage "231.0"
  32.906250	send: Q1
  32.906250	read: timeout
  32.906250	blazer_status: short reply
  32.906250	Communications with UPS lost: status read failed!
  34.906250	send: Q1
  35.171875	received 96 (96)
  35.171875	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
  35.171875	send_to_all: SETINFO input.voltage "233.0"
  35.171875	send_to_all: SETINFO output.voltage "233.0"
  36.906250	send: Q1
  37.171875	received 96 (96)
  37.171875	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
  38.906250	send: Q1
  39.171875	received 96 (96)
  39.171875	read: (234.0 165.0 234.0 024 50.2 13.6 00.0 00001000
  39.171875	send_to_all: SETINFO input.voltage "234.0"
  39.171875	send_to_all: SETINFO output.voltage "234.0"
  39.171875	send_to_all: SETINFO input.frequency "50.2"
  40.906250	send: Q1
  41.171875	received 96 (96)
  41.171875	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
  41.171875	send_to_all: SETINFO input.voltage "233.0"
  41.171875	send_to_all: SETINFO output.voltage "233.0"
  41.171875	send_to_all: SETINFO input.frequency "50.0"
  42.906250	send: Q1
  43.171875	received 96 (96)
  43.171875	read: (234.0 165.0 234.0 024 50.0 13.6 00.0 00001000
  43.171875	send_to_all: SETINFO input.voltage "234.0"
  43.171875	send_to_all: SETINFO output.voltage "234.0"
  44.906250	send: Q1
  45.171875	received 96 (96)
  45.171875	read: (231.0 165.0 231.0 024 50.0 13.6 00.0 00001000
  45.171875	send_to_all: SETINFO input.voltage "231.0"
  45.171875	send_to_all: SETINFO output.voltage "231.0"
  46.906250	send: Q1
  47.171875	received 96 (96)
  47.171875	read: (233.0 165.0 233.0 024 50.2 13.6 00.0 00001000
  47.171875	send_to_all: SETINFO input.voltage "233.0"
  47.171875	send_to_all: SETINFO output.voltage "233.0"
  47.171875	send_to_all: SETINFO input.frequency "50.2"
  48.906250	send: Q1
  49.171875	received 96 (96)
  49.171875	read: (233.0 165.0 233.0 024 50.0 13.6 00.0 00001000
  49.171875	send_to_all: SETINFO input.frequency "50.0"
  50.906250	send: Q1
  51.187500	received 96 (96)
  51.187500	read: (230.0 165.0 230.0 024 50.0 13.6 00.0 00001000
  51.187500	send_to_all: SETINFO input.voltage "230.0"
  51.187500	send_to_all: SETINFO output.voltage "230.0"
^C

hyouko at gmail.com

2013-Sep-17 13:57 UTC

head link

[Nut-upsuser] Zigor Ebro 650 compatibility - revisited (on Windows, at least)

2013/9/16 Martyn Hill <martyn.joseph.hill at
gmail.com>:> Hi Arnaud and NUT team
>
> You may recall some time ago, I and a few others posted questions about the
> above referenced (cheap and cheerful) USB-based UPS - specifically
regarding
> FreeBSD USB support in NUT. The original posting was entitled "Zigor
Ebro
> 650 compatibility".
>
> I've since tried the latest Windows port of NUT with my WinXP laptop
> connected to the Zigor Ebro and finally gotten somewhere!
>
> NUT and Blazer version: Network UPS Tools - Megatec/Q1 protocol USB driver
> 0.09 (2.6.5-3780M)
>
> This at least proves that my previously moody Zigor device _can_
communicate
> nicely with NUT - and one step closer to getting it to work in FreeBSD
(with
> its fancy USB stack...) - which is my ultimate aim.
>
> I attach the output from running the blazer_usb.exe command in debug mode,
> with a very similar ups.conf that I had been using on FreeBSD, thus:
>
> [zigor_ebro_blazer]
>     driver = blazer_usb
>     port = auto
>     desc = "Zigor Ebro 650 USB UPS"
>     subdriver = krauler
>     protocol = megatec
>     langid_fix = 0x409
>     vendorid = 0001
>     productid = 0000
>     bus = bus-0            # This was different for FreeBSD, naturally.
>
> Aside from the occasional "blazer_status: short reply ...
Communications
> with UPS lost: status read failed!" messages (from which it appears to
> recover perfectly well), plus the odd corrupted reply from the device -
e.g.
> "read: #Ff .0 2.0 12.00 50.0... blazer_rating: non numerical value [Ff
.0]",
> the output seems quite promising!
>
> Any ideas where I go from here - firstly to iron-out those buggy responses
> from the device and secondly (and where we left it previously), how to get
> FreeBSD to 'talk' libusb-0.1 or else allow FreeBSD (8.2) and NUT to
work
> with this USB device?
If you're not interested in input.{voltage, current,
frequency}.nominal and battery.voltage.nominal you could add the
'norating' flag in your ups.conf: doing so the driver won't send to
the UPS the 'F' query, whose answer is causing those messages (i.e.
blazer_rating: non numerical value [Ff .0]).

There's something weird in the reply from the UPS: while it should be
like #nnn.n nnn nnn.n/nn.nn nn.n<cr> (n: 0..9), the input voltage
nominal - i.e. the first token - appears to be 'Ff\u0018.0'.
Here
https://lists.alioth.debian.org/pipermail/nut-upsuser/2012-September/007944.html
I see that he has the same UPS and its input.voltage.nominal it's ok.
So, if it's not because of some different configuration in the
ups.conf for the usb quirkiness, maybe it's something os-related.

/dan
>
> Thanks in advance for any guidance in troubleshooting this (possibly not
> very common) configuration.
> Martyn
> London.
>
> --
> "There are 10 types of people in this world. Those who understand
binary and
> those who don't."
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Martyn Hill

2013-Sep-21 10:55 UTC

head link

[Nut-upsuser] Zigor Ebro 650 compatibility - revisited (on Windows, at least)

An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130921/435db3df/attachment.html>

Apparently Analagous Threads

Search for more possibly parallel threads

Nut upsuser - Sep 2013 - Zigor Ebro 650 compatibility - revisited (on Windows, at least)

[Nut-upsuser] Zigor Ebro 650 compatibility - revisited (on Windows, at least)

[Nut-upsuser] Zigor Ebro 650 compatibility - revisited (on Windows, at least)

[Nut-upsuser] Zigor Ebro 650 compatibility - revisited (on Windows, at least)

Apparently Analagous Threads