Re: [Hamlib-developer] Feature-Request: Interface for simple users

[Stephane F. <f8...@fr...>]

Hi Martin,

Martin Biallas skribis:
> Dear Developers,
> 
> hamlib is great. I was using it for years with self-written logbooks.
> I especially appreciate that it (ie. rigctl) can be used in
> command-line form. This makes its usage in scripts -and every other
> codeing-language-  very easy. So far I was mostly needing the
> get-frequency- and get-mode-functions for my logbook (to check for
> dupes), and the send-CW feature with my TS870.
> 
> In the meantime I have the wish to remotely control my TS870, or a
> FT100. Right now, I am running hamlib version 1.2.5, as it comes with
> the GNU/Linux-Debian-stable packages.
>  At least for me, important functionality is missing for the two
> transceivers in use. Could it be, that antenna-selection and
> tuner-control is not implemented for the TS870? Both features would
> come VERY handy for remote control obviously. The FT100 lacks filter
> control among many other things. Though I have heard rumor saying the
> manufacturer has not provided many CAT commands, which the FT100
> manual seems to confirm. Nontheless, more than given with hamlib 1.2.5
> should be possible.

The antenne selection will be present in the next version. It's
implemented in the CVS repository.

> Naturally, I tried to get an insight of how I could implement some
> more features in hamlib. This idea seems not too far fetched, for I
> have coded uCs in C years ago (and never since). But without help of
> someone who knows about hamlib, it would simply take much too long for
> me to get to the level of contributing to the hamlib-community.
> Therefore I have a suggestion for a feature:
> 
> Please provide a rigctl-command that allows simple-minded users like
> me, to send self-defined command/data-bytes to the rig in use.

Isn't "send_cmd" in rigctl what you're looking for?

> For example: According to the TS870 manual, the simple CAT-command
> "AN1;" should be the command to switch to antenna 1. "AN0;" should
> switch to antenna 0.
> 
> hamlib must have all the infrastructure to send data to the TS870, and
> to read TRX-commands from the command-line. So shouldn't it be easy
> for some developers of yours to include such an "gerneral user
> request" command, described above?
> 
> Besides sending simple ASCII-Strings to the serial port (for example),
> the FT100 could require to manipulate single bits of a byte.
> Therefore, a command like suggested should also be able to process hex
> numbers (provided as ASCII-string by the rigctl-user) to the TRX.
> 
> If, finally, there would also a possibility to get back the answer of
> a rig to my proposed general_user_request-command in ASCII form (as a
> string, or as a hex-number-in-string-form) it would be really great.
> 
> Maybe hamlib would get more TRX-support by users like me (who are
> willing to experiment with command-sequences, but are not keen enough
> to code C) submitting verified command sequences that can be
> implemented in future versions of hamlib.
> 
> What I like about that idea to give rigctl-users the opportunity to
> use "homemade commands" easily is, that a) the
> standard-user(=front?)-end remains untouched, while the ambitioned
> rigctl-user has the freedom to provide homemade-commands in case of
> emergency.
> 
> 
> My deepest gratefulness to all who work(ed) on hamlib, es gud dx de

Thanks a lot!
-- 
Stephane - F8CFE