Attitude Data Messages - CCSDS
Attitude Data Messages - CCSDS
Attitude Data Messages - CCSDS
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>CCSDS</strong> RECOMMENDED STANDARD FOR ATTITUDE DATA MESSAGES<br />
4 ATTITUDE EPHEMERIS MESSAGE (AEM)<br />
4.1 OVERVIEW<br />
4.1.1 <strong>Attitude</strong> state information may be exchanged between participants by sending an<br />
ephemeris in the form of a series of attitude states using an <strong>Attitude</strong> Ephemeris Message<br />
(AEM). The message recipient must have a means of interpolating across these attitude<br />
states to obtain the attitude state at an arbitrary time contained within the span of the attitude<br />
ephemeris.<br />
4.1.2 The AEM shall be a text file consisting of attitude data for a single object. It shall be<br />
easily readable by both humans and computers.<br />
4.1.3 The file naming scheme shall be agreed to on a case-by-case basis between the<br />
participating agencies, typically using an Interface Control Document (ICD). The method of<br />
exchanging AEMs shall be decided on a case-by-case basis by the participating agencies and<br />
documented in an ICD.<br />
4.2 AEM CONTENT<br />
4.2.1 GENERAL<br />
4.2.1.1 The AEM shall be represented as a combination of the following:<br />
a) a header;<br />
b) metadata (data about data);<br />
c) optional comments (explanatory information); and<br />
d) attitude data.<br />
4.2.1.2 AEM files must have a set of minimum required sections; some may be repeated.<br />
4.2.1.3 Table 4-1 outlines the contents of an AEM.<br />
<strong>CCSDS</strong> 504.0-B-1 Page 4-1 May 2008