431-HDBK-000076 Revision - Effective Date: To be Added Upon Release
advertisement
431-HDBK-000076 Revision Effective Date: To be Added Upon Release Expiration Date: To be Added Upon Release DRAFT Robotic Lunar Exploration Program Lunar Reconnaissance Orbiter Mission Telemetry & Command (T&C) Database (DB) Style Guide 07/15/2016 Goddard Space Flight Center Greenbelt, Maryland National Aeronautics and Space Administration CHECK WITH RLEP DATABASE AT: https://lunarngin.gsfc.nasa.gov TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT SIGNATURES Prepared by: Mehul Patel Test Conductor Honeywell, Code 444 Date Maxine Saylor Test Conductor Honeywell, Code 444 Date Date Dave Everett Mission Systems Engineer NASA/GSFC, Code 599 Date Reviewed / Approved by: Richard S Saylor, Jr. Ground System Lead Honeywell, Code 444 Arlin Bartels Payload Systems Manager NASA/GSFC, Code 431 Date Joanne Baker I&T Manager NASA/GSFC, Code 568 Date Mike Blau Flight Software Lead NASA/GSFC, Code 582 Approved by: Craig Tooley LRO Project Manager GSFC/NASA, Code 431 Date ii Date LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT PREFACE This document is a Lunar Reconnaissance Orbiter (LRO) Project Configuration Management (CM)-controlled document. Changes to this document require prior approval of the applicable Configuration Control Board (CCB) Chairperson or designee. Proposed changes shall be submitted to the LRO CM Office (CMO), along with supportive material justifying the proposed change. Changes to this document will be made by complete revision. Questions or proposed changes concerning this document shall be addressed to: LRO Configuration Management Office Mail Stop 431 Goddard Space Flight Center Greenbelt, Maryland 20771 iii LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT LUNAR RECONNAISSANCE ORBITER DOCUMENT CHANGE RECORD Sheet: 1 of 1 REV LEVEL DESCRIPTION OF CHANGE Rev - iv APPROVED BY DATE APPROVED LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT LIST OF TBDS/TBRS Sheet: 1 of 1 Item No. Location Summary 1 2 3 4 5 6 v Ind./Org. Due Date LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT TABLE OF CONTENTS 1.0 INTRODUCTION ............................................................................................... 1-1 1.1. 1.2. 1.3. Purpose and Scope ................................................................................. 1-1 Document Structure ................................................................................ 1-1 Applicable Documents ............................................................................. 1-1 2.0 MISSION OVERVIEW ....................................................................................... 2-1 3.0 ITOS DATABASE STYLE GUIDELINES .......................................................... 3-3 3.1. 3.2. Mnemonic Naming Convention ............................................................... 3-3 3.1.1. Naming Assignments and Abbreviations ..................................... 3-4 3.1.2. Conversion Definition Naming Convention .................................. 3-8 Single Database (SDB) Files ................................................................... 3-8 3.2.1. SDB File Format .......................................................................... 3-9 3.2.2. Summary ................................................................................... 3-18 A. TELEMETRY DATABASE (SDB) FILE EXAMPLE ......................................... A-1 B. PSEUDO-TELEMETRY DATABASE (SDB) FILE EXAMPLE ......................... B-1 C. COMMAND DATABASE (SDB) FILE EXAMPLE............................................ C-1 D. ACRONYM LIST .................................................................................................. 2 LIST OF TABLES Table 3-1: Prefix Assignments .....................................................................................3-4 Table 3-2: Component Assignments ............................................................................3-5 Table 3-3: Mnemonic Description Abbreviations ..........................................................3-6 Table 3-3: Mnemonic Description Abbreviations Cont..................................................3-7 Table 3-4: Unit Abbreviations .......................................................................................3-8 Table 3-2: Telemetry (M&T) Record Format ...............................................................3-12 Table 3-3: M&T Telemetry Packet Header Records ....................................................3-16 vi LRO Mission Operations PlanT&C Database Style Guide 1.0 431-HDBK-000076 Revision DRAFT INTRODUCTION The Lunar Reconnaissance Orbiter (LRO) is the first robotic mission of the Robotic Lunar Exploration Program (RLEP). The primary objective of the LRO mission is to conduct investigations that support future human exploration of the Moon. The launch readiness date for LRO is October 2008. 1.1. PURPOSE AND SCOPE The LRO Project has multiple teams contributing database inputs in order to generate a fully integrated database for use by the Integrated Test and Operations System (ITOS) ground system. Therefore, it is necessary to define a common format and naming convention to avoid conflicting inputs and to ensure usability. This document contains guidelines for naming command mnemonics, telemetry mnemonics, discrete names, analog conversion definitions, limit definitions, and database filenames as well as the overall format of the files and individual record types. All teams contributing database inputs to the LRO ITOS ground system shall follow these guidelines. 1.2. DOCUMENT STRUCTURE The following describes the document breakdown structure: Section 1: Introduction – This section describes the purpose and scope of the database style document. Section 2: Observatory Overview – This section provides a high-level overview of the LRO spacecraft (SC) and instruments. Section 3: ITOS Database Style Guidelines – This section describes the elements required for the ITOS database. Guidelines are provided for the format of the database files and records as well as the conventions for naming mnemonics and files. 1.3. APPLICABLE DOCUMENTS The following list contains the reference material used to generate this document. Refer to these sources to support, further define, and clarify the information in this document. 431-OPS-000042 http://itos.gsfc.nasa.gov/ Lunar Reconnaissance Orbiter Launch and Commissioning Handbook Integrated Test and Operations System (ITOS) website 1-1 LRO Mission Operations PlanT&C Database Style Guide 2.0 431-HDBK-000076 Revision DRAFT MISSION OVERVIEW LRO is the first mission of the RLEP. The goal for the RLEP is to prepare for future human exploration of the Moon. LRO specific objectives are: Characterize the lunar radiation environment, biological impacts, and potential mitigation Determine a high resolution global, geodetic grid of the Moon in 3 dimensions Assess in detail the resources and environments of the Moon’s polar cap regions Perform high spatial resolution measurement of the Moon’s surface The LRO instrument complement includes six instruments. Together, all six instruments allow LRO to meet the mission objectives. LRO will also fly a technology demonstration instrument called the Mini-Radio Frequency (RF). The purpose of the Mini-RF is to demonstrate new radar technology for future use in planetary resource mapping. The Mini-RF payload will operate on a non-interference basis throughout the mission. As of the creation of this document, the major spacecraft and subsystem functions are: Command and Data Handling (C&DH) ─ Provides SC processor for attitude control algorithms, command/telemetry processing. ─ Communication cards provide the interfaces to the S-band/Ka-Band RF systems. ─ Hardware command decoding for computer-free recovery ─ Provides high speed and low speed data bus to the instruments and SC components ─ Provides large volume recorder for measurement data and orbiter housekeeping (HK) Guidance Navigation and Control (GN&C) ─ Three axis control with reaction wheels ─ Star Trackers (STs), Inertial Measurement Unit (IMU), Coarse Sun Sensors (CSS) used for attitude control ─ Momentum management is performed periodically with thrusters ─ Control pointing of the solar array (SA) and High Gain Antenna (HGA) gimbals Communication ─ Ka-band transmitter for high rate measurement downlink using the HGA ─ S-Band transponders connected to the omni antennas and HGA for receipt of ground commands and telemetry downlink ─ Orbit determination via turnaround ranging Power ─ SA located on gimbals for power generation ─ One Lithium Ion battery for launch and 48 minute lunar occultations ─ Power switching and distribution ─ Battery charging control 2-1 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT Mechanical & Mechanism ─ Deployable SAs and HGA Flight Software (FSW) ─ Complex algorithms computed on central processor including Attitude Control System (ACS), stored commanding, telemetry and measurement data processing, and fault detection and correction. ─ SC time distribution/maintenance The six instruments are: Lunar Orbiter Laser Altimeter (LOLA): LOLA will determine the global topography of the lunar surface at high resolution, measuring landing site slopes and search for polar ice in shadow regions. Lunar Reconnaissance Orbiter Camera (LROC): LROC will acquire targeted images of the lunar surface capable of resolving small-scale features that could be landing site hazards. LROC will also produce wide-angle images at multiple wavelengths of the lunar poles to document the changing illumination conditions and potential resources. Lunar Exploration Neutron Detector (LEND): LEND will map the flux of neutrons from the lunar surface to search for evidence of water ice and provide measurements of space radiation environment which can be useful for future human exploration. Diviner Lunar Radiometer Experiment (DLRE): Diviner will map the temperature of the entire lunar surface at 300-meter horizontal scales to identify cold-traps and potential ice deposits. Lyman-Alpha Mapping Project (LAMP): LAMP will observe the entire lunar surface in the far ultraviolet (UV). LAMP will search for surface ice and frost in the Polar Regions and provide images of permanently shadowed regions illuminated only by starlight. Cosmic Ray Telescope for Effects of Radiation (CRaTER): CRaTER will investigate the effect of galactic cosmic rays on tissue-equivalent plastics as a constraint on models of biological response to background space radiation. 2-2 LRO Mission Operations PlanT&C Database Style Guide 3.0 431-HDBK-000076 Revision DRAFT ITOS DATABASE STYLE GUIDELINES The following sections outline style guidelines related to the content and format of ITOS database files and records. Each LRO team responsible for generating database inputs is expected to adhere to these guidelines. 3.1. MNEMONIC NAMING CONVENTION Mnemonics may contain only alphabetic and numeric characters. For LRO, due to the length limitation, the use of underscores in mnemonic names is not allowed. In general, each mnemonic name (telemetry, command, pseudo-mnemonic) must be unique and limited to a maximum length of 20 characters, although a length of no more than 15 characters is preferred. LRO telemetry and command mnemonics for spacecraft subsystems and instruments, ground support equipment telemetry and command mnemonics and pseudo-telemetry mnemonics will have the following naming convention: Format: <subsys><component><description><value_state> Where: subsys: required 2-character field as assigned in Table 3-1. Indicates the major subsystem/instrument associated with the telemetry point/command. component: required 2 to 5-character field as assigned in Table 3-2. (If your component was not defined in Table 3-2, please come up with your own unique designation.) Indicates the flight software task, module, board, circuit, component or GSE rack/component where the value was generated or where the command is intended to go. In the case of duplicate components, please end the component field with the component number or letter designation (ie. Star Tracker #1 = ST1, Reaction Wheel #4 = RW4) description: required field of variable length. Describes the function of the telemetry point. Please follow designations for standard descriptions in Table 33. value_state: optional field of variable length. Indicates the functional element value or state. This field may be left blank if the telemetry point is adequately identified in the description field. Please follow designations for values/states in Table 3-3. The remaining portion of the mnemonic name may be assigned at the discretion of the developer. However, it is strongly recommended that the mnemonic name utilize a sequence of characters that make it easily identifiable to the end user, the satellite operations team. For example, if a particular type of temperature sensor is widely used throughout the spacecraft, a mnemonic based on its location rather than the type of sensor is preferred. All pseudo-mnemonic names must end in an “X” so that they are easily distinguishable from telemetry from the spacecraft or Ground Support Equipment (GSE). 3-3 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT 3.1.1. Naming Assignments and Abbreviations To avoid duplicating names for different subsystem database inputs, it is essential that a common naming convention be employed. Table 3-1 defines the two-character prefix to be used when naming all commands, telemetry mnemonics, pseudo-mnemonics, subsystem identifiers, discrete names, analog conversions, and limits. A pseudomnemonic is used to provide further manipulation of telemetry mnemonics, such as logical expressions, concatenation, scientific expressions, etc. The combination of two or more telemetry mnemonics to perform an engineering calculation is a typical usage. Table 3-1: Prefix Assignments Prefix Subsystem Assignment Spacecraft Subsystems: AC Attitude Control Subsystem hardware components and any ACS/GNC-related Flight Software Tasks PD Propulsion/Deployment Electronics PW Power Subsystem generation and distribution RF Radio Frequency Communications/transponders/transmitter/switches TH Thermal Control Subsystem FW C&DH Flight Software CD C&DH Hardware GS Ground Support Equipment (GSE) Instruments: CR CRaTER DV Diviner LP LAMP LN LEND LO LOLA LR LROC MR Mini-RF 3-4 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT Table 3-2 defines the designation for subsystem components to be used when naming all commands, telemetry mnemonics, pseudo-mnemonics, subsystem identifiers, discrete names, analog conversions, and limits. A “#” at the end of the abbreviation indicates the number or letter designation for the component should be identified as part of the abbreviation. If your component is not listed please create your own unique abbreviation and use it consistently. Table 3-2: Component Assignments Abbreviation CSS# GY# RW# ST# Abbreviation DDA DIB LVPC MAC SBC Abbreviation HGA KCOM KPC KTA SCOM SW XMTR XPR Abbreviation DREB DRLE Abbreviation FDV HPT IT# IU LV OCT# Abbreviation BAT OM PMC SA SAM Attitude Control Subsystem Description Coarse Sun Sensor Gyro Reaction Wheel Star Tracker C&DH Hardware Description Disk Drive Assembly Disk Interface Board Low-Voltage Power Card Multi-Analog Card Single Board Computer Communications Description High Gain Antenna Ka-Band Communications Ka-Band Electronics Power Card Ka-Band Transmitter Amplifier (Ka TWTA) S-Band Communications Switch (RF Switch) Transmitter Transponder Diviner Description Diviner Remote Electronics Box Something on Diviner ??? Propulsion Description Fill/Drain Valves Helium Pressure Tank 80 Newton Insertion Thrusters Inhibit Unit Latch Valve 20 Newton Orbital Control Thrusters Power Description Battery Output Module Power Monitor Card Solar Array Solar Array Module Flight Software Abbreviation Description ATP Absolute Time Processor ATS Absolute Time Sequence CI Command Ingest CK Checksum ES Event Services FDH Fault Detection Handling FM File Manager FT CFDP File Transfer HK House Keeping Data Storage HS Health & Safety Manager IM Instrument Manager MD Memory Dwell MM Memory Manager MS EDAC Memory Scrubber RTP Relative Time Processor RTS Relative Time Sequence SB Software Bus SC Stored Commanding SH Software Scheduler ST Self Test TO Telemetry Output TS Telemetry Services TM Time Services XS Executive Services Lunar Reconnaissance Orbiter Camera Abbreviation Description NACL Narrow-angle Camera Left NACR Narrow-angle Camera Right SCS Sequence Control System WAC Wide-angle Camera Mechanisms Abbreviation Description HGGC# High Gain Gimbal Controller SAGC# Solar Array Gimbal Controller 3-5 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT Table 3-3 suggests abbreviations for standard mnemonic descriptions. Please follow these abbreviations when possible. If needed, please create your own unique decription and use it consistently. Table 3-3: Mnemonic Description Abbreviations Abbr ADDR AGC AMP ANG ANT APID ARM AUX BAT BDY BOT BP BS BUF BUS CAL CCD CFG CHN CKSM CLD CLS CLK CLR CMD CNT CNV COHO CTRL DET DIR DIS DLY DMP DNLK DRV DWL ENG EEPR EL ENA Description Address Automatic Gain Control Amplitude Angle Antenna CCSDS Application ID Arm (pyro) Auxillary Battery Body Bottom Baseplate Bias Buffer Bus Calibrate/Calibration Charge Coupled Device Configuration Channel Checksum Cold Closed Clock Clear Command Count Convert/Converter Coherent Control Detector Direction Disable Delay Dump Downlink Drive Dwell Engineering EEPROM Elevation Enable Abbr ENC ERR EXE FEP FIRE FLG FLT FMT FN FPGA FRM FS FW FWD GCE GN HI HK HTR HW I ID INIT INST INT LCK LD LIM LN LO LSB LVL M MAG MAX MD MEM MF MIN MIRR MOD 3-6 Description Encode / Encoder Error Execution Front End Processor Fire (pyro) Flag Filter Format Fine Field Programmable Gate Array Frame Frequency Standard Filter Wheel Forward Gimbal Control Electronics Gain High Housekeeping Heater Hardware Current Identification Initialization Instrument Internal Lock Load Limit Line Low Least Significant Bits Level Minus Magnetic Maximum Mode Memory Mainframe / Main Frame Minimum Mirror Modulation LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT Table 3-3: Mnemonic Description Abbreviations Cont. MON MSB MSG MUX NOCO NOOP OC OFF ON OP OPHTR OPN OR OS OSC OT OV OVR P PKT PB PNT POS PRG PROM PRS PRV PS PWR PYRO RAM RCVD RCVR REC REF REJ REV RF RLY RPM RPT Monitor Most Significant Bits Message Multiplexer Non-Coherent No Operation Overcurrent Off On Operation Operational Heater Open Override Offset Oscillator Over Temperature Overvoltage Over Positive Packet Playback Point / Pointing Position Program Programmable Read-Only Memory Pressure Previous Power Supply Power Pyrotechnic Random Access Memory Received Receiver Record Reference Reject Reverse Radio Frequency Relay Revolutions per Minute Report RST RT SCI SA SAS SEL SH SHNT SHT SHTR SIG SN SPD SPN SPR STAT STW SW SYNC SYS TMP TBL TDRS TELE TLM TNK TOP TRQ ULK UPD UPLK UTC V VAL VC VEC VEL VLV WRM WD 3-7 Reset Real Time Science Solar Array Solar Array Simulator Select Safehold Shunt Shutter Survival Heater Signal Sensor Speed Spin Spare Status / State Stow Software Synchronize System Temperature Table TDRSS Telescope Telemetry Tank Top Torque Unlock Update Uplink Universal Time Coordinated Volts Value Virtual Channel Vector Velocity Valve Warm Word LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT Table 3-4 provides the standard unit abbreviations for LRO. Please adhere to these abbreviations. If you require an abbreviation not listed please make sure it is unique and easily identifiable by the Flight Operations Team. Table 3-4: Unit Abbreviations Abbreviation % A ARCS AU BOOL bps Bps C CM CM/C CNT CYC DAYS DEG eV FRMS Gbps GBps hr Hz I K Kbps KBps KG/M2 Unit Measurement Percent Amp Arc Seconds Astronomical Units Boolean bits per second Bytes per second Degrees Centigrade Centimeters Centimeters per count Counts Cycle Days Degrees Electron Volts Frames Giga bits per second Giga Bytes per second Hours Hertz Current Degrees Kelvin Kilo bits per second Kilo Bytes per second Kilograms per square meter Abbreviation KHz KM KM/s M mA Mbps MBps msec NEG NM NMS OHMS PIX POS PULS R RAD RPM RPS sec uAmp uSec V V/CT W Unit Measurement Kilo Hertz Kilo Meters Kilo Meters per second Meters Milli Amp Mega bits per second Mega Bytes per second Milli Seconds Negative Newton Meter Newton Meters Squared Ohms pixels Positive Pulse Degrees Rankine Radians Revolutions Per Minute Revolutions per second Seconds Nano Amp Nano Second Volts Volts per count Watts 3.1.2. Conversion Definition Naming Convention All conversion definition names for limits, discrete conversions – telemetry and command, and analog conversions must also begin with the assigned two-character prefix in Table 3-1 and may contain only alphanumeric characters. Like mnemonics, the conversion names are limited to 15 characters, but unlike mnemonics, underscores are allowed when naming these elements. 3.2. SINGLE DATABASE (SDB) FILES For each LRO subsystem, two single database (SDB) files must be generated: one for telemetry-related database inputs and one for command-related database inputs. A third SDB file may be created for subsystems that choose to define pseudo-telemetry. 3-8 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT The filename for all SDB files will start with the assigned two-character prefix (nn) from Table 3-1, followed by an “x” if the file contains pseudo-telemetry, indicate whether the file contains telemetry or command information, and end with a ‘.sdb’ suffix. Telemetry SDB filename: nn_tlm.sdb Command SDB filename: nn_cmd.sdb Pseudo-telemetry SDB filename: nnx_tlm.sdb Note that all filenames will use lowercase characters. The following are examples of SDB filenames: Attitude Control Subsystem telemetry Filename: ac_tlm.sdb CRaTER pseudo-telemetry Filename: crx_tlm.sdb LAMP commands Filename: lp_cmd.sdb The exception to these requirements is for the Flight Software (FSW) subsystem. The FSW subsystem may generate a single SDB file per software task. The naming convention for these files should follow the following convention. The filename should start with the assigned two-character prefix for FSW (FW), followed by the two-letter abbreviation for the flight software task (refer to Table 3-2), followed by an “x” if the file contains pseudo-telemetry, indicate whether the file contains telemetry or command information, and end with a ‘.sdb’ suffix. For example: Flight Software Telemetry Output Task command SDB filename Filename: fwto_cmd.sdb 3.2.1. SDB File Format To ensure readability, the SDB files will adhere to specific formatting guidelines. SDB file comments and mnemonic descriptions should make use of both upper and lower case text. However, all other content of SDB files will be uppercase only. The following sections describe both the contents and the format of the telemetry (TLM), pseudotelemetry and command (CMD) SDB files. 3.2.1.1. File Header All SDB files must contain the LRO SDB file standard header. The format for this header can be found in the SDB file examples in the Appendix. The information in the header, Date, Author, Change Description, should be updated in detail every time a change is made to the SDB file. Also in the header, code should be included which will 3-9 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT be used during the Integration and Testing (I&T) phase to keep track of revisions using the Current Version System (CVS) software. This code looks like $Id: nn_tlm.sdb,v $ where the nn_tlm.sdb is the actual name of the SDB file. 3.2.1.2. ITOS Field Delimiters Within any SDB file, fixed column widths will be used for each field to ensure optimum readability. A field (column) delimiter definition record (DEL record type) will be defined in the first record in each SDB file. For LRO, the vertical bar (“|”) is the standard field delimiter. Refer to Appendix A for an example. 3.2.1.3. Comments Comments and blank lines will be used liberally to distinguish between sets of telemetry packets, commands with multiple FLD/SUB records, and configuration control information, etc. Comments begin with a ‘#’ character and continue to the end of the line. To place a ‘#’ in a description field, use ‘\#’ or quote the entire description text. 3.2.1.4. 3.2.1.4.1. Telemetry SDB File Subsystem Identifiers Telemetry and command mnemonics may be assigned to one or more subsystems. The subsystem name is used to limit database searches or reports and for general information. Subsystem identifiers (SSI record type) have a maximum length of 15 characters, and must start with the assigned two-character prefix from Table 3-1. These records will be included as part of the telemetry SDB file. Refer to Appendix A for an example. 3.2.1.4.2. Map Records The basic definition sequence of a telemetry stream starts with the definition of a MAP record for a specific segment of the stream. The MAP record defines general information about a given Application ID (APID) stream referred to as the packet attributes. For LRO, a MAP record should be defined for each packet that is defined. Refer to the ITOS documentation for a definition of the fields of the MAP record and follow the ITOS documentation guidelines in defining these records. Refer to Appendix A for an example. 3.2.1.4.3. Start Byte Offset The Start Byte Offset (SBO record type) provides an initial reference byte in the specified telemetry packet (or APID) from which the start bytes of the subsequent telemetry mnemonics are offset. This value is zero if the first data point is at the beginning of the packet. A non-zero value indicates that the subsequent data points begin at X bytes from the beginning of the packet. This is an especially useful feature when a large number of mnemonics are defined in a single file and not all bits or bytes in the packets are initially defined. This allows the unused parts of the packet to be 3-10 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT skipped and more easily defined later without having to modify the starting byte field in a significant number of subsequent telemetry records. 3.2.1.4.4. M&T Telemetry Records The telemetry SDB file assigns each telemetry data point to a recognizable name, or mnemonic, and is defined by an M&T telemetry record (M&T record type). The M&T records will be organized by (APID) and specified in the same byte order as the data is organized in the telemetry packet. In addition to a mnemonic name, each telemetry record includes fields to identify which telemetry packet contains the data and the exact location within the packet. All the available fields and LRO defined requirements for those fields are outlined in Table 3-2. Appendix A provides an example of a telemetry SDB file that shows how these fields may be defined. Please note that the M&T record type is not an ITOS recognized record type. It is a combination of the ITOS recognized TLM and PKT record types. A custom script must be used in order to build the ITOS database from the SDB files containing the M&T records. This script will break apart the M&T record type into the TLM and PKT record types that ITOS does recognize. More details concerning the script will be supplied in the T&C Database Management Plan. 3-11 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT Table 3-2: Telemetry (M&T) Record Format Field Title Description Field Format 1 Record Type 2 Operation Symbol 3 Mnemonic 4 Packet ID Required. Application ID (APID) 5 Data Type Required. The size of the mnemonic's value, in Alphanumeric bits or, if the ``type'' is a string type, in bytes. If (representing blank, this field value will be inferred from the specific data types) type, if possible. For example, a U12 defaults to 16 bits. Signed and unsigned integers may not be larger than 32 bits; floating-point values may be 32 or 64 bits; and strings have no default size. Note that the size given here is used to limit the range of values that STOL may assign to a mnemonic. For example, a size of 2 bits limits an unsigned integer mnemonic's values to the range 0 to 3. See Section the ITOS documentation for additional details on data types. Required. Describes type of record to follow. For Alphanumeric telemetry, use ‘M&T’. Required. Contains an operation symbol, either Symbol `+' or `-'. The `+' symbol means the record has new or updated information; the `-' symbol means the information for the identifier should be deleted from the existing database. Note that deleting a telemetry mnemonic definition will delete all occurrences of that mnemonic in all packets. Notice that in order to change an identifier, such as a telemetry mnemonic name, you must delete the existing record and add a new record with the same data, but a different name. If you wish to move a mnemonic's value from one source packet to another, you must remember to delete the `pkt' entry for the mnemonic in the first packet. If records are not deleted as required, the database will be cluttered with extraneous information and ground system performance may be degraded. Required. Name of the telemetry data point. Alphanumeric Follow naming guidelines in Section 3.1.1. 3-12 Integer LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT Field Title Description Field Format 6 Start Byte Required. Starting byte where the telemetry data point begins, measured from the beginning of the packet primary header. In other words, the first byte in the packet primary header is byte 0. The starting byte plus the length of the packet item in bytes must not exceed the maximum packet length of 65529. Integer 7 Start Bit Required. Starting bit, within the start byte, for where the telemetry data begins Integer 8 Bit Length Required. Number of bits utilized for the given telemetry data point Integer 9 Units Required if possible. Engineering units string (up to 64 chars). Used when displaying the mnemonic's value. Conform to Table 3-4. Alphanumeric 10 Subsystem Name Required. Indicates which subsystem(s) (as defined by SSI records) this mnemonic is associated with. Up to 16 subsystem names may be specified using spaces to separate the names. Alphanumeric 3-13 LRO Mission Operations PlanT&C Database Style Guide Field Title 11 Event Flag 431-HDBK-000076 Revision DRAFT Description Single alphanumeric character, used to mark mnemonics, which are used to telemeter spacecraft events. This field indicates event packets that contain an event code, a subsystem identifier, a severity code, and four datapoints. The default is ' '. `C' Event code Field Format Alphanumeric `S' Subsystem ID `R' Severity `1' Data Point 1 `2' Data Point 2 `3' Data Point 3 `4' Data Point 4 12 Limits 13 Conversion This field may contain a name, a number, or a Floating Point name and a number separated by white space. If the field contains a name, that name is the limit definition (LIM) that specifies the red/yellow limits for this mnemonic. (If the field does not contain a name, the mnemonic has no red/yellow limits). If the field contains a number, that number is the delta limit for the mnemonic. The name of the analog (ALG) or discrete (DSC) conversion to apply to this mnemonic value when displaying the value or if it is referenced through the STOL `p@' operator. If blank, the mnemonic has no conversion. 3-14 Alphanumeric LRO Mission Operations PlanT&C Database Style Guide Field Title 14 Selector Name 15 Initial Value 16 ReadOnly Flag 17 Array Length 431-HDBK-000076 Revision DRAFT Description Currently unused. Leave blank. Field Format n/a The mnemonic's initial value. Generally, the rule is Floating Point to leave blank (uninitialized). Required. `T' or `F'. If `T', normal STOL assignment directives will not be permitted to change this mnemonic's value. The default is `F'. Reserved for future use. Array length (default = 1). Alphanumeric Integer 18 Array Offset Reserved for future use. The offset, in bits, between array elements. Not used unless the mnemonic is an array. If blank, the default value comes from field 4. If 0, only one array element is extracted. Integer 19 Array Index Reserved for future use. Used for mnemonic arrays, the elements of which are not telemetered at constant intervals in a packet or are not in the same packet. Normally, array elements are in one packet at a constant distance from one another. The “offset between array elements” (field 16) gives this constant distance. Integer 20 Description Required. A brief description of the telemetry point identified by the mnemonic (limited to 64 characters). For additional detail, the <html> indicator allows an unlimited number of text characters to be included. 3.2.1.4.5. Alphanumeric Limit Records The LIM record defines a limit range for an integer or floating-point telemetry mnemonic. A limit set consists of two concentric ranges called the “yellow limits” and “red limits”. A limit definition record may contain more than one limit set. The system chooses which limit set to apply to a mnemonic using the “limit switch”, explained below. Refer to Appendix A for an example. Refer to the ITOS documentation for a description/definition of the LIM record fields. A definition in record fields 1-3, and 12 is required for LRO. 3.2.1.4.6. Discrete Conversion Records Discrete conversions, defined in DSC records, transform a range of numeric values into a set of text strings. The telemetry value is compared to each range in the set. If the value falls within the specified range, the state text associated with that range is displayed. The high value of one range can be the same as the low value of the next 3-15 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT range; otherwise, overlapping ranges are discouraged. Refer to Appendix A for an example. Refer to the ITOS documentation for a description/definition of the DSC record fields. A definition in record fields 1-6, and 9 is required for LRO. 3.2.1.4.7. Analog Conversion Records Analog conversions, defined in ALG records, transform an integer number of “counts” (the output of an analog to digital converter, for example) into a floating-point value in “engineering units”, such as volts, amps, degrees, etc. The ALG record defines the coefficients for an 8th order polynomial. The integer or floating-point telemetry value is applied to the polynomial and the result is a floating-point value. Refer to Appendix A for an example. Refer to the ITOS documentation for a description/definition of the ALG record fields. A definition in record fields 1-12 is required for LRO. 3.2.1.4.8. Telemetry Packet Header Records An exception to the general telemetry mnemonic naming convention is for telemetry packet header field mnemonics, which will be standardized with the format of the single character ‘H’, followed by a three hexidecimal-digit telemetry packet Application ID (APID) and a field name, respectively. Table 3-3 contains the fields for a representative packet, APID xxx. Please note that not all packet secondary headers will be the same for all APIDs, so please use this table as a guide instead of the standard with respect to the secondary header. Packet header records shall be included as M&T records in all telemetry SDB files at the start of each APID for that subsystem. Table 3-3: M&T Telemetry Packet Header Records Start Byte HxxxPKTVNO 0 Mnemonic Start Length in Bit Bits 0 3 Data Type U1 HxxxPCKT HxxxSHDF 0 0 3 4 1 1 U1 U12 HxxxAPID HxxxSEGF 0 2 5 0 11 2 U12 U1 HxxxCNT 2 2 14 U12 HxxxPLEN HxxxSECH 4 6 0 0 16 16 U12 U12 3-16 Description APID xxx Packet ID Version Number APID xxx Packet ID Type APID xxx Packet ID Secondary Header Flag APID xxx Packet ID Application ID APID xxx Packet Sequence Control Segmentation Flag APID xxx Packet Sequence Control Source Sequence Count APID xxx Packet Length APID xxx MSWord LRO Mission Operations PlanT&C Database Style Guide HxxxTIME Start Byte 6 HxxxSECL HxxxSUBS 8 10 Mnemonic 3.2.1.5. 3.2.1.5.1. 431-HDBK-000076 Revision DRAFT Start Length in Data Description Bit Bits Type 0 48 TIME42 APID xxx System Time when packet was formed 0 16 U12 APID xxx System Time LSWord 0 16 U12 APID xxx System Time Subseconds Pseudo-telemetry SDB File Subsystem Identifiers Pseudo-telemetry may be assigned to one or more subsystems. The subsystem name is used to limit database searches or reports and for general information. Subsystem identifiers (SSI record type) have a maximum length of 15 characters, and must start with the assigned two-character prefix from Table 3-1. These records will be included as part of the pseudo-telemetry SDB file. Refer to Appendix B for an example. 3.2.1.5.2. Telemetry Records The pseudo-telemetry SDB file assigns each pseudo-telemetry data point to a recognizable name, or mnemonic, and is defined by a telemetry record (TLM record type). The TLM records will be organized by subsystem. In addition to a mnemonic name, each telemetry record includes fields to identify other attributes of the pseudo-telemetry point. Refer to the ITOS Database Building documentation for the definition of and more information on the TLM record. Appendix B provides an example of a Pseudo-telemetry SDB file that shows how these fields may be defined. A definition in record fields 1-3, 5, 8 if possible, and 14-15 is required for LRO. Please note that LIM, DSC and ALG records must also be included in the pseudotelemetry SDB file if such has been defined in the TLM record of the pseudo_telemetry SDB file. Please follow the same guidelines for these records as explained in Sections 3.2.1.45 – 7. Also, note that packet header information is not to be included in the pseudo-telemetry SDB, since pseudo-telemetry is not contained within a CCSDS packet. 3.2.1.6. Command SDB File The command SDB file is comprised of all command-related records (CMD, FLD, and SUB record types). The following sections define the content and format of each command record type. 3-17 LRO Mission Operations PlanT&C Database Style Guide 3.2.1.6.1. 431-HDBK-000076 Revision DRAFT Command Records Command records are to be organized in ascending order by APID and Function Code/Command Type, respectively. Refer to the ITOS Database Building documentation for the definition of and more information on the CMD record. Appendix C provides an example of a Command SDB file that shows how these fields may be defined. A definition in record fields 1-6, 9-11, and 15 is required for LRO. 3.2.1.6.2. Command Field Records For commands that require commandable inputs, the command field record (FLD record type), also called a submnemonic, is utilized. These records will immediately follow the associated CMD record. Refer to the ITOS Database Building documentation for the definition of and more information on the FLD record. Refer to Appendix C for an example. A definition in record fields 1-5, 7, 8 if applicable, 9, and 13-14 is required for LRO. Note that the “Field Name” (field 3) does not require the pre-defined subsystem prefix, whereas the “Discrete Set Name” (field 13) does. 3.2.1.6.3. Command Discrete Conversion Records For commands that include command field records, a discrete conversion record (SUB record type) may be defined to convert a numerical command input to an alphanumeric discrete name. For example, a value of zero (0) may correspond to an “ON” state and a value of one (1) may correspond to an “OFF” state. This allows the user to use “ON” and “OFF” rather than memorizing which function corresponds to 0 or 1. This significantly increases the usability of the command. Similarly, if a command field needs to be commandable, but is commonly set to the same value, the special name "default" may be used to represent the default value when no other value is specified. This allows the user to use the command field when needed, but otherwise omit it if the default value is acceptable. If a “default” conversion and value are not identified for a given field, the field will always require an input value to be commanded. In the SDB files, these records will immediately follow the associated FLD record(s). Refer to the ITOS Database Building documentation for the definition of and more information on the SUB record. Refer to Appendix C for an example. A definition in all SUB record fields 1-7 is required for LRO. 3.2.2. Summary The following provides a summary of the guidelines when creating and maintaining SDB files to ensure readability and usability: a. Within each record type, fixed column widths will be used for each field to improve readability. b. Comments and blank lines will be used liberally to distinguish between sets of telemetry packets, commands with multiple “FLD”/”SUB” records, and configuration control information, etc. 3-18 LRO Mission Operations PlanT&C Database Style Guide 431-HDBK-000076 Revision DRAFT c. In subsystem telemetry SDB files, the “M&T” records will be specified in the same byte order as the data is organized in the telemetry packet. d. The “M&T”, “DSC”, “ALG”, and “LIM” records for a given telemetry mnemonic will have unique names and be contained in the same file. This is the preferred method. However, if specific “DSC”, “ALG”, or “LIM” records are to be used by several subsystems, they may be defined in the SDB files of only one of the subsystems. CAUTION: This requires careful coordination with other SDB file developers to ensure that the needed records are defined and not mistakenly deleted. e. In command definitions, the “FLD” records for a given command will immediately follow the “CMD” records for that command. f. In command definitions, the “SUB” records for a given command will immediately follow the “FLD” records for that command. 3-19 LRO T&C Database Style Guide A. 431-HDBK-000076 Revision DRAFT TELEMETRY DATABASE (SDB) FILE EXAMPLE ############################################################################### # # Define all LRO Subsystem or Instrument NN Telemetry # # VERSION: # # $Id: nn_tlm.sdb,v $ # # CHANGE HISTORY: # # Date Author Change Description # ---------- -------------- --------------------------------------------------# mm/dd/yyyy initials Example # ############################################################################### DEL,| #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Subsystem Name |+| Description #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# SSI | NNXX_command |+| Subsystem NN, Task or Element XX Commands | SSI | NNXX_telemetry |+| Subsystem NN, Task or Element XX Telemetry | ############################################################################# #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # APID |+| Subsystem Timeout Pkt Length Timestamp Description #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# MAP| 00 |+| NNXX_telemetry | 30 | | | APID 00, NNXX Housekeeping Telemetry Packet | ############################################################################# #--------------------------**********************************START OF Instrument or Subsystem NN, Task or Element XX Status Packet**********************************************--# # SBO | 12 | Start byte offset | # #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # |+| Mnemonic | Pkt| Data|Start|Start| Bit|Units| Subsystem | Evt| Limits | DSC or ALG | Selector |Initial|ReadOnly|Array |Array |Array| Description # | ID| Type|Byte | Bit|Length| | |Flag| | Conversion | Name | Value| Flag|Length|Offset|Index| #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# M&T |+| NNMNEMONICNAME1 | 00| I12 | 12| 0| 16|C | NNXX_telemetry| |NNXX_TEMP_LIM| NNXX_TEMP_ALG| | | F| 1| 0| 0|Max 64 char | M&T |+| NNMNEMONICNAME2 | 00| UB | 14| 0| 4| | NNXX_telemetry| | NNXX_ERR_LIM| NNXX_ERR_DSC| | | F| 1| 0| 0|64 <HTML> More | M&T |+| NNMNEMONICNAME3 | 00| UB | 14| 4| 4| | NNXX_telemetry| | | NNXX_ERR_DSC| | | F| 1| 0| 0|Max 64 char | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Discrete Conversion| String |+| Minimum | Maximum | ForeColor | BackColor | Description #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# DSC |NNXX_ERR_DSC |"NO ERRORS, OR ERRORS CLEARED" |+| 0.0 | 0.0 | GREEN | BLACK | No Error | DSC |NNXX_ERR_DSC |"DIDN'T GET BOOL_TRUE OR BOOL_FALSE" |+| 1.0 | 1.0 | RED | BLACK | Error Message | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Limits |+| Red | Yellow | Yellow | Red | Switch | Limit Switch | Limit Switch | Inversion | Description # |+| Low | Low | High | High | Mnemonic | Low | High | Flag | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# LIM |NNXX_ERR_LIM |+| | | 1 | 2 | | | | F | ERROR limit | LIM |NNXX_TEMP_LIM |+| -25 | -20 | 45 | 50 | NNMNEMONICNAME1 | 1.0 | 3.0 | F | TEMPERATURE limit with a given state of NNMNEMONICNAME1 | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Analog Conversion |+| Coefficient | Coefficient | Coefficient | Coefficient | Coefficient | Coefficient | Coefficient | Coefficient | Description # |+| of X^0 | of X^1 | of X^2 | of X^3 | of X^4 | of X^5 | of X^6 | of X^7 | #-------------------------------------------------------------- ------------------------------------------------------------------------------------------------------------------# ALG |NNXX_TEMP_ALG |+| 3.59971000e+01 | -1.8128900e+00 | 2.08655000e-02 | -1.47476000e-04 | 5.32435000e-07 |5.32435000e-07 |5.32435000e-07 |5.32435000e-07 | RAW TEMPS TO deg C | A-1 LRO T&C Database Style Guide B. 431-HDBK-000076 Revision DRAFT PSEUDO-TELEMETRY DATABASE (SDB) FILE EXAMPLE ############################################################################### # # Define all LRO Subsystem or Instrument NN Pseudo-Telemetry # # VERSION: # # $Id: nnx_tlm.sdb,v $ # # CHANGE HISTORY: # # Date Author Change Description # ---------- -------------- --------------------------------------------------# mm/dd/yyyy initials Example # ############################################################################### DEL,| #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Subsystem Name |+| Description #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# SSI | NNXXX_telem |+| Subsystem NN, Task or Element XX, X Pseudo-telemetry | ############################################################################# #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Mnemonic |+|Mnemonic id Subsystem Data Type Bit Length Units Event Flag Array Length Limits Conversion Initial Value ReadOnly Flag Deescription # TLM | NNMNEMONICNAMEX |+| |NNXXX_telem| DFP | | | | 1 | NNXXX_ERR_LIM |NNXXX_ERR_DSC | | F |Max 64 character | TLM | NNMNEMONICNAMEX |+| |NNXXX_telem| DFP | | | | 1 | NNXXX_TEMP_LIM |NNXXX_TEMP_ALG| | F |Max 64 character | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Discrete Conversion| String |+| Minimum | Maximum | ForeColor | BackColor | Description #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# DSC |NNXXX_ERR_DSC |"NO ERRORS, OR ERRORS CLEARED" |+| 0.0 | 0.0 | GREEN | BLACK | No Error | DSC |NNXXX_ERR_DSC |"DIDN'T GET BOOL_TRUE OR BOOL_FALSE" |+| 1.0 | 1.0 | RED | BLACK | Error Message | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Limits |+| Red | Yellow | Yellow | Red | Switch | Limit Switch | Limit Switch | Inversion | Description # |+| Low | Low | High | High | Mnemonic | Low | High | Flag | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# LIM |NNXXX_ERR_LIM |+| | | 1 | 2 | | | | F | ERROR limit | LIM |NNXXX_TEMP_LIM |+| -25 | -20 | 45 | 50 | NNMNEMONICNAME1X| 1.0 | 3.0 | F | TEMPERATURE limit with a given state of NNMNEMONICNAME1 | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Analog Conversion |+| Coefficient | Coefficient | Coefficient | Coefficient | Coefficient | Coefficient | Coefficient | Coefficient | Description # |+| of X^0 | of X^1 | of X^2 | of X^3 | of X^4 | of X^5 | of X^6 | of X^7 | #-------------------------------------------------------------- ------------------------------------------------------------------------------------------------------------------# ALG |NNXXX_TEMP_ALG |+| 3.59971000e+01 | -1.8128900e+00 | 2.08655000e-02 | -1.47476000e-04 | 5.32435000e-07 |5.32435000e-07 |5.32435000e-07 |5.32435000e-07 | RAW TEMPS TO deg C | B-1 LRO T&C Database Style Guide C. 431-HDBK-000076 Revision DRAFT COMMAND DATABASE (SDB) FILE EXAMPLE ############################################################################### # # Define all LRO Subsystem/Instrument X Telecommands # # VERSION: # # $Id: nn_cmd.sdb,v $ # # CHANGE HISTORY: # # Date Author Change Description # ---------- -------------- --------------------------------------------------# mm/dd/yyyy initials Example # ############################################################################### DEL,| #--------------------------**********************************START OF Instrument or Subsystem NN, Task or Element XX COMMANDS**********************************************-------# #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Command Mnemonic |+| APID | FC |Subsystem |DumpFlag| Dump | CmdBit| RunTime|CritFlag| CritCond | CheckSum | EndItem | Description # | | | | | APID | Length| Flag| | | FuncName | VerifyString | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# CMD |NNXXRESET |+| 0x5e | 0 |NNXX_command | | | 8 | 0 | N | | | | Reset NN, XX Software Status | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Command Mnemonic |+| APID | FC |Subsystem |DumpFlag| Dump | CmdBit| RunTime|CritFlag| CritCond | CheckSum | EndItem | Description # | | | | | APID | Length| Flag| | | FuncName | VerifyString | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# CMD |NNXXCMD1 |+| 0x5e | 1 |NNXX_command | | | 40 | 0 | N | | | | Command XX <HTML> More about NNXX command.| # # Command Mnemonic |Field Name |+| Destination | Array | Start | Start | Bit | Array | ValueRange | ValueRange | Discrete | Description # | DataType | Size | Byte | Bit | Length | Offset | Low Bound | Hi Bound | Set Name | FLD |NNXXCMD1 |WORD |+| U1234 | 1 | 8 | 0 | 32 | 0 | | | | 32-bit Command word value | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# # Command Mnemonic |+| APID | FC |Subsystem |DumpFlag| Dump | CmdBit| RunTime|CritFlag| CritCond | CheckSum | EndItem | Description # | | | | | APID | Length| Flag| | | FuncName | VerifyString | #---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------# CMD |NNXXCMD256 |+| 0x5e | 10 |NNXX_command | | | 40 | 0 | N | | | | Description | # # Command Mnemonic |Field Name |+| Destination | Array | Start | Start | Bit | Array | ValueRange | ValueRange | Discrete | Description # | DataType | Size | Byte | Bit | Length | Offset | Low Bound | Hi Bound | Set Name | FLD |NNXXCMD256 |NNXX_DUMMY |+| UI | 1 | 8 | 0 | 16 | 0 | | | NNFIXED_dsc | Default | FLD |NNXXCMD256 |TYPE |+| UB | 1 | 10 | 0 | 4 | 0 | | | NNTYPE_dsc | Default | FLD |NNXXCMD256 |STATE |+| UB | 1 | 10 | 4 | 4 | 0 | | | NNSTATE_dsc | ON/OFF | FLD |NNXXCMD256 |NNXX_DUMMY2 |+| UB | 1 | 11 | 0 | 8 | 0 | | | NNFIXED1_dsc | Default | # # Discrete Set Name|Value Name |+| Fixed Value |CritFlag| Description SUB |NNFIXED_dsc |DEFAULT |+| 0x0233 | N | Default | SUB |NNTYPE_dsc |DEFAULT |+| 0 | N | Default | SUB |NNSTATE_dsc |ON |+| 5 | N | ON | SUB |NNSTATE_dsc |OFF |+| 0 | N | OFF | SUB |NNFIXED1_dsc |DEFAULT |+| 2 | N | Default | #--------------------------**********************************END OF Instrument or Subsystem NN, Task or Element XX COMMANDS**********************************************---------# C-1 LRO T&C Database Style Guide D. 431-HDBK-000076 Revision DRAFT ACRONYM LIST ACS ALG APID C&DH CCB CM CMD CMO CRaTER CVS DB DLRE DSC FLD FSW GN&C GSE GSFC HGA HK I&T ITOS LAMP LEND LIM LOLA LRO LROC M&T NASA PKT RLEP RF S/C or SC SA SBO SDB SSI SUB T&C TBD TBR TLM UV Attitude Control System Analog Conversion Algorithm Definition Record Application Identification Command and Data Handling Configuration Control Board Configuration Management Command Record Configuration Management Office Cosmic Ray Telescope for Effects of Radiation Current Version System Database Diviner Lunar Radiometer Experiment Discrete Definition Record Command Field (Submnemonic) Flight Software Guidance, Navigation and Control Ground Support Equipment Goddard Space Flight Center High Gain Antenna Housekeeping Integration and Test Integrated Test and Operations System Lyman-Alpha Mapping Project Lunar Exploration Neutron Detector Limit Definition Record Lunar Orbiter Laser Altimeter Lunar Reconnaissance Orbiter Lunar Reconnaissance Orbiter Camera Telemetry Record National Aeronautics and Space Administration Packet Robotic Lunar Exploration Program Radio Frequency Spacecraft Solar Array Start Byte Offset Single Database File Subsystem Identifier Submnemonic Discrete Definition Telemetry and Command To Be Determined To Be Resolved Telemetry Ultraviolet 2
0
advertisement
Download
advertisement
Add this document to collection(s)
You can add this document to your study collection(s)
Sign in Available only to authorized usersAdd this document to saved
You can add this document to your saved list
Sign in Available only to authorized users