urn:nasa:pds:mess-rs-raw:data-tnf:111122000sc236dss24_tnf 1.0 1.13.0.0 Product_Observational Verma, A. K.; Perry, M. E.; Lemoine, F. G.; Smith, D. E.; Ensor, S.; Reid, M. R. 2020 MESSENGER Radio Science Tracking and Navigation File (TNF) 2020-10-12 1.0 This data file has been migrated from PDS3 PRODUCT_ID 111122000SC236DSS24_234 in data set MESS-V/H-RSS-1-EDR-RAWDATA-V1.0 to PDS4. The data file has been sorted according to data type and a new PDS4 label was created as part of the migration process. 2011-04-22T21:14:28Z 2011-04-22T22:59:12Z Science Raw MESSENGER raw radio tracking data Radio Science MErcury Surface, Space ENvironment, GEochemistry, and Ranging Mission Mission urn:nasa:pds:context:investigation:mission.messenger data_to_investigation MESSENGER Spacecraft urn:nasa:pds:context:instrument_host:spacecraft.mess is_instrument_host RSS Instrument urn:nasa:pds:context:instrument:rss.mess is_instrument NASA Deep Space Network Observatory urn:nasa:pds:context:facility:observatory.dsn is_facility DSN Instrumentation Instrument urn:nasa:pds:context:instrument:dsn.rss is_instrument DSN Antenna DSS 24 Telescope urn:nasa:pds:context:telescope:goldstone.dss24_34m is_telescope Mercury Planet urn:nasa:pds:context:target:planet.mercury data_to_target urn:nasa:pds:radiosci.documentation:dsn.trk-2-34:2008-02-29 data_to_document Reference document for the Tracking and Navigation File (TNF) data. For data collected earlier or later than this document, consult other document products in the same collection. IMPORTANT: Records delivered originally by the DSN were in time order, with records for different TNF data types interleaved. Retaining that structure would have made the PDS label many times larger than the data file itself. To keep the size of the label manageable, the original file was sorted so that all records of a single TNF data type are together. The blocks of homogeneous records were then concatenated -- TNF data type 0, followed by TNF data type 1, ... followed by TNF data type 17. When there were no records of a given TNF data type, that block was omitted. Within each block, the records remain in time order. The label is still long, since each block is a Table_Binary with many records containing many fields. But there will never be more than 18 blocks and never more than 18 Table_Binary definitions. The document referenced here correctly describes the record formats. Note, however, that the records are no longer in absolute time order. They are in time order within each block and the blocks are ordered by TNF data type. MESS-V/H-RSS-1-EDR-RAWDATA-V1.0:111122000SC236DSS24_234 data_to_raw_source_product PDS Geosciences Node The value for external_source_product_identifier is constructed from the PDS3 DATA_SET_ID, an ASCII colon character, and the PDS3 PRODUCT_ID. 111122000sc236dss24_tnf.dat 2020-10-12T11:29:38 1143870 f195ac2f0ddec2bc4301b7563fe1cbdb Uplink Carrier Phase (Data Type 00) 0 6285 Raw radio tracking data. 0 5 182 SFDU Label 1 1 6 0 The SFDU label 1 20 SFDU Control Authority 1 1 ASCII_String 4 An ASCII string giving the SFDU Control Authority for this data type. Set to "NJPL", meaning the data description information for this type of SFDU is maintained by the NASA/JPL Control Authority. SFDU Label Version ID 2 5 ASCII_String 1 An ASCII character giving the SFDU Label Version Identifier. Set to "2", meaning the length given in field 6 is formatted as a binary unsigned integer. SFDU Class ID 3 6 ASCII_String 1 An ASCII character giving the SFDU Class Identifier. Set to "I", meaning this is a Compressed Header Data Object (CHDO) structured SFDU. SFDU Reserved 4 7 UnsignedMSB2 2 These two bytes are not defined. SFDU Data Description ID 5 9 ASCII_String 4 An ASCII string giving the SFDU Data Description Identifier. Possible values are: C123 = Uplink data types C124 = Downlink data types C125 = Derived data types C126 = Interferometric data types C127 = Filtered data types SFDU Length 6 13 UnsignedMSB8 8 byte The number of remaining bytes in the SFDU after the 20-byte SFDU label. Aggregation CHDO Label 2 1 2 0 The Aggregation CHDO Label 21 4 Header Aggregation CHDO Type 1 1 UnsignedMSB2 2 Header Aggregation CHDO Type. Set to "1", meaning this CHDO is an aggregation of header CHDOs. The NJPL Control Authority maintains a registry of CHDO types. Header Aggregation CHDO Length 2 3 UnsignedMSB2 2 byte Header Aggregation CHDO Length. Primary CHDO 3 1 6 0 The Primary CHDO 25 8 Primary Header CHDO Type 1 1 UnsignedMSB2 2 Primary Header CHDO Type. Set to to 2, meaning this CHDO is a primary header CHDO. The NJPL Control Authority maintains a registry of CHDO types. Primary Header CHDO Length 2 3 UnsignedMSB2 2 byte Primary Header CHDO Length. Set to 4, meaning length of the value field of the Primary Header CHDO is 4 bytes. Major Data Class 3 5 UnsignedByte 1 Major Data Class. Set to 6, meaning these are ground station monitor data. Minor Data Class 4 6 UnsignedByte 1 Minor Data Class. Set to 14 meaning these are processed tracking data. Mission Identifier 5 7 UnsignedByte 1 Mission Identifier. Set to a number between 0 and 255. Format Code 6 8 UnsignedByte 1 Format Code; also known as the data type. The following data types (DT) are possible: 0 = Uplink Carrier Phase; 1 = Downlink Carrier Phase; 2 = Uplink Sequential Ranging Phase; 3 = Downlink Sequential Ranging Phase; 4 = Uplink PN Ranging Phase; 5 = Downlink PN Ranging Phase; 6 = Doppler; 7 = Sequential Ranging; 8 = Angles; 9 = Ramps; 10 = VLBI; 11 = DRVID; 12 = Smoothed Noise; 13 = Allan Deviation; 14 = PN Ranging; 15 = Tone Ranging; 16 = Carrier Observable; 17 = Total Phase Observable Secondary CHDO 132 4 1 32 0 Secondary CHDO 132 for uplink data types 33 70 secondary_chdo_type 1 1 UnsignedMSB2 2 Type attribute of the secondary CHDO. The following values are possible: 132 = uplink data types; 133 = downlink data types; 134 = derived data types; 135 = interferometric data types; 136 = filtered data types. Set to 132 for this Table. secondary_chdo_length 2 3 UnsignedMSB2 2 Length attribute of the secondary CHDO. Indicates the length of the value field (bytes after this item) of the secondary CHDO. The following values are possible: 66 = uplink data types; 110 = downlink data types; 124 = derived data types; 88 = interferometric data types; 98 = filtered data types. Set to 66 for this Table. orig_id 3 5 UnsignedByte 1 Originator ID. Indicates where this SFDU originated. Values between 0 and 255 are allowed. last_modifier_id 4 6 UnsignedByte 1 Last modifier ID. Indicates where the contents of this SFDU were last modified. Values between 0 and 255 are allowed. reserve1a 5 7 UnsignedByte 1 Reserved for future expansion of the next field (scft_id). A value of 0 is expected. scft_id 6 8 UnsignedByte 1 Spacecraft number. Values between 1 and 255 are allowed. upl_rec_seq_num 7 9 UnsignedMSB4 4 Uplink record sequence number (UPL RSN). This is the record sequence number reported by the uplink subsystem (UPL) equipment. Values between 0 and 2**32-1 are allowed. rec_seq_num 8 13 UnsignedMSB4 4 Record sequence number (RSN). Begins with zero, then increments by one for each successive uplink tracking SFDU of the same data type. Wraps around from 2**32-1 to zero. Value is reset to zero when the data processing system software is restarted. year 9 17 UnsignedMSB2 2 Time tag -- year doy 10 19 UnsignedMSB2 2 Time tag -- day of year sec 11 21 IEEE754MSBDouble 8 second Time tag -- seconds of day rct_day 12 29 UnsignedMSB2 2 day Record creation time -- days since 1 January 1958. rct_msec 13 31 UnsignedMSB4 4 %10d millisecond Record creation time -- milliseconds of day ul_dss_id 14 35 UnsignedByte 1 Uplink antenna number. A value between 0 and 255. ul_band 15 36 UnsignedByte 1 Uplink frequency band. 0 = Unknown; 1 = S-band; 2 = X-band; 3 = Ka-band; 4 = Ku-band; 5 = L-band ul_assembly_num 16 37 UnsignedByte 1 Uplink Assembly Number. Note that this is to allow for potential future cases where there might be more than one uplink of the same band at the same antenna. 0 = Invalid/unknown; 1 = S- or X-band uplink; 2 = Ka-band uplink transmit_num 17 38 UnsignedByte 1 Transmitter number. Value depends on transmitter used. Values between 0 and 3 are allowed; 0 indicates unknown. transmit_stat 18 39 UnsignedByte 1 Transmit status. 0 = Not transmitting out the horn; 1 = Transmitting out the horn; 2 = Invalid/unknown transmit_mode 19 40 UnsignedByte 1 Transmitter mode. 0 = Low power; 1 = High power; 2 = Invalid/unknown cmd_modul_stat 20 41 UnsignedByte 1 Command modulation status. 0 = OFF; 1 = ON; 2 = Invalid/unknown rng_modul_stat 21 42 UnsignedByte 1 Ranging modulation status. 0 = OFF; 1 = ON; 2 = Invalid/unknown fts_vld_flag 22 43 UnsignedByte 1 Frequency and Timing (FTS) validity. 0 = Equipment is not synced with FTS; 1 = Equipment is synced with FTS ul_software_version 23 44 UnsignedByte 1 Uplink Software version number. Gives the version major op code for the uplink software. Values between 0 and 255 are allowed. transmit_time_tag_delay 24 45 IEEE754MSBDouble 8 second Transmit time tag delay. Value used to offset uplink time tag (e.g., for Goldstone Beam Waveguide antennas). Values 0.0 to 1.0 are allowed. Value of -1.0 indicates invalid (or not provided). ul_zheight_corr 25 53 IEEE754MSBSingle 4 second Uplink Z-height correction. Values -1.0 to 1.0 are possible. Value -99.0 indicates invalid. mod_day 26 57 UnsignedMSB2 2 Last modification time -- days since 1 January 1958. Values 0 to 2**16-1 are allowed. mod_msec 27 59 UnsignedMSB4 4 milliseconds Last modification time -- milliseconds of day. Values 0 to 86400999 are allowed. version_num 28 63 UnsignedByte 1 Version number of the assembly that generated the data. Values 0 to 63 are allowed. sub_version_num 29 64 UnsignedByte 1 Sub-version number of the assembly that generated the data. Values 0 to 63 are allowed. sub_sub_version_num 30 65 UnsignedByte 1 Sub-sub-version number of the assembly that generated the data. Values 0 to 63 are allowed. reserve1b 31 66 UnsignedByte 1 %1d Reserved. One byte. reserve4a 32 67 UnsignedMSB4 4 %10d Reserved. Four bytes. Uplink Carrier Phase CHDO (Data Type 0) 5 1 19 0 Uplink Carrier Phase CHDO (Data Type 0) 103 80 chdo_type 1 1 UnsignedMSB2 2 Type attribute of the uplink carrier phase data CHDO. A value 10 is expected, indicating that the CHDO contains binary data. chdo_length 2 3 UnsignedMSB2 2 Length attribute of the uplink carrier phase data CHDO value field. Number of bytes after this item. A value of 76 is expected. ul_hi_phs_cycles 3 5 UnsignedMSB4 4 %10d High part phase data: total integer phase cycles divided by 2**32. ul_lo_phs_cycles 4 9 UnsignedMSB4 4 Low part phase data: total integer phase cycles modulo 2**32. ul_frac_phs_cycles 5 13 UnsignedMSB4 4 %10d Fractional phase data cycles: fractional phase cycles multiplied by 2**32 ramp_freq 6 17 IEEE754MSBDouble 8 hertz The base frequency of a ramped uplink transmission. Values 2.0e9 to 34.7e9 are expected. A value of 0. indicates an invalid or unknown value. Precision varies with band (phase data give higher precision): S-band = 0.5 microHz; X-band = 1.6 microHz; Ka-band = 7.7 microHz ramp_rate 7 25 IEEE754MSBDouble 8 Hz/s Ramp rate of an uplink transmission. Allowed values are -3.2e5 to 3.2e5. transmit_switch_stat 8 33 UnsignedByte 1 %3d Transmitter switch status. 0 = Antenna; 1 = Water load; 2 = Invalid/unknown ramp_type 9 34 UnsignedByte 1 %3d Ramp type. 0 = Snap; 1 = Start of new ramp; 2 = Medial report; 3 = Periodic report; 4 = End of ramps; 5 = Ramping terminated by operator; 6 = Invalid/unknown transmit_op_pwr 10 35 IEEE754MSBSingle 4 watt Transmitter output power. Values 0. to 500,000.0 are allowed. sup_data_id 11 39 ASCII_String 8 Support data ID. Name of the frequency predicts set used. sup_data_rev 12 47 ASCII_String 8 %8s Support data revision. Revision of the frequency predicts set used. prdx_time_offset 13 55 IEEE754MSBDouble 8 second Predicts time offset. Seconds added to current time. Values -31,536,000.0 to 31,536,000.0 are allowed. prdx_freq_offset 14 63 IEEE754MSBDouble 8 hertz Predicts frequency offset. Hz added to predicted value. Values -4.8e6 to 4.8e6 are allowed. time_tag_corr_flag 15 71 UnsignedByte 1 Time tag correction flag. Indicates results of validation of the block time tag. 0 = No validation attempted; 1 = Validated, no change; 2 = Validated, changed type_time_corr_flag 16 72 UnsignedByte 1 Type of time tag correction flag. Indicates what type of time tag correction was made. 0 = No correction; 1 = Year correction; 2 = DOY correction; 3 = Both Year and DOY correction fabricated_sfdu_flag 17 73 UnsignedByte 1 Fabricated SFDU Flag. Indicates whether this SFDU was artificially fabricated in support of 3-way ranging. 0 = Originally generated by UPL and validated by TTC software; 1 = Fabricated by TTC software reserve1c 18 74 UnsignedByte 1 Reserved. One byte. reserve6a 19 75 ASCII_String 6 Reserved. Six bytes.