Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559182
R. McIntyre
United Airlines began using Flight Management Systems (FMS) in 1982. The FMS-equipped aircraft operated initially in the domestic environment. Eventually, FMS-equipped aircraft operated on very long segments, such as Los Angeles to Hong Kong, which often required operation of the aircraft at multiple limits such as maximum takeoff weight, maximum fuel capacity, and/or specified fuel reserves. These limits are not fully considered by the current generation FMS in attempting to optimize the speed schedule. Software enhancements to this speed schedule logic could bring economic benefits to airlines flying these operationally challenging flights.
{"title":"The adverse impact of flight management systems on long range international airline operations","authors":"R. McIntyre","doi":"10.1109/DASC.1996.559182","DOIUrl":"https://doi.org/10.1109/DASC.1996.559182","url":null,"abstract":"United Airlines began using Flight Management Systems (FMS) in 1982. The FMS-equipped aircraft operated initially in the domestic environment. Eventually, FMS-equipped aircraft operated on very long segments, such as Los Angeles to Hong Kong, which often required operation of the aircraft at multiple limits such as maximum takeoff weight, maximum fuel capacity, and/or specified fuel reserves. These limits are not fully considered by the current generation FMS in attempting to optimize the speed schedule. Software enhancements to this speed schedule logic could bring economic benefits to airlines flying these operationally challenging flights.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124720878","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559192
D. Winter
In 1995, an initiative was launched at McDonnell Douglas Aerospace to assess the potential for reuse of flight software across multiple fighter aircraft platforms, and to define and demonstrate a supporting system architecture based upon open commercial hardware, software, standards and practices. The project has, thus far, yielded a preliminary common software architecture for mission processing, and successful demonstration flights of a reusable navigation module on three MDA aircraft (AV-8B, F-15 and F/A-18). The key products and findings, to date, of this ongoing activity are summarized.
1995年，麦克唐纳-道格拉斯航空航天公司启动了一项计划，以评估跨多个战斗机平台飞行软件重用的潜力，并定义和演示基于开放商业硬件、软件、标准和实践的支持系统架构。到目前为止，该项目已经产生了用于任务处理的初步通用软件架构，并在三架MDA飞机(AV-8B, F-15和F/ a -18)上成功地进行了可重复使用导航模块的演示飞行。总结了这项正在进行的活动迄今为止的主要产品和结果。
{"title":"Modular, reusable flight software for production strike aircraft","authors":"D. Winter","doi":"10.1109/DASC.1996.559192","DOIUrl":"https://doi.org/10.1109/DASC.1996.559192","url":null,"abstract":"In 1995, an initiative was launched at McDonnell Douglas Aerospace to assess the potential for reuse of flight software across multiple fighter aircraft platforms, and to define and demonstrate a supporting system architecture based upon open commercial hardware, software, standards and practices. The project has, thus far, yielded a preliminary common software architecture for mission processing, and successful demonstration flights of a reusable navigation module on three MDA aircraft (AV-8B, F-15 and F/A-18). The key products and findings, to date, of this ongoing activity are summarized.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127217234","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559205
R. K. Iyer, M. Hsueh, I. Lee
This paper presents the results of an analyse's of failures in several releases of Tandem's NonStop-UX operating system. NonStop-UX is based on UNIX System V. The analysis covers software failures from the field and failures reported by Tandem's test center. Faults are classified based on the status of the reported failures, the locations of the code that detected the problems, the panic messages generated by the systems, the faulty source modules, and the types of developer's mistakes. We present distributions of the failure and repair times for unique and duplicate failures. We also discuss how the analysis results can be used for assessing the dependability of the operating system and guiding improvement efforts.
本文介绍了对Tandem的NonStop-UX操作系统的几个版本的故障分析的结果。NonStop-UX基于UNIX System v。分析包括现场的软件故障和Tandem测试中心报告的故障。故障分类基于报告的故障状态、检测到问题的代码的位置、系统生成的紧急消息、故障源模块以及开发人员的错误类型。我们给出了唯一故障和重复故障的故障和修复时间的分布。我们还讨论了如何使用分析结果来评估操作系统的可靠性并指导改进工作。
{"title":"Fault/failure analysis of the Tandem NonStop-UX operating system","authors":"R. K. Iyer, M. Hsueh, I. Lee","doi":"10.1109/DASC.1996.559205","DOIUrl":"https://doi.org/10.1109/DASC.1996.559205","url":null,"abstract":"This paper presents the results of an analyse's of failures in several releases of Tandem's NonStop-UX operating system. NonStop-UX is based on UNIX System V. The analysis covers software failures from the field and failures reported by Tandem's test center. Faults are classified based on the status of the reported failures, the locations of the code that detected the problems, the panic messages generated by the systems, the faulty source modules, and the types of developer's mistakes. We present distributions of the failure and repair times for unique and duplicate failures. We also discuss how the analysis results can be used for assessing the dependability of the operating system and guiding improvement efforts.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126259326","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559168
B. Rich
The PAVE PACE program showed that the cost and weight of an avionics system for a new aircraft can be cut in half and its reliability tripled by incorporating the concepts of common modules, resource sharing, and reconfiguration into the sensor domain. The sensor domain includes the classical RF boundaries of Communication-Navigation-Identification (CNI), Radar, and Electronic Warfare (EW). The Integrated Sensor System (ISS) program is a concept development and validation initiative to address the RF avionics affordability. The ISS goal is to define an Open System Architecture (OSA) which provides economies of scale through wide-spread application, decreased number of unique module types, increased competition, and increased leverage of COTS-based hardware and software. Validation is achieved through a series of builds and demonstrations using the open system standards. This paper will describe the RF avionics requirements, the ISS Open System Architecture, and the demonstration system being built to validate the standards.
{"title":"Affordable integrated sensor system","authors":"B. Rich","doi":"10.1109/DASC.1996.559168","DOIUrl":"https://doi.org/10.1109/DASC.1996.559168","url":null,"abstract":"The PAVE PACE program showed that the cost and weight of an avionics system for a new aircraft can be cut in half and its reliability tripled by incorporating the concepts of common modules, resource sharing, and reconfiguration into the sensor domain. The sensor domain includes the classical RF boundaries of Communication-Navigation-Identification (CNI), Radar, and Electronic Warfare (EW). The Integrated Sensor System (ISS) program is a concept development and validation initiative to address the RF avionics affordability. The ISS goal is to define an Open System Architecture (OSA) which provides economies of scale through wide-spread application, decreased number of unique module types, increased competition, and increased leverage of COTS-based hardware and software. Validation is achieved through a series of builds and demonstrations using the open system standards. This paper will describe the RF avionics requirements, the ISS Open System Architecture, and the demonstration system being built to validate the standards.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128484358","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559204
T. Sims
A critical problem in the design of ultra-reliable fault tolerant systems is that of how to bring a redundant member back on-line, after a transient fault, without degrading critical real-time functions. Recovery from transients is imperative to maintain necessary system reliability in the face of transient errors which have been estimated to occur at a rate of 5 to 100 times that of permanent failures. Excessive delays associated with recovery become a problem when as much as 1 Mbytes of RAM in the faulty processor must be made congruent with the processing majority while maintaining full functionality of critical, real-time control algorithms. This paper describes a hardware assisted recovery technique which uses memory "tags" to determine which memory segments need to be restored such that recovery can be performed incrementally without affecting real-time operational tasks. Also presented is performance data associated with this technique's application to a Draper Laboratory quad-redundant processor responsible for vehicle control of a manned undersea vehicle.
{"title":"Real time recovery of fault tolerant processing elements","authors":"T. Sims","doi":"10.1109/DASC.1996.559204","DOIUrl":"https://doi.org/10.1109/DASC.1996.559204","url":null,"abstract":"A critical problem in the design of ultra-reliable fault tolerant systems is that of how to bring a redundant member back on-line, after a transient fault, without degrading critical real-time functions. Recovery from transients is imperative to maintain necessary system reliability in the face of transient errors which have been estimated to occur at a rate of 5 to 100 times that of permanent failures. Excessive delays associated with recovery become a problem when as much as 1 Mbytes of RAM in the faulty processor must be made congruent with the processing majority while maintaining full functionality of critical, real-time control algorithms. This paper describes a hardware assisted recovery technique which uses memory \"tags\" to determine which memory segments need to be restored such that recovery can be performed incrementally without affecting real-time operational tasks. Also presented is performance data associated with this technique's application to a Draper Laboratory quad-redundant processor responsible for vehicle control of a manned undersea vehicle.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"84 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114507940","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559174
M. B. Roark
The Functionally Integrated Resource Manager (FIRM) is an object-oriented database management system (DBMS) for use in avionics applications. It is also suitable for other real-time embedded applications from submarines to space stations. This paper examines the need for FIRM, and the unique requirements for avionics DBMSs not met by ordinary DBMSs. It then describes the unique features and construction of FIRM which allow it to meet those requirements.
{"title":"FIRM-a database management system for real-time avionics","authors":"M. B. Roark","doi":"10.1109/DASC.1996.559174","DOIUrl":"https://doi.org/10.1109/DASC.1996.559174","url":null,"abstract":"The Functionally Integrated Resource Manager (FIRM) is an object-oriented database management system (DBMS) for use in avionics applications. It is also suitable for other real-time embedded applications from submarines to space stations. This paper examines the need for FIRM, and the unique requirements for avionics DBMSs not met by ordinary DBMSs. It then describes the unique features and construction of FIRM which allow it to meet those requirements.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"136 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122776638","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559200
J. V., S. V. Koppen
In support of NASA's Fly-By-Light/Power-By-Wire (FBL/PBW) program, a series of flight tests were conducted by NASA Langley Research Center in February, 1995. The NASA Boeing 757 was flown past known RF transmitters to measure both external and internal radiated fields. The aircraft was instrumented with strategically located sensors for acquiring data on shielding effectiveness and internal coupling. The data are intended to support computational and statistical modeling codes used to predict internal field levels of an electromagnetic environment (EME) on aircraft. The software was an integral part of the flight tests, as well as the data reduction process. The software, which provided flight test instrument control, data acquisition, and a user interface, executes on a Hewlett Packard (HP) 300 series workstation and uses HP VEEtest development software and the C programming language. Software tools were developed for data processing and analysis, and to provide a database organized by frequency bands, test runs, and sensors. This paper describes the data acquisition system on board the aircraft and concentrates on the software portion. Hardware and software interfaces are illustrated and discussed. Particular attention is given to data acquisition and data format. The data reduction process is discussed in detail to provide insight into the characteristics, quality, and limitations of the data. An analysis of obstacles encountered during the data reduction process is presented.
{"title":"A description of the software element of the NASA EME flight tests","authors":"J. V., S. V. Koppen","doi":"10.1109/DASC.1996.559200","DOIUrl":"https://doi.org/10.1109/DASC.1996.559200","url":null,"abstract":"In support of NASA's Fly-By-Light/Power-By-Wire (FBL/PBW) program, a series of flight tests were conducted by NASA Langley Research Center in February, 1995. The NASA Boeing 757 was flown past known RF transmitters to measure both external and internal radiated fields. The aircraft was instrumented with strategically located sensors for acquiring data on shielding effectiveness and internal coupling. The data are intended to support computational and statistical modeling codes used to predict internal field levels of an electromagnetic environment (EME) on aircraft. The software was an integral part of the flight tests, as well as the data reduction process. The software, which provided flight test instrument control, data acquisition, and a user interface, executes on a Hewlett Packard (HP) 300 series workstation and uses HP VEEtest development software and the C programming language. Software tools were developed for data processing and analysis, and to provide a database organized by frequency bands, test runs, and sensors. This paper describes the data acquisition system on board the aircraft and concentrates on the software portion. Hardware and software interfaces are illustrated and discussed. Particular attention is given to data acquisition and data format. The data reduction process is discussed in detail to provide insight into the characteristics, quality, and limitations of the data. An analysis of obstacles encountered during the data reduction process is presented.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128336983","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559184
K. S. Krishnan, D. Lahti, T.S. Leuchars, S. R. Terwilliger
Over the last few years, the Adverse Environment Test Program (AETP) has developed a unique facility at McClellan Air Force Base (AFB), Sacramento, CA. The AETP provides a means for ensuring the nuclear survivability of fiber optic/electro-optic systems for military aircraft, ships, missiles, and ground systems, as well as space-based EO systems. In this paper, we introduce this facility and describe some of our results with a view to encourage industry to make use of this new capability.
{"title":"Fiber-optic component testing","authors":"K. S. Krishnan, D. Lahti, T.S. Leuchars, S. R. Terwilliger","doi":"10.1109/DASC.1996.559184","DOIUrl":"https://doi.org/10.1109/DASC.1996.559184","url":null,"abstract":"Over the last few years, the Adverse Environment Test Program (AETP) has developed a unique facility at McClellan Air Force Base (AFB), Sacramento, CA. The AETP provides a means for ensuring the nuclear survivability of fiber optic/electro-optic systems for military aircraft, ships, missiles, and ground systems, as well as space-based EO systems. In this paper, we introduce this facility and describe some of our results with a view to encourage industry to make use of this new capability.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133352545","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559162
C. Roark
The generic open architecture (GOA) framework is a Society of Automotive (SAE) Avionics Systems Division standard, SAE AS4893. The GOA framework was developed as a framework for discussing open systems architecture and for identifying critical components and interfaces. The GOA framework is being used as a framework within the avionics community for developing a preferred set of interface standards catalog. This paper provides an overview of the GOA framework and other activities on-going within the SAE AS5C GOA subcommittee.
{"title":"SAE AS4893 Generic Open Architecture (GOA) framework","authors":"C. Roark","doi":"10.1109/DASC.1996.559162","DOIUrl":"https://doi.org/10.1109/DASC.1996.559162","url":null,"abstract":"The generic open architecture (GOA) framework is a Society of Automotive (SAE) Avionics Systems Division standard, SAE AS4893. The GOA framework was developed as a framework for discussing open systems architecture and for identifying critical components and interfaces. The GOA framework is being used as a framework within the avionics community for developing a preferred set of interface standards catalog. This paper provides an overview of the GOA framework and other activities on-going within the SAE AS5C GOA subcommittee.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"74 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115088901","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 1996-10-27DOI: 10.1109/DASC.1996.559169
R. Erlandson
A derivation from basic principles is presented of GLONASS receiver in-band susceptibility levels suitable for Category I approach use. The derived limits are -113.5 dBm for interference bandwidths less than 500 kHz and -110.5 dBm/MHz for greater than 500 kHz. The limits are more stringent at the wide and narrow bandwidth extremes than the existing ARINC standard. Also derived are wide and narrow bandwidth GPS limits which are consistent with RTCA/DO-229 except for a 2 dB lower CW level.
{"title":"Susceptibility of GNSS sensors to RFI","authors":"R. Erlandson","doi":"10.1109/DASC.1996.559169","DOIUrl":"https://doi.org/10.1109/DASC.1996.559169","url":null,"abstract":"A derivation from basic principles is presented of GLONASS receiver in-band susceptibility levels suitable for Category I approach use. The derived limits are -113.5 dBm for interference bandwidths less than 500 kHz and -110.5 dBm/MHz for greater than 500 kHz. The limits are more stringent at the wide and narrow bandwidth extremes than the existing ARINC standard. Also derived are wide and narrow bandwidth GPS limits which are consistent with RTCA/DO-229 except for a 2 dB lower CW level.","PeriodicalId":332554,"journal":{"name":"15th DASC. AIAA/IEEE Digital Avionics Systems Conference","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1996-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134288977","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：