Local Data Pool #14

Open
opened 2022-08-29 10:58:16 +02:00 by muellerr · 0 comments
Owner

This issue is tightly related to rust/fsrc-launchpad#13.

The FSFW offers a good way to expose data pool in a distributed manner and then allows grouping them into data sets which can be used by other SW components or packages as housekeeping telemetry directly.

It would be good if the same was possible for Rust. The data set aspect is tightly coupled to the custom packet format issue.

Exposing a pool structure which could be re-used by other SW components (e.g. read single pool variables) is actually a bit more tricky.

One possible way, assuming a std runtime would be to wrap shared pool variables into an Arc<Mutex>> so they can be used by

  1. Other SW components, which simply get an Arc<Mutex>> to that variable, but maybe read-only
  2. Datasets which contain that variable get the variable wrapped inside an Arc<Mutex>> as well.
This issue is tightly related to https://egit.irs.uni-stuttgart.de/rust/fsrc-launchpad/issues/13. The FSFW offers a good way to expose data pool in a distributed manner and then allows grouping them into data sets which can be used by other SW components or packages as housekeeping telemetry directly. It would be good if the same was possible for Rust. The data set aspect is tightly coupled to the [custom packet format](https://egit.irs.uni-stuttgart.de/rust/fsrc-launchpad/issues/13) issue. Exposing a pool structure which could be re-used by other SW components (e.g. read single pool variables) is actually a bit more tricky. One possible way, assuming a std runtime would be to wrap shared pool variables into an `Arc<Mutex>>` so they can be used by 1. Other SW components, which simply get an `Arc<Mutex>>` to that variable, but maybe read-only 2. Datasets which contain that variable get the variable wrapped inside an `Arc<Mutex>>` as well.
muellerr added the
concepts
label 2022-08-29 10:58:16 +02:00
muellerr added this to the satrs v0.1.0 milestone 2023-09-01 23:40:09 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 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#14
No description provided.