[Nut-upsdev] A "standard" serial protocol?

Rob Groner rgroner at RTD.com
Wed May 4 13:32:29 UTC 2016

Thanks, I’ll take a look at that.


From: Nut-upsdev [mailto:nut-upsdev-bounces+rgroner=rtd.com at lists.alioth.debian.org] On Behalf Of Thiago Wiezbicki - NHS
Sent: Monday, May 02, 2016 8:32 AM
To: nut-upsdev <nut-upsdev at lists.alioth.debian.org>
Subject: Re: [Nut-upsdev] A "standard" serial protocol?


My suggestion is using the SEC2400 protocol. It's very simple, complete and based in text using using the idea of requesting and responsing.  In the NUT software the name of the driver that manage this protocol is "gamatronic".

Below the documentation:


Thiago Wiezbicki

De: "Rob Groner" <rgroner at RTD.com<mailto:rgroner at RTD.com>>
Para: "nut-upsdev" <nut-upsdev at lists.alioth.debian.org<mailto:nut-upsdev at lists.alioth.debian.org>>
Enviadas: Quinta-feira, 28 de abril de 2016 13:03:43
Assunto: [Nut-upsdev] A "standard" serial protocol?

I’m still working on the interface to the UPS we’re selling.  USB works great with NUT in Linux, and natively through Windows battery support.  Now I’m looking over the serial protocol.  I can essentially make it anything I want, and it’s VERY tempting to make my own protocol that is intuitive and simple, but I have a feeling every UPS maker does that.  So, before I do that…is there a good, simple, robust protocol in use in multiple UPS’s out there that is somewhat well documented that I could support instead?  It would probably make integrating NUT/serial easier as well.

I looked at what seemed to be some generic serial drivers in NUT, but the commands supported and response patterns didn’t make a lot of sense to me….though I’m not sure how much it really matters if the serial protocol is “readable” to a human.


Rob Groner

Nut-upsdev mailing list
Nut-upsdev at lists.alioth.debian.org<mailto:Nut-upsdev at lists.alioth.debian.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20160504/e6e74d0b/attachment.html>

More information about the Nut-upsdev mailing list