• No results found

TRACKING DATA MESSAGE. PROTOTYPING TEST PLAN Draft #1

N/A
N/A
Protected

Academic year: 2021

Share "TRACKING DATA MESSAGE. PROTOTYPING TEST PLAN Draft #1"

Copied!
7
0
0

Loading.... (view fulltext now)

Full text

(1)

TRACKING DATA

MESSAGE

PROTOTYPING TEST PLAN

Draft #1

(2)

Table of Contents

1. Introduction... 3

2. Blue Book Promotion Criteria ... 3

3. Tracking Data Message (TDM) Testing Goals... 3

4. Test Overview... 4

5. Test Details ... 4

5.1 Test #1: Rosetta / JPL => ESA ... 4

5.2 Test #2: Rosetta / ESA => JPL ... 5

5.3 Test #3: TerraSAR-X / DLR => ESA... 5

5.4 Test #4: TerraSAR-X / ESA => DLR... 5

5.5 Test #5: Dawn / ESA => JPL... 6

5.6 Test #6: Phoenix / ESA => JPL ... 6

6. Test Reports ... 6

7. References... 7

(3)

1. Introduction

This document provides an outline for the prototype testing of the CCSDS Tracking Data Message (TDM), CCSDS 503.0-R-2 (reference [2]). The TDM is part of the technical program of the CCSDS Navigation Working Group. This document has recently

completed the second CCSDS Agency Review; this process is described in reference [1]. This plan has been prepared by the members of the CCSDS Navigation Working Group who will coordinate the prototyping for their respective agencies, specifically:

Jürgen Fertig (ESA) Siegmar Pallaschke (ESA) Reinhard Kiehling (DLR) David Berry (NASA/JPL)

2. Blue Book Promotion Criteria

The CCSDS Procedures Manual states that for a Recommendation to become a Blue Book, the standard must be tested in an operational manner. The following requirements for an Implementation Exercise were excerpted from reference [1]:

“At least two independent and interoperable prototypes or implementations must have been developed and demonstrated in an operationally relevant environment, either real or simulated”

It is the intent of this document to outline the Navigation Working Group’s approach to meeting this requirement for the TDM.

3. Tracking Data Message (TDM) Testing Goals

The test of the TDM will exercise the following features:

• 2-way Doppler • 3-way Doppler • Ranging • Delta-DOR • Angles • Media Calibration • Weather

(4)

4. Test Overview

Prototyping of the TDM will be done for the following spacecraft, by the following agencies and members of the Navigation Working Group:

Test #

Spacecraft Agencies Direction Personnel

1 Rosetta ESA, NASA/JPL NASA/JPL => ESA Jürgen Fertig Siegmar Pallaschke David Berry

Tomas Martin-Mur 2 Rosetta ESA, NASA/JPL ESA => NASA/JPL Jürgen Fertig

Siegmar Pallaschke David Berry

Tomas Martin-Mur 3 TerraSAR-X DLR, ESA DLR => ESA Reinhard Kiehling

Jürgen Fertig

Siegmar Pallaschke 4 TerraSAR-X DLR, ESA ESA => DLR Reinhard Kiehling

Jürgen Fertig Siegmar Pallaschke 5 Dawn ESA, NASA/JPL ESA => NASA/JPL Jürgen Fertig

Siegmar Pallaschke David Berry

Tomas Martin-Mur Don Han

6 Phoenix ESA, NASA/JPL ESA => NASA/JPL Jürgen Fertig Siegmar Pallaschke David Berry

Tomas Martin-Mur Brian Portock

5.

Test Details

5.1 Test #1: Rosetta / JPL => ESA

For this test, NASA/JPL will send TDMs to ESA that contain tracking data for the Rosetta spacecraft. The TDMs will correspond with TRK-2-18 Orbit Data Files (ODF) (reference [3]) that have already been provided from JPL/Deep Space Network (DSN) to ESA (same tracking pass). ESA will process the TDMs with their prototype and the TRK-2-18 data through the normal navigation software, and compare the results. The results of the initial testing will be discussed at the ESA/NASA Technical Interchange Meeting to be held at Darmstadt 25-April-2007 through 27-April-2007, and in subsequent telecons of the Navigation Working Group. Further tests will also be discussed, most

(5)

Expected Results

It is anticipated that the TDM and ODF will produce identical residuals in orbit

determination. It is anticipated that an ODF converted to a TDM can be read back into the TDM prototype, and an identical output TDM produced. Assuming that these criteria are met, the test will be considered successful. In the event of discrepancies,

troubleshooting will be conducted by the participants in the test.

5.2 Test #2: Rosetta / ESA => JPL

For this test, ESA will send TDMs to NASA/JPL that contain tracking data for the Rosetta spacecraft. JPL will process the TDMs sent from ESA with their TDM prototype. The details of this test will be discussed at the ESA/NASA Technical

Interchange Meeting to be held at Darmstadt 25-April-2007 through 27-April-2007, and in subsequent telecons of the Navigation Working Group.

Expected Results

To be specified.

5.3 Test #3: TerraSAR-X / DLR => ESA

For this test, DLR will send TDMs to ESA that contain tracking data for the TerraSAR-X spacecraft. ESA will process the TDMs sent from DLR with their TDM prototype. The results of the testing will be discussed in subsequent telecons of the Navigation Working Group.

Expected Results

To be specified.

5.4 Test #4: TerraSAR-X / ESA => DLR

For this test, DLR will send TDMs to ESA, ….., along with the TRK-2-18 Orbit Data Files that correspond to the TDM (same tracking pass). ESA will process the TDM with their prototype and the TRK-2-18 data through the normal navigation software, and compare the results. The results of the initial testing will be discussed at the ESA/NASA Technical Interchange Meeting to be held at Darmstadt 25-April-2007 through 27-April-2007. Further tests will also be discussed, most particularly the sending of additional data from ESOC to JPL.

(6)

5.5 Test #5: Dawn / ESA => JPL

For this test, ESA will send TDMs to NASA/JPL that contain tracking data for the Dawn spacecraft. ESA will also send the corresponding IFMS data. Of particular interest is the angle data from the initial acquisition at Perth. JPL will process the TDMs sent from ESA with their TDM prototype. The details of this test will be discussed at the ESA/NASA Technical Interchange Meeting to be held at Darmstadt 25-April-2007 through 27-April-2007, and in subsequent telecons of the Navigation Working Group.

Expected Results

To be specified.

5.6 Test #6: Phoenix / ESA => JPL

For this test, ESA will send TDMs to NASA/JPL that contain tracking data for the Phoenix spacecraft. ESA will also send the corresponding IFMS data. Of particular interest is the angle data from the initial acquisition at Kourou. JPL will process the TDMs sent from ESA with their TDM prototype. The details of this test will be

discussed at the ESA/NASA Technical Interchange Meeting to be held at Darmstadt 25-April-2007 through 27-25-April-2007, and in subsequent telecons of the Navigation Working Group.

Expected Results

To be specified.

6.

Test Reports

JPL and ESA will prepare test reports for Tests #1, #2, #5, #6, and send them to the Navigation Working Group via email.

DLR and ESA will prepare test reports for Tests #3, #4, and send them to the Navigation Working Group via email.

The reports from JPL, ESA and DLR will be merged into a single, final test report by the Chair of the CCSDS Navigation Working Group. This report will be posted to the Navigation Working Group Common Working Environment (CWE) on the CCSDS web page at http://cwe.ccsds.org . The report will be submitted to the CCSDS Engineering Steering Group (CESG) and CCSDS Management Council (CMC), along with results of the Agency Reviews. At that time, a formal request will be placed with the CMC for

(7)

7. References

[1] Procedures Manual for the Consultative Committee for Space Data Systems. CCSDS A00.0-Y-9. Yellow Book. Issue 9. Washington, D.C.: CCSDS, November 2003.

[2] Tracking Data Message, CCSDS 503.0-R-2, Red Book, December 2006.

[3] 820-013, TRK-2-18, Tracking System Interfaces, Orbit Data File Interface, Revision D, 20-December-2006.

[4] IFMS-OCC Interface Control Document, Makalumedia/MR/IFMS/ICD/FTP-OCC, Issue 9.3.1, 09-April-2003,

8. Acronyms

CCSDS Consultative Committee for Space Data Systems CESG CCSDS Engineering Steering Group

CMC CCSDS Management Council

CWE Common Working Environment DLR Deutsches Zentrum für Luft und Raumfahrt DSN Deep Space Network

ESA European Space Agency

ESOC European Space Operations Center

IFMS Intermediate Frequency and Modem Systems JPL Jet Propulsion Laboratory

NASA National Aeronautics and Space Administration ODF Orbit Data File (aka TRK-2-18 file)

References

Related documents

As  a  note  owner,  your  goal  is  to  keep  the  length  of  the  lien  as  short  as  possible,  so  that  you  receive  money  faster.  To  shorten  a 

An analysis of the economic contribution of the software industry examined the effect of software activity on the Lebanese economy by measuring it in terms of output and value

Correlated  normal  random  variables  are  well  understood.  The  usual  multivariate  distribution  used  for  analysis  of  related  normals  is  the 

According to Figure 2 regarding matching governance structures with commercial transactions, the decision to integrate an activity within the boundaries of the

On April 25, 2007, the petitioners moved for a stay of the April 17, 2007, order; in that motion, they also requested.. that the court vacate the order. In support of their motion,

1 st September 2004 17 th December 2004 25 th January 2005 11 th February 2005 4 th April 2005 26 th January 2007 27 th February 2007 2 nd April 2007 Version 1.0 Version

However the PWD immediately supplements and corrects that criterion, requiring that preva- lence be given to that part of the mandatory provisions of the host country (i.e.

With all four financing mechanisms, price control results in a price decrease in both the monopolistic and the competitive region due to the incumbent ’s strong market power.. There