[Nut-upsuser] Tripp lite SMART1000LCD

[Karl Dalen]

Charles,

Thanks for your information.
I've just compiled the latest NUT version nut-2.2.1.
When I plug in the USB cable from the ups it looks like
the device does not get recognized at all in the system.
Shouldn't there be some log info in /var/syslog or dmesg
when a device is plugged in? There was nothing there.
I'm running Linux kernel,  2.6.17 (mandriva 2007)

# /usr/local/ups/bin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.2.1
Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1)

No matching HID UPS found
Driver failed to start (exit status=1)

Am I missing some usb utility needed for hid devices to  work in Linux ?
My usb keyboard and mouse do work.

% rpm -qa | grep usb
libusb0.1_4-0.1.12-2mdv2007.0
libusb0.1_4-static-devel-0.1.12-2mdv2007.0
usbutils-0.72-1mdk
libusb0.1_4-devel-0.1.12-2mdv2007.0

% lsusb

Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 0430:0100 Sun Microsystems, Inc. 3-button Mouse
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 004: ID 0430:0005 Sun Microsystems, Inc. Type 6 Keyboard
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

ups.conf
-----------
[SMART1000LCD]
driver = usbhid-ups
port = auto
desc = "Tripp Lite SMART1000LCD USB"

Any suggestions would be appreciated.

/Karl D

> Date: Fri, 25 Jan 2008 08:11:44 -0500
> From: clepple at gmail.com
> To: k_dal2 at hotmail.com
> Subject: Re: [Nut-upsuser] Tripp lite SMART1000LCD
> CC: nut-upsuser at lists.alioth.debian.org
> 
> On Jan 24, 2008 3:08 PM, Karl Dalen <k_dal2 at hotmail.com> wrote:
> > This model is supposed to be fully HID PD class compliant.
> > Should I use the usbhid-ups  or  tripplite_usb driver ?
> 
> usbhid-ups
> 
> The code in the trunk looks like it should recognize both 0x2005 as
> well as 0x2007 for the USB product ID. Which version of NUT are you
> using?
> 
> > HID descriptor:
> >   Descriptor Length:9, Type:33
> >   Hid Class spec release: 110
> >   Country Code: 0 (FYI 33 = US)
> >   Number of class descriptors: 1
> >   Class descriptor type: 34
> >   Total size of Report Descriptor: 2049
> >
> > Don't know what I was doing wrong in reading the
> > HID descriptor (using  another application)  but
> > I got the length 2049, which does not match the true
> > length of the report descriptor (601) I get when reading it.
> 
> There are two ways of getting the report descriptor: one is to fetch
> it explicitly, and the other is to look for it embedded after the
> interface descriptor. The code used by usbhid-ups (drivers/libusb.c)
> checks both methods, and picks the one that looks most  likely. (You
> can see this in the debug messages if you pass several '-D' flags on
> the command line.)
> 
> -- 
> - Charles Lepple

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080126/f3548529/attachment.htm