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

加入VIP,免费下载
 

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

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

下载须知

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

版权提示 | 免责声明

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

REG NASA-LLIS-0559-1997 Lessons Learned Redundant Verification of Critical Command Timing (1995).pdf

1、Lessons Learned Entry: 0559Lesson Info:a71 Lesson Number: 0559a71 Lesson Date: 1997-05-29a71 Submitting Organization: JPLa71 Submitted by: J. Blosiu/D. OberhettingerSubject: Redundant Verification of Critical Command Timing (1995) Abstract: When a new mission software release was uploaded to the spa

2、cecraft, the inflight upload failed to include a software patch that had been written to fix a defective countdown timer. Because an independent “watchdog timer” was planned, but never implemented due to constrained project resources, the thrusters continued to fire after the desired shutdown time a

3、nd the mission was terminated. Recommendations centered on the need for rigorous software configuration management, a watchdog timer to terminate operations, and testbed verification of in-flight software updates.Description of Driving Event: Flight software for a recent mission included a safety fe

4、ature in which the flight computer initiated a command sequence for enabling the thrusters. It also started a countdown timer which limited the duration of the burn. Flight software contained a known defect: whenever numerical computations produced an overflow, the calculations generated false resul

5、ts. When interplanetary mission software was uploaded following conclusion of the first science objective of the mission, the upload failed to include a software patch which had been written to fix the defect.When the thrusters were enabled for a spacecraft pointing maneuver, the flight computer per

6、formed calculations which generated a numeric overflow. A floating point interrupt occurred, and the processor generated erroneous commands affecting various spacecraft functions, including the propulsion subsystem and the countdown timer. With this timer not functioning, the thrusters continued to

7、fire after the desired shutdown time.The 15-minute ground response to the fault allowed the loss of too much fuel to continue the mission. An independent watchdog timer*, redundant with the countdown timer, was planned but Provided by IHSNot for ResaleNo reproduction or networking permitted without

8、license from IHS-,-,-never implemented due to constrained project resources.Contributing Factors:1. Inadequate Operational Configuration Management. The functions of configuration management and software performance analysis and repair lacked adequate staffing.2. Inadequate Redundancy Design and Ove

9、rflow Detection. Spacecraft hardware and software did not provide redundancy checking on the performance of software, such as fault protection monitors, to detect, diagnose and recover from an overflow condition.3. Insufficient Processing Capability. The spacecraft computer was selected chiefly for

10、its physical attributes - principally mass and radiation tolerance - rather than for its computational power. The decision to omit a watchdog timer was influenced by this hardware limitation.4. Lack of Post-Launch Anomaly Analysis and Software Repair Capability. Only a single software development an

11、d simulation model was available for use by the flight project, and it was used continually after launch to generate flight sequences. This meant that the model was unavailable to generate software revisions to fix known bugs, so various software patches had to be uploaded throughout the mission.* W

12、atchdog Timer: A software module which works in conjunction with a hardware time limiter to anticipate periodic receipt of a system health indication and, in the absence of such indication, initiates a system restart, interrupt, or return to a prior state.Lesson(s) Learned: 1. Maintain a rigorous so

13、ftware configuration management program.2. Provide flight software with an independent watchdog timer to terminate operations which exceed the specified maximum time duration.3. Whenever possible, verify in-flight software updates in a testbed.Recommendation(s): See Lesson(s) LearnedEvidence of Recu

14、rrence Control Effectiveness: N/ADocuments Related to Lesson: N/AProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Mission Directorate(s): N/AAdditional Key Phrase(s): 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