ISO 13526:2010/Amd 1:2015
(Amendment)Space data and information transfer systems — Tracking data message — Amendment 1
Space data and information transfer systems — Tracking data message — Amendment 1
Systèmes de transfert des informations et données spatiales — Message de données de suivi — Amendement 1
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 13526
First edition
2010-09-15
AMENDMENT 1
2015-07-01
Space data and information transfer
systems — Tracking data message
AMENDMENT 1
Systèmes de transfert des informations et données spatiales —
Message de données de suivi
AMENDEMENT 1
Reference number
ISO 13526:2010/Amd.1:2015(E)
©
ISO 2015
---------------------- Page: 1 ----------------------
ISO 13526:2010/Amd.1:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2015 – All rights reserved
---------------------- Page: 2 ----------------------
Recommended Standard CCSDS
503.0-B-1
AMENDMENT 1
Issue Date: September 2010
Tracking Data Message
AMENDMENT 1
The Management Council of the Consultative Committee for Space Data Systems (CCSDS) has authorized the
publication of amendment 1 to CCSDS 503.0-B-1, issued November 2007.
Page 3-27
Subsection 3.5.2.6 RANGE,
– insert new sentence following “If ambiguous range is provided . . . the RANGE observable must be
performed”:
“For two-way and three-way data, the ICD should specify whether the observable is based upon the
round trip light time, or half the round trip light time (due to the signal’s having traveled to the
spacecraft and back to the receiver).”
Page 3-31
Subsection 3.5.5.1 CLOCK_BIAS,
– replace third and fourth sentences (“For example, the CLOCK_BIAS keyword . . . consistent with the
TDM convention for differenced data”) with the following:
“For example, the CLOCK_BIAS keyword may be used to show the difference between UTC and a
station clock by setting PARTICIPANT_1 to the name of the station clock and PARTICIPANT_2 to
‘UTC’. The observable should be calculated as clock#2 minus clock#1 (i.e., UTC – ST, where ST is the
station time), consistent with the TDM convention for differenced data.”
Distribution Contr
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.