Re: [Hamlib-developer] Rotator API

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

On Mon, Feb 17, 2003, Alexandru Csete wrote:
> I am currently adding rotator support to grig and I have a couple of
> questions to the rotator API. First, the rot_reset function needs an
> integer parameter besides the usual *rot structure. What is the purpose
> of this integer? The API says it's "The reset operation to perform" but
> what are the choices? Is there a "safe, universal value"?

So far, there's no such backend paying attention to this parameter. 
However, in the future, some backend will.
What about a safe ROT_RESET_ALL define ?

> Second, the rot_move function needs to know the speed, which can be
> between 1..100. Does the speed have a physical unit, or is the value
> specific to the back end?

This speed arg is broken. Let's fix it. 
First, it should not be specific to a backend, and next, it should have a
physical unit. What about a float for radian per second?
I don't have a computer-controlled rotator, so if anyone of you have
a better unit, please stand up.

And of course, the rotator caps are missing minimum and maximum speed
fields (which will depend on the unit).

Any idea?


Stephane