[Nut-upsdev] Fwd: Auto-discard notification
selinger at mathstat.dal.ca
Tue Dec 6 17:34:34 UTC 2005
thanks for your impressive decoding work. Did you compare this with
drivers/tripplite.c in the NUT sources? The protocol seems to be
similar, except that yours appears to send binary data, whereas the
NUT driver sends hex-encoded data.
Does the NUT "tripplite" driver work with your UPS?
If not, it should be relatively easy for you to write a driver that
would work. You could start by modifying the existing "tripplite"
I noticed that you gave the checksums in your decoded protocol as
(0xB1 - (N + N)), (0xB7 - (H + H + H)) etc. I noticed
that the formula simplifies if you include the command letter in the
0xB1 = 0xFF - 'N'
0xB7 = 0xFF - 'H'
etc, so you get:
checksum = (0xFF - ('N' + N + N))
checksum = (0xFF - ('H' + H + H + H))
and so on, which is a nicer formula. -- Peter
Arnaud Quette 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
> Thanks for your contribution, as it might be useful to some NUT developers.
> Tim Steiner wrote:
> 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 -
> OpenSource Developer - http://arnaud.quette.free.fr/
More information about the Nut-upsdev