KSat/fsfw
18
6
Fork 0
forked from fsfw/fsfw
Code Issues Pull Requests 1 Releases Wiki Activity

spahr/handleRecoveryEvents #54

Merged
muellerr merged 5 commits from spahr/handleRecoveryEvents into main 2025-04-01 14:07:10 +02:00
Conversation 2 Commits 5 Files Changed 2 +13 -7
mspahr commented 2025-03-22 10:43:43 +01:00
Member
Copy Link

During the recovery of a device, a series of events is triggered to inform the operator about the progress of the recovery. To make the recovery progress more clear, I

  • added two new events (RECOVERY_WAITING and RECOVERY_RESTARTING)
  • removed old event RECOVERY_STEP because it's no longer needed
  • added the object Id of the recovering device as parameter to all events related to the recovery
Previous Events during Recovery New Events during Recovery
TRYING_RECOVERY (P1: objectId) TRYING_RECOVERY (P1: objectId)
RECOVERY_STEP (P1: 0) RECOVERY_WAITING (P1: objectId)
RECOVERY_STEP (P1: 1) RECOVERY_RESTARTING (P1: objectId)
RECOVERY_DONE RECOVERY_DONE (P1: objectId)
During the recovery of a device, a series of events is triggered to inform the operator about the progress of the recovery. To make the recovery progress more clear, I - added two new events (_RECOVERY_WAITING_ and _RECOVERY_RESTARTING_) - removed old event _RECOVERY_STEP_ because it's no longer needed - added the object Id of the recovering device as parameter to all events related to the recovery | Previous Events during Recovery | New Events during Recovery | | --- | --- | | TRYING_RECOVERY (P1: objectId) | TRYING_RECOVERY (P1: objectId) | | RECOVERY_STEP (P1: 0) | RECOVERY_WAITING (P1: objectId) | | RECOVERY_STEP (P1: 1) | RECOVERY_RESTARTING (P1: objectId) | | RECOVERY_DONE | RECOVERY_DONE (P1: objectId) |
mspahr added 4 commits 2025-03-22 10:43:43 +01:00
mspahr commented 2025-03-22 12:35:58 +01:00
Author
Member
Copy Link

I created a PR for the source-tmtc to update the events definitions accordingly, which I will merge after this.

I created a [PR for the source-tmtc](https://git.ksat-stuttgart.de/source/source-obdh_obsw/tmtc/-/merge_requests/74) to update the events definitions accordingly, which I will merge after this.
muellerr approved these changes 2025-04-01 14:06:29 +02:00
muellerr added 1 commit 2025-04-01 14:06:37 +02:00
muellerr merged commit daac5ea727 into main 2025-04-01 14:07:10 +02:00
muellerr deleted branch spahr/handleRecoveryEvents 2025-04-01 14:07:12 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
muellerr
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
ahinkel dwoodward fbalassa gaisser jgerhards lrajer mdemke meierj mluz mohr msenger mspahr mtompert muellerr nehlichp phoffmann PScheurenbrand taheran tbaumgartl
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KSat/fsfw#54
No description provided.
Delete Branch "spahr/handleRecoveryEvents"

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?