Search NASA⌕ Search

SEARCH · Search NASA

Results for “flight software design”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 343 records · Page 19
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

Automatic Code Generation for Instrument Flight Software

Automatic code generation can be used to convert software state diagrams into executable code, enabling a model- based approach to software design and development. The primary benefits of this process are reduced development time and continuous consistency between the system design (statechart) and its implementation. We used model-based design and code generation to produce software for the Electra UHF radios that is functionally equivalent to software that will be used by the Mars Reconnaissance Orbiter (MRO) and the Mars Science Laboratory to communicate with each other. The resulting software passed all of the relevant MRO flight software tests, and the project provides a useful case study for future work in model-based software development for flight software systems.

state charts↗
NASA NTRS2024

End-to-End Mission Design & Trajectory Optimization

Need: A need exists for a generalized, robust, user-friendly and accessible end-to-end mission design optimization tool. Solution: Our solution to developing this capability was to interface two JSC tools—Copernicus and Genesis. Each of these tools has a specific area of the mission design process that it excels at. By utilizing them both, we can gain performance benefits not seen by either on their own. - Copernicus is a trajectory design and optimization software used for in-space trajectories around multiple bodies. - Genesis is a flight mechanics tool used to model ascent, entry, descent, and landing trajectories around a single planetary body. Year 1 was focused on combining these 2 software packages—allowing Copernicus to incorporate the ascent/descent capabilities of Genesis into the optimization problem—and developing this end-to-end mission design capability. Year 2 we focused on increasing the robustness of this capability by building the initial guess generator (IGG), which produces initial guesses based on simplifying assumptions and the physics of the problem. Year 3 of our project focused on utilizing the end-to-end mission design and optimization capabilities developed in the previous 2 years to analyze specific mission scenarios—scaling up from proof of concept to real analyses—capturing any resulting performance benefits, as well as addressing the Big Data challenges we’re faced with—namely, how we’re going to manage and interpret all the data that’s generated.

Kristin Nichols↗
NASA NTRS1989

NASA/NBS (National Aeronautics and Space Administration/National Bureau of Standards) standard reference model for telerobot control system architecture (NASREM)

The document describes the NASA Standard Reference Model (NASREM) Architecture for the Space Station Telerobot Control System. It defines the functional requirements and high level specifications of the control system for the NASA space Station document for the functional specification, and a guideline for the development of the control system architecture, of the 10C Flight Telerobot Servicer. The NASREM telerobot control system architecture defines a set of standard modules and interfaces which facilitates software design, development, validation, and test, and make possible the integration of telerobotics software from a wide variety of sources. Standard interfaces also provide the software hooks necessary to incrementally upgrade future Flight Telerobot Systems as new capabilities develop in computer science, robotics, and autonomous system control.

Albus, James S.↗
NASA NTRS2018

Assessment of the Mars Helicopter Thermal Design Sensitivities Using the Veritrek Software

The Mars Helicopter will be a technology demonstration conducted during the Mars 2020 mission. The primary mission objective is to achieve several 90-second flights and capture visible light images via forward and nadir mounted cameras. These flights could possibly provide reconnaissance data for sampling site selection for other Mars surface missions. The helicopter is powered by a solar array, which stores energy in secondary batteries for flight operations, imaging, communications, and survival heating. The helicopter thermal design is driven by minimizing survival heater energy while maintaining compliance with allowable flight temperatures in a variable thermal environment. Due to the small size of the helicopter and its complex geometries, along with the fact that it operates with very low power and small margins, additional care had to be paid while planning thermal tests and designing the thermal system. A Thermal Desktop® model has been developed to predict the thermal system’s performance. A reduced-order model (ROM) created with the Veritrek software has been utilized to explore the sensitivities of the thermal system’s drivers, such as electronics dissipations, gas gaps, heat transfer coefficients, etc., as well as to assess and verify the final thermal design. This paper presents the performance of the Veritrek software products and the details of the ROM creation process. The results produced by Veritrek were utilized to study the effect of the major thermal design drivers and Mars environment on the Mars Helicopter in as little as 10 days, an effort that would have taken over 4 months using traditional thermal analysis techniques.

Hengeveld, Derek W.↗
NASA NTRSDate not supplied

MPATH (Measuring Performance for Autonomy Teaming with Humans) Ground Control Station: Design Approach and Initial Usability Results

Envisioned future Advanced Air Mobility (AAM) operations will require a transition of aircraft command and control from onboard pilots to remote operators. The National Aeronautics and Space Administration (NASA) has developed a research ground control station (GCS) software called MPATH (Measuring Performance for Autonomy Teaming with Humans) to study the human factors of remote operators in a representative AAM environment, where small uncrewed aerial systems (sUAS; simulated or real) act as surrogates for larger AAM aircraft. A primary focus of the research being conducted with the MPATH GCS is scalability (i.e., one human managing multiple vehicles). MPATH has demonstrated to be a useful capability for human factors research and remote operations. Two initial usability studies and a multi-vehicle control assessment were recently conducted, and usability data and operator feedback were collected. Generally, participants rated MPATH high on usability and interface quality, whereas information quality was rated slightly lower. These results were supported by specific feedback. Several generalized GCS design recommendations are proposed based on the results and feedback from these flight activities. Future updates to MPATH will incorporate the proposed recommendations. In practice, these recommendations could be used by any GCS software designer or developer to promote usability and safety.

Advanced Air Mobility↗
NASA NTRS2004

Precise and Efficient Static Array Bound Checking for Large Embedded C Programs

In this paper we describe the design and implementation of a static array-bound checker for a family of embedded programs: the flight control software of recent Mars missions. These codes are large (up to 250 KLOC), pointer intensive, heavily multithreaded and written in an object-oriented style, which makes their analysis very challenging. We designed a tool called C Global Surveyor (CGS) that can analyze the largest code in a couple of hours with a precision of 80%. The scalability and precision of the analyzer are achieved by using an incremental framework in which a pointer analysis and a numerical analysis of array indices mutually refine each other. CGS has been designed so that it can distribute the analysis over several processors in a cluster of machines. To the best of our knowledge this is the first distributed implementation of static analysis algorithms. Throughout the paper we will discuss the scalability setbacks that we encountered during the construction of the tool and their impact on the initial design decisions.

Venet, Arnaud↗
NASA NTRS2012

Orbit Software Suite

Orbit Software Suite is used to support a variety of NASA/DM (Dependable Multiprocessor) mission planning and analysis activities on the IPS (Intrusion Prevention System) platform. The suite of Orbit software tools (Orbit Design and Orbit Dynamics) resides on IPS/Linux workstations, and is used to perform mission design and analysis tasks corresponding to trajectory/ launch window, rendezvous, and proximity operations flight segments. A list of tools in Orbit Software Suite represents tool versions established during/after the Equipment Rehost-3 Project.

Osgood, Cathy↗
NASA NTRS1973

Shuttle mission simulator software conceptual design

Software conceptual designs (SCD) are presented for meeting the simulator requirements for the shuttle missions. The major areas of the SCD discussed include: malfunction insertion, flight software, applications software, systems software, and computer complex.

Burke, J. F.↗
NASA NTRS2011

Evolution of Space Shuttle Range Safety (RS) Ascent Flight Envelope Design

Ascent flight envelopes are trajectories that define the normal operating region of a space vehicle s position from liftoff until the end of powered flight. They fulfill part of the RS data requirements imposed by the Air Force s 45th Space Wing (45SW) on space vehicles launching from the Eastern Range (ER) in Florida. The 45SW is chartered to protect the public by minimizing risks associated with the inherent hazards of launching a vehicle into space. NASA s Space Shuttle program has launched 130+ manned missions over a 30 year period from the ER. Ascent envelopes were delivered for each of those missions. The 45SW envelope requirements have remained largely unchanged during this time. However, the methodology and design processes used to generate the envelopes have evolved over the years to support mission changes, maintain high data quality, and reduce costs. The evolution of the Shuttle envelope design has yielded lessons learned that can be applied to future endevours. There have been numerous Shuttle ascent design enhancements over the years that have caused the envelope methodology to evolve. One of these Shuttle improvements was the introduction of onboard flight software changes implemented to improve launch probability. This change impacted the preflight nominal ascent trajectory, which is a key element in the RS envelope design. While the early Shuttle nominal trajectories were designed preflight using a representative monthly mean wind, the new software changes involved designing a nominal ascent trajectory on launch day using real-time winds. Because the actual nominal trajectory position was not known until launch day, the envelope analysis had to be customized to account for this nominal trajectory variation in addition to the other envelope components.

Brewer, Joan D.↗
NASA NTRS1982

Cost effective development of a Shuttle-based astronomical instrument control system

The high level language FORTH is used for the electronic control of the Space Shuttle-based Ultraviolet Imaging Telescope, in a flight computer system which minimizes costs. The greater part of the breadboard version of the flight computer is assembled from commercially available components, reducing novel circuit design features and permitting simultaneous development of both hardware and software. The commercial boards are then refabricated on aluminum core heat conducting stock, using high reliability parts to produce the flight versions of the system. The system's ground support equipment employs a MINC-25 minicomputer which performs such functions as flight computer software development, PROM programming, test and integration support, and flight operations support. The implementation of these concepts in flight computer telescope controls is described.

Parise, R. A.↗
NASA NTRS1984

Executable assertions and flight software

It is pointed out that executable assertions can be used for dynamic testing of software. An executable assertion is a logical statement about the variables or a block of code. If there is no error during execution then the assertion statement results in a true value. Assertions are useful for testing purposes throughout the lifecycle of software. They can be used for validation during the design phase, and for exception handling and error detection during the operation phase. The present investigation has the objective to study the use of executable assertions for testing flight software. Attention is given to details regarding executable assertions, the digital flight control system, testing flight software, and preliminary experimental results.

Mahmood, A.↗
NASA NTRS1983

Application experience with the NASA aircraft interrogation and display system - A ground-support equipment for digital flight systems

The NASA Dryden Flight Research Facility has developed a microprocessor-based, user-programmable, general-purpose aircraft interrogation and display system (AIDS). The hardware and software of this ground-support equipment have been designed to permit diverse applications in support of aircraft digital flight-control systems and simulation facilities. AIDS is often employed to provide engineering-units display of internal digital system parameters during development and qualification testing. Such visibility into the system under test has proved to be a key element in the final qualification testing of aircraft digital flight-control systems. Three first-generation 8-bit units are now in service in support of several research aircraft projects, and user acceptance has been high. A second-generation design, extended AIDS (XAIDS), incorporating multiple 16-bit processors, is now being developed to support the forward swept wing aircraft project (X-29A). This paper outlines the AIDS concept, summarizes AIDS operational experience, and describes the planned XAIDS design and mechanization.

Glover, R. D.↗
NASA NTRS2002

An Automated Method to Compute Orbital Re-entry Trajectories with Heating Constraints

Determining how to properly manipulate the controls of a re-entering re-usable launch vehicle (RLV) so that it is able to safely return to Earth and land involves the solution of a two-point boundary value problem (TPBVP). This problem, which can be quite difficult, is traditionally solved on the ground prior to flight. If necessary, a nearly unlimited amount of time is available to find the 'best' solution using a variety of trajectory design and optimization tools. The role of entry guidance during flight is to follow the pre- determined reference solution while correcting for any errors encountered along the way. This guidance method is both highly reliable and very efficient in terms of onboard computer resources. There is a growing interest in a style of entry guidance that places the responsibility of solving the TPBVP in the actual entry guidance flight software. Here there is very limited computer time. The powerful, but finicky, mathematical tools used by trajectory designers on the ground cannot in general be converted to do the job. Non-convergence or slow convergence can result in disaster. The challenges of designing such an algorithm are numerous and difficult. Yet the payoff (in the form of decreased operational costs and increased safety) can be substantiaL This paper presents an algorithm that incorporates features of both types of guidance strategies. It takes an initial RLV orbital re-entry state and finds a trajectory that will safely transport the vehicle to Earth. During actual flight, the computed trajectory is used as the reference to be flown by a more traditional guidance method.

Zimmerman, Curtis↗
NASA NTRS1985

Designing a priority driven multi-frame rate flight executive

The Advanced Transport Operating System (ATOPS) project is a NASA operational research flight project which is concerned with upgrading the new generation of flight computers. In connection with this work, it becomes also necessary to reassess the adequacy of the flight executive and flight software. In the present discussion, attention is given to the ATOPS project upgrade, the operating flight system, the design criteria for the new flight executive, the implementation of the executive, a sample real-time execution, a real-time debug and test tool, and several experiences which could be useful to others considering a similar exercise.

Smith-Taylor, R.↗
NASA NTRS1985

Space shuttle descent design: From development to operations

The descent guidance system, the descent trajectories design, and generating of the associated flight products are discussed. The programs which allow the successful transitions from development to STS operations, resulting in reduced manpower requirements and compressed schedules for flight design cycles are addressed. The topics include: (1) continually upgraded tools for the job, i.e., consolidating tools via electronic data transfers, tailoring general purpose software for needs, easy access to tools through an interactive approach, and appropriate flexibility to allow design changes and provide growth capability; (2) stabilizing the flight profile designs (I-loads) in an uncertain environment; and (3) standardizing external interfaces within performance and subsystems constraints of the Orbiter.

Crull, T. J.↗
NASA NTRS1990

Operational efficiency

Space transportation avionics technology operational efficiency issues are presented in viewgraph form. Information is given on ascent flight design, autonomous spacecraft control, operations management systems, advanced mission control, telerobotics/telepresence, advanced software integration, advanced test/checkout systems, advanced training systems, and systems monitoring.

Bland, Dan↗
NASA NTRS1999

The Design of a Fault-Tolerant COTS-Based Bus Architecture

In this paper, we report our experiences and findings on the design of a fault-tolerant bus architecture comprised of two COTS buses, the IEEE 1394 and the 12C. This fault-tolerant bus is the backbone system bus for the avionics architecture of the X2000 program at the Jet Propulsion Laboratory. COTS buses are attractive because of the availability of low cost commercial products. However, they are not specifically designed for highly reliable applications such as long-life deep-space missions. The X2000 design team has devised a multi-level fault tolerance approach to compensate for this shortcoming of COTS buses. First, the approach enhances the fault tolerance capabilities of the IEEE 1394 and 12 C buses by adding a layer of fault handling hardware and software. Second, algorithms are developed to enable the IEEE 1394 and the 12 C buses assist each other to isolate and recovery from faults. Third, the set of IEEE 1394 and 12 C buses is duplicated to further enhance system reliability. The X2000 design team has paid special attention to guarantee that all fault tolerance provisions will not cause the bus design to deviate from the commercial standard specifications. Otherwise, the economic attractiveness of using COTS will be diminished. The hardware and software design of the X2000 fault-tolerant bus are being implemented and flight hardware will be delivered to the ST4 and Europa Orbiter missions.

Chau, Savio N.↗