Sync Schedule #200

Open
opened 2024-06-17 11:45:45 +02:00 by lkoester · 1 comment
Member

In order to optimize ergonomics while controlling a spacecraft such as a satellite remotely via a PUS-like infrastructure, it would be beneficial to have a way to synchronize execution schedules between satellite onboard-software and ground control software. Currently, the foundation for this is implemented in sat-rs by means of PUS Service 11 (time-based scheduling). Most of the work to go from a stack-based commanding to a more abstracted commanding using a synchronized schedule needs to be done on the ground-side; however, a couple of adjustments need to be made to the onboard-software framework as well:

  • Addition of scheduling reports (summary as a specified by TM[11,13] or detail as specified by TM[11,10]) to allow for more precise monitoring of the onboard schedule
In order to optimize ergonomics while controlling a spacecraft such as a satellite remotely via a PUS-like infrastructure, it would be beneficial to have a way to synchronize execution schedules between satellite onboard-software and ground control software. Currently, the foundation for this is implemented in sat-rs by means of PUS Service 11 (time-based scheduling). Most of the work to go from a stack-based commanding to a more abstracted commanding using a synchronized schedule needs to be done on the ground-side; however, a couple of adjustments need to be made to the onboard-software framework as well: - Addition of scheduling reports (summary as a specified by TM[11,13] or detail as specified by TM[11,10]) to allow for more precise monitoring of the onboard schedule
lkoester added the
concepts
label 2024-06-17 11:45:45 +02:00
lkoester self-assigned this 2024-06-17 11:45:45 +02:00
Owner

Sounds like a feature which could be implemented in a reasonable time frame. When it comes to the core scheduler API, a reference/range to the internal BTreeMap could probably be used to create those reports.

Sounds like a feature which could be implemented in a reasonable time frame. When it comes to the core scheduler API, a reference/range to the internal BTreeMap could probably be used to create those reports.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: rust/sat-rs#200
No description provided.