Attitude Data Messages - CCSDS

CCSDS RECOMMENDED STANDARD FOR ATTITUDE DATA MESSAGES
B2
PRIMARY REQUIREMENTS ACCEPTED BY THE ATTITUDE DATA
MESSAGES
Table B-1: Primary Requirements
Requirement
Accepted
for APM?
Accepted
for AEM?
Data must be provided in digital form (computer file). Y Y
The file specification must not require of the receiving agency the separate
application of, or modeling of, spacecraft dynamics or gravitational force
models, or integration or propagation.
The interface must facilitate the receiver of the message to generate an
attitude state at any required epoch.
Attitude state information must be provided in a reference frame that is
clearly identified and unambiguous.
Identification of the object must be clearly identified and unambiguous. Y Y
Identification of the center of attitude motion must be clearly identified and
unambiguous.
NOTE – The specification of a center name is not required for the
unambiguous specification of attitude but may be provided if desired.
Time measurements (time stamps, time tags, or epochs) must be provided in
a commonly used, clearly specified system.
The time bounds of the attitude ephemeris must be unambiguously specified. N Y
The standard must provide for clear specification of units of measure. Y Y
N
Y
Y
N
Y
Y
Y
Y
N
Y
Files must be readily ported between, and useable within, all Member
Agency computational environments that could be used to exchange Attitude
Data Messages.
Files must have means of being uniquely identified and clearly annotated.
The file name alone is considered insufficient for this purpose.
File name syntax and length must not violate computer constraints for those
Member Agency computing environments that could be used to exchange
Attitude Data Messages.
Y
Y
Y
Y
Y
Y
CCSDS 504.0-B-1 Page B-2 May 2008