<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<?xml-model href="https://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1A10.sch"
  schematypens="http://purl.oclc.org/dsdl/schematron"?>
<?xml-model href="https://pds.nasa.gov/pds4/mission/mess/v1/PDS4_MESS_1B00_1020.sch"
  schematypens="http://purl.oclc.org/dsdl/schematron"?>

<Product_Observational xmlns="http://pds.nasa.gov/pds4/pds/v1" 
    xmlns:mess="http://pds.nasa.gov/pds4/mission/mess/v1" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:schemaLocation="http://pds.nasa.gov/pds4/pds/v1 https://pds.nasa.gov/pds4/pds/v1/PDS4_PDS_1A10.xsd   http://pds.nasa.gov/pds4/mission/mess/v1 https://pds.nasa.gov/pds4/mission/mess/v1/PDS4_MESS_1B00_1020.xsd">
  <Identification_Area>
    <logical_identifier>urn:nasa:pds:mess_grs_raw:data_edr:grs_cmd2007151zzz_tab</logical_identifier>
    <version_id>1.0</version_id>
    <title>MESSENGER GRS Command product: grs_cmd2007151zzz_tab</title>
    <information_model_version>1.10.1.0</information_model_version>
    <product_class>Product_Observational</product_class>
    <Modification_History>
      <Modification_Detail>
        <modification_date>2018-06-08</modification_date>
        <version_id>1.0</version_id>
        <description>PDS4 migrated product</description>
      </Modification_Detail>
    </Modification_History>
  </Identification_Area>
  <Observation_Area>
    <Time_Coordinates>
      <start_date_time>2007-05-31T14:58:04Z</start_date_time>
      <stop_date_time>2007-05-31T15:17:51Z</stop_date_time>
    </Time_Coordinates>
    <Investigation_Area>
      <name>MESSENGER</name>
      <type>Mission</type>
      <Internal_Reference>
        <lid_reference>urn:nasa:pds:context:investigation:mission.messenger</lid_reference>
        <reference_type>data_to_investigation</reference_type>
      </Internal_Reference>
    </Investigation_Area>
    <Observing_System>
      <Observing_System_Component>
        <name>MESSENGER</name>
        <type>Spacecraft</type>
        <Internal_Reference>
          <lid_reference>urn:nasa:pds:context:instrument_host:spacecraft.mess</lid_reference>
          <reference_type>is_instrument_host</reference_type>
        </Internal_Reference>
      </Observing_System_Component>
      <Observing_System_Component>
        <name>Gamma Ray Spectrometer</name>
        <type>Instrument</type>
        <Internal_Reference>
          <lid_reference>urn:nasa:pds:context:instrument:grs.mess</lid_reference>
          <reference_type>is_instrument</reference_type>
        </Internal_Reference>
      </Observing_System_Component>
    </Observing_System>
    <Target_Identification>
      <name>Venus</name>
      <type>Planet</type>
      <Internal_Reference>
        <lid_reference>urn:nasa:pds:context:target:planet.venus</lid_reference>
        <reference_type>data_to_target</reference_type>
      </Internal_Reference>
    </Target_Identification>
    <Mission_Area>
      <mess:MESSENGER>
        <mess:mission_phase_name>Venus 2 Flyby</mess:mission_phase_name>
        <mess:spacecraft_clock_start_count>1/089110812</mess:spacecraft_clock_start_count>
        <mess:spacecraft_clock_stop_count>1/089111999</mess:spacecraft_clock_stop_count>
        <mess:standard_data_product_id>grs_command_echo</mess:standard_data_product_id>
        <mess:software_name>pipe-grs2edr</mess:software_name>
        <mess:software_version_id>1.0</mess:software_version_id>
      </mess:MESSENGER>
    </Mission_Area>
  </Observation_Area>
  <File_Area_Observational>
    <File>
      <file_name>grs_cmd2007151zzz.tab</file_name>
      <creation_date_time>2008-12-05T19:43:16Z</creation_date_time>
    </File>
    <Table_Character>
      <offset unit="byte">0</offset>
      <records>56</records>
      <description>
        This table contains one set of the commands executed by the MESSENGER
        Gamma-Ray Spectrometer (GRS). A set is defined as all data with
        timestamps corresponding to a given Earth day. Additional details are contained
        in the EDR SIS document.
      </description>
      <record_delimiter>Carriage-Return Line-Feed</record_delimiter>
      <Record_Character>
        <fields>7</fields>
        <groups>0</groups>
        <record_length unit="byte">125</record_length>
        <Field_Character>
          <name>met</name>
          <field_number>1</field_number>
          <field_location unit="byte">1</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">12</field_length>
          <description>Mission Elapsed Time in seconds.</description>
        </Field_Character>
        <Field_Character>
          <name>cmd_utc_time</name>
          <field_number>2</field_number>
          <field_location unit="byte">15</field_location>
          <data_type>ASCII_String</data_type>
          <field_length unit="byte">19</field_length>
          <description>
            UTC time in YYYY-MM-DDTHH:MM:SS format derived from the
            MET using SPICE kernels.
          </description>
        </Field_Character>
        <Field_Character>
          <name>macro_flag</name>
          <field_number>3</field_number>
          <field_location unit="byte">37</field_location>
          <data_type>ASCII_String</data_type>
          <field_length unit="byte">3</field_length>
          <description>
            Identifies the command echo as a single command (CMD) or
            part of a command macro (MAC).
          </description>
        </Field_Character>
        <Field_Character>
          <name>cmd_result</name>
          <field_number>4</field_number>
          <field_location unit="byte">43</field_location>
          <data_type>ASCII_Integer</data_type>
          <field_length unit="byte">3</field_length>
          <description>
            Indicates the level of success for the command.
            The success level is command dependent and is described for each 
            separate command in the GRS Flight Software Document.
          </description>
        </Field_Character>
        <Field_Character>
          <name>cmd_opcode</name>
          <field_number>5</field_number>
          <field_location unit="byte">49</field_location>
          <data_type>ASCII_String</data_type>
          <field_length unit="byte">4</field_length>
          <description>
            The command opcode expressed as a hexidecimal string.
          </description>
        </Field_Character>
        <Field_Character>
          <name>cmd_opcode_string</name>
          <field_number>6</field_number>
          <field_location unit="byte">57</field_location>
          <data_type>ASCII_String</data_type>
          <field_length unit="byte">40</field_length>
          <description>
            The hex command translated into a string mnemonic.
            A hex command without an associated string map is set to
            UNDEFINED_CMD_STRING.
          </description>
        </Field_Character>
        <Field_Character>
          <name>cmd_arg_parameters</name>
          <field_number>7</field_number>
          <field_location unit="byte">101</field_location>
          <data_type>ASCII_String</data_type>
          <field_length unit="byte">22</field_length>
          <description>
            The command echo packet returns up to the first 10 
            command arguments. Most commands contain less than 10. The 
            arguments are represented by a single hex string. The decoding of 
            the hex string is command dependent and described for each separate
            command in the GRS Flight Software Document.
          </description>
        </Field_Character>
      </Record_Character>
    </Table_Character>
  </File_Area_Observational>
  <File_Area_Observational_Supplemental>
    <File>
      <file_name>grs_cmd2007151zzz.lbl</file_name>
    </File>
    <Stream_Text>
      <offset unit="byte">0</offset>
      <parsing_standard_id>PDS3</parsing_standard_id>
      <description>Original PDS3 label</description>
      <record_delimiter>Carriage-Return Line-Feed</record_delimiter>
    </Stream_Text>
  </File_Area_Observational_Supplemental>
</Product_Observational>
