Standardization of Command Responses

[dmknutsen]

Checklist (Please check before submitting)

• [x] I reviewed the Contributing Guide.
• [x] I reviewed the CF README.md file to see if the feature is in the major future work.
• [x] I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

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:

• If the current setting is not in that commanded state,

  1. If the commanded state can be set successfully, a. Increment the command counter b. Send an INFO event that says command successfully executed
  2. otherwise, a. Increment the command error counter b. Send an ERROR event that says failed to execute the command

• If the current setting is already in that commanded state,

  1. Increment the command counter, not command error counter
  2. Send an INFO event that says already in that state

The following command responses do not align with the standard: • For SUSPEND_CC and RESUME_CC - an error event is issued and the error cntr incremented when the state is set to the current state • For ENABLE_ENGINE - an error event is issued and the error counter incremented when the engine is already enabled • For DISABLE_ENGINE - an error event is issued and the error counter incremented when the engine is already disabled

Describe the solution you'd like Update logic to align with the standard.

Requester Info Dan Knutsen NASA Goddard