Add a timestamp to raw Wiretapping upon reception #433
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#433
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
For ACS debugging a accurate timestamp is very useful. Especially for high frequency devices like gyros. This simplifies data analysis a lot.
Timestamp RAW Wiretapping upon receptionto Add a timestamp to raw Wiretapping upon receptionI would like to avoid having two timestamps in the resulting TM packet.
A solution I was thinking about earlier was to extend the TM protocol, ie
TmTcMessage
to carry an optional timestamp. This timestamp, if present, could be used to initialize the timestamp of the actual TM packet.Writing this, it would probably be not much problem to always set the timestamp in the
TmTcMessage
.