Nut upsuser - Dec 2012 - Tecnoware ERA LCD (UPSilon 2000) communication problem

Hi to everyone!

I'm posting here after digging around the nut-upsuser and nut-upsdev
mailing list, hoping I didn't miss something important.

I'm trying to make my ups working with nut: it's a Tecnoware ERA LCD
0.85
which uses the so-hated UPSilon 2000 software to connect via usb.

Personally I checked and seems that this junk software only works from
windows, I'm trying to contact with tecnoware to get some info.
I read a lot in the mailing-list about the "langid_fix" patch that
seems
was definitively included in released 2.6.3.

HCL suggest "blazer_usb langid_fix=0x4095" for a similar product but
it
seems to not work.
Here are my settings, I attached the debug output of blazer_usb start.
Nut version is stable 2.6.5.
Does anyone has any suggestions please?

[ERA_LCD]
     driver = blazer_usb
     subdriver = krauler
     langid_fix=0x4095
     port = /dev/bus/usb/002/002
     vendorid = 0001
     productid = 0000
     desc = "Tecnoware UPS ERA 0.8"

port was setted according to lsusb output:
$ lsusb
[...]
Bus 002 Device 002: ID 0001:0000 Fry's Electronics

Thanks in advance for any help.
Greetings,
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20121227/c4b58c8a/attachment.html>
-------------- next part --------------
$ sudo ./drivers/blazer_usb -a ERA_LCD -u root -DDDDD -q

Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 (2.6.5)
   0.000000     debug level is '5'
   0.002536     language ID workaround enabled (using '0x4095')
   0.173506     Checking device (1D6B/0001) (005/001)
   0.173652     - VendorID: 1d6b
   0.173667     - ProductID: 0001
   0.173678     - Manufacturer: Linux 3.2.0-35-generic-pae uhci_hcd
   0.173691     - Product: UHCI Host Controller
   0.173703     - Serial Number: 0000:00:10.3
   0.173714     - Bus: 005
   0.173725     Trying to match device
   0.173766     Device does not match - skipping
   0.173795     Checking device (1D6B/0001) (004/001)
   0.173848     - VendorID: 1d6b
   0.173862     - ProductID: 0001
   0.173873     - Manufacturer: Linux 3.2.0-35-generic-pae uhci_hcd
   0.173902     - Product: UHCI Host Controller
   0.173913     - Serial Number: 0000:00:10.2
   0.173925     - Bus: 004
   0.173936     Trying to match device
   0.173950     Device does not match - skipping
   0.173969     Checking device (1D6B/0001) (003/001)
   0.174020     - VendorID: 1d6b
   0.174033     - ProductID: 0001
   0.174044     - Manufacturer: Linux 3.2.0-35-generic-pae uhci_hcd
   0.174057     - Product: UHCI Host Controller
   0.174068     - Serial Number: 0000:00:10.1
   0.174079     - Bus: 003
   0.174090     Trying to match device
   0.174104     Device does not match - skipping
   0.174121     Checking device (0001/0000) (002/002)
   0.181800     - VendorID: 0001
   0.182344     - ProductID: 0000
   0.182684     - Manufacturer: unknown
   0.182999     - Product: unknown
   0.183255     - Serial Number: unknown
   0.183508     - Bus: 002
   0.183779     Trying to match device
   0.184084     Device matches
   0.187746     send_to_all: SETINFO ups.vendorid "0001"
   0.188120     send_to_all: SETINFO ups.productid "0000"
   0.191756     send_to_all: SETINFO device.type "ups"
   0.191993     send_to_all: SETINFO driver.version "2.6.5"
   0.192103     send_to_all: SETINFO driver.version.internal "0.09"
   0.192224     send_to_all: SETINFO driver.name "blazer_usb"
   0.192270     Trying megatec protocol...
   0.192384     send: Q1
   0.195773     read: error sending control message: Protocol error
   0.196029     blazer_status: short reply
   0.196145     Status read 1 failed
   0.196188     send: Q1
   0.199758     read: error sending control message: Protocol error
   0.200006     blazer_status: short reply
   0.200049     Status read 2 failed
   0.200168     send: Q1
   0.203763     read: error sending control message: Protocol error
   0.204019     blazer_status: short reply
   0.204136     Status read 3 failed
   0.204178     Trying mustek protocol...
   0.204218     send: QS
   0.204336     read: QS
   0.204414     blazer_status: short reply
   0.204526     Status read 1 failed
   0.204630     send: QS
   0.204670     read: QS
   0.204774     blazer_status: short reply
   0.204815     Status read 2 failed
   0.204932     send: QS
   0.204972     read: QS
   0.205077     blazer_status: short reply
   0.205118     Status read 3 failed
   0.205225     Trying megatec/old protocol...
   0.205267     send: D
   0.205305     read: D
   0.205706     blazer_status: short reply
   0.205932     Status read 1 failed
   0.205977     send: D
   0.206016     read: D
   0.206131     blazer_status: short reply
   0.206171     Status read 2 failed
   0.206273     send: D
   0.206319     read: D
   0.206357     blazer_status: short reply
   0.206461     Status read 3 failed
   0.206501     Trying zinto protocol...
   0.206610     send: Q1
   0.210744     read: error sending control message: Protocol error
   0.210953     blazer_status: short reply
   0.211064     Status read 1 failed
   0.211107     send: Q1
   0.214756     read: error sending control message: Protocol error
   0.215004     blazer_status: short reply
   0.215122     Status read 2 failed
   0.215166     send: Q1
   0.218756     read: error sending control message: Protocol error
   0.219004     blazer_status: short reply
   0.219120     Status read 3 failed
   0.219161     No supported UPS detected

On Dec 26, 2012, at 7:00 PM, Rob Power wrote:
> I read a lot in the mailing-list about the "langid_fix" patch
that seems was definitively included in released 2.6.3.
> 
> HCL suggest "blazer_usb langid_fix=0x4095" for a similar product
but it seems to not work.
> Here are my settings, I attached the debug output of blazer_usb start.
> Nut version is stable 2.6.5.
The suggested langid_fix for Tecnoware appears to be 0x409 (versus 0x4095 for
some other brands). Does that value work?

-- 
Charles Lepple
clepple at gmail

Thanks for your response.
I have same result with 0x409. Any other clues?


2012/12/27 Charles Lepple <clepple at gmail.com>
> On Dec 26, 2012, at 7:00 PM, Rob Power wrote:
>
> > I read a lot in the mailing-list about the "langid_fix"
patch that seems
> was definitively included in released 2.6.3.
> >
> > HCL suggest "blazer_usb langid_fix=0x4095" for a similar
product but it
> seems to not work.
> > Here are my settings, I attached the debug output of blazer_usb start.
> > Nut version is stable 2.6.5.
>
> The suggested langid_fix for Tecnoware appears to be 0x409 (versus 0x4095
> for some other brands). Does that value work?
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20121227/5da8e0e9/attachment.html>