You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Crucially, the endianness of the time field in the telemetry header is only documented as a source code comment. There was a similar ambiguity with the command header, but this was resolved with nasa/cFE#297. Is cFS planning to register the header formats with SANA? If not, will the EDS describing this interface specify endianness?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Per CCSDS 133.0-B-2, the CCSDS secondary header fields are mission specific, but are registered with SANA. At the link provided in the reference (https://sanaregistry.org/r/space_packet_protocol_secondary_header_format_document/), I do not see any entries for either the cFE Telemetry or Command packet secondary headers.
Crucially, the endianness of the time field in the telemetry header is only documented as a source code comment. There was a similar ambiguity with the command header, but this was resolved with nasa/cFE#297. Is cFS planning to register the header formats with SANA? If not, will the EDS describing this interface specify endianness?
Beta Was this translation helpful? Give feedback.
All reactions