From: Stephane Fillod <f8cfe@free.fr>
To: "IT2 Stuart Blake Tener, USNR" <teners@bh90210.net>
Cc: don <don_reid@comcast.net>, Linux HAMs <Linux-hams@vger.kernel.org>
Subject: memory programming, was Re: D-STAR Rig Control
Date: Fri, 11 Apr 2008 14:50:41 +0200 [thread overview]
Message-ID: <20080411125041.GG6021@charybde.local> (raw)
In-Reply-To: <1203096083.47b5ca13b9626@mgtmail.com>
Fri, Feb 15, 2008, IT2 Stuart Blake Tener, USNR skribis:
> Quoting don <don_reid@comcast.net>:
>
> > On Fri, Feb 15, 2008 at 04:02:44PM +0000, IT2 Stuart Blake Tener, USNR wrote:
> > > ALCON:
> > >
> > > I am curious what (if any) integration is existent with controlling rigs
> > such as
> > > the ICOM IC-2820H, IC-91AD, etc..., that are D-STAR radios.
> > >
> > > Being able to read and write memories, etc.., would be quite useful to say
> > the
> > > least.
> >
> > I have an IC-2820 and have looked into what it can do over the computer
> > interface. It appears that it can only upload or download the entire memory
> > as one large chunk. The data is in hex format and is a bit over 100k bytes.
>
> Excellent! My goal (initially) would be to design a software for programming the
> 2820H, and IC-91AD that would be usable on a MacOS/Linux environment.
Do you have the documentation of the protocol/format of the memory data?
> May I respectfully request if you could publish the information regarding how
> one would accomplish this, and if the HamLib supports provisionment of an API
> to do same?
Hamlib already has the API to program memory of rigs[1]. However, we're
badly missing memory programming GUI. Is there's anyone into GUI around
here? It should be done easily cross-platform with FLTK[2] or wxPython[3],
or with any other framework. You will find help on programming with Hamlib
by joining the mailing list here[4].
[1] http://hamlib.sourceforge.net/manuals/1.2.7/html/mem_8c.html
[2] http://www.fltk.org/
[3] http://wxPython.org/
[4] https://lists.sourceforge.net/lists/listinfo/hamlib-developer
73
--
Stephane - F8CFE
next prev parent reply other threads:[~2008-04-11 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 16:02 D-STAR Rig Control IT2 Stuart Blake Tener, USNR
2008-02-15 16:25 ` don
2008-02-15 17:21 ` IT2 Stuart Blake Tener, USNR
2008-04-11 12:50 ` Stephane Fillod [this message]
[not found] ` <20080411165735.GA2371@reid1.localdomain>
2008-04-24 21:01 ` memory programming, was " Stephane Fillod
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=20080411125041.GG6021@charybde.local \
--to=f8cfe@free.fr \
--cc=Linux-hams@vger.kernel.org \
--cc=don_reid@comcast.net \
--cc=teners@bh90210.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