Re: [Hamlib-developer] Problem with rotctl

[Eric S. <wb...@sb...>]

Hello Team

Back in March I requested some help with interfacing Gpredict with Hamlib.
With some advice from Nate I have progressed up to another plateau. The goal
is to track LEO sats at X band with accuracy > 0.1 deg. I am using the
Arduino platform running K3NG code. The rotctld interface is EasycommII.
GS-232B is a possibility but accuracy is limited. My problem is that
Gpredict will control the rotor but reports AZ 000.00 and EL 000.00.

rotctl is querying GS232 (603 rotor) az & el correctly  AZ=358EL=054.


C:\Program Files (x86)\hamlib-win32-1.2.15.3\bin>rotctl -vvvvv -r COM8 -m
603 p
rotctl, Hamlib 1.2.15.3
Report bugs to <ham...@li...>

rot:rot_init called
rot: loading backend gs232a
initrots2_gs232a called
rot_register (601)
rot_register (603)
rot_register (602)
rot_register (604)
rot:rot_open called
Opened rot model 603, 'GS-232B'
Backend version: 0.2, Status: Beta
gs232b_rot_get_position called
write_block(): TX 3 bytes
0000    43 32 0d                                            C2.
read_string(): RX 13 characters
0000    41 5a 3d 33 35 38 45 4c 3d 30 35 34 0d              AZ=358EL=054.
gs232b_rot_get_position: (az, el) = (358.0, 4.0)
358.000000
4.000000
rot:rot_close called
rot:rot_cleanup called



rotctl querying Easycomm 2 (202 rotor) az & el incorrectly  0000    21     !


           
C:\Program Files (x86)\hamlib-win32-1.2.15.3\bin>rotctl -vvvvv -r COM8 -m
202 p
rotctl, Hamlib 1.2.15.3
Report bugs to <ham...@li...>

rot:rot_init called
rot: loading backend easycomm
initrots2_easycomm called
rot_register (201)
rot_register (202)
rot:rot_open called
Opened rot model 202, 'EasycommII'
Backend version: 0.3, Status: Beta
easycomm_rot_get_position called
write_block(): TX 1 bytes
0000    21                                                  !
read_string(): Timed out 0.300000 seconds without reading a character.
get_pos: error = Communication timed out
rot:rot_close called
rot:rot_cleanup called

rotctl reports  "Can get Position:       Y"

C:\Program Files (x86)\hamlib-win32-1.2.15.3\bin>rotctl -vvvvv -r COM8 -m
603 -u

rotctl, Hamlib 1.2.15.3
Report bugs to <ham...@li...>

rot:rot_init called
rot: loading backend easycomm
initrots2_easycomm called
rot_register (201)
rot_register (202)
Caps dump for model:    202
Model name:             EasycommII
Mfg name:               Hamlib
Backend version:        0.3
Backend copyright:      LGPL
Backend status:         Beta
Rot type:               Other
Port type:              RS-232
Serial speed:           9600..19200 bauds, 8N1
Write delay:            0mS, timeout 200mS, 3 retries
Post Write delay:       0mS
Min Azimuth:            0.00
Max Azimuth:            360.00
Min Elevation:          0.00
Max Elevation:          180.00
Has priv data:          N
Has Init:               N
Has Cleanup:            N
Has Open:               N
Has Close:              N
Can set Conf:           N
Can get Conf:           N
Can set Position:       Y
Can get Position:       Y
Can Stop:               Y
Can Park:               Y
Can Reset:              Y
Can Move:               Y
Can get Info:           N

Overall backend warnings: 0
rot:rot_cleanup called

The EasycommII protocol In WISP is not perfectly clear on how to get the
rotor position other that to state that a command without a value will
return the value.  So AZ will return AZxxx.x and EL will return ELxxx.x
This is how the K3NG code works.

Has anyone successfully read back from 202 with rotctl? Anybody have
suggestions on where to go from here? Getting all these software legos to
play nice is really tough.

Eric
WB6KCN