-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
create CFE_TIME_PrintFmt(); #2316
Open
Labels
Comments
2 tasks
CDKnightNASA
added a commit
to CDKnightNASA/cFE
that referenced
this issue
May 24, 2023
…E_StringFmt() and CFE_TIME_StringFmtLen() functions
2 tasks
Issue is being re-opened to address in Equuleus-rc2. |
This was
linked to
pull requests
Jul 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently the
CFE_TIME_Print()
function only producesYYYY-ddd HH:MM:SS.xxxx
formatted timestamps. CFE_EVS now uses that for stdout messages, which adds quite a lot of text.Describe the solution you'd like
I suggest the addition of a new
CFE_TIME_PrintFmt()
function, a-lastrftime
(preferably usingstrftime
, if that is available on all our target platforms) so that applications can produce a time-only format, for example.Additionally, I suggest a "T+" format for such things as EVS stdout output where the first report is the full timestamp for "T0" and all subsequent messages are the number of seconds (
SS.xxxx
) after the T0 epoch for even more storage efficiency and readability.Once this capability is created, EVS should be modified to allow configuring the format.
Describe alternatives you've considered
Another option is to use something other than
CFE_TIME_Print()
in EVS_SendViaPorts().Additional context
See the related PR #2295
Requester Info
Christopher.D.Knight@nasa.gov
The text was updated successfully, but these errors were encountered: