SIS EAE-014, Rev. A, Change 2

MARS OBSERVER

Software Interface Specification

Maneuver Implementation/Reconstruction File

Jet Propulsion Laboratory

California Institute of Technology

Pasadena, California

Table of Contents

Author(s):  John E. Ekelund



	                        SIS EAE-014

                               MARS OBSERVER
                MANEUVER IMPLEMENTATION/RECONSTRUCTION FILE
                      Software Interface Specification

                                17 MAY 1993



ABSTRACT:  This document describes a file created by the Spacecraft Team
for use by MOPS within NAV.  The file contains commands, achievable
attitudes and velocities, and statistics associated with a TCM.



                         Jet Propulsion Laboratory
                    California Institute of Technology
                        Pasadena, California 91109




			         Mars Observer
			Software Interface Specification

Interface Title:  MANEUVER IMPLEMENTATION/RECONSTRUCTION FILE

Interface Id:     EAE 014		VERSION:  FINAL

Author:	J.E. EKELUND			Signature: J. Ekelund    5/20/93

Generating Element Engineer:	ENGINEERING ANALYSIS

	J. McLeod			5/20/93

Receiving Element Engineer:	NAVIGATION ANALYSIS

	J.E. Ekelund			5/20/93

Receiving Element Engineer:	SCIENCE SUPPORT

	M. McCullar			5/20/93

Receiving Element Engineer:	DATA STORAGE & RETRIEVAL

	A. Cherino			5/20/93

Approval Name and Title

	P.B. Esposito			5/25/93
	Cognizant Interface Engineer

	Ben Jai				5/25/93
	MO GDS Software System Engineer


                      DISTRIBUTION LIST





                        DOCUMENT CHANGE LOG

     Change      Date       Affected Portions
     Letter

     Original    1/17/91    All

     Rev. A      7/17/91    Section 4.2.2.3, Maneuver Block Description,
			    Appendix A added.

     Change 1    5/25/92    Section 4.2.2.1, Date definition.

     Change 2	 5/17/93    Section 4.2.2.3, BLKTYP definition.


                        List of TBD Items

        Page    Resolution Date         Item

1. GENERAL DESCRIPTION

1.1 PURPOSE OF INTERFACE

This Software Interface Specification (SIS) contains the description of the Maneuver Implementation/Reconstruction File. This file will be made available for use in MOPS.

1.2 SCOPE

The format and syntax specifications in this SIS apply to all phases of the mission.

1.3 APPLICABLE DOCUMENTS


 SFOC0038-01-09-01    1 May 90     SFOC-1-CDB-ANY-CATALOGUE2

 SFOC0099-01-00       13 Jun 90    Data Dictionary

 SFOC0038-00-08-01    26 Feb 88    SFOC-1-CDB-MGN-TIMESFILE

 SFOC0038-01-09-03    6 Feb 90     SFOC-2-SYS-ANY-TIMEFORMS

                      1 Jul 90     DPTRAJ-ODP User Reference Manual,
                                   SOM Vol. 1 and Vol. 2

                      1 Jul 90     DPTRAJ and ODP Interfaces and File
                                   Format Descriptions, SOM, Vol. 3

 JPL IOM 	      17 May 91    Maneuver Implementation/Reconstruction
 314.9191-638			   File from GE ASTRO

Letters from S. Davis (GE/ASD)

 a) MO-MOS-103	      17 Apr 91	   GE Delivery of the Maneuver Implementation/
				   Reconstruction File

 b) MO-MOS-104	      18 Apr 91	   Maneuver Name Used in the Maneuver
				   Profile File

1.4 FUNCTIONAL DESCRIPTION

1.4.1 Data Source, Destination, and Transfer Method

The source of the data is SCT. The destination of the data is MOPS. Data transfer shall be via the Project Data Base (PDB) using the SFOC LAN.

1.4.2 Pertinent Relationships with Other Interfaces

This file, which is produced by SCT, is a response to the Maneuver Profile File (SIS) previously transmitted from NAV to SCT.

1.4.5 Labeling and Identification (Internal/External)

An identification record shall be provided internally, describing the maneuver and the maneuver design stage (see section 4.2.1). The file name shall provide external identification.

1.4.4 Assumptions and Constraints

N/A

2. ENVIRONMENT

2.1 HARDWARE CHACTERISTICS AND LIMITATIONS

N/A

2.2 INTERFACE MEDIUM AND CHARACTERISTICS

The interface shall be a disk file written in formatted ASCII. The medium for transmittal to the Project Data Base (PDB) shall be the SFOC LAN.

2.3 INPUT/OUTPUT PROTOCOLS

None.

2.3.1 Device Addressing

N/A

2.3.2 Operating System Protocols

N/A

2.3.3 Deformatting

Users of the Implementation/Reconstruction File will be required to have software to remove the SFDU data.

2.3.4 Calling Sequence

N/A

2.4 FAILURE PROTECTION, DETECTION, RECOVERY FEATURES

2.4.1 Backup Requirements

This file may be recreated by the SCT.

2.4.2 Security/Integrity Measures

This file has no inherent security because it is directly text editable using system routines. Unit and system tests will debug the mechanisms for file creation by SCT and file reading by MOPS. As a stored file, the PDB security/integrity measures will be in effect.

2.5 END-OF-FILE (OR MEDIUM) CONVENTIONS

End-of-file shall be the standard end-of-file.

2.6 UTILITY PROGRAMS

A utility program will be required by the users of this file to remove the SFDU labels.

3. DATA FLOW CHARACTERISTICS

3.1 OPERATIONAL CHARACTERISTICS

3.1.1 Generation Method and Frequency

The file is produced by the SCT using the program PAS G&C MANEUVER. This file may be generated several times for a specific maneuver: for preliminary design, for final design, and for tweak.

3.1.2 Time Span of Product

N/A

3.2 DATA VOLUME

Less than 3 kilobytes of disk space.

3.3 FLOW RATE

TBD

4. DETAILED DATA OBJECT DEFINITION

4.1 STRUCTURE AND ORGANIZATION OVERVIEW

The Maneuver Implementation/Reconstruction File is an ASCII file which consists of the SFDU Header, the Maneuver Implementation/ Reconstruction File Headers, and Maneuver Implementation/Reconstruction Data. Each will be described in the following sections.

4.2 DATA FORMAT AND DEFINITION

4.2.1 SFDU Data Description

The SFDU information and structure, for the Maneuver Implementation/ Reconstruction File, (DDID = 0252) in diagramatic representation: 
CCSD3ZS00001AAAAAAAA
    NJPL3KS0L015BBBBBBBB
        <CR><LF>
        MISSION_NAME=MARS_OBSERVER;<CR><LF>
        SPACECRAFT_NAME=MARS_OBSERVER1;<CR><LF>
        DATA_SET_ID=MANEUVER_IMPL;<CR><LF>
        FILE_NAME=mif.sff;<CR><LF>
        PRODUCER_ID=MO_SCT;<CR><LF>
        PRODUCT_CREATION_TIME=1990-07-18T22:00:00;<CR><LF>
    CCSD3RE00000BBBBBBBB
    NJPL3IS00252CCCCCCCC
In the actual Maneuver Implementation/Reconstruction File, the following SFDU data is located at the end of the file, following the non-SFDU data which is described in Section 4.2.2 
    CCSD3RE00000CCCCCCCC
CCSD3RE00000AAAAAAAA

4.2.2 Non-SFDU Data Description

A TCM will usually consist of a sequence of maneuver blocks (example: roll, yaw, roll, burn, etc.). The file shall contain a separate record for the parameters describing each maneuver block. One additional record shall contain parameters describing the total maneuver.

Two dimensional matrices contained in this file are written by PAS/G&C/MANEUVER using the FORTRAN columnwise convention for cycling through the indices. MOPS must read two dimensional matrices using the FORTRAN column-wise convention. If an editor is used to produce a hardcopy of the file, printed matrices will appear as the transpose of the mathematical convention as shown below: 

		A(1,1)     A(2,1)     A(3,1)

		A(1,2)     A(2,2)     A(3,2)

		A(1,3)     A(2,3)     A(3,3)
The non-SFDU portion of the file is as follows:

Header Record

A header record will be provided containing the following information: 

LINE     COLUMN     FORMAT     DESCRIPTION
------------------------------------------
 1          1       A12        `MANEUVER'
 1         13       A36        Text identifying this maneuver

 2          1       A12        `MODE'
 2         13       A36        Text identifying maneuver mode

 3          1       A12        `STAGE'
 3         13       A36        Text describing maneuver design
                               stage

 4          1       A12        `BLOCKS'
 4         13       I3         Number of blocks in the maneuver

 5          1       A12        `S/C'
 5         13       A36        Text identifying the spacecraft

 6          1       A12        `CRS TAPE'
 6         13       A36        Text identifying CRS tape used
                               to generate this file

 7          1       A12        `P-FILE'
 7         13       A36        Text identifying the NAV P-file
                               used to generate the CRS tape

 8          1       A12        `PREP'
 8         13       A36        Name and extension of the analyst
                               who generated this file
 9          1       A12        `CREATION'
 9         13       A8         Creation date of this file in
                               the format MM-DD-YY
 9         25       A8         Creation time of this file in
                               the format HH:MM:SS
10          1       A12        `PROGRAM'
10         13       A12        Name of the program
10         45       A8         Date of program collection
10         55       A8         Time of program collection
Since the format of the header is fixed, there is no need for an "end-of-header" indicator.

Total Maneuver Description

This record contains parameters describing the total maneuver. 
                PARAMETER
LN  COL  FORMAT        NAME        UNITS      DESCRIPTION
---------------------------------------------------------
 1   1   F10.3         VRA          deg       Right ascension of
                                              total achievable
                                              velocity, in
                                              J2000 coordinates
 1  11   F10.3         VDEC         deg       Declination of total
                                              achievable velocity, in
                                              J2000 coordinates
 1  21   D20.9         VMAG         km/sec    Magnitude of total
                                              achievable velocity
 2   1   3D20.9        VE(3)        km/sec    Total achievable
                                              velocity in J2000
                                              coordinates
 3   1   2(3D20.9/),   ETOX(3,3)    none      Initial J2000 to S/C
           3D20.9                             XYZ transformation
                                              matrix
 6   1   F20.3         TSTART     SCE time    Time when first burn
                                  (sec past   of first block
                                  2000.0)UTC  begins
 6  31   F20.3         TEND       SEC time    Time when last burn of
                                  (sec past   last block ends
                                  2000.0)UTC
 7   1   F10.3         MSTART       kg        Vehicle Mass at start
                                              of first block
 7  11   F10.3         MFINAL       kg        Vehicle Mass at end of
                                              last block
 8   1   2(3E15.7/),   VECOV(3,3) (km/sec)2   Covariance of total
           3E15.7                             achievable velocity
                                              in J2000 system
                                              coordinates (one sigma)
11   1   2(3E15.7/),   COV(3,3)     none      Covariance associated
           3E15.7                             with initial ETOX
                                              matrix (one sigma)
14   1   E15.7         FMVERR       km/sec    Fixed magnitude un-
                                              certainty in velocity
                                              (one sigma)
14  16   E15.7         FPVERR       km/sec