XTCE12 — Put Alarms in Arguments; leaves Alarms in Command Parameters

Description Kevin Rice 2007-10-22 21:17:55 BST
Command Argument should have alarms; I have found one user that claims alarms
on USER INPUT arguments. Therefore I believe we should generalize the schema
to having them both in parameters and arguments. In the end I believe we'll be
making arguments and parameters look exactly the same even if the nomenclature
stays separate.
Comment 1 Kevin Rice 2007-10-22 21:20:06 BST
Command Argument should have alarms; I have found one user that claims alarms
on USER INPUT arguments. Therefore I believe we should generalize the schema
to having them both in parameters and arguments. In the end I believe we'll be
making arguments and parameters look exactly the same even if the nomenclature
stays separate.

Not essential to definition exchange

Command arguments are typically associated with operator entry of a command request, or a scripted command request. XTCE Command argument definitions may include a valid range which would define for the ground system the invalid range to reject at command request time. This rejection is not the same as a valid alarm, and the action that the ground system takes when it receives an invalid argument value is system-dependent, but should result in the rejection of the command request.