Open wose opened 3 years ago
Increasing the polling interval didn't help in this case. We should:
The hamlib part seems ok to me. They forward any error during communication with the rotator as IO Error and swallow errno
, which could hold more information on what's happening. The documentation of the rotator implementation states polling the position during movement is ok and it's also synchronized between all clients.
@AdamKrovina: You could try to set additional parameters for hamlib in satnogs-setup -> Advanced -> Hamlib -> HAMLIB_UTILS_ROT_OPTS
. Something like -vvvvv
should give you more logs, and also print errno
. Not sure we can do anything about it though.
Originally posted by @AdamKrovina in https://github.com/wose/satnogs-monitor/issues/26#issuecomment-833023441