Nut upsdev - Dec 2005 - Command summary for Tripplite 500

Tim,

thanks! Does this UPS have a USB port as well?

The key thing for TrippLite UPSes is this command:

Command to UPS			Response from UPS		Function

:00FFCR				00005XXXXCR		unknown

The second and third bytes are the protocol number. I think I may have
misinterpreted something in the formatting -- what are the hex values
of the bytes in this command/response pair?

I don't have time to cross-check this now, but I can take a look later
and see how it compares to our existing TrippLite support.

--
- Charles Lepple



On 12/5/05, Arnaud Quette <aquette.dev@gmail.com>
wrote:
> Hi Tim,
> the best place for such a doc is the NUT development mailing list
(cc'ed in
> the present mail). If it's worth, then it will be put in the protocol
> section...
> Thanks for your contribution, as it might be useful to some NUT developers.
>
>  --
>  Tim Steiner wrote:
> Hello,
>
>    Not sure if this is the appropriate place to send
>  this, but thought it might be of some help.  I spent
>  some time recently trying to figure out how to
>  communicate with a Tripplite 500 directly through a
>  serial port ( rather than using their software ).
>  Anyway the attached document is what I had come up
>  with and, after looking through the NUTS project,
>  thought I should pass it along.
>
>  Hope it helps
>  ---
>
> Arnaud Quette
>  --
>  Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
>  Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
>  Debian Developer - http://people.debian.org/~aquette/
>  OpenSource Developer - http://arnaud.quette.free.fr/
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev

On 12/5/05, Charles Lepple <clepple@gmail.com>
wrote:
> The second and third bytes are the protocol number. I think I may have
> misinterpreted something in the formatting -- what are the hex values
> of the bytes in this command/response pair?
Also note that the byte before CR is generally a checksum (see lines
56 and 527 of
http://boxster.ghz.cc/projects/nut/browser/branches/Development/drivers/tripplite_usb.c
for the algorithm). This should allow you to try commands other than
the ones generated by the official driver.

--
- Charles Lepple