Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “vehicle data collection”

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 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRS1981

A data collection scheme for identification of parameters in a driver model

A high gain steering controller to compensate for limitations in a handicapped driver's range of motion is employed when adapting vehicle to his use. A driver/vehicle system can become unstable as vehicle speed is increased, therefore it is desirable to use a computer simulation of the driver/vehicle combination as a design tool to investigate the system response prior to construction of a controller and road testing. Unknown driver parameters must be identified prior to use of the model for system analysis. A means to collect the data necessary for identification of these driver model parameters without extensive instrumentation of a vehicle to measure and record vehicle states is addressed. Initial tests of the procedure identified all of the driver parameters with errors of 6% or less.

Mooring, B. W.↗
DOE OSTI2024

A framework to enhance disaster debris estimation with AI and aerial photogrammetry

This study addresses the critical need to enhance disaster preparedness and response, focusing on hurricane impact assessment and debris estimation. Accurate assessments in this context are critical for post-event search-and-rescue (SAR) operations and resource distribution. Recent computing advancements are revealing the potential of unmanned aerial vehicles (UAVs) and artificial intelligence (AI) technologies in collecting data and assisting with post-hurricane reconnaissance. However, the use of AI and UAV photogrammetry for accurate disaster impact analysis remains underexplored. To this end, this study proposes a damage and debris analysis framework harnessing reality capture through aerial imagery and photogrammetry. Within this framework, a region-based neural network is leveraged to detect debris locations in aerial imagery with favorable performance. In a testbed within the Beaumont-Port Arthur region, in Southeast Texas, this study performs 3D reality captures of the built environment. Since the accuracy of the 3D reality capture is of importance in research areas associated with time-sensitive disaster response, we further investigate the optimal 2D aerial imagery overlap ratio required to generate a sufficiently accurate 3D model for disaster impact analysis and debris volume estimation. Results indicate that, in the case of aerial imagery for infrastructure systems, a minimum of 60 % overlap is recommended for damage assessment and debris analysis. In contrast, for flat green areas, a minimum of 50 % overlap is adequate. Overall, for disaster response applications, our study reveals that an overlap ratio between 60 % and 70 % is optimal for achieving a balance between time efficiency and data quality in aerial data collection. Furthermore, these quantitative recommendations are crucial for enabling efficient disaster response efforts. Additionally, our study outcomes will improve disaster impact analysis and facilitating timely and effective response strategies.

Artificial intelligence↗
NASA NTRS2016

Comparison of Spatial Correlation Parameters between Full and Model Scale Launch Vehicles

The current vibro-acoustic analysis tools require specific spatial correlation parameters as input to define the liftoff acoustic environment experienced by the launch vehicle. Until recently these parameters have not been very well defined. A comprehensive set of spatial correlation data were obtained during a scale model acoustic test conducted in 2014. From these spatial correlation data, several parameters were calculated: the decay coefficient, the diffuse to propagating ratio, and the angle of incidence. Spatial correlation data were also collected on the EFT-1 flight of the Delta IV vehicle which launched on December 5th, 2014. A comparison of the spatial correlation parameters from full scale and model scale data will be presented.

Kenny, Jeremy↗
DOE OSTI2023

Federal Automotive Statistical Tool: Updates to EVSE Reporting (Federal Electric Vehicle Agency Round-table, October 2023) [Slides]

This presentation presents an overview of coming changes to how federal agencies with motor vehicles will submit required information about the electric vehicle supply equipment (EVSE) inventory and planned deployments through the Federal Automotive Statistical Tool (FAST). This presentation is intended for delivery via WebEx/GoToMeeting at the October 2023 meeting of the DOE-organized Federal Electric Vehicle Agency Round-table (FEVAR). FAST is a web-based information management tool developed and maintained by Idaho National Laboratory and funded by GSA's Office of Government-wide Policy and DOE's Federal Energy Management Program.

33 ADVANCED PROPULSION SYSTEMS↗
NASA NTRSDate not supplied

The Ejectable Data Recorder: A Lean, Risk-Informed Approach for Hardware Development

NASA is developing the Orion spacecraft to transport crew from the Earth to the Moon as part of the Artemis series of missions. To provide a crew escape capability from pre-launch through ascent, the Orion vehicle is equipped with a Launch Abort System (LAS), built by Lockheed Martin, which pulls the capsule away from the launch vehicle in the event of an abort scenario. The Ascent Abort 2 (AA-2) test flight occurred on July 2, 2019,and tested a production version of the LAS to ensure that it can operate as intended, and to collect a large data set from hundreds of sensors on the vehicle to support Orion flight certification. In the original AA-2 architecture, a single-string set of communications antennas on the LAS would downlink all of the in-flight test data to ground stations. However, that communications architecture was predicted to have data dropouts during abort and jettison of the LAS, and would not support data transmission at all after LAS jettison. As a result, a comprehensive trade study was completed, yielding the addition of antennas on the crew module (CM), a buffer/rebroadcast capability for key portions of the flight, and an ejectable data recorder (EDR) subsystem. This EDR subsystem would serve as a backup to the radio frequency (RF) communications system, and would be non-flight critical, providing a unique capability that enabled management to take a different approach with the hardware and software development. The Crew Module and Separation Ring were developed as “Class 1”Flight Hardware, albeit with some tailoring approaches to enable efficiencies. The Class 1 designation requires full rigor for flight hardware and software, documenting everything that happens to a piece of hardware from procurement through disposal, requiring a full spectrum of acceptance tests, and the highest rigor of quality assurance processes. At the other end of the spectrum, Class 3hardware is controlled, but not intended for flight, and leaves the level of rigor up to the project manager. This classification is often used for research and development projects. Similarly,Class-1E has been recently defined at NASA for ISS payloads and technology development projects that are not flight critical and do not need the full rigor of Class 1 to be successful. The EDR subsystem was challenged at commencement to adopt a skunkworks and agile-like approach to hardware development, allowing for a different risk posture than the rest of the AA-2 hardware. After initially pursuing Class 1 processes, the EDR subsystem design evolved to incorporating numerous commercial components, leading to re-designation as a Class-1E subsystem. The resulting EDR subsystem was fully successful in meeting all flight system requirements, and achieved 100% retrieval of flight test data. This paper will discuss the risk posture of the EDR subsystem and the subsequent tailoring that was enacted as part of its Class-1E status.

EDR↗
DOE OSTI2023

Federal Automotive Statistical Tool: Federal Vehicle Fleet Reporting Update (Combined FedFleet/FEVAR/INTERFUEL Meeting, November 2023) [Slides]

This presentation presents an overview of coming changes to how federal agencies with motor vehicles will submit required information about the electric vehicle supply equipment (EVSE) inventory and planned deployments through the Federal Automotive Statistical Tool (FAST), as well as updates on fleet reporting in general. This presentation is intended for delivery via WebEx/GoToMeeting at the November 2023 meeting of the DOE/GSA jointly-organized combined meeting of the Federal Electric Vehicle Agency Round-table (FEVAR), FedFleet, and INTERFUEL working groups. FAST is a web-based information management tool developed and maintained by Idaho National Laboratory and funded by GSA's Office of Government-wide Policy and DOE's Federal Energy Management Program.

33 ADVANCED PROPULSION SYSTEMS↗
NASA NTRS2011

Ground Processing Affordability for Space Vehicles

Launch vehicles and most of their payloads spend the majority of their time on the ground. The cost of ground operations is very high. So, why so often is so little attention given to ground processing during development? The current global space industry and economic environment are driving more need for efficiencies to save time and money. Affordability and sustainability are more important now than ever. We can not continue to treat space vehicles as mere science projects. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability which are not available for ELV's (Expendable Launch Vehicles). More human-rated vehicles are being developed, with the retirement of the Space Shuttles, and for a new global space race, yet these cost more than the many unmanned vehicles of today. We can learn many lessons on affordability from RLV's. DFO (Design for Operations) considers ground operations during design, development, and manufacturing-before the first flight. This is often minimized for space vehicles, but is very important. Vehicles are designed for launch and mission operations. You will not be able to do it again if it is too slow or costly to get there. Many times, technology changes faster than space products such that what is launched includes outdated features, thus reducing competitiveness. Ground operations must be considered for the full product Lifecycle, from concept to retirement. Once manufactured, launch vehicles along with their payloads and launch systems require a long path of processing before launch. Initial assembly and testing always discover problems to address. A solid integration program is essential to minimize these impacts, as was seen in the Constellation Ares I-X test rocket. For RLV's, landing/recovery and post-flight turnaround activities are performed. Multi-use vehicles require reconfiguration. MRO (Maintenance, Repair, and Overhaul) must be well-planned--- even for the unplanned problems. Defect limits and standard repairs need to be in-place as well as easily added. Many routine inspections and maintenance can be like an aircraft overhaul. Modifications and technology upgrades should be expected. Another factor affecting ground operations efficiency is trending. It is essential for RLV's, and also useful for ELV's which fly the same or similar models again. Good data analysis of technical and processing performance will determine fixes and improvements needed for safety, design, and future processing. Collecting such data on new or low-frequency vehicles is a challenge. Lessons can be learned from the Space Shuttle, or even the Concorde aircraft. For all of the above topics, efficient business systems must be established for comprehensive program management and good throughput. Drawings, specifications, and manuals for an entire launch vehicle are often in different formats from multiple vendors, plus they have proprietary constraints. Nonetheless, the integration team must ensure that all data needed is compatible and visible to each appropriate team member. Ground processing systems for scheduling, tracking, problem resolution, etc. must be well laid-out. The balance between COTS (commercial off the shelf) and custom software is difficult. Multiple customers, vendors, launch sites, and landing sites add to the complexity of efficient IT (Information Technology) tools.

Ingalls, John↗
NASA NTRS2024

Concept, Design, & Implementation of a Remote Vehicle Operations Center for Autonomous Missions

The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. The prototype facility known as the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center is being used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. ROAM provides a key capability to enable full end-to-end hardware- and human-in-the-loop simulation testing, connecting with simulated small-UAS and creating a seamless Live-Virtual-Constructive (LVC) environment. This report describes the development of the ROAM UAS Operations Center from concept through design, culminating in the current implementation at NASA’s Langley Research Center.

CERTAIN↗
DOE OSTI2026

Medium- and Heavy-Duty Truck Duty Cycles

This dataset provides second-by-second duty cycle data for Class 6 and Class 8 diesel trucks in Texas, including key vehicle metrics, engine-related data, and GPS data (excluding GPS latitude and longitude to ensure confidentiality). The data were collected via tablets installed on the trucks and organized into daily datasets, each associated with a unique vehicle ID and date. There are 12 daily datasets for Class 6 diesel trucks (three unique vehicle IDs) and 43 daily datasets for Class 8 diesel trucks (six unique vehicle IDs). The units associated with each column are included in the name. The engine performance data include columns such as engine speed, engine percent torque, and engine fuel rate. Road grade (%/100) was estimated using the GPS altitude and wheel-based vehicle speed, which is used as an input for FASTSim. Cumulative distance was also calculated using the wheel-based vehicle speed. Additional columns include: - Engine Speed (RPM): Removed inaccurate readings and used to calculate angular velocity (radians/second). - Torque (N·m): Calculated using engine percent torque, nominal friction percent torque, and engine reference torque values (those columns were removed from dataset), then normalized to express as torque (%). - Flywheel Power (%): Calculated using the angular velocity and torque (in kW), then normalized as a percentage of the maximum value. - Engine Fuel Rate (%) and Torque (%): Both metrics were normalized by dividing by their respective maximum values within each dataset to express them as percentages. The datasets were analyzed to assess the energy impact of various driving behaviors, simulate energy efficiency, and recommend optimal routes for diesel trucks using NLR’s tool called RouteE. For driver coaching, factors like speed and acceleration limits were considered, and idle periods were reduced (assuming the engine was off during idling) to adjust each drive cycle. These adjusted drive cycles were then simulated in FASTSim to evaluate their effect on fleet energy consumption and estimate potential energy savings. The original cycles are available for download on this page ![image](CoVaR_Image_for_Data_Page_Kenworth_Truck.jpg)

1Hz↗
DOE OSTI2026

Introduction to the Demonstration of Pyroshock Response Prediction Methods Using NASA ShockSat Data Virtual Collection

Mechanical shocks, particularly pyroshocks, are environments that all spacecraft and launch vehicles experience. Pyroshocks can be challenging design environments for space hardware because these events are often high frequency, high intensity transients. Furthermore, since design decisions must be made relatively early in the design phase, understanding, and accurately defining pyroshock excitation and the loads that it imparts on components is important to ensure the high reliability required of spacecraft and rockets. Here, general guidelines about shock transmission through spacecraft structures are provided in NASA and MIL handbooks and standards, but these are relatively broad guidelines, and recent studies have shown that more accurate and less-conservative predictions are needed. However, predicting shock response accurately is still a challenge because of the high frequencies in a pyroshock excitation.

Babuska, Vit [Sandia National Laboratories (SNL-NM↗
DOE OSTI2026

2000-2001 California Statewide Household Travel Survey

The 2000-2001 California Statewide Household Travel Survey, conducted under the auspices of the California Department of Transportation, was conducted between October 2000 and December 2001 among households located in each of California's 58 counties. The purpose of the study was to update the statewide database of household socioeconomic and travel information and helped to refine travel estimates, models, and forecasts throughout California. The survey was an essential element in determining statewide and regional travel patterns. A total of 17,040 households participated in the survey, contributing household socioeconomic and travel data. Travel variables collected include trip times, mode, activity at location, origin and destination, and vehicle occupancy, among other travel-related data from 134,173 trips. Residents completed diary records of their daily travel over a 24-hour (weekday) or 48-hour period (Friday/Saturday or Sunday/Monday pair).

1Hz data↗
DOE OSTI2026

Daily operational impacts on battery degradation in heavy-duty electric drayage trucks

Battery aging is a critical factor influencing the performance, longevity, and cost of ownership of battery electric trucks (BETs). This paper presents a comprehensive evaluation of battery aging for two Li-ion battery chemistries, Nickel-Manganese-Cobalt (NMC) and Lithium-Iron-Phosphate (LFP), accounting for both cycling and calendar aging. In contrast to traditional methods that rely on simplified linear degradation models based on manufacturer-provided data, this study employs semi-empirical aging models calibrated to experimentally collected data. The models are integrated into a detailed vehicle simulation environment, enabling a comprehensive assessment of battery degradation under realistic operating conditions. A case study focusing on heavy-duty electric drayage truck operations in the Port of Savannah, GA, is presented to illustrate the impact on battery pack lifespan of: seasonal variations, daily operational activities, charging strategies, and battery storage conditions. The results illuminate the significance of the battery pack’s state of charge during stationary periods, such as overnight storage or weekend parking, on battery degradation and its potential implications for long-term vehicle viability. Additionally, the study explores how different operational and environmental factors affect battery degradation, offering critical insights into best battery charging and storage practices. Our results demonstrate that LFP outperforms NMC in terms of years of useful life; however, by utilizing charging strategies that minimize the amount of time the battery spends resting at high levels of state-of-charge, the lifespan of the battery pack that uses NMC can nonetheless be increased by more than a factor of two.

25 ENERGY STORAGE↗
NASA NTRS2001

Chandra Space Flight Software: Using Software to Autonomously Operation the Largest and Most Sensitive X-Ray Telescope in the World

Chandra is the world's largest and most sensitive X-ray telescope. The Chandra X-ray Observatory is the third in NASA's family of "Great Observatories." The Chandra X-ray Observatory, launched by Space Shuttle Columbia on July 23, 1999, is NASA's newest Great Observatory. The Chandra space flight software is the operational software, which controls and directs the Chandra X-ray Observatory. The Chandra flight software has executed faultlessly for over 13,000 hours on-orbit. The Chandra flight software directly controls the Pointing, Aspect Determination, Electrical Power Subsystem, Propulsion system, and the Command, Communications, and Data Management subsystems. The software controls the spacecraft operations during all phases of the mission. The software also performs thermal control of the telescope to maintain pointing accuracy and monitors radiation levels throughout the orbit so that the Science Instruments can be safed if radiation thresholds are exceeded. The efficient operation of Chandra flight software has enabled the gathering of crucial science data. The Chandra flight software fault protection is the key to early detection and prevention of science instrument or spacecraft damage in an operating platform/environment, which is completely unforgiving. Permanently open Sun Shade Door and ACIS focal plane radiator sensitivity exposes science instruments and mirrors to damage for pointing anomalies causing an attitude excursion. The Chandra flight software must prevent these attitude excursions from occurring for ANY failure. Another example is that the power system has an unregulated bus, which imposes severe operating requirements on Chandra flight software to control array pointing and battery connection/disconnect using a unique algorithmic and logic approach. The Chandra flight software has enabled a truly autonomous vehicle with greater than 99% of all mission data collected as planned. Less than 15% of spacecraft operations are conducted in view (1 hour out of 8) leading to very extended periods without ground contact. The Chandra flight software implements the flexible mission plan during this out of view period, manages the solid state recorder capacity, controls all pointing and maneuvers, provides fault detection for all satellite subsystems, and initiates communications with the ground at the appropriate time. This paper will describe the software architecture features, key design elements and software testing techniques that have facilitated Chandra's success.

Crumbley, Tim↗
NASA NTRS2010

Evaluation of Gear Condition Indicator Performance on Rotorcraft Fleet

The U.S. Army is currently expanding its fleet of Health Usage Monitoring Systems (HUMS) equipped aircraft at significant rates, to now include over 1,000 rotorcraft. Two different on-board HUMS, the Honeywell Modern Signal Processing Unit (MSPU) and the Goodrich Integrated Vehicle Health Management System (IVHMS), are collecting vibration health data on aircraft that include the Apache, Blackhawk, Chinook, and Kiowa Warrior. The objective of this paper is to recommend the most effective gear condition indicators for fleet use based on both a theoretical foundation and field data. Gear diagnostics with better performance will be recommended based on both a theoretical foundation and results of in-fleet use. In order to evaluate the gear condition indicator performance on rotorcraft fleets, results of more than five years of health monitoring for gear faults in the entire HUMS equipped Army helicopter fleet will be presented. More than ten examples of gear faults indicated by the gear CI have been compiled and each reviewed for accuracy. False alarms indications will also be discussed. Performance data from test rigs and seeded fault tests will also be presented. The results of the fleet analysis will be discussed, and a performance metric assigned to each of the competing algorithms. Gear fault diagnostic algorithms that are compliant with ADS-79A will be recommended for future use and development. The performance of gear algorithms used in the commercial units and the effectiveness of the gear CI as a fault identifier will be assessed using the criteria outlined in the standards in ADS-79A-HDBK, an Army handbook that outlines the conversion from Reliability Centered Maintenance to the On-Condition status of Condition Based Maintenance.

Antolick, Lance J.↗
NASA NTRS2017

Open-Loop Flight Testing of COBALT GN&C Technologies for Precise Soft Landing

A terrestrial, open-loop (OL) flight test campaign of the NASA COBALT (CoOperative Blending of Autonomous Landing Technologies) platform was conducted onboard the Masten Xodiac suborbital rocket testbed, with support through the NASA Advanced Exploration Systems (AES), Game Changing Development (GCD), and Flight Opportunities (FO) Programs. The COBALT platform integrates NASA Guidance, Navigation and Control (GN&C) sensing technologies for autonomous, precise soft landing, including the Navigation Doppler Lidar (NDL) velocity and range sensor and the Lander Vision System (LVS) Terrain Relative Navigation (TRN) system. A specialized navigation filter running onboard COBALT fuzes the NDL and LVS data in real time to produce a precise navigation solution that is independent of the Global Positioning System (GPS) and suitable for future, autonomous planetary landing systems. The OL campaign tested COBALT as a passive payload, with COBALT data collection and filter execution, but with the Xodiac vehicle Guidance and Control (G&C) loops closed on a Masten GPS-based navigation solution. The OL test was performed as a risk reduction activity in preparation for an upcoming 2017 closed-loop (CL) flight campaign in which Xodiac G&C will act on the COBALT navigation solution and the GPS-based navigation will serve only as a backup monitor.

Carson, John M., III↗
NASA NTRSDate not supplied

NASA’s Space Launch System: Artemis I Results and the Path Forward

The Artemis era of human space exploration beyond low Earth orbit launched at 1:47 a.m. EST on November 16, 2022. Artemis I was the first integrated flight of the agency’s new super heavy-lift rocket, the Space Launch System (SLS), and the next-generation spacecraft for astronauts, Orion. The mission sent an uncrewed Orion spacecraft into a distant retrograde orbit about the Moon. During the 25-day mission, NASA collected valuable data on the performance of the launch vehicle and crew spacecraft and information on the deep space environment where crews will soon operate. Orion splashed down approximately 80 miles off the coast of Baja, California, at the conclusion of the mission December 11. This paper will provide a summary of the launch campaign from vehicle integration and testing through completion of the upper stage phase with primary emphasis on SLS. It will also discuss highlights of progress on manufacturing and testing of SLS hardware and software for upcoming Artemis missions.

John Honeycutt↗
NASA NTRSDate not supplied

Flight-Test Approach for X-57 Mod II Configuration

The primary objective of the X-57 Mod II test flights is to perform a functional checkout of the research traction battery power and motor systems, perform an airworthiness assessment of the modified vehicle, and to collect baseline performance, stability, and acoustic data for comparisons with later modifications of the X-57 airplane. This paper describes the planned flight operations of the Mod II airplane, the unique considerations and decisions made in operating an electric aircraft, and the development and planning of the research test points necessary to achieve the Mod II flight objectives. Due to the constrained flight time, which resulted from limited capacity of the battery system, careful scripting of flights was required to maximize test time and execute test points efficiently.

James Reynolds↗
DOE OSTI2020

The energy footprint of automotive electronic sensors

We discuss how Information and communication technologies (ICT) have emerged as one of the leading technologies to reduce global emissions, particularly in the mobility sector. Automotive electronics, such as sensors/actuators and microcontrollers (commonly known as electronic control units (ECU) which control one or more of the electrical systems or subsystems in a vehicle), play a key role in ICT. Sensors/actuators are key in electronic ICT devices, starting with the data collection and data communication with the internet. The latest two big trends of electrification and automation in vehicles, are projected to increase the use of worldwide automotive sensors from 7.5 billion units in 2017 to 11.0 billion units by the year 2024. A representative state-of-the art automotive sensor system, (i.e., an ultrasonic backup system), including the ECUs controlling the vehicle electrical systems/subsystems, has been considered to estimate the energy footprint in terms of manufacturing and operational energy of global automotive sensors use. A widely used life cycle energy assessment method (i.e., cumulative energy demand) was used as both direct and indirect (including the extraction, manufacturing, and disposal of the raw and auxiliary materials) energy use can be considered for the energy footprint estimation. The embodied manufacturing energy impacts of the system was estimated to be 559 MJ/system, compared to the 417 MJ/system for lifetime system power and additional gasoline use. The share of purchased energy to the embodied energy where the upstream energy isn't included in the former case, is less than 10% and ~ 85% for the component manufacturing and vehicle operation energy uses, respectively. As the purpose of this ultrasonic backup system is to prevent rear crashes, an estimated 1.0 MJ/system is avoided from reduced lifetime vehicular repairs (from an estimated 11% chance of requiring a rear bumper replacement). While all of this is small compared to the overall automotive manufacturing and use energy, the 11 billion automotive sensors expected to be produced in 2024 could require 1540 PJ for manufacturing and those sensors would require an additional 780–1150 PJ for lifetime energy use.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗