ImageVerifierCode 换一换
格式:PDF , 页数:3 ,大小:14.84KB ,
资源ID:1018207      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-1018207.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(REG NASA-LLIS-0560-1997 Lessons Learned Galileo Scan Platform Anomaly at Ida Encounter (1993).pdf)为本站会员(wealthynice100)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

REG NASA-LLIS-0560-1997 Lessons Learned Galileo Scan Platform Anomaly at Ida Encounter (1993).pdf

1、Lessons Learned Entry: 0560Lesson Info:a71 Lesson Number: 0560a71 Lesson Date: 1997-06-05a71 Submitting Organization: JPLa71 Submitted by: R. Gounley/D. OberhettingerSubject: Galileo Scan Platform Anomaly at Ida Encounter (1993) Abstract: A scan platform anomaly occurred shortly before Galileos enco

2、unter with the asteroid Ida. Because the Galileo architecture did not provide for revolving, short-term storage of downlink data, ground control lacked insight into the cause of the incident.Missions should continuously buffer at least a small amount of high-rate telemetry as it is being downlinked

3、at a lower rate. Storage of high-rate data for the period immediately preceding and following a fault would assist mission analysts in diagnosis of the problem. Description of Driving Event: A scan platform anomaly occurred 5 hours before Galileos August 1993 encounter with the asteroid Ida. During

4、a quiescent period in scan platform activity, it unexpectedly jerked. The fault response sequence interpreted the high rate of scan platform motion as a spacecraft gyro error and turned off the gyros. The flyby continued in cruise mode, using star-based platform pointing. Although the low data rates

5、 available from the low gain antenna provided poor insight into spacecraft condition, ground control received indications of at least 5 more incidences of unexpected platform motion during quiescent periods over the next few hours. Ida encounter continued successfully with the gyros off and with no

6、further signs of the anomaly.No conclusive explanation was found despite extensive ground testing and analysis and attempts to recreate the anomaly on the spacecraft. Consistent x-axis data from both gyros suggested that gyro hardware failure was improbable. Analysis did reveal that the anomaly woul

7、d have aborted the imaging sequence had the additional power drawn during the slew been enough to cause an undervoltage condition. Instead, the first level fault protection (gyros off) allowed the sequence to continue imaging Ida. After the science data had been safely recorded and before the gyros

8、were Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-required, ground control was able to command them back on. This conservative, “first, do no harm“ approach proved successful.The Galileo architecture did not provide for revolving, short-term stora

9、ge of downlink data, which would have been useful in compensating for low telemetry data rates. Galileo telemetry provided data needed to troubleshoot the anomaly only once every two hours. Running intermittently, the tape recorder failed to capture any of the scan platform jerks. Subsequent to the

10、Galileo era, some low data rate missions are being designed to provide for some storage of transient data to improve fault visibility to ground control.Additional Keyword(s): System Design, Transient Event RecordingReference(s): ISA 04013GLesson(s) Learned: 1. Establish “First, do no harm“ as the ov

11、erriding principle guiding both fault protection design and the ground response to in-flight anomalies.2. Where it is not practical to record and downlink all telemetry, future missions should continuously buffer a small amount of high-rate telemetry as it is being downlinked at a lower rate. Should

12、 a fault occur, high-rate data for the period immediately preceeding and following the fault could be stored for later retrieval. This would assist mission analysts in real-time diagnosis of the problem.Recommendation(s): See Lesson(s) LearnedEvidence of Recurrence Control Effectiveness: N/ADocument

13、s Related to Lesson: N/AMission Directorate(s): N/AAdditional Key Phrase(s): Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-N/AAdditional Info: Approval Info: a71 Approval Date: 1997-08-13a71 Approval Name: Carol Dumaina71 Approval Organization: 125-204a71 Approval Phone Number: 818-354-8242Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1