On Sun, 2003-02-23 at 20:36, Stephane Fillod wrote:
> 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 ?
Yes, I think that's a good idea. It would also be consistent with the
rest of the API having #defs for discrete values (like mode, agc, vfo).
In the mean time I leave this feature out.
> > 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.
I think a float specifying degrees per second would be better because
(correct me if I'm wrong, please):
1) rads/sec would always be small number
2) it is easier / we are used to think in degrees rather than in rads?
3) we already use degrees in rot_set/get_position (API doc: "unless
specified otherwise")
> And of course, the rotator caps are missing minimum and maximum speed
> fields (which will depend on the unit).
That would be very nice too.
Alex, OZ9AEC
|
