[Nut-upsdev] TrippLite USB UPS

[Peter Selinger]

Patrick,

the reason your device is not supported is that we have never seen
this device (09AE/4003) before. 

Version 2.0.1 is ancient; USB support has greatly improved since
then. 

To build from SVN sources, do "autoreconf", then "./configure
[options]". What options you need depends on what you want to build
and where you want it installed. See "./configure --help". Probably 
--without-all and --with-usb are reasonable.

Careful when moving sources between your SVN copy and your debian
sources: some drivers (in particular newhidups) have been renamed (it
is now called usbhid-ups in SVN). Also, the drivers from one version
may not always be compatible with upsd from another version.

Here is what I recommend you to do:

* update your SVN sources to the very newest (I just committed a
  change): "svn update"

* run the hidups-ups (formerly newhidups) driver as follows:

hidups-ups -u root -DD -x productid=4003 auto

Report what you see, particularly lines starting with "Path:".

-- Peter

Charles Lepple wrote:
> 
> On 1/21/07, Patrick <cso at satcharters.com> wrote:
> > Good afternoon,
> >
> > I am trying to communicate with a new Tripp-Lite UPS via usb and having little
> > luck. After more than a week on this I've decided to ask for help. I am very
> > inexperienced at posting information to message boards, so hopefully I'm
> > doing this right. I assume this is the correct place to post this message.
> 
> Well, there's a good deal of overlap between the nut-upsuser and
> nut-upsdev lists, but it sounds like there may be some code changes
> needed to support this particular UPS. Nothing to be afraid of,
> though.
> 
> > That seems to have given me some partial success.
> > newhidups sees a device but won't talk to it:
> >    # /lib/nut/newhidups -u root -DDDD /dev/usb/hiddev0
> >    Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)
> >
> >    debug level is '4'
> >    Checking device (09AE/4003) (002/002)
> >    - VendorID: 09ae
> >    - ProductID: 4003
> >    - Manufacturer: Tripp Lite
> >    - Product: TRIPP LITE UPS
> >    - Serial Number: 9530ALCPS519400017
> >    - Bus: 002
> >    Trying to match device
> >    This particular Tripp Lite device (09ae/4003) is not (or perhaps not
> >    yet) supported by newhidups. First try the tripplite_usb driver. If
> >    this fails, please write to the NUT developer's mailing list.
> 
> This is the driver which should eventually handle your UPS. I'll defer
> to Peter Selinger on this, but the newhiudps driver just doesn't know
> about your particular model yet.
> 
> > Decided to try hidups and got a bit more info:
> >    # /lib/nut/hidups -u root -DDDD /dev/usb/hiddev0
> >    Network UPS Tools: HID UPS driver 0.13 (2.0.5)
> >
> >    Warning: This is an experimental driver.
> >    Some features may not function correctly.
> >
> >    debug level is '4'
> >    Detected Tripp Lite       TRIPP LITE UPS
> >    on port /dev/usb/hiddev0
> >    addhidvalue(850066, battery.charge): obtained 100
> >    addhidvalue(850068, battery.runtime): obtained 1903
> >    addhidvalue(840035, ups.load): obtained 24
> >    addhidvalue(840056, ups.delay.start): obtained 0
> >    addhidvalue(840057, ups.delay.shutdown): obtained -1
> 
> The 'hidups' driver is not being maintained any more, but the
> information you got from it leads me to believe that newhidups is the
> place to support it, not tripplite_usb (the latter driver only handles
> older Tripp Lite models that essentially stuff RS-232 into USB
> packets.
> 
> > Downloaded the latest PowerAlert (version 12) and installed it. Found out I
> > needed Java. Downloaded it and got the PA console to load. It shows the
> > device is on battery power (it is not). It also shows the manufacturer
> > correctly as Tripp Lite, but the model is GENERIC.
> 
> Does it say something like "protocol 4003" anywhere?
> 
> > So, bottom line is I don't know where to go from here. I decided I would see
> > if anyone was willing to point me in the right direction for my next steps. I
> > can pretty much do anything with this system to obtain any information asked
> > for, but I might need some help in obtaining it. I am also going to try
> > connecting the UPS to a slightly older Sarge desktop with a serial port to
> > see what happens there.
> 
> If you change from USB to serial (or vice versa), you might be able to
> save yourself a little trouble by completely powering the UPS down and
> unplugging it (for a couple of seconds, or until you hear some relays
> click). Many of these units need to be "cold-booted" like this before
> they will respond properly on the other port.
> 
> -- 
> - Charles Lepple
> 
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
>