Nut upsuser - Mar 2006 - Adding tripplite smart1500 UPS to tripplite_usb

Hello,

I have a Tripplite SMART1500 UPS, and I'm having a little luck with the
tripplite_usb driver.  Only a LITTLE though.  It's working better than any
of the other drivers I've tried, but I'm not getting a status from it.
Here's the output of upsc:
battery.voltage: 0.00
battery.voltage.nominal: 36
driver.name: tripplite_usb
driver.parameter.port: /dev/hiddev0
driver.version: 2.1.0
driver.version.internal: 0.6
input.voltage: 119
input.voltage.nominal: 120
ups.debug.D: 37 37 38 37 0d 00 00 '7787...'
ups.debug.M: 30 30 38 31 0d 00 00 '0081...'
ups.debug.S: 31 34 30 00 5a 30 0d '140.Z0.'
ups.debug.T: 39 44 32 35 37 31 0d '9D2571.'
ups.delay.shutdown: 64
ups.firmware: F1092.D
ups.load: 23
ups.mfr: Tripp Lite
ups.model: SMART1500
ups.power.nominal: 1500
ups.status:

It seems to be reading some things, but not the all important ups.status.
Anyone have any ideas?  Is there anything I can do to help a devloper figure
this out?  I'm quite savvy, just not in writing drivers :)

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060303/02146b5d/attachment.htm

On 3/4/06, Charles Lepple <clepple@gmail.com>
wrote:
>
> On 3/4/06, Brian Mathis <brian.mathis@gmail.com> wrote:
> > I have a Tripplite SMART1500 UPS, and I'm having a little luck
with the
> > tripplite_usb driver.  Only a LITTLE though.  It's working better
than
> any
> > of the other drivers I've tried, but I'm not getting a status
from it.
>
> That's the right driver, using the USB cable. (Have you tried the
> serial cable, by chance? Not sure if it uses a straight-through cable,
> though.)
>
> I'm on travel now - ping me in about 1.5-2 weeks when I will have
> access to one of these units again.
>
> regards,
> - Charles Lepple
>

I did try the serial cable, but was not able to get anything useful out of
it.  I don't remember the specifics, but I tried the drivers listed on the
compatibility page under tripplite, but none seemed to work.  If you know of
a serial setup that does work, I'd be very happy if you could point me to it
:).

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060306/8cd7504c/attachment.html

On 3/3/06, Brian Mathis <brian.mathis@gmail.com>
wrote:
> battery.voltage: 0.00
Found a bug here. I need a refresher course on floating-point math :-/
> battery.voltage.nominal: 36
> driver.name: tripplite_usb
> driver.parameter.port: /dev/hiddev0
> driver.version: 2.1.0
> driver.version.internal : 0.6
> input.voltage: 119
> input.voltage.nominal: 120
> ups.debug.D: 37 37 38 37 0d 00 00 '7787...'
> ups.debug.M: 30 30 38 31 0d 00 00 '0081...'
> ups.debug.S: 31 34 30 00 5a 30 0d '140.Z0.'
Here's the problem: I don't have all the states mapped out yet for
ups.debug.S.

If you have time to run the battery down on this UPS (preferrably
without anything important running on that UPS), I can add the
ups.status states for this model. I used to have this written down
somewhere, but I can't find it, and I'm not sure when I'll have a
chance to run those tests again.

You would just need to compile a table with states like "on AC",
"on
battery", "low battery", "outlets off", etc. with the
corresponding
ups.debug.S value. Let me know if you need help.

--
- Charles Lepple