Software Interface Specification

Maneuver Performance Data File

Jet Propulsion LaboratoryCalifornia Institute of TechnologyPasadena, California

SIS Coordinator: Vic Legerton

Maneuver Performance Data File

Software Interface Specification

10 March 2005

SIS Number: SIS-NAV011

ABSTRACT:

ABSTRACT: This SIS contains the format and description of the Maneuver Performance Data File (MPDF). The MPDF is used in the maneuver design process to specify the flow rates, moment arms, and thrust magnitudes foreach spacecraft thruster. The SIS is applicable for Mars Reconnaissance Orbiter (MRO).

Jet Propulsion Laboratory
California Institute of Technology
Pasadena, California 91109

Updated by: Allen Halsell

Software Interface Specification Maneuver Performance Data File SIS-NAV011 37/106/054
DOCUMENT CHANGE LOG
Status Date Affected Portions
Draft 7/16/2004 Adapted MMO SIS-NAV011
Final 3/10/2005 Replaced appendix A with MRO sample, removed TBD list

TABLE OF CONTENTS

GENERAL DESCRIPTION .......................................................................................................... 1
PURPOSE OF INTERFACE ........................................................................................................ 1
SCOPE ..................................................................................................................................... 1
APPLICABLE DOCUMENTS......................................................................................................1
Lockheed Martin Astronautics (LMA) Documents........................................................................ 1
Jet Propulsion Laboratory (JPL) Documents.............................................................................. 1
SUBSYSTEM CITING................................................................................................................1
Interface Location, Medium..................................................................................................... 1
Data Source, Destinations and Transfer Method......................................................................... 1
Generation Method and Frequency ........................................................................................... 1
Pertinent Relationships with Other Interfaces............................................................................. 2
Labeling and Identification (Internal/External)........................................................................... 2
SECTION 2 INTERFACE CHARACTERISTICS ................................................................................ 3
HARDWARE CHARACTERISTICS ............................................................................................. 3
Special Equipment and Device Interfaces ................................................................................... 3
Special Setup Requirements..................................................................................................... 3
VOLUME AND SIZE.................................................................................................................. 3
INTERFACE MEDIUM CHARACTERISTICS ............................................................................... 3
FAILURE PROTECTION, DETECTION AND RECOVERY FEATURES...........................................3
File Backup Requirements....................................................................................................... 3
Security/Integrity Measures ..................................................................................................... 3
END-OF-FILE (OR MEDIUM) CONVENTIONS ............................................................................. 3
SECTION 3 ACCESS ........................................................................................................................ 4
PROGRAMS USING THE INTERFACE........................................................................................ 4
SYNCHRONIZATION CONSIDERATIONS...................................................................................4
Timing and Sequencing Characteristics..................................................................................... 4
Effective Duration ................................................................................................................. 4
Priority Interrupts................................................................................................................. 4
INPUT/OUTPUT PROTOCOLS, CALLING SEQUENCES...............................................................4
SECTION 4 DETAILED INTERFACE SPECIFICATIONS.................................................................. 5
STRUCTURE AND ORGANIZATION OVERVIEW ........................................................................ 5
SUBSTRUCTURE DEFINITION AND FORMAT ........................................................................... 5
SFDU Data Description ......................................................................................................... 5
Non-SFDU Data Description................................................................................................. 56
Header Record................................................................................................................. 6
Data Record.................................................................................................................... 7
: SAMPLE WRAPPED FILE ...................................................................................A-1
1.0 GENERAL DESCRIPTION

1.1 PURPOSE OF INTERFACE

This Software Interface Specification (SIS) provides the format and syntax for transmission of the ManeuverPerformance Data File (MPDF).

The MPDF is a data file used in the maneuver design process by NAV and FET. It contains spacecraftproperties including spacecraft mass and the thrust vectors, effective thrust, and effective flow rates for thrustersand engines, where applicable. Quantities which are constant such as thruster geometries are traceable to AACSdesign documentation.

1.2 SCOPE

The format, units, numerical precision and syntax specifications in this document apply to all phases of theMars Reconnaissance Orbiter (MRO) mission.

1.3 APPLICABLE DOCUMENTS
1.3.1 Lockheed Martin Astronautics (LMA) Documents

Space Exploration Systems Software Development Plan, MRO-01-0029

MRO OAS Design Specification , MRO 03-0147

MRO OAS Requirements Specification, MRO-03-0146

1.3.2 Jet Propulsion Laboratory (JPL) Documents

DPTRAJ-ODP User Reference Manual, SOM Vol. 1 & 2, November 10, 1999

DPTRAJ and ODP Interfaces and File Format Descriptions, SOM Vol. 3, January 24, 2000

1.4 SUBSYSTEM CITING
1.4.1 Interface Location, Medium

This interface is between the Flight Engineering Team (FET) and the Navigation (NAV) team. The interfaceshall be implemented as a disk file written in ASCII format, transmitted between workstations on the FlightOperation LAN.

1.4.2 Data Source, Destinations and Transfer Method

The source of the data is the FET. The destination of the data is MOPS. Data transfer shall be via the MSOP File Interchange System (FIS).

1.4.3 Generation Method and Frequency This file is generated as needed to support maneuver design and implementation. An MPDF will be deliveredpre-launch and before each propulsive maneuver. This excludes daily or periodic attitude control maneuvers andcertain pre-planned maneuvers (e.g., TCM-0/1 in the case of Genesis).
1.4.4 Pertinent Relationships with Other Interfaces

The MPDF details the FET implementation of NAV's maneuver requirements typically outlined in theManeuver Profile File (MPF). The MPDF joins the Maneuver Implementation File (MIF) in this role, byadding information about detailed thruster performance.

For GNS, iterative development efforts are tracked with the NAV supplied Maneuver Design VerificationMemorandum. Overlap between the Mass Properties Database and the MPDF are noteworthy. Mass estimatescontained in the MPDF are directly extracted from the MPDB.

1.4.5 Labeling and Identification (Internal/External)

Separate files shall be provided for distinct S/C configurations. Each file shall have an identification record, described in section 4.2.1. Each file will be provided with an unique external identification.

SECTION 2 INTERFACE CHARACTERISTICS

2.1 HARDWARE CHARACTERISTICS
2.1.1 Special Equipment and Device Interfaces

An electronic communications path must be provided between the FET host and the NAV host, regardless ofhardware origin or UNIX variant (e.g., Sun, HP, linux).. Interhost file transfer protocol (ftp) is assumed to be available.

2.1.2 Special Setup Requirements None.

2.2 VOLUME AND SIZE

The estimated size of each MPDF is 4300 bytes.

2.3 INTERFACE MEDIUM CHARACTERISTICS

The interface shall be a file written in ASCII format. The medium for the transmittal shall be DOM.

2.4 FAILURE PROTECTION, DETECTION AND RECOVERY FEATURES

2.4.1 File Backup Requirements It is the responsibility of the subsystem engineers to provide backups of this file.

2.4.2 Security/Integrity Measures

Unit and system tests will debug the mechanisms for file creation by FET and file usage by MOPS. As a storedfile, the PDB security/integrity measures will be in effect.

2.5 END-OF-FILE (OR MEDIUM) CONVENTIONS

There are no requirements for an end of file.

SECTION 3 ACCESS

3.1 PROGRAMS USING THE INTERFACE

This file is generated by the PROP_PREDICT program of SPAS and used by the MOPS program of NAV.

3.2 SYNCHRONIZATION CONSIDERATIONS
3.2.1 Timing and Sequencing Characteristics

The requirements for maneuvers always specify an execution time. Adequate test efforts by both NAV and FETmust always be considered in maneuver scheduling. Otherwise, the MPDF shall be considered as expired as ofthe execution time requirement contained in the MPF. See also section 1.4.4.2 requirement for line 4, where anapplicability time span is hosted within the MPDF.

3.2.2 Effective Duration The MPDF is only effective for the current maneuver being planned. Each maneuver requires a unique MPDF.

3.2.3 Priority Interrupts N/A

3.3 INPUT/OUTPUT PROTOCOLS, CALLING SEQUENCES

N/A

SECTION 4 DETAILED INTERFACE SPECIFICATIONS

4.1 STRUCTURE AND ORGANIZATION OVERVIEW

The Maneuver Performance Data File is an ASCII file which consists of the SFDU header, the ManeuverPerformance Data File headers, and the Maneuver Performance Data File data. Each will be described in the following sections.

4.2 SUBSTRUCTURE DEFINITION AND FORMAT
4.2.1 SFDU Data Description

The SFDU format and structure for the Maneuver Performance Data File's SFDU wrapper is shown below.Beginning with the header record:

CCSD3ZS00001AAAAAAAANJPL3KS0L015BBBBBBBB <LF>
MISSION_NAME=MARS_RECONNAISSANCE_ORBITER; <LF>
SPACECRAFT_NAME= MARS_RECONNAISSANCE_ORBITER; <LF>
DATA_SET_ID=MANEUVER_PERF; <LF>
FILE_NAME=mpdf.MRO_TCM1_final; <LF>
PRODUCER_ID=MRO_FET; <LF>
APPLICABLE_START_TIME=2005-08-15T14:00:00; <LF>
APPLICABLE_STOP_TIME=2005-08-15T14:01:31; <LF>
PRODUCT_CREATION_TIME=2005-08-15T22:30:00; <LF>
CCSD3RE00000BBBBBBBBNJPL3IS00251CCCCCCCC

Several items, shown above in italics, vary with mission or maneuver planning stage, and are elaborated below.The following table shows the Mission and Spacecraft Names currently supported by this SIS.

Project Mission Name in SFDU S/C Name in SFDU Mission ID S/CID
Mars Reconnaissance Orbiter MARS_RECONNAISSANCE_ORBITER MARS_RECONNAISSANCE_ORBITER 28 74

Notes:

Mission ID and S/C ID are necessary for SPICE tools and FIS access, and are hard-coded into several SPAS
tools for use with standard NAIF tools.
Lengths of the File Name and Producer Id are constrained to 32 characters and no spaces are permitted.
The underlined characters in the last line of the SFDU Header are the DDID.

The final line of the MPDF following the non-SFDU data (see Section 4.2.2.4), shall be the SFDU Tail tocomplete the SFDU Wrapper. The SFDU Tail is shown below.

CCSD3RE00000CCCCCCCCCCSD3RE00000AAAAAAAA

4.2.2 Non-SFDU Data Description

The non-SFDU portion of the file is described as follows:

4.2.2.1 Header Record

A header record will be provided containing the following information:

LINE COLUMN FORMAT DESCRIPTION

1 1 CHAR*12 'S/C'
1 13 CHAR*36 S/C ID number **
2 1 CHAR*12 'PREP'
2 13 CHAR*26 Name and extension of the analyst
3 1 CHAR*12 'CREATION'
3 13 CHAR*8 Creation date of this file
3 25 CHAR*8 Creation time of this file
4 1 CHAR*12 'VALID'
4 13 CHAR*8 Beginning valid date of this file
4 25 CHAR*8 Ending valid date of this file

Since the format of the header is fixed, there is no need for an "end-of-header" indicator.
Note that line 1 of this "header" shares the same line as the SFDU's trailing line of its "header".

4.2.2.2 Data Record

The following items are passed to the user via Fortran-style namelist $MPDF:

ITEM TYPE UNITS DESCRIPTION

MSC R kg Spacecraft total mass
IISC R(3,3) kg-m2 Spacecraft products and
moments of inertia w.r.t. the
spacecraft coordinates
translated to spacecraft c.m.
CMSC R(3) meters Spacecraft center of mass
w.r.t. spacecraft body
coordinates.
FVEC R(3,25) - Effective thrust direction
unit vectors w.r.t. spacecraft
body coordinates.
FMAG R(25) Newton Effective thrust magnitude.**
RF RF(3,25) meters Thruster location w.r.t.
spacecraft body coordinates.**
FLORAT R(25) kg/sec Propellant flow rate/thruster.

NOTE: Products of Inertia.
Products and moments of inertia are defined in accordance with the following convention:

Ixy = + ∫(xy)dm, Iyz = + ∫(yz)dm, Izx = + ∫(zx)dm

Ixx = + ∫(y2 + z2)dm, Iyy = + ∫(x2 + z2)dm, Izz = + ∫(y2 + x2)dm

The moment of inertia matrix is then given by, I=

[[ Ix -Ixy -Ixz]
[-Ixy Iyy -Iyz]
[-Ixz -Iyz Izz]]

APPENDIX A: SAMPLE WRAPPED FILE [TBR]

A sample wrapped Maneuver Performance Data File is provided in order to show
the expected format of the data. The user should not code specifically to the
real numbers printed.

CCSD3ZS00001AAAAAAAANJPL3KS0L015BBBBBBBB
MISSION_NAME=MARS_RECONNAISANCE_ORBITER;
SPACECRAFT_NAME=MARS_RECONNAISSANCE_ORBITER;
DATA_SET_ID=MANEUVER_PERF;
FILE_NAME=mpdf.MRO_TCM1_ORT;
PRODUCER_ID=MRO_FET;
APPLICABLE_START_TIME=2005-09-24T00:00:00;
APPLICABLE_STOP_TIME=2005-09-26T00:00:00;
PRODUCT_CREATION_TIME=2005-03-01T21:52:15;
CCSD3RE00000BBBBBBBBNJPL3IS00251CCCCCCCCS/C 74
PREP eckart, 303-977-6457
CREATION 03-01-05 21:52:15
VALID 09-24-05 09-26-05

MSC= 2073.37

IISC= 2.65e+07, 142202, -60233
142202, 3.16e+07, -3.49e+06
-60233, -3.49e+06, 3.86e+07
CMSC= 0.209, -101, 1.62
FVEC= 0.867672, -0.00131, -0.497136
-0.867822, -0.001488, -0.496872
-0.868016, -0.000513, 0.496536
0.868468, 0.000148, 0.495745
0.86788, 0.000912, -0.496773
-0.868095, 0.000145, -0.496399
-0.867549, -0.000534, 0.497351
0.86764, -0.001077, 0.497192
0.000659, 0.999999, 0.000828
-0.001273, 0.999998, 0.001754
-0.000339, 0.999998, -0.00175
0.000981, 0.999999, 0.001291
-0.000796, 0.999999, -0.001308
0.000693, 0.999999, -0.000258
0.047722, 0.996272, -0.071864
-0.037362, 0.996225, -0.078363
-0.086098, 0.996283, -0.002705
-0.049322, 0.995941, 0.075298
0.037773, 0.996097, 0.07977
0.086985, 0.996191, 0.006162
0, 0, 0
0, 0, 0
0, 0, 0
0, 0, 0
0, 0, 0

FMAG= 0.004529, 0.004529, 0.004529, 0.004529

0.004529, 0.004529, 0.004529, 0.004529
15.2, 15.2, 15.2, 15.2
15.2, 15.2, 119.7, 119.7

119.7, 119.7, 119.7, 119.7
0, 0, 0, 0
0,

Software Interface Specification Maneuver Performance Data File SIS-NAV011 37/106/054
RF= 0.712724, -0.40005, -1.38105
-0.712876, -0.399872, -1.38062
-0.712521, -0.399999, 1.38013
0.712394, -0.400863, 1.38036
0.712826, -1.52329, -1.38184
-0.7128, -1.52324, -1.38184
-0.712546, -1.52443, 1.37952
0.713384, -1.52507, 1.37988
0.619125, -0.303124, -1.38062
-0.620014, -0.303073, -1.37942
-0.619227, -0.302666, 1.38069
0.620649, -0.303911, 1.38054
1.10002, -0.212395, -0.000381
-1.09926, -0.212776, -0.0004572
0.070104, 0.386182, -0.105816
-0.056896, 0.386283, -0.113462
-0.126924, 0.385724, -0.0082804
-0.0707898, 0.385648, 0.105588
0.0564896, 0.385826, 0.113563
0.126467, 0.385877, 0.0079756
0, 0, 0
0, 0, 0
0, 0, 0
0, 0, 0
0, 0, 0
FLORAT= 3.97393e-06, 3.97393e-06, 3.97393e-06, 3.97393e-06
3.97393e-06, 3.97393e-06, 3.97393e-06, 3.97393e-06
0.00662339, 0.00662339, 0.00662339, 0.00662339
0.00662339, 0.00662339, 0.0555483, 0.0555483
0.0555483, 0.0555483, 0.0555483, 0.0555483
0, 0, 0, 0
0,
CCSD3RE00000CCCCCCCCCCSD3RE00000AAAAAAAA