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.

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

Antenna Rotor Control #121

Open
Gustyarte opened this issue Dec 8, 2023 · 3 comments
Open

Antenna Rotor Control #121

Gustyarte opened this issue Dec 8, 2023 · 3 comments

Comments

@Gustyarte
Copy link

Thank you very much for such an excellent application; it is truly beautiful and accurate so far!

I would like to report that the commands for controlling an antenna rotor are not the same as Gpredict. Therefore, the rotor does not respond to the commands or executes them incorrectly. For example, in Gpredict, the command sent is P 114.80 14.00, while in your application, it is set_pos 114.8 14.0. This subtle difference (at least the one I observed) causes it not to work.

I'm not sure if there is a standard for the rotctl protocol, but I would love to be able to use your application instead of a computer.

Thank you!

@EeeLo
Copy link

EeeLo commented Dec 9, 2023

You can just edit the control file to change that

@rt-bishop
Copy link
Owner

Hey @Gustyarte! I'm sorry for such a slow response. According to ROTCTL docs both short and long command names should be fine to use, so I never thought it can lead to an issue. But you're right, GPredict uses the short naming convention, which I somehow overlooked. I should probably change that just so both apps are aligned.

@rt-bishop
Copy link
Owner

Hey @Gustyarte. In the recent build v3.1.4 I've aligned the rotctl command with what's being sent by Gpredict, so in your case it should work out of the box. It's currently being reviewed by Google. Hopefully it won't break anyone else's implementation =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants