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
Is your feature request related to a problem? Please describe.
Currently, the CFE_SB_TransmitMsg() API has a second parameter, to update the sequence count of the outgoing message.
This was a bit short-sighted because the MSG headers are user-configurable (via customizing the MSG module) ... it is possible that there is more than just a Sequence Count that needs to be maintained. If users can add custom header fields, this hook needs to be more generic to update other headers.
Describe the solution you'd like
Generalize the boolean to mean "Update Headers" (thus not limited to a sequence count). This would include a sequence count, of course, to not break existing code.
Additional context
Other headers that could conceivably be updated, if applicable to the message being sent:
Timestamp
Checksum/error control field
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
This overlaps/supercedes my old issue #1157 ... which was similar in the sense that the boolean on this function was oddly implemented and too limited in nature.
Expand the "Increment Sequence" boolean on transmit message functions to
be a more general "Update Header" boolean, so it can be used for other
fields like timestamps, checksums, or user-defined fields too.
Is your feature request related to a problem? Please describe.
Currently, the CFE_SB_TransmitMsg() API has a second parameter, to update the sequence count of the outgoing message.
This was a bit short-sighted because the MSG headers are user-configurable (via customizing the MSG module) ... it is possible that there is more than just a Sequence Count that needs to be maintained. If users can add custom header fields, this hook needs to be more generic to update other headers.
Describe the solution you'd like
Generalize the boolean to mean "Update Headers" (thus not limited to a sequence count). This would include a sequence count, of course, to not break existing code.
Additional context
Other headers that could conceivably be updated, if applicable to the message being sent:
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: