DHB: Extra PST step #129
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#129
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Maybe I understood something wrong, but I have a qeustion concerning the Polling Sequence Table (PST) for Device handler base (DHB).
If I understood correctly, if there is a device like a gyro which is polled very frequently to satisfy some physical criteria, this is performed in the PST by adding mutliple SEND_READ, GET_READ ... steps in the PST.
But if I see it correctly, SEND_READ does two things here: It performs the communicatinon part (doSendRead()) and also the periodic part of the device handler (e.g. message handling):
Is there a specific reason why the periodic part is not a distinct PST step, for example PERIODIC_OPERATION ?
Part of #281
Part of #281