Re: [Hamlib-developer] Why hamlib is not really suited for satellite radias

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

Hi Luc!

On Thu, Sep 05, 2002, lx...@gm... wrote:
> One of the problem is the sub band. How do I change it at a way that does
> work with every radio? On my IC-910 I have to enable the sub band - set the
> frequency - and disable it. The code should really do that at is own. In the

I agree with you the code(backend) should really do that on his own.
Then, this makes everything looks simple for the application using Hamlib.

> case of the ic910 there is another problem. I want to set a frequency of 145.950
> - but the transceiver has currently 70cm on the main band. I have to
> retrieve the current frequency - look if I need to swap the bands - and swap them if
> needed. This is very IC910 specific - why does I have to do it?

Well, it looks like the IC910 backend needs some changes. And it's not
impossible to extend the frontend API if justified.
Okay, I'd like to understand your needs.

Your goal is to operate in "split" mode, on a full-duplex rig, with a
"follow-me" mode (rx and tx stay consistent).
In satellite mode, you want to be able to control independently the receive 
and the transmit frequencies (and associated modes,etc.). From an API point of
view, this would be done first by entering rig_set_split_mode, and then
using rig_set_freq (receive) and rig_set_split_freq (transmit).
REM: tell me if this is enough or not for your application.
     If not, feel free to express what kind of call you would like to
     have, with a prototype and an idea of the semantic.

Now, let's talk about the IC910. I never operated a rig with a sub band,
I don't have the IC910 manual, so you'll have to walk me. 
Please correct me if I'm wrong on what's following.
The main and sub bands can be seen as 2 independant VFO's when not in
"split" (or satellite?) mode. But in "split" mode, one band is the
receive "channel" and the other one is the "transmit". If I read
correctly between the lines, on the IC910 in this setup, the main and sub
can not be both in the same freq "range" (VHF - VHF, UHF - UHF, SHF - SHF), 
so one has to be VHF and the other one UHF for example.
Question: how do you decide which band is receive, and wich one is
transmit?
Talking about your example (setting freq of 145.950, and main band on
70cm), do you know if you want to change the transmit or the receive
frequency or change the frequency of the 2m link?
In other words, how works you application?


> Note... these 2 examples are only for the IC910 - not for the other
> satellite radios. So, for every satellite radio I still need my satellite dependent
> code? I even don't know if the sub band is uplink or downlink on the different
> radios.

The goal of Hamlib is to hide the radio depdendant code in a library, 
such a way that the application has only to support only one ideal (somewhat
virtual) radio. An abstraction layer if you prefer.

My idea is that an application developer should concentrate on his
*application*, and not on writing code to support every remote control
protocol on earth.

> Note, this is not meant flaming about hamlib. Hamlib is a neat project, and
> the right direction for rig control - but in it's current state not really
> useable for satellite radios.

alright, let's make it useable!

BTW, do you plan to also use the rotator control piece in Hamlib?
There's much to do, but it'd be nice to identify some potential users
first :)

 
73,
Stephane