[Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups

[Barry Skrypnyk]

See comments below.

> -----Original Message-----
> From: Charles Lepple [mailto:clepple at gmail.com]
> Sent: Friday, August 29, 2014 5:35 AM
> To: barry at skrypnyks.com
> Cc: nut-upsuser at lists.alioth.debian.org
> Subject: Re: [Nut-upsuser] Smart1500lcdt will not connect with usbhid-ups
> 
> On Aug 28, 2014, at 6:49 PM, Barry Skrypnyk <barry at skrypnyks.com> wrote:
> 
> > I have searched the archives and googled this problem with usbhid-ups.
I
> would really appreciate any help anyone could offer to solve the problem.
> >
> > System: Ubuntu 14.04.1 Trusty Tahr
> 
> Which kernel version are you using?
3.13.0-35-generic
I just updated this late last night.
> 
> > Installed nut from Ubuntu repositories - nut 2.7.1
> >
> > Ups.conf file
> >
> > maxretry = 3
> >
> > # user = nut
> >
> > [TrippLite]
> >
> >         driver = usbhid-ups
> >
> >         port = auto
> >
> >         productid = 3016
> >
> >         desc = "Tripp Lite UPS, USB Interface"
> 
> Configuration looks good.
> 
> >
> > Data from the usbhid-ups command
> >
> > <<...>>
> 
> This part confuses me:
> 
>   68.487087     Checking device (09AE/3016) (004/008)
>   68.564137     - VendorID: 09ae
>   68.564168     - ProductID: 3016
>   68.564174     - Manufacturer: Tripp Lite
>   68.564220     - Product: TRIPP LITE UPS
>   68.564225     - Serial Number: 2406CVLSM871900494
>   68.564231     - Bus: 004
>   68.564235     Trying to match device
>   68.564255     Device does not match - skipping
> 
> Judging from the time, did the driver connect initially, or is it still
trying to
> reconnect? (I haven't used "maxretry" before.)
Tries to reconnect forever.  It never initially connected.  Maxretry was in
the configuration file as a default of the new installation.  I added from
the user = nut to the end. 
> 
> > Data from lsusb command
> >
> > fs00pc:~$ lsusb
> > Bus 003 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111
> > Card Reader Controller Bus 003 Device 001: ID 1d6b:0002 Linux
> > Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux
> > Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux
> > Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux
> > Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux
> > Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux
> > Foundation 2.0 root hub Bus 004 Device 008: ID 09ae:3016 Tripp Lite
> > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009
> > Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device
> > 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> After the errors from usbhid-ups, does "lsusb -vvv -d 09ae:" return valid
> information, or do you also get timeouts in syslog as well?
I included the result of the command and the syslog in the attached gzip
file.  It looks like it worked but there is also a complaint about not being
able to open the device properly.  Since I installed the new kernel, I
re-ran the tests from before.  I still get an error but it is not in an
infinite loop looking to connect with the Tripp Lite on the usb port as it
was before.
> 
> If lsusb doesn't work, it points to a problem between the UPS firmware and
> your Linux kernel version. (Well, technically, lsusb could be at fault,
but it
> doesn't change as much as the kernel USB HCI drivers.)
> 
> In that case, you may want to check with Tripp Lite; they were kind enough
> to post results of testing their hardware against NUT and Linux. They
should
> be able to repeat that test with Ubuntu 14.04.
I will try to contact Tripp Lite support to see if they can be of some help.
> 
> --
> Charles Lepple
> clepple at gmail
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: usb.txt.gz
Type: application/x-gzip
Size: 2572 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140829/482a5579/attachment.bin>