Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “hardware and 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 685 records · Page 38
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

Using the cFS Command and Data Dictionary (CCDD) to Automate Software Development on Habulous

Final paper is attached. The NASA developed Core Flight System (cFS) is a reusable software architecture that has been used on multiple spaceflight missions. By using this framework, missions are able to reuse code from other missions, as well as leverage deployment onto similar computer architectures (i.e. not "reinvent the wheel" on each new mission). The success in the cFS concept can be seen in the large number of projects using cFS at FSW-2018. The Habulous project is an Earth-based testbed, used for hardware and software that may one day be used on a future space habitat unit, with many participating groups from various NASA centers and aerospace organizations around the country. The distributed nature of the various teams mean that defining (and following) an interface definition is critical on the project. Additionally, since various groups use various types of computer hardware (32/64-bit, big/little endian, Linux/VxWorks/Windows) many additional complications exist in interfacing all the various components into a final integrated system. cFS is used on the majority the flight software (FSW) in running in Habulous. But some subsystems have elected to not use cFS, and use a software bridge (called SBN_lib) to interact with the other cFS nodes in Habulous. In order to most efficiently develop the FSW, a central database is used to define and store each message sent by cFS. A Command and Data Dictionary (CDD) is something nearly universal on spacecraft, but as a team we worked to develop the CDD before the SW development was complete, and not treat it like "as built" documentation. To manage the CDD, the cFS Command and Data Dictionary (CCDD) tool was chosen (available from NASA as open source software). The CCDD tool has successfully been used to automate/autocode a large amount of software used on Habulous, as we are hoping to use it to define even more items in the future (time-triggered Ethernet (TTE) network maps, CPU scheduling). Additionally, Habulous has been exploring the use of cFS on wildly heterogeneous CPUs, and how to coordinate all those various machines using/extending the software bus – network (SBN) application in cFS, as well as TTE to coordinate message passing between various synchronized machines. The major topics to be covered in the presentation are: (1) Updating to the CCSDS_v2 extended headers (and using CPU# as subsystem ID). (2) Managing all the message identification numbers for each cFS message sent/received on any of the various CPUs. (3) Using the CCDD information to automatically generate the C-header files that define the structure for all software bus (SB) commands/telemetry messages. (4) Using the CCDD to automatically generate XML Telemetry and Command Exchange (XTCE) files, which streams display production/integration/testing in a web based display architecture (5) Extending/customizing SBN to pass messages among computers on multiple networks. (6) Using "Protobetter" inside SBN to manage different endian-ness/architectures. (7) Using SBN_lib to allow non-cFS node to communicate with cFS nodes. (8) Developing TTE network and schedule tables for all the various CPUs to use.

Hirsh, Robert L.↗
NASA NTRS2001

A Framework for Distributed Rover Control and Three Sample Applications

In order to develop quality control software for multiple robots, a common interface is required. By developing components in a modular fashion with well-defined boundaries, roboticists can write code to program a generic rover, and only require very simple modifications to run on any robot with a properly implemented framework. The proposed framework advances a Generic Rover that could be any rover, from Real World Interface's All Terrain Robot Vehicle Jr. series to the Fido-class rovers from the Jet Propulsion Laboratory to any other research robot. Using these generic hardware interfaces, software designers and engineers can concentrate on the actual code, and not have to worry about hardware details. In addition to the hardware support framework, three sample applications have been developed to demonstrate the flexibility and extensibility of the framework.

McGuire, Steve↗
NASA NTRS2006

Correction for Thermal EMFs in Thermocouple Feedthroughs

A straightforward measurement technique provides for correction of thermal-electromotive-force (thermal-EMF) errors introduced by temperature gradients along the pins of non-thermocouple-alloy hermetic feedthrough connectors for thermocouple extension wires that must pass through bulkheads. This technique is an alternative to the traditional technique in which the thermal-EMF errors are eliminated by use of custom-made multipin hermetic feedthrough connectors that contain pins made of the same alloys as those of the thermocouple extension wires. One disadvantage of the traditional technique is that it is expensive and time-consuming to fabricate multipin custom thermocouple connectors. In addition, the thermocouple-alloy pins in these connectors tend to corrode easily and/or tend to be less rugged compared to the non-thermocouple-alloy pins of ordinary connectors. As the number of thermocouples (and thus pins) is increased in a given setup, the magnitude of these disadvantages increases accordingly. The present technique is implemented by means of a little additional hardware and software, the cost of which is more than offset by the savings incurred through the use of ordinary instead of thermocouple connectors. The figure schematically depicts a typical measurement setup to which the technique is applied. The additional hardware includes an isothermal block (made of copper) instrumented with a reference thermocouple and a compensation thermocouple. The reference thermocouple is connected to an external data-acquisition system (DAS) through a two-pin thermocouple-alloy hermetic feedthrough connector, but this is the only such connector in the apparatus. The compensation thermocouple is connected to the DAS through two pins of the same ordinary multipin connector that connects the measurement thermocouples to the DAS.

Ziemke, Robert A.↗
NASA NTRSDate not supplied

Exploration Exercise System (EES) Development

Exploration class missions will be required to have an exercise device that is lightweight, has a small footprint, and is capable of providing enough physical stimulus and exercise variability to be an effective countermeasure against muscle and bone loss that results from the microgravity environment. Exploration exercise device prototypes should be evaluated on the ground and in-orbit for feasibility of use in microgravity for long and short duration exploration missions and efficacy of the device to maintain multi-system health and performance. The European Enhanced Exploration Exercise Device (E4D) was selected as the exploration prototype device to be evaluated on ISS for efficacy and feasibility of use as a single multi-modality device for the exercise system for exploration missions. This effort supports the continued development, testing, and verification of E4D hardware and software, internal NASA integration (Human Health and Performance, ISS Vehicle Office, Engineering, and Flight Operations), and external integration across NASA, ESA, and the Danish Aerospace Company (DAC). Providing a feasibility and acceptability assessment from a physiological efficacy and hardware durability standpoint are critical for informing use and risk associated with use on exploration missions. Clearly defined objectives from end users, stakeholders, and Subject Matter Experts (SMEs) will be tested by crewmembers during acute use sessions and long duration use of the exercise device while on ISS. This effort will include a flight study where crewmembers will be asked to exercise using only the E4D during the duration of their mission and participate in a battery of physiological testing to evaluate the efficacy. Hardware is scheduled to launch in FY25 followed by 2 years of operational use after activation and checkout. A final recommendation will be provided to the Artemis program on acceptability of the device for exploration missions. The E4D needs a vibration isolation stabilization (VIS) system that serves as a platform for the exercise hardware to protect the vehicle from loads imparted during exercise. Exploration forward VIS systems will need to protect the vehicle and provide sufficient stabilization for the exerciser during performance of all critical exercises. These enabling capabilities need to be achieved within exploration vehicle power, thermal, mass, and volume limitations.

Kent Lawrence Kalogera↗
NASA NTRS1986

An evaluation of the documented requirements of the SSP UIL and a review of commercial software packages for the development and testing of UIL prototypes

A review was conducted of software packages currently on the market which might be integrated with the interface language and aid in reaching the objectives of customization, standardization, transparency, reliability, maintainability, language substitutions, expandability, portability, and flexibility. Recommendations are given for best choices in hardware and software acquisition for inhouse testing of these possible integrations. Software acquisition in the line of tools to aid expert-system development and/or novice program development, artificial intelligent voice technology and touch screen or joystick or mouse utilization as well as networking were recommended. Other recommendations concerned using the language Ada for the user interface language shell because of its high level of standardization, structure, and ability to accept and execute programs written in other programming languages, its DOD ownership and control, and keeping the user interface language simple so that multiples of users will find the commercialization of space within their realm of possibility which is, after all, the purpose of the Space Station.

Gill, Esther Naomi↗
NASA NTRS1987

X-29A flight control system performance during flight test

An account is given of flight control system performance results for the X-29A forward-swept wing 'Advanced Technology Demonstrator' fighter aircraft, with attention to its software and hardware components' achievement of the requisite levels of system stability and desirable aircraft handling qualities. The Automatic Camber Control Logic is found to be well integrated with the stability loop of the aircraft. A number of flight test support software programs developed by NASA facilitated monitoring of the X-29A's stability in real time, and allowed the test team to clear the envelope with confidence.

Chin, J.↗
NASA NTRS2002

Boudreaux the Robot (a.k.a. EVA Robotic Assistant)

The EVA Robotic Assistant is a prototype for an autonomous rover designed to assist human astronauts. The primary focus of the research is to explore the interaction between humans and robots, particularly in extreme environments, and to develop a software infrastructure that could be applied to any type of assistant robot, whether for planetary exploration or orbital missions. This paper describes the background and current status of the project, the types of scenarios addressed in field demonstrations, the hardware and software that comprise the current prototype, and future research plans.

Shillcutt, Kimberly↗
NASA NTRS2006

Assistant for Analyzing Tropical-Rain-Mapping Radar Data

A document is defined that describes an approach for a Tropical Rain Mapping Radar Data System (TDS). TDS is composed of software and hardware elements incorporating a two-frequency spaceborne radar system for measuring tropical precipitation. The TDS would be used primarily in generating data products for scientific investigations. The most novel part of the TDS would be expert-system software to aid in the selection of algorithms for converting raw radar-return data into such primary observables as rain rate, path-integrated rain rate, and surface backscatter. The expert-system approach would address the issue that selection of algorithms for processing the data requires a significant amount of preprocessing, non-intuitive reasoning, and heuristic application, making it infeasible, in many cases, to select the proper algorithm in real time. In the TDS, tentative selections would be made to enable conversions in real time. The expert system would remove straightforwardly convertible data from further consideration, and would examine ambiguous data, performing analysis in depth to determine which algorithms to select. Conversions performed by these algorithms, presumed to be correct, would be compared with the corresponding real-time conversions. Incorrect real-time conversions would be updated using the correct conversions.

James, Mark↗
NASA NTRSDate not supplied

Mars Ascent Vehicle GNC Targeting Routines with Considerations for Flight Software Development

The Mars Ascent Vehicle (MAV) will be the first vehicle to perform an ascent from the surface of another atmospheric planetary body outside of the Earth-Moon system. Significant light-time delay requires complete autonomy of flight throughout ascent, and naturally a high level of reliability is desired in both MAV’s hardware and software subsystems. The MAV Guidance, Navigation and Controls (GNC) team and the MAV Flight Software (FSW) team have partnered together to improve the efficiency of algorithm integration onto the MAV flight processor, and to increase confidence that said integration is successful and without human error. An interface architecture is proposed for the GNC suite that allows both the guidance and navigation subsystems to provide code algorithms directly in C++, and the controls subsystem to provide MATLAB Simulink auto-coded algorithms. Several continuous integration/deployment (CI/CD) methodologies have been considered for ease of transition of algorithm code from the GNC team to the FSW team. The GNC/FSW teams also worked together to develop a cFS-friendly wrapper which abstracts the integration of the GNC algorithm code into an interface-level API that is compatible with cFS. Several iterations of vehicle GNC code have been produced between the GNC/FSW team’s partnership, and this strong interface between these two teams have allowed the GNC/FSW teams to greatly increase confidence of efficient and error-free implementation of the GNC code onto MAV for a successful flight.

Jason Everett↗
NASA NTRS1984

PASLIB programmer's guide for the finite element machine, revision 2.1-A

PASLIB is a library of Pascal callable subroutines designed to give application programs access to the unique architectural features of the Finite Element Machine and to the software support services provided by the Nodal Exec operating system which runs on it. The PASLIB subroutines are documented and the procedures needed to write Pascal programs for execution on the Finite Element Machine are defined. Considerations for obtaining optimum hardware and software performance are given. A brief overview of debugging and performance analysis capabilities available to the programmer is presented.

Crockett, T. W.↗
NASA NTRS2011

The Use of Modeling for Flight Software Engineering on SMAP

The Soil Moisture Active Passive (SMAP) mission proposes to deploy an Earth-orbiting satellite with the goal of obtaining global maps of soil moisture content at regular intervals. Launch is currently planned in 2014. The spacecraft bus would be built at the Jet Propulsion Laboratory (JPL), incorporating both new avionics as well as hardware and software heritage from other JPL projects. [4] provides a comprehensive overview of the proposed mission

Software architecture↗
NASA NTRS1996

GPS Monitor Station Upgrade Program at the Naval Research Laboratory

One of the measurements made by the Global Positioning System (GPS) monitor stations is to measure the continuous pseudo-range of all the passing GPS satellites. The pseudo-range contains GPS and monitor station clock errors as well as GPS satellite navigation errors. Currently the time at the GPS monitor station is obtained from the GPS constellation and has an inherent inaccuracy as a result. Improved timing accuracy at the GPS monitoring stations will improve GPS performance. The US Naval Research Laboratory (NRL) is developing hardware and software for the GPS monitor station upgrade program to improve the monitor station clock accuracy. This upgrade will allow a method independent of the GPS satellite constellation of measuring and correcting monitor station time to US Naval Observatory (USNO) time. THe hardware consists of a high performance atomic cesium frequency standard (CFS) and a computer which is used to ensemble the CFS with the two CFS's currently located at the monitor station by use of a dual-mixer system. The dual-mixer system achieves phase measurements between the high-performance CFS and the existing monitor station CFS's to within 400 femtoseconds. Time transfer between USNO and a given monitor station is achieved via a two way satellite time transfer modem. The computer at the monitor station disciplines the CFS based on a comparison of one pulse per second sent from the master site at USNO. The monitor station computer is also used to perform housekeeping functions, as well as recording the health status of all three CFS's. This information is sent to the USNO through the time transfer modem. Laboratory time synchronization results in the sub nanosecond range have been observed and the ability to maintain the monitor station CFS frequency to within 3.0 x 10 (sup minus 14) of the master site at USNO.

Galysh, Ivan J.↗
NASA NTRS2012

Development of 3-D Ice Accretion Measurement Method

A research plan is currently being implemented by NASA to develop and validate the use of a commercial laser scanner to record and archive fully three-dimensional (3-D) ice shapes from an icing wind tunnel. The plan focused specifically upon measuring ice accreted in the NASA Icing Research Tunnel (IRT). The plan was divided into two phases. The first phase was the identification and selection of the laser scanning system and the post-processing software to purchase and develop further. The second phase was the implementation and validation of the selected system through a series of icing and aerodynamic tests. Phase I of the research plan has been completed. It consisted of evaluating several scanning hardware and software systems against an established selection criteria through demonstrations in the IRT. The results of Phase I showed that all of the scanning systems that were evaluated were equally capable of scanning ice shapes. The factors that differentiated the scanners were ease of use and the ability to operate in a wide range of IRT environmental conditions.

Lee, Sam↗
NASA NTRS2001

Automated Theorem Proving in High-Quality Software Design

The amount and complexity of software developed during the last few years has increased tremendously. In particular, programs are being used more and more in embedded systems (from car-brakes to plant-control). Many of these applications are safety-relevant, i.e. a malfunction of hardware or software can cause severe damage or loss. Tremendous risks are typically present in the area of aviation, (nuclear) power plants or (chemical) plant control. Here, even small problems can lead to thousands of casualties and huge financial losses. Large financial risks also exist when computer systems are used in the area of telecommunication (telephone, electronic commerce) or space exploration. Computer applications in this area are not only subject to safety considerations, but also security issues are important. All these systems must be designed and developed to guarantee high quality with respect to safety and security. Even in an industrial setting which is (or at least should be) aware of the high requirements in Software Engineering, many incidents occur. For example, the Warshaw Airbus crash, was caused by an incomplete requirements specification. Uncontrolled reuse of an Ariane 4 software module was the reason for the Ariane 5 disaster. Some recent incidents in the telecommunication area, like illegal "cloning" of smart-cards of D2GSM handies, or the extraction of (secret) passwords from German T-online users show that also in this area serious flaws can happen. Due to the inherent complexity of computer systems, most authors claim that only a rigorous application of formal methods in all stages of the software life cycle can ensure high quality of the software and lead to real safe and secure systems. In this paper, we will have a look, in how far automated theorem proving can contribute to a more widespread application of formal methods and their tools, and what automated theorem provers (ATPs) must provide in order to be useful.

Schumann, Johann↗
NASA NTRS2012

Positional Awareness Map 3D (PAM3D)

The Western Aeronautical Test Range of the National Aeronautics and Space Administration s Dryden Flight Research Center needed to address the aging software and hardware of its current situational awareness display application, the Global Real-Time Interactive Map (GRIM). GRIM was initially developed in the late 1980s and executes on older PC architectures using a Linux operating system that is no longer supported. Additionally, the software is difficult to maintain due to its complexity and loss of developer knowledge. It was decided that a replacement application must be developed or acquired in the near future. The replacement must provide the functionality of the original system, the ability to monitor test flight vehicles in real-time, and add improvements such as high resolution imagery and true 3-dimensional capability. This paper will discuss the process of determining the best approach to replace GRIM, and the functionality and capabilities of the first release of the Positional Awareness Map 3D.

Hoffman, Monica↗
NASA NTRS2014

Facility Systems, Ground Support Systems, and Ground Support Equipment General Design Requirements

KSC-DE-512-SM establishes overall requirements and best design practices to be used at the John F. Kennedy Space Center (KSC) for the development of ground systems (GS) in support of operations at launch, landing, and retrieval sites. These requirements apply to the design and development of hardware and software for ground support equipment (GSE), ground support systems (GSS), and facility ground support systems (F-GSS) used to support the KSC mission for transportation, receiving, handling, assembly, test, checkout, servicing, and launch of space vehicles and payloads and selected flight hardware items for retrieval. This standards manual supplements NASA-STD-5005 by including KSC-site-specific and local environment requirements. These requirements and practices are optional for equipment used at manufacturing, development, and test sites.

Ground Support Systems↗
NASA NTRS2017

Space Technology Game Changing Development: NASA Affordable Vehicle Avionics (AVA)

Common Modular Avionics System for Nanolaunchers Offering Affordable Access to Space Small satellites are becoming ever more capable of performing valuable missions for both government and commercial customers. However, currently these satellites can be launched affordably only as secondary payloads. This makes it difficult for the small satellite mission to launch when needed, to the desired orbit, and with acceptable risk. What is needed is a class of low-cost launchers, so that launch costs to low-Earth orbit (LEO) are commensurate with payload costs. Several private and government-sponsored launch vehicle developers are working toward just that—the ability to affordably insert small payloads into LEO. But until now, cost of the complex avionics remained disproportionately high. AVA solves this problem. Significant contributors to the cost of launching nanosatellites to orbit are the avionics and software systems that steer and control the launch vehicles, sequence stage separation, deploy payloads, and telemeter data. The high costs of these guidance, navigation and control (GNC) avionics systems are due in part to the current practice of developing unique, single use hardware and software for each launch. High-performance, high-reliability inertial sensors components with heritage from legacy launchers also contribute to costs—but can low-cost commercial inertial sensors work just as well?

Aquilina, Rudy↗
NASA NTRS1994

Electric power system test and verification program

Space Station Freedom's (SSF's) electric power system (EPS) hardware and software verification is performed at all levels of integration, from components to assembly and system level tests. Careful planning is essential to ensure the EPS is tested properly on the ground prior to launch. The results of the test performed on breadboard model hardware and analyses completed to date have been evaluated and used to plan for design qualification and flight acceptance test phases. These results and plans indicate the verification program for SSF's 75-kW EPS would have been successful and completed in time to support the scheduled first element launch.

Rylicki, Daniel S.↗