WIP: CFDP Router and CFDP Handlers #662
No reviewers
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
Reference: fsfw/fsfw#662
Loading…
Reference in New Issue
No description provided.
Delete Branch "mueller/cfdp-routers"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Builds on top of #655
This PR introduces improvements and unittests for the TMTC routing stack of the FSFW.
It will also introduce the CFDP router component which will be able to route CFDP packet in both source to destination direction and vice-versa.
UPDATE: Change architecture to be similar to how PUS packets are handled: There is a distributor instead of a router which contains a list of valid CFDP entities which can received PDUs. These entities send their generated TM to an object implementing
AcceptsTelemetryIF
instead of sending them to the router.UPDATE2: Oof, thats a large PR again. Will look into splitting it up a bit..
CFDP Routersto CFDP RouterCFDP Routerto WIP: CFDP RouterWIP: CFDP Routerto WIP: CFDP Router and CFDP HandlersI will package the destination (and possible the source handler) into a separate PR because those are complex classes with state machines. Time constraints only permit a minimal implementation with minimal or insufficient error handling for framework quality standards, so those might require additional work before they are merged here.
Replaced with smaller PRs
Pull request closed