Search NASA⌕ Search

SEARCH · Search NASA

Results for “vehicle operating data”

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 127 records · Page 7

An Alternative for Emergency Preemption of Traffic Lights

An electronic communication-and-control system has been developed as a prototype of advanced means of automatically modifying the switching of traffic lights to give priority to emergency vehicles. This system could be used alternatively or in addition to other emergency traffic-light-preemption systems, including a variety of systems now in use as well as two proposed systems described in "Systems Would Preempt Traffic Lights for Emergency Vehicles" (NPO-30573), NASA Tech Briefs, Vol. 28, No. 10 (October 2004), page 36. Unlike those prior systems that depend on detection of sounds and/or lights emitted by emergency vehicles, this system is not subject to severe range limitations. This system can be retrofitted into any pre-existing traffic-light-control system, without need to modify that system other than to make a minimal number of wire connections between the two systems. This system comprises several subsystems, including a transponder and interface circuitry on each emergency vehicle, a monitoring and control unit at each intersection equipped with traffic lights, and a wide-area two-way radio communication network that connects the emergency vehicles and intersection units. Computers in the various intersections and vehicle units run special-purpose software that implements the traffic- light-preemption scheme. The operations of the intersection and vehicle units are synchronized by use of Global Positioning System (GPS) timing signals. The transponder in each vehicle estimates its own position and velocity by use of GPS signals, deductive ("dead") reckoning, data from the onboard diagnostic (OBD) computer of the vehicle, and/or triangulation of beacon signals. When the operator of an emergency vehicle turns on its flashing lights and sirens in response to a request for an emergency response, the transponder unit goes into action, reading the OBD data to determine speed and acceleration, and reading and gathering further navigational data as described above. The position, velocity, and acceleration data are combined with vehicle-identification data in a prescribed format, and the resulting set of data is transmitted to the intersections within communication range of the transponder.

Foster, Conrad↗

An investigation of the landing characteristics of the NASA-MSC August 1969 baseline orbiter configuration in ground effect

A 0.05 scale model of the NASA-MSC August 1969 baseline shuttle craft was tested in Texas A&M University's 7- x 10-foot low speed wind tunnel facility. The purpose of the test was to determine the landing aerodynamic characteristics of the shuttle craft vehicle in ground effect and to evaluate control surface hinge moments experienced in the cruise and landing operational phases of flight. Analysis of the final data will allow evaluation of vehicle flight stability in ground effect and estimation of vehicle control surface power system requirements.

Chambliss, E. B.↗

Gemini Program Mission Planning Report

This report defines the Gemini Program objectives and presents guidelines for the individual Gemini missions. It provides general space vehicle configuration data, and descriptions of planned missions. Contingency mission requirements and extravehicular operations to be performed during specific missions are described in the last two sections of the basic document. Data on spacecraft weights and Gemini Launch Vehicle performance capabilities are provided in Appendix A, while Appendix B provides descriptions of onboard experiments to be conducted during Gemini missions.

Source record↗

Humidity

The glossary contains atmospheric and ground vapor concentration data on the various NASA space vehicle development and operation sites for consideration by the vehicle design engineer.

Daniels, G. E.↗

A PC-based bus monitor program for use with the transport systems research vehicle RS-232 communication interfaces

Experiment critical use of RS-232 data busses in the Transport Systems Research Vehicle (TSRV) operated by the Advanced Transport Operating Systems Program Office at the NASA Langley Research Center has recently increased. Each application utilizes a number of nonidentical computer and peripheral configurations and requires task specific software development. To aid these development tasks, an IBM PC-based RS-232 bus monitoring system was produced. It can simultaneously monitor two communication ports of a PC or clone, including the nonstandard bus expansion of the TSRV Grid laptop computers. Display occurs in a separate window for each port's input with binary display being selectable. A number of other features including binary log files, screen capture to files, and a full range of communication parameters are provided.

Easley, Wesley C.↗

Wind Flow Simulation Around NASA KSC Vehicle Assembly Building

A model of the wind flow conditions around Kennedy Space Center (KSC) Vehicle Assembly Building (VA B) is presented. An incompressible Navier-Stokes flow solver was used to compute the flow field around fixed Launch Complex 39 (LC-39) buildings and structures. The 3-D flow field. including velocity magnitude and velocity vectors, was established to simulate the localized wind speeds and directions at specified locations in and around LC-39 buildings and structures. The results of this study not only help explain the physical phenomena of the flow patterns around LC-39 buildings but also are useful to the Shuttle personnel. Current Operations and Maintenance Requirements and Specifications (OMRS) for vehicle transfer operations are based on empirically derived historical data, and no detailed mathematical analysis of wind conditions around LC-39 structures has ever been accomplished.

Vu, B. T.↗

HIRF Tolerance and Avoidance for Advanced Air Mobility Vehicles

Advanced Air Mobility (AAM), including Urban Air Mobility (UAM), and Unmanned Aerial Systems (UAS) vehicles may fly in similar airspace to Transport Category Rotorcraft, thereby requiring meeting the same stringent High-Intensity Radiated Fields (HIRF) certification requirements. In a previous effort, a proposed map-based approach protects a vehicle by keeping it away from high power sources at safe distances based on its tolerance level. By designing to a lower tolerance level, significant cost savings can be achieved at the cost of slightly more complex flight planning. However, too low a threshold can result in large avoidance areas, potentially reducing the vehicle operating space. This current effort suggests a minimum threshold for vehicles operating in an urban area. It is derived from analyzing regulatory transmitter data for New York City as a representative metropolitan. As a result, a vehicle can tolerate common lower-power transmitters by default and only needs to avoid far less common high-power sources. It is also found the existing HIRF requirements may be insufficient against many powerful transmitters such as weather radars and satellite uplink transmitters, and that the map-based approach can address this concern.

HIRF↗

Pathfinding for Airspace with Autonomous Vehicles (PAAV) Multi-Vehicle Operations with Digital Trajectories

The Path Finding for Airspace with Autonomous Vehicles (PAAV) subproject under ATM-X is developing concepts and solutions to allow pilots to supervise multiple uncrewed flights at a time. This line of research stems from industry's desire to leverage Uncrewed Aircraft (UA) operations to achieve maximum productivity from pilot and aircraft resources, driven partially by pilot staffing shortages. Trajectory based solutions delivered by data link offer a potential solution to the multi-vehicle (m:N) problem by minimizing the number of instructions between remote pilots and air traffic controllers. Furthermore, such solutions avoid the need for pilots to monitor multiple voice frequencies at a time for air traffic control instructions to manage multiple flights. This panel presentation will give a brief introduction to PAAV followed by a description of NASA's AutoResolver capability for generating comprehensive air traffic control clearances and communicating them via data link for controller approval and flight execution.

multi vehicle control, trajectory based operations↗

Computer vision research at Marshall Space Flight Center

Orbital docking, inspection, and sevicing are operations which have the potential for capability enhancement as well as cost reduction for space operations by the application of computer vision technology. Research at MSFC has been a natural outgrowth of orbital docking simulations for remote manually controlled vehicles such as the Teleoperator Retrieval System and the Orbital Maneuvering Vehicle (OMV). Baseline design of the OMV dictates teleoperator control from a ground station. This necessitates a high data-rate communication network and results in several seconds of time delay. Operational costs and vehicle control difficulties could be alleviated by an autonomous or semi-autonomous control system onboard the OMV which would be based on a computer vision system having capability to recognize video images in real time. A concept under development at MSFC with these attributes is based on syntactic pattern recognition. It uses tree graphs for rapid recognition of binary images of known orbiting target vehicles. This technique and others being investigated at MSFC will be evaluated in realistic conditions by the use of MSFC orbital docking simulators. Computer vision is also being applied at MSFC as part of the supporting development for Work Package One of Space Station Freedom.

Vinz, Frank L.↗

Identifying Common Use Cases across Extensible Traffic Management (xTM) for Interactions with Air Traffic Controllers

NASA’s Extensible Traffic Management (xTM) builds on the foundation and the architecture of Unmanned Aircraft Systems (UAS) Traffic Management (UTM) concept and extends it broadly to other domains, such as Advanced / Urban Air Mobility (AAM/UAM) and Upper Class E Traffic Management (ETM). These xTM concepts assume the ability to fly in airspace that is authorized to operate solely under xTM services and mostly without any air traffic control (ATC) support. However, they also assume circumstances in which the xTM vehicles would need to operate in conventional ATC-managed airspace, both during nominal and off-nominal scenarios. Due to the vast differences in the xTM vehicle performances and missions, there is a concern that ATC may have difficulty in safely managing the xTM traffic and providing appropriate services to all vehicles, unless a consistent set of roles, procedures, and data exchange requirements are defined across the diverse set of xTM vehicle operations. In this paper, we describe a set of use cases that have been identified in UTM, AAM/UAM, and ETM operations that are related to ATC interactions, and we propose to categorize these use cases across xTM domains based on common trigger events. Organizing the use cases from the perspective of ATC roles per each trigger event is expected to provide the first step in discovering common procedures and data requirements across xTM domains that could help ease the controllers’ cognitive task load and allow them to manage these interactions more safely.

Extensible Traffic Management (xTM)↗

HIRF Tolerance and Avoidance for Advanced Air Mobility Vehicles

Advanced Air Mobility (AAM), including Urban Air Mobility (UAM), and Unmanned Aerial Systems (UAS) vehicles may fly in similar airspace to Transport Category Rotorcraft, thereby requiring meeting the same stringent High-Intensity Radiated Fields (HIRF) certification requirements. In a previous effort, a proposed map-based approach protects a vehicle by keeping it away from high power sources at safe distances based on its tolerance level. By designing to a lower tolerance level, significant cost savings can be achieved at the cost of slightly more complex flight planning. However, too low a threshold can result in large avoidance areas, potentially reducing the vehicle operating space. This current effort suggests a minimum threshold for vehicles operating in an urban area. It is derived from analyzing regulatory transmitter data for New York City as a representative metropolitan area. As a result, a vehicle can tolerate common lower-power transmitters by default and only needs to avoid far less common high-power sources. It is also found the existing HIRF requirements may be insufficient against many powerful transmitters such as weather radars and satellite uplink transmitters, and that the map-based approach can address this concern.

HIRF↗

Status Report on Aeroelasticity in the Vehicle Development for X-57 Maxwell

Risk reduction is the objective of the X-57 Maxwell aeroelasticity team. The X-57, NASA’s experimental electric propulsion aircraft, has a long thin wing with primary propulsion systems located at the wing tips and high lift motors distributed along the span. Many of the classical aeroelastic concerns associated with such a configuration were addressed through early design decisions. The as-designed intermediate flight vehicle configurations show flutter mechanisms associated with flexible models of control surface systems –the stabilator, flaps and ailerons. Improvements to the analytical models, based on ground test data and project decisions about flight operations, show improved prospects of the vehicle being aeroelastically stable throughout the flight envelope. On-going ground testing and further analyses will lend credibility to the flutter predictions and vehicle safety.

Heeg, Jennifer↗

NASA Crew Launch Vehicle Approach Builds on Lessons from Past and Present Missions

The United States Vision for Space Exploration, announced in January 2004, outlines the National Aeronautics and Space Administration's (NASA) strategic goals and objectives, including retiring the Space Shuttle and replacing it with a new human-rated system suitable for missions to the Moon and Mars. The Crew Exploration Vehicle (CEV) that the new Crew Launch Vehicle (CLV) lofts into space early next decade will initially ferry astronauts to the International Space Station and be capable of carrying crews back to lunar orbit and of supporting missions to Mars orbit. NASA is using its extensive experience gained from past and ongoing launch vehicle programs to maximize the CLV system design approach, with the objective of reducing total lifecycle costs through operational efficiencies. To provide in-depth data for selecting this follow-on launch vehicle, the Exploration Systems Architecture Study was conducted during the summer of 2005, following the confirmation of the new NASA Administrator. A team of aerospace subject matter experts used technical, budget, and schedule objectives to analyze a number of potential launch systems, with a focus on human rating for exploration missions. The results showed that a variant of the Space Shuttle, utilizing the reusable Solid Rocket Booster as the first stage, along with a new upper stage that uses a derivative of the RS-25 Space Shuttle Main Engine to deliver 25 metric tons to low-Earth orbit, was the best choice to reduce the risks associated with fielding a new system in a timely manner. The CLV Project, managed by the Exploration Launch Office located at NASA's Marshall Space Flight Center, is leading the design, development, testing, and operation of this new human-rated system. The CLV Project works closely with the Space Shuttle Program to transition hardware, infrastructure, and workforce assets to the new launch system . leveraging a wealth of lessons learned from Shuttle operations. The CL V is being designed to reduce costs through a number of methods, ranging from validating requirements to conducting trades studies against the concept design. Innovations such as automated processing will build on lessons learned from the Shuttle, other launch systems, Department of Defense operations experience, and subscale flight tests such as the Delta Clipper-Experimental Advanced (DCXA) vehicle operations that utilized minimal touch labor, automated cryogen ic propellant loading , and an 8-hour turnaround for a cryogenic propulsion system. For the CLV, the results of hazard analyses are contributing to an integrated vehicle health monitoring system that will troubleshoot anomalies and determine which ones can be solved without human intervention. Such advances will help streamline the mission operations process for pilots and ground controllers alike. In fiscal year 2005, NASA invested approximately $4.5 billion of its $16 bill ion budget on the Space Shuttle. The ultimate goal of the CLV Project is to deliver a safe, reliable system designed to minimize lifecycle costs so that NASA's budget can be invested in missions of scientific discovery. Lessons learned from developing the CLV will be applied to the growth path for future systems, including a heavy lift launch vehicle.

Dumbacher, Daniel L.↗

Development of a Display Tool to Quality Control Weather Balloon Data for Space Launch Vehicles Using Python

Continuous atmospheric data analysis is an important factor for space launch vehicle design and operations. The balloon quality control tool was developed by NASA’s Marshall Space Flight Center (MSFC) Natural Environments Branch (NEB) for monitoring quality control processes and verifying the automated flags created on the balloon data sets analyzed. The data sets currently analyzed are comprised of high-resolution and low-resolution balloon data from NASA Kennedy Space Center (KSC), co-located on the United States Air Force’s Eastern range (ER) at the Cape Canaveral Air Force Station. The NEB was tasked to perform a quality assessment of these data sets and needed a tool to confirm the quality control (QC) flags produced from an automated process and add additional QC flags if necessary. This Graphical User Interface (GUI) was developed to visualize all of the data from these balloon sets, display any flags from the automated QC process, and add additional flags to variables if necessary. The GUI was developed in Python 3.6 utilizing different packages available such as pandas for data analysis and manipulation, NumPy for high-performance multidimensional array and tools to compute with and manipulate arrays, Matplotlib for plotting data and Tkinter to build the GUI.

Jessica K Headley↗

Development of a Display Tool to Quality Control Weather Balloon Data for Space Launch Vehicles

Continuous atmospheric data analysis is an important factor for space launch vehicle design and operations. The balloon quality control tool was developed by NASA’s Marshall Space Flight Center (MSFC) Natural Environments Branch (NEB) for monitoring quality control processes and verifying the automated flags created on the balloon data sets analyzed. The data sets currently analyzed are comprised of high-resolution and low-resolution balloon data from NASA Kennedy Space Center (KSC), co-located on the United States Air Force’s Eastern range (ER) at the Cape Canaveral Air Force Station. The NEB was tasked to perform a quality assessment of these data sets and needed a tool to confirm the quality control (QC) flags produced from an automated process and add additional QC flags if necessary. This Graphical User Interface (GUI) was developed to visualize all of the data from these balloon sets, display any flags from the automated QC process, and add additional flags to variables if necessary. The GUI was developed in Python 3.6 utilizing different packages available such as pandas for data analysis and manipulation, NumPy for high-performance multidimensional array and tools to compute with and manipulate arrays, Matplotlib for plotting data and Tkinter to build the GUI.

Jessica K Headley↗

Simulating Secure Data Exchange and Storage for Urban Air Mobility Environments

Urban Air Mobility (UAM) defines an environment for managing operations of vertical takeoff and landing (VTOL) and short takeoff and landing (STOL) vehicles in an urban environment. Within a UAM environment, UAM operators manage fleets of vehicles, relying on Providers of Services for UAM (PSUs) for managing flights in a region of airspace. Flight plan deconfliction is primarily performed by the Discovery and Synchronization Service (DSS), and the Federal Aviation Administration (FAA) maintains control over the UAM space via the FAA-Industry Exchange Protocol (FIDXP). UAM is a federated environment with many different entities owning and operating vehicles, PSUs, and other services. These entities often need to interoperate or access data generated by other organizations. This paper demonstrates the feasibility of using blockchain to facilitate a secure data exchange and storage for this flight information in a UAM environment. In particular, this paper is focused on flight plans and telemetry data. A blockchain network was developed with a set of smart contracts for managing relevant flight data. Hyperledger Fabric was chosen as it is performent, scalable, and allows organizations to reuse existing public key infrastructure (PKI) for identity management. A set of simulated UAM services were also developed. These services propose flight plans and negotiate with other UAM services for airspace access. All interactions between UAM services, as well as vehicle telemetry data, is recorded onto the blockchain. Vehicle telemetry data is generated by a vehicle flight simulation service. This paper successfully demonstrates the feasibility of using blockchain as a secure data exchange and storage mechanism in a UAM environment.

UAM↗

Uranus Orbiter and Probe: Mission Challenges and Concept Updates Since the Origins, Worlds, and Life Decadal Survey

Origins, Worlds, and Life: Planetary Science and Astrobiology in the Next Decade identified a Uranus Orbiter and Probe as the highest-priority strategic mission for the decade 2023–2032, as it enables broad cross-disciplinary science in the largely unexplored Uranian system. The mission architecture evaluated by the Decadal Survey was a singular proof of concept demonstrating that a moderately instrumented mission could deliver Decadal-priority science with a reduced cost and risk posture by leveraging existing technologies to the maximum extent possible. With revised assumptions since the Decadal, we have explored a large trade space including launch vehicles, propulsion options, cruise trajectories, available power sources, viable concept of operations, and science data return for later launch dates without a Jupiter gravity assist. The most repeatable trajectory solutions employ either a commercially derived solar electric propulsion (SEP) transfer stage or the availability of a more capable launch vehicle under development, such as the SpaceX Starship. Orbit insertion has been moved farther from Uranus to acknowledge the remaining uncertainty in Uranian ring structure. A streamlined, SEP-adaptable, orbiter design was developed using two Next Gen Radioisotope Thermoelectric Generators, and the probe design was matured, reducing the entry gravitational acceleration, and assuming the largest Decadal-recommended payload to provide margin for future instrument selections. With this updated design, we also constructed a detailed concept of operations for three representative science cases, returning 13–15 Gbit of science data and spacecraft telemetry per ∼34 day orbit.

Amy A Simon↗