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

Arming and actuator state telemetry #13

Open
linguini1 opened this issue Oct 2, 2024 · 1 comment
Open

Arming and actuator state telemetry #13

linguini1 opened this issue Oct 2, 2024 · 1 comment
Assignees

Comments

@linguini1
Copy link
Contributor

The hybrid communication specification requires that arming states and actuator states be sent as telemetry packets whenever a change to them occurs. This needs to be implemented in the pad server.

In addition, the pad server implementation should broadcast states periodically on a timer to cover scenarios where:

  • There are lost packets
  • The connection is momentarily interrupted
  • New telemetry clients join the multicast group and need to be informed of the current state
@bskdany bskdany self-assigned this Oct 7, 2024
@bskdany
Copy link
Contributor

bskdany commented Oct 10, 2024

This issue is blocked by #10

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

2 participants