Skip to content

GP misses a beat #383

@aviatorhh

Description

@aviatorhh

Looking at the commands going to rotctld I can see that GP sends 4 commands with 1s in between and then pauses for one turn.

2025-12-13 17:13:25,281 ['P', '174.46', '0.00\n']
2025-12-13 17:13:25,281 moving to az:174.46 el: 0.0
2025-12-13 17:13:25,386 received data: b'p\n'
2025-12-13 17:13:25,431 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:26,135 received data: b'P 174,46 0,00\n'
2025-12-13 17:13:26,135 ['P', '174.46', '0.00\n']
2025-12-13 17:13:26,135 moving to az:174.46 el: 0.0
2025-12-13 17:13:26,240 received data: b'p\n'
2025-12-13 17:13:26,285 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:27,092 received data: b'p\n'
2025-12-13 17:13:27,125 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:27,931 received data: b'p\n'
2025-12-13 17:13:27,964 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:28,669 received data: b'P 174,46 0,00\n'
2025-12-13 17:13:28,669 ['P', '174.46', '0.00\n']
2025-12-13 17:13:28,669 moving to az:174.46 el: 0.0
2025-12-13 17:13:28,775 received data: b'p\n'
2025-12-13 17:13:28,819 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:29,524 received data: b'P 174,46 0,00\n'
2025-12-13 17:13:29,524 ['P', '174.46', '0.00\n']
2025-12-13 17:13:29,524 moving to az:174.46 el: 0.0
2025-12-13 17:13:29,630 received data: b'p\n'
2025-12-13 17:13:29,675 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:30,379 received data: b'P 174,46 0,00\n'
2025-12-13 17:13:30,379 ['P', '174.46', '0.00\n']
2025-12-13 17:13:30,379 moving to az:174.46 el: 0.0
2025-12-13 17:13:30,484 received data: b'p\n'
2025-12-13 17:13:30,529 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:31,231 received data: b'P 174,46 0,00\n'
2025-12-13 17:13:31,231 ['P', '174.46', '0.00\n']
2025-12-13 17:13:31,231 moving to az:174.46 el: 0.0
2025-12-13 17:13:31,333 received data: b'p\n'
2025-12-13 17:13:31,381 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:32,189 received data: b'p\n'
2025-12-13 17:13:32,221 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:33,029 received data: b'p\n'
2025-12-13 17:13:33,060 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:33,766 received data: b'P 174,46 0,00\n'
2025-12-13 17:13:33,766 ['P', '174.46', '0.00\n']
2025-12-13 17:13:33,766 moving to az:174.46 el: 0.0
2025-12-13 17:13:33,870 received data: b'p\n'
2025-12-13 17:13:33,916 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:34,618 received data: b'P 174,46 0,00\n'
2025-12-13 17:13:34,618 ['P', '174.46', '0.00\n']
2025-12-13 17:13:34,619 moving to az:174.46 el: 0.0
2025-12-13 17:13:34,720 received data: b'p\n'
2025-12-13 17:13:34,769 Received response: b'174.47\n' b'0.00\n'
2025-12-13 17:13:35,474 received data: b'P 174,46 0,00\n'

If you look at the lines coming in like ['P', '174.46', '0.00\n'] and their timestamps it is obvious.
In terms of functionality it is no big issue but irritates as the setting in the antenna tracking windows say like 1000ms (without pausing).

Gpredict 2.2.1

Thank you

Nicholas

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions