Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Singletrack UI slow if the rotor controller is slow to respond #108

Open
bjorgan opened this issue Nov 9, 2022 · 1 comment
Open

Singletrack UI slow if the rotor controller is slow to respond #108

bjorgan opened this issue Nov 9, 2022 · 1 comment
Assignees
@bjorgan
Labels
bug

Comments

@bjorgan
Copy link
Member

bjorgan commented Nov 9, 2022

Issue at LA1K station: The rotor controller often times out and is slow to respond, so the UI hangs since we always wait for the response of the last command before issuing a new rotor position. Ends up screwing up the doppler shift correction as well.

(Mentioned in #103 (comment))
@bjorgan bjorgan self-assigned this Nov 9, 2022
@bjorgan bjorgan added the bug label Nov 9, 2022
@bjorgan bjorgan mentioned this issue Nov 15, 2022
Merged
bjorgan added a commit that referenced this issue Nov 15, 2022
@bjorgan
Use non-blocking reads for rotctl track responses (#109)
15667b4 
Ref. #108: Flyby singletrack UI can
become unresponsive during tracking since we wait for confirmation of
the previous response before we try to set a new position.

These changes modify the socket read to be non-blocking, so that we can
return back to the UI loop when the full response is not available yet,
and still retain the mechanism with the previous response being required
before we are allowed to set a new position.

This does not fully solve #108 since
we will have an issue with the hamlib status windows, but I'll continue
on that in a different branch and merge this already now so that the
user experience can be improved.
@bjorgan
Copy link
Member Author

bjorgan commented Dec 6, 2022

Mostly fixed in #109, still missing improvements to the status window.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bjorgan bjorgan

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bjorgan