Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
This project contains software to support the Object Management Group (OMG) Space Domain Task Force (SDTF) maintained XML Telemetry and Command Exchange (XTCE) specification.
A type definition used as the base type for a CommandDefinition
source
<complexType name="MetaCommandType" mixed="false"> <annotation> <documentation xml:lang="en">A type definition used as the base type for a CommandDefinition</documentation> </annotation> <complexContent> <extension base="xtce:NameDescriptionType"> <sequence> <element name="BaseMetaCommand" minOccurs="0"> <annotation> <documentation xml:lang="en">The MetaCommand is derived from this Base. Arguments of the base MetaCommand are further specified.</documentation> </annotation> <complexType> <sequence> <element name="ArgumentAssignmentList" minOccurs="0"> <complexType> <sequence> <element name="ArgumentAssignment" maxOccurs="unbounded"> <complexType> <attribute name="argumentName" type="xtce:NameReferenceType" use="required"/> <attribute name="argumentValue" type="string" use="required"/> </complexType> </element> </sequence> </complexType> </element> </sequence> <attribute name="metaCommandRef" type="xtce:NameReferenceType" use="required"/> </complexType> </element> <element name="SystemName" type="string" minOccurs="0"> <annotation> <documentation xml:lang="en">Optional. Normally used when the database is built in a flat, non-hierarchical format</documentation> </annotation> </element> <element name="ArgumentList" minOccurs="0"> <annotation> <documentation xml:lang="en">Many commands have one or more options. These are called command arguments. Command arguments may be of any of the standard data types. MetaCommand arguments are local to the MetaCommand.</documentation> </annotation> <complexType> <choice maxOccurs="unbounded"> <element name="Argument" maxOccurs="unbounded"> <annotation> <appinfo>Need to ensure that the named types actually exist</appinfo> </annotation> <complexType> <complexContent> <extension base="xtce:NameDescriptionType"> <attribute name="argumentTypeRef" type="xtce:NameReferenceType" use="required"/> <attribute name="initialValue" type="string"> <annotation> <documentation xml:lang="en">Used to set the initial calibrated values of Arguments. Will overwrite an initial value defined for the ArgumentType. For integer types base 10 (decimal) form is assumed unless: if proceeded by a 0b or 0B, value is in base two (binary form, if proceeded by a 0o or 0O, values is in base 8 (octal) form, or if proceeded by a 0x or 0X, value is in base 16 (hex) form. Floating point types may be specified in normal (100.0) or scientific (1.0e2) form. Time types are specified using the ISO 8601 formats described for XTCE time data types. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. Initial values for Array or Aggregate types may not be set.</documentation> </annotation> </attribute> </extension> </complexContent> </complexType> </element> </choice> </complexType> </element> <element name="CommandContainer" type="xtce:CommandContainerType" minOccurs="0"> <annotation> <documentation xml:lang="en">Tells how to package this command, for example in a packet or minor frame. This element is not visible to SequenceContainer in ContainerSet or CommandContainerSet. It may not be a ContainerRefEntry in another construct but it may be in a BaseContainer in another MetaCommand/CommandContainer.</documentation> </annotation> </element> <element name="TransmissionConstraintList" minOccurs="0"> <annotation> <documentation xml:lang="en">Appended to the TramsmissionConstraint List of the base command. Constraints are checked in order. </documentation> </annotation> <complexType> <sequence> <element name="TransmissionConstraint" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">A CommandTransmission constraint is used to check that the command can be run in the current operating mode and may block the transmission of the command if the constraint condition is true.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:MatchCriteriaType"> <attribute name="timeOut" type="xtce:RelativeTimeType"> <annotation> <documentation xml:lang="en">Pause during timeOut, fail when the timeout passes</documentation> </annotation> </attribute> <attribute name="suspendable" type="boolean" default="false"> <annotation> <documentation xml:lang="en">Indicates whether the constraints for a Command may be suspended.</documentation> </annotation> </attribute> </extension> </complexContent> </complexType> </element> </sequence> </complexType> </element> <element name="DefaultSignificance" type="xtce:SignificanceType" minOccurs="0"> <annotation> <documentation xml:lang="en">Some Command and Control Systems may require special user access or confirmations before transmitting commands with certain levels. The level is inherited from the Base MetaCommand.</documentation> </annotation> </element> <element name="ContextSignificanceList" minOccurs="0"> <annotation> <documentation xml:lang="en">Used when the significance (possible consequence) of a command varies by the operating context</documentation> </annotation> <complexType> <sequence> <element name="ContextSignificance" maxOccurs="unbounded"> <complexType> <sequence> <element name="ContextMatch" type="xtce:MatchCriteriaType"/> <element name="Significance" type="xtce:SignificanceType"/> </sequence> </complexType> </element> </sequence> </complexType> </element> <element name="Interlock" minOccurs="0"> <annotation> <documentation xml:lang="en">An Interlock is a type of Constraint, but not on Command instances of this MetaCommand; Interlocks apply instead to the next command. An Interlock will block successive commands until this command has reached a certain stage (through verifications). Interlocks are scoped to a SpaceSystem basis.</documentation> </annotation> <complexType> <attribute name="scopeToSpaceSystem" type="xtce:NameReferenceType"> <annotation> <documentation xml:lang="en">The name of a SpaceSystem this Interlock applies to. By default, it only applies to the SpaceSystem that contains this MetaCommand.</documentation> </annotation> </attribute> <attribute name="verificationToWaitFor" type="xtce:VerifierEnumerationType" default="complete"/> <attribute name="verificationProgressPercentage" type="decimal"> <annotation> <documentation xml:lang="en">Only applies when the verificationToWaitFor attribute is 'queued' or 'executing'.</documentation> </annotation> </attribute> <attribute name="suspendable" type="boolean" default="false"> <annotation> <documentation xml:lang="en">A flag that indicates that under special circumstances, this Interlock can be suspended.</documentation> </annotation> </attribute> </complexType> </element> <element name="VerifierSet" minOccurs="0"> <annotation> <documentation xml:lang="en">A Command Verifier is a conditional check on the telemetry from a SpaceSystem that that provides positive indication on the processing state of a command. There are eight different verifiers each associated with difference states in command processing: TransferredToRange, TransferredFromRange, Received, Accepted, Queued, Execution, Complete, and Failed. There may be multiple ‘complete’ verifiers. ‘Complete’ verifiers are added to the Base MetaCommand ‘Complete’ verifier list. All others will overide a verifier defined in a Base MetaCommand. </documentation> </annotation> <complexType> <sequence> <element name="TransferredToRangeVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">Transferred to range means the command has been received to the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="SentFromRangeVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">Sent from range means the command has been transmitted to the spacecraft by the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="ReceivedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that simply means the SpaceSystem has received the command.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="AcceptedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that means the SpaceSystem has accepted the command</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="QueuedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifer that means the command is scheduled for execution by the SpaceSystem.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="ExecutionVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that indicates that the command is being executed. An optional Element indicates how far along the command has progressed either as a fixed value or an (possibly scaled) ParameterInstance value.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"> <sequence minOccurs="0"> <element name="PercentComplete" type="xtce:DecimalValueType"> <annotation> <documentation>Values should be from 0 to 100</documentation> </annotation> </element> </sequence> </extension> </complexContent> </complexType> </element> <element name="CompleteVerifier" minOccurs="0" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">A possible set of verifiers that all must be true for the command be considered completed. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"> <sequence minOccurs="0"> <element name="ReturnParmRef" type="xtce:ParameterRefType"/> </sequence> </extension> </complexContent> </complexType> </element> <element name="FailedVerifier" type="xtce:CommandVerifierType" minOccurs="0"> <annotation> <documentation xml:lang="en">When true, indicates that the command failed. timeToWait is how long to wait for the FailedVerifier to test true.</documentation> </annotation> </element> </sequence> </complexType> </element> <element name="ParameterToSetList" minOccurs="0"> <annotation> <documentation xml:lang="en">Parameters that are set with a new value after the command has been sent. Appended to the Base Command list</documentation> </annotation> <complexType> <sequence> <element name="ParameterToSet" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">Sets a Parameter to a new value (either from a derivation or explicitly) after the command has been verified (all verifications have passed)</documentation> <appinfo>Value type must match Parameter type</appinfo> </annotation> <complexType> <complexContent> <extension base="xtce:ParameterRefType"> <choice> <element name="Derivation"> <annotation> <documentation>Result of the MathOperation will be the new Parameter value</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:MathOperationType"/> </complexContent> </complexType> </element> <element name="NewValue" type="string"/> </choice> <attribute name="setOnVerification" type="xtce:VerifierEnumerationType" default="complete"/> </extension> </complexContent> </complexType> </element> </sequence> </complexType> </element> <element name="ParametersToSuspendAlarmsOnSet" minOccurs="0"> <annotation> <documentation xml:lang="en">Sometimes it is necessary to suspend alarms - particularly 'change' alarms for commands that will change the value of a Parameter</documentation> </annotation> <complexType> <sequence> <element name="ParameterToSuspendAlarmsOn" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">Will suspend all Alarms associated with this Parameter for the given suspense time after the given verifier</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:ParameterRefType"> <attribute name="suspenseTime" type="xtce:RelativeTimeType" use="required"/> <attribute name="verifierToTriggerOn" type="xtce:VerifierEnumerationType" default="release"/> </extension> </complexContent> </complexType> </element> </sequence> </complexType> </element> </sequence> <attribute name="abstract" type="boolean" default="false"/> </extension> </complexContent> </complexType>
Optional. Normally used when the database is built in a flat, non-hierarchical format
source
<element name="SystemName" type="string" minOccurs="0"> <annotation> <documentation xml:lang="en">Optional. Normally used when the database is built in a flat, non-hierarchical format</documentation> </annotation> </element>
Many commands have one or more options. These are called command arguments. Command arguments may be of any of the standard data types. MetaCommand arguments are local to the MetaCommand.
source
<element name="ArgumentList" minOccurs="0"> <annotation> <documentation xml:lang="en">Many commands have one or more options. These are called command arguments. Command arguments may be of any of the standard data types. MetaCommand arguments are local to the MetaCommand.</documentation> </annotation> <complexType> <choice maxOccurs="unbounded"> <element name="Argument" maxOccurs="unbounded"> <annotation> <appinfo>Need to ensure that the named types actually exist</appinfo> </annotation> <complexType> <complexContent> <extension base="xtce:NameDescriptionType"> <attribute name="argumentTypeRef" type="xtce:NameReferenceType" use="required"/> <attribute name="initialValue" type="string"> <annotation> <documentation xml:lang="en">Used to set the initial calibrated values of Arguments. Will overwrite an initial value defined for the ArgumentType. For integer types base 10 (decimal) form is assumed unless: if proceeded by a 0b or 0B, value is in base two (binary form, if proceeded by a 0o or 0O, values is in base 8 (octal) form, or if proceeded by a 0x or 0X, value is in base 16 (hex) form. Floating point types may be specified in normal (100.0) or scientific (1.0e2) form. Time types are specified using the ISO 8601 formats described for XTCE time data types. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. Initial values for Array or Aggregate types may not be set.</documentation> </annotation> </attribute> </extension> </complexContent> </complexType> </element> </choice> </complexType> </element>
Used to set the initial calibrated values of Arguments. Will overwrite an initial value defined for the ArgumentType. For integer types base 10 (decimal) form is assumed unless: if proceeded by a 0b or 0B, value is in base two (binary form, if proceeded by a 0o or 0O, values is in base 8 (octal) form, or if proceeded by a 0x or 0X, value is in base 16 (hex) form. Floating point types may be specified in normal (100.0) or scientific (1.0e2) form. Time types are specified using the ISO 8601 formats described for XTCE time data types. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. Initial values for Array or Aggregate types may not be set.
annotation
appinfo
Need to ensure that the named types actually exist
source
<element name="Argument" maxOccurs="unbounded"> <annotation> <appinfo>Need to ensure that the named types actually exist</appinfo> </annotation> <complexType> <complexContent> <extension base="xtce:NameDescriptionType"> <attribute name="argumentTypeRef" type="xtce:NameReferenceType" use="required"/> <attribute name="initialValue" type="string"> <annotation> <documentation xml:lang="en">Used to set the initial calibrated values of Arguments. Will overwrite an initial value defined for the ArgumentType. For integer types base 10 (decimal) form is assumed unless: if proceeded by a 0b or 0B, value is in base two (binary form, if proceeded by a 0o or 0O, values is in base 8 (octal) form, or if proceeded by a 0x or 0X, value is in base 16 (hex) form. Floating point types may be specified in normal (100.0) or scientific (1.0e2) form. Time types are specified using the ISO 8601 formats described for XTCE time data types. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. Initial values for Array or Aggregate types may not be set.</documentation> </annotation> </attribute> </extension> </complexContent> </complexType> </element>
Used to set the initial calibrated values of Arguments. Will overwrite an initial value defined for the ArgumentType. For integer types base 10 (decimal) form is assumed unless: if proceeded by a 0b or 0B, value is in base two (binary form, if proceeded by a 0o or 0O, values is in base 8 (octal) form, or if proceeded by a 0x or 0X, value is in base 16 (hex) form. Floating point types may be specified in normal (100.0) or scientific (1.0e2) form. Time types are specified using the ISO 8601 formats described for XTCE time data types. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. Initial values for Array or Aggregate types may not be set.
source
<attribute name="initialValue" type="string"> <annotation> <documentation xml:lang="en">Used to set the initial calibrated values of Arguments. Will overwrite an initial value defined for the ArgumentType. For integer types base 10 (decimal) form is assumed unless: if proceeded by a 0b or 0B, value is in base two (binary form, if proceeded by a 0o or 0O, values is in base 8 (octal) form, or if proceeded by a 0x or 0X, value is in base 16 (hex) form. Floating point types may be specified in normal (100.0) or scientific (1.0e2) form. Time types are specified using the ISO 8601 formats described for XTCE time data types. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. Initial values for Array or Aggregate types may not be set.</documentation> </annotation> </attribute>
Tells how to package this command, for example in a packet or minor frame. This element is not visible to SequenceContainer in ContainerSet or CommandContainerSet. It may not be a ContainerRefEntry in another construct but it may be in a BaseContainer in another MetaCommand/CommandContainer.
source
<element name="CommandContainer" type="xtce:CommandContainerType" minOccurs="0"> <annotation> <documentation xml:lang="en">Tells how to package this command, for example in a packet or minor frame. This element is not visible to SequenceContainer in ContainerSet or CommandContainerSet. It may not be a ContainerRefEntry in another construct but it may be in a BaseContainer in another MetaCommand/CommandContainer.</documentation> </annotation> </element>
element MetaCommandType/TransmissionConstraintList
Appended to the TramsmissionConstraint List of the base command. Constraints are checked in order.
source
<element name="TransmissionConstraintList" minOccurs="0"> <annotation> <documentation xml:lang="en">Appended to the TramsmissionConstraint List of the base command. Constraints are checked in order. </documentation> </annotation> <complexType> <sequence> <element name="TransmissionConstraint" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">A CommandTransmission constraint is used to check that the command can be run in the current operating mode and may block the transmission of the command if the constraint condition is true.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:MatchCriteriaType"> <attribute name="timeOut" type="xtce:RelativeTimeType"> <annotation> <documentation xml:lang="en">Pause during timeOut, fail when the timeout passes</documentation> </annotation> </attribute> <attribute name="suspendable" type="boolean" default="false"> <annotation> <documentation xml:lang="en">Indicates whether the constraints for a Command may be suspended.</documentation> </annotation> </attribute> </extension> </complexContent> </complexType> </element> </sequence> </complexType> </element>
element MetaCommandType/TransmissionConstraintList/TransmissionConstraint
Indicates whether the constraints for a Command may be suspended.
annotation
documentation
A CommandTransmission constraint is used to check that the command can be run in the current operating mode and may block the transmission of the command if the constraint condition is true.
source
<element name="TransmissionConstraint" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">A CommandTransmission constraint is used to check that the command can be run in the current operating mode and may block the transmission of the command if the constraint condition is true.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:MatchCriteriaType"> <attribute name="timeOut" type="xtce:RelativeTimeType"> <annotation> <documentation xml:lang="en">Pause during timeOut, fail when the timeout passes</documentation> </annotation> </attribute> <attribute name="suspendable" type="boolean" default="false"> <annotation> <documentation xml:lang="en">Indicates whether the constraints for a Command may be suspended.</documentation> </annotation> </attribute> </extension> </complexContent> </complexType> </element>
Pause during timeOut, fail when the timeout passes
source
<attribute name="timeOut" type="xtce:RelativeTimeType"> <annotation> <documentation xml:lang="en">Pause during timeOut, fail when the timeout passes</documentation> </annotation> </attribute>
Indicates whether the constraints for a Command may be suspended.
source
<attribute name="suspendable" type="boolean" default="false"> <annotation> <documentation xml:lang="en">Indicates whether the constraints for a Command may be suspended.</documentation> </annotation> </attribute>
No specific meanings have been assigned to these different levels, but they mirror the Alarm levels of Telemetry.
annotation
documentation
Some Command and Control Systems may require special user access or confirmations before transmitting commands with certain levels. The level is inherited from the Base MetaCommand.
source
<element name="DefaultSignificance" type="xtce:SignificanceType" minOccurs="0"> <annotation> <documentation xml:lang="en">Some Command and Control Systems may require special user access or confirmations before transmitting commands with certain levels. The level is inherited from the Base MetaCommand.</documentation> </annotation> </element>
A flag that indicates that under special circumstances, this Interlock can be suspended.
annotation
documentation
An Interlock is a type of Constraint, but not on Command instances of this MetaCommand; Interlocks apply instead to the next command. An Interlock will block successive commands until this command has reached a certain stage (through verifications). Interlocks are scoped to a SpaceSystem basis.
source
<element name="Interlock" minOccurs="0"> <annotation> <documentation xml:lang="en">An Interlock is a type of Constraint, but not on Command instances of this MetaCommand; Interlocks apply instead to the next command. An Interlock will block successive commands until this command has reached a certain stage (through verifications). Interlocks are scoped to a SpaceSystem basis.</documentation> </annotation> <complexType> <attribute name="scopeToSpaceSystem" type="xtce:NameReferenceType"> <annotation> <documentation xml:lang="en">The name of a SpaceSystem this Interlock applies to. By default, it only applies to the SpaceSystem that contains this MetaCommand.</documentation> </annotation> </attribute> <attribute name="verificationToWaitFor" type="xtce:VerifierEnumerationType" default="complete"/> <attribute name="verificationProgressPercentage" type="decimal"> <annotation> <documentation xml:lang="en">Only applies when the verificationToWaitFor attribute is 'queued' or 'executing'.</documentation> </annotation> </attribute> <attribute name="suspendable" type="boolean" default="false"> <annotation> <documentation xml:lang="en">A flag that indicates that under special circumstances, this Interlock can be suspended.</documentation> </annotation> </attribute> </complexType> </element>
The name of a SpaceSystem this Interlock applies to. By default, it only applies to the SpaceSystem that contains this MetaCommand.
source
<attribute name="scopeToSpaceSystem" type="xtce:NameReferenceType"> <annotation> <documentation xml:lang="en">The name of a SpaceSystem this Interlock applies to. By default, it only applies to the SpaceSystem that contains this MetaCommand.</documentation> </annotation> </attribute>
Only applies when the verificationToWaitFor attribute is 'queued' or 'executing'.
source
<attribute name="verificationProgressPercentage" type="decimal"> <annotation> <documentation xml:lang="en">Only applies when the verificationToWaitFor attribute is 'queued' or 'executing'.</documentation> </annotation> </attribute>
attribute MetaCommandType/Interlock/@suspendable
type
boolean
properties
default
false
annotation
documentation
A flag that indicates that under special circumstances, this Interlock can be suspended.
source
<attribute name="suspendable" type="boolean" default="false"> <annotation> <documentation xml:lang="en">A flag that indicates that under special circumstances, this Interlock can be suspended.</documentation> </annotation> </attribute>
A Command Verifier is a conditional check on the telemetry from a SpaceSystem that that provides positive indication on the processing state of a command. There are eight different verifiers each associated with difference states in command processing: TransferredToRange, TransferredFromRange, Received, Accepted, Queued, Execution, Complete, and Failed. There may be multiple ‘complete’ verifiers. ‘Complete’ verifiers are added to the Base MetaCommand ‘Complete’ verifier list. All others will overide a verifier defined in a Base MetaCommand.
source
<element name="VerifierSet" minOccurs="0"> <annotation> <documentation xml:lang="en">A Command Verifier is a conditional check on the telemetry from a SpaceSystem that that provides positive indication on the processing state of a command. There are eight different verifiers each associated with difference states in command processing: TransferredToRange, TransferredFromRange, Received, Accepted, Queued, Execution, Complete, and Failed. There may be multiple ‘complete’ verifiers. ‘Complete’ verifiers are added to the Base MetaCommand ‘Complete’ verifier list. All others will overide a verifier defined in a Base MetaCommand. </documentation> </annotation> <complexType> <sequence> <element name="TransferredToRangeVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">Transferred to range means the command has been received to the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="SentFromRangeVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">Sent from range means the command has been transmitted to the spacecraft by the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="ReceivedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that simply means the SpaceSystem has received the command.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="AcceptedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that means the SpaceSystem has accepted the command</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="QueuedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifer that means the command is scheduled for execution by the SpaceSystem.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element> <element name="ExecutionVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that indicates that the command is being executed. An optional Element indicates how far along the command has progressed either as a fixed value or an (possibly scaled) ParameterInstance value.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"> <sequence minOccurs="0"> <element name="PercentComplete" type="xtce:DecimalValueType"> <annotation> <documentation>Values should be from 0 to 100</documentation> </annotation> </element> </sequence> </extension> </complexContent> </complexType> </element> <element name="CompleteVerifier" minOccurs="0" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">A possible set of verifiers that all must be true for the command be considered completed. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"> <sequence minOccurs="0"> <element name="ReturnParmRef" type="xtce:ParameterRefType"/> </sequence> </extension> </complexContent> </complexType> </element> <element name="FailedVerifier" type="xtce:CommandVerifierType" minOccurs="0"> <annotation> <documentation xml:lang="en">When true, indicates that the command failed. timeToWait is how long to wait for the FailedVerifier to test true.</documentation> </annotation> </element> </sequence> </complexType> </element>
element MetaCommandType/VerifierSet/TransferredToRangeVerifier
Transferred to range means the command has been received to the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft.
source
<element name="TransferredToRangeVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">Transferred to range means the command has been received to the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element>
element MetaCommandType/VerifierSet/SentFromRangeVerifier
Sent from range means the command has been transmitted to the spacecraft by the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft.
source
<element name="SentFromRangeVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">Sent from range means the command has been transmitted to the spacecraft by the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element>
element MetaCommandType/VerifierSet/ReceivedVerifier
A verifier that simply means the SpaceSystem has received the command.
source
<element name="ReceivedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that simply means the SpaceSystem has received the command.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element>
element MetaCommandType/VerifierSet/AcceptedVerifier
A verifier that means the SpaceSystem has accepted the command
source
<element name="AcceptedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that means the SpaceSystem has accepted the command</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element>
element MetaCommandType/VerifierSet/QueuedVerifier
A verifer that means the command is scheduled for execution by the SpaceSystem.
source
<element name="QueuedVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifer that means the command is scheduled for execution by the SpaceSystem.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"/> </complexContent> </complexType> </element>
element MetaCommandType/VerifierSet/ExecutionVerifier
A verifier that indicates that the command is being executed. An optional Element indicates how far along the command has progressed either as a fixed value or an (possibly scaled) ParameterInstance value.
source
<element name="ExecutionVerifier" minOccurs="0"> <annotation> <documentation xml:lang="en">A verifier that indicates that the command is being executed. An optional Element indicates how far along the command has progressed either as a fixed value or an (possibly scaled) ParameterInstance value.</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"> <sequence minOccurs="0"> <element name="PercentComplete" type="xtce:DecimalValueType"> <annotation> <documentation>Values should be from 0 to 100</documentation> </annotation> </element> </sequence> </extension> </complexContent> </complexType> </element>
element MetaCommandType/VerifierSet/ExecutionVerifier/PercentComplete
<element name="PercentComplete" type="xtce:DecimalValueType"> <annotation> <documentation>Values should be from 0 to 100</documentation> </annotation> </element>
element MetaCommandType/VerifierSet/CompleteVerifier
A possible set of verifiers that all must be true for the command be considered completed.
source
<element name="CompleteVerifier" minOccurs="0" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">A possible set of verifiers that all must be true for the command be considered completed. </documentation> </annotation> <complexType> <complexContent> <extension base="xtce:CommandVerifierType"> <sequence minOccurs="0"> <element name="ReturnParmRef" type="xtce:ParameterRefType"/> </sequence> </extension> </complexContent> </complexType> </element>
element MetaCommandType/VerifierSet/CompleteVerifier/ReturnParmRef
When true, indicates that the command failed. timeToWait is how long to wait for the FailedVerifier to test true.
source
<element name="FailedVerifier" type="xtce:CommandVerifierType" minOccurs="0"> <annotation> <documentation xml:lang="en">When true, indicates that the command failed. timeToWait is how long to wait for the FailedVerifier to test true.</documentation> </annotation> </element>
Parameters that are set with a new value after the command has been sent. Appended to the Base Command list
source
<element name="ParameterToSetList" minOccurs="0"> <annotation> <documentation xml:lang="en">Parameters that are set with a new value after the command has been sent. Appended to the Base Command list</documentation> </annotation> <complexType> <sequence> <element name="ParameterToSet" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">Sets a Parameter to a new value (either from a derivation or explicitly) after the command has been verified (all verifications have passed)</documentation> <appinfo>Value type must match Parameter type</appinfo> </annotation> <complexType> <complexContent> <extension base="xtce:ParameterRefType"> <choice> <element name="Derivation"> <annotation> <documentation>Result of the MathOperation will be the new Parameter value</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:MathOperationType"/> </complexContent> </complexType> </element> <element name="NewValue" type="string"/> </choice> <attribute name="setOnVerification" type="xtce:VerifierEnumerationType" default="complete"/> </extension> </complexContent> </complexType> </element> </sequence> </complexType> </element>
element MetaCommandType/ParameterToSetList/ParameterToSet
Sets a Parameter to a new value (either from a derivation or explicitly) after the command has been verified (all verifications have passed)
appinfo
Value type must match Parameter type
source
<element name="ParameterToSet" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">Sets a Parameter to a new value (either from a derivation or explicitly) after the command has been verified (all verifications have passed)</documentation> <appinfo>Value type must match Parameter type</appinfo> </annotation> <complexType> <complexContent> <extension base="xtce:ParameterRefType"> <choice> <element name="Derivation"> <annotation> <documentation>Result of the MathOperation will be the new Parameter value</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:MathOperationType"/> </complexContent> </complexType> </element> <element name="NewValue" type="string"/> </choice> <attribute name="setOnVerification" type="xtce:VerifierEnumerationType" default="complete"/> </extension> </complexContent> </complexType> </element>
Result of the MathOperation will be the new Parameter value
source
<element name="Derivation"> <annotation> <documentation>Result of the MathOperation will be the new Parameter value</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:MathOperationType"/> </complexContent> </complexType> </element>
element MetaCommandType/ParameterToSetList/ParameterToSet/NewValue
diagram
namespace
http://www.omg.org/space/xtce
type
string
properties
content
simple
source
<element name="NewValue" type="string"/>
element MetaCommandType/ParametersToSuspendAlarmsOnSet
Sometimes it is necessary to suspend alarms - particularly 'change' alarms for commands that will change the value of a Parameter
source
<element name="ParametersToSuspendAlarmsOnSet" minOccurs="0"> <annotation> <documentation xml:lang="en">Sometimes it is necessary to suspend alarms - particularly 'change' alarms for commands that will change the value of a Parameter</documentation> </annotation> <complexType> <sequence> <element name="ParameterToSuspendAlarmsOn" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">Will suspend all Alarms associated with this Parameter for the given suspense time after the given verifier</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:ParameterRefType"> <attribute name="suspenseTime" type="xtce:RelativeTimeType" use="required"/> <attribute name="verifierToTriggerOn" type="xtce:VerifierEnumerationType" default="release"/> </extension> </complexContent> </complexType> </element> </sequence> </complexType> </element>
element MetaCommandType/ParametersToSuspendAlarmsOnSet/ParameterToSuspendAlarmsOn
Will suspend all Alarms associated with this Parameter for the given suspense time after the given verifier
source
<element name="ParameterToSuspendAlarmsOn" maxOccurs="unbounded"> <annotation> <documentation xml:lang="en">Will suspend all Alarms associated with this Parameter for the given suspense time after the given verifier</documentation> </annotation> <complexType> <complexContent> <extension base="xtce:ParameterRefType"> <attribute name="suspenseTime" type="xtce:RelativeTimeType" use="required"/> <attribute name="verifierToTriggerOn" type="xtce:VerifierEnumerationType" default="release"/> </extension> </complexContent> </complexType> </element>