DHB Reply Timeout #637
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#637
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "meier/dhbReplyTimeout"
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?
DHB Reply Timeoutto WIP: DHB Reply TimeoutWIP: DHB Reply Timeoutto DHB Reply Timeout@ -431,1 +447,4 @@
info.command = deviceCommandMap.end();
info.countdown = countdown;
if (info.periodic) {
info.active = true;
So far, convention is that periodic packets are disabled by default and need to be exlpicitely enabled. See
info.delayCycles = 0;
above.@ -962,6 +1002,10 @@ ReturnValue_t DeviceHandlerBase::enableReplyInReplyMap(DeviceCommandMap::iterato
info->delayCycles = info->maxDelayCycles;
please add a comment, that both delay Cycles as well as the countdown are set if a countdown is preset, but the countdown will take precedence.
@ -448,6 +448,9 @@ class DeviceHandlerBase : public DeviceHandlerIF,
* by the device repeatedly without request) or not. Default is aperiodic (0).
* Please note that periodic replies are disabled by default. You can enable them with
* #updatePeriodicReply
updatePeriodicReply
needs to be adapted, too.Also, dude, you wrote a DHB unit test (add exploding head emoji, it seems gitea can not handle unicode..)
As I think it is faster than writing about it, I took the liberty to add my remaining comments directly as code.
@meierj if you agree with my changes, feel free to add a positive review and merge this PR.
Also, I think we should remove the delay based solution completely some time in the future. The countdown based one is nicer and having both gives not exactly beautiful code.
I am working on refactoring the command/reply API anyway, it has become bloated up a bit.