Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “sequencing commanding operations”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Survey of Command Execution Systems for NASA Spacecraft and Robots

NASA spacecraft and robots operate at long distances from Earth Command sequences generated manually, or by automated planners on Earth, must eventually be executed autonomously onboard the spacecraft or robot. Software systems that execute commands onboard are known variously as execution systems, virtual machines, or sequence engines. Every robotic system requires some sort of execution system, but the level of autonomy and type of control they are designed for varies greatly. This paper presents a survey of execution systems with a focus on systems relevant to NASA missions.

Verma, Vandi↗
NASA NTRS1993

Connecting science and operations: The operations coordinator

For a current space mission under development at the Applied Physics Laboratory, the Mission Operations staff includes a team of 'Operations Coordinators' who have been working with the Mission Science and Spacecraft Development teams since completion of mission conceptual design. The Operations Coordinators are responsible for bringing knowledge of the spacecraft to the Mission Science team and bringing knowledge of the experiment requirements to the Spacecraft Development and Mission Operations teams. Once on-orbit operations begin, the Operations Coordinators will be responsible for implementation of specific science experiments from analysis through scheduling, generation of spacecraft command sequences, delivery of science data to the end user, and operations assessment. The Operations Coordinator concept is proving very effective during the development phase of the current mission.

Marshall, Madeleine H.↗
NASA NTRS1994

(abstract) Automated Constraint Checking of Spacecraft Command Sequences

Making certain that spacecraft command sequences do not violate any constraints is often tedious and expensive in terms of both personnel and software development. To reduce this cost, we have pursued the development of a flexible system for specifying models of spacecraft behavior in response to commands as well as constraints on that behavior. The potential need for modeling complex spacecraft behavior required that the system be designed to be usable both on a conventional workstation and a parallel supercomputer. Finally, it needed to be intuitive enough for the the intended mission operations users to easily design sets of rules and models to automate tedious, resource-consuming constraint checking of commands. We have defined a Specification And Verification Environment (SAVE) for spacecraft flight rules.

automation spacecraft command sequences constraint↗
NASA NTRS1990

Failure of the ERBE scanner instrument aboard NOAA 10 spacecraft and results of failure analysis

The Earth Radiation Budget Experiment (ERBE) scanner instrument on the NOAA 10 spacecraft malfunctioned on May 22, 1989, after more than 4 years of in-flight operation. After the failure, all instrument operational mode commands were tested and the resulting data analyzed. Details of the tests and analysis of output data are discussed therein. The radiometric and housekeeping data appear to be valid. However, the instrument will not correctly execute operational scan mode commands or the preprogrammed calibration sequences. The data indicate the problem is the result of a failure in the internal address decoding circuity in one of the ROM (read only memory) chips of the instrument computer.

Miller, J. B.↗
NASA NTRS1998

RHETT/EPDM Performance Characterization

The 0.6 kW Electric Propulsion Demonstration Module (EPDM) flight thruster system was tested in a large vacuum facility for performance measurements and functional checkout. The thruster was operated at a xenon flow rate of 3.01 mg/s, which was supplied through a self-contained propellant system. All power was provided through a flight-packaged power processing unit, which was mounted in vacuum on a cold plate. The thruster was cycled through 34 individual startup and shutdown sequences. Operating periods ranged from 3 to 3600 seconds. The system responded promptly to each command sequence and there were no involuntary shutdowns. Direct thrust measurements indicated that steady state thrust was temperature sensitive, and varied from a high of 41.7 mN at 16 C, to a low of 34.8 mN at 110 C. Short duration thruster firings showed rapid response and good repeatability.

Haag, T.↗
NASA NTRS2000

Remotely-Sensed Geology from Lander-Based to Orbital Perspectives: Results for FIDO Rover Field Tests

Tests of the FIDO (Field Integration Design and Operations) rover and Athena-like operational scenarios were conducted May 7-16, 2000. A group located at the Jet Propulsion Lab, Pasadena, CA, formed the Core Operations Team (COT) that designed experiments and command sequences while another team tracked, maintained, and secured the rover in the field. The COT had no knowledge of the specific field location, thus the tests were done "blind." In addition to FIDO rover instrumentation, the COT had access to LANDSAT 7, TIMS, and AVIRIS regional coverage and color descent images. Using data from the FIDO instruments, primarily a color microscopic imager (CMI), infrared point spectrometer (IPS; 1.5-2.4 microns), and a three-color stereo panoramic camera (Pancam), the COT correlated lithologic features (mineralogy, rock types) from the simulated landing site to a regional scale. The May test results provide an example of how to relate site geology from landed rover investigations to the regional geology using remote sensing. The capability to relate mineralogic signatures using the point IR spectrometer to remotely sensed, multispectral or hyperspectral data proved to be key to integration of the in-situ and remote data. This exercise demonstrated the potential synergy between lander-based and orbital data, and highlighted the need to investigate a landing site in detail and at multiple scales.

Jolliff, B.↗
NASA NTRSDate not supplied

Atacama Rover Astrobiology Drilling Studies Project: Final Year

The Atacama Rover Astrobiology Drilling Studies (ARADS) project, a simulated Mars rover biomarker detection mission, was iteratively developed over four years from 2015 -2019, including three NASA centers, the Centro de Astrobiologia, Johns Hopkins University, Honeybee Robotics, Maxar and the University of Antofagasta. The final (4th) ARADS field season, in 2019, tested an integrated mobile life-prospecting platform loosely inspired by the 2000’s Astrobiology Field Laboratory concept, with a 1m rotary-percussive drill and sample transfer robot arm that fed three astrobiology instruments operating in-situ on the KREX2 medium rover prototype. A fourth instrument was field tested earlier in 2019 due to flight mission requirements. In the final ARADS field deployment in September 2019, the project conducted a remote mission operation simulation (Stoker 2022)demonstrating sample drilling, acquisition and transfer into the rover instruments (while minimizing cross-contamination), performing in-situ analysis of the samples, and returning the results to a remote science operations team(which commanded the daily science goals and uploaded operations sequences).

astrobiology↗
NASA NTRS2000

Multi-Agent Diagnosis and Control of an Air Revitalization System for Life Support in Space

An architecture of interoperating agents has been developed to provide control and fault management for advanced life support systems in space. In this adjustable autonomy architecture, software agents coordinate with human agents and provide support in novel fault management situations. This architecture combines the Livingstone model-based mode identification and reconfiguration (MIR) system with the 3T architecture for autonomous flexible command and control. The MIR software agent performs model-based state identification and diagnosis. MIR identifies novel recovery configurations and the set of commands required for the recovery. The AZT procedural executive and the human operator use the diagnoses and recovery recommendations, and provide command sequencing. User interface extensions have been developed to support human monitoring of both AZT and MIR data and activities. This architecture has been demonstrated performing control and fault management for an oxygen production system for air revitalization in space. The software operates in a dynamic simulation testbed.

Malin, Jane T.↗
NASA NTRS2012

Rapid Diagnostics of Onboard Sequences

Keeping track of sequences onboard a spacecraft is challenging. When reviewing Event Verification Records (EVRs) of sequence executions on the Mars Exploration Rover (MER), operators often found themselves wondering which version of a named sequence the EVR corresponded to. The lack of this information drastically impacts the operators diagnostic capabilities as well as their situational awareness with respect to the commands the spacecraft has executed, since the EVRs do not provide argument values or explanatory comments. Having this information immediately available can be instrumental in diagnosing critical events and can significantly enhance the overall safety of the spacecraft. This software provides auditing capability that can eliminate that uncertainty while diagnosing critical conditions. Furthermore, the Restful interface provides a simple way for sequencing tools to automatically retrieve binary compiled sequence SCMFs (Space Command Message Files) on demand. It also enables developers to change the underlying database, while maintaining the same interface to the existing applications. The logging capabilities are also beneficial to operators when they are trying to recall how they solved a similar problem many days ago: this software enables automatic recovery of SCMF and RML (Robot Markup Language) sequence files directly from the command EVRs, eliminating the need for people to find and validate the corresponding sequences. To address the lack of auditing capability for sequences onboard a spacecraft during earlier missions, extensive logging support was added on the Mars Science Laboratory (MSL) sequencing server. This server is responsible for generating all MSL binary SCMFs from RML input sequences. The sequencing server logs every SCMF it generates into a MySQL database, as well as the high-level RML file and dictionary name inputs used to create the SCMF. The SCMF is then indexed by a hash value that is automatically included in all command EVRs by the onboard flight software. Second, both the binary SCMF result and the RML input file can be retrieved simply by specifying the hash to a Restful web interface. This interface enables command line tools as well as large sophisticated programs to download the SCMF and RMLs on-demand from the database, enabling a vast array of tools to be built on top of it. One such command line tool can retrieve and display RML files, or annotate a list of EVRs by interleaving them with the original sequence commands. This software has been integrated with the MSL sequencing pipeline where it will serve sequences useful in diagnostics, debugging, and situational awareness throughout the mission.

Starbird, Thomas W.↗
NASA NTRS2006

Spitzer Space Telescope Sequencing Operations Software, Strategies, and Lessons Learned

The Space Infrared Telescope Facility (SIRTF) was launched in August, 2003, and renamed to the Spitzer Space Telescope in 2004. Two years of observing the universe in the wavelength range from 3 to 180 microns has yielded enormous scientific discoveries. Since this magnificent observatory has a limited lifetime, maximizing science viewing efficiency (ie, maximizing time spent executing activities directly related to science observations) was the key operational objective. The strategy employed for maximizing science viewing efficiency was to optimize spacecraft flexibility, adaptability, and use of observation time. The selected approach involved implementation of a multi-engine sequencing architecture coupled with nondeterministic spacecraft and science execution times. This approach, though effective, added much complexity to uplink operations and sequence development. The Jet Propulsion Laboratory (JPL) manages Spitzer s operations. As part of the uplink process, Spitzer s Mission Sequence Team (MST) was tasked with processing observatory inputs from the Spitzer Science Center (SSC) into efficiently integrated, constraint-checked, and modeled review and command products which accommodated the complexity of non-deterministic spacecraft and science event executions without increasing operations costs. The MST developed processes, scripts, and participated in the adaptation of multi-mission core software to enable rapid processing of complex sequences. The MST was also tasked with developing a Downlink Keyword File (DKF) which could instruct Deep Space Network (DSN) stations on how and when to configure themselves to receive Spitzer science data. As MST and uplink operations developed, important lessons were learned that should be applied to future missions, especially those missions which employ command-intensive operations via a multi-engine sequence architecture.

missions operations↗
NASA NTRS2014

LADEE Multi-Domain Simulation

The Lunar Atmosphere Dust Environment Explorer (LADEE) was a small explorer class spacecraft that was launched on Sept 7, 2013 and that was de-orbited and successfully impacted the Moons surface on April 17, 2014 after completing all of the mission objectives. The low-cost rapidly prototyped hardware design used for the spacecraft was extend to the development of the software base. To achieve this goal, a Model Based Design approach was utilized to develop the onboard flight software, and out of this development a model based multipurpose simulator was created of the LADEE spacecraft and its mission environment. This simulator extended the traditional function of propagating the vehicle's kinematic and rotational states and included the electrical and thermal states propagation. Traditionally, these domains are handled by domain specific high fidelity simulations that use the states histories from other domains as input. By reducing the fidelity and abstracting the relevant features being monitored and controlled by the flight software, it was possible to model the coupling across these domains resulting in more accurate overall system behavior. A faster than real-time workstation (WSIM) version of the LADEE simulator was used to develop and test the software control algorithms in the Simulink environment. To maximize the performance of the simulation, modeling knobs were introduced to reduce the resolution of the some of the domains models when the effects of that domain were not significant for the scope of that simulation. The automatic code generation feature in Simulink was used to port the simulation to several real-time environments to support Processor-in-the-Loop (PIL) and Hardware-in-the-Loop (HIL) testing, verification and validation. The real-time environment required that the design of each of the domain models be deterministic as possible in the time required to perform all of the calculations to update its states. The simulation interface was designed to be compatible with the command interface employed by the LADEE mission operation team. The WSIM, PIL, and HIL simulators thus used a common interface and thus were used for flight software testing, for mission operations personnel training (nominal and off-nominal operations) prior to the mission and to perform command sequence verification during the mission. This presentation will look at the modeling strategies used to create a common interface to the simulator and to model and couple multiple domains within the simulation, the results of those strategies, and the lessons learned.

Multi-Domain↗
NASA NTRS2017

Dawn Spacecraft Performance at Ceres: Results of Hybrid Control for Ceres Mapping

Dawn is a low-thrust interplanetary spacecraft currently orbiting the dwarf planet Ceres, to better understand the early creation of the solar system. Launched in September 2007, Dawn arrived at Vesta in July 2011. After a 16-month successful science campaign at Vesta, Dawn departed for Ceres, arriving in early 2015. The Dawn spacecraft uses both reaction wheel assemblies (RWA) and a reaction control system (RCS) to provide 3-axis attitude control for the spacecraft. Reaction wheels were designed to be the primary system for attitude control, however two wheels have shown high friction anomalies and have been removed from service. The project has implemented a hybrid control algorithm using two reaction wheels and RCS thrusters. This hybrid control capability enabled Dawn to achieve very high science return, while significantly conserving remaining hydrazine propellant. With only two remaining healthy RWA’s, hybrid control became part of the baseline plan for Ceres science operations. The Dawn team developed specific operational approaches in which sequences were developed with careful consideration of science versus resource trades. Commanding and sequence planning also incorporated contingency planning, in the event that another reaction wheel may fail. Despite the differences in operational approach between Vesta and Ceres, both campaigns achieved very rich scientific data return. This paper highlights Dawn’s recent flight experience with hybrid attitude control during Ceres orbit operations. The discussion includes the approaches utilized by the Dawn team to address unique operational challenges presented by the hybrid approach, and reviews spacecraft performance under hybrid control in low orbit at Ceres. Additionally, methods used to optimize hydrazine use and thereby extend the science campaign will be presented. Finally, a preliminary assessment of an orbit transfer with two reaction wheels, during extended mission operations, is discussed.

Smith, Brett A.↗
NASA NTRS2006

Multiuser Collaboration with Networked Mobile Devices

In this paper we describe a multiuser collaboration infrastructure that enables multiple mission scientists to remotely and collaboratively interact with visualization and planning software, using wireless networked personal digital assistants(PDAs) and other mobile devices. During ground operations of planetary rover and lander missions, scientists need to meet daily to review downlinked data and plan science activities. For example, scientists use the Science Activity Planner (SAP) in the Mars Exploration Rover (MER) mission to visualize downlinked data and plan rover activities during the science meetings [1]. Computer displays are projected onto large screens in the meeting room to enable the scientists to view and discuss downlinked images and data displayed by SAP and other software applications. However, only one person can interact with the software applications because input to the computer is limited to a single mouse and keyboard. As a result, the scientists have to verbally express their intentions, such as selecting a target at a particular location on the Mars terrain image, to that person in order to interact with the applications. This constrains communication and limits the returns of science planning. Furthermore, ground operations for Mars missions are fundamentally constrained by the short turnaround time for science and engineering teams to process and analyze data, plan the next uplink, generate command sequences, and transmit the uplink to the vehicle [2]. Therefore, improving ground operations is crucial to the success of Mars missions. The multiuser collaboration infrastructure enables users to control software applications remotely and collaboratively using mobile devices. The infrastructure includes (1) human-computer interaction techniques to provide natural, fast, and accurate inputs, (2) a communications protocol to ensure reliable and efficient coordination of the input devices and host computers, (3) an application-independent middleware that maintains the states, sessions, and interactions of individual users of the software applications, (4) an application programming interface to enable tight integration of applications and the middleware. The infrastructure is able to support any software applications running under the Windows or Unix platforms. The resulting technologies not only are applicable to NASA mission operations, but also useful in other situations such as design reviews, brainstorming sessions, and business meetings, as they can benefit from having the participants concurrently interact with the software applications (e.g., presentation applications and CAD design tools) to illustrate their ideas and provide inputs.

ground operations↗
NASA NTRS2005

Data visualization for effective rover sequencing

The Rover Sequencing and Visualization Program is a suite of toos for the commanding of planetary rovers which are subject to significant light time delay and thus are unsuitable for tele-operation.

surface operations↗
NASA NTRS2008

Converting from DDOR SASF to APF

A computer program called ddor_sasf2apf converts delta-door (delta differential one-way range) request from an SASF (spacecraft activity sequence file) format to an APF (apgen plan file) format for use in the Mars Reconnaissance Orbiter (MRO) missionplanning- and-sequencing process. The APF is used as an input to APGEN/AUTOGEN in the MRO activity- planning and command-sequencegenerating process to sequence the delta-door (DDOR) activity. The DDOR activity is a spacecraft tracking technique for determining spacecraft location. The input to ddor_sasf2apf is an input request SASF provided by an observation team that utilizes DDOR. ddor_sasf2apf parses this DDOR SASF input, rearranging parameters and reformatting the request to produce an APF file for use in AUTOGEN and/or APGEN. The benefit afforded by ddor_sasf2apf is to enable the use of the DDOR SASF file earlier in the planning stage of the command-sequence-generating process and to produce sequences, optimized for DDOR operations, that are more accurate and more robust than would otherwise be possible.

Gladden, Roy E.↗