Search NASA⌕ Search

SEARCH · Search NASA

Results for “launch software”

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 181 records · Page 10

Automated Translation of Safety Critical Application Software Specifications into PLC Ladder Logic

The numerous benefits of automatic application code generation are widely accepted within the software engineering community. A few of these benefits include raising the abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at the NASA Kennedy Space Center (KSC) recognized the need for PLC code generation while developing their new ground checkout and launch processing system. They developed a process and a prototype software tool that automatically translates a high-level representation or specification of safety critical application software into ladder logic that executes on a PLC. This process and tool are expected to increase the reliability of the PLC code over that which is written manually, and may even lower life-cycle costs and shorten the development schedule of the new control system at KSC. This paper examines the problem domain and discusses the process and software tool that were prototyped by the KSC software engineers.

Leucht, Kurt W.↗

Space Launch System Day of Launch Loads for Artemis I

NASA’s Space Launch System (SLS) was successfully launched on November 16, 2022. During the years leading up to the first flight, Artemis I, a DOLILU (Day of Launch I-Load Update) process was developed to design, verify, and upload the first stage flight trajectory on day-of-launch to ensure a safe flight. The evaluation of integrated vehicle loads is a key component of the DOLILU process. The SLS Artemis I DOL loads project has involved methodology development, software development, software testing and certification, operator training, and simulation and launch support. The resulting DOL process successfully calculated loads for all launch opportunities within the window, with the robust nature of the process contributing to all opportunities being go for loads.

SLS↗

Mars Sample Return Landed with Red Dragon

A Mars Sample Return (MSR) mission is the highest priority science mission for the next decade as recommended by the recent Decadal Survey of Planetary Science. However, an affordable program to carry this out has not been defined. This paper describes a study that examined use of emerging commercial capabilities to land the sample return elements, with the goal of reducing mission cost. A team at NASA Ames examined the feasibility of the following scenario for MSR: A Falcon Heavy launcher injects a SpaceX Dragon crew capsule and trunk onto a Trans Mars Injection trajectory. The capsule is modified to carry all the hardware needed to return samples collected on Mars including a Mars Ascent Vehicle (MAV), an Earth Return Vehicle (ERV) and Sample Collection and Storage hardware. The Dragon descends to land on the surface of Mars using SuperSonic Retro Propulsion (SSRP) as described by Braun and Manning [IEEEAC paper 0076, 2005]. Samples are acquired and deliverd to the MAV by a prelanded asset, possibly the proposed 2020 rover. After samples are obtained and stored in the ERV, the MAV launches the sample-containing ERV from the surface of Mars. We examined cases where the ERV is delivered to either low Mars orbit (LMO), C3 = 0 (Mars escape), or an intermediate energy state. The ERV then provides the rest of the energy (delta V) required to perform trans-Earth injection (TEI), cruise, and insertion into a Moon-trailing Earth Orbit (MTEO). A later mission, possibly a crewed Dragon launched by a Falcon Heavy (not part of the current study) retrieves the sample container, packages the sample, and performs a controlled Earth re-entry to prevent Mars materials from accidentally contaminating Earth. The key analysis methods used in the study employed a set of parametric mass estimating relationships (MERs) and standard aerospace analysis software codes modified for the MAV class of launch vehicle to determine the range of performance parameters that produced converged spacecraft designs capable of meeting mission requirements. Subsystems modeled in this study included structures, power system, propulsion system, nose fairing, thermal insulation, actuation devices, and GN&C. Best practice application of loads and design margins for all resources were used. Both storable and cryogenic propellant systems were examined. The landed mass and lander capsule size provide boundary conditions for the MAV design and packaging. We estimated the maximum mass the Dragon capsule is capable of landing. This and the volume capability to store the MAV was deduced from publically available data from SpaceX as well as our own engineering and aerodynamic estimates. Minimum gross-liftoff mass (GLOM) for the MAV were obtained for configurations that used pump-fed storable bi-propellant rocket engines for both the MAV and the ERV stage. The GLOM required fits within our internal estimate of the mass that Dragon can land at low elevation/optimal seasons on Mars. Based on the analysis, we show that a single Mars launch sample return mission is feasible using current commercial capabilities to deliver the return spacecraft assets.

Mars Ascent Vehicle (MAV)↗

Space shuttle natural environment analysis

Five major tasks are briefly outlined: development of detailed wind profile measurements for Kennedy Space Center (KSC) and Vandenberg Air Force Base (VAFB): development of software to construct meteorological data tapes for use in the STS Post Ascent Analysis; development of storage, access, and utilization codes for Global Cloud Cover data; development of software and meteorological data bases to establish launch delay risks at KSC and VAFB; and development of the meteorological tower 301 climatological data base at VAFB.

Batts, Wade↗

The X-windows interactive navigation data editor

A new computer program called the X-Windows Interactive Data Editor (XIDE) was developed and demonstrated as a prototype application for editing radio metric data in the orbit-determination process. The program runs on a variety of workstations and employs pull-down menus and graphical displays, which allow users to easily inspect and edit radio metric data in the orbit data files received from the Deep Space Network (DSN). The XIDE program is based on the Open Software Foundation OSF/Motif Graphical User Interface (GUI) and has proven to be an efficient tool for editing radio metric data in the navigation operations environment. It was adopted by the Magellan Navigation Team as their primary data-editing tool. Because the software was designed from the beginning to be portable, the prototype was successfully moved to new workstation environments. It was also itegrated into the design of the next-generation software tool for DSN multimission navigation interactive launch support.

Rinker, G. C.↗

Flight Dynamics Mission Support and Quality Assurance Process

This paper summarizes the method of the Computer Sciences Corporation Flight Dynamics Operation (FDO) quality assurance approach to support the National Aeronautics and Space Administration Goddard Space Flight Center Flight Dynamics Support Branch. Historically, a strong need has existed for developing systematic quality assurance using methods that account for the unique nature and environment of satellite Flight Dynamics mission support. Over the past few years FDO has developed and implemented proactive quality assurance processes applied to each of the six phases of the Flight Dynamics mission support life cycle: systems and operations concept, system requirements and specifications, software development support, operations planing and training, launch support, and on-orbit mission operations. Rather than performing quality assurance as a final step after work is completed, quality assurance has been built in as work progresses in the form of process assurance. Process assurance activities occur throughout the Flight Dynamics mission support life cycle. The FDO Product Assurance Office developed process checklists for prephase process reviews, mission team orientations, in-progress reviews, and end-of-phase audits. This paper will outline the evolving history of FDO quality assurance approaches, discuss the tailoring of Computer Science Corporations's process assurance cycle procedures, describe some of the quality assurance approaches that have been or are being developed, and present some of the successful results.

Oh, InHwan↗

Marketing Remote Sensing Data for North Pacific Fisheries Development and Management

Fish poaching, drug trafficking, ocean dumping, and other illegal activities are important problems on the high seas and in national economic zones. The primary thrust of the EOCAP II project, "Marketing Remote Sensing Data for North Pacific Fisheries Development and Management", was to use space-based sensors to improve the effectiveness of marine monitoring, control, and surveillance (MCS). Our initial objectives were to concentrate on the development of MCS tools using Advanced Very High Resolution Radiometry (AVHRR) and Synthetic Aperture Radar (SAR) data. Although we have successfully completed development of an initial version of our SAR-based monitoring tool (OmniVision), project activity has resulted in a much broader application of space-based assets to marine applications. Based in part on work commenced within EOCAP II, a new company, Ocean and Coastal Environmental Sensing, Inc. (OCENS), has been launched and the development of several new software products outside of the MCS arena initiated. One of those products, SeaStation, is near completion with a Fall, 1995 release date. Equity investment in OCENS now totals $70,000-with an additional amount being sought in the first round of financing. One of the pre-eminent objectives of EOCAP II is to make contributions to the US economy and job growth through the expansion of commercial uses of remotely sensed data. OCENS and the software products it is introducing into marine and coastal zone markets responds to this primary object*e. EOCAP II funding leveraged the market and technical know-how of OCENS founders into smart products that benefit marine and coastal zone users. Although technical difficulties and geopolitical shifts damaged the commercial feasibility of initial project objectives, the flexibility of the EOCAP II program now permits long-term business success. This in no small part stems from the fact that the EOCAP program recognizes the realities of small and start-up businesses and does not attempt to force these conditions to fit the apparent needs of big government. Instead, EOCAP works with those who know their market best in order to produce successful products and expanding businesses.

Source record↗

The Development of a User Inclusion Strategy for CLCS Display Design

This report summarizes a ten week effort to evaluate the software development process in the Checkout and Launch Control System (CLCS) for the presence of user inclusion in the design operation. A background is presented that highlights the value of achieving usability through user inclusion, progress-to-date is described, and future work is suggested so that a user inclusive design environment can be accomplished.

Jacko, Julie A.↗

Modeling and Performance Considerations for Automated Fault Isolation in Complex Systems

The purpose of this paper is to document the modeling considerations and performance metrics that were examined in the development of a large-scale Fault Detection, Isolation and Recovery (FDIR) system. The FDIR system is envisioned to perform health management functions for both a launch vehicle and the ground systems that support the vehicle during checkout and launch countdown by using suite of complimentary software tools that alert operators to anomalies and failures in real-time. The FDIR team members developed a set of operational requirements for the models that would be used for fault isolation and worked closely with the vendor of the software tools selected for fault isolation to ensure that the software was able to meet the requirements. Once the requirements were established, example models of sufficient complexity were used to test the performance of the software. The results of the performance testing demonstrated the need for enhancements to the software in order to meet the demands of the full-scale ground and vehicle FDIR system. The paper highlights the importance of the development of operational requirements and preliminary performance testing as a strategy for identifying deficiencies in highly scalable systems and rectifying those deficiencies before they imperil the success of the project

Ferrell, Bob↗

Comparison Campaign of VLBI Data Analysis Software - First Results

During the development of the Vienna VLBI Software VieVS at the Institute of Geodesy and Geophysics at Vienna University of Technology, a special comparison setup was developed with the goal of easily finding links between deviations of results achieved with different software packages and certain parameters of the observation. The object of comparison is the computed time delay, a value calculated for each observation including all relevant models and corrections that need to be applied in geodetic VLBI analysis. Besides investigating the effects of the various models on the total delay, results of comparisons between VieVS and Occam 6.1 are shown. Using the same methods, a Comparison Campaign of VLBI data analysis software called DeDeCC is about to be launched within the IVS soon.

Plank, Lucia↗

KSC Tech Transfer News, Volume 4, No. 2

There is a strong focus on technology in our human exploration strategy and a focus on a wide range of technology readiness levels (TRLs) across all NASA missions - from low-TRL development of innovative technological concepts that help reposition NASA on the cutting edge, to infusion of technology to solve critical mission needs. Throughout the TRL spectrum, there is a major emphasis on partnerships with academia, industry, and other Government agencies and among NASA Centers. This edition features are: (1) Aluminum Foam Heat Exchanger for Cold Helium Production, (2) Launching a Small Business with NASA Shuttle Software, (4) Aviation Technologies and the Personal Cabin Pressurization Monitor, (5) Granular Mechanics and Regolith Laboratory, (6) The Leahy-Smith America Invents Act

Dunn, Carol↗

Software Development for Remote Control and Firing Room Displays

The Launch Control System (LCS) developed at NASA's Kennedy Space Center (KSC) will be used to launch future spacecraft. Two of the many components of this system are the Application Control Language (ACL) and remote displays. ACL is a high level domain specific language that is used to write remote control applications for LCS. Remote displays are graphical user interfaces (GUIs) developed to display vehicle and Ground Support Equipment (GSE) data, they also provide the ability to send commands to control GSE and the vehicle. The remote displays and the control applications have many facets and this internship experience dealt with several of them.

LCS↗

Dynamic Modeling and Soil Mechanics for Path Planning of the Mars Exploration Rovers

To help minimize risk of high sinkage and slippage during drives and to better understand soil properties and rover terramechanics from drive data, a multidisciplinary team was formed under the Mars Exploration Rover (MER) project to develop and utilize dynamic computer-based models for rover drives over realistic terrains. The resulting tool, named ARTEMIS (Adams-based Rover Terramechanics and Mobility Interaction Simulator), consists of the dynamic model, a library of terramechanics subroutines, and the high-resolution digital elevation maps of the Mars surface. A 200-element model of the rovers was developed and validated for drop tests before launch, using MSC-Adams dynamic modeling software. Newly modeled terrain-rover interactions include the rut-formation effect of deformable soils, using the classical Bekker-Wong implementation of compaction resistances and bull-dozing effects. The paper presents the details and implementation of the model with two case studies based on actual MER telemetry data. In its final form, ARTEMIS will be used in a predictive manner to assess terrain navigability and will become part of the overall effort in path planning and navigation for both Martian and lunar rovers.

terramechanics↗

NASA’s Space Launch System Successfully Launches Artemis I Mission and Hardware Progress Continues for Next Artemis Missions

NASA’s Artemis I mission will be the first flight of the agency’s Space Launch System (SLS) rocket. It will launch an uncrewed Orion spacecraft to the Moon, where it will enter a highly elliptical retrograde orbit. In 2022, final tests, checkouts, and preparations were on schedule to be completed, including the vital wet dress rehearsal (WDR) at Kennedy Space Center’s (KSC) Launch Complex 39B. Following successful completion of WDR, which is expected in summer 2022, the Artemis I launch vehicle will be returned to the Vehicle Assembly Building (VAB) at KSC where it will be prepared for launch. Important data were collected during launch and will be shared as applicable. While the Artemis I hardware and mission took center stage in 2022, significant progress was made on hardware and software for future Artemis missions, including for the first crewed launch and the following SLS Block 1B and Block 2 variants of the rocket.

John Honeycutt↗

Launch Commit Criteria Monitoring Agent

The Spaceport Processing Systems Branch at NASA Kennedy Space Center has developed and deployed a software agent to monitor the Space Shuttle's ground processing telemetry stream. The application, the Launch Commit Criteria Monitoring Agent, increases situational awareness for system and hardware engineers during Shuttle launch countdown. The agent provides autonomous monitoring of the telemetry stream, automatically alerts system engineers when predefined criteria have been met, identifies limit warnings and violations of launch commit criteria, aids Shuttle engineers through troubleshooting procedures, and provides additional insight to verify appropriate troubleshooting of problems by contractors. The agent has successfully detected launch commit criteria warnings and violations on a simulated playback data stream. Efficiency and safety are improved through increased automation.

Semmel, Glenn S.↗

Demonstration of the Dynamic Flowgraph Methodology using the Titan 2 Space Launch Vehicle Digital Flight Control System

Dynamic Flowgraph Methodology (DFM) is a new approach developed to integrate the modeling and analysis of the hardware and software components of an embedded system. The objective is to complement the traditional approaches which generally follow the philosophy of separating out the hardware and software portions of the assurance analysis. In this paper, the DFM approach is demonstrated using the Titan 2 Space Launch Vehicle Digital Flight Control System. The hardware and software portions of this embedded system are modeled in an integrated framework. In addition, the time dependent behavior and the switching logic can be captured by this DFM model. In the modeling process, it is found that constructing decision tables for software subroutines is very time consuming. A possible solution is suggested. This approach makes use of a well-known numerical method, the Newton-Raphson method, to solve the equations implemented in the subroutines in reverse. Convergence can be achieved in a few steps.

Yau, M.↗

Writing a New Automated Testing Method for Custom Display Components

During the launch process of the Space Launch System (SLS), engineers in the Firing Room of the Launch Control Center (LCC) will be analyzing displays that show data and statistics about the vehicle and launch. These displays are subject to a battery of tests, but the custom components they use are not currently supported by any testing framework. My project is to modify a testing framework so that the custom components on these displays can be tested similarly to how a user would interact with them.

Automated Testing↗

Advanced Information Processing System (AIPS)-based fault tolerant avionics architecture for launch vehicles

An avionics architecture for the advanced launch system (ALS) that uses validated hardware and software building blocks developed under the advanced information processing system program is presented. The AIPS for ALS architecture defined is preliminary, and reliability requirements can be met by the AIPS hardware and software building blocks that are built using the state-of-the-art technology available in the 1992-93 time frame. The level of detail in the architecture definition reflects the level of detail available in the ALS requirements. As the avionics requirements are refined, the architecture can also be refined and defined in greater detail with the help of analysis and simulation tools. A useful methodology is demonstrated for investigating the impact of the avionics suite to the recurring cost of the ALS. It is shown that allowing the vehicle to launch with selected detected failures can potentially reduce the recurring launch costs. A comparative analysis shows that validated fault-tolerant avionics built out of Class B parts can result in lower life-cycle-cost in comparison to simplex avionics built out of Class S parts or other redundant architectures.

Lala, Jaynarayan H.↗