dhb multiple replies support #416
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#416
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "eive/fsfw:meier/multipleRepliesDhb"
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?
Fixes #405
Implemented appraoch 3
@ -309,2 +309,4 @@
Clock::getUptime(¤tUptime);
if (currentUptime - timeoutStart >= childTransitionDelay) {
#if FSFW_VERBOSE_LEVEL >= 1
char printout[60];
This information is part of the event below (Line 319), which is printed as debug output as well. Is there a special reason to print it twice?
It is not printed if
FSFW_OBJ_EVENT_TRANSLATION == 0
. I suggest to change#if FSFW_VERBOSE_LEVEL >= 1
to#if FSFW_VERBOSE_LEVEL >= 1 && FSFW_OBJ_EVENT_TRANSLATION == 0
This is something I wrote and we decided to keep it in there because it's a useful printout
Ok, than we keep it but I disagree with the comment:
/* Very common configuration error, so print it */
This happens in flight as well if your device does not respond, which happens from time to time for radiation.
I think the second one is a good idea. Otherwise you will just spam your console with duplicate information.