درباره ما
NASA-LLIS-0209
Lessons Learned - Time Correlation Between Multiple Telemetry Systems
Year: 1992
Abstract: Description of Driving Event:
The Space Shuttle Main Engine (SSME) telemetry system does not show absolute Greenwich Mean Time (GMT), but rather, the number of controller cycles since change in mode. Approximate timing had been established (during the STS 51-L launch process) by aligning the first guidance cycle after engine start with the engine start command time determined by analysis of the General Purpose Computer (GPC) event times. This aligned the SSME event times to the GPC event times to within a few tens of milliseconds, sufficient for normal flight analysis but insufficient for determining event sequencing for a system failure, which involves an interaction between the SSME and the rest of the vehicle. Without precise correlation between multiple data systems, there may be a delay in subsequent anomaly investigations due to timing uncertainties or a need to correct data timing.
The Space Shuttle Main Engine (SSME) telemetry system does not show absolute Greenwich Mean Time (GMT), but rather, the number of controller cycles since change in mode. Approximate timing had been established (during the STS 51-L launch process) by aligning the first guidance cycle after engine start with the engine start command time determined by analysis of the General Purpose Computer (GPC) event times. This aligned the SSME event times to the GPC event times to within a few tens of milliseconds, sufficient for normal flight analysis but insufficient for determining event sequencing for a system failure, which involves an interaction between the SSME and the rest of the vehicle. Without precise correlation between multiple data systems, there may be a delay in subsequent anomaly investigations due to timing uncertainties or a need to correct data timing.
Subject: Flight Equipment
Show full item record
| contributor author | NASA - National Aeronautics and Space Administration (NASA) | |
| date accessioned | 2017-09-04T16:58:23Z | |
| date available | 2017-09-04T16:58:23Z | |
| date copyright | 33921 | |
| date issued | 1992 | |
| identifier other | XIZCQCAAAAAAAAAA.pdf | |
| identifier uri | https://yse.yabesh.ir/std/handle/yse/121747 | |
| description abstract | Description of Driving Event: The Space Shuttle Main Engine (SSME) telemetry system does not show absolute Greenwich Mean Time (GMT), but rather, the number of controller cycles since change in mode. Approximate timing had been established (during the STS 51-L launch process) by aligning the first guidance cycle after engine start with the engine start command time determined by analysis of the General Purpose Computer (GPC) event times. This aligned the SSME event times to the GPC event times to within a few tens of milliseconds, sufficient for normal flight analysis but insufficient for determining event sequencing for a system failure, which involves an interaction between the SSME and the rest of the vehicle. Without precise correlation between multiple data systems, there may be a delay in subsequent anomaly investigations due to timing uncertainties or a need to correct data timing. | |
| language | English | |
| title | NASA-LLIS-0209 | num |
| title | Lessons Learned - Time Correlation Between Multiple Telemetry Systems | en |
| type | standard | |
| page | 2 | |
| status | Active | |
| tree | NASA - National Aeronautics and Space Administration (NASA):;1992 | |
| contenttype | fulltext | |
| subject keywords | Flight Equipment | |
| subject keywords | Flight Operations | |
| subject keywords | Launch Vehicle |