-
Notifications
You must be signed in to change notification settings - Fork 25
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
Standardization of Command Responses #118
Comments
First list: all of those (except RESET) were fixed in #115 Second list: Larger issue here of the |
Thanks for pointing that out! For the purpose of this issue I would just make FM_RESET_CMD_EID be informational/consistent with the rest of the commands. FM's use of a child task warning counter is a bit different than how some of the other apps work...but I think the implementation is straight forward enough/self explanatory that I don't think it is causing anyone any heartburn/issues. |
…esponses Fix #118, Standardize command responses
Checklist (Please check before submitting)
Is your feature request related to a problem? Please describe.
cFS should have standardized command responses for commands that set a state/mode like enable/disable, on/off, true/false, start/stop/pause/resume, etc.
For those commands, the app should respond as describe below:
The following command response does not align with the standard:
Successful commanding events are debug type:
The following failure events are of info type:
Describe the solution you'd like
Update logic to align with the standard.
Requester Info
Dan Knutsen
NASA Goddard
The text was updated successfully, but these errors were encountered: