Add a timestamp to raw Wiretapping upon reception #433

Open
opened 2021-06-14 15:20:26 +02:00 by gaisser · 1 comment
Owner

For ACS debugging a accurate timestamp is very useful. Especially for high frequency devices like gyros. This simplifies data analysis a lot.

For ACS debugging a accurate timestamp is very useful. Especially for high frequency devices like gyros. This simplifies data analysis a lot.
gaisser added the
feature
label 2021-06-14 15:20:26 +02:00
gaisser changed title from Timestamp RAW Wiretapping upon reception to Add a timestamp to raw Wiretapping upon reception 2021-06-14 15:22:40 +02:00
Owner

I 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.

I 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`.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fsfw/fsfw#433
No description provided.