| IOC-MIPS_020a | 10130C | |||||||
| Title: | Command and Data Paths | |||||||
| Objective: | To confirm that instrument input/output are functional. | |||||||
| Description: | This test should confirm that the instrument can receive commands and that it emits | |||||||
| telemetry and science data as expected. | ||||||||
| This is a MIPS-specific electronics test that will do things like confirming telemetry | ||||||||
| output, instrument configuration commands, state changes, etc. | ||||||||
| We'll need further input from Ball on what goes on here. | ||||||||
| Place in Schedule: | The telescope does not have to be cold, so this can be done during initial instrument check-out. | |||||||
| Required Conditions: | no PCS capabilities are required - the initial CE checkout must be done | |||||||
| Resources: | ||||||||
| duration (best estimate) | 1 hour? | |||||||
| real time downlink (Y / N) | ||||||||
| special post event actions (Y / N) | ||||||||
| Outcome: | ||||||||
| description | ||||||||
| can proceed in parallel with other activity | ||||||||
| must outcome be confirmed before next event / test /activity | ||||||||
| method of confirmation (sensor TLM, data analysis, etc.) | ||||||||
| estimate of data turn around if required for confirmation | ||||||||
| Unique or included in planned uplink or downlink/analysis tool | unique | |||||||
| Contingency Plan: | ||||||||
| "What if..." | ||||||||
| IOC Critical | Y | |||||||
| References: | ||||||||
| Template last updated: | 11-Sep-95 | |||||||
| C.W. Engelbracht | ||||||||