[Hamlib-developer] Proper API implementation for Rotor-EZ

[Nate B. <n0...@ne...>]

When I implemented the rotorez backend I consolidated the rotor aiming
and rotating commands into rot_set_position.  I have a feeling this may 
be the wrong way to do it based on another reading of the API.

In my current implementation there is no use for the rot_move function.
As it is currently structured that when rot_set_position is called the
azimuth value is checked and then the command string is created and sent
to the rotor interface.  Next, the command to actually move the rotor to
the desired position is sent.

However, the Rotor-EZ and DCU-1 (Hy-Gain) interfaces do not support what
I gather to be the rot_move function's idea of direction (CW, CCW, Up or
Down) nor a rotational speed.  So, to use rot_move any passed values
would be ignored and a static command sent to the interface.

So, what is the intent of the API?  Is the application code expected to 
call rot_set_position and then rot_move for positioning to actually occur?
I see that fodtrack uses just rot_set_position while easycomm uses
rot_move.  So, whichever why I go will set a 2 to 1 preference.

I'd be happy to add comments to rotator.c to make this more clear.  :-)

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "We have awakened a
 Internet | n0...@ne...               | sleeping giant and
 Location | Bremen, Kansas USA EM19ov           | have instilled in him
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamamoto