[Nut-upsdev] smart1050slt by tripp lite

[chance fulton]

Attached the log below, of the aforementioned command. I also have no
luck wuth the upsc, as I get connection refused (probably user issues) I
do have all the users in upsd.users setup correctly as far as I can
tell. I suppose that is not a problem until I get the driver talking to
the device itself.

Is this easier to do over a serial cable, or is USB just as good?

On Sun, 2010-01-31 at 16:45 -0500, Charles Lepple wrote:
> On Jan 31, 2010, at 4:29 PM, chance fulton wrote:
> 
> > On Sun, 2010-01-31 at 16:09 -0500, Charles Lepple wrote:
> >> On Jan 31, 2010, at 3:56 PM, chance fulton wrote:
> >>
> >>> On Sun, 2010-01-31 at 14:38 -0500, Charles Lepple wrote:
> >>>> On Jan 31, 2010, at 1:44 PM, chance fulton wrote:
> >>>>
> >>>>> Original Message
> >>>>>> I have 2 SmartUOS1050SLT's that apparently protocol 3004, has  
> >>>>>> there
> >>>>>> been
> >>>>>> any progress on getting these units supported under nut? I am
> >>>>>> running
> >>>>>> version 2.4.1, and get the following output when starting the
> >>>>>> driver.
> >>>>>
> >>>>>> #lsusb
> >>>>>> Bus 005 Device 002: ID 09ae:0001 Tripp Lite
> >>>>>
> >>>>>> # upsdrvctl -DDDD start
> >>>>>> Network UPS Tools - UPS driver controller 2.4.1
> >>>>>> Starting UPS: tripplite
> >>>>>> exec: /lib/nut/tripplite_usb -a tripplite
> >>>>>> Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20
> >>>>>> (2.4.1)
> >>>>>> Warning: This is an experimental driver.
> >>>>>> Some features may not function correctly.
> >>>>>
> >>>>>> Detected a UPS: TRIPP LITE/TRIPP LITE SMART1050SLT
> >>>>>> Unknown input voltage range: 0x02
> >>>>>> Unknown number of switchable load banks: 0x00
> >>>>>> Unit ID: 0
> >>>>>> Unknown protocol (3004)Attached to Tripp Lite SMART1050SLT
> >>>>>> Unknown value for s[1]: 0x01
> >>>>
> >> [...]
> >>
> >>>> Please post a few details about your OS distribution and version.
> >>>>
> >>> I have Ubuntu server 9.10 Kernel 2.6.31-17-generic-pae
> >>> I have just installed Network UPS Tools - UPS driver controller
> >>> 2.4.1-r2286
> >>>
> >>> And still have the same issue.
> >>
> >> I just committed a few changes to SVN. In a few minutes, it should
> >> build another tarball for r2294:
> >>
> >> http://buildbot.ghz.cc/public/nut/waterfall?branch=trunk&builder=Debian-etch-x86
> >>
> >> A couple of questions:
> >>
> >>  - When you were testing, how did you run the driver?
> >>  - Is the Ubuntu package for NUT still installed?
> >>  - Are you using SVN, or the tarballs?
> >>
> >> thanks,
> >>
> >> - Charles
> > OK will do, as for the questions.
> >
> > I run the driver from this command:
> > sudo /usr/local/ups/bin/upsdrvctl start
> >
> > I uninstalled the Ubuntu package, and purged the configs. then I  
> > copied
> > in my settings from the old installation to the new config files.
> >
> > I am using the tarballs as I an new with the whole autoconf thing, and
> > could not get it going.
> >
> >
> > I have just removed the previous version, and installed from the svn
> > trunk version 2297. I now get this.
> >
> > Network UPS Tools - UPS driver controller 2.4.1-2297
> > Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20
> > (2.4.1-2297)
> > Warning: This is an experimental driver.
> > Some features may not function correctly.
> >
> > Detected a UPS: TRIPP LITE/TRIPP LITE SMART1050SLT
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > libusb_get_interrupt() returned 0 instead of 8 while sending 3a 00  
> > ff 0d
> > 00 00 00 00 '........'
> > Unknown input voltage range: 0x02
> > Unknown number of switchable load banks: 0x00
> > Unit ID: 0
> > Unknown protocol (3004)Attached to Tripp Lite SMART1050SLT
> > Unknown value for s[1]: 0x01
> >
> > Pretty much the same, just more debug info.
> 
> Another tarball coming: http://buildbot.ghz.cc/public/nut/waterfall?branch=branches%2Ftripplite-proto-3004&builder=Debian-etch-x86&reload=none
> 
> This time, when you start it, run the driver directly (without  
> upsdrvctl), and send the output to a logfile. It'll be something like:
> 
>     /usr/local/ups/bin/tripplite_usb -a name-of-ups -DDD | tee /tmp/ 
> log-r2298.txt
> 
> Also, you can start upsd, and record what 'upsc name-of-ups at localhost'  
> shows.
> 
> Please gzip both logs before mailing them to the list.
> 
> Thanks,
> 
> - Charles

-------------- next part --------------
A non-text attachment was scrubbed...
Name: logr2298.txt.gz
Type: application/x-gzip
Size: 1275 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100131/df323797/attachment.bin>