08.11.2014 Views

Attitude Data Messages - CCSDS

Attitude Data Messages - CCSDS

Attitude Data Messages - CCSDS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>CCSDS</strong> RECOMMENDED STANDARD FOR ATTITUDE DATA MESSAGES<br />

ICD Item<br />

9 If floating-point numbers in extended-single or extended-double precision<br />

are to be used, then discussion of implementation-specific attributes is<br />

required.<br />

10 Information which must appear in comments for any given ADM<br />

exchange.<br />

Section<br />

Trace<br />

5.6.5<br />

5.8.1.3<br />

11 Whether the format of the ADM will be KVN or XML 1 . 1.2.3<br />

12 A reference orientation should be specified in an ICD if a body-fixed<br />

frame is to be used for the specification of Euler angles. For instance,<br />

demonstrating the alignment of the body axes with the local orbit frame or<br />

an inertial frame that gives a context to interpret the Euler angle data.<br />

13 If the angle units will be radians (outside the standard), this must be<br />

specified in the ICD.<br />

3.2.5.4.1<br />

3.2.5.3.2<br />

14 Provisions that are made to ensure information security. 6<br />

15 Values used for those keywords listed in annex A when those values are<br />

different from those given in annex A.<br />

16 Specification of interpretation of MET, MRT and SCLK, if to be<br />

exchanged, and how to transform it to a standardized time system such as<br />

UTC, TAI, etc. An ICD should specify that elapsed days are to be used<br />

for epochs, with year starting at zero.<br />

17 Exact specification of reference frames used in messages, if different from<br />

those specified in annex A.<br />

5.6.1<br />

A<br />

A2<br />

A4<br />

1 XML implementation awaiting approval as a standard.<br />

<strong>CCSDS</strong> 504.0-B-1 Page C-2 May 2008

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!