625-610 SIS 211-05 P2 Rev. A TABLE OF CONTENTS 1.0 GENERAL DESCRIPTION 1.2 SCOPE 1.3 APPLICABLE DOCUMENTS 1.4 SUBSYSTEM SITING 1.4.1 Interface Location Medium 1.4.2 Data Source, Destinations and Transfer Method 1.4.3 Pertinent Relationships with Other Interfaces 1.4.4 Labeling and Identification (Internal/External) 2. INTERFACE CHARACTERISTICS 2.1 HARDWARE CHARACTERISTICS. 2.1.1 Special Equipment and Device Interfaces 2.1.2 Special Setup Requirements 2.2 VOLUME AND SIZE 2.3 INTERFACE MEDIUM CHARACTERISTICS 2.4 FAILURE PROTECTION, DETECTION AND RECOVERY 2.4.1 File Backup Requirements 2.4.2 Security/Integrity Measures 2.5 END-OF-FILE (OR MEDIUM) CONVENTIONS 3. ACCESS 3.1 PROGRAMS USING THE INTERFACE 3.2 SYNCHRONIZATION CONSIDERATIONS. 3.2.1 Timing and Sequencing Characteristics 3.2.2 Effective Duration 3.2.3 Priority Interrupts 3.3 INPUT/OUTPUT PROTOCOLS, CALLING SEQUENCES 4. DETAILED INTERFACE SPECIFICATIONS 4.1 STRUCTURE AND ORGANIZATION OVERVIEW 4.2 SUBSTRUCTURE DEFINITION AND FORMAT 4.2.1 Header 4.2.2 Body 4.2.2.1 DMS Status Event 4.2.2.2 TVSHUT Status Event 4.2.2.3 SSIMODE Status Event 4.2.2.4 RFS Status Event. 4.2.2.5 MDS Statue Event 4.2.2.6 AACS Status Event 4.2.2.7 PB (Playback) Status Event 4.2.2.8 BITS Status Event 4.2.2.9 INST_REC_SEL Status Event 4.2.2.10 INST_RT_SEL Status Event 625-610 SIS 211-05 P2 Rev. A 4.2.2.11 RRCC Status Event 4.2.2.12 PBSELVECT Status Event 4.2.2.13 TLMFRAME Status Event 4.2.2.14 INST_RT_DATA Event 4.2.2.15 INST_PB_DATA Event 4.2.2.16 BDTT Event 4.3 EXAMPLE SPACECRAFT EVENT FILE ____________________________________________________________________________ | | 625-610: | | PROJECT GALILEO | NUMBER: 211-05 P2 | | | | | SOFTWARE INTERFACE SPECIFICATION | REVISION: Rev. A | | | Phase 2 | | | | | Cover Sheet | DATE: 06/07/94 | ____________________________________________________________________________ | SIS NAME: Spacecraft Event File (SEF) | ____________________________________________________________________________ | DOMAIN: | | System Subsystem Program Make/Use | | MSS Sequence Generation SEQGEN Make | | MSS Sequence of Events Gen SEG Use | | MSS Scan Platform Modeling SCANOPS Use | | MSS Command Generation SEQTRAN Use | | SVC Science VAX Cluster C-Kernel Use | | SNIPGEN SNIPGEN Use | | OES G&C Analysis GCFS Use | | OES Power Analysis RSEF Use | | NAV OMAS OMAS Use | | DMS Utilities AQQC/SCEGEN Use | | | | Computer System: Unisys 2200, Varian | ____________________________________________________________________________ | PURPOSE OF INTERFACE (SUMMARY): This interface provides a people-oriented | | form of sequence data at the individual event (i.e. command) level intended| | for use in the mission operations environment. The format for the follow- | | ing interface is fully defined by SIS 211-59, Ground Event File. | ____________________________________________________________________________ | INTERFACE MEDIUM: | | Disk File: [X] | | Magnetic Tape: [ ] Tracks: _____ Density: _____ Data Code: _____ | | Other: [ ]: |____________________________________________________________________________ | SIS COORDINATOR: A. Amador | ____________________________________________________________________________ | SIGNATURES: | | Approval Position Name Date | | | | Ground S/W System Engineer W. Sible ____________________ __________ | | | | Concurrence: | | | | System: | | Program Position Name Date | | | | MSS: SYS E A. Amador ____________________ __________ | | | | SEQGEN COG E V. Wang ____________________ __________ | | | | SEQGEN COG P J. Dale ____________________ __________ | | | | SEG COG E E. Erwin ____________________ __________ | | | | SEG COG P K. Miller ____________________ __________ | | | | SCANOPS COG E/COG P S. Javidnia ____________________ __________ | | | | SEQTRAN COG E/COG P T. Loesch ____________________ __________ | | | | MCHS COG E/COG P C. Sagoian ____________________ __________ | | | | SVC: SYS E J. Anderson ____________________ __________ | | | | C-Kernel COG E K. Deutsch ____________________ __________ | | | | COG P N. Bachman ____________________ __________ | | | | SNIPGEN COG E/P K. Deutsch ____________________ __________ | |____________________________________________________________________________| SIS 211-05 (Continued) ____________________________________________________________________________ | | | OES: SYS E J. Hofman ____________________ __________ | | | | RSEF COG E/COG P B. Rein ____________________ __________ | | | | | | NAV: SYS E J. Ekelund ____________________ __________ | | | | OMAS COG E R. P. Davis ____________________ __________ | | | | OMAS COG P W.M. Owen ____________________ __________ | | | | | | DMS: SYS E C. Hidalgo ____________________ __________ | | | | AQQC COG E/COG P T. Specht ____________________ __________ | | | | SCEGEN COG E/COG P J. Schmidling ____________________ __________ | |____________________________________________________________________________| Custodian: V. Wang 625-610 PROJECT GALILEO SOFTWARE INTERFACE SPECIFICATION S/C Event File (SEF) SIS #211-05 P2 June 07, 1994 ABSTRACT: This SIS describes the form and syntax of each S/C Event File (SEF) which is a product of the Mission Sequence System (MSS). Each SEF will contain a header that identifies and describes the scope of the file, plus a body which provides a time ordered list of events occurring in a particular sequence. CHANGE CONTROL: The Galileo change control procedures specified in STAP 2.17 apply to this document. Jet Propulsion Laboratory California Institute of Technology JPL D-296625-610 SIS 211-05 P2 Rev. A DOCUMENT CHANGE LOG Change Date Affected Portions Original 07/24/81 All Change 1 05/17/83 Indicated by change bars Original Phase 2 Build C 2/5/85 All Change 1 07/10/85 Indicated by change bars per SCR 749 Change 2 02/19/86 Indicated by change bars per SCR 693 Change 3 09/10/86 Indicated by change bars per SCR 919 Change 4 06/03/87 Indicated by change bars per SCR A298 Change 5 09/01/88 Indicated by change bars per SCRs 715A,881, A361 and A583 Change 6 1/09/89 Indicated by change bars per SCR A764 Rev. A, Phase 2 06/07/94 Indicated by change bars per SCR B400 List of TBD Items Page Resolution Date Item None 625-610 SIS 211-05 P2 Rev. A SECTION 1 GENERAL DESCRIPTION 1.1 CONTENT OVERVIEW This Software Interface Specification (SIS) provides a people-oriented form and syntax for displaying sequence data within the Mission Operation System (MOS) environment. The header section identifies the type of file, its creation date, scope and genealogical ancestry. The body section lists sequence components, special subsystem status summaries and other events. 1.2 SCOPE The format and syntax specifications in this document apply to all phases of the Galileo Mission. 1.3 APPLICABLE DOCUMENTS 625-640-211031 SEQGEN SRD 625-645-211031 SEQuence GENeration User's Guide MOS-GLL-4-211 Functional Requirement, Galileo Mission Sequence System 625-640-211061 MCHS SRD 625-640-211101 SEG SRD SIS 211-13 Standard Sequence Data File (SSDF) 625-540 Sequence Component Definition Document Volume 2: Profile Activity Catalog Volume 3: Block Dictionary 625-675-211031 Algorithm Dictionary GLL-3-290 Command Structure and Assignments MCCC1843-1 LIB*CLIB$ Special Feature Library, Sections 3.1 - 3.3 UP 4144.31 Sperry Univac 1100 Series Executive, Volume 3, Section 11.2.3, System Data Formats 625-610 SIS 211-05 P2 Rev. A UP 8478 Sperry Univac 1100 Series Processor Common Input/Output System (PCIOS), Section 5.2, System Data Format 1.4 SUBSYSTEM SITING 1.4.1 Interface Location, Medium This interface shall be implemented in an ASCII element of a program file in Univac Standard Data File Format (SDFF). It will be in human-readable form and printouts will be generated. 1.4.2 Data Source, Destinations and Transfer Method The S/C Event File (SEF) is generated by the CHECKER processor of the SEQGEN Program. It is read by the MCHS-SETUP Program (in SEQTRAN) which generates "PREDICTS" for sequences simulated in the MCHS. It is also read by SEG in order to create a Sequence Of Events (SOE). SNIP reads the SEF to obtain SSI shutter time and PWS event time, NIMS OBSTAB reads the SEF to obtain NIMS events, and, SNIP, OBSTAB and DMT AQQC all read the SEF for playback process predicts. C-KERNEL reads SCANOPS Predicts file. The SEF is read by E-Kernel generation software (name TBD), which is operated by GLL SDT. 1.4.3 Pertinent Relationships with Other Interfaces N/A 1.4.4 Labeling and Identification (Internal/External) The original file name will be written into the header in the form: Qualifier*File.Element/Version 625-610 SIS 211-05 P2 Rev. A SECTION 2 INTERFACE CHARACTERISTICS 2.1 HARDWARE CHARACTERISTICS 2.1.1 Special Equipment and Device Interfaces None. 2.1.2 Special Setup Requirements None. 2.2 VOLUME AND SIZE Each SEF shall be limited to 10000 parameter sets. A parameter set contains all the data necessary to invoke a given sequence component. Parameter sets shall conform to the requirements of the Standard Sequence Data File, see SIS 211-13. There shall be no more than 15 EPOCH header records (see 4.2-1). 2.3 INTERFACE MEDIUM CHARACTERISTICS The file shall be written in Univac Standard Data File Format (SDFF). This is the format described in the Univac Executive manual and used by Univac Fortran V, Athena Fortran and LIB*CLIB$ routines ELT READ and ELT WRITE. It is not the format described in the Univac PCIOS manual and used by Univac FTN and PL/1. 2.4 FAILURE PROTECTION, DETECTION AND RECOVERY FEATURES 2.4.1 File Backup Requirements This is handled by the individual software systems, e.g. the MSS ARCHIVE subsystem. 2.4.2 Security/Integrity Measures These files have no inherent security because they are directly text editable using system routines. 2.5 END-OF-FILE (OR MEDIUM) CONVENTIONS End-of-File conventions shall be in accordance with Univac Standard Data File Format (SDFF). 625-610 SIS 211-05 P2 Rev. A SECTION 3 ACCESS 3.1 PROGRAMS USING THE INTERFACE It is required for SEQTRAN, SCANOPS and SEG to access this file. 3.2 SYNCHRONIZATION CONSIDERATIONS 3.2.1 Timing and Sequencing Characteristics. There shall be a BEGIN and a CUTOFF time in the header section. Each event in the body of the file shall have a time which falls in between BEGIN and CUTOFF. In this document "time" refers to Spacecraft Event Time, which is Universal Time (UT, also referred to as GMT) of execution on the spacecraft bus. Unless otherwise specified, "time" is expressed in the form "yy-ddd/hh:mm:ss.fff, i.e. years, days of year, hours, minutes, seconds and fractions of a second. Within the body of the file the events shall be arranged in time order. 3.2.2 Effective Duration The effective duration is the difference between the BEGIN and the CUTOFF times of the header section. 3.2.3 Priority Interrupts N/A 3.3 INPUT/OUTPUT PROTOCOLS, CALLING SEQUENCES N/A 625-610 SIS 211-05 P2 Rev. A SECTION 4 DETAILED INTERFACE SPECIFICATIONS 4.1 STRUCTURE AND ORGANIZATION OVERVIEW The SEF file shall consist of an ASCII element of a program file. There will be exactly one file per element. The element shall consist of 132- character images. The file shall be organized into a header section and a body section as follows: Keyword Data Content # $$GLL SPACECRAFT EVENT FILE # * # *LEVEL # *PREP # *RUNID # *PROGRAM # *CREATION