Search NASA⌕ Search

SEARCH · Search NASA

Results for “software testing”

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 1,081 records · Page 60

Ensemble Eclipse: A Process for Prefab Development Environment for the Ensemble Project

This software simplifies the process of having to set up an Eclipse IDE programming environment for the members of the cross-NASA center project, Ensemble. It achieves this by assembling all the necessary add-ons and custom tools/preferences. This software is unique in that it allows developers in the Ensemble Project (approximately 20 to 40 at any time) across multiple NASA centers to set up a development environment almost instantly and work on Ensemble software. The software automatically has the source code repositories and other vital information and settings included. The Eclipse IDE is an open-source development framework. The NASA (Ensemble-specific) version of the software includes Ensemble-specific plug-ins as well as settings for the Ensemble project. This software saves developers the time and hassle of setting up a programming environment, making sure that everything is set up in the correct manner for Ensemble development. Existing software (i.e., standard Eclipse) requires an intensive setup process that is both time-consuming and error prone. This software is built once by a single user and tested, allowing other developers to simply download and use the software

Wallick, Michael N.↗

Mars rover mechanisms designed for Rocky 4

A Mars rover prototype vehicle named Rocky 4 was designed and built at JPL during the fall of 1991 and spring 1992. This vehicle is the fourth in a series of rovers designed to test vehicle mobility and navigation software. Rocky 4 was the first attempt to design a vehicle with 'flight like' mass and functionality. It was consequently necessary to develop highly efficient mechanisms and structures to meet the vehicles very tight mass limit of 3 Kg for the entire mobility system (7 Kg for the full system). This paper will discuss the key mechanisms developed for the rover's innovative drive and suspension system. These are the wheel drive and strut assembly, the rocker-bogie suspension mechanism and the differential pivot. The end-to-end design, analysis, fabrication and testing of these components will also be discussed as will their performance during field testing. The lessons learned from Rocky 4 are already proving invaluable for the design of Rocky 6. Rocky 6 is currently being designed to fly on NASA's MESUR mission to Mars scheduled to launch in 1996.

Rivellini, Tommaso P.↗

Man-rated flight software for the F-8 DFBW program

The design, implementation, and verification of the flight control software used in the F-8 DFBW program are discussed. Since the DFBW utilizes an Apollo computer and hardware, the procedures, controls, and basic management techniques employed are based on those developed for the Apollo software system. Program assembly control, simulator configuration control, erasable-memory load generation, change procedures and anomaly reporting are discussed. The primary verification tools are described, as well as the program test plans and their implementation on the various simulators. Failure effects analysis and the creation of special failure generating software for testing purposes are described.

Bairnsfather, R. R.↗

Six-Degree-of-Freedom Test Facility

Shuttle to Space station docking has become an important issue in the last few years. Docking sensors have been proposed that will provide high precision measurements required for the fuel efficient rendezvous and docking of space vehicles. These sensors will also be used for satellite servicing and orbital assembly. The performance of the docking sensors must be tested before they are implemented in a space environment. A Six-Degree-of-Freedom (6-DOF) Test Facility has been developed at the Tracking & Communications Section, Johnson Space Center to test the static and dynamic accuracies of docking sensors. A candidate sensor is evaluated by comparing the sensor's static position and velocity measurements to the more accurate 6-DOF system. The 6-DOF Test Facility's hardware is fully integrated. Software has been developed in-house to support system operation. The system has been tested statically and the operational parameters verified. System accuracies remain to be determined. Dynamic testing of the facility is expected to begin shortly. Several companies such as McDonnell Douglas, Autonomous Technologies, and General Dynamics are scheduled to test sensors in the next few months. The 6-DOF facility will be available for use in November 1991. This presentation describes the subcomponents, operation, and capabilities of the 6-DOF Test Facility. Discussions will be held on system accuracies. Additional applications of the 6-DOF system will also be addressed.

Bittel, Michelle A.↗

Database Reports Over the Internet

Most of the summer was spent developing software that would permit existing test report forms to be printed over the web on a printer that is supported by Adobe Acrobat Reader. The data is stored in a DBMS (Data Base Management System). The client asks for the information from the database using an HTML (Hyper Text Markup Language) form in a web browser. JavaScript is used with the forms to assist the user and verify the integrity of the entered data. Queries to a database are made in SQL (Sequential Query Language), a widely supported standard for making queries to databases. Java servlets, programs written in the Java programming language running under the control of network server software, interrogate the database and complete a PDF form template kept in a file. The completed report is sent to the browser requesting the report. Some errors are sent to the browser in an HTML web page, others are reported to the server. Access to the databases was restricted since the data are being transported to new DBMS software that will run on new hardware. However, the SQL queries were made to Microsoft Access, a DBMS that is available on most PCs (Personal Computers). Access does support the SQL commands that were used, and a database was created with Access that contained typical data for the report forms.

Dean Lance Smith↗

Results from Automated Cloud and Dust Devil Detection Onboard the MER

We describe a new capability to automatically detect dust devils and clouds in imagery onboard rovers, enabling downlink of just the images with the targets or only portions of the images containing the targets. Previously, the MER rovers conducted campaigns to image dust devils and clouds by commanding a set of images be collected at fixed times and downloading the entire image set. By increasing the efficiency of the campaigns, more campaigns can be executed. Software for these new capabilities was developed, tested, integrated, uploaded, and operationally checked out on both rovers as part of the R9.2 software upgrade. In April 2007 on Sol 1147 a dust devil was automatically detected onboard the Spirit rover for the first time. We discuss the operational usage of the capability and present initial dust devil results showing how this preliminary application has demonstrated the feasibility and potential benefits of the approach.

dust devils↗

Autonomous Sciencecraft Experiment (ASE) Test Operations in 2003

NASA has identified the development of an autonomously operating spacecraft as a necessity for an expanded program of missions exploring the Solar System. The Autonomous Sciencecraft Experiment (ASE) has been selected for flight demonstration by NASA s New Millennium Program (NMP) as part of the Space Technology 6 (ST6) mission. ASE is scheduled to fly on the US Air Force Research Laboratory (AFRL) Techsat-21 constellation in 2006. Tech- Sat-21 consists of three satellites flying in a variable-geometry formation in Earth orbit. Each satellite is equipped with X-band Synthetic Aperture Radar, yielding high spatial resolution images (approx. 3 m) of the Earth s surface. The constellation will fly at an altitude of 550 km, in a 35.4 inclination circular orbit, yielding exact repeat-track observations every 13 days. Prior to full deployment, elements of the versatile ASE spacecraft command and control software, image formation software and science processing software will be utilized and tested on two very different platforms in 2003: AirSAR and EO-1 (described below). Advantages of Autonomous Operations: ASE will demonstrate advanced autonomous science data acquisition, processing, and product downlink prioritization, as well as autonomous spacecraft command and control, and fault detection. The advantages of spacecraft autonomy are to future missions include: (a) making the best use of reduced downlink; (b) the overcoming of communication delays through decisionmaking in situ, enabling fast reaction to dynamic events; (c) an increase of science content per byte of returned data; and (d) an avoidance of return of null (no-change/no feature) datasets: if there is no change detectable between two scenes of the same target, there is no need to return the second dataset.

Chien, S.↗

TRIDENT Drill Validation at Mars and Lunar Analog Field Sites

Drilling on Earth is typically a human-intensive activity. Drilling on other planets is further complicated by the lack of prior local field surveys of their target area, hence blindly drilling into uncertain target rocks. Field conditions on the Moon or Mars are also different than for shallow drilling on Earth: lower temperatures and pressures, less power available, low masses (hence less weight-on-bit). Given the cost of transport from Earth, no drilling muds or working fluids are likely to be available to carry away cuttings. And impact-gardened regolith and dust vary mechanically and texturally from most terrestrial soils. The Regolith and Ice Drill for Exploration of New Terrains (TRIDENT) is a rotary-percussive 1m-class drill from Honeybee Robotics. It is low-power (rotary and percussive actuators are 200 W each) and lightweight (<20 kg) with the maximum weight on bit limited to 200 N. TRIDENT has been manifested for the Volatiles Investigating Polar Exploration Rover (VIPER) and PRIME-1 lunar south pole missions in 2024, has previously been field tested at a hot, dry analog site in the Atacama Desert, and in lunar conditions in thermal vacuum chamber tests. TRIDENT was also part of the 2019 Icebreaker Mars Discovery proposal, as well as in the Mars Life Explorer concept. During ARADS tests, drill control and fault recovery automation software enabled hands-off operations of a rover-mounted TRIDENT drill. TRIDENT Drill Analog Site Validation: Past TRIDENT tests in thermal vacuum (TVAC) chambers targeted containers of manufactured lunar simulants with added volatiles. 2022 TRIDENT ambient testing at NASA Ames drilled into cemented lunar simulant materials. Low cuttings-permeability led to cuttings buildup, and drill choking and binding was observed. The Atacama analog site in ARADS had desiccated unconsolidated sediments that did not challenge the TRIDENT design. However, lunar polar regolith is expected to be diverse and heterogeneous with varying clast sizes, with abundant impactites and perhaps subsurface ice deposits. Neither the simulants nor Atacama testing had completely covered the TRIDENT-targeted field characteristics, motivating further analog tests prior to the planned lunar missions. To gain more insight into the behavior of the TRIDENT hardware in diverse impactites and subsurface ice, and to verify the software automation in that environment, in August 2023 TRIDENT was brought to Haughton Crater, a field analog site in the Canadian Arctic. In September 2023 the same drill was brought to the Bishop Tuff in southern California to verify whether drilling binding behaviors previously seen in lunar simulant testing would be observed in naturally occurring fine-grained massive layers. The ~22 Ma Haughton Crater impact structure is located at 75 ̊22’ N, 89 ̊41’ W, on northwestern Devon Island, Nunavut, Canada. Numerous deposits of pale-grey crater-fill polymictic impact-melt breccia are found within the crater with a typical thickness reaching ~125 m or greater and covering ~60 km -2 . An approximately 600m-thick permafrost layer is also present with ice typically found within 0.5-0.6m of the surface. The volcanic tableland north of Bishop, CA exposes densely welded tuff laid down during the eruption that created the Long Valley Caldera at approximately 0.76 Ma. Extensional faults and the Owens River gorge expose cross-sections across the plateau. The area is viewed as an analog site for Mars features believed to be of pyroclastic origin. Results: Haughton Crater.Drilling tests were conducted 8-13 August 2023 at a previously undisturbed area separated 5-10 m from past years’ Drill Hill test sites (75.4208, -089.7613). In six days, TRIDENT drilled 8 holes to nearly 1 m depth each, totaling 7.80 m. The active layer/ice boundary was at ~67 cm depth, with a total of approximately 2.4 m drilled into ice or ice-cemented impact breccia. During drilling, five drill fault states were observed and successfully recovered. Holes 23-1, 4 and 7 were drilled under manual control, using Honeybee’s Thorax user interface. Holes 23-5, 6, and 8 were drilled with the Ames IBexec automated drilling control software. TRIDENT was observed to have little difficulty in the thawed uncemented impact breccia above the active layer boundary, but required percussion to make slower headway in the ice-cemented breccia. In Hole 23-7 (Fig.1), drilling slowed down in a massive unit just above the active-layer boundary (perhaps a large rock extending into the ice-cementation?), with only 7cm progress made in 27 minutes of high auger torque and constant percussion, leading to a choking fault and then a binding fault. A similar pattern had been observed in TRIDENT Rio Tinto test data from 2017 [6] as well as in the 2022laboratory tests.Bishop Tuff.A team from NASA Ames and the US Geological Survey deployed the same TRIDENT drill to Bishop Sites 1B and 1C (37.4203, -118.4289; 37.4265, -118.4215) on 13-16 September 2023, on the Bishop Tuff plateau. A third drill site was used 17-18 September 2023(37.4598, -118.3667) in an abandoned pumice mine. Four holes (totaling 2.5m depth) were drilled into the fine-grained, meters-thick tuff units at Sites 1B and 1C, and a further two boreholes (totaling 1.98m depth) were made at the pumice site. Drill behavior in the tuff below 10 cm depth was similar to that seen at 65-74 cm depth in Haughton Hole 23-7 (Fig. 1) and that seen in the 2022 lab simulant drilling. Drill safety torque limits were exceeded multiple times resulting in drill stops downhole. These freezes then required external added torques (with a pipe wrench) to resume rotation, to unstick the drill for withdrawal. To prevent this choking and binding behavior we found that more-frequent cuttings removal was necessary, e.g., reducing the “drill bite” size from the nominal 10 cm to 2 cm per bite --bringing the auger up to the surface more frequently, as seen in Bishop Site 1C Hole 2 (Fig.2). This permitted slow progress without drill binding and without external interventions. Conversely, TRIDENT drilling in the more porous pumice target material showed no cuttings buildup issue, and single bites as large as 40 cm were demonstrated. Discussion: We observed that TRIDENT easily penetrated unconsolidated heterogeneous soils (both above the active layer boundary at Haughton and previously in the Atacama). Cemented or consolidated targets that were cuttings-permeable (icy impact breccia, pumice) required more energy applied and percussion. However, in non-cuttings-permeable targets (welded microporous tuff, cemented simulants, boulder) TRIDENT was observed to be prone to excessive cuttings accumulation leading to choking/binding faults and stalling. The wedge cutting bit, used by TRIDENT in field tests and in its flight versions, pulverizes the target rock and creates fine cuttings that ideally are transported up the auger spirals for removal. In porous, fractured or vesicular target materials (such as at the Bishop pumice site) a significant portion of the cuttings are pushed aside, but for non-fractured, microporous targets the cuttings remain in the borehole and accumulate. Rock powder is relatively incompressible as a working fluid at only 100-200N downward force (TRIDENT limits) and hence eventual drilling progress slows or stops. Our recommended strategy for improving TRIDENT cuttings removal in massive target units with low cuttings-permeability is to reduce TRIDENT bite sizes when encountering these units, from 10cm to as little as 1-2cm, to effectively bail the accumulating cuttings. This approach was demonstrated to reduce choking and allowed slow progress to continue in cuttings-impermeable microporous target units (viz. the Bishop tuff in our September 2023 tests or cemented simulants in 2022 ambient tests).

robotic drilling↗

Man-rated flight software for the F-8 DFBW program

The design, implementation, and verification of the flight control software used in the F-8 DFBW program are discussed. Since the DFBW utilizes an Apollo computer and hardware, the procedures, controls, and basic management techniques employed are based on those developed for the Apollo software system. Program Assembly Control, simulator configuration control, erasable-memory load generation, change procedures and anomaly reporting are discussed. The primary verification tools--the all-digital simulator, the hybrid simulator, and the Iron Bird simulator--are described, as well as the program test plans and their implementation on the various simulators. Failure-effects analysis and the creation of special failure-generating software for testing purposes are described. The quality of the end product is evidenced by the F-8 DFBW flight test program in which 42 flights, totaling 58 hours of flight time, were successfully made without any DFCS inflight software, or hardware, failures.

Bairnsfather, R. R.↗

Development of a 32-bit UNIX-based ELAS workstation

A mini/microcomputer UNIX-based image analysis workstation has been designed and is being implemented to use the Earth Resources Laboratory Applications Software (ELAS). The hardware system includes a MASSCOMP 5600 computer, which is a 32-bit UNIX-based system (compatible with AT&T System V and Berkeley 4.2 BSD operating system), a floating point accelerator, a 474-megabyte fixed disk, a tri-density magnetic tape drive, and an 1152 by 910 by 12-plane color graphics/image interface. The software conversion includes reconfiguring the ELAs driver Master Task, recompiling and then testing the converted application modules. This hardware and software configuration is a self-sufficient image analysis workstation which can be used as a stand-alone system, or networked with other compatible workstations.

Spiering, Bruce A.↗

Verifying Correct Functionality of Avionics Subsystems

This project focuses on the testing of the telecommunications interface subsystem of the Multi-Mission System Architecture Platform to ensure proper functionality. The Multi-Mission System Architecture Platform is a set of basic tools designed to be used in future spacecraft. The responsibilities of the telecommunications interface include communication between the spacecraft and ground teams as well as acting as the bus controller for the system. The tests completed include bit wise read\write tests to each register, testing of status bits, and verifying various bus controller activities. Testing is accomplished through the use of software-based simulations run on an electronic design of the system. The tests are written in Verilog Hardware Definition Language and they simulate specific states and conditions in telecommunication interfaces. Upon successful completion, the output is examined to verify that the system responded appropriately.

Meuer, Ben t.↗

Evolution of the Space Shuttle Primary Avionics Software and Avionics for Shuttle Derived Launch Vehicles

As a result of recommendation from the Augustine Panel, the direction for Human Space Flight has been altered from the original plan referred to as Constellation. NASA s Human Exploration Framework Team (HEFT) proposes the use of a Shuttle Derived Heavy Lift Launch Vehicle (SDLV) and an Orion derived spacecraft (salvaged from Constellation) to support a new flexible direction for space exploration. The SDLV must be developed within an environment of a constrained budget and a preferred fast development schedule. Thus, it has been proposed to utilize existing assets from the Shuttle Program to speed development at a lower cost. These existing assets should not only include structures such as external tanks or solid rockets, but also the Flight Software which has traditionally been a "long pole" in new development efforts. The avionics and software for the Space Shuttle was primarily developed in the 70 s and considered state of the art for that time. As one may argue that the existing avionics and flight software may be too outdated to support the new SDLV effort, this is a fallacy if they can be evolved over time into a "modern avionics" platform. The technology may be outdated, but the avionics concepts and flight software algorithms are not. The reuse of existing avionics and software also allows for the reuse of development, verification, and operations facilities. The keyword is evolve in that these assets can support the fast development of such a vehicle, but then be gradually evolved over time towards more modern platforms as budget and schedule permits. The "gold" of the flight software is the "control loop" algorithms of the vehicle. This is the Guidance, Navigation, and Control (GNC) software algorithms. This software is typically the most expensive to develop, test, and verify. Thus, the approach is to preserve the GNC flight software, while first evolving the supporting software (such as Command and Data Handling, Caution and Warning, Telemetry, etc.). This can be accomplished by gradually removing the "support software" from the legacy flight software leaving only the GNC algorithms. The "support software" could be re-developed for modern platforms, while leaving the GNC algorithms to execute on technology compatible with the legacy system. It is also possible to package the GNC algorithms into an emulated version of the original computer (via Field Programmable Gate Arrays or FPGAs), thus becoming a "GNC on a Chip" solution where it could live forever to be embedded in modern avionics platforms.

Ferguson, Roscoe C.↗

A data acquisition and storage system for the ion auxiliary propulsion system cyclic thruster test

A nine-track tape drive interfaced to a standard personal computer was used to transport data from a remote test site to the NASA Lewis mainframe computer for analysis. The Cyclic Ground Test of the Ion Auxiliary Propulsion System (IAPS), which successfully achieved its goal of 2557 cycles and 7057 hr of thrusting beam on time generated several megabytes of test data over many months of continuous testing. A flight-like controller and power supply were used to control the thruster and acquire data. Thruster data was converted to RS232 format and transmitted to a personal computer, which stored the raw digital data on the nine-track tape. The tape format was such that with minor modifications, mainframe flight data analysis software could be used to analyze the Cyclic Ground Test data. The personal computer also converted the digital data to engineering units and displayed real time thruster parameters. Hardcopy data was printed at a rate dependent on thruster operating conditions. The tape drive provided a convenient means to transport the data to the mainframe for analysis, and avoided a development effort for new data analysis software for the Cyclic test. This paper describes the data system, interfacing and software requirements.

Hamley, John A.↗

International Space Station Urine Monitoring System Functional Integration and Science Testing

Exposure to microgravity during human spaceflight needs to be better understood as the human exploration of space requires longer duration missions. It is known that long term exposure to microgravity causes bone loss. Measuring the calcium and other metabolic byproducts in a crew member s urine can evaluate the effectiveness of bone loss countermeasures. The International Space Station (ISS) Urine Monitoring System (UMS) is an automated urine collection device designed to collect urine, separate the urine and air, measure the void volume, and allow for syringe sampling. Accurate measuring and minimal cross-contamination is essential to determine bone loss and the effectiveness of countermeasures. The ISS UMS provides minimal cross-contamination (<0.7 mL urine) and has volume accuracy of 2% between 100 to 1000 mL urine voids. Designed to provide a non-invasive means to collect urine samples from crew members, the ISS UMS operates in-line with the Node 3 Waste and Hygiene Compartment (WHC). The ISS UMS has undergone modifications required to interface with the WHC, including material changes, science algorithm improvements, and software platform revisions. Integrated functional testing was performed to determine the pressure drop, air flow rate, and the maximum amount of fluid capable of being discharged from the UMS to the WHC. This paper will detail the results of the science and the functional integration tests.

Rodriquez, Branelle R.↗

Integration of an expert system into a user interface language demonstration

The need for a User Interface Language (UIL) has been recognized by the Space Station Program Office as a necessary tool to aid in minimizing the cost of software generation by multiple users. Previous history in the Space Shuttle Program has shown that many different areas of software generation, such as operations, integration, testing, etc., have each used a different user command language although the types of operations being performed were similar in many respects. Since the Space Station represents a much more complex software task, a common user command language--a user interface language--is required to support the large spectrum of space station software developers and users. To assist in the selection of an appropriate set of definitions for a UIL, a series of demonstration programs was generated with which to test UIL concepts against specific Space Station scenarios using operators for the astronaut and scientific community. Because of the importance of expert system in the space station, it was decided that an expert system should be embedded in the UIL. This would not only provide insight into the UIL components required but would indicate the effectiveness with which an expert system could function in such an environment.

Stclair, D. C.↗

SEDS1 mission software verification using a signal simulator

The first flight of the Small Expendable Deployer System (SEDS1) is scheduled as the secondary payload of a Delta II in late 1992. The objective of the SEDS1 mission is to collect data to validate the concept of tethered satellite systems and to verify computer simulations used to predict their behavior. A series of tests will be performed to exercise the software modules which make up the Mission Software of the SEDS Data System. These tests will be performed by using a SEDS Signal Simulator to generate signals which will simulate the inputs normally produced by sensors and circuits in the SEDS system. The SEDS Signal Simulator will be used in the debugging and in the formal verification of the SEDS1 Mission Software. The Simulator will not only emulate normal flight conditions but also exercise all modules written to handle anticipated anomalous flight conditions, conditions that would be difficult to reproduce and control with actual SEDS hardware. The simulator will help to expedite software development and to increase the confidence of the users of the Mission Software. With little modification, the Simulator should be useful in the software development of future SEDS flights.

Pierson, William E.↗

Universal computer test stand (recommended computer test requirements)

Techniques are considered which would be used to characterize areospace computers with the space shuttle application as end usage. The system level digital problems which have been encountered and documented are surveyed. From the large cross section of tests, an optimum set is recommended that has a high probability of discovering documented system level digital problems within laboratory environments. Defined is a baseline hardware, software system which is required as a laboratory tool to test aerospace computers. Hardware and software baselines and additions necessary to interface the UTE to aerospace computers for test purposes are outlined.

Source record↗

A Reference Model for Software and System Inspections. White Paper

Software Quality Assurance (SQA) is an important component of the software development process. SQA processes provide assurance that the software products and processes in the project life cycle conform to their specified requirements by planning, enacting, and performing a set of activities to provide adequate confidence that quality is being built into the software. Typical techniques include: (1) Testing (2) Simulation (3) Model checking (4) Symbolic execution (5) Management reviews (6) Technical reviews (7) Inspections (8) Walk-throughs (9) Audits (10) Analysis (complexity analysis, control flow analysis, algorithmic analysis) (11) Formal method Our work over the last few years has resulted in substantial knowledge about SQA techniques, especially the areas of technical reviews and inspections. But can we apply the same QA techniques to the system development process? If yes, what kind of tailoring do we need before applying them in the system engineering context? If not, what types of QA techniques are actually used at system level? And, is there any room for improvement.) After a brief examination of the system engineering literature (especially focused on NASA and DoD guidance) we found that: (1) System and software development process interact with each other at different phases through development life cycle (2) Reviews are emphasized in both system and software development. (Figl.3). For some reviews (e.g. SRR, PDR, CDR), there are both system versions and software versions. (3) Analysis techniques are emphasized (e.g. Fault Tree Analysis, Preliminary Hazard Analysis) and some details are given about how to apply them. (4) Reviews are expected to use the outputs of the analysis techniques. In other words, these particular analyses are usually conducted in preparation for (before) reviews. The goal of our work is to explore the interaction between the Quality Assurance (QA) techniques at the system level and the software level.

He, Lulu↗