Nut upsuser - Feb 2011 - Plexus 800VA UPS on ReadyNAS Duo

Hi

I Bought a cheap Plexus 800VA UPS from ebuyer :
http://www.ebuyer.com/product/240319 to use with my Netgear ReadyNAS duo.

Initial version of NUT was very old and NAS didn't detect it although in the
NAS log it said "UPS Disconnected". Syslog did send the following :

Jan 25 12:46:36 nas-27lfc kernel: usb 1-1: new low speed USB device using
uhci_hcd and address 2
Jan 25 12:46:37 nas-27lfc kernel: usb 1-1: configuration #1 chosen from 1
choice
Jan 25 12:46:39 nas-27lfc kernel: usbcore: registered new driver hiddev
Jan 25 12:46:39 nas-27lfc kernel: hiddev96: USB HID v1.11 Device [ATCL FOR
UPS ATCL FOR UPS] on usb-0000:00:
17.0-1
Jan 25 12:46:39 nas-27lfc kernel: usbcore: registered new driver usbhid
Jan 25 12:46:39 nas-27lfc kernel: drivers/usb/input/hid-core.c: v2.6:USB HID
core driver

Installed 2.4.1 using apt and installed in place of initial version

Found various web documents detailing that blazer_usb would probably be the
driver to use.

using usb.conf :

[UPS]
driver = blazer_usb
port = auto

and running the driver in debug mode gives the following :

nas:/etc/nut# /lib/nut/blazer_usb -a UPS -u root -DDD
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.1)
debug level is '3'
Checking device (0000/0000) (003/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: Linux 2.6.17.14ReadyNAS ehci_hcd
- Product: EHCI Host Controller
- Serial Number: 0000:00:17.2
- Bus: 003
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (002/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: Linux 2.6.17.14ReadyNAS uhci_hcd
- Product: UHCI Host Controller
- Serial Number: 0000:00:17.1
- Bus: 002
Trying to match device
Device does not match - skipping
Checking device (0001/0000) (001/003)
- VendorID: 0001
- ProductID: 0000
- Manufacturer: ATCL FOR UPS
- Product: ATCL FOR UPS
- Serial Number: ATCL FOR UPS
- Bus: 001
Trying to match device
Device matches
failed to claim USB device: could not claim interface 0: Device or resource
busy
detached kernel driver from USB device...
Trying megatec protocol...
send: Q1
read: error sending control message: Broken pipe
blazer_status: short reply
Status read 1 failed
send: Q1
read: error sending control message: Broken pipe
blazer_status: short reply
Status read 2 failed
send: Q1
read: error sending control message: Broken pipe
blazer_status: short reply
Status read 3 failed
Trying mustek protocol...
send: QS
read: QS
blazer_status: short reply
Status read 1 failed
send: QS
read: QS
blazer_status: short reply
Status read 2 failed
send: QS
read: QS
blazer_status: short reply
Status read 3 failed
Trying megatec/old protocol...
send: D
read: D
blazer_status: short reply
Status read 1 failed
send: D
read: D
blazer_status: short reply
Status read 2 failed
send: D
read: D
blazer_status: short reply
Status read 3 failed
No supported UPS detected

lsusb gives :

nas:/etc/nut# lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 0001:0000 Fry's Electronics
Bus 001 Device 001: ID 0000:0000

I also tried the usbhid-ups driver in explore mode as some people seemed to
think that may work

[UPS]
driver = usbhid-ups
vendorid = 0001
productid = 0000
desc = "Plexus 800VA USB"
port = auto
explore

nas:/etc/nut# /lib/nut/usbhid-ups -a UPS -u root -DDD
Network UPS Tools - Generic HID driver 0.34 (2.4.1)
USB communication driver 0.31
debug level is '3'
upsdrv_initups...
Checking device (0000/0000) (003/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: Linux 2.6.17.14ReadyNAS ehci_hcd
- Product: EHCI Host Controller
- Serial Number: 0000:00:17.2
- Bus: 003
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (002/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: Linux 2.6.17.14ReadyNAS uhci_hcd
- Product: UHCI Host Controller
- Serial Number: 0000:00:17.1
- Bus: 002
Trying to match device
Device does not match - skipping
Checking device (0001/0000) (001/003)
- VendorID: 0001
- ProductID: 0000
- Manufacturer: ATCL FOR UPS
- Product: ATCL FOR UPS
- Serial Number: ATCL FOR UPS
- Bus: 001
Trying to match device
Device matches
HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01 22 20 00
HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22 20 00
HID descriptor length 32
Report Descriptor size = 32
Report Descriptor: (32 bytes) => 06 a0 ff 09 01 a1 01 09 03 15 00 25 01 75
 08 95 08 81 02 09 04 15 00 25 01 75 08 95 08 91 02 c0
Using subdriver: EXPLORE HID 0.1
Can't retrieve Report 0: Broken pipe
Path: ffa00001.ffa00003, Type: Input, ReportID: 0x00, Offset: 0, Size: 8
Can't retrieve Report 0: Broken pipe
Path: ffa00001.ffa00004, Type: Output, ReportID: 0x00, Offset: 0, Size: 8
Report descriptor retrieved (Reportlen = 32)
Found HID device
Detected a UPS: ATCL FOR UPS/ATCL FOR UPS
upsdrv_initinfo...
upsdrv_updateinfo...
file_report_buffer: expected 0 bytes, but got 128!
Report[err]: (128 bytes) => 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01
 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00
 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00
 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
 00 00 00 00 01 00 00 00 00 00 00 00
HIDGetEvents: failed to buffer report: Numerical result out of range
Got -34 HID objects...
Quick update...
dstate_init: sock /var/run/nut/usbhid-ups-UPS open on fd 5
upsdrv_updateinfo...
file_report_buffer: expected 0 bytes, but got 128!
Report[err]: (128 bytes) => 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01
 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00
 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00
 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
 00 00 00 00 01 00 00 00 00 00 00 00
HIDGetEvents: failed to buffer report: Numerical result out of range
Got -34 HID objects...
Quick update...
Signal 2: exiting
upsdrv_cleanup...

this last section keeps repeating ad infinitum

I did also download the source for nut-2.6 and compiled it. Using the
drivers from that version I get a similar result :

nas:/etc/nut# /usr/local/ups/bin/usbhid-ups -a plexus -u root -DDDDDD
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000     debug level is '6'
   0.008437     upsdrv_initups...
   0.013888     Checking device (0000/0000) (003/001)
   0.014529     - VendorID: 0000
   0.014730     - ProductID: 0000
   0.014890     - Manufacturer: Linux 2.6.17.14ReadyNAS ehci_hcd
   0.015050     - Product: EHCI Host Controller
   0.015190     - Serial Number: 0000:00:17.2
   0.015351     - Bus: 003
   0.015491     Trying to match device
   0.016072     Device does not match - skipping
   0.016353     Checking device (0000/0000) (002/001)
   0.016854     - VendorID: 0000
   0.017054     - ProductID: 0000
   0.017214     - Manufacturer: Linux 2.6.17.14ReadyNAS uhci_hcd
   0.017375     - Product: UHCI Host Controller
   0.017515     - Serial Number: 0000:00:17.1
   0.017675     - Bus: 002
   0.017816     Trying to match device
   0.018076     Device does not match - skipping
   0.018277     Checking device (0001/0000) (001/003)
   0.059018     - VendorID: 0001
   0.062545     - ProductID: 0000
   0.065952     - Manufacturer: ATCL FOR UPS
   0.069319     - Product: ATCL FOR UPS
   0.072685     - Serial Number: ATCL FOR UPS
   0.076152     - Bus: 001
   0.079459     Trying to match device
   0.083206     Device matches
   0.102265     HID descriptor, method 1: (9 bytes) => 09 21 11 01 00 01 22
20 00
   0.105872     i=0, extra[i]=09, extra[i+1]=21
   0.110180     HID descriptor, method 2: (9 bytes) => 09 21 11 01 00 01 22
20 00
   0.113387     HID descriptor length 32
   0.124890     Report Descriptor size = 32
   0.128417     Report Descriptor: (32 bytes) => 06 a0 ff 09 01 a1 01 09 03
15 00 25 01 75
   0.131964      08 95 08 81 02 09 04 15 00 25 01 75 08 95 08 91 02 c0
   0.137816     Using subdriver: EXPLORE HID 0.1
   0.141102     Entering libusb_get_report
   0.148517     Can't retrieve Report 00: Broken pipe
   0.152705     hid_lookup_path: ffa00001 -> not found in lookup table
   0.156212     hid_lookup_path: ffa00003 -> not found in lookup table
   0.159659     Path: ffa00001.ffa00003, Type: Input, ReportID: 0x00,
Offset: 0, Size: 8
   0.163026     Entering libusb_get_report
   0.170641     Can't retrieve Report 00: Broken pipe
   0.174068     hid_lookup_path: ffa00001 -> not found in lookup table
   0.175832     hid_lookup_path: ffa00004 -> not found in lookup table
   0.177395     Path: ffa00001.ffa00004, Type: Output, ReportID: 0x00,
Offset: 0, Size: 8
   0.179279     send_to_all: SETINFO ups.mfr "ATCL FOR UPS"
   0.181884     send_to_all: SETINFO ups.model "ATCL FOR UPS"
   0.188277     send_to_all: SETINFO ups.serial "ATCL FOR UPS"
   0.189980     send_to_all: SETINFO ups.vendorid "0001"
   0.191663     send_to_all: SETINFO ups.productid "0000"
   0.193186     Report descriptor retrieved (Reportlen = 32)
   0.197435     Found HID device
   0.200762     Detected a UPS: ATCL FOR UPS/ATCL FOR UPS
   0.204569     find_nut_info: unknown info type: load.off.delay
   0.208397     find_nut_info: unknown info type: load.on.delay
   0.210040     find_nut_info: unknown info type: load.off.delay
   0.211703     send_to_all: SETINFO device.type "ups"
   0.213387     send_to_all: SETINFO driver.version "2.6.0"
   0.215190     send_to_all: SETINFO driver.version.internal "0.35"
   0.216854     send_to_all: SETINFO driver.name "usbhid-ups"
   0.218437     upsdrv_initinfo...
   0.220060     send_to_all: SETINFO driver.version.data "EXPLORE HID
0.1"
   0.221784     send_to_all: SETINFO driver.parameter.pollfreq "30"
   0.223387     upsdrv_updateinfo...
   0.485812     libusb_get_interrupt: Connection timed out
   0.486032     Got 0 HID objects...
   0.486212     Quick update...
   0.486453     send_to_all: SETINFO ups.status "OB"
   0.486734     send_to_all: DATAOK
   0.487535     dstate_init: sock /var/state/ups/usbhid-ups-plexus open on
fd 5
   0.487836     send_to_all: SETINFO driver.parameter.pollinterval "2"
   0.488096     send_to_all: SETINFO device.mfr "ATCL FOR UPS"
   0.488337     send_to_all: SETINFO device.model "ATCL FOR UPS"
   0.488597     send_to_all: SETINFO device.serial "ATCL FOR UPS"
   0.488778     upsdrv_updateinfo...
   0.745691     libusb_get_interrupt: Connection timed out
   0.745932     Got 0 HID objects...
   0.746092     Quick update...
   2.313347     Signal 2: exiting
   2.313607     upsdrv_cleanup...

using Blazer_usb on 2.6 gives virtually the same output as 2.4.1

Any ideas?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20110208/1c76ce2f/attachment-0001.htm>

Citeren Mike Barber <badpatch op googlemail.com>:
> Installed 2.4.1 using apt and installed in place of initial version
>
> Found various web documents detailing that blazer_usb would probably be the
> driver to use.
>
> using usb.conf :
>
> [UPS]
> driver = blazer_usb
> port = auto
>
> and running the driver in debug mode gives the following :
[...]
> Checking device (0001/0000) (001/003)
> - VendorID: 0001
> - ProductID: 0000
> - Manufacturer: ATCL FOR UPS
> - Product: ATCL FOR UPS
> - Serial Number: ATCL FOR UPS
The VendorID / ProductID combination is bogus. The manufacturer of the  
UPS was too cheap to apply for a real USB ID and made one up. This  
means that this will give us no clue how to communicate with this  
device based on this information. A few years ago we ran into this  
combination for the first time and at that time we found out how to  
talk to that particular device. However, this doesn't mean that yours  
will work in the same way (it may be something completely different,  
there is no way to tell).

There is a very small chance that one of the other subdrivers in  
blazer_usb is able to talk to device. You'll have to help finding it  
by specifying 'vendorid', 'productid' and 'subdriver' in
ups.conf. See
'man 8 blazer' for more information. If this also fails to detect your  
UPS you're basically out of luck. Unless *you* can provide us with the  
protocol this device uses (ask the vendor, manufacturer, reverse  
engineer it, whatever), we can't support it in NUT.
> using Blazer_usb on 2.6 gives virtually the same output as 2.4.1
You'll definitely need to use this one for the above to have any  
chance of success. Good luck.

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)