Standardization of Command Responses

[dmknutsen]

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I reviewed the README file to see if the feature is in the major future work.
• 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,
    If the commanded state can be set successfully,
    a. Increment the command counter
    b. Send an INFO event that says command successfully executed
    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,
    Increment the command counter, not command error counter
    Send an INFO event that says already in that state

The following command response does not align with the standard:

The following success events are debug type:

SC_RESET_DEB_EID
SC_DISABLE_RTS_DEB_EID
SC_ENABLE_RTS_DEB_EID
SC_CONT_CMD_DEB_EID

SC_JUMP_ATS_CC command issues 2 success events, consider combining:

 SC_JUMPATS_CMD_LIST_INF_EID
 SC_JUMP_ATS_INF_EID

SC_MANAGE_TABLE_CC command does not issue success events in all success cases.

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

Requester Info
Dan Knutsen
NASA Goddard