Add Small Event Support #18

muellerr · 2022-10-23T18:39:48+02:00

muellerr commented

2022-10-23 18:39:48 +02:00

Adds support for small events where the raw representation only spans two bytes.

When it comes to TM downlink, minimizing the size of the received telemetry is always something worth considering. Adding a small event type allows to make all PUS event telemetry packets smaller.

Having a limit of around 70-80 group IDs and up to 255 events for each group ID should also be sufficient for many missions.

Further roadmap:

Parameterize the Event types for all Severity Variants. This would allow for creating type-safe event APIs which can only process events of a certain severity.
Look into introspection and other ways to make supplying human readable data for events and for MIBs as conveniently as possible. It would be great if no additional code parser is needed. For an info string, an appropriate associated function for EventProvider could be used. For the event name itself, this is actually tricky without a code parser and would probably require a macro. Maybe stringify can be used in some way? This is a good starting point to try creating a static library which can be consumed to retrieve MIB values or an event list CSV.

Adds support for small events where the raw representation only spans two bytes. When it comes to TM downlink, minimizing the size of the received telemetry is always something worth considering. Adding a small event type allows to make all PUS event telemetry packets smaller. Having a limit of around 70-80 group IDs and up to 255 events for each group ID should also be sufficient for many missions. Further roadmap: - Parameterize the Event types for all Severity Variants. This would allow for creating type-safe event APIs which can only process events of a certain severity. - Look into introspection and other ways to make supplying human readable data for events and for MIBs as conveniently as possible. It would be great if no additional code parser is needed. For an info string, an appropriate associated function for `EventProvider` could be used. For the event name itself, this is actually tricky without a code parser and would probably require a macro. Maybe `stringify` can be used in some way? This is a good starting point to try creating a static library which can be consumed to retrieve MIB values or an event list CSV.

muellerr added 5 commits 2022-10-23 18:39:53 +02:00

add small event impl b7dbeb2dfd

cargo fmt 3ffbd3697e

severity only uses two bits now b26703e0a9

trying to make this generic 2004155b7b

small event support complete dd2929eb98

muellerr merged commit afc094e77a into main

2022-10-23 18:41:14 +02:00

muellerr referenced this issue from a commit

2022-10-23 18:41:14 +02:00

Merge pull request 'Add Small Event Support' (#18) from mueller/continue-event-pus-manager into main

muellerr deleted branch mueller/continue-event-pus-manager