urn:nasa:pds:mess_mla_calibrated:data_cdr:mlastacdr0408200900_tab 1.0 1.10.1.0 Product_Observational 2018-06-04 1.0 PDS4 migrated product. 2004-08-20T09:00:00.844Z 2004-08-20T09:59:59.873Z Calibration Calibrated MESSENGER Mission urn:nasa:pds:context:investigation:mission.messenger data_to_investigation MESSENGER Spacecraft urn:nasa:pds:context:instrument_host:spacecraft.mess is_instrument_host Mercury Laser Altimeter Instrument urn:nasa:pds:context:instrument:mla.mess is_instrument Earth Planet urn:nasa:pds:context:target:planet.earth data_to_target Launch 1/001479633 1/001483232 mlastatuscdr mlastacdr 1.0 mlastacdr0408200900.tab 2008-10-22T21:20:41Z 0 3614 This table contains one set of instrument engineering data as reported by the MESSENGER Mercury Laser Altimeter (MLA) status packets. Nominal rate is 1 Hz or less. Additional details are contained in the CDR SIS document. Carriage-Return Line-Feed 117 0 512 et 1 1 ASCII_Real 16 second The independent variable of the equations of motion, in seconds from the J2000 epoch, at the shot timing origin T0. In the past this variable has been referred to at JPL as Ephemeris Time and at MIT, later at the Center for Astrophysics, as Coordinate Time. Its practical realization is the project-supplied clock kernel, applied to the Spacecraft Clock Mission Elapsed Time (MET) count that is transmitted to MESSENGER subsystems by the Integrated Electronics Module corresponding to the 1 PPS signal. The NAIF SPICE spacecraft clock (SCLK) kernel determines a corresponding Terrestrial Dynamic Time. These times are synchronous with respect to an observer at the Solar System barycenter in a relativistic sense. The SPICE library routine SCS2E performs the conversion to Ephemeris Time as used by the Project-supplied ephemeris files. utc 2 18 ASCII_String 24 Spacecraft clock (MET) converted to Coordinated Universal Time (UTC) using the project-supplied conversion from MET into Terrestrial Dynamical Time (TDT) seconds past the J2000 epoch, and by accounting for leap seconds and the offset between atomic time and UTC, into to an ISO standard calendar representation of UTC. met 3 43 ASCII_Integer 9 Spacecraft clock count, the Mission Elapsed Time in seconds, transmitted to subsystems by the Integrated Electronics Module, corresponding to the 1 PPS signal. rmu_data_size 4 53 ASCII_Integer 1 RMU supports two interfaces in reading the RMU shot data after every RUPT: byte mode and nibble mode. The nibble mode is not supported by flight software, therefore this telemetry point should always read 0, for byte mode. rmu_test_pattern 5 55 ASCII_Integer 1 Test pattern used to fill RMU shot data. 0,6,7: real data, 1: LFSR, 2: 0xAA, 3: 0x55, 4: Counter, 5: ~Counter rmu_data_type 6 57 ASCII_Integer 1 Identifies shot data as real or test data. =0 real data, =1 test data rmu_rate_select 7 59 ASCII_Integer 1 RMU Rate selected. =0, 1Hz, =1 6Hz, =2 8Hz, =3 10Hz canned_data 8 61 ASCII_Integer 1 Designates whether flight software is using a collection of RMU shot data or fake data as input to the science algorithms. =0 Real Data, =1 Fake Data rmu_1pps_sync 9 63 ASCII_Integer 1 RMU synchronized with 1PPS flag. =0, not synchronized, =1 synchronized rmu_transfer_mode 10 65 ASCII_Integer 1 Data Transfer mode commanded to RMU. Does not reflect the state of the RMU but rather the state of the software and how the software is reading the RMU. It is possible after an RMU reset to have this telemetry point not coincide with RMU_DATA_SIZE. =0 byte mode, =1 low nibble, =2 high nibble detector_ch3 11 67 ASCII_Integer 1 Status of detector channel 3: =0 enabled, =1 disabled. detector_ch2 12 69 ASCII_Integer 1 Status of detector channel 2: =0 enabled, =1 disabled. detector_ch1lo 13 71 ASCII_Integer 1 Status of detector channel 1 low: =0 enabled, =1 disabled. detector_ch1hi 14 73 ASCII_Integer 1 Status of detector channel 1 high: =0 enabled, =1 disabled. dump_active 15 75 ASCII_Integer 1 Designates whether software is performing a memory dump. =0 not performing memory dump =1 currently performing memory dump rmu_clock_select 16 77 ASCII_Integer 1 Clock configuration for the RMU. This drives the entire operation of the RMU. RMU has 4 different 5MHz clocks available to it, two internal to the RMU board and two external from the spacecraft. =0 Oscillator A, =1 Internal 40%, =2 Internal 50%, =3 Oscillator B rmu_cycle_reset_tof 17 79 ASCII_Integer 1 RMU uses TOF chips to measure in fine detail the return pulses coming back from a laser fire. The chips are prone to lockup if flooded with input. If the flight software detects that they are locked up, it will automatically configure the RMU to reset the TOF chips for one shot. Unfortunately the rate at which this telemetry point is monitored means that it is very unlikely that this event will ever be reflected in this telemetry point. =0 TOF chips are not reset after each shot. =1 TOF chips are reset after each shot. rmu_cal_select 18 81 ASCII_Integer 1 Indicates which calibration setting was applied to the RMU during ground testing, if enabled: 00=0ns, 01=200ns, 10=400ns, 11=200ns rmu_cal_enable 19 83 ASCII_Integer 1 Indicates whether RMU will output a fixed test pattern during ground testing as selected by RMU_CAL_SELECT: 00,01,10=Real Data from instrument, 11=TOF-A calibration data ovr_threshold_ch3 20 85 ASCII_Integer 1 Indicates whether the science task has overridden (via command) the channel 3 threshold value written as a DAC to the hardware. =0 not overridden, =1 overridden ovr_threshold_ch2 21 87 ASCII_Integer 1 Indicates whether the science task has overridden (via command) the channel 2 threshold value written as a DAC to the hardware. =0 not overridden, =1 overridden ovr_threshold_ch1lo 22 89 ASCII_Integer 1 Indicates whether the science task has overridden (via command) the channel 1 low threshold value written as a DAC to the hardware. =0 not overridden, =1 overridden ovr_threshold_ch1hi 23 91 ASCII_Integer 1 Indicates whether the science task has overridden (via command) the channel 1 high threshold value written as a DAC to the hardware. =0 not overridden, =1 overridden ovr_chan_disables 24 93 ASCII_Integer 1 Indicates whether channel disables mask used by science algorithms has been overridden. This mask is used to enable and disable the return channels (1hi, 1low, 2, 3). =0 not overridden, =1 overridden. ovr_gain 25 95 ASCII_Integer 1 Indicates whether the science task has overridden (via command) the gain value written as a DAC to the hardware. =0 not overridden, =1 overridden. ovr_range_window 26 97 ASCII_Integer 1 Indicates whether the science task has overridden (via command) the range window vlaue used to write the RMU range gate start and stop. =0 not overridden, =1 overridden. ovr_range_delay 27 99 ASCII_Integer 1 Indicates whether the science task has overridden (via command) the range delay value used to write the RMU range gate start and stop. =0 not overridden, =1 overridden. v2dot5_mon 28 101 ASCII_Integer 3 The ADC of the +2.5 volt monitor. v5_mon 29 105 ASCII_Integer 3 The ADC of the +5 volt monitor. v5neg_mon 30 109 ASCII_Integer 3 The ADC of the -5 volt monitor. v12_mon 31 113 ASCII_Integer 3 The ADC of the +12 volt monitor. v32dot5_mon 32 117 ASCII_Integer 3 The ADC of the +32.5 volt monitor. v550_mon 33 121 ASCII_Integer 3 The ADC of the +550 volt monitor. volt2dot5 34 125 ASCII_Real 4 volt The voltage of the +2.5 volt monitor. volt5 35 130 ASCII_Real 4 volt The voltage of the +5 volt monitor. volt5neg 36 135 ASCII_Real 6 volt The voltage of the -5 volt monitor. volt12 37 142 ASCII_Real 6 volt The voltage of the +12 volt monitor. volt32dot5 38 149 ASCII_Real 6 volt The voltage of the +32.5 volt monitor. volt550 39 156 ASCII_Real 5 volt The voltage of the +550 volt monitor. laser_tx_threshold 40 162 ASCII_Integer 3 The ADC of the laser Tx threshold which is commanded by the science task automatically every shot, via a DAC write, using a table value. volt_laser_tx_threshold 41 166 ASCII_Real 7 volt The voltage of the laser Tx threshold which is commanded by the science task automatically every shot, via a DAC write, using a table value. aem_latchup_ctr 42 174 ASCII_Integer 3 Count of the number of times the flight software responds to an AEM latch-up. It is important to note that this counter does not reflect the number of AEM latch-ups, but rather the number of times the software responds to a latch-up. Because the AEM is not able to remove the latch-up condition fast enough, the software will attempt to acknoweldge the same latch-up multiple times. Because of this, the software limits the number of latch-up acknowledgements a second to 2. In practice, for every AEM latch-up this counter will increment by 2. detector_board_temp 43 178 ASCII_Integer 3 The ADC of the detector board temperature. altimeter_det_temp 44 182 ASCII_Integer 3 The ADC of the altimeter detector temperature. analog_board_temp 45 186 ASCII_Integer 3 The ADC of the analog board temperature. rmu_board_temp 46 190 ASCII_Integer 3 The ADC of the RMU board temperature. xtal_oscillator_temp 47 194 ASCII_Integer 3 The ADC of the crystal oscillator temperature. cpu_board_temp 48 198 ASCII_Integer 3 The ADC of the CPU board temperature. laser_elec_temp 49 202 ASCII_Integer 3 The ADC of the laser electronics temperature. laser_amp_temp 50 206 ASCII_Integer 3 The ADC of the laser amplifier temperature. laser_oscillator_temp 51 210 ASCII_Integer 3 The ADC of the laser oscillator temperature. pca_temp 52 214 ASCII_Integer 3 The ADC of the PCA temperature. beam_xpand_top_temp 53 218 ASCII_Integer 3 The ADC of the beam expander top temperature. beam_xpand_base_temp 54 222 ASCII_Integer 3 The ADC of the beam expander base temperature. rx_tubelens_top_temp 55 226 ASCII_Integer 3 The ADC of the receiver tube lens temperature. mla_housing_temp 56 230 ASCII_Integer 3 The ADC of the MLA housing temperature. cal_lo_temp 57 234 ASCII_Integer 3 The ADC of the low calibration temperature. cal_hi_temp 58 238 ASCII_Integer 3 The ADC of the high calibration temperature. deg_detector_board_temp 59 242 ASCII_Real 6 degC The detector board temperature. deg_altimeter_det_temp 60 249 ASCII_Real 6 degC The altimeter detector temperature. deg_analog_board_temp 61 256 ASCII_Real 6 degC The analog board temperature. deg_rmu_board_temp 62 263 ASCII_Real 6 degC The RMU board temperature. deg_xtal_oscillator_temp 63 270 ASCII_Real 6 degC The crystal oscillator temperature. deg_cpu_board_temp 64 277 ASCII_Real 6 degC The CPU board temperature. deg_laser_elec_temp 65 284 ASCII_Real 6 degC The laser electronics temperature. deg_laser_amp_temp 66 291 ASCII_Real 6 degC The laser amplifier temperature. deg_laser_oscillator_temp 67 298 ASCII_Real 6 degC The laser oscillator temperature. deg_pca_temp 68 305 ASCII_Real 6 degC The PCA temperature. deg_beam_xpand_top_temp 69 312 ASCII_Real 6 degC The beam expander top temperature. deg_beam_xpand_base_temp 70 319 ASCII_Real 6 degC The beam expander base temperature. deg_rx_tubelens_top_temp 71 326 ASCII_Real 6 degC The receiver tube lens temperature. deg_mla_housing_temp 72 333 ASCII_Real 6 degC The MLA housing temperature. deg_cal_lo_temp 73 340 ASCII_Real 6 degC The low calibration temperature. deg_cal_hi_temp 74 347 ASCII_Real 6 degC The high calibration temperature. telemetry_volume 75 354 ASCII_Integer 5 Telemetry volume counter. Increments by 1 for every 1KB of data output by the telemetry framer task since the last software boot. checksum_enabled 76 360 ASCII_Integer 5 An integer representation of the 16-bit mask that shows which tables in memory are being checksummed. Each bit in the mask corresponds to the table ID of the same number (bit 4 in the mask corresponds to table 4). Convert back to binary notation before evaluating the checksumenabled mask: =0 table is not being checksummed, =1 table is being checksummed. checksum_status 77 366 ASCII_Integer 5 An integer representation of the 16-bit mask that shows whether the checksum of a table in memory is correct or incorrect. Each bit in the mask corresponds to the table ID of the same number (bit 4 in the mask corresponds to table 4). Convert back to binary notation before evaluating the checksumstatus mask: =0 Checksum is correct, =1 checksum is incorrect tof_lockup_cntr 78 372 ASCII_Integer 3 There are 6 TOF chips in the RMU. The RMU uses them to time stamp the Tx pulse, the high return, and the low returns. Every 16 shots the software analyzes the state of the TOFs. If during the past 16 shots the fine time (least significant 10 bits) on a RMU time stamp has not changed at all, and the coarse time has changed at least once, then a TOF lockup is detected and this telemetry point is incremented, and for the next shot, the TOF chips are configured to be reset. The software will immediately begin monitoring for the next 16 shots. The software only monitors the TOF lockups in Standby and Science modes. telem_rate_config 79 376 ASCII_Integer 1 Indicates whether the TELEMETRY_VOLUME counter is derived from the FSW or from a test source: 0=Oper, 1=Test. sdhwdiag_liteswitch 80 378 ASCII_Integer 1 =0 The MLA_HWDiagLite packet is off. =1 The MLA_HwDiagLite packet is on. si_timing_valid 81 380 ASCII_Integer 1 Check of timing integrity at rate of once per second. Three checks are performed: 1. Has MET message from S/C been received 2. Has the 1PPS signal from the S/C been received 3. Is the phase lock to the 1PPS off by more than 5 us If any of the checks fail then the timing integrity is in question. =0 Timing integrity fine, =1 Timing integrity under question. checksum_en_flag 82 382 ASCII_Integer 1 =0 checksumming of tables is disabled. =1 checksumming of tables is enabled. one_pps_occurred 83 384 ASCII_Integer 1 Each second the spacecraft sends a 1PPS signal to the MLA instrument. The flight software uses this signal to synchronize. =0 1PPS did not occur, =1 1PPS occured. sdhwdiag_fullswitch 84 386 ASCII_Integer 1 =0 MLA_HwDiagnostic packet is off. =1 MLA_HwDiagnostic packet is on. os_eprom_version 85 388 ASCII_Integer 1 There are two banks of EEPROM that the software is stored in. When the instrument is turned on, or any time the CPU board is rebooted, the code stored in EEPROM is copied out of one of the two banks, into RAM and executed there. This telemetry point says which bank of EEPROM the code was copied out of. =0 EEPROM Bank 0 - Non Write-Protected =1 EEPROM Bank 1 - Write-Protected sidirect_thres_ovr 86 390 ASCII_Integer 1 The science task allows the thresholds applied to each of the channels to be overridden. The science algorithms specify that the value commanded for them to be overridden with must be scaled by a function of the gain, and range window. For testing purposes, it was necessary to have the ability to directly apply the threshold given in the threshold override command. =0 thresholds are scaled as prescribed in science algorithm. =1 thresholds are directly applied idle_checkin 87 392 ASCII_Integer 1 By default, the flight software requires certain critical tasks to 'check in' in order for the watchdog to be kicked. In diagnosing a problem it might be necessary to disable that behavior. =0 critical tasks do NOT have to check in. =1 critical tasks DO have to check in. idle_met_checkin 88 394 ASCII_Integer 1 By default, the software checks that the MET is being received while in Science mode. If the MET is missing for a preset amount of time, then the software will execute the Mla_Safe script which will transition the software to Keep Alive mode. This telemetry point reflects whether or not the software is actively checking if the MET is being received. =0 MET not being checked. =1 MET being checked. sisc_time_bias 89 396 ASCII_Real 8 second The difference between the s/c ranging data alignment to the value of the MET, used in Science algorithm mode 1. Value is a B8 fraction. sisc_range_bias 90 405 ASCII_Integer 5 The difference between the s/c ranging data alignment to the range value, used in Science algorithm mode 1 to account for orbital error and other biases. Value is a signed integer number of counts. si_transmit_threshold 91 411 ASCII_Integer 4 The transmit start detector threshold value commanded by the Science task (currently defaults to 15 counts). volt_si_transmit_threshold 92 416 ASCII_Real 7 volt The transmit start detector threshold voltage. sd_aem_error_count 93 424 ASCII_Integer 5 Once a second, the flight software performs a series of ADCs on the temperatures and voltages. After every RUPT, the flight software performs a series of ADCs on all the items that can be written to via a DAC. If any ADC fails, due to a time out (the software pends on the AEM asserting that it is finished the ADC), then this counter is incremented. si_rmu_error_count 94 430 ASCII_Integer 5 Every shot when the software is in Science mode, the science task writes the values of the range gates (start and stop). At that time it also reads the values back and compares them to the values it wrote. If those two values do not agree then the science task increments this counter. cmd_accept_ctr 95 436 ASCII_Integer 3 Counter increments every time a command is sent and the software executes that command to completion without any errors. cmd_opcode 96 442 ASCII_String 4 The opcode of the last command that was processed, as a hexadecimal value. cmd_resultcode 97 450 ASCII_String 4 The error code generated by the last command executed. If the last command executed did not generate an error, then this value is zero. The error code is a hexadecimal value. alarm_id 98 458 ASCII_String 4 The ID of the last alarm issued by the flight software. The id is a hexadecimal value. alarm_count 99 464 ASCII_Integer 3 Counter is incremented every time an alarm is issued by the flight software. The flight software treats the reset message as an alarm, therefore value is one at boot up. However the actual integer range of values will be from 129 to 255 because the most significant bit of the telemetry point is used as a flag that is always set to 1. cmd_reject_count 100 468 ASCII_Integer 3 Counter increments every time the flight software fails to execute a command. itf_reject_count 101 472 ASCII_Integer 3 Counter is incremented every time the flight software receives an ITF and the ITF is either invalid or unable to be processed. The four cases for which this counter increments are: Not enough memory available to allocate a software bus packet; Invalid command format; Incorrect checksum; Synch pattern incorrect. watchdog_count 102 476 ASCII_Integer 3 Increments on reset of the flight software watchdog. cpureset_count 103 480 ASCII_Integer 3 Increments on every reset of the flight software CPU. A CPU reset can occur one of two ways: Software was directly commanded to reset; Software erroneously branched to an unused memory address and executed a 0xFF instruction. reset_cause 104 484 ASCII_Integer 1 Every time the flight software reboots, registers in the CPU board FPGA are examined in order to determine the cause of the reboot: =0 Power On, =1 CPU Reset, =2 Watchdog, =3 Invalid. mla_mode 105 486 ASCII_Integer 1 Flight software mode: =0 Keep Alive, =1 Standby, =2 Science dpu_selection 106 488 ASCII_Integer 1 The S/C has two DPUs that can interface to the MLA instrument. Only one of them can be active at a time. =0 DPU A, =1 DPU B watchdog_enabled 107 490 ASCII_Integer 1 =1 Watchdog enabled. =0 Watchdog disabled. Flight software will still continue to service the watchdog but it will have no affect, nor will there be any effect if the software fails to service the watchdog. pca_power_mode 108 492 ASCII_Integer 1 The PCA controls the power on the MLA instrument. There are two power modes. Under normal operation, Keep Alive software mode configures the PCA to low power mode. Standby and Science software modes configure the PCA to high power mode. =0 low power mode, =1 high power mode. pca_laser_enabled 109 494 ASCII_Integer 1 The laser on the MLA instrument can be directly turned on and off. Under normal operations the laser is automatically configured to be on in Science mode and automatically configured to be off in all other modes. =0 laser is OFF, =1 laser is ON. algorithm_mode 110 496 ASCII_Integer 1 The currently designated science algorithm mode. Only modes 0 and 1 were implemented in FSW at launch. =0 Mode 0 or Fixed, =1 Mode 1 or Scraft Range, =2 Closed Loop. range_mode 111 498 ASCII_Integer 1 The currently designated range tracking mode: 0= Don't use the s/c range data 1= Use s/c range in tracking algorithm 2= Reserved for future use in Algorithm Mode 2. hwdiag_tlm_config 112 500 ASCII_Integer 1 =0 neither MLA_HwDiagnostic nor MLA_HwDiagLite is on. =1, one of the hardware diagnostic packets is on. swdiag_tlm_config 113 502 ASCII_Integer 1 =0 The Mla_SwDiagnostic packet is OFF =1 The Mla_SwDiagnostic packet is ON met_free_run 114 504 ASCII_Integer 1 Every second the flight software checks to see if it has received a MET message from the spacecraft. If it did not receive the MET message it will free run off an internal clock until the MET message is received again. When using GSEOS build 4 or lower, the MET message is not consistently issued, and therefore this telemetry point will show the software free running often; this is fine. There is one known error condition for this telemetry point and that is when the science task overruns and delays the telemetry framer task for a considerable period of time (over 50ms). It is possible in that case that the MET was received, but because the task that monitors the MET was delayed, the software believes it is free running and will flag this telemetry point. =0 the flight software did receive a MET message =1 the flight software did NOT receive an MET message mem_write_enable 115 506 ASCII_Integer 1 =0 memory is not write enabled =1 memory is write enabled. sd_parity_error 116 508 ASCII_Integer 1 Every time the RUPT is generated, the flight software reads 166 bytes from the RMU (the shot data). The last byte of the data read from the RMU is a parity byte (XOR over entire block). The flight software also computes a parity for the data read from the RMU. If the two parities do not equal each other this telemetry point increments. This value should never be anything but 0. spare 117 510 ASCII_Integer 1 Spare column. mlastacdr0408200900.lbl 0 PDS3 Original PDS3 label Carriage-Return Line-Feed