Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Matt Ettus <matt@ettus.com>
To: Stephane Fillod <fillods@users.sourceforge.net>,
	Hamlib developers <hamlib-developer@lists.sourceforge.net>
Cc: Linux HAMs <Linux-hams@vger.kernel.org>
Subject: Re: [Hamlib-developer] [ANN] Hamlib 1.1.3 released
Date: Tue, 18 Jun 2002 05:53:40 -0000	[thread overview]
Message-ID: <aemi30$c8o$2@main.gmane.org> (raw)


Stephane Fillod <fillods@users.sourceforge.net> said:

>  * rotator frontend, new easycomm backend

Any interest in an F1EHN Az-el controller?  EME guys seem to love it.  I found
info on the control protocol from some guys who cloned the damned thing...  I
think its amazing that somebody put the effort in to copy bad hardware and
protocols just to be compatible with closed source control software...

Anyway, they have docs on the [primitive] protocol here...

http://www.dnai.com/~rexa/Projects/EMEboard.html

> Plan for 1.1.4:
> * collaboration with gnuradio project

Cool.  Did you get a chance to grab the gnuradio code?

Matt


                 reply	other threads:[~2002-06-18  5:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='aemi30$c8o$2@main.gmane.org' \
    --to=matt@ettus.com \
    --cc=Linux-hams@vger.kernel.org \
    --cc=fillods@users.sourceforge.net \
    --cc=hamlib-developer@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox