You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is maybe over year since I have last played with rotctld. Using rotor
Dummy #1 is a good second choice as there are not so many rotors to test
with.
If I do remember right issuing P or M command has made Dummy to "turn"
slowly so that one can see what happens with CO program while polling
rigctld.
At the moment (rotctl(d), Hamlib 4.4~git su marras 07 14:21:54 2021
+0000 SHA=41ebbb) issuing P or M causes Dummy to jump immediately to
given position, or to end of turn. With M the speed value seems to be
useless, too (actually I do not remember did it ever work) but P did
cause slowly changing reading.
Is this delay loop removed in purpose from Dummy rotator?
--
Saku
OH1KH
The text was updated successfully, but these errors were encountered:
It is maybe over year since I have last played with rotctld. Using rotor
Dummy #1 is a good second choice as there are not so many rotors to test
with.
If I do remember right issuing P or M command has made Dummy to "turn"
slowly so that one can see what happens with CO program while polling
rigctld.
At the moment (rotctl(d), Hamlib 4.4~git su marras 07 14:21:54 2021
+0000 SHA=41ebbb) issuing P or M causes Dummy to jump immediately to
given position, or to end of turn. With M the speed value seems to be
useless, too (actually I do not remember did it ever work) but P did
cause slowly changing reading.
Is this delay loop removed in purpose from Dummy rotator?
--
Saku
OH1KH
The text was updated successfully, but these errors were encountered: